Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For Honolulu, we can start with a very simple approach of doing this decomposition based on the number of cells controlled by each Near-RT RIC for a given S-NSSAI. 

Alternatively, we can do the split based on the PM data collected for each S-NSSAI at cell level, and taking capacity into consideration. For example:

  • Based on PDU sessions setup successfully overall in that cell (PM data) and consider the maximum number of UEs that can be supported by the cell (pre-configured limit) (and what is already allocated) to determine maxNumberofUEs for each Near-RT RIC scope for that S-NSSAI.
CellNear-RT RIC IdPDU sessions setup successfullyMaximum number of connections that can be supported (unallocated)
A15075
B125100
C24090

If Slice Profile has maxNumberofUEs = 120:

maxNumberofUEs for Near-RT RIC 1 = 120*(25+40)/(50+25+40), subject to constraint of supporting only a maximum of 90% of (75+100).

maxNumberofUEs for Near-RT RIC 2 = 120*(50)/(50+25+40), subject to constraint of supporting only a maximum of 90% of (90).

  • Based on DL/UL PRBs used (PM data) and consider the areaTrafficCapDL/areaTrafficCapUL that can be supported by the cell/TA (and what is already allocated) to determine for each areaTrafficCapDL/areaTrafficCapUL for each Near-RT RIC scope for that S-NSSAI.

...