Comment: (Vladimir Y.) The whole text is about E2E slicing, not RAN slicing. See e.g. the diagram
...
A service is the business entity that connects properties if the intended function with guaranties (SLA) and other business-related concepts. The term “service” is used interchangeable in the literature – sometimes to denote the blue-print or descriptor for how to create instances of that service, and sometimes to denote a particular instance (the word “instance” is simply omitted).
Comment: (Vladimir Y.) There is no definition of service in 28.801v1.3.0. So this is a new definition which is not really in the scope. Suggest to remove this part.
...
A network slice subnet instance (NSSI) constituent may include NF(s) and other NSSI(s).
Comment (Vladimir Y.) How is the right hand side of the diagram relevant to the document?
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Goal
Comment (Vladimir Y.) In 3GPP the 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?
Comment (Shekar S): I might have rephrased the goal as "Slice-related requests from a system upstream of ONAP (e.g. Ordering system, Operator GUI) is received by ONAP. ONAP performs the slice-related request; upon successful completion of the request, ONAP starts or continues to monitor the Slice. It is assumed that the request contains all of the required information necessary for completing the request (based on the design specification)". I used the phrase "Slice-related request" because there could be many types of requests (e.g. Initial creation of a slice, Modification of an existing Slice, etc.)
Comment (Vladimir Y.) I agree with Shekar: it can be any authorized caller. We can say "A request (for example, from ...) is received ...". The syntax of the request can be as in IFA013 (Instantiate NS operation with reference to NSD plus reference to NS DF).
Comment (Vladimir Y.) Need a link to the reference model (TMN?). In 3GPP reference model there is no Service Management Function (yet).
Use Case 1: Design slice template
...
Use Case 3: Manage the slice SLA/SLO
Comment (Vladimir Y.) These "use cases" (maybe better call it "scenarios"? We already have Use Cases) need clarification. How #2 is different from #1?
If we already refer to 28.801, there is description of network slice LCM operations: create (instantiate), activate, de-activate etc.
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. If the group is OK with such direction, I can provide the text.
- Define model/attributes for slice and its relationship to underlying VNF/Resources
- Design parameters needed for use by ONAP Optimization Framework (HAS) for decomposition and placement of resources needed for the slice
Design recipes/models for instantiating slices, modifying / expanding / shrinking slices, etc.
Design recipes/models for instantiating dedicated resources (e.g. AR / VR server)
Question (Stephen Terrill): what constitutes a dedicated resource? I agree we need to do this, but how to treat e.g. transport tin this context.
Comment (Shekar S): I would assume that the upfront planning/design specifies what is dedicated and what is shared (part of the slice definition)Comment (Vladimir Y.) There is no explanation in NGMN and 3GPP what "dedicated resources" (for the slice) are. I suggest that we either explain what "dedicated resources"are or remove the notion of "dedicated resources"
- Create an abstracted view of the services provided by the RAN, Transport, Core network functions, and create configuration parameters for these
- Author policy definitions and their enforcement points (VNF, Controllers, DCAE / SO, etc.)
- Specify fault, performance and log data collection, Analytics, thresholds for violations, and associated corrective action
...
-------- Temporary Text ----------
...
Instantiate NS operation