What does UL Information Transfer IRAT carry?
It carries UE-to-network inter-RAT-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 | IRAT Information Transfer |
| Full message name | 5G NR - UL Information Transfer IRAT |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Used when the UE needs to transfer inter-RAT-related information to the network. |
| Main purpose | Lets the UE send inter-RAT-related information through a dedicated RRC container when the wider procedure needs it. |
| Main specification | 3GPP TS 38.331, 6.2.2 |
| Release added | Release 16 |
| Procedures where used | Inter-RAT Information Transfer, Mobility Support |
UL Information Transfer IRAT is the UE-to-network NR RRC wrapper used to carry inter-RAT related information in the uplink direction.
Lets the UE send inter-RAT-related information through a dedicated RRC container when the wider procedure needs it.
UL Information Transfer IRAT is an uplink RRC wrapper for inter-RAT information.
Call flow position: Sent when the UE transfers inter-RAT-related information in the uplink.
Typical state: UE is in connected mode during an inter-RAT-related workflow.
Preconditions:
Next likely message: Network-side inter-RAT handling
Previous message(s): Mobility From NR Command, RRC Reconfiguration
Next message(s): Inter-RAT handling at the network
Security context: Sent as protected connected-mode signaling.
ULInformationTransferIRAT ::= SEQUENCE {
dedicatedIRAT-Message OCTET STRING
}
Engineers use the message to follow inter-RAT side information rather than standard NAS transfer.
UL-DCCH-Message
message: ulInformationTransferIRAT
dedicatedIRAT-Message: present
| IE | Required | Description |
|---|---|---|
dedicatedIRAT-Message | Yes | Carries the actual inter-RAT-related content. |
dedicatedIRAT-MessageCarries the actual inter-RAT-related content.
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 UE may not have sent the required IRAT-related information.
What to inspect: Check this message and correlate it with the surrounding mobility flow.
Next step: Compare it with the relevant command or target-system behavior.
It carries UE-to-network inter-RAT-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.