1- What do you mean by Low correlated Users

or Users being separated in the spatial

domain?
It simply means that users should be geographically separated; in other words, it
means that each user is served by different beams.

And you need to consider that the performance of Multi-User MIMO is likely to be
comprised if users are clustered together at one location.

2- Does Multi-user MIMO only work with

Massive MIMO?
Multiuser MIMO is not restricted to Massive MIMO and can be supported by smaller
antenna systems such as 8T8R.

However, the smaller antenna system has a lower beamforming gain. Accordingly,
the Massive MIMO System will have less beamforming and Multiuser -performance
gain.
3- Does Multi-user MIMO work by both analog
and digital beamforming?
Multiuser MIMO is only supported by digital beamforming. And this is because analog
beamforming can generate only a single beam.
4- Is it possible for Paired Users to operate
with Rank4 during Multi-User MIMO?
As per 3GPP, Vendors should provide the assumptions of the maximum supported
ranking during Multi-User MIMO.

However, Multi-User MIMO is typically associated with lower Order MIMO. Maximum
2X2 MIMO can be supported in 5G because it becomes difficult to identify sufficient
uncorrelated propagation paths toward each UE.

Hence, a lower ranking might impact the maximum speed in some particular
scenarios, so it is recommended to enable MU-MIMO in high traffic demands sites and
to go through all related MU-MIMO Triggering conditions/parameters to ensure that
MU-MIMO is taking more effect in High-Traffic.
5- What are the main differences between 4G
& 5G Multi-User MIMO?
There are no major differences between 4G & 5G.

Both support up to 16 Paired Layers in Downlink and 8 Layers for Uplink (64T64R)

However, the main difference is that only 5G can support PDCCH Multi-User MIMO.

6- How to measure the performance of Multi-

User MIMO?
You need to verify/monitor the performance of Multi-User MIMO from both Fields and
KPIs:

From field testing, you can verify through simulating a test like the previously
illustrated User throughput and cell throughput testing, Where Multiple Drive testers
are allocated in different directions, and each is performing download in sequence to
gauge the impact on both User throughput and Cell Throughput.

From KPIs: You can verify through the following:

1- Traffic distribution per Layer to check the maximum supported Layers.

2- Disable MU-MIMI to gauge the impact during high-traffic scenarios.

3- Check the Transmission Mode Distribution in 4G, Beamforming Modes(TM7 & TM8
expected to be higher in High Load Scenarios)
VoLTE Traffic Model & VoLTE Bearers(Training Session#1)
This training session focuses on 4G & 5G voice services, 𝗶𝗻𝗰𝗹𝘂𝗱𝗶𝗻𝗴 𝗩𝗼𝗡𝗥, 𝗩𝗼𝗟𝗧𝗘,
𝗮𝗻𝗱 𝗘𝗣𝗦 𝗙𝗮𝗹𝗹𝗯𝗮𝗰𝗸. The comprehensive End-to-End (E2E) VoLTE Training will cover an

using logs, and main features. 𝗜𝗻 𝘁𝗵𝗶𝘀 𝘃𝗶𝗱𝗲𝗼, 𝘄𝗲 𝘄𝗶𝗹𝗹 𝗰𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴
overview of VoLTE, including traffic models, IMS architecture, end-to-end call flow analysis

𝘁𝗼𝗽𝗶𝗰𝘀:

1- Introduction(Contents)

2- VoLTE Introduction Overview

3- Traffic Model Scheme and Speech Codec

4- High-level Overview of VoLTE/IMS Architecture

5- VoLTE Bearers and Protocols

6- High-Level VoLTE Call Procedures

Deep Dive into E2E 5G NSA Accessibility Signaling and

Failures: Your Complete Handbook(Article)

Mohamed ELAdawi
Apr 8, 2024 — 13 min read
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 amp; Measurement Report

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:
 ERAB ID and DRB mapping information
 ENDC (Evolved-Universal Terrestrial Radio Access-New Radio Dual Connectivity) bearer type
 ERAB QoS (Quality of Service) parameters
 eNodeB IP address and Tunnel Endpoint ID (TEID) for X2-U
 Serving Gateway (SGW) IP address and TEID for S1-U
 UE (User Equipment) NR capabilities
 Target gNodeB cell measurement information

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.

 Candidate cell information: Indicate the target cell PCI and SSB RSRP
 Maximum allowed UE Power For EUTRAN & NR, each 20 dBm
 E-RAB QoS parameters
 MeNB-DL-GTP-TEIDatMCG: eNodeB IP and TE ID for X2-U spilt bearer
 S1-UL-GTPtunnelEndpoint: SGW IP and TEID (Option3x)
 Masked-IMEISV: information which can be used to get the device type.
 SPID: Subscriber profile ID Feature
 (4) SgNB Addition Request Ack:

The SgNB Addition Acknowledgment message will include the following key information from
the gNodeB:
 NR cell configuration, which will be relayed to the UE via LTE messaging.
 gNodeB IP address and Tunnel Endpoint ID (TEID). Two TEIDs will be assigned for the S1-U IP path and
X2-U split bearer, while an additional two TEIDs will be designated for temporary data forwarding during
the SCG addition procedure.

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.

 SgNB IP and TEID for S1 IP path.

 SgNB IP and TEID for X2 split bearer.
 SgNB IP and TEID for X2 DL forwarding bearer during the addition procedure.
 SgNB IP and TEID for X2 UL forwarding bearer during the addition procedure.
 MCG E-RAB QoS Parameter.
 (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:
 CellGroupConfig: This configuration encompasses settings for RLC/MAC/PHY and spcellConfig for the
primary NR cell.
 spCellconfiguration: This section includes ReconfigWithSync (for initial access synchronization), RLF
(Radio Link Failure) timer, and spCelldedicated. The ReconfigWithSync component incorporates
spCellcomm and RACH dedicated (non-contention-based random access for NSA).
 MeasConfig: This conveys the measurement configuration specific to NR.
 SCG-RB-Config: This delivers parameters for uplink traffic split and the primary data path.
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.

 SCG RLC/MAC/PHY Protocol Layer Configuration: This pertains to the protocol layer configuration
specifically for the Secondary Cell Group (SCG) in the NR context.
 ReconfigWithSync: This includes parameters related to UE random access, comprising both common and
dedicated configurations.
 spCellConfigDedicated: This configuration is utilized to set up the dedicated Bandwidth Part (BWP) for
the UE within the Secondary Cell Group (SCG).
 NR A2/A3 Event Measurement Configuration for NSA Mobility: This specifies the configuration for NR
mobility event measurements (A2/A3 events) relevant to Non-Standalone Access (NSA) scenarios.
 SCG UL Data Split Parameters: These parameters define the parameters for splitting uplink (UL) data
within the Secondary Cell Group (SCG).
 (6) E-RAB Modification Indication:

 The 4G Master Node initiates the signaling which is used to move the S1-U connection from the 4G
Master Node to the 5G Secondary Node. This is done by sending an S1AP: E-RAB Modification Indication
to the MME.

 The E-RAB to be modified List provides the Transport Layer Address and DL GRP TEID provide by the 5G
Secondary Node within the X2AP: SGNB Addition Request Acknowledge.
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.

E2E VoLTE Training (Semi-Persistent Scheduling, Packet
Bundling, Delay based Scheduling) - Session 8

This is the final session of the VoLTE E2E 𝗙𝗿𝗲𝗲 𝗧𝗿𝗮𝗶𝗻𝗶𝗻𝗴 on my YouTube Channel. The 4-
hour training covers extensive content(Highlighted below), which took over a month to prepare.
I believe this material is highly valuable and difficult not easy to find in other free or even paid
sources. While there's more to explore about VoLTE, the content presented here is
comprehensive enough to take you from beginner to advanced level. I kindly ask those who
watched the series to share their feedback, whether positive or negative, as it will help me
improve further. If you enjoyed the content, please subscribe to my YouTube channel. Stay
tuned for the next training about VONR

1- VoLTE Overview- 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗱 (1 Video)

2- E2E IMS & EPC Registration flow and Capabilities check- 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗱 (1 Video)
3- E2E VoLTE MO Call Flow using Logs- 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗱 (1 Video)
4- E2E VoLTE MT Call Flow using Logs- 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗱 (1 Video)
5- VoLTE RAN Features - 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗱 (4 Sessions)
 YouTube video for the same:
References:
 3GPP TS 37.340
 3GPP TS 38.423
 5G NR in Bullets