7 Transport layer

38.4223GPPNG-RANRelease 16TSXn signalling transport

SCTP (IETF RFC 4960 [2]) shall be supported as the transport layer of Xn-C signalling bearer. The Payload Protocol Identifier (ppid) assigned by IANA to be used by SCTP for the application layer protocol XnAP is 61, and 67 for DTLS over SCTP (IETF RFC 6083 [7]). The byte order of the ppid shall be big-endian.

SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.

An NG RAN node shall support a configuration with a single SCTP association per NG RAN node pair. Configurations with multiple SCTP endpoints per the NG RAN node pair should be supported. When configurations with multiple SCTP associations are supported, the NG RAN node may request to dynamically add/remove SCTP associations between the NG RAN node pair. Within the set of SCTP associations established between one NG RAN node pair, a single SCTP association shall be employed for XnAP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. The SCTP Destination Port number value assigned by IANA to be used for XnAP is 38422. When a NG-RAN node requests to dynamically add additional SCTP associations between the NG RAN node pair, the SCTP Destination Port number value may be 38422, or any dynamic port value (IETF RFC 6335 [8]). The NG RAN node configuration update procedure shall be the first XnAP procedure triggered on an additional TNLA of an already setup Xn-C interface instance after the TNL association has become operational, and the peer NG RAN node shall associate the TNLA to the Xn-C interface instance using the included Global NG-RAN Node ID.

Between one pair of two NG-RAN nodes:

– a single pair of stream identifiers shall be reserved over an SCTP association for the sole use of XnAP elementary procedures that utilize non UE-associated signalling.

– At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of XnAP elementary procedures that utilize UE-associated signallings. However, a few pairs (i.e. more than one) should be reserved.

– For a single UE-associated signalling, the NG RAN nodes shall use one SCTP association and one SCTP stream and the SCTP association/stream should not be changed during the communication of the UE-associated signalling unless TNL binding update is performed.

Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from one NG-RAN node, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 [2] in sub clause 5.2.

The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages.

Annex A (informative):
Change history

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2018-01

RAN3-AH-1801

R3-180544

Reflected agreed TP in RAN3-AH-1801 in 2018-01 (Sophia Antipolis)

0.2.0

2018-05

RAN3#100

R3-183596

Reflected agreed TP in RAN3#100 in 2018-05 (Busan) and made some editorial corrections

0.3.0

2018-06

RAN#80

RP-180682

Submitted to RAN plenary for Approval

1.0.0

2018-06

RAN#80

RP-181276

Typos corrected ("NGAP" corrected to "XnAP" in two places)

1.0.1

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

2018-12

RAN#82

RP-182447

0003

F

Enabling multiple SCTP associations

15.2.0

2019-09

RAN#85

RP-192166

0005

1

F

CR on PPID value for DTLS over SCTP

15.3.0

2019-09

RAN#85

RP-192167

0007

1

F

Use of SCTP ports for multiple TNLA

15.3.0

2019-12

RAN#86

RP-192915

0008

F

Ambiguity with multiple SCTP associations in 38.422

15.4.0

2020-03

RAN#87-e

RP-200425

0009

F

Rapporteur’s Update for 38.422

16.0.0