| 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 / BR |
| Full message name | LTE RRC SCPTM Configuration BR r14 |
|---|---|
| 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 a BR-oriented branch. |
| Main purpose | Carries SC-PTM configuration adapted for BR-oriented operation so the UE can continue the relevant group-service branch. |
| Main specification | 3GPP TS 36.331, 5.9, 6.2.2 |
| Release added | Release 14 |
| Procedures where used | SC-PTM BR configuration |
Downlink LTE RRC message used to deliver SC-PTM configuration for bandwidth-reduced UE contexts.
Carries SC-PTM configuration adapted for BR-oriented operation so the UE can continue the relevant group-service branch.
SCPTM Configuration BR r14 is the LTE message the network uses to configure BR-specific SC-PTM handling.
Call flow position: Network message delivering BR-adapted SC-PTM configuration.
Typical state: The UE is receiving SC-PTM configuration tailored to a BR-oriented operating branch.
Preconditions:
Next likely message: Later BR-specific SC-PTM continuation
Call flow position: Configuration update used when the BR-specific SC-PTM branch changes.
Typical state: The message updates BR-specific group-service context rather than starting a failure branch.
Preconditions:
Next likely message: Updated BR group-service continuation
Previous message(s): SystemInformation-BR-r13, RRCConnectionReconfiguration
Next message(s): Later BR-specific SC-PTM continuation
Security context: Read it as BR-specific SC-PTM configuration delivery.
SCPTMConfiguration-BR-r14 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
scptmConfiguration-BR-r14 SCPTMConfiguration-BR-r14-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read it together with the BR-oriented system-information and service branch.
DL-DCCH-Message
message c1 : scptmConfiguration-BR-r14 : {
criticalExtensions c1 : scptmConfiguration-BR-r14 : {
scptmConfiguration-BR-r14 present
}
}
| IE | Required | Description |
|---|---|---|
scptmConfiguration-BR-r14 | Yes | Carries the BR-specific SC-PTM configuration. |
scptmConfiguration-BR-r14Carries the BR-specific SC-PTM configuration.
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 BR-specific SC-PTM configuration may be missing, delayed, or inconsistent with the surrounding branch.
What to inspect: Check whether SCPTM Configuration BR r14 appears and what later branch follows.
Next step: Read it together with BR-specific system information and group-service continuation.
It is the downlink LTE RRC message the network uses to deliver BR-specific 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.