Deep Dive into E2E 5G NSA Accessibility Signaling and Failures: Your Complete Handbook
Mohamed ElAdawi Ashour
Senior Solution Architect at Ericsson`s Strategic Competence Unit
Introduction:
This Article is a deep dive into 5G NSA Accessibility Signaling overview and Failures Possible Causes & Troubleshooting Methods.
The following topics are explored in this article:
1. NSA(ENDC) Network Overview
2. 5G Secondary Node Addition procedure
3. Signaling Key Information Elements Contents
4. 5G NSA Troubleshooting Guide: Identification of Accessibility Issues
5G NSA(ENDC) Network Overview
5G NSA Option 3X Architecture
Before delving into the details, let's first recap the simplified network architecture of 5G NSA (Non Standalone). 5G Non Standalone signifies that the deployment of the 5G Network still relies on the existing 4G Network (RAN & Core). In this setup, the 4G Network serves as an anchor to the 5G. In simpler terms, most current deployment scenarios utilize the Option 3X Architecture. Here, all signaling and control planes are managed through the 4G eNodeB, and data split occurs on the SgNB. The data split bearer primarily supports SCG Split Bearer, indicating that user-plane data is split at the PDCP layer of the SgNB, distributed to the RLC layers of the MeNB and SgNB, as illustrated in the figure below, and then aggregated at the PDCP layer of the UE.
In summary:
· 5G NSA can be deployed in areas where LTE and NR network coverage overlap.
· The network architecture utilized depends on how the eNodeB/gNodeB and the EPC are interconnected.
Related Concepts
This section utilizes the picture and table below to illustrate the concepts related to NSA networking. In this example:
- Carrier aggregation is carried out separately on the eNodeB and gNodeB sides, followed by providing Dual Connectivity (DC) for the NSA UE.
- Each carrier corresponds to a cell. Cells 1 and 3 represent co-coverage cells of the eNodeB, while cells 2 and 4 represent co-coverage cells of the gNodeB.
It's essential to grasp the related concepts and naming conventions outlined in the table below for the 5G NSA network, as this will streamline the signaling analysis. The key concepts to bear in mind relate to the Cell Category, where:
- PCell: The Primary Cell (PCell) of the NSA UE is a cell served by the MeNB on which the UE is camping.
- PSCell: The Primary SCG Cell (PSCell) of the NSA UE is a primary cell served by the SgNB and configured for the UE through an RRC message sent by the MeNB. During SgNB Addition, the eNodeB delivers an RRC Reconfiguration message containing all relevant parameters and configurations for the PScell (SpCell), which will be covered in this article.
- SCell: A Secondary Cell (SCell) of the NSA UE is a cell served by either the MeNB or SgNB and configured for the UE through an RRC message sent by the MeNB. This cell can provide the UE with additional radio resources. (For example, Cells 3 and 4 are SCells).
Note: The PUCCH is available in each PCell and PSCell but not available in any SCell.
EN-DC Accessibility and Mobility Scenarios:
In this article, we'll deep dive into the signaling call flow of Secondary Node addition. The eNodeB triggers SgNB additions during initial access or when specified traffic volume thresholds are met, as set by vendors or operators. SgNB addition may occur in the following scenarios:
- Initial SgNB addition
- After SgNB addition failure
- SgNB addition during an incoming handover or SCell Change
5G Secondary Node Addition procedure:
- Lets begin by summarizing the procedure for adding a secondary node from a high-level perspective before exploring the detailed signaling call flow. The overall general procedure is outlined in the figure below.
Assuming the UE was in Idle mode, the first step is to initiate the initial access procedure to establish the UE context. After the UE is connected, the eNodeB will provide the necessary configuration for the NR B1 event required for SgNB addition measurements. Once the UE receives the B1-related configuration, it will measure the 5G SSB and report the measurement results to the 4G network if the specified B1 event conditions are met. Upon receiving the measurement report, the eNB will begin the SgNB addition procedures and instruct the UE to add the NR Spcell by sending all relevant information through an RRC Reconfiguration message. The UE will then complete DL synchronization with the NR cell and initiate RACH procedures towards the gNB to establish UL synchronization.
- Now lets go through 3GPP TS 37.340 Secondary Node Addition procedure procedures:
The Secondary Node Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. The below Figure shows the Secondary Node Addition procedure.
1. The MN decides to request the SN to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the SN, the MN provides X2-U TNL address information for the respective E-RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The SN may reject the request.
NOTE 1 : For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MNs decision is reflected in step 1 by the E- RAB parameters signaled to the SN, which may differ from E-RAB parameters received over SI.
NOTE 2: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e.,
without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer.
2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources. For bearers requiring SCG radio resources, the SN triggers Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN in a NR RRC configuration message contained in the SgNB Addition Request Acknowledge message. In case of bearer options that require X2-U resources between the MN and the SN, the SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the Sl-U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided.
NOTE 3: For the SN terminated split bearer option, the SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the SN together, or even more. The SNs decision is reflected in step 2 by the E- RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1. The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1.
NOTE 4: In case of MN terminated bearers, transmission of user plane data may take place after step 2.
NOTE 5: In case of SN terminated bearers , data forwarding and the SN Status Transfer may take place after step 2.
2. The MN sends to the UE the RRCConnectionReconfiguration message including the NR RRC configuration message, without modifying it.
3. The UE applies the new configuration and replies to MN with RRCConnectionReconfigurationComplete message, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure.
4. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SgNB ReconfigurationComplete message, including the encoded NR RRC response message, if received from the UE.
5. If configured with bearers requiring SCG radio resources, the UE performs synchronisation towards the PSCell of the SN. The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure.
6. In case of SN terminated bearers using RLC AM, the MN sends SN Status Transfer.
7. In case of SN terminated bearers using RLC AM, and dependent on the bearer characteristics of the respective E- RAB, the MN may take actions to minimize service interruption due to activation of EN-DC (Data forwarding).
9-12. For SN terminated bearers, the update of the UP path towards the EPC is performed.
- Now let’s go through the Most important Signaling message’s contents for the E2E Secondary Node Addition Procedure:
The below figure shows the E2E 5G Addition Call flow for NSA Option 3X starting from 4G Idle till path update procedures:
(1) Initial UE Context Setup Request:
The below table summarizes the mandatory and optional messages contents:
This is how the Initial UE Context Setup Request contents will looks like from the traces
(2) 4G RRC Reconfiguration and Measurement Report
Recommended by LinkedIn
RRC Reconfiguration: initially the g-NB deliver the NR EventB1 related thresholds as shown in the below figure:
Measurement Report: initially the UE will report the RSRP & RSRQ for the best serving cells once it is achieve the above given B1Event thresholds
(3) SgNB Addition Request:
In the SgNB Addition Request message, the eNodeB will provide the following parameters to the gNodeB:
The below table summarizes the mandatory and optional messages contents:
What will the SgNB Addition request look like in the traces? The following contents are the most important.
(4) SgNB Addition Request Ack:
The SgNB Addition Acknowledgment message will include the following key information from the gNodeB:
The below table summarizes the mandatory and optional messages contents:
What will the SgNB Addition request Ack look like in the traces? The following contents are the most important.
(5) RRC Reconfiguration:
After receiving the ACK message from the gNodeB, the eNodeB proceeds to directly transmit the NR configuration details to the UE over the air interface. This message encompasses all the cell configuration parameters pertinent to the NR side. It comprises the following components:
Among these four categories, the most crucial is the spCellConfig, which contains all the NR channel configurations. In NSA (Non-Standalone), all configurations are delivered in a single message, whereas in SA (Standalone), they are separated into distinct messages.
What will the RRC Reconfiguration message look like in the traces? The following contents are the most important.
(6) E-RAB Modification Indication:
5G NSA Troubleshooting Guide: Identification of Accessibility Issues
This section describes the user access process and common fault demarcation methods to preliminarily isolate and locate access problems. The most common failures can be categorized and classified into the 5 main parts:
1- The eNodeB did not deliver the NR B1 measurement configuration. Which is mostly can be caused by the following:
a. Configuration Issue: NSA Main Switch Not Enabled
b. Missing Frequency Definitions
c. Core Network Restriction (nRestriction IE) Preventing UEs from Using NSA or DCNR is restricted
d. DRB Configured for Emergency Calls
e. UE MR-DC Capability Does Not Support Current Band Combination
1- The UE did not report B1 Measurement Report
a. The SSB frequency in the B1 measurement control message is incorrect.
b. The 5G cell is experiencing abnormalities.
c. RF coverage issue or interference with the 5G SSB.
2- The eNodeB receives a measurement report but does not initiate an SgNB addition procedure.
a. Neighboring cell configuration is abnormal (PCI Conflict or Missing Definition).
b. The X2 link to the target site is abnormal.
c. PLMN configured for the eNodeB is consistent with the PLMN configured for the gNodeB.
3- The gNodeB rejects the SgNB addition request
a. Transport resource not available: Access is rejected due to transmission faults on the 5G side.
b. No radio resource available: Insufficient license for the number of users in the 5G cell, or other resources on the 5G network are abnormal.
c. Cell Not Available: Abnormal status of the 5G cell.
4- UE didn`t initiate RACH Procedure and reported scg-reconfigFailure or SCG_FAIL_INFO
a. UE Issues
b. High UL Interference
c. RACH parameters are configured incorrectly.
YouTube video for the same:
References:
Product Project Manager | Senior RAN Engineer | RF Manager
6moAs always Mohamed ElAdawi Ashour, impressive. Thank you for sharing this valuable information and insight. We encountered similar cases to the ones in the handbook from raw counters side where : Encountering high ENDC attempts with zero ENDC attempts success, it most likely indicates a configuration issue at the SCTP (transport layer) level. Most probably the SCTPLOCALPOINT definition appear to be absent in this case. But when there is no ENDC attempts at all ( Zero ENDC attempts with Zero ENDC Attempts success ), this is mainly (1) a missing neighbor relations or termpointtognb definition issue, (2) the traffic router IP is set wrong (3) ENDC profile setting from LTE node side is set wrongly ( QCIs are not following the baseline or gold standard ).
Senior RAN | 4G-LTE | 5G-NR
6moThanks a lot for sharing