◆ 100% verbatim from Huawei HedEx · nothing invented

EPC+ Core Optimization for 5G NSA
Option 3 / 3a / 3x

Configuration and optimization reference for Huawei's EPC+ core on a 5G non-standalone network — CloudUSN (MME/SGSN) and CloudUGW (S-GW/P-GW). Every feature ID, MML parameter, IE, counter, KPI formula and fault case on this page is extracted directly out of the HedEx libraries on disk.

EPC counters
Cause-tagged counters
S1 KPI formulas
Signalling messages
IE definitions
Message-IE rows
MML commands
MML parameters
NSA software params
Huawei fault cases
1.1

Architecture Evolution to 5G

Verbatim — CloudUSN → Solutions → NSA → NSA Overview.

There are three core networks involved in 4G-to-5G evolution, that is, EPC, EPC+ (enhanced EPC to support 5G NR), and 5GC. There are also three radio access technologies (RATs) involved in the evolution, that is, LTE, eLTE (enhanced LTE to support interworking with 5GC), and NR.

The 4G SA network is evolved to a 5G NSA network using option 3/7/4, and then to the 5G SA network using option 2. In the NSA networking architecture, options 3, 7, and 4 indicate three phases of NSA during 4G-to-5G evolution.

CloudUSN → Solutions → NSA → NSA Overview toctopics/en-us_concept_0145383747

The three NSA phases

1First phase — Option 3
“eNodeBs and gNodeBs share the EPC+, and signaling messages are exchanged between the UE and the EPC+ through eNodeBs.”
2Second phase — Option 7
“eLTE eNodeBs and gNodeBs share the 5GC, and signaling messages are exchanged between the UE and the 5GC through eLTE eNodeBs.”
3Third phase — Option 4
“eNodeBs and gNodeBs share the 5GC, and signaling messages are exchanged between the UE and the 5GC through gNodeBs.”
Verbatim. “NSA option 3/4/7 has their respective variants regarding the entities selected for traffic splitting on the user plane when a UE accesses the NSA network using MR-DC. The variants of option 3 are option 3, option 3a, and option 3x. In option 3, traffic is split across 4G and 5G at LTE eNodeB. In option 3a, traffic is split across 4G and 5G at EPC+. In option 3x, traffic is split across 4G and 5G at NR gNodeB. The variants of option 4 are option 4 and option 4a. The variants of option 7 are option 7, option 7a, and option 7x.”
1.2

Animated NSA Architecture — live topology

Switch between option 3 / 3a / 3x and watch the S1-U tunnels, the split anchor and the downlink user plane change. Topology, tunnel count and split behaviour are transcribed from Huawei NSA Solution Architecture; the description under the canvas is the verbatim HedEx paragraph for the selected option.

Verbatim, common to all three options. “Huawei uses option 3/3a/3x as the networking solution for early deployments of 5G NSA. In these options, eNodeBs and gNodeBs share the EPC+. The connection signaling is transmitted between the UE and the MME through the eNodeB.” … “In the three options, the UE control plane anchors on the eNodeB, and the UE does not trigger the handover procedure until it moves out of the coverage area served by the eNodeB.”
CloudUSN → Solutions → NSA → Huawei NSA Solution Architecture toctopics/en-us_concept_0145383748
1.3

Comparison of Traffic Splitting in Option 3/3a/3x

Verbatim — “Table 1 Comparison of option 3/3a/3x”. Data splitting anchor, splitting process, and networking advantages & disadvantages, exactly as Huawei states them.

Verbatim. “In the three options, the eNodeB determines whether to split user-plane data traffic according to the air interface status and the service type.”
CloudUSN → Solutions → NSA → Huawei NSA Solution Architecture toctopics/en-us_concept_0145383748
1.4

MR-DC — Multi-RAT Dual Connectivity

Verbatim — CloudUSN → Solutions → NSA → Appendix → MR-DC.

1.5

NSA Feature Inventory — WSFD IDs

Verbatim — “Table 1 CloudUSN features” from the NSA appendix. Feature ID → functions provided.

CloudUSN FeatureFunctions
WSFD-021101 5G NSA (Opt.3) Dual Connectivity Management Security parameter transmission
Data usage reporting
5G UE information exchange between SGSNs/MMEs
WSFD-021102 UE Capability-based Access Management UE capability-based access management
WSFD-121401 UE Capability-based User Plane Selection Selection of a high-speed S-GW/P-GW based on UE capability
WSFD-121402 5G Service Continuity Assurance Selection of a high-speed GGSN based on UE capability
WSFD-110531 DECOR in Pool 5G UE redirection to an appropriate MME
WSFD-021200 5G Ultra-High Bandwidth Basic Functions(1Gbps) 1 Gbit/s high-speed transmission rate on a single PDN connection for a maximum of 1000 UEs
WSFD-021201 5G Ultra-High Bandwidth Basic Functions(2Gbps) 2 Gbit/s high-speed transmission rate on a single PDN connection for a maximum of 1000 UEs
CloudUSN → Solutions → NSA → Appendix → NSA Features toctopics/en-us_concept_0154566722

Feature descriptions — verbatim

2.1

NSA Attach Procedure — 21 steps

Verbatim. “Compared with the LTE attach procedure, the 5G NSA attach procedure for UEs that support DCNR incorporates the NSA IEs in messages and transfer of 5G security parameters.” Each step description below is the exact HedEx paragraph for that step.

CloudUSN → NSA → 5G NSA Protocol Updates → 5G NSA Procedures → Attach Procedure toctopics/en-us_concept_0145383751

Message & IE detail for the selected step

As you step through the procedure above, this panel shows that step's verbatim Huawei message topic — the Message Function, the complete Associated IE table with 3GPP presence requirements, and a click-through to the full description of every IE.

2.2

NSA Mobility — S1 HO · X2 HO · TAU · Usage Reporting · MR-DC

Every mobility procedure Huawei documents for NSA, verbatim, each step opening its real message topic and full Associated-IE table. 48 steps across 5 procedures.

Why these five belong together. On NSA the control plane never leaves LTE, so every mobility event is an EPC event — but each one has to carry the DCNR bit, the 5G security parameters and the NR volume with it. S1 and X2 handover move the UE; TAU moves its context between MMEs; periodic usage reporting keeps NR volume flowing when nothing moves at all; and MR-DC establishment is the moment the NR leg is actually added. Miss any one and 5G silently degrades to 4G.

S1 Handover Procedure — 21 steps

Verbatim. “The S1 handover procedure in NSA architecture is similar to the LTE handover procedure. The only difference lies in NSA IEs and 5G security parameters, as well as the messages and IEs for NR data usage reporting. The following figure shows only the key steps in the S1 handover and TAU procedures and the steps closely related to NSA architecture.”

CloudUSN → NSA → 5G NSA Procedures → S1 Handover Procedure toctopics/en-us_concept_0145383751

Message & IE detail for the selected S1 handover step

The IRSGW / IRPGW rule — verbatim, and the reason NR volume goes missing. In Forward Relocation Complete Acknowledge and Modify Bearer Request the values of IRSGW and IRPGW are 0 and 1 respectively. “This is because IRPGW is used for the target MME to indicate whether the target S-GW forwards data usage reports to the P-GW. IRSGW is used for the target MME to indicate whether the target S-GW locally saves data usage reports. In the S-GW relocation scenario, the target S-GW forwards these reports to the P-GW, without locally saving them.”

The other four mobility procedures


Mobility counters — verbatim


Mobility KPIs — verbatim formulas

2.3

New NSA IEs — 22 rows, verbatim

Verbatim. “In the NSA architecture, NSA IEs and extended parameters are added to some existing messages. They vary with service procedures. The following table lists the new IEs and the procedures where these IEs are involved. The existing HSSs/MMEs/eNodeBs on the live network are upgraded to support 5G NSA features.”

CloudUSN → NSA → 5G NSA Protocol Updates → New NSA IEs toctopics/en-us_concept_0145383752
2.4

Secondary RAT Usage Data Reporting

The gNodeB carries the NR bytes; the EPC+ writes the CDR. These CloudUGW software parameters govern how that volume is measured, timestamped and reported — descriptions verbatim.

CloudUGW — Interworking Between LTE and 5G

2.5

Message & IE Reference — every message, every IE

The complete CloudUSN EPC signalling reference, verbatim: every message on every interface (S1-MME, S6a, S13, S10, S11, S5/S8, S2a/S2b, S3, S4, Gn, Gx, Gy, Sx/PFCP, RADIUS) with its Message Function, full Associated-IE table and 3GPP presence requirements — and every IE drillable to its own description.

3.1

NSA Configuration Pipeline — what to do, in order

The complete NSA bring-up as an executable pipeline. Run it, or click any stage. Each stage states what to do, the exact MML commands, the feature it belongs to, and why — quoted verbatim from the CloudUSN documentation.


Deployment Cockpit — “Deploying Basic NSA Services”, live on the topology

Huawei's own deployment task as a mission: press ▶ Deploy and watch each step light up the NE and interface it configures on the network map. Three phases — Configure CloudUSN (6 steps) · Configure CloudUGW/CGW (3 steps) · Verify (3 trace scenarios with animated expected-result checklists). Every task line, script, data-plan parameter and expected result is verbatim.

CloudUSN → Solutions → NSA → Project Implementation → Deploying Basic NSA Services toctopics/en-us_opi_0150351514.html
3.2

Feature Lifecycle Console — WSFD-021101 Activate ⏻ / Deactivate ⏼

The activation and deactivation tasks as a live state machine. Flip the rocker, press ▶ Walk, and watch the feature move INACTIVE → ACTIVE step by step — while the five control points on the right flip in real time. Deactivation runs the exact mirror: every SET/ADD …=YES becomes a SET/MOD …=NO rollback. Task text, MML, required data and verification are verbatim from the two CloudUSN feature-operation topics.

CloudUSN → Feature Guide → CloudUSN Features → WSFD-021101 → Activating / Deactivating vusn/om/cn_10_19_15812101 · cn_10_19_15812102
3.3

MML Command Reference — 127 commands

Every NSA-relevant command on the CloudUSN, grouped by function: NSA control, S1 interface, gateway characteristics, GTP-C compatibility, DNS/host file, DECOR/DCN, MNO/MVNO and licence. Each carries its verbatim Function, a real MML example, and every parameter with value range, default and configuration notes.

3.4

NSA Software Parameters — golden-parameter ladder

All 103 NSA / DCNR / 5G software parameters across the CloudUSN and CloudUGW, sorted by Huawei's own Impact Level. Each shows Applicable NEs, Description, Value Description (range, recommended and initial value), Application Scenario, Impact on the System and Time to Take Effect — verbatim.

3.5

Deploying a High-Speed Gateway in NSA Networking

The verbatim task for WSFD-121401 UE Capability-based User Plane Selection, as a runnable 13-step task across CloudUSN and CloudUGW. Press ▶ Run task — each step shows its verbatim text, MML and its own slice of the 39-row data plan. Below, the animated +nc-nr DNS resolution that decides whether a gateway is high-speed at all.

3.6

Deploying DECOR in Pool

The verbatim task for WSFD-110531 DECOR in Pool — “5G UE redirection to an appropriate MME”. 14 steps: plan the MME group, the UE Usage Type group, and the DCN mapping that steers a DCNR UE onto an NSA-capable MME while the pool is only partly upgraded.

4.1

S1-Mode KPI Library — verbatim formulas

Each KPI is transcribed from the HedEx counter reference — exact formula, exact counter IDs, exact unit and measured object. Filter by category, or search a counter ID to find which KPI consumes it.

4.2

Counter Explorer — 3,060 EPC counters

The complete CloudUSN counter reference for the EPC: S1 mode MM, S1 mode SM, S1, S6a, GTPC, GTPU, SGs and CDR — 105 measurement units. Every counter carries its verbatim Description, Unit, Measurement Point (exactly when the MME increments it), Measurement Type and formula.

4.3

Cause-Code Analyzer — 808 cause-tagged counters

Huawei counts every reject per EMM/ESM cause code. This is the fastest path from “success rate dropped” to “which cause is rising, and where exactly does the MME count it”.

4.2

Huawei Fault Cases — Symptom · Possible Causes · Procedure

The complete CloudUSN troubleshooting set for LTE service faults and DNS query errors, verbatim. These are Huawei's own documented fault cases — symptom, possible causes and the exact MML procedure to rectify each one.

4.5

Full CloudUSN KPI Set — all categories

The complete MME/SGSN KPI library — Mobility management, Authentication, Session management, Traffic mode, CSFB, VoLTE and NB-IoT.

5.1

Source Provenance

Every claim on this page resolves to a file inside a HedEx library on disk.

libIdLibraryVersionIssueTopicsDate
CEK09147CloudUSN Product DocumentationV100R020C60SPC1000430,7082026-01-10
CEK0811GCloudUGW Product DocumentationV100R020C60SPC1001125,4242026-02-04
CEK0812DCloudUGW Product Documentation (CGW&DGW)V100R020C60SPC1001233,0072026-02-04
CEK1018WCloudCG Product DocumentationV100R019C15SPC500039,6282025-02-24
CEP0409SUNC Product Documentation (MME/SGSN KPI model)25.1.00251,5042025-07-31
Extraction method. Each .hdx is a ZIP archive containing profile.xml, resources/navi.xml (the full topic tree) and per-topic HTML. The chapter tree, KPI formulas, MML parameter tables, IE tables and fault cases on this page were parsed directly out of that archive — so the text here is the text in the library, not a transcription by hand.