Comment (Vladimir Y.) The whole text is about E2E slicing, not RAN slicing. See e.g. the diagram
This page contains work in progress! |
|---|
Questions and comments are inserted in the text as needed, prefix them with "Question:" or "Comment:". Text below the line "----temporary text ----" is a placeholder for text that may or may not be used later on. |
...
| Rev | Author | Comment |
|---|---|---|
| 9/7/17 | Peter L | Copied text from the v4 document, must check the v5 document for additional parts |
Introduction
Each Service Provider (SP) needs to support a rich set of advanced 5G wireless services, such as enhanced Mobile Broad Band (eMBB), massive Internet of Things (mIoT), and Ultra-Reliable, Low-latency Communications (URLLC ), for mission critical communications.
...
- 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).
Service and Slice concepts according to 3GPP TR 28.801v1.3.0
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 service instance is realized by one or more network slice instances (NSINSIs).
Comment (Vladimir Y.) The definition of NSSI in 28.801 is different: includes recurrence.
A An NSI may be composed of network slice subnet instance s (NSSI), in turn consisting of a set of Physical Network Functions and/or Virtualized Network Functions) constituent may include NF(s) and other NSSI(s).
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Goal
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?
...
- <<<<<< 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
The Network slice instance is operational. ONAP is actively collecting measurement information for the slice. All related Policies are deployed and active across the ONAP components.
-------- Temporary Text ----------
...