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 re... |
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... |
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 ... |
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 acknow... |
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 ... |
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/No... |
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 t... |
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 ... |
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 delive... |
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... |
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 reque... |
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... |
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 Infor... |
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 ... |
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 o... |
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: Netwo... |
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
Id... |
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 granu... |
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.
- Fo... |
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... |
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]... |
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.
[... |
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 per... |
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 intr... |
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 f... |
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 o... |
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 w... |
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, AD... |
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). ... |
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 suppor... |
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 3GP... |
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) a... |
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 ... |
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 identif... |
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 ... |
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 acc... |
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 invo... |
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... |
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 an... |
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 t... |
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 b... |
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 Geographic... |
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 se... |
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 tet... |
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 base... |
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.