6 MDT Reporting
32.4223GPPRelease 17Subscriber and equipment traceTelecommunication managementTrace control and configuration managementTS
6.1 MDT reporting in case of Immediate MDT for UTRAN and E-UTRAN
Figure 6.1 illustrates an example of the procedure for Immediate MDT reporting for UTRAN and E-UTRAN.
Figure 6.1: Procedure for Immediate MDT reporting
In case of Immediate MDT, the MDT related measurements are sent in RRC as part of the existing RRC measurements. Whenever the eNB/RNC receives the MDT measurements it shall save it to a Trace Record. The Trace Records are sent to the TCE either directly or via EM (where EM can reside in the eNB/RNC).
The time and the criteria when the Trace Records are sent to the TCE is vendor specific however if the Trace Session is deactivated, the Trace Records shall be sent to the TCE latest by 2 hours after the Trace Session deactivation.
Editor’s note: The exact time is FFS.
For reporting of MDT data in single operator and participating operator cases, see clause 7.
6.2 MDT reporting in case of Logged MDT for UTRAN and E-UTRAN
Figure 6.2 illustrates an example of the MDT reporting in case of Logged MDT for UTRAN and E-UTRAN:
Figure 6.2: MDT reporting in case of Logged MDT
In case of Logged MDT, the UE collects the measurements while it is in IDLE or INACTIVE mode. Once the UE goes to RRC CONNECTED mode, the UE indicates MDT log availability in the RRCConnectionSetupComplete message or RRCResumeComplete message (E-UTRAN only) to the eNB/RNC. When the eNB/RNC receives this indication it can request the MDT log (if the UE is still in the same RAT type where the MDT configuration was done) by sending the UEInformationRequest message to the UE. The MDT logs are sent to the network in the UEInformationResponse message. At the reception of the UEInformationResponse message the eNB/RNC shall save the received MDT log to the Trace Record. The Trace Records are sent to the TCE either directly or via EM (where EM can reside in the eNB/RNC).
The time and criteria when the Trace Records are sent to the TCE is vendor specific however if the Trace Session is deactivated, the Trace Records shall be sent to the TCE latest by 2 hours after the Trace Session deactivation.
Editor’s note: The exact time is FFS.
6.3 MDT reporting in case of Logged MBSFN MDT
In case of Logged MBSFN MDT, a UE configured to perform Logged MDT MBSFN measurements indicates the availability of Logged MDT MBSFN measurements, by means of an indicator, in RRCConnectionSetupComplete message during connection establishment. The indicator shall be provided within E-UTRAN also at handover and re-establishment, except when the logged measurement configuration is active in CONNECTED mode.
When the eNB receives this indication it can request the MDT log (if the UE is still in the same RAT type where the MDT configuration was done) by sending the UEInformationRequest message to the UE. The MDT logs are sent to the network in the UEInformationResponse message. At the reception of the UEInformationResponse message the eNB shall saves the received MDT log to the Trace Record. The Trace Records are sent to the TCE either directly or via EM (where EM can reside in the eNB).
Figure 6.3 illustrates an example of the MDT reporting in case of Logged MBSFN MDT (applicable only for E-UTRAN):
Figure 6.3: Procedure for Logged MBSFN MDT reporting
The time and criteria when the Trace Records are sent to the TCE is vendor specific however if the Trace Session is deactivated, the Trace Records shall be sent to the TCE latest by 2 hours ( the exact time is FFS) after the Trace Session deactivation.
6.4 MDT reporting in case of Immediate MDT for NG-RAN
Figure 6.4.1 illustrates an example of MDT reporting in the case of Immediate MDT for NG-RAN:
Figure 6.4.1: Immediate MDT reporting in the case of non split architecture
In case of Immediate MDT, the MDT related measurements are sent in RRC as part of the existing RRC measurements. Whenever the gNB receives the MDT measurements it shall save it to a Trace Record. The Trace Records are sent to the TCE either directly or via Management System.
In a split architecture, the MDT Trace Records shall be sent directly from each node where the MDT session has been activated to TCE or management system. If the management system receives the MDT Trace Records, the management system should send the MDT Trace Records to TCE [44].
The time and the criteria when the Trace Records are sent to the TCE is vendor specific however if the Trace Session is deactivated, the Trace Records shall be sent to the TCE latest by 2 hours after the Trace Session deactivation.
Editor’s note: The exact time is FFS.
6.5 MDT reporting in case of Logged MDT for NG-RAN
Figure 6.5.1 illustrates an example of the MDT reporting in case of Logged MDT for NG-RAN:
Figure 6.5.1: Logged MDT reporting in the case of non split architecture
In case of Logged MDT, the UE collects the measurements while it is in IDLE mode or INACTIVE state. Once the UE goes to RRC CONNECTED mode, the UE indicates MDT log availability in the RRCSetupComplete message or RRCResumeComplete message to the gNB. When the gNB receives this indication, it can request the MDT log (if the UE is still in the same RAT type where the MDT configuration was done) by sending the UEInformationRequest message to the UE. The MDT logs are sent to the network in the UEInformationResponse message. At the reception of the UEInformationResponse message the gNB shall save the received MDT log to the Trace Record. The Trace Records are sent to the TCE either directly or via Management System.
In a split architecture, the MDT Trace Records shall be sent directly from each node where the MDT session has been activated to TCE or management system. If the management system receives the MDT Trace Records, the management system should send the MDT Trace Records to TCE [44].
The time and criteria when the Trace Records are sent to the TCE is vendor specific however if the Trace Session is deactivated.