4 Reference Architecture for Data Analytics

29.5523GPP5G SystemNetwork Data Analytics signalling flowsRelease 17Stage 3TS

4.1 General

For the enablement of network data analytics services, the NWDAF interacts with different entities for different purposes:

– Data Collection:

a) collecting Data from OAM and/or 5GC NFs (e.g. AMF);

b) collecting Data from untrusted AF via NEF; and/or

c) collecting Analytics and/or Data from 5GC NFs via DCCF or via DCCF together with ADRF and/or MFAF or via NWDAF hosting DCCF i.e. an NWDAF that implements DCCF functionality internally and supports the Nnwdaf_DataManagement API;

– Analytics Exposure:

a) Exposing Analytics to 5GC NFs;

b) Exposing Analytics to untrusted AF via NEF; and/or

c) Exposing Analytics to 5GC NFs via DCCF or via DCCF together with ADRF and/or MFAF or via NWDAF hosting DCCF and/or ADRF i.e. an NWDAF that implements DCCF and/or ADRF functionality internally and supports the Nnwdaf_DataManagement API;

– Storing and Retrieving data in ADRF.

The entities mentioned above interact also with each other as described in the procedures of clause 5.

4.2 Data Collection

As depicted in Figure 4.2-1, the 5G System architecture allows NWDAF to collect data from any 5GC NF (e.g. AMF, SMF) and/or OAM directly or via DCCF, DCCF together with ADRF and/or MFAF, or via NWDAF.

Figure 4.2-1: Data Collection Architecture

When DCCF, ADRF, MFAF or NWDAF hosting DCCF are present in the network, whether the NWDAF directly contacts the Data Source NF or goes via the DCCF, or NWDAF hosting DCCF is based on configuration of the NWDAF.

The Data Source NF may be AMF, SMF, UDM, AF, NSACF, NRF and/or NEF with the related data collection procedures described in clause 5.5. The Data Source NF may also be UPF while how to collect data from UPF is not defined in this release of the specification. If the Data Source is OAM, The NWDAF may collect relevant management data from the services in the OAM as configured by the PLMN operator. The NWDAF may use the OAM services e.g. generic performance assurance and fault supervision management services as defined in TS 28.532 [19], PM (Performance Management) services as defined in TS 28.550 [31] and/or FS (Fault Supervision) services as defined in TS 28.545 [37].

For the specific analytics event, the applicable Data Source NF(s) and the related data collection procedures and scope are descibed in the corresponding analytics event subcluase within clause 5.7.

4.3 Analytics Exposure

As depicted in Figure 4.3-1, the 5G System architecture allows NWDAF to expose data to any 5GC NF (e.g. AMF) directly or via DCCF/MFAF.

Figure 4.3-1: Analytics Exposing Architecture

When DCCF, ADRF, MFAF or NWDAF are present in the network, whether the Analytics consumer directly contacts the NWDAF or goes via the DCCF or via the NWDAF hosting DCCF and/or ADRF is based on configuration of the Analytics consumer.

The Analytics consumer may be AMF, SMF, NSSF, PCF, AF, NEF, OAM and/or CEF when directly contacts NWDAF with the related analytics exposure procedures described in clause 5.2.2 and clause 5.2.3. The Analytics consumers may be AMF, SMF, NSSF, PCF AF and/or NEF when contacts via the DCCF with the related analytics exposure procedures described in clause 5.2.4 and clause 5.2.5.

For the specific analytics event, the applicable Analytics consumer(s) and the related analytics exposure procedures and scope are descibed in the corresponding analytics event subcluase within clause 5.7.

4.4 Data Storage and Retrieval

As depicted in Figure 4.4-1, the 5G System architecture allows the consumer to store and retrieve the collected data in the ADRF directly or via DCCF/MFAF.

Figure 4.4-1: Data Storage and Retrieval Architecture