NSA Mobility Managment.pptx

HUAWEI TECHNOLOGIES CO., LTD.
NR NSA Mobility
Management

HISILICON SEMICONDUCTOR
HUAWEI TECHNOLOGIES CO., LTD. Page 2
Contents
1. Terms & Definitions
2. Mobility Management Under NSA DC
3. Mobility Features
4. NSA Mobility Management
5. PSCell Change Process
6. Main Procedures
7. Feature Deployment Script
8. KPIs and Counters

Terms & Definitions
• EN-DC: Is short for E-UTRA-NR Dual Connectivity (DC) and represents dual connectivity between LTE and
New Radio (NR).
• NSA: Non-standalone.
• MN: Master Node.
• SN: Secondary Node.
• S-SN: Source Secondary Node.
• T-SN: Target Secondary Node.
• MCG: The Master Cell Group of an NSA DC UE is an LTE cell group configured on the LTE side.
• SCG: The Secondary Cell Group of an NSA DC UE is the NR cell group configured on the NR side.
• MeNB: The Master eNodeB of an NSA DC UE is the LTE eNodeB that serves the cell on which a UE is
currently camping.
• SgNB: The Secondary gNodeB of an NSA DC UE is the NR gNodeB configured for the UE through an
RRC message sent by the MeNB.
• PCell: Is the primary serving cell and represents a primary cell of the Master eNodeB.
• PSCell: Is the primary secondary cell and represents a primary cell of a Secondary gNodeB.

Mobility Management Under NSA DC
• In an EN-DC network, the eNodeB serves as the MN and connects to the EPC, and the gNodeB acts as the SN and
connects to the eNodeB over an X2 interface.
• The LTE network is used as an anchor; the UE can only camp on the LTE network and all idle mode mobility is
controlled by that layer. Other Vendor eNodeB cannot be used as an anchor for a Huawei gNodeB, so there will be no
5G service when the UE is on a other eNodeB.
• Since the LTE network is used as an anchor the 5G mobility strategy is dictated by the current 3G/4G mobility strategy
The current network strategy is that LTE1800 or LTE2100 cells can be used as the anchor but not LTE800 cells.
• All NR signaling messages are delivered through the eNodeB. The gNodeB sends measurement configurations to the
eNodeB through the X2 interface and the eNodeB then forwards these configurations to UEs. UEs report measurement
results to the eNodeB, and the eNodeB transfers the results to the gNodeB over the X2 interface to support PSCell
changes.
• The SgNB is responsible for its mobility management, including measurement control and RRC connection
reconfiguration.
• The X2 interface will be defined between sites (inter-site) but at the moment the issue is that there is no redundancy (if
the SeGW goes down). There isn’t any redundancy for the LTE X2 link either but the difference is that in LTE the S1 link
can be used if the X2 goes down.

Option 3x (SCG split bearer) The user-plane data is first transmitted from the core network to the
PDCP layer of the gNodeB. Then, the PDCP layer of the gNodeB distributes the data to the RLC layer of the eNodeB
through the X2 interface

Feature Deployment: License Packaging
Feature ID Feature Name Basic Or Optional Sales Unit Sales NE Control NE
FOFD-021209 Inter-RAT Mobility From NG-RAN to E-UTRAN Optional per Cell gNodeB gNodeB
FOFD-021210 Voice Fallback Optional per Cell gNodeB gNodeB
Feature ID Feature Name Basic Or Optional Sales Unit Sales NE Control NE
LEOFD-151330 Inter-RAT Mobility From E-UTRAN to NG-RAN Optional per Cell eNodeB eNodeB
LEOFD-151331 E-UTRAN to NG-RAN Traffic Steering Optional per Cell eNodeB eNodeB
LEOFD-151332 Fast Return From E-UTRAN to NG-RAN Optional per Cell eNodeB eNodeB
5G
4G FDD
Feature ID Feature Name Summary
FBFD-010014 Mobility Management
 NSA Mobility Management
 SA Mobility Management in
Connected Mode
 SA Mobility Management in
Idle Mode
5G

NSA Mobility Management
1. NSA access: same as LTE access.
2. The eNodeB delivers event B1 measurement configuration
for NR SgNB addition.
• Only coverage-based handover is
supported in the current release.
Mobility Scenario
SgNB addition
The eNodeB periodically adds an SgNB for a UE after an initial access, incoming
handover, incoming reestablishment, or initial addition failure.
SgNB change/modification
SgNB Modification: intra-frequency handover within a gNodeB
SgNB Change: intra-frequency handover between gNodeBs
MeNB handover with SgNB modification
Intra-frequency or inter-frequency handover within an eNodeB, or between
eNodeBs, based on event A3. The NR side initiates an RRC connection
reconfiguration, instructing the UE to re-access the cell.
SgNB release
The UE moves out of the gNodeB coverage area (event A2 is reported or RLC
retransmissions exceed the specified threshold) and the SgNB is released.
• Note: data forwarding during SgNB modification, change and release is supported.

Main Procedures: SgNB Addition Triggered by the MeNB
1. After receiving the B1 measurement report, the Huawei MeNB triggers an SgNB
addition procedure by sending an SgNB Addition Request message to the SgNB.
2. After the admission control is complete and the SgNB allocates resources, the
SgNB returns an SgNB Addition Request Acknowledge message to the MeNB.
3. The MeNB sends an RRC Connection Reconfiguration message to the UE. This
message contains the NR RRC configuration message.
4. The UE returns an RRC Connection Reconfiguration Complete message to the
MeNB, including the NR RRC response message.
5. The MeNB sends an SgNB Reconfiguration Complete message to the SgNB to
confirm that the UE has completed the reconfiguration procedure.
6. If the bearers configured for the UE require SCG radio resources, the UE
synchronizes with the SgNB PSCell and initiates random access to the SgNB
PSCell.
In the current network, blind PSCell addition and the initial data volume check are
disabled. Hence, the MeNB triggers measurement-based PSCell configuration (based
on B1 events) immediately if no VoLTE call is ongoing.

NSA Mobility Management
PSCell Change Within a Base Station PSCell Change Between Base Stations
PSCell is changed to another cell under the same
SgNB. In this case, the SgNB modification
procedure applies.
A PSCell is changed to another cell under a different SgNB.
In this case, the SgNB change procedure applies
In NR, event A3 is used to trigger a PSCell change. Event A3 indicates that the signal quality of a neighboring cell is higher
than that of the serving cell by a certain threshold. A maximum of four cells can be contained in one event A3
measurement report, and the number of times of reporting one measurement event is unlimited

PSCell Change Process
1. Measurement configuration delivery
• The gNodeB transfers measurement configurations to the LTE MeNB over the X2 interface and the LTE MeNB
forwards them to the UE.
• In 5G RAN2.1, only intra-frequency measurements based on event A3 are supported.
2. UE reporting of measurement results
• If the criteria for reporting an event A3 are satisfied, the UE reports the measurement results of the serving and
neighboring cells to the LTE MeNB and the LTE MeNB forwards the results to the SgNB through the X2 interface.
• Reporting criteria for event A3: The RSRP of a neighboring cell is greater than that of the serving cell by a certain
margin.
3. SgNB change/modification decision
• The gNodeB selects the cell with the best signal quality from the target cell list and attempts to perform an SgNB
change/modification.
4. SgNB change/modification execution
• The gNodeB performs the SgNB change/modification.
Type Condition Action
Entering
event A3
Mn + Ofn + Ocn – Hys > Ms
+ Ofs + Ocs + Off
Event A3 is reported for the
neighbouring cell.
Leaving
event A3
Mn + Ofn + Ocn + Hys < Ms
+ Ofs + Ocs + Off
Event A3 reporting is stopped for
the neighbouring cell.

Process-Intra-SgNB Change
UE MeNB
1. NR A3 Measure Control
2. NR A3 Measure Report
5. RRC CONN RECFG(NR Reconfig)
6. RRC CONN RECFG CMP
8. Random Access
SgNB
3. RRC Transfer (NR A3)
4. SgNB Mod Req
7. SgNB Modification Confirm
1. The SgNB sends an A3 measurement control message to the
UE.
2. The UE sends an event A3 measurement report to the MeNB.
3. The MeNB forwards the A3 measurement report to the SgNB.
4. The SgNB initiates a change request to the MeNB.
5. The MeNB sends a reconfiguration command to the UE,
carrying the NR configuration.
6. The UE sends a reconfiguration completion message to the
MeNB.
7. The MeNB forwards the reconfiguration completion message
to the SgNB.
8. The UE sends a random access request to the SgNB.
The eNodeB transparently transmits the NR A3
measurement report.

Process-Inter-SgNB Change
UE MeNB
2. NR A3 Measure Report
7. RRC CONN RECFG(NR Config)
S-SgNB
9. SgNB Change Confirm
MME
15. E-RAB Modification Indication
10. SgNB Reconfig CMP
16. E-RAB Modification Confirm
3. RRC Transfer (NR A3)
4. SgNB Change Required
5. SgNB Addition Request
6. SgNB Addition Request
Acknowledge
T-SgNB
12. SN Status Transfer
13. SN Status Transfer
1. The S-SgNB sends an A3 measurement control message to the UE.
2. The UE sends an A3 measurement report to the MeNB to report a
stronger NR neighboring cell.
3. The MeNB forwards the measurement information to the S-SgNB.
4. The S-SgNB initiates an NR change request to the MeNB.
5. The MeNB sends an NR addition request to the T-SgNB.
6. The T-SgNB sends an NR addition acknowledge message to the MeNB.
7. The MeNB sends a reconfiguration message to the UE, carrying NR
Config.
8. The UE sends a reconfiguration completion message to the MeNB.
9. The MeNB sends a reconfiguration confirmation message to the S-SgNB.
10. The MeNB sends a reconfiguration completion message to the T-SgNB.
11. The UE sends a random access request to the T-SgNB.
12. The S-SgNB sends an SN status transfer message to the MeNB (only
when the RLC mode is AM).
13. The MeNB forwards the SN status transfer message to the T-SgNB (only
when the RLC mode is AM).
14. The S-SgNB forwards data to the T-SgNB.
15. The MeNB sends a bearer change indication message to the core network.
16. The core network sends a bearer change confirmation message to the
MeNB.
17. The MeNB sends a context release request to the S-SgNB. 17. UE Context Release
14. Data
Forwarding
11. Random Access

Process-Intra-MeNB Handover
UE MeNB
1. LTE A3/A4 Measure Control
2. LTE A3/A4 Measure Report
5. RRC CONN RECFG(LTE intra-eNB HO CMD)
SgNB
3. SgNB Mod Req
4. SgNB Mod Req Ack
8. SgNB Reconfig CMP
6. Random Access
9. Random Access
1. The MeNB sends a measurement control message to the
UE.
2. The UE sends a measurement report to the MeNB to report
a stronger neighboring LTE cell.
3. When an LTE handover occurs and the key is changed, the
MeNB sends a modification request to the SgNB, instructing
the NR side to modify the PDCP key.
4. The SgNB sends a modification request acknowledge
message to the MeNB.
5. The MeNB sends an LTE handover command to the UE,
carrying the NR configuration.
6. The UE resends a random access request to the MeNB.
7. The UE sends a handover completion message to the
MeNB.
8. The MeNB sends a reconfiguration completion message to
the SgNB.
9. The UE sends a random access request to the SgNB.
This process is always initiated by the Huawei MeNB and it is based on the normal intra-
frequency and inter-frequency procedures used in LTE. It should be noted that in the current
design the PSCell is not changed during the MeNB handover procedure

Process-Inter-MeNB Handover
UE
S-
eNB
S-GW MME
1. LTE A3/A4 Measure Control
2. LTE A3/A4 Measure Report 3. HO Req
6. HO Req
Ack
8. RRC CONN
RECFG
10. RRC CONN RECFG
CMP
13. Path Switch
S-
gNB
14. UE Context Rel
7. SgNB Rel
Req
15. UE Context Rel
T-eNB
5. SgNB Add Req ACK
4. SgNB Add Req
12. SgNB Recfg
CMP
9. Random Access
11. Random Access
1. The S-eNB sends an LTE measurement control message to
the UE.
2. The UE sends a measurement report to the S-eNB,
indicating a stronger inter-eNodeB neighboring LTE cell.
3. The S-eNB sends a handover request to the T-eNB.
4. The T-eNB sends an addition request to the S-gNB.
5. The S-gNB sends an addition acknowledge message to the
T-eNB.
6. The T-eNB sends a handover acknowledge message to the
S-eNB.
7. The S-eNB sends a release request to the S-gNB.
8. The S-eNB sends an inter-eNodeB handover command to
the UE.
9. The UE sends a random access request to the target cell.
10. The UE sends a handover completion message to the
target LTE cell.
11. The UE sends a random access request to the S-gNB.
12. The T-eNB sends a reconfiguration completion message to
the S-gNB.
13. The T-eNB sends a path switch message to the core
network.
14. The T-eNB sends a context release request to the S-eNB.
15. The S-eNB sends a context release request to the S-gNB.
Important Notes:-
If the handover is from an MeNB to a Huawei eNB (that doesn’t support NSA DC), the SgNB is released before the MeNB
handover is executed.
If the handover is from an MeNB to a Samsung eNB, the SgNB is not released and 5G will be dropped after the handover.
Handover to LTE800 will result in the SgNB being released since the 3UK strategy is to only enable anchoring on LTE1800
and LTE2100 cells.

Process-SgNB Release
The SgNB release (PSCell deletion) can be triggered by either:-
1. The Huawei MeNB due to SCG link faulty or packets lost; or
2. The SgNB due to A2 threshold, UE inactivity, X2 delay or packets lost.
The coverage (A2) threshold is triggered if the PSCell RSRP decreases below a defined threshold:
Note that the A2 time to trigger is fixed (not configurable) at 640ms
1. After receiving the A2 measurement report the SgNB sends an SgNB Release
Required message to initiate an SgNB release procedure.
2. The MeNB sends an SgNB Release Confirm message to the SgNB to confirm that
the SgNB is released. After receiving this message, the SgNB stops sending data
to the UE.
3. NSA DC RRC disconnection is exactly the same as LTE RRC disconnection, so it
is not covered in this document.

Parameters to set on 4G sites to enable 5G mobility
# Set PSCell addition B1 threshold and time to trigger
MOD NRSCGFREQCONFIG: PccDlEarfcn=xxxx, ScgDlArfcn=*, ScgDlArfcnPriority=1, NsaDcB1ThldRsrp=-115,
NrB1TimeToTrigger=512MS;
# Point NSA DC UEs to the same mobility groups used by non-NSA DC UEs
MOD CELLQCIPARA: LOCALCELLID=0, QCI=1, NsaDcInterFreqHoGroupId=0, NsaDcInterRatHoCommGroupId=0, NsaDcUtranHoGroupId=0, NsaDcIntraFreqHoGroupId=0;

Parameters to set on 5G sites to enable Mobility
# Define Intra-frequency handover group
MOD NRCELLQCIBEARER: NrCellId=101, Qci=1, IntraFreqHoMeasGroupId=0;
# Set Intra-frequency handover parameters
MOD NRCELLINTRAFHOMEAGRP: NrCellId=101, IntraFreqHoMeasGroupId=0, IntraFreqHoA3Offset=2, IntraFreqHoA3Hyst=2, IntraFreqHoA3TimeToTrig=320MS;
# Set filter coefficients for measurements
MOD NRCELLMOBILITYCONFIG: NrCellId=101, BeamRsrpFilterCoeff=FC4, CellRsrpFilterCoeff=FC4;
# Set coverage A2 threshold for PSCell removal
MOD NRCellNsaDcConfig: NrCellId=101, PscellA2RsrpThld=-121;

Main KPIs Formulas
KPI name KPI formula
Success rate of PCell change L.NsaDc.PCell.Change.Succ/L.NsaDc.PCell.Change.Exec x 100%
SgNB addition success rate L.NsaDc.SgNB.Add.Succ/L.NsaDc.SgNB.Add.Att x 100%
[SgNB addition success rate] ( [N.NsaDc.SgNB.Add.Succ] / [N.NsaDc.SgNB.Add.Att] )*{100}
[Intra-SgNB PSCell change success rate] ( [N.NsaDc.IntraSgNB.PSCell.Change.Succ] / [N.NsaDc.IntraSgNB.PSCell.Change.Att] )*{100}
[Inter-SgNB PSCell change success rate] ( [N.NsaDc.InterSgNB.PSCell.Change.Succ] / [N.NsaDc.InterSgNB.PSCell.Change.Att] )*{100}
NR drop rate ( [N.NsaDc.SgNB.AbnormRel] / [N.NsaDc.SgNB.Rel] )*{100}
User Downlink Average Throughput(NR) User Downlink Average Throughput(NR) = (N.ThpVol.DL - N.ThpVol.DL.LastSlot) / N.ThpTime.DL.RmvLastSlot
User Uplink Average Throughput(NR) User Uplink Average Throughput(NR) = (N.ThpVol.UL- N.ThpVol.UE.UL.SmallPkt) / N.ThpTime.UE.UL.RmvSmallPkt
Cell Downlink Average Throughput Cell Downlink Average Throughput = N.ThpVol.DL.Cell / N.ThpTime.DL.Cell
Cell Uplink Average Throughput Cell Uplink Average Throughput = N.ThpVol.UL.Cell / N.ThpTime.UL.Cell
Downlink Resource Block Utilizing Rate Downlink Resource Block Utilizing Rate =(N.PRB.DL.Used.Avg/N.PRB.DL.Avail.Avg)× 100%
Uplink Resource Block Utilizing Rate Uplink Resource Block Utilizing Rate =(N.PRB.UL.Used.Avg/N.PRB.UL.Avail.Avg)× 100%
Radio Network Unavailability Rate Radio Network Unavailability Rate =( [N.Cell.Unavail.Dur.System.Avg] + [N.Cell.Unavail.Dur.Manual.Avg] )/({GP}*{60})*100
Downlink Traffic Volume Downlink Traffic Volume =N.ThpVol.DL
Uplink Traffic Volume Uplink Traffic Volume = N.ThpVol.UL
Average User Number
NSA:
Average User Number =N.User.RRCConn.Avg
[DRB setup success rate] ( [N.NsaDc.DRB.Add.Succ] / [N.NsaDc.DRB.Add.Att] )*{100}

LTE Counter- NSA DC Counters
Counter ID Counter Name Counter Description
1526747851 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
1526747852 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
1526747853 L.NsaDc.SCG.Change.Att Total number of SCG change attempts for UEs that treat the local cell as their PCell in the LTE-NR NSA DC state
1526747854 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
1526747855 L.NsaDc.SgNB.Rmv.Att Total number of SgNB removal attempts for UEs that treat the local cell as their PCell in the LTE-NR NSA DC state
1526747856 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
1526748735 L.NsaDc.PCell.Change.Exec Number of PCell change executions in LTE-NR NSA DC scenarios
1526748736 L.NsaDc.PCell.Change.Succ Number of successful PCell changes in LTE-NR NSA DC scenarios
1526748737 L.NsaDc.E-RAB.AbnormRel Total number of abnormal E-RAB releases in LTE-NR NSA DC scenarios
1526748825 L.NsaDc.SCG.Mod.Req.Att Number of SCG modification attempts for UEs that treat the local cell as their PCell in the LTE-NR NSA DC state
1526748826 L.NsaDc.SCG.Mod.Req.Succ Number of successful SCG modifications for UEs that treat the local cell as their PCell in the LTE-NR NSA DC state
1526748827 L.NsaDc.SCG.Mod.Required.Att Number of SCG modification attempts received by UEs in the LTE-NR NSA DC state in a cell
1526748828 L.NsaDc.SCG.Mod.Required.Succ Number of successful SCG modifications received by UEs in the LTE-NR NSA DC state in a cell
1526748829 L.NsaDc.E-RAB.Mod.Ind.Att Number of E-RAB modification attempts initiated by UEs in the LTE-NR NSA DC state in a cell
1526748830 L.NsaDc.E-RAB.Mod.Ind.Succ Number of successful E-RAB modifications initiated by UEs in the LTE-NR NSA DC state in a cell
1526755742 L.NsaDc.E-RAB.NormRel Total number of normal E-RAB releases for NSA DC UEs
1526755743 L.NsaDc.HHO.PrepAttOut Number of outgoing handover preparation attempts for NSA DC UEs
1526755744 L.NsaDc.HHO.ExecAttOut Number of outgoing handover executions for NSA DC UEs
1526755745 L.NsaDc.HHO.ExecSuccOut Number of successful outgoing handovers for NSA DC UEs

5G Counters- NSA DC Measurements
Counter ID Counter Name Counter Description
1911816746 N.NsaDc.SgNB.Add.Att Number of SgNB addition requests in the LTE-NR NSA DC scenario
1911816747 N.NsaDc.SgNB.Add.Succ Number of successful SgNB additions in the LTE-NR NSA DC scenario
1911816748 N.NsaDc.InterSgNB.PSCell.Change.Att Number of inter-SgNB PSCell change requests in the LTE-NR NSA DC scenario
1911816749 N.NsaDc.InterSgNB.PSCell.Change.Succ Number of successful inter-SgNB PSCell changes in the LTE-NR NSA DC scenario
1911816750 N.NsaDc.IntraSgNB.PSCell.Change.Att Number of intra-SgNB PSCell change requests in the LTE-NR NSA DC scenario
1911816751 N.NsaDc.IntraSgNB.PSCell.Change.Succ Number of successful intra-SgNB PSCell changes in the LTE-NR NSA DC scenario
1911816752 N.NsaDc.SgNB.Rel Total number of SgNB releases in the LTE-NR NSA DC scenario
1911816753 N.NsaDc.SgNB.AbnormRel.Radio Total number of abnormal SgNB releases in the LTE-NR NSA DC scenarios caused by radio layer issues
1911816754 N.NsaDc.DRB.Add.Att Number of DRB addition requests for LTE-NR NSA DC UEs on the SgNB
1911816755 N.NsaDc.DRB.Add.Succ Number of successful DRB additions for LTE-NR NSA DC UEs on the SgNB
1911816756 N.NsaDc.DRB.Rel Number of DRB releases for LTE-NR NSA DC UEs on the SgNB
1911816757 N.NsaDc.DRB.AbnormRel Number of abnormal DRB releases for LTE-NR NSA DC UEs on the SgNB
1911816836 N.NsaDc.SgNB.AbnormRel.Radio.SUL Total number of abnormal SgNB releases in the LTE-NR NSA DC scenarios caused by radio layer issues of the SUL
1911816843 N.NsaDc.SgNB.Rel.Coverage Number of coverage-based SgNB releases in LTE-NR NSA DC scenarios
1911817841 N.NsaDc.SgNB.Rel.SgNBTrigger Total number of SgNB releases triggered by SgNB in LTE-NR NSA DC scenarios
1911817842 N.NsaDc.SgNB.AbnormRel.Trans Total Number of abnormal SgNB releases due to the transport layer in LTE-NR NSA DC scenarios
1911817843 N.NsaDc.SgNB.AbnormRel Total number of abnormal SgNB releases triggered by SgNB in LTE-NR NSA DC scenarios
1911817848 N.NsaDc.IntraSgNB.PSCell.Change.Fail.Conflict Number of intra-SgNB PSCell change failures caused by procedure conflicts in LTE-NR NSA DC scenarios
1911817849 N.NsaDc.InterSgNB.PSCell.Change.Fail.Conflict Number of inter-SgNB PSCell change failures caused by procedure conflicts in LTE-NR NSA DC scenarios
1911817850 N.NsaDc.SgNB.Mod.Req.Fail.Radio Number of failures of SgNB modifications initiated by the MeNB due to radio faults in LTE-NR NSA DC scenarios
1911817851 N.NsaDc.SgNB.Mod.Req.Fail.TNL
Number of failures of SgNB modifications initiated by the MeNB due to transmission faults in LTE-NR NSA DC
scenarios
1911817852 N.NsaDc.SgNB.Mod.Req.Succ Number of successful SgNB modifications initiated by the MeNB in LTE-NR NSA DC scenarios
1911817853 N.NsaDc.SgNB.Mod.Req.Att Number of SgNB modification attempts initiated by the MeNB in LTE-NR NSA DC scenarios
1911817854 N.NsaDc.SgNB.Add.Fail.Radio Number of SgNB addition failures caused by radio faults in LTE-NR NSA DC scenarios
1911817855 N.NsaDc.SgNB.Add.Fail.Radio.NoRes Number of SgNB addition failures caused by the unavailability of radio resources in LTE-NR NSA DC scenarios
1911817856 N.NsaDc.SgNB.Add.Fail.TNL Number of SgNB addition failures caused by transmission faults in LTE-NR NSA DC scenarios
1911817857 N.NsaDc.SgNB.AbnormRel.Radio.UeLost Number of abnormal SgNB releases initiated by the SgNB caused by UE LOST
1911817858 N.NsaDc.SgNB.AbnormRel.NoReply Number of abnormal SgNB releases initiated by the SgNB caused by no response

5G NR – Inter-SgNB PSCell Change SR [BXXXXX]
BYYYYY OA @ 27th Feb 2020
Summary:-
 From SON log analysis, X2 interface wasn’t established earlier although neighbor external cell has been defined due to maximum x2
interface(384) reached for this site.
 X2 interface between Site BXXXXX and BYYYYY was established on 3rd March 2020; issue resolved after X2 interface between gNB
created.
1.17k
m
3843
11869
Analysis:-
From trace found out the
SGNB_Change_Refuse due to failure of
“Transport-resource-unvailable”

5G NR – [Analysis] Inter-SgNB Change SR
From MAN101 BRD, main inter-SgNB change failure due to
“X2_SGNB_CHANGE_REFUSE/TRANSP_RSRC_UNAVAILABLE_CAU
SE_TRANSP”
MAN004 LTE X2 interface
MAN004
(615)
MAN101 (751)
MAN101
(751)
MAN004 (615)
MAN101 LTE X2 interface
From BRD of MAN101, main failure due
to
“X2_SGNB_CHANGE_REFUSE/TRANS
P_RSRC_UNAVAILABLE_CAUSE_TR
ANSP “; further check found MAN004
and MAN101 X2 are facing SCTP link
issue; which suspect causing the failures
on inter-SgNB change.
Issue normalizing after 28th March.

NSA Mobility Managment.pptx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to NSA Mobility Managment.pptx

Similar to NSA Mobility Managment.pptx (20)

Recently uploaded

Recently uploaded (20)

NSA Mobility Managment.pptx