| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6.6, 6.2.2 |
| Direction | eNodeB -> UE | Message Type | Logged MDT Control |
| Full message name | LTE RRC Logged Measurement Configuration-r10 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | eNodeB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | The network wants the UE to start logged MDT-style measurement collection for later retrieval. |
| Main purpose | Provides the UE with the logging session reference, area scope, interval, and duration used for later logged measurement storage. |
| Main specification | 3GPP TS 36.331, 5.6.6, 6.2.2 |
| Release added | Release 10 |
| Procedures where used | Logged MDT, Measurement Logging |
Downlink LTE RRC message used to configure logged measurement collection for MDT-related behavior.
Provides the UE with the logging session reference, area scope, interval, and duration used for later logged measurement storage.
Logged Measurement Configuration-r10 tells the UE how to collect and store measurements for later retrieval.
Call flow position: Configuration step that starts or refreshes the logged-measurement collection parameters.
Typical state: UE is in connected mode when the configuration is delivered.
Preconditions:
Next likely message: Later logged measurement retrieval
Call flow position: Updated configuration step when the logging area or session parameters change.
Typical state: UE is still in connected mode.
Preconditions:
Next likely message: Later UE information retrieval
Previous message(s): Connected-mode measurement control
Next message(s): UE stores logged measurements for later retrieval, UEInformationResponse-r9 in later retrieval paths
Security context: Normally sent as protected connected-mode signaling.
LoggedMeasurementConfiguration-r10 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
loggedMeasurementConfiguration-r10 LoggedMeasurementConfiguration-r10-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
LoggedMeasurementConfiguration-r10-IEs ::= SEQUENCE {
traceReference-r10 TraceReference-r10,
traceRecordingSessionRef-r10 TraceRecordingSessionRef-r10,
tce-Id-r10 TCE-Id-r10,
areaConfiguration-r10 AreaConfiguration-r10,
loggingDuration-r10 LoggingDuration-r10,
loggingInterval-r10 LoggingInterval-r10,
nonCriticalExtension SEQUENCE {} OPTIONAL
}
The main value is in the logging scope and session parameters, not in any immediate radio action.
DL-DCCH-Message
message c1 : loggedMeasurementConfiguration-r10 : {
criticalExtensions c1 : loggedMeasurementConfiguration-r10 : {
traceReference-r10 '0102030405'H,
traceRecordingSessionRef-r10 '21'H,
tce-Id-r10 1,
loggingDuration-r10 min30,
loggingInterval-r10 ms120
}
}
| IE | Required | Description |
|---|---|---|
traceReference-r10 | Yes | Identifies the trace and logging context used by the network. |
traceRecordingSessionRef-r10 | Yes | Session reference for the logged measurement collection instance. |
loggingInterval-r10 | Yes | Tells the UE how often measurements should be logged. |
loggingDuration-r10 | Yes | Defines how long the logging session should continue. |
areaConfiguration-r10 | Yes | Defines the area scope where logging applies. |
traceReference-r10Identifies the trace and logging context used by the network.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
traceRecordingSessionRef-r10Session reference for the logged measurement collection instance.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
loggingInterval-r10Tells the UE how often measurements should be logged.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
loggingDuration-r10Defines how long the logging session should continue.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
areaConfiguration-r10Defines the area scope where logging applies.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Likely cause: The logging scope, duration, or collection window may not match the later retrieval expectation.
What to inspect: Check the logging interval, duration, and the configured area against the later retrieval attempt.
Next step: Compare the configuration against a known-good MDT logging case.
It is the LTE RRC message used to configure logged MDT-style measurement collection at the UE.
No. It configures later logged collection and later retrieval rather than an immediate live report.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.