hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.1 General | The following information flows are specified for the predictive slice modification support based on 9.9.2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.2 Application service continuity requirement request | Table 9.9.3.2-1 describes information elements for the Application service continuity requirement request from the VAL server to the NSCE server.
Table 9.9.3.2-1: Application service continuity requirement request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
Security credentials
M
Security credentials resulting from a successful authorization.
VAL service ID
M
The identifier of the VAL service for which the requirement request applies
VAL UE ID list
O
The list of VAL UE IDs for which the requirement request applies
Service Continuity Requirement
M
The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area.
Slice identifier
O
The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server
Target Service Area
O
The target area can be represented as the geographical coordinates / set of waypoints outside the original service area, where the VAL application/ UE(s) is expected or predicted to move.
Application QoS requirements
O
The QoS requirements / KPIs for the VAL service |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.3 Application service continuity requirement response | Table 9.9.3.3-1 describes information elements for the Application service continuity requirement response from the NSCE server to the VAL server.
Table 9.9.3.3-1: Application service continuity requirement response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.4 Service continuity negotiation request | Table 9.9.3.4-1 describes information elements for the service continuity negotiation request from the S-NSCE server to the T-NSCE server.
Table 9.9.3.4-1: service continuity negotiation request
Information element
Status
Description
S-NSCE server ID
M
The identifier of the source NSCE server
VAL service ID
M
The identifier of the VAL service for which the request applies
VAL UE ID list
O
The list of VAL UE IDs for which the request applies
Service Continuity Requirement
M
The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area.
Proposed Trigger Action
O
The proposed slice licecycle change for the target VAL UE or VAL application
Slice identifier
M
The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server
Application QoS requirements
O
The QoS requirements / KPIs for the VAL service |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.5 Service continuity negotiation response | Table 9.9.3.5-1 describes information elements for the service continuity negotiation response from the T-NSCE server to the S-NSCE server.
Table 9.9.3.5-1: service continuity negotiation response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement)
Trigger Action
O
The determined trigger action which can be the slice licecycle change for the target VAL UE or VAL application |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.3.6 Slice modification notify | Table 9.9.3.6-1 describes information elements for the slice modification notify message from the NSCE server to the VAL server or the VAL client (via NSCE client).
Table 9.9.4.6-1: slice modification notify
Information element
Status
Description
VAL service ID
M
The identifier of the VAL application which is expected to be impacted by the slice modification
VAL UE ID list
O
The identifiers of the VAL UEs which are expected to be impacted by the slice modification
Slice identifier
M
The slice identifier (S-NSSAI, NSI ID or ENSI) which is expected or predicted to modify to extend slice availability to the target service area
Target NSCE server ID and address
M
The identifier and address of the target NSCE server
Target Service Area
M
The target area can be represented as the edge service area (including the target DNN/DNAI) or the topological area (e.g. list of cells/TAs) for which the slice modification applies. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.1 General | Table 9.9.4.1-1 illustrates the NSCE APIs for the predictive slice modification support feature.
Table 9.9.4.1-1: List of APIs for the predictive slice modification support feature
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_Service_Continuity_Requirement
Service_Continuity_Requirement
VAL server
Request / Response
SS_NSCE_Service_Continuity_Negotiation
Service_Continuity_Negotiation
NSCE server
Request / Response
SS_NSCE_Slice_Modification_Notify
Slice_Modification_Notify
VAL server or VAL client
Notify |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.2 SS_NSCE_Service_Continuity_Requirement | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.2.1 General | API description: This API enables the VAL server to communicate with the network slice capability enablement server for requesting a service continuity requirement over NSCE-S. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.2.2 Service_Continuity_Requirement | API operation name: Service_Continuity_Requirement
Description: Providing for Service_Continuity_Requirement to the NSCE server and receiving a response / result.
Known Consumers: VAL server.
Inputs: See table 9.9.3.2-1
Outputs: See table 9.9.3.3-1 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.3 SS_NSCE_Service_Continuity_Negotiation | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.3.1 General | API description: This API enables the S-NSCE server to communicate with the T-SNCE server for requesting a service continuity negotiation over NSCE-X. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.3.2 Service_Continuity_Negotiation | API operation name: Service_Continuity_ Negotiation
Description: Providing for Service_Continuity_ Negotiation to the T-NSCE server and receiving a response / result.
Known Consumers: S-NSCE server.
Inputs: See table 9.9.3.4-1
Outputs: See table 9.9.3.5-1 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.4 SS_NSCE_Slice_Modification_Notify | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.4.1 General | API description: This API enables the network slice capability enablement server to communicate with the VAL server or VAL UE (NSCE client or VAL client) for notifying the slice modification to extend to the target service area. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.9.4.4.2 Slice_Modification_Notify | API operation name: Slice_Modification_Notify
Description: Notifying about the slice modification to extend to the target area.
Known Consumers: VAL server.
Inputs: See table 9.9.3.6-1
Outputs: None |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10 Multiple slices coordinated resource optimization | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.1 General | Based on preferred QoS request from the vertical applications, the performance monitoring of multiple slices of one network (PNI-NPN slice and PLMN slice) and resource adjustment between different slices can be made to realize optimized and efficient resource usage. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.2.1 Procedure on multiple slices coordinated resource optimization | Figure 9.10.2.1-1 illustrates the procedure of multiple slices coordinated resource optimization 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.
Figure 9.10.2.1-1: Multiple slices coordinated resource optimization process
1. The VAL server initiates multiple slices coordinated resource optimization request towards the NSCE server. The request includes VAL server ID, VAL service ID. The message also includes preferred optimization zone.
2. Upon receiving the request from the VAL server to make the network slice resource optimization, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized to send multiple slices coordinated resource optimization request, the NSCE server replies with failure response.
3. The NSCE server makes mapping from VAL service ID that received from VAL server to slice identities (S-NSSAIs allocated in multiple networks) and retrieves the network slice related status information from 5GC or OAM of PLMN for PNI-NPN slices, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11].
4. The NSCE server retrieves the network slice related status information for PLMN from 5GC or OAM of PLMN networks for PLMN slices, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11]. The PLMN operator can choose to deploy NSCE-Server acting as single entry of PLMN capability exposure which can be optional.
5. The NSCE server verifies and analyses status data of network slices instance as well as network slice performance monitoring response (optional), then NSCE server makes resource optimization (e.g. shared radio resources, etc.) decision among different kinds of slices in specific location zone.
6-7. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [8] to PNI-NPN slice. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s) and sends LCM response including slice resource adjustment result.
8-9. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [8] to PLMN slice. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s) and sends LCM response including slice resource adjustment result. The PLMN operator can choose to deploy NSCE-S acting as single entry of PLMN capability exposure which can be optional.
10. The NSCE server sends the multiple slices coordinated resource optimization response towards VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.3.1 General | The following information flows are specified:
- Multiple slices coordinated resource optimization request and response. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.3.2 Multiple slices coordinated resource optimization request | Table 9.10.3.2-1 describes information elements for the multiple slices coordinated resource optimization request from the VAL server to the NSCE server.
Table 9.10.3.2-1: Multiple slices coordinated resource optimization 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.
VAL service identity
M
Identifier of the VAL service application to be monitored.
Optimization Zone
O
The preferred location area of the performance monitoring and optimization.
Requested S-NSSAI(s)
O
Indication of the S-NSSAI(s) which are requested. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.3.3 Multiple slices coordinated resource optimization response | Table 9.10.3.3-1 describes the information elements for the multiple slices coordinated resource optimization response from the NSCE server to the VAL server.
Table 9.10.3.3-1: Multiple slices coordinated resource optimization response
Information element
Status
Description
Result
M
Indicates the success or failure of the multiple slices resource optimization request.
> VAL service identity
O
(see NOTE 1)
Identifier of the VAL service application to be monitored.
> Cause
O
(see NOTE 2)
Indicates the cause of multiple slices resource optimization 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.10.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.4.1 General | Table 9.10.4.1-1 illustrates the API for multiple slices coordinated resource optimization.
Table 9.10.4.1-1: Multiple slices coordinated resource optimization
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_MultiSlices_Optimization
MultiSlices_Optimization
VAL server
Request /Response |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.10.4.2 SS_NSCE_MultiSlices_Optimization operation | API operation name: SS_NSCE_MultiSlices_Optimization_Request
Description: The consumer subscribes for multiple slices coordinated resource optimization .
Inputs: See clause 9.10.3.2.
Outputs: See clause 9.10.3.3.
See clause 9.10.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11 Network slice adaptation for VAL application | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.1 General | This subclause describes the procedure for network slice adaptation at the Network Slice Capability Enablement (NSCE) server, based on a request from a VAL server to adapt the network slice for the VAL application. This request is handled between the NSCE server and the NSCE client per each VAL UE of the VAL application. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS (denoted in clause 9.11.2.1 as network-based mechanism). |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.2 Procedures | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.2.1 Procedure for VAL server-triggered and network-based network slice adaptation for VAL application - request and response model | Figure 9.11.2.1-1 illustrates the VAL server-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Figure 9.11.2.1-1: Network slice adaptation for VAL application
1. The VAL server sends a network slice adaptation request to the NSCE server for the VAL application (and the VAL UEs within the VAL application). This request may be in the form of exact requested network slice (and optionally DNN) for all the VAL UEs of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The request optionally includes the adaptation threshold of network slice adaptation as defined in Table 9.11.3.1-1.
2. [Optional]NSCE server collects the network slice status information, including network slice performance measurements in clause 5.1.1.1, clause 5.1.1.2, clause 5.1.1.3, in 3GPP TS 28.552 [19] and key performance indicators in clause 6.3, in 3GPP TS 28.554 [20], and network slice related E2E latency analytics report in clause 8.4.2.4.3, in 3GPP TS 28.104 [21] from network slice management functions by utilizing MnS of create MOI operation defined in clause 11.1 and MnS of streaming data reporting service or file data reporting service defined in clause 11.5 and 11.6, 3GPP TS 28.532 [7].
3. The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application. If network slice status from step 2 is considered, the NSCE server analyses the network slice status information before triggering the network slice configuration. If the threshold is crossed for the current network slice of adaptation and the objective network slice satisfy the requests, NSCE server triggers the network slice configuration per VAL UE within the VAL Application.
4. The NSCE server acting as AF provides the updated S-NSSAI and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (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). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic.
NOTE: NSCE server provides the updated S-NSSAI/DNN as a suggestion/guidance to PCF; however it is up to PCF to decide whether to perform the slice/DNN re-mapping
5. Upon successful adaptation of the route selection parameters, the NSCE server provides a network slice adaptation response to the VAL server, providing information on the fulfilment of the network slice adaptation request per VAL application. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.2.2 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application - request and response model | Figure 9.11.2.2-1 illustrates the VAL UE-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Pre-condition:
- The NSCE client has connected to the NSCE server;
Figure 9.11.2.2-1: Network slice adaptation for VAL application
1. The VAL client provides a new application requirement to the NSCE client, indicating a new service profile for the VAL application. This may be in the form of a change at the application QoS requirements, location requirements, time window requirement, access type preference (e.g., 3GPP, non-3GPP or multi access) service operation change, or other application-related parameters.
2. The NSCE client sends a network slice adaptation trigger to the NSCE server for the VAL application. This trigger may be in the form of exact requested network slice (and optionally DNN) for the VAL UE of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The trigger may also include additional application requirements based on step1, e.g., the requested location criteria, time window.
NOTE 1：How the requested network slice is known by the NSCE client is out of scope of this release.
3. The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application.
NOTE 2：Whether and how the NSCE server triggers the network slice adaptation for all the VAL UEs within the VAL Application is out of scope of this release.
NOTE 3: How the NSCE server decides to trigger the network slice configuration is implementation dependent.
4. The NSCE server acting as AF provides the updated S-NSSAI, application requirements and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (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). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI, application requirements) that can be associated with applications matching the application traffic. 5GC uses this information to update the URSP to the affected UE(s).
NOTE 4: NSCE server provides the updated S-NSSAI/DNN as a suggestion/guidance to PCF; however it is up to PCF to decide whether to perform the slice/DNN re-mapping
5. The NSCE server sends the response to the NSCE client indicating success or failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.2.3 Procedure for VAL server-triggered and network-based network slice adaptation for VAL application – subscribe and notify model | Figure 9.11.2.3-1 illustrates the VAL server-triggered and network-based procedure with subscribe and notify model where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Figure 9.11.2.3-1: Network slice adaptation for VAL application
1. The VAL server sends a network slice adaptation subscribe request to the NSCE server for the VAL application (and the VAL UEs within the VAL application). This request may be in the form of exact requested network slice (and optionally DNN) for all the VAL UEs of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The request optionally includes the adaptation threshold of network slice adaptation as defined in Table 9.11.3.1-1.
2. The NSCE server confirms the subscription and returns the network slice adaptation subscribe response.
3. The NSCE server may interact with the 5GC and OAM to collects the network slice status and performs the network slice adaptation per VAL UE as described in step 2- step 4 in clause 9.11.2.1.
4. When the network slice adaptation completes, and the adaption result comes out and available, the NSCE server provides the network slice adaptation notification to the VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.2.4 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application - subscribe and notify model | Figure 9.11.2.4-1 illustrates the VAL UE-triggered and network-based procedure with subscribe and notify modeld where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Pre-condition:
- The NSCE client has connected to the NSCE server;
Figure 9.11.2.4-1: Network slice adaptation for VAL application
1. The VAL client provides a new application requirement to the NSCE client, indicating a new service profile for the VAL application. This may be in the form of a change at the application QoS requirements, location requirements, time window requirement, access type preference (e.g., 3GPP, non-3GPP or multi access) service operation change, or other application-related parameters.
2. The NSCE client sends a network slice adaptation trigger subscribe request to the NSCE server for the VAL application. This trigger may be in the form of exact requested network slice (and optionally DNN) for the VAL UE of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The trigger may also include additional application requirements based on step1, e.g., the requested location criteria, time window.
NOTE：How the requested network slice is known by the NSCE client is out of scope of this release.
3. The NSCE server confirms the subscription and responds with a network slice adaptation trigger subscribe response.
4. The NSCE server performs the network slice adaptation per VAL UE as described in step 3- step 4 in clause 9.11.2.2.
5. When the network slice adaptation completes, and the adaption result comes out and available, the NSCE server provides the network slice adaptation notification to the NSCE client. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.1 Network slice adaptation request | Table 9.11.3.1-1 describes the information flow network slice adaptation request from the VAL server to the NSCE server.
Table 9.11.3.1-1: Network slice adaptation request
Information element
Status
Description
VAL service ID
M
The VAL service ID of the VAL application for which the network slice adaptation may corresponds to.
List of VAL UE IDs
M
List of the VAL UE IDs within the VAL service for which the slice adaptation request corresponds
Requested Network slice related identifier(s)
O
Identifier of network slice for which the VAL server requests to use for adaptation
Requested monitored Network slice related identifier(s)
O
(see NOTE 1)
Identifier of the provisioned network slice(s) which are provisioned for the listed UE(s) and requested to be monitored by NSCE server
Requested DNN
O
Indication of the new DNN which is requested.
Requested Adaptation threshold
O
(see NOTE 2)
The threshold of network slice adaptation
>Requested adaptation threshold of the delay of network slice
O
The network slice delay defined clause 5.1.1.1, 5.1.1.2, 5.1.1.3, in 3GPP TS 28.552 [19] and key performance indicators in clause 6.3, in TS 28.554 [20], and network slice related analytics report in clause 8.4.2.4.3, in 3GPP TS 28.104 [21].
NOTE 1: If this IE is not present then the NSCE server monitors all the slices provisioned for the listed UE(s) mentioned in this request. If this IE is present, the NSCE server monitors the network slice(s) only indicated by the identifier(s).
NOTE 2: The NSCE is requested to adapt UE to the requested network slice only when the status of the provisioned network slice for the listed UE(s) crosses the requested threshold. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.2 Network slice adaptation response | Table 9.11.3.2-1 describes the information flow network slice adaptation response from the NSCE server to the VAL server.
Table 9.11.3.2-1: Network slice adaptation response
Information element
Status
Description
Result
M
Result includes success or failure of the network slice adaptation with the underlying network.
Cause
O
Indicates the cause of failure |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.3 Network slice adaptation trigger | Table 9.11.3.3-1 describes the information flow Network slice adaptation trigger from the NSCE client to the NSCE server.
Table 9.11.3.3-1: Network slice adaptation trigger
Information element
Status
Description
VAL UE ID(s)
M
The VAL UE ID(s) within the VAL service, for which the network slice adaptation trigger applies
VAL service ID
M
The VAL service ID of the VAL application for which the network slice configuration may corresponds to.
Requested S-NSSAI
M
Indication of the new S-NSSAI which is requested.
Requested DNN
O
Indication of the new DNN which is requested.
Request application requirements
O
The application-related request parameters
>Requested time window
O
Indication of the new scheduled time window that is requested
>Requested location criteria
O
Indication of the new location criteria that is requested
>Requested access type preference
O
Indication of the new access type (3GPP, non-3GPP or multi-access) preference that is requested. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.4 Network slice adaptation trigger response | Table 9.11.3.4-1 describes the information flow network slice adaptation trigger response from the NSCE server to the NSCE client and optionally to the VAL client.
Table 9.11.3.4-1: Network slice adaptation trigger response
Information element
Status
Description
Result
M
Result includes success or failure of the network slice adaptation.
Cause
O
Indicates the cause of failure |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.5 Network slice adaptation subscribe request | Table 9.11.3.5-1 describes the information flow network slice adaptation subscribe request from the VAL server to the NSCE server.
Table 9.11.3.5-1: Network slice adaptation subscribe request
Information element
Status
Description
VAL service ID
M
The VAL service ID of the VAL application for which the network slice adaptation may corresponds to.
List of VAL UE IDs
M
List of the VAL UE IDs within the VAL service for which the slice adaptation request corresponds
Requested Network slice related identifier(s)
O
Identifier of network slice for which the VAL server requests to use for adaptation
Requested monitored Network slice related identifier(s)
O
(see NOTE 1)
Identifier of the provisioned network slice(s) which are provisioned for the listed UE(s) and requested to be monitored by NSCE server
Requested DNN
O
Indication of the new DNN which is requested.
Requested Adaptation threshold
O
(see NOTE 2)
The threshold of network slice adaptation
>Requested adaptation threshold of the delay of network slice
O
The network slice delay defined clause 5.1.1.1, 5.1.1.2, 5.1.1.3, in 3GPP TS 28.552 [19] and key performance indicators in clause 6.3, in TS 28.554 [20], and network slice related analytics report in clause 8.4.2.4.3, in 3GPP TS 28.104 [21].
NOTE 1: If this IE is not present then the NSCE server monitors all the slices provisioned for the listed UE(s) mentioned in this request. If this IE is present, the NSCE server monitors the network slice(s) only indicated by the identifier(s).
NOTE 2: The NSCE is requested to adapt UE to the requested network slice only when the status of the provisioned network slice for the listed UE(s) crosses the requested threshold. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.6 Network slice adaptation subscribe response | Table 9.11.3.6-1 describes the information flow network slice adaptation subscribe response from the NSCE server to the VAL server.
Table 9.11.3.6-1: Network slice adaptation subscribe response
Information element
Status
Description
Subscription ID
M
(see NOTE)
Identifier of the subscription
Result
M
Result includes success or failure of subscription
Cause
O
Indicates the cause of failure
NOTE: Only present if the result is success. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.7 Network slice adaptation trigger subscribe request | Table 9.11.3.7-1 describes the information flow Network slice adaptation trigger subscribe request from the NSCE client to the NSCE server.
Table 9.11.3.7-1: Network slice adaptation trigger subscribe request
Information element
Status
Description
VAL UE ID(s)
M
The VAL UE ID(s) within the VAL service, for which the network slice adaptation trigger applies
VAL service ID
M
The VAL service ID of the VAL application for which the network slice configuration may corresponds to.
Requested S-NSSAI
M
Indication of the new S-NSSAI which is requested.
Requested DNN
O
Indication of the new DNN which is requested.
Request application requirements
O
The application-related request parameters
>Requested time window
O
Indication of the new scheduled time window that is requested
>Requested location criteria
O
Indication of the new location criteria that is requested
>Requested access type reference
O
Indication of the new access type (3GPP, non-3GPP or multi-access) preference that is requested. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.8 Network slice adaptation trigger subscribe response | Table 9.11.3.8-1 describes the information flow network slice adaptation trigger subscribe response from the NSCE server to the NSCE client and optionally to the VAL client.
Table 9.11.3.8-1: Network slice adaptation trigger subscribe response
Information element
Status
Description
Subscription ID
M
(see NOTE)
Identifier of the subscription
Result
M
Result includes success or failure of subscription
Cause
O
Indicates the cause of failure
NOTE: Only present if the result is success. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.3.9 Network slice adaptation notification | Table 9.11.3.9-1 describes the information flow network slice adaptation notification from the NSCE server to the VAL server or to the NSCE client.
Table 9.11.3.9-1: Network slice adaptation notification
Information element
Status
Description
Subscription ID
M (NOTE)
Identifier of the subscription
Adaption result
M
Result includes success or failure of the network slice adaptation with the underlying network.
Cause
O
Indicates the cause of failure |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.4.1 General | Table 9.11.4.1-1 illustrates the APIs for VAL server-triggered and network-based network slice adaptation.
Table 9.11.4.1-1: List of APIs for network slice adaptation
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ NSCE_NetworkSliceAdaptation
Network_slice_adaptation
VAL server
Request /Response
Table 9.11.4.1-2 illustrates the APIs for VAL UE-triggered and network-based network slice adaptation
Table 9.11.4.1-2: List of APIs for network slice capability adaptation trigger
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ NSCE_NetworkSliceAdaptationTrigger
Network_slice_adaptation_trigger
VAL server
Request /Response |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.4.2 SS_NSCE_NetworkSliceAdaptation API | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.4.2.1 General | API description: This API enables the VAL server to communicate with the network slice capability enablement server for network slice adaptation over NSCE-S. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.11.4.2.2 Network_Slice_Adaptation | API operation name: Network_Slice_Adaptation
Description: Requesting for network slice adaptation.
Known Consumers: VAL server.
Inputs: See subclause 9.11.3.1
Outputs: See subclause 9.11.3.2
See subclause 9.11.2.1 for the details of usage of this API operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12 Slice related communication service lifecycle management exposure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.1 General | The NSCE server supports the slice related communication service lifecycle management exposure to VAL server. The NSCE server acquires the application services related requirements for a specific VAL service from the vertical industry perspective, evaluates these requirements and then determines the network slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined the NSCE server allocate proper network slice resources to support the application services. The NSCE server also enables the VAL server to reconfigure or disengage the slice related communication services for the application. The procedures in clause 9.12.2 are for creation, reconfiguration and disengagement of slice related communication service respectively. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.2.1 Procedures on slice related communication service lifecycle management exposure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.2.1.1 Slice related Communication Service Creation | Figure 9.12.2.1.1-1 illustrates the procedure of slice related communication service creation. The NSCE helps to allocate network slice resources to support the application service required by the verticals.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
Figure 9.12.2.1.1-1: Slice related communication service creation
1. The VAL server sends a request to NSCE server to create a slice related communication service to support a specific application service, e.g., the VAL server wants to create a video streaming service in a future factory, the slice related communication service creation request carries the identifier of the video streaming service and the corresponding service attributes.
2. NSCE server translates the application service requirements (e.g., for a video streaming service, the service location and the resolution of the video) and then perform slice determination (e.g., dLtThptPerSlice, uLtThptPerSlice, latency as defined in serviceProfile TS 28.541[14]). The NSCE may perform the translation by pre-configured industry profiles or by KQI-KPI translation algorithms which are out scope of standard. The procedures of APIs translation defined in clause 9.3 are referred to.
3. NSCE server initiates the Slice Service subscription procedures by utilizing the management service of network slice creation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. The slice creation request may fail due to the shortage of network resources or other causes.
4. NCSE server sends the slice related communication service creation response to VAL server. If the slice creation is succeeded in step3, then the response from NSCE server should include the attributes and the values of network slice determined by NSCE server. If the slice creation failed in step3, the NSCE server shall indicate the cause of the creation failure, e.g. the shortage of network slice resources. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.2.1.2 Slice related Communication Service Reconfiguration | Figure 9.12.2.1.2-1 illustrates the procedure of slice related communication service reconfiguration to support the application service. The NSCE server provides the APIs to enable the VAL server to reconfigure the application service related requirements in case the current application service is not satisfied or application service is adjusted.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
2. The VAL server has requested the NSCE server to create a slice related communication service to support the application service.
Figure 9.12.2.1.2-1: Slice related communication service reconfiguration
1. VAL server sends the slice related communication service reconfiguration request to the NSCE server to reconfigure the properties of the application service (e.g., In case there is a downgrade/upgrade of the application service where the application service profile is changed).
2. NSCE server translates the application requirements according to the reconfigured application properties then updates the requested network slice.
3. NSCE server initiates the Slice Service update procedures by utilize the management service of network slice modification as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5.
4. NCSE server sends the slice related communication service modification response to VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.2.1.3 Slice related Communication Service disengagement | Figure 9.12.2.1.3-1 illustrates the procedure of slice related communication service disengagement. The NSCE server provides the APIs to enable the VAL server to terminate an application service.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
2. The VAL server has requested the NSCE server to create a slice related communication service to support the application service.
Figure 9.12.2.1.3-1: Slice related Communication service disengagement
1. The VAL server sends a request to NSCE server to disengage the slice related communication service when the application service is to be terminated.
2. NSCE server initiates the Slice Service de-allocation procedures by utilizing the management service of network slice de-allocation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5.
3. NCSE server sends the slice related communication service disengagement response to VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.3.1 General | The following information flows are specified for slice related communication service lifecycle management:
- slice related communication service creation
- slice related communication service reconfiguration
- slice related communication service disengagement |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.3.2 Slice related communication service creation | Table 9.12.3.2-1 and Table 9.12.3.2-2 describe information elements for slice related communication service creation request and response between the VAL server and the NSCE server.
Table 9.12.3.2-1: Slice related communication service creation request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service name
M
The name of the application service to be supported by the created slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
…
VAL service ID
M
Identifier of the application service
Area of interest
M
The service area for which the application service profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
Application service profile
M
The list of the requirements of the corresponding application service
> ReqInfo
M
The element containing the reqName and reqValue
>>ReqName
M
The name of the application service requirement, the value of this IE can be as followings:
the resolution of a video service,
the end user numbers,
the latency,
…
>>ReqValue
M
The corresponding value of the application service requirement
Table 9.12.3.2-2: Slice related communication service creation response
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
Identifier of the application service to be supported by the created slice related communication service.
Result
M
Indicates the success or failure of the slice related communication service creation
Network slice info List
O
(see NOTE 1)
The list of the network slice info determined by NSCE
> Network slice info
O
(see NOTE 1)
The network slice info which includes the attributes and the corresponding values of network slice
>>S-NSSAI
O
(see NOTE 1)
The identifier of network slice
>>attributes of network slice
O
(see NOTE 1)
The list of attributes of the serviceProfile e.g, dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541[10]
>>AttributeValues
O
(see NOTE 1)
The corresponding values of the attributes of the service profiles that determined by the NSCE server
Cause
O
(see NOTE 2)
Indicates the cause of creation failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise
NOTE 2: Shall be present if the result is failure and shall not be present otherwise |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.3.3 Slice related communication service reconfiguration | Table 9.12.3.3-1 and Table 9.12.3.3-2 describe information elements for slice related communication service reconfiguration request and response between the VAL server and the NSCE server.
Table 9.12.3.3-1: Slice related communication service reconfiguration request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service name
M
The name of the application service to be upgrade/downgrade which requires the reconfiguration of the slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
…
VAL service ID
M
Identifier of the application service
Area of interest
M
The service area for which the application profile applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
Application service profile
M
The list of the requirements of the corresponding application service to be changed
> ReqInfo
M
The element containing the reqName and reqValue
>>ReqName
M
The name of the application service requirement, the value of this IE can be as followings:
the resolution of a video service,
the end user numbers,
the latency,
…
>>ReqValue
M
The corresponding updated value of the application service requirement
Table 9.12.3.3-2: Slice related communication service reconfiguration response
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
Identifier of the application service
Result
M
Indicates the success or failure of the slice related communication service reconfiguration
Network slice info List
O (see NOTE 1)
The list of the network slice info updated by NSCE
> Network slice info
O (see NOTE 1)
The network slice info which includes the attributes and the corresponding values of network slice
>>S-NSSAI
O (see NOTE 1)
The identifier of network slice
>>Attributes of network slice
O (see NOTE 1)
The list of attributes of the serviceProfile e.g., dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541[10]
>>AttributeValues
O (see NOTE 1)
The corresponding values of the attributes of the service profiles that updated by the NSCE server
Cause
O
(see NOTE 2)
Indicates the cause of reconfiguration failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise
NOTE 2: Shall be present if the result is failure and shall not be present otherwise |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.3.4 Slice related communication service disengagement | Table 9.12.3.4-1: Slice related communication service disengagement request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service name
M
The name of the application service to be terminated which requires the disengagement of the slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
…
VAL service ID
M
Identifier of the application service
Table 9.12.3.4-2: Slice related communication service disengagement response
Information element
Status
Description
Result
M
Indicates the success or failure of the slice related communication service disengagement request
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
Identifier of the application service
Cause
O(see NOTE)
Indicates the cause of disengagement failure
NOTE: Shall be present if the result is failure and shall not be present otherwise |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.4.1 General | Table 9.12.4.1-1 and 9.12.4.1-2 illustrate the API for slice related communication service lifecycle management exposure.
Table 9.12.4.1-1: SS_NSCE_SliceCommServiceCreation
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_SliceCommService_Creation
SliceCommService_Creation_Request
Request /Response
VAL server
Table 9.12.4.1-2 SS_NSCE_ SliceCommServiceReconfiguration
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_SliceCommService_Reconfiguration
SliceCommService_Reconfiguration_Request
Request /Response
VAL Server
Table 9.12.4.1-3: SS_NSCE_ SliceCommServiceDisengagement
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_SliceCommService_Disengagement
SliceCommService_Disengagement_Request
Request /Response
VAL Server |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.4.2 SS_NSCE_SliceCommService_Creation API | API operation name: SliceCommService_Creation
Description: The consumer requests to create the slice related communication service
Known Consumers: VAL server.
Inputs: See table 9.12.3.2-1.
Outputs: See table 9.12.3.2-2.
See clause 9.12.2.1.1 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.4.3 SS_NSCE_SliceCommService_Reconfiguration API | API operation name: SliceCommService_Reconfiguration
Description: The consumer requests to report reconfigure the slice related communication service.
Known Consumers: VAL server.
Inputs: See table 9.12.3.3-1.
Outputs: See table 9.12.3.3-2.
See clause 9.12.2.1.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.12.4.4 SS_NSCE_SliceCommService_Disengagement API | API operation name: SliceCommService_Disengagement
Description: The consumer requests to disengagement the slice related communication service.
Known Consumers: VAL server.
Inputs: See table 9.12.3.4-1.
Outputs: See table 9.12.3.4-2.
See clause 9.12.2.1.3 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13 Predictive slice modification in Inter-PLMN based slice service continuity | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.1 General | This feature applies to the specific deployment where NSCE service provider provides its services when connected to two PLMNs and has SLA with them (i.e. deployment shown in 3GPP TS 23.434 [2] Figure 8.2.2-2). In this feature, the NSCE server initially receives an expected/predicted UE location/mobility change request outside a PLMN1 slice service area for one or more UEs within the VAL application session (e.g. such session can be a V2X session). Then, the NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target PLMN. The NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change). Based on this decision/recommendation, it provides the action to the OAM of PLMN2 proactively, before UE mobility happens. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.2 Procedure | In the procedure shown in Figure 9.13.2-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 PLMN supported by the same NSCE server.
Pre-conditions:
1. Enterprise hosting the VAL server has SLA for slice services with NSCE service provider.
2. The VAL server has subscribed to the network slice capability enablement server managing slice services from PLMN1 and PLMN2.
3. The VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to PLMN1.
4. The NSCE server is connected to 5GS of PLMN1 and PLMN2.
5. The VAL server is subscribed to and received mobility predictions of UE location change (according to 6.7.2.3 of 3GPP TS 23.288 [4]) from PLMN1 and/or PLMN2 in advance before the actual event. The VAL server correlated received mobility predictions and determined PLMN change.
Figure 9.13.2-1: Predictive Inter-PLMN slice service continuity
1. The VAL server sends to NSCE server an Inter-PLMN application service continuity requirement request due to predicted/expected UE or group UE mobility from source service area of slice1 in PLMN1 to a target service area covered by a different slice service area in slice#2/PLMN2.
NOTE: Such UE predicted mobility at the VAL server can be available before the event based on UE mobility analytics received by NWDAF or can be predicted by the VAL layer (VAL server or VAL UE).
2. NSCE server sends an Inter-PLMN application service continuity requirement response to the VAL server as positive or negative acknowledgement depending on its capability to provide such service serving both areas/slices in both PLMNs and available resources.
3. NSCE server determines to query the underlying 5G system on the slice availability and conditions at the target service area/slice2/PLMN2 (based on step 1 requirement). Such query may be in form of a request/response and include:
a. NSCE server interacting with 5GS/PLMN2 to query the UEs specific information (location, UEs connection capabilities) as well as network conditions, slice related analytics (from NWDAF as specified in 3GPP TS 3.288 [4]).
b. NSCE server may also interact with 5GS/PLMN2 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. NSCE server determines the need for a slice lifecycle change at the slice target area and translates this to a trigger action. This trigger action can be based on the outcome of step 3 and can be a requested slice modification (slice2/PLMN2) or creation/instantiation of new slice at the target area (this may happen if a group of UEs are moving to the target area and the requested slice2 is missing in the target area).
5. The NSCE server may send the trigger action as a slice modification trigger request to the slice provisioning MnS producer at OAM/PLMN2 (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 with a positive or negative result.
6. After the slice lifecycle change execution (based on the indication in step 5), the NSCE server sends a notification to the VAL server and optionally to the VAL client containing the positive or negative result from step5.
7. If big number of UEs is migrating from PLMN1 to PLMN2, there might be a need to further modify/reduce the respective slice resources of PLMN1. NSCE sends trigger request to the slice provisioning MnS producer at OAM/PLMN1 (e.g. slice modification for network slice) to decrease slice availability to the source area after the UEs have migrated. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.3.1 General | The following information flows are specified for predictive inter-PLMN slice service continuity:
- Inter-PLMN application service continuity requirement
- Slice modification notification |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.3.2 Inter-PLMN application service continuity requirement request | Table 9.13.3.2-1 and Table 9.13.3.2-2 describe information elements inter-PLMN application service continuity requirement request and response between the VAL server and the NSCE server.
Table 9.13.3.2-1: Inter-PLMN application service continuity requirement request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
Security credentials
M
Security credentials resulting from a successful authorization.
VAL service ID
M
The identifier of the VAL service for which the requirement request applies
VAL UE ID list
O
The list of VAL UE IDs for which the requirement request applies
Service Continuity Requirement
M
The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area.
Target PLMN ID
M
PLMN identifier of the target PLMN
Slice identifier
O
(see NOTE)
The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server
Target Service Area
O
The target area can be represented as the geographical coordinates / set of waypoints outside the original service area, where the VAL application/ UE(s) is expected or predicted to move.
Application QoS requirements
O
The QoS requirements / KPIs for the VAL service
NOTE: Slice info can be available based on SLA between VAL service provider and network operator.
Table 9.13.3.2-2: Inter-PLMN application service continuity requirement response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.3.3 Inter-PLMN slice modification notify | Table 9.13.3.3-1 describes information elements for the inter-PLMN slice modification notify message from the NSCE server to the VAL server or the VAL client (via NSCE client).
Table 9.13.3.3-1: Inter-PLMN slice modification notify
Information element
Status
Description
VAL service ID
M
The identifier of the VAL application which is impacted by the slice modification
VAL UE ID list
O
The identifiers of the VAL UEs which are impacted by the slice modification
Slice identifier
M
The slice identifier (S-NSSAI, NSI ID or ENSI) which is used and/or modified to extend slice availability to the target service area
PLMN ID
M
PLMN identifier of the PLMN where modification was performed
Target Service Area
M
The target area, can be represented as the geographical coordinates / set of waypoints outside the original service area, for which the modification applies. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.4.1 General | Table 9.13.4.1-1 illustrates the API for inter-PLMN application service continuity exposure.
Table 9.13.4.1-1: Inter-PLMN application service continuity requirement
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_InterPLMN_Continuity
Inter-PLMN_Continuity_Requirement
Request /Response
VAL server
SS_NSCE_InterPLMN_Slice_Modification_Notify
Inter-PLMN_Slice_Modification_Notify
Notify
VAL server or VAL client |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.4.2 SS_NSCE_Inter-PLMN_Continuity API | API operation name: Inter-PLMN_Continuity_Requirement
Description: The consumer requests to have inter-PLMN slice service continuity
Known Consumers: VAL server.
Inputs: See table 9.13.3.2-1.
Outputs: See table 9.13.3.2-2.
See clause 9.13.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.13.4.3 SS_NSCE_Inter-PLMN_slice modification notify API | API operation name: Inter-PLMN_Slice_Modification_Notify
Description: The NSCE notifies about slice modification
Known Consumers: VAL server.
Inputs: See table 9.13.3.3-1
Outputs: None
See clause 9.13.2 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14 Network slice diagnostics | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.1 General | Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service – either reported from a mobile user or service or detected by application and can initiate a check with NSCE. The NSCE server can provide details related to the identified event. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.2.1 Network slice diagnostics procedure | In the procedure shown in Figure 9.14.2.1-1, a mechanism is provided to allow for vertical/ASP using VAL server to initiate request for network slice diagnostics and receive all the relevant information about specific events.
Pre-conditions:
1. Enterprise hosting the VAL server has SLA for slice services with NSCE service provider.
2. The VAL server has subscribed to the network slice capability enablement server managing slice services.
3. The NSCE server has initiated monitoring and gathering statistical data about its managed slices from ADAES according to TS 23.436 clause 8.3 and 8.7.
4. The VAL server has identified there is specific event where the application has experienced service degradation (reported errors from VAL client for degraded service (bad quality), reported errors from application (downgrade of communication, detected communication errors).
Figure 9.14.2.1-1: Network slice diagnostics procedure
1. The VAL server sends to NSCE server a network slice diagnostics request containing information about detected service degradation.
2. NSCE server determines which specific statistics to request from ADAES based on the indicated service degradation. If the service degradation is related to detected communication error, then slice usage pattern statistics are needed. If bad quality is reported from the VAL client slice-specific application performance statistics are needed. NSCE server collects the needed statistics based on the procedure described in TS23.436 clause 8.7.3.
3. Based on the received statistics information and input from VAL server, the NSCE server correlated data and prepares network slice diagnostics report about the needed diagnostics.
4. NSCE server sends network slice diagnostics reply to VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.3.1 General | The following information flows are specified for Network slice diagnostics:
- Network slice diagnostics request and response |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.3.2 Network slice diagnostics request and response | Table 9.14.3.2-1 and Table 9.14.3.2-2 describe information elements for the network slice diagnostics request and response between the VAL server and the NSCE server.
Table 9.14.3.2-1: Network slice diagnostics request
Information element
Status
Description
VAL information
M
The information of the VAL server.
Network Slice Diagnostics ID
M
Identifier of the network slice diagnostics.
Service degradation type
M
The information of service degradation.
> VAL service identity
M
Identifier of the VAL service to be monitored.
>ErrorsList
M
The list of registered errors by VAL server.
>> ErrorName
M
The name of the reported error: detected communication error; RTT above limit; QoS downgrade.
>> Network slice related Identifier(s)
M
Identifier(s) of the network slice to be checked.
>> UE(s) related Identifier(s)
O
Identifier(s) of the related UE(s).
>> 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).
>>StartTime
M
The start time point of the registered service degradation.
>>EndTime
M
The end time point of the registered service degradation.
Table 9.14.3.2-2: Network slice diagnostics response
Information element
Status
Description
Result
M
Indicates the success or failure of network slice diagnostics request.
> Network slice Diagnostics ID
O
(see NOTE 1)
Identifier of the network slice diagnostics.
>StartTime
O
(see NOTE 1)
The start time point of the available data for network slice service degradation.
>EndTime
O
(see NOTE 1)
The start time point of the available data for network slice service degradation.
>Data type
O
(see NOTE 1)
The type of the reported data samples (UE data, network data, application data).
>Data output
O
(see NOTE 1)
The reported data related to the reported error(s) in the network slice diagnostics request.
>Cause
O
(see NOTE 2)
Indicates the cause of the network slice diagnostics request failure.
NOTE 1: Shall be present if the result is success.
NOTE 2: Shall be present if the result is failure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.4.1 General | Table 9.14.3.2-1 and 9.14.3.2-2 illustrate the API for network slice diagnostics.
Table 9.14.4.1-1: List of APIs for the network slice diagnostics feature
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_Network Slice Diagnostics
Network Slice Diagnostics
VAL server
Request / Response |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.4.2 SS_NSCE_Network_Slice_Diagnostics | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.4.2.1 General | API description: This API enables the VAL server to communicate with the network slice capability enablement server for requesting network slice diagnostics over NSCE-S. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.14.4.2.2 Network_Slice_Diagnostics | API operation name: Network_Slice_Diagnostics
Description: Request for Network_Slice_Diagnostics to the NSCE server and receiving a response / result.
Known Consumers: VAL server.
Inputs: See table 9.14.3.2-1.
Outputs: See table 9.14.3.2-2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15 Network slice fault management capability exposure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.1 General | 5GS is required to provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party according to operator policies. And network diagnostics is of key importance that helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient fault diagnosis results that characterize the quality of the network connections and services. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems. Also, the alarm data from different sources (e.g., OAM, VAL server, NSCE client) can be used to help the third-party to diagnose the fault problem of the services, locate the fault causes, and to be aware of the potential fault. In TS 28.545 [23], the fault supervision management services are standardized by which the alarm of the network slice instance from network resource aspects can be subscribed and reported. This alarm information together with the application function's fault report and communication service related knowledge can be utilized by the NSCE to diagnose the cause of the service performance deterioration, locate the fault of the communication services, and expose the fault report to the third-party.
For example, if the status of the required communication is not correct, the SEAL/NSCE derives this alarm information from application functions. In this case, it is the SEAL/NSCE's responsibility to detect whether this fault is caused by the 5GS network or not and exposed the fault report to the third-party. If it is, then the SEAL/NSCE may inform the management functions the location of the fault and ask for the maintenance of the managed functions to clear the fault.
This service provides a possible procedure to illustrate the network slice fault management capability exposed by NSCE server. The performance data and alarm data from multiple sources is helpful to characterize the quality of the network connection. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.2.1 Procedures on network slice fault management capability exposure | Figure 9.15.2.1-1 illustrates the network slice fault management process to address the key issue 4 of network slice fault management.
Pre-conditions:
1. The network slice enabler layer is capable to interact with NEF and OAM system.
2. The VAL server has checked the status of application layer.
Figure 9.15.2.1-1: Support for predictive slice modification in distributed NSCE server deployments
1. The VAL server sends a subscription to NSCE server to subscribe the fault diagnosis of the applications and networks. This request may be triggered by the errors of the applications detected by the VAL server itself, or the VAL server may periodically collect the fault diagnostic report subscribing to the NSCE.
2. NSCE server sends the response of the subscription to VAL server.
3. Optionally, on receiving the request from VAL server, NSCE server subscribes the performance data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[7] is utilized. For CN functions, the APIs of Nnwdaf_AnalyticsInfo service defined in clause 7.3, TS 23.288[4] can be utilized.
The analytics data defined in clause 6.3 to clause 6.14, TS 23.288[4], network slice instance related performance data defined in clause 5, TS 28.552[19] and network analytics data in clause 8.3 and clause 8.4 TS 28.104[21] exposed by OAM system may be acquired. Also, the analytics result of slice-specific performance and slice usage analytics defined in TS 23.436[26] can be utilized.
4. NSCE server subscribes the alarms of network slice instances from OAM system via the procedures defined in clause 6.1, TS 28.545[23], and the alarms are defined in clause 4.1.1.1, TS 32.111-1 [24], e.g., the fault of communication, environmental, equipment, processing error, QoS for device/resource/file/functionality/smallest.
5. NSCE server may subscribe the alarm information (e.g., the 5GS network is not work or the required performance is under the threshold which leads the service's problem) collected by NSCE client if possible. The information collected by the NSCE client depends on the third-parties' requirements and implementation.
6. NSCE client report the requested fault information to NSCE server.
Note: The collection of fault data from NSCE client follows the mechanism defined in EVEX in SA4.
7. Every time the notifications from the OAM, NSCE client or ADAEs are received, NSCE server correlates this data, diagnoses the causes of the fault of the applications or services by analysing the fault information from different sources and prepares report for the VAL to be notified about the respective fault event. For example, the RAN function of the slice instance which is utilized to support the service of the smart grid application, for a certain time duration, the smart grid suffered the bad experience caused by Service Availability Failure Events, and in the RAN function is detected continuously to report an alarm of environmental fault in the same time duration, then the environment fault may be the root cause of the Service Availability Failure and should be prioritized to be solved. The fault may be identified with "critical", "major", "minor", "ignore" to show its prioritization.
8. If the NSCE server detects that the application/service error (reported from NSCE client) is caused by the 5GS, the VAL server may send the fault diagnosis report to OAM system to indicate the server fault which causes the application/service failure by utilizing the NSCE-OAM interface.
NOTE: The APIs utilized to send the fault diagnosis report to OAM will re-utilize the fault management services in TS 28.532[7] exposed by EGMF as defined in TS 28.533[25].
9. NSCE server send a notification to VAL server with the fault diagnostics report prepared in step 7. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.3.1 General | The following information flows are specified for the network slice fault management capability exposure. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.3.2 Fault diagnosis subscription request | Table 9.15.3.2-1 describes information elements for fault diagnosis subscription.
Table 9.15.3.2-1: Fault diagnosis subscription
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 request applies
VAL UE ID list
O
The list of VAL UE IDs for which the request applies
Fault diagnosis information
O
Indicate what kind of fault is need for the subscription, e.g., time, specific problem, etc..
Network slice related Identifier(s)
O
Identifier(s) of the network slice to be monitored |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.3.3 Response of fault diagnosis subscription | Table 9.15.3.3-1 describes information elements for response of fault diagnosis subscription.
Table 9.15.3.3-1: Response of fault diagnosis subscription
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription
Result
M
The result of the request (positive or negative acknowledgement) |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.3.4 Fault diagnosis notification | Table 9.15.3.4-1 describes information elements for fault diagnosis notification.
Table 9.15.3.3-4: Fault diagnosis notification
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription
Fault Report ID
M
Identifier of the fault Report
FaultReport
M
The report of the fault diagnosis
>CorrelatedAlarmList
M
The list of the correlated alarms
>>CorrelatedAlarm
M
The correlated alarms
>rootCause
M
The root cause of the fault |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.15.4 APIs |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.