A.4 Trace IRP XML File Name Conventions

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

For Trace failure notification XML File Name Conventions the generic file name definitions as specified by the FT IRP apply (see [28]) with the “specificIRP extension” defined below.

<SenderType>.<SenderName>

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

Some examples describing the use of the “specificIRP_extension” in Trace failure notification naming:

specificIRP_extension: MME.MME04
meaning: file produced by MME<MME04>.

specificIRP_extension: ENB.ENB122
meaning: file produced by ENB<ENB122>.

file name: CT201105131405-060012MME.MME04
meaning: unique call trace (Trace failure notification) file produced by MME<MME04> on May 13, 2011 at 14:05 local with a time differential of -6 hours against UTC and expiring in 12 hours after creation

file name: CT201105131315-060012ENB.ENB122_-_2
meaning: second non-unique (RC=”2”) call trace (Trace failure notification) file produced by ENB<ENB122> on May 13, 2011 at 13:15 local with a time differential of -6 hours against UTC and expiring in 12 hours after creation.