Goal

To satisfy request for allocation of a network slice instance with certain characteristics, by creation of new or using existing network slice instance; the request includes the network slice related requirements.

Actors and Roles

A network slice provisioniong management service consumer.

Telecom resources

Network slice instance
Network slice subnet instance
Transport network
A network slice provisioning management service provider.
A network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

N/A

Begins when

The network slice provisioning management service provider receives the request for allocation of the network slice instance with certain characteristics; the request contains network slice related requirements and the information indicating whether the requested NSI could be shared with other consumers.

Step 1 (M)

If the requested NSI can be shared and if an existing NSI can be used, the network slice provisioning management service provider decides to use the existing NSI.
Modification of the existing NSI may be needed to satisfy the network slice instance related requirements. Use case is completed go to “Step 8".
Otherwise, the network slice provisioning management service provider triggers to create a new NSI, for which the following steps 2 – 8 are needed.

Step 2 (M)

The network slice provisioning management service provider decides on the constituent NSSIs and the topology of the NSI to be created using the information from service profile [6]. For the constituent NSSIs, the network slice provisioning management service provider derives network slice subnet related requirements from the network slice related requirements. If reconfiguration of the transport network is needed, the network slice provisioning management service provider derives transport network related requirements (e.g. latency, bandwidth) from the network slice related requirements.

Step 3 (M)

For the required NSSI(s), the network slice provisioning management service provider sends network slice subnet related requirements to the network slice subnet provisioning management service provider to request allocation of the required NSSI(s).

Network slice subnet instance allocation use case

Step 4 (M)

The network slice provisioning management service provider receives the information of the allocated NSSI(s) (e.g. the management identifier of NSSI, service access point information of NSSI, external connection point information of NSSI) from NSSMF.

Step 5 (M)

The network slice provisioning management service provider, via the network slice subnet provisioning management service provider, sends the transport network related requirements (e.g. external connection point, latency and bandwidth) to the TN Manager. The TN manager reconfigures the TN accordingly and responds to the network slice provisioning management service provider via the network slice subnet provisioning management service provider.

Step 6 (M)

The network slice provisioning management service provider receives the response from TN Manager via the network slice subnet provisioning management service provider.

Step 7 (M)

The network slice provisioning management service provider associates the NSSI(s) with the corresponding NSI (e.g. allocation of the management identifier of NSI and mapping the management identifier of NSI with the received management Identifier of NSSI(s)) and triggers to establish the links between the service access points of the NSSI(s).

Step 8 (M)

The network slice provisioning management service provider notifies the network slice instance information of NSI (e.g., the management identifier of NSI).

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

An NSI is ready to satisfy the network slice related requirements.

Traceability

REQ-PRO_NSSI-FUN-1, REQ-PRO_NSI-FUN-3.

Goal

Create a new network slice subnet instance or use an existing network slice subnet instance to satisfy the network slice subnet related requirements; provide the provisioning service consumer with identity of the NFVO which the consumer can use for further access to the information of the involved VNFs, PNFs and NSs.

Actors and Roles

A network slice subnet provisioning management service consumer.

Telecom resources

Network Slice Subnet instance
Network Service instance
A network slice subnet provisioning management service provider.
The operator deployed NFVO to manage the lifecycle of VNFs and interconnection between the VNFs and PNFs in terms of the NS instances.

Assumptions

Network slice subnet instance may include network functions which are virtualized.

Pre-conditions

VNF Packages for virtualized network functions to be included in the network slice subnet instance have been already on-boarded.

Begins when

The network slice subnet provisioning management service consumer sends to the network slice subnet provisioning management service provider a request for an NSSI to be associated with the NSI; the request contains network slice subnet related requirements including the SliceProfile [6].

The network slice subnet provisioning management service provider receives request for a network slice subnet instance. The request contains network slice subnet related requirements. The request may also include query of the identity of the NFVO to be used.

Step 1 (M)

Based on the network slice subnet related requirements received, the network slice subnet provisioning management service provider decides to create a new NSSI or use an existing NSSI.

Step 2 (M)

If an existing network slice subnet instance is decided to be used, the network slice subnet provisioning management service provider may trigger to modify the existing network slice subnet instance to satisfy the network slice subnet related requirements. Go to “Step 8”.
Otherwise, the network slice subnet provisioning management service provider triggers to create a new NSSI, the following steps are needed.

Step 3 (O)

If the required NSSI contains constituent NSSI(s) managed by other network slice subnet provisioning management service provider (s), the first network slice subnet provisioning management service provider derives the requirements for the constituent NSSI(s) and sends those requirements to the corresponding network slice subnet provisioning management service provider (s) which manages the constituent NSSI(s).

The first network slice subnet provisioning management service provider receives the constituent NSSI information from the other network slice subnet provisioning management service provider (s) and associates the constituent NSSI(s) with the required NSSI.

Step 4 (M)

Based on the network slice subnet related requirements received and SliceProfile [6], the network slice subnet provisioning management service provider decides that to satisfy the NSSI requirements, the part of the network controlled by certain NFVO should be involved. The network slice subnet provisioning management service provider determines the NS related requirements (i.e. information about the target NSD and additional parameterization for the specific NS to instantiate, see clause 7.3.3 in ETSI GS NFV-IFA013 [3]).

Step 5 (M)

Based on the NS related requirements, the network slice subnet provisioning management service provider triggers corresponding NS instantiation request to NFVO via Os-Ma-nfvo interface as described in clause 6.4.3 in TS 28.525 [2], and the NFVO performs NS instantiation. (see note)

TS 28.525 [2] Clause 6.4.3 NS instance use cases

Step 6 (M)

The network slice subnet provisioning management service provider associates the NS instance with corresponding network slice subnet instance (e.g. allocation of the management identifier of NSSI and mapping with the corresponding identifiers).

Step 7 (M)

The network slice subnet provisioning management service provider is using the NF provisioning service to configure the NSSI constituents.

In case of RAN NSSI, the configuration contains RRM policy information for individual Radio cells. In the cells shared by multiple NSSIs such policy includes guidance for split of Radio resources between the NSSIs.

NF provisioning service

Step 8 (M)

The network slice subnet provisioning management service provider notifies the provisioning service consumer with the NSSI information (e.g. the management identifier of NSSI). The network slice provisioning management service provider associates the NSSI with the NSI.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

A NSSI is ready to satisfy the network slice subnet related requirements.

Traceability

REQ-PRO_NSSI-FUN-2, REQ-PRO_NSSI-FUN-3, REQ-PRO_NSSI-FUN-4, REQ-PRO_NSSI-FUN-5, REQ-PRO_NSSI-FUN-6, REQ-PRO_NSSI-FUN-14.

NOTE: According to the TS 28.525 [2], for the PNFs, NS instantiation includes only establishment of interconnection with other NFs.

Goal

To deallocate a network slice instance.

Actors and Roles

A network slice provisioning management service consumer.

Telecom resources

Network slice instance
Network slice subnet instances
A network slice provisioning management service provider.
A network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

N/A

Begins when

The network slice provisioning management service provider receives the request indicating that an existing NSI is no longer needed to support a particular service (identified by service profile Id). The NSI identification is included in the request.

Step 1 (M)

Based on the request, the network slice provisioning management service provider deletes the corresponding slice profile and checks if there are other services to be supported by the NSI. If there are none the network slice provisioning management service provider may decide to terminate the NSI; then proceed to Step 2.
Otherwise, the network slice provisioning management service provider may decide to trigger to modify the NSI or to do nothing.
The use case is completed; go to step 5.

NSI modification use case

Step 2 (M)

If the NSI to be terminated is active, the network slice provisioning management service provider de-activates the NSI. Then, the NSI to be terminated is inactive.

NSI de-activation use case

Step 3 (M)

The network slice provisioning management service provider identifies the network slice subnet instances used by the NSI, and for every such NSSI sends the request to the corresponding network slice subnet provisioning management service provider (s) indicating that the NSSI(s) are no longer needed for the NSI. The network slice subnet provisioning management service provider (s) may decide to terminate or modify the NSSI(s) based on the request and disassociates them with the NSI.

Step 4 (M)

The network slice provisioning management service provider receives the response from the network slice subnet provisioning management service provider (s) and terminates the NSI.

Step 5 (M)

The network slice provisioning management service provider notifies its consumer of the deallocation of the service profile.

Ends when

All the steps identified above are successfully completed or skipped per condition in the Step 1.

Exceptions

One of the steps identified above fails.

Post-conditions

The NSI has been deallocated.

Traceability

REQ-PRO_NSI-FUN-3

Goal

To deallocate a network slice subnet instance.

Actors and Roles

Network slice subnet provisioning management service consumer.

Telecom resources

Network slice subnet instance
Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

N/A

Begins when

The network slice subnet provisioning management service provider receives network slice subnet related request from its authorized consumer indicating that an existing NSSI is no longer needed to support a particular set of network slice subnet requirements identified by a slice profile id). The NSSI identification is included in the request.

Step 1 (M)

Based on the request, the network slice subnet provisioning management service provider decides whether the NSSI should be terminated.

If the decision is the NSSI should be terminated, go to the Step 2.

If the decision is that the NSSI should not be terminated (e.g., the NSSI is shared or the network slice subnet provisioning management service provider decides to keep the NSSI for later use), the network slice subnet provisioning management service provider disassociates the NSSI from its consumer and provides feedback to the authorized consumer, maybe with removing its consumer’s configuration or not. Go to Step 5.

Step 2 (M)

If the NSSI consists of constituent NSSIs that are not managed directly by the network slice subnet provisioning management service provider, the network slice subnet provisioning management service provider sends a request to other network slice subnet provisioning management service provider(s) indicating that the constituent NSSIs are no longer needed for the NSSI.

Step 3 (M)

If the NSSI is associated with NSI, the network slice subnet provisioning management service provider disassociates the NSI from the NSSI to be terminated, and the network slice subnet provisioning management service provider may trigger request to NFVO for terminating or updating (e.g. scaling-in) the NS instance. . (see note).

Step 4 (M)

If there exists a transport network segment used by the NSSI, the network slice subnet provisioning management service provider may indicate that the transport network segment is no longer needed to support the NSSI.

Step 5 (M)

The network slice subnet provisioning management service provider sends response to its consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The NSSI has been deallocated.

Traceability

REQ-PRO_NSSI-FUN-8, REQ-PRO_NSSI-FUN-11

NOTE: In case where the NS instance is not dedicated for the NSSI, the network slice subnet provisioning management service provider does not terminate the NS instance.

Goal

Enable the network slice subnet provisioning management service consumer to obtain network slice subnet instance information (e.g. Slice/Service type, network slice subnet capability information).

Actors and Roles

Network slice subnet provisioning management service consumer.

Telecom resources

Network slice subnet instance
Network slice subnet provisioning management service provider.

Assumptions

The network slice subnet provisioning management service consumer is authorized to obtain the network slice subnet instance information from the network slice subnet provisioning management service provider.

Pre-conditions

NSSI is created.

Begins when

The network slice subnet provisioning management service consumer wants to obtain the network slice subnet instance information.

Step 1 (M)

The network slice subnet provisioning management service consumer sends a request to the network slice subnet provisioning management service provider to obtain the network slice subnet instance information.

The indication on which information needs to be obtained may be included in the request.

Step 2 (M)

The network slice subnet provisioning management service provider processes this request.

Step 3 (M)

The network slice subnet provisioning management service provider sends the result of network slice subnet instance information to the network slice subnet provisioning management service consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The network slice subnet provisioning management service consumer has obtained the network slice subnet instance information.

Traceability

REQ-PRO_NSSI-FUN-7.

Goal

To check the feasibility of provisioning a network slice to determine whether the network slice requirements can be satisfied at a particular point in time (e.g., in terms of resources)

Actors and Roles

Network slice management service consumer. For example, CSP providing NSaaS plays the role of network slice management service consumer.

Telecom resources

Network slice management service provider.

Assumptions

Network slice management service consumer has decided to check the feasibility of provisioning a network slice based on, for example, internal decision or to facilitate an external service requests.

Pre-conditions

Network slice requirements have been derived or received by network slice management service consumer.

Begins when

Network slice management service provider receives the request to evaluate the feasibility of provisioning a network slice according to the network slice requirements at a particular point in time.

Step 1 (M)

Network slice management service provider identifies the network slice subnets according to the requirements.

Step 2 (M)

Network slice management service provider obtains the information necessary to evaluate the feasibility of provisioning a network slice by requesting the network slice subnet service provider(s) to evaluate the availability of resources under their contol.

Step 3 (M)

Network slice subnet management service provider(s) checks the feasibility of provisioning a slice subnet(s) by analysing network constituents to ensure that their capabilities, e.g., resources, management services, etc. are (or will be) adequate to provision network slice instance, satisfying all requirements without impacting existing services. For the purpose of checking the feasibility of provisioning a network slice subnet(s) of the network slice , network slice subnet management service provider(s) may obtain information from the network (e.g., current or predicted load level information from the NWDAF).

5.1.21 Network slice subnet feasibility check

Ends when

Feasibility check results have been provided to network slice management service consumer.

Exceptions

One of the mandatory steps fails.

Post-conditions

N/A

Traceability

REQ-PRO_NSSI-FUN-12, REQ-PRO_NSSI-FUN-13, REQ-PRO_NSI-FUN-8.

Goal

To activate an existing network slice instance which is inactive

Actors and Roles

Network slice provisioning management service consumer. For example, CSP providing NSaaS plays the role of Network slice management service consumer.

Telecom resources

Network slice instance
Network slice provisioning management service provider.

Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

An NSI has already been created and it is inactive.

Begins when

The network slice provisioning management service provider decides to activate an NSI based on the received network slice related request from its authorized consumer.

Step 1 (M)

The network slice provisioning management service provider checks whether NSSIs associated with the NSI are all active, if there is an inactive NSSI, the network slice provisioning management service provider requests the network slice subnet provisioning management service provider to activate the corresponding NSSI.

Network slice subnet instance activation use case

Step 2 (M)

The network slice provisioning management service provider receives response from the network slice subnet provisioning management service provider indicating that the NSSI is active.

Step 3 (M)

The network slice provisioning management service provider activates the NSI and sends response to the requesting consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

An NSI has been activated.

Traceability

REQ-PRO_NSI–FUN-4

Goal

To deactivate an existing network slice instance which is active.

Actors and Roles

Network slice provisioning management service consumer. For example, CSP providing NSaaS plays the role of network slice provisioning management service consumer.

Telecom resources

Network slice instance
Network slice provisioning management service provider.

Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

NSI has already been created and it is active.

Begins when

The network slice provisioning management service provider decides to deactivate an NSI based on the received network slice related request from its authorized consumer.

Step 1 (M)

The network slice provisioning management service provider stops the NSI serving its subscribers.

Step 2 (M)

The network slice provisioning management service provider checks whether NSSIs associated with the NSI are all inactive. If there is an active NSSI, the network slice provisioning management service provider requests the network slice subnet provisioning management service provider to deactivate the corresponding NSSI.
The network slice subnet provisioning management service provider receives the request and decides if the NSSI will be disassociated and deactivated.

Network slice subnet instance deactivation use case

Step 3 (M)

The network slice provisioning management service provider receives response from the network slice subnet provisioning management service provider that the NSSI deactivation request has been processed.

Step 4 (M)

The network slice provisioning management service provider deactivates the NSI and sends response to its authorized consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

An NSI has been deactivated.

Traceability

REQ-PRO_NSI–FUN-5

Goal

To modify an existing network slice instance

Actors and Roles

Network slice provisioning management service consumer. See NOTE.

Telecom resources

Network slice instance
Network slice provisioning management service provider.

Assumptions

N/A

Pre-conditions

N/A.

Begins when

The network slice provisioning management service provider receives request from its authorized customer with new set of network slice related requirements and decides to modify an existing NSI.

Step 1 (M)

The network slice provisioning management service provider identifies the NSSI(s) associated with the NSI to be modified and generates network slice subnet related requirements for the NSSI(s).

Step 2 (M)

The network slice provisioning management service provider sends requests to the network slice subnet provisioning management service provider with new sets of network slice subnet related requirements.

The network slice provisioning management service provider receives request and decides whether the NSSI needs to be modified.

Network slice subnet instance modification use case

Step 3 (M)

The network slice provisioning management service provider receives the response from the network slice subnet provisioning management service provider. If the NSSI modification request cannot be satisfied by the network slice subnet provisioning management service provider, the network slice provisioning management service provider may re-generate the network slice subnet related requirements for the NSSI and go to step 2, or the network slice provisioning management service provider may decide the modification request cannot be satisfied.

Step 4 (M)

The network slice provisioning management service provider sends response to its authorized consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The NSI is modified.

Traceability

REQ-PRO_NSI-FUN-6

NOTE: Examples of roles and actors for this use case can be found in TS 28.530 [4].

Goal

To activate an existing network slice subnet instance which is inactive.

Actors and Roles

Network slice subnet provisioning management service consumer.

Telecom resources

Network slice subnet instance
Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

An NSSI has already been created and it is inactive.

Begins when

The network slice subnet provisioning management service provider decides to activate an NSSI based on the received network slice subnet related request from its authorized consumer.

Step 1 (M)

The network slice subnet provisioning management service provider identifies inactive constituents (e.g. NSSI, NF) of the NSSI and decides to activate those constituents.

Step 2 (M)

If the constituent of NSSI is managed directly by the the network slice subnet provisioning management service provider, the network slice subnet provisioning management service provider activates the NSSI constituent directly.

Step 3 (M)

If an NSSI constituent is managed by other network slice subnet provisioning management service provider, the network slice subnet provisioning management service provider requests other network slice subnet provisioning management service provider to activate the constituent NSSI.

Step 4 (M)

If an NSSI constituent is an NF managed by NF related provisioning management service provider, the network slice subnet provisioning management service provider request the NF related provisioning management service provider to activate the NF (e.g., activate the NF in sleep mode, turn on the ports).

Step 5 (M)

The network slice subnet provisioning management service provider receives response indicating that NSSI constituents are all activated.

Step 6 (M)

The network slice subnet provisioning management service provider activates the network slice subnet instance and sends response to its authorized consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

An NSSI has been activated.

Traceability

REQ-PRO_NSSI–FUN-9

Goal

To deactivate an existing network slice subnet instance which is active.

Actors and Roles

Network slice subnet provisioning management service consumer.

Telecom resources

Network slice subnet instance.
Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

An NSSI has already been created and is active.

Begins when

The network slice subnet provisioning management service provider decides to deactivate an NSSI based on the received network slice subnet related request from its authorized customer.

Step 1 (M)

The network slice subnet provisioning management service provider identifies the NSSI constituents that need to be deactivated.

Step 2 (M)

If the constituent of NSSI is managed directly by the network slice subnet provisioning management service provider, the network slice subnet provisioning management service provider deactivates the NSSI constituent directly.

Step 3 (M)

If an NSSI constituent is managed by other network slice subnet provisioning management service provider, the network slice subnet provisioning management service provider requests other network slice subnet provisioning management service provider to deactivate the constituent NSSI.

Step 4 (M)

If an NSSI constituent is managed by the NF related provisioning management service provider, the network slice subnet provisioning management service provider requests the NF related provisioning management service provider to either deactivate the NF (if it is dedicated for this NSSI and not being used by any other NSSI) or to modify the NF (if it is shared by other NSSI).

Step 5 (M)

The network slice subnet provisioning management service provider receives response indicating that corresponding NSSI constituents are deactivated or not deactivated (e.g., shared constituents cannot be deactivated).

Step 6 (M)

The network slice subnet provisioning management service provider deactivates the network slice subnet instance and send response to its authorized consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

A network slice subnet instance has been deactivated.

Traceability

REQ-PRO_NSSI–FUN-10

Goal

To modify an existing network slice subnet instance

Actors and Roles

Network slice subnet provisioning management service consumer.

Telecom resources

Network slice subnet instance
Network slice subnet provisioning management service provider.

Assumptions

N/A

Pre-conditions

N/A

Begins when

The network slice subnet provisioning management service provider receives request from its authorized consumer with new sets of network slice subnet related requirements and decides to modify an existing NSSI.

Step 1 (M)

The network slice subnet provisioning management service provider identifies the NSSI constituents as well as the transport network (TN) part within the NSSI that needs to be modified, and generates new sets of requirements for the NSSI constituents and transport network if needed.

Step 2 (M)

The network slice subnet provisioning management service provider checks whether the requirements for the identified NSSI constituents managed by itself could be satisfied, and then triggers the modification of the corresponding NSSI constituents if needed.

Step 3 (M)

If the NSSI consists of constituent NSSI managed by other network slice subnet provisioning management service provider, and the constituent NSSI is identified to be modified, the network slice subnet provisioning management service provider sends modification request to other network slice subnet provisioning management service provider which manages the constituent NSSI with new sets of constituent NSSI requirements.

Network slice subnet instance modification use case

Step 4 (M)

If the NS instance associated with the NSSI needs to be modified, the network slice subnet provisioning management service provider derives the new sets of NS related requirements and triggers corresponding NS instance request to NFVO with Os-Ma-nfvo interface as described in clause 6.4.3 in TS 28.525 [2].

TS 28.525 [2] Clause 6.4.3 NS instance use cases

Step 5 (M)

If the related TN part of the NSSI is identified to be modified, the network slice subnet provisioning management service provider derives new sets of requirements for the TN part and coordinates with the corresponding TN management system.

Step 6 (M)

The network slice subnet provisioning NetworkSliceSubnet management service provider generates the modification result based on the received response and send response to its authorized consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The NSSI is modified.

Traceability

REQ-PRO_NSSI-FUN-11

Goal

To provide service for slice-specific (re)configuration of NSSI.

Actors and Roles

Network slice subnet provisioning management service consumer (e.g., the operator)

Telecom resources

Network slice subnet provisioning management service provider

Network slice subnet instance

NF(s)

Assumptions

Authorized network slice subnet provisioning management service consumer provide slice operation information (see 4.2) for (re-)configuring NSSI constituents.

Pre-conditions

NSSI exists.

Begins when

The network slice subnet provisioning management service consumer wants to (re-)configure the constituents of a NSSI.

Step 1 (M)

The network slice subnet provisioning management service consumer sends requests to the network slice subnet provisioning management service provider with slice operation information for (re-)configuring a network slice subnet.

Step 2 (M)

The network slice subnet provisioning management service provider (derives and) decomposes the received slice operation information, and then makes them as separate CM requests for each constituent if necessary and applicable. These (decomposed) requests may be delegated to other provisioning management service providers (e.g., other network slice subnet provisioning service providers, NF provisioning management service providers) with corresponding slice operation information.

These requests may contain configuration for specific NFs such as 1) Configuration of dedicated NFs (e.g., configure the SMF with the information of new instantiated UPFs, see 5.3.2, 5.3.3 in [6]) and 2) Configuration of shared NFs (see 4.2 so that this information can be accessed by other constituents of the NSS (e.g., NSSF, AMF, SMF).

Step 3 (M)

The network slice subnet provisioning management service provider sends the processing result to the network slice subnet provisioning management service consumer (might be based on applicable processing results from other CM service providers).

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The required (re)configuration is configured at the corresponding constituent(s).

Traceability

REQ-PRO_NSSI-FUN-16

Goal

Enable network slice management service consumer to obtain network slice management data (e.g. PM data, FM data).

Actors and Roles

Network slice management service consumer.

Network slice management service provider..

Telecom resources

Network slice instance

Assumptions

The network slice management service consumer is authorized to obtain the network slice management data from the network slice management service provider.

Pre-conditions

NSI is created.

Begins when

The network slice management service consumer wants to obtain the network slice management data.

Step 1 (M)

The network slice management service consumer sends a request to the network slice management service provider to obtain the network slice management data.

Step 2 (M)

The network slice management service provider provides the network slice management service consumer with the network slice management data .

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The network slice management service consumer obtained the network slice management data.

Traceability

REQ-PRO_NSI-FUN-7

Goal

Enable authorized network slice management service consumer to obtain certain management capability to manage the network slice instance (e.g., provisioning) through the exposure interface.

Actors and Roles

Network slice management service consumer. For example, CSP providing NSaaS plays the role of network slice management service consumer.

Telecom resources

Network slice instance

Network slice management service provider. For example, NSMF plays the role of network slice management service provider.

Assumptions

The network slice management service consumer is authorized to obtain the allowed management capability from the network slice management service provider according to the pre-defined agreements.

Pre-conditions

Level of management exposure has been agreed upon between the network slice management service provider and the network slice management service consumer.

Begins when

The network slice management service consumer wants to obtain the network slice management capability.

Step 1 (M)

The network slice management service consumer sends a request to the network slice management service provider to obtain the network slice management capability.

The information indicating which specific management capability needs to be obtained may be included in the request.

Step 2 (M)

The network slice management service provider provides the required management capability to the network slice management service consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The network slice management service consumer obtained the allowed network slice management capability.

Traceability

REQ-PRO_NSI-FUN-1, REQ-PRO_NSI-FUN-3, REQ-PRO_NSI-FUN-6

Goal

Enable authorized NSS management service consumer to obtain network slice subnet management capability (e.g. obtaining measurement, updating resource allocations).

Actors and Roles

NSS management service consumer (e.g., the operator)

Telecom resources

NSS management service provider

Network slice subnet instance

NF(s)

Assumptions

The NSS management service consumer is authorized to obtain the allowed management capability from NSS management service provider.

Pre-conditions

NSSI is created.

Begins when

The NSS management service consumer wants to obtain the network slice subnet management capability.

Step 1 (M)

The NSS management service consumer sends a request to NSS management service provider to obtain the network slice subnet instance management capability.

The information indicating which specific management capability need to be obtained may be included in the request.

Step 2 (M)

The NSS management service provider processes this request.

Step 3 (M)

The NSS management service provider provides the required exposure interfaces to the NSS management service consumer.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The NSS management service consumer obtained the allowed network slice subnet instance management capability.

Traceability

REQ-PRO_NSSI-FUN-15

Goal

To enable the authorized consumer to request creation of an instance of 3GPP NF.

Actors and Roles

An authorized consumer of the NF creation provisioning management service.

Telecom resources

VNF package(s) of the virtualized part of 3GPP NF;

ETSI NFV MANO system;

NF provisioning management service producer.

Assumptions

N/A

Pre-conditions

The VNF package(s) of the virtualized part of 3GPP NF have been on-boarded to ETSI NFV MANO system.

Begins when

The authorized consumer needs to create a new instance of 3GPP NF.

Step 1 (M)

The authorized consumer requests the NF provisioning management service producer to create a new instance of 3GPP NF.

Step 2 (M)

The NF provisioning management service producer checks the subject 3GPP NF contains virtualized part and/or non-virtualized part. If it contains virtualized part, then the NF instantiation service producer performs the step 3 and 4 to instantiate the virtualized part of the subject 3GPP NF.

How to instantiate the non-virtualized part of the subject 3GPP NF is out of scope of present document.

Step 3 (M)

The NF provisioning management service producer interacts, or requests another NF provisioning management service producer to interact, with ETSI NFV MANO system to instantiate the VNF(s) that are realizing the virtualized part of subject 3GPP NF.

Step 4 (M)

If all of the contained parts (i.e., virtualized part and non-virtualized part if any) of the 3GPP NF have been successfully instantiated, the NF provisioning management service producer informs the consumer(s) (who have subscribed to the notifications for NF creation) that the instance of 3GPP NF has been created, and creates the MOI(s) for the subject 3GPP NF.

Step 5 (M)

Created MOI(s) may be maintained by a Management Function which has the NF provisioning management service or the 3GPP NF. When the MOI(s) is maintained by the 3GPP NF, the NF provisioning management service producer sends a request of creating the MOI(s) to the corresponding NF provisioning management service producers in the created NF.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The instance of 3GPP NF has been created, and the MOI(s) of the 3GPP NF have been created.

Traceability

REQ-PRO_NF-FUN-1, REQ-PRO_NF-FUN-2, REQ-PRO_NF-FUN-7

Goal

To enable the authorized consumer to request configuration of a 3GPP NF instance.

Actors and Roles

An authorized consumer of the NF provisioning management service.

Telecom resources

ETSI NFV MANO system;

NF provisioning management service producer.

Assumptions

N/A

Pre-conditions

The NF to be configured has been instantiated;

The MOI of the NF has been created.

Begins when

The authorized consumer needs to configure a 3GPP NF instance.

Step 1 (M)

The consumer requests the NF provisioning management service producer to modify the attribute(s) of the MOI of the 3GPP NF instance.

Step 2 (O)

If the 3GPP NF contains virtualized part and the corresponding VNF instance(s) need to be updated, the NF provisioning management service producer interacts, or requests another NF provisioning management service producer to interact, with ETSI NFV MANO system to update the corresponding VNF instance(s).

Step 3 (M)

The NF provisioning management service producer configures the 3GPP NF instance, per the MOI attribute modification request received from the consumer.

Step 4 (M)

The NF provisioning management service producer modifies the attributes of the MOI and informs the consumer that the 3GPP NF instance has been configured successfully.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The 3GPP NF instance has been configured.

Traceability

REQ-PRO_NF-FUN-4, REQ-PRO_NF-FUN-5, REQ-PRO_NF-FUN-6, REQ-PRO_NF-FUN-3

Goal

To enable the authorized consumer to request creation of a 3GPP sub-network.

Actors and Roles

An authorized consumer of the sub-network provisioning management service.

Telecom resources

VNF package(s) of the virtualized part of 3GPP NF(s);

NSD(s) of the NS(s);

ETSI NFV MANO system;

Network provisioning service producer;

NF provisioning service producer.

Assumptions

N/A

Pre-conditions

The non-virtualized part of the NFs (including completely non-virtualized NFs) constituting the 3GPP sub-network have been deployed;

The VNF package(s) of the virtualized part of 3GPP NF(s) have been on-boarded to ETSI NFV MANO system;

The NSD(s) of the NS realizing the 3GPP sub-network have been on-boarded to ETSI NFV MANO system.

Begins when

The authorized consumer needs to create a 3GPP sub-network.

Step 1 (M)

The authorized consumer requests the sub-network provisioning management service producer to create a 3GPP sub-network. The request needs to indicate the network capacity (e.g., the number of instances of each kind of NFs, and the capacity of each NF instance, for example, number of flows with certain QoS attributes to be supported), network topology information (e.g., the connections between NF instances), and the network QoS requirements (e.g., bandwidth and latency requirements of the interface between two NF instances).

Step 2 (M)

The network provisioning management service producer interacts, or requests another network provisioning management service producer to interact, with ETSI NFV MANO system to instantiate the NS(s) realizing the sub-network.

Step 3 (M)

ETSI NFV MANO system informs the NF provisioning management service producer about the instantiation of the NSs and the new VNFs.

Step 4 (M)

The NF provisioning management service producer creates the MOI(s) of the 3GPP NFs that are realized by the newly instantiated VNF(s); there may be MOI(s) that specify the topology of the instantiated NSs.

Step 5 (M)

The sub-network provisioning management service producer is using the NF provisioning management service to configure the 3GPP NF instance(s) that are constituting the subject 3GPP sub-network.

NF configuration service

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The 3GPP sub-network has been created.

Traceability

REQ-PRO_NW-FUN-1, REQ-PRO_NW-FUN-2

Goal

To enable the authorized consumer to request configuration of a 3GPP sub-network.

Actors and Roles

An authorized consumer of the network provisioning management service.

Telecom resources

3GPP network;

3GPP NFs;

ETSI NFG MANO system;

Network provisioning management service producer.

Assumptions

N/A

Pre-conditions

The 3GPP sub-network has been created;

The MOI(s) related to the sub-network has been created.

Begins when

The authorized consumer needs to configure a 3GPP sub-network.

Step 1 (M)

The authorized consumer requests to configure a 3GPP sub-network.

Step 2 (M)

The consumer requests the network provisioning management management service producer to modify the attribute of the MOI(s) related to the 3GPP sub-network.

Step 3 (O)

If the 3GPP network is realized by NS(s) (ETSI ISG NFV concept), the network provisioning management service producer requests (directly or indirectly via another) ETSI NFV MANO system to update the NS(s) realizing the 3GPP sub-network.

Step 4 (O)

If there are new VNFs instantiated by the NS update, ETSI NFV MANO system informs the NF provisioning management service producer about the instantiation of VNFs.

Step 5 (O)

The NF provisioning management service producer creates the MOI(s) of the 3GPP NFs that are realized by the newly instantiated VNF(s).

Step 6 (M)

The network provisioning management service producer consumes the NF provisioning management service to configure the impacted 3GPP NF instance(s).

NF configuration service

Step 7 (M)

The network provisioning management service producer configures the 3GPP sub-network, per the MOI attribute modification request received from the consumer.

Step 8 (M)

The NF provisioning management service producer modifies the attributes of the MOI(s) of the 3GPP network and informs the consumer that the 3GPP sub-network has been configured successfully.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The 3GPP network has been configured.

Traceability

REQ-PRO_NW-FUN-3, REQ-PRO_NW-FUN-4

Goal

To check the feasibility of provisioning a network slice subnet to determine whether network slice subnet requirements can be satisfied at a particular point of time (e.g., in terms of resources)

Actors and Roles

Network slice subnet management service consumer. For example, when a network slice subnet instance is to be provided as a constituent of a network slice instance.

Telecom resources

Network slice subnet instance
Network slice management service provider. For example, a management function that plays the role of network slice management service provider.

Assumptions

Network slice subnet management service consumer has decided to check the feasibility of provisioning a network slice subnet based on, for example, internal decision or to facilitate an external service requests.

Pre-conditions

Network slice subnet requirements have been derived or received by network slice subnet management service consumer.

Begins when

Network slice subnet management service provider receives the request to evaluate the feasibility of provisioning a network slice subnet according to the network slice requirements at a particular point in time.

Step 1 (M)

Network slice subnet management service provider identifies the network slice subnets constituents according to the requirements, e.g., network services to be requested from MANO.

Step 2 (O)

For the purpose of checking the feasibility of provisioning a network slice subnet(s) of the network slice instance, network slice subnet management service provider(s) may obtain information from the network (e.g., current or predicted load level information, current or predicted resource usage information from management data analytics services).

Step 3 (M)

Network slice subnet management service provider sends enquiries with reservation requests to other management providers (e.g., MANO) to determine availability of network constituents, e.g., network services, network functions. If some of the responses are negative, network slice subnet management service provider may send enquiries to different management providers.

Ends when

Feasibility check results have been provided to network slice subnet management service consumer.

Exceptions

One of the mandatory steps fails.

Post-conditions

N/A

Traceability

Goal

To calculate capacity of network slice instances and network slice subnet instances.

Actors and Roles

Network slice management service consumer.

Telecom resources

Network slice instance

Network slice subnet instance
Network slice management service provider.

Assumptions

The network slice management service consumer has decided to perform network slice resource capacity optimization process.

Pre-conditions

Network slice resource capacity optimization objectives are set by the network slice management service consumer.

Begins when

The network slice management service consumer requests resource capacity planning of the NSIs and/or NSSIs when the pre-set resource optimization objectives need to be satisfied.

Step 1 (M)

The network slice management service provider obtains information needed for the optimization process such as slice provisioning requirements, existing active or non-active NSI and/or NSSI resource information, and performance measurement data by requesting feasibility check operation.

Step 2 (M)

The network slice management service provider performs resource optimization process based on the information obtained in Step 1. The goal of the process is to find an optimal capacity availability against the target objective

Step 3 (M)

The network slice management service provider proceeds with network slice (NSI and/or NSSI) provisioning or modification processes until it meets the resource capacity optimization objective.

Network slice instance creation or modification/network slice subnet instance creation or modification use cases

Step 4 (M)

The network slice management service provider updates capacity availability information after provisioning or modification processes.

Ends when

The capacity resource planning ends when it meets the optimization objective.

Exceptions

One of the mandatory steps fails.

Post-conditions

Capacity planning policy for either provisioning or modification is generated.

Traceability

REQ-PRO_NSSI-FUN-3, REQ-PRO_NSI-FUN-9

Goal

To assign priority on existing network slice subnet instance(s).

Actors and Roles

Network slice subnet provisioning management service consumer.

Network slice subnet provisioning management service provider

Telecom resources

Network slice subnet instance (i.e. NSSI)
Network slice subnet provisioning management service provider

Assumptions

Network slice subnet instance is deployed to support a communication service with priority, set by the operator.

Pre-conditions

This use case is based on the condition that operator requires a priority assigned to network slice subnet.

Begins when

The NSSI(s) should have been assigned with priority set by the operator.

Step 1 (M)

The network slice provisioning management service provider identifies the NSSI(s) that needs to be associated with the priority, requested by authorized network slice subnet provisioning management service consumer.

The network slice provisioning management service provider assigns priority to the identified NSSI(s)

Network slice subnet instance modification use case

Step 2 (M)

The network slice provisioning management service provider sends response to its authorized consumer about assigned priority on identified NSSI(s).

Ends when

All the steps identified above are successfully completed. Network slice subnet priority was assigned by the network slice subnet management service provider.

Exceptions

One of the steps identified above fails.

Post-conditions

Traceability

REQ-PRO_NSI-FUN-x

Goal

To enable the authorized consumer to request creation of a 3GPP sub-network, management interactions with NFV MANO is needed. This management interaction will assign priority on NFV NS(s).

Actors and Roles

An authorized consumer of 3GPP sub-network creation.

Telecom resources

VNF package(s) of the virtualized part of 3GPP NF(s);

NSD(s) of the NS(s);

ETSI NFV MANO system;

Assumptions

N/A

Pre-conditions

The ETSI NFV VNF package(s) of the virtualized part of 3GPP NF(s) have been on-boarded to ETSI NFV MANO system;

The ETSI NFV NSD(s) used to instantiate NS(s) for realizing the 3GPP sub-network have been on-boarded to ETSI NFV MANO system.

Begins when

The authorized consumer needs to create a 3GPP sub-network. This creation operation also needs to assign priority on 3GPP sub-network and on related ETSI NFV NS(s).

Step 1 (M)

The authorized consumer requests the 3GPP sub-network creation service producer to create a 3GPP sub-network.

Step 2 (M)

The sub-network creation service producer interacts, or requests another sub-network creation service producer to interact, with ETSI NFV MANO system to instantiate the NS(s) realizing the 3GPP sub-network.

Step 3 (M)

ETSI NFV MANO is informed about NS priority.

Ends when

All the steps identified above are successfully completed.

Exceptions

One of the steps identified above fails.

Post-conditions

The 3GPP sub-network has been created. Network service priority is identified by NFVO to support the 3GPP sub-network.

Traceability

REQ-PRO_NW-FUN-1, REQ-PRO_NW-FUN-2