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.4 Application layer network slice lifecycle management
9.4.1 General
9.4.2 Procedure
9.4.2.1 Procedures on slice lifecycle management
9.4.3 Information flows
9.4.4 APIs
9.4.4.1 General
9.4.4.2 SS_NSCE_AppLayerNSLCM_Subscribe operation
9.4.4.3 SS_NSCE_AppLayerNSLCM_Notify operation
9.4.4.4 SS_NSCE_Val_QoEMetrics_Subscribe operation
9.4.4.5 SS_NSCE_Val_QoEMetrics_Notify operation
9.4.4.6 SS_NSCE_Val_NSLCMRecommendation _Request operation
...
...
9.4 Application layer network slice lifecycle management p. 30
9.4.1 General p. 30
When NSCE receives a request for application layer network slice lifecycle management (AppLayer_NS_LCM) from VAL server, the NSCE server performs the service operations including subscribing the event which may trigger the management system to do the network slice lifecycle management, making the network slice lifecycle management recommendation/decision, triggering the network slice lifecycle management operations, notifying the consumer about the network slice information.
9.4.2 Procedure p. 30
9.4.2.1 Procedures on slice lifecycle management p. 30
Figure 9.4.2.1-1 illustrates a procedure of application layer network slice lifecycle management based on network slice related data and QoE collected from application layer.
Pre-conditions:
- The NSCE server has authenticated and authorized to the capabilities to collect current network slice from 5GS.
- The NSCE server has authenticated and authorized to the capabilities trigger the network slice LCM operations.
- There is signed contract for LCM between the entities using VAL server and entities using NSCE.
Step 1.
The VAL server sends the application layer network slice lifecycle management (AppLayer-NS-LCM) subscribe request to NSCE server, with network slice requirements from VAL server/consumer (e.g. delay, throughput, load, the maximum number of users supported, etc.). The request can indicate whether the notification is needed before performing the AppLayer-NS-LCM. The request can also indicate the trigger conditions, such as by providing the monitored parameters and the corresponding thresholds as described in clause 9.4.3.2.
Step 2.
After receiving the request, the NSCE server checks that the user is authenticated and authorized to perform the corresponding AppLayer-NS-LCM operations, and filters the unauthorized requests, if any.
Step 3.
According to network slice requirements and/or the trigger conditions, NSCE server triggers the provision of network slice status and QoE metrics. If the trigger conditions are not indicated in the subscription, the NSCE server can help to configure an appropriate trigger condition, such as report period or thresholds.
Step 3a.
The network slice status could be collected through subscribing or requesting to 5GS. List of network slice status parameters to be collected are:
Step 3b.
- Network Slice load statistics information, and/or Network Slice load predictions information from NWDAF/NEF as defined in TS 23.288 Table 6.3.3A-1.
- Performance metric in the performance data file from OAM as defined in clause 11.3 of TS 28.532.
Also, the NSCE server could get the information of QoE metrics from the application layer domain by QoE metric subscribe as described in clause 9.4.3.5.
Step 4.
Once authenticated and authorized, the NSCE server sends the AppLayer-NS-LCM response to the VAL server.
Step 5.
The NSCE server may process and combine the collected network slice status and QoE metrics, if needed. The NSCE server may process and combine the parameters in the trigger conditions, if multiple trigger conditions were provided. Once the trigger condition or the combination of trigger conditions are met which indicating the network slice requirements from VAL server is not satisfied, the NSCE server determines whether and what network slice LCM operations should be taken based on requirements from VAL server/consumer and network slice status and QoE metrics, and makes the decision(s)/recommendation(s), such as modifyNsi/AllocateNsi/DeallocateNsi request as specified in TS 28.531.
Step 6.
Optionally, if it is indicated in the request to notify the VAL server/consumer before performing the AppLayer-NS-LCM, the NSCE sends the network slice LCM recommendation(s) with network slice information to VAL server, to see whether takes the recommendation(s) or not.
Step 7.
Optionally, the VAL server sends the response to NSCE server.
Step 8.
Based on decision made by VAL server or NSCE server, the NSCE server sends the network slice LCM request to the OAM.
Step 9.
According to the corresponding operation(s) result, the NSCE server sends the response to the VAL server.
9.4.3 Information flows p. 32
9.4.3.1 General p. 32
The following information flows are specified for AppLayer_NS_LCM:
- AppLayer_NS_LCM subscribe, response and notification;
- QoE metrics subscribe, response and notification;
- Network slice LCM recommendation request and response;
9.4.3.2 Application layer network slice lifecycle management subscribe request p. 32
Table 9.4.3.2-1 describes information elements for the application layer network slice lifecycle management subscribe request from the VAL server to the NSCE server.
| Information element | Status | Description |
|---|---|---|
| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). |
| Security credentials | M | Security credentials resulting from a successful authorization for the NSCE service. |
| Service requirement | M | The VAL application requirements pertaining to the slice as defined in Table 9.1.1.1-1. |
| AppLayer-NS-LCM notification indication | M | Indicates whether to notify the VAL server/consumer about the AppLayer-NS-LCM. |
| >AppLayer-NS-LCM notification address (see NOTE) | O | The address (e.g. URL) of the consumer that can receive the AppLayer-NS-LCM notification. |
| Trigger condition | O |
Indicates the monitored parameters and the corresponding thresholds which could trigger the AppLayer-NS-LCM.
The supported trigger conditions are:
|
| Proposed expiration time | O | Proposed expiration time for the subscription. |
|
NOTE:
When the AppLayer-NS-LCM recommendation notification is needed, AppLayer-NS-LCM notification indication should be provided.
|
||
9.4.3.3 Application layer network slice lifecycle management response p. 32
The information elements specified in the Table 9.4.3.3-1 is used for the application layer network slice lifecycle management response sent from the NSCE server to the VAL server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates that the success or failure. |
| > Cause | O
(see NOTE) | Indicates the cause of AppLayer-NS-LCM request failure. |
|
NOTE:
May only be present if the result is failure.
|
||
9.4.3.4 Application layer network slice lifecycle management notification p. 33
The information elements specified in the Table 9.4.3.4-1 is used for the application layer network slice lifecycle management notification sent from the NSCE server to the VAL server.
| Information element | Status | Description |
|---|---|---|
| Successful response (see NOTE) | O | Indicates that the AppLayer-NS-LCM request was successful. |
| > network slice information | M | Network slice information (i.e. NEST) with network slice identifier(i.e. S-NSSAI). |
| Failure response (see NOTE) | O | Indicates that the AppLayer-NS-LCM request failed. |
| > Cause | O | Indicates the cause of AppLayer-NS-LCM request failure. |
|
NOTE:
One of these IEs shall be present in the message.
|
||
9.4.3.5 QoE metrics subscribe p. 33
Table 9.4.3.5-1 describes information elements for the QoE metrics subscribe from the NSCE server to the VAL server.
| Information element | Status | Description |
|---|---|---|
| Requestor Identifier | M | Unique identifier of the requestor (i.e. NSCE server ID). |
| Security credentials | M | Security credentials resulting from a successful authorization. |
| Notification Target Address | O | The Notification Target Address (e.g. URL) where the notifications destined for the requestor should be sent to. |
| Subscription ID | M | Identifier of the subscription. |
| Event Filter | M | The associated filter on a network slice to be notified. |
| > Network slice related Identifier(s) | M | Identifier of the interested network slice. |
| > VAL service ID | O | Indicator of the interested application (i.e. App ID). |
| > QoE type indicator | M | QoE metric type including latency, throughput, jitter, etc. |
| Event Reporting information | M | Information indicates how the notification is supposed to be sent, threshold based or the notification is periodical or the Immediate reporting is requested. |
| > Threshold | O | Threshold of QoE metrics. |
| > Reporting period | O | Indicating the metrics reporting period. |
| > Immediate reporting flag | O | Indicating the request needs immediate reporting or not. |
| Proposed expiration time | O | Proposed expiration time for the subscribe. |
9.4.3.6 QoE metrics response p. 34
Table 9.4.3.6-1 describes the information elements for the QoE metrics response from the VAL server to the NSCE server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates the success or failure of the QoE metrics request. |
| > Subscription ID | O
(see NOTE 1) | Subscription identifier corresponding to the subscription. |
| > QoE metrics report | O
(see NOTE 2) | List of result values for the observed or computed QoE metrics value if the immediate reporting is needed. |
| > Cause | O
(see NOTE 3) | Indicates the cause of QoE metrics request failure. |
|
NOTE 1:
Shall be present if the result is success and shall not be present otherwise.
NOTE 2:
May only be present if the result is success.
NOTE 3:
May only be present if the result is failure.
|
||
9.4.3.7 QoE metrics notification p. 34
Table 9.4.3.7-1 describes the information elements for the QoE metrics notification from the VAL server to the NSCE server.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Indicates that the QoE metrics request was successful. |
| QoE metrics report | M | List of result values for the observed or computed QoE metrics value. |
9.4.3.8 Network slice LCM recommendation request p. 34
Table 9.4.3.8-1 describes information elements for the Network slice LCM recommendation request from the NSCE server to the VAL server.
| Information element | Status | Description |
|---|---|---|
| Requestor Identifier | M | Unique identifier of the requestor (i.e. NSCE server ID). |
| Security credentials | M | Security credentials resulting from a successful authorization. |
| Network slice LCM recommendation | M | Recommended network slice lifecycle management operation. |
| > Network slice related Identifier(s) | M | Identifier of the network slice. |
| >Recommend network slice LCM action | M | Recommend network slice LCM action(i.e. modifying the configuration, allocating a network slice). |
| >Network slice information | O | Network slice information if the action is taken(i.e. NEST). |
9.4.3.9 Network slice LCM recommendation response p. 34
Table 9.4.3.9-1 describes the information elements for the Network slice LCM recommendation response from the VAL server to the NSCE server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates that the Network slice LCM recommendation request was accepted or not. |
| > Cause | O
(see NOTE) | Indicates the cause of failure. |
|
NOTE:
May only be present if the result is failure.
|
||
9.4.4 APIs p. 35
9.4.4.1 General p. 35
Table 9.4.4.1-1 illustrates the API for application layer network slice lifecycle management.
| API Name | API Operations | Operation Semantics | Consumer(s) |
|---|---|---|---|
| SS_NSCE_AppLayerNSLCM | Subscribe | Subscribe/Response | VAL server |
| Notify | Notify | VAL server | |
| SS_NSCE_Val_QoEMetrics | Subscribe | Subscribe/Response | NSCE |
| Notify | Notify | NSCE | |
| SS_NSCE_Val_NSLCMRecommendation | Subscribe | Subscribe/Response | NSCE |
9.4.4.2 SS_NSCE_AppLayerNSLCM_Subscribe operation p. 35
API operation name:
AppLayerNSLCM_Request
Description:
The consumer subscribes for AppLayer_NS_LCM.
Inputs:
See clause 9.4.3.2.
Outputs:
See clause 9.4.3.3.
See clause 9.4.2 for details of usage of this operation.
9.4.4.3 SS_NSCE_AppLayerNSLCM_Notify operation p. 35
API operation name:
AppLayerNSLCM_Notify
Description:
The consumer is notified with result of AppLayer_NS_LCM.
Inputs:
See clause 9.4.3.4.
Outputs:
None
See clause 9.4.2 for details of usage of this operation.
9.4.4.4 SS_NSCE_Val_QoEMetrics_Subscribe operation p. 35
API operation name:
QoEMetrics_Subscribe
Description:
The consumer subscribes for the QoE metrics.
Inputs:
See clause 9.4.3.5.
Outputs:
See clause 9.4.3.6.
See clause 9.4.2 for details of usage of this operation.
9.4.4.5 SS_NSCE_Val_QoEMetrics_Notify operation p. 36
API operation name:
QoEMetrics_Notify
Description:
The consumer is notified with the QoE metrics.
Inputs:
See clause 9.4.3.7.
Outputs:
None
See clause 9.4.2 for details of usage of this operation.
9.4.4.6 SS_NSCE_Val_NSLCMRecommendation _Request operation p. 36
API operation name:
NSLCMRecommendation _Request
Description:
The consumer request for whether to take the recommendation of the AppLayer_NS_LCM.
Inputs:
See clause 9.4.3.8.
Outputs:
See clause 9.4.3.9.
See clause 9.4.2 for details of usage of this operation.
