What is MeasReportAppLayer r15 in LTE?
It is the uplink LTE RRC message the UE uses to report configured application-layer measurement results.
| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6, 6.2.2 |
| Direction | UE -> eNodeB | Message Type | Application-Layer Measurement |
| Full message name | LTE RRC MeasReportAppLayer r15 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | UE -> eNodeB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Triggered when configured application-layer measurement conditions produce a reportable result. |
| Main purpose | Carries app-layer measurement results so the eNodeB can evaluate service-aware measurement behavior and continue application-related optimization handling. |
| Main specification | 3GPP TS 36.331, 5.6, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | Application-layer measurement reporting |
Uplink LTE RRC message used by the UE to report configured application-layer measurement results to the network.
Carries app-layer measurement results so the eNodeB can evaluate service-aware measurement behavior and continue application-related optimization handling.
MeasReportAppLayer r15 is the LTE UE report for configured application-layer measurements.
Call flow position: UE report sent after configured app-layer measurement conditions are met.
Typical state: The report gives the network service-aware measurement context rather than only radio-layer measurements.
Preconditions:
Next likely message: Later optimization or measurement continuation
Call flow position: UE report used by the network before it decides whether any service-aware optimization action is needed.
Typical state: The message extends measurement handling into the application-layer domain.
Preconditions:
Next likely message: Connected-mode continuation or later reconfiguration
Previous message(s): RRCConnectionReconfiguration
Next message(s): Application-layer measurement continuation, Later optimization handling
Security context: Sent as protected connected-mode signaling.
MeasReportAppLayer-r15 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
measReportAppLayer-r15 MeasReportAppLayer-r15-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read it as the app-layer counterpart of a normal radio measurement report.
UL-DCCH-Message
message c1 : measReportAppLayer-r15 : {
criticalExtensions c1 : measReportAppLayer-r15 : {
measResultAppLayer-r15 present
}
}
| IE | Required | Description |
|---|---|---|
measResultAppLayer-r15 | Yes | Carries the application-layer measurement results reported by the UE. |
measResultAppLayer-r15Carries the application-layer measurement results 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 UE may not have produced the expected app-layer report, or the network may not have acted on it.
What to inspect: Check whether MeasReportAppLayer r15 appears and what later branch follows.
Next step: Compare it with the earlier app-layer configuration and any later reconfiguration.
It is the uplink LTE RRC message the UE uses to report configured application-layer measurement results.
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.