4.4 Managed network slice concepts

28.5303GPPConcepts, use cases and requirementsManagement and orchestrationRelease 17TS

4.4.1 General

From a management point of view a network slice is complete in the sense that it includes all the network function instances, with their supporting resources, to provide service for certain business purpose (e.g. to support a certain set of communication services, provide PNI-NPNs, etc. in NSaaS model) or operational efficiencies purpose (e.g. to optimize operator internal O&M procedures in network slice as NOP internals model). In other words, the network slice is complete because it completely satisfies the associated SLS.

The following concepts are related to network slicing management:

a. Services which are supported by network slices (services whose service level requirements are satisfied by the SLS associated with the network slices).

b. Network slice subnet instances and networks composed of PNF, VNF or both and offered as network slices.

c. Network function (PNFs, VNFs) grouped into network slice subnets.

d. Resources which support the network (e.g. virtualized resource, non-virtualized resource)

The management aspects of the network slice are represented by management of the CN part, and AN part which are directly managed by the 3GPP management system, and management of non-3GPP part which is not directly managed by the 3GPP management system. The non-3GPP part includes TN parts. The 3GPP management system provides the network slice requirements to the corresponding management systems of those non-3GPP parts, e.g. the TN part supports connectivity within and between CN and AN parts. For the TN part, the 3GPP management system provides the TN topology requirements and individual TN links’ QoS attributes requirements to the TN management system.

The 3GPP management system maintains the network topology and the related QOS requirements.

Figure 4.4.1.1: Example of a network slice