B.1 File naming convention

32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The following convention shall be applied for trace result file naming:

<Type><Startdate>.<Starttime>‑<SenderType>.<SenderName>.[<TraceReference>].[<TraceRecordingSessionRef>]

1) The Type field indicates if the file contains trace data for single or multiple calls, where:

– "A" means single Trace Recording Session, single sender NE;

– "B" means multiple Trace Recording Sessions, single sender NE;

– "C" means IMSI/IMEI (SV) information for cell traffic trace or IMEI-TAC if area based MDT trace is involved (3GPP TS 32.422 [3] clause 4.4) .

2) The Startdate field indicates the date of the first record in the trace file. The Startdate field is of the form YYYYMMDD, where:

– YYYY is the year in four-digit notation;

– MM is the month in two digit notation (01 – 12);

– DD is the day in two digit notation (01 – 31).

3) The Starttime field indicates the time of the first record in the trace file. The Starttime field is of the form HHMMSSshhmm, where:

– HH is the two digit hour of the day (local time), based on 24 hour clock (00 – 23);

– MM is the two digit minute of the hour (local time) (00 – 59);

– SS is the two digit second of the minute (local time) (00 – 59);

– s is the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the sign may be arbitrarily set to "+" or "-";

– hh is the two digit number of hours of the local time differential from UTC (00-23);

– mm is the two digit number of minutes of the local time differential from UTC (00-59).

4) SenderType field is the type of NE defined by IOC attribute managedElementType in 3GPP TS 32.622 [12] that recorded and sent the trace file; SenderName field is the identifier of the NE that recorded and sent the trace file.

5) TraceRecordingSessionReference field is set only if the type field is A, and is represented in hexa-decimal format. TraceRecordingSessionReference is a 4 digit hexadecimal number and will not include filler digits for values less than 4 digits in length. All hexadecimal letters (A thru F) are capitalized.

6) TraceReference field is set if the type field is A. For type B the Trace Reference is optional and will be used when one trace file is created per trace session with multiple trace recording session. Trace Reference is represented in hexadecimal format. Trace Reference as defined in 3GPP TS 32.422 [3] is composed of PLMN ID (MCC, MNC) and Trace ID. The PLMN identity consists of 3 digits for MCC followed by either – a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or 3 digits from MNC (in case of a 3 digit MNC). MCC and MNC are in BCD format.

Example: If MCC: 405, MNC: 139

octet 1: 0x04 (MCC digit 2, MCC digit 1)

octet 2: 0x15 (MNC digit 1, MCC digit 3)

octet 3: 0x93 (MNC digit 3, MNC digit 2)

Also if the MNC is 2 digits (MCC: 405 and MNC 39)

octet 1: 0x04 (MCC digit 2, MCC digit 1)

octet 2: 0xF5 (MNC digit 1, MCC digit 3)

octet 3: 0x93 (MNC digit 3, MNC digit 2)

7) Trace Reference is set if the type field is C.

See bullet 6 above for details regarding the representation of the Trace Reference.Some examples describing file naming convention:

1) file name: A20090928.231500+0200-MME.MME5. 13F23200056.125,

meaning: file produced by MME< MME5> on September 28, 2009, first trace record at 23:15:00 local time with a time differential of +2 hours against UTC. The file contains trace data for the Trace Session with the Trace reference 13F232000056 (where MCC is 312, MNC is 23, and Trace ID is 000056, all in hexadecimal format) and for the Trace Recording Session with the reference 125.

2) file name: B20030115.170000-0300-RNC.RNC02,

meaning: file produced by RNC<RNC02> on January 15, 2003, first trace record at 17:00:00 local time with a time differential of -3 hours against UTC. The file contains trace data for several Trace Recording Sessions.

3) file name: B20030115.170000-0300-RNC.RNC02. 4358070034D7,

meaning: file produced by RNC<RNC02> on January 15, 2003, first trace record at 17:00:00 local time with a time differential of -3 hours against UTC. The file contains trace 4358070034D7 (where MCC is 348, MNC is 570, and Trace ID is 0034D7) data for Trace reference and several Trace Recording Sessions.

4) file name C20030115.170000-0300-MME.MME02. 26F452550021

Meaning: file produced by MME<MME02> on January 15, 2003, first trace record at 17:00:00 local time with a time differential of -3 hours against UTC. The file contains IMSI/IMEI (SV) or IMEI-TAC information for one or more UEs traced at eNB with Trace Reference26F452550021 (where MCC is 624, MNC is 25, and Trace ID is 550021).