02 5G Network Protocols ISSUE1.00
02 5G Network Protocols ISSUE1.00
www.huawei.com
1. NR Network Architecture
2. 5G Network Interfaces and Protocol Stack
3. NR Air Interface Protocol Stack
NGC
AMF/SMF/UPF AMF/SMF/UPF
NG-C/U
NG-C/U
NG-
C/U
NG-
C/U
Xn NG-RAN
gNB gNB
X
n
X
n
gNB
NGC: It refers to the next-generation core network where the AMF, UPF, and SMF are deployed.
3GPP has confirmed the Service Based Architecture (SBA) led and
proposed by China Mobile as the basic architecture of 5G core network.
The interfaces between 2G, 3G, and 4G NEs must be predefined and configured with
dedicated protocols. These interfaces can be used only between two types of NEs and
cannot be invoked.
N12 N8 N10
N14 N15
N1 N2 N4
UE (R)AN N3 UPF N6 DN
N9
AMF: UPF:
Termination of uplink NAS signaling Anchor point for mobility management user
NAS signaling security plane
AS security control PDU session node
Signaling node for interoperability in 3GPP Downlink data routing and forwarding
systems
User-plane data detection and policy execution
Idle UE reachability management
Uplink service type identification
UE location area management
UE access authentication QoS-based packet filter and processing
SMF:
Session management UPF control
CP and UP UP CP and UP
CP and UP
S1 NG
CP and UP CP and UP
LTE eNB gNB eLTE eNB gNB
X2 Xn
S1
X2
eNodeB gNodeB
User plane
4G/5G dual-mode UE
Control plane
Option 3 and option 3a: The legacy LTE EPC network is reused.
EPC EPC
S1-C S1-U S1-C S1-U S1-U
Option 3 Option 3a
Option 3: To control the NR bandwidth, the LTE eNodeB needs to be
upgraded to forward mass data on the 5G user plane.
EPC
S1-C S1-U S1-U
NGC NGC
NG-C NG-U NG-C NG-U NG-U
eLTE eNB
New RAN
gNB
Xn Xn
Xn
eLTE eNB gNB
NGC: It refers to the next-generation core network where the AMF, UPF, and SMF are deployed.
NGC NGC
NG-C NG-U NG-U NG-C NG-U
Option 4 Option 4a
Option 4: The LTE eNodeB is upgraded to forward mass data on
the 5G user plane.
NGC NGC
NG-C NG-U NG-C NG-U
Option 5 Option 2
Option 5: The LTE eNodeB is upgraded to support the control plane and user plane of the NGC.
Option 2: The control plane and user plane of the 5G gNodeB access the NGC.
1. NR Network Architecture
UE mobility management
The NG-C interface currently supports the SCTP and GTP-U protocols.
GTP-U
SCTP
UDP
IP
IP
Data link layer
Data link layer
Physical layer Physical layer
NG-C NG-U
Xn-U Xn-U
eLTE eNB gNB gNB
Xn-C Xn-C
The transport layer protocol of the Xn control plane uses SCTP, the application layer
protocol stack uses XnAP, and the user plane supports at least the GTP-U protocol stack.
GTP-U
SCTP
UDP
IP
IP
Data link layer Data link layer
Xn-C Xn-U
Service data
PDCP PDCP
MAC MAC
PHY Layer 1
PHY
MCG bearer Split bearer SCG bearer MCG bearer SCG split
bearer
S1 S1 S1 S1
Xx Xx
PDCP PDCP NR PDCP PDCP NR PDCP NR PDCP
1. NR Network Architecture
2. 5G Network Interfaces and Protocol Stack
3. NR Air Interface Protocol Stack
RRC RRC
PDCP PDCP
PDCP PDCP
RLC RLC
RLC RLC
MAC MAC
MAC MAC
Layer 3: Provides air interface services for RRC signaling and user plane data.
Layer 2: Differentiates Layer 3 data and provides different services.
Layer 1 (physical layer): Provides radio resources and physical layer processing for higher-layer data.
NR RRC_CONNECTED
Resume / Release
with Suspend
Establish /
Release
NR RRC_INACTIVE
Release
NR RRC_IDLE
UE NB UPF
PDU Session
Radio Bearer NG-U Tunnel
QoS Flow
QoS Flow
Radio Bearer
QoS Flow
Radio N3
The NGC sets up one or more PDU sessions for each UE. One or more QoS flows may
be established in a PDU session. The NG-RAN establishes different DRBs for the QoS
flows that have QoS requirements, or map QoS flows in the same PDU session to a
DRB.
The 5G QoS model is created based on the QoS flow. The QoS flow is the best
granularity for differentiating QoS differences in a PDU session, and uniquely
identified by the QFI. Each QoS flow has its associated QoS attribute set.
The UE and UPF associate the services with the QoS flows through the packet filter
set. The RAN maps the QoS flows to the DRBs to ensure the service quality.
Data Oct 1
….
Oct N
Data Oct 2
...
Data Oct N
SN addition Decompression
Header compression
Packets associated to
a PDCP SDU
Packets associated to
a PDCP SDU
associated to a
associated to a
Packets not
PDCP SDU
Reordering and repeated
Packets not
PDCP SDU
Integrity protection discard
Length Description
12 UM DRBs, AM DRBs, and SRBs
HFN PDCP SN
Integrity protection can be used for SRBs and DRBs and cannot be used for PDCP
control PDUs.
Restoration of raw data focuses on key consistency of the sender and receiver.
1 ⊕ 0 1
1 ⊕ 0 ?
1 ⊕ 1 0 0 ⊕ 1 ?
0 ⊕ 0 0 0 ⊕ 0 ?
0 ⊕ 1 1 1 ⊕ 1 ?
Sender Receiver
KEYSTREAM KEYSTREAM
BLOCK BLOCK
Sender Receiver
Input and output procedures of user plane data encryption and decryption
PDCN SN
association
discardTimer startup
Next_PDCP_TX_SN
PDCP Header compression
SN
Encryption and
integrity protection NO:Next_PDCP_TX_SN++
YES:
Next_PDCP_TX_SN >
Next_PDCP_TX_SN Next_PDCP_TX_SN=0
Maximum_PDCP_SN
TX_HFN++
PDCP PDU
Reception of
Received PDCP SN PDCP SDU
underlying data
PDCP entity
Received data
Received PDCP SN
COUNT
HFN calculation
according to rules
Decryption
RX_HFN
Header
decompression
Locally stored data
Next_PDCP_RX_S
N;
RX_HFN;
Maximum_PDCP_S
N
...
When the air interface quality is poor and a large number of packets are lost, how to set
the PDCP SN length to resolve the HFN synchronization problem?
UE/GNB GNB/UE
Radio interface (Uu)
TM-RLC channel TM-RLC channel
Transmittin Receiving
g TM-RLC TM-RLC
Transmission entity entity
buffer
BCCH/PCCH/CCCH BCCH/PCCH/CCCH
DTCH DTCH
Reception
buffer
DTCH/DCCH DTCH/DCCH
BYTE_WITHOUT_POLL ≥ pollByte
After the condition is met, the AM RLC entity at the sender side
performs the following operations:
Initiating a query of the P position 1 of the RLC data PDU to the receiver.
After receiving the RLC packet carrying the P identifier, the receiver needs
to feed back the status report, but the following timer requirements must
be met:
t-StatusProhibit timer: This timer specifies the interval for sending status
reports.
After receiving the status report, the sender stops the t-PollRetransmit
timer.
Is packet
retransmission
required?
Yes
No
No Is the number of
retransmission retransmissions less than
maxRetxThreshold?
Ye
s
Does the underlying resource
size meet the requirement of
PDU size?
Yes
Segmentation/R Retransmission
e-segmentation
Data PDUs
TMD PDU
UMD PDU
AMD PDU
Control PDUs
STATUS PDU
Data Oct 1
...
Oct N
SI R R R R R R Oct 1
Data Oct 2
...
Oct N
SI SN Oct 1
SO Oct 2
SO Oct 3
Data Oct 4
...
Oct N
SI R R SN Oct 1
SN Oct 2
SO Oct 3
SO Oct 4
Data Oct 5
...
Oct N
D/C P SI R R SN Oct 1
SN Oct 2
SN Oct 3
SO Oct 4
SO Oct 5
Data Oct 6
...
Oct N
Value Description
00 Data field contains all bytes of an RLC SDU.
01 Data field contains the first segment of an RLC SDU.
10 Data field contains the last segment of an RLC SDU.
11 Data field contains neither the first nor last segment of an RLC SDU.
Data/Control (D/C)
Indicates the RLC PDU type.
Value Description
0 Control PDU
1 Data PDU
Value Description
0 Status report not requested
1 Status report is requested
What are the functions of the t-PollRetransmit, t-Reassembly, and t-StatusProhibit timers?
Demultiplexing/Multiplexing
Ctrl
Concatenation and segmentation of the RLC PDUs. In the NR network, the RLC
layer no longer provides the concatenation function of RLC SDUs.
Abbreviatio
Transport Channel Downlink Uplink
n
Broadcast channel BCH X
The logical channels on the NR network are the same as those on the LTE network.
Control Traffic
Logical Channel Abbreviation
Channel Channel
Broadcast control channel BCCH X
RRC/NAS IP Layer 3
packet
SDAP
PDCP PDCP
RLC RLC
Layer 2
Logical
channel MAC MAC
Transport
channel PHY PHY Layer 1
Physical
channel gNodeB
UE
Secondary uplink
scheduling f or UEs
based on logical
channel priorities
On the uplink, the UE applies for scheduling through the SR or random access procedure,
and reports the BSR and PHR. The gNodeB uses the scheduling algorithm for UE
scheduling information output and sends the scheduling information to the UE through
the PDCCH. The UE then obtains its scheduling information through the PDCCH and RNTI.
Value RNTI
0000 N/A
0001–FFEF RA-RNTI, Temporary C-RNTI, C-RNTI, CS-RNTI,
TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-
RNTI, and TPC-SRS-RNTI
FFF0–FFFD Reserved
FFFE P-RNTI
FFFF SI-RNTI
Uplink authorization.
After receiving the initial random access preamble from the UE, the
gNodeB responds to the random access. The RAR message carries
the following information:
Timing Advance
UL Grant Oct 2
Command
UL Grant Oct 3
UL Grant Oct 4
The UE sends a BSR to notify the gNodeB of how many data packets to be
sent. The BSR has two formats:
A short BSR PDU carries the buffer report of a logical channel group.
A long BSR carries the buffer reports of multiple logical channel groups.
following table lists the mapping between the buffered data and the buffer indices.
To ensure data transfer reliability, the receiver uses CRC to verify data correctness and uses
the HARQ retransmission mechanism to ensure data transfer reliability. HARQ is classified
into the following types based on the retransmission time:
Synchronous HARQ: Retransmission of an HARQ process occurs at fixed time, and the
receiver knows the time in advance.
Asynchronous HARQ: Retransmission of an HARQ process may occur at any time, and
the receiver does not know the time in advance.
HARQ can be classified into non-adaptive HARQ and adaptive HARQ based on whether the
data characteristics change during retransmission. Different from the LTE network, the NR
network currently uses asynchronous HARQ in both uplink and downlink.
PUSCH
PDCCH scheduling
PDCCH PDSCH retransmission
PUSCH/PUCCH
Downlink LCID
Channel coding
Modulation
The receiver uses modulo-2 binary division to divide A+B by CRC to generate the
polynomial. If the result is not 0, an error occurs during frame transmission.
There are multiple CRC lengths for the uplink and downlink traffic
channels in the NR. The CRC length is usually 24 bits.
g CRC24A D [ D 24 D 23 D18 D17 D14 D11 D10 D 7 D 6 D 5 D 4 D 3 D 1]
The maximum number of input bits for the LDPC code is 8448, as
specified in 3GPP TS 38.212.
QPSK QPSK
16QAM 16QAM
Uplink 64QAM 64QAM
256QAM
QPSK QPSK
16QAM 16QAM
64QAM 64QAM
Downlink 256QAM 256QAM
Downlink Uplink
CSI-RS
PUSCH Physical downlink shared channel Used to carry uplink user data.
Uplink: CP-OFDM/DFT-
s-OFDM
SCMA
PDMA
...
Timeslot
Physical channels
and signals
Basic time
unit: Ts
What is the size of the data PDUs after the PDCP layer processes
them?
What is the size of the data PDUs after the RLC layer processes them?
What is the data size of data PDUs after the MAC layer and physical
layer process them?
Item NR LTE
The SDAP protocol is added to the
SDAP No SDAP protocol
user plane.
PDCP layer
PDCP layer
PDCP reordering and encryption integrity
encryption integrity protection
protection
AM/TM/UM mode AM/TM/UM mode, ARQ function, RLC PDU
RLC
ARQ function submission in sequence, and reordering