| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.8, 6.2.2 |
| Direction | eNodeB -> UE | Message Type | MBMS Control |
| Full message name | LTE RRC MBMS Counting Request r10 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | eNodeB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | Triggered when the network wants counting feedback from UEs interested in a given MBMS service. |
| Main purpose | Starts the MBMS counting branch so the network can estimate interested UE population before continuing MBMS-related handling. |
| Main specification | 3GPP TS 36.331, 5.8, 6.2.2 |
| Release added | Release 10 |
| Procedures where used | MBMS counting |
Downlink LTE RRC message used by the network to request MBMS counting responses from interested UEs.
Starts the MBMS counting branch so the network can estimate interested UE population before continuing MBMS-related handling.
MBMS Counting Request r10 is the LTE network asking interested UEs to identify themselves for MBMS counting.
Call flow position: Network request sent to solicit MBMS counting feedback from UEs.
Typical state: The network is measuring MBMS interest before deciding later service handling.
Preconditions:
Next likely message: MBMSCountingResponse-r10 from interested UEs
Call flow position: Control message used before the network decides how to continue MBMS service delivery.
Typical state: The request itself does not change service state; it gathers demand information.
Preconditions:
Next likely message: Counting response aggregation and later MBMS continuation
Previous message(s): SystemInformationBlockType13
Next message(s): MBMSCountingResponse-r10
Security context: Sent as protected signaling when MBMS counting control is active.
MBMSCountingRequest-r10 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
mbmsCountingRequest-r10 MBMSCountingRequest-r10-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read it as a demand-estimation control message for MBMS services.
DL-DCCH-Message
message c1 : mbmsCountingRequest-r10 : {
criticalExtensions c1 : mbmsCountingRequest-r10 : {
countingRequestList-r10 present
}
}
| IE | Required | Description |
|---|---|---|
countingRequestList-r10 | Yes | Identifies the MBMS services or counting items being requested. |
countingRequestList-r10Identifies the MBMS services or counting items being requested.
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 request or the response branch may be missing.
What to inspect: Check whether MBMS Counting Request r10 appears and whether counting responses follow.
Next step: Read it as an MBMS demand-estimation branch rather than a service-delivery command.
It is the downlink LTE RRC message the network uses to request MBMS counting feedback from interested UEs.
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.