LTE RRC Failure Information r16

Message Fact Sheet

Protocol	lte-rrc	Network	lte
Spec	3GPP TS 36.331	Spec Section	5.6, 6.2.2
Direction	UE -> eNodeB	Message Type	Failure Reporting

Full message name	LTE RRC Failure Information r16
Protocol	LTE-RRC
Technology	LTE
Direction	UE -> eNodeB
Interface	Uu
Signaling bearer / channel	SRB1 / UL-DCCH
Typical trigger	Triggered when the UE has release 16 failure context available to report.
Main purpose	Lets the network receive newer failure-reporting payloads so it can investigate the problem and continue with later recovery or optimization decisions.
Main specification	3GPP TS 36.331, 5.6, 6.2.2
Release added	Release 16
Procedures where used	Failure information reporting

What is LTE RRC Failure Information r16 in simple terms?

Uplink LTE RRC message used by the UE to return release 16 failure information to the network.

Lets the network receive newer failure-reporting payloads so it can investigate the problem and continue with later recovery or optimization decisions.

Why this message matters

Failure Information r16 is the LTE UE report used to give the network newer release 16 failure context.

Where this message appears in the call flow

Release 16 failure information reporting

LTE flow showing Failure Information r16 sent after earlier failure handling — Failure Information r16 appears when the UE can return release 16 failure context after the earlier failure branch.

Call flow position: UE failure report sent when release 16 failure context needs to be uploaded.

Typical state: The network is collecting more detailed or newer failure evidence from the UE.

Preconditions:

The UE has release 16 failure information available.

Next likely message: Failure investigation or later reconfiguration

Failure log upload continuation

LTE flow showing Failure Information r16 as later failure evidence upload — The message is a later failure-evidence report, so the useful read is the earlier failure event it describes.

Call flow position: UE report sent after the failing branch was recovered enough to allow protected signaling again.

Typical state: The report explains an earlier failure path rather than representing the failure event itself.

Preconditions:

A relevant earlier failure occurred.

Next likely message: Investigation or optimization continuation

Call flow position

Previous message(s): Recovery or reconnect continuation

Next message(s): Failure investigation, Later connected-mode continuation

Message direction and transport

Sender and receiver: UE -> eNodeB

Interface: Uu

Domain: Access-side radio control and failure reporting

Signaling bearer: SRB1

Logical channel: UL-DCCH

Transport / encapsulation: Protected LTE RRC signaling in connected mode

Security context: Sent as protected connected-mode signaling.

Message Structure Overview

FailureInformation-r16 is the release 16 evolution of uplink LTE failure reporting.

ASN.1 for LTE RRC Failure Information r16

FailureInformation-r16 ::= SEQUENCE {
  criticalExtensions CHOICE {
    c1 CHOICE {
      failureInformation-r16 FailureInformation-r16-IEs,
      spare3 NULL,
      spare2 NULL,
      spare1 NULL
    },
    criticalExtensionsFuture SEQUENCE {}
  }
}

How to read this ASN.1

Read it as a newer uplink failure-reporting payload that extends the same general failure-evidence idea.

LTE RRC Failure Information r16 - Example Dump

UL-DCCH-Message
  message c1 : failureInformation-r16 : {
    criticalExtensions c1 : failureInformation-r16 : {
      failureInformation-r16 present
    }
  }

How to read this dump

The key is the earlier failure branch this report belongs to.

Important Information Elements

IE	Required	Description
`failureInformation-r16`	Yes	Carries the release 16 failure information payload returned by the UE.

Detailed field explanation

`failureInformation-r16`

Carries the release 16 failure information payload returned by the UE.

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.

What to check in logs and traces

Identify the earlier failure event.
Check why the report appears in this later part of the trace.
Correlate the report with the follow-up investigation or optimization branch.

Common Issues and Troubleshooting

Release 16 failure context is needed to explain a behavior gap in the trace.

Likely cause: The UE may have returned Failure Information r16 after the failing branch was recovered enough for protected signaling.

What to inspect: Check the report timing against the earlier failure and the later recovery or reconfiguration branch.

Next step: Treat it as supplementary failure evidence and compare it with the older failure-reporting path if both exist.

FAQ

What is Failure Information r16 in LTE?

It is the uplink LTE RRC message the UE uses to report release 16 failure information back to the network.

Related message pages

Related Procedures

Related Tools

Use This Reference in Practice

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.