| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 6.2.2 |
| Direction | UE -> gNB | Message Type | Failure Reporting |
| Full message name | 5G NR - SCG Failure Information EUTRA |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / SRB3 / UL-DCCH |
| Typical trigger | Used when the UE detects SCG failure in an E-UTRA secondary context. |
| Main purpose | Lets the UE report failure that affects an E-UTRA SCG when dual connectivity spans NR and LTE contexts. |
| Main specification | 3GPP TS 38.331, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | E-UTRA SCG Failure Reporting, EN-DC Recovery |
SCG Failure Information EUTRA is the NR RRC message used to report failure in an E-UTRA secondary cell group context.
Lets the UE report failure that affects an E-UTRA SCG when dual connectivity spans NR and LTE contexts.
This message reports failure in an LTE/E-UTRA secondary cell group.
Call flow position: Sent when the UE reports a failure in an E-UTRA secondary cell group.
Typical state: UE is in dual-connectivity operation with an E-UTRA SCG.
Preconditions:
Next likely message: Recovery or reconfiguration
Previous message(s): RRC Reconfiguration
Next message(s): Recovery handling, Reconfiguration, Release
Security context: Sent as protected connected-mode signaling.
SCGFailureInformationEUTRA ::= SEQUENCE {
failureInfoEUTRA OCTET STRING
}
Engineers use it when the secondary context is LTE/E-UTRA rather than pure NR.
UL-DCCH-Message
message: scgFailureInformationEUTRA
failureInfoEUTRA: present
| IE | Required | Description |
|---|---|---|
failureInfoEUTRA | Yes | Carries failure information specific to the E-UTRA SCG context. |
failureInfoEUTRACarries failure information specific to the E-UTRA SCG context.
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 detected E-UTRA SCG failure and reported it.
What to inspect: Check this message and the later EN-DC recovery path.
Next step: Correlate with LTE-side SCG behavior rather than NR-only assumptions.
It is used when the failing secondary cell group is E-UTRA rather than NR.
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.