Features and related Counters
NokiaEDU
Features and related Counters
5G Performance and Optimization principles for
Nokia customers [5G19]
RA57340-V-19
© Nokia 2019
RA57340-V-19
1
Features and related Counters
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of the
applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No
part of this document may be reproduced or made
available to the public or to any third party in any
form or means without the prior written permission
of Nokia. This document is to be used by properly
trained professional personnel. Any use of the
contents in this document is limited strictly to the
use(s) specifically created in the applicable
agreement(s) under which the document is
submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback").
2
Such Feedback may be used in Nokia products and
related specifications or other documentation.
Accordingly, if the user of this document gives Nokia
Feedback on the contents of this document, Nokia
may freely use, disclose, reproduce, license,
distribute and otherwise commercialize the
feedback in any Nokia product, technology, service,
specification or other documentation.
are made in relation to the accuracy, reliability or
contents of this document. NOKIA SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT or for any loss of data or income or any
special, incidental, consequential, indirect or direct
damages howsoever caused, that might arise from
the use of this document or any contents of this
document.
Nokia operates a policy of ongoing development.
Nokia reserves the right to make changes and
improvements to any of the products and/or
services described in this document or withdraw this
document at any time without prior notice.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties
of any kind, either express or implied, including, but
not limited to, the implied warranties of
merchantability and fitness for a particular purpose,
RA57340-V-19
Nokia is a registered trademark of Nokia
Corporation. Other product and company names
mentioned herein may be trademarks or trade
names of their respective owners.
© Nokia 2019
RA57340-V-19
Features and related Counters
Module Objective
After completing this learning element, the participant should be able to:
Restate F1 Link Management
Recall NSA Call
List 5G - LTE flow control at X2
Explain Radio Admission Control
Relate Radio Link Failure
Review UE Inactivity
4
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
5
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
6
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
F1 Link Management
Description 5GC000481: F1 Link Management
The 5GC000481: F1 Link Management feature allows the operator to establish and maintain an F1 connection.
F1 interface procedures:
• The F1 Application Protocol (F1AP) F1 setup procedure initiated by the NR NodeB Distributed Unit (gNB-DU) is the first
procedure to be processed after the F1-C transport link establishment. The F1 setup procedure allows to set F1AP interface
available for further F1AP procedures which might be UE-associated or non-UE-associated.
• The F1AP reset is used to initialize the peer entity after a failure event. It might be trigged either by gNB-DU or by gNB-CU. The
procedure might concern a partial reset or a full reset.
• The F1AP error indication is used by the receiver (gNB-DU/gNB-CU) to indicate the sender (gNB-CU/gNB-DU) that an error
has been detected upon receipt of an F1AP message.
7
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
F1 Link Management
F1 Link Management Connectivity
8
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
F1 Link Management
Performance Management - related Counters
9
Counter ID
NetAct Name
Network Element Name
M55117C01501
F1_CU_SETUP_REQUEST_RCV
Number of F1AP: F1 Setup Request message received by gNB-CU
M55117C01502
F1_CU_SETUP_REQUEST_RCV_PT_ERR
Number of F1AP: F1 Setup Request message received by gNB-CU with protocol error
M55117C01503
F1_CU_SETUP_RESPONSE_SENT
Number of F1AP: F1 Setup Response message sent by gNB-CU
M55117C01504
F1_CU_SETUP_FAILURE_SENT
Number of F1AP: F1 Setup Failure message sent by gNB-CU
M55117C01505
F1_SETUP_ATT
Number of F1AP: F1 Setup procedure attempted
M55117C01506
F1_SETUP_SUCC
Number of F1AP: F1 Setup procedure successful
M55117C01507
F1_SETUP_FAIL
Number of F1AP: F1 Setup procedure unsuccessful
M55117C01508
F1_SETUP_FAIL_NO_RESP
Number of unsuccessful F1AP: F1 Setup procedure due to no response
M55117C01509
F1_SETUP_FAIL_OVERLOAD
Number of unsuccessful F1AP: F1 Setup procedure due to overload
M55117C01510
F1_SETUP_FAIL_PROT_ERR
Number of unsuccessful F1AP: F1 Setup procedure due to protocol error
M55117C01511
F1_DU_RESET_RCV_PROT_ERR
Number of F1AP: Reset message received with protocol error by gNB-DU
M55117C01512
F1_DU_P_RESET_RCV
Number of partial F1AP: Reset message received by gNB-DU
M55117C01513
F1_DU_P_RESET_ACK_SENT
Number of partial F1AP: Reset Acknowledge message sent by gNB-DU
M55117C01514
F1_DU_P_RESET_ATT
Number of partial F1AP: Reset procedure attempted by gNB-DU
M55117C01515
F1_DU_P_RESET_SUCC
Number of successfull partial F1AP: Reset procedure completed by gNB-DU
M55117C01516
F1_DU_P_RESET_FAIL
Number of unsuccessful partial F1AP: Reset procedure initiated by gNB-DU
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
F1 Link Management
Performance Management - related Counters
10
Counter ID
NetAct Name
Network Element Name
M55117C01517
F1_DU_P_RESET_FAIL_NRESP
Number of unsuccessful partial F1AP: Reset procedure initiated by gNB-DU due to no response
M55117C01518
F1_DU_G_RESET_RCV
Number of global F1AP: Reset message received by gNB-DU
M55117C01519
F1_DU_G_RESET_ACK_SENT
Number of global F1AP: Reset Acknowledge message sent by gNB-DU
M55117C01520
F1_DU_G_RESET_ATT
Number of global F1AP: Reset procedure attempted by gNB-DU
M55117C01521
F1_DU_G_RESET_SUCC
Number of successfull global F1AP: Reset procedure completed by gNB-DU
M55117C01522
F1_DU_G_RESET_FAIL
Number of unsuccessful global F1AP: Reset procedure initiated by gNB-DU
M55117C01523
F1_DU_G_RESET_FAIL_NRESP
Number of unsuccessful global F1AP: Reset procedure initiated by gNB-DU due to no response
M55117C01524
F1_DU_RESET_FAIL_PROT_ERR
Number of unsuccessful F1AP: Reset procedure initiated by gNB-DU due to protocol error
M55117C01530
F1_DU_ERROR_IND_SENT
Number of F1AP: F1 Error Indication message sent by gNB-DU
M55117C01531
F1_DU_ERROR_IND_RCV
Number of F1AP: F1 Error Indication message is received by gNB-DU
M55117C01532
F1_DU_ERROR_IND_RCV_ERR
Number of F1AP: F1 Error Indication message is received with protocol error by gNB-DU
M55117C01533
F1_DU_UNKNOWN_MSG_RCV
Number of failed decoding or unknown F1AP message received by gNB-DU
M55117C01534
F1_CU_RESET_RCV_PROT_ERR
Number of F1AP: Reset message received with protocol error by gNB-CU
M55117C01535
F1_CU_P_RESET_RCV
Number of partial F1AP: Reset message received by gNB-CU
M55117C01536
F1_CU_P_RESET_ACK_SENT
Number of partial F1AP: Reset Acknowledge message sent by gNB-CU
M55117C01537
F1_CU_P_RESET_ATT
Number of partial F1AP: Reset procedure attempted by gNB-CU
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
F1 Link Management
Performance Management - related Counters
11
Counter ID
NetAct Name
Network Element Name
M55117C01538
F1_CU_P_RESET_SUCC
Number of successfull partial F1AP: Reset procedure completed by gNB-CU
M55117C01539
F1_CU_P_RESET_FAIL
Number of unsuccessful partial F1AP: Reset procedure initiated by gNB-CU
M55117C01540
F1_CU_P_RESET_FAIL_NRESP
Number of unsuccessful partial F1AP: Reset procedure initiated by gNB-CU due to no response
M55117C01541
F1_CU_G_RESET_RCV
Number of global F1AP: Reset message received by gNB-CU
M55117C01542
F1_CU_G_RESET_ACK_SENT
Number of global F1AP: Reset Acknowledge message sent by gNB-CU
M55117C01543
F1_CU_G_RESET_ATT
Number of global F1AP: Reset procedure attempted by gNB-CU
M55117C01544
F1_CU_G_RESET_SUCC
Number of successfull global F1AP: Reset procedure completed by gNB-CU
M55117C01545
F1_CU_G_RESET_FAIL
Number of unsuccessful global F1AP: Reset procedure initiated by gNB-CU
M55117C01546
F1_CU_G_RESET_FAIL_NRESP
Number of unsuccessful global F1AP: Reset procedure initiated by gNB-CU due to no response
M55117C01547
F1_CU_RESET_FAIL_PROT_ERR
Number of unsuccessful F1AP: Reset procedure initiated by gNB-CU due to protocol error
M55117C01548
F1_CU_ERROR_IND_SENT
Number of F1AP: F1 Error Indication message sent by gNB-CU
M55117C01549
F1_CU_ERROR_IND_RCV
Number of F1AP: F1 Error Indication message is received by gNB-CU
M55117C01550
F1_CU_ERROR_IND_RCV_ERR
Number of F1AP: F1 Error Indication message is received with protocol error by gNB-CU
M55117C01551
F1_CU_UNKNOWN_MSG_RCV
Number of failed decoding or unknown F1AP message received by gNB-CU
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
12
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
NSA Call
Main Idea of the Feature and Advantages
The 5GC000509: L3 Non Standalone Call with Data Transmission feature introduces the support of Layer 3 (L3) call in gNB,
for data transmission between UE and Serving Gateway (S-GW), NSA mode 3x.
Data transmission is supported for Uplink (UL) and Downlink (DL). This feature includes:
• UE context setup and DRB establishment
• Contention (free or based) random access
• User data transfer through the SgNB
• UE context release
Covers the end-to-end data transmission without data forwarding and data split over X2, which are introduced by other
features:
5GC000475: SgNB Addition and Release for NSA Mode 3x Operation and
5GC000570: 5G - LTE Flow Control at X2.
Benefit: data transmission bit rate increase
13
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
NSA Call
Performance Management - related Counters
14
Counter ID
NetAct Name
Network Element Name
M55112C00502
SGNB_REL_SN_REQ_UE_LOST
Number of SGNB RELEASE REQUIRED message sent with cause equal to Radio Connection With UE lost
M55112C01001
NX2CC_UE_RELEASE_ABNORMAL
Number of UE Release due to abnormal reasons
M55112C01002
NX2CC_BEARER_FAIL_TYP_NOT_SUPP
Number of bearer addition failures due to bearer type mismatch
M55112C01003
NX2CC_BEARER_FAIL_SEC_NOT_SUPP
Number of bearer addition failures due to security algorithm mismatch
M55112C01004
NX2CC_BEARER_FAIL_QCI_NOT_SUPP
Number of bearer addition failures due to QCI related errors
M55112C01005
NX2CC_BEARER_FAIL_IP_NOT_SUPP
Number of bearer addition failures due to IP version mismatch
M55112C01006
NX2CC_BEARER_FAIL_MISC
Number of UE Context Setup failure due to all other causes
M55113C01001
NF1CC_UECTXT_STP_REQSENT
Number of Ue Context Setup Requests sent
M55113C01002
NF1CC_UECTXT_STP_RESPRECD
Number of Ue Context Setup Response received
M55113C01003
NF1CC_UECTXT_STP_QCINOTSUPP
Number of UE Context Setup failure due to QCI related errors
M55113C01004
NF1CC_UECTXT_STP_IPNOTSUPP
Number of UE Context Setup failure due to IP version mismatch
M55113C01005
NF1CC_UECTXT_STP_FAILMISC
Number of UE Context Setup failure due to all other causes
M55113C01006
NF1CC_UECTXT_MOD_REQRECD
Number of UE Context Modification Required received
M55113C01008
NF1CC_UECTXT_REL_REQRECD
Number of Ue Context Release Request received
M55113C01009
NF1CC_UECTXT_REL_CMDSENT
Number of Ue Context Release Command sent
M55113C01010
NF1CC_UE_CTXT_REL_CMP_RECD
Number of Ue Context Release Complete received
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
NSA Call
Performance Management - related Counters
15
Counter ID
NetAct Name
Network Element Name
M55113C01011
NF1CC_UECTXT_MOD_CNFSENT
Number of UE Context Modification Confirm sent
M55116C00013
RLF_INITIATED_UE_SCG_RECNF_F
The number of UEs rejected due to RLF initiated by UE with the root cause SCG reconfig failure.
M55117C01001
NF1CD_UECTXT_STP_REQRECD
Number of Ue Context Setup requests received
M55117C01002
NF1CD_UECTXT_STP_RESPSENT
Number of Ue Context setup response sent
M55117C01003
NF1CD_UECTXT_STP_QCINOTSUPP
Number of UE Context Setup failure due to QCI related errors
M55117C01004
NF1CD_UECTXT_STP_IPNOTSUPP
Number of UE Context Setup failure due to IP version mismatch
M55117C01005
NF1CD_UECTXT_STP_FAILMISC
Number of UE Context Setup failure due to all other causes
M55117C01006
NF1CD_UECTXT_MOD_REQSENT
Number of UE Context Modification Required sent
M55117C01008
NF1CD_UECTXT_REL_REQSENT
Number of Ue Context Release Requests sent
M55117C01009
NF1CD_UECTXT_REL_CMDRECD
Number of Ue Context Release Command received
M55117C01010
NF1CD_UECTXT_REL_CMPSENT
Number of Ue Context Release Complete sent
M55117C01011
NF1CD_UECTXT_MOD_CNFRECD
Number of UE Context Modification Confirm received
M55315C00001..20
DL_PDCP_SDU_RCV_S1U_QOS_GRP_01..20
Number of downlink PDCP SDU received over NR S1-U DL GTP-U tunnel - QoS Group 01..20
M55315C01001..20
DL_PDCP_VOL_RCV_S1U_QOS_GRP_01..20
Downlink data volume received over NR S1-U DL GTP-U tunnel - QoS Group 01..20
M55315C02001..20
UL_PDCP_SDU_SNT_S1U_QOS_GRP_01..20
Number of Uplink PDCP SDU sent over NR S1-U UL GTP-U tunnel - QoS Group 01..20
M55315C03001..20
UL_PDCP_VOL_SNT_S1U_QOS_GRP_01..20
Uplink data volume sent over NR S1-U UL GTP-U tunnel - QoS Group 01..20
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
NSA Call
UE Context Setup
5G-CP-RT shall perform QCI Validation.
5G-CP-RT shall perform IP Address version
validation.
5G-CP-RT shall retrieve the QCI from EUTRAN QoS IE.
16
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
NSA Call
UE Context Setup Failures
Cell level: NF1CC_UECTXT_STP_QCINOTSUPP
Incremented when F1AP: UE CONTEXT SETUP
FAILURE is received with causes associated with QCI
related failures
Cell level: NF1CC_UECTXT_STP_IPNOTSUPP
Incremented when F1AP: UE CONTEXT SETUP
FAILURE is received with Cause: Transport Resource
unavailable
Cell level: NF1CC_UECTXT_STP_FAILMISC
Incremented when F1AP: UE CONTEXT
MODIFICATION REQUIRED with Cause: RLC Failure
is received in gNB-CU
17
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
18
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
5GC000630 F1-U Interface
•
•
The feature introduce the support for F1-U Interface between gNB CU and gNB DU which
implies PDCP-RLC split over F1 Interface
The feature introduces the user plane data protocol, a flow control and a fast
retransmission of lost PDUs at the F1-U interface.
PDCP-RLC split.
– PDCP-RLC split for UserPlane is agreed in 3GPP. This mean that the PDCP functions are to be
hosted on the gNB-CU and RLC function are to be hosted on the gNB-DU. The data transfer
between gNB-CU and gNB-DU is done using F1-U Interface.
F1-U Interface
– Support for F1-U and F1AP in gNB CU and gNB DU
Nokia Internal Use
19
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
5G Non-Standalone Architecture
F1 part
SgNB
DC UE
The Dual Connectivity and the split bearer
are combined together in the 5G-LTE
interworking.
The Control Plane will always go over the
LTE layer.
The data bearers to the DC-enabled UE can
go over LTE or over 5G.
X2 part
The data bearer that goes over 5G radio
can be split and sent partially over 5G
radio (using F1 interface) and partially
over LTE radio (with data packets relayed
over X2 connection).
S1-U
X2
S1-U
S1-C
MeNB
EPC
Split bearer – Control Plane
Split bearer – User Plane
Nokia Internal Use
20
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
Data split
happens here
5GC000570 Feature
The 5GC000570 feature introduces flow
control for downlink user data transmission on
the X2-U interface between a 5G gNB and a
LTE eNB for UEs operating in NSA mode 3x and
F1-U / X2-U data split
5GC000630
gNB-DU
gNB-CU
F1-U
NR
DC UE
S1-U
3GPP based flow
control
algorithm
Nokia proprietary
flow control
mechanism
X2-U
SCG Split
Data Bearer
S-GW
Flow control over
X2-U
Flow control over
F1-U *)
LTE
S1-U
MeNB
5GC000570
S1-C
=
Data split between X2-U and F1-U
Nokia Internal Use
21
MME
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
*) introduced in 5GC000630
NR
part
LTE
part
Features and related Counters
5G - LTE flow control at X2
Data Split
•
Flow control algorithm checks the amount of data sent over the given interface
•
Data split algorithm decides which interface will be used to sent the current PDU
•
The DL data split and flow control operation can work in the following modes:
–
•
Additionally ,if the estimated delay exceeds the target, the PDCP PDUs are no longer sent over that interface
The least latency path is selected
•
•
Complete downlink user data transfer via the F1-U interface with 3GPP/Nokia flow control
Complete downlink user data transfer via the X2-U interface with 3GPP/Nokia flow control
•
Downlink user data transfer with 3GPP/Nokia flow control with data split over the X2-U interface and F1-U interface
SgNB
MeNB
S-GW
NR only
(F1-U)
S-GW
Nokia Internal Use
22
SgNB
SgNB
MeNB
LTE only
(X2-U)
Nokia internal use
RA57340-V-19
MeNB
S-GW
Data split (F1U / X2_U)
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
DDDS
5GC000570
Flow control over X2-U interface
•
The DL Data Delivery Status Extended (DDDS – see TS 36.425 for Multivendor interoperability) is used by the gNB for
deriving the delay over X2-U interface for the packets. For the flow control algorithm execution at gNB-CU, eNB provides
the following periodically in the DDDS:
–
–
–
Expected throughput.
Highest PDCP SN submitted to MAC.
Average RLC PDU queuing time within eNB.
One of two algorithms for link delay estimation can be used:
• The 3GPP flow control (as per TS 36.425)
• Nokia proprietary algorithm that re-interprets the existing IEs in DDDS for more precise calculation of the PDCP PDUs delay
over the X2. It can be used only in case of Nokia LTE eNB and gNB
The calculated link delay shall be used for estimating the amount of data (PDCP PDUs) that should be
sent in a given period from gNB to eNB to avoid/limit congestion and packet drops
If the estimated delay exceeds the operator configured “Delay threshold”, gNB shall stop sending of
data over the X2-U interface for the SCG split bearer.
Nokia Internal Use
23
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
Performance Management - related Counters
24
Counter ID
NetAct Name
Network Element Name
M55312C17001..20
DL_PDCP_SDU_D_QDLY_QOS_GRP_01..20
DL PDCP SDUs discarded due to the exceeding Queuing delay - QoS Group 01..20
M55312C18001..20
DL_PDCP_VOL_D_QDLY_QOS_GRP_01..20
DL PDCP SDUs volume discarded due to the exceeding Queuing delay - QoS Group 01..20
M55312C19001..20
DL_PDCP_DELAY_DISC_QOS_GRP_01..20
DL PDCP delay of discarded SDUs - QoS Group 01..20
M55313C04001..20
NUM_DL_PDU_LOST_X2_QOS_GRP_01..20
Number of downlink PDCP PDU packet lost on NR X2-U interface- QoS Group 01..20
M55313C05001..09
EST_INTF_LATENCY_X2_BIN_01..09
Distribution of Estimated NR X2-U Latency - Bin 01..09
M55313C06001..09
EST_RLC_QUEUE_DELAY_X2_BIN_01..09
Distribution of Estimated RLC PDU queuing Time over NR X2-U - Bin 01..09
M55313C07001..20
NUM_OPPT_DL_DAT_SPT_QOS_GRP_01..20
Number of opportunities for the DL Data split over NR F1-U and NR X2-U - QoS Group 01..20
M55313C08001..20
DL_PDCP_VOL_SNT_X2_QOS_GRP_01..20
DL data volume sent over NR X2-U DL GTP-U tunnel - QoS Group 01..20
M55313C09001..20
VOL_DL_PDCP_SNT_INT_QOS_GRP_01..20
DL data volume sent over X2-U/F1-U during the initial phase of data transmission - QoS Group 01..20
M55313C11001..20
UL_PDCP_VOL_RCV_X2_QOS_GRP_01..20
UL data volume received over NR X2-U UL GTP-U tunnel - QoS Group 01..20
M55313C13001..20
DL_PDCP_NUM_SNT_X2_QOS_GRP_01..20
Number of DL PDCP PDU sent over NR X2-U DL GTP-U tunnel - QoS Group 01..20
M55313C17001..20
MAX_DL_PDCP_SNT_X2_QOS_GRP_01..20
Max data volume sent over X2-U DL GTP-U tunnel in the sample time- QoS Group 01..20
M55313C18001..20
MIN_DL_PDCP_SNT_X2_QOS_GRP_01..20
Min data volume sent over X2-U DL GTP-U tunnel in the sample time- QoS Group 01..20
M55313C19001..20
MAX_UL_PDCP_RCV_X2_QOS_GRP_01..20
Max data volume received over X2-U UL GTP-U tunnel in the sample time- QoS Group 01..20
M55313C20001..20
MIN_UL_PDCP_RCV_X2_QOS_GRP_01..20
Min data volume received over X2-U UL GTP-U tunnel in the sample time- QoS Group 01..20
M55313C21001..20
MEAS_PERIOD_NR_X2_REPORT
Duration of the measurement period for the NRX2U report
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
5G - LTE flow control at X2
Performance Management - related Counters
25
Counter ID
NetAct Name
Network Element Name
M55313C22001..09
EST_PDU_DELV_DELAY_X2_BIN_01..09
Distribution of Estimated PDU Delivery Delay over X2-U - Bin 01..09
M55320C09001..20
DL_SDU_DISC_QUEDLY_QOS_GRP_01..20
DL PDCP SDUs discarded due to the exceeding Queuing delay - QoS Group 01..20
M55320C10001..20
DL_VOL_DISC_QUEDLY_QOS_GRP_01..20
DL PDCP SDUs volume discarded due to the exceeding Queuing delay - QoS Group 01..20
M55320C11001..20
DL_DELAY_DISC_QOS_GRP_01..20
DL PDCP delay of discarded SDUs - QoS Group 01..20
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
26
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Introduction
•
•
•
The feature 5GC000480 Radio Admission Control for NSA mode 3x operation
introduces basic radio admission control for the gNB.
The purpose of the Radio Admission Control (RAC) feature is to protect L1 and
L2 resources against high load.
High load may be caused by high utilization of radio resources or due to L1 or L2
processing power need.
Radio Admission Control
Best Resource
Admission
Admission request
or
Admission rejection
27
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Thresholds
The following Radio Admission Control thresholds are introduced:
• Maximum Number of Active UEs operating in NSA mode 3x per 5G DU (NRDU)
• Maximum Number of Active UEs operating in NSA mode 3x in a NR Cell Group (NRCELLGRP)
• Maximum Number of active UEs operating in NSA mode 3x per 5G cell (NRCELL)
• Maximum Number of non-GBR DRBs operating in NSA mode 3x per 5G DU (NRDU)
• Maximum Number of non-GBR DRBs operating in NSA mode 3x per in a NR Cell Group
(NRCELLGRP)
# of non-GBR DRBs (per NRDU or per NRCELLGRP)
# of active UEs (per NRDU or per NRCELLGRP)
# of active UEs per Cell (NRCELL)
28
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Checks 1
29
Amount of NSA users
in the cell group
Maximum number of active users in a NR cell group for NSA operation.
Parameter NRCELLGRP:maxNumOfUsers – up to 500 per NRCELLGRP
Amount of non-GBR
bearers in cell group for
SA
Maximum number of non-GBR data radio bearers in New Radio Cell Group for SA
Parameter NRCELLGRP.maxNumOfNonGBRBearersCGRPSA - up to 500
Amount of non-GBR
bearers in the cell group
Maximum number of non-GBR DRBs per NR Cell Group for NSA operation
Parameter NRCELLGRP:maxNumOfNonGBRBearers – up to 500 per NRCELLGRP
Amount of non-GBR
bearers in NR Cell for SA
Maximum number of non-GBR data radio bearers in a New Radio cell for SA
Parameter NRCELL.maxNumOfNonGBRBearersSA– up to 500 per 5GNB DU
Amount of NSA users
in the cell
Maximum number of NSA users per 5GNB cell.
Parameter NRCELL:maxNumOfUsersPerCell – up to 250 per 5GNB cell
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Checks 2
30
Additional number of
Users for handover
Additional number of NSA UEs for handovers for NSA operation.
Parameter NRCELLLLGRP:addNumOfHoUsers – up to 500
Additional number of
non-GBR DRBs
for handover
Additional number of non-GBR DRBs for handovers for NSA operation.
Parameter NRCELLGRP:addNumOfNonGBRBearersHo – up to 500
Additional number of
RRC users for SA HO
Additional number of RRC connected users in a New Radio cell for SA handover
Parameter NRCELLGRP.addNumOfRrcCGRPSAHo– up to 500
Additional number of
non-GBR DRBs in NR
CGRP for SA HO
Additional number of non-GBR data radio bearers in a NR Cell Group for SA handovers
Parameter NRCELLGRP.addNumOfNonGBRBearersCGRPSAHo – up to 500
Amount of Scell
allocations in a cell for
NSA operation
Maximum number of UEs allocated in a cell for NSA operation as SCel.
Parameter NRCELL:maxNumOfScellAlloc* – up to 250 per NRCELL
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Performance Management - related Counters
31
Counter ID
NetAct Name
Network Element Name
M55114C00001
SGNB_NSA_ADMISSION_REQ
The number of radio admission requests for NSA user
M55114C00002
SGNB_NSA_ADMISSION_SUCC
The number of radio admitted UEs for NSA user
M55114C00003
SGNB_NSA_NGBR_DRB_REQ
The number of non-GBR DRB radio admission requests for NSA user
M55114C00004
SGNB_NSA_NGBR_DRB_SUCC
The number of radio admitted non-GBR DRBs for NSA user
M55114C00005
SGNB_NSA_RAC_REJ_DUE_TO_CPUE
The number of admission rejects due to lack of CP-UE capacity for NSA user
M55114C00006
SGNB_NSA_RAC_REJ_DUE_TO_NSA
The number of admission rejects due to lack of NSA user capacity
M55114C00007
SGNB_NSA_RAC_REJ_DUE_TO_NGBR
The number of admission rejects due to lack of non-GBR capacity for NSA user
M55114C00008
AVE_NUMBER_OF_NSA_USERS
Average number of NSA users
M55114C00009
AVE_NUMBER_OF_NSA_USERS_DENOM
Average number of NSA users denominator
M55114C00010
PEAK_NUMBER_OF_NSA_USERS
Peak number of NSA users
M55114C00011
AVE_NSA_USER_HOLDING_TIME
Average admission holding time of NSA users
M55114C00012
AVE_NSA_USER_HOLDING_TIME_DEN
Average admission holding time of NSA users denominator
M55114C00013
PEAK_NSA_USER_HOLDING_TIME
Peak holding time of NSA users
M55114C00016
SGNB_NSA_HO_ADMISSION_REQ
The number of radio admission requests for handover for NSA users
M55114C00017
SGNB_NSA_NGBR_DRB_HO_REQ
The number of non-GBR DRB radio admission requests for handovers for NSA user
M55114C00018
SGNB_NSA_HO_ADMISSION_SUCC
The number of radio admitted UEs for handover for NSA user
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Performance Management - related Counters
32
Counter ID
NetAct Name
Network Element Name
M55114C00019
SGNB_NSA_NGBR_DRB_HO_SUCC
The number of radio admitted non-GBR DRBs for handovers for NSA user
M55114C00020
SGNB_CU_NSA_ADMISSION_UNSUCC
The number of unsuccessful radio admissions for NSA users
M55114C00021
SGNB_SCELL_1_ADMISSION_REQ
The number of radio admission requests for 1 Scell
M55114C00022
SGNB_SCELL_2_ADMISSION_REQ
The number of radio admission requests for 2 Scells
M55114C00023
SGNB_SCELL_3_ADMISSION_REQ
The number of radio admission requests for 3 Scells
M55114C00024
SGNB_SCELL_4_ADMISSION_REQ
The number of radio admission requests for 4 Scells
M55114C00025
SGNB_SCELL_5_ADMISSION_REQ
The number of radio admission requests for 5 Scells
M55114C00026
SGNB_SCELL_6_ADMISSION_REQ
The number of radio admission requests for 6 Scells
M55114C00027
SGNB_SCELL_7_ADMISSION_REQ
The number of radio admission requests for 7 Scells
M55114C00028
SGNB_SCELL_1_ADMISSION_SUCC
The number of successful radio admissions for 1 Scell additions.
M55114C00029
SGNB_SCELL_2_ADMISSION_SUCC
The number of successful radio admissions for 2 Scell additions.
M55114C00030
SGNB_SCELL_3_ADMISSION_SUCC
The number of successful radio admissions for 3 Scell additions.
M55114C00031
SGNB_SCELL_4_ADMISSION_SUCC
The number of successful radio admissions for 4 Scell additions.
M55114C00032
SGNB_SCELL_5_ADMISSION_SUCC
The number of successful radio admissions for 5 Scell additions.
M55114C00033
SGNB_SCELL_6_ADMISSION_SUCC
The number of successful radio admissions for 6 Scell additions.
M55114C00034
SGNB_SCELL_7_ADMISSION_SUCC
The number of successful radio admissions for 7 Scell additions.
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Performance Management - related Counters
33
Counter ID
NetAct Name
Network Element Name
M55114C00035
SGNB_SCELL_ADMISSION_UNSUCC
The number of unsuccessful radio admissions for Scells additions.
M55114C00036
PEAK_NUMBER_OF_NSA_USERS_GR
Peak number of NSA users in the cell group
M55114C00037
SGNB_NSA_AC_REL_DUE_CHANGE
The number of PsCell releases due to PsCell change
M55114C00038
SGNB_NSA_AC_SUCC_DUE_CHANGE
The number of successful PsCell changes
M55115C00002
SGNB_DU_NSA_ADMISSION_REQ
The number of admission requests for NSA user
M55115C00003
SGNB_DU_NSA_ADMISSION_SUCC
The number of successful radio admitted NSA users
M55115C00004
SGNB_DU_NSA_ADMISSION_UNSUCC
The number of unsuccessful radio admissions for NSA users
M55115C00005
SGNB_DU_NSA_ADMISSION_NO_PUCCH
The number of unsuccessful radio admissions for NSA users due to no PUCCH capacity
M55115C00006
SGNB_DU_SCELL_ADMISSION_REQ
The number of radio admission requests for the Scell
M55115C00007
SGNB_DU_SCELL_ADMISSION_SUCC
The number of successful radio admissions for the Scell
M55115C00008
SGNB_DU_SCELL_1_ADMISSION_REQ
The number of radio admission requests for 1 Scell
M55115C00009
SGNB_DU_SCELL_2_ADMISSION_REQ
The number of radio admission requests for 2 Scells
M55115C00010
SGNB_DU_SCELL_3_ADMISSION_REQ
The number of radio admission requests for 3 Scells
M55115C00011
SGNB_DU_SCELL_4_ADMISSION_REQ
The number of radio admission requests for 4 Scells
M55115C00012
SGNB_DU_SCELL_5_ADMISSION_REQ
The number of radio admission requests for 5 Scells
M55115C00013
SGNB_DU_SCELL_6_ADMISSION_REQ
The number of radio admission requests for 6 Scells
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Admission Control
Performance Management - related Counters
34
Counter ID
NetAct Name
Network Element Name
M55115C00014
SGNB_DU_SCELL_7_ADMISSION_REQ
The number of radio admission requests for 7 Scells
M55115C00015
SGNB_DU_SCELL_1_ADMISSION_SUCC
The number of successful radio admissions for 1 Scell additions.
M55115C00016
SGNB_DU_SCELL_2_ADMISSION_SUCC
The number of successful radio admissions for 2 Scell additions.
M55115C00017
SGNB_DU_SCELL_3_ADMISSION_SUCC
The number of successful radio admissions for 3 Scell additions.
M55115C00018
SGNB_DU_SCELL_4_ADMISSION_SUCC
The number of successful radio admissions for 4 Scell additions.
M55115C00019
SGNB_DU_SCELL_5_ADMISSION_SUCC
The number of successful radio admissions for 5 Scell additions.
M55115C00020
SGNB_DU_SCELL_6_ADMISSION_SUCC
The number of successful radio admissions for 6 Scell additions.
M55115C00021
SGNB_DU_SCELL_7_ADMISSION_SUCC
The number of successful radio admissions for 7 Scell additions.
M55115C00022
SGNB_NSA_ADMISSION_CHANGE_REQ
The number of PsCell change requests in DU
M55115C00023
SGNB_NSA_ADMISSION_CHANGE_SUCC
The number of PsCell successful changes in DU
M55131C00001
PEAK_NUMBER_OF_NSA_USERS_CU
Peak number of NSA users in the CU
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
35
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Link Failure
UE initiated RLF handling overview
•
•
•
•
•
•
36
SgNB
SgNB  UE timers for UE reported RLF detection
UEs declare RLF upon;
–
DL out-of-sync,
–
Random access procedure failure,
–
RLC failure detection,
SCG failure
–
SCG change,
–
SCG reconfig &
–
SRB3 integrity failure*
UE reports radio link failure to the SgNB via MeNB over the X2 interface
(SCGFailureInformation).
The SgNB may then attempt a PSCell change if another suitable 5G cell is available
Otherwise, the SgNB starts a timer during which the data can be switched to the LTE leg of the
split bearer
After timer expiry, if UE is not recovered, the SgNB will release the UE context by sending an
SgNB initiated SgNB Release Required with the cause value ‘Radio Connection with UE lost’ to
MeNB.
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
SCG failure
MeNB
Features and related Counters
Radio Link Failure
SgNB initiated RLF handling overview
•
•
37
SgNB uses
– DTX detection for downlink HARQ feedback
– DTX detection for CSI reports to detect potential RLFs,
– RLF can also be initiated by SgNB due to RLC failure detection
SgNB
When SgNB declares RLF on the PSCell: control timer starts
– During the waiting time, data could be switched to LTE leg of the split bearer
–
After timer expiry, if UE has not recovered, SgNB release UE context
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
MeNB
Features and related Counters
Radio Link Failure
Radio Link Monitoring
•
•
•
38
Radio Link Monitoring is done per configured carrier and for each UE
starts once a permanent UE context is created (for the PSCell) in NSA
operation Mode 3X and RACH procedure completed
– In case of RACH procedure UE initiated RLF is supported
From 3GPP, the 5G UE conducts the radio link monitoring and RLF
related functions only on PSCell:
– “The downlink radio link quality of the primary cell is monitored by
a UE for the purpose of indicating out-of-sync/in-sync status to
higher layers. The UE is not required to monitor the downlink
radio link quality in DL BWPs other than the active DL BWP on
the primary cell.”
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
SgNB
RLF ?
MeNB
Features and related Counters
Radio Link Failure
UE initiated RLF (1)
With LTE4193* the SgNB Addition Request sent when UE Measurement
Report Rx’d with that fulfills the NR activation conditions
•
•
•
During Initial Context Setup procedure in LTE, UE
Capability Information message indicates LTE/5G
dual connectivity
MeNB retrieves UE capabilities and triggers SgNB
addition procedure
RRC Connection Reconfiguration message SgNB
provides parameters:
– NRBTS: T310, NRBTS: N310 , NRBTS: N311
–
NRCELL: preambleTransMax
–
NRBTS: maxRetxThreshold (rlcProfX)
SgNB- CU
MeNB
UE
Measurements
UE context setup request
RRC Connection Reconfiguration
SgNB Addition Request Ack
RRC Connection Reconfiguration
Complete
SgNB Reconfiguration
Complete
Cell Detection (PSS and SSS)
System Information decoding
Random Access Procedure
39
SgNB- DU
SgNB Addition Request
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
UE context setup response
Features and related Counters
Radio Link Failure
UE initiated RLF (2)
•
•
•
40
Reasons for UE initiated Radio Link Failure on 5G side:
SgNB
– Random Access Procedure Failure
– DL out-of-sync (OOS)
– RLC failure – maximum number of retransmissions is reached
– SCG** change failure
– SCG reconfiguration failure* - UE is unable to comply with the
SCG failure
configuration included in the RRCReconfiguration message received
SCG failure
over SRB3
MeNB
– SRB3 integrity failure*- indication from SCG lower layers concerning
SRB3
On RLF detection UE informs MeNB which passes information to SgNB
Data is switched to LTE leg and if 5G radio link will not recover itself or via
PSCell change then MeNB initiates SgNB release
– conditions for PSCell change must be fulfilled in order to trigger PSCell
change
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Radio Link Failure
SgNB initiated RLF
•
•
•
•
41
SgNB detects RLF for 5G link based on:
– DTX detection for requested DL HARQ feedback on PUCCH
– DTX detection of CSI reports on PUCCH
– Radio Link Control (RLC) failure – maximum numer of retransmissions is
reached
When a SgNB declares an RLF on the PSCell a control timer starts
During the waiting time, data is switched to LTE leg of the split bearer
– Scope of 5GC000570 5G - LTE flow control at X2
When timer expires, SgNB will release the UE context by sending an SgNB initiated
SgNB release with the cause: ‘Radio Connection with UE lost’ to MeNB
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
SgNB
MeNB
Features and related Counters
Radio Link Failure
Performance Management - related Counters
42
Counter ID
NetAct Name
Network Element Name
M55112C00501
SGNB_REL_SN_SUCC_UE_LOST
Number of Successful SGNB RELEASE procedure due to UE lost
M55112C00502
SGNB_REL_SN_REQ_UE_LOST
Number of SGNB RELEASE REQUIRED message sent with cause equal to Radio Connection With UE lost
M55112C00503
SGNB_MOD_REQUEST
Number of SGNB MODIFICATION REQUEST received due to failure by UE
M55116C00004
RLF_INITIATED_RNL
Number of UE Context Modification Required with cause Radio Network Layer / radio link failure
M55116C00005
RLF_INITIATED_UE_MEAS_FAULTY
The num of UEs released due to RLF init by UE, PSCell Chnge not triggred as gNB received faulty meas
M55116C00006
RLF_INITIATED_UE_PSCELL_CHN_F
The number of unsuccessful PSCell changes post radio link failure initiated by UE.
M55116C00007
RLF_INITIATED_UE_PSCELL_CHANGE
The number of successful PSCell changes post radio link failure initiated by UE.
M55116C00008
RLF_INITIATED_UE_T310_EXPIRY
The number of UEs released due to RLF initiated by UE with the root cause t310 expiry
M55116C00009
RLF_INITIATED_UE_RACH_FAIL
The number of UEs released due to RLF initiated by UE with the root cause RACH problem.
M55116C00010
RLF_INITIATED_UE_MAX_RLC_RETX
The number of UEs released due to RLF initiated by UE with the root cause Max RLC retransmission
M55116C00011
RLF_INITIATED_UE_SRB_INTGRTY_F
The number of UEs rejected due to RLF initiated by UE with the root cause SRB3 Integrity failure.
M55116C00012
RLF_INITIATED_UE_SCG_CHGE_FAIL
The number of UEs rejected due to RLF initiated by UE with the root cause SCG change fail.
M55116C00013
RLF_INITIATED_UE_SCG_RECNF_F
The number of UEs rejected due to RLF initiated by UE with the root cause SCG reconfig failure.
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
43
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE Inactivity
5GC000479 UE inactivity handling for NSA mode 3x operation
• This feature introduces radio Link Failure (RLF) handling
for UEs operating in NSA mode 3x
• UE initiated RLF handling (SN Radio Link Failure)
• SgNB initiated RLF detection and handling
• SgNB initiated UE inactivity detection
MeNB
44
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE Inactivity
SgNB initiated UE inactivity detection
5G inactivity
SgNB
•
UE inactivity at SgNB is detected for UEs operating in NSA mode 3x, if
there is no user data sent or received on SCG split bearer from a UE for an
operator configurable time.
•
After the inactivity detection the SgNB sends an SgNB Release Required
message to the MeNB (covered by 5GC000475) with the cause value ‘User
Inactivity’ (SgNB initiated SgNB Release)
•
If the UE is also inactive on LTE eNB, then the UE may be released by LTE
eNB (separate LTE eNB feature)
•
If the UE is inactive on 4G but active on 5G, the UE can not be released
by the LTE eNB (i.e. with 4G inactivity as a sole cause)
MeNB
SgNB
LTE
inactivity
MeNB
45
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE Inactivity
Performance Management - related Counters
46
Counter ID
NetAct Name
Network Element Name
M55112C02001
SGNB_RELEASE_REQ_UE_INACT
Number of SGNB RELEASE REQUIRED message sent with cause equal to User inactivity
M55112C02002
SGNB_RELEASE_SUCC_UE_INACT
Number of successful SgNB Release due to User inactivity
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
Index
F1 Link Management
NSA Call
5G - LTE flow control at X2
Radio Admission Control
Radio Link Failure
UE Inactivity
UE capability handling for NSA mode 3x operation
47
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
gNB functionalities and UE capabilities
5GC000482: UE Capability Handling for NSA Mode 3x Operation feature introduces the UE capability handling for
Non-Standalone (NSA) mode 3x operation.
It ensures the consistency between activated features and UE capabilities.
Introduced gNB functionalities
• Retrieval of UE capabilities from CellGroupConfigInfo (CG-ConfigInfo) in the SgNB Addition Request Procedure.
• UE capabilities decoding and storing in gNB Central Unit (gNB-CU).
• Sending UE capability in the UE context setup procedure to gNB Distributed Unit (gNB-DU) over F1-C interface.
• UE capabilities decoding and storing in gNB-DU.
• Failure scenario - missing UE capabilities or decoding failure.
UE capabilities
For NSA mode, UE capabilities include:
• RF capabilities: band combinations and capabilities that are per-band-combination
• Physical layer (PHY) capabilities: receiver, Multiple Input Multiple Output (MIMO) and Transmission Mode (TM) capabilities, feedback, codebooks
• Protocol-specific capabilities: MAC, RLC and PDCP based capabilities
• E-UTRA-NR Dual Connectivity (EN-DC) capabilities
48
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
CellGroupConfigInfo message
CellGroupConfigInfo message
CellGroupConfigInfo message is used by Master eNB (MeNB) to request the Secondary gNB (en-gNB) to perform certain actions
(establishing, modifying or releasing a Secondary Cell Group (SCG)).
The message may include additional information, for example to assist the en-gNB to set the SCG configuration. It can also be used by a
gNB-CU to request a gNB-DU to perform certain actions (establishing, modifying or releasing a Master Cell Group (MCG) or SCG).
This message is defined in 3GPP TS 38.331.
CG-ConfigInfo is sent by MeNB to en-gNB, or from gNB-CU to gNB-DU.
49
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
SgNB Addition Request procedure
SgNB Addition Request procedure
1. UE attaches to MeNB.
2. MeNB configures one non-Guaranteed Bit Rate (non-GBR) bearer, that is split bearer for the UE.
3. MeNB sends SgNB Addition Request to en-gNB.
4. en-gNB decodes the SgNB Addition Request.
5. en-gNB stores the received UE capability.
6. en-gNB sends SgNB Addition Request Acknowledge to MeNB.
50
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
Success scenario
Handling of UE capabilities - success scenario
1. MeNB sends SgNB Addition Request to en-gNB with UE capabilities embedded inside CG-ConfigInfo message.
2. gNB-CU receives a request from MeNB to setup UE Context with one NSA 3x bearer.
3. gNB-CU decodes CG-ConfigInfo and configures resources for SCG bearer.
4. gNB-CU sets up the UE Context and bearer context, that is Data Radio Bearer (DRB) in gNB-DU by sending F1 Application Protocol
(F1AP) message. UE capabilities are sent as a part of UE Context setup from gNB-CU to gNB-DU.
5. MeNB receives SgNB Addition Request Acknowledge sent by en-gNB.
6. en-gNB stores UE capabilities until the en-gNB is released, either with the reception of SgNB Release Request message (MeNB initiated
release) or a SgNB Release Confirm message (en-gNB initiated release).
Multi Radio Dual Connectivity (MRDC) and New Radio (NR) capabilities of the UE are sent by MeNB.
51
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
Failure scenario
Handling of UE capabilities - failure scenario
1. MeNB sends SgNB Addition Request without UE capabilities inside CG-ConfigInfo.
2. en-gNB rejects SgNB Addition Request due to missing UE capabilities.
3. en-gNB sends SgNB Addition Request Reject message. Failure scenario may occur also due to decoding failure..
52
Nokia internal use
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
UE capability handling for NSA mode 3x operation
Performance Management - related Counters
53
Counter ID
NetAct Name
Network Element Name
M55112C01501
X2_SGNB_REQ_REJ_MISSING_UE_CAP
Number of SGNB ADDITION REQUEST REJECT due to missing UE Capabilities
RA57340-V-19
© Nokia 2019
RA57340-V-19
Features and related Counters
RA57340-V-19