LTE RRC Connection Resume Complete-r13

Message Fact Sheet

Protocol	lte-rrc	Network	lte
Spec	3GPP TS 36.331	Spec Section	5.3.12, 6.2.2, Annex B
Direction	UE -> eNodeB	Message Type	Suspend / Resume Control

Full message name	LTE RRC Connection Resume Complete-r13
Protocol	LTE-RRC
Technology	LTE
Direction	UE -> eNodeB
Interface	Uu
Signaling bearer / channel	SRB1 / UL-DCCH
Typical trigger	The UE successfully applies RRCConnectionResume-r13 and is ready to confirm that the resumed context is usable.
Main purpose	Confirms completion of the LTE suspend and resume path so the resumed connected context can continue with later dedicated signaling.
Main specification	3GPP TS 36.331, 5.3.12, 6.2.2, Annex B
Release added	Release 13
Procedures where used	LTE Suspend and Resume, Resume Return from Suspended Context

What is LTE RRC Connection Resume Complete-r13 in simple terms?

Uplink LTE RRC message sent by the UE to confirm that the resume branch completed successfully and the suspended context was restored.

Confirms completion of the LTE suspend and resume path so the resumed connected context can continue with later dedicated signaling.

Why this message matters

RRCConnectionResumeComplete-r13 is the UE confirming that the LTE resume branch finished successfully.

Where this message appears in the call flow

LTE suspend and resume

Call flow position: UE completion step sent after the network accepted resume and the stored context was applied successfully.

Typical state: UE is in the resume success branch and is confirming the restored context.

Preconditions:

RRCConnectionResume-r13 was received.
The UE could apply the resumed configuration successfully.

Next likely message: Later resumed connected-mode LTE signaling

Paging-driven resume return

LTE paging-driven resume flow showing acceptance and RRCConnectionResumeComplete-r13 — When paging return resumes a stored context successfully, the completion message confirms that the resumed branch finished cleanly.

Call flow position: Completion step used when paging or service return led into the resume branch and the stored context resumed successfully.

Typical state: UE is continuing from a resumed context rather than a fresh new setup.

Preconditions:

The network chose resume instead of fresh setup.
The resumed context is still usable.

Next likely message: Later resumed connected-mode continuation

Call flow position

Previous message(s): RRCConnectionResume-r13

Next message(s): Later resumed connected-mode LTE signaling, Recovered user-plane and control-plane continuation

Message direction and transport

Sender and receiver: UE -> eNodeB

Interface: Uu

Domain: Access-side radio control suspend and resume handling

Signaling bearer: SRB1

Logical channel: UL-DCCH

Transport / encapsulation: RRC over DCCH on the resumed dedicated signaling path after the network accepted resume

Security context: Sent after the resume-accept step on the restored dedicated signaling path.

Message Structure Overview

RRCConnectionResumeComplete-r13 is a compact confirmation message in the LTE resume success branch.
Its practical value is procedural: it confirms that the stored context resumed formally.
If this message is missing, the network should not assume the resume branch finished successfully.

ASN.1 for LTE RRC Connection Resume Complete-r13

RRCConnectionResumeComplete-r13 ::= SEQUENCE {
  rrc-TransactionIdentifier RRC-TransactionIdentifier,
  criticalExtensions CHOICE {
    c1 CHOICE {
      rrcConnectionResumeComplete-r13 RRCConnectionResumeComplete-r13-IEs,
      spare3 NULL,
      spare2 NULL,
      spare1 NULL
    },
    criticalExtensionsFuture SEQUENCE {}
  }
}

RRCConnectionResumeComplete-r13-IEs ::= SEQUENCE {
  nonCriticalExtension RRCConnectionResumeComplete-v1430-IEs OPTIONAL
}

How to read this ASN.1

The message is structurally simple. The useful checks are transaction pairing and whether later resumed behavior matches a successful resume path.

LTE RRC Connection Resume Complete-r13 - Example Dump

UL-DCCH-Message
  message c1 : rrcConnectionResumeComplete-r13 : {
    rrc-TransactionIdentifier 1,
    criticalExtensions c1 : rrcConnectionResumeComplete-r13 : {
    }
  }

How to read this dump

Check that the transaction identifier matches the earlier RRCConnectionResume-r13.
The main significance is that the UE finished the resume branch successfully.
If later behavior still fails, use this message as the checkpoint proving that resume at least completed formally.

Important Information Elements

IE	Required	Description
`rrc-TransactionIdentifier`	Yes	Transaction identifier matching the preceding RRCConnectionResume-r13.
`criticalExtensions`	Yes	Versioned wrapper for the completion message.
`nonCriticalExtension`	Optional	Release-extension branch for later additions.

Detailed field explanation

`rrc-TransactionIdentifier`

Transaction identifier matching the preceding RRCConnectionResume-r13.

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.

`criticalExtensions`

Versioned wrapper for the completion message.

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.

`nonCriticalExtension`

Release-extension branch for later additions.

Presence: Optional

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

Confirm the message follows RRCConnectionResume-r13.
Verify the transaction identifier matches the earlier acceptance message.
Check whether later resumed behavior looks stable.
Correlate the message with the earlier paging or suspend context.
If the message is missing, do not assume resume finished.

Common Issues and Troubleshooting

RRCConnectionResume-r13 is present but the complete message never appears.

Likely cause: The UE may have failed to apply the resumed configuration or the branch may have broken again before completion.

What to inspect: Check the resume-accept content, the resumed radio behavior, and whether the UE had a chance to send the completion.

Next step: Use the missing completion as the strongest sign that resume did not finish cleanly.

The complete message is present but later behavior still falls back to fresh setup.

Likely cause: Resume may have completed formally, but the stored context may still have been unstable or abandoned later.

What to inspect: Compare the resumed behavior with the earlier paging or suspend context and the later signaling path.

Next step: Continue into the resumed path and locate where fallback actually begins.

Paging-driven return seems to resume successfully, but service still fails.

Likely cause: The radio control branch may have resumed, while later service continuation still failed for other reasons.

What to inspect: Treat the completion message as proof of resume success, then move forward into later signaling and service behavior.

Next step: Do not re-debug the request stage if completion is already present.

LTE / 5G / Variant Comparison

Compared with RRCConnectionResume-r13

RRCConnectionResume-r13 is the network acceptance of the resume branch. RRCConnectionResumeComplete-r13 is the UE confirmation that the accepted resume finished.

Compared with RRCConnectionSetupComplete

Both are UE completion messages, but one confirms fresh setup and the other confirms resumption of a stored suspended context.

FAQ

What is RRCConnectionResumeComplete-r13 in LTE?

It is the uplink LTE RRC message the UE sends to confirm that the resume branch completed successfully.

What should I inspect first in RRCConnectionResumeComplete-r13?

Start with the transaction identifier, the earlier RRCConnectionResume-r13 message, and whether later resumed behavior is stable.

What does it mean if RRCConnectionResumeComplete-r13 is missing?

It is a strong clue that the resume branch did not finish cleanly.

Does this message guarantee that later service will work?

No. It confirms formal resume completion, but later service or signaling can still fail for other reasons.

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.