Content for TS 29.552 Word version: 17.3.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Reference Architecture for Data Analytics
4.1 General
4.2 Data Collection
4.3 Analytics Exposure
4.4 Data Storage and Retrieval
...
...
1 Scope p. 7
The present document specifies detailed call flows of Network Data Analytics over the Nnwdaf, Nsmf, Npcf, Nnsacf, Namf, Nnrf, Nnssf, Nnef, Naf, Ndccf, Nadrf, Nmfaf and Nudm service-based interfaces and their relationship with the flow level signalling in 5G system.
The stage 2 definition and procedures of Network Data Analytics are contained in TS 23.288 and TS 23.502. The 5G System Architecture is defined in TS 23.501.
Detailed definitions of the involved services are provided in TS 29.520, TS 29.508, TS 29.523, TS 29.554, TS 29.521, TS 29.522, TS 29.591, TS 29.517, TS 29.574, TS 29.575, TS 29.576, TS 29.503, TS 29.510, TS 29.507 and TS 29.512.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in TS 29.500 and TS 29.501.
2 References p. 7
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[5]
TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
[6]
TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[7]
TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[8]
TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".
[9]
TS 29.521: "5G System; Binding Support Management Service; Stage 3".
[10]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[11]
TS 29.591: "5G System; Network Exposure Function Southbound Services; Stage 3".
[12]
TS 29.517: "5G System; Application Function Event Exposure Service; Stage 3".
[13]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[14]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[15]
TS 29.574: "5G System; Data Collection Coordination Services; Stage 3".
[16]
TS 29.575: "5G System; Analytics Data Repository Services; Stage 3".
[17]
TS 29.576: "5G System; Messaging Framework Adaptor Services; Stage 3".
[18]
TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[19]
TS 28.532: "Management and orchestration; Generic management services".
[20]
TS 29.536: "5G System: Network Slice Admission Control Services; Stage 3".
[21]
TS 29.531: "5G System: Network Slice Selection Services; Stage 3".
[22]
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[23]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[24]
TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
[25]
TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[26]
TS 29.510: "5G System: Network function repository services; Stage 3".
[27]
TS 28.552: "Management and orchestration; 5G performance measurements".
[28]
TS 28.533: "Management and orchestration; Architecture framework".
[29]
TS 37.320: " Radio measurement collection for Minimization of Drive Tests (MDT); Overall description".
[30]
TS 28.554: " Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[31]
TS 28.550: "Management and orchestration; Performance assurance".
[32]
TS 37.320: "Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; stage 2".
[33]
TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[34]
TS 36.331: "Radio Resource Control (RRC); Protocol specification".
[35]
TS 38.215: "NR; Physical layer measurements".
[36]
TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[37]
TS 28.545: "Management and orchestration; Fault Supervision (FS)".
3 Definitions of terms, symbols and abbreviations p. 8
3.1 Terms p. 8
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
3.2 Symbols p. 9
None.
3.3 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
ADRF
Analytics Data Repository Function
AF
Application Function
AMF
Access and Mobility Management Function
AnLF
Analytics Logical Function
DCCF
Data Collection Coordination Function
MFAF
Messaging Framework Adaptor Function
MDT
Minimization of Drive Tests
ML
Machine Learning
MTLF
Model Training Logical Function
NEF
Network Exposure Function
NRF
Network Repository Function
NSACF
Network Slice Admission Control Function
NWDAF
Network Data Analytics Function
PCF
Policy Control Function
SMF
Session Management Function
UDM
Unified Data Management
4 Reference Architecture for Data Analytics p. 9
4.1 General p. 9
For the enablement of network data analytics services, the NWDAF interacts with different entities for different purposes:
-
Data Collection:
- collecting Data from OAM and/or 5GC NFs (e.g. AMF);
- collecting Data from untrusted AF via NEF; and/or
-
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:
- Exposing Analytics to 5GC NFs;
- Exposing Analytics to untrusted AF via NEF; and/or
-
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.
4.2 Data Collection p. 10
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.
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, PM (Performance Management) services as defined in TS 28.550 and/or FS (Fault Supervision) services as defined in TS 28.545.
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 p. 10
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.
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 p. 11
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.
