Content for TR 28.806 Word version: 16.1.0
0 Introduction
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
...
...
0 Introduction p. 5
Subscriber and Equipment Trace, standardized by 3GPP SA5 in the family of specifications TS 32.421 / TS 32.422 / TS 32.423, was originally introduced for diagnostic and troubleshooting purposes. With the introduction of Self Organized Networks (SON) concepts in 3GPP Rel-8, the Trace was being considered as one of the data sources for Centralized SON (C-SON) algorithms. In addition to traditional Trace, other Trace job types such as collection of MDT measurements, Radio Link Failure (RLF) and Radio Connection Establishment Failure (RCEF) reports were added to trace specifications and used extensively for the NM centralized Coverage and Capacity Optimization (NM CCO TR 32.836).
Traditional trace reporting is file-based and therefore implies certain time restrictions on the availability of trace data preventing it from being used in fast control loop automation processes. In addition, file-based trace reporting may cause scalability issues in scenarios involving processing the records of multiple traces delivered at high rate.
1 Scope p. 6
The present document investigates the opportunities for new trace reporting methods. It identifies and documents use cases and potential requirements for non-file-based trace reporting, documents and evaluates potential solutions, and provides recommendations for the normative work aligned with 5G Services Based Management Architecture (SBMA).
2 References p. 6
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 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[3]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[4]
TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management"
[5]
TR 32.836: "Telecommunication management; Study on Network Management (NM) centralized Coverage and Capacity Optimization (CCO) Self-Organizing Networks (SON) function".
[6]
TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
[7]
TS 28.532: "Management and orchestration; Generic management services".
[8]
TS 28.533: "Management and orchestration; Architecture framework".
[9]
RFC 6455: "The WebSocket Protocol".
[10]
RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3".
[11]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[12]
TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
3 Definitions of terms, symbols and abbreviations p. 6
3.1 Terms p. 6
For the purposes of the present document, the terms given in TR 21.905, TS 32.421, TS 32.422, TS 32.423 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. 7
Void.
3.3 Abbreviations p. 7
For the purposes of the present document, the abbreviations given in TR 21.905, TS 32.421, TS 32.422, TS 32.423 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.
