hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
4
1.47k
content
stringlengths
0
6.67M
a89a0ce5789287ec186d94e36b976f2e
23.435
7.3.3 Network slice capability enablement client
The network slice capability enablement client functional entity acts as the application client for the slice enablement. The network slice capability enablement client interacts with the network slice capability enablement server to trigger network slice related operations such as adaptation due to an application requirement change. This trigger may be due to an application QoS requirement change, a service operation change. The NSCE client may receive a network slice / DNN re-mapping notification from the NSCE server. The NSCE client may optionally notify the VAL client on the network slice / DNN re-mapping.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4 Reference points description
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.1 General
The reference points for the functional model for network slice capability enablement are described in the following subclauses.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.2 NSCE-UU
The interactions related to network slice capability enablement functions between the network slice capability enablement server and the network slice capability enablement client are supported by NSCE-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.501 [14].
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.3 NSCE-C
The interactions related to network slice capability enablement functions between the VAL client(s) and the network slice capability enablement client within a VAL UE are supported by the NSCE-C reference point. The NSCE client may receive application requirement change, application client information (such as its KQI) over NSCE-C. Further, the NSCE client may provide a notification on the network slice adaptation upon successful adaptation of the slice to application mapping.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.4 NSCE-S
The interactions related to network slice capability enablement functions between the VAL server(s) and the network slice capability enablement server are supported by the NSCE-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [3].
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.5 N33
The reference point N33 supports the interactions between the network slice capability enablement server and the NEF and is specified in 3GPP TS 23.501 [14]. N33 is used for the network-based mechanism for slice re-mapping, where NSCE server acting as AF influences the URSP rules for the application traffic per UE by providing a guidance on the route selection parameters (including the S-NSSAI and DNN mapping), as specified in 3GPP TS 23.502 [12] clause 4.15.6.10, 3GPP TS 23.503 [17] clause 6.6.2.2, 3GPP TS 23.548 [18] clause 6.2.4.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.6 NSCE-E
The interactions between the NSCE servers are generically referred to as NSCE-E reference point. This reference point supports information collection from other NSCE servers as defined in clause 9.8, Service continuity negotiation as defined in clause 9.9.2.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.7 NSCE-OAM
The interface between the NSCE server and the OAM system are generically referred to as NSCE-OAM reference point. This reference point supports provisioning of management service as defined in clause 6.1, 3GPP TS 28.531 [8]. NOTE: The NSCE-OAM reference point is out of scope of this specification, and is defined by SA5.
a89a0ce5789287ec186d94e36b976f2e
23.435
7.4.8 SEAL-X
The interactions between the NSCE servers and other SEAL servers are generically referred to as SEAL‑X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in 3GPP TS 23.434 [2].
a89a0ce5789287ec186d94e36b976f2e
23.435
8 Identities and commonly used values
a89a0ce5789287ec186d94e36b976f2e
23.435
8.1 General
The common identities for SEAL refer to TS 23.434[2]. The following clauses list the additional identities and commonly used values for Network Slice Capability Enablement.
a89a0ce5789287ec186d94e36b976f2e
23.435
8.2 NSCE server ID
The NSCE server ID uniquely identifies the Network Slice Capability enablement server.
a89a0ce5789287ec186d94e36b976f2e
23.435
8.3 NSCE client ID
The Network Slice Capability enablement client ID identifies a particular NSCE client.
a89a0ce5789287ec186d94e36b976f2e
23.435
8.4 Network Slice related Identifier
The network slice related identifier identifies the network slice, which is mapped to the VAL application. The identifier of the network slice is either S-NSSAI defined in 5.15.2.1 TS 23.501[16], or External Network Slice Information (ENSI) defined in TS 33.501[14]. Based on the operator’s policy, if the service applies for a certain network slice instance, the identifier of Network Slice instance is used, i.e. NSI ID as defined in TS 23.501 or ENSI. If used, the NSI ID is associated with S-NSSAI.
a89a0ce5789287ec186d94e36b976f2e
23.435
8.5 Slice coverage area
The slice coverage area is the area where the network slice is available in the whole PLMN or in one or more Tracking Areas of the PLMN. The slice coverage area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geographical coordinates) or both.
a89a0ce5789287ec186d94e36b976f2e
23.435
8.6 NSCE service area
The NSCE service area is the area where the Network Slice Capability Enablement server owner provides its services. It is equal to the collection of coverage area of slices it can enable. The NSCE service area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geographical coordinates) or both. NOTE: The NSCE server service area shall not smaller than the collection of slice(s) coverage area(s) the NSCE server can enable.
a89a0ce5789287ec186d94e36b976f2e
23.435
9 Procedures and information flows
a89a0ce5789287ec186d94e36b976f2e
23.435
9.1 General
a89a0ce5789287ec186d94e36b976f2e
23.435
9.1.1 Common Information Elements
9.1.1.1 General This clause provides descriptions for Information Elements which are commonly used in several procedures.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.1.1.2 Service requirement
The service requirement indicates the VAL application requirements pertaining to the slice(s). Table 9.1.1.2-1: Service requirement Information element Status Description VAL service ID M The identification of the application ID related with the service requirement. VAL service KPIs O KPIs including application QoS requirements (latency, error rates, throughput, jitter,..) Network slice related identifier(s) M Identifier of network slice for which the request applies Application layer Service Profile O The properties of network slice related requirement. If Service Profile is known by the VAL server, it can be provided to the NSCE server. The GST defined by GSMA (see clause 2.2 in [5]) and the performance requirements defined in clause 7 TS 22.261 [6] are all considered as input for it. Area of interest O The service area for which the requirement applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
a89a0ce5789287ec186d94e36b976f2e
23.435
9.2 Registration
For registration of the VAL server to be a recognized user of the CAPIF, the VAL server triggers the CAPIF Onboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.1. The NSCE server could be deployed with CAPIF core function. NOTE: What additional information is needed, and if needed, whether it is specific for NSCE service or generally applicable for CAPIF is not specified in this release. For de-registration of the VAL server, the VAL server triggers the CAPIF Offboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.2.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3 Slice API configuration and translation
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.1 General
This functionality is a service related to the translation of the service API as invoked by the end applications to slice APIs based on the API configuration and application to slice mapping. Slice APIs can be defined as customized/tailored sets of service APIs (which can be either NEF northbound APIs or OAM provided APIs or enabler layer/SEAL provided APIs) and can be mapped to particular slice instances. The slice APIs can be a bundled or combined API comprising of different types of APIs, which will be used to expose the telco (5GS/SEAL)-provided services as needed by the applications of the slice customer. Each slice API may be configured per network slice instance.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2 Procedure
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2.1 Procedures on slice API configuration
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2.1.1 General
In the Initial Configuration procedure, the VAL server initially provides an application requirement to enabler server including the service KPIs and the subscribed/preferred slices. Then, the slice enabler configures the mapping of the VAL application to a slice API which is a combination/bundling of northbound APIs (from both management and control plane). In particular, a slice API consists of telco-provided/platform dependent service APIs (e.g., NEF, OAM, SEAL, etc), and provides an abstraction/simplification on top of them. The VAL server-initiated Configuration Update procedure covers the scenario where a trigger event occurs (e.g., QoS degradation, slice load) and the mapping configuration or the slice API configuration needed to be changed. In this scenario, the slice enabler updates the configuration of the API and provides a notification to the VAL server. These two procedures for the initial configuration and the configuration update are covered in 9.3.2.1 and 9.3.2.2 respectively.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2.1.2 Initial Configuration
Figure 9.3.2.1.2-1 illustrates the procedure of the initial slice API configuration. Pre-conditions: 1. The VAL server has registered to receive NSCE services. Figure 9.3.2.1.2-1: Initial Slice API configuration 1. The VAL server sends a VAL application requirement request to the NSCE server. If CAPIF is used, the NSCE server acts as AEF, and the authorization is obtained from CCF. NOTE: The NSCE server provided service can serve any slice. 2. The NSCE server maps the VAL application requirement to a slice API which includes a list of APIs which is needed to be consumed as part of this service capability exposure. The NSCE server may also store the mapping of the slice API to the service API list and per service API information (e.g. data encoding, transport technology, API protocol and versions) 3. The NSCE server registers to consume the corresponding APIs from the 5GS (NEF and OAM) and SEAL service producers. The NSCE server registers to the following: - to consume NEF monitoring events as specified in 3GPP TS 29.522 clause 5 e.g., network monitoring, slice status, analytics exposure, etc - to consume PM services and KPI monitoring from OAM - to consume SEAL services based on 3GPP TS 23.434 If CAPIF is used, the subscription/registration requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. The preferred network slice related identifier received in step 1 is used by the NSCE server in requesting CCF authorization to consume the service provided by 5GS/SEAL. 4. The NSCE server sends a VAL application requirement response to notify on the result of the request and indicate whether the configuration of slice API is possible or not. 5. The NSCE server sends the slice API information notification to the VAL server.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2.1.3 VAL server-initiated Configuration Update
Figure 9.3.2.1.3-1 illustrates the procedure of the slice API configuration updated based on a trigger event. Pre-conditions: 1. Initial configuration of the slice API has been completed successfully. 2. A trigger event, which may result the need of a slice configuration change, is captured by the VAL server (application server relocation to different EDN/DN, UE mobility to different EDN, application change of behaviour). Figure 9.3.2.1.3-1: Slice API configuration update 1. The VAL server sends a VAL server-initiated configuration update request to the NSCE server. 2. The NSCE server processes the trigger event and checks the feasibility of such change and updates the mapping of service APIs to the slice APIs. One criterion for the update of the mapping is, if possible, to avoid changing the slice API configuration, which can be achieved by the re-mapping of the underlying service APIs 3. The NSCE server updates the subscription/registration to the underlying 5GS and SEAL service producers, if an update on the service APIs (e.g., NEF APIs, SEAL APIs, OAM provided APIs) is needed. 4. The NSCE server sends a VAL server-initiated configuration update response, containing the new slice API information, if an update has been carried out by the NSCE server.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.2.2 Procedure on slice API translation
This procedure follows the 9.3.2.1 and aims to describe how the slice API invocation request is translated to service API invocations after the slice API configuration mapping. In this procedure, the NSCE server initially receives a slice API invocation request from the vertical application. Then, the NSCE server fetches the service APIs to be invoked based on the slice API configuration and performs invocation requests to the corresponding service API providers. Figure 9.3.2.2-1 illustrates the procedure of the slice API translation based on the initial configuration. Pre-conditions: 1. The VAL server has registered to receive NSCE services. 2. The slice API mapping to the VAL server has been performed based on 9.3.2.1.2 step 2 and the slice API information is provided to the VAL server based on 9.3.2.1.2 step 5. Figure 9.3.2.2-1: Slice API translation 1. The VAL server sends a slice API invocation request to the NSCE server 2. The NSCE server checks that the user is authenticated and authorized to perform the slice API invocation and maps the requested slice API to a service APIs. If CAPIF is used, the NSCE server acts as AEF, and the authorization is obtained from CCF. NOTE: The NSCE server provided service can serve any slice. 3. The NSCE server generates a trigger for service API invocation requests to all the service APIs within the slice API. 4. The NSCE server performs the corresponding service API invocation procedures based on CAPIF or via performing requests to the corresponding service API providers, which are mapped to the slice API. If CAPIF is used, the requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. The requested network slice related identifier received in step 1 is used by the NSCE server in requesting CCF authorization to consume the service provided by 5GS/SEAL. 5. The NSCE server sends a slice API invocation response to the VAL server, based on the result of the service API invocation response(s) of step 4. 9.3. 3 Information flows
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.1 General
The following information elements are specified for slice API translation and configuration specified in clause 9.3.2.1 and 9.3.2.2.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.2 VAL application requirement request
Table 9.3.3.2-1 describes information elements for the VAL application requirement request from the VAL server to the NSCE server. This request provides the service requirements / KPIs, the capability exposure requirements and a preferred/subscribed slice identification (e.g., S-NSSAI or ENSI). Table 9.3.3.2-1: VAL application requirement request Information element Status Description VAL server ID M The identifier of the VAL server List of service requirement(s) M The VAL application requirements pertaining to the slice(s) as defined in table 9.1.1.1-1 Time validity O The time validity of the request NOTE: One of this shall be present
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.3 VAL application requirement response
Table 9.3.3.3-1 describes information elements for the VAL application requirement response from the NSCE server to the VAL server. Table 9.3.3.3-1: VAL application requirement response Information element Status Description Result M Indicates the success or failure of the VAL application requirements request. >Cause O (see NOTE) Indicates the cause of failure NOTE : May only be present if the result is failure.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.4 Slice API information notify
Table 9.3.3.4-1 describes information elements for the Slice API information notification from the NSCE server to the VAL server. The Slice API information notification is used by NSCE server to send Slice API information to VAL server in the Initial Configuration and Configuration Update procedures. Table 9.3.3.4-1: Slice API information notify Information element Status Description Slice API info M The information for the configured slice API
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.5 VAL server-initiated configuration update request
Table 9.3.3.5-1 describes information elements of the VAL server-initiated configuration update request sent by the VAL server to the NSCE server. Table 9.3.3.5-1: VAL server-initiated configuration update request Information element Status Description VAL server ID M The identifier of the VAL server Network slice ID O Identifier of the network slice for which the API configuration update is requested Trigger Event Details M The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be: • the UE mobility to a different service area (outside the original area of interest), • application server migration to different edge/cloud platform, • service API unavailability, • VAL application QoS requirements change
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.6 VAL server-initiated configuration update response
Table 9.3.3.6-1 describes information elements of the VAL server-initiated configuration update response sent by the NSCE server to the VAL server. Table 9.3.3.6-1: VAL server-initiated configuration update response Information element Status Description Configuration changed O (see NOTE) Indicates that the slice configuration has been changed. > Updated slice API information M The information for the updated slice API Configuration not changed O (see NOTE) The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be > Cause M Indicates the reason for not changing the slice configuration. The reason may be that no change was needed, failure of changing in 5GS/SEAL or other (e.g. server internal error). NOTE: Only one of these IEs is present in the message.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.7 slice API invocation request
Table 9.3.3.7-1 describes information elements for the slice API invocation request from the VAL server to the NSCE server. Table 9.3.3.7-1: slice API invocation request Information element Status Description VAL server ID M The identifier of the VAL server Authorization information O The authorization information obtained before initiating the slice API invocation request Slice API identification M The identification information of the slice API for which invocation is requested. The slice API identification is part of the specific slice API invocation request.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.3.8 slice API invocation response
Table 9.3.3.8-1 describes information elements for the slice API invocation response from the NSCE server to the VAL server. Table 9.3.3.8-1: slice API invocation response Information element Status Description Result M Indicates the success or failure of slice API invocation request. >Cause O (see NOTE) Indicates the cause of failure NOTE: May only be present if the result is failure.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4 APIs
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.1 General
Table 9.3.4.1-1 illustrates the NSCE APIs for the slice API configuration and translation feature. Table 9.3.4.1-1: List of APIs for slice API configuration and translation feature API Name API Operations Known Consumer(s) Communication Type SS_NSCE_SliceApiConfiguration Slice_API_configuration VAL server Request /Response Slice_API_configuration_update VAL server Request /Response Slice_API_information_notify VAL server Notify SS_NSCE_Slice_ApiInvocation Slice_API_invocation VAL server Request /Response
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.2 SS_NSCE_SliceApiConfiguration API
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.2.1 General
API description: This API enables the VAL server to communicate with the NSCE server for the initial configuration of the slice API and possible subsequent slice API configuration update(s).
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.2.2 SS_NSCE_Slice_API_configuration
API operation name: Slice_API_configuration Description: Providing for VAL_Application_requirement to the NSCE server. Known Consumers: VAL server Inputs: See subclause 9.3.3.2 Outputs: See subclause 9.3.3.3
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.2.3 SS_NSCE_Slice_API_configuration_update
API operation name: Slice_API_configuration_update Description: VAL server providing trigger event information to the NSCE server that may potentially invoke slice API configuration change(s). Known Consumers: VAL server Inputs: See subclause 9.3.3.5 Outputs: See subclause 9.3.3.6
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.2.4 SS_NSCE_Slice_API_information_notify
API operation name: Slice_API_information_notify Description: Notifying the slice API information Known Consumers: VAL server Inputs: See subclause 9.3.3.4 Outputs: None
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.3 SS_NSCE_Slice_ApiInvocation API
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.3.1 General
API description: This API enables the VAL server to communicate with the NSCE server for invoking the slice API over NSCE-S.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.3.4.3.2 SS_NSCE_Slice_API_invocation
API operation name: Slice_API_invocation Description: Requesting slice API invocation from NSCE server. Known Consumers: VAL server Inputs: See subclause 9.3.3.7 Outputs: See subclause 9.3.3.8
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4 Application layer network slice lifecycle management
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.1 General
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.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.2 Procedure
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.2.1 Procedures on slice lifecycle management
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: 1. The NSCE server has authenticated and authorized to the capabilities to collect current network slice from 5GS. 2. The NSCE server has authenticated and authorized to the capabilities trigger the network slice LCM operations. 3. There is signed contract for LCM between the entities using VAL server and entities using NSCE. Figure 9.4.2.1-1: Application layer network slice lifecycle management 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. 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. 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. 3a. The network slice status could be collected through subscribing or requesting to 5GS. List of network slice status parameters to be collected are: - 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. - Performance metric in the performance data file from OAM as defined in clause 11.3 of TS 28.532 [7]. 3b. 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. 4. Once authenticated and authorized, the NSCE server sends the AppLayer-NS-LCM response to the VAL server. 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 [8]. 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. 7. Optionally, the VAL server sends the response to NSCE server. 8. Based on decision made by VAL server or NSCE server, the NSCE server sends the network slice LCM request to the OAM. 9. According to the corresponding operation(s) result, the NSCE server sends the response to the VAL server.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3 Information flows
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.1 General
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;
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.2 Application layer network slice lifecycle management subscribe request
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. Table 9.4.3.2-1: AppLayer-NS-LCM Subscribe 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: - The Network Slice load exceeds the threshold. - The collected Network Slice performance exceeds the threshold; - The collected QoE exceeds the threshold. 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.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.3 Application layer network slice lifecycle management response
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. Table 9.4.3.3-1: AppLayer-NS-LCM Response 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.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.4 Application layer network slice lifecycle management notification
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. Table 9.4.3.4-1: AppLayer-NS-LCM Notification 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.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.5 QoE metrics subscribe
Table 9.4.3.5-1 describes information elements for the QoE metrics subscribe from the NSCE server to the VAL server. Table 9.4.3.5-1: QoE metrics Subscribe 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
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.6 QoE metrics response
Table 9.4.3.6-1 describes the information elements for the QoE metrics response from the VAL server to the NSCE server. Table 9.4.3.6-1: QoE metrics Response Information element Status Description Result M Indicates the success or failure of the QoE metrics request. > Subscription ID O (see NOTE1) Subscription identifier corresponding to the subscription. >QoE metrics report O (see NOTE2) List of result values for the observed or computed QoE metrics value if the immediate reporting is needed. > Cause O (see NOTE3) 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.
a89a0ce5789287ec186d94e36b976f2e
23.435
9.4.3.7 QoE metrics notification
Table 9.4.3.7-1 describes the information elements for the QoE metrics notification from the VAL server to the NSCE server. Table 9.4.3.7-1: QoE metrics Notify 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.
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.