5G NR gNB Logical Architecture and It’s Functional Split Options

by · Published · Updated

The logical architecture of gNB is shown in figure below with Central Unit (CU) and Distributed Unit (DU). Fs-C and Fs-U provide control plane and user plane connectivity over Fs interface.

In this architecture, Central Unit (CU) and Distribution Unit (DU) can be defined as follows.

Central Unit (CU): It is a logical node that includes the gNB functions like Transfer of user data, Mobility control, Radio access network sharing, Positioning, Session Management etc., except those functions allocated exclusively to the DU. CU controls the operation of DUs over front-haul (Fs) interface. A central unit (CU) may also be known as BBU/REC/RCC/C-RAN/V-RAN

Distributed Unit (DU): This logical node includes a subset of the gNB functions, depending on the functional split option. Its operation is controlled by the CU. Distributed Unit (DU) also known with other names like RRH/RRU/RE/RU.

Central Unit (CU) and Distributed Unit Functional Split Options

As a part of study item for New Radio (NR), 3GPP started studying different functional splits between central and distributed units. For the initial phase, 3GPP has taken LTE protocol stack as a basis for the discussion, until RAN2 defines and freezes the protocol stack for New Radio (NR). They have proposed about 8 possible options shown in below figure.

  • Option 1 (RRC/PCDP 1A-like split)
  • Option 2 (PDCP/RLC Split 3C-like split)
  • Option 3 (High RLC/Low RLC split, Intra RLC split)
  • Option 4 (RLC-MAC split)
  • Option 5 (Intra MAC split)
  • Option 6 (MAC-PHY split)
  • Option 7 (Intra PHY split)
  • Option 8 (PHY-RF split)

Option 1 (RRC/PDCP, 1A-like split): In this split option, RRC is in the central unit while PDCP, RLC, MAC, physical layer and RF are kept in the distributed unit. Thus the entire user plane is in the distributed unit.

Option 2 (PDCP/RLC split): Option 2 may be a base for an X2-like design due to similarity on U-plane but some functionality may be different e.g. C-plane since some new procedures may be needed. There are two possible variants available in this option.

  • Option 2-1 Split U-plane only (3C like split): In this split option, RRC, PDCP are in the central unit. RLC, MAC, physical layer and RF are in the distributed unit.
  • Option 2-2: In this split option, RRC, PDCP are in the central unit. RLC, MAC, physical layer and RF are in the distributed unit.  In addition, this option can be achieved by separating the RRC and PDCP for the CP stack and the PDCP for the UP stack into different central entities.

Option 3 (High RLC/Low RLC Split): In this option, two approaches are taken based on Real time/Non-Real time functions split which are as follows:

  • Option 3-1 Split based on ARQ
  • Option 3-2 Split based on TX RLC and RX RLC

Option 3-1 Split based on ARQ

  • Low RLC may be composed of segmentation functions;
  • High RLC may be composed of ARQ and other RLC functions;

This option splits the RLC sublayer into High RLC and Low RLC sublayers such that for RLC Acknowledge Mode operation, all RLC functions may be performed at the High RLC sublayer residing in the central unit, while the segmentation may be performed at the Low RLC sublayer residing in the distributed unit. Here, High RLC segments RLC PDU based on the status reports while Low RLC segments RLC PDU into the available MAC PDU resources.

Option 3-2 Split based on TX RLC and RX RLC

  • Low RLC may be composed of transmitting TM RLC entity, transmitting UM RLC entity, a transmitting side of AM and the routing function of a receiving side of AM, which are related to downlink transmission.
  • High RLC may be composed of receiving TM RLC entity, receiving UM RLC entity and a receiving side of AM except for the routing function and reception of RLC status reports, which are related to uplink transmission.

Option 4 (RLC-MAC split): In this split option, RRC, PDCP, and RLC are in the central unit. MAC, physical layer, and RF are in the distributed unit.

Option 5 (Intra MAC split)

Option 5 assumes the following distribution:

  • RF, physical layer and lower part of the MAC layer (Low-MAC) are in the Distributed Unit
  • Higher part of the MAC layer (High-MAC), RLC and PDCP are in the Central Unit

Therefore, by splitting the MAC layer into 2 entities (e.g. High-MAC and Low-MAC), the services and functions provided by the MAC layer will be located in the Central Unit (CU), in the Distributed Unit (DU), or in both. An example of this kind distribution given below.

  • In High-MAC sublayer the centralized scheduling in the High-MAC sublayer will be in charge of the control of multiple Low-MAC sublayers. It takes high-level centralized scheduling decision. The inter-cell interference coordination in the High-MAC sublayer will be in charge of interference coordination methods such as JP/CS CoMP.
  • In Low-MAC sublayer the time-critical functions in the Low-MAC sublayer include the functions with stringent delay requirements (e.g. HARQ) or the functions where performance is proportional to latency (e.g. radio channel and signal measurements from PHY, random access control). It reduces the delay requirements on the fronthaul interface. Radio specific functions in the Low-MAC sublayer can for perform scheduling-related information processing and be reporting. It can also measure/estimate the activities on the configured operations or the served UE’s statistics and report periodically or as requested to the High-MAC sublayer.

Option 6 (MAC-PHY split): The MAC and upper layers are in the central unit (CU). PHY layer and RF are in the DU. The interface between the CU and DUs carries data, configuration, and scheduling-related information (e.g. MCS, Layer Mapping, Beamforming, Antenna Configuration, resource block allocation, etc.) and measurements.

Option 7 (Intra PHY split): Multiple realizations of this option are possible, including asymmetrical options which allow obtaining benefits of different sub-options for UL and DL independently.

This option requires some kind of compression technique to reduce transport bandwidth requirements between the DU and CU.

  • In the UL, FFT, and CP removal reside in the DU and for the two sub-variants, 7-1 and 7-2 are described below. Remaining functions reside in the CU.
  • In the downlink, iFFT and CP addition reside in the DU and the rest of the PHY resides in the CU.

Considering above there are three sub-variant available for this option described as below

Option 7-1 In this option the UL, FFT, CP removal and possibly PRACH filtering functions reside in the DU, the rest of PHY functions reside in the CU. In the DL, iFFT and CP addition functions reside in the DU, the rest of PHY functions reside in the CU.

Option 7-2 In this option the UL, FFT, CP removal, resource de-mapping and possibly pre-filtering functions reside in the DU, the rest of PHY functions reside in the CU. In the DL, iFFT, CP addition, resource mapping and precoding functions reside in the DU, the rest of PHY functions reside in the CU.

Option 7-3 (Only for DL): Only the encoder resides in the CU, and the rest of PHY functions reside in the DU.

Option 8 (PHY-RF split): This option allows to separate the RF and the PHY layer. This split permit centralization of processes at all protocol layer levels, resulting in very tight coordination of the RAN. This allows efficient support of functions such as CoMP, MIMO, load balancing, mobility.

Benefits of RAN Spilt Architecture

Some of the benefits of an architecture with the deployment flexibility to split and move New Radio (NR) functions between central and distributed units are below:

  • Flexible HW implementations allows scalable cost-effective solutions
  • A split architecture (between central and distributed units) allows for coordination for performance features, load management, real-time performance optimization, and enables NFV/SDN
  • Configurable functional splits enables adaptation to various use cases, such as variable latency on transport
Which split function to use where?

The choice of how to split New Radio (NR) functions in the architecture depends on some factors related to radio network deployment scenarios, constraints and intended supported services. Some examples of such factors are:

  • Support of specific QoS per offered services (e.g. low latency, high throughput)
  • Support of specific user density and load demand per given geographical area (which may influence the level of RAN coordination)
  • Availability transport networks with different performance levels, from ideal to non-ideal
  • Application type e.g. Real-time or Non- Real Time
  • Features requirement at Radio Network level e.g. CA, eICIC, CoMP etc.

Reference:

  • 3GPP TR 38.801 Radio Access Architecture and Interfaces Release 14

Related Post



Tags:

You may also like...