Content for TR 28.873 Word version: 19.0.0
0 Introduction
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
4 Concept and background
...
...
0 Introduction p. 5
In the existing system it is a need that the "job reference" (e.g. Trace Reference for TraceJob, jobId for PerfMetricJob and qoEReference for QMCJob) is unique within a PLMN so that the producer can send the requested data to the right consumer.
In the existing system it is the consumers that sets the "job reference". With a number of consumers that are separated from each other, it is not possible to fulfil the requirement of uniqueness, as the consumers can be different Network Functions (NFs) as well as different MnFs (Management Function).
With an increasing number of consumers, it is likely that the same data is requested by different consumers. It is investigated whether the NF needs to capture those data several times or if the reporting to different consumers can be moved out from the NF without any significant drawback.
1 Scope p. 6
The present document investigates how unique "job reference id" (e.g. Trace Reference, QoE Reference, Job Id) can be unique within a 3GPP system and whether it is possible to decrease the load in the NFs when there are several consumers asking for the same data within a PLMN.
The study is done for 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 28.622: "Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[3]
TS 32.422: "Telecommunication management; Subscriber and equipment trace: Trace control and configuration management".
[4]
TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions".
[5]
TS 28.532: "Management and orchestration; Generic management services".
[6]
TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[7]
TS 32.422: "Telecommunication management; Subscriber and equipment trace: Trace control and configuration management".
[8]
TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management".
[9]
TS 28.404: "Telecommunication management; Quality of Experience (QoE) measurement collection; Concepts, use cases and requirements".
[10]
TS 28.405: "Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration".
[11]
TS 28.550: "Management and orchestration; Performance assurance".
[12]
TS 28.537: "Management and orchestration; Management capabilities".
3 Definitions of terms, symbols and abbreviations p. 7
3.1 Terms p. 7
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.
Collection Id:
A globally unique identification which is used as reference identify in PM/Trace/QoE/MDT procedure.Examples of the Collection Ids are Trace Reference for TraceJob, jobId for PerfMetricJob and qoEReference for QMCJob.
3.2 Symbols p. 7
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations p. 7
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.
MnF
Management Function
NF
Network Function
SBMA
Service Based Management Architecture
4 Concept and background p. 7
The existing solutions for retrieving management data (performance measurements, trace, MDT and QoE) build on that there are few consumers that request these data. It is the consumer that has the responsibility to ensure that the collectionId (e.g. Trace Reference for TraceJob, jobId for PerfMetricJob and qoEReference for QMCJob) is unique within a PLMN.
But the number of consumers of these data is getting many, and they do not have interface to coordinate the collectionId. The consequence is that the collectionId might not be unique, which can lead to e.g. that a consumer does not receive the data that it has requested.
As the number of consumers are increasing much, it also leads to that the true data producer may get many requests for the same data (e.g. measurement). Therefore, the producer needs to be able to handle many requests from many consumers, of which several can be for the same data (e.g. measurement). At the producer this leads to an increased amount of memory and processor power is needed for administrating all those requests.
