...
Goal
Comment (Vladimir Y.) In 3GPP t We need to decide what is the genre of this section: is it like Use Case in 3GPP (pre-condition, then steps, then post-condition) or it's Requirements. Currently it's sort of both.he text below would be titled "pre-condition" (of a Use Case). Suggest to change the title to "Pre-condition"
A request from the order handling system (the Service Management Function in OSS/BSS) is received by ONAP. ONAP instantiates the slice without any manual operator interaction. ONAP start actively monitoring the slice.
Question (Peter L): Is this realistic? Won't it be a parameterized request that must match a prepared slice template, and if not all parameters for that template are provided the onap operator would need to fill that in? How do we distinguish the NS-MF and NSS-MF from other "functions" implemented by ONAP?
...
If we already refer to 28.801, there is description of network slice LCM operations: create (instantiate), activate, de-activate etc.
Comment (Vladimir Y.) This part below is in the format of requirements, not fully in line with previous
The ONAP Design Studio (SDC) must support the following capabilities
Comment (Vladimir Y.) I have a general comment to this part. We already have a reference to NSSI concept in 28.801. Network Slice Instance (NSI) is in fact a particular case of the NSSI. The concept of the NSSI can easily be mapped onto the "Network Service" (NS) in ETSI NFV. If we agree to go over this path, we will be able to "copy" where reasonable, the concepts, operations and structures defined in ETSI and accommodated in 3GPP. This includes also E2E vs. RAN-only slicing. If the group is OK with such direction, I can provide the text.
...
The Network slice instance is operational. ONAP is actively collecting measurement information for on the slice. All related Policies are deployed and active across the ONAP components.
...
-------- Temporary Text ----------
...
...