9 - LTE NB-IoT V100R015C10 Data Configuration

LTE NB-IoT V100R015C10 Data Configuration
Confidential Information of Huawei. No Spreading Without Permission



 LTE guard band deployment

 To prevent inter-carrier or inter-RAT interference, the existing communication
technologies reserve guard bands in addition to valid bands. Generally, an
inter-carrier guard band has a bandwidth of 180 kHz or higher. NB-IoT is a
narrowband communication technology in which a bandwidth of 180 kHz is
allocated to both the uplink and downlink. Therefore, services can be deployed
on the guard bands of existing RATs, which eliminates the need for new
spectrum and improves the utilization of old spectrum.
 LTE in-band deployment utilizes RBs within an LTE FDD band for NB-IoT.

 There are two options for standalone deployment: refarming an existing RAT's
spectrum and using idle spectrum.
 Refarming: The spectrum of an existing RAT can be refarmed for NB-IoT,
without affecting the functionality of that RAT. Generally, the GSM spectrum
can be refarmed for NB-IoT. During deployment, a guard band needs to be
reserved between NB-IoT and GSM. The GSM network is then replanned to
minimize the impact of the refarming on GSM services.
 Using idle spectrum: Operators may have some nonstandard spectrum
resources that do not meet the requirements of existing RATs. These
resources can be utilized by NB-IoT. To protect the existing RATs from being
affected, sufficient guard bands must be reserved between NB-IoT and the
RATs.

 LTE guard band deployment

To prevent inter-carrier or inter-RAT interference, the existing communication
technologies reserve guard bands in addition to valid bands. Generally, an inter-
carrier guard band has a bandwidth of 180 kHz or higher. NB-IoT is a
narrowband communication technology in which a bandwidth of 180 kHz is
allocated to both the uplink and downlink. Therefore, services can be deployed
on the guard bands of existing RATs, which eliminates the need for new
spectrum and improves the utilization of old spectrum.

 In LTE in-band deployment, NB-IoT is deployed using resource blocks (RBs) within
an existing LTE FDD band.
 Uplink positions recommended for NB-IoT are edge RBs. If the PUCCH is
dynamically configured, the first or last RB can be used for NB-IoT. If an edge RB has
been occupied by the LTE FDD PRACH or static PUCCH, it cannot be used for NB-
IoT.
 Downlink RB positions available and recommended for NB-IoT are listed in the
following table.
LTE FDD Cell Available Downlink RB Positions for Recommended Downlink RB

Bandwidth NB-IoT Positions for NB-IoT
5 MHz 2, 7, 17, 22 7, 17
10 MHz 4, 9, 14, 19, 30, 35, 40, 45 19, 30
2, 7, 12, 17, 22, 27, 32, 42, 47, 52,
15 MHz 32, 42
57, 62, 67, 72
4, 9, 14, 19, 24, 29, 34, 39, 44, 55,
20 MHz 44, 55
60, 65, 70, 75, 80, 85, 90, 95


 A new S1 interface must be set up for NB-IoT. Two SCTP links can be configured,
one for LTE and the other for NB-IoT.

 A new S1 interface can be set up for NB-IoT, or the existing FDD/TDD S1 interface
can be used for NB-IoT.
 Two SCTP links can be configured, one for FDD and the other for NB-IoT.
Alternatively, one SCTP link is shared by NB-IoT and FDD/TDD.




 ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33,

NbIotTaFlag=BOOLEAN_TRUE;
 This parameter indicates whether the current tracking area identity (TAI) applies only
to NB-IoT. If this parameter is set to BOOLEAN_TRUE, the current TAI applies only to
NB-IoT. If this parameter is set to BOOLEAN_FALSE, the current TAI does not apply
to NB-IoT. Do not set the NB-IoT TAI to the same value as an FDD/TDD TAI because
NB-IoT does not support inter-RAT mobility according to 3GPP specifications.


• Note:
• When configuring an LBBP, set the Work Mode parameter based on the actual
application scenario.
• When configuring a UBBP, set the Base Band Work Standard parameter to
LTE_FDD or LTE_TDD.

 ADD BRD: SN=3, BT=UBBP, BBWS=NBIOT-1;

 ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=MO,
RXNUM=2, TXNUM=2, MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF,
RFTXSIGNDETECTSW=OFF;


 In the SET GTRANSPARA command, when TRANSCFGMODE is set to OLD, the old
transmission configuration model is used. When this parameter is set to NEW, the
new transmission configuration model is used.
 In the new transmission model, the binding relationship between the transport layer
and the device model is decoupled. That is, transmission parameters are no longer
associated with physical boards or ports. When planning transmission configuration
data in the new model, you do not need to pay attention to the physical information
about boards.
 In the new model, an INTERFACE MO is added at the data link layer to isolate the
upper layers from the physical layer. The new model simplifies operations in
scenarios such as changing transmission boards and changing transmission ports.
 In the new model, the IPv4 and IPv6 models are normalized, and the IPv4 and IPv6
configuration objects above the IP layer are combined, which facilitates the extension
of new transmission functions and reduces transmission configuration parameters.



华为技术有限公司版权所有未经许可不得扩散

 The endpoint mode has a complete configuration procedure and a simplified

configuration procedure. For details, see the configuration guide.
 In CP mode, user plane information such as IP path does not need to be configured
generally. It can be configured if required.

 NB-IoT supports only S1 and X2-C (control plane) interfaces. It does not support X2-U
(user plane) interfaces.

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1INTERFACE_CFG,

S1InterfaceId=0, NbCiotEpsOptCap=CP_UP, NbLteSupportCap=SUPPORT;

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1_CFG,

NbCiotEpsOptCap=CP_UP, NbLteSupportCap=SUPPORT;


 If you need to specify BBPs for cells, run the ADD BASEBANDEQM command to add
baseband equipment.

 ADD CELL: LocalCellId=0, CellName="NBIOT", NbCellFlag=TRUE,

CoverageLevelType=COVERAGE_LEVEL_0-1, CellId=0, PhyCellId=0,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE,
HighSpeedFlag=LOW_SPEED, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;

 ADD PRB: LocalCellId=0, PrbId=0, DeployMode=STAND_ALONE,

WorkMode=UL_DL, FreqBand=8, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3550,
DlFreqOffset=NEG_0DOT5, AnchorCarrierFlag=TRUE;

 ADD EUPRBSECTOREQM: LocalCellId=0, PrbId=0, SectorEqmId=0;

 Which common device data needs to be configured?

 Common device data includes cabinet data, BBP data, RF unit data, time data,
and clock data.



 If LTE FDD and NB-IoT share the same EPC and S1 interface, NB-IoT cell
deployment in standalone mode is similar to FDD cell deployment. The main
difference lies in RAT.



 ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=LM,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF,

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1_CFG, S1Id=0,

NbCiotEpsOptCap=CP, NbLteSupportCap=SUPPORT;
 Set MME capability information, enabling the MME to support both NB-IoT and LTE
and support control plane CIoT EPS optimization.


 What are the differences in co-EPC co-S1 standalone cell deployment?

 Set different TACs for FDD and NB-IoT cells.
 Set the work mode of an RRU to LM if the RRU is shared.
 Enable the MME to support LTE.
 Configure the S1 interface user plane.






 ADD CELL: LocalCellId=1, CellName="NB-IOT INBAND", NbCellFlag=TRUE,

MultiRruCellFlag=BOOLEAN_FALSE;



 ADD CELLRBRESERVE: LocalCellId=0, Index=0, RbRsvMode=NB_RESERVED,

RbRsvType=DOWNLINK_MODE, RbRsvStartIndex=4, RbRsvEndIndex=4;
 ADD CELLRBRESERVE: LocalCellId=0, Index=1, RbRsvMode=NB_RESERVED,
RbRsvType=UPLINK_MODE, RbRsvStartIndex=4, RbRsvEndIndex=4;
 The value NB_RESERVED indicates that the RB is not used to deploy NB-IoT. In the
uplink, it is mainly used as a guard band; in the downlink, it is punctured to reduce the
interference with the NB-IoT cell. The value NB_DEPLOYMENT indicates that the RB
is used to deploy NB-IoT.
 When the cell bandwidth is 3 MHz, the parameter value range is 0 to 14.
 When the cell bandwidth is 5 MHz, the parameter value range is 0 to 24. When the
RbRsvMode parameter is set to NB_DEPLOYMENT and the RbRsvType parameter
is set to DOWNLINK_MODE, this parameter must be set to 2, 7, 17, or 22.
is set to DOWNLINK_MODE, this parameter must be set to 4, 9, 14, 19, 30, 35, 40, or
45.

is set to DOWNLINK_MODE, this parameter must be set to 2, 7, 12, 17, 22, 27, 32, 42,
47, 52, 57, 62, 67, or 72.
is set to DOWNLINK_MODE, this parameter must be set to 4, 9, 14, 19, 24, 29, 34, 39,
44, 55, 60, 65, 70, 75, 80, 85, 90, or 95.

 ADD PRB: LocalCellId=1, PrbId=1, DeployMode=IN_BAND, WorkMode=UL_DL,

FreqBand=8, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3563, DlFreqOffset=NEG_1,
LteCellId=0, AnchorCarrierFlag=TRUE;


 What precautions should be taken when adding MME capability information?

 The MME Support LTE Capability parameter specifies whether the MME
supports NB-IoT and LTE. If NbCiotEpsOptCap is set to CP and
NbLteSupportCap is set to SUPPORT, the MME supports both NB-IoT and
LTE. The setting of NbLteSupportCap will affect LTE services.






 ADD CELL: LocalCellId=1, CellName="NB-IOT", NbCellFlag=TRUE,




 ADD PRB: LocalCellId=1, PrbId=1, DeployMode=GUARD_BAND,

DlFreqOffset=NEG_1, LteBandWidth=LTE_SYSTEM_BW_10M, LteDlEarfcn=3700,
AnchorCarrierFlag=TRUE;


 What are the NB-IoT deployment modes?

 There are three NB-IoT deployment modes, which are specified by the
DeployMode parameter. The value STAND_ALONE indicates that out-of-
band LTE spectrum resources are used to deploy NB-IoT PRBs. The value
GUARD_BAND indicates that NB-IoT PRBs are deployed on the LTE guard
band. The value IN_BAND indicates that PRBs are deployed on the LTE RB
resources, which means that less RBs are available for LTE. This parameter
applies only to NB-IoT.







 ADD CELL: LocalCellId=1, CellName="NB-IOT", NbCellFlag=TRUE,


 ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0,

UpEpGroupId=0;


NbCiotEpsOptCap=CP, NbLteSupportCap=NOT_SUPPORT;

 ADD PRB: LocalCellId=1, PrbId=1, DeployMode=GUARD_BAND,

DlFreqOffset=POS_0, LteBandWidth=LTE_SYSTEM_BW_10M, LteDlEarfcn=3700,
AnchorCarrierFlag=TRUE;


 What are the differences in co-operator separate-EPC separate-S1 standalone cell

deployment?
 For details, see the previous descriptions in this document.


 LTE bandwidths include 10 MHz, 20 MHz, and others. For the 10 MHz bandwidth,
only 9 MHz is used while 0.5 MHz is reserved for protection at each of channel edges.
There is a DC subcarrier in the center of LTE. It has a bandwidth of 15 kHz, with 7.5
kHz on each side.

 NB-IoT requires that a center frequency should be an integer multiple of 100 kHz.

 FDL_low: lowest frequency of the downlink band

 NOffs-DL: downlink EARFCN start offset
 NDL: NB-IoT downlink EARFCN
 MDL: NB-IoT downlink frequency offset
 FUL_low: lowest frequency of uplink band
 NOffs-UL: uplink EARFCN start offset
 NUL: NB-IoT uplink EARFCN
 MUL: NB-IoT uplink frequency offset



9 - LTE NB-IoT V100R015C10 Data Configuration

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

9 - LTE NB-IoT V100R015C10 Data Configuration

Încărcat de

Drepturi de autor:

Formate disponibile

LTE NB-IoT V100R015C10 Data Configuration

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 LTE guard band deployment

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 LTE guard band deployment

Confidential Information of Huawei. No Spreading Without Permission

LTE FDD Cell Available Downlink RB Positions for Recommended Downlink RB

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD BRD: SN=3, BT=UBBP, BBWS=NBIOT-1;

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

华为技术有限公司 版权所有 未经许可不得扩散

 The endpoint mode has a complete configuration procedure and a simplified

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1INTERFACE_CFG,

Confidential Information of Huawei. No Spreading Without Permission

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1_CFG,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD CELL: LocalCellId=0, CellName="NBIOT", NbCellFlag=TRUE,

Confidential Information of Huawei. No Spreading Without Permission

 ADD PRB: LocalCellId=0, PrbId=0, DeployMode=STAND_ALONE,

Confidential Information of Huawei. No Spreading Without Permission

 ADD EUPRBSECTOREQM: LocalCellId=0, PrbId=0, SectorEqmId=0;

Confidential Information of Huawei. No Spreading Without Permission

 Which common device data needs to be configured?

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1_CFG, S1Id=0,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 What are the differences in co-EPC co-S1 standalone cell deployment?

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33,

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 ADD CELL: LocalCellId=1, CellName="NB-IOT INBAND", NbCellFlag=TRUE,

华为技术有限公司版权所有未经许可不得扩散