You are on page 1of 18

04/21/17 Security Level: INTERNAL

NB-IoT Network Design


Technical Training
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential


Transmission Differences Between NB-IoT and
FDD Networks
1. NB-IoT networks support only the S1-C interface when deploying only Control plane CIoT EPS optimisation. As NB-IoT networks do not support the S1-U, X2, eX2, and
eCoordinator interfaces, and therefore do not support the transmission over these interfaces, such as IPPM.
2. Transmission-related features and functions supported on NB-IoT networks are the same as those supported on FDD networks, such as active and backup route, and BFD.
3. In a co-MPT scenario, the OM channel must be shared, and OM channel configurations do not need to be modified.
In the following slides, transmission-related configurations in new NB-IoT network deployment scenarios and FDD/TDD-to-FDD/TDD+NB-IoT evolution scenarios are separately
described.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2


New NB-IoT Network Deployment Scenario
When an new NB-IoT base station is deployed , or a GU base station is evolved to support NB-IoT
service, the NB-IoT EPC must also be deployed.

Abis/Iub link
BTS/NodeB BSC/RNC

NB-IoT SCTP link


eNodeB (NB-IoT)
NB-IoT EPC

1. In a new NB-IoT base station deployment, port planning, VLAN, IP addresses, SCTP planning,
and QoS planning are the same as those in an FDD base station.
2. In a NB-IoT and GU co-BBU or co-MPT scenario, either co-transmission or separate-
transmission is supported, and co-transmission planning is the same as that in an FDD
scenario.
3. The NB-IoT capability of the MME needs to be configured. The S1-flex feature should be
enabled if required.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3


S1 Configuration in New NB-IoT EPC Deployment
Model 1: One NB-IoT MME is Model 2: Multiple NB-IoT MMEs
configured on an S1 object. are configured on an S1 object.

NB-IoT MME NB-IoT MME NB-IoT MME NB-IoT MME


... ...

S1 Interface S1 Interface S1 Interface S1 Interface


...
...
Configuration
S1 model 1 Configuration
S1 S1
model 2

eNodeB eNodeB

S1 Configuration
Model NB-IoT Capability Configuration Operator Configuration S1-flex Suggestion
Mode
One MME is 1. In eRAN12.01, NB-IoT networks
1 configured on an 1. The NB-IoT capability can be configured on
do not support RAN Sharing, Recommended
S1 object. the S1 object. The NB-IoT capability must
and only the primary operator If multiple NB-IoT
be same for all MMEs under this S1 object.
can be configured for the S1 MMEs need to be
2. 2. The NB-IoT capability can be
object or S1 interface. connected to an
Multiple MMEs independently configured for an MME on
2. New TAIs (PLMNs+TACs) must eNodeB, the license
are configured on the S1 interface. (The configured capability
2 be planned for NB-IoT networks, for S1-flex is required Recommended
an S1 object. can be different from capability configured
and these TAIs should be for NB-IoT.
on the S1 object it belongs to and is
different from TAIs planned FDD
preferentially used by a base station.)
or TDD networks.

Note: MMEs support different NB-IoT capabilities, such as CP Only, CP+UP, CP+FDD/TDD, and CP+UP+FDD/TDD. It is
recommended that MMEs with the same NB-IoT capability are configured on the same S1 object.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4


S1 Configuration in New NB-IoT EPC Deployment
S1-C: EP mode
Manually configuring ADD CNOPERATOR: CnOperatorId=0, CnOperatorName=CMCC",
SCTPPEER CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc=00";
/* Adding a TAI for NB-IoT */
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=18888
NbIotTaFlag=BOOLEAN_TRUE;
ADD EPGROUP: EPGROUPID=0, USERLABEL=NB-IoT S1_1";
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0,
SWITCHBACKFLAG=ENABLE;
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="
100.96.194.17 ", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN= 36412, SCTPTEMPLATEID=0,
USERLABEL=NB-IoT S1";
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="
100.75.244.6 ", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN= 36412, USERLABEL="NB-IoT
MME1";
ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag= CP_CFG,
CpEpGroupId=0, Priority=10;
/* Configuring NB-IoT capabilities depending on the S1 object (CP Only is
supported, and CP+FDD/TDD is not supported.) */
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1_CFG , S1Id=0,
NbCiotEpsOptCap=CP NbLteSupportCap= NOT_SUPPORT;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5


S1 Configuration in New NB-IoT EPC Deployment
S1-C: EP mode
Automatically configuring SCTPPEER
Step 1: Enable the DNS self-setup function, and run the STR DNS command
(DNS-based self-setup) to trigger DNS querying.
ADD EPGROUP: EPGROUPID=0, USERLABEL=NB-IoT S1_1";
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0,
SWITCHBACKFLAG=ENABLE;
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="
100.96.194.17 ", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN= 36412, SCTPTEMPLATEID=0,
USERLABEL=NB-IoT S1";
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD DNSSRV: DNSSRVID=2, IPVER=IPv4, DNSCIP4="20.2.7.37",
DNSSIP4="185.22.63.78";
MOD GLOBALPROCSWITCH: S1MMESonSwitch=S1MMESonSetupSwitch-
1&S1MMESonDeleteSwitch-1, MMEDomNameMode=Auto;
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag= CP_CFG,
CpEpGroupId=0, Priority=10;

Note: Step 2: Query GUMMEIs of all MMEs and the S1 interface ID after DNS self-
An eNodeB cannot automatically determine whether setup is complete.
an MME is an NB-IoT MME or FDD/TDD MME based DSP SERVEDGUMMEIS;
on DNS query results, and therefore cannot
automatically configure the NB-IoT capability for the
Step 3: Configure the NB-IoT capability based on the S1 interface ID (with the
MME. A self-setup S1-C link to the MME will be
automatically deleted and therefore the NB-IoT value of 1) of the NB-IoT MME.
capability of the MME is difficult to maintain. In this /* Configuring NB-IoT capabilities depending on the S1 interface (CP Only is
case, it is recommended that DNS-based self-setup supported, and CP+FDD/TDD is not supported.) */
not be used for establishing the S1-C link to the NB- ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1INTERFACE _CFG ,
IoT MME. S1InterfaceId=1, NbCiotEpsOptCap=CP, NbLteSupportCap=
NOT_SUPPORT;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6


S1 Configuration in New NB-IoT EPC Deployment

ADD SCTPLNK: SCTPNO=0, SN=7, LOCIP="100.96.194.17,


LOCPORT=36412, PEERIP="100.75.244.6, PEERPORT=36412,
S1-C: Link mode AUTOSWITCH=ENABLE, DESCRI=NB-IoT MME1";
The NB-IoT capability ADD CPBEARER: CPBEARID=0, BEARTYPE=SCTP,
is independently FLAG=MASTER;
configured for an ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0,
MME on the S1 CnOperatorId=0, Priority=255;
interface. /* Configuring NB-IoT capabilities depending on the S1 interface (CP
Only is supported, and CP+FDD/TDD is not supported.) */
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1INTERFACE
_CFG ,
S1InterfaceId=0 NbCiotEpsOptCap=CP NbLteSupportCap=
NOT_SUPPORT;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7


Evolution from FDD/TDD to FDD/TDD+NB-
IoT (Separate-EPC Deployment)
Scenario description: NB-IoT is deployed on an FDD/TDD base station, and the NB-IoT EPC and FDD/TDD EPC are separately deployed
and use different MME IP addresses.
NB-IoT requires a new S1 interface. Two SCTP links can be configured (one for FDD, and the other for NB-IoT).

FDD/TDD SCTP link


eNodeB FDD/TDD EPC
(FDD/TDD)

eNodeB (NB-IoT) NB-IoT SCTP link

NB-IoT EPC
Data planning (EP):
SCTP Link IP Address SFTP Port No. EP
NB-IoT and Two different SCTP Local ends: must be the Local ends: must be the Two different EP groups
FDD/TDD are links are used. same. same. are used. (The quantity is
deployed by the Peer ends: must be Peer ends: can be the the same as that of S1
same operator. different. same or different. objects.)

Data planning (LINK):


SCTP Link IP Address SFTP Port No.
NB-IoT and FDD/TDD Two different SCTP Local ends: can be the same Local ends: can be the same or
are deployed by the links are used. or different. different.Page 8
same operator. Peer ends: must be different. Peer ends: can be the same or different.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8


S1 Configuration in NB-IoT EPC and FDD/TDD
EPC Separate Deployment
Model 1: Setting up an S1 object Model 2: Sharing the S1 object for FDD/TDD
dedicated for NB-IoT
FDD/TDD MME NB-IoT MME
FDD/TDD MME FDD/TDD MME NB-IoT MME
...
S1Interface S1Interface
S1Interface
S1Interface S1Interface S1Interface
S1Interface
...
Configuration Configuration
S1 model 1 S1 model 2
S1

eNodeB eNodeB

S1
Configuration NB-IoT Capability
Model Operator Configuration S1-flex Suggestion
Configuration
Mode
The NB-IoT capability can be
configured depending on the S1 1. In eRAN12.01, NB-IoT networks do
Setting up an S1 not support RAN Sharing, and only
object. The same NB-IoT If multiple NB-IoT
1 object dedicated the primary operator can be Recommended
capability must be configured MMEs need to be
for NB-IoT configured for the S1 object or S1
for all MMEs under an S1 connected to an
object. interface.
eNodeB, the license for
2. New TAIs (PLMNs+TACs) must be
The NB-IoT capability can be S1-flex is required for
Sharing the S1 planned for NB-IoT networks, and
independently configured for an NB-IoT. Not
2 object for these TAIs should be different from
MME depending on the S1 TAIs planned FDD or TDD networks. recommended
FDD/TDD
interface.
Note: In the simplified EP mode, an operator is not allowed to use different S1 objects. Therefore, configuration mode
1 cannot be used.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9


S1 Configuration in NB-IoT EPC and FDD/TDD
EPC Separate Deployment
The S1 object for NB-IoT is newly set up, and the NB-IoT capability is configured for an MME
depending on the S1 object.
For details, see section "S1 Configuration in New NB-IoT EPC Deployment."

The S1 object for FDD/TDD is shared, and the NB-IoT capability is independently configured for
an MME depending on the S1 interface.
Step 1: Run the following command to add the SCTP peer for the NB-IoT MME:
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4=100.75.244.6",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36412, USERLABEL="
NB-IoT MME1"; ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;

Step 2: Run the following command to query GUMMEIs and S1 interface IDs of all MMEs and
determine the S1 interface ID of the MME supporting NB-IoT:
DSP SERVEDGUMMEIS;

Step 3: Run the following command to configure the NB-IoT capability based on the S1
interface ID (with the value of 1) of the NB-IoT MME:
/* Configuring NB-IoT capabilities depending on the S1 interface (CP Only is supported, and
CP+FDD/TDD is not supported.) */
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1INTERFACE _CFG , S1InterfaceId=1,
NbCiotEpsOptCap=CP, NbLteSupportCap= NOT_SUPPORT;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10


Evolution from FDD/TDD to FDD/TDD+NB-
IoT (Co-EPC Deployment)
Scenario description: NB-IoT is deployed on an FDD/TDD base station, and shares the same EPC with FDD/TDD using
the same MME IP address. NB-IoT reuses the S1 interface for FDD/TDD and shares the SCTP link for FDD/TDD.

FDD/TDD and NB-IoT share


an SCTP link.

eNodeB (FDD/TDD) NB-IoT and


FDD/TDD share an
EPC.

eNodeB (NB-IoT)

Data
planning: SCTP Link IP Address SFTP Port No.
NB-IoT and FDD/TDD NB-IoT and FDD/TDD The SCTP IP address that is The SCTP port No. that is
are deployed by the share an SCTP link. the same as that for the same as that for
same operator. FDD/TDD has been FDD/TDD has been planned.
planned.
Data planning in EP configuration mode is the same as that in LINK
configuration mode.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11


S1 Configuration in NB-IoT EPC and FDD/TDD
EPC Co-Deployment
Model 1: Some MMEs support NB-IoT after being upgraded. Model 2: Some MMEs support NB-IoT after being
(A new S1 object dedicated for NB-IoT is required.) upgraded. (An S1 object for FDD/TDD is shared.)

FDD/TDD+NB-IoT MME FDD/TDD MME FDD/TDD+NB-IoT MME


FDD/TDD MME

S1Interface S1Interface S1Interface


S1Interface
S1Interface S1Interface

Configuration
S1 Configuration
S1 S1 model 1
model 3
eNodeB
eNodeB
S1 Configuration
Model NB-IoT Capability Configuration Suggestion
Mode
The NB-IoT capability can be
Model 3: All MMEs support NB-IoT after being upgraded. Setting up an S1 configured depending on the S1
1 object dedicated for object. The same NB-IoT capability Recommended
FDD/TDD+NB-IoT
FDD/TDD+NB-IoTMME
MME FDD/TDD+NB-IoT MME NB-IoT must be configured for all MMEs
under an S1 object.
The NB-IoT capability can be
Sharing the S1 independently configured for an Not
2
S1Interface S1Interface
S1Interface object for FDD/TDD MME depending on the S1 recommended
interface.
The NB-IoT capability can be
Updating the NB-IoT configured depending on the S1
S1 Configuration 3 capability for the S1 object. The same NB-IoT capability recommended
model 2 object must be configured for all MMEs
under an S1 object.
eNodeB Note: In simplified EP mode, an operator is not allowed to use different S1
objects. Therefore, configuration mode 1 cannot be used.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12
S1 Configuration in NB-IoT EPC and FDD/TDD
EPC Co-Deployment
The S1 object for NB-IoT is newly set up, and the NB-IoT capability is configured for an MME
depending on the S1 object.
For details, see section "S1 Configuration in New NB-IoT EPC Deployment."
Note: As the MME also supports FDD/TDD, NbLteSupportCap in the ADD MmeCapInfo command must be set to
SUPPORT.

The S1 object for FDD/TDD is reused, and the NB-IoT capability is configured for an MME
depending on the S1 interface.
Step 1: Run the following command to add a TAI for NB-IoT:
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=18888 NbIotTaFlag=BOOLEAN_TRUE;
Step 2: Run the following command to query GUMMEIs and S1 interface IDs of all MMEs and determine the S1 interface
ID of the MME supporting NB-IoT:
DSP SERVEDGUMMEIS;
Step 3: Run the following command to configure the NB-IoT capability based on the S1 interface ID (with the value of 1) of
the NB-IoT MME:
/* Configuring NB-IoT capabilities depending on the S1 interface (CP Only is supported, and CP+FDD/TDD is not
supported.) */
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1INTERFACE _CFG , S1InterfaceId=1, NbCiotEpsOptCap=CP,
NbLteSupportCap= SUPPORT;

The S1 object for FDD/TDD is changed to support NB-IoT.


Step 1: Run the following command to add a TAI for NB-IoT:
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=18888, NbIotTaFlag=BOOLEAN_TRUE;
Step 2: Run the following command to configure NB-IoT capabilities depending on the S1 object (CP Only or
CP+FDD/TDD is supported):
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1_CFG , S1Id=0, NbCiotEpsOptCap=CP, NbLteSupportCap=
SUPPORT;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13


S1 Configuration in NB-IoT EPC and FDD/TDD
EPC Co-Deployment
After the NB-IoT capability is added for the S1 object for FDD/TDD, one of MMEs must be
rolled back to support only FDD/TDD.

Step 1: Run the following command to configure NB-IoT capabilities depending on the S1 object
(CP Only or CP+FDD/TDD is supported):
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1 _CFG , S1Id=0, NbCiotEpsOptCap=CP,
NbLteSupportCap= SUPPORT;
Step 2: Run the following command to query GUMMEIs and S1 interface IDs of MMEs and
determine the S1 interface ID of the MME to be rolled back:
DSP SERVEDGUMMEIS;
Step 3: Run the following command to change the NB-IoT capability of the MME based on the S1
interface ID (with the value of 1) of the MME that doe not support NB-IoT:
ADD MmeCapInfo: MmeCapCfgId=0, S1CfgType= S1INTERFACE _CFG , S1InterfaceId=1,
NbCiotEpsOptCap=NOT_ SUPPORT , NbLteSupportCap= SUPPORT;

The NB-IoT capability configured for the S1 interface using the MmeCapInfo MO can be different
from that configured for the S1 object. An eNodeB preferentially determines the MME capability
based on the configuration over the S1 interface.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14


Evolution from CP to CP+UP for NB-IoT

1. EP configuration mode:
In separate- or co-EPC deployment, if NB-IoT and FDD/TDD are deployed by the same
operator, user-plane IP addresses must be the same.
In separate- or co-EPC deployment, if NB-IoT and FDD/TDD are deployed by different
operators, user-plane IP addresses can be the same or different.
2. LINK configuration mode:
The S1-U interfaces of NB-IoT and FDD/TDD can use the same IP path or different IP paths.
3. During S1 user-plane parameter configuration for the NB-IoT MME in eRAN12.01, if the S1
user-plane peer address has been planned, the S1 user plane can also be configured. If the
user-plane peer address has not been planned, only information about the user-plane local
end can be configured. After the UP function is supported in eRAN12.1, information about the
user-plane peer end will be automatically configured.
To simplify configurations, it is recommended that NB-IoT share the user-plane local address of
FDD/TDD.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15


QoS Design
The following table lists values recommended by Huawei. These values can be changed based on customers' requirements.

DSCP
DSCP MML Command Used for Configuring a
Service Type (Hexadecimal Value Type VLAN Pri
(Decimal) DSCP Value
)
QCI1 0x2E 46 ADD UDTPARAGRP USERDATA 5
QCI2 0x1A 34 ADD UDTPARAGRP USERDATA 4
QCI3 0x1A 34 ADD UDTPARAGRP USERDATA 4
QCI4 0x1A 34 ADD UDTPARAGRP USERDATA 4
S1-U/X1-U QCI5 0x2E 46 ADD UDTPARAGRP USERDATA 5
QCI6 0x12 18 ADD UDTPARAGRP USERDATA 2
QCI7 0x12 18 ADD UDTPARAGRP USERDATA 2
QCI8 0x12 18 ADD UDTPARAGRP USERDATA 2
QCI9 0 0 ADD UDTPARAGRP USERDATA 0
eX2-U0 0x1A 34 ADD UDTPARAGRP USERDATA 3

eX2-U1 0x12 18 ADD UDTPARAGRP USERDATA 2

eX2-U2 0 0 ADD UDTPARAGRP USERDATA 0


S1-C/X1-C/eX2-
0x30 48 SET DIFPRI SIG 6
C SCTP
MML 0x2E 46 SET DIFPRI OM_H 5
OM FTP 0x12 18 SET DIFPRI OM_L 2
IP clock 1588V2 0x2E 46 SET DIFPRI USERDATA 5
This value is configured based on
BFD Manual Configuration ADD BFDSESSION OTHER the DSCP value on a customer's
network.
IKE 0x30 48 SET IKECFG USERDATA 6
This value is configured based on
IPPM Manual Configuration ADD IPPMSESSION OTHER the DSCP value on a customer's
network.
Ping packet 0 0 PING USERDATA 0
GTPU echo detection 0x2E 46 MOD GTPU OTHER 5
This value is configured based on
TWAMP Manual Configuration ADD TWAMPSENDER OTHER the DSCP value on a customer's
network.
TRACERT 0 0 TRACERT USERDATA 0
This value does not need to be configured.
The DSCP value in a response packet from
NB-IoT services
Ping (response packet)for CP 0only involve
0 SCTP service flows, and therefore NB-IoT data flows
0 are
an eNodeB is the same as that of the peer
USERDATA
eNodeB. In most cases, the DSCP value in a
scheduled based on SCTP priorities. The default DSCP value in the red row is 48.
ping command for the transmission
equipment or CN is 0.
ARP No DSCP value This value does not need to be configured. OTHER 5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16


Transmission Bandwidth
Transmission bandwidth
= (Average bandwidth of a single NB-IoT cell over the air interface x Number of cell under the single NB-IoT
base station x Scenario factor/Transmission efficiency) + 600kbps OM bandwith
The following table lists Huawei model-based scenario factors.
Scenario Coefficient
DU (dense urban area) 1
U (urban area) 0.9
SU (suburban area) 0.8
RA (rural area) 0.7

The average bandwidth of a single NB-IoT cell over the air interface is 250 kbit/s (uplink peak bandwidth of signaling
and data), and the average packet length is 200 Bytes (SCTP payload). The IPsec transmission efficiency calculated
based on the average bandwidth and packet length is 58%, and non-IPsec transmission efficiency is 72.9%.

The following table lists transmission bandwidths calculated in an NB-IoT base station serving three cells.

Bandwidth (kbit/s)
Scenario
IPsec Non-IPsec
DU (dense urban area) 1893 1627
U (urban area) 1764 1526
SU (suburban area) 1634 1423
RA (rural area) 1505 1320

Conclusion: It is recommended that the bandwidth of 2 MHz be reserved during NBIOT


transmission bandwidth planning.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17


THANK YOU
WWW.HUAWEI.COM

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18