Technical_Training_of_5G_Networking_Design.pptx

HUAWEI TECHNOLOGIES CO., LTD.
www.huawei.com
Huawei Confidential
Internal
2018/02/12
Technical Training of
5G Networking Design

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2
5G RAN2.0 supports only non-standalone (NSA)
networking. This document describes the network
design and recommended configurations in the
engineering preparation and goods delivery phase, as
well as the differences between gNodeBs and
eNodeBs in network design. It also guides network
design and implementation. This document provides
service, marketing, and network design departments
with network planning, while helping telecom
operators implement network development planning.

Contents
Network Design Overview of 5G NSA Networking
OM Networking, gNodeB Naming and Numbering, and NE Timing
1
2
Clock Synchronization (Frequency/Time Synchronization) Design
3
Transmission Overview, IP Interconnection Design, Interface Bandwidth
Calculation, and QoS Design
4
Transmission Reliability and Security Design
5

1. Understand the overall network design architecture, contents, and
deliverables.
2. Understand OM design (networking, reliability, security, gNodeB/cell
naming rules, and timing server selection).
3. Understand external clock source selection and recommendation
policies.
4. Understand NSA transmission networking (address, VLAN planning,
bandwidth calculation, delay, jitter, packet loss rate, and QoS
requirements).
5. Understand the network reliability and security requirements as well as
feature supports in target markets.

5G NSA Networking Introduction
1. Networking of option 3X prevents issues raised by insufficient processing capabilities of existing boards. However, the impacts on mobility from areas with 5G
coverage to area without 5G coverage are greater in comparison with option 3.
2. Option 3X is recommended to reduce the dependence on existing networks and improve 5G capabilities in service expansion and network evolution.
Local site
EPC
BTS3900(L)
BBU5900(NR)
DC
X2
S1-C
S1-U
Option 3X
UMPTe
UMPTa/b
Local site
EPC
BTS3900(L)
BBU5900(NR)
DC
S1-C/S1-U
Option 3
UMPTe
UMPTa/b
X2
eNodeB (LTE)
MACLTE
gNodeB (5G)
PDCPLTE
RLCNR
MACNR
S1-U
X2
RLCLTE
GTP-U
GTP-U
eNodeB (LTE)
MACLTE
gNodeB (5G)
PDCPNR
RLCNR
MACNR
S1-U
X2
RLCLTE
GTP-U
GTP-U
Option 3 Option 3X
Dynamic data transfer ☺ Supported, and controlled by an eNodeB algorithm ☺ Supported, and controlled by a gNodeB algorithm
Impacts on existing eNodeBs
 eNodeB service processing capabilities must meet the requirements of 5G S1-U
PDCP processing and service traffic.
☺ eNodeB service processing capabilities do not need to be
enhanced.
5G service expansion capabilities
 5G service expansion capabilities may be limited due to insufficient eNodeB service
processing capabilities.
☺ Excellent 5G service expansion capabilities
UE mobility
☺ Small impacts on services due to eNodeB measurement and data transfer capabilities
when UEs move from areas with 5G coverage to areas without 5G coverage.
5G services are interrupted over the air interface when UEs move
from areas with 5G coverage to areas without 5G coverage.
Planning of transmission to/from CN ☺ None S1-U transmission links must be planned for gNodeBs.

NSA Network Design and Comparison with LTE in 5G RAN2.0
Aggregation
S1-U
S1-C
Last Mile Access
gNodeB
IP Core
U2020
OM
eNodeB
X2
SeGW
PKI Server
MME
HSS
Serving GW PDN GW
PCRF
5G-Uu
5G UE
User plane
Option 3X (data transfer to 5G) is recommended.
User plane
Control plane
X2-U
traffic
5G NSA Integrated Base Station Network Design
 5G NSA networking must be deployed together with LTE. For LTE network design, see LTE FDD Network Design technical training (eRAN 12.1).
 OM planning (same as LTE)
 Reference clock source planning (similar to LTE with a difference that 5G only supports GPS and 1588v2)
 Service interface and address planning (option 3X: S1-U/X2; option 3: X2)
 Interface bandwidth calculation (based on the NSA service traffic model)
 QoS design (QoS design for transmission of NSA is the same as that for transmission of LTE; QoS design for the air interface will be supported in 5G RAN2.0)
 Reliability and security design (same as LTE)

Network design Network operation and optimization
Network construction
Network planning
Network planning HLD&LLD
Network
construction
Routine maintenance and
network optimization
 New network deployment
New network deployment
(main scenarios)
 Capacity expansion
required due to increased
service volume during
normal network operation
Network capacity expansion
 Replacement of non-
Huawei devices
Network migration
 Promotion of new
functions and
services
Network evolution
Network design scenarios
Position of Network Design in Network Lifecycle

Network Design Process
Contract
Target network diagram
Operator's requirements
Project
Information
Note: The inputs are
determined based on
requirements on
network design of
target sites.
Input Output
Input
HLD LLD
Information
collection
Planning Project
overview
Requirements on air
interface counters
Target network scale
System clock
Network reliability and interface
security
IP interconnection, bandwidth, latency,
packet loss, and QoS
O&M design (networking, gNodeB naming
and numbering, and NE timing)
Hardware resource configuration Network design
Note:
1. For details on hardware
resource configuration
design, see the 5G site
design training slides.
2. EMS and CN design for
5G is the same as that
for LTE and is not
described in this
document.
Design of operator's existing
networks

Network Design Scope
SSL, IPsec channel, 802.1X, and others
5G site/cell naming
Timing for routine maintenance after gNodeBs work on networks
5G transmission port, IP address, VLAN planning, and others
Address planning, reliability, and OM security policies
Route backup, OMCH backup, and others
NE timing
Transmission reliability design
IP interconnection design
OM networking design
Transmission security design
Naming and numbering
QoS design
Recommended 5G QoS configurations and future QoS requirement
planning
5G clock source selection principles and recommended policy design
Clock synchronization design
Transmission bandwidth calculated based on the 5G traffic model
Requirements on the delay, jitter, and packet loss rate of 5G services
Requirements on the bandwidth,
delay, jitter, and packet loss rate

5G NSA OM Design
OMCH QoS OM security policy
OM network topology and address plan OMCH reliability
 Network topology
1. Co-EMS with LTE (recommended, same as LTE)
2. Separate-EMS with LTE (Features that require U2020 cooperation for
inter-RAT interaction, for example X2 self-setup, are not supported.)
 Address planning is the same as that for LTE. (IP interconnection)
 DHCP configurations during PnP deployment are the same as those
for LTE.
 The maintenance IP address and service IP address are different.
The logical IP address and interface IP address are decoupled.
(Recommended, the same as LTE)
 SSL secure communication is used. (Recommended, the same
as LTE)
OMCH backup function (used in remote HA U2020 systems, same
as LTE)
ADD OMCH: FLAG=MASTER…;
ADD OMCH: FLAG=SLAVE…;
The priority is high, which is the same as LTE. A DSCP value of 46 is
recommended for MML data and a DSCP value of 18 is recommended for
FTP data.
SET DIFPRI: PRIRULE=DSCP, MHIGHPRI=46, OMLOWPRI=18;
QoS design
gNodeB
eNodeB
U2020
UMPTe
DEVIP: 10.1.1.X
OMIP: 20.1.1.X
X2/S1IP: 30.1.1.X
Reference:
 For details on PDCP during PnP deployment, see Automatic OMCH Establishment
Feature Parameter Description for BTS5900.
 To enable SSL, choose Security > Certificate Authentication Management > SSL
Connection Management on the U2020. For details on how to enable SSL, see SSL
Feature Parameter Description for BTS5900.
Refer to the design of existing networks for how to deploy gNodeBs on LTE networks, 5G transmission addresses, route planning,
server deployment, and reliability and security solutions.

5G Site/Cell Naming Design
Note: The naming rules are the same as those for LTE, as required by telecom operators.
 Recommended site name: Region name+"_"+Site type+"_"+Site number. Abbreviate the region name if possible. For example,
Shanghai Jinqiao_DBS5900_1
Restriction: The site name is a string of a maximum of 64 characters. The string cannot be all null characters or contain any of
the following characters: question marks (?), colons (:), right angle brackets (>), left angle brackets (<), stars (*), slashes (/),
backslashes(), pipes (|), double quotation marks ("), commas (,), semicolons (;), equal signs (=), single quotation marks ('), three
or more consecutive plus signs (+), two or more consecutive spaces, and two or more consecutive percentage signs (%).
 Recommended cell name: Site name+"_"+Cell+Cell number. For example, Shanghai Jinqiao_DBS5900_1_Cell1.
1. Cell numbers start from 1. If there are multiple frequencies on the operator's network, for example, the numbers of cells
operating at the first frequency are 1 to 5 and the numbers of those operating at the second frequency are 6 to 10.
2. Restriction: The cell name is a string of a maximum of 99 characters. The string cannot be all null characters or contain any
of the following characters: question marks (?), colons (:), right angle brackets (>), left angle brackets (<), stars (*), slashes
(/), backslashes(), pipes (|), double quotation marks ("), commas (,), semicolons (;), equal signs (=), single quotation marks
('), three or more consecutive plus signs (+), two or more consecutive spaces, and two or more consecutive percentage
signs (%).
 Description of site and cell IDs
gNBId: a 20-bit ID. That is, the ID range is from 0 to 1048575.
gNBDuId: a 24-bit ID. That is, the ID range is from 0 to 16777215. In 5G RAN2.0, 5G is deployed on CU/DU integrated base stations, and therefore
this gNodeB DU ID is usually set to the same value a the gNodeB ID.
CellId: The ID range is from 0 to 255. A combination of the PLMN, site ID, and cell ID uniquely identifies a 5G cell in the globe.
NrLocalCellId: The ID range is from 0 to 255.
PhysicalCellId: The ID range is from 0 to 1007. (PCI multiplexing is required, but the PCIs of adjacent cells must be different to avoid interference
over the radio interface.)

Item Recommendation Selection Policy
Timing mode
(The
recommendations
have a descending
order of priorities.)
GPS
1. If the operator's network can
access the GPS, use the GPS.
2. GPS antennas need to be
installed. There are special
requirements on the site
selection to allow GPS signal
reception.
Private NTP server of the operator Considering reliability, the private
NTP server is preferred.
NTP server in the U2020
Timing period
(configurable)
360 minutes
An excessively short timing period
will lead to frequent timing and heavy
load of the NTP server.
Number of the
timing port
(configurable)
123 by default
Reliability
A maximum of four NTP servers
can be configured on a base
station, with one of them as the
primary NTP server.
If synchronization with the primary
NTP server fails, the base station
synchronizes with other NTP servers.
NE Timing (Synchronization with Time Source)
Timing (synchronization with the time source) aims to ensure that the time on devices within a
network is consistent. This enables the devices to provide multiple applications that require timing.
The base station uses Coordinated Universal Time (abbreviated to UTC).
Note: If NTP time synchronization of the base station fails, the internal timing of the base station is not interrupted. The time deviation of the base station depends on the
internal clock precision.
When the internal clock is synchronized with the external clock source, the time deviation of the base station does not exceed 1 second each day.

Timing Configuration (Reference)
GPS timing configuration
SET TIMESRC: TIMESRC=GPS;
SET TZ: ZONET=GMT+0800, DST=NO;
NTP timing configuration
SET TIMESRC: TIMESRC=NTP;
SET TZ: ZONET=GMT+0800, DST=NO;
ADD NTPC: MODE=IPV4, IP="10.10.10.1", PORT=123, SYNCCYCLE=360, AUTHMODE=PLAIN;
In a remote HA U2020 system, the active and standby U2020s use different IP addresses.
Considering security, configure both the two U2020s as NTP servers and assign the primary NTP
server. The following is an MML example:
ADD NTPC: MODE=IPV4, IP="10.10.10.2", PORT=123, SYNCCYCLE=360, AUTHMODE=PLAIN;
SET MASTERNTPS: MODE=IPV4, IP="10.10.10.1";

gNodeB Clock Synchronization Design
 gNodeB clock synchronization recommend time synchronization.
 TDD networks adopt time division multiplexing and require time synchronization to mitigate inter-base station and inter-UE
interference. To achieve time synchronization, both frequency and phase synchronization must be achieved. The TDD clock
source must also meet the requirements for FDD frequency synchronization.
 The requirements on clock accuracy of gNodeBs are described as follows:
 Frequency synchronization: ±0.05 ppm as recommended by 3GPP. The deviation is ±0.5 Hz for 10 MHz clocks.
 Time synchronization: < 3 μs (±1.5 μs) as agreed by 3GPP specifications.
 gNodeB clock source type
 gNodeB clock source working
mode
System clock source information

System clock source configuration
GPS
1588v2: The clock recovery quality is vulnerable to
the delay, jitter, and packet loss of data networks.
Manual mode
gNodeB
Clock
server
Network
Technology Counter Specifications
IEEE 1588v2 Jitter < 20 ms
Packet loss rate < 1%

gNodeB Configuration (Reference)
• (Optional) If the clock source is 1588v2:
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="xxx.xxx.xxx.xxx",
SIP="xxx.xxx.xxx.xxx", DELAYTYPE=E2E, PROFILETYPE=1588V2;
• (Mandatory) Set the clock synchronization mode.
SET CLKSYNCMODE:CLKSYNCMODE=TIME;
• (Optional) If the clock source is GPS:
ADD GPS: GN=0,CN=0,SRN=0,SN=7,CABLE_LEN=30,MODE=GPS,PRI=1,POSCHECKSW=ON;
1. The compensation value is calculated based the GPS feeder length to improve clock accuracy. An
excessively large difference between the configured GPS feeder length and the actual length will affect the
clock accuracy.
2. Whether to use the GPS clock relies on satellite card capabilities and operator's requirements. In 5G RAN2.0,
only UMPTe boards can serve as 5G main control boards. The UMPTe boards integrate GPS/BDS satellite
cards. Currently, GPS satellite cards are more widely used.
• (Mandatory) Set the clock synchronization mode.
SET CLKMODE: MODE=MANUAL, CLKSRC=XXX, SYNMODE=OFF;

gNodeB Clock Source Selection
Synchronization
Technology
5G RAN2.0
Frequency
Synchronization
Time
Synchronization
Advantage Disadvantage
GPS Recommended Supported Supported
1. Each gNodeB is configured with an
independent GPS satellite card or RGPS device,
without the support of the network.
2. The clock accuracy is high.
Investments in the GPS satellite card or RGPS device and
their installation and maintenance are required.
IEEE 1588v2
Not
recommended
Supported Supported
1. Investments on equipment are low.
2. IEEE 1588v2 is a standard protocol. Therefore,
interworking between equipment of different
vendors is supported.
1. To provide time synchronization, all the transmission
equipment must support IEEE 1588v2.
2. The clock recovery quality is vulnerable to the delay, jitter,
and packet loss of data networks.
BITS (Building
Integrated Timing
Supply)
Not supported Supported Not supported
Synchronous
Ethernet
Not supported Supported Not supported
Clock over IP Not supported Supported Not supported
E1/T1 line clock Not supported Supported Not supported

gNodeB Clock Source Introduction
gNodeBs obtain GPS clock signals
from the GPS through external
antenna systems and UMPT boards
equipped with satellite cards.
The GPS antenna system receives
GPS signals at 1575.42 MHz and
transmits the signals to the GPS
satellite card. At least four satellites
need to be traced.
• A clock server sends IEEE 1588v2 clock
synchronization packets to the gNodeB through the
data bearer network.
• All intermediate equipment on the data bearer network
must support the BC/TC function defined in the IEEE
1588v2 standards.
• Clock servers need to input precise clock signals by
GPS.
gNodeB
gNodeB
IEEE 1588v2 packet transmission path
Clock synchronization link
FE/GE link
Metro Ethernet
Or private packet
network
Router or
Ethernet switch
BC/TC
Router or
Ethernet switch
BC/TC
Clock server
BC
Clock server
BC
Clock server
BC
GPS

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
 Combined synchronization sources:
Page 18
Clock Reliability
 Master and backup clock solution
1. Backup clock link
2. GPS clock + IEEE 1588v2 clock
gNodeB IEEE 1588v2
clock packets
IEEE
1588v2 BC
IEEE
1588v2 BC
SyncE
node
SyncE
node
Synchronous
Ethernet
IEEE 1588v2
clock server
GPS
SyncE
clock
signals Transport network SyncE
node
SyncE
node
GPS
gNodeB
GPS
GPS antenna
Transport network
SyncE
clock
signals
Synchronous
Ethernet clock
source
2. Combination of GPS and synchronous Ethernet
1. Combination of IEEE 1588v2 and synchronous Ethernet

5G NSA IP Interconnection Design Overview
X2-U
X2-C
EPC
eNodeB gNodeB
S1-U
5G UE
User plane
User plane
Control plane
S1-C
U2020
OM
Option 3X (recommended)
Option 3X (recommended)
 UE signaling is transmitted from eNodeBs to the CN, and S1-C links are established on eNodeBs and
not on gNodeBs.
 S1-U links are established between gNodeBs and the CN. S1 self-setup is supported. User traffic is
transferred to gNodeBs and LTE/5G DC is supported.
 5G networks rely on LTE networks. X2 links are established between eNodeBs and gNodeBs. (X2
self-setup is supported only in 5G/LTE co-EMS scenarios.)
 In 5G RAN2.0, 5G main control boards must be UMPTe boards. Each UMPTe has two 10 GE optical
transmission ports, each supporting a bandwidth of 10 Gbit/s.
 If the transmission bandwidth of the base station is insufficient, use the following methods to improve
bandwidth capabilities:
Use two main control boards with one of them working as a transmission interface board (only for 5G).
Option 3
 S1 links are established only on eNodeBs and not on gNodeBs. User traffic is transferred to
eNodeBs and LTE/5G DC is supported.
 X2 links are established between eNodeBs and gNodeBs. (X2 self-setup is supported in co-EMS
scenarios.)
 The interface bandwidth capabilities of existing LTE main control boards (UMPTa and UMPTb
boards) are insufficient and therefore option 3 is not recommended.
X2-U
X2-C
EPC
eNodeB gNodeB
5G UE
User plane
User plane
Control plane
S1-C
U2020
OM
S1-U
Option 3

IP Address and VLAN Planning
 Policies of intra-base station IP address planning
Base station transmission links include S1-U links (option 3X), X2 links, OM links, and clock links (optional).
IP Address Solution Advantage Disadvantage Selection Policy
Logical host addresses are used.
Service addresses and interface addresses are decoupled
and address planning is easy to be unified.
Service IP addresses in secure networking are not exposed
on public networks.
A single RAT occupies many IP addresses.
Default and
recommended
Interface addresses or addresses in
the same network segment as
interface addresses are used.
IP addresses of a single RAT are easy to manage and
maintain.
Gateway routes do not need to be configured.
Service addresses and interface addresses are coupled
and address planning is difficult to be unified.
This solution does not apply to secure networking.
Recommended plans for option 3X
1. If the interface bandwidth meets requirement, use one physical port to save physical resources.
2. Assign two logical IP addresses for each gNodeB, one for S1-U/X2 links and the other for OM/clock links. VLAN isolation is recommended.
3. Consider plans of operator's existing networks when planning interface IP addresses and VLANs for multiple gNodeBs.
Scenario Planning Solution Solution Description Advantage and Disadvantage
The base station is directly
connected to the gateway.
Different network segments
and same VLAN
It is recommended that the interface IP subnet mask be /30.
IP address wastes
Easy planning and maintenance
IP resources are sufficient
and VLAN isolation between
base stations is required.
Different network segments
and different VLANs
It is recommended that the interface IP subnet mask be set to /29 (compatible with VRRP
networking of remote routers; at least 4 IP addresses are required).
IP address wastes
High security and reliability
IP resources are insufficient
base stations is not required.
Same network segment
and same VLAN
It is recommended that the interface IP subnet mask be set to /25 and that a maximum of
100 base stations be deployed on the same network segment to prevent L2 network
broadcast storms. 50 base stations are recommended in the early stage of network
construction.
Less IP addresses occupied
Storm risks in the broadcast
domain
IP resources are insufficient
base stations is required.
Same network segment
and different VLANs
1. It is recommended that the interface IP subnet mask be /25.
2. Super VLANs must be configured on the gateway device and different VLANs must be
configured for different base stations.
Less IP addresses occupied and
isolates between base stations
Routes must support super VLANs.
 Policies of inter-base station IP address and VLAN planning (depending on whether IP resources are sufficient and whether network isolation between base stations is
required)

Communication Ports
 If a firewall is deployed between the gNodeB and the peer device or NE (such as the
U2020 or S-GW), the corresponding communication port of the firewall must be
enabled. For details, see the latest communication matrix at
http://support.huawei.com.
 gNodeB communication ports are the same as eNodeB communication ports. NSA
networking is based on LTE networks, and the firewall communication ports are
usually enabled on operator's networks.

Interface Bandwidth Calculation of 5G Option 3X
Parameter Default Remark
Number of Users 1200 Data source: number of users in a cell
Average Throughput Rate/User_UL(Mbps) 0.8
Data source: cell plan
Average Throughput Rate/User_DL(Mbps) 4.8
Packet Payload Size(Bytes) 700
X2U to S1U Ratio(%) 10
Data source: empirical value in the range of [0,100]
Data transferred to gNodeB
1. S1-U -> BTS5900 -> X2 -> LTE
2. S1-U -> BTS5900 -> 5G Uu
Enable VLAN YES
Data source: operator's network security requirements
(VLANs are planned by default.)
Enable IPSEC NO
(IPsec is disabled by default.)
Duplex Type Full-Duplex
Data source: operator's network security requirements (Full
duplex is used by default.)
GTPU Head(Bytes) 12
UDP Head(Bytes) 8
IP Head(Bytes) 20
IPSEC Head(Bytes) 70
VLAN Head(Bytes) 4
MAC Head(Bytes) 18
Peak Average Ratio 1.25 Data source: empirical value, 1.25 by default
Control to User Ratio(%) 1 Data source: empirical value, 1% by default
OM Bandwidth(Kbps) 1024 Data source: empirical value, 1024 kbit/s by default
IPCLK Bandwidth(Kbps) 0
This parameter is available only when an IP clock server is
deployed.
S1U Peak Bandwidth(Mbps) 7838 S1-U interface bandwidth: 5G traffic
S1C Peak Bandwidth(Mbps) 79 S1-C interface bandwidth: LTE traffic
X2U Peak Bandwidth(Mbps) 784
X2-U interface bandwidth: LTE traffic (5G traffic is included
in S1-U traffic.)
X2C Peak Bandwidth(Mbps) 8 X2-C interface bandwidth: LTE and 5G traffic
5G Total Bandwidth Required(Mbps) 7848 Total 5G bandwidth requirements
LTE Additional Bandwidth Required(Mbps) 871 Additional eNodeB traffic
Interface Formula (Full-Duplex)
S1-U traffic
Number of users over the air interface x
Size of a single transport layer packet x
(Average downlink air interface rate of a
single user/Size of a single air interface
packet) x Traffic peak-to-average ratio
S1-C traffic S1-U traffic x Control to User Ratio
X2 traffic
S1-U traffic x (X2U to S1U Ratio) x (1+
Control to User Ratio)
Total gNodeB
traffic
S1-U traffic + X2-C traffic + OM traffic +
IP clock traffic
Additional
eNodeB traffic
X2 traffic + S1-C traffic

Interface Bandwidth Calculation of 5G Option 3
The differences between option 3X and option 3 are
as follows:
1. In option 3 networking, X2U to S1U Ratio equals 90%.
2. In option 3 networking, the transmission capabilities of the
main control boards in existing base stations are insufficient,
and this poses a limitation on the number of users in cells.
Parameter Value Remark
Number of Users 200 Data source: number of users in a cell
Average Throughput Rate/User_UL(Mbps) 0.8 Rate over the Uu interface
Data source: cell plan
Average Throughput Rate/User_DL(Mbps) 4.8
Packet Payload Size(Bytes) 700
X2U to S1U Ratio(%) 90
Data source: empirical value in the range of [0,100]
Data transferred to eNodeB
1. S1-U -> LTE -> X2 -> 5G
2. S1-U -> LTE -> Uu
Enable VLAN YES
(VLANs are planned by default.)
Enable IPSEC NO
(IPsec is disabled by default.)
Duplex Type Full-Duplex
(Full duplex is used by default.)
GTPU Head(Bytes) 12
UDP Head(Bytes) 8
IP Head(Bytes) 20
IPSEC Head(Bytes) 70
VLAN Head(Bytes) 4
MAC Head(Bytes) 18
Peak Average Ratio 1.25 Data source: empirical value, 1.25 by default
Control to User Ratio(%) 1 Data source: empirical value, 1% by default
OM Bandwidth(Kbps) 1024 Data source: empirical value, 1024 kbit/s by default
IPCLK Bandwidth(Kbps) 0
This parameter is available only when an IP clock server
is deployed.
S1U Interface Peak Bandwidth(Mbps) 1307 S1-U interface bandwidth: LTE traffic
S1C Interface Peak Bandwidth(Mbps) 14 S1-C interface bandwidth: LTE traffic
X2U Interface Peak Bandwidth(Mbps) 1177
X2-U interface bandwidth: 5G traffic (LTE traffic is
included in S1-U traffic.)
X2C Interface Peak Bandwidth(Mbps) 12 X2-C interface bandwidth: LTE and 5G traffic
5G Total Bandwidth Required(Mbps) 1191 Total 5G bandwidth requirements
LTE Additional Bandwidth Required(Mbps) 1333 Additional eNodeB traffic
Traffic Formula (Full-Duplex)
S1-U traffic
Number of users over the air interface x Size of a
single transport layer packet x (Average downlink air
interface rate of a single user/Size of a single air
interface packet) x Traffic peak-to-average ratio
S1-C traffic S1-U traffic x Control to User Ratio
X2 traffic
S1-U traffic x (X2U to S1U Ratio) x (1+ Control to
User Ratio)
Total gNodeB
traffic
X2 traffic + OM traffic + IP clock traffic
Additional
eNodeB traffic
S1-U traffic + S1-C traffic + X2-C traffic

5G NSA Networking Requirements on Delay, Jitter, and Packet Loss Rate
NSA One-Way Delay (ms) Jitter (ms) Packet Loss Ratio
Optimum Value Recommended Value Tolerable Value
Optimum
Value
Recommended Value Tolerable Value
Optimum
Value
S1 interface 5 10 20 2 4 8
0.0001% 0.001% 0.5%
X2 interface 10 20 40 4 7 10
SA One-Way Delay (ms) One-Way Jitter (ms) Packet Loss Ratio
Optimum Value Recommended Value Tolerable Value
Optimum
Value
Optimum
Value
NG interface 1 5 20 0.5 2 8
0.00001% 0.0001% 0.5%
Xn interface 2 10 40 1 4 10
The following table lists 5G RAN2.0 requirements on the transmission delay, jitter, and packet loss rate.
The following tables list the requirements on the transmission delay, jitter, and packet loss rate after inter-site coordination and SA networking are
supported in the future.
Inter-site
coordination
The following table lists 5G RAN2.0 requirements on the air
interface jitter and packet loss rate.

5G NSA QoS Design Wireless network layer design
 On the user plane, high-priority services are mapped to high-priority
logical channels based on the QCI types configured on the CN to
ensure preferential scheduling.
 The control plane is always preferentially scheduled.
 5G RAN2.0 supports QoS design.
 QoS processing on the E-UTRAN side remains unchanged.
Transport network layer design
 Transmission QoS control is performed between the local base
station and the CN or neighboring base stations. Different DSCPs
are tagged according to the data transmission priorities and mapped
to different VLAN priorities. The mappings are configurable.
 Priorities are determined based on the operator's service
requirements. Service QCIs must be consistent with those
configured on the CN. You can configure the service QCIs
according to Huawei-recommended values. Signaling and OM
transmission bandwidth must be preferentially ensured.
User service classification
 User-plan service types in NSA networking comply with LTE
specifications (QCIs 1 to 9).
 New 5G service types are supported in SA networking.
X2-U
X2-C
EPC
eNodeB gNodeB
S1-U
5G UE
User plane
User plane
Control plane
S1-C
U2020
OM
S1-U
Wireless network layer
Transport network layer
Blue: option 3X
Red: option 3

Page 26
Service Type DSCP (Hexadecimal) DSCP (Decimal) MML Command Used for Configuring DSCP Values VLAN Priority
User plane
QCI 1 0x2E 46 ADD UDTPARAGRP 5
QCI 2 0x1A 34 ADD UDTPARAGRP 4
QCI 5 0x2E 46 ADD UDTPARAGRP 5
QCI 6 0x12 18 ADD UDTPARAGRP 2
QCI 9 0 0 ADD UDTPARAGRP 0
Control plane (SCTP) 0x30 48 SET DIFPRI 6
OM
MML 0x2E 46 SET DIFPRI 5
FTP 0x12 18 SET DIFPRI 2
IP clock 1588V2 0x2E 46 SET DIFPRI 5
BFD Configurable ADD BFDSESSION
Configured based on existing DSCP values of the operator's
network
IKE 0x30 48 SET IKECFG 6
IPPM Configurable
ADD IPPMSESSION Configured based on existing DSCP values of the operator's
network
Ping packets 0 0 PING 0
GTPU echo detection 0x2E 46 MOD GTPU 5
TWAMP Configurable ADD TWAMPSENDER
Configured based on existing DSCP values of the operator's
network
TRACERT 0 0 TRACERT 0
Ping responses packets 0 0
No configuration is required. DSCP values of ping response packets equal
those of ping packets. Generally, DSCP values of ping packets from
transmission devices and CN are 0.
0
ARP None No configuration is required. 5
DSCP Value Range VLAN Priority
56 to 63 7
48 to 55 6
40 to 47 5
32 to 39 4
24 to 31 3
16 to 23 2
8 to 15 1
0 to 7 0
The right table provides the default mappings between
DSCP value ranges and VLAN priorities. If modification
is required, run the SET DSCPMAP command.
Huawei-Recommended Transport Network Layer QoS Configuration

5G NSA Transmission Redundancy and Fault Detection Design
After detecting transmission link faults, the gNodeB uses the corresponding redundancy mechanisms to perform active/standby switchover to
achieve transmission reliability.
Protocol
Layer
Target
Transmission
Reliability
Transmission Detection
Redundancy
Mechanism
Detection Mechanism Detection Period
Application
layer
OMCH OMCH backup OM heartbeat (enabled by default) 3s to 5s
Transport
layer
S1-U/X2 None
SCTP heartbeat and retransmission (enabled by default) 1s to 60s, configurable
Static GTP-U echo detection (disabled by default)
100 ms level
Static GTP-U echo detection (enabled by default)
Network
layer
Route and link IP route backup
BFD detection (disabled by default) 10 ms to 1000 ms, configurable
IPPM QoS detection, which complies a proprietary protocol and used for
routine O&M with higher accuracy and without affecting services (disabled
by default)
100 ms to 10000 ms, configurable
TWAMP QoS detection, which complies a standard protocol and used for
deployment and routine O&M with services affected
(disabled by default)
UDP packet injection QoS detection, which complies with a proprietary
protocol and is used for deployment with large traffic
(disabled by default)
ICMP ping (disabled by default) 1000 ms to 10000 ms, configurable
Route tracing (disabled by default)
Data link
layer
Link and
Ethernet port
Ethernet Port
Trunk
IEEE 802.3ah detection (disabled by default) 3s
IEEE 802.1ag detection (disabled by default) 1s
Physical
layer
Port None Physical port detection (enabled by default) ms level

5G NSA Security Design
 5G NSA networking depends on LTE networks. Refer to the requirements of operator's existing networks for security
networking policies. No additional design is required.
 Transport layer security of 5G is the same as that of LTE.
 The following table describes 5G transport layer security policies.
Transport Plane Security Feature Protective Measure
OM
SSL (mandatory) and
IPsec (optional)
User service data encryption, bidirectional authentication, and anti-tampering
Port security
management
local access monitoring and alarm reporting
Local Ethernet port enabling and disabling
When SCTP links or PPP links are disconnected, the link disconnection causes are
reported. When links are recovered, the number of reconnection attempts is reported.
CLK IPsec (optional) User service data encryption, bidirectional authentication, and anti-tampering
X2 IPsec (optional) User service data encryption, bidirectional authentication, and anti-tampering
S1-U IPsec (optional) User service data encryption, bidirectional authentication, and anti-tampering
Device access
802.1x access
authentication (optional)
Access authentication (The RADIUS server must be configured with the Huawei CA
certificate and base station ESN.)
 5G networking evolution analysis
Transport security policies are irrelevant to RATs but are related to operator's security requirements. In the future, the
security networking design solution for 5G SA sites will not change theoretically.

Network Design Item Sub-Item Planned Value
OM design Sites, cells, and parameters Network planning and optimization
OMCH
Co-EMS with LTE; OM IP address: 11.0.0.10 (site 1)/11.0.0.11 (site 2); Base station interface address: 20.0.0.10 (site 1)/20.0.0.11 (site 2) VLANs and routes are planned.
SSL is configured on the U2020. Whether to use OMCH backup is determined based on operator's existing networks.
Time source GPS
Clock synchronization design Clock source Specific GPS parameters are configured based on operator's existing networks.
IP interconnection design
Option 3X networking
S1-U/X2
S1/X2 logical address: 12.0.0.10 (site 1)/12.0.0.11 (site 2); EPC S1-U address
Base station interface address: 20.0.0.10 (site 1)/20.0.0.11 (site 2)
Co-VLAN of Service links (route planning); IP route backup (designed based on existing networks)
Ports described in the communication matrix. Ensure that the ports have been enabled on the firewall.
Interface bandwidth
calculation
2618 Mbit/s in non-secure networking scenarios where there are 400 users and the rate of traffic transferred to eNodeBs to traffic transferred to gNodeBs is 10%.
QoS design Configured according to recommended QoS
Reliability Configured based on operator's existing networks
Security Non-secure networking is used, 802.1x access authentication is not required, and IPsec is not deployed.
Case 1: 5G NSA Networking Design
Note: The U2000 in the left figure has been renamed
U2020.

Base Station
1. In the option 3X networking, a gNodeB connects to a 10 GE optical port on the PTN at the access stratum using a single 10 GE fiber optic cable. The port works at 10000 Mbit/s
in full-duplex mode.
2. The gNodeB considers the PTN L3 address as the gateway.
3. The PTN must support DHCP relay to support PnP deployment.
4. SCTP dual-homing is used between the eNodeB and the MME in the new network.
Bearer network
1. Access ring: The rate of the connection to the base station is 10 Gbit/s and the rate of the connections between transport equipment is 50 Gbit/s or 100 Gbit/s. In long-term
commercial use scenarios, a 50 Gbit/s access ring is connected to 8 to 10 base station, and a 100 Gbit/s access ring is used in scenarios with BBUs stacked.
2. Aggregation ring: One aggregation ring with 10 access rings for long-term commercial use and two to three new test networks
3. Core ring: N x 200 Gbit/s or 400 Gbit/s is used for long-term commercial use. The number of core aggregation rings depends on the base station distribution.
Example of calculating the peak bandwidth of a single gNodeB (calculated based on the total traffic of the three sectors among which the single-cell or single-UE peak
rate in off-peak hours is used for one sector and peak rates in busy hours are used for the others)
Scenario
Bandwidth of a Single
Base Station
Calculation
Average cell rate Spectrum bandwidth x Average spectral efficiency x Downlink subframe ratio = 100 Mbit/s x 17.7 x 75%
Peak rate of a single user 4.6 Gbit/s
1 x Peak rate of a single user x Transmission efficiency + 2 x Average cell rate x Transmission efficiency = 1.5 x 1.1 + 2 x 100
Mbit/s x 17.7 x 75% x 1.1
Peak rate of a single cell 8.5 Gbit/s
1 x Peak rate of a single cell x Transmission efficiency + 2 x Average cell rate x Transmission efficiency = 5 x 1.1 + 2 x 100 Mbit/s
x 17.7 x 75% x 1.1
Case 2: 5G NSA Trial Network Transport Solution and Bandwidth Calculation

Thank you

Clock Synchronization
The transport network needs to be synchronized with clock reference signals, that is, synchronization sources, to ensure that
transmitted information is not lost or distorted. A complete and effective synchronization mechanism is essential for a transmission
network to work normally. The gNodeB needs to obtain the precise frequency from the clock signal provided by the transport
network. Without clock synchronization, the gNodeB cannot perform handovers. Clock synchronization is classified into frequency
synchronization, phase synchronization, and time synchronization.
Frequency synchronization: Two signals have the same number of bursts in
the same period. Frequency synchronization has nothing to do with the sequence
of burst occurrence and the start and end time of each burst.
Phase synchronization: Two signals have the same frequency and the same
start and end time of each burst. Phase synchronization has nothing to do with
the sequence of burst occurrence.
Time synchronization: Two signals have the same frequency, phase, and burst
sequence. The origin of the timescale for a signal needs to be synchronized with
the UTC. Therefore, time synchronization implies synchronization in absolute
time. The UTC is a universal timing standard, in which the atomic clock is
maintained accurately to ensure time synchronization across the world, with the
precision to microseconds.

Technical_Training_of_5G_Networking_Design.pptx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Technical_Training_of_5G_Networking_Design.pptx

Similar to Technical_Training_of_5G_Networking_Design.pptx (20)

Recently uploaded

Recently uploaded (20)

Technical_Training_of_5G_Networking_Design.pptx