Versions Compared

Key

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

...

For NSI selection, for the above proposal of coverageArea specification, OOF can check if the coverageArea is a subset of the coverageArea of an existing NSI (when sharing is allowed)  en when determining feasibility of reuse. It would be better to do this check in a separate method, so that it can be easily replaced by another one, when a different approach of specifying coverageArea is adopted. This check can be taken up even beyond H-release.

2. Decomposition of RAN NF Slice Profile for each Near-RT RIC

...

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.


Slice Profile Attribute that needs decompositionDecomposed Value sent to Near-RT RICRRM 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
on expDataRateDL (currently copied from dLThptPerSlice) and expDataRateUL (currently copied from uLThptPerSlice) and the ratio of coverage area of the Near-RT RIC over the total coverage area (determined by number of cells mapped under it).

expDataRateDL, expDataRateUL(At present, this has to be determined from the value in the Slice Profile divided by (number of UEs * activity factor. Later when this carries the data rate per UE correctly, no decomposition is required))
  • At present, total PRBs (across NRCellDUs, GNBDUFunctions for the S-NSSAI) to be determined based on average of
areaTrafficCapDL and areaTrafficCapUL
  • expDataRateDL and expDataRateUL . 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.
  • Later, when expDataRateDL and expDataRateUL convey the data rate per UE, the total per slice shall be determined using number of UEs and activity factor.


3. Enhancements in NSI/NSSI selection

...

Refer NST Selection for relevant info.

7. Slice Modification recommendations

Drawio
bordertrue
diagramNameslice modification
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth741
revision1