hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.15.4.1 General
|
Table 9.15.4.1-1 illustrates the APIs for the network slice fault management capability exposure.
Table 9.15.4.1-1: fault diagnosis request.
API Name
API Operations
Communication Type
Consumer(s)
SS_NSCE_FaultDiagnosis
Fault_Diagnosis_Subscribe
subscription / notification
VAL server
Fault_Diagnosis_Notification
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.15.4.2 SS_NSCE_FaultDiagnosis API
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.15.4.2.1 General
|
API description: This API enables the VAL server to communicate with the network slice capability enablement server to request the fault diagnosis over NSCE-S.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.15.4.2.2 Fault_Diagnosis_Subscribe
|
API operation name: Fault_Diagnosis_Subscribe
Description: The consumer subscribes to the network slice fault diagnosis
Known Consumers: VAL server
Inputs: See table 9.15.3.2-1
Outputs: See table 9.15.3.3-1
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.15.4.2.3 Fault_Diagnosis_Notification
|
API operation name: Fault_Diagnosis_Notification
Description: The consumer notifies the network slice fault diagnosis results
Known Consumers: VAL server
Inputs: None
Outputs: See table 9.15.3.4-1
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16 Slice requirements verification and alignment capability exposure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.1 General
|
Verticals can compare the QoS achieved by the provider with the QoS/slice requirements and its own experience of the QoS to verify if the QoS/Slice requirements are reasonably configured. To order a slice with certain slice requirements parameters and their values, the verticals will put their best effort into slice requirements translation. However, they are not able to guarantee that all the potential factors will be considered to generate the optimal slice requirements parameters on the first try.
In some cases, there may be some unforeseen exceptions (e.g., unexpected traffic changes) and the current configured slice requirements parameters are not able to fulfil the verticals requirements (e.g., more resources are required to address the exceptions), the VAL client may also suffer unsatisfied experience. Or in some other cases, when the service is executed on the required slice, the slice may not fully match the service real-time running conditions, for example, maybe only 60% of the slice resource is used to support the service, and rest of the slice resource is always idle, or the slice resource is insufficient due to under-provisioning.
Hence, NSCE is able to provide the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client to check whether the existing QoS/Slice related data is able to satisfy the VAL clients and send periodically alignment notifications to VAL server for the slice requirements. To enable the VAL server to configure the optimal slice requirements parameters to align with the real vertical needs, the NSCE layer is able to monitor the network performance statistics and to evaluate whether the current slice requirements parameters are reasonable to achieve the maximum return of investment. To enable the slice/service self-management, the NSCE server may have the capability to generate and configure more reasonable slice requirements parameters. To avoid frequently reconfiguration of network slice requirements, the action of alignment is triggered by the evaluation of network performance statistics during a certain time period but not by a single event.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.2.1 Procedures on slice requirements verification and alignment capability exposure
|
Figure 9.16.2.1-1 provides a possible procedure of slice requirements verification and alignment capability exposure.
Pre-conditions:
1. The NSCE Server has subscribed to the service of network slice performance management provided by EGMF.
Figure 9.16.2.1-1: Slice requirements verification and alignment process
1. The VAL server sends slice requirements verification and alignment subscription NSCE server to require the NSCE server to check whether the slice requirements (by configuring the attributes of serviceProfile) matches the real network slice usage status, the request may include the S-NSSAI, the ID of the VAL server, the slice requirements parameters (attributes of serviceProfile) which is requested to be aligned. Optionally, the request includes the reporting criteria indicating when the NSCE server needs to send the notification. This alignment reporting allows the VAL server to configure the reporting based on number of UEs, and time information in order to send/block the reporting of alignment notification. The automatic enforcement mode indicates the NSCE server should automatically enforce the updated slice requirement.
2. The NSCE server checks if the VAL server is authorized to trigger the service of slice requirements alignment.
3. The NSCE server response to VAL server with the result of slice requirements verification and alignment request, e.g., the slice requirements alignment request is accepted.
4. The NSCE server may optionally subscribe the QoE data from the NSCE client. The QoE data can refer to the data defined in clause 16, TS 26.114[27].
Note: The QoE data collection from NSCE client follows the mechanism defined in EVEX work in SA4.
5. The NSCE server subscribes the network slice related performance data and KPIs (e.g., the average PRB usage, the distribution of the PRB usage) defined in TS 28.552[19]. The NSCE server can aslo subscribe the analytics data (both statistics and predictions) from MDAS and ADAEs.
6a-6b. NSCE server periodically receives the subscribed data (from steps 4 and 5) and compares the slice requirement parameters of network slice (the values of attributes of serviceProfile, e.g., radioSpectrum, the maxNumberofUEs) with network slice performance statistics (e.g., active number of users, the average PRB usage, the distribution of the PRB usage of the S-NSSAI) to generate the optimal slice requirements for the required service (represented by S-NSSAI) of the vertical.
This step depends on implementation (e.g., if in implementation specific time window the VAL client experience is satisfied while the network slice resources are with low utilization, the resources required in the slice requirements could be reduced based on predictions and statistics). When the reporting criteria is met like generated slice requirement is outside the given slice requirement range, the NSCE server send the notification to inform the VAL about the result of the verification and alignment. If automatic enforcement mode is indicated by the VAL server, the NSCE server enforces the slice optimization with the generated optimal slice requirement as the procedure defined in clause 9.12.2.1.2.
7. Based on the analysis in step 6, the NSCE server periodically sends notifications to VAL server to inform the recommended changes of the slice requirements parameters. Optionally, if VAL server configures the reporting based on the alignment criteria then the NSCE server reports the notification to the VAL server e.g. based on the mentioned number of UEs are present in the slice, time information.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.3.1 General
|
The following information flows are specified for slice requirements verification and alignment capability exposure.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.3.2 Slice requirements verification and alignment subscription
|
Table 9.16.3.2-1 describes information elements for slice requirements verification and alignment subscription.
Table 9.16.3.2-1: Slice requirements verification and alignment 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 requirement request applies
VAL UE ID list
O
The list of VAL UE IDs for which the requirement request applies
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
Slice Requirements List
M
The list of the slice requirements which need to be aligned.
>sliceRequirement
M
The requirement which need to be aligned, this parameter refers to the attribute of serviceProfile defined in TS 28.541 [10]
Reporting criteria
O
Indicate the notification reporting criteria, e.g. generated slice requirement is outside the given slice requirement range
Automatic enforcement mode
O
Indicates the mode for automatic enforcement of the generated optimal slice requirements to meet the slice requirements. E.g OFF or ON
Alignment reporting criteria
O
Indicates the alignment reporting conditions to the VAL server e.g. based on count of UEs, based on temporal (time information)
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.3.3 Response of slice requirements verification and alignment subscription
|
Table 9.16.3.3-1 describes information elements for response of slice requirements verification and alignment subscription.
Table 9.16.3.3-1: Response of slice requirements verification and alignment subscription
Information element
Status
Description
Result
M
The result of the subscription (positive or negative acknowledgement)
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.3.4 Slice requirements verification and alignment notification
|
Table 9.16.3.4-1 describes information elements for slice requirements verification and alignment notification.
Table 9.16.3.4-1: Slice requirements verification and alignment notification
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 requirement request applies
VAL UE ID list
O
The list of VAL UE IDs for which the requirement request applies
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
Updated Slice requirements info
M
The attributes and values of slice requirements
> Slice requirement alignment enforcement
O
Indicates the updated slice requirement is enforced or not. E.g Yes or No
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4 APIs
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4.1 General
|
Table 9.16.4.1-1 illustrates the APIs for the network slice verification and alignment capability exposure.
Table 9.16.4.1-1: List of APIs for network slice verification and alignment
API Name
API Operations
Communication Type
Consumer(s)
SS_NSCE_SliceReq_VerifyAndAlign
SliceReq_VerifyAndAlign_Subscribe
Subscription/Notification
VAL server
SliceReq_VerifyAndAlign_Notification
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4.2 SS_NSCE_SliceReq_VerifyAndAlign API
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4.2.1 General
|
API description: This API enables the VAL server to communicate with the network slice capability enablement server to consume the network slice requirements verification and alignment service.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4.2.2 SliceReq VerifyAndAlign_Subscribe
|
API operation name: SliceReq_VerifyAndAlign
Description: The consumer subscribe to the network slice requirements verification and alignment.
Known Consumers: VAL server
Inputs: See table 9.16.3.2-1
Outputs: See table 9.16.3.3-1
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.16.4.2.3 SliceReq_VerifyAndAlign_Notification
|
API operation name: SliceReq_VerifyAndAlign_Notification
Description: The consumer is notified with the updated network slice requirements information according to the slice requirements verification and alignment.
Known Consumers: VAL server
Inputs: None
Outputs: See table 9.16.3.4-1
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17 Network Slice Information delivery
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.1 General
|
The NSCE layer provides the feature of Network Slice information delivery. The Network Slice information is necessary for the VAL server to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice.
The Network Slice information that is delivered to the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards.
The NSCE server performs the below.
- Retrieval of Network Slice ServiceProfile in 5GS (e.g., NSMF) as specified in 3GPP TS 28.532 [7]
- Conversion of Network Slice ServiceProfile (specified in 3GPP TS 28.541 [10]) to Network Slice Information
- Creation of Network Slice Information
- Storing of Network Slice Information
- Delivery of Network Slice Information to VAL server that the Network Slice Customer is authorized to use.
NOTE: The Network Slice Information provided to the VAL server depends on service agreements.
The VAL server as a Network Slice consumer makes use of the delivered Network Slice information for the Network Slice Lifecycle management for its service.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.2.1 Network Slice Information delivery request
|
This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE server, when the VAL server requests the Network Slice Information after registration.
Pre-condition:
1. The NSCE server should have the agreement with MNO (NOP) for retrieval of ServiceProfile, if the NSCE server is the external entity.
Figure 9.17.2.1-1: Network Slice Information delivery request
1. The NSCE server retrieves the Network Slice ServiceProfile from 5GS (e.g., NSMF) when the NSCE server acting as a NSP prepares a Network Slice to be provided. The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'getMOIAttributes' operation as specified in 3GPP TS 28.532[7].
NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. The delivered Network Slice Service Profile contains the values of attributes such as PLMN, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Slice Coverage Area, Latency, and, Data volume, which specify the Network Slice characteristics, as specified in clause of ServiceProfile in 3GPP TS 28.541 [10].
2. The NSCE server, as Network Slice as a Service, creates and stores the Network Slice information. When NSCE server retrieves the Network Slice Information, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information and to compose the Network Slice information, according to the NSP's policy.
In order to reduce to request often the Network Slice Information Retrieval, the NSCE server stores the Network Slice information.
3. The VAL server requests the Network Slice Information to the NSCE server. If the VAL server needs to know the specific attribute value for its service, then the attribute name of Network Slice Information (e.g., S-NSSAI, SST, Slice Coverage Area, etc.) can be added in the Request message.
4. The NSCE server performs to check whether the requesting VAL server is registered or not. The NSCE server identifies which the Network Slice Customer is authorized to use.
5. The NSCE server sends the Network Slice Information, if the VAL server is registered and authorized. The NSCE server rejects to the request of the Network Slice Information, if not registered.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.2.2 Network Slice Information delivery to NSCE client request
|
This subclause depicts the procedure of the Network Slice Information delivery to the NSCE client via NSCE server.
Pre-condition:
1. The network slice has been allocated/created to VAL server.
Figure 9.17.2.2-1: Network Slice Information delivery to NSCE client
1. The VAL server sends a request to NSCE server to deliver the Network Slice Information to the NSCE Clients. The request includes the network slice information and indication of the UE notification with VAL UE's ID List.
2. The NSCE server delivers the Network Slice Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 1, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS.
The Network Slice Information contains the VAL service ID, S-NSSAI, and DNN.
3. The NSCE client stores and applies the Network Slice Information.
NOTE: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in clause 6.1.2.2.1 of 3GPP TS 23.503 [17]. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent.
4. The NSCE client sends the Network Slice Allocation Information response to the NSCE server.
5. The NSCE server sends the response to the Network Slice Information delivery to NSCE client request.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.3.1 Network Slice Information delivery request
|
Table 9.17.3.1-1 describes the information flows for Network Slice Information delivery from the VAL server to the NSCE server.
Table 9.17.3.1-1: Network Slice Information delivery 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 VAL service ID of the VAL application
Requested network slice information list
O
Network slice information that is requested by the VAL server
> S-NSSAI information request
O
Indicates to request S-NSSAI
> SST information request
O
Indicates SST
> Slice Coverage Area information request
O
Indicates slice coverage area
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.3.2 Network Slice Information delivery response
|
Table 9.17.3.2-1 describes the information flows for Network Slice Information delivery response from the NSCE server to the VAL server.
Table 9.17.3.2-1: Network slice information response
Information element
Status
Description
Result
M
Result includes success or failure of the Network Slice Information delivery request
> Network slice Information
O
(see NOTE 1)
Network slice information
>> S-NSSAI
O
S-NSSAI
>> SST
O
Slice/Service Type
>> Slice Coverage Area
O
Coverage area of the network slice
> Cause
O
(see NOTE 2)
Indicates the cause of Network Slice Information delivery 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.17.3.3 Slice Information delivery to NSCE client
|
Table 9.17.3.3-1 describes information elements for the Slice Information delivery to NSCE client request between the NSCE server and the NSCE client.
Table 9.17.3.3-1: Slice Information delivery to NSCE client request
Information element
Status
Description
VAL service ID
M
The identifier of the VAL service
NSCE server ID and address
M
The identifier and address of the NSCE server
VAL UE ID list
O
The identifiers of the VAL UEs which are impacted by the slice modification
>Network slice information
M
Network slice information
>> Network Slice related Identifier
M
The allocated slice identifier
>>DNN
O
The allocated DNN
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.3.4 Slice Information delivery to NSCE client
|
Table 9.17.3.4-1 describes information elements for the Slice Information delivery to NSCE client response between the NSCE server and the NSCE client.
Table 9.17.3.4-1: Slice Information delivery to NSCE client response
Information element
Status
Description
Result
M
Indicates the success or failure of the Slice Information delivery.
> Cause
O
(see NOTE)
Indicates the cause of Slice Information delivery request failure.
NOTE: Shall be present if the result is failure and shall not be present otherwise.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.4 APIs
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.4.1 General
|
Table 9.17.4.1-1 illustrates the APIs for the Network Slice Information delivery.
Table 9.17.4.1-1: List of APIs for Network Slice Information delivery
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_NSInfoDelivery
NSInfoDelivery_request
Request/Response
VAL Server
Table 9.17.4.1-2 illustrates the APIs for the Network Slice Information delivery to NSCE client.
Table 9.17.4.1-2: List of APIs for Network Slice Information delivery to NSCE client
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_NSInfoDelivery_Client
NSInfoDelivery_Client
Request/Response
VAL Server
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.4.2 SS_NSCE_NSInfoDelivery Get operation
|
API operation name: SS_NSCE_NSInfoDelivery Get
Description: The consumer requests to get Network Slice Information.
Inputs: See clause 9.17.3.1.
Outputs: See clause 9.17.3.2.
See clause 9.17.2.1 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.17.4.3 SS_NSCE_NSInfoDelivery_Client Request operation
|
API operation name: SS_NSCE_NSInfoDelivery_Client Request
Description: The consumer requests to deliver the network slice information to NSCE client.
Inputs: See table 9.17.3.3-1.
Outputs: See table 9.17.3.4-1.
See clause 9.17.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18 Network Slice Allocation in NSaaS model
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18.1 General
|
When in NSaaS model, the NSCE server performs the Network Slice allocation operation on behalf of the VAL server. The non-trusted 3rd party application (i.e., VAL server) cannot access to the 5GS management system directly. So, the NSCE server needs to perform the authentication and authorization for the registration of VAL server on behalf of 5G MnS.
The Network Slice creation that is triggered by the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards.
The VAL server can identify the Network slice in Network Slice creation request with the Network Slice indicator (e.g., S-NSSAI).
Upon network slice allocation, the NSCE server acts as the network slice provisioning MnS consumer. The NSCE server requests 'AllocacatedNsi' operation to the network slice provisioning MnS producer as specified in 3GPP TS 28.531 [8]. When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer in 5GS performs charging mechanism as specified in 3GPP TS 28.202 [28].
The NSCE server sends the allocated Network Slice information (e.g., S-NSSAI) to the NSCE Client, after the Network Slice allocation to the VAL server is successful.
With the above regards, the NSCE server performs the below for the Network Slice Allocation for the VAL server.
- Network Slice Allocation operation on behalf of VAL Server as specified in TS 28.531 [8]
- Delivery of the Network Slice Allocation result
- Delivery of the allocated Network Slice Information to NSCE client
The VAL server as a Network Slice consumer makes use of the APIs provided from NSCE server to allocate the Network Slice for the Network Slice Lifecycle management for its service.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18.2.1 Network Slice Allocation in NSaaS model
|
This subclause depicts the procedure of the Network Slice Allocation in NSaaS model, when the VAL server needs to allocate the Network Slice, interaction with 5GS via the NSCE server.
Pre-conditions:
1. The VAL server has the network slice information using the procedure defined in clause 9.17.
Figure 9.18.2.1-1: Network Slice Allocation in NSaaS model
1. The VAL server makes a request to order the Network Slice. The VAL server specifies the Network Slice requirements for the VAL service. The Network Slice requirement at the VAL server may be specified with the attributes of GST (which results in NEST) as specified in GSMA NG.116.
2. The VAL server requests the Network Slice allocation with the Network Slice requirements. The Network Slice allocation request includes the VAL Service ID, VAL UE's ID List, and S-NSSAI. The VAL server may provide the prioritized slice identifier list for allocation. The VAL server also provides an endpoint to receive the notification. Optionally, the VAL server may include slice adjustment requirements in the request. e.g maximum and minimum requirement.
3. The NSCE server performs the Network Slice Allocation. If the NSCE server act as NSaaS provider, and the existing allocated network slice could satisfied the Network Slice requirements, the NSCE server allocates the existing network slice to the VAL. Otherwise, the NSCE server as network slice provisioning MnS consumer requests of 'AllocacatedNsi' operation as specified in 3GPP TS 28.531 [8]. If the VAL server provides the Slice adjustment requirements in Network Slice allocation request, then the NSCE server uses the Slice adjustment requirements for slice allocation.
NOTE 1: How the NSCE server performs the slice adjustment is implementation-specific and out of the scope of this specification.
When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer performs charging mechanism as specified in 3GPP TS 28.202 [28].
The NSCE server performs AF-driven guidance for URSP determination to 5GS per VAL UE.
NOTE 2: According to the network operator policy, the NSCE server acting as AF may send the created network slice information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in TS 23.501 [16]). This guidance may create the new route selection parameters to indicate sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic.
4a. The NSCE server sends the result of Network Slice Allocation to the VAL server if notification endpoint is not provided by the VAL server.
4b. The NSCE server sends the result of Network Slice Allocation to the VAL server as a notification message if the endpoint is provided by the VAL server.
NOTE 3: Either step 4a or step 4b will be delivered as a response.
5. The NSCE server delivers the Network Slice Allocation Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 2, using the procedure defined in 9.17.2.2 step 2 – step 4, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS in step 3. The Network Slice Allocation Information contains the VAL service ID, S-NSSAI, and DNN.
NOTE 4: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in clause 6.1.2.2.1 of 3GPP TS 23.503 [17]. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.18.3.1 General
|
The following information flows are specified for Network Slice Allocation:
- Network Slice Allocation request and response.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.