| Protocol | lte-rrc | Network | lte |
|---|---|---|---|
| Spec | 3GPP TS 36.331 | Spec Section | 5.6, 6.2.2 |
| Direction | eNodeB -> UE | Message Type | Coverage Enhancement / PUR |
| Full message name | LTE RRC PUR Configuration Request r16 |
|---|---|
| Protocol | LTE-RRC |
| Technology | LTE |
| Direction | eNodeB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | Triggered when the network needs to configure PUR-related behavior. |
| Main purpose | Starts the PUR-related configuration branch so the UE can apply or react to the requested periodic uplink resource handling. |
| Main specification | 3GPP TS 36.331, 5.6, 6.2.2 |
| Release added | Release 16 |
| Procedures where used | PUR configuration |
Downlink LTE RRC message used to request or deliver PUR-related configuration handling.
Starts the PUR-related configuration branch so the UE can apply or react to the requested periodic uplink resource handling.
PUR Configuration Request r16 is the LTE network message used to configure a PUR-related branch.
Call flow position: Network message used to configure a PUR-related branch.
Typical state: The UE is receiving periodic uplink resource related handling instructions.
Preconditions:
Next likely message: Later PUR continuation
Call flow position: Configuration update used when the PUR-related branch changes.
Typical state: The message updates PUR handling instead of acting as a mobility or failure command.
Preconditions:
Next likely message: Updated PUR continuation
Previous message(s): RRCConnectionReconfiguration
Next message(s): Later PUR-related continuation
Security context: Sent as protected connected-mode signaling.
PURConfigurationRequest-r16 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
purConfigurationRequest-r16 PURConfigurationRequest-r16-IEs,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
criticalExtensionsFuture SEQUENCE {}
}
}
Read it as configuration delivery for PUR-related LTE handling.
DL-DCCH-Message
message c1 : purConfigurationRequest-r16 : {
criticalExtensions c1 : purConfigurationRequest-r16 : {
pur-ConfigRequest-r16 present
}
}
| IE | Required | Description |
|---|---|---|
pur-ConfigRequest-r16 | Yes | Carries the PUR-related configuration request content. |
pur-ConfigRequest-r16Carries the PUR-related configuration request content.
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 PUR configuration request may be missing, delayed, or not matched by later behavior.
What to inspect: Check whether PUR Configuration Request r16 appears and what later branch follows.
Next step: Treat it as PUR-related configuration analysis rather than generic mobility troubleshooting.
It is the downlink LTE RRC message the network uses to configure a PUR-related branch.
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.