Content for TS 25.331 Word version: 16.1.0
8.2 Radio Bearer control procedures
8.2.1 Radio bearer establishment
8.2.2 Reconfiguration procedures
8.2.3 Radio bearer release
8.2.4 Transport channel reconfiguration
8.2.5 Transport format combination control
8.2.6 Physical channel reconfiguration
8.2.7 Physical Shared Channel Allocation [TDD only]
8.2.8 PUSCH capacity request [TDD only]
8.2.10 Uplink Physical Channel Control [TDD only]
8.2.11 Physical channel reconfiguration failure
...
...
8.2 Radio Bearer control procedures Word‑p. 178
8.2.1 Radio bearer establishment
8.2.2 Reconfiguration procedures
8.2.2.1 General Word‑p. 180
8.2.2.2 Initiation
8.2.2.2a Initiation of handover from GERAN Iu mode |R5| Word‑p. 182
8.2.2.3 Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE or TRANSPORT CHANNEL RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message, TTI switch HS-SCCH order or Target cell HS-SCCH order by the UE Word‑p. 183
8.2.2.3a Reception of RADIO BEARER RECONFIGURATION message by the UE performing handover from GERAN Iu mode |R5| Word‑p. 203
8.2.2.4 Transmission of a response message by the UE, normal case Word‑p. 204
8.2.2.5 Reception of a response message by the UTRAN, normal case Word‑p. 207
8.2.2.5a Rejection by the UE |R6| Word‑p. 208
8.2.2.6 Unsupported configuration in the UE
8.2.2.7 Physical channel failure Word‑p. 209
8.2.2.8 Cell re-selection Word‑p. 210
8.2.2.9 Transmission of a response message by the UE, failure case
8.2.2.10 Reception of a response message by the UTRAN, failure case Word‑p. 211
8.2.2.11 Invalid configuration
8.2.2.12 Incompatible simultaneous reconfiguration
8.2.2.12a Incompatible simultaneous security reconfiguration Word‑p. 212
8.2.2.12b Cell update procedure during security reconfiguration
8.2.2.13 Invalid received message Word‑p. 213
8.2.2.14 Radio link failure
8.2.3 Radio bearer release Word‑p. 214
8.2.4 Transport channel reconfiguration
8.2.5 Transport format combination control
8.2.5.1 General Word‑p. 215
8.2.5.2 Initiation
8.2.5.3 Reception of a TRANSPORT FORMAT COMBINATION CONTROL message by the UE
8.2.5.4 Invalid configuration Word‑p. 217
8.2.5.5 Invalid TRANSPORT FORMAT COMBINATION CONTROL message Word‑p. 218
8.2.6 Physical channel reconfiguration
8.2.7 Physical Shared Channel Allocation [TDD only]
8.2.7.1 General
8.2.7.2 Initiation Word‑p. 219
8.2.7.3 Reception of a PHYSICAL SHARED CHANNEL ALLOCATION message by the UE
8.2.7.4 Invalid PHYSICAL SHARED CHANNEL ALLOCATION message Word‑p. 221
8.2.8 PUSCH capacity request [TDD only]
8.2.8.1 General
8.2.8.2 Initiation Word‑p. 222
8.2.8.3 PUSCH CAPACITY REQUEST message contents to set
8.2.8.4 Reception of a PUSCH CAPACITY REQUEST message by the UTRAN Word‑p. 223
8.2.8.5 T310 expiry
8.2.9 Void
8.2.10 Uplink Physical Channel Control [TDD only] Word‑p. 224
8.2.10.1 General
8.2.10.2 Initiation
8.2.10.3 Reception of UPLINK PHYSICAL CHANNEL CONTROL message by the UE
8.2.10.4 Invalid UPLINK PHYSICAL CHANNEL CONTROL message
8.2.11 Physical channel reconfiguration failure Word‑p. 225
