| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6, 6.2.2 |
| Direction | UE -> eNodeB | Message Type | Dedicated Transfer / MR-DC |
| Full message name | LTE RRC UL Information Transfer MRDC r15 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | UE -> eNodeB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Triggered when the UE needs to deliver dedicated information in an MR-DC branch. |
| Main purpose | Carries UE-originated dedicated information upward during MR-DC operation so the network can forward or process the payload. |
| Main specification | 3GPP TS 36.331, 5.6, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | MR-DC dedicated information transfer |
Uplink LTE RRC message used to transfer dedicated information in MR-DC related contexts.
Carries UE-originated dedicated information upward during MR-DC operation so the network can forward or process the payload.
UL Information Transfer MRDC r15 is the LTE UE message that carries dedicated MR-DC-related information to the network.
Call flow position: UE message carrying dedicated information during an MR-DC branch.
Typical state: The message transports a payload rather than commanding a mobility or failure action.
Preconditions:
Next likely message: Later network-side handling
Call flow position: Uplink transfer step used when the UE must send information associated with MR-DC handling.
Typical state: The message is best read as a transport wrapper for the payload it carries.
Preconditions:
Next likely message: Forwarding, processing, or later reconfiguration
Previous message(s): RRCConnectionReconfiguration
Next message(s): Network-side dedicated-information handling
Security context: Sent as protected connected-mode signaling.
ULInformationTransferMRDC-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
ulInformationTransferMRDC-r15 ULInformationTransferMRDC-r15-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
The practical meaning depends on the dedicated information container being transported.
UL-DCCH-Message
message c1 : ulInformationTransferMRDC-r15 : {
criticalExtensions c1 : ulInformationTransferMRDC-r15 : {
dedicatedInfoType-r15 present
}
}
| IE | Required | Description |
|---|---|---|
dedicatedInfoType-r15 | Yes | Carries the MR-DC-related dedicated payload type. |
dedicatedInfoType-r15Carries the MR-DC-related dedicated payload type.
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 uplink information transfer may be missing, delayed, or carrying unexpected payload context.
What to inspect: Check whether UL Information Transfer MRDC r15 appears and what dedicated container it carries.
Next step: Treat the issue as payload transport or interpretation before assuming a control-plane failure.
It is the uplink LTE RRC message the UE uses to transfer dedicated information in MR-DC related contexts.
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.