Scribd
Upload
251 views

5G NR-Load Sharing and Load Balancing Optimization: (As Per 3GPP TS37.816 v16.0.0)

Load sharing and balancing across cells, carriers, and RATs can improve network efficiency. This includes distributing cell load evenly, offloading congested cells, and achieving energy savings. For 5G NR, load sharing should consider new features like network slicing and be optimized across DUs, CU-UPs, and between LTE and NR. Solutions involve reporting load metrics over X2, Xn, F1 and E1 interfaces, including composite available capacity, load levels, PRB usage, and transport network load. Further work is needed to specify load metrics and management procedures in 3GPP Release 16.

Uploaded by

mohamed fadl
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
251 views

5G NR-Load Sharing and Load Balancing Optimization: (As Per 3GPP TS37.816 v16.0.0)

Load sharing and balancing across cells, carriers, and RATs can improve network efficiency. This includes distributing cell load evenly, offloading congested cells, and achieving energy savings. For 5G NR, load sharing should consider new features like network slicing and be optimized across DUs, CU-UPs, and between LTE and NR. Solutions involve reporting load metrics over X2, Xn, F1 and E1 interfaces, including composite available capacity, load levels, PRB usage, and transport network load. Further work is needed to specify load metrics and management procedures in 3GPP Release 16.

Uploaded by

mohamed fadl
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

5G NR-Load Sharing and Load Balancing Optimization

(as per 3GPP TS37.816 v16.0.0)


As a very good saying among kids is SHARING IS CARING

So is with the technologies stands true for its resources. Optimization and shared resources always pay
and the technologies up-gradation also implies towards the same.

Improved resource efficiency can be achieved by capacity sharing or load balancing

1. Use case description


The objective of load sharing and load balancing is to distribute cell load evenly among cells or to transfer
part of the traffic from congested cell, or to offload users from one cell or carrier or RAT to achieve
network energy saving, This can be done by means of optimization of cell reselection/handover
parameters and handover actions. The automation of such optimization can provide high quality user
experience, while simultaneously improving the system capacity and also to minimize human intervention
in the network management and optimization tasks.

Compared to LTE, NR new features, e.g. CU/DU split and CP-UP separation architecture, network slicing,
and EN-DC/MR-DC should be considered in the load sharing and load balancing optimization in NR.
Study on load sharing and balancing across DUs within one gNB is needed (load management over F1),
as well as load sharing and balancing across CU-UPs within one gNB (E1 load management). It should
be studied whether slicing level metrics e.g. slice level radio resource utilization and slice availability also
need to be taken into account for the reselection/handover parameters and handover action optimization.

Both intra-RAT and inter-RAT load balancing scenarios should be supported. LTE is the baseline, studies
for NR will focus on:

1) Definition of the data required the load sharing and load balancing;

2) Functionalities and actions required to support the load sharing and load balancing, e.g. load
reporting architecture, adapting handover and/or reselection configuration.

2.Solution description
There are possible solutions that enable load management over X2, Xn, F1 and E1 interfaces. On X2 and
Xn, the reported information should contain at least cell level load (e.g. resource utilization). Likewise,
similar information is required from the gNB-DU to gNB-CU over F1 in case of disaggregated architecture.
For E1, load information should also be provided from the gNB-CU-UP to the gNB-CU-CP.

Furthermore, which procedure (i.e. new, reuse of existing one) and the periodicity (i.e. periodic reporting,
event-triggered) needs to be considered.

And indicative summary of the load related information discussed during the study phase is summarized
in below Table. More discussions may be needed during normative phase to specify the details of the
metrics reported below.
Load Related Information

Load Category Load Related Information X2 Xn F1 E1


Cell Level Composite Available Capacity (CAC) ● ● ●
Cell Level Cell Level Load (DL/UL/SUL) ● ● ●
Cell Level Cell Level Load per Slice ● ●
Cell Level Cell Level Load per Band ● ● ● ●
Cell Level PRB Usage for SUL ● ● ●
Cell Level Number of RRC Connections ● ●
Beam Level PRB Usage for SSBs ● ● ●
Beam Level Composite Available Capacity (CAC) per SSB Beam ● ● ●
Hardware Level HW Load Indicator ● ● ● ●
Hardware Level CU-CP Hardware Load ● ●
Hardware Level CU-UP Hardware Load ● ● ●
Hardware Level CU Hardware Load (CU-CP+CU-UP) ● ●
Hardware Level CU-UP (Hardware) Load per Slice ●
Hardware Level CU-UP Max Number of DRB Supported ●
Hardware Level DU Hardware Load ●
Hardware Level DU DRB Capacity ●
Transport Level TNL Load Indicator ● ● ● ●

3.Conclusion
Load sharing and load balancing functions over X2, Xn, F1 and E1 interfaces should be specified in
Release 16 normative phase. At least the following load related information should be specified. Whether
the reporting mechanism supports both periodic and event-triggered procedures is for further decision
during normative phase.

- Composite Available Capacity per cell (DL/UL), reported via X2, Xn and F1 interfaces

- Cell Level Load (DL/UL/SUL) reported via X2, Xn, and F1 interfaces

- TNL Load reported via X2, Xn, F1, and E1 interfaces

Further refinement on the above metrics, as well as an evaluation on whether these metrics are sufficient
for the correct functioning of the load management function and whether they should be complemented
with additional enhancements should take place during Release 16 normative phase.

Likewise, introduction of additional load information over X2, Xn, F1 and E1 interfaces is seen as potential
enhancement on several areas and may be considered for specification in Release 16. Details to be
further discussed during normative phase:

- Beam level load indication

- Hardware load related information

- Per slice/band level reporting

- For EN-DC case, the EN-DC X2 interface are enhanced to support load information report from
SgNB to MeNB

You might also like