TS 38.420
NG-RAN — Xn interface –
General Aspects and Principles
V18.1.0 (PDF)
2024/03 20 p.
V17.2.0
2022/09 19 p.
V16.0.0
2020/06 18 p.
V15.2.0
2018/12 16 p.
- Rapporteur:
- Mr. Krishnan, Shankar
Qualcomm Incorporated
Content for TS 38.420 Word version: 18.1.0
1 Scope
2 References
3 Definitions and abbreviations
4 General aspects
5 Functions of the Xn interface
5.1 General
5.2 Functions of Xn-C
5.3 Functions of Xn-U
6 Xn interface procedures
6.1 General
6.2 Control plane protocol procedures
6.3 User plane protocol procedures
7 Xn interface protocol structure
7.1 Xn Control Plane
7.2 Xn User Plane
8 Other Xn interface specifications
$ Change history
1 Scope p. 6
The present document is an introduction to the TSG RAN TS 38.42x series of Technical Specifications that define the Xn interface. It is an interface for the interconnection of two NG-RAN nodes within the NG-RAN architecture (TS 38.401).
2 References p. 6
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 38.401: "NG-RAN; Architecture description".
[3]
TS 38.421: "NG-RAN; Xn layer 1".
[4]
TS 38.422: "NG-RAN; Xn signalling transport".
[5]
TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[6]
TS 38.424: "NG-RAN; Xn data transport".
[7]
TS 38.425: "NG-RAN; NR user plane protocol".
[8]
TS 38.300: "NR; Overall Description; Stage 2".
[9]
TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
[10]
TS 38.415: "PDU Session User Plane protocol".
[11]
TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
3 Definitions and abbreviations p. 6
3.1 Definitions p. 6
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
AI:
as defined in TS 38.300.
Boundary IAB-node:
as defined in TS 38.401.
corresponding node:
as defined in TS 38.425.
F1-terminating IAB-donor:
as defined in TS 38.401.
IAB-DU:
as defined in TS 38.300.
IAB-MT:
as defined in TS 38.300.
Mobile IAB-node:
as defined in TS 38.300.
Non-F1-terminating IAB-donor:
as defined in TS 38.401.
ML:
as defined in TS 38.300.
NG-RAN node:
as defined in TS 38.300.
RRC-terminating IAB-donor:
as defined in TS 38.401.
secondary node:
as defined in TS 37.340.
3.2 Abbreviations p. 7
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
IAB
Integrated Access and Backhaul
MBS
Multicast Broadcast Service
QMC
QoE Measurement Collection
QoE
Quality of Experience
SCTP
Stream Control Transmission Protocol
Xn-C
Xn Control plane
Xn-U
Xn User plane
4 General aspects p. 7
4.1 Introduction p. 7
The interface allowing to interconnect NG-RAN nodes with each other is referred to as the Xn interface.
4.2 Xn interface general principles p. 7
The general principles for the specification of the Xn interface are as follows:
- the Xn interface is open;
- the Xn interface supports the exchange of signalling information between two NG-RAN nodes, and the forwarding of PDUs to the respective tunnel endpoints;
- from a logical standpoint, the Xn is a point-to-point interface between two NG-RAN nodes. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two NG-RAN nodes.
4.3 Xn interface specification objectives p. 7
The Xn interface specifications facilitate the following:
- inter-connection of NG-RAN nodes supplied by different manufacturers;
- support of continuation between NG-RAN nodes of the NG-RAN services offered via the NG interface;
- separation of Xn interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology.
4.4 Xn interface capabilities p. 8
The Xn interface supports:
- procedures to support intra-NG-RAN mobility;
- procedures to support dual connectivity between NG-RAN nodes.
5 Functions of the Xn interface p. 8
5.1 General p. 8
The following clauses describe the functions supported in Xn interface.
5.2 Functions of Xn-C p. 8
5.2.1 Xn-C interface management and error handling functions p. 8
5.2.1.1 General p. 8
These functions allow for managing of signalling associations between NG-RAN nodes, surveying the Xn interface and recovering from errors.
5.2.1.2 Xn Setup function p. 8
This function allows for the initial setup of an Xn interface between two NG-RAN nodes, including exchange of application level data.
5.2.1.3 Error Indication function p. 8
This function allows the reporting of general error situations on application level.
5.2.1.4 Xn reset function p. 8
This function allows an NG-RAN node to inform a second NG-RAN node that it has recovered from an abnormal failure and that either all or some of the contexts (except the application level data) related to the first node and stored in the second shall be deleted, and the associated resources released.
5.2.1.5 Xn configuration data update function p. 8
This function allows two NG-RAN nodes to update application level data at any time.
5.2.1.6 Xn removal function p. 8
This function allows two NG-RAN nodes to remove the respective Xn interface.
5.2.2 UE mobility management functions p. 8
5.2.2.1 Handover preparation function p. 8
This function allows the exchange of information between source and target NG-RAN nodes in order to initiate the handover of a certain UE to the target.
5.2.2.2 Handover cancellation function p. 9
This function allows informing an already prepared target NG-RAN node that a prepared handover will not take place. It allows releasing the resources allocated during a preparation.
5.2.2.3 Retrieve UE Context function p. 9
The Retrieve UE context function is used for a NG-RAN node to retrieve UE context from another one.
5.2.2.4 RAN Paging function p. 9
The RAN paging function allows a NG-RAN node to initiate the paging for a UE in the inactive state.
5.2.2.5 Data Forwarding control function p. 9
The data forwarding control function allows establishing and releasing transport bearers between source and target NG-RAN nodes for data forwarding.
5.2.2.6 Handover Success Indication Function |R16| p. 9
This function allows informing a source NG-RAN node that the UE has successfully accessed a target NG-RAN node.
5.2.2.7 Conditional Handover cancellation function |R16| p. 9
This function allows informing a source NG-RAN node that resources reserved for candidate target cell(s) during a conditional handover preparation are about to be released by the target NG-RAN node.
5.2.3 Dual connectivity function p. 9
The dual connectivity function enables usage of additional resources in a secondary node in the NG-RAN.
5.2.4 Energy saving function p. 9
This function enables decreasing energy consumption by indication of cell activation/deactivation or SSB beam activation/deactivation over the Xn interface.
5.2.5 Resource coordination function p. 9
This function enables coordination of cell resource usage between two NG-RAN nodes.
5.2.6 Secondary RAT Data Volume Report function p. 9
This function enables the NG-RAN node to report Secondary RAT usage data information in case of MR-DC with 5GC, either with a dedicated procedure or by including Secondary RAT usage data information in other messages.
5.2.7 Trace function |R16| p. 9
The Trace function provides means to control trace sessions for a UE over Xn interface.
5.2.8 Load management function |R16| p. 9
This function allows exchanging resource status and traffic load information between NG-RAN nodes, such that the NG-RAN node can control the traffic load appropriately.
5.2.9 Data exchange for self-optimisation function |R16| p. 9
This function allows two NG-RAN nodes to exchange information in order to support self-optimization functionality.
5.2.10 IAB support function |R17| p. 10
5.2.10.1 F1-C Traffic Transfer function p. 10
This function is used to deliver F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected IAB-node, where the F1-C traffic is either received from the IAB-node or sent to the IAB-node.
5.2.10.2 IAB Transport Migration function p. 10
This function allows the exchange of information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, for the purpose of managing the migration of the boundary and descendant IAB-node traffic between the topologies managed by the two IAB-donors. This function also allows the exchange of information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node, for the purpose of managing the migration of the mobile IAB-node traffic between the topologies managed by the two IAB-donors. This function also allows the exchange of information, e.g., the authorization status, of IAB-nodes or mobile IAB-nodes.
5.2.10.3 IAB Resource Coordination function p. 10
This function is used to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node in order to support resource multiplexing between the IAB-MT and the IAB-DU of the boundary IAB-node. This function is also used to exchange resource multiplexing related information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node in order to support resource multiplexing between the IAB-MT and the IAB-DU of the mobile IAB-node.
5.2.11 Small data transmission function |R17| p. 10
5.2.11.1 General p. 10
This function supports small data transmission sessions in RRC_INACTIVE both with and without anchor relocation.
5.2.11.2 Partial UE Context Transfer function p. 10
The Partial UE Context Transfer function is used for the last serving NG-RAN node to provide part of the UE Context to the receiving gNB.
5.2.12 QMC support function |R17| p. 10
The QMC function provides means to support the mobility of QMC sessions over the Xn interface and to support the coordination of QMC information in case of dual connectivity.
5.2.13 MBS management support function |R17| p. 10
This function is used to support the management of MBS Sessions, including the addition of MBS related information in interface management and mobility procedures, and the support of RAN Multicast paging.
5.2.14 AI/ML support function |R18| p. 10
This function is used to support AI/ML for NG-RAN, including initiation of data collection and reporting of collected data.
5.3 Functions of Xn-U p. 11
5.3.1 Data transfer function p. 11
The data transfer function allows the transfer of data between NG-RAN nodes to support dual connectivity or mobility operation.
5.3.2 Flow control function p. 11
The flow control function enables a NG-RAN node receiving user plane data from a second NG-RAN node to provide feedback information associated with the data flow.
5.3.3 Assistance information function p. 11
The assistance information function enables a NG-RAN node receiving user plane data from a second NG-RAN node to provide assistance information to the second node (e.g. related to radio conditions).
5.3.4 Fast retransmission function p. 11
The fast retransmission function provides coordination between PDCP-hosting node and corresponding node in case of outage in one of the nodes, to enables the node in good RF conditions to handle data previously forwarded to the node in outage.
6 Xn interface procedures p. 11
6.1 General p. 11
The Xn interface supports procedures over the control plane (Xn-C) and user plane (Xn-U).
6.2 Control plane protocol procedures p. 11
6.2.1 Mobility management procedures p. 11
The mobility management procedures are used to manage the UE mobility in Connected or RRC_Inactive modes:
- Handover Preparation
- Handover Cancel
- SN Status Transfer
- Retrieve UE Context
- RAN Paging
- Xn-U Address Indication
- UE Context Release
- Handover Success Indication
- Conditional Handover Cancel
- Retrieve UE Context Confirm
6.2.2 Dual Connectivity procedures p. 12
The dual connectivity procedures are used to add, modify and releases resources for the operation of Dual Connectivity:
- S-NG-RAN-node Addition Preparation
- S-NG-RAN-node Reconfiguration Completion
- M-NG-RAN-node initiated S-NG-RAN-node Modification Preparation
- S-NG-RAN-node initiated S-NG-RAN-node Modification
- M-NG-RAN-node initiated S-NG-RAN-node Release
- S-NG-RAN-node initiated S-NG-RAN-node Release
- S-NG-RAN-node Counter Check
- RRC Transfer
- Notification Control Indication
- Activity Notification
- Secondary RAT Data Usage Report
- Conditional PSCell Change Cancel
6.2.3 Global procedures p. 12
The global procedures are used to exchange configuration level data between two NG-RAN nodes, or to remove Xn connectivity between two NG-RAN nodes in a controlled manner:
- Xn Setup
- NG-RAN-node Configuration Update
- Xn Removal
6.2.4 Interface Management procedures p. 12
The interface management procedures are used to align resources between two NG-RAN nodes in the event of failures, and to report detected protocol errors:
- Reset
- Error Indication
6.2.5 Energy saving procedures p. 12
- Cell Activation procedure: enables an NG-RAN node to request the activation of a previously deactivated cell or SSB beam hosted in another NG-RAN node.
6.2.6 Resource coordination procedures |R16| p. 12
- E-UTRA - NR Cell Resource Coordination procedure: enables an ng-eNB and a gNB to interact for resource coordination purposes.
6.2.7 UE Tracing procedures |R16| p. 12
The following procedures are used to trace the UE:
- Trace Start procedure
- Deactivate Trace procedure
- Cell Traffic Trace
6.2.8 Load management procedures |R16| p. 13
The load management procedures are used by NG-RAN nodes to indicate resource status, overload and traffic load to each other.
- Resource Status Reporting Initiation
- Resource Status Reporting
6.2.9 Data exchange for self-optimisation procedures |R16| p. 13
The data exchange for self-optimisation procedures are used to transfer failure, access and mobility related information among NG-RAN nodes to enable self-optimisation
- Failure Indication
- Handover report
- Mobility Settings Change
- Access and Mobility Indication
- SCG Failure Information Report
- SCG Failure Transfer
- RACH Indication
6.2.10 IAB procedures |R17| p. 13
The IAB procedures are used to enable the transfer of F1/non-F1 traffic for IAB, to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to enable the delivery of F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected non-boundary IAB-node, to exchange resource multiplexing related information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to exchange information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node, to exchange resource multiplexing related information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of the mobile IAB-node, to exchange information, e.g., the authorization status, of IAB-nodes or mobile IAB-nodes:
- F1-C Traffic Transfer
- IAB Transport Migration Management
- IAB Transport Migration Modification
- IAB Resource Coordination
6.2.11 MBS Management procedures |R17| p. 13
The MBS management procedures are used to manage the MBS Session:
- RAN Multicast Group Paging procedure
6.2.12 Small data transmission procedures |R17| p. 13
Small data transmission is also supported by the following procedures:
- Partial UE Context Transfer: enables exchange of information between NG-RAN nodes for SDT transmission without anchor relocation
- RRC Transfer
- Retrieve UE Context Confirm
- RAN Paging
6.2.13 QMC support procedures |R17| p. 14
The following procedures are used to transfer QMC configuration and session information to the target NG-RAN node during UE intra-system intra-RAT mobility:
- Handover Preparation.
- Retrieve UE Context.
- Handover Preparation.
- S-NG-RAN node Addition Preparation
- M-NG-RAN node initiated S-NG-RAN node Modification Preparation
- S-NG-RAN node initiated S-NG-RAN node Modification
- S-NG-RAN node initiated S-NG-RAN node Change
- RRC Transfer
6.2.14 AI/ML support procedures |R18| p. 14
The following procedures are used to initiate data collection and report collected data to support, e.g., AI/ML for NG-RAN:
- Data Collection Reporting Initiation
- Data Collection Reporting
6.3 User plane protocol procedures p. 14
The user plane protocol procedures are used to exchange user plane information between Xn-U protocol peers:
- Transfer of Downlink User Data procedure: enables the node hosting the NR PDCP entity to provide user plane information to the corresponding node.
- Downlink Data Delivery Status procedure: enables the corresponding node to provide feedback to the node hosting the NR PDCP entity.
- Transfer of Assistance Information: enables the corresponding node to provide assistance information to the node hosting the NR PDCP entity.
- Transfer of PDU Session Information procedure: enables an NG-RAN node to provide user plane information associated with the forwarding of data towards a peer NG-RAN node, when using PDU session tunnels.
7 Xn interface protocol structure p. 15
7.1 Xn Control Plane p. 15
The control plane protocol stack of the Xn interface is shown on Figure 7.1-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as XnAP (Xn Application Protocol).
7.2 Xn User Plane p. 15
The Xn user plane (Xn-U) interface is defined between two NG-RAN nodes. The Xn-U interface provides non-guaranteed delivery of user plane PDUs between two NG-RAN nodes.
The protocol stack for Xn-U is shown in Figure 7.2-1.
The user plane packets conveyed by GTP-U may be PDCP PDUs (e.g. in case of dual connectivity), PDCP SDUs (e.g. in case of DRB level data forwarding), or SDAP SDUs (e.g. in PDU Session level data forwarding).
User plane protocol messages (as defined in TS 38.425 and TS 38.415) are carried by container fields in the GTP-U extension header as specified in TS 29.281. A single GTP-U packet may carry a user plane packet and/or a user plane protocol message. The mapping between container fields and Xn user plane protocol procedures and functions is described in Table 7.2-1.
| Xn-U Function | Container Type | Xn UP Protocol Procedure |
|---|---|---|
| Data transfer | NR RAN Container, as per TS 29.281 (Note 1) | Transfer of Downlink User Data, TS 38.425 |
| PDU Session Container, as per TS 29.281 (Note 2) | Transfer of DL PDU Session Information, TS 38.415 Transfer of UL PDU Session Information, TS 38.415 | |
| PDU Set Information Container, as per TS 29.281 (Note 5) | Transfer of DL PDU Set Information Container, TS 38.415 | |
| No container (Note 3) | NA | |
| Flow control | NR RAN Container as per TS 29.281 (Note 4) | Downlink Data Delivery Status, TS 38.425 Transfer of Downlink User Data, TS 38.425 |
| Fast retransmission | NR RAN Container as per TS 29.281 (Note 4) | Downlink Data Delivery Status, TS 38.425 Transfer of Downlink User Data, TS 38.425 |
| Assistance information | NR RAN Container as per TS 29.281 (Note 4) | Transfer of Assistance Information, TS 38.425 |
|
NOTE 1:
optionally used in Dual Connectivity DL data transfer.
NOTE 2:
in case of PDU Session level forwarding only.
NOTE 3:
all other cases of data transfer when no other Xn-U functionality is required
NOTE 4:
optionally used in Dual Connectivity
NOTE 5:
optionally used in case forwarding PDU Set Information container is required
|
||
8 Other Xn interface specifications p. 16
8.1 NG-RAN Xn interface: Xn layer 1 (TS 38.421) p. 16
TS 38.421 specifies the physical layer technologies that may be used to support the Xn interface.
8.2 NG-RAN Xn interface: Xn signalling transport (TS 38.422) p. 16
TS 38.422 specifies how the XnAP signalling messages are transported over Xn.
8.3 NG-RAN Xn interface: Xn application protocol (XnAP) (TS 38.423) p. 16
TS 38.423 specifies the radio network layer signalling procedures of the control plane between NG-RAN nodes.
8.4 NG-RAN Xn interface: Xn data transport (TS 38.424) p. 16
TS 38.424 specifies the standards for user data transport protocols over the NG-RAN Xn interface.
8.5 NG-RAN Xn interface: NR user plane protocol (TS 38.425) p. 17
TS 38.425 specifies the user plane protocol procedures for dual connectivity over the NG-RAN Xn interface.
8.6 NG-RAN Xn interface: PDU Session User Plane Protocol (TS 38.415) p. 17
TS 38.415 specifies the user plane protocol procedures for data forwarding using PDU Session tunnels over the NG-RAN Xn interface.
TS 38.415 specifies the PDU Set Information user plane protocol for sending PDU Set Information and indication of End of Data Burst over the NG-RAN Xn interface.
8.7 Summary of NG-RAN Xn interface Technical Specifications p. 17
The relationship between the technical specifications that define the NG-RAN Xn interface is shown in Figure 8.7-1.
$ Change history p. 18
