SRAN13.1&15.0 NSA Networking Based On EPC-20180905
SRAN13.1&15.0 NSA Networking Based On EPC-20180905
After completing this course, you will be able to understand the basic principles, application scenarios,
and specifications of the NSA Networking based on EPC feature, and be able to site-design,
configure, commission, and verify the feature by referring to related documents.
NR NSA NR SA Full-IMT2020 NR
(non-independent RAT) (independent RAT) • Full 5G standard and mMTC capability
definition
• NSA definition, eMBB • Definitions of NGCN and NR • Enhanced capability definition: Soft
NR service objectives • NSA, SA architecture
Numerology, frame AI/D2D/D-TDD/Flexible Duplex
• structure (eMBB/URLLC)
eMBB
• URLLC • Native M-MIMO & Expected in 2019 H2
• mMTC waveform Launch of NSA terminals
5G New RAT
SRAN13.1 is the first version of NSA Networking based on EPC. In SRAN15.0, interference coordination is added and mobility
management is enhanced.
Legend
Option 3a Option 7a
Control Plane EPC NC EPC NC Option 4a
S1-U NC
S1
EPC
Ng Ng-U
X2-C
LTE NR
User Plane eLTE Xn-C NR
eLTE NR
Feature Planning
MN, SN;
• EN-DC specifications: 1 MeNB+1 SgNB Step 2: GAP-assisted measurement control is performed.
• Intra-RAT CA specifications: When a UE needs to measure the quality of inter-frequency channels, GAP-
MCG, SCG;
DL: LTE support 5CC, NR support 2CC(Only intra-band CA were supported in NR side). assisted measurement needs to be started.
Pcell,
UL: LTEPscell, Scell;2CC(Only intra-RAT CA were supported in NR side)
1CC, NR C-BAND Step 3: The UE sends an event B1 measurement report to the
MeNB.
MeNB carrier management
Step 4: After receiving the measurement report, the MeNB
• PCC anchor selection(for UE in RRC_CONNECTED status, RRC_IDLE status, duplex-
decides to trigger an SgNB Addition (PSCell configuration)
mode-priority-based PCC anchoring selection, and load-based PCC anchoring selection)
procedure.
• SCC carrier management (SCell configuration, SCell change, enhanced SCell
If multiple cells are reported in the measurement report, the MeNB adds the
selection, SCell activation, SCell deactivation, and SCell removal)
strongest RSRP cell of SgNB reported in the measurement report.
3GPP.TS.37.3400
SCG
SCG_SPLIT_BEARER DlDataPdcpSplitMode UlDataSplitThreshold = Infinity
SCG_ONLY SCG
( Option 3X ) ( NR QCI level parameter ) Or Other
SCG_AND_MCG NsaDcDefaultBearerMode NsaDcUeMcgUlAmbrRatio UlDataSplitThreshold LTE parameter
• Cross-modulation interference: LTE-NR uplink concurrency produces cross-modulation • Cross-modulation interference avoidance solution
interference, affecting LTE downlink reception. Subframe-level TDM: After LTE-NR subframes are aligned, LTE and NR uplink subframes are scheduled
• Harmonic interference: LTE uplink secondary harmonic interferes NR downlink at different time.
reception.
NR S subframes are used for SRS or PRACH transmission, the proportion of UpPTS is small (about 0.07 ms),
and LTE U subframes and NR S subframes can be transmitted simultaneously.
• Secondary harmonic interference avoidance solution
LTE channels are yielded to NR common channels (PBCH/PSS/SSS and common PDCCH) in
Cross-modulation interference Harmonic interference scheduling.
Slot
Customer Benefits
• Cross-modulation interference avoidance: LTE channels are yielded to NR
LTE common channels are not affected (ensuring UE mobility). common channels in uplink scheduling
PRB
Single-user downlink performance improves by 30%. (converted to the frequency range that
• Harmonic interference avoidance: NR common channels are not affected (ensuring generates secondary harmonic
interference).
UE mobility). Time-frequency positions of NR
common channels
MME SGW
S1-U
S1-C S1-U
X2-C
eNodeB gNodeB
X2-U
In the EN-DC architecture, the eNodeB/gNodeB supports only the EN-DC X2 self-management includes the following functions:
configuration of the X2/S1-U interface in the endpoint configuration X2 Self-Setup
mode.
The eNodeB sets up EN-DC services to trigger X2 self-setup. X2 self-setup involves manual
• The logical interface between the eNodeB and the gNodeB is the configuration of the peer IP addresses and automatic configuration of the peer IP addresses.
X2 interface. The X2 interface includes the X2 interface on the Currently, only X2 self-setup over U2020 is supported, and the eNodeB and gNodeB must be
control plane (X2-C) and X2 interface on the user plane (X2-U). managed by the same U2020.
The X2 control plane is based on the SCTP (Stream Control X2 Self-Update
Transmission Protocol) and the user plane is based on the GTP-U During network operation, the IP address or operator information (MNC, MCC, or Global
(GPRS Tunneling Protocol-User Plane). eNodeB ID) of the peer eNodeB may be modified. When the X2 interface is faulty, the X2 self-
• The user-plane interface between the gNodeB and the S-GW is setup procedure is triggered again.
S1-U. S1-U is based on the GTP-U. In the Option 3X architecture, X2 Self-Removal
the S1-U interface between the gNodeB and S-GW must be The eNodeB proactively releases the X2-U links that are not used or disconnected for a long
configured. time.
S1-U self-setup
S1-U self-setup between the gNodeB and S-GW is implemented only in
the Option 3X architecture and not in the Option 3 architecture.
HUAWEI TECHNOLOGIES CO., LTD. Page 13
Contents
Feature Planning
Version Positioning
1. In 18B and 19A, NSA Networking based on EPC is a basic function of 5G NSA networking.
2. NSA Networking based on EPC is a multi-mode basic feature. It is not sold independently and no license is planned.
00 FDD Multi-mode Basic Features MRFD-131122 NSA Networking based on EPC (LTE FDD)
00 TDD Multi-mode Basic Features MRFD-131132 NSA Networking based on EPC (LTE TDD)
00 NR Multi-mode Basic Features MRFD-131162 NSA Networking based on EPC (NR)
00 FDD Multi-mode Basic Features MRFD-131121 LTE and NR X2 Interface Self-Configuration (LTE FDD)
00 TDD Multi-mode Basic Features MRFD-131131 LTE and NR X2 Interface Self-Configuration (LTE TDD)
00 NR Multi-mode Basic Features MRFD-131161 LTE and NR X2 Interface Self-Configuration (NR)
parameter
NR
NSA DlDataScgSplitBearerMode Downlink Data SCG Split Bearer Mode SCG_AND_MCG SCG_ONLY
NR
Sample: gNodeB
Networking
based on EPC
MOD NRCellNsaDcConfig UlDataSplitPrimaryPath Uplink Data Split Primary Path MCG SCG
Sample:
parameter
NR
19A Option3x
CQI level
parameter
LTE parameter
DC scenario
selection &
data split
configuration
LTE -> NR
Neighbor
Average number of UEs that treat the local cell as their PCell in the N.User.NsaDc.PSCell.Avg Average number of LTE-NR NSA DC UEs using the current cell as PSCell
L.Traffic.User.NsaDc.PCell.Avg
LTE-NR NSA DC state
N.NsaDc.SgNB.Add.Att Number of SgNB addition requests in the LTE-NR NSA DC scenario
Total traffic volume offloaded from UEs in the PCell at the PDCP
L.Thpt.bits.DL.McgSplit.MeNB N.NsaDc.SgNB.Add.Succ Number of successful SgNB additions in the LTE-NR NSA DC scenario
layer to the MeNB during LTE-NR NSA DC 3C offloading
Number of inter-SgNB PSCell change requests in the LTE-NR NSA DC
N.NsaDc.InterSgNB.PSCell.Change.Att
Total traffic volume offloaded from UEs in the PCell at the PDCP scenario
L.Thpt.bits.DL.McgSplit.SgNB
layer to the SgNB during LTE-NR NSA DC 3C offloading Number of successful inter-SgNB PSCell changes in the LTE-NR NSA DC
N.NsaDc.InterSgNB.PSCell.Change.Succ
scenario
Total uplink MeNB traffic volume received by UEs in the PCell from Number of intra-SgNB PSCell change requests in the LTE-NR NSA DC
L.Thpt.bits.UL.McgSplit.MeNB N.NsaDc.IntraSgNB.PSCell.Change.Att
the PDCP layer of the MeNB during LTE-NR NSA DC 3C offloading scenario
Number of successful intra-SgNB PSCell changes in the LTE-NR NSA DC
N.NsaDc.IntraSgNB.PSCell.Change.Succ
Total uplink SgNB traffic volume received by UEs in the PCell from scenario
L.Thpt.bits.UL.McgSplit.SgNB
the PDCP layer of the MeNB during LTE-NR NSA DC 3C offloading N.NsaDc.SgNB.Rel Total number of SgNB releases in the LTE-NR NSA DC scenario
Total number of SgNB addition attempts for UEs that treat the local N.NsaDc.SgNB.AbnormRel Number of abnormal SgNB releases in the LTE-NR NSA DC scenario
L.NsaDc.SgNB.Add.Att
cell as their PCell in the LTE-NR NSA DC state
N.NsaDc.DRB.Add.Att Number of DRB addition requests for LTE-NR NSA DC UEs on the SgNB
Total number of successful SgNB additions for UEs that treat the
L.NsaDc.SgNB.Add.Succ N.NsaDc.DRB.Add.Succ Number of successful DRB additions for LTE-NR NSA DC UEs on the SgNB
local cell as their PCell in the LTE-NR NSA DC state
Total number of SCG change attempts for UEs that treat the local N.NsaDc.DRB.Rel Number of DRB releases for LTE-NR NSA DC UEs on the SgNB
L.NsaDc.SCG.Change.Att
cell as their PCell in the LTE-NR NSA DC state N.NsaDc.DRB.AbnormRel Number of abnormal DRB releases for LTE-NR NSA DC UEs on the SgNB
N.PDCP.DL.X2U.TrfPDU.TxPackets Number of downlink PDCP PDUs transmitted over the X2 interface in a cell
Total number of successful SCG changes for UEs that treat the
L.NsaDc.SCG.Change.Succ
local cell as their PCell in the LTE-NR NSA DC state N.PDCP.UL.X2U.TrfPDU.RxPackets Number of uplink PDCP PDUs received over the X2 interface in a cell
N.PDCP.Vol.DL.X2U.TrfPDU.Tx Traffic of downlink PDCP PDUs transmitted over the X2 interface in a cell
Total number of SgNB removal attempts for UEs that treat the local N.PDCP.Vol.UL.X2U.TrfPDU.Rx Traffic of uplink PDCP PDUs received over the X2 interface in a cell
L.NsaDc.SgNB.Rmv.Att
cell as their PCell in the LTE-NR NSA DC state
Total number of SCG-related failures for UEs that treat the local cell
L.NsaDc.ScgFailure
as their PCell in the LTE-NR NSA DC state
Divider
③ New direct-connected
CPE 100G CPRI optical cable ④ New BBU5900 ⑨ Added RAN OSS
5G
TUE
XGE electrical interface
interconnection
RRU(TDD1900) New CN OSS
4G ⑧ Added CN OSS
TUE
BBU39X0(LTE)
RRU(TDD2600) NG Core
⑦ NG Core
⑧ New PLMN (5G)
Anchor eNodeB
MME/SGSN S-GW/P-GW/GGSN
New EPC+
5G-Uu
gNodeB
NSA UE
MME (old): does not support NSA; MME (new): supports NSA.
Function switch on the eNodeB side: CNOPERATOR.OperatorFunSwitch: DCN_SUPPORT_SWITCH
The NAS message redirection procedure is as follows:
1. Upon the access of a UE, the eNodeB selects an MME for the UE based on access information and sends an Initial UE Message to the MME.
2. If an NSA UE accesses the MME (old) or an LTE-only UE (including a non-subscription NSA-capable UE) accesses the MME (new), it triggers an NAS message redirection
procedure by sending a Reroute NAS Request message to the eNodeB. This message contains the following IEs:
- original RAN message, which is a complete packet data unit (PDU) received from the RAN. It contains the original NAS request message and all RAN IEs.
- MME Group ID, which determines the next serving DCN.
- Additional GUTI, which helps the eNodeB to select an MME.
- UE Usage Type, which is optional. Its value is specified upon UE subscription and sent by the eNodeB to the next MME.
3. The eNodeB selects a new MME based on the IEs MME Group ID and Additional GUTI carried in the Reroute NAS Request message.
4. The eNodeB sends an Initial UE Message to the newly selected MME. This message contains the IEs MME Group ID and UE Usage Type (which is available only if it is
contained in the Reroute NAS Request message). Based on the IE MME Group ID, the new MME determines that this is an Initial UE Message sent after a triggered
redirection. Therefore, the MME does not forward this message but processes or rejects it.
MME selection based on DECOR requires wireless support (starting from 18A) and CN support (starting from 19A).
Intra-site DC: L/NR co-MPT (supported in 19A) Intra-site DC: CI interconnection (not recommended)
Co-PDCP
RL RLC
C(N (L) Split Bearer 5900
R) TRAN UBBP (NR)
PDCP (L)
RLC RLC
(NR) (L) PDCP (NR) UMPT(LNR
)
TRAN
Split Bearer
Intra-site DC based on transmission interconnection (recommended) Inter-site DC: This scenario supports only the X2 transmission
interconnection solution (< 20 ms).
LSW
LSW
LSW