| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.9, 6.2.2 |
| Direction | eNodeB -> UE | Message Type | Group Communication Control |
| Full message name | LTE RRC SCPTM Configuration r13 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | eNodeB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | Triggered when the network configures SC-PTM handling for the UE. |
| Main purpose | Carries single-cell point-to-multipoint configuration so the UE can receive or interpret SC-PTM service handling. |
| Main specification | 3GPP TS 36.331, 5.9, 6.2.2 |
| Release added | Release 13 |
| Procedures where used | SC-PTM configuration |
Downlink LTE RRC message used to deliver SC-PTM configuration to the UE.
Carries single-cell point-to-multipoint configuration so the UE can receive or interpret SC-PTM service handling.
SCPTM Configuration r13 is the LTE network message that configures SC-PTM handling for the UE.
Call flow position: Network message delivering single-cell point-to-multipoint configuration to the UE.
Typical state: The UE is receiving SC-PTM-related service configuration.
Preconditions:
Next likely message: Later SC-PTM continuation
Call flow position: Configuration update used when the SC-PTM branch changes.
Typical state: The message updates SC-PTM service context rather than starting a failure or recovery branch.
Preconditions:
Next likely message: Updated group-service continuation
Previous message(s): RRCConnectionReconfiguration
Next message(s): Later SC-PTM continuation
Security context: Read it as SC-PTM configuration delivery rather than a failure message.
SCPTMConfiguration-r13 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scptmConfiguration-r13 SCPTMConfiguration-r13-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
The useful read is the SC-PTM configuration branch it introduces or updates.
DL-DCCH-Message
message c1 : scptmConfiguration-r13 : {
criticalExtensions c1 : scptmConfiguration-r13 : {
scptmConfiguration-r13 present
}
}
| IE | Required | Description |
|---|---|---|
scptmConfiguration-r13 | Yes | Carries the SC-PTM configuration delivered by the network. |
scptmConfiguration-r13Carries the SC-PTM configuration delivered by the network.
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 relevant SCPTM Configuration r13 may be missing, late, or not aligned with the later branch.
What to inspect: Check whether the configuration message appears and what later SC-PTM continuation follows.
Next step: Treat it as group-service configuration analysis rather than ordinary unicast signaling troubleshooting.
It is the downlink LTE RRC message the network uses to deliver SC-PTM configuration.
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.