RA57331-V-5G19

5G Performance Aspects in Trials and Pilots

Basic signaling and procedure verification

1 © 2019 Nokia
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").
Such Feedback may be used in Nokia products and
2 © 2019 Nokia
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.
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.
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, 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.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
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.
Revision history and metadata
Please delete this slide if document is uncontrolled
Document ID: DXXXXXXXXX
Document Location:
Organization:

Version Description of charges Date Author Owner Status Reviewed Reviewed Approver Approval
by date date

DD-MM-YYYY DD-MM-YYYY DD-MM-YYYY

3 © 2019 Nokia
Module Objective
After completing this learning element, the participant should be able to:

Explain Secondary Node Addition Procedure

Repeat X2 Link Management
Locate UE Context Setup
Define Handover

4 © 2019 Nokia
Index
Secondary Node Addition Procedure
X2 Link Management
UE Context Setup
Handover

5 © 2019 Nokia
Index
Secondary Node Addition Procedure
X2 Link Management
UE Context Setup
Handover

6 © 2019 Nokia
Secondary Node Addition Procedure
Overview

UE MN SN S-GW MME

1. SgNB Addition Request

2. SgNB Addition Request Acknowledge

3. RRCConnectionReconfiguration

4. RRCConnectionReconfigurationComplete

5. SgNB Reconfiguration Complete

6. Random Access Procedure
7. SN Status Transfer
8. Data Forwarding

Path Update procedure 9. E-RAB Modification Indication

10. Bearer Modication

11. End Marker Packet

12. E-RAB Modification Confirm

7 © 2019 Nokia
Secondary Node Addition Procedure
Successful SgNB Connection Establishment

The X2_SgNB_Add_REQ_RECEIVED is
Incremented when X2AP SgNB
Addition Request is received by gNB.

The X2_SgNB_Add_REQ_ACK_SENT is
Incremented when X2AP SgNB
Reconfiguration Complete is received
by gNB.

8 © 2019 Nokia
Secondary Node Addition Procedure
F1 Ue Context Setup

NF1CC_UECTXT_STP_REQSENT Incremented when F1AP:

UE CONTEXT SETUP REQUEST is sent by gNB-CU

NF1CD_UECTXT_STP_REQRECD Incremented when F1AP:

UE CONTEXT SETUP REQUEST is received in gNB-DU

NF1CC_UECTXT_STP_RESPRECD Incremented when F1AP:

UE CONTEXT SETUP RESPONSE is received at gNB-CU

NF1CD_UECTXT_STP_RESPSENT Incremented when F1AP:

UE CONTEXT SETUP RESPONSE is sent from gNB-DU

9 © 2019 Nokia
Secondary Node Addition Procedure
Successful SN Status Transfer

X2_SGNB_RECONF_RECEIVED Incremented when X2AP

SgNB Reconfiguration Complete is received by gNB.

X2_SGNB_RECONF_ACK_RECEIVED Incremented when X2AP

SgNB Reconfiguration Complete is received with
Configuration successfully applied IE by gNB.

X2_SN_STATUS_TRANSFER_RECEIVED Incremented when

X2AP SN Status Transfer is received by gNB.

10 © 2019 Nokia
Secondary Node Addition Procedure
SgNB Addition Failures due to SCG configuration rejection

X2_SGNB_RECONF_NACK_RECEIVED Incremented when

X2AP SgNB Reconfiguration Complete is received with
Configuration rejected IE by gNB.

11 © 2019 Nokia
Secondary Node Addition Procedure
SgNB Addition Failure Due to SN Status Transfer not received

X2_SN_STATUS_TRANSFER_T Incremented when

TimerX2UeProcGuard timer expires while waiting
for the X2AP SN Status Transfer from MeNB

12 © 2019 Nokia
Index
Secondary Node Addition Procedure
X2 Link Management
UE Context Setup
Handover

13 © 2019 Nokia
X2 Link Management
X2 Link Setup

ENDC_X2_SETUP_REQUEST_RECEIVED: Incremented when X2AP EN-

DC X2 Setup Request is received by gNB.

ENDC_X2_SETUP_RESPONSE_SENT: Incremented when X2AP EN-DC

X2 Setup Response is sent by gNB.

14 © 2019 Nokia
X2 Link Management
X2 Link Setup Failures

No EN-DC X2 SETUP request initiated by LTE eNB

ENDC_X2_SETUP_REQUEST_NOT_RCVD: Incremented when X2AP EN-DC X2 Setup

Request is not received after enDcX2SetupReqTmr timer expiry

15 © 2019 Nokia
X2 Link Management
X2 Link Setup Failures with Causes

• ENDC_X2_SETUP_FAIL_NOSUP: Number of unsuccessful EN-DC X2 SETUP procedure (source not supported).

Corresponding to the failure cases: the initiating Node Type is not an eNB, the initiating Node Type is an eNB,
but the Global eNB ID received from initiating LTE eNB is not of type ‘Macro eNB’

• ENDC_X2_SETUP_FAIL_MAX_X2: Number of unsuccessful EN-DC X2 SETUP procedure (max already reached)

• ENDC_X2_SETUP_FAIL_PROCESSING: Number of unsuccessful EN-DC X2 SETUP procedure (processing)

corresponding to the failure case: max number of ongoing X2 Setup request attempts

• ENDC_X2_SETUP_FAIL_NOCELL: Number of unsuccessful EN-DC X2 SETUP procedure (cell not available)

Corresponding to the failure case: no Served cell to include in EN-DC X2 Setup Response

• ENDC_X2_SETUP_FAIL_LOCKED: Number of unsuccessful EN-DC X2 SETUP procedure (locked) Corresponding to

the failure case: LTEENB object corresponding to the LTE eNB is locked

16 © 2019 Nokia
X2 Link Management
Incoming X2 Link Reset

X2_RESET_REQUEST_RECEIVED: Incremented when X2AP Reset

Request is received by gNB.
X2_RESET_RESPONSE_SENT: Incremented when X2AP Reset Response
is sent by gNB.

17 © 2019 Nokia
X2 Link Management
Outgoing X2 Reset

(1) 5G-CP-NB receives an information that the

X2-C link is locked by the operator
(2) 5G-CP-NB forwards the information to 5G-
CP-IF.
(3) 5G-CP-IF acknowledges the request from
5G-CP-NB
(4) 5G-CP-NB acknowledges the modification of
LTEEB object
(5) 5G-CP-IF will send REST Requet to LTE eNB
and starts x2ReseRsp Tmr timer
(6) 5G-CP-IF receives RESET Response from LTE
eNB over the single SCTP stream used for
X2 non-UE associated signalling.
(7) 5G-CP-IF asks 5G-CP-NB to update LTEENB
instance with X2-C link state to
“unavailable”.
(8) 5G-CP-IF stops x2ResetRspTmr timer and
requests to shutdown the SCTP association.

18 © 2019 Nokia
X2 Link Management
Link Shutdown

When gNB-CU replies to MeNB with an EN-DC X2 SETUP failure or when there is no EN-DC X2 Setup procedure triggered by LTE (expiry of the waiting
timer for EN-DC X2 setup procedure), a waiting timer for SCTP link shutdown due to no traffic is started.

After expiry of the waiting timer for SCTP link shutdown due to no traffic (no X2 message was received from LTE eNB), gNB-CU asks to shutdown the
SCTP association

X2_SHUTDOWN_NO_TRAFFIC: Incremented when no more traffic on X2 link after shutdownNoX2TrafficTmr timer expiry

19 © 2019 Nokia
Index
Secondary Node Addition Procedure
X2 Link Management
UE Context Setup
Handover

20 © 2019 Nokia
UE Context Setup
Overview

5G-CP-RT shall perform QCI Validation.

5G-CP-RT shall perform IP Address version

validation.

5G-CP-RT shall retrieve the QCI from E-

UTRAN QoS IE.

21 © 2019 Nokia
UE Context Setup
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

22 © 2019 Nokia
UE Context Setup
Bearer Setup Failures
NX2CC_BEARER_FAIL_TYP_NOT_SUPP: Incremented when
X2AP: SGNB ADDITION REQUEST REJECT is sent for bearer type
mismatch.

NX2CC_BEARER_FAIL_SEC_NOT_SUPP: Incremented when

X2AP: SGNB ADDITION REQUEST REJECT is sent with causes
associated with QCI related failures - 3x bearer not allowed,
QoS profile not configured

NX2CC_BEARER_FAIL_QCI_NOT_SUPP: Incremented when

X2AP: SGNB ADDITION REQUEST REJECT is sent with causes
associated with QCI related failures - 3x bearer not allowed,
QoS profile not configured

NX2CC_BEARER_FAIL_IP_NOT_SUPP: Incremented when

X2AP: SGNB ADDITION REQUEST REJECT is sent with causes
associated with IP version mismatch

NX2CC_BEARER_FAIL_MISC: Incremented when X2AP: SGNB

ADDITION REQUEST REJECT is sent with any other cause than
Bearer Type, QCI, Security algorithm mismatch or IP version
mismatch

23 © 2019 Nokia
UE Context Setup
UE Context Release over X2

NF1CC_UECTXT_REL_CMDSENT: Number of F1AP: Ue Context

Release Command message sent from gNB-CU

NNF1CC_UE_CTXT_REL_CMP_RECD: Number of F1AP: Ue

Context Release Complete received in gNB-CU

24 © 2019 Nokia
Index
Secondary Node Addition Procedure
X2 Link Management
UE Context Setup
Handover

25 © 2019 Nokia
Handover
Overview
• In 5G early release, PM counters from this measurements came from feature
5GC000572 Intra-Frequency Intra gNB mobility (NSA option 3x)
ID NetAct Name Description Updated

This counter indicates the number of When X2AP: SgNB Modification Required
M55120C00001 INTRA_FR_PSCEL_CH_ATTEMPT intra gNB intra frequency PS-Cell message is sent to MeNB with the SCG
change attempts Change Indication set as "PS-CellChange"
This counter indicates the number of
When the TDCoverall timer has elapsed
intra gNB intra frequency PS-Cell
M55120C00002 INTRA_FR_PSCEL_CH_FAI_TDC_EXP before gNB receives the X2AP: SgNB
change failures due to TDCoverall
Modification Confirm message
timer expiry
This counter indicates the number of When MeNB replies to X2AP: SgNB
M55120C00003 INTRA_FR_PSCEL_CH_FAI_MENB_REF intra gNB intra frequency PS-Cell Modification Required message with the
change failures due to MeNB refusal X2AP: SgNB Modification Refuse message
This counter indicates the number of
intra gNB intra frequency PS-Cell
M55120C00004 INTRA_FR_PSCEL_CH_FAI_RES_ALLO When AC fails for PS-Cell change
change failures due to target cell
resource allocation failure

26 © 2019 Nokia
Handover
Number of intra gNB intra frequency PS-Cell change attempts

UE MeNB SgNB-CU Source SgNB-DU Target SgNB-DU

F1AP: UE Context Setup Request

F1AP: UE Context Setup Response

F1AP: UE Context
Modification Request
F1AP: UE Context
Modification Response

X2AP: SgNB Modification Required

RRC: RRC Connection
Reconfiguration • X2AP: SgNB Modification Required message
is sent to MeNB with the
SCGChangeIndication containing
pSCellChange
• INTRA_FR_PSCEL_CH_ATTEMPT is updated

27 © 2019 Nokia
Handover
PS-Cell change failures due to TDCoverall timer expiry
UE MeNB SgNB-CU Source SgNB-DU Target SgNB-DU

X2AP: SgNB Modification Required

TDCoverall guard timer

• PSCell change is canceled with cause "Unsuccessful
PSCell change due to TDCOverall timer expiry„
RRC: RRC Connection TDCoverall timer • INTRA_FR_PSCEL_CH_FAI_TDC_EXP is updated
Reconfiguration expires before
acknowledgement
RRC: RRC Connection is received from
Reconfiguration Complete MeNB

F1AP: UE Context Release Command

F1AP: UE Context Release Complete

X2AP: SgNB Release

Required
X2AP: SgNB Release
Confirm

28 © 2019 Nokia
Handover
PS-Cell change failures due to MeNB refusal

UE MeNB SgNB-CU Source SgNB-DU Target SgNB-DU

X2AP: SgNB Modification Required

TDCoverall guard timer

• PSCell change is cancelled with cause " Unsuccessful
PSCell Change due to X2AP: SgNB Modification Refuse
from MeNB" „
• INTRA_FR_PSCEL_CH_FAI_MENB_REF is updated
X2AP: SgNB Modification
Refuse

F1AP: UE Context Release Command

F1AP: UE Context Release Complete

X2AP: SgNB Release

Required
X2AP: SgNB Release
Confirm

29 © 2019 Nokia
Handover
PS-Cell change failures due to target cell resource allocation failure
UE MeNB SgNB-CU Source SgNB-DU Target SgNB-DU

Measurement Report

Admission Control failed

at CU level or DU level

• Handover preparation fails because admission control

fails to target SgNB-DU
• INTRA_FR_PSCEL_CH_FAI_RES_ALLO is updated

30 © 2019 Nokia