Content for TR 23.791 Word version: 16.2.0

3.1 Definitions 3.3 Abbreviations 4.1 General 4.2 General Framework
...

1 Scope p. 11

The aim of this Technical Report is to study and specify how to collect data and how to feedback data analytics to the network functions.

2 References p. 11

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.501: "System Architecture for the 5G System".

[3]

TS 23.502: "Procedures for the 5G System".

[4]

TS 23.503: "Policy and Charging Control Framework for the 5G System".

[5]

TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".

[6]

TS 23.724: "Study on Cellular Internet of Things (IoT) support and evolution for the 5G System".

[7]

TS 32.426: "Telecommunication management; Performance Management (PM); Performance measurements Evolved Packet Core (EPC) network".

[8]

TS 22.261: "Service requirements for next generation new services and markets".

[9]

TS 29.122: "T8 reference point for Northbound APIs".

[10]

TS 29.520: "5G System; Network Data Analytics Services; Stage 3".

[11]

ITU-T Recommendation P.1203.3: "Parametric bitstream-based quality assessment of progressive download and adaptive audiovisual streaming services over reliable transport - Quality integration module ".

[12]

RFC 8300: "Network Service Header (NSH)".

[13]

TS 28.550: "Management and orchestration of networks and network slicing; Performance Management; Stage 1".

[14]

TS 28.551: "Management and orchestration of networks and network slicing; Performance Management (PM); Stage 2 and stage 3".
→ to date, withdrawn by 3GPP

[15]

TS 28.552: "Management and orchestration of networks and network slicing; NR and NG-RAN performance measurements and assurance data".

[16]

TS 28.553: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) performance measurements and assurance data".
→ to date, withdrawn by 3GPP

[17]

TS 28.554: "Management and orchestration of networks and network slicing; 5G End to end Key Performance Indicators (KPI), performance measurements and assurance data ".

[18]

TS 28.545: "Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 1".

[19]

TS 28.546: "Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 2 and stage 3".
→ to date, withdrawn by 3GPP

[20]

TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".

[21]

TS 29.510: "5G System; Network function repository services; Stage 3".

[22]

TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".

[23]

TS 28.531: "Management and orchestration; Provisioning".

[24]

TS 28.532: "Management and orchestration; Generic management services".

[25]

OMA API Inventory: "http://technical.openmobilealliance.org/API/APIsInventory.aspx".

[26]

TR 28.805: "Telecommunication management; Study on management aspects of communication services".

[27]

TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".

3 Definitions and Abbreviations p. 12

3.1 Definitions p. 12

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.

3.3 Abbreviations p. 12

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.

Data Network

NWDAF

Network Data Analytics Function

OAM

Operation, Administration, and Maintenance

OTT

Over The Top

URSP

UE Route Selection Policy

4 Architecture Assumptions p. 12

4.1 General p. 12

The following architectural assumptions are applicable for all potential solutions:

The NWDAF (Network Data Analytics Function) as defined in TS 23.503 is used for data collection and data analytics in centralized manner. An NWDAF may be used for analytics for one or more Network Slice.
For instances where certain analytics can be performed by a 5GS NF independently, a NWDAF instance specific to that analytic maybe collocated with the 5GS NF. The data utilized by the 5GS NF as input to analytics in this case should also be made available to allow for the centralized NWDAF deployment option.
5GS Network Functions and OAM decide how to use the data analytics provided by NWDAF to improve the network performance.
NWDAF utilizes the existing service based interfaces to communicate with other 5GC Network Functions and OAM.
A 5GC NF may expose the result of the data analytics to any consumer NF utilizing a service based interface.
The interactions between NF(s) and the NWDAF take place in the local PLMN (the reporting NF and the NWDAF belong to the same PLMN).
Solutions shall neither assume NWDAF knowledge about NF application logic. The NWDAF may use subscription data but only for statistical purpose.
It is further assumed that NWDAF and NFs cooperate adequately to contribute to consistent policies, analytics output results, and finally decision-making in the PLMN.

4.2 General Framework p. 13

The Figure 4.2-1 shows general framework for 5G network automation in Release 16, depicting that the NWDAF should be able to collect data from the operator OAM, AFs and 5GC network functions.

Copy of original 3GPP image for 3GPP TS 23.791, Fig. 4.2-1: general framework for 5G network automation

Figure 4.2-1: general framework for 5G network automation
(⇒ copy of original 3GPP image)

As part of this study, exchange of information between NWDAF and OAM may be defined. Interactions between OAM and NWDAF shall be based on use case requirements. The OAM could be a potential consumer or provider of the information for the NWDAF. The definition of such interaction shall be coordinated with SA WG5.

For the collection of OAM data, the NWDAF shall reuse existing mechanisms and interfaces defined by SA WG5. For OAM information exchange beyond existing mechanisms and interfaces defined by SA WG5, close co-operation with SA WG5 is needed.

Depending on network deployments and on AF(s), the AF may exchange information with the NWDAF via the NEF, or use the service based interfaces to access the NWDAF directly.

NWDAF accesses network data from data repositories (e.g. UDR).

For 5GC NFs, the NWDAF utilizes the service based interfaces to communicate to get network data and dedicated analytics.

Based on the aforementioned data collection, the NWDAF performs data analysis and provides the analytical result to the AF, the 5GC NFs and the OAM.

The output of the analytics provided to the AF, NFs, and OAM by the NWDAF and vice versa will be defined depending on the selected solutions for the key issues.