Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

full Table of Contents for  TS 23.501  Word version:   16.3.0

Top   Up   Prev   Next
1…   3…   4…   4.2.4   4.2.5…   4.2.8            4.2.9…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8   5…   5.4…   5.6…   5.7…   5.8…   5.10…   5.16…   5.17   5.18…   5.27…   5.31   5.32   5.33   5.34   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…

 

5.35  Support for Integrated access and backhaul (IAB) [R16]Word-p. 312
5.35.1  IAB architecture and functional entities
Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links. The Uu backhaul links can exist between the IAB-node and:
  • a gNB referred to as IAB-donor; or
  • another IAB-node.
The part of the IAB node that supports the Uu interface towards the IAB-donor or another parent IAB-node (and thus manages the backhaul connectivity with the PLMN it is registered with) is referred to as an IAB-UE.
Reproduction of 3GPP TS 23.501, Figure 5.35.1-1: IAB architecture for 5GS
Figure 5.35.1-1: IAB architecture for 5GS
5.35.2  5G System enhancements to support IABWord-p. 313
5.35.3  Data handling and QoS support with IABWord-p. 314
5.35.4  Mobility support with IAB
5.35.5  Charging support with IABUp
5.35.6  IAB operation involving EPC
5.36  RIM Information Transfer [R16]Word-p. 315
The purpose of RIM Information Transfer is to enable the transfer of RIM (Remote Interference Management) information between two RAN nodes via 5GC. The RIM Information Transfer is specified in TS 38.413.
When the source AMF receives RIM information from source NG-RAN towards target NG-RAN, the source AMF forwards the RIM information to the target AMF, as described in TS 38.413, TS 29.518. The AMF does not interpret the transferred RIM information.

Up   Top   ToC