7 Transport layer
38.4123GPPNG signalling transportNG-RANRelease 17TS
SCTP (IETF RFC 4960 [2]) shall be supported as the transport layer of NG-C signalling bearer. The Payload Protocol Identifier (ppid) assigned by IANA to be used by SCTP for the application layer protocol NGAP is 60, and 66 for DTLS over SCTP (IETF RFC 6083 [8]). 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.
NG-RAN node and AMF shall support a configuration with a single SCTP association per NG-RAN node/AMF pair. Configurations with multiple SCTP endpoints per NG-RAN node/AMF pair should be supported. When configurations with multiple SCTP associations are supported, the AMF may request to dynamically add/remove SCTP associations between the NG-RAN node/AMF pair. Within the set of SCTP associations established between one AMF and NG-RAN node pair, the AMF may request the NG-RAN node to restrict the usage of SCTP association for certain types of NG-C signalling. If no restriction information is provided for an SCTP association, any type of NG-C signalling is allowed via the SCTP association. Selection of the SCTP association by the NG-RAN node and the AMF is specified in TS 23.501 [3] and TS 23.502 [4]. The NG-RAN node shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for NGAP is 38412. When the AMF requests to dynamically add additional SCTP associations between the NG-RAN node/AMF pair, the SCTP Destination Port number value may be 38412, or any dynamic port value (IETF RFC 6335 [9]). When the configuration with multiple SCTP endpoints per NG-RAN node is supported and the NG-RAN node wants to add additional SCTP endpoints, the RAN configuration update procedure shall be the first NGAP procedure triggered on an additional TNLA of an already setup NG-C interface instance after the TNL association has become operational, and the AMF shall associate the TNLA to the NG-C interface instance using the included Global RAN node ID.
Between one AMF and NG-RAN node pair:
– A single pair of stream identifiers shall be reserved over at least one SCTP association for the sole use of NGAP 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 NGAP 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 node 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 until after current SCTP association is failed, or TNL binding update is performed as described in TS 23.502 [3].
Transport network redundancy can 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 SCTP endpoint (in the NG-RAN node or AMF) may send an INIT, at any time for an already established SCTP association, which the other SCTP endpoint shall handle as defined in IETF RFC 4960 [2] in subclause 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-180541 |
Reflected agreed TP in RAN3-AH-1801 in 2018-01 (Sophia Antipolis) |
0.2.0 |
|||
|
2018-03 |
RAN3#99 |
R3-181587 |
Reflected agreed TP in RAN3#99 in 2018-03 (Athens) |
0.3.0 |
|||
|
2018-05 |
RAN3#100 |
R3-183591 |
Reflected agreed TP in RAN3#100 in 2018-05 (Busan) and made some editorial corrections |
0.4.0 |
|||
|
2018-06 |
RAN#80 |
RP-180681 |
Submitted to RAN plenary for Approval |
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 |
|
|
2018-09 |
RAN#81 |
RP-181922 |
0003 |
F |
NR Corrections (38.412 Baseline CR covering RAN3#101 agreements) |
15.1.0 |
|
|
2019-07 |
RAN#84 |
RP-191395 |
0008 |
1 |
F |
Clarify the support for multiple TNL Endpoints in the NG-RAN node |
15.2.0 |
|
2019-09 |
RAN#85 |
RP-192166 |
0010 |
1 |
F |
CR on PPID value for DTLS over SCTP |
15.3.0 |
|
2019-09 |
RAN#85 |
RP-192167 |
0011 |
1 |
F |
Use of SCTP ports for multiple TNLA |
15.3.0 |
|
2019-12 |
RAN#86 |
RP-192915 |
0012 |
– |
F |
Ambiguity with multiple SCTP associations in 38.412 |
15.4.0 |
|
2020-03 |
RAN#87-e |
RP-200425 |
0013 |
– |
F |
Rapporteur’s Update for 38.412 |
16.0.0 |
|
2020-09 |
RAN#89-e |
RP-201954 |
0015 |
2 |
A |
SCTP association change when current SCTP association is failed |
16.1.0 |
|
2022-03 |
SA#95-e |
Promotion to Release 17 without technical change |
17.0.0 |
||||