...
Comment: (Vladimir Y.) Some of terms and concepts used in the text below are not defined in 3GPP or assume too specific implementation or cannot be easily interpreted (marked by red). They should be replaced with terms / concepts defined in 3GPP and/or generalized. Use of The terms "PLMN" and the label "PLMN-ID" is are misleading as slice instances and their RAN or CN components are not separated PLMNs
...
- The ONAP Service Designer define TOSCA templates for the reusable tasks, examples could be:
- Create a VLAN to be used for control and user data within an NSI
- Per CN node type: Create yet another node connected to the proper VLAN
- Per RAN resource to be shared (e.g. the EUtranCell): Reconfigure to use yet another PLMN and a specific VLAN for that PLMN
Question: How do we address the EUtranCell – do we need to model that entity and include all provided cells in e.g. the AAI? - Create a CN NSSI using provided VLAN tags and PLMNI-ID value with a specified “capacity” (the “capacity” value to be used to select number of CN nodes to spin up).
This also includes filtering or aggregation rules for DCAE to produce NSSI related FM/PM/Event data. - Create a RAN NSSI template using provided VLAN tags and PLMN-ID covering a specified set of cells. This also includes filtering or aggregation rules for DCAE to produce NSSI related FM/PM/Event data.
- Create a Service NSI used to instantiate, modify, and remove “Service 2”. This also includes filtering or aggregation rules for DCAE to produce NSI related FM/PM/Event data, aggregating that data into KPI values for SLA evaluation.
- The Service/Network Operator adds (or removes) a NSI in the production environment:
- The Service/Network Operator uses the ONAP Portal to add (or activate) a NSI
- The ONAP Service Designer (or the Service/Network operator using the portal) publish the availability of a NSI for usage over the ONAP NBI.<Does the Service Designer create NSI = Network Slice Instance?>
Question: What functionality do we have in e.g. AAI to control visibility of service templates, e.g. our NSI description for access over NBI?
Question: What functionality do we have in MSO to execute service instantiation requests originating from NBI?
Question: How does an external application figure out what service templates are available and what data are needed when using them? (assuming we should not ship the entire service template over NBI…) - An NSI related request is received over ONAP NBI (e.g. from an ordering system or operator GUI), the MSO appies theparameters applies the parameters to the NSI template and executes the request.
Question: Any improv,ments needed in the interaction between the external part and the MSO for starting such requests, monitor the progress of the request and reciving the result?
- The Service/Network Operator Operator verifies reception of NSI related KPI data using the ONAP Portal.
...
- How an external application, when requesting a slice (NSI), can also request KPI/SLA stats to be propagated back to the external application.
- Definition of slice related closed loop activities via the ONAP runtime – this functionality is generic regardless if a slice is involved or not, and thus it does not belong in a use case targeting slice management.
Exception: If the functionality is already in place, but we only lack the capability to focus selected automation on data and resources related to a specific slice only – in that case it’s viable to include the extension of existing automation functionality to also become slice aware.
---------- Temporary Text / Old Text ---------- Temporary Text / Old Text ----------
Comment (Peter L): Do you agree to my color coding below: Green: covered above/resolved Blue: out of scope/not applicable Red:remains to be resolved/discussed
Comment: (Vladimir Y.) Sorry, but no. Please refer to the red marks above. In some cases it is difficult to understand the text.
Goal
Comment (Vladimir Y.) 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.
...