10 Metric identifier

32.4223GPPRelease 17Subscriber and equipment traceTelecommunication managementTrace control and configuration managementTS

10.1 General

The metric identifiers are a sequence of items separated by ".". The sequence of items identifying a measurement is organised from the general to the particular. The individual items follow the Lower Camel Case naming convention [61]. There are different sequences for Immediate MDT, Logged MDT, Logged MBSFN MDT, Trace, RLF reports and RCEF reports.

10.2 Immediate MDT

The measurement names for Immediate MDT measurements consist of the following items:

– The first item identifies the MDT mode, i.e. "immediateMdt".

– The second item identifies the radio access technology (RAT), i.e. "nr", "lte" or "umts"

– The third item identifies the name of the measurement itself (e.g. m1, m2), see TS 37.320 [30].

– An additional item of the measurement attribute name may be present, e.g. "rsrp" or "ueLocation" or "ulThpTime" see TS 32.423 [3].

Possible examples:

– immediateMdt.nr.m1.rsrp

– immediateMdt.nr.m2

– immediateMdt.nr.m4

– immediateMdt.nr.m5.ulThpTime

– immediateMdt.nr.m6

– immediateMdt.nr.m7

– immediateMdt.nr.m8

– immediateMdt.nr.m9

– immediateMdt.lte.m2

10.3 Logged MDT and Logged MBSFN MDT

The measurement names for Logged MDT and Logged MBSFN MDT measurements consist of the following items:

– The first item identifies the MDT mode, i.e. "loggedMdt" or "loggedMbsfnMdt".

– The second item is optional and identifies the measurement attribute name, e.g. "rsrp" or "ueLocation".

Possible examples:

– loggedMdt.rsrp

– loggedMbsfnMdt

10.4 Trace

The measurement names for Trace messages consist of the following items:

– The first item identifies the job type, i.e. "trace".

– The second item identifies the network element type (e.g. amf, upf, gnbCuCp, gnbCuUp, gnbDu), see clause 5.4.

– The third item is optional and identifies the interface (e.g. n1, n2, n4, ng-c, xn-c, uu, f1-c, e1, x2-c) , see clause 5.5.

– The fourth item is optional and identifies the message name e.g. "ueContextReleaseRequest" or "handoverFailure".

– The fifth item is optional and identifies the IE name e.g. "cause".

Possible examples:

– trace.amf.n1

– trace.amf.n1.registrationRequest.requestedNssai

– trace.amf.n1.serviceRequest.serviceRequestMessageIdentity

– trace.amf.n1.serviceRequest.ulDataStatus

– trace.mme.s1-mme.ueContextReleaseRequest.cause

10.5 RLF report and RCEF report

The measurement names for RLF reports and RCEF reports consist of the following items:

– The first item identifies the job type, i.e. "rlfReport" or "rcefReport".

– The second item is optional and identifies the measurement attribute name, e.g. "rsrp" or "ueLocation".

Possible examples:

– rlfReport.rsrp

– rcefReport

Annex A (normative):Trace failure notification file format