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. |
Page History
| 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.
These services have very different requirements on latency, reliability, availability, mobility, and bandwidth. Deploying multiple separate networks to support these varying requirements is not practical. End to End vertical network slicing as defined by 3GPP provides specifications for efficient creation of multiple logical networks[PL1] sharing a common network infrastructure while meeting the specified service levels for each of the services. ONAP must support the complete lifecycle management of such network slicing.
Automated Configuration: Automated configuration of a slice during the instantiation, configuration, and activation phases, a newly created set of identifying parameters automatically configured
Automated reconfiguration. Automated reconfiguration happens during run-time e.g. an active slice can be reconfigured automatically because of a change in the service requirements or service conditions.
Here are some of the network elements participating in E2E Slicing:
- Distributed Radio Element
- Distributed BBU
- Centralized BBU and nrt-L2 function (CU-UP)
- Centralized Radio Control Unit (CU-CP)
- Layer 3 Transport Elements
- NG S/P Gateway
- NG PCRF
- Etc.
Goal
....