| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.8, 6.2.2 |
| Direction | UE -> eNodeB | Message Type | MBMS Control |
| Full message name | LTE RRC MBMS Counting Response r10 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | UE -> eNodeB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Triggered after MBMSCountingRequest-r10 when the UE has matching MBMS interest to report. |
| Main purpose | Returns MBMS interest feedback so the network can complete the counting branch and continue MBMS service decisions. |
| Main specification | 3GPP TS 36.331, 5.8, 6.2.2 |
| Release added | Release 10 |
| Procedures where used | MBMS counting |
Uplink LTE RRC message used by the UE to answer an MBMS counting request.
Returns MBMS interest feedback so the network can complete the counting branch and continue MBMS service decisions.
MBMS Counting Response r10 is the UE telling the network which MBMS services it is responding for in the counting branch.
Call flow position: UE feedback message returned after the MBMS counting request.
Typical state: The UE is reporting service interest into the counting branch.
Preconditions:
Next likely message: Counting aggregation and later MBMS continuation
Call flow position: UE answer used by the network to estimate service demand.
Typical state: The response contributes to counting, not to immediate service-state change by itself.
Preconditions:
Next likely message: Later MBMS handling
Previous message(s): MBMSCountingRequest-r10
Next message(s): MBMS counting aggregation, Later MBMS continuation
Security context: Sent as protected signaling when MBMS counting is active.
MBMSCountingResponse-r10 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
mbmsCountingResponse-r10 MBMSCountingResponse-r10-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read it together with the earlier request and the later MBMS demand-estimation outcome.
UL-DCCH-Message
message c1 : mbmsCountingResponse-r10 : {
criticalExtensions c1 : mbmsCountingResponse-r10 : {
countingResponseList-r10 present
}
}
| IE | Required | Description |
|---|---|---|
countingResponseList-r10 | Yes | Identifies the MBMS services the UE is responding for. |
countingResponseList-r10Identifies the MBMS services the UE is responding for.
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: Counting responses may be missing, delayed, or filtered by UE interest.
What to inspect: Check whether MBMS Counting Response r10 appears after the request and which services it references.
Next step: Treat the problem as incomplete counting feedback before assuming a later MBMS service-delivery issue.
It is the uplink LTE RRC message the UE uses to answer an MBMS counting request.
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.