Professional Documents
Culture Documents
SRAN13.1 NSA Networking Based On EPC
SRAN13.1 NSA Networking Based On EPC
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 install, configure,
commission, and verify the feature by referring to related documents.
SRAN13.1 is the first version of the NSA Networking based on EPC feature. The following basic functions are planned:
Carrier management Uplink power control
Mobility management eNodeB and gNodeB interconnection modes
Data split (UL/DL)
Legend
Option 3a Option 7a
EPC NC EPC NC Option 4a
Control Plane S1
S1-U
EPC NC
Ng Ng-U
X2-C
LTE NR
eLTE Xn-C NR
eLTE NR
User Plane
NR Non-Standalone NR Standalone
Phase 1.1 Phase 1.2 (new core)
Note: Option 2/5 is NR/eLTE standalone.
For LTE- NR DC, Huawei currently focuses on Option 3/3x NSA deployment.
HUAWEI TECHNOLOGIES CO., LTD. Page 4
Contents
Feature Planning
Same as LTE carrier management. For details, see Carrier Aggregation Feature Parameter
Description.
Secondary node release The UE moves out of the gNodeB coverage area.
3GPP.TS.37.3400
Split at LTE PDCP layer (MCG Split Bearer) Split at NR PDCP layer (SCG Split
Bearer)
Parameter settings for downlink data split
• [LTE Parameter] NsaDcDefaultBearerMode: specifies whether data split is performed at the LTE PDCP
layer or NR PDCP layer.
• [LTE Parameter] DlDataMcgSplitBearerMode: specifies the LTE PDCP data split mode.
SCG_AND_MCG: dynamic data split
MCG_ONLY: distributes data only to the MCG.
SCG_ONLY: distributes data only to the SCG. Solution:
• [NR Parameter] DlDataScgSplitBearerMode: specifies the NR PDCP data split mode. 1. Data distribution to the PDCP anchor is preferred.
SCG_AND_MCG: dynamic data split 2. The X2 transmission delay is supplemented so that data transmitted
MCG_ONLY: distributes data only to the MCG. from the MeNB and SgNB reaches the UE simultaneously.
3. Packets are sent in turn based on the ratio of the RLC perceived
SCG_ONLY: distributes data only to the SCG.
rate.
UE Uplink data
UlDataPrimaryPath UlDataSplitThreshold
path
1. The MAC/RLC entities of the master or secondary base Null MCG
stations corresponding to the UE are independent. MCG Non-null, UL data volume < UlDataSplitThreshold MCG
2. Uplink data scheduling and BSR reporting are independent. Non-null, UL data volume > UlDataSplitThreshold MCG+SCG
3. On the UE side, the PDCP entity is shared by NR and LTE.
Null SCG
4. The UE performs uplink data split according to the
SCG Non-null, UL data volume < UlDataSplitThreshold SCG
configuration command delivered by the master base
Non-null, UL data volume > UlDataSplitThreshold MCG+SCG
station.
For example, in the Option 3X architecture, uplink and downlink For example, UP data is carried on the NR side in the Option 3X architecture
data split is implemented based on parameter settings: based on the uplink and downlink data split policies.
DL data carried on NR: Set DlDataMcgSplitBearerMode to DL data carried on NR: Set DlDataScgSplitBearerMode to SCG_ONLY.
SCG_ONLY. UL data carried on NR: Set UlDataPrimaryPath to SCG and UlDataSplitThreshold to
UL data carried on LTE: Set UlDataPrimaryPath to MCG and Null.
UlDataSplitThreshold to Null.
Intra-site DC: L/NR co-BBU [co-MPT is not supported Inter-site DC: This scenario supports only the X2
in 18B, supported in 19A] transmission interconnection solution (< 20 ms).
Co-PDCP
RLC RLC LSW
(NR (L) Split Bear 5900 LSW
) TRAN UBBP(NR)
UBBP(L) UBBP(L)
PDCP(L)
RLC RLC
PDCP(NR) UMPT ( L
(NR (L) )
UMPT(NR)
) TRAN
Split Bear
• X2 data between L and NR is exchanged inside the BBU • X2 data between L and NR is exchanged by network.
1.
2.
X2 setup procedure
1. SgNB Addition Request 1. The eNodeB sends an SgNB Addition Request message to
the gNodeB. The message carries the S1-U address
2. SgNB Addition Request ACK information on the S-GW side. The gNodeB can send
uplink data based on the information.
2. The gNodeB sends an SgNB Addition Request ACK
UE Access NR message to the eNodeB. The message carries the S1-U
Procedure address information on the gNodeB side.
3. eRAB Modification Indication 3. The eNodeB sends an eRAB Modification Indication
message to the MME. The message carries the S1-U
4. Bearer Modification address information on the gNodeB side. The S-GW can
eRAB Modification Confirm
send downlink data based on the information. (no this
message in option 3)
DL data 4. The MME exchanges messages with the S-GW to notify
the S-GW of the S1-U address information corresponding
to the bearer on the RAN side.
5. The MME sends an eRAB Modification Confirm message
to the eNodeB.
Feature Planning
2. NSA Networking based on EPC is a multi-mode basic feature. It is not sold independently and no license is planned.
00 FDD Multimode Basic Feature MRFD-131122 NSA Networking based on EPC (LTE FDD)
00 TDD Multimode Basic Feature MRFD-131132 NSA Networking based on EPC (LTE TDD)
00 NR Multimode Basic Feature MRFD-131162 NSA Networking based on EPC (5G NR)
00 FDD Multimode Basic Feature MRFD-131121 LTE and NR X2 Interface Self-Configuration (LTE FDD)
00 TDD Multimode Basic Feature MRFD-131131 LTE and NR X2 Interface Self-Configuration (LTE TDD)
00 NR Multimode Basic Feature MRFD-131161 LTE and NR X2 Interface Self-Configuration (5G NR)
Feature Activation (the DC feature is enabled on both the LTE and NR sides)
• LTE side: Run the following MML command: MOD NSADCMGMTCONFIG, selecting the NSA_DC_CAPABILITY_SWITCH value to the
NsaDcAlgoSwitch parameter.
• NR side: Run the MOD NRCELLALGOSWITCH command with the NsaDcSwitch parameter set to ON.
• LTE side: Run the MOD NSADCMGMTCONFIG command with NsaDcDefaultBearerMode set to MCG_SPLIT_BEARER.
• LTE side: Run the MOD NSADCMGMTCONFIG command with NsaDcDefaultBearerMode set to SCG_SPLIT_BEARER.
Total number of SCG-related failures for UEs that treat the local Number of abnormal DRB releases for LTE-NR NSA DC UEs on the
L.NsaDc.ScgFailure N.NsaDc.DRB.AbnormRel
cell as their PCell in the LTE-NR NSA DC state SgNB
③ New direct-connected
Divider
CPE CPRI optical cable ④ New BBU5900 ⑨ Added RAN OSS
5G
TUE
XGE electrical port
interconnection
RRU (TDD1900) New CN OSS
4G
⑧ Added CN OSS
TUE
Alternative 1: Core network upgrade and reconstruction Alternative 2: New EPC deployment, new EPC and inventory EPC forming MOCN
PLMN AAA
EPC EPC EPC
Existing core network NG core
4G Only UE NSA UE
Solution 2: New core network is deployed.
Solution 1: The existing core network is upgraded and Advantages: Existing users on the live network are not affected.
expanded. Disadvantages: 1. Core networks need to be selected for different users.
Advantages: There is no requirement for core network selection. 2. For future commercial use, you need to configure a complex roaming policy so that users of PLMN BBB
Disadvantages: Existing users on the live network are affected. can roam to PLMN AAA.
Solution 1 is preferred for commercial deployment. In the initial test phase, the independent PLMN solution can be used.