5 Trace/UE measurement control and configuration parameters

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

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

5.1 Triggering Events (CM)

This conditional mandatory parameter defines when to start a Trace Recording Session and which message shall be recorded first, when to stop a Trace Recording Session and which message shall be recorded last respectively. The messages in the start triggering event tables indicate the transaction to be recorded first and the starting time of the Trace Recording Session within a Trace Session for the traced MS/subscriber in the given NE.

The messages in the stop triggering event tables indicate the transaction to be recorded last and the stopping time of the Trace Recording Session.

MSC Server	Start triggering events	Stop triggering events
Mobile Originated Call	Receipt of the CM SERVICE-REQUEST message with service type set to originating call establishment	Reception of CC-RELEASE COMPLETE or CM-SERVICE ABORT message
Mobile Terminated Call	Sending of PAGING REQUEST message	Reception of CC-RELEASE COMPLETE or CM-SERVICE ABORT message
Mobile Originated SMS	Receipt of the CM SERVICE-REQUEST message with service type set to Short Message service	Transmission of RP-ACK/RP-NACK message
Mobile Terminated SMS	Sending of PAGING REQUEST message	Reception of RP-ACK/RP-NACK message
IMSI Attach	Receipt of the MM-LOCATION UPDATING REQUEST message	Sending of MM-LOCATION-UPDATING ACCEPT or MM-LOCATION-UPDATING-REJECT message
Location Update	Receipt of the MM-LOCATION UPDATING REQUEST message	Sending of MM-LOCATION-UPDATING ACCEPT or MM-LOCATION-UPDATING-REJECT message
IMSI Detach	Receipt of the MM-IMSI DETACH INDICATION message	Reception of MM-IMSI DETACH INDICATION message
Handover	Receipt of the BSSMAP-HANDOVER-REQUIRED message in case of GSM or RANAP-RELOCATION-REQUIRED message in case of UMTS	Reception of BSSMAP-CLEAR COMPLETE message in case of GSM or RANAP-IU RELEASE COMPLETE message in case of UMTS or BSSMAP-HANDOVER FAILURE in case of GSM or RANAP-RELOCATION FAILURE in case of UMTS.
Supplementary Service	TBD	TBD

MGW	Start triggering events	Stop triggering events
Context	Reception of H.248-ADD command, or reception of H.248 MODIFY command	Sending of H.248- SUBTRACT reply

SGSN	Start triggering events	Stop triggering events
PDP Context	Reception of SM-ACTIVATE PDP CONTEXT REQUEST or sending SM-REQUEST PDP CONTEXT ACTIVATION or reception of SM- MODIFY PDP CONTEXT REQUEST	Reception or sending of SM- DEACTIVATE PDP CONTEXT REQUEST or sending SM-ACTIVATE PDP CONTEXT REJECT
Mobile Originated SMS	Receipt of RP-DATA message	Transmission of RP-ACK/RP-NACK message
Mobile Terminated SMS	Transmission of RP-DATA message	Reception of RP-ACK/RP-NACK message
GPRS Attach	Reception of MM-ATTACH-REQUEST	Sending MM-ATTACH-ACCEPT or MM-ATTACH-REJECT
Routing Area Update	Reception of MM-ROUTING AREA UPDATE REQUEST	Sending MM-ROUTING AREA UPDATE ACCEPT or MM-ROUTING AREA UPDATE REJECT
GPRS Detach	Reception MM-DETACH REQUEST	Reception of MM-DETACH ACCEPT
MBMS Context	Sending SM-Request MBMS Context Activation or reception of SM-Update MBMS Context Request	Sending of SM-Deactivate MBMS Context Request or sending of SM-Activate MBMS Context Reject

GGSN	Start triggering events	Stop triggering events
PDP Context	Reception of GTP Create PDP context request or reception of GTP Update PDP context request	Sending of GTP Delete PDP context response
MBMS Context	Reception of GTP Create MBMS Context Request or reception of GTP Update MBMS Context Request	Sending of GTP Delete MBMS Context Response

IMS Network Element	Start triggering events	Stop triggering events
SIP session or standalone transaction	Reception of an initial SIP request that matches the start trigger event configured by the Management System via the Trace IRP TS 32.442 [24]	Sending of a SIP final response to a SIP BYE or other request (originating or terminating), timer expiry or other event that matches the stop trigger event configured by the Management System via the Trace IRP TS 32.442 [24].

BM-SC	Start triggering events	Stop triggering events
MBMS Multicast service activation	Reception of MBMS Authorization Request	Reception of Deactivation Indication for user deactivation or sending of Session Stop Request for service deactivation

MME	Start triggering events	Stop triggering events
Service request	Reception of NAS: Service Request message or S11: Downlink Data Notification Note: The Service Request message shall not start a new Trace Recording Session when received after a Downlink Data Notification for the same service request instance.	Reception of S11: Modify Bearer Response or sending of NAS: SERVICE REJECT Note: Modify Bearer Response shall stop the Trace Recording Session only if it has been sent as part of the Service Request procedure
UE initiated PDN connectivity	Reception of NAS: PDN connectivity Request message	Reception of NAS PDN Connectivity Complete
Initial Attach, Tracking area update, Detach	Initial Attach: Reception of the NAS: ATTACH REQUEST or of S6a Update Location Answer Tracking Area Update: Reception of the NAS: TRACKING AREA UPDATE REQUEST Detach: Reception of the NAS: DETACH REQUEST or S3 Detach Notification or S6a Cancel Location Request or sending of S11 Delete Session Request. Note: Cancel location location shall not trigger new Trace Recording Session if it is sent as part of the tracking area update procedure. Note: The Delete Session Request message shall trigger a new Trace Recording Session only if sent as part of a Detach procedure and only if a Detach Request has not been received for the same instance of the procedure. Note: Update Location Answer shall be a start trigger for a Trace Recording Session only if sent as part of Attach procedure and if containing Trace Data.	Initial Attach: Reception of the NAS: ATTACH COMPLETE or sending of the NAS: ATTACH REJECT Tracking Area Update: Sending of the NAS: TRACKING AREA UPDATE ACCEPT or sending of NAS: TRACKING AREA UPDATE REJECT Detach: Sending of NAS: DETACH ACCEPT or S3 Detach Acknowledgement message or S6a Cancel Location Answer message or reception S11 Delete Session Response Note: Cancel Location Answer shall not stop a Trace Recording Session if it is sent as part of the TAU procedure. Note: The Delete Session Response message shall stop a Trace Recording Session only if sent as part of a Detach procedure and only if a Detach Request has not been received for the same instance of the procedure.
UE initiated PDN disconnection	Sending of the S11: Delete Session Request Note: The S11 Delete Session Request message shall trigger a new Trace Recording Session only if it is sent as part of the UE initiated PDN disconnection procedure.	Reception of NAS Deactivate EPS Bearer Context Accept
Bearer Activation/Modification/Deactivation	Bearer Activation: Reception of S11: Create Bearer Request Bearer Modification: Reception of S11: Update Bearer Request Bearer Deactivation: Reception of S11 Delete Bearer Request Note: Create Bearer Request shall not trigger a new trace recording session if it is sent due to Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures	Bearer Activation: Sending of S11: Create Bearer Response Bearer Modification: Sending of S11: Update Bearer Response Bearer Deactivation: Sending of S11: Delete Bearer Response
Handover	Inter-eNB/Intra-MME: Reception of S1AP: Path Switch Request or S1AP Handover Required Inter-eNB/Inter-MME – Inter RAT (source MME): Reception of S1AP: Handover Required Inter-eNB/Inter-MME – Inter RAT (target MME): Reception of S10/S3: Forward Relocation Request	Inter-eNB/Intra-MME: Sending of S1AP: Path Switch Request Acknowledge or S1AP: Path Switch Request Failure, or S1AP: Handover Preparation Failure or S1AP: Handover Cancel Acknowledge or receiving Handover Notify Inter eNB – Inter MME / Inter RAT (source MME): Reception of S10/S3 Forward Relocation Complete Notification or sending of S1AP Handover Cancel Acknowledge or S1AP Handover Preparation Failure Inter eNB – Inter MME /Inter RAT (target MME): Sending of S10/S3 Forward Relocation Complete Notification or of S10/S3 Relocation Cancel Response or of S10/S3 Forward Relocation Response with reject cause value

SGW	Start triggering events	Stop triggering events
PDN connection creation	Reception of the S11: Create Session Request	Sending of the S11: Create Session Response
PDN connection termination	Reception of the S11: Delete Session Request	Sending of the S11: Delete Session Response
Bearer Activation/Modification/Deactivation	Bearer Activation: Reception of the S5: Create Bearer Request or S11: Bearer Resource Command Bearer Modification: Reception of the S11: Modify Bearer Request or S5: Update Bearer Request Bearer Deletion: Reception of the S11: Deactivate Bearer Command or S5: Delete Bearer Request	Bearer Activation: Sending of the S5: Create Bearer Response Bearer Modification: Sending of the S11: Modify Bearer Response or S5: Update Bearer Response Bearer Deletion: Sending of S5: Delete Bearer Response

PGW

Start triggering events

Stop triggering events

PDN connection creation

Reception of S5: Create Session Request (GTP) or Proxy Binding Update (PMIP)

Reception of S2b: Create Session Request (GTP)

Sending of S5: Create Session Response (GTP) or Proxy Binding Update Ack (PMIP)

Sending of S2b: Create Session Response (GTP)

PDN connection termination

Reception of the S5: Delete Session Request or Proxy Binding Update

Reception of the S2b: Delete Session Request

Sending of the S5: Delete Session Response (GTP) or Proxy Binding Update ACK (PMIP)

Sending of the S2b: Delete Session Response (GTP)

Bearer Activation/Modification/Deactivation

Note: this is applicable only to GTP based S5 interface.

Bearer Activation: Sending of the S5/S2b: Create Bearer Request

Bearer Modification: Reception of the S5: Modify Bearer Request or sending of the S5/S2b: Update Bearer Request

Bearer Deletion: Reception of the S5: Delete Bearer Command or sending of S5/S2b: Delete Bearer Request

Bearer Activation: Reception of the S5/S2b: Create Bearer Response

Bearer Modification: Sending of the S5: Modify Bearer Response or reception of the S5/S2b: Update Bearer Response

Bearer Deletion: Reception of the S5/S2b: Delete Bearer Response

AMF	Start triggering events	Stop triggering events
UE initiated Registration Procedure	NAS Registration Request message from the UE	Sending of Registration Accept Receipt of Registration Complete
UE initiated Service Request Procedure	NAS message from the UE	Optional Service Accept
N2 or Xn Handover	Reception of N2 Path Switch Request message from source NG-RAN	Sending of N2 Path Switch Request Ack message to target NG-RAN
UE initiated Deregistration Procedure	NAS Deregistration Request message from the UE	Sending of Deregistration Accept
Network initiated Deregistration Procedure	AMF timer or UDM request	Receipt of Deregistration Accept
UE mobility from EPC	Receipt of N26 Forward Relocation request	Sending of N26 Forward Relocation response
UE mobility to EPC	Receipt of N2 HO Request to E-UTRAN	Receipt of Nudm_UECM_DeregistrationNotification

AUSF	Start triggering events	Stop triggering events
UE Authentication	Receipt of Nausf_UEAuthentication_authenticate request	Sending of Nausf_UEAuthentication_authenticate response

NEF	Start triggering events	Stop triggering events
Event Exposure	Receipt of Nnef_EventExposure_Subscribe from AF Receipt of Nnef_EventExposure_Unsubscribe from AF Sending of Nnef_EventExposure_Notify to AF	Sending of Nnef_EventExposure_Subscribe result indication to AF Sending of Nnef_EventExposure_Unsubscribe result indication to AF Processing of Nnef_EventExposure_Notify
PFD Management	Receipt of Nnef_PFDManagement_Fetch request from SMF Receipt of Nnef_PFDmanagement_Subscribe from SMF Sending of Nnef_PFDManagement_Notify to SMF Receipt of Nnef_PFDManagement_Unsubscribe from SMF	Sending of Nnef_PFDManagement_Fetch response to SMF Processing of Nnef_PFDmanagement_Subscribe Processing of Nnef_PFDManagement_Notify Processing of Nnef_PFDManagement_Unsubscribe
Parameter Provision	Receipt of Nnef_ParameterProvision_Update from AF	Sending of Nnef_ParameterProvision_Update result indication to AF
Trigger	Receipt of Nnef_Trigger_Request from AF Receipt of Nnef_Trigger_UpdateNotify from AF	Sending of Nnef_Trigger_Request operation result to AF Sending of Nnef_Trigger_UpdateNotify delivery report

NRF	Start triggering events	Stop triggering events
NF Management	Receipt of NFRegister/NFUpdate/NFDeregister request from NF	Sending of NFRegister/NFUpdate/NFDeregister response to NF
NF Discovery	Receipt of Nnrf_NFDiscovery_Request from NF	Sending of target NF information to the requestor

NSSF

Start triggering events

Stop triggering events

NS Selection

Receipt of Nnssf_NSSelection_Get request from AMF, NSSF in different PLMN or NRF

Sending of Nnssf_NSSelection_Get response to AMF, NSSF in different PLMN or NRF

NSSAI Availability

Receipt of Nnssf_NSSAIAvailability_Update request from AMF

Sending of Nnssf_NSSAIAvailability_Notify to AMF

Sending of Nnssf_NSSAIAvailability_Update response to AMF

Processing of Nnssf_NSSAIAvailability_Notify

PCF

Start triggering events

Stop triggering events

AM Policy Control

Receipt of Npcf_AMPolicyControl_Get request from AMF

Receipt of Npcf_AMPolicyControl_Delete request from AMF

Sending of Npcf_AMPolicyControl_UpdateNotify to AMF

Sending of Npcf_AMPolicyControl_Get response to AMF

Sending of Npcf_AMPolicyControl_Delete response to AMF

Receipt of Npcf_AMPolicyControl_UpdateNotify result from AMF

SM Policy Control

Receipt of Npcf_SMPolicyControl_Get request from SMF

Receipt of Npcf_SMPolicyControl_Delete request from SMF

Sending of Npcf_SMPolicyControl_UpdateNotify to SMF

Sending of Npcf_SMPolicyControl_Get response to SMF

Sending of Npcf_SMPolicyControl_Delete response to SMF

Receipt of Npcf_SMPolicyControl_UpdateNotify result from SMF

Policy Authorization

Receipt of Npcf_PolicyAuthorization_Create request from AF or NEF

Receipt of Npcf_PolicyAuthorization_Update request from AF or NEF

Receipt of Npcf_PolicyAuthorization_Delete request from AF or NEF

Sending of Npcf_PolicyAuthorization_Notify to AF or NEF

Receipt of Npcf_PolicyAuthorization_Subscribe request from AF or NEF

Receipt of Npcf_PolicyAuthorization_Unsubscribe request from AF or NEF

Sending of Npcf_PolicyAuthorization_Create response to AF or NEF

Sending of Npcf_PolicyAuthorization_Update response to AF or NEF

Sendng of Npcf_PolicyAuthorization_Delete response to AF or NEF

Processing of Npcf_PolicyAuthorization_Notify

Sendng of Npcf_PolicyAuthorization_Subscribe response to AF or NEF

Sendng of Npcf_PolicyAuthorization_Unsubscribe response to AF or NEF

Background data transfer policy

Receipt of Npcf_BDTPolicyControl_Update request from NEF

Receipt of Npcf_BDTPolicyControl_Get request from NEF

Sending of Npcf_BDTPolicyControl_Update response to NEF

Sending of Npcf_BDTPolicyControl_Get response to NEF

SMF	Start triggering events	Stop triggering events
UE initiated PDU Session Establishment procedure	NAS signalling from the UE, N16 signalling from VSMF Receipt of Nsmf_PDUSession_CreateSMContext request from AMF NAS signalling from the UE, N16a signalling from I-SMF	Sending of Nsmf_PDUSession_CreateSMContext response
UE initiated PDU Session Modification procedure	NAS signalling from the UE, N16 signalling from VSMF Receipt of Nsmf_PDUSession_UpdateSMContext request from AMF NAS signalling from the UE, N16a signalling from I-SMF	Sending of Nsmf_PDUSession_UpdateSMContext response
UE initiated PDU Session Release procedure	NAS signalling from the UE, N16 signalling from VSMF Receipt of Nsmf_PDUSession_ReleaseSMContext request from AMF NAS signalling from the UE, N16a signalling from I-SMF	Sending of Nsmf_PDUSession_ReleaseSMContext response
UE initiated PDU Session UP activation / deactivation	N11 request from AMF (may come from a NAS SR or Registration)	Sending of N11 response to AMF
Mobility of a PDU Session between 3GPP and N3GPP access to 5GC	NAS signalling from the UE (Request Type = "Existing PDU Session")	Sending of NAS signalling to UE
Mobility of a PDU Session from EPC	N11 request from AMF (comes from a N26 forward relocation request)	Sending of Nsmf_PDUSession_UpdateSMContext response

SMSF	Start triggering events	Stop triggering events
SMService	Receipt of Nsmsf_SMService_Activate from AMF	Receipt of Nsmsf_SMService_Deactivate from AMF

UDM	Start triggering events	Stop triggering events
UE Context Management	Receipt of Nudm_UECM_Registration request from AMF, SMF or SMSF Sending of Nudm_UECM_DeregistrationNotification to AMF, SMF or SMSF Receipt of Nudm_UECM_Deregistration request from AMF, SMF or SMSF Receipt of Nudm_UECM_Get request from AMF, SMF or SMSF	Sending of Nudm_UECM_Registration response to AMF, SMF or SMSF Processing of Nudm_UECM_DeregistrationNotification Sending of Nudm_UECM_Deregistration result indication to AMF, SMF or SMSF Sending of Nudm_UECM_Get response to AMF, SMF or SMSF
Subscriber Data Management	Receipt of Nudm_SDM_Get request from AMF, SMF or SMSF Sending of Nudm_SDM_Notification to AMF, SMF or SMSF Receipt of Nudm_SDM_Subscribe from AMF, SMF or SMSF Receipt of Nudm_SDM_Unsubscribe from AMF, SMF or SMSF	Sending of Nudm_SDM_Get response to AMF, SMF or SMSF Processing of Nudm_SDM_Notification Processing of Nudm_SDM_Subscribe Processing of Nudm_SDM_Unsubscribe
UE Authentication	Receipt of Nudm_UEAuthentication_Get request from AUSF	Sending Nudm_UEAuthentication_Get response to AUSF
Event Exposure	Receipt of Nudm_EventExposure_Subscribe request from NEF	Receipt of Nudm_EventExposure_Unsubscribe from NEF

UPF

Start triggering events

Stop triggering events

N4 Session

Receipt of N4 Session Establishment from SMF

Receipt of N4 Session Modification from SMF

Receipt of N4 Session Termination from SMF

Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
MSC Server

MGW
SGSN

GGSN
BM-SC
MME
PGW				SGW
AMF
SMF
PCF				UPF
AUSF				NEF
NRF				NSSF
SMSF				UDM

MSC Server
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare		spare	SS	Handover	LU, IMSI attach, IMSI detach	MO and MT SMS	MO and MT calls
spare

MGW
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare						spare	Context

SGSN
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare				MBMS Context	RAU, GPRS attach, GPRS detach	MO and MT SMS	PDP context
Reserved

GGSN
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare						MBMS Context	PDP Context

BM-SC
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare						Spare	MBMS activation

MME

Bit 8

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

spare

Spare

Handover

Bearer

Activation

Modification

Deletion

UE initiated PDN disconnection

Initial Attach, Tracking area update, Detach

Service requests

UE initiated PDN connectivity request

PGW

SGW

Bit 8

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

spare

Bearer

Activation

Modification

Deletion

PDN connection termination

PDN connection creation

Spare

Bearer

Activation

Modification

Deletion

PDN connection termination

PDN Connection creation

AMF

Bit 8

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Spare

UE Mobility to EPC

UE Mobility from EPC

Network Deregistration

UE Deregistration

Handover

Service

Request

Registration

SMF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare	Spare	Mobility from EPC	Mobility between 3GPP and N3GPP to 5GC	PDU Session UP activation / deactivation	PDU Session Release	PDU Session Modification	PDU Session Establishment

PCF
Bit 4	Bit 3	Bit 2	Bit 1
BDT policy	Authorization	SM Policy	AM Policy

UPF
Bit 4	Bit 3	Bit 2	Bit 1
Spare	Spare	Spare	N4 Session

AUSF				NEF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	spare	UE Authentication	Trigger	Parameter Provision	PFD Management	Event Exposure

NRF				NSSF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	NF Discovery	NF Management	spare	spare	NSSAI	NS Selection

SMSF				UDM
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	spare	SM Service	Event Exposure	UE Authentication	Subscriber data	UE Context

If a bit is set to 1 the given event shall be traced, i.e. a Trace Recording Session shall be started for that event.

If a bit is set to 0 the given event should not be traced, i.e. Trace Recording Session should not be started.

5.2 Void

5.3 Trace Depth (CM)

This conditional mandatory parameter defines how detailed information should be recorded in the Network Element. The Trace Depth is a parameter for Trace Session level, i.e., the Trace Depth is the same for all of the NEs to be traced in the same Trace Session.

The following table describes the values of the Trace Depth parameter.

Trace Depth	Meaning
Minimum	Recording of some IEs in the signalling messages plus any vendor specific extensions to this definition, in decoded format.
Medium	Recording of some IEs in the signalling messages together with the radio measurement IEs plus any vendor specific extensions to this definition, in decoded format.
Maximum	Recording entire signalling messages plus any vendor specific extensions to this definition, in encoded format.
MinimumWithoutVendorSpecificExtension	Recording of some IEs in the signalling messages in decoded format.
MediumWithoutVendorSpecificExtension	Recording of some IEs in the signalling messages together with the radio measurement IEs in decoded format.
MaximumWithoutVendorSpecifcExtension	Recording entire signalling messages in encoded format.

At least one of Minimum, Medium or Maximum trace depth shall be supported depending on the NE type (see trace record description in TS 32.423 [3] for details).

Trace depth shall be an enumerated parameter with the following possible values:

Minimum (0),

Medium (1)

Maximum (2)

MinimumWithoutVendorSpecificExtension (3)

MediumWithoutVendorSpecificExtension (4)

MaximumWithoutVendorSpecificExtension (5)

5.4 List of NE Types (CM)

This conditional mandatory parameter defines the Network Element types where Trace Session activation is needed. The condition of this parameter is that signalling based activation mechanism is used except in IMS. This parameter determines whether the Trace Session Activation shall be propagated further to other Network Elements. In the management based activation mechanism, and in the signalling based activation mechanism for IMS, this parameter is not needed.

The following list contains the Network Element types:

– MSC Server

– MGW

– RNC

– SGSN

– GGSN

– BM-SC

– MME

– SGW

– PDN GW

– eNB

– AMF

– PCF

– SMF

– UPF

– gNB-CU-CP

– gNB-CU-UP

– gNB-DU

– AUSF

– SMSF

– ng-eNB

– HSS

– UDM

Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
SGW	MME	BM-SC	RNC	GGSN	SGSN	MGW	MSC-S
gNB-CU-UP	gNB-CU-CP	UPF	PCF	SMF	AMF	eNB	PDN GW
spare	spare	UDM	HSS	SMSF	AUSF	ng-eNB	gNB-DU

If a bit is set to 1, Trace Session to that Network Element shall be activated.

If a bit is set to 0, Trace Session is not needed in that Network Element.

5.5 List of Interfaces (CO)

This is an optional parameter, which defines the interfaces to be recorded in the Network Element.

The following list contains the list of interfaces in each Network Element:

– MSC Server: A, Iu-CS, Mc and MAP (G, B, E, F, D, C) interfaces, CAP.

– MGW: Mc, Nb-UP, Iu-UP.

– RNC: Iu-CS, Iu-PS, Iur, Iub and Uu interfaces.

– SGSN: Gb, Iu-PS, Gn, MAP (Gr, Gd, Gf), CAP (Ge), Gs, S6d, S4, S3, S13′ interfaces.

– GGSN: Gn, Gi and Gmb interfaces.

– S-CSCF: Mw, Mg, Mr and Mi interfaces.

– P-CSCF: Gm and Mw interfaces.

– I-CSCF: Cx, Dx, Mg, Mw.

– MRFC: Mp, Mr.

– MGCF: Mg, Mj, Mn.

– IBCF: Ix, Mx.

– E-CSCF: Mw, Ml, Mm, Mi/Mg.

– BGCF: Mi, Mj, Mk.

– AS: Dh, Sh, ISC, Ut.

– HSS: MAP (C, D, Gc, Gr), Cx, S6d, S6a, Sh, N70, N71 and NU1 interfaces and location and subscription information.

– EIR: MAP (F), S13, S13’, MAP (Gf)

– BM-SC: Gmb interface.

– MME: S1-MME, S3, S6a, S10, S11, S13

– SGW: S4, S5, S8, S11, Gxc

– PDN GW: S2a, S2b, S2c, S5, S6b, Gx, S8, SGi

– eNB/en-gNB: S1-MME, X2, Uu, F1-C, E1

– AMF: N1, N2, N8, N11, N12, N14, N15, N20, N22, N26

– AUSF: N12, N13

– NEF: N29, N30, N33

– NRF: N27

– NSSF: N22, N31

– PCF: N5, N7, N15

– SMF: N4, N7, N10, N11, S5-C, N16, N16a

– SMSF: N20, N21

– UDM: N8, N10, N13, N21, NU1

– UPF: N4

– ng-eNB: NG-C, Xn-C, Uu

– gNB-CU-CP: NG-C, Xn-C, Uu, F1-C, E1, X2-C

– gNB-CU-UP: E1

– gNB-DU: F1-C

NOTE 1: For IMS Network Elements other than P-CSCF and S-CSCF the interfaces included in the Trace Job for a particular type of IMS session are configured in the Management System via the Trace IRP (3GPP TS 32.442 [24]).

NOTE 2: The logical RAN node.gNB and en-gNB are defined in 3GPP TS 38.401 [44] clause 3.1. Both of these logical nodes are comprised of the following 3 Network Elements or Managed Functions (MFs): gNB-CU-CP, gNB-CU-UP & gNB-DU in either a 3-split, 2-split or non-split deployment scenario, as described in 3GPP TS 28.541 [46] clause 4.2.1 (and 4.3.2.1).

– The "List of interfaces" for these 4 Network Element types are combined into a single bitmap parameter below for the logical NG-RAN node, to be consumed and interpreted by each of these Network Elements irrespective of NR SA deployment scenario i.e.

(Logical NG-RAN node) ng-eNB/gNB-CU-CP/gNB-CU-UP/gNB-DU: NG-C, Xn-C, Uu, F1-C, E1

– The "List of interfaces" for these 3 Network Element types are combined with the existing eNB Network Element bitmap into a single bitmap parameter below for both eNB & en-gNB node, to be consumed and interpreted by each of these Network Elements irrespective of NR NSA deployment scenario i.e.

(Logical eNB/en-gNB) eNB/gNB-CU-CP/gNB-CU-UP/gNB-DU: S1-MME, X2, Uu, F1-C, E1

Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
MSC Server

MGW
SGSN

GGSN
RNC
BM-SC
MME
SGW
PDN GW
(Logical eNB/en-gNB) eNB/gNB-CU-CP/gNB-CU-UP/gNB-DU
HSS

EIR
AMF

PCF
SMF
UPF
(Logical NG-RAN node) ng-eNB/gNB-CU-CP/gNB-CU-UP/gNB-DU
UDM

MSC Server
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
CAP	MAP-F	MAP-E	MAP-B	MAP-G	Mc	Iu	A
spare						MAP-C	MAP-D

SGSN
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Ge	Gs	MAP-Gf	MAP-Gd	MAP-Gr	Gn	Iu	Gb
spare				S13′	S3	S4	S6d

MGW
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare					Iu-UP	Nb-UP	Mc

GGSN
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare					Gmb	Gi	Gn

RNC
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare				Uu	Iub	Iur	Iu

BM-SC
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare							Gmb

MME
Bit 8	Bit 7		Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare		S13		S11	S10	S6a	S3	S1-MME

SGW
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare			Gxc	S11	S8b	S5	S4

PDN GW
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
SGi	S8b	Gx	S6b	S5	S2c	S2b	S2a

(eNB/en-gNB) eNB(Management Based Activation and Signaling Based Activation)/gNB-CU-CP/gNB-CU-UP/gNB-DU (Signaling Based Activation only)
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare	Spare	Spare	E1	F1-C	Uu	X2	S1-MME

NOTE 3: For NR NSA, the existing 1 bitmaskis extended to representation for eNB to additionally include all 3 NEs of the logical en-gNB (relevant interfaces only). The receiving MF entity interprets only the bits that are valid for its interface.

HSS
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Sh	S6a	S6d	Cx	MAP-Gr	MAP-Gc	MAP-D	MAP-C
spare	spare	spare	spare	spare	NU1	N71	N70

EIR
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare				MAP-Gf	S13’	S13	MAP-F

AMF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
N20	N15	N14	N12	N11	N8	N2	N1
spare						N26	N22

PCF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	spare	spare	spare	N15	N7	N5

SMF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	N16a	N16a	S5-C	N11	N10	N7	N4

UPF
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	spare	spare	spare	spare	spare	N4

(NG-RAN node) ng-eNB/gNB-CU-CP/gNB-CU-UP/gNB-DU (Management Based Activation and Signaling Based Activation),

(en-gNB) gNB-CU-CP/gNB-CU-UP/gNB-DU (Management Based Activation only)

Bit 8

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

spare

E1-C

F1-C

Xn-C/X2

NG-C

UDM
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
spare	spare	spare	NU1	N21	N13	N10	N8

NOTE 4: For Management Based Activation, only this one NG-RAN bitmask above needs to be used for cell traffic trace functionality (not 2 different bitmasks).
As the gNB-CU-CP can be either logical gNB role or logical en-gNB role, then Bits 1 and 2 can be interpreted differently depending on the role and whether it is an NSA user or SA user.
SA User.
– Bit 1 = NG-C
– Bit 2 = Xn-C
NSA User
– Bit 1 = N/A
– Bit 2 = X2

If a bit is set to 1, the interface should be traced in the given Network Element.

If a bit is set to 0, that interface should not be traced in the given Network Element.

NOTE 5: The bit significance of the bitmaps defined above for the OAM interface can be different from the bit significance of the corresponding bitmaps in the signalling interface specifications.

5.6 Trace Reference (M)

The Trace Reference parameter shall be globally unique, therefore the Trace Reference shall compose as follows:

MCC+MNC+Trace ID, where the MCC and MNC are coming with the Trace activation request from the management system to identify one PLMN containing the management system, and Trace ID is a 3 byte Octet String.

NOTE 1: Trace ID referred here is the same as Trace Reference in previous releases.

NOTE 2: The MCC+MNC being part of the Trace Reference from Rel-8 onwards (e.g. ignored by Rel-6 / Rel-7 UTRAN Network Elements), the uniqueness of the Trace Reference may not be guaranteed with Rel-6 / Rel-7 Network Element(s) involved in the Trace.

5.7 Trace Recording Session Reference (M)

This parameter shall be a 2 byte Octet String.

5.8 Void

5.9 Trace Collection Entity (TCE) IP Address (CM,CO)

For file-based reporting, this is a parameter which defines the IP address to which the Trace records shall be transferred. Either an IPv4 or an IPv6 address shall be signalled.

This parameter is mandatory when file based tracing and/or MDT in EPS or 5GS is supported.This parameter is optional when file based tracing in UMTS is supported.

This parameter may be present only if the Trace Reporting MnS Consumer URI parameter is not present.

5.9a Job Type (M)

The Job Type is a mandatory parameter. The condition is either MDT or RLF or RCEF data collection functionality is supported. It defines if a single trace job, a combined MDT and trace job or RLF report collection job or RCEF report collection job is activated. This parameter also defines the MDT mode. The Job Type parameter is an enumerated type with the following values:

– Immediate MDT only (0);

– Logged MDT only (1);

– Trace only (2);

– Immediate MDT and Trace (3);

– RLF reports only (4) ;

– RCEF reports only (5).

– Logged MBSFN MDT (6).

NOTE 1: The Job Type "RLF reports only" and "RCEF reports only" are applicable only in management based trace activation in E-UTRAN and NG-RAN.

NOTE 2: Logged MBSFN MDT is applicable only for activation in E-UTRAN.

5.9b PLMN Target (CM)

This parameter defines the PLMN for which sessions shall be selected in the Trace Session in case of management based activation when several PLMNs are supported in the RAN (this means that shared cells and not shared cells are allowed for the specified PLMN. Furthermore, several PLMNs can be used for not shared RAN cases as well as for shared RAN cases.). Only the sessions may be selected where the PLMN that the UE reports as selected PLMN is the same as the PLMN Target.

Note that the PLMN Target might differ from the PLMN specified in the Trace Reference, as that specifies the PLMN that is containing the management system requesting the Trace Session from the NE.

5.9c Trace Reporting Consumer URI (CM)

For streaming reporting, this is a parameter which defines the URI of the Trace Reporting MnS consumer to which the Trace records shall be streamed.

The detailed URI structure is defined in clause 4.4 TS 32.158 [53].

This parameter is mandatory when streaming trace and/or MDT is supported.The parameter may be present only if the IP address of TCE is not present.

5.10 MDT specific configuration parameters (CM)

5.10.1 Void

5.10.2 Area Scope

The Area Scope optional parameter defines the area in terms of Cells or Tracking Area/Routing Area/Location Area where the MDT data collection shall take place. The area scope specified in an MDT session shall support the PLMNs of the MDT PLMN list (defined in clause 5.10.24). If the parameter is not present the MDT data collection shall be done throughout the PLMNs of the MDT PLMN list. For further details see also TS 37.320 [30].

The Area Scope parameter in UMTS is either:

– list of Cells, identified by CGI. Maximum 32 CGI can be defined.

– List of Routing Area, identified by RAI. Maximum of 8 RAIs can be defined.

– List of Location Area, identified by LAI. Maximum of 8 LAIs can de defined.

The Area Scope parameter in LTE and NR is either:

– list of Cells, identified by E-UTRAN-CGI or NG-RAN CGI. Maximum 32 CGI can be defined.

– List of Tracking Area, identified by TAC. Maximum of 8 TAC can be defined.

– List of Tracking Area Identity, identified by TAC with associated plmn-Identity perTAC-List containing the PLMN identity for each TAC. Maximum of 8 TAI can be defined. For further details see also TS 36.331[32].

5.10.3 List of Measurements

This parameter is mandatory if the Job Type is configured for Immediate MDT or combined Immediate MDT and Trace. This parameter defines the measurements that shall be collected. For further details see also TS 37.320 [30]. The parameter is 4 octet long bitmap.

The parameter can have the following values in UMTS:

– M1: CPICH RSCP and CPICH Ec/No measurement by UE.

– M2: For 1.28 Mcps TDD, P-CCPCH RSCP and Timeslot ISCP measurement by UE.

– M3: SIR and SIR error (FDD) by NodeB

– M4: UE power headroom (UPH) by the UE, applicable for E-DCH transport channels.

– M5: Received total wideband power (RTWP) by Node B

– M6: Data Volume measurement, separately for DL and UL, by RNC.

– M7: Throughput measurement, separately for DL and UL, per RAB and per UE, by RNC.

– Any combination of the above

Detailed information for M3, M5, is defined TS 25.215 [54], for M1, M2 in TS 25.331[31] and for M4 in TS 25.321[55].

The parameter can have the following values in LTE:

– M1: RSRP, RSRQ and SINR measurement by UE

– M2: Power Headroom (PH) measurement by UE
NOTE: Available from MAC layer

– M3: Received Interference Power measurement by eNB

– M4: Data Volume measurement separately for DL and UL, per QCI per UE, by eNB

– M5: Scheduled IP Throughput measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB

– M6: Packet Delay measurement, separately for DL and UL, per QCI per UE, see UL PDCP Delay, by the UE, and Packet Delay in the DL per QCI, by the eNB

– M7: Packet Loss rate measurement, separately for DL and UL per QCI per UE, by the eNB

– M8: RSSI measurement by UE for WLAN and Bluetooth^®

– M9: RTT measurement by UE only for WLAN

– And any combination of above.

Detailed information for M4, M5, M6, M7 is defined TS 36.314 [56], for M1, M3, M8, M9 in TS 36.331[31], for M2 in TS 36.321[57].

The parameter can have the following values in NR:

– M1: DL signal quantities measurement results for the serving cell and for intra-frequency/Inter-frequency/inter-RAT neighbour cells, including cell/beam level measurement by UE.

– M2: Power headroom (PH) measurement by UE

– M3 is not supported by this release

– M4: PDCP SDU Data volume measurement separately for DL and UL, per DRB per UE by gNB

– M5: Average UE throughput measurement separately for DL and UL, per DRB per UE and per UE for the DL, per DRB per UE and per UE for the UL, by gNB

– M6: Packet delay measurement, separately for DL and UL, per DRB per UE by gNB

– M7: Packet loss rate measurement, separately for DL and UL, per DRB per UE by gNB

– M8: RSSI measurement by UE for WLAN and Bluetooth®

– M9: RTT measurement by UE for WLAN

– And any combination of above

Detailed information for M4, M5, M6, M7 is defined in TS 28.552 [58] and TS 38.314 [50], for M1, M8, M9 in TS 38.331[43], for M2 in TS 38.321[51].

UMTS
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
M7 for DL	M6 for UL	M6 for DL	M5	M4	M3	M2	M1
spare							M7 for UL
spare
spare

LTE
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
M7 for DL	M6 for DL	logging of M1 from event triggered measurement reports according to existing RRM configuration	M5	M4	M3	M2	M1
spare				M7 for UL	M6 for UL	M9	M8
spare
spare

NR
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
M8	logging of M1 from event triggered measurement reports according to existing RRM configuration.	M7 for DL	M6 for DL	M5 for DL	M4 for DL	M2 for DL	M1 for DL
spare			M7 for UL	M6 for UL	M5 for UL	M4 for UL	M9
spare
spare

NOTE: Value "1" indicates "activate" and value "0" indicates "do not activate".

5.10.4 Reporting Trigger

This parameter is mandatory if the list of measurements parameter is configured for UE side measurement ( M1 in LTE and NR, and M1/M2 in UMTS) and the jobtype is configured for Immediate MDT or combined Immediate MDT and Trace.

The parameter shall not have the combination of periodical, event based and event based periodic reporting at the same time, i.e. :

– For LTE and NR, only one of the bits 1, 2, and 5 can be set.

– For UMTS, bit 1 cannot be set at the same time with either bit 3 or bit 4.

The parameter is one octet long bitmap and can have the following values in LTE, UMTS, NR (detailed definition of the parameter is in 3GPP TS 37.320 [30]):

– Periodical,

– Event A2 for LTE and NR:

– Event 1f for UMTS,

– Event 1i for UMTS 1.28 Mcps TDD,

– A2 event triggered periodic for LTE and NR.

– All configured RRM event triggers for M1 measurement for LTE and NR. See also TS 37.320 [30] clauses 5.2.1.1 and 5.4.1.1.

– All configured RRM event triggers for M1/M2 measurement for UMTS. See also TS 37.320 [30] clause 5.3.1.1.

Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Reserved	All configured RRM event triggers for UMTS	All configured RRM event triggers for LTE and NR	A2 event triggered periodic for LTE and NR	Event 1i for UMTS 1.28 MCPS TDD	Event 1f for UMTS	Event A2 for LTE and NR	Periodical

5.10.5 Report Interval

This parameter is mandatory if the Reporting trigger is configured for Periodic UE side measurements (M1 in LTE or NR and M1/M2 in UMTS) and the jobtype is configured for Immediate MDT or combined Immediate MDT and Trace. The parameter indicates the interval between the periodical measurements to be taken when UE is in connected mode.

The parameter is enumerated type with the following values in milliseconds in case of UMTS (detailed definition is in 3GPP TS 25.331 [31]:

– 250 ms (0),

– 500 ms (1),

– 1000 ms (2),

– 2000 ms (3),

– 3000 ms (4),

– 4000 ms (5),

– 6000 ms (6),

– 8000 ms (7),

– 12000 ms (8),

– 16000 ms (9),

– 20000 ms (10),

– 24000 ms (11),

– 28000 ms (12),

– 32000 ms (13),

– 64000 ms (14)

The parameter can have the following values in LTE (detailed definition is in 3GPP TS 36.331 [32]):

– 120 ms (0),

– 240 ms (1),

– 480 ms (2),

– 640 ms (3),

– 1024 ms (4),

– 2048 ms (5),

– 5120 ms (6),

– 10240ms (7),

– 1 min=60000 ms (8),

– 6 min=360000 ms (9),

– 12 min=720000 ms (10),

– 30 min=1800000 ms (11),

The parameter can have the following values in NR (detailed definition is in 3GPP TS 38.331 [43]):

– 120 ms (0),

– 240 ms (1),

– 480 ms (2),

– 640 ms (3),

– 1024 ms (4),

– 2048 ms (5),

– 5120 ms (6),

– 10240 ms (7),

– 20480 ms (8),

– 40960 ms (9),

– 1 min=60000 ms (10),

– 6 min=360000 ms (11),

– 12 min=720000 ms (12),

– 30 min=1800000 ms (13),

5.10.6 Report Amount

The parameter is mandatory if the reporting trigger is configured for periodical UE side measurement (M1 in LTE or NR and M1/M2 in UMTS) and the jobtype is configured for Immediate MDT or combined Immediate MDT and Trace. The parameter defines the number of measurement reports that shall be taken for periodical reporting while UE is in connected mode. Detailed definition of the paremeter is in TS 38.331 [43], TS 36.331 [32] and TS 25.331 [31].

The parameter is an enumerated type with the following values in UMTS, in LTE, and in NR:

– 1 (0),

– 2 (1),

– 4 (2),

– 8 (3),

– 16 (4),

– 32 (5),

– 64 (6),

– infinity (7)

5.10.7 Event Threshold for Event A2

The parameter is mandatory if the report trigger parameter is configured for A2 event reporting or A2 event triggered periodic reporting and the Job Type parameter is configured for Immediate MDT or combined Immediate MDT and Trace.

For trigger quantity RSRP:

Detailed definition of the parameter for LTE is in TS 36.331 [32].

The parameter is an Integer number between 0-97.

Detailed definition of the parameter for NR is in TS 38.331 [43].

The parameter is an Integer number between 0-127.

For trigger quantity RSRQ:

Detailed definition of the parameter for LTE is in 3GPP TS 36.331 [32].

The parameter is an Integer number between 0-34.

Detailed definition of the parameter for NR is in 3GPP TS 38.331 [43].

The parameter is an Integer number between 0-127.

For trigger quantity SINR:

Detailed definition of the parameter for LTE is in 3GPP TS 36.331 [32]

The parameter is an Integer number between 0-127.

Detailed definition of the parameter for NR is in 3GPP TS 38.331 [43].

The parameter is an Integer number between 0-127

5.10.7a Void

5.10.8 Logging Interval

The parameter is mandatory if the Job Type is configured for Logged MDT or Logged MBSFN MDT. The parameter defines the periodicity for logging MDT measurement results for periodic downlink pilot strength measurement when UE is in Idle or Inactive mode.

Detailed definition of the parameter is in 3GPP TS 37.320 [30].

The parameter is an enumerated type with the following values in UMTS, and LTE as per defined in TS 25.331 [31] and TS 36.331 [32] :

– 1280 ms (0),

– 2560 ms (1),

– 5120 ms (2),

– 10240 ms (3),

– 20480 ms (4),

– 30720 ms (5),

– 40960 ms (6),

– 61440 ms (7)

The parameter is an enumerated type with the following values in NR as per defined in 3GPP TS 38.331 [43]:

– 1280 ms (0),

– 2560 ms (1),

– 5120 ms (2),

– 10240 ms (3),

– 20480 ms (4),

– 30720 ms (5),

– 40960 ms (6),

– 61440 ms (7)

– 320 ms (8)

– 640 ms (9)

– Infinity (10).

5.10.9 Logging Duration

The parameter is mandatory if the the Job Type parameter is configured for Logged MDT or Logged MBSFN MDT. The parameter determines the validity of MDT logged configuration for IDLE and INACTIVE mode. The timer starts at time of receiving configuration by the UE, and continues independent of UE state transitions and RAT or RPLMN changes.

Detailed definition of the parameter is in TS 37.320 [30], TS 25.331 [31], TS 36.331 [32] and TS 38.331[43]:

The parameter is an enumerated type with the following values in UMTS, LTE and NR:

– 600 sec (0),

– 1200 sec (1),

– 2400 sec (2),

– 3600 sec (3),

– 5400 sec (4),

– 7200 sec (5)

5.10.10 Void

5.10.11 Trace Collection Entity (TCE) Id

This is a mandatory parameter for Logged MDT which defines the TCE Id which is sent to the UE. The UE returns it to the network together with the logged data. The network has a configured mapping of the TCE Id and the destination to which trace records shall be transferred.

The destination is determined considering the PLMN (delivered as part of the Trace Reference) and the IP address of TCE for the file-based trace reporting, or URI of the TCE or MnS trace reporting MnS consumer for the streaming trace reporting. The mapping needs to be unique within the PLMN. The size of the parameter is one byte.

For further details on the procedure see clause 4.1.1.2a for UTRAN, clauses 4.1.1.6a and 4.1.1.6b for E-UTRAN and clause 4.1.1.9.2 for NR.

5.10.12 Anonymization of MDT Data

This is a mandatory parameter for management based MDT when Job Type is

– Immediate MDT only (0);

– Logged MDT only (1);

– Immediate MDT and Trace (3).

– Logged MBSFN MDT (6).

This configuration parameter provides anonymization of MDT data (Refer to clause 4.7).

The parameter is an enumerated type with the following possible values:

No Identity (0);

IMEI-TAC (1)

5.10.13 Event Threshold for Event 1f

The parameter is mandatory if the reporting trigger parameter is configured for 1f event reporting and the job type parameter is configured for Immediate MDT or combined Trace and Immediate MDT.

The parameter defines the threshold for reporting UMTS M1 measurements for 1f event based reporting trigger Detailed definition of the parameter is in 3GPP TS 25.331 section 14.1.2.6 [31].

– The parameter is an Integer number between -120-165

The range used depends on the measurement as configured by the parameter "measurement quantity":

– CPICH RSCP the range is: -120 – 25 dBm

– For CPICH Ec/No the range is -24 – 0 dB

– For Pathloss 30-165 dB.

5.10.14 Event Threshold for Event 1i

The parameter is mandatory if the reporting trigger parameter is configured for 1i event reporting and the Job Type parameter is configured for Immediate MDT or combined Trace and Immediate MDT.

The parameter defines the threshold for reporting UMTS M2 measurements for 1i event based reporting trigger. Detailed definition of the parameter is in 3GPP TS 25.331 section 14.1.3.3. [31].

– The parameter is an Integer number between -120 .. -25

5.10.15 Measurement Quantity

The parameter is mandatory if the reporting trigger parameter is configured for 1f event reporting and the Job Type parameter is configured for Immediate MDT or combined Trace and Immediate MDT.

The parameter describes for what M1 measurements the Event Threshold 1f parameter is applicable.

The parameter is a bitmap with the following values:

Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Reserved	Reserved	Reserved	Reserved	Reserved	Pathloss	CPICH RSCP	CPICH Ec/N0

No more than one bit shall be selected at a time.

This parameter is only applicable to UMTS.

5.10.16 void

5.10.17 void

5.10.18 void

5.10.19 Positioning Method

This parameter is optional and is used only if the Job Type is set to Immediate MDT or Immediate MDT and Trace.

This parameter defines what positioning method should be used for the MDT job. The parameter is a bitmap, each bit represents a positioning method. The parameter is applicable only for LTE and NR. In LTE the bit1 (GNSS) may be selected only if the M1 measurement is selected in the "List of measurements" parameter (defined in Section 5.10.3).

For LTE, if the positioning method parameter indicates both E-Cell ID and GNSS positioning, the eNB may use E-Cell ID measurement collection only if the UE does not provide GNSS based location information.

For NR, the detailed actions associated with each positioning method are specified in TS 38.305 [52].

LTE
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare						E-Cell ID	GNSS

NR
Bit 8	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1
Spare							GNSS

If the parameter is not present, then best effort positioning method is used (i.e. in worst scenario only cell ID).

5.10.20 Collection Period for RRM Measurements LTE

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and the bit 3 (M3) of the list of measurements parameter (defined in Section 5.10.3) in LTE is set to 1. The parameter is used only in case of RAN side measurements whose configuration is determined by RRM.

This measurement parameter defines the collection period that should be used to collect available measurement samples in case of RRM configured measurements. The same collection period should be used for all such measurements that are requested in the same MDT or combined Trace and MDT job.

The parameter is an enumerated type with the following values (detailed definition is in 3GPP TS 36.413 [36]):

– 100 ms (0)

– 1000 ms (1)

– 1024 ms (2),

– 1280 ms (3),

– 2048 ms (4),

– 2560 ms (5),

– 5120 ms (6),

– 10000 ms (7),

– 10240 ms (8),

– 1 min (9).

Some values may not be always available e.g., due to the large amount of logging they would generate in a highly loaded network. The selection of a specific subset of supported values at the eNB is vendor-specific.

5.10.21 Collection Period for RRM Measurements UMTS

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bits 4 (M4), 5 (M5) of the list of measurements parameter (defined in Section 5.10.3) in UMTS is set to 1. The parameter is used only in case of RAN side measurements whose configuration is determined by RRM.

The parameter is an enumerated type with the following values:

– 100ms (0)

– 250 ms (1)

– 500 ms (2)

– 1000 ms (3),

– 2000 ms (4),

– 3000 ms (5),

– 4000 ms (6),

– 6000 ms (7),

5.10.22 Measurement Period UMTS

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and either the bit 6 or bit 7 or bit 8 or bit 9 of list of measurements parameter in UMTS (M6 for DL or M6 for UL or M7 for DL or M7 for UL) is set to 1.

This measurement parameter defines the measuremet period that should be used for the Data Volume and Throughput measurements made by the RNC. The same measurement period should be used for the UL and DL.

The parameter is an enumerated type with the following values:

– 1000 ms (0),

– 2000 ms (1),

– 3000 ms (2),

– 4000 ms (3),

– 6000 ms (4),

– 8000 ms (5),

– 12000 ms (6),

– 16000 ms (7),

– 20000 ms (8),

– 24000 ms (9),

– 28000 ms (10),

– 32000 ms (11),

– 64000 ms (12).

5.10.23 Measurement Period LTE

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and either the bit 4 or bit 5 of list of measurements parameter in LTE (M4 or M5) is set to 1.

This measurement parameter defines the measuremet period that should be used for the Data Volume and Scheduled IP Throughput measurements made by the eNB. The same measurement period should be used for the UL and DL.

The parameter is an enumerated type with the following values:

– 1024 ms (0),

– 2048 ms (2),

– 5120 ms (4),

– 10240 ms (5)

– 1 min (6).

5.10.24 MDT PLMN List

This is an optional parameter indicating the PLMNs where measurement collection, status indication and log reporting is allowed. E.g. the UE performs these actions for Logged MDT when the RPLMN is part of this set of PLMNs. Maximum of 16 PLMNs can be defined.

To the UE it is communicated as the plmn-IdentityList. Between the NEs it is communicated either as the Management Based MDT PLMN List or as the Signalling Based MDT PLMN List, depending on how the MDT was activated. For further details see also TS 37.320 [30], TS 36.331 [32], TS 38.331 [43], TS 36.413 [36] and TS 38.413 [49].

5.10.25 MBSFN Area List

MBSFN Area(s) for MBSFN measurement logging. The MBSFN Area consists of a MBSFN Area ID and Carrier Frequency (EARFCN). The target MBSFN area List can have up to 8 entries.

If target MBSFN area(s) is configured, UE applies it in addition to other restrictions such as the logging area. The UE will log measurements as long as it receives MBMS service from an indicated target MBSFN area and is within the configured logging area.

For further details see also TS 37.320 [30], TS 36.331 [32] and TS 36.413 [36].

This parameter is applicable only if the Job Type is Logged MBSFN MDT and for eUTRAN only.

5.10.26 Area Configuration for Neighbouring Cells

This NR parameter is optional for logged MDT and defines the area for which UE is requested to perform measurement logging for neighbour cells which have a list of carrier frequencies. Each frequency will have one PCI that will list out the neighbouring cell. The maximum number of cell identities to be configured as part of area configuration is 32. If it is not configured, the UE shall perform measurement logging for all the neighbour cells.

5.10.27 Report Type for Logged MDT

This NR parameter is mandatory and defines report type for logged MDT as:

– periodical.

– event triggered.

5.10.28 Event List for Event Triggered Measurement

This NR parameter is mandatory for event triggered measurement in the case of logged MDT. Each trace session shall configure at most one event. The UE shall perform logging of measurements only upon certain condition being fulfilled:

– Out of coverage.

– L1 event.

Detailed definition of the parameter is in 3GPP TS 38.331 [43].

5.10.29 Sensor Information

This NR parameter is optional and defines which sensor information shall be included in logged MDT and immediate MDT measurement if they are available. The following sensor measurement can be included or excluded for the UE.

– Barometric pressure.

– UE speed.

– UE orientation.

Detailed definition of the parameter is in TS 38.331 [43].

5.10.30 Collection Period for RRM Measurements NR

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bits 3 (M4) or 4 (M5) of the list of measurements parameter (defined in Section 5.10.3) in NR is set to 1. The parameter is used only in case of RAN side measurements whose configuration is determined by RRM.

The parameter is an enumerated type with the following values (detailed definition is in 3GPP TS 38.413 [49]:

– 1024 ms (0),

– 2048 ms (1),

– 5120 ms (2),

– 10240 ms (3),

– 60000 ms (4).

5.10.31 Void

5.10.32 Collection Period M6 in LTE

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bit 7 or bit 11 of list of measurements parameter (defined in Section 5.10.3) in LTE (M6 for DL or M6 for UL) is set to 1.

This measurement parameter defines the collection period that should be used for packet delay measurement made by the eNB. The same collection period should be used for the UL and DL.

The parameter is an enumerated type with the following values (detailed definition is in 3GPP TS 36.413 [36]):

– 1024 ms (0),

– 2048 ms (1),

– 5120 ms (2),

– 10240 ms (3)

5.10.33 Collection Period M7 in LTE

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bit 8 or bit 12 of list of measurements parameter (defined in Section 5.10.3) in LTE (M7 for DL or M7 for UL) is set to 1.

This measurement parameter defines the collection period that should be used for packet loss rate measurement made by the eNB. The same collection period should be used for the UL and DL.

The parameter is an integer type with the following values (detailed definition is in 3GPP TS 36.413 [36]):

1..60 min

5.10.34 Collection Period M6 in NR

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bit 5 or bit 12 of list of measurements parameter (defined in Section 5.10.3) in NR (M6 for DL or M6 for UL) is set to 1.

This measurement parameter defines the collection period that should be used for packet delay measurement made by the gNB. The same collection period should be used for the UL and DL.

The parameter is an enumerated type with the following values (detailed definition is in 3GPP TS 38.413 [49]):

– 120 ms (0),

– 240 ms (1),

– 480 ms (2),

– 640 ms (3)

– 1024 ms (4),

– 2048 ms (5),

– 5120 ms (6),

– 10240 ms (7)

– 20480 ms (8),

– 40960 ms (9),

– 1 min (10)

– 6 min (11).

– 12 min (12)

– 30 min (13)

5.10.35 Collection Period M7 in NR

This parameter is mandatory if the Job Type is set to Immediate MDT or Immediate MDT and Trace and any of the bit 6 or bit 13 of list of measurements parameter (defined in Section 5.10.3) in NR (M7 for DL or M7 for UL) is set to 1.

This measurement parameter defines the collection period that should be used for packet loss rate measurement made by the gNB. The same collection period should be used for the UL and DL.

The parameter is an integer type with the following values (detailed definition is in 3GPP TS 38.413 [49]):

1..60 min

5.10.36 Event Threshold for L1 Event

The parameter is mandatory for event triggered measurement in the case of logged MDT in NR and the event type is configured for L1 event.

The parameter defines the threshold for reporting measurements in NR Logged MDT for L1 event based reporting trigger. Detailed definition of the parameter is in TS 38.331 [43] and TS 38.413 [49].

The range used depends on the used measurement quantity:

– RSRP range: 0 – 127 (for calculating the actual value see RSRP-Range in TS 38.331 [43])

– RSRQ range: 0 – 127 (for calculating the actual value see RSRQ-Range in TS 38.331 [43]).

5.10.37 Hysteresis for L1 Event

The parameter is mandatory for event triggered measurement in the case of logged MDT in NR and the event type is configured for L1 event.

The parameter is used within the entry and leave condition of the L1 event triggered reporting in NR Logged MDT. Detailed definition of the parameter is in TS 38.331 [43] and TS 38.413 [49].

The parameter is an Integer number between 0 .. 30. For calculating the actual value see Hysteresis in TS 38.331 [43]).

5.10.38 Time to Trigger for L1 Event

The parameter is mandatory for event triggered measurement in the case of logged MDT in NR and the event type is configured for L1 event.

The parameter defines the time during which specific criteria for the event needs to be met in order to trigger a measurement report. Detailed definition of the parameter is in TS 38.331 [43] and TS 38.413 [49].

The parameter is an is an enumerated type with the following values:

– 0 ms (0),

– 40 ms (1),

– 64 ms (2),

– 80 ms (3)

– 100 ms (4),

– 128 ms (5),

– 160 ms (6),

– 256 ms (7)

– 320 ms (8),

– 480 ms (9),

– 512 ms (10),

– 640 ms (11),

– 1024 ms (12)

– 1280 ms (13),

– 2560 ms (14),

– 5120 ms (15),

5.10.39 Event Threshold for UE Power Headroom (UPH) Measurement UMTS

The parameter is optional for event triggered measurement in the case UMTS Power Headroom Measurement (M4).

The parameter defines the threshold for initiating and stopping reporting UE Power Headroom (UPH) measurements (M4) in UMTS. If the UPH value falls below the indicated threshold, reporting is started and is periodically done until UPH value goes above this threhold. Detailed definition of the parameter is in TS 25.331 [31] and TS 25.413 [13].

The parameter is an Integer number between 0 .. 31. (for calculating the actual value see Hysteresis in TS 25.123 [59] and TS 25.133 [60].

5.10.40 Beam level measurement

This NR parameter is mandatory if the Job Type is configured for Immediate MDT or combined Immediate MDT and Trace and the bit 1 (M1) in the list of measurements parameter (defined in Section 5.10.3) for NR is set to 1.

The parameter is a Boolean type.

Detailed definition of the parameter is in clause 6.3.2, TS 38.331 [43].

NOTE: It is expected that the configurations provided by OAM are hold by gNB. However, gNB has final decision to deviate from the OAM configuration e.g. due to processing limitations.

5.10.41 Excess packet delay thresholds

This conditional mandatory parameter defines the excess packet delay thresholds to enable the calculation of the PDCP Excess Packet Delay in the uplink in case of M6 uplink measurements are requested. This parameter is mandatory if the Job Type is set to Immediate MDT and the bit 12 of list of measurements parameter (defined in Section 5.10.3) in NR (M6 for UL) is set to 1.

The parameter can have the following values:

– Excess packet delay threshold.

– 5QI value.

5.11 Void

5.12 Trace Target (M)

The Trace Target is a mandatory parameter. It specifies the target object of the Trace and MDT. It consists of the ID type and the ID value. The ID type depends on the network element to which the Trace Session is activated.

The ID type is an enumerated parameter with the following possible values:

– IMSI,

– IMEI,

– IMEISV,

– SUPI,

– Public User Identity,

– UTRAN cell,

– E-UTRAN cell,

– NG-RAN cell,

– RNC,

– eNB,

– gNB.

The ID types are mutually exclusive.