| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6.22, 6.2.2 |
| Direction | UE -> eNodeB | Message Type | Segmented Dedicated Control |
| Full message name | LTE RRC UL Dedicated Message Segment-r16 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | UE -> eNodeB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / SRB2 / UL-DCCH |
| Typical trigger | An uplink dedicated LTE RRC payload is too large for a single message unit and must be segmented. |
| Main purpose | Lets the UE deliver a large protected dedicated RRC payload over multiple uplink segments for later reassembly at the network. |
| Main specification | 3GPP TS 36.331, 5.6.22, 6.2.2 |
| Release added | Release 16 |
| Procedures where used | UL Message Segment Transfer, Segmented Dedicated RRC Delivery |
Uplink LTE RRC segmentation container used when a UE dedicated LTE RRC message is sent in multiple fragments.
Lets the UE deliver a large protected dedicated RRC payload over multiple uplink segments for later reassembly at the network.
UL Dedicated Message Segment-r16 is the LTE wrapper the UE uses when a large dedicated uplink RRC message must be split into pieces.
Call flow position: Fragment container used during uplink delivery of a large dedicated LTE RRC payload.
Typical state: UE is in connected mode.
Preconditions:
Next likely message: Further UL segments or network-side reassembly
Call flow position: Segmentation branch used when a large UE-originated payload cannot fit in one message unit.
Typical state: UE remains in connected mode.
Preconditions:
Next likely message: Final reassembly and later network handling
Previous message(s): Large uplink dedicated LTE RRC payload becomes segmented
Next message(s): Further UL segments, Network-side reassembly
Security context: Sent as protected connected-mode signaling.
ULDedicatedMessageSegment-r16 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
ULDedicatedMessageSegment-r16-IEs ::= SEQUENCE {
segmentNumber-r16 INTEGER,
rrc-MessageSegmentContainer-r16 OCTET STRING
}
The outer structure is simple. The practical issue is whether the network received the full sequence of segments.
UL-DCCH-Message
message c1 : ulDedicatedMessageSegment-r16 : {
criticalExtensions c1 : ulDedicatedMessageSegment-r16 : {
segmentNumber-r16 2,
rrc-MessageSegmentContainer-r16 '7C4409'H
}
}
| IE | Required | Description |
|---|---|---|
segmentNumber-r16 | Yes | Identifies the uplink segment sequence. |
rrc-MessageSegmentContainer-r16 | Yes | Carries the fragment of the uplink dedicated RRC payload. |
segmentNumber-r16Identifies the uplink segment sequence.
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.
rrc-MessageSegmentContainer-r16Carries the fragment of the uplink dedicated RRC payload.
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: One or more uplink segments may be missing or not reassembled correctly.
What to inspect: Check segment continuity and the absence of the expected later network handling.
Next step: Treat the issue as segmented uplink delivery failure rather than a generic RRC decode issue.
It is the LTE RRC uplink segment container used when a large dedicated message is sent in multiple pieces.
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.