-
A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs;
-
One gNB-DU is connected to only one gNB-CU-CP;
-
One gNB-CU-UP is connected to only one gNB-CU-CP;
-
One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP;
-
One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP;
-
Here I try to depict the functional split of RNL(Layer 2) between gNB-CU and gNB-DU based on 3GPP specification.
LinkedIn: Rahim Navaei on LinkedIn: #5g #5gnr #4g
1 Like
๐ก๐ฒ๐ฒ๐ฑ ๐ผ๐ณ ๐ฆ๐ฒ๐ฝ๐ฎ๐ฟ๐ฎ๐๐ฒ ๐จ๐๐ฒ๐ฟ ๐ฎ๐ป๐ฑ ๐๐ผ๐ป๐๐ฟ๐ผ๐น ๐ฃ๐น๐ฎ๐ป๐ฒ ๐ถ๐ป ๐ฑ๐
๐ฟ๐๐๐๐๐ง๐๐ฃ๐ฉ ๐ฉ๐ฎ๐ฅ๐ ๐ค๐ ๐ฟ๐๐ซ๐๐๐๐จ
-
MMTC devices needs very less amount of Data but use equivalent amount of Signaling , We need to scale Signaling Infrastructure for such devices
-
eMBB devices consumes lots of Data , We need to Scale User Plane Infrastructure for such devices
-
No Separation of Control and Signaling Plane would lead to scaling up overall capacity of Node for both User and Control plane which is wastage & Inefficient way to scale capacity
๐๐๐ฉ๐๐ฃ๐๐ฎ ๐๐๐ฆ๐ช๐๐ง๐๐ข๐๐ฃ๐ฉ๐จ
-
Latency Sensitive Applications needs user plane to be situated Geographically near to users ( Regional , Local or Zonal Deployment of User plane capacities ) , While control plane Nodes can deployed centrally at one location for easy maintenance , operations & administration
-
This will also help us to save Media / Transmission costs also
๐ผ๐๐ซ๐๐ฃ๐ฉ๐๐๐๐จ ๐ค๐ ๐พ๐๐๐
-
Reducing Latency on User Plane
-
Support Rapid Increase of Data Traffic
-
Better Administration and Operational Control
-
Better Integration with SDN
-
Minimizing Wastage of Unused capacity
Credits: 
