hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.18.3.2 Network Slice Allocation | Table 9.18.3.2-1 and Table 9.18.3.2-2 describe information elements for Network Slice Allocation request and response between the VAL server and the NSCE server.
Table 9.18.3.2-1: Network Slice Allocation request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
VAL service ID
M
Identifier of the application service
VAL UE's ID List
O
The list of VAL UE IDs for which the request applies
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).
Network slice related Identifier(s)
O
The slice identifier(s) which can be in a prioritized order.
Network Slice requirements
O
The properties of network slice related requirement. If Service Profile is known by the VAL server, it can be provided to the NSCE server. The GST defined by GSMA (see clause 2.2 in [5]) and the performance requirements defined in clause 7 TS 22.261 [6] are all considered as input for it.
Slice adjustment requirements
O
Indicates the adjustment for slice requirements
Notification endpoint
O
Indicates the VAL server endpoint to receive notification.
Table 9.18.3.2-2: Network Slice Allocation 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 allocated 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
>Failed Network Slice Info List
O
(see NOTE 2)
Indicates the list of network slice info which cannot be allocated by NSCE server.
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
Table 9.18.3.2-3: Network Slice Allocation notification
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 allocated 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
>Failed Network Slice Info List
O
(see NOTE 2)
Indicates the list of network slice info which cannot be allocated by NSCE server.
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.18.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.18.4.1 General | Table 9.18.4.1-1 illustrates the API for Network Slice Allocation.
Table 9.18.4.1-1: SS_NSCE_NSAllocation
API Name
API Operations
Operation
Semantics
Consumer(s)
SS_NSCE_NSAllocation
NSAllocation_Request /Response
Request /Response
VAL server |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.18.4.2 SS_NSCE_NSAllocation_Request /Response operation | API operation name: SS_NSCE_NSAllocation_Request /Response
Description: The consumer requests the network slice allocation.
Inputs: See table 9.18.3.2-1.
Outputs: See table 9.18.3.2-2.
See clause 9.18.2.1 for details of usage of this operation. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.19 Authorization and authentication | VAL server authorization and authentication are specified in 3GPP TS 33.434 [22], clause 5.1.1.8. Annex A (informative): Deployment models A.1 Deployment scenarios A.1.1 General Based on the network slicing capability of the S-NSSAI granularity provided by SA2 and the network slicing capability of the NSI/S-NSSAI granularity provided by SA5, the NSCE service is provides network slicing management and control capabilities in the S-NSSAI granularity for vertical industries. A network slice can have only one owner and one NSCE service provider. NSCE service provider and slice owner can be different. For example the slice owner is VAL server, but the NSCE service provider is MNO. This clause describes examples of deployment models with respect to different deployment scenarios as follows. A.1.2 Centralized NSCE deployment Figure A.1.2 provides a example of centralized deployment of NSCE server whose service area covering the whole PLMN. It is also possible slice coverage area to be smaller than the NSCE service area. The network slice capability enablement service is provided with the view of whole PLMN in this scenario. Figure A.1.2: Illustration of centralized NSCE deployment A.1.3 Distributed NSCE deployment The distributed deployment refers to the deployment model in which multiple NSCE servers are deployed by same provider, whose service area only covers some specific areas as shown below (based on geographical coordinates or TA list(s)). Figure A.1.3: Illustration of distributed NSCE deployment When there are multiple NSCE servers managed by same provider, NSCE server(s) can be subscribed for providing the network slice statistics to another NSCE server to provide a global view. There can be two use cases to provide the NSCE service in the distributed deployment: One use case is that the distributed deployed NSCE is about a slice service area which is equivalent to the edge/NPN’s service area. For this scenario, if the distributed deployed NSCE wants to access the NEF/NWDAF/NSACF services or to receive policies from OAM, it needs to interact to the global NSCE. A further use case could be that some NSCE services (e.g. MnS discovery) are locally provided to VAL servers (for example as a micro-service), whereas other capabilities are provided for the whole PLMN area. So, the distributed NSCE includes a subset of capabilities which are edge native. The local deployment of such capabilities can allow for more efficient services to the VAL servers (e.g. for QoS verification, the edge deployed NSCE can receive more timely KQI/QoE measurements and can process them locally before triggering an event). A.1.4 NPN NSCE deployment The NSCE architecture supports the deployment that NSCE server is deployed in NPN. Figure A.1.4 shows a deployment example of NSCE server deployment in the NPN. This case is valid if a geographical match between slice coverage area, NPN coverage area and NSCE service area is pre-configured. The matching may be pre-configured in the NSCE server by network operator based on the TA list or geographical coordinates. The NSCE server is deployed in Non-public network to provide the network slice capabilities exposure application service based on the interaction with NPN-5GC and NPN management system. Figure A.1.4: Illustration of NPN NSCE deployment A.1.5 Edge NSCE deployment The NSCE architecture supports the depolyment that the NSCE server is deployed in EDN as an EAS to provide the network slice capabilities exposure application service, based on the interaction with 5GS pertaining the network slice, and edge computing management system. Figure A.1.5 shows the edge NSCE deployment cases when the NSCE server is deployed in the EDN using LADNs as described in Annex A.2.4 of TS 23.558 [22]. This case is valid if a geographical match between slice coverage area, LADN service area (which is EDN service area) and NSCE service area is pre-configured in the NSCE server. The matching can based on the TA list or geographical coordinates. Figure A.1.5: Illustration of edge NSCE deployment A.2 Deployment of NSCE server(s) in relation to VAL server and 3GPP system To support the centralized/distributed deployment, the NSCE server(s) will have different deployment models and different relation with VAL server and 3GPP system. A.2.1 Centralized NSCE deployment The NSCE server can be deployed in single PLMN operator domain (as a SEAL server as specified in Figure 8.2.1-1 TS 23.434), deployed in VAL service provider domain by vertical (as a SEAL server as specified in Figure 8.2.2-1 TS 23.434), or deployed outside of both the VAL service provider domain and PLMN operator domain i.e. in 3rd party domain (as a SEAL server as specified in Figure 8.2.3-1 TS 23.434). The deployment of NSCE server(s), with connections to 3GPP network systems in multiple PLMN operator domains (as a SEAL server as specified in Figure 8.2.2-2) is also supported. When the vertical consumer wants to get NSCE services in two countries which are operated by two different MNOs, the NSCE service provider has to interact with two 3GPP network systems. The NSCE server is either deployed in the VAL service provider domain or deployed separately in the 3rd party domain. A.2.2 Distributed NSCE deployment The NSCE servers can be distributed in multiple PLMN domains (as a SEAL server as specified in TS 23.434 Figure 8.2.1-2, Figure 8.2.1-3), or distributed in single PLMN operator domain (as a SEAL server as specified in TS 23.434 Figure 8.2.1-4). The NSCE servers can also distributed in VAL service provider domain by vertical (as a SEAL server as specified in TS 23.434 Figure 8.2.2-3), or distributed deployed in 3rd party domain by 3rd party. The VAL server can communicate with multiple NSCE servers via NSCE-S as long as other NSCE servers are discovered and accessible. Or, the VAL server can communicate with other NSCE servers via NSCE-E if needed. A.3 Deployment of NSCE server(s) in relation to SEAL The NSCE server(s) supports standalone deployment independent with other SEAL services, it can interact with other SEAL service(s) via SEAL-X interface as specified in Clause 6.2 TS 23.434, . The NSCE service(s) supports combined deployment with other SEAL services, it can interact with other SEAL service via service API as specified in clause 15 TS 23.434. Annex B (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2022-06 SA6#49-bis-e TS skeleton 0.0.0 2022-07 SA6#49-bis-e TS Skeleton agreed in SA6#49-bis-e: S6-221640, Implemented pCRs approved in SA6#49-bis-e: S6-221641, S6-221642, S6-221643, S6-221822, S6-221818. 0.1.0 2022-09 SA6#50-e Implemented pCRs approved in SA6#50: S6-222146, S6-222197, S6-222407 Editorial changes by the rapporteur. 0.2.0 2022-10 SA6#51-e Implemented pCRs approved in SA6#51: S6-223036, S6-223035, S6-222901, S6-222764. Editorial changes by the rapporteur. 0.3.0 2022-11 SA6#52 Implemented pCRs approved in SA6#51: S6-223449, S6-223517, S6-223595, S6-223557, S6-223207, S6-223477 Editorial changes by the rapporteur. 0.4.0 2023-01 SA6#52-bis-e Implemented pCRs approved in SA6#52-bis-e: S6-230053, S6-230054, S6-230353, S6-230467, S6-230355, S6-230359, S6-230379, S6-230397, S6-230459, S6-230360, S6-230460, S6-230352, S6-230403, S6-230136, S6-230417, S6-230419, S6-230420, S6-230421, S6-230422, S6-230461 Editorial changes by the rapporteur. 0.5.0 2023-03 SA6#53 Implemented pCRs approved in SA6#53: S6-230960, S6-230961, S6-230616, S6-231027, S6-231028, S6-230997, S6-231069, S6-230967, S6-231009, S6-230968, S6-230598Editorial changes by the rapporteur. 0.6.0 2023-03 SA#99 SP-230272 Presentation for information at SA#99 1.0.0 2023-03 SA#99 SP-230346 Correction of implementation of pCR S6-231009 and presentation for information at SA#99 1.1.0 2023-04 SA6#54 Implemented pCRs approved in SA6#54: S6-231499, S6-231616, S6-231617, S6-231618, S6-231619, S6-231467, S6-231259, S6-231258, S6-231620, S6-231338, S6-231445, S6-231621 Editorial changes by the rapporteur. 1.2.0 2023-05 SA6#55 Implemented pCRs approved in SA6#55: S6-232092, S6-231800, S6-231802, S6-231803, S6-232093, S6-231805, S6-231806, S6-232094, S6-232095, S6-232096. Editorial changes by the rapporteur. 1.3.0 2023-06 SA#100 SP-230686 Presentation for approval at SA#100 2.0.0 2023-06 SA#100 SP-230686 MCC Editorial update for publication after TSG SA approval (SA#100) 18.0.0 2023-12 SA#102 SP-231561 0002 2 F Solve the EN in registration 18.1.0 2023-12 SA#102 SP-231571 0003 1 B Solve EN in clause 9.2 19.0.0 2023-12 SA#102 SP-231571 0004 3 B Enhancements to Network slice allocation procedure in NSaaS model 19.0.0 2023-12 SA#102 SP-231571 0005 3 B Enhancements to Slice requirement verification and alignment capability 19.0.0 2023-12 SA#102 SP-231571 0006 1 F Correction of reference 19.0.0 2024-03 SA#103 SP-240307 0009 1 A Fault diagnosis subscription request 19.1.0 2024-03 SA#103 SP-240307 0011 3 A Add late notification to the network slice adaptation procedures 19.1.0 2024-03 SA#103 SP-240319 0017 3 B Enhancements to Slice requirement verification and alignment capability 19.1.0 2024-03 SA#103 SP-240307 0018 1 A Correction of Area of interest 19.1.0 2024-03 SA#103 SP-240307 0018 1 A IE Name and Reference Corrections 19.1.0 2024-06 SA#104 SP-240760 0021 1 A Correction of Procedure name 19.2.0 2024-06 SA#104 SP-240774 0022 1 B Enhancements to Slice requirement verification and alignment capability 19.2.0 2024-06 SA#104 SP-240760 0024 3 A Update on predictive slice modification in Inter-PLMN based slice service continuity 19.2.0 2024-06 SA#104 SP-240760 0026 1 A UE IP address preservation indicator deletion 19.2.0 2024-09 SA#105 SP-241215 0030 2 A Adding a note on predictive slice modification in inter-PLMN based slice service continuity 19.3.0 |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 1 Scope | The present document specifies the procedures, information flows and APIs necessary for Application Data Analytics Enablement SEAL Service. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3] 3GPP TS 26.531: "Data Collection and Reporting; General Description and Architecture"
[4] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[5] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".
[6] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[7] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[8] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs".
[9] 3GPP TS 23.501: “System architecture for the 5G System”.
[10] GSMA NG.116 - Generic Network Slice Template.
[11] 3GPP TS 22.261: “Service requirements for the 5G system”.
[12] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS)".
[13] 3GPP TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".
[14] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[15] 3GPP TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
[16] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[17] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[18] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[19] 3GPP TS 23.482: “Functional architecture and information flows for AIML Enablement Service”. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 3 Definitions of terms and abbreviations | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
ADAES Application Data Analytics Enabler Server
ADAEC Application Data Analytics Enabler Client
A-ADRF Application layer - Analytical Data Repository Function
A-DCCF Application layer - Data Collection and Coordination Function
ASP Application Service Provider
DNAI Data Network Access Identifier
EAS Edge Application Server
EEL Edge Enabler Layer
EES Edge Enabler Server
FLS Fused Location Server
LMS Location Management Server
MDAS Management Domain Analytics Service
NSCE Network Slice Capability Enablement
NWDAF Network Data Analytics Function
OAM Operation, Administration and Maintenance
RNIS Radio Network Information Service
RTT Round-Trip Time
VAL Vertical Application Layer |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 4 Architectural requirements | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 4.1 General Description | The following clauses specify the requirements for application data analytics enablement service. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 4.2 General Requirements | [AR-4.2-a] The ADAE client and the ADAE server shall support one or more VAL applications.
[AR-4.2-b] Supported ADAE capabilities shall be offered as APIs to the VAL applications.
[AR-4.2-c] The ADAE shall support interaction with 3GPP network system to consume network and management data analytics services.
[AR-4.2-d] The ADAE client shall be capable to communicate with one or more ADAE servers of the same ADAE service provider. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 4.3 ADAE internal architecture requirements | [AR-4.3-a] The ADAE layer shall be able to provide a data collection coordination functionality to enable the collection from diverse data sources (OAM, 5GC, UE) per application data analytics event type.
[AR-4.3-b] The ADAE layer shall include a data analytics repository function to store application data analytics.
[AR-4.3-c] The data collection coordination and repository capabilities may be offered as APIs to ADAE server. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 4.4 ADAE capability related requirements | [AR-4.4-a] The ADAE server shall be capable of providing data analytics for the VAL server performance.
[AR-4.4-b] The ADAE server shall be capable of providing data analytics for the VAL application sessions (for both Uu-based and PC5-based sessions).
[AR-4.4-c] The ADAE server shall be able to collect application performance measurements and analytics from one or more ADAE clients.
[AR-4.4-d] The ADAE server shall be capable of collecting edge data from one or more edge platforms
[AR-4.4-e] The ADAE server shall enable the exposure of edge data analytics to the VAL applications
[AR-4.4-f] The ADAE server shall be capable of providing data analytics for the VAL server or VAL session performance for a requested slice or slice instance.
[AR-4.4-g] The ADAE server shall be capable of providing data analytics for the location accuracy of one or more VAL UEs.
[AR-4.4-h] The ADAE server shall be capable of providing data analytics related to the availability and status of one or more service APIs. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5 Application architecture for ADAES | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.1 General | This clause provides the functional architecture for ADAE. This includes the on-network and off-network functional models which are provided in detail in clause 5.2.
In addition, the ADAE internal architecture is described in 5.3, which aligns with the 3GPP data analytics framework (specified in TS 23.288 [4]) and introduces new logical entities within ADAE framework, such as the A-DCCF and A-ADRF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.2 Functional architecture | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.2.1 General | The functional architecture for the application data analytics enablement is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe a functional architecture which addresses the support for application data analytics enablement aspects for vertical applications. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.2.2 On-network Functional Architecture | For the on-network functional architecture, both service-based representation and reference point representation are provided.
Figure 5.2.2-1 depicts the application data analytics enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other.
Figure 5.2.2-1: Architecture for application data analytics enablement – reference points representation
The application data analytics enablement client communicates with the application data analytics enablement server over the ADAE-UU reference point. The application data analytics enablement client provides the support for application data analytics enablement functions to the VAL client(s) over ADAE‑C reference point. The VAL server(s) communicates with the application data analytics enablement server over the ADAE-S reference point. The application data analytics enablement server, acting as AF, may communicate with the 5G Core Network functions (over N33 reference point to NEF and N6 reference point to UPF) and OAM (over ADAE-OAM interface).
Figure 5.2.2-2 exhibits the service-based interfaces for providing and consuming application data analytics enablement services. The application data analytics enablement server could provide service to VAL server and ADAE client through interface SAdae.
Figure 5.2.2-2: Architecture for application data analytics enablement – Service based representation
Figure 5.2.2-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [9].
Figure 5.2.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation
Figure 5.2.2-4 illustrates the architecture for inter-service communication between ADAES server and other SEAL server.
Figure 5.2.2-4: Inter-service communication between ADAES server and other SEAL server
The ADAE server interacts with another SEAL server for inter-service communication over SEAL-X reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.2.3 Off-network Functional Architecture | Figure 5.2.3-1 illustrates the generic off-network functional model for ADAE.
Figure 5.2.3-1: Generic off-network functional model
In the vertical application layer, the VAL client of UE1 communicates with VAL client of UE2 over VAL-PC5 reference point. An application data analytics enablement client of UE1 interacts with the corresponding application data analytics enablement client of UE2 over ADAE-PC5 reference points. The UE1, if connected to the network via Uu reference point, can also act as a UE-to-network relay, to enable UE2 to access the VAL server(s) over the VAL-UU reference point.
The service-based interface representation is specified in clause 15 of 3GPP TS 23.434 [2]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.2.4 Functional Architecture for supporting interactions with SEAL AIMLE | Figure 5.2.4-1 illustrates the architecture representation including AIMLE (as specified in 3GPP TS 23.482 [19]) for supporting ML-enabled analytics in ADAES. In this representation, the AIML support capabilities serve ADAES to enhance its analytics services. Based on the VAL request to provide ML-enabled analytics, ADAES may consume AIMLE services (e.g., for ML model training for a given analytics ID) to derive application layer data analytics.
Figure 5.2.4-1: Architecture representation for supporting AIML-enabled ADAE analytics.
For the interaction between AIMLE server and ADAES, AIML-X is introduced to support consuming AIMLE services for deriving ADAE analytics (e.g. VAL server performance analytics).
The ML repository is specified in 3GPP TS 23.482 [19] as a repository for the ML model and registry for the ML-related information (such as ML/FL members). This repository may be utilized by ADAES via AIMLE server (via AIML-R) for fetching ML-related information (e.g., trained ML model, ML/FL members) which is used for a given ADAE analytics event.
Further details on the AIMLE capabilities and architecture, where the ADAES is a consumer of the AIMLE services, are specified in 3GPP TS 23.482 [19]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.3 ADAE internal architecture | In ADAE framework, A-DCCF and A-ADRF can be defined as functionalities within the internal ADAE architecture and can offer the following functionalities:
- Application layer - Data Collection and Coordination Function (A-DCCF) coordinates the collection and distribution of data requested by the consumer (ADAE server). Data Collection Coordination is supported by a A-DCCF. ADAE server can send requests for data to the A-DCCF rather than directly to the Data Sources. A-DCCF may also perform data processing/abstraction and data preparation based on the VAL server requirements.
- Application layer – Analytics and Data Repository Function (A-ADRF) stores historical data and/or analytics, i.e., data and/or analytics related to past time period that has been obtained by the consumer (e.g. ADAE server). After the consumer obtains data and/or analytics, consumer may store historical data and/or analytics in an A-ADRF. Whether the consumer directly contacts the A-ADRF or goes via the A-DCCF is based on configuration.
Figure 5.3-1 illustrates the generic functional model for ADAE when re-using the 3GPP network data analytics model.
Figure 5.3-1: ADAE internal functional architecture
In this model, an A-DCCF is used to fetch data or put data into an application-level entity (e.g. A-ADRF, Data Source). Such A-DCCF coordinates the collection and distribution of data requested by ADAE server (over ADCCF-1, ADAE-X). ADAE server can also directly interact with the Data Sources via ADAE-Y.
Also, Application layer – Analytics and Data Repository Function (A-ADRF) can be used to store historical data and/or analytics, i.e., data and/or analytics related to past time period that has been obtained by the ADAE server (via AADRF-1) or other NFs/NWDAF. ADAE server can also fetch historical data from A-ADRF. Whether the ADAE server directly contacts the A-ADRF or goes via the A-DCCF is based on configuration.
Data Sources can be 5GS data sources (5GC, OAM) or enablement layer data sources (SEAL, EEL) or external data sources at the DN side (VAL server/ EAS) and VAL UEs. A-DCCF and A-ADRF can be used only for interacting with certain data sources (e.g., 5GC, OAM) based on configuration, and can be hidden from the VAL layer.
NOTE: If the Data Source is the VAL UE, then the data collection mechanism shall reuse the SA4 mechanism based on EVEX study (TS 26.531 [3]). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.4 Functional entities description | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.4.1 General | The functional entities for ADAE service are described in the following subclauses. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.4.2 Application Data Analytics Enablement client | The application data analytics enablement and provides client side functionalities for the functionalties provided by the application data analytics enablement server. The application data analytics enablement client interacts with the application data analytics enablement server. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.4.3 Application Data Analytics Enablement server | The application data analytics enablement server functional entity provides application layer analytics to support the VAL applications. The application data analytics enablement server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The application data analytics enablement server also supports interactions with the corresponding application data analytics enablement server in distributed SEAL deployments. The ADAE server also interacts with 3GPP core network over N33 or N6 interface to subscribe to changes in configuration or other application server specific events. The ADAE server also acts as a co-ordinating entity to collect data from different sources and perform necessary actions to provide required analytics.
The ADAE server provides following server side functionalities:
- monitoring performance of an application (VAL server or EAS, application session) and providing support for application performance analytics;
- monitoring performance of a given network slice (from a list of subscribed slices for the VAL customer) and also usage pattern, and providing support for slice-specific application performance analytics and slice usage pattern analytics;
- monitoring performance of an application session among two or more VAL UEs within a service or group, and providing support for UE-to-UE application performance analytics;
- monitoring accuracy of a location and providing support for location accuracy analytics;
- monitoring availability and service level for service APIs and providing support for service API analytics;
- monitoring edge load parameters and providing support for edge load analytics;
- monitoring ranging/SL positioning data and location information, and providing support for collision detection analytics.
- monitoring location information and providing support for location-related UE group analytics.
- monitoring application layer AI/ML member capability data and providing support for Application Layer AI/ML Member Capability Analytics.
To support ML-enabled analytics services, the ADAE server may provide the above server-side functionalities by consuming SEAL AIMLE services (as specified in 3GPP TS 23.482 [19]). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5 Reference points description | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.1 General | The reference points for the functional model for application data analytics enablement are described in the following subclauses. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.2 ADAE-UU | The interactions related to application data analytics enablement functions between the application data analytics enablement client and the application data analytics enablement server are supported by ADAE-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [16] and 3GPP TS 23.501 [9]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.3 ADAE-PC5 | The interactions related to application data analytics enablement functions between the application data analytics enablement clients located in different VAL UEs are supported by the ADAE-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [17]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.4 ADAE-C | The interactions related to application data analytics enablement functions between the VAL client(s) and the application data analytics enablement client within a VAL UE are supported by the ADAE-C reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.5 ADAE-S | The interactions related to application data analytics enablement functions between the VAL server(s) and the application data analytics enablement server are supported by the ADAE-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.4 ADAE-X | The interactions related to application data analytics enablement functions between the application data analytics enablement server and the Application-layer DCCF (A-DCCF) for data coordination aspects are supported by the ADAE-X reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.5 ADAE-Y | The interactions related to application data analytics enablement functions between the application data analytics enablement server and the data producers (or data sources) for collecting data to be used for the ADAE analytics services (if A-DCCF is not used) are supported by the ADAE-Y reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.6 ADCCF-1 | The interactions related to application data analytics enablement functions between the application layer data collection and coordination entity and the data sources for data coordination aspects are supported by the ADCCF-1 reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.7 AADRF-1 | The interactions related to application data analytics enablement functions between the application data analytics enablement server (or the A-DCCF) and the application layer - analytics and data repository function (A-ADRF) for storing data and analytics related to the ADAE analytics services (if A-DCCF is not used) are supported by the AADRF-1 reference point. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.8 SEAL-X | The interactions between the NSCE servers and other SEAL servers are generically referred to as SEAL‑X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in 3GPP TS 23.434 [2]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 5.5.9 AIML-X | The interactions between the SEAL AIMLE server and ADAES for supporting ML-enabled analytics is generically referred to as AIML‑X reference point. AIML-X is an instance of SEAL-X as described 3GPP TS 23.434 [2]. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6 ADAE layer Functional Description | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.1 Support for application performance analytics | This feature supports the derivation and exposure of application layer analytics to provide insight on the operation and performance of an application (VAL server or EAS, application session), and in particular statistics or prediction on parameters related to e.g. VAL server number of connections for a given time and area, VAL server rate of connection requests, connection probability failure rates, RTT and deviations for a VAL server or VAL UE session, packet loss rates etc. This feature also supports the collection of service experience information from the ADAE clients (as described in clause 8.9) to support application performance analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.2 Support for slice-specific application performance analytics | This feature introduces application layer analytics to provide insight on the performance of the VAL applications when using a given network slice (from a list of subscribed slices for the VAL customer). Such capability provides an analytics service to a consumer who can be either the VAL server (for helping to identify what slice it will use for its applications) or for other consumers such as SEAL NSCE to support on providing analytics (since NSCE doesn't contain an analytics engine for providing analytics on top of NWDAF [4] /MDAS [5]). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.3 Support for UE-to-UE application performance analytics | This feature supports the derivation and exposure of application layer analytics to predict the performance of an application session among two or more VAL UEs within a service or group. Such prediction relates to application QoS attributes prediction for a given time horizon and area. This can be requested by the VAL server during the session, or the VAL server can subscribe to receive predicted application QoS downgrade indication for an ongoing session. Such analytics will help improving the application service experience and allow the VAL layer to pro-actively adapt to predicted application QoS changes. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.4 Support for location accuracy analytics | This feature supports application layer analytics enablement to allow a VAL server to be notified based on analytics whether the accuracy of a location can be met for a given application and optionally for a given UE/group route. For example, a VAL server may request the ADAE server to provide analytics whether the accuracy of a location for the UEs within a VAL application is predicted to be sustainable or is expected to downgrade in a specific area or for an expected route from location A to location B. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.5 Support for service API analytics | This feature introduces service API analytics to allow a VAL server or any other consumer (e.g. API provider) to be notified on the predicted /statistic availability and service level for the requested service API analytics. Such analytics may be utilized by the API provider to perform actions to avoid service API invocation failures or other actions like throttling/rate limitations. Also, such analytics will support the VAL server to identify if/when to perform an API invocation request based on the API expected status at the given area and time horizon. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.6 Slice usage pattern analytics | Slice usage pattern analytics provides network slice usage pattern analytics based on collected network slice performance and analytics, historical network slice status, and network performance to help the analytics consumer manage the network slice. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.7 Support for edge load analytics | Edge load analytics provide insight on the operation and performance of an EDN and in particular statistics or prediction on parameters related to:
- the EAS / EES load for one or more EAS/EES
- edge platform load parameters, which include the aggregated load per EDN or per DNAI due to the edge support services and e.g., load level of edge computational resources.
Such analytics can improve edge support services by allowing the pro-active edge service operation changes to deal with possible edge overload scenarios. For example, this can trigger EAS migration to a different EDN / central DN, or pro-active EAS reselection for a target UE or group of UEs. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.8 Edge computing preparation analytics | This feature introduces exposure of edge computing preparation analytics of the EAS, EES, and/or ECS to the analytics consumer (e.g., the VAL server, ECS, EES). The ADAE server provides the edge computing preparation analytics based on collected edge deployment time information, historical edge computing preparation analytics, instantiation triggering time and registration time from the EDN. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.9 Support for server-to-server performance analytics | This feature supports server-to-server performance analytics to allow an analytics consumer (such as VAL server or EES) to be notified on QoS analytics or predictions between two or more servers. Such prediction relates to QoS attributes prediction for a given time horizon and area. Such analytics allow the VAL layer to pro-actively adapt to predicted QoS changes. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.10 Support for collision detection analytics | This feature supports collision detection analytics to allow an analytics consumer (such as VAL Server, LM server, UAE server, UAS application specific server) to be notified on analytics for collision detection between any target VAL UEs, collision detection between any UEs and target VAL UEs, or collision detection between any UE within the Area of Interest. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.11 Support for location-related UE group analytics | This feature supports location-related UE group analytics to allow an analytics consumer (such as LMS) to be notified on analytics for UE group route or UE group member deviation. Such analytics can be used, e.g. UE group route prediction can be used to formulate application group profile with Expected Group Geographical Service Area as described in 3GPP TS 23.558 [14] clause 8.2.11. UE group member deviation prediction can be used for VAL to know which UE group member falls behind other group members or target group member (then VAL can send warning/reminder to the group members). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.12 Support for Application Layer AI/ML Member Capability Analytics | This feature supports Application Layer AI/ML Member Capability Analytics to allow an analytics consumer (such as e.g. VAL Server, AIMLE Server) to be notified on analytics for application layer AI/ML Member capability. Such analytics can be used to support application layer AI/ML services, e.g. supporting FL member selection and reselection. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.13 Support for VAL performance analytics for tethered UEs | This feature supports a new ADAES analytics functionality on tethered VAL connectivity performance. The tethered VAL connectivity performance can be defined as the application session performance corresponding to either only the tethered link (tethered UE and host UE) or the end-to-end VAL performance including the tethered link (as extension of VAL session performance analytics). |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.14 Support for DN Energy Analytics | This feature supports a logical functionality at the ADAES to provide analytics on the energy consumption /efficiency of an edge platform (including the EESs / EASs). The DN energy analytics is performed per DNN/ DNAI and may be used to trigger the application server migration to different cloud. The analytics are based on NWDAF analytics and UPF/DN measurements on user plane load as well as edge/app side measurements on the energy consumption. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 6.15 Support for ML Model Performance Degradation Detection | This feature supports ML model performance degradation detection to allow a consumer (such as e.g. AIMLE Server) to be notified on performance degradation of an ML model. Such detection can be used to support application layer AI/ML operations, e.g. supporting decision making on retrain an ML model. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 7 Identities and commonly used values | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 7.1 General | The common identities for SEAL refer to TS 23.434[2]. The following clauses list the additional identities and commonly used values for Application Data Analytics Enablement Service. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 7.2 ADAE Server ID | The ADAE server ID uniquely identifies the application data analytics enablement server, and each ADAE server ID is unique within PLMN domain. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 7.3 ADAE client ID | The ADAE client ID uniquely identifies the application data analytics enablement client. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 7.4 A-ADRF ID | The A-ADRF ID uniquely identifies the application data analytics repository function. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.