Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 28.531  Word version:  17.1.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.1.8…   5.1.16…   5.2…   6…   7…   8…

 

5.1.8  Network slice instance deactivationWord‑p. 19

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo deactivate an existing network slice instance which is active.
Actors and RolesNetwork slice provisioning management service consumer. For example, CSP providing NSaaS plays the role of network slice provisioning management service consumer.
Telecom resourcesNetwork slice instance
Network slice provisioning management service provider.
Network slice subnet provisioning management service provider.
AssumptionsN/A
Pre-conditionsNSI has already been created and it is active.
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsAn NSI has been deactivated.
TraceabilityREQ-PRO_NSI-FUN-5
Up

5.1.9  Network slice instance modificationWord‑p. 20

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo modify an existing network slice instance
Actors and RolesNetwork slice provisioning management service consumer. For example, CSP providing NSaaS plays the role of network slice provisioning management service consumer.
Telecom resourcesNetwork slice instance
Network slice provisioning management service provider.
AssumptionsN/A
Pre-conditionsN/A
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsThe NSI is modified.
TraceabilityREQ-PRO_NSI-FUN-6
Up

5.1.10  Network slice subnet instance activationWord‑p. 21

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo activate an existing network slice subnet instance which is inactive.
Actors and RolesNetwork slice subnet provisioning management service consumer.
Telecom resourcesNetwork slice subnet instance
Network slice subnet provisioning management service provider.
AssumptionsN/A
Pre-conditionsAn NSSI has already been created and it is inactive.
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsAn NSSI has been activated.
TraceabilityREQ-PRO_NSSI-FUN-9
Up

5.1.11  Network slice subnet instance deactivationWord‑p. 22

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo deactivate an existing network slice subnet instance which is active.
Actors and RolesNetwork slice subnet provisioning management service consumer.
Telecom resourcesNetwork slice subnet instance. Network slice subnet provisioning management service provider.
AssumptionsN/A
Pre-conditionsAn NSSI has already been created and is active.
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsA network slice subnet instance has been deactivated.
TraceabilityREQ-PRO_NSSI-FUN-10
Up

5.1.12  Network slice subnet instance modificationWord‑p. 23

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo modify an existing network slice subnet instance
Actors and RolesNetwork slice subnet provisioning NetworkSliceSubnet management service consumer. For example, NSMF or NSSMF plays the role of NetworkSliceSubnet management service consumer.
Telecom resourcesNetwork slice subnet instance
Network SliceSubnet slice subnet provisioning management service provider. For example, NSSMF plays the role of NetworkSliceSubnetmanagement service provider.
AssumptionsN/A
Pre-conditionsN/A
Begins whenThe network slice subnet provisioning The NetworkSliceSubnet 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 NetworkSliceSubnet 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 NetworkSliceSubnet 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 NetworkSliceSubnet management service provider, and the constituent NSSI is identified to be modified, the network slice subnet provisioning NetworkSliceSubnet management service provider sends modification request to other network slice subnet provisioning NetworkSliceSubnet 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 NetworkSliceSubnet 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.TS 28.525, 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 NetworkSliceSubnet 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsThe NSSI is modified.
TraceabilityREQ-PRO_NSSI-FUN-11
Up

5.1.13  Network slice subnet configurationWord‑p. 24

Use case stage Evolution/Specification <<Uses>> Related use
GoalTo provide service for slice-specific (re)configuration of NSSI.
Actors and RolesNSS Network slice subnet provisioning management service consumer (e.g., the operator or NSMF)
Telecom resourcesNetwork slice subnet provisioning NSS management service provider (e.g., NSSMF)
Network slice subnet instance
NF(s)
AssumptionsAuthorized network slice subnet provisioning NSS management service consumer provide slice operation information (see clause 4.2) for (re-)configuring NSSI constituents.
Pre-conditionsNSSI exists.
Begins whenThe network slice subnet provisioning NSS management service consumer wants to (re-)configure the constituents of a NSSI.
Step 1 (M)The network slice subnet provisioning NSS management service consumer sends requests to the network slice subnet provisioning NSS management service provider with slice operation information for (re-)configuring a network slice subnet.
Step 2 (M)The network slice subnet provisioning NSS 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 CM provisioning management service providers (e.g., other network slice subnet provisioning NSS service providers, CM of NFsNF 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 clauses 5.3.2, 5.3.3 in TS 28.541) and 2) Configuration of shared NFs (see clause 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 NSS management service provider sends the processing result to the network slice subnet provisioning NSS management service consumer (might be based on applicable processing results from other CM service providers).
Ends whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsThe required (re)configuration is configured at the corresponding constituent(s).
TraceabilityREQ-PRO_NSSI-FUN-16
Up

5.1.14  Exposure of network slice management dataWord‑p. 25

Use case stage Evolution/Specification <<Uses>> Related use
GoalEnable network slice management service consumer to obtain network slice management data (e.g. PM data, FM data).
Actors and RolesNetwork slice management service consumer. For example, CSMF plays the role of network slice management service consumer. Network slice management service provider. For example, NSMF plays the role of network slice management service provider.
Telecom resourcesNetwork slice instance
AssumptionsThe network slice management service consumer is authorized to obtain the network slice management data from the network slice management service provider.
Pre-conditionsNSI is created.
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsThe network slice management service consumer obtained the network slice management data.
TraceabilityREQ-PRO_NSI-FUN-7
Up

5.1.15  Exposure of network slice management capabilityWord‑p. 25

Use case stage Evolution/Specification <<Uses>> Related use
GoalEnable 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 RolesNetwork slice management service consumer. For example, CSP providing NSaaS plays the role of network slice management service consumer.
Telecom resourcesNetwork slice instance
Network slice management service provider. For example, NSMF plays the role of network slice management service provider.
AssumptionsThe 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-conditionsLevel of management exposure has been agreed upon between the network slice management service provider and the network slice management service consumer.
Begins whenThe 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 whenAll the steps identified above are successfully completed.
ExceptionsOne of the steps identified above fails.
Post-conditionsThe network slice management service consumer obtained the allowed network slice management capability.
TraceabilityREQ-PRO_NSI-FUN-1, REQ-PRO_NSI-FUN-3, REQ-PRO_NSI-FUN-6
Up

Up   Top   ToC