Versions Compared

Key

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

...

ScenarioAction(s)Scope in Honolulu
Core NSSMF has decided to instantiate a new Core NSSI. All Core NFs have to be instantiated newlyOOF will be triggered for determining the Core NF placementIntent is to cover this (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

AttributeDetails
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 RANWhere will distance or DC location be specified? Will it be part of AAI or ??? Shall we ignore this because of next attribute?
Latency of transportPart of TN BH Slice Profile

Question: Which Core NFs shall we consider for placement - only UPF to start with?

6. Enhancements in NST selection

...