hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.8 Network slice LCM recommendation request | Table 9.4.3.8-1 describes information elements for the Network slice LCM recommendation request from the NSCE server to the VAL server.
Table 9.4.3.8-1: Network slice LCM recommendation Request
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) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.9 Network slice LCM recommendation response | 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.
Table 9.4.3.9-1: Network slice LCM recommendation Response
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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.1 General | Table 9.4.4.1-1 illustrates the API for application layer network slice lifecycle management.
Table 9.4.4.1-1: 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 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.2 SS_NSCE_AppLayerNSLCM_Subscribe operation | 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.3 SS_NSCE_AppLayerNSLCM_Notify operation | 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.4 SS_NSCE_Val_QoEMetrics_Subscribe operation | 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.5 SS_NSCE_Val_QoEMetrics_Notify operation | 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.4.6 SS_NSCE_Val_NSLCMRecommendation _Request operation | 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5 Network slice optimization based on VAL server policy | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.1 General | Based on policy from the vertical applications (e.g., to trigger some network slice operations when the pre-configured thresholds are met), the network slice parameters for the vertical applications could be optimized by triggering the slice modification. The slice optimization can be triggered by OAM, data/prediction retrieved from NWDAF via NEF, and NSCE server itself as describe in 9.5.2.2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1 VAL server policy management | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1.1 VAL server policy provisioning | Figure 9.5.2.1.1 illustrates the procedure of VAL server policy provisioning from the VAL server to the NSCE server.
Pre-conditions:
1. The NSCE server has information about the existing slice/slice profile/slice services which VAL server is using.
Figure 9.5.2.1.1: VAL server policy provisioning
1. VAL server sends VAL server policy provisioning request to NSCE server. The request contains the policy, VAL server ID, Default policy indication, and S-NSSAI. Optionally, the request contains the indicator of policy harmonization.
The VAL server can request the NSCE server to mark the provisioned policy as the default policy using the Default policy indication. The default policy should serve as a VAL server policy for the slices provisioned without any policy. Either the policy or default policy indication can be provided by the VAL server.
The VAL server policy is in form of a policy profile which contains list of trigger events associated with the parameters and expected actions. It contains priority and scheduling information with pre-emption capability for the policies. The scheduling information schedules the policy by defining the schedule (start and end time) for the policy. The pre-emption capability provides another, already successfully provisioned policy to pre-empt the scheduled policy in the scheduled period.
The supported policies are:
- Based on monitored performance metric from OAM, when the max number of PDU sessions or max number of UE is reached, trigger the slice modification with expected parameters.
- Based on monitored Network Slice load from NSACF, when the number of PDU sessions or number of UE exceeds the threshold, trigger the slice modification with expected parameters.
- Based on monitored Network Slice load predictions from NWDAF, when Network Slice load predictions (Predicted Number of PDU Session establishments at the Network Slice) exceeds the threshold with high confidence, trigger the slice modification with expected parameters.
- Based on the monitored the time period, when getting to a certain time period (e.g. summer vacation, spring festival etc.), trigger the slice modification with expected parameters.
- Based on the monitored time period, when getting to a certain time period, trigger the slice modification based on the expected QoS per UE. QoS is mapped/calculated by NSCE to specific parameters of the slice such as the dLThptPerUE, uLThptPerUE, dLThptPerSliceSubnet, uLThptPerSliceSubnet, delayTolerance, dLLatency, uLLatency.
2. The NSCE server checks whether the policy is conflict with the MNO policies or NSPP. One criterion is to translate the network slice parameters in the service profile to see whether it is conflict with that in the VAL provided policy. If policy harmonization is not requested and policies conflict then the request could be rejected. The NSCE server also checks the validity of the policy (policy is valid for the specified time period or until the specified threshold count of trigger events is achieved) to avoid a ping-pong effect of slice modification. If the policy is invalid, the request could be rejected.
3. If the policy harmonization is requested, the NSCE server can harmonize the policy as per clause 9.5.2.1.4 and this may result in the changes to the current VAL server policy under provisioning.
4. NSCE server sends the VAL server policy provisioning response to the VAL server to indicate whether the request is successful or not. If it is successful, policy ID is provided to VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1.2 VAL server policy Update | Figure 9.5.2.1.2-1 illustrates the VAL server policy update procedure.
Pre-conditions:
1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using.
2. The VAL server has created policies in NSCE server using the procedure defined in clause 9.5.2.1.1.
Figure 9.5.2.1.2-1: VAL server policy update
1. VAL server sends VAL server policy update request to NSCE server. The request shall contain the policy ID and policy modification details for updating the policy in the NSCE server. The request can update the existing default policy or specify a new default policy for the mentioned slice in the request. The policy update procedure can update the scheduling and pre-emption information for the policy.
2. The NSCE server checks whether the policy is conflict with the MNO policies or NSPP.
3. If authorized, the NSCE server can harmonize the policy as per clause 9.5.2.1.4 and this may result in the changes to the current VAL server policy under update process.
4. If the VAL server is authorized to update the VAL server policy, the NSCE server checks the modification with existing policies to avoid conflict and provides the response to the VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1.3 VAL server policy Delete | Figure 9.5.2.1.3-1 illustrates the VAL server policy delete procedure.
Pre-conditions:
1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using.
2. The VAL server has created one or more policies in NSCE server using the procedure defined in clause 9.5.2.1.1.
Figure 9.5.2.1.3-1: VAL server policy delete
1. VAL server sends VAL server policy delete request to NSCE server. The request contains the policy ID, and optionally default policy indication. The default policy indicates the update of the default policy in the case of a delete request for the default policy. The policy delete procedure can be used to delete one or more policies.
2. If the VAL server is authorized to delete the VAL server policy, the NSCE server deletes the policy. In the case of a default policy delete request, the NSCE server first updates the default policy with the policy mentioned in the delete request and then deletes the old default policy. The NSCE server reports the outcome of the deletion of the requested policy with policy ID and priority for the new default policy. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1.4 Policy harmonization | Policy harmonization is to make sure the VAL server Policy (from VAL Provider/ slice customer/ASP) is compatible with the MNO policies and NSCE service provider policy for the same service or slice. The policy harmonization could be requested through the policy provisioning/update service.
Figure 9.5.2.1.4-1 illustrates the procedure for policy harmonization.
Pre-conditions:
1. The NSCE service provider policy (NSPP) and MNO policy is available at the NSCE Server.
2. The VAL server is authorized to receive NSCE services.
Figure 9.5.2.1.4-1: Policy harmonization
1. When receiving the policy provisioning, or policy update request, and the result of policy check turn out the policy is conflict, the policy harmonization is triggered.
2. The NSCE server determines parameters harmonizing the policy, if previously authorized.
3. NSCE server sends the VAL server a notification providing parameters values that allow the policies to be harmonized. Then the VAL server would decide whether to accept the provided optional parameters values. If they are accepted, the VAL server may invoke VAL server policy provisioning/ VAL server policy update procedure defined in clause 9.5.2.1.1, 9.5.2.1.2 with harmonized parameters values. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.1.5 VAL server policy Usage Reporting data | Figure 9.5.2.1.5-1 illustrates the VAL server policy usage reporting data procedure.
Pre-conditions:
1. The NSCE server has information about the existing slice/slice profile/slice services which VAL server is using.
2. The VAL server has created one or more policies using in the NSCE server the procedure defined in clause 9.5.2.1.1.
Figure 9.5.2.1.5-1: VAL server policy usage reporting data
1. VAL server sends VAL server policy usage reporting data subscribe request to NSCE server. The request contains the policy ID, reporting interval, and the required duration of the data.
2. The NSCE server responds with a VAL server policy usage reporting data subscribe response message indicating the success or failure of the subscription.
3. The NSCE server reports the policy reporting data containing the number of times the policy has been used and the duration for which the policy was active in the requested duration and details of the preemption of policies. The reporting interval enables the periodic reporting of the requested report. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.2 Network slice optimization based on VAL server policy | Figure 9.5.2.2-1 illustrates the procedure of network slice optimization based on VAL server policy.
Pre-conditions:
1. The NSCE server is authorized to get network slice management data notification from OAM, and/or NWDAF via NEF.
2. The VAL server is authorized to the NSCE server for network slice optimization.
3. There is enough network capacity when the expected action is to expand the network slice.
4. The VAL server policy has been pre-configured on the VAL server.
5. The VAL server policy has been provided to the NSCE server as specified in clause 9.5.2.1.
Figure 9.5.2.2-1: Network slice optimization based on VAL server policy
1. VAL server sends network slice optimization subscription request to NSCE server. The request contains the policy ID indicating the different policies. Optionally the request contains the Secondary policy ID indicating the fallback policy to be used for the failed network slice optimization. The NSCE server retries the network slice optimization using a Secondary policy in the case of a failed optimization.
2. The NSCE server translates the trigger event to service API(s) with necessary parameters, and subscribe to the related service if needed.
- To get the monitored performance metric from OAM, the notifyThresholdCrossing as defined in TS 28.532[7] clause 11.3.1.3 which is filled in with corresponding S-NSSAI in objectInstance could be used.
- To obtain the Network Slice load predictions from NWDAF, the NSCE server subscribes to the NWDAF prediction by invoking Nnef_AnalyticsExposure_Subscribe or Nnef_AnalyticsExposure_Fetch as defined in TS 23.288[4] clauses 6.1.1.2, and 6.1.1.2.
- To monitor the Network Slice load (e.g. the number of UEs or the number of PDU Sessions) from NSACF, the NSCE server subscribes to the NSACF by using the Nnef_EventExposure_Subscribe Request or Nnsacf_SliceEventExposure_Subscribe_Request as defined in clause 4.15.3.2.10 of TS 23.502 [12], and the APIs defined in clause 6.2 of TS 29.536 [13] can be utilized.
- To monitor the time period, the NSCE server setup the timer.
3. NSCE server sends the network slice optimization subscription response to the VAL server to confirm the subscription of network slice optimization.
4. Upon receiving the notification which indicating the trigger event is met, i.e., the monitored information reaches the threshold or specific time period is arrived, the NSCE server performs the expected action by triggering the slice modification as specified in the VAL server policy. The network slice modification could be triggered by consuming the Network Slice Provisioning service with the modifyMOIAttributes operation as specified in TS 28.531 [8]. The OAM responds back to NSCE server that the requested slice modification was successful or not. The slice modification requests contain the parameters need to be updated to fit the requirement of network slice (e.g., scale in or scale out the network slice capability), including at least one of the following, uLThptPerSlice, dLThptPerSlice, dLThptPerUE, uLThptPerUE, dLThptPerSliceSubnet, uLThptPerSliceSubnet, delayTolerance, dLLatency, uLLatency, maximum number of UEs, maximum number of PDU session as specified in TS 28.541 [10].
NOTE 1: The slice modification could be done by application layer network slice lifecycle management as defined in clause 9.4.
5. The NSCE server provides a network slice optimization notification to the VAL server. The successful response optionally includes the Optimization time and the Enforced policy ID. The optimization time indicates the time the NSCE server has taken to optimize the slice. The Enforced policy ID indicates which secondary policy is used by the NSCE server for slice optimization in the case of a failed attempt for network slice optimization.
NOTE 2: There is no expectation to have constant and exact mapping between slice configuration parameters and actual traffic load of the same slice. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.2.3 Network slice optimization report retrieval | Figure 9.5.2.3-1 illustrates the Network slice optimization report retrieval procedure.
Pre-conditions:
1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using.
2. The VAL server has the created policies using the procedure defined in clause 9.5.2.1.1.
3. The VAL server has subscribed for the network slice optimization using the procedure defined in clause 9.5.2.2.
Figure 9.5.2.3-1: Network slice optimization report retrieval
1. The VAL server sends a Network slice optimization report request to the NSCE server. The request shall contain the subscription ID, optimization result window, and optional elements like optimization result filters, sorting rules, and result size. The VAL server creates a filter using the optimization result filter for the NSCE server requesting filtered successful or failed responses. The VAL server can create additional sorting rules for the NSCE server to request sorted results based on optimization time or policy ID or slice optimization event time in ascending or descending order. The result size indicates the number of results or responses for the report.
2. The NSCE server provides the report to the VAL server as per the request of the VAL server containing optimization response, optimization time, policy ID, and Enforced Policy information. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.1 General | The following information flows are specified:
- VAL server policy provisioning request and response;
- Network slice optimization subscription, response and notification;
- VAL server policy update request and response;
- VAL server policy delete request and response;
- VAL server policy usage reporting data subscribe request, response, and notification; and
- Network slice optimization report retrieval request and response.
- Policy harmonization notify. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.2 VAL server policy provisioning request | Table 9.5.3.2-1 describes information elements for the VAL server policy provisioning request from the VAL server to the NSCE server.
Table 9.5.3.2-1: VAL server policy provisioning Request
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.
Network slice related Identifier(s)
O
Identifier of the network slice.
Requested DNN
O
Indication of the DNN which is requested.
Indicator of policy harmonization
O
Indicating whether the policy harmonization is requested.
Policy
O
The policy profile is defined in Table 9.5.3.2-2. The supported VAL server policies are listed in Table 9.5.3.2-3 to Table 9.5.3.2-5.
Default policy indication
O
Indicates the policy in the request to mark as a default policy for slices provisioned without any policy.
Table 9.5.3.2-2 describes Policy profile of the VAL server policy provisioning request.
Table 9.5.3.2-2: Policy profile
Information element
Status
Description
Policy
O
The name of VAL server policy.
>Area of interest
M
The service area for which the policy profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>Trigger event
M
Indicating the event that should be monitored, associated with the threshold of the monitored parameter.
>Expected action
M
Indicating the excepted actions associated with the updated parameter.
Lifetime or number of events
M
Time duration or number of times the policy can take action.
Priority
O
Indicates the priority of the policy.
Scheduling period
O
Indicates the scheduling of policy in terms of time.
>Start time
M
Indicates the scheduled start time.
>End time
M
Indicates the scheduled end time.
Preemption
O
Indicates the pre-empt capability of the policy.
Table 9.5.3.2-3 to Table 9.5.3.2-6 list the supported policies.
Table 9.5.3.2-3: Policy of Max number of PDU sessions/ max number of UEs
Information element
Status
Description
Policy
O
Max number of PDU sessions/ max number of UEs
>Area of interest
M
The service area for which the policy profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>Trigger event
M
Threshold information, i.e. reached utilization of available capacity in %), or number of PDU sessions request/ UEs reached the threshold
>Expected action
M
Modification of PDU sessions / max number of UEs (step for increase in %)
Lifetime or number of events
M
Time duration or number of times the policy can take action.
Priority
O
Indicates the priority of the policy.
Scheduling period
O
Indicates the scheduling of policy in terms of time.
>Start time
M
Indicates the scheduled start time.
>End time
M
Indicates the scheduled end time.
Preemption
O
Indicates the pre-empt capability of the policy.
Table 9.5.3.2-4: Policy of Network slice load prediction
Information element
Status
Description
Policy
O
Network slice load prediction
>Area of interest
M
The service area for which the policy profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>Trigger event
M
Network Slice load predictions information from NWDAF as defined in TS 23.288 [4] clause 6.1.1 (exceeding utilization of available capacity in %)
>Expected action
M
Modification of related network slice parameters (step for increase in %)
Lifetime or number of events
M
Time duration or number of times the policy can take action.
Priority
O
Indicates the priority of the policy.
Scheduling period
O
Indicates the scheduling of policy in terms of time.
>Start time
M
Indicates the scheduled start time.
>End time
M
Indicates the scheduled end time.
Preemption
O
Indicates the pre-empt capability of the policy.
Table 9.5.3.2-5: Policy of Time period and average QoS per UE
Information element
Status
Description
Policy
O
Time period and average QoS per UE
>Area of interest
M
The service area for which the policy profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>Trigger event
M
Time/day configuration where specific network slice capacity /QoS per UE is expected, average QoS per UE requested
>Expected action
M
Modification of slice capacity to the requested needs
Lifetime or number of events
M
Time duration or number of times the policy can take action.
Priority
O
Indicates the priority of the policy.
Scheduling period
O
Indicates the scheduling of policy in terms of time.
>Start time
M
Indicates the scheduled start time.
>End time
M
Indicates the scheduled end time.
Preemption
O
Indicates the pre-empt capability of the policy.
Table 9.5.3.2-6: Policy of needed minimum QoS per UE
Information element
Status
Description
Policy
O
Minimum QoS per UE
Area of interest
M
The service area for which the policy profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>Trigger event
M
Time/day where minimum QoS per UE is expected, minimum QoS per UE requested
>Expected action
M
Modification of slice capacity to have the needed QoS per UE
Lifetime or number of events
M
Time duration or number of times the policy can take action.
Priority
O
Indicates the priority of the policy.
Scheduling period
O
Indicates the scheduling of policy in terms of time.
>Start time
M
Indicates the scheduled start time.
>End time
M
Indicates the scheduled end time.
Preemption
O
Indicates the pre-empt capability of the policy. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.3 VAL server policy provisioning response | Table 9.5.3.3-1 describes the information elements for the VAL server policy provisioning response from the NSCE server to the VAL server.
Table 9.5.3.3-1: VAL server policy provisioning Response
Information element
Status
Description
Result
M
Indicates the success or failure of the VAL server policy provisioning request.
> Policy ID
O
(see NOTE1) NOTE1)
Identifies the provided policy.
> Cause
O
(see NOTE2)
Indicates the cause of VAL server policy provisioning request 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.4 VAL server policy update request | Table 9.5.3.4-1 describes the information elements for the VAL server policy update request from the VAL server to the NSCE server.
Table 9.5.3.4-1: VAL server policy update request
Information element
Status
Description
Requestor Identifier
M
Unique identifier of the requestor (i.e. VAL server ID).
Requested slice information
M
Indication of the slice which is requested.
Policy ID
M
Identifies the provided policy.
Policy modification details (see NOTE)
O
Describe the details for the policy update. The policy profile is defined in Table 9.5.3.2-2. The supported VAL server policies are listed in Table 9.5.3.2-3 to Table 9.5.3.2-5.
Priority (see NOTE)
O
Indicates the priority of the policy.
Default policy indication (see NOTE)
O
Indicates the default policy for slices provisioned without any policy.
NOTE: At least one of these information elements shall be present. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.5 VAL server policy update response | Table 9.5.3.5-1 describes the information elements for the VAL server policy update response from the NSCE server to the VAL server.
Table 9.5.3.5-1: VAL server policy update response
Information element
Status
Description
Result
M
Indicates the success or failure of the VAL server policy update request.
>Policy ID
O
(see NOTE 1)
Identifies the provided policy.
>Updated Default policy indication
O
(see NOTE 2)
Indicates the update of default policy.
>Cause
O
(see NOTE 3)
Indicates the cause of the 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.6 VAL server policy delete request | Table 9.5.3.6-1 describes the information elements for the VAL server policy delete request from the VAL server to the NSCE server.
Table 9.5.3.6-1: VAL server policy delete request
Information element
Status
Description
Policy ID
M
Identifies the provided policy for delete.
Update Default policy indication
O
Indicates the update of default policy.
>Policy ID
M
Identifies the provided policy. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.7 VAL server policy delete response | Table 9.5.3.7-1 describes the information elements for the VAL server policy delete response from the NSCE server to the VAL server.
Table 9.5.3.7-1: VAL server policy delete response
Information element
Status
Description
Result
M
Indicates the success or failure of the VAL server policy delete request.
>Updated default policy
O
(see NOTE 1)
Policies with updated priority values.
>>Policy ID
M
Identifies the provided policy.
>>Priority
O
Indicates the updated priority values.
>Cause
O
(see NOTE 2)
Indicates the cause of the failure.
NOTE 1: May only be present if the result is success.
NOTE 2: May only be present if the result is failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.8 VAL server policy usage reporting data subscribe request | Table 9.5.3.8-1 describes information elements for the VAL server policy usage reporting data subscribe request from the VAL server to the NSCE server.
Table 9.5.3.8-1: VAL server policy usage reporting data subscribe request
Information element
Status
Description
Requestor Identifier
M
Unique identifier of the requestor (i.e. VAL server ID).
Requested slice information
M
Indication of the slice which is requested.
Requested policy reporting data
M
Indicates the request for policy reporting data.
>Policy ID
M
Identifies the provided policy.
>Start time
M
Indicates start time for the policy reporting data.
>End time
M
Indicates end time for the policy reporting data.
Reporting interval
O
Indicates the policy report data reporting interval. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.9 VAL server policy usage reporting data subscribe response | Table 9.5.3.9-1 describes information elements for the VAL server policy usage reporting data subscribe response from the NSCE server to the VAL server.
Table 9.5.3.9-1: VAL server policy usage reporting data subscribe response
Information element
Status
Description
Result
M
Indicates the success or failure of the VAL server policy usage reporting data subscribe request.
>Subscribe ID
O
(see NOTE 1)
Identifies the VAL server policy reporting subscribe event.
>Cause
O
(see NOTE 2)
Indicates the cause of the 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 failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.10 VAL server policy usage reporting data notification | Table 9.5.3.10-1 describes information elements for the VAL server policy usage reporting data notification from the NSCE server to the VAL server.
Table 9.5.3.10-1: VAL server policy usage reporting data notification
Information element
Status
Description
Subscribe ID
M
Identifies the VAL server policy usage reporting subscribe request.
Policy reporting data
M
Indicates the requested VAL server policy reporting data.
>Policy ID
M
Identifies the provided policy.
>Policy count
M
Indicates the number of times the policy is active.
>Policy time spent
M
Indicates the duration for usage of policy.
>Pre-empt count
O
Indicates the number of times the policy is premept with another policy.
>Pre-empt policy ID
O
Indicates the policy used for pre-emption. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.11 Network slice optimization subscription request | Table 9.5.3.11-1 describes information elements for the Network slice optimization subscription request from the VAL server to the NSCE server.
Table 9.5.3.11-1: Network slice optimization subscription request
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.
Notification Target Address
O
The Notification Target Address (e.g. URL) where the notifications destined for the requestor should be sent to.
Network slice related Identifier(s)
O
Identifier of the network slice.
Requested DNN
O
Indication of the DNN which is requested.
Policy ID
O
Identifies the VAL server policy.
Proposed expiration time
O
Proposed expiration time for the subscription.
Secondary policy ID
O
Secondary policy act as a fallback policy for the network slice optimization in the case of a failed network slice optimization. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.12 Network slice optimization subscription response | The information elements specified in the table 9.5.3.12-1 is used for the Network slice optimization subscription response sent from the NSCE server to the VAL server.
Table 9.5.3.12-1: Network slice optimization subscription Response
Information element
Status
Description
Result
M
Indicates the success or failure of the Network slice optimization subscription request.
> Subscribe ID
O
(see NOTE 1)
Identifies the Network slice optimization subscribe event.
> Cause
O
(see NOTE 2)
Indicates the cause of Network slice optimization subscription request 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.13 Network slice optimization notification | The information elements specified in the table 9.5.3.13-1 is used for the Network slice optimization notification sent from the NSCE server to the VAL server.
Table 9.5.3.13-1: Network slice optimization Notification
Information element
Status
Description
> Subscribe ID
M
Identifies the Network slice optimization subscribe event.
>Network slice information
M
Network slice information (i.e. NEST) with network slice identifier(i.e. S-NSSAI)
>Optimization time
O
Indicates time spent for slice optimization by the NSCE Server.
>Enforced policy ID
O
Indicates the policy used for slice optimization in the case of the failed network slice optimization.
NOTE: One of these IEs shall be present in the message. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.14 Network slice optimization report retrieval request | Table 9.5.3.14-1 describes information elements for the Network slice optimization report retrieval request from the VAL server to the NSCE server.
Table 9.5.3.14-1: Network slice optimization report retrieval request
Information element
Status
Description
Subscribe ID
M
Identifies the Network slice optimization subscribe event.
Optimization result filter
O
Filter for network slice optimization responses (successful or failure). The default value is successful responses.
Optimization result sort
O
Sort optimization results based on slice optimization event time or optimization time, or policy ID. The default value is Optimization time.
>Sort type
O
Indicate sort type (ascending or descending). The default value is ascending.
>Optimization result size
O
Indicate the number of results of network slice optimization responses. The default value is 1.
Optimization result window
M
Indicates the time duration window for the report.
>Start time
M
Indicates the start time for generating the report.
>End time
M
Indicates the end time to finish the capture of the report. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.15 Network slice optimization report retrieval response | Table 9.5.3.15-1 describes information elements for the Network slice optimization report retrieval response from the NSCE server to the VAL server.
Table 9.5.3.15-1: Network slice optimization report retrieval response
Information element
Status
Description
Optimization report results
M
Report results based on the network slice optimization request.
>Subscribe ID
M
Identifies the Network slice optimization subscribe event.
>Optimization response
M
Indicates network slice optimization response as per the filter in the request.
>Optimization time
M
Indicates time spent for slice optimization by the NSCE Server.
>Policy ID
O
Identifies the VAL server policy.
>Enforced policy ID
O
Indicates the policy used for slice optimization in the case of the failed network slice optimization. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.3.16 Policy harmonization subscribe notify | Table 9.5.3.16-1 describes information elements for the Policy harmonization subscribe notify from the NSCE server to the VAL server.
Table 9.5.3.16-1: Policy harmonization subscribe notify
Information element
Status
Description
Policy ID
M
Identifies of the harmonized policy.
>harmonized policy
M
Pairs of policy attribute and harmonized parameter |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.1 General | Table 9.5.4.1-1 illustrates the API for Network slice optimization based on VAL server policy.
Table 9.5.4.1-1: Network slice optimization based on VAL server policy
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_PolicyManagement
Policy_Provisioning
Request/Response
VAL server
Policy_Update
Request/Response
Policy_Delete
Request/Response
Policy_Usage_Reporting_Data_Subscribe
Subscribe/Notify
Policy_Usage_Reporting_Data_Notification
SS_NSCE_NSOptimization
NS_Optimization_Subscription
Subscribe/Notify
VAL server
NS_Optimization_Notification
NS_Optimization_Report_Retrieval
Request/Response
SS_NSCE_Policy_harmonization
Policy_harmonization_Notify
Notify
VAL server |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.2 SS_NSCE_ Policy_Provisioning operation | API operation name: Policy_Provisioning_Request
Description: The consumer subscribes for VAL server policy Provisioning.
Inputs: See clause 9.5.3.2.
Outputs: See clause 9.5.3.3.
See clause 9.5.2.1.1 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.3 SS_NSCE_ Policy_Update operation | API operation name: Policy_Update
Description: Providing the policy update to the NSCE server.
Inputs: Refer subclause 9.5.3.4.
Outputs: Refer subclause 9.5.3.5.
See subclause 9.5.2.1.2 for details of the usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.4 SS_NSCE_ Policy_Delete operation | API operation name: Policy_Delete
Description: Requesting policy delete to the NSCE server.
Inputs: Refer subclause 9.5.3.6.
Outputs: Refer subclause 9.5.3.7.
See subclause 9.5.2.1.3 for details of the usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.5 SS_NSCE_Policy_harmonization Notify_operation | API operation name: Policy_harmonization_Notify
Description: The consumer is notified with result of Policy harmonization .
Inputs: See clause 9.5.3.16
Outputs: None
See clause 9.5.2.1.4 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.6 SS_NSCE_ Policy_Usage_Reporting_Data_Subscribe operation | API operation name: Policy_Usage_Reporting_Data_Subscribe
Description: Subscription to the VAL server policy usage reporting data.
Inputs: Refer subclause 9.5.3.8.
Outputs: Refer subclause 9.5.3.9.
See subclause 9.5.2.1.5 for details of the usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.7 SS_NSCE_ Policy_Usage_Reporting_Data_Notification operation | API operation name: Policy_Usage_Reporting_Data_Notification
Description: VAL server policy usage reporting data notification to the existing subscription.
Inputs: Refer subclause 9.5.3.10.
Outputs: None
See subclause 9.5.2.1.5 for details of the usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.8 SS_NSCE_NS_Optimization_Report_Retrieval operation | API operation name: NSOptimizationReportRetrieval
Description: Providing the network slice optimization report to the VAL server.
Inputs: Refer subclause 9.5.3.14.
Outputs: Refer subclause 9.5.3.15.
See subclause 9.5.2.3 for details of the usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.9 SS_NSCE_NSOptimization_Subscribe Request operation | API operation name: Ensce_NSOptimization _ Subscribe
Description: The consumer request for Network Slice Optimization.
Inputs: See clause 9.5.3.11.
Outputs: See clause 9.5.3.12.
See clause 9.5.2.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.5.4.10 SS_NSCE_NSOptimization_Notification operation | API operation name: Ensce_NSOptimization_Notification
Description: The consumer is notified with result of Network Slice Optimization.
Inputs: See clause 9.5.3.13.
Outputs: None
See clause 9.5.2.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6 Discovery of management service exposure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.1 General | A Management Domain (MD) feature/capability is anything of use offered by the management system to the 3rd party application. Therefore, a new feature could be a managed entity, a MnS or management API, any software, hardware, or other functionality – for example, new technology support, new coverage area, new network slice type or instance, new NFs or new network slice subnet type or instance. To be able to utilise capabilities/features of the management system the applications must be made aware of existence of such features and capabilities. All MD features/capabilities come with a pre-configured exposure, where this can be configured by the operator for a given slice. This exposure is used to decide which application can see which information regarding the capability/feature. Exposure refers to the permissions that the 3rd party entity has gained over its use of the management service, e.g., the ability to read, or execute or modify or delete can be considered as different sorts of exposure.
The first procedure (9.6.2.1) provides the NSCE server support for translating the VAL server request to a MnS requirement and the exposure of service/management data related to his request. The second procedure (9.6.2.2) supports the notification to the VAL server, based on a new/modified MnS / capability for a target slice. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.2.1 VAL-triggered MnS discovery procedure | In this procedure, the VAL server initially requests the new MnS which are supported by a target slice and based on this request the NSCE server requests from the OAM/MnS registry the MnS discovery. Then, the OAM/MnS registry derives the details to be exposed based on the NSCE server/VAL server permissions and provides the list of MnS for the given slice and the access details via the NSCE server to the VAL server.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
2. The NSCE server is trusted by the OAM, and a contract has been signed between the MNO and NSCE server provider to allow OAM interfaces and/or network slice information exposure.
3. MnS registry at OAM is aware of the allowed MnS and the permissions for a given slice.
Figure 9.6.2.1-1 illustrates a solution for the MnS discovery support.
Figure 9.6.2.1-1: MnS discovery support
The steps of this procedure are as follows:
1. The VAL server sends a Management Service Discovery subscribe request message to NSCE server to indicate a requirement for receiving the expected exposure capability type and the related permissions for a target slice or for a given VAL application.
2. The NSCE server sends a response to the subscription request, indicating a success or failure of the subscription request.
NOTE 1: If CAPIF is used, the API interactions for the MnS discovery subscription shall be compliant with CAPIF as specified in 3GPP TS 23.222.
3. The NSCE server translates the requirement based on the subscription, and in particular identifies the needed exposure capability type and translates it to a MnS exposure requirement. Such translation of the requirement includes the mapping to a list of MnSs (specified in TS 28.532) which are needed for the given slice and VAL server permissions.
4. The NSCE server coordinates with the 5GS and discovers the related network service(s), by triggering the MnS service discovery as specified in TS 28.537[9], clause 5.2.1.3. In particular, NSCE server acts as MnS discovery service consumer (for all MnS needed for a target slice based on VAL requirement) requests from MnS discovery service producer(s) at OAM the discovery of MnS information for the MnS related to the target slice or VAL application. The 5GS, MnS discovery service producer(s) sends the discovery result including related exposure information such as management service identifier, management service information and management service producer information to the NSCE server.
NOTE 2: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5.
5. The NSCE server sends a management service discovery subscription notify message to provide the service/management data based on step 4, including the list of MnS and the corresponding exposure details to the VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.2.2 OAM-triggered new/modified MnS discovery | This procedure includes the case when a new/modified MnS is deployed at the MD for the given slice, and the OAM/MnS registry provides this information directly to VAL server (assuming that VAL server has registered to the MD).
Pre-conditions:
1. VAL server is registered to NSCE server based on clause 9.2.
2. NSCE server has subscribed to OAM / MnS discovery service registry.
Figure 9.6.2.2-1: OAM-triggered new/modified MnS discovery
1. The MnS registry may discover new or modified MnS in the 3GPP MD. Such changes may be due to new/modified management service producers, new managed entities (such as new radio, new technology or new NFs), new/modified technical support (such as support in a new geography or coverage area), availability of new management data, e.g., related to slice performance. An example procedure related to the addition of a new MnS producer is provided in TS 28.537 clause 5.2.1.1.
The MnS discovery service producer when capturing new or modified capability (e.g. new MnS producer) related to the target slice or VAL application identifies the NSCE server which needs to be informed (based on the subscription) on the new/modified capability and derives the details to be exposed to the VAL server (via the NSCE server). Then, the MnS registry sends to the NSCE server the new / modified MnS.
NOTE: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5.
2. The NSCE server determines the VAL server(s) that needs to be notified on the new or modified MnS / MD capability based on their registrations. Then, NSCE server generates and sends a notification with the required information to be provided to the VAL server.
3. The information on the discovered new/modified MnS is sent as a management service discovery notification message from the NSCE server to VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.3.1 General | The following information flows are specified for the MnS discovery support based on 9.6.2 and 9.6.3. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.3.2 Management service discovery subscribe request | Table 9.6.4.2-1 describes information elements for the Management service discovery subscribe request from the VAL server to the NSCE server.
Table 9.6.3.2-1: Management service discovery subscribe request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
The identifier of the VAL service for which the MnS discovery request applies
Network slice related Identifier(s)
O
The slice identifier, if known by the VAL server
Exposure capability requirement
O
The requirement includes indication of the requested permissions for exposing information related to the target slice. Also, the requirement may include the exposure capability type which is supported (e.g. via EGMF or directly to MnS producer) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.3.3 Management service discovery subscribe response | Table 9.6.3.3-1 describes information elements for the Management service discovery subscribe response from the NSCE server to the VAL server.
Table 9.6.3.3-1: Management service discovery subscribe response
Information element
Status
Description
Result
M
The result of the subscription request (positive or negative acknowledgement)
> Cause
O
(see NOTE)
Indicates the cause of failure.
NOTE: May only be present if the result is failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.3.4 Management service discovery notify | Table 9.6.3.4-1 describes information elements for the Management service discovery notify message from the NSCE server to the VAL server.
Table 9.6.3.4-1: Management service discovery notify
Information element
Status
Description
VAL service ID
M
The identifier of the VAL application
Management Domain/System ID
M
The identifier of the management system/domain of interest
List of MnS IDs / MnS producer IDs
M
The list of identifiers of the needed MnSs / MnS producers
>MnS capability
M
The capability per needed MnS. Such capability may related to the managed elements such as considerations for radio, technology, coverage or NFs
>MnS permissions
O
Allowed permissions of the VAL server over the MnS, e.g. whether it is allowed to read, write, delete, and/or update.
Network slice related Identifier(s)
O
The slice identifier which is mapped to the VAL application and the list of MnSs. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.4.1 General | Table 9.6.4.1-1 illustrates the NSCE APIs for the MnS discovery feature.
Table 9.6.4.1-1: List of APIs for the MnS discovery feature
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_Management_Service_Discovery
Management_Service Discovery
VAL server
Subscribe/Notify |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.4.2 SS_NSCE_Management_Service Discovery | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.4.2.1 General | API description: This API enables the VAL server to communicate with the network slice capability enablement server for requesting management service discovery over NSCE-S. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.6.4.2.2 SS_NSCE_Management_Service Discovery | API operation name: Management_Service Discovery
Description: Providing for Management_Service Discovery subscribe to the NSCE server and receiving a confirmation.
Known Consumers: VAL server.
Inputs: See subclause 9.6.2.1 (step 1)
Outputs: See subclause 9.6.2.1 (step 4), 9.6.2.2 (step 3) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7 Network slice related performance and analytics monitoring | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.1 General | The NSCE server supports the end to end network slice related performance and analytic monitoring capability exposure. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the Core Network or the VAL end users), performs the data organizations and aggregations and expose the processed data to VAL servers for monitoring. Following clauses are for the procedures, information flows and APIs for Network slice related performance and analytics monitoring request and Network slice related performance and analytics reporting respectively. The procedure in clause 9.7.2.1 is for task creation of the network slice performance and analytics monitoring. The procedure in clause 9.7.2.2 is for the performance and analytics data retrieving when the data is available. The procedure in clause 9.7.2.3 is for multiple network slices performance and analytics consolidated report. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.2.1 Network slice related performance and analytics monitoring job creation request | For network slice related performance and analytics monitoring job creation capabilities exposed to the VAL server, the VAL server triggers the procedure by sending the network slice related performance and analytics monitoring job creation request to NSCE server as Figure 9.7.2.2-1 shows:
Figure 9.7.2.1-1: Request Network slice related performance and analytics job creation monitoring
1. The VAL server sends a request to NSCE server to create the Network slice related performance and analytics monitoring job to collect the desired service/VAL service specific performance and analytics data, the detailed content of the reported data depends on the type of the VAL services. The required end-to-end network slice related data performance data are indicated by Perflist IE as described in table 9.7.3.2-1.
2. The NSCE server shall check if the VAL server is authorized to request the network slice performance and analytics data monitoring job creation.
3. NSCE server determines the requested data needed to collect from network side and collects the performance measurements and analytics data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[7] is utilized, e.g., packet delay, radio resource utilization. For CN functions, the APIs of Nnwdaf_AnalyticsInfo service defined in clause 7.3, TS 23.288 [4] is utilized, e.g., slice load level related network data analytics, slice load level related network data analytics.
4. Optionally, NSCE server retrieves the KQI data of services, the QoE data and the end user’s information from NSCE client.
NOTE 1: The Data collection from NSCE client follows the mechanism defined in SA4 EVEX in TS 26.531 clause 5.6.
NOTE 2: How the collected data is stored in the NSCE server is implementation based.
5. NSCE server responds to VAL server to inform the VAL server if the monitoring request is succeed. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.2.2 Network slice related performance and analytics report subscription and report | For network slice related performance and analytics result subscription and report, the VAL server triggers the procedure by sending the network slice related performance and analytics report subscription to NSCE server, the NSCE server reports the performance and analytics report after the subscription is succeed, as Figure 9.7.2.2-1 shows:
Figure 9.7.2.2-1: Network slice related performance and analytics report subscription and report
1. The VAL server subscribes to the required performance and analytics report.
2. The NSCE server response to the VAL server to indicate whether the report is successfully generated and ready.
3. NSCE server correlates the performance data of network slice instance, the analytics data of group of UEs and the KQI/QoE data to generate the performance data and analytics data report as required by VAL server.
4. NSCE server sends the performance report Notify to VAL server if the report is ready. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.2.3 Multiple slices related performance and analytics consolidated report request | Based on preferred performance report request from the vertical applications, the consolidated performance report for dedicated service from multiple slices (PNI-NPN slice and PLMN slice of one network) can be offered to trusted third-party AF.
Figure 9.7.2.3-1 illustrates the procedure of multiple slices coordinated performance and analytics report service from VAL server to NSCE server.
Pre-conditions:
1. The network slice enabler layer is capable to interact with PLMN 5GC or OAM system to handle slices of PLMN and its PNI-NPNs.
2. PNI-NPNs are deployed as network slices of the PLMN.
3. NSCE server has subscribed for MDE and NWDAF analytics for the managed slices of PLMN and PNI-NPN.
Figure 9.7.2.3 -1: Multiple slices performance and analytics consolidated report process
1. The VAL server initiates multiple slices related performance and analytics consolidated report request towards the NSCE server. The request includes VAL server ID, VAL service ID. The message also includes application key performance indicator (such as end-to-end delay, throughput, etc.) list and monitoring period.
2. Upon receiving the request from the VAL server to manage the network slice QoS monitoring report, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized, the NSCE server replies with failure response.
3. The NSCE server makes mapping from application ID that received from VAL server to slice identities (S-NSSAIs allocated in each network) and retrieves the PNI-NPN slice related status information from MDE/NWDAF, i.e. analytics data specified in 3GPP TS 28.104 [21] and TS 23.288 [4].
4. The NSCE server retrieves the PLMN slice related performance information from MDE/NWDAF. The services of Nnwdaf_AnalyticsInfo service defined in clause 7.3 of TS 23.288 [4] and analytics data as specified in 3GPP TS 28.104 [21] can be utilized.
5. The NSCE server verifies and analyses analytics data of network slice instances that is received from MDE/NWDAF about both PNI-NPN and PLMN slices, then NSCE server makes consolidated performance report among different kinds of network slices in specific period of time/location zone.
6. The NSCE server sends the multiple slices related performance and analytics consolidated report response towards VAL server including application key performance indicator (such as end-to-end delay, throughput, etc. ) list and monitoring period. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3.1 General | The following information flows are specified for Network slice related performance and analytics monitoring:
- Network slice related performance and analytics monitoring job creation request and response
- Network slice related performance and analytics monitoring report subscription
- Network slice related performance and analytics monitoring report Notify
- Multiple slices related performance and analytics consolidated report request and response |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3.2 Network slice related performance and analytics monitoring job creation request and response | Table 9.7.3.2-1 and Table 9.7.3.2-2 describe information elements for the network slice related performance and analytics monitoring job creation request and response between the VAL server and the NSCE server.
Table 9.7.3.2-1: Network slice related performance and analytics monitoring job creation request
Information element
Status
Description
VAL information
M
The information of the VAL server
Performance Monitoring Request ID
M
Identifier of the performance and analytics monitoring job
Performance and analytics monitoring metrics
M
The information of performance and analytics monitoring
> VAL service identity
M
Identifier of the VAL service to be monitored
>PerfList
M
The list of performance to be monitored
>> PerfName
M
The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load.
> Network slice related Identifier(s)
O
Identifier(s) of the network slice to be monitored
>StartTime
M
The start time point of the performance and analytics monitoring
>EndTime
O
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
Table 9.7.3.2-2: Network slice related performance and analytics monitoring job creation response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics monitoring request
> Performance Monitoring Request ID
O
(see NOTE 1)
Identifier of the performance and analytics monitoring job
>StartTime
O
(see NOTE 1)
The start time point of the performance and analytics monitoring
>EndTime
O
(see NOTE 2)
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
>Cause
O
(see NOTE 3)
Indicates the cause of VAL performance and analytics monitoring 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: Shall be present if the result is failure and shall not be present otherwise. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3.3 Network slice related performance and analytics report subscription | Table 9.7.3.3-1 and 9.7.3.3-2 describe information elements for Network slice related performance and analytics report subscription from the NSCE server to the VAL server.
Table 9.7.3.3-1: Network slice related performance and analytics report subscription
Information element
Status
Description
VAL information
M
The information of the VAL server
>VAL server ID
M
The identifier of the VAL server
Report ID
M
Identifier of performance and analytics results the report
Report Information
M
The information of performance and analytics report retrieving
> VAL service identity
M
Identifier of the VAL service of which the performance and analytics results are required
> Network slice related Identifier(s)
O
Identifier(s) of the network slice
>StartTime
M
The start time point of the performance and analytics report
>EndTime
M
The end time point of the performance and analytics report
>Notification time interval
O
The time interval that the network slice related performance and analytics report are supposed to be notified
>PerfList
M
The list of performance to be reported
>>PerfName
M
The name of the performance to be reported
Table 9.7.3.3-2: Response of Network slice related performance and analytics report subscription
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics subscription
>Report ID
O
(see NOTE 1)
Identifier of the performance and analytics report Id
>Cause
O
(see NOTE 2)
Indicates the cause of VAL performance and analytics subscription 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3.4 Network slice related performance and analytics report Notify | Table 9.7.3.4-1 and 9.7.3.4-2 describe information elements for Network slice related performance and analytics report Notify from the NSCE server to the VAL server.
Table 9.7.3.4-1: Network slice related performance and analytics report Notify
Information element
Status
Description
VAL information
M
The information of the VAL server
>VAL server ID
M
The identifier of the VAL server
>Network slice related performance and analytics report
M
Network slice related performance and analytics report as defined in Table 9.7.3.4-2
Table 9.7.3.4-2: Network slice related performance and analytics report
Information element
Status
Description
Report ID
M
Identifier of the report
PerfResultFile
CM
(see NOTE 1)
PerfResultFile contains one or more PerfResult
>PerfResult
CM
Information element containing the VAL service identity or S-NSSAI followed by a list of result values for the aggregated or analyzed network slice related performance
>VAL service identity
M
Identifier of the VAL service of which the performance and analytics results are reported
> Network slice related Identifier(s)
O
Identifier(s) of the network slice
>ResultsValueList
List of ResultsValue
>>ResultsValue
M
Information element containing the perfName and perfValue.
>>>PerfName
M
The name of the performance to be reported
>>>PerfValue
M
The corresponding value of the monitored performance
Failure response
CM
(see NOTE 2)
Indicates that network slice related performance and analytics results reporting failed.
>Cause
CM
(see NOTE 2)
Indicates the cause of network slice related performance and analytics results report failure
NOTE 1: Information element shall be present when the network slice related performance and analytics results retrieving is successful.
NOTE 2: Information element shall be present when the network slice related performance and analytics results retrieving is failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.3.5 Multiple slices related performance and analytics consolidated report request and response | Table 9.7.3.x-1 and Table 9.7.3.x-2 describe information elements for the multiple slices related performance and analytics consolidated report request and response between the VAL server and the NSCE server.
Table 9.7.3.5-1: Multiple slices related performance and analytics consolidated report request
Information element
Status
Description
VAL information
M
The information of the VAL server
Performance Monitoring Request ID
M
Identifier of the performance and analytics monitoring
Performance and analytics monitoring metrics
M
The information of performance and analytics monitoring
> VAL service identity
M
Identifier of the VAL service to be monitored
>PerfList
M
The list of performance to be monitored
>> PerfName
M
The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load.
> Network slice related Identifier(s)
O
Identifier(s) of the network slice to be monitored
>StartTime
M
The start time point of the performance and analytics monitoring
>EndTime
M
The end time point of the performance and analytics monitoring.
> Report ID
M
Identifier of performance and analytics report.
Table 9.7.3.5-2: Multiple slices related performance and analytics consolidated report response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics monitoring request
>StartTime
O
(see NOTE 1)
The start time point of the performance and analytics monitoring
>EndTime
O
(see NOTE 1)
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
>Report ID
O
(see NOTE 1)
Identifier of the report
>VAL service identity
O
(see NOTE 1)
Identifier of the VAL service of which the performance and analytics results are reported
>>Network slice related Identifier
O
(see NOTE 1)
Identifier of the network slice. One VAL service can be offerred on one or more network slices
>>>ResultsValue
O
(see NOTE 1)
Information element containing the perfName and perfValue
>>>>PerfName
O
(see NOTE 1)
The name of the performance to be reported
>>>>PerfValue
O
(see NOTE 1)
The corresponding value of the monitored performance
>Cause
O
(see NOTE 2)
Indicates the cause of VAL performance and analytics monitoring request 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4.1 General | Table 9.7.4.1-1 and 9.7.4.1-2 illustrate the API for network slice related performance and analytics monitoring.
Table 9.7.4.1-1: SS_NSCE_PerfMonitoring API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_PerfMonitoring
Perf_Monitoring_Request
Request /Response
VAL server
Table 9.7.4.1-2 SS_NSCE_PerfResultReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE__PerfReportSubscription
Perf_ PerfReport_Subscription
Subscription/response
VAL Server
Table 9.7.4.1-3: SS_NSCE_PerfReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_PerfReporting
Perf_Report
Notify
VAL Server
Table 9.7.4.1-4: SS_NSCE_MultiSlicePerfReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_MultiSlicePerfReport
Multi_Slice_Perf_Report
Request /Response
VAL Server |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4.2 SS_NSCE_PerfMonitoring API | API operation name: Perf_Monitoring
Description: The consumer requests to monitor network slice related performance and analytics.
Known Consumers: VAL server.
Inputs: See table 9.7.3.2-1.
Outputs: See table 9.7.2.2-2.
See clause 9.7.2.1 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4.3 SS_NSCE_PerfReportSubscription API | API operation name: Perf_Result_Reporting
Description: The consumer requests to report network slice related performance and analytics.
Known Consumers: VAL server.
Inputs: See table 9.7.3.3-1.
Outputs: See table 9.7.3.3-2.
See clause 9.7.2.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4.4 SS_NSCE_PerfReport API | API operation name: Perf_ Report
Description: The consumer get notify of network slice related performance and analytics report.
Known Consumers: VAL server.
Inputs: See table 9.7.3.4-1.
Outputs: See table 9.7.3.4-2.
See clause 9.7.2.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.7.4.5 SS_NSCE_MultiSlicePerfReport API | API operation name: Multi_Slice_Perf_Report
Description: The consumer requests to get multiple slices related performance and analytics consolidated report.
Known Consumers: VAL server.
Inputs: See table 9.7.3.5-1.
Outputs: See table 9.7.3.5-2.
See clause 9.7.2.3 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8 Information collection from NSCE server(s) | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.1 General | The collected information by NSCE server could be exposed to other NSCE server(s) to optimize network resource allocation, based on the agreement among the NSCE servers. Then the NSCE server providing network slice related information acts as the producer, while the NSCE server obtaining network slice related information is the consumer. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.2.1 Information collection from NSCE server(s) subscribe request and response | Pre-condition:
1. The producer NSCE server #2 has agreement with consumer NSCE server #1 to provide the collected slice information.
Figure 9.8.2.1-1: Information collection from NSCE server(s) subscribe request and response
1. The NSCE server#1 sends out the information collection subscribe request with expected period and interested slice ID, e.g., List of SNSSAI. This step could be done by pre-configuration.
2. The NSCE server #2 shall check if the NSCE server #1 is authorized to get the network slice information.
3. After authentication, the NSCE server #2 collects slice information as defined in clause 9.7.2.1 step3, step4.
NOTE: When the producer NCSE server is edge NSCE server, only local information is collected and provided.
4. The NSCE server #2 sends collected slice information to NSCE server #1.
5. The NSCE server #1 may process the collected slice information (such as information aggregation), if needed. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.2.2 Information collection from NSCE server(s) Notify | Figure 9.8.2.2-1: Information collection from NSCE server(s) Notify
1. Once the reporting period is reached or the threshold is crossed, the NSCE server #2 sends information collection notify to NSCE server #1. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.3.1 General | The following information flows are specified for Information collection from NSCE server(s):
- Information collection from NSCE server(s) subscribe request, response and notify; |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.3.2 Information collection from NSCE server(s) subscribe request | Table 9.8.3.2-1 describes information elements for the Information collection from NSCE server(s) subscribe request from the consumer NSCE server to the producer NSCE server(s).
Table 9.8.3.2-1: Information collection from NSCE server(s) subscribe request
Information element
Status
Description
Requester Identifier
M
Unique identifier of the requester (i.e. NSCE server ID).
Security credentials
M
Security credentials resulting from a successful authorization for the NSCE service.
Notification Target Address
O
The Notification Target Address (e.g. URL) where the notifications destined for the requester should be sent to.
List of S-NSSAI(s)
M
Identifier of the interested network slice
>QoS type indicator
O
QoS metric type including latency, throughput, jitter, etc.
>Threshold
O
Threshold of QoS 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 subscription |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.3.3 Information collection from NSCE server(s) subscribe response | The information elements specified in the Table 9.8.3.3-1 is used for the Information collection from NSCE server(s) subscribe response sent from the producer NSCE server to the consumer NSCE server.
Table 9.8.3.3-1: Information collection from NSCE server(s) subscribe Response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics subscription.
> Subscription ID
O
(see NOTE 1)
Subscription identifier corresponding to the subscription.
>Network slice related performance and analytics report
O
(see NOTE 2)
Network slice related performance and analytics report as defined in Table 9.7.3.4-2
> Cause
O
(see NOTE 3)
Indicates the cause of 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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.3.4 Information collection from NSCE server(s) notify | The information elements specified in Table 9.8.3.4-1 are used for the information collection from NSCE server(s) notify sent from the producer NSCE server to the consumer NSCE server.
Table 9.8.3.4-1: Information collection from NSCE server(s) Notify
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
>Network slice related performance and analytics report
M
Network slice performance and analytics (i.e. slice load) with network slice identifier(i.e. S-NSSAI) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.4.1 General | Table 9.8.4.1-1 illustrates the API for information collection from NSCE server(s).
Table 9.8.4.1-1: API for Information collection from NSCE server(s)
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_InfoCollection
Subscribe
Subscribe/Response
NSCE server
Notify
Notify
NSCE server |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.4.2 SS_NSCE_InfoCollection_Subscribe operation | API operation name: InfoCollection_Subscribe
Description: The consumer subscribes for Information collection from NSCE server(s).
Inputs: See clause 9.8.3.2.
Outputs: See clause 9.8.3.3.
See clause 9.8.2.1 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.8.4.3 SS_NSCE_InfoCollection_Notify operation | API operation name: InfoCollection_Notify
Description: The consumer is notified with result of information collection from NSCE server(s).
Inputs: See clause 9.8.3.4
Outputs: None
See clause 9.8.2.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9 Predictive slice modification in edge based NSCE deployments | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.1 General | In this feature, the NSCE server initially receives an expected/predicted UE location/mobility change request outside an EDN service area for one or more UEs within the VAL application session (e.g. such session can be an indirect V2V session or a multiplayer gaming session). Then, the source NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target EDN. Thereafter, NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change) e.g. a slice subnet resource adaptation to allow for optimizing the application performance at the target area. Based on this decision/recommendation, it provides the action to the OAM and supports the re-mapping of NSCE server for the NSCE client proactively, before UE mobility happens. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.2.1 Procedures on predictive slice modification in edge based NSCE deployments | In the procedure shown in Figure 9.9.2.1-1, a mechanism is provided to allow for slice modification when a vertical application of single or group of VAL UEs migrates (or is expected/predicted to migrate) to a different EDN supported by different NSCE server.
Pre-conditions:
1. The VAL server has subscribed to the network slice capability enablement server
2. The VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to NSCE server#1 (S-NSCE server).
3. The S-NSCE server has already discovered the T-NSCE server and its area of coverage.
4. The VAL server is subscribed to and received prediction of UE location change.
Figure 9.9.2.1-1: Support for predictive slice modification in distributed NSCE server deployments
1. The VAL server sends to S-NSCE server an application service continuity requirement request due to predicted/expected UE or group UE mobility to a target service area covered by a different EDN.
NOTE: Such UE predicted mobility at the VAL server can be based on UE mobility analytics received by NWDAF or can be predicted by the VAL layer (VAL server or VAL UE).
2. S-NSCE server sends an application service continuity requirement response to the VAL server as positive or negative acknowledgement.
3. S-NSCE server determines to query the underlying 3GPP system on the slice availability and conditions at the target service area (based on step 1 requirement). Such query may be in form of a request/response and include:
a. S-NSCE server interacting with 5GC to query the UE specific information (location, UE connection capabilities) as well as network conditions (network monitoring from NEF) and/or slice related analytics on the slice load (from NWDAF as specified in TS 23.288 [4]).
b. S-NSCE server may also interact with OAM to query on the target slice availability and the up-to-date configured slice parameters e.g. slice RRM policies, modification of the NSI/NSSI resources (see TS 28.531 [8], 5.1.12) at the target service area and measurements for the slice at the target area.
4. S-NSCE server evaluates whether new NSCE service area supports slice #1 and if slice #1 offers similar performance in target area.
5. If the current slice doesn't fulfil these requirements, S-NSCE sends to the T-NSCE server (covering the target area) a service continuity negotiation request (including the VAL application service continuity requirement and optionally a proposed action) to negotiate on the trigger action.
6. T-NSCE server determines the need for a slice lifecycle change at the target area and translates this to a trigger action. This trigger action can be based on the proposed action in step 5 and can be a requested slice modification or the slice #1 creation/instantiation at the target area (this may happen if a group of UEs are moving to the target area and use slice #1, so it may be beneficial to create slice #1 at the target area).
7. T-NSCE server sends to the S-NSCE server a service continuity negotiation response including the determined trigger action.
8. The S- or T-NSCE server may send the trigger action as a slice modification trigger request to the slice provisioning MnS producer at OAM (e.g. slice modification for network slice) to extend slice availability to the target service area based on the expected/predicted VAL UE or VAL group mobility. As response to the trigger action, the provisioning MnS producer provides a slice modification trigger response to the corresponding NSCE server with a positive or negative result.
9. After the slice lifecycle change execution (based on the indication in step 5), the S-NSCE server sends a notification to the VAL server and optionally to the VAL client via S-NSCE client
10. If the NSCE client needs to be remapped to different NSCE server (due to the expected change of UE location), the NSCE client establishes a new connection with T-NSCE and terminates the one with S-NSCE (in case of subscription-based interaction), or in case of request-based interaction, it updates the mapping at the client side, and maintains the new NSCE server address / ID for the target NSCE area. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3 Information flows |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.