4.6 Slice profile and service profile concepts

28.5303GPPConcepts, use cases and requirementsManagement and orchestrationRelease 17TS

4.6.1 Slice profile

The network slice subnet has an associated set of requirements (e.g. those derived from service level requirements) that are applicable to the network slice subnet constituents, such set is called slice profile. TN requirements (e.g. set of QoS attributes for the links interconnecting network slice subnet constituent network functions) is an example of requirements that may be included in the slice profile. The slice profile may be common (applicable to all network slice subnet constituents, regardless of their types) or specific (applicable to only AN network function or only to CN network function network slice subnet constituents).

4.6.2 Service profile

Depending on industry requirements and operator’s requirements, different service profiles may be used to represent SLS associated with network slices.

The following are examples for service profiles:

– A service profile is used to capture a set of requirements for the new network slice such as (eMBB, MIoT, URLLC).

– A service profile is used to capture a set of specific industry requirements for creation of network slice such as V2X, smart grid, Remote Healthcare.