566204064-SRAN13-1-15-0-NSA-Networking-Based-on-EPC-20180905.pptx

HUAWEI TECHNOLOGIES CO., LTD.
www.huawei.com
Huawei Confidential
Security Level:
2024/1/4
SRAN15.0 NSA Networking
based on EPC

Objectives
 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.

HUAWEI TECHNOLOGIES CO., LTD. Page 3
NSA Standard Planning and Functions
 NSA: Completed the NSA standard architecture in December 2017, froze procedures and messages in March 2018, and specified
message IEs in June 2018.
LTE-A Pro
2016
5G New RAT
Rel-15
2017 2018 2019
5G Phase 1.1 5G Phase 1.2 5G Phase 2
Rel-16
Rel-14
NR NSA
(non-independent RAT)
NR SA
(independent RAT)
Full-IMT2020 NR
• Definitions of NGCN and NR
NSA, SA architecture
(eMBB/URLLC)
• Full 5G standard and mMTC capability
definition
• Enhanced capability definition: Soft
AI/D2D/D-TDD/Flexible Duplex
• NSA definition, eMBB
• Numerology, frame
structure
• Native M-MIMO &
waveform
• eMBB
• URLLC
• mMTC
 SRAN13.1 is the first version of NSA Networking based on EPC. In SRAN15.0, interference coordination is added and mobility
management is enhanced.
 Carrier management
 Mobility management
 Data split (UL/DL)
 Uplink power control
 eNodeB and gNodeB interconnection modes
 Interference coordination between LTE and NR
NR service objectives
Expected in 2019 H2
Launch of NSA terminals

LTE+NR DC Deployment Scenarios
LTE Anchor, EPC eLTE Anchor, New Core NR Anchor, New Core
Option 3 [18B/19A]
S1
X2
NR Non-Standalone
EPC NC
LTE NR
EPC NC
LTE
X2
EPC NC
LTE NR
Option 3a
Option 3X [18B/19A]
S1
S1
EPC
NR
EPC
NR
NC
NC
Option 7
Option 7a
eLTE
EPC NC
NR
eLTE
Option 4
S1-U
EPC NC
NR
eLTE
Option 4a
eLTE
S1-U
Ng
Xn
Ng Ng-U
NR Standalone
X2-C
NR
Legend
User Plane
Control Plane
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.
EPC
NR
NC
Option 7X
eLTE
Ng
Xn
Xn-C
Ng-U
5G NSA gNodeBs will support
5G SA without any hardware
changes.
EN-DC NGEN-DC NE-DC
in option 3x, S1-U
with LTE only used
for LTE bearer setup
and GBR service.
No data transferred.

DC Related Concepts
MR-DC
category
Specific
Scenario
Full Name
Core
network
MN SN Option
MR-DC with
EPC
EN-DC
E-UTRA-NR Dual
Connectivity
EPC LTE NR 3/3a/3x
MR-DC with
5GC
NGEN-
DC
NG-RAN E-
UTRA-NR Dual
Connectivity
5GC eLTE NR 7/7a/7x
NE-DC
NR-E-UTRA Dual
Connectivity
5GC NR eLTE 4/4a
DC (Dual-Cell): Two carriers are bundled to implement a technology that
doubles the rate of a single carrier. like DC-HSDPA+ in UMTS. This DC(Dual-Cell)
is not the one described in this document.
DC（Dual Connection）：Indicates the operation mode of the UE in RRC
connected mode. The UE is configured with a primary cell combination and a
secondary cell group. The "DC" in the document indicates the LTE DC.
MR-DC ：Multi-RAT Dual Connectivity. Including EN-DC, NE-DC, and NGEN-DC.
MeNB：Master eNB, the eNB with S1-MME interface in the DC.
SgNB：Secondary gNodeB, the NR site configured by the MeNB through RRC
connection signaling for the NSA DC terminal. In 18B and 19A, only the NR site can be
set to the SgNB.
Pcell：Primary Cell. Primary cell of the MeNB, which cell the NSA DC terminal
camps on.
PSCell：Primary Secondary Cell: The primary cell of the SgNB which is
configured by the MeNB using RRC connection signaling for NSA DC user. The
PSCell is in the activated state once PSCELL is configured successfully.
Scell：Secondary Cell, a secondary cell configured by the MeNB. It works on the
SCC, which can provide more radio resources for the NSA DC terminal.
Cell Group：A group of serving cells on the MeNB or the SeNB In the DC.
MCG：Master Cell Group. A cell group on the MeNB has one Pcell and one or
more SCells.
SCG：Secondary Cell Group. In the DC, the serving cell is only related to the
SgNB, and has one PSCell and one or more optional SCells.
3GPP 36300-R14

Contents
 Functions and Principles
• EN-DC Carrier Management
• EN-DC Data Split
• EN-DC Uplink Power Configuration
 Feature Planning
 Feature Installation and Commissioning
 Feature Acceptance and Maintenance

EN-DC Carrier Management
• The eNodeB is MeNB, and the gNodeB is SgNB.
• EN-DC specifications: 1 MeNB+1 SgNB
• Intra-RAT CA specifications:
DL: LTE support 5CC, NR support 2CC(Only intra-band CA were supported in NR side).
UL: LTE 1CC, NR C-BAND 2CC(Only intra-RAT CA were supported in NR side)
 NSA networking based on EPC
 MeNB carrier management
• PCC anchor selection(for UE in RRC_CONNECTED status, RRC_IDLE status, duplex-
mode-priority-based PCC anchoring selection, and load-based PCC anchoring selection)
• SCC carrier management (SCell configuration, SCell change, enhanced SCell selection,
SCell activation, SCell deactivation, and SCell removal)
The MeNB carrier management is identical with LTE carrier management.
For details, see <LTE Carrier Aggregation Feature Parameter Description>.
 SgNB carrier management (only PSCell configuration)
• Triggering conditions of PSCell configuration:
1. The MeNB PCC anchoring procedure is complete.
2. The UE supports NR.
3. The one-way transmission delay between the MeNB and SgNB
is less than 60ms (20ms for better performance).
• PSCell Configuration Procedure
Step 1: The MeNB fills and delivers an SCG measurement control
message.
The MeNB delivers the NR measurement control to the UE. Direct signaling
interaction between the gNodeB and the UE is not supported.
Step 2: GAP-assisted measurement control is performed.
When a UE needs to measure the quality of inter-frequency channels, GAP-
assisted measurement needs to be started.
Step 3: The UE sends an event B1 measurement report to the
MeNB.
Step 4: After receiving the measurement report, the MeNB decides
to trigger an SgNB Addition (PSCell configuration) procedure.
If multiple cells are reported in the measurement report, the MeNB adds the
strongest RSRP cell of SgNB reported in the measurement report.
CC1
CC2
CC3
CC4
CC5
3.5G
LTE NR
DC
3.5G
LTE 5CC + NR 2CC
Please show the corresponding NE:
MN, SN;
MCG, SCG;
Pcell, Pscell, Scell;

SgNB Addition Procedure
3GPP.TS.37.3400

EN-DC Data Split
MeNB (LTE)
PDCPLTE
RLCLTE
MACLTE
SgNB (NR)
PDCPNR
RLCNR
MACNR
S1-U
X2
RLCLTE
MeNB (LTE)
PDCPLTE
RLCLTE
MACLTE
SgNB (NR)
PDCPNR
RLCNR
MACNR
S1-U
X2
RLCLTE
Data split at LTE PDCP layer
MCG Split Bearer:
 Downlink data split architecture
 Parameter settings for downlink data split
SGW
MCG Split Bear SCG Split Bear
1. The MAC/RLC entities of the master or secondary base
stations corresponding to the UE are independent.
2. Uplink data scheduling and BSR reporting are independent.
3. On the UE side, the PDCP entity is shared by NR and LTE.
4. The UE performs uplink data split according to the
configuration command delivered by the master base station.
MAC MAC
RLC RLC
PDCP
UE
Split bearer
MeNB/MgNB SgNB/SeNB
BSR+Data BSR+Data
Configuration
 Uplink data split architecture
LTE parameter
NR CQI level parameter
NsaDcDefaultBearerMode NsaDcUeMcgUlAmbrRatio
UlDataSplitPrimaryPath UlDataSplitThreshold
UlDataSplitThreshold
Data split at NR PDCP layer
SCG Split Bearer:

Typical scenario parameter setting
Solution:
1. Data distribution to the PDCP anchor is preferred.
2. The X2 transmission delay and LTE/NR RLC buffer delay are supplemented.
3. Packets are sent in turn based on the ratio of the RLC perceived rate.
 Dynamic data split solution (gNB PDCP split as example)
 The 5G gNB PDCP layer distributes data to the LTE RLC and NR
RLC layers by packet.
5G uplink and downlink
balance area
5G uplink restricted
area
Downlink data carried on 5G
Uplink data carried on 4G
4G coverage
 NR UL/DL Separation
 NR CP/UP Separation
UE
eNodeB
gNodeB
Parameter Dynamic data split NR UL/DL Separation NR CP/UP Separation
DlDataPdcpSplitMode SCG_AND_MCG SCG_ONLY SCG_ONLY
UlDataSplitPrimaryPath SCG MCG SCG
UlDataSplitThreshold BIT0 Infinity Infinity
For Insufficient NR uplink coverage scenario.
Static configuration: UL data transmitted on
LTE, and DL data transmitted on NR.
• CP data carried on LTE, UP data carried on NR
• NR can provide high capacity/throughput by
large bandwidth.
• LTE provide mobility, and handovers can be
performed without any interruptions.
 Typical scenario parameter setting
(Option 3X as example)
• Actual RLC buffer
• Traffic of PDCP PDUs
received by RLC
• User-perceived RLC rate
Reporting period: 100 ms
DL Data Delivery Status [10 ms]:
• Actual RLC buffer [100 ms]
• Traffic of PDCP PDUs received by
RLC [100 ms]
• User-perceived RLC rate [100 ms]
Distributed data
Status feedback

EN-DC Uplink Power Configuration
 Uplink power configuration
• A proper proportion of the UE power is allocated between LTE and NR to ensure the transmission of uplink data and
signaling of the UE.
• Power configuration parameters (controlled on the LTE side)-19A
NsaDcUeMcgUlMaximumPower (NSA DC UE MCG uplink maximum power)
NsaDcUeScgUlMaximumPower (NSA DC UE SCG uplink maximum power)
• Power configuration
According to 3GPP specifications, the maximum uplink transmit power of NSA UEs is 23 dBm.
This version supports only power control in semi-persistent scheduling. Currently, the uplink TDM power control mode
and dynamic power sharing mode are not supported. Therefore, the following configuration is recommended:
NsaDcUeMcgUlMaximumPower=NsaDcUeScgUlMaximumPower=20dBm

EN-DC Interference Avoidance
 Solutions
• Cross-modulation interference avoidance solution
Subframe-level TDM: After LTE-NR subframes are aligned, LTE and NR uplink subframes are scheduled
at different time.
• X2 interface message in the avoidance solution
The frequency information and graph structure are transmitted according to 3GPP X2 interface
standard messages.
 Scenario Analysis
• Cross-modulation interference: LTE-NR uplink concurrency produces cross-modulation
interference, affecting LTE downlink reception.
• Harmonic interference: LTE uplink secondary harmonic interferes NR downlink
reception.
Cross-modulation interference Harmonic interference
 Customer Benefits
• Cross-modulation interference avoidance:
LTE common channels are not affected (ensuring UE mobility).
Single-user downlink performance improves by 30%.
• Harmonic interference avoidance: NR common channels are not affected (ensuring
UE mobility).
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
scheduling.
Slot
PRB
Time-frequency positions of NR
common channels
LTE channels are yielded to NR
common channels in uplink scheduling
(converted to the frequency range that
generates secondary harmonic
interference).

X2 Interface Management
MME
eNodeB gNodeB
SGW
S1-C
S1-U
S1-U
X2-C
X2-U
EN-DC X2 self-management includes the following functions:
 X2 Self-Setup
The eNodeB sets up EN-DC services to trigger X2 self-setup. X2 self-setup involves manual
configuration of the peer IP addresses and automatic configuration of the peer IP addresses.
Currently, only X2 self-setup over U2020 is supported, and the eNodeB and gNodeB must be
managed by the same U2020.
 X2 Self-Update
During network operation, the IP address or operator information (MNC, MCC, or Global
eNodeB ID) of the peer eNodeB may be modified. When the X2 interface is faulty, the X2 self-
setup procedure is triggered again.
 X2 Self-Removal
The eNodeB proactively releases the X2-U links that are not used or disconnected for a long
time.
In the EN-DC architecture, the eNodeB/gNodeB supports only the
configuration of the X2/S1-U interface in the endpoint configuration
mode.
• The logical interface between the eNodeB and the gNodeB is the
X2 interface. The X2 interface includes the X2 interface on the
control plane (X2-C) and X2 interface on the user plane (X2-U).
The X2 control plane is based on the SCTP (Stream Control
Transmission Protocol) and the user plane is based on the GTP-U
(GPRS Tunneling Protocol-User Plane).
• The user-plane interface between the gNodeB and the S-GW is
S1-U. S1-U is based on the GTP-U. In the Option 3X architecture,
the S1-U interface between the gNodeB and S-GW must be
configured.
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.

Contents
 Functions and Principles
 Feature Planning
 Feature Installation and Commissioning
 O&M and Performance Counters

Version/License 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.
 Feature Names and IDs
00 FDD Multi-mode Basic Features
00 TDD Multi-mode Basic Features
00 NR Multi-mode Basic Features
MRFD-131122
MRFD-131132
MRFD-131162
NSA Networking based on EPC (LTE FDD)
NSA Networking based on EPC (LTE TDD)
NSA Networking based on EPC (NR)
00 FDD Multi-mode Basic Features
00 TDD Multi-mode Basic Features
00 NR Multi-mode Basic Features
MRFD-131121
MRFD-131131
MRFD-131161
LTE and NR X2 Interface Self-Configuration (LTE FDD)
LTE and NR X2 Interface Self-Configuration (LTE TDD)
LTE and NR X2 Interface Self-Configuration (NR)

DC scenario
selection &
data split
configuration
Installation and Commissioning-Feature Activation and Data Split Mode Configuration
NE Feature MML Command Parameter ID Parameter Name Default Value Recommended Value
MOD NRCellAlgoSwitch NsaDcSwitch NSA DC switch ON ON
DlDataScgSplitBearerMode Downlink Data SCG Split Bearer Mode SCG_AND_MCG SCG_ONLY
UlDataSplitPrimaryPath Uplink Data Split Primary Path MCG SCG
UlDataSplitThreshold UL Data Split Threshold BYTE200 BYTE0
MOD eNodeBAlgoSwitch CaAlgoSwitch CA Algorithm Switch OFF FreqCfgSwitch-1
PccDlEarfcn PCC Downlink EARFCN None Keep current value if exist
PreferredPccPriority Preferred PCC Priority 0 Keep current value if exist
PccA4RsrpThd PCC A4 RSRP Threshold -105 Keep current value if exist
PccA4RsrqThd PCC A4 RSRQ Threshold -20 Keep current value if exist
PccDlEarfcn PCC DL EARFCN None LTE DL EARFCN
ScgDlArfcn SCG DL ARFCN None NR DL NARFCN
ScgDlArfcnPriority SCG DL ARFCN Priority None Refer to Planning Result
NsaDcB1ThldRsrp NSA DC B1 Event RSRP Threshold -105 -105
NsaDcAlgoSwitch NSA DC Algorithm Switch OFF NSA_DC_CAPABILITY_SWITCH-1
NsaDcDefaultBearerMode NSA DC Default Bearer Mode SCG_SPLIT_BEARER SCG_SPLIT_BEARER
NsaDcUeMcgUlAmbrRatio NSA DC User MCG UL AMBR Ratio 50% 0.3
NsaDcUeMcgUlPowerRate NSA DC UE MCG UL Power Rate 9 9
NsaDcUeScgUlPowerRate NSA DC UE SCG UL Power Rate 9 9
MOD UECOOPERATIONPARA SpecUserCooperationSwitch Identify specific UEs SpecUeIdentifySwitch:Off SpecUeIdentifySwitch-1
MOD CELL DlBandWidth Downlink Bandwidth None CELL_BW_N50
DlArfcn Downlink ARFCN None NR DL NARFCN
UlArfcnConfigInd Uplink ARFCN Configuration Indicator NOT_CFG NOT_CFG
Mcc Mobile Country Code None Refer to Actual information.
Mnc Mobile Network Code None Refer to Actual information.
gNodebId gNodeB ID None Refer to Planning Result
CellId Cell ID None Refer to Planning Result
DlArfcn Downlink ARFCN None NR DL NARFCN
UlArfcnConfigInd Uplink ARFCN Configuration Indicator None NOT_CFG
PhyCellId Physical Cell ID None Refer to Planning Result
Tac Tracking Area Code None Refer to Planning Result
Mcc Mobile Country Code None Refer to Planning Result
Mnc Mobile Network Code None Refer to Planning Result
gNodebId gNodeB ID None Refer to Planning Result
CellId Cell ID None Refer to Planning Result
MOD NRCellNsaDcConfig
NR
gNodeB
MRFD-131162
NSA
Networking
based on EPC
(5G NR)
MOD NsaDcMgmtConfig
ADD NRNFREQ
ADD NREXTERNALCELL
ADD NRNRELATIONSHIP
ADD NrScgFreqConfig
ADD PCCFREQCFG
(Keep current value if exist, don't
modify)
MRFD-131122
NSA
Networking
based on EPC
(LTE FDD)
LTE
eNodeB
Sample:
18B Option3x
LTE -> NR
Neighbor
LTE
parameter
NR
parameter

Installation and Commissioning-Feature Activation and Data Split Mode Configuration
Sample:
19A Option3x
LTE -> NR
Neighbor
LTE
parameter
NR
parameter
DC scenario
selection &
data split
configuration
CQI level
parameter

Activation Evaluation
 LTE Traffic Statistics  NR Traffic Statistics
Counter Name Counter Description
L.Traffic.User.NsaDc.PCell.Avg
Average number of UEs that treat the local cell as their PCell in the
LTE-NR NSA DC state
L.Thpt.bits.DL.McgSplit.MeNB
Total traffic volume offloaded from UEs in the PCell at the PDCP
layer to the MeNB during LTE-NR NSA DC 3C offloading
L.Thpt.bits.DL.McgSplit.SgNB
Total traffic volume offloaded from UEs in the PCell at the PDCP
layer to the SgNB during LTE-NR NSA DC 3C offloading
L.Thpt.bits.UL.McgSplit.MeNB
Total uplink MeNB traffic volume received by UEs in the PCell from
the PDCP layer of the MeNB during LTE-NR NSA DC 3C offloading
L.Thpt.bits.UL.McgSplit.SgNB
Total uplink SgNB traffic volume received by UEs in the PCell from
the PDCP layer of the MeNB during LTE-NR NSA DC 3C offloading
L.NsaDc.SgNB.Add.Att
Total number of SgNB addition attempts for UEs that treat the local
cell as their PCell in the LTE-NR NSA DC state
L.NsaDc.SgNB.Add.Succ
Total number of successful SgNB additions for UEs that treat the
local cell as their PCell in the LTE-NR NSA DC state
L.NsaDc.SCG.Change.Att
Total number of SCG change attempts for UEs that treat the local
L.NsaDc.SCG.Change.Succ
Total number of successful SCG changes for UEs that treat the
local cell as their PCell in the LTE-NR NSA DC state
L.NsaDc.SgNB.Rmv.Att
Total number of SgNB removal attempts for UEs that treat the local
L.NsaDc.ScgFailure
Total number of SCG-related failures for UEs that treat the local cell
as their PCell in the LTE-NR NSA DC state
Counter Name Counter Description
N.User.NsaDc.PSCell.Avg Average number of LTE-NR NSA DC UEs using the current cell as PSCell
N.NsaDc.SgNB.Add.Att Number of SgNB addition requests in the LTE-NR NSA DC scenario
N.NsaDc.SgNB.Add.Succ Number of successful SgNB additions in the LTE-NR NSA DC scenario
N.NsaDc.InterSgNB.PSCell.Change.Att
Number of inter-SgNB PSCell change requests in the LTE-NR NSA DC
scenario
N.NsaDc.InterSgNB.PSCell.Change.Succ
Number of successful inter-SgNB PSCell changes in the LTE-NR NSA DC
scenario
N.NsaDc.IntraSgNB.PSCell.Change.Att
Number of intra-SgNB PSCell change requests in the LTE-NR NSA DC
scenario
N.NsaDc.IntraSgNB.PSCell.Change.Succ
Number of successful intra-SgNB PSCell changes in the LTE-NR NSA DC
scenario
N.NsaDc.SgNB.Rel Total number of SgNB releases in the LTE-NR NSA DC scenario
N.NsaDc.SgNB.AbnormRel Number of abnormal SgNB releases in the LTE-NR NSA DC scenario
N.NsaDc.DRB.Add.Att Number of DRB addition requests for LTE-NR NSA DC UEs on the SgNB
N.NsaDc.DRB.Add.Succ Number of successful DRB additions for LTE-NR NSA DC UEs on the SgNB
N.NsaDc.DRB.Rel Number of DRB releases for LTE-NR NSA DC UEs on the SgNB
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
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
N.PDCP.Vol.UL.X2U.TrfPDU.Rx Traffic of uplink PDCP PDUs received over the X2 interface in a cell

Examples of Signaling Tracing
LTE Uu interface tracing (event B1 measurement of NR delivered by the eNodeB)
S1 interface tracing (E-RAB path change in the Option 3X architecture)
L-NR X2 interface tracing (the eNodeB sends an SgNB addition request)
E-RAB path change

NSA DC Deployment on the Live Network
New RAN OSS
New CN OSS
NG Core
AAU (NR 3.5G)
RRU(TDD1900)
RRU(TDD2600)
③ New direct-connected
100G CPRI optical cable
BBU5900 (NR)
BBU39X0(LTE)
④ New BBU5900
⑥ Transmission bandwidth:
8.5 Gbit/s (peak bandwidth of a single cell)
16.5 Gbit/s (peak bandwidth of three cells)
GPS
⑤ Added GPS/BeiDou
divider and cables
CPE
Terminal Antenna RRU and CPRI BBU Transmission
and clock
Core
network
NMS
② Added NR 3.5 GHz AAU
Divider
⑦ NG Core
⑧ New PLMN (5G)
⑨ Added RAN OSS
⑧ Added CN OSS
5G
TUE
4G
TUE
XGE electrical interface
interconnection
E2E networking

UE Access network Policy Overview
gNodeB
Anchor eNodeB
5G-Uu
NSA UE
Transport Network
RAN Network
MME/SGSN S-GW/P-GW/GGSN
MME/SGSN S-GW/P-GW/GGSN
Core Network
Existing EPC
New EPC+
4G only UE 4G-Uu
UE Access Anchor UE Access Core Network
Purpose: Purpose:
Optional UE access anchor policy: Optional UE access CN policy:
NSA UE and 4G only UE access control at RAN
1. NSA UE can be accessed only at anchor
2. Whether 4G only UE can access anchor
1. Multi-PLMN access control
a) Combining MOCN Policies
b) 5M LTE Dedicated Carrier realize isolation.
2. Single PLMN access control:
a) reserved cell of the operator + AC level control
b) Select NSA Terminal by TAC+IMSI
NSA UE and 4G only UE core network access control at CN
1. NSA UE can only select EPC+
2. Whether 4G only UE can be controlled by EPC+
1. Décor (19A support)
2. MOCN
3. Fixed GUMMEI by Msg5+S1 flex (Not recommended. Need R&D
engineers support, if it’s required.)
4. Use 5M LTE dedicated network, select the corresponding CN based
on the UE access anchor control policy.
UE access network policy involve UE access anchor policy and UE access core network policy.
Material & Video
Release Link

MME Selection Based on DECOR (DCN) in 19A
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.
LTE UE eNodeB MME (new) MME (old)
RRC Connection Setup
Initial UE Message
Reroute NAS Request,
including GUTI
Select the old MME
based on GUMMI in
GUTI
The MME identifies the LTE
UE and reroutes it to the old
MME.
Initial UE Message
NSA UE eNodeB MME (old) MME (new)
RRC Connection Setup
Initial UE Message
Reroute NAS Request,
including GUTI
Select a new MME
based on GUMMI in
GUTI.
The MME identifies the
NSA UE and reroutes it to
a new MME.
Initial UE Message
MME (old): does not support NSA; MME (new): supports NSA.
Function switch on the eNodeB side: CNOPERATOR.OperatorFunSwitch: DCN_SUPPORT_SWITCH
MME selection based on DECOR requires wireless support (starting from 18A) and CN support (starting from 19A).

Thank you

 Inter-site DC: This scenario supports only the X2 transmission
interconnection solution (< 20 ms).
 Intra-site DC: CI interconnection (not recommended)
 Intra-site DC based on transmission interconnection (recommended)
LSW
LSW
LSW
Interconnection Between gNodeB and eNodeB Under EN-DC
 Intra-site DC: L/NR co-MPT (supported in 19A)
TRAN
Co-PDCP
RLC
(L)
RLC
(NR) Split Bearer
UBBP (NR)
UBBP (L) UBBP (L)
UMPT(LNR)
5900
TRAN
PDCP (NR)
RLC
(L)
RLC
(NR)
Split Bearer
PDCP (L)

566204064-SRAN13-1-15-0-NSA-Networking-Based-on-EPC-20180905.pptx

Recommended

Recommended

More Related Content

Similar to 566204064-SRAN13-1-15-0-NSA-Networking-Based-on-EPC-20180905.pptx

Similar to 566204064-SRAN13-1-15-0-NSA-Networking-Based-on-EPC-20180905.pptx (20)

Recently uploaded

Recently uploaded (20)

566204064-SRAN13-1-15-0-NSA-Networking-Based-on-EPC-20180905.pptx