11 Overall procedures in NG-RAN Architecure
38.4013GPPArchitecture descriptionNG-RANRelease 17TS
11.1 Multiple TNLAs for Xn-C
In the following, the procedure for managing multiple TNLAs for Xn-C is described.
Figure 11.1-1: Managing multiple TNLAs for Xn-C.
1. The NG-RAN node1 establishes the first TNLA with the NG-RAN node2 using a configured TNL address.
NOTE: The NG-RAN node1 may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the NG-RAN node1 gets the remote IP end point(s) and its own IP address are outside the scope of this specification.
2-3. Once the TNLA has been established, the NG-RAN node1 initiates the Xn Setup procedure to exchange application level configuration data
4-6. The NG-RAN node2 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node2 to request the NG-RAN node1 to modify or release TNLA(s).
7-9. The NG-RAN node1 may add additional TNL Endpoint(s) to be used for Xn-C signalling between the NG-RAN node1 and the NG-RAN node2 pair using the NG-RAN node Configuration Update procedure. NG-RAN node Configuration Update procedure also allows the NG-RAN node1 to request the NG-RAN node2 to modify or release TNLA(s).
The XnAP UE TNLA binding is a binding between a XnAP UE association and a specific TNL association for a given UE. After the XnAP UE TNLA binding is created, the NG-RAN node1 or the NG-RAN node2 can update the UE TNLA binding by sending the first available XnAP message for the UE to the peer NG-RAN node via a different TNLA. The peer NG-RAN node shall update the XnAP UE TNLA binding with the new TNLA.
Annex A (informative):
Deployment scenarios of gNB/en-gNB
Figure A-1 shows logical nodes (CU-C, CU-U and DU), internal to a logical gNB/en-gNB. Protocol terminations of the NG and Xn interfaces are depicted as ellipses in Figure A-1. The terms "Central Entity" and "Distributed Entity" shown in Figure A-1 refer to physical network nodes.
Figure A-1: Example deployment of an Logical gNB/en-gNB
Annex B:
NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast (informative)
Each gNB-DU serving a cell identified by a Cell Identity associated with a subset of PLMNs is connected to a gNB-CU via a single F1-C interface instance.
Each F1-C interface instance is setup individually.
F1-C interface instances terminating at gNB-DUs which share the same physical radio resources may share the same F1-C signalling transport resources. If this option is applied,
– non-UE associated signalling is associated to an F1-C interface instance by allocating the corresponding Transaction ID from a value range associated to that F1-C interface instance.
– node related, non-UE associated F1-C interface signalling may provide information destined for multiple logical nodes in a single F1AP procedure instance once the F1-C interface instance is setup.
NOTE 1: If the Transaction ID corresponds to more than one interface instance, the respective F1AP message carries information destined for multiple logical nodes.
– a UE associated signalling connection is associated to an F1-C interface instance by allocating values for the corresponding gNB-DU UE F1AP ID and gNB-CU UE F1AP ID so that they can be mapped to that interface instance.
NOTE 2: One possible implementation is to partition the value ranges of the gNB-DU UE F1AP ID and gNB-CU UE F1AP ID and associate each value range with an F1-C interface instance.
Interpreting the content of RRC MSG3 and other unciphered RRC message by the gNB-DU is supported.
Content for System Information Broadcast is assumed to be coordinated among the sharing PLMNs. PLMN specific SIB1 content is controlled by the respective PLMN owner. Non PLMN specific content needs coordination to avoid contradicting indication by PLMN specific gNB-CUs. For Warning messages (SIB6, SIB7 and SIB8), if provided by more than one gNB-CU, warning message duplicates are identified by provision of the Message Number and the Serial Number by the gNB-CU and don’t trigger new broadcast or replace existing broadcast. Other coordination between gNB-CUs is ensured by appropriate implementation.
Annex C (informative):
Change History
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-04 |
RAN3#95bis |
R3-171307 |
First Draft |
0.0.1 |
|||
|
2017-05 |
RAN3#96 |
R3-171962 |
Reflected agreed TP in RAN3#96. Added new Clause 8 for overall procedure for gNB-CU/DU architecture |
0.1.0 |
|||
|
2017-06 |
RAN3#NR Ad Hoc |
R3-172634 |
Reflected agreed TP in RAN3#NR Ad Hoc in 2017-06 (Qingdao) |
0.2.0 |
|||
|
2017-08 |
RAN3#97 |
R3-173449 |
Reflected agreed TP in RAN3#97 |
0.3.0 |
|||
|
2017-10 |
RAN3#97bis |
R3-174237 |
Reflected agreed TP in RAN3#97bis |
0.4.0 |
|||
|
2017-10 |
RAN3#97bis |
R3-174258 |
Removed subclauses under 10.3 (moved to 38.470) |
0.4.1 |
|||
|
2017-11 |
RAN3#98 |
R3-175054 |
Reflected agreed TP in RAN3#98 |
0.5.0 |
|||
|
2017-12 |
RP-78 |
RP-172545 |
Submit to RAN Plenary#78 for approval |
1.0.0 |
|||
|
2017-12 |
RP-78 |
TR Approved by RAN plenary |
15.0.0 |
||||
|
2018-03 |
RP-79 |
RP-180468 |
0007 |
1 |
– |
Correction on intra-gNB-DU handover |
15.1.0 |
|
2018-06 |
RP-80 |
RP-181237 |
0001 |
5 |
B |
Introduction of SA NR (38.401 Baseline CR covering RAN3 agreements) |
15.2.0 |
|
2018-06 |
RP-80 |
RP-181240 |
0008 |
4 |
B |
Introduction of Separation of CP and UP for Split Option 2 (38.401 Baseline CR covering RAN3 agreements) |
15.2.0 |
|
2018-06 |
RP-80 |
RP-181238 |
0012 |
1 |
F |
CR to TS38.401 on UL blockage |
15.2.0 |
|
2018-06 |
RP-80 |
RP-181238 |
0014 |
1 |
F |
CR to 38.401 on DL User Data to DU |
15.2.0 |
|
2018-06 |
RP-80 |
RP-181238 |
0016 |
– |
F |
TP for 38.401 in supporting full configuration |
15.2.0 |
|
2018-09 |
RP-81 |
RP-181922 |
0022 |
2 |
F |
NR Corrections (38.401 Baseline CR covering RAN3-101 agreements) |
15.3.0 |
|
2018-12 |
RP-82 |
RP-182707 |
0023 |
3 |
F |
NR Corrections (TS 38.401 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) |
15.4.0 |
|
2019-03 |
RP-83 |
RP-190554 |
0025 |
– |
F |
Correction to Intra-gNB-CU mobility |
15.5.0 |
|
2019-03 |
RP-83 |
RP-190560 |
0026 |
1 |
F |
Correction from Rapporteur for 38.401 |
15.5.0 |
|
2019-03 |
RP-83 |
RP-190554 |
0037 |
1 |
F |
About Cells Failed to be Activated IE |
15.5.0 |
|
2019-07 |
RP-84 |
RP-191394 |
0039 |
3 |
F |
Correction of AMF set related statements |
15.6.0 |
|
2019-07 |
RP-84 |
RP-191395 |
0063 |
1 |
F |
CR to 38.401 on Multiple TNLAs for F1-C and E1 |
15.6.0 |
|
2019-07 |
RP-84 |
RP-191395 |
0065 |
F |
Multiple TNLAs for Xn-C |
15.6.0 |
|
|
2019-07 |
RP-84 |
RP-191502 |
0043 |
2 |
F |
Clarify the support for multiple TNLAs for F1-C |
15.6.0 |
|
2019-07 |
RP-84 |
RP-191397 |
0067 |
1 |
F |
RAN sharing with multiple Cell ID broadcast |
15.6.0 |
|
2019-07 |
RP-84 |
RP-191396 |
0068 |
1 |
F |
Procedure description on optional IEs in CU to DU RRC information IE. |
15.6.0 |
|
2019-12 |
RP-86 |
RP-192916 |
0045 |
4 |
F |
Correction to RRC Inactive transition |
15.7.0 |
|
2019-12 |
RP-86 |
RP-192916 |
0104 |
– |
F |
Inter-gNB-DU mobility using MCG SRB procedure |
15.7.0 |
|
2019-12 |
RP-86 |
RP-192754 |
0105 |
2 |
F |
CR for RRC Container IE in Initial UL RRC Message Transfer procedure |
15.7.0 |
|
2019-12 |
RP-86 |
RP-192908 |
0060 |
4 |
B |
Introduction of RIM in TS 38.401 |
16.0.0 |
|
2019-12 |
RP-86 |
RP-192913 |
0075 |
1 |
F |
Trace function support stage-2 |
16.0.0 |
|
2019-12 |
RP-86 |
RP-192913 |
0097 |
2 |
F |
Introduction of common time standard source |
16.0.0 |
|
2019-12 |
RP-86 |
RP-192911 |
0107 |
2 |
F |
CR to 38.401 on corrections to ng-eNB deployment |
16.0.0 |
|
2019-12 |
RP-86 |
RP-192908 |
0109 |
– |
B |
Introduction of Cross-link Interference Management |
16.0.0 |
|
2019-12 |
RP-86 |
RP-192910 |
0112 |
– |
B |
Support of SN Resume during the RRCResume procedure |
16.0.0 |
|
2020-03 |
RP-87-e |
RP-200425 |
0114 |
– |
D |
Rapporteur updating of specification 38.401 |
16.1.0 |
|
2020-07 |
RP-88-e |
RP-201077 |
0033 |
21 |
B |
BL CR to 38.401 Support for IAB |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201082 |
0099 |
7 |
B |
Addition of MDT features |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201080 |
0102 |
6 |
B |
BL CR NPN for TS 38.401 |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201075 |
0110 |
6 |
B |
Baseline CR for introducing Rel-16 NR mobility enhancement |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201082 |
0116 |
4 |
B |
Addition of SON features |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201091 |
0122 |
1 |
A |
Correction for gNB-DU transmission stop descriptoin in the inter-gNB HO involving gNB-CU-UP change |
16.2.0 |
|
2020-07 |
RP-88-e |
RP-201085 |
0130 |
– |
F |
Rapporteur Corrections to 38.401 |
16.2.0 |
|
2020-09 |
RP-89-e |
RP-201945 |
0115 |
7 |
B |
F1 support for positioning |
16.3.0 |
|
2020-09 |
RP-89-e |
RP-201954 |
0135 |
2 |
A |
Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR |
16.3.0 |
|
2020-09 |
RP-89-e |
RP-201954 |
0137 |
2 |
A |
SCTP association change when current SCTP association is failed |
16.3.0 |
|
2020-09 |
RP-89-e |
RP-201947 |
0142 |
1 |
F |
Rapporteur Corrections to 38.401 |
16.3.0 |
|
2020-09 |
RP-89-e |
RP-201954 |
0148 |
2 |
A |
Correction for intra-gNB-DU handover description |
16.3.0 |
|
2020-12 |
RP-90-e |
RP-202311 |
0154 |
1 |
F |
Correction on CPC Complete Transfer |
16.4.0 |
|
2020-12 |
RP-90-e |
RP-202311 |
0156 |
3 |
F |
Correction of Intra-system HO data forwarding |
16.4.0 |
|
2021-03 |
RP-91-e |
RP-210231 |
0146 |
4 |
F |
Corrections on clarification of non-F1 traffic |
16.5.0 |
|
2021-03 |
RP-91-e |
RP-210233 |
0168 |
1 |
F |
Stage-2 CR on transmission stop for Rel-16 DAPS handover |
16.5.0 |
|
2021-06 |
RP-92-e |
RP-211317 |
0172 |
1 |
F |
Correction on Signalling based MDT Activation [NR_SON_MDT-Core] |
16.6.0 |
|
2021-09 |
RP-93-e |
RP-211882 |
0170 |
3 |
F |
Suspend Configuration |
16.7.0 |
|
2021-12 |
RP-94-e |
RP-212864 |
0188 |
1 |
F |
Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R16) |
16.8.0 |
|
2022-03 |
RP-95-e |
RP-220276 |
0193 |
2 |
F |
CR to 38.401: Correction on IPv6 Flow Label handling for IAB using IPsec tunnel mode |
16.9.0 |
|
2022-03 |
RP-95-e |
RP-220224 |
0153 |
13 |
B |
Introduction of NR MBS |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220221 |
0165 |
9 |
B |
BLCR to 38.401_Addition of SON features enhancement |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220935 |
0166 |
9 |
B |
BLCR to 38.401: Support of MDT enhancement |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220218 |
0174 |
7 |
B |
CPAC BL CR to TS38.401 |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220218 |
0176 |
10 |
B |
SCG BL CR to TS 38.401 |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220217 |
0178 |
7 |
B |
CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220222 |
0179 |
10 |
B |
BL CR to TS 38.401 on support of eIAB |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220230 |
0191 |
3 |
B |
Draft BL CR to TS 38.401 on RedCap UEs |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220233 |
0192 |
3 |
B |
RA-SDT BLCR to TS 38.401 |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220231 |
0195 |
3 |
B |
BL CR to TS38.401 on Rel-17 Sidelink Relay |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220233 |
0196 |
1 |
B |
CG-SDT BLCR to TS 38.401 |
17.0.0 |
|
2022-03 |
RP-95-e |
RP-220229 |
0198 |
– |
B |
BL CR to TS38.401 for alignment of MDT and QoE |
17.0.0 |
|
2022-06 |
RP-96 |
RP-221136 |
0202 |
1 |
F |
Correction on SDT |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221141 |
0207 |
1 |
F |
Corrections on MDT |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221139 |
0209 |
1 |
F |
CR on TS38.401 for Rel-17 Sidelink Relay |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221145 |
0210 |
2 |
D |
Rapporteur Update to TS 38.401 |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221134 |
0214 |
2 |
F |
Remove the editor’s notes related to consent information |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221135 |
0220 |
1 |
F |
CR to 38.401 for Corrections on Overall procedures for CPAC |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221141 |
0225 |
1 |
F |
Correction to 38.401 for SON features enhancement |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221135 |
0228 |
2 |
F |
Correction for stage 2 on SCG (de)activation |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221143 |
0232 |
1 |
F |
QoE Rel-17 Corrections |
17.1.0 |
|
2022-06 |
RP-96 |
RP-221128 |
0233 |
– |
F |
Stage-2 corrections on IAB architecture |
17.1.0 |
|
2022-07 |
Editorial correction – change the font style from "H1" to "normal" in clause 7.10. |
17.1.1 |
|||||
|
2022-09 |
RP-97-e |
RP-222189 |
0235 |
2 |
F |
Stage 2 Clarification on SDT to TS 38.401 |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222201 |
0239 |
2 |
F |
Correction on gNB-DU ID |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222189 |
0241 |
1 |
F |
Clarification to CG based SDT |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222183 |
0242 |
– |
F |
Correction on protocol stack for IAB |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222188 |
0244 |
– |
F |
Further Corrections for NR MBS |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222183 |
0246 |
2 |
F |
Corrections for Rel-17 IAB on topology adaptation |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222183 |
0250 |
2 |
F |
Corrections on IAB inter-CU topology adaptation |
17.2.0 |
|
2022-09 |
RP-97-e |
RP-222190 |
0252 |
1 |
F |
Correction to 38.401 for SL relay |
17.2.0 |