9.1.1 Messages for Basic Mobility Procedures

38.4233GPPNG-RANRelease 17TSXn Application Protocol (XnAP)

9.1.1.1 HANDOVER REQUEST

This message is sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for a handover.

Direction: source NG-RAN node  target NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

Source NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the source NG-RAN node

YES

reject

Cause

M

9.2.3.2

YES

reject

Target Cell Global ID

M

9.2.3.25

Includes either an E-UTRA CGI or an NR CGI

YES

reject

GUAMI

M

9.2.3.24

YES

reject

UE Context Information

1

YES

reject

>NG-C UE associated Signalling reference

M

AMF UE NGAP ID

9.2.3.26

Allocated at the AMF on the source NG-C connection.

>Signalling TNL association address at source NG-C side

M

CP Transport Layer Information

9.2.3.31

This IE indicates the AMF’s IP address of the SCTP association used at the source NG-C interface instance.

Note: If no UE TNLA binding exists at the source NG-RAN node, the source NG-RAN node indicates the TNL association address it would have selected if it would have had to create a UE TNLA binding.

>UE Security Capabilities

M

9.2.3.49

>AS Security Information

M

9.2.3.50

>Index to RAT/Frequency Selection Priority

O

9.2.3.23

>UE Aggregate Maximum Bit Rate

M

9.2.3.17

>PDU Session Resources To Be Setup List

1

9.2.1.1

Similar to NG-C signalling, containing UL tunnel information per PDU Session Resource;

and in addition, the source side QoS flow  DRB mapping

>RRC Context

M

OCTET STRING

Either includes the HandoverPreparationInformation message as defined in subclause 10.2.2. of TS 36.331 [14], or the HandoverPreparationInformation-NB message as defined in subclause 10.6.2 of TS 36.331 [14], if the target NG-RAN node is an ng-eNB,

or the HandoverPreparationInformation message as defined in subclause 11.2.2 of TS 38.331 [10], if the target NG-RAN node is a gNB.

>Location Reporting Information

O

9.2.3.47

Includes the necessary parameters for location reporting.

>Mobility Restriction List

O

9.2.3.53

>5GC Mobility Restriction List Container

O

9.2.3.100

YES

ignore

>NR UE Sidelink Aggregate Maximum Bit Rate

O

9.2.3.107

This IE applies only if the UE is authorized for NR V2X services.

YES

ignore

>LTE UE Sidelink Aggregate Maximum Bit Rate

O

9.2.3.108

This IE applies only if the UE is authorized for LTE V2X services.

YES

ignore

>Management Based MDT PLMN List

O

MDT PLMN List

9.2.3.133

YES

ignore

>UE Radio Capability ID

O

9.2.3.138

YES

reject

>MBS Session Information List

O

9.2.1.36

YES

ignore

>5G ProSe UE PC5 Aggregate Maximum Bit Rate

O

NR UE Sidelink Aggregate Maximum Bit Rate

9.2.3.107

This IE applies only if the UE is authorized for 5G ProSe services.

YES

ignore

>UE Slice Maximum Bit Rate List

O

9.2.3.167

YES

ignore

Trace Activation

O

9.2.3.55

YES

ignore

Masked IMEISV

O

9.2.3.32

YES

ignore

UE History Information

M

9.2.3.64

YES

ignore

UE Context Reference at the S-NG-RAN node

O

YES

ignore

>Global NG-RAN Node ID

M

9.2.2.3

>S-NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID

9.2.3.16

Conditional Handover Information Request

O

YES

reject

>CHO Trigger

M

ENUMERATED (CHO-initiation, CHO-replace, …)

>Target NG-RAN node UE XnAP ID

C-ifCHOmod

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the target NG-RAN node

>Estimated Arrival Probability

O

INTEGER (1..100)

NR V2X Services Authorized

O

9.2.3.105

YES

ignore

LTE V2X Services Authorized

O

9.2.3.106

YES

ignore

PC5 QoS Parameters

O

9.2.3.109

This IE applies only if the UE is authorized for NR V2X services.

YES

ignore

Mobility Information

O

BIT STRING (SIZE (32))

Information related to the handover; the source NG-RAN node provides it in order to enable later analysis of the conditions that led to a wrong HO.

YES

ignore

UE History Information from the UE

O

9.2.3.110

YES

ignore

IAB Node Indication

O

ENUMERATED (true, …)

YES

reject

No PDU Session Indication

O

ENUMERATED (true, …)

This IE applies only if the UE is an IAB-MT.

YES

ignore

Time Synchronisation Assistance Information

O

9.2.3.153

YES

ignore

QMC Configuration Information

O

9.2.3.156

YES

ignore

5G ProSe Authorized

O

9.2.3.159

YES

ignore

5G ProSe PC5 QoS Parameters

O

9.2.3.160

This IE applies only if the UE is authorized for 5G ProSe services.

YES

ignore

Condition

Explanation

ifCHOmod

This IE shall be present if the CHO Trigger IE is present and set to "CHO-replace".

Range bound

Explanation

maxnoofMDTPLMNs

PLMNs in the Management Based MDT PLMN list. Value is 16.

9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE

This message is sent by the target NG-RAN node to inform the source NG-RAN node about the prepared resources at the target.

Direction: target NG-RAN node  source NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the source NG-RAN node

YES

ignore

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the target NG-RAN node

YES

ignore

PDU Session Resources Admitted List

M

9.2.1.2

YES

ignore

PDU Session Resources Not Admitted List

O

9.2.1.3

YES

ignore

Target NG-RAN node To Source NG-RAN node Transparent Container

M

OCTET STRING

Either includes the HandoverCommand message as defined in subclause 10.2.2 of TS 36.331 [14], if the target NG-RAN node is an ng-eNB,

or the HandoverCommand message as defined in subclause 11.2.2 of TS 38.331 [10], if the target NG-RAN node is a gNB.

YES

ignore

UE Context Kept Indicator

O

9.2.3.68

YES

ignore

Criticality Diagnostics

O

9.2.3.3

YES

ignore

DRBs transferred to MN

O

DRB List

9.2.1.29

In case of DC, indicates that SN Status is needed for the listed DRBs from the S-NG-RAN node.

YES

ignore

DAPS Response Information

O

9.2.1.34

YES

reject

Conditional Handover Information Acknowledge

O

YES

reject

>Requested Target Cell ID

M

Target Cell Global ID

9.2.3.25

Target cell indicated in the corresponding HANDOVER REQUEST message

>Maximum Number of CHO Preparations

O

9.2.3.101

MBS Session Information Response List

O

9.2.1.38

YES

ignore

9.1.1.3 HANDOVER PREPARATION FAILURE

This message is sent by the target NG-RAN node to inform the source NG-RAN node that the Handover Preparation has failed.

Direction: target NG-RAN node  source NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the source NG-RAN node

YES

ignore

Cause

M

9.2.3.2

YES

ignore

Criticality Diagnostics

O

9.2.3.3

YES

ignore

Requested Target Cell ID

O

Target Cell Global ID

9.2.3.25

Target cell indicated in the corresponding HANDOVER REQUEST message

YES

reject

9.1.1.4 SN STATUS TRANSFER

This message is sent by the source NG-RAN node to the target NG-RAN node to transfer the uplink/downlink PDCP SN. HFN status and MRO related information during a handover or for dual connectivity.

Direction: source NG-RAN node  target NG-RAN node(handover),
NG-RAN node from which the DRB context is transferred  NG-RAN node to which the DRB context is transferred (RRC connection re-establishment or dual connectivity).

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

ignore

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the source NG-RAN node and for dual connectivity at the NG-RAN node from which the DRB context is transferred.

YES

reject

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the target NG-RAN node and for dual connectivity at the NG-RAN node to which the DRB context is transferred.

YES

reject

DRBs Subject To Status Transfer List

M

9.2.1.14

YES

ignore

CHO Configuration

O

9.2.2.76

YES

ignore

Mobility Information

O

BIT STRING (SIZE (32))

YES

ignore

9.1.1.5 UE CONTEXT RELEASE

This message is sent by the target NG-RAN node to the source NG-RAN node to indicate that resources can be released.

Direction: target NG-RAN node  source NG-RAN node, M-NG-RAN node  S-NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the source NG-RAN node or for dual connectivity at the S-NG-RAN node.

YES

reject

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the target NG-RAN node or for dual connectivity at the M-NG-RAN node.

YES

reject

9.1.1.6 HANDOVER CANCEL

This message is sent by the source NG-RAN node to the target NG-RAN node to cancel an ongoing handover.

Direction: source NG-RAN node  target NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

ignore

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the source NG-RAN node.

YES

reject

Target NG-RAN node UE XnAP ID

O

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the target NG-RAN node.

YES

ignore

Cause

M

9.2.3.2

YES

ignore

Candidate Cells To Be Cancelled List

0 .. <maxnoofCellsinCHO>

YES

reject

>Target Cell ID

M

Target Cell Global ID

9.2.3.25

Range bound

Explanation

maxnoofCellsinCHO

Maximum no. cells that can be prepared for a conditional handover. Value is 8.

9.1.1.7 RAN PAGING

This message is sent by the NG-RAN node1 to NG-RAN node2 to page a UE.

Direction: NG-RAN node1  NG-RAN node2.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

CHOICE UE Identity Index Value

M

YES

reject

>Length-10

>>Index Length-10

M

BIT STRING (SIZE(10))

Coded as specified in TS 38.304 [33] and TS 36.304 [34].

UE RAN Paging Identity

M

9.2.3.43

YES

ignore

Paging DRX

M

9.2.3.66

Includes the RAN paging cycle as defined in TS 36.304 [34] and 38.304 [33].

YES

ignore

RAN Paging Area

M

9.2.3.38

YES

reject

Paging Priority

O

9.2.3.44

YES

ignore

Assistance Data for RAN Paging

O

9.2.3.41

YES

ignore

UE Radio Capability for Paging

O

9.2.3.91

YES

ignore

Extended UE Identity Index Value

O

9.2.3.141

Coded as specified in TS 36.304 [34].

YES

ignore

E-UTRA Paging eDRX Information

O

9.2.3.142

YES

ignore

UE specific DRX

O

9.2.3.143

Includes the UE specific paging cycle as defined in TS 36.304 [34] and 38.304 [33].

YES

ignore

NR Paging eDRX Information

O

9.2.3.161

YES

ignore

NR Paging eDRX Information for RRC INACTIVE

O

9.2.3.162

YES

ignore

Paging Cause

O

ENUMERATED (voice, …)

YES

ignore

PEIPS Assistance Information

O

9.2.3.166

YES

ignore

9.1.1.8 RETRIEVE UE CONTEXT REQUEST

This message is sent by the new NG-RAN node to request the old NG-RAN node to transfer the UE Context to the new NG-RAN.

Direction: new NG-RAN node  old NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

reject

UE Context ID

M

9.2.3.40

YES

reject

Integrity protection

M

BIT STRING (SIZE (16))

RRC Resume:

ResumeMAC-I either contained in the RRC ResumeRequest or the RRCResumeRequest1 message as defined in TS 38.331 [10])

or the ShortResumeMAC-I in the RRCConnection ResumeRequest message as defined in TS 36.331 [14])

RRC Reestablishment:

ShortMAC-I contained in the RRCReestablishmentRequest as defined in TS 38.331 [10])

or the ShortMAC-I in the RRCConnection ReestablishmentRequest message as defined in TS 36.331 [14]).

RRC Resume for UP CIoT Optimization:

ShortResumeMAC-I in the RRCConnection ResumeRequest message or RRCConnection ResumeRequest-NB message as defined in TS 36.331 [14].

YES

reject

New Cell Identifier

M

NG-RAN Cell Identity

9.2.2.9

RRC Resume:

Corresponds to the targetCellIdentity within the VarResumeMAC-Input as specified in TS 38.331 [10] or the cellIdentity within the VarShortINACTIVE-MAC-Input as specified in TS 36.331 [14].

RRC Reestablishment:

Corresponds to the targetCellIdentity within the VarShortMAC-Input as specified in TS 38.331 [10] or the cellIdentity within the VarShortMAC-Input as specified in TS 36.331 [14].

RRC Resume for UP CIoT Optimization:

Corresponds to the cellIdentity within the VarShortResumeMAC-Input or VarShortResumeMAC-Input-NB as specified in TS 36.331 [14].

YES

reject

RRC Resume Cause

O

9.2.3.61

In case of RNA Update, contains the cause value provided by the UE in the RRCResumeRequest or the RRCResumeRequest1 message, as defined in TS 38.331 [10],

or in the RRCConnection ResumeRequest message, as defined in TS 36.331 [14].

YES

ignore

SDT Support Request

O

9.2.3.163

YES

ignore

9.1.1.9 RETRIEVE UE CONTEXT RESPONSE

This message is sent by the old NG-RAN node to transfer the UE context to the new NG-RAN node.

Direction: old NG-RAN node  new NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node

YES

ignore

GUAMI

M

9.2.3.24

YES

reject

UE Context Information – Retrieve UE Context Response

M

9.2.1.13

YES

reject

Trace Activation

O

9.2.3.55

YES

ignore

Masked IMEISV

O

9.2.3.32

YES

ignore

Location Reporting Information

O

9.2.3.47

Includes the necessary parameters for location reporting.

YES

ignore

Criticality Diagnostics

O

9.2.3.3

YES

ignore

NR V2X Services Authorized

O

9.2.3.105

YES

ignore

LTE V2X Services Authorized

O

9.2.3.106

YES

ignore

PC5 QoS Parameters

O

9.2.3.109

This IE applies only if the UE is authorized for NR V2X services.

YES

ignore

UE History Information

O

9.2.3.64

YES

ignore

UE History Information from the UE

O

9.2.3.110

YES

ignore

Management Based MDT PLMN List

O

MDT PLMN List

9.2.3.133

YES

ignore

IAB Node Indication

O

ENUMERATED (true, …)

YES

reject

UE Context Reference at the S-NG-RAN node

O

YES

ignore

>Global NG-RAN Node ID

M

9.2.2.3

>S-NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID

9.2.3.16

Time Synchronisation Assistance Information

O

9.2.3.153

YES

ignore

QMC Configuration Information

O

9.2.3.156

YES

ignore

5G ProSe Authorized

O

9.2.3.159

YES

ignore

5G ProSe PC5 QoS Parameters

O

9.2.3.160

This IE applies only if the UE is authorized for 5G ProSe services.

YES

ignore

Range bound

Explanation

maxnoofMDTPLMNs

PLMNs in the Management Based MDT PLMN list. Value is 16.

9.1.1.10 RETRIEVE UE CONTEXT FAILURE

This message is sent by the old NG-RAN node to inform the new NG-RAN node that the Retrieve UE Context procedure has failed.

Direction: old NG-RAN node  new NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

Old NG-RAN node To New NG-RAN node Resume Container

O

OCTET STRING

Includes either the RRCRelease message as defined in TS 38.331 [10], or the RRCConnectionRelease message as defined in TS 36.331 [14], encapsulated in a PDCP-C PDU.

YES

ignore

Cause

M

9.2.3.2

YES

ignore

Criticality Diagnostics

O

9.2.3.3

YES

ignore

9.1.1.11 XN-U ADDRESS INDICATION

This message is either sent by the new NG-RAN node to transfer data forwarding information to the old NG-RAN node, or by the M-NG-RAN node to provide either data forwarding or Xn-U bearer address related information for SN terminated bearers to the S-NG-RAN node.

Direction: new NG-RAN node  old NG-RAN node, M-NG-RAN node  S-NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node

YES

ignore

Xn-U Address Information per PDU Session Resources List

1

YES

reject

>Xn-U Address Information per PDU Session Resources Item

1..<maxnoofPDUSessions>

>>PDU Session ID

M

9.2.3.18

>>Data Forwarding Info from target NG-RAN node

O

Data Forwarding Info from target NG-RAN node
9.2.1.16

>>Secondary Data Forwarding Info from target NG-RAN node List

O

9.2.1.31

This IE would be present only when the target M-NG-RAN node decide to split a PDU session between MN and SN

YES

ignore

>>PDU Session Resource Setup Complete Info – SN terminated

O

9.2.1.30

>>DRB IDs taken into use

O

DRB List 9.2.1.29

Indicating the DRB IDs taken into use by the target NG-RAN node, as specified in TS 37.340 [8].

YES

reject

>>Data Forwarding Info from target E-UTRAN node

O

9.2.1.35

YES

ignore

CHO MR-DC Indicator

O

ENUMERATED (true, …)

Indicating that the XN-U ADDRESS INDICATION message is for Conditional Handover, as specified in TS 37.340 [8].

YES

reject

CHO MR-DC Early Data Forwarding Indicator

O

ENUMERATED (stop, …)

YES

ignore

CPC Data Forwarding indicator

O

ENUMERATED (triggered, early data transmission stop, …)

Indicating that the XN-U ADDRESS INDICATION message is for a Conditional PSCell Change.

YES

reject

Range bound

Explanation

maxnoofPDUSsessions

Maximum no. of PDU sessions. Value is 256

9.1.1.12 HANDOVER SUCCESS

This message is sent by the target NG-RAN node to the source NG-RAN node to indicate the successful access of the UE toward the target NG-RAN node.

Direction: target NG-RAN node  source NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

ignore

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID

9.2.3.16

Allocated at the source NG-RAN node.

YES

reject

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID

9.2.3.16

Allocated at the target NG-RAN node.

YES

reject

Requested Target Cell ID

M

Target Cell Global ID

9.2.3.25

Target cell indicated in the corresponding Handover Preparation procedure

YES

reject

9.1.1.13 CONDITIONAL HANDOVER CANCEL

This message is sent by the target NG-RAN node to the source NG-RAN node to cancel an already prepared conditional handover.

Direction: target NG-RAN node  source NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

ignore

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the source NG-RAN node.

YES

ignore

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the target NG-RAN node.

YES

reject

Candidate Cells To Be Cancelled List

0 .. <maxnoofCellsinCHO>

YES

reject

>Target Cell ID

M

Target Cell Global ID

9.2.3.25

Cause

M

9.2.3.2

YES

ignore

Range bound

Explanation

maxnoofCellsinCHO

Maximum no. cells that can be prepared for a conditional handover. Value is 8.

9.1.1.14 EARLY STATUS TRANSFER

This message is sent by the source NG-RAN node to the target NG-RAN node to transfer the COUNT value related to the forwarded downlink SDUs during DAPS Handover or Conditional Handover.

For MR-DC with 5GC, the message is also used, during a Conditional Handover, to transfer from the source S-NG-RAN node to the source M-NG-RAN node, the COUNT value related to the forwarded downlink SDUs.

For MR-DC with NG SCG, this message is also used, during a CPAC, to transfer from the source S-NG-RAN node to the M-NG-RAN node, and from the M-NG-RAN node to the target S-NG-RAN node, the COUNT value related to the forwarded downlink SDUs.

Direction: source NG-RAN node  target NG-RAN node (DAPS Handover or Conditional Handover).

Direction: source S-NG-RAN node  source M-NG-RAN node (Conditional Handover)

Direction: M-NG-RAN node  S-NG-RAN node (Conditional PSCell Addition)

Direction: source S-NG-RAN node  M-NG-RAN node (Conditional PSCell Change)

Direction: M-NG-RAN node  target S-NG-RAN node (Conditional PSCell Change)

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

ignore

Source NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the source NG-RAN node.

YES

reject

Target NG-RAN node UE XnAP ID

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated for handover at the target NG-RAN node.

YES

reject

CHOICE Procedure Stage

M

YES

reject

>First DL COUNT

>>DRBs Subject To Early Status Transfer List

M

1

>>>DRBs Subject To Early Status Transfer Item

1 .. <maxnoofDRBs>

>>>>DRB ID

M

9.2.3.33

>>>>CHOICE First DL COUNT

M

>>>>>12 bits

>>>>>> FIRST DL COUNT Value

M

COUNT Value for PDCP SN Length 12 9.2.3.36

PDCP-SN and Hyper frame number of the first DL SDU forwarded to the receiving NG-RAN node in case of 12 bit long PDCP-SN

>>>>>18 bits

>>>>>> FIRST DL COUNT Value

M

COUNT Value for PDCP SN Length 18 9.2.3.37

PDCP-SN and Hyper frame number of the first DL SDU forwarded to the receiving NG-RAN node in case of 18 bit long PDCP-SN

>DL Discarding

>>DRBs Subject To DL Discarding List

M

1

>>>DRBs Subject To DL Discarding Item

1 .. <maxnoofDRBs>

>>>>DRB ID

M

9.2.3.33

>>>>CHOICE DL Discarding

M

>>>>>12 bits

>>>>>> DISCARD DL COUNT Value

M

COUNT Value for PDCP SN Length 12 9.2.3.36

PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs associated with lower values in case of 12 bit long PDCP-SN

>>>>>18 bits

>>>>>> DISCARD DL COUNT Value

M

COUNT Value for PDCP SN Length 18 9.2.3.37

PDCP-SN and Hyper frame number for which the receiving NG-RAN node should discard forwarded DL SDUs associated with lower values in case of 18 bit long PDCP-SN

Range bound

Explanation

maxnoofDRBs

Maximum no. of DRBs allowed towards one UE. Value is 32.

9.1.1.15 RAN MULTICAST GROUP PAGING

This message is sent by the NG-RAN node1 to NG-RAN node2 to page UEs for a multicast session.

Direction: NG-RAN node1  NG-RAN node2.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

MBS Session ID

M

9.2.3.146

YES

reject

UE Identity Index List

1

YES

reject

>UE Identity Index Item

1 .. <maxnoofUEIDOindicesforMBSPaging>

>>CHOICE UE Identity Index Value

M

>>>Length-10

>>>>Index Length-10

M

BIT STRING (SIZE(10))

Coded as specified in TS 38.304 [33].

>>Paging DRX

O

UE Specific DRX

9.2.3.143

Includes the UE specific paging cycle as defined in TS 38.304 [33].

Multicast RAN Paging Area

M

RAN Paging Area

9.2.3.38

YES

reject

Range bound

Explanation

maxnoofUEIDIndicesforMBSPaging

Maximum no. of UE Identity Indices for multicast group paging. Value is 4096.

9.1.1.16 RETRIEVE UE CONTEXT CONFIRM

This message is sent by the new NG-RAN node to the old NG-RAN node to inform the old NG-RAN node whether the S-NG-RAN node associated with the old NG-RAN node for the UE that was indicated during UE context retrieval is kept or not by the new NG-RAN node during RRC resumption.

In case of RACH based SDT without UE context relocation, the Retrieve UE Context Confirm procedure is also used to request termination of SDT session from the new NG-RAN node to the old NG-RAN node.

Direction: new NG-RAN node  old NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node

YES

ignore

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

UE Context Kept Indicator

O

9.2.3.68

YES

ignore

SDT Termination Request

O

ENUMERATED (radio link problem, normal, …)

Indicate the reason of request for termination of an ongoing SDT session.

YES

ignore

9.1.1.17 PARTIAL UE CONTEXT TRANSFER

This message is sent by the old NG-RAN node to transfer part of the UE Context to the new NG-RAN node.

Direction: old NG-RAN node  new NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node.

YES

reject

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node.

YES

ignore

Partial UE Context Information for SDT

M

9.2.3.164

YES

ignore

9.1.1.18 PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE

This message is sent by the new NG-RAN node to acknowledge the transferring part of the UE context from the old NG-RAN node. This message is also used to provide data forwarding related information for NR SDT.

Direction: new NG-RAN node  old NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node

YES

ignore

SDT Data Forwarding DRB List

0..1

YES

ignore

>SDT Data Forwarding DRB Item

1..<maxnoofDRBs>

>>DRB ID

M

9.2.3.33

>>DL TNL Information

O

UP Transport Layer Information 9.2.3.30

Criticality Diagnostics

O

9.2.3.3

YES

ignore

Range bound

Explanation

maxnoofDRBs

Maximum no. of DRBs. Value is 32.

9.1.1.19 PARTIAL UE CONTEXT TRANSFER FAILURE

This message is sent by the new NG-RAN node to inform the old NG-RAN node that the Partial UE Context Transfer procedure has failed.

Direction: new NG-RAN node  old NG-RAN node.

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Criticality

Assigned Criticality

Message Type

M

9.2.3.1

YES

reject

New NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the new NG-RAN node

YES

ignore

Old NG-RAN node UE XnAP ID reference

M

NG-RAN node UE XnAP ID
9.2.3.16

Allocated at the old NG-RAN node.

YES

ignore

Cause

M

9.2.3.2

YES

ignore

Criticality Diagnostics

O

9.2.3.3

YES

ignore