Content for TS 23.435 Word version: 19.3.0
0…
4…
5…
7…
9…
9.4…
9.5…
9.6…
9.7…
9.8…
9.9…
9.10…
9.11…
9.12…
9.13…
9.14…
9.15…
9.16…
9.17…
9.18…
A…
9.12 Slice related communication service lifecycle management exposure
9.12.1 General
9.12.2 Procedure
9.12.2.1 Procedures on slice related communication service lifecycle management exposure
9.12.2.1.1 Slice related Communication Service Creation
9.12.2.1.2 Slice related Communication Service Reconfiguration
9.12.2.1.3 Slice related Communication Service disengagement
9.12.3 Information flows
9.12.4 APIs
9.12.4.1 General
9.12.4.2 SS_NSCE_SliceCommService_Creation API
9.12.4.3 SS_NSCE_SliceCommService_Reconfiguration API
9.12.4.4 SS_NSCE_SliceCommService_Disengagement API
...
...
9.12 Slice related communication service lifecycle management exposure p. 84
9.12.1 General p. 84
The NSCE server supports the slice related communication service lifecycle management exposure to VAL server. The NSCE server acquires the application services related requirements for a specific VAL service from the vertical industry perspective, evaluates these requirements and then determines the network slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined the NSCE server allocate proper network slice resources to support the application services. The NSCE server also enables the VAL server to reconfigure or disengage the slice related communication services for the application. The procedures in clause 9.12.2 are for creation, reconfiguration and disengagement of slice related communication service respectively.
9.12.2 Procedure p. 84
9.12.2.1 Procedures on slice related communication service lifecycle management exposure p. 84
9.12.2.1.1 Slice related Communication Service Creation p. 84
Figure 9.12.2.1.1-1 illustrates the procedure of slice related communication service creation. The NSCE helps to allocate network slice resources to support the application service required by the verticals.
Pre-conditions:
- The VAL server has registered to receive NSCE services.
Step 1.
The VAL server sends a request to NSCE server to create a slice related communication service to support a specific application service, e.g., the VAL server wants to create a video streaming service in a future factory, the slice related communication service creation request carries the identifier of the video streaming service and the corresponding service attributes.
Step 2.
NSCE server translates the application service requirements (e.g., for a video streaming service, the service location and the resolution of the video) and then perform slice determination (e.g., dLtThptPerSlice, uLtThptPerSlice, latency as defined in serviceProfile TS 28.541). The NSCE may perform the translation by pre-configured industry profiles or by KQI-KPI translation algorithms which are out scope of standard. The procedures of APIs translation defined in clause 9.3 are referred to.
Step 3.
NSCE server initiates the Slice Service subscription procedures by utilizing the management service of network slice creation as defined in clause 6.1 of TS 28.531 exposed by EGMF defined in SA5. The slice creation request may fail due to the shortage of network resources or other causes.
Step 4.
NCSE server sends the slice related communication service creation response to VAL server. If the slice creation is succeeded in step3, then the response from NSCE server should include the attributes and the values of network slice determined by NSCE server. If the slice creation failed in step3, the NSCE server shall indicate the cause of the creation failure, e.g. the shortage of network slice resources.
9.12.2.1.2 Slice related Communication Service Reconfiguration p. 85
Figure 9.12.2.1.2-1 illustrates the procedure of slice related communication service reconfiguration to support the application service. The NSCE server provides the APIs to enable the VAL server to reconfigure the application service related requirements in case the current application service is not satisfied or application service is adjusted.
Pre-conditions:
- The VAL server has registered to receive NSCE services.
- The VAL server has requested the NSCE server to create a slice related communication service to support the application service.
Step 1.
VAL server sends the slice related communication service reconfiguration request to the NSCE server to reconfigure the properties of the application service (e.g., In case there is a downgrade/upgrade of the application service where the application service profile is changed).
Step 2.
NSCE server translates the application requirements according to the reconfigured application properties then updates the requested network slice.
Step 3.
NSCE server initiates the Slice Service update procedures by utilize the management service of network slice modification as defined in clause 6.1 of TS 28.531 exposed by EGMF defined in SA5.
Step 4.
NCSE server sends the slice related communication service modification response to VAL server.
9.12.2.1.3 Slice related Communication Service disengagement p. 86
Figure 9.12.2.1.3-1 illustrates the procedure of slice related communication service disengagement. The NSCE server provides the APIs to enable the VAL server to terminate an application service.
Pre-conditions:
- The VAL server has registered to receive NSCE services.
- The VAL server has requested the NSCE server to create a slice related communication service to support the application service.
Step 1.
The VAL server sends a request to NSCE server to disengage the slice related communication service when the application service is to be terminated.
Step 2.
NSCE server initiates the Slice Service de-allocation procedures by utilizing the management service of network slice de-allocation as defined in clause 6.1 of TS 28.531 exposed by EGMF defined in SA5.
Step 3.
NCSE server sends the slice related communication service disengagement response to VAL server.
9.12.3 Information flows p. 87
9.12.3.1 General p. 87
The following information flows are specified for slice related communication service lifecycle management:
- slice related communication service creation,
- slice related communication service reconfiguration,
- slice related communication service disengagement.
9.12.3.2 Slice related communication service creation p. 87
Table 9.12.3.2-1 and Table 9.12.3.2-2 describe information elements for slice related communication service creation request and response between the VAL server and the NSCE server.
| Information element | Status | Description |
|---|---|---|
| VAL server ID | M | The identifier of the VAL server. |
| VAL service name | M |
The name of the application service to be supported by the created slice related communication service, the value can be as followings:
|
| VAL service ID | M | Identifier of the application service. |
| Area of interest | M | The service area for which the application service profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA). |
| Application service profile | M | The list of the requirements of the corresponding application service. |
| > ReqInfo | M | The element containing the reqName and reqValue. |
| >> ReqName | M |
The name of the application service requirement, the value of this IE can be as followings:
|
| >> ReqValue | M | The corresponding value of the application service requirement. |
| Information element | Status | Description |
|---|---|---|
| VAL server ID | M | The identifier of the VAL server. |
| VAL service ID | M | Identifier of the application service to be supported by the created slice related communication service. |
| Result | M | Indicates the success or failure of the slice related communication service creation. |
| Network slice info List | O
(see NOTE 1) | The list of the network slice info determined by NSCE. |
| > Network slice info | O
(see NOTE 1) | The network slice info which includes the attributes and the corresponding values of network slice. |
| >> S-NSSAI | O
(see NOTE 1) | The identifier of network slice. |
| >> attributes of network slice | O
(see NOTE 1) | The list of attributes of the serviceProfile e.g, dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541. |
| >> AttributeValues | O
(see NOTE 1) | The corresponding values of the attributes of the service profiles that determined by the NSCE server. |
| Cause | O
(see NOTE 2) | Indicates the cause of creation failure. |
|
NOTE 1:
Shall be present if the result is success and shall not be present otherwise.
NOTE 2:
Shall be present if the result is failure and shall not be present otherwise.
|
||
9.12.3.3 Slice related communication service reconfiguration p. 88
Table 9.12.3.3-1 and Table 9.12.3.3-2 describe information elements for slice related communication service reconfiguration request and response between the VAL server and the NSCE server.
| Information element | Status | Description |
|---|---|---|
| VAL server ID | M | The identifier of the VAL server. |
| VAL service name | M |
The name of the application service to be upgrade/downgrade which requires the reconfiguration of the slice related communication service, the value can be as followings:
|
| VAL service ID | M | Identifier of the application service. |
| Area of interest | M | The service area for which the application profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA). |
| Application service profile | M | The list of the requirements of the corresponding application service to be changed. |
| > ReqInfo | M | The element containing the reqName and reqValue. |
| >> ReqName | M |
The name of the application service requirement, the value of this IE can be as followings:
|
| >> ReqValue | M | The corresponding updated value of the application service requirement. |
| Information element | Status | Description |
|---|---|---|
| VAL server ID | M | The identifier of the VAL server. |
| VAL service ID | M | Identifier of the application service. |
| Result | M | Indicates the success or failure of the slice related communication service reconfiguration. |
| Network slice info List | O
(see NOTE 1) | The list of the network slice info updated by NSCE. |
| > Network slice info | O
(see NOTE 1) | The network slice info which includes the attributes and the corresponding values of network slice. |
| >> S-NSSAI | O
(see NOTE 1) | The identifier of network slice. |
| >> Attributes of network slice | O
(see NOTE 1) | The list of attributes of the serviceProfile e.g., dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541. |
| >> AttributeValues | O
(see NOTE 1) | The corresponding values of the attributes of the service profiles that updated by the NSCE server. |
| Cause | O
(see NOTE 2) | Indicates the cause of reconfiguration failure. |
|
NOTE 1:
Shall be present if the result is success and shall not be present otherwise.
NOTE 2:
Shall be present if the result is failure and shall not be present otherwise.
|
||
9.12.3.4 Slice related communication service disengagement p. 90
| Information element | Status | Description |
|---|---|---|
| VAL server ID | M | The identifier of the VAL server. |
| VAL service name | M |
The name of the application service to be terminated which requires the disengagement of the slice related communication service, the value can be as followings:
|
| VAL service ID | M | Identifier of the application service. |
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates the success or failure of the slice related communication service disengagement request. |
| VAL server ID | M | The identifier of the VAL server. |
| VAL service ID | M | Identifier of the application service. |
| Cause | O
(see NOTE) | Indicates the cause of disengagement failure. |
|
NOTE:
Shall be present if the result is failure and shall not be present otherwise.
|
||
9.12.4 APIs p. 90
9.12.4.1 General p. 90
Table 9.12.4.1-1 and Table 9.12.4.1-2 illustrate the API for slice related communication service lifecycle management exposure.
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| SS_NSCE_SliceCommService_Creation | SliceCommService_Creation_Request | Request /Response | VAL server |
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| SS_NSCE_SliceCommService_Reconfiguration | SliceCommService_Reconfiguration_Request | Request /Response | VAL Server |
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| SS_NSCE_SliceCommService_Disengagement | SliceCommService_Disengagement_Request | Request /Response | VAL Server |
9.12.4.2 SS_NSCE_SliceCommService_Creation API p. 90
API operation name:
SliceCommService_Creation
Description:
The consumer requests to create the slice related communication service
Known Consumers:
VAL server.
Inputs:
See Table 9.12.3.2-1.
Outputs:
See Table 9.12.3.2-2.
See clause 9.12.2.1.1 for details of usage of this operation.
9.12.4.3 SS_NSCE_SliceCommService_Reconfiguration API p. 91
API operation name:
SliceCommService_Reconfiguration
Description:
The consumer requests to report reconfigure the slice related communication service.
Known Consumers:
VAL server.
Inputs:
See Table 9.12.3.3-1.
Outputs:
See Table 9.12.3.3-2.
See clause 9.12.2.1.2 for details of usage of this operation.
9.12.4.4 SS_NSCE_SliceCommService_Disengagement API p. 91
API operation name:
SliceCommService_Disengagement
Description:
The consumer requests to disengagement the slice related communication service.
Known Consumers:
VAL server.
Inputs:
See Table 9.12.3.4-1.
Outputs:
See Table 9.12.3.4-2.
See clause 9.12.2.1.3 for details of usage of this operation.
