Page History

...

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).

A service instance is realized by one or more network slice instances (NSI).

An NSI may be composed of network slice subnet instances (NSSI), in turn consisting of a set of Physical Network Functions and/or Virtualized Network Functions.

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 temlate 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?

Use Case 1: Design slice template

...