...
- Abstraction of the services offered by the different domains/segments
- Ability to tie the services offered by the different domains/segments into an e2e service.
- Support the network to provide isolation between the slices (to the extent that is reasonable according to the networks capabilities).
In order simplify the use case, a network plan containing as few as possible of the above listed participating elements should be used.
Service and Slice concepts according to 3GPP TR 28.801v2.0.1 (2017-09) (was: 1.3.0)
...
Comment (Vladimir Y.) These are not "layers", simply interconnection between CSMF, NSMF and NSSMF which is not that important. If we want to address these functions in ONAP, some text is needed saying exactly that.
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Comment (Peter L): Re-writing this section, trying to catch the commens. Old text available at the end.
Goal for this Use Case:
To show that ONAP can be used to desgn and deploy the Service 2 in a CN and selected portion of a RAN currently providing Service 1 using NSI A, see Figure 1.
Precondition and assumptions
- The slice separation is based on PLMN-ID, using the symbolic PLMN-ID "NORMAL" for the existing CN "NSSI:Normal" and "PREMIUM" for the new CN "NSSI:Premium"
- It is known from ONAP R1 how to instantiate and deploy a minmal viable CN and the VLAN tagging to use for transport between RAN and that CN.
- The RAN consist of a set of distributed, physical eNodeB nodes, already integrated and in service as part of PLMN-ID "NORMAL" (the primary PLMN-ID).
- The RAN sharing for the part of the RAN that is to be shared (a sub-set of the cells) is unconstrained, only controlled by the QCI settings provided by the respective CN for each UE and radio bearer.
Post Conditions
- The "Service 2" is operational in all radio cells selected to support this service
- ONAP has knowledge about what resources (VNFs, PNFs and the services provided by these as relevant) are used by NSI A, NSI B or both.
- Some of the observability (PM/FM/events) as produced by DCAE for consumption within ONAP and above is available per NSI
Steps
- ...
-------- Temporary Text / Old 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.
...
The Network slice instance is operational. ONAP is actively collecting measurement information on the slice. All related Policies are deployed and active across the ONAP components.
...
...