8.3.26 Iur Invoke Trace

25.4233GPPRelease 17TSUTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling

8.3.26.1 General

The purpose of the Iur Invoke Trace procedure is to inform the DRNC that it should begin a Trace Session for a given UE Context according to the Trace Parameters indicated by the SRNC. This procedure is used for Trace Parameter Propagation in the Signalling Based Activation mechanism as defined in TS 32.421 [48] and TS 32.422 [49].

This procedure shall use the signalling bearer mode specified below.

8.3.26.2 Successful Operation

Figure 26K: Iur Invoke Trace procedure, Successful Operation

The Iur Invoke Trace procedure is invoked by the SRNC by sending an IUR INVOKE TRACE message to the DRNC.

When the concerned UE is utilising one or more radio links in the DRNC the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the D-RNTI IE shall be included in the message to identify the UE Context in the DRNC.

Upon receiving the IUR INVOKE TRACE message, the DRNC should begin a Trace Recording Session according to the parameters indicated in the IUR INVOKE TRACE message.

If the List Of Interfaces To Trace IE is included in the IUR INVOKE TRACE message, the DRNC shall trace, for the concerned UE Context, the interfaces indicated by the List Of Interfaces To Trace IE. Otherwise, the DRNC shall trace, for the concerned UE Context, the Iur and Iub interfaces.

The values of the UE Identity IE, Trace Reference IE and Trace Recording Session Reference IE are used to tag the Trace Record to allow simpler construction of the total record by the entity which combines Trace Records.

If the DRNC does not support the requested value “Minimum” or “Medium” of the Trace Depth IE, the DRNC should begin a Trace Recording Session with maximum Trace Depth.

The DRNC may not start a Trace Recording Session if there are insufficient resources available within the DRNC.

If the MDT Configuration IE is included and the MDT Activation IE is set to “MDT and Trace” then the DRNC shall, if supported, initiate the requested trace function and MDT function (M3 Report, if indicated) as described in TS 32.422 [49].

If the MDT Configuration IE is included and the MDT Activation IE is set to “MDT Only” then the DRNC shall, if supported, initiate the requested MDT function (M3 Report, if indicated) as described in TS 32.422 [49] and shall ignore the List of Interfaces to Trace IE and the Trace Depth IE.

If Trace Collection Entity IP Address IE is included then the DRNC shall, if supported, store the Trace Collection Entity IP address and may use the Trace Collection Entity IP address when transferring trace records.

8.3.26.3 Abnormal Conditions

If the MDT Configuration IE is included in the IUR INVOKE TRACE message and the Trace Collection Entity IP Address IE is not included, the DRNC shall ignore the MDT Configuration.