...
- 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"
Comment (Peter L) Whatever VNFs we decide to include in the CN NSSI would include such special-purpose VNFs - i.e. I can't see how it differs from any other VNF?- Create an abstracted view of the services provided by the RAN, Transport, Core network functions, and create configuration parameters for these
Comment (Peter L): Is this part of slicing - or should it be par of the Integrate RAN UC? - 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
The ONAP execution framework should support the following activities.
- The Orchestrator executes the E2E Slice creation / modification recipe
- Instantiate any new VNF needed for the slice
- Pass configuration specifications, as per abstraction standards, to the RAN controller for radio slice creation, and packet core for core slice creation
- Pass QoS, bandwidth, resiliency requirements for transport network to SDN-Controller
- Configure the vEPC using App-C, orchestrated by EPC resource and service orchestration
- Start data collection and service monitoring at the relevant DCAE locations
- Track inventory/topology of slices and their states with AAI
- Collect data and perform the needed analytics about the various slices
- Trigger corrective / remedial actions for detected network impairments and service level violations
- Closed loop action initiated using SO and / or controllers
Note: ONAP also needs to be able to instantiate the required ONAP components to support the slice.
- <<<<<< Lets work on a figure to put here to help the understanding. This would be good to describe RAN scope vs E2E scope (and EPC scope, etc.). >>>>>>
Post-Condition
...
...