Cell Management(5G RAN2.1_Draft a)

(1)

5G RAN

Cell Management Feature Parameter

Description

Issue

Issue Draft ADraft A Date

(2)

(3)

No part of

No part of this document may be reproduced or transmitted in any form or this document may be reproduced or transmitted in any form or by any means without prior writtenby any means without prior written consent of Huawei Technologies Co., Ltd.

consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other tradem

All other trademarks and trade arks and trade names mennames mentioned in thitioned in this document as document are the property ore the property of their respectivef their respective holders.

holders. Notice Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the The purchased products, services and features are stipulated by the contract made between Huawei and the customer

customer. All . All or part of or part of the products, services and features described in this document may not be the products, services and features described in this document may not be within thewithin the purchase scope or the usage scope. Unless otherwise specified in the contract, all

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, informatiostatements, information,n, and recommendations in this document are provided "AS IS" without warranties, guarantees or

and recommendations in this document are provided "AS IS" without warranties, guarantees or representatio

representations of any ns of any kind, either express or implied.kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but

preparation of this document to ensure accuracy of the contents, but all statements, information, andall statements, information, and recommend

recommendations in this document do not constitute a ations in this document do not constitute a warranty of any kind, express or warranty of any kind, express or implied.implied.

Huawei Technologies Co., Ltd.

Address:

Address: Huawei InduHuawei Industrial Basestrial Base Bantian, Longgang Bantian, Longgang Shenzhen 518129 Shenzhen 518129

People's Republic of China People's Republic of China Website:

Website: http://www.huawei.comhttp://www.huawei.com

Email:

(4)

1 Change

History...

...

.

1

1.1 5G RAN2

1.1 5G RAN2.1 Draft A .1 Draft A (2018-12-30)...(2018-12-30)...11

2 General

Statements...

...

3

3 3 Cell Ma

3 Cell Management...

nagement...

...

...5

..5

3.1 Principles

3.1 Principles...55

3.1.1 Definiti

3.1.1 Definition...5on...5

3.1.2 Related

3.1.2 RelatedConcepts...Concepts...55

3.1.2.1 Cell....

3.1.2.1 Cell...6...6

3.1.2.2 Sector

3.1.2.2 Sector ...77

3.1.2.3 Sector

3.1.2.3 Sector Equipment...Equipment...77

3.1.2.4 RF Eq

3.1.2.4 RF Equipment...7uipment...7

3.1.2.5 Baseb

3.1.2.5 Baseband Equipment...and Equipment...77

3.1.2.6 NR D

3.1.2.6 NR DU Cell TRP...7U Cell TRP...7

3.1.2.7 NR D

3.1.2.7 NR DU Cell Coverage Area...U Cell Coverage Area...77

3.1.3 Typical

3.1.3 TypicalScenarios...7Scenarios...7

3.1.3.1 Comm

3.1.3.1 Common on Cell...Cell...8...8

3.1.3.2 Combi

3.1.3.2 Combined-RRU ned-RRU Cell...Cell...88

3.1.3.3 Cells i

3.1.3.3 Cells in Multi-Carrier n Multi-Carrier Sectors...Sectors...8...8

3.1.3.4 Uplink

3.1.3.4 Uplink and Dow and Downlink Decoupling nlink Decoupling Cells...Cells...99

3.1.3.5 RF Co

3.1.3.5 RF Combination Cell...mbination Cell...99

3.1.4 Cell-rela

3.1.4 Cell-related ted Parameters...Parameters...10...10

3.1.4.1 Freque

3.1.4.1 Frequency Band...ncy Band...1010

3.1.4.2 NARF

3.1.4.2 NARFCN...CN...1010

3.1.4.3 SSB F

3.1.4.3 SSB Frequency-Domain Position...12requency-Domain Position...12

3.1.4.4 Cell Bandwidth...

3.1.4.4 Cell Bandwidth...1313

3.1.4.5 Subca

3.1.4.5 Subcarrier rrier Spacing...Spacing...13...13

3.1.4.6 Uplink

3.1.4.6 Uplink -Downlink Slot Configuration...13-Downlink Slot Configuration...13

3.1.4.7 Trans

3.1.4.7 Transmit/Receive mit/Receive Mode...Mode...13...13

3.1.4.8 Maximum Transmit Power...

3.1.4.8 Maximum Transmit Power...1313

3.2 Network A

3.2 Network Analysis...nalysis...1414

3.2.1 Benefits...

3.2.1 Benefits...1414

3.2.2

3.2.2 Impacts...Impacts...14...14

C

(5)

3.3 Requirements... 14

3.3.1 Licenses... 14

3.3.2 Software...14

3.3.3 Hardware... 15

3.4 Operation and Maintenance...16

3.4.1 Data Configuration... 17

3.4.1.1 Data Preparation... 17

3.4.1.2 Using MML Commands...23

3.4.1.3 Using the CME... 29

3.4.2 Activation Observation...29

4 Glossary...30

5 Reference Documents...31

(6)

1

Change History

This section describes changes not included in the "Parameters", "Counters", "Glossary", and "Reference Documents" chapters. These ch anges include:

l Technical changes

Changes in functions and their corresponding parameters l Editorial changes

Improvements or revisions to the documentation

1.1 5G RAN2.1 Draft A (2018-12-30)

This issue introduces the following changes to 5G RAN2.0 01 (2018-10-10).

Technical Changes

Change Description Parameter Change Base Station

Model Changed the name of the MO NRCell

containing theTrackingAreaId parameter to

NRDUCELL. For details, see:

l 3.4.1.1 Data Preparation l 3.4.1.2 Using MML Commands NRDUCell.Tracking AreaId 5900 series base stations

Added the configurations for the frequency-domain position of the synchronization signal block (SSB). For details, see3.1.4.3 SSB

Frequency-Domain Position.

Added the following parameters: l NRDUCell. SsbDe scMethod l NRDUCell. SsbFr eqPos 5900 series base stations

Added feature support for LampSite base stations. For details, see:

l 3.1.3.5 RF Combination Cell

l 3.4.1.2 Using MML Commands

NA DBS5900

LampSite base stations

(7)

Editorial Changes

Optimized descriptions for configuring the SSB center frequency. For details, see 3.1.4.2

NARFCN.

Added support for the typical scenario of combined-RRU/RFU-sector cells. For details, see

3.1.3.2 Combined-RRU Cell.

(8)

2

General Statements

Purpose

Feature Parameter Description documents are intended to acquaint readers with: l The technical principles of features and their related parameters

l The scenarios where these features are used, the benefits they provide, and the impact they have on networks and functions

l Requirements of the operating environment that must be met before feature activation l Parameter configuration required for feature activation, verification of feature activation,

and monitoring of feature performance

NOTE

This document only provides guidance for feature activation. Feature deployment and feature gains depend on the specifics of the network scenario where the feature is deployed. To achieve the desired gains, contact Huawei professional service engineers.

Software Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter Description documents apply only to the corresponding software release. For future software releases, refer to the corresponding updated product documentation.

Trial Features

Trial features are features that are not yet ready for full commercial release for certain

reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible. However, these features can still be used for testing purposes or commercial network trials. Anyone who desires to use the trial features shall contact Huawei and enter into a

memorandum of understanding (MoU) with Huawei prior to an official application of such trial features. Trial features are not for sale in the current version but customers may try them for free.

Customers acknowledge and undertake that trial features may have a certain degree of risk due to absence of commercial testing. Before using them, customers shall fully understand not only the expected benefits of such trial features but also the possible impact they may exert on the network. In addition, customers acknowledge and undertake that since trial features are free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the trial features. Huawei does not promise that problems with trial features will be resolved in

(9)

the current version. Huawei reserves the rights to convert trial features into commercial

features in later R/C versions. If trial features are converted into commercial features in a later version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the said commercial features. If a customer fails to purchase such a license, the trial feature(s) will be invalidated automatically when the product is upgraded.

(10)

3

Cell Management

3.1 Principles

3.1.1 Definition

Cell management refers to management of communications resources by establishing cells and configuring related parameters.

3.1.2 Related Concepts

Figure 3-1 illustrates the components involved in cell management.

(11)

Figure 3-1 Components involved in cell management

3.1.2.1 Cell

A cell is an area where radio communications services are provided. It is the fundamental unit of a radio network. Run the ADD NRCELL andADD NRDUCELL commands to add cell resources for NR networks. Coverage of the entire radio network is provided by cells.

(12)

3.1.2.2 Sector

A sector is an area covered by antennas. A sector is added by running the ADD SECTOR

command. Each sector uses one or more radio carriers to provide coverage. A sector can be omnidirectional or directional, depending on the antenna type.

l Omnidirectional

An omnidirectional sector uses omnidirectional antennas to provide 360° coverage with the antenna at the center. In light-traffic areas, the deployment of omnidirectional sectors means fewer antennas need to be deployed, which reduces equipment cost.

l Directional

A directional sector uses directional antennas to provide coverage. Each directional antenna covers a 60° or 120° sector area, depending on whether there are six or three sectors configured on the gNodeB. The azimuth of each sector is slightly over 60 or 120 degrees in actual scenarios so that the sectors can overlap to ensure seamless coverage. In heavy-traffic areas, the deployment of directional sectors supports more traffic volume. Directional sectors allow for greater flexibility in area and sector planning.

3.1.2.3 Sector Equipment

Sector equipment is a set of antennas that are used to provide coverage for the same sector. A sector is linked to a set of antennas comprising a specific piece of sector equipment by

running theADD SECTOR andADD SECTOREQM commands.

3.1.2.4 RF Equipment

RF equipment is a set of RF processing units, such as remote radio units (RRUs) or active antenna units (AAUs). RF equipment is added and associated with CPRI ports on baseband processing units (BBPs) by running theADD RRUCHAIN andADD RRU commands.

3.1.2.5 Baseband Equipment

A set of baseband equipment consists of one or more BBPs. A BBP is added by running the

ADD BRD command. It can be added to a piece of baseband equipment by running the ADD

BASEBANDEQM command.

The baseband equipment for NR must support both uplink and downlink transmissions.

3.1.2.6 NR DU Cell TRP

An NR DU cell transmission reception point (TRP) specifies the baseband equipment used by a cell. If no baseband equipment is specified for the NR DU cell TRP, the BBP directly

connected to the RRU or AAU is used by default. An NR DU cell TRP is added by running

theADD NRDUCELLTRP command. Each common cell corresponds to only one NR DU

cell TRP.

3.1.2.7 NR DU Cell Coverage Area

An NR DU cell coverage area refers to a radio coverage area of an NR DU cell. You can run

theADD NRDUCELLCOVERAGE command to add an NR DU cell coverage area.

3.1.3 Typical Scenarios

(13)

3.1.3.1 Common Cell

A common cell is a cell that is established in a sector served by an RF module. The cell shown inFigure 3-2 is a common cell.

Figure 3-2 Common cell

3.1.3.2 Combined-RRU Cell

A combined-RRU cell is served by two RRUs connected to the same antenna to cover the same area. This networking applies only to NR SUL (supplementary uplink) cells. SUL cells supports combination of 1T2R or 2T2R RRUs.

Figure 3-3 Combined-RRU-sector cell (using 2T2R RRUs as an example)

If combination of RRUs in star topology applies to three SUL sectors, six CPRI ports are required. If the baseband processing unit (BBP) cannot provide enough CPRI ports, cascading networking or LNR CPRI MUX networking is an option. In cascading networking, the fiber optic cable between two RRUs to be cascaded must be less than 100 m. Two combined RRUs must be connected to the same BBP.

3.1.3.3 Cells in Multi-Carrier Sectors

In this scenario, cells working on different frequencies are set up in a single sector, as shown inFigure 3-4. This solution helps to expand system capacity without having to deploy additional base stations.

Figure 3-4 Cells in a multi-carrier sector

(14)

Multi-carrier sectors are used in densely populated areas where traffic increases rapidly, such as exhibition centers, airport waiting areas, shopping malls, central business districts, and high-end residential areas.

For details about carrier specifications, see RRU technical descriptions in 3900 & 5900 Series Base Station Product Documentation.

3.1.3.4 Uplink and Downlink Decoupling Cells

Uplink and downlink decoupling cells are cells that use high bands (such as 3.5 GHz) for downlink and low bands (such as 1.8 GHz/700 MHz) for uplink to improve uplink coverage.

Figure 3-5 illustrates an uplink and downlink decoupling cell.

Figure 3-5 Uplink and downlink decoupling cell

3.1.3.5 RF Combination Cell

In a LampSite scenario, RF signals from multiple pRRUs are combined in the RHUB to form an RF combination cell. That is, pRRUs connected to the same or different RHUBs are

combined to serve one cell, extending cell coverage. See Figure 3-6.

Figure 3-6 RF combination cell

(15)

3.1.4 Cell-related Parameters

This chapter describes the following cell-related parameters: frequency band, NR absolute radio frequency channel number (NARFCN), SSB frequency-domain position, cell

bandwidth, subcarrier spacing, uplink-downlink slot configuration, transmit/receive mode, and maximum transmit power.

For details about other parameters of a cell, see the corresponding feature documentation. For example, for details about CPRI compression, see CPRI Compression.

This version supports only TDD cells and SUL cells.

3.1.4.1 Frequency Band

The frequency band of a cell is specified by the NRCell.FrequencyBand andNRDUCell

parameters. The two parameters must be set to the same value.Table 3-1 lists the frequency bands supported by NR cells. For details, see section 5.2 "Operating bands for NR" in 3GPP

TS 38.104 V15.2.0.

Table 3-1 Frequency bands supported by NR cells

Frequency Band

Uplink Frequency Range (Lowest and Highest Frequencies)

Downlink Frequency Range (Lowest and Highest

Frequencies) Duplex Mode n77 3300 MHz 4200 MHz 3300 MHz 4200 MHz TDD n78 3300 MHz 3800 MHz 3300 MHz 3800 MHz TDD n79 4400 MHz 5000 MHz 4400 MHz 5000 MHz TDD

n80 1710MHz 1785MHz N/A N/A SUL

3.1.4.2 NARFCN

The NARFCN, center frequency of the cell carrier, is used to determine the center frequency-domain position of an NR DU cell. An NARFCN is classified into uplink NARFCN and downlink NARFCN.

The uplink NARFCN must be configured for an SUL cell based on the network plan. It is specified by NRDUCell.UlNarfcn. For non-SUL cells, whether to configure the uplink NARFCN is based on the value of theNRDUCell.UlNarfcnConfigInd parameter.

l If NRDUCell.UlNarfcnConfigInd is set to CONFIG, configure the uplink NARFCN

and downlink NARFCN by respectively specifying theNRDUCell.UlNarfcn and

(16)

l If NRDUCell.UlNarfcnConfigInd is set to NOT_CONFIG, calculate the uplink NARFCN and downlink NARFCN based on the start and end frequencies of the cell.

The calculation procedure is as follows:

a. Determine the downlink center frequency of a cell based on the downlink start frequency and downlink bandwidth of the cell.

Cell's downlink center frequency (DLCELL_REF) = Cell downlink start frequency (MHz) + Cell downlink bandwidth (MHz)/2

b. Determine the uplink center frequency of a cell based on the uplink start frequency and uplink bandwidth of the cell.

Cell's uplink center frequency (ULCELL_REF) = Cell uplink start frequency (MHz) + Cell uplink bandwidth (MHz)/2

c. Calculate the downlink and uplink center NARFCNs of the cell based on the cell downlink center frequency (DLCELL_REF) and the cell uplink center frequency (ULCELLREF), respectively.

Cell's downlink center NARFCN (N_REF-DLCELL) = Int{(DLCELL_REF - F_REF-Offs)/ ΔFGlobal + NREF-Offs}

Cell's uplink center NARFCN (N_REF-ULCELL) = Int{(ULCELL_REF - F_REF-Offs)/ ΔFGlobal + NREF-Offs}

Table 3-2 Requirements for available NARFCNs

Frequency Band Subcarrier Spacing Available NARFCN

n41 30 kHz The NARFCN must be an

integral multiple of 6.

even number.

n257 120 kHz The NARFCN must be an odd number.

Parameters involved in the formula are listed in Table 3-3.

(17)

Table 3-3 Parameters related to N_REF-CELL Frequency

Range (MHz)

ΔF_Global (MHz) F_REF-Offs (MHz) N_REF-Offs

0–3000 0.005 0 0

3000–24250 0.015 3000 600000

24250_–100000 0.06 24250.08 2016667

3.1.4.3 SSB Frequency-Domain Position

In an NR system, an SSB comprises a primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH. Each SSB provides 240 consecutive subcarriers. A UE searches for cells based on received PSS and SSS signals and obtains necessary

information from the received broadcast system messages. Then, the UE selects the most appropriate cell to camp on using the received information.

The SSB frequency-domain position indicates the SSB center frequency position of a cell. It is specified by the NRDUCell. SsbDescMethod andNRDUCell. SsbFreqPos parameters. The SSB frequency-domain position is not configured for SUL cells, but must be configured for TDD cells.

When the SSB frequency-domain position is configured,NRDUCell. SsbDescMethod is only set to SSB_DESC_TYPE_NARFCN.NRDUCell. SsbFreqPos specifies the NARFCN corresponding to the SSB center frequency.Table 3-4 lists theNRDUCell. SsbFreqPos

settings.

Table 3-4 SSB frequency-domain position configurations

Frequency Band

Cell Bandwidth SSB Frequency-Domain

Position n41 20 MHz, 50 MHz, 70MHz, 80 MHz, 90 MHz, and 100 MHz Value of NRDUCELL. DlNarfcn minus 36 n41 30MHz, 40 MHz, 60 and MHz Value of NRDUCELL. DlNarfcn n77, n78, and n79 20 MHz, 50 MHz, 70 MHz, 80 MHz, 90 MHz, and 100 MHz Value of NRDUCELL. DlNarfcn minus 12 n77, n78, and n79 30 MHz, 40 MHz, 60 and MHz Value of NRDUCELL. DlNarfcn n257, n258, and n260 100 MHz, and 200 MHz Value of NRDUCELL. DlNarfcn

(18)

3.1.4.4 Cell Bandwidth

The uplink and downlink bandwidths of a cell are respectively specified by the

NRDUCell.UlBandwidth andNRDUCell. DlBandwidth parameters. The uplink and

downlink bandwidths of a cell must be the same.

Table 3-5 lists the bandwidth supported by an NR cell.

Table 3-5 Bandwidth supported by an NR cell

Duplex Mode Supported Cell Bandwidth

TDD 40 MHz, 60 MHz, 80 MHz, 100 MHz

SUL 15 MHz, 20 MHz

3.1.4.5 Subcarrier Spacing

The subcarrier spacing of a cell is specified by the NRDUCell. SubcarrierSpacing parameter. l The subcarrier spacing of TDD cells must be set to 30 kHz.

l The subcarrier spacing of SUL cells must be set to 15 kHz.

3.1.4.6 Uplink-Downlink Slot Configuration

For a TDD cell, the uplink-downlink slot configuration must be specified. For details, see Standards Compliance.

3.1.4.7 Transmit/Receive Mode

The transmit/receive mode of a cell is specified by the NRDUCellTrp.TxRxMode parameter.

Table 3-6 lists the transmit/receive modes supported by NR cells.

Table 3-6 Transmit/receive modes supported by NR cells

Duplex Mode Supported Transmit/Receive Mode

TDD 8T8R, 1T1R, 2T2T, 4T4R, 32T32R, and 64T64R

SUL SUL stands for supplementary uplink. SUL cells, which are limited to uplink reception, support 2R and 4R.

NOTE

The cell must have the same TX/RX mode as the AAU/RRU.

3.1.4.8 Maximum Transmit Power

The maximum transmit power of a single antenna (P_{max_out}) is specified by the

NRDUCellTRP. MaxTransmitPower parameter. The total transmit power of a cell (P_Cell) is determined by the maximum transmit power of a single antenna (Pmax_out) and the number of

(19)

transmit antennas (N_Tx). N_Tx is configured by the NRDUCellTRP.TxRxMode parameter. The total transmit power of a cell is calculated as follows: PCell = Pmax_out + 10 x log10(NTx).

If multiple cells are served by the same R RU or AAU, the sum of Pmax_out of these cells must

be less than or equal to the maximum transmit power of the RRU's or AAU's transmit channel. Otherwise, ALM-29870 NR DU Cell TRP Unavailable is generated.

NOTE

l For details about the maximum transmit power of RRUs or AAUs when different quantities of carriers are configured, see the following section in 3900 & 5900 Series Base Station Product Documentation: 3900 & 5900 Series Base Station Technical Description > Typical Power

Configuration Reference for RF Modules.

l SUL cells involve only uplink transmission and therefore require no transmit power configurations.

3.2 Network Analysis

3.2.1 Benefits

The primary function of gNodeBs is to provide radio cell coverage for UEs. Cell management is mandatory.

3.2.2 Impacts

Network Impacts

None

Function Impacts

None

3.3 Requirements

3.3.1 Licenses

Cell establishment requires a valid capacity license. For details about capacity license control items, see License Management .

3.3.2 Software

Prerequisite Functions

None

Mutually Exclusive Functions

(20)

3.3.3 Hardware

Base Station Models

l 5900 series base stations

l DBS5900 LampSite base stations

Boards

Only the UBBPfw1 and UMPTe boards support this function. For details about the RATs supported by boards, see BBU5900 Hardware Description in 3900 & 5900 Series Base Station Product Documentation.

RF Modules

All NR-capable AAUs/RRUs/pRRUs support this function.

l For details about NR-capable AAUs, see AAU Technical Specifications. l For details about NR-capable RRUs, see RRU Technical Specifications.

l For details about NR-capable pRRUs, see DBS3900 LampSite & DBS5900 LampSite Technical Description.

Common Cells

Requirements for setting up common cells are as follows:

l The hardware resources of BBPs, CPRI ports, and RF modules meet the cell

requirements before the cell is established. For the hardware requirements of macro base stations, see the following section in 3900 & 5900 Series Base Station Product

Documentation: 3900 & 5900 Series Base Station Technical Description >Product Specifications.

l The transmit/receive mode of the cell must match the number of transmit/receive channels of the RF module or the cell will not work normally. For details about the number of transmit/receive channels supported by RF modules, see the following sections in 3900 & 5900 Series Base Station Product Documentation: 3900 & 5900 Series Base Station Technical Description >Product Specifications >Technical

Specifications of RRUs andTechnical Specifications of AAUs.

l The CPRI data rates for the BBP optical modules must match the cell bandwidths and transmit/receive modes when selecting optical modules for BBPs. For the constraints between the CPRI data rates and the cell bandwidths and transmit/receive modes, see the

following section in 3900 & 5900 Series Base Station Product Documentation: 3900 & 5900 Series Base Station Technical Description >Product Specifications >Technical

Specifications of the BBU5900.

l Bandwidths of the cells served by the RRUs/AAUs must fall within the frequency bands supported by the RRUs/AAUs.

l AAUs must be used to establish 32T32R or 64T64R cells. l RRUs must support 8T8R to establish 8-antenna cells.

The following table describes extra requirements for configuring TDD cells.

(21)

l If TDD cells under a base station have different uplink-downlink slot configurations, they must be bound to different BBPs. The uplink-downlink slot configurations of all TDD cells on the same BBP must be the same.

l If TDD cells under a base station have different subcarrier spacing, they must be bound to different BBPs. The subframe spacing of all TDD cells on the same BBP must be the same.

l If TDD cells under a base station have different bandwidths, they must be bound to different BBPs. The bandwidths of all TDD cells on the same BBP must be the same. l If both eCPRI 64T64R TDD cells and CPRI 64T64R TDD cells are served by the same

base station, they must be bound to different BBPs. The RF module models of all TDD cells on the same BBP must be the same.

l If TDD cells under a base station have different transmit/receive modes, they must be bound to different BBPs. The transmit/receive modes of all TDD cells on the same BBP

must be the same.

The following requirements for configuring high-frequency cell must apply:

Cells must be established on the BBP directly connected the RRU/AAU over the CPRI/eCPRI optic fiber, and such cells must also be bound to this BBP, if required.

Cells in a Multi-Carrier Sector

Requirements for setting up cells in multi-carrier sectors are as follows:

l The RRUs/AAUs must support multiple carriers. For details about RRUs/AAUs that support multiple carriers, see the following section in 3900 & 5900 Series Base Station Product Documentation: 3900 & 5900 Series Base Station Technical Description >

Product Specifications >Technical Specifications of RRUs orTechnical

Specifications of AAUs.

l The frequency range of the two cells must be within the frequency bands supported by the RRUs/AAUs.

l When two cells are configured for the same RF module, the bandwidths of the two cells must be the same.

l The frequency range of the two cells cannot overlap.

Uplink and Downlink Decoupling Cells

Requirements for establishing uplink and downlink decoupling cells are as follows: l One of the following band combinations is used.

3.5 GHz/3.7 GHz (subcarrier spacing of 30 kHz) + 1800 MHz (subcarrier spacing of 15 kHz)

4.9 GHz (subcarrier spacing of 30 kHz) + 1800 MHz (subcarrier spacing of 15 kHz) l The TDD cells and SUL cells must meet the following condition:

They are served by the same BBPs.

3.4 Operation and Maintenance

(22)

3.4.1 Data Configuration

3.4.1.1 Data Preparation

The following table describes the parameters that must be set in a SECTOR MO to configure a sector.

Parameter Name Parameter ID Setting Notes

Sector ID SECTOR . SECTORID Set this parameter to a unique value. Sector Name SECTOR . SECNAME N/A

Location Name SECTOR . LOCATIONN AME

N/A

User Label SECTOR .USERLABEL N/A Antenna Azimuth SECTOR . ANTAZIMUT

H

N/A

The following table describes the parameters that must be set in a SECTOREQM MO to configure a piece of sector equipment.

Sector Equipment ID

SECTOREQM. SECTOR

EQMID

N/A

Sector ID SECTOREQM. SECTOR ID N/A Sector Equipment Antenna SECTOREQM. SECTOR EQMANTENNA N/A Antenna Config Mode SECTOREQM. ANTCF GMODE

Set this parameter to BEAM only for massive MIMO cells.

RRU Cabinet No. SECTOREQM. RRUCN N/A RRU Subrack No. SECTOREQM. RRUSR

N

N/A

RRU Slot No. SECTOREQM. RRUSN N/A Beam Shape SECTOREQM. BEAMS

HAPE

Set this parameter to SEC_120DEG if

theSECTOREQM. ANTCFGMODE

parameter is set toBEAM. Beam Layer Split SECTOREQM. BEAML

AYERSPLIT

Set this parameter to None if the

SECTOREQM. ANTCFGMODE

parameter is set toBEAM.

(23)

Parameter Name Parameter ID Setting Notes Beam Azimuth

Offset

SECTOREQM. BEAMA

ZIMUTHOFFSET

Set this parameter to None if the

SECTOREQM. ANTCFGMODE

parameter is set toBEAM. Antenna Number SECTOREQM. ANTNU

M

-Cabinet No. of Antenna 1

SECTOREQM. ANT1CN This parameter is mandatory when

SECTOREQM. ANTCFGMODE is

set toANTENNAPORT. Subrack No. of

Antenna 1

SECTOREQM. ANT1SR

N

This parameter is mandatory when

set toANTENNAPORT. Slot No. of

Antenna 1

SECTOREQM. ANT1SN This parameter is mandatory when

set toANTENNAPORT. Channel No. of

Antenna 1

SECTOREQM. ANT1N This parameter is mandatory when

set toANTENNAPORT. Antenna 1 RX/TX

Mode

SECTOREQM. ANTTYP

E1

This parameter is mandatory when

set toANTENNAPORT.

The following table describes the parameters that must be set in a gNBOperator MO to configure an operator.

Operator ID gNBOperator.OperatorI d

N/A

Operator Name gNBOperator.Operator Name N/A Mobile Country Code gNBOperator. Mcc N/A Mobile Network Code gNBOperator. Mnc N/A

The following table describes the parameters that must be set in a gNBTrackingArea MO to configure a tracking area for an operator.

(24)

Parameter Name Parameter ID Setting Notes Tracking Area ID gNBTrackingArea.Track

ingAreaId

The setting of this parameter takes effect only for the gNodeB. The tracking area identity (TAI) specified by this parameter is different from the

TAI configured in the tracking area list (TAL) in the core network.

Tracking Area Code gNBTrackingArea.Tac N/A

The following table describes the parameters that must be set in an NRCell MO to configure an NR cell.

NR Cell ID NRCell. NrCellId N/A Cell Name NRCell.CellName N/A Frequency Band NRCell.FrequencyBand N/A

Cell ID NRCell.CellId N/A

Duplex Mode NRCell. DuplexMode Set this parameter to CELL_TDD. User Label NRCell.UserLabel N/A

The following table describes the parameters that must be set in an NRDUCell MO to configure an NR DU cell.

NR DU Cell ID NRDUCell. NrDuCellId N/A NR DU Cell Name NRDUCell. NrDuCellNa

me

N/A

Frequency Band NRDUCell.FrequencyB and

N/A

Uplink Bandwidth NRDUCell.UlBandWidt h N/A Downlink Bandwidth NRDUCell. DlBandWidt h N/A

Duplex Mode NRDUCell. DuplexMode Set this parameter to CELL_TDD.

(25)

Cell Radius NRDUCell.CellRadius The value of this parameter must be greater than or equal to the actual cell radius. Otherwise, UEs at the cell edge may fail to access the network.

Slot Assignment NRDUCell. SlotAssignm ent

This parameter needs to be set only for TDD cells.

Slot Structure NRDUCell. SlotStructure This parameter needs to be set only for TDD cells.

Cell ID NRDUCell.CellId N/A

Uplink NARFCN NRDUCell.UlNarfcn N/A Downlink NARFCN NRDUCell. DlNarfcn N/A Physical Cell ID NRDUCell. PhysicalCellI

d

For two NR DU cells with overlapped parts, if the uplink frequencies or

downlink frequencies of the two cells are the same, to avoid mutual

interference between the two cells, the

NRDUCell. PhysicalCellId settings of the two cells must be different.

Subcarrier Spacing NRDUCell. SubcarrierSp acing

N/A

Cyclic Prefix Length NRDUCell.CyclicPrefix Length N/A Uplink NARFCN Configuration Indicator NRDUCell.UlNarfcnCo nfigInd N/A

Tracking Area ID NRDUCell.TrackingAre aId

This parameter must be set to the same value as the Tracking Area ID

parameter in thegNBTrackingArea

MO. SSB Frequency Position Describe Method NRDUCell. SsbDescMet hod

Set this parameter based on the network plan.

SSB Frequency Position

NRDUCell. SsbFreqPos Set this parameter based on the

network plana.

a: The requirements for configuring NRDUCell. SsbFreqPos are as follows:

l If NRDUCell.FrequencyBand is set to n3 or n28 and NRDUCell. DlBandwidth is set to

15 MHz, NRDUCell. SsbFreqPos must be set to the value of NRDUCell. DlNarfcn

minus 18. IfNRDUCell.FrequencyBand is set to n41 and NRDUCell. DlBandwidth is

(26)

set to 20 MHz, 50 MHz, 70 MHz, 80 MHz, 90 MHz, or 100 MHz,

NRDUCell. SsbFreqPos must be set to the value ofNRDUCell. DlNarfcn minus 36.

l If NRDUCell.FrequencyBand is set to n77, n78, or n79, and NRDUCell. DlBandwidth

is set to 20 MHz, 50 MHz, 70 MHz, 80 MHz, 90 MHz, or 100 MHz,

NRDUCell. SsbFreqPos must be set to the value ofNRDUCell. DlNarfcn minus 12.

l If NRDUCell.FrequencyBand is set to n3 or n28 and NRDUCell. DlBandwidth is not

set to 15 MHz,NRDUCell. SsbFreqPos must be set to the value of

NRDUCell. DlNarfcn.

l If NRDUCell.FrequencyBand is set to n41 and NRDUCell. DlBandwidth is not set to

20 MHz, 50 MHz, 70 MHz, 80 MHz, 90 MHz, or 100 MHz, NRDUCell. SsbFreqPos

must be set to the value of NRDUCell. DlNarfcn.

l If NRDUCell.FrequencyBand is set to n77, n78, or n79, and NRDUCell. DlBandwidth

is not set to 20 MHz, 50 MHz, 70 MHz, 80 MHz, 90 MHz, or 100 MHz,

NRDUCell. SsbFreqPos must be set to the value ofNRDUCell. DlNarfcn.

l If NRDUCell.FrequencyBand is set to n257, n258, or n260, NRDUCell. SsbFreqPos

must be set to the value of NRDUCell. DlNarfcn.

The following table describes the parameters that must be set in an NRDUCellTrp MO to configure the TRP for an NR DU cell.

NR DU Cell TRP ID NRDUCellTrp. NrDuCel lTrpId

N/A

NR DU Cell ID NRDUCellTrp. NrDuCel lId N/A Transmit and Receive Mode NRDUCellTrp.TxRxMo de N/A Baseband Equipment ID NRDUCellTrp. Baseban dEqmId

If this parameter is set to 255, no baseband equipment is specified. In

this case, a TDD cell can only use baseband equipment directly

connected to the RF unit of the cell. Max Transmit Power NRDUCellTrp. MaxTran

smitPower

N/A

CPRI Compression NRDUCellTrp.CpriCom pression

N/A

The following table describes the parameters that must be set in an NRDUCellCoverage MO to configure the information about the coverage area of an NR DU cell.

NR DU Cell TRP ID NRDUCellCoverage. Nr DuCellTrpId

N/A

(27)

Parameter Name Parameter ID Setting Notes NR DU Cell Coverage ID NRDUCellCoverage. Nr DuCellCoverageId N/A

Sector Equipment ID NRDUCellCoverage. Sec torEqmId

N/A

The following table describes the parameters that must be set in a BaseBandEqm MO to configure baseband equipment information.

Baseband Equipment ID

BASEBANDEQM. BAS

EBANDEQMID

EachBASEBANDEQMID parameter

value identifies a piece of baseband equipment.

One piece of baseband equipment can include multiple BBPs.

A BBP cannot belong to multiple pieces of baseband equipment. Baseband Equipment Type BASEBANDEQM. BAS EBANDEQMTYPE N/A Baseband Equipment Board BASEBANDEQM. BAS EBANDEQMBOARD N/A UMTS UL Demodulation Mode BASEBANDEQM.UMT SDEMMODE

It is recommended that this parameter be set toNULL because it is not used

for gNodeBs.

The following table describes the parameters that must be set in an NRDUCellPrach MO to configure the information about Logical Root Sequence Index.

NR DU Cell ID NRDUCellPrach. NrDu CellId -Logical Root Sequence Index NRDUCellPrach. RootS equenceIndex

Set this parameter based on the network plana.

a: The requirements for configuring NRDUCellPrach. RootSequenceIndex are as follows: l When the system frequency is sub-6 GHz and the duplex mode is SUL, set the parameter

to a value in the range of 0 to 837.

When the system frequency is on sub-6 GHz, the duplex mode is TDD, the

(28)

and the PRACH configuration index is 0 to 7, 12, 16, or 65535, set the parameter to a value in the range of 0 to 837.

If two neighboring cells with the same value range of the

NRDUCellPrach. RootSequenceIndex parameter and overlapping time and frequency

resources have this parameter set to M and N , respectively, [M, M + x _– 1] and [N, N + x– 1] must not overlap. The value of x depends on the cell radius.

– If the cell radius is 0 to 0.5 km, x is 1. – If the cell radius is 0.5 km to 2.5 km, x is 2. – If the cell radius is 2.5 km to 4 km, x is 3. – If the cell radius is 4 km to 5.5 km, x is 4. – If the cell radius is 5.5 km to 7 km, x is 5. – If the cell radius is 7.5 km to 9.5 km, x is 6. – If the cell radius is 9.5 km to 12 km, x is 8. – If the cell radius is 12 km to 14.5 km, x is 10.

l When the system frequency is sub-6 GHz, the duplex mode is TDD, the uplink-downlink slot configuration is 4_1_DDDSU, and the subcarrier spacing is 30 kHz, set the

parameter to a value in the range of 0 to 137.

When the system frequency is sub-6 GHz, the duplex mode is TDD, the uplink-downlink slot configuration is 8_2_DDDDDDDSUU, the subcarrier spacing is 30 kHz, and the PRACH configuration index is 245 or 255, set the parameter to a value in the range of 0 to 137.

If two neighboring cells with the same value range of

theNRDUCellPrach. RootSequenceIndex parameter and overlapping time and

frequency resources have this parameter set to M and N , respectively, [M, M + x – 1] and [N, N + x – 1] must not overlap. The value of x depends on the cell radius.

– If the cell radius is 0 to 0.5 km, x is 6. – If the cell radius is 0.5 km to 1 km, x is 10. – If the cell radius is 1 km to 1.5 km, x is 13. – If the cell radius is 1.5 km to 2 km, x is 16. – If the cell radius is 2 km to 3 km, x is 22. – If the cell radius is 3 km to 4.5 km, x is 32. – If the cell radius is 4.5 km to 14.5 km, x is 64.

– When the system frequency is on mmWave, set the parameter to a value in the range of 0 to 137.

l If two neighboring cells with the same value range of the

NRDUCellPrach. RootSequenceIndex parameter and overlapping time and frequency

resources have this parameter set to M and N , respectively, [M, M + x – 1] and [N, N + x– 1] must not overlap. The value of x depends on the cell radius.

– If the cell radius is 0 to 0.5 km, x is 16. – If the cell radius is 0.5 km to 1 km, x is 32. – If the cell radius is 1 km to 14.5 km, x is 64.

3.4.1.2 Using MML Commands

This section provides the MML command examples in different scenarios.

(29)

l Scenario 1: Establishing a Common Cell

l Scenario 2: Establishing a Multi-Carrier Cell

l Scenario 3: Establishing Uplink and Downlink Decoupling Cells

l Scenario 4: Establishing a LampSite RF Combination Cell

This section provides examples of MML commands for setting up a cell. Parameter values in the following examples are for reference only. On live networks, these parameters must be configured based on the operator's network plan.

LampSite base stations support only scenario 1 and scenario 4.

Process

Figure 3-7 Cell deployment process

For details about how to configure device data, see 3900 & 5900 Series Base Station Initial Configuration Guide in 3900 & 5900 Series Base Station Product Documentation.

Scenario 1: Establishing a Common Cell

To establish a common cell, perform the common process shown in Figure 3-7 with necessary adjustment. The common process is as follows:

(30)

NOTE

l The antenna transmit/receive mode must match the number of antennas in a sector. Accordingly, the sector serving the cell must be configured with the required number of antennas (specified by the SECTOR. ANTNUM parameter). For example, if a cell works in 8T8R mode, the

SECTOR. ANTNUM parameter must be set to 8.

l If the SECTOR.CREATESECTOREQM parameter under ADD SECTOR is set to TRUE, there is no need to run the ADD SECTOREQM command. The SECTOR.CREATESECTOREQM parameter is set to FALSE by default.

Establishing a 100 MHz 8T8R TDD cell

//(Optional) Adding sectors and sector equipment, setting the SECTOR . ANTNUM

parameter to 8, and configuring eight antenna channels of an RRU for this sector when an RRU is added

ADD SECTOR: SECTORID=0, SECNAME="0", USERLABEL="0", ANTNUM=8, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, ANT5CN=0, ANT5SRN=60, ANT5SN=0, ANT5N=R0E, ANT6CN=0, ANT6SRN=60, ANT6SN=0, ANT6N=R0F, ANT7CN=0, ANT7SRN=60, ANT7SN=0, ANT7N=R0G, ANT8CN=0, ANT8SRN=60, ANT8SN=0, ANT8N=R0H, CREATESECTOREQM=TRUE, SECTOREQMID=0; //(Optional) Adding baseband equipment

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=0; //(Optional) Adding operator and tracking area information (if not added before) //(Optional) Adding an operator

ADD GNBOPERATOR: OperatorId=0, OperatorName="CMCC", Mcc="460", Mnc="00"; //(Optional) Adding a tracking area for the operator

ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1; //Adding a 100 MHz TDD cell

ADD NRCELL: NrCellId=0, CellName="CELL1", CellId=1, FrequencyBand=N78, DuplexMode=CELL_TDD;

//Adding a TDD DU cell

ADD NRDUCELL: NrDuCellId=0, NrDuCellName="DUCELL1", DuplexMode=CELL_TDD, CellId=1, PhysicalCellId=1, FrequencyBand=N78, UlNarfcnConfigInd=NOT_CONFIG, DlNarfcn=634000, UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M,

SlotAssignment=4_1_DDDSU, SlotStructure=SS2, TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=633988;

//Adding a TRP for an NR DU cell, and optionally binding baseband equipment to the TRP

ADD NRDUCELLTRP: NrDuCellTrpId=0, NrDuCellId=0, TxRxMode=8T8R,

MaxTransmitPower=320, BasebandEqmId=0, CpriCompression=3DOT2_COMPRESSION;

//Adding an NR DU cell coverage area, and binding sector equipment to the TRP of the NR DU cell

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=0; //Activating the cell

ACT NRCELL: NrCellId=0;

Establishing a 100 MHz 64T64R massive MIMO TDD cell

//(Optional) Adding sectors and sector equipment in scenarios where AAUs are added, with the SECTOR . ANTNUM parameter set to 0

//(Optional) Adding a sector

ADD SECTOR: SECTORID=0, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=0, CREATESECTOREQM=FALSE;

//(Optional) Adding sector equipment

ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=60, RRUSN=0, BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None; //(Optional) Adding baseband equipment

ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1; //Adding a 100 MHz TDD cell

ADD NRCELL: NrCellId=0, CellName="CELL1", CellId=1, FrequencyBand=N78, DuplexMode=CELL_TDD, UserLabel="CELL1";

//Adding an NR DU cell

ADD NRDUCELL: NrDuCellId=1, NrDuCellName="CELL1", DuplexMode=CELL_TDD, CellId=1,PhysicalCellId=1, FrequencyBand=N78, UlNarfcnConfigInd=NOT_CONFIG,

(31)

DlNarfcn=634000, UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M, SlotAssignment=4_1_DDDSU, SlotStructure=SS2, TrackingAreaId=0,

SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=633988;

ADD NRDUCELLTRP: NrDuCellTrpId=0, NrDuCellId=1, TxRxMode=64T64R, MaxTransmitPower=300, CpriCompression=3DOT2_COMPRESSION;

Establishing a LampSite 100 MHz 4T4R TDD cell

//(Optional) Adding sectors and sector equipment, setting the SECTOR . ANTNUM

parameter to 4, and configuring four antenna channels of a pRRU for this sector when a pRRU is added

ADD SECTOR: SECTORID=0, SECNAME="0", USERLABEL="0", ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=0;

//(Optional) Adding baseband equipment

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=0; //(Optional) Adding operator and tracking area information (if not added before) //(Optional) Adding an operator and configuring NR networking as SA or NSA

ADD GNBOPERATOR: OperatorId=0, OperatorName="CMCC", Mcc="460", Mnc="00", OperatorType=PRIMARY_OPERATOR, NrNetworkingOption=SA;

//(Optional) Adding a tracking area for the operator ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1;

//Adding a 100 MHz TDD cell

SlotAssignment=4_1_DDDSU, SlotStructure=SS2, LampSiteCellFlag=YES,

TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=636654;

ADD NRDUCELLTRP: NrDuCellTrpId=0, NrDuCellId=0, TxRxMode=4T4R, BasebandEqmId=0, MaxTransmitPower=240, CpriCompression=3DOT2_COMPRESSION;

Scenario 2: Establishing a Multi-Carrier Cell

Establishing cells in a two-carrier scenario is used as an example

l Signals of other carriers will be interrupted intermittently when a carrier is added to or removed from a multi-carrier RRU. Therefore, you are advised to add or remove a carrier in off-peak hours.

l Before establishing multi-carrier cells, ensure that the multi-carrier capabilities supported by RRUs and CPRI ports and the BBP's cell specifications meet the requirements

described in3.3.3 Hardware.

(32)

ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=0;

ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1;

//Establishing cell 1, ensuring that the frequency bands of the two cells do not overlap

//Adding an NR DU cell for cell 1

ADD NRDUCELL: NrDuCellId=0, NrDuCellName="DUCELL1", CellId=1, PhysicalCellId=0, FrequencyBand=N77, DlNarfcn=623000, UlBandwidth=CELL_BW_40M,

DlBandwidth=CELL_BW_40M, DuplexMode=CELL_TDD, TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=623000;

//Adding a TRP for cell 1's NR DU cell, and optionally binding baseband equipment to the TRP

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=0; //Establishing cell 2, ensuring that the frequency bands of the two cells do not overlap

ADD NRCELL: NrCellId=1, CellName="CELL2", CellId=2, FrequencyBand=n41, DuplexMode=CELL_TDD;

//Adding an NR DU cell for cell 2

ADD NRDUCELL: NrDuCellId=1, NrDuCellName="DUCELL2", CellId=2, PhysicalCellId=0, FrequencyBand=N77, DlNarfcn=625666, UlBandwidth=CELL_BW_40M,

DlBandwidth=CELL_BW_40M, DuplexMode=CELL_TDD, TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=625666;

//Adding a TRP for cell 2's NR DU cell, and optionally binding baseband equipment to the TRP (the settings of NRDUCellCoverage.SectorEqmId are the same for these cells.)

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=0, SectorEqmId=0; //Activating the two cells

ACT NRCELL: NrCellId=0; ACT NRCELL: NrCellId=1;

Scenario 3: Establishing Uplink and Downlink Decoupling Cells

Uplink and downlink decoupling cells correspond to one NR cell and two NR DU cells.

//For TDD cells

//(Optional) Adding a sector and sector equipment when an RRU is added

ADD SECTOR: SECTORID=0, SECNAME="0", LOCATIONNAME="0", USERLABEL="0", ANTNUM=0, CREATESECTOREQM=FALSE;

//(Optional) Adding sector equipment

ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=60, RRUSN=0, BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None; //(Optional) Adding baseband equipment

ADD GNBOPERATOR: OperatorId=0, OperatorName="CMCC", Mcc="460", Mnc="00";

(33)

//(Optional) Adding a tracking area for the operator ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1;

//Adding a 100 MHz TDD cell

ADD NRCELL: NrCellId=0, CellName="CELL1", CellId=1, FrequencyBand=N78, DuplexMode=CELL_TDD, UserLabel="CELL1";

//Adding an NR DU cell

ADD NRDUCELL: NrDuCellId=1, NrDuCellName="CELL1", DuplexMode=CELL_TDD, CellId=1, PhysicalCellId=1, FrequencyBand=N78, UlNarfcnConfigInd=NOT_CONFIG,

DlNarfcn=634000, UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M, SlotAssignment=4_1_DDDSU, SlotStructure=SS2, TrackingAreaId=0,

SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=633988;

ADD NRDUCELLTRP: NrDUCellTrpId=0, NrDuCellId=1, TxRxMode=64T64R, BasebandEqmId=0, MaxTransmitPower=300, CpriCompression=3DOT2_COMPRESSION;

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=0; //For SUL cells

//(Optional) Adding a sector when an RRU is added

ADD SECTOR: SECTORID=1, SECNAME="1", USERLABEL="1", ANTNUM=4, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=61, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=FALSE;

//(Optional) Adding sector equipment when an RRU is added

ADD SECTOREQM: SECTOREQMID=1, SECTORID=1, ANTCFGMODE=ANTENNAPORT, ANTNUM=4, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANTTYPE1=RX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B, ANTTYPE2=RX_MODE, ANT3CN=0, ANT3SRN=61,

ANT3SN=0, ANT3N=R0C, ANTTYPE3=RX_MODE, ANT4CN=0, ANT4SRN=61, ANT4SN=0, ANT4N=R0D, ANTTYPE4=RX_MODE;

//Adding an SUL DU cell

ADD NRDUCELL: NrDuCellId=2, NrDuCellName="SUL", DuplexMode=CELL_SUL, FrequencyBand=N80, UlNarfcnConfigInd=CONFIG, UlNarfcn=350000,

UlBandwidth=CELL_BW_20M;

ADD NRDUCELLTRP: NrDuCellTrpId=1, NrDuCellId=2, TxRxMode=4R, BasebandEqmId=0, CpriCompression=NO_COMPRESSION;

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=0, SectorEqmId=1; //Adding an SUL carrier for an NR DU cell

ADD NRDUCELLSUL: NrDuCellId=1, SulNrDuCellId=2; //Setting UL and DL Decoupling Switch to On

MOD NRDUCELLALGOSWITCH: NrDuCellId=1, UlDlDecouplingSwitch=ON; //Configuring the logical root sequence index of the PRACH MOD NRDUCellPrach: NrDuCellId=1, RootSequenceIndex=80; MOD NRDUCellPrach: NrDuCellId=2, RootSequenceIndex=82; //Activating the cell

ACT NRCELL: NrCellId=0; //Redeploying the NR DU cell

STR NRDUCELLREDEPLOY: NrDuCellId=1;

Scenario 4: Establishing a LampSite RF Combination Cell

Establishing a LampSite 100 MHz 4T4R TDD RF combination cell

// (Optional) Adding sectors and sector equipment, setting the SECTOR . ANTNUM

parameter to 4, and configuring four antenna channels of a pRRU for this sector when a pRRU is added (an RF combination cell requires multiple sectors and sector equipment.)

ADD SECTOR: SECTORID=0, SECNAME="0", USERLABEL="0", ANTNUM=4, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=0;

ADD SECTOR: SECTORID=1, SECNAME="1", USERLABEL="1", ANTNUM=4, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B,

(34)

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=0; //(Optional) Adding operator and tracking area information (if not added before) //Adding an operator and configuring NR networking as SA or NSA

ADD GNBOPERATOR: OperatorId=0, OperatorName="CMCC", Mcc="460", Mnc="00", OperatorType=PRIMARY_OPERATOR, NrNetworkingOption=SA;

//Adding a tracking area for the operator ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=1; //Adding a 100 MHz TDD cell

SlotAssignment=4_1_DDDSU, SlotStructure=SS2, LampSiteCellFlag=YES,

TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=636654;

//Adding an NR DU cell coverage area, and binding sector equipment to the TRP of the NR DU cell (an RF combination cell requires multiple NR DU cell coverage areas, with each bound to one piece of sector equipment.)

ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=0; ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=1, SectorEqmId=1; //Activating the cell

Deactivation Command Examples

//Deactivating a cell DEA NRCELL: NrCellId=0;

3.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.

3.4.2 Activation Observation

Step 1 Run the DSP NRCELL command to check the cell status.

If the value of Cell Availability State in the command output isAvailable, the cell has been successfully set up.

Step 2 Use a UE to access this cell. If the UE successfully accesses the cell, the cell is working properly.

----End

(35)

4

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Cell Management(5G RAN2.1_Draft a)

5G RAN

5G RAN

Cell Management Feature Parameter

Cell Management Feature Parameter

Description

Description

Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Contents

Contents

1 Change

1 Change

History...

History...

...

...

...

...

...

...

...

.

1

1

2 General

2 General

Statements...

Statements...

...

...

...

...

...

...

3

3

3 Cell Ma

3 Cell Management...

nagement...

...

...

...

...

...

...5

..5

4 Glossary...30

5 Reference Documents...31

1

Change History

1.1 5G RAN2.1 Draft A (2018-12-30)

Technical Changes

Editorial Changes

2

General Statements

Purpose

Software Interfaces

Trial Features

3

Cell Management

3.1 Principles

3.1.1 Definition

3.1.2 Related Concepts

3.1.2.1 Cell

3.1.2.2 Sector

3.1.2.3 Sector Equipment

3.1.2.4 RF Equipment

3.1.2.5 Baseband Equipment

3.1.2.6 NR DU Cell TRP

3.1.2.7 NR DU Cell Coverage Area

3.1.3 Typical Scenarios

3.1.3.1 Common Cell

3.1.3.2 Combined-RRU Cell

3.1.3.3 Cells in Multi-Carrier Sectors

3.1.3.4 Uplink and Downlink Decoupling Cells

3.1.3.5 RF Combination Cell

3.1.4 Cell-related Parameters

3.1.4.1 Frequency Band

3.1.4.2 NARFCN