5 Xn interface user plane protocol

38.4243GPPNG-RANRelease 16TSXn data transport

5.1 General

The transport layer for data streams over Xn is an IP based Transport. The following figure shows the transport protocol stacks over Xn.

Figure 5.1: Transport network layer for data streams over Xn

The GTP-U (TS 29.281 [2]) protocol over UDP over IP shall be supported as the transport for data streams on the Xn interface. The data link layer is as specified in clause 4.

The transport bearer is identified by the GTP-U TEID (TS 29.281 [3]) and the IP address (source TEID, destination TEID, source IP address, destination IP address).

5.2 GTP-U

The GTP-U (TS 29.281 [2]) protocol shall be used over the Xn interface between two NG-RAN nodes.

5.3 UDP/IP

The path protocol used shall be UDP (IETF RFC 768 [3]).

The UDP port number for GTP-U shall be as defined in TS 29.281 [2].

The NG-RAN nodes over the Xn interface shall support fragmentation and assembly of GTP packets at the IP layer.

The NG-RAN nodes shall support IPv6 (IETF RFC 8200 [5]) and/or IPv4 (IETF RFC 791 [6]).

There may be one or several IP addresses in both NG-RAN nodes. The packet processing function in the source NG-RAN node shall send downstream packets of a given flow to the target NG-RAN node IP address (received in XnAP) associated to the DL transport bearer of that particular flow. The packet processing function in the source NG-RAN node shall send upstream packets of a given flow to the target NG-RAN node IP address (received in XnAP) associated to the UL transport bearer of that particular flow.

The Transport Layer Address signalled in XnAP messages is a bit string of:

a) 32 bits in case of IPv4 address according to IETF RFC 791 [6]; or

b) 128 bits in case of IPv6 address according to IETF RFC 8200 [5]; or

c) 160 bits if both IPv4 and IPv6 addresses are signalled, in which case the IPv4 address is contained in the first 32 bits.

5.4 DiffServ code point marking

IP Differentiated Services code point marking (IETF RFC 2474 [4]) shall be supported. The mapping between traffic categories and DiffServ code points shall be configurable by O&M based on 5G QoS Class Identifier (5QI) , the Priority Level (if explicitly signalled), and other NG-RAN traffic parameters (e.g. ARP). Traffic categories are implementation-specific and may be determined from the application parameters.

Annex A (informative):
Change history

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

May 2017

R3#96

R3-171482

Initial draft TS

0.0.2

May 2017

R3#96

R3-172020

FFS for GTP-U reference

Flows instead of bearers

Diffserv codepoints and 5QI

0.1.0

June 2017

R3 NR#02

R3-172635

0.1.0 agreed

0.2.0

January 2018

R3 NR#03

R3-180546

Correct specification name, NG-RAN node instead of Gnb

0.3.0

April 2018

R3#99bis

R3-182528

Editorial in document title

Remove FFS

0.4.0

June 2018

RAN#80

RP-180814

Presentation to RAN

1.0.0

2018-06

RAN#80

Specification approved at TSG-RAN and placed under change control

15.0.0

2018-09

RAN#81

RP-181920

0001

F

Updated reference to IPv6

15.1.0

2019-07

RAN#84

RP-191396

0005

1

F

Use of Priority Level and ARP for the DSCP Derivation at the gNB

15.2.0

2020-07

RAN#88-e

RP-201085

0006

F

Rapporteur’s Update for 38.424

16.0.0