What does UL Information Transfer MRDC do?
It carries UE-to-network MR-DC-related information inside a dedicated RRC wrapper.
| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 6.2.2 |
| Direction | UE -> gNB | Message Type | MR-DC Information Transfer |
| Full message name | 5G NR - UL Information Transfer MRDC |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / SRB3 / UL-DCCH |
| Typical trigger | Used when the UE needs to send MR-DC-related information to the network. |
| Main purpose | Lets the UE deliver MR-DC-related information back to the network through a dedicated RRC container. |
| Main specification | 3GPP TS 38.331, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | MR-DC Coordination, Dual Connectivity Context Handling |
UL Information Transfer MRDC is the UE-to-network NR RRC wrapper used to carry MR-DC-related information in the uplink direction.
Lets the UE deliver MR-DC-related information back to the network through a dedicated RRC container.
UL Information Transfer MRDC is an uplink RRC wrapper for MR-DC information.
Call flow position: Sent when the UE transfers MR-DC-related information upward.
Typical state: UE is in connected mode with dual-connectivity context.
Preconditions:
Next likely message: Network-side MR-DC handling or reconfiguration
Previous message(s): 5g-dl-information-transfer-mrdc, RRC Reconfiguration
Next message(s): Network-side MR-DC handling
Security context: Sent as protected connected-mode signaling.
ULInformationTransferMRDC ::= SEQUENCE {
dedicatedMRDC-Message OCTET STRING
}
Engineers usually inspect this message together with the downlink MRDC transfer and later SCG or dual-connectivity behavior.
UL-DCCH-Message
message: ulInformationTransferMRDC
dedicatedMRDC-Message: present
| IE | Required | Description |
|---|---|---|
dedicatedMRDC-Message | Yes | Carries the actual MR-DC-related content in the uplink wrapper. |
dedicatedMRDC-MessageCarries the actual MR-DC-related content in the uplink wrapper.
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 MRDC transfer may be absent or malformed.
What to inspect: Check the dedicated MRDC payload and the later response.
Next step: Correlate it with dual-connectivity state and SCG behavior.
It carries UE-to-network MR-DC-related information inside a dedicated RRC wrapper.
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.