...
Use Case Blueprint | Key Updates | Benefits | ||
5G | 5G use case covers a few independent use cases which improves the ONAP capabilities on PNF management. Key use cases which are supported in ONAP Frankfurt release:
| |||
E2E Network Slicing (a new E2E use case for Frankfurt, we'd also like to apply to publish a separate Blueprint White Paper for E2E Network Slicing use case, same as the community did for other use cases in every release) | 5G Network Slicing is one of the key features of 5G. The essence of Network Slicing is in sharing network resources (PNFs, VNFs, CNFs) while satisfying | E2E Network Slicing (a new E2E use case for Frankfurt, we'd also like to apply to publish a separate Blueprint White Paper for E2E Network Slicing use case, same as the community did for other use cases in every release) | 5G Network Slicing is one of the key features of 5G. The essence of Network Slicing is in sharing network resources (PNFs, VNFs, CNFs) while satisfying widely varying and sometimes seemingly contradictory requirements to different customers in an optimal manner. Same network is expected to provide different Quality of Experience to different consumers, use case categories and industry verticals including factory automation, connected home, autonomous vehicles, smart cities, remote healthcare, in-stadium experience and rural broadband. An End-to-End Network Slice consists of RAN, Transport and Core network slice sub-nets. This Use Case intends to demonstrate the modeling, orchestration and assurance of a simple network slice (e.g. eMBB). While 3GPP standards are evolving and 5G RAN and core are being realized, this Use Case will start with realizing an E2E Network Slice with a simple example of a 5G RAN, Core and Transport Network Slice sub-nets. It will also align with relevant standard bodies (e.g., 3GPP, ETSI, TM Forum) as well as other open initiatives such as O-RAN where relevant, with respect to both interfaces as well as the functional aspects. Key features in Frankfurt:
Key capabilities added for ONAP Frankfurt release:
This use case is a multi release effort and we will continue to provide more enhancements and features based on what we've implemented in Frankfurt in the subsequent releases. |
|
PNF software upgrade without schema update | PNF software updates are routine for network upgrades to support new features, improve efficiency or increase capacity on the field, and to eliminate bugs. This use case positions ONAP as a vantage point in orchestrating and managing PNF software upgrades inline with the business and service objectives. Deployment and orchestration of new network services over both VNFs and PNFs in a model and software driven way simplifies the network management. As 5G networks will host a large number of PNFs from multiple vendors, streamlining service upgrades that involve PNF software changes through ONAP will reduce the OPEX substantially. The following upgrade scenarios are supported in ONAP Frankfurt release: | |||
PNF software version onboarding is a key feature to onboard the vendor provide PNF software version into the ONAP internal PNF descriptor. This PNF software version information will be used by ONAP Run Time components for the purpose of PNF life cycle management. | ||||
CCVPN | Adding two extension functions / sub use cases for Frankfurt.
|
| ||
BBS | In Frankfurt, the BBS team focused mainly on bug fixes, improving the BBS use case multi-vendor support and documentation. This is based on feedback received from many showcases during the previous ONAP releases. The BBS use case continues providing inputs to standardization bodies like BBF (Broadband Forum) in the context of the CloudCO framework interfaces definition. | 1. Establishment of a subscriber's HSIA (High Speed Internet Access) service from an ONT to the Internet drain 2. Support the change of location for ONT devices (Nomadic ONT devices) 2.1 PNF (Re-)Registration for an ONT | ||
O-RAN Harmonization | See 5G | |||
Tactical Use Case Blueprint | ||||
PNF support | See 5G | |||
Change Management |
| |||
Control Loop | See above | |||
K8s cloud region | Significant progress in supporting
Integration with Macro instantiation flow and with CDS for vFW Use Case
| |||
Scaling |
|
...