...
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.
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.
...
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.
...
| Slice Profile Attribute that needs decomposition | Decomposed Value sent to Near-RT RIC | RRM policy value to be sent to CU/DU | Remarks |
|---|---|---|---|
| maxNumberofUEs | Based 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). |
|
| 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). |
| ||
| areaTrafficCapDL, areaTrafficCapUL | Based 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)) |
|
|
3. Enhancements in NSI/NSSI selection
...
In Honolulu, we can consider 2 cloud instances (one edge DC and one regional DC), and based on the Slice Profile, we could consider Core NF placement - e.g., for a URLLC slice (low latency), we could place UPF in the edge DC.
| Scenario | Action(s) | Scope in Honolulu |
|---|---|---|
| Core NSSMF has decided to instantiate a new Core NSSI. All Core NFs have to be instantiated newly | OOF will be triggered for determining the Core NF placement | In scope, see details below the table |
| Core NSSMF has decided to instantiate a new Core NSSI. Some Core NFs have to be instantiated newly (e.g., UPF), while others shall be reused (e.g., AMF) - this is determined by examining the shareability of Core NFs and feasibility to support the new NSSI (based on capacity/resource occupancy levels/scaleability). | OOF will be triggered for determining the Core NF placement for the new Core NFs. In case of scaling any existing Core NF, OOF shall be triggered for placement of new instance. (Note: This also has implications in Modeling of Core NS, and resourceSharingLevel of Core NSSI) | Out of scope |
| Core NSSMF has decided to reuse an existing Core NSSI. All Core NFs shall be reused, without scaling. | No impact. | Covered |
| Core NSSMF has decided to reuse an existing Core NSSI. All Core NFs shall be reused, one or more with scaling. | OOF shall be triggered for placement of new instance. | Out of scope |
| Core NSSMF has decided to reuse an existing Core NSSI with modifications. Some Core NFs shall be reused (with/without scaling) while others have to be instantiated newly or selected from those serving other NSSIs. | OOF will be triggered for determining the Core NF placement for the new Core NFs. In case of scaling any existing Core NF, OOF shall be triggered for placement of new instance. For selecting Core NFs serving other NSSIs, OOF may be triggered considering placement also. (Note: This also has implications in Modeling of Core NS, and resourceSharingLevel of Core NSSI) | Out of scope |
Considerations for Honolulu
| Attribute | Details |
|---|---|
| Remaining Capacity (feasibility check) | Capacity could be simply based on number of NF instances that can be supported in a DC (configured), and number of instances active currently (fetched from AAI). Question: Will this work in case of CNFs? |
| Distance from RAN | Where will distance or DC location be specified? Will it be part of AAI or ??? Shall we ignore this because of next attribute? |
| Latency of transport | Part of TN BH Slice Profile |
Question: Which Core NFs shall we consider for placement - only UPF to start with?
...
Refer NST Selection for relevant info.
7. Slice Modification recommendations
| Drawio | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|