| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 6.2.2 |
| Direction | UE -> gNB | Message Type | Sidelink Control |
| Full message name | 5G NR - Sidelink UE Information NR |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Used when the UE needs to provide sidelink-related information to the network. |
| Main purpose | Lets the UE signal sidelink-related context, needs, or status so the network can apply the right sidelink handling. |
| Main specification | 3GPP TS 38.331, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | Sidelink Control, Sidelink Coordination |
| Related timers | None highlighted |
Sidelink UE Information NR is the UE-to-network NR RRC message used to provide sidelink-related information toward the network.
Lets the UE signal sidelink-related context, needs, or status so the network can apply the right sidelink handling.
Sidelink UE Information NR lets the UE send sidelink-related information to the network.
Call flow position: Sent when the UE provides sidelink information through dedicated RRC signaling.
Typical state: UE is in connected mode with sidelink-related context.
Preconditions:
Next likely message: Network sidelink handling or reconfiguration
Previous message(s): RRC Reconfiguration, System Information Block 12 (SIB12)
Next message(s): Sidelink-related configuration or handling at the network
Security context: Sent as protected connected-mode signaling.
SidelinkUEInformationNR ::= SEQUENCE {
sidelinkInfoNR OCTET STRING
}
Engineers correlate it with sidelink configuration, pools, or positioning context depending on the scenario.
UL-DCCH-Message
message: sidelinkUEInformationNR
sidelinkInfoNR: present
| IE | Required | Description |
|---|---|---|
sidelinkInfoNR | Yes | Carries the UE's sidelink-related information toward the network. |
sidelinkInfoNRCarries the UE's sidelink-related information toward 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.
Likely cause: The UE may not have sent its sidelink information.
What to inspect: Check whether this message is present and aligned with the scenario.
Next step: Compare it with later network-side sidelink handling.
It carries UE-provided sidelink-related information toward the network.
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.