...
- Generate valid combinations of Slice Profiles based on sub-net capabilities, meeting the Service Profile constraints.
- Select the Slice Profiles which are 'closest' to existing Slice Profiles in terms of performance requirements - 'closeness' could be given a weight per attribute (we could start with a limited set of attributes, say latency, throughput, we could end up in 2 scenarios: say, 2 Slice Profiles (e.g., RAN and Core) are close, while 3rd (TN) is far off, all 3 are 'somewhat' close - in such a case, we should have some a mechanism to select the the most appropriate one. This would require 'normalization' of attributes, and whether greater closeness for one or more attributes should be preferred over a normalized sum of closeness across all attributes.
5. Core NF placement
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.
...