What is WLAN Connection Status Report r13 in LTE?
It is the uplink LTE RRC message the UE uses to report WLAN connection status to the eNodeB.
| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6, 6.2.2 |
| Direction | UE -> eNodeB | Message Type | WLAN Status Reporting |
| Full message name | LTE RRC WLAN Connection Status Report r13 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | UE -> eNodeB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Triggered when WLAN connection status needs to be reported to the LTE network. |
| Main purpose | Lets the UE inform the eNodeB about WLAN connection state so the network can continue or adjust WLAN interworking decisions. |
| Main specification | 3GPP TS 36.331, 5.6, 6.2.2 |
| Release added | Release 13 |
| Procedures where used | WLAN interworking status reporting |
Uplink LTE RRC message used by the UE to report WLAN connection status relevant to LTE and WLAN interworking handling.
Lets the UE inform the eNodeB about WLAN connection state so the network can continue or adjust WLAN interworking decisions.
WLAN Connection Status Report r13 tells the LTE network what WLAN connection state the UE currently has.
Call flow position: UE report sent to expose WLAN connectivity state to the eNodeB.
Typical state: The network can use the report in later LTE and WLAN interworking decisions.
Preconditions:
Next likely message: Later connected-mode WLAN-aware handling
Call flow position: UE report sent when WLAN status changed and the network needs an updated view of the interworking branch.
Typical state: The message helps the eNodeB distinguish whether WLAN offload or WLAN continuity is still available.
Preconditions:
Next likely message: Network continuity or optimization continuation
Previous message(s): RRCConnectionReconfiguration
Next message(s): WLAN-aware continuation, Later connected-mode optimization
Security context: Sent as protected connected-mode signaling.
WLANConnectionStatusReport-r13 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
wlanConnectionStatusReport-r13 WLANConnectionStatusReport-r13-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read this message mainly through the WLAN status it reports and the interworking branch around it.
UL-DCCH-Message
message c1 : wlanConnectionStatusReport-r13 : {
criticalExtensions c1 : wlanConnectionStatusReport-r13 : {
wlan-Status-r13 connected
}
}
| IE | Required | Description |
|---|---|---|
wlan-Status-r13 | Yes | Carries the WLAN connection status reported by the UE. |
wlan-Status-r13Carries the WLAN connection status reported 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.
Likely cause: The network may be working from WLAN connection status that changed, was delayed, or was not reported.
What to inspect: Check whether WLAN Connection Status Report r13 appears and what status it carries.
Next step: Read it together with later continuity or optimization actions.
It is the uplink LTE RRC message the UE uses to report WLAN connection status to the eNodeB.
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.