Content for TR 23.700-36 Word version: 18.1.0
5 Architecture aspects
5.1 Architecture related requirements
5.2 ADAE capability related requirements
5.2.1 Application performance analytics requirements
5.2.2 Edge load analytics requirements
5.2.3 Slice related application data analytics requirements
5.3 Functional Architecture
5.3.1 General
5.3.2 On-network Functional Architecture
...
...
5 Architecture aspects p. 12
5.1 Architecture related requirements p. 12
5.1.1 Description p. 12
This subclause specifies the general and ADAE internal requirements for application data analytics enablement layer functional architecture.
5.1.2 General Requirements p. 12
[AR-5.1.2-a]
The ADAE client and the ADAE server shall support one or more VAL applications.
[AR-5.1.2-b]
Supported ADAE capabilities may be offered as APIs to the VAL applications.
[AR-5.1.2-c]
The ADAE shall support interaction with 3GPP network system to consume network data analytics services.
[AR-5.1.2-d]
The ADAE client shall be capable to communicate with one or more ADAE servers of the same ADAE service provider.
5.1.3 ADAE internal architecture requirements p. 12
[AR-5.1.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-5.1.3-b]
The ADAE layer shall include a data analytics repository function to store application data analytics.
[AR-5.1.3-c]
The data collection coordination and repository capabilities may be offered as APIs to ADAE server.
5.2 ADAE capability related requirements p. 12
5.2.1 Application performance analytics requirements p. 12
5.2.1.1 Description p. 12
This subclause specifies the requirements for application performance analytics capability.
5.2.1.2 Requirements p. 12
[AR-5.2.1.2-a]
The ADAE server shall be capable of providing data analytics for the VAL server performance.
[AR-5.2.1.2-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-5.2.1.2-c]
The ADAE server shall be able to collect application performance measurements and analytics from one or more ADAE clients.
5.2.2 Edge load analytics requirements p. 12
5.2.2.1 Description p. 12
This subclause specifies the requirements for edge load analytics capability.
5.2.2.2 Requirements p. 13
[AR-5.2.2.2-a]
The ADAE server shall be capable of collecting edge data from one or more edge platforms
[AR-5.2.2.2-b]
The ADAE server shall enable the exposure of edge data analytics to the VAL applications
5.2.3 Slice related application data analytics requirements p. 13
5.2.3.1 Description p. 13
This subclause specifies the requirements for slice related application data analytics capability.
5.2.3.2 Requirements p. 13
[AR-5.2.3.2-a]
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-5.2.3.2-b]
The ADAE server shall be able to collect slice related measurements and analytics from one or more 3GPP network system domains (OAM, 5GC).
5.3 Functional Architecture p. 13
5.3.1 General p. 13
This clause provides the overall functional architecture description, which includes the on-network and off-network functional models.
5.3.2 On-network Functional Architecture p. 13
For the on-network functional architecture, both service-based representation and reference point representation are provided.
Figure 5.3.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.3.2-1: Architecture for application data analytics enablement - reference points representation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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.3.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 SAdaee.
Figure 5.3.2-2: Architecture for application data analytics enablement - Service based representation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Figure 5.3.2-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in TS 23.501.
Figure 5.3.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA - Service based representation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
The application data analytics enablement server can be deployed as a SEAL server; hence enhancements to SEAL architecture (as specified in TS 23.434) are needed to incorporate the ADAE service. Figure 5.3.2-4 illustrates the service-based representation including ADAE server as part of the SEAL framework.
Figure 5.3.2-4: SEAL functional model representation using service-based interfaces and including ADAE function
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
