19 Application Data Analytics Enablement
23.4343GPPFunctional architecture and information flowsRelease 18Service Enabler Architecture Layer for Verticals (SEAL)TS
19.1 General
The application data analytics enablement is a SEAL service that offers value-add application data analytics capabilities which cover stats/predictions for the end-to-end application service.
19.2 Functional architecture
19.2.1 General
The functional architecture for the application data analytics enablement is based on the generic functional model specified in clause 6.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.
NOTE: In addition to the generic functional architecture, the internal ADAE functional architecture is described in TS 23.436 [49] clause 5.2.
19.2.2 On-network Functional Architecture
For the on-network functional architecture, both service-based representation and reference point representation are provided.
Figure 19.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 19.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 19.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 19.2.2-2: Architecture for application data analytics enablement – Service based representation
Figure 19.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 [10].
Figure 19.2.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation
Figure 19.2.2-4 illustrates the service-based representation including ADAE server as part of the SEAL framework.
Figure 19.2.2-4: SEAL functional model representation using service-based interfaces and including ADAE function
19.2.3 Off-network Functional Architecture
Figure 19.2.3-1 illustrates the generic off-network functional model for ADAE.
Figure 19.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.
19.3 Procedures and information flows for application data analytics enablement
The procedures and information flows for application data analytics enablement are presented in TS 23.436 [49].
Annex A (informative):
SEAL integration with 3GPP network exposure systems
NOTE: Not all possible SEAL integration with 3GPP network exposure systems are illustrated in this subclause.
Figure A-1 illustrates the service-based interface representation of the functional model for SEAL services integration with 5GC network exposure system.
Figure A-1: SEAL integration with 5GC network exposure system
The details of NEF and its role in exposing network capabilities of 5GS to 3rd party applications are specified in 3GPP TS 23.501 [10] and the details of NEF service operations are specified in 3GPP TS 23.502 [11].
Figure A-2 illustrates the service-based interface representation of the functional model for SEAL services integration with EPC network exposure system.
Figure A-2: SEAL integration with EPC network exposure system
The details of SCEF and its role in exposing network capabilities of EPS to 3rd party applications are specified in 3GPP TS 23.682 [13].
Annex B (informative):
SEAL functional model mapping with Common functional architecture (CFA)
The table B-1 shows the mapping between the SEAL functional model and the Common functional architecture (CFA). The details of CFA functional entities and reference points are specified in 3GPP TS 23.280 [4].
Table B-1: SEAL functional model mapping with CFA
|
SEAL service |
Aspects |
SEAL |
CFA |
|
Location management |
Functional entity |
Location management client |
Location management client |
|
Location management server |
Location management server |
||
|
Reference points |
LM-UU |
CSC-14 |
|
|
LM-S |
CSC-15 |
||
|
LM-C |
Not defined |
||
|
LM-E |
Not defined |
||
|
LM-PC5 |
Not defined |
||
|
Group management |
Functional entity |
Group management client |
Group management client |
|
Group management server |
Group management server |
||
|
Reference points |
GM-UU |
CSC-2 |
|
|
GM-S |
CSC-3 |
||
|
GM-C |
Not defined |
||
|
GM-E |
CSC-16 |
||
|
GM-PC5 |
CSC-12 |
||
|
Configuration management |
Functional entity |
Configuration management client |
Configuration management client |
|
Configuration management server |
Configuration management server |
||
|
Reference points |
CM-UU |
CSC-4 |
|
|
CM-S |
CSC-5 |
||
|
CM-C |
Not defined |
||
|
CM-E |
CSC-17 |
||
|
CM-PC5 |
CSC-11 |
||
|
Identity management |
Functional entity |
Identity management client |
Identity management client |
|
Identity management server |
Identity management server |
||
|
Reference points |
IM-UU |
CSC-1 |
|
|
IM-S |
Not defined |
||
|
IM-C |
Not defined |
||
|
IM-E |
Not defined |
||
|
IM-PC5 |
Not defined |
||
|
Key management |
Functional entity |
Key management client |
Key management client |
|
Key management server |
Key management server |
||
|
Reference points |
KM-UU |
CSC-8 |
|
|
KM-S |
CSC-9 |
||
|
KM-PC5 |
Not defined |
||
|
Network resource management |
Functional entity |
Network resource management client |
Not defined (see NOTE) |
|
Network resource management server |
Not defined (see NOTE) |
||
|
Reference points |
NRM-UU |
Not defined (see NOTE) |
|
|
NRM-S |
Not defined |
||
|
NRM-C |
Not defined |
||
|
NRM-E |
Not defined |
||
|
NRM-PC5 |
Not defined |
||
|
NOTE: Defined in the application layer for Mission Critical service (e.g. MCPTT). |
|||
Annex C (normative):
Protocol realizations of LWP in the signalling control plane