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.


Cell
Slice Profile Attribute that needs decompositionDecomposed Value sent to Near-RT RIC
IdPDU sessions setup successfullyMaximum number of connections that can be supported (unallocated)A15075B125100C24090

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.

Beyond Honolulu, we can further enhance it to generate the optimal decomposition using more sophisticated mechanism, and additional inputs.

maxNumberofUEs

coverageAreaTAList

latency

uEMobilityLevel

resourceSharingLevel

Slice Profile Attribute that needs decompositionDecomposed Value sent to Near-RT RICRRM policy value to be sent to CU/DU/RUmaxNumberofUEsRRC (NRCellCU, GNBCUCPFunction) = expDataRateDL (Integer), expDataRateUL (Integer), areaTrafficCapDL (Integer), areaTrafficCapUL (Integer), overallUserDensity (Integer),cSAvailabilityTarget (Float), cSReliabilityMeanTime (String), , expDataRate (Integer), msgSizeByte (String), transferIntervalTarget (String), survivalTime (String

The resource type of interest for an RRM Policy.

 

allowedValues:

PRB (for NRCellDU, GNBDUFunction)

RRC connected users (for NRCellCU, GNBCUCPFunction)

DRB (for GNBCUUPFunction)

See NOTE 2and NOTE 4
RRM policy value to be sent to CU/DURemarks
maxNumberofUEsBased on RRC (RRM Policy) distribution across cells (NRCellCUs), maxNumberofUEs split to be determined (using activityFactor).Total RRC (across NRCellCUs, GNBCUCPFunctions for the S-NSSAI) to be determined based on activityFactor and maxNumberofUEs. Then RRC to be distributed across the NRCellCUs in the coverageAreaTAList based on current RRC occupancy levels (i.e., % already consumed by other slice instances).
  • activityFactor shall also be sent to Near-RT RIC (Service Profile → Slice Profile → info to be passed to Near-RT RIC without any modifications)
  • Can PDU sessions setup successfully overall in that cell (PM data) also be used to determine initial RRC setting?
  • What about adaptations to RRC later based on PM data - will Near RT RIC do it?
  • Assumption on total RRC capacity per cell to be made (100% = e.g., 1000 RRCs). This can be made configurable by storing it in CPS.


Total DRBs (across GNBCUUPFunctions) to be determined to be determined based on activityFactor and maxNumberofUEs (and average number of radio bearers per UE???). Then DRB to be distributed across the GNBCUUPFunctions in the coverageAreaTAList based on current DRB occupancy levels (i.e., % already consumed by other slice instances).
  • Assumption on total DRB capacity per cell to be made (100% = e.g., 1000 DRBs). This can be made configurable by storing it in CPS.
 areaTrafficCapDL, areaTrafficCapULBased on PRB distribution, dLThptPerSlice, uLThptPerSlice shall be determined.Total PRBs (across NRCellDUs, GNBDUFunctions for the S-NSSAI) to be determined based on average of areaTrafficCapDL and areaTrafficCapUL. Then PRB to be distributed across the NRCellDUs in the coverageAreaTAList based on current PRB occupancy levels (i.e., % already consumed by other slice instances).
  • Assumption on 1 PRB = x kbps shall be made.


3. Enhancements in NSI/NSSI selection

...