hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.3 SS_NSCE_ Policy_Update operation
|
API operation name: Policy_Update
Description: Providing the policy update to the NSCE server.
Inputs: Refer subclause 9.5.3.4.
Outputs: Refer subclause 9.5.3.5.
See subclause 9.5.2.1.2 for details of the usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.4 SS_NSCE_ Policy_Delete operation
|
API operation name: Policy_Delete
Description: Requesting policy delete to the NSCE server.
Inputs: Refer subclause 9.5.3.6.
Outputs: Refer subclause 9.5.3.7.
See subclause 9.5.2.1.3 for details of the usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.5 SS_NSCE_Policy_harmonization Notify_operation
|
API operation name: Policy_harmonization_Notify
Description: The consumer is notified with result of Policy harmonization .
Inputs: See clause 9.5.3.16
Outputs: None
See clause 9.5.2.1.4 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.6 SS_NSCE_ Policy_Usage_Reporting_Data_Subscribe operation
|
API operation name: Policy_Usage_Reporting_Data_Subscribe
Description: Subscription to the VAL server policy usage reporting data.
Inputs: Refer subclause 9.5.3.8.
Outputs: Refer subclause 9.5.3.9.
See subclause 9.5.2.1.5 for details of the usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.7 SS_NSCE_ Policy_Usage_Reporting_Data_Notification operation
|
API operation name: Policy_Usage_Reporting_Data_Notification
Description: VAL server policy usage reporting data notification to the existing subscription.
Inputs: Refer subclause 9.5.3.10.
Outputs: None
See subclause 9.5.2.1.5 for details of the usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.8 SS_NSCE_NS_Optimization_Report_Retrieval operation
|
API operation name: NSOptimizationReportRetrieval
Description: Providing the network slice optimization report to the VAL server.
Inputs: Refer subclause 9.5.3.14.
Outputs: Refer subclause 9.5.3.15.
See subclause 9.5.2.3 for details of the usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.9 SS_NSCE_NSOptimization_Subscribe Request operation
|
API operation name: Ensce_NSOptimization _ Subscribe
Description: The consumer request for Network Slice Optimization.
Inputs: See clause 9.5.3.11.
Outputs: See clause 9.5.3.12.
See clause 9.5.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.5.4.10 SS_NSCE_NSOptimization_Notification operation
|
API operation name: Ensce_NSOptimization_Notification
Description: The consumer is notified with result of Network Slice Optimization.
Inputs: See clause 9.5.3.13.
Outputs: None
See clause 9.5.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6 Discovery of management service exposure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.1 General
|
A Management Domain (MD) feature/capability is anything of use offered by the management system to the 3rd party application. Therefore, a new feature could be a managed entity, a MnS or management API, any software, hardware, or other functionality – for example, new technology support, new coverage area, new network slice type or instance, new NFs or new network slice subnet type or instance. To be able to utilise capabilities/features of the management system the applications must be made aware of existence of such features and capabilities. All MD features/capabilities come with a pre-configured exposure, where this can be configured by the operator for a given slice. This exposure is used to decide which application can see which information regarding the capability/feature. Exposure refers to the permissions that the 3rd party entity has gained over its use of the management service, e.g., the ability to read, or execute or modify or delete can be considered as different sorts of exposure.
The first procedure (9.6.2.1) provides the NSCE server support for translating the VAL server request to a MnS requirement and the exposure of service/management data related to his request. The second procedure (9.6.2.2) supports the notification to the VAL server, based on a new/modified MnS / capability for a target slice.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.2.1 VAL-triggered MnS discovery procedure
|
In this procedure, the VAL server initially requests the new MnS which are supported by a target slice and based on this request the NSCE server requests from the OAM/MnS registry the MnS discovery. Then, the OAM/MnS registry derives the details to be exposed based on the NSCE server/VAL server permissions and provides the list of MnS for the given slice and the access details via the NSCE server to the VAL server.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
2. The NSCE server is trusted by the OAM, and a contract has been signed between the MNO and NSCE server provider to allow OAM interfaces and/or network slice information exposure.
3. MnS registry at OAM is aware of the allowed MnS and the permissions for a given slice.
Figure 9.6.2.1-1 illustrates a solution for the MnS discovery support.
Figure 9.6.2.1-1: MnS discovery support
The steps of this procedure are as follows:
1. The VAL server sends a Management Service Discovery subscribe request message to NSCE server to indicate a requirement for receiving the expected exposure capability type and the related permissions for a target slice or for a given VAL application.
2. The NSCE server sends a response to the subscription request, indicating a success or failure of the subscription request.
NOTE 1: If CAPIF is used, the API interactions for the MnS discovery subscription shall be compliant with CAPIF as specified in 3GPP TS 23.222.
3. The NSCE server translates the requirement based on the subscription, and in particular identifies the needed exposure capability type and translates it to a MnS exposure requirement. Such translation of the requirement includes the mapping to a list of MnSs (specified in TS 28.532) which are needed for the given slice and VAL server permissions.
4. The NSCE server coordinates with the 5GS and discovers the related network service(s), by triggering the MnS service discovery as specified in TS 28.537[9], clause 5.2.1.3. In particular, NSCE server acts as MnS discovery service consumer (for all MnS needed for a target slice based on VAL requirement) requests from MnS discovery service producer(s) at OAM the discovery of MnS information for the MnS related to the target slice or VAL application. The 5GS, MnS discovery service producer(s) sends the discovery result including related exposure information such as management service identifier, management service information and management service producer information to the NSCE server.
NOTE 2: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5.
5. The NSCE server sends a management service discovery subscription notify message to provide the service/management data based on step 4, including the list of MnS and the corresponding exposure details to the VAL server.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.2.2 OAM-triggered new/modified MnS discovery
|
This procedure includes the case when a new/modified MnS is deployed at the MD for the given slice, and the OAM/MnS registry provides this information directly to VAL server (assuming that VAL server has registered to the MD).
Pre-conditions:
1. VAL server is registered to NSCE server based on clause 9.2.
2. NSCE server has subscribed to OAM / MnS discovery service registry.
Figure 9.6.2.2-1: OAM-triggered new/modified MnS discovery
1. The MnS registry may discover new or modified MnS in the 3GPP MD. Such changes may be due to new/modified management service producers, new managed entities (such as new radio, new technology or new NFs), new/modified technical support (such as support in a new geography or coverage area), availability of new management data, e.g., related to slice performance. An example procedure related to the addition of a new MnS producer is provided in TS 28.537 clause 5.2.1.1.
The MnS discovery service producer when capturing new or modified capability (e.g. new MnS producer) related to the target slice or VAL application identifies the NSCE server which needs to be informed (based on the subscription) on the new/modified capability and derives the details to be exposed to the VAL server (via the NSCE server). Then, the MnS registry sends to the NSCE server the new / modified MnS.
NOTE: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5.
2. The NSCE server determines the VAL server(s) that needs to be notified on the new or modified MnS / MD capability based on their registrations. Then, NSCE server generates and sends a notification with the required information to be provided to the VAL server.
3. The information on the discovered new/modified MnS is sent as a management service discovery notification message from the NSCE server to VAL server.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.3.1 General
|
The following information flows are specified for the MnS discovery support based on 9.6.2 and 9.6.3.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.3.2 Management service discovery subscribe request
|
Table 9.6.4.2-1 describes information elements for the Management service discovery subscribe request from the VAL server to the NSCE server.
Table 9.6.3.2-1: Management service discovery subscribe request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
The identifier of the VAL service for which the MnS discovery request applies
Network slice related Identifier(s)
O
The slice identifier, if known by the VAL server
Exposure capability requirement
O
The requirement includes indication of the requested permissions for exposing information related to the target slice. Also, the requirement may include the exposure capability type which is supported (e.g. via EGMF or directly to MnS producer)
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.3.3 Management service discovery subscribe response
|
Table 9.6.3.3-1 describes information elements for the Management service discovery subscribe response from the NSCE server to the VAL server.
Table 9.6.3.3-1: Management service discovery subscribe response
Information element
Status
Description
Result
M
The result of the subscription request (positive or negative acknowledgement)
> Cause
O
(see NOTE)
Indicates the cause of failure.
NOTE: May only be present if the result is failure.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.3.4 Management service discovery notify
|
Table 9.6.3.4-1 describes information elements for the Management service discovery notify message from the NSCE server to the VAL server.
Table 9.6.3.4-1: Management service discovery notify
Information element
Status
Description
VAL service ID
M
The identifier of the VAL application
Management Domain/System ID
M
The identifier of the management system/domain of interest
List of MnS IDs / MnS producer IDs
M
The list of identifiers of the needed MnSs / MnS producers
>MnS capability
M
The capability per needed MnS. Such capability may related to the managed elements such as considerations for radio, technology, coverage or NFs
>MnS permissions
O
Allowed permissions of the VAL server over the MnS, e.g. whether it is allowed to read, write, delete, and/or update.
Network slice related Identifier(s)
O
The slice identifier which is mapped to the VAL application and the list of MnSs.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.4 APIs
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.4.1 General
|
Table 9.6.4.1-1 illustrates the NSCE APIs for the MnS discovery feature.
Table 9.6.4.1-1: List of APIs for the MnS discovery feature
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_Management_Service_Discovery
Management_Service Discovery
VAL server
Subscribe/Notify
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.4.2 SS_NSCE_Management_Service Discovery
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.4.2.1 General
|
API description: This API enables the VAL server to communicate with the network slice capability enablement server for requesting management service discovery over NSCE-S.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.6.4.2.2 SS_NSCE_Management_Service Discovery
|
API operation name: Management_Service Discovery
Description: Providing for Management_Service Discovery subscribe to the NSCE server and receiving a confirmation.
Known Consumers: VAL server.
Inputs: See subclause 9.6.2.1 (step 1)
Outputs: See subclause 9.6.2.1 (step 4), 9.6.2.2 (step 3)
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7 Network slice related performance and analytics monitoring
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.1 General
|
The NSCE server supports the end to end network slice related performance and analytic monitoring capability exposure. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the Core Network or the VAL end users), performs the data organizations and aggregations and expose the processed data to VAL servers for monitoring. Following clauses are for the procedures, information flows and APIs for Network slice related performance and analytics monitoring request and Network slice related performance and analytics reporting respectively. The procedure in clause 9.7.2.1 is for task creation of the network slice performance and analytics monitoring. The procedure in clause 9.7.2.2 is for the performance and analytics data retrieving when the data is available. The procedure in clause 9.7.2.3 is for multiple network slices performance and analytics consolidated report.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.2.1 Network slice related performance and analytics monitoring job creation request
|
For network slice related performance and analytics monitoring job creation capabilities exposed to the VAL server, the VAL server triggers the procedure by sending the network slice related performance and analytics monitoring job creation request to NSCE server as Figure 9.7.2.2-1 shows:
Figure 9.7.2.1-1: Request Network slice related performance and analytics job creation monitoring
1. The VAL server sends a request to NSCE server to create the Network slice related performance and analytics monitoring job to collect the desired service/VAL service specific performance and analytics data, the detailed content of the reported data depends on the type of the VAL services. The required end-to-end network slice related data performance data are indicated by Perflist IE as described in table 9.7.3.2-1.
2. The NSCE server shall check if the VAL server is authorized to request the network slice performance and analytics data monitoring job creation.
3. NSCE server determines the requested data needed to collect from network side and collects the performance measurements and analytics data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[7] is utilized, e.g., packet delay, radio resource utilization. For CN functions, the APIs of Nnwdaf_AnalyticsInfo service defined in clause 7.3, TS 23.288 [4] is utilized, e.g., slice load level related network data analytics, slice load level related network data analytics.
4. Optionally, NSCE server retrieves the KQI data of services, the QoE data and the end user’s information from NSCE client.
NOTE 1: The Data collection from NSCE client follows the mechanism defined in SA4 EVEX in TS 26.531 clause 5.6.
NOTE 2: How the collected data is stored in the NSCE server is implementation based.
5. NSCE server responds to VAL server to inform the VAL server if the monitoring request is succeed.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.2.2 Network slice related performance and analytics report subscription and report
|
For network slice related performance and analytics result subscription and report, the VAL server triggers the procedure by sending the network slice related performance and analytics report subscription to NSCE server, the NSCE server reports the performance and analytics report after the subscription is succeed, as Figure 9.7.2.2-1 shows:
Figure 9.7.2.2-1: Network slice related performance and analytics report subscription and report
1. The VAL server subscribes to the required performance and analytics report.
2. The NSCE server response to the VAL server to indicate whether the report is successfully generated and ready.
3. NSCE server correlates the performance data of network slice instance, the analytics data of group of UEs and the KQI/QoE data to generate the performance data and analytics data report as required by VAL server.
4. NSCE server sends the performance report Notify to VAL server if the report is ready.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.2.3 Multiple slices related performance and analytics consolidated report request
|
Based on preferred performance report request from the vertical applications, the consolidated performance report for dedicated service from multiple slices (PNI-NPN slice and PLMN slice of one network) can be offered to trusted third-party AF.
Figure 9.7.2.3-1 illustrates the procedure of multiple slices coordinated performance and analytics report service from VAL server to NSCE server.
Pre-conditions:
1. The network slice enabler layer is capable to interact with PLMN 5GC or OAM system to handle slices of PLMN and its PNI-NPNs.
2. PNI-NPNs are deployed as network slices of the PLMN.
3. NSCE server has subscribed for MDE and NWDAF analytics for the managed slices of PLMN and PNI-NPN.
Figure 9.7.2.3 -1: Multiple slices performance and analytics consolidated report process
1. The VAL server initiates multiple slices related performance and analytics consolidated report request towards the NSCE server. The request includes VAL server ID, VAL service ID. The message also includes application key performance indicator (such as end-to-end delay, throughput, etc.) list and monitoring period.
2. Upon receiving the request from the VAL server to manage the network slice QoS monitoring report, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized, the NSCE server replies with failure response.
3. The NSCE server makes mapping from application ID that received from VAL server to slice identities (S-NSSAIs allocated in each network) and retrieves the PNI-NPN slice related status information from MDE/NWDAF, i.e. analytics data specified in 3GPP TS 28.104 [21] and TS 23.288 [4].
4. The NSCE server retrieves the PLMN slice related performance information from MDE/NWDAF. The services of Nnwdaf_AnalyticsInfo service defined in clause 7.3 of TS 23.288 [4] and analytics data as specified in 3GPP TS 28.104 [21] can be utilized.
5. The NSCE server verifies and analyses analytics data of network slice instances that is received from MDE/NWDAF about both PNI-NPN and PLMN slices, then NSCE server makes consolidated performance report among different kinds of network slices in specific period of time/location zone.
6. The NSCE server sends the multiple slices related performance and analytics consolidated report response towards VAL server including application key performance indicator (such as end-to-end delay, throughput, etc. ) list and monitoring period.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3.1 General
|
The following information flows are specified for Network slice related performance and analytics monitoring:
- Network slice related performance and analytics monitoring job creation request and response
- Network slice related performance and analytics monitoring report subscription
- Network slice related performance and analytics monitoring report Notify
- Multiple slices related performance and analytics consolidated report request and response
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3.2 Network slice related performance and analytics monitoring job creation request and response
|
Table 9.7.3.2-1 and Table 9.7.3.2-2 describe information elements for the network slice related performance and analytics monitoring job creation request and response between the VAL server and the NSCE server.
Table 9.7.3.2-1: Network slice related performance and analytics monitoring job creation request
Information element
Status
Description
VAL information
M
The information of the VAL server
Performance Monitoring Request ID
M
Identifier of the performance and analytics monitoring job
Performance and analytics monitoring metrics
M
The information of performance and analytics monitoring
> VAL service identity
M
Identifier of the VAL service to be monitored
>PerfList
M
The list of performance to be monitored
>> PerfName
M
The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load.
> Network slice related Identifier(s)
O
Identifier(s) of the network slice to be monitored
>StartTime
M
The start time point of the performance and analytics monitoring
>EndTime
O
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
Table 9.7.3.2-2: Network slice related performance and analytics monitoring job creation response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics monitoring request
> Performance Monitoring Request ID
O
(see NOTE 1)
Identifier of the performance and analytics monitoring job
>StartTime
O
(see NOTE 1)
The start time point of the performance and analytics monitoring
>EndTime
O
(see NOTE 2)
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
>Cause
O
(see NOTE 3)
Indicates the cause of VAL performance and analytics monitoring request failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2 May only be present if the result is success.
NOTE 3: Shall be present if the result is failure and shall not be present otherwise.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3.3 Network slice related performance and analytics report subscription
|
Table 9.7.3.3-1 and 9.7.3.3-2 describe information elements for Network slice related performance and analytics report subscription from the NSCE server to the VAL server.
Table 9.7.3.3-1: Network slice related performance and analytics report subscription
Information element
Status
Description
VAL information
M
The information of the VAL server
>VAL server ID
M
The identifier of the VAL server
Report ID
M
Identifier of performance and analytics results the report
Report Information
M
The information of performance and analytics report retrieving
> VAL service identity
M
Identifier of the VAL service of which the performance and analytics results are required
> Network slice related Identifier(s)
O
Identifier(s) of the network slice
>StartTime
M
The start time point of the performance and analytics report
>EndTime
M
The end time point of the performance and analytics report
>Notification time interval
O
The time interval that the network slice related performance and analytics report are supposed to be notified
>PerfList
M
The list of performance to be reported
>>PerfName
M
The name of the performance to be reported
Table 9.7.3.3-2: Response of Network slice related performance and analytics report subscription
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics subscription
>Report ID
O
(see NOTE 1)
Identifier of the performance and analytics report Id
>Cause
O
(see NOTE 2)
Indicates the cause of VAL performance and analytics subscription failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2 Shall be present if the result is failure and shall not be present otherwise.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3.4 Network slice related performance and analytics report Notify
|
Table 9.7.3.4-1 and 9.7.3.4-2 describe information elements for Network slice related performance and analytics report Notify from the NSCE server to the VAL server.
Table 9.7.3.4-1: Network slice related performance and analytics report Notify
Information element
Status
Description
VAL information
M
The information of the VAL server
>VAL server ID
M
The identifier of the VAL server
>Network slice related performance and analytics report
M
Network slice related performance and analytics report as defined in Table 9.7.3.4-2
Table 9.7.3.4-2: Network slice related performance and analytics report
Information element
Status
Description
Report ID
M
Identifier of the report
PerfResultFile
CM
(see NOTE 1)
PerfResultFile contains one or more PerfResult
>PerfResult
CM
Information element containing the VAL service identity or S-NSSAI followed by a list of result values for the aggregated or analyzed network slice related performance
>VAL service identity
M
Identifier of the VAL service of which the performance and analytics results are reported
> Network slice related Identifier(s)
O
Identifier(s) of the network slice
>ResultsValueList
List of ResultsValue
>>ResultsValue
M
Information element containing the perfName and perfValue.
>>>PerfName
M
The name of the performance to be reported
>>>PerfValue
M
The corresponding value of the monitored performance
Failure response
CM
(see NOTE 2)
Indicates that network slice related performance and analytics results reporting failed.
>Cause
CM
(see NOTE 2)
Indicates the cause of network slice related performance and analytics results report failure
NOTE 1: Information element shall be present when the network slice related performance and analytics results retrieving is successful.
NOTE 2: Information element shall be present when the network slice related performance and analytics results retrieving is failure.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.3.5 Multiple slices related performance and analytics consolidated report request and response
|
Table 9.7.3.x-1 and Table 9.7.3.x-2 describe information elements for the multiple slices related performance and analytics consolidated report request and response between the VAL server and the NSCE server.
Table 9.7.3.5-1: Multiple slices related performance and analytics consolidated report request
Information element
Status
Description
VAL information
M
The information of the VAL server
Performance Monitoring Request ID
M
Identifier of the performance and analytics monitoring
Performance and analytics monitoring metrics
M
The information of performance and analytics monitoring
> VAL service identity
M
Identifier of the VAL service to be monitored
>PerfList
M
The list of performance to be monitored
>> PerfName
M
The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load.
> Network slice related Identifier(s)
O
Identifier(s) of the network slice to be monitored
>StartTime
M
The start time point of the performance and analytics monitoring
>EndTime
M
The end time point of the performance and analytics monitoring.
> Report ID
M
Identifier of performance and analytics report.
Table 9.7.3.5-2: Multiple slices related performance and analytics consolidated report response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics monitoring request
>StartTime
O
(see NOTE 1)
The start time point of the performance and analytics monitoring
>EndTime
O
(see NOTE 1)
The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated.
>Report ID
O
(see NOTE 1)
Identifier of the report
>VAL service identity
O
(see NOTE 1)
Identifier of the VAL service of which the performance and analytics results are reported
>>Network slice related Identifier
O
(see NOTE 1)
Identifier of the network slice. One VAL service can be offerred on one or more network slices
>>>ResultsValue
O
(see NOTE 1)
Information element containing the perfName and perfValue
>>>>PerfName
O
(see NOTE 1)
The name of the performance to be reported
>>>>PerfValue
O
(see NOTE 1)
The corresponding value of the monitored performance
>Cause
O
(see NOTE 2)
Indicates the cause of VAL performance and analytics monitoring request failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: Shall be present if the result is failure and shall not be present otherwise.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4 APIs
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4.1 General
|
Table 9.7.4.1-1 and 9.7.4.1-2 illustrate the API for network slice related performance and analytics monitoring.
Table 9.7.4.1-1: SS_NSCE_PerfMonitoring API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_PerfMonitoring
Perf_Monitoring_Request
Request /Response
VAL server
Table 9.7.4.1-2 SS_NSCE_PerfResultReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE__PerfReportSubscription
Perf_ PerfReport_Subscription
Subscription/response
VAL Server
Table 9.7.4.1-3: SS_NSCE_PerfReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_PerfReporting
Perf_Report
Notify
VAL Server
Table 9.7.4.1-4: SS_NSCE_MultiSlicePerfReport API
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_MultiSlicePerfReport
Multi_Slice_Perf_Report
Request /Response
VAL Server
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4.2 SS_NSCE_PerfMonitoring API
|
API operation name: Perf_Monitoring
Description: The consumer requests to monitor network slice related performance and analytics.
Known Consumers: VAL server.
Inputs: See table 9.7.3.2-1.
Outputs: See table 9.7.2.2-2.
See clause 9.7.2.1 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4.3 SS_NSCE_PerfReportSubscription API
|
API operation name: Perf_Result_Reporting
Description: The consumer requests to report network slice related performance and analytics.
Known Consumers: VAL server.
Inputs: See table 9.7.3.3-1.
Outputs: See table 9.7.3.3-2.
See clause 9.7.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4.4 SS_NSCE_PerfReport API
|
API operation name: Perf_ Report
Description: The consumer get notify of network slice related performance and analytics report.
Known Consumers: VAL server.
Inputs: See table 9.7.3.4-1.
Outputs: See table 9.7.3.4-2.
See clause 9.7.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.7.4.5 SS_NSCE_MultiSlicePerfReport API
|
API operation name: Multi_Slice_Perf_Report
Description: The consumer requests to get multiple slices related performance and analytics consolidated report.
Known Consumers: VAL server.
Inputs: See table 9.7.3.5-1.
Outputs: See table 9.7.3.5-2.
See clause 9.7.2.3 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8 Information collection from NSCE server(s)
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.1 General
|
The collected information by NSCE server could be exposed to other NSCE server(s) to optimize network resource allocation, based on the agreement among the NSCE servers. Then the NSCE server providing network slice related information acts as the producer, while the NSCE server obtaining network slice related information is the consumer.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.2.1 Information collection from NSCE server(s) subscribe request and response
|
Pre-condition:
1. The producer NSCE server #2 has agreement with consumer NSCE server #1 to provide the collected slice information.
Figure 9.8.2.1-1: Information collection from NSCE server(s) subscribe request and response
1. The NSCE server#1 sends out the information collection subscribe request with expected period and interested slice ID, e.g., List of SNSSAI. This step could be done by pre-configuration.
2. The NSCE server #2 shall check if the NSCE server #1 is authorized to get the network slice information.
3. After authentication, the NSCE server #2 collects slice information as defined in clause 9.7.2.1 step3, step4.
NOTE: When the producer NCSE server is edge NSCE server, only local information is collected and provided.
4. The NSCE server #2 sends collected slice information to NSCE server #1.
5. The NSCE server #1 may process the collected slice information (such as information aggregation), if needed.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.2.2 Information collection from NSCE server(s) Notify
|
Figure 9.8.2.2-1: Information collection from NSCE server(s) Notify
1. Once the reporting period is reached or the threshold is crossed, the NSCE server #2 sends information collection notify to NSCE server #1.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.3 Information flows
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.3.1 General
|
The following information flows are specified for Information collection from NSCE server(s):
- Information collection from NSCE server(s) subscribe request, response and notify;
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.3.2 Information collection from NSCE server(s) subscribe request
|
Table 9.8.3.2-1 describes information elements for the Information collection from NSCE server(s) subscribe request from the consumer NSCE server to the producer NSCE server(s).
Table 9.8.3.2-1: Information collection from NSCE server(s) subscribe request
Information element
Status
Description
Requester Identifier
M
Unique identifier of the requester (i.e. NSCE server ID).
Security credentials
M
Security credentials resulting from a successful authorization for the NSCE service.
Notification Target Address
O
The Notification Target Address (e.g. URL) where the notifications destined for the requester should be sent to.
List of S-NSSAI(s)
M
Identifier of the interested network slice
>QoS type indicator
O
QoS metric type including latency, throughput, jitter, etc.
>Threshold
O
Threshold of QoS metrics
>Reporting period
O
Indicating the metrics reporting period
>Immediate reporting flag
O
Indicating the request needs immediate reporting or not
Proposed expiration time
O
Proposed expiration time for the subscription
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.3.3 Information collection from NSCE server(s) subscribe response
|
The information elements specified in the Table 9.8.3.3-1 is used for the Information collection from NSCE server(s) subscribe response sent from the producer NSCE server to the consumer NSCE server.
Table 9.8.3.3-1: Information collection from NSCE server(s) subscribe Response
Information element
Status
Description
Result
M
Indicates the success or failure of the performance and analytics subscription.
> Subscription ID
O
(see NOTE 1)
Subscription identifier corresponding to the subscription.
>Network slice related performance and analytics report
O
(see NOTE 2)
Network slice related performance and analytics report as defined in Table 9.7.3.4-2
> Cause
O
(see NOTE 3)
Indicates the cause of request failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: May only be present if the result is success.
NOTE 3: May only be present if the result is failure.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.3.4 Information collection from NSCE server(s) notify
|
The information elements specified in Table 9.8.3.4-1 are used for the information collection from NSCE server(s) notify sent from the producer NSCE server to the consumer NSCE server.
Table 9.8.3.4-1: Information collection from NSCE server(s) Notify
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
>Network slice related performance and analytics report
M
Network slice performance and analytics (i.e. slice load) with network slice identifier(i.e. S-NSSAI)
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.4 APIs
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.4.1 General
|
Table 9.8.4.1-1 illustrates the API for information collection from NSCE server(s).
Table 9.8.4.1-1: API for Information collection from NSCE server(s)
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_InfoCollection
Subscribe
Subscribe/Response
NSCE server
Notify
Notify
NSCE server
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.4.2 SS_NSCE_InfoCollection_Subscribe operation
|
API operation name: InfoCollection_Subscribe
Description: The consumer subscribes for Information collection from NSCE server(s).
Inputs: See clause 9.8.3.2.
Outputs: See clause 9.8.3.3.
See clause 9.8.2.1 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.8.4.3 SS_NSCE_InfoCollection_Notify operation
|
API operation name: InfoCollection_Notify
Description: The consumer is notified with result of information collection from NSCE server(s).
Inputs: See clause 9.8.3.4
Outputs: None
See clause 9.8.2.2 for details of usage of this operation.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.9 Predictive slice modification in edge based NSCE deployments
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.9.1 General
|
In this feature, the NSCE server initially receives an expected/predicted UE location/mobility change request outside an EDN service area for one or more UEs within the VAL application session (e.g. such session can be an indirect V2V session or a multiplayer gaming session). Then, the source NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target EDN. Thereafter, NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change) e.g. a slice subnet resource adaptation to allow for optimizing the application performance at the target area. Based on this decision/recommendation, it provides the action to the OAM and supports the re-mapping of NSCE server for the NSCE client proactively, before UE mobility happens.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.9.2 Procedure
| |
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.9.2.1 Procedures on predictive slice modification in edge based NSCE deployments
|
In the procedure shown in Figure 9.9.2.1-1, a mechanism is provided to allow for slice modification when a vertical application of single or group of VAL UEs migrates (or is expected/predicted to migrate) to a different EDN supported by different NSCE server.
Pre-conditions:
1. The VAL server has subscribed to the network slice capability enablement server
2. The VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to NSCE server#1 (S-NSCE server).
3. The S-NSCE server has already discovered the T-NSCE server and its area of coverage.
4. The VAL server is subscribed to and received prediction of UE location change.
Figure 9.9.2.1-1: Support for predictive slice modification in distributed NSCE server deployments
1. The VAL server sends to S-NSCE server an application service continuity requirement request due to predicted/expected UE or group UE mobility to a target service area covered by a different EDN.
NOTE: Such UE predicted mobility at the VAL server can be based on UE mobility analytics received by NWDAF or can be predicted by the VAL layer (VAL server or VAL UE).
2. S-NSCE server sends an application service continuity requirement response to the VAL server as positive or negative acknowledgement.
3. S-NSCE server determines to query the underlying 3GPP system on the slice availability and conditions at the target service area (based on step 1 requirement). Such query may be in form of a request/response and include:
a. S-NSCE server interacting with 5GC to query the UE specific information (location, UE connection capabilities) as well as network conditions (network monitoring from NEF) and/or slice related analytics on the slice load (from NWDAF as specified in TS 23.288 [4]).
b. S-NSCE server may also interact with OAM to query on the target slice availability and the up-to-date configured slice parameters e.g. slice RRM policies, modification of the NSI/NSSI resources (see TS 28.531 [8], 5.1.12) at the target service area and measurements for the slice at the target area.
4. S-NSCE server evaluates whether new NSCE service area supports slice #1 and if slice #1 offers similar performance in target area.
5. If the current slice doesn't fulfil these requirements, S-NSCE sends to the T-NSCE server (covering the target area) a service continuity negotiation request (including the VAL application service continuity requirement and optionally a proposed action) to negotiate on the trigger action.
6. T-NSCE server determines the need for a slice lifecycle change at the target area and translates this to a trigger action. This trigger action can be based on the proposed action in step 5 and can be a requested slice modification or the slice #1 creation/instantiation at the target area (this may happen if a group of UEs are moving to the target area and use slice #1, so it may be beneficial to create slice #1 at the target area).
7. T-NSCE server sends to the S-NSCE server a service continuity negotiation response including the determined trigger action.
8. The S- or T-NSCE server may send the trigger action as a slice modification trigger request to the slice provisioning MnS producer at OAM (e.g. slice modification for network slice) to extend slice availability to the target service area based on the expected/predicted VAL UE or VAL group mobility. As response to the trigger action, the provisioning MnS producer provides a slice modification trigger response to the corresponding NSCE server with a positive or negative result.
9. After the slice lifecycle change execution (based on the indication in step 5), the S-NSCE server sends a notification to the VAL server and optionally to the VAL client via S-NSCE client
10. If the NSCE client needs to be remapped to different NSCE server (due to the expected change of UE location), the NSCE client establishes a new connection with T-NSCE and terminates the one with S-NSCE (in case of subscription-based interaction), or in case of request-based interaction, it updates the mapping at the client side, and maintains the new NSCE server address / ID for the target NSCE area.
|
a89a0ce5789287ec186d94e36b976f2e
|
23.435
|
9.9.3 Information flows
| |
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
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.