5 NBAP signalling bearer
25.4323GPPRelease 17TSUTRAN Iub interface: signalling transport
5.1 Introduction
The Signalling Bearer for NBAP (TS 25.433 [21]) is a point-to-point protocol. There may be multiple point-to-point links between an RNC and a Node B. As shown in figure 1, the standard allows operators to choose one out of two protocol suites for transporting the NBAP messages.
Figure 1: Iub NBAP Signalling Transport
5.2 Signalling bearer in case of ATM Transport Option
The signalling bearer in the Radio Network Control Plane is SAAL-UNI (ITU-T Rec. Q.2100 [1]) over ATM. The protocols to be used to support NBAP signalling are SSCF-UNI (ITU-T Rec. Q.2130 [2]) on top of SSCOP (ITU-T Rec. Q.2110 [3]) and AAL Type 5 (ITU-T Rec. I.363.5 [4]).
5.3 Signalling bearer in case of IP Transport Option
SCTP (IETF RFC 2960 [7]) over IP shall be supported as the transport for NBAP signalling bearer on Iub Interface. A RNC equipped with the SCTP stack option shall initiate the INIT procedure for establishing association. The data link layer is as specified in chapter 4.2.
The checksum method specified in IETF RFC 3309 [20] shall be used instead of the method specified in IETF RFC 2960 ([7]).
An IP UTRAN node shall support IPv6 (IETF RFC 2460 [8]). The support of IPv4 (IETF RFC 791 [9]) is optional.
NOTE: This does not preclude single implementation and use of IPv4.
IP dual stack is recommended for the potential transition period from IPv4 to IPv6 in the transport network.
Each signalling bearer between the RNC and Node B shall correspond to one single SCTP stream in UL and one single SCTP stream in DL direction, both streams belonging to the same SCTP association.
IP Differentiated Services code point marking (IETF RFC 2474 [10]) shall be supported. The Diffserv code point may be determined from the application parameters.
Annex A (informative):
Change history
|
Date / TSG |
TSG Doc. |
CR |
Rev |
Subject/Comment |
New |
|
12/2008 |
– |
– |
– |
Creation of Rel-8 version based on v7.1.0 |
8.0.0 |
|
12/2009 |
– |
– |
– |
Creation of Rel-9 version based on v8.0.0 |
9.0.0 |
|
SP-49 |
SP-100629 |
Clarification on the use of References (TS 21.801 CR#0030) |
9.0.1 |
||
|
03/2011 |
Creation of Rel-10 version based on v9.0.1 |
10.0.0 |
|||
|
52 |
RP-110685 |
0008 |
1 |
Correction to the References |
10.1.0 |
|
09/2012 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||
|
09/2014 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||
|
12/2015 |
Update to Rel-13 version (MCC) |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
Promotion to Release 14 without technical change |
14.0.0 |
||||
|
2018-07 |
SA#80 |
– |
– |
– |
– |
Promotion to Release 15 without technical change |
15.0.0 |
|
2020-07 |
SA#88-e |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-03 |
SA#95-e |
Promotion to Release 17 without technical change |
17.0.0 |
||||