RRC 6n0

3GPP TS 25.331 V6.23.
0 (2009-09)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 6)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
Keywords
UMTS, radio
3GPP Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2009, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
Contents
Foreword........................................................................................................................................................... 29 1 2 3
3.1 3.2
Scope ...................................................................................................................................................... 30 References .............................................................................................................................................. 30 Definitions and abbreviations................................................................................................................. 32

Definitions ....................................................................................................................................................... 32 Abbreviations ................................................................................................................................................... 33
4
4.1 4.2 4.3
General ................................................................................................................................................... 35
Overview of the specification .......................................................................................................................... 35 RRC Layer Model............................................................................................................................................ 36 Protocol specification principles ...................................................................................................................... 39
5
5.1 5.2 5.3
RRC Functions and Services provided to upper layers .......................................................................... 39

RRC Functions................................................................................................................................................. 39 RRC Services provided to upper layers ........................................................................................................... 40 Primitives between RRC and upper layers ...................................................................................................... 40
6
6.1 6.2 6.3
Services expected from lower layers ...................................................................................................... 40

Services expected from Layer 2 ....................................................................................................................... 40 Services expected from Layer 1 ....................................................................................................................... 40 Signalling Radio Bearers ................................................................................................................................. 40
7
7.1 7.2 7.2.1 7.2.2 7.2.2.1 7.2.2.2 7.2.2.3
Protocol states ........................................................................................................................................ 41

Overview of RRC States and State Transitions including GSM ...................................................................... 41 Processes in UE modes/states .......................................................................................................................... 42 UE Idle mode ............................................................................................................................................. 42 UTRA RRC Connected mode .................................................................................................................... 42 URA_PCH or CELL_PCH state ........................................................................................................... 42 CELL_FACH state ............................................................................................................................... 43 CELL_DCH state ................................................................................................................................. 43
RRC procedures ..................................................................................................................................... 44
8.1 RRC Connection Management Procedures...................................................................................................... 45 8.1.1 Broadcast of system information ................................................................................................................ 45 8.1.1.1 General ................................................................................................................................................. 45 8.1.1.1.1 System information structure .......................................................................................................... 45 8.1.1.1.2 System information blocks.............................................................................................................. 46 8.1.1.1.3 Segmentation and concatenation of system information blocks ..................................................... 50 8.1.1.1.4 Re-assembly of segments ................................................................................................................ 51 8.1.1.1.5 Scheduling of system information .................................................................................................. 52 8.1.1.2 Initiation ............................................................................................................................................... 53 8.1.1.3 Reception of SYSTEM INFORMATION messages by the UE ........................................................... 53 8.1.1.4 Void ...................................................................................................................................................... 53 8.1.1.5 Actions upon reception of the Master Information Block and Scheduling Block(s) ............................ 53 8.1.1.6 Actions upon reception of system information blocks ......................................................................... 57 8.1.1.6.1 System Information Block type 1 ................................................................................................... 58 8.1.1.6.2 System Information Block type 2 ................................................................................................... 59 8.1.1.6.3 System Information Block type 3 ................................................................................................... 59 8.1.1.6.4 System Information Block type 4 ................................................................................................... 60 8.1.1.6.5 System Information Block type 5 and 5bis ..................................................................................... 61 8.1.1.6.6 System Information Block type 6 ................................................................................................... 62 8.1.1.6.7 System Information Block type 7 ................................................................................................... 63 8.1.1.6.8 Void ................................................................................................................................................ 63 8.1.1.6.9 Void ................................................................................................................................................ 64 8.1.1.6.10 Void ................................................................................................................................................ 64 8.1.1.6.11 System Information Block type 11 ................................................................................................. 64 8.1.1.6.11a System Information Block type 11bis ............................................................................................. 65
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.1.6.12 8.1.1.6.13 8.1.1.6.14 8.1.1.6.15 8.1.1.6.16 8.1.1.6.17 8.1.1.6.18 8.1.1.7 8.1.1.7.1 8.1.1.7.2 8.1.1.7.3 8.1.1.7.4 8.1.2 8.1.2.1 8.1.2.2 8.1.2.3 8.1.3 8.1.3.1 8.1.3.2 8.1.3.3 8.1.3.4 8.1.3.5 8.1.3.5a 8.1.3.6 8.1.3.7 8.1.3.8 8.1.3.9 8.1.3.10 8.1.4 8.1.4.1 8.1.4.2 8.1.4.3 8.1.4.4 8.1.4.5 8.1.4.6 8.1.4.7 8.1.4.8 8.1.4.9 8.1.4.10 8.1.4.11 8.1.4a 8.1.4a.1 8.1.4a.2 8.1.5 8.1.6 8.1.6.1 8.1.6.2 8.1.6.3 8.1.6.4 8.1.6.5 8.1.6.6 8.1.7 8.1.7.1 8.1.7.2 8.1.7.3 8.1.7.4 8.1.8 8.1.8.1 8.1.8.2 8.1.8.2a
System Information Block type 12 ................................................................................................. 65 System Information Block type 13 ................................................................................................. 67 System Information Block type 14 ................................................................................................. 67 System Information Block type 15 ................................................................................................. 67 System Information Block type 16 ................................................................................................. 69 System Information Block type 17 ................................................................................................. 70 System Information Block type 18 ................................................................................................. 70 Modification of system information ..................................................................................................... 71 Modification of system information blocks using a value tag ........................................................ 71 Synchronised modification of system information blocks .............................................................. 71 Actions upon system information change ....................................................................................... 72 Actions upon expiry of a system information expiry timer............................................................. 72 Paging......................................................................................................................................................... 73 General ................................................................................................................................................. 73 Initiation ............................................................................................................................................... 73 Reception of a PAGING TYPE 1 message by the UE ......................................................................... 73 RRC connection establishment .................................................................................................................. 75 General ................................................................................................................................................. 75 Initiation ............................................................................................................................................... 75 RRC CONNECTION REQUEST message contents to set .................................................................. 76 Reception of an RRC CONNECTION REQUEST message by the UTRAN ...................................... 77 Cell re-selection, T300 or T318 timeout ............................................................................................... 78 Abortion of RRC connection establishment ......................................................................................... 79 Reception of an RRC CONNECTION SETUP message by the UE .................................................... 79 Physical channel failure or cell re-selection ......................................................................................... 81 Invalid RRC CONNECTION SETUP message, unsupported configuration or invalid configuration......................................................................................................................................... 81 Reception of an RRC CONNECTION REJECT message by the UE .................................................. 82 Invalid RRC CONNECTION REJECT message ................................................................................. 85 RRC connection release ............................................................................................................................. 86 General ................................................................................................................................................. 86 Initiation ............................................................................................................................................... 86 Reception of an RRC CONNECTION RELEASE message by the UE ............................................... 86 Invalid RRC CONNECTION RELEASE message .............................................................................. 88 Cell re-selection or radio link failure .................................................................................................... 88 Expiry of timer T308, unacknowledged mode transmission ................................................................ 89 Void ...................................................................................................................................................... 89 Reception of an RRC CONNECTION RELEASE COMPLETE message by UTRAN ....................... 89 Unsuccessful transmission of the RRC CONNECTION RELEASE COMPLETE message, acknowledged mode transmission ........................................................................................................ 90 Detection of loss of dedicated physical channel by UTRAN in CELL_DCH state .............................. 90 Failure to receive RRC CONNECTION RELEASE COMPLETE message by UTRAN .................... 90 RRC connection release requested by upper layers.................................................................................... 90 General ................................................................................................................................................. 90 Initiation ............................................................................................................................................... 90 Void ............................................................................................................................................................ 91 Transmission of UE capability information ............................................................................................... 91 General ................................................................................................................................................. 91 Initiation ............................................................................................................................................... 91 Reception of a UE CAPABILITY INFORMATION message by the UTRAN ................................... 92 Reception of the UE CAPABILITY INFORMATION CONFIRM message by the UE ..................... 92 Invalid UE CAPABILITY INFORMATION CONFIRM message ..................................................... 92 T304 timeout ........................................................................................................................................ 93 UE capability enquiry................................................................................................................................. 93 General ................................................................................................................................................. 93 Initiation ............................................................................................................................................... 93 Reception of a UE CAPABILITY ENQUIRY message by the UE...................................................... 93 Invalid UE CAPABILITY ENQUIRY message................................................................................... 94 Initial Direct transfer .................................................................................................................................. 94 General ................................................................................................................................................. 94 Initiation of Initial direct transfer procedure in the UE ........................................................................ 94 RLC re-establishment or inter-RAT change ......................................................................................... 96
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.8.2ab Inter-RAT handover from UTRAN to GERAN Iu mode ..................................................................... 96 8.1.8.2b Abortion of signalling connection establishment ................................................................................. 96 8.1.8.3 Reception of INITIAL DIRECT TRANSFER message by the UTRAN ............................................. 97 8.1.9 Downlink Direct transfer ............................................................................................................................ 97 8.1.9.1 General ................................................................................................................................................. 97 8.1.9.2 Initiation of downlink direct transfer procedure in the UTRAN .......................................................... 97 8.1.9.3 Reception of a DOWNLINK DIRECT TRANSFER message by the UE ............................................ 98 8.1.9.3a No signalling connection exists ............................................................................................................ 98 8.1.9.4 Invalid DOWNLINK DIRECT TRANSFER message ......................................................................... 98 8.1.10 Uplink Direct transfer................................................................................................................................. 99 8.1.10.1 General ................................................................................................................................................. 99 8.1.10.2 Initiation of uplink direct transfer procedure in the UE ........................................................................ 99 8.1.10.2a RLC re-establishment or inter-RAT change ......................................................................................... 99 8.1.10.2b Inter-RAT handover from UTRAN to GERAN Iu mode ................................................................... 100 8.1.10.3 Reception of UPLINK DIRECT TRANSFER message by the UTRAN ........................................... 100 8.1.11 UE dedicated paging ................................................................................................................................ 100 8.1.11.1 General ............................................................................................................................................... 100 8.1.11.2 Initiation ............................................................................................................................................. 100 8.1.11.3 Reception of a PAGING TYPE 2 message by the UE ....................................................................... 100 8.1.11.4 Invalid PAGING TYPE 2 message .................................................................................................... 101 8.1.12 Security mode control .............................................................................................................................. 101 8.1.12.1 General ............................................................................................................................................... 101 8.1.12.2 Initiation ............................................................................................................................................. 102 8.1.12.2.1 Ciphering configuration change .................................................................................................... 102 8.1.12.2.2 Integrity protection configuration change ..................................................................................... 103 8.1.12.3 Reception of SECURITY MODE COMMAND message by the UE ................................................. 104 8.1.12.3.1 New ciphering and integrity protection keys ................................................................................ 108 8.1.12.4 Void .................................................................................................................................................... 110 8.1.12.4a Incompatible simultaneous security reconfiguration .......................................................................... 110 8.1.12.4b Cell update procedure during security reconfiguration....................................................................... 110 8.1.12.4c Invalid configuration .......................................................................................................................... 111 8.1.12.5 Reception of SECURITY MODE COMPLETE message by the UTRAN......................................... 112 8.1.12.6 Invalid SECURITY MODE COMMAND message ........................................................................... 114 8.1.13 Signalling connection release procedure .................................................................................................. 114 8.1.13.1 General ............................................................................................................................................... 115 8.1.13.2 Initiation of SIGNALLING CONNECTION RELEASE by the UTRAN ......................................... 115 8.1.13.3 Reception of SIGNALLING CONNECTION RELEASE by the UE ................................................ 115 8.1.13.4 Invalid SIGNALLING CONNECTION RELEASE message ............................................................ 115 8.1.13.5 Invalid configuration .......................................................................................................................... 115 8.1.14 Signalling connection release indication procedure ................................................................................. 116 8.1.14.1 General ............................................................................................................................................... 116 8.1.14.2 Initiation ............................................................................................................................................. 116 8.1.14.2a RLC re-establishment or inter-RAT change ....................................................................................... 117 8.1.14.3 Reception of SIGNALLING CONNECTION RELEASE INDICATION by the UTRAN ............... 117 8.1.15 Counter check procedure .......................................................................................................................... 117 8.1.15.1 General ............................................................................................................................................... 117 8.1.15.2 Initiation ............................................................................................................................................. 117 8.1.15.3 Reception of a COUNTER CHECK message by the UE ................................................................... 118 8.1.15.4 Reception of the COUNTER CHECK RESPONSE message by UTRAN ......................................... 118 8.1.15.5 Cell re-selection .................................................................................................................................. 118 8.1.15.6 Invalid COUNTER CHECK message ................................................................................................ 119 8.1.16 Inter RAT handover information transfer................................................................................................. 119 8.1.16.1 General ............................................................................................................................................... 119 8.1.16.2 Initiation ............................................................................................................................................. 119 8.1.16.3 INTER RAT HANDOVER INFO message contents to set ................................................................ 120 8.2 Radio Bearer control procedures ................................................................................................................... 121 8.2.1 Radio bearer establishment ...................................................................................................................... 121 8.2.2 Reconfiguration procedures ..................................................................................................................... 121 8.2.2.1 General ............................................................................................................................................... 123 8.2.2.2 Initiation ............................................................................................................................................. 124 8.2.2.2a Initiation of handover from GERAN Iu mode .................................................................................... 125
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.2.3
8.2.2.3a 8.2.2.4 8.2.2.5 8.2.2.5a 8.2.2.6 8.2.2.7 8.2.2.8 8.2.2.9 8.2.2.10 8.2.2.11 8.2.2.12 8.2.2.12a 8.2.2.12b 8.2.2.13 8.2.2.14 8.2.3 8.2.4 8.2.5 8.2.5.1 8.2.5.2 8.2.5.3 8.2.5.4 8.2.5.5 8.2.6 8.2.7 8.2.7.1 8.2.7.2 8.2.7.3 8.2.7.4 8.2.8 8.2.8.1 8.2.8.2 8.2.8.3 8.2.8.4 8.2.8.5 8.2.9 8.2.10 8.2.10.1 8.2.10.2 8.2.10.3 8.2.10.4 8.2.11 8.2.11.1 8.2.11.2 8.2.11.3 8.3 8.3.1 8.3.1.1 8.3.1.2 8.3.1.3 8.3.1.4 8.3.1.4.1 8.3.1.4.2 8.3.1.5 8.3.1.6 8.3.1.7 8.3.1.7a 8.3.1.8
Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE or TRANSPORT CHANNEL RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message by the UE .............................................. 126 Reception of RADIO BEARER RECONFIGURATION message by the UE performing handover from GERAN Iu mode ........................................................................................................ 135 Transmission of a response message by the UE, normal case ............................................................ 136 Reception of a response message by the UTRAN, normal case ......................................................... 138 Rejection by the UE ............................................................................................................................ 139 Unsupported configuration in the UE ................................................................................................. 139 Physical channel failure ...................................................................................................................... 140 Cell re-selection .................................................................................................................................. 140 Transmission of a response message by the UE, failure case ............................................................. 141 Reception of a response message by the UTRAN, failure case .......................................................... 141 Invalid configuration .......................................................................................................................... 142 Incompatible simultaneous reconfiguration........................................................................................ 142 Incompatible simultaneous security reconfiguration .......................................................................... 142 Cell update procedure during security reconfiguration....................................................................... 143 Invalid received message .................................................................................................................... 144 Radio link failure ................................................................................................................................ 144 Radio bearer release ................................................................................................................................. 145 Transport channel reconfiguration ........................................................................................................... 145 Transport format combination control...................................................................................................... 145 General ............................................................................................................................................... 146 Initiation ............................................................................................................................................. 146 Reception of a TRANSPORT FORMAT COMBINATION CONTROL message by the UE........... 146 Invalid configuration .......................................................................................................................... 147 Invalid TRANSPORT FORMAT COMBINATION CONTROL message ........................................ 148 Physical channel reconfiguration ............................................................................................................. 148 Physical Shared Channel Allocation [TDD only] .................................................................................... 148 General ............................................................................................................................................... 149 Initiation ............................................................................................................................................. 149 Reception of a PHYSICAL SHARED CHANNEL ALLOCATION message by the UE ................. 149 Invalid PHYSICAL SHARED CHANNEL ALLOCATION message .............................................. 151 PUSCH capacity request [TDD only] ...................................................................................................... 151 General ............................................................................................................................................... 152 Initiation ............................................................................................................................................. 152 PUSCH CAPACITY REQUEST message contents to set ................................................................. 152 Reception of a PUSCH CAPACITY REQUEST message by the UTRAN ....................................... 153 T310 expiry ........................................................................................................................................ 153 Void .......................................................................................................................................................... 154 Uplink Physical Channel Control [TDD only] ......................................................................................... 154 General ............................................................................................................................................... 154 Initiation ............................................................................................................................................. 154 Reception of UPLINK PHYSICAL CHANNEL CONTROL message by the UE ............................ 154 Invalid UPLINK PHYSICAL CHANNEL CONTROL message....................................................... 155 Physical channel reconfiguration failure .................................................................................................. 155 General ............................................................................................................................................... 155 Runtime error due to overlapping compressed mode configurations ................................................. 155 Void .................................................................................................................................................... 156 RRC connection mobility procedures ............................................................................................................ 156 Cell and URA update procedures ............................................................................................................. 156 General ............................................................................................................................................... 158 Initiation ............................................................................................................................................. 159 CELL UPDATE / URA UPDATE message contents to set ............................................................... 163 T305 expiry and the UE detects "out of service area" ........................................................................ 166 Re-entering "in service area" ........................................................................................................ 166 Expiry of timer T307 .................................................................................................................... 167 Reception of an CELL UPDATE/URA UPDATE message by the UTRAN ..................................... 167 Reception of the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message by the UE ...... 168 Transmission of a response message to UTRAN ............................................................................... 174 Physical channel failure ...................................................................................................................... 178 Unsupported configuration by the UE ................................................................................................ 179
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.1.9 8.3.1.9a 8.3.1.9b 8.3.1.10 8.3.1.11 8.3.1.12 8.3.1.13 8.3.1.14 8.3.1.15 8.3.2 8.3.3 8.3.3.1 8.3.3.2 8.3.3.3 8.3.3.4 8.3.3.5 8.3.3.5a 8.3.3.6 8.3.4 8.3.4.1 8.3.4.2 8.3.4.3 8.3.4.4 8.3.4.5 8.3.4.5a 8.3.4.5b 8.3.4.6 8.3.4.7 8.3.4.8 8.3.4.9 8.3.5 8.3.5.1 8.3.5.1.1 8.3.5.1.2 8.3.5.2 8.3.5.2.1 8.3.5.2.2 8.3.6 8.3.6.1 8.3.6.2 8.3.6.3 8.3.6.4 8.3.6.4a 8.3.6.5 8.3.6.6 8.3.7 8.3.7.1 8.3.7.2 8.3.7.3 8.3.7.4 8.3.7.5 8.3.7.6 8.3.7.7 8.3.7.8 8.3.7.8a 8.3.8 8.3.8.1 8.3.8.2 8.3.8.2a 8.3.8.3 8.3.8.3a 8.3.9
Invalid configuration .......................................................................................................................... 180 Incompatible simultaneous reconfiguration........................................................................................ 181 Security reconfiguration during Cell update procedure ...................................................................... 182 Confirmation error of URA ID list ..................................................................................................... 183 Invalid CELL UPDATE CONFIRM/URA UPDATE CONFIRM message ...................................... 184 T302 expiry or cell reselection ........................................................................................................... 184 T314 expiry ........................................................................................................................................ 187 T315 expiry ........................................................................................................................................ 188 Reception of the UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN ....... 189 URA update .............................................................................................................................................. 189 UTRAN mobility information .................................................................................................................. 189 General ............................................................................................................................................... 190 Initiation ............................................................................................................................................. 190 Reception of UTRAN MOBILITY INFORMATION message by the UE ........................................ 190 Reception of an UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN ........ 193 Cell re-selection .................................................................................................................................. 193 Incompatible simultaneous security reconfiguration .......................................................................... 194 Invalid UTRAN MOBILITY INFORMATION message .................................................................. 194 Active set update ...................................................................................................................................... 195 General ............................................................................................................................................... 195 Initiation ............................................................................................................................................. 195 Reception of an ACTIVE SET UPDATE message by the UE ........................................................... 196 Unsupported configuration in the UE ................................................................................................. 198 Invalid configuration .......................................................................................................................... 198 Void .................................................................................................................................................... 199 Incompatible simultaneous reconfiguration........................................................................................ 199 Reception of the ACTIVE SET UPDATE COMPLETE message by the UTRAN ............................ 199 Reception of the ACTIVE SET UPDATE FAILURE message by the UTRAN ................................ 199 Invalid ACTIVE SET UPDATE message .......................................................................................... 199 Reception of an ACTIVE SET UPDATE message in wrong state ..................................................... 200 Hard handover .......................................................................................................................................... 200 Timing re-initialised hard handover ................................................................................................... 200 General .......................................................................................................................................... 200 Initiation (FDD only) .................................................................................................................... 201 Timing-maintained hard handover ..................................................................................................... 202 General .......................................................................................................................................... 202 Initiation (FDD only) .................................................................................................................... 202 Inter-RAT handover to UTRAN .............................................................................................................. 202 General ............................................................................................................................................... 203 Initiation ............................................................................................................................................. 203 Reception of HANDOVER TO UTRAN COMMAND message by the UE ...................................... 203 Invalid Handover to UTRAN command message .............................................................................. 207 Unsupported configuration in HANDOVER TO UTRAN COMMAND message ............................ 208 UE fails to perform handover ............................................................................................................. 208 Reception of message HANDOVER TO UTRAN COMPLETE by the UTRAN ............................. 208 Inter-RAT handover from UTRAN .......................................................................................................... 208 General ............................................................................................................................................... 209 Initiation ............................................................................................................................................. 209 Reception of a HANDOVER FROM UTRAN COMMAND message by the UE ............................. 209 Successful completion of the inter-RAT handover ............................................................................. 210 UE fails to complete requested handover ........................................................................................... 211 Invalid HANDOVER FROM UTRAN COMMAND message .......................................................... 211 Reception of an HANDOVER FROM UTRAN FAILURE message by UTRAN ............................. 212 Unsupported configuration in HANDOVER FROM UTRAN COMMAND message ...................... 212 Reception of HANDOVER FROM UTRAN COMMAND message by UE in CELL_FACH .......... 213 Inter-RAT cell reselection to UTRAN ..................................................................................................... 213 General ............................................................................................................................................... 213 Initiation ............................................................................................................................................. 213 Initiation of inter-RAT cell reselection from GERAN Iu mode ......................................................... 214 UE fails to complete an inter-RAT cell reselection ............................................................................ 214 UE fails to complete an inter-RAT cell reselection from GERAN Iu mode ....................................... 214 Inter-RAT cell reselection from UTRAN................................................................................................. 215
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.9.1 General ............................................................................................................................................... 215 8.3.9.2 Initiation ............................................................................................................................................. 215 8.3.9.2a Initiation of inter-RAT cell reselection to GERAN Iu mode .............................................................. 215 8.3.9.3 Successful cell reselection .................................................................................................................. 215 8.3.9.4 UE fails to complete an inter-RAT cell reselection ............................................................................ 215 8.3.10 Inter-RAT cell change order to UTRAN .................................................................................................. 216 8.3.10.1 General ............................................................................................................................................... 216 8.3.10.2 Initiation ............................................................................................................................................. 216 8.3.10.3 UE fails to complete an inter-RAT cell change order......................................................................... 216 8.3.11 Inter-RAT cell change order from UTRAN ............................................................................................. 216 8.3.11.1 General ............................................................................................................................................... 217 8.3.11.2 Initiation ............................................................................................................................................. 217 8.3.11.3 Reception of an CELL CHANGE ORDER FROM UTRAN message by the UE ............................. 217 8.3.11.4 Successful completion of the cell change order.................................................................................. 218 8.3.11.5 Expiry of timer T309 or UE fails to complete requested cell change order........................................ 218 8.3.11.6 Unsupported configuration in CELL CHANGE ORDER FROM UTRAN message ......................... 219 8.3.11.7 Invalid CELL CHANGE ORDER FROM UTRAN message ............................................................ 220 8.4 Measurement procedures ............................................................................................................................... 220 8.4.0 Measurement related definitions .............................................................................................................. 220 8.4.1 Measurement control ................................................................................................................................ 222 8.4.1.1 General ............................................................................................................................................... 222 8.4.1.2 Initiation ............................................................................................................................................. 222 8.4.1.3 Reception of MEASUREMENT CONTROL by the UE.................................................................... 222 8.4.1.4 Unsupported measurement in the UE ................................................................................................. 228 8.4.1.4a Configuration Incomplete ................................................................................................................... 228 8.4.1.5 Invalid MEASUREMENT CONTROL message ............................................................................... 229 8.4.1.6 Measurements after transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state ... 229 8.4.1.6.1 Intra-frequency measurement ....................................................................................................... 229 8.4.1.6.2 Inter-frequency measurement ....................................................................................................... 230 8.4.1.6.3 Inter-RAT measurement ............................................................................................................... 230 8.4.1.6.4 Quality measurement .................................................................................................................... 230 8.4.1.6.5 UE internal measurement .............................................................................................................. 230 8.4.1.6.6 Traffic volume measurement ........................................................................................................ 231 8.4.1.6.7 UE positioning measurement ........................................................................................................ 231 8.4.1.6a Actions in CELL_FACH/CELL_PCH/URA/PCH state upon cell re-selection.................................. 233 8.4.1.7 Measurements after transition from CELL_FACH to CELL_DCH state ........................................... 233 8.4.1.7.1 Intra-frequency measurement ....................................................................................................... 233 8.4.1.7.2 Inter-frequency measurement ....................................................................................................... 234 8.4.1.7.3 Inter-RAT measurement ............................................................................................................... 234 8.4.1.7.4 Traffic volume measurement ........................................................................................................ 234 8.4.1.7.5 UE positioning measurement ........................................................................................................ 235 8.4.1.8 Measurements after transition from idle mode to CELL_DCH state ................................................. 235 8.4.1.8.1 Intra-frequency measurement ....................................................................................................... 235 8.4.1.8.2 Inter-frequency measurement ....................................................................................................... 235 8.4.1.8.3 Inter-RAT measurement ............................................................................................................... 235 8.4.1.8.4 Traffic volume measurement ........................................................................................................ 236 8.4.1.8.5 UE positioning measurement ........................................................................................................ 236 8.4.1.9 Measurements after transition from idle mode to CELL_FACH state ............................................... 236 8.4.1.9.1 Intra-frequency measurement ....................................................................................................... 236 8.4.1.9.2 Inter-frequency measurement ....................................................................................................... 236 8.4.1.9.3 Inter-RAT measurement ............................................................................................................... 236 8.4.1.9.4 Traffic volume measurement ........................................................................................................ 236 8.4.1.9.5 UE positioning measurement ........................................................................................................ 236 8.4.1.9a Measurements after transition from connected mode to idle mode .................................................... 237 8.4.1.9a.1 Intra-frequency measurement ....................................................................................................... 237 8.4.1.9a.2 Inter-frequency measurement ....................................................................................................... 237 8.4.1.9a.3 Inter-RAT measurement ............................................................................................................... 237 8.4.1.9a.4 UE positioning measurement ........................................................................................................ 237 8.4.1.9b Measurements after transition from CELL_FACH to CELL_PCH/URA_PCH ................................ 238 8.4.1.9b.1 Traffic volume measurement ........................................................................................................ 238 8.4.1.9b.2 UE positioning measurement ........................................................................................................ 238 8.4.1.9c Measurements after transition from CELL_PCH/URA_PCH to CELL_FACH ................................ 238
3GPP
Release 6
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.9c.1 Traffic volume measurement ........................................................................................................ 238 8.4.1.9c.2 UE positioning measurement ........................................................................................................ 239 8.4.1.10 Changes in measurement objects ........................................................................................................ 239 8.4.1.10.1 Traffic volume measurement ........................................................................................................ 239 8.4.1.10.2 Quality measurement .................................................................................................................... 240 8.4.1.10.3 Intra-frequency, Inter-frequency and Inter-RAT measurements ................................................... 240 8.4.2 Measurement report.................................................................................................................................. 240 8.4.2.1 General ............................................................................................................................................... 240 8.4.2.2 Initiation ............................................................................................................................................. 240 8.4.3 Assistance Data Delivery ......................................................................................................................... 242 8.4.3.1 General ............................................................................................................................................... 242 8.4.3.2 Initiation ............................................................................................................................................. 242 8.4.3.3 Reception of ASSISTANCE DATA DELIVERY message by the UE .............................................. 242 8.4.3.4 Invalid ASSISTANCE DATA DELIVERY message ........................................................................ 242 8.5 General procedures ........................................................................................................................................ 243 8.5.1 Selection of initial UE identity ................................................................................................................. 243 8.5.2 Actions when entering idle mode from connected mode ......................................................................... 243 8.5.3 Open loop power control upon establishment of DPCCH........................................................................ 244 8.5.4 Physical channel establishment criteria .................................................................................................... 245 8.5.5 Actions in "out of service area" and "in service area" .............................................................................. 245 8.5.5.1 Detection of "out of service" area ....................................................................................................... 245 8.5.5.1.1 Actions following detection of "out of service" area in URA_PCH or CELL_PCH state.................. 245 8.5.5.1.2 Actions following detection of "out of service" area in CELL_FACH state ...................................... 245 8.5.5.1.3 Actions following detection of "out of service" area on transition from CELL_DCH to URA_PCH or CELL_PCH ................................................................................................................. 245 8.5.5.1.4 Actions following detection of "out of service" area on transition from CELL_DCH to CELL_FACH ..................................................................................................................................... 246 8.5.5.2 Detection of "in service" area ............................................................................................................. 246 8.5.5.2.1 Actions following Re-entry into "in service area" in URA_PCH or CELL_PCH state ...................... 246 8.5.5.2.2 Actions following re-entry into "in service area" in CELL_FACH state ........................................... 246 8.5.5.3 T316 expiry ........................................................................................................................................ 247 8.5.5.4 T317 expiry ........................................................................................................................................ 247 8.5.6 Radio link failure criteria and actions upon radio link failure .................................................................. 247 8.5.7 Open loop power control .......................................................................................................................... 247 8.5.8 Maintenance of Hyper Frame Numbers ................................................................................................... 251 8.5.9 START value calculation ......................................................................................................................... 252 8.5.10 Integrity protection ................................................................................................................................... 253 8.5.10.1 Integrity protection in downlink ......................................................................................................... 254 8.5.10.2 Integrity protection in uplink .............................................................................................................. 255 8.5.10.3 Calculation of message authentication code ....................................................................................... 255 8.5.11 FACH measurement occasion calculation................................................................................................ 256 8.5.12 Establishment of Access Service Classes ................................................................................................. 256 8.5.13 Mapping of Access Classes to Access Service Classes ............................................................................ 257 8.5.14 PLMN Type Selection .............................................................................................................................. 257 8.5.14a Neighbour cells list narrowing for cell reselection ................................................................................... 258 8.5.15 CFN calculation ....................................................................................................................................... 258 8.5.15.1 Initialisation for CELL_DCH state after state transition .................................................................... 258 8.5.15.2 Initialisation in CELL_DCH state at hard handover........................................................................... 258 8.5.15.3 Initialisation for CELL_FACH ........................................................................................................... 259 8.5.15.4 Initialisation after intersystem handover to UTRAN .......................................................................... 259 8.5.15.5 Initialisation for MTCH and/or MSCH carried on S-CCPCH that may be soft combined ................. 259 8.5.16 Configuration of CTCH occasions ........................................................................................................... 259 8.5.17 PRACH selection ..................................................................................................................................... 260 8.5.18 Selection of RACH TTI ........................................................................................................................... 261 8.5.18.1 FDD .................................................................................................................................................... 261 8.5.18.2 1.28 Mcps TDD .................................................................................................................................. 262 8.5.19 Secondary CCPCH selection .................................................................................................................... 262 8.5.19a Secondary CCPCH and FACH selection for MCCH reception ............................................................... 263 8.5.20 Unsupported configuration ....................................................................................................................... 263 8.5.21 Actions related to Radio Bearer mapping ................................................................................................ 263 8.5.22 Actions when entering another RAT from connected mode .................................................................... 267 8.5.23 Measured results on RACH...................................................................................................................... 268
3GPP
Release 6
10
3GPP TS 25.331 V6.23.0 (2009-09)
8.5.24 Change of PLMN while in RRC connected mode ................................................................................... 269 8.5.25 Actions related to HS_DSCH_RECEPTION variable ............................................................................. 270 8.5.26 Service prioritisation ................................................................................................................................ 271 8.5.27 MBMS frequency selection ...................................................................................................................... 272 8.5.28 Actions related to E_DCH_TRANSMISSION variable........................................................................... 274 8.5.29 MBMS modification period identity calculation ...................................................................................... 275 8.5.30 Detecting MBMS service reception inability ........................................................................................... 275 8.6 Generic actions on receipt and absence of an information element ............................................................... 276 8.6.1 CN information elements ......................................................................................................................... 276 8.6.1.1 Void .................................................................................................................................................... 276 8.6.1.2 CN information info ........................................................................................................................... 276 8.6.1.3 Signalling connection release indication ............................................................................................ 276 8.6.2 UTRAN mobility information elements ................................................................................................... 277 8.6.2.1 URA identity ...................................................................................................................................... 277 8.6.2.2 Mapping info ...................................................................................................................................... 277 8.6.3 UE information elements ......................................................................................................................... 277 8.6.3.1 Activation time ................................................................................................................................... 277 8.6.3.1a CN domain specific DRX cycle length coefficient............................................................................. 279 8.6.3.1b H-RNTI .............................................................................................................................................. 279 8.6.3.2 UTRAN DRX Cycle length coefficient .............................................................................................. 279 8.6.3.3 Generic state transition rules depending on received information elements ....................................... 279 8.6.3.4 Ciphering mode info ........................................................................................................................... 280 8.6.3.5 Integrity protection mode info ............................................................................................................ 283 8.6.3.5.1 Initialisation of Integrity Protection .............................................................................................. 284 8.6.3.5.2 Integrity Protection Re-configuration for SRNS Relocation and handover from GERAN Iu mode ............................................................................................................................................. 285 8.6.3.5.3 Integrity Protection modification in case of new keys or initialisation of signalling connection.. 286 8.6.3.6 Void .................................................................................................................................................... 287 8.6.3.7 Void .................................................................................................................................................... 287 8.6.3.8 Integrity check info ............................................................................................................................. 287 8.6.3.9 New C-RNTI ...................................................................................................................................... 287 8.6.3.9a New DSCH-RNTI .............................................................................................................................. 287 8.6.3.10 New U-RNTI ...................................................................................................................................... 287 8.6.3.11 RRC transaction identifier .................................................................................................................. 287 8.6.3.12 Capability Update Requirement ......................................................................................................... 291 8.6.3.13 Group release information .................................................................................................................. 292 8.6.3.14 New E-RNTI ...................................................................................................................................... 292 8.6.4 Radio bearer information elements .......................................................................................................... 293 8.6.4.1 Signalling RB information to setup list .............................................................................................. 293 8.6.4.2 RAB information for setup ................................................................................................................. 294 8.6.4.2a RAB information to reconfigure ......................................................................................................... 295 8.6.4.3 RB information to setup ..................................................................................................................... 295 8.6.4.4 RB information to be affected ............................................................................................................ 297 8.6.4.4a Void .................................................................................................................................................... 297 8.6.4.5 RB information to reconfigure............................................................................................................ 297 8.6.4.6 RB information to release ................................................................................................................... 298 8.6.4.7 RB with PDCP information ................................................................................................................ 298 8.6.4.8 RB mapping info ................................................................................................................................ 298 8.6.4.9 RLC Info ............................................................................................................................................. 301 8.6.4.10 PDCP Info .......................................................................................................................................... 303 8.6.4.11 PDCP SN Info .................................................................................................................................... 305 8.6.4.12 NAS Synchronisation Indicator .......................................................................................................... 305 8.6.4.13 PDCP context relocation info ............................................................................................................. 305 8.6.4.14 RLC Info MBMS ................................................................................................................................ 305 8.6.4.15 RAB information for MBMS ptp bearer............................................................................................. 305 8.6.5 Transport channel information elements .................................................................................................. 306 8.6.5.1 Transport Format Set .......................................................................................................................... 306 8.6.5.2 Transport format combination set ....................................................................................................... 307 8.6.5.3 Transport format combination subset ................................................................................................. 309 8.6.5.4 DCH quality target ............................................................................................................................. 311 8.6.5.5 Added or Reconfigured UL TrCH information .................................................................................. 311 8.6.5.5a Added or reconfigured MAC-d flow .................................................................................................. 311
3GPP
Release 6
11
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.5.6 8.6.5.6a 8.6.5.6b 8.6.5.7 8.6.5.8 8.6.5.9 8.6.5.10 8.6.5.11 8.6.5.12 8.6.5.12a 8.6.5.13 8.6.5.14 8.6.5.15 8.6.5.16 8.6.5.17 8.6.5.18 8.6.6 8.6.6.1 8.6.6.2 8.6.6.2a 8.6.6.3 8.6.6.3a 8.6.6.4 8.6.6.5 8.6.6.6 8.6.6.7 8.6.6.8 8.6.6.9 8.6.6.10 8.6.6.11 8.6.6.12 8.6.6.13 8.6.6.14 8.6.6.15 8.6.6.16 8.6.6.17 8.6.6.18 8.6.6.19 8.6.6.20 8.6.6.21 8.6.6.22 8.6.6.23 8.6.6.24 8.6.6.25 8.6.6.26 8.6.6.26a 8.6.6.27 8.6.6.28 8.6.6.28a 8.6.6.29 8.6.6.30 8.6.6.31 8.6.6.32 8.6.6.33 8.6.6.34 8.6.6.35 8.6.6.36 8.6.6.37 8.6.7 8.6.7.1 8.6.7.2 8.6.7.3
Added or Reconfigured DL TrCH information .................................................................................. 312 Void .................................................................................................................................................... 313 HARQ Info ......................................................................................................................................... 313 Deleted UL TrCH information ........................................................................................................... 313 Deleted DL TrCH information ........................................................................................................... 313 UL Transport channel information common for all transport channels .............................................. 314 DL Transport channel information common for all transport channels .............................................. 314 Void .................................................................................................................................................... 315 TFCS Reconfiguration/Addition Information .................................................................................... 315 Additional RACH TFCS for CCCH ................................................................................................... 316 TFCS Removal Information ............................................................................................................... 316 Void .................................................................................................................................................... 316 TFCS Explicit Configuration .............................................................................................................. 316 E-DCH Transmission Time Interval ................................................................................................... 316 HARQ Info for E-DCH ...................................................................................................................... 317 Added or reconfigured E-DCH MAC-d flow ..................................................................................... 317 Physical channel information elements .................................................................................................... 318 Frequency info .................................................................................................................................... 318 Void .................................................................................................................................................... 318 PNBSCH allocation ............................................................................................................................ 318 Void .................................................................................................................................................... 319 Downlink information per radio link list ............................................................................................ 319 Downlink information for each radio link .......................................................................................... 320 Void .................................................................................................................................................... 322 Uplink DPCH info .............................................................................................................................. 322 Void .................................................................................................................................................... 322 Maximum allowed UL TX power ...................................................................................................... 322 Void .................................................................................................................................................... 323 Void .................................................................................................................................................... 323 Uplink DPCH power control info ....................................................................................................... 323 Secondary CPICH info ....................................................................................................................... 324 Primary CPICH usage for channel estimation .................................................................................... 324 DPCH frame offset (FDD Only)......................................................................................................... 324 DPCH Compressed mode info............................................................................................................ 326 Repetition period, Repetition length, Offset (TDD only) ................................................................... 329 Primary CCPCH info .......................................................................................................................... 330 Primary CPICH info ........................................................................................................................... 330 Void .................................................................................................................................................... 330 Void .................................................................................................................................................... 330 Void .................................................................................................................................................... 330 Secondary Scrambling Code, Code Number ...................................................................................... 330 PDSCH Power Control info ............................................................................................................... 331 Tx Diversity Mode ............................................................................................................................. 331 Void .................................................................................................................................................... 332 UL Timing Advance Control (TDD only) .......................................................................................... 332 Uplink synchronisation parameters (TDD only)................................................................................. 333 Downlink information common for all radio links ............................................................................. 333 Downlink DPCH info common for all radio links .............................................................................. 333 Downlink F-DPCH info common for all radio links .......................................................................... 335 ASC setting ......................................................................................................................................... 335 SRB delay, PC preamble (FDD only) ................................................................................................. 337 Void .................................................................................................................................................... 337 Void .................................................................................................................................................... 337 HS-SCCH Info.................................................................................................................................... 337 Measurement Feedback Info............................................................................................................... 338 DPC Mode .......................................................................................................................................... 338 Downlink HS-PDSCH Information .................................................................................................... 338 E-DCH Info ........................................................................................................................................ 339 Measurement information elements ......................................................................................................... 339 Measurement validity ......................................................................................................................... 339 Filter coefficient ................................................................................................................................. 340 Intra-frequency/Inter-frequency/Inter-RAT cell info list .................................................................... 341
3GPP
Release 6
12
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.4 Intra-frequency measurement quantity ............................................................................................... 348 8.6.7.5 Inter-RAT measurement quantity ....................................................................................................... 348 8.6.7.6 Inter-RAT reporting quantity .............................................................................................................. 349 8.6.7.7 Cell Reporting Quantities ................................................................................................................... 350 8.6.7.8 Periodical Reporting Criteria .............................................................................................................. 351 8.6.7.9 Reporting Cell Status .......................................................................................................................... 351 8.6.7.10 Traffic Volume Measurement............................................................................................................. 352 8.6.7.11 Traffic Volume Measurement Reporting Criteria............................................................................... 352 8.6.7.12 FACH measurement occasion info ..................................................................................................... 353 8.6.7.13 Measurement Reporting Mode ........................................................................................................... 353 8.6.7.14 Inter-frequency measurement ............................................................................................................. 354 8.6.7.15 Inter-RAT measurement ..................................................................................................................... 355 8.6.7.16 Intra-frequency measurement ............................................................................................................. 355 8.6.7.17 Quality measurement .......................................................................................................................... 355 8.6.7.18 UE internal measurement ................................................................................................................... 356 8.6.7.18a Void .................................................................................................................................................... 356 8.6.7.19 UE positioning .................................................................................................................................... 356 8.6.7.19.0 UE positioning reporting criteria .................................................................................................. 356 8.6.7.19.1 UE positioning reporting quantity................................................................................................. 356 8.6.7.19.1a UE positioning reporting for UE assisted methods ....................................................................... 357 8.6.7.19.1b UE positioning reporting for UE based methods .......................................................................... 359 8.6.7.19.2 UE positioning OTDOA assistance data for UE-assisted ............................................................. 361 8.6.7.19.2a UE positioning OTDOA assistance data for UE-based................................................................. 361 8.6.7.19.3 UE positioning GPS assistance data ............................................................................................. 363 8.6.7.19.4 UE positioning Ciphering info ...................................................................................................... 366 8.6.7.19.5 UE positioning Error ..................................................................................................................... 367 8.6.7.19.6 Void .............................................................................................................................................. 368 8.6.7.20 Void .................................................................................................................................................... 368 8.6.7.21 Intra-frequency reporting quantity for RACH reporting .................................................................... 368 8.6.7.22 Additional Measurement List ............................................................................................................. 368 8.6.8 Void .......................................................................................................................................................... 369 8.6.9 MBMS specific information elements...................................................................................................... 369 8.6.9.1 Continue MCCH Reading .................................................................................................................. 369 8.6.9.1a MBMS dynamic persistence level ...................................................................................................... 369 8.6.9.2 MBMS PL Service Restriction Information ....................................................................................... 369 8.6.9.3 MBMS L1 combining schedule .......................................................................................................... 369 8.6.9.3a MBMS Number of neighbour cells .................................................................................................... 370 8.6.9.4 MBMS Preferred frequency information ............................................................................................ 370 8.6.9.4a Void .................................................................................................................................................... 370 8.6.9.4b MBMS p-t-m activation time ............................................................................................................. 370 8.6.9.5 MBMS RB list released to change transfer mode ............................................................................... 371 8.6.9.6 MBMS Required UE action ............................................................................................................... 371 8.6.9.6a MBMS re- acquire MCCH ................................................................................................................. 372 8.6.9.7 MBMS Service transmissions info list ............................................................................................... 372 8.6.9.8 MBMS Short transmission ID ............................................................................................................ 372 8.6.9.9 MBMS Transmission identity ............................................................................................................ 373 8.6.9.9a MBMS transmission time difference .................................................................................................. 373 8.6.9.9b MCCH configuration information ...................................................................................................... 373 8.6.9.10 Next scheduling period ....................................................................................................................... 374 8.7 MBMS specific procedures ........................................................................................................................... 374 8.7.1 Reception of MBMS control information ................................................................................................ 374 8.7.1.1 General ............................................................................................................................................... 374 8.7.1.2 Initiation ............................................................................................................................................. 375 8.7.1.3 UE requirements on reading of MCCH information .......................................................................... 375 8.7.1.4 UE requirements on reading of MSCH information ........................................................................... 376 8.7.2 MCCH acquisition ................................................................................................................................... 376 8.7.2.1 General ............................................................................................................................................... 376 8.7.2.2 Initiation ............................................................................................................................................. 377 8.7.2.3 MCCH information to be acquired by the UE .................................................................................... 377 8.7.2.4 Reception of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION by the UE ................................................................. 377 8.7.2.5 Reception of the other MBMS messages by the UE........................................................................... 378
3GPP
Release 6
13
3GPP TS 25.331 V6.23.0 (2009-09)
8.7.3 8.7.3.1 8.7.3.2 8.7.3.3 8.7.3.3.1 8.7.3.3.2 8.7.3.3.3 8.7.3.4 8.7.3.5 8.7.4 8.7.4.1 8.7.4.2 8.7.4.3 8.7.4.4 8.7.4.5 8.7.5 8.7.5.1 8.7.5.2 8.7.5.3 8.7.5.4 8.7.6 8.7.6.1 8.7.6.2 8.7.6.2a 8.7.6.3 8.7.7 8.7.7.1 8.7.7.2 8.7.7.3
MBMS Notification ................................................................................................................................. 378 General ............................................................................................................................................... 379 Initiation ............................................................................................................................................. 379 Receiving the MBMS Notification information ................................................................................. 379 Reception via MCCH .................................................................................................................... 379 Void .............................................................................................................................................. 380 Reception via DCCH .................................................................................................................... 380 UE action upon receiving MBMS MODIFIED SERVICES INFORMATION message ................... 380 UE fails to receive MBMS Notification information ......................................................................... 381 MBMS counting ....................................................................................................................................... 381 General ............................................................................................................................................... 382 Initiation ............................................................................................................................................. 382 Reception of the MBMS ACCESS INFORMATION ........................................................................ 382 Termination of the MBMS counting procedure.................................................................................. 383 Failure of the counting response procedure ........................................................................................ 383 MBMS p-t-m radio bearer configuration ................................................................................................. 384 General ............................................................................................................................................... 384 Initiation ............................................................................................................................................. 384 Reception of the MBMS Current Cell PTM RB information ............................................................. 384 Reception of the MBMS Neighbouring Cell PTM RB information ................................................... 385 MBMS modification request .................................................................................................................... 385 General ............................................................................................................................................... 385 Initiation ............................................................................................................................................. 385 MBMS MODIFICATION REQUEST message contents to set ......................................................... 386 Reception of a MBMS MODIFICATION REQUEST message by the UTRAN ............................... 386 MBMS service scheduling ....................................................................................................................... 387 General ............................................................................................................................................... 387 Initiation ............................................................................................................................................. 387 Reception of the MBMS scheduling information ............................................................................... 387 General........................................................................................................................................................... 387 ASN.1 violation or encoding error................................................................................................................. 388 Unknown or unforeseen message type........................................................................................................... 388 Unsolicited received message ........................................................................................................................ 388 Unexpected critical message extension.......................................................................................................... 389 Unknown or unforeseen information element value, mandatory information element .................................. 389 Conditional information element error .......................................................................................................... 390 Unknown or unforeseen information element value, conditional information element ................................. 390 Unknown or unforeseen information element value, optional information element ...................................... 391 Unexpected non-critical message extension .................................................................................................. 391 Handling of errors in nested information elements ........................................................................................ 392
9
9.1 9.2 9.3 9.3a 9.3b 9.4 9.5 9.6 9.7 9.8 9.9
Handling of unknown, unforeseen and erroneous protocol data .......................................................... 387
10
Message and information element functional definition and content .................................................. 393
10.1 General........................................................................................................................................................... 393 10.1.1 Protocol extensions .................................................................................................................................. 394 10.1.1.1 Non-critical extensions ....................................................................................................................... 395 10.1.1.1.1 Extension of an information element with additional values or choices ....................................... 395 10.1.1.1.2 Extension of a message with additional information elements ..................................................... 396 10.1.1.2 Critical extensions .............................................................................................................................. 396 10.1.1.2.1 Extension of an information element with additional values or choices ....................................... 396 10.1.1.2.2 Extension of a message with additional information elements ..................................................... 396 10.2 Radio Resource Control messages ................................................................................................................. 396 10.2.1 ACTIVE SET UPDATE .......................................................................................................................... 396 10.2.2 ACTIVE SET UPDATE COMPLETE .................................................................................................... 398 10.2.3 ACTIVE SET UPDATE FAILURE......................................................................................................... 398 10.2.4 ASSISTANCE DATA DELIVERY ......................................................................................................... 399 10.2.5 CELL CHANGE ORDER FROM UTRAN ............................................................................................. 400 10.2.6 CELL CHANGE ORDER FROM UTRAN FAILURE ........................................................................... 401 10.2.7 CELL UPDATE ....................................................................................................................................... 401 10.2.8 CELL UPDATE CONFIRM .................................................................................................................... 403 10.2.9 COUNTER CHECK ................................................................................................................................ 406
3GPP
Release 6
14
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.10 10.2.11 10.2.12 10.2.13 10.2.14 10.2.15 10.2.16 10.2.16a 10.2.16b 10.2.16c 10.2.16d 10.2.16e 10.2.16f 10.2.16g 10.2.16h 10.2.16i 10.2.16j 10.2.16k 10.2.16L 10.2.16m 10.2.17 10.2.18 10.2.19 10.2.20 10.2.21 10.2.22 10.2.23 10.2.24 10.2.25 10.2.26 10.2.27 10.2.28 10.2.29 10.2.30 10.2.31 10.2.32 10.2.33 10.2.34 10.2.35 10.2.36 10.2.37 10.2.38 10.2.39 10.2.40 10.2.41 10.2.41a 10.2.42 10.2.43 10.2.44 10.2.45 10.2.46 10.2.47 10.2.48 10.2.48.1 10.2.48.2 10.2.48.3 10.2.48.4 10.2.48.5 10.2.48.6 10.2.48.7 10.2.48.8 10.2.48.8.1
COUNTER CHECK RESPONSE............................................................................................................ 406 DOWNLINK DIRECT TRANSFER ....................................................................................................... 407 Void .......................................................................................................................................................... 407 Void .......................................................................................................................................................... 407 Void .......................................................................................................................................................... 408 HANDOVER FROM UTRAN COMMAND .......................................................................................... 408 HANDOVER FROM UTRAN FAILURE ............................................................................................... 410 HANDOVER TO UTRAN COMMAND ................................................................................................ 411 HANDOVER TO UTRAN COMPLETE ................................................................................................ 413 INITIAL DIRECT TRANSFER .............................................................................................................. 415 INTER RAT HANDOVER INFO ........................................................................................................... 416 MBMS ACCESS INFORMATION ......................................................................................................... 417 MBMS COMMON P-T-M RB INFORMATION.................................................................................... 417 MBMS CURRENT CELL P-T-M RB INFORMATION ........................................................................ 420 MBMS GENERAL INFORMATION ..................................................................................................... 422 MBMS MODIFICATION REQUEST ..................................................................................................... 423 MBMS MODIFIED SERVICES INFORMATION ................................................................................. 424 MBMS NEIGHBOURING CELL P-T-M RB INFORMATION............................................................. 426 MBMS SCHEDULING INFORMATION............................................................................................... 429 MBMS UNMODIFIED SERVICES INFORMATION ........................................................................... 430 MEASUREMENT CONTROL................................................................................................................ 430 MEASUREMENT CONTROL FAILURE .............................................................................................. 432 MEASUREMENT REPORT ................................................................................................................... 433 PAGING TYPE 1 ..................................................................................................................................... 433 PAGING TYPE 2 ..................................................................................................................................... 434 PHYSICAL CHANNEL RECONFIGURATION.................................................................................... 434 PHYSICAL CHANNEL RECONFIGURATION COMPLETE.............................................................. 436 PHYSICAL CHANNEL RECONFIGURATION FAILURE .................................................................. 437 PHYSICAL SHARED CHANNEL ALLOCATION ............................................................................... 438 PUSCH CAPACITY REQUEST ............................................................................................................. 439 RADIO BEARER RECONFIGURATION .............................................................................................. 440 RADIO BEARER RECONFIGURATION COMPLETE ........................................................................ 443 RADIO BEARER RECONFIGURATION FAILURE ............................................................................ 444 RADIO BEARER RELEASE .................................................................................................................. 445 RADIO BEARER RELEASE COMPLETE ............................................................................................ 448 RADIO BEARER RELEASE FAILURE ................................................................................................ 449 RADIO BEARER SETUP ....................................................................................................................... 450 RADIO BEARER SETUP COMPLETE ................................................................................................. 453 RADIO BEARER SETUP FAILURE...................................................................................................... 455 RRC CONNECTION REJECT ................................................................................................................ 455 RRC CONNECTION RELEASE ............................................................................................................ 456 RRC CONNECTION RELEASE COMPLETE ...................................................................................... 457 RRC CONNECTION REQUEST ............................................................................................................ 457 RRC CONNECTION SETUP .................................................................................................................. 459 RRC CONNECTION SETUP COMPLETE ............................................................................................ 462 RRC FAILURE INFO .............................................................................................................................. 462 RRC STATUS .......................................................................................................................................... 463 SECURITY MODE COMMAND ........................................................................................................... 463 SECURITY MODE COMPLETE............................................................................................................ 464 SECURITY MODE FAILURE ................................................................................................................ 465 SIGNALLING CONNECTION RELEASE ............................................................................................ 465 SIGNALLING CONNECTION RELEASE INDICATION .................................................................... 466 SYSTEM INFORMATION ..................................................................................................................... 466 First Segment ...................................................................................................................................... 468 First Segment (short) .......................................................................................................................... 468 Subsequent Segment ........................................................................................................................... 468 Last Segment ...................................................................................................................................... 469 Last Segment (short)........................................................................................................................... 469 Complete SIB ..................................................................................................................................... 469 Complete SIB (short) .......................................................................................................................... 470 System Information Blocks ................................................................................................................ 470 Master Information Block ............................................................................................................. 471
3GPP
Release 6
15
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.2 Scheduling Block 1 ....................................................................................................................... 471 10.2.48.8.3 Scheduling Block 2 ....................................................................................................................... 471 10.2.48.8.4 System Information Block type 1 ................................................................................................. 472 10.2.48.8.5 System Information Block type 2 ................................................................................................. 472 10.2.48.8.6 System Information Block type 3 ................................................................................................. 472 10.2.48.8.7 System Information Block type 4 ................................................................................................. 474 10.2.48.8.8 System Information Block type 5 and 5bis ................................................................................... 474 10.2.48.8.9 System Information Block type 6 ................................................................................................. 476 10.2.48.8.10 System Information Block type 7 ................................................................................................. 477 10.2.48.8.11 Void .............................................................................................................................................. 477 10.2.48.8.12 Void .............................................................................................................................................. 477 10.2.48.8.13 Void .............................................................................................................................................. 478 10.2.48.8.14 System Information Block type 11 ............................................................................................... 478 10.2.48.8.14a System Information Block type 11bis ........................................................................................... 478 10.2.48.8.15 System Information Block type 12 ............................................................................................... 478 10.2.48.8.16 System Information Block type 13 ............................................................................................... 478 10.2.48.8.16.1 System Information Block type 13.1 ....................................................................................... 479 10.2.48.8.16.2 System Information Block type 13.2 ....................................................................................... 479 10.2.48.8.16.3 System Information Block type 13.3 ....................................................................................... 479 10.2.48.8.16.4 System Information Block type 13.4 ....................................................................................... 480 10.2.48.8.17 System Information Block type 14 ............................................................................................... 480 10.2.48.8.18 System Information Block type 15 ............................................................................................... 480 10.2.48.8.18.1 System Information Block type 15.1 ....................................................................................... 481 10.2.48.8.18.2 System Information Block type 15.2 ....................................................................................... 481 10.2.48.8.18.3 System Information Block type 15.3 ....................................................................................... 481 10.2.48.8.18.4 System Information Block type 15.4 ....................................................................................... 482 10.2.48.8.19 System Information Block type 16 ............................................................................................... 483 10.2.48.8.20 System Information Block type 17 ............................................................................................... 483 10.2.48.8.21 System Information Block type 18 ............................................................................................... 484 10.2.49 SYSTEM INFORMATION CHANGE INDICATION ........................................................................... 484 10.2.50 TRANSPORT CHANNEL RECONFIGURATION ................................................................................ 484 10.2.51 TRANSPORT CHANNEL RECONFIGURATION COMPLETE .......................................................... 487 10.2.52 TRANSPORT CHANNEL RECONFIGURATION FAILURE .............................................................. 488 10.2.53 TRANSPORT FORMAT COMBINATION CONTROL ........................................................................ 488 10.2.54 TRANSPORT FORMAT COMBINATION CONTROL FAILURE ...................................................... 489 10.2.55 UE CAPABILITY ENQUIRY ................................................................................................................. 490 10.2.56 UE CAPABILITY INFORMATION ....................................................................................................... 490 10.2.57 UE CAPABILITY INFORMATION CONFIRM .................................................................................... 491 10.2.58 UPLINK DIRECT TRANSFER .............................................................................................................. 491 10.2.59 UPLINK PHYSICAL CHANNEL CONTROLtest ................................................................................. 492 10.2.60 URA UPDATE......................................................................................................................................... 493 10.2.61 URA UPDATE CONFIRM ..................................................................................................................... 494 10.2.62 UTRAN MOBILITY INFORMATION ................................................................................................... 495 10.2.63 UTRAN MOBILITY INFORMATION CONFIRM ................................................................................ 496 10.2.64 UTRAN MOBILITY INFORMATION FAILURE ................................................................................. 497 10.3 Information element functional definitions .................................................................................................... 498 10.3.1 CN Information elements ......................................................................................................................... 498 10.3.1.1 CN domain identity ............................................................................................................................ 498 10.3.1.2 CN Domain System Information ........................................................................................................ 498 10.3.1.3 CN Information info ........................................................................................................................... 499 10.3.1.3a CN Information info full..................................................................................................................... 499 10.3.1.3b Domain Specific Access Restriction .................................................................................................. 500 10.3.1.3c Domain Specific Access Restriction Parameters ................................................................................ 500 10.3.1.4 IMEI ................................................................................................................................................... 500 10.3.1.5 IMSI (GSM-MAP) ............................................................................................................................. 500 10.3.1.6 Intra Domain NAS Node Selector ...................................................................................................... 501 10.3.1.7 Location Area Identification ............................................................................................................... 502 10.3.1.7a Multiple PLMN List ........................................................................................................................... 503 10.3.1.8 NAS message...................................................................................................................................... 503 10.3.1.9 NAS system information (GSM-MAP) .............................................................................................. 503 10.3.1.10 Paging record type identifier .............................................................................................................. 503 10.3.1.11 PLMN identity .................................................................................................................................... 504
3GPP
Release 6
16
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.11a 10.3.1.12 10.3.1.13 10.3.1.14 10.3.1.15 10.3.1.16 10.3.1.17 10.3.2 10.3.2.1 10.3.2.2 10.3.2.3 10.3.2.4 10.3.2.5 10.3.2.6 10.3.3 10.3.3.1 10.3.3.2 10.3.3.3 10.3.3.4 10.3.3.5 10.3.3.6 10.3.3.7 10.3.3.8 10.3.3.9 10.3.3.9a 10.3.3.10 10.3.3.10a 10.3.3.11 10.3.3.12 10.3.3.13 10.3.3.14 10.3.3.14o 10.3.3.14a 10.3.3.15 10.3.3.16 10.3.3.17 10.3.3.18 10.3.3.19 10.3.3.19a 10.3.3.20 10.3.3.21 10.3.3.21a 10.3.3.22 10.3.3.23 10.3.3.24 10.3.3.25 10.3.3.26 10.3.3.27 10.3.3.28 10.3.3.29 10.3.3.30 10.3.3.31 10.3.3.32 10.3.3.32a 10.3.3.33 10.3.3.33a 10.3.3.33b 10.3.3.33c 10.3.3.34 10.3.3.35 10.3.3.35o 10.3.3.35a
PLMN identity with Optional MCC ................................................................................................... 504 PLMN Type ........................................................................................................................................ 504 P-TMSI (GSM-MAP) ......................................................................................................................... 504 RAB identity ....................................................................................................................................... 505 Routing Area Code ............................................................................................................................. 505 Routing Area Identification ................................................................................................................ 505 TMSI (GSM-MAP) ............................................................................................................................ 506 UTRAN mobility Information elements .................................................................................................. 506 Cell Access Restriction ....................................................................................................................... 506 Cell identity ........................................................................................................................................ 506 Cell selection and re-selection info for SIB3/4 ................................................................................... 507 Cell selection and re-selection info for SIB11/12 ............................................................................... 511 Mapping Info ..................................................................................................................................... 512 URA identity ...................................................................................................................................... 513 UE Information elements ......................................................................................................................... 514 Activation time ................................................................................................................................... 514 Capability Update Requirement ......................................................................................................... 514 Cell update cause ................................................................................................................................ 514 Ciphering Algorithm........................................................................................................................... 515 Ciphering mode info ........................................................................................................................... 515 CN domain specific DRX cycle length coefficient............................................................................. 515 Void .................................................................................................................................................... 515 C-RNTI ............................................................................................................................................... 516 Void .................................................................................................................................................... 516 DSCH-RNTI ....................................................................................................................................... 516 Void .................................................................................................................................................... 516 E-RNTI ............................................................................................................................................... 516 Establishment cause ............................................................................................................................ 517 Expiration Time Factor ....................................................................................................................... 518 Failure cause ....................................................................................................................................... 518 Failure cause and error information .................................................................................................... 518 Group release information .................................................................................................................. 519 H-RNTI .............................................................................................................................................. 519 Initial UE identity ............................................................................................................................... 519 Integrity check info ............................................................................................................................. 520 Integrity protection activation info ..................................................................................................... 520 Integrity protection Algorithm............................................................................................................ 521 Integrity protection mode info ............................................................................................................ 521 Void .................................................................................................................................................... 521 Void .................................................................................................................................................... 522 Measurement capability ...................................................................................................................... 522 Measurement capability extension ..................................................................................................... 524 Paging cause ....................................................................................................................................... 526 Paging record ...................................................................................................................................... 526 PDCP capability ................................................................................................................................. 528 Physical channel capability ................................................................................................................ 529 Protocol error cause ............................................................................................................................ 531 Protocol error indicator....................................................................................................................... 532 RB timer indicator .............................................................................................................................. 532 Redirection info .................................................................................................................................. 532 Re-establishment timer ....................................................................................................................... 533 Rejection cause ................................................................................................................................... 533 Release cause ...................................................................................................................................... 533 RF Capability Compressed ................................................................................................................. 534 RF capability FDD ............................................................................................................................. 534 RF capability FDD extension ............................................................................................................. 534 RF capability TDD ............................................................................................................................. 535 RF capability TDD 1.28 Mcps............................................................................................................ 535 RLC capability.................................................................................................................................... 535 RLC re-establish indicator .................................................................................................................. 535 RRC connection release information .................................................................................................. 535 RRC State Indicator ............................................................................................................................ 536
3GPP
Release 6
17
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.36 RRC transaction identifier .................................................................................................................. 536 10.3.3.37 Security capability .............................................................................................................................. 536 10.3.3.38 START ............................................................................................................................................... 537 10.3.3.39 Void .................................................................................................................................................... 537 10.3.3.40 Transport channel capability............................................................................................................... 537 10.3.3.41 UE multi-mode/multi-RAT capability ................................................................................................ 539 10.3.3.42 UE radio access capability .................................................................................................................. 539 10.3.3.42o UE radio access capability compressed .............................................................................................. 541 10.3.3.42oa UE radio access capability comp 2 ..................................................................................................... 542 10.3.3.42a UE radio access capability extension ................................................................................................. 542 10.3.3.42b UE security information ..................................................................................................................... 543 10.3.3.42c UE security information2 ................................................................................................................... 543 10.3.3.43 UE Timers and Constants in connected mode .................................................................................... 543 10.3.3.44 UE Timers and Constants in idle mode .............................................................................................. 545 10.3.3.45 UE positioning capability ................................................................................................................... 546 10.3.3.46 URA update cause .............................................................................................................................. 546 10.3.3.47 U-RNTI .............................................................................................................................................. 546 10.3.3.47a U-RNTI group .................................................................................................................................... 547 10.3.3.48 U-RNTI Short ..................................................................................................................................... 547 10.3.3.49 UTRAN DRX cycle length coefficient ............................................................................................... 547 10.3.3.50 Wait time ............................................................................................................................................ 547 10.3.3.51 UE Specific Behaviour Information 1 idle ......................................................................................... 548 10.3.3.52 UE Specific Behaviour Information 1 interRAT ................................................................................ 548 10.3.4 Radio Bearer Information elements ......................................................................................................... 548 10.3.4.0 Default configuration identity............................................................................................................. 548 10.3.4.1 Downlink RLC STATUS info ............................................................................................................ 548 10.3.4.1a PDCP context relocation info ............................................................................................................. 549 10.3.4.2 PDCP info ........................................................................................................................................... 549 10.3.4.2a PDCP ROHC target mode .................................................................................................................. 551 10.3.4.3 PDCP SN info..................................................................................................................................... 551 10.3.4.4 Polling info ......................................................................................................................................... 552 10.3.4.5 Predefined configuration identity ....................................................................................................... 552 10.3.4.5a Predefined configuration status information....................................................................................... 552 10.3.4.5b Predefined configuration status information compressed ................................................................... 553 10.3.4.6 Predefined configuration value tag ..................................................................................................... 553 10.3.4.7 Predefined RB configuration .............................................................................................................. 554 10.3.4.8 RAB info ............................................................................................................................................ 554 10.3.4.9 RAB info Post..................................................................................................................................... 555 10.3.4.10 RAB information for setup ................................................................................................................. 555 10.3.4.11 RAB information to reconfigure ......................................................................................................... 555 10.3.4.11a RAB information for MBMS ptp bearers ........................................................................................... 556 10.3.4.12 NAS Synchronization indicator .......................................................................................................... 556 10.3.4.13 RB activation time info....................................................................................................................... 556 10.3.4.14 RB COUNT-C MSB information ....................................................................................................... 556 10.3.4.15 RB COUNT-C information ................................................................................................................ 556 10.3.4.16 RB identity ......................................................................................................................................... 557 10.3.4.17 RB information to be affected ............................................................................................................ 557 10.3.4.18 RB information to reconfigure............................................................................................................ 557 10.3.4.19 RB information to release ................................................................................................................... 557 10.3.4.20 RB information to setup ..................................................................................................................... 558 10.3.4.21 RB mapping info ................................................................................................................................ 558 10.3.4.22 RB with PDCP information ................................................................................................................ 561 10.3.4.23 RLC info ............................................................................................................................................. 561 10.3.4.23a RLC info MBMS ................................................................................................................................ 563 10.3.4.24 Signalling RB information to setup .................................................................................................... 564 10.3.4.25 Transmission RLC Discard ................................................................................................................ 564 10.3.4.26 UM Duplication Avoidance and Reordering info .............................................................................. 565 10.3.4.27 UM Out of sequence delivery info .................................................................................................... 565 10.3.5 Transport CH Information elements ......................................................................................................... 566 10.3.5.1 Added or Reconfigured DL TrCH information .................................................................................. 566 10.3.5.1a Added or reconfigured MAC-d flow .................................................................................................. 567 10.3.5.1b Added or reconfigured E-DCH MAC-d flow ..................................................................................... 567
3GPP
Release 6
18
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.2 Added or Reconfigured UL TrCH information .................................................................................. 569 10.3.5.2a Additional Dynamic Transport Format Information for CCCH ......................................................... 569 10.3.5.2b Additional RACH TFCS for CCCH ................................................................................................... 570 10.3.5.3 Void .................................................................................................................................................... 570 10.3.5.4 Deleted DL TrCH information ........................................................................................................... 570 10.3.5.5 Deleted UL TrCH information ........................................................................................................... 570 10.3.5.6 DL Transport channel information common for all transport channels .............................................. 571 10.3.5.7 Void .................................................................................................................................................... 572 10.3.5.7a HARQ Info ......................................................................................................................................... 572 10.3.5.7b Void .................................................................................................................................................... 572 10.3.5.7c MAC-d Flow Identity ......................................................................................................................... 572 10.3.5.7d HARQ Info for E-DCH ...................................................................................................................... 572 10.3.5.7e E-DCH MAC-d Flow Identity ............................................................................................................ 573 10.3.5.8 Power Offset Information ................................................................................................................... 573 10.3.5.9 Predefined TrCH configuration .......................................................................................................... 574 10.3.5.10 Quality Target ..................................................................................................................................... 574 10.3.5.11 Semi-static Transport Format Information ......................................................................................... 575 10.3.5.12 Void .................................................................................................................................................... 575 10.3.5.13 TFCS Explicit Configuration .............................................................................................................. 576 10.3.5.14 Void .................................................................................................................................................... 576 10.3.5.15 TFCS Reconfiguration/Addition Information .................................................................................... 577 10.3.5.16 TFCS Removal Information ............................................................................................................... 578 10.3.5.17 Void .................................................................................................................................................... 578 10.3.5.18 Transport channel identity .................................................................................................................. 578 10.3.5.19 Transport Format Combination (TFC) ............................................................................................... 578 10.3.5.20 Transport Format Combination Set .................................................................................................... 578 10.3.5.21 Transport Format Combination Set Identity ....................................................................................... 578 10.3.5.22 Transport Format Combination Subset ............................................................................................... 579 10.3.5.23 Transport Format Set .......................................................................................................................... 579 10.3.5.24 UL Transport channel information common for all transport channels .............................................. 581 10.3.6 Physical CH Information elements........................................................................................................... 582 10.3.6.1 AC-to-ASC mapping .......................................................................................................................... 582 10.3.6.2 AICH Info ........................................................................................................................................... 583 10.3.6.3 AICH Power offset ............................................................................................................................. 583 10.3.6.4 Allocation period info ......................................................................................................................... 583 10.3.6.5 Alpha .................................................................................................................................................. 583 10.3.6.6 ASC setting ......................................................................................................................................... 583 10.3.6.7 Void .................................................................................................................................................... 585 10.3.6.8 CCTrCH power control info ............................................................................................................... 585 10.3.6.8a Cell and Channel Identity info ............................................................................................................ 585 10.3.6.9 Cell parameters Id ............................................................................................................................... 586 10.3.6.10 Common timeslot info ........................................................................................................................ 586 10.3.6.10a Common timeslot info MBMS ........................................................................................................... 587 10.3.6.11 Constant value .................................................................................................................................... 587 10.3.6.11a Constant value TDD ........................................................................................................................... 587 10.3.6.12 Void .................................................................................................................................................... 587 10.3.6.13 Void .................................................................................................................................................... 587 10.3.6.14 Void .................................................................................................................................................... 587 10.3.6.15 Void .................................................................................................................................................... 588 10.3.6.16 Default DPCH Offset Value ............................................................................................................... 588 10.3.6.17 Downlink channelisation codes .......................................................................................................... 588 10.3.6.18 Downlink DPCH info common for all RL.......................................................................................... 588 10.3.6.19 Downlink DPCH info common for all RL Post .................................................................................. 590 10.3.6.20 Downlink DPCH info common for all RL Pre ................................................................................... 590 10.3.6.21 Downlink DPCH info for each RL ..................................................................................................... 591 10.3.6.22 Downlink DPCH info for each RL Post ............................................................................................. 592 10.3.6.23 Downlink DPCH power control information...................................................................................... 593 10.3.6.23oa Downlink F-DPCH info common for all RL ...................................................................................... 593 10.3.6.23ob Downlink F-DPCH info for each RL.................................................................................................. 594 10.3.6.23a Downlink HS-PDSCH Information .................................................................................................... 595 10.3.6.24 Downlink information common for all radio links ............................................................................. 595 10.3.6.25 Downlink information common for all radio links Post ..................................................................... 596
3GPP
Release 6
19
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.26 10.3.6.27 10.3.6.28 10.3.6.29 10.3.6.30 10.3.6.31 10.3.6.32 10.3.6.33 10.3.6.34 10.3.6.35 10.3.6.35a 10.3.6.35b 10.3.6.35c 10.3.6.36 10.3.6.36oo 10.3.6.36o 10.3.6.36a 10.3.6.36b 10.3.6.37 10.3.6.38 10.3.6.39 10.3.6.40 10.3.6.40a 10.3.6.41 10.3.6.42 10.3.6.43 10.3.6.44 10.3.6.45 10.3.6.46 10.3.6.47 10.3.6.48 10.3.6.49 10.3.6.50 10.3.6.51 10.3.6.51a 10.3.6.52 10.3.6.53 10.3.6.54 10.3.6.55 10.3.6.56 10.3.6.57 10.3.6.58 10.3.6.59 10.3.6.60 10.3.6.61 10.3.6.62 10.3.6.63 10.3.6.64 10.3.6.65 10.3.6.66 10.3.6.67 10.3.6.68 10.3.6.69 10.3.6.69a 10.3.6.70 10.3.6.70a 10.3.6.71 10.3.6.71a 10.3.6.72 10.3.6.72a 10.3.6.73 10.3.6.74
Downlink information common for all radio links Pre ....................................................................... 596 Downlink information for each radio link .......................................................................................... 597 Downlink information for each radio link Post .................................................................................. 597 Void .................................................................................................................................................... 598 Void .................................................................................................................................................... 598 Downlink rate matching restriction information................................................................................. 598 Downlink Timeslots and Codes .......................................................................................................... 598 DPCH compressed mode info ............................................................................................................ 599 DPCH Compressed Mode Status Info ................................................................................................ 602 Dynamic persistence level .................................................................................................................. 603 FPACH info ........................................................................................................................................ 603 Frequency band indicator ................................................................................................................... 603 Frequency band indicator 2 ................................................................................................................ 603 Frequency info .................................................................................................................................... 604 HS-PDSCH Midamble Configuration ................................................................................................ 604 HS-PDSCH Timeslot Configuration .................................................................................................. 604 HS-SCCH Info.................................................................................................................................... 606 HS-SICH Power Control Info ............................................................................................................. 608 Individual timeslot info ...................................................................................................................... 609 Individual Timeslot interference......................................................................................................... 609 Maximum allowed UL TX power ...................................................................................................... 609 Void .................................................................................................................................................... 610 Measurement Feedback Info............................................................................................................... 610 Midamble shift and burst type ............................................................................................................ 610 PDSCH Capacity Allocation info ....................................................................................................... 611 Void .................................................................................................................................................... 612 PDSCH info ........................................................................................................................................ 612 PDSCH Power Control info ............................................................................................................... 612 PDSCH system information ............................................................................................................... 612 Void .................................................................................................................................................... 613 Persistence scaling factors .................................................................................................................. 613 PICH Info ........................................................................................................................................... 613 PICH Power offset .............................................................................................................................. 614 PRACH Channelisation Code List ..................................................................................................... 615 PRACH Channelisation Code 1.28 Mcps TDD.................................................................................. 615 PRACH info (for RACH) ................................................................................................................... 615 PRACH partitioning ........................................................................................................................... 617 PRACH power offset .......................................................................................................................... 617 PRACH system information list ......................................................................................................... 617 Predefined PhyCH configuration ........................................................................................................ 619 Primary CCPCH info .......................................................................................................................... 619 Primary CCPCH info post .................................................................................................................. 620 Primary CCPCH TX Power ................................................................................................................ 620 Primary CPICH info ........................................................................................................................... 620 Primary CPICH Tx power .................................................................................................................. 620 Primary CPICH usage for channel estimation .................................................................................... 621 PUSCH info ........................................................................................................................................ 621 PUSCH Capacity Allocation info ....................................................................................................... 621 PUSCH power control info ................................................................................................................. 621 PUSCH system information ............................................................................................................... 622 RACH transmission parameters ......................................................................................................... 623 Radio link addition information.......................................................................................................... 623 Radio link removal information.......................................................................................................... 624 E-DCH reconfiguration information ................................................................................................... 624 Void .................................................................................................................................................... 626 SCTD indicator ................................................................................................................................... 626 Secondary CCPCH info ...................................................................................................................... 627 Secondary CCPCH info MBMS ......................................................................................................... 628 Secondary CCPCH system information ............................................................................................. 629 Secondary CCPCH system information MBMS ................................................................................ 630 Secondary CPICH info ....................................................................................................................... 630 Secondary scrambling code ................................................................................................................ 630
3GPP
Release 6
20
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.74a 10.3.6.75 10.3.6.75a 10.3.6.76 10.3.6.77 10.3.6.78 10.3.6.78a 10.3.6.79 10.3.6.80 10.3.6.81 10.3.6.82 10.3.6.83 10.3.6.84 10.3.6.85 10.3.6.85a 10.3.6.86 10.3.6.87 10.3.6.87a 10.3.6.88 10.3.6.89 10.3.6.90 10.3.6.91 10.3.6.92 10.3.6.93 10.3.6.94 10.3.6.95 10.3.6.96 10.3.6.97 10.3.6.98 10.3.6.99 10.3.6.100 10.3.6.101 10.3.6.102 10.3.7 10.3.7.1 10.3.7.2 10.3.7.3 10.3.7.4 10.3.7.5 10.3.7.6 10.3.7.7 10.3.7.8 10.3.7.9 10.3.7.10 10.3.7.11 10.3.7.12 10.3.7.13 10.3.7.14 10.3.7.15 10.3.7.16 10.3.7.17 10.3.7.18 10.3.7.19 10.3.7.20 10.3.7.20a 10.3.7.21 10.3.7.22 10.3.7.23 10.3.7.24 10.3.7.25 10.3.7.26 10.3.7.27
Serving HS-DSCH cell information ................................................................................................... 631 SFN Time info .................................................................................................................................... 631 Special Burst Scheduling .................................................................................................................... 631 Void .................................................................................................................................................... 631 Void .................................................................................................................................................... 631 STTD indicator ................................................................................................................................... 631 SYNC_UL info ................................................................................................................................... 632 TDD open loop power control ............................................................................................................ 632 TFC Control duration ......................................................................................................................... 633 Void .................................................................................................................................................... 633 TGPSI ................................................................................................................................................. 633 Time info ............................................................................................................................................ 633 Timeslot number ................................................................................................................................. 633 TPC combination index ...................................................................................................................... 634 TSTD indicator ................................................................................................................................... 634 TX Diversity Mode............................................................................................................................. 634 UL interference ................................................................................................................................... 634 UL interference TDD.......................................................................................................................... 635 Uplink DPCH info .............................................................................................................................. 636 Uplink DPCH info Post ...................................................................................................................... 637 Uplink DPCH info Pre........................................................................................................................ 637 Uplink DPCH power control info ....................................................................................................... 638 Uplink DPCH power control info Post ............................................................................................... 639 Uplink DPCH power control info Pre ................................................................................................ 640 Uplink Timeslots and Codes............................................................................................................... 640 Uplink Timing Advance ..................................................................................................................... 641 Uplink Timing Advance Control ........................................................................................................ 641 E-DCH Info ........................................................................................................................................ 644 E-DPCCH Info ................................................................................................................................... 645 E-DPDCH Info ................................................................................................................................... 646 E-AGCH Info ..................................................................................................................................... 647 E-HICH Info ....................................................................................................................................... 647 E-RGCH Info...................................................................................................................................... 647 Measurement Information elements ......................................................................................................... 648 Additional measurements list ............................................................................................................. 648 Cell info .............................................................................................................................................. 648 Cell measured results .......................................................................................................................... 649 Cell measurement event results .......................................................................................................... 650 Cell reporting quantities ..................................................................................................................... 650 Cell synchronisation information ....................................................................................................... 651 Event results ....................................................................................................................................... 651 FACH measurement occasion info ..................................................................................................... 652 Filter coefficient ................................................................................................................................. 653 HCS Cell re-selection information ..................................................................................................... 653 HCS neighbouring cell information.................................................................................................... 653 HCS Serving cell information ............................................................................................................ 654 Inter-frequency cell info list ............................................................................................................... 654 Inter-frequency event identity............................................................................................................. 655 Inter-frequency measured results list .................................................................................................. 655 Inter-frequency measurement ............................................................................................................. 655 Inter-frequency measurement event results ........................................................................................ 656 Inter-frequency measurement quantity ............................................................................................... 656 Inter-frequency measurement reporting criteria ................................................................................. 657 Inter-frequency measurement system information ............................................................................. 660 Inter-frequency RACH reporting information .................................................................................... 660 Inter-frequency reporting quantity ...................................................................................................... 660 Inter-frequency SET UPDATE........................................................................................................... 661 Inter-RAT cell info list ....................................................................................................................... 661 Inter-RAT event identity .................................................................................................................... 662 Inter-RAT info .................................................................................................................................... 662 Inter-RAT measured results list .......................................................................................................... 663 Inter-RAT measurement ..................................................................................................................... 664
3GPP
Release 6
21
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.28 10.3.7.29 10.3.7.30 10.3.7.31 10.3.7.32 10.3.7.33 10.3.7.34 10.3.7.35 10.3.7.36 10.3.7.37 10.3.7.38 10.3.7.39 10.3.7.40 10.3.7.41 10.3.7.42 10.3.7.43 10.3.7.43a 10.3.7.44 10.3.7.45 10.3.7.46 10.3.7.47 10.3.7.47a 10.3.7.48 10.3.7.49 10.3.7.50 10.3.7.51 10.3.7.52 10.3.7.53 10.3.7.53aa 10.3.7.53a 10.3.7.54 10.3.7.54a 10.3.7.55 10.3.7.56 10.3.7.57 10.3.7.58 10.3.7.59 10.3.7.60 10.3.7.61 10.3.7.62 10.3.7.63 10.3.7.64 10.3.7.65 10.3.7.66 10.3.7.67 10.3.7.68 10.3.7.69 10.3.7.70 10.3.7.71 10.3.7.72 10.3.7.73 10.3.7.74 10.3.7.75 10.3.7.76 10.3.7.77 10.3.7.78 10.3.7.79 10.3.7.80 10.3.7.81 10.3.7.82 10.3.7.83 10.3.7.84
Inter-RAT measurement event results ................................................................................................ 664 Inter-RAT measurement quantity ....................................................................................................... 665 Inter-RAT measurement reporting criteria ......................................................................................... 665 Inter-RAT measurement system information ..................................................................................... 666 Inter-RAT reporting quantity .............................................................................................................. 666 Intra-frequency cell info list ............................................................................................................... 666 Intra-frequency event identity............................................................................................................. 667 Intra-frequency measured results list .................................................................................................. 668 Intra-frequency measurement ............................................................................................................. 668 Intra-frequency measurement event results ........................................................................................ 669 Intra-frequency measurement quantity ............................................................................................... 669 Intra-frequency measurement reporting criteria ................................................................................. 669 Intra-frequency measurement system information ............................................................................. 673 Intra-frequency reporting quantity ...................................................................................................... 673 Intra-frequency reporting quantity for RACH reporting .................................................................... 673 Maximum number of reported cells on RACH................................................................................... 674 MBMS preferred frequency information ............................................................................................ 675 Measured results ................................................................................................................................. 675 Measured results on RACH ................................................................................................................ 676 Measurement Command ..................................................................................................................... 678 Measurement control system information .......................................................................................... 678 Measurement control system information extension .......................................................................... 679 Measurement Identity ......................................................................................................................... 680 Measurement reporting mode ............................................................................................................. 680 Measurement Type ............................................................................................................................. 680 Measurement validity ......................................................................................................................... 681 Void .................................................................................................................................................... 681 Periodical reporting criteria ................................................................................................................ 681 Periodical reporting info-1b ................................................................................................................ 681 PLMN identities of neighbour cells .................................................................................................... 681 Primary CCPCH RSCP info ............................................................................................................... 682 Qhcs .................................................................................................................................................... 682 Quality measured results list ............................................................................................................... 684 Quality measurement .......................................................................................................................... 685 Quality measurement event results ..................................................................................................... 685 Quality measurement reporting criteria .............................................................................................. 685 Quality reporting quantity .................................................................................................................. 686 Reference time difference to cell ........................................................................................................ 686 Reporting Cell Status .......................................................................................................................... 686 Reporting information for state CELL_DCH ..................................................................................... 689 SFN-SFN observed time difference.................................................................................................... 689 Time to trigger .................................................................................................................................... 689 Timeslot ISCP info ............................................................................................................................. 689 Traffic volume event identity ............................................................................................................. 690 Traffic volume measured results list ................................................................................................... 690 Traffic volume measurement .............................................................................................................. 691 Traffic volume measurement event results ......................................................................................... 691 Traffic volume measurement object ................................................................................................... 692 Traffic volume measurement quantity ................................................................................................ 692 Traffic volume measurement reporting criteria .................................................................................. 693 Traffic volume measurement system information .............................................................................. 694 Traffic volume reporting quantity ...................................................................................................... 694 UE internal event identity ................................................................................................................... 694 UE internal measured results .............................................................................................................. 695 UE internal measurement ................................................................................................................... 696 UE internal measurement event results .............................................................................................. 696 UE internal measurement quantity ..................................................................................................... 696 UE internal measurement reporting criteria........................................................................................ 697 Void .................................................................................................................................................... 698 UE Internal reporting quantity ............................................................................................................ 698 UE Rx-Tx time difference type 1 ....................................................................................................... 698 UE Rx-Tx time difference type 2 ....................................................................................................... 699
3GPP
Release 6
22
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.85 UE Transmitted Power info ................................................................................................................ 699 10.3.7.86 UE positioning Ciphering info............................................................................................................ 699 10.3.7.87 UE positioning Error .......................................................................................................................... 700 10.3.7.88 UE positioning GPS acquisition assistance ........................................................................................ 700 10.3.7.88a UE positioning GPS Additional Assistance Data Request ................................................................. 702 10.3.7.89 UE positioning GPS almanac ............................................................................................................. 703 10.3.7.90 UE positioning GPS assistance data ................................................................................................... 703 10.3.7.90a Void .................................................................................................................................................... 704 10.3.7.91 UE positioning GPS DGPS corrections .............................................................................................. 704 10.3.7.91a UE positioning GPS Ephemeris and Clock Correction parameters .................................................... 705 10.3.7.92 UE positioning GPS ionospheric model ............................................................................................. 707 10.3.7.93 UE positioning GPS measured results ................................................................................................ 707 10.3.7.94 UE positioning GPS navigation model ............................................................................................... 708 10.3.7.95 UE positioning GPS real-time integrity .............................................................................................. 709 10.3.7.95a Void .................................................................................................................................................... 709 10.3.7.96 UE positioning GPS reference time .................................................................................................... 709 10.3.7.97 UE positioning GPS UTC model........................................................................................................ 710 10.3.7.98 UE positioning IPDL parameters........................................................................................................ 710 10.3.7.99 UE positioning measured results ........................................................................................................ 711 10.3.7.100 UE positioning measurement .............................................................................................................. 711 10.3.7.101 UE positioning measurement event results ......................................................................................... 712 10.3.7.102 Void .................................................................................................................................................... 712 10.3.7.103 UE positioning OTDOA assistance data for UE-assisted ................................................................... 713 10.3.7.103a UE positioning OTDOA assistance data for UE-based ...................................................................... 713 10.3.7.104 Void .................................................................................................................................................... 713 10.3.7.105 UE positioning OTDOA measured results ......................................................................................... 713 10.3.7.106 UE positioning OTDOA neighbour cell info ...................................................................................... 714 10.3.7.106a UE positioning OTDOA neighbour cell info for UE-based ............................................................... 716 10.3.7.107 UE positioning OTDOA quality ......................................................................................................... 716 10.3.7.108 UE positioning OTDOA reference cell info ....................................................................................... 717 10.3.7.108a UE positioning OTDOA reference cell info for UE-based ................................................................. 718 10.3.7.109 UE positioning position estimate info ................................................................................................ 719 10.3.7.109a UE positioning Relative Time Difference quality .............................................................................. 720 10.3.7.110 UE positioning reporting criteria ........................................................................................................ 720 10.3.7.111 UE positioning reporting quantity ...................................................................................................... 721 10.3.7.112 TADV info ......................................................................................................................................... 722 10.3.8 Other Information elements ..................................................................................................................... 723 10.3.8.1 BCCH modification info .................................................................................................................... 723 10.3.8.2 BSIC ................................................................................................................................................... 723 10.3.8.3 CBS DRX Level 1 information .......................................................................................................... 723 10.3.8.4 Cell Value tag ..................................................................................................................................... 723 10.3.8.4a Ellipsoid point .................................................................................................................................... 724 10.3.8.4b Ellipsoid point with Altitude .............................................................................................................. 724 10.3.8.4c Ellipsoid point with Altitude and uncertainty ellipsoid ...................................................................... 724 10.3.8.4d Ellipsoid point with uncertainty Circle ............................................................................................... 725 10.3.8.4e Ellipsoid point with uncertainty Ellipse.............................................................................................. 726 10.3.8.4f GERAN system information .............................................................................................................. 726 10.3.8.4g GSM Target Cell Info ......................................................................................................................... 726 10.3.8.5 Inter-RAT change failure.................................................................................................................... 727 10.3.8.6 Inter-RAT handover failure ................................................................................................................ 727 10.3.8.7 Inter-RAT UE radio access capability ................................................................................................ 728 10.3.8.8 Void .................................................................................................................................................... 729 10.3.8.8a Inter-RAT UE security capability ....................................................................................................... 729 10.3.8.9 MIB Value tag .................................................................................................................................... 729 10.3.8.10 PLMN Value tag................................................................................................................................. 729 10.3.8.10a PNBSCH allocation ............................................................................................................................ 729 10.3.8.11 Predefined configuration identity and value tag ................................................................................. 730 10.3.8.12 Protocol error information .................................................................................................................. 730 10.3.8.13 References to other system information blocks .................................................................................. 730 10.3.8.14 References to other system information blocks and scheduling blocks .............................................. 731 10.3.8.15 Rplmn information ............................................................................................................................. 731
3GPP
Release 6
23
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8.16 10.3.8.17 10.3.8.18 10.3.8.18a 10.3.8.18b 10.3.8.19 10.3.8.20 10.3.8.20a 10.3.8.20b 10.3.8.20c 10.3.8.21 10.3.8.22 10.3.9 10.3.9.1 10.3.9.2 10.3.9.3 10.3.9.4 10.3.9.5 10.3.9.6 10.3.9.7 10.3.9.8 10.3.9.9 10.3.9.10 10.3.9.11 10.3.9a 10.3.9a.1 10.3.9a.2 10.3.9a.3 10.3.9a.4 10.3.9a.5 10.3.9a.6 10.3.9a.7 10.3.9a.7o 10.3.9a.7a 10.3.9a.7b 10.3.9a.7c 10.3.9a.7d 10.3.9a.8 10.3.9a.8a 10.3.9a.9 10.3.9a.10 10.3.9a.10a 10.3.9a.11 10.3.9a.12 10.3.9a.13 10.3.9a.14 10.3.9a.15 10.3.9a.16 10.3.10
Scheduling information ...................................................................................................................... 732 SEG COUNT ...................................................................................................................................... 733 Segment index .................................................................................................................................... 733 SIB and SB type ................................................................................................................................. 733 SIB type extension .............................................................................................................................. 734 SIB data fixed ..................................................................................................................................... 734 SIB data variable ................................................................................................................................ 734 SIB occurrence identity ...................................................................................................................... 735 SIB occurrence identity and value tag ................................................................................................ 735 SIB occurrence value tag .................................................................................................................... 735 SIB type .............................................................................................................................................. 735 SIB type SIBs only ............................................................................................................................. 736 ANSI-41 Information elements ................................................................................................................ 737 ANSI-41 Core Network Information .................................................................................................. 737 ANSI-41 Global Service Redirection information ............................................................................. 737 ANSI-41 NAS parameter.................................................................................................................... 737 ANSI-41 NAS system information ..................................................................................................... 738 ANSI-41 Private Neighbour List information .................................................................................... 738 ANSI-41 RAND information ............................................................................................................. 738 ANSI-41 User Zone Identification information .................................................................................. 738 MIN_P_REV ...................................................................................................................................... 738 NID ..................................................................................................................................................... 739 P_REV ................................................................................................................................................ 739 SID...................................................................................................................................................... 739 MBMS Information elements ................................................................................................................... 739 MBMS Common CCTrCH identity.................................................................................................... 739 MBMS Common PhyCh identity ....................................................................................................... 740 MBMS Common RB identity ............................................................................................................. 740 MBMS Common TrCh identity .......................................................................................................... 740 MBMS Current cell S-CCPCH identity ............................................................................................. 740 Void .................................................................................................................................................... 740 MBMS L1 combining schedule .......................................................................................................... 741 MBMS p-t-m activation time ............................................................................................................. 741 MBMS p-t-m RB information ............................................................................................................ 742 MBMS Selected Service Info ............................................................................................................. 742 MBMS Selected Services Full ............................................................................................................ 743 MBMS Selected Services Short.......................................................................................................... 743 MBMS Service identity ...................................................................................................................... 744 MBMS Service ID ............................................................................................................................. 744 MBMS Session identity ...................................................................................................................... 745 MBMS Short transmission identity .................................................................................................... 745 MBMS Soft Combining Timing Offset .............................................................................................. 745 MBMS specific timers and counters................................................................................................... 746 MBMS Transmission identity ............................................................................................................ 746 MCCH configuration information ...................................................................................................... 746 MICH configuration information ....................................................................................................... 748 MICH Power offset ........................................................................................................................... 748 MSCH configuration information....................................................................................................... 749 Multiplicity values and type constraint values ......................................................................................... 749
11
11.0 11.1 11.2 11.3 11.4 11.5
Message and Information element abstract syntax (with ASN.1) ........................................................ 752
General........................................................................................................................................................... 753 General message structure ............................................................................................................................. 753 PDU definitions ............................................................................................................................................. 757 Information element definitions ..................................................................................................................... 832 Constant definitions ....................................................................................................................................... 991 RRC information between network nodes ..................................................................................................... 993
12
12.1 12.1.1 12.1.2
Message transfer syntax ..................................................................................................................... 1010

Structure of encoded RRC messages ........................................................................................................... 1010 Basic production..................................................................................................................................... 1010 Extension ................................................................................................................................................ 1010
3GPP
Release 6
24
3GPP TS 25.331 V6.23.0 (2009-09)
12.1.3 Padding................................................................................................................................................... 1010 12.2 ECN link module for RRC........................................................................................................................... 1013 12.3 ECN modules for RRC ................................................................................................................................ 1014 12.4 RRC messages encoded otherwise............................................................................................................... 1014 12.4.1 Messages using tabular encoding specification ...................................................................................... 1014 12.4.1.1 TRANSPORT FORMAT COMBINATION CONTROL using transparent DCCH ........................ 1015 12.4.1.1.1 TRANSPORT FORMAT COMBINATION CONTROL, 3 bit format ...................................... 1015 12.4.1.1.2 Void ............................................................................................................................................ 1015 12.4.1.1.3 Void ............................................................................................................................................ 1015
13
Protocol timers, counters, other parameters and default configurations ............................................ 1016
Timers for UE .............................................................................................................................................. 1016 Counters for UE ........................................................................................................................................... 1017 UE constants and parameters ....................................................................................................................... 1018 UE variables................................................................................................................................................. 1018 AM_RLC_ERROR_PENDING_RB234................................................................................................ 1018 AM_RLC_ERROR_PENDING_RB5_AND_UP .................................................................................. 1018 CELL_INFO_LIST ................................................................................................................................ 1018 Void ........................................................................................................................................................ 1019 CELL_UPDATE_STARTED ................................................................................................................ 1019 CIPHERING_STATUS ......................................................................................................................... 1020 Void ........................................................................................................................................................ 1020 CONFIGURATION_INCOMPLETE .................................................................................................... 1020 C_RNTI .................................................................................................................................................. 1020 DSAC_PARAM ..................................................................................................................................... 1021 DSCH_RNTI .......................................................................................................................................... 1021 Void ........................................................................................................................................................ 1021 E_DCH_TRANSMISSION ................................................................................................................... 1021 E_RNTI .................................................................................................................................................. 1022 ESTABLISHED_RABS......................................................................................................................... 1022 ESTABLISHED_SIGNALLING_CONNECTIONS ............................................................................. 1023 ESTABLISHMENT_CAUSE ................................................................................................................ 1023 FAILURE_CAUSE ................................................................................................................................ 1023 FAILURE_INDICATOR ....................................................................................................................... 1023 H_RNTI ................................................................................................................................................. 1024 HS_DSCH_RECEPTION ...................................................................................................................... 1024 INCOMPATIBLE_SECURITY_RECONFIGURATION ..................................................................... 1024 INITIAL_UE_IDENTITY ..................................................................................................................... 1025 INTEGRITY_PROTECTION_ACTIVATION_INFO .......................................................................... 1025 INTEGRITY_PROTECTION_INFO .................................................................................................... 1025 INTER_RAT_HANDOVER_INFO_TRANSFERRED ........................................................................ 1026 INVALID_CONFIGURATION ............................................................................................................ 1028 LATEST_CONFIGURED_CN_DOMAIN ........................................................................................... 1028 LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE .................................................... 1028 MBMS_ACTIVATED_SERVICES ...................................................................................................... 1028 MBMS_PREV_FREQUENCY_INFO................................................................................................... 1029 MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED .......................................................... 1029 MEASUREMENT_IDENTITY ............................................................................................................. 1029 Void ........................................................................................................................................................ 1030 ORDERED_RECONFIGURATION ..................................................................................................... 1030 PDCP_ROHC_TARGET_MODE ......................................................................................................... 1030 PDCP_SN_INFO ................................................................................................................................... 1030 PHYSICAL_SHARED_CHANNEL_CONFIGURATION ................................................................... 1031 PROTOCOL_ERROR_INDICATOR.................................................................................................... 1031 PROTOCOL_ERROR_INFORMATION.............................................................................................. 1032 PROTOCOL_ERROR_REJECT ........................................................................................................... 1032 RB_TIMER_INDICATOR .................................................................................................................... 1032 RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO ................................................................. 1032 SECURITY_MODIFICATION ............................................................................................................. 1032 Void ........................................................................................................................................................ 1033 START_THRESHOLD ......................................................................................................................... 1033 START_VALUE_TO_TRANSMIT ...................................................................................................... 1033
13.1 13.2 13.3 13.4 13.4.ob 13.4.oc 13.4.0 13.4.00 13.4.0a 13.4.1 13.4.2 13.4.2a 13.4.3 13.4.3o 13.4.3a 13.4.4 13.4.4o 13.4.4a 13.4.5 13.4.5a 13.4.6 13.4.7 13.4.8 13.4.8o 13.4.8oo 13.4.8a 13.4.9 13.4.9a 13.4.10 13.4.10a 13.4.11 13.4.11a 13.4.11b 13.4.11c 13.4.11d 13.4.11e 13.4.12 13.4.13 13.4.14 13.4.14a 13.4.15 13.4.15a 13.4.16 13.4.17 13.4.18 13.4.19 13.4.20 13.4.20a 13.4.21 13.4.22 13.4.23
3GPP
Release 6
25
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.24 TFC_SUBSET........................................................................................................................................ 1033 13.4.25 TGPS_IDENTITY ................................................................................................................................. 1035 13.4.26 TGSN_REPORTED ............................................................................................................................... 1035 13.4.26a TIMERS_AND_CONSTANTS ............................................................................................................. 1036 13.4.27 TRANSACTIONS ................................................................................................................................. 1036 13.4.27a TRIGGERED_1A_EVENT ................................................................................................................... 1036 13.4.27b TRIGGERED_1B_EVENT ................................................................................................................... 1037 13.4.27c TRIGGERED_1C_EVENT ................................................................................................................... 1038 13.4.27d BEST_CELL_1D_EVENT .................................................................................................................... 1038 13.4.27e TRIGGERED_1E_EVENT .................................................................................................................... 1038 13.4.27f TRIGGERED_1F_EVENT .................................................................................................................... 1039 13.4.27f1 TRIGGERED_1G_EVENT ................................................................................................................... 1039 13.4.27f2 TRIGGERED_1H_EVENT ................................................................................................................... 1039 13.4.27f3 TRIGGERED_1I_EVENT ..................................................................................................................... 1039 13.4.27f4 BEST_FREQUENCY_2A_EVENT ...................................................................................................... 1040 13.4.27f5 TRIGGERED_2B_EVENT ................................................................................................................... 1040 13.4.27f6 TRIGGERED_2C_EVENT ................................................................................................................... 1040 13.4.27f7 TRIGGERED_2D_EVENT ................................................................................................................... 1040 13.4.27f8 TRIGGERED_2E_EVENT .................................................................................................................... 1041 13.4.27f9 TRIGGERED_2F_EVENT .................................................................................................................... 1041 13.4.27f10 TRIGGERED_3A_EVENT ................................................................................................................... 1041 13.4.27f11 TRIGGERED_3B_EVENT ................................................................................................................... 1042 13.4.27f12 TRIGGERED_3C_EVENT ................................................................................................................... 1042 13.4.27f13 BEST_CELL_3D_EVENT .................................................................................................................... 1042 13.4.27f14 TRIGGERED_6A_EVENT ................................................................................................................... 1043 13.4.27f15 TRIGGERED_6B_EVENT ................................................................................................................... 1043 13.4.27f16 TRIGGERED_6C_EVENT ................................................................................................................... 1043 13.4.27f17 TRIGGERED_6D_EVENT ................................................................................................................... 1043 13.4.27f18 TRIGGERED_6E_EVENT .................................................................................................................... 1043 13.4.27f19 TRIGGERED_6F_EVENT .................................................................................................................... 1043 13.4.27f20 TRIGGERED_6G_EVENT ................................................................................................................... 1044 13.4.27f21 TRIGGERED_1J_EVENT..................................................................................................................... 1044 13.4.27g UE_CAPABILITY_REQUESTED........................................................................................................ 1044 13.4.28 UE_CAPABILITY_TRANSFERRED................................................................................................... 1045 13.4.28a UE_POSITIONING_GPS_DATA ......................................................................................................... 1045 13.4.28b UE_POSITIONING_OTDOA_DATA_UE_ASSISTED ...................................................................... 1047 13.4.28c UE_POSITIONING_OTDOA_DATA_UE_BASED ............................................................................ 1048 13.4.29 UNSUPPORTED_CONFIGURATION................................................................................................. 1048 13.4.30 URA_IDENTITY ................................................................................................................................... 1048 13.4.31 U_RNTI ................................................................................................................................................. 1048 13.4.32 VALUE_TAG ........................................................................................................................................ 1049 13.5 UE RRC Procedure Performance................................................................................................................. 1051 13.5.1 Definitions .............................................................................................................................................. 1051 13.5.2 RRC procedure performance values ....................................................................................................... 1051 13.6 RB information parameters for signalling radio bearer RB 0 ...................................................................... 1057 13.6a RB information parameters for SHCCH ...................................................................................................... 1057 13.6b RB information parameters for BCCH mapped to FACH ........................................................................... 1057 13.6c RB information parameters for PCCH mapped to PCH .............................................................................. 1058 13.6d Parameters for BCCH mapped to BCH ....................................................................................................... 1058 13.7 Parameter values for default radio configurations ....................................................................................... 1058
14
Specific functions ............................................................................................................................... 1126

Intra-frequency measurements ..................................................................................................................... 1126 Intra-frequency measurement quantities ................................................................................................ 1126 Intra-frequency reporting events for FDD .............................................................................................. 1126 Reporting event 1A: A Primary CPICH enters the reporting range.................................................. 1126 Reporting event 1B: A primary CPICH leaves the reporting range.................................................. 1129 Reporting event 1C: A non-active primary CPICH becomes better than an active primary CPICH 1131 Reporting event 1D: Change of best cell .......................................................................................... 1134 Reporting event 1E: A Primary CPICH becomes better than an absolute threshold ........................ 1136 Reporting event 1F: A Primary CPICH becomes worse than an absolute threshold ........................ 1137
14.1 14.1.1 14.1.2 14.1.2.1 14.1.2.2 14.1.2.3 14.1.2.4 14.1.2.5 14.1.2.6
3GPP
Release 6
26
3GPP TS 25.331 V6.23.0 (2009-09)
14.1.2.7
Reporting event 1J: A non-active E-DCH but active DCH primary CPICH becomes better than an active E-DCH primary CPICH .................................................................................................... 1139 14.1.3 Intra-frequency reporting events for TDD ............................................................................................. 1142 14.1.3.1 Reporting event 1G: Change of best cell (TDD) .............................................................................. 1142 14.1.3.2 Reporting event 1H: Timeslot ISCP below a certain threshold (TDD) ............................................ 1143 14.1.3.3 Reporting event 1I: Timeslot ISCP above a certain threshold (TDD) .............................................. 1144 14.1.4 Event-triggered periodic intra-frequency measurement reports (informative) ....................................... 1146 14.1.4.1 Cell addition failure (FDD only) ...................................................................................................... 1146 14.1.4.1a Cell removal failure (FDD only) ...................................................................................................... 1147 14.1.4.2 Cell replacement failure (FDD only) ................................................................................................ 1148 14.1.5 Mechanisms available for modifying intra-frequency measurement reporting behaviour (informative) .......................................................................................................................................... 1148 14.1.5.1 Hysteresis ......................................................................................................................................... 1148 14.1.5.2 Time-to-trigger ................................................................................................................................. 1149 14.1.5.3 Cell individual offsets ....................................................................................................................... 1150 14.1.5.4 Forbid a Primary CPICH to affect the reporting range (FDD only) ................................................. 1151 14.1.6 Report quantities in intra-frequency measurements ............................................................................... 1152 14.2 Inter-frequency measurements ..................................................................................................................... 1153 14.2.0a Inter-frequency measurement quantities ................................................................................................ 1153 14.2.0b Frequency quality estimate..................................................................................................................... 1153 14.2.0b.1 FDD cells .......................................................................................................................................... 1153 14.2.0b.2 TDD cells ......................................................................................................................................... 1154 14.2.0c Inter-frequency reporting quantities ....................................................................................................... 1154 14.2.1 Inter-frequency reporting events ............................................................................................................ 1155 14.2.1.1 Event 2a: Change of best frequency. ................................................................................................ 1155 14.2.1.2 Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold. .................................... 1156 14.2.1.3 Event 2c: The estimated quality of a non-used frequency is above a certain threshold .................... 1157 14.2.1.4 Event 2d: The estimated quality of the currently used frequency is below a certain threshold ........ 1158 14.2.1.5 Event 2e: The estimated quality of a non-used frequency is below a certain threshold ................... 1159 14.2.1.6 Event 2 f: The estimated quality of the currently used frequency is above a certain threshold ........ 1160 14.3 Inter-RAT measurements ............................................................................................................................. 1161 14.3.0a Inter-RAT measurement quantities ........................................................................................................ 1161 14.3.0b Frequency quality estimate of the UTRAN frequency ........................................................................... 1162 14.3.0c Inter-RAT reporting quantities ............................................................................................................... 1162 14.3.1 Inter-RAT reporting events .................................................................................................................... 1162 14.3.1.1 Event 3a: The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold. ..................... 1163 14.3.1.2 Event 3b: The estimated quality of other system is below a certain threshold ................................. 1165 14.3.1.3 Event 3c: The estimated quality of other system is above a certain threshold .................................. 1166 14.3.1.4 Event 3d: Change of best cell in other system .................................................................................. 1167 14.3.2 GSM measurements in compressed mode .............................................................................................. 1169 14.3.2.1 GSM RSSI measurements ................................................................................................................ 1169 14.3.2.2 Initial BSIC identification ................................................................................................................ 1169 14.3.2.3 BSIC re-confirmation ....................................................................................................................... 1169 14.4 Traffic Volume Measurements .................................................................................................................... 1169 14.4.1 Traffic Volume Measurement Quantity ................................................................................................. 1169 14.4.2 Traffic Volume reporting triggers .......................................................................................................... 1170 14.4.2.1 Reporting event 4 A: Transport Channel Traffic Volume becomes larger than an absolute threshold ........................................................................................................................................... 1174 14.4.2.2 Reporting event 4 B: Transport Channel Traffic Volume becomes smaller than an absolute threshold ........................................................................................................................................... 1174 14.4.3 Traffic volume reporting mechanisms.................................................................................................... 1175 14.4.3.1 Pending time after trigger ................................................................................................................. 1175 14.4.3.2 Time-to-trigger ................................................................................................................................. 1175 14.4.4 Interruption of user data transmission .................................................................................................... 1176 14.5 Quality Measurements ................................................................................................................................. 1176 14.5.1 Quality reporting measurement quantities.............................................................................................. 1176 14.5.2 Quality reporting events ......................................................................................................................... 1176 14.5.2.1 Reporting event 5A: A predefined number of bad CRCs is exceeded .............................................. 1176 14.6 UE internal measurements ........................................................................................................................... 1177 14.6.1 UE internal measurement quantities....................................................................................................... 1177
3GPP
Release 6
27
3GPP TS 25.331 V6.23.0 (2009-09)
14.6.2 14.6.2.1 14.6.2.2 14.6.2.3 14.6.2.4 14.6.2.5 14.6.2.6
UE internal measurement reporting events ............................................................................................ 1177 Reporting event 6A: The UE Tx power becomes larger than an absolute threshold ........................ 1177 Reporting event 6B: The UE Tx power becomes less than an absolute threshold ............................ 1178 Reporting event 6C: The UE Tx power reaches its minimum value ................................................ 1179 Reporting event 6D: The UE Tx power reaches its maximum value ............................................... 1180 Reporting event 6E: The UE RSSI reaches the UE's dynamic receiver range .................................. 1181 Reporting event 6F (FDD): The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold ....................................................................................... 1181 14.6.2.6a Reporting event 6F (1.28 Mcps TDD): The time difference indicated by TADV becomes larger than an absolute threshold ................................................................................................................ 1182 14.6.2.7 Reporting event 6G: The UE Rx-Tx time difference for a RL included in the active set becomes less than an absolute threshold ......................................................................................................... 1182 14.7 UE positioning measurements ..................................................................................................................... 1183 14.7.1 UE positioning measurement quantities ................................................................................................. 1183 14.7.2 Void ........................................................................................................................................................ 1183 14.7.3 UE positioning reporting events ............................................................................................................. 1183 14.7.3.1 Reporting Event 7a: The UE position changes more than an absolute threshold ............................. 1183 14.7.3.2 Reporting Event 7b: SFN-SFN measurement changes more than an absolute threshold ................. 1184 14.7.3.3 Reporting Event 7c: GPS time and SFN time have drifted apart more than an absolute threshold .. 1184 14.8 Void ............................................................................................................................................................. 1185 14.9 Downlink power control .............................................................................................................................. 1185 14.9.1 Generalities ............................................................................................................................................ 1185 14.9.2 Downlink power control in compressed mode ....................................................................................... 1185 14.10 Calculated Transport Format Combination.................................................................................................. 1186 14.10.1 Default TFCS for MBMS ....................................................................................................................... 1186 14.10.1.1 S-CCPCH configuration including a FACH carrying MSCH .......................................................... 1186 14.10.1.2 S-CCPCH configuration not including a FACH carrying MSCH .................................................... 1186 14.11 UE autonomous update of virtual active set on non-used frequency (FDD only) ....................................... 1187 14.11.1 Initial virtual active set ........................................................................................................................... 1187 14.11.2 Virtual active set update during an inter-frequency measurement ......................................................... 1188 14.12 Provision and reception of RRC information between network nodes ........................................................ 1189 14.12.0 General ................................................................................................................................................... 1189 14.12.0a General error handling for RRC messages exchanged between network nodes .................................... 1190 14.12.1 RRC Information to target RNC ............................................................................................................ 1191 14.12.2 RRC information, target RNC to source RNC ....................................................................................... 1191 14.12.3 Void ........................................................................................................................................................ 1193 14.12.4 RRC messages exchanged between network nodes ............................................................................... 1193 14.12.4.0 HANDOVER TO UTRAN COMMAND......................................................................................... 1193 14.12.4.0a INTER RAT HANDOVER INFO .................................................................................................... 1193 14.12.4.1 INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES ....................................... 1193 14.12.4.2 SRNS RELOCATION INFO ........................................................................................................... 1194 14.12.4.3 Void .................................................................................................................................................. 1207 14.12.4.4 RFC 3095 CONTEXT INFO ............................................................................................................ 1207 14.13 Void ............................................................................................................................................................. 1210 14.14 Void ............................................................................................................................................................. 1210
Annex A (informative):
A.1 A.2 A.3 A.4 B.1 B.2 B.2.1 B.3 B.3.1 B.3.1.1 B.3.1.2 B.3.1.3 B.3.1.4
USIM parameters ...................................................................................... 1211
Introduction.................................................................................................................................................. 1211 Ciphering information.................................................................................................................................. 1211 Frequency information ................................................................................................................................. 1211 Multiplicity values and type constraint values ............................................................................................. 1212
Annex B (informative):
Description of RRC state transitions ....................................................... 1213
RRC states and state transitions including GSM ......................................................................................... 1213 Transition from Idle Mode to UTRA RRC Connected Mode ...................................................................... 1213 Transitions for Emergency Calls ............................................................................................................ 1213 UTRA RRC Connected Mode States and Transitions ................................................................................. 1213 CELL_DCH state ................................................................................................................................... 1213 Transition from CELL_DCH to Idle Mode ...................................................................................... 1214 Transition from CELL_DCH to CELL_FACH state ........................................................................ 1214 Transition from CELL_DCH to CELL_PCH state ........................................................................... 1214 Transition from CELL_DCH to URA_PCH state ............................................................................ 1214
3GPP
Release 6
28
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.1.5 B.3.1.6 B.3.1.7 B.3.1.8 B.3.2 B.3.2.1 B.3.2.2 B.3.2.3 B.3.2.4 B.3.2.5 B.3.2.6 B.3.2.7 B.3.2.8 B.3.3 B.3.3.1 B.3.3.2 B.3.3.3 B.3.3.4 B.3.3.5 B.3.4 B.3.4.1 B.3.4.2 B.3.4.3 B.3.4.4 B.3.4.5 B.3.5 B.4 B.5 B.6 B.6.1 B.6.2
Radio Resource Allocation tasks (CELL_DCH) .............................................................................. 1214 RRC Connection mobility tasks (CELL_DCH) ............................................................................... 1215 UE Measurements (CELL_DCH)..................................................................................................... 1215 Acquisition of system information (CELL_DCH) ........................................................................... 1215 CELL_FACH state ................................................................................................................................. 1215 Transition from CELL_FACH to CELL_DCH state ........................................................................ 1215 Transition from CELL_FACH to CELL_PCH state ........................................................................ 1215 Transition from CELL_FACH to Idle Mode .................................................................................... 1215 Transition from CELL_FACH to URA_PCH State ......................................................................... 1215 Radio Resource Allocation Tasks (CELL_FACH)........................................................................... 1216 RRC Connection mobility tasks (CELL_FACH) ............................................................................. 1216 UE Measurements (CELL_FACH) .................................................................................................. 1216 Transfer and update of system information (CELL_FACH) ............................................................ 1216 CELL_PCH state .................................................................................................................................... 1217 Transition from CELL_PCH to CELL_FACH state ........................................................................ 1217 Radio Resource Allocation Tasks (CELL_PCH) ............................................................................. 1217 RRC Connection mobility tasks (CELL_PCH) ................................................................................ 1217 UE Measurements (CELL_PCH) ..................................................................................................... 1217 Transfer and update of system information (CELL_PCH) ............................................................... 1217 URA_PCH State..................................................................................................................................... 1218 Transition from URA_PCH State to CELL_FACH State (URA_PCH) ........................................... 1218 Radio Resource Allocation Tasks (URA_PCH) ............................................................................... 1218 RRC Connection mobility tasks (URA_PCH).................................................................................. 1218 UE Measurements (URA_PCH) ....................................................................................................... 1218 Transfer and update of system information (URA_PCH) ................................................................ 1219 States and Transitions for Cell Reselection in URA_PCH, CELL_PCH, and CELL_FACH ................ 1219 Inter-RAT handover with CS domain services ............................................................................................ 1219 Inter-RAT handover with PS domain services............................................................................................. 1220 Inter-RAT handover with simultaneous PS and CS domain services .......................................................... 1220 Inter-RAT handover UTRAN to GSM / BSS......................................................................................... 1220 Inter-RAT handover GSM / BSS to UTRAN......................................................................................... 1220
Annex C (informative):
C.1 C.2
Description for the Compressed Coding of Pre-defined configurations included in the INTER RAT HANDOVER INFO message ....................................................................................................... 1221
Definitions ................................................................................................................................................... 1221 Examples of the methodology ..................................................................................................................... 1221
Annex D (Normative): Annex E (informative):
Implementation of Domain Specific Access Control (DSAC) in UEs of 3GPP Release 5 .......................................................................................... 1224 Change history ........................................................................................... 1225
3GPP
Release 6
29
3GPP TS 25.331 V6.23.0 (2009-09)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 6
30
3GPP TS 25.331 V6.23.0 (2009-09)
Scope
The present document specifies the Radio Resource Control protocol for the UE-UTRAN radio interface. The scope of the present document also includes: the information to be transported in a transparent container between source RNC and target RNC in connection with SRNC relocation; the information to be transported in a transparent container between a target RNC and another system.
References
References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". 3GPP TS 25.301: "Radio Interface Protocol Architecture". 3GPP TS 25.303: "Interlayer Procedures in Connected Mode". 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3". 3GPP TS 25.103: "RF parameters in support of RRM". 3GPP TS 25.215: "Physical layer Measurements (FDD)". 3GPP TS 25.225: "Physical layer Measurements (TDD)". 3GPP TS 25.401: "UTRAN overall description". 3GPP TS 25.402: "Synchronization in UTRAN; Stage 2". 3GPP TS 23.003: "Numbering, addressing and identification". ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interface". RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)". 3GPP TR 25.921: "Guidelines and principles for protocol description and error handling". 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". 3GPP TS 25.305: "Stage 2 Functional Specification of UE Positioning in UTRAN". 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
3GPP
Release 6
31
3GPP TS 25.331 V6.23.0 (2009-09)
[20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50]
3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)". 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)". 3GPP TS 25.102: "UE Radio Transmission and Reception (TDD)". 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode". 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". 3GPP TS 25.213: "Spreading and modulation (FDD)". 3GPP TS 25.214: "Physical layer procedures (FDD)". 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". 3GPP TS 25.223: "Spreading and modulation (TDD)". 3GPP TS 25.224: "Physical Layer Procedures (TDD)". 3GPP TS 25.302: "Services provided by the physical layer ". 3GPP TS 25.306 "UE Radio Access Capabilities". 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) Specification". 3GPP TS 25.324: "Broadcast/Multicast Control BMC". 3GPP TR 25.922: "Radio resource management strategies". 3GPP TR 25.925: "Radio interface for broadcast/multicast services". 3GPP TS 33.102: "3G Security; Security Architecture". 3GPP TS 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing". 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". 3GPP TS 45.005: "Radio transmission and reception". 3GPP TS 45.008: "Radio subsystem link control". ITU-T Recommendation X.680 (07/2002) "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". ITU-T Recommendation X.681 (07/2002) "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". 3GPP TS 31.102: "Characteristics of the USIM Application".
3GPP
Release 6
32
3GPP TS 25.331 V6.23.0 (2009-09)
[51] [52] [53] [54] [55] [56] [57] [58]
3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA): Overall Description; Stage 2". IANA ROHC profile identifier definition (http://www.iana.org/assignments/rohc-pro-ids). 3GPP TS 44.118: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol, Iu Mode". 3GPP TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description". 3GPP TS 25.346: " Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (Stage-2)". 3GPP TR 25.992: "Multimedia Broadcast Multicast Service (MBMS); UTRAN/GERAN Requirements". 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". 3GPP TS 25.309: "FDD Enhanced Uplink; Overall Description; Stage 2".
3
3.1
Definitions and abbreviations

Definitions
For the purposes of the present document, the terms and definitions given in [1] apply, together as: Data Description Indicator (DDI): MAC-e header field used to identify the logical channel, MAC-d flow and the size of the MAC-d PDUs concatenated into a MAC-es PDU. E-DCH active set: The set of cells which carry the E-DCH for one UE. Only radio links for which an E-HICH configuration is stored are considered part of the E-DCH active set. HARQ profile: One HARQ profile consists of a power offset attribute and maximum number of transmissions. MBMS activated services: the MBMS multicast services the UE has joined as well as the broadcast services the UE is interested in. MCCH acquisition: the procedure for acquiring all MCCH information relevant for the UE ie. includes reception of the RB information for the UEs MBMS activated services. MBMS controlling cell: the cell from which the UE receives MCCH. MBMS notification: a notification provided by UTRAN indicating a change in the provision of one or more MBMS services. MBMS transmission: a possibly repeated session of an MBMS service. An MBMS transmission is uniquely identified by the combination of the MBMS service identity and the MBMS session identity. MBMS Selected Services: a subset of the MBMS activated services of the Broadcast type for which the UE applies RRC procedures to inform UTRAN that the service has been selected (by upper layers). Primary Absolute Grant: Absolute Grant received with the primary E-RNTI. Secondary Absolute Grant: Absolute Grant received with the secondary E-RNTI. Serving E-DCH cell: Cell from which the UE receives Absolute Grants from the Node-B scheduler. A UE has one Serving E-DCH cell. Serving E-DCH RLS or Serving RLS: Set of cells which contains at least the Serving E-DCH cell and from which the UE can receive and combine one Relative Grant. The UE has only one Serving E-DCH RLS.
3GPP
Release 6
33
3GPP TS 25.331 V6.23.0 (2009-09)
Non-serving E-DCH RL or Non-serving RL: Cell which belongs to the E-DCH active set but does not belong to the Serving E-DCH RLS and from which the UE can receive one Relative Grant. The UE can have zero, one or several Non-serving E-DCH RL(s).
3.2
Abbreviations
Acknowledgement Absolute Grant Acquisition Indicator CHannel Acknowledged Mode Access Stratum Access Service Class Abstract Syntax Notation.1 Broadcast Control Channel Broadcast Control Functional Entity Bit Error Rate BLock Error Rate Base Station Sub-system Common Control Channel Common Control Physical CHannel Conditional on history Connection Management Core Network Cell RNTI Common Traffic CHannel Calculated Transport Format Combination Conditional on value Dynamic Channel Allocation Dedicated Control Channel Dedicated Control Functional Entity Dedicated Channel Dedicated Control SAP Data Description Indicator Differential Global Positioning System Downlink Downlink Shared Channel Dedicated Traffic Channel E-DCH Absolute Grant Channel Enhanced uplink DCH E-DCH Dedicated Physical Control Channel E-DCH Dedicated Physical Data Channel E-DCH HARQ Acknowledgement Indicator Channel E-DCH Relative Grant Channel E-DCH RNTI E-DCH Transport Format Combination Indicator Forward Access Channel Frequency Division Duplex Fractional DPCH General Control SAP GSM/EDGE Radio Access Network GERAN Registration Area GERAN Radio Network Temporary Identity Hybrid Automatic Repeat Request Hierarchical Cell Structure Hyper Frame Number HS-DSCH RNTI High Speed Downlink Shared Channel Identifier Intra Domain NAS Node Selector
For the purposes of the present document, the following abbreviations apply: ACK AG AICH AM AS ASC ASN.1 BCCH BCFE BER BLER BSS CCCH CCPCH CH CM CN C-RNTI CTCH CTFC CV DCA DCCH DCFE DCH DC-SAP DDI DGPS DL DSCH DTCH E-AGCH E-DCH E-DPCCH E-DPDCH E-HICH E-RGCH E-RNTI E-TFCI FACH FDD F-DPCH GC-SAP GERAN GRA G-RNTI HARQ HCS HFN H-RNTI HS-DSCH ID IDNNS
3GPP
Release 6
34
3GPP TS 25.331 V6.23.0 (2009-09)
IE IETF IMEI IMSI IP ISCP L1 L2 L3 LAI MAC MBMS MCC MCCH MD MICH MM MNC MP MTCH MSCH NACC NAS Nt-SAP NW OP PCCH PCH PDCP PDSCH PDU PLMN PNFE PRACH PSI p-t-m P-TMSI p-t-p PUSCH QoS RAB RACH RAI RAT RB RFE RG RL RLC RLS RNC RNTI RRC RSCP RSN RSSI SAP SCFE SCTD SCTO SF SG
Information element Internet Engineering Task Force International Mobile Equipment Identity International Mobile Subscriber Identity Internet Protocol Interference on Signal Code Power Layer 1 Layer 2 Layer 3 Location Area Identity Media Access Control Multimedia Broadcast Multicast Service Mobile Country Code MBMS point-to-multipoint Control Channel Mandatory default MBMS notification Indicator Channel Mobility Management Mobile Network Code Mandatory present MBMS point-to-multipoint Traffic Channel MBMS point-to-multipoint Scheduling Channel Network Assisted Cell Change Non Access Stratum Notification SAP Network Optional Paging Control Channel Paging Channel Packet Data Convergence Protocol Physical Downlink Shared Channel Protocol Data Unit Public Land Mobile Network Paging and Notification Control Functional Entity Physical Random Access CHannel Packet System Information Point-to-Multipoint Packet Temporary Mobile Subscriber Identity Point-to-Point Physical Uplink Shared Channel Quality of Service Radio access bearer Random Access CHannel Routing Area Identity Radio Access Technology Radio Bearer Routing Functional Entity Relative Grant Radio Link Radio Link Control Radio Link Set Radio Network Controller Radio Network Temporary Identifier Radio Resource Control Received Signal Code Power Retransmission Sequence Number Received Signal Strength Indicator Service Access Point Shared Control Function Entity Space Code Transmit Diversity Soft Combining Timing Offset (MBMS) Spreading Factor Serving grant
3GPP
Release 6
35
3GPP TS 25.331 V6.23.0 (2009-09)
SHCCH SI SIR S-RNTI TDD TF TFCS TFS TM TME TMSI Tr TSN Tx UE UL UM URA U-RNTI USCH UTRAN
Shared Control Channel System Information Signal to Interference Ratio SRNC - RNTI Time Division Duplex Transport Format Transport Format Combination Set Transport Format Set Transparent Mode Transfer Mode Entity Temporary Mobile Subscriber Identity Transparent Transmission Sequence Number Transmission User Equipment Uplink Unacknowledged Mode UTRAN Registration Area UTRAN-RNTI Uplink Shared Channel Universal Terrestrial Radio Access Network
General
If not specified differently, descriptions are relevant for both FDD and TDD. Descriptions for TDD only are relevant for both 1.28 Mcps TDD and 3.84 Mcps TDD if not specified differently.
4.1
-
Overview of the specification

subclause 4.2 contains the description of the model of the RRC protocol layer; clause 5 lists the RRC functions and the services provided to upper layers; clause 6 lists the services expected from the lower layers and specifies the radio bearers available for usage by the RRC messages; clause 7 specifies the UE states for the Access Stratum, and also specifies the processes running in the UE in the respective states; clause 8 specifies RRC procedures, including UE state transitions; clause 9 specifies the procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity; clause 10 describes the message in a Tabular format; these messages descriptions are referenced in clause 8; clause 11 specifies the encoding of the messages of the RRC protocol. This is based on the Tabular description in clause 10. clause 12 specifies the transfer syntax for RRC PDUs derived from the encoding definition; clause 13 lists the protocol timers, counters, constants and variables to be used by the UE; clause 14 specifies some of the processes applicable in UTRA RRC connected mode e.g. measurement processes, and also the RRC information to be transferred between network nodes. Note that not all the processes applicable in UTRA RRC connected mode are specified here i.e. some UTRA RRC connected mode processes are described in [4] e.g. cell re-selection; Annex A contains recommendations about the network parameters to be stored on the USIM;
This specification is organised as follows:
3GPP
Release 6
36
3GPP TS 25.331 V6.23.0 (2009-09)
Annex B contains informative Stage 2 description of the RRC protocol states and state transitions.
The following figure summarises the mapping of UE states, including states in GSM, to the appropriate UTRA and GSM specifications that specify the UE behaviour.
UE switch-on
UE Idle 3GPP TS 25.304 TS 23.122
UE connected 3GPP TS 25.331
GSM connected GSM TS 04.18
GPRS Packet Transfer GSM TS 04.60
GSM idle GSM TS 05.08
UE idle 3GPP TS 25.304 3GPP TS 25.331
CELL_DCH 3GPP TS 25.331
CELL_FACH 3GPP TS 25.331 3GPP TS 25.304
CELL_PCH 3GPP TS 25.331 3GPP TS 25.304
URA_PCH 3GPP TS 25.331 3GPP TS 25.304
Figure 4.1-1: Mapping of UE state to 3GPP Specifications
4.2
-
RRC Layer Model

Routing of higher layer messages to different MM/CM entities (UE side) or different core network domains (UTRAN side) is handled by the Routing Function Entity (RFE). Broadcast functions are handled in the broadcast control function entity (BCFE). The BCFE is used to deliver the RRC services, which are required at the GC-SAP. The BCFE can use the lower layer services provided by the Tr-SAP and UM-SAP. Paging of UEs that do not have an RRC connection is controlled by the paging and notification control function entity (PNFE). The PNFE is used to deliver the RRC services that are required at the Nt-SAP. The PNFE can use the lower layer services provided by the Tr-SAP and UM-SAP. The Dedicated Control Function Entity (DCFE) handles all functions specific to one UE. The DCFE is used to deliver the RRC services that are required at the DC-SAP and can use lower layer services of UM/AM-SAP and Tr-SAP depending on the message to be sent and on the current UE service state. In TDD mode, the DCFE is assisted by the Shared Control Function Entity (SCFE) location in the C-RNC, which controls the allocation of the PDSCH and PUSCH using lower layers services of UM-SAP and Tr-SAP. The Transfer Mode Entity (TME) handles the mapping between the different entities inside the RRC layer and the SAPs provided by RLC.
The functional entities of the RRC layer are described below:
NOTE 1: Logical information exchange is necessary also between the RRC sublayer functional entities. Most of that is implementation dependent and not necessary to present in detail in a specification. Figure 4.2-1 shows the RRC model for the UE and Figure 4.2-2 and Figure 4.2-3 show the RRC model for the UTRAN. NOTE 2: The figure shows only the types of SAPs that are used. Multiple instances of Tr-SAP, UM-SAP and AMSAP are possible. Especially, different functional entities usually use different instances of SAP types.
3GPP
Release 6
37
3GPP TS 25.331 V6.23.0 (2009-09)
NAS NAS
GC-SAP
GC-SAP
... ...
GC-SAP
Nt-SAP
Nt-SAP
... ...
DC-SAP
Nt-SAP
DC-SAP
... ...
DC-SAP
Access Stratum RRC SAPs
RFE
RFE
RFE
RRC
BCFE PNFE DCFE SCFE
TME
RLCctrl
Tr-SAP
UM SAP
AM SAP
RLC
MAC ctrl L1-ctrl
MAC L1
Figure 4.2-1: UE side model of RRC
3GPP
Release 6
38
3GPP TS 25.331 V6.23.0 (2009-09)
Access Stratum
...
RFE
...
RFE
...
RFE
RRC SAPs
RRC
BCFE PNFE DCFE TME SCFE
RLCctrl
Tr-SAP
UM SAP
AM SAP
RLC
MAC ctrl L1-ctrl
MAC L1
Figure 4.2-2: UTRAN side RRC model (DS-MAP system)
NAS
NAS
DC-SAP
GC-SAP
GC-SAP
... ...
GC-SAP
Nt-SAP
Nt-SAP
... ...
DC-SAP
Nt-SAP
DC-SAP
... ...
DC-SAP
RFE
RFE
RFE
RRC
SCFE
BCFE
PNFE
DCFE
TME
RLCctrl
Tr-SAP
UM SAP
AM SAP
RLC
MAC ctrl L1-ctrl
MAC L1
Figure 4.2-3: UTRAN side RRC model (DS-41 System)
3GPP
Release 6
39
3GPP TS 25.331 V6.23.0 (2009-09)
4.3
Protocol specification principles
This protocol specification is based on the applicable general guidelines given in [14]. In this specification, a notation of variables is used. The variables are defined in subclause 13.4. Variables are typically used to represent a status or a result of an action, such as reception of an information element in a message, which is used to specify a behaviour somewhere else in the specification, such as when setting the value of an information element in a transmitted message. The variables only serve the purpose of specifying the protocol, and do not therefore impose any particular implementation. When specifying the UE behaviour at reception of messages, the behaviour that is tied to reception or non-reception of individual information elements, and in some cases combinations of information elements, is specified in one location (subclause 8.6).
5
5.1
-
RRC Functions and Services provided to upper layers

RRC Functions
Broadcast of information related to the non-access stratum (Core Network); Broadcast of information related to the access stratum; Establishment, maintenance and release of an RRC connection between the UE and UTRAN; Establishment, reconfiguration and release p-t-p of Radio Bearers; Establishment, reconfiguration and release of p-t-m Radio Bearers; Assignment, reconfiguration and release of radio resources for the RRC connection; RRC connection mobility functions; Control of requested QoS; UE measurement reporting and control of the reporting; Outer loop power control; Control of ciphering; Slow DCA (TDD mode); Paging; Initial cell selection and cell re-selection; Arbitration of radio resources on uplink DCH; RRC message integrity protection; Timing advance (TDD mode); CBS control; MBMS control.
The RRC performs the functions listed below. A more detailed description of these functions is provided in [2]:
3GPP
Release 6
40
3GPP TS 25.331 V6.23.0 (2009-09)
5.2
RRC Services provided to upper layers
The RRC offers the following services to upper layers, a description and primitives of these services are provided in [2] and [17]. General Control; Notification; Dedicated control.
The RRC layer provides the UE-UTRAN portion of signalling connections to the upper layers to support the exchange of upper layer's information flow. The signalling connection is used between the user equipment and the core network to transfer upper layer information. For each core network domain, at most one signalling connection may exist at the same time. The RRC layer maps the signalling connections for one UE on a single RRC connection. For the upper layer data transfer on signalling connections, the RRC layer supports the discrimination between two different classes, named "High priority" (corresponding to "SAPI 0" for a GSM-MAP based core network) and "Low priority" (corresponding to "SAPI 3" for a GSM-MAP based core network).
5.3
Primitives between RRC and upper layers
The primitives between RRC and the upper layers are described in [17].
6
6.1
Services expected from lower layers

Services expected from Layer 2
The services provided by layer 2 are described in [2], [15] and [16].
6.2
Services expected from Layer 1
The services provided by layer 1 are described in [2].
6.3
Signalling Radio Bearers
The Radio Bearers (RB) available for transmission of RRC messages are defined as "signalling radio bearers" and are specified in the following. The UE and UTRAN shall select the signalling radio bearers for RRC messages using RLCTM, RLC-UM or RLC-AM on the DCCH and CCCH, according to the following: Signalling radio bearer RB0 shall be used for all messages sent on the CCCH (UL: RLC-TM, DL: RLC-UM). Signalling radio bearer RB1 shall be used for all messages sent on the DCCH, when using RLC unacknowledged mode (RLC-UM). Signalling radio bearer RB2 shall be used for all messages sent on the DCCH, when using RLC acknowledged mode (RLC-AM), except for the RRC messages carrying higher layer (NAS) signalling. Signalling radio bearer RB3 and optionally Signalling radio bearer RB4 shall be used for the RRC messages carrying higher layer (NAS) signalling and sent on the DCCH in RLC acknowledged mode (RLC-AM), as specified in subclauses 8.1.8., 8.1.9 and 8.1.10. Additionally, RBs whose identities shall be set between 5 and 32 may be used as signalling radio bearer for the RRC messages on the DCCH sent in RLC transparent mode (RLC-TM). RRC messages on the SHCCH are mapped either on RACH or on the USCH in the uplink using TM and either on FACH or on the DSCH using RLC-UM. These messages are only specified for TDD mode.
3GPP
Release 6
41
3GPP TS 25.331 V6.23.0 (2009-09)
RRC messages on the MCCH are mapped on FACH using RLC-UM. The transport channel configuration for MCCH is indicated on BCCH. For this signalling radio bearer no identity is applied. RRC messages on the MSCH are mapped on FACH using RLC-UM. The transport channel configuration for MSCH is indicated on MCCH. For this signalling radio bearer no identity is applied.
The Radio Bearer configuration for signalling radio bearer RB0, SHCCH, BCCH on FACH, PCCH on PCH and BCCH mapped to BCH are specified in subclauses 13.6, 13.6a, 13.6b and 13.6c. Ciphering is never applied to signalling radio bearer RB0 or signalling radio bearers using RLC TM.
7
7.1
Protocol states
Overview of RRC States and State Transitions including GSM
Figure 7.1-1 shows the RRC states in UTRA RRC Connected Mode, including transitions between UTRA RRC connected mode and GSM connected mode for CS domain services, and between UTRA RRC connected mode and GSM/GPRS packet modes for PS domain services. It also shows the transitions between Idle Mode and UTRA RRC Connected Mode and furthermore the transitions within UTRA RRC connected mode.
UTRA RRC Connected Mode URA_PCH
out of service in service
CELL_PCH
UTRA: Inter-RAT Handover
GSM: Handover
GSM Connected Mode
UTRA: Inter-RAT Handover
CELL_DCH
CELL_FACH
GSM: PS Handover
GPRS Packet Transfer Mode

Release RR Connection Initiation of temporary block flow Establish RR Connection
Cell reselection
Release of temporary block flow
Release RRC Connection
Establish RRC Release RRC Connection Connection
Establish RRC Connection
GPRS Packet Idle Mode1 Camping on a UTRAN cell1 Camping on a GSM / GPRS cell1
Idle Mode
: 1
NOTE
: The indicated division within Idle Mode is only included for clarification and shall not be interpreted as states.
Figure 7.1-1: RRC States and State Transitions including GSM The RRC connection is defined as a point-to-point bi-directional connection between RRC peer entities in the UE and the UTRAN characterised by the allocation of a U-RNTI. A UE has either zero or one RRC connection. If NAS informs AS about a new selected PLMN, registered PLMN or equivalent PLMN list while being in connected mode, the UE shall perform the actions according to subclause 8.5.24. NOTE: The state transitions are specified in clause 8.
3GPP
Release 6
42
3GPP TS 25.331 V6.23.0 (2009-09)
7.2
NOTE:
Processes in UE modes/states
This subclause specifies what processes shall be active in the UE in the different RRC modes/states. The related procedures and the conditions on which they are triggered are specified either in clause 8 or elsewhere in the relevant process definition.
7.2.1
UE Idle mode
UE processes that are active in UE Idle mode are specified in [4]. The UE shall perform a periodic search for higher priority PLMNs as specified in [25].
7.2.2
UTRA RRC Connected mode
In this specification unless otherwise mentioned "connected mode" shall refer to "UTRA RRC connected mode".
7.2.2.1
URA_PCH or CELL_PCH state
In the URA_PCH or CELL_PCH state the UE shall perform the following actions: NOTE: Neither DCCH nor DTCH are available in these states.
1> if the UE is "in service area": 2> maintain up-to-date system information as broadcast by the serving cell as specified in the subclause 8.1.1; 2> perform cell reselection process as specified in [4]; 2> perform a periodic search for higher priority PLMNs as specified in [25]; NOTE: If the DRX cycle length is 80ms, then a search for higher priority PLMNs may not identify all the available PLMNs due to the paging occasion on the current serving cell coinciding with the MIB of the cell of interest.
2> monitor the paging occasions and PICH monitoring occasions determined according to subclauses 8.6.3.1a and 8.6.3.2 and receive paging information on the PCH mapped on the S-CCPCH selected by the UE according to the procedure in subclause 8.5.19; 2> act on RRC messages received on PCCH and BCCH; 2> perform measurements process according to measurement control information as specified in subclause 8.4 and in subclause 14.4; 2> maintain up-to-date BMC data if it supports Cell Broadcast Service (CBS) as specified in [37]; 2> act on RRC messages received on MCCH if it supports MBMS and has activated an MBMS service as specified in subclause 8.7; 2> run timer T305 for periodical URA update if the UE is in URA_PCH or for periodical cell update if the UE is in CELL_PCH. 1> if the UE is "out of service area": 2> perform cell selection process as specified in [4]; 2> run timer T316; 2> run timer T305 or T307; 2> if the cell selection process fails to find a suitable cell after a complete scan of all RATs and all frequency bands supported by the UE, the UE shall after a minimum of TimerOutOfService time (default value 30 s) of being "out of service area": 3> indicate all available PLMNs to NAS to enable the selection of a new PLMN;
3GPP
Release 6
43
3GPP TS 25.331 V6.23.0 (2009-09)
3> if an acceptable cell is found then the UE shall camp on that cell to obtain limited service as defined in [4] and, perform actions according to subclause 8.5.24; 3> else if no acceptable cell is found, the UE shall continue looking for an acceptable cell as defined in [4].
7.2.2.2
CELL_FACH state
In the CELL_FACH state the UE shall perform the following actions: NOTE: DCCH and, if configured, DTCH are available in this state.
1> if the UE is "in service area": 2> maintain up-to-date system information as broadcast by the serving cell as specified in subclause 8.1.1; 2> perform cell reselection process as specified in [4]; 2> perform measurements process according to measurement control information as specified in subclause 8.4 and in subclause 14.4; 2> run timer T305 (periodical cell update); 2> select and configure the RB multiplexing options applicable for the transport channels to be used in this RRC state; 2> listen to all FACH transport channels mapped on the S-CCPCH selected by the UE according to the procedure in subclause 8.5.19; 2> act on RRC messages received on BCCH, CCCH and DCCH; 2> act on RRC messages received on MCCH if it supports MBMS and has activated an MBMS service as specified in subclause 8.7; 2> act on RRC messages received on, if available, SHCCH (TDD only). 1> if the UE is "out of service area": 2> perform cell selection process as specified in [4]; 2> run timers T305 (periodical cell update), and T317 (cell update when re-entering "in service") or T307 (transition to Idle mode), if started; 2> run timers T314 and/or T315, if started; 2> if the cell selection process fails to find a suitable cell after a complete scan of all RATs and all frequency bands supported by the UE, the UE shall after a minimum of TimerOutOfService time (default value 30 seconds) of being "out of service area": 3> indicate all available PLMNs to NAS to enable the selection of a new PLMN; 3> if an acceptable cell is found then the UE shall camp on that cell to obtain limited service as defined in [4] and perform actions according to subclause 8.5.24; 3> else if no acceptable cell is found, the UE shall continue looking for an acceptable cell as defined in [4].
7.2.2.3
CELL_DCH state
In the CELL_DCH state the UE shall perform the following actions: NOTE: DCCH and, if configured, DTCH are available in this state.
1> read the system information as specified in subclause 8.1.1 (for UEs in TDD mode); 1> perform measurements process according to measurement control information as specified in subclause 8.4 and in clause 14;
3GPP
Release 6
44
3GPP TS 25.331 V6.23.0 (2009-09)
1> select and configure the RB multiplexing options applicable for the transport channels to be used in this RRC state; 1> act on RRC messages received on DCCH; 1> act on RRC messages received on BCCH (applicable only to UEs with certain capabilities and in FDD mode); 1> act on RRC messages received on MCCH if it supports MBMS and has activated an MBMS service as specified in subclause 8.7 (applicable only to UEs supporting MBMS with certain capabilities); 1> act on RRC messages received on BCCH (TDD only) and, if available, SHCCH (TDD only). NOTE: If any of the above procedures results in different HS-DSCH and E-DCH serving cells, the UE behaviour is unspecified.
RRC procedures
The UE shall be able to process several simultaneous RRC procedures. After the reception of a message which invoked a procedure, the UE shall be prepared to receive and act on another message which may invoke a second procedure. Whether this second invocation of a procedure (transaction) is accepted or rejected by the UE is specified in the subclauses of this clause, and in particular in subclause 8.6.3.11 (RRC transaction identifier). On receiving a message the UE shall: 1> check that the message is addressed to the UE (e.g. by checking the IE "Initial UE identity" or the IE "U-RNTI" for messages on CCCH); 1> discard the messages addressed to other UEs. and then the UE shall: 1> apply integrity check as appropriate; 1> proceed with error handling as specified in clause 9; 1> act upon the IE "RRC transaction identifier"; 1> continue with the procedure as specified in the relevant subclause. NOTE: Due to an error in the Release '99 ASN.1, a Release '99 UE is unable to determine which UE is addressed by a downlink CCCH message corresponding to a protocol version later than Release '99. As a result, the Release '99 UE will not be able to return a protocol error according to subclause 9.3a. Therefore, the UTRAN should only send a Release '99 message version towards UEs that have indicated conformance to Release '99 in the IE "Access stratum release indicator".
The RRC entity in the UE shall consider PDUs to have been transmitted when they are submitted to the lower layers. If the RRC entity in the UE submits a message for transmission using AM RLC, it shall consider the message successfully transmitted when UTRAN reception of all relevant PDUs is acknowledged by RLC. In the UE, timers are started when the PDUs are sent on the radio interface in the case of the transmission using the CCCH.
3GPP
Release 6
45
3GPP TS 25.331 V6.23.0 (2009-09)
8.1
8.1.1
RRC Connection Management Procedures

Broadcast of system information
UE UTRAN
SYSTEM INFORMATION
Figure 8.1.1-1: Broadcast of system information

UE UTRAN
PAGING TYPE 1
Figure 8.1.1-2: Notification of system information modification for UEs in idle mode, CELL_PCH state and URA_PCH state
UE UTRAN
SYSTEM INFORMATION CHANGE INDICATION
Figure 8.1.1-3: Notification of system information modification for UEs in CELL_FACH and CELL_DCH(TDD only) state
8.1.1.1
General
The purpose of this procedure is to broadcast system information from the UTRAN to UEs in a cell.
8.1.1.1.1
System information structure
The system information elements are broadcast in system information blocks. A system information block groups together system information elements of the same nature. Different system information blocks may have different characteristics, e.g. regarding their repetition rate and the requirements on UEs to re-read the system information blocks. The system information is organised as a tree. A master information block gives references and scheduling information to a number of system information blocks in a cell. The system information blocks contain the actual system information. The master information block may optionally also contain reference and scheduling information to one or two scheduling blocks, which give references and scheduling information for additional system information blocks. Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks.
3GPP
Release 6
46
3GPP TS 25.331 V6.23.0 (2009-09)
For all system information blocks except System Information Block types 15.2, 15.3 and 16, the content is the same in each occurrence for system information blocks using value tag. System Information Block types 15.2, 15.3 and 16 may occur more than once with different content. In this case scheduling information is provided for each such occurrence of the system information block. System information blocks that do not use value tag may have different content for each occurrence.
8.1.1.1.2
System information blocks
Table 8.1.1 specifies all system information blocks and their characteristics. The area scope column in table 8.1.1 specifies the area where a system information block's value tag is valid. If the area scope is cell, the UE shall consider the system information block to be valid only in the cell in which it was read. If system information blocks have been previously stored for this cell, the UE shall check whether the value tag for the system information block in the entered cell is different compared to the stored value tag. If the area scope is PLMN or Equivalent PLMN, the UE shall check the value tag for the system information block when a new cell is selected. If the value tag for the system information block in the new cell is different compared to the value tag for the system information block stored in the UE, the UE shall re-read the system information block. If the area scope is PLMN, the UE shall consider the system information block to be valid only within the PLMN in which it was read. If the area scope is Equivalent PLMN, the UE shall consider the system information block to be valid within the PLMN in which it was received and all PLMNs which are indicated by higher layers to be equivalent. For System information block types 15.2, 15.3 and 16, which may have multiple occurrences, each occurrence has its own independent value tag. The UE- shall re-read a particular occurrence if the value tag of this occurrence has changed compared to that stored in the UE. The UE mode/state column when block is valid in Table 8.1.1 specifies in which UE mode or UE state the IEs in a system information block shall be regarded as valid by the UE. In other words, the indicated system information block becomes invalid upon change to a mode/state that is not included in this column. System Information Block Type 16 remains also valid upon transition to or from GSM/GPRS. In some cases, the states are inserted in brackets to indicate that the validity is dependent on the broadcast of the associated System Information Blocks by the network as explained in the relevant procedure subclause. The UE mode/state column when block is read in Table 8.1.1 specifies in which UE mode or UE state the IEs in a system information block may be read by the UE. The UE shall have the necessary information prior to execution of any procedure requiring information to be obtained from the appropriate system information block. The requirements on the UE in terms of when to read the system information may therefore be derived from the procedure specifications that specify which IEs are required in the different UE modes/states in conjunction with the different performance requirements that are specified. The UE shall: 1> if System Information Block type 11 is referenced in the master information block or in the scheduling blocks: 2> if System Information Block type 12 is not referenced in the master information block or in the scheduling blocks , or broadcast of System Information Block type 12 is not indicated in System Information Block type 11: 3> have read and acted upon System Information Block type 11 and System Information Block type 11bis, if scheduled on BCH and supported by the UE, in a cell when the UE transmits an RRC message on RACH. 2> else: 3> have read and acted upon System Information Block type 11 and System Information Block type 11bis, if scheduled on BCH and supported by the UE, in a cell before the UE transmits the RRC CONNECTION REQUEST message. 3> have read and acted upon both System Information Block type 11 and System Information Block type 11bis, if scheduled on BCH and supported by the UE, and System Information Block type 12 in a cell when: 4> the UE transmits an RRC message on RACH in RRC connected mode; or 4> the UE receives a message commanding to enter Cell_DCH state.
3GPP
Release 6
47
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE 1: There are a number of system information blocks that include the same IEs while the UE mode/state in which the information is valid differs. This approach is intended to allows the use of different IE values in different UE mode/states. NOTE 2: System Information Block Type 16 is also obtained by a UE while in GSM/GPRS. The details of this are not within the scope of this specification. The Scheduling information column in table 8.1.1 specifies the position and repetition period for the System Information Block. The modification of system information column in table 8.1.1 specifies the update mechanisms applicable for a certain system information block. For system information blocks with a value tag, the UE shall update the information according to subclause 8.1.1.7.1 or 8.1.1.7.2. For system information blocks with an expiration timer, the UE shall, when the timer expires, perform an update of the information according to subclause 8.1.1.7.4. Table 8.1.1: Specification of system information block characteristics
System information block Master information block Area scope UE mode/state when block is valid Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH URA_PCH UE mode/state when block is read Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle, CELL_FACH, CELL_PCH, URA_PCH URA_PCH Scheduling information Modification of system information Value tag Additional comment
Cell
SIB_POS = 0 SIB_REP = 8 (FDD) SIB_REP = 8, 16, 32 (TDD) SIB_OFF=2 Specified by the IE "Scheduling information" in MIB
Scheduling block 1
Cell
Value tag
Scheduling block 2
Cell
Specified by the IE "Scheduling information" in MIB
Value tag
System information block type 1
PLMN
Specified by the IE "Scheduling information"
Value tag
System information block type 2 System information block type 3 System information block type 4
Cell
Cell
Cell
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH) CELL_FACH, CELL_PCH, URA_PCH
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH) CELL_FACH, CELL_PCH, URA_PCH
Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information"
Value tag
Value tag
Value tag
System information block type 5 and 5bis
Cell
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only))
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only))
Value tag
If System information block type 4 is not broadcast in a cell, the connected mode UE shall apply information in System information block type 3 in connected mode. System information block type 5bis is sent instead of system information block type 5 in cells that use Band IV.
3GPP
Release 6 System information block System information block type 6 Area scope UE mode/state when block is valid CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) UE mode/state when block is read CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)
48 Scheduling information
3GPP TS 25.331 V6.23.0 (2009-09) Modification of system information Value tag Additional comment
Cell
If system information block type 6 is not broadcast in a cell, the connected mode UE shall read System information block type 5 or System information block type 5bis. If some of the optional IEs are not included in System information block type 6, the UE shall read the corresponding IEs in System information block type 5 or System information block type 5bis. In TDD mode system information block 6 shall only be read in CELL_DCH if required for open loop power control as specified in subclause 8.5.7 and/or if shared transport channels are assigned to the UE. If in these cases system information block type 6 is not broadcast the UE shall read system information block type 5. In TDD mode system information block type 7 shall only be read in CELL_DCH if shared transport channels are assigned to the UE.
Cell
System information block type 11 System information block type 11bis
Cell
Cell
Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH) Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH)
Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode (CELL_FACH, CELL_PCH, URA_PCH) Idle mode (CELL_FACH, CELL_PCH, URA_PCH)
Expiration timer = MAX(32 , SIB_REP * ExpirationTi meFactor) Value tag
Value tag
3GPP
Release 6 System information block System information block type 12 Area scope UE mode/state when block is valid CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH UE mode/state when block is read Idle mode, CELL_FACH, CELL_PCH, URA_PCH
Cell
If system information block type 12 is not broadcast in a cell, the connected mode UE shall read System information block type 11. If some of the optional IEs are not included in System information block type 12, the UE shall read the corresponding IEs in System information block type 11.
System information block type 13 System information block type 13.1 System information block type 13.2 System information block type 13.3 System information block type 13.4 System information block type 14
Cell
Cell
Cell
Cell
Cell
Cell
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information"
Value tag
Value tag
Value tag
Value tag
Value tag
Expiration timer = MAX(32 , SIB_REP * ExpirationTi meFactor)
This system information block is used in 3.84 Mcps TDD mode only. System information block type 14 shall only be read in CELL_DCH if required for open loop power control as specified in subclause 8.5.7.
System information block type 15 System information block type 15.1 System information block type 15.2 System information block type 15.3
Cell
Cell
Cell
PLMN
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information"
Value tag
Value tag
Value tag
Value tag
For this system information block there may be multiple occurrences For this system information block there may be multiple occurrences
3GPP
Release 6 System information block System information block type 15.4 System information block type 15.5 System information block type 16 Area scope UE mode/state when block is valid Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH UE mode/state when block is read Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Cell
Specified by the IE "Scheduling information" Specified by the IE "Scheduling information" Specified by the IE "Scheduling information"
Cell
Value tag
Equival ent PLMN
Value tag
Cell
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Expiration timer = SIB_REP
For this system information block there may be multiple occurrences. This system information block is also valid while in GSM/GPRS. This system information block is used in TDD mode only. System information block type 17 shall only be read if shared transport channels are assigned to the UE.
System Information Block type 18
Cell
Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle mode, CELL_FACH, CELL_PCH, URA_PCH
Value tag
8.1.1.1.3
Segmentation and concatenation of system information blocks
A generic SYSTEM INFORMATION message is used to convey the system information blocks on the BCCH. A given BCCH may be mapped onto either a BCH or a FACH transport channel according to subclause 8.1.1.1.2. The size of the SYSTEM INFORMATION message shall fit the size of a BCH or a FACH transport block. The RRC layer in UTRAN performs segmentation and concatenation of encoded system information blocks. If the encoded system information block is larger than the size of a SYSTEM INFORMATION message, it will be segmented and transmitted in several messages. If the encoded system information block is smaller than a SYSTEM INFORMATION message, UTRAN may concatenate several system information blocks, or the first segment or the last segment into the same message as specified in the remainder of this clause. Four different segment types are defined: First segment; Subsequent segment; Last segment; Complete.
Each of the types - First, Subsequent and Last segment - is used to transfer segments of a master information block, scheduling block or a system information block. The segment type, Complete, is used to transfer a complete master information block, complete scheduling block or a complete system information block.
3GPP
Release 6
51
3GPP TS 25.331 V6.23.0 (2009-09)
Each segment consists of a header and a data field. The data field carries the encoded system information elements. The header contains the following parameters: The number of segments in the system information block (SEG_COUNT). This parameter is only included in the header if the segment type is "First segment". SIB type. The SIB type uniquely identifies the master information block, scheduling block or a system information block. Segment index. This parameter is only included in the header if the segment type is "Subsequent segment" or "Last segment".
UTRAN may combine one or several segments of variable length in the same SYSTEM INFORMATION message. The following combinations are allowed: 1. No segment; 2. First segment; 3. Subsequent segment; 4. Last segment; 5. Last segment + First segment; 6. Last segment + one or several Complete; 7. Last segment + one or several Complete + First segment; 8. One or several Complete; 9. One or several Complete + First segment; 10. One Complete of size 215 to 226; 11. Last segment of size 215 to 222. The "No segment" combination is used when there is no master information block, scheduling block or system information block scheduled for a specific BCH transport block. UEs are not required to support the reception of multiple occurrences of the same system information block type within one SYSTEM INFORMATION message. NOTE: Since the SIB type is the same for each occurrence of the system information block, the UE does not know the order in which the occurrences, scheduled for this SYSTEM INFORMATION message, appear. Therefore, the UE is unable to determine which scheduling information, e.g., value tag relates to which occurrence of the system information block.
8.1.1.1.4
Re-assembly of segments
The RRC layer in the UE shall perform re-assembly of segments. All segments belonging to the same master information block, scheduling block or system information block shall be assembled in ascending order with respect to the segment index. When all segments of the master information block, scheduling block or a system information block have been received, the UE shall perform decoding of the complete master information block, scheduling block or system information block. For System Information Block types 15.2, 15.3 and 16, which may have multiple occurrences, each occurrence shall be re-assembled independently. The UE shall discard system information blocks of which segments were missing, of which segments were received out of sequence and/or for which duplicate segments were received. The only valid sequence is an ascending one with the sequence starting with the First Segment of the associated System Information Block.
3GPP
Release 6
52
3GPP TS 25.331 V6.23.0 (2009-09)
If the UE receives a Subsequent segment or Last segment where the index in IE "Segment index" is equal to or larger than the number of segments stated in IE "SEG_COUNT" in the scheduling information for that scheduling block or system information block: 1> the UE may: 2> read all the segments to create a system information block as defined by the scheduling information read by the UE; 2> store the content of the system information block with a value tag set to the value NULL; and 2> consider the content of the scheduling block or system information block as valid: 3> until it receives the same type of scheduling block or system information block in a position according to its scheduling information; or 3> at most for 6 hours after reception. 1> and the UE shall: 2> re-read scheduling information for that scheduling block or system information block. If the UE receives a Subsequent segment or Last segment where the index in IE "Segment index" is equal to or larger than the number of segments stated in IE "SEG_COUNT" in the First segment, the UE shall 1> discard all segments for that master information block, scheduling block or system information block; and 1> re-read the scheduling information for that system information block; 1> then re-read all segments for that system information block.
8.1.1.1.5
Scheduling of system information
Scheduling of system information blocks is performed by the RRC layer in UTRAN. If segmentation is used, it should be possible to schedule each segment separately. To allow the mixing of system information blocks with short repetition period and system information blocks with segmentation over many frames, UTRAN may multiplex segments from different system information blocks. Multiplexing and de-multiplexing is performed by the RRC layer. The scheduling of each system information block broadcast on a BCH transport channel is defined by the following parameters: the number of segments (SEG_COUNT); the repetition period (SIB_REP). The same value applies to all segments; the position (phase) of the first segment within one cycle of the Cell System Frame Number (SIB_POS(0)). Since system information blocks are repeated with period SIB_REP, the value of SIB_POS(i), i = 0, 1, 2, SEG_COUNT-1 must be less than SIB_REP for all segments; the offset of the subsequent segments in ascending index order (SIB_OFF(i), i = 1, 2, SEG_COUNT-1) The position of the subsequent segments is calculated using the following: SIB_POS(i) = SIB_POS(i-1) + SIB_OFF(i).
The scheduling is based on the Cell System Frame Number (SFN). The SFN of a frame at which a particular segment, i, with i = 0, 1, 2, SEG_COUNT-1 of a system information block occurs, fulfils the following relation: SFN mod SIB_REP = SIB_POS(i) In FDD and TDD the scheduling of the master information block is fixed as defined in table 8.1.1. For TDD, UTRAN may apply one of the values allowed for the master information block's repetition period. The value that UTRAN is using in TDD is not signalled; UEs have to determine it by trial and error.
3GPP
Release 6
53
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.1.2
Initiation
The system information is continuously broadcast on a regular basis in accordance with the scheduling defined for each system information block.
8.1.1.3
Reception of SYSTEM INFORMATION messages by the UE
The UE shall read SYSTEM INFORMATION messages broadcast on a BCH transport channel in idle mode and in the connected mode in states CELL_FACH, CELL_PCH, URA_PCH and CELL_DCH (TDD only). In addition, UEs in FDD mode which support simultaneous reception of one SCCPCH and one DPCH shall read system information on a FACH transport channel when in CELL_DCH state. In idle mode and connected mode different combinations of system information blocks are valid. The UE shall acquire the system information blocks that are needed according to table 8.1.1. The UE may store system information blocks with cell, PLMN or Equivalent PLMN area scope (including their value tag if applicable) for different cells and different PLMNs, to be used if the UE returns to these cells. The UE shall consider all stored system information blocks as invalid after it has been switched off. Some information obtained from system information may be stored by the UE or in the USIM for use in a stored information cell selection. When selecting a new cell the UE shall consider all current system information blocks with area scope cell to be invalid. If the UE has stored valid system information blocks for the newly selected cell, the UE may set those as current system information blocks. After selecting a new cell and this cell broadcasts an IE "PLMN Identity" in the MIB which is different from the IE "PLMN Identity" broadcast in the MIB in the previously selected cell, the UE shall consider all current system information blocks with area scope PLMN to be invalid. If the UE has previously stored valid system information blocks for the selected cell of the new PLMN, the UE may set those as current system information blocks. When NAS informs AS about a new selected PLMN, the UE shall consider all stored system information blocks with area scope Equivalent PLMN to be invalid.
8.1.1.4
Void
8.1.1.5
Actions upon reception of the Master Information Block and Scheduling Block(s)
When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate the master information block in the cell. Upon reception of the master information block, the UE shall: 1> if the IE "Multiple PLMN List" is not present in the Master Information Block: 2> consider the IE "PLMN identity" in the Master Information Block as the PLMN identity of the cell. 1> else: 2> consider the PLMN identities in the IE "Multiple PLMN List" as the PLMN identities of the cell; 2> when reading the "Multiple PLMN List", read all the PLMN identities in the list as follows: 3> if the IE "MIB PLMN Identity" is set to TRUE: 4> read the "PLMN identity" IE in the MIB and consider it as a part of the "Multiple PLMN List". 3> if the IE "MIB PLMN Identity" is set to FALSE: 4> not consider the "PLMN identity" IE in the MIB as a part of the "Multiple PLMN List";
3GPP
Release 6
54
3GPP TS 25.331 V6.23.0 (2009-09)
4> not consider the IE "PLMN identity" in the MIB as a PLMN identity of the cell; 4> not forward the PLMN in the IE "PLMN identity" of the MIB to upper layers. 3> if the MCC is not present when reading a IE "PLMN identity with Optional MCC" in the IE "Multiple PLMN List": 4> set the MCC of this PLMN identity equal to the MCC of the closest preceding "PLMN identity with Optional MCC" in the "Multiple PLMN List" that includes an MCC; 4> or, if no such "PLMN identity with Optional MCC" exists, the UE shall set the MCC of this PLMN identity to the MCC of the "PLMN identity" IE in the Master Information Block irrespective of the value of the IE "MIB PLMN Identity". 1> if the UE is operating in "ANSI-41 mode" and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41": 2> store the ANSI-41 Information elements contained in the master information block and perform initial process for ANSI-41. 1> compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG; 1> if the value tags differ, or if no IEs for the master information block are stored: 2> store the value tag into the variable VALUE_TAG for the master information block; 2> read and store scheduling information included in the master information block. 1> if the value tags are the same the UE may use stored system information blocks and scheduling blocks using value tag that were stored for this cell and this PLMN as valid system information. For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE shall perform the following actions: 1> for all system information blocks with area scope "PLMN" or "Equivalent PLMN" that use value tags: 2> compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG for that system information block; 2> if the value tags differ, or if no IEs for the corresponding system information block are stored: 3> store the value tag read in scheduling information for that system information block into the variable VALUE_TAG; 3> read and store the IEs of that system information block. 2> if the value tags are the same the UE may use stored system information blocks using value tag that were stored in this PLMN as valid system information. 1> for all system information blocks or scheduling blocks with area scope cell that use value tags: 2> compare the value tag read in scheduling information for that system information block or scheduling block with the value stored within the variable VALUE_TAG for that system information block or scheduling block; 2> if the value tags differ, or if no IEs for the corresponding system information block or scheduling block are stored: 3> store the value tag read in scheduling information for that system information block or scheduling block into the variable VALUE_TAG; 3> read and store the IEs of that system information block or scheduling block. 2> if the value tags are the same the UE may use stored system information blocks using value tags that were stored for this cell and this PLMN as valid system information.
3GPP
Release 6
55
3GPP TS 25.331 V6.23.0 (2009-09)
1> for system information blocks which may have multiple occurrences: 2> compare the value tag and the configuration or multiple occurrence identity for the occurrence of the system information blocks read in scheduling information with the value tag and configuration or multiple occurrence identity stored within the variable VALUE_TAG: 3> if the value tags differ, or if no IEs from the occurrence with that configuration or multiple occurrence identity of the system information block are stored: 4> store the value tag read in scheduling information for that system information block and the occurrence with that configuration or multiple occurrence identity into the variable VALUE_TAG; 4> read and store the IEs of that system information block. 3> if the value tags and the configuration or multiple occurrence identity are identical to those stored, the UE may use stored occurrences of system information blocks that were stored for this cell and this PLMN as valid system information. For system information blocks, not supported by the UE, but referenced either in the master information block or in the scheduling blocks, the UE may: 1> skip reading this system information block; 1> skip monitoring changes to this system information block. If the UE: 1> receives a scheduling block at a position different from its position according to the scheduling information for the scheduling block; or 1> receives a scheduling block for which scheduling information has not been received: the UE may: 1> store the content of the scheduling block with a value tag set to the value NULL; and 1> consider the content of the scheduling block as valid until it receives the same type of scheduling block in a position according to its scheduling information or at most for 6 hours after reception. If the UE does not find a scheduling block in a position where it should be according to its scheduling information, but a transport block with correct CRC was found at that position, the UE shall: 1> read the scheduling information for this scheduling block. If the UE does not find the master information block in a position fulfilling: SFN mod 32 = 0 but a transport block with correct CRC was found at that position), the UE shall: 1> consider the master information block as not found; and 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". NOTE: This permits a different repetition for the MIB in later versions for FDD. In TDD it allows for a variable SIB_REP in this and future releases.
If system information block type 1 is not scheduled on BCH, and system information block type 13 is not scheduled on BCH, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
3GPP
Release 6
56
3GPP TS 25.331 V6.23.0 (2009-09)
If the UE only supports GSM-MAP but finds a cell that broadcasts System Information Block type 13 but not System Information Block type 1, the UE shall: 1> consider the cell barred. If: system information block type 1 is not scheduled on BCH; and the UE is operating in "GSM-MAP mode"; and the IE "PLMN type" in the Master Information Block has the value "GSM-MAP" or "GSM-MAP and ANSI-41":
the UE shall: 1> indicate to upper layers that no CN system information is available. If in idle mode and System Information Block type 3 is not scheduled on BCH, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". If in connected mode and System Information Block type 3 is not scheduled on BCH, and System Information Block type 4 is not scheduled on BCH, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". If in idle mode and neither System Information Block type 5 nor type 5bis is scheduled on BCH, or System Information Block type 5 or type 5bis is scheduled but IE "AICH info" (FDD) or IE "PICH info" is not present, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". If in connected mode and neither System Information Block type 5 nor type 5bis is scheduled on BCH, and System Information Block type 6 is not scheduled on BCH, or any of System Information Block type 5, type 5bis or type 6 is scheduled but IE "AICH info" (FDD) or IE "PICH info" is not present, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". If System Information Block type 7 is not scheduled on BCH, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". In 3.84 Mcps TDD, if System Information Block type 14 is not scheduled on BCH, the UE shall: 1> consider the cell to be barred according to [4]; and 1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". If System Information Block type 5 and System Information Block type 5bis are both scheduled on BCH: 1> the UE behaviour is unspecified.
3GPP
Release 6
57
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.1.6
Actions upon reception of system information blocks
The UE may use the scheduling information included within the master information block and the scheduling blocks to locate each system information block to be acquired. The UE should only expect one occurrence of the scheduling information for a system information block in the master information block and any of the scheduling blocks except for System Information Block type 16, System Information Block type 15.2 and System Information Block type 15.3, which may have multiple occurrences. However, to enable future introduction of new system information blocks, the UE shall also be able to receive system information blocks other than the ones indicated within the scheduling information. The UE may ignore contents of such system information block. If the UE: 1> receives a system information block in a position according to the scheduling information for the system information block; and 1> this system information block uses a value tag; or 1> this system information block uses a value tag and configuration or multiple occurrence identity: the UE shall: 1> store the content of the system information block together with the value of its value tag or the values of configuration and multiple occurrence identity and the associated value tag in the scheduling information for the system information block; and 1> consider the content of the system information block valid until, if used, the value tag in the scheduling information for the system information block is changed or at most for 6 hours after reception. If the UE: 1> receives a system information block in a position according to the scheduling information for the system information block; and 1> this system information block does not use a value tag according to the system information block type: the UE shall: 1> store the content of the system information block; and 1> start an expiration timer using a value as defined in Table 8.1.1 for that system information block type; and 1> consider the content of the system information block valid until, the expiration timer expires. If the UE: 1> receives a system information block at a position different from its position according to the scheduling information for the system information block; or 1> receives a system information block for which scheduling information has not been received; and 1> this system information block uses a value tag: the UE may: 1> store the content of the system information block with a value tag set to the value NULL; and 1> consider the content of the system information block as valid until it receives the same type of system information block in a position according to its scheduling information or at most for 6 hours after reception. If the UE: 1> receives a system information block with multiple occurrences at a position different from its position according to the scheduling information for the system information block; or
3GPP
Release 6
58
3GPP TS 25.331 V6.23.0 (2009-09)
1> receives a system information block with multiple occurrences for which scheduling information has not been received; and 1> this system information block uses a value tag and configuration or multiple occurrence identity: the UE shall: 1> ignore this information. If the UE does not find a system information block in a position where it should be according to its scheduling information, but a transport block with correct CRC was found at that position, the UE shall read the scheduling information for this system information block. The UE shall act upon all received information elements as specified in subclause 8.6 unless specified otherwise in the following subclauses.
8.1.1.6.1
The UE should store all relevant IEs included in this system information block if the UE is operating in "GSM-MAP mode" and the IE "PLMN type" in the Master Information Block has the value "GSM-MAP" or "GSM-MAP and ANSI-41". The UE shall also: 1> check that the cell, according to information included in IE "CN common GSM-MAP NAS system information", is suitable [4]; 1> if in connected mode: 2> not forward the content of the IE "CN common GSM-MAP NAS system information" to upper layers. 1> if in idle mode: 2> forward the content of the IE "CN common GSM-MAP NAS system information" to upper layers. 1> for the IE "CN domain system information list": 2> for each IE "CN domain system information" that is present: 3> check that the cell, according to information included in IE "CN domain specific NAS system information", is suitable [4]; 3> if in connected mode: 4> not forward the content of the IE "CN domain specific NAS system information" to upper layers. 3> if in idle mode: 4> forward the content of the IE "CN domain specific NAS system information" and the IE "CN domain identity" to upper layers; 4> use the IE "CN domain specific DRX cycle length coefficient" to calculate frame number for the Paging Occasions as specified in [4]; 4> store the value of the IE "CN domain specific DRX cycle length coefficient" for use in connected mode. 2> if an IE "CN domain system information" is not present for a particular CN domain: 3> if in idle mode: 4> indicate to upper layers that no CN system information is available for that CN domain. 1> if the UE has not yet entered UTRA RRC connected mode: 2> store the values of the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS. 1> use the values stored in the variable TIMERS_AND_CONSTANTS for the relevant timers and constants.
3GPP
Release 6
59
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.1.6.2
If in connected mode the UE should store all relevant IEs included in this system information block. The UE shall: 1> if in state URA_PCH, start to perform URA updates using the information in the IE "URA identity". If in idle mode, the UE shall not use the values of the IEs in this system information block.
8.1.1.6.3
The UE should store all relevant IEs included in this system information block. The UE shall: 1> if in connected mode, and System Information Block 4 is indicated as used in the cell: 2> read and act on information sent in that block. With respect to Domain Specific Access Control, the UE shall: 1> if the IE "Multiple PLMN List" is not included in the Master Information Block: 2> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB". 1> else: 2> if the PLMN specified by the IE "PLMN Identity" of the Master Information Block is chosen by the UE: 3> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB". 2> else, if N-th (N=1..5) PLMN in the IE "Multiple PLMNs" contained in the IE "Multiple PLMN List" is chosen by the UE: 3> if the IE "Domain Specific Access Restriction List" of the IE "Domain Specific Access Restriction For Shared Network" is indicated: 4> if the IE "Domain Specific Access Restriction Parameters For OperatorN" is indicated: 5> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For OperatorN". 3> else, if the IE "Domain Specific Access Restriction Parameters For All" of the IE "Domain Specific Access Restriction For Shared Network" is indicated: 4> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For All". The UE shall apply the following handling with respect to any Access Class Barring information: 1> if in idle mode: 2> if the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", the IE "Domain Specific Access Restriction Parameters For OperatorN" or the IE "Domain Specific Access Restriction Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3, the UE shall: 3> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4]. If "no restriction" was indicated in restriction status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction"; 3> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4]. If "no restriction" was indicated in restriction
3GPP
Release 6
60
3GPP TS 25.331 V6.23.0 (2009-09)
status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction"; 3> upon transition to UTRA RRC connected, the UE shall: 4> store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released; 4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4]; 4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4]; 2> else: 3> act on the IE "Access Class Barred list" when initiating RRC Connection establishment as specified in [4]. 1> if in connected mode: 2> if the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", the IE "Domain Specific Access Restriction Parameters For OperatorN" or the IE "Domain Specific Access Restriction Parameters For All" to be applied according to the requirements above is included in the System Information Block Type 3: 3> if the variable "DSAC_PARAM is not set, the UE shall: 4> store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released; 4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS, as specified in [4]; 4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4]. 3> else (the access class barring information is stored) UE shall: 4> update the variable "DSAC_PARAM" with that Domain Specific Access Restriction Parameters; 4> act on the updated IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4]; 4> act on the updated IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4]. 2> else: 3> if the variable "DSAC_PARAM" is set, the UE shall: 4> clear the variable "DSAC_PARAM"; 4> act as if no Access Class is barred.
8.1.1.6.4
If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall:
3GPP
Release 6
61
3GPP TS 25.331 V6.23.0 (2009-09)
1> if in connected mode: 2> read and act on information sent in this block; 2> read the System Information Block Type 3 for any Access Class Barring information and act on that information as described in subclause 8.1.1.6.3. If in idle mode, the UE shall not use the values of the IEs included in this system information block.
8.1.1.6.5
System Information Block type 5 and 5bis
The UE should store all relevant IEs included in this system information block. The UE shall: 1> if the IE "Frequency band indicator" is included and if the frequency band indicated in the IE is not part of the frequency bands supported in the UE radio access capability; or 1> if the IE "Frequency band indicator 2" is included and if the frequency band indicated in the IE is not part of the frequency bands supported in the UE radio access capability; or 1> if the IE "Frequency band indicator" is included and set to "extension indicator", and the UE does not support any of the frequency bands that can be indicated by the IE "Frequency band indicator 2" (i.e., Band VIII or beyond); or 1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 2110MHz-2170MHz, and Band I is not part of the frequency bands supported by the UE in the UE radio access capability, or 1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 1805MHz-1880MHz, and Band III is not part of the frequency bands supported by the UE in the UE radio access capability: 2> consider the cell to be barred according to [4]; and 2> consider the barred cell as using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". 1> if the cell belongs to any frequency band equal to Band IV or greater and neither the IE "Frequency band indicator" nor the IE "Frequency band indicator 2" are included in System Information Block type 5 or in System Information Block type 5bis: 2> the UE behaviour is not specified. 1> if in connected mode, and System Information Block type 6 is indicated as used in the cell: 2> read and act on information sent in System Information Block type 6. 1> replace the TFS of the RACH with the one stored in the UE if any; 1> let the physical channel(s) of type PRACH given by the IE(s) "PRACH info" be the default in uplink for the PRACH if UE is in CELL_FACH state; 1> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" (FDD only) when given allocated PRACH is used; 1> if the IE "Additional Dynamic Transport Format Information for CCCH" is included for the selected PRACH: 2> use this transport format for transmission of the CCCH. 1> else: 2> use the first instance of the list of transport formats as in the IE "RACH TFS" for the used RACH received in the IE "PRACH system information list" when using the CCCH. 1> replace the TFS of the FACH/PCH with the one stored in the UE if any;
3GPP
Release 6
62
3GPP TS 25.331 V6.23.0 (2009-09)
1> select a Secondary CCPCH as specified in [4] and in subclause 8.5.19, and start to receive the physical channel of type PICH associated with the PCH carried by the selected Secondary CCPCH using the parameters given by the IE "PICH info" if UE is in Idle mode or in CELL_PCH or URA_PCH state; 1> start to monitor its paging occasions on the selected PICH if UE is in Idle mode or in CELL_PCH or URA_PCH state; 1> start to receive the selected physical channel of type Secondary CCPCH using the parameters given by the IE(s) "Secondary CCPCH info" if UE is in CELL_FACH state; 1> in 3.84 Mcps TDD: 2> use the IE "TDD open loop power control" as defined in subclause 8.5.7 when allocated PRACH is used. 1> in TDD: 2> if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included: 3> store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. For every configuration, for which the IE "SFN Time info" is included, the information shall be stored for the duration given there. If a UE is a 12 kbps class UE according to [35] and the UE has a lower capability than required to support all transport channel configurations mapped on a specific Secondary CCPCH, the UE shall at a certain time instant still be able to decode those transport channels mapped on this Secondary CCPCH that do match the capability supported by the UE. The UE shall use the TFCI bits for that Secondary CCPCH, to distinguish a transport channel configuration that is supported by the UE from a transport channel configuration that is not supported by the UE. In particular if the UE is a 12 kbps class UE according to [35] and it does not support the processing requirement at a given point in time for a Secondary CCPCH, it shall still be able to decode the same Secondary CCPCH when the processing requirement is consistent with the UE capability. Or if the UE does not support the number of TFs or the coding of a certain transport channel on a Secondary CCPCH, it shall still be able to decode other transport channels mapped on the same Secondary CCPCH that is consistent with what is supported by the UE. The UE shall: 1> if the IE "Secondary CCPCH system information MBMS" is included: 2> apply the Secondary CCPCH and FACH indicated by the IE "FACH carrying MCCH" for receiving MCCH. 1> otherwise, if the IE "Secondary CCPCH system information" includes the IE "MCCH configuration information": 2> apply the Secondary CCPCH and FACH indicated by the IE MCCH configuration information for receiving MCCH.
8.1.1.6.6
If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall: 1> if the IE "Frequency band indicator" is included: 2> if the frequency band indicated in the IE is not part of the frequency bands supported in the UE radio access capability; or 2> if the IE "Frequency band indicator 2" is included and if the frequency band indicated in the IE is not part of the frequency bands supported in the UE radio access capability; or 2> if the IE "Frequency band indicator" is included and set to "extension indicator", and the UE does not support any of the frequency bands that can be indicated by the IE "Frequency band indicator 2" (i.e., Band VIII or beyond): 3> consider the cell to be barred according to [4]; and 3> consider the barred cell as using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
3GPP
Release 6
63
3GPP TS 25.331 V6.23.0 (2009-09)
1> replace the TFS of the RACH with the one stored in the UE if any; 1> let the physical channel(s) of type PRACH given by the IE(s) "PRACH info" be the default in uplink if UE is in CELL_FACH state. If the IE "PRACH info" is not included, the UE shall read the corresponding IE(s) in System Information Block type 5 or System Information Block type 5bis and use that information to configure the PRACH; 1> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" when associated PRACH is used. If the IE "AICH info" is not included, the UE shall read the corresponding IE in System Information Block type 5 or System Information Block type 5bis and use that information (FDD only); 1> if the IE "Additional Dynamic Transport Format Information for CCCH" is included for the selected PRACH: 2> use this transport format for transmission of the CCCH (FDD only). 1> else: 2> use the first instance of the list of transport formats as in the IE "RACH TFS" for the used RACH received in the IE "PRACH system information list" when using the CCCH (FDD only). 1> replace the TFS of the FACH/PCH with the one stored in the UE if any; 1> select a Secondary CCPCH as specified in [4] and in subclause 8.5.19, and start to receive the physical channel of type PICH associated with the PCH carried by the selected Secondary CCPCH using the parameters given by the IE "PICH info" if the UE is in CELL_PCH or URA_PCH state. If the IE "PICH info" is not included, the UE shall read the corresponding IE in System Information Block type 5 or System Information Block type 5bis and use that information; 1> start to monitor its paging occasions on the selected PICH if the UE is in CELL_PCH or URA_PCH state; 1> start to receive the selected physical channel of type Secondary CCPCH using the parameters given by the IE(s) "Secondary CCPCH info" if the UE is in CELL_FACH state. If the IE "Secondary CCPCH info" is not included, the UE shall read the corresponding IE(s) in System Information Block type 5 or System Information Block type 5bis and use that information; 1> in 3.84 Mcps TDD: use the IE "TDD open loop power control" as defined in subclause 8.5.7; 1> in TDD: if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included, store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. For every configuration, for which the IE "SFN Time info" is included, the information shall be stored for the duration given there. If in idle mode, the UE shall not use the values of the IEs in this system information block. If a UE is a 12 kbps class UE according to [35] and the UE has a lower capability than required to support all transport channel configurations mapped on a specific Secondary CCPCH, the UE shall at a certain time instant still be able to decode those transport channels mapped on this Secondary CCPCH that do match the capability supported by the UE. The UE shall use the TFCI bits for that Secondary CCPCH, to distinguish a transport channel configuration that is supported by the UE from a transport channel configuration that is not supported by the UE. In particular if the UE is a 12 kbps class UE according to [35] and it does not support the processing requirement at a given point in time for a Secondary CCPCH, it shall still be able to decode the same Secondary CCPCH when the processing requirement is consistent with the UE capability. Or if the UE does not support the number of TFs or the coding of a certain transport channel on a Secondary CCPCH, it shall still be able to decode other transport channels mapped on the same Secondary CCPCH that is consistent with what is supported by the UE.
8.1.1.6.7
The UE should store all relevant IEs included in this system information block.
8.1.1.6.8
Void
3GPP
Release 6
64
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.1.6.9
Void
8.1.1.6.10
Void
8.1.1.6.11
The UE should store all relevant IEs included in this system information block. The UE shall: 1> if in idle mode: 2> clear the variable MEASUREMENT_IDENTITY. 1> if IE "FACH measurement occasion info" is included: 2> act as specified in subclause 8.6.7. 1> else: 2> may perform inter-frequency/inter-RAT measurements or inter-frequency/inter-RAT cell re-selection evaluation, if the UE capabilities permit such measurements while simultaneously receiving the S-CCPCH of the serving cell. 1> clear the variable CELL_INFO_LIST; 1> act upon the received IE "Intra-frequency cell info list"/"Inter-frequency cell info list"/"Inter-RAT cell info list" as described in subclause 8.6.7.3; 1> if the IE "Inter-frequency RACH reporting information" is included in the system information block: 2> read the IE and use that information for the inter-frequency measurements as specified in subclause 8.5.23. 1> if in idle mode; or 1> if in connected mode and if System Information Block type 12 is not broadcast in the cell: 2> if no intra-frequency measurement stored in the variable MEASUREMENT_IDENTITY was set up or modified through a MEASUREMENT CONTROL message: 3> if included, store the IE "Intra-frequency reporting quantity" and the IE "Intra-frequency measurement reporting criteria" or "Periodical reporting criteria" in order to activate reporting when state CELL_DCH is entered in the variable MEASUREMENT_IDENTITY. The IE "Cells for measurement" is absent for this measurement. The IE "Measurement Validity" is absent for this measurement after a state transition to CELL_DCH; 1> if in connected mode and if System Information Block type 12 is not broadcast in the cell: 2> read the IE "Traffic volume measurement information"; 2> if no traffic volume measurement with the measurement identity indicated in the IE "Traffic volume measurement system information" was set up or modified through a MEASUREMENT CONTROL message: 3> update the variable MEASUREMENT_IDENTITY with the measurement information received in that IE. 1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IE "intrafrequency cell info list", the IE "inter-frequency cell info list" or the IE "inter-RAT cell info list" in System Information Block type 11: 2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information". 1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:
3GPP
Release 6
65
3GPP TS 25.331 V6.23.0 (2009-09)
2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 11: 3> use the default values specified for the IE "HCS neighbouring cell information" for that cell. 2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 11: 3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 11. 1> if the value of the IE "Cell selection and reselection quality measure" is different from the value of the IE "Cell selection and reselection quality measure" obtained from System Information Block type 3 or System Information Block type 4: 2> use the value of the IE from this System Information Block and ignore the value obtained from System Information Block type 3 or System Information Block type 4. 1> if in connected mode, and System Information Block type 12 is indicated as used in the cell: 2> read and act on information sent in System Information Block type 12 as indicated in subclause 8.1.1.6.12.
8.1.1.6.11a
System Information Block type 11bis
If supported by the UE the UE should store all relevant IEs included in this system information block. The UE shall: 1> after reception of SIB 11 act upon the received IEs "Intra-frequency cell info list", "Inter-frequency cell info list" and "Inter-RAT cell info list" as described in subclause 8.6.7.3; 1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IEs "New Intrafrequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis: 2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information". 1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following: 2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IEs "New Intrafrequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis: 3> use the default values specified for the IE "HCS neighbouring cell information" for that cell. 2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IEs "New Intrafrequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis: 3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 11bis.
8.1.1.6.12
If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall: 1> after reception of System Information Block type 11; and 1> after reception of System Information Block type 11bis, if broadcast in the cell and supported by the UE: 2> update the variable MEASUREMENT_IDENTITY with the measurement information in the received IEs unless specified otherwise. 1> if IE "FACH measurement occasion info" is included:
3GPP
Release 6
66
3GPP TS 25.331 V6.23.0 (2009-09)
2> act as specified in subclause 8.6.7. 1> else: 2> may perform inter-frequency/inter-RAT measurements or inter-frequency/inter-RAT cell re-selection evaluation, if the UE capabilities permit such measurements while simultaneously receiving the S-CCPCH of the serving cell. 1> act upon the received IE "Intra-frequency cell info list"/"Inter-frequency cell info list"/"Inter-RAT cell info list" as described in subclause 8.6.7.3; 1> if any of the IEs "Intra-frequency measurement quantity", "Intra-frequency reporting quantity for RACH reporting", "Maximum number of reported cells on RACH" or "Reporting information for state CELL_DCH" are not included in the system information block: 2> read the corresponding IE(s) in system information block type 11 and use that information for the intrafrequency measurement. 1> if the IE "Inter-frequency RACH reporting information" is included in this system information block or in System Information Block type 11: 2> if the IE is not included in the system information block, read the corresponding IE(s) in System Information Block type 11; 2> use the received information for the inter-frequency measurements as specified in subclause 8.5.23. 1> if included in this system information block or in System Information Block type 11: 2> if no intra-frequency measurement in the variable MEASUREMENT_IDENTITY was set up or modified through a MEASUREMENT CONTROL message: 3> store the IE "Intra-frequency reporting quantity" and the IE "Intra-frequency measurement reporting criteria" or "Periodical reporting criteria" in order to activate reporting when state CELL_DCH is entered in the variable MEASUREMENT_IDENTITY. The IE "Cells for measurement" is absent for this measurement. The IE "Measurement Validity" is absent for this measurement after a state transition to CELL_DCH; 1> if the IE "Traffic volume measurement system information" is not included in this system information block: 2> read the corresponding IE in System Information Block type 11. 1> if the IE "Traffic volume measurement system information" was received either in this system information block or in System Information Block type 11: 2> if no traffic volume measurement with the measurement identity indicated in the IE "Traffic volume measurement system information" was set up or modified through a MEASUREMENT CONTROL message: 3> update the variable MEASUREMENT_IDENTITY with the measurement information received in that IE. 1> if in CELL_FACH state: 2> start or continue the traffic volume measurements stored in the variable MEASUREMENT_IDENTITY that are valid in CELL_FACH state. 1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IE "Intrafrequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 12: 2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information". 1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:
3GPP
Release 6
67
3GPP TS 25.331 V6.23.0 (2009-09)
2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 12: 3> use the default values specified for the IE "HCS neighbouring cell information" for that cell. 2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 12: 3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 12. 1> if the value of the IE "Cell selection and reselection quality measure" is different from the value of the IE "Cell selection and reselection quality measure" obtained from System Information Block type 3 or System Information Block type 4: 2> use the value of the IE from this System Information Block and ignore the value obtained from System Information Block type 3 or System Information Block type 4. If in idle mode, the UE shall not use the values of the IEs in this system information block.
8.1.1.6.13
If in idle or connected mode, the UE should store all relevant IEs included in this system information block except for the IEs "CN domain specific DRX cycle length coefficient", "UE timers and constants in idle mode" and "Capability update requirement" which shall be stored only in the idle mode case. The UE shall read System Information Block type 13 and the associated System Information Block types 13.1, 13.2, 13.3 and 13.4 only when the UE is operating in "ANSI-41 mode" and the IE "PLMN type" in the Master Information Block has the value "ANSI-41" or "GSM-MAP and ANSI-41". The UE shall also: 1> forward the content of the IE "CN domain specific NAS system information" to the non-access stratum entity indicated by the IE "CN domain identity"; 1> use the IE "CN domain specific DRX cycle length coefficient" to calculate frame number for the Paging Occasions and Page indicator as specified in [4]. Refer to TIA/EIA/IS-2000.5-A for actions on information contained in System Information Block types 13.1, 13.2, 13.3 and 13.4.
8.1.1.6.14
This system information block type is used only in 3.84 Mcps TDD. The UE should store all relevant IEs included in this system information block. The UE shall: 1> use the IE "UL Timeslot Interference" to calculate PRACH, DPCH and PUSCH transmit power for TDD uplink open loop power control as defined in subclause 8.5.7.
8.1.1.6.15
If the UE is in idle or connected mode, and supports GPS location services it should store all relevant IEs included in this system information block. The UE shall: 1> if the IE "GPS Data ciphering info" is included: 1> act as specified in the subclause 8.6.7.19.4.- act upon the received IE "Reference position" as specified in subclause 8.6.7.19.3.8; 1> act upon the received IE "GPS reference time" as specified in subclause 8.6.7.19.3.7; 1> if IE "Satellite information" is included: 2> act upon this list of bad satellites as specified in subclause 8.6.7.19.3.6.
3GPP
Release 6
68
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
For efficiency purposes, the UTRAN should broadcast System Information Block type 15 if it is broadcasting System Information Block type 15.2. System Information Block type 15.1
8.1.1.6.15.1
The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall: 1> act on "DGPS information" in the IE "DGPS Corrections" in a similar manner as specified in [13] except that the scale factors for PRC and RRC are different; 1> act upon the received IE " UE Positioning GPS DGPS corrections" as specified in subclause 8.6.7.19.3.3. In this version of the specification, the UE shall: 1> ignore the following IEs: "Delta PRC2", "Delta RRC2", "Delta PRC3" and "Delta RRC3". 8.1.1.6.15.2 System Information Block type 15.2
For System Information Block type 15.2 multiple occurrences may be used; one occurrence for one satellite. To identify the different occurrences, the scheduling information for System Information Block type 15.2 includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall: 1> compare for each occurrence the value tag of the stored occurrence, if any, with the occurrence value tag included in the IE "SIB occurrence identity and value tag" for the occurrence of the System Information Block with the same occurrence identity; 1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different: 2> store the occurrence information together with its identity and value tag for later use. 1> in case an occurrence with the same identity but different value tag was stored: 2> overwrite this one with the new occurrence read via system information for later use. 1> interpret IE "Transmission TOW" as a very coarse estimate of the current time, i.e., the approximate GPS timeof-week when the message is broadcast; 1> interpret IE "SatID" as the satellite ID of the data from which this message was obtained; 1> act upon the received IEs "Sat ID" and "GPS Ephemeris and Clock Corrections Parameter" as specified in subclause 8.6.7.19.3.4. The IE "Transmission TOW" may be different each time a particular SIB occurrence is transmitted. The UTRAN should not increment the value tag of the SIB occurrence if the IE "Transmission TOW" is the only IE that is changed. The UE may not need to receive all occurrences before it can use the information from any one occurrence. 8.1.1.6.15.3 System Information Block type 15.3
For System Information Block type 15.3 multiple occurrences may be used; one occurrence for each set of satellite data. To identify the different occurrences, the scheduling information for System Information Block type 15.3 includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall: 1> compare for each occurrence the value tag of the stored occurrence, if any, with the occurrence value tag included in the IE "SIB occurrence identity and value tag" for the occurrence of the System Information Block with the same occurrence identity; 1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different: 2> store the occurrence information together with its identity and value tag for later use.
3GPP
Release 6
69
3GPP TS 25.331 V6.23.0 (2009-09)
1> in case an occurrence with the same identity but different value tag was stored: 2> overwrite this one with the new occurrence read via system information for later use. 1> interpret IE "Transmission TOW" as a very coarse estimate of the current time, i.e., the approximate GPS timeof-week when the message is broadcast; 1> if the IE "GPS Almanac and Satellite Health" is included: 2> interpret IE "SatMask" as the satellites that contain the pages being broadcast in this message; 2> interpret IE "LSB TOW" as the least significant 8 bits of the TOW ([12]); 2> act upon the received IE "GPS Almanac and Satellite Health" as specified in subclause 8.6.7.19.3.2. 1> if the IE "GPS ionospheric model" is included: 2> act upon the received IE "GPS ionospheric model" as specified in subclause 8.6.7.19.3.5. 1> if the IE "GPS UTC model" is included: 2> act upon the received IE "GPS UTC model" as specified in subclause 8.6.7.19.3.9. The IE "Transmission TOW" may be different each time a particular SIB occurrence is transmitted. The UTRAN should not increment the value tag of the SIB occurrence if the IE "Transmission TOW" is the only IE that is changed. One SIB occurrence value tag is assigned to the table of subclause 10.2.48.8.18.3. The UE may not need to receive all occurrences before it can use the information for any one occurrence. 8.1.1.6.15.4 System Information Block type 15.4
If the UE is in idle mode or connected mode, the UE shall: 1> if the IE "OTDOA Data ciphering info" is included: 2> act as specified in subclause 8.6.7.19.4. If the UE is in connected mode, the UE shall: 1> act as specified in subclause 8.6.7.19.2. 8.1.1.6.15.5 System Information Block type 15.5
If the UE is in idle or connected mode, the UE shall: 1> if the UE supports UE-based OTDOA positioning: 2> act as specified in subclause 8.6.7.19.2a.
8.1.1.6.16
For System Information Block type 16 multiple occurrences may be used; one occurrence for each predefined configuration. To identify the different predefined configurations, the scheduling information for System Information Block type 16 includes IE "Predefined configuration identity and value tag". The UE should store all relevant IEs included in this system information block. The UE shall: 1> compare for each predefined configuration the value tag of the stored predefined configuration with the preconfiguration value tag included in the IE "Predefined configuration identity and value tag" for the occurrence of the System Information Block with the same predefined configuration identity; 1> in case the UE has no predefined configuration stored with the same identity: 2> store the predefined configuration information together with its identity and value tag for later use e.g. during handover to UTRAN.
3GPP
Release 6
70
3GPP TS 25.331 V6.23.0 (2009-09)
1> in case a predefined configuration with the same identity but different value tag was stored: 2> overwrite this one with the new configuration read via system information for later use e.g. during handover to UTRAN. The above handling applies regardless of whether the previously stored predefined configuration information has been obtained via UTRA or via another RAT. The UE is not required to complete reading of all occurrences of System Information Block type 16 before initiating RRC connection establishment. The UE is not required to store more than maxPredefConfig preconfigurations even in the case of multiple equivalent PLMNs.
8.1.1.6.17
This system information block type is used only for TDD. If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall: 1> if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included, store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. This information shall become invalid after the time specified by the repetition period (SIB_REP) for this system information block. If in idle mode, the UE shall not use the values of the IEs in this system information block.
8.1.1.6.18
If the System Information Block type 18 is present, a UE shall obtain knowledge of the PLMN identity of the neighbour cells to be considered for cell reselection, and shall behave as specified in this subclause and in subclause 8.5.14a. The UE should store all the relevant IEs included in this system information block. A UE in idle mode shall act according to the following rules: 1> if System Information Block type 11bis is supported by the UE; and System Information Block type 11bis is scheduled on BCH; and the IE "Idle mode PLMN identities for SIB 11bis" is present: 2> any PLMN list of a given type (IEs "PLMNs of intra-frequency cells list", "PLMNs of inter-frequency cells list", "PLMNs of inter-RAT cell lists") included in the IE "Idle mode PLMN identities for SIB 11bis" is paired with the list of cells of the same type derived from System Information Block type 11 and System Information Block 11bis; 1> else: 2> any PLMN list of a given type (IEs "PLMNs of intra-frequency cells list", "PLMNs of inter-frequency cells list", "PLMNs of inter-RAT cell lists") included in the IE "Idle mode PLMN identities" is paired with the list of cells of the same type derived from System Information Block type 11 and System Information Block type 11bis if scheduled on BCH and supported by the UE. 1> the PLMN identity located at a given rank in the PLMN list is that of the cell with the same ranking in the paired list of cells, the cells being considered in the increasing order of their associated identities ("Intra-frequency cell id", "Inter-frequency cell id", "Inter-RAT cell id"); 1> if no identity is indicated for the first PLMN in a list, the UE shall assume that the neighbouring cell broadcasts the same PLMN configuration (i.e. IE "PLMN Identity" and IE "Multiple PLMN List") as the current cell; 1> if no identity is indicated for another entry in the list, the UE shall assume that the neighbouring cell broadcasts the same PLMN configuration (i.e. IE "PLMN Identity" and IE "Multiple PLMN List") as the previous cell in the list; 1> if the number of identities in a PLMN list exceeds the number of neighbour cells in the paired list (if any), the extra PLMN identities are considered as unnecessary and ignored;
3GPP
Release 6
71
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the number of identities in a PLMN list (if any) is lower than the number of neighbour cells in the paired list, the missing PLMN identities are replaced by the PLMN configuration for the last cell in the list. A UE in connected mode shall act in the same manner as a UE in idle mode with the following modifications: 1> if System Information Block type 11bis is supported by the UE; and System Information Block type 11bis is scheduled on BCH: 2> the PLMN lists to be considered are the ones included, when present, in the IE "Connected mode PLMN identities for SIB 11bis"; 2> otherwise, the UE shall use, in place of any missing list, when present, the corresponding one in the IE "Idle mode PLMN identities for SIB11bis"; 2> otherwise, the UE shall use, in place of any missing list, when present, the corresponding one in the IE "Connected mode PLMN identities"; 2> otherwise, the UE shall use, in place of any missing list, the corresponding one in the IE "Idle mode PLMN identities"; 1> else: 2> the PLMN lists to be considered are the ones included, when present, in the IE "Connected mode PLMN identities"; 2> otherwise, the UE shall use, in place of any missing list, the corresponding one in the IE "Idle mode PLMN identities"; 1> the paired lists of cells are the ones derived from System Information Block type 11, and System Information Block 11bis if scheduled on BCH and supported by the UE, and System Information Block type 12 if present.
8.1.1.7
Modification of system information
For System Information Block type 15.2, 15.3 and 16 that may have multiple occurrences, the UE shall handle each occurrence independently as specified in the previous; that is each occurrence is handled as a separate system information block. NOTE: It should be noted that for the proper operation of the BCCH Modification Information sent on a PCH, the System Information should not be changed more frequently than can be accommodated by mobile stations operating at the maximum DRX cycle length supported by the UTRAN.
8.1.1.7.1
Modification of system information blocks using a value tag
Upon modifications of system information blocks using value tags, UTRAN should notify the new value tag for the master information block in the IE "BCCH modification info", transmitted in the following way: 1> to reach UEs in idle mode, CELL_PCH state and URA_PCH state, the IE "BCCH modification info" is contained in a PAGING TYPE 1 message transmitted on the PCCH in all paging occasions in the cell; 1> to reach UEs in CELL_FACH state or TDD UEs in CELL_DCH with S-CCPCH assigned, the IE "BCCH modification info" is contained in a SYSTEM INFORMATION CHANGE INDICATION message transmitted on the BCCH mapped on at least one FACH on every Secondary CCPCH in the cell. Upon reception of a PAGING TYPE 1 message or a SYSTEM INFORMATION CHANGE INDICATION message containing the IE "BCCH modification info" containing the IE "MIB value tag" but not containing the IE "BCCH modification time", the UE shall perform actions as specified in subclause 8.1.1.7.3. If the IE "BCCH modification time" is included the UE shall perform actions as specified in subclause 8.1.1.7.2.
8.1.1.7.2
Synchronised modification of system information blocks
For modification of some system information elements, e.g. reconfiguration of the channels, it is important for the UE to know exactly when a change occurs. In such cases, the UTRAN should notify the SFN when the change will occur as
3GPP
Release 6
72
3GPP TS 25.331 V6.23.0 (2009-09)
well as the new value tag for the master information block in the IE "BCCH modification info" transmitted in the following way: 1> To reach UEs in idle mode, CELL_PCH state and URA_PCH state, the IE "BCCH modification info" is contained in a PAGING TYPE 1 message transmitted on the PCCH in all paging occasions in the cell; 1> To reach UEs in CELL_FACH state, the IE "BCCH modification info" is contained in a SYSTEM INFORMATION CHANGE INDICATION message transmitted on the BCCH mapped on at least one FACH on every Secondary CCPCH in the cell. Upon reception of a PAGING TYPE 1 message or a SYSTEM INFORMATION CHANGE INDICATION message containing the IE "BCCH modification info" containing the IE "MIB value tag" and containing the IE "BCCH modification time", the UE shall: 1> perform the actions as specified in subclause 8.1.1.7.3 at the time, indicated in the IE "BCCH Modification Info".
8.1.1.7.3
The UE shall:
Actions upon system information change
1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG. 1> if the value tags differ: 2> read the master information block on BCH; 2> if the value tag of the master information block in the system information is the same as the value in IE "MIB value tag" in "BCCH modification info" but different from the value tag stored in the variable VALUE_TAG: 3> perform actions as specified in subclause 8.1.1.5. 2> if the value tag of the master information block in the system information is the same as the value tag stored in the variable VALUE_TAG: 3> for the next occurrence of the master information block: 4> perform actions as specified in subclause 8.1.1.7.3 again. 2> if the value tag of the master information block in the system information is different from the value tag stored in the variable VALUE_TAG, and is different from the value in IE "MIB value tag" in "BCCH modification info": 3> perform actions as specified in subclause 8.1.1.5; 3> if (VTCI-VTMIB) mod 8 < 4, where VTCI is the value tag in the IE "MIB value tag" in "BCCH modification info" and VTMIB is the value tag of the master information block in the system information: 4> for the next occurrence of the master information block: 5> perform actions as specified in subclause 8.1.1.7.3 again.
8.1.1.7.4
Actions upon expiry of a system information expiry timer
When the expiry timer of a system information block not using a value tag expires the UE shall: 1> consider the content of the system information block invalid; 1> re-acquire the system information block again before the content can be used;
3GPP
Release 6
73
3GPP TS 25.331 V6.23.0 (2009-09)
In FDD for system information blocks other than System Information Block type 7, or in states other than CELL_FACH, or in TDD for system information blocks other than System Information Block type 14, or in states other than CELL_FACH or CELL_DCH the UE may: 1> postpone reading the system information block until the content is needed. In FDD for System Information Block type 7, while in state CELL_FACH, and in TDD for System Information Block type 14, while in state CELL_FACH or CELL DCH the UE shall always keep an up to date version of the relevant IEs, unless this is not possible because system information can not be received due to bad radio conditions.
8.1.2
Paging
UE UTRAN
PAGING TYPE 1
Figure 8.1.2-1: Paging
8.1.2.1
General
This procedure is used to transmit paging information to selected UEs in idle mode, CELL_PCH or URA_PCH state using the paging control channel (PCCH). Upper layers in the network may request paging, to e.g. establish a signalling connection. UTRAN may initiate paging for UEs in CELL_PCH or URA_PCH state to trigger a cell update procedure. In addition, UTRAN may initiate paging for UEs in idle mode, CELL_PCH and URA_PCH state to trigger reading of updated system information. UTRAN may also initiate paging for UEs in CELL_PCH and URA_PCH state to release the RRC connection.
8.1.2.2
Initiation
UTRAN initiates the paging procedure by transmitting a PAGING TYPE 1 message on an appropriate paging occasion on the PCCH. UTRAN may repeat transmission of a PAGING TYPE 1 message to a UE in several paging occasions to increase the probability of proper reception of a page. UTRAN may page several UEs in the same paging occasion by including one IE "Paging record" for each UE in the PAGING TYPE 1 message. For CN originated paging, UTRAN should set the IE "Paging cause" to the cause for paging received from upper layers. If no cause for paging is received from upper layers, UTRAN should set the value "Terminating cause unknown". UTRAN may also indicate that system information has been updated, by including the value tag of the master information block in the IE "BCCH modification info" in the PAGING TYPE 1 message. In this case, UTRAN may omit the IEs "Paging record".
8.1.2.3
Reception of a PAGING TYPE 1 message by the UE
A UE in idle mode, CELL_PCH state or URA_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in idle mode, the paging occasions are specified in [4] and depend on the IE "CN domain specific DRX cycle length coefficient", as specified in subclause 8.6.3.1a. For a UE in CELL_PCH state or URA_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC State Indicator", as specified in subclauses 8.6.3.2 and 8.6.3.3 respectively. When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below. If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:
3GPP
Release 6
74
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Used paging identity" is a CN identity: 2> compare the IE "UE identity" with all of its allocated CN UE identities: 2> if one match is found: 3> indicate reception of paging; and 3> forward the IE "CN domain identity", the IE "UE identity" and the IE "Paging cause" to the upper layers. 1> otherwise: 2> ignore that paging record. If the UE is in connected mode, for each occurrence of the IE "Paging record" included in the message the UE shall: 1> if the IE "Used paging identity" is a UTRAN single UE identity and if this U-RNTI is the same as the U-RNTI allocated to the UE stored in the UE variable U_RNTI: 2> if the optional IE "CN originated page to connected mode UE" is included: 3> indicate reception of paging; and 3> forward the IE "CN domain identity", the IE "Paging cause" and the IE "Paging record type identifier" to the upper layers. 2> if the IE "Release indicator" in the IE "RRC connection release information" has the value "Release": 3> release all its radio resources; 3> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to the upper layers; 3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> clear the variable ESTABLISHED_RABS; 3> pass the value of the IE "Release cause" received in the IE "Release information" to upper layers; 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode; 3> and the procedure ends. 2> otherwise: 3> perform a cell update procedure with cause "paging response" as specified in subclause 8.3.1.2. 2> ignore any other remaining IE "Paging record" that may be present in the message. 1> if the IE "Used paging identity" is a UTRAN group identity and there is a group identity match according to subclause 8.6.3.13: 2> if the IE "Release indicator" in the IE "RRC connection release information" has the value "Release": 3> release all its radio resources; 3> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to the upper layers; 3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> clear the variable ESTABLISHED_RABS; 3> pass the value of the IE "Release cause" received in the IE Release information to upper layers;
3GPP
Release 6
75
3GPP TS 25.331 V6.23.0 (2009-09)
3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode; 3> and the procedure ends. 2> otherwise: 3> perform a cell update procedure with cause "paging response" as specified in subclause 8.3.1.2. 2> ignore any other remaining IE "Paging record" that may be present in the message. 1> otherwise: 2> ignore that paging record. If the IE "BCCH modification info" is included, any UE in idle mode, CELL_PCH or URA_PCH state shall perform the actions as specified in subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message as specified above.
8.1.3
RRC connection establishment

UE RRC CONNECTION REQUEST UTRAN
RRC CONNECTION SETUP
RRC CONNECTION SETUP COMPLETE
Figure 8.1.3-1: RRC Connection Establishment, network accepts RRC connection
UE RRC CONNECTION REQUEST
UTRAN
RRC CONNECTION REJECT
Figure 8.1.3-2: RRC Connection Establishment, network rejects RRC connection
8.1.3.1
General
The purpose of this procedure is to establish an RRC connection.
8.1.3.2
Initiation
The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection and the UE is in idle mode (no RRC connection exists), as specified in subclause 8.1.8. Upon initiation of the procedure, the UE shall: 1> set the variable PROTOCOL_ERROR_INDICATOR to FALSE;
3GPP
Release 6
76
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the USIM is present: 2> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the 20 MSBs of the value stored in the USIM [50] for the maximum value of START for each CN Domain. 1> if the SIM is present: 2> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the default value in [40] for each CN Domain. 1> set the IE "Initial UE identity" in the variable INITIAL_UE_IDENTITY according to subclause 8.5.1; 1> set the contents of the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 1> set CFN in relation to SFN of current cell according to subclause 8.5.15; 1> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH; 1> set counter V300 to 1; and 1> if the variable ESTABLISHMENT_CAUSE is set to "MBMS reception": 2> when the MAC layer indicates success or failure to transmit the message: 3> if the MAC layer indicates failure: 4> enter idle mode; 4> consider the procedure to be unsuccessful; 4> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2; 4> the procedure ends. 3> else: 4> start timer T318; 4> apply value 0 for counter N300 regardless of the value included in IE "UE Timers and Constants in idle mode". 1> otherwise: 2> start timer T300 when the MAC layer indicates success or failure to transmit the message. 1> select a Secondary CCPCH according to [4]; 1> start receiving all FACH transport channels mapped on the selected Secondary CCPCH.
8.1.3.3
RRC CONNECTION REQUEST message contents to set
The UE shall, in the transmitted RRC CONNECTION REQUEST message: 1> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE; 1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY; 1> set the IE "Protocol error indicator" to the value of the variable PROTOCOL_ERROR_INDICATOR; and 1> include the IE "Predefined configuration status information" and set this IE to true if the UE has all preconfigurations stored with the same value tag as broadcast in the cell in which the RRC connection establishment is initiated. 1> if the UE is attempting to establish the signalling connection to PS-domain:
3GPP
Release 6
77
3GPP TS 25.331 V6.23.0 (2009-09)
2> include the IE "Domain Indicator" and set it to "PS domain". 1> else if the UE is attempting to establish the signalling connection to CS domain: 2> include the IE "Domain Indicator" and set it to "CS domain". 1> if the UE only supports HS-DSCH but not E-DCH: 2> include the IE "UE capability indication" and set it to the "HS-DSCH" value. 1> if the UE supports HS-DSCH and E-DCH: 2> include the IE "UE capability indication" and set it to the "HS-DSCH+E-DCH" value. 1> if the UE performs connection establishment for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and 1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service: 2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the ptp radio bearer request: 3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority; 3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8. 1> otherwise if the UE performs connection establishment for MBMS counting as specified in subclause 8.7.4; and 1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service: 2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response: 3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority; 3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8. 1> if the UE included one or more "MBMS Selected Service ID" IEs: 2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29. The UE shall not include the IE "UE Specific Behaviour Information 1 idle".
8.1.3.4
Reception of an RRC CONNECTION REQUEST message by the UTRAN
Upon receiving an RRC CONNECTION REQUEST message, UTRAN should either: 1> accept the request and use a predefined or default radio configuration, in which case it should: 2> include the following information in the RRC CONNECTION SETUP message: 3> the IE "Predefined configuration identity", to indicate which pre-defined configuration of RB and, transport channel parameters shall be used; or 3> the IE "Default configuration mode" and IE "Default configuration identity", to indicate which default configuration of RB and transport channel parameters shall be used; 3> PhyCH information elements.
3GPP
Release 6
78
3GPP TS 25.331 V6.23.0 (2009-09)
2> submit the RRC CONNECTION SETUP message to the lower layers for transmission on the downlink CCCH. NOTE 1: UTRAN should only apply a predefined radio configuration in case it orders the UE to enter CELL_DCH. This is because the predefined configuration information included in System Information Block 16 mandatorily includes information only required in CELL_DCH state. 1> accept the request without using a predefined or default radio configuration, in which case it should: 2> include in the RRC CONNECTION SETUP message the complete set of RB, TrCH and PhyCH information elements to be used; 2> submit the RRC CONNECTION SETUP message to the lower layers for transmission on the downlink CCCH; NOTE 2: In R'99, the RRC CONNECTION SETUP message always includes the IEs "Added or Reconfigured TrCH information list", both for uplink and downlink transport channels, even if UTRAN orders the UE to move to CELL_FACH and hence need not configure any transport channels. In these cases, UTRAN may include a configuration that adds little to the encoded message size e.g. a DCH with a single zero size transport format. At a later stage, UTRAN may either remove or reconfigure this configuration. 1> submit an RRC CONNECTION REJECT message on the downlink CCCH. In the RRC CONNECTION REJECT message, the UTRAN may direct the UE to another UTRA carrier or to another system. After the RRC CONNECTION REJECT message has been sent, all context information for the UE may be deleted in UTRAN.
8.1.3.5
Cell re-selection, T300 or T318 timeout
1> if the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and 1> if cell re-selection or expiry of timer T300 or timer T318 occurs: the UE shall: 1> check the value of V300; and 2> if V300 is equal to or smaller than N300: 3> if cell re-selection occurred: 4> set CFN in relation to SFN of current cell according to subclause 8.5.15. 3> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 3> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13; and 3> apply the given Access Service Class when accessing the RACH; 3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH; 3> increment counter V300; 3> restart timer T300 when the MAC layer indicates success or failure to transmit the message. 2> if V300 is greater than N300: 3> enter idle mode; 3> consider the procedure to be unsuccessful; 3> Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 3> the procedure ends.
3GPP
Release 6
79
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.3.5a
Abortion of RRC connection establishment
If the UE has not yet entered UTRA RRC Connected mode and the RRC connection establishment is to be aborted as specified in subclause 8.1.8, the UE shall: 1> consider the procedure to be unsuccessful; 1> perform the actions when entering idle mode as specified in subclause 8.5.2. The procedure ends.
8.1.3.6
Reception of an RRC CONNECTION SETUP message by the UE
The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message with the value of the variable INITIAL_UE_IDENTITY. If the values are different, the UE shall: 1> ignore the rest of the message. If the values are identical, the UE shall: 2> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Predefined configuration": 3> initiate the radio bearer and transport channel configuration in accordance with the predefined parameters identified by the IE "Predefined configuration identity" with the following exception; 4> ignore the IE "RB to setup list" and the IE "Re- establishment timer". NOTE: IE above IEs are mandatory to include in IE Predefined RB configuration that is included in System Information Block 16 but should be ignored since it is not possible to establish a RAB during RRC connection establishment.
3> initiate the physical channels in accordance with the received physical channel information elements; 2> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Default configuration": 3> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity" with the following exception: 4> ignore the radio bearers other than signalling radio bearers. 3> initiate the physical channels in accordance with the received physical channel information elements. NOTE: IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used.
2> if IE "Specification mode" is set to "Complete specification": 3> initiate the radio bearer, transport channel and physical channel configuration in accordance with the received radio bearer, transport channel and physical channel information elements. 1> clear the variable ESTABLISHMENT_CAUSE; 1> stop timer T300 or T318, whichever one is running, and act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following: 2> if the UE, according to subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this procedure: 3> if the IE "Frequency info" is included: 4> select a suitable UTRA cell according to [4] on that frequency.
3GPP
Release 6
80
3GPP TS 25.331 V6.23.0 (2009-09)
3> enter UTRA RRC connected mode; 3> select PRACH according to subclause 8.5.17; 3> select Secondary CCPCH according to subclause 8.5.19; 3> ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX. 1> if the UE, according to subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure: 2> perform the physical layer synchronisation procedure A as specified in [29] (FDD only); 2> enter UTRA RRC connected mode. 1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after successful state transition per subclause 8.6.3.3, with the contents set as specified below: 2> set the IE "RRC transaction identifier" to: 3> the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; and 3> clear that entry. 2> if the USIM or SIM is present: 3> set the "START" for each CN domain in the IE "START list" in the RRC CONNECTION SETUP COMPLETE message with the corresponding START value that is stored in the USIM [50] if present, or as stored in the UE if the SIM is present; and then 3> set the START value stored in the USIM [50] if present, and as stored in the UE if the SIM is present for any CN domain to the value "THRESHOLD" of the variable START_THRESHOLD. 2> if neither the USIM nor SIM is present: 3> set the "START" for each CN domain in the IE "START list" in the RRC CONNECTION SETUP COMPLETE message to zero; 3> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the default value [40]. 2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then 2> include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED; 2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and then 2> include this in IE "UE system specific capability". When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the UE shall: 1> if the UE has entered CELL_FACH state: 2> start timer T305 using its initial value if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS. 1> store the contents of the variable UE_CAPABILITY_REQUESTED in the variable UE_CAPABILITY_TRANSFERRED; 1> initialise variables upon entering UTRA RRC connected mode as specified in subclause 13.4; 1> consider the procedure to be successful; And the procedure ends.
3GPP
Release 6
81
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.3.7
Physical channel failure or cell re-selection
1> If the UE failed to establish, per subclause 8.5.4, the physical channel(s) indicated in the RRC CONNECTION SETUP message; or 1> if the UE performs cell re-selection; or 1> if the UE will be in the CELL_FACH state at the conclusion of this procedure; and 1> if the received RRC CONNECTION SETUP message included the IE "Frequency info" and the UE could not find a suitable UTRA cell on that frequency but it could find a suitable UTRA cell on another frequency; or 1> if the received RRC CONNECTION SETUP message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selected another cell than indicated by this IE; or 1> if the contents of the variable C_RNTI is empty; 1> after having received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and 1> before the RRC CONNECTION SETUP COMPLETE message is delivered to lower layers for transmission: the UE shall: 1> clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> check the value of V300, and: 2> if V300 is equal to or smaller than N300: 3> set CFN in relation to SFN of current cell according to subclause 8.5.15; 3> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 3> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH; 3> increment counter V300; and 3> restart timer T300 when the MAC layer indicates success or failure in transmitting the message. 2> if V300 is greater than N300: 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 3> consider the RRC establishment procedure to be unsuccessful; 3> the procedure ends.
8.1.3.8
Invalid RRC CONNECTION SETUP message, unsupported configuration or invalid configuration
If the UTRAN instructs the UE to use a configuration, which it does not support e.g., the message includes a predefined configuration that the UE has not stored and/or if the received message causes the variable UNSUPPORTED_CONFIGURATION or the variable INVALID_CONFIGURATION to be set to TRUE the UE shall perform procedure specific error handling as specified in this subclause. If the UE receives an RRC CONNECTION SETUP message which contains an IE "Initial UE identity" with a value which is identical to the value of the variable INITIAL_UE_IDENTITY, but the RRC CONNECTION SETUP message
3GPP
Release 6
82
3GPP TS 25.331 V6.23.0 (2009-09)
contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> stop timer T300 or T318, whichever one is running; and 1> clear the entry for the RRC CONNECTION SETUP message in the table "Rejected transactions" in the variable TRANSACTIONS and proceed as below. If the UE receives an RRC CONNECTION SETUP message which contains an IE "Initial UE identity" with a value which is identical to the value of the variable INITIAL_UE_IDENTITY: 1> if the RRC CONNECTION SETUP message contained a configuration the UE does not support; and/or 1> if the variable UNSUPPORTED_CONFIGURATION becomes set to TRUE due to the received RRC CONNECTION SETUP message; and/or 1> if the variable INVALID_CONFIGURATION becomes set to TRUE due to the received RRC CONNECTION SETUP message: the UE shall: 1> stop timer T300 or T318, whichever one is running; and 1> clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS and proceed as below. If V300 is equal to or smaller than N300, the UE shall: 1> set the variable PROTOCOL_ERROR_INDICATOR to TRUE; 1> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 1> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13; and 1> apply the given Access Service Class when accessing the RACH; 1> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH; 1> increment counter V300; and 1> restart timer T300 when the MAC layer indicates success or failure in transmitting the message. If V300 is greater than N300, the UE shall: 1> enter idle mode; 1> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 1> consider the RRC establishment procedure to be unsuccessful; 1> the procedure ends.
8.1.3.9
Reception of an RRC CONNECTION REJECT message by the UE
When the UE receives an RRC CONNECTION REJECT message on the downlink CCCH, it shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION REJECT message with the value of the variable INITIAL_UE_IDENTITY: If the values are different, the UE shall ignore the rest of the message; If the values are identical, the UE shall: 1> stop timer T300 or T318, whichever one is running; and 1> clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS;
3GPP
Release 6
83
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the UE has disabled cell reselection to a UTRA carrier due to an earlier RRC CONNECTION REJECT message, the UE shall resume cell reselection to that UTRA carrier; 1> if the Rejection Cause is 'unspecified' and the IE "Counting Completion" is present, the UE should terminate an ongoing MBMS counting procedure according to clause 8.7.4.4; 1> if the IE "wait time" <> '0'; and 1> if the IE "frequency info" is present and: 2> if V300 is equal to or smaller than N300: 3> select a suitable UTRA cell according to [4] on that frequency; 3> after having selected and camped on a suitable cell on the designated UTRA carrier: 4> set CFN in relation to SFN of current cell according to subclause 8.5.15; 4> set the contents of the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 4> transmit an RRC CONNECTION REQUEST message on the uplink CCCH; 4> reset counter V300; 4> start timer T300 when the MAC layer indicates success or failure in transmitting the message; 4> disable cell reselection to original UTRA carrier until the time stated in the IE "wait time" has elapsed or until the RRC connection establishment procedure ends, whichever occurs first; 3> if no suitable cell on the designated UTRA carrier is found: 4> wait for at least the time stated in the IE "wait time"; 4> set CFN in relation to SFN of current cell according to subclause 8.5.15; 4> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH of the original serving cell; 4> increment counter V300; 4> restart timer T300 when the MAC layer indicates success or failure to transmit the message; 2> if V300 is greater than N300: 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 3> consider the RRC establishment procedure to be unsuccessful; 3> the procedure ends. 1> if the IE "inter-RAT info" is present: 2> if the IE "wait time" = '0': 3> the UE behaviour is not specified. 2> if V300 is equal to or smaller than N300:
3GPP
Release 6
84
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "GSM target cell info" is present: 4> attempt to camp on a suitable cell of the list of cells indicated for that RAT; 4> if the UE selects and camps on one of the cells indicated for that RAT: 5> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed. 4> if the UE cannot find any suitable cell from the indicated ones within 10s, the UE is allowed to camp on any suitable cell on that RAT. 3> if the IE "GSM target cell info" is not present: 4> select a suitable cell in the designated RAT; 4> after having selected and camped on a suitable cell on the designated RAT: 5> disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed or until the UE successfully establishes a connection on the designated RAT, whichever occurs first. 3> if no suitable cell in the designated RAT is found: 4> wait at least the time stated in the IE "wait time"; 4> set CFN in relation to SFN of current cell according to subclause 8.5.15; 4> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.2. 4> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 4> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH; 4> increment counter V300; 4> restart timer T300 when the MAC layer indicates success or failure to transmit the message; 2> if V300 is greater than N300: 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 3> consider the RRC establishment procedure to be unsuccessful; 3> the procedure ends. 1> if the IE "wait time" <> '0'; and 1> if neither the IEs "frequency info" nor "inter-RAT info" are present: 2> if V300 is equal to or smaller than N300: 3> wait at least the time stated in the IE "wait time"; 3> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.2; 3> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH; 3> increment counter V300; 3> restart timer T300 when the MAC layer indicates success or failure to transmit the message;
3GPP
Release 6
85
3GPP TS 25.331 V6.23.0 (2009-09)
2> if V300 is greater than N300: 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 3> consider the RRC establishment procedure to be unsuccessful; 3> the procedure ends. 1> if the IE "wait time" = '0': 2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 2> consider the RRC establishment procedure to be unsuccessful; 2> the procedure ends.
8.1.3.10
Invalid RRC CONNECTION REJECT message
If the UE receives an RRC CONNECTION REJECT message which contains an IE "Initial UE identity" with a value which is identical to the value of the IE "Initial UE identity" in the most recent RRC CONNECTION REQUEST message sent by the UE; but the RRC CONNECTION REJECT message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: The UE shall: 1> stop timer T300 or T318, whichever one is running; and 1> clear the entry for the RRC CONNECTION REJECT message in the table "Rejected transactions" in the variable TRANSACTIONS; 1> if V300 is equal to or smaller than N300: 2> set the variable PROTOCOL_ERROR_INDICATOR to TRUE; 2> set the IEs in the RRC CONNECTION REQUEST message according to subclause 8.1.3.3; 2> perform the mapping of the Access Class to an Access Service Class as specified in subclause 8.5.13, and apply the given Access Service Class when accessing the RACH; 2> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink CCCH; 2> increment counter V300; 2> restart timer T300 when the MAC layer indicates success or failure to transmit the message. 1> if V300 is greater than N300: 2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 2> consider the procedure to be successful; 2> the procedure ends.
3GPP
Release 6
86
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.4
RRC connection release

UE RRC CONNECTION RELEASE UTRAN
RRC CONNECTION RELEASE COMPLETE
Figure 8.1.4-1: RRC Connection Release procedure on the DCCH

UE RRC CONNECTION RELEASE UTRAN
Figure 8.1.4-2: RRC Connection Release procedure on the CCCH
8.1.4.1
General
The purpose of this procedure is to release the RRC connection including all radio bearers and all signalling radio bearers between the UE and the UTRAN. By doing so, all established signalling connections will be released.
8.1.4.2
Initiation
When the UE is in state CELL_DCH or CELL_FACH, the UTRAN may at anytime initiate an RRC connection release by transmitting an RRC CONNECTION RELEASE message using UM RLC. When UTRAN transmits an RRC CONNECTION RELEASE message the downlink DCCH should be used, if available. If the downlink DCCH is not available in UTRAN and the UE is in CELL_FACH state, the downlink CCCH may be used. UTRAN may transmit several RRC CONNECTION RELEASE messages to increase the probability of proper reception of the message by the UE. In such a case, the RRC SN for these repeated messages should be the same. The number of repeated messages and the interval between the messages is a network option.
8.1.4.3
Reception of an RRC CONNECTION RELEASE message by the UE
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states. When the UE receives the first RRC CONNECTION RELEASE message; and 1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or 1> if the message is received on DCCH: the UE shall perform the RRC connection release procedure as specified below. When the UE receives the first RRC CONNECTION RELEASE message; and 1> if the message is received on the CCCH, the IE "UTRAN group identity" is present and there is a group identity match according to subclause 8.6.3.13:
3GPP
Release 6
87
3GPP TS 25.331 V6.23.0 (2009-09)
the UE shall perform the RRC connection release procedure as specified below. The UE shall: 1> in state CELL_DCH: 2> initialise the counter V308 to zero; 2> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; 2> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using UM RLC on the DCCH to the UTRAN; 2> if the IE "Rplmn information" is present: 3> the UE may: 4> store the IE on the ME together with the PLMN id for which it applies; 3> the UE may then: 4> utilise this information, typically indicating where a number of BCCH frequency ranges of a RAT may be expected to be found, during subsequent Rplmn selections of the indicated PLMN. 2> start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio interface. 1> in state CELL_FACH: 2> if the RRC CONNECTION RELEASE message was received on the DCCH: 3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; 3> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using AM RLC on the DCCH to the UTRAN. 3> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been confirmed by the lower layers: 4> release all its radio resources; and 4> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; and 4> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; 4> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 4> clear the variable ESTABLISHED_RABS; 4> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers; 4> enter idle mode; 4> perform the actions specified in subclause 8.5.2 when entering idle mode. 3> and the procedure ends. 2> if the RRC CONNECTION RELEASE message was received on the CCCH: 3> release all its radio resources;
3GPP
Release 6
88
3GPP TS 25.331 V6.23.0 (2009-09)
3> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to the upper layers; 3> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; 3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> clear the variable ESTABLISHED_RABS; 3> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers; 3> enter idle mode; 3> perform the actions specified in subclause 8.5.2 when entering idle mode; 3> and the procedure ends.
8.1.4.4
Invalid RRC CONNECTION RELEASE message
If the RRC CONNECTION RELEASE message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, and if the "protocol error cause" in PROTOCOL_ERROR_INFORMATION is set to any cause value except "ASN.1 violation or encoding error", the UE shall perform procedure specific error handling as follows: The UE shall: 1> ignore any IE(s) causing the error but treat the rest of the RRC CONNECTION RELEASE message as normal according to subclause 8.1.4.3, with an addition of the following actions: 2> if the RRC CONNECTION RELEASE message was received on the DCCH: 3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Rejected transactions" in the variable TRANSACTIONS; 3> include the IE "Error indication" in the RRC CONNECTION RELEASE COMPLETE message with: 4> the IE "Failure cause" set to the cause value "Protocol error"; and 4> the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION.
8.1.4.5
Cell re-selection or radio link failure
If the UE performs cell re-selection or the radio link failure criteria in subclause 8.5.6 are met at any time during the RRC connection release procedure and the UE has not yet entered idle mode, the UE shall: 1> if cell re-selection occurred (CELL_FACH state): 2> perform a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection". 1> if radio link failure occurred (CELL_DCH state): 2> release all its radio resources; 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS;
3GPP
Release 6
89
3GPP TS 25.331 V6.23.0 (2009-09)
2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode; 2> and the procedure ends.
8.1.4.6
Expiry of timer T308, unacknowledged mode transmission
When in state CELL_DCH and the timer T308 expires, the UE shall: 1> increment V308 by one; 1> if V308 is equal to or smaller than N308: 2> prior to retransmitting the RRC CONNECTION RELEASE COMPLETE message: 3> if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started": 4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity check info", which is set as specified in subclause 8.5.10. 3> else: 4> include the same IEs as in the last unsuccessful attempt of this message. 2> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message retransmitted below to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; 2> send the RRC CONNECTION RELEASE COMPLETE message on signalling radio bearer RB1; 2> start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio interface. 1> if V308 is greater than N308: 2> release all its radio resources; 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode; 2> and the procedure ends.
8.1.4.7
Void
8.1.4.8
Reception of an RRC CONNECTION RELEASE COMPLETE message by UTRAN
When UTRAN receives an RRC CONNECTION RELEASE COMPLETE message from the UE, it should: 1> release all UE dedicated resources and the procedure ends on the UTRAN side.
3GPP
Release 6
90
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.4.9
Unsuccessful transmission of the RRC CONNECTION RELEASE COMPLETE message, acknowledged mode transmission
When acknowledged mode was used and RLC does not succeed in transmitting the RRC CONNECTION RELEASE COMPLETE message, the UE shall: 1> release all its radio resources; 1> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 1> clear the variable ESTABLISHED_RABS; 1> enter idle mode; 1> perform the actions specified in subclause 8.5.2 when entering idle mode; 1> and the procedure ends.
8.1.4.10
Detection of loss of dedicated physical channel by UTRAN in CELL_DCH state
If the release is performed from the state CELL_DCH, and UTRAN detects loss of the dedicated physical channel according to subclause 8.5.6, UTRAN may release all UE dedicated resources, even if no RRC CONNECTION RELEASE COMPLETE message has been received.
8.1.4.11
Failure to receive RRC CONNECTION RELEASE COMPLETE message by UTRAN
If UTRAN does not receive any RRC CONNECTION RELEASE COMPLETE message, it should release all UE dedicated resources.
8.1.4a
8.1.4a.1
RRC connection release requested by upper layers

General
The purpose of this procedure is to release the RRC connection and bar the current cell or cells. The procedure is requested by upper layers when they determine that the network has failed an authentication check [5].
8.1.4a.2
Initiation
If the upper layers request the release of the RRC connection, the UE shall: 1> release all its radio resources; 1> enter idle mode; 1> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2; 1> if the UE was in CELL_DCH state prior to entering idle mode: 2> consider all cells that were in the active set prior to entering idle mode to be barred according to [4]; and 2> consider the barred cells as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred". 1> if the UE was in CELL_FACH or CELL_PCH or URA_PCH state prior to entering idle mode: 2> consider the cell on which the UE was camped prior to entering idle mode to be barred according to [4]; and
3GPP
Release 6
91
3GPP TS 25.331 V6.23.0 (2009-09)
2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
8.1.5
Void
8.1.6
Transmission of UE capability information

UE UTRAN
UE CAPABILITY INFORMATION
UE CAPABILITY INFORMATION CONFIRM
Figure 8.1.6-1: Transmission of UE capability information, normal flow
8.1.6.1
General
The UE capability update procedure is used by the UE to convey UE specific capability information to the UTRAN.
8.1.6.2
Initiation
The UE shall initiate the UE capability update procedure in the following situations: 1> the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN; 1> while in connected mode the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED. If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the UE shall: 1> include the IE "RRC transaction identifier"; and 1> set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> for the UE capabilities defined prior to REL-6: 2> retrieve its UTRA UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and 2> include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE is included in variable UE_CAPABILITY_REQUESTED; 2> retrieve its inter-RAT-specific UE radio access capability information elements from variable UE_CAPABILITY_REQUESTED; and 2> include this in IE "UE system specific capability". 1> for the UE capabilities defined in REL-6 or later: 2> include the information elements associated with the capabilities included in the variable UE_CAPABILITY_REQUESTED and the variable UE_CAPABILITY_TRANSFERRED.
3GPP
Release 6
92
3GPP TS 25.331 V6.23.0 (2009-09)
If the UE CAPABILITY INFORMATION message is sent because one or more of the UE capabilities change compared to those stored in the variable UE_CAPABILITY_TRANSFERRED while in connected state, the UE shall: 1> for the UE capabilities defined prior to REL-6, include the information elements associated with the capabilities that have changed in the UE CAPABILITY INFORMATION message; and 1> for the UE capabilities defined in REL-6 or later, include the information elements associated with the capabilities included in the variable UE_CAPABILITY_TRANSFERRED. If the UE is in CELL_PCH or URA_PCH state, it shall first perform a cell update procedure using the cause "uplink data transmission", see subclause 8.3.1. The UE RRC shall submit the UE CAPABILITY INFORMATION message to the lower layers for transmission on the uplink DCCH using AM RLC. When the message has been delivered to lower layers for transmission the UE RRC shall start timer T304 and set counter V304 to 1.
8.1.6.3
Reception of a UE CAPABILITY INFORMATION message by the UTRAN
Upon reception of a UE CAPABILITY INFORMATION message, the UTRAN should transmit a UE CAPABILITY INFORMATION CONFIRM message on the downlink DCCH using UM or AM RLC. After the UE CAPABILITY INFORMATION CONFIRM message has been submitted to the lower layers for transmission, the procedure is complete.
8.1.6.4
Reception of the UE CAPABILITY INFORMATION CONFIRM message by the UE
Upon reception of a UE CAPABILITY INFORMATION CONFIRM message, the UE shall: 1> stop timer T304; 1> if there is an entry for the UE CAPABILITY ENQUIRY message is present in the table "Accepted transactions" in the variable TRANSACTIONS: 2> clear that entry. 1> update its variable UE_CAPABILITY_TRANSFERRED with the UE capabilities it has last transmitted to the UTRAN during the current RRC connection; 1> clear the variable UE_CAPABILITY_REQUESTED; 1> and the procedure ends.
8.1.6.5
Invalid UE CAPABILITY INFORMATION CONFIRM message
If the UE receives a UE CAPABILITY INFORMATION CONFIRM message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> stop timer T304; 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to UE CAPABILITY INFORMATION CONFIRM; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY INFORMATION CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION;
3GPP
Release 6
93
3GPP TS 25.331 V6.23.0 (2009-09)
1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> restart timer T304 and continue with any ongoing procedures or processes as if the invalid UE CAPABILITY INFORMATION CONFIRM message has not been received.
8.1.6.6
T304 timeout
Upon expiry of timer T304, the UE shall check the value of V304 and: 1> if V304 is smaller than or equal to N304: 2> prior to retransmitting the UE CAPABILITY INFORMATION message: 3> if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started": 4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity check info", which is set as specified in subclause 8.5.10. 3> else: 4> include the same IEs as in the last unsuccessful attempt of this message. 2> send the UE CAPABILITY INFORMATION message on signalling radio bearer RB2; 2> restart timer T304; 2> increment counter V304. 1> if V304 is greater than N304: 2> initiate the Cell update procedure as specified in subclause 8.3.1, using the cause "Radio link failure".
8.1.7
UE capability enquiry
UE UTRAN
UE CAPABILITY ENQUIRY
Figure 8.1.7-1: UE capability enquiry procedure, normal flow
8.1.7.1
General
The UE capability enquiry can be used to request the UE to transmit its capability information related to any radio access network that is supported by the UE.
8.1.7.2
Initiation
The UE capability enquiry procedure is initiated by the UTRAN by transmitting a UE CAPABILITY ENQUIRY message on the DCCH using UM or AM RLC.
8.1.7.3
Reception of a UE CAPABILITY ENQUIRY message by the UE
Upon reception of a UE CAPABILITY ENQUIRY message, the UE shall act on the received information elements as specified in subclause 8.6 and initiate the transmission of UE capability information procedure, which is specified in subclause 8.1.6.
3GPP
Release 6
94
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.7.4
Invalid UE CAPABILITY ENQUIRY message
If the UE receives a UE CAPABILITY ENQUIRY message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to UE CAPABILITY ENQUIRY; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with the ongoing processes and procedures as if the invalid UE CAPABILITY ENQUIRY message has not been received.
8.1.8
Initial Direct transfer

UE UTRAN
INITIAL DIRECT TRANSFER
Figure 8.1.8-1: Initial Direct transfer in the uplink, normal flow
8.1.8.1
General
The initial direct transfer procedure is used in the uplink to establish a signalling connection. It is also used to carry an initial upper layer (NAS) message over the radio interface.
8.1.8.2
Initiation of Initial direct transfer procedure in the UE
In the UE, the initial direct transfer procedure shall be initiated, when the upper layers request establishment of a signalling connection. This request also includes a request for the transfer of a NAS message. Upon initiation of the initial direct transfer procedure the UE shall: 1> set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers. Upon initiation of the initial direct transfer procedure when the UE is in idle mode, the UE shall: 1> perform an RRC connection establishment procedure, according to subclause 8.1.3; NOTE: If an RRC connection establishment is ongoing, this procedure continues unchanged, i.e. it is not interrupted.
1> if the RRC connection establishment procedure was not successful:
3GPP
Release 6
95
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the establishment cause for the failed RRC connection establishment was set to "MBMS reception" and a different cause value is stored in the variable "ESTABLISHMENT_CAUSE": 3> UE-AS (RRC) initiates a new RRC connection establishment procedure, using the establishment cause as contained in the variable ESTABLISHMENT_CAUSE. 2> otherwise: 3> indicate failure to establish the signalling connection to upper layers and end the procedure. 1> when the RRC connection establishment procedure is completed successfully: 2> continue with the initial direct transfer procedure as below. Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall: 1> perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission"; 1> when the cell update procedure completed successfully: 2> continue with the initial direct transfer procedure as below. The UE shall, in the INITIAL DIRECT TRANSFER message: 1> set the IE "NAS message" as received from upper layers; and 1> set the IE "CN domain identity" as indicated by the upper layers; and 1> set the IE "Intra Domain NAS Node Selector" as follows: 2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and 2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities: 1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available; 2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available; 3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE. 1> if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary PLMN Identity" in the IE "CN Information Info": 2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling connection is requested, and this PLMN is not in agreement with the latest PLMN information received via dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be informed. 1> if the UE, on the existing RRC connection, has not received a dedicated RRC message containing the IE "CN Information Info" , and if the IE "Multiple PLMN List" was broadcast in the cell where the current RRC connection was established: 2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the PLMN chosen by higher layers [5, 25] amongst the PLMNs in the IE "Multiple PLMN List" broadcast in the cell where the RRC connection was established. 1> if the IE "Activated service list" within variable MBMS_ACTIVATED_SERVICES includes one or more MBMS services with the IE "Service type" set to "Multicast" and; 1> if the IE "CN domain identity" as indicated by the upper layers is set to "CS domain" and; 1> if the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity 'PS domain': 2> include the IE "MBMS joined information";
3GPP
Release 6
96
3GPP TS 25.331 V6.23.0 (2009-09)
2> include the IE "P-TMSI" within the IE "MBMS joined information" if a valid PTMSI is available. 1> if the variable ESTABLISHMENT_CAUSE_ is initialised: 2> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE; 2> clear the variable ESTABLISHMENT_CAUSE. 1> calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and 1> include the calculated START value for that CN domain in the IE "START". The UE shall: 1> transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3; 1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission: 2> confirm the establishment of a signalling connection to upper layers; and 2> add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable ESTABLISHED_SIGNALLING_CONNECTIONS. 1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC: 2> the procedure ends. When not stated otherwise elsewhere, the UE may also initiate the initial direct transfer procedure when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected. A new signalling connection request may be received from upper layers during transition to idle mode. In those cases, from the time of the indication of release to upper layers until the UE has entered idle mode, any such upper layer request to establish a new signalling connection shall be queued. This request shall be processed after the UE has entered idle mode.
8.1.8.2a
RLC re-establishment or inter-RAT change
If a re-establishment of the transmitting side of the RLC entity on signalling radio bearer RB3 occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, the UE shall: 1> retransmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3. If an Inter-RAT handover from UTRAN procedure occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, for messages with the IE "CN domain identity" set to "CS domain", the UE shall: 1> retransmit the NAS message as specified in subclause 8.3.7.4.
8.1.8.2ab
Inter-RAT handover from UTRAN to GERAN Iu mode
If an Inter-RAT handover from UTRAN to GERAN Iu mode occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, for messages for all CN domains, the UE shall: 1> retransmit the NAS message as specified in subclause 8.3.7.4.
8.1.8.2b
Abortion of signalling connection establishment
If the UE receives a request from upper layers to release (abort) the signalling connection for the CN domain for which the initial direct transfer procedure is ongoing, the UE shall: 1> if the UE has not yet entered UTRA RRC connected mode: 2> abort the RRC connection establishment procedure as specified in subclause 8.1.3;
3GPP
Release 6
97
3GPP TS 25.331 V6.23.0 (2009-09)
the procedure ends.
8.1.8.3
Reception of INITIAL DIRECT TRANSFER message by the UTRAN
On reception of the INITIAL DIRECT TRANSFER message the NAS message should be routed using the IE "CN Domain Identity". UTRAN may also use the IE "Intra Domain NAS Node Selector" and the IE "PLMN identity" for routing among the CN nodes for the addressed CN domain. If no signalling connection exists towards the chosen node, then a signalling connection is established. When the UTRAN receives an INITIAL DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere. The UTRAN should: 1> set the START value for the CN domain indicated in the IE "CN domain identity" to the value of the IE "START".
8.1.9
Downlink Direct transfer

UE UTRAN
DOWNLINK DIRECT TRANSFER
Figure 8.1.9-1: Downlink Direct transfer, normal flow
8.1.9.1
General
The downlink direct transfer procedure is used in the downlink direction to carry upper layer (NAS) messages over the radio interface.
8.1.9.2
Initiation of downlink direct transfer procedure in the UTRAN
In the UTRAN, the direct transfer procedure is initiated when the upper layers request the transfer of a NAS message after the initial signalling connection is established. The UTRAN may also initiate the downlink direct transfer procedure when another RRC procedure is ongoing, and in that case the state of the latter procedure shall not be affected. The UTRAN shall transmit the DOWNLINK DIRECT TRANSFER message on the downlink DCCH using AM RLC on signalling radio bearer RB3 or signalling radio bearer RB4. The UTRAN should: 1> if upper layers indicate "low priority" for this message: 2> select signalling radio bearer RB4, if available. Specifically, for a GSM-MAP based CN, signalling radio bearer RB4 should, if available, be selected when "SAPI 3" is requested; 2> select signalling radio bearer RB3 when signalling radio bearer RB4 is not available. 1> if upper layers indicate "high priority" for this message: 2> select signalling radio bearer RB3. Specifically, for a GSM-MAP based CN, signalling radio bearer RB3 should be selected when "SAPI 0" is requested. The UTRAN sets the IE "CN Domain Identity" to indicate, which CN domain the NAS message is originated from.
3GPP
Release 6
98
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.9.3
Reception of a DOWNLINK DIRECT TRANSFER message by the UE
Upon reception of the DOWNLINK DIRECT TRANSFER message, the UE RRC shall, using the IE "CN Domain Identity", route the contents of the IE "NAS message" and the value of the IE"CN Domain Identity" to upper layers. The UE shall clear the entry for the DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable TRANSACTIONS. When the UE receives a DOWNLINK DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures when not stated otherwise elsewhere.
8.1.9.3a
No signalling connection exists
If the UE receives a DOWNLINK DIRECT TRANSFER message, and the signalling connection identified with the IE "CN domain identity" does not exist according to the variable ESTABLISHED_SIGNALLING_CONNECTIONS, the UE shall: 1> ignore the content of the DOWNLINK DIRECT TRANSFER message; 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible with receiver state". When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall: 1> continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has not been received.
8.1.9.4
Invalid DOWNLINK DIRECT TRANSFER message
If the UE receives a DOWNLINK DIRECT TRANSFER message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall: 1> continue with any ongoing processes and procedures as if the invalid DOWNLINK DIRECT TRANSFER message has not been received.
3GPP
Release 6
99
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.10
Uplink Direct transfer

UE UTRAN
UPLINK DIRECT TRANSFER
Figure 8.1.10-1: Uplink Direct transfer, normal flow
8.1.10.1
General
The uplink direct transfer procedure is used in the uplink direction to carry all subsequent upper layer (NAS) messages over the radio interface belonging to a signalling connection.
8.1.10.2
Initiation of uplink direct transfer procedure in the UE
In the UE, the uplink direct transfer procedure shall be initiated when the upper layers request a transfer of a NAS message on an existing signalling connection. When not stated otherwise elsewhere, the UE may initiate the uplink direct transfer procedure when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected. Upon initiation of the uplink direct transfer procedure in CELL_PCH or URA_PCH state, the UE shall: 1> perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission"; 1> when the cell update procedure has been completed successfully: 2> continue with the uplink direct transfer procedure as below. The UE shall transmit the UPLINK DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3 or signalling radio bearer RB4. The UE shall: 1> if upper layers indicate "low priority" for this message: 2> select signalling radio bearer RB4, if available. Specifically, for a GSM-MAP based CN, signalling radio bearer RB4 shall, if available, be selected when "SAPI 3" is requested; 2> select signalling radio bearer RB3 when signalling radio bearer RB4 is not available; 1> if upper layers indicate "high priority" for this message: 2> select signalling radio bearer RB3. Specifically, for a GSM-MAP based CN, signalling radio bearer RB3 shall be selected when "SAPI 0" is requested. The UE shall set the IE "NAS message" as received from upper layers and set the IE "CN domain identity" as indicated by the upper layers. When the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC the procedure ends.
8.1.10.2a
If signalling radio bearer RB n (where n equals to 3 or 4) was used when transmitting the UPLINK DIRECT TRANSFER message and a re-establishment of the transmitting side of the RLC entity on the same signalling radio bearer RB n occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, the UE shall:
3GPP
Release 6
100
3GPP TS 25.331 V6.23.0 (2009-09)
1> retransmit the UPLINK DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB n. If an Inter-RAT handover from UTRAN procedure occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, for messages with the IE "CN domain identity" set to "CS domain", the UE shall: 1> retransmit the NAS message as specified in subclause 8.3.7.4.
8.1.10.2b
Inter-RAT handover from UTRAN to GERAN Iu mode
If an Inter-RAT handover from UTRAN to GERAN Iu mode occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, for messages for all CN domains, the UE shall: 1> retransmit the NAS message as specified in subclause 8.3.7.4.
8.1.10.3
Reception of UPLINK DIRECT TRANSFER message by the UTRAN
On reception of the UPLINK DIRECT TRANSFER message the NAS message should be routed using the value indicated in the IE "CN domain identity". When the UTRAN receives an UPLINK DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere.
8.1.11
UE dedicated paging
UE UTRAN
PAGING TYPE 2
Figure 8.1.11-1: UE dedicated paging
8.1.11.1
General
This procedure is used to transmit dedicated paging information to one UE in connected mode in CELL_DCH or CELL_FACH state. Upper layers in the network may request initiation of paging.
8.1.11.2
Initiation
For a UE in CELL_DCH or CELL_FACH state, UTRAN initiates the procedure by transmitting a PAGING TYPE 2 message on the DCCH using AM RLC. When not stated otherwise elsewhere, the UTRAN may initiate the UE dedicated paging procedure also when another RRC procedure is ongoing, and in that case the state of the latter procedure shall not be affected. UTRAN should set the IE "Paging cause" to the cause for paging received from upper layers. If no cause for paging is received from upper layers, UTRAN should set the value "Terminating cause unknown".
8.1.11.3
Reception of a PAGING TYPE 2 message by the UE
When the UE receives a PAGING TYPE 2 message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere. The UE shall: 1> indicate reception of paging; and
3GPP
Release 6
101
3GPP TS 25.331 V6.23.0 (2009-09)
1> forward the IE "Paging cause" and the IE "Paging record type identifier" to upper layers. The UE shall: 1> clear the entry for the PAGING TYPE 2 message in the table "Accepted transactions" in the variable TRANSACTIONS.
8.1.11.4
Invalid PAGING TYPE 2 message
If the UE receives a PAGING TYPE 2 message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to PAGING TYPE 2; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the PAGING TYPE 2 message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid PAGING TYPE 2 message has not been received.
8.1.12
Security mode control

UE UTRAN
SECURITY MODE COMMAND
SECURITY MODE COMPLETE
Figure 8.1.12-1: Security mode control procedure
8.1.12.1
General
The purpose of this procedure is to trigger the start of ciphering or to command the restart of the ciphering with a new ciphering configuration, for the radio bearers of one CN domain and for all signalling radio bearers. It is also used to start integrity protection or to modify the integrity protection configuration for all signalling radio bearers.
3GPP
Release 6
102
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.12.2
8.1.12.2.1
Initiation
Ciphering configuration change
To start/restart ciphering, UTRAN sends a SECURITY MODE COMMAND message on the downlink DCCH in AM RLC using the most recent ciphering configuration. If no such ciphering configuration exists then the SECURITY MODE COMMAND is not ciphered. UTRAN should not transmit a SECURITY MODE COMMAND to signal a change in ciphering algorithm. When configuring ciphering, UTRAN should ensure that the UE needs to store at most two different ciphering configurations (keyset and algorithm) per CN domain, in total over all radio bearers at any given time. For signalling radio bearers the total number of ciphering configurations that need to be stored is at most three. Prior to sending the SECURITY MODE COMMAND, for the CN domain indicated in the IE "CN domain identity" in the SECURITY MODE COMMAND, UTRAN should: 1> suspend all radio bearers using RLC-AM or RLC-UM and all signalling radio bearers using RLC-AM or RLCUM, except the signalling radio bearer used to send the SECURITY MODE COMMAND message on the downlink DCCH in RLC-AM, and except signalling radio bearer RB0, according to the following: 2> not transmit RLC PDUs with sequence number greater than or equal to the number in IE "Radio bearer downlink ciphering activation time info" on all suspended radio bearers and all suspended signalling radio bearers. 1> set, for the signalling radio bearer used to send the SECURITY MODE COMMAND, the "RLC sequence number" in IE "Radio bearer downlink ciphering activation time info" in the IE "Ciphering mode info", at which time the new ciphering configuration shall be applied; NOTE: The UTRAN should avoid the situation that the UE is aware of more than one pending downlink ciphering activation times for SRB2. In such a case the UE behaviour is unspecified.
1> if a transparent mode radio bearer for this CN domain exists: 2> include the IE "Ciphering activation time for DPCH" in IE "Ciphering mode info", at which time the new ciphering configuration shall be applied and specify a CFN value for this IE that is a multiple of 8 frames (CFN mod 8 = 0). NOTE: UTRAN should chose the value for the IE "Ciphering activation time for DPCH" such that the new ciphering configuration will occur after all the pending ciphering activation times have been reached for the transparent mode radio bearers of this CN domain.
1> consider a ciphering activation time in downlink to be pending until the RLC sequence number of the next RLC PDU to be transmitted for the first time is equal to or larger than the selected activation time; 1> set, for each suspended radio bearer and signalling radio bearer that has no pending ciphering activation time set by a previous security mode control procedure, an "RLC sequence number" in IE "Radio bearer downlink ciphering activation time info" in the IE "Ciphering mode info", at which time the new ciphering configuration shall be applied; 1> set, for each suspended radio bearer and signalling radio bearer that has a pending ciphering activation time set by a previous security mode control procedure, the "RLC sequence number" in IE "Radio bearer downlink ciphering activation time info" in the IE "Ciphering mode info" to the value used in the previous security mode control procedure, at which time the latest ciphering configuration shall be applied; 1> if Integrity protection has already been started for the UE: 2> if for the CN domain indicated in the IE "CN domain identity" in the SECURITY MODE COMMAND, a new security key set (new ciphering and integrity protection keys) has been received from upper layers since the transmission of the last SECURITY MODE COMMAND message for that CN domain: 3> include the IE "Integrity protection mode info" in the SECURITY MODE COMMAND. 2> if the IE "CN domain identity" in the SECURITY MODE COMMAND is different from the IE "CN domain identity" that was sent in the previous SECURITY MODE COMMAND message to the UE: 3> include the IE "Integrity protection mode info" in the SECURITY MODE COMMAND.
3GPP
Release 6
103
3GPP TS 25.331 V6.23.0 (2009-09)
1> transmit the SECURITY MODE COMMAND message on RB2.
8.1.12.2.2
Integrity protection configuration change
To start or modify integrity protection, UTRAN sends a SECURITY MODE COMMAND message on the downlink DCCH in AM RLC using the new integrity protection configuration. UTRAN should not "modify" integrity protection for a CN domain to which a SECURITY MODE COMMAND configuring integrity protection has been previously sent for an ongoing signalling connection unless the application of new integrity keys needs to be signalled to the UE. UTRAN should not transmit a SECURITY MODE COMMAND to signal a change in integrity protection algorithm. In case of Inter-RAT handover to UTRAN, after the reception of the HANDOVER TO UTRAN COMPLETE message and a key set is received, UTRAN should transmit a SECURITY MODE COMMAND message containing IE "Integrity protection mode info" in order to initiate integrity protection with the integrity key of the key set used in the other RAT (see subclause 8.3.6.3). When configuring Integrity protection, UTRAN should: 1> ensure that the UE needs to store at most three different Integrity protection configurations (keysets) at any given time. This includes the total number of Integrity protection configurations for all signalling radio bearers; 1> if Ciphering has already been started for the UE for the CN domain to be set in the IE "CN domain identity" in the SECURITY MODE COMMAND: 2> if for the CN domain indicated in the IE "CN domain identity" in the SECURITY MODE COMMAND, a new security key set (new ciphering and integrity protection keys) has been received from upper layers since the transmission of the last SECURITY MODE COMMAND message for that CN domain: 3> include the IE "Ciphering mode info" in the SECURITY MODE COMMAND. 1> if Ciphering has already been configured for the UE for a CN domain different from the CN domain to be set in the IE "CN domain identity" in the SECURITY MODE COMMAND: 2> include the IE "Ciphering mode info" in the SECURITY MODE COMMAND. Prior to sending the SECURITY MODE COMMAND, for the CN domain indicated in the IE "CN domain identity" in the SECURITY MODE COMMAND, UTRAN should: 1> if this is the first SECURITY MODE COMMAND sent for this RRC connection: 2> if new keys have been received: 3> initialise the hyper frame numbers as follows: 4> set all bits of the hyper frame numbers of the COUNT-I values for all signalling radio bearers to zero. 2> else (if new keys have not been received): 3> use the value "START" in the most recently received IE "START list" or IE "START" that belongs to the CN domain indicated in the IE "CN domain identity" to initialise all hyper frame numbers of COUNT-I for all the signalling radio bearers by: 4> setting the 20 most significant bits of the hyper frame numbers for all signalling radio bearers to the value "START" in the most recently received IE "START list" or IE "START" for that CN domain; 4> setting the remaining bits of the hyper frame numbers equal to zero. 1> else (this is not the first SECURITY MODE COMMAND sent for this RRC connection): 2> if new keys have been received: 3> initialise the hyper frame number for COUNT-I for RB2 as follows: 4> set all bits of the HFN of the COUNT-I value for RB2 to zero. 2> if new keys have not been received:
3GPP
Release 6
104
3GPP TS 25.331 V6.23.0 (2009-09)
3> initialise the hyper frame number for COUNT-I for RB2 as follows: 4> set the 20 most significant bits of the HFN of the downlink and uplink COUNT-I to the value of the most recently received IE "START" or IE "START list" for the CN domain to be set in the IE "CN Domain Identity"; 4> set the remaining bits of the HFN of the downlink and uplink COUNT-I to zero. 1> if the IE "Integrity protection mode command" has the value "Start": 2> prohibit the transmission of signalling messages with any RRC SN on all signalling radio bearers, except RB2; 2> set the FRESH value in the IE "Integrity protection initialisation number", included in the IE "Integrity protection mode info". 1> if the IE "Integrity protection mode command" has the value "Modify": 2> for each signalling radio bearer RBn, except RB2: 3> prohibit the transmission of signalling messages with RRC SN greater or equal to the RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity protection mode info". 2> consider an integrity protection activation time in downlink to be pending until the selected activation time is equal to the next RRC sequence number to be used, which means that the last RRC message using the old integrity protection configuration has been submitted to lower layers; 2> set, for each signalling radio bearer RBn, that has no pending integrity protection activation time set by a previous security mode control procedure, an RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity protection mode info", at which time the new integrity protection configuration shall be applied; 2> set, for each signalling radio bearer RBn, that has a pending integrity protection activation time set by a previous security mode control procedure, the RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity protection mode info", to the value used in the previous security mode control procedure, at which time the latest integrity protection configuration shall be applied. 1> transmit the SECURITY MODE COMMAND message on RB2 using the new integrity protection configuration. NOTE1: In the case of re-initialisation of Integrity Protection at HFN wrap around, the network should take into account the UE actions as described in subclauses 8.5.10.1 and 8.5.10.2. NOTE2: After the SECURITY MODE COMMAND message is transmitted, the network should ensure that it can revert back to old integrity protection until it receives the SECURITY MODE COMPLETE message, to take into account the UE actions when security mode control procedure is unsuccessful. The network should also be aware that the UE may revert to old configuration when waiting for the acknowledgement from L2 for the SECURITY MODE COMPLETE message, and act accordingly. NOTE3: In the case of the first SECURITY MODE COMMAND message following an SRNS relocation, the network should set the IE "Downlink integrity protection activation info" for SRB3 and SRB4 to at least "the current downlink RRC sequence number +2". As a consequence, at least the first message sent on SRB3 and SRB4 by the Target RNC will use the old integrity protection configuration.
8.1.12.3
Reception of SECURITY MODE COMMAND message by the UE
Upon reception of the SECURITY MODE COMMAND message, the UE shall: 1> if neither IE "Ciphering mode info" nor IE "Integrity protection mode info" is included in the SECURITY MODE COMMAND: 2> set the variable INVALID_CONFIGURATION to TRUE.
3GPP
Release 6
105
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Security capability" is the same as indicated by variable UE_CAPABILITY_TRANSFERRED, and the IE "GSM security capability" (if included in the SECURITY MODE COMMAND) is the same as indicated by the variable UE_CAPABILITY_TRANSFERRED: 2> set the variable LATEST_CONFIGURED_CN_DOMAIN equal to the IE "CN domain identity"; 2> set the IE "Status" in the variable SECURITY_MODIFICATION for the CN domain indicated in the IE "CN domain identity" in the received SECURITY MODE COMMAND to the value "Affected"; 2> set the IE "Status" in the variable SECURITY_MODIFICATION for all CN domains other than the CN domain indicated in the IE "CN domain identity" to "Not affected"; 2> set the IE "RRC transaction identifier" in the SECURITY MODE COMPLETE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info": 3> perform the actions as specified in subclause 8.6.3.4. 2> if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info": 3> perform the actions as specified in subclause 8.6.3.5. 1> prior to sending the SECURITY MODE COMPLETE message: 2> use the old ciphering configuration for this message; 2> if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info": 3> include and set the IE "Radio bearer uplink ciphering activation time info" to the value of the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 3> for each radio bearer and signalling radio bearer that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN: 4> start or continue incrementing the COUNT-C values for all RLC-AM and RLC-UM signalling radio bearers at the ciphering activation time as specified in the procedure; 4> start or continue incrementing the COUNT-C values common for all transparent mode radio bearers for this CN domain at the ciphering activation time as specified in the procedure; 4> continue incrementing the COUNT-C values for all RLC-AM and RLC-UM radio bearers. 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN: 4> for ciphering on signalling radio bearers using RLC-AM and RLC-UM in the downlink, at the RLC sequence number indicated in IE "Radio bearer downlink ciphering activation time info" in the IE "Ciphering mode info" included in the SECURITY MODE COMMAND, for each signalling radio bearer: 5> set the 20 most significant bits of the HFN component of the downlink COUNT-C to the value "START" in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 5> set the remaining bits of the hyper frame numbers to zero. 3> if new keys have been received: 4> perform the actions in subclause 8.1.12.3.1. 2> if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info":
3GPP
Release 6
106
3GPP TS 25.331 V6.23.0 (2009-09)
3> include and set the IE "Uplink integrity protection activation info" to the value of the variable INTEGRITY_PROTECTION_ACTIVATION_INFO for each signalling radio bearer; 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN, for RB2: 4> in the downlink, for the received SECURITY MODE COMMAND message: 5> set the 20 most significant bits of the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to the value "START" in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 5> set the remaining bits of the IE "Downlink RRC HFN" to zero. 4> in the uplink, for the transmitted response message, SECURITY MODE COMPLETE: 5> set the 20 most significant bits of the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to the value "START" in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 5> set the remaining bits of the IE "Uplink RRC HFN" to zero. 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN, for each signalling radio bearer other than RB2: 4> if the IE "Integrity protection mode command" has the value "start": 5> in the downlink, for this signalling radio bearer: 6> set the 20 most significant bits of IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to the value START transmitted in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 6> set the remaining bits of the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to zero; 4> else: 5> in the downlink, for the first message for which the RRC sequence number in a received RRC message for this signalling radio bearer is equal to or greater than the activation time as indicated in IE "Downlink integrity protection activation info" as included in the IE "Integrity protection mode info", for this signalling radio bearer: 6> set the 20 most significant bits of the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to the value "START" in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 6> set the remaining bits of the IE "Downlink RRC HFN" to zero. 3> if new keys have been received: 4> perform the actions in subclause 8.1.12.3.1. 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted SECURITY MODE COMPLETE message;
3GPP
Release 6
107
3GPP TS 25.331 V6.23.0 (2009-09)
2> transmit the SECURITY MODE COMPLETE message on RB2. NOTE: After submission of the SECURITY MODE COMPLETE message to the lower layers, the UE should accept messages received in the DL which require the new security configuration to be applied on them. If the received message is successfully integrity checked, the UE should not discard the message due to lack of completion of the security procedure, caused by the successful delivery of the SECURITY MODE COMPLETE not having yet been confirmed by lower layers, unless the security configuration to be applied has been aborted and the message received requires integrity protection [5].
1> when the successful delivery of the SECURITY MODE COMPLETE message has been confirmed by RLC: 2> if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info": 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN: 4> for ciphering on signalling radio bearers using RLC-AM and RLC-UM in the uplink, at the RLC sequence number indicated in IE "Radio bearer uplink ciphering activation time info" included in the SECURITY MODE COMPLETE, for each signalling radio bearer: 5> set the 20 most significant bits of the HFN component of the uplink COUNT-C to the value "START" in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 5> set the remaining bits of the hyper frame numbers to zero. 3> if new keys have been received: 4> perform the actions in subclause 8.1.12.3.1. 3> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; 3> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 3> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 2> if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info": 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN, for each signalling radio bearer other than RB2: 4> if the IE "Integrity protection mode command" has the value "start": 5> in the uplink, for this signalling radio bearer: 6> set the 20 most significant bits of IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to the value START transmitted in the most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 6> set the remaining bits of the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to zero. 4> else: 5> in the uplink, for the first transmitted RRC message for this signalling radio bearer with RRC sequence number equal to the activation time as indicated in IE "Uplink integrity protection activation info" included in the transmitted SECURITY MODE COMPLETE, for this signalling radio bearer: 6> set the 20 most significant bits of the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to the value "START" in the
3GPP
Release 6
108
3GPP TS 25.331 V6.23.0 (2009-09)
most recently transmitted IE "START list" or IE "START", at the reception of the SECURITY MODE COMMAND, that belongs to the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 6> set the remaining bits of the IE "Uplink RRC HFN" to zero. 3> if new keys have been received: 4> perform the actions in subclause 8.1.12.3.1. 3> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; 3> set "Uplink RRC Message sequence number" for signalling radio bearer RB0 in the variable INTEGRITY_PROTECTION_INFO to a value such that next RRC message to be sent on uplink RB0 will use the new integrity protection configuration and the "RRC Message sequence number" in the IE "Integrity check info" in the next RRC message will equal to the activation time for RB0 as indicated in IE "Uplink integrity protection activation info" included in the transmitted SECURITY MODE COMPLETE; 3> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 3> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> clear the variable SECURITY_MODIFICATION; 2> notify upper layers upon change of the security configuration; 2> and the procedure ends. 1> if the IE "Security capability" is not the same as indicated by the variable UE_CAPABILITY_TRANSFERRED, or the IE "GSM security capability" (if included in the SECURITY MODE COMMAND) is not the same as indicated by the variable UE_CAPABILITY_TRANSFERRED, or if the IE "GSM security capability" is not included in the SECURITY MODE COMMAND and is included in the variable UE_CAPABILITY_TRANSFERRED: 2> release all its radio resources; 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> clear the variable SECURITY_MODIFICATION; 2> enter idle mode; 2> perform actions when entering idle mode as specified in subclause 8.5.2; 2> and the procedure ends.
8.1.12.3.1
NOTE:
New ciphering and integrity protection keys

The actions in this subclause are to be performed only if the new keys were received for an ongoing RRC connection while in UTRA.
If a new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN, the UE shall: 1> set the START value for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN to zero; 1> if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info":
3GPP
Release 6
109
3GPP TS 25.331 V6.23.0 (2009-09)
2> for integrity protection in the downlink on each signalling radio bearer except RB2: 3> if IE "Integrity protection mode command" has the value "start": 4> for the first received message on this signalling radio bearer: 5> start using the new integrity key; 5> for this signalling radio bearer: 6> set the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to zero. 3> else: 4> for the first message for which the RRC sequence number in a received RRC message for this signalling radio bearer is equal to or greater than the activation time as indicated in IE "Downlink integrity protection activation info" as included in the IE "Integrity protection mode info": 5> start using the new integrity key; 5> for this signalling radio bearer: 6> set the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to zero. 2> for integrity protection in the uplink on each signalling radio bearer except RB2: 3> for the first message for which the RRC sequence number in a to be transmitted RRC message for this signalling radio bearer is equal to the activation time as indicated in IE "Uplink integrity protection activation info" included in the transmitted SECURITY MODE COMPLETE message: 4> start using the new integrity key; 4> for this signalling radio bearer: 5> set the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to zero. 2> for integrity protection in the downlink on signalling radio bearer RB2: 3> at the received SECURITY MODECOMMAND: 4> start using the new integrity key; 4> set the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink COUNT-I to zero. 2> for integrity protection in the uplink on signalling radio bearer RB2 : 3> at the transmitted SECURITY MODE COMPLETE: 4> start using the new integrity key; 4> set the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink COUNT-I to zero. 1> if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info": 2> for each signalling radio bearer and for each radio bearer for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN: 3> if the IE "Status" in the variable CIPHERING_STATUS has the value "Started" for this CN domain, then for ciphering on radio bearers using RLC-TM: 4> at the CFN as indicated in the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info":
3GPP
Release 6
110
3GPP TS 25.331 V6.23.0 (2009-09)
5> start using the new key in uplink and downlink; 5> set the HFN component of the COUNT-C to zero. 3> if the IE "Status" in the variable CIPHERING_STATUS has the value "Started" for this CN domain, then for ciphering on radio bearers and signalling radio bearers using RLC-AM and RLC-UM: 4> in the downlink, at the RLC sequence number indicated in IE "Radio bearer downlink ciphering activation time info" in the IE "Ciphering mode info": 5> start using the new key; 5> set the HFN component of the downlink COUNT-C to zero. 4> in the uplink, at the RLC sequence number indicated in IE "Radio bearer uplink ciphering activation time info": 5> start using the new key; 5> set the HFN component of the uplink COUNT-C to zero. 1> consider the value of the latest transmitted START value to be zero.
8.1.12.4
Void
8.1.12.4a
Incompatible simultaneous security reconfiguration
If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION becomes set to TRUE of the received SECURITY MODE COMMAND message, the UE shall: 1> transmit a SECURITY MODE FAILURE message on the uplink DCCH using AM RLC, using the ciphering and integrity protection configurations prior to the reception of this SECURITY MODE COMMAND; 1> set the IE "RRC transaction identifier" in the SECURITY MODE FAILURE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration"; 1> when the response message has been submitted to lower layers for transmission: 2> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE; 2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; 2> only accept a message on SRB 2, with a COUNT-I that: 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and 3> does not take into account the HFN from the received SECURITY MODE COMMAND message. 2> and the procedure ends.
8.1.12.4b
If: -
Cell update procedure during security reconfiguration
a cell update procedure according to subclause 8.3.1 is initiated; and the received SECURITY MODE COMMAND message causes either,
3GPP
Release 6
111
3GPP TS 25.331 V6.23.0 (2009-09)
the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:
the UE shall: 1> abort the ongoing integrity and/or ciphering reconfiguration; 1> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; 1> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; 1> when the CELL UPDATE message has been submitted to lower layers for transmission: 2> if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info": 3> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 3> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info": 3> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 3> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> continue with any ongoing processes and procedures as if the SECURITY MODE COMMAND message has not been received; 2> only accept a message on SRB 2, with a COUNT-I that: 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and 3> does not take into account the HFN from the received SECURITY MODE COMMAND message. 2> if the UE has already submitted the SECURITY MODE COMPLETE message, use a COUNT-I value for transmission of the next message on SRB2 as stated below: 3> take the COUNT-I used prior to the transmission of the SECURITY MODE COMPLETE message; 3> increment that COUNT-I with 2; 3> apply that COUNT-I on the next message to transmit. 2> clear the variable SECURITY_MODIFICATION; 2> the procedure ends.
8.1.12.4c
Invalid configuration
If the variable INVALID_CONFIGURATION is set to TRUE due to the received SECURITY MODE COMMAND message, the UE shall: 1> transmit a SECURITY MODE FAILURE message on the DCCH using AM RLC after setting the IEs as specified below: 2> set the IE "RRC transaction identifier" in the SECURITY MODE FAILURE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to the cause value "invalid configuration". 1> when the response message has been submitted to lower layers for transmission:
3GPP
Release 6
112
3GPP TS 25.331 V6.23.0 (2009-09)
2> set the variable INVALID_CONFIGURATION to FALSE; 2> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; 2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; 2> only accept a message on SRB 2, with a COUNT-I that: 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and 3> does not take into account the HFN from the received SECURITY MODE COMMAND message. 2> and the procedure ends.
8.1.12.5
Reception of SECURITY MODE COMPLETE message by the UTRAN
UTRAN should apply integrity protection on the received SECURITY MODE COMPLETE message and all subsequent messages with the new integrity protection configuration, if changed. When UTRAN has received a SECURITY MODE COMPLETE message and the integrity protection has successfully been applied, UTRAN should: 1> if the IE "Ciphering mode info" was included in the SECURITY MODE COMMAND message: 2> if new keys were received for the CN domain set in the IE "CN Domain Identity" in the SECURITY MODE COMMAND: 3> set, at the downlink and uplink activation time, all the bits of the hyper frame numbers of the downlink and uplink COUNT-C values respectively for all radio bearers for this CN domain and all signalling radio bearers to zero. 2> else (if new keys were not received): 3> use, at the downlink and uplink activation time, the value "START" in the most recently received IE "START list" or IE "START" that belongs to the CN domain as indicated in the IE "CN domain identity" to initialise all hyper frame numbers of the downlink and uplink COUNT-C values respectively for all the signalling radio bearers as follows: 4> set the 20 most significant bits of the hyper frame numbers of the COUNT-C for all signalling radio bearers to the value "START" in the most recently received IE "START list" or IE "START" for that CN domain; 4> set the remaining bits of the hyper frame numbers equal to zero. 1> if the IE "Integrity protection mode info" was included in the SECURITY MODE COMMAND message: 2> if this was not the first SECURITY MODE COMMAND message for this RRC connection: 3> if new keys have been received for the CN domain set in the IE "CN Domain Identity" included in the transmitted SECURITY MODE COMMAND message: 4> initialise, at the downlink and uplink activation time, all hyper frame numbers of the downlink and uplink COUNT-I values respectively for all the signalling radio bearers other than RB2 as follows: 5> set all bits of the hyper frame numbers of the uplink and downlink COUNT-I to zero. 3> if no new keys have been received for the CN domain set in the IE "CN Domain Identity" included in the transmitted SECURITY MODE COMMAND message: 4> use, at the downlink and uplink activation time, the value "START" in the most recently received IE "START list" or IE "START" that belongs to the CN domain as indicated in the IE "CN domain identity" to initialise all hyper frame numbers of the downlink and uplink COUNT-I values respectively for all the signalling radio bearers other than RB2 as follows:
3GPP
Release 6
113
3GPP TS 25.331 V6.23.0 (2009-09)
5> set the 20 most significant bits of the hyper frame numbers of the downlink and uplink COUNT-I respectively for all signalling radio bearers to the value "START" in the most recently received IE "START list" or IE "START" for that CN domain; 5> set the remaining bits of the hyper frame numbers equal to zero. 1> send an indication to upper layers that the new security configuration has been activated; 1> resume, in the downlink, all suspended radio bearers and all signalling radio bearers; 1> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; 1> if the IE "Integrity protection mode command" included in the SECURITY MODE COMMAND had the value "Start": 2> start applying integrity protection in the downlink for all signalling radio bearers. 1> if the IE "Integrity protection mode command" included in the SECURITY MODE COMMAND had the value "Modify": 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number, for each signalling radio bearers RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info"; 2> continue applying the new integrity configuration for signalling radio bearer RB2; 2> apply the new integrity protection configuration on the received signalling messages with RRC SN greater than or equal to the number associated with the signalling radio bearer in IE "Uplink integrity protection activation info". 1> apply the old ciphering configuration for the transmission of RLC PDUs with RLC sequence number less than the number indicated in the IE "Radio bearer downlink ciphering activation time info" included in the IE "Ciphering mode info"; 1> apply the new ciphering configuration for the transmission of RLC PDUs with RLC sequence number greater than or equal to the number indicated in IE "Radio bearer downlink ciphering activation time info" included in the IE "Ciphering mode info"; 1> apply the old integrity protection configuration on the received signalling messages with RRC SN smaller than the number associated with the signalling radio bearer in IE "Uplink integrity protection activation info"; 1> for radio bearers using RLC-AM or RLC-UM: 2> use the old ciphering configuration for received RLC PDUs with RLC sequence number less than the RLC sequence number indicated in the IE "Radio bearer uplink ciphering activation time info" sent by the UE; 2> use the new ciphering configuration for received RLC PDUs with RLC sequence number greater than or equal to the RLC sequence number indicated in the IE "Radio bearer uplink ciphering activation time info" sent by the UE; 2> if an RLC reset or re-establishment of the transmitting side of an RLC entity occurs after the SECURITY MODE COMPLETE message has been received by UTRAN before the downlink activation time for the new ciphering configuration has been reached, ignore the activation time and apply the new ciphering configuration in downlink immediately after the RLC reset or RLC re-establishment; 2> if an RLC reset or re-establishment of the receiving side of an RLC entity occurs after the SECURITY MODE COMPLETE message has been received by UTRAN before the uplink activation time for the new ciphering configuration has been reached, ignore the activation time and apply the new ciphering configuration in uplink immediately after the RLC reset or RLC re-establishment.
3GPP
Release 6
114
3GPP TS 25.331 V6.23.0 (2009-09)
1> for radio bearers using RLC-TM: 2> use the old ciphering configuration for the received RLC PDUs before the CFN as indicated in the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info" as included in the SECURITY MODE COMMAND; 2> use the new ciphering configuration for the received RLC PDUs at the CFN as indicated in the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info" as included in the SECURITY MODE COMMAND. 1> and the procedure ends.
8.1.12.6
Invalid SECURITY MODE COMMAND message
If the SECURITY MODE COMMAND message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> transmit a SECURITY MODE FAILURE message on the uplink DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the SECURITY MODE FAILURE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the response message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; 2> only accept a message on SRB 2, with a COUNT-I that: 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and 3> does not take into account the HFN from the received SECURITY MODE COMMAND message. 2> and the procedure ends.
8.1.13
Signalling connection release procedure

UE UTRAN
SIGNALLING CONNECTION RELEASE
Figure 8.1.13-1: Signalling connection release procedure, normal case
3GPP
Release 6
115
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.13.1
General
The signalling connection release procedure is used to notify to the UE that one of its ongoing signalling connections has been released. The procedure does not initiate the release of the RRC connection.
8.1.13.2
Initiation of SIGNALLING CONNECTION RELEASE by the UTRAN
To initiate the procedure, the UTRAN transmits a SIGNALLING CONNECTION RELEASE message on DCCH using AM RLC.
8.1.13.3
Reception of SIGNALLING CONNECTION RELEASE by the UE
Upon reception of a SIGNALLING CONNECTION RELEASE message, the UE shall: 1> indicate the release of the signalling connection and pass the value of the IE "CN domain identity" to upper layers; 1> remove the signalling connection with the identity indicated by the IE "CN domain identity" from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 1> clear the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> the procedure ends.
8.1.13.4
Invalid SIGNALLING CONNECTION RELEASE message
If the UE receives a SIGNALLING CONNECTION RELEASE message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> include the IE "Identification of received message"; and 2> set the IE "Received message type" to SIGNALLING CONNECTION RELEASE; 2> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the SIGNALLING CONNECTION RELEASE message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry. 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION RELEASE message has not been received.
8.1.13.5
If radio access bearers for the CN domain indicated by the IE "CN domain identity" exist in the variable ESTABLISHED_RABS, the UE shall: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to SIGNALLING CONNECTION RELEASE; and
3GPP
Release 6
116
3GPP TS 25.331 V6.23.0 (2009-09)
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS and clear that entry; 1> include the IE "Protocol error information" with contents set to the value "Message not compatible with receiver state"; 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION RELEASE message has not been received.
8.1.14
Signalling connection release indication procedure

UE UTRAN
SIGNALLING CONNECTION RELEASE INDICATION
Figure 8.1.14-1: Signalling connection release indication procedure, normal case
8.1.14.1
General
The signalling connection release indication procedure is used by the UE to indicate to the UTRAN that one of its signalling connections has been released. The procedure may in turn initiate the RRC connection release procedure.
8.1.14.2
Initiation
The UE shall, on receiving a request to release (abort) the signalling connection from upper layers for a specific CN domain: 1> if a signalling connection in the variable ESTABLISHED_SIGNALLING_CONNECTIONS for the specific CN domain identified with the IE "CN domain identity" exists: 2> initiate the signalling connection release indication procedure. 1> otherwise: 2> abort any ongoing establishment of signalling connection for that specific CN domain as specified in 8.1.3.5a. Upon initiation of the signalling connection release indication procedure in CELL_PCH or URA_PCH state, the UE shall: 1> perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission"; 1> when the cell update procedure completed successfully: 2> continue with the signalling connection release indication procedure as below. The UE shall: 1> set the IE "CN Domain Identity" to the value indicated by the upper layers. The value of the IE indicates the CN domain whose associated signalling connection the upper layers are indicating to be released; 1> remove the signalling connection with the identity indicated by upper layers from the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
3GPP
Release 6
117
3GPP TS 25.331 V6.23.0 (2009-09)
1> transmit a SIGNALLING CONNECTION RELEASE INDICATION message on DCCH using AM RLC. When the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC the procedure ends.
8.1.14.2a
If a re-establishment of the transmitting side of the RLC entity on signalling radio bearer RB2 occurs before the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC, the UE shall: 1> retransmit the SIGNALLING CONNECTION RELEASE INDICATION message on the uplink DCCH using AM RLC on signalling radio bearer RB2. If an Inter-RAT handover from UTRAN procedure occurs before the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC, the UE shall: 1> abort the signalling connection while in the new RAT.
8.1.14.3
Reception of SIGNALLING CONNECTION RELEASE INDICATION by the UTRAN
Upon reception of a SIGNALLING CONNECTION RELEASE INDICATION message, the UTRAN requests the release of the signalling connection from upper layers. Upper layers may then initiate the release of the signalling connection.
8.1.15
Counter check procedure

UE COUNTER CHECK UTRAN
COUNTER CHECK RESPONSE
Figure 8.1.15-1: Counter check procedure
8.1.15.1
General
The counter check procedure is used by the UTRAN to perform a local authentication. The purpose of the procedure is to check that the amount of data sent in both directions (uplink and downlink) over the duration of the RRC connection is identical at the UTRAN and at the UE (to detect a possible intruder a 'man-in-the-middle' from operating). This procedure is only applicable to radio bearers, and only to radio bearers using RLC-AM or RLC-UM. It should be noted that this requires that the COUNT-C values for each UL and DL radio bearers using RLC-AM or RLC-UM continue to be incremented even if ciphering is not used. This procedure is not applicable to signalling radio bearers.
8.1.15.2
Initiation
The UTRAN monitors the COUNT-C value associated with each radio bearer using UM or AM RLC. The procedure is triggered whenever any of these values reaches a critical checking value. The granularity of these checking values and the values themselves are defined to the UTRAN by the visited network. The UTRAN initiates the procedure by sending a COUNTER CHECK message on the downlink DCCH.
3GPP
Release 6
118
3GPP TS 25.331 V6.23.0 (2009-09)
8.1.15.3
Reception of a COUNTER CHECK message by the UE
When the UE receives a COUNTER CHECK message it shall compare the COUNT-C MSB values received in the IE "RB COUNT-C MSB information" in the COUNTER CHECK message to the COUNT-C MSB values of the corresponding radio bearers. The UE shall: 1> set the IE "RRC transaction identifier" in the COUNTER CHECK RESPONSE message to the value of "RRC transaction identifier" in the entry for the COUNTER CHECK message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry. If: there is one or more radio bearer(s) using UM or AM RLC mode stored in the variable ESTABLISHED_RABS, which is (are) not included in the IE "RB COUNT-C MSB information"; or there is one or more radio bearer(s) included in the IE "RB COUNT-C MSB information", which is (are) not stored in the variable ESTABLISHED_RABS; or for any radio bearer (excluding signalling radio bearers) using UM or AM RLC mode stored in the variable ESTABLISHED_RABS and included in the IE "RB COUNT-C MSB information" with COUNT-C MSB values different from the MSB part of the COUNT-C values in the UE:
the UE shall: 1> include these radio bearers in the IE "RB COUNT-C information" in the COUNTER CHECK RESPONSE message. For any RB which is included in the IE "RB COUNT-C MSB information" in the COUNTER CHECK message but not stored in the variable ESTABLISHED_RABS in the UE, the MSB part of COUNT-C values in the COUNTER CHECK RESPONSE message shall be set identical to COUNT-C-MSB values in the COUNTER CHECK message. The LSB part shall be filled with zeroes. The UE shall: 1> if no COUNT-C exists for a radio bearer for a given direction (uplink or downlink) because: 2> it is a uni-directional radio bearer configured only for the other direction (downlink or uplink respectively); or 2> it has been configured to RLC-TM mode in one direction (uplink or downlink) and RLC-UM in the other (downlink or uplink respectively): 3> set the COUNT-C in the IE "RB COUNT-C information" in the COUNTER CHECK RESPONSE message, to any value. 1> submit a COUNTER CHECK RESPONSE message to lower layers for transmission on the uplink DCCH using AM RLC. When the COUNTER CHECK RESPONSE message has been submitted to lower layers for transmission the procedure ends.
8.1.15.4
Reception of the COUNTER CHECK RESPONSE message by UTRAN
If the UTRAN receives a COUNTER CHECK RESPONSE message that does not contain any COUNT-C values, the procedure ends. If the UTRAN receives a COUNTER CHECK RESPONSE message that contains one or several COUNT-C values the UTRAN may release the RRC connection.
8.1.15.5
Cell re-selection
If the UE performs cell re-selection anytime during this procedure it shall, without interrupting the procedure:
3GPP
Release 6
119
3GPP TS 25.331 V6.23.0 (2009-09)
1> initiate the cell update procedure according to subclause 8.3.1.
8.1.15.6
Invalid COUNTER CHECK message
If the UE receives a COUNTER CHECK message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to COUNTER CHECK; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UE COUNTER CHECK message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid COUNTER CHECK message has not been received.
8.1.16
Inter RAT handover information transfer

UE UTRAN
[ INTER RAT HANDOVER INFO ] (sent via other RAT)
Figure 8.1.16-1: Inter RAT handover information transfer, normal flow
8.1.16.1
General
The inter RAT handover information transfer procedure is used by the UE to convey RRC information needed for inter RAT handover to UTRAN.
8.1.16.2
If: -
Initiation
a radio access technology other than UTRA, e.g. GSM, using radio access technology-specific procedures, orders the UE to provide the INTER RAT HANDOVER INFO message; or a radio access technology other than UTRA, e.g. GSM, using radio access technology-specific procedures, configures the UE to send the INTER RAT HANDOVER INFO message upon system specific conditions not involving an explicit order e.g. early classmark sending upon entering connected mode; or while in connected mode using another radio access technology, the inter RAT handover info changes compared to what has previously been sent via the other radio access technology:
the UE shall:
3GPP
Release 6
120
3GPP TS 25.331 V6.23.0 (2009-09)
1> initiate the inter RAT handover information transfer procedure. To determine if the inter RAT handover info has changed compared to what has previously been sent, the UE shall: 1> store the information last sent in the variable INTER_RAT_HANDOVER_INFO_TRANSFERRED; 1> if this variable has not yet been set: 2> not initiate the inter RAT handover information transfer procedure due to change of inter RAT handover info. NOTE: Currently neither the UE security information nor the predefined configuration status information change while in connected mode using GSM radio access technology.
8.1.16.3
The UE shall:
INTER RAT HANDOVER INFO message contents to set
1> include the IE "UE security information", and the IE "UE security information2" if supported by the UE; and 1> not include the IE "UE Specific Behaviour Information 1 interRAT". 1> in case support for the compressed version of the inter RAT handover info is indicated via the other radio access technology: 2> include of the following IEs the IE that after encoding has the smallest size: IE "Predefined configuration status information compressed" or the IE "Predefined configuration status information"; 2> include the IE "UE radio access capability compressed". 1> else: 2> include the IE "Predefined configuration status information"; 2> include the IE "UE capability container", containing the IE "UE radio access capability" and the IE "UE radio access capability extension", in accordance with the following: 3> if the UE supports multiple UTRA FDD Frequency Bands; or 3> if the UE supports a single UTRA FDD Frequency Band different from Band I [21]: 4> include the IE "UE radio access capability", excluding IEs "RF capability FDD" and "Measurement capability"; 4> include the IE "UE radio access capability extension", including the IEs "RF capability FDD extension" and the "Measurement capability extension" associated with each supported UTRA FDD frequency band indicated in the IE "Frequency band". 3> else: 4> include the IE "UE radio access capability", including the IEs "RF capability FDD" and "Measurement capability" associated with the Band I [21]; 4> include the IE "UE radio access capability extension", including the IEs "RF capability FDD extension" and the "Measurement capability extension" associated with each supported UTRA FDD frequency band indicated in the IE "Frequency band". 1> For FDD, include the IE "UE radio access capability comp 2"; 1> initiate the transfer of the INTER RAT HANDOVER INFO message via the other radio access technology, using radio access technology-specific procedures; 1> store the following in the variable INTER_RAT_HANDOVER_INFO_TRANSFERRED if they were included in the INTER RAT HANDOVER INFO message: 2> the IE "Predefined configuration status information"; 2> the IE "Predefined configuration status information compressed";
3GPP
Release 6
121
3GPP TS 25.331 V6.23.0 (2009-09)
2> the IE "UE security information"; 2> the IE "UE security information2"; 2> the IE "UE radio access capability"; 2> the IE "UE radio access capability extension"; and 2> the IE "UE radio access capability compressed"; 2> if the IE "UE radio access capability compressed" were included in the INTER RAT HANDOVER INFO message: 3> set the IE "Security Capability" to the mandatory R99 algorithms. 1> and the procedure ends.
8.2
8.2.1
Radio Bearer control procedures

Radio bearer establishment
See subclause 8.2.2 Reconfiguration procedures.
8.2.2
Reconfiguration procedures
UE RADIO BEARER SETUP UTRAN
RADIO BEARER SETUP COMPLETE
Figure 8.2.2-1: Radio Bearer Establishment, normal case

UE RADIO BEARER SETUP UTRAN
RADIO BEARER SETUP FAILURE
Figure 8.2.2-2: Radio Bearer Establishment, failure case
3GPP
Release 6
122
3GPP TS 25.331 V6.23.0 (2009-09)
UE
UTRAN
RADIO BEARER RECONFIGURATION
RADIO BEARER RECONFIGURATION COMPLETE
Figure 8.2.2-3: Radio bearer reconfiguration, normal flow

UE UTRAN
RADIO BEARER RECONFIGURATION
RADIO BEARER RECONFIGURATION FAILURE
Figure 8.2.2-4: Radio bearer reconfiguration, failure case

UE RADIO BEARER RELEASE UTRAN
RADIO BEARER RELEASE COMPLETE
Figure 8.2.2-5: Radio Bearer Release, normal case

UE RADIO BEARER RELEASE UTRAN
RADIO BEARER RELEASE FAILURE
Figure 8.2.2-6: Radio Bearer Release, failure case
3GPP
Release 6
123
3GPP TS 25.331 V6.23.0 (2009-09)
UE TRANSPORT CHANNEL RECONFIGURATION
UTRAN
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
Figure 8.2.2-7: Transport channel reconfiguration, normal flow

UE TRANSPORT CHANNEL RECONFIGURATION UTRAN
TRANSPORT CHANNEL RECONFIGURATION FAILURE
Figure 8.2.2-8: Transport channel reconfiguration, failure case

UE PHYSICAL CHANNEL RECONFIGURATION UTRAN
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
Figure 8.2.2-9: Physical channel reconfiguration, normal flow

UE PHYSICAL CHANNEL RECONFIGURATION UTRAN
PHYSICAL CHANNEL RECONFIGURATION FAILURE
Figure 8.2.2-10: Physical channel reconfiguration, failure case
8.2.2.1
General
Reconfiguration procedures include the following procedures: the radio bearer establishment procedure; radio bearer reconfiguration procedure;
3GPP
Release 6
124
3GPP TS 25.331 V6.23.0 (2009-09)
the radio bearer release procedure; the transport channel reconfiguration procedure; and the physical channel reconfiguration procedure.
The radio bearer establishment procedure is used to establish new radio bearer(s). The radio bearer reconfiguration procedure is used to reconfigure parameters for a radio bearer. The radio bearer release procedure is used to release radio bearer(s). The transport channel reconfiguration procedure is used to reconfigure transport channel parameters. The physical channel reconfiguration procedure is used to establish, reconfigure and release physical channels. While performing any of the above procedures, these procedures may perform a hard handover (subclause 8.3.5) and/or an HS-DSCH cell change and/or a serving E-DCH cell change. The reconfiguration procedures are also used to change the feedback configuration for HS-DSCH.
8.2.2.2
Initiation
To initiate any one of the reconfiguration procedures, UTRAN should: 1> configure new radio links in any new physical channel configuration; 1> start transmission and reception on the new radio links; 1> for a radio bearer establishment procedure: 2> transmit a RADIO BEARER SETUP message on the downlink DCCH using AM or UM RLC; 2> if signalling radio bearer RB4 is setup with this procedure and signalling radio bearers RB1-RB3 were already established prior to the procedure: 3> if the variable "LATEST_CONFIGURED_CN_DOMAIN" has been initialised: 4> connect any radio bearers setup by the same message as signalling radio bearer RB4 to the CN domain indicated in the variable "LATEST CONFIGURED CN DOMAIN". 1> for a radio bearer reconfiguration procedure: 2> transmit a RADIO BEARER RECONFIGURATION message on the downlink DCCH using AM or UM RLC. 1> for a radio bearer release procedure: 2> transmit a RADIO BEARER RELEASE message on the downlink DCCH using AM or UM RLC. 1> for a transport channel reconfiguration procedure: 2> transmit a TRANSPORT CHANNEL RECONFIGURATION message on the downlink DCCH using AM or UM RLC. 1> for a physical channel reconfiguration procedure: 2> transmit a PHYSICAL CHANNEL RECONFIGURATION message on the downlink DCCH using AM or UM RLC. 1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure: 2> if the transmitted message is a RADIO BEARER RECONFIGURATION: 3> include the IE "New U-RNTI". 2> else:
3GPP
Release 6
125
3GPP TS 25.331 V6.23.0 (2009-09)
3> include the IE "Downlink counter synchronisation info". 2> if ciphering and/or integrity protection are activated: 3> include new ciphering and/or integrity protection configuration information to be used after reconfiguration. 2> use the downlink DCCH using AM RLC. 1> if transport channels are added, reconfigured or deleted in uplink and/or downlink: 2> set TFCS according to the new transport channel(s). 1> if transport channels are added or deleted in uplink and/or downlink, and RB Mapping Info applicable to the new configuration has not been previously provided to the UE, the UTRAN should: 2> send the RB Mapping Info for the new configuration. In the Radio Bearer Reconfiguration procedure UTRAN may indicate that uplink transmission shall be stopped or continued on certain radio bearers. Uplink transmission on a signalling radio bearer used by the RRC signalling (signalling radio bearer RB1 or signalling radio bearer RB2) should not be stopped. NOTE 1: The Release '99 RADIO BEARER RECONFIGURATION message always includes the IE "RB information to reconfigure", even if UTRAN does not require the reconfiguration of any RB. In these cases, UTRAN may include only the IE "RB identity" within the IE "RB information to reconfigure". NOTE 2: The Release '99 RADIO BEARER RECONFIGURATION message always includes the IE "Downlink information per radio link list", even if UTRAN does not require the reconfiguration of any RL. In these cases, UTRAN may re-send the currently assigned values for the mandatory IEs included within the IE "Downlink information per radio link list ". NOTE 3: The Release '99 RADIO BEARER RECONFIGURATION message always includes the IE "Primary CPICH Info" (FDD) or IE "Primary CCPCH Info" (TDD) within IE "Downlink information per radio link list". This implies that in case UTRAN applies the RADIO BEARER RECONFIGURATION message to move the UE to CELL_FACH state, it has to indicate a cell. However, UTRAN may indicate any cell; the UE anyhow performs cell selection and notifies UTRAN if it selects another cell than indicated by UTRAN. If the IE "Activation Time" is included, UTRAN should set it to a value taking the UE performance requirements into account. UTRAN should take the UE capabilities into account when setting the new configuration. If the message is used to initiate a transition from CELL_DCH to CELL_FACH state, the UTRAN may assign a CRNTI to be used in that cell by the UE.
8.2.2.2a
Initiation of handover from GERAN Iu mode
To initiate the handover from GERAN Iu mode, UTRAN should: 1> provide a RADIO BEARER RECONFIGURATION message to be encapsulated in INTERSYSTEM HANDOVER TO UTRAN COMMAND message, sent on the downlink SRB2 in GERAN Iu mode, as specified in [53]. 1> in case UTRAN decides to use a predefined or default radio configuration that is stored in the UE, it should include the following information in the RADIO BEARER RECONFIGURATION message: PhyCH information elements; and either: the IE "Predefined configuration identity", to indicate which pre-defined configuration of RB, transport channel and physical channel parameters shall be used; or the IE "Default configuration mode" and IE "Default configuration identity", to indicate which default configuration of RB, transport channel and physical channel parameters shall be used.
3GPP
Release 6
126
3GPP TS 25.331 V6.23.0 (2009-09)
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 by the UE
The UE shall: 1> be able to receive any of the following messages: 2> RADIO BEARER SETUP message; or 2> RADIO BEARER RECONFIGURATION message; or 2> RADIO BEARER RELEASE message; or 2> TRANSPORT CHANNEL RECONFIGURATION message; or 2> PHYSICAL CHANNEL RECONFIGURATION message; 1> be able to perform a hard handover and apply physical layer synchronisation procedure A as specified in [29], even if no prior UE measurements have been performed on the target cell and/or frequency. In case the reconfiguration procedure is used to remove all existing RL(s) in the active set while new RL(s) are established the UE shall: 1> For FDD: 2> if the UE has a pending "TGPS reconfiguration CFN" at the activation time received in the reconfiguration message and the reconfiguration requests a timing re-initialised hard handover (see subclause 8.3.5.1), the UE may: 3> abort the pending CM activation; 3> set the CM_PATTERN_ACTIVATION_ABORTED to TRUE. 2> otherwise: 3> set the CM_PATTERN_ACTIVATION_ABORTED to FALSE. If the UE receives: a RADIO BEARER SETUP message; or a RADIO BEARER RECONFIGURATION message; or a RADIO BEARER RELEASE message; or a TRANSPORT CHANNEL RECONFIGURATION message; or a PHYSICAL CHANNEL RECONFIGURATION message:
it shall: 1> set the variable ORDERED_RECONFIGURATION to TRUE; 1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure: 2> perform the physical layer synchronisation procedure A as specified in [29] (FDD only). 1> act upon all received information elements as specified in subclause 8.6, unless specified in the following and perform the actions below. The UE may: 1> maintain a list of the set of cells to which the UE has Radio Links if the IE "Cell ID" is present.
3GPP
Release 6
127
3GPP TS 25.331 V6.23.0 (2009-09)
The UE may first release the physical channel configuration used at reception of the reconfiguration message. The UE shall then: 1> enter a state according to subclause 8.6.3.3. In case the UE receives a RADIO BEARER RECONFIGURATION message including the IE "RB information to reconfigure" that only includes the IE "RB identity", the UE shall: 1> handle the message as if IE "RB information to reconfigure" was absent. NOTE: The ASN.1 "r3" version of the RADIO BEARER RECONFIGURATION message always includes the IE "RB information to reconfigure". UTRAN has to include it even if it does not require the reconfiguration of any RB.
In case the UE receives a RADIO BEARER RECONFIGURATION message with the IE "Specification mode" set to "Preconfiguration" while the message is not sent through GERAN Iu mode, the UE behaviour is unspecified. In case the UE receives a RADIO BEARER SETUP message with the IE "Specification mode" not set to "Complete Specification" the UE behaviour is unspecified. If after state transition the UE enters CELL_DCH state, the UE shall, after the state transition: 1> in FDD; or 1> in TDD when "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified: 2> remove any C-RNTI from MAC; 2> clear the variable C_RNTI. If after state transition the UE leaves CELL_DCH state, the UE shall, after the state transition: 1> if any IEs releated to HS-DSCH are stored in the UE: 2> clear any stored IE "Downlink HS-PDSCH information"; 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 1> if any IEs related to E-DCH are stored in the UE: 2> clear any stored IE "E-DCH info"; 2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall: 1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration; 1> in TDD: 2> if "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified: 3> remove any C-RNTI from MAC; 3> clear the variable C_RNTI. 2> if "Primary CCPCH Info" is included indicating a new target cell and "New H-RNTI" is not specified: 3> remove any H-RNTI from MAC; 3> clear the variable H_RNTI; 3> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.
3GPP
Release 6
128
3GPP TS 25.331 V6.23.0 (2009-09)
1> if "DPCH frame offset" is included for one or more RLs in the active set, and the reconfiguration procedure does not request a timing reinitialized hard handover (see subclause 8.3.5.1): 2> use its value to determine the beginning of the DPCH or F-DPCH frame in accordance with the following: 3> if the received IE "DPCH frame offset" is across the value range border compared to the DPCH or FDPCH frame offset currently used by the UE: 4> consider it to be a request to adjust the timing with 256 chips across the frame border (e.g. if the UE receives value 0 while the value currently used is 38144 consider this as a request to adjust the timing with +256 chips). 3> if after taking into account value range borders, the received IE "DPCH frame offset" corresponds to a request to adjust the timing with a step exceeding 256 chips: 4> set the variable INVALID_CONFIGURATION to TRUE. 3> and the procedure ends. 2> adjust the radio link timing accordingly. If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition: 1> if the IE "Frequency info" is included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4] on that frequency; 2> if the UE finds a suitable UTRA cell on that frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> when the cell update procedure completed successfully: 5> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 2> else, if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> when the cell update procedure completed successfully: 4> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 1> if the IE "Frequency info" is not included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4]; 2> if the UE finds a suitable UTRA cell on the current frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> when the cell update procedure completed successfully:
3GPP
Release 6
129
3GPP TS 25.331 V6.23.0 (2009-09)
5> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 2> else, if the UE can not find a suitable UTRA cell on the current frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> when the cell update procedure completed successfully: 4> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 1> start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS; 1> select PRACH according to subclause 8.5.17; 1> select Secondary CCPCH according to subclause 8.5.19; 1> use the transport format set given in system information; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> ignore that IE and stop using DRX. 1> if the contents of the variable C_RNTI is empty: 2> perform a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 2> when the cell update procedure completed successfully: 3> if the UE is in CELL_PCH or URA_PCH state: 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission"; 4> proceed as below. If the UE was in CELL_FACH state upon reception of the reconfiguration message and remains in CELL_FACH state, the UE shall: 1> if the IE "Frequency info" is included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4] on that frequency; 2> if the UE finds a suitable UTRA cell on that frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selected another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "cell reselection"; 4> when the cell update procedure completed successfully: 5> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 2> else, if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> when the cell update procedure completed successfully:
3GPP
Release 6
130
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. 1> if the IE "Frequency info" is not included in the received reconfiguration message: 2> if the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) is included the UE shall either: 3> ignore the content of the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) and proceed as below; 2> or: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CPCH info" (for TDD), and it is different from the current cell: 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> when the cell update procedure completed successfully: 5> if the UE is in CELL_PCH or URA_PCH state, initiate a cell update procedure according to subclause 8.3.1 using the cause "Uplink data transmission" and proceed as below. If after state transition the UE leaves CELL_FACH state, the UE shall: 1> stop timer T305. If after state transition the UE enters CELL_PCH or URA_PCH state, the UE shall: 1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message: 2> set the variable INVALID_CONFIGURATION to TRUE. The UE shall transmit a response message as specified in subclause 8.2.2.4, setting the information elements as specified below. The UE shall: 1> if the received reconfiguration message included the IE "Downlink counter synchronisation info"; or 1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New URNTI" is included: 2> if the variable PDCP_SN_INFO is empty: 3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "stop". 2> else: 3> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "stop"; 3> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "stop". 2> re-establish the RLC entity for RB2; 2> for the downlink and the uplink, apply the ciphering configuration as follows: 3> if the received re-configuation message included the IE "Ciphering Mode Info": 4> use the ciphering configuration in the received message when transmitting the response message. 3> if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because the activation times not having been reached: 4> if the previous SECURITY MODE COMMAND was received due to new keys being received: 5> consider the new ciphering configuration to include the received new keys;
3GPP
Release 6
131
3GPP TS 25.331 V6.23.0 (2009-09)
5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 8.1.12.3.1. 4> else if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 5> consider the new ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN; 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "START list" or IE "START" for the LATEST_CONFIGURED_CN_DOMAIN at the reception of the previous SECURITY MODE COMMAND. 4> apply the new ciphering configuration immediately following RLC re-establishment. 3> else: 4> continue using the current ciphering configuration. 2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2); 2> increment by one the downlink and uplink values of the HFN of COUNT-C for RB2; 2> calculate the START value according to subclause 8.5.9; 2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info". 1> if the received reconfiguration message did not include the IE "Downlink counter synchronisation info": 2> if the variable START_VALUE_TO_TRANSMIT is set: 3> include and set the IE "START" to the value of that variable. 2> if the variable START_VALUE_TO_TRANSMIT is not set and the IE "New U-RNTI" is included: 3> calculate the START value according to subclause 8.5.9; 3> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info". 2> if the received reconfiguration message caused a change in the RLC size for any RB using RLC-AM: 3> calculate the START value according to subclause 8.5.9; 3> include the calculated START values for the CN domain associated with the corresponding RB identity in the IE "START list" in the IE "Uplink counter synchronisation info". 1> if the received reconfiguration message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info": 2> set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable SECURITY_MODIFICATION to "Affected". 1> if the received reconfiguration message contained the IE "Ciphering mode info": 2> if the reconfiguration message is not used to perform SRNS relocation with change of ciphering algorithm: 3> the UE behaviour is not specified. 2> if the message is used to perform a timing re-initialised hard handover: 3> if IE "Ciphering activation time for DPCH" is included:
3GPP
Release 6
132
3GPP TS 25.331 V6.23.0 (2009-09)
4> the UE behaviour is not specified. 2> else: 3> if the reconfiguration message is used to setup radio bearer(s) using RLC-TM; or 3> if radio bearer(s) using RLC-TM already exist: 4> if IE "Ciphering activation time for DPCH" is not included: 5> the UE behaviour is not specified. 1> if the received reconfiguration message did not contain the IE "Ciphering activation time for DPCH" in IE "Ciphering mode info": 2> if prior to this procedure there exist no transparent mode RLC radio bearers: 3> if, at the conclusion of this procedure, the UE will be in CELL_DCH state; and 3> if, at the conclusion of this procedure, at least one transparent mode RLC radio bearer exists: 4> include the IE "COUNT-C activation time" and specify a CFN value for this IE that is a multiple of 8 frames (CFN mod 8 = 0) and lies at least 200 frames ahead of the CFN in which the response message is first transmitted. NOTE: UTRAN should not include the IE "Ciphering mode info" in any reconfiguration message unless it is also used to perform an SRNS relocation with change of ciphering algorithm.
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> if the variable PDCP_SN_INFO is not empty: 2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO. 1> in TDD, if the procedure is used to perform a handover to a cell where timing advance is enabled, and the UE can calculate the timing advance value in the new cell (i.e. in a synchronous TDD network): 2> set the IE "Uplink Timing Advance" according to subclause 8.6.6.26. 1> if the IE "Integrity protection mode info" was present in the received reconfiguration message: 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message. If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the response message: 1> if the IE "Frequency info" is included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4] on that frequency. 2> if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency: 3> proceed as below. 1> if the IE "Frequency info" is not included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4]. 1> prohibit periodical status transmission in RLC; 1> remove any C-RNTI from MAC; 1> clear the variable C_RNTI;
3GPP
Release 6
133
3GPP TS 25.331 V6.23.0 (2009-09)
1> start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS; 1> select Secondary CCPCH according to subclause 8.5.19; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in subclause 8.6.3.2. 1> if the criteria for URA update caused by "URA reselection" according to subclause 8.3.1 are fulfilled after cell selection: 2> initiate a URA update procedure according to subclause 8.3.1 using the cause "URA reselection"; 2> when the URA update procedure is successfully completed: 3> the procedure ends. If after state transition the UE enters CELL_PCH state from CELL_DCH state, the UE shall, after the state transition and transmission of the response message: 1> if the IE "Frequency info" is included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4] on that frequency. 2> if the UE finds a suitable UTRA cell on that frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> proceed as below. 2> else, if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> proceed as below. 1> if the IE "Frequency info" is not included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4]. 2> if the UE finds a suitable UTRA cell on the current frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> proceed as below. 2> else, if the UE can not find a suitable UTRA cell on the current frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> proceed as below. 1> prohibit periodical status transmission in RLC;
3GPP
Release 6
134
3GPP TS 25.331 V6.23.0 (2009-09)
1> remove any C-RNTI from MAC; 1> clear the variable C_RNTI; 1> start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS; 1> select Secondary CCPCH according to subclause 8.5.19; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in subclause 8.6.3.2. 1> the procedure ends. If after state transition the UE enters CELL_PCH state from CELL_FACH state, the UE shall, after the state transition and transmission of the response message: 1> if the IE "Frequency info" is included in the received reconfiguration message: 2> select a suitable UTRA cell according to [4] on that frequency. 2> if the UE finds a suitable UTRA cell on that frequency: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selected another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "cell reselection"; 4> proceed as below. 2> else, if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency: 3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 3> proceed as below. 1> if the IE "Frequency info" is not included in the received reconfiguration message: 2> if the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) is included the UE shall either: 3> ignore the content of the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD) and proceed as below; 2> or: 3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CPCH info" (for TDD), and it is different from the current cell: 4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection"; 4> proceed as below. 1> prohibit periodical status transmission in RLC; 1> remove any C-RNTI from MAC; 1> clear the variable C_RNTI; 1> start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS;
3GPP
Release 6
135
3GPP TS 25.331 V6.23.0 (2009-09)
1> select Secondary CCPCH according to subclause 8.5.19; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in subclause 8.6.3.2. 1> the procedure ends.
8.2.2.3a
Reception of RADIO BEARER RECONFIGURATION message by the UE performing handover from GERAN Iu mode
If the UE is performing handover from GERAN Iu mode, the UE shall, in addition to the actions in 8.2.2.3: 1> if the IE "Specification mode" is set to "Preconfiguration" and the IE "Preconfiguration mode" is set to "Predefined configuration": 2> initiate the radio bearer and transport channel configuration in accordance with the predefined parameters identified by the IE "Predefined configuration identity"; 2> initiate the physical channels in accordance with the predefined parameters identified by the IE "Predefined radio configuration identity" and the received physical channel information elements; 2> store information about the established radio access bearers and radio bearers according to the IE "Predefined configuration identity"; and 1> if the IE "Specification mode" is set to "Preconfiguration" and the IE "Preconfiguration mode" is set to "Default configuration": 2> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and the IE "Default configuration identity"; 2> initiate the physical channels in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity" and the received physical channel information elements; NOTE: The IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used.
1> if IE "Specification mode" is set to "Complete specification": 2> initiate the radio bearer, transport channel and physical channel configuration in accordance with the received radio bearer, transport channel and physical channel information elements. 1> perform an open loop estimation to determine the UL transmission power according to subclause 8.5.3; 1> set the following variables equal to the corresponding variables in GERAN Iu mode: CIPHERING_STATUS ESTABLISHED_RABS ESTABLISHED_SIGNALLING_CONNECTIONS INTEGRITY_PROTECTION_INFO INTER_RAT_HANDOVER_INFO_TRANSFERRED LATEST_CONFIGURED_CN_DOMAIN START_THRESHOLD UE_CAPABILITY_TRANSFERRED. 1> set the new uplink and downlink HFN of RB2 to MSB20(MAX(uplink HFN of RB2, downlink HFN of RB2));
3GPP
Release 6
136
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
MSB20() operation provides the HFN mapping from GERAN Iu mode to UTRAN. In GERAN Iu mode the length of HFN component of the COUNT-C of RB2 is longer than 20 bits.
1> initialise the variable TIMERS_AND_CONSTANTS to the default values and start to use those timer and constants values.
8.2.2.4
Transmission of a response message by the UE, normal case
In case the procedure was triggered by reception of a RADIO BEARER SETUP message, the UE shall: 1> transmit a RADIO BEARER SETUP COMPLETE as response message on the uplink DCCH using AM RLC. In case the procedure was triggered by reception of a RADIO BEARER RECONFIGURATION message, the UE shall: 1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC. In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall: 1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC. In case the procedure was triggered by reception of a TRANSPORT CHANNEL RECONFIGURATION message, the UE shall: 1> transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC. In case the procedure was triggered by reception of a PHYSICAL CHANNEL RECONFIGURATION message, the UE shall: 1> transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message on the uplink DCCH using AM RLC. If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition, and the UE shall: 1> if the IE "Downlink counter synchronisation info" was included in the reconfiguration message; or 1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New URNTI" is included: 2> when RLC has confirmed the successful transmission of the response message: 3> if the variable PDCP_SN_INFO is empty: 4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "continue". 3> else: 4> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "continue"; 4> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "continue". 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN; 3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
3GPP
Release 6
137
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "PDCP context relocation info" is not present: 4> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36]. 3> if the IE "PDCP context relocation info" is present: 4> perform the actions as specified in subclause 8.6.4.13. 1> if the variable PDCP_SN_INFO is empty: 2> if the received reconfiguration message contained the IE "Ciphering mode info": 3> when RLC has confirmed the successful transmission of the response message: 4> notify upper layers upon change of the security configuration; 4> perform the actions below. 2> if the received reconfiguration message did not contain the IE "Ciphering mode info": 3> when RLC has been requested to transmit the response message: 4> perform the actions below. 1> if the variable PDCP_SN_INFO is non-empty: 2> when RLC has confirmed the successful transmission of the response message: 3> for each radio bearer in the variable PDCP_SN_INFO: 4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started": 5> configure the RLC entity for that radio bearer to "continue". 3> perform the actions below. If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall: 1> when RLC has confirmed the successful transmission of the response message: 2> for each radio bearer in the variable PDCP_SN_INFO: 3> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started": 4> configure the RLC entity for that radio bearer to "continue". 2> enter the new state (CELL_PCH or URA_PCH, respectively); 2> perform the actions below. The UE shall: 1> set the variable ORDERED_RECONFIGURATION to FALSE; 1> if the received reconfiguration message contained the IE "Ciphering mode info": 2> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; 2> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 1> if the received reconfiguration message contained the IE "Integrity protection mode info": 2> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN;
3GPP
Release 6
138
3GPP TS 25.331 V6.23.0 (2009-09)
2> set "Uplink RRC Message sequence number" for signalling radio bearer RB0 in the variable INTEGRITY_PROTECTION_INFO to a value such that next RRC message to be sent on uplink RB0 will use the new integrity protection configuration; 2> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 1> clear the variable PDCP_SN_INFO; 1> clear the variable START_VALUE_TO_TRANSMIT; 1> clear the variable SECURITY_MODIFICATION.
8.2.2.5
Reception of a response message by the UTRAN, normal case
When UTRAN has received the RADIO BEARER SETUP COMPLETE message; or the RADIO BEARER RECONFIGURATION COMPLETE message; or the RADIO BEARER RELEASE COMPLETE message; or the TRANSPORT CHANNEL RECONFIGURATION COMPLETE message; or the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
UTRAN may: 1> delete the old configuration. If the procedure caused the UE to leave the CELL_FACH state, UTRAN may: 1> delete the C-RNTI of the UE. If the IE "UL Timing Advance" is included in TDD, UTRAN should: 1> evaluate the timing advance value that the UE has to use in the new cell after handover. If the IE "START" or the IE "START list " is included, UTRAN should: 1> set the START value for each CN domain with the corresponding values as received in this response message; 1> consequently, then use the START values to initialise the hyper frame numbers, in the same way as specified for the UE in subclause 8.2.2.3, for any new radio bearers that are established. If UTRAN has ordered a ciphering reconfiguration by including the IE "Ciphering mode info", UTRAN should: 1> for radio bearers using RLC-AM or RLC-UM: 2> on the receiving side of an RLC entity apply the new ciphering configuration in uplink immediately; 2> on the transmitting side of an RLC entity apply the new ciphering configuration in downlink immediately. 1> for radio bearers using RLC-TM: 2> begin incrementing the COUNT-C at the CFN only as indicated in: 3> the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode info", if included in the message that triggered the radio bearer control procedure; or 3> the IE "COUNT-C activation time", if included in the response message for this procedure. 1> and the procedure ends on the UTRAN side.
3GPP
Release 6
139
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.2.5a
Rejection by the UE
If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service, identified by the IE "MBMS Session identity", for which upper layers indicate that it has already been received correctly, the UE shall: 1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; 2> clear that entry; and 2> set the IE "failure cause" to "MBMS session already received correctly". 1> set the variable UNSUPPORTED_CONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. 1> the procedure ends. If the UTRAN establishes one or more p-t-p radio bearer(s) for the transmission of a session of an MBMS service, which will inhibit reception of one or more MBMS services which according to upper layers are of higher priority, the UE may: 1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; 2> clear that entry; and 2> set the IE "failure cause" to "Lower priority MBMS service". 1> set the variable UNSUPPORTED_CONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. 1> the procedure ends.
8.2.2.6
Unsupported configuration in the UE
If the UTRAN instructs the UE to use a configuration, which it does not support and/or if the received message causes the variable UNSUPPORTED_CONFIGURATION to be set to TRUE, the UE shall: 1> transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to "configuration unsupported". 1> set the variable UNSUPPORTED_CONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. The procedure ends.
3GPP
Release 6
140
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.2.7
Physical channel failure
If the received message caused the UE to be in CELL_DCH state and the UE according to subclause 8.5.4 failed to establish the dedicated physical channel(s) indicated in the received message or for 3.84 Mcps TDD failed to establish the physical channel(s) indicated in the received message to which DCCH(s) are mapped the UE shall: 1> For TDD or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is not set to TRUE: 2> revert to the configuration prior to the reception of the message (old configuration), including any HS-DSCH and E-DCH configuration if existing; 2> For FDD: if the UE was in Cell DCH state prior to the reconfiguration: 3> perform the physical layer synchronisation procedure A as specified in [29]; 3> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; and 3> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE or while the physical channel is not considered established;. 1> if the old configuration includes dedicated physical channels (CELL_DCH state) and the UE is unable to revert to the old configuration or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is set to TRUE: 2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure"; 2> after the cell update procedure has completed successfully: 3> proceed as below. 1> if the old configuration does not include dedicated physical channels (CELL_FACH state): 2> select a suitable UTRA cell according to [4]; 2> if the UE selects another cell than the cell the UE camped on upon reception of the reconfiguration message: 3> initiate a cell update procedure according to subclause 8.3.1, using the cause "Cell reselection"; 3> after the cell update procedure has completed successfully: 4> proceed as below. 1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to "physical channel failure". 1> set the variable ORDERED_RECONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. The procedure ends.
8.2.2.8
Cell re-selection
If the UE performs cell re-selection during the reconfiguration procedure, the UE shall: 1> initiate a cell update procedure, as specified in subclause 8.3.1;
3GPP
Release 6
141
3GPP TS 25.331 V6.23.0 (2009-09)
1> continue with the reconfiguration procedure. NOTE: After the completion of the cell update procedure and completion of the reconfiguration procedure within the UE, the UE will move to the RRC state as indicated in the reconfiguration message.
8.2.2.9
The UE shall:
Transmission of a response message by the UE, failure case
1> in case of reception of a RADIO BEARER SETUP message: 2> if the radio bearer establishment procedure affects several radio bearers: 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER SETUP FAILURE message. 2> transmit a RADIO BEARER SETUP FAILURE as response message on the DCCH using AM RLC. 1> in case of reception of a RADIO BEARER RECONFIGURATION message: 2> if the radio bearer reconfiguration procedure affects several radio bearers: 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RECONFIGURATION FAILURE message. 2> transmit a RADIO BEARER RECONFIGURATION FAILURE as response message on the DCCH using AM RLC. 1> in case of reception of a RADIO BEARER RECONFIGURATION message encapsulated in INTERSYSTEM HANDOVER TO UTRAN COMMAND message in GERAN Iu mode: 2> perform the actions as specified in [53]. 1> in case of reception of a RADIO BEARER RELEASE message: 2> if the radio bearer release procedure affects several radio bearers: 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RELEASE FAILURE message. 2> transmit a RADIO BEARER RELEASE FAILURE as response message on the DCCH using AM RLC. 1> in case of reception of a TRANSPORT CHANNEL RECONFIGURATION message: 2> transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE as response message on the DCCH using AM RLC. 1> in case of reception of a PHYSICAL CHANNEL RECONFIGURATION message: 2> transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE as response message on the DCCH using AM RLC. 1> when the response message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if no reconfiguration attempt had occurred.
8.2.2.10
Reception of a response message by the UTRAN, failure case
When the UTRAN has received: the RADIO BEARER SETUP FAILURE message; or the RADIO BEARER RECONFIGURATION FAILURE message; or the RADIO BEARER RELEASE FAILURE message; or
3GPP
Release 6
142
3GPP TS 25.331 V6.23.0 (2009-09)
the TRANSPORT CHANNEL RECONFIGURATION FAILURE message; or the PHYSICAL CHANNEL RECONFIGURATION FAILURE message:
the UTRAN may restore the old and delete the new configuration. Upper layers should be notified of the failure. The procedure ends on the UTRAN side.
8.2.2.11
If the variable INVALID_CONFIGURATION is set to TRUE the UE shall: 1> keep the configuration existing before the reception of the message; 1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 3> clear that entry. 2> set the IE "failure cause" to "invalid configuration". 1> set the variable INVALID_CONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. The procedure ends.
8.2.2.12
Incompatible simultaneous reconfiguration
If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable PROTOCOL_ERROR_REJECT is set to FALSE, the UE shall: 1> not apply the configuration contained in the received reconfiguration message; 1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to "incompatible simultaneous reconfiguration". 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. The procedure ends.
8.2.2.12a
If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION is set to TRUE due to the received reconfiguration message, the UE shall: 1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and
3GPP
Release 6
143
3GPP TS 25.331 V6.23.0 (2009-09)
2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration". 1> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE; 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. The procedure ends.
8.2.2.12b
If: -
Cell update procedure during security reconfiguration
a cell update procedure according to subclause 8.3.1 is initiated; and the received reconfiguration message causes either: the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:
the UE shall: 1> release all radio resources; 1> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; and 1> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; 1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 1> clear the variable ESTABLISHED_RABS; 1> if the received reconfiguration message contained the IE "Ciphering mode info": 2> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable SECURITY_MODIFICATION. 1> if the received reconfiguration message contained the IE "Integrity protection mode info": 2> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 1> enter idle mode; 1> perform the actions specified in subclause 8.5.2 when entering idle mode; 1> and the procedure ends. NOTE: UTRAN should use RB Control messages to perform an SRNS relocation only in case of state transitions from CELL_DCH to CELL_DCH.
3GPP
Release 6
144
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.2.13
Invalid received message
If the received reconfiguration message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to the cause value "protocol error"; 2> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. The procedure ends.
8.2.2.14
Radio link failure
If the criteria for radio link failure are met in the old configuration during the reconfiguration procedure as specified in subclause 8.5.6, the UE shall: 1> if UE would have entered CELL_PCH or URA_PCH as a result of this reconfiguration procedure and UE has already submitted a response message to lower layers: 2> act as if the reconfiguration message was not received; 2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure"; 2> the procedure ends. NOTE: UTRAN should consider the reconfiguration procedure as unsuccessful in this case even if a success response message had been received.
1> if the UE would have remained in CELL_DCH state as a result of this reconfiguration procedure: 2> initiate a cell update procedure according to subclause 8.3.1, using the cause "radio link failure"; 2> after the cell update procedure has completed successfully: 3> transmit a failure response message as specified in subclause 8.2.2.9, setting the information elements as specified below: 4> include the IE "RRC transaction identifier"; and 4> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 4> clear that entry; 4> set the IE "failure cause" to "physical channel failure". 3> act as if the reconfiguration message was not received; 3> the procedure ends. If the criteria for radio link failure are met in the new configuration during the reconfiguration procedure (i.e. while UE is waiting for RLC acknowledgement for a response message.) as specified in subclause 8.5.6, the UE shall: 1> if the received reconfiguration causes either:
3GPP
Release 6
145
3GPP TS 25.331 V6.23.0 (2009-09)
the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:
2> perform the actions specified in subclause 8.2.2.12b. 1> else, the UE should: 2> release all its radio resources; 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode; and 2> the procedure ends.
8.2.3
Radio bearer release
See subclause 8.2.2 (Reconfiguration procedures).
8.2.4
Transport channel reconfiguration
See subclause 8.2.2 (Reconfiguration procedures).
8.2.5
Transport format combination control

UE UTRAN
TRANSPORT FORMAT COMBINATION CONTROL
Figure 8.2.5-1: Transport format combination control, normal flow

UE TRANSPORT FORMAT COMBINATION CONTROL UTRAN
TRANSPORT FORMAT COMBINATION CONTROL FAILURE
Figure 8.2.5-2: Transport format combination control, failure case
3GPP
Release 6
146
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.5.1
General
The transport format combination control procedure is used to control the allowed uplink transport format combinations within the transport format combination set.
8.2.5.2
Initiation
To initiate the transport format combination control procedure, the UTRAN transmits the TRANSPORT FORMAT COMBINATION CONTROL message on the downlink DCCH using AM, UM or TM RLC. When not stated otherwise elsewhere, the UTRAN may initiate the transport format combination control procedure also when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected. To change the sub-set of allowed transport format combinations, the UTRAN should: 1> set the allowed TFCs in the IE "Transport Format Combination subset" ("TFC subset"). The UTRAN may specify the duration for which a new TFC sub-set applies by using the IE "TFC Control duration" and independently may specify the time at which a new TFC sub-set shall be applied using the IE "Activation time for TFC subset". To remove completely the previous restrictions of allowed transport format combinations, the UTRAN should: 1> set the IE "full transport format combination set " in the IE "TFC subset".
8.2.5.3
Reception of a TRANSPORT FORMAT COMBINATION CONTROL message by the UE
If the TRANSPORT FORMAT COMBINATION CONTROL message was received on AM RLC or UM RLC, the UE shall: 1> act upon all received information elements as specified in 8.6, unless specified otherwise in the following; 1> perform the actions for the transport format combination subset specified in the IE "DPCH/PUSCH TFCS in uplink" according to subclause 8.6.5.3; 1> if the variable INVALID_CONFIGURATION is set to FALSE: 2> if the IE "TFC Control duration" is included in the message: 3> store the value of the IE "TFC Control duration" in the IE "Duration" in the variable TFC_SUBSET; 3> set the IE "Current TFC subset" (for the CCTrCH indicated by the IE "TFCS Id" in case of TDD) in the variable TFC_SUBSET to the value of the IE "Transport format combination subset"; 3> at the CFN indicated by IE "Activation time for TFC subset" apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET for the number of (10 ms) frames specified in the IE "Duration"; 3> at the end of the time period defined by the IE "Duration"in the variable TFC_SUBSET: 4> if the IE "Current TFC subset" (for the CCTrCH indicated by the IE "TFCS Id" in case of TDD) in the variable TFC_SUBSET has not subsequently been changed by another message: 5> set the value of the IE "Current TFC subset" to the value of the IE "Default TFC subset" in the variable TFC_SUBSET; 5> clear the IE "Duration" in the variable TFC_SUBSET; 5> apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET; 2> if the IE "TFC Control duration" is not included in the message: 3> clear the value of the IE "Duration" in the variable TFC_SUBSET;
3GPP
Release 6
147
3GPP TS 25.331 V6.23.0 (2009-09)
3> set both the IE "Current TFC subset" and the IE "Default TFC subset" ( for the CCTrCH indicated by the IE "TFCS Id" in case of TDD) in the variable TFC_SUBSET to the value of the IE "Transport format combination subset"; 3> at the CFN indicated by the IE "Activation time for TFC subset" apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET. If the TRANSPORT FORMAT COMBINATION CONTROL message was received on TM RLC, the UE shall: 1> if the IE "TFC subset identity" identifies one of the TFC subsets stored in the IE "TFC subset list" in the variable TFC_SUBSET: 2> perform the actions as specified in subclause 8.6.5.3; 2> if the variable INVALID_CONFIGURATION is set to FALSE: 3> in the variable TFC_SUBSET, set the IE "Current TFC subset" and the IE "default TFC subset" to the value of the IE "TFC subset" in "TFC subset list" which is identified by the IE "TFC subset identity"; 3> clear the IE "Duration" in the variable TFC_SUBSET; 3> apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET. 1> if the IE "TFC subset identity" is greater than the maximum number of TFC subsets stored in the IE "TFC subset list" in the variable TFC_SUBSET: 2> set the variable INVALID_CONFIGURATION to TRUE. NOTE: The UTRAN should only send the TRANSPORT FORMAT COMBINATION CONTROL message on TM RLC in order to control the rate of TM RBs (for example, carrying multi-rate AMR or WB-AMR) otherwise the UE behaviour is not specified.
The UE shall: 1> clear the entry for the TRANSPORT FORMAT COMBINATION CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> and the procedure ends.
8.2.5.4
If the variable INVALID_CONFIGURATION is set to TRUE due to the received TRANSPORT FORMAT COMBINATION CONTROL message the UE shall: 1> if the TRANSPORT FORMAT COMBINATION CONTROL message was received on AM RLC: 2> keep the TFC subset existing before the TRANSPORT FORMAT COMBINATION CONTROL message was received; 2> transmit a TRANSPORT FORMAT COMBINATION CONTROL FAILURE message on the DCCH using AM RLC; 2> set the IE "RRC transaction identifier" in the TRANSPORT FORMAT COMBINATION CONTROL FAILURE message to the value of "RRC transaction identifier" in the entry for the TRANSPORT FORMAT COMBINATION CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to "invalid configuration"; 2> when the TRANSPORT FORMAT COMBINATION CONTROL FAILURE message has been submitted to lower layers for transmission the procedure ends. 1> if the TRANSPORT FORMAT COMBINATION CONTROL message was received on UM RLC or TM RLC:
3GPP
Release 6
148
3GPP TS 25.331 V6.23.0 (2009-09)
2> ignore the TRANSPORT FORMAT COMBINATION CONTROL message; 2> clear the entry for the TRANSPORT FORMAT COMBINATION CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS.
8.2.5.5
Invalid TRANSPORT FORMAT COMBINATION CONTROL message
If the TRANSPORT FORMAT COMBINATION CONTROL message was received on AM RLC or UM RLC and contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit a TRANSPORT FORMAT COMBINATION CONTROL FAILURE message on the uplink DCCH using AM RLC setting the information elements as specified below: 2> set the IE "RRC transaction identifier" in the TRANSPORT FORMAT COMBINATION CONTROL FAILURE message to the value of "RRC transaction identifier" in the entry for the TRANSPORT FORMAT COMBINATION CONTROL message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to the cause value "protocol error"; 2> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> when the TRANSPORT FORMAT COMBINATION CONTROL FAILURE message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid TRANSPORT FORMAT COMBINATION CONTROL message has not been received; 2> and the procedure ends. If the TRANSPORT FORMAT COMBINATION CONTROL message was received on TM RLC and contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> ignore the invalid TRANSPORT FORMAT COMBINATION CONTROL message as if it has not been received; 1> the procedure ends.
8.2.6
Physical channel reconfiguration
See subclause 8.2.2 Reconfiguration procedures.
8.2.7
Physical Shared Channel Allocation [TDD only]

UE UTRAN PHYSICAL SHARED CHANNEL ALLOCATION
Figure 8.2.7-1: Physical Shared Channel Allocation
3GPP
Release 6
149
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.7.1
General
The purpose of this procedure is to allocate radio resources to USCH and/or DSCH transport channels in TDD mode, for use by a UE. This procedure can also be used to indicate to the UE, that a PUSCH allocation is pending, in order to prevent further capacity requests from the UE. UEs are not required to receive FACH and DSCH simultaneously, i.e. if resources are allocated to DSCH the FACH reception may be suspended.
8.2.7.2
Initiation
To initiate the Physical Shared Channel Allocation procedure, the UTRAN sends the "PHYSICAL SHARED CHANNEL ALLOCATION" message on the downlink SHCCH or on the downlink DCCH using UM RLC. The DSCH-RNTI shall be included for UE identification, if the message is sent on the SHCCH.
8.2.7.3
Reception of a PHYSICAL SHARED CHANNEL ALLOCATION message by the UE
Upon reception of a "PHYSICAL SHARED CHANNEL ALLOCATION" message, if the message is received on the downlink SHCCH the UE shall: 1> check the DSCH-RNTI to see if the UE is addressed by the message; 1> if the UE is addressed by the message, or if the message is received on the downlink DCCH: 2> perform the following actions. 1> otherwise: 2> ignore the message. 1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following: 1> if the IE "ISCP Timeslot list" is included: 2> store the timeslot numbers given there for future Timeslot ISCP measurements and reports in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION. 1> if the IE "PDSCH capacity allocation info" is included: 2> configure the physical resources used for the downlink CCTrCH given by the IE "TFCS ID" according to the following: 3> if the CHOICE "Configuration" has the value "Old configuration": 4> if the UE has stored a PDSCH configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION with the identity given by the IE "PDSCH Identity": 5> configure the physical resources according to that configuration. 4> otherwise: 5> ignore the IE "PDSCH capacity allocation info". 3> if the CHOICE "Configuration" has the value "New configuration": 4> configure the physical resources according to the information given in IE "PDSCH Info". If IE "Common timeslot info" or IE "PDSCH timeslots and codes" IE are not present in IE "PDSCH Info": 5> reuse the configuration stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION for this CCTrCH. 4> if the IE "PDSCH Identity" is included:
3GPP
Release 6
150
3GPP TS 25.331 V6.23.0 (2009-09)
5> store the new configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION using that identity. 2> start using the new configuration at the CFN specified by the IE "Allocation activation time", and use that for the duration given by the IE "Allocation duration"; 2> if the IE "Confirm request" has the value "Confirm PDSCH" and IE "PDSCH Identity" is included in IE "PDSCH capacity allocation info": 3> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8. 1> if the IE "PUSCH capacity allocation info" is included: 2> stop the timer T310, if running; 2> if the CHOICE "PUSCH allocation" has the value "PUSCH allocation pending": 3> start the timer T311. 2> if the CHOICE "PUSCH allocation" has the value "PUSCH allocation assignment": 3> stop the timer T311, if running; 3> configure the physical resources used for the uplink CCTrCH given by the IE "TFCS ID" according to the following: 4> if the CHOICE "Configuration" has the value "Old configuration": 5> if the UE has stored a PUSCH configuration with the identity given by the IE "PUSCH Identity" in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION: 6> configure the physical resources according to that configuration.
5> otherwise: 6> ignore the IE "PUSCH capacity allocation info".
4> if the CHOICE "Configuration" has the value "New configuration", the UE shall: 5> configure the physical resources according to the information given in IE "PUSCH Info". If IE "Common timeslot info" or IE "PUSCH timeslots and codes" is not present in IE "PUSCH Info": 6> reuse the configuration stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION for this CCTrCH. 5> if the IE "PUSCH Identity" is included: 6> store the new configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION using that identity.
3> if the IE "PUSCH power control info" is present in this message and includes the parameter "UL target SIR" for 3.84 Mcps TDD, or the parameters "PRXPUSCHdes" and "Beacon PL Est. " and "TPC Step Size" for 1.28 Mcps TDD, or the parameters are stored in the variable PHYSICAL SHARED CHANNEL CONFIGURATION for this CCTrCH: 4> start using the new configuration at the CFN specified by the IE "Allocation activation time", and use that for the duration given by the IE "Allocation duration". 3> otherwise: 4> ignore the IE "PUSCH capacity allocation info". 3> if the IE "PUSCH power control info" is present in this message and includes the parameter "UL target SIR" for 3.84 Mcps TDD, or the parameters "PRXPUSCHdes" and/or "Beacon PL Est. " and/or "TPC Step Size" for 1.28 Mcps TDD:
3GPP
Release 6
151
3GPP TS 25.331 V6.23.0 (2009-09)
4> replace the parameters "UL target SIR" or "PRXPUSCHdes" or "TPC Step Size" stored in the variable PHYSICAL SHARED CHANNEL CONFIGURATION for this CCTrCH with the signalled values. 3> if the IE "Traffic volume report request " is included: 4> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8 at the time indicated by the IE "Traffic volume report request". 3> if the IE "Confirm request" has the value "Confirm PUSCH" and IE "PUSCH Identity" is included in IE "PUSCH capacity allocation info": 4> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8. 3> determine the TFCS subset and hence the TFCI values which are possible given the PUSCH allocation for that CCTrCH; 3> configure the MAC-c/sh in the UE with this TFCS restriction if necessary; 3> transmit USCH Transport Block Sets as required, within the TFCS limits given by the PUSCH allocation. NOTE: The UE shall: 1> clear the entry for the PHYSICAL SHARED CHANNEL ALLOCATION message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> and the procedure ends. If the UE has just entered a new cell and System Information Block Type 6 has not yet been scheduled, PUSCH/PDSCH information should be specified in the allocation message.
8.2.7.4
Invalid PHYSICAL SHARED CHANNEL ALLOCATION message
If the UE receives a PHYSICAL SHARED CHANNEL ALLOCATION message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> ignore the invalid PHYSICAL SHARED CHANNEL ALLOCATION message; 1> submit the PUSCH CAPACITY REQUEST message for transmission on the uplink SHCCH, setting the information elements in the message as specified in subclause 8.2.8.3; 1> reset counter V310; 1> start timer T310; 1> proceed as described in subclause 8.2.8.
8.2.8
PUSCH capacity request [TDD only]

UE PUSCH CAPACITY REQUEST UTRAN
PHYSICAL SHARED CHANNEL ALLOCATION
Figure 8.2.8-1: PUSCH Capacity request procedure
3GPP
Release 6
152
3GPP TS 25.331 V6.23.0 (2009-09)
8.2.8.1
General
With this procedure, the UE transmits its request for PUSCH resources to the UTRAN. In the normal case, the UTRAN responds with a PHYSICAL SHARED CHANNEL ALLOCATION message, which either allocates the requested PUSCH resources, and/or allocates a PDSCH resource, or may just serve as an acknowledgement, indicating that PUSCH allocation is pending. This procedure can also be used to acknowledge the reception of a PHYSICAL SHARED CHANNEL ALLOCATION message, or to indicate a protocol error in that message. With the PUSCH CAPACITY REQUEST message, the UE can request capacity for one or more USCH.
8.2.8.2
Initiation
This procedure is initiated: 1> in the CELL_FACH or CELL_DCH state; 1> and when at least one RB using USCH has been established; 1> and when the UE sees the requirement to request physical resources (PUSCH) for an USCH channel or there is the need to reply to a PHYSICAL SHARED CHANNEL ALLOCATION message as described in clause 8.2.7 (i.e. to confirm the reception of a message, if requested to do so, or to indicate a protocol error). The procedure can be initiated if: Timer T311 is not running. The timer T310 (capacity request repetition timer) is not running.
The UE shall: 1> set the IEs in the PUSCH CAPACITY REQUEST message according to subclause 8.2.8.3; 1> if the procedure is triggered to reply to a previous PHYSICAL SHARED CHANNEL ALLOCATION message by the IE "Confirm request" set to "Confirm PUSCH" and the IE "PUSCH capacity allocation info" is not present: 2> transmit the PUSCH CAPACITY REQUEST message on RACH. 1> else: 2> transmit the PUSCH CAPACITY REQUEST message on the uplink SHCCH. 1> set counter V310 to 1; 1> start timer T310.
8.2.8.3
PUSCH CAPACITY REQUEST message contents to set
With one PUSCH CAPACITY REQUEST message, capacity for one or more USCH can be requested. It shall include these information elements: 1> DSCH-RNTI to be used as UE identity if the message is sent on RACH; 1> Traffic volume measured results for each radio bearer satisfying the reporting criteria as specified in the MEASUREMENT CONTROL procedure (if no radio bearer satisfies the reporting criteria, traffic volume measured results shall not be included). These results shall include: 2> Radio Bearer ID of the Radio Bearer being reported; 2> RLC buffer payload for these radio bearers, as specified by the MEASUREMENT CONTROL procedure. The UE shall:
3GPP
Release 6
153
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the initiation of the procedure is triggered by the IE "Traffic volume report request" in a previously received PHYSICAL SHARED CHANNEL ALLOCATION message: 2> report the traffic volume measurement result for the radio bearer mapped on USCH transport channel specified in the received message. These results shall include: 3> Radio Bearer ID of the Radio Bearer being reported; 3> RLC buffer payload for this radio bearer. 1> if the initiation of the procedure is triggered by the IE "Confirm request" set to "Confirm PDSCH" in a previously received PHYSICAL SHARED CHANNEL ALLOCATION message and the IE "PUSCH capacity allocation info" is present in this message: 2> set the CHOICE "Allocation confirmation" to "PDSCH Confirmation" with the value given in the IE "PDSCH Identity" stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION. 1> if the initiation of the procedure is triggered by the IE "Confirm request" set to "Confirm PUSCH" in a previously received PHYSICAL SHARED CHANNEL ALLOCATION message: 2> set the CHOICE "Allocation confirmation" to "PUSCH Confirmation" with the value given in the IE "PUSCH Identity" stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION. 1> if the variable PROTOCOL_ERROR_REJECT is set to TRUE: 2> include the IE "RRC transaction identifier" in the response message transmitted below; and 2> set it to the value of "RRC transaction identifier" in the entry for the PHYSICAL SHARED CHANNEL ALLOCATION message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "protocol error indicator" to TRUE; 2> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> if the value of the variable PROTOCOL_ERROR_ REJECT is FALSE: 2> set the IE "Protocol error indicator" to FALSE. As an option, the message may include IE "Timeslot ISCP" and IE "Primary CCPCH RSCP". The timeslots for which "Timeslot ISCP" may be reported shall have been configured with a previous PHYSICAL SHARED CHANNEL ALLOCATION message and stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION. "Primary CCPCH RSCP" is reported when requested with a previous PHYSICAL SHARED CHANNEL ALLOCATION message.
8.2.8.4
Reception of a PUSCH CAPACITY REQUEST message by the UTRAN
Upon receiving a PUSCH CAPACITY REQUEST message with traffic volume measurement included for at least one radio bearer, the UTRAN should initiate the PHYSICAL SHARED CHANNEL ALLOCATION procedure, either for allocating PUSCH or PDSCH resources as required, or just as an acknowledgement, indicating a pending PUSCH allocation, as described in subclause 8.2.7.
8.2.8.5
T310 expiry
Upon expiry of timer T310, the UE shall: 1> if V310 is smaller than N310: 2> transmit a new PUSCH CAPACITY REQUEST message on the Uplink SHCCH; 2> restart timer T310;
3GPP
Release 6
154
3GPP TS 25.331 V6.23.0 (2009-09)
2> increment counter V310; 2> set the IEs in the PUSCH CAPACITY REQUEST message as specified in subclause 8.2.8.3. 1> if V310 is greater than or equal to N310: 2> the procedure ends.
8.2.9
Void
8.2.10
Uplink Physical Channel Control [TDD only]

UE UTRAN
UPLINK PHYSICAL CHANNEL CONTROL
Figure 8.2.10-1: Uplink Physical Channel Control
8.2.10.1
General
The uplink physical channel control procedure is used in TDD to control the uplink outer loop power control and timing advance running in the UE.
8.2.10.2
Initiation
The UTRAN initiates the procedure by transmitting the UPLINK PHYSICAL CHANNEL CONTROL message on the downlink DCCH using AM or UM RLC in order to update parameters for uplink open loop power control in the UE for one CCTrCH or to inform the UE about a new timing advance value to be applied. Especially, uplink interference information measured by the UTRAN can be included for the uplink timeslots used for the CCTrCH.
8.2.10.3
Reception of UPLINK PHYSICAL CHANNEL CONTROL message by the UE
Upon reception of the UPLINK PHYSICAL CHANNEL CONTROL message, the UE shall: 1> act upon all received information elements as specified in subclause 8.6. In 1.28 Mcps TDD, if the IE "Uplink DPCH Power Control Info" and IE "PRXHS-SICH" and IE "TPC step size" are transmitted, this information shall be taken into account by the UE for uplink open loop power control and for uplink closed loop power control as described in subclause 8.6.6.11, and the"PRXHS-SICH" shall be taken into account by the UE for open loop power control as described in subclause 8.5.7 and the "TPC step size" for closed loop power control on HS-SICH. In 3.84 Mcps TDD, if the IEs "Uplink DPCH Power Control Info", "PRACH Constant Value", "PUSCH Constant Value", "HS-SICH Power Control Info", "Alpha" or IE group "list of UL Timeslot Interference" are transmitted, this information shall be taken into account by the UE for uplink open loop power control as specified in subclause 8.5.7. If the UE is capable of using IPDLs for UE positioning, the IE "IPDL-Alpha" shall be used instead of the IE "Alpha". If the IE "IPDL-Alpha" parameter is not present, the UE shall use IE "Alpha". If the IE Special Burst Scheduling is transmitted the UE shall: 1> use the new value for the "Special Burst Generation Period".
3GPP
Release 6
155
3GPP TS 25.331 V6.23.0 (2009-09)
The UE shall: 1> clear the entry for the UPLINK PHYSICAL CHANNEL CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS; 1> and the procedure ends.
8.2.10.4
Invalid UPLINK PHYSICAL CHANNEL CONTROL message
If the UE receives a UPLINK PHYSICAL CHANNEL CONTROL message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC, setting the information elements as specified below: 2> include the IE "Identification of received message"; and 2> set the IE "Received message type" to UPLINK PHYSICAL CHANNEL CONTROL; and 2> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UPLINK PHYSICAL CHANNEL CONTROL message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid UPLINK PHYSICAL CHANNEL CONTROL message has not been received.
8.2.11
Physical channel reconfiguration failure

UE UTRAN
PHYSICAL CHANNEL RECONFIGURATION FAILURE
Figure 8.2.11-1: Physical channel reconfiguration failure in case of runtime configuration error
8.2.11.1
General
The physical channel reconfiguration failure procedure is used to indicate to the network a runtime configuration error in the UE.
8.2.11.2
Runtime error due to overlapping compressed mode configurations
When the UE has received from the UTRAN the configurations of several compressed mode transmission gap pattern sequences, and if several of these patterns are to be simultaneously active, the UE shall check to see if these simultaneously active transmission gap pattern sequences create transmission gaps in the same frame. An illegal overlap is created if two or more transmission gap pattern sequences create transmission gaps in the same frame, irrespective of the gaps are created in uplink or downlink.
3GPP
Release 6
156
3GPP TS 25.331 V6.23.0 (2009-09)
If the parallel transmission gap pattern sequences create an illegal overlap, the UE shall: 1> delete the overlapping transmission gap pattern sequence configuration stored in the variable TGPS_IDENTITY, which is associated with the highest value of IE "TGPSI"; 1> transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting the information elements as specified below: 2> not include the IE "RRC transaction identifier"; 2> set the cause value in IE "failure cause" to value "compressed mode runtime error". 1> terminate the inter-frequency and/or inter-RAT measurements corresponding to the deleted transmission gap pattern sequence; 1> when the PHYSICAL CHANNEL RECONFIGURATION FAILURE message has been submitted to lower layers for transmission: 2> the procedure ends.
8.2.11.3
Void
8.3
8.3.1
RRC connection mobility procedures

Cell and URA update procedures
UE CELL UPDATE UTRAN
CELL UPDATE CONFIRM
Figure 8.3.1-1: Cell update procedure, basic flow
UE CELL UPDATE
UTRAN
CELL UPDATE CONFIRM
UTRAN MOBILITY INFORMATION CONFIRM
Figure 8.3.1-2: Cell update procedure with update of UTRAN mobility information
3GPP
Release 6
157
3GPP TS 25.331 V6.23.0 (2009-09)
UE CELL UPDATE
UTRAN
CELL UPDATE CONFIRM
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
Figure 8.3.1-3: Cell update procedure with physical channel reconfiguration
UE CELL UPDATE
UTRAN
CELL UPDATE CONFIRM
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
Figure 8.3.1-4: Cell update procedure with transport channel reconfiguration
UE CELL UPDATE
UTRAN
CELL UPDATE CONFIRM
RADIO BEARER RELEASE COMPLETE
Figure 8.3.1-5: Cell update procedure with radio bearer release
UE CELL UPDATE
UTRAN
CELL UPDATE CONFIRM
RADIO BEARER RECONFIGURATION COMPLETE
Figure 8.3.1-6: Cell update procedure with radio bearer reconfiguration
3GPP
Release 6
158
3GPP TS 25.331 V6.23.0 (2009-09)
UE CELL UPDATE
UTRAN
RRC CONNECTION RELEASE
Figure 8.3.1-7: Cell update procedure, failure case
UE URA UPDATE
UTRAN
URA UPDATE CONFIRM
Figure 8.3.1-8: URA update procedure, basic flow
UE URA UPDATE
UTRAN
URA UPDATE CONFIRM
UTRAN MOBILITY INFORMATION CONFIRM
Figure 8.3.1-9: URA update procedure with update of UTRAN mobility information
UE URA UPDATE
UTRAN
RRC CONNECTION RELEASE
Figure 8.3.1-10: URA update procedure, failure case
8.3.1.1
General
The URA update and cell update procedures serve several main purposes: to notify UTRAN after re-entering service area in the URA_PCH or CELL_PCH state; to notify UTRAN of an RLC unrecoverable error [16] on an AM RLC entity; to be used as a supervision mechanism in the CELL_FACH, CELL_PCH, or URA_PCH state by means of periodical update.
3GPP
Release 6
159
3GPP TS 25.331 V6.23.0 (2009-09)
In addition, the URA update procedure also serves the following purpose: to retrieve a new URA identity after cell re-selection to a cell not belonging to the current URA assigned to the UE in URA_PCH state.
In addition, the cell update procedure also serves the following purposes: to update UTRAN with the current cell the UE is camping on after cell reselection; to act on a radio link failure in the CELL_DCH state; to act on the transmission failure of the UE CAPABILITY INFORMATION message; when triggered in the URA_PCH or CELL_PCH state, to notify UTRAN of a transition to the CELL_FACH state due to the reception of UTRAN originated paging or due to a request to transmit uplink data; to count the number of UEs in URA_PCH, CELL_PCH and CELL_FACH that are interested to receive an MBMS transmission; when triggered in the URA_PCH, CELL_PCH and CELL_FACH state, to notify UTRAN of the UEs interest to receive an MBMS service; to request the MBMS P-T-P RB setup by the UE in CELL_PCH, URA_PCH and CELL_FACH state.
The URA update and cell update procedures may: 1> include an update of mobility related information in the UE; 1> cause a state transition from the CELL_FACH state to the CELL_DCH, CELL_PCH or URA_PCH states or idle mode. The cell update procedure may also include: a re-establish of AM RLC entities; a radio bearer release, radio bearer reconfiguration, transport channel reconfiguration or physical channel reconfiguration.
8.3.1.2
Initiation
A UE shall initiate the cell update procedure in the following cases: 1> Uplink data transmission: 2> if the UE is in URA_PCH or CELL_PCH state; and 2> if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit: 3> perform cell update using the cause "uplink data transmission". 1> Paging response: 2> if the criteria for performing cell update with the cause specified above in the current subclause are not met; and 2> if the UE in URA_PCH or CELL_PCH state, receives a PAGING TYPE 1 message fulfilling the conditions for initiating a cell update procedure specified in subclause 8.1.2.3: 3> perform cell update using the cause "paging response". 1> Radio link failure: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met: 3> if the UE is in CELL_DCH state and the criteria for radio link failure are met as specified in subclause 8.5.6; or
3GPP
Release 6
160
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the transmission of the UE CAPABILITY INFORMATION message fails as specified in subclause 8.1.6.6: 4> perform cell update using the cause "radio link failure". 1> MBMS ptp RB request: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and 2> if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and 2> if the UE should perform cell update for MBMS ptp radio bearer request as specified in 8.6.9.6: 3> perform cell update using the cause "MBMS ptp RB request". 1> Re-entering service area: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and 2> if the UE is in CELL_FACH or CELL_PCH state; and 2> if the UE has been out of service area and re-enters service area before T307 or T317 expires: 3> perform cell update using the cause "re-entering service area". 1> RLC unrecoverable error: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and 2> if the UE detects RLC unrecoverable error [16] in an AM RLC entity: 3> perform cell update using the cause "RLC unrecoverable error". 1> Cell reselection: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met: 3> if the UE is in CELL_FACH or CELL_PCH state and the UE performs cell re-selection; or 3> if the UE is in CELL_FACH state and the variable C_RNTI is empty: 4> perform cell update using the cause "cell reselection". 1> Periodical cell update: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and 2> if the UE is in CELL_FACH or CELL_PCH state; and 2> if the timer T305 expires; and 2> if the criteria for "in service area" as specified in subclause 8.5.5.2 are fulfilled; and 2> if periodic updating has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity": 3> perform cell update using the cause "periodical cell update". 1> MBMS reception: 2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and
3GPP
Release 6
161
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and 2> if the UE should perform cell update for MBMS counting as specified in subclause 8.7.4: 3> perform cell update using the cause "MBMS reception". A UE in URA_PCH state shall initiate the URA update procedure in the following cases: 1> URA reselection: 2> if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not present in the list of URA identities in system information block type 2; or 2> if the list of URA identities in system information block type 2 is empty; or 2> if the system information block type 2 can not be found: 3> perform URA update using the cause "change of URA". 1> Periodic URA update: 2> if the criteria for performing URA update with the causes as specified above in the current subclause are not met; and 2> if the timer T305 expires; and 2> if periodic updating has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity": 3> perform URA update using the cause "periodic URA update". When initiating the URA update or cell update procedure, the UE shall: 1> stop timer T305; 1> if the UE is in CELL_DCH state: 2> in the variable RB_TIMER_INDICATOR, set the IE "T314 expired" and the IE "T315 expired" to FALSE; 2> if the stored values of the timer T314 and timer T315 are both equal to zero; or 2> if the stored value of the timer T314 is equal to zero and there are no radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315": 3> release all its radio resources; 3> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> clear the variable ESTABLISHED_RABS; 3> enter idle mode; 3> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2; 3> and the procedure ends. 2> if the stored value of the timer T314 is equal to zero: 3> release all radio bearers, associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314"; 3> in the variable RB_TIMER_INDICATOR set the IE "T314 expired" to TRUE;
3GPP
Release 6
162
3GPP TS 25.331 V6.23.0 (2009-09)
3> if all radio access bearers associated with a CN domain are released: 4> release the signalling connection for that CN domain; 4> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 4> indicate release (abort) of the signalling connection to upper layers; 4> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 2> if the stored value of the timer T315 is equal to zero: 3> release all radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315"; 3> in the variable RB_TIMER_INDICATOR set the IE "T315 expired" to TRUE; 3> if all radio access bearers associated with a CN domain are released: 4> release the signalling connection for that CN domain; 4> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 4> indicate release (abort) of the signalling connection to upper layers; 4> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 2> if the stored value of the timer T314 is greater than zero: 3> if there are radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314": 4> start timer T314. 3> if there are no radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314" or "useT315": 4> start timer T314. 2> if the stored value of the timer T315 is greater than zero: 3> if there are radio bearers associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315": 4> start timer T315. 2> for the released radio bearer(s): 3> delete the information about the radio bearer from the variable ESTABLISHED_RABS; 3> when all radio bearers belonging to the same radio access bearer have been released: 4> indicate local end release of the radio access bearer to upper layers using the CN domain identity together with the RAB identity stored in the variable ESTABLISHED_RABS; 4> delete all information about the radio access bearer from the variable ESTABLISHED_RABS. 2> move to CELL_FACH state; 2> select a suitable UTRA cell on the current frequency according to [4]; 2> select PRACH according to subclause 8.5.17; 2> select Secondary CCPCH according to subclause 8.5.19;
3GPP
Release 6
163
3GPP TS 25.331 V6.23.0 (2009-09)
2> use the transport format set given in system information as specified in subclause 8.6.5.1; 2> set the variable ORDERED_RECONFIGURATION to FALSE. 1> set the variables PROTOCOL_ERROR_INDICATOR, FAILURE_INDICATOR, UNSUPPORTED_CONFIGURATION and INVALID_CONFIGURATION to FALSE; 1> set the variable CELL_UPDATE_STARTED to TRUE; 1> if any IEs releated to HS-DSCHare stored in the UE: 2> clear any stored IE "Downlink HS-PDSCH information"; 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 1> if any IEs related to E-DCHare stored in the UE: 2> clear any stored IE "E-DCH info"; 2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. 1> if the UE is not already in CELL_FACH state: 2> move to CELL_FACH state; 2> select PRACH according to subclause 8.5.17; 2> select Secondary CCPCH according to subclause 8.5.19; 2> use the transport format set given in system information as specified in subclause 8.6.5.1. 1> if the UE performs cell re-selection: 2> clear the variable C_RNTI; and 2> stop using that C_RNTI just cleared from the variable C_RNTI in MAC. 1> set CFN in relation to SFN of current cell according to subclause 8.5.15; 1> in case of a cell update procedure: 2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3; 2> submit the CELL UPDATE message for transmission on the uplink CCCH. 1> in case of a URA update procedure: 2> set the contents of the URA UPDATE message according to subclause 8.3.1.3; 2> submit the URA UPDATE message for transmission on the uplink CCCH. 1> set counter V302 to 1; 1> start timer T302 when the MAC layer indicates success or failure in transmitting the message.
8.3.1.3
CELL UPDATE / URA UPDATE message contents to set
In case of cell update procedure the UE shall transmit a CELL UPDATE message. In case of URA update procedure the UE shall transmit a URA UPDATE message. The UE shall set the IEs in the CELL UPDATE message as follows: 1> set the IE "Cell update cause" corresponding to the cause specified in subclause 8.3.1.2 that is valid when the CELL UPDATE message is submitted to lower layers for transmission;
3GPP
Release 6
164
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
During the time period starting from when a cell update procedure is initiated by the UE until when the procedure ends, additional CELL UPDATE messages may be transmitted by the UE with different causes.
1> if the IE "Cell update cause" is set to "uplink data transmission" and if an event triggered traffic volume measurement has been configured: 2> if the TCTV is larger than the threshold in the IE "Reporting threshold" for a traffic volume measurement stored in the MEASUREMENT_IDENTITY variable and that traffic volume measurement has "measurement identity" equal to 4, "Traffic volume event identity" equal to "4a", "Measurement validity" equal to "all states" or "all states except CELL_DCH": 3> set the IE "Traffic volume indicator" to TRUE. 2> else: 3> set the IE "Traffic volume indicator" to FALSE. 1> set the IE "U-RNTI" to the value of the variable U_RNTI; 1> if the value of the variable PROTOCOL_ERROR_INDICATOR is TRUE: 2> include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> include and set the IE "failure cause" to the cause value "protocol error"; 2> set the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> if the value of the variable FAILURE_INDICATOR is TRUE: 2> include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS. 2> include and set the IE "failure cause" to the value of the variable FAILURE_CAUSE. 1> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised: 2> for each CN domain for which an entry exists in the variable ESTABLISHED_RABS or which is indicated in the variable LATEST CONFIGURED CN DOMAIN: 3> include the START value calculated according to subclause 8.5.9. 1> else: 2> include the START value for either the CS domain or the PS domain, calculated according to subclause 8.5.9. 1> if an unrecoverable error [16] in any of the AM RLC entities for the signalling radio bearers RB2, RB3 or RB4 is detected: 2> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to TRUE; 2> set the variable AM_RLC_ERROR_PENDING_RB234 to TRUE. 1> otherwise: 2> if the value of the variable AM_RLC_ERROR_PENDING_RB234 is TRUE: 3> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to TRUE. 2> otherwise:
3GPP
Release 6
165
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to FALSE. 1> if an unrecoverable error [16] in any of the AM RLC entities for the RB5 or upward is detected: 2> set the IE "AM_RLC error indication (RB>4)" to TRUE; 2> set the variable AM_RLC_ERROR_PENDING_RB5_AND_UP to TRUE. 1> otherwise: 2> if the value of the variable AM_RLC_ERROR_PENDING_RB5_AND_UP is TRUE: 3> set the IE "AM_RLC error indication (RB>4)" to TRUE. 2> otherwise: 3> set the IE "AM_RLC error indication (RB>4)" to FALSE. 1> set the IE "RB Timer indicator" to the value of the variable RB_TIMER_INDICATOR; 1> if the variable ESTABLISHMENT_CAUSE is initialised: 2> include the IE "Establishment cause" and set it to the value of the variable ESTABLISHMENT_CAUSE. 1> if the variable ORDERED_RECONFIGURATION is set to TRUE: 2> include the IE "Reconfiguration Status Indicator" and set it to TRUE. 1> if the IE "Cell update cause" is set to "radio link failure" and the UE has submitted a reconfiguration response message to RLC and the UE has not received the RLC acknowledgement for the response message: 2> include the IE "Reconfiguration Status Indicator" and set it to TRUE. 1> if the UE performs cell update for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and 1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service: 2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates ptp radio bearer request: 3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority; 3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8. 1> otherwise, if the UE performs cell update for MBMS counting as specified in subclause 8.7.4; and 1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service: 2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response: 3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority; 3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8. 1> if the UE included one or more "MBMS Selected Service ID" IEs: 2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29. The UE shall set the IEs in the URA UPDATE message as follows:
3GPP
Release 6
166
3GPP TS 25.331 V6.23.0 (2009-09)
1> set the IE "U-RNTI" to the value of the variable U_RNTI; 1> set the IE "URA update cause" corresponding to which cause as specified in subclause 8.3.1.2 that is valid when the URA UPDATE message is submitted to lower layers for transmission; NOTE: During the time period starting from when a URA update procedure is initiated by the UE until when the procedure ends, additional URA UPDATE messages may be transmitted by the UE with different causes, depending on which causes are valid for the respective URA UPDATE message.
1> if the value of the variable PROTOCOL_ERROR_INDICATOR is TRUE: 2 > include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> set the IE "Protocol error indicator" to TRUE; 2> include the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> if the value of the variable PROTOCOL_ERROR_INDICATOR is FALSE: 2> if the value of the variable INVALID_CONFIGURATION is TRUE: 3> include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; 3> set the IE "Protocol error indicator" to TRUE; 3> include the IE "Protocol error information" set to "Information element value not comprehended". 2> if the value of the variable INVALID_CONFIGURATION is FALSE: 3> set the IE "Protocol error indicator" to FALSE.
8.3.1.4
T305 expiry and the UE detects "out of service area"
When the T305 expires and the UE detects that it is "out of service area" as specified in subclause 8.5.5.1, the UE shall 1> start timer T307; 1> act according to subclause 7.2.2.
8.3.1.4.1
Re-entering "in service area"
If the UE detects "in service area" according to subclause 8.5.5.2 and timer T307 or T317 is running, the UE shall: 1> check the value of V302; and 1> if V302 is equal to or smaller than N302: 2> in case of a cell update procedure: 3> set the contents of the CELL UPDATE message according to subclause 8.3.1.3; 3> submit the CELL UPDATE message for transmission on the uplink CCCH. 2> in case of a URA update procedure: 3> set the contents of the URA UPDATE message according to subclause 8.3.1.3; 3> submit the URA UPDATE message for transmission on the uplink CCCH. 2> increment counter V302;
3GPP
Release 6
167
3GPP TS 25.331 V6.23.0 (2009-09)
2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> in case of a cell update procedure: 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> in case of a URA update procedure: 3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> enter idle mode; 2> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2; 2> and the procedure ends.
8.3.1.4.2
Expiry of timer T307
When the T307 expires, the UE shall: 1> move to idle mode; 1> release all dedicated resources; 1> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 1> clear the variable ESTABLISHED_RABS; 1> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2; 1> and the procedure ends.
8.3.1.5
Reception of an CELL UPDATE/URA UPDATE message by the UTRAN
When the UTRAN receives a CELL UPDATE/URA UPDATE message, the UTRAN should: 1> in case the procedure was triggered by reception of a CELL UPDATE: 2> if SRNS relocation was performed: 3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH. 2> otherwise:
3GPP
Release 6
168
3GPP TS 25.331 V6.23.0 (2009-09)
3> update the START value for each CN domain as maintained in UTRAN (refer to subclause 8.5.9) with "START" in the IE "START list" for the CN domain as indicated by "CN domain identity" in the IE "START list"; 3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH or optionally on the CCCH but only if ciphering is not required; and 3> optionally set the IE "RLC re-establish indicator (RB2, RB3 and RB4)" and/or the IE "RLC re-establish indicator (RB5 and upwards)" to TRUE to request a RLC re-establishment in the UE, in which case the corresponding RLC entities should also be re-established in UTRAN; or 1> in case the procedure was triggered by reception of a URA UPDATE: 2> if SRNS relocation was performed: 3> transmit a URA UPDATE CONFIRM message on the downlink DCCH. 2> otherwise: 3> transmit a URA UPDATE CONFIRM message on the downlink CCCH or DCCH. 2> include the IE "URA identity" in the URA UPDATE CONFIRM message in a cell where multiple URA identifiers are broadcast; or 1> initiate an RRC connection release procedure (see subclause 8.1.4) by transmitting an RRC CONNECTION RELEASE message on the downlink CCCH. In particular UTRAN should: 2> if the CELL UPDATE message was sent because of an unrecoverable error in RB2, RB3 or RB4: 3> initiate an RRC connection release procedure (subclause 8.1.4) by transmitting an RRC CONNECTION RELEASE message on the downlink CCCH. UTRAN may transmit several CELL UPDATE CONFIRM/URA UPDATE CONFIRM messages to increase the probability of proper reception of the message by the UE. In such a case, the RRC SN for these repeated messages should be the same.
8.3.1.6
Reception of the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message by the UE
When the UE receives a CELL UPDATE CONFIRM/URA UPDATE CONFIRM message; and if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or if the message is received on DCCH:
the UE may: 1> maintain a list of the set of cells to which the UE has Radio Links if the IE "Cell ID" is present. the UE shall: 1> stop timer T302; 1> in case of a cell update procedure and the CELL UPDATE CONFIRM message: 2> includes "RB information elements"; and/or 2> includes "Transport channel information elements"; and/or 2> includes "Physical channel information elements"; and 2> if the variable ORDERED_RECONFIGURATION is set to FALSE: 3> set the variable ORDERED_RECONFIGURATION to TRUE.
3GPP
Release 6
169
3GPP TS 25.331 V6.23.0 (2009-09)
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following: 2> if the IE "Frequency info" is included in the message: 3> if the IE "RRC State Indicator" is set to the value "CELL_FACH" or "CELL_PCH" or URA_PCH": 4> select a suitable UTRA cell according to [4] on that frequency; 4> if the UE finds a suitable UTRA cell on that frequency: 5> if the received CELL UPDATE CONFIRM message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received CELL UPDATE CONFIRM message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD): 6> act as specified in subclause 8.3.1.12. 4> else, if the UE can not find a suitable UTRA cell on the indicated frequency but it finds a suitable UTRA cell on another frequency: 5> act as specified in subclause 8.3.1.12. 3> if the IE "RRC State Indicator" is set to the value "CELL_DCH": 4> act on the IE "Frequency info" as specified in subclause 8.6.6.1. 2> use the transport channel(s) applicable for the physical channel types that is used; and 2> if the IE "TFS" is neither included nor previously stored in the UE for that transport channel(s): 3> use the TFS given in system information. 2> if none of the TFS stored is compatible with the physical channel: 3> delete the stored TFS; 3> use the TFS given in system information. 2> if the IE "RLC re-establish indicator (RB2, RB3 and RB4)" in the CELL UPDATE CONFIRM message is set to TRUE: 3> re-establish the RLC entities for signalling radio bearer RB2, signalling radio bearer RB3 and signalling radio bearer RB4 (if established); 3> if the value of the IE "Status" in the variable CIPHERING_STATUS of the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN is set to "Started": 4> set the HFN component of the respective COUNT-C values for AM RLC entities with RB identity 2,RB identity 3 and RB identity 4 (if established) equal to the START value included in the latest transmitted CELL UPDATE message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN. 2> if the IE "RLC re-establish indicator (RB5 and upwards)" in the CELL UPDATE CONFIRM message is set to TRUE: 3> for radio bearers with RB identity 5 and upwards: 4> re-establish the AM RLC entities; 4> if the value of the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started": 5> set the HFN component of the respective COUNT-C values for AM RLC entities equal to the START value included in this CELL UPDATE message for the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS.
3GPP
Release 6
170
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
UE actions, in case IE "Downlink counter synchronisation info" is included and either IE "RLC reestablish indicator (RB2, RB3 and RB4)" or IE "RLC re-establish indicator (RB5 and upwards)" are set to TRUE, are not defined.
1> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info": 2> set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable SECURITY_MODIFICATION to "Affected". 1> if the variable ESTABLISHMENT_CAUSE is set: 2> clear the variable ESTABLISHMENT_CAUSE. 1> enter a state according to subclause 8.6.3.3 applied on the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message. If the UE after state transition enters CELL_DCH state, it shall: 1> perform the physical layer synchronisation procedure A as specified in [29] (FDD only); 1> not prohibit periodical status transmission in RLC. If the UE after state transition remains in CELL_FACH state, it shall 1> start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity"; 1> select PRACH according to subclause 8.5.17; 1> select Secondary CCPCH according to subclause 8.5.19; 1> not prohibit periodical status transmission in RLC; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> ignore that IE and stop using DRX. If the UE after state transition enters URA_PCH or CELL_PCH state, it shall: 1> prohibit periodical status transmission in RLC; 1> clear the variable C_RNTI; 1> stop using that C_RNTI just cleared from the variable C_RNTI in MAC; 1> start the timer T305 using its initial value if timer T305 is not running and periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity"; 1> select Secondary CCPCH according to subclause 8.5.19; 1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message: 2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging Occasion and PICH Monitoring Occasion as specified in subclause 8.6.3.2. NOTE: In the case of a cell update procedure during an ongoing reconfiguration procedure moving the UE into CELL_PCH/URA_PCH then the value of the IE "UTRAN DRX Cycle length coefficient" sent in the CELL UPDATE CONFIRM message should be the same as the value sent in the reconfiguration message.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message: 2> set the variable INVALID_CONFIGURATION to TRUE. If the UE after the state transition remains in CELL_FACH state; and
3GPP
Release 6
171
3GPP TS 25.331 V6.23.0 (2009-09)
1> the contents of the variable C_RNTI are empty: it shall check the value of V302; and: 1> if V302 is equal to or smaller than N302: 2> if, caused by the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: 3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> abort the ongoing integrity and/or ciphering reconfiguration; 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info": 5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Integrity protection mode info": 5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> in case of a URA update procedure: 3> stop the URA update procedure; 3> clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and 3> continue with a cell update procedure. 2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3, except for the IE "Cell update cause" which shall be set to "cell reselection"; 2> submit the CELL UPDATE message for transmission on the uplink CCCH; 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> in case of a cell update procedure: 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> in case of a URA update procedure: 3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers;
3GPP
Release 6
172
3GPP TS 25.331 V6.23.0 (2009-09)
2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends. If the UE after the state transition remains in CELL_FACH state; and or the UE after the state transition moves to another state than the CELL_FACH state: a C-RNTI is stored in the variable C_RNTI;
the UE shall: 1> in case cell reselection interrupted an ongoing cell update procedure and a CELL UPDATE CONFIRM/URA UPDATE CONFIRM was received with the IE "Downlink counter synchronisation info" present and the response to which was not submitted to the lower layers due to the cell re-selection: 2> include the IE "START list" in the response message transmitted according to subclause 8.3.1.7; 2> if the CELL UPDATE CONFIRM/URA UPDATE CONFIRM, the response to which was not delivered to the lower layers, due to the cell re-selection, included the IE "RB with PDCP information list": 3> include the IE "RB with PDCP information list" in the response message transmitted according to subclause 8.3.1.7. 1> in case of a cell update procedure: 2> set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry. 1> in case of a URA update procedure: 2> set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 1> if the variable PDCP_SN_INFO is non-empty: 2> include the IE "RB with PDCP information list" in any response message transmitted below and set it to the value of the variable PDCP_SN_INFO. 1> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message included the IE "Downlink counter synchronisation info": 2> if the variable PDCP_SN_INFO is empty: 3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "stop". 2> else: 3> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "stop"; 3> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "stop".
3GPP
Release 6
173
3GPP TS 25.331 V6.23.0 (2009-09)
2> re-establish the RLC entity for RB2; 2> for the downlink and the uplink, apply the ciphering configuration as follows: 3> if the received re-configuation message included the IE "Ciphering Mode Info": 4> use the ciphering configuration in the received message when transmitting the response message. 3> if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because the activation times not having been reached: 4> if the previous SECURITY MODE COMMAND was received due to new keys being received: 5> consider the new ciphering configuration to include the received new keys; 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 8.1.12.3.1. 4> else if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 5> consider the new ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN; 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "START list" or IE "START" for the LATEST_CONFIGURED_CN_DOMAIN at the reception of the previous SECURITY MODE COMMAND. 4> apply the new ciphering configuration immediately following RLC re-establishment. 3> else: 4> continue using the current ciphering configuration. 2> set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2); 2> increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2; 2> calculate the START value according to subclause 8.5.9; 2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in any response message transmitted below. 1> transmit a response message as specified in subclause 8.3.1.7; 1> if the IE "Integrity protection mode info" was present in the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message. 1> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: 2> set the variable ORDERED_RECONFIGURATION to FALSE. 1> clear the variable PDCP_SN_INFO; 1> when the response message transmitted per subclause 8.3.1.7 to the UTRAN has been confirmed by RLC: 2> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Ciphering mode info":
3GPP
Release 6
174
3GPP TS 25.331 V6.23.0 (2009-09)
3> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; 3> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 3> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 2> if the CELL UPDATE CONFIRM / URA UPDATE CONFIRM message contained the IE "Integrity protection mode info": 3> set "Uplink RRC Message sequence number" for signalling radio bearer RB0 in the variable INTEGRITY_PROTECTION_INFO to a value such that next RRC message to be sent on uplink RB0 will use the new integrity protection configuration; 3> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; 3> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE. 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 1> in case of a cell update procedure: 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 1> in case of a URA update procedure: 2> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 1> set the variable CELL_UPDATE_STARTED to FALSE; 1> if the variable AM_RLC_ERROR_PENDING_RB234 is set to TRUE: 2> set the variable AM_RLC_ERROR_PENDING_RB234 to FALSE. 1> if the variable AM_RLC_ERROR_PENDING_RB5_AND_UP is set to TRUE: 2> set the variable AM_RLC_ERROR_PENDING_RB5_AND_UP to FALSE. 1> clear the variable SECURITY_MODIFICATION. 1> stop timers T314 and/or T315 if they are running. The procedure ends.
8.3.1.7
Transmission of a response message to UTRAN
If the CELL UPDATE CONFIRM message: includes the IE "RB information to release list":
the UE shall: 1> transmit a RADIO BEARER RELEASE COMPLETE as response message using AM RLC. If the CELL UPDATE CONFIRM message: does not include the IE "RB information to release list"; and includes the IE "RB information to reconfigure list"; or includes the IE "RB information to be affected list":
the UE shall: 1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using AM RLC.
3GPP
Release 6
175
3GPP TS 25.331 V6.23.0 (2009-09)
If the CELL UPDATE CONFIRM message: does not include the IE "RB information to release list", nor the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and includes "Transport channel information elements":
the UE shall: 1> transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message using AM RLC. If the CELL UPDATE CONFIRM message: does not include the IE "RB information to release list", nor the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and does not include "Transport channel information elements"; and includes "Physical channel information elements":
the UE shall: 1> transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message using AM RLC. If the CELL UPDATE CONFIRM message: does not include the IE "RB information to release list", nor the IE "RB information to reconfigure list", nor the IE "RB information to be affected list"; and does not include "Transport channel information elements"; and does not include "Physical channel information elements"; and includes "CN information elements"; or includes the IE "Ciphering mode info"; or includes the IE "Integrity protection mode info"; or includes the IE "New C-RNTI"; or includes the IE "New U-RNTI"; or includes the IE "Downlink counter synchronisation info" and the IE "New U-RNTI":
NOTE: In the case of a cell update procedure during an ongoing reconfiguration procedure moving the UE into CELL_PCH/URA_PCH the CELL UPDATE CONFIRM message should include the IE "New C-RNTI". the UE shall: 1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC. If the CELL UPDATE CONFIRM message: does not include "RB information elements"; and does not include "Transport channel information elements"; and does not include "Physical channel information elements"; and does not include "CN information elements"; and does not include the IE "Ciphering mode info"; and does not include the IE "Integrity protection mode info"; and does not include the IE "New C-RNTI"; and
3GPP
Release 6
176
3GPP TS 25.331 V6.23.0 (2009-09)
does not include the IE "New U-RNTI":
the UE shall: 1> transmit no response message. If the URA UPDATE CONFIRM message: includes "CN information elements"; or includes the IE "Ciphering mode info"; or includes the IE "Integrity protection mode info"; or includes any one or both of the IEs "New C-RNTI" and "New U-RNTI"; or includes the IE "Downlink counter synchronisation info" and the IE "New U-RNTI":
the UE shall: 1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC. If the URA UPDATE CONFIRM message: does not include "CN information elements"; and does not include the IE "Ciphering mode info"; and does not include the IE "Integrity protection mode info"; and does not include the IE "New U-RNTI"; and does not include the IE "New C-RNTI":
the UE shall: 1> transmit no response message. If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition., and the UE shall: 1> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: 2> when RLC has confirmed the successful transmission of the response message: 3> if the variable PDCP_SN_INFO is empty: 4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "continue". 3> else: 4> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "continue"; 4> configure the RLC entity for UM and AM radio bearers for which the IE " PDCP SN Info" is not included to "continue". 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN; 3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3GPP
Release 6
177
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "PDCP context relocation info" is not present: > re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36]. 3> if the IE "PDCP context relocation info" is present: 4> perform the actions as specified in subclause 8.6.4.13. 1> if the variable PDCP_SN_INFO is empty: 2> if the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info": 3> when RLC has confirmed the successful transmission of the response message: 4> continue with the remainder of the procedure. 2> if the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message did not contain the IE "Ciphering mode info": 3> when RLC has been requested to transmit the response message, 4> continue with the remainder of the procedure. 1> if the variable PDCP_SN_INFO is non-empty: 2> when RLC has confirmed the successful transmission of the response message: 3> for each radio bearer in the variable PDCP_SN_INFO: 4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started": 5> configure the RLC entity for that radio bearer to "continue". 3> continue with the remainder of the procedure. If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted in CELL_FACH state, and the UE shall: 1> when RLC has confirmed the successful transmission of the response message: 2> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN; 3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero; 3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36]. 2> for each radio bearer in the variable PDCP_SN_INFO: 3> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started": 4> configure the RLC entity for that radio bearer to "continue". 2> enter the new state (CELL_PCH or URA_PCH, respectively). 1> continue with the remainder of the procedure.
3GPP
Release 6
178
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.1.7a
Physical channel failure
If the received CELL UPDATE CONFIRM message would cause the UE to transit to CELL_DCH state: 1> if the UE failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM message according to the criteria defined in subclause 8.5.4 are not fulfilled; 1> if the received CELL UPDATE CONFIRM message does not contain dedicated physical channels; or 1> for 3.84 Mcps TDD, if the received CELL UPDATE CONFIRM does not contain physical channels to which DCCH(s) are mapped: the UE shall: 1> if, caused by the received CELL UPDATE CONFIRM message 2> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 2> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 3> abort the ongoing integrity and/or ciphering reconfiguration; 3> if the received CELL UPDATE CONFIRM message contained the IE "Ciphering mode info": 4> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 4> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 3> if the received CELL UPDATE CONFIRM message contained the IE "Integrity protection mode info": 4> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 4> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 1> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message: 2> set the IE "failure cause" to "physical channel failure"; 2> set the variable ORDERED_RECONFIGURATION to FALSE. 1> if V302 is equal to or smaller than N302: 2> select a suitable UTRA cell according to [4]; 2> set the contents of the CELL UPDATE message according to subclause 8.3.1.3, except for the IE "Cell update cause" which shall be set to "Radio link failure"; 2> submit the CELL UPDATE message for transmission on the uplink CCCH; 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> in case of a cell update procedure: 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> release all its radio resources;
3GPP
Release 6
179
3GPP TS 25.331 V6.23.0 (2009-09)
2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode.
8.3.1.8
Unsupported configuration by the UE
If the UE does not support the configuration in the CELL UPDATE CONFIRM message and/or the variable UNSUPPORTED_CONFIGURATION is set to TRUE, the UE shall: 1> if V302 is equal to or smaller than N302, the UE shall: 2> if, caused by the received CELL UPDATE CONFIRM message 3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> abort the ongoing integrity and/or ciphering reconfiguration; 4> if the received CELL UPDATE CONFIRM message contained the IE "Ciphering mode info": 5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 4> if the received CELL UPDATE CONFIRM message contained the IE "Integrity protection mode info": 5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> if the variable ORDERED_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM message in case of a cell update procedure: 3> set the variable ORDERED_RECONFIGURATION to FALSE. 2> set the variable FAILURE_INDICATOR to TRUE; 2> set the variable FAILURE_CAUSE to "Unsupported configuration"; 2> set the content of the CELL UPDATE message according to subclause 8.3.1.3; 2> submit the CELL UPDATE message for transmission on the uplink CCCH; 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302, the UE shall: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS;
3GPP
Release 6
180
3GPP TS 25.331 V6.23.0 (2009-09)
2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends.
8.3.1.9
If the variable INVALID_CONFIGURATION is set to TRUE, the UE shall: 1> if V302 is equal to or smaller than N302: 2> if, caused by the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message 3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> abort the ongoing integrity and/or ciphering reconfiguration; 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info": 5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Integrity protection mode info"; 5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: 3> set the variable ORDERED_RECONFIGURATION to FALSE. 2> in case of a cell update procedure: 3> set the variable FAILURE_INDICATOR to TRUE; 3> set the variable FAILURE_CAUSE to "Invalid configuration"; 3> set the contents of the CELL UPDATE message according to subclause 8.3.1.3; 3> submit the CELL UPDATE message for transmission on the uplink CCCH. 2> in case of a URA update procedure: 3> set the contents of the URA UPDATE message according to subclause 8.3.1.3; 3> submit the URA UPDATE message for transmission on the uplink CCCH.
3GPP
Release 6
181
3GPP TS 25.331 V6.23.0 (2009-09)
2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> the procedure ends.
8.3.1.9a
In case of a cell update procedure and if the received CELL UPDATE CONFIRM message or If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message: the UE shall: 1> if V302 is equal to or smaller than N302: 2> if, caused by the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message 3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> abort the ongoing integrity and/or ciphering reconfiguration; 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Ciphering mode info": includes the IE "RB information to release list", and/or the IE "RB information to reconfigure list", and/or the IE "RB information to be affected list", and/or includes "Transport channel information elements"; and/or includes "Physical channel information elements"; and the variable ORDERED_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration procedure;
3GPP
Release 6
182
3GPP TS 25.331 V6.23.0 (2009-09)
5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 4> if the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message contained the IE "Integrity protection mode info": 5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> if the variable ORDERED_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM message in case of a cell update procedure: 3> set the variable ORDERED_RECONFIGURATION to FALSE. 2> set the variable FAILURE_INDICATOR to TRUE; 2> set the variable FAILURE_CAUSE to "Incompatible simultaneous reconfiguration"; 2> set the content of the CELL UPDATE message according to subclause 8.3.1.3; 2> submit the CELL UPDATE message for transmission on the uplink CCCH; 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> the procedure ends.
8.3.1.9b
If: -
Security reconfiguration during Cell update procedure
the variable CELL_UPDATE_STARTED is set to TRUE; and the UE receives a SECURITY MODE COMMAND message:
3GPP
Release 6
183
3GPP TS 25.331 V6.23.0 (2009-09)
the UE shall 1> ignore the received SECURITY MODE COMMAND and continue with any ongoing processes and procedures as if the SECURITY MODE COMMAND message has not been received.
8.3.1.10
Confirmation error of URA ID list
If the URA UPDATE CONFIRM message causes a confirmation error of URA identity list as specified in subclause 8.6.2.1 the UE shall: 1> check the value of V302; and 1> if V302 is smaller or equal than N302: 2> if, caused by the received URA UPDATE CONFIRM message 3> the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE; and/or 3> the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> abort the ongoing integrity and/or ciphering reconfiguration; 4> if the received URA UPDATE CONFIRM message contained the IE "Ciphering mode info": 5> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 5> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 4> if the received URA UPDATE CONFIRM message contained the IE "Integrity protection mode info" 5> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 5> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> set the IEs in the URA UPDATE message according to subclause 8.3.1.3; 2> submit the URA UPDATE message for transmission on the uplink CCCH; 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302: 2> release all its radio resources; 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> perform the actions specified in subclause 8.5.2 when entering idle mode from connected mode; 2> the procedure ends.
3GPP
Release 6
184
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.1.11
Invalid CELL UPDATE CONFIRM/URA UPDATE CONFIRM message
If the UE receives an CELL UPDATE CONFIRM/URA UPDATE CONFIRM message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows: 1> If V302 is equal to or smaller than N302, the UE shall: 2> set the variable PROTOCOL_ERROR_INDICATOR to TRUE; 2> in case of a cell update procedure: 3> set the contents of the CELL UPDATE message according to subclause 8.3.1.3; 3> submit the CELL UPDATE message for transmission on the uplink CCCH. 2> in case of a URA update procedure: 3> set the contents of the URA UPDATE message according to subclause 8.3.1.3; 3> submit the URA UPDATE message for transmission on the uplink CCCH. 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302, the UE shall: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> in case of a cell update procedure: 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> in case of a URA update procedure: 3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> release all its radio resources; 2> enter idle mode; 2> Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> the procedure ends.
8.3.1.12
T302 expiry or cell reselection
If any or several of the following conditions are true: expiry of timer T302; reselection to another UTRA cell (including the previously serving cell) before completion of the cell update or URA update procedure;
3GPP
Release 6
185
3GPP TS 25.331 V6.23.0 (2009-09)
the UE shall: 1> stop T302 if it is running; 1> if the UE was in CELL_DCH state prior to the initiation of the procedure; and 2> if timers T314 and T315 have elapsed while T302 was running: 3> enter idle mode. 3> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers. Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2. 3> and the procedure ends. 2> if timer T314 has elapsed while T302 was running and, 3> if "T314 expired" in the variable RB_TIMER_INDICATOR is set to FALSE and 3> if T315 is still running: 4> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314"; 4> indicate release of those radio access bearers to upper layers; 4> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 4> set "T314 expired" in the variable RB_TIMER_INDICATOR to TRUE; 4> if all radio access bearers associated with a CN domain are released: 5> release the signalling connection for that CN domain; 5> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 5> indicate release (abort) of the signalling connection to upper layers; 5> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 2> if timer T315 has elapsed while T302 was running and, 3> if "T315 expired" in the variable RB_TIMER_INDICATOR is set to FALSE and, 3> if T314 is still running: 4> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315"; 4> indicate release of those radio access bearers to upper layers; 4> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 4> set "T315 expired" in the variable RB_TIMER_INDICATOR to TRUE; 4> if all radio access bearers associated with a CN domain are released: 5> release the signalling connection for that CN domain; 5> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 5> indicate release (abort) of the signalling connection to upper layers;
3GPP
Release 6
186
3GPP TS 25.331 V6.23.0 (2009-09)
5> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 2> if timers T314 and T315 are not running: 3> enter idle mode; 3> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers. Other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 3> and the procedure ends. 1> check whether it is still in "in service area" (see subclause 8.5.5.2); 1> if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: 2> set the variable ORDERED_RECONFIGURATION to FALSE. 1> in case of a cell update procedure: 2> clear any entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS. 1> in case of a URA update procedure: 2> clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS. If the UE detects "in service area" if it has not entered idle mode, and: 1> if V302 is equal to or smaller than N302, the UE shall: 2> if the UE performed cell re-selection: 3> delete its C-RNTI. 2> in case of a cell update procedure: 3> set the contents of the CELL UPDATE message according to subclauses 8.3.1.3 and 8.5.10; 3> if a CELL UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE: 4> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM message: 5> apply the new security (integrity protection) configuration received in the CELL UPDATE CONFIRM on the CELL UPDATE message. 3> submit the CELL UPDATE message for transmission on the uplink CCCH. 2> in case of a URA update procedure: 3> set the contents of the URA UPDATE message according to subclauses 8.3.1.3 and 8.5.10; 3> if a URA UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE: 4> if the IE "Downlink counter synchronisation info" was included in the received URA UPDATE CONFIRM message:
3GPP
Release 6
187
3GPP TS 25.331 V6.23.0 (2009-09)
5> apply the new security (integrity protection) configuration received in the URA UPDATE CONFIRM on the URA UPDATE message. 3> submit the URA UPDATE message for transmission on the uplink CCCH. 2> increment counter V302; 2> restart timer T302 when the MAC layer indicates success or failure to transmit the message. 1> if V302 is greater than N302, the UE shall: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> in case of a cell update procedure: 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> in case of a URA update procedure: 3> clear the entry for the URA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS. 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends. If the UE detects "out of service area", it shall: 1> act according to subclause 7.2.2.
8.3.1.13
T314 expiry
Upon expiry of timer T314 the UE shall: 1> if timer T302 is running: 2> continue awaiting response message from UTRAN. 1> if timer T302 is not running and timer T315 is running: 2> set IE "T314 expired" in variable RB_TIMER_INDICATOR to TRUE; 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314"; 2> indicate release of those radio access bearers to upper layers;
3GPP
Release 6
188
3GPP TS 25.331 V6.23.0 (2009-09)
2> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 2> if all radio access bearers associated with a CN domain are released: 3> release the signalling connection for that CN domain; 3> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> indicate release (abort) of the signalling connection to upper layers; 3> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 1> if timers T302 and T315 are not running: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends.
8.3.1.14
T315 expiry
Upon expiry of timer T315 the UE shall: 1> if timer T302 is running: 2> continue awaiting response message from UTRAN. 1> if timer T302 is not running and timer T314 is running: 2> set IE "T315 expired" in variable RB_TIMER_INDICATOR to TRUE; 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "use T315"; 2> indicate release of those radio access bearers to upper layers; 2> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 2> if all radio access bearers associated with a CN domain are released: 3> release the signalling connection for that CN domain;
3GPP
Release 6
189
3GPP TS 25.331 V6.23.0 (2009-09)
3> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> indicate release (abort) of the signalling connection to upper layers; 3> the UE may initiate the signalling connection release indication procedure, as if the upper layers requested the release (abort) of the signalling connection, according to subclause 8.1.14. 1> if timers T302 and T314 are not running: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends.
8.3.1.15
Reception of the UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN
See subclause 8.3.3.4.
8.3.2
URA update
See subclause 8.3.1.
8.3.3
UTRAN mobility information

UE UTRAN MOBILITY INFORMATION UTRAN MOBILITY INFORMATION CONFIRM UTRAN
Figure 8.3.3-1: UTRAN mobility information procedure, normal flow
3GPP
Release 6
190
3GPP TS 25.331 V6.23.0 (2009-09)
UE UTRAN MOBILITY INFORMATION
UTRAN
UTRAN MOBILITY INFORMATION FAILURE
Figure 8.3.3-2: UTRAN mobility information procedure, failure case
8.3.3.1
General
The purpose of this procedure is to allocate any one or a combination of the following to a UE in connected mode: a new C-RNTI; a new U-RNTI; other mobility related information.
8.3.3.2
Initiation
To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only.
8.3.3.3
Reception of UTRAN MOBILITY INFORMATION message by the UE
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall: 1> act on received information elements as specified in subclause 8.6; 1> if the IE "UE Timers and constants in connected mode" is present: 2> store the values of the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS, replacing any previously stored value for each timer and constant; and 2> for each updated timer value: 3> start using the new value next time the timer is started; NOTE: If a new value of timer T305 is included in the IE "UE Timers and constants in connected mode", and the old value of timer T305 is "infinity", the UE will not use the new value of the timer T305 until the next cell reselection.
2> for each updated constant value: 3> start using the new value directly; 1> if the IE "CN domain specific DRX cycle length coefficient" is present: 2> store the value of the IE "CN domain specific DRX cycle length coefficient" for that CN domain, replacing any previously stored value; and 2> use the value to determine the connected mode paging occasions according to [4]. 1> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION CONFIRM message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info" or contained the IE "Integrity protection mode info":
3GPP
Release 6
191
3GPP TS 25.331 V6.23.0 (2009-09)
2> set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable SECURITY_MODIFICATION to "Affected". 1> if the variable PDCP_SN_INFO is non-empty: 2> include the IE "RB with PDCP information list" in the UTRAN MOBILITY INFORMATION CONFIRM message and set it to the value of the variable PDCP_SN_INFO. 1> if the received UTRAN MOBILITY INFORMATION message included the IE "Downlink counter synchronisation info": 2> if the variable PDCP_SN_INFO is empty: 3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "stop". 2> else: 3> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "stop"; 3> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "stop". 2> re-establish the RLC entity for RB2; 2> for the downlink and the uplink, apply the ciphering configuration as follows: 3> if the received re-configuation message included the IE "Ciphering Mode Info": 4> use the ciphering configuration in the received message when transmitting the response message. 3> if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because the activation times not having been reached: 4> if the previous SECURITY MODE COMMAND was received due to new keys being received: 5> consider the new ciphering configuration to include the received new keys; 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 8.1.12.3.1. 4> else if the ciphering configuration for RB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 5> consider the new ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN; 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "START list" or IE "START" for the LATEST_CONFIGURED_CN_DOMAIN at the reception of the previous SECURITY MODE COMMAND. 4> apply the new ciphering configuration immediately following RLC re-establishment. 3> else: 4> continue using the current ciphering configuration. 2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2); 2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2; 2> calculate the START value according to subclause 8.5.9;
3GPP
Release 6
192
3GPP TS 25.331 V6.23.0 (2009-09)
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in the UTRAN MOBILITY INFORMATION CONFIRM message. 1> transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC; 1> if the IE "Integrity protection mode info" was present in the UTRAN MOBILITY INFORMATION message: 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted UTRAN MOBILITY INFORMATION CONFIRM message. 1> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message: 2> when RLC has confirmed the successful transmission of the response message: 3> if the variable PDCP_SN_INFO is empty: 4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except RB2 to "continue". 3> else: 4> configure the RLC entity for signalling radio bearers RB1, RB3 and RB4 to "continue"; 4> configure the RLC entity for UM and AM radio bearers for which the IE "PDCP SN Info" is not included to "continue". 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN; 3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero; 3> if the IE "PDCP context relocation info" is not present: 4> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36]. 3> if the IE "PDCP context relocation info" is present: 4> perform the actions as specified in subclause 8.6.4.13. 1> if the variable PDCP_SN_INFO is empty; and 2> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info": 3> when RLC has confirmed the successful transmission of the UTRAN MOBILITY INFORMATION CONFIRM message: 4> perform the actions below: 2> if the UTRAN MOBILITY INFORMATION message did not contain the IE "Ciphering mode info": 3> when RLC has been requested to transmit the UTRAN MOBILITY INFORMATION CONFIRM message: 4> perform the actions below. 1> if the variable PDCP_SN_INFO is non-empty: 2> when RLC has confirmed the successful transmission of the UTRAN MOBILITY INFORMATION CONFIRM message: 3> for each radio bearer in the variable PDCP_SN_INFO:
3GPP
Release 6
193
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started": 5> configure the RLC entity for that radio bearer to "continue". 3> clear the variable PDCP_SN_INFO; and 3> perform the actions below. The UE shall: 1> if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info": 2> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; 2> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO. 1> if the UTRAN MOBILITY INFORMATION message contained the IE "Integrity protection mode info": 2> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; 2> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 1> clear the variable SECURITY_MODIFICATION. The procedure ends.
8.3.3.4
Reception of an UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN
When the network receives UTRAN MOBILITY INFORMATION CONFIRM message, UTRAN may delete any old U-RNTI. The procedure ends.
8.3.3.5
Cell re-selection
If the UE performs cell re-selection, the UE shall: 1> initiate a cell update procedure according to subclause 8.3.1; 1> if the UTRAN MOBILITY INFORMATION message contains the IE "New C-RNTI"; and 1> if the UE has not yet submitted the UTRAN MOBILITY INFORMATION CONFIRM message to lower layers for transmission; and 1> if the IE "Downlink counter synchronisation info" was not included in the received UTRAN MOBILITY INFORMATION message: 2> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC; 2> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry. 2> set the IE "failure cause" to the cause value "cell update occurred"; 2> when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission: 3> continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION message has not been received and the procedure ends.
3GPP
Release 6
194
3GPP TS 25.331 V6.23.0 (2009-09)
1> otherwise: 2> if a UTRAN MOBILITY INFORMATION message was received and caused the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE; and 2> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message: 3> apply the new security (integrity protection) configuration received in the UTRAN MOBILITY INFORMATION message on the CELL UPDATE message to be transmitted. 2> continue the procedure normally.
8.3.3.5a
If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION becomes set to TRUE of the received UTRAN MOBILITY INFORMATION message, the UE shall: 1> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration"; 1> when the UTRAN MOBILITY INFORMATION FAILURE message has been delivered to lower layers for transmission: 2> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE; 2> continue with any ongoing processes and procedures as if the UTRAN MOBILITY INFORMATION message has not been received; 2> and the procedure ends.
8.3.3.6
Invalid UTRAN MOBILITY INFORMATION message
If the UTRAN MOBILITY INFORMATION message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the table "Rejected transactions" in the variable TRANSACTIONS, and; 1> clear that entry. 1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION message has not been received; 2> and the procedure ends.
3GPP
Release 6
195
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.4
Active set update

UE ACTIVE SET UPDATE UTRAN
ACTIVE SET UPDATE COMPLETE
Figure 8.3.4-1: Active Set Update procedure, successful case

UE ACTIVE SET UPDATE UTRAN
ACTIVE SET UPDATE FAILURE
Figure 8.3.4-2: Active Set Update procedure, failure case
8.3.4.1
General
The purpose of the active set update procedure is to update the active set of the connection between the UE and UTRAN. This procedure shall be used in CELL_DCH state. The UE should keep on using the old RLs while configuring the new RLs. Also the UE should keep the transmitter turned on during the procedure. This procedure is only used in FDD mode.
8.3.4.2
Initiation
The procedure is initiated when UTRAN orders a UE in CELL_DCH state, to make the following modifications of the active set of the connection: a) Radio link addition; b) Radio link removal; c) Combined radio link addition and removal; d) Addition of a radio link to the E-DCH active set; e) Removal of a radio link from the E-DCH active set. In case a) and c), UTRAN should: 1> prepare new additional radio link(s) in the UTRAN prior to the command to the UE. In all cases, UTRAN should: 1> send an ACTIVE SET UPDATE message on downlink DCCH using AM or UM RLC; 1> create active sets that contain at least one common radio link across a DPCH or F-DPCH frame boundary as the result of one or multiple (parallel) active set update procedures. UTRAN should include the following information: 1> IE "Radio Link Addition Information": Downlink DPCH information and other optional parameters relevant for the radio links to be added along with the IE "Primary CPICH info" used for the reference ID to indicate which radio link to add. This IE is needed in cases a) and c) listed above;
3GPP
Release 6
196
3GPP TS 25.331 V6.23.0 (2009-09)
1> IE "Radio Link Removal Information": IE "Primary CPICH info" used for the reference ID to indicate which radio link to remove. This IE is needed in cases b) and c) listed above; 1> IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH information" to indicate which radio link to add to the E-DCH active set. This IE is needed in case d) above, when the RL added to the E-DCH active set is already in the DCH active set; 1> IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH release indicator" to indicate which radio link to remove from the E-DCH active set. This IE is needed in case e) above, when the RL removed from the E-DCH active set remains in the DCH active set.
8.3.4.3
Reception of an ACTIVE SET UPDATE message by the UE
Upon reception of an ACTIVE SET UPDATE message the UE shall act upon all received information elements as specified in 8.6, unless specified otherwise in the following. The UE may: 1> maintain a list of the set of cells to which the UE has Radio Links if the IE "Cell ID" is present. The UE shall: 1> first add the RLs indicated in the IE "Radio Link Addition Information"; 1> remove the RLs indicated in the IE "Radio Link Removal Information". If the UE active set is full or becomes full, an RL, which is included in the IE "Radio Link Removal Information" for removal, shall be removed before adding RL, which is included in the IE "Radio Link Addition Information" for addition; 1> perform the physical layer synchronisation procedure B as specified in [29]; 1> if the IE "E-HICH information" is included: 2> store this E-HICH configuration for the concerning radio link. 1> if the IE "E-HICH information" is included: 2> store this E-RGCH configuration for the concerning radio link, if included. 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28; 1> if the radio link currently considered to be the serving HS-DSCH radio link is indicated in the IE "Radio Link Removal Information": 2> no longer consider any radio link as the serving HS-DSCH radio link; 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 1> if "Serving HS-DSCH cell information" IE is present, act on received information elements as specified in subclause 8.6: 2> if the IEs "ACK", "NACK", and "HARQ_preamble_mode" are present, act on the received information elements; 2> if the new H-RNTI and "Primary CPICH info" are included: 3> consider the cell indicated in Primary CPICH as serving HS-DSCH cell and no longer consider any other radio link as serving HS-DSCH cell. 2> if the IE "MAC-hs reset indicator" is included: 3> reset the MAC-hs entity [15]. 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.
3GPP
Release 6
197
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "E-DCH reconfiguration information" is included: 2> if the IE "E-DCH RL Info other cells" is present: 3> if the IE "E-HICH Information" is present: 4> store the E-HICH and E-RGCH information (if present), contained therein, for the indicated radio link. 3> if the IE "E-HICH release indicator" is present: 4> delete the stored E-HICH, E-AGCH and E-RGCH (if any) configurations. 3> if the IE "E-RGCH release indicator" is set present: 4> delete the stored E-RGCH configuration for this RL. 2> if the IE "E-DCH RL Info new serving cell" is present: 3> consider the cell indicated in "Primary CPICH info" as serving E-DCH radio link and no longer consider any other radio link as serving E-DCH radio link; 3> store the E-HICH and E-RGCH information (if present), contained therein, for the new serving E-DCH radio link; 3> if the IE "E-RGCH release indicator" is present: 4> delete the stored E-RGCH configuration for this RL. 3> store the newly received E-AGCH configuration; 3> if the IE "Serving Grant" is included, and if the IE "Serving Grant Value" is not included: 4> the UE behaviour is not specified. 2> if the IEs "E-DPCCH/DPCCH power offset" and/or "Reference E-TFCI PO" and/or "Power offset for scheduling info" are present, act on the received information elements. 2> if the serving E-DCH radio link was another radio link than this radio link prior to reception of the message: 3> if the IE "New Primary E-RNTI" is not included: 4> clear the Primary E-RNTI stored in the variable E_RNTI. 3> if the IE "New Secondary E-RNTI" is not included: 4> clear the Secondary E-RNTI stored in the variable E_RNTI. 1> if the radio link currently considered to be the serving E-DCH radio link is indicated in the IE "Radio Link Removal Information": 2> no longer consider any radio link as the serving E-DCH radio link. 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. 1> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE COMPLETE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH using AM RLC without waiting for the completion of the Physical Layer synchronisation B, as specified in [29]; 1> the procedure ends on the UE side.
3GPP
Release 6
198
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.4.4
Unsupported configuration in the UE
If UTRAN instructs the UE to use a configuration that it does not support, the UE shall: 1> keep the active set as it was before the ACTIVE SET UPDATE message was received; 1> transmit an ACTIVE SET UPDATE FAILURE message on the DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to "configuration unsupported"; 1> when the ACTIVE SET UPDATE FAILURE message has been submitted to lower layers for transmission: 2> the procedure ends on the UE side.
8.3.4.5
If any of the following conditions are valid: a radio link indicated by the IE "Downlink DPCH info for each RL" in the IE "Radio link addition information" has a different spreading factor than the spreading factor for the radio links in the active set that will be established at the time indicated by the IE "Activation time"; and/or a radio link in the IE "Radio link addition information" is also present in the IE "Radio Link Removal Information"; and/or the IE "Radio Link Removal Information" contains all the radio links which are part of or will be part of the active set at the time indicated by the IE "Activation time"; and/or the IE "TX Diversity Mode" is not set to "none" and it indicates a diversity mode that is different from the one currently used (<STTD> or <closed loop mode1>) in all or part of the active set; and/or a radio link indicated by the IE "Radio Link Removal Information" does not exist in the active set; and/or after the removal of all radio links indicated by the IE "Radio Link Removal Information" and the addition of all radio links indicated by the IE "Radio Link Addition Information" the active set would contain more than the maximum allowed number of radio links; and/or after the addition of all radio links indicated by the IE "Radio Link Addition Information" the active set would contain radio links indicated by the IE "Downlink DPCH info for each RL" and radio links indicated by the IE "Downlink F-DPCH info for each RL"; and/or the variable INVALID_CONFIGURATION is set to TRUE:
the UE shall: 1> keep the active set as it was before the ACTIVE SET UPDATE message was received; 1> transmit an ACTIVE SET UPDATE FAILURE message on the DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to "Invalid configuration"; 1> When the ACTIVE SET UPDATE FAILURE message has been submitted to lower layers for transmission: 2> the procedure ends on the UE side.
3GPP
Release 6
199
3GPP TS 25.331 V6.23.0 (2009-09)
If the following condition is valid: the active set update procedure results in active sets that do not contain at least one common radio link before and after a DPCH or F-DPCH frame boundary:
the UE behaviour is not specified.
8.3.4.5a
Void
8.3.4.5b
If the variable ORDERED_RECONFIGURATION is set to TRUE, the UE may: 1> if the activation time for the procedure that has set variable ORDERED_RECONFIGURATION and the activation time for the Active Set Update procedure are within a time window of 5 frames: 2> transmit an ACTIVE SET UPDATE FAILURE message on the uplink DCCH using AM RLC; 2> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration"; 2> when the ACTIVE SET UPDATE FAILURE message has been delivered to lower layers for transmission: 3> continue with any ongoing processes and procedures as if the ACTIVE SET UPDATE message has not been received. 3> and the procedure ends.
8.3.4.6
Reception of the ACTIVE SET UPDATE COMPLETE message by the UTRAN
When the UTRAN has received the ACTIVE SET UPDATE COMPLETE message, 1> the UTRAN may remove radio link(s) that are indicated to remove to the UE in case b) and c); and 1> the procedure ends on the UTRAN side.
8.3.4.7
Reception of the ACTIVE SET UPDATE FAILURE message by the UTRAN
When the UTRAN has received the ACTIVE SET UPDATE FAILURE message, the UTRAN may delete radio links that were included in the IE "Radio Link Addition Information" for addition. The procedure ends on the UTRAN side.
8.3.4.8
Invalid ACTIVE SET UPDATE message
If the ACTIVE SET UPDATE message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit a ACTIVE SET UPDATE FAILURE message on the uplink DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry;
3GPP
Release 6
200
3GPP TS 25.331 V6.23.0 (2009-09)
1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> when the ACTIVE SET UPDATE FAILURE message has been delivered to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid ACTIVE SET UPDATE message has not been received; 2> and the procedure ends.
8.3.4.9
Reception of an ACTIVE SET UPDATE message in wrong state
If the UE is in another state than CELL_DCH state upon reception of the ACTIVE SET UPDATE message, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit a ACTIVE SET UPDATE FAILURE message on the uplink DCCH using AM RLC; 1> set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible with receiver state"; 1> when the ACTIVE SET UPDATE FAILURE message has been delivered to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the ACTIVE SET UPDATE message has not been received; 2> and the procedure ends.
8.3.5
Hard handover
When performing hard handover with change of frequency, the UE shall: 1> stop all intra-frequency and inter-frequency measurement reporting on the cells listed in the variable CELL_INFO_LIST. Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.
8.3.5.1
8.3.5.1.1
Timing re-initialised hard handover

General
The purpose of the timing re-initialised hard handover procedure is to remove all the RL(s) in the active set and establish new RL(s) along with a change in the CFN in the UE according to the SFN of the target cell.(see subclause 8.5.15). For TDD timimg re-initialised hard handover is realised via CFN calculation (see subclause 8.5.15.2). NOTE: For FDD, during the hard-handover procedure, the UE will align the timing of the uplink transmission as specified in [26].
This procedure is initiated when UTRAN does not know the target SFN timing before hard handover.
3GPP
Release 6
201
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.5.1.2
Initiation (FDD only)
Timing re-initialised hard handover initiated by the UTRAN is normally performed by using the procedure "Physical channel reconfiguration" (subclause 8.2.6), but may also be performed by using either one of the following procedures: "radio bearer establishment" (subclause 8.2.1); "Radio bearer reconfiguration" (subclause 8.2.2); "Radio bearer release" (subclause 8.2.3); or "Transport channel reconfiguration" (subclause 8.2.4).
In this case of a timing re-initialised hard handover, UTRAN should include the IE "Default DPCH Offset Value" and: 1> in FDD mode: 2> if the UE is configured for DPCH: 3> set "Default DPCH Offset Value" and "DPCH frame offset" respecting the following relation (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.
2> if the UE is configured for F-DPCH: 3> set "Default DPCH Offset Value" and "DPCH frame offsetj" respecting one of the following relations: 4> (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj; or 4> (Default DPCH Offset Value+256) mod 38400 = DPCH frame offsetj, where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.
If the IE "Default DPCH Offset Value" is included, the UE shall: 1> in FDD mode: 2> if the UE is configured for DPCH: 3> if (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj, where j indicates the first radio link listed in the message:
4> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 3> else: 4> set the variable INVALID_CONFIGURATION to true. 2> if the UE is configured for F-DPCH: 3> if (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj, where j indicates the first radio link listed in the message:
4> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 3> else if (Default DPCH Offset Value+256) mod 38400 = DPCH frame offsetj, where j indicates the first radio link listed in the message:
4> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value + 256. 3> else:
3GPP
Release 6
202
3GPP TS 25.331 V6.23.0 (2009-09)
4> set the variable INVALID_CONFIGURATION to true. If the IE "Default DPCH Offset Value" is not included, the UE shall: 1> set the variable INVALID_CONFIGURATION to true.
8.3.5.2
8.3.5.2.1
Timing-maintained hard handover

General
The purpose of the Timing-maintained hard handover procedure is to remove all the RL(s) in the active set and establish new RL(s) while maintaining the CFN in the UE. For TDD timimg re-initialised hard handover is realised via CFN calculation (see subclause 8.5.15.2). NOTE: For FDD, during the hard-handover procedure, the UE will align the timing of the uplink transmission as specified in [26].
This procedure can be initiated only if UTRAN knows the target SFN timing before hard handover. The target SFN timing can be known by UTRAN in the following 2 cases: UE reads SFN when measuring "Cell synchronisation information" and sends it to the UTRAN in MEASUREMENT REPORT message. UTRAN internally knows the time difference between the cells.
8.3.5.2.2
Initiation (FDD only)
Timing-maintained hard handover initiated by the network is normally performed by using the procedure "Physical channel reconfiguration" (subclause 8.2.6), but may also be performed by using either one of the following procedures: "radio bearer establishment" (subclause 8.2.1); "Radio bearer reconfiguration" (subclause 8.2.2); "Radio bearer release" (subclause 8.2.3); or "Transport channel reconfiguration" (subclause 8.2.4).
In this case of a timing maintained hard handover procedure the UTRAN should not include the IE "Default DPCH Offset Value". If the IE "Default DPCH Offset Value" is included, the UE shall: 1> ignore the IE "Default DPCH Offset Value".
8.3.6
Inter-RAT handover to UTRAN

UE UTRAN
HANDOVER TO UTRAN COMMAND (sent via other system)
HANDOVER TO UTRAN COMPLETE
Figure 8.3.6-1: Inter-RAT handover to UTRAN, successful case
3GPP
Release 6
203
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.6.1
General
The purpose of the inter-RAT handover procedure is to, under the control of the network, transfer a connection between the UE and another radio access technology (e.g. GSM) to UTRAN.
8.3.6.2
Initiation
The procedure is initiated when a radio access technology other than UTRAN, e.g. GSM, using radio access technology-specific procedures, orders the UE to make a handover to UTRAN. A HANDOVER TO UTRAN COMMAND message is sent to the UE via the radio access technology from which interRAT handover is performed. In case UTRAN decides to uses a predefined or default radio configuration that is stored in the UE, it should include the following information in the HANDOVER TO UTRAN COMMAND message. the IE "New U-RNTI" to be assigned; the IE "Predefined configuration identity", to indicate which pre-defined configuration of RB, transport channel and physical channel parameters shall be used; or the IE "Default configuration mode" and IE "Default configuration identity", to indicate which default configuration of RB, transport channel and physical channel parameters shall be used; PhyCH information elements.
NOTE 1: When using a predefined or default configuration during handover to UTRAN, UTRAN can only assign values of IEs "New U-RNTI" and "scrambling code" that are within the special subranges defined exclusively for this procedure. UTRAN may re- assign other values after completion of the handover procedure. NOTE 2: When using a predefined or default configuration during handover to UTRAN, fewer IEs are signalled; when using this signalling option some parameters e.g. concerning compressed mode, DSCH can not be configured. In this case, the corresponding functionality can not be activated immediately. NOTE 3: When using a predefined or default configuration, the HANDOVER TO UTRAN COMMAND should not include more than one radio link. If UTRAN includes more than one radio link in the HANDOVER TO UTRAN COMMAND using a predefined or default configuration, the UE behaviour is unspecified. In case UTRAN does not use a predefined radio configuration that is stored in the UE, it should include the following information in the HANDOVER TO UTRAN COMMAND message. the IE "New U-RNTI" to be assigned; the complete set of RB, TrCH and PhyCH information elements to be used.
8.3.6.3
Reception of HANDOVER TO UTRAN COMMAND message by the UE
The UE shall be able to receive a HANDOVER TO UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target UTRAN cell and/or frequency. The UE shall act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following. The UE may: 1> maintain a list of the set of cells to which the UE has Radio Links if the IE "Cell ID" is present. The UE shall: 1> store a U-RNTI value (32 bits), which is derived by the IEs "SRNC identity" (12 bits) and "S-RNTI 2" (10 bits) included in IE "U-RNTI-short". In order to produce a full size U-RNTI value, a full size "S-RNTI" (20 bits) shall be derived by padding the IE "S-RNTI 2" with 10 zero bits in the most significant positions; and
3GPP
Release 6
204
3GPP TS 25.331 V6.23.0 (2009-09)
1> initialise the variable ESTABLISHED_SIGNALLING_CONNECTIONS with the signalling connections that remains after the handover according to the specifications of the source RAT; 1> initialise the variable UE_CAPABILITIES_TRANSFERRED with the UE capabilities that have been transferred to the network up to the point prior to the handover, if any; 1> initialise the variable TIMERS_AND_CONSTANTS to the default values and start to use those timer and constants values; 1> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Predefined configuration": 2> initiate the radio bearer and transport channel configuration in accordance with the predefined parameters identified by the IE "Predefined configuration identity"; 2> initiate the physical channels in accordance with the predefined parameters identified by the IE "Predefined radio configuration identity" and the received physical channel information elements; 2> store information about the established radio access bearers and radio bearers according to the IE "Predefined configuration identity"; and 2> set the IE "RAB Info Post" in the variable ESTABLISHED_RABS and the IE "Re-establishment timer" in the IE "RAB Info" in the variable ESTABLISHED_RABS to "useT314". 1> if IE "Specification mode" is set to "Preconfiguration" and IE "Preconfiguration mode" is set to "Default configuration": 2> initiate the radio bearer and transport channel configuration in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity"; 2> initiate the physical channels in accordance with the default parameters identified by the IE "Default configuration mode" and IE "Default configuration identity" and the received physical channel information elements; NOTE 1: IE "Default configuration mode" specifies whether the FDD or TDD version of the default configuration shall be used. 2> set the IE "RAB Info Post" in the variable ESTABLISHED_RABS and the IE "Re-establishment timer" in the IE "RAB Info" in the variable ESTABLISHED_RABS to "useT314". 1> if IE "Specification mode" is set to "Preconfiguration": 2> use the following values for parameters that are neither signalled within the HANDOVER TO UTRAN COMMAND message nor included within pre-defined or default configuration: 3> 0 dB for the power offset P Pilot-DPDCH bearer in FDD; 3> calculate the Default DPCH Offset Value using the following formula: 3> in FDD: Default DPCH Offset Value = (SRNTI 2 mod 600) * 512 3> in TDD: Default DPCH Offset Value = (SRNTI 2 mod 7) 3> handle the above Default DPCH Offset Value as if an IE with that value was included in the message, as specified in subclause 8.6.6.21. 1> if IE "Specification mode" is set to "Complete specification": 2> initiate the radio bearer, transport channel and physical channel configuration in accordance with the received radio bearer, transport channel and physical channel information elements. 1> perform an open loop estimation to determine the UL transmission power according to subclause 8.5.3;
3GPP
Release 6
205
3GPP TS 25.331 V6.23.0 (2009-09)
1> set the IE "START" for each CN domain, in the IE "START list" in the HANDOVER TO UTRAN COMPLETE message equal to the START value for each CN domain stored in the USIM if the USIM is present, or as stored in the UE for each CN domain if the SIM is present; NOTE 2: Keys received while in another RAT are not regarded as "new" (i.e.do not trigger the actions in subclause 8.1.12.3.1) in a subsequent security mode control procedure in UTRAN, irrespective of whether the keys are already being used in the other RAT or not. If the UE has received new keys in the other RAT before handover, then the START values in the USIM (sent in the HANDOVER TO UTRAN COMPLETE message and in the INTER_RAT_HANDOVER_INFO sent to the BSS while in the other RAT) will not reflect the receipt of these new keys If ciphering has been active for the CS domain in the other RAT, then during the first security mode control procedure following the Inter-RAT handover to UTRAN procedure, UE activates integrity protection using the integrity key of the key set used. The term "key set used" denotes the key set that was used in the last successfully completed RRC Security Mode Control (UTRAN), RR Cipher Mode Control procedure or GMM Authentication and Ciphering procedure (GERAN) after entering connected mode in UTRAN or GERAN. The term "if ciphering has been active for the CS domain" is defined by a successfully completed RRC Security Mode Control procedure with "Ciphering Mode Info" (UTRAN) or RR Cipher Mode Control procedure (GERAN) for the CS domain. More specifically the state of ciphering refers to the establishment of a security context where the key is loaded from the (U)SIM to the ME even if the security command indicates NULL ciphering ("no ciphering" in GERAN or UEA0 in UTRAN). 1> set the value of "THRESHOLD" in the variable "START_THRESHOLD" to the 20 MSBs of the value stored in the USIM [50] for the maximum value of START for each CN Domain, or to the default value in [40] if the SIM is present; 1> if ciphering is indicated in the HANDOVER TO UTRAN COMMAND by the presence of the IE "Ciphering Algorithm": 2> for the handover of CS domain, indicated by the IE "CN domain identity" of the IE "RAB info" of the IE "RAB information to setup" set to "CS domain" or absence of this IE, if ciphering was not active in the radio access technology from which inter-RAT handover is performed: 3> the UE behaviour is unspecified. NOTE 2a: The distinction between CS and PS domains is that CS ciphering must be maintained across an inter-RAT handover procedure, whereas PS ciphering in UTRAN is not dependent on previous ciphering status in the source radio access technology. 2> set the variable LATEST_CONFIGURED_CN_DOMAIN to the value indicated in the IE "CN domain identity" of the IE "RAB info" of the IE "RAB information to setup", or to the CS domain when this IE is not present; 2> for the CN domain in variable "LATEST_CONFIGURED_CN_DOMAIN" set the IE "Status" in the variable "CIPHERING_STATUS" to "Started"; 2> if the variable "LATEST_CONFIGURED_CN_DOMAIN" is set to "CS domain": 3> set the 20 MSB of the HFN component of the COUNT-C variable for all signalling radio bearers to the "START" value from the IE "UE security information" in the variable "INTER_RAT_HANDOVER_INFO_TRANSFERRED". 2> else if the variable "LATEST_CONFIGURED_CN_DOMAIN" is set to "PS domain": 3> set the 20 MSB of the HFN component of the COUNT-C variable for all signalling radio bearers to the "START" value from the IE "UE security information2" in the variable "INTER_RAT_HANDOVER_INFO_TRANSFERRED". 2> if the CN domain indicated in the IE "CN domain identity" of any instance of the IE "RAB info" in the IE "RAB information to setup" is "CS domain": 3> set the 20 MSB of the HFN component of the COUNT-C variable for all CS domain radio bearers to the "START" value included in the IE "UE security information" in the variable "INTER_RAT_HANDOVER_INFO_TRANSFERRED";
3GPP
Release 6
206
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the IE "Status" in the variable CIPHERING_STATUS to "Started". 2> else if the CN domain indicated in the IE "CN domain identity" of any instance of the IE "RAB info" in the IE "RAB information to setup" is "PS domain": 3> set the 20 MSB of the HFN component of the COUNT-C variable for all PS domain radio bearers to the "START" value included in the IE "UE security information2" in the variable "INTER_RAT_HANDOVER_INFO_TRANSFERRED"; 3> set the IE "Status" in the variable CIPHERING_STATUS to "Started". NOTE: It is not possible to include instances of both CS domain and PS domain bearers in the IE "RAB Info".
2> set the remaining LSBs of the HFN component of COUNT-C for all radio bearers to zero; 2> not increment the HFN component of COUNT-C for radio bearers using RLC-TM, i.e. keep the HFN value fixed without incrementing every CFN cycle; 2> set the CFN component of the COUNT-C variable for radio bearers using RLC-TM to the value of the CFN as calculated in subclause 8.5.15; 2> for all user radio bearers belonging to the "CS domain" and for signalling radio bearers when the "LATEST_CONFIGURED_CN_DOMAIN" is set to "CS domain": 3> apply the algorithm according to IE "Ciphering Algorithm" with the ciphering key of the key set used and apply ciphering immediately upon reception of the HANDOVER TO UTRAN COMMAND. 2> for all user radio bearers belonging to the "PS domain" and for signalling radio bearers when the "LATEST_CONFIGURED_CN_DOMAIN" is set to "PS domain": 3> apply the algorithm according to IE "Ciphering Algorithm" with the ciphering key stored in the USIM/SIM and apply ciphering immediately upon reception of the HANDOVER TO UTRAN COMMAND. NOTE 3: If ciphering is indicated in the HANDOVER TO UTRAN COMMAND, UTRAN should not include the IE "Ciphering mode info" in the SECURITY MODE COMMAND message that starts Integrity protection. NOTE 4: Void. 1> if ciphering is not indicated in the HANDOVER TO UTRAN COMMAND: 2> for the CN domain(s) included in the IE "CN domain identity" which is included in the IE "RAB info" of the IE "RAB information to setup", or the CS domain when these IEs are not present: 3> set the IE "Status" in the variable CIPHERING_STATUS to "Not Started". If the UE succeeds in establishing the connection to UTRAN, it shall: 1> if CN domain is set to CS domain only indicate to upper layers that no CN system information is available for any domain other than the CS domain (see NOTE 5); 1> if CN domain is set to PS domain only indicate to upper layers that no CN system information is available for any domain other than the PS domain (see NOTE 6); NOTE 5: After CS handover has been completed, the UTRAN should provide the UE with the CN system information of the PS domain as soon as possible, in order not to delay access to the PS domain. NOTE 6: After PS handover has been completed, the UTRAN should provide the UE with the CN system information of the CS and PS domain as soon as possible in order not to delay access to the CS domain and trigger a NAS procedure for the PS domain. 1> if the USIM or SIM is present: 2> set the START value stored in the USIM [50] if present, and as stored in the UE if the SIM is present for any CN domain to the value "THRESHOLD" of the variable START_THRESHOLD.
3GPP
Release 6
207
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Status" in the variable CIPHERING_STATUS of a CN domain is set to "Started" and transparent mode radio bearers have been established by this procedure for that CN domain: 2> include the IE "COUNT-C activation time" in the response message and specify a CFN value for this IE other than the default, "Now", that is a multiple of 8 frames (CFN mod 8 =0) and lies at least 200 frames ahead of the CFN in which the response message is first transmitted; 2> at the CFN value as indicated in the response message in the IE "COUNT-C activation time" for radio bearers using RLC-TM: 3> set the 20 MSB of the HFN component of the COUNT-C variable common for all transparent mode radio bearers of this CN domain to the START value as indicated in the IE "START list" of the response message for the relevant CN domain; and 3> set the remaining LSBs of the HFN component of COUNT-C to zero; 3> increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is equal to zero; 3> set the CFN component of the COUNT-C to the value of the IE "COUNT-C activation time" of the response message. The HFN component and the CFN component completely initialise the COUNT-C variable; 3> step the COUNT-C variable, as normal, at each CFN value. The HFN component is no longer fixed in value but incremented at each CFN cycle. 1> if the IE "Status" in the variable CIPHERING_STATUS of a CN domain is set to "Not Started" and transparent mode radio bearers have been established by this procedure for that CN domain: 2> initialise the 20 MSB of the HFN component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value as indicated in the IE "START list" of the response message for the relevant CN domain; 2> set the remaining LSBs of the HFN component of COUNT-C to zero; 2> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain. 1> transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH, using, if ciphering has been started, the new ciphering configuration; 1> when the HANDOVER TO UTRAN COMPLETE message has been submitted to lower layers for transmission: 2> enter UTRA RRC connected mode in state CELL_DCH; 2> initialise variables upon entering UTRA RRC connected mode as specified in subclause 13.4; 2> update the variable UE_CAPABILITY_TRANSFERRED with the UE capabilities stored in the variable INTER_RAT_HANDOVER_INFO_TRANSFERRED. 1> and the procedure ends.
8.3.6.4
Invalid Handover to UTRAN command message
If the UE receives a HANDOVER TO UTRAN COMMAND message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling according to the source radio access technology. The UE shall: 1> if allowed by the source RAT: 2> transmit an RRC FAILURE INFO message to the source radio access technology; and 2> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> Other details may be provided in the specifications related to the source radio access technology.
3GPP
Release 6
208
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
The other RAT may include the above diagnostics information in a subsequent handover request towards the same RNC.
8.3.6.4a
Unsupported configuration in HANDOVER TO UTRAN COMMAND message
If the UE does not support the configuration included in the HANDOVER TO UTRAN COMMAND message, e.g., the message includes a pre-defined configuration that the UE has not stored, the UE shall: 1> continue the connection using the other radio access technology; and 1> indicate the failure to the other radio access technology.
8.3.6.5
UE fails to perform handover
If the UE does not succeed in establishing the connection to UTRAN, it shall: 1> terminate the procedure including release of the associated resources; 1> resume the connection used before the handover; and 1> indicate the failure to the other radio access technology. Upon receiving an indication about the failure from the other radio access technology, UTRAN should release the associated resources and the context information concerning this UE.
8.3.6.6
Reception of message HANDOVER TO UTRAN COMPLETE by the UTRAN
Upon receiving a HANDOVER TO UTRAN COMPLETE message, UTRAN should consider the inter-RAT handover procedure as having been completed successfully and indicate this to the Core Network.
8.3.7
Inter-RAT handover from UTRAN

UE UTRAN
HANDOVER FROM UTRAN COMMAND
Figure 8.3.7-1: Inter-RAT handover from UTRAN, successful case

UE UTRAN
HANDOVER FROM UTRAN COMMAND
HANDOVER FROM UTRAN FAILURE
Figure 8.3.7-2: Inter-RAT handover from UTRAN, failure case
3GPP
Release 6
209
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.7.1
General
The purpose of the inter-RAT handover procedure is to, under the control of the network, transfer a connection between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in CELL_DCH state. This procedure may be used to perform CS handover which applies when the variable ESTABLISHED_SIGNALLING_CONNECTIONS includes at least the CN domain identity "CS Domain". When the UE supports Inter Rat PS handover, this procedure may be used to perform PS handover which applies when the variable ESTABLISHED_SIGNALLING_CONNECTIONS includes at least the CN domain identity "PS Domain".
8.3.7.2
Initiation
The procedure is initiated when UTRAN orders a UE in CELL_DCH state, to make a handover to a radio access technology other than UTRAN, e.g. GSM. To initiate the procedure, UTRAN sends a HANDOVER FROM UTRAN COMMAND message.
8.3.7.3
Reception of a HANDOVER FROM UTRAN COMMAND message by the UE
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell. The UE shall: 1> For FDD: 2> if the UE has a pending "TGPS reconfiguration CFN" at the activation time received in the HANDOVER FROM UTRAN COMMAND the UE may: 3> abort the pending CM activation; 3> set the CM_PATTERN_ACTIVATION_ABORTED to TRUE. 2> otherwise: 3> set the CM_PATTERN_ACTIVATION_ABORTED to FALSE. 1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" GSM Standard to apply Inter RAT Message
GSM TS 04.18, version 8.5.0 or later, or 3GPP TS 44.018 3GPP TS 44.060, version 6.13.0 or later 3GPP TS 44.118 TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later
HANDOVER COMMAND
GERAN Iu cdma2000
PS HANDOVER COMMAND RADIO BEARER RECONFIGURATION
1> if the IE "System type" has the value "GSM" or "GERAN Iu": 2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used": 3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band". 2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used": 3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
3GPP
Release 6
210
3GPP TS 25.331 V6.23.0 (2009-09)
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message: 2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain": 3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message. 2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "PS domain": 3> connect upper layer entities corresponding to the indicated PS domain RAB to the radio resources indicated in the inter-RAT message. 3> if the "System type" is "GSM": 4> use the contents of the IE "GERAN system information" as the system information to begin access on the target GERAN cell. NOTE1: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1. NOTE2: In handover to GERAN Iu mode, the RAB information is included in the RADIO BEARER RECONFIGURATION message specified in [53]. NOTE3: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification. NOTE4: The UE may ignore the IE "NAS synchronisation indicator" if included in the HANDOVER FROM UTRAN COMMAND message; NOTE5: The UE behaviour is undefined if the IE "Re-establishment timer" in the IE "RAB info" indicates a timer different from the timer currently configured for this RAB. NOTE6: The IE "GERAN System Information" is constructed in the same way as in 2G to 2G PS Handover in [44].
8.3.7.4
Successful completion of the inter-RAT handover
Upon successfully completing the handover, UTRAN should: 1> release the radio connection; and 1> remove all context information for the concerned UE. Upon successfully completing the handover, the UE shall: 1> if inter-RAT handover to GERAN Iu mode is performed: 2> perform the actions on reception of the RADIO BEARER RECONFIGURATION message as specified in [53]. 1> if inter-RAT handover to GERAN Iu mode is performed and if there are any NAS messages for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 has not yet been confirmed by RLC; or 1> if inter-RAT handover to other RAT than GERAN Iu mode is performed and if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
3GPP
Release 6
211
3GPP TS 25.331 V6.23.0 (2009-09)
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology. 1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4. NOTE: The release of the UMTS radio resources is initiated from the target RAT.
8.3.7.5
UE fails to complete requested handover
If the UE does not succeed in establishing the connection to the target radio access technology, it shall: 1> revert back to the UTRA configuration; 1>For FDD: 2> if the CM_PATTERN_ACTIVATION_ABORTED flag is not set to TRUE: 3> establish the UTRA physical channel(s) (including HS-DSCH and E-DCH related channels) used at the time for reception of HANDOVER FROM UTRAN COMMAND; 3> perform the physical layer synchronisation procedure A as specified in [29] (FDD only); 3> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; and 3> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE or while the physical channel is not considered established. 1> if the UE does not succeed to establish the UTRA physical channel(s) or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is set to TRUE: 2> perform a cell update procedure according to subclause 8.3.1 with cause "Radio link failure"; 2> when the cell update procedure has completed successfully: 3> proceed as below. 1> transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "Inter-RAT handover failure" to "physical channel failure". 1> When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission: 2> the procedure ends.
8.3.7.6
Invalid HANDOVER FROM UTRAN COMMAND message
If the IE "Inter-RAT message" received within the HANDOVER FROM UTRAN COMMAND message does not include a valid inter RAT handover message in accordance with the protocol specifications for the target RAT, the UE shall perform procedure specific error handling as follows. The UE shall: 1> set the IE "failure cause" to the cause value "Inter-RAT protocol error"; 1> include the IE "Inter-RAT message" in accordance with the specifications applicable to the other RAT; 1> transmit a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC;
3GPP
Release 6
212
3GPP TS 25.331 V6.23.0 (2009-09)
1> when the transmission of the HANDOVER FROM UTRAN FAILURE message has been confirmed by RLC: 2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received; 2> and the procedure ends. If the HANDOVER FROM UTRAN COMMAND message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> set the IE "RRC transaction identifier" in the HANDOVER FROM UTRAN FAILURE message to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> transmit a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC; 1> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received; 2> and the procedure ends.
8.3.7.7
Reception of an HANDOVER FROM UTRAN FAILURE message by UTRAN
Upon receiving an HANDOVER FROM UTRAN FAILURE message, UTRAN may initiate the release the resources in the target radio access technology.
8.3.7.8
If: -
Unsupported configuration in HANDOVER FROM UTRAN COMMAND message
the UTRAN instructs the UE to perform a non-supported handover scenario; or the UTRAN instructs the UE to use a non-supported configuration; or the UE does not support PS Handover to GERAN, and the inter-RAT handover to other RAT than GERAN Iu mode is performed and the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message and this IE does not include any IE "RAB Info" with the IE "CN domain Identity" set to "CS domain"; or the HANDOVER FROM UTRAN COMMAND message includes the IE "RAB information List" and includes at least one IE "RAB Info" with the IE "CN domain Identity" set to "PS domain", and the IE "GERAN System Information" is not present:
the UE shall: 1> transmit a HANDOVER FROM UTRAN FAILURE message, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
3GPP
Release 6
213
3GPP TS 25.331 V6.23.0 (2009-09)
2> clear that entry; 2> set the IE "Inter-RAT handover failure" to "configuration unacceptable"; 2> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission: 3> resume normal operation as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received; 3> and the procedure ends.
8.3.7.8a
Reception of HANDOVER FROM UTRAN COMMAND message by UE in CELL_FACH
If the UE receives HANDOVER FROM UTRAN COMMAND while in CELL_FACH, the UE shall: 1> transmit a HANDOVER FROM UTRAN FAILURE message, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry; 2> set the IE "Inter-RAT handover failure" to "protocol error", include IE "Protocol error information"; and 2> set the value of IE "Protocol error cause" to "Message not compatible with receiver state"; 2> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission: 3> resume normal operation as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received; 3> and the procedure ends.
8.3.8
8.3.8.1
Inter-RAT cell reselection to UTRAN

General
The purpose of the inter-RAT cell reselection procedure to UTRAN is to transfer, under the control of the UE and to some extent the source radio access technology, a connection between the UE and another radio access technology (e.g. GSM/GPRS, but not UTRAN) to UTRAN.
8.3.8.2
Initiation
When the UE makes an inter-RAT cell reselection to UTRAN according to the criteria specified in [4], it shall initiate this procedure. The inter-RAT cell reselection made by the UE may use system information broadcast from the source radio access technology or UE dedicated information. If the NAS procedures associated with inter-system change specified in [5] require the establishment of an RRC connection, the UE shall: 1> set the variable ESTABLISHMENT_CAUSE to "Inter-RAT cell reselection"; NOTE: This value of ESTABLISHMENT_CAUSE has priority over the cause requested by upper layers.
1> initiate an RRC connection establishment procedure as specified in subclause 8.1.3; 1> after initiating an RRC connection establishment:
3GPP
Release 6
214
3GPP TS 25.331 V6.23.0 (2009-09)
2> release all resources specific to the other radio access technology. If the NAS procedures associated with inter-system change specified in [5] do not require the establishment of an RRC connection, the UE shall: 1> enter idle mode in the target cell without accessing the cell; and 1> release all resources specific to the other radio access technology.
8.3.8.2a
Initiation of inter-RAT cell reselection from GERAN Iu mode
When the UE performs an inter-RAT cell reselection from GERAN Iu mode Cell_Shared state, the UE shall: 1> initiate the cell update procedure as specified for the cell reselection case in CELL_FACH and CELL_PCH states, using the cause "cell reselection"and setting the G-RNTI in the IE "U-RNTI". When the UE performs an inter-RAT cell reselection from GERAN Iu mode GRA_PCH state, the UE shall: 1> compare the GRA identity which the MS had been assigned to in GERAN against the URA identities which are broadcast in the UTRAN cell. 1> If the assigned GRA identity is not present in the list of URA identities that are broadcast in the UTRAN cell: 2> initiate the URA update procedure as specified for the URA reselection case in URA_PCH state, using the cause "change of URA" and setting the G-RNTI in the IE "U-RNTI". The UE shall: 1> set the following variables equal to the corresponding variables in GERAN Iu mode: CIPHERING_STATUS ESTABLISHED_RABS ESTABLISHED_SIGNALLING_CONNECTIONS INTEGRITY_PROTECTION_INFO INTER_RAT_HANDOVER_INFO_TRANSFERRED LATEST_CONFIGURED_CN_DOMAIN START_THRESHOLD UE_CAPABILITY_TRANSFERRED. 1> set the new uplink and downlink HFN of RB2 to MSB20(MAX(uplink HFN of RB2, downlink HFN of RB2)). NOTE: MSB20() operation provides the HFN mapping from GERAN Iu mode to UTRAN. In GERAN Iu mode the length of HFN component of the COUNT-C of RB2 is longer than 20 bits. 1> initialise the variable TIMERS_AND_CONSTANTS to the default values and start to use those timer and constants values.
8.3.8.3
UE fails to complete an inter-RAT cell reselection
If the inter-RAT cell reselection fails before the UE has initiated the RRC connection establishment the UE may return back to the other radio access technology. If the RRC connection establishment fails, the UE shall enter idle mode.
8.3.8.3a
UE fails to complete an inter-RAT cell reselection from GERAN Iu mode
When the UE performs an inter-RAT cell reselection from GERAN Iu mode to UTRAN, and the cell reselection fails: 1> the UE may return back to the GERAN Iu mode state from which it initiated the inter-RAT cell reselection.
3GPP
Release 6
215
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.9
8.3.9.1
Inter-RAT cell reselection from UTRAN

General
The purpose of the inter-RAT cell reselection procedure from UTRAN is to transfer, under the control of the UE and to some extent the UTRAN, a connection between the UE and UTRAN to another radio access technology (e.g. GSM/GPRS).
8.3.9.2
Initiation
This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH. When the UE based on received system information makes a cell reselection to a radio access technology other than UTRAN, e.g. GSM/GPRS, according to the criteria specified in [4], the UE shall: 1> If the NAS procedures associated with inter-system change specified in [5] require the establishment of a connection: 2> initiate the establishment of a connection to the target radio access technology according to its specifications.
8.3.9.2a
Initiation of inter-RAT cell reselection to GERAN Iu mode
When the UE in CELL_PCH or CELL_FACH state performs an inter-RAT cell reselection to GERAN Iu mode, according to the criteria specified in [4], the UE shall: 1> initiate the cell update procedure according to 3GPP TS 44.118 [53], setting the U-RNTI in the IE "G-RNTI". When the UE in URA_PCH state performs an inter-RAT cell reselection to GERAN Iu mode, according to the criteria specified in [4], the UE shall: 1> compare the URA identity which the UE had been assigned to in UTRAN against the GRA identities which are broadcast in the GERAN cell; 1> If the assigned URA identity is not present in the list of GRA identities that are broadcast in the GERAN cell: 2> initiate the GRA update procedure as specified in 3GPP TS 44.118 [53], setting the U-RNTI in the IE "GRNTI".
8.3.9.3
Successful cell reselection
When the UE has succeeded in reselecting a cell in the target radio access technology, the UE shall:
1> release all UTRAN specific resources. UTRAN should: 1> release all UE dedicated resources upon indication that the UE has completed a connection establishment to the other radio access technology.
8.3.9.4
UE fails to complete an inter-RAT cell reselection
If the inter-RAT cell reselection fails, the UE shall: 1> resume the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection procedure.
3GPP
Release 6
216
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.10
8.3.10.1
Inter-RAT cell change order to UTRAN

General
The purpose of the inter-RAT cell change order to UTRAN procedure is to transfer, under the control of the source radio access technology, a connection between the UE and another radio access technology (e.g. GSM/GPRS) to UTRAN.
8.3.10.2
Initiation
The procedure is initiated when a radio access technology other than UTRAN, e.g. GSM/GPRS, using procedures specific for that RAT, orders the UE to change to a UTRAN cell. NOTE: The UE shall: 1> set the variable ESTABLISHMENT_CAUSE to "Inter-RAT cell change order"; NOTE: This value of ESTABLISHMENT_CAUSE has priority over the cause requested by upper layers. Within the message used to order the UE to change to a UTRAN cell, the source RAT should specify the identity of the target UTRAN cell as specified in the specifications for that RAT.
1> initiate an RRC connection establishment procedure as specified in subclause 8.1.3.
8.3.10.3
UE fails to complete an inter-RAT cell change order
If the inter-RAT cell reselection fails the UE shall return to the other radio access technology and proceed as specified in the appropriate specifications for that RAT. NOTE 3: The cell change was network ordered. Therefore, failure to change to the target cell should not cause the UE to move to UE- controlled cell selection.
8.3.11
Inter-RAT cell change order from UTRAN

UE UTRAN
CELL CHANGE ORDER FROM UTRAN
Figure 8.3.11-1: InterRAT cell change order from UTRAN

UE UTRAN
CELL CHANGE ORDER FROM UTRAN FAILURE
Figure 8.3.11-2: Inter-RAT cell change order from UTRAN, failure case
3GPP
Release 6
217
3GPP TS 25.331 V6.23.0 (2009-09)
8.3.11.1
General
The purpose of the inter-RAT cell change order procedure is to transfer, under the control of the network, a connection between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in CELL_DCH and CELL_FACH state. This procedure may be used when no RABs are established or when the established RABs are only from PS domain. This procedure may not be used when there is no PS signalling connection.
8.3.11.2
Initiation
The procedure is initiated when UTRAN orders a UE in CELL_DCH or CELL_FACH state, to make a cell change to a radio access technology other than UTRAN, e.g. GSM. To initiate the procedure, UTRAN sends a CELL CHANGE ORDER FROM UTRAN message.
8.3.11.3
Reception of an CELL CHANGE ORDER FROM UTRAN message by the UE
The UE shall be able to receive a CELL CHANGE ORDER FROM UTRAN message and perform a cell change order to another RAT, even if no prior UE measurements have been performed on the target cell. If the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity "PS domain", or if the variable ESTABLISHED_SIGNALLING_CONNECTIONS includes the CN domain identity "CS domain": 1> the UE shall act as if the message was never received. The UE shall: 1> For FDD: 2> if the UE has a pending "TGPS reconfiguration CFN" at the activation time received in the CELL CHANGE ORDER FROM UTRAN message the UE may: 3> abort the pending CM activation; 3> set the CM_PATTERN_ACTIVATION_ABORTED to TRUE. 2> otherwise: 3> set the CM_PATTERN_ACTIVATION_ABORTED to FALSE. 1> start timer T309; and 1> establish the connection to the other radio access technology, as specified within IE "Target cell description". This IE specifies the target cell identity, in accordance with the specifications for that other RAT. In case the target cell is a GSM/ GPRS cell, IE "Target cell description" may also include IE "NC mode", which specifies the cell selection mode to be applied in the target cell; and 1> if IE "NC mode" is not included in the CELL CHANGE ORDER FROM UTRAN: 2> retrieve it from the target cell as specified in [43]; 2> act upon IE "NC mode" as specified in [43]. 1> if the IE "RAB Information List" is included in the CELL CHANGE ORDER FROM UTRAN message: 2> ignore the contents of the IE "RAB Information List". NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification. In case of GSM/GPRS proceed according to the procedure Network control cell reselection procedure as specified in [44].
1> if the UE supports UTRAN to GERAN Network Assisted Cell Change, the IE "Geran System Information" is present and the UE is in CELL_DCH state:
3GPP
Release 6
218
3GPP TS 25.331 V6.23.0 (2009-09)
2> if according to [44] the IE "GERAN System Information" includes a correct and consistent set of SI or PSI messages: 3> use this information as the system information to begin access on the target GERAN cell. 2> otherwise: 3> ignore the IE "GERAN System Information" and continue the Cell Change Order procedure. NOTE: The IE "GERAN System Information" is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are encoded as such, whereas the SI messages exclude 2 octets of headers, see [44].
8.3.11.4
Successful completion of the cell change order
The UE regards the procedure as completed when it has received a successful response from the target RAT, e.g. in case of GSM when it received the response to a (PACKET) CHANNEL REQUEST in the new cell. Upon successful completion of the cell change order, the UE shall: 1> stop timer T309; 1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4. Upon indication of the UE having successfully completed the cell change order, UTRAN should: 1> release the radio connection; and 1> remove all context information for the concerned UE. NOTE: The release of the UMTS radio resources is initiated from another RAT.
8.3.11.5
If: -
Expiry of timer T309 or UE fails to complete requested cell change order
timer T309 expires prior to the successful establishment of a connection to the target RAT; or if the establishment of the connection to the other RAT failed due to other reasons e.g. (random) access failure, rejection due to lack of resources:
the UE shall: 1> if it received the CELL CHANGE ORDER FROM UTRAN message in state CELL_DCH: 2> For TDD or for FDD if the CM_PATTERN_ACTIVATION_ABORTED flag is not set to TRUE: 3> revert back to the UTRA configuration; 3> establish the UTRA physical channel(s) (including HS-DSCH and E-DCH related channels) used at the time for reception of CELL CHANGE ORDER FROM UTRAN. 2> For FDD: 3> perform the physical layer synchronisation procedure A as specified in [29]; 3> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; and 3> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE or while the physical channel is not considered established; 3> if the CM_PATTERN_ACTIVATION_ABORTED flag is set to TRUE or if the UE does not succeed in establishing the UTRA physical channel(s): 4> perform a cell update procedure according to subclause 8.3.1 with cause "Radio link failure";
3GPP
Release 6
219
3GPP TS 25.331 V6.23.0 (2009-09)
4> when the cell update procedure has completed successfully: 5> proceed as below. 3> transmit the CELL CHANGE ORDER FROM UTRAN FAILURE message setting the information elements as specified below: 4> include the IE "RRC transaction identifier"; and 4> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 4> clear that entry; 4> set the IE "Inter-RAT change failure" to "physical channel failure". 3> When the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layer for transmission, the procedure ends. 1> if the UE receives the CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state: 2> revert to the cell it was camped on at the reception of the CELL CHANGE ORDER FROM UTRAN message; 2> if the UE is unable to return to this cell: 3> select a suitable UTRA cell according to [4]; 3> initiate the cell update procedure according to subclause 8.3.1 using the cause "cell re-selection"; 3> when the cell update procedure completed successfully: 4> proceed as below. 2> transmit the CELL CHANGE ORDER FROM UTRAN FAILURE message setting the information elements as specified below: 3> include the IE "RRC transaction identifier"; and 3> set it to the value of "RRC transaction identifier" in the entry for the CELL CHANGE ORDER FROM UTRAN message in the table "Accepted transactions" in the variable TRANSACTIONS; and 3> clear that entry; 3> set the IE "Inter-RAT change failure" to "physical channel failure". 2> When the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layer for transmission: 3> the procedure ends.
8.3.11.6
Unsupported configuration in CELL CHANGE ORDER FROM UTRAN message
If the UTRAN instructs the UE to perform a non-supported cell change order scenario or to use a non-supported configuration, the UE shall: 1> transmit a CELL CHANGE ORDER FROM UTRAN FAILURE message, setting the information elements as specified below: 2> include the IE "RRC transaction identifier"; and 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and 2> clear that entry;
3GPP
Release 6
220
3GPP TS 25.331 V6.23.0 (2009-09)
2> set the IE "Inter-RAT change failure" to "configuration unacceptable"; 2> when the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layers for transmission: 3> resume normal operation as if the CELL CHANGE ORDER FROM UTRAN message has not been received; 3> and the procedure ends.
8.3.11.7
Invalid CELL CHANGE ORDER FROM UTRAN message
If the CELL CHANGE ORDER FROM UTRAN message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> set the IE "RRC transaction identifier" in the CELL CHANGE ORDER FROM UTRAN FAILURE message to the value of "RRC transaction identifier" in the entry for the CELL CHANGE ORDER FROM UTRAN message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> set the IE "Inter-RAT change failure" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> transmit a CELL CHANGE ORDER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC; 1> when the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layers for transmission: 2> resume normal operation as if the invalid CELL CHANGE ORDER FROM UTRAN message has not been received; 2> and the procedure ends.
8.4
8.4.0
Measurement procedures
Measurement related definitions
UTRAN may control a measurement in the UE either by broadcast of SYSTEM INFORMATION and/or by transmitting a MEASUREMENT CONTROL message. The following information is used to control the UE measurements and the measurement results reporting: 1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying or releasing the measurement and by the UE in the measurement report. 2. Measurement command: One out of three different measurement commands. Setup: Setup a new measurement. Modify: Modify a previously defined measurement, e.g. to change the reporting criteria. Release: Stop a measurement and clear all information in the UE that are related to that measurement.
3. Measurement type: One of the types listed below describing what the UE shall measure. Presence or absence of the following control information depends on the measurement type 4. Measurement objects: The objects on which the UE shall measure measurement quantities, and corresponding object information.
3GPP
Release 6
221
3GPP TS 25.331 V6.23.0 (2009-09)
5. Measurement quantity: The quantity the UE shall measure on the measurement object. This also includes the filtering of the measurements. 6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are mandatory to report for the specific event. 7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-triggered reporting. 8. Measurement Validity: Defines in which UE states the measurement is valid. 9. Measurement reporting mode: This specifies whether the UE shall transmit the measurement report using AM or UM RLC. 10. Additional measurement identities: A list of references to other measurements. When this measurement triggers a measurement report, the UE shall also include the reporting quantities for the measurements referenced by the additional measurement identities. All these measurement parameters depend on the measurement type and are described in more detail in clause 14. The different types of measurements are: Intra-frequency measurements: measurements on downlink physical channels at the same frequency as the active set. A measurement object corresponds to one cell. Detailed description is found in subclause 14.1. Inter-frequency measurements: measurements on downlink physical channels at frequencies that differ from the frequency of the active set and on downlink physical channels in the active set. A measurement object corresponds to one cell. Detailed description is found in subclause 14.2. Inter-RAT measurements: measurements on downlink physical channels belonging to another radio access technology than UTRAN, e.g. GSM. A measurement object corresponds to one cell. Detailed description is found in subclause 14.3. Traffic volume measurements: measurements on uplink traffic volume. A measurement object corresponds to one cell. Detailed description is found in subclause 14.4. Quality measurements: Measurements of downlink quality parameters, e.g. downlink transport block error rate. A measurement object corresponds to one transport channel in case of BLER. A measurement object corresponds to one timeslot in case of SIR (TDD only). Detailed description is found in subclause 14.5. UE-internal measurements: Measurements of UE transmission power and UE received signal level. Detailed description is found in subclause 14.6. UE positioning measurements: Measurements of UE position. Detailed description is found in subclause 14.7.
The UE shall support a number of measurements running in parallel as specified in [19] and [20]. The UE shall also support that each measurement is controlled and reported independently of every other measurement. Cells that the UE is monitoring are grouped in the UE into three mutually exclusive categories: 1. Cells, which belong to the active set. User information is sent from all these cells. In FDD, the cells in the active set are involved in soft handover. In TDD the active set always comprises one cell only. The UE shall only consider active set cells included in the variable CELL_INFO_LIST for measurement; i.e. active set cells not included in the CELL_INFO_LIST shall not be considered in any event evaluation and measurement reporting. 2. Cells, which are not included in the active set, but are included in the CELL_INFO_LIST belong to the monitored set. 3. Cells detected by the UE, which are neither in the CELL_INFO_LIST nor in the active set belong to the detected set. Reporting of measurements of the detected set is only applicable to intra-frequency measurements made by UEs in CELL_DCH state. If the IE "Cells for measurement" has been included in a MEASUREMENT CONTROL message, only monitored set cells explicitly indicated for a given intra-frequency (resp. inter-frequency, interRAT) measurement by the IE "Cells for measurement" shall be considered for measurement. If the IE "Cells for measurement" has not been included in a MEASUREMENT CONTROL message, all of the intra-frequency (resp. inter-frequency, inter RAT) cells stored in the
3GPP
Release 6
222
3GPP TS 25.331 V6.23.0 (2009-09)
variable CELL_INFO_LIST shall be considered for measurement. The IE "Cells for measurement" is not applicable to active set cells e.g. when the triggering condition refers to active set cells, the UE shall consider all active set cells in the CELL_INFO_LIST for measurement irrespective if these cells are explicitly indicated by the IE "Cells for measurement".
8.4.1
Measurement control
UE MEASUREMENT CONTROL UTRAN
Figure 8.4.1-1: Measurement Control, normal case

UE MEASUREMENT CONTROL UTRAN
MEASUREMENT CONTROL FAILURE
Figure 8.4.1-2: Measurement Control, failure case
8.4.1.1
General
The purpose of the measurement control procedure is to setup, modify or release a measurement in the UE. In subclause 8.4.1 and its subclauses references to System Information Block type 11 mean the merge of System Information Block Type 11 and System Information Block type 11bis, if scheduled on BCH and supported by the UE.
8.4.1.2
Initiation
The UTRAN may request a measurement by the UE to be setup, modified or released with a MEASUREMENT CONTROL message, which is transmitted on the downlink DCCH using AM RLC. The UTRAN should take the UE capabilities into account when a measurement is requested from the UE. When a new measurement is created, UTRAN should set the IE "Measurement identity" to a value, which is not used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type". In case of setting several "Measurement identity" within a same "Measurement type", the measurement object or the list of measurement objects can be set differently for each measurement with different "Measurement identity ". When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement identity", it is not needed for UTRAN to indicate the IEs other than modified IEs, and the UE continues to use the current values of the IEs that are not modified. UTRAN should not use "modify" to change the type of measurement stored in the variable MEASUREMENT_IDENTITY for a given measurement identity.
8.4.1.3
Reception of MEASUREMENT CONTROL by the UE
Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in subclause 8.6 unless otherwise specified below.
3GPP
Release 6
223
3GPP TS 25.331 V6.23.0 (2009-09)
The UE shall: 1> read the IE "Measurement command"; 1> if the IE "Measurement command" has the value "setup": 2> store this measurement in the variable MEASUREMENT_IDENTITY according to the IE "measurement identity", first releasing any previously stored measurement with that identity if that exists; 2> if the measurement type is quality, UE internal, intra-frequency, inter-frequency or inter-RAT: 3> if the UE is in CELL_FACH state: 4> the UE behaviour is not specified. 2> for measurement types "inter-RAT measurement" or "inter-frequency measurement" that require measurements on a frequency other than the actually used frequency: 3> if, according to its measurement capabilities, the UE requires compressed mode to perform that measurement type and after reception of this message a compressed mode pattern sequence with an appropriate measurement purpose is active according to the IE "Current TGPS Status Flag" in UE variable TGPS_IDENTITY; or 3> if, according to its measurement capabilities, the UE does not require compressed mode to perform the measurements on at least one supported band of that measurement type: 4> if the measurement is valid in the current RRC state of the UE: 5> begin measurements according to the stored control information for this measurement identity. NOTE: The UE is not required to perform measurements on cells for which it needs compressed mode but a suitable compressed mode pattern is not activated.
2> for measurement type "inter-frequency measurement" that requires measurements only on the same frequency as the actually used frequency: 3> if the measurement is valid in the current RRC state of the UE: 4> begin measurements according to the stored control information for this measurement identity. 2> for measurement type "UE positioning measurement": 3> if the UE is in CELL_FACH state: 4> if IE "Positioning Method" is set to "OTDOA": 5> if IE "Method Type" is set to "UE assisted": 6> if IE "UE positioning OTDOA assistance data for UE assisted" is not included: 7> if System Information Block type 15.4 is broadcast: 8> read System Information Block type 15.4. 7> act as specified in subclause 8.6.7.19.2. 5> if IE "Method Type" is set to "UE based": 6> if IE "UE positioning OTDOA assistance data for UE based" is not included: 7> if System Information Block type 15.5 is broadcast: 8> read System Information Block type 15.5. 7> act as specified in subclause 8.6.7.19.2a. 2> for any other measurement type:
3GPP
Release 6
224
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the measurement is valid in the current RRC state of the UE: 4> begin measurements according to the stored control information for this measurement identity. 1> if the IE "Measurement command" has the value "modify": 2> for all IEs present in the MEASUREMENT CONTROL message: 3> if a measurement was stored in the variable MEASUREMENT_IDENTITY associated to the identity by the IE "measurement identity": 4> if the measurement type is quality, UE internal, intra-frequency, inter-frequency or inter-RAT: 5> if the UE is in CELL_FACH state: 6> the UE behaviour is not specified. 4> if measurement type is set to "intra-frequency measurement", for any of the optional IEs "Intrafrequency measurement objects list", "Intra-frequency measurement quantity", "Intra-frequency reporting quantity", "Measurement Validity", "report criteria" and "parameters required for each event" (given "report criteria" is set to "intra-frequency measurement reporting criteria") that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "inter-frequency measurement", for any of the optional IEs "Interfrequency measurement quantity", "Inter-frequency reporting quantity", "Measurement Validity", "Inter-frequency set update" and "parameters required for each event" (given "report criteria" is set to either "inter-frequency measurement reporting criteria" or "intra-frequency measurement reporting criteria") that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "inter-RAT measurement", for any of the optional IEs "Inter-RAT measurement objects list", "Inter-RAT measurement quantity", and "Inter-RAT reporting quantity" that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "UE positioning measurement" and the IE "UE positioning OTDOA assistance data" is present, for any of the optional IEs "UE positioning OTDOA neighbour cell info for UE-assisted", "UE positioning OTDOA reference cell info for UE-assisted", "UE positioning OTDOA reference cell info for UE-based", "UE positioning OTDOA neighbour cell info for UEbased" and "UE positioning" that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "UE positioning measurement" and the IE "UE positioning GPS assistance data" is present, for any of the optional IEs "UE positioning GPS reference time", "UE positioning GPS reference UE position", "UE positioning GPS DGPS corrections", "UE positioning GPS ionospheric model", "UE positioning GPS UTC model", "UE positioning GPS acquisition assistance", "UE positioning GPS real-time integrity" that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "traffic volume measurement", for any of the optional IEs "Traffic volume measurement Object", "Traffic volume measurement quantity", "Traffic volume reporting quantity", and"Measurement Validity" that are present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "quality measurement", for the optional IE "Quality reporting quantity" if it is present in the MEASUREMENT CONTROL message: 4> if measurement type is set to "UE internal measurement", for any of the optional IEs "UE internal measurement quantity", and "UE internal reporting quantity" that are present in the MEASUREMENT CONTROL message: 5> replace all instances of the IEs listed above (and all their children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IEs received in the MEASUREMENT CONTROL message; 5> leave all other stored information elements unchanged in the variable MEASUREMENT_IDENTITY. 3> otherwise:
3GPP
Release 6
225
3GPP TS 25.331 V6.23.0 (2009-09)
4> set the variable CONFIGURATION_INCOMPLETE to TRUE. 2> if measurement type is set to "inter-frequency measurement": 3> if "report criteria" is set to "intra-frequency measurement reporting criteria" and "reporting criteria" in "inter-frequency measurement quantity" is set to "intra-frequency reporting criteria": 4> leave the currently stored "inter-frequency measurement reporting criteria" within "report criteria" and "inter-frequency reporting criteria" within "inter-frequency measurement quantity" unchanged, and continue to act on the information stored in these variables. NOTE: If the UTRAN wants to modify the inter-frequency cell info list for an inter-frequency measurement configured with event based reporting without repeating any IEs related to the configured events, one possibility is to set the IE "report criteria" to "intra-frequency measurement reporting criteria", not include the IE "parameters required for each event", and set the IE "reporting criteria" in the IE "inter-frequency measurement quantity" to "intra-frequency reporting criteria".
2> for measurement types "inter-frequency measurement" that require measurements on a frequency other than the actually used frequency, or that require measurements on another RAT: 3> if, according to its measurement capabilities, the UE requires compressed mode to perform that measurement type and after reception of this message a compressed mode pattern sequence with an appropriate measurement purpose is active according to the IE "Current TGPS Status Flag" in UE variable TGPS_IDENTITY; or 3> if, according to its measurement capabilities, the UE does not require compressed mode, on at least one supported band of that measurement type, to perform the measurements: 4> resume the measurements according to the new stored measurement control information. 2> for measurement type "inter-frequency measurement" that requires measurements only on the same frequency as the actually used frequency: 3> if the measurement is valid in the current RRC state of the UE: 4> resume measurements according to the new stored control information for this measurement identity. 2> for any other measurement type: 3> resume the measurements according to the new stored measurement control information. 2> for measurement type "inter-RAT measurement": 3> if "report criteria" is set to "inter-RAT measurement reporting criteria": 4> if the value of "report criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is not "inter-RAT measurement reporting criteria"; or 4> if the value of "report criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is "inter-RAT measurement reporting criteria" and if the IE "Parameters required for each event" is present: 5> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "reporting criteria" received in the MEASUREMENT CONTROL message. 3> if "report criteria" is not set to "inter-RAT measurement reporting criteria": 4> replace the IE "reporting criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "reporting criteria" received in the MEASUREMENT CONTROL message. 2> for measurement type "UE positioning measurement": 3> if "reporting criteria" is set to "UE positioning reporting criteria":
3GPP
Release 6
226
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the value of "reporting criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is not "UE positioning reporting criteria", or; 4> if the value of "reporting criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is "UE positioning reporting criteria" and if the IE "Parameters required for each event" is present: 5> replace the IE "reporting criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message. 3> if "reporting criteria" is not set to "UE positioning reporting criteria": 4> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message. 2> for measurement type "traffic volume measurement": 3> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message. 2> for measurement type "quality measurement": 3> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message; 3> if "report criteria" is set to "quality measurement reporting criteria": 4> if the value of "BLER reporting" in any instance of the IE "Quality reporting quantity" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message is set to TRUE: 5> the UE behaviour is unspecified. 2> for measurement type "UE internal measurement": 3> if "report criteria" is set to "UE internal measurement reporting criteria": 4> if the value of "report criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is not "UE internal measurement reporting criteria"; or 4> if the value of "report criteria" stored in the variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" is "UE internal measurement reporting criteria" and if the IE "Parameters sent for each UE internal measurement event" is present: 5> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message. 3> if "report criteria" is not set to "UE internal measurement reporting criteria": 4> replace the IE "report criteria" (and all its children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IE "report criteria" received in the MEASUREMENT CONTROL message. 1> if the IE "measurement command" has the value "release": 2> terminate the measurement associated with the identity given in the IE "measurement identity"; 2> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY.
3GPP
Release 6
227
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "DPCH Compressed Mode Status Info" is present: 2> if, as the result of this message, UE will have more than one transmission gap pattern sequence with the same measurement purpose active (according to IEs "TGMP" and "Current TGPS Status Flag" in variable TGPS_IDENTITY): 3> set the variable CONFIGURATION_INCOMPLETE to TRUE. 2> if there is any pending "TGPS reconfiguration CFN" or any pending "TGCFN": 3> the UE behaviour is unspecified. 2> if there is a pending "activation time" for a reconfiguration procedure that included the IE "DPCH Compressed mode info": 3> the UE behaviour is unspecified. 2> if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag") in the variable TGPS_IDENTITY): 3> if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence: 4> deactivate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN" received in the message; 4> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "inactive" at the frame indicated by IE "TGPS reconfiguration CFN" received in the message. 3> if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence: 4> deactivate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN" received in the message. NOTE1: The temporary deactivation of pattern sequences for which the status flag is set to "activate" can be used by the network to align the timing of already active patterns with newly activated patterns. NOTE2: The deactivation of pattern sequences only occurs as a result of RRC messages received by the UE, i.e. the UE does not set the "Current TGPS Status Flag" to "inactive" after the final gap of a finite length pattern sequence. 2> after the time indicated by IE "TGPS reconfiguration CFN" has elapsed: 3> activate the pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" in this message is set to "activate" at the time indicated by IE "TGCFN"; and 3> set the corresponding "Current TGPS status flag" for this pattern sequence in the variable TGPS_IDENTITY to "active"; and 3> begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence measurement purpose of each activated pattern sequence; 3> if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal: 4> start the concerned pattern sequence immediately at that CFN. 2> not alter pattern sequences stored in variable TGPS_IDENTITY, if the pattern sequence is not identitifed in IE "TGPSI" in the received message. 1> if the UE in CELL_FACH state receives a MEASUREMENT CONTROL message, which indicates the same measurement identity as that stored in the variable MEASUREMENT_IDENTITY: 2> update the stored information with the traffic volume measurement control information in variable MEASUREMENT_IDENTITY; and 2> refrain from updating the traffic volume measurement control information associated with this measurement identity in the variable MEASUREMENT_IDENTITY with the information received in System Information
3GPP
Release 6
228
3GPP TS 25.331 V6.23.0 (2009-09)
Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11) until this measurement is explicitly released with another MEASUREMENT CONTROL message. 1> if the IE "Read SFN indicator" included in the IE "Cell info" of an inter-frequency cell is set to TRUE and the variable UE_CAPABILITY_TRANSFERRED has the DL "Measurement capability" for "FDD measurements" set to TRUE (the UE requires DL compressed mode in order to perform measurements on FDD): 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> clear the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS. The UE may: 1> if the IE "Measurement command" has the value "setup": 2> for measurement type "UE positioning measurement": 3> if the UE is CELL_FACH state: 4> if IE "Positioning Method" is set to "GPS": 5> if IE "UE positioning GPS assistance data" is not included and variable UE_POSITIONING_GPS_DATA is empty: 6> if System Information Block types 15, 15.1, 15.2 and 15.3 are broadcast: 7> read System Information Block types 15, 15.1, 15.2 and 15.3. 6> act as specified in subclause 8.6.7.19.3. 1> and the procedure ends.
8.4.1.4
Unsupported measurement in the UE
If UTRAN instructs the UE to perform a measurement that is not supported by the UE, or would cause the maximum number of reporting criteria supported by the UE [19] to be exceeded, the UE shall: 1> retain the measurement configuration that was valid before the MEASUREMENT CONTROL message was received; 1> set the IE "RRC transaction identifier" in the MEASUREMENT CONTROL FAILURE message to the value of "RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS; and 1> clear that entry. 1> set the cause value in IE "failure cause" to "unsupported measurement"; 1> submit the MEASUREMENT CONTROL FAILURE message to lower layers for transmission on the DCCH using AM RLC; 1> continue with any ongoing processes and procedures as if the invalid MEASUREMENT CONTROL message has not been received; 1> and the procedure ends.
8.4.1.4a
Configuration Incomplete
If the variable CONFIGURATION_INCOMPLETE is set to TRUE, the UE shall: 1> retain the measurement configuration that was valid before the MEASUREMENT CONTROL message was received;
3GPP
Release 6
229
3GPP TS 25.331 V6.23.0 (2009-09)
1> set the IE "RRC transaction identifier" in the MEASUREMENT CONTROL FAILURE message to the value of "RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS and clear that entry; 1> clear the variable CONFIGURATION_INCOMPLETE; 1> set the cause value in IE "failure cause" to "Configuration incomplete"; 1> submit the MEASUREMENT CONTROL FAILURE message to lower layers for transmission on the DCCH using AM RLC; 1> continue with any ongoing processes and procedures as if the invalid MEASUREMENT CONTROL message has not been received; 1> and the procedure ends.
8.4.1.5
Invalid MEASUREMENT CONTROL message
If the MEASUREMENT CONTROL message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> set the IE "RRC transaction identifier" in the MEASUREMENT CONTROL FAILURE message to the value of "RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry. 1> set the IE "failure cause" to the cause value "protocol error"; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION; 1> submit the MEASUREMENT CONTROL FAILURE message to lower layers for transmission on the DCCH using AM RLC; 1> continue with any ongoing processes and procedures as if the invalid MEASUREMENT CONTROL message has not been received; 1> and the procedure ends.
8.4.1.6
Measurements after transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state
The UE shall apply the following rules for different measurement types after transiting from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state:
8.4.1.6.1
Intra-frequency measurement
Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall: 1> stop intra-frequency type measurement reporting; 1> if the transition is due to a reconfiguration message which included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects a cell other than that indicated by this IE on the current frequency (in case the IE "Frequency info" is not received) or other than that indicated by this IE on the frequency indicated by the IE "Frequency info" (when the IE "Frequency info" is included); or 1> if the transition is due to a reconfiguration message which does not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD); or 1> if the transition is not due to a reconfiguration message: 2> delete the measurements of type intra-frequency associated with the variable MEASUREMENT_IDENTITY.
3GPP
Release 6
230
3GPP TS 25.331 V6.23.0 (2009-09)
1> begin monitoring cells listed in the IE "intra-frequency cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11).
8.4.1.6.2
Inter-frequency measurement
Upon transition from CELL_DCH to CELL_FACH/ CELL_PCH/URA_PCH state, the UE shall: 1> stop the inter-frequency type measurement reporting assigned in a MEASUREMENT CONTROL message; 1> if the transition is due to a reconfiguration message which included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects a cell other than that indicated by this IE on the current frequency (in case the IE "Frequency info" is not received) or other than that indicated by this IE on the frequency indicated by the IE "Frequency info" (when the IE "Frequency info" is included); or 1> if the transition is due to a reconfiguration message which does not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD); or 1> if the transition is not due to a reconfiguration message: 2> delete the measurements of type inter-frequency associated with the variable MEASUREMENT_IDENTITY and delete the corresponding compressed mode pattern stored in the variable TGPS_IDENTITY. 1> for remaining compressed mode patterns, set the IE "TGPS Status Flag" to "deactivate" and the IE "Current TGPS Status Flag" to "inactive" in the variable TGPS_IDENTITY. 1> begin monitoring cells listed in the IE "inter-frequency cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11); 1> in CELL_FACH state: 2> perform measurements on other frequencies according to the IE "FACH measurement occasion info".
8.4.1.6.3
Inter-RAT measurement
Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall: 1> stop the inter-RAT type measurement reporting assigned in a MEASUREMENT CONTROL message; 1> delete the measurements of type inter-RAT associated with the variable MEASUREMENT_IDENTITY and delete the corresponding compressed mode pattern stored in the variable TGPS_IDENTITY; 1> begin monitoring cells listed in the IE "inter-RAT cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11); 1> in CELL_FACH state: 2> perform measurements on other systems according to the IE "FACH measurement occasion info".
8.4.1.6.4
Quality measurement
Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall: 1> stop quality type measurement reporting; 1> delete all measurement control information of measurement type "quality" stored in the variable MEASUREMENT_IDENTITY.
8.4.1.6.5
UE internal measurement
Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall: 1> stop UE internal measurement type measurement reporting; 1> delete all measurement control information of measurement type "UE internal" stored in the variable MEASUREMENT_IDENTITY.
3GPP
Release 6
231
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.6.6
Traffic volume measurement
Upon transition from CELL_DCH to CELL_FACH or CELL_PCH or URA_PCH state, the UE shall: 1> retrieve each set of measurement control information of measurement type "traffic volume" stored in the variable MEASUREMENT_IDENTITY; and 2> if the optional IE "measurement validity" for this measurement has not been included: 3> delete the measurement associated with the variable MEASUREMENT_IDENTITY. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "CELL_DCH": 3> stop measurement reporting; 3> store the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_DCH state. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states" or "all states except CELL_DCH", and if the state transition is from CELL_DCH to CELL_PCH or URA_PCH state: 3> stop measurement reporting; 3> store the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_FACH state. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states", and if the state transition is from CELL_DCH to CELL_FACH state: 3> continue measurement reporting. 2> if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value "all states except CELL_DCH", and if the state transition is from CELL_DCH to CELL_FACH state: 3> resume this measurement and associated reporting. 1> if no traffic volume type measurement has been assigned to the UE with a MEASUREMENT CONTROL message that is valid in CELL_FACH or CELL_PCH or URA_PCH states (stored in the variable MEASUREMENT_IDENTITY), which has the same identity as the one indicated in the IE "Traffic volume measurement system information": 2> store the measurement control information from the IE "Traffic volume measurement system information" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11) in the variable MEASUREMENT_IDENTITY; 2> perform traffic volume measurement reporting according to the assigned information, when in CELL_FACH state.
8.4.1.6.7
UE positioning measurement
Upon transition from CELL_DCH to CELL_FACH and upon transition from CELL_DCH to CELL_PCH or URA_PCH for UE assisted GPS measurements, the UE shall: 1> retrieve each set of measurement control information of measurement type "UE positioning" stored in the variable MEASUREMENT_IDENTITY; and 2> if the optional IE "measurement validity" for this measurement has not been included: 3> delete the measurement associated with the variable MEASUREMENT_IDENTITY. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "CELL_DCH": 3> stop measurement reporting;
3GPP
Release 6
232
3GPP TS 25.331 V6.23.0 (2009-09)
3> store the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_DCH state. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states": 3> upon transition from CELL_DCH to CELL_PCH or URA_PCH: 4> if the choice in the IE "Reporting Criteria" included the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "UE positioning reporting criteria" and the value of the IE "Measurement interval" included in this IE is less than 64 seconds: 5>use a value of 64 seconds for the measurement interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. 4> if the choice in the IE "Reporting Criteria" included the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "Periodical Reporting Criteria" and the value of the IE "Reporting interval" included in this IE is less than 64 seconds: 5> use a value of 64 seconds for the reporting interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. 3> continue measurement reporting according to its UE positioning measurement reporting capability. 2> if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value "all states except CELL_DCH": 3> upon transition from CELL_DCH to CELL_PCH or URA_PCH: 4> if the choice in the IE "Reporting Criteria" included the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "UE positioning reporting criteria" and the value of the IE "Measurement interval " included in this IE is less than 64 seconds: 5> use a value of 64 seconds for the measurement interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. 4> if the choice in the IE "Reporting Criteria" included the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "Periodical Reporting Criteria" and the value of the IE "Reporting interval" included in this IE is less than 64 seconds: 5> use a value of 64 seconds for the reporting interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. 3> resume this measurement and associated reporting according to its UE Positioning measurement reporting capability. 1> if the transition is due to a reconfiguration message which included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects a cell other than that indicated by this IE; or 1> if the transition is due to a reconfiguration message which does not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD); or 1> if the transition is due to a reconfiguration message which included the IE "Frequency info", and the UE selects a cell on another frequency than that indicated by this IE; or 1> if the transition is due to a reconfiguration message which does not include the IE "Frequency info", and the UE can not find a cell on the current frequency, but it selects a cell on another frequency; or 1> if the transition is not due to a reconfiguration message: 2> delete the assistance data included in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED and UE_POSITIONING_OTDOA_DATA_UE_ASSISTED. 1> if the IE "Positioning Methods" stored in the variable MEASUREMENT_IDENTITY is set to "OTDOA" or "OTDOA or GPS":
3GPP
Release 6
233
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the IE "Method type" stored in the variable MEASUREMENT_IDENTITY is set to "UE-based" or "UE assisted preferred but UE-based allowed" or "UE-based preferred but UE-assisted allowed": 3> begin monitoring assistance data received in System Information Block type 15.4 and System Information Block type 15.5 according to subclause 8.1.1.6.15. 2> if the IE "Method type" stored in the variable MEASUREMENT_IDENTITY is set to "UE-assisted": 3> begin monitoring assistance data received in System Information Block type 15.4 according to subclause 8.1.1.6.15. 1> if the UE is in CELL_FACH state: 2> if the IE "UE positioning OTDOA neighbour cell list for UE assisted" stored in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED or UE_POSITIONING_OTDOA_DATA_UE_BASED contains neighbour cells on other frequencies than the current frequency: 3> perform measurements on other frequencies according to the IE "FACH measurement occasion info". The UE may: 1> if the IE "Positioning Methods" stored in the variable MEASUREMENT_IDENTITY is set to "GPS" or "OTDOA or GPS": 2> begin monitoring assistance data received in System Information Block type 15 and/or System Information Block type 15.1 and/or System Information Block type 15.2 and/or System Information Block type 15.3 according to subclause 8.1.1.6.15. NOTE: In the case that the measurement or reporting intervals are modified to 64 seconds during a transition to CELL_PCH/URA_PCH as described above, the UE retains the previously used values of "Measurement interval" and "Reporting interval" for use after transition out of CELL_PCH/URA_PCH.
8.4.1.6a
Actions in CELL_FACH/CELL_PCH/URA/PCH state upon cell re-selection
Upon cell reselection while in CELL_FACH/CELL_PCH/URA/PCH state and the cell reselection has occurred after the measurement control information was stored, the UE shall: 1> delete all measurements of type intra-frequency, inter-frequency, and inter-RAT associated with the variable MEASUREMENT_IDENTITY; 1> delete all compressed mode patterns associated with inter-frequency and inter-RAT measurements stored in the variable TGPS_IDENTITY; 1> delete the traffic volume measurements that have not been set up or modified through a MEASUREMENT CONTROL message.
8.4.1.7
Measurements after transition from CELL_FACH to CELL_DCH state
The UE shall apply the following rules for different measurement types after transiting from CELL_FACH to CELL_DCH state:
8.4.1.7.1
Upon transition from CELL_FACH to CELL_DCH state: 1> if intra-frequency measurements applicable to CELL_DCH state are stored in the variable MEASUREMENT_IDENTITY: 2> if the cell in which the UE transited from CELL_FACH state is included in the active set for the CELL_DCH state, the UE shall: 3> resume the measurement reporting. 2> otherwise, the UE shall:
3GPP
Release 6
234
3GPP TS 25.331 V6.23.0 (2009-09)
3> not resume the measurement reporting. The measurement shall be restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.
8.4.1.7.2
Upon transition from CELL_FACH to CELL_DCH state: 1> if inter-frequency measurements applicable to CELL_DCH state are stored in the variable MEASUREMENT_IDENTITY: 2> if the cell in which the UE transited from CELL_FACH state is included in the active set for the CELL_DCH state, the UE shall: 3> resume the measurement reporting. 2> otherwise, the UE shall: 3> not resume the measurement reporting. The measurement shall be restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.
8.4.1.7.3
Upon transition from CELL_FACH to CELL_DCH state, the UE shall: 1> stop monitoring the list of cells assigned in the IE "inter-RAT cell info list" in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11).
8.4.1.7.4
Upon transition from CELL_FACH to CELL_DCH state, the UE shall: 1> retrieve each set of measurement control information of measurement type "traffic volume" stored in the variable MEASUREMENT_IDENTITY; 2> if the optional IE "measurement validity" for this measurement has not been included: 3> delete the measurement associated with the variable MEASUREMENT_IDENTITY. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states except CELL_DCH": 3> stop measurement reporting; and 3> save the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_FACH/CELL_PCH/URA_PCH state. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states": 3> continue measurement reporting. 2> if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value "CELL_DCH": 3> resume this measurement and associated reporting. 1> if no traffic volume type measurement has been assigned to the UE with a MEASUREMENT CONTROL message that is valid in CELL_DCH and has the same identity as the one indicated in the IE "Traffic volume measurement system information": 2> store the measurement control information from the IE "Traffic volume measurement system information" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11) in the variable MEASUREMENT_IDENTITY; 2> begin traffic volume measurement reporting according to the assigned information.
3GPP
Release 6
235
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.7.5
Upon transition from CELL_FACH to CELL_DCH state, the UE shall: 1> retrieve each set of measurement control information of measurement type "UE positioning" stored in the variable MEASUREMENT_IDENTITY; and 2> if the optional IE "Measurement validity" for this measurement has not been included: 3> delete the measurement associated with the variable MEASUREMENT_IDENTITY. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states except CELL_DCH": 3> stop measurement reporting; and 3> save the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_FACH/CELL_PCH/URA_PCH state. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states": 3> continue measurement reporting. 2> if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value "CELL_DCH": 3> resume this measurement and associated reporting. 1> stop monitoring assistance data received in System Information Block type 15 or System Information Block type 15.1 or System Information Block type 15.2 or System Information Block type 15.3 or System Information Block type 15.4 or System Information Block 15.5.
8.4.1.8
Measurements after transition from idle mode to CELL_DCH state
The UE shall obey the following rules for different measurement types after transiting from idle mode to CELL_DCH state:
8.4.1.8.1
Upon transition from idle mode to CELL_DCH state: 1> if intra-frequency measurements applicable to CELL_DCH state are stored in the variable MEASUREMENT_IDENTITY: 2> if the cell in which the UE transited from idle mode is included in the active set for the CELL_DCH state, the UE shall: 3> begin measurement reporting. 2> otherwise, the UE shall: 3> not begin the measurement reporting. The measurement shall be restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.
8.4.1.8.2
Upon transition from idle mode to CELL_DCH state, the UE shall: 1> stop monitoring the list of cells assigned in the IE "inter-frequency cell info list" in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11).
8.4.1.8.3
Upon transition from idle mode to CELL_DCH state, the UE shall:
3GPP
Release 6
236
3GPP TS 25.331 V6.23.0 (2009-09)
1> stop monitoring the list of cells assigned in the IE "inter-RAT cell info list" in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11).
8.4.1.8.4
Upon transition from idle mode to CELL_DCH state, the UE shall: 1> begin a traffic volume type measurement, assigned in System Information Block type 11 (or System Information Block type 12, according to subclause 8.1.1.6.11).
8.4.1.8.5
Upon transition from idle mode to CELL_DCH state, the UE shall: 1> stop monitoring assistance data received in System Information Block type 15 or System Information Block type 15.1 or System Information Block type 15.2 or System Information Block type 15.3 or System Information Block type 15.4 or System Information Block type 15.5.
8.4.1.9
Measurements after transition from idle mode to CELL_FACH state
The UE shall obey the follow rules for different measurement types after transiting from idle mode to CELL_FACH state:
8.4.1.9.1
Upon transition from idle mode to CELL_FACH state, the UE shall: 1> begin or continue monitoring cells listed in the IE "intra-frequency cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11).
8.4.1.9.2
Upon transition from idle mode to CELL_FACH state, the UE shall: 1> begin or continue monitoring cells listed in the IE "inter-frequency cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11); 1> perform measurements on other frequencies according to the IE "FACH measurement occasion info".
8.4.1.9.3
Upon transition from idle mode to CELL_FACH state, the UE shall: 1> begin or continue monitoring cells listed in the IE "inter-RAT cell info list" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11); 1> perform measurements on other systems according to the IE "FACH measurement occasion info".
8.4.1.9.4
Upon transition from idle mode to CELL_FACH state, the UE shall: 1> store the measurement control information from the IE "Traffic volume measurement system information" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11) in the variable MEASUREMENT_IDENTITY; 1> begin traffic volume measurement reporting according to the assigned information.
8.4.1.9.5
Upon transition from idle mode to CELL_FACH state, the UE may:
3GPP
Release 6
237
3GPP TS 25.331 V6.23.0 (2009-09)
1> begin or continue monitoring assistance data received in System Information Block type 15 or System Information Block type 15.1 or System Information Block type 15.2 or System Information Block type 15.3 or System Information Block type 15.4 or System Information Block type 15.5 according to subclause 8.1.1.6.15; 1> if the IE "UE positioning OTDOA neighbour cell list for UE assisted" stored in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED; or 1> if the IE "UE positioning OTDOA neighbour cell list for UE based" stored in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED contains neighbour cells on other frequencies than the current frequency: 2> perform measurements on other frequencies according to the IE "FACH measurement occasion info".
8.4.1.9a
Measurements after transition from connected mode to idle mode
Upon transition from connected mode to idle mode the UE shall: 1> stop measurement reporting for all measurements stored in the variable MEASUREMENT_IDENTITY; 1> clear the variable MEASUREMENT_IDENTITY; 1> apply the following rules for different measurement types.
8.4.1.9a.1 Intra-frequency measurement

Upon transition from connected mode to idle mode, the UE shall: 1> stop monitoring intra-frequency cells listed in the IE "intra-frequency cell info list" received in System Information Block type 12 (if System Information Block type 12 is transmitted in the cell, according to subclause 8.1.1.6.11); 1> begin monitoring intra-frequency cells listed in the IE "intra-frequency cell info list" received in System Information Block type 11.
8.4.1.9a.2
Upon transition from connected mode to idle mode, the UE shall: 1> stop monitoring inter-frequency cells listed in the IE "inter-frequency cell info list" received in System Information Block type 12 (if System Information Block type 12 is transmitted in the cell, according to subclause 8.1.1.6.11); 1> begin monitoring inter-frequency cells listed in the IE "inter-frequency cell info list" received in System Information Block type 11.
8.4.1.9a.3
Upon transition from connected mode to idle mode, the UE shall: 1> stop monitoring inter-RAT cells listed in the IE "inter-RAT cell info list" received in System Information Block type 12 (if System Information Block type 12 is transmitted in the cell, according to 8.1.1.6.11); 1> begin monitoring inter-RAT cells listed in the IE "inter-RAT cell info list" received in System Information Block type 11.
8.4.1.9a.4
Upon transition from connected mode to idle mode, the UE may: 1> begin or continue monitoring assistance data received in System Information Block type 15 or System Information Block type 15.1 or System Information Block type 15.2 or System Information Block type 15.3 or System Information Block type 15.4 or System Information Block type 15.5.
3GPP
Release 6
238
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.9b
Measurements after transition from CELL_FACH to CELL_PCH/URA_PCH
8.4.1.9b.1 Traffic volume measurement

Upon transition from CELL_FACH to CELL_PCH or URA_PCH, the UE shall: 1> stop any ongoing traffic volume measurement, and associated traffic volume measurement reporting. 1> store the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the next transition to CELL_FACH state; 1> if no traffic volume type measurement has been assigned to the UE with a MEASUREMENT CONTROL message that is valid in CELL_FACH or CELL_PCH or URA_PCH states (stored in the variable MEASUREMENT_IDENTITY), which has the same identity as the one indicated in the IE "Traffic volume measurement system information": 2> store the measurement control information from the IE "Traffic volume measurement system information" received in System Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11) in the variable MEASUREMENT_IDENTITY.
8.4.1.9b.2 UE positioning measurement

Upon transition from CELL_FACH to CELL_PCH or URA_PCH, the UE shall: 1> retrieve each set of measurement control information of measurement type "UE positioning" stored in the variable MEASUREMENT_IDENTITY; and 2> if the optional IE "measurement validity" for this measurement has not been included: 3> delete the measurement associated with the variable MEASUREMENT_IDENTITY. 2> if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been assigned to value "all states" or "all states except CELL_DCH": 3> if the choice in the IE "Reporting Criteria" included in the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "UE positioning reporting criteria" and the value of the IE "Measurement interval" included in this IE is less than 64 seconds: 4> use a value of 64 seconds for the measurement interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. 3> if the choice in the IE "Reporting Criteria" included in the IE "UE Positioning measurement" stored in the variable MEASUREMENT_IDENTITY is set to "Periodical Reporting Criteria" and the value of the IE "Reporting interval" included in this IE is less than 64 seconds: 4> use a value of 64 seconds for the reporting interval associated with this measurement while the UE remains in CELL_PCH/URA_PCH. NOTE: In the case that the measurement or reporting intervals are modified to 64 seconds as described above, the UE retains the previously used values of "Measurement interval" and "Reporting interval" for use after transition out of CELL_PCH/URA_PCH.
8.4.1.9c
Measurements after transition from CELL_PCH/URA_PCH to CELL_FACH
8.4.1.9c.1 Traffic volume measurement

Upon transition from CELL_PCH or URA_PCH to CELL_FACH, the UE shall resume any traffic volume measurement stored in the variable MEASUREMENT_IDENTITY with measurement validity "all states" or "all states except CELL_DCH", and start the associated traffic volume measurement reporting.
3GPP
Release 6
239
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.9c.2 UE positioning measurement

Upon transition from CELL_PCH or URA_PCH to CELL_FACH, the UE shall continue any UE positioning measurement stored in the variable MEASUREMENT_IDENTITY with measurement validity "all states" or "all states except CELL_DCH", and continue the associated UE positioning measurement reporting. NOTE: The UE's values of "Measurement interval" in the IE "UE positioning reporting criteria" and "Reporting interval" in the IE "Periodical Reporting Criteria" after this state transition revert to the values stored during the transition to CELL_PCH/URA_PCH (i.e., the 64-second interval specified in subclause 8.4.1.9b.2 is not retained).
8.4.1.10
8.4.1.10.1
Changes in measurement objects

When performing traffic volume event evaluation or reporting related to a certain transport channel, the UE shall consider all RBs which are mapped to the concerning transport channel e.g. if an additional RB is established on a transport channel used for event triggering or reporting, the new RB shall be taken into account. NOTE: The UE shall: 1> if the IE "Traffic volume measurement object" is included for this measurement: 2> while a transport channel that is referenced in the IE "Traffic volume measurement object" does not exist: 3> not perform any reporting related to this transport channel. 1> else: 2> report on all existing uplink transport channels; e.g. if an additional transport channel is established while the measurement is ongoing, this new transport channel shall be taken into account in the traffic volume measurement reporting. For every traffic volume event, the UE shall: 1> if the IE "Uplink transport channel type" is not included in the IE "Traffic volume measurement reporting criteria", or the "Uplink transport channel type" has the value "DCH" or "USCH" and the IE "UL transport channel id" is not included in the IE "Traffic volume measurement reporting criteria": 2> if the IE "Traffic volume measurement object" is not included: 3> take all existing UL transport channels into account for event triggering; e.g. if an additional transport channel is established while the measurement is ongoing, this new transport channel shall be taken into account in the traffic volume event triggering. 2> else: 3> while a transport channel that is referenced in the IE "Traffic Volume Measurement object" does not exist: 4> not take this transport channel identity into account in the traffic volume measurement triggering. 1> else: 2> while a transport channel that is referenced in the IE "Traffic Volume Measurement Reporting Criteria" does not exist: 3> not take this transport channel identity into account in the traffic volume event triggering. In this subclause, an "existing" uplink transport channel refers to a configured uplink transport channel applicable in the current RRC state.
3GPP
Release 6
240
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.1.10.2
Quality measurement
While a transport channel that is explicitly referenced with a transport channel identity in the IE "Quality Reporting Quantity" does not exist, the UE shall: 1> not perform any reporting related to this transport channel identity. If the IE "Quality Reporting Quantity" does not contain any explicit transport channel identities, the UE shall: 1> report the quality of all existing downlink dedicated transport channels; 1> if an additional transport channel is established while the measurement is ongoing: 2> take into account this new transport channel in the quality measurement reporting. While a transport channel that is explicitly referenced with a transport channel id in the IE "Quality Measurement Reporting Criteria" does not exist, the UE shall: 1> not take this transport channel identity into account in the quality measurement event triggering.
8.4.1.10.3
Intra-frequency, Inter-frequency and Inter-RAT measurements
For measurements which include the IE "Cells for measurement" the UE shall: 1> while an IE "Intra-frequency cell id" or IE "Inter-frequency cell id" or IE "Inter-RAT cell id" in the IE "Cells for measurement" points to a position in the variable CELL_INFO_LIST which is marked as "vacant": 2> not take this position into account for event triggering and reporting.
8.4.2
Measurement report
UE MEASUREMENT REPORT UTRAN
Figure 8.4.2-1: Measurement report, normal case
8.4.2.1
General
The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRAN.
8.4.2.2
Initiation
In CELL_DCH state, the UE shall: 1> transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing measurements that are being performed in the UE. In CELL_FACH state, the UE shall: 1> transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing traffic volume measurement or UE positioning measurement that is being performed in the UE. In TDD, if the Radio Bearer associated with the MEASUREMENT_IDENTITY fulfilling the reporting criteria for an ongoing traffic volume measurement is mapped on transport channel of type USCH, the UE shall:
3GPP
Release 6
241
3GPP TS 25.331 V6.23.0 (2009-09)
1> initiate the "PUSCH CAPACITY REQUEST" procedure instead of transmitting a MEASUREMENT REPORT (TDD Only). In CELL_PCH or URA_PCH state, the UE shall: 1> first perform the cell update procedure according to subclause 8.3.1, using the cause "uplink data transmission", in order to transit to CELL_FACH state; and then 1> transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are fulfilled for any ongoing UE positioning measurement which is being performed in the UE. The reporting criteria are fulfilled if either: a periodic MEASUREMENT REPORT message shall be sent according to the IE "Periodical Reporting Criteria"; or an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for different measurement types are described in detail in clause 14.
For the measurement, which triggered the MEASUREMENT REPORT message, the UE shall: 1> set the IE "measurement identity" to the measurement identity, which is associated with that measurement in variable MEASUREMENT_IDENTITY; 1> set the IE "measured results" to include measurements according to the IE "reporting quantity" of that measurement stored in variable MEASUREMENT_IDENTITY; and 2> if all the reporting quantities are set to "false": 3> not set the IE "measured results". 1> set the IE "Measured results" in the IE "Additional measured results" according to the IE "reporting quantity" for all measurements associated with the measurement identities included in the "Additional measurements list" stored in variable MEASUREMENT_IDENTITY of the measurement that triggered the measurement report; and 2> if one or more additional measured results are to be included: 3> include only the available additional measured results, and sort them in ascending order according to their IE "measurement identity" in the MEASUREMENT REPORT message. 1> if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report): 2> set the IE "Event results" according to the event that triggered the report. 1> if the IE Inter-RAT measured results list or the IE Inter-RAT measurement event results is included in the measurement report: 2> if the indication status of the IE "Inter-RAT cell info indication" in the variable CELL_INFO_LIST is marked "present" , include the stored value of the IE "Inter-RAT cell info indication" in the MEASUREMENT REPORT message. The UE shall: 1> transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RLC according to the stored IE "measurement reporting mode" associated with the measurement identity that triggered the report. When the MEASUREMENT REPORT message has been submitted to lower layers for transmission: 1> the procedure ends.
3GPP
Release 6
242
3GPP TS 25.331 V6.23.0 (2009-09)
8.4.3
Assistance Data Delivery

UE UTRAN
ASSISTANCE DATA DELIVERY
Figure 8.4.3-1 Assistance Data Delivery
8.4.3.1
General
The purpose of the assistance data delivery procedure is to transfer UE positioning related assistance data from the UTRAN to the UE.
8.4.3.2
Initiation
When requested by the Core Network, the UTRAN may deliver UE positioning related assistance data with a ASSISTANCE DATA DELIVERY message, which is transmitted on the downlink DCCH using AM RLC
8.4.3.3
Reception of ASSISTANCE DATA DELIVERY message by the UE
Upon reception of a ASSISTANCE DATA DELIVERY message the UE shall: 1> if IE "UE positioning OTDOA assistance data for UE-based" is included: 2> act as specified in subclause 8.6.7.19.2a. 1> if IE "UE positioning GPS assistance data" is included: 2> act as specified in subclause 8.6.7.19.3.
8.4.3.4
Invalid ASSISTANCE DATA DELIVERY message
If the UE receives a ASSISTANCE DATA DELIVERY message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall: 1> transmit an RRC STATUS message on the uplink DCCH using AM RLC; 1> include the IE "Identification of received message"; and 1> set the IE "Received message type" to ASSISTANCE DATA DELIVERY; and 1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the ASSISTANCE DATA DELIVERY message in the table "Rejected transactions" in the variable TRANSACTIONS; and 1> clear that entry; 1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION. 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid ASSISTANCE DATA DELIVERY message has not been received.
3GPP
Release 6
243
3GPP TS 25.331 V6.23.0 (2009-09)
8.5
8.5.1
General procedures
Selection of initial UE identity
The purpose of the IE "Initial UE identity" is to provide a unique UE identification at the establishment of an RRC connection. The type of identity shall be selected by the UE according to the following. If the UE is operating in "GSM-MAP mode", the UE shall choose "UE id type" in the IE "Initial UE identity" with the following priority: 1. TMSI (GSM-MAP): The TMSI (GSM-MAP) shall be chosen if available. The IE "LAI" in the IE "Initial UE identity" shall also be present when TMSI (GSM-MAP) is used, for making it unique. 2. P-TMSI (GSM-MAP): The P-TMSI (GSM-MAP) shall be chosen if available and no TMSI (GSM-MAP) is available. The IE "RAI" in the IE "Initial UE identity" shall in this case also be present when P-TMSI (GSMMAP) is used, for making it unique. 3. IMSI (GSM-MAP): The IMSI (GSM-MAP) shall be chosen if available and no TMSI (GSM-MAP) or P-TMSI is available. 4. IMEI: The IMEI shall be chosen when none of the above three conditions are fulfilled. When being used, the IEs "TMSI (GSM-MAP)," "P-TMSI (GSM-MAP)", "IMSI (GSM-MAP)", "LAI" and "RAI" shall be set equal to the values of the corresponding identities stored in the USIM or SIM. If the UE is operating in "ANSI-41 mode", the UE shall choose "UE id type" in the IE "Initial UE identity" according to the procedure specified in the 3GPP2 document "3GPP2 C.P0004-A".
8.5.2
Actions when entering idle mode from connected mode
When entering idle mode from connected mode, the UE shall: 1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4; 1> if the RRC CONNECTION RELEASE message was received and the IE "Redirection info" was present therein: 2> attempt to camp on a suitable cell on the indicated UTRA carrier included in the RRC CONNECTION RELEASE message; 2> attempt to camp on a suitable cell of the list of cells for the indicated RAT included in the RRC CONNECTION RELEASE message. If no cells were indicated for that RAT or no suitable cell of the indicated cells for that RAT is found within 10s, attempt to camp on any suitable cell of that RAT; or 2> if no suitable cell is found on the indicated UTRA carrier or RAT camp on any suitable cell. 1> attempt to select a suitable cell to camp on. When leaving connected mode according to [4], the UE shall: 1> perform cell selection. While camping on a cell, the UE shall: 1> acquire system information according to the system information procedure in subclause 8.1; 1> perform measurements according to the measurement control procedure specified in subclause 8.4; and 1> if the UE is registered: 2> be prepared to receive paging messages according to the paging procedure in subclause 8.2. If the UE is operating in "GSM-MAP mode", the UE shall: 1> delete any NAS system information received in connected mode;
3GPP
Release 6
244
3GPP TS 25.331 V6.23.0 (2009-09)
1> acquire the NAS system information in system information block type 1; and 1> proceed according to subclause 8.6.1.2. When entering idle mode, the UE shall: 1> if the USIM is present, for each CN domain: 2> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: 3> set the START value for this domain to zero; and 3> store this START value for this domain in the USIM. 2> else: 3> if the current "START" value, according to subclause 8.5.9 for a CN domain, is greater than or equal to the value "THRESHOLD" of the variable START_THRESHOLD: 4> delete the ciphering and integrity keys that are stored in the USIM for that CN domain; 4> inform the deletion of these keys to upper layers. 3> else: 4> store the current "START" value for this CN domain on the USIM. NOTE: 1> else: 2> if the SIM is present, for each CN domain: 3> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: 4> set the START value for this domain to zero; and 4> store this START value for this domain in the UE 3> else: 4> if the current "START" value, according to subclause 8.5.9 for this CN domain, is greater than or equal to the value "THRESHOLD" of the variable START_THRESHOLD: 5> delete the Kc key for this CN domain; 5> delete the ciphering and integrity keys that are stored in the UE for that CN domain; 5> set the "START" values for this CN domain to zero and store it the UE; 5> inform the deletion of the key to upper layers. 4> else: 5> store the current "START" value for this CN domain in the UE. NOTE: Prior to storing the "START" value, the UE should calculate this "START" value according to subclause 8.5.9. Prior to storing the "START" value, the UE should calculate this "START" value according to subclause 8.5.9.
8.5.3
Open loop power control upon establishment of DPCCH
This procedure is used in FDD mode only. When establishing the first DPCCH the UE shall start the UL inner loop power control at a power level according to:
3GPP
Release 6
245
3GPP TS 25.331 V6.23.0 (2009-09)
1> DPCCH_Initial_power = DPCCH_Power_offset CPICH_RSCP Where DPCCH_Power_offset shall have the value of IE "DPCCH Power offset" in IE "Uplink DPCH power control info" The value for the CPICH_RSCP shall be measured by the UE.
8.5.4
Physical channel establishment criteria
When a physical dedicated channel establishment is initiated by the UE, the UE shall start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE shall consider this as a "physical channel failure". NOTE: The criteria defined in this subclause only apply in case the UE performs synchronisation procedure A (FDD only).
8.5.5
Actions in "out of service area" and "in service area"
This subclause specifies the general actions the UE shall perform when it detects "out of service" or "in service" area. The specific UE behaviour when it detects "out of service" or "in service area" and periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" is specified in subclause 8.3.1.
8.5.5.1
Detection of "out of service" area
The UE shall detect "out of service" area as defined in [19].
8.5.5.1.1
Actions following detection of "out of service" area in URA_PCH or CELL_PCH state
If the UE detects the "out of service area" and the UE is in URA_PCH or CELL_PCH state it shall perform the following actions: 1> start timer T316; 1> perform processes described in subclause 7.2.2.
8.5.5.1.2
Actions following detection of "out of service" area in CELL_FACH state
If the UE detects the "out of service area" and the UE is in CELL_FACH state it shall perform the following actions. The UE shall: 1> start timer T317 if not already running; 1> perform processes described in subclause 7.2.2.
8.5.5.1.3
Actions following detection of "out of service" area on transition from CELL_DCH to URA_PCH or CELL_PCH
If the UE detects the "out of service area" on transition from CELL_DCH to URA_PCH or CELL_PCH, it shall perform the following actions: 1> start timer T316; 1> start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity";
3GPP
Release 6
246
3GPP TS 25.331 V6.23.0 (2009-09)
1> perform processes described in subclause 7.2.2.
8.5.5.1.4
Actions following detection of "out of service" area on transition from CELL_DCH to CELL_FACH
If the UE detects the "out of service area" on transition from CELL_DCH to CELL_FACH, it shall perform the following actions: 1> if the transition is triggered by a reconfiguration procedure: 2> start timer T317; 2> start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity"; 2> perform processes described in subclause 7.2.2. 1> otherwise: 2> perform processes described in subclause 7.2.2.
8.5.5.2
Detection of "in service" area
When a suitable cell is found based on the description in [4], the UE considers it as having detected "in service area".
8.5.5.2.1
Actions following Re-entry into "in service area" in URA_PCH or CELL_PCH state
If the UE re-enters "in service area" before T316 expiry the UE shall perform the following actions. The UE shall: 1> stop T316; 1> if T307 is active: 2> stop T307. 1> if the UE is in CELL_PCH state and the UE is camped on a cell different from the one where service was lost: 2> initiate the cell update procedure using the cause "cell-reselection" as specified in subclause 8.3.1. 1> perform processes described in subclause 7.2.2.
8.5.5.2.2
Actions following re-entry into "in service area" in CELL_FACH state
If the UE detects "in service area" before T317 expiry the UE shall perform the following actions. If no cell update procedure or URA update procedure is ongoing, the UE shall: 1> stop T317; 1> if T307 is active: 2> stop T307. 1> initiate the cell update procedure using as cause "Re-entering service area" as specified in subclause 8.3.1; 1> perform processes described in subclause 7.2.2. If a cell update procedure or URA update procedure is ongoing, the UE shall: 1> stop T317; 1> perform the actions as specified in 8.3.1.
3GPP
Release 6
247
3GPP TS 25.331 V6.23.0 (2009-09)
8.5.5.3
T316 expiry
On T316 expiry the UE shall perform the following actions. The UE shall: 1> if "out of service area" is detected: 2> start timer T317; 2> move to CELL_FACH state; 2> perform processes described in subclause 7.2.2. 1> if "in service area" is detected: 2> initiate the cell update procedure using as cause "Re-entering service area" as specified in subclause 8.3.1; 2> perform processes described in subclause 7.2.2.
8.5.5.4
T317 expiry
T317 shall never expire, i.e. all its values shall be assumed to be "infinity". If T317 is running: 1> the UE behaviour shall be as specified in subclause 7.2.2.2.
8.5.6
Radio link failure criteria and actions upon radio link failure
In CELL_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1 for the established DPCCH or F-DPCH physical channel in FDD, and the physical channels associated with mapped DCCHs in TDD, the UE shall: 1> start timer T313; 1> upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state: 2> stop and reset timer T313. 1> if T313 expires: 2> consider it as a "Radio link failure". Periods in time where neither "in sync" nor "out of sync" is reported by layer 1 do not affect the evaluation of the number of consecutive (resp. successive) "in sync" or "out of sync" indications. When a radio link failure occurs, the UE shall: 1> clear the dedicated physical channel configuration; 1> perform actions as specified for the ongoing procedure; 1> if no procedure is ongoing or no actions are specified for the ongoing procedure: 2> perform a cell update procedure according to subclause 8.3.1 using the cause "radio link failure".
8.5.7
Open loop power control
For FDD and prior to PRACH transmission the UE shall: 1> acquire valid versions of the necessary System Information IEs as follows: 2> if the UE has stored valid versions of the IEs "Primary CPICH Tx power" and "Constant value": 3> use the stored content of the IEs. 2> otherwise:
3GPP
Release 6
248
3GPP TS 25.331 V6.23.0 (2009-09)
3> read and store the IE "Primary CPICH Tx power" and "Constant value" in System Information Block type 6 (or System Information Block type 5 or System Information Block type 5bis, if System Information Block type 6 is not being broadcast). 2> if the UE has a valid version of the IE "UL interference" stored: 3> use the stored content of the IE "UL interference". 2> otherwise: 3> read and store the IE "UL interference" in System Information Block type 7; 3> if the UE fails to read the IE "UL interference" in System Information Block type 7 due to bad radio conditions, the UE shall use the last stored IE "UL interference". 1> measure the value for the CPICH_RSCP; 1> calculate the power for the first preamble as: Preamble_Initial_Power = Primary CPICH TX power CPICH_RSCP + UL interference + Constant Value Where, Primary CPICH TX power shall have the value of IE "Primary CPICH Tx power", UL interference shall have the value of IE "UL interference"; and Constant Value shall have the value of IE "Constant value". 1> as long as the physical layer is configured for PRACH transmission: 2> continuously recalculate the Preamble_Initial_Power when any of the broadcast parameters used in the above formula changes; and 2> resubmit to the physical layer the new calculated Preamble_Initial_Power. For 3.84 Mcps TDD the UE shall: 1> if in the IE "Uplink DPCH Power Control info" the "CHOICE UL OL PC info" has the value "Broadcast UL OL PC info": 2> prior to DPCH transmission the UE shall: 3> acquire valid versions of the necessary System Information IEs as follows: 4> if the UE has stored valid versions of the IEs "Primary CCPCH Tx power" and "DPCH Constant value": 5> use the stored content of the IEs. 4> otherwise: 5> read and store the IE "Primary CCPCH Tx power" and "DPCH Constant value" in System Information Block type 6 (or System Information Block type 5, if System Information Block type 6 is not being broadcast). 3> if the UE has a valid version of the IE "UL interference" for each active UL timeslot stored: 4> use the stored content of the IE "UL interference" for each active UL timeslot. 3> otherwise: 4> read and store the IE "UL Timeslot Interference" for each active UL timeslot in System Information Block type 14; 4> if the UE fails to read the IE "UL Timeslot Interference" for each active UL time slot in System Information Block type 14 due to bad radio conditions, the UE shall use the last stored IE "UL Timeslot interference" for each active UL timeslot.
3GPP
Release 6
249
3GPP TS 25.331 V6.23.0 (2009-09)
1> otherwise: 2> acquire Reference Power, Constant Values and IBTS for all active UL timeslots from the IE "Uplink DPCH Power Control info". 1> for PUSCH, PRACH and HS-SICH power control: 2> prior to PUSCH or PRACH transmission the UE shall: 3> acquire valid versions of the necessary System Information IEs as follows: 4> if the UE has stored valid versions of the IEs "Primary CCPCH Tx power" and "PUSCH Constant value" for PUSCH transmissions or "PRACH Constant value" for PRACH transmissions: 5> use the stored content of the IEs. 4> otherwise: 5> read and store the IE "Primary CCPCH Tx power" and "PUSCH Constant value" for PUSCH transmissions or "PRACH Constant value" for PRACH transmissions in System Information Block type 6 (or System Information Block type 5, if System Information Block type 6 is not being broadcast). 3> if the UE has a valid version of the IE "UL interference" for each active UL timeslot stored: 4> use the stored content of the IE "UL interference" for each active UL timeslot. 3> otherwise: 4> read and store the IE "UL Timeslot Interference" for each active UL timeslot in System Information Block type 14; 4> if the UE fails to read the IE "UL Timeslot Interference" for each active UL time slot in System Information Block type 14 due to bad radio conditions, the UE shall use the last stored IE "UL Timeslot interference" for each active UL timeslot. calculate the UL transmit power according to the following formula for the PRACH continuously while the physical channel is active: PPRACH = LPCCPCH + IBTS + PRACH Constant value, 2> 3dB shall be added to RACH Constant Value in the above equation for the case where RACH Spreading Factor = 8. 1> calculate the UL transmit power according to the following formula for the DPCH continuously while the physical channel is active: PDPCH = LPCCPCH+(1-)L0 + IBTS + SIRTARGET+ DPCH Constant value 1> calculate the UL transmit power according to the following formula for the PUSCH continuously while the physical channel is active: PPUSCH = LPCCPCH+(1-)L0 + IBTS + SIRTARGET+ PUSCH Constant value 1> calculate the initial UL transmit power for HS-SICH according to the following formula: PHS-SICH = LPCCPCH+(1-)L0 + IBTS + SIRTARGET+ HS-SICH Constant value Where, for all the above equations for 3.84 Mcps TDD the following apply: PPRACH, PDPCH, PPUSCH and PHS-SICH: Transmitter power level in dBm; Pathloss values: LPCCPCH: Measurement representing path loss in dB based on beacon channels (the reference transmit power is signalled as the value of the IE "Primary CCPCH Tx Power" on BCH in System Information
3GPP
Release 6
250
3GPP TS 25.331 V6.23.0 (2009-09)
Block type 6 (or System Information Block type 5, according to subclause 8.1.1.6.5), or individually signalled in the IE" Uplink DPCH Power Control info"). L0: Long term average of path loss in dB; If the midamble is used in the evaluation of LPCCPCH and L0, and the Tx diversity scheme used for the PCCPCH involves the transmission of different midambles from the diversity antennas, the received power of the different midambles from the different antennas shall be combined prior to evaluation of the variables.
IBTS: Interference signal power level at cell's receiver in dBm. IBTS shall have the value of the IE "UL Timeslot Interference" (IE "UL Timeslot Interference" is broadcast on BCH in System Information Block type 14 or individually signalled to each UE in the IE "Uplink DPCH Power Control info" for each active uplink timeslot). : is a weighting parameter, which represents the quality of path loss measurements. may be a function of the time delay between the uplink time slot and the most recent down link PCCPCH time slot. is calculated at the UE. shall be smaller or equal to the value of the IE "Alpha". If the IE "Alpha" is not explicitly signalled to the UE shall be set to 1. If UE is capable of estimating its position by using the OTDOA IPDL method, the UE shall use the IPDL- parameter. SIRTARGET: Target SNR in dB. This value is individually signalled to UEs in IE "UL target SIR" in IE "Uplink DPCH Power Control Info" or in IE "PUSCH Power Control Info" or in IE "HS-SICH Power Control Info". PRACH Constant value: PRACH Constant value shall have the value of the IE "PRACH Constant value". DPCH Constant value: DPCH Constant value shall have the value of the IE "DPCH Constant value". PUSCH Constant value: PUSCH Constant value shall have the value of the IE "PUSCH Constant value". HS-SICH Constant value: HS-SICH Constant value shall have the value of the IE "HS-SICH Constant value". Values received by dedicated signalling shall take precedence over broadcast values. If IPDLs are applied, the UE may increase UL Tx power by the value given in the IE "Max power increase". This power increase is only allowed in the slots between an idle slot and the next beacon slot.
For 1.28 Mcps TDD the UE shall: 1> acquire valid versions of the necessary System Information IEs as follows: 2> if the UE has stored a valid version of the IE "Primary CCPCH Tx Power": 3> use the stored content of the IE. 2> otherwise: 3> read and store the IE "Primary CCPCH Tx Power" from System Information Block type 6 (or System Information Block type 5, if System Information Block type 6 is not being broadcast). 1> calculate the UL transmit power according to the following formula for each UpPCH code transmission: PUpPCH = LPCCPCH + PRXUpPCHdes + (i-1)* Pwrramp NOTE: When i equals 1, the initial signature power "Signature_Initial_Power" defined in [33] corresponds to PUpPCH with i set to 1.
1> calculate the UL transmit power according to the following formula for each PRACH transmission: PPRACH = LPCCPCH + PRXPRACHdes + (iUpPCH-1) * Pwrramp 1> calculate the initial UL transmit power according to the following formula for the PUSCH. Once the UE receives TPC bits relating to the PUSCH then it transitions to closed loop power control. If successive PUSCH resource
3GPP
Release 6
251
3GPP TS 25.331 V6.23.0 (2009-09)
allocations are contiguous then no return is made to open loop power control at the beginning of the succeeding resource allocation. PUSCH = PRXPUSCHdes + LPCCPCH 1> calculate the initial UL transmit power for HS-SICH according to the following formula: PHS-SICH = PRXHS-SICH + LPCCPCH 1> calculate the initial UL transmit power according to the following formula for the DPCH. Once the UE receives TPC bits relating to the uplink DPCH then it transitions to closed loop power control. PDPCH = PRXDPCHdes + LPCCPCH Where: PUpPCH, PPRACH, PDPCH, PHS-SICH & PUSCH: Transmitter power level in dBm. LPCCPCH: Measurement representing path loss in dB (reference transmit power "Primary CCPCH Tx Power" is broadcast on BCH in System Information Block type 5 and System Information Block type 6, or individually signalled to each UE in the IE" Uplink DPCH Power Control info"). i is the number of transmission attempts on UpPCH, i=1Max SYNC_UL Transmissions. iUpPCH is the final value of i. PRXPRACHdes: Desired PRACH RX power at the cell's receiver in dBm signalled to the UE by the network in the FPACH response to the UE's successful SYNC_UL transmission. PRXUpPCHdes: Desired UpPCH RX power at the cell's receiver in dBm. The value is broadcast in "PRXUpPCHdes" in IE "SYNC_UL info" on BCH and shall be read on System Information Block type 5 and System Information Block type 6. It can also be signalled directly to the UE in IE "Uplink Timing Advance Control" contained in a protocol message triggering a hard handover or a transition from cell FACH to cell DCH state. PRXPUSCHdes: Desired PUSCH RX power at the cell's receiver in dBm signalled to the UE in IE "PUSCH Power Control Info". PRXDPCHdes: Desired DPCH RX power at the cell's receiver in dBm signalled to the UE in IE "Uplink DPCH Info" and IE "Uplink DPCH Power Control Info". Pwrramp: The UE shall increase its transmission power by the value of the IE "Power Ramp step" by every UpPCH transmission. Its value is signalled in the IE "SYNC UL info" in System Information Block type 5 and System Information Block type 6 or is signalled to the UE in the IE "Uplink Timing Advance Control" contained in a protocol message triggering a hard handover or a transition from cell FACH state to cell DCH state. PRXHS-SICH: Desired HS-SICH RX power at the cell's receiver in dBm signalled to the UE in IE "Downlink HS-PDSCH Information". Ack-Nack Power Offset: Difference in the desired RX power between HS-SICH transmissions conveying an acknowledgement and transmissions conveying a negative acknowledgement signalled to the UE in IE "HSSCCH Info".
8.5.8
Maintenance of Hyper Frame Numbers
The MSBs of both the ciphering sequence numbers (COUNT-C) and integrity sequence numbers (COUNT-I), for the ciphering and integrity protection algorithms, respectively [40], are called the Hyper Frame Numbers (HFN). For integrity protection, the UE shall: 1> maintain COUNT-I as specified in subclause 8.5.10. The following hyper frame numbers types are defined:
3GPP
Release 6
252
3GPP TS 25.331 V6.23.0 (2009-09)
MAC-d HFN: 24 MSB of COUNT-C for data sent over RLC TM RLC UM HFN: 25 MSB of COUNT-C for data sent over RLC UM RLC AM HFN: 20 MSB of COUNT-C for data sent over RLC AM RRC HFN: 28 MSB of COUNT-I For non-transparent mode RLC signalling radio bearers and radio bearers, the UE shall: 1> maintain one uplink and one downlink COUNT-C per signalling radio bearer and per radio bearer and one uplink and one downlink COUNT-I per signalling radio bearer; 1> increment the RLC UM HFN and RLC AM HFN in uplink and downlink by one each time the RLC sequence number wraps around in uplink and downlink respectively; 1> if the activation time for a new ciphering configuration set by an RRC procedure is equal to zero: 2> apply the configured RLC UM HFN or RLC AM HFN at this activation time, i.e. the configured HFN is not incremented. NOTE: On the receiver side it may happen that the RLC PDU with sequence number equal to the activation time is lost and the first received PDU after the activation time implies a wrap around of the sequence number compared to the activation time. In this case the configured HFN is incremented by one. This action is taken only when the activation time is set to a RLC PDU sequence number value other than zero.
For all transparent mode RLC signalling radio bearers and radio bearers of each CN domain, the UE shall: 1> maintain one COUNT-C, common for all radio bearers in uplink and downlink; 1> increment the MAC-d HFN by one each time the CFN wraps around; 1> if the activation time for a new ciphering configuration set by an RRC procedure is equal to zero: 2> apply the configured MAC-d HFN at this activation time, i.e. the configured HFN is not incremented. 1> maintain one uplink and one downlink COUNT-I per signalling radio bearer. NOTE: In this release of the specification there is only an uplink transparent mode COUNT-I, which is used for signalling radio bearer RB0.
COUNT-C and COUNT-I are defined in [40], with the following supplement for COUNT-C: for transparent mode RLC radio bearers with a transmission time interval of x radio frames (x = 2, 4, 8), the MAC PDU is carried by L1 in x consecutive radio frames due to radio frame segmentation. In this case, the CFN of the first radio frame in the TTI shall be used as the CFN component of COUNT-C for ciphering of all data in the TTI [15].
8.5.9
START value calculation
In connected mode, if a security mode command procedure has been successfully completed for a CN domain during the current RRC connection, the START value for that CN domain is calculated as: Let STARTX = the START value for CN domain 'X' prior to the calculation below: STARTX' = MSB20 ( MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2. if STARTX'= the maximum value = 1048575 then STARTX = STARTX'; if the current STARTX < STARTX' then STARTX = STARTX', otherwise STARTX is unchanged.
3GPP
Release 6
253
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
Here, "most recently configured" means that if there is more than one key in use for a CN domain, due to non-expiry of the ciphering and/or integrity protection activation time for any signalling radio bearers and/or radio bearers, do not include the COUNT-I/COUNT-C for these signalling radio bearers and/or radio bearers in the calculation of the START X'.
COUNT-C corresponding to non-ciphered radio bearers (i.e. RBs with ciphering status set to "not started") shall not be included in the calculation of the STARTX'. If a radio bearer is released and the radio bearer was ciphered, the values of the COUNT-C at the time the radio bearer is released shall be taken into account in the calculation of the STARTX'. If a security mode command procedure has not been successfully completed for a CN domain during the current RRC connection, the UE shall use the latest transmitted START value for this CN domain.
8.5.10
Integrity protection
If the "Status" in the variable INTEGRITY_ PROTECTION_INFO has the value "Started" then the UE shall: 1> perform integrity protection (and integrity checking) on all RRC messages, with the following exceptions: HANDOVER TO UTRAN COMPLETE MBMS ACCESS INFORMATION MBMS COMMON P-T-M RB INFORMATION MBMS CURRENT CELL P-T-M RB INFORMATION MBMS GENERAL INFORMATION MBMS MODIFIED SERVICES INFORMATION (MCCH only) MBMS NEIGHBOURING CELL P-T-M RB INFORMATION MBMS SCHEDULING INFORMATION MBMS UNMODIFIED SERVICES INFORMATION PAGING TYPE 1 PUSCH CAPACITY REQUEST PHYSICAL SHARED CHANNEL ALLOCATION RRC CONNECTION REQUEST RRC CONNECTION SETUP RRC CONNECTION SETUP COMPLETE RRC CONNECTION REJECT RRC CONNECTION RELEASE (CCCH only) SYSTEM INFORMATION SYSTEM INFORMATION CHANGE INDICATION TRANSPORT FORMAT COMBINATION CONTROL (TM DCCH only) If the "Status" in the variable INTEGRITY_ PROTECTION_INFO has the value "Not started" then integrity protection (and integrity checking) shall not be performed on any RRC message. For each signalling radio bearer, the UE shall use two RRC hyper frame numbers: "Uplink RRC HFN"; "Downlink RRC HFN".
3GPP
Release 6
254
3GPP TS 25.331 V6.23.0 (2009-09)
and two message sequence numbers: "Uplink RRC Message sequence number"; "Downlink RRC Message sequence number".
The above information is stored in the variable INTEGRITY_PROTECTION_INFO per signalling radio bearer (RB0RB4). Upon the first activation of integrity protection for an RRC connection, UE and UTRAN initialise the "Uplink RRC Message sequence number" and "Downlink RRC Message sequence number" for all signalling radio bearers as specified in subclauses 8.6.3.5 and 8.5.10.1. The RRC message sequence number (RRC SN) is incremented for every integrity protected RRC message. If the IE "Integrity Protection Mode Info" is present in a received message, the UE shall: 1> perform the actions in subclause 8.6.3.5 before proceeding with the integrity check of the received message.
8.5.10.1
Integrity protection in downlink
If the UE receives an RRC message on signalling radio bearer with RB identity n, the "Status" in the variable INTEGRITY_ PROTECTION_INFO has the value "Started" and the IE 'Integrity check info' is present the UE shall: 1> check the value of the IE "RRC message sequence number" included in the IE "Integrity check info"; 2> if the "Downlink RRC Message sequence number" is not present in the variable INTEGRITY_PROTECTION_INFO: 3> initialise the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO with the value of the IE "RRC message sequence number" included in the IE "Integrity check info" of the received message. 2> if the "Downlink RRC Message sequence number" is present in the variable INTEGRITY_PROTECTION_INFO: 3> if the RRC message sequence number is lower than the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO: 4> increment "Downlink RRC HFN" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO with one. NOTE: The actions above imply that also for the case the "Downlink RRC HFN" is re-initialised by a security mode control procedure, this "Downlink RRC HFN" value is incremented by one before it is applied for the integrity protection of any received message if the conditions above are fulfilled.
3> if the RRC message sequence number is equal to the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO: 4> discard the message. 1> calculate an expected message authentication code in accordance with subclause 8.5.10.3; 1> compare the expected message authentication code with the value of the received IE "message authentication code" contained in the IE "Integrity check info"; 2> if the expected message authentication code and the received message authentication code are the same, the integrity check is successful: 3> update the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO with the value of the IE "RRC message sequence number" included in the IE "Integrity check info" of the received RRC message. 2> if the calculated expected message authentication code and the received message authentication code differ: 3> act as if the message was not received.
3GPP
Release 6
255
3GPP TS 25.331 V6.23.0 (2009-09)
If the UE receives an RRC message on signalling radio bearer with identity 0, 1, or 2, the "Status" in the variable INTEGRITY_ PROTECTION_INFO has the value "Started" and the IE 'Integrity check info' is not present the UE shall: 1> discard the message. If the UE receives an RRC message on signalling radio bearer with identity 3 or 4, the "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and the IE 'Integrity check info' is not present: 1> if a security mode command procedure has not been successfully completed during the current RRC connection for the CN domain indicated by IE "CN Domain Identity" in the received message: 2> the UE shall forward the message to upper layer. 1> else: 2> the UE shall discard the message. UTRAN may transmit several copies of the same message in the downlink to increase the probability of proper reception of the message by the UE. In such a case, the RRC SN for these repeated messages should be the same.
8.5.10.2
Integrity protection in uplink
Prior to sending an RRC message using the signalling radio bearer with radio bearer identity n, and the "Status" in the variable INTEGRITY_ PROTECTION_INFO has the value "Started" the UE shall: 1> increment "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO with 1, even if the message is a retransmission of a previously transmitted message. 1> if the "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO equals zero: 2> increment "Uplink RRC HFN" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO by one. NOTE 1: The actions above imply that also for the case the "Uplink RRC HFN" is re-initialised by a security mode control procedure, this "Uplink RRC HFN" is incremented before it is applied in the integrity protection of any transmitted message if the conditions above are fulfilled. NOTE 2: For SRB0, this is also valid in case the Message Sequence Number has been increased by N302 +2 resulting in an MSN which equals 0 (i.e.: SRB0 UL activation time equals 0). Then the uplink RRC HFN is incremented by 1 after it is re-initialized and before it is applied in the integrity protection of any transmitted message. 1> calculate the message authentication code in accordance with subclause 8.5.10.3; 1> replace the "Message authentication code" in the IE "Integrity check info" in the message with the calculated message authentication code; 1> replace the "RRC Message sequence number" in the IE "Integrity check info" in the message with contents set to the new value of the "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO. In the response message for the procedure ordering the security reconfiguration, the UE indicates the activation time, for each signalling radio bearer. When the new integrity configuration is to be applied in uplink, UTRAN should start to apply the new integrity protection configuration according to the activation time for each signalling radio bearer (except for the signalling radio bearer which is used to send the message that is reconfiguring the security configuration where the new configuration is to be applied starting from and including reception of the response message).
8.5.10.3
Calculation of message authentication code
The UE shall calculate the message authentication code in accordance with [40]. The input parameter MESSAGE [40] for the integrity algorithm shall be constructed by:
3GPP
Release 6
256
3GPP TS 25.331 V6.23.0 (2009-09)
1> setting the "Message authentication code" in the IE "Integrity check info" in the message to the value of the IE "RB identity" for the signalling radio bearer; 1> setting the "RRC Message sequence number" in the IE "Integrity check info" in the message to zero; 1> encoding the message; 1> appending RRC padding (if any) as a bit string to the encoded bit string as the least significant bits. For usage on an RRC message transmitted or received on the radio bearer with identity n, the UE shall: 1> construct the input parameter COUNT-I [40] by appending the following IEs from the IE "Signalling radio bearer specific integrity protection information" for radio bearer n in the variable INTEGRITY_PROTECTION_INFO: 2> for uplink: 3> "Uplink RRC HFN", as the MSB, and "Uplink RRC Message sequence number", as LSB. 2> for downlink: 3> "Downlink RRC HFN", as the MSB, and the IE "RRC message sequence number" included in the IE "Integrity check info", as LSB.
8.5.11
FACH measurement occasion calculation
When in CELL_FACH state and when the variable C_RNTI is non-empty the UE in FDD mode shall perform measurements as specified in subclauses 8.4.1.6 and 8.4.1.9 during the frame(s) with the SFN value fulfilling the following equation: SFN div N = C_RNTI mod M_REP + n * M_REP where N is the TTI (in number of 10ms frames) of the FACH having the largest TTI on the SCCPCH selected by the UE according to the procedure in subclause 8.5.19. FACHs that only carry MBMS logical channels (MTCH, MSCH, or MCCH) are excluded from measurement occasion calculations. C_RNTI is the C-RNTI value of the UE stored in the variable C_RNTI M_REP is the Measurement Occasion cycle length. According to the equation above, a FACH Measurement Occasion of N frames will be repeated every N * M_REP frame, and M_REP = 2k. where, k is the FACH Measurement occasion cycle length coefficient. The value of the FACH Measurement occasion cycle length coefficient is read in system information in "System Information Block type 11" or "System Information Block type 12" in the IE "FACH measurement occasion info".
n = 0,1,2 as long as SFN is below its maximum value
The UE is allowed to measure on other occasions in case the UE moves "out of service" area or in case it can simultaneously perform the ordered measurements. A UE in TDD mode shall use the frame(s) with the SFN value fulfilling the above equation for neighbour cells measurements. NOTE: For FDD, in order to meet the MBMS demodulation performance requirements [21], a UE receiving MBMS PTM may not be able use the entire measurement occasion.
8.5.12
Establishment of Access Service Classes
The PRACH resources (i.e. access slots and preamble signatures for FDD), timeslot (with specific frame allocation and channelisation code for 3.84 Mcps TDD and SYNC_UL codes (with specific frame allocation) for 1.28 Mcps TDD)
3GPP
Release 6
257
3GPP TS 25.331 V6.23.0 (2009-09)
may be divided between different Access Service Classes in order to provide different priorities of RACH usage. It is possible for more than one ASC or for all ASCs to be assigned to the same access slot/signature space in FDD or frame allocation/channelisation codes in 3.84 Mcps TDD or frame allocation/SYNC_UL codes in 1.28 Mcps TDD. Access Service Classes shall be numbered in the range 0 i NumASC 7 (i.e. the maximum number of ASCs is 8). An ASC is defined by an identifier, i, that defines a certain partition of the PRACH resources (SYNC_UL resources in 1.28 Mcps TDD) and an associated persistence value Pi. A set of ASC parameters consists of "NumASC+1" such parameters (i, Pi), i = 0, , NumASC. PRACH partitions shall be established using the information element "PRACH partitioning". The persistence values Pi to be associated with each ASC shall be derived from the dynamic persistence level N = 1,, 8 which is broadcast in System Information Block 7, and the persistence scaling factors si, broadcast in System Information Block Type 5 or System Information Block type 5bis and possibly also in System Information Block Type 6, as follows: P(N) = 2(N 1)
ASC # i Pi 0 1 1 P(N) 2 s2 P(N) 3 s3 P(N) 4 s4 P(N) 5 s5 P(N) 6 s6P(N) 7 s7 P(N)
In addition, MBMS specific persistence values may be provided within the MBMS MODIFIED SERVICES INFORMATION message. The UE behaviour upon receiving upon receiving an MBMS dynamic persistence value is specified in subclause 8.6.9.1a. Scaling factors si are provided optionally for i = 2,, NumASC, where NumASC+1 is the number of ASCs as defined by PRACH partitioning. If no scaling factors are broadcast, default value 1 shall be used if NumASC 2. If k 1 scaling factors are broadcast and NumASC k+2 then the last scaling factor sk+1 shall be used as default for the ASCs where i > k +1. The set of ASC parameters is provided to MAC with the CMAC-Config-REQ primitive (see [15]), the PRACH partitioning is provided to PHY using the CPHY-RL-Setup-REQ primitive (see [34]). The ASC enumeration shall be such that it corresponds to the order of priority (ASC 0 = highest priority, ASC 7 = lowest priority). ASC 0 shall be used in case of Emergency Call or for reasons with equivalent priority. ASCs are numbered according to the order in which the IEs "ASC Setting" appear in the IE "PRACH partitioning", where the first IE "ASC Setting" describes ASC 0, the second IE "ASC Setting" describes ASC 1, etc. At radio bearer setup/reconfiguration each involved logical channel is assigned a MAC Logical channel Priority (MLP) in the range 1,,8. When the MAC sublayer is configured for RACH transmission in the UE, these MLP levels shall be employed for ASC selection on MAC.
8.5.13
Mapping of Access Classes to Access Service Classes
Access Classes shall only be applied at initial access, i.e. when sending an RRC CONNECTION REQUEST message. A mapping between Access Class (AC) and Access Service Class (ASC) shall be indicated by the information element "AC-to-ASC mapping" in System Information Block type 5 or System Information Block type 5bis. The correspondence between AC and ASC shall be indicated as follows.
AC ASC 0-9 st 1 IE 2
nd
10 IE
11 rd 3 IE
12 th 4 IE
13 th 5 IE
14 th 6 IE
15 th 7 IE
In the table, "nth IE" designates an ASC number i in the range 0 - 7 to AC. If the ASC indicated by the "nth IE" is undefined, the UE behaviour is unspecified. For the random access, the parameters implied by the respective ASC shall be employed. In case the UE is member of several ACs it shall select the ASC for the highest AC number. In connected mode, AC shall not be applied.
8.5.14
PLMN Type Selection
Depending on UE configuration, the UE is operating in "ANSI-41 mode" or "GSM-MAP mode".
3GPP
Release 6
258
3GPP TS 25.331 V6.23.0 (2009-09)
8.5.14a Neighbour cells list narrowing for cell reselection

While a UE is camping on a suitable cell, a UE having performed the PLMN identification of the neighbour cells as specified in subclause 8.1.1.6.18 shall narrow the cell list to be used for cell reselection ([4]) to those neighbour cells for which: The PLMN identity is part of the PLMNs that can make a cell suitable as defined in [4].
8.5.15
CFN calculation
The DOFF used in the formulas in this clause concerns the value of IE "Default DPCH Offset Value" received in the message that instructs the UE to enter CELL_DCH state or to perform timing re-initialised hard handover. Subclause 8.5.15.5 is used in FDD to initialise the CFN for MTCH and/or MSCH if the IE "MBMS Soft Combining Timing Offset" is included for an S-CCPCH in MBMS CURRENT CELL P-T-M RB INFORMATION or MBMS NEIGHBOURING CELL P-T-M RB INFORMATION, and if only MTCH and/or MSCH are on the S-CCPCH. Otherwise, subclauses 8.5.15.1 through 8.5.15.4 are used to intialise the CFN.
8.5.15.1
Initialisation for CELL_DCH state after state transition
When the UE receives any of the messages causing the UE to perform a state transition to CELL_DCH, the UE shall set the CFN in relation to the SFN of the first radio link listed in the IE "Downlink information per radio link list" included in that message according to the following formula: for FDD: CFN = (SFN - (DOFF div 38400)) mod 256 where the formula gives the CFN of the downlink DPCH or F-DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. DOFF is determined according to subclause 8.6.6.14. for TDD: CFN = (SFN - DOFF) mod 256.
8.5.15.2
Initialisation in CELL_DCH state at hard handover
When the UE is in CELL_DCH state and receives any of the messages causing the UE to perform a hard handover, the UE shall check the IE "Timing indication" in that message and: 1> if IE "Timing indication" has the value "initialise" (i.e. timing re-initialised hard handover): 2> read SFN on target cell identified by the first radio link listed in the IE "Downlink information per radio link list" included in that message; 2> set the CFN according to the following formula: 3> for FDD: CFN = (SFN - (DOFF div 38400)) mod 256 where the formula gives the CFN of the downlink DPCH or F-DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. 3> for TDD: CFN = (SFN - DOFF) mod 256. 1> if IE "Timing indication" has the value "maintain" (i.e. timing-maintained hard handover), the UE shall keep CFN with no change due to the hard handover, and only increase CFN (mod 256) by 1 every frame.
3GPP
Release 6
259
3GPP TS 25.331 V6.23.0 (2009-09)
8.5.15.3
Initialisation for CELL_FACH
Unless the conditions of subclause 8.15.5.5 are met, when the UE performs cell selection, re-selection or changes to CELL_FACH state the UE shall set CFN for all common or shared channels according to: CFN = SFN mod 256 where the formula gives the CFN of the downlink common or shared channel frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. After the initialisation, the CFN in the UE is increased (mod 256) by 1 every frame.
8.5.15.4
Initialisation after intersystem handover to UTRAN
Upon inter RAT handover to UTRAN the UE shall, regardless of the value received within IE "Timing indication" (if received): 1> read SFN on target cell and set the CFN according to the following formula: 2> for FDD: CFN = (SFN - (DOFF div 38400)) mod 256 where the formula gives the CFN of the downlink DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. 2> for TDD: CFN = (SFN - DOFF) mod 256.
8.5.15.5
Initialisation for MTCH and/or MSCH carried on S-CCPCH that may be soft combined
For FDD, if the IE "MBMS Soft Combining Timing Offset" is included for an S-CCPCH in MBMS CURRENT CELL P-T-M RB INFORMATION or MBMS NEIGHBOURING CELL P-T-M RB INFORMATION, and if only MTCH and/or MSCH are on the S-CCPCH, the UE shall set CFN for the S-CCPCH according to: CFN = (SFN (SCTO div 10ms)) mod 256 where the formula gives the CFN of the downlink S-CCPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN. the SCTO used in the formula is the IE "MBMS Soft Combining Timing Offset". After the initialisation, the CFN in the UE is increased (mod 256) by 1 every frame.
8.5.16
Configuration of CTCH occasions
The CTCH, carrying CBS data is mapped onto only one S-CCPCH. If more than one CTCH is defined, the first CTCH that is configured in the list of S-CCPCHs is the one that is used for CBS data. If the UE is in connected mode it shall ignore any CTCH configuration contained in System Information Block type 6 and use the CTCH configuration contained in System Information Block 5. The CTCH occasions are identified by the first radio frame of the TTI that can contain CTCH data. The CTCH occasions are fixed on the system frame number cycle 0 .. 4095 (i.e. no modulo calculation) and thus repeated cyclically. The CTCH occasions are determined by a set of parameters. MTTI: number of radio frames within the TTI of the FACH used for CTCH N: period of CTCH allocation on S-CCPCH, integer number of radio frames, MTTI N 256, where N is a multiple of MTTI (see [27] and [31]).
3GPP
Release 6
260
3GPP TS 25.331 V6.23.0 (2009-09)
MaxSFN: maximum system frame number = 4095 (see [10]). K: CBS frame offset, integer number of radio frames 0 K N-1 where K is a multiple of MTTI . The CTCH occasions are calculated as follows: SFN = (K + m N), m = 0, 1,..., M, with M chosen that K+MN MaxSFN. The parameters N and K are broadcast as system information. If the IE "Period of BMC scheduling messages (P)" is included in System Information Block type 5 or System Information Block type 5bis then BMC Schedule Messages are transmitted periodically every P CTCH occasions. One BMC Schedule Message may be segmented across more than one CTCH occasion. The CTCH occasions that contain the start of the BMC Schedule Messages are calculated as follows: SFN = (K + m P N), where m is an integer and 0 SFN MaxSFN If the IE "Period of BMC scheduling messages (P)" is not included in system information block type 5 then BMC Schedule Messages could be transmitted in any CTCH occasion.
8.5.17
PRACH selection
For this version of the specification, when a UE selects a cell, the uplink frequency to be used for the initial PRACH transmission shall have a default duplex frequency spacing offset from the downlink frequency that the cell was selected on. The default duplex frequency separation to be used by the UE is specified in [21] for each frequency band (for FDD only). NOTE: The PRACH selection scheme assumes that all PRACHs configured in System Information Block type 5, System Information Block type 5bis and System Information Block type 6 support all (implicitly or explicitly) configurable RLC sizes of the cell, i.e. at least the transport formats corresponding to a single transport block of each applicable RLC size of the cell must be defined for each PRACH.
The UE shall select a "PRACH system information" according to the following rule. The UE shall: 1> select a "PRACH system information" from the ones indicated in the IE "PRACH system information list" in System Information Block type 5 or in System Information Block type 5bis (applicable in Idle Mode and Connected Mode) or System Information Block type 6 (applicable in Connected Mode only), as follows: 2> if in connected mode and System Information Block type 6 is defined and includes PRACH info: 3> compile a list of candidate PRACHs that consists of the PRACH system information listed in System Information Block 6, in the order of appearance as in System Information Block 6. 2>otherwise: 3> compile a list of candidate PRACHs that consists of the PRACH system information listed in System Information Block 5 or in System Information Block 5bis, in the order of appearance as in System Information Block 5 or in System Information Block 5bis, respectively. 2> in FDD: 3> perform RACH TTI selection as specified in subclause 8.5.18.1. 2> in 1.28 Mcps TDD: 3> perform RACH TTI selection according to subclause 8.5.18.2. 2> remove from the list of candidate PRACHs those PRACHs that have a TTI length different from the selected value; 2> select a PRACH randomly from the list of candidate PRACHs as follows: "Index of selected PRACH" = floor (rand * K) where K is equal to the number of candidate PRACH system informations, "rand" is a random number uniformly distributed in the range 0 rand < 1 and "floor" refers to rounding down to nearest integer. The
3GPP
Release 6
261
3GPP TS 25.331 V6.23.0 (2009-09)
candidate PRACH system informations shall be indexed from 0 to K-1. The random number generator is left to implementation. The scheme shall be implemented such that one of the available PRACH system informations is randomly selected with uniform probability. At start-up of the random number generator in the UE the seed shall be dependent on the IMSI of the UE or time, thereby avoiding that all UEs select the same RACH; 2> use the TFCS of the selected PRACH when performing TFC selection (see [15]); 2> reselect the PRACH system information when a new cell is selected. RACH reselection may also be performed after each transmission of a Transport Block Set on RACH. 1> for emergency call, the UE is allowed to select any of the available PRACH system informations. After selecting a PRACH system information, the RRC in the UE shall configure the MAC and the physical layer for the RACH access according to the parameters included in the selected "PRACH system information" IE.
8.5.18
8.5.18.1
Selection of RACH TTI

FDD
In FDD mode, a RACH may employ either 10 or 20 ms TTI. The supported TTI is indicated as a semi-static parameter of the RACH Transport Format in system information. The UE shall select an appropriate TTI length from the RACHs included in the list of candidate PRACH(s) according to the following rule. The UE shall: 1> if only RACHs with one particular TTI length are included in the list of candidate PRACH(s): 2> select this TTI length and proceed as specified in subclause 8.5.17. 1> if both PRACHs with 10ms and 20ms TTI lengths are included in the list of candidate PRACH(s): 2> perform TTI selection as follows: 3> when the UE calculates the initial preamble transmit power ("Preamble_Initial_Power") as specified in subclause 8.5.7: 4> select a TF to be employed for calculation of a transmit power margin as follows: 5> from the TFs supported by all candidate PRACHs keep those which correspond to a single transport block of all configured RLC sizes (i.e., in idle mode, the RLC size applicable for RB0, in connected mode, the RLC sizes configured with explicit "RB mapping info"). If more than a single TF remain applicable, the UE may select any of these. Preferably the UE should select the TF which is intended to be used at the next transmission or, if such information is not available, the TF corresponding to the largest configured RLC size. 4> calculate a transmit power margin, Margin = {min(Maximum allowed UL tx power, P_MAX) max(Preamble_Initial_Power, 2 Preamble_Initial_Power + Pp-m + 10*log10(1 + (d /c) )} where "Maximum allowed UL tx power" is the maximum allowed uplink transmit power indicated in system information (in dBm), and P_MAX is the maximum RF output power of the UE (dBm). The margin shall be calculated for the gain factors d and c of the TF selected in the step above, using 10ms TTI length. NOTE 1: the expression Preamble_Initial_Power + Pp-m + 10*log10(1 + (d /c) ) represents the total RACH message power if the message would be sent after the initial preamble. NOTE 2: For all PRACHs with the same TTI the UTRAN should set each of the IEs "Primary CPICH TX power", "Constant value" to the same value, and within these PRACH configurations, the UTRAN should, for all TFs including a single TB, set each of the IEs "Gain Factor c ", "Gain Factor d" and "Power offset P pm" to the same value. If these guidelines are not followed, the UE behaviour is unspecified.
2
3GPP
Release 6
262
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the resulting "Margin" value is less than 6 dB: 4> select RACH with 20 ms TTI, and proceed as specified in subclause 8.5.17. 3> otherwise, if the last L1 message transmission on PRACH failed (see [15]): 4> the UE may select RACH with 20ms TTI length and proceed as specified in subclause 8.5.17. 3> otherwise: 4> select RACH with 10ms TTI length and proceed as specified in subclause 8.5.17.
8.5.18.2
1.28 Mcps TDD
In 1.28 Mcps TDD, a RACH may be assigned a 5, 10 or 20 ms TTI. If, in one cell, more than one RACH is defined a UE shall select the RACH that is to be used for each transmission according to the following rule: 1> if only RACHs with one particular TTI length are assigned a transport format that is suitable for the transmission of the transport block set: 2> select this RACH's TTI length. 1> if more than one RACHs are assigned a transport format that is suitable for the transmission of the transport block set: 2> select the longest of the TTI lengths of these RACHs.
8.5.19
Secondary CCPCH selection
In UTRAN Connected mode, the UE shall select the Secondary CCPCH according to the following rules: 1> in Cell_DCH state: 2> select Secondary CCPCH according to subclause 8.6.6.4. 1> in Cell_FACH state: 2> if System Information Block type 6 is defined and includes one or more SCCPCH that carry a FACH, compile a list of candidate SCCPCH that consists of these SCCPCH, in the order of appearance in System Information Block type 6. NOTE 1: An SCCPCH carries a FACH if the size of the "FACH/PCH information" list within the IE "Secondary CCPCH system information" exceeds 1 or if the size of this list equals 1 while IE "Secondary CCPCH system information" does not contain an IE "PICH info". 2> otherwise: 3> compile a list of candidate SCCPCH that consists of the SCCPCH(s) included in System Information Block type 5 or System Information Block type 5bis that carry a FACH, in the order of appearance in System Information Block type 5 or System Information Block type 5bis. 2> select an SCCPCH from the list of candidate SCCPCHs based on U-RNTI as follows: "Index of selected SCCPCH" = U-RNTI mod K, where K is equal to the number of candidate SCCPCHs. 1> in Cell_PCH and URA_PCH states: 2> if System Information Block type 6 is defined and includes one or more SCCPCH that carry a PCH, compile a list of candidate SCCPCH that consists of these SCCPCH, in the order of appearance in System Information Block type 6; NOTE 2: An SCCPCH carries a PCH if the IE "Secondary CCPCH system information" contains IE "PICH info"
3GPP
Release 6
263
3GPP TS 25.331 V6.23.0 (2009-09)
2> otherwise compile a list of candidate SCCPCH that consists of the SCCPCH(s) included in System Information Block type 5 or System Information Block type 5bis that that carry a PCH , in the order of appearance in System Information Block type 5 or System Information Block type 5bis; 2> select an SCCPCH from the list of candidate SCCPCHs based on U-RNTI as follows: "Index of selected SCCPCH" = U-RNTI mod K, where K is equal to the number of candidate SCCPCHs. The UE shall set the CFN in relation to the SFN of the current cell according to subclause 8.5.15. The UE shall decode all transport formats on all FACHs multiplexed on the selected S-CCPCH according to its UE capability, as defined in subclauses 8.1.1.6.5 and 8.1.1.6.6, to find blocks adressed to the UE.
8.5.19a Secondary CCPCH and FACH selection for MCCH reception

The UE shall select the Secondary CCPCH for acquiring MCCH information according to the following rules: 1> if System Information Block type 5 or System Information Block type 5bis is defined and includes an S-CCPCH within the IE "Secondary CCPCH system information" including a FACH for which the IE "MCCH configuration information" is included: 2> select that S-CCPCH and FACH for receiving MCCH. 1> otherwise if System Information Block type 5 or System Information Block type 5bis is defined and includes an SCCPCH within the IE "Secondary CCPCH system information MBMS" for which the IE "FACH carrying MCCH" is included: 2> select that S-CCPCH and FACH for receiving MCCH.
8.5.20
Unsupported configuration
The UE should set the variable UNSUPPORTED_CONFIGURATION to TRUE if the received message is not according to the UE capabilities.
8.5.21
Actions related to Radio Bearer mapping
When the UE receives the IE "RB mapping info" and/or the IE "Transport format set", when transport channels, MAC-d flows or E-DCH MAC-d flows are added or deleted, when the UE performs a cell reselection or a state transition, or when the UE releases a RB, the UE shall for each of the configured Radio Bearers: 1> upon moving to CELL_FACH state from CELL_DCH state to initiate a cell update procedure and upon subsequent cell reselections until the first successfully completed cell update procedure, only perform the actions defined in the remainder of this subclause after reception of the CELL UPDATE CONFIRM message; 1> for FDD, select the multiplexing option according to the following: 2> if the UE is in CELL_FACH state: 3> if the RB has a multiplexing option with transport channel type "FACH" for the DL and transport channel type "RACH" for the UL: 4> select this multiplexing option. 2> if the UE is in CELL_DCH state: 3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and MAC-d flow are configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured: 4> select this multiplexing option; else
3GPP
Release 6
264
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and MAC-d flow are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DCH + DSCH" for the DL: 4> the UE behaviour is unspecified; else 3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow is configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DSCH" for the DL: 4> the UE behaviour is unspecified; else 3> if the RB has a multiplexing option with transport channel type "DSCH" for the DL, and the corresponding DSCH transport channel is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DCH" for the DL, and the corresponding DCH transport channel is configured, and with transport channel type "E-DCH" for the UL, and the corresponding E-DCH MAC-d flow is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DCH" for the DL, and the corresponding DCH transport channel is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option. 1> for TDD, select the multiplexing option according to the following: 2> if the UE is in CELL_FACH state: 3> if the RB has the multiplexing options with the transport channel types "FACH" and "DSCH" for the DL, and the corresponding FACH and DSCH transport channels are configured, and with the transport channel types "RACH" and "USCH" for the UL, and the corresponding RACH and USCH transport channels are configured: 4> if both PUSCH and PDSCH are allocated: 5> select the multiplexing option "DSCH" for DL and "USCH" for UL; else 4> if only PUSCH is allocated: 5> select the multiplexing option "FACH" for DL and "USCH" for UL; else 4> if only PDSCH is allocated: 5> select the multiplexing option "DSCH" for DL and "RACH" for UL; else 4> if neither PUSCH nor PDSCH is allocated:
3GPP
Release 6
265
3GPP TS 25.331 V6.23.0 (2009-09)
5> select the multiplexing option "FACH" for DL and "RACH" for UL. 3> if the RB has a single multiplexing option with the transport channel type "FACH" for the DL and the transport channel type "RACH" for the UL: 4> select this multiplexing option; else 3> if the RB has a single multiplexing option with the transport channel type "DSCH" for the DL, and the corresponding DSCH tranfsport channel is configured, and with the transport channel type "USCH" for the UL, and the corresponding USCH transport channel is configured: 4> select this multiplexing option; else 2> if the UE is in CELL_DCH state: 3> if the RB has a multiplexing option with transport channel type "DCH + HS-DSCH" for the DL, and both the corresponding DCH transport channel and MAC-d flow are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DCH + DSCH" for the DL, and both the corresponding DCH and DSCH transport channels are configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "HS-DSCH" for the DL, and the corresponding MAC-d flow is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if the RB has a multiplexing option with transport channel type "DCH" for the DL, and the corresponding DCH transport channel is configured, and with transport channel type "DCH" for the UL, and the corresponding DCH transport channel is configured: 4> select this multiplexing option; else 3> if theRB has a multiplexing option with transport channel type "DSCH" for the DL, and the corresponding DSCH transport channel is configured, and with transport channel "USCH" for the UL, and the corresponding USCH transport channel is configured: 4> select this multiplexing option. 1> configure the MAC with the appropriate transport format set (with computed transport block sizes) for the transport channel used by that RB; 1> in case the selected multiplexing option is a multiplexing option on E-DCH: 2> the set of RLC sizes that apply to the logical channel used by that RB consists of all RLC PDU sizes listed in the IE "RLC PDU size list" in the RB mapping info for E-DCH. 1> else: 2> determine the sets of RLC sizes that apply to the logical channels used by that RB, based on the IEs "RLC size list" and/or the IEs "Logical Channel List" included in the applicable "Transport format set" (either the ones received in the same message or the ones stored if none were received); 1> in case the selected multiplexing option is a multiplexing option on RACH: 2> ignore the RLC size indexes that do not correspond to any RLC size within the Transport Format Set stored for RACH. 2> if there is no remaining RLC size index corresponding to an RLC size within the Transport Format Set stored for RACH:
3GPP
Release 6
266
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the variable INVALID_CONFIGURATION to TRUE. 1> if RACH is the transport channel to be used on the uplink, if that RB has a multiplexing option on RACH and if it is using AM: 2> apply the largest size amongst the ones derived according to the previous bullet for the RLC size (or RLC sizes in case the RB is realised using two logical channels) for the corresponding RLC entity. NOTE: The IE "RB mapping info" is only included in the IE "Predefined RB configurations" in system information when used for Inter-RAT handover to UTRAN and there is no AM RLC size change involved in this case.
1> if that RB is using AM and the RLC size applicable to the uplink logical channel transporting data PDUs is different from the one derived from the previously stored configuration; and 1> none of the following conditions is met: the RLC size change is caused by a CELL UPDATE CONFIRM and the CELL UPDATE CONFIRM message includes the IE "Downlink counter synchronisation info". the RLC size change is caused by a reconfiguration message, and a cell update procedure occurs during the reconfiguration procedure and the CELL UPDATE CONFIRM message includes the IE "Downlink counter synchronisation info". the RLC size change is caused by a reconfiguration message, and a cell update procedure occurs during this reconfiguration procedure and the CELL UPDATE CONFIRM message includes the IE "RLC re-establish indicator" being set to TRUE for the corresponding radio bearer.
2> if the RLC size change is caused by a reconfiguration message or a CELL UPDATE CONFIRM; and 2> the IE "one sided RLC re-establishment" is included in that message and is set to TRUE: 3> re-establish the transmitting side of the corresponding RLC entity. 2> else: 3> re-establish the corresponding RLC entity. 2> configure the corresponding RLC entity with the new uplink RLC size; 2> for each AM RLC radio bearer in the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS whose RLC size is changed; and 2> for each AM RLC signalling radio bearer in the CN domain as indicated in the IE "CN domain identity" in the variable LATEST_CONFIGURED_CN_DOMAIN whose RLC size is changed: 3> if the IE "Status" in the variable CIPHERING_STATUS of this CN domain is set to "Started": 4> if the information causing the RLC re-establishment was included in system information: 5> set the HFN values for the corresponding RLC entity equal to the value of the IE "START" for this CN domain that will be included in the CELL UPDATE message following cell reselection. NOTE: Since the UE cannot predict the START value at the time of the next CELL UPDATE transmission in the future, UTRAN should desist from changing the RLC size for a signalling radio bearer within a cell. Other than this case the change in RLC size for a signalling radio bearer is known to the UE when reading system information following cell reselection. 4> if the RLC re-establishment is caused by a CELL UPDATE CONFIRM: 5> if the whole RLC entity was re-established: 6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain. 5> if only the transmitting side of the RLC entity was re-established:
3GPP
Release 6
267
3GPP TS 25.331 V6.23.0 (2009-09)
6> set the HFN value for the corresponding RLC entity in the uplink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain. 4> if the RLC re-establishment is caused by a reconfiguration message: 5> if the whole RLC entity was re-established: 6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain. 5> if only the transmitting side of the RLC entity was re-established: 6> set the HFN value for the corresponding RLC entity in the direction uplink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain. NOTE1: If the UTRAN modifies the RLC size for RB2 on any reconfiguration message or Cell Update Confirm message, the UE behaviour is unspecified in this version of the specification. NOTE2: The UE cannot rely on the configured Transport Formats to determine the RLC sizes to be used in downlink for a particular logical channel. This size can be signalled explicitly in the RLC Info IE. 1> if that RB is using UM: 2> indicate the largest RLC size applicable for uplink to the corresponding RLC entity. 1> configure MAC multiplexing according to the selected multiplexing option (MAC multiplexing shall only be configured for a logical channel if the transport channel it is mapped on according to the selected multiplexing option is the same as the transport channel another logical channel is mapped on according to the multiplexing option selected for it); 1> configure the MAC with the logical channel priorities according to selected multiplexing option; 1> configure the MAC with the set of applicable RLC Sizes for each of the logical channels used for that RB; 1> if there is no multiplexing option applicable for the transport channels and MAC-d flows to be used: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if there is more than one multiplexing option applicable for the transport channels or MAC-d flows to be used: 2> set the variable INVALID_CONFIGURATION to TRUE. If upon cell re-selection or upon moving to CELL_FACH state from CELL_DCH state to initiate cell update procedure the UE sets variable INVALID_CONFIGURATION to TRUE as a result of the actions defined in this subclause, the UE should: 1> move to idle mode; 1> release (locally) the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and the established radio access bearers (as stored in the variable ESTABLISHED_RABS) and indicate this to upper layers; 1> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2.
8.5.22
NOTE:
Actions when entering another RAT from connected mode

This section does not apply when entering GERAN Iu mode from UTRAN connected mode.
When entering another RAT from connected mode (due to Inter-RAT handover from UTRAN, Inter-RAT cell change order from UTRAN or Inter-RAT cell reselection from UTRAN), after successful completion of the procedure causing the transition to the other RAT, the UE shall:
3GPP
Release 6
268
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the USIM is present, for each CN domain: 2> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: 3> set the START value for this domain to zero and; 3> store this START value for this domain in the USIM; 2> else: 3> store the current START value for every CN domain in the USIM [50]. NOTE: Prior to storing the START value, the UE should calculate this START value according to subclause 8.5.9.
1> if the SIM is present, for each CN domain: 2> if a new security key was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: 3> set the START value for this domain to zero and; 3> store this START value for this domain in the UE. 2> else: 3> store the current START value for this CN domain in the UE. NOTE: Prior to storing the START value, the UE should calculate this START value according to subclause 8.5.9.
8.5.23
Measured results on RACH
When transmitting an uplink RRC message, the UE shall: 1> if the uplink RRC message is an RRC CONNECTION REQUEST message: 2> if the IE "Intra-frequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" are included in System Information Block type 11: 3> include a measurement report in the IE "Measured results on RACH", as specified in the IE "Intrafrequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" in System Information Block type 11. 2> if the IE "Inter-frequency RACH reporting information" is included in System Information Block type 11: 3> if, at the time the message is to be sent, valid measurements are available; and 3> there is one or more cells for which the quantity, indicated by the IE "Reporting quantity" in the IE "Interfrequency RACH reporting information, exceeds the threshold specified by the IE "Inter-frequency RACH reporting threshold": 4> include a measurement report in the IE "Measured results on RACH"; 4> include the cells for which the quantity, indicated by the IE "Reporting quantity" in the IE "Interfrequency RACH reporting information", exceeds the threshold specified by the IE "Inter-frequency RACH reporting threshold"; 4> set the IE "Inter-frequency cell indication- SIB11" to the following value: Value_Tag MOD 2, with Value_Tag corresponding to the value tag of System Information Block Type 11; 4> set the IE "Inter-frequency cell indication- SIB12" to any value. 1> for any other uplink RRC message which optionally includes the IE "Measured results on RACH":
3GPP
Release 6
269
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the IE "Intra-frequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" are included in System Information Block type 12 (or "System Information Block Type 11", if these IEs are not included in the broadcast "System Information Block Type 12" or "System Information Block Type 12" is not being broadcast). 3> include a measurement report in the IE "Measured results on RACH", as specified in the IE "Intrafrequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" in System Information Block type 12 (or "System Information Block Type 11" if these IEs are not included in the broadcast "System Information Block Type 12" or "System Information Block Type 12" is not being broadcast). 2> if the IE "Inter-frequency RACH reporting information" is included in "System Information Block type 12" (or "System Information Block Type 11" if this IE is not included in the "System Information Block Type 12" or if "System Information Block Type 12" is not being broadcast): 3> if, at the time the message is to be sent, valid measurements are available; and 3> there is one or more cells for which the quantity, indicated by the IE "Reporting quantity" in the IE "Interfrequency RACH reporting information, exceeds the threshold specified by the IE "Inter-frequency RACH reporting threshold": 4> include a measurement report in the IE "Measured results on RACH"; 4> include the cells for which the quantity, indicated by the IE "Reporting quantity" in the IE "Interfrequency RACH reporting information", exceeds the threshold specified by the IE "Inter-frequency RACH reporting threshold"; 4> set the IE "Inter-frequency cell indication- SIB11" to the following value: Value_Tag MOD 2, with Value_Tag corresponding to the value tag of System Information Block Type 11; 4> if "System Information Block Type 12" is being broadcast: 5> set the IE "Inter-frequency cell indication- SIB12" to the following value: Value_Tag MOD 2, with Value_Tag corresponding to the value tag of System Information Block Type 12. 4> else: 5> set the IE "Inter-frequency cell indication- SIB12" to any value. 1> include in the IE "Measured results on RACH" all requested reporting quantities for cells for which measurements are reported. NOTE: The UE only includes measurement results for neighbour cells for which valid measurements are available at the time the message is sent. At cell access following selection or reselection to a cell, the UE may not have had sufficient time to obtain valid measurement results for neighbour cells.
1> for messages transmitted on CCCH, take care that the maximum allowed message size is not exceeded when forming the IE "Measured results on RACH", i.e. limit the number of included neighbour cells or if required omit the IE "Measured results on RACH" altogether. When limiting the number of included neighbouring cells, the number of inter-frequency cells should be limited first i.e. inter-frequency cells should be omitted before limiting the number of intra- frequency cells. If the IE "Measured results on RACH" is present in the message, the UTRAN should extract the contents to be used for radio resource control.
8.5.24
Change of PLMN while in RRC connected mode
If the UE camps on an acceptable cell to obtain limited service while in RRC connected mode the UE shall: 1> keep the RRC connection and its behaviour, while camping on an acceptable cell as if in Idle mode in that PLMN; 1> if the UE re-enters "in service area" in a suitable cell, or cannot maintain limited service (i.e. cannot find any acceptable cell of any PLMN), the UE shall resume its RRC Connected mode behaviour as if it had not camped on any cell whilst being in "out of service area".
3GPP
Release 6
270
3GPP TS 25.331 V6.23.0 (2009-09)
The UE shall: 1> if the NAS indicates the selection of a new PLMN resulting from manual- or automatic mode PLMN selection [25] while the UE is in RRC connected mode; or 1> if the UE attempts transmission on an acceptable cell while the UE is in RRC connected mode (i.e. to initiate emergency call), the UE shall: 2> move to idle mode; 2> release all dedicated resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; and 2> perform actions specified in subclause 8.5.2 when entering idle mode from connected mode. NOTE: NAS can inform AS about a new selected PLMN as a result of a PLMN selection (manual- or automatic mode PLMN selection (see [25])), or as a result of network signalling (after inter-RAT handover or interPLMN SRNS relocation). Only in the first case (manual- or automatic mode PLMN selection), this will result in an immediate RRC connection release.
8.5.25
Actions related to HS_DSCH_RECEPTION variable
The variable HS_DSCH_RECEPTION shall be set to "TRUE" only when all the following conditions are met: 1> for FDD and 1.28 Mcps TDD: 2> the UE is in CELL_DCH state. 1> for 3.84 Mcps TDD: 2> a dedicated physical channel is allocated to the UE in the uplink. 1> the variable H_RNTI is set; 1> the UE has a stored IE "HS-SCCH info"; 1> the UE has a stored IE "HARQ info"; 1> for FDD: 2> one of the radio links in the active set is configured as the serving HS-DSCH radio link; 2> the UE has stored the following IEs: IE "Measurement Feedback Info"; IE "Uplink DPCH Power Control Info" including stored ACK, NACK and Ack-NACK Repetition factor.
1> for 3.84 Mcps TDD, the UE has stored the IE "HS-PDSCH Timeslot Configuration" and either of the following conditions are met: 2> a dedicated physical channel is allocated to the UE in the downlink; 2> the UE has stored Dhs-sync. 1> for 1.28 Mcps TDD, the UE has stored the following IE: IE "HS-PDSCH Midamble Configuration".
1> there is at least one RB mapped to HS-DSCH;
3GPP
Release 6
271
3GPP TS 25.331 V6.23.0 (2009-09)
1> at least for one of the RBs mapped to HS-DSCH, there is at least one MAC-hs queue (including the IE "MAC-d PDU size Info") configured for the concerning MAC-d flow; NOTE 1: To enable or disable HS-DSCH reception, the UTRAN has the possibility to add/remove the concerning HS-DSCH related RB mapping options, add/remove the concerning MAC-d flows or, for FDD, add/remove the serving HS-DSCH radio link or, for TDD add/remove H-RNTI upon hard handover. NOTE 2: If HS_DSCH_RECEPTION is set to "TRUE" and a reconfiguration, an inter-RAT handover from UTRAN, or a cell change order procedure is initiated, the UE checks the conditions only when the reconfiguration, inter-RAT handover from UTRAN, or cell change order procedure is successfully completed. Doing so ensures that, in case of failure in the reconfiguration, inter-RAT handover from UTRAN, or cell change order procedure, the UE can return to the old configuration as if the message was not received, e.g. without performing a MAC-HS reset. If any of the above conditions is not met and the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall: 1> set the variable HS_DSCH_RECEPTION to FALSE; 1> stop any HS_SCCH reception procedures; 1> stop any HS-DSCH reception procedures; 1> clear the variable H_RNTI and remove any stored H-RNTI; 1> reset the MAC-hs entity [15]; 1> release all HARQ resources; 1> no long consider any radio link to be the HS-DSCH serving radio link; 1> for 3.84 Mcps TDD, if no downlink DPCH is assigned the UE shall clear the uplink DPCH configuration and initiate the Cell Update procedure according to subclause 8.3.1, cause "radio link failure". NOTE 3: If configured for HS-DSCH and not explicitly indicated as being cleared, the UE will have still stored the IEs "HARQ info", "Added or Reconfigured MAC-d flow", "RB mapping Info" and "Downlink HS-PDSCH information". Whenever the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall: 1> perform HS_SCCH reception procedures according to the stored HS-SCCH configuration as stated in: 2> subclause 8.6.6.33 for the IE "HS-SCCH Info". 1> perform HS-DSCH reception procedures according to the stored HS-PDSCH configuration as stated in: 2> subclause 8.6.3.1b for the IE "H-RNTI"; 2> subclause 8.6.5.6b for the IE "HARQ info"; 2> subclause 8.6.6.34 for the IE "Measurement Feedback Info". Whenever the variable HS_DSCH_RECEPTION is set to FALSE, the UE shall: 1> not perform HS_SCCH reception procedures; 1> not perform HS-DSCH reception procedures.
8.5.26
Service prioritisation
If the UE detects an MBMS service reception inability as specified in subclause 8.5.30, the UE may: 1> request upper layers to prioritise the services and to initiate release of non- prioritised services that may cause interruption in the reception of the prioritised services; 1> if reception of the prioritised MBMS service is inhibited by one or more MBMS service(s) provided via a p-t-p radio bearer:
3GPP
Release 6
272
3GPP TS 25.331 V6.23.0 (2009-09)
2> request UTRAN to terminate these MBMS service(s) using the MBMS MODIFICATION REQUEST message as specified in subclause 8.7.6. NOTE: The termination of MBMS services is performed by RRC procedures, while clearing of non- MBMS services is performed by upper layers.
8.5.27
MBMS frequency selection
The UE shall perform the MBMS frequency layer selection procedure upon receiving the IE "MBMS Preferred frequency information", when specified explicitly e.g. as in subclause 8.6.9.2, or when the priority for an MBMS service as indicated by upper layers changes. The UE shall: 1> if there exist two or more preferred frequencies for services included in variable MBMS_ACTIVATED_SERVICES: 2> request from upper layers the priorities of the different MBMS services included in variable MBMS_ACTIVATED_SERVICES for which a preferred frequency has been received. 1> if the UE is in idle mode: 2> if a preferred frequency layer applies for a service included in variable MBMS_ACTIVATED_SERVICES: 3> select the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists as the preferred frequency. 1> if the UE is in CELL_FACH, CELL_PCH or URA_PCH state; and 1> if there exists one or more preferred frequencies for services included in variable MBMS_ACTIVATED_SERVICES and the variable MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED is set to FALSE: 2>if the IE "RAB information" in the variable ESTABLISHED_RABS is not empty: 3> if the current frequency is the frequency corresponding with the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists: 4> select the current frequency as the preferred frequency. 3> else: 4> if there exists one or more preferred frequencies for services included in variable MBMS_ACTIVATED_SERVICES for which the IE "MBMS PL Service Restriction Information" has not been received in the MBMS GENERAL INFORMATION message: 5> select the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists for which the IE "MBMS PL Service Restriction Information" has not been received in the MBMS GENERAL INFORMATION message as the preferred frequency. 2> else: 3> select the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists as the preferred frequency. 1> if the UE is in CELL_DCH: 2> if there exists one or more preferred frequencies for services included in variable MBMS_ACTIVATED_SERVICES and the variable MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED is set to FALSE: 3> if the current frequency does not correspond to the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists:
3GPP
Release 6
273
3GPP TS 25.331 V6.23.0 (2009-09)
4> select as preferred frequency the preferred frequency indicated for the MBMS service(s) prioritised most by upper layers for which a preferred frequency exists for which the IE "MBMS PL Service Restriction Information" is not included in the MBMS GENERAL INFORMATION message; 4> if a preferred frequency has been selected and the current frequency is different from the selected frequency: 5> request UTRAN to be moved to the preferred frequency by means of the MBMS MODIFICATION REQUEST message as specified in subclause 8.7.6; 5> if the variable MBMS_PREV_FREQUENCY_INFO is empty: 6> upon receiving a request to move to the requested preferred frequency, store the frequency information of the frequency on which the UE was operating prior to the hard-handover to the preferred frequency in the variable MBMS_PREV_FREQUENCY_INFO. 1> if a preferred frequency has been selected: 2> if the UE is not in CELL_DCH state: 3> apply the cell-reselection procedure as described in [4], using the received "MBMS Preferred frequency information" applicable to the selected frequency; 3> if the UE re-selects to a cell on the indicated preferred frequency: 4> if HCS is not used, and the IE "Qoffmbms" is not present for the MBMS preferred frequency: 5> consider the cells on the MBMS preferred frequency having a Qoffmbms equal to "infinity". 4> if HCS is used, and the IE "HCS_OFFmbms" is not present for the MBMS preferred frequency: 5> consider the cells on the MBMS preferred frequency having the highest HCS priority level. 4> if the UE is in CELL_FACH, CELL_PCH or URA_PCH: 5> act according to subclause 8.3.1.2. 4> if the selected frequency is different to the frequency on which the UE was previously operating; and 4> if the variable MBMS_PREV_FREQUENCY_INFO is empty: 5> store the frequency information of the frequency on which the UE was operating prior to cellreselection to the preferred frequency in the variable MBMS_PREV_FREQUENCY_INFO. 4> apply the MCCH acquisition procedure, as specified in subclause 8.7.2. 1> else: 2> if the UE is not in CELL_DCH state: 3> stop applying any "MBMS Preferred frequency information"; 3> if the UE is not redirected to another frequency; and 3> if the UE does not decide to receive an MBMS service; and 3> if the variable MBMS_PREV_FREQUENCY_INFO is not empty: 4> if any frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 5> select a suitable UTRA cell in that frequency; 5> if no suitable UTRA cell in that frequency is found: 6> select a suitable UTRA cell in another frequency.
3GPP
Release 6
274
3GPP TS 25.331 V6.23.0 (2009-09)
4> if no frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 5> select a frequency randomly among the inter-frequencies indicated in SIB11 or SIB12: 6> select a suitable UTRA cell in the selected frequency; 6> if no suitable UTRA cell in the selected frequency is found: 7> select a suitable UTRA cell in another frequency. 4> clear the variable MBMS_PREV_FREQUENCY_INFO. NOTE: The UE is only required to acquire the relevant SIB11 or SIB12, according to what is specified in subclauses 8.1.1.6.11 and 8.1.1.6.12.
8.5.28
Actions related to E_DCH_TRANSMISSION variable
The variable E_DCH_TRANSMISSION shall be set to "TRUE" only when all the following conditions are met: 1> the UE is in CELL_DCH state; 1> the variable E_RNTI includes either the Primary E-RNTI or the Secondary E-RNTI or both the Primary and the Secondary E-RNTI; 1> the UE has stored the following IEs: IE "E-DCH Transmission Time Interval"; IE "HARQ info for E-DCH"; IE "E-DCH info", including the IE "E-DPCCH info" and the IE "E-DPDCH info". one of the radio links in the active set is configured as the serving E-DCH radio link, and for this radio link the UTRAN has configured the IE "E-HICH configuration" and the IE "E-AGCH info".
1> there is at least one logical channel mapped to E-DCH for which: 2> the corresponding E-DCH MAC-d flow is configured, i.e. the IEs "E-DCH MAC-d flow power offset" and "E-DCH MAC-d flow maximum number of retransmissions", and the transmission grant type are configured. If any of the above conditions is not met and the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall: 1> set the variable E_DCH_TRANSMISSION to FALSE; 1> stop any E-AGCH, E-HICH and E-RGCH reception procedures; 1> stop any E-DPCCH and E-DPDCH transmission procedures; 1> clear the variable E_RNTI; 1> act as if the IE "MAC-es/e reset indicator" was received and set to TRUE; 1> release all E-DCH HARQ resources; 1> no longer consider any radio link to be the serving E-DCH radio link. Whenever the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall: 1> perform E-AGCH reception procedures according to the stored E_AGCH configuration as stated in: 2> subclause 8.6.3.14 for the IE "New Primary E-RNTI" and the IE "New Secondary E-RNTI". 1> perform E-HICH reception procedures for all radio links in the E-DCH active set; 1> perform E-RGCH reception procedures for all radio links in the active set for which an E-RGCH configuration has been provided;
3GPP
Release 6
275
3GPP TS 25.331 V6.23.0 (2009-09)
1> perform E-DPCCH transmission procedures according to the stored E-DPCCH configuration as stated in: 2> subclause 8.6.6.37 for the IE "E-DPCCH Info"; 1> perform E-DPDCH transmission procedures according to the stored E-DPDCH configuration as stated in: 2> subclause 8.6.5.16 for the IE "E-DCH Transmission Time Interval"; 2> subclause 8.6.5.17 for the IE "HARQ info for E-DCH". 2> subclause 8.6.6.37 for the IE "E-DPDCH Info". 1> inclusion of MAC-d PDU's in a MAC-e PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall: 2> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18). 1> inclusion of MAC-d PDU's in a MAC-e PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall: 2> be performed in accordance with the received scheduling grant on E-AGCH/E-RGCH (see [15]); and 2> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37). Whenever the variable E_DCH_TRANSMISSION is set to FALSE, the UE shall: 1> not perform E-AGCH, E-HICH and E-RGCH reception procedures; 1> not perform E-DPCCH and E-DPDCH transmission procedures.
8.5.29
MBMS modification period identity calculation

MP identity= (SFNMP div MPlen) mod 2
The UE shall calculate the identity of a Modification period as follows:
With SFNMP being the SFN corresponding with the frame in which the concerned Modification Period starts MPlen being the length of the Modification Period, that is indicated by the IE "Modification period coefficient" that is included in System Information Block type 5 and 5bis.
8.5.30
Detecting MBMS service reception inability
The UE may detect that it becomes incapable of receiving all services it is interested in at any time due to implementation specific constraints as well as upon state transitions, service / session start, service / session stop, service reconfiguration e.g. transfer mode change and preferred frequency layer changes or whenever there are changes concerning the subset of services that it has selected to receive. When evaluating its MBMS service reception abilities, the UE shall: 1> consider that MBMS services, for which a preferred frequency layer is specified, are available only on the concerned frequency; 1> consider that MBMS services, for which no preferred frequency layer is specified are available on all frequencies; 1> consider non- MBMS services to be available on all frequencies unless specified otherwise in the following; 1> if the variable MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED is set to TRUE: 2> consider the established non-MBMS services not to be available on any MBMS preferred frequency. 1> if the IE "MBMS PL Service Restriction Information" is included in the MBMS GENERAL INFORMATION message for the MBMS preferred frequency the UE is considering to select to: 2> consider non-MBMS services not to be available on the concerned MBMS preferred frequency.
3GPP
Release 6
276
3GPP TS 25.331 V6.23.0 (2009-09)
If the UE is unable to receive the MBMS and the non-MBMS services it is interested in, the UE shall: 1> detect an MBMS service reception inability.
8.6
8.6.1
8.6.1.1
Generic actions on receipt and absence of an information element

CN information elements
Void
8.6.1.2
CN information info
If the IE "CN information info" is present in a message, the UE shall: 1> if the IE "Primary PLMN Identity" is present: 2> forward the content of the IE "Primary PLMN identity" to upper layers. 1> else: 2> if the IE "PLMN Identity" is present: 3> forward the content of the IE "PLMN identity" to upper layers. 1> if present, forward the content of the IE "CN common GSM-MAP NAS system information" to upper layers; 1> if the IE "CN domain related information" is present: 2> forward each occurrence of the IE "CN domain specific GSM-MAP NAS system info" together with the IE "CN domain identity" to upper layers. 2> if an IE "CN domain specific GSM-MAP NAS system info" is not present for a particular CN domain: 3> indicate to upper layers that no CN system information is available for that CN domain. NOTE: If UTRAN at SRNS relocation includes and sets the IE "Primary PLMN identity" to the PLMN identity signalled in RANAP RELOCATION REQUEST [57], the UTRAN should also set the IE "PLMN identity" to the PLMN identity in the IE "PLMN Identity" of the Master Information Block transmitted in the cell(s) used by the UE after completed SRNS relocation.
8.6.1.3
Signalling connection release indication
If the IE "Signalling Connection release indication" is present in a message, the UE shall: 1> if all radio access bearers for the CN domain identified with the value of the IE "Signalling Connection release indication" would have been released in the variable ESTABLISHED_RABS after processing of the received message: 2> indicate release of the signalling connection identified with the value of the IE "Signalling Connection release indication" to the upper layers; 2> remove the signalling connection identified with the value of the IE "Signalling Connection release indication" from the variable ESTABLISHED_SIGNALLING_CONNECTIONS. 1> if radio access bearers for the CN domain identified with the value of the IE "Signalling Connection release indication" would remain in the variable ESTABLISHED_RABS after processing of the received message: 2> set the variable INVALID_CONFIGURATION to TRUE.
3GPP
Release 6
277
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.2
8.6.2.1
The UE shall:
UTRAN mobility information elements

URA identity
1> if the IE "URA identity" is included in a received message: 2> if the IE "RRC State Indicator" is included and set to "URA_PCH": 3> store this URA identity in the variable URA_IDENTITY; 3> after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read system information block type 2 in the selected cell; 3> if the stored URA identity in the variable URA_IDENTITY is not included in the list of URA identities in System Information Block type 2 in the selected cell, the list of URA identities in system information block type 2 is empty or if the system information block type 2 can not be found, a confirmation error of URA identity list has occurred: 4> if no URA update procedure is ongoing: 5> initiate a URA update procedure after entering URA_PCH state; see subclause 8.3.1.2. 4> if a URA update procedure is ongoing: 5> take actions as specified in subclause 8.3.1.10. 1> if the IE "URA identity" is not included in a received message: 2> if the IE "RRC State Indicator" is included and set to " URA_PCH": 3> after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read System Information Block type 2 in the selected cell; 3> if System Information Block type 2 in the selected cell contains a single URA identity: 4> store this URA identity in the variable URA_IDENTITY. 3> if System Information Block type 2 of the selected cell contains more than one URA identity, the list of URA identities in system information block type 2 is empty or if the system information block type 2 can not be found, a confirmation error of URA identity list has occurred: 4> if no URA update procedure is ongoing: 5> initiate a URA update procedure after entering URA_PCH state, see subclause 8.3.1.2. 4> if a URA update procedure is ongoing: 5> take actions as specified in subclause 8.3.1.10.
8.6.2.2
Mapping info
If the IE "Mapping info" is received, the UE shall in this version of the specification: 1> ignore the contents of this IE.
8.6.3
8.6.3.1
UE information elements
Activation time
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
3GPP
Release 6
278
3GPP TS 25.331 V6.23.0 (2009-09)
1> let the "reference CCTrCH" be defined as the CCTrCh that includes any transport channel or is associated with any physical channel which is being added, re-configured or removed, or, in the case of HS-DSCH, the CCTrCh including the associated DCH; 1> if the frame boundary immediately before the frame with the CFN (Connection Frame Number) value indicated by the IE "Activation Time" is at the TTI boundary common to all the transport channels that are multiplexed onto the reference CCTrCh: 2> select that frame boundary as the activation time T. 1> else: 2> select the next TTI boundary, which is common to all the transport channels that are multiplexed onto the reference CCTrCh, after the frame with the CFN (Connection Frame Number) value indicated by the IE "Activation Time", as the activation time T. 1> if the IE "Delay restriction flag" is received and activation time T is more than 128 frames from the CFN at which the message was received: 2> choose an activation time T as soon as possible after reception of the message, respecting the performance requirements in subclause 13.5, which is common to all the transport channels that are multiplexed onto the reference CCTrCh. NOTE: If the UE receives a message containing the IE "Delay restriction flag" and that message causes a transport channel or physical channel reconfiguration of the reference CCTrCH then the UE behaviour is not specified.
1> at the activation time T: 2> for a physical channel reconfiguration other than an HS-DSCH related reconfiguration, caused by the received message: 3> release the physical channel configuration, which was present before T; 3> initiate the establishment of the physical channel configuration as specified for the physical channel information elements in the received message as specified elsewhere. 2> for an HS-DSCH related reconfiguration in FDD or 1.28 Mcps TDD caused by the received message: 3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T; 3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration. 2> for an HS-DSCH related reconfiguration in 3.84 Mcps TDD caused by the received message: 3> start using, at activation time T, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration. 2> for actions, other than a physical channel reconfiguration, caused by the received message: 3> perform the actions for the information elements in the received message as specified elsewhere. NOTE: In FDD an "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is the default value "Now", the UE shall: 1> choose an activation time T as soon as possible after the reception of the message, respecting the performance requirements in subclause 13.5; 1> at the activation time T: 2> perform the actions for the information elements in the received message as specified elsewhere.
3GPP
Release 6
279
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
In FDD, if the UE was in idle mode or CELL_FACH state upon reception of the message, regardless of the state the UE enters after reception of the message, and the value of the IE "Activation time" in the received message is different from "Now", the UE behaviour is unspecified. In TDD, if the UE was in idle mode or CELL_FACH state upon reception of the message, the value of the IE "Activation time" in the received message is relative to the CFN associated with the cell from which the message was received.
8.6.3.1a
CN domain specific DRX cycle length coefficient
The UE updates CN domain specific DRX cycle length coefficient as specified in [4]. The UE shall use it to calculate the CN domain specific DRX cycle length, according to the following: 1> set k to the value of the IE "CN domain specific DRX cycle length coefficient". 1> store the result of MAX(2 , PBP), where PBP is the Paging Block Periodicity, as the CN domain specific DRX cycle length for the CN domain indicated by the IE "CN domain identity". For FDD PBP=1. The UE shall determine its idle mode paging occasions and PICH monitoring occasions for that CN domain, according to [4], based on the stored CN domain specific DRX cycle length, when using DRX in idle mode.
k
8.6.3.1b
H-RNTI
If the IE "New H-RNTI" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall: 1> store the value in the variable H_RNTI; 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. If the message that triggers the HS_DSCH_RECEPTION variable to change value from FALSE to TRUE does not contain the IE "New H-RNTI": 1> the UE behaviour is not defined. When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall: 1> use the value of the variable H_RNTI as UE identity in the HS-SCCH reception procedure in the physical layer.
8.6.3.2
UTRAN DRX Cycle length coefficient
If the IE "UTRAN DRX cycle length coefficient" is present, the UE shall use it to calculate the UTRAN DRX cycle length, according to the following: 1> set k to the value of the IE "UTRAN DRX cycle length coefficient"; 1> store the result of MAX(2k,PBP), where PBP is the Paging Block Periodicity, as the DRX cycle length. The UE shall determine its connected mode paging occasions and PICH monitoring occasions in the same way as for idle mode, according to [4]. The DRX cycle length to use in connected mode is defined in [4].
8.6.3.3
Generic state transition rules depending on received information elements
The IE "RRC State Indicator" indicates the state the UE shall enter. The UE shall enter the state indicated by the IE "RRC State Indicator" even if the received message includes other IEs relevant only for states other than indicated by the IE "RRC State Indicator". E.g. if the RRC state indicator is set to CELL_FACH while other IEs provide information about a configuration including dedicated channels, the UE shall enter CELL_FACH state. If however the UE has no information about the configuration corresponding to the state indicated by the IE "RRC State Indicator", it shall consider the requested configuration as invalid. The UE shall, if the IE "RRC State Indicator" in the received message has the value:
3GPP
Release 6
280
3GPP TS 25.331 V6.23.0 (2009-09)
1> "CELL_FACH": 2> enter CELL_FACH state as dictated by the procedure governing the message received. 1> "CELL_DCH": 2> if neither DPCH is assigned in the message nor is the UE in CELL_DCH: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> else: 3> enter CELL_DCH state as dictated by the procedure governing the message received. 1> "CELL_PCH": 2> if the received message is RRC CONNECTION SETUP and IE "RRC State Indicator" is set to CELL_PCH: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> else: 3> enter CELL_PCH state as dictated by the procedure governing the message received. 1> "URA_PCH": 2> if the received message is RRC CONNECTION SETUP and IE "RRC State Indicator" is set to URA_PCH: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> else: 3> enter URA_PCH state as dictated by the procedure governing the message received.
8.6.3.4
Ciphering mode info
The IE "Ciphering mode info" defines the new ciphering configuration. At any given time, the UE needs to store at most two different ciphering configurations (keyset and algorithm) per CN domain at any given time in total for all radio bearers and three configurations in total for all signalling radio bearers. If the IE "Ciphering mode info" is present and if the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to TRUE, the UE shall: 1> ignore this second attempt to change the ciphering configuration; and 1> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to TRUE. If the IE "Ciphering mode info" is present and if the IE "Reconfiguration" in the variable CIPHERING_STATUS is set to FALSE, the UE shall: 1> if none of the IE "Status" in the variable CIPHERING STATUS has the value "Started", and this IE "Ciphering mode info" was included in a message that is not the message SECURITY MODE COMMAND; or 1> if the IE "Ciphering Mode Info" was received in the message SECURITY MODE COMMAND and there does not exist exactly one ciphering activation time in the IE "Radio bearer downlink ciphering activation time info" for each established RLC-AM and RLC-UM radio bearers included in the IE "RB information" in the IE "ESTABLISHED_RABS" for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; or 1> if the IE "Ciphering Mode Info" was received in the message SECURITY MODE COMMAND and the IE "Ciphering activation time for DPCH" is not included in the message, and there exist radio bearers using RLCTM according to the IE "RB information" in the IE "ESTABLISHED_RABS" for the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; or 1> if the IE "Ciphering Mode Info" was received in the message SECURITY MODE COMMAND and there does not exist exactly one ciphering activation time in the IE "Radio bearer downlink ciphering activation time info"
3GPP
Release 6
281
3GPP TS 25.331 V6.23.0 (2009-09)
for each established signalling radio bearer included in the IE "Signalling radio bearer information" in the IE "ESTABLISHED_RABS": 2> ignore this attempt to change the ciphering configuration; 2> set the variable INVALID_CONFIGURATION to TRUE; 2> perform the actions as specified in subclause 8.1.12.4c. 1> set the IE "Reconfiguration" in the variable CIPHERING_STATUS to TRUE; 1> set the IE "Status" in the variable CIPHERING_STATUS of the CN domains for which the IE "Status" of the variable SECURITY_MODIFICATION is set to "Affected" to "Started"; 1> apply the new ciphering configuration in the lower layers for all RBs that belong to a CN domain for which the IE "Status" of the variable SECURITY_MODIFICATION is set to "Affected" and all signalling radio bearers: 2> using the ciphering algorithm (UEA [40]) indicated by the IE "Ciphering algorithm" as part of the new ciphering configuration; 2> for each radio bearer that belongs to a CN domain for which the IE "Status" of the variable SECURITY_MODIFICATION is set to "Affected" and all signalling radio bearers: 3> using the value of the IE "RB identity" in the variable ESTABLISHED_RABS minus one as the value of BEARER [40] in the ciphering algorithm. 1> for the downlink and the uplink, apply the new ciphering configuration as follows: 2> if the ciphering configuration for a AM or UM radio bearer or signalling radio bearer from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the current received message includes the IE "DL Counter Synch Info" or the current received message is a RADIO BEARER RECONFIGURATION message and includes the IE "New U-RNTI": 3> if the previous SECURITY MODE COMMAND was received due to new keys being received: 4> consider the new ciphering configuration to include the received new keys. 3> else if the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 4> consider the new ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN. 3> apply the new ciphering configuration in uplink and downlink immediately following RLC reestablishment. 2> if the IE "Ciphering activation time for DPCH" is present in the IE "Ciphering mode info" and the UE was in CELL_DCH state prior to this procedure: 3> for radio bearers using RLC-TM: 4> apply the old ciphering configuration for CFN less than the number indicated in the IE "Ciphering activation time for DPCH"; 4> apply the new ciphering configuration for CFN greater than or equal to the number indicated in IE "Ciphering activation time for DPCH". 2> if the IE "Radio bearer downlink ciphering activation time info" is present: 3> apply the following procedure for each radio bearer and signalling radio bearers using RLC-AM or RLCUM indicated by the IE "RB identity": 4> suspend uplink transmission on the radio bearer or the signalling radio bearer (except for the SRB where the response message is transmitted) according to the following:
3GPP
Release 6
282
3GPP TS 25.331 V6.23.0 (2009-09)
5> do not transmit RLC PDUs with sequence number greater than or equal to the uplink activation time, where the uplink activation time is selected according to the rules below. 4> select an "RLC sequence number" at which (activation) time the new ciphering configuration shall be applied in uplink for that radio bearer according to the following: 5> consider a ciphering activation time in uplink to be pending until the RLC sequence number of the next RLC PDU to be transmitted for the first time is equal to or larger than the selected activation time; 5> for each radio bearer and signalling radio bearer that has no pending ciphering activation time in uplink as set by a previous procedure changing the security configuration: 6> set a suitable value that would ensure a minimised delay in the change to the latest ciphering configuration. 5> for each radio bearer and signalling radio bearer that has a pending ciphering activation time in uplink as set by a previous procedure changing the security configuration: 6> for radio bearers and signalling radio bearers except SRB2: 7> set the same value as the pending ciphering activation time. 6> for signalling radio bearer SRB2: 7> set a suitable value that would ensure a minimised delay in the change to the latest ciphering configuration. 4> store the selected "RLC sequence number" for that radio bearer in the entry for the radio bearer in the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 4> switch to the new ciphering configuration according to the following: 5> use the old ciphering configuration for the transmitted and received RLC PDUs with RLC sequence numbers smaller than the corresponding RLC sequence numbers indicated in the IE "Radio bearer uplink ciphering activation time info" sent to UTRAN and in the received IE "Radio bearer downlink ciphering activation time info" received from UTRAN, respectively; 5> use the new ciphering configuration for the transmitted and received RLC PDUs with RLC sequence numbers greater than or equal to the corresponding RLC sequence numbers indicated in the IE "Radio bearer uplink ciphering activation time info" sent to UTRAN and in the received IE "Radio bearer downlink ciphering activation time info" received from UTRAN, respectively; 5> for a radio bearer using RLC-AM, when the RLC sequence number indicated in the IE "Radio bearer downlink ciphering activation time info" falls below the RLC receiving window and the RLC sequence number indicated in the IE "Radio bearer uplink ciphering activation time info" falls below the RLC transmission window, the UE may release the old ciphering configuration for that radio bearer; 5> if an RLC reset or re-establishment of the transmitting side of an RLC entity occurs before the activation time for the new ciphering configuration has been reached in uplink, ignore the activation time and apply the new ciphering configuration in uplink immediately after the RLC reset or RLC re-establishment; 5> if an RLC reset or re-establishment of the receiving side of an RLC entity occurs before the activation time for the new ciphering configuration has been reached in downlink, ignore the activation time and apply the new ciphering configuration in downlink immediately after the RLC reset or RLC re-establishment. 2> if the current received message includes the IE "Downlink counter synchronisation info" or the current received message is a RADIO BEARER RECONFIGURATION message and includes the IE "New URNTI": 3> apply the new ciphering configuration in uplink and downlink immediately following RLC reestablishment.
3GPP
Release 6
283
3GPP TS 25.331 V6.23.0 (2009-09)
If the IE "Radio bearer downlink ciphering activation time info" was received in another message than SECURITY MODE COMMAND: 1> the UE behaviour is unspecified. If the IE "Ciphering mode info" is not present, the UE shall: 1> for the downlink and the uplink, apply the ciphering configuration as follows: 2> if the ciphering configuration for a AM or UM radio bearer or signalling radio bearer from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the current received message includes the IE "Downlink counter synchronisation info" or the current received message is a RADIO BEARER RECONFIGURATION message and includes the IE "New U-RNTI": 3> if the previous SECURITY MODE COMMAND was received due to new keys being received: 4> consider the ciphering configuration to include the received new keys. 3> else if the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 4> consider the ciphering configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN. 3> apply the ciphering configuration in uplink and downlink immediately following RLC re-establishment. 2> else: 3> not change the ciphering configuration.
8.6.3.5
Integrity protection mode info
The IE "Integrity protection mode info" defines the new integrity protection configuration. At any given time, the UE needs to store at most three different integrity protection configurations (keysets) in total for all signalling radio bearers for all CN domains. If the IE "Integrity protection mode info" is present and if the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to TRUE, the UE shall: 1> ignore this second attempt to change the integrity protection configuration; and 1> set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to TRUE. If the IE "Integrity protection mode command" has the value "Start", the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Not started" and the IE "Integrity protection mode info" was not included in the message SECURITY MODE COMMAND; or If the IE "Integrity protection mode command" has the value "Start", the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Not started", the IE "Integrity protection mode info" was included in the message SECURITY MODE COMMAND and the IE "Integrity protection algorithm" is not included; or If the IE "Integrity protection mode command" has the value "Modify" and the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Not Started"; or If the IE "Integrity protection mode command" has the value "Start", the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and the IE "Integrity protection mode command info" was included in the message SECURITY MODE COMMAND; or If the IE "Integrity protection mode command" has the value "Modify" and there does not exist exactly one integrity protection activation time in the IE "Downlink integrity protection activation info" for each established signalling radio bearer included in the IE "Signalling radio bearer information" in the IE "ESTABLISHED_RABS"; or If the IE "Integrity protection mode command" has the value "Modify", the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and the IE "Integrity protection mode info" was not included in the message SECURITY MODE COMMAND:
3GPP
Release 6
284
3GPP TS 25.331 V6.23.0 (2009-09)
the UE shall: 1> ignore this attempt to change the integrity protection configuration; and 1> set the variable INVALID_CONFIGURATION to TRUE. If the IE "Integrity protection mode info" is not present, the UE shall: 1> not change the integrity protection configuration. If the IE "Integrity protection mode info" is present and if the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO is set to FALSE, the UE shall: 1> set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to TRUE; 1> perform the actions in accordance with subclauses 8.6.3.5.1, 8.6.3.5.2 and 8.6.3.5.3.
8.6.3.5.1
The UE shall:
Initialisation of Integrity Protection
1> if the IE "Integrity protection mode command" has the value "start" and the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Not started", and this IE was included in the message SECURITY MODE COMMAND: 2> initialise the information for all signalling radio bearers in the variable INTEGRITY_PROTECTION_INFO according to the following: 3> set the IE "Uplink RRC Message sequence number" in the variable INTEGRITY_PROTECTION_INFO to zero; 3> do not set the IE "Downlink RRC Message sequence number" in the variable INTEGRITY_PROTECTION_INFO; 3> set the variable INTEGRITY_PROTECTION_ACTIVATION_INFO to zero for each signalling radio bearer in the IE "ESTABLISHED_RABS". NOTE: The IEs "Integrity protection activation info" and "RRC Message sequence number"included in the IE "Integrity Check Info" in the transmitted message do not have identical values, but integrity protection is applied from the first transmitted message.
2> set the IE "Status" in the variable INTEGRITY_PROTECTION_INFO to the value "Started"; 2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in subclause 8.5.10.1 by: 3> using the algorithm (UIA [40]) indicated by the IE "Integrity protection algorithm" contained in the IE "Integrity protection mode info"; 3> using the IE "Integrity protection initialisation number", contained in the IE "Integrity protection mode info" as the value of FRESH [40]. 2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer in the IE "ESTABLISHED_RABS" except RB2 at the next received RRC message; 2> start applying the new integrity protection configuration in the downlink for signalling radio bearer RB2 from and including the received SECURITY MODE COMMAND message; 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted SECURITY MODE COMPLETE message; 2> start applying the new integrity protection configuration in the uplink for signalling radio bearers other than RB2 at the uplink activation time included in the IE "Uplink integrity protection activation info".
3GPP
Release 6
285
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
After Inter-RAT handover to UTRAN, and ciphering was activated in the other RAT, then during the first security mode control procedure following the handover, UE activates integrity protection using the integrity key of the same key set as used in the other RAT (see.subclause 8.3.6.3).
8.6.3.5.2
The UE shall:
Integrity Protection Re-configuration for SRNS Relocation and handover from GERAN Iu mode
1> if IE "Integrity protection mode command" has the value "start" and the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was not included SECURITY MODE COMMAND: NOTE: This case is used in SRNS relocation and in handover from GERAN Iu mode.
2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in subclause 8.5.10.1 by: 3> using the algorithm (UIA [40]) indicated by the IE "Integrity protection algorithm" contained in the IE "Integrity protection mode info"; 3> using the IE "Integrity protection initialisation number", contained in the IE "Integrity protection mode info" as the value of FRESH [40]. 2> let RBm be the signalling radio bearer where the reconfiguration message was received and let RBn be the signalling radio bearer where the response message is transmitted; 2> prohibit transmission of RRC messages on all signalling radio bearers in the IE "ESTABLISHED_RABS" except on RB0 and the radio bearer where the response message is transmitted; 2> for the downlink, for each signalling radio bearer, if for the signalling radio bearer, a security configuration triggered by a previous SECURITY MODE COMMAND has not yet been applied, due to the activation time for the signalling radio bearer not having been reached: 3> set "Down link RRC Message sequence number" for this signalling radio bearer in the variable INTEGRITY_PROTECTION_INFO to (activation time -1), where the activation time is the corresponding activation time for this signalling radio bearer; 3> if the previous SECURITY MODE COMMAND was received due to new keys being received: 4> consider the new integrity protection configuration to include the received new keys. 3> else if the previous SECURITY MODE COMMAND caused a change in LATEST_CONFIGURED_CN_DOMAIN: 4> consider the new Integrity Protection configuration to include the keys associated with the LATEST_CONFIGURED_CN_DOMAIN associated with the previously received SECURITY MODE COMMAND. 2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer in the IE "ESTABLISHED_RABS" except RBm at the next received RRC message for the corresponding signalling radio bearer; 2> start applying the new integrity protection configuration in the downlink for signalling radio bearer RBm from and including the received configuration message; 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RBn from and including the transmitted response message; 2> start applying the new integrity protection configuration in the uplink for signalling radio bearers other than RBn from the first message onwards.
3GPP
Release 6
286
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.3.5.3
The UE shall:
Integrity Protection modification in case of new keys or initialisation of signalling connection
1> if the IE "Integrity protection mode command" has the value "modify" and the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was included in SECURITY MODE COMMAND: 2> store the (oldest currently used) integrity protection configuration until activation times have elapsed for the new integrity protection configuration to be applied on all signalling radio bearers; 2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer n, at the first received message with RRC Sequence number greater than or equal to the RRC sequence number indicated by the entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity protection mode info"; 2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in subclause 8.5.10.1; 3> if present, use the algorithm indicated by the IE "Integrity protection algorithm" (UIA [40]); 2> set the content of the variable INTEGRITY_PROTECTION_ACTIVATION_INFO according to the following: 3> for each established signalling radio bearer, stored in the variable ESTABLISHED_RABS: 4> select a value of the RRC sequence number at which (activation) time the new integrity protection configuration shall be applied in uplink for that signalling radio bearer according to the following: 5> for each signalling radio bearer except RB0: 6> set the activation time for the new integrity protection configuration to the next RRC SN. 4> for signalling radio bearer RB0: 5> set the value of the included RRC sequence number to greater than or equal to the current value of the RRC sequence number for signalling radio bearer RB0 in the variable INTEGRITY_PROTECTION_INFO, plus the value of the constant N302 plus two. 4> prohibit the transmission of RRC messages on all signalling radio bearers, except for RB2, with RRC SN greater than or equal to the value in the "RRC message sequence number list" for the signalling radio bearer in the IE "Uplink integrity protection activation info" of the variable INTEGRITY_PROTECTION_ACTIVATION_INFO. 2> start applying the new integrity protection configuration in the uplink at the RRC sequence number, for each RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Uplink integrity protection activation info", included in the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> start applying the new integrity protection configuration in the uplink at the RRC sequence number for signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration; 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number, for each RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "Downlink integrity protection activation info"; NOTE: For signalling radio bearers that have a pending activation time as set for integrity protection by a previous procedure changing the integrity protection configuration, UTRAN should set this value in IE "Downlink integrity protection activation info".
2> start applying the new integrity protection configuration in the downlink at the RRC sequence number for signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration.
3GPP
Release 6
287
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.3.6
Void
8.6.3.7
Void
8.6.3.8
Integrity check info
If the IE "Integrity check info" is present the UE shall: 1> act as described in subclause 8.5.10.1.
8.6.3.9
New C-RNTI
If the IE "New C-RNTI" is included, the UE shall: 1> store the value in the variable C_RNTI, replacing any old stored value; 1> use that C-RNTI when using common transport channels of type RACH and FACH in the current cell.
8.6.3.9a
New DSCH-RNTI
In TDD if the IE "New DSCH-RNTI" is included, the UE shall: 1> if the UE will be in CELL_DCH or CELL_FACH at the end of the procedure where the received message included this IE: 2> if the UE supports DSCH or USCH as indicated in the IE "Physical Channel Capability" included in the IE "UE Radio Access Capability": 3> store the value in the variable DSCH_RNTI, replacing any old stored value; 3> use that DSCH-RNTI when using SHCCH signalling in the current cell.
8.6.3.10
New U-RNTI
If the IE "New U-RNTI" is included in a received message, the UE shall: 1> store the value in the variable U_RNTI, replacing any old stored value.
8.6.3.11
RRC transaction identifier
The IE "RRC transaction identifier" may be used, together with the message type, for identification of an invocation of a downlink procedure (transaction). The UE behaviour for accepting or rejecting transactions based on the message type and the IE "RRC transaction identifier" is specified below. If the IE "RRC transaction identifier" is included in a received message, the UE shall perform the actions below. The UE shall: If the received message is any of the messages: RADIO BEARER SETUP; or RADIO BEARER RECONFIGURATION; or RADIO BEARER RELEASE; or TRANSPORT CHANNEL RECONFIGURATION; or PHYSICAL CHANNEL RECONFIGURATION:
3GPP
Release 6
288
3GPP TS 25.331 V6.23.0 (2009-09)
the UE shall: 1> if the variable ORDERED_RECONFIGURATION is set to FALSE; and 1> if the variable CELL_UPDATE_STARTED is set to FALSE; and 1> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL_ERROR_REJECT is set to FALSE; and 1> if the table "Accepted transactions" in the variable TRANSACTIONS does not contain an entry with an IE "Message Type" set to ACTIVE SET UPDATE: 2> accept the transaction; and 2> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS. 1> else: 2> if the variable ORDERED_RECONFIGURATION is set to TRUE; or 2> if the variable CELL_UPDATE_STARTED is set to TRUE; or 2> if the table "Accepted transactions" in the variable TRANSACTIONS contains an entry with an IE "Message Type" set to ACTIVE SET UPDATE; or 2> if the received message contains a protocol error according to clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE: 3> if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction identifier" stored for the same "Message Type" as the received message in the table "Accepted transactions" in the variable TRANSACTIONS: 4> ignore the transaction; and 4> continue with any ongoing processes and procedures as the message was not received; 4> and end the procedure. 3> else: 4> reject the transaction; and 4> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: 5> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. Else: If the received message is any of the messages: RRC CONNECTION SETUP; or CELL UPDATE CONFIRM; or URA UPDATE CONFIRM; or UE CAPABILITY ENQUIRY:
the UE shall: 1> if the IE "Message Type" of the received message is not present in the table "Accepted transactions" in the variable TRANSACTIONS: 2> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL_ERROR_REJECT is set to FALSE:
3GPP
Release 6
289
3GPP TS 25.331 V6.23.0 (2009-09)
3> accept the transaction; and 3> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS. 2> else: 2> if the received message contains a protocol error according to clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE: 3> reject the transaction; and 3> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: 4> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. 1> else: 1> if the IE "Message Type" of the received message is present in the table "Accepted transactions" in the variable TRANSACTIONS: 2> if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction identifier" stored for the "Message Type" in the table "Accepted transactions" in the variable TRANSACTIONS: 3> ignore the transaction; and 3> continue with any ongoing processes and procedures as the message was not received; and 3> end the procedure. 2> else: 2> if the IE "RRC transaction identifier" of the received message is different from the "RRC transaction identifier" stored for the "Message Type" in the table "Accepted transactions" in the variable TRANSACTIONS: 3> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL_ERROR_REJECT is set to FALSE: 4> ignore the once accepted transaction and instead accept the new transaction; and 4> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS, replacing the previous entry. NOTE 1: The UE is expected to process the first RRC CONNECTION SETUP/CELL UPDATE CONFIRM/URA UPDATE COMFIRM message that it receives after transmitting an RRC CONNECTION REQUEST/CELL_UPDATE/URA_UPDATE message. If the UE receives further RRC CONNECTION SETUP/CELL UPDATE CONFIRM/URA UPDATE COMFIRM messages without having transmitted another RRC CONNECTION REQUEST/CELL_UPDATE/URA_UPDATE message, the UE is not required to process these messages. NOTE 2: If the previously accepted transaction was a CELL UPDATE CONFIRM/URA UPDATE CONFIRM that included the IE "Dowlink counter synchronisation info", rather than ignore the first accepted transaction the UE may continue with the first transaction in the case where a cell re-selection interrupted the ongoing procedure causing a cell update procedure to be triggered. In this case the response message acts as an explicit acknowledgement of both the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message signalling an SRNS relocation and the subsequent CELL UPDATE CONFIRM/URA UPDATE CONFIRM. 3> else: 3> if the received message contains a protocol error according to clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE:
3GPP
Release 6
290
3GPP TS 25.331 V6.23.0 (2009-09)
4> reject the transaction; and 4> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: 5> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. Else: If the received message is any of the messages: HANDOVER FROM UTRAN COMMAND; or CELL CHANGE ORDER FROM UTRAN:
the UE shall: 1> if the variable ORDERED_RECONFIGURATION is set to TRUE; 2> reject the transaction; and 2> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: 3> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. Else: If the received message is any other message, the UE shall: 1> if the IE "Message Type" of the received message is not present in the table "Accepted transactions" in the variable TRANSACTIONS: 2> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL_ERROR_REJECT is set to FALSE: 3> accept the transaction; and 3> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS. 2> else: 2> if the received message contains a protocol error according to clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE: 3> reject the transaction; and 3> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. 1> else: 1> if the IE "Message Type" of the received message is present in the table "Accepted transactions" in the variable TRANSACTIONS: 2> if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction identifier" stored in any entry for the "Message Type" in the table "Accepted transactions" in the variable TRANSACTIONS: 3> ignore the transaction; and 3> continue with any ongoing processes and procedures as the message was not received; and 3> end the procedure.
3GPP
Release 6
291
3GPP TS 25.331 V6.23.0 (2009-09)
2> else: 2> if the IE "RRC transaction identifier" of the received message is different from the "RRC transaction identifier" stored in all entries for the "Message Type" in the table "Accepted transactions" in the variable TRANSACTIONS: 3> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL_ERROR_REJECT is set to FALSE: 4> accept the additional transaction; and 4> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS, in addition to the already existing entries. 3> else: 3> if the received message contains a protocol error according to clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE: 4> reject the transaction; and 4> store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS.
8.6.3.12
Capability Update Requirement
If the IE "Capability Update Requirement" is included the UE shall: 1> if the IE "UE radio access FDD capability update requirement" has the value TRUE: 2> if the UE supports FDD mode: 3> store its UTRA FDD capabilities and its UTRA capabilities common to FDD and TDD in the IE "UE radio access capability" and the IE "UE radio access capability extension" in variable UE_CAPABILITY_REQUESTED as specified below: 4> if the UE supports any radio access capability included in IE "UE radio access capability extension" that is not included in IE "UE radio access capability": NOTE: This is valid e.g. for UE that supports multiple UTRA FDD Bands and UE that supports a single UTRA FDD Band different from Band I [21]. 5> store the IE "UE radio access capability", excluding IEs "RF capability FDD" and "Measurement capability"; 5> store the IE "UE radio access capability extension", including the IEs "RF capability FDD extension" and the "Measurement capability extension" associated with each supported UTRA FDD frequency band indicated in the IE "Frequency band". 4> else: 5> store the IE "UE radio access capability", including the IEs "RF capability FDD" and "Measurement capability" associated with the Band I [21]. 1> if the IE "UE radio access 3.84 Mcps TDD capability update requirement" has the value TRUE: 2> if the UE supports 3.84 Mcps TDD mode: 3> store its UTRAN-specific 3.84 Mcps TDD capabilities and its UTRANspecific capabilities common to FDD and TDD in the variable UE_CAPABILITY_REQUESTED. 1> if the IE "UE radio access 1.28 Mcps TDD capability update requirement" has the value TRUE: 2> if the UE supports 1.28 Mcps TDD mode:
3GPP
Release 6
292
3GPP TS 25.331 V6.23.0 (2009-09)
3> store its UTRAN-specific 1.28 Mcps TDD capabilities and its UTRANspecific capabilities common to FDD and TDD in the variable UE_CAPABILITY_REQUESTED. 1> if the IE "System specific capability update requirement list" is present: 2> for each of the RAT requested in the IE "UE system specific capability" 3> if the UE supports the listed RAT: 4> include its inter-RAT radio access capabilities for the listed RAT in the IE "UE system specific capability" from the variable UE_CAPABILITY_REQUESTED. 4> if the listed RAT is GSM and PS Handover to GPRS is supported: 5> include the IE ''MS Radio Access Capability'' in the variable UE_CAPABILITY_REQUESTED; If the IE " Capability update requirement " is not present, the UE shall: 1> assume the default values as specified in subclause 10.3.3.2 and act in accordance with the above.
8.6.3.13
Group release information
The UE shall apply the following procedure to compare the IE "U-RNTI group" with the U-RNTI allocated to the UE stored in the variable U_RNTI. If the IE "group discriminator" is equal to "All": 1> consider this as a group identity match. If the IE "group discriminator" is equal to "U-RNTI mask": 1> let N be the value of the IE "U-RNTI bit mask index"; 1> if N is equal to b20, b21, or b31: 2> compare pairs of bits, starting from bit b31 downto, and including, bit N of the "SRNC identity" of the IE "URNTI" with the corresponding bits stored in the variable U_RNTI; 2> if all pairs of bits are equal: 3> consider this as a group identity match. 1> if N is equal to b1, b2, or b19: 2> compare pairs of bits, starting from bit b31 downto, and including, bit b20 of the "SRNC identity" in the IE "U-RNTI" with the corresponding bits of the "SRNC identity" stored in the variable U_RNTI; 2> if all pairs of bits are equal: 3> then compare pairs of bits, starting from bit b19 downto, and including, bit N of the "S-RNTI" in the IE "U-RNTI" with the corresponding bits of the "S-RNTI" stored in the variable U_RNTI; 3> if all pairs of bits are equal: 4> consider this as a group identity match.
8.6.3.14
New E-RNTI
If the IE "New Primary E-RNTI" and/or the IE "New Secondary E-RNTI" are/is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall: 1> store the new value(s) in the variable E_RNTI; 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.
3GPP
Release 6
293
3GPP TS 25.331 V6.23.0 (2009-09)
If, after the completion of this procedure, the variable E_DCH_TRANSMISSION is set to FALSE, the UE shall: 1> clear the variable E_RNTI. When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall: 1> use the value of the Primary E-RNTI and/or Secondary E-RNTI stored in the variable E_RNTI as UE identities in the E-AGCH reception procedure in the physical layer.
8.6.4
8.6.4.1
Radio bearer information elements

Signalling RB information to setup list
If the IE "Signalling RB information to setup list" is included the UE shall: 1> use the same START value to initialise the COUNT-C and COUNT-I variables for all the signalling radio bearers in the list; 1> if the IE "Signalling RB information to setup list" was included in the RADIO BEARER SETUP message: 2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised: 3> calculate the START value only once during this procedure according to subclause 8.5.9 for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN; 3> store the calculated START value in the variable START_VALUE_TO_TRANSMIT. 1> for each occurrence of the IE "Signalling RB information to setup": 2> use the value of the IE "RB identity" as the identity of the signalling radio bearer to setup; 2> if the signalling radio bearer identified with the IE "RB identity" does not exist in the variable ESTABLISHED_RABS: 3> create a new entry for the signalling radio bearer in the variable ESTABLISHED_RABS. 2> if the IE "Signalling RB information to setup list" was received in a message other than HANDOVER TO UTRAN COMMAND; and 2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised and the value "STATUS" of the variable CIPHERING_STATUS of the CN domain stored in this variable is "Started": 3> if the IE "Uplink RLC mode" or the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "AM RLC" or "UM RLC": 4> initialise the 20 MSB of the hyper frame number component of COUNT-C for this signalling radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT; 4> set the remaining LSB of the hyper frame number component of COUNT-C for this signalling radio bearer to zero; 4> start to perform ciphering on this signalling radio bearer, using the value of the IE "RB identity" minus one as the value of BEARER in the ciphering algorithm. 2> if the IE "Signalling RB information to setup list" was received in a message other than HANDOVER TO UTRAN COMMAND; and 2> if the variable LATEST_CONFIGURED_CN_DOMAIN has been initialised and the value "Status" of the variable "INTEGRITY_PROTECTION_INFO" of the CN domain stored in this variable is "Started": 3> initialise the 20 MSB of the hyper frame number component of COUNT-I for this signalling radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT; 3> set the remaining LSB of the hyper frame number component of COUNT-I for this signalling radio bearer to zero;
3GPP
Release 6
294
3GPP TS 25.331 V6.23.0 (2009-09)
3> for this signalling radio bearer, set the IE "Uplink RRC Message sequence number" in the variable INTEGRITY_PROTECTION_INFO to zero; 3> start performing integrity protection according to subclauses 8.5.10.1 and 8.5.10.2. 2> perform the actions for the IE "RLC info" as specified in subclause 8.6.4.9, applied for that signalling radio bearer; 2> perform the actions for the IE "RB mapping info" as specified in subclause 8.6.4.8, applied for that signalling radio bearer. 1> apply a default value of the IE "RB identity" equal to 1 for the first IE "Signalling RB information to setup"; and 1> increase the default value by 1 for each occurrence. NOTE: The UTRAN should only use the default value of the IE "RB identity" within the RRC Connection Setup and Handover to UTRAN Command messages. If the default value of the IE "RB identity" is used in any other message then the UE behaviour is not specified.
8.6.4.2
RAB information for setup
If the IE "RAB information for setup" is included, the procedure is used to establish radio bearers belonging to a radio access bearer, and the UE shall: 1> if several IEs "RAB information for setup" are included and the included IEs "CN domain identity" in the IE "RAB info" does not all have the same value: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the radio access bearer identified with the IE "RAB info" does not exist in the variable ESTABLISHED_RABS: 2> create a new entry for the radio access bearer in the variable ESTABLISHED_RABS; 2> store the content of the IE "RAB info" in the entry for the radio access bearer in the variable ESTABLISHED_RABS; 2> indicate the establishment of the radio access bearer to the upper layer entity using the IE "CN domain identity", forwarding the content of the IE "RAB identity"; 2> if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE "CN domain identity" and at least one transparent mode radio bearer is included in the IE "RB information to setup"; or 2> if at least one RLC-AM or RLC-UM radio bearer is included in the IE "RB information to setup": 3> calculate the START value only once during this procedure (the same START value shall be used on all new radio bearers created for this radio access bearer) according to subclause 8.5.9 for the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" part of the IE "RAB information to setup"; 3> store the calculated START value in the variable START_VALUE_TO_TRANSMIT. 1> for each radio bearer in the IE "RB information to setup": 2> if the radio bearer identified with the IE "RB identity" does not exist in the variable ESTABLISHED_RABS: 3> perform the actions specified in subclause 8.6.4.3; 3> store information about the new radio bearer in the entry for the radio access bearer identified by "RAB info" in the variable ESTABLISHED_RABS; 3> create a new RAB subflow for the radio access bearer; 3> number the RAB subflow in ascending order, assigning the smallest number to the RAB subflow corresponding to the first radio bearer in the list;
3GPP
Release 6
295
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "CN domain identity" in the IE "RAB info" is set to "PS domain" and the number of RAB subflows for the radio access bearer is greater than 1: 4> set the variable INVALID_CONFIGURATION to TRUE. 2> if the radio bearer identified with the IE "RB identity" already exists in the variable ESTABLISHED_RABS: 3> set the variable INVALID_CONFIGURATION to TRUE.
8.6.4.2a
RAB information to reconfigure
If the IE "RAB information to reconfigure" is included then the UE shall: 1> if the entry for the radio access bearer identified by the IE "CN domain identity" together with the IE "RAB Identity" in the variable ESTABLISHED_RABS already exists: 2> perform the action for the IE "NAS Synchronization Indicator", according to subclause 8.6.4.12. 1> else: 2> set the variable INVALID_CONFIGURATION to TRUE.
8.6.4.3
RB information to setup
If the IE "RB information to setup" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall: 1> use the same START value to initialise the hyper frame number components of COUNT-C variables for all the new radio bearers to setup; 1> perform the actions for the IE "PDCP info", if present, according to subclause 8.6.4.10, applied for the radio bearer; 1> perform the actions for the IE "RLC info", according to subclause 8.6.4.9, applied for the radio bearer; 1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer; 1> if the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "TM RLC": 2> configure delivery of erroneous SDUs in lower layers according to indication from upper layer [5]. 1> if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN COMMAND; and 1> if the IE "Uplink RLC mode" or the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "AM RLC" or "UM RLC": 2> initialise the 20 MSB of the hyper frame number component of COUNT-C for this radio bearer with the START value in the variable START_VALUE_TO_TRANSMIT; 2> set the remaining LSB of the hyper frame number component of COUNT-C for this radio bearer to zero; 2> start incrementing the COUNT-C values. 1> if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN COMMAND; and 1> if the IE "Uplink RLC mode" and the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the RB identity in the IE "Same as RB" is set to "TM RLC": 2> if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS and at least one transparent mode radio bearer is included in the IE "RB information to setup":
3GPP
Release 6
296
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Not Started": 4> at the activation time as specified in the IE "Ciphering activation time for DPCH" if included in the IE "Ciphering mode info" in the command message or, if this IE is not included, as specified in the IE "COUNT-C activation time" included in the response message: 5> initialise the 20 most significant bits of the hyper frame number component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START_VALUE_TO_TRANSMIT; 5> set the remaining LSB of the hyper frame number component of COUNT-C to zero; 5> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain. 3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to " Started": 4> at the activation time as specified in the IE "Activation Time" in the RADIO BEARER SETUP message: 5> initialise the 20 most significant bits of the HFN component of COUNT-C common for all transparent mode RLC radio bearer to the value of the latest transmitted START for this CN domain, while not incrementing the value of the HFN component of COUNT-C at each CFN cycle; and 5> set the remaining LSB of the HFN component of COUNT-C to zero; 5> start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN. 4> at the activation time as specified in the IE "Ciphering activation time for DPCH" if included in the IE "Ciphering mode info" in the command message or, if this IE is not included, as specified in the IE "COUNT-C activation time" included in the response message: 5> initialise the 20 most significant bits of the HFN component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START_VALUE_TO_TRANSMIT; 5> set the remaining LSB of the HFN component of COUNT-C to zero; 5> if the received message is used to perform a Timing re-initialised hard handover: 6> increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is set to zero.
5> start incrementing the COUNT-C value common for all transparent mode radio bearers of this CN domain as normal, at each CFN value, i.e. the HFN component is no longer fixed in value but incremented at each CFN cycle. 2> if prior to this procedure there exists at least one transparent mode radio bearer for the CN domain included in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS: 3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Not Started": 4> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain. 3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started": 4> use the COUNT-C value common for all transparent mode radio bearers of this CN domain. 1> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":
3GPP
Release 6
297
3GPP TS 25.331 V6.23.0 (2009-09)
2> start to perform ciphering on the radio bearer in lower layers, using the value of the IE "RB identity" minus one as the value of BEARER in the ciphering algorithm. NOTE: UTRAN should not use the IE "RB information to setup" to setup radio bearers with RB identity in the range 1-4.
8.6.4.4
RB information to be affected
If the IE "RB information to be affected" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall: 1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer.
8.6.4.4a
Void
8.6.4.5
RB information to reconfigure
If the IE "RB information to reconfigure" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall: 1> perform the actions for the IE "PDCP info", if present, according to subclause 8.6.4.10, applied for the radio bearer; 1> if the IE "RLC info" is present: 2> perform the actions for the IE "RLC info", according to subclause 8.6.4.9, applied for the radio bearer. 1> else: 2> continue using the current RLC configuration for the radio bearer. 1> perform the actions for the IE "RB mapping info", according to subclause 8.6.4.8, applied for the radio bearer; 1> if the IE "Downlink RLC mode" in the IE "RLC info" is set to "TM RLC": 2> configure delivery of erroneous SDUs in lower layers according to indication from upper layer [5]. 1> if the IE "PDCP SN info" is included: 2> perform the actions as specified in subclause 8.6.4.11 applied for the radio bearer. 1> if the IE "RB stop/continue" is included; and 2> if the "RB identity" has a value greater than 2; and 3> if the value of the IE "RB stop/continue" is "stop": 4> configure the RLC entity for the radio bearer to stop; 4> set the IE "RB started" in the variable ESTABLISHED_RABS to "stopped" for that radio bearer. 3> if the value of the IE "RB stop/continue" is "continue": 4> configure the RLC entity for the radio bearer to continue; 4> set the IE "RB started" in the variable ESTABLISHED_RABS to "started" for that radio bearer. 2> if the IE "RB identity" is set to a value less than or equal to 2: 3> set the variable INVALID_CONFIGURATION to TRUE.
3GPP
Release 6
298
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.4.6
RB information to release
If the IE "RB information to release" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall: 1> if the IE "RB identity" is set to a value less than 4: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE "RB identity" refers to a signalling radio bearer: 2> release the RLC entity for the signalling radio bearer; 2> delete the information about the signalling radio bearer from the variable ESTABLISHED_RABS. 1> if the IE "RB identity" refers to a radio bearer: 2> release the PDCP and RLC entities for that radio bearer; 2> indicate release of the RAB subflow associated with the radio bearer to upper layers; 2> delete the information about the radio bearer from the variable ESTABLISHED_RABS; 2> when all radio bearers belonging to the same radio access bearer have been released: 3> indicate release of the radio access bearer to upper layers providing the "CN domain identity" together with the "RAB identity" stored in the variable ESTABLISHED_RABS; 3> delete all information about the radio access bearer from the variable ESTABLISHED_RABS. The UE shall: 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25; 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.
8.6.4.7
RB with PDCP information
If the IE "RB with PDCP information" is included, the UE shall apply the following actions on the radio bearer identified with the value of the IE "RB identity". The UE shall: 1> for the IE "PDCP SN info": 2> perform the actions as specified in subclause 8.6.4.11.
8.6.4.8
RB mapping info
If the IE "RB mapping info" is included, the UE shall: 1> for each multiplexing option of the RB: 2> if a multiplexing option that maps a logical channel corresponding to a TM-RLC entity onto RACH, FACH, USCH, DSCH (only for TDD), HS-DSCH or E-DCH is included: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> if the multiplexing option realises the radio bearer on the uplink (resp. on the downlink) using two logical channels with different values of the IE "Uplink transport channel type" (resp. of the IE "Downlink transport channel type"): 3> set the variable INVALID_CONFIGURATION to TRUE.
3GPP
Release 6
299
3GPP TS 25.331 V6.23.0 (2009-09)
2> if that RB is using TM and the IE "Segmentation indication" is set to TRUE and, based on the multiplexing configuration resulting from this message, the logical channel corresponding to it is mapped onto the same transport channel as another logical channel: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> if the transport channel considered in that multiplexing option is different from RACH and if that RB is using AM and the set of RLC sizes applicable to the uplink logical channel transferring data PDUs has more than one element not equal to zero: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> if that RB is using UM or TM and the multiplexing option realises it using two logical channels: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> for each logical channel in that multiplexing option: 3> if the value of the IE "RLC size list" is set to "Explicit list": 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and the value (index) of any IE "RLC size index" in the IE "Explicit list" does not correspond to an "RLC size" in the IE transport format set of that transport channel given in the message; or 4> if the transport channel this logical channel is mapped on in this multiplexing option is different from RACH, and if a "Transport format set" for that transport channel is not included in the same message, and the value (index) of any IE "RLC size index" in the IE "Explicit list" does not correspond to an "RLC size" in the stored transport format set of that transport channel; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and the value of any IE "Logical channel list" in the transport format set is not set to "Configured"; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is not included in the same message, and the value of any IE "Logical channel list" in the stored transport format set of that transport channel is not set to "Configured": 5> set the variable INVALID_CONFIGURATION to TRUE. 3> if the value of the IE "RLC size list" is set to "All": 4> if the transport channel this logical channel is mapped on is RACH; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and the value of any IE "Logical channel list" in the transport format set is not set to "Configured"; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is not included in the same message, and the value of any IE "Logical channel list" in the stored transport format set of that transport channel is not set to "Configured": 5> set the variable INVALID_CONFIGURATION to TRUE. 3> if the value of the IE "RLC size list" is set to "Configured": 4> if the transport channel this logical channel is mapped on is RACH; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is included in the same message, and for none of the RLC sizes defined for that transport channel in the "Transport format set", the "Logical Channel List" is set to "All" or given as an "Explicit List" which contains this logical channel; or 4> if a "Transport format set" for the transport channel this logical channel is mapped on in this multiplexing option is not included in the same message, and for none of the RLC sizes defined in the
3GPP
Release 6
300
3GPP TS 25.331 V6.23.0 (2009-09)
transport format set stored for that transport channel, the "Logical Channel List" is set to "All" or given as an "Explicit List" which contains this logical channel: 5> set the variable INVALID_CONFIGURATION to TRUE. 1> if, for the HS-DSCH transport channel, as a result of the message this IE is included in, several radio bearers can be mapped onto the same MAC-d flow, and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on that MAC-d flow or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on that MAC-d flow: 2> the UE behaviour is not specified. 1> if, as a result of the message this IE is included in, several radio bearers can be mapped onto the E-DCH MAC-d flows(s), and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on at least one E-DCH MAC-d flow or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on any MAC-d flow: 2> the UE behaviour is not specified. 1> if, for transport channels other than HS-DSCH and E-DCH, as a result of the message this IE is included in, several radio bearers can be mapped onto the same transport channel, and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio bearers for a multiplexing option on that transport channel or the same "Logical Channel Identity" was used more than once in the RB mapping info of those radio bearers for the multiplexing options on that transport channel: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the "RB mapping info" is considered as valid according to the rules above: 2> delete all previously stored multiplexing options for that radio bearer; 2> store each new multiplexing option for that radio bearer; 2> perform the actions as specified in subclause 8.5.21; 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25; 2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. 1> if the IE "Uplink transport channel type" is set to the value "RACH": 2> in FDD: 3> refer the IE "RLC size index" to the RACH Transport Format Set of the first PRACH received in the IE "PRACH system information list" received in System Information Block 5, System Information Block 5bis or System Information Block 6. 2> in TDD: 3> use the first Transport Format of the PRACH of the IE "PRACH system information list" at the position equal to the value in the IE "RLC size index". In case IE "RLC info" includes IE "Downlink RLC mode" ("DL RLC logical channel info" is mandatory present) but IE "Number of downlink RLC logical channels" is absent in the corresponding IE "RB mapping info", the parameter values are exactly the same as for the corresponding UL logical channels. In case two multiplexing options are specified for the UL, the first options shall be used as default for the DL. As regards the IE "Channel type", the following rule should be applied to derive the DL channel type from the UL channel included in the IE:
3GPP
Release 6 Channel used in UL DCH RACH USCH
301
3GPP TS 25.331 V6.23.0 (2009-09)
DL channel type implied by "same as" DCH FACH DSCH
If ciphering is applied, UTRAN should not map Transparent Mode RBs of different CN domains on the same transport channel and it should not map transparent mode SRBs and RBs onto the same transport channel. In such cases the UE behaviour is not specified. For FDD the list of multiplexing options configured in the UE for each RB and SRB should comply with the following rules otherwise the UE behaviour is not specified: at most one multiplexing option can contain the combination "FACH" for the DL and "RACH" for the UL; at most one multiplexing option can contain the combination "DCH" or "DCH + HS-DSCH" for the DL together with "DCH" for he UL; at most one multiplexing option can contain the combination "HS-DSCH" or "DCH + HS-DSCH" for the DL together with "DCH" for the UL; at most one multiplexing option can contain the combination "DCH" or "DCH + HS-DSCH" for the DL together with "E-DCH" for the UL; and at most one multiplexing option can contain the combination "HS-DSCH" or "DCH + HS-DSCH" for the DL together with "E-DCH" for the UL.
8.6.4.9
RLC Info
Upon reception of the IE "RLC Info", the UE shall: 1> if both the IE "Uplink RLC mode" and the IE "Downlink RLC mode" are present in the IE "RLC info": 2> configure the transmitting and receiving RLC entities in the UE for that radio bearer accordingly. 1> else, if the IE "Uplink RLC mode" is present and the IE "Downlink RLC mode" is not present in the IE "RLC info": 2> configure the transmitting RLC entity in the UE for that radio bearer accordingly and keep the configuration existing before the reception of the message for the receiving RLC entity. 1> else, if the IE "Uplink RLC mode" is not present and the IE "Downlink RLC mode" is present in the IE "RLC info": 2> configure the receiving RLC entity in the UE for that radio bearer accordingly and keep the configuration existing before the reception of the message for the transmitting RLC entity. 1> if the IE "Polling info" is present in the IE "RLC info": 2> for each present IE in the IE "Polling info": 3> configure RLC to use the corresponding function according to the value of the IE. 2> for each absent IE in the IE "Polling info": 3> configure RLC to not use the corresponding function. 1> if the IE "Polling info" is absent: 2> configure RLC to not use the polling functionality. 1> if the IE "Downlink RLC STATUS info" is present in the IE "RLC info" (this IE is present for AM RLC): 2> for each present IE in the IE "Downlink RLC STATUS info": 3> configure RLC to use the corresponding function according to value of the IE.
3GPP
Release 6
302
3GPP TS 25.331 V6.23.0 (2009-09)
2> for each absent IE in the IE "Downlink RLC STATUS info": 3> configure RLC to not use the corresponding function. 1> if the IE "Transmission RLC discard" is present: 2> configure the discard procedure in RLC according to the IE "Transmission RLC discard" 1> if the IE "Transmission RLC discard" is absent (only possible for TM RLC and UM RLC): 2> do not configure SDU discard in RLC. 1> if the IE "Uplink RLC mode" is present and is set to "UM RLC": 2> if the IE "Alternative E-bit interpretation" is present: 3> configure the uplink RLC entity to use the alternative E-bit interpretation and corresponding LI's. 2> if the IE "Alternative E-bit interpretation" is not present: 3> configure the uplink RLC entity to use the normal E-bit interpretation and corresponding LI's. 1> if the IE "Downlink RLC mode" is present and is set to "AM RLC": 2> if IE "DL RLC PDU size" is not present: 3> determining the downlink RLC PDU size will be handled at RLC level as described in [16], without any configuration from RRC. NOTE: The case where this mandatory IE is not present is meant to handle the interaction with a network using an earlier release of the specification.
2> else, if the IE "DL RLC PDU size" is present and no downlink RLC PDU size is currently set in the RLC entity: 3> configure the corresponding RLC entity with the downlink RLC PDU size. 2> else, if the IE "DL RLC PDU size" is present and its value is different from the one currently set in the RLC entity: NOTE: The downlink RLC PDU size set in the RLC entity can either be explicitly configured or, in case no explicit configuration is provided, derived by the first received RLC PDU [16].
3> if the IE "one sided RLC re-establishment" is set to TRUE: 4> re-establish the receiving side of the corresponding RLC entity. 3> else: 4> re-establish the corresponding RLC entity. 3> configure the corresponding RLC entity with the new downlink RLC PDU size; 3> if the UE supports the lossless DL RLC PDU size change and PDCP was configured for that radio bearer with the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" set to TRUE: 4> include the current DL PDCP receive sequence number and the radio bearer identity for that radio bearer in the variable PDCP_SN_INFO. 3> if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain identity" in the IE "RAB info" for this radio bearer is set to "Started": 4> if the RLC re-establishment is caused by a CELL UPDATE CONFIRM: 5> if only the receiving side of the RLC entity was re-established:
3GPP
Release 6
303
3GPP TS 25.331 V6.23.0 (2009-09)
6>
set the HFN values for the corresponding RLC entity in downlink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain.
5> if the whole RLC entity was re-established: 6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" included in the latest transmitted CELL UPDATE message for this CN domain.
4> if the RLC re-establishment is caused by a reconfiguration message: 5> if only the receiving side of the RLC entity was re-established: 6> set the HFN values for the corresponding RLC entity in downlink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain.
5> if the whole RLC entity was re-established: 6> set the HFN values for the corresponding RLC entity in uplink and downlink equal to the value of the IE "START" that will be included in the reconfiguration complete message for this CN domain.
1> if the IE "Downlink RLC mode" is present and is set to "UM RLC": 2> if the IE "DL UM RLC LI size" is not present: 3> configure the corresponding RLC entity with an LI size of 7 bits; NOTE: The case where this mandatory IE is not present is meant to handle the interaction with a network using an earlier release of the specification.
2> else: 3> configure the corresponding RLC entity with the LI size indicated in the IE "DL UM RLC LI size". 2> if the IE "DL Reception Window Size" is present: 3> if the variable UE_CAPABILITY_TRANSFERRED indicates "Support of HS-PDSCH" as "Supported": 4> configure the corresponding RLC entity to support out-of-sequence reception with the receive window size indicated in the IE. 3> if the variable UE_CAPABILITY_TRANSFERRED indicates "Support of HS-PDSCH" as "Unsupported": 4> the UE behaviour is not specified. 2> else: 3> configure the corresponding RLC entity without out-of-sequence reception. NOTE: If the "Uplink RLC mode" or the "Downlink RLC mode" of an existing radio bearer is modified by a reconfiguration message, the UE behaviour is unspecified.
2> if the IE "Alternative E-bit interpretation" is present: 3> configure the downlink RLC entity to use the alternative E-bit interpretation and corresponding LI's. 2> if the IE "Alternative E-bit interpretation" is not present: 3> configure the downlink RLC entity to use the normal E-bit interpretation and corresponding LI's.
8.6.4.10
For RFC 3095:
PDCP Info
3GPP
Release 6
304
3GPP TS 25.331 V6.23.0 (2009-09)
1> the chosen MAX_CID shall be less than the value "Maximum number of ROHC context sessions" as indicated in the IE "PDCP Capability". If IE "PDCP info" is included, the UE shall: 1> if the radio bearer is connected to a CS domain radio access bearer: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE "PDCP PDU header" is set to the value "absent": 2> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is true: 3> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE "PDCP PDU header" is set to the value "present": 2> include PDCP headers in both uplink and downlink PDCP PDUs; 2> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is false: 3> if the IE "Header compression information" is absent: 4> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE "Header compression information" is absent: 2> not use Header compression after the successful completion of this procedure; 2> remove any stored configuration for the IE "Header compression information". 1> if the IE "Header compression information" is present: 2> if the IE "Algorithm Type" is set to "RFC 2507": 3> if the UE capability "Maximum header compression context space", as specified in [35], is exceeded with this configuration: 4> set the variable INVALID_CONFIGURATION to TRUE. 2> if the IE "Algorithm Type" is set to "RFC 3095": 3> if the uplink RLC mode for this radio bearer is RLC-TM: 4> the behaviour of the UE is unspecified. 1> configure the PDCP entity for that radio bearer accordingly; 1> configure the RLC entity for that radio bearer according to the value of the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change"; 1> set the PROFILES parameter, used by inband ROHC profile negotiation, for this PDCP entity for both UL and DL equal to the list of ROHC profiles received in the IE "PDCP info". A UE complying to this version of the protocol shall support ROHC profiles 0x0000 (ROHC uncompressed), 0x0001 (ROHC RTP), 0x0002 (ROHC UDP) and 0x0003 (ROHC ESP) (see [52]). 1> if the IE "PDCP ROHC target mode" is received: 2> set the variable " PDCP_ROHC_TARGET_MODE " to the received value. 1> if the IE "PDCP ROHC target mode" is not received in either of the CELL UPDATE CONFIRM, the RADIO BEARER RECONFIGURATION or the RADIO BEARER SETUP message: 2> delete the variable "PDCD_ROHC_TARGET_MODE" and act according to actions specified in [36].
3GPP
Release 6
305
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.4.11
PDCP SN Info
If the IE "PDCP SN Info" is included, the UE shall: 1> transfer the sequence number to the PDCP entity for the radio bearer; 1> configure the RLC entity for the radio bearer to stop; 1> include the current PDCP receive sequence number and the radio bearer identity for the radio bearer in the variable PDCP_SN_INFO.
8.6.4.12
NAS Synchronisation Indicator
If the IE "NAS Synchronisation Indicator" is present in a message, the UE shall: 1> forward the content to upper layers along with the IE "CN domain identity" of the associated RAB stored in the variable ESTABLISHED_RABS at the CFN indicated in the IE "Activation time" in order to synchronise actions in NAS and AS.
8.6.4.13
PDCP context relocation info
If the IE "PDCP context relocation info" is included, the UE shall, for each radio bearer included in this IE: 1> If the IE "Downlink RFC 3095 context relocation indication" is set to TRUE: 2> perform the actions as specified in [36] for all RFC 3095 contexts associated with that radio bearer in the downlink. 1> If the IE "Uplink RFC 3095 context relocation indication" is set to TRUE: 2> perform the actions as specified in [36] for all RFC 3095 contexts associated with that radio bearer in the uplink.
8.6.4.14
RLC Info MBMS
Upon reception of the IE "RLC Info MBMS", the UE shall: 1> configure the receiving RLC entity in the UE for that radio bearer accordingly; 1> configure the corresponding RLC entity with the LI size indicated in the IE "DL UM RLC LI size". 1> if the IE "DL Duplication Avoidance and Reordering info" is present: 2> configure the corresponding RLC entity to use the UM duplication avoidance and reordering functionality. 1> if the IE "DL Out of sequence delivery info" is present: 2> configure the corresponding RLC entity to use the UM out of sequence delivery functionality.
8.6.4.15
RAB information for MBMS ptp bearer
If the UE has included the IE "Support of MBMS service change for a ptp RB" in a previous MBMS MODIFICATION REQUEST message and if the IE "RAB information for MBMS ptp bearer" is included then the UE shall: 1> if an entry for the radio access bearer identified by the IE "RB Identity" already exists in the variable ESTABLISHED_RABS and a value of the IE "MBMS Service Identity" is stored in this entry of the variable ESTABLISHED_RABS: 2> notify upper layers that the radio access bearer characterised by the parameters currently stored in this entry of the variable ESTABLISHED_RABS is released; 2> reuse this entry of the variable ESTABLISHED_RABS and update it with the received value of IE "MBMS Service Identity" and, if included, with the received value of IE "MBMS Session Identity";
3GPP
Release 6
306
3GPP TS 25.331 V6.23.0 (2009-09)
2> notify upper layers that the radio access bearer characterised by the updated parameters in this entry is established. 1> else: 2> set the variable INVALID_CONFIGURATION to TRUE.
8.6.5
8.6.5.1
Transport channel information elements

Transport Format Set
If the IE "Transport format set" is included, the UE shall: 1> if the transport format set is a RACH TFS received in System Information Block type 5 or System Information Block type 5bis or System Information Block type 6, and CHOICE "Logical Channel List" has a value different from "Configured": 2> ignore that System Information Block. NOTE: The TFS added by the IE "Additional Dynamic Transport Format Information for CCCH" has no CHOICE "Logical Channel List" and can thus never be considered as different from "Configured".
1> if the transport format set for a downlink transport channel is received in a System Information Block, and CHOICE "Logical Channel List" has a value different from 'ALL': 2> ignore that System Information Block. 1> if the transport format set for a downlink transport channel is received in a message on a DCCH, and CHOICE "Logical Channel List" has a value different from 'ALL': 2> keep the transport format set if this exists for that transport channel; 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the value of any IE "RB identity" (and "Logical Channel" for RBs using two UL logical channels) in the IE "Logical channel list" does not correspond to a logical channel indicated to be mapped onto this transport channel in any RB multiplexing option (either included in the same message or previously stored and not changed by this message); or 1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is set to "Configured" while it is set to "All" or given as an "Explicit List" for any other RLC size; or 1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is set to "All" and for any logical channel mapped to this transport channel, the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is not set to "Configured"; or 1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is given as an "Explicit List" that contains a logical channel for which the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is not set to "Configured"; or 1> if the "Logical Channel List" for all the RLC sizes defined for that transport channel are given as "Explicit List" and if one of the logical channels mapped onto this transport channel is not included in any of those lists; or 1> if the "Logical Channel List" for the RLC sizes defined for that transport channel is set to "Configured" and for any logical channel mapped onto that transport channel, the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is also set to "Configured"; or 1> if the IE "Transport Format Set" was not received within the IE "PRACH system information list" and if the "Logical Channel List" for the RLC sizes defined for that transport channel is set to "Configured" and for any logical channel mapped onto that transport channel, the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored ) is given as an "Explicit List" that includes an "RLC size index" that does not correspond to any RLC size in this "Transport Format Set"; or
3GPP
Release 6
307
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Transport Format Set" was not received within the IE "PRACH system information list", and if that RB is using AM and the set of RLC sizes applicable to the logical channel transferring data PDUs has more than one element not equal to zero: 2> keep the transport format set if this exists for that transport channel; 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the total number of configured transport formats for the transport channel exceeds maxTF: 2> keep the transport format set if this exists for that transport channel; 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE "Transport format set" is considered as valid according to the rules above: 2> remove a previously stored transport format set if this exists for that transport channel; 2> store the transport format set for that transport channel; 2> consider the first instance of the parameter Number of TBs and TTI List within the Dynamic transport format information to correspond to transport format 0 for this transport channel, the second to transport format 1 and so on; 2> if the IE "Transport format Set" has the choice "Transport channel type" set to "Dedicated transport channel": 3> calculate the transport block size for all transport formats in the TFS using the following TB size = RLC size + MAC header size TB size = 0 where: MAC header size is calculated according to [15] if MAC multiplexing is used. Otherwise it is 0 bits; 'RLC size' reflects the RLC PDU size. if "RLC size" <> 0, if "RLC size" = 0,
2> if the IE "Transport format Set" has the choice "Transport channel type" set to "Common transport channel": 3> calculate the transport block size for all transport formats in the TFS using the following: TB size = RLC size. 2> if the IE "Number of Transport blocks" <> 0 and IE "RLC size" = 0, no RLC PDU data exists but only parity bits exist for that transport format; 2> if the IE "Number of Transport blocks" = 0, neither RLC PDU neither data nor parity bits exist for that transport format; 2> perform the actions as specified in subclause 8.5.21. For configuration restrictions on Blind Transport Format Detection, see [27].
8.6.5.2
Transport format combination set
If the IE "Transport format combination set" is included for the uplink, the UE shall for that direction: 1> store the new transport format combination set, or (if this exists) modify a previously stored transport format combination set according to IEs included in IE "Transport format combination set"; 1> start to respect those transport format combinations; 1> if IE "Transport format combination subset" is received in this message: 2> perform the actions as specified in subclause 8.6.5.3. 1> if IE "Transport format combination subset" is not received in this message:
3GPP
Release 6
308
3GPP TS 25.331 V6.23.0 (2009-09)
2> clear the IE "Duration" in the variable TFC_SUBSET; 2> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the value indicating "full transport format combination set". If the IE "Transport format combination set" is included for the downlink, the UE shall for that direction: 1> store the new transport format combination set, or (if this exists) modify a previously stored transport format combination set according to IEs included in IE "Transport format combination set"; 1> start to respect those transport format combinations. If the IE "Transport format combination set" is not included for the uplink and if there is no addition, removal or reconfiguration of transport channels, the UE shall for that direction: 1> use a previously stored transport format combination set if this exists. If the IE "Transport format combination set" is not included for the downlink and if there is no addition, removal or reconfiguration of transport channels, the UE shall for that direction: 1> use a previously stored transport format combination set if this exists. If the IE "Transport format combination set" is not included for either the uplink or the downlink and for that direction after the reconfiguration there is one or more stored DCH configuration; and 1> if no transport format combination set is stored in the UE; or 1> if transport channels are added or removed in the message; or 1> if any transport channel is reconfigured in the message such that the size of the transport format set is changed: the UE shall: 1> set the variable INVALID_CONFIGURATION to TRUE. If the IE "Transport format combination set" is not included for either the uplink or the downlink and for that direction after the reconfiguration there is no stored DCH configuration, the UE shall: 1> remove any stored transport format combination set for dedicated channels for that direction. In the uplink TFCS the minimum set of TFCs is the set of TFCs that is needed for the TFC selection algorithm defined in [15] to give a predictable result. Any configured TFCS or TFC subset shall satisfy the requirements as specified by the minimum set. In the definition of the minimum set of TFCs below, only logical channels for which the TFCS or the TFC subset include at least one TFC with non-empty TF for the corresponding transport channel should be considered. The minimum set of TFCs consists of the following: 1> for each UM logical channel: 2> a TFC with one transport block for this transport channel and empty TFs (see [34]) for all the others. If more than one TFC fulfils these criteria, only the TFC with the lowest number of bits should be included in the minimum set of TFCs. 1> for each AM logical channel: 2> a TFC with a non-empty TF for the corresponding transport channel and empty TFs for all other transport channels, where the non-empty TF includes one transport block with "Configured RLC Size" equal to the RLC PDU size. 1> for each set of "synchronous" TM logical channels (see the definition below) and for each set of SDU sizes associated with it: 2> a TFC with TFs corresponding to any combination of SDU sizes that can be received in a TTI from higher layers on the corresponding transport channels and empty TFs for all other transport channels.
3GPP
Release 6
309
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
In case an adaptive rate codec is used and the TFCS has been restricted by the IE "TFC subset", the minimum set consists of the set of TFCs with TFs corresponding to any combination of SDU sizes that can be received in a TTI respecting the restricted TFCS.
1> for each TM logical channel that is not part of a set of "synchronous" TM logical channels (see the definition below): 2> a TFC with non-empty TFs for the corresponding transport channel, and empty TFs for all other transport channels, where 3> for non-segmented mode TM-RLC logical channels the non-empty TFs include, for the smallest SDU size that can be received in a single TTI from higher layer: 4> a TF with non-zero number of transport blocks with "Configured RLC Size" equal to the corresponding SDU size. If more than one TFC fulfils these criteria, only the TFC with the lowest number of bits in the TFC is included in the minimum set of TFCs. 3> for segmented mode TM-RLC, the non-empty TFs include any TF such that the number of transport blocks multiplied by the "Configured RLC Size" is equal to the smallest SDU size that can be received in a single TTI from higher layer. 1> an "empty" TFC (see [34]). Furthermore, the UTRAN should ensure that the uplink TFCS and any configured TFC Subset satisfies the following rules: 1> for each TTI length with which at least one transport channel is configured: 2> for each combination of TFs for the transport channels configured with this TTI length included in the TFCS: 3> a TFC with these TFs for the transport channels configured with this TTI length and empty TFs on all transport channels configured with shorter TTI lengths is also included in the TFCS. For TDD, the TFCS of a CCTrCH should include those of the above combinations, which include a TF with one transport block for a transport channel used in that CCTrCH, and the "empty" TFC should be included in the TFCS of every CCTrCH. Synchronous TM logical channels are logical channels on which higher layer traffic is generated in a perfectly correlated fashion (e.g. AMR RAB). NOTE: The "Configured RLC Size" is defined as the transport block size minus the MAC header size.
8.6.5.3
Transport format combination subset
When configuring a TFC Subset, the UTRAN should follow the guidelines defined in subclause 8.6.5.2. If the IE "Transport format combination subset"("TFC subset") is included, the UE shall: 1> if the IE "Minimum allowed Transport format combination index" is included; and 2> if the value of the IE "Minimum allowed Transport format combination index" is greater than the highest TFCI value in the current transport format combination set: 3> consider the TFC subset to be incompatible with the current transport format combination set. 1> if the IE "Allowed transport format combination list" is included; and 2> if the value of any of the IEs "Allowed transport format combination" included in the IE "Allowed transport format combination list" does not match a TFCI value in the current transport format combination set: 3> consider the TFC subset to be incompatible with the current transport format combination set. 1> if the IE "Non-allowed transport format combination list" is included; and
3GPP
Release 6
310
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the value of any of the IEs "Non-allowed transport format combination" included in the IE "Non-allowed transport format combination list" does not match a TFCI value in the current transport format combination set: 3> consider the TFC subset to be incompatible with the current transport format combination set. 1> if the IE "Restricted TrCH information" is included: 2> if the value of any of the IEs "Uplink transport channel type" and "Restricted UL TrCH identity" included in the IE "Restricted TrCH information" do not correspond to any of the transport channels for which the current transport format combination set is valid: 3> consider the TFC subset to be incompatible with the current transport format combination set. 2> if the IE "Allowed TFIs" is included; and 3> if the value of each of the IEs "Allowed TFI" included in the IE "Allowed TFIs" corresponds to a transport format for that transport channel within the current transport format combination set: 4> allow all transport format combinations that include these transport formats for the transport channel; 4> restrict all other transport format combinations. 3> else: 4> consider the TFC subset to be incompatible with the current transport format combination set. 2> if the IE "Allowed TFIs" is not included: 3> restrict all transport format combinations where the transport channel has a transport format of non-zero rate. 1> if the UE considers the TFC subset to be incompatible with the current Transport format combination set according to the above: 2> keep any previous restriction of the transport format combination set; 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the UE does not consider the TFC subset to be incompatible with the current Transport format combination set according to the above: 2> if the IE "Transport format combination subset" is received in a message other than a TRANSPORT FORMAT COMBINATION CONTROL message: 3> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the IE "Transport format combination subset" (in case of TDD for the uplink CCTrCH specified by the IE "TFCS Id"); 3> clear the IE "Duration" in the variable TFC_SUBSET; 3> apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET. 1> if the IE "transport format combination subset" indicates the "full transport format combination set": 2> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the value indicating "full transport format combination set"; 2> clear the IE "Duration" in the variable TFC_SUBSET; 2> if the IE "Transport format combination subset" is received in a TRANSPORT FORMAT COMBINATION CONTROL message, then at the CFN indicated by the IE "Activation time for TFC subset" any restriction on transport format combination set is released and the UE may use the full transport format combination set; 2> else:
3GPP
Release 6
311
3GPP TS 25.331 V6.23.0 (2009-09)
3> any restriction on transport format combination set is released and the UE may use the full transport format combination set.
8.6.5.4
DCH quality target
If the IE "DCH quality target" is included, the UE shall: 1> set, at physical channel establishment, the initial downlink target SIR value based on the received IE "DCH quality target" for the transport channel with respect to all transport formats; 1> adjust the target SIR for the downlink power control to meet the quality target received in the IE "DCH quality target" for the transport channel. The UE shall not compensate for the fact that the required SIR to achieve a target BLER for a particular transport format may be different from the required SIR to achieve the target BLER for another transport format.. NOTE 1: Adjusting the target SIR is possible to do continuously by the UE if a CRC exists in all transport formats in the downlink TFS for a DCH. If a CRC does not exist in all transport formats, the UE can only adjust the target SIR when receiving transport formats containing a CRC and the UE has knowledge about the transport format according to [27]. NOTE 2: If the UTRAN configures a UE to use blind transport format detection and configures a transport channel such that single transport format detection [27] must be used to detect the TF, then it is not possible for the UE to maintain a quality target for that transport channel.
8.6.5.5
Added or Reconfigured UL TrCH information
If the IE "Added or Reconfigured UL TrCH information" is included then the UE shall: 1> for the transport channel identified by the IE "UL Transport Channel Identity" and IE "Uplink transport channel type": 2> perform the actions for the IE "Transport Format Set" as specified in subclause 8.6.5.1. NOTE: The UE stores the UL transport channel configuration until it is explicitly deleted by a message containing the IE "Deleted UL TrCH information" or the UE leaves RRC Connected mode.
1> if the choice "UL parameters" is set to 'E-DCH': 2> apply the values of the IE "E-DCH Transmission Time Interval" and the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows. 2> for the IE "HARQ Info for E-DCH": 3> perform the actions specified in subclause 8.6.5.17. 2> if the IE "Added or Reconfigured E-DCH MAC-d Flow list " is included: 3> for each MAC-d flow identified by the IE "Mac-d flow identity": 4> perform the actions as specified in subclause 8.6.5.18. 2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. NOTE: In case of multiple E-DCH MAC-d flows, IE "Added or Reconfigured UL TrCH information" is only included once. If the IE "Added or Reconfigured UL TrCH information" is included more than once with the IE "Uplink transport channel type" set to 'E-DCH', the UE behaviour is unspecified.
8.6.5.5a
Added or reconfigured MAC-d flow
If the IE "Added or reconfigured MAC-d flow" is included, the UE shall: 1> if a MAC-hs queue (identified by the IE "MAC-hs queue Id") is included in both the IE "MAC-hs queue to add or reconfigure list" and the IE "MAC-hs queue to delete list":
3GPP
Release 6
312
3GPP TS 25.331 V6.23.0 (2009-09)
2> set the variable INVALID_CONFIGURATION to TRUE. 1> for each MAC-hs queue included in the IE "MAC-hs queue to add or reconfigure" list: 2> if the UE has previously stored a mapping between this MAC-hs queue and a MAC-d flow: 3> delete the old mapping. 2> map the MAC-d flow indicated in the current message to this MAC-hs queue; 2> set the release timer for each of the MAC-hs queues in the MAC-hs entity to the value in the corresponding IE "T1"; 2> set the MAC-hs receiver window size for each of the MAC-hs queues in the MAC-hs entity to the value in the corresponding IE "MAC-hs window size"; and 2> configure MAC-hs with the mapping between MAC-d PDU sizes index and allowed MAC-d PDU sizes as follows: 3> if a MAC-d PDU size has been stored for a MAC-d PDU size index for the corresponding MAC-hs queue and no mapping is provided in the current message for this MAC-d PDU index: 4> continue to use this mapping. 3> if a MAC-d PDU size has been stored for a MAC-d PDU size index for the corresponding MAC-hs queue and a mapping is provided in the current message for this MAC-d PDU index: 4> configure the MAC-hs entity with the mapping indicated in the current message. 1> for each MAC-hs queue included in the IE "MAC-hs queue to delete" list: 2> delete any information about the MAC-hs queue identified by the IE "MAC-hs queue Id". 1> if the IE "Added or reconfigured MAC-d flow" is considered valid according to the rules above: 2> perform the actions as specified in subclause 8.5.21.
8.6.5.6
Added or Reconfigured DL TrCH information
If the IE "Added or Reconfigured DL TrCH information" is included then for the transport channel identified by the IE "DL Transport Channel Identity" the UE shall: 1> if the choice "DL parameters" is set to 'explicit': 2> perform the actions for the IE "Transport Format Set" as specified in subclause 8.6.5.1. 1> if the choice "DL parameters" is set to 'same as uplink': 2> if the IE "UL Transport Channel Identity" indicates an existing or a new UL Transport Channel: 3> store as transport format for this transport channel the transport format associated with the transport channel identified by the IE "UL Transport Channel Identity". 2> else: 3> set the variable INVALID_CONFIGURATION to TRUE. 1> if the choice "DL parameters" is set to 'HSDSCH': 2> if the IE "HARQ Info" is included: 3> perform the actions specified in subclause 8.6.5.6b. 2> if the IE "Added or Reconfigured MAC-d Flow" is included: 3> perform the actions as specified in subclause 8.6.5.5a.
3GPP
Release 6
313
3GPP TS 25.331 V6.23.0 (2009-09)
2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 1> if the IE "DCH quality target" is included: 2> perform the actions specified in subclause 8.6.5.4. NOTE: The UE stores the DL transport channel configuration until it is explicitly deleted by a message containing the IE "Deleted DL TrCH information" or the UE leaves RRC connected mode.
8.6.5.6a 8.6.5.6b
Void HARQ Info
If the IE "HARQ Info" is included, the UE shall: 1> store the received configuration; 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall: 1> configure the MAC-hs entity with the number of HARQ processes indicated in IE "Number of Processes"; 1> assign to each of these HARQ processes IDs going from 0 to "Number of Processes" 1; 1> if the IE "Memory Partitioning" is set to 'Implicit': 2> partition the soft memory buffer in the MAC-hs entity equally among the processes configured above. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearerst Integer value. 1> if the IE "Memory Partitioning" is set to 'Explicit': 2> if the UE capability "Total number of soft channel bits in HS-DSCH", as specified in [35], is exceeded with this configuration: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> else: 3> partition the soft memory buffer in the MAC-hs entity according to the IE "Process memory size" assuming that the order in the list follows the order in the HARQ process IDs.
8.6.5.7
Deleted UL TrCH information
If the IE "Deleted UL TrCH information" is included the UE shall: 1> if an Uplink transport channel is requested to be deleted: 2> delete any information about the transport channel identified by the IE "UL TrCH identity" and the IE "Uplink transport channel type". 1> if an E-DCH MAC-d flow is requested to be deleted: 2> delete any information about the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity"; 2> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.
8.6.5.8
Deleted DL TrCH information
If the IE "Deleted DL TrCH information" is included the UE shall:
3GPP
Release 6
314
3GPP TS 25.331 V6.23.0 (2009-09)
1> if a Downlink transport channel is requested to be deleted: 2> delete any information about the transport channel identified by the IE "DL TrCH identity". 1> if a DL MAC-d flow is requested to be deleted: 2> delete any information about the DL HS-DSCH MAC-d flow identified by the IE "MAC-d Flow Identity", i.e. delete any information about MAC-hs queue(s) mapped onto this MAC-d flow. 2> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.
8.6.5.9
UL Transport channel information common for all transport channels
If the IE "UL Transport channel information common for all transport channels" is included the UE shall: 1> perform actions for the IE "TFC subset" as specified in subclause 8.6.5.3; 1> if the IE "PRACH TFCS" is included: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE has the choice "mode" set to FDD: 2> perform actions for the IE "UL DCH TFCS" as specified in subclause 8.6.5.2. 1> if the IE has the choice "mode" set to TDD: 2> if the IE "Individual UL CCTrCH information" is included: 3> for each TFCS identified by IE "UL TFCS id": 4> perform actions for the IE "UL TFCS" as specified in subclause 8.6.5.2. 1> if the IE "TFC subset list" is included: 2> remove a previously stored TFC subset list if this exists in the IE "TFC subset list" in the variable TFC_SUBSET; 2> store the IE "TFC subset list" in the IE "TFC subset list" in the variable TFC_SUBSET; 2> consider the first instance of the IE "TFC subset" in the IE "TFC subset list" as Transport Format Combination Subset 0 (TFC subset identity = 0), the second instance as Transport Format Combination Subset 1 (TFC subset identity = 1) and so on; 2> if the IE"TFC subset list" contains greater than 8 elements then the UE behaviour is not specified. NOTE: The UTRAN should not modify the TFC subset list when a temporary restriction of the TFC set is being applied, due to the reception of the IE "TFC Control Duration" in a TRANSPORT FORMAT COMBINATION CONTROL message is still being applied.
8.6.5.10
DL Transport channel information common for all transport channels
If the IE "DL Transport channel information common for all transport channels" is included the UE shall: 1> if the IE "SCCPCH TFCS" is included: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the IE choice "mode" is set to FDD: 2> if the choice "DL parameters" is set to 'explicit': 3> if the IE "DL DCH TFCS" is included:
3GPP
Release 6
315
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the IE "SCCPCH TFCS" is included and the state the UE enters after handling the received information is other than CELL_DCH: 5> ignore the received IE "DL DCH TFCS". NOTE: the IE "DL Transport channel information common for all transport channels" always includes a DL DCH TFCS configuration, either by including the IE "DL DCH TFCS " or by specifying that the TFCS is the same as in UL. If UTRAN does not require the reconfiguration of the concerned parameters, UTRAN may replace one TFC with the value that is already assigned for this IE. 4> else: 5> perform actions as specified in subclause 8.6.5.2. 1> if the IE choice "mode" is set to TDD: 2> if the IE "Individual DL CCTRCH information" is included: 3> for each DL TFCS identified by the IE "DL TFCS identity": 4> if the IE choice "DL parameters" is set to 'independent': 5> perform actions for the IE "DL TFCS" as specified in subclause 8.6.5.2. 4> if the IE choice "DL parameters" is set to 'same as UL': 5> if the IE "UL DCH TFCS identity" indicates an existing or a new UL TFCS: 6> store for that DL TFCS the TFCS identified by the IE "UL DCH TFCS identity". 5> else: 6> set the variable INVALID_CONFIGURATION to TRUE.
8.6.5.11
Void
8.6.5.12
TFCS Reconfiguration/Addition Information
If the IE "TFCS Reconfiguration/Addition Information" is included the UE shall: 1> store the TFCs to be reconfigured/added indicated in the IE "CTFC information" as specified below; 1> if the IE "Power offset information" is included: 2> perform actions as specified in [29]. In order to identify the TFCs included in this IE the UE shall calculate the CTFC as specified in subclause 14.10. 1> if the IE "Additional Dynamic Transport Format Information for CCCH" was included in the IE "RACH TFS": 2> ignore for the CTFC calculation any TF added by the IE "Additional Dynamic Transport Format Information for CCCH". If the IE "TFCS Reconfiguration/Addition Information" is used in case of TFCS "Complete reconfiguration" the UE shall: 1> remove a previously stored transport format combination set if this exists; 1> consider the first instance of the IE "CTFC information" as Transport Format Combination 0 in FDD (TFCI=0) and 1 in TDD (TFCI=1), the second instance as Transport Format Combination 1 in FDD (TFCI=1) and 2 in TDD (TFCI=2) and so on. In TDD the TFCI value = 0 is reserved for physical layer use. If the IE "TFCS Reconfiguration/Addition Information" is used in case of TFCS "Addition" the UE shall insert the new additional(s) TFC into the first available position(s) in ascending TFCI order in the TFCS.
3GPP
Release 6
316
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.5.12a
Additional RACH TFCS for CCCH
If the IE "Additional RACH TFCS for CCCH " is included the UE shall: 1> if the IE "Power offset information" is included: 2> perform actions as specified in [29]. 1> add to the TFCS as calculated in 8.6.5.12 for the corresponding PRACH the TFC which consists of the TF added by the IE "Additional Dynamic Transport Format Information for CCCH" into the next position in ascending order after the highest TFCI value already used. NOTE: On PRACH only one transport channel can be multiplexed.
8.6.5.13
TFCS Removal Information
If the IE "TFCS Removal Information" is included the UE shall: 1> remove the TFC indicated by the IE "TFCI" from the current TFCS, and regard this position (TFCI) in the TFCS as vacant.
8.6.5.14
Void
8.6.5.15
TFCS Explicit Configuration
If the IE " TFCS Explicit Configuration" is included the UE shall: 1> if the IE choice "TFCS representation" is set to 'complete reconfiguration': 2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12. 1> if the IE choice "TFCS representation" is set to 'addition': 2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12. 1> if the IE choice "TFCS representation" is set to 'removal': 2> perform the actions for the IE "TFCS Removal Information" as specified in subclause 8.6.5.13. 1> if the IE choice "TFCS representation" is set to 'replace': 2> perform first the actions for the IE "TFCS Removal Information" as specified in subclause 8.6.5.13; and then 2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12.
8.6.5.16
E-DCH Transmission Time Interval
If the IE "E-DCH Transmission Time Interval" is included, the UE shall: 1> store the received TTI; 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall: 1> apply the TTI as signalled in the IE "E-DCH Transmission Time Interval" on the E-DPDCH. If the received "E-DCH Transmission Time Interval" is 2 ms and the previously stored TTI was 10 ms:
3GPP
Release 6
317
3GPP TS 25.331 V6.23.0 (2009-09)
1> not send any data on E-DPDCH in first 8 TTIs after activation time of new TTI.
8.6.5.17
HARQ Info for E-DCH
If the IE "HARQ Info for E-DCH" is included, the UE shall: 1> store the received configuration; 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall: 1> use a redundancy version for each HARQ transmission as configured by the IE "HARQ RV Configuration".
8.6.5.18
Added or reconfigured E-DCH MAC-d flow
If the IE "Added or reconfigured E-DCH MAC-d flow" is included, the UE shall: 1> if the IE "E-DCH MAC-d flow power offset" is included: 2> configure the power offset indicated in the IE "E-DCH MAC-d flow power offset" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity". 1> if the IE "E-DCH MAC-d flow maximum number of retransmissions" is included: 2> configure the maximum number of retransmissions indicated in the IE "E-DCH MAC-d flow maximum number of retransmissions" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity". 1> if the IE "E-DCH MAC-d flow multiplexing list" is included: 2> only multiplex MAC-d PDUs from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from E-DCH MAC-d flows with which multiplexing in the same MAC-e PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list". 1> else: 2> if previously the IE "E-DCH MAC-d flow multiplexing list" was already received for this E-DCH MAC-d flow: 3> continue to only multiplex E-DCH PDU's from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from E-DCH MAC-d flows with which multiplexing in the same MAC-e PDU is allowed according to the previously received IE E-DCH MAC-d flow multiplexing list. 2> else (never received the IE "E-DCH MAC-d flow multiplexing list" for this E-DCH MAC-d flow): 3> allow multiplexing of MAC-d PDUs from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from any other E-DCH MAC-d flow in the same MAC-e PDU. 1> if the IE "Non-scheduled transmission grant info" is included: 2> if the TTI configured on the E-DCH equals 2ms, and the IE "2ms non-scheduled transmission grant HARQ process allocation" is configured for this MAC-d flow: 3> MAC-d PDU's for logical channels belonging to this MAC-d flow shall only be included in a MAC-e PDU transmitted by HARQ processes allowed by the IE "2ms non-scheduled transmission grant HARQ process allocation", with a total contribution from this MAC-d flow (i.e. including MAC-e/es headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size". 2> else: 3> MAC-d PDU's for logical channels belonging to this MAC-d flow shall be included in a MAC-e PDU transmitted by any HARQ process, with a total contribution from this MAC-d flow (i.e. including MACe/es headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".
3GPP
Release 6
318
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Scheduled transmission grant info" is included: 2> transmission of MAC-d PDU's for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH/E-RGCH (see [15]). 1> perform the actions as specified in subclause 8.5.21; 1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.
8.6.6
Physical channel information elements
This subclause specifies the actions upon reception and/or non-reception of the physical channel information elements. The combination of the values of those information elements included in a given message shall follow the compatibility rules that are specified in the physical layer specifications. In case those rules are not followed, the UE shall set the variable INVALID_CONFIGURATION to TRUE.
8.6.6.1
Frequency info
If, after completion of the procedure, the UE will be in CELL_DCH state, the UE shall: 1> if the IE "Frequency info" is included: 2> if the frequency is different from the currently used frequency: 3> store and use the frequency indicated by the IE "Frequency Info"; 3> if the received message is used to perform a Timing-maintained hard handover (see subclause 8.3.5.2), and IE "Timing maintained Synchronization indicator" is included: 4> not perform any physical layer synchronisation procedure (FDD only); 3> else: 4> perform the physical layer synchronisation procedure A as specified in [29] (FDD only). 2> if the frequency is the same as the currently used frequency: 3> continue to use the currently used frequency; 3> perform the physical layer synchronisation procedure A as specified in [29] (FDD only). 1> if the IE "Frequency info" is not included and the UE has a currently used frequency: 2> continue to use the currently used frequency; NOTE If the received message is used to perform a Timing-reinitialised hard handover, and the IE "Frequency Info" is not included, the UE may perform the physical layer synchronisation procedure A as specified in [29] (FDD only).
8.6.6.2
Void
8.6.6.2a
PNBSCH allocation
The UE shall consider the frame numbers fulfilling the following equation as "PRACH blocked frames" as specified in [33]. SFN = k * Repetition period for an integer k with k {0, 1, 2, 3, 4, ... , value of IE "Number of repetitions per SFN period" - 1}, where: Repetition period is: 4096 / value of IE "Number of repetitions per SFN period".
3GPP
Release 6
319
3GPP TS 25.331 V6.23.0 (2009-09)
The UE shall configure the physical layer for the physical random access procedure accordingly.
8.6.6.3
Void
8.6.6.3a
Downlink information per radio link list
If the IE "Downlink information per radio link list" is included in a received message, the UE shall: 1> if the active set resulting after the reception of the IE "Downlink information per radio link list" would contain radio links indicated by the IE "Downlink DPCH info for each RL" and radio links indicated by the IE "Downlink F-DPCH info for each RL": 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message: 2> for FDD, check whether the radio links included in the IE "Downlink information per radio link list" are part of the current active set considering that a radio link is uniquely identified by the downlink UARFCN and the primary scrambling code; 2> for TDD, check whether the radio links included in the IE "Downlink information per radio link list" are part of the current active set considering that a radio link is uniquely identified by the UARFCN and the primary CCPCH; 2> if all radio links included in the IE "Downlink information per radio link list" are part of the current active set: 3> for radio links part of the current active set, and present in the IE "Downlink information per radio link list": 4> update the downlink physical channel configuration according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4. 3> for radio links part of the current active set, and absent in the IE "Downlink information per radio link list": 4> not change its current downlink physical channel configuration; 4> For FDD, in case the IE "Serving HS-DSCH radio link indicator" is set to 'TRUE' for another radio link, no longer consider any of these absent radio links as serving HS-DSCH radio link; 4> For FDD, in case the IE "Serving E-DCH radio link indicator" is set to 'TRUE' for another radio link, no longer consider any of these absent radio links as serving E-DCH radio link. 2> if all radio links included in the IE "Downlink information per radio link list" are not part of the current active set: 3> perform a hard handover by replacing all the radio links in the current active set with the radio links in the IE "Downlink information per radio link list", each with a downlink physical channel configuration according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4; 3> perform the checks on the value of the IE "Default DPCH Offset Value" as specified in subclause 8.3.5.1.2 or 8.3.5.2.2; 3> act on the IE "Timing indication" and the IE "Default DPCH Offset Value", if included, as specified in subclause 8.5.15.2; NOTE: UTRAN should not mix radio links which are part of the current active set and radio links which are not part of the current active set in the same IE "Downlink information per radio link list". In such cases the UE behaviour is unspecified.
1> otherwise:
3GPP
Release 6
320
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the message was received in CELL_FACH state and the UE would transit to CELL_DCH state according to subclause 8.6.3.3 applied on the received message: 3> establish a downlink physical channel configuration for each of the included radio links according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4.
8.6.6.4
Downlink information for each radio link
If the IE "Downlink information for each radio link" is included in a received message, the UE shall: 1> if the UE would enter CELL_DCH state according to subclause 8.6.3.3 applied on the received message: 2> if the UE is in TDD mode and shared transport channels are assigned to the UE: 3> start to receive the indicated Secondary CCPCH. 2> if the UE is in TDD mode and no shared transport channels are assigned to the UE: 3> set the variable UNSUPPORTED_CONFIGURATION to TRUE. 2> For FDD: 3> if the IE "Serving HS-DSCH radio link indicator" is set to 'TRUE': 4> consider this radio link as the serving HS-DSCH radio link and no longer consider any other radio link as serving HS-DSCH radio link. 2> For FDD: 3> if the IE "Serving E-DCH radio link indicator" is set to 'TRUE': 4> consider this radio link as the serving E-DCH radio link and no longer consider any other radio link as serving E-DCH radio link. 3> if the IE "E-AGCH Info" is included for the serving E-DCH radio link: 4> store the newly received E-AGCH configuration. NOTE: The UTRAN should always include the IE "E-AGCH info" if the serving E-DCH radio link indicated in the message is another radio link than the serving E-DCH radio link prior to the procedure.
3> if the IE "E-HICH information" is included: 4> store this E-HICH configuration for the concerning radio link. 3> if the IE "E-HICH information" is included or previously stored: 4> store this E-RGCH configuration for the concerning radio link, if included. 3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. 2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link. 1> in addition, if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message: 2> For FDD: 3> if the IE "Serving HS-DSCH radio link indicator" is set to 'TRUE': 4> consider this radio link as the serving HS-DSCH radio link; 4> if the serving HS-DSCH radio link was another radio link than this radio link prior to reception of the message and the IE "H-RNTI" is not included:
3GPP
Release 6
321
3GPP TS 25.331 V6.23.0 (2009-09)
5> clear the variable H_RNTI. 3> if the IE "Serving HS-DSCH radio link indicator" is set to FALSE and this radio link was considered the serving HS-DSCH radio link prior to reception of this message: 4> no longer consider this radio link as the serving HS-DSCH radio link. 3> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 3> if the IE "Serving E-DCH radio link indicator" is set to 'TRUE': 4> consider this radio link as the serving E-DCH radio link; 4> if the serving E-DCH radio link was another radio link than this radio link prior to reception of the message: 5> if the IE "New Primary E-RNTI" is not included: 6> clear the Primary E-RNTI stored in the variable E_RNTI. 5> if the IE "New Secondary E-RNTI" is not included: 6> clear the Secondary E-RNTI stored in the variable E_RNTI. 3> if the IE "Serving E-DCH radio link indicator" is set to FALSE and this radio link was considered the serving E-DCH radio link prior to reception of this message: 4> no longer consider this radio link as the serving E-DCH radio link. 3> if the IE "E-HICH release indicator" is present: 4> delete the stored E-HICH, E-AGCH and E-RGCH (if any) configurations. 3> if the IE "E-RGCH release indicator" is present: 4> delete the stored E-RGCH configuration for this RL. 3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. 2> For TDD: 3> if the IE "H-RNTI" is not included and the primary CCPCH has changed: 4> clear the variable H_RNTI. 3> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. 2> for each optional IE part of the IE "Downlink information for each radio link" that is not present: 3> do not change its current downlink physical channel configuration corresponding to the IE, which is absent, if not stated otherwise elsewhere. NOTE: The Release '99 RADIO BEARER RECONFIGURATION message always includes at least one IE "Downlink information for each radio link" containing the mandatory IEs, even if UTRAN does not require the reconfiguration of any radio link.
1> if the UE would enter either the CELL_FACH, CELL_PCH or URA_PCH state according to subclause 8.6.3.3 applied on the received message: 2> if IEs other than the IE "Primary CPICH info" (for FDD) or the IE "Primary CCPCH info" (for TDD) are included in the IE "Downlink information for each radio link": 3> ignore these IEs.
3GPP
Release 6
322
3GPP TS 25.331 V6.23.0 (2009-09)
2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link.
8.6.6.5
Void
8.6.6.6
Uplink DPCH info
If the IE "Uplink DPCH info" is included, the UE shall: For FDD: 1> release any active uplink physical channels and activate the given physical channels; 1> if the IE "Number of FBI bits" is not included: 2> use 0 FBI bits in the Uplink DPCH. 1> use an SF equal to or greater than the minimum SF indicated in the IE "Spreading Factor" during uncompressed frames or compressed frames by HL scheduling; 1> use an SF equal to or greater than the minimum SF divided by 2 during compressed frames by SF reduction. For TDD: 1> release the uplink physical channels associated with any CCTrCH that is removed or reconfigured and activate the physical channels assigned to any CCTrCH that is added or reconfigured; 1> for 3.84 Mcps TDD use the IE "UL target SIR" specified for each added or reconfigured CCTrCH as described in subclause 8.5.7. For 1.28 Mcps TDD use the value of IE UL target SIR specified for each added or reconfigured CCTrCH for parameter PRXDPCHdes as described in subclause 8.5.7; 1> use the parameters of the IE "Time info" for each added or reconfigured CCTrCH; 1> if present, use the IE "Uplink Timing Advance Control" as specified in subclause 8.6.6.26.
8.6.6.7
Void
8.6.6.8
Maximum allowed UL TX power
If the IE "Maximum allowed UL TX power" is included in the Handover to UTRAN Command, in any other dedicated message or in System Information Block type 3 or in System Information Block 4, the UE shall: 1> store and use the value until it is updated. If the IE "Maximum allowed UL TX power" was not included in any dedicated message, the UE shall: 1> use the value previously stored, when received in an earlier dedicated message, Handover to UTRAN Command message or received in System Information Block type 3 or in System Information Block 4. For all cases, the UE shall: 1> keep the UE uplink transmit power at or below the indicated power value; 1> if the current UE uplink transmit power is above the indicated power value: 2> decrease the power to a level at or below the power value. The maximum UE TX power is defined as the lower of the maximum output power of the UE power class and the maximum allowed UL TX power indicated in this IE. The maximum UE TX power shall not be exceeded.
3GPP
Release 6
323
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.6.9
Void
8.6.6.10
Void
8.6.6.11
The UE shall: 1> in FDD:
Uplink DPCH power control info
2> if the IE "Uplink DPCH power control info" is included: 3> if a synchronisation procedure A is performed according to [29]: 4> calculate and set an initial uplink transmission power; 4> start inner loop power control as specified in subclause 8.5.3; 4> for the UL inner loop power control: 5> use the parameters specified in the IE. 3> else: 4> ignore the IEs "DPCCH Power offset", "PC Preamble" and "SRB delay"; 4> act on the IE "Power control algorithm" and the IE "TPC step size", if included. 3> act on the IEs "ACK", "NACK" and "Ack-Nack repetition factor", if included; 3> use the procedure for transmitting HS-DPCCH preamble and postamble according to [29], if the IE "HARQ_preamble_mode" is set to 1. 1> in 3.84 Mcps TDD: 2> if the IE "Uplink DPCH power control info" is included: 3> use the parameters specified in the IE for open loop power control as defined in subclause 8.5.7. 2> else: 3> use the current uplink transmission power. 1> in 1.28 Mcps TDD: 2> if the CHOICE UL OL PC info is set to 'Broadcast UL OL PC info': 3> set the variable INVALID_CONFIGURATION to true. 2> if the IE "Uplink DPCH power control info"is included in the UPLINK PHYSICAL CHANNEL CONTROL message: 3> use "Beacon PL Est. " and the TPC step size for the closed loop power control of the CCTrCH identified in the message, replacing the existing value used for the CCTrCH. 3> if the IE " UL target SIR " is included: 4> use this value for parameter PRXDPCHdes for open loop power control of the CCTrCH identified in the message in the case of a transition from closed loop to open loop power control as specified in [33]. 2> if the IE "Uplink DPCH power control info" is included in the IE "Uplink DPCH info":
3GPP
Release 6
324
3GPP TS 25.331 V6.23.0 (2009-09)
3> use the "Beacon PL Est. " and TPC step size for the closed loop power control of all CCTrCH added or reconfigured by the IE replacing any existing values used for the CCTrCHs; 3> if the IE " UL target SIR " is included ignore the parameter. 1> both in FDD and TDD; 2> if the IE "Uplink DPCH power control info" is not included in a message used to enter CELL_DCH: 3> set the variable INVALID_CONFIGURATION to true. 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.
8.6.6.12
Secondary CPICH info
If the IE Secondary CPICH info is included, the UE may: 1> use the channelisation code according to IE "channelisation code", with scrambling code according to IE "DL scrambling code" in the IE "Secondary CPICH info", for channel estimation of that radio link; 1> use the pilot bits on DPCCH for channel estimation. If the IE Secondary CPICH info is not included, the UE shall: 1> not use any previously stored configuration corresponding to the usage of the Secondary CPICH info.
8.6.6.13
Primary CPICH usage for channel estimation
If the IE "Primary CPICH usage for channel estimation" is included and has the value "Primary CPICH may be used" the UE: 1> may use the Primary CPICH for channel estimation; 1> may use the pilot bits on DPCCH for channel estimation. NOTE: If the IE "Primary CPICH usage for channel estimation" has the value "Primary CPICH shall not be used" and the IE "Secondary CPICH info" is not included for that radio link then the UE behaviour is not specified.
If the IE "Primary CPICH usage for channel estimation" is included and has the value "Primary CPICH shall not be used" the UE: 1> shall not use the Primary CPICH for channel estimation; 1> may use the Secondary CPICH for channel estimation; 1> may use the pilot bits on DPCCH for channel estimation.
8.6.6.14
DPCH frame offset (FDD Only)
If "DPCH frame offset" is included in a message that instructs the UE to enter CELL_DCH state: 1> UTRAN should: 2> if only one Radio Link is included in the message: 3> if the UE is configured for DPCH: 4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting the following relation: (Default DPCH Offset Value) mod 38400 = DPCH frame offset where the IE values used are the Actual Values of the IEs as defined in clause 11.
3> if the UE is configured for F-DPCH:
3GPP
Release 6
325
3GPP TS 25.331 V6.23.0 (2009-09)
4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting one of the following relations: 5> (Default DPCH Offset Value) mod 38400 = DPCH frame offset; or 5> (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset, where the IE values used are the Actual Values of the IEs as defined in clause 11.
2> if more than one Radio Link are included in the message: 3> if the UE is configured for DPCH: 4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting the following relation: (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.
3> if the UE is configured for F-DPCH: 4> set "Default DPCH Offset Value" and "DPCH frame offsetj" respecting one of the following relations: 5> (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj; or 5> (Default DPCH Offset Value+256) mod 38400 = DPCH frame offsetj, 1> The UE shall: 2> if only one Radio Link is included in the message: 3> if the UE is configured for DPCH: 4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset: 5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 4> else: 5> set the variable INVALID_CONFIGURATION to true. 3> if the UE is configured for F-DPCH: 4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset: 5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 4> else if (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset: 5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value + 256. 4> else: 5> set the variable INVALID_CONFIGURATION to true. 2> if more than one Radio Links are included in the message: 3> if the UE is configured for DPCH: 4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj, where j indicates the first radio link listed in the message: where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.
5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 4> else:
3GPP
Release 6
326
3GPP TS 25.331 V6.23.0 (2009-09)
5> set the variable INVALID_CONFIGURATION to true. 3> if the UE is configured for F-DPCH: 4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offsetj,, where j indicates the first radio link listed in the message:
5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value. 4> else if (Default DPCH Offset Value+256) mod 38400 = DPCH frame offsetj , where j indicates the first radio link listed in the message:
5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value + 256. 4> else: 5> set the variable INVALID_CONFIGURATION to true. If the IE "DPCH frame offset" is included the UE shall: 1> use its value to determine the beginning of the DPCH or F-DPCH frame.
8.6.6.15
DPCH Compressed mode info
If the IE "DPCH compressed mode info" is included, and if the IE group "transmission gap pattern sequence configuration parameters" is included, the UE shall for each transmission gap pattern sequence perform the following consistency checks: 1> if the UE, according to its measurement capabilities, and for all supported bands of the UTRA mode or RAT associated with the measurement purpose indicated by IE "TGMP", requires UL compressed mode, and CHOICE 'UL/DL mode' indicates 'DL only': 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the UE, according to its measurement capabilities, and for all supported bands of the UTRA mode or RAT associated with the measurement purpose indicated by IE "TGMP", requires DL compressed mode, and CHOICE 'UL/DL mode' indicates 'UL only': 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the UE, according to its measurement capabilities, does not require UL compressed mode for any of supported band of the UTRA mode or RAT associated with the measurement purpose indicated by the IE "TGMP", and CHOICE 'UL/DL mode' indicates 'UL only' or 'UL and DL': 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if the UE, according to its measurement capabilities, does not require DL compressed mode for any supported band of the UTRA mode or RAT associated with the measurement purpose indicated by the IE "TGMP", and CHOICE 'UL/DL mode' indicates 'DL only' or 'UL and DL': 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if UE already has an active transmission gap pattern sequence that, according to IE "TGMP", has the same measurement purpose, and both patterns will be active (according to the IE "Current TGPS Status Flag" in variable TGPS_IDENTITY) after the new configuration has been taken into use: 2> set the variable INVALID_CONFIGURATION to TRUE. 1> if there is any pending "TGPS reconfiguration CFN" or any pending "TGCFN": 2> the UE behaviour is unspecified. If variable INVALID_CONFIGURATION has value FALSE after UE has performed the checks above, the UE shall:
3GPP
Release 6
327
3GPP TS 25.331 V6.23.0 (2009-09)
1> if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag") in the variable TGPS_IDENTITY): 2> if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence: 3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use. 3> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "inactive" at the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use. 2> if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence: 3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use. NOTE1: The temporary deactivation of pattern sequences for which the status flag is set to "activate" can be used by the network to align the timing of already active patterns with newly activated patterns. NOTE2: The deactivation of pattern sequences only occurs as a result of RRC messages received by the UE, i.e. the UE does not set the "Current TGPS Status Flag" to "inactive" after the final gap of a finite length pattern sequence. 1> update each pattern sequence to the variable TGPS_IDENTITY according to the IE "TGPSI"; 1> update into the variable TGPS_IDENTITY the configuration information defined by IE group" transmission gap pattern sequence configuration parameters "; 1> if an F-DPCH is configured: 2> not use the IEs "Downlink compressed mode method", "Downlink frame type", "DeltaSIR1", "DeltaSIRafter1", and if included, the IEs "DeltaSIR2", "DeltaSIRafter2". 1> after the instant in which the message is to be executed, as specified in subclause 8.6.3.1: 2> activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" in the variable TGPS_IDENTITY is set to "activate" at the time indicated by IE "TGCFN"; and 2> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "active". NOTE1: If the pattern is activated with a message that includes the IE "Activation time", and if the CFN value indicated by the IE "Activation Time" and the CFN value indicated by the TGCFN are included in the same TTI (but not at the TTI boundary) common to all the transport channels that are multiplexed onto the reference CCTrCh (as defined in subclause 8.6.3.1), and if the CFN value indicated by the TGCFN is equal or higher than the CFN value indicated by the IE "Activation Time" (as defined in subclause 8.6.3.1) value, the UE behaviour is not specified. NOTE2: If the pattern is activated with a message used to perform timing re-initialised hard handover, the UE can start evaluating the activation of the pattern (i.e. compare the value of the CFN in the new configuration with the value of the TGCFN) at any time between the message activation time and the completion of the synchronisation procedure A. 2> if the IE "DPCH compressed mode info" is included in a message used to perform a Hard Handover with change of frequency (see subclause 8.3.5); or 2> if the IE "DPCH compressed mode info" is included in a message used to transfer the UE from Cell_FACH to Cell_DCH, and the cell in which the UE transited from CELL_FACH state is not included in the active set for the CELL_DCH state (see subclause 8.4.1.7.2): 3> not begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence. 2> else:
3GPP
Release 6
328
3GPP TS 25.331 V6.23.0 (2009-09)
3> begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence. 2> begin the inter-RAT measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence; 2> if the new configuration is taken into use at the same CFN as indicated by IE "TGCFN": 3> start the concerned pattern sequence immediately at that CFN. 1> monitor if the parallel transmission gap pattern sequences create an illegal overlap, and in case of overlap, take actions as specified in subclause 8.2.11.2. If the IE "DPCH compressed mode info" is included, and if the IE group "transmission gap pattern sequence configuration parameters" is not included, the UE shall: 1> if, as the result of this message, UE will have more than one transmission gap pattern sequence with the same measurement purpose active (according to IEs "TGMP" and "Current TGPS Status Flag" in variable TGPS_IDENTITY): 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if there is any pending "TGPS reconfiguration CFN" or any pending "TGCFN": 2> the UE behaviour is unspecified. 1> if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag" in the variable TGPS_IDENTITY): 2> if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence: 3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use; 3> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "inactive" at the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use. 2> if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence: 3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use. NOTE1: The temporary deactivation of pattern sequences for which the status flag is set to "activate" can be used by the network to align the timing of already active patterns with newly activated patterns. NOTE2: The deactivation of pattern sequences only occurs as a result of RRC messages received by the UE, i.e. the UE does not set the "Current TGPS Status Flag" to "inactive" after the final gap of a finite length pattern sequence. 1> after the instant in which the message is to be executed, as specified in subclause 8.6.3.1: 2> activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" is set to "activate" at the time indicated by IE "TGCFN"; and NOTE1: If the pattern is activated with a message that includes the IE "Activation time", and if the CFN value indicated by the IE "Activation Time" and the CFN value indicated by the TGCFN are included in the same TTI (but not at the TTI boundary) common to all the transport channels that are multiplexed onto the reference CCTrCh (as defined in subclause 8.6.3.1), and if the CFN value indicated by the TGCFN is equal or higher than the CFN value indicated by the IE "Activation Time" (as defined in subclause 8.6.3.1) value, the UE behaviour is not specified.
3GPP
Release 6
329
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE2: If the pattern is activated with a message used to perform timing re-initialised hard handover, the UE can start evaluating the activation of the pattern (i.e. compare the value of the CFN in the new configuration with the value of the TGCFN) at any time between the message activation time and the completion of the synchronisation procedure A. 2> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "active"; 2> if the IE "DPCH compressed mode info" is included in a message used to perform a Hard Handover with change of frequency (see subclause 8.3.5); or 2> if the IE "DPCH compressed mode info" is included in a message used to transfer the UE from Cell_FACH to Cell_DCH, and the cell in which the UE transited from CELL_FACH state is not included in the active set for the CELL_DCH state (see subclause 8.4.1.7.2): 3> not begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence. 2> else: 3> begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence. 2> begin the inter-RAT measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence; 2> if the new configuration is taken into use at the same CFN as indicated by IE "TGCFN": 3> start the concerned pattern sequence immediately at that CFN. For transmission gap pattern sequences stored in variable TGPS_IDENTITY, but not identified in IE "TGPSI" (either due to the absence of the IE "DPCH compressed mode info" in the received message or due to not receiving the corresponding TGPSI value in the IE "DPCH compressed mode info"), the UE shall: 1> if the received message implies a timing re-initialised hard handover (see subclause 8.3.5.1): 2> deactivate such transmission gap pattern sequences at the beginning of the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message; and 2> set IE "Current TGPS Status Flag" in corresponding UE variable TGPS_IDENTITY to 'inactive'. 1> if the received message not implies a timing re-initialised hard handover (see subclause 8.3.5.1): 2> continue such transmission gap pattern sequence according to IE "Current TGPS Status Flag" in the corresponding UE variable TGPS_IDENTITY. Uplink and downlink compressed mode methods are described in [27]. For UL "higher layer scheduling" compressed mode method and transport format combination selection, see [15].
8.6.6.16
Repetition period, Repetition length, Offset (TDD only)
In case the physical allocations of different channels overlap the following priority rules shall apply for common channels and shall be taken into account by the UE: 1> PICH takes precedence over Primary CCPCH; 1> PICH takes precedence over Secondary CCPCH; 1> MICH takes precedence over Primary CCPCH; 1> MICH takes precedence over Secondary CCPCH; 1> Secondary CCPCH takes precedence over Primary CCPCH. The frame allocation can be derived by following rules: If no IE "Offset" is explicitly given, the parameter "Offset" to be used is calculated by the following equation:
3GPP
Release 6
330
3GPP TS 25.331 V6.23.0 (2009-09)
Activation time mod Repetition period = Offset. Frames from CFN CFNoff to CFNoff + Repetition length - 1 belong to the allocation with CFNoff fulfilling the following equation: CFNoff mod Repetition period = Offset. Repetition length is always a multiple of the largest TTI within the CCTrCH fulfilling the following equation: (largest TTI within CCTrCH) * X = Repetition Length Example of usage:
0 C o d e s 64 frames physic. channel (Code 7; Repetition period=8; Repetition length=5; Activation time = 4 => Offset = 4 => CFNoff = 4, 12, 20, 28, 36, 44, 52, 60) physic. channel (Code 5; Repetition Period=1 => Repetition length=0; Offset = 0 => CFNoff = 0, 1, 2, 3, 4, ... (continuous allocation)) physic. channel (Code 3; Repetition period=16; Repetition length=3; Activation time = 23 =>Offset = 7 => CFNoff = 7, 23, 39, 55 ) 10 20 30 40 50 60
Figure 8.6.6.16-1: Examples for frame allocations in TDD
8.6.6.17
Primary CCPCH info
If the IE "Primary CCPCH info" is included, the UE shall: 1> use the information elements in this IE.
8.6.6.18
Primary CPICH info
If the IE "Primary CPICH info" in FDD is included, the UE shall: 1> use the value of this IE as the primary scrambling code for the downlink radio link.
8.6.6.19
Void
8.6.6.20
Void
8.6.6.21
Void
8.6.6.22
Secondary Scrambling Code, Code Number
The following description applies to FDD.
3GPP
Release 6
331
3GPP TS 25.331 V6.23.0 (2009-09)
Code Number can be assigned by following rules: 1> When more than one DL DPDCH is assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to [27]. When p number of DL DPDCHs are assigned to each RL, the first pair of Secondary Scrambling Code and Code Number corresponds to "PhCH number 1", the second to "PhCH number 2", and so on until the pth to "PhCH number p".
8.6.6.23
The UE shall:
PDSCH Power Control info
1> if the IE "PDSCH Power Control info" is included: 2> configure PDSCH power control with the received values. 1> if the IE "PDSCH Power Control info" is not included: 2> continue to use the stored values.
8.6.6.24
Tx Diversity Mode
If the IE "Tx Diversity Mode" is included the UE shall: 1> if the value of the IE "Tx Diversity Mode" is STTD: 2> configure the Layer 1 to use the Tx diversity mode indicated in the IE "Tx Diversity Mode" for the radio links for which the IE "Closed loop timing adjustment mode" is included, ignoring the actual value of IE "Closed loop timing adjustment mode". 1> if the value of the IE "Tx Diversity Mode" is closed loop mode 1: 2> configure the Layer 1 to use the Tx diversity mode indicated in the IE "Tx Diversity Mode" for the radio links for which the IE "Closed loop timing adjustment mode" is included, using the actual value of the IE "Closed loop timing adjustment mode". 1> if the value of the IE "Tx Diversity Mode" is "none": 2> configure the Layer 1 not to use Tx diversity for all radio links in the active set. If the IE "Tx Diversity Mode" is not included, the UE shall: 1> continue to use the already configured Tx diversity mode; 1> in case no Tx diversity mode has been configured: 2> do not apply Tx diversity. For F-DPCH the UE shall: 1> if the IE "STTD indication" is included in the IE "Downlink F-DPCH info for each RL": 2> use STTD for F-DPCH on the radio links for which the IE "STTD indication" is set to TRUE. For HS-SCCH, the UE shall: 1> if the DPCH associated with a HS-SCCH is using either open or closed loop transmit diversity on the radio link transmitted from the HS-DSCH serving cell: 2> use STTD for this HS-SCCH; 1> if the F-DPCH associated with an HS-SCCH is using open loop transmit diversity on the radio link transmitted from the HS-DSCH serving cell: 2> use STTD for this HS-SCCH. 1> otherwise:
3GPP
Release 6
332
3GPP TS 25.331 V6.23.0 (2009-09)
2> not use Tx diversity for this HS-SCCH. For E-AGCH, E-RGCH, and E-HICH from the same cell, the UE shall: 1> for each radio link: 2> if the DPCH associated with E-AGCH, E-RGCH, and E-HICH from the same cell is using either open or closed loop transmit diversity: 3> use STTD for these E-AGCH, E-RGCH, and E-HICH. 2> if the F-DPCH associated with E-AGCH, E-RGCH, and E-HICH from the same cell is using open loop transmit diversity: 3> use STTD for these E-AGCH, E-RGCH, and E-HICH. 2> otherwise: 3> not use Tx diversity for these E-AGCH, E-RGCH, and E-HICH.
8.6.6.25
Void
8.6.6.26
UL Timing Advance Control (TDD only)
If the IE "UL Timing Advance Control" is present, the UE shall: 1> if the IE "Uplink Timing Advance Control" has the value "disabled": 2> reset timing advance to 0; 2> disable calculated timing advance following handover; 2> in case of handover: 3> start uplink transmissions in the target cell without applying timing advance. 1> if the IE "Uplink Timing Advance Control" has the value "enabled": 2> in 3.84 Mcps TDD: 3> in case of no cell change: 4> evaluate and apply the timing advance value for uplink transmission as indicated in the IE "Uplink Timing Advance" at the CFN indicated in the IE "Activation Time". 3> in case of cell change: 4> use the IE "Uplink Timing Advance" as TAold and apply TAnew for uplink transmission in the target cell at the CFN indicated in the IE "Activation Time" as specified in [33]; 4> include the value of the applied timing advance in the IE "Timing Advance" in the COMPLETE message. 2> in 1.28 Mcps TDD: 3> if the IE "Synchronisation parameters" is included: 4> initiate a sequence of UpPCH SYNC_UL code transmissions using a code selected from the set specified and continue until a timing correction is received in the specified FPACH (received for WT sub-frames following the sub-frame in which the transmission was made) or until Max SYNC_UL transmissions have been completed. The power used for each SYNC_UL transmission is as specified in subclause 8.5.7. Each transmission is made in the first sub-frame possible following the end of each FPACH reception interval using the timing specified in [33]. A new code is selected for each
3GPP
Release 6
333
3GPP TS 25.331 V6.23.0 (2009-09)
transmission. The detection that the FPACH relates to the transmitted SYNC_UL code is described in [33]; 4> if a timing correction is received within Max SYNC_UL transmissions the procedure is completed. The assigned uplink resources may then be used, commencing at the first possible TTI boundary or the SFN in which the assignment commences, whichever is the later. The timing of the uplink transmission is described in [33]; 4> if no timing correction has been received within Max SYNC_UL transmissions, the synchronisation procedure has failed. If the assigned resources are DCH, the UE should not transmit using these resources and should respond as if a physical channel failure has occurred as specified in subclauses 8.1.3.7 or 8.2.2.7 or 8.3.1.7, or 8.3.6.5. If the assigned resources are USCH then the UE should ignore the USCH allocation. 3> if the IE "Synchronisation parameters" is not included: 4> in case of no cell change: 5> continue to use the current uplink timing. 4> in case of cell change: 5> evaluate and apply the timing correction TAnew for uplink transmissions using the procedure as specified in [33].
8.6.6.26a
Uplink synchronisation parameters (TDD only)
The UE shall apply uplink synchronisation using the values of the IEs "Uplink synchronisation step size" and "Uplink synchronisation frequency" as specified in [33].
8.6.6.27
Downlink information common for all radio links
If the IE "Downlink information common for all radio links " is included the UE shall: 1> if the IE "Downlink DPCH info common for all RL" is included: 2> perform actions as specified in subclause 8.6.6.28. 1> if the IE "Downlink F-DPCH info common for all RL" is included: 2> perform actions as specified in subclause 8.6.6.28a. 1> if the IE choice "mode" is set to 'FDD': 2> perform actions for the IE "DPCH compressed mode info" as specified in subclause 8.6.6.15; 2> perform actions for the IE "Tx Diversity mode" as specified in subclause 8.6.6.24. 1> if the IE "MAC-hs reset indicator" is included: 2> if the serving HS-DSCH radio link is the same radio link as prior to the reception of the message: 3> the UE behaviour is unspecified; 2> reset the MAC-hs entity [15].
8.6.6.28
Downlink DPCH info common for all radio links
If the IE "Downlink DPCH info common for all RL" is included the UE shall: 1> if: 2> the IE "Downlink DPCH info common for all RL" is included in a reconfiguration message; and 2> the UE was in CELL_DCH state upon reception of the message and remains in CELL_DCH state; and
3GPP
Release 6
334
3GPP TS 25.331 V6.23.0 (2009-09)
2> the message is not used to perform a hard handover (as specified in subclause 8.6.6.3a) and the IE "Timing indication" is set to "initialise": 3> the UE behaviour is not specified. 1> if the IE "Downlink DPCH power control information" is included: 2> in the case of FDD: 3> perform actions for the IE "DPC Mode" according to [29]. 2> in the case of TDD: 3> perform actions for the IE "TPC Step Size" according to [33]. 1> if the IE choice "mode" is set to 'FDD': 2> if the IE "Downlink rate matching restriction information" is included: 3> set the variable INVALID_CONFIGURATION to TRUE. 2> perform actions for the IE "spreading factor"; 2> perform actions for the IE "Fixed or Flexible position"; 2> perform actions for the IE "TFCI existence"; 2> if the IE choice "SF" is set to 256: 3> store the value of the IE "Number of bits for pilot bits". 2> if the IE choice "SF" is set to 128: 3> store the value of the IE "Number of bits for pilot bits". If the IE "Downlink DPCH info common for all RL" is included in a message used to perform a Timing re-initialised hard handover or the IE "Downlink DPCH info common for all RL" is included in a message other than RB SETUP used to transfer the UE from a state different from Cell_DCH to Cell_DCH, and ciphering is active for any radio bearer using RLC-TM, the UE shall, after having activated the dedicated physical channels indicated by that IE: 1> if any ciphering configuration for a radio bearer using RLC-TM has not been applied, due to that the activation time from a previous procedure has not elapsed: 2> apply the ciphering configuration immediately and consider the activation time from the previous procedure to be elapsed. 1> if the IE "MAC-d HFN initial value" is included in the IE "Downlink DPCH info common for all RL": 2> set the HFN component of COUNT-C for TM-RLC to the value of the IE "MAC-d HFN initial value", while not incrementing the value of the HFN component of COUNT-C at each CFN cycle. NOTE: The UTRAN should choose a value for the IE "MAC-d HFN initial value" using the COUNT-C value of the RBs using RLC-TM indicated by the Source RNC to the Target RNC in the IE "SRNS Relocation Info" and include some margin in such a way that no values of COUNT-C are repeated after the handover.
1> else: 2> set the 20 MSB of the HFN component of COUNT-C for TM-RLC to the value of the latest transmitted IE "START" or "START List" for this CN domain, while not incrementing the value of the HFN component of COUNT-C at each CFN cycle; and 2> set the remaining LSBs of the HFN component of COUNT-C to zero. 1> start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN;
3GPP
Release 6
335
3GPP TS 25.331 V6.23.0 (2009-09)
1> include the IE "COUNT-C activation time" in the response message and specify a CFN value for this IE other than the default, "Now", that is a multiple of 8 frames (CFN mod 8 =0) and lies at least 200 frames ahead of the CFN in which the response message is first transmitted; 1> calculate the START value according to subclause 8.5.9; 1> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in the response message; 1> at the CFN value as indicated in the response message in the IE "COUNT-C activation time": 2> set the 20 MSB of the HFN component of the COUNT-C variable common for all transparent mode radio bearers of this CN domain to the START value as indicated in the IE "START list" of the response message for the relevant CN domain; and 2> set the remaining LSBs of the HFN component of COUNT-C to zero; 2> increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is equal to zero; 2> set the CFN component of the COUNT-C to the value of the IE "COUNT-C activation time" of the response message. The HFN component and the CFN component completely initialise the COUNT-C variable; 2> step the COUNT-C variable, as normal, at each CFN value, i.e. the HFN component is no longer fixed in value but incremented at each CFN cycle.
8.6.6.28a
Downlink F-DPCH info common for all radio links
If the IE "Downlink F-DPCH info common for all RL" is included the UE shall: 1> if the IE "Downlink F-DPCH info common for all RL" is included in a message used to perform a hard handover: 2> perform actions for the IE "Timing indication" as specified in subclause 8.5.15.2, and subclause 8.3.5.1 or 8.3.5.2. 1> if the IE "Downlink DPCH power control information" is included: 2> perform actions for the IE "DPC Mode" according to [29].
8.6.6.29
ASC setting
If the IE "ASC setting" is included, the UE shall: 1> establish the available signatures for this ASC as specified in the following: 2> renumber the list of available signatures specified in the IE "Available signature" included in the IE "PRACH info" from signature index 0 to signature index N-1, where N is the number of available signatures, starting with the lowest available signature number and continuing in sequence, in the order of increasing signature numbers; 2> consider as available signatures for this ASC the signatures included in this renumbered list from the index specified by the IE "Available signature Start Index" to the index specified by the IE "Available signature End Index". 1> establish the available access slot sub-channels for this ASC as specified in the following: 2> if the IE "AICH transmission timing" included in the IE "AICH Info" is set to '0'; 3> ignore the leftmost (most significant) bit (bit b3) of the bit string specified by the IE "Assigned SubChannel Number"; 3> repeat 4 times the 3 rightmost (least significant) bits (bits b2-b0) of the bit string specified by the IE "Assigned Sub-Channel Number" to form a resulting bit string 'b2 b1 b0 b2 b1 b0 b2 b1 b0 b2 b1 b0' of length 12 bits, where the leftmost bit is the most significant.
3GPP
Release 6
336
3GPP TS 25.331 V6.23.0 (2009-09)
2> if the IE "AICH transmission timing" included in the IE "AICH Info" is set to '1': 3> repeat 3 times the bit string (bits b3-b0) specified by the IE "Assigned Sub-Channel Number" to form a bit string 'b3 b2 b1 b0 b3 b2 b1 b0 b3 b2 b1 b0' of length 12 bits, where the leftmost bit is the most significant. 2> perform in both cases, for the resulting bit string (that includes the repetitions) bit-wise logical AND operation with the IE "Available Sub Channel number" included in IE "PRACH info (for RACH)"; 2> consider as available sub-channels for this ASC the available sub-channels indicated in the resulting bit string, after logical AND operation i.e. each bit set to 1 or 0 indicates availability or non-availability, respectively, of sub-channel number x, with x from 0 to 11, for the respective ASC. NOTE 1: In FDD, the list of available signatures is renumbered from signature index 0 to signature index N-1, where N is the number of available signatures, starting with the lowest available signature number and continuing in sequence, in the order of increasing signature numbers. - List of available signatures: 16 or fewer signatures are available. - Example: only signatures 0, 5, 10 and 15 are available, then : - Signature 0 is: available signature index 0 - Signature 5 is: available signature index 1 - Signature 10 is: available signature index 2 - Signature 15 is: available signature index 3 NOTE 2: In 3.84 Mcps TDD, the list of available channelisation codes (defined in PRACH info) is renumbered from channelisation code index 0 to channelisation code index N-1, where N is the number of available channelisation codes, starting with the lowest available channelisation code number and continuing in sequence, in the order of increasing channelisation code numbers List of available channelisation codes : 8 or less channelisation codes are available. The i-th bit of the bitmap defined in the IE "Available Channelisation Code indices" defines whether the channelisation code with the available channelisation code index i is to be used for this ASC (bit set means used, bit unset means not used). Only the low N bits shall be used in the bitmap, where N is the number of available channelisation codes defined in PRACH info. Ex : spreading factor 16, channelisation codes 16/1, 16/2, 16/5, 16/8 are available : Channelisation code 16/1 is: available channelisation code index 0 Channelisation code 16/2 is: available channelisation code index 1 Channelisation code 16/5 is: available channelisation code index 2 Channelisation code 16/8 is: available channelisation code index 3 Available Channelisation Code indices has the value '00001100' means: Channelisation Codes 16/5 and 16/8 are available for this ASC. NOTE 3: In TDD, the subchannel description is found in [33].
3GPP
Release 6
337
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE 4: In 1.28 Mcps TDD, the list of available SYNC_UL codes (defined in PRACH info) is numbered from SYNC_UL code index 0 to SYNC_UL code index N-1, where N is the number of available SYNC_UL codes, starting with the lowest available SYNC_UL code number and continuing in sequence, in the order of increasing SYNC_UL code numbers The i-th bit of the bitmap defined in the IE "Available SYNC_UL codes indices" defines whether the SYNC_UL code with the available SYNC_UL code index i is to be used for this ASC (bit set means used, bit unset means not used). Only the low N bits shall be used in the bitmap, where N is the number of available SYNC_UL codes defined in PRACH info. - List of available SYNC_UL codes: 8 or fewer SYNC_UL codes are available. Example: only signatures 0, 5, 6 and 7 are available, then: - SYNC_UL codes 0 is: available SYNC_UL codes index 0 - SYNC_UL codes 5 is: available SYNC_UL codes index 1 - SYNC_UL codes 6 is: available SYNC_UL codes index 2 - SYNC_UL codes 7 is: available SYNC_UL codes index 3 Available SYNC_UL codes indices has the value '00001100' means: SYNC_UL codes 6 and 7 are available for this ASC.
8.6.6.30
SRB delay, PC preamble (FDD only)
When the IE "SRB delay" and IE "PC preamble" is received in a message that results in a configuration of uplink DPCH or E-DPCH and synchronisation procedure A is being used as specified in [29], the UE shall: 1> store the received IE "SRB delay" and IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; 1> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble"; and 1> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" or while the physical channel is not considered established.
8.6.6.31
Void
8.6.6.32
Void
8.6.6.33
HS-SCCH Info
If the IE "HS-SCCH Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall: 1> store the received configuration. 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall: 1> in the case of FDD: 2> receive the HS-SCCH(s) according to the IE "HS-SCCH channelisation code" on the serving HS-DSCH radio link applying the scrambling code as received in the IE "DL Scrambling code". 1> in the case of TDD:
3GPP
Release 6
338
3GPP TS 25.331 V6.23.0 (2009-09)
2> receive the HS-SCCH(s) according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs. 2> transmit the HS-SICH according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs. 2> for HS-SCCH power control the UE shall use the "BLER target" signalled in the first occurrence of the "HSSCCH Set Configuration". 2> in 3.84 Mcps TDD: 3> use the parameters specified in the IE "HS-SICH power control info" for open loop power control as defined in subclause 8.5.7. 2> in 1.28 Mcps TDD: 3> use the IE " PRXHS-SICH " to calculate and set an initial uplink transmission power; 3> use the IE " TPC step size" upon reception of TPC commands for closed loop power control; 3> use default value of "Uplink synchronisation frequency" and same value of "Uplink synchronisation step size" in "Uplink DPCH info" for HS-SICH upon reception of SS commands for closed loop uplink synchronisation on HS-SICH.
8.6.6.34
Measurement Feedback Info
If the IE "Measurement Feedback Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall: 1> store the received configuration; 1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25. When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall: 1> use the information for the channel quality indication (CQI) procedure in the physical layer on the serving HSDSCH radio link.
8.6.6.35
DPC Mode
If the IE "DPC Mode" is included, the UE shall: 1> apply the indicated DPC mode according to [29]. If the IE "DPC Mode" is not included, the UE shall: 1> continue with the currently used DPC mode.
8.6.6.36
Downlink HS-PDSCH Information
If the IE "Downlink HS-PDSCH Information" is included and the UE would be in CELL_DCH state after completion of this procedure, the UE shall: 1> if the IE "HS-SCCH Info" is included: 2> act as specified in subclause 8.6.6.33. 1> if the IE "Measurement Feedback Info" is included: 2> act as specified in subclause 8.6.6.34. 1> if the IE "HS-DSCH Timeslot Configuration" or "HS-PDSCH Midamble Configuration" is included: 2> store the received configuration;
3GPP
Release 6
339
3GPP TS 25.331 V6.23.0 (2009-09)
2> determine the value for the HS_DSCH_RECEPTION variable and take actions as described in subclause 8.5.25.
8.6.6.37
E-DCH Info
If the IE "E-DCH Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall: 1> if the IE "E-DPCCH Info" is included: 2> store the newly received E-DPCCH configuration. 1> if the IE "E-DPDCH Info" is included: 2> store the newly received E-DPDCH configuration. NOTE 1: The UTRAN should ensure the ordering of the E-TFCI table in strictly increasing order of transmission power prior to quantization, by correct setting of the reference E-TFCI power offsets otherwise the UE behaviour is unspecified. NOTE 2: If a reference E-TFCI signalled to the UE is outside the UE physical channel capability, the UE behaviour is unspecified. 1> if the IE "MAC-es/e reset indicator" is included: 2> reset the MAC-es/e entity [15]. NOTE: If the IE "MAC-es/e reset indicator" is not set to TRUE in case the IE E-DCH Transmission Time Interval is reconfigured, the UE behaviour is unspecified.
1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28. When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall: 1> configure the UL E-DPCCH in accordance with the stored IE "E-DPCCH" configuration; 1> configure the MAC with the stored IE "E-DPDCH" configuration and/or the information contained in IE "Scheduled Transmission configuration".
8.6.7
Measurement information elements
On reception of measurement information elements the UE shall: 1> store the received information in the variable MEASUREMENT_IDENTITY and CELL_INFO_LIST as specified; 1> perform further actions as specified in subclause 8.6.7 and subclause 8.4, based on the content of the variable MEASUREMENT_IDENTITY. If a configuration is considered to be invalid the UE may: 1> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.1
Measurement validity
If the IE "measurement validity" for a given measurement has not been included in measurement control information, the UE shall delete the measurement associated with the variable MEASUREMENT_IDENTITY after the UE makes a transition to a new state. If the IE "measurement validity" for this measurement has been included in measurement control information, the UE shall save the measurement associated with the variable MEASUREMENT_IDENTITY. The IE "UE state" defines the scope of resuming the measurement.
3GPP
Release 6
340
3GPP TS 25.331 V6.23.0 (2009-09)
If the "UE state" is defined as "all states", the UE shall continue the measurement after making a transition to a new state. This scope is assigned for traffic volume measurement type and UE positioning measurement type. For traffic volume measurement type this scope can only be applied by the UE if the IE " traffic volume measurement object" has been included in measurement control information. If the IE " traffic volume measurement object" has not been included in measurement control information, the UE shall not save the measurement control information in variable MEASUREMENT_IDENTITY, but shall send a MEASUREMENT CONTROL FAILURE message to the UTRAN with failure cause "Configuration incomplete". If the "UE state" is defined as "all states except CELL_DCH", the UE shall store the measurement to be resumed after a subsequent transition from CELL_DCH state to any of the other states in connected mode. This scope is assigned for traffic volume measurement type or UE positioning measurement type. If the "UE state" is defined as "CELL_DCH", the UE shall store the measurement to be resumed after a subsequent transition to CELL_DCH state. If the IE "measurement type" received in a MEASUREMENT CONTROL message is set to "inter-frequency measurement" or "intra-frequency measurement" and the IE "measurement validity" is present and is set to a value other than "CELL_DCH", the UE behaviour is unspecified.
8.6.7.2
Filter coefficient
If the IE "Filter coefficient" is received the UE shall, depending on the measurement quantity (see Table 8.6.7.2), apply filtering of the measurements for that measurement quantity according to the formula below. This filtering shall be performed by the UE before UE event evaluation. The UE shall depending on the reporting quantity (see Table 8.6.7.2), also filter the measurements reported in the IE "Measured results". The filtering shall not be performed for the measurements reported in the IE "Measured results on RACH" and for cell-reselection in connected or idle mode. The filtering shall be performed according to the following formula.
Fn = (1 a ) Fn1 + a M n
The variables in the formula are defined as follows: Fn is the updated filtered measurement result Fn-1 is the old filtered measurement result Mn is the latest received measurement result from physical layer measurements, the unit used for Mn is the same unit as the reported unit in the MEASUREMENT REPORT message or the unit used in the event evaluation. a = 1/2(k/2), where k is the parameter received in the IE "Filter coefficient". NOTE: if k is set to 0 that will mean no layer 3 filtering.
In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received. The physical layer measurement results are sampled once every measurement period. The measurement period and the accuracy for a certain measurement is defined in [19] and [20]. Table 8.6.7.2 lists for all measurement quantities and reporting quantities if L3-filtering is applicable or not and used L3-filtering type for each measurement quantity. Table 8.6.7.2: L3 filtering applicable for each measurement quantity and reporting quantity Measurement- / Reporting quantity Pathloss Cell synchronisation information Cell Identity Frequency quality estimate L3-filtering applicable Yes No No No Linear or logarithmic filtering Log Comment
Although the frequency quality estimate itself is not filtered, the inputs to the frequency quality estimate
3GPP
Release 6
341
3GPP TS 25.331 V6.23.0 (2009-09)
calculation (CPICH Ec/N0 or CPICH RSCP or P-CCPCH RSCP) are filtered UTRA carrier RSSI GSM carrier RSSI UE transmitted power FDD > UE Rx-Tx time difference > CPICH Ec/N0 > CPICH RSCP TDD > Primary CCPCH RSCP > Proposed TGSN > Timeslot ISCP > TADV (1.28 Mcps TDD) > Applied TA (3.84 Mcps TDD) Yes Yes Yes No Yes Yes Yes No Yes No No Log Log Log Log Log Log Log -
The UE shall support 2 different layer 3 filters per measurement type defined in subclause 8.4.0 (i.e. the UE shall be capable to apply at least 2 different L3 filters to intra-frequency measurement results see NOTE, at least 2 different L3 filters to inter-frequency measurement results, etc.). If a MEASUREMENT CONTROL message is received that would require the UE to configure more than 2 different layer 3 filters, the UE may: 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. NOTE: Any L3 filter applied to a measurement configured with measurement quantity and/or reporting quantity that evaluates or reports measurement results for the current used frequency, is counted as one intrafrequency L3 filter, and is therefore included in the count of used intra-frequency filters.
8.6.7.3
Intra-frequency/Inter-frequency/Inter-RAT cell info list
If the IE "Intra-frequency cell info list" is received in System Information Block Type 11, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the IE "Intra-frequency cell removal" is received: 2> ignore the IE. 1> if the IE "New Intra-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Intra-frequency cell id" is received: 4> store received cell information at this position in the Intra-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Intra-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Intra-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Intra-frequency cell info list" is received in System Information Block Type 11bis and System Information Block type 11bis is supported by the UE, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows:
3GPP
Release 6
342
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "Intra-frequency cell id" is received: 4> store received cell information at this position in the Intra-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Intra-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Intra-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Intra-frequency cell info list" is received in System Information Block Type 12, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the IE "Intra-frequency cell removal" is received: 2> if it has the value "Remove some intra-frequency cells", at the position indicated by the IE "Intra-frequency cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant". 2> if it has the value "Remove all intra-frequency cells": 3> for each position referring to an intra-frequency cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no intra-frequency cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Intra-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Intra-frequency cell id" is received: 4> store received cell information at this position in the Intra-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Intra-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Intra-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Intra-frequency cell info list" is received in a MEASUREMENT CONTROL message, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the CHOICE "Intra-frequency cell removal" is received: 2> if it has the value "Remove some intra-frequency cells", at the position indicated by the IE "Intra-frequency cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant".
3GPP
Release 6
343
3GPP TS 25.331 V6.23.0 (2009-09)
2> if it has the value "Remove all intra-frequency cells": 3> for each position referring to an intra-frequency cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no intra-frequency cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Intra-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Intra-frequency cell id" is received: 4> store received cell information at this position in the Intra-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Intra-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Intra-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". 1> if the IE "Cells for measurement" is received, in the measurement configured by this message only: 2> consider Intra-frequency cells whose cell information is stored at the position indicated by the IE "Intrafrequency cell id" in the variable CELL_INFO_LIST. 1> if the IE "Cells for measurement" is not received, in the measurement configured by this message: 2> consider all Intra-frequency cells whose cell information is stored in CELL_INFO_LIST. If the IE "Inter-frequency cell info list" is received in System Information Block Type 11 update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the IE "Inter-frequency cell removal" is received: 2> ignore the IE. 1> if the IE "New Inter-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Inter-frequency cell id" is received: 4> store received cell information at this position in the Inter-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Inter-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Inter-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied".
3GPP
Release 6
344
3GPP TS 25.331 V6.23.0 (2009-09)
If the IE "Inter-frequency cell info list" is received in System Information Block Type 11bis and System Information Block type 11bis is supported by the UE, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Inter-frequency cell id" is received: 4> store received cell information at this position in the Inter-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Inter-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Inter-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Inter-frequency cell info list" is received in System Information Block Type 12, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the CHOICE "Inter-frequency cell removal" is received: 2> if it has the value "Remove some inter-frequency cells", at the position indicated by the IE "Inter-frequency cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant". 2> if it has the value "Remove all inter-frequency cells": 3> for each position referring to an inter-frequency cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no inter-frequency cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Inter-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Inter-frequency cell id" is received: 4> store received cell information at this position in the Inter-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Inter-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Inter-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Inter-frequency cell info list" is received in a MEASUREMENT CONTROL message, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order:
3GPP
Release 6
345
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the CHOICE "Inter-frequency cell removal" is received: 2> if it has the value "Remove some inter-frequency cells", at the position indicated by the IE "Inter-frequency cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant". 2> if it has the value "Remove all inter-frequency cells": 3> for each position referring to an inter-frequency cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no inter-frequency cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Inter-frequency cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Inter-frequency cell id" is received: 4> store received cell information at this position in the Inter-frequency cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Inter-frequency cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Inter-frequency cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". 1> if the IE "Cells for measurement" is received, in the measurement configured by this message only: 2> consider Inter-frequency cells whose cell information is stored at the position indicated by the IE "Interfrequency cell id" in the variable CELL_INFO_LIST. 1> if the IE "Cells for measurement" is not received, in the measurement configured by this message: 2> consider all Inter-frequency cells whose cell information is stored in CELL_INFO_LIST. If the IE "Inter-RAT cell info list" is received in System Information Block Type 11, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> ignore the IE "Inter-RAT cell removal". 1> if the IE "New Inter-RAT cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> if the IE "Radio Access Technology" is set to "None": 3> ignore the cell. 2> otherwise: 3> update the variable CELL_INFO_LIST as follows: 4> if the IE "Inter-RAT cell id" is received: 5> store received cell information at this position in the Inter-RAT cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and
3GPP
Release 6
346
3GPP TS 25.331 V6.23.0 (2009-09)
5> mark the position "occupied". 4> if the IE "Inter-RAT cell id" is not received: 5> store the received cell information at the first vacant position in ascending order in the Inter-RAT cell info list in the variable CELL_INFO_LIST; and 5> mark the position as "occupied". 1> if the IE "Cells for measurement" is received: 2> ignore the IE. 1> set the "Inter-RAT cell info indication" to the value "0" and mark the indication status "present" in the variable CELL_INFO_LIST. If the IE "Inter-RAT cell info list" is received in System Information Block Type 11bis and System Information Block type 11bis is supported by the UE, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> for each cell, and in the same order as the cells appear in the IE: 2> update the variable CELL_INFO_LIST as follows: 3> if the IE "Inter-RAT cell id" is received: 4> store received cell information at this position in the Inter-RAT cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 4> mark the position "occupied". 3> if the IE "Inter-RAT cell id" is not received: 4> store the received cell information at the first vacant position in ascending order in the Inter-RAT cell info list in the variable CELL_INFO_LIST; and 4> mark the position as "occupied". If the IE "Inter-RAT cell info list" is received in System Information Block Type 12, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the IE "Inter-RAT cell removal" is received: 2> if it has the value "Remove some inter-RAT cells", at the position indicated by the IE "Inter-RAT cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant". 2> if it has the value "Remove all inter-RAT cells": 3> for each position referring to an inter-RAT cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no inter-RAT cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Inter-RAT cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> if the IE "Radio Access Technology" is set to "None": 3> ignore the cell. 2> otherwise:
3GPP
Release 6
347
3GPP TS 25.331 V6.23.0 (2009-09)
3> update the variable CELL_INFO_LIST as follows: 4> if the IE "Inter-RAT cell id" is received: 5> store received cell information at this position in the Inter-RAT cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 5> mark the position "occupied". 4> if the IE "Inter-RAT cell id" is not received: 5> store the received cell information at the first vacant position in ascending order in the Inter-RAT cell info list in the variable CELL_INFO_LIST; and 5> mark the position as "occupied". 1> if the IE "Cells for measurement" is received: 2> ignore the IE; 1> set the "Inter-RAT cell info indication" to the value "0" and mark the indication status "present" in the variable CELL_INFO_LIST. If the IE "Inter-RAT cell info list" is received in a MEASUREMENT CONTROL message, the UE shall update the variable CELL_INFO_LIST accordingly and in the following order. The UE shall: 1> if the IE "Inter-RAT cell removal" is received: 2> if it has the value "Remove some inter-RAT cells", at the position indicated by the IE "Inter-RAT cell id": 3> clear the cell information stored in the variable CELL_INFO_LIST; and 3> mark the position "vacant". 2> if it has the value "Remove all inter-RAT cells": 3> for each position referring to an inter RAT cell in the variable CELL_INFO_LIST: 4> clear the cell information stored in the variable CELL_INFO_LIST; and 4> mark the position "vacant". 2> if it has the value "Remove no inter-RAT cells": 3> leave the variable CELL_INFO_LIST unchanged. 1> if the IE "New Inter-RAT cells" is received, for each cell, and in the same order as the cells appear in the IE: 2> if the IE "Radio Access Technology" is set to "None": 3> ignore the cell. 2> otherwise: 3> update the variable CELL_INFO_LIST as follows: 4> if the IE "Inter-RAT cell id" is received: 5> store received cell information at this position in the Inter-RAT cell info list in the variable CELL_INFO_LIST, possibly overwriting any existing information in this position; and 5> mark the position "occupied". 4> if the IE "Inter-RAT cell id" is not received: 5> store the received cell information at the first vacant position in ascending order in the Inter-RAT cell info list in the variable CELL_INFO_LIST; and
3GPP
Release 6
348
3GPP TS 25.331 V6.23.0 (2009-09)
5> mark the position as "occupied". 1> if the IE "Cells for measurement" is received, in the measurement configured by this message only: 2> consider Inter-RAT cells whose cell information is stored at the position indicated by the IE "Inter-RAT cell id" in the variable CELL_INFO_LIST. 1> if the IE "Cells for measurement" is not received, in the measurement configured by this message: 2> consider all Inter-RAT cells whose cell information is stored in CELL_INFO_LIST. 1> if the IE "Cell selection and re-selection info for SIB11/12" is present: 2> ignore the IE. 1> if the IE "Inter-RAT cell info indication" is present: 2> store the received value of the IE "Inter-RAT cell info indication" and mark the indication status "present" in the variable CELL_INFO_LIST. 1> if the IE "Inter-RAT cell info indication" is not present: 2> clear the "Inter-RAT cell info indication" and mark the indication status "not present" in the variable CELL_INFO_LIST. NOTE: If UTRAN signalling would result in more than "maxCellMeas" cells for the Intra-frequency, Interfrequency or Inter-RAT cell information list the UE behaviour is unspecified.
8.6.7.4
Intra-frequency measurement quantity
If the IE "Intra-frequency measurement quantity" is received in a MEASUREMENT CONTROL message, the UE shall: 1> if the IE "Measurement quantity" is set to "pathloss"; and 1> for any intra-frequency cell indicated by the IE "Cells for measurement", the IE "Primary CPICH Tx power" in FDD or the IE "Primary CCPCH TX Power" in TDD in the intra frequency cell info list in the variable CELL_INFO_LIST is not present: 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> else: 2> configure the measurement quantity accordingly.
8.6.7.5
Inter-RAT measurement quantity
If the IE "Inter-RAT measurement quantity" is received in a MEASUREMENT CONTROL message and CHOICE system is GSM, the UE shall: 1> if IE "BSIC verification required" is set to "required", for cells that match any of the BCCH ARFCN and BSIC combinations in the list of inter-RAT cells that the UE has received in IE "Inter-RAT cell info list", and that has a "verified" BSIC: 2> report measurement quantities according to IE "inter-RAT reporting quantity" taking into account the restrictions defined in subclause 8.6.7.6; 2> trigger inter-RAT events according to IE "inter-RAT measurement reporting criteria"; and 2> perform event evaluation for event-triggered reporting after BSIC has been verified for a GSM cell as defined in [19]; and 2> trigger periodical reports according to the given "Reporting interval"; and 2> when a periodical measurement report is triggered, include only BSIC verified GSM cells in the IE "InterRAT measured results list"; and
3GPP
Release 6
349
3GPP TS 25.331 V6.23.0 (2009-09)
3> indicate verified BSIC for a GSM cell in the IE "Inter-RAT measured results list" as defined in subclause 8.6.7.6. 2> when an event triggered measurement report is triggered, include only BSIC verified GSM cells in the IE "Inter-RAT measured results list"; and 3> indicate verified BSIC for a GSM cell in the IE "Inter-RAT measured results list" as defined in subclause 8.6.7.6. 1> if IE "BSIC verification required" is set to "not required", for cells that match any of the BCCH ARFCN in the list of inter-RAT cells that the UE has received in IE "Inter-RAT cell info list", regardless if the BSIC is "verified" or "non-verified": 2> report measurement quantities according to IE "inter-RAT reporting quantity"; 2> trigger inter-RAT events according to IE "inter-RAT measurement reporting criteria"; 2> when an event triggered or periodical measurement report is triggered, include GSM cells in the IE "InterRAT measured results list" regardless of whether the BSIC of the GSM cell has been verified or not; and 3> for any GSM cell that has not been verified, indicate non-verified BSIC for a GSM cell in the "Inter-RAT measured results list" IE as defined in subclause 8.6.7.6. 3> for any GSM cell that has been verified, indicate verified BSIC for a GSM cell in the "Inter-RAT measured results list" IE as defined in subclause 8.6.7.6. 1> if the IE "Measurement quantity" is set to "pathloss": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. NOTE: The requirements for a cell to be considered "verified" or "non-verified" can be found in [19].
8.6.7.6
Inter-RAT reporting quantity
If the IE "Inter-RAT reporting quantity" is received by the UE, the UE shall: 1> store the content of the IE to the variable MEASUREMENT_IDENTITY. If the IE "Inter-RAT measurement quantity" is received and CHOICE system is GSM, the UE shall check each quantity in the GSM choice. The UE shall include measured results in MEASUREMENT REPORT as specified in the IE "InterRAT reporting quantity" with the following restrictions: 1> if the UE has not confirmed the BSIC of the measured cell: 2> if no compressed mode pattern sequence specified with measurement purpose "Initial BSIC identification" is active and according to its capabilities the UE requires compressed mode to measure this, the UE is not required to include the "inter-RAT cell id" in the IE "Inter-RAT measured results list", when a MEASUREMENT REPORT is triggered. 1> if the UE has confirmed the BSIC of the measured cell, then: 2> if no compressed mode pattern sequence specified with measurement purpose "Initial BSIC identification" nor "BSIC re-confirmation" is active and according to its capabilities the UE requires compressed mode to measure this, the UE is not required to include the "inter-RAT cell id" in the IE "Inter-RAT measured results", when a MEASUREMENT REPORT is triggered. If no compressed mode pattern sequence with measurement purpose "GSM carrier RSSI measurements" is active and according to its capabilities the UE requires compressed mode to measure this, the UE may include "inter-RAT cell id" in MEASUMENT REPORT without "GSM carrier RSSI" even if it is defined in the IE "Inter-RAT reporting quantity". 1> if the IE "UTRAN estimated quality" is set to "TRUE": 2> ignore that IE. 1> if IE "GSM Carrier RSSI" is set to "TRUE":
3GPP
Release 6
350
3GPP TS 25.331 V6.23.0 (2009-09)
2> include optional IE "GSM Carrier RSSI" with a value set to the measured RXLEV to that GSM cell in IE "Inter-RAT measured results list". If no compressed mode pattern sequence specified with measurement purpose "GSM carrier RSSI measurements" is active and according to its capabilities the UE requires compressed mode to measure this, the UE is not required to include the "GSM carrier RSSI" in the IE " InterRAT measured results list ", when a MEASUREMENT REPORT is triggered. 1> if the BSIC of reported GSM cell is "verified": 2> set the CHOICE BSIC to "Verified BSIC" and IE "inter-RAT cell id" to the value that GSM cell had in the IE "Inter-RAT cell info list". 1> if the BSIC of reported GSM cell is "non-verified": 2> set the CHOICE BSIC to "Non verified BSIC" and the IE "BCCH ARFCN" to the value of that GSM cells ARFCN. The requirements for a cell to be considered "verified" or "non-verified" can be found in [19].
8.6.7.7
Cell Reporting Quantities
If the IE "Cell Reporting Quantities" is received by the UE, the UE shall store the content of the IE "Cell Reporting Quantities" to the variable MEASUREMENT_IDENTITY. The UE shall include measured results in MEASUREMENT REPORT as specified in the IE "Cell Reporting Quantities", except for the following cases: If the IE "Cell Identity" is set to TRUE, the UE shall in this version of the specification: 1> treat the IE as if the IE "Cell Identity" is set to FALSE. If the IE "Cell synchronisation information reporting indicator" is set to TRUE, the UE shall: 1> include the IE "Cell synchronisation information" in MEASUREMENT REPORT as specified in the IE "Cell Reporting Quantities": 2> if the measurement is performed on another frequency; or 2> if the IE "Read SFN indicator" included in the IE "Cell info" of the measured cell is set to FALSE: 3> the UE may omit the information group "COUNT-C-SFN frame difference" in the IE "Cell synchronisation information". 2> if the measurement is performed on the same frequency and no RLC Transparent Mode COUNT-C exists in the UE: 3> set the IE "COUNT-C-SFN high" to 0. 2> otherwise: 3> include the information group "COUNT-C-SFN frame difference" with IE "COUNT-C-SFN high" set to: COUNT-C-SFN high = (((SFN - (COUNT-C mod 4096)) mod 4096) div 256) * 256; 3> if RLC Transparent Mode COUNT-Cs exist in both CN domains: 4> use the COUNT-C of CS domain in this measurement. If the IE "Proposed TGSN Reporting required" is set to TRUE, the UE shall: 1> if compressed mode was used to monitor a TDD cell and the variable TGSN_REPORTED is set to FALSE: 2> report the IE "Proposed TGSN" indicating the TGSN that suits best to the measured cell; 2> set the variable TGSN_REPORTED to TRUE. 1> otherwise
3GPP
Release 6
351
3GPP TS 25.331 V6.23.0 (2009-09)
2> omit the IE "Proposed TGSN".
8.6.7.8
Periodical Reporting Criteria
If the IE "Periodical Reporting Criteria" is received by the UE, the UE shall: 1> store the contents of the IE "Amount of Reporting" and IE "Reporting interval" in the variable MEASUREMENT_IDENTITY. For the first MEASUREMENT REPORT message, the UE shall: 1> send the MEASUREMENT REPORT as soon as all requested reporting quantities are available according to the requirements and the measurement capabilities set in [19] and [20] for at least one measurement object stored in the variable MEASUREMENT_IDENTITY, but never later than one reporting interval after measurement initiation. Following the first MEASUREMENT REPORT message, the UE shall: 1> send a MEASUREMENT REPORT message one reporting interval after the previous MEASUREMENT REPORT message; The first and subsequent periodic MEASUREMENT REPORT messages shall only include measured results for reporting quantities that are available according to the requirements and the measurement capabilities set in [19] and [20] i.e. if no measured results are available and the measurement type is not UE positioning, the IE "Measured Results" shall not be included in the MEASUREMENT REPORT message. If no measured results are available and the measurement type is UE positioning, the UE shall include the IE "Measured Results" in the MEASUREMENT REPORT message in order to include the IE "UE positioning error" as specified in 8.6.7.19a and 8.6.7.19b. After the UE has sent a total number of MEASUREMENT REPORT messages, which equal the value indicated in the IE "Amount of reporting", the UE shall: 1> terminate measurement reporting; and 1> delete all measurement information linked with the "Measurement identity" of the ongoing measurement from the variable MEASUREMENT_IDENTITY. If according to subclause 8.6.7.19.1a or 8.6.7.19.1b, a UE configured with a UE positioning measurement is unable to report the requested measurement results due to missing GPS assistance data and sends a MEASUREMENT REPORT containing the IE "UE positioning error" and the IE "Error reason" is set to "Assistance Data Missing", then this is not counted in the total number of MEASUREMENT REPORT messages sent.
8.6.7.9
Reporting Cell Status
If the IE "Reporting Cell Status" is received, the UE shall set the IE "Measured Results" in MEASUREMENT REPORT as follows. The UE shall: 1> for intra-frequency measurement and inter-frequency measurement: 2> include the IE "Cell Measured Results" for cells (excluding cells of another RAT) that satisfy the condition (such as "Report cells within active set") specified in the IE "Reporting Cell Status", in descending order by the measurement quantity. 2> the maximum number of the IE "Cell Measured Results" to be included in the IE "Measured Results" per reported frequency is the number specified in the IE "Reporting Cell Status". 1> for periodic inter-frequency measurement: 2> include in the IE "Inter-frequency measured results list" the measured results for all non-used frequencies. 1> for inter-RAT measurement: 2> include the measurement results for cells of other RAT (e.g., GSM) that satisfy the condition specified in the IE "Reporting Cell Status", in descending order by the measurement quantity.
3GPP
Release 6
352
3GPP TS 25.331 V6.23.0 (2009-09)
2> the maximum number of the IE "Measured GSM Cells" to be included in the IE "Measured Results" is the number specified in the IE "Reporting Cell Status". If the IE "Reporting Cell Status" is not received for intra-frequency, inter-frequency measurement, or inter-RAT measurement, the UE shall: 1> for intra-frequency measurement, inter-frequency measurement and inter-RAT measurement: 2> exclude the IE "Measured Results" in MEASUREMENT REPORT. NOTE: The IE "Reporting Cell Status" within "Event Criteria List" defines whether "Cell Measured Results" is present for event-based reporting.
The IE "Reporting Cell Status" is not included in System Information Block 11/12 for periodic intra-frequency measurements. In this case the UE shall assume the default values "Report cells within active set and/or monitored set on used frequency " and "6".
8.6.7.10
Traffic Volume Measurement
If the IE "Traffic Volume Measurement" is received by the UE, the UE shall: 1> store the content of the IE to the variable MEASUREMENT_IDENTITY. If IE "Traffic volume measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", and if the IE "traffic volume reporting quantity" is included, the UE shall: 1> if the parameter "Average of RLC Buffer Payload for each RB" or the parameter "Variance of RLC Buffer payload for each RB" is set to "TRUE": 2> if the IE "Traffic volume measurement quantity" is not included: 3> set the variable CONFIGURATION_INCOMPLETE to TRUE. 2> if the IE "Traffic volume measurement quantity" is included: 3> if the parameter "time interval to take an average or a variance" is not included: 4> set the variable CONFIGURATION_INCOMPLETE to TRUE. If IE "Traffic volume measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "Traffic volume reporting quantity" or is not received, the UE shall: 1> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.11
Traffic Volume Measurement Reporting Criteria
If the IE "Traffic Volume Measurement Reporting Criteria" is received by the UE, the UE shall: 1> if the IE "Parameters sent for each transport channel" is absent: 2> set the variable PROTOCOL_ERROR_REJECT to TRUE; 2> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Information element missing". 1> for each IE "Parameters sent for each transport channel": 2> if the IE "Parameters required for each Event" is absent: 3> set the variable CONFIGURATION_INCOMPLETE to TRUE.
3GPP
Release 6
353
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.12
FACH measurement occasion info
IE "FACH measurement occasion info" is used to control UE measurement activities in inter-frequency and inter-RAT cells in CELL_FACH state. If IE "FACH measurement occasion info" is received, UE shall, when in CELL_FACH state: 1> if IE "FACH Measurement occasion cycle length coefficient" is included: 2> if, according to its measurement capabilities, UE is not able to perform some of the indicated measurements in this IE simultaneously as receiving the SCCPCH of serving cell: 3> perform those measurements during FACH measurement occasions, see subclause 8.5.11. 2> if, according to its measurement capabilities, UE is able to perform some of the indicated measurements in this IE simultaneously as receiving the SCCPCH of serving cell: 3> UE may perform measurements also on other occasions. 2> if, according to its measurement capabilities, UE is able to perform the measurements and indicated in this IE simultaneously as receiving the SCCPCH of serving cell: 3> perform the measurements simultaneously as receiving the SCCPCH of serving cell. 1> if IE "FACH Measurement occasion cycle length coefficient" is not included: 2> perform those indicated measurements indicated in this IE that UE, according to its measurement capabilities, is able to perform simultaneously as receiving the SCCPCH of serving cell. 1> if IE "Inter-frequency FDD measurement indicator" is set to TRUE: 2> perform measurements and evaluate cell re-selection criteria according to [4] on inter-frequency FDD cells listed in "System Information Block type 11", "System Information Block type 11bis", if scheduled on BCH and supported by the UE, and "System Information Block type 12", if scheduled on BCH. 1> if IE "Inter-frequency FDD measurement indicator" is set to FALSE: 2> neither perform measurements nor evaluate cell re-selection criteria on inter-frequency FDD cells. 1> if IE "Inter-frequency TDD measurement indicator" is set to TRUE: 2> perform measurements and evaluate cell re-selection criteria according to [4] on inter-frequency TDD cells listed in "System Information Block type 11", "System Information Block type 11bis", if scheduled on BCH and supported by the UE, and "System Information Block type 12", if scheduled on BCH. 1> if IE "Inter-frequency TDD measurement indicator" is set to FALSE: 2> neither perform measurements nor evaluate cell re-selection criteria on inter-frequency TDD cells. 1> if IE "Inter-RAT measurement indicators" is included: 2> perform measurements and evaluate cell re-selection criteria according to [4] on those cells of listed InterRAT types that are present in "System Information Block type 11", "System Information Block type 11bis" and supported by the UE, if scheduled on BCH, and "System Information Block type 12", if scheduled on BCH.
8.6.7.13
Measurement Reporting Mode
If IE "Measurement Reporting Mode" is received by the UE, the UE shall: 1> store the contents of the IE "Measurement Report Transfer Mode" in the variable MEASUREMENT_IDENTITY; 1> use the indicated RLC mode when sending MEASUREMENT REPORT message(s) related to this measurement; 1> ignore IE "Periodical Reporting / Event Trigger Reporting Mode".
3GPP
Release 6
354
3GPP TS 25.331 V6.23.0 (2009-09)
If IE "Measurement Reporting Mode" is not received by the UE in MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.14
If the Inter-frequency cell info list, included in the variable CELL_INFO_LIST, includes a number (M) of frequencies that is larger than the number (N) considered in a UE performance requirement defined in [19] and [20]: 1> the UE shall: 2> meet this performance requirement on the first relevant (N) frequencies, according to the order defined by the position of the frequencies in the Inter-frequency cell info list, included in the variable CELL_INFO_LIST. 1> the UE may: 2> ignore the remaining (M-N) frequencies. If IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "Inter-frequency measurement quantity", IE "Inter-frequency reporting quantity" or IE "parameters required for each event" (given "CHOICE Report criteria" is set to "interfrequency measurement reporting criteria") is not received, the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. If IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "modify": 1> if CHOICE "Report criteria" in IE "Inter-frequency measurement" is set to "intra-frequency measurement reporting criteria" and IE "parameters required for each event" is present: 2> the UE behaviour is unspecified. If IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup" and CHOICE "Report criteria" in IE "Inter-frequency measurement" is set to "intra-frequency measurement reporting criteria": 1> the UE behaviour is unspecified. In the case of an inter-frequency measurement for FDD, the UE shall: 1> if IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", if an inter-frequency event is configured that is different from event 2d or 2f, and if the IE "Inter-frequency SET UPDATE" is not received in that same message: 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. NOTE: The UTRAN should include the IE "Inter-frequency SET UPDATE" in the MEASUREMENT CONTROL message with the IE "measurement command" set to "modify" when event 2a, 2b, 2c or 2e is first configured, and when the UE is requested to measure a frequency that has not been previously measured. Otherwise the UE behaviour is unspecified.
If IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message: 1> if CHOICE "Report criteria" is set to "inter-frequency measurement reporting criteria" and CHOICE "reporting criteria" in "inter-frequency measurement quantity" is not set to "inter-frequency reporting criteria"; or 1> if CHOICE "Report criteria" is set to "intra-frequency measurement reporting criteria" and CHOICE "reporting criteria" in "inter-frequency measurement quantity" is not set to "intra-frequency reporting criteria":
3GPP
Release 6
355
3GPP TS 25.331 V6.23.0 (2009-09)
2> the UE behaviour is not specified. If the variable CONFIGURATION_INCOMPLETE is set to TRUE, the UE shall: 1> act as described in subclause 8.4.1.4a.
8.6.7.15
If the Inter-RAT cell info list, included in the variable CELL_INFO_LIST, includes a number (M) of frequencies that is larger than the number (N) considered in a UE performance requirement defined in [19] and [20]: 1> the UE shall: 2> meet this performance requirement on the first relevant (N) frequencies, according to the order defined by the position of the frequencies in the Inter-RAT cell info list, included in the variable CELL_INFO_LIST. 1> the UE may: 2> ignore the remaining (M-N) frequencies. If IE "Inter-RAT measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "Inter-RAT measurement quantity", IE "Inter-RAT reporting quantity" or "parameters required for each event" (given "CHOICE Report criteria" is set to "inter-RAT measurement reporting criteria") is not received, the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.16
If IE "Intra-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "Intra-frequency measurement quantity", IE "Intra-frequency reporting quantity", "CHOICE Report criteria" or "parameters required for each event" (given "CHOICE report criteria" is set to "intra-frequency measurement reporting criteria") is not received, the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. In case of 1a or 1e event-triggered reporting: 1> if the IE "Intra-frequency measurement quantity" is set to "pathloss", the UE shall: 2> if detected set cells are indicated as possibly triggering the event within the IEs "Triggering condition 2" : 3> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.17
Quality measurement
If IE "Quality measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "Quality reporting quantity" is not received, the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. If Transport Channel BLER reporting is requested in IE "Quality Reporting Quantity", but no transport channels are explicitly referenced with transport channel identities, the UE shall 1> report BLER for all downlink transport channels, for which Transport Channel BLER is defined and can be requested [7, 8].
3GPP
Release 6
356
3GPP TS 25.331 V6.23.0 (2009-09)
If a transport channel, for which Transport Channel BLER is not defined and can not be requested [7, 8], is referenced with a transport channel identity in IE "Quality Reporting Quantity" and/or IE "Quality Measurement Reporting Criteria": 1> the UE behaviour is not specified.
8.6.7.18
If IE "UE internal measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE "measurement command" has the value "setup", but IE "UE internal measurement quantity", IE "UE internal reporting quantity" or "parameters sent for each UE internal measurement event" (given "CHOICE report criteria" is set to "UE internal measurement reporting criteria") is not received, the UE shall: 1> clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTITY; 1> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.18a
Void
8.6.7.19
8.6.7.19.0
UE positioning
UE positioning reporting criteria
If IE "UE positioning reporting criteria" is included, the UE shall: 1> perform the necessary measurements and evaluate the event in the interval indicated in IE "Measurement Interval"; 1> if IE "Event ID" is set to "7a" and if IE "Report first fix" is set to TRUE: 2> if the IE "Method Type" included in the variable MEASUREMENT_IDENTITY is set to "UE based": 3> act as specified in subclause 8.6.7.19.1b.
8.6.7.19.1
The UE shall:
UE positioning reporting quantity
1> ignore IE "Multiple Sets"; 1> ignore IE "Response Time"; 1> if IE "Horizontal Accuracy" and/or IE "Vertical Accuracy" is included: 2> should try to achieve the requested level(s) of positioning accuracy with 67% confidence. 1> if IE "Positioning Methods" is set to "Cell ID": 2> act as specified in subclause 8.6.7.19.1a. 1> if the IE "Method Type" is set to "UE based": 2> act as specified in subclause 8.6.7.19.1b. 1> if the IE "Method Type" is set to "UE assisted": 2> act as specified in subclause 8.6.7.19.1a. 1> if the IE "Method Type" is set to "UE-assisted preferred but UE-based allowed" or "UE-based preferred but UEassisted allowed":
3GPP
Release 6
357
3GPP TS 25.331 V6.23.0 (2009-09)
2> act either according to subclause 8.6.7.19.1a or 8.6.7.19.1b depending on the method type chosen by the UE. If UE according to its capabilities supports Rx-Tx time difference type 2 measurement and if IE "Positioning Methods" is set to "Cell ID" and the IE "Method Type" is set to "UE-based", the UE shall: 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. If UE according to its capabilities supports Rx-Tx time difference type 2 measurement and if IE "Positioning Methods" is set to "Cell ID" and the IE "Measurement validity" stored in the variable MEASUREMENT_IDENTITY is other than "CELL_DCH", the UE shall: 1> set the variable CONFIGURATION_INCOMPLETE to TRUE. The UE shall perform the following consistency check: 1> if UE, according to its capabilities, does not support UE-based OTDOA and if IE "Positioning Methods" is set to "OTDOA" and if IE "Method Type" is set to "UE-based": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support UE-assisted OTDOA and if IE "Positioning Methods" is set to "OTDOA" and if IE "Method Type" is set to "UE-assisted": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support UE-based GPS and if IE "Positioning Methods" is set to "GPS" and if IE "Method Type" is set to "UE-based": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support UE-assisted GPS and if IE "Positioning Methods" is set to "GPS" and if IE "Method Type" is set to "UE-assisted": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support UE-based positioning and if IE "Positioning Methods" is set to "OTDOAorGPS" and if IE "Method Type" is set to "UE-based": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support Rx-Tx time difference type 2 measurement and if IE "Positioning Methods" is set to "Cell ID": 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if UE, according to its capabilities, does not support UE GPS timing of cell frames measurement and if IE "GPS timing of Cell wanted" is set to TRUE: 2> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.19.1a
The UE shall:
UE positioning reporting for UE assisted methods
1> when a measurement report is triggered: 2> if the UE was able to perform measurements on at least one neighbour cell included in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED in case of OTDOA or one satellite included in the variable UE_POSITIONING_GPS_DATA in case of GPS positioning or one cell from the active set in case of CELL ID: 3> if the IE "Vertical Accuracy" is included: 4> interpret the presence of this IE to indicate that the UTRAN desires to compute a 3-dimensional position estimate. 3> if the IE "Positioning Methods" is set to "GPS":
3GPP
Release 6
358
3GPP TS 25.331 V6.23.0 (2009-09)
4> include the IE "UE positioning GPS measured results" in the measurement report and set the contents of the IE as follows: 5> if the UE supports the capability to provide the GPS timing of the cell frames measurement: 6> if the IE "GPS timing of Cell wanted" is set to TRUE: 7> perform the UE GPS timing of cell frames measurement on the serving cell or on one cell of the active set. 7> include the IE "Primary CPICH Info" for FDD or the IE "cell parameters id" for TDD; and 7> include the IE "Reference SFN" and the IE "UE GPS timing of cell frames". 6> if the IE "GPS timing of Cell wanted" is set to FALSE: 7> include the IE "GPS TOW msec" and set it to the GPS TOW when the measurements included in the MEASUREMENT REPORT were valid. 5> if the UE does not support the capability to provide the GPS timing of the cell: 6> include the IE "GPS TOW msec" and set it to the GPS TOW when the measurements included in the MEASUREMENT REPORT were valid. 3> if the IE "Positioning Methods" is set to "OTDOA": 4> include the IE "UE positioning OTDOA measured results " in the measurement report and set the contents of the IE as follows: 5> set IE "SFN" to the SFN when the last measurement was performed; 5> if the UE supports the capability to perform the Rx-Tx time difference type 2 measurement: 6> if the UE is in CELL_DCH state: 7> if the measured value is equal to "1279.9375": 8> set the IE "Rx-Tx time difference type 2" in IE "UE positioning OTDOA measured results" for the reference cell to "1279.8750". 7> otherwise: 8> set the IE "Rx-Tx time difference type 2" in IE "UE positioning OTDOA measured results" for the reference cell to the measured value. 7> include the IE group "Rx-Tx time difference type 2 info" for the reference cell and for each neighbour cell listed in variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED that belongs to the active set. 5> if the UE does not support the capability to perform the Rx-Tx time difference type 2 measurement: 6> set the IE "Rx-Tx time difference type 2" in IE "UE positioning OTDOA measured results" for the reference cell to value "1279.9375" to indicate that the measurement is not supported. 4> include IE group "Neighbour" for all neighbour cells listed in variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED on which the SFN-SFN observed time difference type 2 measurement could be performed. 3> if IE "Positioning Methods" in the MEASUREMENT CONTROL message has been assigned to value "OTDOA or GPS": 4> the UE may choose to either act as if IE "Positioning Methods" is set to "GPS" or "OTDOA" depending on the method chosen by the UE. 3> if the IE "Positioning Methods" is set to "CELL ID":
3GPP
Release 6
359
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the UE supports the capability to perform the Rx-Tx time difference type 2 measurement; and 4> if the UE is in CELL_DCH state: 5> perform the Rx-Tx time difference type 2 measurement on the cells in the active set; and 5> report the measurement results back to the network in the MEASUREMENT REPORT by using IE "UE positioning OTDOA measured results" including measurements on the cells in the active set; and 5> report Rx-Tx time difference type 2 measurement of the reference cell (as designated by the UE); and 5> for all reported neighbour cells: 6> report Rx-Tx time difference type 2 measurement; and 6> set the IE "SFN-SFN observed time difference type 2" and all IEs within the corresponding IE "UE positioning OTDOA quality" in IE "UE positioning OTDOA measured results" to value "0". 2> if the UE is not able to report the requested measurement results: 3> include IE "UE positioning error" in the MEASUREMENT REPORT and set the contents of this IE as specified in subclause 8.6.7.19.5. 1> if the UE is unable to report the requested measurement results due to missing GPS assistance data: 2> the UE may at anytime send a measurement report containing the IE "UE positioning error" and set the contents of this IE as specified in subclause 8.6.7.19.5. 2> after sending the measurement report, the UE shall not send another measurement report to request the same GPS assistance data for at least 20s. This requirement does not apply after release of the current RRC connection.
8.6.7.19.1b
The UE shall:
UE positioning reporting for UE based methods
1> when a measurement report is triggered: 2> if the UE has been able to calculate a position after performing measurements on the cells included in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED in case of OTDOA or the UE has been able to calculate a position in case of GPS positioning: 3> include IE "UE positioning Position Estimate Info" in the MEASUREMENT REPORT and set the contents of the IE as follows: 4> if the UE supports the capability to perform the UE GPS timing of cell frames measurement: 5> if the IE "GPS timing of Cell wanted" is set to TRUE: 6> of the active set. 6> 6> 6> include the IE "Primary CPICH Info" for FDD or the IE "cell parameters id" for TDD; include the SFN when the position was determined; include the IE "UE GPS timing of cell frames". perform the UE GPS timing of cell frames measurement on the serving cell or on one cell
5> if the IE "GPS timing of Cell wanted" is set to FALSE: 6> include the IE "GPS TOW msec" and set it to the GPS TOW when the position estimate was valid.
3GPP
Release 6
360
3GPP TS 25.331 V6.23.0 (2009-09)
4> if the UE does not support the capability to provide the GPS timing of the cell: 5> include the IE "GPS TOW msec" and set it to the GPS TOW when the position estimate was valid. 4> if IE "Vertical Accuracy" has been included in IE "UE positioning reporting quantity": 5> if the IE "Vertical Accuracy" has been assigned to value "0": 6> if the IE "Horizontal Accuracy" has been assigned a value "0": 7> may include IE "Ellipsoid point with altitude". 6> if the IE "Horizontal Accuracy" has been assigned a value unequal to "0"; and 6> if the UE has been able to calculate a 3-dimensional position 7> include IE "Ellipsoid point with altitude" or IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate. 6> if the UE has not been able to calculate a 3-dimensional position: 7> may act as if IE "Vertical Accuracy" was not included in IE "UE positioning reporting quantity". 5> if the IE "Vertical Accuracy" has been assigned to a value unequal to "0": 6> if the UE has been able to calculate a 3-dimensional position: 7> include IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate. 6> if the UE has not been able to calculate a 3-dimensional position: 7> act as if IE "Vertical Accuracy" has not been included in IE "UE positioning reporting quantity". 4> if IE "Vertical Accuracy" has not been included in IE "UE positioning reporting quantity": 5> if IE "Horizontal Accuracy" in IE "UE positioning reporting quantity" has been assigned to value "0": 6> may include IE "Ellipsoid point". 5> if IE "Horizontal Accuracy" in IE "UE positioning reporting quantity" has been assigned to a value unequal to 0: 6> include either IE "Ellipsoid point with uncertainty circle" or IE "Ellipsoid point with uncertainty ellipse" or IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate. 2> if the UE was not able to calculate a position: 3> include IE "UE positioning error" in the MEASUREMENT REPORT and set the contents of this IE as specified in subclause 8.6.7.19.5. 1> if the UE is unable to calculate a position due to missing GPS assistance data: 2> the UE may at any time send a measurement report containing the IE "UE positioning error" and set the contents of this IE as specified in subclause 8.6.7.19.5; 2> after sending the measurement report, the UE shall not send another measurement report to request the same GPS assistance data for at least 20s. This requirement does not apply after release of the current RRC connection.
3GPP
Release 6
361
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.19.2
UE positioning OTDOA assistance data for UE-assisted
If IE "UE positioning OTDOA reference cell info for UE-assisted" is received in System Information Block type 15.4 or in the MEASUREMENT CONTROL message, the UE shall update the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED accordingly. The UE shall: 1> store received cell information in the UE positioning reference cell info in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED, overwriting any existing information. If IE "UE positioning OTDOA neighbour cell list for UE-assisted" is received in System Information Block type 15.4 or in the MEASUREMENT CONTROL message, the UE shall update the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED accordingly. The UE shall: 1> store received cell information in the neighbour cell info list in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED, overwriting any existing information. If, according to its capabilities, UE does not support IPDLs and if IE "IPDL parameters" is received for the reference or any of the neighbour cells, the UE shall: 1> ignore this IE. In 1.28 Mcps TDD, if the IE "IPDL parameters" is received and the UE supports IPDLs, the UE shall: 1> ignore the IE IP_Slot; 1> if the IE "IP_PCCPCH" is set to FALSE: 2> configure the physical layer with IP_Sub to be first subframe according to [33]. 1> if the IE "IP_PCCPCH" is set to TRUE: 2> configure the physical layer with IP_Sub to be second subframe according to [33]. 1> if the IE "IP_PCCPCH" is absent: 2> configure the physical layer with IP_Sub to use both subframes according to [33]. If IE "SFN offset validity" is set to FALSE, the UE shall: 1> ignore the IE "SFN offset". If IE "UE positioning measurement" is received in the MEASUREMENT CONTROL message, the UE shall also perform the following consistency checks: 1> if IE "Positioning Methods" is set to "OTDOA": 2> if IE "UE positioning OTDOA reference cell info for UE-assisted" is not included and if UE positioning OTDOA reference cell info for UE-assisted in variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED is empty: 3> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if IE "Positioning Methods" is set to "OTDOA": 2> if IE "UE positioning OTDOA neighbour cell list for UE-assisted" is not included and if less than two neighbour cells are stored in UE positioning OTDOA neighbour cell info list for UE-assisted in variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED: 3> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.19.2a
The UE shall:
UE positioning OTDOA assistance data for UE-based
1> if IE "UE positioning OTDOA reference cell info for UE-based" is received in System Information Block type 15.5 or in the MEASUREMENT CONTROL message or in the ASSISTANCE DATA DELIVERY:
3GPP
Release 6
362
3GPP TS 25.331 V6.23.0 (2009-09)
2> update the variable UE_POSITIONING_OTDOA_DATA_UE_BASED accordingly; 2> store received cell information in the UE positioning reference cell info for UE-based in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED, overwriting any existing information. 1> if IE "UE positioning OTDOA neighbour cell list for UE-based" is received in System Information Block type 15.5 or in the MEASUREMENT CONTROL message or in the ASSISTANCE DATA DELIVERY: 2> update the variable UE_POSITIONING_OTDOA_DATA_UE_BASED accordingly; 2> store received cell information in the neighbour cell info list for UE-based in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED, overwriting any existing information. 1> if, according to its capabilities, UE does not support IPDLs and if IE "IPDL parameters" is received for the reference or any of the neighbour cells: 2> ignore this IE. 1> in 1.28 Mcps TDD: 2> if the IE "IPDL parameters" is received and the UE supports IPDLs: 3> ignore the IE IP_Slot; 3> if the IE "IP_PCCPCH" is set to FALSE: 4> configure the physical layer with IP_Sub to be first subframe according to [33]. 3> if the IE "IP_PCCPCH" is set to TRUE: 4> configure the physical layer with IP_Sub to be second subframe according to [33]. 3> if the IE "IP_PCCPCH" is absent: 4> configure the physical layer with IP_Sub to use both subframes according to [33]. 1> if IE "SFN offset validity" is set to FALSE: 2> ignore the IE "SFN offset". 1> if IE "UE positioning measurement" is received in the MEASUREMENT CONTROL message: 2> also perform the following consistency checks: 3> if IE "Positioning Methods" is set to "OTDOA": 4> if IE "UE positioning OTDOA reference cell info for UE-based" is not included and if UE positioning OTDOA reference cell info for UE-based in variable UE_POSITIONING_OTDOA_DATA_UE_BASED is empty: 5> set the variable CONFIGURATION_INCOMPLETE to TRUE. 3> if IE "Positioning Methods" is set to "OTDOA": 4> if IE "UE positioning OTDOA neighbour cell list for UE-based" is not included and if less than two neighbour cells are stored in UE positioning OTDOA neighbour cell info list for UE-based in variable UE_POSITIONING_OTDOA_DATA_UE_BASED: 5> set the variable CONFIGURATION_INCOMPLETE to TRUE. 4> if IE "Method Type" is set to "UE based": 5> if IE "UE positioning OTDOA reference cell info for UE-based" is included and if IE "Cell Position" for the reference cell is not included: 6> set the variable CONFIGURATION_INCOMPLETE to TRUE.
3GPP
Release 6
363
3GPP TS 25.331 V6.23.0 (2009-09)
5> if the IE "UE positioning OTDOA neighbour cell list for UE-based" is included and if cell position of less than two neighbour cells of the cells included in this IE and stored in variable UE_POSITIONING_OTDOA_DATA_UE_BASED are different and if those cell positions are not different to the one of the reference cell stored in variable UE_POSITIONING_OTDOA_DATA_UE_BASED: 6> set the variable CONFIGURATION_INCOMPLETE to TRUE. 5> if the IE "UE positioning OTDOA neighbouring cell list for UE-based " is included and only two neighbour cells are included or stored in variable UE_POSITIONING_OTDOA_DATA_UE_BASED and if the IE "Round Trip Time" is neither included for the neighbour cells nor for the reference cell info: 6> set the variable CONFIGURATION_INCOMPLETE to TRUE.
8.6.7.19.3
UE positioning GPS assistance data
The UE may receive GPS assistance data in System Information Block types 15, 15.1, 15.2, or 15.3, or in the ASSISTANCE DATA DELIVERY message, or in the MEASUREMENT CONTROL message. 8.6.7.19.3.1 UE positioning GPS acquisition assistance
If the IE "UE positioning GPS acquisition assistance" is included, the UE shall: 1> update the variable UE_POSITIONING_GPS_DATA as follows: 2> delete all information currently stored in the IE "UE positioning GPS acquisition assistance" in the variable UE_POSITIONING_GPS_DATA; 2> store the received acquisition assistance information in the IE "UE positioning GPS acquisition assistance" in the variable UE_POSITIONING_GPS_DATA; 2> store the IE "GPS TOW msec" in the IE "UE positioning GPS acquisition assistance" in variable UE_POSITIONING_GPS_DATA and use it as an estimate of the GPS Time-of-Week at the time of reception of the complete message containing the IE "GPS TOW msec"; NOTE: The UE does not need to apply any compensation on the GPS Time-of-Week.
1> if the IEs "SFN" and "UTRAN GPS timing of cell frames" are included: 2> if the UE is able to utilise these IEs: 3> store these IEs in the IE "UE positioning GPS acquisition assistance " in variable UE_POSITIONING_GPS_DATA; 3> if the IE "Primary CPICH Info" for FDD or IE "cell parameters id" for TDD is not included: 4> if the UE is not in CELL_DCH state: 5> use IEs "SFN" and "UTRAN GPS timing of cell frames" to estimate the relationship between GPS time and radio interface timing of the NODE B transmission in the serving cell. 4> if the UE is in CELL_DCH state: 5> ignore IEs "SFN" and "UTRAN GPS timing of cell frames". 3> if the IE "Primary CPICH Info" for FDD or IE "cell parameters id" for TDD is also included: 4> store this IE in the IE "UE positioning acquisition assistance" in variable UE_POSITIONING_GPS_DATA; 4> use IEs "SFN" and "UTRAN GPS timing of cell frames" to estimate the relationship between GPS time and air-interface timing of the NODE B transmission in the cell indicated by "Primary CPICH info" or "cell parameters id".
3GPP
Release 6
364
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.19.3.2
UE positioning GPS Almanac
If the IE "UE positioning GPS Almanac" is included, the UE shall: 1> if the IE "SV Global Health" is included: 1> store this IE in the IE in the IE "SV Global Health" in the IE "UE positioning GPS Almanac" in variable UE_POSITIONING_GPS_DATA. 1> for each satellite: 2> store received GPS almanac information at the position indicated by the IE "Sat ID" in the IE "UE positioning GPS Almanac" in the variable UE_POSITIONING_GPS_DATA, possibly overwriting any existing information in this position. 2> interpret IE "Data ID" as the Data ID field contained in the indicated subframe, word 3, most significant 2 bits, as defined by [12]; 2> act on the rest of the IEs in a similar manner as specified in [12]. 8.6.7.19.3.3 UE positioning D-GPS Corrections
If the IE "UE positioning GPS DGPS corrections" is included, the UE shall: 1> update the variable UE_POSITIONING_GPS_DATA as follows: 2> delete all information currently stored in the IE "UE positioning GPS DGPS corrections" in the variable UE_POSITIONING_GPS_DATA; 2> store the received DGPS corrections in the IE "UE positioning GPS DGPS corrections" in the variable UE_POSITIONING_GPS_DATA. 1> use IE "GPS TOW sec" to determine when the differential corrections were calculated; 1> use IE "Status/Health" to determine the status of the differential corrections. 8.6.7.19.3.3a UE positioning GPS Navigation Model
If the IE "UE positioning GPS Navigation Model" is included, for each satellite, the UE shall: 1> use IE "Satellite Status" to determine if an update of IE "UE positioning GPS Ephemeris and Clock Correction parameters" has been provided for the satellite indicated by the IE "SatID"; 1> if an update has been provided for this satellite: 2> act as specified in subclause 8.6.7.19.3.4. 8.6.7.19.3.4 UE positioning GPS Ephemeris and Clock Correction Parameters
If the IE "UE positioning GPS Ephemeris and Clock Correction parameters" is included, for each satellite, the UE shall: 1> update the variable UE_POSITIONING_GPS_DATA as follows: 2> store this IE at the position indicated by the IE "Sat ID" in the IE "UE positioning GPS Navigation Model" in the variable UE_POSITIONING_GPS_DATA, possibly overwriting any existing information in this position. 1> act on these GPS ephemeris and clock correction parameters in a manner similar to that specified in [12]. 8.6.7.19.3.5 UE positioning GPS ionospheric model
If IE "UE positioning GPS ionospheric model" is included, the UE shall: 1> store this IE in the IE "UE positioning GPS ionospheric model" in variable UE_POSITIONING_GPS_DATA; 1> act on these GPS ionospheric model parameters in a manner similar to that specified in [12].
3GPP
Release 6
365
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.19.3.6
UE positioning GPS real-time integrity
If this list of bad satellites is included, the UE shall: 1> update the variable UE_POSITIONING_GPS_DATA as follows: 2> add the Sat IDs that are not yet included in the list of satellites in the IE "UE positioning GPS real time integrity" in the variable UE_POSITIONING_GPS_DATA; 2> remove all Sat IDs in the list of satellites in the IE "UE positioning GPS real time integrity" in the variable UE_POSITIONING_GPS_DATA that are not included in IE UE positioning GPS real time integrity. 1> consider the data associated with the satellites identified in the variable UE_POSITIONING_GPS_DATA as invalid. 8.6.7.19.3.7 UE positioning GPS reference time
If the IE "UE positioning GPS reference time" is included, the UE shall: 1> store the IE "GPS Week" in "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA and use it as the current GPS week; 1> store the IE "GPS TOW msec" in the IE "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA and use it as an estimate of the GPS Time-of-Week at the time of reception of the complete message containing the IE "GPS TOW msec"; NOTE: The UE does not need to apply any compensation on the GPS Time-of-Week.
1> if the IE "SFN" and IE "UTRAN GPS timing of cell frames" are included: 2> if the UE is able to utilise the IEs: 3> store these IEs in the IE "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA; 3> if the IE "Primary CPICH Info" for FDD or IE "cell parameters id" for TDD is not included: 4> if the UE is not in CELL_DCH state: 5> use IEs "SFN" and "UTRAN GPS timing of cell frames" to estimate the relationship between GPS time and air-interface timing of the NODE B transmission in the serving cell. 4> if the UE is in CELL_DCH state: 5> ignore IEs "SFN" and "UTRAN GPS timing of cell frames". 3> if the IE "Primary CPICH Info" for FDD or IE "cell parameters id" for TDD is also included: 4> store this IE in the IE "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA; 4> use IEs "SFN" and "UTRAN GPS timing of cell frames" to estimate the relationship between GPS time and air-interface timing of the NODE B transmission in the cell indicated by "Primary CPICH info" or "cell parameters id". 1> if the IE "SFN-TOW Uncertainty" is included: 2> store this IE in the IE "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA and use it to determine if the relationship between GPS time and air-interface timing of the NODE B transmission is known to within at least 10ms. 1> if the IE "TUTRAN-GPS drift rate" is included: 2> store this IE in the IE "UE positioning GPS reference time" in variable UE_POSITIONING_GPS_DATA; and 2> may use it as an estimate of the drift rate of the NODE B clock relative to GPS time.
3GPP
Release 6
366
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "GPS TOW Assist" is included: 2> for each satellite: 3> delete all information currently stored in the IE "GPS TOW Assist" in the IE "UE positioning GPS reference time" in the variable UE_POSITIONING_GPS_DATA; 3> store the received GPS TOW Assist information in the IE "UE positioning GPS reference time" in the variable UE_POSITIONING_GPS_DATA. 8.6.7.19.3.8 UE positioning GPS reference UE position
If the IE "UE positioning GPS reference UE position" is included, the UE shall: 1> store this IE in the IE "UE positioning GPS reference UE position" in variable UE_POSITIONING_GPS_DATA; and 1> use it as a priori knowledge of the approximate location of the UE. 8.6.7.19.3.9 UE positioning UTC model
If the IE "UE positioning GPS UTC model" is included, the UE shall: 1> store this IE in the IE "UE positioning GPS UTC model" in variable UE_POSITIONING_GPS_DATA.
8.6.7.19.4
The UE shall:
UE positioning Ciphering info
1> if deciphering information is received from higher layers for deciphering of GPS assistance data broadcast on system information: 2> store the current key in IE "Current deciphering key" in variable UE_POSITIONING_GPS_DATA; 2> store the next key in IE "Next deciphering key" in variable UE_POSITIONING_GPS_DATA; 2> store the ciphering key flag in UE_POSITIONING_GPS_DATA. 1> if deciphering information is received from higher layers for deciphering of OTDOA assistance data broadcast on system information: 2> store the current key in IE "Current deciphering key" in variable UE_POSITIONING_OTDOA_DATA_UE_BASED; 2> store the next key in IE "Next deciphering key" in variable UE_POSITIONING_OTDOA_DATA_UE_BASED; 2> store the ciphering key flag in UE_POSITIONING_OTDOA_DATA_UE_BASED. 1> if the IE "GPS Data ciphering info" is included in System Information Block type 15: 2> select one of the two deciphering keys received and stored it in UE_POSITIONING_GPS_DATA according to the following: 3> if the value of the received IE "Ciphering Key Flag" is the same as the value of the IE "Ciphering Key Flag" stored in the variable UE_POSITIONING_GPS_DATA: 4> select the current deciphering key. 3> if the value of the received IE "Ciphering Key Flag" is different from the value of the IE "Ciphering Key Flag" stored in the variable UE_POSITIONING_GPS_DATA: 4> select the next deciphering key. 2> store the received IE in the variable UE_POSITIONING_GPS_DATA;
3GPP
Release 6
367
3GPP TS 25.331 V6.23.0 (2009-09)
2> use the selected deciphering key to decipher the broadcast UE positioning GPS information contained within the System Information Block types 15.1, 15.2 and 15.3. 1> if the IE "OTDOA positioning ciphering info" is included in System Information Block type 15.4: 2> select one of the two deciphering keys and stored it in UE_POSITIONING_OTDOA_DATA_UE_BASED according to the following: 3> if the value of the received IE "Ciphering Key Flag" is the same as the value of the IE "Ciphering Key Flag" stored in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED: 4> select the current deciphering key. 3> if the value of the received IE "Ciphering Key Flag" is different from the value of the IE "Ciphering Key Flag" stored in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED: 4> select the next deciphering key. 2> store the received IE in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED; 2> use the selected deciphering key to decipher the IE "OTDOA assistance data" included in the System Information Block types 15.4.
8.6.7.19.5
UE positioning Error
The UE shall set the contents of the IE "UE positioning Error" as follows: 1> if the IE "Positioning Methods" in IE "UE positioning reporting quantity" has been assigned to value "OTDOA" and no neighbour cells could be received, 2> set IE "Error reason" to "Not Enough OTDOA Cells"; 1> if the IE "Positioning Methods" in IE "UE positioning reporting quantity" has been assigned to value "GPS": 2> if there were not enough GPS satellites to be received: 3> set IE "Error reason" to "Not Enough GPS Satellites". 2> if some GPS assistance data was missing: 3> set IE "Error reason" to "Assistance Data Missing"; and 3> if the IE "Additional Assistance Data Request" included in the IE "UE positioning reporting quantity" stored in the variable MEASUREMENT_IDENTITY is set to TRUE: 4> include the IE "GPS Additional Assistance Data Request". 3> if the IE "Additional Assistance Data Request" included in the IE "UE positioning reporting quantity" stored in the variable MEASUREMENT_IDENTITY is set to FALSE: 4> not include the IE "GPS Additional Assistance Data Request", and use the assistance data available for doing a positioning estimate. 2> if the UE was not able to read the SFN of the reference cell included in the IE "UE positioning GPS reference time" or in the IE "UE positioning acquisition assistance": 3> set IE "Error reason" to "Reference Cell Not Serving Cell". 2> if the UE was not able to measure the requested GPS timing of cell frames measurement: 3> set IE "Error reason" to "Not Accomplished GPS Timing Of Cell Frames". 1> if none of the conditions above are fulfilled: 2> set IE "Error reason" to "Undefined Error". The UE shall not set the IE "Error reason" to "Request Denied By User" or "Not Processed and Timeout".
3GPP
Release 6
368
3GPP TS 25.331 V6.23.0 (2009-09)
8.6.7.19.6
Void
8.6.7.20 8.6.7.21
Void Intra-frequency reporting quantity for RACH reporting
If the IE "Intra-frequency reporting quantity for RACH reporting" is included, the UE shall: 1> if the IE "SFN-SFN observed time difference reporting indicator" has the value "type 2": 2> act as if the value of the IE "SFN-SFN observed time difference reporting indicator" is "no reporting". 1> if the IE "Reporting quantity" (FDD) or all IEs "Reporting quantity" (TDD) have the value "no report": 2> the UE behaviour is unspecified.
8.6.7.22
Additional Measurement List
If the IE "Additional Measurement List" is received in a MEASUREMENT CONTROL message, the UE shall: 1> if the received measurement configuration in this MEASUREMENT CONTROL message, or any measurement referenced in the "Additional Measurement List" do not all have the same validity (for this consistency check the UE shall assume "CELL_DCH" as the measurement validity for measurements of type "inter-RAT", "UE internal", and "quality"): 2> set the variable CONFIGURATION_INCOMPLETE to TRUE. 1> if any of the measurements referenced in the "Additional Measurement List" is an intra-frequency, interfrequency or inter-RAT measurement, and this measurement is configured with event based reporting: 2> the UE behaviour is not specified. 1> if any of the "intra-frequency", "inter-frequency", "traffic volume" or "UE positioning" measurements referenced in the "Additional Measurement List" has been setup without including the IE "measurement validity": 2> the UE behaviour is not specified. 1> if the result of this MEASUREMENT CONTROL message is such that more than one additional measurement of the same type will be referenced in the IE "Additional Measurement List" in the MEASUREMENT_IDENTITY variable: 2> the UE behaviour is not specified. 1> if the UE has no IE "Additional Measurement List" stored the in variable MEASUREMENT_IDENTITY associated with the identity indicated by the IE "measurement identity": 2> store the received IE "Additional Measurement List" in the variable MEASUREMENT_IDENTITY.
If the IE "Additional Measurement List" is received in a MEASUREMENT CONTROL message with the IE "Measurement command" value set to "modify", and the UE has an IE "Additional Measurement List" stored in the variable MEASUREMENT_IDENTITY associated with the identity indicated by the IE "measurement identity", the UE shall: 1> replace the information stored in "Additional Measurement List" in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the one received in the MEASUREMENT CONTROL message. If the IE "Additional Measurement List" is not received in a MEASUREMENT CONTROL message and the IE "Measurement command" has the value "modify" and the UE has an IE "Additional Measurement List" stored in the variable MEASUREMENT_IDENTITY associated with the identity indicated by the IE "measurement identity", the UE shall:
3GPP
Release 6
369
3GPP TS 25.331 V6.23.0 (2009-09)
1> leave the IE "Additional Measurement List" stored in the variable MEASUREMENT_IDENTITY associated with the identity indicated by the IE "measurement identity" unchanged. If, at any time during the life-time of a measurement, any measurement referenced in the Additional Measurement List does not exist, the UE shall: 1> remove this measurement identity from the Additional Measurement List. NOTE: A measurement referenced in the Additional Measurement List which is updated with a measurement command set to "modify", or replaced with a measurement command set to "setup", continues to exist.
If the measurement configured with the MEASUREMENT CONTROL message triggers a measurement report, the UE shall: 1> also include the reporting quantities for the measurements referenced by the additional measurement identities. The contents of the IE "Additional Measured results" are completely determined by the measurement configuration of the referenced additional measurement.
8.6.8 8.6.9
Void MBMS specific information elements
The UE shall perform the generic actions defined in this subclause only for the information elements corresponding with services that are included in variable MBMS_ACTIVATED_SERVICES.
8.6.9.1
Continue MCCH Reading
If the "Continue MCCH Reading " is included the UE shall: 1> if the IE "Continue MCCH reading " is set to 'TRUE': 2> continue receiving the MBMS MODIFIED SERVICES INFORMATION from MCCH in the next modification period and act upon it as specified in subclause 8.7.3.4.
8.6.9.1a
MBMS dynamic persistence level
If the IE "MBMS dynamic persistence level" is included the UE shall: 1> Apply the dynamic persistence level in place of that broadcast in SIB 7 for MBMS related PRACH transmissions that are made within the modification period in which this IE was received.
8.6.9.2
The UE shall:
MBMS PL Service Restriction Information
1> if the UE receives a Radio Bearer Control message or a CELL UPDATE CONFIRM message: 2> if the IE "MBMS PL Service Restriction Information" is included: 3> set the variable MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED to TRUE. 2> else: 3> set the variable MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED to FALSE. 1> if the UE receives a Radio Bearer Control message or a CELL UPDATE CONFIRM message or an MBMS GENERAL INFORMATION message: 2> perform the MBMS frequency selection procedure as specified in subclause 8.5.27.
8.6.9.3
MBMS L1 combining schedule
If the IE "MBMS L1 combining schedule" is included the UE may:
3GPP
Release 6
370
3GPP TS 25.331 V6.23.0 (2009-09)
1> apply L1 combining between the concerned neighbouring cells S-CCPCH and the corresponding current cells S-CCPCH for the periods indicated by this IE.
8.6.9.3a
The UE may:
MBMS Number of neighbour cells
1> apply the number of neighbour cells to identify if all MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages have been received from MCCH.
8.6.9.4
MBMS Preferred frequency information
If the IE "MBMS Preferred frequency information" is included the UE shall: 1> if HCS is not used, and the IE "Qoffmbms" is not present for the MBMS preferred frequency: 2> consider the cells on the MBMS preferred frequency having a Qoffmbms equal to "infinity". 1> if HCS is used, and the IE "HCS_OFFmbms" is not present for the MBMS preferred frequency: 2> consider the cells on the MBMS preferred frequency having the highest HCS priority level. 1> perform the MBMS frequency layer selection procedure as specified in subclause 8.5.27.
8.6.9.4a
Void
8.6.9.4b
MBMS p-t-m activation time
Upon reception of the IE "MBMS p-t-m activation time", for the services included in the IE "Modified service list" in the MBMS MODIFIED SERVICES INFORMATION message, and, if the IE "MBMS all unmodified p-t-m services" is included in the MBMS MODIFIED SERVICES INFORMATION message, for the services included in the IE "Unmodified services list" included in the MBMS UNMODIFIED SERVICES INFORMATION message, the UE shall: 1> if the IE "MBMS required UE action" for this service is set to "Acquire PTM RB info": 2> for the current cell: 3> stop using any old configuration on TTIs that are after or contain the time instant as indicated by the IE "MBMS p-t-m activation time"; 3> start using the configuration for the S-CCPCH received for that p-t-m bearer in the same modification period as the IE "MBMS p-t-m activation time" on TTIs that are after or that contain the time instant as indicated by the IE "MBMS p-t-m activation time". 2> for neighbouring cells: 3> for the neighbouring cells for which the IE "MBMS transmission time difference" is included: 4> stop using any old configuration on TTIs corresponding to the TTIs of the cell wherein the UE is reading the MCCH from and where the new p-t-m radio bearer information is valid according to the above; 4> start using the configuration for the S-CCPCH received for that p-t-m bearer in the same modification period as the IE "MBMS p-t-m activation time" on TTIs corresponding to the TTIs of the cell wherein the UE is reading the MCCH from and where the new p-t-m radio bearer information is valid according to the above. 3> for the neighbouring cells for which the IE "MBMS transmission time difference" is not included: 4> stop using any old configuration on TTIs that are after or contain the time instant as indicated by the IE "MBMS p-t-m activation time";
3GPP
Release 6
371
3GPP TS 25.331 V6.23.0 (2009-09)
4> start using the configuration for the S-CCPCH received for that p-t-m bearer in the same modification period as the IE "MBMS p-t-m activation time" on TTIs that are after the time instant as indicated by the IE "MBMS p-t-m activation time".
8.6.9.5
MBMS RB list released to change transfer mode
If the IE "MBMS RB list released to change transfer mode" is included the UE shall: 1> perform the service prioritisation procedure as specified in subclause 8.5.26, taking into account that the MBMS service(s) for which the radio bearers are released will be provided via p-t-m radio bearer(s).
8.6.9.6
MBMS Required UE action
If the IE "MBMS required UE action" is included and concerns an MBMS activated service the UE shall: 1> if the "MBMS required UE action" is set to 'None': 2> take no action with respect to this IE. 1> if the IE "MBMS required UE action" is set to 'Acquire counting info' or set to 'Acquire counting info PTM RBs unmodified': 2> perform the MBMS counting procedure as specified in subclause 8.7.4; NOTE: If upper layers indicate that an MBMS transmission has already been received correctly, the UE will continue as if the information about the concerned MBMS transmission was not included in the message. This implies that the UE does not respond to counting for a transmission already received correctly.
1> if the IE "MBMS required UE action" is set to 'Acquire PTM RB info'; or 1> if the IE "MBMS required UE action" is set to 'Acquire counting info PTM RBs unmodified' and the UE is not receiving a p-t-m RB for the concerned service: 2> continue acquiring the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3; 2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5. 1> if the IE "MBMS required UE action" is set to 'Request PTP RB': 2> if the UE is in idle mode: 3> indicate to upper layers that establishment of a PS signalling connection is required to receive the concerned MBMS service [5], unless the UE has already requested p-t-p RB establishment in the current modification period, and use the establishment cause set to 'MBMS ptp RB request' in the RRC connection establishment procedure. 2> if the UE is in URA_PCH, Cell_PCH, or CELL_FACH states: 3> indicate to upper layers to initiate a service request procedure [5] to receive the concerned MBMS service; 3> perform the cell update procedure with cause "MBMS ptp RB request", as specified in subclause 8.3.1.2, unless the UE has already requested p-t-p RB establishment in the current modification period. 2> if the UE is in CELL_DCH: 3> indicate to upper layers to initiate a service request procedure [5] to receive the concerned MBMS service. 1> if the IE "MBMS required UE action" is set to 'Release PTM RB':
3GPP
Release 6
372
3GPP TS 25.331 V6.23.0 (2009-09)
2> stop receiving the concerned MBMS service; 2> if the UE is in a state other than CELL_DCH (for FDD) or if the UE is in Idle mode, URA_PCH or CELL_PCH state (for TDD); and 2> if the UE decides not to receive an MBMS service indicated on the MCCH; and 2> if the variable MBMS_PREV_FREQUENCY_INFO is not empty: 3> if any frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 4> select a suitable UTRA cell in that frequency. 4> if no suitable UTRA cell in that frequency is found: 5> select a suitable UTRA cell in another frequency. 3> if no frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO. 4> select a frequency randomly among the inter-frequencies indicated in SIB11 or SIB12. 5> select a suitable UTRA cell in the selected frequency. 5> if no suitable UTRA cell in the selected frequency is found: 6> select a suitable UTRA cell in another frequency. 3> clear the variable MBMS_PREV_FREQUENCY_INFO. 2> clear all service specific information applicable for the concerned service. NOTE: The UE is only required to acquire the relevant SIB11 or SIB12, according to what is specified in subclauses 8.1.1.6.11 and 8.1.1.6.12.
8.6.9.6a
MBMS re- acquire MCCH
If the UE receives the IE " MBMS re- acquire MCCH", the UE shall: 1> perform the MCCH acquisition procedure as specified in subclause 8.7.2.
8.6.9.7
MBMS Service transmissions info list
If the UE receives the IE "MBMS Service transmissions info list", the UE may: 1> discontinue reception of the S-CCPCH on which the IE was received, except for the service transmissions indicated by this IE for the concerned scheduling period.
8.6.9.8
MBMS Short transmission ID
If the IE "MBMS short transmission ID" is included the UE shall: 1> if the value of the "MBMS short transmission ID" is less than or equal to the number of services identified by the IE "Modified services list" included in the MBMS MODIFIED SERVICES INFORMATION message acquired in the same modification period as the one in which the "MBMS short transmission ID" is received: 2> consider the "MBMS short transmission ID" to be an index to the list of services contained in the IE "Modified services list" and apply the MBMS transmission identity specified for this entry. 1> otherwise: 2> compile a list of available MBMS services, as included in the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages acquired in the same modification period as the one in which the "MBMS short transmission ID" is received:
3GPP
Release 6
373
3GPP TS 25.331 V6.23.0 (2009-09)
3> concatenate the services contained in IE "Modified services list" included in the MBMS MODIFIED SERVICES INFORMATION and the services contained in IE "Unmodified services list" included in the MBMS UNMODIFIED SERVICES INFORMATION. 2> consider the "MBMS short transmission ID" to be the index of the entry in the list of available services and apply the MBMS transmission identity specified for this entry.
8.6.9.9
MBMS Transmission identity
If the IE "MBMS transmission identity" is included the UE shall: 1> if upper layers indicate that the MBMS transmission has already been received correctly: 2> ignore the information about this MBMS transmission i.e. continue as if the information about the concerned MBMS transmission was not included in the message. 1> otherwise: 2> act upon the information about the concerned MBMS transmission as specified elsewhere. The UE behaviour is unspecified if an MBMS transmission identity appears more than once in the combined list of transmissions i.e. the IE is included more than once in the MBMS MODIFIED SERVICES INFORMATION or in the MBMS UNMODIFIED SERVICES INFORMATION, or once in both message.
8.6.9.9a
MBMS transmission time difference
The IE "MBMS transmission time difference" indicates the time difference between the transmissions on the current and the neighbour cell i.e. indicating the TTIs that can be L1- combined. The UE shall: 1> derive the parameter Neighbor_Start from the IE MBMS transmission time difference as follows: MBMS transmission time difference = (Neighbor_Start / Max_TTI_Size) mod 4 where Neighbor_Start is the CFN of the first radio frame in a TTI on the neighbour cell that may be combined with the TTI on the current cell of which the CFN of the first radio frame equals 0 while Max_TTI_Size is the largest TTI size on the S-CCPCHs to be soft combined; 1> in case of partial soft combining, derive the CFN of the first radio frame in a TTI on the neighbour cell that may be combined assuming the same time difference applies. The maximum delay between S-CCPCH clusters that the UE may combine is set by UE performance requirements. NOTE: The MBMS transmission time difference is semi-static; it does not vary within or between L1 combining periods nor when full combining is used.
8.6.9.9b
MCCH configuration information
If the IE "MCCH configuration information" is included the UE shall: 1> Consider an access information period to start from the frame with the SFN value fulfilling the following equation (where m is the modification period coefficient and a is the access info period coefficient): SFN mod 2(m a) = 0 1> Consider a repetition period to start from the frame with the SFN value fulfilling the following equation (where m is the modification period coefficient and r is the repetition period coefficient): SFN mod 2(m r) = 0 1> Consider a modification period to start from the frame with the SFN value fulfilling the following equation (where m is the modification period coefficient): SFN mod 2m = 0 1> configure the RLC entity in the UE used for receiving MCCH in accordance with 8.6.4.9;
3GPP
Release 6
374
3GPP TS 25.331 V6.23.0 (2009-09)
1> configure the MAC entity in the UE, used for receiving MCCH, for receiving TCTF field unless the IE 'TCTF presence' is received;
8.6.9.10
Next scheduling period
If the IE "Next scheduling period" is included for an MBMS service the UE may: 1> discontinue reception of the given MBMS service for the number of scheduling periods indicated by this IE.
8.7 MBMS specific procedures

8.7.1
8.7.1.1
Reception of MBMS control information

General
The procedure for receiving MBMS control information is used by a UE to receive information from UTRAN concerning the way it provides MBMS services the UE has activated. The procedure applies to all UEs supporting MBMS, irrespective of its state (idle, URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH). Most MBMS control information is provided on the MCCH. The information on MCCH is transmitted using a fixed schedule, which is common for all services. MCCH information other than MBMS ACCESS INFORMATION message is transmitted periodically based on a repetition period. This MCCH information is repeated a configurable number of times with exactly the same content; the period in which the content of MCCH information other than MBMS ACCESS INFORMATION message remains unchanged is called the modification period. MBMS ACCESS INFORMATION message may be transmitted more frequently, based on the Access Info period. The transmissions of MBMS ACCESS INFORMATION message within a modification period need not have exactly the same content (the value of some parameters eg. IE 'Access probability factor Idle' may change). Nevertheless, the transmissions of MBMS ACCESS INFORMATION message within a modification period should concern the same MBMS service(s), although information for a service may be removed eg. upon completion of the counting for that service. The general principles are illustrated in figure 8.7.1-1, in which different colours indicate potentially different content of the MCCH information.
Access Info period
Repetition period
Modification period
MCCH
Figure 8.7.1-1: Scheduling of MCCH Information For services provided via a p-t-m radio bearer scheduling information may be provided on an MSCH mapped on the same S-CCPCH as the p-t-m radio bearer(s). For some of the services provided p-t-m this scheduling information may be provided by signalling an MBMS SCHEDULING INFORMATION message at every scheduling period, while for others the MBMS SCHEDULING INFORMATION message may be signalled less frequently i.e. after a multiple of the scheduling period. In general, the UE is neither required to acquire MSCH information nor to act on it. In case the UE shall acquire MCCH information that is scheduled at the same time as MSCH information, the reception of the MCCH information shall take precedence. In order to minimise the time the UE needs to read MCCH upon notification as specified in 8.7.3 to acquire the required information, UTRAN should schedule the MCCH messages in a specific order ie. any message that needs to be read by any UE due to the reception of the MBMS MODIFIED SERVICES INFORMATION message should be scheduled prior to the remaining messages. More specifically, the UE may assume that UTRAN schedules the MCCH messages in the following order: MBMS MODIFIED SERVICES INFORMATION,
3GPP
Release 6
375
3GPP TS 25.331 V6.23.0 (2009-09)
followed by messages that needs to be read by any UE due to the content of the MBMS MODIFIED SERVICES INFORMATION message in the following order: MBMS GENERAL INFORMATION, MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION, one or more MBMS NEIGHBOURING CELL P-T-M RB INFORMATION, MBMS UNMODIFIED SERVICES INFORMATION, followed by messages that do not need to be read by any UE due to the content of the MBMS MODIFIED SERVICES INFORMATION message in the following order: MBMS GENERAL INFORMATION, MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION, one or more MBMS NEIGHBOURING CELL P-T-M RB INFORMATION
8.7.1.2
Initiation
The requirements concerning which MBMS control information the UE shall acquire in the different cases is specified in other subclauses. This section specifies common requirements concerning the reception of MCCH information and MSCH information.
8.7.1.3
UE requirements on reading of MCCH information
When requested to acquire MBMS control information other than the MBMS ACCESS INFORMATION message , the UE shall: 1> if requested to start reading MCCH at the next modification period: 2> start reading MCCH at the beginning of the next modification period. 1> otherwise 2> start reading MCCH at the beginning of the next repetition period. 1> if requested to stop reading MCCH at the end of the modification period: 2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first; 2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly or until the end of the modification period. 1> otherwise: 2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first; 2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly. NOTE 1: The UE may combine information received at different repetition periods within a modification period. When requested to acquire the MBMS ACCESS INFORMATION message, the UE shall: 1> if requested to start reading MCCH at the next modification period: 2> start reading MCCH at the beginning of the next modification period. 1> otherwise: 2> start reading MCCH at the beginning of the next access info period. 1> continue reading MCCH in this manner at every subsequent access info period, until the message is received correctly or until the end of the modification period. If the UE is CELL_DCH and has a compressed mode pattern that overlaps with the period in which it needs to read MCCH, the UE may temporarily refrain from receiving MCCH unless it is capable of simultaneous operation. If the UE is CELL_FACH and has a measurement occasion that overlaps with the period in which it needs to read MCCH, the UE
3GPP
Release 6
376
3GPP TS 25.331 V6.23.0 (2009-09)
may temporarily refrain from receiving MCCH unless it is capable of simultaneous operation. A UE in CELL_FACH may omit performing measurements during a measurement occasion in order to receive MCCH provided that this does not prevent it from fulfilling the measurement performance requirements as specified in [19]. In Idle mode as well as in CELL_PCH and URA_PCH states the UE may temporarily refrain from receiving MCCH if needed to fulfil the measurements performance requirements as specified in [19]. NOTE 2: The UTRAN should endeavour to ensure that for each UE in CELL_FACH the assigned measurement occasions do not overlap constantly with the periodic MCCH transmissions. If the UE selects to another cell, the UE shall re-establish the RLC entity used for MCCH reception.
8.7.1.4
UE requirements on reading of MSCH information
If the UE supports reception of MSCH, UE shall: 1> if the UE needs to acquire MCCH information that is transmitted at the same time as the MSCH information and the UE does not support simultaneous reception: 2> refrain from reading MSCH. If the UE supports reception of MSCH, UE should: 1> start reading MSCH at the beginning of the next scheduling period; 1> continue reading MSCH until the required MBMS control information is received or until the UE detects a TTI in which no MSCH information is transmitted, whichever is first.
8.7.2
MCCH acquisition
UE UTRAN
MBMS MODIFIED SERVICES INFORMATION MBMS UNMODIFIED SERVICES INFORMATION
MBMS ACCESS INFORMATION MBMS GENERAL INFORMATION
MBMS COMMON P-T-M RB INFORMATION MBMS CURRENT CELL P-T-M RB INFORMATION MBMS NEIGHBOURING CELL P-T-M RB INFORMATION
Figure 8.7.2-1: MCCH acquisition, normal
8.7.2.1
General
The UE applies the MCCH acquisition procedure to determine the MBMS services available in the cell and to initiate reception of the services that the UE has activated. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle, URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH). The UE may also apply the MCCH acquisition procedure to inform NAS of other available services that are not activated.
3GPP
Release 6
377
3GPP TS 25.331 V6.23.0 (2009-09)
8.7.2.2
Initiation
If the variable MBMS_ACTIVATED_SERVICES is not empty, the UE shall apply the MCCH acquisition procedure upon selecting (eg. upon power on) or reselecting a cell supporting MBMS, upon change of MBMS controlling cell (eg. due to an active set update or hard handover), upon entering UTRA from another RAT, upon release of a MBMS PTP RB for the purpose of changing transfer mode, upon return from loss of coverage and upon receiving an indication from upper layers that the set of activated services has changed.
8.7.2.3
MCCH information to be acquired by the UE
The UE shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3. The UE shall immediately acquire the MBMS ACCESS INFORMATION and the MBMS GENERAL INFORMATION messages ie. it shall not delay reception of these messages until it has completed the acquisition of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages. Likewise, the UE should immediately acquire the MBMS CURRENT CELL P-T-M RB INFORMATION and MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages. The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information eg. both the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION message should be acquired in the same modification period.
8.7.2.4
Reception of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION by the UE
If the UE is receiving an MBMS service that is not included in variable MBMS_ACTIVATED_SERVICES and that is using a p-t-m radio bearer, the UE shall: 1> stop receiving the concerned MBMS service and clear all service specific information applicable for the concerned service. 1> if the UE is in a state other than CELL_DCH (for FDD) or if the UE is in Idle mode, URA_PCH or CELL_PCH state (for TDD); and 1> if the UE does not decide to receive an MBMS service; and 1> if the variable MBMS_PREV_FREQUENCY_INFO is not empty: 2> if any frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 3> select a suitable UTRA cell in that frequency; 3> if no suitable UTRA cell in that frequency is found: 4> select a suitable UTRA cell in another frequency. 2> if no frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 3> select a frequency randomly among the inter-frequencies indicated in SIB11 or SIB12: 4> select a suitable UTRA cell in the selected frequency; 4> if no suitable UTRA cell in the selected frequency is found: 5> select a suitable UTRA cell in another frequency. 2> clear the variable MBMS_PREV_FREQUENCY_INFO. NOTE: The UE is only required to acquire the relevant SIB11 or SIB12, according to what is specified in subclauses 8.1.1.6.11 and 8.1.1.6.12.
3GPP
Release 6
378
3GPP TS 25.331 V6.23.0 (2009-09)
Upon completing the reception of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages, the UE shall 1> act as follows for each of the services included in these messages provided that the service is included in variable MBMS_ACTIVATED_SERVICES and upper layers indicate that the session has not yet been received correctly (referred to as 'applicable services'); 1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following; 1> if one or more preferred frequency applies for the applicable services: 2> delay acting upon the "MBMS Preferred frequency information" until receiving the relevant MCCH information i.e. the MBMS GENERAL INFORMATION message; 2> act upon the "MBMS Preferred frequency information" as specified in subclause 8.6.9.4 for the service(s) that upper layers indicate to have highest priority. 1> perform MBMS frequency selection procedure as specified in subclause 8.5.27; 1> if the UE receives an MBMS service using a p-t-m radio bearer and the received messages do not contain an IE "MBMS required UE action" set to "Acquire PTM RB info" or set to "Acquire counting info PTM RBs unmodified" for that service then the UE shall: 2> stop receiving the concerned MBMS service and clear all service specific information applicable for the concerned service.
8.7.2.5
Reception of the other MBMS messages by the UE
Upon receiving the MBMS ACCESS INFORMATION message, the UE shall act as specified in subclause 8.7.4.3. Upon receiving the MBMS GENERAL INFORMATION message, the UE should store all relevant IEs included in this message. The UE shall also: 1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following. Upon receiving the MBMS CURRENT CELL P-T-M RB INFORMATION and MBMS NEIGHBOURING CELL P-TM RB INFORMATION messages, the UE shall act as specified in subclauses 8.7.5.3 and subclause 8.7.5.4 respectively. The procedure ends.
8.7.3
MBMS Notification
UE
UTRAN
MCCH: MBMS MODIFIED SERVICES INFORMATION
MCCH: updated MBMS control information
Figure 8.7.3-1: MBMS notification on MCCH
3GPP
Release 6
379
3GPP TS 25.331 V6.23.0 (2009-09)
UE
UTRAN
DCCH: MBMS MODIFIED SERVICES INFORMATION
MCCH: updated MBMS control information
Figure 8.7.3-2: MBMS notification on DCCH
8.7.3.1
General
The MBMS notification procedure is used by the UE to respond to a notification provided by UTRAN, indicating a change applicable for one or more MBMS services the UE has activated. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle and connected mode: URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH). The actual notification mechanism to be used depends on the UE state. Reception of the MBMS MODIFIED SERVICES INFORMATION message on DCCH is optional for a UE capable of reading MCCH in CELL_DCH.
8.7.3.2
Initiation
UTRAN initiates the notification procedure to inform UEs about a change applicable for one or more MBMS services available in a cell. Some types of MBMS service changes e.g. the establishment of a p-t-m radio bearer, involve a modification of MCCH messages other than the MBMS MODIFIED SERVICES INFORMATION message. NOTE 1: On MCCH, the MBMS MODIFIED SERVICES INFORMATION as well as the MBMS UNMODIFIED SERVICES INFORMATION messages are signalled even if no services are contained in the message. NOTE 2: A service remains in the MBMS MODIFIED SERVICES INFORMATION message until it enters a 'steady state', upon which it moves to the MBMS UNMODIFIED SERVICES INFORMATION message. In case counting is used, the service remains in the MBMS MODIFIED SERVICES INFORMATION message through the moment UTRAN has decided the transfer mode.
8.7.3.3
8.7.3.3.1
The UE may:
Receiving the MBMS Notification information

Reception via MCCH
1> monitor the MBMS notification Indicator Channel (MICH); 1> if a notification on the MICH for one or more of the MBMS services included in the variable MBMS_ACTIVATED_SERVICES is detected: 2> acquire the MBMS MODIFIED SERVICES INFORMATION message with delaying the reading of MCCH until the next modification period and with stopping at the end of the modification period, in accordance with subclause 8.7.1.3; 2> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4. The UE shall: 1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state: 2> if not monitoring MICH: 3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3; 3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.
3GPP
Release 6
380
3GPP TS 25.331 V6.23.0 (2009-09)
1> if in CELL_DCH state: 2> if receiving an MBMS service that is provided via a p-t-m radio bearer and not monitoring MICH: 3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3; 3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.
8.7.3.3.2
Void
8.7.3.3.3
Reception via DCCH
Notification via DCCH is used to notify the UE about the start of a session for which a PL applies, to notify the UE about the establishment of a p-t-m radio bearer and to request a UE in PMM_idle state to establish a PMM connection to enable reception of a service provided via a p-t-p radio bearer. Upon receiving the MBMS MODIFIED SERVICES INFORMATION message via DCCH, a UE in CELL_DCH shall: 1> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.
8.7.3.4
UE action upon receiving MBMS MODIFIED SERVICES INFORMATION message
Upon receiving the MBMS MODIFIED SERVICES INFORMATION message, the UE shall act as follows for each of the services included in this messages provided that the service is included in variable MBMS_ACTIVATED_SERVICES and upper layers indicate that the session has not yet been received correctly (referred to as 'applicable services'): 1> if the IE "MBMS all unmodified p-t-m services" is included in the MBMS MODIFIED SERVICES INFORMATION messages: 2> for all services listed in the message UNMODIFIED SERVICES INFORMATION, provided that the service is included in variable MBMS_ACTIVATED_SERVICES, upper layers indicate that the session has not yet been received correctly (referred to as 'applicable services') and the IE "MBMS required UE action" in the message MBMS UNMODIFIED SERVICES INFORMATION is set to "Acquire PTM RB info": 3> continue acquiring the MBMS UNMODIFIED SERVICES INFORMATION, MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION, and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3; 3> act upon the MBMS UNMODIFIED SERVICES INFORMATION MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5, and assuming the p-t-m configuration indicated in these messages is valid immediately, unless the IE "MBMS p-t-m activation time" is included in the MBMS MODIFIED SERVICES INFORMATION message. 2> if the UE receives an MBMS service using a p-t-m radio bearer and the messages MBMS UNMODIFIED SERVICES INFORMATION and MBMS MODIFIED SERVICES INFORMATION do not contain an IE "MBMS required action" set to "Acquire PTM RB info" or set to "Acquire counting info PTM RBs unmodified" for that service then the UE shall: 3> stop receiving the concerned MBMS service and clear all service specific information applicable for the concerned service. 3> if the UE is in a state other than CELL_DCH (for FDD) or if the UE is in Idle mode, URA_PCH or CELL_PCH state (for TDD); and 3> if the UE does not decide to receive an MBMS service; and
3GPP
Release 6
381
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the variable MBMS_PREV_FREQUENCY_INFO is not empty: 4> if any frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 5> select a suitable UTRA cell in that frequency; 5> if no suitable UTRA cell in that frequency is found: 6> select a suitable UTRA cell in another frequency. 4> if no frequency in SIB11 or SIB12 has the same frequency stored in the variable MBMS_PREV_FREQUENCY_INFO: 5> select a frequency randomly among the inter-frequencies indicated in SIB11 or SIB12: 6> select a suitable UTRA cell in the selected frequency; 6> if no suitable UTRA cell in the selected frequency is found: 7> select a suitable UTRA cell in another frequency. 4> clear the variable MBMS_PREV_FREQUENCY_INFO. NOTE: The UE is only required to acquire the relevant SIB11 or SIB12, according to what is specified in subclauses 8.1.1.6.11 and 8.1.1.6.12.
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following 1> if one or more preferred frequency applies for the applicable services: 2> acquire the MBMS GENERAL INFORMATION message. 1> perform the MBMS frequency selection procedure as specified in subclause 8.5.27; 1> the procedure ends.
8.7.3.5
UE fails to receive MBMS Notification information
If the UE fails to receive the MBMS MODIFIED SERVICES INFORMATION message within the current modification period, the UE shall: 1> Acquire the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages without delaying reading of MCCH until the next modification period and with stopping at the end of that modification period, in accordance with subclause 8.7.1.3; 1> act upon the received MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages as specified in subclause 8.7.2.4.
8.7.4
MBMS counting
UE UTRAN
MCCH: MBMS ACCESS INFORMATION
Access Info Period: 0
MCCH: MBMS ACCESS INFORMATION Access Info Period: 1
Figure 8.7.4-1: MBMS counting, normal
3GPP
Release 6
382
3GPP TS 25.331 V6.23.0 (2009-09)
8.7.4.1
General
The MBMS counting procedure is used by the UE to inform UTRAN about its interest to receive an MBMS transmission. The procedure applies to UEs supporting MBMS that are in idle mode or in connected mode. In connected mode the procedure applies to the URA_PCH, Cell_PCH and/ or Cell_FACH states dependent upon the value of the IE "Connected mode counting scope".
8.7.4.2
Initiation
The UE initiates the MBMS counting procedure for an MBMS transmission upon receiving an MBMS MODIFIED SERVICES message including IE "MBMS required UE action" with the value set to 'Acquire counting info' or set to "Acquire counting info PTM RBs unmodified".
8.7.4.3
Reception of the MBMS ACCESS INFORMATION
The UE shall acquire the MBMS ACCESS INFORMATION message without delaying reading of MCCH until the next modification period in accordance with subclause 8.7.1.3. If the procedure the UE would apply to respond to counting (Idle mode: RRC connection establishment, connected mode: Cell update) is ongoing, the UE may defer acquiring the MBMS ACCESS INFORMATION message until this procedure has completed. The UE behaviour upon receiving an MBMS ACCESS INFORMATION message that is contained in more than one TTI is not specified. Upon receiving the MBMS ACCESS INFORMATION message including one or more MBMS service(s) it has joined, and/or including one or more MBMS Selected Services the UE shall for each joined and/or selected service: 1> if the UE is in idle mode: 2> draw a random number, "rand", uniformly distributed in the range: 0 rand < 1 2> if 'rand' is lower than the value indicated by the IE 'Access probability factor-Idle' for the concerned service: 3> indicate to upper layers that establishment of an RRC connection is required to receive the concerned MBMS service, with the establishment cause set to 'MBMS reception'; 3> if the above condition applies for more than one service, initiate a single indication to upper layers; 3> if the RRC connection establishment succeeds, the procedure ends. 2> otherwise: 3> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE: 4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3. 3> otherwise: 4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and with stopping at the end of the modification period, in accordance with subclause 8.7.1.3. 1> if the UE is in URA_PCH state, Cell_PCH or Cell_FACH state and the IE "Connected mode counting scope" indicates that counting is applicable for this UE state: 2> draw a random number, "rand", uniformly distributed in the range: 0 rand < 1. 2> if 'rand' is lower than the value indicated by the IE 'Access probability factor-connected' for the concerned service: 3> if a cell update has not been successfully transmitted for this service in the current modification period:
3GPP
Release 6
383
3GPP TS 25.331 V6.23.0 (2009-09)
4> initiate the cell update procedure with 'Cell update cause' set to "MBMS reception", in accordance with subclause 8.3.1; 4> if the above condition applies for more than one service, initiate a single cell update; 4> if the cell update procedure succeeds, 5> the procedure ends. 2> otherwise: 3> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE: 4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3. 3> otherwise: 4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and with stopping at the end of the modification period, in accordance with subclause 8.7.1.3. 1> otherwise: 2> the procedure ends; Upon receiving the MBMS ACCESS INFORMATION message not including an MBMS service(s) the UE has joined or selected: 1> the procedure ends;
8.7.4.4
Termination of the MBMS counting procedure
If the UE detects that the MBMS ACCESS INFORMATION message is not provided at an access info period; OR If the UE receives an MBMS ACCESS INFORMATION message not including an MBMS service the UE has joined or selected, the UE shall: 1> terminate the MBMS counting procedure. If the UE receives an RRC CONNECTION REJECT message with Rejection Cause 'unspecified' and including the MBMS "Counting completion" IE, the UE should: 1> consider the MBMS counting procedure ended for the MBMS service(s) for which the UE has initiated the MBMS counting response; 1> indicate to upper layers that the establishment of an RRC connection with the establishment cause set to 'MBMS reception' shall be aborted.
8.7.4.5
Failure of the counting response procedure
If the counting response procedure (RRC connection establishment or Cell update) fails, the UE shall: 1> if the failure occurs in the same modification period as the one in which the UE initiated the counting response procedure; or 1> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE that is applicable in the modification period in which the UE detects the failure: 2> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3. 1> otherwise:
3GPP
Release 6
384
3GPP TS 25.331 V6.23.0 (2009-09)
2> the procedure ends.
8.7.5
MBMS p-t-m radio bearer configuration

UE MBMS COMMON P-T-M RB INFORMATION MBMS CURRENT CELL P-T-M RB INFORMATION MBMS NEIGHBOURING CELL P-T-M RB INFORMATION UTRAN
Figure 8.7.5-1: MBMS p-t-m radio bearer modification, normal
8.7.5.1
General
The MBMS p-t-m radio bearer configuration procedure is used by the UE to acquire the (modified) radio bearer configuration for one or more activated MBMS services. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle and connected mode: URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH).
8.7.5.2
Initiation
The UE applies the MBMS p-t-m radio bearer configuration procedure whenever it detects that one of the activated services is provided by means of a p-t-m radio bearer. This may occur as part of the MCCH acquisition or the MBMS Notification procedure.
8.7.5.3
Reception of the MBMS Current Cell PTM RB information
Upon completing the reception of the MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION messages for an activated MBMS service, the UE shall: 1> if the UE is already receiving an MTCH and does not have the capability to receive the new service in addition: 2> the UE behaviour is undefined. NOTE: In this case, the UE may request upper layers to prioritise the services and only receive the service(s) prioritised by upper layers.
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following; 1> if the UE previously received the service by means of a p-t-m radio bearer from a cell belonging to another MBMS cell group: 2> re-establish RLC; 2> re-initialise PDCP. 1> start immediately to use the indicated configuration unless specified otherwise; 1> start or continue receiving the indicated p-t-m radio bearers depending on its UE capabilities. The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information i.e. the MBMS MODIFIED SERVICES INFORMATION message, MBMS UNMODIFIED SERVICES INFORMATION message, MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION message should be acquired in the same modification period.
3GPP
Release 6
385
3GPP TS 25.331 V6.23.0 (2009-09)
8.7.5.4
Reception of the MBMS Neighbouring Cell PTM RB information
Upon receiving the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message for an activated MBMS service, the UE shall: 1> start immediately to use the indicated neighbouring cells and configuration, or a subset of them, for L1- or L2 combining unless specified otherwise; 1> start or continue receiving the indicated p-t-m radio bearers from the selected neighbouring cells depending on its UE capabilities. The UE shall apply MBMS NEIGHBOURING CELL P-T-M RB INFORMATION only in combination with an MBMS MODIFIED SERVICES INFORMATION message, MBMS UNMODIFIED SERVICES INFORMATION message, MBMS COMMON P-T-M RB INFORMATION and MBMS CURRENT CELL P-T-M RB INFORMATION message acquired in the same modification period.
8.7.6
MBMS modification request

UE UTRAN
MBMS MODIFICATION REQUEST
Figure 8.7.6-1: MBMS modification request, normal
8.7.6.1
General
The MBMS modification request procedure is used by the UE to request UTRAN to release the p-t-p radio bearers ofone or more MBMS services the UE is receiving. The procedure is also used to request to be moved to a preferred frequency applicable for one or more (prioritised) activated MBMS services, and to indicate the UE MBMS Selected Services. The procedure applies to all UEs supporting MBMS, that are in CELL_DCH, CELL_PCH, URA_PCH or CELL_FACH state.
8.7.6.2
Initiation
A UE entering CELL_DCH shall initiate the MBMS modification request procedure in the following cases: 1> if the UE has any MBMS Selected Service; and 1> if the IE "MCCH configuration information" was received in System Information Block Type 5 or System Information Block Type 5bis prior to entering CELL_DCH. A UE completing an RRC Connection Setup procedure shall initiate the MBMS modification request procedure in the following cases: 1> if the UE has any MBMS Selected Service; and 1> if the IE "MCCH configuration information" was received in System Information Block Type 5 or System Information Block Type 5bis prior to completing the RRC Connection Setup procedure. A UE in CELL_DCH shall initiate the MBMS modification request procedure in the following cases: 1> the preferred frequency applicable for the MBMS service prioritised by upper layers is different from the currently used frequency; 1> upper layers request to discontinue reception of an MBMS service provided via a p-t-p radio bearer e.g. because this inhibits reception of a higher priority service; 1> upon a change in selection of the MBMS Selected Services.
3GPP
Release 6
386
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE:
The above case may occur upon receiving a dedicated notification or in other cases eg. a change of transfer mode from p-t-p to p-t-m for the UE's highest priority MBMS service.
A UE in CELL_FACH, CELL_PCH or URA_PCH state shall initiate the MBMS modification request procedure in the following cases: 1> upon a change in selection of the MBMS Selected Services that are indicated on MCCH; and 1> if the IE "Indicate changes in MBMS Selected Services" that is included in the MBMS GENERAL INFORMATION message is set to TRUE. If the UE is required to initiate the MBMS modification request procedure as specified in the conditions above, the UE shall: 1> transmit an MBMS MODIFICATION REQUEST message with the contents as specified in subclause 8.7.6.2a. If applicable, the UE shall use a single MBMS MODIFICATION REQUEST message to request a move to the preferred frequency and/or to request release of radio bearers corresponding with lower priority MBMS services provided p-t-p and/or to report the MBMS Selected Services.
8.7.6.2a
MBMS MODIFICATION REQUEST message contents to set
The UE shall set the contents of the MBMS MODIFICATION REQUEST message as follows: 1> if the preferred frequency applicable for the MBMS service prioritised by upper layers is different from the currently used frequency: 2> include the IE "MBMS preferred frequency request" and set it to the prioritised MBMS service identity. 1> if upper layers request to discontinue reception of an MBMS service provided via a p-t-p radio bearer: 2> include the p-t-p radio bearers used for the corresponding MBMS services within the IE "MBMS RB list requested to be released". 1> if the UE enters CELL_DCH; or 1> if the UE completes the RRC connection establishment procedure; or 1> if there is a change in selection of one or more of the MBMS Selected Services: 2> if the UE has not selected any MBMS Selected Service: 3> include the IE "MBMS Selected Service Info" and set the Status to 'None'. 2> otherwise: 3> include the IE "MBMS Selected Service Info" and set the Status to 'Some'; 3> if the UE supports the actions specified upon reception of the IE "RAB information for MBMS ptp bearer": 4> include the IE "Support of MBMS service change for a ptp RB". 3> for each MBMS Selected Service: 4> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Full" before those selected with a lower priority; 4> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Full".
8.7.6.3
Reception of a MBMS MODIFICATION REQUEST message by the UTRAN
Upon reception of a MBMS MODIFICATION REQUEST message, the UTRAN may take further action depending on the contents of the received message. The procedure ends.
3GPP
Release 6
387
3GPP TS 25.331 V6.23.0 (2009-09)
8.7.7
MBMS service scheduling

UE UTRAN
MSCH: MBMS SCHEDULING INFORMATION
Scheduling Period: 0
MSCH: MBMS SCHEDULING INFORMATION Scheduling Period: 1
Figure 8.7.7-1: MBMS service scheduling, normal
8.7.7.1
General
The MBMS service scheduling procedure is used by the UE that is receiving one or more activated MBMS services to acquire the MBMS scheduling information for the MBMS services. The procedure applies to all UEs that are receiving an MBMS service provided via a p-t-m radio bearer, irrespective of their state (idle and connected mode: URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH).
8.7.7.2
Initiation
The UE may initiate the MBMS service scheduling procedure for any scheduling period of the concerned MBMS service while receiving an SCCPCH carrying an MBMS service.
8.7.7.3
Reception of the MBMS scheduling information
Upon receiving the MBMS SCHEDULING INFORMATION message, the UE should: 1> act as follows for each of the services included in these messages provided that the service is included in variable MBMS_ACTIVATED_SERVICES; 1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following. The procedure ends.
9
9.1
Handling of unknown, unforeseen and erroneous protocol data

General
This subclause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to provide recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocol. The error handling procedures specified in this subclause shall apply to all RRC messages. When there is a specific handling for messages received on different logical channels this is specified. For system information received on the BCCH, the error handling procedures are applied on the BCCH message SYSTEM INFORMATION, the re-assembled system information segments as well as the system information blocks (including the master information block and the scheduling blocks), with specific error handling as specified below. When the UE receives an RRC message, it shall set the variable PROTOCOL_ERROR_REJECT to FALSE and then perform the checks in the order as defined below.
3GPP
Release 6
388
3GPP TS 25.331 V6.23.0 (2009-09)
The error cases specified in the following include the handling upon reception of spare values. This behaviour also applies in case the actual value of the IE results from mapping the originally sent IE value. Moreover, in certain error cases, as specified in the following, default values apply. In this case, the default values specified within the ASN.1, the tabular and the procedure specifications apply.
9.2
ASN.1 violation or encoding error
If the UE receives an RRC message on the DCCH for which the encoded message does not result in any valid abstract syntax value [49] (or "encoding error"), it shall perform the following. The UE shall: 1> set the variable PROTOCOL_ERROR_REJECT to TRUE; 1> transmit an RRC STATUS message on the uplink DCCH. The IE "Protocol error information" shall contain an IE "Protocol error cause" set to "ASN.1 violation or encoding error"; 1> when RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid message had not been received. NOTE In this case, the UE does not perform procedure specific error handling according to clause 8.
If the UE receives an RRC message sent via a radio access technology other than UTRAN, for which the encoded message does not result in any valid abstract syntax, the UE shall: 1> set the variable PROTOCOL_ERROR_REJECT to TRUE; 1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "ASN.1 violation or encoding error"; 1> perform procedure specific error handling according to clause 8. If a reassembled set of system information segments received in messages on the BCCH does not result in any valid abstract syntax value, the UE shall: 1> ignore the reassembled set of system information segments; 1> treat the rest of each message containing the ignored system information segments as if those segments were not present. If the UE receives an RRC message on the BCCH, PCCH, CCCH, MCCH, MSCH or SHCCH for which the encoded message does not result in any valid abstract syntax value, it shall ignore the message.
9.3
Unknown or unforeseen message type
If a UE receives an RRC message on the DCCH with a message type not defined for the DCCH it shall: 1> set the variable PROTOCOL_ERROR_REJECT to TRUE; 1> transmit an RRC STATUS message on the uplink DCCH. The IE "Protocol error information" shall contain an IE "Protocol error cause" set to "Message type non-existent or not implemented"; 1> when the RRC STATUS message has been submitted to lower layers for transmission: 2> continue with any ongoing processes and procedures as if the invalid message had not been received. If the UE receives an RRC message on the BCCH, PCCH, CCCH, MCCH, MSCH or SHCCH with a message type not defined for the logical channel type the message was received on, it shall ignore the message.
9.3a
-
Unsolicited received message
If the UE receives any of the following messages: an RRC CONNECTION SETUP message addressed to the UE on the CCCH; or
3GPP
Release 6
389
3GPP TS 25.331 V6.23.0 (2009-09)
an RRC CONNECTION REJECT message addressed to the UE on the CCCH; or a UE CAPABILITY INFORMATION CONFIRM message on the DCCH; or a CELL UPDATE CONFIRM message addressed to the UE on the CCCH or on the DCCH; or a URA UPDATE CONFIRM message addressed to the UE on the CCCH or on the DCCH
and no procedure is ongoing according to clause 8 which expects the message to be received: the UE shall: 1> ignore the received message.
9.3b
Unexpected critical message extension
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, containing an undefined critical message extension, the UE shall: 1> set the variable PROTOCOL_ERROR_REJECT to TRUE; 1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended"; 1> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: 2> store the IE "Message type" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and 2> set the IE "RRC transaction identifier" to zero in that table entry. 1> perform procedure specific error handling according to clause 8. If the UE receives an RRC message on the BCCH, MCCH, MSCH or PCCH, containing an undefined critical message extension, the UE shall: 1> ignore the message.
9.4
Unknown or unforeseen information element value, mandatory information element
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, with a mandatory IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined: 2> treat the rest of the message using the default value of the IE. 1> if no default value of the IE is defined: 2> set the variable PROTOCOL_ERROR_REJECT to TRUE; 2> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Information element value not comprehended"; 2> perform procedure specific error handling according to clause 8. If the UE receives a system information block on the BCCH with a mandatory IE having a value reserved for future extension (spare)or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined:
3GPP
Release 6
390
3GPP TS 25.331 V6.23.0 (2009-09)
2> treat the rest of the system information block using the default value of the IE. 1> if no default value of the IE is defined: 2> ignore the system information block. If the UE receives an RRC message on the BCCH, MCCH, MSCH or PCCH with a mandatory IE having a value reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined: 2> treat the rest of the message using the default value of the IE. 1> if no default value of the IE is defined: 2> ignore the message.
9.5
Conditional information element error
If the UE receives an RRC message on the DCCH, BCCH, PCCH, MCCH, MSCH or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, for which the specified conditions for absence of a conditional IE are met and that IE is present, the UE shall: 1> ignore the IE; 1> treat the rest of the message as if the IE was not present. If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, for which the specified conditions for presence of a conditional IE are met and that IE is absent, the UE shall: 1> set the variable PROTOCOL_ERROR_REJECT to TRUE; 1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to " Information element missing"; 1> perform procedure specific error handling according to clause 8. If the UE receives a system information block on the BCCH for which the specified conditions for presence of a conditional IE are met and that IE is absent, the UE shall: 1> ignore the system information block. If the UE receives an RRC message on the BCCH, MCCH, MSCH or PCCH for which the specified conditions for presence of a conditional IE are met and that IE is absent, the UE shall: 1> ignore the message.
9.6
Unknown or unforeseen information element value, conditional information element
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, for which the specified conditions for presence of a conditional IE are met, that IE is present, and that IE has a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined: 2> treat the rest of the message using the default value of the IE. 1> if no default value of the IE is defined: 2> set the variable PROTOCOL_ERROR_REJECT to TRUE;
3GPP
Release 6
391
3GPP TS 25.331 V6.23.0 (2009-09)
2> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Information element value not comprehended"; 2> perform procedure specific error handling according to clause 8. If the UE receives a system information block on the BCCH for which the specified conditions for presence of a conditional IE are met, that IE is present, and that IE has a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined: 2> treat the rest of the system information block using the default value of the IE. 1> if no default value of the IE is defined: 2> ignore the system information block. If the UE receives an RRC message on the BCCH, MCCH, MSCH or PCCH for which the specified conditions for presence of a conditional IE are met, that IE is present, and that IE has a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> if a default value of the IE is defined: 2> treat the rest of the message using the default value of the IE. 1> if no default value of the IE is defined: 2> ignore the message.
9.7
Unknown or unforeseen information element value, optional information element
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, with an optional IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), it shall: 1> ignore the value of the IE; 1> treat the rest of the message as if the IE was not present. If the UE receives a system information block on the BCCH with an optional IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), it shall: 1> ignore the value of the IE; 1> treat the rest of the system information block as if the IE was not present. If the UE receives an RRC message on the BCCH, MCCH or MSCH or PCCH with an optional IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), it shall: 1> ignore the value of the IE; 1> treat the rest of the message as if the IE was not present.
9.8
Unexpected non-critical message extension
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, containing an undefined non-critical message extension, the UE shall: 1> if the non critical extension is included in the "Variable Length Extension Container":
3GPP
Release 6
392
3GPP TS 25.331 V6.23.0 (2009-09)
2> ignore the content of the extension and the contents of this container after the not comprehended extension, and continue decoding the rest of the message. 1> otherwise: 2> ignore the content of the extension and the message contents after the extension, but treat the parts of the message up to the extension normally. If the UE receives a system information block on the BCCH containing an undefined non-critical message extension, the UE shall: 1> ignore the content of the extension and the system information block contents after the extension, but treat the parts of the system information block up to the extension normally. If the UE receives an RRC message on the BCCH, MCCH or MSCH or PCCH, containing an undefined non-critical message extension, the UE shall: 1> ignore the content of the extension and the message contents after the extension, but treat the parts of the message up to the extension normally.
9.9
Handling of errors in nested information elements
An erroneous IE may be included in another IE, which may be included in another IE and so on. This subclause specifies the handling of errors in mandatory IEs as well as for conditional IEs for which the specified conditions for presence are met, that are nested in another IE. In case the UE receives an IE (IE1) that includes a mandatory IE (IE1-1) having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> consider IE1 to have an undefined value; and 1> apply the corresponding generic error handling to IE1. In case there are many IE nesting levels, in all of which the IE is mandatory while no default value is defined, this treatment may need to be repeated several times. The following example illustrates the general principle.
ExampleMessage ::= SEQUENCE { ie1 IE1 OPTIONAL, ie2 IE2 } IE1 ::= SEQUENCE { ie1-1 INTEGER (1..16), -- ie1-1 values 13..16 are spare and should not be used in this version of the protocol ie1-2 IE1-2 OPTIONAL, ie1-3 IE1-3 }
If in the above example, UTRAN would include ie1 and set ie1-1 to value 13, the UE experiences an error in a mandatory IE. The guideline outlined in the previous then means that the UE shall not discard the entire message but instead consider "ie1" to have an unknown value. Since IE1 is optional, the generic error handling would be to ignore "ie1". In case the UE receives an IE (IE1) that includes a list of another IE (IE1-1) for which one or more entries in the list have a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall: 1> consider the list as if these entries were not included. NOTE: In case the above generic error handling procedures do not result in the desired behaviour, the introduction of spares may need to be reconsidered.
3GPP
Release 6
393
3GPP TS 25.331 V6.23.0 (2009-09)
10
10.1
Message and information element functional definition and content

General
The function of each Radio Resource Control message together with message contents in the form of a list of information elements is defined in subclause 10.2. Functional definitions of the information elements are then described in subclause 10.3. Information elements are marked as either MP - Mandatory present, MD - Mandatory with default value, OP - Optional, CV - Conditional on value or CH - Conditional on history (see Table 10.1 with information extracted from [14]). Table 10.1: Meaning of abbreviations used in RRC messages and information elements
Abbreviation MP Meaning Mandatory present A value for that information is always needed, and no information is provided about a particular default value. If ever the transfer syntax allows absence (e.g., due to extension), then absence leads to an error diagnosis. Mandatory with default value A value for that information is always needed, and a particular default value is mentioned (in the 'Semantical information' column). This opens the possibility for the transfer syntax to use absence or a special pattern to encode the default value. Conditional on value The need for a value for that information depends on the value of some other IE or IEs, and/or on the message flow (e.g., channel, SAP). The need is specified by means of a condition, the result of which may be that the information is mandatory present, mandatory with default value, not needed or optional. If one of the results of the condition is that the information is mandatory present, the transfer syntax must allow for the presence of the information. If in this case the information is absent an error is diagnosed. If one of the results of the condition is that the information is mandatory with default value, and a particular default value is mentioned (in the 'Semantical information' column), the transfer syntax may use absence or a special pattern to encode the default value. If one of the results of the condition is that the information is not needed, the transfer syntax must allow encoding the absence. If in this case the information is present, it will be ignored. In specific cases however, an error may be diagnosed instead. If one of the results of the condition is that the information is optional, the transfer syntax must allow for the presence of the information. In this case, neither absence nor presence of the information leads to an error diagnosis. Conditional on history The need for a value for that information depends on information obtained in the past (e.g., from messages received in the past from the peer). The need is specified by means of a condition, the result of which may be that the information is mandatory present, mandatory with default value, not needed or optional. The handling of the conditions is the same as described for CV. Optional The presence or absence is significant and modifies the behaviour of the receiver. However whether the
MD
CV
CH
OP
3GPP
Release 6 Abbreviation
394
3GPP TS 25.331 V6.23.0 (2009-09)
Meaning information is present or not does not lead to an error diagnosis.
10.1.1
Protocol extensions
RRC messages may be extended in future versions of this protocol, either by adding values for choices, enumerated and size constrained types or by adding information elements. An important aspect concerns the behaviour of a UE, conforming to this revision of the standard, upon receiving a not comprehended future extension. The details of this error handling behaviour are provided in clause 9. NOTE 1: By avoiding the need for partial decoding (skipping uncomprehended IEs to continue decoding the remainder of the message), the RRC protocol extension mechanism also avoids the overhead of length determinants for extensions. "Variable length extension containers" (i.e. non critical extension containers that have their abstract syntax defined using the ASN.1 type "BIT STRING") have been defined to support the introduction of extensions to a release after the subsequent release is frozen (and UEs based on that subsequent release may appear). For this container a length determinant is used, which facilitates partial decoding of the container as well as the decoding of the extensions included after the container. Two kinds of protocol extensions are distinguished: non-critical and critical extensions. In general, a receiver shall process a message including not comprehended non-critical extensions as if the extensions were absent. However, a receiver shall entirely reject a message including not comprehended critical extensions (there is no partial rejection) and notify the sender, as specified in clause 9. The general mechanism for adding critical extensions is by defining a new version of the message, which is indicated at the beginning of the message. The UE shall always comprehend the complete transfer syntax specified for the protocol version it supports; if the UE comprehends the transfer syntax defined within protocol version A for message 1, it shall also comprehend the transfer syntax defined within protocol version A for message 2. The following table shows for which messages only non-critical extensions may be added while for others both critical and non-critical extensions may be added. NOTE 2: Critical extensions can only be added to certain downlink messages.
Extensions Critical and non-critical extensions Message ACTIVE SET UPDATE 10.2.1 ASSISTANCE DATA DELIVERY 10.2.4 CELL CHANGE ORDER FROM UTRAN 10.2.5 CELL UPDATE CONFIRM 10.2.8 COUNTER CHECK 10.2.9 DOWNLINK DIRECT TRANSFER 10.2.11 HANDOVER TO UTRAN COMMAND 10.2.16a HANDOVER FROM UTRAN COMMAND 10.2.15 MEASUREMENT CONTROL 10.2.17 PHYSICAL CHANNEL RECONFIGURATION 10.2.22 PHYSICAL SHARED CHANNEL ALLOCATION 10.2.25 RADIO BEARER RECONFIGURATION 10.2.27 RADIO BEARER RELEASE 10.2.30 RADIO BEARER SETUP 10.2.33 RRC CONNECTION REJECT 10.2.36 RRC CONNECTION RELEASE 10.2.37 RRC CONNECTION SETUP 10.2.40 SECURITY MODE COMMAND 10.2.43 SIGNALLING CONNECTION RELEASE 10.2.46 TRANSPORT CHANNEL RECONFIGURATION 10.2.50 UE CAPABILITY ENQUIRY 10.2.55 UE CAPABILITY INFORMATION CONFIRM 10.2.57 UPLINK PHYSICAL CHANNEL CONTROL 10.2.59 URA UPDATE CONFIRM 10.2.61 UTRAN MOBILITY INFORMATION 10.2.62 ACTIVE SET UPDATE COMPLETE 10.2.2 ACTIVE SET UPDATE FAILURE 10.2.3 CELL CHANGE ORDER FROM UTRAN FAILURE 10.2.6
Non-critical extensions only
3GPP
Release 6 Extensions
395
3GPP TS 25.331 V6.23.0 (2009-09)
No extensions
Message CELL UPDATE 10.2.7 COUNTER CHECK RESPONSE 10.2.10 HANDOVER TO UTRAN COMPLETE 10.2.16b INITIAL DIRECT TRANSFER 10.2.16c HANDOVER FROM UTRAN FAILURE 10.2.16 MBMS ACCESS INFORMATION 10.2.16e MBMS COMMON P-T-M RB INFORMATION 10.2.16f MBMS CURRENT CELL P-T-M RB INFORMATION 10.2.16g MBMS GENERAL INFORMATION 10.2.16h MBMS MODIFICATION REQUEST 10.2.16i MBMS MODIFIED SERVICES INFORMATION 10.2.16j MBMS NEIGHBOURING CELL P-T-M RB INFORMATION 10.2.16k MBMS SCHEDULING INFORMATION 10.2.16L MBMS UNMODIFIED SERVICES INFORMATION 10.2.16m MEASUREMENT CONTROL FAILURE 10.2.18 MEASUREMENT REPORT 10.2.19 PAGING TYPE 1 10.2.20 PAGING TYPE 2 10.2.21 PHYSICAL CHANNEL RECONFIGURATION COMPLETE 10.2.23 PHYSICAL CHANNEL RECONFIGURATION FAILURE 10.2.24 PUSCH CAPACITY REQUEST 10.2.26 RADIO BEARER RECONFIGURATION COMPLETE 10.2.28 RADIO BEARER RECONFIGURATION FAILURE 10.2.29 RADIO BEARER RELEASE COMPLETE 10.2.31 RADIO BEARER RELEASE FAILURE 10.2.32 RADIO BEARER SETUP COMPLETE 10.2.34 RADIO BEARER SETUP FAILURE 10.2.35 RRC CONNECTION RELEASE COMPLETE 10.2.38 RRC CONNECTION REQUEST 10.2.39 RRC CONNECTION SETUP COMPLETE 10.2.41 RRC STATUS 10.2.42 SECURITY MODE COMPLETE 10.2.44 SECURITY MODE FAILURE 10.2.45 SIGNALLING CONNECTION RELEASE INDICATION 10.2.47 Master Information Block 10.2.48.8.1 System Information Block type 1 to System Information Block type 18 10.2.48.8.4 to 10.2.48.8.21 SYSTEM INFORMATION CHANGE INDICATION 10.2.49 TRANSPORT CHANNEL RECONFIGURATION COMPLETE 10.2.51 TRANSPORT CHANNEL RECONFIGURATION FAILURE 10.2.52 TRANSPORT FORMAT COMBINATION CONTROL 10.2.53 TRANSPORT FORMAT COMBINATION CONTROL FAILURE 10.2.54 UE CAPABILITY INFORMATION 10.2.56 UPLINK DIRECT TRANSFER 10.2.58 URA UPDATE 10.2.60 UTRAN MOBILITY INFORMATION CONFIRM 10.2.63 UTRAN MOBILITY INFORMATION FAILURE 10.2.64 SYSTEM INFORMATION 10.2.48 First Segment 10.2.48.1 Subsequent or last Segment 10.2.48.3 Complete SIB 10.2.48.5 SIB content 10.2.48.8.1
NOTE 3: For the SYSTEM INFORMATION message protocol extensions are only possible at the level of system information blocks.
10.1.1.1
10.1.1.1.1
Non-critical extensions
Extension of an information element with additional values or choices
In future versions of this protocol, non-critical values may be added to choices, enumerated and size constrained types. For choices, enumerated and size constrained types it is possible to indicate how many non-critical spare values need to be reserved for future extension. In this case, the tabular format should indicate the number of spare values that are
3GPP
Release 6
396
3GPP TS 25.331 V6.23.0 (2009-09)
needed. The value range defined in ASN.1 for the extensible IE should include the number of spares that are needed, since a value outside the range defined for this IE will result in a general ASN.1 violation error. For downlink messages, spare values may be defined for non-critical information elements for which the need is specified to be MD or OP (or CV case leading to MD or OP). In this case, a receiver not comprehending the received spare value shall consider the information element to have the default value or consider it to be absent respectively. For uplink messages spare values may be defined for all information elements, including those for which the need is specified to be MP (or CV case leading to MP). In all cases at most one spare should be defined for choices. In this case, information elements applicable to the spare choices shall be added to the end of the message.
10.1.1.1.2
Extension of a message with additional information elements
In future versions of this protocol, non-critical information elements may be added to RRC messages. These additional information elements shall be normally appended at the end of the message; the transfer syntax specified in this revision of the standard facilitates this. A receiver conformant to this revision of the standard shall accept such extension, and proceed as if it was not included. A transmitter conformant to this version of the standard shall not include an extension reserved for introducing non critical extensions in later versions of the standard; i.e. the corresponding parameter defined in the ASN.1 shall be absent. NOTE: If an extension, reserved for future non-critical extensions, is included (even if it is empty), this may result in transfer syntax errors when received by an implementation conforming to a later version of the standard.
Extensions to a release that are introduced after the subsequent release is frozen may however be inserted prior to the end of the message. To facilitate this, "variable length extension containers" have been introduced in most messages.
10.1.1.2
10.1.1.2.1
Critical extensions
Extension of an information element with additional values or choices
In versions of this protocol, choices, enumerated and size constrained types may be extended with critical values. For extension with critical values the general critical extension mechanism is used, i.e. for this no spare values are reserved since backward compatibility is not required.
10.1.1.2.2
Extension of a message with additional information elements
In future versions of this protocol, RRC messages may be extended with new information elements. Since messages including critical extensions are rejected by receivers not comprehending them, these messages may be modified completely, e.g. IEs may be inserted at any place and IEs may be removed or redefined.
10.2
10.2.1
NOTE:
Radio Resource Control messages

ACTIVE SET UPDATE
Only for FDD.
This message is used by UTRAN to add, replace or delete radio links in the active set of the UE. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type Need MP Multi Type and reference Message Semantics description Version
3GPP
Release 6 Information Element/Group name UE information elements RRC transaction identifier Need Multi
397 Type and reference Type
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version
MP
CH
Activation time
MD
New U-RNTI New H-RNTI New Primary E-RNTI New Secondary E-RNTI CN information elements CN Information info
OP OP OP OP
RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Activation time 10.3.3.1 U-RNTI 10.3.3.47 H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI 10.3.3.10a
Default value is "now".
REL-6 REL-6 REL-6
OP
CN Information info 10.3.1.3
Phy CH information elements Uplink radio resources Maximum allowed UL TX power
MD
Maximum allowed UL TX power 10.3.6.39
Default value is the existing "maximum UL TX power.
Downlink radio resources Radio link addition information >Radio link addition information
OP
1 to <maxRL -1> Radio link addition information 10.3.6.68 1 to <maxRL > Radio link removal information 10.3.6.69 TX Diversity Mode 10.3.6.86
Radio link addition information required for each RL to add
MP
Radio link removal information >Radio link removal information
OP
Radio link removal information required for each RL to remove
MP
TX Diversity Mode
MD
Default value is the TX diversity mode currently used in all or part of the active set.
3GPP
Release 6 Information Element/Group name DPC Mode Need OP Multi
398 Type and reference Enumerate d (Single TPC, TPC triplet in soft) Serving HS-DSCH cell information 10.3.6.74a E-DCH reconfigura tion information 10.3.6.69a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description "Single TPC" is DPC_Mode=0 and "TPC triplet in soft" is DPC_mode=1 in [29]. Version REL-5
Serving HS-DSCH cell information
OP
REL-6
E-DCH reconfiguration information
OP
REL-6
10.2.2
NOTE:
ACTIVE SET UPDATE COMPLETE

For FDD only.
This message is sent by UE when active set update has been completed. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Semantics description
MP
CH
10.2.3
NOTE:
ACTIVE SET UPDATE FAILURE

Only for FDD.
This message is sent by UE if the update of the active set has failed, e.g. because the radio link is not a part of the active set. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
Release 6 Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP
399 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description
MP
CH
Failure cause
MP
10.2.4
ASSISTANCE DATA DELIVERY
This message is sent by UTRAN to convey UE positioning assistance data to the UE. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
MP
CH
Measurement Information elements UE positioning OTDOA assistance data for UE-based
OP
OP
UE positioning OTDOA assistance data for UEbased 10.3.7.103a UE positioning GPS assistance data 10.3.7.90
3GPP
Release 6
400
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.5
This message is used to order a cell change from UTRA to another radio access technology, e.g., GSM. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type Semantics description Version
MP
Integrity check info Activation time RB Information elements RAB information list
CH MD
RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Activation time 10.3.3.1
Default value is "now"
OP
1 to <maxRA Bsetup> RAB info 10.3.4.8
This IE should not be included in this version of the protocol.
>RAB info Other information elements Target cell description >CHOICE Radio Access Technology >>GSM >>>BSIC >>>Band Indicator
MP
MP MP
Two spare values are needed. BSIC 10.3.8.2 Enumerated (DCS 1800 band used, PCS 1900 band used) Integer (0..1023) Bit string(3)
MP MP
Indicates how to interpret the BCCH ARFCN
>>>BCCH ARFCN >>>NC mode
MP OP
[45] Includes bits b1-b3 of the NC mode IE specified in [43]. b1 is the least significant bit. NOTE: The Bit string should be extended to 4 bits in a later version of the message. REL-5
>>>CHOICE GERAN System Info type >>>>SI
OP GERAN system information 10.3.8.4f GERAN system information 10.3.8.4f See [44]
REL-5
>>>>PSI
See [44]
REL-5
>>IS-2000
3GPP
Release 6
401
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.6
CELL CHANGE ORDER FROM UTRAN FAILURE
This message is sent on the RRC connection used before the Cell change order from UTRAN was executed. The message indicates that the UE has failed to seize the new channel in the other radio access technology. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Inter-RAT change failure 10.3.8.5 Semantics description
MP
CH
Other information elements Inter-RAT change failure
MP
10.2.7
CELL UPDATE
This message is used by the UE to initiate a cell update procedure. RLC-SAP: TM Logical channel: CCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements U-RNTI RRC transaction identifier Need MP Multi Type and reference Message Type Semantics description Version
MP CVFailure
CH
U-RNTI 10.3.3.47 RRC transactio n identifier 10.3.3.36 Integrity check info 10.3.3.16 1 to <maxCN domains > CN domain identity 10.3.1.1 START [40] values for all CN domains.
START list
MP
>CN domain identity
MP
3GPP
Release 6 Information Element/Group name >START AM_RLC error indication(RB2, RB3 or RB4) Need MP MP Multi
402 Type and reference START 10.3.3.38 Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description START value to be used in this CN domain. TRUE indicates AM_RLC unrecoverable error [16] occurred on RB2, RB3 or RB4 in the UE TRUE indicates AM_RLC unrecoverable error [16] occurred on RB>4 in the UE Version
AM_RLC error indication(RB>4)
MP
Boolean
Cell update cause
MP
Traffic volume indicator
OP
Cell update cause 10.3.3.3 Enumerat ed (true)
This IE shall be set to TRUE when the criteria for event based traffic volume measurement reporting is fulfilled. Absence of this element means not fulfilled.
REL-6
Failure cause
OP
RB timer indicator
MP
Establishment cause
OP
Reconfiguration Status Indicator
OP
Failure cause and error informatio n 10.3.3.14 RB timer indicator 10.3.3.28 Establish ment cause 10.3.3.11 Enumerat ed (true)
REL-5
TRUE indicates a reconfiguration procedure is ongoing within the UE or a response message has been submitted to RLC and the UE is waiting for the layer 2 ACK.
REL-6
MBMS Selected Services
OP
MBMS Selected Services Short 10.3.9a.7 d
REL-6
Measurement information elements Measured results on RACH
OP
Measured results on RACH 10.3.7.45
Condition Failure
Explanation This IE is mandatory present if the IE "Failure cause" is present and not needed otherwise.
3GPP
Release 6
403
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.8
CELL UPDATE CONFIRM
This message confirms the cell update procedure and can be used to reallocate new RNTI information for the UE valid in the new cell. RLC-SAP: UM Logical channel: CCCH or DCCH Direction: UTRANUE
Information Element/Group name Message Type UE Information Elements U-RNTI RRC transaction identifier Need MP Multi Type and reference Message Type U-RNTI 10.3.3.47 RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Semantics description Version
CV-CCCH MP
CH
OP
Ciphering mode info
OP
Ciphering mode info 10.3.3.5
Activation time New U-RNTI New C-RNTI New DSCH-RNTI
MD OP OP OP
Activation time 10.3.3.1 U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 DSCH-RNTI 10.3.3.9a
The UTRAN should not include this IE unless it is performing an SRNS relocation or a cell reselection from GERAN Iu mode The UTRAN should not include this IE unless it is performing either an SRNS relocation or a cell reselection from GERAN Iu mode, and a change in ciphering algorithm. Default value is "now"
Should not be set in FDD. If received, the UE should ignore it REL-5 REL-6 REL-6
New H-RNTI New Primary E-RNTI New Secondary E-RNTI RRC State Indicator
OP OP OP MP
UTRAN DRX cycle length coefficient
OP
H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI 10.3.3.10a RRC State Indicator 10.3.3.35a UTRAN DRX cycle length coefficient 10.3.3.49
3GPP
Release 6 Information Element/Group name RLC re-establish indicator (RB2, RB3 and RB4) Need MP
404 Multi Type and reference RLC reestablish indicator 10.3.3.35
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Should not be set to TRUE if IE "Downlink counter synchronisation info" is included in message. Should not be set to TRUE if IE "Downlink counter synchronisation info" is included in message. Version
RLC re-establish indicator (RB5 and upwards)
MP
RLC reestablish indicator 10.3.3.35
CN Information Elements CN Information info
OP
CN Information info 10.3.1.3 URA identity 10.3.2.6 1 to <maxRB> RB information to release 10.3.4.19 1 to <maxRB> RB information to reconfigure 10.3.4.18 1 to <maxRB> RB information to be affected 10.3.4.17
UTRAN Information Elements URA identity RB information elements RB information to release list >RB information to release
OP
OP MP
RB information to reconfigure list >RB information to reconfigure
OP MP
RB information to be affected list >RB information to be affected
OP MP
Downlink counter synchronisation info >RB with PDCP information list
OP OP 1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 This IE is needed for each RB having PDCP in the case of lossless SRNS relocation This IE is needed for each RB having PDCP and performing PDCP context relocation REL-5 REL-5
>>RB with PDCP information
MP
>>PDCP context relocation info
OP OP
PDCP ROHC target mode
OP
PDCP context relocation info 10.3.4.1a PDCP ROHC target mode 10.3.4.2a
REL-5
TrCH Information Elements Uplink transport channels UL Transport channel information common for all
OP
UL Transport channel
3GPP
Release 6 Information Element/Group name transport channels Need
405 Multi Type and reference information common for all transport channels 10.3.5.24
Deleted TrCH information list
OP
1 to <maxTrCH > Deleted UL TrCH information 10.3.5.5 1 to <maxTrCH > Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH > Deleted DL TrCH information 10.3.5.4 1 to <maxTrCH > Added or Reconfigure d DL TrCH information 10.3.5.1 Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88. E-DCH Info 10.3.6.97 Downlink HS_PDSCH Information 10.3.6.23a Downlink information common for Default value is the existing maximum UL TX power
>Deleted UL TrCH information
MP
Added or Reconfigured TrCH information list >Added or Reconfigured UL TrCH information
OP
MP
Downlink transport channels DL Transport channel information common for all transport channels
OP
OP
>Deleted DL TrCH information
MP
Added or Reconfigured TrCH information list >Added or Reconfigured DL TrCH information
OP
MP
PhyCH information elements Frequency info
OP
Uplink radio resources Maximum allowed UL TX power
MD
Uplink DPCH info
OP
E-DCH Info Downlink radio resources Downlink HS-PDSCH Information
OP
REL-6
OP
REL-5
OP
3GPP
Release 6 Information Element/Group name Need
406 Multi Type and reference all radio links 10.3.6.24
OP
1 to <maxRL>
Send downlink information for each radio link to be set-up Downlink information for each radio link 10.3.6.27 Enumerated (TRUE)
>Downlink information for each radio link
MP
OP
REL-6
Condition CCCH
Explanation This IE is mandatory present when CCCH is used and ciphering is not required and not needed otherwise.
10.2.9
COUNTER CHECK
This message is used by the UTRAN to indicate the current COUNT-C MSB values associated to each radio bearer utilising UM or AM RLC mode and to request the UE to compare these to its COUNT-C MSB values and to report the comparison results to UTRAN. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements RRC transaction identifier Presence MP MP RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 1 to < maxRBallR ABs > RB COUNTC MSB information 10.3.4.14 For each RB (excluding signalling radio bearers) using UM or AM RLC. Multi IE type and reference Semantics description
CH
RB information elements RB COUNT-C MSB information
MP
>RB COUNT-C MSB information
MP
10.2.10 COUNTER CHECK RESPONSE

This message is used by the UE to respond to a COUNTER CHECK message. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
Release 6 Information Element/Group name Message Type UE information elements RRC transaction identifier Presence MP MP
407 Multi IE type and reference
CH
RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 1 to < maxRBallR ABs > RB COUNTC information 10.3.4.15
RB information elements RB COUNT-C information
OP
>RB COUNT-C information
MP
10.2.11 DOWNLINK DIRECT TRANSFER

This message is sent by UTRAN to transfer higher layer messages. RLC-SAP: AM Logical channel: DCCH Direction: UTRAN -> UE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Core Network Domain Identity 10.3.1.1 NAS message 10.3.1.8 Semantics description
MP
CH
CN information elements CN Domain Identity
MP
NAS message
MP
10.2.12 Void
10.2.13 Void
3GPP
Release 6
408
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.14 Void
10.2.15 HANDOVER FROM UTRAN COMMAND

This message is used for handover from UMTS to another system e.g. GSM. One or several messages from the other system can be included in the Inter-RAT message information element in this message. These messages are structured and coded according to that systems specification. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
MP
CH
Activation time
MD
RRC transactio n identifier 10.3.3.36 Integrity check info 10.3.3.16 Activation time 10.3.3.1
RB information elements RAB information list
OP
1 to <maxRA Bsetup>
For each RAB to be handed over. In handover to GERAN Iu mode the RAB information is included in the GERAN Iu message below. RAB info 10.3.4.8
>RAB info Other information elements CHOICE System type
MP
MP
This IE indicates which specification to apply, to decode the transported messages Enumerat ed (GSM/DC S 1800 band used), GSM/PC S 1900 band used) Bit string (no explicit size Formatted and coded according to GSM specifications The first/leftmost/most
>GSM >>Frequency band
MP
>>GSM message >>>Single GSM message
MP
3GPP
Release 6 Information Element/Group name Need Multi
409 Type and reference constraint )
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description significant bit of the bit string contains bit 8 of the first octet of the GSM message. Formatted and coded according to GSM specifications. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the GSM message. REL-6 Version
>>>GSM message List
MP
1.to.<ma xInterSy sMessa ges>
Bit string (1..512)
>>CHOICE GERAN System Info type >>>SI
OP GERAN system informatio n 10.3.8.4f GERAN system informatio n 10.3.8.4f MP Enumerat ed (GSM/DC S 1800 band used), GSM/PC S 1900 band used) Bit string (no explicit size constraint ) 1 to <maxInt erSysMe ssages> Bit string (1..32768) Formatted and coded according to [53]. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the message. Formatted and coded according to [53]. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the message. See [44]
REL-6
>>>PSI
See [44]
REL-6
>GERAN Iu >>Frequency band
REL-5 REL-5
>>GERAN Iu message >>>Single GERAN Iu message
MP
REL-5 REL-5
>>>GERAN Iu message List
MP
REL-5
>cdma2000 >>cdma2000MessageLis t
MP
1.to.<ma xInterSy sMessa ges> Bit string (8) Formatted and coded according to cdma2000 specifications. The MSG_TYPE bits are numbered b0 to b7. The first/leftmost/most significant bit of the bit string contains bit 7 of the MSG_TYPE. Formatted and coded according to cdma2000
>>>MSG_TYPE(s)
MP
>>>cdma2000Messagep ayload(s)
MP
Bit string (1..512)
3GPP
410 Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description specifications. The first/leftmost/most significant bit of the bit string contains the bit 7 of the first octet of the cdma2000 message. Version
10.2.16 HANDOVER FROM UTRAN FAILURE

This message is sent on the RRC connection used before the Inter-RAT Handover was executed. The message indicates that the UE has failed to seize the new channel in the other system. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
MP
CH
RRC transactio n identifier 10.3.3.36 Integrity check info 10.3.3.16
Other information elements Inter-RAT handover failure
OP
Inter-RAT handover failure 10.3.8.6 This IE indicates which specification to apply to decode the transported messages 1.to.<ma xInterSy sMessa ges> Bit string (1..512) Formatted and coded according to GSM specifications. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the GSM message. Formatted and coded according to [53]. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the message. REL-5 REL-5
CHOICE System type
OP
>GSM >>GSM message List
MP
>GERAN Iu >>GERAN Iu message List
MP
1 to <maxInt erSysMe ssages>
Bit string (1..32768)
>cdma2000 >>cdma2000MessageLis t
MP
1.to.<ma xInterSy sMessa ges>
3GPP
Release 6 Information Element/Group name >>>MSG_TYPE(s) Need MP Multi
411 Type and reference Bit string (8)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Formatted and coded according to cdma2000 specifications. The MSG_TYPE bits are numbered b0 to b7. The first/leftmost/most significant bit of the bit string contains bit 7 of the MSG_TYPE. Formatted and coded according to cdma2000 specifications. The first/leftmost/most significant bit of the bit string contains bit 7 of the first octet of the cdma2000 message. Version
MP
Bit string (1..512)
10.2.16a HANDOVER TO UTRAN COMMAND

This message is sent to the UE via other system to make a handover to UTRAN. RLC-SAP: N/A (Sent through a different RAT) Logical channel: N/A (Sent through a different RAT) Direction: UTRAN UE
Information Element/Group name New U-RNTI Need MP Multi Type and reference U-RNTI Short 10.3.3.48 Ciphering algorithm 10.3.3.4 H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI 10.3.3.10a Semantics description Version
Ciphering algorithm
OP
UE HSPA Identities >New H-RNTI >New Primary E-RNTI >New Secondary E-RNTI CHOICE specification mode >Complete specification RB information elements >>Signalling RB information to setup list
OP OP OP OP MP
REL-6 REL-6 REL-6
MP
1 to <maxSRBsetup>
For each signalling radio bearer established Signalling RB information to setup 10.3.4.24
>>>Signalling RB information to setup
MP
>>RAB information to setup list >>>RAB information for setup
OP MP
1 to <maxRABsetup> RAB information for setup 10.3.4.10 UL Transport
For each RAB established
Uplink transport channels >>UL Transport channel information common for all
MP
3GPP
Release 6 Information Element/Group name transport channels Need Multi
412 Type and reference channel information common for all transport channels 10.3.5.24
>>Added or Reconfigured TrCH information >>>Added or Reconfigured UL TrCH information
MP MP
1 to <maxTrCH> Added or Reconfigure d UL TrCH information 10.3.5.2
Downlink transport channels >>DL Transport channel information common for all transport channels
MP
DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH> Added or Reconfigure d DL TrCH information 10.3.5.1 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH Information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <maxRL> Downlink information for each radio link 10.3.6.27
>>Added or Reconfigured TrCH information >>>Added or Reconfigured DL TrCH information
MP MP
Uplink radio resources >>Uplink DPCH info
MP
OP
REL-6
OP
REL-6
>>Downlink information common for all radio links
MP
>>Downlink information per radio link >>>Downlink information for each radio link
MP MP
>Preconfiguration >>CHOICE Preconfiguration mode >>>Predefined configuration
MP MP Predefined configuration identity 10.3.4.5 Enumerated (FDD, TDD) Indicates whether the FDD or TDD version of the
>>>Default configuration >>>>Default configuration mode
MP
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description default configuration shall be used Version
>>>>Default configuration identity
MP
>>RAB info
OP
>>Uplink DPCH info
MP
Default configuration identity 10.3.4.0 RAB info Post 10.3.4.9 Uplink DPCH info Post 10.3.6.89 Downlink information common for all radio links Post 10.3.6.25 1 to <maxRL>
One RAB is established
Downlink radio resources >>Downlink information common for all radio links
MP
>>Downlink information per radio link
MP
Send downlink information for each radio link to be setup. In TDD MaxRL is 1. Downlink information for each radio link Post 10.3.6.28 (no data)
>>>Downlink information for each radio link
MP
>>CHOICE mode >>>FDD >>>TDD >>>>Primary CCPCH Tx Power
MP
MP
Frequency info
MP
MP
Primary CCPCH Tx Power 10.3.6.59 Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39
10.2.16b HANDOVER TO UTRAN COMPLETE

This message is sent by the UE when a handover to UTRAN has been completed. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type Need MP Multi Type and reference Message Type Semantics description
3GPP
Release 6 Information Element/Group name UE Information elements START list Need
414 Multi Type and reference
CH
1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 Activation time 10.3.3.1
START [40] values for all CN domains.
>CN domain identity
MP
>START RB Information elements COUNT-C activation time
MP
OP
Used for radio bearers mapped on RLC-TM.
3GPP
Release 6
415
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.16c INITIAL DIRECT TRANSFER

This message is used to initiate a signalling connection based on indication from the upper layers, and to transfer a NAS message. RLC-SAP: AM Logical channel: DCCH Direction: UE -> UTRAN
Information Element/Group name Message Type UE information elements Integrity check info Need MP Multi Type and reference Message Type Semantics description Version
CH
PLMN identity
OP
Integrity check info 10.3.3.16 PLMN identity 10.3.1.11
This IE indicates the PLMN to which the UE requests the signalling connection to be established.
REL-6
CN information elements CN domain identity
MP
Intra Domain NAS Node Selector
MP
NAS message
MP
START
OP
CN domain identity 10.3.1.1 Intra Domain NAS Node Selector 10.3.1.6 NAS message 10.3.1.8 START 10.3.3.38
START value to be used in the CN domain as indicated in the IE "CN domain identity". This IE shall always be present in this version of the protocol. Rel-5
Establishment cause
OP
Establish ment cause 10.3.3.11
OP
Measured results on RACH 10.3.7.45 P-TMSI (GSMMAP) 10.3.1.13 REL-6 REL-6
MBMS joined information >P-TMSI
OP OP
3GPP
Release 6
416
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.16d INTER RAT HANDOVER INFO

This message is sent by the UE via another radio access technology to provide information to the target RNC when preparing for a handover to UTRAN. RLC-SAP: N/A (Sent through a different RAT) Logical channel: N/A (Sent through a different RAT) Direction: UE UTRAN
Information Element/Group Name Radio Bearer IEs Predefined configuration status information Need Multi Type and reference Predefined configuration status information 10.3.4.5a Predefined configuration status information compressed 10.3.4.5b Semantics description Version
OP
Predefined configuration status information compressed
OP
REL-5
UE Information elements UE security information
OP
UE security information2
OP
UE Specific Behaviour Information 1 interRAT
OP
UE security information 10.3.3.42b UE security information2 10.3.3.42c UE Specific Behaviour Information 1 interRAT 10.3.3.52 UE radio access capability 10.3.3.42 UE radio access capability extension 10.3.3.42a UE radio access capability compressed 10.3.3.42o UE radio access capability comp 2 10.3.3.42oa
REL-6
This IE shall not be included in this version of the protocol
UE capability container >UE radio access capability
OP MP
>UE radio access capability extension
MP
Although this IE is not always required, the need has been set to MP to align with the ASN.1 REL-5
UE radio access capability compressed
OP
UE radio access capability comp 2
CV-Fdd
REL6
Condition Fdd
Explanation This IE is mandatory present for FDD, otherwise it is not needed.
3GPP
Release 6
417
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.16e MBMS ACCESS INFORMATION

This message is transmitted periodically by UTRAN to inform UEs that have joined or selected a particular MBMS service about the need to establish an RRC connection or to perform a cell update. While the message contents may change within a modification period, all occurances of the information within a modification period concern the same MBMS service(s). RLC-SAP: UM Logical channel: MCCH Direction: UTRAN UE
Information Element/Group name Message type Service list Need MP MP 1 to <maxMB MSserv Count> MBMS Short transmissi on identity 10.3.9a.1 0 Integer (0 to 960 by step of 32, 1000) Reference/ index to a transmission listed in the MBMS MODIFIED SERVICES INFORMATION or MBMS UNMODIFIED SERVICES INFORMATION Access probability factor for UEs in idle mode. The actual Access Probability (AP) is a function of the Access Probability Factor (APF): -(APF/100) AP (APF) = 2 Access probability factor for UEs in connected mode. The actual Access Probability (AP) is a function of the Access Probability Factor (APF): -(APF/100) AP (APF) = 2 Default value is the value included in IE "Access probability factor - Idle" >Connected mode counting scope >>URA_PCH MP MP BOOLEA N BOOLEA N BOOLEA N TRUE means that UEs in URA_PCH state shall participate in counting TRUE means that UEs in CELL_PCH state shall participate in counting TRUE means that UEs in CELL_FACH state shall participate in counting REL-6 REL-6 Multi Type and reference Message Type Semantics description Version REL-6 REL-6
>MBMS short transmission ID
MP
REL-6
>Access probability factor - Idle
MP
REL-6
>Access probability factor connected
MD
Integer (0 to 960 by step of 32, 1000)
REL-6
>>CELL_PCH
MP
REL-6
>> CELL_FACH
MP
REL-6
10.2.16f MBMS COMMON P-T-M RB INFORMATION

This message is transmitted periodically by UTRAN to inform UEs about the p-t-m RB configuration information that may be common between different services, applicable in the current and/ or in neighbouring cells. The message contents does not change within a modification period. RLC-SAP: UM Logical channel: MCCH
3GPP
Release 6
418
3GPP TS 25.331 V6.23.0 (2009-09)
Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message type RB information list Need MP MP 1 to <maxMB MSCommo nRB> Multi
419 Type and reference Message Type
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version REL-6 REL-6
>RB identity
MP
>PDCP info
MP
>RLC info
MP
MBMS Common RB identity 10.3.9a.3 PDCP info 10.3.4.2 RLC info MBMS 10.3.4.23 a 1 to <maxMB MSCommo nTrCh> MBMS Common TrCh identity 10.3.9a.4 Transport format set 10.3.5.23 1 to <maxMB MSCommo nCCTrC h> MBMS Common CCTrCh identity 10.3.9a.1 Transport format combinati on set 10.3.5.20 1 to <maxMB MSCommo nPhyCh > MBMS Common PhyCh identity 10.3.9a.2 Secondar y CCPCH info MBMS 10.3.6.71 a The list needs not include the CCTrCh for which the default TFCS for MBMS applies, as specified in subclause 14.10.1.
REL-6
REL-6
REL-6
TrCh information for each TrCh
MP
REL-6
>Transport channel identity
MP
REL-6
>TFS
MP
REL-6
TrCh information for each CCTrCh
OP
REL-6
>CCTrCH identity
MP
REL-6
>TFCS
MP
REL-6
PhyCh information
MP
REL-6
>PhyCh identity
MP
REL-6
>Secondary CCPCH info MBMS
MP
REL-6
3GPP
Release 6
420
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.16g MBMS CURRENT CELL P-T-M RB INFORMATION

This message is transmitted periodically by UTRAN to inform UEs about the PTM RB configuration used to in a cell, in case one or more MBMS service is provided using p-t-m radio bearers. The message contents does not change within a modification period. RLC-SAP: UM Logical channel: MCCH Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message type S-CCPCH list Need MP OP 1 to <maxSC CPCH> Multi
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Current cell PTM RB info Absent in case MTCH are only mapped to the S-CCPCH(s) included in SIB type 5 or 5bis When L1- or L2 combining applies, this identity is used to refer to this S-CCPCH within the NEIGHBOURING CELL P-T-M RB INFORMATION message Refers to a configuration in the common RB info Version REL-6 REL-6
>S-CCPCH identity
OP
>Secondary CCPCH info
MP
>MBMS Soft Combining Timing Offset
CV-SoftFDD
>TrCh information common for all TrCh
MD
MBMS Current cell SCCPCH identity 10.3.9a.5 MBMS Common PhyCh identity 10.3.9a.2 MBMS Soft Combinin g Timing Offset 10.3.9a.1 0a MBMS Common CCTrCh identity 10.3.9a.1 1 to <maxFA CHPCH > MBMS Common TrCh identity 10.3.9a.4 1 to <maxRB perTrCh > MBMS pt-m RB informatio n 10.3.9a.7 a MSCH configurat ion informatio n 10.3.9a.1 6 1 to <maxSC CPCH> Integer (1..maxS CCPCH)
REL-6
REL-6
Timing offset applied in the CFN calculation in sub-clause 8.5.15.5. The default value is 0 ms.
REL-6
Refers to a (TFCS) configuration in the common RB info The default value of the TFCS is specified in subclause 14.10.1 List of FACH transport channels carrying one or more MTCH and optionally one MSCH Refers to a (TFS) configuration in the common RB info
REL-6
>TrCH information list
MP
REL-6
>>TrCh information
MP
REL-6
>>RB information list
OP
The IE is absent if temporarily no RBs are mapped to this TrCh or if the TrCH only carries MSCH
REL-6
>>>RB information
MP
REL-6
>>MSCH configuration information
OP
REL-6
S-CCPCH in SIB type 5
OP
>S-CCPCH identity
Every S-CCPCHs included in SIB type 5 or 5bis may carry MTCH Index of the S-CCPCH within the list included in SIB type 5 or 5bis List of FACH transport channels carrying one or more MTCH and optionally one MSCH
REL-6
REL-6
>TrCH information list
MP
1 to <maxFA CHPCH > Integer (1..maxF
REL-6
>>TrCh identity
MP
Index of the FACH within the list of TrChs defined for that S-
REL-6
3GPP
422 Type and reference ACHPCH)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description CCPCH as included in SIB type 5 or 5bis The IE is absent if this TrCh only carries MSCH Version
>>RB information list
OP
1 to <maxRB perTrCh > MBMS pt-m RB informatio n 10.3.9a.7 a MSCH configurat ion informatio n 10.3.9a.1 6
REL-6
>>>RB information
MP
REL-6
>>MSCH configuration information
OP
Included if the TrCH carries MSCH
REL-6
Condition Soft-FDD
Explanation This IE is used only for FDD. It is mandatory default for FDD if the IE "L1 combining" is included in MBMS NEIGHBOURING CELL P-T-M RB INFORMATION. Otherwise it is not needed.
10.2.16h MBMS GENERAL INFORMATION

This message is transmitted periodically by UTRAN to inform UEs about the general MBMS (configuration) information. The message contents does not change within a modification period. RLC-SAP: UM Logical channel: MCCH Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message type MBMS preferred frequency information Need MP OP Multi
423 Type and reference Message Type MBMS preferred frequency informatio n 10.3.7.43 a MBMS specific timers and counters 10.3.9a.1 1 MICH configurat ion informatio n 10.3.9a.1 4 Bit string (12)
MBMS timers and counters
MP
REL-6
MICH configuration information
MP
REL-6
Cell group identity
MP
Default MSCH configuration information
OP
Indicate changes in MBMS Selected Services
MD
MSCH configurat ion informatio n 10.3.9a.1 6 Boolean
Identifies the group of cells for which the same common RLC and PDCP entity is used as the current cell The default MSCH configuration
REL-6
REL-6
True means the UE indicates changes in MBMS Selected Services while in URA_PCH, CELL_PCH or in CELL_FACH Default value is FALSE
REL-6
10.2.16i MBMS MODIFICATION REQUEST

The UE transmits this message to request UTRAN to take certain actions to improve the UE's ability to receive its (prioritised) activated MBMS services and/ or sessions. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
3GPP
Release 6 Information Element/Group name Message type UE information elements Integrity check info Need MP Multi
CH
Integrity check info 10.3.3.16
REL-6
MBMS information elements MBMS preferred frequency request
REL-6 OP MBMS service identity 10.3.9a.8 The MBMS preferred frequency the UE would like to be moved to. The MBMS preferred frequency is identified by the identity of the MBMS service the UE would like to receive RBs of lower priority MBMS services inhibiting reception of a higher priority service REL-6
MBMS RB list requested to be released >RB information to release
OP
1 to <maxRB > RB informatio n to release 10.3.4.19 MBMS Selected Service Info 10.3.9a.7 b Enumerat ed (true)
REL-6
MP
REL-6
MBMS Selected Service Info
OP
REL-6
Support of MBMS service change for a ptp RB
OP
Indicates that the UE supports the actions upon reception of IE RAB information for MBMS ptp bearer
REL-6
10.2.16j MBMS MODIFIED SERVICES INFORMATION

This information is transmitted periodically by UTRAN to inform UEs about a change applicable for one or more MBMS services available in the current cell and possibly in neighbouring cells. RLC-SAP: AM (DCCH only) or UM Logical channel: MCCH, DCCH Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message type UE information elements Integrity check info Need MP Multi
CVDCCHC H
Integrity check info is included if integrity protection is applied
REL-6
MBMS information elements Modified service list
REL-6 OP 1.. <maxMB MSserv Modif> MBMS Transmis sion identity 10.3.9a.1 2 Enumerat ed (None, Acquire counting info, Acquire counting info PTM RBs unmodifie d, Acquire PTM RB info, RequestP TP RB, Release PTM RB) REL-6
>MBMS Transmission identity
MP
REL-6
>MBMS required UE action
MP
Indicates required UE action upon receiving the message. When sent on the DCCH, only the following values apply: None, Acquire PTM RB info, request PTP RB).
REL-6
>MBMS preferred frequency >>PFL index
OP
CVMCCH
>>PFL info
CVDCCH MP
>Continue MCCH reading
Integer (1.. <maxMB MSFreq>) Frequenc y info 10.3.6.36 BOOLEA N
Indicates the frequency that UEs shall consider as the preferred frequency. Index pointing to an entry in the list included in MBMS GENERAL INFORMATION.
REL-6
REL-6
REL-6
MCCH inband notification. Indicates whether or not the UE should continue reading MCCH in the next modification period. Not applicable when sent on the DCCH
REL-6
MBMS re- acquire MCCH
MBMS dynamic persistence level
CVMCCHO P CVMCCHO P CVMCCHO P
Enumerat ed (True) Dynamic persistenc e level 10.3.6.35 Integer (1..16)
REL-6
REL-6
End of modified MCCH information
If present: the UE may assume that, in each repetition period, all the MCCH information preceding the MBMS UNMODIFIED SERVICES INFORMATION message is transmitted within the
REL-6
3GPP
Release 6 Information Element/Group name MBMS number of neighbour cells Need Multi
426 Type and reference Integer (0..32)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description indicated number of TTIs. Indicates the number of MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages that are contained within the MCCH transmission. Not applicable when sent on the DCCH. True means that the UE should re-acquire the PtM information for all services listed in the message MBMS UNMODIFIED SERVICES INFORMATION with the IE MBMS required UE action set to Acquire PTM RB info Version
MP
REL-6
MBMS all unmodified p-tm services
CVMCCHO P
Enumerat ed (True)
REL-6
CVMCCHO P
MBMS pt-m activation time 10.3.9a.7 o
REL-6
Condition MCCH DCCH MCCHOP DCCHCH
Explanation This IE is mandatory present if the message is sent via MCCH and not needed otherwise. This IE is mandatory present if the message is sent via DCCH and not needed otherwise. This IE is optionally present if the message is sent via MCCH and not needed otherwise. This IE is present conditionnaly on history if the message is sent via DCCH and not present otherwise.
10.2.16k MBMS NEIGHBOURING CELL P-T-M RB INFORMATION

This message is transmitted periodically by UTRAN to inform UEs about the p-t-m RB configuration used to in neighbouring cells, indicating the UE may perform selection and/ or soft combining. The message content does not change within a modification period. RLC-SAP: UM Logical channel: MCCH Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message type Neighbouring cell identity Need MP MP Multi
427 Type and reference Message Type Integer (0..<max CellMeas 1>)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version REL-6 The intra-frequency cell id of the cell obtained from the IE 'Intrafrequency Cell Info list' in SIB 11/ SIB 11bis. In case the intrafrequency cell id is omitted in the IE Intra-frequency Cell Info list in SIB 11/SIB11bis, it refers to the index (starting at zero) in the CELL_INFO_LIST as if the CELL_INFO_LIST was constructed from SIB11/SIB11bis only, see 8.6.7.3. REL-6
Neighbouring cells SCCPCH list >Secondary CCPCH info
MP
1 to <maxSC CPCH> MBMS Common PhyCh identity 10.3.9a.2 Integer (-6, -3, 3, 6) S-CCPCH configuration used in neighbouring cell. Refers to a configuration in the common RB info of the current cell Difference (Pn Of) between the S-CCPCH power offset (Pn) of the neighboring cell S-CCPCH and the S-CCPCH power offset (Of) of the serving cell that is going to be combined to this neighbour cell S-CCPCH, in dB. Default value is 0. Note 3 and 4. L2- combining applies if the IE is absent
REL-6
MP
REL-6
>Secondary CCPCH Power Offset Difference
MD
REL-6
>L1 combining >>CHOICE mode >>>FDD >>>>MBMS Soft Combining Timing Offset
OP MP MP MBMS Soft Combinin g Timing Offset 10.3.9a.1 0a Integer (0..3)
REL-6 REL-6 REL-6 REL-6
Timing offset applied in the CFN calculation in subclause 8.5.15.5
>>>>MBMS transmission time difference
MP
>>>>MBMS L1 combining schedule
OP
MBMS L1 combining schedule 10.3.9a.7
>>>TDD >CHOICE L23 configuration >>SameAs Current cell
Indicates the time difference between the TTIs on the current and the neighbouring cells SCCPCH that can be L1combined If included partial layer 1 combining applies, in which case this IE indicates when L1combining applies. If the IE is absent, L1 combining applies continuously (no data)
REL-6
REL-6
MP Apart from the physical channel configuration and the MSCH configuration information, the same configuration as for the indicated S-CCPCH used in the current cell applies. The MSCH is mapped on the same transport channel as in the current cell. Reference to the S-CCPCH in the current cell which uses exaclty
REL-6 REL-6 REL-6
>>>Current cell's SCCPCH
MP
MBMS Current
REL-6
3GPP
428 Type and reference cell SCCPCH identity 10.3.9a.5 MSCH configurat ion informatio n 10.3.9a.1 6 MBMS Common CCTrCh identity 10.3.9a.1 1 to <maxFA CHPCH > MBMS Common TrCh identity 10.3.9a.4 BOOLEA N
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description the same configuration (excluding MSCH configuration). Version
>>>MSCH configuration information
OP
REL-6
>>Different >>>TrCh information for common for all TrCh
MD
Refers to a (TFCS) configuration in the common RB info The default value of the TFCS is specified in subclause 14.10.1 List of FACH transport channels carrying one or more MTCH and optionally one MSCH Refers to a (TFS) configuration in the common RB info
REL-6 REL-6
>>>TrCH information list
MP
REL-6
>>>>TrCh information
MP
REL-6
>>>>TrCh combining status
MP
>>>>RB information list
OP
1 to <maxRB perTrCh > MBMS pt-m RB informatio n 10.3.9a.7 a MSCH configurat ion informatio n 10.3.9a.1 6
Value TRUE means that TrCh combining is used for this transport channel (TDD only). Note 2. The IE shall be ignored in FDD mode. The IE is only present for the radio bearers for which selection (FDD) or transport channel (TDD) combining applies.
REL-6
REL-6
>>>>>RB information
MP
REL-6
>>>>MSCH configuration information
OP
Included if the TrCH carries MSCH
REL-6
NOTE 1: The signalling supports the option that UTRAN maps one service to L1 combining slots for some neighbours and to the L2 combining slots for other neighbours ie. the use of different combining schemes for different neighbours NOTE 2: Transport combining can only be indicated when the complete L2 configuration is provided for the neighbouring cell (i.e. using L2 configuration choice different). Fortunately, a scenario in which the neighbouring cell configuration is different from the current cell is regarded as the typical scenario for using transport combining. NOTE 3: For FDD, an S-CCPCH power offset is defined as the offset between the transmitted power of the data part of one S-CCPCH and the transmitted power of the P-CPICH of a given cell (Ps-ccpch Pp-cpich). For TDD, an S-CCPCH power offset is defined as the offset between one S-CCPCH and the P-CCPCH of a given cell (Ps-ccpch Pp-ccpch).
3GPP
Release 6
429
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE 4: The Secondary CCPCH Power Offset Difference IE gives the UE an indication of the S-CCPCH power on the neighbouring cells that may be used to complete the neighbouring cell ranking based on P-CPICH power for FDD or P-CCPCH for TDD.
10.2.16L MBMS SCHEDULING INFORMATION

This message is transmitted periodically by UTRAN to inform UEs when the MBMS services, provided on the same SCCPCH as the message is sent, are scheduled to be transmitted. The UE may use the scheduling information to discontinue receiving the concerned S-CCPCH. The message is transmitted in accordance with the MSCH configuration applicable for the corresponding S-CCPCH. RLC-SAP: UM Logical channel: MSCH Direction: UTRAN UE
Information Element/Group name Message type Service scheduling info list Need MP MP 1 to < maxMB MSserv Sched> MBMS Transmis sion identity 10.3.9a.1 2 1 to < maxMB MSTran smis> Integer (0..1020) by step of 4 One or more sets of scheduling information comprising of the beginning and duration of an MBMS service transmission for one scheduling period Indicates the start of the transmission relative to the start of the TTI in which the MBMS SCHEDULING INFORMATION message was received. In number of radio frames (i.e. the value 0 would correspond to the start of the MBMS transmission being in the same TTI as the MBMS Scheduling Information message). See note 1. In number of radio frames Multi Type and reference Message Type Semantics description Version REL-6 REL-6
MP
REL-6
>MBMS Service transmissions info list
OP
REL-6
>>Start
MP
REL-6
>>Duration
MP
>Next scheduling period
MP
Integer (4..1024) by step of 4 Integer (0..31)
REL-6
Number of scheduling periods (see 10.3.9a.16), after the current scheduling period, in which no data will be transmitted for the concerned service. If the Next scheduling period is set to 0, data may be transmitted for the concerned service in the scheduling period immediately following the current scheduling period
REL-6
NOTE:
If UTRAN sets the value of the IE "Start" to a value less than or equal to 16 then the UE may not successfully receive the start of the MTCH transmission.
3GPP
Release 6
430
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.16m MBMS UNMODIFIED SERVICES INFORMATION

This message is transmitted periodically by UTRAN to inform UEs about the MBMS services, available in the current cell and possibly in neighbouring cells, that have not changed if the IE "MBMS all unmodified p-t-m services" is not included in the MBMS MODIFIED SERVICES INFORMATION message in this modification period. The message is repeated every repetition period while its content does not change within a modification period. RLC-SAP: UM Logical channel: MCCH Direction: UTRAN UE
Information Element/Group name Message type Unmodified services list Need MP OP 1 to <maxMB MSserv Unmodif > Multi Type and reference Message Type Semantics description Version REL-6 If the IE MBMS all unmodified p-t-m services is included in the MBMS MODIFIED SERVICES INFORMATION message in this modification period, the services with the IE MBMS required UE action set to Acquire PTM RB info in the message MBMS UNMODIFIED SERVICES INFORMATION should be considered as modified. MBMS Transmis sion identity 10.3.9a.1 2 Enumerat ed (None, Acquire PTM RB info, Request PTP RB ) Integer (1.. <maxMB MSFreq>) REL-6
MP
REL-6
>MBMS required UE action
MP
Indication of the UE action required to receive the service.
REL-6
>MBMS preferred frequency
OP
Information about the frequency that UEs shall consider as the preferred frequency layer for cell re-selection during a session for an activated MBMS service, as specified in [25.304]. Index pointing to an entry in the list included in MBMS GENERAL INFORMATION
REL-6
10.2.17 MEASUREMENT CONTROL

This message is sent by UTRAN to setup, modify or release a measurement in the UE. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements Need MP Multi Type and reference Message Type Semantics description
3GPP
Release 6 Information Element/Group name RRC transaction identifier Need MP
431 Multi Type and reference RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16
CH
Measurement Information elements Measurement Identity
MP
Measurement Command
MP
OP
Additional measurements list
OP
Measuremen t Identity 10.3.7.48 Measuremen t Command 10.3.7.46 Measuremen t Reporting Mode 10.3.7.49 Additional measuremen ts list 10.3.7.1
CHOICE Measurement type >Intra-frequency measurement
CVcommand Intrafrequency measuremen t 10.3.7.36 Interfrequency measuremen t 10.3.7.16 Inter-RAT measuremen t 10.3.7.27 UE positioning measuremen t 10.3.7.100 Traffic Volume measuremen t 10.3.7.68 Quality measuremen t 10.3.7.56 UE internal measuremen t 10.3.7.77
>Inter-frequency measurement
>Inter-RAT measurement
>UE positioning measurement
>Traffic Volume measurement
>Quality measurement
>UE internal measurement
Physical channel information elements DPCH compressed mode status info
OP
DPCH compressed mode status info 10.3.6.34
Condition Command
Explanation The IE is mandatory present if the IE "Measurement command" is set to "Setup", optional if the IE "Measurement command" is set to "modify", otherwise the IE is not needed.
3GPP
Release 6
432
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.18 MEASUREMENT CONTROL FAILURE

This message is sent by UE, if it cannot initiate a measurement as instructed by UTRAN. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14 Semantics description
MP
CH
Failure cause
MP
3GPP
Release 6
433
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.19 MEASUREMENT REPORT

This message is used by UE to transfer measurement results to the UTRAN. RLC-SAP: AM or UM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements Integrity check info Need MP Multi Type and reference Message Type Semantics description Version
CH
Measurement Information Elements Measurement identity
MP
Measured Results
OP
Measured Results on RACH
OP
Measure ment identity 10.3.7.48 Measured Results 10.3.7.44 Measured Results on RACH 10.3.7.45 1 to <maxAd ditional Meas> Measured Results 10.3.7.44 Event results 10.3.7.7 Integer (0..3)
Additional Measured results
OP
>Measured Results
MP
Event results
OP
Inter-RAT cell info indication
CVIRAT
REL-5
Condition IRAT
Explanation The IE is optionally present if at least one of the IE "Inter-RAT measured results list" and the IE "InterRAT measurement event results" is included in the message. Otherwise, the IE is not needed.
10.2.20 PAGING TYPE 1

This message is used to send information on the paging channel. One or several UEs, in idle or connected mode, can be paged in one message, which also can contain other information. RLC-SAP: TM Logical channel: PCCH Direction: UTRAN UE
Information Element/Group name Need Multi Type and reference Semantics description
3GPP
Release 6 Message Type UE Information elements Paging record list MP
434 Message Type 1 to <maxPage 1> Paging record 10.3.3.23 BCCH modification info 10.3.8.1
3GPP TS 25.331 V6.23.0 (2009-09)
OP
>Paging record
MP
Other information elements BCCH modification info
OP
If the encoded message does not fill a transport block, the RRC layer shall add padding according to subclause 12.1.
10.2.21 PAGING TYPE 2

This message is used to page a UE in connected mode, when using the DCCH for CN originated paging. RLC-SAP: AM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Paging cause 10.3.3.22 CN domain identity 10.3.1.1 Paging Record Type Identifier 10.3.1.10 Semantics description
MP
CH
Paging cause
MP
CN Information elements CN domain identity
MP
Paging Record Type Identifier
MP
10.2.22 PHYSICAL CHANNEL RECONFIGURATION

This message is used by UTRAN to assign, replace or release a set of physical channels used by a UE. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type Need MP Multi Type and reference Message Type Semantics description Version
3GPP
Release 6 Information Element/Group name UE Information Elements RRC transaction identifier Need
435 Multi Type and reference RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5
MP
CH
OP
Ciphering mode info
OP
Activation time Delay restriction flag
MD OP
Activation time 10.3.3.1 Enumerated (TRUE)
The UTRAN should not include this IE unless it is performing an SRNS relocation The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in ciphering algorithm Default value is "now" This IE is always set to TRUE and included if the activation time is restricted according to subclause 8.6.3.1
REL-6
New U-RNTI New C-RNTI New DSCH-RNTI
OP OP OP
U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 DSCH-RNTI 10.3.3.9a
Should not be set in FDD. If received the UE should ignore it REL-5 REL-6 REL-6
OP OP OP MP
OP
H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI 10.3.3.10a RRC State Indicator 10.3.3.35a UTRAN DRX cycle length coefficient 10.3.3.49 CN Information info 10.3.1.3
OP
UTRAN mobility information elements URA identity RB information elements Downlink counter synchronisation info >RB with PDCP information list
OP
URA identity 10.3.2.6
OP OP 1 to <maxRBall RABs>
3GPP
Release 6 Information Element/Group name >>RB with PDCP information Need MP
436 Multi Type and reference RB with PDCP information 10.3.4.22
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description This IE is needed for each RB having PDCP in the case of lossless SRNS relocation This IE is needed for each RB having PDCP and performing PDCP context relocation Version
OP OP
PDCP context relocation info 10.3.4.1a Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS_PDSCH Information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <maxRL> Downlink information for each radio link 10.3.6.27 Enumerated (TRUE)
REL-5 REL-5
OP
MD
Default value is the existing value of the maximum allowed UL TX power
Uplink DPCH info
OP
OP
REL-6
OP
REL-5
OP
Downlink information per radio link list >Downlink information for each radio link
OP
Send downlink information for each radio link
MP
OP
REL-6
10.2.23 PHYSICAL CHANNEL RECONFIGURATION COMPLETE

This message is sent from the UE when a physical channel reconfiguration has been done. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC Semantics description Version
MP
3GPP
437 Multi Type and reference transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17
CH
Uplink integrity protection activation info
OP
CHOICE mode >FDD >TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>>Uplink Timing Advance
MP (no data) MP MP OP REL-4 REL-4 Uplink Timing Advance 10.3.6.95 (no data) OP Activation time 10.3.3.1 Used for radio bearers mapped on RLC-TM. REL-4
>>>1.28 Mcps TDD RB Information elements COUNT-C activation time
Uplink counter synchronisation info >RB with PDCP information list
OP OP 1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains.
MP
>START list
MP
>>CN domain identity
MP
>>START
MP
START value to be used in this CN domain.
10.2.24 PHYSICAL CHANNEL RECONFIGURATION FAILURE

This message is sent by UE if the configuration given by UTRAN is unacceptable or if the UE failed to assign, replace or release a set of physical channel(s). RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
Release 6 Information Element/Group name Message type UE information elements RRC transaction identifier Need MP
438 Multi Type and reference Message type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14
OP
CH
Failure cause
MP
10.2.25 PHYSICAL SHARED CHANNEL ALLOCATION

NOTE: Only for TDD. This message is used by UTRAN to assign physical resources to USCH/DSCH transport channels in TDD, for temporary usage by the UE. RLC-SAP: UM on SHCCH, UM on DCCH Logical channel: SHCCH or DCCH Direction: UTRAN UE
Information Element/Group name Message Type DSCH-RNTI RRC transaction identifier Need MP OP MP Multi Type and reference Message type DSCH-RNTI 10.3.3.9a RRC transaction identifier 10.3.3.36 Uplink Timing Advance Control 10.3.6.96 PUSCH Capacity Allocation info 10.3.6.64 PDSCH Capacity Allocation info 10.3.6.42 Enumerated( No Confirm, Confirm PDSCH, Confirm PUSCH) Integer (0 .. 255) Semantics description
Uplink timing advance Control
MD
Default value is the existing value for uplink timing advance
PUSCH capacity allocation info
OP
PDSCH capacity allocation info
OP
Confirm request
MD
Default value is No Confirm
Traffic volume report request
OP
Indicates the number of frames between start of the allocation period and sending measurement report. The
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description value should be less than the value for Allocation Duration.
ISCP Timeslot list >Timeslot number
OP MP
1 to maxTS Timeslot number 10.3.6.84 Boolean Timeslot numbers, for which the UE shall report the timeslot ISCP in PUSCH CAPACITY REQUEST message. TRUE indicates that a Primary CCPCH RSCP measurement shall be reported by the UE in PUSCH CAPACITY REQUEST message.
Request P-CCPCH RSCP
MP
10.2.26 PUSCH CAPACITY REQUEST

NOTE: Only for TDD. This message is used by the UE for request of PUSCH resources to the UTRAN. RLC-SAP: TM Logical channel: SHCCH Direction: UE UTRAN
Information Element/Group name Message Type DSCH-RNTI RRC transaction identifier Need MP OP CV-ProtErr Multi Type and reference Message Type DSCH-RNTI 10.3.3.9a RRC transaction identifier 10.3.3.36 Traffic Volume, measured results list 10.3.7.67 Semantics description
Traffic Volume
OP
Timeslot list >Timeslot number
OP MP
1 to maxTS Timeslot number 10.3.6.84 Timeslot ISCP info 10.3.7.65 Primary CCPCH RSCP info 10.3.7.54 Integer(1..hi PDSCHident ities) Integer(1..hi PUSCHident ities) Protocol error indicator 10.3.3.27
>Timeslot ISCP
MP
Primary CCPCH RSCP
OP
CHOICE Allocation confirmation >PDSCH Confirmation
OP
>PUSCH Confirmation
Protocol error indicator
MD
Default value is FALSE
3GPP
Release 6 Information Element/Group name Protocol error information Need CV-ProtErr
440 Multi Type and reference Protocol error information 10.3.8.12
Condition ProtErr
Explanation This IE is mandatory present if the IE "Protocol error indicator" has the value "TRUE". Otherwise it is not needed.
10.2.27 RADIO BEARER RECONFIGURATION

This message is sent from UTRAN to reconfigure parameters related to a change of QoS or to release and setup a radio bearer used for ptp transmission of MBMS services of the broadcast type. This procedure can also change the multiplexing of MAC, reconfigure transport channels and physical channels. This message is also used to perform a handover from GERAN Iu mode to UTRAN. RLC-SAP: AM or UM or sent through GERAN Iu mode Logical channel: DCCH or sent through GERAN Iu mode Direction: UTRAN UE
Information Element/Group name Message Type UE Information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Semantics description Version
MP
CH
OP
Ciphering mode info
OP
Ciphering mode info 10.3.3.5
MD OP
The UTRAN should not include this IE unless it is performing an SRNS relocation or a handover from GERAN Iu mode The UTRAN should not include this IE unless it is performing either an SRNS relocation or a handover from GERAN Iu mode and a change in ciphering algorithm Default value is "now" This IE is always set to TRUE and included if the activation time is restricted according to
REL-6
3GPP
Release 6 Information Element/Group name New U-RNTI New C-RNTI New DSCH-RNTI Need
441 Multi Type and reference U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 DSCH-RNTI 10.3.3.9a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description subclause 8.6.3.1 Version
OP OP OP
Should not be set in FDD. If received The UE should ignore it REL-5 REL-6 REL-6
OP OP OP MP
OP
CN information elements CN Information info
OP
UTRAN mobility information elements URA identity CHOICE specification mode >Complete specification RB information elements >>RAB information to reconfigure list >>>RAB information to reconfigure
OP MP
URA identity 10.3.2.6 REL-5
OP
1 to < maxRABse tup > RAB information to reconfigure 10.3.4.11 1 to < maxMBMS servSelect > RAB information for MBMS ptp bearer 10.3.4.11a 1to <maxRB> Although this IE is not always required, need is MP to align with ASN.1 REL-4 RB information to reconfigure 10.3.4.18 1 to <maxRB> RB information REL-6
MP
>>RAB information for MBMS ptp bearer list
OP
>>>RAB information for MBMS ptp bearer
MP
REL-6
>>RB information to reconfigure list
MP
>>>RB information to reconfigure
OP MP
>>RB information to be affected list >>>RB information to be affected
OP MP
3GPP
442 Multi Type and reference to be affected 10.3.4.17
>>RB with PDCP context relocation info list
OP
1 to <maxRBall RABs>
This IE is needed for each RB having PDCP and performing PDCP context relocation PDCP context relocation info 10.3.4.1a PDCP ROHC target mode 10.3.4.2a
REL-5
>>>PDCP context relocation info
MP
REL-5
>>PDCP ROHC target mode
OP
REL-5
TrCH Information Elements Uplink transport channels >>UL Transport channel information common for all transport channels
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <maxTrCH > Deleted UL TrCH information 10.3.5.5 1 to <maxTrCH > Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH > Deleted DL TrCH information 10.3.5.4 1 to <maxTrCH > Added or Reconfigure d DL TrCH information 10.3.5.1
>>Deleted TrCH information list
OP
>>>Deleted UL TrCH information
MP
>>Added or Reconfigured TrCH information list >>>Added or Reconfigured UL TrCH information
OP
MP
OP
OP
>>>Deleted DL TrCH information
MP
>>Added or Reconfigured TrCH information list >>>Added or Reconfigured DL TrCH information
OP
MP
3GPP
Release 6 Information Element/Group name >Preconfiguration >>CHOICE Preconfiguration mode Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description This value only applies in case the message is sent through GERAN Iu mode Predefined configuration identity 10.3.4.5 Enumerated (FDD, TDD) Indicates whether the FDD or TDD version of the default configuration shall be used Version REL-5
MP
>>>Predefined configuration identity
MP
MP
MP
Default configuration identity 10.3.4.0 Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH Information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <maxRL> Although this IE is not always required, need is MP to align with ASN.1 REL-4 Downlink information for each radio link 10.3.6.27 Enumerated (TRUE) Default value is the existing maximum UL TX power
OP
MD
Uplink DPCH info
OP
OP
REL-6
OP
REL-5
OP
MP
OP MP
OP
REL-6
10.2.28 RADIO BEARER RECONFIGURATION COMPLETE

This message is sent from the UE when a RB and signalling link reconfiguration has been done.
3GPP
Release 6
444
3GPP TS 25.331 V6.23.0 (2009-09)
RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN

Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17 (no data) MP OP Uplink Timing Advance 10.3.6.95 (no data) OP Activation time 10.3.3.1 Used for radio bearers mapped on RLC-TM. REL-4 REL-4 REL-4 Semantics description Version
MP
CH
OP
MP
OP OP 1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains.
MP
>START list
MP
MP
>>START
MP
10.2.29 RADIO BEARER RECONFIGURATION FAILURE

This message is sent by UE if the configuration given by UTRAN is unacceptable or if the UE failed to establish the physical channel(s). RLC-SAP: AM Logical channel: DCCH
3GPP
Release 6
445
3GPP TS 25.331 V6.23.0 (2009-09)
Direction: UEUTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14 1 to <maxRB> RB identity, 10.3.4.16 Semantics description
MP
CH
Failure cause
MP
RB information elements Radio bearers for which reconfiguration would have succeeded List >Radio bearer for which reconfiguration would have succeeded
OP
MP
10.2.30 RADIO BEARER RELEASE

This message is used by UTRAN to release a radio bearer. It can also include modifications to the configurations of transport channels and/or physical channels. It can simultaneously indicate release of a signalling connection when UE is connected to more than one CN domain. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type UE Information Elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5 Semantics description Version
MP
CH
OP
Ciphering mode info
OP
Activation time New U-RNTI New C-RNTI
MD OP OP
Activation time 10.3.3.1 U-RNTI 10.3.3.47 C-RNTI
The UTRAN should not include this IE unless it is performing an SRNS relocation. The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in ciphering algorithm. Default value is "now"
3GPP
Release 6 Information Element/Group name New DSCH-RNTI Need
446 Multi Type and reference 10.3.3.8 DSCH-RNTI 10.3.3.9a H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI 10.3.3.10a RRC State Indicator 10.3.3.35a UTRAN DRX cycle length coefficient 10.3.3.49 CN Information info 10.3.1.3 CN domain identity 10.3.1.1
OP
OP OP OP MP
OP
OP
Signalling Connection release indication UTRAN mobility information elements URA identity RB Information Elements RAB information to reconfigure list >RAB information to reconfigure
OP
OP
URA identity 10.3.2.6 1 to < maxRABse tup > RAB information to reconfigure 10.3.4.11 1 to <maxRB> RB information to release 10.3.4.19 1to <maxRB> RB information to reconfigure 10.3.4.18 1 to <maxRB> RB information to be affected 10.3.4.17 REL-6 REL-6
OP
MP
RB information to release list >RB information to release
MP MP
RB information to reconfigure list >RB information to reconfigure
OP MP
RB information to be affected list >RB information to be affected
OP MP
Downlink counter synchronisation info >RB with PDCP information list
OP OP 1 to <maxRBall RABs>
3GPP
Release 6 Information Element/Group name >>RB with PDCP information Need MP
447 Multi Type and reference RB with PDCP information 10.3.4.22
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description This IE is needed for each RB having PDCP in the case of lossless SRNS relocation REL-5 REL-5 Version
>RB with PDCP context relocation info list >>PDCP context relocation info
OP OP
1 to <maxRBall RABs> PDCP context relocation info 10.3.4.1a This IE is needed for each RB having PDCP and performing PDCP context relocation
MP
REL-5
TrCH Information Elements Uplink transport channels UL Transport channel information common for all transport channels
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <maxTrCH > Deleted UL TrCH information 10.3.5.5 1 to <maxTrCH > Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH > Deleted DL TrCH information 10.3.5.4 1 to <maxTrCH > Added or Reconfigure d DL TrCH information 10.3.5.1 Frequency info 10.3.6.36
OP
>Deleted UL TrCH information
MP
OP
MP
OP
OP
>Deleted DL TrCH information
MP
OP
MP
OP
Uplink radio resources
3GPP
Release 6 Information Element/Group name Maximum allowed UL TX power Need MD
448 Multi Type and reference Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH Information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <maxRL> Downlink information for each radio link 10.3.6.27 Enumerated (TRUE) 1 to <maxRB> RB information to release 10.3.4.19
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Default value is the existing maximum UL TX power Version
Uplink DPCH info
OP
OP
REL-6
OP
REL-5
OP
OP MP
Send downlink information for each radio link to be set-up
MBMS PL Service Restriction Information MBMS RB list released to change transfer mode >RB information to release
OP OP MP
REL-6 REL-6 REL-6
10.2.31 RADIO BEARER RELEASE COMPLETE

This message is sent from the UE when radio bearer release has been completed. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17 Semantics description Version
MP
CH
OP
CHOICE mode
MP
3GPP
Release 6 Information Element/Group name >FDD >TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>>Uplink Timing Advance Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description (no data) Version
MP OP Uplink Timing Advance 10.3.6.95 This information element shall be present in case of handover procedure if timing advance is enabled. Calculated timing advance value for the new cell after handover in a synchronous TDD network (no data) Used for radio bearers mapped on RLC-TM.
REL-4 REL-4
REL-4
OP
Activation time 10.3.3.1
OP OP 1 to <maxRBall RABs> This IE is needed for each RB having PDCP in the case of lossless SRNS relocation RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains.
MP
>START list
MP
MP
>>START
MP
10.2.32 RADIO BEARER RELEASE FAILURE

This message is sent by UE if the configuration given by UTRAN is unacceptable or if radio bearer cannot be released. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
450 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14 1 to <maxRB> RB identity, 10.3.4.16
MP
CH
Failure cause
MP
RB information elements Radio bearers for which reconfiguration would have succeeded >Radio bearer for which reconfiguration would have been succeeded
OP
MP
10.2.33 RADIO BEARER SETUP

This message is sent by UTRAN to the UE to establish new radio bearer(s). It can also include modifications to the configurations of transport channels and/or physical channels. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type UE Information Elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5 Semantics description Version
MP
CH
OP
Ciphering mode info
OP
Activation time New U-RNTI
MD OP
Activation time 10.3.3.1 U-RNTI 10.3.3.47
The UTRAN should not include this IE unless it is performing an SRNS relocation The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in ciphering algorithm Default value is "now"
3GPP
Release 6 Information Element/Group name New C-RNTI New DSCH-RNTI Need OP OP
451 Multi Type and reference C-RNTI 10.3.3.8 DSCH-RNTI 10.3.3.9a
OP OP OP MP
OP
OP
UTRAN mobility information elements URA identity RB Information Elements CHOICE specification mode >Complete specification
OP
URA identity 10.3.2.6 REL-6 REL-6
MP In this version of the specification, only this value is specified. For each signalling radio bearer established Signalling RB information to setup 10.3.4.24 1 to <maxRABs etup> RAB information for setup 10.3.4.10 1 to < maxRABse tup > RAB information to reconfigure 10.3.4.11 1to <maxRB> RB information to reconfigure 10.3.4.18 1 to <maxRB> For each RAB established
>>Signalling RB information to setup list >>>Signalling RB information to setup
OP
1 to <maxSRBs etup>
MP
>>RAB information to setup list
OP
>>>RAB information for setup
MP
>>RAB information to reconfigure list >>>RAB information to reconfigure
OP
REL-6
MP
REL-6
>>RB information to reconfigure list >>>RB information to reconfigure
OP MP
REL-6 REL-6
>>RB information to be affected list
OP
3GPP
Release 6 Information Element/Group name >>>RB information to be affected Need MP
452 Multi Type and reference RB information to be affected 10.3.4.17
>>Downlink counter synchronisation info >>>RB with PDCP information list >>>>RB with PDCP information
MP
>>>>PDCP context relocation info
OP OP
>>PDCP ROHC target mode
OP
PDCP context relocation info 10.3.4.1a PDCP ROHC target mode 10.3.4.2a
REL-5
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <maxTrCH > Deleted UL TrCH information 10.3.5.5 1 to <maxTrCH > Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels10. 3.5.6 1 to <maxTrCH > Deleted DL TrCH information 10.3.5.4 1 to
OP
>>>Deleted UL TrCH information
MP
>>Added or Reconfigured TrCH information list >>>Added or Reconfigured UL TrCH information
OP
MP
OP
OP
>>>Deleted DL TrCH information
MP
>>Added or Reconfigured TrCH
OP
3GPP
Release 6 Information Element/Group name information list >>>Added or Reconfigured DL TrCH information Need
453 Multi <maxTrCH > MP Added or Reconfigure d DL TrCH information 10.3.5.1 Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH Information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <maxRL> Downlink information for each radio link 10.3.6.27 Enumerated (TRUE) Type and reference
OP
MD
Default value is the existing maximum UL TX power
Uplink DPCH info
OP
OP
REL-6
OP
REL-5
OP
OP
MP
OP
REL-6
10.2.34 RADIO BEARER SETUP COMPLETE

This message is sent by the UE to confirm the establishment of the radio bearer. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Semantics description Version
MP
CH
3GPP
Release 6 Information Element/Group name Uplink integrity protection activation info Need OP
454 Multi Type and reference Integrity protection activation info 10.3.3.17
OP (no data) MP OP Uplink Timing Advance 10.3.6.95 This information element shall be present in case of handover procedure if timing advance is enabled. Calculated timing advance value for the new cell after handover in a synchronous TDD network (No data) This information element is not needed for transparent mode RBs if prior to this procedure there exists one RB using RLC-TM. Used for radio bearers mapped on RLC-TM. REL-4 REL-4
>>>1.28 Mcps TDD START
REL-4
OP
START 10.3.3.38
RB Information elements COUNT-C activation time
OP
Activation time 10.3.3.1
OP OP 1 to <maxRBall RABs> This IE is needed for each RB having PDCP in the case of lossless SRNS relocation RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains.
MP
>START list
MP
MP
>>START
MP
3GPP
Release 6
455
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.35 RADIO BEARER SETUP FAILURE

This message is sent by UE, if it does not support the configuration given by UTRAN. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Failure cause and error information 10.3.3.14 1 to <maxRB> RB identity, 10.3.4.16 Semantics description
MP
CH
Failure cause
MP
RB information elements Radio bearers for which reconfiguration would have succeeded >Radio bearer for which reconfiguration would have succeeded
OP
MP
10.2.36 RRC CONNECTION REJECT

The network transmits this message when the requested RRC connection cannot be accepted. RLC-SAP: UM Logical channel: CCCH Direction: UTRAN UE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Initial UE identity 10.3.3.15 Rejection cause 10.3.3.31 Wait time 10.3.3.50 Redirection info 10.3.3.29 Semantics description Version
MP
Initial UE identity
MP
Rejection cause
MP
Wait time Redirection info
MP OP
3GPP
Release 6 Counting completion OP
456 Enumerated (TRUE)
3GPP TS 25.331 V6.23.0 (2009-09) This field may be present if the Rejection Cause is set to unspecified otherwise it shall be ignored. REL-6
10.2.37 RRC CONNECTION RELEASE

This message is sent by UTRAN to release the RRC connection. The message also releases the signalling connection and all radio bearers between the UE and UTRAN. RLC-SAP: UM Logical channel: CCCH or DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements CHOICE identity type >U-RNTI > Group identity 1 to <maxUR NTIgrou p> MP Group release informatio n 10.3.3.14 o RRC transactio n identifier 10.3.3.36 Integrity check info 10.3.3.16 Integer(1.. 8) Release cause 10.3.3.32 Need MP Multi Type and reference Message Type Semantics description Version
CVCCCH U-RNTI 10.3.3.47
REL-5
REL-5
>>Group release information
REL-5
MP
CVDCCH CHCell_DC H MP
N308
Release cause
Other information elements Rplmn information
OP
Rplmn informatio n 10.3.8.15
Redirection info
OP
Redirecti on info 10.3.3.2 9
REL-6
3GPP
Release 6 Condition CCCH DCCH Cell_DCH
457
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation This IE is mandatory present when CCCH is used and not needed otherwise. This IE is mandatory present when DCCH is used and not needed otherwise. This IE is mandatory present when UE is in CELL_DCH state and not needed otherwise.
10.2.38 RRC CONNECTION RELEASE COMPLETE

This message is sent by UE to confirm that the RRC connection has been released. RLC-SAP: AM or UM Logical channel: DCCH Direction: UE UTRAN
MP
CH
Error indication
OP
10.2.39 RRC CONNECTION REQUEST

RRC Connection Request is the first message transmitted by the UE when setting up an RRC Connection to the network. RLC-SAP: TM Logical channel: CCCH Direction: UE UTRAN
3GPP
Release 6 Information Element/Group name Message Type Radio Bearer IEs Predefined configuration status information Need MP
458 Multi Type and reference Message Type Boolean
MP
True indicates the UE has all preconfigurations stored with the same value tag as broadcast in the cell in which the RRC connection establishment is initiated
REL-5
UE information elements Initial UE identity
MP
Establishment cause
MP
MD
>UE Specific Behaviour Information 1 idle
OP
Domain indicator
MP
Call type
CV-CSdomain OP
UE capability indication
Initial UE identity 10.3.3.15 Establishme nt cause 10.3.3.11 Protocol error indicator 10.3.3.27 UE Specific Behaviour Information 1 idle 10.3.3.51 CN domain identity 10.3.1.1 Enumerated (speech, video, other) Enumerated (HS-DSCH, HSDSCH+EDCH) MBMS Selected Services Short 10.3.9a.7d Enumerated (True)
This IE shall not be included in this version of the protocol REL-6
One spare value is needed Absence of this IE implies that neither HS-DSCH nor E-DCH are supported by the UE
REL-6
REL-6
MBMS Selected Services
OP
REL-6
Support for F-DPCH
OP
The IE shall be set to TRUE when F-DPCH is fully supported by the UE. Absence of this information element indicates that F-DPCH is not fully supported
REL-6
3GPP
Release 6 Measurement information elements Measured results on RACH
459
3GPP TS 25.331 V6.23.0 (2009-09)
OP
Access stratum release indicator
MP
Measured results on RACH 10.3.7.45 Enumerated( REL-4,
REL-5
Absence of the IE implies R99. The IE also indicates the release of the RRC transfer syntax supported by the UE 13 spare values are needed
REL-4
REL-5
REL-6)
REL-6
Condition CS-domain
Explanation This IE is mandatory present if the IE "Domain indicator" has the value "CS domain". Otherwise it is not needed.
If the encoded message does not fill a transport block, the RRC layer shall insert padding according to subclause 12.1.
10.2.40 RRC CONNECTION SETUP

This message is used by the network to accept the establishment of an RRC connection for a UE, including assignment of signalling link information, transport channel information and optionally physical channel information. RLC-SAP: UM Logical channel: CCCH Direction: UTRAN UE
Information Element/Group name Message Type UE Information Elements Initial UE identity Need MP Multi Type and reference Message Type Initial UE identity 10.3.3.15 RRC transaction identifier 10.3.3.36 Activation time 10.3.3.1 U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 H-RNTI 10.3.3.14a E-RNTI 10.3.3.10a E-RNTI Semantics description Version
MP
MP
Activation time New U-RNTI New C-RNTI New H-RNTI New Primary E-RNTI New Secondary E-RNTI
MD MP OP OP OP OP
REL-6 REL-6 REL-6
3GPP
Release 6 Information Element/Group name RRC State Indicator Need
460 Multi Type and reference 10.3.3.10a RRC State Indicator 10.3.3.35a UTRAN DRX cycle length coefficient 10.3.3.49 Capability update requirement 10.3.3.2
MP
MP
Capability update requirement
MD
Default value is defined in subclause 10.3.3.2 REL-5
CHOICE specification mode >Complete specification RB Information Elements >>Signalling RB information to setup list >>>Signalling RB information to setup
MP
MP MP
3 to 4 Signalling RB information to setup 10.3.4.24
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <maxTrCH > Although this IE is not required when the IE "RRC state indicator" is set to "CELL_FACH", need is MP to align with ASN.1 REL-4 Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH > Although this IE is not required when the IE "RRC state indicator" is set to "CELL_FACH", need is MP to align with ASN.1 REL-4 Added or Reconfigure d DL TrCH information 10.3.5.1
>>Added or Reconfigured TrCH information list
MP
>>>Added or Reconfigured UL TrCH information
OP MP
OP
>>Added or Reconfigured TrCH information list
MP
>>>Added or Reconfigured DL TrCH information
OP MP
3GPP
Release 6 Information Element/Group name >Preconfiguration >>CHOICE Preconfiguration mode >>>Predefined configuration identity Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version REL-5 REL-5 Predefined configuration identity 10.3.4.5 Enumerated (FDD, TDD) Indicates whether the FDD or TDD version of the default configuration shall be used REL-5
MP MP
MP
REL-5 REL-5
MP
Default configuration identity 10.3.4.0 OP Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH information 10.3.6.23a Downlink information common for all radio links 10.3.6.24 1 to <MaxRL> Send downlink information for each radio link to be set-up Downlink information for each radio link 10.3.6.27 Default value is the existing maximum UL TX power
REL-5
MD
Uplink DPCH info
OP
OP
REL-6
OP
REL-6
OP
OP
MP
3GPP
Release 6
462
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.41 RRC CONNECTION SETUP COMPLETE

This message confirms the establishment of the RRC Connection by the UE. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type UE Information Elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 UE radio access capability 10.3.3.42 UE radio access capability extension 10.3.3.42a 1 to <maxInter SysMessa ges> Inter-RAT UE radio access capability 10.3.8.7 START [40] values for all CN domains. Semantics description
MP
START list
MP
>CN domain identity
MP
>START UE radio access capability
MP OP
UE radio access capability extension
OP
Other information elements UE system specific capability
OP
>Inter-RAT UE radio access capability
MP
10.2.41a RRC FAILURE INFO

This message is sent by the UE via another radio access technology to provide information about the cause for failure to perform the requested operation. RLC-SAP: N/A (Sent through a different RAT) Logical channel: N/A (Sent through a different RAT) Direction: UE UTRAN
3GPP
Release 6 Information Element/Group Name Other Information elements Failure cause Need
463 Multi Type and reference Failure cause 10.3.3.13 Protocol error information 10.3.8.12
MP
Protocol error information
CV-ProtErr
Condition ProtErr
Explanation Presence is mandatory if the IE "Failure cause" has the value "Protocol error"; otherwise the element is not needed in the message.
10.2.42 RRC STATUS

This message is sent to indicate a protocol error. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements Integrity check info Need MP Multi Type and reference Message Type Integrity check info 10.3.3.16 Semantics description
CH
Identification of received message >Received message type >RRC transaction identifier
CVMessage identified MP MP
Message Type RRC transaction identifier 10.3.3.36 Protocol error information 10.3.8.12
Other information elements Protocol error information
MP
Condition Message identified
Explanation This IE is mandatory present if the IE "Protocol error cause" in the IE "Protocol error information" has any other value than "ASN.1 violation or encoding error" or "Message type non-existent or not implemented" and not needed otherwise.
10.2.43 SECURITY MODE COMMAND

This message is sent by UTRAN to start or reconfigure ciphering and/or integrity protection parameters. RLC-SAP: AM Logical channel: DCCH
3GPP
Release 6
464
3GPP TS 25.331 V6.23.0 (2009-09)
Direction: UTRAN to UE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Security capability 10.3.3.37 Ciphering mode info 10.3.3.5 Integrity protection mode info 10.3.3.19 CN domain identity 10.3.1.1 1 to <maxInter SysMessa ges> Inter-RAT UE security capability 10.3.8.8a Semantics description
MP
MP
Security capability
MP
Ciphering mode info
OP
Only present if ciphering shall be controlled Only present if integrity protection shall be controlled
OP
CN Information elements CN domain identity
MP
Indicates which ciphering and integrity protection keys are applicable This IE is included if the IE "Inter-RAT UE radio access capability" was included in RRC CONNECTION SETUP COMPLETE message
Other information elements UE system specific security capability
CH
>Inter-RAT UE security capability
MP
10.2.44 SECURITY MODE COMPLETE

This message is sent by UE to confirm the reconfiguration of ciphering and/or integrity protection. RLC-SAP: AM Logical channel: DCCH Direction: UE to UTRAN
3GPP
465 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17 RB activation time info 10.3.4.13
MP
MP
OP
RB Information elements Radio bearer uplink ciphering activation time info
OP
10.2.45 SECURITY MODE FAILURE

This message is sent to indicate a failure to act on a received SECURITY MODE COMMAND message. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
MP
CH
Failure cause
MP
10.2.46 SIGNALLING CONNECTION RELEASE

This message is used to notify the UE that its ongoing signalling connection to a CN domain has been released. RLC-SAP: AM Logical channel: DCCH Direction: UTRANUE
3GPP
466 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 CN domain identity 10.3.1.1
MP
CH
MP
10.2.47 SIGNALLING CONNECTION RELEASE INDICATION

This message is used by the UE to indicate to UTRAN the release of an existing signalling connection. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
Information Element/Group name Message Type UE Information Elements Integrity check info Need MP Multi IE type and reference Message type Integrity check info 10.3.3.16 CN domain identity 10.3.1.1 Semantics description
CH
MP
10.2.48 SYSTEM INFORMATION

Information Element/Group name Message type SFNprime Need CVchannel1 CVchannel2 Multi Type and reference Message type Integer(0..40 94 by step of 2) Semantics description
CHOICE Segment combination >Combination 1 >Combination 2 >>First Segment
MP
SFN=SFNprime (for first 10ms frame of 20ms TTI), SFN=SFNprime+1 (for last 10ms frame of 20ms TTI) Five spares are needed (no data)
MP
First Segment, 10.2.48.1 Subsequent Segment, 10.2.48.3 Last segment
>Combination 3 >>Subsequent Segment
MP
>Combination 4 >>Last segment
MP
3GPP
467 Multi Type and reference (short),10.2. 48.5 Last Segment (short)10.2.4 8.5 First Segment (short), 10.2.48.2
>Combination 5 >>Last segment
Note 2 MP
>>First Segment
MP
>Combination 6 >>Last Segment
Note 2 MP Last Segment (short), 10.2.48.5 1 to maxSIBper Msg Complete SIB (short),10.2. 48.7 Note 2 MP Last Segment (short), 10.2.48.5 1..< maxSIBper Msg> Complete SIB (short),10.2. 48.7 First Segment (short), 10.2.48.2 1 to maxSIBper Msg Complete SIB (short),10.2. 48.7 1..MaxSIB perMsg Complete SIB (short),10.2. 48.7 First Segment (short), 10.2.48.2 Complete SIB,10.2.48. 6 Last segment,10. Note 2 Note 1 Note 2 Note 1 Note 1 Note 1
>>Complete list
MP
>>>Complete
MP
>Combination 7 >>Last Segment
>>Complete list
MP
>>>Complete
MP
>>First Segment
MP
>Combination 8 >>Complete list
MP
>>>Complete
MP
>Combination 9 >>Complete list >>>Complete
MP MP
>>First Segment
MP
>Combination 10 >>>Complete SIB of size 215 to 226 >Combination 11 >>Last segment of size 215 to 222
MP
MP
3GPP
468 Multi Type and reference 2.48.4
Condition channel1 channel2
Explanation The IE is mandatory present if the message is sent on the FACH and not needed otherwise. This IE is mandatory present if the channel is BCH, otherwise it is not needed.
If the encoded message does not fill a transport block, the RRC layer shall insert padding according to subclause 12.1. Padding is needed e.g. if the remaining space is insufficient to start a new First Segment (which requires several bits for SIB type, SEG_COUNT and SIB data). NOTE 1: If Combination 6 - 9 contains a Master information block Master information shall be located as the first IE in the list. NOTE 2: If one of the combinations 5 to 9 is used, the IE "SIB type" = "Extension Type" should not occur more than once in that message, otherwise the UE behaviour is unspecified.
10.2.48.1
First Segment
This segment type is used to transfer the first segment of a segmented system information block. The IE is used when the first segment fills the entire transport block (Combination 2).
Information Element/Group name Other information elements SIB type SEG_COUNT Need Multi Type and reference SIB Type, 10.3.8.21 SEG COUNT, 10.3.8.17 SIB data fixed, 10.3.8.19 Semantics description
MP MP
SIB data fixed
MP
10.2.48.2
First Segment (short)
This segment type is used to transfer the first segment of a segmented system information block. The IE is used when the first segment is concatenated after other segments in a transport block (Combination 5, 7 and 9).
Information Element/Group name Other information elements SIB type SEG_COUNT Need Multi Type and reference SIB Type, 10.3.8.21 SEG COUNT, 10.3.8.17 SIB data variable, 10.3.8.20 Semantics description
MP MP
SIB data variable
MP
10.2.48.3
Subsequent Segment
This segment type is used to transfer a subsequent segment of a segmented system information block.
3GPP
Release 6 Information Element/Group name Other information elements SIB type Segment index Need
469 Multi Type and reference SIB Type, 10.3.8.21 Segment Index, 10.3.8.18 SIB data fixed, 10.3.8.19
MP MP
SIB data fixed
MP
10.2.48.4
Last Segment
This segment type is used to transfer the last segment of a segmented system information block. The IE is used when the last segment has a length, excluding length denominator, from 215 through 222 (Combination 11).
Information Element/Group name Other information elements SIB type Segment index Need Multi Type and reference SIB Type, 10.3.8.21 Segment Index, 10.3.8.18 SIB data fixed, 10.3.8.19 Semantics description
MP MP
SIB data fixed
MP
In case the SIB data is less than 222 bits, padding shall be used. The same padding bits shall be used as defined in clause 12.1
10.2.48.5
Last Segment (short)
This segment type is used to transfer the last segment of a segmented system information block. The IE is used when the last segment has a length, excluding length denominator, of upto 214 bits (Combination 4, 5, 6 and 7).
Information Element/Group name Other information elements SIB type Segment index Need Multi Type and reference SIB Type, 10.3.8.21 Segment Index, 10.3.8.18 SIB data variable, 10.3.8.20 Semantics description
MP MP
SIB data variable
MP
10.2.48.6
Complete SIB
This segment type is used to transfer a non-segmented system information block. The IE is used when the complete SIB has a length, excluding length denominator, from 215 through 226 (Combination 10).
3GPP
Release 6 Information Element/Group name Other information elements SIB type SIB data fixed Need
470 Multi Type and reference SIB Type, 10.3.8.21 Bit string (226)
MP MP
The first/leftmost/most significant bit of the bit string contains the first bit of the segment. In case the SIB data is less than 226 bits, padding shall be used. The same padding bits shall be used as defined in clause 12.1
10.2.48.7
Complete SIB (short)
This segment type is used to transfer a non-segmented system information block. The IE is used when the complete SIB has a length, excluding length denominator, of upto 214 bits (Combination 6, 7, 8 and 9).
Information Element/Group name Other information elements SIB type SIB data variable Need Multi Type and reference SIB Type, 10.3.8.21 SIB data variable, 10.3.8.20 Semantics description
MP MP
10.2.48.8
System Information Blocks
The IE "SIB data" within the IEs, "First Segment", "Subsequent or last Segment" and "Complete SIB" contains either complete system information block or a segment of a system information block. The actual system information blocks are defined in the following clauses.
3GPP
Release 6
471
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.1
Master Information Block

Need Multi Type and reference MIB Value tag 10.3.8.9 PLMN Type 10.3.1.12 PLMN Identity 10.3.1.11 Multiple PLMN List 10.3.1.7a Semantics description Version
Information Element/Group name Other information elements MIB Value tag CN information elements Supported PLMN types PLMN Identity
MP
MP CV-GSM
Multiple PLMN List
OP
If present, this IE specifies the PLMNs of the cell. If absent, the IE PLMN Identity specifies the PLMN of the cell.
REL-6
ANSI-41 information elements ANSI-41 Core Network Information
CV-ANSI41
References to other system information blocks and scheduling blocks
MP
ANSI-41 Core Network Information 10.3.9.1 References to other system information blocks and scheduling blocks 10.3.8.14
Condition GSM
ANSI-41
Explanation The IE is mandatory present if the IE "Supported PLMN Types" is set to 'GSM-MAP' or 'GSM-MAP AND ANSI-41', and not needed otherwise The IE is mandatory present if the IE "Supported PLMN Types" is set to 'ANSI-41' or 'GSM-MAP AND ANSI-41', and not needed otherwise
10.2.48.8.2
Scheduling Block 1
Need MP Multi Type and reference References to other system information blocks 10.3.8.13 Semantics description
Information Element/Group name References to other system information blocks
10.2.48.8.3
Scheduling Block 2
Need MP Multi Type and reference References to other system information blocks 10.3.8.13 Semantics description
Information Element/Group name References to other system information blocks
3GPP
Release 6
472
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.4
The system information block type 1 contains NAS system information as well as UE timers and counters to be used in idle mode and in connected mode.
Information Element/Group name CN information elements CN common GSM-MAP NAS system information Need Multi Type and reference NAS system information (GSM-MAP) 10.3.1.9 1 to <maxCNdo mains> CN domain system information 10.3.1.2 UE Timers and constants in idle mode 10.3.3.44 UE Timers and constants in connected mode 10.3.3.43 The UE behaviour is unspecified if this IE is absent. Send CN information for each CN domain. Semantics description
MP
CN domain system information list >CN domain system information
MP
MP
UE information UE Timers and constants in idle mode
MD
UE Timers and constants in connected mode
MD
Default value means that for all timers and constants - For parameters with need MD, the defaults specified in 10.3.3.43 apply and - For parameters with need OP, the parameters are absent
10.2.48.8.5
The system information block type 2 contains the URA identity.

Information Element/Group name UTRAN mobility information elements URA identity list Need Multi Type and reference Semantics description
MP
1 ..<maxUR A> URA identity 10.3.2.6
>URA identity
MP
10.2.48.8.6
The system information block type 3 contains parameters for cell selection and re-selection.
3GPP
Release 6 Information Element/Group name SIB4 Indicator UTRAN mobility information elements Cell identity Cell selection and re-selection info Need MP
473 Multi Type and reference Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE indicates that SIB4 is broadcast in the cell. Version
MP MP
Cell Access Restriction
MP
Domain Specific Access Restriction Parameters For PLMN Of MIB
OP
Cell identity 10.3.2.2 Cell selection and reselection info for SIB3/4 10.3.2.3 Cell Access Restriction 10.3.2.1 Domain Specific Access Restriction Parameters 10.3.1.3c
This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the PLMN in the IE PLMN identity of the Master Information Block.
REL-6
Domain Specific Access Restriction For Shared Network >CHOICE barring representation >>Domain Specific Access Restriction List >>>Domain Specific Access Restriction Parameters For Operator1
OP MP
REL-6 REL-6 REL-6 Domain Specific Access Restriction Parameters 10.3.1.3c Domain Specific Access Restriction Parameters 10.3.1.3c Domain Specific Access Restriction Parameters 10.3.1.3c Domain Specific Access Restriction Parameters 10.3.1.3c Domain Specific Access Restriction Parameters 10.3.1.3c This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the first PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the second PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the third PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the fourth PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. This IE specifies the Domain Specific Access Restriction Parameters for UEs which has chosen the fifth PLMN in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block. REL-6
OP
>>>Domain Specific Access Restriction Parameters For Operator2
OP
REL-6
OP
REL-6
OP
REL-6
OP
REL-6
>>Domain Specific Access Restriction Parameters For All >>>Domain Specific Access Restriction Parameters
REL-6 Domain Specific This IE specifies the common Domain Specific Access REL-6
3GPP
Release 6
474 Access Restriction Parameters 10.3.1.3c
3GPP TS 25.331 V6.23.0 (2009-09) Restriction Parameters applied to all PLMNs in the IE multiplePLMNs in the IE Multiple PLMN List of the Master Information Block.
10.2.48.8.7
The system information block type 4 contains parameters for cell selection and re-selection to be used in connected mode.
Information Element/Group name UTRAN mobility information elements Cell identity Cell selection and re-selection info Need Multi Type and reference Semantics description
MP MP
MP
Cell identity 10.3.2.2 Cell selection and reselection info for SIB3/4 10.3.2.3 Cell Access Restriction 10.3.2.1
10.2.48.8.8
System Information Block type 5 and 5bis
The system information block type 5 contains parameters for the configuration of the common physical channels in the cell. System information block type 5bis uses the same structure as System information block type 5. System information block type 5bis is sent instead of system information block type 5 in cells that use Band IV.
Information Element/Group name SIB6 Indicator Need MP Multi Type and reference Boolean Semantics description TRUE indicates that SIB6 is broadcast in the cell. Version
PhyCH information elements PICH Power offset
MP
PICH Power offset 10.3.6.50
CHOICE mode >FDD >>AICH Power offset
MP MP AICH Power offset 10.3.6.3 PUSCH system informatio n 10.3.6.66 PDSCH system informatio n 10.3.6.46 TDD open loop power
>TDD >>PUSCH system information
OP
>>PDSCH system information
OP
>>TDD open loop power control
MP
3GPP
475 Type and reference control 10.3.6.79 Primary CCPCH info 10.3.6.57 PRACH system informatio n list 10.3.6.55 Secondar y CCPCH system informatio n 10.3.6.72 CBS DRX Level 1 informatio n 10.3.8.3 Frequenc y band indicator 10.3.6.35 b Frequenc y band indicator 2 10.3.6.35 c Enumerat ed (HSDPA Capable Cell)
Primary CCPCH info
OP
Note 1
PRACH system information list
MP
Secondary CCPCH system information
MP
Note 2
CBS DRX Level 1 information
CVCTCH
Frequency band indicator
OP
REL-6
Frequency band indicator 2
OP
REL-6
HSDPA cell Indicator
MD
Default is HSDPA capability not indicated. HSDPA Capable Cell means that the UE may consider this cell as part of the HSDPA coverage area for display indication only. This indication shall not be used for any other purpose. Default is E-DCH capability not indicated. E-DCH Capable Cell means that the UE may consider this cell as part of the E-DCH coverage area for display indication only. This indication shall not be used for any other purpose. Included if MCCH is on an S-CCPCH used only for MBMS. Note 2
REL-6
E-DCH cell Indicator
MD
Enumerat ed (EDCH Capable Cell)
REL-6
Secondary CCPCH system information MBMS
OP
Secondar y CCPCH system informatio n MBMS 10.3.6.72 a
REL-6
NOTE 1: DL scrambling code of the Primary CCPCH is the same as the one for Primary CPICH (FDD only).
3GPP
Release 6
476
3GPP TS 25.331 V6.23.0 (2009-09)
NOTE 2: There is only one MCCH in a cell, which may either be mapped on to an S-CCPCH also used for nonMBMS purposes or to an S-CCPCH dedicated to MBMS. In the first case the MCCH configuration is specified within the IE "Secondary CCPCH system information", in the latter case the MCCH configuration is provided within the IE "Secondary CCPCH system information MBMS".
Condition CTCH Explanation The IE is mandatory present if the IE "CTCH indicator" is equal to TRUE for at least one FACH, otherwise the IE is not needed in the message
10.2.48.8.9
The system information block type 6 contains parameters for the configuration of the common and shared physical channels to be used in connected mode.
Information Element/Group name PhyCH information elements PICH Power offset Need Multi Type and reference Semantics description Version
MP
PICH Power offset 10.3.6.50
CHOICE mode >FDD >>AICH Power offset
MP MP AICH Power offset 10.3.6.3 PUSCH system informatio n 10.3.6.66 PDSCH system informatio n 10.3.6.46 TDD open loop power control 10.3.6.79 Primary CCPCH info 10.3.6.57 PRACH system informatio n list 10.3.6.55 Secondar y CCPCH system informatio n 10.3.6.72 CBS DRX Level 1 informatio n 10.3.8.3
>TDD >>PUSCH system information
OP
>>PDSCH system information
OP
>>TDD open loop power control
MP
Primary CCPCH info
OP
Note 1
OP
OP
CVCTCH
3GPP
Release 6 Information Element/Group name Frequency band indicator Need OP Multi
477 Type and reference Frequenc y band indicator 10.3.6.35 b Frequenc y band indicator 2 10.3.6.35 c
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version REL-6
OP
REL-6
NOTE 1: DL scrambling code of the Primary CCPCH is the same as the one for Primary CPICH (FDD only).
Condition CTCH Explanation The IE is mandatory present if the IE "CTCH indicator" is equal to TRUE for at least one FACH, otherwise the IE is not needed
10.2.48.8.10
The system information block type 7 contains the fast changing parameters UL interference and Dynamic persistence level.
Information Element/Group name CHOICE mode >FDD >>UL interference Need MP MP UL interference 10.3.6.87 (no data) MP 1 to<maxPR ACH> Dynamic persistence level 10.3.6.35 1 to <maxPRA CH> Dynamic persistence level 10.3.6.35 Expiration Time Factor 10.3.3.12 The order of the PRACHs is the same as in system information block type 6. The order of the PRACHs is the same as in system information block type 5 or 5bis. Multi Type and reference Semantics description
>TDD PhyCH information elements PRACHs listed in system information block type 5
>Dynamic persistence level
MP
PRACHs listed in system information block type 6 >Dynamic persistence level
OP
MP
Expiration Time Factor
MD
Default is 1.
10.2.48.8.11
Void
10.2.48.8.12
Void
3GPP
Release 6
478
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.13
Void
10.2.48.8.14
The system information block type 11 contains measurement control information to be used in the cell.
Information Element/Group name SIB12 Indicator Measurement information elements FACH measurement occasion info Need MP Multi Type and reference Boolean Semantics description TRUE indicates that SIB12 is broadcast in the cell.
OP
Measurement control system information
MP
FACH measuremen t occasion info 10.3.7.8 Measuremen t control system information 10.3.7.47
10.2.48.8.14a
System Information Block type 11bis
The system information block type 11bis contains measurement control information to be used in the cell in addition to System Information Block type 11.
Information Element/Group name Measurement information elements Measurement control system information extension Need Multi Type and reference Semantics description Version REL-6 MP Measuremen t control system information extension 10.3.7.47a REL-6
10.2.48.8.15
The system information block type 12 contains measurement control information to be used in connected mode.
Information Element/Group name Measurement information elements FACH measurement occasion info Need Multi Type and reference Semantics description
OP
MP
FACH measuremen t occasion info 10.3.7.8 Measuremen t control system information 10.3.7.47
10.2.48.8.16
The system information block type 13 contains ANSI-41 system information.
3GPP
Release 6 Information Element/Group name Other information elements CN Information Elements CN Domain system information list >CN Domain system information Need
MP
1 to <maxCNdo mains> CN Domain system information 10.3.1.2 UE timers and constants in idle mode 10.3.3.44 Capability update requirement 10.3.3.2
Send CN information for each CN domain.
MP
UE Information UE timers and constants in idle mode
MD
The UE behaviour is unspecified if this IE is absent.
MD
Default value is defined in subclause 10.3.3.2
10.2.48.8.16.1
System Information Block type 13.1
The system information block type 13.1 contains the ANSI-41 RAND information.
Information Element/Group name ANSI-41 information elements ANSI-41 RAND information Need Multi Type and reference ANSI-41 RAND information 10.3.9.6 Semantics description
MP
10.2.48.8.16.2
The system information block type 13.2 contains the ANSI-41 User Zone Identification information.
Information Element/Group name ANSI-41 information elements ANSI-41 User Zone Identification information Need Multi Type and reference ANSI-41 User Zone Identification information 10.3.9.7 Semantics description
MP
10.2.48.8.16.3
The system information block type 13.3 contains the ANSI-41 Private Neighbour List information.
Information Element/Group name ANSI-41 information elements ANSI-41 Private Neighbour List information Need Multi Type and reference ANSI-41 Private Neighbour List information 10.3.9.5 Semantics description
MP
3GPP
Release 6
480
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.16.4
The system information block type 13.4 contains the ANSI-41 Global Service Redirection information.
Information Element/Group name ANSI-41 information elements ANSI-41 Global Service Redirection information Need Multi Type and reference ANSI-41 Global Service Redirection information 10.3.9.2 Semantics description
MP
10.2.48.8.17
NOTE:
Only for 3.84 Mcps TDD.
The system information block type 14 contains parameters for common and dedicated physical channel uplink outer loop power control information to be used in both idle and connected mode.
Information Element/Group name PhyCH information elements Individual Timeslot interference list >Individual Timeslot interference Need Multi Type and reference Semantics description
MP MP
1 to <maxTS> Individual Timeslot interference 10.3.6.38 Expiration Time Factor 10.3.3.12
MD
Default is 1.
10.2.48.8.18
The system information block type 15 contains information useful for UE-based or UE-assisted positioning methods.
Information Element/Group name GPS Data ciphering info Need OP Multi Type and Reference UE positioning Ciphering info 10.3.7.86 Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c UE positioning GPS reference time 10.3.7.96 1 to <maxSat> Enumerated( 0..63) Semantics description If this IE is present then the SIB types 15.1, 15.2 & 15.3 are ciphered in accordance with the Data Assistance Ciphering Algorithm specified in [18] approximate position where the UE is located
Reference position
MP
GPS reference time
MP
Satellite information
OP
This IE is present whenever bad (failed/failing) satellites are detected by UTRAN [18].
>BadSatID
MP
3GPP
Release 6
481
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.18.1
The system information block type 15.1 contains information useful for UE positioning DGPS Corrections. The DGPS Corrections message contents are based on a Type-1 message of DGPS specified in [13].
Information Element/Group name DGPS corrections Need MP Multi Type and Reference UE positioning GPS DGPS corrections 10.3.7.91 Semantics description
10.2.48.8.18.2
The system information block type 15.2 contains information useful for GPS Navigation Model. These IE fields are based on information extracted from the subframes 1 to 3 of the GPS navigation message [12].
Information Element/Group name Transmission TOW Need MP Multi Type and Reference Integer (0..604799) Semantics description The approximate GPS time-ofweek when the message is broadcast. in seconds Satellite ID
SatID GPS Ephemeris and Clock Correction Parameters
MP MP
Enumerated( 0..63) UE positioning GPS Ephemeris and Clock Correction parameters 10.3.7.91a
10.2.48.8.18.3
The system information block type 15.3 contains information useful for ionospheric delay, UTC offset, and Almanac. These IEs contain information extracted from the subframes 4 and 5 of the GPS navigation message, [12].
3GPP
Release 6 Information Element/Group name Transmission TOW Need MP
482 Multi Type and Reference Integer (0..604799)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The approximate GPS time-ofweek when the message is broadcast. in seconds
GPS Almanac and Satellite Health
OP
GPS ionospheric model
OP
GPS UTC model
OP
SatMask
CVAlmanac CVAlmanac
UE positioning GPS almanac 10.3.7.89 UE positioning GPS ionospheric model 10.3.7.92 UE positioning GPS UTC model 10.3.7.97 Bit string(1..32) Bit string(8)
indicates the satellites that contain the pages being broadcast in this data set
LSB TOW
Condition Almanac
Explanation This IE is mandatory present if the IE "GPS Almanac and Satellite Health" is present
10.2.48.8.18.4 System Information Block type 15.4 The system information block type 15.4 contains ciphering information for System Information Block type 15.5 and information useful for OTDOA UE-assisted Positioning method.
Information Element/Group name OTDOA Data ciphering info Need OP Multi Type and Reference UE positioning Ciphering info 10.3.7.86 UE positioning OTDOA assistance data for UEassisted 10.3.7.103 Semantics description If this IE is present then the for UE-based the System Information Block type 15.5 is ciphered in accordance with the Data Assistance Ciphering Algorithm specified in [18]
OTDOA assistance data for UEassisted
MP
10.2.48.8.18.4a
The system information block type 15.5 contains information useful for OTDOA UE-based Positioning method.
3GPP
Release 6 Information Element/Group name OTDOA assistance data for UEbased Need MP
483 Multi Type and Reference UE positioning OTDOA assistance data for UEbased 10.3.7.103a
10.2.48.8.19 System Information Block type 16

The system information block type 16 contains radio bearer, transport channel and physical channel parameters to be stored by UE in idle and connected mode for use during handover to UTRAN.
Information Element/Group name RB information elements Predefined RB configuration Need Multi Type and Reference Predefined RB configuration 10.3.4.7 Predefined TrCH configuration 10.3.5.9 Predefined PhyCH configuration 10.3.6.56 Semantics description
MP
TrCH Information Elements Predefined TrCH configuration
MP
PhyCH Information Elements Predefined PhyCH configuration
MP
10.2.48.8.20
NOTE:
Only for TDD.
The system information block type 17 contains fast changing parameters for the configuration of the shared physical channels to be used in connected mode.
Information Element/Group name PhyCH information elements PUSCH system information Need Multi Type and reference PUSCH system information 10.3.6.66 PDSCH system information 10.3.6.46 Semantics description
OP
PDSCH system information
OP
3GPP
Release 6
484
3GPP TS 25.331 V6.23.0 (2009-09)
10.2.48.8.21
The System Information Block type 18 contains PLMN identities of neighbouring cells to be considered in idle mode as well as in connected mode.
Information Element/Group name Idle mode PLMN identities Need OP Multi Type and reference PLMN identities of neighbour cells 10.3.7.53a PLMN identities of neighbour cells 10.3.7.53a PLMN identities of neighbour cells 10.3.7.53a PLMN identities of neighbour cells 10.3.7.53a Semantics description Version
Connected mode PLMN identities
OP
Idle mode PLMN identities for SIB 11bis
OP
REL-6
Connected mode PLMN identities for SIB 11bis
OP
REL-6
10.2.49 SYSTEM INFORMATION CHANGE INDICATION

This message is used to send information on FACH to the UEs in state CELL_FACH or CELL_DCH(TDD only) about coming modification of the system information. RLC-SAP: TM Logical channel: BCCH Direction: UTRAN UE
Information Element/Group name Message Type Other information elements BCCH modification info Need MP Multi Type and reference Message Type BCCH modification info 10.3.8.1 Semantics description
MP
If the encoded message does not fill a transport block, the RRC layer shall insert padding according to subclause 12.1.
10.2.50 TRANSPORT CHANNEL RECONFIGURATION

This message is used by UTRAN to configure the transport channel of a UE. This also includes a possible reconfiguration of physical channels. The message can also be used to assign a TFC subset and reconfigure physical channel. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
3GPP
Release 6 Information Element/Group name Message Type UE Information Elements RRC transaction identifier Need MP
485 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5
MP
CH
OP
Ciphering mode info
OP
MD OP
The UTRAN should not include this IE unless it is performing an SRNS relocation The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in ciphering algorithm Default value is "now" This IE is always set to TRUE and included if the activation time is restricted according to subclause 8.6.3.1
REL-6
New U-RNTI New C-RNTI New DSCH-RNTI
OP OP OP
U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 DSCH-RNTI 10.3.3.9a
OP OP OP MP
OP
OP
OP
OP OP 1 to
3GPP
486 Multi <maxRBall RABs> Type and reference
MP
RB with PDCP information 10.3.4.22
This IE is needed for each RB having PDCP in the case of lossless SRNS relocation This IE is needed for each RB having PDCP and performing PDCP context relocation REL-5 REL-5
OP OP
PDCP context relocation info 10.3.4.1a
TrCH Information Elements Uplink transport channels UL Transport channel information common for all transport channels
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <maxTrCH > Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH > Added or Reconfigure d DL TrCH information 10.3.5.1 Frequency info 10.3.6.36 Maximum allowed UL TX power 10.3.6.39 Uplink DPCH info 10.3.6.88 E-DCH Info 10.3.6.97 Downlink HS-PDSCH Information Default value is the existing maximum UL TX power
OP
MP
OP
OP
MP
OP
MD
Uplink DPCH info
OP
OP
REL-6
OP
REL-5
3GPP
Release 6 Information Element/Group name Downlink information common for all radio links Need
487 Multi Type and reference 10.3.6.23a Downlink information common for all radio links 10.3.6.24
OP
OP
1 to <maxRL> Downlink information for each radio link 10.3.6.27 Enumerated (TRUE)
MP
OP
REL-6
10.2.51 TRANSPORT CHANNEL RECONFIGURATION COMPLETE

This message is sent from the UE when a transport channel reconfiguration has been done. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17 (no data) MP OP Uplink Timing Advance 10.3.6.95 (no data) OP Activation time 10.3.3.1 Used for radio bearers mapped on RLC-TM. Only applicable if the UE is moving to CELL_DCH state due to this procedure REL-4 REL-4 REL-4 Semantics description Version
MP
CH
OP
OP
3GPP
Release 6 Information Element/Group name Uplink counter synchronisation info >RB with PDCP information list Need OP OP
1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains.
MP
>START list
MP
MP
>>START
MP
10.2.52 TRANSPORT CHANNEL RECONFIGURATION FAILURE

This message is sent by UE if the configuration given by UTRAN is unacceptable or if the UE failed to establish the physical channel(s). RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
MP
CH
Failure cause
MP
10.2.53 TRANSPORT FORMAT COMBINATION CONTROL

This message is sent by UTRAN to control the uplink transport format combination within the allowed transport format combination set. This message has different structures depending if the message is sent on transparent (TM) or nontransparent mode (AM or UM). RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRANUE
3GPP
489 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16
MP
CH
TrCH information elements CHOICE mode >FDD >TDD >>TFCS Id
MP (no data) OP Transport Format Combination Set Identity 10.3.5.21 Transport Format Combination subset 10.3.5.22 Activation time 10.3.3.1 TFC Control duration 10.3.6.80
DPCH/PUSCH TFCS in uplink
MP
Activation time for TFC subset
MD
TFC Control duration
OP
In case of transparent mode signalling the following message structure shall be used: RLC-SAP: TM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name TFC subset identity Need MP Multi Type and reference INTEGER (0..7) Semantics description
The encoding of this message is specified in subclause 12.4.1.1.
10.2.54 TRANSPORT FORMAT COMBINATION CONTROL FAILURE

This message is sent to indicate that a received TRANSPORT FORMAT COMBINATION CONTROL message could not be handled by the UE. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
MP
CH
Failure cause
MP
10.2.55 UE CAPABILITY ENQUIRY

The UE CAPABILITY ENQUIRY is used by the UTRAN to enquire inter-RAT classmarks from the UE. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Capability update requirement 10.3.3.2 Semantics description
MP
CH
MP
10.2.56 UE CAPABILITY INFORMATION

This message is sent by UE to convey UE specific capability information to the UTRAN. RLC-SAP: AM Logical channel: DCCH Direction: UE UTRAN
3GPP
491 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 UE radio access capability 10.3.3.42 UE radio access capability extension 10.3.3.42a 1 to <maxInter SysMessa ges> Inter-RAT UE radio access capability10. 3.8.7
OP
CH
UE radio access capability
OP
OP
Other information elements UE system specific capability
OP
MP
10.2.57 UE CAPABILITY INFORMATION CONFIRM

This message is sent by UTRAN to confirm that UE capability information has been received. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRAN UE
MP
CH
10.2.58 UPLINK DIRECT TRANSFER

This message is used to transfer NAS messages for an existing signalling connection. RLC-SAP: AM Logical channel: DCCH Direction: UE ->UTRAN
3GPP
Release 6 Information Element/Group name Message Type UE information elements Integrity check info Need MP
492 Multi Type and reference Message Type Integrity check info 10.3.3.16 CN domain identity 10.3.1.1 NAS message 10.3.1.8
CH
MP
NAS message
MP
OP
Measured results on RACH 10.3.7.45
10.2.59 UPLINK PHYSICAL CHANNEL CONTROLtest

NOTE: Only for TDD. This message is used to transfer uplink physical channel parameters to the UE. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements RRC transaction identifier Need MP Multi Type and Reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 CCTrCH power control info 10.3.6.8 Special Burst Scheduling 10.3.6.75a Power control information for one CCTrCH UL Special Burst generation period in radio frames REL-4 REL-4 Alpha 10.3.6.5 UL Timing Advance Control 10.3.6.96 Constant value TDD Semantics description Version
MP
OP
PhyCH information elements CCTrCH power control info
OP
Special Burst Scheduling
OP
CHOICE TDD option >3.84 Mcps TDD >>Alpha >>Timing Advance Control
MP OP OP
>>PRACH Constant Value
OP
Operator controlled PRACH
3GPP
Release 6 Information Element/Group name >>PUSCH Constant Value Need
493 Multi Type and Reference 10.3.6.11a Constant value TDD 10.3.6.11a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Margin Operator controlled PUSCH Margin Version
OP
>>UE positioning related parameters >>>IPDL-Alpha >>>Max power increase >> HS-SICH power control info
CV-IPDLs MP MP OP Alpha 10.3.6.5 Integer (0..3) HS-SICH Power Control Info 10.3.6.36b
REL-4 REL-4 In dB Only applies to TDD 3.84 Mcps REL-4 REL-5
>1.28 Mcps TDD >>Uplink synchronisation parameters
MD
>>>Uplink synchronisation step size
MP
Integer(1..8)
>>>Uplink synchronisation frequency
MP
Integer(1..8)
>>PRXHS-SICH >>TPC step size
OP OP
Integer (-120..-58 by step of 1) Integer (1, 2, 3)
Default: Uplink synchronisation step size 1. Uplink synchronisation frequency 1. This parameter specifies the step size to be used for the adjustment of the uplink transmission timing This parameter specifies the frequency of the adjustment of the uplink transmission timing In dBm. Desired power level for HS-SICH In dB. For HSSICH
REL-4 REL-4
REL-4
REL-4
REL-6 REL-6
Condition IPDLs
Explanation This IE is present only if idle periods are applied
10.2.60 URA UPDATE

This message is used by the UE to initiate a URA update procedure. RLC-SAP: TM Logical channel: CCCH Direction: UEUTRAN
Information Element/Group name Message Type UE information elements U-RNTI Need MP Multi Type and reference Message Type U-RNTI 10.3.3.47 Semantics description
MP
3GPP
Release 6 Information Element/Group name RRC transaction identifier Need CVProtErr
494 Multi Type and reference RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 URA update cause 10.3.3.46 Protocol error indicator 10.3.3.27 Protocol error information 10.3.8.12
CH
URA update cause
MP
MD
Other information elements Protocol error information
CV-ProtErr
Condition ProtErr
Explanation The IE is mandatory present if the IE "Protocol error indicator" has the value "TRUE" and not needed otherwise.
10.2.61 URA UPDATE CONFIRM

This message confirms the URA update procedure and can be used to reallocate new RNTI information for the UE valid after the URA update. RLC-SAP: UM Logical channel: CCCH or DCCH Direction: UTRANUE
Information Element/Group name Message Type UE information elements U-RNTI RRC transaction identifier Need MP Multi Type and reference Message Type U-RNTI 10.3.3.47 RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5 Semantics description Version
CV-CCCH MP
CH
OP
Ciphering mode info
OP
Integrity check info is included if integrity protection is applied The UTRAN should not include this IE unless it is performing an SRNS relocation The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description ciphering algorithm Version
New U-RNTI New C-RNTI RRC State Indicator
OP OP MP
OP
U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 RRC State Indicator 10.3.3.35a UTRAN DRX cycle length coefficient 10.3.3.49 CN Information info 10.3.1.3
OP
OP
MP
OP OP
Condition CCCH
Explanation This IE is mandatory present when CCCH is used and not needed otherwise.
10.2.62 UTRAN MOBILITY INFORMATION

This message is used by UTRAN to allocate a new RNTI and to convey other UTRAN mobility related information to a UE. RLC-SAP: AM or UM Logical channel: DCCH Direction: UTRANUE
Information Element/Group name Message Type UE Information Elements Integrity check info Need MP Multi Type and reference Message Type Integrity check info Semantics description Version
CH
3GPP
Release 6 Information Element/Group name RRC transaction identifier Need
496 Multi Type and reference 10.3.3.16 RRC transaction identifier 10.3.3.36 Integrity protection mode info 10.3.3.19 Ciphering mode info 10.3.3.5
MP
OP
Ciphering mode info
OP
The UTRAN should not include this IE unless it is performing an SRNS relocation The UTRAN should not include this IE unless it is performing an SRNS relocation and a change in ciphering algorithm
New U-RNTI New C-RNTI UE Timers and constants in connected mode
OP OP OP
U-RNTI 10.3.3.47 C-RNTI 10.3.3.8 UE Timers and constants in connected mode 10.3.3.43 CN Information info full 10.3.1.3a URA identity 10.3.2.6
OP
UTRAN Information Elements URA identity RB Information elements Downlink counter synchronisation info >RB with PDCP information list
OP
MP
OP OP
10.2.63 UTRAN MOBILITY INFORMATION CONFIRM

This message is used to confirm the new UTRAN mobility information for the UE. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
497 Multi Type and reference Message Type RRC transaction identifier 10.3.3.36 Integrity check info 10.3.3.16 Integrity protection activation info 10.3.3.17 Activation time 10.3.3.1
MP
CH
OP
RB Information elements COUNT-C activation time
OP
Used for radio bearers mapped on RLC-TM. Only applicable if the UE is moving to CELL_DCH state due to this procedure
OP OP 1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 1 to <maxCNdo mains> CN domain identity 10.3.1.1 START 10.3.3.38 START [40] values for all CN domains. This IE is needed for each RB having PDCP in the case of lossless SRNS relocation
MP
>START list
MP
MP
>>START
MP
10.2.64 UTRAN MOBILITY INFORMATION FAILURE

This message is sent to indicate a failure to act on a received UTRAN MOBILITY INFORMATION message. RLC-SAP: AM Logical channel: DCCH Direction: UEUTRAN
3GPP
MP
CH
Failure cause
MP
10.3
10.3.1
10.3.1.1
Information element functional definitions

CN Information elements
CN domain identity
Identifies the type of core network domain.

Information Element/Group name CN domain identity Need MP Multi Type and reference Enumerated (CS domain, PS domain) Semantics description
10.3.1.2
CN Domain System Information

Need MP Multi Type and reference CN domain identity 10.3.1.1 Semantics description
Information Element/Group name CN domain identity
CHOICE CN Type >GSM-MAP >>CN domain specific NAS system information
MP MP NAS system information (GSM-MAP) 10.3.1.9 ANSI-41 NAS system information, 10.3.9.4 CN domain specific DRX cycle length coefficient, 10.3.3.6
>ANSI-41 >>CN domain specific NAS system information
MP
MP
3GPP
Release 6
499
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.3
CN Information info
Need OP Multi Type and reference PLMN identity 10.3.1.11 NAS system information (GSM-MAP) 10.3.1.9 Semantics description Version
Information Element/Group name PLMN identity
CN common GSM-MAP NAS system information
OP
CN domain related information
OP
1 to <maxCNdo mains> CN domain identity 10.3.1.1 NAS system information (GSM-MAP) 10.3.1.9 PLMN identity 10.3.1.11
>CN domain identity
MP
>CN domain specific GSM-MAP NAS system info
MP
Primary PLMN identity
OP
REL-6
10.3.1.3a
CN Information info full

Need OP Multi Type and reference PLMN identity 10.3.1.11 NAS system information (GSM-MAP) 10.3.1.9 Semantics description Version
Information Element/Group name PLMN identity
CN common GSM-MAP NAS system information
OP
CN domain related information
OP
1 to <maxCNdo mains> CN domain identity 10.3.1.1 NAS system information (GSM-MAP) 10.3.1.9 CN domain specific DRX cycle length coefficient, 10.3.3.6 PLMN identity 10.3.1.11
>CN domain identity
MP
>CN domain specific GSM-MAP NAS system info
MP
>CN domain specific DRX cycle length coefficient
MP
Primary PLMN identity
OP
REL-6
3GPP
Release 6
500
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.3b
Domain Specific Access Restriction

Need MP (no data) This means no Access Class is barred MD <MaxAC> The first instance of the parameter corresponds to Access Class 0, the second to Access Class 1 and so on up to Access Class 15. UE reads this IE of its access class stored in SIM. The default value is the IE "Access Class Barred list" contained in the IE "Cell Access Restriction" of the System Information Block Type 3. Enumerated( barred, not barred) Multi Type and reference Semantics description Version REL-6 REL-6
Information Element/Group name CHOICE restriction status >no restriction
>restriction >>Domain Specific Access Class Barred List
REL-6 REL-6
>>>Access Class Barred
MP
REL-6
10.3.1.3c
Domain Specific Access Restriction Parameters
This IE specifies domain specific access class restriction parameters for CS and PS domain.
Information Element/Group name CS Domain Specific Access Restriction Need MP Multi Type and reference Domain Specific Access Restriction 10.3.1.3b Domain Specific Access Restriction 10.3.1.3b Semantics description This IE contains Domain Specific Access Restriction Parameters for CS domain. Version REL-6
PS Domain Specific Access Restriction
MP
This IE contains Domain Specific Access Restriction Parameters for PS domain.
REL-6
10.3.1.4
IMEI
This IE contains an International Mobile Equipment Identity. Setting specified in [11].

Information Element/Group name IMEI Need MP 15 Multi Type and reference Semantics description The first element contains the first IMEI digit, the second element the second IMEI digit and so on. INTEGER(0. .15)
>IMEI digit
MP
10.3.1.5
IMSI (GSM-MAP)
This IE contains an International Mobile Subscriber Identity, used towards a GSM-MAP type of PLMN. Setting specified in [11].
3GPP
Release 6 Information Element/Group name IMSI Need MP
501 Multi 6 to 21 Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The first element contains the first IMSI digit, the second element the second IMSI digit and so on. Although normally upto 15 digits are used for this IE, a bigger length is used to support future extension. INTEGER(0. .9)
>IMSI digit
MP
10.3.1.6
Intra Domain NAS Node Selector
This IE carries information to be used to route the establishment of a signalling connection to a CN node within a CN domain.
Information Element/Group name CHOICE version >R99 Need MP This choice shall also be used by mobiles that are compliant to this version of the protocol MP MP TMSI allocated in the current LA or PTMSI allocated in the current RA The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bit b23 of the TMSI/PTMSI. TMSI allocated in another LA of this PLMN or PTMSI allocated in another RA this PLMN The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI. TMSI or a PTMSI allocated in another PLMN Multi Type and reference Semantics description
>>CHOICE CN type >>>GSM-MAP >>>>CHOICE Routing basis >>>>>local (P)TMSI
>>>>>>Routing parameter
MP
Bit string (10)
>>>>>(P)TMSI of same PLMN, different (RA)LA
>>>>>>Routing parameter
MP
Bit string (10)
>>>>>(P)TMSI of different PLMN
3GPP
Release 6 Information Element/Group name >>>>>>Routing parameter Need MP
502 Multi Type and reference Bit string (10)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant. The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/leftmost/most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI. NAS identity is IMSI The "Routing parameter" bit string consists of DecimalToBinary [(IMSI div 10) mod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result. NAS identity is IMSI The "Routing parameter" bit string consists of DecimalToBinary [(IMSI div 10) mod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result. NAS parameter is IMEI The "Routing parameter" bit string consists of DecimalToBinary [(IMEI div 10) mod 1000]. The first/leftmost bit of the bit string contains the most significant bit of the result. This choice shall not be used in this version This choice shall not be used in this version All bits shall be set to 0 This bit string shall not be sent by mobiles that are compliant to this version of the protocol.
>>>>>IMSI(response to IMSI paging) >>>>>>Routing parameter
MP
Bit string (10)
>>>>>IMSI(cause UE initiated event) >>>>>>Routing parameter
MP
Bit string (10)
>>>>>IMEI >>>>>>Routing parameter
MP
Bit string (10)
>>>>>Spare 1 >>>>>Spare 2 >>>ANSI-41 >Later
Bit string (10) Bit string (10) Bit string (14) Bit string(15)
10.3.1.7
Location Area Identification
Identifies uniquely a location area for a GSM-MAP type of PLMN. Setting specified in [5].
Information Element/Group name PLMN identity Need MP Multi Type and reference PLMN identity 10.3.1.11 Bit string(16) Semantics description
LAC
MP
The first/leftmost bit of the bit string contains the most significant bit of the LAC..
3GPP
Release 6
503
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.7a
Multiple PLMN List
This information element identifies the multiple Public Land Mobile Networks (for a GSM-MAP type of PLMN) of a cell in a shared network.
Information Element/Group name MIB PLMN Identity Need MP Multi Type and reference Boolean Semantics description The PLMN identity IE 10.3.1.11, broadcasted in the MIB, shall be included in the multiple PLMN list if and only if this IE is TRUE. Version REL-6
Multiple PLMNs >PLMN identity with Optional MCC
MP
1 to 5 PLMN identity with Optional MCC 10.3.1.11a
REL-6 REL-6
10.3.1.8
NAS message
A non-access stratum message to be transferred transparently through UTRAN.

Information Element/Group name NAS message Need MP Multi Type and reference Octet string (1..4095) Semantics description The first octet contains octet 1 [17] of the NAS message, the second octet contains octet 2 of the NAS message and so on.
10.3.1.9
NAS system information (GSM-MAP)
This information element contains system information that belongs to the non-access stratum for a GSM-MAP type of PLMN. This information is transparent to RRC. It may contain either information specific to one CN domain (CS or PS) or information common for both CN domains.
Information Element/Group name GSM-MAP NAS system information Need MP Multi Type and reference Octet string(1..8 ) Semantics description The first octet contains octet 1 [5] of the NAS system information element, the second octet contains octet 2 of the NAS system information element and so on.
10.3.1.10
Paging record type identifier

Need MP Multi Type and reference Enumerated (IMSI (GSMMAP), TMSI (GSM-MAP)/ P-TMSI, IMSI (DS41), TMSI (DS-41)) Semantics description
Information Element/Group name Paging record type identifier
3GPP
Release 6
504
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.11
PLMN identity
This information element identifies a Public Land Mobile Network for a GSM-MAP type of PLMN. Setting of digits is defined in [11].
Information Element/Group name MCC Need MP 3 Multi Type and reference Semantics description The first element contains the first MCC digit, the second element the second MCC digit and so on. INTEGER(0. .9) 2 to 3 The first element contains the first MNC digit, the second element the second MNC digit and so on. INTEGER(0. .9)
>MCC digit MNC
MP MP
>MNC digit
MP
10.3.1.11a
PLMN identity with Optional MCC
This information element is a PLMN identity in subclause 10.3.1.11 where MCC is optional. It is used in a shared network and inserted in the Multiple PLMN List in subclause 10.3.1.7a.
Information Element/ Group name MCC Need MD Multi 3 Type and reference Semantics description The first element contains the first MCC digit, the second element the second MCC digit and so on. Integer (0..9) 2 to 3 The first element contains the first MNC digit, the second element the second MNC digit and so on. Integer (0..9) Version REL-6
>MCC digit MNC
MP MP
REL-6 REL-6
>MNC digit
MP
REL-6
10.3.1.12
PLMN Type
Identifies the type of Public Land Mobile Network (PLMN). This IE shall be used to control the interpretation of network dependent messages and information elements in the RRC protocol.
Information Element/Group name PLMN Type Need MP Multi Type and reference Enumerated (GSM-MAP, ANSI-41, GSM-MAP and ANSI41) Semantics description One spare value is needed.
10.3.1.13
P-TMSI (GSM-MAP)
This IE contains a Packet Temporary Mobile Subscriber Identity, used towards a GSM-MAP type of PLMN.
3GPP
Release 6 Information Element/Group name P-TMSI Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Setting specified in [11]. The first/leftmost bit of the bit string contains the most significant bit of the P-TMSI.
10.3.1.14
RAB identity
This information element uniquely identifies a radio access bearer within a CN domain.
Information Element/Group name CHOICE RAB identity type >RAB identity (GSM-MAP) Need MP Bit string (8) Formatted according to [5]. The first/leftmost bit of the bit string contains the most significant bit of the RAB identity. In case of a radio bearer setup for an MBMS selected service, the RAB identity is set to the value reserved for MBMS Broadcast mode, see [5]. The first/leftmost bit of the bit string contains the most significant bit of the RAB identity. Multi Type and reference Semantics description
>RAB identity (ANSI-41)
Bit string (8)
CHOICE NAS binding info type RAB identity (GSM-MAP) RAB identity (ANSI-41)
Condition under which the given RAB identity type is chosen PLMN is of type GSM-MAP PLMN is of type ANSI-41
10.3.1.15
Routing Area Code
Identifies a routing area within a location area for a GSM-MAP type of PLMN.
Information Element/Group name Routing Area Code Need MP Multi Type and reference Bit string(8) Semantics description Setting specified in [11]. The first/leftmost bit of the bit string contains the most significant bit of the Routing Area Code.
10.3.1.16
Routing Area Identification
Identifies uniquely a routing area for a GSM-MAP type of PLMN. Setting specified in [11].
Information Element/Group name LAI Need MP Multi Type and reference Location area identification 10.3.1.7 Routing area code 10.3.1.15 Semantics description
RAC
MP
3GPP
Release 6
506
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.1.17
TMSI (GSM-MAP)
This IE contains a Temporary Mobile Subscriber Identity, used towards a GSM-MAP type of PLMN.
Information Element/Group name TMSI (GSM-MAP) Need MP Multi Type and reference Bit string (32) Semantics description Setting specified in [11]. The first/leftmost bit of the bit string contains the most significant bit of the TMSI.
10.3.2
10.3.2.1
UTRAN mobility Information elements

Indicates the restrictions to cell access.

Information Element/Group name Cell Barred Need MP Multi Type and reference Enumerated( not barred, barred) Enumerated( not allowed, allowed) Integer (10,20,40,80 ,160,320,640 ,1280) Enumerated( reserved, not reserved) Enumerated( reserved, not reserved) Semantics description
Intra-frequency cell re-selection indicator Tbarred
CV-Barred
CV-Barred
[4] [s]
Cell Reserved for operator use
MP
Cell Reservation Extension
MP
Access Class Barred list
CV-SIB3MD
maxAC
Default is no access class barred is applied. The first instance of the parameter corresponds to Access Class 0, the second to Access Class 1 and so on up to Access Class 15. UE reads this IE of its access class stored in SIM. Enumerated (barred, not barred)
>Access Class Barred
MP
Condition Barred
SIB3-MD
Explanation The IE is mandatory present if the IE "Cell Barred" has the value "Barred"; otherwise the element is not needed in the message. The IE is mandatory and has a default value if the IE "Cell Access Restriction" is included in SIB 3. Otherwise the IE is not needed.
10.3.2.2
Cell identity
This information element identifies a cell unambiguously within a PLMN. NOTE: This information element may carry any implementation dependent identity that unambiguously identifies a cell within a PLMN.
3GPP
Release 6 Information Element/Group name Cell identity Need MP
507 Multi Type and reference bit string(28)
10.3.2.3
Cell selection and re-selection info for SIB3/4

Need OP Multi Type and reference Mapping info 10.3.2.5 Enumerat ed (CPICH Ec/N0, CPICH RSCP) Semantics description This IE should not be sent. Choice of measurement (CPICH Ec/N0 or CPICH RSCP) to use as quality measure Q for FDD cells. This IE is also sent to the UE in SIB11/12. Both occurrences of the IE should be set to the same value. Version
Information Element/Group name Mapping Info
Cell selection and reselection quality measure
MP
CHOICE mode >FDD >>Sintrasearch
MP OP Integer (32..20 by step of 2) If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB]
>>Sintersearch
OP
Integer (32..20 by step of 2)
>>SsearchHCS
OP
>>RAT List
OP
1 to <maxOt herRAT > Enumerat ed (GSM, cdma200 0) Integer (32..20 by step of 2)
>>>RAT identifier
MP
>>>Ssearch,RAT
MP
>>>SHCS,RAT
OP
>>>Slimit,SearchRAT
MP
Integer (-
In case the value 20 is received the UE shall consider this IE as if it was absent according to [4] If a negative value is received the UE shall consider the value to be 0. [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is
3GPP
508 Type and reference 32..20 by step of 2)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description received the UE shall consider the value to be 0. [4] [dB] Ec/N0, [dB] RSCP, [dBm] Version
>>Qqualmin >>Qrxlevmin
MP MP
>> DeltaQrxlevmin
CVDelta
Integer (24..0) Integer (115..-25 by step of 2) Integer(4..-2 by step of 2)
If present, the actual value of Qrxlevmin = Qrxlevmin + DeltaQrxlevmin If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB]
REL-5
>TDD >>Sintrasearch
OP
>>Sintersearch
OP
>>SsearchHCS
OP
>>RAT List
OP
1 to <maxOt herRAT > Enumerat ed (GSM, cdma200 0) Integer (105..91 by step of 2)
>>>RAT identifier
MP
>>>Ssearch,RAT
MP
>>>SHCS,RAT
OP
>>>Slimit,SearchRAT
MP
>>Qrxlevmin
MP
Integer (115..-25
In case the value 91 is received the UE shall consider this IE as if it was absent according to [4] If a negative value is received the UE shall consider the value to be 0. [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB] If a negative value is received the UE shall consider the value to be 0. [4] [dB] RSCP, [dBm]
3GPP
509 Type and reference by step of 2) Integer(4..-2 by step of 2) Integer (0..40 by step of 2) Integer (0..40)
>>DeltaQrxlevmin
CVDelta
Qhyst1s
MP
If present, the actual value of Qrxlevmin = Qrxlevmin + DeltaQrxlevmin [4] [dB] If present, it is used as Qhyst1s for UE in CELL_PCH or URA_PCH state [4] [dB] If present, it is used as Qhyst1s for UE in CELL_FACH state [4] [dB] Default value is Qhyst1s [4] [dB] If present, it is used as Qhyst2s for UE using CPICH Ec/No quality measure in CELL_PCH or URA_PCH state. Default value is Qhyst1s,PCH [4] [dB] If present, it is used as Qhyst2s for UE using CPICH Ec/No quality measure in CELL_FACH state. Default value is Qhyst1s,FACH [4] [dB] [s] If present, it is used as Treselections for UE in CELL_PCH or URA_PCH state [4] [s] If present, it is used as Treselections for UE in CELL_FACH state [4] [s] This IE is used by the UE in high mobility state as scaling factor for Treselections or Treselections,PCH or Treselections,FACH [4]. If present, it is used by the UE as scaling factor
REL-5
Qhyst1s,PCH
CV-SIB4
REL-5
Qhyst1s,FACH
CV-SIB4
Integer (0..40)
REL-5
Qhyst2s
Qhyst2s,PCH
CVFDDQualityMeasure CVSIB4FDDQualityMeasure
Integer (0..40 by step of 2) Integer (0..40)
REL-5
Qhyst2s,FACH
CVSIB4FDDQualityMeasure
Integer (0..40)
REL-5
Treselections Treselections,PCH
MP CV-SIB4
Integer (0..31) Integer (0..31)
REL-5
Treselections,FACH
CV-SIB4
Real (0..6.2 by step of 0.2) Real (0..1 by step of 0.1)
REL-5
Speed dependent ScalingFactor for Treselection
OP
REL-5
Inter-frequency ScalingFactor for
OP
Real (1..4.75
REL-5
3GPP
Release 6 Information Element/Group name Treselection Need Multi
510 Type and reference by step of 0.25)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description for Treselections or Treselections,PCH or Treselections,FACH for inter-frequency cell reselection evaluation [4]. If present, it is used by the UE as scaling factor for Treselections or Treselections,PCH or Treselections,FACH for inter-RAT cell reselection evaluation [4]. [s] Default value is not used. REL-5 Version
Inter-RAT ScalingFactor for Treselection
OP
Real (1..4.75 by step of 0.25)
Non-HCS_TCRmax
MD
Enumerat ed (not used, 30, 60, 120, 180, 240) Integer (1..16)
REL-5
Non-HCS_NCR
CV-UE speed detector _MD CV-UE speed detector _MP
Default value = 8
REL-5
Non-HCS_TCRmaxHyst
Enumerat ed (not used, 10, 20, 30, 40, 50, 60, 70) HCS Serving cell informatio n 10.3.7.12 Maximum allowed UL TX power 10.3.6.39
[s]
REL-5
HCS Serving cell Information
OP
MP
[dBm] UE_TXPWR_MAX_RA CH in [4].
3GPP
Release 6 Condition FDD-Quality-Measure
511
3GPP TS 25.331 V6.23.0 (2009-09)
Delta SIB4
Explanation The IE is not needed if the IE "Cell selection and reselection quality measure" has the value CPICH RSCP, otherwise the IE is mandatory and has a default value. This IE is optional if the value of Qrxlevmin is below 115dBm. It is not needed otherwise. This IE is optional if the IE Cell selection and reselection info for SIB3/4 is included in SIB type 4. It is not needed otherwise. This IE is optional if the IE Cell selection and reselection info for SIB3/4 is included in SIB type 4, and the IE "Cell selection and reselection quality measure" has the value CPICH Ec/N0. It is not needed otherwise. This IE is not needed if non-HCS_TCRmax equals 'not used', else it is mandatory default. This IE is not needed if non-HCS_TCRmax equals 'not used', else it is mandatory present.
SIB4-FDD-Quality-Measure
UE Speed detector_MD (non-HCS)
UE Speed detector_MP (non-HCS)
10.3.2.4
Cell selection and re-selection info for SIB11/12

Need MD CVFDDQualityMeasure MD Multi Type and reference Integer(50..50) Integer(50..50) Semantics description Default value is 0. [dB] Default value is 0. [dB] Version
Information Element/Group name Qoffset1s,n Qoffset2s,n
Maximum allowed UL TX power 10.3.6.39
According to UE_TXPWR_MAX_RA CH in [4], [dBm]. If applied to FDD or TDD cells, the default is the Maximum allowed UL TX power for the serving cell. If applied to a GSM cell, the default is the UE maximum output power applicable for this GSM cell, according to the UE's radio access capability.
HCS neighbouring cell information
OP
HCS Neighbou ring cell informatio n 10.3.7.11
CHOICE mode >FDD >>Qqualmin
MP CVFDDServingCell MD Integer (24..0) Ec/N0, [dB] Default value is Qqualmin for the serving cell RSCP, [dBm] Default value is Qrxlevmin for the serving cell
>>Qrxlevmin
Integer (115..-25 by step of 2)
3GPP
Release 6 Information Element/Group name >>DeltaQrxlevmin Need CVDelta Multi
512 Type and reference Integer(4..-2 by step of 2)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description If present, the actual value of Qrxlevmin = Qrxlevmin + DeltaQrxlevmin RSCP, [dBm] Default value is Qrxlevmin for the serving cell If present, the actual value of Qrxlevmin = Qrxlevmin + DeltaQrxlevmin GSM RSSI, [dBm] Default value is Qrxlevmin for the serving cell Version REL-5
>TDD >>Qrxlevmin
MD
>> DeltaQrxlevmin
CVDelta
Integer (115..-25 by step of 2) Integer(4..-2 by step of 2)
REL-5
>GSM >>Qrxlevmin
MD
Integer (115..-25 by step of 2)
Condition FDD-Quality-Measure
FDD-Serving-Cell
Delta
Explanation This IE is mandatory and has a default value for Intra/Inter Frequency Cells if the IE "Cell selection and reselection quality measure" has the value CPICH Ec/No. Otherwise the IE is absent. This IE is mandatory and has a default value if the serving cell is an FDD cell. Otherwise the IE is mandatory present. This IE is optional if Qrxlevmin is present and the value of Qrxlevmin is below 115dBm. It is not needed otherwise.
10.3.2.5
Mapping Info
Need MP MP Multi 1 to <MaxRAT> Enumerated (UTRA FDD, UTRA TDD 3.84 Mcps, UTRA TDD 1.28 Mcps, GSM, cdma2000) 1 to <maxMeas Intervals> Enumerated (linear, function type 2, function type 3, function type 4) Integer (0..99) Type of the function within the interval. UTRA TDD 1.28 Mcps is included for REL4. Type and Reference Semantics description Version
Information Element/Group name Mapping List >RAT
>Mapping Function Parameter List >>Function type
MP
MP
>>Map_parameter_1
MD
Parameter describing the mapping function between the quality measurement and the representing quality value, see
3GPP
513 Multi Type and Reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description [4]. Default value is zero for the first interval or otherwise the value of Map_parameter_2 of the interval before. Version
>>Map_parameter_2
MP
Integer (0..99)
Parameter describing the mapping function between the quality measurement and the representing quality value, see [4]. Upper limit of interval for which the Map_parameter_1 and Map_parameter_2 are valid. MaxMeas = 25 if RAT = UTRA FDD / CPICH Ec/N0, MaxMeas = 91 if RAT = UTRA TDD 3.84 Mcps or if RAT = UTRA TDD 1.28 Mcps or if RAT = UTRA FDD/ CPICH RSCP, MaxMeas = 63 if RAT = GSM. UTRA TDD 1.28 Mcps is included for REL4.
>>Upper_limit
CV-MaxInt
Integer (1..MaxMeas )
Condition MaxInt
Explanation This IE is mandatory present if Mapping Function Parameter List has not reached maxMeasIntervals and is not needed otherwise.
10.3.2.6
URA identity
Gives the identity of the UTRAN Registration Area. It can be used to indicate to the UE which URA it shall use in case of overlapping URAs.
Information Element/Group name URA identity Need MP Multi Type and reference bit string(16) Semantics description
3GPP
Release 6
514
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3
10.3.3.1
UE Information elements
Activation time
Activation Time defines the frame number/time at which the operation/changes caused by the related message shall take effect. Values between 0 and 255 indicate the absolute value of CFN (Connection Frame Number) of that frame number/time.
Information Element/Group name Activation time Need MP Multi Type and reference Integer(0.. 255) Semantics description CFN [10]
10.3.3.2
Capability Update Requirement
This IE indicates to the UE which specific capabilities to transfer to the network.

Information Element/Group name UE radio access FDD capability update requirement UE radio access 3.84 Mcps TDD capability update requirement UE radio access 1.28 Mcps TDD capability update requirement System specific capability update requirement list Need MP MP Multi Type and reference Boolean Boolean Semantics description TRUE indicates update required TRUE indicates update required TRUE indicates update required In this version, a maximum size of 4 of the list shall be applied and any items after the th 4 item in the list shall be ignored. Version
MP OP 1 to <maxSyste mCapabilit y>
Boolean
Name changed in REL-4 REL-4
>System specific capability update requirement
MP
Enumerated (GSM , GERAN Iu)
REL-5
Default value is: "UE radio capability FDD update requirement" = false "UE radio capability 3.84 Mcps TDD update requirement" = false "UE radio capability 1.28 Mcps TDD update requirement" = false "System specific capability update requirement" not present.
10.3.3.3
Cell update cause
Indicates the cause for cell update.
3GPP
Release 6 Information Element/Group name Cell update cause Need MP
515 Multi
3GPP TS 25.331 V6.23.0 (2009-09) Type and reference Enumerated (cell reselection, periodical cell update, uplink data transmission, paging response, re-entered service area, radio link failure, RLC unrecoverable error, MBMS reception, MBMS ptp RB request) Semantics description One spare value is needed. Version
REL-6
10.3.3.4
Ciphering Algorithm
Need MP Multi Type and reference Enumerated (UEA0, UEA1) Semantics description
Information Element/Group name Ciphering algorithm
10.3.3.5
Ciphering mode info
This information element contains the ciphering specific security mode control information.
Information Element/Group name Ciphering mode command Ciphering algorithm Need MP MP Multi Type and reference Enumerated (start/restart) Ciphering algorithm 10.3.3.4 Activation time 10.3.3.1 RB activation time info, 10.3.4.13 Semantics description
Ciphering activation time for DPCH
OP
Radio bearer downlink ciphering activation time info
OP
Used for radio bearers mapped on RLC-TM. Only applicable if the UE is already in CELL_DCH state Used for radio bearers mapped on RLC-AM or RLCUM The UTRAN should not include this IE in a message other than a SECURITY MODE COMMAND
10.3.3.6
A coefficient in the formula to count the paging occasions to be used by a specific UE (specified in [4]) .
Information Element/Group name CN domain specific DRX cycle length coefficient Need MP Multi Type and reference Integer(6...9) Semantics description Refers to 'k' in the formula as specified in [4], Discontinuous reception
10.3.3.7
Void
3GPP
Release 6
516
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.8
C-RNTI
The cell RNTI (C-RNTI) identifies a UE having a RRC connection within a cell.
Information Element/Group name C-RNTI Need MP Multi Type and reference bit string(16) Semantics description
10.3.3.9
Void
10.3.3.9a
DSCH-RNTI
In TDD, the DSCH-RNTI identifies a UE in CELL_DCH or CELL_FACH using a DSCH or USCH within the cell.
Information Element/Group name DSCH-RNTI Need MP Multi Type and reference bit string(16) Semantics description
10.3.3.10
Void
10.3.3.10a
E-RNTI
Need MP Multi Type and reference bit string(16) Semantics description Version REL-6
Information Element/Group name E-RNTI
3GPP
Release 6
517
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.11
Establishment cause
Cause for an RRC connection establishment request.

Information Element/Group name Establishment cause Need MP Multi Type and reference Enumerated( Originating Conversatio nal Call, Originating Streaming Call, Originating Interactive Call, Originating Background Call, Originating Subscribed traffic Call, Terminating Conversatio nal Call, Terminating Streaming Call, Terminating Interactive Call, Terminating Background Call, Emergency Call, Inter-RAT cell reselection, Inter-RAT cell change order, Registration, Detach, Originating High Priority Signalling, Originating Low Priority Signalling, Call reestablishme nt, Terminating High Priority Signalling, Terminating Low Priority Signalling, Terminating cause unknown, MBMS reception, MBMS ptp RB request) Semantics description Eleven spare values are needed.
3GPP
Release 6
518
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.12

Need MP Multi Type and reference Enumerated( 2times, 4times, 8times, 16times, 32times, 64times, 128times, 256times) Semantics description
Information Element/Group name Expiration Time Factor
10.3.3.13
Failure cause
Cause for failure to perform the requested procedure.

Information Element/Group name Failure cause Need MP Multi Type and reference Enumerated (configuratio n unsupported, physical channel failure, incompatible simultaneou s reconfigurati on, protocol error, compressed mode runtime error, cell update occurred, invalid configuration , configuration incomplete, unsupported measuremen t, MBMS session already received correctly, lower priority MBMS service) Semantics description Five spare values are needed.
10.3.3.14
Failure cause and error information
Cause for failure to perform the requested procedure.

Information Element/Group name Failure cause Need MP Multi Type and reference Failure cause 10.3.3.13 Semantics description
3GPP
Release 6 Protocol error information CV-ProtErr
519 Protocol error information 10.3.8.12 TGPSI 10.3.6.82
3GPP TS 25.331 V6.23.0 (2009-09)
Deleted TGPSI
CVCompMod eErr
Condition ProtErr
CompModeErr
Explanation The IE is mandatory present if the IE "Failure cause" has the value "Protocol error"; otherwise it is not needed in the message. The IE is mandatory present if the IE "Failure cause" has the value " Compressed mode runtime error"; otherwise it is not needed in the message
10.3.3.14o
Group release information
Contains addressing information to perform a release of a group of RRC connections.

Information Element/Group name U-RNTI group Need MP Multi Type and reference U-RNTI group 10.3.3.47a Semantics description Version REL-5
10.3.3.14a
H-RNTI
The H-RNTI identifies an UE having a HS-PDSCH assignment within a cell.

Information Element/Group name H-RNTI Need MP Multi Type and reference bit string(16) Semantics description Version REL-5
10.3.3.15
Initial UE identity
This information element identifies the UE at a request of an RRC connection.

Information Element/Group name CHOICE UE id type >IMSI (GSM-MAP) Need MP IMSI (GSMMAP) 10.3.1.5 MP TMSI (GSMMAP) 10.3.1.17 Location Area Identification 10.3.1.7 P-TMSI (GSM-MAP) 10.3.1.13 Routing Area Identification 10.3.1.16 IMEI 10.3.1.4 Multi Type and reference Semantics description
>TMSI and LAI (GSM-MAP) >>TMSI (GSM-MAP)
>>LAI (GSM-MAP)
MP
>P-TMSI and RAI (GSM-MAP) >>P-TMSI (GSM-MAP)
MP
>>RAI (GSM-MAP)
MP
>IMEI
3GPP
Release 6 >ESN (DS-41) >IMSI (DS-41) >IMSI and ESN (DS-41) >>IMSI (DS-41) >>ESN (DS-41) >TMSI (DS-41)
520 Bit string (SIZE (32)) Octet string (SIZE (5..7)) MP MP Octet string (SIZE (5..7)) Bit string (SIZE (32)) Octet string (SIZE (2..17))
3GPP TS 25.331 V6.23.0 (2009-09) TIA/EIA/IS-2000-4 TIA/EIA/IS-2000-4 TIA/EIA/IS-2000-4 TIA/EIA/IS-2000-4 TIA/EIA/IS-2000-4 TIA/EIA/IS-2000-4 Although normally upto 12 digits are used for this IE, a bigger length is used to support future extension.
10.3.3.16
The Integrity check info contains the RRC message sequence number needed in the calculation of XMAC-I [40] and the calculated MAC-I.
Information Element/Group name Message authentication code Need MP Multi Type and reference bit string(32) Semantics description MAC-I [40]. The first/leftmost bit of the bit string contains the most significant bit of the MAC-I. The 27 MSB of the IE shall be set to zero and the 5 LSB of the IE shall be set to the value of the IE "RB identity" for the used signalling radio bearer when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm. The local RRC hyper frame number (RRC HFN) is concatenated with the RRC message sequence number to form the input parameter COUNT-I for the integrity protection algorithm. The IE value shall be set to zero when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm.
RRC Message sequence number
MP
Integer (0..15)
10.3.3.17
Integrity protection activation info
This IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers.
3GPP
Release 6 Information Element/Group name RRC message sequence number list Need MP
521 Multi 4 to 5 Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The RRC sequence number when a new integrity protection configuration shall be applied, for signalling radio bearers in the order RB0, RB1, RB2, RB3, RB4. The value for RB1 shall be ignored if this IE was included in a RRC message sent on RB1. The value for RB2 shall be ignored if this IE was included in a RRC message sent on RB2.
>RRC message sequence number
MP
Integer (0.. 15)
10.3.3.18
Integrity protection Algorithm

Need MP Multi Type and reference Enumerated (UIA1) Semantics description
Information Element/Group name Integrity protection algorithm
10.3.3.19

Need MP CV-modify Multi Type and reference Enumerated( start, modify) Integrity protection activation info 10.3.3.17 Integrity protection algorithm 10.3.3.18 Bit string(32) Semantics description
Information Element/Group name Integrity protection mode command Downlink integrity protection activation info
Integrity protection algorithm
OP
Integrity protection initialisation number
CV-start
FRESH [40]. The first/leftmost bit of the bit string contains the most significant bit of the FRESH.
Condition Start
Modify
Explanation The IE is mandatory present if the IE "Integrity protection mode command" has the value "start ", otherwise it is not needed in the message. The IE is mandatory present if the IE "Integrity protection mode command" has the value "modify" and not needed otherwise.
10.3.3.19a
Void
3GPP
Release 6
522
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.20
Void
10.3.3.21
Measurement capability
Need Multi Type and reference Semantics description Version
Information Element/Group name Need for downlink compressed mode FDD measurements
MP
Boolean
3.84 Mcps TDD measurements
CV3.84_Mcps _tdd_sup
Boolean
Boolean
TRUE means that the UE requires DL compressed mode in order to perform measurements on FDD TRUE means that the UE requires DL compressed mode in order to perform measurements on 3.84 Mcps TDD TRUE means that the UE requires DL compressed mode in order to perform measurements on 1.28 Mcps TDD
Name changed in REL-4
REL-4
GSM measurements >GSM 900
CVgsm_sup MP
Boolean
>DCS 1800
MP
Boolean
>GSM 1900
MP
Boolean
Multi-carrier measurement
CVmc_sup
Boolean
TRUE means that the UE requires DL compressed mode in order to perform measurements on GSM 900 TRUE means that the UE requires DL compressed mode in order to perform measurements on DCS 1800 TRUE means that the UE requires DL compressed mode in order to perform measurements on GSM 1900 TRUE means that the UE requires DL compressed mode in order to perform measurements on multi-carrier
Need for uplink compressed mode FDD measurements
MP
Boolean
TRUE means that the UE requires UL compressed mode in order to
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description perform measurements on FDD TRUE means that the UE requires UL compressed mode in order to perform measurements on 3.84 Mcps TDD TRUE means that the UE requires DL compressed mode in order to perform measurements on 1.28 Mcps TDD Version
Boolean
Name changed in REL-4
Boolean
REL-4
GSM measurements >GSM 900
CVgsm_sup MP
Boolean
>DCS 1800
MP
Boolean
>GSM 1900
MP
Boolean
CVmc_sup
Boolean
TRUE means that the UE requires UL compressed mode in order to perform measurements on GSM 900 TRUE means that the UE requires UL compressed mode in order to perform measurements on DCS 1800 TRUE means that the UE requires UL compressed mode in order to perform measurements on GSM 1900 TRUE means that the UE requires UL compressed mode in order to perform measurements on multi-carrier
Condition 3.84_Mcps_tdd_sup
1.28_Mcps_tdd_sup
gsm_sup
mc_sup
Explanation The IE is mandatory present if an IE "TDD RF capability" is present with the IE "Chip rate capability" set to "3.84 Mcps". Otherwise this field is not needed in the message. The IE is mandatory present if an IE "TDD RF capability" is present with the IE "Chip rate capability" set to "1.28 Mcps". Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Inter-RAT UE radio access capability" indicates support for GSM900, GSM1800 and/or GSM1900. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Support of multi-carrier" has the value TRUE. Otherwise this field is not needed in the message.
3GPP
Release 6
524
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.21a
Measurement capability extension
This IE may be used to replace the measurement capability information provided within IE "Measurement capability".
Information Element/Group name FDD measurements Need MP Multi 1 to <maxFre qBands FDD> Enumerat ed(Band I, Band II, Type and reference Semantics description The network should ignore the entry that includes the extension indicator. The default value is the same as indicated in the IE "Frequency band" included in the IE " UE radio access capability extension". Band numbering is defined in [21]. The default value is the same as R99, if the IE FDD Frequency band 2 below is not included. The default value is the same as the IE FDD Frequency band 2, if the IE FDD Frequency band 2 is included. The setting of the value extension indicatior by the UE is not specified in the specification. The default value is the same as indicated in the IE "Frequency band 2" included in the IE " UE radio access capability extension"., if the IE FDD Frequency band above is not included. The default value is the same as the IE FDD Frequency band, if the IE FDD Frequency band is included. The setting of the value extension indicatior by the UE is not specified in the specification. Thirteen spare values are needed TRUE means that the UE requires DL compressed mode in order to perform measurements on the FDD frequency band indicated by the IE "FDD Frequency band" REL-5 REL-6 Version
>FDD Frequency band
MD
Band III, Band VI, Band IV, Band V, Band VII, extension indicator)
>FDD Frequency band 2
MD
Enumerat ed(Band VIII, Band IX, extension Indicator)
REL-6
>Need for DL compressed mode
MP
Boolean
3GPP
Release 6 Information Element/Group name >Need for UL compressed mode Need MP Multi
525 Type and reference Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE means that the UE requires UL compressed mode in order to perform measurements on the FDD frequency band indicated by the IE "FDD Frequency band" Version
TDD measurements
CVtdd_sup
1 to <maxFre qBands TDD> Enumerat ed(a, b, c) Boolean
>TDD Frequency band >Need for DL compressed mode
MP MP
>Need for UL compressed mode
MP
Boolean
TRUE means that the UE requires DL compressed mode in order to perform measurements on TDD frequency band indicated by the IE "TDD Frequency band" TRUE means that the UE requires UL compressed mode in order to perform measurements on TDD frequency band indicated by the IE "TDD Frequency band"
GSM measurements
CVgsm_su p MP
1 to <maxFre qBands GSM> Enumerat ed(GSM4 50, GSM480, GSM850, GSM900 P, GSM900 E, GSM1800 , GSM1900 ) Boolean as defined in [45]. Nine spare values are needed.
>GSM Frequency band
>Need for DL compressed mode
MP
MP
Boolean
TRUE means that the UE requires DL compressed mode in order to perform measurements on GSM frequency band indicated by the IE "GSM Frequency band" TRUE means that the UE requires UL compressed mode in order to perform measurements on GSM frequency band indicated by the IE "GSM Frequency band"
CVmc_sup
3GPP
Release 6 Information Element/Group name >Need for DL compressed mode Need MP Multi
526 Type and reference Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE means that the UE requires DL compressed mode in order to perform measurements on multicarrier TRUE means that the UE requires UL compressed mode in order to perform measurements on multicarrier Version
MP
Boolean
Condition tdd_sup
gsm_sup
mc_sup
Explanation The IE is mandatory present if the IE "Multi-mode capability" has the value "TDD" or "FDD/TDD". Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Support of GSM" has the value TRUE. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Support of multi-carrier" has the value TRUE. Otherwise this field is not needed in the message.
10.3.3.22
Paging cause
Cause for a CN originated page.

Information Element/Group name Paging cause Need MP Multi Type and reference Enumerated( Terminating Conversatio nal Call, Terminating Streaming Call, Terminating Interactive Call, Terminating Background Call, Terminating High Priority Signalling, Terminating Low Priority Signalling, Terminating cause unknown ) Semantics description One spare value is needed.
10.3.3.23
Paging record
Need MP Multi Type and reference Semantics description Version
Information Element/Group name CHOICE Used paging identity >CN identity
3GPP
Release 6 Information Element/Group name >>Paging cause Need MP Multi
527 Type and reference Paging cause 10.3.3.22 CN domain identity 10.3.1.1
MP
>>CHOICE UE Identity >>>IMSI (GSM-MAP)
MP IMSI (GSMMAP) 10.3.1.5 TMSI (GSMMAP) 10.3.1.17 P-TMSI (GSMMAP) 10.3.1.13 TIA/EIA/I S-2000-4 TIA/EIA/I S-2000-4
Three spare values are needed.
>>>TMSI (GSM-MAP)
>>>P-TMSI (GSM-MAP)
>>>IMSI (DS-41) >>>TMSI (DS-41) >UTRAN single UE identity >>U-RNTI >>CN originated page to connected mode UE >>>Paging cause
MP OP MP
U-RNTI 10.3.3.47
>>>CN domain identity
MP
>>>Paging record type identifier
MP
Paging cause 10.3.3.22 CN domain identity 10.3.1.1 Paging record type identifier 10.3.1.10
3GPP
Release 6 Information Element/Group name >>RRC connection release information Need MP Multi
528 Type and reference RRC connectio n release informatio n 10.3.3.35 o
>UTRAN group identity
1 to <maxUR NTIgrou p> MP RRC connectio n release informatio n 10.3.3.35 o Group release informatio n 10.3.3.14 o
REL-5
>>RRC connection release information
REL-5
>>Group release information
MP
REL-5
Condition CHOICE Used paging identity CN identity UTRAN single UE identity UTRAN group identity
Explanation Condition under which the given used paging identity is chosen For CN originating pages (for idle mode UEs) For UTRAN originating pages (for connected mode UEs), addressing a single UE For UTRAN originating pages (for connected mode UEs), addressing a group of UEs
10.3.3.24
PDCP capability
Indicates which algorithms and which value range of their parameters are supported by the UE.
Information Element/Group name Support for lossless SRNS relocation Support for lossless DL RLC PDU size change Support for RFC2507 >Max HC context space Need MP CVnot_iRAT_ HoInfo2 MP MP Multi Type and reference Boolean Boolean Semantics description TRUE means supported TRUE means supported Default value is FALSE TRUE means supported Version
REL-5
Boolean Integer(1024 , 2048, 4096, 8192, 16384, 32768, 65536, 131072) Boolean
Note 1
REL-5
Support for RFC 3095
>Maximum number of ROHC context sessions
CVnot_iRAT_ HoInfo MD
TRUE means supported Default value is 16.
REL-4
Integer( 2, 4, 8, 12, 16, 24, 32, 48, 64, 128, 256, 512, 1024, 16384)
REL-4
3GPP
Release 6 Information Element/Group name >Reverse decompression depth Need
529 Multi Type and reference Integer (0..65535)
3GPP TS 25.331 V6.23.0 (2009-09)
Semantics Version description MD Default value is 0 REL-4 (reverse decompression is not supported). >Support for RFC 3095 context MP Boolean TRUE means REL-5 relocation supported Note 1: The IE "Max HC context space" values 16384, 32768, 65536 and 131072 are not used in the INTER RAT HANDOVER INFO message.
Condition not_iRAT_HoInfo not_iRAT_HoInfo2
Explanation The IE is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is mandatory present. The IE is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is mandatory default.
10.3.3.25
Physical channel capability

Need Multi Type and Reference Semantics description Version
Information Element/Group name Downlink physical channel capability information elements FDD downlink physical channel capability >Max no DPCH codes
CHfdd_req_su p MP
Integer (1..8)
>Max no physical channel bits received
MP
>Support for SF 512 and 80 ms TTI for DPCH >CHOICE Support of HSPDSCH >>Supported >>>HS-DSCH physical layer category >>Unsupported 3.84 Mcps TDD downlink physical channel capability
MP CVnot_iRAT_ HoInfo MP
Integer (1200, 2400, 3600, 4800, 7200, 9600, 14400, 19200, 28800, 38400, 48000, 57600, 67200, 76800) Boolean
Maximum number of DPCH codes to be simultaneously received Maximum number of physical channel bits received in any 10 ms interval (DPCH, SCCPCH)
TRUE means supported REL-5
Integer (1..64)
As defined in [35] (no data)
REL-5 REL-5 REL-5 Name changed in REL-4
>Maximum number of timeslots per frame >Maximum number of physical channels per frame >Minimum SF >Support of PDSCH >CHOICE Support of HSPDSCH
CH3.84_Mcps _tdd_req_s up MP MP MP MP CVnot_iRAT_
Integer (1..14) Integer (5..224) Integer (1, 16) Boolean
3GPP
Release 6 Information Element/Group name >>Supported >>>HS-DSCH physical layer category >>Unsupported >Maximum number of physical channels per timeslot 1.28 Mcps TDD downlink physical channel capability Need HoInfo MP
As defined in [35]. (no data)
REL-5 REL-5 REL-5
MP CH1.28_Mcps _tdd_req_s up MP MP MP MP CVnot_iRAT_ HoInfo MP
REL-4
>Maximum number of timeslots per subframe >Maximum number of physical channels per subframe >Minimum SF >Support of PDSCH >CHOICE Support of HSPDSCH >>Supported >>>HS-DSCH physical layer category >>Unsupported >Maximum number of physical channels per timeslot >Support of 8PSK Uplink physical channel capability information elements FDD uplink physical channel capability >Maximum number of DPDCH bits transmitted per 10 ms
Integer (1..6) Integer (1..96) Integer (1, 16) Boolean
REL-4 REL-4 REL-4 TRUE means supported REL-4 REL-5
Integer (1..64) Integer (1..16) Boolean
As defined in [35] (no data)
REL-5 REL-5 REL-5 REL-4 REL-4
MP MP
TRUE means supported
CHfdd_req_su p MP
Integer (600, 1200, 2400, 4800. 9600, 19200. 28800, 38400, 48000, 57600) REL-6
>CHOICE Support of E-DCH
CVnot_iRAT_ HoInfo MP Integer (1..16) As defined in [35] (no data) CH3.84_Mcps _tdd_req_s up MP MP MP MP CH1.28_Mcps
>>Supported >>>E-DCH physical layer category >>Unsupported 3.84 Mcps TDD uplink physical channel capability
REL-6 REL-6 REL-6 Name changed in REL-4
>Maximum Number of timeslots per frame >Maximum number of physical channels per timeslot >Minimum SF >Support of PUSCH 1.28 Mcps TDD uplink physical channel capability
Integer (1..14) Integer (1, 2) Integer (1, 2, 4, 8) Boolean
3GPP
Release 6 Information Element/Group name Need _tdd_req_s up MP MP MP
>Maximum Number of timeslots per subframe >Maximum number of physical channels per timeslot >Minimum SF
>Support of PUSCH >Support of 8PSK
MP MP
Integer (1..6) Integer (1, 2) Integer (1, 2, 4, 8, 16) Boolean Boolean
REL-4 REL-4 REL-4
TRUE means supported TRUE means supported
REL-4 REL-4
Condition 3.84_Mcps_tdd_req_sup
1.28_Mcps_tdd_req_sup
fdd_req_sup
not_iRAT_HoInfo
not_iRAT_HoInfo
Explanation The IE is mandatory present if the IE "TDD RF capability" is present with the IE "Chip rate capability" set to "3.84 Mcps" and a 3.84 Mcps TDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "TDD RF capability" is present with the IE "Chip rate capability" set to "1.28 Mcps" and a 1.28 Mcps TDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Multi-mode capability" has the value "FDD" or "FDD/TDD" and a FDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. The CHOICE Support of HS-PDSCH is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is mandatory present. The CHOICE Support of E-DCH is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is mandatory present.
10.3.3.26
Protocol error cause
This IE indicates the cause for a message or information that was not comprehended.
3GPP
Release 6 Information Element/Group name Protocol error cause Need MP
532 Multi Type and reference Enumerated (ASN.1 violation or encoding error, Message type nonexistent or not implemented , Message not compatible with receiver state, Information element value not comprehend ed, Information element missing, Message extension not comprehend ed)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Two spare values are needed.
10.3.3.27
This IE indicates whether a message was transmitted due to a protocol error or not.
Information Element/Group name Protocol error indicator Need MP Multi Type and Reference Boolean Semantics description TRUE means a protocol error occurred. FALSE means a protocol error did not occur.
10.3.3.28
RB timer indicator
This IE is used to indicate to UTRAN if the timers T314 or T315 has expired in the UE.
Information Element/Group name T314 expired Need MP Multi Type and reference Boolean Semantics description TRUE means that the timer has expired or the stored value is zero. FALSE means that the timer has not expired. TRUE means that the timer has expired or the stored value is zero. FALSE means that the timer has not expired.
T315 expired
MP
Boolean
10.3.3.29
Redirection info
This IE is used to redirect the UE to another frequency or other system. With the Release 6 version a list of cells may be provided to the UE, where cell selection shall be started.
3GPP
Release 6 Information Element/Group name CHOICE Redirection Information >Frequency info Need MP Multi
>Inter-RAT info
Frequenc y info 10.3.6.36 Inter-RAT info 10.3.7.25
10.3.3.30
Re-establishment timer
This information element indicates which timer to associate with RAB.

Information Element/Group name Re-establishment timer Need MP Multi Type and reference Enumerated( useT314, useT315) Semantics description
10.3.3.31
Rejection cause
Cause for rejection of RRC connection establishment request.

Information Element/Group name Rejection cause Need MP Multi Type and reference Enumerated( congestion, unspecified) Semantics description
10.3.3.32
Release cause
Cause for release of RRC connection.

Information Element/Group name Release cause Need MP Multi Type and reference Enumerated (normal event, unspecified, pre-emptive release, congestion, reestablishme nt reject, user inactivity), directed signalling connection reestablishme nt) Semantics description One spare value is needed.
3GPP
Release 6
534
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.32a
RF Capability Compressed
Need MP MP 1..<maxf reqband sFDD> 1..<maxf reqband sFDDext> Enumerated (not supported, default TxRx separation) TX/RX frequency separation capability for the supported frequency band(s). Default is the TX/RX frequency separation defined in [21] for each frequency band. Two spare values are needed. Multi Type and reference Semantics description Version REL-5 REL-5 REL-5
Information Element/Group name CHOICE FDD >Supported >>RF capability band FDD list Compressed
REL-6
>>>RF Capability Band FDD Compressed
MP
REL-5
>Not supported CHOICE TDD-3.84Mcps >Supported >>Radio Frequency Band TDD List >Not supported CHOICE TDD-1.28Mcps >Supported >>Radio Frequency Band TDD List >Not supported
NULL MP MP Enumerated (a, b, c, a+b, a+c, b+c, a+b+c) NULL As defined in [22]. One spare value needed
MP MP Enumerated (a, b, c, a+b, a+c, b+c, a+b+c) NULL As defined in [22]. One spare value needed
REL-5
10.3.3.33
RF capability FDD
Need MP MP Multi Type and Reference Enumerated( 1..4) Enumerated( default TxRx separation) Semantics description As defined in [21] Default is the TX/RX frequency separation defined in [21] for each frequency band. Two spare values are needed. Version
Information Element/Group name UE power class Tx/Rx frequency separation
10.3.3.33a
RF capability FDD extension

Need MP MP Multi Type and Reference Enumerated( 1..4) Enumerated( default TxRx separation) Semantics description As defined in [21]. Four spare values are needed Default is the TX/RX frequency separation defined in [21] for each frequency band. Two spare values are needed.
Information Element/Group name UE power class extension Tx/Rx frequency separation
3GPP
Release 6
535
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.33b
RF capability TDD
Need MP MP Multi Type and Reference Enumerated (1..4) Enumerated( a, b, c, a+b, a+c, b+c, a+b+c) Enumerated( 3.84Mcps,1. 28Mcps) Semantics description as defined in [22] as defined in [22]. One spare value needed.
Information Element/Group name UE power class Radio frequency bands
Chip rate capability
MP
as defined in [22]
10.3.3.33c
RF capability TDD 1.28 Mcps

Need MP Multi Type and Reference Enumerated( a, b, c, a+b, a+c, b+c, a+b+c) Semantics description as defined in [22]. One spare value needed.
Information Element/Group name Radio frequency bands
10.3.3.34
RLC capability
Need Multi Type and Referenc e Integer (10, 50, 100, 150, 500, 1000, 200, 300, 400, 750) Integer(20 47,4095) Semantics description Version
Information Element/Group name Total RLC AM buffer size
MP
Total receiving and transmitting RLC AM buffer and MAC-hs reordering buffer capability in kBytes. Note 1. Maximum supported RLC TX and RX window in UE
REL-5
Maximum RLC AM Window Size Maximum number of AM entities Note 1:
MP
Integer (4,5,6,8,1 6,30) The IE "Total RLC AM buffer size" values 200, 300, 400 and 750 are not used in the INTER RAT HANDOVER INFO message.
MP
10.3.3.35
RLC re-establish indicator
This IE is used to re-configure AM RLC on c-plane and u-plane.

Information Element/Group name RLC re-establish indicator Need MP Multi Type and reference Boolean Semantics description TRUE means re-establish required FALSE means re-establish not required
10.3.3.35o
RRC connection release information
Indicates whether the UE shall perform a release of the RRC connection.
3GPP
Release 6 Information Element/Group name CHOICE Release indicator >No release >Release >>Release cause Need MD
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Default value is No release Version REL-5 REL-5 REL-5 REL-5
MP
Release cause 10.3.3.32
10.3.3.35a
RRC State Indicator
Indicates to a UE the RRC state to be entered.

Information Element/Group name RRC State indicator Need MP Multi Type and reference Enumerated( CELL_DCH, CELL_FACH , CELL_PCH, URA_PCH) Semantics description
10.3.3.36
This IE contains an identification of the RRC procedure transaction local for the type of the message this IE was included within.
Information Element/Group name CHOICE RRC Tr Id type >Normal >>RRC transaction identifier >Extended >>RRC transaction identifier Need MP MP Integer (0..3) Integer (0..15) REL-5 REL-5 Multi Type and reference Semantics description Version REL-5
MP
CHOICE RRC Tr Id type Normal Extended
Condition under which the given RRC Tr Id type is chosen All cases where the RRC Tr Id type: Extended is not chosen. Optional in the MEASUREMENT CONTROL message. Mandatory in the MEASUREMENT CONTROL FAILURE message.
10.3.3.37
Security capability
Need MP MP MP MP Multi Type and reference Boolean Boolean Boolean Semantics description
Information Element/Group name Ciphering algorithm capability >UEA0 >UEA1 >Spare
14
Shall be set to FALSE by UEs complying with this version of the protocol.
Integrity protection algorithm capability >UIA1 >Spare
MP MP MP 15 Boolean Boolean The value TRUE means that UIA1, Kasumi, is supported Shall be set to FALSE by UEs complying with this version of the protocol.
3GPP
Release 6
537
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.38
START
There is a START value per CN domain. The START is used to initialise the 20 MSBs of all hyper frame numbers (MAC-d HFN, RLC UM HFN, RLC AM HFN, RRC HFN) for a CN domain.
Information Element/Group name START Need MP Multi Type and Reference Bit string (20) Semantics description START [40]. The first/leftmost bit of the bit string contains the most significant bit of the START.
10.3.3.39
Void
10.3.3.40
Transport channel capability

Need Multi Type and Reference Semantics description
Information Element/Group name Downlink transport channel capability information elements Max no of bits received
MP
Max convolutionally coded bits received
MP
Max turbo coded bits received
CVturbo_dec_ sup
Maximum number of simultaneous transport channels Maximum number of simultaneous CCTrCH Max no of received transport blocks
MP MP MP
Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(4, 8, 16, 32) Integer (1..8) Integer(4, 8, 16, 32, 48, 64, 96, 128, 256, 512) Integer(16, 32, 48, 64, 96, 128, 256, 512, 1024) Integer(32, 64, 128, 256, 512, 1024)
Maximum sum of number of bits of all transport blocks received at an arbitrary time instant
Maximum sum of number of bits of all convolutionally coded transport blocks received at an arbitrary time instant
Maximum sum of number of bits of all turbo coded transport blocks received at an arbitrary time instant
Maximum total number of transport blocks received within TTIs that end at within the same 10ms interval
Maximum number of TFC
MP
Maximum number of TF
MP
3GPP
Release 6 Information Element/Group name Support for turbo decoding Uplink transport channel capability information elements Max no of bits transmitted Need MP
538 Multi Type and Reference Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE means supported
MP
Max convolutionally coded bits transmitted
MP
Max turbo coded bits transmitted
CVturbo_enc_ sup
Maximum number of simultaneous transport channels Maximum number of simultaneous CCTrCH of DCH type Max no of transmitted transport blocks
MP CHtdd_req_su p MP
Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840) Integer(4, 8, 16, 32) Integer (1..8)
Maximum sum of number of bits of all transport blocks transmitted at an arbitrary time instant
Maximum sum of number of bits of all convolutionally coded transport blocks transmitted at an arbitrary time instant
Maximum sum of number of bits of all turbo coded transport blocks transmitted at an arbitrary time instant
Maximum number of TFC
MP
Maximum number of TF
MP
Support for turbo encoding
MP
Integer(4, 8, 16, 32, 48, 64, 96, 128, 256, 512) Integer(16, 32, 48, 64, 96, 128, 256, 512, 1024) Integer(32, 64, 128, 256, 512, 1024) Boolean
Maximum total number of transport blocks transmitted within TTIs that start at the same time
TRUE means supported
Condition turbo_dec_sup
turbo_enc_sup
tdd_req_sup
Explanation The IE is mandatory present if the IE "Support of turbo decoding" = True. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Support of turbo encoding" = True. Otherwise this field is not needed in the message. The IE is mandatory present if the IE "Multi-mode capability" has the value "TDD" or "FDD/TDD" and a TDD capability update has been requested in a previous message. Otherwise this field is not needed in the message.
3GPP
Release 6
539
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.41
UE multi-mode/multi-RAT capability
Need Multi Type and Referenc e Boolean Boolean Enumerat ed (TDD, FDD, FDD/TDD ) Boolean Semantics description Version
Information Element/Group name Multi-RAT capability Support of GSM Support of multi-carrier Multi-mode capability
MP MP MP
Support of UTRAN to GERAN NACC
Support of Handover to GAN
CVnot_iRA T_HoInf o OP
REL-5
Support of Inter-RAT PS handover
CVnot_iRA T_HoInf o2
Enumerat ed ( DoesSup portHand overToGA N) Enumerat ed (DoesSup portInterRAT-PSHandover )
Absence of this IE means that the UE does not support Handover to GAN. Absence of this IE means that the UE does not support InterRAT PS Handover
REL-6
REL-6
Condition not_iRAT_HoInfo CV-not_iRAT_HoInfo2
Explanation The IE is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is mandatory present. The IE is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is optional.
NOTE:
The UE sets the capability of Inter-RAT PS Handover (by means of the IE "Support of Inter-RAT PS handover") to the same value as the corresponding GERAN capability in [5].
10.3.3.42

Need MP Multi Type and reference Enumerated( R99) Semantics description Indicates the release of the UE according to [35]. The IE also indicates the release of the RRC transfer syntax supported by the UE.. 13 spare values are needed. Version
Information Element/Group name Access stratum release indicator
CVnot_rrc_co nnectionSe tupComple te
Enumerated( REL-4, REL-5 REL-6)
DL capability with simultaneous HS-DSCH configuration
CVnot_iRAT_ HoInfo
Enumerated( 32kbps, 64kbps, 128kbps,
3GPP
Release 6 Information Element/Group name PDCP capability Need
540 Multi Type and reference 384kbps) PDCP capability 10.3.3.24 RLC capability 10.3.3.34 Transport channel capability 10.3.3.40 RF capability FDD 10.3.3.33 RF capability TDD 10.3.3.33b
MP
RLC capability
MP
Transport channel capability
MP
RF capability FDD
OP
RF capability TDD
OP
1 to 2 RF capability TDD 1.28 Mcps CViRAT_HoIn fo MP RF capability TDD 1.28 Mcps 10.3.3.33c Physical channel capability 10.3.3.25 UE multimode/multiRAT capability 10.3.3.41 Security capability 10.3.3.37 UE positioning capability 10.3.3.45 Measuremen t capability 10.3.3.21 Enumerated (DoesNotBe nefitFromBat teryConsum ptionOptimis ation)
One "TDD RF capability" entity shall be included for every Chip rate capability supported. Note 1 Note 1
REL-4 REL-4
Physical channel capability
UE multi-mode/multi-RAT capability
MP
Security capability
MP
UE positioning capability
MP
Measurement capability
Device type
CVfdd_req_su p MD
Absence of this value means that the device does benefit from NWbased battery consumption optimisation. UE may set the value to DoesNotBenefitFr omBatteryConsu mptionOptimisatio n when it does not foresee to particularly benefit from NW-based The IE shall be set to TRUE when System Information Block type 11bis is
REL-6
Support for System Information Block type 11bis
OP
Enumerated (True)
REL-6
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description supported by the UE. Absence of this information element indicates that System Information Block type 11bis is not supported The IE shall be set to TRUE when F-DPCH is fully supported by the UE. Version
Support for F-DPCH
OP
Enumerated (True)
REL-6
Absence of this information element indicates that F-DPCH is not fully supported Note 1: The second entity of the "RF capability TDD" is not needed in the INTER RAT HANDOVER INFO message: if both TDD 3.84 Mcps and TDD 1.28 Mcps are supported, the "RF capability TDD 1.28 Mcps" entity shall be used for TDD 1.28 Mcps; the "UE power class" in the "RF capability TDD" entity shall apply for both chip rates.
Condition fdd_req_sup
not_rrc_connectionSetupComplete
not_iRAT_HoInfo iRAT_HoInfo
Explanation The IE is mandatory present if the IE "Multi-mode capability" has the value "FDD" or "FDD/TDD" and a FDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. The IE is not needed in the RRC CONNECTION SETUP COMPLETE message. Otherwise the IE is mandatory present. The IE is not needed in the INTER RAT HANDOVER INFO message. Otherwise, it is optional. The IE is optional in the INTER RAT HANDOVER INFO message. Otherwise, the IE is not needed.
10.3.3.42o

Need MP Multi Type and reference Enumerated( R99, REL-4, REL-5 REL-6) BOOLEAN RF capability compressed 10.3.3.32a Enumerated (True) Semantics description 13 spare values are needed Version REL-5
Information Element/Group name Access stratum release indicator
Total AM RLC buffer size exceeds 10 kByte RF capability compressed
MP MP
REL-6 REL-5 REL-5
Support for System Information Block type 11bis
OP
The IE shall be set to TRUE when System Information Block type 11bis is supported by the UE. Absence of this information element indicates that
REL-6
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description System Information Block type 11bis is not supported Version
10.3.3.42oa UE radio access capability comp 2

Information Element/Group name FDD physical channel capability for HS-PDSCH/E-DCH >DL capability with simultaneous HS-DSCH configuration Need OP OP Enumerated (32, 64, 128, 384) Unit: kbps. This IE is always required, but the need is set to OP to align with ASN.1 As defined in [35] Multi Type and reference Semantics description Version REL-6 REL-6
>HS-DSCH physical layer category >CHOICE Support of E-DCH >>Supported >>>E-DCH physical layer category >>Unsupported Support for F-DPCH
MP MP MP
Integer (1..64)
REL-6 REL-6 REL-6 REL-6 REL-6 REL-6
Integer (1..16)
As defined in [35] (no data) The IE shall be set to TRUE when FDPCH is fully supported by the UE. Absence of this information element indicates that F-DPCH is not fully supported
OP
Enumerated (True)
10.3.3.42a

Need MP Multi 1 to <maxFre qbandsF DD> Enumerat ed(Band I, Band II, Band III, Band VI, Band IV, Band V, Band VII, extension indicator) Enumerat ed(Band VIII, Band IX, extension Indicator) Type and reference Semantics description The network should ignore the entry that includes the extension indicator. Version
Information Element/Group name Frequency band specific capability list
>Frequency band
MP
The setting of the value extension indicatior by the UE is not specified in the specification.
REL-5 REL-6
>Frequency band 2
OP
This IE indicates the supported frequency bands Band VIII and beyond. The setting of the value extension indicatior by the UE is not specified in the specification. Thirteen spare values are needed
REL-6
3GPP
Release 6 Information Element/Group name >RF capability FDD extension Need MD Multi
543 Type and reference RF capability FDD extension 10.3.3.33 a Measure ment capability extension 10.3.3.21 a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description the default values are the same values as in the immediately preceding IE "RF capability FDD extension"; the first occurrence is MP Version
>Measurement capability extension
MP
10.3.3.42b
UE security information
Upon receiving a UE information request from another system, the UE shall indicate the requested security information. The UE security information includes the following RRC information.
Information Element/Group name UE information elements START-CS Need Multi Type and reference START 10.3.3.38 Semantics description
MP
START values to be used in this CN domain.
10.3.3.42c
Upon receiving a UE information request from another system, the UE shall indicate the requested security information. The UE security information includes the following RRC information.
Information Element/Group name START-PS Need MP Multi Type and reference START 10.3.3.38 Semantics description START values to be used in this CN domain. Version Rel-6
10.3.3.43
UE Timers and Constants in connected mode
This information element specifies timer- and constants values used by the UE in connected mode.
Information Element/Group name T301 Need MD Multi Type and reference Integer(10 0, 200 .. 2000 by step of 200, 3000, 4000, 6000, 8000) Integer(0.. 7) Semantics description Value in milliseconds. Default value is 2000. This IE should not be used by the UE in this release of the protocol. One spare value is needed. Version
N301
MD
T302
MD
Integer(10 0, 200... 2000 by step of 200, 3000,
Default value is 2. This IE should not be used by the UE in this release of the protocol. Value in milliseconds. Default value is 4000. One spare value is needed.
3GPP
544 Type and reference 4000, 6000, 8000) Integer(0.. 7) Integer(10 0, 200, 400, 1000, 2000) Integer(0.. 7) Integer(5, 10, 30, 60, 120, 360, 720, infinity) Integer(5, 10, 15, 20, 30, 40, 50) Integer(40 , 80, 160, 320) Integer(1 8) Integer(40 .. 320 by step of 40) Integer(0 .. 7) Integer(25 0 .. 2000 by step of 250) Integer (0..15)
N302 T304
MD MD
Default value is 3. Value in milliseconds. Default value is 2000. Three spare values are needed. Default value is 2.. Value in minutes. Default value is 30. Infinity means no update Value in seconds. Default value is 30. One spare value is needed. Value in milliseconds. Default value is 160. Value in seconds. Default value is 5. Value in milliseconds. Default value is 160.
N304 T305
MD MD
T307
MD
T308
MD
T309 T310
MD MD
N310 T311
MD MD
Default value is 4. Value in milliseconds. Default value is 2000.
T312
MD
N312
MD
T313 N313
MD MD
T314
MD
T315
MD
N315
MD
Integer (1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000) Integer (0..15) Integer (1, 2, 4, 10, 20, 50, 100, 200) Integer(0, 2, 4, 6, 8, 12, 16, 20) Integer (0,10, 30, 60, 180, 600, 1200, 1800) Integer (1, 2, 4, 10,
Value in seconds. Default value is 1. The value 0 is not used in this version of the specification. Default value is 1.
Value in seconds. Default value is 3. Default value is 20.
Value in seconds. Default value is 12.
Value in seconds. Default value is 180.
Default value is 1.
3GPP
545 Type and reference 20, 50, 100, 200, 400, 600, 800, 1000) Integer(0, 10, 20, 30, 40, 50, infinity)
T316
MD
Value in seconds. Default value is 30. One spare value is needed.
T317
MD Enumerat ed (infinity, infinity, infinity, infinity, infinity, infinity, infinity, infinity) Default value is infinity. All the values are changed to "infinity" in the Rel-5. REL-5
10.3.3.44
UE Timers and Constants in idle mode
This information element specifies timer- and constant values used by the UE in idle mode.
Information Element/Group name T300 Need MP Multi Type and reference Integer(100, 200... 2000 by step of 200, 3000, 4000, 6000, 8000) Integer(0..7) Semantics description Value in milliseconds. Default value is 1000. Use of Default is described in 10.2.48.8.4 and in 10.2.48.8.16.
N300
MP
T312
MP
Integer(0 .. 15)
N312
MP
Integer (1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000)
Default value is 3. Use of Default is described in 10.2.48.8.4 and in 10.2.48.8.16. Value in seconds. Default value is 1. Use of Default is described in 10.2.48.8.4 and in 10.2.48.8.16. The value 0 is not used in this version of the specification. Default value is 1. Use of Default is described in 10.2.48.8.4 and in 10.2.48.8.16.
3GPP
Release 6
546
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.3.45
UE positioning capability
Need MP Multi Type and reference Boolean Semantics description Defines if a UE can measure its location by some means unrelated to UTRAN TRUE means supported TRUE means supported Defines if the UE supports network based or UE based GPS methods.
Information Element/Group name Standalone location method(s) supported UE based OTDOA supported Network Assisted GPS support
MP MP
Support for GPS timing of cell frames measurement
MP
Boolean Enumerated ('Network based', 'UE based', 'Both', 'None') Boolean
Support for IPDL
MP
Boolean
Support for Rx-Tx time difference type2 measurement Support for UP assisted GPS measurement validity in CELL_PCH and URA_PCH states Support for SFN-SFN observed time difference type 2 measurement
MP CVGPSsuppo rted OP
Boolean Enumerated (true)
Defines if a UE has the capability to perform the UE GPS timing of cell frames measurement [7]. TRUE means capable Defines if a UE has the capability to use IPDL to enhance its 'SFN-SFN observed time difference type 2' measurement. TRUE means supported TRUE means supported
Enumerated (true)
Absence of this element means not supported and presence means supported.
Condition GPSsupported
Explanation This IE is mandatory present if the IE Network Assisted GPS support is set to 'Network based', 'UE based' or 'Both'. Otherwise, it is not needed.
10.3.3.46
URA update cause
Indicates the cause for s URA update.

Information Element/Group name URA update cause Need MP Multi Type and reference Enumerated( change of URA, periodic URA update) Semantics description One spare value is needed.
10.3.3.47
U-RNTI
The U-RNTI (UTRAN Radio Network Temporary Identity) is allocated to a UE having a RRC connection and identifies the UE within UTRAN.
3GPP
Release 6 Information Element/Group name SRNC identity Need MP
547 Multi Type and reference bit string(12)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The SRNC identity bits are numbered b20 to b31, where b20 is the least significant bit. The S-RNTI bits are numbered b0 to b19, where b0 is the least significant bit.
S-RNTI
MP
bit string(20)
10.3.3.47a
U-RNTI group
The U-RNTI group is used to identify a group of UEs having an RRC connection.
Information Element/Group name CHOICE group discrimimator >All >U-RNTI mask >>U-RNTI Need MP (no data) MP U-RNTI 10.3.3.47 The bits that are less significant than the bit position indicated by the U-RNTI bit mask index shall be ignored. Values b1 to b19 indicate bit positions in the SRNTI. Values b20 to b31 indicate bit positions in the SRNC identity. Multi Type and reference Semantics description Version REL-5 REL-5 REL-5 REL-5
>>U-RNTI bit mask index
MP
Enumerated( b1, b2,..b31)
REL-5
10.3.3.48
U-RNTI Short
The U-RNTI (UTRAN Radio Network Temporary Identity) is allocated to a UE having a RRC connection and identifies the UE within UTRAN.
Information Element/Group name SRNC identity Need MP Multi Type and reference bit string(12) Semantics description The SRNC identity bits are numbered b20 to b31, where b20 is the least significant bit. The S-RNTI 2 bits are numbered b0 to b9, where b0 is the least significant bit.
S-RNTI 2
MP
bit string(10)
10.3.3.49
A coefficient in the formula to count the paging occasions to be used by a specific UE (specified in [4]).
Information Element/Group name DRX cycle length coefficient Need MP Multi Type and reference Integer(3...9) Semantics description Refers to 'k' in the formula as specified in [4], Discontinuous reception
10.3.3.50
Wait time
Wait time defines the time period the UE has to wait before repeating the rejected procedure.
3GPP
Release 6 Information Element/Group name Wait time Need MP
548 Multi Type and reference Integer(0.. 15)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Wait time in seconds The value 0 indicates that repetition is not allowed.
10.3.3.51
UE Specific Behaviour Information 1 idle
This IE indicates the UE conformance typically for RRC connection establishment from idle mode.
Information Element/Group name UE Specific Behaviour Information 1 idle Need MP Multi Type and Reference bit string(4) Semantics description
10.3.3.52
This IE indicates the UE conformance typically for RRC connection establishment from another RAT.
Information Element/Group name UE Specific Behaviour Information 1 interRAT Need MP Multi Type and Reference bit string(8) Semantics description
10.3.4
10.3.4.0
Radio Bearer Information elements

Default configuration identity
This information element identifies a default radio parameter configuration. The corresponding default configurations are specified in subclause 13.7.
Information Element/Group name Default configuration identity Need MP Multi Type and reference Integer (0..10, 11, 13, Semantics description Version
Default configuration ID 2 is not used.
REL-4 REL-5
12, 14, 15, 16, 17,
REL-6 Used only in RRC Connection Setup message. Reserved for future extension REL-6
18..22, 23..31)
REL-6 REL-6
10.3.4.1
Downlink RLC STATUS info

Need OP Multi Type and reference Integer(10..5 50 by step of 10, 550..1000 by step of 50) Boolean Semantics description Minimum time in ms between STATUS reports
Information Element/Group name Timer_Status_Prohibit
Missing PDU Indicator
MP
Value true indicates that UE should send a STATUS report
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description for each missing PDU that is detected Time in milliseconds
Timer_STATUS_periodic
OP
Integer(100, 200, 300, 400, 500, 750, 1000, 2000)
10.3.4.1a
PDCP context relocation info
This information element indicates that the header compression context relocation is to be performed during SRNS relocation for the given radio bearer.
Information Element/Group name RB identity Downlink RFC 3095 context relocation indication Need MP MP Multi Type and reference RB identity 10.3.4.16 Boolean Semantics description Version REL-5 TRUE means RFC 3095 context relocation is performed in downlink TRUE means RFC 3095 context relocation is performed in uplink REL-5
Uplink RFC 3095 context relocation indication
MP
Boolean
REL-5
10.3.4.2
PDCP info
The purpose of the PDCP info IE is to indicate which algorithms shall be established and to configure the parameters of each of the algorithms.
Information Element/Group name Support for lossless SRNS relocation or for lossless DL RLC PDU size change Max PDCP SN window size Need CVLosslessCr iteria CVLossless Multi Type and reference Boolean Semantics description TRUE means support Maximum PDCP sequence number window size. The handling of sequence number when the Max PDCP SN window size is 255 is specified in [23]. Whether a PDCP PDU header is existent or not. Version
Enumerated( sn255, sn65535)
PDCP PDU header
MP
Enumerated (present, absent) 1 to <maxPDC PAlgoType >
Header compression information
OP
>CHOICE algorithm type >>RFC 2507
MP
>>>F_MAX_PERIOD
MD
Integer (1..65535)
Note 1 Header compression according to IETF standard RFC 2507 Largest number of compressed non-
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TCP headers that may be sent without sending a full header. Default value is 256. Compressed headers may not be sent more than F_MAX_TIME seconds after sending last full header. Default value is 5. The largest header size in octets that may be compressed. Default value is 168. Maximum CID value for TCP connections. Default value is 15. Maximum CID value for non-TCP connections. Default value is 15. Whether the algorithm shall reorder PDCP SDUs or not. Default value is "reordering not expected". Header compression according to IETF standard RFC 3095 Profiles supported by both compressor and decompressor in both UE and UTRAN. Profile 0 shall always be supported. 1 = 0x0001, 2 = 0x0002, 3 = 0x0003 (see [52]) Indicates the necessary information elements for Uplink. Highest context ID number to be used by the UE compressor. Default value is 15. Version
>>>F_MAX_TIME
MD
Integer (1..255)
>>>MAX_HEADER
MD
Integer (60..65535)
>>>TCP_SPACE
MD
Integer (3..255)
>>>NON_TCP_SPACE
MD
Integer (3..65535)
>>>EXPECT_REORDERING
MD
Enumerated (reordering not expected, reordering expected)
>>RFC 3095
REL-4
>>>Profiles
MP
1 to <maxROH CProfiles>
REL-4
>>>>Profile instance
MP
Integer(1.. 3)
REL-4
>>>Uplink
OP
REL-4
>>>>Max_CID
MD
Integer (1.. 16383)
REL-4
3GPP
Release 6 Information Element/Group name >>>Downlink Need
3GPP TS 25.331 V6.23.0 (2009-09)
Semantics Version description OP Indicates the REL-4 necessary information elements for Downlink. >>>>Max_CID MD Integer (1.. Highest context ID REL-4 16383) number to be used by the UE decompressor. Default value is 15. >>>>Reverse_Decompression_ MD Integer Determines REL-4 Depth (0..65535) whether reverse decompression should be used or not and the maximum number of packets that can be reverse decompressed by the UE decompressor. Default value is 0 (reverse decompression shall not be used). Note 1: If several occurrences of the same algorithm type are included in the same IE header compression information, the UE behaviour is unspecified.
Condition LosslessCriteria
Lossless
Explanation This IE is mandatory present if the IE "RLC mode" is "Acknowledged", the IE "In-sequence delivery " is "True" and the IE "SDU Discard Mode" is "No discard" and not needed otherwise. This IE is mandatory present if the IE "Support for lossless SRNS relocation or for lossless RLC PDU size change" Is TRUE, otherwise it is not needed.
10.3.4.2a
PDCP ROHC target mode

Need MP Multi Type and Reference Enumerated (O-mode, Rmode) Semantics description The UE shall only transit to the signalled mode for operation of ROHC as decribed in [36]. Version REL-5
Information Element/Group name Target Mode
10.3.4.3
PDCP SN info
Need MP Multi Type and Reference Integer(0..65 535) Semantics description The PDCP sequence number, which the sender of the message is expecting next to be received.
Information Element/Group name Receive PDCP sequence number
3GPP
Release 6
552
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.4
Polling info
Need OP Multi Type and reference Integer(10..5 50 by step of 10, 600..1000 by step of 50) Integer(10..5 50 by step of 10, 600..1000 by step of 50) Integer(1,2,4 ,8,16,32,64,1 28) Integer(1,4,1 6,64) Boolean Semantics description Minimum time between polls in ms
Information Element/Group name Timer_poll_prohibit
Timer_poll
OP
Time in ms.
Poll_PDU
OP
Number of PDUs, interval between pollings Number of SDUs, interval between pollings TRUE indicates that poll is made at last PDU in transmission buffer TRUE indicates that poll is made at last PDU in retransmission buffer Percentage of transmission window, threshold for polling Time in milliseconds Timer for periodic polling.
Poll_SDU Last transmission PDU poll
OP MP
Last retransmission PDU poll
MP
Boolean
Poll_Window
OP
Timer_poll_periodic
OP
Integer(50,6 0,70,80,85,9 0,95,99) Integer(100, 200, 300, 400, 500, 750, 1000, 2000)
10.3.4.5
Predefined configuration identity
This information element identifies a predefined radio parameter configuration.

Information Element/Group name Predefined radio configuration identity Need MP Multi Type and reference Integer (0..15) Semantics description
10.3.4.5a
Predefined configuration status information
Another system may provide the UE with one or more predefined UTRAN configurations, comprising of radio bearer, transport channel and physical channel parameters. If requested, the UE shall indicate the configurations it has stored. The predefined configuration status information should include the following RRC information.
Information Element/Group name RB information elements Predefined configurations Need Multi Type and reference Semantics description
maxPredef ConfigCou nt OP Predefined configuration value tag 10.3.4.6
The list is in order of preconfiguration identity The UE shall include the value tag if it has stored the concerned configuration
>Predefined configuration value tag
Multi Bound MaxPredefConfigCount
Explanation Maximum number of predefined configurations
3GPP
Release 6
553
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.5b
Another system may provide the UE with one or more predefined UTRAN configurations, comprising of radio bearer, transport channel and physical channel parameters. If requested, the UE shall indicate the configurations it has stored. The compressed predefined configuration status information should include the following RRC information.
Information Element/Group name Sets with different value tags >Pre-defined configuration set with different value tags >>Start position Need MP MP 1..2 Multi Type and reference Semantics description Version REL-5 REL-5
MD
INTEGER (0..10)
>>Pre-defined configuration value tag list Other Entries >Pre-defined configuration list with variable size
MP
6..<max PredefC onfig>
Pre-defined configuration value tag 10.3.4.6
Default value is 0, corresponding with the first predefined configuration. The pre-defined configuration where the consecutive sequence of pre-defined configurations begins. Value Tags for each pre-defined configuration starting from the lowest.
REL-5
REL-5
OP MP
1..<max PredefC onfig>
>>Predefined configuration value tag
OP
Predefined configuration value tag 10.3.4.6
List of other pre-defined configurations not included within the Sets with different value tags, in consecutive order starting with the lowest. If there are stored pre-defined configurations positioned after a pre-defined configuration that is not stored, the UE shall indicate the not-stored pre-defined configuration by explicitly indicating it to be absent. If there are no stored pre-defined configurations positioned after a pre-defined configuration that is not stored, then the UE may totally omit these pre-defined configurations from the IE, i.e. reduce the size of the list to correspond to the last position that contained a stored predefined configuration. The UE shall include the value tag if it has stored the concerned configuration
REL-5 REL-5
REL-5
10.3.4.6
Predefined configuration value tag
This information element is used to identify different versions of a radio bearer configuration as may be used within one PLMN e.g. to support different UTRAN implementations.
Information Element/Group name Predefined configuration value tag Need MP Multi Type and Reference Integer(0..15 ) Semantics description
3GPP
Release 6
554
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.7
Predefined RB configuration
This information element concerns a predefined configuration of radio bearer parameters
Information Element/Group name UE information elements Re-establishment timer Need Multi Type and Reference Reestablishme nt timer 10.3.3.30 Semantics description
MP
Only one RAB supported
Signalling radio bearer information Signalling RB information to setup List >Signalling RB information to setup
MP
1 to <maxSRBs etup> Signalling RB information to setup 10.3.4.24
For each signalling radio bearer
MP
RB information RB information to setup list
Only one RAB supported MP 1 to <maxRBpe rRAB> RB information to setup 10.3.4.20
>RB information to setup
MP
10.3.4.8
RAB info
This IE contains information used to uniquely identify a radio access bearer.

Information Element/Group name RAB identity MBMS Service Identity Need MP CVMessage Multi Type and reference RAB identity 10.3.1.14 MBMS service ID 10.3.9a.8a Semantics description Version
Included when establishing a RB for a MBMS service of the broadcast type; NOTE 1
REL-6
MBMS Session identity
MBMS REL-6 Session identity 10.3.9a.9 CN domain identity MP CN domain identity 10.3.1.1 NAS Synchronization Indicator OP NAS Synchronizat ion indicator 10.3.4.12 Re-establishment timer MP Reestablishme nt timer 10.3.3.30 NOTE 1: Only the "MBMS Service ID" part of the MBMS service identity is signalled in this IE. The UE should consider that the "PLMN identity" part of the MBMS service identity equals the PLMN identity of an MBMS service with the same "MBMS Service ID" stored in the variable ACTIVATED_MBMS_SERVICES. If there is no such MBMS service or more than one such MBMS service, the UE behaviour is unspecified.
CVMessage
3GPP
Release 6 Condition Message
555
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation This IE is optionally present in the RADIO BEARER SETUP and the SRNS RELOCATION INFO messages and not needed otherwise.
10.3.4.9
RAB info Post
This IE contains information used to uniquely identify a radio access bearer.

Information Element/Group name RAB identity CN domain identity Need MP MP Multi Type and reference RAB identity 10.3.1.14 CN domain identity 10.3.1.1 NAS Synchronizat ion indicator 10.3.4.12 Semantics description
NAS Synchronization Indicator
OP
10.3.4.10
RAB information for setup

Need MP MP 1 to <maxRBpe rRAB> RB information to setup 10.3.4.20 Multi Type and reference RAB info 10.3.4.8 Semantics description
Information Element/Group name RAB info RB information to setup list
>RB information to setup
MP
10.3.4.11
RAB information to reconfigure

Need MP MP Multi Type and reference RAB Identity 10.3.1.14 CN domain identity 10.3.1.1 NAS Synchronizat ion info 10.3.4.12 Semantics description
Information Element/Group name RAB identity CN domain identity
NAS synchronization indicator
MP
3GPP
Release 6
556
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.11a
RAB information for MBMS ptp bearers

Need MP MP Multi Type and reference RB identity 10.3.4.16 MBMS Service ID 10.3.9a.8a Semantics description Version REL-6 Indicates that this radio bearer is used for a different MBMS service. Indicates that this radio bearer is used for a different session of the MBMS service. REL-6
Information Element/Group name RB identity MBMS Service Identity
MBMS Session Identity
OP
MBMS Session identity 10.3.9a.9
REL-6
10.3.4.12
NAS Synchronization indicator
A container for non-access stratum information to be transferred transparently through UTRAN.

Information Element/Group name NAS Synchronization indicator Need MP Multi Type and reference Bit string(4) Semantics description The first/leftmost bit of the bit string contains the most significant bit of the NAS Synchronization indicator.
10.3.4.13
RB activation time info
This IE contains the time, in terms of RLC sequence numbers, when a certain configuration shall be activated, for a number of radio bearers.
Information Element/Group name Radio bearer activation time >RB identity >RLC sequence number Need MP MP MP Multi 1 to <maxRB> RB identity 10.3.4.16 Integer (0.. 4095) Type and reference Semantics description
RLC SN [16] . Used for radio bearers mapped on RLC AM and UM
10.3.4.14
RB COUNT-C MSB information
The MSB of the COUNT-C values of the radio bearer.

Information Element/Group name RB identity COUNT-C-MSB-uplink COUNT-C-MSB-downlink Needed MP MP MP Multi Type and reference RB identity 10.3.4.16 Integer (0.. 2^25-1) Integer (0.. 2^25-1) Semantics description
25 MSBs from COUNT-C associated to this RB 25 MSBs from COUNT-C associated to this RB
10.3.4.15
RB COUNT-C information
The COUNT-C values of the radio bearer.
3GPP
Release 6 Information Element/Group name RB identity COUNT-C-uplink COUNT-C-downlink Needed MP MP MP
557 Multi Type and reference RB identity 10.3.4.16 Integer (0.. 2^32-1) Integer (0.. 2^32-1)
10.3.4.16
RB identity
An identification number for the radio bearer affected by a certain message.

Information Element/Group name RB identity Need MP Multi Type and reference Integer(1..32 ) Semantics description Values 1-4 shall only be used for signalling radio bearers. The IE value minus one shall be used as BEARER in the ciphering algorithm.
10.3.4.17
RB information to be affected
Need MP MP Multi Type and reference RB identity 10.3.4.16 RB mapping info 10.3.4.21 Semantics description
Information Element/Group name RB identity RB mapping info
10.3.4.18
RB information to reconfigure
Need MP OP OP Multi Type and reference RB identity 10.3.4.16 PDCP info 10.3.4.2 PDCP SN info 10.3.4.3 RLC info 10.3.4.23 RB mapping info 10.3.4.21 Enumerated( stop, continue) Semantics description
Information Element/Group name RB identity PDCP info PDCP SN info
PDCP sequence number info from the network. Present only in case of lossless SRNS relocation.
RLC info RB mapping info
OP OP
RB stop/continue
OP
10.3.4.19
RB information to release
Need MP Multi Type and reference RB identity 10.3.4.16 Semantics description
Information Element/Group name RB identity
3GPP
Release 6
558
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.20
RB information to setup
Need MP OP MP RLC info 10.3.4.23 RB identity 10.3.4.16 RB mapping info 10.3.4.21 Multi Type and reference RB identity 10.3.4.16 PDCP info 10.3.4.2 Semantics description
Information Element/Group name RB identity PDCP info CHOICE RLC info type >RLC info >Same as RB RB mapping info
Identity of RB with exactly the same RLC info IE values
MP
NOTE:
This information element is included within IE "Predefined RB configuration".
10.3.4.21
RB mapping info
A multiplexing option for each possible transport channel MAC-d flow or E-DCH MAC-d flow this RB can be multiplexed on.
Information Element/Group name Information for each multiplexing option >RLC logical channel mapping indicator Need MP Multi 1 to <maxRBM uxOptions> Boolean TRUE indicates that the first logical channel shall be used for data PDUs and the second logical channel shall be used for control PDUs. FALSE indicates that control and data PDUs can be sent on either of the two logical channels. This parameter is not used in this release and shall be set to TRUE. 1 or 2 logical channels per RLC entity or radio bearer RLC [16] REL-6 REL-6 MP Enumerated( DCH,RACH, USCH Transport channel identity 10.3.5.18 Integer(1..15 ) USCH is TDD only This is the ID of a DCH or USCH (TDD only) that this RB could be mapped onto. This parameter is used to Type and reference Semantics description Version
CV-ULRLCLogica lChannels
>Number of uplink RLC logical channels
CV-ULRLC info
1 to MaxLoCHp erRLC
>>CHOICE Uplink transport channel type >>>DCH, RACH, USCH >>>>Uplink transport channel type >>>>ULTransport channel identity
CV-ULDCH/USC H
>>>>Logical channel identity
OP
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description distinguish logical channels multiplexed by MAC on a transport channel. The RLC sizes that are allowed for this logical channel. All RLC sizes listed in the Transport Format Set. 10.3.5.23 The RLC sizes configured for this logical channel in the Transport Format Set. 10.3.5.23 if present in this message or in the previously stored configuration otherwise Lists the RLC sizes that are valid for the logical channel. The integer number is a reference to the RLC size which arrived at that position in the Transport Format Set 10.3.5.23 Note 4 This parameter is used to distinguish logical channels multiplexed by MAC on a transport channel Version
>>>>CHOICE RLC size list
MP
>>>>>All
Null
>>>>>Configured
Null
>>>>>Explicit List
1 to <maxTF>
>>>>>>RLC size index
MP
Integer(1..m axTF)
>>>E-DCH >>>>Logical channel identity
MP
Integer(1..15 )
REL-6 REL-6
>>>>E-DCH MAC-d flow identity
MP
>>>>DDI
MP
E-DCH MAC-d flow identity 10.3.5.7e Integer (0..62)
REL-6
If more than 1 UL RLC PDU size is configured for this RB, the different sizes will use subsequent DDI values starting from this DDI value. Value 0x3F is reserved
REL-6
>>>>RLC PDU size list
MP
1 to <maxRLC PDUsizeP erLogChan > Integer(16..5 000 by step Unit is bits
REL-6
>>>>>RLC PDU size
MP
REL-6
3GPP
Release 6 Information Element/Group name >>>>Include in Scheduling Info Need
560 Multi Type and reference of 8) Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Indicates whether or not this logical channel is to be considered when performing scheduling info reporting, as per [15] This is priority between a user's different RBs (or logical channels). [15] Version
MP
REL-6
>>MAC logical channel priority
MP
Integer(1..8)
>Downlink RLC logical channel info >>Number of downlink RLC logical channels
CV-DLRLC info MD
1 to MaxLoCHp erRLC
>>>Downlink transport channel type
Enumerated( DCH,FACH, DSCH,DCH+ DSCH , HS-DSCH, Note 4 REL-5 DCH + HSDSCH) CV-DL>>>DL DCH Transport channel Transport DCH identity channel identity 10.3.5.18 >>>DL DSCH Transport channel CV-DLTransport DSCH identity channel identity 10.3.5.18 CV-DL-HS>>>DL HS-DSCH MAC-d flow MAC-d flow REL-5 DSCH identity identity 10.3.5.7c >>>Logical channel identity OP Integer(1..15 16 is reserved ) Note 3: The IE "Downlink transport channel type" values " DSCH and DCH+DSCH " should not be used for FDD. If received the UE behaviour is unspecified. Note 4: If included in System Information Block Type 16, the values HS-DSCH and DCH + HS-DSCH do not apply for the IE "Downlink transport channel type". Furthermore, if included in System Information Block Type 16, the value "E-DCH for the IE "Uplink transport channel type" does not apply.
MP
1 or 2 logical channels per RLC entity or radio bearer RLC [16] Default value is that parameter values for DL are exactly the same as for corresponding UL logical channel. In case two multiplexing options are specified for the UL, the first options shall be used as default for the DL. As regards to the IE "Channel type", rule is specified in 8.6.4.8. Note 3
3GPP
Release 6
561
3GPP TS 25.331 V6.23.0 (2009-09)
Condition UL-RLC info
DL-RLC info
UL-RLCLogicalChannels
UL-DCH/USCH
DL-DCH
DL-DSCH
DL-HS-DSCH
Explanation If "CHOICE Uplink RLC mode" in the IE "RLC info" that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the "RB mapping info" was received, or the one stored or received in the same message for the RB pointed at in the IE "Same as RB" in the IE "RB information to setup" stored or received in the same message) is present this IE is mandatory present. Otherwise the IE is not needed. If "CHOICE Downlink RLC mode" in the IE "RLC info" that applies for that RB (i.e. either the one stored or received in the same message for the RB for which the "RB mapping info" was received, or the one stored or received in the same message for the RB pointed at in the IE "Same as RB" in the IE "RB information to setup" stored or received in the same message) is present this IE is mandatory present. Otherwise the IE is not needed. If "Number of uplink RLC logical channels" in IE "RB mapping info" is 2, then this IE is mandatory present. Otherwise this IE is not needed. If IE "Uplink transport channel type" is equal to "DCH" or "USCH" (TDD only) this IE is mandatory present. Otherwise the IE is not needed. If IE "Downlink transport channel type" is equal to "DCH", "DCH+DSCH" or DCH + HS-DSCH this IE is mandatory present. Otherwise the IE is not needed. If IE "Downlink transport channel type" is equal to "DSCH" or "DCH+DSCH" this IE is mandatory present. Otherwise the IE is not needed. If IE "Downlink transport channel type" is equal to "HSDSCH" or DCH + HS-DSCH this IE is mandatory present. Otherwise the IE is not needed.
10.3.4.22
RB with PDCP information

Need MP MP Multi Type and reference RB identity 10.3.4.16 PDCP SN info 10.3.4.3 Semantics description Version
Information Element/Group name RB identity PDCP SN info
PDCP sequence number info from the sender of the message for lossless SRNS relocation. PDCP sequence number info from the sender of the message for lossless SRNS relocation or for lossless DL RLC PDU size change.
REL-5
10.3.4.23
RLC info
Need OP Multi Type and reference Semantics description Indicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be used. Transmissio n RLC Version
Information Element/Group name CHOICE Uplink RLC mode
>AM RLC >>Transmission RLC discard
MP
3GPP
562 Multi Type and reference discard 10.3.4.25 Integer(1,8,1 6,32,64,128, 256,512,768, 1024,1536,2 047,2560,30 72,3584,409 5) Integer(50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 700, 800, 900, 1000) Integer(1, 4, 6, 8, 12 16, 24, 32) Polling info 10.3.4.4 Transmissio n RLC discard 10.3.4.25 Transmissio n RLC discard 10.3.4.25 Boolean
>>Transmission window size
MP
>>Timer_RST
MP
Maximum number of RLC PUs sent without getting them acknowledged. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN receiver window is equal to this value. Elapsed time in milliseconds. It is used to trigger the retransmission of RESET PDU.
>>Max_RST
MP
Defined in [16]
>>Polling info >UM RLC >>Transmission RLC discard
OP
OP
>TM RLC >>Transmission RLC discard
OP
>>Segmentation indication CHOICE Downlink RLC mode
MP OP
TRUE indicates that segmentation is performed. Indicates if Acknowledged, Unacknowledged or Transparent mode RLC shall be used
>AM RLC >>DL RLC PDU size
MP
>>In-sequence delivery
MP
Integer(16..5 000 by step of 8) Boolean
Unit is bits
REL-5
>>Receiving window size
MP
>>Downlink RLC status Info
MP
Integer(1,8,1 6,32,64,128, 256,512,768, 1024,1536,2 047,2560,30 72,3584,409 5) Downlink RLC status info 10.3.4.1
TRUE indicates that RLC shall preserve the order of higher layer PDUs when these are delivered. FALSE indicates that receiving RLC entity could allow SDUs to be delivered to the higher layer in different order than submitted to RLC sublayer at the transmitting side. Maximum number of RLC PUs allowed to be received. This parameter is needed if acknowledged mode is used. UE shall also assume that the UTRAN transmitter window is equal to this value
3GPP
Release 6 Information Element/Group name >UM RLC >>DL UM RLC LI size >>DL Reception Window Size Need
563 Multi Type and reference Integer(7, 15) Integer(32, 48, 64, 80, 96, 112) Boolean Boolean
MP CV-NotSIB16o
Size in bits to use for the downlink RLC UM LI.
REL-5 REL-6
>TM RLC >>Segmentation indication One sided RLC re-establishment
MP MP
Alternative E-bit interpretation
CV-NotSIB16o
Enumerated (true)
TRUE indicates that segmentation is performed. TRUE indicates that only one side of the AM RLC entity is re-established. The absence of this IE implies: "normal E-bit interpretation".
REL-5
REL-6
Condition Not-SIB16o
Explanation If included in SYSTEM INFORMATION BLOCK TYPE 16, this IE is not needed. Otherwise the IE is optional
NOTE:
10.3.4.23a
RLC info MBMS
The IE RLC info MBMS is used for point-to-multipoint radio bearers, featuring only the downlink RLC UMD.
Information Element/Group name DL UM RLC LI size DL Duplication Avoidance and Reordering info Need MP CV-MTCH Multi Type and reference Integer (7, 15) UM Duplication Avoidance and Reordering info 10.3.4.26 UM Out of sequence delivery info 10.3.4.27 Semantics description Size in bits to use for the downlink RLC UM LI. Version REL-6 REL-6
DL Out of sequence delivery info
CV-MCCH
REL-6
Condition MTCH MCCH
Explanation If the IE concerns MTCH, this IE is optional. Otherwise the IE is not needed. If the IE concerns MCCH, this IE is optional. Otherwise the IE is not needed.
3GPP
Release 6
564
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.4.24
Signalling RB information to setup

Need MD MP RLC info 10.3.4.23 RB identity 10.3.4.16 RB mapping info 10.3.4.21 Multi Type and reference RB identity 10.3.4.16 Semantics description Default value is specified in subclause 8.6.4.1
Information Element/Group name RB identity CHOICE RLC info type >RLC info >Same as RB RB mapping info
Identity of RB with exactly the same RLC info IE values
MP
NOTE:
10.3.4.25
Transmission RLC Discard

Need MP Multi Type and reference Semantics description Different modes for discharge the RLC buffer on the transmitter side; "Timer based with explicit signalling", "Timer based without explicit signalling", "Discard after Max_DAT retransmissions" or "No_discard". For unacknowledged mode and transparent mode, only Timer based without explicit signalling is applicable. If "No_discard" is used, reset procedure shall be done after Max_DAT retransmissions Integer(50,6 0, 70, 80, 90, 100, 120, 140, 160, 180, 200, 300, 400, 500, 700, 900) Integer(100, 250, 500, 750, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 7500) Integer(1, 4, 6, 8, 12 16, 24, 32) Integer(10,2 0,30,40,50,6 0,70,80,90,1 00) Integer(1, 2, 3, 4, 5, 6, 7, Elapsed time in milliseconds. It is used to trigger the retransmission of a STATUS PDU containing an MRW SUFI field
Information Element/Group name CHOICE SDU Discard Mode
>Timer based explicit >>Timer_MRW
MP
>>Timer_discard
MP
Elapsed time in milliseconds before a SDU is discarded.
>>MaxMRW
MP
Defined in [16]
>Timer based no explicit >>Timer_discard
MP
Elapsed time in milliseconds before a SDU is discarded.
>Max DAT retransmissions >>Max_DAT
MP
Defined in [16]
3GPP
565 Multi Type and reference 8, 9, 10, 15, 20, 25, 30, 35, 40) Integer(50, 60, 70, 80, 90, 100, 120, 140, 160, 180, 200, 300, 400, 500, 700, 900) Integer(1, 4, 6, 8, 12 16, 24, 32) Integer(1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40)
>>Timer_MRW
MP
Elapsed time in milliseconds. It is used to trigger the retransmission of a STATUS PDU containing an MRW SUFI field
>>MaxMRW
MP
Defined in [16]
>No discard >>Max_DAT
MP
Defined in [16]
CHOICE SDU Discard Mode Timer based explicit
Timer based no explicit
Max DAT retransmissions
No discard
Condition under which the given SDU Discard Mode is chosen If the modes for discharge of the RLC buffer on the transmitter side is "Timer based with explicit signalling" If the modes for discharge of the RLC buffer on the transmitter side is "Timer based without explicit signalling" For unacknowledged mode, only Timer based without explicit signalling is applicable. If the modes for discharge of the RLC buffer on the transmitter side is "Discard after Max_DAT retransmissions" If the modes for discharge the of RLC buffer on the transmitter side is "Reset procedure shall be done after Max_DAT retransmissions"
10.3.4.26
UM Duplication Avoidance and Reordering info

Need MP Multi Type and reference Integer(40, 80, 120, 160, 240, 320, 480, 640, 960, 1280, 1920, 2560, 3840, 5120) Integer(4, 8, 16, 32, 40, 48, 56, 64) Semantics description Timer (in milliseconds) when PDUs are released to the upper layers even though there are outstanding PDUs with lower RLC SN values. Version REL-6
Information Element/Group name Timer_DAR
Window size DAR
MP
REL-6
10.3.4.27
UM Out of sequence delivery info

Need CVnotMCCH Multi Type and reference Integer (40, 80, 120, 160, 240, 320, 480, 640, Semantics description Version REL-6
Information Element/Group name Timer_OSD
3GPP
566 Multi Type and reference 960, 1280, 1920, 2560, 3840, 5120) Integer(8, 16, 32,40, 48, 56, 64)
Window size OSD
MP
REL-6
NOTE:
This timer used to flush the buffer is configured at RRC level and indicated via a local primitive.
Condition notMCCH
Explanation If this concerns a logical channel other than MCCH then this IE is mandatory otherwise it is not needed. In the latter case Timer_OSD takes the value of the IE Modification Period as indicated within the IE MCCH configuration information
10.3.5
10.3.5.1
Transport CH Information elements

Added or Reconfigured DL TrCH information
Need MP Multi Type and reference Enumerated( DCH,DSCH ,HS-DSCH) Transport channel identity 10.3.5.18 Semantics description Note 2 Version
Information Element/Group name Downlink transport channel type
REL-5
DL Transport channel identity
MP
CV-not HS-DSCH CHOICE DL parameters >Explicit >>TFS
REL-5
MP
Transport Format Set 10.3.5.23 Enumerated( DCH,USCH) Transport channel identity 10.3.5.18 HARQ info 10.3.5.7a Added or reconfigured MAC-d flow 10.3.5.1a Quality target 10.3.5.10 USCH is TDD only Same TFS applies as specified for indicated UL TrCH REL-5 REL-5 REL-5
>SameAsUL >>Uplink transport channel type >>UL TrCH identity
MP MP
>HS-DSCH >>HARQ Info >>Added or reconfigured MAC-d flow
OP OP
DCH quality target
OP
Note 1: Note 2:
Void The IE "Downlink transport channel type" value " DSCH " should not be used for FDD. If received the UE behaviour is unspecified.
3GPP
Release 6 Condition NotHS-DSCH
567
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation If the downlink transport channel type is DCH or DSCH then this IE is mandatory otherwise it is not needed.
10.3.5.1a
Added or reconfigured MAC-d flow
This IE is used in relation to the MAC-d flows mapped to the HS-DSCH transport channel.
Information Element/Group name MAC-hs queue to add or reconfigure list >MAC-hs queue Id Need OP Multi <1 to maxQueue ID> Integer(0..7) The MAC-hs queue ID is unique across all MAC-d flows. Type and reference Semantics description Version REL-5
MP
REL-5
>MAC-d Flow Identity
MP
>T1
MP
MAC-d Flow Identity 10.3.5.7c Integer(10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 120, 140, 160, 200, 300, 400)
REL-5
Timer (in milliseconds) when PDUs are released to the upper layers even though there are outstanding PDUs with lower TSN values.
REL-5
>MAC-hs window size
MP
Integer(4, 6, 8, 12, 16, 24, 32) <1 to max MACdPDU sizes> Mapping of the different MAC-d PDU sizes configured for the HS-DSCH to the MAC-d PDU size index in the MAChs header. Integer (1..5000) Integer(0..7) <1 to maxQueue ID> Integer(0..7) The MAC-hs queue ID is unique across all MAC-d flows.
REL-5
>MAC-d PDU size Info
OP
REL-5
>>MAC-d PDU size >>MAC-d PDU size index MAC-hs queue to delete list
MP MP OP
REL-5 REL-5 REL-5
>MAC-hs queue Id
MP
REL-5
10.3.5.1b
Added or reconfigured E-DCH MAC-d flow
This IE is used in relation to MAC-d flows mapped to the E-DCH transport channel.
3GPP
Release 6 Information Element/Group name E-DCH MAC-d flow identity Need MP
568 Multi Type and reference E-DCH MAC-d flow identity 10.3.5.7e Integer(0..6)
E-DCH MAC-d flow power offset
OP
E-DCH MAC-d flow maximum number of retransmissions
OP
Integer (0..15)
E-DCH MAC-d flow multiplexing list
OP
Bitstring (maxEDCHMACdFl ow)
Only allowed to be absent when already defined for this E-DCH MAC-d flow, unit is dB Only allowed to be absent when already defined for this E-DCH MAC-d flow Indicates, if this is the first MAC-d flow for which PDUs are placed in the MAC-e PDU, the other MAC-d flows from which MAC-d PDUs are allowed to be included in the same MAC-e PDU. Bit 0 is for MAC-d flow 0, Bit 1 is for MAC-d flow 1, Value '1' for a bit means multiplexing is allowed. Bit 0 is the first/leftmost bit of the bit string. NOTE: The bit that corresponds to the MAC-d flow itself is ignored. Only allowed to be absent when already defined for this E-DCH MAC-d flow
REL-6
REL-6
REL-6
CHOICE transmission grant type
OP
REL-6
>Non-scheduled transmission grant info >>Max MAC-e PDU contents size >>2ms non-scheduled transmission grant HARQ process allocation
REL-6 MP MD Integer (1..19982) Bitstring (8) REL-6 MAC-d PDUs for this MAC-d flow are only allowed to be transmitted in those processes for which the bit is set to 1. Bit 0 corresponds to HARQ process 0, bit 1 corresponds to HARQ process 1, Default value is: transmission in all REL-6
3GPP
Release 6
569
3GPP TS 25.331 V6.23.0 (2009-09) HARQ processes is allowed. Bit 0 is the first/leftmost bit of the bit string.
>Scheduled transmission grant info
NULL
REL-6
10.3.5.2
Added or Reconfigured UL TrCH information

Need MP Multi Type and reference Enumerated( DCH,USCH ,E-DCH) Transport channel identity 10.3.5.18 Semantics description USCH is TDD only Note 1 REL-6 Version
Information Element/Group name Uplink transport channel type
UL Transport channel identity
MP
CV-NotEDCH CHOICE UL parameters >DCH,USCH >>TFS
REL-6 REL-6 REL-6
MP
Transport Format Set 10.3.5.23 Integer(2,10) 10.3.5.7d <1 to maxEDCHMACd Flow> Unit is ms. REL-6 REL-6 REL-6 REL-6
>E-DCH >>E-DCH Transmission Time Interval >>HARQ info for E-DCH >>Added or reconfigured E-DCH MAC-d flow list
MP MP OP
>>>Added or reconfigured EDCH MAC-d flow
Note 1:
Added or REL-6 reconfigured E-DCH MAC-d flow 10.3.5.1b If included in System Information Block Type 16, the values E-DCH does not apply for the IE "Uplink transport channel type".
MP
Condition NotE-DCH
Explanation If the uplink transport channel type is DCH or USCH then this IE is mandatory otherwise it is not needed.
NOTE:
10.3.5.2a
Additional Dynamic Transport Format Information for CCCH

Need MP Multi Type and reference Integer (48..4968) Semantics description Unit is bits For FDD, values are restricted to: Integer (48..296 by step of 8, 312..1320 by step of 16, 1384..4968 by step of 64) Version Rel-6
Information Element/Group name RLC Size
Number of Transport blocks
MP
Integer(1)
Rel-6
3GPP
Release 6
570
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.2b
Additional RACH TFCS for CCCH

Need MP Multi Type and reference Power Offset Information 10.3.5.8 Semantics description The actual TFCS is specified in 8.6.5.12a Version Rel-6
Information Element/Group name Power offset Information
10.3.5.3
Void
10.3.5.4
Deleted DL TrCH information

Need MP Multi Type and reference Enumerated( DCH,DSCH ,HS-DSCH) Transport channel identity 10.3.5.18 Semantics description Note 1 Version
Information Element/Group name Downlink transport channel type
REL-5
DL Transport channel identity
MP
DL HS-DSCH MAC-d flow identity Note 1:
MAC-d flow REL-5 identity 10.3.5.7c The IE "Downlink transport channel type" value " DSCH " should not be used for FDD. If received the UE behaviour is unspecified.
CV-notHSDSCH CV-HSDSCH
REL-5
Condition NotHS-DSCH
HS-DSCH
Explanation If the downlink transport channel type is DCH or DSCH then this IE is mandatory otherwise it is not needed. If the downlink transport channel type is HSDSCH then this IE is mandatory otherwise it is not needed.
10.3.5.5
Deleted UL TrCH information

Need MP Multi Type and reference Enumerated( DCH,USCH ,E-DCH) Transport channel identity 10.3.5.18 Semantics description USCH is TDD only REL-6 Version
Information Element/Group name Uplink transport channel type
UL Transport channel identity
MP
E-DCH MAC-d flow identity
CV-NotEDCH CV-E-DCH
REL-6 E-DCH MAC-d flow identity 10.3.5.7e REL-6
3GPP
Release 6 Condition NotE-DCH E-DCH
571
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation If the uplink transport channel type is DCH or USCH then this IE is mandatory otherwise it is not needed. If the uplink transport channel type is E-DCH then this IE is mandatory otherwise it is not needed.
10.3.5.6

Need OP Multi Type and reference Transport Format Combination Set 10.3.5.20 Semantics description This IE should not be included in this version of the protocol. Although this IE is not always required, need is MP to align with ASN.1 REL-4 Version
Information Element/Group name SCCPCH TFCS
CHOICE mode
MP
OP >FDD >>CHOICE DL parameters >>>Explicit >>>>DL DCH TFCS OP MP Transport Format Combination Set 10.3.5.20 Although this IE is not always required, need is MP to align with ASN.1
OP >>>SameAsUL >TDD >>Individual DL CCTrCH information >>>DL TFCS Identity (no data) See note 2 OP 1 to <maxCCTr CH> Transport format combination set identity 10.3.5.21 Identifies a special CCTrCH for shared or dedicated channels.
REL-4
MP
>>>CHOICE DL parameters >>>>Independent >>>>>DL TFCS
MP MP Transport format combination set 10.3.5.20 Transport format combination set identity 10.3.5.21 See note 2 Same TFCS applies as specified for the indicated UL DCH TFCS identity except for information applicable for UL only
>>>>SameAsUL >>>>>UL DCH TFCS Identity
MP
NOTE 1: This information element is included within IE "Predefined TrCh configuration". NOTE 2: The UTRAN should only use the choice "SameAsUL" if the transport channel numbering, the number of TFs in the TFS of each transport channel, and the TFCS are identical in the uplink and downlink.
3GPP
Release 6
572
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.7
Void
10.3.5.7a
HARQ Info
This IE is used in relation to the HS-DSCH transport channel.

Information Element/Group name Number of Processes CHOICE Memory Partitioning >Implicit Need MP MP UE shall apply memory partitioning of equal size across all HARQ processes MP <1 to MaxHProc esses> Integer(800 .. 16000 by step of 800, 17600 .. 32000 by step of 1600, 36000 .. 80000 by step of 4000, 88000 .. 160000 by step of 8000, 176000 .. 304000 by step of 16000) Maximum number of soft channel bits available in the virtual IR buffer [27] Multi Type and reference Integer (1..8) Semantics description Version REL-5 REL-5 REL-5
>Explicit >>Memory size
REL-5 REL-5
>>>Process Memory size
MP
REL-5
10.3.5.7b 10.3.5.7c
Void MAC-d Flow Identity

Need MP Multi Type and reference Integer (0..7) Semantics description Version REL-5
Information Element/Group name MAC-d flow identity
10.3.5.7d
HARQ Info for E-DCH
This IE is used in relation to the E-DCH transport channel.
3GPP
Release 6 Information Element/Group name HARQ RV Configuration Need MP
573 Multi Type and reference Enumerated (rv0, rvtable)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description If rv0 is indicated, the UE shall only use E_DCH RV index 0. If rvtable is indicated, the UE shall use an RSN based RV index as specified in [27] Version REL-6
10.3.5.7e
E-DCH MAC-d Flow Identity

Need MP Multi Type and reference Integer (0..maxEDCHMACdFl ow-1) Semantics description Version REL-6
Information Element/Group name E-DCH MAC-d flow identity
10.3.5.8
Power Offset Information

Need MP Multi Type and reference Semantics description
Information Element/Group name CHOICE Gain Factors >Signalled Gain Factors >>CHOICE mode >>>FDD >>>>Gain Factor c >>>TDD >>Gain Factor d >>Reference TFC ID >Computed Gain Factors >>Reference TFC ID
MP
Integer (0.. 15) Integer (0..15) Integer (0..3)
MP
OP
For UL DPCCH or control part of PRACH (no data) For UL DPDCH or data part of PRACH and all uplink channels in TDD If this TFC is a reference TFC, indicates the reference ID. Indicates the reference TFC Id of the TFC to be used to calculate the gain factors for this TFC. In case of using computed gain factors, at least one signalled gain factor is necessary for reference.
MP
Integer (0.. 3)
CHOICE mode >FDD >>Power offset P p-m
MP OP Integer(5..10) In dB. Power offset between the last transmitted preamble and the control part of the message (added to the preamble power to receive the power of the message control part ) Needed only for PRACH (no data)
>TDD
3GPP
Release 6 CHOICE Gain Factors Signalled Gain Factors
574
3GPP TS 25.331 V6.23.0 (2009-09) Condition under which the way to signal the Gain Factors is chosen
The values for gain factors c (only in FDD mode) and d are signalled directly for a TFC. The gain factors c (only in FDD mode) and d are computed for a TFC, based on the signalled settings for the associated reference TFC.
Computed Gain Factors
10.3.5.9
Predefined TrCH configuration
This information element concerns a predefined configuration of transport channel parameters.
Information Element/Group name UL Transport channel information common for all transport channels Need MP Multi Type and Reference UL Transport channel information common for all transport channels 10.3.5.24 Semantics description
Added or Reconfigured TrCH information Added or Reconfigured UL TrCH information >Added or Reconfigured UL TrCH information
MP
1 to <maxTrCH preconf> Added or Reconfigure d UL TrCH information 10.3.5.2 DL Transport channel information common for all transport channels 10.3.5.6 1 to <maxTrCH preconf> Added or Reconfigure d DL TrCH information 10.3.5.1
MP
MP
Downlink transport channels Added or Reconfigured DL TrCH information >Added or Reconfigured DL TrCH information
MP
MP
10.3.5.10
Quality Target
Need MP Multi Type and reference Real(-6.3 ..0 by step of 0.1) Semantics description Signalled value is Log10(Transport channel BLER quality target)
Information Element/Group name BLER Quality value
3GPP
Release 6
575
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.11
Semi-static Transport Format Information

Need MP Multi Type and reference Integer(10, 20, 40, 80, dynamic Semantics description In ms. The value dynamic is only used in TDD mode. For FDD DCH, the value 80 is applicable only when SF=512. 5 is only applicable for the RACH in 1.28 Mcps TDD The option "No coding" is only valid for TDD. Version
Information Element/Group name Transmission time interval
5)
REL-4
Type of channel coding
MP
Coding Rate Rate matching attribute CRC size
CV-Coding MP MP
Enumerated( No coding, Convolutiona l, Turbo) Enumerated( 1/2, 1/3) Integer(1..hi RM) Integer(0, 8, 12, 16, 24)
in bits
Condition Coding
Explanation This IE is mandatory present if IE "Type of channel coding" is "Convolutional" and not needed otherwise.
10.3.5.12
Void
3GPP
Release 6
576
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.13
TFCS Explicit Configuration

Need MP MP TFCS Reconfigurat ion/Addition information 10.3.5.15 TFCS Reconfigurat ion/Addition information 10.3.5.15 TFCS Removal Information 10.3.5.16 TFCS Removal Information 10.3.5.16 TFCS Reconfigurat ion/Addition information 10.3.5.15 Multi IE type and reference Semantics description
Information Element/Group name CHOICE TFCS representation >Complete reconfiguration >>TFCS complete reconfiguration information
>Addition >>TFCS addition information
MP
>Removal >>TFCS removal information
MP
>Replace >>TFCS removal information
MP
>>TFCS addition information
MP
10.3.5.14
Void
3GPP
Release 6
577
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.15
TFCS Reconfiguration/Addition Information

Need MP MP MP OP 1 to <maxTFC> Integer(0..3) Power Offset Information 10.3.5.8 1 to <maxTFC> Integer(0..15 ) Power Offset Information 10.3.5.8 1 to <maxTFC> Integer(0..63 ) Power Offset Information 10.3.5.8 1 to <MaxTFC> Integer(0..25 5) Power Offset Information 10.3.5.8 1 to <maxTFC> Integer(0..40 95) Power Offset Information 10.3.5.8 1 to <maxTFC> Integer(0..65 535) Power Offset Information 10.3.5.8 1 to <MaxTFC> Integer(0..16 777215) Power Offset Information 10.3.5.8 Needed only for uplink physical channels. Multi IE type and reference Semantics description
Information Element/Group name CHOICE CTFC Size >2 bit CTFC >>CTFC information >>>2bit CTFC >>>Power offset Information
>4 bit CTFC >>CTFC information >>>4bit CTFC >>>Power offset Information
MP MP OP
Needed only for uplink physical channels.
>6 bit CTFC >>CTFC information >>>6 bit CTFC >>>Power offset Information
MP MP OP
MP MP OP
MP MP OP
MP MP OP
MP MP OP
3GPP
Release 6
578
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.5.16
TFCS Removal Information

Need MP MP Multi 1 to <maxTFC> Transport Format Combination (TFC) 10.3.5.19 In TDD 0 is a reserved value IE type and reference Semantics description
Information Element/Group name Removal TFCI information >TFCI
10.3.5.17
Void
10.3.5.18
Transport channel identity
This information element is used to distinguish transport channels. Transport channels of different type (RACH, USCH, FACH/PCH, DSCH or DCH) have separate series of identities. This also holds for uplink and downlink transport channel identities (i.e. for DCH). Depending on in which context a transport channel identity n that is sent, it will have different meaning
Information Element/Group name Transport channel identity Need MP Multi Type and reference Integer(1..32 ) Semantics description
10.3.5.19
Transport Format Combination (TFC)

Need MP Multi Type and reference Integer (0.. 1023) Semantics description
Information Element/Group name Transport format combination
10.3.5.20
Transport Format Combination Set
Indicates the allowed combinations of already defined Transport formats and the mapping between these allowed TFCs and the corresponding TFCI values. For TDD, different coded composite transport channels have independent transport format combination sets and thus independent TFCI values.
Information Element/Group name TFCI Field 1 Information
Need MP
Multi
IE type and reference TFCS explicit Configuratio n 10.3.5.13
Semantics description
10.3.5.21 Transport Format Combination Set Identity

NOTE: Only for TDD.
Need MD Multi Type and reference Integer Semantics description Indicates the identity of every
Information Element/Group name TFCS ID
3GPP
Release 6
579 (1...8)
3GPP TS 25.331 V6.23.0 (2009-09) TFCS within a UE. Default value is 1. TRUE indicates the use of shared channels. Default is false.
Shared Channel Indicator
MP
Boolean
10.3.5.22
Transport Format Combination Subset
Indicates which Transport format combinations in the already defined Transport format combination set are allowed.
Information Element/Group name CHOICE Subset representation >Minimum allowed Transport format combination index Need MP Transport format combination 10.3.5.19 1 to <maxTFC> MP Transport format combination 10.3.5.19 1 to <maxTFC> MP Transport format combination 10.3.5.19 1 to <maxTrCH > MP MP Enumerated( DCH, USCH) Transport channel identity 10.3.5.18 1 to <maxTF> Integer(0..31 ) (No data) USCH is TDD only Multi Type and reference Semantics description
>Allowed transport format combination list >>Allowed transport format combination
>Non-allowed transport format combination list >>Non-allowed transport format combination
>Restricted TrCH information
>>Uplink transport channel type >>Restricted UL TrCH identity
>>Allowed TFIs >>>Allowed TFI >Full transport format combination set
OP MP
10.3.5.23
Transport Format Set

Need MP The transport channel that is configured with this TFS is of type DCH MP MP 1 to <maxTF> Integer(16..5 000 by step of 8) 1 to <maxTF> Integer(10,2 0,40,80) Unit is bits Multi Type and reference Semantics description Version
Information Element/Group name CHOICE Transport channel type >Dedicated transport channels
>>Dynamic Transport Format Information >>>RLC Size
>>>Number of TBs and TTI List
MP
>>>>Transmission Time Interval
CVdynamicTT
Present for every valid number of TB's (and TTI) for this RLC Size. Unit is ms.
3GPP
Release 6 Information Element/Group name >>>>Number of Transport blocks >>>CHOICE Logical Channel List >>>>ALL >>>>Configured Need I MP MP
580 Multi Type and reference Integer(0..51 2)
The logical channels that are allowed to use this RLC Size Null Null All logical channels mapped to this transport channel. The logical channels configured to use this RLC size in the RB mapping info. 10.3.4.21 if present in this message or in the previously stored configuration otherwise Lists the logical channels that are allowed to use this RLC size.
>>>>Explicit List
1 to 15
>>>>>RB Identity >>>>>LogicalChannel
MP CH-ULRLCLogica lChannels
RB identity 10.3.4.16 Integer(0..1)
Indicates the relevant UL logical channel for this RB. "0" corresponds to the first, "1" corresponds to the second UL logical channel configured for this RB in the IE "RB mapping info".
>>Semi-static Transport Format Information
MP
Semi-static Transport Format Information 10.3.5.11 The transport channel that is configured with this TFS is of a type not equal to DCH Note Integer (48..4968) Unit is bits. For FDD, values are restricted to: Integer (48..296 by step of 8, 312..1320 by step of 16, 1384..4968 by step of 64). Present for every valid number of TB's (and TTI) for this RLC Size.
>Common transport channels
>>Dynamic Transport Format Information >>>RLC Size
MP MP
1 to <maxTF>
>>>Number of TBs and TTI List
MP
1 to <maxTF> Integer(0..51 2)
>>>>Number of Transport blocks >>>>CHOICE mode >>>>>FDD >>>>>TDD >>>>>>Transmission Time Interval >>>CHOICE Logical Channel List >>>>ALL >>>>Configured
MP MP
(no data) CVdynamicTT I MP Integer(10,2 0,40,80) Unit is ms.
Null Null
>>>>Explicit List
1 to 15
The logical channels that are allowed to use this RLC Size. All logical channels mapped to this transport channel. The logical channels configured to use this RLC size in the RB mapping info. 10.3.4.21 if present in this message or in the previously stored configuration otherwise Lists the logical channels that are allowed to use this RLC size.
3GPP
Release 6 Information Element/Group name >>>>>RB Identity >>>>>LogicalChannel Need MP CV-ULRLCLogica lChannels
581 Multi Type and reference RB identity 10.3.4.16 Integer(0..1)
Indicates the relevant UL logical channel for this RB. "0" corresponds to the first, "1" corresponds to the second UL logical channel configured for this RB in the IE "RB mapping info".
>>Semi-static Transport Format Information
MP
Semi-static Transport Format Information 10.3.5.11
Condition dynamicTTI
UL-RLCLogicalChannels
Explanation This IE is mandatory present if dynamic TTI usage is indicated in IE Transmission Time Interval in Semistatic Transport Format Information. Otherwise it is not needed. If "Number of uplink RLC logical channels" in IE "RB mapping info" in this message is 2 or the IE "RB mapping info" is not present in this message and 2 UL logical channels are configured for this RB, then this IE is mandatory present. Otherwise this IE is not needed.
10.3.5.24
UL Transport channel information common for all transport channels

Need OP Multi Type and reference Transport format combination set 10.3.5.20 Semantics description This IE should not be included in this version of the protocol. Version
Information Element/Group name PRACH TFCS
CHOICE mode >FDD
OP
3GPP
Release 6 >>TFC subset MD
582 Transport Format Combination Subset 10.3.5.22 Transport format combination set 10.3.5.20 1 to <maxCCTr CH> Transport format combination set identity 10.3.5.21 Transport format combination set 10.3.5.20 Transport Format Combination Subset 10.3.5.22 1 to <maxTFCs ub>
3GPP TS 25.331 V6.23.0 (2009-09) Default value is the complete existing set of transport format combinations
>>UL DCH TFCS
MP
>TDD >>Individual UL CCTrCH information >>>UL TFCS Identity
OP
MP
Identifies a special CCTrCH for shared or dedicated channels.
>>>UL TFCS
MP
>>>TFC subset
MD
TFC subset list
OP
Default value is the complete existing set of transport format combinations The maximum number of elements in the TFC subset list is 8. (no data)
REL-4
>CHOICE mode >>FDD >>TDD >>>TFCS Id
MP
OP
>TFC subset
MD
Transport Format Combination Set Identity 10.3.5.21 Transport Format Combination Subset 10.3.5.22
REL-4
NOTE:
This information element is included within IE "Predefined TrCh configuration".
10.3.6
10.3.6.1
Physical CH Information elements

AC-to-ASC mapping
Need MP MP Multi maxASCm ap Integer(07 ) Mapping of Access Classes to Access Service Classes (see subclause 8.5.13.) Type and reference Semantics description
Information Element/Group name AC-to-ASC mapping table >AC-to-ASC mapping
3GPP
Release 6
583
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.2
NOTE:
AICH Info
Only for FDD.
Need MP MP Multi Type and reference Integer(0..25 5) STTD Indicator 10.3.6.78 Enumerated (0, 1) Semantics description SF is fixed and equal to 256
Information Element/Group name Channelisation code STTD indicator
AICH transmission timing
MP
See parameter AICH_Transmission_Timing in [26]
10.3.6.3
NOTE:
AICH Power offset

Only for FDD.
This parameter is used to indicate the power level of AICH channel. This is the power per transmitted Acquisition Indicator minus power of the Primary CPICH.
Information Element/Group name AICH Power offset Need MP Multi Type and reference Integer(22..+5) Semantics description Offset in dB
10.3.6.4
NOTE:
Allocation period info

Only for TDD.
Parameters used by UE to determine period of shared channel allocation.

Information Element/Group name Allocation Activation Time Allocation Duration Need MP MP Multi Type and reference Integer (0..255) Integer (1..256) Semantics description Start the allocation period at the given CFN. Total number of frames for the allocation period.
10.3.6.5
Alpha
Need MP Multi Type and reference Enumerated( 0, 1/8, 2/8, 3/8, 4/8, 5/8, 6/8, 7/8, 1) Semantics description
Information Element/Group name Alpha Value
10.3.6.6
ASC setting
Need MP MP MP MP Integer(0..15 ) Integer(0..15 ) Bit string(4) Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>Available signature Start Index >>Available signature End Index >>Assigned Sub-Channel
This IE defines
3GPP
Release 6 Information Element/Group name Number Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description the subchannel assignment as specified in 8.6.6.29. The first/leftmost bit of the bit string contains the most significant bit of the Assigned SubChannel Number.. Version
>TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>>Available Channelisation codes indices
MP MD Bit string(8) Each bit indicates availability of a channelisation code index, where the channelisation code indices are numbered "channelisation code index 0" to "channelisation code index 7". The value 1 of a bit indicates that the channelisation code index is available for the ASC this IE is associated to. The value 0 of a bit indicates that the channelisation code index is not available for the ASC this IE is associated to. Default is that all channelisation codes defined in PRACH Info are available. Each bit indicates availability of a SYNC_UL code index, where the SYNC_UL code indices are numbered "SYNC_UL code index 0" to "SYNC_UL code index 7". The value 1 of a bit indicates that the SYNC_UL code index is available for the ASC this IE is associated to. The value 0 of a bit indicates that the SYNC_UL code index is not available for the
REL-4 REL-4
>>>1.28 Mcps TDD >>>>Available SYNC_UL codes indices
MD
Bit string(8)
REL-4 REL-4
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description ASC this IE is associated to. Default is that all SYNC_UL codes defined in SYNC_UL Info are available. Version
>>CHOICE subchannel size >>>Size1 >>>>Available Subchannels
MP MP null Indicates that all Subchannels are available NOTE NOTE NOTE
>>>Size2 >>>>Available Subchannels >>>Size4 >>>>Available Subchannels >>>Size8 >>>>Available Subchannels
MD MD MD
Bit string (2) Bit string (4) Bit string (8)
NOTE:
Each bit indicates availability of a subchannel, where the subchannels are numbered subchannel 0, subchannel 1 etc. The value 1 of a bit indicates that the subchannel is available for the ASC this IE is associated with. The value 0 of a bit indicates that the subchannel is not available for the ASC this IE is associated with. Default value of the IE is that all subchannels within the size are available for the ASC this IE is associated with.
10.3.6.7
Void
10.3.6.8
CCTrCH power control info
Parameters used by UE to set the SIR target value for uplink open loop power control in TDD.
Information Element/Group name TFCS Identity Need OP Multi Type and Reference Transport Format Combination Set Identity 10.3.5.21 Uplink DPCH power control info 10.3.6.91 Semantics description TFCS Identity of this CCTrCH. Default value is 1.
MP
10.3.6.8a
NOTE:
Cell and Channel Identity info

Only for TDD.
3GPP
Release 6 Information Element/Group name Burst type Need MP
586 Multi Type and Reference Enumerated (Type1, Type2)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Identifies the channel in combination with the Midamble shift and slot number. It is not used in 1.28 Mcps TDD and may be set to either value. This IE should be ignored by the receiver.
Midamble Shift Time Slot
MP OP
Integer (015) Timeslot number 10.3.6.84
Cell parameters ID
MP
Cell parameters ID 10.3.6.9
This IE is present only if no IPDL scheme is configured in the reference cell. Otherwise the slot is defined by the IPDL configuration. Identifies the cell
10.3.6.9
Cell parameters Id
Need MP Multi Type and Reference Integer(0..12 7) Semantics description
Information Element/Group name Cell parameter Id
10.3.6.10
Common timeslot info

Need MD Multi Type and reference Enumerated( Frame, Timeslot) Integer(4,8,1 6,32) Semantics description Frame timeslot related interleaving. Default value is "Frame" Describes the amount of bits for the TFCI bits code word as described in [31]. Defaults is no TFCI bit: In case of 8 PSK in 1.28Mcps TDD: 4 corresponds to 6 TFCI code word bits. 8 corresponds to 12 TFCI code word bits. 16 corresponds to 24 TFCI code word bits. 32 corresponds to 48 TFCI code word bits.
Information Element/Group name nd 2 interleaving mode
TFCI coding
MD
Puncturing limit
MP
Repetition period
MD
Repetition length
MP
Real(0.40..1. 0 by step of 0.04) Integer(1, 2,4,8,16,32,6 4) Integer(1.. Repetition period 1 )
Default is continuous allocation. Value 1 indicate continuous NOTE: This is empty if repetition period is set to 1.
3GPP
Release 6
587
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.10a
Common timeslot info MBMS

Need MD Multi Type and reference Enumerated( Frame, Timeslot) Integer(4,8,1 6,32) Semantics description Frame timeslot related interleaving. Default value is "Frame" Describes the amount of bits for the TFCI bits code word as described in [31]. Defaults is no TFCI bit: In case of 8 PSK in 1.28Mcps TDD: 4 corresponds to 6 TFCI code word bits. 8 corresponds to 12 TFCI code word bits. 16 corresponds to 24 TFCI code word bits. 32 corresponds to 48 TFCI code word bits.
Information Element/Group name nd 2 interleaving mode
TFCI coding
MD
Puncturing limit
MP
Real(0.40..1. 0 by step of 0.04)
10.3.6.11
NOTE:
Constant value
Only for FDD.
This constant value is used by the UE to calculate the initial output power on PRACH according to the Open loop power control procedure.
Information Element/Group name Constant value Need MP Multi Type and reference Integer (35..-10) Semantics description In dB
10.3.6.11a
NOTE:
Constant value TDD
3.84 Mcps TDD constant values are used for open loop power control of PRACH, USCH, HS-SICH and UL DPCH as defined in subclause 8.5.7.
Information Element/Group name TDD Constant value Need MP Multi Type and reference Integer (35..+10) Semantics description In dB
10.3.6.12
Void
10.3.6.13
Void
10.3.6.14
Void
3GPP
Release 6
588
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.15
Void
10.3.6.16
Default DPCH Offset Value
Indicates the default offset value within interleaving size at a resolution of 512chip (1/5 slot) in FDD and a resolution of one frame in TDD to offset CFN in the UE. This is used to distribute discontinuous transmission periods in time and also to distribute NodeB-RNC transmission traffics in time. Even though the CFN is offset by DOFF, the start timing of the interleaving will be the timing that "CFN mod (interleaving size)"=0 (e.g. interleaving size: 2,4,8) in both UE and SRNC.
Information Element/Group name CHOICE mode >FDD >>Default DPCH Offset Value (DOFF) Need Multi Type and reference Semantics description
MP
Integer (0..306688 by step of 512) Integer(0..7)
Number of chips=. 0 to 599 time 512 chips, see [10].
>TDD >>Default DPCH Offset Value (DOFF)
MP
Number of frames; See [10]
10.3.6.17
NOTE:
Downlink channelisation codes

Only for TDD
Need MP MP Enumerated ( (16/1)...(16/1 6)) Enumerated ( (16/1)...(16/1 6)) Bit string(16) If a TFCI exists in this timeslot, it is mapped to the channelisation code as defined in [30]. If this is the same as First channelisation code, only one code is used by the physical layer. Each bit indicates the availability of a channelisation code for SF16, where the channelisation codes are numbered as channelisation code 1 (SF16) to channelisation code 16 (SF16). (For SF 16, a 1 in the bitmap means that the corresponding code is used, a 0 means that the corresponding code is not used.) If all bits are set to zero, SF 1 shall be used. Multi Type and reference Semantics description
Information Element/Group name CHOICE codes representation >Consecutive codes >>First channelisation code
>>Last channelisation code
MP
>Bitmap >>Channelisation codes bitmap
MP
10.3.6.18
Downlink DPCH info common for all RL

Need MP Multi Type and reference Enumerat ed(Initialis Semantics description NOTE Version
Information Element/Group name Timing Indication
3GPP
589 Type and reference e, Maintain) Enumerat ed (false)
Timing maintained Synchronization indicator
CVSynch
FALSE indicates that no synchronisation procedure shall be performed for timing maintained interfrequency hard handover [29]. Absence of this element means that the synchronization procedure A shall be used.
REL-6
Downlink DPCH power control information
OP
MAC-d HFN initial value
CHOICE mode >FDD >>Power offset P PilotDPDCH
CVMessag e MP MP
Downlink DPCH power control informatio n 10.3.6.23 Bit string(24)
REL-4
Integer(0.. 24)
>>Downlink rate matching restriction information
OP
>>Spreading factor
MP
>>Fixed or Flexible Position >>TFCI existence
MP
MP
Downlink rate matching restriction informatio n 10.3.6.31 Integer(4, 8, 16, 32, 64, 128, 256, 512) Enumerat ed (Fixed, Flexible) Boolean
Power offset equals PPilot - PDPDCH, range 0..6 dB, in steps of 0.25 dB If this IE is set to "absent", no Transport CH is restricted in TFI.
TRUE indicates that TFCI is used. When spreading factor is less than or equal to 64, FALSE indicates that TFCI is not used and therefore DTX is used in the TFCI field.
>>CHOICE SF >>>SF = 256 >>>>Number of bits for Pilot bits >>>SF = 128 >>>>Number of bits for Pilot bits >>>Otherwise
MP MP Integer (2,4,8) Integer(4, 8) In bits
MP
In bits (no data). In ASN.1 choice "Otherwise" is not explicitly available as all values are available, it is implied by the use of any value other than 128 or 256. (no data)
>TDD
3GPP
Release 6
590
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE SF SF=128 SF=256 Otherwise
Condition under which the given SF is chosen "Spreading factor" is set to 128 "Spreading factor" is set to 256 "Spreading factor" is set to a value distinct from 128 and 256
Condition Message
Synch
Explanation This IE is not needed if the IE "Downlink DPCH info common for all RL" is included in RRC CONNECTION SETUP or HANDOVER TO UTRAN COMMAND messages. Otherwise it is optional. The IE is not needed in the CELL UPDATE CONFIRM, HANDOVER TO UTRAN COMMAND and the RRC CONNECTION SETUP messages or if the IE "Timing Indication" is set to "Initialise" or if the IE Frequency Info is not included. Otherwise, it is optional.
NOTE:
Within the HANDOVER TO UTRAN COMMAND message, only value "initialise" is applicable.
10.3.6.19
Downlink DPCH info common for all RL Post

Need OP Multi Type and reference Downlink DPCH power control information 10.3.6.23 Semantics description
Information Element/Group name Downlink DPCH power control information
10.3.6.20
Downlink DPCH info common for all RL Pre

Need MP MP Integer(4, 8, 16, 32, 64, 128, 256, 512) Enumerated (Fixed, Flexible) Boolean Defined in CHOICE SF512Andpilot with "number of its for pilot bits" in ASN.1 Multi Type and reference Semantics description
Information Element/Group name CHOICE mode >FDD >>Spreading factor
>>Fixed or Flexible Position
MP
>>TFCI existence
MP
TRUE indicates that TFCI is used. When spreading factor is less than or equal to 64, FALSE indicates that TFCI is not used and therefore DTX is used in the TFCI field.
>>CHOICE SF >>>SF = 256 >>>>Number of bits for Pilot bits >>>SF = 128 >>>>Number of bits for Pilot bits >>>Otherwise >TDD >>Common timeslot info
MP MP Integer (2,4,8) Integer(4,8) In bits
MP
In bits (no data)
MP
Common Timeslot Info 10.3.6.10
3GPP
Release 6
591
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE SF SF=128 SF=256 Otherwise
Condition under which the given SF is chosen "Spreading factor" is set to 128 "Spreading factor" is set to 256 "Spreading factor" is set to a value distinct from 128 and 256
10.3.6.21
Downlink DPCH info for each RL

Need MP MP Primary CPICH usage for channel estimation 10.3.6.62 Integer(0.. 38144 by step of 256) Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>Primary CPICH usage for channel estimation
>>DPCH frame offset
MP
Offset (in number of chips) between the beginning of the PCCPCH frame and the beginning of the DPCH frame This is called DPCH,n in [26]
>>Secondary CPICH info
OP
Secondar y CPICH info 10.3.6.73 1 to <maxDP CHDLchan > For the purpose of physical channel mapping [27] the DPCHs are numbered, starting from DPCH number 1, according to the order that they are contained in this IE. Default is the same scrambling code as for the Primary CPICH
>>DL channelisation code
MP
>>>Secondary scrambling code
MD
>>>Spreading factor
MP
Secondar y scramblin g code 10.3.6.74 Integer(4, 8, 16, 32, 64, 128, 256, 512) Integer(0.. Spreading factor - 1) Enumerat ed (code change, no code change) TPC combinati on index 10.3.6.85 Integer (0..24) Integer(1,
Defined in CHOICE SF512AndCodenumber with "code number" in ASN.1
>>>Code number
MP
>>>Scrambling code change
CH-SF/2
Indicates whether the alternative scrambling code is used for compressed mode method 'SF/2'.
>>TPC combination index
MP
>>Power offset PTPCDPDCH
OP
>>Closed loop timing
CH-
Power offset equals PTPC- PDPDCH, range 0..6 dB, in steps of 0.25 dB It is present if Tx
REL-5
3GPP
Release 6 Information Element/Group name adjustment mode >TDD >>DL CCTrCh List Need TxDivers ity Mode OP 1..<max CCTrCH > Multi
592 Type and reference 2)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Diversity is used in the radio link. DL physical channels to establish or reconfigure list. Identity of this CCTrCh. Default value is 1 Version
>>>TFCS ID >>>Time info >>>Common timeslot info
MD MP MD
>>>Downlink DPCH timeslots and codes
MD
Integer(1.. 8) Time Info 10.3.6.83 Common Timeslot Info 10.3.6.10 Downlink Timeslots and Codes 10.3.6.32 0..<max CCTrCH >
Default is the current Common timeslot info
Default is to use the old timeslots and codes.
>>>UL CCTrCH TPC List
MD
UL CCTrCH identities for TPC commands associated with this DL CCTrCH. Default is previous list or all defined UL CCTrCHs. This list is not required for 1.28 Mcps TDD and is to be ignored by the UE. Transport Format Combinati on Set Identity 10.3.5.21
>>>>UL TPC TFCS Identity
MP
>>DL CCTrCH List to Remove >>>TFCS ID
OP
1..<max CCTrCH > Integer(1.. 8)
DL physical channels to remove list.
MP
Condition SF/2
TxDiversity Mode
Explanation The information element is mandatory present if the UE has a compressed mode pattern sequence configured in variable TGPS_IDENTITY or included in the message including IE "Downlink DPCH info for each RL", which is using compressed mode method "SF/2". Otherwise the IE is not needed. This IE is mandatory present if any TX Diversity Mode is used on the radio link, i.e. if STTD or "closed loop mode 1" is used on the radio link. Otherwise the IE is not needed.
10.3.6.22
Downlink DPCH info for each RL Post

Need MP MP Primary CPICH usage for channel Multi Type and reference Semantics description
Information Element/Group name CHOICE mode >FDD >>Primary CPICH usage for channel estimation
3GPP
593 Multi Type and reference estimation 10.3.6.62 Secondary scrambling code 10.3.6.74 Integer(4, 8, 16, 32, 64, 128, 256, 512) Integer(0.. Spreading factor - 1) Enumerated (code change, no code change) TPC combination index 10.3.6.85 Downlink Timeslots and Codes 10.3.6.32
>>Secondary scrambling code
MD
Default is the same scrambling code as for the Primary CPICH
>>CHOICE Spreading factor
MP
Defined in CHOICE SF512AndCodenumber with "code number" in ASN.1
>>Code number
MP
>>Scrambling code change
CH-SF/2
MP
>TDD >>Downlink DPCH timeslots and codes
MP
Condition SF/2
Explanation The information element is mandatory present if the UE has a compressed mode pattern sequence configured in variable TGPS_IDENTITY or included in the message including IE "Downlink DPCH info for each RL Post", which is using compressed mode method "SF/2". Otherwise the IE is not needed.
10.3.6.23
Downlink DPCH power control information

Need MP MP Enumerated (Single TPC, TPC triplet in soft) Integer (1, 2, 3) "Single TPC" is DPC_Mode=0 and "TPC triplet in soft" is DPC_mode=1 in [29]. Multi Type and reference Semantics description
Information Element/Group name CHOICE mode >FDD >>DPC Mode
>TDD >>TPC Step Size
OP
In dB
10.3.6.23oa Downlink F-DPCH info common for all RL

NOTE: For FDD only.
Information Element/Group name Timing Indication Timing maintained Synchronization
MP CVSynch
Enumerated (Initialise, Maintain) Enumerated (false)
REL-6 FALSE indicates that no REL-6
3GPP
Release 6 Information Element/Group name indicator Need Multi
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description synchronisation procedure shall be performed for timing maintained intra- and interfrequency hard handover [29]. Absence of this element means that the synchronization procedure A shall be used. Version
Downlink F-DPCH power control information TPC command error rate target
OP
MP
Downlink DPCH power control information 10.3.6.23 Real (0.01..0.1 by step of 0.01)
REL-6
REL-6
Condition Synch
Explanation The IE is not needed in the CELL UPDATE CONFIRM, HANDOVER TO UTRAN COMMAND and the RRC CONNECTION SETUP messages or if the IE "Timing Indication" is set to "Initialise". Otherwise, it is optional.
10.3.6.23ob Downlink F-DPCH info for each RL

NOTE: For FDD only.
Need Multi Type and reference Primary CPICH usage for channel estimation 10.3.6.62 Integer (0..38144 by step of 256) Semantics description Version
Information Element/Group name Primary CPICH usage for channel estimation F-DPCH frame offset
MP
REL-6
MP
Offset (in number of chips) between the beginning of the PCCPCH frame and the beginning of the F-DPCH frame This is called F-DPCH,n in [26]
REL-6
Secondary CPICH info Secondary scrambling code
OP MD
Secondary CPICH info 10.3.6.73 Secondary scrambling code 10.3.6.74
REL-6 Default is the same scrambling code as for the Primary CPICH REL-6
Code number TPC combination index STTD indication
MP MP
Integer (0..255) TPC combination index 10.3.6.85 Enumerated (true) This IE shall be set to TRUE
REL-6 REL-6
CVNoHOtoUTRAN
REL-6
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description when STTD is used. Absence of this element means STTD is not used. Version
Condition NoHOtoUTRAN
Explanation This IE is not needed in the HANDOVER TO UTRAN COMMAND and it is optional in all the other messages in which the IE "Downlink F-DPCH info for each RL" can be included.
10.3.6.23a

Need OP Multi Type and reference HS-SCCH Info 10.3.6.36a Measuremen t Feedback Info 10.3.6.40a Semantics description Version REL-5
Information Element/Group name HS-SCCH Info
OP
REL-5
CHOICE mode >TDD >>CHOICE TDD option >>>3.84 Mcps >>>>HS-PDSCH Timeslot Configuration
MP MP OP HS-PDSCH Timeslot Configuratio n 10.3.6.36o HS-PDSCH Midamble Configuratio n 10.3.6.36oo (No data)
REL-5 REL-5 REL-5
>>> 1.28 Mcps >>>> HS-PDSCH Midamble Configuration
OP
REL-5
>FDD
10.3.6.24

Need OP MP Multi Type and reference Downlink DPCH info common for all RL 10.3.6.18 Downlink FDPCH info common for all RL 10.3.6.23oa Semantics description Version REL-6
Information Element/Group name CHOICE DPCH info >Downlink DPCH info common for all RL
>Downlink F-DPCH info common for all RL
MP
REL-6
CHOICE mode >FDD >>DPCH compressed mode info
MP OP DPCH compressed mode info 10.3.6.33
3GPP
Release 6 Information Element/Group name >>TX Diversity Mode Need MD
596 Multi Type and reference TX Diversity Mode 10.3.6.86
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Default value is the existing value of TX Diversity mode (no data) (no data) Version
>TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>1.28 Mcps TDD >>>>TSTD indicator
MP
MP
Default DPCH Offset Value
OP
MAC-hs reset indicator
Post-verification period
CVmessageT ype OP
TSTD indicator 10.3.6.85a Default DPCH Offset Value, 10.3.6.16 Enumerated (true) Enumerated (true)
TRUE Indicates the MAC-hs entity needs to be reset. TRUE indicates that a postverification period shall be used [29]. Absence of this element means that a postverification period shall not be used.
REL-5
REL-6
Condition MessageType
Explanation The IE is not needed in the HANDOVER TO UTRAN COMMAND and the RRC CONNECTION SETUP messages. Otherwise, it is optional.
10.3.6.25
Downlink information common for all radio links Post

Need MP Multi Type and reference Downlink DPCH info common for all RL Post 10.3.6.19 Semantics description
Information Element/Group name Downlink DPCH info common for all RL
10.3.6.26
Downlink information common for all radio links Pre

Need MP Multi Type and reference Downlink DPCH info common for all RL Pre 10.3.6.20 Semantics description
Information Element/Group name Downlink DPCH info common for all RL
3GPP
Release 6
597
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.27
Downlink information for each radio link

Need MP MP Primary CPICH info 10.3.6.60 Cell ID 10.3.2.2 Boolean Multi Type and reference Semantics description Version
Information Element/Group name Choice mode >FDD >>Primary CPICH info
>>Cell ID >>Serving HS-DSCH radio link indicator
OP MP
REL-4 The value "TRUE" indicates that this radio link is the serving HS-DSCH radio link The value "TRUE" indicates that this radio link is the serving E-DCH radio link REL-5
>> Serving E-DCH radio link indicator
MP
Boolean
REL-6
>TDD >>Primary CCPCH info
MP
Primary CCPCH info 10.3.6.57 REL-6 Downlink DPCH info for each RL 10.3.6.21 Downlink FDPCH info for each RL 10.3.6.23ob E-AGCH Info 10.3.6.100 E-HICH Info 10.3.6.101 (no data)
CHOICE DPCH info >Downlink DPCH info for each RL
OP MP
>Downlink F-DPCH info for each RL
MP
REL-6
E-AGCH Info CHOICE E-HICH Information >E-HICH Information >E-HICH release indicator CHOICE E-RGCH Information >E-RGCH Information
OP OP MP
OP MP
E-RGCH Info 10.3.6.102 (no data)
>E-RGCH release indicator
REL-6
10.3.6.28
Downlink information for each radio link Post

Need MP MP Primary CPICH info 10.3.6.60 Cell ID 10.3.2.2 Primary CCPCH info post 10.3.6.58 Downlink DPCH info for each RL Multi Type and reference Semantics description Version
Information Element/Group name Choice mode >FDD >>Primary CPICH info
>>Cell ID >TDD >>Primary CCPCH info
OP
REL-4
MP
Downlink DPCH info for each RL
MP
3GPP
598 Multi Type and reference Post 10.3.6.22
10.3.6.29
Void
10.3.6.30
Void
10.3.6.31
Downlink rate matching restriction information
This IE indicates which TrCH is restricted in TFI.

Information Element/Group name Restricted TrCH information Need OP Multi 1 to <maxTrCH > Enumerated( DCH) Transport channel identity 10.3.5.18 1 to <maxTF> Integer(0..31 ) Type and reference Semantics description
>Downlink transport channel type >Restricted DL TrCH identity
MP MP
>Allowed TFIs >>Allowed TFI
MP MP
10.3.6.32
NOTE:
Downlink Timeslots and Codes

Only for TDD
Need MP Multi Type and reference Individual timeslot info 10.3.6.37 Downlink channelisatio n codes 10.3.6.17 Semantics description Individual timeslot info for the first timeslot used by the physical layer. These codes shall be used by the physical layer in the timeslot given in First Individual timeslot info. (no data)
Information Element/Group name First Individual timeslot info
First timeslot channelisation codes
MP
CHOICE more timeslots >No more timeslots >Consecutive timeslots
MP
3GPP
Release 6 Information Element/Group name >>Number of additional timeslots Need MP
599 Multi Type and reference Integer(1..m axTS-1)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The timeslots used by the physical layer shall be timeslots: N mod maxTS (N+1) mod maxTS ... (N+k) mod maxTS in that order, where N is the timeslot number in the First individual timeslot info and k the Number of additional timeslots. The additional timeslots shall use the same parameters (e.g. channelisation codes, midamble shifts etc.) as the first timeslot. The first instance of this parameter corresponds to the timeslot that shall be used second by the physical layer, the second to the timeslot that shall be used third and so on.
>Timeslot list >>Additional timeslot list
MP
1 to <maxTS1>
>>>CHOICE parameters >>>>Same as last >>>>>Timeslot number
MP MP Timeslot Number 10.3.6.84 The physical layer shall use the same parameters (e.g. channelisation codes, midamble shifts etc.) for this timeslot as for the last one.
>>>>New parameters >>>>>Individual timeslot info
MP
>>>>>Channelisation codes
MP
Individual timeslot info 10.3.6.37 Downlink channelisatio n codes 10.3.6.17
10.3.6.33
NOTE:
DPCH compressed mode info

Only for FDD.
This information element indicates the parameters of the compressed mode to be used by the UE in order to perform inter-frequency and inter-RAT measurements.
Information Element/Group name Transmission gap pattern sequence >TGPSI >TGPS Status Flag Need MP Multi 1 to <maxTGP S> TGPSI 10.3.6.82 Enumerated( activate, deactivate) Type and reference Semantics description
MP MP
This flag indicates whether the Transmission Gap Pattern Sequence shall be activated or deactivated.
3GPP
Release 6 Information Element/Group name >TGCFN Need CV-Active
600 Multi Type and reference Integer (0..255)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Connection Frame Number of the first frame of the first pattern within the Transmission Gap Pattern Sequence.
>Transmission gap pattern sequence configuration parameters >>TGMP
OP
MP
>>TGPRC
MP
Enumerated( TDD measuremen t, FDD measuremen t, GSM carrier RSSI measuremen t, GSM Initial BSIC identification, GSM BSIC reconfirmation, Multi-carrier measuremen t) Integer (1..511, Infinity) Integer (0..14)
Transmission Gap pattern sequence Measurement Purpose.
>>TGSN
MP
>>TGL1
MP
Integer(1..14 )
>>TGL2
MD
Integer (1..14)
>>TGD
MP
Integer(15..2 69, undefined)
The number of transmission gap patterns within the Transmission Gap Pattern Sequence. Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN. The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1. The value of TGL2 shall be ignored if TGD is set to "undefined" Transmission gap distance indicates the number of slots between starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to undefined. The duration of transmission gap pattern 1. Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. Indicates whether normal PC mode or compressed PC mode is applied
>>TGPL1 >>RPP
MP MP
Integer (1..144) Enumerated (mode 0, mode 1).
3GPP
Release 6 Information Element/Group name >>ITP Need MP
601 Multi Type and reference Enumerated (mode 0, mode 1).
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Initial Transmit Power is the uplink power control method to be used to compute the initial transmit power after the compressed mode gap. Compressed mode used in DL only Method for generating downlink compressed mode gap. If F-DPCH is configured this IE shall not be used by the UE Compressed mode used in UL only Method for generating uplink compressed mode gap
>>CHOICE UL/DL mode >>>DL only >>>>Downlink compressed mode method
MP
MP
Enumerated (SF/2, higher layer scheduling)
>>>UL only >>>>Uplink compressed mode method MP Enumerated (SF/2, higher layer scheduling)
>>>UL and DL >>>>Downlink compressed mode method MP Enumerated (SF/2, higher layer scheduling)
Compressed mode used in UL and DL Method for generating downlink compressed mode gap. If F-DPCH is configured this IE shall not be used by the UE Method for generating uplink compressed mode gap
>>>>Uplink compressed mode method
MP
>>Downlink frame type >>DeltaSIR1
MP MP
Enumerated (SF/2, higher layer scheduling) Enumerated (A, B) Real(0..3 by step of 0.1)
>>DeltaSIRafter1
MP
Real(0..3 by step of 0.1)
>>DeltaSIR2
OP
>>DeltaSIRafter2
OP
If F-DPCH is configured this IE shall not be used by the UE Delta in DL SIR target value to be set in the UE during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase). If F-DPCH is configured this IE shall not be used by the UE Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the first transmission gap in the transmission gap pattern. If F-DPCH is configured this IE shall not be used by the UE Delta in DL SIR target value to be set in the UE during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) When omitted, DeltaSIR2 = DeltaSIR1. If F-DPCH is configured this IE shall not be used by the UE Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the second transmission gap in the
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1. If F-DPCH is configured this IE shall not be used by the UE Indicates the maximum number of repeats of patterns that the UE shall use to attempt to decode the unknown BSIC of the GSM cell in the initial BSIC identification procedure Indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure. The time is given in steps of 0.5 seconds.
>>N Identify abort
CV-Initial BSIC
Integer(1..12 8)
>>T Reconfirm abort
CV-Reconfirm BSIC
Real(0.5..10. 0 by step of 0.5)
Condition Active
Initial BSIC
Re-confirm BSIC
Explanation This IE is mandatory present when the value of the IE "TGPS Status Flag" is "Activate" and not needed otherwise. This IE is mandatory present when the value of the IE "TGMP" is set to "GSM Initial BSIC identification" and not needed otherwise. This IE is mandatory present when the value of the IE "TGMP" is set to "GSM BSIC re-confirmation" and not needed otherwise.
10.3.6.34
DPCH Compressed Mode Status Info
This information element indicates status information of the compressed mode used by the UE in order to perform interfrequency and inter-RAT measurements.
Information Element/Group name TGPS reconfiguration CFN Transmission gap pattern sequence >TGPSI Need MP MP 1 to <maxTGP S> TGPSI 10.3.6.82 Enumerated( activate, deactivate) Integer (0..255) Transmission Gap Pattern Sequence Identifier This flag indicates whether the Transmission Gap Pattern Sequence it shall be activated or deactivated. Connection Frame Number of the first frame of the first pattern within the Transmission Gap Pattern Sequence. Multi Type and reference Integer (0..255) Semantics description
MP
>TGPS Status Flag
MP
>TGCFN
CV-Active
Condition Active
Explanation This IE is mandatory present when the value of the IE "TGPS Status Flag" is "Activate" and not needed otherwise.
3GPP
Release 6
603
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.35
Dynamic persistence level

Need MP Multi Type and reference Integer(1..8) Semantics description Level shall be mapped to a dynamic persistence value in the range 0 .. 1. The mapping is described in subclause 8.5.12.
Information Element/Group name Dynamic persistence level
10.3.6.35a
NOTE:
FPACH info

Need MP MP Multi Type and reference Integer(0..6) Enumerated( (16/1)..(16/1 6) Midamble shift and burst type 10.3.6.41 Integer(1..4) Semantics description Version REL-4 REL-4
Information Element/Group name Timeslot number Channelisation code
Midamble Shift and burst type
MP
REL-4
WT
MP
The number of sub-frames, following the subframe in which the SYNC UL is transmitted, in which the FPACH can be transmitted.
REL-4
10.3.6.35b
Frequency band indicator

Need MP Multi Type and reference Enumerated( Band I, Band II, Band III, Band IV, Band V, Band VI, Band VII, extension indicator) Semantics description Version REL-6
Information Element/Group name Frequency band indicator
10.3.6.35c

Need MP Multi Type and reference Enumerated( Band VIII, Band IX, Band X, Band XI, Band XII, Band XIII, Band XIV, Band XV, Band XVI, Semantics description Band X Band XXII are yet to be defined in this version of the specification Version REL-6
Information Element/Group name Frequency band indicator 2
3GPP
604 Multi Type and reference Band XVII, Band XVIII, Band XIX, Band XX, Band XXI, Band XXII, extension indicator)
10.3.6.36
Frequency info
Need MP OP Integer(0..16 383) If this IE is not present, the default duplex distance defined for the operating frequency band shall be used [21] [21] Multi Type and reference Semantics description
Information Element/Group name CHOICE mode >FDD >>UARFCN uplink (Nu)
>>UARFCN downlink (Nd) >TDD >>UARFCN (Nt)
MP
Integer(0 .. 16383) Integer(0 .. 16383)
MP
[22]
10.3.6.36oo HS-PDSCH Midamble Configuration

NOTE: Only for TDD 1.28 Mcps.
Information Element/Group name Midamble Allocation Mode Need MP Multi Type and reference Enumerated( Default midamble, Common midamble, UE specific midamble) Integer(2, 4, 6, 8, 10, 12, 14, 16) Semantics description This midamble allocation mode applies to all HSPDSCH resources assigned to the UE. This configuration applies to all HSPDSCH resources assigned to the UE. This shift, when present, applies to all HS-PDSCH resources assigned to the UE. Version REL-5
Midamble Configuration
MP
REL-5
Midamble Shift
CV-UE
Integer(0..15 )
REL-5
Condition
UE
Explanation This IE is mandatory present when the value of the IE "Midamble Allocation Mode" is "UE specific midamble" and not needed otherwise.
10.3.6.36o
HS-PDSCH Timeslot Configuration
NOTE: Only for TDD 3.84 Mcps.
3GPP
Release 6 Information Element/Group name HS-PDSCH Timeslot Configuration List >Timeslot Number >CHOICE Burst Type >>Type 1 >>>Midamble Allocation Mode Need MP
605 Multi 1 to <maxTS1> Integer (0..14) Type and reference
MP MP MP
>>>Midamble configuration burst type 1 and 3 >>>Midamble Shift >>Type 2 >>>Midamble Allocation Mode
MP CV-UE
Enumerated (Default midamble, Common midamble, UE specific midamble) Integer (4, 8, 16) Integer (0..15) Enumerated (Default midamble, Common midamble, UE specific midamble) Integer (3, 6) Integer (0..5)
As defined in [30]
MP
>>>Midamble configuration burst type 2 >>>Midamble Shift
MP CV-UE
As defined in [30]
REL-5 REL-5
Condition
UE
3GPP
Release 6
606
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.36a
HS-SCCH Info
Need MP MD Secondary scrambling code 10.3.6.74 DL Scrambling code to be applied for HS-DSCH and HS-SCCH. Default is same scrambling code as for the primary CPICH. Multi Type and reference Semantics description Version REL-5 REL-5 REL-5
Information Element/Group name CHOICE mode >FDD >>DL Scrambling Code
>>HS-SCCH Channelisation Code Information >>>HS-SCCH Channelisation Code >TDD >>CHOICE TDD option >>>3.84 Mcps >>>> Ack-Nack Power Offset
MP
1 to <maxHSS CCHs > Integer (0..127)
REL-5
MP
MP MP Integer (-7..8 by step of 1) HS-SICH Power Control Info 10.3.6.36b Real (-3.15..0 by step of 0.05) dB Note
>>>> HS-SICH Power Control Info
MP
REL-5
>>>> BLER target
MP
>>>> Dhs-sync
OP
Integer (20..+10)
Signalled value is Log10(HS-SCCH BLER quality target).This IE is Not Present in REL-5. Value in dB set to indicate the dB difference between the maximum allowed HS-SCCH physical channel transmit power [33] and the beacon reference power (it is one means of controlling the area of HS-DSCH operation within the cell).
REL-6
REL-6
>>>>HS-SCCH Set Configuration >>>>>Timeslot number >>>>>Channelisation code
MP
1 to <maxHSS CCHs> Integer (0..14) Enumerated ((16/1) ..(16/16)) Enumerated (Default midamble, Common midamble, UE specific midamble) Integer
REL-5
MP MP
REL-5 REL-5
>>>>>Midamble Allocation mode
MP
HS-SCCH always uses burst type 1.
REL-5
>>>>>Midamble configuration
MP
REL-5
3GPP
Release 6
607 (4, 8, 16) Integer(0..15 ) Real (-3.15..0 by step of 0.05)
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>Midamble Shift >>>>>BLER target
CV-UE MP
REL-5 Signalled value is Log10(HS-SCCH BLER quality target). This IE is Not Present in REL-6 and beyond. REL-5
>>>>>HS-SICH configuration >>>>>>Timeslot number >>>>>>Channelisation code
MP MP
>>>>>>Midamble Allocation mode
MP
>>>>>>Midamble configuration >>>>>>Midamble Shift
MP CV-UE
Integer (0..14) Enumerated ((16/1) ..(16/16)) Enumerated (Default midamble, UE specific midamble) Integer (4, 8, 16) Integer (0..15)
REL-5 REL-5 REL-5
HS-SICH always uses burst type 1.
REL-5
REL-5 REL-5
>>>1.28 Mcps >>>>Ack-Nack Power Offset
MP
Integer (-7..8 by step of 1)
dB. This IE is Not Present in REL-5. Note dBm. Desired power level for HS-SICH. This IE is Not Present in REL-5 dB. This IE is Not Present in REL-5. Signalled value is Log10(HS-SCCH BLER quality target). This IE is Not Present in REL-5.
REL-5 REL-6
>>>>PRXHS-SICH
MP
Integer (-120..-58 by step of 1)
REL-6
>>>>TPC step size
MP
Integer (1, 2, 3) Real (-3.15..0 by step of 0.05)
REL-6
>>>>BLER target
MP
REL-6
>>>>HS-SCCH Set Configuration >>>>>Timeslot number >>>>>First Channelisation code
MP
1 to <maxHSS CCHs> Integer (0..6) Enumerated ((16/1) ..(16/16)) Enumerated ((16/1) ..(16/16)) Enumerated (Default midamble, Common midamble, UE specific midamble) Integer (0..15)
REL-5
MP MP
REL-5 REL-5
>>>>>Second Channelisation code >>>>>Midamble Allocation mode
MP
REL-5
MP
REL-5
>>>>> Midamble Shift
CV-UE
REL-5
3GPP
Release 6 >>>>>Midamble configuration MP
608 Integer (2, 4, 6, 8, 10, 12, 14, 16) Real (-3.15..0 by step of 0.05)
3GPP TS 25.331 V6.23.0 (2009-09) REL-5
>>>>>BLER target
MP
Signalled value is Log10(HS-SCCH BLER quality target). This IE is Not Present in REL-6.
REL-5
>>>>>HS-SICH configuration >>>>>>Timeslot number >>>>>>Channelisation code
MP MP
>>>>>>Midamble Allocation mode
MP
>>>>>>Midamble configuration
MP
>>>>>>Midamble Shift >>>>>>Ack-Nack Power Offset
CV-UE MP
Integer (0..6) Enumerated ((16/1) ..(16/16)) Enumerated (Default midamble, UE specific midamble) Integer (2, 4, 6, 8, 10, 12, 14, 16) Integer (0..15) Integer (-7..8 by step of 1)
REL-5 REL-5 REL-5
REL-5
REL-5
REL-5 dB. This IE is Not Present in REL-6 and beyond. REL-5
Note dBm. Desired REL-5 power level for HS-SICH. This IE is Not Present in REL-6 and beyond. >>>>>>TPC step size MP Integer dB. This IE is Not REL-5 (1, 2, 3) Present in REL-6 and beyond. Note: Ack-Nack Power Offset is the difference in the desired RX power between HS-SICH transmissions conveying an acknowledgement and transmissions conveying a negative acknowledgement signalled to the UE in IE "HS-SCCH Info". >>>>>>PRXHS-SICH MP Integer (-120..-58 by step of 1)
Condition
UE
10.3.6.36b
HS-SICH Power Control Info
This IE is used to transfer HS-SICH power control info to the UE and only applies to TDD 3.84 Mcps.
Information Element/Group name UL target SIR Need MP Multi Type and reference Real (-11..20 by step of 0.5 ) Constant value TDD 10.3.6.11a Semantics description dB Version REL-5
HS-SICH Constant value
MP
REL-5
3GPP
Release 6
609
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.37
Individual timeslot info

Need MP Multi Type and reference Timeslot number 10.3.6.84 Boolean Semantics description Timeslot within a frame TRUE indicates that the TFCI exists. It shall be coded in the physical channel defined in [30] of this timeslot. Version
Information Element/Group name Timeslot number
TFCI existence
MP
Midamble Shift and burst type
MP
Midamble shift and burst type 10.3.6.41 (no data) REL-4 REL-4 REL-4 REL-4
CHOICE TDD option >3.84 Mcps TDD >1.28 Mcps TDD >>Modulation
MP
MP
>>SS-TPC Symbols
MP
Enumerated( QPSK, 8PSK) Enumerated( 0, 1, 16/SF)
>>Additional TPC-SS Symbols
OP
Integer(1..15 )
Denotes amount of SS and TPC bits send in this timeslot Specifies the number of additional codes in this timeslot that carry TPC and SS symbols as specified in [33]
REL-4
REL-4
10.3.6.38 Individual Timeslot interference

Parameters used by the UE for uplink open loop power control in TDD.
Information element Timeslot number Need MP Multi Type and reference Timeslot number 10.3.6.84 UL Interference TDD 10.3.6.87a Semantics description
UL Timeslot Interference
MP
10.3.6.39
This information element indicates the maximum allowed uplink transmit power.
Information Element Maximum allowed UL TX power Need MP Multi Type and reference Integer(50..33) Semantics description In dBm
3GPP
Release 6
610
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.40 Void
10.3.6.40a

Need MP MP Real (-6 .. 13 by step of 0.5) Integer (0, 2, 4, 8, 10, 20, 40, 80, 160) Integer (1..4) Integer (0..8) The measurement power offset, , in dB, as described in [29]. In milliseconds. Multi Type and reference Semantics description Version REL-5 REL-5 REL-5
Information Element/Group name CHOICE mode >FDD >>Measurement Power Offset
>>CQI Feedback cycle, k
MP
REL-5
>>CQI repetition factor >>CQI
MP MP
REL-5 Refer to quantization of the power offset in [28] (no data) REL-5
>TDD
REL-5
10.3.6.41
NOTE:
Midamble shift and burst type

Only for TDD.
This information element indicates burst type and midamble allocation. Three different midamble allocation schemes exist: Default midamble: the midamble shift is selected by layer 1 depending on the associated channelisation code (DL and UL) Common midamble: the midamble shift is chosen by layer 1 depending on the number of channelisation codes (possible in DL only) UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL).
Information Element/Group name CHOICE TDD option >3.84 Mcps TDD >>CHOICE Burst Type >>>Type 1 >>>>Midamble Allocation Mode Need MP MP MP Enumerated (Default midamble, Common midamble, UE specific midamble) Integer(4, 8, 16) Integer(0..15 ) Enumerated (Default midamble, Common midamble, Multi Type and reference Semantics description Version REL-4 REL-4
>>>>Midamble configuration burst type 1 and 3 >>>>Midamble Shift >>>Type 2 >>>>Midamble Allocation Mode
MP CV-UE
As defined in [30]
MP
3GPP
611 Multi Type and reference UE specific midamble) Integer(3, 6) Integer(0..5) Enumerated (Default midamble, UE specific midamble) Integer(4, 8, 16) Integer (0..15)
>>>>Midamble configuration burst type 2 >>>>Midamble Shift >>>Type 3 >>>>Midamble Allocation Mode
MP CV-UE MP
As defined in [30]
>>>>Midamble configuration burst type 1 and 3 >>>>Midamble Shift
MP CV-UE
As defined in [30] NOTE: Burst Type 3 is only used in uplink. REL-4 REL-4
>1.28 Mcps TDD >>Midamble Allocation Mode
MP
>>Midamble configuration
MP
>>Midamble Shift
CV-UE
Enumerated (Default midamble, Common midamble, UE specific midamble) Integer(2, 4, 6, 8, 10, 12, 14, 16) Integer (0..15)
As defined in [30]
REL-4
REL-4
Condition UE
Explanation This IE is mandatory present when the value of the IE "Midamble Allocation Mode" is "UE-specific midamble" and not needed otherwise.
10.3.6.42
NOTE:
PDSCH Capacity Allocation info

Only for TDD.
Need MP Multi Type and reference Allocation Period Info 10.3.6.4 Semantics description
Information Element/Group name PDSCH allocation period info
CHOICE Configuration >Old configuration >>TFCS ID >>PDSCH Identity
MP MD MP Integer(1..8) Integer(1..hi PDSCHident ities) PDSCH Info 10.3.6.44 Integer(1..hi PDSCHident ities) PDSCH power control info 10.3.6.45 Default is 1.
>New configuration >>PDSCH Info >>PDSCH Identity
MP OP
>>PDSCH power control info
OP
3GPP
Release 6
612
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.43
Void
10.3.6.44
NOTE:
PDSCH info
Only for TDD.
Need MD OP Multi Type and reference Integer(1..8) Common timeslot info 10.3.6.10 Downlink Timeslots and Codes 10.3.6.32 Semantics description TFCS to be used. Default value is 1.
Information Element/Group name TFCS ID Common timeslot info
PDSCH timeslots and codes
OP
10.3.6.45
NOTE:
PDSCH Power Control info

Only for TDD.
Need OP OP 1..<maxCC TrCH> Multi Type and reference Integer (1, 2, 3) Semantics description In dB UL CCTrCH identities for TPC commands associated with this DL CCTrCH. This list is not used in 1.28 Mcps TDD.
Information Element/Group name TPC Step Size UL CCTrCH TPC List
>UL TPC TFCS Identity
MP
Transport Format Combination Set Identity 10.3.5.21
10.3.6.46
NOTE:
PDSCH system information

Only for TDD.
3GPP
Release 6 Information Element/Group name PDSCH information Need MP Multi 1 to <maxPD SCH>
>PDSCH Identity
MP
>PDSCH info
MP
>SFN Time Info
CHBlock17 OP
>DSCH TFS
Integer(1.. hiPDSCHi dentities) PDSCH info 10.3.6.44 SFN Time Info 10.3.6.75 Transport format set 10.3.5.23 1 to <maxTr CH> Transport channel identity 10.3.5.18 Transport format set 10.3.5.23 Transport Format Combinati on Set 10.3.5.20 If PDSCH is configured for 3.84Mcps TDD in Rel-5 this IE may be included. REL-5
>DSCH Transport Channels
OP
>> DSCH Transport channel identity
MP
REL-5
>>DSCH TFS
MP
REL-5
>DSCH TFCS
OP
Condition Block17
Explanation This IE is not needed in System Information Block 17. Otherwise it is optional.
10.3.6.47
Void
10.3.6.48
Persistence scaling factors
This IE defines scaling factors associated with ASC 2 ASC 7 to be applied to the dynamic persistence value.
Information Element/Group name Access Service Class Need MP Multi 1 to maxASCpe rsist Real(0.9..0.2 , by step of 0.1) Type and reference Semantics description multiplicity corresponds to the number of PRACH partitions minus 2 Scaling factors in the range 0,,1
>Persistence scaling factor
MP
10.3.6.49
PICH Info
Need MP MP Integer(0..25 SF is fixed and Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>Channelisation code
3GPP
Release 6
614 5) Integer (18, 36, 72, 144) STTD Indicator 10.3.6.78 Timeslot number 10.3.6.84
3GPP TS 25.331 V6.23.0 (2009-09) equal to 256
>>Number of PI per frame >>STTD indicator
MP MP
>TDD >>Timeslot number
MD
Default value is the timeslot used by the SCCPCH carrying the associated PCH.
>>Midamble shift and burst type
MP
Midamble shift and burst type 10.3.6.41 REL-4 REL-4 Enumerated ( (16/1)...(16/1 6)) Default value is the channelisation code used by the SCCPCH carrying the associated PCH. REL-4 REL-4 REL-4
>>CHOICE TDD option >>>3.84 Mcps TDD >>>>Channelisation code
MP MD
>>>1.28 Mcps TDD >>>>Codes list >>>>>Channelisation code
MP MP
1..2 Enumerated ( (16/1)...(16/1 6)) Enumerated( (4/2),(8/2), (8/4),(16/2), (16/4), (32/2),(32/4), (64/2),(64/4)) Integer (0...Repetitio n period -1) Integer (4, 8, 16)
>>Repetition period/length
MD
Default value is "(64/2)".
>>Offset
MP
>>Paging indicator length
MD
>>NGAP
MD
Integer(2, 4, 8)
>>NPCH
MD
Integer(1 .. 8)
SFN mod Repetitionperiod = Offset. Indicates the length of one paging indicator in Bits. Default value is 4. Number of frames between the last frame carrying PICH for this Paging Occasion and the first frame carrying paging messages for this Paging Occasion. Default value is 4. Number of paging groups. Default value is 2.
10.3.6.50
PICH Power offset
This is the power transmitted on the PICH minus power of the Primary CPICH in FDD and Primary CCPCH Tx Power in TDD.
3GPP
Release 6 Information Element/Group name PICH Power offset Need MP
615 Multi Type and reference Integer(-10 .. +5)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Offset in dB
10.3.6.51
NOTE:
PRACH Channelisation Code List

Need MP MP MP 1 to 8 Enumerated ((16/1)...(16/ 16)) There is a 1:1 mapping between spreading code and midamble shift defined in [30] for channelisation codes (16/1) to (16/8). NOTE: channelisation codes (16/9) to (16/16) are not to be used. Multi Type and reference Semantics description Version
Information Element/Group name CHOICE SF >SF16 >>Channelisation Code List >>>Channelisation code
>SF8 >>Channelisation Code List >>>Channelisation Code
MP MP
1 to 8 Enumerated( (8/1)..(8/8))
10.3.6.51a
NOTE:
PRACH Channelisation Code 1.28 Mcps TDD

Need MP MP Multi 1 to 4 Enumerated( (4/1)..(4/4),(8 /1)..(8/8),(16/ 1)..(16/16)) Type and reference Semantics description Version REL-4 REL-4
Information Element/Group name Channelisation Code List >Channelisation Code
10.3.6.52
PRACH info (for RACH)

Need MP MP Bit string(16) Each bit indicates availability for a signature, where the signatures are numbered "signature 0" up to "signature 15". The value 1 of a bit indicates that the corresponding Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>Available Signature
3GPP
Release 6
616
3GPP TS 25.331 V6.23.0 (2009-09) signature is available and the value 0 that it is not available. In chips per symbol Defines the minimum allowed SF (i.e. the maximum rate) Identification of scrambling code see [28]
>>Available SF
MP
Integer (32,64,128,2 56)
>>Preamble scrambling code number >>Puncturing Limit
MP
Integer (0 .. 15) Real(0.40..1. 00 by step of 0.04) Bit string(12)
MP
>>Available Sub Channel Number
MP
Each bit indicates availability for a subchannel, where the subchannels are numbered "subchannel 0" to "subchannel 11". The value 1 of a bit indicates that the corresponding subchannel is available and the value 0 indicates that it is not available. REL-4 REL-4
>TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>>Timeslot number
MP MP Timeslot number 10.3.6.84 PRACH Channelisati on Code List 10.3.6.51 Enumerated (Direct, Direct/Invert ed) PNBSCH allocation 10.3.8.10a
>>>>PRACH Channelisation Code List
MP
>>>>PRACH Midamble
MP
>>>>PNBSCH allocation
OP
Direct or direct and inverted midamble are used for PRACH Identifies frames used for cell synchronisation purposes
REL-4
>>>1.28 Mcps TDD >>>>SYNC_UL info
MP
SYNC_UL info 10.3.6.78a 1..<maxPR ACH_FPA CH> Timeslot number 10.3.6.84 PRACH Channelisati on Code 1.28 Mcps TDD 10.3.6.51a Midamble shift and
REL-4 REL-4
>>>>PRACH Definition
MP
REL-4
>>>>>Timeslot number
MP
REL-4
>>>>>PRACH Channelisation Code
MP
REL-4
>>>>>Midamble Shift and burst type
MP
REL-4
3GPP
Release 6
617 burst type 10.3.6.41 FPACH info 10.3.6.35a
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>FPACH info
MP
REL-4
10.3.6.53
PRACH partitioning
Need MP Multi 1 to maxASC Type and reference Semantics description If only "NumASC+1" (with, NumASC+1 < maxASC) ASCs are listed, the remaining (NumASC+2 through maxASC) ASCs are unspecified. The default values are same as the previous ASC. If the "default" is used for the first ASC, the default values are all available signatures and "all available subchannels" for FDD and "all available channelisation codes" and "all available subchannels" with "subchannel size=Size 1" in TDD.
Information Element/Group name Access Service class
>ASC Setting
MD
ASC setting 10.3.6.6
10.3.6.54
NOTE:
PRACH power offset

Only for FDD.
Need MP Multi Type and reference Integer (1..8) Semantics description Power step when no acquisition indicator is received in dB Maximum number of preambles in one preamble ramping cycle
Information Element/Group name Power Ramp Step
Preamble Retrans Max
MP
Integer (1..64)
10.3.6.55

Need MP Multi 1 .. <maxPRA CH> PRACH info (for RACH) 10.3.6.52 Transport channel identity 10.3.5.18 Transport format set 10.3.5.23 Type and reference Semantics description Version
Information element PRACH system information
>PRACH info
MP
>Transport channel identity
MP
>RACH TFS
MD
Default value is the value of "RACH TFS" for the previous PRACH in the list NOTE: The first occurrence is then MP). NOTE: For TDD in this release there is a single TF
3GPP
Release 6 Information element Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description within the RACH TFS. Version
>Additional RACH TFS for CCCH
OP
>RACH TFCS
MD
Additional Dynamic Transport Format Information for CCCH 10.3.5.2a Transport Format Combination Set 10.3.5.20
FDD only
REL-6
Default value is the value of "RACH TFCS" for the previous PRACH in the list. NOTE: The first occurrence is then MP). NOTE: For TDD in this release there is no TFCS required. REL-6
>Additional RACH TFCS for CCCH
CV-AddRACH-TFS
>PRACH partitioning
MD
Additional RACH TFCS for CCCH 10.3.5.2b PRACH partitioning 10.3.6.53
>Persistence scaling factors
OP
Persistence scaling factors 10.3.6.48
>AC-to-ASC mapping
CV-SIB5MD
AC-to-ASC mapping 10.3.6.1
Default value is the value of "PRACH partitioning" for the previous PRACH in the list (note : the first occurrence is then MP) This IE shall not be present if only ASC 0 and ASC 1 are defined. If this IE is absent, value is the value of "Persistence scaling factors" for the previous PRACH in the list if value exists Only present in SIB 5 and in SIB 5bis. Default value is the value of "AC-to-ASC mapping" for the previous PRACH in the list. NOTE: The first occurrence is then MP in SIB5 and in SIB5bis.
>CHOICE mode >>FDD >>>Primary CPICH TX power
MP MD Primary CPICH TX power 10.3.6.61 Constant value 10.3.6.11 Default value is the value of "Primary CPICH TX power" for the previous PRACH in the list. NOTE: The first occurrence is then MP. Default value is the value of "Constant value" for the previous PRACH in the list. NOTE: The first occurrence is then MP. Default value is the value of "PRACH power offset" for the previous PRACH in the list. NOTE: The first occurrence is then MP. Default value is the value of "RACH transmission parameters" for the previous PRACH in the list. NOTE: The first occurrence is then MP. Default value is the value of "AICH info" for the previous
>>>Constant value
MD
>>>PRACH power offset
MD
PRACH power offset 10.3.6.54
>>>RACH transmission parameters
MD
RACH transmission parameters 10.3.6.67
>>>AICH info
MD
AICH info 10.3.6.2
3GPP
Release 6 Information element Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description PRACH in the list. NOTE: The first occurrence is then MP. (no data) Version
>>TDD
Condition SIB5-MD
Add-RACH-TFS
Explanation The information element is present only in SIB 5 and in SIB5bis. In SIB 5 and in SIB 5bis it is mandatory with default. The information element is MP if the IE "Additional RACH TFS for CCCH" is included. Otherwise the information element is not needed.
NOTE:
If the setting of the PRACH information results in that a combination of a signature, preamble scrambling code and subchannel corresponds to a RACH with different TFS and/or TFCS, then for that combination only the TFS/TFCS of the PRACH listed first is valid, where PRACHs listed in System Information Block type 5 or 5bis shall be counted first.
10.3.6.56
Predefined PhyCH configuration
This information element concerns a predefined configuration of physical channel parameters.
Information Element/Group name Uplink radio resources Uplink DPCH info Need Multi Type and Reference Uplink DPCH info Pre 10.3.6.90 Downlink information common for all radio links Pre 10.3.6.26 Semantics description
MP
Downlink radio resources Downlink information common for all radio links
OP
10.3.6.57
Primary CCPCH info

Need MP MP Boolean TRUE indicates that transmit diversity is used. REL-4 REL-4 Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>TX Diversity indicator
>TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>>>CHOICE SyncCase >>>>>Sync Case 1 >>>>>>Timeslot >>>>>Sync Case 2 >>>>>>Timeslot >>>1.28 Mcps TDD >>>>TSTD indicator
MP OP MP Integer (0...14) Integer(0..6) TSTD indicator 10.3.6.85a Cell PCCPCH timeslot
MP MP
REL-4 REL-4
>>Cell parameters ID
OP
The Cell
3GPP
620 Multi Type and reference parameters Id 10.3.6.9 SCTD indicator 10.3.6.70a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description parameters ID is described in [32]. Version
>>SCTD indicator
MP
10.3.6.58
NOTE:
Primary CCPCH info post

Only for TDD
Need MP MP MP Integer (0...14) Integer(0..6) TSTD indicator 10.3.6.85a Cell parameters Id 10.3.6.9 SCTD indicator 10.3.6.70a REL-4 REL-4 PCCPCH timeslot Multi Type and reference Semantics description Version REL-4 REL-4
Information Element/Group name CHOICE TDD option >3.84 Mcps TDD >>CHOICE SyncCase >>>Sync Case 1 >>>>Timeslot >>>Sync Case 2 >>>>Timeslot >1.28 Mcps TDD >>TSTD indicator
MP MP
Cell parameters ID
MP
The Cell parameters ID is described in [32].
SCTD indicator
MP
10.3.6.59
NOTE:
Primary CCPCH TX Power

Only for TDD.
Need MP Multi Type and reference Integer(6..43 ) Semantics description In dBm
Information Element/group name Primary CCPCH Tx Power
10.3.6.60
NOTE:
Primary CPICH info

Only for FDD.
Need MP Multi Type and reference Integer(0..51 1) Semantics description
Information Element/Group name Primary scrambling code
10.3.6.61
NOTE:
Primary CPICH Tx power

Only for FDD.
Need MP Multi Type and reference Integer(10..50) Semantics description Power in dBm.
Information Element/Group name Primary CPICH Tx Power
3GPP
Release 6
621
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.62
NOTE:
Primary CPICH usage for channel estimation

Only for FDD.
Need MP Multi Type and Reference Enumerated( Primary CPICH may be used, Primary CPICH shall not be used) Semantics description
Information Element/Group name Primary CPICH usage for channel estimation
10.3.6.63
NOTE:
PUSCH info
Only for TDD.
Need MD OP Multi Type and reference Integer(1..8) Common timeslot info 10.3.6.10 Uplink Timeslots and Codes 10.3.6.94 Semantics description Default value is 1
Information Element/Group name TFCS ID Common timeslot info
PUSCH timeslots and codes
OP
10.3.6.64
NOTE:
PUSCH Capacity Allocation info

Only for TDD.
Need MP (no data) MP Allocation Period Info 10.3.6.4 PUSCH power control info 10.3.6.65 Multi Type and reference Semantics description
Information Element/Group name CHOICE PUSCH allocation >PUSCH allocation pending >PUSCH allocation assignment >>PUSCH allocation period info
>>PUSCH power control info
OP
>>CHOICE Configuration >>>Old configuration >>>>TFCS ID >>>>PUSCH Identity
MP MD MP Integer(1..8) Integer(1..hi PUSCHident ities) PUSCH info 10.3.6.63 Integer(1.. hiPUSCHide ntities) Default is 1.
>>>New configuration >>>>PUSCH info >>>>PUSCH Identity
MP OP
10.3.6.65
NOTE:
PUSCH power control info

Only for TDD.
3GPP
Release 6
622
3GPP TS 25.331 V6.23.0 (2009-09)
Interference level measured for a frequency at the UTRAN access point used by UE to set PUSCH output power.
Information Element/Group name UL target SIR Need MP Multi Type and reference Real (-11 .. 20 by step of 0.5 dB) Semantics description For 1.28 Mcps TDD this parameter represents PRXPUSCHdes with range Integer(-120-58 by step of 1) dBm (no data) OP OP Integer (1, 2, 3) Enumerated (true) In dB The presence of this IE indicates that the UE may take into account path loss estimated from beacon function physical channels. The absence indicates that UE may not take into account path loss estimated from beacon function physical channels Version
REL-4
CHOICE TDD option >3.84 Mcps TDD >1.28 Mcps TDD >>TPC Step Size >>Beacon PL Est.
MP
10.3.6.66
NOTE:
PUSCH system information

Only for TDD.
Need MP Multi 1 to <maxPU SCH> Integer(1.. hiPUSCHi dentities) PUSCH info 10.3.6.63 SFN Time Info 10.3.6.75 Transport format set 10.3.5.23 Type and reference Semantics description Version
Information Element/Group name PUSCH information
>PUSCH Identity
MP
>PUSCH info
MP
>SFN Time Info
CHBlock17 OP
>USCH TFS
3GPP
Release 6 Information Element/Group name >USCH Transport Channels Need OP Multi 1 to <maxTr CH>
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description If PUSCH is configured for 3.84 Mcps TDD in Rel-5 this IE may be included. Version REL-5
>> USCH Transport channel identity
MP
>>USCH TFS
MP
>USCH TFCS
OP
Transport channel identity 10.3.5.18 Transport format set 10.3.5.23 Transport Format Combinati on Set 10.3.5.20
REL-5
REL-5
Condition Block17
Explanation This IE is not needed in System Information Block 17. Otherwise it is optional.
10.3.6.67
NOTE:
RACH transmission parameters

Only for FDD.
Need MP MP MP Multi Type and reference Integer(1..32 ) Integer(0..50 ) Integer(0..50 ) Semantics description Maximum number of preamble cycles Sets lower bound for random back-off Sets upper bound for random back-off
Information Element/Group name Mmax NB01min NB01max
10.3.6.68
Radio link addition information

Need MP Multi Type and reference Primary CPICH info 10.3.6.60 Cell ID 10.3.2.2 Downlink DPCH info for each RL 10.3.6.21 Downlink FF-DPCH info for each RL 10.3.6.23ob E-HICH Info 10.3.6.101 E-RGCH Info 10.3.6.102 Semantics description Version
Information Element/Group name Primary CPICH info
Cell ID CHOICE DPCH info >Downlink DPCH info for each RL
OP MP MP
REL-4 REL-6
>Downlink F-DPCH info for each RL
MP
REL-6
E-HICH Information E-RGCH Information
OP OP
REL-6 REL-6
3GPP
Release 6
624
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.69
Radio link removal information

Need MP Multi Type and reference Primary CPICH info 10.3.6.60 Semantics description
Information Element/Group name Primary CPICH info
10.3.6.69a
E-DCH reconfiguration information

Need OP MP Multi Type and reference Primary CPICH info 10.3.6.60 E-AGCH Info 10.3.6.100 Semantics description Indicates scheduling E-DCH cell from the active set cells. Version REL-6 REL-6
Information Element/Group name E-DCH RL Info new serving cell >Primary CPICH info
>E-AGCH Info
MP
REL-6
3GPP
Release 6 Information Element/Group name >Serving Grant >>Serving Grant value Need OP OP
625 Multi Type and reference Integer (0..37,38)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description (0..37) indicates E-DCH serving grant index as defined in [15]; index 38 means zero grant. Indicates whether the Serving Grant is received with a Primary E-RNTI or Secondary ERNTI. Refer to quantization of the power offset in [28]. See [29]. Version REL-6 REL-6
>>Primary/Secondary Grant Selector
MP
Enumerated (primary, secondary)
REL-6
>E-DPCCH/DPCCH power offset
OP
Integer (0..8)
REL-6
>Reference E-TFCIs >>Reference E-TFCI >>Reference E-TFCI PO
OP MP MP
1 to 8 Integer (0..127) Integer (0..29)
REL-6 REL-6 REL-6
>Power Offset for Scheduling Info
OP
Integer (0..6)
>3-Index-Step Threshold
OP
Integer (0..37)
>2-Index-Step Threshold
OP
Integer (0..37)
>E-HICH Information
OP
E-HICH Info 10.3.6.101
>CHOICE E-RGCH Information
OP
Refer to quantization of the power offset in [28]. Only used when no MACd PDUs are included in the same MACe PDU. Unit is in dB. Refers to an index in the SG-Table (see [15]). NOTE 1 Refers to an index in the SG-Table (see [15]). NOTE 1 This IE is not present if the serving E-DCH cell is added to the active set with this message. This IE is not present if the serving E-DCH cell is added to the active set with this message
REL-6
REL-6
REL-6
REL-6
REL-6
>>E-RGCH Information
MP
E-RGCH Info 10.3.6.102 1 to <maxEDC HRL> (no data) This IE is not allowed to include information on a RL added by this message Primary CPICH info 10.3.6.60 E-HICH Info 10.3.6.101 (no data)
REL-6
>>E-RGCH release indicator E-DCH RL Info other cells
OP
REL-6 REL-6
>Primary CPICH info
MP
REL-6
>CHOICE E-HICH Information >>E-HICH Information >>E-HICH release indicator
OP MP
REL-6 REL-6 REL-6
3GPP
Release 6 Information Element/Group name >CHOICE E-RGCH Information >>E-RGCH Information Need OP MP
626 Multi Type and reference E-RGCH Info 10.3.6.102
>>E-RGCH release indicator (no data) REL-6 NOTE 1: If the 3-index-Step Threshold value is greater than 2-index-Step Threshold, the UE behaviour is unspecified.
10.3.6.70
Void
10.3.6.70a
NOTE:
SCTD indicator
Only for TDD

Need MP Multi Type and reference Boolean Semantics description TRUE indicates that SCTD is used
Information Element/Group name SCTD indicator
3GPP
Release 6
627
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.71
Secondary CCPCH info

Need MP OP Secondary scrambling code 10.3.6.74 STTD Indicator 10.3.6.78 Integer(4, 8, 16, 32, 64, 128, 256) Integer(0..Sp reading factor - 1) Boolean Boolean May only be sent for SCCPCH channels not carrying the PCH. Multi Type and reference Semantics description
Information Element/Group name CHOICE mode >FDD >>Secondary scrambling code
>>STTD indicator
MP
>>Spreading factor
MP
>>Code number
MP
>>Pilot symbol existence >>TFCI existence
MP MP
TRUE means the existence. TRUE indicates that TFCI is used. When spreading factor is less than or equal to 64, FALSE indicates that TFCI is not used and therefore DTX is used in the TFCI field.
>>Fixed or Flexible Position
MP
>>Timing Offset
MD
Enumerated (Fixed, Flexible) Integer(0..38 144 by step of 256)
Chip Delay of the Secondary CCPCH relative to the Primary CCPCH. Default value is 0. SFN modulo Repetition period = offset. Repetition period is the one indicated in the accompanying Common timeslot info IE
>TDD >>Offset
MP
Integer (0...Repetitio n Period -1)
>>Common timeslot info
MP
>>Individual timeslot info
MP
Common timeslot info 10.3.6.10 Individual timeslot info 10.3.6.37 1 to 16 Enumerated( (16/1)..(16/1 6))
>>Code List >>>Channelisation Code
MP MP
3GPP
Release 6
628
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.71a
Secondary CCPCH info MBMS

Need MP OP Secondary scrambling code 10.3.6.74 STTD Indicator 10.3.6.78 Integer(4, 8, 16, 32, 64, 128, 256) Integer(0..Sp reading factor 1) Integer(0..38 144 by step of 256) May only be sent for SCCPCH channels not carrying the PCH. Multi Type and reference Semantics description Version REL-6 REL-6 REL-6
Information Element/Group name CHOICE mode >FDD >>Secondary scrambling code
>>STTD indicator
MP
REL-6
>>Spreading factor
MP
REL-6
>>Code number
MP
REL-6
>>Timing Offset
MD
Chip Delay of the Secondary CCPCH relative to the Primary CCPCH. Default value is 0. Interleaving mode, TFCI coding and puncturing limit for Secondary CCPCH info MBMS One or more timeslots and codes for S-CCPCH supporting MBMS MTCHSFN
REL-6
>TDD >>Common timeslot info MBMS
MP
Common timeslot info MBMS 10.3.6.10a Downlink timeslots and codes 10.3.6.32
REL-6 REL-6
>>Downlink Timeslots and Codes
MP
REL-6
NOTE:
For FDD, the S-CCPCH signalled in this IE is always configured with flexible position, TFCI is always present and pilot is always absent.
3GPP
Release 6
629
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.72

Need MP Multi 1 to <maxSCC PCH> Secondary CCPCH info 10.3.6.71 Transport format combination set 10.3.5.20 Note 1 Type and reference Semantics description Version
Information element Secondary CCPCH system information list >Secondary CCPCH info
MP
>TFCS
MD
>FACH/PCH information list
MD
1 to <maxFAC HPCH>
>>TFS
MP
>>Transport channel identity
MP
>>CTCH indicator
MP
Transport format set 10.3.5.23 Transport channel identity 10.3.5.18 Boolean
For FACHs and PCH Default value is the value of "TFCS" for the previous SCCPCH in the list. NOTE: The first occurrence is then MP. Default value is the value of "FACH/PCH" for the previous SCCPCH in the list. NOTE: The first occurrence is then MP. For each FACH and PCH Note 2
>PICH info
OP
PICH info 10.3.6.49 MCCH configuration information 10.3.9a.13
CV-SIB type 5
The value "TRUE" indicates that a CTCH is mapped on the FACH, and "FALSE" that no CTCH is mapped. PICH info is present only when PCH is multiplexed on Secondary CCPCH Included if MCCH is on an SCCPCH used also for NonMBMS Note 3
REL-6
NOTE 1: The secondary CCPCHs carrying a PCH shall be listed first. NOTE 2: TFS for PCH shall be the first "FACH/PCH information" in the list if a PCH exists for the respective secondary CCPCH. NOTE 3: If the IE "MCCH configuration information is included", it applies to the last S-CCPCH in the IE "Secondary CCPCH system information list" and to the last FACH included in the IE "FACH/PCH information list".
Condition SIB type 5 Explanation The IE is optional if the IE " Secondary CCPCH system information" is included in the SIB type 5 or 5bis, otherwise the IE is not needed in the message
3GPP
Release 6
630
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.72a
Secondary CCPCH system information MBMS

Need MP Multi Type and reference Semantics description An S-CCPCH carrying MCCH and possibly also MTCH and MSCH Secondary CCPCH info MBMS 10.3.6.71a Transport format combination set 10.3.5.20 Transport format set 10.3.5.23 MCCH configuration information 10.3.9a.13 1 to <maxFAC HPCH> Transport format set 10.3.5.23 Transport format set 10.3.5.23 Transport channel carrying MSCH Version REL-6
Information element Secondary CCPCH system information >Secondary CCPCH info MBMS
MP
REL-6
>TFCS
MP
REL-6
>FACH carrying MCCH >>TFS
MP MP
REL-6 REL-6
>>MCCH configuration information
MP
REL-6
>FACH carrying MTCH list
OP
REL-6
>>TFS
MP
REL-6
>Scheduling information >>FACH carrying MSCH
OP MP
REL-6 REL-6
10.3.6.73
NOTE:
Secondary CPICH info

Only for FDD.
Need MD Multi Type and reference Secondary scrambling code 10.3.6.74 Integer(0..25 5) Semantics description Default is the same scrambling code as for the Primary CPICH
Information Element/Group name Secondary scrambling code
Channelisation code
MP
SF=256
10.3.6.74
Secondary scrambling code

Need MP Multi Type and reference Integer(1..15 ) Semantics description
Information Element/Group name Secondary scrambling code
3GPP
Release 6
631
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.74a
Serving HS-DSCH cell information

Need OP OP MP Multi Type and reference Integer(0..8) Integer(0..8) Integer(0, 1) Semantics description Refer to quantization of the power offset in [28] Refer to quantization of the power offset in [28] 1 indicates that preamble and postamble are used on the HSDPCCH see [29] Indicate the new HS-DSCH serving cell Version REL-6 REL-6 REL-6
Information Element/Group name ACK NACK HARQ_preamble_mode
Primary CPICH info
OP
OP
HARQ Info MAC-hs reset indicator
OP OP
Primary CPICH info 10.3.6.60 Downlink HS_PDSCH Information 10.3.6.23a HARQ info 10.3.5.7a Enumerated (true)
REL-6
REL-6
REL-6 TRUE Indicates the MAC-hs entity needs to be reset. REL-6
10.3.6.75
SFN Time info

Need MP Multi Type and reference Integer (0..4095) Integer(1..40 96) Semantics description System frame number start of the physical channel existence. Total number of frames the physical channel will exist.
Information Element/Group name Activation time SFN
Duration
MP
10.3.6.75a
NOTE:
Special Burst Scheduling
Only for TDD.

Need MP Multi Type and reference Integer (0..7) Semantics description Value represents number of radio frames 0 = 2 frames, 1 = 4 frames, 2 = 8 frames, 3 = 16 frames, 4 = 32 frames, 5 = 64 frames, 6 = 128 frames, 7 =256 frames
Information Element/Group name Special Burst Generation Period
10.3.6.76
Void
10.3.6.77
Void
10.3.6.78
NOTE:
STTD indicator
Only for FDD
3GPP
Release 6
632
3GPP TS 25.331 V6.23.0 (2009-09)
Indicates whether STTD is used or not.

Information Element/Group name STTD Indicator Need MP Multi Type and reference Boolean Semantics description TRUE means that STTD is used
10.3.6.78a
NOTE:
SYNC_UL info

Need MP Multi Type and reference Bitstring(8) Semantics description Each bit indicates availability of a SYNC_UL code, where the SYNC_UL codes are numbered "code 0" to "code 7". The value 1 of a bit indicates that the corresponding SYNC_UL code can be used. The value 0 of a bit indicates that the corresponding SYNC_UL code can not be used. In dBm Version REL-4
Information Element/ Group name SYNC_UL codes bitmap
PRXUpPCHdes
MP
Power Ramp Step Max SYNC_UL Transmissions
MP MP
Integer(120-58 by step of 1) Integer(0,1,2 ,3) Integer(1,2,4 ,8)
REL-4
In dB Maximum numbers of SYNC_UL transmissions in a power ramping sequence. Maximum number of synchronisation attempts.
REL-4 REL-4
Mmax
MP
Integer(1..32 )
REL-4
10.3.6.79
TDD open loop power control
This information element contains parameters for open loop power control setting for TDD.
Information Element/Group name Primary CCPCH Tx Power Need MP Multi Type and reference Primary CCPCH Tx Power 10.3.6.59 Semantics description For path loss calculation Version
CHOICE TDD option >3.84 Mcps TDD >>Alpha >>PRACH Constant Value
MP OP MP Alpha 10.3.6.5 Constant Value TDD 10.3.6.11a Constant
REL-4 REL-4
>>DPCH Constant Value
MP
Operator controlled PRACH Margin Operator
3GPP
633 Multi Type and reference Value TDD 10.3.6.11a Constant Value TDD 10.3.6.11a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description controlled UL DPCH Margin Operator controlled PUSCH Margin Version
>>PUSCH Constant Value
OP
>>UE positioning related parameters >>>IPDL-Alpha >>>Max power increase >1.28 Mcps TDD
CV-IPDLs MP MP Alpha 10.3.6.5 Integer (0..3)
REL-4 REL-4 In db (no data) REL-4 REL-4
Condition IPDLs
Explanation This IE is present only if idle periods are applied
10.3.6.80
TFC Control duration

Need MP Multi Type and reference Integer (1, 2, 4, 8, 16, 24, 32, 48, 64, 128, 192, 256, 512) Semantics description Defines the period in multiples of 10 ms frames for which the defined TFC sub-set is to be applied.
Information Element/Group name TFC Control duration
10.3.6.81
Void
10.3.6.82
TGPSI
Need MP Multi Type and reference Integer(1..M axTGPS) Semantics description Transmission Gap Pattern Sequence Identifier Establish a reference to the compressed mode pattern sequence. Up to <MaxTGPS> simultaneous compressed mode pattern sequences can be used.
Information Element/Group name TGPSI
10.3.6.83
Time info
Need MD Multi Type and reference Activation time 10.3.3.1 Integer(1..40 96, infinite) Semantics description Frame number start of the physical channel existence. Default value is "Now" Total number of frames the physical channel will exist. Default value is "infinite".
Information Element/Group name Activation time
Duration
MD
10.3.6.84
Timeslot number
Information Element/Group name
3GPP
Release 6 Information Element/Group name CHOICE TDD option >3.84 Mcps TDD >>Timeslot number >1.28 Mcps TDD >>Timeslot number Need MP MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Version REL-4 REL-4 Integer(0..14 ) Integer(0..6) Timeslot within a frame Timeslot within a subframe REL-4 REL-4
MP
10.3.6.85
NOTE:
TPC combination index

Only for FDD.
Need MP Multi Type and reference Integer(0.. 5) Semantics description Radio links with the same index have TPC bits, which for the UE are known to be the same. Radio links that are part of the E-DCH active set and with the same index have acknowledgement feedback signals on the E-HICH which for the UE are known to be the same. Version
Information Element/Group name TPC combination index
REL-6
10.3.6.85a
NOTE:
TSTD indicator

Need MD Multi Type and reference Boolean Semantics description Default value is "TRUE" Version REL-4
Information Element/Group name TSTD indicator
10.3.6.86
NOTE:
TX Diversity Mode
Only for FDD.
Need MP Multi Type and reference Enumerated (none, STTD, closed loop mode1) Semantics description
Information Element/Group name Tx diversity Mode
10.3.6.87
UL interference
Need MP Multi Type and reference Integer (110..-70) Semantics description In dBm
Information Element/Group name UL interference
NOTE:
In TDD, this IE is a timeslot specific value.
3GPP
Release 6
635
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.87a
NOTE:
UL interference TDD
Only for TDD.

Need MP Multi Type and reference Integer (110..-52) Semantics description In dBm
Information Element/Group name TDD UL interference
NOTE:
This IE is a timeslot specific value.
3GPP
Release 6
636
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.88
Uplink DPCH info

Need OP Multi Type and reference Uplink DPCH power control info 10.3.6.91 Semantics description Version
Information Element/Group name Uplink DPCH power control info
CHOICE mode >FDD >>Scrambling code type
MP MP Enumerat ed(short, long) Integer(0.. 16777215 ) Integer(1.. maxDPD CH-UL, 0)
>>Scrambling code number >>Number of DPDCH
MP
MD
Default value is 1. Number of DPDCH is 1 in HANDOVER TO UTRAN COMMAND. Value 0 may only be used if target configuration has no uplink DPDCH. Minimum allowed SF of the channelisation code for data part TRUE means existence. In bits. REL-6
>>Spreading factor
CVDPDCH present MP OP CVDPDCH present
>>TFCI existence >>Number of FBI bits >>Puncturing Limit
Integer(4, 8, 16, 32, 64, 128, 256) Boolean Integer (1, 2) Real(0.40 ..1 by step of 0.04) Uplink Timing Advance Control 10.3.6.96 1 to <maxCC TrCH> Integer(1.. 8) Real (-11 .. 20 by step of 0.5dB)
>TDD >>Uplink Timing Advance Control
OP
>>UL CCTrCH List
OP
>>>TFCS ID >>>UL target SIR
MD MP
UL physical channels to establish or reconfigure list. Default value is 1. In dB For 1.28 Mcps TDD this parameter represents PRXDPCHdes with range Integer(-12058 by step of 1) dBm
REL-4
>>>Time info >>>Common timeslot info
MP MD
>>>Uplink DPCH timeslots and codes
MD
Time info 10.3.6.83 Common timeslot info 10.3.6.10 Uplink Timeslots and Codes 10.3.6.94
Default is the current Common timeslot info
3GPP
Release 6 Information Element/Group name >>UL CCTrCH List to Remove >>>TFCS ID Need OP Multi 1..<max CCTrCH >
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description UL physical channels to remove list Version
MP
Integer(1.. 8)
Condition DPDCHpresent
Explanation This IE is mandatory if the target configuration includes a DPDCH, otherwise it is not needed.
10.3.6.89
Uplink DPCH info Post

Need MP Multi Type and reference Uplink DPCH power control info Post 10.3.6.92 Semantics description
CHOICE mode >FDD >>Scrambling code type >>Reduced scrambling code number >>Spreading factor
MP MP MP MP Enumerated( short, long) Integer(0..81 91) Integer(4, 8, 16, 32, 64, 128, 256)
Sub-range of values for initial use upon handover to UTRAN. SF of the channelisation code for data part There is only one DPDCH for this case
>TDD >>Uplink Timing Advance Control
OP
>>Uplink DPCH timeslots and codes
MP
Uplink Timing Advance Control 10.3.6.96 Uplink Timeslots and Codes 10.3.6.94
10.3.6.90
Uplink DPCH info Pre

Need OP Multi Type and reference Uplink DPCH power control info Pre 10.3.6.93 Semantics description
CHOICE mode >FDD >>TFCI existence >>Puncturing Limit
MP MP MP Boolean Real(0.40 ..1 by step of 0.04) Common Timeslot Info 10.3.6.10 TRUE means existence. Default value is "TRUE"
>TDD >>Common timeslot info
MP
3GPP
Release 6 Condition Single
638
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation This IE is mandatory present if the IE "Number of DPDCH" is "1" and not needed otherwise.
10.3.6.91
Parameters used by UE to set DPCH initial output power and to use for closed-loop power control in FDD and 1.28 Mcps TDD and parameters for uplink open loop power control in 3.84 Mcps TDD.
Information Element/Group name CHOICE mode >FDD >>DPCCH Power offset Need MP MP Integer(164,..-6 by step of 2) Integer (0..7) Integer(0..7) Enumerated (algorithm 1, algorithm 2) In dB Multi Type and reference Semantics description Version
>>PC Preamble >>SRB delay >>Power Control Algorithm
MP MP MP
>>TPC step size >>ACK
CV-algo OP
Integer (1, 2) Integer (0..8)
>>NACK
OP
Integer (0..8)
In number of frames In number of frames Specifies algorithm to be used by UE to interpret TPC commands In dB Refer to quantization of the power offset in [28] refer to quantization of the power offset in [28] 1 indicates that preamble and postamble are used on the HSDPCCH see [29] In dB For 1.28 Mcps TDD this parameter represents PRXDPCHdes with range Integer(120-58 by step of 1) dBm No data
REL-5
REL-5
>>Ack-Nack repetition factor >>HARQ_preamble_mode
OP MP
Integer(1..4) Integer (0, 1)
REL-5 REL-6
>TDD >>>>UL target SIR
OP
Real (-11 .. 20 by step of 0.5dB)
REL-4
>>CHOICE UL OL PC info >>>Broadcast UL OL PC info >>>Individually Signalled >>>>CHOICE TDD option >>>>>3.84 Mcps TDD >>>>>>Individual timeslot interference info >>>>>>>Individual timeslot interference
MP Null OP MP MP MP 1 to <maxTS> Individual timeslot interference 10.3.6.38 Constant Value TDD 10.3.6.11a
REL-4 REL-4
>>>>>>DPCH Constant Value
OP
Quality Margin
>>>>>1.28 Mcps TDD
REL-4
3GPP
Release 6 Information Element/Group name >>>>>>Beacon PL Est. Need CVhoutran
639 Multi Type and reference Enumerated (true)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The presence of this IE indicates that the UE may take into account path loss estimated from beacon function physical channels. The absence indicates that UE may not take into account path loss estimated from beacon function physical channels Version REL-6
>>>>>>TPC step size >>>>Primary CCPCH Tx Power
MP OP
Integer(1,2,3 ) Primary CCPCH Tx Power 10.3.6.59
REL-4 For Pathloss Calculation
Condition algo
houtran
Explanation The IE is mandatory present if the IE "Power Control Algorithm" is set to "algorithm 1", otherwise the IE is not needed This IE is optional in Cell Update Confirm, Physical Channel Reconfiguration, Radio Bearer Reconfiguration, Radio Bearer Release, Radio Bearer Setup, Transport Channel Reconfiguration and Uplink Physical Channel Control. The IE is not included in the Handover To UTRAN Command
10.3.6.92
Uplink DPCH power control info Post
Parameters used by UE to set DPCH initial output power and to use for closed-loop power control.
Information Element/Group name CHOICE mode >FDD >>DPCCH Power offset Need MP MP Integer(110..-50 by step of 4) Integer (0..7) Integer (0..7) In dB Multi Type and reference Semantics description Version
>>PC Preamble >>SRB delay >TDD >>UL target SIR
MP MP
in number of frames In number of frames In dB For 1.28 Mcps TDD this parameter represents PRXDPCHdes with range Integer(120-58 by step of 1) dBm
MP
Real (-11 .. 20 by step of 0.5dB)
REL-4
>>CHOICE TDD option >>>3.84 Mcps TDD >>>>UL Timeslot Interference
MP MP UL Interference TDD
REL-4 REL-4
3GPP
Release 6 Information Element/Group name >>>1.28 Mcps TDD Need
640 Multi Type and reference 10.3.6.87a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description (no data) Version
REL-4
Condition algo
Explanation The IE is mandatory present if the IE "Power Control Algorithm" is set to "algorithm 1", otherwise the IE is not needed
10.3.6.93
Uplink DPCH power control info Pre
Parameters used by UE to set DPCH initial output power and to use for closed-loop power control in FDD and parameters for uplink open loop power control in 3.84 Mcps TDD.
Information Element/Group name CHOICE mode >FDD >>Power Control Algorithm Need MP MP Enumerated (algorithm 1, algorithm 2) Specifies algorithm to be used by UE to interpret TPC commands In dB (No data) REL-4 REL-4 Constant Value TDD 10.3.6.11a Quality Margin Multi Type and reference Semantics description Version
>>TPC step size >TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>DPCH Constant Value
CV-algo MP MP
Integer (1, 2)
>>>1.28 Mcps TDD
(no data)
REL-4
Condition algo
Explanation The IE is mandatory present if the IE "Power Control Algorithm" is set to "algorithm 1", otherwise the IE is not needed
10.3.6.94
NOTE:
Uplink Timeslots and Codes

Only for TDD
Need MP MP Multi Type and reference Boolean Individual timeslot info 10.3.6.37 Semantics description
Information Element/Group name Dynamic SF usage First Individual timeslot info
First timeslot Code List
MP
1..2
Individual timeslot info for the first timeslot used by the physical layer. Code list used in the timeslot. given in First individual timeslot info.
>Channelisation Code
MP
Enumerated( (1/1),)(2/1),( 2/2),(4/1)..(4/ 4),(8/1)..(8/8) ,(16/1)..(16/1 6)) (no data)
CHOICE more timeslots >No more timeslots >Consecutive timeslots
MP
3GPP
Release 6 Information Element/Group name >>Number of additional timeslots Need MP
641 Multi Type and reference Integer(1..m axTS-1)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The timeslots used by the physical layer shall be timeslots: N mod maxTS (N+1) mod maxTS ... (N+k) mod maxTS in that order, where N is the timeslot number in the First individual timeslot info and k the Number of additional timeslots. The additional timeslots shall use the same parameters (e.g. channelisation codes, midamble shifts etc.) as the first timeslot. The first instance of this parameter corresponds to the timeslot that shall be used second by the physical layer, the second to the timeslot that shall be used third and so on.
>Timeslot list >>Additional timeslot list
MP
1 to <maxTS1>
>>>CHOICE parameters >>>>Same as last >>>>>Timeslot number
MP MP Timeslot Number 10.3.6.84 This physical layer shall use the same parameters (e.g. channelisation codes, midamble shifts etc.) for this timeslot as for the last one.
>>>>New parameters >>>>>Individual timeslot info
MP
Individual timeslot info 10.3.6.37 1..2 Enumerated( (1/1),)(2/1),( 2/2),(4/1)..(4/ 4),(8/1)..(8/8) ,(16/1)..(16/1 6))
>>>>>Code List >>>>>>Channelisation Code
MP MP
10.3.6.95
NOTE:
Uplink Timing Advance

Need MP Multi Type and reference Integer (0..63) Semantics description Absolute timing advance value to be used to avoid large delay spread at the NodeB Version
Information Element/Group name UL Timing Advance
10.3.6.96
NOTE:
Uplink Timing Advance Control

Only for TDD
Need MP Multi Type and reference Semantics description Version
Information Element/Group name CHOICE Timing Advance
3GPP
Release 6 Information Element/Group name >Disabled Need
642 Multi Type and reference Null
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Indicates that no timing advance is applied Version
>Enabled >>CHOICE TDD option >>>3.84 Mcps TDD >>>>UL Timing Advance
MP MD Uplink Timing Advance 10.3.6.95 Absolute timing advance value to be used to avoid large delay spread at the NodeB. Default value is the existing value for uplink timing advance. Frame number timing advance is to be applied. This IE is required when a new UL Timing Advance adjustment is specified and Activation Time is not otherwise specified in the RRC message. (no data) Default: Uplink synchronisation step size is 1. Uplink synchronisation frequency is 1. This parameter specifies the step size to be used for the adjustment of the uplink transmission timing This parameter specifies the frequency of the adjustment of the uplink transmission timing Each bit indicates availability of a SYNC_UL code, where the SYNC_UL codes are numbered "code 0" to "code 7". The value 1 of a bit indicates that the corresponding SYNC_UL code can be used. The value 0 of a bit indicates that the corresponding SYNC_UL code
REL-4 REL-4
>>>>Activation Time
OP
Activation Time 10.3.3.1
>>1.28 Mcps TDD >>>Uplink synchronisation parameters
MD
REL-4 REL-4
>>>>Uplink synchronisation step size
MP
Integer(1..8)
REL-4
>>>>Uplink synchronisation frequency
MP
Integer(1..8)
REL-4
>>>Synchronisation parameters >>>>SYNC_UL codes bitmap
OP MP
Bitstring(8)
REL-4
3GPP
Release 6 Information Element/Group name >>>>FPACH info >>>>PRXUpPCHdes Need
643 Multi Type and reference FPACH info 10.3.6.35a Integer(120-58 by step of 1)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description can not be used. Version
MP MP
REL-4 In dBm REL-4
>>>>SYNC_UL procedure
MD
>>>>>Max SYNC_UL Transmissions
MP
Integer(1,2,4 ,8)
>>>>>Power Ramp Step
MP
Integer(0,1,2 ,3)
Default is: Max SYNC_UL Transmission is 2. Power Ramp Step is 2. Maximum numbers of SYNC_UL transmissions in a power ramping sequence. In dB
REL-4
REL-4
REL-4
3GPP
Release 6
644
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.97
E-DCH Info
Need OP Multi Type and reference Enumerated (true) Semantics description TRUE Indicates the MAC-es/e entity needs to be reset. Version REL-6
Information Element/Group name MAC-es/e reset indicator
E-DPCCH info
OP
E-DPDCH info
OP
E-DPCCH Info 10.3.6.98 E-DPDCH info 10.3.6.99
REL-6
REL-6
Scheduled Transmission configuration >2ms scheduled transmission grant HARQ process allocation
OP MD Bitstring (8) MAC-d PDUs belonging to MAC-d flows not configured with a Max MAC-e PDU contents size are only allowed to be transmitted in those processes for which the bit is set to 1. Bit 0 corresponds to HARQ process 0, bit 1 corresponds to HARQ process 1, Default value is: transmission in all HARQ processes is allowed. Bit 0 is the first/leftmost bit of the bit string. (0..37) indicates E-DCH serving grant index as defined in [15]; index 38 means zero grant. Indicates whether the Serving Grant is received with a Primary E-RNTI or Secondary ERNTI
REL-6 REL-6
>Serving Grant >>Serving Grant value
OP MP
Integer (0..37,38)
REL-6 REL-6
>>Primary/Secondary Grant Selector
MP
Enumerated (primary, secondary)
REL-6
3GPP
Release 6
645
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.98
E-DPCCH Info
Need MP Multi Type and reference Integer (0..8) Semantics description Refer to quantization of the power offset in [28] To be used when determining the setting of the happy bit (see [15]) Version REL-6
Information Element/Group name E-DPCCH/DPCCH power offset
Happy bit delay condition
MP
Enumerated (2ms, 10ms,20ms, 50ms, 100ms, 200ms, 500ms, 1000ms)
REL-6
3GPP
Release 6
646
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.99
E-DPDCH Info
Need MP Multi Type and reference Integer (0..1) Semantics description Indicates which standardised ETFCI TB size table shall be used See [15]; Absence means no E-DCH minimum set See [29] Version REL-6
Information Element/Group name E-TFCI table index
E-DCH minimum set E-TFCI
MD
Integer (0..127)
REL-6
Reference E-TFCIs >Reference E-TFCI >Reference E-TFCI PO
MP MP MP
1 to 8 Integer (0..127) Integer (0..29)
REL-6 REL-6 REL-6
Refer to quantization of the power offset in [28]
Maximum channelisation codes
MP
PLnon-max
MP
Enumerated (sf256, sf128, sf64, sf32, sf16, sf8, sf4, 2sf4, 2sf2, 2sf2and2sf4) Real (0.44 ..1.0 by step of 0.04)
REL-6
As defined in [27]
REL-6
Scheduling Information Configuration >Periodicity for Scheduling Info no grant
MP MD Enumerated (everyEDCHT TI,4,10,20,50, 100,200,500,1 000) Enumerated (everyEDCHT TI,4,10,20,50, 100,200,500,1 000) Integer (0..6) Values in ms. Default value is no report NOTE 1. Values in ms. Default value is no report NOTE 1.
REL-6 REL-6
>Periodicity for Scheduling Info grant
MD
REL-6
>Power Offset for Scheduling Info
Only used when REL-6 no MACd PDUs are included in the same MACe PDU. Unit is in dB. 3-Index-Step Threshold MD Integer (0..37) Refers to an REL-6 index in the SG-Table (see [15]). Default value is 0. NOTE 2. 2-Index-Step Threshold MD Integer (0..37) Refers to an REL-6 index in the SG-Table (see [15]). Default value is 0. NOTE 2. NOTE 1: If the Periodicity is set to 4ms and the E-DCH TTI is set to 10ms, the UE shall interpret the periodicity value as 10ms. NOTE 2: If the 3-index-Step Threshold value is greater than 2-index-Step Threshold, the UE behaviour is unspecified.
MP
3GPP
Release 6
647
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.6.100
E-AGCH Info
Includes the configuration for the E-DCH related Absolute Grant Channel.
Information Element/Group name E-AGCH Channelisation Code Need MP Multi Type and reference Integer (0..255) Semantics description Version REL-6
10.3.6.101
E-HICH Info
Includes the configuration for the E-DCH related HARQ Acknowledgement Indicator Channel.
Information Element/Group name Channelisation Code Signature Sequence Need MP MP Multi Type and reference Integer (0..127) Integer (0..39) Semantics description Version REL-6 REL-6
10.3.6.102
E-RGCH Info
Includes the configuration for the E-DCH related Relative Grant Channel. The E-RGCH is using the same channelisation code as configured for the E-HICH channel (see subclause 10.3.6.101).
Information Element/Group name Signature Sequence RG combination index Need MP MP Multi Type and reference Integer(0..39 ) Integer(0..5) Semantics description Version REL-6
Cells with an index equal to the index of the Serving E-DCH cell belong to the Serving EDCH RLS. The E-RGCH from these cells have RG commands which for the UE are known to be the same as the RG commands from the Serving E-DCH cell.
REL-6
3GPP
Release 6
648
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7
10.3.7.1
Measurement Information elements

Additional measurements list
Need MP Multi 1 to <MaxAdditi onalMeas> Measuremen t identity 10.3.7.48 Type and reference Semantics description
Information Element/Group name Additional measurements
>Additional measurement identity
MP
10.3.7.2
Cell info
Includes non-frequency related cell info used in the IE "inter-frequency cell info list" and "intra frequency cell info list".
Information Element/Group name Cell individual offset Need MD Multi Type and reference Real(-10..10 by step of 0.5) Semantics description In dB Default value is 0 dB Used to offset measured quantity value In chips. This IE is absent for serving cell. Version
Reference time difference to cell
OP
Read SFN indicator
MP
Reference time difference to cell 10.3.7.60 Boolean
TRUE indicates that read of SFN is requested for the target cell
CHOICE mode >FDD >>Primary CPICH info
MP OP Primary CPICH info 10.3.6.60 This IE is absent only if measuring RSSI only (broadband measurement.) Required if calculating pathloss. TRUE indicates that transmit diversity is used.
>>Primary CPICH Tx power
OP
>>TX Diversity Indicator
MP
Primary CPICH Tx power 10.3.6.61 Boolean
MP
>>Primary CCPCH TX power
OP
Primary CCPCH info 10.3.6.57 Primary CCPCH TX power 10.3.6.59 1 to <maxTS> The UE shall report Timeslot ISCP values according the order of the listed Timeslot numbers REL-4 REL-4 Integer Timeslot
>>Timeslot list
OP
>>>CHOICE TDD option >>>>3.84 Mcps TDD >>>>>Timeslot number
MP MP
3GPP
Release 6
649 (0...14)
3GPP TS 25.331 V6.23.0 (2009-09) numbers, for which the UE shall report Timeslot ISCP Use for Timeslot ISCP measurements only. Default value is "Type1" Timeslot numbers, for which the UE shall report Timeslot ISCP This IE is absent for the serving cell. REL-4 REL-4
>>>>>Burst Type
MD
Enumerated (Type1, Type2)
>>>>1.28 Mcps TDD >>>>>Timeslot number
MP
Integer (0...6)
Cell Selection and Re-selection Info
CVBCHopt
Cell Selection and Reselection for SIB11/12Info 10.3.2.4
Condition BCHopt
Explanation This IE is Optional when sent in SYSTEM INFORMATION, Otherwise, the IE is not needed
10.3.7.3
Cell measured results
Includes non-frequency related measured results for a cell.

Information Element/Group name Cell Identity Need OP Multi Type and reference Cell Identity 10.3.2.2 Cell synchroni sation informatio n 10.3.7.6 Semantics description Version
Cell synchronisation information
OP
MP MP Primary CPICH info 10.3.6.60 Integer(0.. 49)
>>CPICH Ec/N0
OP
>>CPICH RSCP
OP
Integer(0.. 91)
>>DeltaCPICH RSCP
CVRSCP
Integer(5..-1)
>>Pathloss
OP
Integer(46 ..158)
According to CPICH_Ec/No in [19] and [20]. Fourteen spare values are needed. According to CPICH_RSCP in [19] and [20]. Thirty-six spare values are needed. If present, the actual value of CPICH RSCP = CPICH RSCP+ DeltaCPICH RSCP In dB. Fifteen spare values are needed.
REL-5
>TDD >>Cell parameters Id
MP
Cell
3GPP
650 Type and reference parameter s Id 10.3.6.9 Integer (0..14) Primary CCPCH RSCP info 10.3.7.54 Integer(46 ..158)
>>Proposed TGSN >>Primary CCPCH RSCP
OP OP
Proposal for the next TGSN
>>Pathloss
OP
In dB. Fifteen spare values are needed.
>>Timeslot list >>>Timeslot ISCP
OP MP
1 to < maxTS> Timeslot ISCP Info 10.3.7.65 The UE shall report the Timeslot ISCP in the same order as indicated in the cell info
Condition RSCP
Explanation This IE is mandatory if the IE "Cell measured results" is included in the IE "Measured Results" (i.e. not included in the IE "Additional Measured Results") and if CPICH RSCP is present and if the value of the CPICH RSCP is below 0. It is not needed otherwise.
10.3.7.4
Cell measurement event results
Includes non-frequency related cell reporting quantities.

Information Element/Group name CHOICE mode >FDD >>Primary CPICH info Need MP MP 1 to <maxCellM eas> 1 to <maxCellM eas> Primary CPICH info 10.3.6.60 Primary CCPCH info 10.3.6.57 Multi Type and reference Semantics description
MP
10.3.7.5
Cell reporting quantities
Includes non-frequency related cell reporting quantities. For all boolean types TRUE means inclusion in the report is requested.
Information Element/Group name Cell synchronisation information reporting indicator Cell Identity reporting indicator CHOICE mode >FDD >>CPICH Ec/N0 reporting indicator >>CPICH RSCP reporting indicator >>Pathloss reporting indicator Need MP MP MP MP MP MP Multi Type and reference Boolean Boolean Semantics description
Boolean Boolean Boolean
3GPP
Release 6 Information Element/Group name >TDD >>Timeslot ISCP reporting indicator >>Proposed TGSN Reporting required >>Primary CCPCH RSCP reporting indicator >>Pathloss reporting indicator Need
651 Multi Type and reference Boolean Boolean Boolean Boolean
MP MP MP MP
10.3.7.6
Cell synchronisation information
The IE "Cell synchronisation information" contains the OFF and Tm as defined in [7] and [8] and the four most significant bits of the difference between the 12 least significant bits of the RLC Transparent Mode COUNT-C in the UE and the SFN of the measured cell. It is notified to SRNC by Measurement Report message or Measurement Information Element in other RRC messages
Information Element/Group name CHOICE mode >FDD >>COUNT-C-SFN frame difference >>>COUNT-C-SFN high Need Multi Type and reference Semantics description
MP OP MP MP MP OP MP MP
Integer(0..38 40 by step of 256) Integer(0..25 5) in frames Integer(0..38 40 by step of 256) Integer(0..25 5) Integer(0..38 399) in frames
>>>OFF >>Tm >TDD >>COUNT-C-SFN frame difference >>>COUNT-C-SFN high
in frames in chips
>>>OFF
in frames
10.3.7.7
Event results
Need MP Intrafrequency measuremen t event results 10.3.7.37 Interfrequency measuremen t event results 10.3.7.17 Inter-RAT measuremen t event results 10.3.7.28 Traffic Multi Type and reference Semantics description One spare value is needed.
Information Element/Group name CHOICE event result >Intra-frequency measurement event results
>Inter-frequency measurement event results
>Inter-RAT measurement event results
For IS-2000 results, include fields of the Pilot Strength Measurement Message from subclause 2.7.2.3.2.5 of TIA/EIA/IS-2000.5
>Traffic volume measurement
3GPP
Release 6 Information Element/Group name event results Need
652 Multi Type and reference volume measuremen t event results 10.3.7.69 Quality measuremen t event results 10.3.7.57 UE internal measuremen t event results 10.3.7.78 UE positioning measuremen t event results 10.3.7.101
>Quality measurement event results
>UE internal measurement event results
>UE positioning measurement event results
CHOICE event result Intra-frequency measurement event results Inter-frequency measurement event results Inter-RAT measurement event results Traffic volume measurement event results Quality measurement event results UE internal measurement event results UE positioning measurement event results
Condition under which the given event result is chosen If measurement type = intra-frequency measurement If measurement type = inter-frequency measurement If measurement type = inter-RAT measurement If measurement type = traffic volume measurement If measurement type = Quality measurement If measurement type = UE internal measurement If measurement type = UE positioning measurement
10.3.7.8
FACH measurement occasion info

Need OP MP Multi Type and reference Integer(1..12 ) Boolean Semantics description Version
Information Element/Group name FACH Measurement occasion cycle length coefficient Inter-frequency FDD measurement indicator Inter-frequency TDD 3.84 Mcps measurement indicator Inter-frequency TDD 1.28 Mcps measurement indicator Inter-RAT measurement indicators >RAT type
MP
Boolean
MP
Boolean
TRUE means that measurements are required TRUE means that measurements are required TRUE means that measurements are required
REL-4
REL-4
OP
1 to <maxOther RAT> Enumerated( GSM, IS2000)
MP
3GPP
Release 6
653
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.9
Filter coefficient
Need MD Multi Type and reference Integer(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19) Semantics description Default value is 0
Information Element/Group name Filter coefficient
10.3.7.10
HCS Cell re-selection information

Need MD Multi Type and reference Integer(0, 10, 20, 30, 40, 50, 60) Semantics description Default value is 0 which means = not used In seconds
Information Element/Group name Penalty_time
Temporary_offsets >Temporary_offset1
CV-Penalty used MP
>Temporary_offset2
CV-FDDQualityMeasure
Integer(3, 6, 9, 12, 15, 18, 21, inf) Integer(2, 3, 4, 6, 8, 10, 12, inf)
[dB]
[dB]
Condition Penalty used FDD-Quality-Measure
Explanation This IE is not needed if the IE "Penalty time" equals "not used", else it is mandatory present. This IE is not needed if the IE "Cell selection and reselection quality measure" has the value CPICH RSCP, otherwise the IE is mandatory present. This conditional presence is implemented in ASN.1 by the use of a specific RSCP and EcN0 variant of 10.3.7.10.
10.3.7.11
HCS neighbouring cell information

Need MD MD MP Multi Type and reference Integer (0..7) Qhcs 10.3.7.54a HCS Cell Re-selection Information 10.3.7.10 Semantics description Default value = 0 Default value = 0
Information Element/Group name HCS_PRIO Qhcs HCS Cell Re-selection Information
3GPP
Release 6
654
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.12
HCS Serving cell information

Need MD MD MD Multi Type and Reference Integer (0..7) Qhcs 10.3.7.54a Enumerated( not used, 30, 60, 120, 180, 240) Integer(1..16 ) Enumerated( not used, 10, 20, 30, 40, 50, 60, 70) Semantics description Default value = 0 Default value = 0 [s] Default value is not used
Information Element/Group name HCS_PRIO Qhcs TCRmax
NCR
TCrmaxHyst
CV-UE speed detector CV-UE speed detector
Default value = 8
[s]
Condition UE Speed detector
Explanation This IE is not needed if TCrmax equals 'not used', else it is mandatory present.
10.3.7.13
Inter-frequency cell info list
Contains the information for the list of measurement objects for an inter-frequency measurement.
Information Element/Group name CHOICE Inter-frequency cell removal >Remove all inter-frequency cells >Remove some inter-frequency cells >>Removed inter-frequency cells >>>Inter-frequency cell id Need OP No data Multi Type and reference Semantics description
MP
1 .. <maxCellM eas> Integer(0 .. <maxCellMe as>-1) No data
MP
>No inter-frequency cells removed New inter-frequency cells
OP
1 to <maxCellM eas> Integer(0 .. <maxCellMe as>-1) Frequency info 10.3.6.36
>Inter-frequency cell id
MD
>Frequency info
MD
Default value is the value of the previous "frequency info" in the list. NOTE: The first occurrence is then MP.
>Cell info Cells for measurement
MP CVBCHopt MP 1 to <maxCellM eas>
Cell info 10.3.7.2
>Inter-frequency cell id
Integer(0 .. <maxCellMe as>-1)
3GPP
Release 6 Condition BCHopt
655
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation This IE is not needed when sent in SYSTEM INFORMATION. Otherwise, the IE is Optional
10.3.7.14
Inter-frequency event identity

Need MP Multi Type and reference Enumerated( 2a, 2b, 2c, 2d, 2e, 2f) Semantics description Two spare values are needed.
Information Element/Group name Inter-frequency event identity
10.3.7.15
Inter-frequency measured results list

Need OP MD Multi 1 to <maxFreq> Frequency info 10.3.6.36 Default value is the value of the previous "frequency info" in the list. NOTE: The first occurrence is then MP. According to UTRA_carrier_RSSI_LEV in [19] and [20]. Fifty-one spare values are needed. Only cells for which all reporting quantities are available should be included. Type and reference Semantics description
Information Element/Group name Inter-frequency measurement results >Frequency info
>UTRA carrier RSSI
OP
Integer(0..76 )
>Inter-frequency cell measurement results >>Cell measured results
OP
1 to <maxCellM eas> Cell measured results 10.3.7.3
MP
10.3.7.16
Need MP Multi Type and reference Interfrequency cell info list 10.3.7.13 Interfrequency measuremen t quantity 10.3.7.18 Interfrequency reporting quantity 10.3.7.21 Reporting cell status 10.3.7.61 Measuremen t validity 10.3.7.51 Interfrequency Semantics description
Information Element/Group name Inter-frequency measurement objects list
Inter-frequency measurement quantity
OP
Inter-frequency reporting quantity
OP
Reporting cell status
CVreporting OP
Inter-frequency set update
OP
3GPP
656 Multi Type and reference set update 10.3.7.22 Intrafrequency measuremen t reporting criteria 10.3.7.39 Interfrequency measuremen t reporting criteria 10.3.7.19 Periodical reporting criteria 10.3.7.53
CHOICE report criteria >Intra-frequency measurement reporting criteria
MP
>Inter-frequency measurement reporting criteria
>Periodical reporting criteria
>No reporting
(no data) Chosen when this measurement only is used as additional measurement to another measurement
Condition reporting
Explanation This IE is optional if the CHOICE "report criteria" is equal to "periodical reporting criteria" or "No reporting", otherwise the IE is not needed
10.3.7.17
Inter-frequency measurement event results
This IE contains the measurement event results that are reported to UTRAN for inter-frequency measurements.
Information Element/Group name Inter-frequency event identity Need MP Multi Type and reference Interfrequency event identity 10.3.7.14 Semantics description
Inter-frequency cells >Frequency info
OP MP
1 to <maxFreq> Frequency info 10.3.6.36 Cell measureme nt event results 10.3.7.4
>Non frequency related measurement event results
MP
10.3.7.18
Inter-frequency measurement quantity
The quantity the UE shall measure in case of inter-frequency measurement. It also includes the filtering of the measurements.
Information Element/Group name CHOICE reporting criteria >Intra-frequency reporting Need MP Multi Type and reference Semantics description
3GPP
Release 6 Information Element/Group name criteria >>Intra-frequency measurement quantity Need
657 Multi Type and reference Intrafrequency measuremen t quantity 10.3.7.38
MP
>Inter-frequency reporting criteria >>Filter coefficient
MP
Filter coefficient 10.3.7.9
>>CHOICE mode >>>FDD >>>>Measurement quantity for frequency quality estimate
MP MP Enumerated( CPICH Ec/N0, CPICH RSCP) Enumerated( Primary CCPCH RSCP)
>>>TDD >>>>Measurement quantity for frequency quality estimate
MP
10.3.7.19
Inter-frequency measurement reporting criteria
The triggering of the event-triggered reporting for an inter-frequency measurements. All events concerning interfrequency measurements are labelled 2x where x is a,b,c, ... Event 2a: Change of best frequency. Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold. Event 2c: The estimated quality of a non-used frequency is above a certain threshold. Event 2d: The estimated quality of the currently used frequency is below a certain threshold. Event 2e: The estimated quality of a non-used frequency is below a certain threshold. Event 2f: The estimated quality of the currently used frequency is above a certain threshold.
3GPP
Release 6 Information Element/Group name Parameters required for each event Need OP Multi 1 to <maxMe asEvent >
>Inter-frequency event identity
MP
>Threshold used frequency
CV clause 0
Interfrequency event identity 10.3.7.14 Integer(115..0)
Integer (120..0)
>DeltaThreshold used frequency
CVclause 3
Integer(5..-1)
Ranges used depend on measurement quantity. CPICH Ec/No -24..0dB CPICH/Primary CCPCH RSCP -115..-25dBm Ranges used depend on measurement quantity. CPICH Ec/No -24..0dB CPICH/Primary CCPCH RSCP -120..-25dBm If present, the actual value of Threshold used frequency = Threshold used frequency + DeltaThreshold used frequency Not used in Release 6 and later
REL-6
REL-5
REL-6
>W used frequency
CV clause 2
>Hysteresis
MP
>Time to trigger
MP
Real(0, 0.1..2.0 by step of 0.1) Real(0, 0.5..14.5 by step of 0.5) Time to trigger 10.3.7.64
In event 2a, 2b, 2c, 2d, 2e, 2f
Indicates the period of time during which the event condition has to be satisfied, before sending a Measurement Report. Time in ms.
>Reporting cell status
OP
Reporting cell status 10.3.7.61 1 to <maxFre q> In this release, the first listed threshold and W parameter shall apply to all non-used frequencies.
>Parameters required for each non-used frequency
OP
3GPP
Release 6 Information Element/Group name >>Threshold non used frequency Need CV clause 1 Multi
659 Type and reference Integer(115..0)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Ranges used depend on measurement quantity. CPICH Ec/No -24..0dB CPICH/Primary CCPCH RSCP -115..-25dBm. This IE is not needed if the IE "Inter-frequency event identity" is set to 2a. However, it is specified to be mandatory to align with the ASN.1. Ranges used depend on measurement quantity. CPICH Ec/No -24..0dB CPICH/Primary CCPCH RSCP -120..-25dBm This IE is not needed if the IE "Inter-frequency event identity" is set to 2a. If present, the actual value of Threshold non used frequency = Threshold non used frequency + DeltaThreshold non used
frequency
Version
Integer (120..0)
REL-6
>> DeltaThreshold non used

frequency
CVclause 4
Integer(5..-1)
REL-5
Not used in Release 6 and later >>W non-used frequency CVclause 1 Real(0, 0.1..2.0 by step of 0.1)
REL-6
Condition Clause 0
Clause 1
Clause 2
Clause 3
Clause 4
Explanation This IE is mandatory present if the IE "Inter frequency event identity" is set to 2b, 2d, or 2f, otherwise the IE is not needed. This IE is mandatory present if the IE "Inter frequency event identity" is set to 2a, 2b, 2c or 2e, otherwise the IE is not needed This IE is mandatory present if the IE "Inter-frequency event identity" is set to 2a, 2b, 2d or 2f, otherwise the IE is not needed. This IE is optional if the IE "Inter frequency event identity" is set to 2b, 2d, or 2f. Otherwise the IE is not needed. Note that in order to align with the ASN.1, this IE is always included when the IE DeltaThreshold non used frequency is present, but the value shall be ignored if the "Inter-frequency event identity" is not set to 2b, 2d or 2f. This IE is optional if the IE "Inter frequency event identity" is set to 2a, 2b, 2c or 2e. Otherwise the IE is not needed.
3GPP
Release 6
660
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.20
Inter-frequency measurement system information

Need OP Multi Type and reference Interfrequency cell info list 10.3.7.13 Interfrequency RACH reporting information 10.3.7.20a Semantics description Version
Information Element/Group name Inter-frequency cell info list
Inter-frequency RACH reporting information
OP
REL-6
10.3.7.20a
Inter-frequency RACH reporting information
Contains the reporting configuration information for an inter-frequency measurement report, which is sent on the RACH.
Information Element/Group name CHOICE mode >FDD >> Inter-frequency RACH reporting quantity >TDD >>Reporting quantity list >>> Inter-frequency RACH reporting quantity Inter-frequency RACH reporting threshold Need MP MP Enumerated(CPICH Ec/N0, CPICH RSCP) 1 to 2 Enumerated(Primary CCPCH RSCP) Integer(-115..0) Ranges used depend on measurement quantity. CPICH Ec/No 24..0dB CPICH/Primary CCPCH RSCP 115..-25dBm. Indicates the total number for all nonused frequencies Multi Type and reference Semantics description Version REL-6 REL-6 REL-6
MP MP
REL-6 REL-6 REL-6
MP
REL-6
Maximum number of inter-frequency RACH reporting cells
MP
Integer(1..8)
REL-6
10.3.7.21
Inter-frequency reporting quantity

Need MP MP Multi Type and reference Boolean Boolean Semantics description TRUE means report is requested. TRUE means that report is requested. This parameter is not used in this release and should be set to FALSE. It shall be ignored by the UE.
Information Element/Group name UTRA Carrier RSSI Frequency quality estimate
Non frequency related cell reporting quantities
MP
Cell reporting quantities 10.3.7.5
3GPP
Release 6
661
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.22
Inter-frequency SET UPDATE
NOTE 1: Only for FDD. This information makes it possible to use events defined for Intra-frequency measurement within the same non-used frequency for Inter-frequency measurement reporting criteria.
Information Element/group name UE autonomous update mode Need MP Multi Type and reference Enumerated (On with no reporting) Semantics description Required for backwards compatibility with a UE not supporting this revision of the standard
10.3.7.23
Inter-RAT cell info list
Contains the information for the list of measurement objects for an inter-RAT measurement.
Information Element/Group name CHOICE Inter-RAT cell removal >Remove all inter-RAT cells >Remove some inter-RAT cells >>Removed inter-RAT cells Need MP No data MP 1 to <maxCellM eas> Integer(0 .. <maxCellMe as> - 1) 1 to <maxCellM eas> Although this IE is not always required, need is MP to align with ASN.1 REL-4 Integer(0 .. <maxCellMe as> - 1) Multi Type and reference Semantics description Version
>>>Inter-RAT cell id
MP
>Remove no inter-RAT cells New inter-RAT cells
MP
>Inter-RAT cell id
OP OP
>CHOICE Radio Access Technology >>GSM >>>Cell individual offset
MP
MP
Integer (50..50 )
>>>Cell selection and reselection info
OP
>>>BSIC >>>Band indicator
MP MP
>>>BCCH ARFCN >>IS-2000 >>>System specific measurement info
MP
Cell selection and reselection info for SIB11/12 10.3.2.4 BSIC 10.3.8.2 Enumerated (DCS 1800 band used, PCS 1900 band used) Integer (0..1023) enumerated (frequency, timeslot,
In dB Used to offset measured quantity value See subclause 8.6.7.3
Indicates how to interpret the BCCH ARFCN
[45]
MP
For IS-2000, use fields from TIA/EIA/IS-
3GPP
662 Multi Type and reference colour code, output power, PN offset)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description 2000.5, subclause 3. 7.3.3.2.27, Candidate Frequency Neighbour List Message This value has been introduced to handle the case when IE "New inter-RAT cells" is not required Version
>>None
(no data)
Cell for measurement
OP
1 to <maxCellM eas> Integer(0 .. <maxCellMe as>-1) Integer (0..3)
>Inter-RAT cell id
MP
Inter-RAT cell info indication
CVMessage
NOTE 1 and 2
REL-5
Condition Message
Explanation The IE is optionally present in the MEASUREMENT CONTROL and in the SRNS RELOCATION INFO messages, otherwise the IE is not needed.
NOTE 1: The UTRAN may choose not to use the "Inter-RAT cell info indication" value "0" in the MEASUREMENT CONTROL message, to distinguish that case from those cases where the UE receives the IE "Inter-RAT cell info list" in SIB11 or SIB12. NOTE 2: In case of an SRNS relocation, if the UE has been sent the "Inter-RAT cell info indication" in the MEASUREMENT CONTROL message and the IE "Inter-RAT cell info list" is included in the SRNS RELOCATION INFO sent from the source RNC to the target RNC, the "Inter-RAT cell info indication" should be included in the IE "Inter-RAT cell info list". NOTE 3: If the UTRAN configures a UE with an "Inter-RAT cell info list" containing a set of GSM cells where one or more cell(s) belong to DCS 1800 band and one or more cell(s) belong to PCS 1900 band, the UE behaviour is unspecified.
10.3.7.24
Inter-RAT event identity

Need MP Multi Type and reference Enumerated (3a, 3b, 3c, 3d) Semantics description
Information Element/Group name Inter-RAT event identity
10.3.7.25
Inter-RAT info
Inter-RAT info defines the target system for redirected cell selection.
3GPP
Release 6 Information Element/Group name Inter-RAT info GSM target cell info Need MP CV-GSM
663 Multi Type and reference Enumerated (GSM) GSM target cell info 10.3.8.4g
REL-6
Condition GSM
Explanation This IE is optional if the IE "Inter-RAT info" is set to GSM and not needed otherwise.
10.3.7.26
Inter-RAT measured results list

Need OP Multi 1 to <maxOther RAT-16> One spare value is needed. 1 to <maxRepo rtedGSMC ells> bit string(6) RXLEV is mapped to a value between 0 and 63, [46]. When mapping the RXLEV value to the RSSI bit string, the first/leftmost bit of the bit string contains the most significant bit. Type and reference Semantics description
Information Element/Group name Inter-RAT measurement results
>CHOICE system >>GSM >>>Measured GSM cells
MP MP
>>>>GSM carrier RSSI
OP
>>>>CHOICE BSIC >>>>>Verified BSIC >>>>>>inter-RAT cell id
MP MP Integer(0..< maxCellMea s>-1) Integer (0..1023) [45]
>>>>>Non verified BSIC >>>>>>BCCH ARFCN
MP
3GPP
Release 6
664
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.27
Need OP Multi Type and reference Inter-RAT cell info list 10.3.7.23 Inter-RAT measuremen t quantity 10.3.7.29 Inter-RAT reporting quantity 10.3.7.32 Reporting cell status 10.3.7.61 Inter-RAT measuremen t reporting criteria 10.3.7.30 Periodical reporting criteria 10.3.7.53 (no data) Chosen when this measurement only is used as additional measurement to another measurement Semantics description
Information Element/Group name Inter-RAT measurement objects list Inter-RAT measurement quantity
OP
OP
CVreporting MP
CHOICE report criteria >Inter-RAT measurement reporting criteria
>No reporting
Condition reporting
10.3.7.28
Inter-RAT measurement event results
This IE contains the measurement event results that are reported to UTRAN for inter-RAT measurements.
Information Element/Group name Inter-RAT event identity Need MP Multi Type and reference Inter-RAT event identity 10.3.7.24 Semantics description
Cells to report
MP
1 to <maxCellM eas>
>CHOICE BSIC >>Verified BSIC >>>inter-RAT cell id
MP MP Integer(0..< maxCellMea s>-1) Integer (0..1023) [45]
>>Non verified BSIC >>>BCCH ARFCN
MP
3GPP
Release 6
665
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.29
Inter-RAT measurement quantity
The quantity the UE shall measure in case of inter-RAT measurement. It also includes the filtering of the measurements.
Information Element/Group name Measurement quantity for UTRAN quality estimate Need OP Multi Type and reference Intrafrequency measuremen t quantity 10.3.7.38 Semantics description
CHOICE system >GSM >>Measurement quantity
MP MP Enumerated( GSM Carrier RSSI) Filter coefficient 10.3.7.9 Enumerated( required, not required) Integer(0..63 ) Integer(0..15 ) Admission criteria for neighbours, see subclause 2.6.6.2.6 of TIA/EIA/IS-2000.5 Admission criteria for neighbours, see subclause 2.6.6.2.5.2 of TIA/EIA/IS2000.5 Admission criteria for neighbours, see subclause 2.6.6.2.3 and 2.6.6.2.5.2 of TIA/EIA/IS-2000.5 Admission criteria for neighbours, see subclause 2.6.6.2.5.2 of TIA/EIA/IS2000.5
>>Filter coefficient
MP
>>BSIC verification required
MP
>IS2000 >>TADD Ec/I0
MP
>>TCOMP Ec/I0
MP
>>SOFT SLOPE
OP
Integer(0..63 )
>>ADD_INTERCEPT
OP
Integer(0..63 )
10.3.7.30
Inter-RAT measurement reporting criteria
The triggering of the event-triggered reporting for an inter-RAT measurement. All events concerning inter-RAT measurements are labelled 3x where x is a,b,c, ... Event 3a: The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold. Event 3b: The estimated quality of other system is below a certain threshold. Event 3c: The estimated quality of other system is above a certain threshold. Event 3d: Change of best cell in other system.
3GPP
Release 6 Information Element/Group name Parameters required for each event >Inter-RAT event identity Need OP
666 Multi 1 to <maxMeas Event> Inter-RAT event identity 10.3.7.24 Integer (115..0) Real(0, 0.1..2.0 by step of 0.1) Integer (115..0) Real(0..7.5 by step of 0.5) Time to trigger 10.3.7.64 Type and reference
MP
>Threshold own system >W
CVclause 0 CVclause 0 CVclause 1 MP
In event 3a
>Threshold other system >Hysteresis
In event 3a, 3b, 3c
>Time to trigger
MP
Indicates the period of time during which the event condition has to be satisfied, before sending a Measurement Report.
OP
Reporting cell status 10.3.7.61
Condition Clause 0 Clause 1
Explanation The IE is mandatory present if the IE "Inter-RAT event identity" is set to "3a", otherwise the IE is not needed The IE is mandatory present if the IE "Inter-RAT event identity" is set to 3a, 3b or 3c, otherwise the IE is not needed
10.3.7.31
Inter-RAT measurement system information

Need OP Multi Type and reference Inter-RAT cell info list 10.3.7.23 Semantics description
Information Element/Group name Inter-RAT cell info list
10.3.7.32
For all boolean types TRUE means inclusion in the report is requested.
Information Element/Group name UTRAN estimated quality Need MP Multi Type and reference Boolean Semantics description This parameter is not used in this release and should be set to FALSE.
CHOICE system >GSM >>GSM Carrier RSSI Reporting indicator
MP MP Boolean
10.3.7.33
Intra-frequency cell info list
Contains the information for the list of measurement objects for an intra-frequency measurement.
3GPP
Release 6 Information Element/Group name CHOICE Intra-frequency cell removal >Remove all intra-frequency cells >Remove some intra-frequency cells >>Removed intra-frequency cells >>>Intra-frequency cell id Need OP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Absence of this IE is equivalent to choice "Remove no intra-frequency cells". No data
MP
1 to <maxCell Meas> Integer(0 .. <maxCellMea s> - 1)
MP
>Remove no intra-frequency cells New intra-frequency cells
OP
1 to <maxCell Meas>
This information element must be present when "Intrafrequency cell info list" is included in the system information Integer(0 .. <maxCellMea s> - 1) Cell info 10.3.7.2
>Intra-frequency cell id
OP
>Cell info
MP
This IE must be included for the serving cell when the IE "Intra frequency cell info list" is included in System Information Block type 11.
Cells for measurement
CVBCHopt MP
1 to <maxCell Meas> Integer(0 .. <maxCellMea s>-1)
>Intra-frequency cell id
Condition BCHopt
Explanation This IE is not needed when sent in SYSTEM INFORMATION. Otherwise, the IE is Optional
10.3.7.34
Intra-frequency event identity

Need MP Multi Type and reference Enumerated (1a,1b,1c,1d, 1e,1f,1g,1h,1 i, 1j) Semantics description Seven spare values are needed. Version
Information Element/Group name Intra-frequency event identity
Six spare values are needed.
REL-6
3GPP
Release 6
668
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.35
Intra-frequency measured results list

Need OP Multi 1 to <maxCellM eas> Cell measured results 10.3.7.3 Only cells for which all reporting quantities are available should be included. Type and reference Semantics description
Information Element/Group name Intra-frequency measurement results >Cell measured results
MP
10.3.7.36
Need OP Multi Type and reference Intrafrequency cell info list 10.3.7.33 Intrafrequency measuremen t quantity 10.3.7.38 Intrafrequency reporting quantity 10.3.7.41 Reporting cell status 10.3.7.61 Measuremen t validity 10.3.7.51 Semantics description Version
Information Element/Group name Intra-frequency measurement objects list
OP
Intra-frequency reporting quantity
OP
CVreporting OP
OP MP Intrafrequency measuremen t reporting criteria 10.3.7.39 Periodical reporting criteria 10.3.7.53
See note 1
REL-6
>No reporting
(no data) Chosen when this measurement only is used as additional measurement to another measurement
Condition reporting
NOTE 1: The IE "report criteria" is optional in all releases except the Release 6. In the Release 6 the IE "report criteria" is mandatory present in order to align the tabular format with the Release 6 ASN.1.
3GPP
Release 6
669
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.37
Intra-frequency measurement event results
This IE contains the measurement event results that are reported to UTRAN for intra-frequency measurements.
Information Element/Group name Intra-frequency event identity Need MP Multi Type and reference Intrafrequency event identity 10.3.7.34 Cell measureme nt event results 10.3.7.4 Semantics description
Cell measurement event results
MP
10.3.7.38
The quantity the UE shall measure in case of intra-frequency measurement. It also includes the filtering of the measurements.
Information Element/Group name Filter coefficient Need MP Multi Type and reference Filter coefficient 10.3.7.9 Semantics description
CHOICE mode >FDD >>Measurement quantity
MP MP Enumerated( CPICH Ec/N0, CPICH RSCP, Pathloss) MP MP 1 to 4 Enumerated( Primary CCPCH RSCP, Pathloss, Timeslot ISCP)
>TDD >>Measurement quantity list >>>Measurement quantity
10.3.7.39
Intra-frequency measurement reporting criteria
The triggering of the event-triggered reporting for an intra-frequency measurement. All events concerning intrafrequency measurements are labelled 1x where x is a, b, c. Event 1a: A Primary CPICH enters the Reporting Range (FDD only). Event 1b: A Primary CPICH leaves the Reporting Range (FDD only). Event 1c: A Non-active Primary CPICH becomes better than an active Primary CPICH (FDD only). Event 1d: Change of best cell (FDD only). Event 1e: A Primary CPICH becomes better than an absolute threshold (FDD only). Event 1f: A Primary CPICH becomes worse than an absolute threshold (FDD only). Event 1g: Change of best cell in TDD.
3GPP
Release 6
670
3GPP TS 25.331 V6.23.0 (2009-09)
Event 1h: Timeslot ISCP below a certain threshold (TDD only). Event 1i: Timeslot ISCP above a certain threshold (TDD only). Event 1j: A Non-active E-DCH but active DCH Primary CPICH becomes better than an active E-DCH Primary CPICH (FDD only).
Information Element/Group name Parameters required for each event Need OP Multi 1 to <maxMe asEvent > Intrafrequency event identity 10.3.7.34 Enumerat ed(Active set cells, Monitored set cells, Active set cells and monitored set cells) Enumerat ed(Active set cells, Monitored set cells, Active set cells and monitored set cells, Detected set cells, Detected set cells and monitored set cells) Real(0..1 4.5 by step of 0.5) 1 to <maxCel lMeas> Type and reference Semantics description Version
>Intra-frequency event identity
MP
>Triggering condition 1
CV clause 0
Indicates which cells can trigger the event
>Triggering condition 2
CV clause 6 CVclause 10
Indicates which cells can trigger the event REL-5
>Reporting Range Constant
CV clause 2
In dB. In event 1a,1b.
>Cells forbidden to affect Reporting range >>CHOICE mode >>>FDD >>>>Primary CPICH info
CV clause 1 MP MP
In event 1a,1b
Primary CPICH info 10.3.6.60 Primary CCPCH info 10.3.6.57 Real(0.0.. 2.0 by step of 0.1) Real(0..7. 5 by step of 0.5)
>>>TDD >>>>Primary CCPCH info
MP
>W
CV clause 2
>Hysteresis
MP
In dB.
3GPP
Release 6 Information Element/Group name >Threshold used frequency Need CVclause 3 Multi
671 Type and reference Integer (115..165)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Range used depend on measurement quantity. CPICH RSCP -115..-25 dBm CPICH Ec/No -24..0 dB Pathloss 30..165dB ISCP -115..-25 dBm Range used depend on measurement quantity. CPICH RSCP -120..-25 dBm CPICH Ec/No -24..0 dB Pathloss 30..165dB ISCP -120..-25 dBm If present, the actual value of Threshold used frequency = Threshold used frequency + DeltaThreshold used frequency Not used in Release 6 and later In event 1a Indicates the maximum number of cells allowed in the active set in order for event 1a to occur. 0 means not applicable . In event 1c Indicates the minimum number of cells allowed in the active set in order for event 1c to occur. 0 means not applicable In event 1j Indicates the minimum number of cells allowed in the E-DCH active set in order for event 1j to occur. For event 1j values 5, 6 and 7 are not applicable. 0 means not applicable Indicates the period of time during which the event condition has to be satisfied, before sending a Measurement Report. Time in ms In case the IE "Intrafrequency reporting criteria" is included in the IE "Inter-frequency measurement", this IE is not needed. Version
Integer (120..165)
REL-6
>DeltaThreshold used frequency
CVclause 8
Integer(5..-1)
REL-5
REL-6
>Reporting deactivation threshold
CV clause 4
Integer(0, 1, 2, 3, 4, 5, 6, 7)
>Replacement activation threshold
CVclause 5
Integer(0, 1, 2, 3, 4, 5, 6, 7)
REL-6
>Time to trigger
MP
Time to trigger 10.3.7.64
>Amount of reporting
CV clause 7
Integer(1, 2, 4, 8, 16, 32, 64, Infinity)
3GPP
Release 6 Information Element/Group name >Reporting interval Need CV clause 7 Multi
672 Type and reference Integer(0, 250, 500, 1000, 2000, 4000, 8000, 16000)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Indicates the interval of periodical reporting when such reporting is triggered by an event. Interval in milliseconds. 0 means no periodical reporting. In case the IE "Intra-frequency reporting criteria" is included in the IE "Interfrequency measurement", this IE is not needed. Version
OP
>Periodical reporting information-1b
CV clause 9
Reporting cell status 10.3.7.61 Periodical reporting info-1b 10.3.7.53 aa Boolean
>Use CIO
CVclause 10
In case the IE "Intrafrequency reporting criteria" is included in the IE "Inter-frequency measurement", this IE is not needed. TRUE indicates that the cell individual offset shall be used for event evaluation
REL-5
REL-5
Condition Clause 0
Clause 1
Clause 2
Clause 3
Clause 4
Clause 5
Clause 6
Clause 7
Clause 8
Clause 9 Clause 10
Explanation The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1b" or "1f", otherwise the IE is not needed. The IE is optional if the IE "Intra-frequency event identity" is set to "1a" or "1b", otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1a" or "1b", otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to , "1e", "1f", "1h" or "1i", otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1a", otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1c" or 1j , otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1a" or "1e", otherwise the IE is not needed. The IE is mandatory present if the IE "Intra-frequency event identity" is set to "1a", "1c" or 1j, otherwise the IE is not needed. The IE is optional if the IE "Intra-frequency event identity" is set to "1e", "1f", "1h" or "1i". Otherwise the IE is not needed. The IE is optional if the IE "Intra-frequency event identity" is set to "1b", otherwise the IE is not needed. The IE is optional if the IE "Intra-frequency event identity" is set to "1d", otherwise the IE is not needed.
3GPP
Release 6
673
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.40
Intra-frequency measurement system information

Need MD Multi Type and reference Measuremen t identity 10.3.7.48 Intrafrequency cell info list 10.3.7.33 Intrafrequency measuremen t quantity 10.3.7.38 Intrafrequency reporting quantity for RACH Reporting 10.3.7.42 Maximum number of reported cells on RACH 10.3.7.43 Reporting information for state CELL_DCH 10.3.7.62 Semantics description The intra-frequency measurement identity has default value 1.
Information Element/Group name Intra-frequency measurement identity Intra-frequency cell info list
OP
OP
Intra-frequency reporting quantity for RACH Reporting
OP
Maximum number of reported cells on RACH
OP
Reporting information for state CELL_DCH
OP
Note 1
NOTE 1: The reporting of intra-frequency measurements is activated when state CELL_DCH is entered.
10.3.7.41
Intra-frequency reporting quantity
Contains the reporting quantity information for an intra-frequency measurement.

Information Element/Group name Reporting quantities for active set cells Need MP Multi Type and reference Cell reporting quantities 10.3.7.5 Cell reporting quantities 10.3.7.5 Cell reporting quantities 10.3.7.5 Semantics description
Reporting quantities for monitored set cells
MP
Reporting quantities for detected set cells
OP
10.3.7.42
Intra-frequency reporting quantity for RACH reporting
Contains the reporting quantity information for an intra-frequency measurement report, which is sent on the RACH.
Information Element/Group name SFN-SFN observed time difference reporting indicator Need MP Multi Type and reference Enumerated( No report, Semantics description
3GPP
674 Multi Type and reference type 1, type 2)
CHOICE mode >FDD >>Reporting quantity
MP MP Enumerated( CPICH Ec/N0, CPICH RSCP, Pathloss, No report) MP MP 1 to 2 Enumerated( Timeslot ISCP, Primary CCPCH RSCP, No report)
>TDD >>Reporting quantity list >>>Reporting quantity
10.3.7.43
Maximum number of reported cells on RACH
Contains the maximum number of intra-frequency cells to be reported on RACH.

Information Element/Group name Maximum number of reported cells Need MP Multi Type and reference Enumerated (no report, current cell, current cell + best neighbour, current cell+2 best neighbours, , current cell+6 best neighbours) Semantics description
3GPP
Release 6
675
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.43a
MBMS preferred frequency information

Need MP Multi 1 to < maxMB MSFreq> Integer(1 .. <maxMBM S-Freq>) Absence of this information element means the currently used frequency. Value n corresponds with the th n frequency included in the IE New interfrequency cells that is specified within SIB 11 Type and reference Semantics description Version REL-6
Information Element/Group name MBMS preferred frequency list
>MBMS preferred frequency
OP
REL-6
>CHOICE Layer convergence information >>No HCS >>>Qoffmbms
MP
REL-6 REL-6 REL-6
MP
Enumerate d (4, 8, 12, 16, 20, 30, 40, infinity) Integer (0..7)
The offset in decibel [dB] added to cells on this MBMS preferred frequency Offset added to the normal HCS priority level of cells on this MBMS preferred frequency Included if some service restrictions apply for this preferred frequency e.g. congestion
>>HCS >>>HCS_OFFmbms
MP
REL-6 REL-6
>MBMS PL Service Restriction Information
OP
Enumerate d (TRUE)
REL-6
10.3.7.44
Measured results
Contains the measured results of the quantity indicated optionally by Reporting Quantity in Measurement Control. "Measured results" can be used for both event trigger mode and periodical reporting mode. For intra-frequency and inter-frequency measurements the list shall be in the order of the value of the measurement quantity (the first cell shall be the best cell). The "best" FDD cell has the largest value when the measurement quantity is "Ec/No" or "RSCP". On the other hand, the "best" cell has the smallest value when the measurement quantity is "Pathloss". The "best" TDD cell has the largest value when measurement quantity is "Primary CCPCH RSCP". For intra-frequency measurements, the ordering shall be applied to all cells included in the IE "Measured results". For inter-frequency measurements, the ordering shall be applied to all cells on the same frequency included in the IE "Measured results". For other measurements, the order of reported measurement objects is not specified.
Information Element/Group name CHOICE Measurement >Intra-frequency measured results list Need MP Intrafrequency measured results list 10.3.7.35 Interfrequency measured results list 10.3.7.15 Inter-RAT measured results list 10.3.7.26 Traffic Multi Type and reference Semantics description One spare value is needed.
>Inter-frequency measured results list
>Inter-RAT measured results list
>Traffic volume measured
3GPP
Release 6 Information Element/Group name results list Need
676 Multi Type and reference volume measured results list 10.3.7.67 Quality measured results list 10.3.7.55 UE Internal measured results 10.3.7.76 UE positioning measured results 10.3.7.99
>Quality measured results list
>UE Internal measured results
>UE positioning measured results
10.3.7.45
Measured results on RACH
For measurements on used frequency, this IE contains the measured results on RACH of the quantity indicated by Reporting quantity in the IE "Intra-frequency reporting quantity for RACH Reporting" in system information broadcast on BCH. The list, measurement results for monitored cells (not including the current cell) shall be in the order of the value of the measurement quantity as indicated by Reporting Quantity in the IE "Intra-frequency reporting quantity for RACH Reporting" (the first cell shall be the best cell). For measurements on non-used frequencies, this IE includes the best cell on each non- used frequency, in order of decreasing quality and up to a maximum number as specified by the IE "Maximum number of inter-frequency RACH reporting cells". The "best" FDD cell has the largest value when the measurement quantity is "Ec/No" or "RSCP". On the other hand, the "best" cell has the smallest value when the measurement quantity is "Pathloss". The "best" TDD cell has the largest value when measurement quantity is "Primary CCPCH RSCP".
Information Element/group name Measurement result for current cell >CHOICE mode >>FDD >>>CHOICE measurement quantity >>>>CPICH Ec/N0 Need MP MP MP Integer(0..49 ) One spare value is needed. In dB. According to CPICH_Ec/No in [19]. Fourteen spare values are needed. In dBm. According to CPICH_RSCP_LE V in [19]. Thirty-six spare values are needed. In dB. Fifteen spare values are needed. REL-4 REL-4 1 to 14 Multi Type and reference Semantics description Version
>>>>CPICH RSCP
Integer(0..91 )
>>>>Pathloss
Integer(46..1 58)
>>TDD >>>CHOICE TDD option >>>>3.84 Mcps TDD >>>>>Timeslot List
MP OP
3GPP
Release 6 Information Element/group name >>>>>>Timeslot ISCP Need MP
677 Multi Type and reference Timeslot ISCP info 10.3.7.65
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The UE shall report the Timeslot ISCP in the same order as indicated in the cell info Version
>>>>1.28 Mcps TDD >>>>>Timeslot List >>>>>>Timeslot ISCP
OP MP
1 to 6 Timeslot ISCP info 10.3.7.65 The UE shall report the Timeslot ISCP in the same order as indicated in the cell info
REL-4 REL-4 REL-4
>>>Primary CCPCH RSCP
OP
Primary CCPCH RSCP info 10.3.7.54 1 to 8
Measurement results for monitored cells on used frequency >SFN-SFN observed time difference
OP
OP
SFN-SFN observed time difference 10.3.7.63
>CHOICE mode >>FDD >>>Primary CPICH info
MP MP Primary CPICH info 10.3.6.60 One spare value is needed. In dB. According to CPICH_Ec/No in [19]. Fourteen spare values are needed. In dBm. According to CPICH_RSCP_LE V in [19]. Thirty-six spare values are needed. In dB. Fifteen spare values are needed.
>>>CHOICE measurement quantity >>>>CPICH Ec/N0
OP Integer(0..49 )
>>>>CPICH RSCP
Integer(0..91 )
>>>>Pathloss
Integer(46..1 58)
>>TDD >>>Cell parameters Id
MP
>>>Primary CCPCH RSCP
MP
Cell parameters Id 10.3.6.9 Primary CCPCH RSCP info 10.3.7.54 REL-6
Measurement results for monitored cells on non-used frequencies >Inter-frequency cell indicationSIB11 >Inter-frequency cell indicationSIB12
OP
MP MP
REL-6 REL-6
3GPP
Release 6 Information Element/group name >Inter-frequency cell list Need MP
678 Multi 1 to <maxFreq > Integer(0 .. <maxCellMe as>-1) Type and reference
>>Inter-frequency cell id
MP
REL-6
NOTE:
Monitored cells consist of neighbouring cells.
10.3.7.46
Measurement Command
Need MP Multi Type and reference Enumerated( Setup, Modify, Release) Semantics description
Information Element/Group name Measurement command
10.3.7.47

Need MP Multi Type and reference Enumerated (Not used, used) Enumerated (CPICH Ec/N0, CPICH RSCP) Semantics description Indicates if the serving cell belongs to a HCS structure Choice of measurement (CPICH Ec/N0 or CPICH RSCP) to use as quality measure Q.
Information element/Group name Use of HCS
Cell selection and reselection quality measure
MP
NOTE: For TDD,each choice of this parameter represents PCCPCH RSCP.
Intra-frequency measurement system information
OP
Inter-frequency measurement system information
OP
Inter-RAT measurement system information
OP
Traffic volume measurement system information
OP
Intrafrequency measuremen t system information 10.3.7.40 Interfrequency measuremen t system information 10.3.7.20 Inter-RAT measuremen t system information 10.3.7.31 Traffic volume measuremen t system information 10.3.7.73
3GPP
Release 6
679
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.47a
Measurement control system information extension

Need OP MP Multi Type and reference Semantics description Version REL-6 REL-6
Information element/Group name Intra-frequency cell info list >New intra-frequency cells
1 to <maxCellM eas> Integer(0 .. <maxCellMe as> - 1) Cell info 10.3.7.2 1 to <maxCellM eas> Frequency info 10.3.6.36 Default value is the value of the previous "frequency info" in the list. NOTE: The first occurrence is then MP.
>>Intra-frequency cell id
OP
REL-6
>>Cell info Inter-frequency cell info list >New inter-frequency cells
MP OP MP
REL-6 REL-6 REL-6
>>Frequency Info
MD
REL-6
>>Inter-frequency cell id
OP
>>Cell info Inter-RAT cell info list >>New inter-RAT cells
MP OP MP
Integer(0 .. <maxCellMe as> - 1) Cell info 10.3.7.2 1 to <maxCellM eas> Integer(0 .. <maxCellMe as> - 1)
REL-6
REL-6 REL-6 REL-6
>>Inter-RAT cell id
OP
REL-6
>>CHOICE Radio Access Technology >>>GSM >>>>Cell individual offset
MP
REL-6 REL-6 REL-6
MP
Integer (50..50 )
>>>>Cell selection and reselection info
OP
>>>>BSIC >>>>Band indicator
MP MP
>>>>BCCH ARFCN >>>IS-2000 >>>>System specific measurement info
MP
Cell selection and reselection info for SIB11/12 10.3.2.4 BSIC 10.3.8.2 Enumerated (DCS 1800 band used, PCS 1900 band used) Integer (0..1023) enumerated (frequency, timeslot, colour code, output power, PN offset)
In dB Used to offset measured quantity value See subclause 8.6.7.3
REL-6
REL-6 Indicates how to interpret the BCCH ARFCN REL-6
[45]
REL-6 REL-6 REL-6
MP
For IS-2000, use fields from TIA/EIA/IS2000.5, subclause 3. 7.3.3.2.27, Candidate
3GPP
Release 6
680
3GPP TS 25.331 V6.23.0 (2009-09) Frequency Neighbour List Message This value has been introduced to handle the case when IE "New inter-RAT cells" is not required
>>>None
(no data)
REL-6
10.3.7.48
Measurement Identity
A reference number that is used by the UTRAN at modification and release of the measurement, and by the UE in the measurement report.
Information Element/Group name Measurement identity Need Multi Type and reference Integer(1..16 ) Semantics description
MP
10.3.7.49
Measurement reporting mode
Contains the type of Measurement Report transfer mode and the indication of periodical/event trigger.
Information Element/Group name Measurement Report Transfer Mode Need Multi Type and reference enumerated (Acknowledg ed mode RLC, Unacknowle dged mode RLC) Enumerated (Periodical Semantics description
MP
Periodical Reporting / Event Trigger Reporting Mode
MP
reporting, Event trigger)
10.3.7.50
Measurement Type
Need MP Multi Type and reference Enumerated( Intrafrequency, Interfrequency, Inter-RAT, Traffic volume, Quality, UE internal, UE positioning) Semantics description
Information Element/Group name Measurement Type
3GPP
Release 6
681
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.51
Need MP Multi Type and reference Enumerated( CELL_DCH, all states except CELL_DCH, all states) Semantics description
Information Element/Group name UE state
10.3.7.52
Void
10.3.7.53
Periodical reporting criteria
Contains the periodical reporting criteria information. It is necessary only in the periodical reporting mode.
Information Element/Group name Amount of reporting Need MD Multi Type and reference Integer(1, 2, 4, 8, 16, 32, 64, Infinity) Integer(250, 500, 1000, 2000, 3000, 4000, 6000, 8000, 12000, 16000, 20000, 24000, 28000, 32000, 64000) Semantics description The default value is infinity.
Reporting interval
MP
Indicates the interval of periodical report. Interval in milliseconds
10.3.7.53aa Periodical reporting info-1b

Information Element/Group name Amount of reporting Need MP Multi Type and reference Integer(1, 2, 4, 8, 16, 32, 64, Infinity) Integer(0, 250, 500, 1000, 2000, 4000, 8000, 16000) Semantics description Version REL-5
Reporting interval
MP
Indicates the interval of periodical reporting when such reporting is triggered by an event. Interval in milliseconds. 0 means no periodical reporting.
REL-5
10.3.7.53a
PLMN identities of neighbour cells
This IE contains the PLMN identities of neighbour cells.

Information Element/Group name PLMNs of intra-frequency cells list Need OP Multi 1 to <maxCellM eas> Type and reference Semantics description
3GPP
Release 6 Information Element/Group name >PLMN identity Need OP
682 Multi Type and reference PLMN identity 10.3.1.11
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Action when not present is specified in subclause 8.1.1.6.18.
PLMNs of inter-frequency cells list >PLMN identity
OP
1 to <maxCellM eas> PLMN identity 10.3.1.11 1 to <maxCellM eas> PLMN identity 10.3.1.11 Action when not present is specified in subclause 8.1.1.6.18. Action when not present is specified in subclause 8.1.1.6.18.
OP
PLMNs of inter-RAT cells list
OP
>PLMN identity
OP
10.3.7.54
NOTE:
Primary CCPCH RSCP info

Only for TDD
Need Multi IE type and reference Integer(0.. 91) Semantics description Version
Information Element/Group name Primary CCPCH RSCP
MP
DeltaPrimary CCPCH RSCP
CV-Rel5
Integer(5..-1)
According to PCCPCH_RSCP_LEV in [19] and [20]. Thirty-six spare values are needed. If present, the actual value of Primary CCPCH RSCP = Primary CCPCH RSCP+ DeltaPrimary
CCPCH RSCP
REL-5
Condition Rel5
Explanation This IE is mandatory if the value of Primary CCPCH RSCP is below 0. Othewise the IE is not needed.
10.3.7.54a
Qhcs
Need Multi Type and Referenc e Semantics description Version
Information Element/Group name
3GPP
Release 6 Information Element/Group name Qhcs Need Multi
683 Type and Referenc e Integer( 0..99)
MP
Qhcs, mapped from CPICH Ec/No (FDD), see [4] [dB] 0: -24 1: -23.5 2: -23 3: -22.5 ... 45: -1.5 46: -1 47: -0.5 48: 0 49: (spare) ... 98: (spare) 99: (spare) Qhcs, mapped from CPICH RSCP (FDD), see [4] [dBm] 0: -115 1: -114 2: -113 : 88: -27 89: -26 90: -(spare) 91: -(spare) : 98: -(spare) 99: -(spare) Qhcs, mapped from PCCPCH RSCP (TDD), see [4] [dBm] 0: -115 1: -114 2: -113 : 88: -27 89: -26 90: -(spare) 91: -(spare) : 98: -(spare) 99: -(spare)
3GPP
684 Type and Referenc e
DeltaQhcs-RSCP
CVRSCP
Integer(5..-1)
Qhcs level, mapped from Averaged received signal level RSSI (GSM), see [4] [dBm] 0: -110 1: -109 2: -108 : 61: -49 62: -48 63: -47 64: -46 65: -45 66: -44 67: -43 68: -42 69: -41 70: -40 71: -39 72: -38 73: -37 74: -(spare) : 98: -(spare) 99: -(spare) If present, the actual value of Qhcs = Qhcs + DeltaQhcs-RSCP
REL-5
Condition RSCP
Explanation This IE is optional if Qhcs is mapped from CPICH RSCP or PCCPCH RSCP, and if the value of the RSCP is below 0 (-115dBm). It is not needed otherwise.
10.3.7.55
Quality measured results list

Need OP Multi 1 to <maxTrCH > Transport channel identity 10.3.5.18 Integer (0..63) transport channel type = DCH Type and reference Semantics description
Information Element/Group name BLER measurement results
>DL Transport channel identity
MP
>DL Transport Channel BLER CHOICE mode >FDD >TDD >>SIR measurement results
OP MP
According to BLER_LOG in [19] and [20] No data
OP
1 to <MaxCCTr CH> Integer(1...8) 1 to <maxTS> Integer(0..63 )
SIR measurements for DL CCTrCH
>>>TFCS ID >>>Timeslot list >>>>SIR
MP MP MP
for all timeslot on which the CCTrCH is mapped on According to UE_SIR in [20]
3GPP
Release 6
685
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.56
Quality measurement
Need OP Multi Type and reference Quality reporting quantity 10.3.7.59 Quality measuremen t reporting criteria 10.3.7.58 Periodical reporting criteria 10.3.7.53 Semantics description
Information Element/Group name Quality reporting quantity
CHOICE report criteria >Quality measurement reporting criteria
MP Note Given this choice, the IE "DL Transport Channel BLER" shall be set to "False" (see subclause 10.3.7.59) Note
>No reporting
Note (no data) Chosen when this measurement only is used as additional measurement to another measurement
NOTE:
In this version of the specification, BLER as additional measurement is not supported.
10.3.7.57
Quality measurement event results

Need OP Multi 1 to <maxTrCH > Transport channel identity 10.3.5.18 transport channel type = DCH Type and reference Semantics description
Information Element/Group name Transport channels causing the event >DL Transport channel identity
MP
10.3.7.58
Quality measurement reporting criteria
Event 5a: Number of bad CRCs on a certain transport channel exceeds a threshold.
Information Element/Group name Parameters sent for each transport channel >DL Transport channel identity Need MP Multi 1 to <maxTrCH > Transport channel identity 10.3.5.18 Integer(1..51 2) Integer(1..51 2) Integer(1..51 2) transport channel type = DCH Type and reference Semantics description
MP
>Total CRC >Bad CRC >Pending after trigger
MP MP MP
Number of CRCs Number of CRCs Number of CRCs
3GPP
Release 6
686
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.59
Quality reporting quantity

Need MP CV-BLER reporting Multi Type and reference Boolean Semantics description TRUE means report requested The default, if no transport channel identities are present, is that the BLER is reported for all downlink transport channels transport channel type = DCH
Information Element/Group name DL Transport Channel BLER Transport channels for BLER reporting
1 to <maxTrCH > Transport channel identity 10.3.5.18
>DL Transport channel identity
MP
CHOICE mode >FDD >TDD >>SIR measurement list
MP No data OP 1 to <maxCCTr CH> Integer(1...8) SIR measurements shall be reported for all listed TFCS IDs
>>>TFCS ID
MP
Condition BLER reporting
Explanation This IE is not needed if the IE "DL Transport Channel BLER" is "False" and optional if the IE "DL Transport Channel BLER" is "True"
10.3.7.60
Reference time difference to cell
In the System Information message, the reference time difference to cell indicates the timing difference between the primary CCPCH of the current cell and the primary CCPCH of a neighbouring cell.. In the Measurement Control message, the reference time difference to cell indicates the timing difference between UE uplink transmission timing and the primary CCPCH of a neighbouring cell.
Information Element/Group name CHOICE accuracy >40 chips >>Reference time difference Need MP MP Integer(0..38 400 by step of 40) Integer(0.. 38400 by step of 256) Integer(0.. 38400 by step of 2560) In chips Multi Type and reference Semantics description
>256 chips >>Reference time difference
MP
In chips
>2560 chips >>Reference time difference
MP
In chips
10.3.7.61
Reporting Cell Status
Indicates maximum allowed number of cells to report and whether active set cells and/or virtual active set cells and/or monitored set cells on and/or detected set cells used frequency and/or monitored set cells on non used frequency should/should not be included in the IE "Measured results".
Information Element/Group name CHOICE reported cell >Report cells within active set Need Multi Type and reference Semantics description
MP
This choice is not valid for inter-RAT measurements. For inter-frequency measurements
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description it is only valid for reporting events 2D and 2F. See NOTE 1.
>>Maximum number of reported cells >Report cells within monitored set cells on used frequency >>Maximum number of reported cells >Report cells within active set and/or monitored set cells on used frequency >>Maximum number of reported cells >Report cells within detected set on used frequency >>Maximum number of reported cells >Report cells within monitored set and/or detected set on used frequency >>Maximum number of reported cells >Report all active set cells + cells within monitored set on used frequency >>Maximum number of reported cells
MP
Integer(1..6) This choice is not valid for inter-RAT or inter-frequency measurements
MP
MP
MP
MP
MP
Enumerated (virtual/activ e set cells+1, virtual/active set cells+2, ., virtual/active set cells+6) This choice is not valid for inter-RAT or inter-frequency measurements
>Report all active set cells + cells within detected set on used frequency >>Maximum number of reported cells
MP
Enumerated (virtual/activ e set cells+1, virtual/active set cells+2, ., virtual/active set cells+6) This choice is not valid for inter-RAT or inter-frequency measurements
>Report all active set cells + cells within monitored set and/or detected set on used frequency >>Maximum number of reported cells
MP
Enumerated (virtual/activ e set cells+1, virtual/active set cells+2, ., virtual/active set cells+6) This choice is not valid for intra-frequency or inter-RAT measurements
>Report cells within virtual active set >>Maximum number of reported cells per reported non-used frequency >Report cells within monitored set on non-used frequency
MP
Integer(1..6)
This choice is not valid for intra-frequency or inter-RAT
3GPP
Release 6 Information Element/Group name >>Maximum number of reported cells per reported non-used frequency >Report cells within monitored and/or virtual active set on nonused frequency >>Maximum number of reported cells per reported non-used frequency >Report all virtual active set cells + cells within monitored set on non-used frequency >>Maximum number of reported cells per reported non-used frequency Need
688 Multi Type and reference Integer(1..6)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description measurements
MP
This choice is not valid for intra-frequency or inter-RAT measurements
MP
Integer(1..6)
This choice is not valid for intra-frequency or inter-RAT measurements
MP
Enumerated (virtual/activ e set cells+1, virtual/active set cells+2, ., virtual/active set cells+6) If this choice is selected for inter-RAT measurements, the UE shall report only cells of the other RAT. If this choice is selected for intra-frequency measurements, the UE shall report cells within the active set. If this choice is selected for inter-frequency measurements, the UE shall report cells within the virtual active set.
>Report cells within active set or within virtual active set or of the other RAT
>>Maximum number of reported cells >Report cells within active and/or monitored set on used frequency or within virtual active and/or monitored set on nonused frequency
MP
Integer (1..12) This choice is not valid for inter-RAT measurements. If this choice is selected for intra-frequency measurements, the UE shall report cells within the active and/or monitored set. If this choice is selected for inter-frequency measurements, the UE shall report cells within the virtual active set and/or monitored set on non-used frequency.
>>Maximum number of reported cells
MP
Integer(1..12 )
NOTE 1: For Inter-frequency reporting events 2D and 2F, only CHOICE "Report cells within active set" is valid.
3GPP
Release 6
689
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.62
Reporting information for state CELL_DCH

Need MP Multi Type and reference Intrafrequency reporting quantity 10.3.7.41 Measuremen t Reporting Mode 10.3.7.49 Intrafrequency measuremen t reporting criteria 10.3.7.39 Periodical reporting criteria 10.3.7.53 Semantics description
Information Element/Group name Intra-frequency reporting quantity
MP
MP
10.3.7.63
SFN-SFN observed time difference

Need MP Integer(0.. 9830399) According to T1_SFN-SFN_TIME in [19] and [20]. For FDD and 3.84 Mcps TDD: 6946816 spare values are needed. For 1.28 Mcps TDD: 13500416 spare values are needed. According to T2_SFN-SFN_TIME in [19] and [20]. 24574 spare values are needed. For 1.28 Mcps TDD: 37886 spare values are needed. Multi Type and reference Semantics description Version
Information Element/Group name CHOICE type >Type 1
>Type 2
Integer(0.. 3276799) Integer(0.. 40961) Integer(0.. 27649)
Rel-4
Rel-4
10.3.7.64
Time to trigger
Need MP Multi Type and reference Integer(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000) Semantics description Time in ms
Information Element/Group name Time to trigger
10.3.7.65
NOTE:
Timeslot ISCP info

Only for TDD
3GPP
Release 6 Information Element/Group name Timeslot ISCP Need MP
690 Multi IE type and reference Integer (0..91)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description According to UE_TS_ISCP_LEV in [20]. Thirty-six spare values are needed.
10.3.7.66
Traffic volume event identity

Need MP Multi Type and reference Enumerated( 4a, 4b) Semantics description
Information Element/Group name Traffic volume event identity
10.3.7.67
Traffic volume measured results list

Need OP MP OP Multi 1 to <maxRB> RB Identity 10.3.4.16 Enumerated( 0, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2K, 4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K, 1024K) Enumerated( 0, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2K, 4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K, 1024K) Enumerated( 0, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2K, 4K, 8K, 16K) Type and reference Semantics description
Information Element/Group name Traffic volume measurement results >RB Identity >RLC Buffers Payload
In bytes And N Kbytes = N*1024 bytes. Twelve spare values are needed.
>Average of RLC Buffer Payload
OP
In bytes And N Kbytes = N*1024 bytes. Twelve spare values are needed.
>Variance of RLC Buffer Payload
OP
In bytes And N Kbytes = N*1024 bytes. Two spare values are needed.
3GPP
Release 6
691
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.68

Need OP Multi Type and reference Traffic volume measuremen t Object 10.3.7.70 Traffic volume measuremen t quantity 10.3.7.71 Traffic volume reporting quantity 10.3.7.74 Measuremen t validity 10.3.7.51 Traffic volume measuremen t reporting criteria 10.3.7.72 Periodical reporting criteria 10.3.7.53 (no data) Chosen when this measurement only is used as additional measurement to another measurement Semantics description
Information Element/Group name Traffic volume measurement Object
Traffic volume measurement quantity
OP
Traffic volume reporting quantity
OP
OP
CHOICE report criteria >Traffic volume measurement reporting criteria
MP
>No reporting
10.3.7.69
Traffic volume measurement event results
Contains the event result for a traffic volume measurement.

Information Element/Group name Uplink transport channel type causing the event Need MP Multi Type and reference Enumerated( DCH,RACH, USCH) Transport channel identity 10.3.5.18 Traffic volume event identity 10.3.7.66 Semantics description USCH is TDD only. RACH is the currently configured default in the uplink.
UL Transport Channel identity
CV-ULDCH/USC H MP
Traffic volume event identity
Condition UL-DCH/USCH
Explanation If IE "Uplink transport channel type" is equal to "DCH" or "USCH" (TDD only) this IE is mandatory present. Otherwise the IE is not needed.
3GPP
Release 6
692
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.70
Traffic volume measurement object
Contains the measurement object information for a traffic volume measurement.

Information Element/Group name Traffic volume measurement objects >Uplink transport channel type Need MP Multi 1 to <maxTrCH > Enumerated( DCH,RACH, USCH) Transport channel identity 10.3.5.18 USCH is TDD only. RACH is the currently configured default in the uplink. Type and reference Semantics description
MP
>UL Target Transport Channel ID
CV-ULDCH/USC H
Explanation If IE "Uplink transport channel type" is equal to "DCH" or "USCH" (TDD only) this IE is mandatory present. Otherwise the IE is not needed.
10.3.7.71
Contains the measurement quantity information for a traffic volume measurement.

Information Element/Group name Measurement quantity Need MP Multi Type and reference Enumerated( RLC buffer payload, Average RLC buffer payload, Variance of RLC buffer payload) Integer(20, 40, ..260, by steps of 20) Semantics description This parameter should be ignored.
Time Interval to take an average or a variance
CV-A/V
In ms
Condition A/V
Explanation This IE is mandatory present when "Average RLC buffer" or "Variance of RLC buffer payload" is chosen and not needed otherwise.
3GPP
Release 6
693
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.72
Traffic volume measurement reporting criteria
Contains the measurement reporting criteria information for a traffic volume measurement. Event 4a: Transport Channel Traffic Volume [15] exceeds an absolute threshold. Event 4b: Transport Channel Traffic Volume [15] becomes smaller than an absolute threshold.
Information Element/Group name Parameters sent for each transport channel >Uplink transport channel type Need OP Multi 1 to <maxTrCH > Enumerated( DCH,RACH, USCH) Transport channel identity 10.3.5.18 1 to <maxMeas parEvent> Traffic volume event identity 10.3.7.66 Enumerated( 8,16,32,64,1 28,256,512,1 024,2K,3K,4 K,6K,8K,12K ,16K,24K,32 K,48K,64K,9 6K,128K,192 K,256K,384 K,512K,768 K) Time to trigger 10.3.7.64 Type and reference Semantics description This IE is always required, need is OP to align with ASN.1 USCH is TDD only. RACH is the currently configured default in the uplink.
OP
>UL Transport Channel ID
CV-ULDCH/USC H OP
>Parameters required for each Event >>Traffic volume event identity
MP
>>Reporting Threshold
MP
Threshold in bytes And N Kbytes = N*1024 bytes
>>Time to trigger
OP
>>Pending time after trigger
OP
Integer(250, 500, 1000, 2000, 4000, 8000, 16000)
>>Tx interruption after trigger
OP
Integer (250, 500, 1000, 2000, 4000, 8000, 16000)
Indicates the period of time during which the event condition has to be satisfied, before sending a Measurement Report. Time in ms Indicates the period of time during which it is forbidden to send any new measurement reports with the same Traffic volume event identity even if the triggering condition is fulfilled. Time in milliseconds Time in milliseconds. Indicates how long the UE shall block DTCH transmissions on the RACH after a measurement report is triggered.
Explanation If IE "Uplink transport channel type" is equal to "DCH" or "USCH" (TDD only) this IE is optional. Otherwise the IE is not needed.
3GPP
Release 6
694
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.73
Traffic volume measurement system information

Need MD Multi Type and reference Measuremen t identity 10.3.7.48 Traffic volume measuremen t object 10.3.7.70 Traffic volume measuremen t quantity 10.3.7.71 Traffic volume reporting quantity 10.3.7.74 Measuremen t validity 10.3.7.51 Measuremen t Reporting Mode 10.3.7.49 Traffic volume measuremen t reporting criteria 10.3.7.72 Periodical reporting criteria 10.3.7.53 Semantics description The traffic volume measurement identity has default value 4.
Information Element/Group name Traffic volume measurement identity Traffic volume measurement object
OP
OP
OP
OP
MP
CHOICE reporting criteria >Traffic volume measurement reporting criteria
MP
10.3.7.74
Contains the reporting quantity information for a traffic volume measurement. For all boolean types TRUE means inclusion in the report is requested.
Information Element/Group name RLC Buffer Payload for each RB Average of RLC Buffer Payload for each RB Variance of RLC Buffer Payload for each RB Need MP MP MP Multi Type and reference Boolean Boolean Boolean Semantics description
10.3.7.75
UE internal event identity

Need MP Multi Type and reference Enumerated( 6a,6b,6c,6d, 6e, 6f, 6g) Semantics description
Information Element/Group name UE internal event identity
3GPP
Release 6
695
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.76
UE internal measured results

Need MP OP UE Transmitted Power info 10.3.7.85 1 to <maxRL> Primary CPICH info 10.3.6.60 UE Rx-Tx time difference type 1 10.3.7.83 1 to <maxTS> Primary CPICH info for each cell included in the active set UE Rx-Tx time difference in chip for each RL included in the active set UE Transmitted Power for each used uplink timeslot in ascending timeslot number order UE Transmitted Power info 10.3.7.85 REL-4 REL-4 Uplink Timing Advance 10.3.6.95 TADV info 10.3.7.112 Uplink timing advance applied by the UE REL-4 REL-4 Multi Type and reference Semantics description Version
Information Element/Group name CHOICE mode >FDD >>UE Transmitted Power
>>UE Rx-Tx report entries >>>Primary CPICH info
OP MP
>>>UE Rx-Tx time difference type 1
MP
>TDD >>UE Transmitted Power list
OP
>>>UE Transmitted Power
MP
>>CHOICE TDD option >>>3.84 Mcps TDD >>>>Applied TA
MP OP
>>>1.28 Mcps TDD >>>>TADV
OP
3GPP
Release 6
696
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.77
Need OP Multi Type and reference UE internal measuremen t quantity 10.3.7.79 UE internal reporting quantity 10.3.7.82 UE internal measuremen t reporting criteria 10.3.7.80 Periodical reporting criteria 10.3.7.53 (no data) Chosen when this measurement only is used as additional measurement to another measurement Semantics description
Information Element/Group name UE internal measurement quantity
UE internal reporting quantity
OP
CHOICE report criteria >UE internal measurement reporting criteria
MP
>No reporting
CHOICE report criteria UE internal measurement reporting criteria Periodical reporting criteria No reporting
Condition under which the given report criteria is chosen Chosen when UE internal measurement event triggering is required Chosen when periodical reporting is required Chosen when this measurement only is used as additional measurement to another measurement
10.3.7.78
UE internal measurement event results
This IE contains the measurement event results that are reported to UTRAN for UE internal measurements.
Information Element/Group name UE internal event identity Need MP Multi Type and reference UE internal event identity 10.3.7.75 Semantics description
CHOICE mode >FDD >Primary CPICH info
MP CV-clause 1 Primary CPICH info 10.3.6.60 (no data)
>TDD
Condition Clause 1
Explanation This IE is mandatory present if the IE "UE internal event identity" is set to "6f" or "6g", otherwise the IE is not needed.
10.3.7.79
UE internal measurement quantity
The quantity the UE shall measure in case of UE internal measurement.
3GPP
Release 6 Information Element/Group name CHOICE mode >FDD >>Measurement quantity Need MP MP
Enumerated( UE Transmitted Power, UTRA Carrier RSSI, UE Rx-Tx time difference) Enumerated( UE Transmitted Power, UTRA Carrier RSSI, TADV)
>TDD >>Measurement quantity
MP
Filter coefficient
OP
Filter coefficient 10.3.7.9
Measurement on Timing Advance is for 1.28 Mcps TDD If the IE "Measurement quantity" is set to "Rx-Tx time difference" and this IE is present, the UE behaviour is unspecified.
REL-4
10.3.7.80
UE internal measurement reporting criteria
The triggering of the event-triggered reporting for a UE internal measurement. All events concerning UE internal measurements are labelled 6x where x is a, b, c. In TDD, the events 6a - 6d are measured and reported on timeslot basis. Event 6a: The UE Transmitted Power becomes larger than an absolute threshold Event 6b: The UE Transmitted Power becomes less than an absolute threshold Event 6c: The UE Transmitted Power reaches its minimum value Event 6d: The UE Transmitted Power reaches its maximum value Event 6e: The UE RSSI reaches the UEs dynamic receiver range Event 6f (FDD): The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold Event 6f (1.28 Mcps TDD): The time difference indicated by TADV becomes larger than an absolute threshold Event 6g: The UE Rx-Tx time difference for a RL included in the active set becomes less than an absolute threshold
Information Element/Group name Parameters sent for each UE internal measurement event >UE internal event identity Need OP Multi 1 to <maxMeas Event> UE internal event identity 10.3.7.75 Type and reference Semantics description Version
MP
3GPP
Release 6 Information Element/Group name >Time-to-trigger Need MP
698 Multi Type and reference Integer(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000) Integer(50..33) Integer(768.. 1280) Real (0..63 step 0.125)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Time in ms. Indicates the period of time between the timing of event detection and the timing of sending Measurement Report. Power in dBm. In event 6a, 6b. Time difference in chip. In event 6f, 6g. Time difference in chip. In event 6f Version
>UE Transmitted Power Tx power threshold >UE Rx-Tx time difference threshold >TADV threshold
CV-clause 1 CV-clause 2 CV-clause 3
REL-4
Condition Clause 1
Clause 2
Clause 3
Explanation The IE is mandatory present if the IE "UE internal event identity" is set to "6a" or "6b", otherwise the IE is not needed. In FDD, the IE is mandatory present if the IE "UE internal event identity" is set to "6f" or "6g", otherwise the IE is not needed. In 1.28 Mcps TDD the IE is mandatory present if the IE "UE internal event identity" is set to "6f", otherwise the IE is not needed.
10.3.7.81
Void
10.3.7.82
UE Internal reporting quantity
For all boolean types TRUE means inclusion in the report is requested.
Information Element/Group name UE Transmitted Power CHOICE mode >FDD >>UE Rx-Tx time difference >TDD >>CHOICE TDD option >>>3.84 Mcps TDD >>Applied TA >>>1.28 Mcps TDD >>>>TADV info Need MP MP MP Multi Type and reference Boolean Semantics description Version
Boolean REL-4 REL-4 REL-4 REL-4
(no data) MP MP Boolean Boolean
10.3.7.83
UE Rx-Tx time difference type 1
The difference in time between the UE uplink DPCCH/DPDCH frame transmission and the first detected path (in time), of the downlink DPCH or F-DPCH frame from the measured radio link, as defined in [7]. This measurement is for FDD only.
Information Element/Group name UE Rx-Tx time difference type 1 Need Multi Type and reference Integer(768.. 1280) Semantics description In chips. 511 spare values are needed.
MP
3GPP
Release 6
699
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.84
UE Rx-Tx time difference type 2
The difference in time between the UE uplink DPCCH/DPDCH frame transmission and the first detected path (in time), of the downlink DPCH or F-DPCH frame from the measured radio link, as defined in [7].
Information Element/Group name UE Rx-Tx time difference type 2 Need Multi Type and reference Integer (0..8191) Semantics description According to [19].
MP
10.3.7.85
UE Transmitted Power info
Information Element/Group name UE Transmitted Power
Need MP
Multi
IE type and reference Integer (0..104)
Semantics description According to UE_TX_POWER in [19] and [20]
10.3.7.86
UE positioning Ciphering info
This IE contains information for the ciphering of UE positioning assistance data broadcast in System Information.
Information Element/Group name Ciphering Key Flag Ciphering Serial Number Need MP MP Multi Type and Reference Bit string(1) Integer(0..65 535) Semantics description
The serial number used in the DES ciphering algorithm
3GPP
Release 6
700
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.87
UE positioning Error
Need MP Multi Type and Reference Enumerated( Not Enough OTDOA Cells, Not Enough GPS Satellites, Assistance Data Missing, Not Accomplishe d GPS Timing Of Cell Frames, Undefined Error, Request Denied By User, Not Processed And Timeout, Reference Cell Not Serving Cell) UE positioning GPS Additional Assistance Data Request 10.3.7.88a Semantics description Note 1
Information Element/Group name Error reason
GPS Additional Assistance Data Request
CVGPSdataM issing
NOTE 1: The following table describes each value of the IE "Error reason".
Value Not Enough OTDOA Cells Not Enough GPS Satellites Assistance Data Missing Not Accomplished GPS Timing Of Cell Frames Undefined Error Request Denied By User Not Processed And Timeout Reference Cell Not Serving Cell Indication There were not enough cells to be received. There were not enough GPS satellites to be received. UE positioning GPS assistance data missing. UE was not able to accomplish the GPS timing of cell frames measurement. Undefined error. UE positioning request denied by upper layers. UE positioning request not processed by upper layers and timeout. UE was not able to read the SFN of the reference cell.
Condition GPSdataMissing
Explanation The IE is optional if the IE "Error reason" is " Assistance Data Missing " and not needed otherwise.
10.3.7.88
UE positioning GPS acquisition assistance
This IE contains parameters that enable fast acquisition of the GPS signals in UE-assisted GPS positioning.
Information Element/Group name GPS TOW msec Need MP Multi Type and Reference Integer(0..6. Semantics description GPS Time of Week in
3GPP
701 Multi Type and Reference 8 048*10 -1)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description milliseconds rounded down to the nearest millisecond unit. It is also the time when satellite information is valid. GPS timing of cell frames in steps of 1 chip.
UTRAN GPS reference time >UTRAN GPS timing of cell frames >CHOICE mode >>FDD >>>Primary CPICH Info
OP MP
Integer(0 ... 2322431999 999)
OP MP Primary CPICH Info 10.3.6.60 Cell parameters id 10.3.6.9 Integer(0..40 95) 1 to <maxSat> Integer (0..63) Real(5120..5117.5 by step of 2.5) Real (0.966..0.483 by step of 0.023) Enumerated (12.5,25,50, 100,200) Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. Hz Identifies the reference cell for the GPS TOW-SFN relationship Identifies the reference cell for the GPS TOW-SFN relationship The SFN which the UTRAN GPS timing of cell frames time stamps.
>>TDD >>>cell parameters id
MP
>SFN
MP
Satellite information >SatID

th
MP MP
>Doppler (0 order term)
MP
>Extra Doppler st >>Doppler (1 order term)
OP MP
Hz/s
>>Doppler Uncertainty
MP
>Code Phase
MP
Integer(0..10 22)
>Integer Code Phase
MP
Integer(0..19 )
>GPS Bit number >Code Phase Search Window
MP MP
Integer(0..3) Integer(1023 ,1,2,3,4,6,8,1 2,16,24,32,4 8,64,96,128, 192) Real(0..348. 75 by step of 11.25)
Hz. Three spare values are needed. The Doppler experienced by a stationary UE is in the range Doppler Doppler Uncertainty to Doppler + Doppler Uncertainty. GPS chips. Increasing binary values of the field signify increasing predicted pseudoranges. Number of code periods that have elapsed since the latest GPS bit boundary, in units of C/A code period. Specifies GPS bit number modulo 4 Expected code-phase is in the range Code Phase Code Phase Search Window to Code Phase + Code Phase Search Window. Degrees An angle of x degrees means the satellite azimuth a is in the range x a < x+11.25 degrees. Degrees An angle of y degrees means
>Azimuth and Elevation >>Azimuth
OP MP
>>Elevation
MP
Real(0..78.7 5 by step of
3GPP
702 Multi Type and Reference 11.25)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description the satellite elevation e is in the range y e < y+11.25 degrees except for y=78.75 where the range is extended to include 90 degrees.
10.3.7.88a
UE positioning GPS Additional Assistance Data Request

Need MP MP MP MP MP MP MP MP MP CVNavigation Model MP MP Multi Type and Reference Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Semantics description TRUE means requested TRUE means requested TRUE means requested TRUE means requested TRUE means requested TRUE means requested TRUE means requested TRUE means requested TRUE means requested this IE is present only if "Navigation Model" is set to TRUE otherwise it is absent
Information Element/Group name Almanac UTC Model Ionospheric model Navigation Model DGPS Corrections Reference Location Reference Time Acquisition Assistance Real-Time Integrity Navigation Model Additional data >GPS Week >GPS_Toe
>T-Toe limit
MP
Integer (0..10) 0 to <maxSat> Integer (0..63) Integer (0..255)
GPS time of ephemeris in hours of the latest ephemeris set contained by the UE. Eighty-eight spare values needed. ephemeris age tolerance of the UE to UTRAN in hours. Five spare values needed.
>Satellites list related data >>SatID
MP MP
>>IODE
MP
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. Issue of Data Ephemeris for SatID
3GPP
Release 6
703
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.89
UE positioning GPS almanac
This IE contains a reduced-precision subset of the ephemeris and clock correction parameters.
Information Element/Group name WNa Satellite information >DataID >SatID Need MP MP MP MP Multi Type and Reference Bit string(8) Semantics description Almanac Reference Week [12]
1 to <maxSat> Integer(0..3) Enumerated( 0..63) Bit string(16) Bit string(8) Bit string(16) Bit string(16) See [12] Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. Eccentricity [12] Reference Time of Almanac [12] Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles/sec) [12] Semi-Major Axis (meters) [12] Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) [12] Mean Anomaly at Reference Time (semi-circles) [12] Argument of Perigee (semicircles) [12] apparent clock correction [12] apparent clock correction [12] This enables GPS time recovery and possibly extended GPS correlation intervals. It is specified in page 25 of subframes 4 and 5 [12]
1/2
>e >toa >i >OMEGADOT
MP MP MP MP
>SV Health 1/2 >A >OMEGA0
MP MP MP
Bit string(8) Bit string(24) Bit string(24)
>M0 > >af0 >af1 SV Global Health
MP MP MP MP OP
Bit string(24) Bit string(24) Bit string(11) Bit string(11) Bit string(364)
10.3.7.90
This IE contains GPS assistance data.

Information Element/Group name UE positioning GPS reference time Need OP Multi Type and Reference UE positioning GPS reference time 10.3.7.96 Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c UE positioning GPS DGPS corrections 10.3.7.91 Semantics description
UE positioning GPS reference UE position
OP
A priori knowledge of UE 3-D position.
UE positioning GPS DGPS corrections
OP
3GPP
Release 6 Information Element/Group name UE positioning GPS navigation model Need OP
704 Multi Type and Reference UE positioning GPS navigation model 10.3.7.94 UE positioning GPS ionospheric model 10.3.7.92 UE positioning GPS UTC model 10.3.7.97 UE positioning GPS almanac 10.3.7.89 UE positioning GPS acquisition assistance 10.3.7.88 UE positioning GPS realtime integrity 10.3.7.95
UE positioning GPS ionospheric model
OP
UE positioning GPS UTC model
OP
UE positioning GPS almanac
OP
UE positioning GPS acquisition assistance
OP
OP
10.3.7.90a
Void
10.3.7.91
This IE contains DGPS corrections to be used by the UE.

Information Element/Group name GPS TOW sec Need MP Multi Type and Reference Integer(0..60 4799) Semantics description seconds GPS time-of-week when the DGPS corrections were calculated
Status/Health
MP
Enumerated( UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.2, UDRE scale 0.1, no data, invalid data) 1 to <maxSat> If the Cipher information is included these fields are ciphered.
DGPS information
CVStatus/Hea lth
3GPP
Release 6 Information Element/Group name >SatID Need MP
705 Multi Type and Reference Enumerated (063) Integer(0..25 5) Enumerated( UDRE 1.0 m, 1.0m < UDRE 4.0m, 4.0m < UDRE 8.0m, 8.0m < UDRE) Real(655.04..655. 04 by step of 0.32) Real(4.064..4.064 by step of 0.032) Integer(127..127) Real(0.224..0.224 by step of 0.032) Integer(127..127)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12].
>IODE >UDRE
MP MP
The value in this field shall be multiplied by the UDRE Scale Factor in the IE Status/Health to determine the final UDRE estimate for the particular satellite.
>PRC
MP
meters (different from [13])
>RRC
MP
meters/sec (different from [13])
>Delta PRC2
MP
>Delta RRC2
MP
In this version of the protocol this IE should be set to zero and the UE shall ignore it In this version of the protocol this IE should be set to zero and the UE shall ignore it This IE should not be included in this version of the protocol and if received the UE shall ignore it This IE should not be included in this version of the protocol and if received the UE shall ignore it
>Delta PRC3
OP
>Delta RRC3
OP
Real(0.224..0.224 by step of 0.032)
Condition Status/Health
Explanation This IE is mandatory present if "status" is not equal to "no data" or "invalid data", otherwise the IE is not needed.
10.3.7.91a
UE positioning GPS Ephemeris and Clock Correction parameters
This IE contains information for GPS ephemeris and clock correction.

Information Element/Group name C/A or P on L2 URA Index SV Health IODC L2 P Data Flag SF 1 Reserved TGD toc af2 Need MP MP MP MP MP MP MP MP MP Multi Type and Reference Bit string(2) Bit string(4) Bit string(6) Bit string(10 Bit string(1) Bit string(87) Bit string(8) Bit string(16 Bit string(8)
) )
Semantics description Code(s) on L2 Channel [12] User Range Accuracy [12] [12] Issue of Data, Clock [12] [12] [12] Estimated group delay differential [12] apparent clock correction [12] apparent clock correction [12]
3GPP
Release 6 Information Element/Group name af1 af0 Crs n M0 Cuc Need MP MP MP
706 Multi Type and Reference Bit string(16) Bit string(22) Bit string(16)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description apparent clock correction [12] apparent clock correction [12] Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) [12] Mean Motion Difference From Computed Value (semicircles/sec) [12] Mean Anomaly at Reference Time (semi-circles) [12] Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) [12] c Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) [12] Semi-Major Axis (meters) [12] Reference Time Ephemeris [12] [12] Age Of Data Offset [12] Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) [12] Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) [12] Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) [12] Inclination Angle at Reference Time (semi-circles) [12] Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) [12] Argument of Perigee (semicircles) [12] Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles/sec) [12] Rate of Inclination Angle (semi-circles/sec) [12]
1/2
MP
Bit string(16)
MP MP
Bit string(32) Bit string(16)
e Cus
MP MP
Bit string(32 Bit string(16)
(A) toe
1/2
MP MP MP MP MP
Bit string(32 Bit string(16
) )
Fit Interval Flag AODO Cic
Bit string(1) Bit string(5) Bit string(16)
OMEGA0 Cis
MP
Bit string(32)
MP
Bit string(16)
i0 Crc OMEGAdot
MP MP
MP MP
Idot
MP
Bit string(14)
3GPP
Release 6
707
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.92
The IE contains fields needed to model the propagation delays of the GPS signals through the ionosphere.
Information Element/Group name 0 1 2 3 0 1 2 3 Need MP MP MP MP MP MP MP MP Multi Type and Reference Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Semantics description Note 1 Note 1 Note 1 Note 1 Note 2 Note 2 Note 2 Note 2
NOTE 1: The parameters n are the coefficients of a cubic equation representing the amplitude of the vertical delay [12]. NOTE 2: The parameters n are the coefficients of a cubic equation representing the period of the ionospheric model [12].
10.3.7.93
UE positioning GPS measured results

Need MP MP Integer(0.. 3715891199 9999 GPS Time of Week in units of th 1/16 UMTS chips according to [19]. 33209832177664 spare values are needed. Multi Type and Reference Semantics description
Information Element/Group name CHOICE Reference Time >UTRAN reference time >>UE GPS timing of cell frames
>>CHOICE mode >>>FDD >>>>Primary CPICH Info
MP MP Primary CPICH Info 10.3.6.60 Cell parameters id 10.3.6.9 Integer(0..40 95) Identifies the reference cell for the GPS TOW-SFN relationship. Identifies the reference cell for the GPS TOW-SFN relationship. The SFN for which the location is valid. This IE indicates the SFN at which the UE timing of cell frames is captured. GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit).
>>>TDD >>>>cell parameters id
MP
>>Reference SFN
MP
>GPS reference time only >>GPS TOW msec
MP
Integer(0..6. 8 048*10 -1) 1 to <maxSat> Enumerated( 0..63) Integer(0..63 )
Measurement Parameters >Satellite ID
MP MP
>C/No
MP
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. the estimate of the carrier-tonoise ratio of the received signal from the particular satellite used in the measurement. It is given in units of dB-Hz (typical levels will be in the range of 20 50 dB-Hz).
3GPP
Release 6 Information Element/Group name >Doppler Need MP
708 Multi Type and Reference Integer(32768..3276 8) Integer(0..10 22)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Hz, scale factor 0.2.
>Whole GPS Chips
MP
>Fractional GPS Chips
MP
Integer(0..(2 0 -1))
>Multipath Indicator
MP
>Pseudorange RMS Error
MP
Enumerated( NM, low, medium, high) Enumerated( range index 0..range index 63)
Unit in GPS chips. Whole value of the UE GPS code-phase measurement, where increasing binary values of the field signify increasing measured pseudoranges.The UE GPS code-phase measurement is divided into the fields Whole GPS Chips and Fractional GPS Chips. -10 Scale factor 2 Fractional value of the UE GPS code-phase measurement. Note 1.
Note 2.
NOTE 1: The following table gives the mapping of the multipath indicator field.
Value NM Low Medium High Multipath Indication Not measured MP error < 5m 5m < MP error < 43m MP error > 43m
NOTE 2: The following table gives the bitmapping of the Pseudorange RMS Error field.
Range Index 0 1 I 62 63 Mantissa 000 001 X 110 111 Exponent 000 000 Y 111 111 Floating-Point value, xi 0.5 0.5625 0.5 * (1 + x/8) * 2 112 -y
Pseudorange value, P P < 0.5 0.5 <= P < 0.5625 xi-1 <= P < xi 104 <= P < 112 112 <= P
10.3.7.94
UE positioning GPS navigation model
This IE contain information required to manage the transfer of precise navigation data to the GPS-capable UE.
Information Element/Group name Satellite information >SatID Need MP MP Multi 1 to <maxSat> Enumerated( 0..63) Enumerated( NS_NN, Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. NOTE Type and Reference Semantics description
>Satellite Status
MP
3GPP
709 Multi Type and Reference ES_SN, ES_NN, REVD) UE positioning GPS Ephemeris and Clock Correction parameters 10.3.7.91a
>GPS Ephemeris and Clock Correction parameters
CVSatellite status
NOTE:
The UE shall interpret enumerated symbols as follows.

Value NS_NN ES_SN ES_NN REVD Indication New satellite, new Navigation Model Existing satellite, same Navigation Model Existing satellite, new Navigation Model Reserved
Condition Satellite status
Explanation The IE is not needed if the IE "Satellite status" is ES_SN and mandatory present otherwise.
10.3.7.95
This IE contains parameters that describe the real-time status of the GPS constellation.
Information Element/Group name Satellite information >BadSatID Need MP MP Multi 1 to <maxSat> Enumerated( 0..63) Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. Type and Reference Semantics description
10.3.7.95a
Void
10.3.7.96
UE positioning GPS reference time

Need MP MP Multi Type and Reference Integer(0..10 23) Integer(0..6. 8 048*10 -1) Semantics description
Information Element/Group name GPS Week GPS TOW msec
GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit). UTRAN GPS timing of cell frames in steps of 1 chip
UTRAN GPS reference time >UTRAN GPS timing of cell frames >CHOICE mode >>FDD >>>Primary CPICH Info
OP MP
Integer(0.. 2322431999 999)
OP MP Primary CPICH Info 10.3.6.60 Identifies the reference cell for the GPS TOW-SFN relationship
>>TDD
3GPP
Release 6 Information Element/Group name >>>cell parameters id Need MP
710 Multi Type and Reference Cell parameters id 10.3.6.9 Integer(0..40 95) Enumerated (lessThan10, moreThan10 ) Integer (0, 1, 2, 5, 10, 15, 25, 50, -1, 2, -5, -10, 15, -25, -50) 1 to <maxSat> Enumerated( 0..63) Bit string(14) Bit string(2) Boolean Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Identifies the reference cell for the GPS TOW-SFN relationship The SFN which the UTRAN GPS timing of cell frames time stamps. This field indicates the uncertainty of the relation GPS TOW/SFN. lessThan10 means the relation is accurate to at least 10 ms. in 1/256 chips per sec.
>SFN
MP
SFN-TOW Uncertainty
OP
TUTRAN-GPS drift rate
OP
GPS TOW Assist >SatID
OP MP
Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12].
>TLM Message >TLM Reserved >Alert >Anti-Spoof
MP MP MP MP
10.3.7.97
The UTC Model field contains a set of parameters needed to relate GPS time to Universal Time Coordinate (UTC).
Information Element/Group name A1 A0 tot WNt tLS WNLSF DN tLSF Need MP MP MP MP MP MP MP MP Multi Type and Reference Bit string(24) Bit string(32) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Bit string(8) Semantics description sec/sec [12] seconds [12] seconds [12] weeks [12] seconds [12] weeks [12] days [12] seconds [12]
10.3.7.98
UE positioning IPDL parameters
This IE contains parameters for the IPDL mode. The use of this parameters is described in [29].
Information Element/Group name CHOICE mode >FDD >>IP spacing Need Multi Type and Reference Semantics description Version REL-4 REL-4 MP Integer(5,7,1 0,15,20,30,4 0,50) Integer(5,10) Integer(0..9) Integer(0..63 ) Integer(30,4 0,50,70,100) Integer(0..40 See [29]
>>IP length >>IP offset >>Seed >TDD >>IP spacing >>IP_Start
MP MP MP
See [29] See [29] See [29] REL-4 REL-4 REL-4
MP MP
See [33] See [33]
3GPP
Release 6 Information Element/Group name >>IP_Slot >>IP_PCCPCH Burst mode parameters >Burst Start >Burst Length >Burst freq Need
711 Multi Type and Reference 95) Integer(0..14 ) Boolean
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description See [33] See [33] Version
MP CVchannel OP MP MP MP
REL-4 REL-4
Integer(0..15 ) Integer(10..2 5) Integer(1..16 )
See [29] and [33] See [29] and [33] See [29] and [33]
Condition channel
Explanation This IE is present only if the idle slot carries the PCCPCH
10.3.7.99
UE positioning measured results

Need OP Multi Type and reference UE positioning OTDOA measured results 10.3.7.105 UE positioning Position estimate info 10.3.7.109 UE positioning GPS measured results 10.3.7.93 UE positioning error 10.3.7.87 Semantics description
Information Element/Group name UE positioning OTDOA measured results
UE positioning Position estimate info
OP
UE positioning GPS measured results
OP
UE positioning error
OP
Included if UE positioning error occurred
10.3.7.100
Need MP Multi Type and reference UE positioning reporting quantity 10.3.7.111 Measuremen t validity 10.3.7.51 UE positioning reporting criteria 10.3.7.110 Semantics description
Information Element/Group name UE positioning reporting quantity
OP
CHOICE reporting criteria >UE positioning reporting criteria
MP
3GPP
Release 6 Information Element/Group name >Periodical reporting criteria Need
712 Multi Type and reference Periodical reporting criteria 10.3.7.53
>No reporting UE positioning OTDOA assistance data for UE-assisted OP UE positioning OTDOA assistance data for UEassisted 10.3.7.103 UE positioning OTDOA assistance data for UEbased 10.3.7.103a UE positioning GPS assistance data 10.3.7.90
(no data)
UE positioning OTDOA assistance data for UE-based
OP
OP
10.3.7.101
UE positioning measurement event results
This IE contains the measurement event results that are reported to UTRAN for UE positioning measurements.
Information Element/Group name CHOICE Event ID >7a >>UE positioning Position estimate info Need MP MP UE positioning Position estimate info 10.3.7.109 UE positioning OTDOA measured results 10.3.7.105 UE positioning GPS measured results 10.3.7.93 Multi Type and Reference Semantics description One spare value is needed.
>7b >>UE positioning OTDOA measured results
MP
>7c >>UE positioning GPS measurement
MP
10.3.7.102
Void
3GPP
Release 6
713
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.103
UE positioning OTDOA assistance data for UE-assisted

Need OP Multi Type and Reference UE positioning OTDOA reference cell info 10.3.7.108 Semantics description
Information Element/Group name UE positioning OTDOA reference cell info for UEassisted
UE positioning OTDOA neighbour cell list for UEassisted >UE positioning OTDOA neighbour cell info for UEassisted
OP
1 to <maxCellM eas> UE positioning OTDOA neighbour cell info 10.3.7.106
MP
10.3.7.103a UE positioning OTDOA assistance data for UE-based

Information Element/Group name UE positioning OTDOA reference cell info for UE-based Need OP Multi Type and Reference UE positioning OTDOA reference cell info for UE-based 10.3.7.108a Semantics description
UE positioning OTDOA neighbour cell list for UE-based >UE positioning OTDOA neighbour cell info for UE-based
OP
1 to <maxCellM eas> UE positioning OTDOA neighbour cell info for UE-based 10.3.7.106a
MP
10.3.7.104
Void
10.3.7.105
UE positioning OTDOA measured results

Need MP Multi Type and Reference Integer(0..40 95) Semantics description SFN during which the last measurement was performed
Information Element/Group name SFN CHOICE mode >FDD >>Reference cell id
MP
Primary CPICH info 10.3.6.60
>>UE Rx-Tx time difference type 2 info >>>UE Rx-Tx time difference type 2
MP MP UE Rx-Tx time difference
3GPP
714 Multi Type and Reference type 2 10.3.7.84 UE positioning OTDOA quality 10.3.7.107 Cell parameters ID 10.3.6.9 0 to <maxCellM eas>
>>>UE positioning OTDOA quality
MP
Quality of the UE Rx-Tx time difference type 2 measurement from the reference cell. (no data)
>TDD >>Reference cell id
MP
Neighbours
MP
>CHOICE mode >>FDD >>>Neighbour Identity
MP MD Primary CPICH info 10.3.6.60 Frequency info 10.3.6.36 Default value is the same as in the first set of multiple sets. Default value is the existing value of frequency information Included for cell in the active set excluding the reference cell. UE Rx-Tx time difference type 2 10.3.7.84 UE positioning OTDOA quality 10.3.7.107 Cell and Channel Identity info 10.3.6.8a UE positioning OTDOA quality 10.3.7.107 SFN-SFN observed time difference 10.3.7.63
>>>Frequency info
MD
>>>UE Rx-Tx time difference type 2 info >>>>UE Rx-Tx time difference type 2
OP
MP
>>>>UE positioning OTDOA quality
MP
Quality of the UE Rx-Tx time difference type 2 measurement from the neighbour cell.
>>TDD >>>Cell and Channel ID
MD
Default value is the same as in the first set of multiple sets.
>UE positioning OTDOA quality
MP
Quality of the SFN-SFN observed time difference type 2 measurement from the neighbour cell. Gives the timing relative to the reference cell. Only type 2 is allowed.
>SFN-SFN observed time difference type 2
MP
10.3.7.106
UE positioning OTDOA neighbour cell info
This IE gives approximate cell timing in order to decrease the search window.
Information Element/Group name CHOICE mode >FDD >>Primary CPICH info Need MP MP Primary CPICH info 10.3.6.60 Multi Type and Reference Semantics description
>TDD
3GPP
Release 6 Information Element/Group name >>cell and channel ID Need MP
715 Multi Type and Reference Cell and Channel Identity info 10.3.6.8a Frequency info 10.3.6.36 UE positioning IPDL parameters 10.3.7.98 Integer (0 .. 4095)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Identifies the channel to be measured on.
Frequency info
MD
Default value is the existing value of frequency information
IPDL parameters
CV-IPDLs
SFN offset
MP
SFN offset validity
MD
Enumerated (false)
SFN-SFN relative time difference
MP
Integer(0.. 38399)
SFN-SFN drift
OP
Search Window Size
MP
Integer (0, 1, -2, -3, -4, 5, -8, -10, 15, -25, -35, -50, -65, -80, -100, 1, 2, 3, 4, 5, 8, 10, 15, 25, 35, 50, 65, 80, 100) Integer(20, 40, 80, 160, 320, 640, 1280, infinity)
Although this IE is not always required, need is MP to align with ASN.1. Define Tref as the time of beginning of system frame number SFNref of the reference cell. Define Tnc as the beginning of a frame from the neighbour cell occurring immediately after the time Tref. Let the corresponding system frame number be SFNnc. Then SFNnc = SFNref-SFN offset modulo 4096. Absence of this element means SFN offset is valid. False means SFN offset is not valid. Gives the relative timing compared to the reference cell. Equal to (Tnc6 Tref)*(3.84*10 ) where () denotes rounding to the nearest lower integer. In chips, Tnc = the time of beginning of a system frame from the neighbour cell, Tref = the time of beginning of a system frame from the reference cell. in 1/256 chips per second
In chips. If the value is X then the expected SFN-SFN observed time difference is in the range [RTD-X, RTD+X] where RTD is the value of the field SFN-SFN relative time difference. Infinity means that the uncertainty is larger than 1280 chips. (no data)
CHOICE PositioningMode >UE based
MP
3GPP
Release 6 Information Element/Group name >UE assisted Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description (no data)
Condition IPDLs
Explanation This IE is mandatory present if IPDLs are applied and not needed otherwise.
10.3.7.106a UE positioning OTDOA neighbour cell info for UE-based

This IE gives approximate cell timing in order to decrease the search window, as well as the cell locations and fine cell timing for UE based OTDOA.
Information Element/Group name UE positioning OTDOA neighbour cell info Need MP Multi Type and Reference UE positioning OTDOA neighbour cell info 10.3.7.106 Semantics description
Cell Position >Relative North
MD OP Integer(20000..2000 0) Integer(20000..2000 0) Integer(4000..4000) Real(0..0.93 75 in steps of 0.0625) UE positioning OTDOA quality 10.3.7.109a Real(876.00 .. 2923.875) in steps of 0.0625
>Relative East
OP
>Relative Altitude Fine SFN-SFN
OP MP
Default is the same as previous cell Seconds of angle, scale factor 0.03. Relative position compared to reference cell. Seconds of angle, scale factor 0.03. Relative position compared to reference cell. Relative altitude in meters compared to ref. cell. Gives finer resolution
UE positioning Relative Time Difference Quality
MP
Quality of the relative time difference between neighbour and reference cell.
Round Trip Time
OP
In chips. Included if cell is in active set.
10.3.7.107
UE positioning OTDOA quality

Need MP Multi Type and Reference Bit string(2) Semantics description Std Resolution field includes the resolution used in Std of OTDOA Measurements field. Encoding on two bits as follows: '00' 10 meters '01' 20 meters '10' 30 meters '11' Reserved The 'Number of OTDOA measurements' field indicates how many OTDOA measurements have been used in the UE to determine the sample standard deviation
Information Element/Group name Std Resolution
Number of OTDOA Measurements
MP
Bit string(3)
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description of the measurements. Following 3 bit encoding is used: '001' 5-9 '010' 10-14 '011' 15-24 '100' 25-34 '101' 35-44 '110' 45-54 '111' 55 or more
Special case: '000':In this case the field 'Std of OTDOA measurements' contains the std of the reported SFNSFN otd value = E[(x-)2],
where x is the reported value and = E[x] is the expectation value (i.e. the true value) of x. This std can be used irrespective of the number of measurements and reporting of the number of measurements is not needed. Also other measurements such as Ec/No or Rx levels can be utilised in this case to evaluate the 'Std of OTDOA measurements' reported in this IE. Std of OTDOA Measurements field includes sample standard deviation of OTDOA measurements (when number of measurements is reported in 'Number of OTDOA measurements field') or standard deviation of the reported SFN-SFN otd value = 2 E[(x-) ], where x is the reported value and = E[x] is the expectation value (i.e. the true value) of x (when '000' is given in 'Number of OTDOA measurements' field). Following linear 5 bit encoding is used: '00000' 0 - (R*1-1) meters '00001' R*1 (R*2-1) meters '00010' R*2 (R*3-1) meters '11111' R*31 meters or more where R is the resolution defined by Std Resolution field. E.g. R=20 m corresponds to 0-19 m, 20-39 m,,620+ m.
Std of OTDOA Measurements
MP
Bit string(5)
10.3.7.108
UE positioning OTDOA reference cell info
This IE defines the cell used for time references in all OTDOA measurements.
Information Element/Group name Need Multi Type and Reference Semantics description
3GPP
Release 6 Information Element/Group name SFN Need OP
718 Multi Type and Reference Integer (0..4095)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Time stamp (SFN of Reference Cell) of the SFNSFN relative time differences and SFN-SFN drift rates. Included if any SFN-SFN drift value is included in IE UE positioning OTDOA neighbour cell info.
MP MP Primary CPICH info 10.3.6.60 Cell and Channel Identity info 10.3.6.8a Frequency info 10.3.6.36 Identifies the channel to be measured on.
>TDD >>cell and channel ID
MP
Frequency info
MD
Default value is the existing value of frequency information. This IE shall always be set to default value
CHOICE PositioningMode >UE based >UE assisted IPDL parameters
MP (no data) If this element is not included there are no idle periods present
OP
UE positioning IPDL parameters 10.3.7.98
10.3.7.108a UE positioning OTDOA reference cell info for UE-based

This IE defines the cell used for time references in all OTDOA measurements for UE-based methods.
Information Element/Group name UE positioning OTDOA reference cell info Need MP Multi Type and Reference UE positioning OTDOA reference cell info 10.3.7.108 Semantics description
CHOICE Cell Position
OP
The position of the antenna that defines the cell. Used for the UE based method. Ellipsoid point 10.3.8.4a Ellipsoid point with altitude 10.3.8.4b Real(876.00 .. 2923.875) in steps of 0.0625
>Ellipsoid >>Ellipsoid point
MP
>Ellipsoid with altitude >>Ellipsoid point with altitude
MP
Round Trip Time
OP
In chips.
3GPP
Release 6
719
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.109
UE positioning position estimate info
The purpose of this IE is to provide the position estimate from the UE to the network, if the UE is capable of determining its own position.
Information Element/Group name CHOICE Reference Time >UTRAN GPS reference time >>UE GPS timing of cell frames Need MP MP Integer(0.. 3715891199 9999) GPS Time of Week in units of th 1/16 UMTS chips according to [19]. 33209832177664 spare values are needed. Multi Type and Reference Semantics description
>>CHOICE mode >>>FDD >>>>Primary CPICH Info
MP MP Primary CPICH Info 10.3.6.60 Cell parameters id 10.3.6.9 Integer(0..40 95) Identifies the reference cell for the GPS TOW-SFN relationship Identifies the reference cell for the GPS TOW-SFN relationship. The SFN for which the location is valid. This IE indicates the SFN at which the UE timing of cell frame is captured. GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit). SFN during which the position was calculated.
>>>TDD >>cell parameters id
MP
>>Reference SFN
MP
>GPS reference time only >>GPS TOW msec
MP
Integer(0..6. 8 048*10 -1)
>Cell timing >>SFN >>CHOICE mode >>>FDD >>>>Primary CPICH Info
MP MP MP
Integer(0..40 95)
Primary CPICH Info 10.3.6.60 Cell parameters id 10.3.6.9 Ellipsoid Point; 10.3.8.4a Ellipsoid point with uncertainty circle 10.3.8.4d Ellipsoid point with uncertainty ellipse 10.3.8.4e Ellipsoid point with altitude 10.3.8.4b Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c
Identifies the reference cell for SFN
>>>TDD >>cell parameters id
MP
Identifies reference cell for SFN
CHOICE Position estimate >Ellipsoid Point
MP
>Ellipsoid point with uncertainty circle
>Ellipsoid point with uncertainty ellipse
>Ellipsoid point with altitude
>Ellipsoid point with altitude and uncertainty ellipsoid
3GPP
Release 6
720
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.7.109a UE positioning Relative Time Difference quality

Information Element/Group name Relative Time Difference Std Resolution Need MP Multi Type and Reference Bit string(2) Semantics description Std Resolution field includes the resolution used in Std of Relative Time Difference field. Encoding on two bits as follows: '00' 10 meters '01' 20 meters '10' 30 meters '11' Reserved Std of Relative Time difference field includes standard deviation of (SFN-SFN relative time difference + Fine SFNSFN). Following linear 5 bit encoding is used: '00000' 0 - (R*1-1) meters '00001' R*1 (R*2-1) meters '00010' R*2 (R*3-1) meters '11111' R*31 meters or more where R is the resolution defined by Std Resolution field. E.g. R=20 m corresponds to 0-19 m, 20-39 m,,620+ m.
Std of Relative Time Difference
MP
Bit string(5)
10.3.7.110
UE positioning reporting criteria
The triggering of the event-triggered reporting for a UE positioning measurement.
3GPP
Release 6 Information Element/Group name Parameters required for each event >Amount of reporting Need OP
721 Multi 1 to <maxMeas Event> Integer(1, 2, 4, 8, 16, 32, 64,infinite) Boolean Type and Reference
MP
>Report first fix
MP
>Measurement interval
MP
Integer(5,15, 60,300,900,1 800,3600,72 00)
If true the UE reports the position once the measurement control is received, and then each time an event is triggered. Indicates how often the UE should make the measurement In seconds
>CHOICE Event ID >>7a >>>Threshold Position Change
MP MP Integer(10,2 0,30,40,50,1 00,200,300,5 00,1000,200 0,5000,1000 0,20000,500 00,100000) Real(0.25,0. 5,1,2,3,4,5,1 0,20,50,100, 200,500,100 0,2000,5000 ) Integer(1,2,3 ,5,10,20,50,1 00) Meters. Indicated how much the position should change compared to last reported position fix in order to trigger the event.
>>7b >>>Threshold SFN-SFN change
MP
Chips. Indicates how much the SFN-SFN measurement of ANY measured cell is allowed to change before the event is triggered.
>>7c >>>Threshold SFN-GPS TOW
MP
Time in ms. When the GPS TOW and SFN timer has drifted apart more than the specified value the event is triggered.
10.3.7.111
UE positioning reporting quantity
The purpose of the element is to express the allowed/required location method(s), and to provide information desired QoS.
Information Element/Group name Method Type Need MP Multi Type and Reference Enumerated( UE assisted, UE based, UE based is preferred but UE assisted is allowed, UE assisted is preferred but UE based is allowed) Enumerated( OTDOA, GPS, OTDOA or GPS, Cell ID) Integer(1,2,4 Semantics description
Positioning Methods
MP
Response Time
MP
This IE shall be ignored.
3GPP
722 Multi Type and Reference , 8, 16, 32, 64, 128) Bit string(7)
Horizontal Accuracy
Vertical Accuracy
GPS timing of Cell wanted
CVMethodTyp e CVMethodTyp e MP
Bit string(7)
Boolean
Multiple Sets Additional Assistance Data Request
MP MP
Boolean Boolean
Environment Characterisation
OP
Enumerated( possibly heavy multipath and NLOS conditions, no or light multipath and usually LOS conditions, not defined or mixed environment)
The uncertainty is derived from the "uncertainty code" k by k r = 10*(1.1 -1) in meters. The uncertainty is derived from the "uncertainty code" k by k r = 45*(1.025 -1) in meters. If true the SRNC wants the UE to report the SFN-GPS timing of the reference cell. This is however optional in the UE. This IE shall be ignored. TRUE indicates that the UE is requested to send the IE "Additional assistance Data Request" when the IE "UE positioning Error" is present in the UE positioning measured results. FALSE indicates that the UE shall use the assistance data available. One spare value is needed.
Condition Method Type
Explanation The IE is optional if the IE "Method Type" is "UE assisted"; otherwise it is mandatory present.
10.3.7.112
NOTE:
TADV info
TADV indicates the difference between the Rx timing and Tx timing of a UE.
Information Element/group name TADV SFN Need MP MP Multi Type and reference Integer (0..2047) Integer(0..40 95) Semantics description As defined in [20]. SFN during which the TADV measurement was performed. Version REL-4 REL-4
3GPP
Release 6
723
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8
10.3.8.1
Other Information elements

BCCH modification info
Indicates modification of the System Information on BCCH.

Information Element/Group name MIB Value tag BCCH modification time Need MP OP Multi Type and reference MIB Value tag 10.3.8.9 Integer (0.. 4088 in step of 8) Semantics description
All SFN values in which MIB may be mapped are allowed.
10.3.8.2
BSIC
Need MP MP bit string(3) Multi Type and reference Semantics description [11] The first/leftmost bit of the bit string contains the most significant bit of the NCC. The first/leftmost bit of the bit string contains the most significant bit of the BCC.
Information Element/Group name Base transceiver Station Identity Code (BSIC) >Network Colour Code (NCC)
>Base Station Colour Code (BCC)
MP
bit string(3)
10.3.8.3
This information element contains the CBS discontinuous reception information to be broadcast for CBS DRX Level 1 calculations in the UE.
Information Element/Group name Period of CTCH allocation (N) CBS frame offset (K) Period of BMC scheduling messages (P) Need MP MP CV-SIB5 Multi Type and reference Integer (1..256) Integer (0..255) Integer (8, 16, 32, 64, 128, 256) Semantics description MTTI N 256, N multiple of MTTI 0 K N-1, K multiple of MTTI Version
REL-6
Condition SIB5
Explanation The IE is optional when the IE "CBS DRX Level 1 information" in SIB5, otherwise the IE is not needed
10.3.8.4
Cell Value tag

Need MP Multi Type and reference Integer (1..4) Semantics description
Information Element/Group name Cell Value tag
3GPP
Release 6
724
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8.4a
Ellipsoid point
This IE contains the description of an ellipsoid point as in [24].

Information Element/Group name Latitude sign Need MP Multi Type and Reference Enumerated (North, South) Integer (0...2 -1)
23
Degrees Of Latitude
MP
The IE value (N) is derived by this formula: N2 X /90 < N+1 X being the latitude in degree (0 90 .. ) The IE value (N) is derived by this formula: N2 X /360 < N+1 X being the longitude in degree (-180 ..+180 )
24 23
Degrees Of Longitude
MP
Integer (2 ...2 -1)

23 23
10.3.8.4b
Ellipsoid point with Altitude
This IE contains the description of an ellipsoid point with altitude as in [24].

23
Degrees Of Latitude
MP
The IE value (N) is derived by this formula: N2 X /90 < N+1 X being the latitude in degree (0 90 .. ) The IE value (N) is derived by this formula: N2 X /360 < N+1 X being the longitude in degree (-180 ..+180 )
24 23
MP
Integer (2 ...2 -1)

23 23
Altitude Direction
MP
Altitude
MP
Enumerated (Height, Depth) Integer (0..2 -1)

15
The IE value (N) is derived by this formula: Na < N+1 a being the altitude in metres
10.3.8.4c
Ellipsoid point with Altitude and uncertainty ellipsoid
This IE contains the description of an ellipsoid point with altitude and uncertainty ellipsoid as in [24].
23
Degrees Of Latitude
MP
The IE value (N) is derived by this formula: N2 X /90 < N+1 X being the latitude in degree (0 90 .. )
23
3GPP
Release 6 Information Element/Group name Degrees Of Longitude Need MP
725 Multi Type and Reference Integer (2 ...2 -1)

23 23
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The IE value (N) is derived by this formula: N2 X /360 < N+1 X being the longitude in degree (-180 ..+180 )
24
Altitude Direction
MP
Altitude
MP
Enumerated (Height, Depth) Integer (0..2 -1)

15
Uncertainty semi-major
MP
Integer (0...127)
The IE value (N) is derived by this formula: Na < N+1 a being the altitude in metres The uncertainty r is derived from the "uncertainty code" k by r = 10x(1.1 -1) The uncertainty r is derived from the "uncertainty code" k by r = 10x(1.1 -1) The IE value (N) is derived by this formula: 2N a < 2(N+1) a being the orientation in degree (0 179 .. ) The uncertainty in altitude, h, expressed in metres is mapped from the IE value (K), with the following formula:
k k
Uncertainty semi-minor
MP
Integer (0...127)
Orientation of major axis
MP
Integer (0..89)
Uncertainty Altitude
MP
Integer(0..12 7)
h = C (1 + x )K 1
Confidence
MP
Integer (0..100)
with C = 45 and x = 0.025. in percentage
10.3.8.4d
Ellipsoid point with uncertainty Circle
This IE contains the description of an ellipsoid point with an uncertainty circle as in [24].
23
Degrees Of Latitude
MP
The IE value (N) is derived by this formula: N2 X /90 < N+1 X being the latitude in degree (0 90 .. ) The IE value (N) is derived by this formula: N2 X /360 < N+1 X being the longitude in degree (-180 ..+180 ) The uncertainty r is derived from the "uncertainty code" k by r = 10x(1.1 -1)
k 24 23
MP
Integer (2 ...2 -1)

23 23
Uncertainty Code
MP
Integer (0...127)
3GPP
Release 6
726
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8.4e
Ellipsoid point with uncertainty Ellipse
This IE contains the description of an ellipsoid point with an uncertainty ellipse as in [24].
23
Degrees Of Latitude
MP
The IE value (N) is derived by this formula: N2 X /90 < N+1 X being the latitude in degree (0 90 .. ) The IE value (N) is derived by this formula: N2 X /360 < N+1 X being the longitude in degree (-180 ..+180 ) The uncertainty r is derived from the "uncertainty code" k by r = 10x(1.1 -1) The uncertainty r is derived from the "uncertainty code" k by r = 10x(1.1 -1) The IE value (N) is derived by this formula: 2N a < 2(N+1) a being the orientation in degree (0 179 .. ) in percentage
k k 24 23
MP
Integer (2 ...2 -1)

23 23
Uncertainty semi-major
MP
Integer (0...127)
Uncertainty semi-minor
MP
Integer (0...127)
Orientation of major axis
MP
Integer (0..89)
Confidence
MP
Integer (0..100)
10.3.8.4f
GERAN system information

Information Element/Group name >>> GERAN System Info >>>> GERAN system info block
MP
1 to <maxGERAN SI> Octet string(1..23) The first octet contains octet 1 of the GERAN system information block, the second octet contains octet 2 of the GERAN system information block and so on.
REL-5
MP
REL-5
10.3.8.4g
GSM Target Cell Info

Information Element/Group name GSM Target Cell Info List >BCCH ARFCN >Band indicator
MP
1 to <maxGSMTar getCells> Integer (0..1023) Enumerated [45] Indicates how to
REL-6
MP MP
REL-6 REL-6
3GPP
727 Type and reference (DCS 1800 band used, PCS 1900 band used) BSIC 10.3.8.2
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description interpret the BCCH ARFCN REL-6 Version
>BSIC
OP
10.3.8.5
Inter-RAT change failure

Need MP Multi Type and reference Enumerated( Configuratio n unacceptabl e, physical channel failure, protocol error, unspecified) Protocol error information 10.3.8.12 Semantics description Four spare values are needed.
Information Element/Group name Inter-RAT change failure cause
CV-ProtErr
Condition ProtErr
Explanation The IE is mandatory present if the IE "Inter-RAT change failure cause" has the value "Protocol error" and not needed otherwise.
10.3.8.6
Inter-RAT handover failure

Need MD Multi Type and reference Enumerated( Configuratio n unacceptabl e, physical channel failure, protocol error, inter-RAT protocol error, unspecified) Protocol error information 10.3.8.12 Semantics description Default value is "unspecified". Eleven spare values are needed.
Information Element/Group name Inter-RAT handover failure cause
CV-ProtErr
Condition ProtErr
Explanation The IE is mandatory present if the IE "Inter-RAT handover failure cause" has the value "Protocol error" and not needed otherwise.
3GPP
Release 6
728
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8.7
Inter-RAT UE radio access capability
This Information Element contains the inter-RAT UE radio access capability that is structured and coded according to the specification used for the corresponding system type.
Information Element/Group name CHOICE system >GSM >>Mobile Station Classmark 2 Need MP MP Octet string (5) This IE is formatted as 'TLV' and is coded in the same way as the Mobile Station Classmark 2 information element in [5]. The first octet is the Mobile station classmark 2 IEI and its value shall be set to 33H(except in the case of NOTE 2). The second octet is the Length of mobile station classmark 2 and its value shall be set to 3. The octet 3 contains the first octet of the value part of the Mobile Station Classmark 2 information element, the octet 4 contains the second octet of the value part of the Mobile Station Classmark 2 information element and so on. For each of these octets, the first/ leftmost/ most significant bit of the octet contains b8 of the corresponding octet of the Mobile Station Classmark 2. See NOTE 2 This IE is formatted as 'V' and is coded in the same way as the value part in the Mobile station classmark 3 information element in [5]. The first octet contains octet 1 of the value part of Mobile station classmark 3, the second octet contains octet 2 of the value part of Mobile station classmark 3 and so on. See NOTE 1, NOTE 2. This IE is formatted as 'V' and is coded in the same way as the value part in the MS Radio Access Capability information element in [5]. Formatted and coded according to [53]. The first/leftmost/most significant bit of the bit string contains bit 8 of the first octet of the IE. Multi Type and reference Semantics description Version
>>Mobile Station Classmark 3
MP
Octet string (1..32)
>>MS Radio Access Capability
OP
Octet string (1..64)
REL-6
>GERAN Iu >>MS GERAN Iu mode Radio Access Capability
MP
Bit string (1..170)
REL-5 REL-5
>cdma2000 >>cdma2000Message
MP
1.to.<ma xInterSy sMessa ges> Bit string (8) Formatted and coded according to cdma2000 specifications. The first/leftmost/most significant bit of the bit string contains bit 7 of the MSG_TYPE. Formatted and coded according to cdma2000 specifications. The first/leftmost/most significant bit of the bit string contains bit 7 of the first octet of the cdma2000 message.
>>>MSG_TYPE(s)
MP
MP
Bit string (1..512)
3GPP
Release 6
729
3GPP TS 25.331 V6.23.0 (2009-09)
Information Need Multi Type and Semantics description Version Element/Group name reference NOTE 1: The value part is specified by means of CSN.1, which encoding results in a bit string, to which final padding may be appended upto the next octet boundary [5]. The first/ leftmost bit of the CSN.1 bit string is placed in the first/ leftmost/ most significant bit of the first octet. This continues until the last bit of the CSN.1 bit string, which is placed in the last/ rightmost/ least significant bit of the last octet. NOTE 2: The information in these IEs is optionally present in the INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES message, otherwise it is mandatory present. If the information in the IEs "Mobile Station Classmark 2" and "Mobile Station Classmark 3" is not included, it is indicated by setting the first octet (IEI) of the IE "Mobile Station Classmark 2" to 00H. In this case, the receiver should ignore the value parts of the Mobile Station Classmark 2 and the Mobile Station Classmark 3. The contents of those are set to zero.
10.3.8.8
Void
10.3.8.8a
Inter-RAT UE security capability

Need MP MP The value TRUE means that the indicated ciphering algorithm is supported. Boolean Boolean Boolean Boolean Boolean Boolean Boolean Multi Type and reference Semantics description Version
Information Element/Group name CHOICE system >GSM >>GSM security capability
>>>A5/7 supported >>>A5/6 supported >>>A5/5 supported >>>A5/4 supported >>>A5/3 supported >>>A5/2 supported >>>A5/1 supported
MP MP MP MP MP MP MP
10.3.8.9
MIB Value tag

Information Element/Group name MIB Value tag
10.3.8.10
PLMN Value tag

Information Element/Group name PLMN Value tag
10.3.8.10a
PNBSCH allocation
UTRAN may use this IE to provide silent periods in the cell that may be used for cell synchronisation purposes.
3GPP
Release 6 Information Element/Group name Number of repetitions per SFN period Need MP
730 Multi Type and reference Integer(2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 18, 20, 24, 28, 32, 36, 40, 48, 56, 64, 72, 80)
10.3.8.11
Predefined configuration identity and value tag

Need MP Multi Type and reference Predefined configuration identity 10.3.4.5 Predefined configuration value tag 10.3.4.6 Semantics description
Information Element/Group name Predefined configuration identity
Predefined configuration value tag
MP
10.3.8.12
This information element contains diagnostics information returned by the receiver of a message that was not completely understood.
Information Element/Group name CHOICE diagnostics type >Protocol error cause Need MP Protocol error cause 10.3.3.26 Multi Type and reference Semantics description One spare value is needed.
10.3.8.13
References to other system information blocks

Need MP Multi 1 to <maxSIB> Type and reference Semantics description System information blocks for which multiple occurrences are used, may appear more than once in this list Version
Information element/Group name References to other system information blocks
>Scheduling information
MP
>SIB type SIBs only
MP
Scheduling information, 10.3.8.16 SIB Type SIBs only, 10.3.8.22 1 to <maxSIB> Scheduling information, 10.3.8.16 SIB type extension 10.3.8.18b REL-6 REL-6
References to other extension system information blocks >Scheduling information
OP MP
>Extension SIB type
MP
REL-6
3GPP
Release 6
731
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.8.14
References to other system information blocks and scheduling blocks

Need MP Multi 1 to <maxSIB> Type and reference Semantics description System information blocks for which multiple occurrences are used, may appear more than once in this list Version
Information element/Group name References to other system information blocks
>Scheduling information
MP
>SIB and SB type
MP
Scheduling information, 10.3.8.16 SIB and SB Type, 10.3.8.18a 1 to <maxSIB> Scheduling information, 10.3.8.16 SIB type extension 10.3.8.18b REL-6 REL-6
References to other extension system information blocks >Scheduling information
OP MP
>Extension SIB type
MP
REL-6
10.3.8.15
Rplmn information
Contains information to provide faster RPLMN selection in the UE.

Information Element/Group name GSM BA Range Need OP Multi 1 to maxNumG SMFreqRa nges Integer(0..16 383) Integer(0..16 383) 1 to maxNumF DDFreqs Integer(0..16 383) Integer(0..16 383) [21] [21] This IE is only needed when the FDD frequency list is specifying a range. Type and reference Semantics description GSM BA Range Version
>GSM Lower Range (UARFCN)
MP
>GSM Upper Range (UARFCN)
MP
Lower bound for range of GSM BA freqs Upper bound for range of GSM BA freqs
FDD UMTS Frequency list
OP
>UARFCN (Nlow) >UARFCN (Nupper)
MP OP
3.84 Mcps TDD UMTS Frequency list >UARFCN 1.28 Mcps TDD UMTS Frequency list >UARFCN CDMA2000 UMTS Frequency list
OP
1 to maxNumT DDFreqs Integer(0..16 383) 1 to maxNumT DDFreqs Integer(0..16 383) 1 to maxNumC DMA200Fr [22] [22] REL-4
MP OP
MP OP
REL-4
3GPP
Release 6 Information Element/Group name >BAND_CLASS Need
732 Multi eqs MP Bit string(5 bits) Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TIA/EIA/IS-2000 When mapping the BAND_CLASS to the bit string, the first/leftmost bit of the bit string contains the most significant bit.. TIA/EIA/IS-2000 When mapping the CDMA_FREQ to the bit string, the first/leftmost bit of the bit string contains the most significant bit.. Version
>CDMA_FREQ
MP
Bit string (11 bits)
10.3.8.16
Scheduling information
Need OP PLMN Value tag 10.3.8.10 This IE is included if the following conditions are fulfilled: the SIB type equals system information block type 1 This IE is included if the following conditions are fulfilled: the SIB type equals system information block type 16 This IE is included if the following conditions are fulfilled: the area scope for the system information block is set to "cell" in table 8.1.1. a value tag is used to indicate changes in the system information block. This IE is included if the following conditions are fulfilled: the SIB type equals system information block types 15.2 and 15.3 Default value is 1 Multi Type and reference Semantics description
Information Element/Group name CHOICE Value tag >PLMN Value tag
>Predefined configuration identity and value tag
>Cell Value tag
Predefined configuration identity and value tag 10.3.8.11 Cell Value tag 10.3.8.4
>SIB occurrence identity and value tag
SIB occurrence identity and value tag 10.3.8.20b MP MD
Scheduling >SEG_COUNT
>SIB_REP
MP
>SIB_POS
MP
SEG COUNT 10.3.8.17 Integer (4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096) Integer (0 ..Rep-2 by step of 2) 1..15 Integer(2..32 by step of 2)
Repetition period for the SIB in frames
>SIB_POS offset info >>SIB_OFF
MD MP
Position of the first segment Rep is the value of the SIB_REP IE see below for default value Offset of subsequent segments
3GPP
Release 6
733
3GPP TS 25.331 V6.23.0 (2009-09)
Field SIB_POS offset info
Default value The default value is that all segments are consecutive, i.e., that the SIB_OFF = 2 for all segments except when MIB segment/complete MIB is scheduled to be transmitted in between segments from same SIB. In that case, SIB_OFF=4 in between segments which are scheduled to be transmitted at SFNprime = 8 *n-2 and 8*n + 2, and SIB_OFF=2 for the rest of the segments.
10.3.8.17
SEG COUNT
Need MP Multi Type and reference Integer (1..16) Semantics description Number of segments in the system information block
Information Element/Group name SEG_COUNT
10.3.8.18
Segment index
Each system information segment has an individual segment index.

Information Element/Group name Segment index Need MP Multi Type and reference Integer (1..15) Semantics description Segments of a system information block are numbered starting with 0 for the first segment and 1 for the next segment, which can be the first subsequent segment or a last segment.
10.3.8.18a
SIB and SB type
The SIB type identifies a specific system information block.

Information Element/Group name SIB and SB type Need MP Multi Type and reference Enumerated, see below Semantics description Two spare values are needed
3GPP
Release 6 List of enumerated values System Information Type 1, System Information Type 2, System Information Type 3, System Information Type 4, System Information Type 5, System Information Type 6, System Information Type 7, System Information Type 11, System Information Type 12, System Information Type 13, System Information Type 13.1, System Information Type 13.2, System Information Type 13.3, System Information Type 13.4, System Information Type 14, System Information Type 15, System Information Type 15.1, System Information Type 15.2, System Information Type 15.3, System Information Type 15.4, System Information Type 15.5, System Information Type 16, System Information Type 17, System Information Type 18, Scheduling Block 1, Scheduling Block 2, System Information Type 5bis Version
734
3GPP TS 25.331 V6.23.0 (2009-09)
REL-6
10.3.8.18b
SIB type extension
The SIB type identifies a specific extension system information block.

Information Element/Group name SIB type extension Need MP Multi Type and reference Enumerated, see below Semantics description Seven spare values are needed
List of enumerated values System Information Type 11bis
Version REL-6
10.3.8.19
SIB data fixed
Contains the result of a master information block or a system information block after encoding and segmentation. The IE is used for segments with fixed length (segments filling an entire transport block).
Information Element/Group name SIB data fixed Need MP Multi Type and reference Bit string ( 222) Semantics description The first bit contains the first bit of the segment.
10.3.8.20
SIB data variable
Contains either a complete system information block or a segment of a system information block. Contains the result of a master information block or a system information block after encoding and segmentation. The IE is used for segments with variable length. The system information blocks are defined in clauses10.2.48.8.1 to10.2.48.8.18.
3GPP
Release 6 Information Element/Group name SIB data variable Need MP
735 Multi Type and reference Bit string ( 1..214)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The first bit contains the first bit of the segment.
10.3.8.20a
SIB occurrence identity
This information element identifies a SIB occurrence for System Information Block types 15.2 and 15.3. For System Information Block type 15.2, this identity is assigned to the visible satellite only. Unused identities are claimed by newly rising satellites.
Information Element/Group name SIB occurrence identity Need MP Multi Type and reference Integer (0..15) Semantics description
10.3.8.20b
SIB occurrence identity and value tag

Need MP Multi Type and reference SIB occurrence identity 10.3.8.20a SIB occurrence value tag 10.3.8.20c Semantics description
Information Element/Group name SIB occurrence identity
SIB occurrence value tag
MP
10.3.8.20c
SIB occurrence value tag
This information element is used to identify different versions of SIB occurrence for System Information Block types 15.2 and 15.3.
Information Element/Group name SIB occurrence value tag Need MP Multi Type and Reference Integer(0..15 ) Semantics description
10.3.8.21
SIB type

Information Element/Group name SIB type Need MP Multi Type and reference Enumerated, see below Semantics description No spare value is needed
3GPP
Release 6 List of enumerated values Master information block, System Information Type 1, System Information Type 2, System Information Type 3, System Information Type 4, System Information Type 5, System Information Type 6, System Information Type 7, System Information Type 11, System Information Type 12, System Information Type 13, System Information Type 13.1, System Information Type 13.2, System Information Type 13.3, System Information Type 13.4, System Information Type 14, System Information Type 15, System Information Type 15.1, System Information Type 15.2, System Information Type 15.3, System Information Type 15.4, System Information Type 15.5, System Information Type 16, System Information Type 17, System Information Type 18, Scheduling Block 1, Scheduling Block 2, System Information Type 5bis, Extension Type Version
736
3GPP TS 25.331 V6.23.0 (2009-09)
REL-6
10.3.8.22
SIB type SIBs only

Information Element/Group name SIB type SIBs only Need MP Multi Type and reference Enumerated, see below Semantics description Four spare values are needed
3GPP
Release 6 List of enumerated values System Information Type 1, System Information Type 2, System Information Type 3, System Information Type 4, System Information Type 5, System Information Type 6, System Information Type 7, System Information Type 11, System Information Type 12, System Information Type 13, System Information Type 13.1, System Information Type 13.2, System Information Type 13.3, System Information Type 13.4, System Information Type 14, System Information Type 15, System Information Type 15.1, System Information Type 15.2, System Information Type 15.3, System Information Type 15.4, System Information Type 15.5, System Information Type 16, System Information Type 17, System Information Type 18, System Information Type 5bis Version
737
3GPP TS 25.331 V6.23.0 (2009-09)
REL-6
10.3.9
10.3.9.1
ANSI-41 Information elements

ANSI-41 Core Network Information
Need MP MP MP MP Multi Type and reference P_REV 10.3.9.10 MIN_P_REV 10.3.9.8 SID 10.3.9.11 NID 10.3.9.9 Semantics description
Information element/Group name P_REV MIN_P_REV SID NID
10.3.9.2
ANSI-41 Global Service Redirection information
This Information Element contains ANSI-41 Global Service Redirection information.

Information Element/Group name ANSI-41 Global Service Redirection information Need MP Multi Type and reference ANSI-41 NAS parameter, 10.3.9.3 Semantics description Formatted and coded according to the 3GPP2 document "G3G CDMA DS on ANSI-41"
10.3.9.3
ANSI-41 NAS parameter
This Information Element contains ANSI-41 User Zone Identification information.
3GPP
Release 6 Information Element/Group name ANSI-41 NAS parameter Need MP
738 Multi Type and reference Bit string (size (1..2048))
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The first bit contains the first bit of the ANSI-41 information.
10.3.9.4
ANSI-41 NAS system information
This Information Element contains ANSI-41 system information.

Information Element/Group name NAS (ANSI-41) system information Need MP Multi Type and reference ANSI-41 NAS parameter, 10.3.9.3 Semantics description Formatted and coded according to the 3GPP2 document "G3G CDMA DS on ANSI-41"
10.3.9.5
ANSI-41 Private Neighbour List information
This Information Element contains ANSI-41 Private Neighbour List information.

Information Element/Group name ANSI-41 Private Neighbour List information Need MP Multi Type and reference ANSI-41 NAS parameter, 10.3.9.3 Semantics description Formatted and coded according to the 3GPP2 document "G3G CDMA DS on ANSI-41"
10.3.9.6
ANSI-41 RAND information
This Information Element contains ANSI-41 RAND information.

Information Element/Group name ANSI-41 RAND information Need MP Multi Type and reference ANSI-41 NAS parameter, 10.3.9.3 Semantics description Formatted and coded according to the 3GPP2 document "G3G CDMA DS on ANSI-41"
10.3.9.7
ANSI-41 User Zone Identification information
This Information Element contains ANSI-41 User Zone Identification information.

Information Element/Group name ANSI-41 User Zone Identification information Need MP Multi Type and reference ANSI-41 NAS parameter, 10.3.9.3 Semantics description Formatted and coded according to the 3GPP2 document "G3G CDMA DS on ANSI-41"
10.3.9.8
MIN_P_REV
This Information Element contains minimum protocol revision level.
3GPP
Release 6 Information Element/Group name MIN_P_REV Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Minimum protocol revision level. The first/leftmost bit of the bit string contains the most significant bit of the MIN_P_REV.
10.3.9.9
NID
This Information Element contains Network identification.

Information Element/Group name NID Need MP Multi Type and reference Bit string (16) Semantics description Network identification. The first/leftmost bit of the bit string contains the most significant bit of the NID.
10.3.9.10
P_REV
This Information Element contains protocol revision level.

Information Element/Group name P_REV Need MP Multi Type and reference Bit string (8) Semantics description Protocol revision level. The first/leftmost bit of the bit string contains the most significant bit of the P_REV.
10.3.9.11
SID
This Information Element contains System identification.

Information Element/Group name SID Need MP Multi Type and reference Bit string (15) Semantics description System identification. The first/leftmost bit of the bit string contains the most significant bit of the SID.
10.3.9a MBMS Information elements

10.3.9a.1 MBMS Common CCTrCH identity
Identifies a Coded Composite Transport channel configuration included within the MBMS COMMON P-T-M RB INFORMATION message.
Information element/Group name MBMS Common CCTrCh identity Need MP Multi Type and reference Integer (1..32) Semantics description Version REL-6
3GPP
Release 6
740
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.2
MBMS Common PhyCh identity
Identifies a physical channel configuration included within the MBMS COMMON P-T-M RB INFORMATION message.
Information element/Group name MBMS Common PhyCh identity Need MP Multi Type and reference Integer (1..32) Semantics description Version REL-6
10.3.9a.3
MBMS Common RB identity
Identifies a radio bearer channel configuration included within the MBMS COMMON P-T-M RB INFORMATION message.
Information element/Group name MBMS Common RB identity Need MP Multi Type and reference Integer (1..32) Semantics description Version REL-6
10.3.9a.4
MBMS Common TrCh identity
Identifies a transport channel configuration included within the MBMS COMMON P-T-M RB INFORMATION message.
Information element/Group name MBMS Common TrCh identity Need MP Multi Type and reference Integer (1..32) Semantics description Version REL-6
10.3.9a.5
MBMS Current cell S-CCPCH identity
Identifies one of the current cell's Secondary CCPCH's.

Information element/Group name MBMS Current cell SCCPCH identity Need MP Multi Type and reference Integer (1..maxSC CPCH) Semantics description Version REL-6
10.3.9a.6
Void
3GPP
Release 6
741
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.7
MBMS L1 combining schedule
Includes information about the MBMS L1 combining schedule.

Information element/Group name MBMS L1 combining cycle length Need MP Multi Type and reference Enumerate d (32, 64, 128, 256, 512, 1024) Integer (0.. MBMS L1 combining cycle length - 4) by step of 4 Semantics description In number of radio frames Version REL-6
MBMS L1 combining cycle offset
MD
MTCH L1- combining period list
MP
1 to < maxMB MSL1CP> Integer (0.. MBMS L1 combining cycle length - 4) by step of 4 Integer (4.. MBMS L1 combining cycle length) by step of 4
Start of the L1 combining cycle (relative to the timing of the current cell) in number of radio frames. Default value is no offset One or more periods in which L1 combining is performed Number of frames from the end of the previous combining period or the start of the cycle (for the first period)
REL-6
REL-6
>Start
MP
REL-6
>Duration
MP
Number of frames (see note)
REL-6
NOTE:
The MTCH L1- combining period should indicate one or more complete TTIs.
10.3.9a.7o
Information Need Multi Type and Semantics description Version Element/Group name reference MBMS p-t-m activation MP Integer The 11 LSB of the SFN. Note 1 REL-6 time (0..2047) and 2. Note 1: The MBMS p-t-m activation time indicates the start of the 10 ms frame corresponding to the indicated SFN value and of the primary CCPCH of the cell where this IE is transmitted. Note 2: The range of the MBMS p-t-m activation time is from 10 ms after the beginning of the MCCH modification period wherein it is transmitted and to the end of next following MCCH modification period. The UE shall consider a value out of this range as expired.
3GPP
Release 6
742
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.7a
MBMS p-t-m RB information
Includes information about an MBMS p-t-m radio bearers mapped on a TrCH.

Information element/Group name RB information Need CV-Curr Multi Type and reference MBMS Common RB identity 10.3.9a.3 MBMS Short transmissi on identity 10.3.9a.1 0 Integer (1..15) Semantics description Version REL-6
MBMS short transmission ID
MP
REL-6
MBMS logical channel identity
MP
L1 combining status
CVNeigh
Boolean
This identifier is used to distinguish different MTCH mapped on to a TrCh (MBMS-Id within the MAC header[15]) The IE is only applicable in case of partial L1 comining, in which case value TRUE means that L1 combining is used for this radio bearer
REL-6
REL-6
Condition Curr
Neigh
Explanation The IE is mandatory present if the IE MBMS p-t-m RB information list is included in the MBMS CURRENT CELL P-T-M RB INFORMATION message and not needed otherwise The IE is mandatory present if the IE MBMS p-t-m RB information list is included in the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message and not needed otherwise
10.3.9a.7b
This IE indicates whether the UE has any MBMS Selected Services, and if it does it includes the list of MBMS Selected Services.
Information element/Group name CHOICE Status >None >Some Need Multi Type and reference Semantics description (no data) MP MBMS Selected Services Full 10.3.9a.7c REL-6 Version
3GPP
Release 6
743
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.7c
MBMS Selected Services Full
This IE provides the MBMS Selected Services by means of the full identity.
Information element/Group name MBMS Selected Services Need MP Multi 1 to < maxMBM SservSel ect> MBMS service identity 10.3.9a.8 Type and reference Semantics description Version REL-6
>MBMS Selected Service ID
MP
REL-6
10.3.9a.7d
MBMS Selected Services Short
This IE indicates the MBMS Selected Services by means of a short identity to identify the MBMS transmission by referencing the services included in the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages.
Information element/Group name MBMS Selected Services Need MP Multi 1 to < maxMBM SservSel ect> MBMS Short transmissio n identity 10.3.9a.10 Integer (0..1) Type and reference Semantics description Version REL-6
>MBMS Selected Service ID
MP
REL-6
Modification period identity
MP
Indicates the modification period the MBMS short transmission identities refer to
REL-6
3GPP
Release 6
744
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.8
MBMS Service identity
Includes information about the identity of an MBMS service.

Information element/Group name MBMS Service ID Need MP Multi Type and reference MBMS Service ID 10.3.9a.8a Semantics description Version REL-6
CHOICE PLMN identity >SameAs-MIB
MP (No data) The PLMN identity is the same as indicated by the IE PLMN identity in MIB
REL-6 REL-6
>SameAsMIBMultiPLMN-Id >>Multi PLMN id
REL-6 MP Integer (1..5) The PLMN identity is one of the PLMN identities (1 to 5) in the IE "Multiple PLMN List" in MIB REL-6
>ExplicitPLMN-Id >>PLMN identity
MP
PLMN identity 10.3.1.11
REL-6 REL-6
10.3.9a.8a
MBMS Service ID
Uniquely identifies an MBMS bearer service within a PLMN.

Information element/Group name MBMS Service ID Need MP Multi Type and reference Octet string (3 ) Semantics description The content of the MBMS Service ID field is coded as octets 3 to 5 of the IE Temporary Mobile Group Identity [5] Version REL-6
3GPP
Release 6
745
3GPP TS 25.331 V6.23.0 (2009-09)
10.3.9a.9
MBMS Session identity
Includes information about the the identity of a session of an MBMS service.

Information element/Group name MBMS Session ID Need MP Multi Type and reference Octet string (1) Semantics description Version REL-6
10.3.9a.10
MBMS Short transmission identity
Includes a short identity of the MBMS transmission identity, which concerns a session of a specific service.
Information element/Group name MBMS short transmission identity Need MP Multi Type and reference Integer (1..maxMB MSservUn modif) Semantics description Reference/ index to a transmission listed in the MBMS MODIFIED SERVICES INFORMATION or MBMS UNMODIFIED SERVICES INFORMATION Version REL-6
10.3.9a.10a MBMS Soft Combining Timing Offset

Indicates the timing offset applied in the CFN calculation in sub-clause 8.5.15.5 for a secondary CCPCH carrying only MBMS logical channels. It is used for FDD only.
3GPP
Release 6 Information Element/Group name >MBMS Soft Combining Timing Offset Need MP Multi
746 Type and reference Integer (0, 10, 20, 40)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Timing offset applied in the CFN calculation in sub-clause 8.5.15.5, in ms. Version REL-6
10.3.9a.11
MBMS specific timers and counters
Includes MBMS specific timers and counters.

Information element/Group name T318 Need MD Multi Type and reference Integer(25 0... 2000 by step of 250, 3000, 4000, 6000, 8000, 10000, 12000, 16000) Semantics description Value in milliseconds. Default value is 1000. Version REL-6
10.3.9a.12
MBMS Transmission identity
Includes information about the MBMS transmission identity, which concerns a session of a specific service.
Information element/Group name MBMS Service ID Need MP Multi Type and reference MBMS Service identity 10.3.9a.8 MBMS Session identity 10.3.9a.9 Semantics description Version REL-6
MBMS Session ID
OP
REL-6
10.3.9a.13
Includes information about the MCCH configuration.

Information element/Group name Access Info Period coefficient Need MP Multi Type and reference Integer (0..3) Semantics description Represents a, the access information coefficient. The number of repetitions per modification period a equals 2 while the actual access information period, in number of frames, a equals MP DIV 2 Represents r, the repetition period coefficient. The number of repetitions per modification period r equals 2 while the actual repetition period, in number of frames, r equals MP DIV 2 Version REL-6
Repetition Period coefficient
MP
Integer (0..3)
REL-6
3GPP
Release 6 Modification period coefficient MP
747 Integer (7..10)
3GPP TS 25.331 V6.23.0 (2009-09) Represents m, the modification period coefficient. The actual modification period (MP), in number of m frames, equals 2 REL-6
RLC info
MP
TCTF presence
CVMBMS
RLC info MBMS 10.3.4.23a Enumerate d (false)
REL-6
By default the TCTF is present even though the FACH only carries one logical channel (type). When this IE is included, the TCTF is absent
REL-6
3GPP
Release 6 Condition MBMS
748
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation This IE is not needed if the IE is contained within the IE Secondary CCPCH system information, otherwise the IE is optional.
10.3.9a.14
MICH configuration information
Includes information about the MICH configuration.

Information element/Group name MICH Power offset Need MP Multi Type and reference MICH Power offset 10.3.9a.15 Semantics description Version REL-6
CHOICE mode >FDD >>Channelisation code >>Number of NI per frame >>STTD indicator
MP MP MP Integer (0.255) Integer (18, 36, 72, 144) STTD Indicator 10.3.6.78 Timeslot number 10.3.6.84 Midamble shift and burst type 10.3.6.41
MP
REL-6
>TDD >>Timeslot number
MP
REL-6 REL-6
>>Midamble shift and burst type
MP
REL-6
>>CHOICE TDD option >>>3.84 Mcps TDD >>>>Channelisation code
MP MP Enumerate d( (16/1)(16 /16)) 1 to 2 Enumerate d( (16/1)(16 /16)) Enumerate d((4/2),(8/2 ), (8/4),(16/2) , (16/4), (32/2),(32/ 4),(64/2),(6 4/4)) Integer (0Repetit ion period 1) Integer (4, 8, 16)
REL-6 REL-6 REL-6
>>>1.28 Mcps TDD >>>>Codes list >>>>>Channelisation code
MP MP
REL-6 REL-6 REL-6
>>Repetition period/length
MD
Default value is (64/2).
REL-6
>>Offset
MP
SFN mod Repetitionperiod = Offset. Indicates the length of one MBMS Notification indicator in bits. Default value is 4.
REL-6
>>MBMS Notification indicator length
MD
REL-6
10.3.9a.15
MICH Power offset
3GPP
Release 6
749
3GPP TS 25.331 V6.23.0 (2009-09)
This is the power transmitted on the MICH minus power of the Primary CPICH in FDD and Primary CCPCH Tx Power in TDD.
Information Element/Group name MICH Power offset Need MP Multi Type and reference Integer(-10 .. +5) Semantics description Offset in dB Version REL-6
10.3.9a.16
MSCH configuration information
Includes information about the MSCH configuration.

Information element/Group name MSCH configuration information Need MP Multi Type and reference Semantics description For FDD, scheduling information is provided starting at (SFN (SCTO div 10ms)) mod MSCH_REP = MSCH_OFF For TDD, scheduling information is provided starting at SFN mod MSCH_REP = MSCH_OFF The period, in number of frames, between MBMS scheduling messages (MSCH_REP) Default value is the value included in the MBMS GENERAL INFORMATION message The position of MBMS scheduling messages relative to timing of the corresponding cell (MSCH_OFF) Default value is the value included in the MBMS GENERAL INFORMATION message Default value is the one included in the MBMS GENERAL INFORMATION message By default the TCTF is present even though the FACH only carries one logical channel (type). When this IE is included, the TCTF is absent Version REL-6
>Scheduling period
MD
Enumerate d (32, 64, 128, 256, 512, 1024)
REL-6
>Scheduling offset
MD
Integer (0..(MSCH _REP-1))
REL-6
>RLC info
MD
RLC info MBMS 10.3.4.23a
REL-6
TCTF presence
OP
Enumerate d (false)
REL-6
10.3.10 Multiplicity values and type constraint values

The following table includes constants that are either used as multi bounds (name starting with "max") or as high or low value in a type specification (name starting with "lo" or "hi"). Constants are specified only for values appearing more than once in the RRC specification. In case a constant is related to one or more other constants, an expression is included in the "value" column instead of the actual value.
3GPP
Release 6 Constant CN information maxCNdomains UTRAN mobility information maxRAT maxOtherRAT maxURA maxInterSysMessages maxRABsetup UE information maxtransactions maxPDCPalgoType maxFreqBandsFDD maxFreqBandsFDD-ext maxFreqBandsTDD maxFreqBandsGSM maxPage1 maxSystemCapability MaxURNTIgroup RB information maxPredefConfig maxRB maxSRBsetup maxRBperRAB maxRBallRABs maxRBperTrCh maxRBMuxOptions maxLoCHperRLC maxRLCPDUsizePerLogCha n MaxROHC-PacketSizes MaxROHC-Profiles maxRFC 3095-CID TrCH information maxE-DCHMACdFlow MaxHProcesses MaxHSDSCH_TB_index
750 Explanation Maximum number of CN domains
3GPP TS 25.331 V6.23.0 (2009-09) Value 4 Version
Maximum number or Radio Access Technologies Maximum number or other Radio Access Technologies Maximum number of URAs in a cell Maximum number of Inter System Messages Maximum number of RABs to be established Maximum number of parallel RRC transactions in downlink Maximum number of PDCP algorithm types Maximum number of frequency bands supported by the UE as defined in [21] Maximum number of frequency bands as defined in [21] and treated by RRC Maximum number of frequency bands supported by the UE as defined in [22] Maximum number of frequency bands supported by the UE as defined in [45] Number of UEs paged in the Paging Type 1 message Maximum number of system specific capabilities that can be requested in one message. Maximum number of U-RNTI groups in one message Maximum number of predefined configurations Maximum number of RBs Maximum number of signalling RBs to be established Maximum number of RBs per RAB Maximum number of non signalling RBs Maximum number of RB per TrCh Maximum number of RB multiplexing options Maximum number of logical channels per RLC entity Maximum number of RLC PDU sizes per logical channel mapped on E-DCH Maximum number of packet sizes that are allowed to be produced by ROHC. Maximum number of profiles supported by ROHC on a given RB. Maximum number of available CID values per radio bearer Maximum number of E-DCH MAC-d flows Maximum number of H-ARQ processes Maximum number of TB set size configurations for the HS-DSCH. Maximum number of MAC-d PDU sizes per queue permitted for MAC-hs Maximum number of transport channels used in one direction (UL or DL) Maximum number of preconfigured Transport channels, per direction Maximum number of CCTrCHs Maximum number of Mac-hs queues Maximum number of different transport formats that can be included in the Transport format set for one transport channel
maxOtherRAT + 1 15 8 4 16 25 8 8 22 4 16 8 16 8 REL-5 REL-6
16 32 8 8 27 16 8 2 32 16 8 16384 REL-5
REL-6
REL-6
maxMACdPDUSizes maxTrCH maxTrCHpreconf maxCCTrCH maxQueueID MaxTF
8 8 64 (FDD and 1.28 MCPS TDD); 512 (3.84 Mcps TDD) 8 32 16 8 8 32
REL-6 REL-5 REL-5
REL-5
REL-5
3GPP
Release 6 Constant maxTFC maxTFCsub maxSIBperMsg maxSIB maxSIB-FACH PhyCH information maxHSSCCHs maxAC maxASC maxASCmap maxASCpersist maxPRACH MaxPRACH_FPACH maxFACHPCH maxRL maxEDCHRL maxSCCPCH maxDPDCH-UL maxDPCH-DLchan
751
3GPP TS 25.331 V6.23.0 (2009-09) Value 1024 1024 16 32 8 Version
Explanation Maximum number of Transport Format Combinations Maximum number of Transport Format Combinations Subset Maximum number of complete system information blocks per SYSTEM INFORMATION message Maximum number of references to other system information blocks. Maximum number of references to system information blocks on the FACH Maximum number of HSSCCH codes that can be assigned to a UE Maximum number of access classes Maximum number of access service classes Maximum number of access class to access service classes mappings Maximum number of access service classes for which persistence scaling factors are specified Maximum number of PRACHs in a cell Maximum number of PRACH / FPACH pairs in a cell (1.28 Mcps TDD) Maximum number of FACHs and PCHs mapped onto one secondary CCPCHs Maximum number of radio links Maximum number of E-DCH radio links Maximum number of secondary CCPCHs per cell Maximum number of DPDCHs per cell Maximum number of channelisation codes used for DL DPCH Maximum number of PUSCHs Maximum number of PDSCHs Maximum number of timeslots used in one direction (UL or DL)
4 16 8 7 6 16 8 8 8 4 16 6 8
REL-5
REL-4
REL-6
maxPUSCH maxPDSCH maxTS
hiPUSCHidentities hiPDSCHidentities Measurement information maxTGPS maxAdditionalMeas maxMeasEvent maxMeasParEvent maxMeasIntervals
Maximum number of PUSCH Identities Maximum number of PDSCH Identities Maximum number of transmission gap pattern sequences Maximum number of additional measurements for a given measurement identity Maximum number of events that can be listed in measurement reporting criteria Maximum number of measurement parameters (e.g. thresholds) per event Maximum number of intervals that define the mapping function between the measurements for the cell quality Q of a cell and the representing quality value Maximum number of cells to measure Maximum number of GSM cells to be reported Maximum number of frequencies to measure Maximum number of satellites to measure Maximum number of satellites for which to store GPS Almanac information Maximum number that could be set as rate matching attribute for a transport channel Maximum number of FDD carrier frequencies to be stored in USIM Maximum number of TDD carrier frequencies to be stored in USIM
(8) 8 14 (3.84 Mcps TDD) 6 (1.28 Mcps TDD) 64 64 6 4 8 2 1
REL-4
maxCellMeas maxReportedGSMCells maxFreq maxSat maxSatAlmanacStorage HiRM Frequency information MaxFDDFreqList MaxTDDFreqList
32 8 8 16 32 256
4 4
3GPP
Release 6 Constant MaxFDDFreqCellList MaxTDDFreqCellList MaxGSMCellList Other information MaxGERANSI maxNumGSMFreqRanges MaxNumFDDFreqs MaxNumTDDFreqs maxNumCDMA200Freqs maxGSMTargetCells MBMS information maxMBMS-CommonCCTrCh
752
3GPP TS 25.331 V6.23.0 (2009-09) Value 32 32 32 Version
Explanation Maximum number of neighbouring FDD cells to be stored in USIM Maximum number of neighbouring TDD cells to be stored in USIM Maximum number of GSM cells to be stored in USIM Maximum number of GERAN SI blocks that can be provided as part of NACC information Maximum number of GSM Frequency Ranges to store Maximum number of FDD centre frequencies to store Maximum number of TDD centre frequencies to store Maximum number of CDMA2000 centre frequencies to store Maximum number of GSM target cells Maximum number of CCTrCh configurations included in the MBMS COMMON P-T-M RB INFORMATION message Maximum number of PhyCh configurations included in the MBMS COMMON P-T-M RB INFORMATION message Maximum number of RB configurations included in the MBMS COMMON P-T-M RB INFORMATION message Maximum number of TrCh configurations included in the MBMS COMMON P-T-M RB INFORMATION message Maximum number of MBMS preferred frequencies Maximum number of periods in which layer 1 combining applies Maximum number of MBMS services in a Access Info message Maximum number of MBMS services in a MBMS MODIFIED SERVICES INFORMATION message Maximum number of MBMS services in a MBMS SCHEDULING INFORMATION message Maximum number of MBMS Selected Services in a CELL UPDATE or RRC CONNECTION REQUEST message Maximum number of MBMS services in a MBMS UNMODIFIED SERVICES INFORMATION message Maximum number of transmissions for which scheduling information is provided within a scheduling period Maximum number of MBMS services the UE stores in the variable MBMS_ACTIVATED_SERVICES
8 32 8 8 8 32 32
REL-5
REL-6 REL-6
maxMBMS-CommonPhyCh
32
REL-6
maxMBMS-CommonRB
32
REL-6
maxMBMS-CommonTrCh
32
REL-6
maxMBMS-Freq maxMBMS-L1CP maxMBMSservCount maxMBMSservModif maxMBMSservSched maxMBMSservSelect
4 4 8 32 16 8
maxMBMSservUnmodif
64
REL-6
maxMBMSTransmis
REL-6
maxMBMS-Services
64
REL-6
11
Message and Information element abstract syntax (with ASN.1)
This clause contains definitions for RRC PDUs and IEs using a subset of ASN.1 as specified in [14]. PDU and IE definitions are grouped into separate ASN.1 modules.
3GPP
Release 6
753
3GPP TS 25.331 V6.23.0 (2009-09)
11.0
General
Some messages and/or IEs may include one or more IEs with name "dummy" that are included only in the ASN.1. The UE should avoid sending information elements that are named "dummy" to UTRAN. Likewise, UTRAN should avoid sending IEs with name "dummy" to the UE. If the UE anyhow receives an information element named "dummy", it shall ignore the IE and process the rest of the message as if the IE was not included. NOTE: An IE with name "dummy" concerns an information element that was (erroneously) included in a previous version of the specification and has been removed by replacing it with a dummy with same type.
The UE shall only include the "variable length extension container" when it sends a non critical extension that according to this specification shall be transferred within this container. If the abstract syntax of an IE is defined using the ASN.1 type "BIT STRING", and this IE corresponds to a functional IE definition in tabular format, in which the significance of bits is semantically defined, the following general rule shall be applied: The bits in the ASN.1 bit string shall represent the semantics of the functional IE definition in decreasing order of bit significance; with the first (or leftmost) bit in the bit string representing the most significant bit; and with the last (or rightmost) bit in the bit string representing the least significant bit.
11.1
BEGIN IMPORTS
General message structure
Class-definitions DEFINITIONS AUTOMATIC TAGS ::=
ActiveSetUpdate, ActiveSetUpdateComplete, ActiveSetUpdateFailure, AssistanceDataDelivery, CellChangeOrderFromUTRAN, CellChangeOrderFromUTRANFailure, CellUpdate, CellUpdateConfirm-CCCH, CellUpdateConfirm, CounterCheck, CounterCheckResponse, DownlinkDirectTransfer, HandoverToUTRANComplete, InitialDirectTransfer, HandoverFromUTRANCommand-GERANIu, HandoverFromUTRANCommand-GSM, HandoverFromUTRANCommand-CDMA2000, HandoverFromUTRANFailure, MBMSAccessInformation, MBMSCommonPTMRBInformation, MBMSCurrentCellPTMRBInformation, MBMSGeneralInformation, MBMSModificationRequest, MBMSModifiedServicesInformation, MBMSNeighbouringCellPTMRBInformation, MBMSSchedulingInformation, MBMSUnmodifiedServicesInformation, MeasurementControl, MeasurementControlFailure, MeasurementReport, PagingType1, PagingType2, PhysicalChannelReconfiguration, PhysicalChannelReconfigurationComplete, PhysicalChannelReconfigurationFailure, PhysicalSharedChannelAllocation, PUSCHCapacityRequest, RadioBearerReconfiguration, RadioBearerReconfigurationComplete,
3GPP
Release 6
RadioBearerReconfigurationFailure, RadioBearerRelease, RadioBearerReleaseComplete, RadioBearerReleaseFailure, RadioBearerSetup, RadioBearerSetupComplete, RadioBearerSetupFailure, RRCConnectionReject, RRCConnectionRelease, RRCConnectionRelease-CCCH, RRCConnectionReleaseComplete, RRCConnectionRequest, RRCConnectionSetup, RRCConnectionSetupComplete, RRCStatus, SecurityModeCommand, SecurityModeComplete, SecurityModeFailure, SignallingConnectionRelease, SignallingConnectionReleaseIndication, SystemInformation-BCH, SystemInformation-FACH, SystemInformationChangeIndication, TransportChannelReconfiguration, TransportChannelReconfigurationComplete, TransportChannelReconfigurationFailure, TransportFormatCombinationControl, TransportFormatCombinationControlFailure, UECapabilityEnquiry, UECapabilityInformation, UECapabilityInformationConfirm, UplinkDirectTransfer, UplinkPhysicalChannelControl, URAUpdate, URAUpdateConfirm, URAUpdateConfirm-CCCH, UTRANMobilityInformation, UTRANMobilityInformationConfirm, UTRANMobilityInformationFailure FROM PDU-definitions -- User Equipment IEs : IntegrityCheckInfo FROM InformationElements;
754
3GPP TS 25.331 V6.23.0 (2009-09)
--************************************************************** --- Downlink DCCH messages ---************************************************************** DL-DCCH-Message ::= SEQUENCE { integrityCheckInfo IntegrityCheckInfo message DL-DCCH-MessageType } DL-DCCH-MessageType ::= CHOICE { activeSetUpdate assistanceDataDelivery cellChangeOrderFromUTRAN cellUpdateConfirm counterCheck downlinkDirectTransfer handoverFromUTRANCommand-GSM handoverFromUTRANCommand-CDMA2000 measurementControl pagingType2 physicalChannelReconfiguration physicalSharedChannelAllocation radioBearerReconfiguration radioBearerRelease radioBearerSetup rrcConnectionRelease securityModeCommand signallingConnectionRelease transportChannelReconfiguration transportFormatCombinationControl ueCapabilityEnquiry
OPTIONAL,
ActiveSetUpdate, AssistanceDataDelivery, CellChangeOrderFromUTRAN, CellUpdateConfirm, CounterCheck, DownlinkDirectTransfer, HandoverFromUTRANCommand-GSM, HandoverFromUTRANCommand-CDMA2000, MeasurementControl, PagingType2, PhysicalChannelReconfiguration, PhysicalSharedChannelAllocation, RadioBearerReconfiguration, RadioBearerRelease, RadioBearerSetup, RRCConnectionRelease, SecurityModeCommand, SignallingConnectionRelease, TransportChannelReconfiguration, TransportFormatCombinationControl, UECapabilityEnquiry,
3GPP
Release 6
ueCapabilityInformationConfirm uplinkPhysicalChannelControl uraUpdateConfirm utranMobilityInformation handoverFromUTRANCommand-GERANIu mbmsModifiedServicesInformation spare5 spare4 spare3 spare2 spare1 }
755
3GPP TS 25.331 V6.23.0 (2009-09)
UECapabilityInformationConfirm, UplinkPhysicalChannelControl, URAUpdateConfirm, UTRANMobilityInformation, HandoverFromUTRANCommand-GERANIu, MBMSModifiedServicesInformation, NULL, NULL, NULL, NULL, NULL
--************************************************************** --- Uplink DCCH messages ---************************************************************** UL-DCCH-Message ::= SEQUENCE { integrityCheckInfo IntegrityCheckInfo message UL-DCCH-MessageType }
OPTIONAL,
UL-DCCH-MessageType ::= CHOICE { activeSetUpdateComplete ActiveSetUpdateComplete, activeSetUpdateFailure ActiveSetUpdateFailure, cellChangeOrderFromUTRANFailure CellChangeOrderFromUTRANFailure, counterCheckResponse CounterCheckResponse, handoverToUTRANComplete HandoverToUTRANComplete, initialDirectTransfer InitialDirectTransfer, handoverFromUTRANFailure HandoverFromUTRANFailure, measurementControlFailure MeasurementControlFailure, measurementReport MeasurementReport, physicalChannelReconfigurationComplete PhysicalChannelReconfigurationComplete, physicalChannelReconfigurationFailure PhysicalChannelReconfigurationFailure, radioBearerReconfigurationComplete RadioBearerReconfigurationComplete, radioBearerReconfigurationFailure RadioBearerReconfigurationFailure, radioBearerReleaseComplete RadioBearerReleaseComplete, radioBearerReleaseFailure RadioBearerReleaseFailure, radioBearerSetupComplete RadioBearerSetupComplete, radioBearerSetupFailure RadioBearerSetupFailure, rrcConnectionReleaseComplete RRCConnectionReleaseComplete, rrcConnectionSetupComplete RRCConnectionSetupComplete, rrcStatus RRCStatus, securityModeComplete SecurityModeComplete, securityModeFailure SecurityModeFailure, signallingConnectionReleaseIndication SignallingConnectionReleaseIndication, transportChannelReconfigurationComplete TransportChannelReconfigurationComplete, transportChannelReconfigurationFailure TransportChannelReconfigurationFailure, transportFormatCombinationControlFailure TransportFormatCombinationControlFailure, ueCapabilityInformation UECapabilityInformation, uplinkDirectTransfer UplinkDirectTransfer, utranMobilityInformationConfirm UTRANMobilityInformationConfirm, utranMobilityInformationFailure UTRANMobilityInformationFailure, mbmsModificationRequest MBMSModificationRequest, spare1 NULL } --************************************************************** --- Downlink CCCH messages ---************************************************************** DL-CCCH-Message ::= SEQUENCE { integrityCheckInfo IntegrityCheckInfo message DL-CCCH-MessageType } DL-CCCH-MessageType ::= CHOICE { cellUpdateConfirm
OPTIONAL,
CellUpdateConfirm-CCCH,
3GPP
Release 6
rrcConnectionReject rrcConnectionRelease rrcConnectionSetup uraUpdateConfirm spare3 spare2 spare1 }
756
RRCConnectionReject, RRCConnectionRelease-CCCH, RRCConnectionSetup, URAUpdateConfirm-CCCH, NULL, NULL, NULL
3GPP TS 25.331 V6.23.0 (2009-09)
--************************************************************** --- Uplink CCCH messages ---************************************************************** UL-CCCH-Message ::= SEQUENCE { integrityCheckInfo IntegrityCheckInfo message UL-CCCH-MessageType } UL-CCCH-MessageType ::= CHOICE { cellUpdate rrcConnectionRequest uraUpdate spare }
OPTIONAL,
CellUpdate, RRCConnectionRequest, URAUpdate, NULL
--************************************************************** --- PCCH messages ---************************************************************** PCCH-Message ::= SEQUENCE { message PCCH-MessageType } PCCH-MessageType ::= CHOICE { pagingType1 spare }
PagingType1, NULL
--************************************************************** --- Downlink SHCCH messages ---************************************************************** DL-SHCCH-Message ::= SEQUENCE { message DL-SHCCH-MessageType } DL-SHCCH-MessageType ::= CHOICE { physicalSharedChannelAllocation spare }
PhysicalSharedChannelAllocation, NULL
--************************************************************** --- Uplink SHCCH messages ---************************************************************** UL-SHCCH-Message ::= SEQUENCE { message UL-SHCCH-MessageType } UL-SHCCH-MessageType ::= CHOICE { puschCapacityRequest spare }
PUSCHCapacityRequest, NULL
--************************************************************** --- BCCH messages sent on FACH ---**************************************************************
3GPP
Release 6
757
3GPP TS 25.331 V6.23.0 (2009-09)
BCCH-FACH-Message ::= SEQUENCE { message BCCH-FACH-MessageType } BCCH-FACH-MessageType ::= CHOICE { systemInformation systemInformationChangeIndication spare2 spare1 }
SystemInformation-FACH, SystemInformationChangeIndication, NULL, NULL
--************************************************************** --- BCCH messages sent on BCH ---************************************************************** BCCH-BCH-Message ::= SEQUENCE { message SystemInformation-BCH } --************************************************************** --- MCCH messages ---************************************************************** MCCH-Message ::= SEQUENCE { message MCCH-MessageType } MCCH-MessageType ::= CHOICE { mbmsAccessInformation MBMSAccessInformation, mbmsCommonPTMRBInformation MBMSCommonPTMRBInformation, mbmsCurrentCellPTMRBInformation MBMSCurrentCellPTMRBInformation, mbmsGeneralInformation MBMSGeneralInformation, mbmsModifiedServicesInformation MBMSModifiedServicesInformation, mbmsNeighbouringCellPTMRBInformation MBMSNeighbouringCellPTMRBInformation, mbmsUnmodifiedServicesInformation MBMSUnmodifiedServicesInformation, spare9 NULL, spare8 NULL, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL } --************************************************************** --- MSCH messages ---************************************************************** MSCH-Message ::= SEQUENCE { message MSCH-MessageType } MSCH-MessageType ::= CHOICE { mbmsSchedulingInformation spare3 spare2 spare1 } END
MBMSSchedulingInformation, NULL, NULL, NULL
11.2
PDU definitions
--************************************************************** --- TABULAR: The message type and integrity check info are not -- visible in this module as they are defined in the class module.
3GPP
Release 6
758
3GPP TS 25.331 V6.23.0 (2009-09)
-- Also, all FDD/TDD specific choices have the FDD option first -- and TDD second, just for consistency. ---************************************************************** PDU-definitions DEFINITIONS AUTOMATIC TAGS ::= BEGIN --************************************************************** --- IE parameter types from other modules ---************************************************************** IMPORTS -- Core Network IEs : CN-DomainIdentity, CN-InformationInfo, CN-InformationInfo-r6, CN-InformationInfoFull, NAS-Message, PagingRecordTypeID, PLMN-Identity, -- UTRAN Mobility IEs : CellIdentity, CellIdentity-PerRL-List, URA-Identity, -- User Equipment IEs : UE-RadioAccessCapabBandFDDList2, UE-RadioAccessCapabBandFDDList-ext, AccessStratumReleaseIndicator, ActivationTime, C-RNTI, CapabilityUpdateRequirement, CapabilityUpdateRequirement-r4, CapabilityUpdateRequirement-r4-ext, CapabilityUpdateRequirement-r5, CellUpdateCause, CellUpdateCause-ext, CipheringAlgorithm, CipheringModeInfo, DelayRestrictionFlag, DSCH-RNTI, E-RNTI, EstablishmentCause, FailureCauseWithProtErr, FailureCauseWithProtErrTrId, GroupReleaseInformation, H-RNTI, UESpecificBehaviourInformation1idle, UESpecificBehaviourInformation1interRAT, InitialUE-Identity, IntegrityProtActivationInfo, IntegrityProtectionModeInfo, N-308, PagingCause, PagingRecordList, PagingRecord2List-r5, ProtocolErrorIndicator, ProtocolErrorIndicatorWithMoreInfo, RadioFrequencyBandTDDList, Rb-timer-indicator, RedirectionInfo, RedirectionInfo-r6, RejectionCause, ReleaseCause, RF-CapabilityComp, RRC-StateIndicator, RRC-TransactionIdentifier, SecurityCapability, START-Value, STARTList, SystemSpecificCapUpdateReq-v590ext, U-RNTI, U-RNTI-Short, UE-CapabilityContainer-IEs,
3GPP
Release 6
UE-HSPA-Identities-r6, UE-RadioAccessCapability, UE-RadioAccessCapability-v370ext, UE-RadioAccessCapability-v380ext, UE-RadioAccessCapability-v3a0ext, UE-RadioAccessCapability-v3g0ext, UE-RadioAccessCapability-v4b0ext, UE-RadioAccessCapability-v590ext, UE-RadioAccessCapability-v5c0ext, UE-RadioAccessCapability-v650ext, UE-RadioAccessCapability-v680ext, UE-RadioAccessCapabilityComp, UE-RadioAccessCapabilityComp-ext, UE-RadioAccessCapabilityComp2, DL-PhysChCapabilityFDD-v380ext, UE-ConnTimersAndConstants, UE-ConnTimersAndConstants-v3a0ext, UE-ConnTimersAndConstants-r5, UE-SecurityInformation, UE-SecurityInformation2, URA-UpdateCause, UTRAN-DRX-CycleLengthCoefficient, WaitTime, -- Radio Bearer IEs : DefaultConfigIdentity, DefaultConfigIdentity-r4, DefaultConfigIdentity-r5, DefaultConfigIdentity-r6, DefaultConfigMode, DL-CounterSynchronisationInfo, DL-CounterSynchronisationInfo-r5, PDCP-ROHC-TargetMode, PredefinedConfigIdentity, PredefinedConfigStatusList, PredefinedConfigStatusListComp, PredefinedConfigSetWithDifferentValueTag, RAB-Info, RAB-Info-r6, RAB-Info-Post, RAB-InformationList, RAB-InformationList-r6, RAB-InformationReconfigList, RAB-InformationMBMSPtpList, RAB-InformationSetupList, RAB-InformationSetupList-r4, RAB-InformationSetupList-r5, RAB-InformationSetupList-r6-ext, RAB-InformationSetupList-r6, RAB-InformationSetupList-v6b0ext, RB-ActivationTimeInfoList, RB-COUNT-C-InformationList, RB-COUNT-C-MSB-InformationList, RB-IdentityList, RB-InformationAffectedList, RB-InformationAffectedList-r5, RB-InformationAffectedList-r6, RB-InformationChangedList-r6, RB-InformationReconfigList, RB-InformationReconfigList-r4, RB-InformationReconfigList-r5, RB-InformationReconfigList-r6, RB-InformationReleaseList, RB-PDCPContextRelocationList, SRB-InformationSetupList, SRB-InformationSetupList-r5, SRB-InformationSetupList-r6, SRB-InformationSetupList2, SRB-InformationSetupList2-r6, UL-CounterSynchronisationInfo, -- Transport Channel IEs: CPCH-SetID, DL-AddReconfTransChInfo2List, DL-AddReconfTransChInfoList, DL-AddReconfTransChInfoList-r4, DL-AddReconfTransChInfoList-r5, DL-CommonTransChInfo, DL-CommonTransChInfo-r4, DL-DeletedTransChInfoList,
759
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6
DL-DeletedTransChInfoList-r5, DRAC-StaticInformationList, PowerOffsetInfoShort, TFC-Subset, TFCS-Identity, UL-AddReconfTransChInfoList, UL-AddReconfTransChInfoList-r6, UL-CommonTransChInfo, UL-CommonTransChInfo-r4, UL-DeletedTransChInfoList, UL-DeletedTransChInfoList-r6, -- Physical Channel IEs : Alpha, BEACON-PL-Est, CCTrCH-PowerControlInfo, CCTrCH-PowerControlInfo-r4, CCTrCH-PowerControlInfo-r5, ConstantValue, ConstantValueTdd, CPCH-SetInfo, DHS-Sync, DL-CommonInformation, DL-CommonInformation-r4, DL-CommonInformation-r5, DL-CommonInformation-r6, DL-CommonInformationPost, DL-HSPDSCH-Information, DL-HSPDSCH-Information-r6, DL-InformationPerRL-List, DL-InformationPerRL-List-r4, DL-InformationPerRL-List-r5, DL-InformationPerRL-List-r5bis, DL-InformationPerRL-List-r6, DL-InformationPerRL-List-v6b0ext, DL-InformationPerRL-ListPostFDD, DL-InformationPerRL-PostTDD, DL-InformationPerRL-PostTDD-LCR-r4, DL-PDSCH-Information, DL-TPC-PowerOffsetPerRL-List, DPC-Mode, DPCH-CompressedModeStatusInfo, DynamicPersistenceLevel, E-DCH-ReconfigurationInfo, FrequencyInfo, FrequencyInfoFDD, FrequencyInfoTDD, HARQ-Preamble-Mode, HS-SICH-Power-Control-Info-TDD384, MaxAllowedUL-TX-Power, OpenLoopPowerControl-IPDL-TDD-r4, PDSCH-CapacityAllocationInfo, PDSCH-CapacityAllocationInfo-r4, PDSCH-Identity, PrimaryCPICH-Info, PrimaryCCPCH-TX-Power, PUSCH-CapacityAllocationInfo, PUSCH-CapacityAllocationInfo-r4, PUSCH-Identity, PUSCH-SysInfoList-HCR-r5, PDSCH-SysInfoList-HCR-r5, RL-AdditionInformationList, RL-AdditionInformationList-r6, RL-AdditionInformation-list-v6b0ext, RL-RemovalInformationList, Serving-HSDSCH-CellInformation, SpecialBurstScheduling, SSDT-Information, SSDT-Information-r4, TFC-ControlDuration, SSDT-UL, TimingMaintainedSynchInd, TimeslotList, TimeslotList-r4, TX-DiversityMode, UL-ChannelRequirement, UL-ChannelRequirement-r4, UL-ChannelRequirement-r5, UL-ChannelRequirementWithCPCH-SetID, UL-ChannelRequirementWithCPCH-SetID-r4,
760
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6
UL-ChannelRequirementWithCPCH-SetID-r5, UL-DPCH-Info, UL-DPCH-Info-r4, UL-DPCH-Info-r5, UL-DPCH-Info-r6, UL-DPCH-InfoPostFDD, UL-DPCH-InfoPostTDD, UL-DPCH-InfoPostTDD-LCR-r4, UL-EDCH-Information-r6, UL-SynchronisationParameters-r4, UL-TimingAdvance, UL-TimingAdvanceControl, UL-TimingAdvanceControl-r4, -- Measurement IEs : AdditionalMeasurementID-List, DeltaRSCP, Frequency-Band, EventResults, Inter-FreqEventCriteriaList-v590ext, Intra-FreqEventCriteriaList-v590ext, IntraFreqReportingCriteria-1b-r5, IntraFreqEvent-1d-r5, IntraFreqCellID, InterFreqEventResults-LCR-r4-ext, InterRATCellInfoIndication, InterRAT-TargetCellDescription, MeasuredResults, MeasuredResults-v390ext, MeasuredResults-v590ext, MeasuredResultsList, MeasuredResultsList-LCR-r4-ext, MeasuredResultsOnRACH, MeasuredResultsOnRACHinterFreq, MeasurementCommand, MeasurementCommand-r4, MeasurementCommand-r6, MeasurementIdentity, MeasurementReportingMode, PrimaryCCPCH-RSCP, SFN-Offset-Validity, TimeslotListWithISCP, TrafficVolumeMeasuredResultsList, UE-Positioning-GPS-AssistanceData, UE-Positioning-Measurement-v390ext, UE-Positioning-OTDOA-AssistanceData, UE-Positioning-OTDOA-AssistanceData-r4ext, UE-Positioning-OTDOA-AssistanceData-UEB, -- Other IEs : BCCH-ModificationInfo, CDMA2000-MessageList, GSM-TargetCellInfoList, GERANIu-MessageList, GERAN-SystemInformation, GSM-MessageList, InterRAT-ChangeFailureCause, InterRAT-HO-FailureCause, InterRAT-UE-RadioAccessCapabilityList, InterRAT-UE-RadioAccessCapability-v590ext, InterRAT-UE-SecurityCapList, IntraDomainNasNodeSelector, ProtocolErrorMoreInformation, Rplmn-Information, Rplmn-Information-r4, SegCount, SegmentIndex, SFN-Prime, SIB-Data-fixed, SIB-Data-variable, SIB-Type, -- MBMS IEs: MBMS-CellGroupIdentity-r6, MBMS-CommonRBInformationList-r6, MBMS-CurrentCell-SCCPCHList-r6, MBMS-JoinedInformation-r6, MBMS-MICHConfigurationInfo-r6, MBMS-ModifedServiceList-r6, MBMS-MSCH-ConfigurationInfo-r6, MBMS-NeighbouringCellSCCPCHList-r6, MBMS-NumberOfNeighbourCells-r6,
761
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6
MBMS-PhyChInformationList-r6, MBMS-PL-ServiceRestrictInfo-r6, MBMS-PreferredFreqRequest-r6, MBMS-PreferredFrequencyList-r6, MBMS-PTMActivationTime-r6, MBMS-SelectedServiceInfo, MBMS-SelectedServicesShort, MBMS-ServiceAccessInfoList-r6, MBMS-ServiceIdentity-r6, MBMS-ServiceSchedulingInfoList-r6, MBMS-SIBType5-SCCPCHList-r6, MBMS-TimersAndCounters-r6, MBMS-TranspChInfoForEachCCTrCh-r6, MBMS-TranspChInfoForEachTrCh-r6, MBMS-UnmodifiedServiceList-r6 FROM InformationElements maxSIBperMsg, maxURNTI-Group FROM Constant-definitions;
762
3GPP TS 25.331 V6.23.0 (2009-09)
-- *************************************************** --- ACTIVE SET UPDATE (FDD only) --- *************************************************** ActiveSetUpdate ::= CHOICE { r3 SEQUENCE { activeSetUpdate-r3 ActiveSetUpdate-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions activeSetUpdate-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { activeSetUpdate-v4b0ext ActiveSetUpdate-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { activeSetUpdate-v590ext ActiveSetUpdate-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { activeSetUpdate-v690ext ActiveSetUpdate-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r6 SEQUENCE { activeSetUpdate-r6 ActiveSetUpdate-r6-IEs, activeSetUpdate-r6-add-ext BIT STRING OPTIONAL, v6b0nonCriticalExtensions SEQUENCE { activeSetUpdate-v6b0ext ActiveSetUpdate-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } ActiveSetUpdate-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy IntegrityProtectionModeInfo OPTIONAL, dummy2 CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, newU-RNTI U-RNTI OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- Radio bearer IEs -- dummy3 is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy3 DL-CounterSynchronisationInfo OPTIONAL, -- Physical channel IEs maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL,
3GPP
Release 6
763
3GPP TS 25.331 V6.23.0 (2009-09)
rl-AdditionInformationList RL-AdditionInformationList OPTIONAL, rl-RemovalInformationList RL-RemovalInformationList OPTIONAL, tx-DiversityMode TX-DiversityMode OPTIONAL, -- dummy4 is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy4 SSDT-Information OPTIONAL } ActiveSetUpdate-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE RL-AdditionInformationList included in this message cell-id-PerRL-List CellIdentity-PerRL-List } ActiveSetUpdate-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs dpc-Mode dl-TPC-PowerOffsetPerRL-List } ActiveSetUpdate-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity } ActiveSetUpdate-r6-IEs ::= SEQUENCE { -- User equipment IEs activationTime newU-RNTI newH-RNTI newPrimary-E-RNTI newSecondary-E-RNTI -- Core network IEs cn-InformationInfo -- Physical channel IEs maxAllowedUL-TX-Power rl-AdditionInformationList rl-RemovalInformationList tx-DiversityMode dpc-Mode serving-HSDSCH-CellInformation e-dch-ReconfigurationInfo } ActiveSetUpdate-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs rl-AdditionInformation-list-v6b0ext }
OPTIONAL,
OPTIONAL
DPC-Mode, DL-TPC-PowerOffsetPerRL-List
OPTIONAL
PLMN-Identity
OPTIONAL
ActivationTime U-RNTI H-RNTI E-RNTI E-RNTI CN-InformationInfo-r6 MaxAllowedUL-TX-Power RL-AdditionInformationList-r6 RL-RemovalInformationList TX-DiversityMode DPC-Mode Serving-HSDSCH-CellInformation E-DCH-ReconfigurationInfo
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
RL-AdditionInformation-list-v6b0ext OPTIONAL
-- *************************************************** --- ACTIVE SET UPDATE COMPLETE (FDD only) --- *************************************************** ActiveSetUpdateComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy IntegrityProtActivationInfo OPTIONAL, -- Radio bearer IEs -- dummy2 and dummy3 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy2 RB-ActivationTimeInfoList OPTIONAL, dummy3 UL-CounterSynchronisationInfo OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions activeSetUpdateComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- ***************************************************
3GPP
Release 6
764
3GPP TS 25.331 V6.23.0 (2009-09)
--- ACTIVE SET UPDATE FAILURE (FDD only) --- *************************************************** ActiveSetUpdateFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions activeSetUpdateFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- Assistance Data Delivery --- *************************************************** AssistanceDataDelivery ::= CHOICE { r3 SEQUENCE { assistanceDataDelivery-r3 AssistanceDataDelivery-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { assistanceDataDelivery-v3a0ext AssistanceDataDelivery-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions assistanceDataDelivery-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { assistanceDataDelivery-v4b0ext AssistanceDataDelivery-v4b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } AssistanceDataDelivery-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Measurement Information Elements ue-positioning-GPS-AssistanceData UE-Positioning-GPS-AssistanceData OPTIONAL, ue-positioning-OTDOA-AssistanceData-UEB UE-Positioning-OTDOA-AssistanceData-UEB OPTIONAL } AssistanceDataDelivery-v3a0ext ::= SEQUENCE { sfn-Offset-Validity SFN-Offset-Validity }
OPTIONAL,
OPTIONAL
AssistanceDataDelivery-v4b0ext-IEs ::= SEQUENCE { ue-Positioning-OTDOA-AssistanceData-r4ext UE-Positioning-OTDOA-AssistanceData-r4ext } -- *************************************************** --- CELL CHANGE ORDER FROM UTRAN --- *************************************************** CellChangeOrderFromUTRAN ::= CHOICE { r3 SEQUENCE { cellChangeOrderFromUTRAN-IEs CellChangeOrderFromUTRAN-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions cellChangeOrderFromUTRAN-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { cellChangeOrderFromUTRAN-v590ext CellChangeOrderFromUTRAN-v590ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL
OPTIONAL
3GPP
Release 6
} OPTIONAL }, later-than-r3 rrc-TransactionIdentifier criticalExtensions } }
765
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { RRC-TransactionIdentifier, SEQUENCE {}
CellChangeOrderFromUTRAN-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy IntegrityProtectionModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, -- the IE rab-InformationList is not used in this version of the specification, it should -- not be sent and if received it should be ignored. The IE may be used in a later -- version of the protocol and hence it is not changed into a dummy rab-InformationList RAB-InformationList OPTIONAL, interRAT-TargetCellDescription InterRAT-TargetCellDescription } CellChangeOrderFromUTRAN-v590ext-IEs ::= SEQUENCE { geran-SystemInfoType CHOICE { sI GERAN-SystemInformation, pSI GERAN-SystemInformation } OPTIONAL } -- *************************************************** --- CELL CHANGE ORDER FROM UTRAN FAILURE --- *************************************************** CellChangeOrderFromUTRANFailure ::= CHOICE { r3 SEQUENCE { cellChangeOrderFromUTRANFailure-r3 CellChangeOrderFromUTRANFailure-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions cellChangeOrderFromUTRANFailure-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, -- dummy is not used in this version of the specification and it -- should be ignored. dummy SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } CellChangeOrderFromUTRANFailure-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy IntegrityProtectionModeInfo OPTIONAL, interRAT-ChangeFailureCause InterRAT-ChangeFailureCause } -- *************************************************** --- CELL UPDATE --- *************************************************** CellUpdate ::= SEQUENCE { -- User equipment IEs u-RNTI U-RNTI, startList STARTList, am-RLC-ErrorIndicationRb2-3or4 BOOLEAN, am-RLC-ErrorIndicationRb5orAbove BOOLEAN, cellUpdateCause CellUpdateCause, -- TABULAR: RRC transaction identifier is nested in FailureCauseWithProtErrTrId failureCause FailureCauseWithProtErrTrId OPTIONAL, rb-timer-indicator Rb-timer-indicator,
3GPP
Release 6
766
3GPP TS 25.331 V6.23.0 (2009-09)
-- Measurement IEs measuredResultsOnRACH MeasuredResultsOnRACH OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions cellUpdate-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { cellUpdate-v590ext CellUpdate-v590ext, v690NonCriticalExtensions SEQUENCE { cellUpdate-v690ext CellUpdate-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { cellUpdate-v6b0ext CellUpdate-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } CellUpdate-v590ext ::= SEQUENCE { establishmentCause }
EstablishmentCause
OPTIONAL
CellUpdate-v690ext-IEs ::= SEQUENCE { -- User equipment IEs cellUpdateCause-ext CellUpdateCause-ext trafficVolumeIndicator ENUMERATED { true } -- Measurement IEs measuredResultsOnRACHinterFreq MeasuredResultsOnRACHinterFreq reconfigurationStatusIndicator ENUMERATED { true } } CellUpdate-v6b0ext-IEs ::= -- MBMS IEs mbmsSelectedServices } SEQUENCE { MBMS-SelectedServicesShort
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
OPTIONAL
-- *************************************************** --- CELL UPDATE CONFIRM --- *************************************************** CellUpdateConfirm ::= CHOICE { r3 SEQUENCE { cellUpdateConfirm-r3 CellUpdateConfirm-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v3a0ext CellUpdateConfirm-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions cellUpdateConfirm-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v4b0ext CellUpdateConfirm-v4b0ext-IEs, v590NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v590ext CellUpdateConfirm-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v690ext CellUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { cellUpdateConfirm-r4 CellUpdateConfirm-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 cellUpdateConfirm-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v590ext CellUpdateConfirm-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs,
3GPP
Release 6
767
v690NonCriticalExtensions cellUpdateConfirm-v690ext nonCriticalExtensions } OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL
3GPP TS 25.331 V6.23.0 (2009-09)

SEQUENCE { CellUpdateConfirm-v690ext-IEs, SEQUENCE {} OPTIONAL
} }, criticalExtensions CHOICE { r5 SEQUENCE { cellUpdateConfirm-r5 CellUpdateConfirm-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 cellUpdateConfirm-r5-add-ext BIT STRING OPTIONAL, v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v690ext CellUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { cellUpdateConfirm-r6 CellUpdateConfirm-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 cellUpdateConfirm-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v6b0ext CellUpdateConfirm-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } CellUpdateConfirm-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, rlc-Re-establishIndicatorRb2-3or4 BOOLEAN, rlc-Re-establishIndicatorRb5orAbove BOOLEAN, -- CN information elements cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rb-InformationReleaseList RB-InformationReleaseList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, modeSpecificTransChInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL }, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL,
3GPP
Release 6
768
3GPP TS 25.331 V6.23.0 (2009-09)
ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL } CellUpdateConfirm-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received the UE behaviour -- is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } CellUpdateConfirm-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } CellUpdateConfirm-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-TPC-PowerOffsetPerRL-List DL-TPC-PowerOffsetPerRL-List }
OPTIONAL,
OPTIONAL
OPTIONAL
CellUpdateConfirm-v5d0ext-IEs ::= SEQUENCE { --Radio Bearer IEs pdcp-ROHC-TargetMode PDCP-ROHC-TargetMode OPTIONAL } CellUpdateConfirm-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, rlc-Re-establishIndicatorRb2-3or4 BOOLEAN, rlc-Re-establishIndicatorRb5orAbove BOOLEAN, -- CN information elements cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rb-InformationReleaseList RB-InformationReleaseList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r4 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, modeSpecificTransChInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL }, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Physical channel IEs
3GPP
Release 6
769
3GPP TS 25.331 V6.23.0 (2009-09)
frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL } CellUpdateConfirm-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, rlc-Re-establishIndicatorRb2-3or4 BOOLEAN, rlc-Re-establishIndicatorRb5orAbove BOOLEAN, -- CN information elements cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rb-InformationReleaseList RB-InformationReleaseList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r5 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList-r5 OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, modeSpecificTransChInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL }, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r5 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } CellUpdateConfirm-r6-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime new-U-RNTI U-RNTI
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
3GPP
Release 6
770
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL,
----
--
--
-}
new-C-RNTI C-RNTI -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI new-H-RNTI H-RNTI newPrimary-E-RNTI E-RNTI newSecondary-E-RNTI E-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient rlc-Re-establishIndicatorRb2-3or4 BOOLEAN, rlc-Re-establishIndicatorRb5orAbove BOOLEAN, CN information elements cn-InformationInfo CN-InformationInfo-r6 UTRAN mobility IEs ura-Identity URA-Identity Radio bearer IEs rb-InformationReleaseList RB-InformationReleaseList rb-InformationReconfigList RB-InformationReconfigList-r6 rb-InformationAffectedList RB-InformationAffectedList-r6 dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 pdcp-ROHC-TargetMode PDCP-ROHC-TargetMode Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 ul-deletedTransChInfoList UL-DeletedTransChInfoList-r6 ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 dl-CommonTransChInfo DL-CommonTransChInfo-r4 dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 Physical channel IEs frequencyInfo FrequencyInfo maxAllowedUL-TX-Power MaxAllowedUL-TX-Power ul-DPCH-Info UL-DPCH-Info-r6 ul-EDCH-Information UL-EDCH-Information-r6 dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 dl-CommonInformation DL-CommonInformation-r6 dl-InformationPerRL-List DL-InformationPerRL-List-r6 MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
CellUpdateConfirm-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL } CellUpdateConfirm-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext }
DL-InformationPerRL-List-v6b0ext
OPTIONAL
-- *************************************************** --- CELL UPDATE CONFIRM for CCCH --- *************************************************** CellUpdateConfirm-CCCH ::= CHOICE { r3 SEQUENCE { -- User equipment IEs u-RNTI U-RNTI, -- The rest of the message is identical to the one sent on DCCH. cellUpdateConfirm-r3 CellUpdateConfirm-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions cellUpdateConfirm-CCCH-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v4b0ext CellUpdateConfirm-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v590ext CellUpdateConfirm-v590ext-IEs,
3GPP
Release 6
771
3GPP TS 25.331 V6.23.0 (2009-09)
} }, later-than-r3 SEQUENCE { u-RNTI U-RNTI, rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { -- The rest of the message is identical to the one sent on DCCH. cellUpdateConfirm-r4 CellUpdateConfirm-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 cellUpdateConfirm-CCCH-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v590ext CellUpdateConfirm-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v690ext CellUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { cellUpdateConfirm-r5 CellUpdateConfirm-r5-IEs, cellUpdateConfirm-CCCH-r5-add-ext BIT STRING OPTIONAL, v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v690ext CellUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { cellUpdateConfirm-r6 CellUpdateConfirm-r6-IEs, cellUpdateConfirm-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v6b0ext CellUpdateConfirm-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } -- *************************************************** --- COUNTER CHECK --- *************************************************** CounterCheck ::= CHOICE { r3 SEQUENCE { counterCheck-r3 CounterCheck-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions counterCheck-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier,
v5d0NonCriticalExtenstions SEQUENCE { cellUpdateConfirm-v5d0ext CellUpdateConfirm-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { cellUpdateConfirm-v690ext CellUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL
3GPP
Release 6
criticalExtensions } } CounterCheck-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier -- Radio bearer IEs rb-COUNT-C-MSB-InformationList }
772
SEQUENCE {}
3GPP TS 25.331 V6.23.0 (2009-09)
RRC-TransactionIdentifier, RB-COUNT-C-MSB-InformationList
-- *************************************************** --- COUNTER CHECK RESPONSE --- *************************************************** CounterCheckResponse ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Radio bearer IEs rb-COUNT-C-InformationList RB-COUNT-C-InformationList laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions counterCheckResponse-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- DOWNLINK DIRECT TRANSFER --- *************************************************** DownlinkDirectTransfer ::= CHOICE { r3 SEQUENCE { downlinkDirectTransfer-r3 DownlinkDirectTransfer-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions downlinkDirectTransfer-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } DownlinkDirectTransfer-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Core network IEs cn-DomainIdentity CN-DomainIdentity, nas-Message NAS-Message } -- *************************************************** --- HANDOVER TO UTRAN COMMAND --- ***************************************************
OPTIONAL,
HandoverToUTRANCommand ::= CHOICE { r3 SEQUENCE { handoverToUTRANCommand-r3 HandoverToUTRANCommand-r3-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL }, criticalExtensions CHOICE { r4 SEQUENCE { handoverToUTRANCommand-r4 HandoverToUTRANCommand-r4-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { handoverToUTRANCommand-r5 HandoverToUTRANCommand-r5-IEs,
3GPP
Release 6
773
3GPP TS 25.331 V6.23.0 (2009-09)
nonCriticalExtensions SEQUENCE {} OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { handoverToUTRANCommand-r6 HandoverToUTRANCommand-r6-IEs, v6b0NonCriticalExtensions SEQUENCE { handoverToUTRANCommand-v6b0ext HandoverToUTRANCommand-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } }
HandoverToUTRANCommand-r3-IEs ::= SEQUENCE { -- User equipment IEs new-U-RNTI U-RNTI-Short, -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy ActivationTime OPTIONAL, cipheringAlgorithm CipheringAlgorithm OPTIONAL, -- Radio bearer IEs -- Specification mode information specificationMode CHOICE { complete SEQUENCE { srb-InformationSetupList SRB-InformationSetupList, rab-InformationSetupList RAB-InformationSetupList OPTIONAL, ul-CommonTransChInfo UL-CommonTransChInfo, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList, dl-CommonTransChInfo DL-CommonTransChInfo, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList, ul-DPCH-Info UL-DPCH-Info, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of specification, -- they should not be sent and if received they should be ignored. dummy DL-PDSCH-Information OPTIONAL, dummy2 CPCH-SetInfo OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation, dl-InformationPerRL-List DL-InformationPerRL-List, frequencyInfo FrequencyInfo }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity } }, rab-Info RAB-Info-Post OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostFDD, dl-CommonInformationPost DL-CommonInformationPost, dl-InformationPerRL-List DL-InformationPerRL-ListPostFDD, frequencyInfo FrequencyInfoFDD }, tdd SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD, dl-CommonInformationPost DL-CommonInformationPost, dl-InformationPerRL DL-InformationPerRL-PostTDD, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } }, -- Physical channel IEs
3GPP
Release 6
maxAllowedUL-TX-Power }
774
MaxAllowedUL-TX-Power
3GPP TS 25.331 V6.23.0 (2009-09)
HandoverToUTRANCommand-r4-IEs ::= SEQUENCE { -- User equipment IEs new-U-RNTI U-RNTI-Short, cipheringAlgorithm CipheringAlgorithm OPTIONAL, -- Radio bearer IEs -- Specification mode information specificationMode CHOICE { complete SEQUENCE { srb-InformationSetupList SRB-InformationSetupList, rab-InformationSetupList RAB-InformationSetupList-r4 OPTIONAL, ul-CommonTransChInfo UL-CommonTransChInfo-r4, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList, dl-CommonTransChInfo DL-CommonTransChInfo-r4, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4, ul-DPCH-Info UL-DPCH-Info-r4, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of specification, -- they should not be sent and if received they should be ignored. dummy DL-PDSCH-Information OPTIONAL, dummy2 CPCH-SetInfo OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4, dl-InformationPerRL-List DL-InformationPerRL-List-r4, frequencyInfo FrequencyInfo }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r4 } }, rab-Info RAB-Info-Post OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostFDD, dl-CommonInformationPost DL-CommonInformationPost, dl-InformationPerRL-List DL-InformationPerRL-ListPostFDD, frequencyInfo FrequencyInfoFDD }, tdd CHOICE { tdd384 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD, dl-InformationPerRL DL-InformationPerRL-PostTDD, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power }, tdd128 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD-LCR-r4, dl-InformationPerRL DL-InformationPerRL-PostTDD-LCR-r4, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } } }, -- Physical channel IEs maxAllowedUL-TX-Power MaxAllowedUL-TX-Power } HandoverToUTRANCommand-r5-IEs ::= SEQUENCE { -- User equipment IEs new-U-RNTI U-RNTI-Short, cipheringAlgorithm CipheringAlgorithm -- Radio bearer IEs -- Specification mode information specificationMode CHOICE {
OPTIONAL,
3GPP
Release 6
775
3GPP TS 25.331 V6.23.0 (2009-09)
complete SEQUENCE { srb-InformationSetupList SRB-InformationSetupList-r5, rab-InformationSetupList RAB-InformationSetupList-r5 OPTIONAL, ul-CommonTransChInfo UL-CommonTransChInfo-r4, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList, dl-CommonTransChInfo DL-CommonTransChInfo-r4, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5, ul-DPCH-Info UL-DPCH-Info-r5, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of specification, -- they should not be sent and if received they should be ignored. dummy DL-PDSCH-Information OPTIONAL, dummy2 CPCH-SetInfo OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4, dl-InformationPerRL-List DL-InformationPerRL-List-r5, frequencyInfo FrequencyInfo }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r5 } }, rab-Info RAB-Info-Post OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostFDD, dl-CommonInformationPost DL-CommonInformationPost, dl-InformationPerRL-List DL-InformationPerRL-ListPostFDD, frequencyInfo FrequencyInfoFDD }, tdd CHOICE { tdd384 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD, dl-InformationPerRL DL-InformationPerRL-PostTDD, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power }, tdd128 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD-LCR-r4, dl-InformationPerRL DL-InformationPerRL-PostTDD-LCR-r4, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } } }, -- Physical channel IEs maxAllowedUL-TX-Power MaxAllowedUL-TX-Power } HandoverToUTRANCommand-r6-IEs ::= SEQUENCE { -- User equipment IEs new-U-RNTI U-RNTI-Short, cipheringAlgorithm CipheringAlgorithm OPTIONAL, -- Radio bearer IEs -- Specification mode information specificationMode CHOICE { complete SEQUENCE { srb-InformationSetupList SRB-InformationSetupList-r6, rab-InformationSetupList RAB-InformationSetupList-r6 OPTIONAL, ul-CommonTransChInfo UL-CommonTransChInfo-r4, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6, dl-CommonTransChInfo DL-CommonTransChInfo-r4, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5, ul-DPCH-Info UL-DPCH-Info-r6, ul-EDCH-Information UL-EDCH-Information-r6 OPTIONAL, dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 OPTIONAL,
3GPP
Release 6
dl-CommonInformation dl-InformationPerRL-List frequencyInfo
776
3GPP TS 25.331 V6.23.0 (2009-09)
DL-CommonInformation-r6, DL-InformationPerRL-List-r6, FrequencyInfo
}, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r6 } }, rab-Info RAB-Info-Post OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostFDD, dl-CommonInformationPost DL-CommonInformationPost, dl-InformationPerRL-List DL-InformationPerRL-ListPostFDD, frequencyInfo FrequencyInfoFDD }, tdd CHOICE { tdd384 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD, dl-InformationPerRL DL-InformationPerRL-PostTDD, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power }, tdd128 SEQUENCE { ul-DPCH-Info UL-DPCH-InfoPostTDD-LCR-r4, dl-InformationPerRL DL-InformationPerRL-PostTDD-LCR-r4, frequencyInfo FrequencyInfoTDD, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } } }, -- Physical channel IEs maxAllowedUL-TX-Power } HandoverToUTRANCommand-v6b0ext-IEs ::= SEQUENCE { ue-hspa-identities UE-HSPA-Identities-r6 } -- *************************************************** --- HANDOVER TO UTRAN COMPLETE --- *************************************************** HandoverToUTRANComplete ::= SEQUENCE { --TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs -- TABULAR: startList is conditional on history. startList STARTList OPTIONAL, -- Radio bearer IEs count-C-ActivationTime ActivationTime OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions handoverToUTRANComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- INITIAL DIRECT TRANSFER --- *************************************************** InitialDirectTransfer ::= SEQUENCE { -- Core network IEs cn-DomainIdentity intraDomainNasNodeSelector
MaxAllowedUL-TX-Power
OPTIONAL
CN-DomainIdentity, IntraDomainNasNodeSelector,
3GPP
Release 6
777
3GPP TS 25.331 V6.23.0 (2009-09)
nas-Message NAS-Message, -- Measurement IEs measuredResultsOnRACH MeasuredResultsOnRACH OPTIONAL, v3a0NonCriticalExtensions SEQUENCE { initialDirectTransfer-v3a0ext InitialDirectTransfer-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions initialDirectTransfer-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { initialDirectTransfer-v590ext InitialDirectTransfer-v590ext, v690NonCriticalExtensions SEQUENCE { initialDirectTransfer-v690ext InitialDirectTransfer-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } InitialDirectTransfer-v3a0ext ::= SEQUENCE { -- start-value shall always be included in this version of the protocol start-Value START-Value OPTIONAL } InitialDirectTransfer-v590ext ::= SEQUENCE { establishmentCause EstablishmentCause OPTIONAL } InitialDirectTransfer-v690ext-IEs ::= SEQUENCE { -- Core network IEs plmn-Identity PLMN-Identity -- Measurement IEs measuredResultsOnRACHinterFreq MeasuredResultsOnRACHinterFreq -- MBMS IEs mbms-JoinedInformation MBMS-JoinedInformation-r6 } -- *************************************************** --- HANDOVER FROM UTRAN COMMAND --- *************************************************** HandoverFromUTRANCommand-GSM ::= CHOICE { r3 SEQUENCE { handoverFromUTRANCommand-GSM-r3 HandoverFromUTRANCommand-GSM-r3-IEs, -- UTRAN should not include the IE laterNonCriticalExtensions when it sets the IE -- gsm-message included in handoverFromUTRANCommand-GSM-r3 to single-GSM-Message. The UE -- behaviour upon receiving a message with this combination of IE values is unspecified. laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions handoverFromUTRANCommand-GSM-r3-add-ext BIT STRING OPTIONAL, -- UTRAN may apply the r3 version of the message to perform PS handover -- for a single RAB only v690NonCriticalExtensions SEQUENCE { handoverFromUTRANCommand-GSM-v690ext HandoverFromUTRANCommand-GSM-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r6 SEQUENCE { handoverFromUTRANCommand-GSM-r6 HandoverFromUTRANCommand-GSM-r6-IEs, handoverFromUTRANCommand-GSM-r6-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL }, criticalExtensions SEQUENCE {} } } } HandoverFromUTRANCommand-GSM-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, activationTime ActivationTime -- Radio bearer IEs
OPTIONAL, OPTIONAL, OPTIONAL
OPTIONAL,
3GPP
Release 6
778
3GPP TS 25.331 V6.23.0 (2009-09)
toHandoverRAB-Info RAB-Info OPTIONAL, -- Measurement IEs frequency-band Frequency-Band, -- Other IEs gsm-message CHOICE { -- In the single-GSM-Message case the following rules apply: -- 1> the GSM message directly follows the basic production; the final padding that -results when PER encoding the abstract syntax value is removed prior to appending -the GSM message. -- 2> the RRC message excluding the GSM part, does not contain a length determinant; -there is no explicit parameter indicating the size of the included GSM message. -- 3> depending on need, final padding (all 0s) is added to ensure the final result -comprises a full number of octets single-GSM-Message SEQUENCE {}, gsm-MessageList SEQUENCE { gsm-Messages GSM-MessageList } } } HandoverFromUTRANCommand-GSM-r6-IEs ::= SEQUENCE { -- User equipment IEs activationTime ActivationTime OPTIONAL, -- Radio bearer IEs toHandoverRAB-Info RAB-InformationList-r6 OPTIONAL, -- Measurement IEs frequency-band Frequency-Band, -- Other IEs gsm-message CHOICE { -- In the single-GSM-Message case the following rules apply: -- 1> the GSM message directly follows the basic production; the final padding that -results when PER encoding the abstract syntax value is removed prior to appending -the GSM message. -- 2> the RRC message excluding the GSM part, does not contain a length determinant; -there is no explicit parameter indicating the size of the included GSM message. -- 3> depending on need, final padding (all 0s) is added to ensure the final result -comprises a full number of octets single-GSM-Message SEQUENCE {}, gsm-MessageList SEQUENCE { gsm-Messages GSM-MessageList } }, geran-SystemInfoType CHOICE { sI GERAN-SystemInformation, pSI GERAN-SystemInformation } OPTIONAL } HandoverFromUTRANCommand-GSM-v690ext-IEs ::= SEQUENCE { geran-SystemInfoType CHOICE { sI GERAN-SystemInformation, pSI GERAN-SystemInformation } OPTIONAL } HandoverFromUTRANCommand-GERANIu ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, handoverFromUTRANCommand-GERANIu CHOICE { r5 SEQUENCE { handoverFromUTRANCommand-GERANIu-r5 HandoverFromUTRANCommand-GERANIu-r5-IEs, -- UTRAN should not include the IE nonCriticalExtensions when it sets -- the IE geranIu-message included in handoverFromUTRANCommand-GERANIu-r5 to -- single-GERANIu-Message -- The UE behaviour upon receiving a message including this combination of IE values is -- not specified nonCriticalExtensions SEQUENCE {} OPTIONAL }, later-than-r5 SEQUENCE { criticalExtensions SEQUENCE {} } } } HandoverFromUTRANCommand-GERANIu-r5-IEs ::= SEQUENCE { -- User equipment IEs activationTime ActivationTime -- Measurement IEs
OPTIONAL,
3GPP
Release 6
779
3GPP TS 25.331 V6.23.0 (2009-09)
---
frequency-Band Frequency-Band, -- Other IEs geranIu-Message CHOICE { -- In the single-GERANIu-Message case the following rules apply: -- 1> the GERAN Iu message directly follows the basic production; the final padding that -results when PER encoding the abstract syntax value is removed prior to appending -the GERAN Iu message. -- 2> the RRC message excluding the GERAN Iu part does not contain a length determinant; there is no explicit parameter indicating the size of the included GERAN Iu message. -- 3> depending on need, final padding (all 0s) is added to ensure the final result -comprises a full number of octets. single-GERANIu-Message SEQUENCE {}, geranIu-MessageList SEQUENCE { geranIu-Messages GERANIu-MessageList } }
} HandoverFromUTRANCommand-CDMA2000 ::= CHOICE { r3 SEQUENCE { handoverFromUTRANCommand-CDMA2000-r3 HandoverFromUTRANCommand-CDMA2000-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions handoverFromUTRANCommand-CDMA2000-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } HandoverFromUTRANCommand-CDMA2000-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, activationTime ActivationTime -- Radio bearer IEs toHandoverRAB-Info RAB-Info -- Other IEs cdma2000-MessageList CDMA2000-MessageList } -- *************************************************** --- HANDOVER FROM UTRAN FAILURE --- *************************************************** HandoverFromUTRANFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Other IEs interRAT-HO-FailureCause InterRAT-HO-FailureCause OPTIONAL, -- In case the interRATMessage to be transferred is for GERAN Iu mode, the -- message should be placed in the HandoverFromUtranFailure-v590ext-IEs -- non-critical extension container. interRATMessage CHOICE { gsm SEQUENCE { gsm-MessageList GSM-MessageList }, cdma2000 SEQUENCE { cdma2000-MessageList CDMA2000-MessageList } } OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions handoverFromUTRANFailure-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { handoverFromUTRANFailure-v590ext HandoverFromUtranFailure-v590ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }
OPTIONAL, OPTIONAL,
3GPP
Release 6
780
3GPP TS 25.331 V6.23.0 (2009-09)
HandoverFromUtranFailure-v590ext-IEs ::= SEQUENCE { geranIu-MessageList GERANIu-MessageList } -- *************************************************** --- INTER RAT HANDOVER INFO --- ***************************************************
OPTIONAL
InterRATHandoverInfo ::= SEQUENCE { -- This structure is defined for historical reasons, backward compatibility with 44.018 predefinedConfigStatusList CHOICE { absent NULL, present PredefinedConfigStatusList }, uE-SecurityInformation CHOICE { absent NULL, present UE-SecurityInformation }, ue-CapabilityContainer CHOICE { absent NULL, -- present is an octet aligned string containing IE UE-RadioAccessCapabilityInfo present OCTET STRING (SIZE (0..63)) }, -- Non critical extensions v390NonCriticalExtensions CHOICE { absent NULL, present SEQUENCE { interRATHandoverInfo-v390ext InterRATHandoverInfo-v390ext-IEs, v3a0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3a0ext InterRATHandoverInfo-v3a0ext-IEs, laterNonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3d0ext InterRATHandoverInfo-v3d0ext-IEs, -- Container for additional R99 extensions interRATHandoverInfo-r3-add-ext BIT STRING (CONTAINING InterRATHandoverInfo-r3-add-ext-IEs) OPTIONAL, v3g0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3g0ext InterRATHandoverInfo-v3g0ext-IEs, v4b0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v4b0ext InterRATHandoverInfo-v4b0ext-IEs, v4d0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v4d0ext InterRATHandoverInfo-v4d0ext-IEs, -- Reserved for future non critical extension v590NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v590ext InterRATHandoverInfo-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v690ext InterRATHandoverInfo-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v6b0ext InterRATHandoverInfo-v6b0ext-IEs, v6e0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v6e0ext InterRATHandoverInfo-v6e0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } } } InterRATHandoverInfo-v390ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v380ext UE-RadioAccessCapability-v380ext dl-PhysChCapabilityFDD-v380ext DL-PhysChCapabilityFDD-v380ext } InterRATHandoverInfo-v3a0ext-IEs ::= SEQUENCE { -- User equipment IEs
OPTIONAL,
3GPP
Release 6
ue-RadioAccessCapability-v3a0ext } InterRATHandoverInfo-v3d0ext-IEs ::= SEQUENCE { -- User equipment IEs uESpecificBehaviourInformation1interRAT OPTIONAL }
781
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
UE-RadioAccessCapability-v3a0ext
UESpecificBehaviourInformation1interRAT
InterRATHandoverInfo-v3g0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v3g0ext UE-RadioAccessCapability-v3g0ext } InterRATHandoverInfo-r3-add-ext-IEs ::= SEQUENCE { interRATHandoverInfo-v690ext1 InterRATHandoverInfo-v690ext1-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } InterRATHandoverInfo-v4b0ext-IEs ::= SEQUENCE { -- User equipment IEs accessStratumReleaseIndicator AccessStratumReleaseIndicator } InterRATHandoverInfo-v4d0ext-IEs ::= SEQUENCE { -- User equipment IEs tdd128-RF-Capability RadioFrequencyBandTDDList }
OPTIONAL
OPTIONAL
InterRATHandoverInfo-v590ext-IEs ::= SEQUENCE { -- User equipment IEs predefinedConfigStatusListComp PredefinedConfigStatusListComp ue-RadioAccessCapabilityComp UE-RadioAccessCapabilityComp } InterRATHandoverInfo-v690ext1-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v650ext UE-RadioAccessCapability-v650ext } InterRATHandoverInfo-v690ext-IEs ::= SEQUENCE { -- User equipment IEs ue-SecurityInformation2 UE-SecurityInformation2 ue-RadioAccessCapabilityComp UE-RadioAccessCapabilityComp-ext ue-RadioAccessCapabilityComp2 UE-RadioAccessCapabilityComp2 } InterRATHandoverInfo-v6b0ext-IEs ::= SEQUENCE { -- User equipment IEs supportForSIB11bis ENUMERATED { true } } InterRATHandoverInfo-v6e0ext-IEs ::= SEQUENCE { -- User equipment IEs supportForFDPCH ENUMERATED { true } } -- *************************************************** --- MEASUREMENT CONTROL --- ***************************************************
OPTIONAL, OPTIONAL
OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL
OPTIONAL
MeasurementControl ::= CHOICE { -- The Rel-4 functionality of UE Positioning OTDOA AssistanceData TDD is only available -- in the later-than-r3 branch of this message (i.e. through the use of the IE -- ue-Positioning-OTDOA-AssistanceData-r4) r3 SEQUENCE { measurementControl-r3 MeasurementControl-r3-IEs, v390nonCriticalExtensions SEQUENCE { measurementControl-v390ext MeasurementControl-v390ext, v3a0NonCriticalExtensions SEQUENCE { measurementControl-v3a0ext MeasurementControl-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions measurementControl-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE{ -- The content of the v4b0 non-critical extension has been removed. If sent
3GPP
Release 6
782
3GPP TS 25.331 V6.23.0 (2009-09)
} } } }
-- to a UE of AS release 4, the UE behaviour is unspecified. A UE of AS -- release 5 onward shall comply with the v4b0 and later extensions in this -- branch of the message. v590NonCriticalExtensions SEQUENCE { measurementControl-v590ext MeasurementControl-v590ext-IEs, v5b0NonCriticalExtensions SEQUENCE { measurementControl-v5b0ext MeasurementControl-v5b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL OPTIONAL OPTIONAL OPTIONAL
}, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { measurementControl-r4 MeasurementControl-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 measurementControl-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE{ measurementControl-v590ext MeasurementControl-v590ext-IEs, v5b0NonCriticalExtensions SEQUENCE { measurementControl-v5b0ext MeasurementControl-v5b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r4 SEQUENCE { -- Most significant part of "RRC transaction identifier" (MSP), -- "RRC transaction identifier" = rrc-TransactionIdentifier-MSP * 4 + -- rrc-TransactionIdentifier rrc-TransactionIdentifier-MSP RRC-TransactionIdentifier, criticalExtensions CHOICE { r6 SEQUENCE { measurementControl-r6 MeasurementControl-r6-IEs, v6a0NonCriticalExtensions SEQUENCE { measurementControl-v6a0ext MeasurementControl-v6a0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } MeasurementControl-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Measurement IEs measurementIdentity MeasurementIdentity, -- TABULAR: The measurement type is included in MeasurementCommand. measurementCommand MeasurementCommand, measurementReportingMode MeasurementReportingMode OPTIONAL, additionalMeasurementList AdditionalMeasurementID-List OPTIONAL, -- Physical channel IEs dpch-CompressedModeStatusInfo DPCH-CompressedModeStatusInfo OPTIONAL } MeasurementControl-v390ext ::= SEQUENCE { ue-Positioning-Measurement-v390ext }
UE-Positioning-Measurement-v390ext
OPTIONAL
MeasurementControl-v3a0ext ::= SEQUENCE { sfn-Offset-Validity SFN-Offset-Validity }
OPTIONAL
MeasurementControl-r4-IEs ::= SEQUENCE { -- Measurement IEs measurementIdentity MeasurementIdentity, -- TABULAR: The measurement type is included in measurementCommand. measurementCommand MeasurementCommand-r4,
3GPP
Release 6
measurementReportingMode additionalMeasurementList -- Physical channel IEs dpch-CompressedModeStatusInfo }
783
MeasurementReportingMode AdditionalMeasurementID-List DPCH-CompressedModeStatusInfo
3GPP TS 25.331 V6.23.0 (2009-09)

MeasurementControl-v590ext-IEs ::= SEQUENCE { measurementCommand-v590ext CHOICE { -- the choice intra-frequency shall be used for the case of intra-frequency measurement, -- as well as when intra-frequency events are configured for inter-frequency measurement intra-frequency Intra-FreqEventCriteriaList-v590ext, inter-frequency Inter-FreqEventCriteriaList-v590ext } OPTIONAL, intraFreqReportingCriteria-1b-r5 IntraFreqReportingCriteria-1b-r5 OPTIONAL, intraFreqEvent-1d-r5 IntraFreqEvent-1d-r5 OPTIONAL, -- most significant part of "RRC transaction identifier" (MSP), -- "RRC transaction identifier" = rrc-TransactionIdentifier-MSP-v590ext * 4 + -- rrc-TransactionIdentifier rrc-TransactionIdentifier-MSP-v590ext RRC-TransactionIdentifier } MeasurementControl-v5b0ext-IEs ::= interRATCellInfoIndication } SEQUENCE { InterRATCellInfoIndication
OPTIONAL
MeasurementControl-r6-IEs ::= SEQUENCE { -- Measurement IEs measurementIdentity MeasurementIdentity, -- TABULAR: The measurement type is included in measurementCommand. measurementCommand MeasurementCommand-r6, measurementReportingMode MeasurementReportingMode OPTIONAL, additionalMeasurementList AdditionalMeasurementID-List OPTIONAL, -- Physical channel IEs dpch-CompressedModeStatusInfo DPCH-CompressedModeStatusInfo OPTIONAL } MeasurementControl-v6a0ext-IEs ::= SEQUENCE { intraFreqReportingCriteria-1b-r5 IntraFreqReportingCriteria-1b-r5 } -- *************************************************** --- MEASUREMENT CONTROL FAILURE --- *************************************************** MeasurementControlFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions measurementControlFailure-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { measurementControlFailure-v590ext MeasurementControlFailure-v590ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } MeasurementControlFailure-v590ext-IEs ::= SEQUENCE { -- most significant part of "RRC transaction identifier" (MSP), -- "RRC transaction identifier" = rrc-TransactionIdentifier-MSP-v590ext * 4 + -- rrc-TransactionIdentifier -- If the rrc-TransactionIdentifier-MSP-v590ext was not received in the MEASUREMENT CONTROL -- message, then the rrc-TransactionIdentifier-MSP-v590ext shall be set to zero rrc-TransactionIdentifier-MSP-v590ext RRC-TransactionIdentifier } -- *************************************************** --- MEASUREMENT REPORT --- *************************************************** MeasurementReport ::= SEQUENCE { -- Measurement IEs measurementIdentity MeasurementIdentity,
OPTIONAL
3GPP
Release 6
784
3GPP TS 25.331 V6.23.0 (2009-09)
measuredResults MeasuredResults OPTIONAL, measuredResultsOnRACH MeasuredResultsOnRACH OPTIONAL, additionalMeasuredResults MeasuredResultsList OPTIONAL, eventResults EventResults OPTIONAL, -- Non-critical extensions v390nonCriticalExtensions SEQUENCE { measurementReport-v390ext MeasurementReport-v390ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions measurementReport-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { measurementReport-v4b0ext MeasurementReport-v4b0ext-IEs, -- Extension mechanism for non-Rel4 information v590NonCriticalExtensions SEQUENCE { measurementReport-v590ext MeasurementReport-v590ext-IEs, v5b0NonCriticalExtensions SEQUENCE { measurementReport-v5b0ext MeasurementReport-v5b0ext-IEs, v690NonCriticalExtensions SEQUENCE { measurementReport-v690ext MeasurementReport-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } MeasurementReport-v390ext ::= SEQUENCE { measuredResults-v390ext MeasuredResults-v390ext }
OPTIONAL
MeasurementReport-v4b0ext-IEs ::= SEQUENCE { interFreqEventResults-LCR InterFreqEventResults-LCR-r4-ext OPTIONAL, -- additionalMeasuredResults-LCR shall contain measurement results and additional measurement -- results list. additionalMeasuredResults-LCR MeasuredResultsList-LCR-r4-ext OPTIONAL, -- dummy is not used in this version of the specification. It should not be sent and -- if received it should be ignored. dummy PrimaryCPICH-Info OPTIONAL } MeasurementReport-v590ext-IEs ::= SEQUENCE { measuredResults-v590ext MeasuredResults-v590ext } MeasurementReport-v5b0ext-IEs ::= interRATCellInfoIndication } SEQUENCE { InterRATCellInfoIndication
OPTIONAL
OPTIONAL
MeasurementReport-v690ext-IEs ::= SEQUENCE { measuredResultsOnRACHinterFreq MeasuredResultsOnRACHinterFreq } -- *************************************************** --- PAGING TYPE 1 --- *************************************************** PagingType1 ::= SEQUENCE { -- User equipment IEs pagingRecordList -- Other IEs bcch-ModificationInfo laterNonCriticalExtensions -- Container for additional pagingType1-r3-add-ext v590NonCriticalExtensions pagingType1-v590ext nonCriticalExtensions } OPTIONAL } OPTIONAL } PagingType1-v590ext-IEs ::= SEQUENCE { -- User equipment IEs pagingRecord2List
OPTIONAL
PagingRecordList BCCH-ModificationInfo SEQUENCE { R99 extensions BIT STRING OPTIONAL, SEQUENCE { PagingType1-v590ext-IEs, SEQUENCE {} OPTIONAL
OPTIONAL, OPTIONAL,
PagingRecord2List-r5
OPTIONAL
3GPP
Release 6
}
785
3GPP TS 25.331 V6.23.0 (2009-09)
-- *************************************************** --- PAGING TYPE 2 --- *************************************************** PagingType2 ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier pagingCause -- Core network IEs cn-DomainIdentity pagingRecordTypeID laterNonCriticalExtensions -- Container for additional pagingType2-r3-add-ext nonCriticalExtensions } OPTIONAL }
RRC-TransactionIdentifier, PagingCause, CN-DomainIdentity, PagingRecordTypeID, SEQUENCE { R99 extensions BIT STRING OPTIONAL, SEQUENCE {} OPTIONAL
-- *************************************************** --- PHYSICAL CHANNEL RECONFIGURATION --- *************************************************** PhysicalChannelReconfiguration ::= CHOICE { r3 SEQUENCE { physicalChannelReconfiguration-r3 PhysicalChannelReconfiguration-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { physicalChannelReconfiguration-v3a0ext PhysicalChannelReconfiguration-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions physicalChannelReconfiguration-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtenstions SEQUENCE { physicalChannelReconfiguration-v4b0ext PhysicalChannelReconfiguration-v4b0ext-IEs, v590NonCriticalExtenstions SEQUENCE { physicalChannelReconfiguration-v590ext PhysicalChannelReconfiguration-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { physicalChannelReconfiguration-v690ext PhysicalChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { physicalChannelReconfiguration-r4 PhysicalChannelReconfiguration-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 physicalChannelReconfiguration-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtenstions SEQUENCE { physicalChannelReconfiguration-v590ext PhysicalChannelReconfiguration-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { physicalChannelReconfiguration-v690ext PhysicalChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { physicalChannelReconfiguration-r5 PhysicalChannelReconfiguration-r5-IEs, -- Container for adding non critical extensions after freezing REL-6
3GPP
Release 6
786
3GPP TS 25.331 V6.23.0 (2009-09)
physicalChannelReconfiguration-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { physicalChannelReconfiguration-v690ext PhysicalChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { physicalChannelReconfiguration-r6 PhysicalChannelReconfiguration-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 physicalChannelReconfiguration-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { physicalChannelReconfiguration-v6b0ext PhysicalChannelReconfiguration-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } PhysicalChannelReconfiguration-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, -- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. ul-ChannelRequirement UL-ChannelRequirementWithCPCH-SetID OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL } PhysicalChannelReconfiguration-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received the UE behaviour -- is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } PhysicalChannelReconfiguration-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } PhysicalChannelReconfiguration-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs
OPTIONAL,
OPTIONAL
3GPP
Release 6
dl-TPC-PowerOffsetPerRL-List }
787
DL-TPC-PowerOffsetPerRL-List
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
PhysicalChannelReconfiguration-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, -- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. ul-ChannelRequirement UL-ChannelRequirementWithCPCH-SetID-r4 OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL } PhysicalChannelReconfiguration-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, -- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. ul-ChannelRequirement UL-ChannelRequirementWithCPCH-SetID-r5 OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } PhysicalChannelReconfiguration-r6-IEs ::= SEQUENCE {
3GPP
Release 6
788
3GPP TS 25.331 V6.23.0 (2009-09)
-- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime delayRestrictionFlag DelayRestrictionFlag new-U-RNTI U-RNTI new-C-RNTI C-RNTI -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI new-H-RNTI H-RNTI newPrimary-E-RNTI E-RNTI newSecondary-E-RNTI E-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient -- Core network IEs cn-InformationInfo CN-InformationInfo-r6 -- UTRAN mobility IEs ura-Identity URA-Identity -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 -- Physical channel IEs frequencyInfo FrequencyInfo maxAllowedUL-TX-Power MaxAllowedUL-TX-Power ul-DPCH-Info UL-DPCH-Info-r6 ul-EDCH-Information UL-EDCH-Information-r6 dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 dl-CommonInformation DL-CommonInformation-r6 dl-InformationPerRL-List DL-InformationPerRL-List-r6 -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
PhysicalChannelReconfiguration-v690ext-IEs ::= SEQUENCE { -- User Equipment IEs delayRestrictionFlag DelayRestrictionFlag OPTIONAL, -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, timingMaintainedSynchInd TimingMaintainedSynchInd OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL } PhysicalChannelReconfiguration-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext DL-InformationPerRL-List-v6b0ext } -- *************************************************** --- PHYSICAL CHANNEL RECONFIGURATION COMPLETE --- *************************************************** PhysicalChannelReconfigurationComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo OPTIONAL, -- TABULAR: UL-TimingAdvance is applicable for TDD mode only. ul-TimingAdvance UL-TimingAdvance OPTIONAL, -- Radio bearer IEs count-C-ActivationTime ActivationTime OPTIONAL, -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList OPTIONAL, ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions physicalChannelReconfigurationComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL
OPTIONAL
3GPP
Release 6
}
789
3GPP TS 25.331 V6.23.0 (2009-09)
-- *************************************************** --- PHYSICAL CHANNEL RECONFIGURATION FAILURE --- *************************************************** PhysicalChannelReconfigurationFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier OPTIONAL, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions physicalChannelReconfigurationFailure-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- PHYSICAL SHARED CHANNEL ALLOCATION (TDD only) --- *************************************************** PhysicalSharedChannelAllocation ::= CHOICE { r3 SEQUENCE { physicalSharedChannelAllocation-r3 PhysicalSharedChannelAllocation-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions physicalSharedChannelAllocation-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { dsch-RNTI DSCH-RNTI OPTIONAL, rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { physicalSharedChannelAllocation-r4 PhysicalSharedChannelAllocation-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 physicalSharedChannelAllocation-r4-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { physicalSharedChannelAllocation-v690ext PhysicalSharedChannelAllocation-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } PhysicalSharedChannelAllocation-r3-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs dsch-RNTI DSCH-RNTI OPTIONAL, rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Physical channel IEs ul-TimingAdvance UL-TimingAdvanceControl OPTIONAL, pusch-CapacityAllocationInfo PUSCH-CapacityAllocationInfo OPTIONAL, pdsch-CapacityAllocationInfo PDSCH-CapacityAllocationInfo OPTIONAL, -- TABULAR: If confirmRequest is not present, the default value "No Confirm" -- shall be used as specified in 10.2.25. confirmRequest ENUMERATED { confirmPDSCH, confirmPUSCH } OPTIONAL, trafficVolumeReportRequest INTEGER (0..255) OPTIONAL, iscpTimeslotList TimeslotList OPTIONAL, requestPCCPCHRSCP BOOLEAN } PhysicalSharedChannelAllocation-r4-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- Physical channel IEs
3GPP
Release 6
790
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL, OPTIONAL, OPTIONAL, Confirm"
ul-TimingAdvance UL-TimingAdvanceControl-r4 pusch-CapacityAllocationInfo PUSCH-CapacityAllocationInfo-r4 pdsch-CapacityAllocationInfo PDSCH-CapacityAllocationInfo-r4 -- TABULAR: If confirmRequest is not present, the default value "No -- shall be used as specified in 10.2.25. confirmRequest ENUMERATED { confirmPDSCH, confirmPUSCH } trafficVolumeReportRequest INTEGER (0..255) iscpTimeslotList TimeslotList-r4 requestPCCPCHRSCP BOOLEAN } PhysicalSharedChannelAllocation-v690ext-IEs ::= SEQUENCE { -- Physical Channel IEs beaconPLEst BEACON-PL-Est } -- *************************************************** --- PUSCH CAPACITY REQUEST (TDD only) --- ***************************************************
OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL
PUSCHCapacityRequest ::= SEQUENCE { -- User equipment IEs dsch-RNTI DSCH-RNTI OPTIONAL, -- Measurement IEs trafficVolume TrafficVolumeMeasuredResultsList OPTIONAL, timeslotListWithISCP TimeslotListWithISCP OPTIONAL, primaryCCPCH-RSCP PrimaryCCPCH-RSCP OPTIONAL, allocationConfirmation CHOICE { pdschConfirmation PDSCH-Identity, puschConfirmation PUSCH-Identity } OPTIONAL, protocolErrorIndicator ProtocolErrorIndicatorWithMoreInfo, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions puschCapacityRequest-r3-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { puschCapacityRequest-v590ext PUSCHCapacityRequest-v590ext, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } PUSCHCapacityRequest-v590ext ::= SEQUENCE { primaryCCPCH-RSCP-delta DeltaRSCP } -- *************************************************** --- RADIO BEARER RECONFIGURATION --- ***************************************************
OPTIONAL
RadioBearerReconfiguration ::= CHOICE { r3 SEQUENCE { radioBearerReconfiguration-r3 RadioBearerReconfiguration-r3-IEs, -- Prefix "v3ao" is used (in one instance) to keep alignment with R99 v3aoNonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v3a0ext RadioBearerReconfiguration-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerReconfiguration-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v4b0ext RadioBearerReconfiguration-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v590ext RadioBearerReconfiguration-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { radioBearerReconfiguration-v5d0ext RadioBearerReconfiguration-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v690ext RadioBearerReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL
3GPP
Release 6
} OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL
791
3GPP TS 25.331 V6.23.0 (2009-09)
} }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { radioBearerReconfiguration-r4 RadioBearerReconfiguration-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 radioBearerReconfiguration-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v590ext RadioBearerReconfiguration-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { radioBearerReconfiguration-v5d0ext RadioBearerReconfiguration-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v690ext RadioBearerReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { radioBearerReconfiguration-r5 RadioBearerReconfiguration-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 radioBearerReconfiguration-r5-add-ext BIT STRING OPTIONAL, v5d0NonCriticalExtenstions SEQUENCE { radioBearerReconfiguration-v5d0ext RadioBearerReconfiguration-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v690ext RadioBearerReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { radioBearerReconfiguration-r6 RadioBearerReconfiguration-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 radioBearerReconfiguration-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { radioBearerReconfiguration-v6b0ext RadioBearerReconfiguration-v6b0ext-IEs, v6f0NonCriticalExtensions SEQUENCE { radioBearerRconfiguration-v6f0ext RadioBearerReconfiguration-v6f0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } RadioBearerReconfiguration-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime new-U-RNTI U-RNTI new-C-RNTI C-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient -- Core network IEs cn-InformationInfo CN-InformationInfo -- UTRAN mobility IEs ura-Identity URA-Identity
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
3GPP
Release 6
792
3GPP TS 25.331 V6.23.0 (2009-09)
-- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, -- NOTE: IE rb-InformationReconfigList should be optional in later versions -- of this message rb-InformationReconfigList RB-InformationReconfigList, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfo2List OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, -- NOTE: IE dl-InformationPerRL-List is optional in later versions -- of this message dl-InformationPerRL-List DL-InformationPerRL-List } RadioBearerReconfiguration-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received the UE behaviour -- is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } RadioBearerReconfiguration-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } RadioBearerReconfiguration-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-TPC-PowerOffsetPerRL-List DL-TPC-PowerOffsetPerRL-List } RadioBearerReconfiguration-v5d0ext-IEs ::= SEQUENCE { --Radio Bearer IEs pdcp-ROHC-TargetMode PDCP-ROHC-TargetMode }
OPTIONAL,
OPTIONAL
OPTIONAL
OPTIONAL
RadioBearerReconfiguration-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL,
3GPP
Release 6
793
3GPP TS 25.331 V6.23.0 (2009-09)
-- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r4 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL } RadioBearerReconfiguration-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Specification mode information specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r5 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList-r5 OPTIONAL, rb-PDCPContextRelocationList RB-PDCPContextRelocationList OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the -- specification, they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL,
3GPP
Release 6
dl-CommonTransChInfo dl-DeletedTransChInfoList dl-AddReconfTransChInfoList
794
3GPP TS 25.331 V6.23.0 (2009-09)

DL-CommonTransChInfo-r4 DL-DeletedTransChInfoList-r5 DL-AddReconfTransChInfoList-r5
}, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r5 } } } }, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r5 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } RadioBearerReconfiguration-r6-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, delayRestrictionFlag DelayRestrictionFlag OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, newPrimary-E-RNTI E-RNTI OPTIONAL, newSecondary-E-RNTI E-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo-r6 OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Specification mode information specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r6 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList-r6 OPTIONAL, rb-PDCPContextRelocationList RB-PDCPContextRelocationList OPTIONAL, pdcp-ROHC-TargetMode PDCP-ROHC-TargetMode OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList-r6 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE {
3GPP
Release 6
defaultConfigMode defaultConfigIdentity } } } }, -- Physical channel IEs frequencyInfo maxAllowedUL-TX-Power ul-DPCH-Info ul-EDCH-Information dl-HSPDSCH-Information dl-CommonInformation dl-InformationPerRL-List -- MBMS IEs mbms-PL-ServiceRestrictInfo }
795
3GPP TS 25.331 V6.23.0 (2009-09)

DefaultConfigMode, DefaultConfigIdentity-r6
FrequencyInfo MaxAllowedUL-TX-Power UL-DPCH-Info-r6 UL-EDCH-Information-r6 DL-HSPDSCH-Information-r6 DL-CommonInformation-r6 DL-InformationPerRL-List-r6 MBMS-PL-ServiceRestrictInfo-r6
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
RadioBearerReconfiguration-v690ext-IEs ::= SEQUENCE { -- User Equipment IEs delayRestrictionFlag DelayRestrictionFlag OPTIONAL, -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, timingMaintainedSynchInd TimingMaintainedSynchInd OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL } RadioBearerReconfiguration-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext DL-InformationPerRL-List-v6b0ext } RadioBearerReconfiguration-v6f0ext-IEs ::= SEQUENCE { -- Specification mode information specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs rab-InformationMBMSPtpList RAB-InformationMBMSPtpList } } } -- *************************************************** --- RADIO BEARER RECONFIGURATION COMPLETE --- *************************************************** RadioBearerReconfigurationComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo -- TABULAR: UL-TimingAdvance is applicable for TDD mode only. ul-TimingAdvance UL-TimingAdvance -- Radio bearer IEs count-C-ActivationTime ActivationTime -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerReconfigurationComplete-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RADIO BEARER RECONFIGURATION FAILURE
OPTIONAL
OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL,
3GPP
Release 6
796
3GPP TS 25.331 V6.23.0 (2009-09)
--- *************************************************** RadioBearerReconfigurationFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, -- Radio bearer IEs potentiallySuccesfulBearerList RB-IdentityList laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerReconfigurationFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RADIO BEARER RELEASE --- *************************************************** RadioBearerRelease ::= CHOICE { r3 SEQUENCE { radioBearerRelease-r3 RadioBearerRelease-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { radioBearerRelease-v3a0ext RadioBearerRelease-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerRelease-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { radioBearerRelease-v4b0ext RadioBearerRelease-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { radioBearerRelease-v590ext RadioBearerRelease-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerRelease-v690ext RadioBearerRelease-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { radioBearerRelease-r4 RadioBearerRelease-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 radioBearerRelease-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { radioBearerRelease-v590ext RadioBearerRelease-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerRelease-v690ext RadioBearerRelease-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { radioBearerRelease-r5 RadioBearerRelease-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 radioBearerRelease-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { radioBearerRelease-v690ext RadioBearerRelease-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { radioBearerRelease-r6 RadioBearerRelease-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 radioBearerRelease-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { radioBearerRelease-v6b0ext RadioBearerRelease-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL
OPTIONAL,
OPTIONAL,
3GPP
Release 6
} OPTIONAL }, criticalExtensions } } } } }
797
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE {}
RadioBearerRelease-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, signallingConnectionRelIndication CN-DomainIdentity OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReleaseList RB-InformationReleaseList, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfo2List OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL } RadioBearerRelease-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received the UE behaviour -- is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } RadioBearerRelease-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } RadioBearerRelease-v590ext-IEs ::= SEQUENCE {
OPTIONAL,
OPTIONAL
3GPP
Release 6
-- Physical channel IEs dl-TPC-PowerOffsetPerRL-List }
798
3GPP TS 25.331 V6.23.0 (2009-09)
DL-TPC-PowerOffsetPerRL-List
OPTIONAL
RadioBearerRelease-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, signallingConnectionRelIndication CN-DomainIdentity OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReleaseList RB-InformationReleaseList, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL } RadioBearerRelease-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime new-U-RNTI U-RNTI new-C-RNTI C-RNTI -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI new-H-RNTI H-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient -- Core network IEs cn-InformationInfo CN-InformationInfo signallingConnectionRelIndication CN-DomainIdentity -- UTRAN mobility IEs ura-Identity URA-Identity -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
3GPP
Release 6
799
3GPP TS 25.331 V6.23.0 (2009-09)
rb-InformationReleaseList RB-InformationReleaseList, rb-InformationAffectedList RB-InformationAffectedList-r5 OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r5 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } RadioBearerRelease-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, timingMaintainedSynchInd TimingMaintainedSynchInd OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL, mbms-RB-ListReleasedToChangeTransferMode RB-InformationReleaseList OPTIONAL } RadioBearerRelease-r6-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime new-U-RNTI U-RNTI new-C-RNTI C-RNTI -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI new-H-RNTI H-RNTI newPrimary-E-RNTI E-RNTI newSecondary-E-RNTI E-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient -- Core network IEs cn-InformationInfo CN-InformationInfo-r6 signallingConnectionRelIndication CN-DomainIdentity -- UTRAN mobility IEs ura-Identity URA-Identity -- Radio bearer IEs rab-InformationReconfigList RAB-InformationReconfigList rb-InformationReleaseList RB-InformationReleaseList, rb-InformationReconfigList RB-InformationReconfigList-r6 rb-InformationAffectedList RB-InformationAffectedList-r6
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
3GPP
Release 6
800
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 ul-deletedTransChInfoList UL-DeletedTransChInfoList-r6 ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 dl-CommonTransChInfo DL-CommonTransChInfo-r4 dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 -- Physical channel IEs frequencyInfo FrequencyInfo maxAllowedUL-TX-Power MaxAllowedUL-TX-Power ul-DPCH-Info UL-DPCH-Info-r6 ul-EDCH-Information UL-EDCH-Information-r6 dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 dl-CommonInformation DL-CommonInformation-r6 dl-InformationPerRL-List DL-InformationPerRL-List-r6 -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 mbms-RB-ListReleasedToChangeTransferMode RB-InformationReleaseList } RadioBearerRelease-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext }
OPTIONAL
-- *************************************************** --- RADIO BEARER RELEASE COMPLETE --- *************************************************** RadioBearerReleaseComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo -- TABULAR: UL-TimingAdvance is applicable for TDD mode only. ul-TimingAdvance UL-TimingAdvance -- Radio bearer IEs count-C-ActivationTime ActivationTime -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerReleaseComplete-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RADIO BEARER RELEASE FAILURE --- *************************************************** RadioBearerReleaseFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, -- Radio bearer IEs potentiallySuccesfulBearerList RB-IdentityList laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerReleaseFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RADIO BEARER SETUP --- *************************************************** RadioBearerSetup ::= CHOICE {
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
3GPP
Release 6
r3
801
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { radioBearerSetup-r3 RadioBearerSetup-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { radioBearerSetup-v3a0ext RadioBearerSetup-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerSetup-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { radioBearerSetup-v4b0ext RadioBearerSetup-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { radioBearerSetup-v590ext RadioBearerSetup-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { radioBearerSetup-v5d0ext RadioBearerSetup-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerSetup-v690ext RadioBearerSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL
}, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { radioBearerSetup-r4 RadioBearerSetup-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 radioBearerSetup-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { radioBearerSetup-v590ext RadioBearerSetup-v590ext-IEs, v5d0NonCriticalExtenstions SEQUENCE { radioBearerSetup-v5d0ext RadioBearerSetup-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerSetup-v690ext RadioBearerSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { radioBearerSetup-r5 RadioBearerSetup-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 radioBearerSetup-r5-add-ext BIT STRING OPTIONAL, v5d0NonCriticalExtenstions SEQUENCE { radioBearerSetup-v5d0ext RadioBearerSetup-v5d0ext-IEs, v690NonCriticalExtensions SEQUENCE { radioBearerSetup-v690ext RadioBearerSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { radioBearerSetup-r6 RadioBearerSetup-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 radioBearerSetup-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { radioBearerSetup-v6b0ext RadioBearerSetup-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } RadioBearerSetup-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier integrityProtectionModeInfo cipheringModeInfo
RRC-TransactionIdentifier, IntegrityProtectionModeInfo CipheringModeInfo
OPTIONAL, OPTIONAL,
3GPP
Release 6
802
3GPP TS 25.331 V6.23.0 (2009-09)
----
--
--
activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList OPTIONAL, rab-InformationSetupList RAB-InformationSetupList OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList OPTIONAL, Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL
} RadioBearerSetup-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received the UE behaviour -- is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } RadioBearerSetup-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } RadioBearerSetup-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-TPC-PowerOffsetPerRL-List DL-TPC-PowerOffsetPerRL-List } RadioBearerSetup-v5d0ext-IEs ::= --Radio Bearer IEs pdcp-ROHC-TargetMode } SEQUENCE { PDCP-ROHC-TargetMode OPTIONAL
OPTIONAL,
OPTIONAL
OPTIONAL
RadioBearerSetup-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo cipheringModeInfo activationTime new-U-RNTI
IntegrityProtectionModeInfo CipheringModeInfo ActivationTime U-RNTI
3GPP
Release 6
803
3GPP TS 25.331 V6.23.0 (2009-09)
----
--
--
new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList OPTIONAL, rab-InformationSetupList RAB-InformationSetupList-r4 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL
} RadioBearerSetup-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList-r5 OPTIONAL, rab-InformationSetupList RAB-InformationSetupList-r5 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList-r5 OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL,
3GPP
Release 6
dummy2 }, tdd
804
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
DRAC-StaticInformationList
NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r5 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } RadioBearerSetup-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, timingMaintainedSynchInd TimingMaintainedSynchInd OPTIONAL, -- Radio bearer IEs rab-InformationSetupList RAB-InformationSetupList-r6-ext OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL } RadioBearerSetup-r6-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, newPrimary-E-RNTI E-RNTI OPTIONAL, newSecondary-E-RNTI E-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo-r6 OPTIONAL, specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList-r6 OPTIONAL, rab-InformationSetupList RAB-InformationSetupList-r6 OPTIONAL, rab-InformationReconfigList RAB-InformationReconfigList OPTIONAL, rb-InformationReconfigList RB-InformationReconfigList-r6 OPTIONAL, rb-InformationAffectedList RB-InformationAffectedList-r6 OPTIONAL, dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, pdcp-ROHC-TargetMode PDCP-ROHC-TargetMode OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-deletedTransChInfoList UL-DeletedTransChInfoList-r6 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-DeletedTransChInfoList DL-DeletedTransChInfoList-r5 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL },
3GPP
Release 6
805
3GPP TS 25.331 V6.23.0 (2009-09)
-- dummy is not used in this version of the specification -- if it is sent, the UE behaviour is unspecified. dummy SEQUENCE { rab-Info RAB-Info-r6, defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r6, rb-InformationChangedList RB-InformationChangedList-r6 powerOffsetInfoShort PowerOffsetInfoShort } }, -- Physical channel IEs frequencyInfo maxAllowedUL-TX-Power ul-DPCH-Info ul-EDCH-Information dl-HSPDSCH-Information dl-CommonInformation dl-InformationPerRL-List -- MBMS IEs mbms-PL-ServiceRestrictInfo }
OPTIONAL,
FrequencyInfo MaxAllowedUL-TX-Power UL-DPCH-Info-r6 UL-EDCH-Information-r6 DL-HSPDSCH-Information-r6 DL-CommonInformation-r6 DL-InformationPerRL-List-r6 MBMS-PL-ServiceRestrictInfo-r6
RadioBearerSetup-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext DL-InformationPerRL-List-v6b0ext OPTIONAL, -- MBMS IEs -- The order of the RABs in IE rab-InformationSetupListExt is the same as -- in IE rab-InformationSetupList that is included in this message rab-InformationSetupListExt RAB-InformationSetupList-v6b0ext OPTIONAL } -- *************************************************** --- RADIO BEARER SETUP COMPLETE --- *************************************************** RadioBearerSetupComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo OPTIONAL, -- TABULAR: UL-TimingAdvance is applicable for TDD mode only. ul-TimingAdvance UL-TimingAdvance OPTIONAL, start-Value START-Value OPTIONAL, -- Radio bearer IEs count-C-ActivationTime ActivationTime OPTIONAL, -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList OPTIONAL, ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerSetupComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RADIO BEARER SETUP FAILURE --- *************************************************** RadioBearerSetupFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, -- Radio bearer IEs potentiallySuccesfulBearerList RB-IdentityList OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions radioBearerSetupFailure-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --
3GPP
Release 6
806
3GPP TS 25.331 V6.23.0 (2009-09)
-- RRC CONNECTION REJECT --- *************************************************** RRCConnectionReject ::= CHOICE { r3 SEQUENCE { rrcConnectionReject-r3 RRCConnectionReject-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionReject-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionReject-v690ext RRCConnectionReject-v690ext-IEs, v6f0NonCriticalExtensions SEQUENCE { rrcConnectionReject-v6f0ext RRCConnectionReject-v6f0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { initialUE-Identity InitialUE-Identity, rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } RRCConnectionReject-r3-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs initialUE-Identity InitialUE-Identity, rrc-TransactionIdentifier RRC-TransactionIdentifier, rejectionCause RejectionCause, waitTime WaitTime, redirectionInfo RedirectionInfo OPTIONAL } RRCConnectionReject-v690ext-IEs ::= SEQUENCE { redirectionInfo-v690ext GSM-TargetCellInfoList } RRCConnectionReject-v6f0ext-IEs ::= SEQUENCE { countingCompletion ENUMERATED { true } } -- *************************************************** --- RRC CONNECTION RELEASE --- *************************************************** RRCConnectionRelease ::= CHOICE { r3 SEQUENCE { rrcConnectionRelease-r3 RRCConnectionRelease-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionRelease-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionRelease-v690ext RRCConnectionRelease-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { rrcConnectionRelease-r4 RRCConnectionRelease-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-6 rrcConnectionRelease-r4-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionRelease-v690ext RRCConnectionRelease-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {}
OPTIONAL
OPTIONAL
3GPP
Release 6
} } }
807
3GPP TS 25.331 V6.23.0 (2009-09)
RRCConnectionRelease-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- n-308 is conditional on the UE state n-308 N-308 releaseCause ReleaseCause, rplmn-information Rplmn-Information } RRCConnectionRelease-r4-IEs ::= SEQUENCE { -- User equipment IEs -- n-308 is conditional on the UE state. n-308 N-308 releaseCause ReleaseCause, rplmn-information Rplmn-Information-r4 } RRCConnectionRelease-v690ext-IEs ::= SEQUENCE { redirectionInfo-v690ext RedirectionInfo-r6 } -- *************************************************** --- RRC CONNECTION RELEASE for CCCH --- ***************************************************
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
OPTIONAL
RRCConnectionRelease-CCCH ::= CHOICE { r3 SEQUENCE { rrcConnectionRelease-CCCH-r3 RRCConnectionRelease-CCCH-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionRelease-CCCH-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionRelease-v690ext RRCConnectionRelease-CCCH-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { u-RNTI U-RNTI, rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { rrcConnectionRelease-CCCH-r4 RRCConnectionRelease-CCCH-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 rrcConnectionRelease-CCCH-r4-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionRelease-v690ext RRCConnectionRelease-CCCH-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE { -- TABULAR: CHOICE IdentityType (U-RNTI, GroupIdentity) is replaced with the -- optional element groupIdentity, since the U-RNTI is mandatory in ASN.1. -- In case CHOICE IdentityType is equal to GroupIdentity the value of the U-RNTI -- shall be ignored by a UE complying with this version of the message. groupIdentity SEQUENCE ( SIZE (1 .. maxURNTI-Group) ) OF GroupReleaseInformation OPTIONAL, criticalExtensions CHOICE { r5 SEQUENCE { rrcConnectionRelease-CCCH-r5 RRCConnectionRelease-CCCH-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 rrcConnectionRelease-CCCH-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionRelease-v690ext RRCConnectionRelease-CCCH-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } }
3GPP
Release 6
} } }
808
3GPP TS 25.331 V6.23.0 (2009-09)
RRCConnectionRelease-CCCH-r3-IEs ::= SEQUENCE { -- User equipment IEs u-RNTI U-RNTI, -- The rest of the message is identical to the one sent on DCCH. rrcConnectionRelease RRCConnectionRelease-r3-IEs } RRCConnectionRelease-CCCH-r4-IEs ::= SEQUENCE { -- The rest of the message is identical to the one sent on DCCH. rrcConnectionRelease RRCConnectionRelease-r4-IEs } -- The R5 and R4 sequence of IEs are identical in this message RRCConnectionRelease-CCCH-r5-IEs ::= RRCConnectionRelease-CCCH-r4-IEs -- The R6 non-critical extension is identical to the one sent on DCCH. RRCConnectionRelease-CCCH-v690ext-IEs ::= RRCConnectionRelease-v690ext-IEs -- *************************************************** --- RRC CONNECTION RELEASE COMPLETE --- *************************************************** RRCConnectionReleaseComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, errorIndication FailureCauseWithProtErr laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionReleaseComplete-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- RRC CONNECTION REQUEST --- *************************************************** RRCConnectionRequest ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs initialUE-Identity InitialUE-Identity, establishmentCause EstablishmentCause, -- protocolErrorIndicator is MD, but for compactness reasons no default value -- has been assigned to it. protocolErrorIndicator ProtocolErrorIndicator, -- Measurement IEs measuredResultsOnRACH MeasuredResultsOnRACH OPTIONAL, -- Non critical Extensions v3d0NonCriticalExtensions SEQUENCE { rRCConnectionRequest-v3d0ext RRCConnectionRequest-v3d0ext-IEs, -- Reserved for future non critical extension v4b0NonCriticalExtensions SEQUENCE { rrcConnectionRequest-v4b0ext RRCConnectionRequest-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { rrcConnectionRequest-v590ext RRCConnectionRequest-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { rrcConnectionRequest-v690ext RRCConnectionRequest-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { rrcConnectionRequest-v6b0ext RRCConnectionRequest-v6b0ext-IEs, v6e0NonCriticalExtensions SEQUENCE { rrcConnectionRequest-v6e0ext RRCConnectionRequest-v6e0ext-IEs, -- Reserved for future non critical extension nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }
OPTIONAL,
OPTIONAL,
3GPP
Release 6
809
3GPP TS 25.331 V6.23.0 (2009-09)
RRCConnectionRequest-v3d0ext-IEs ::= SEQUENCE { -- User equipment IEs uESpecificBehaviourInformation1idle UESpecificBehaviourInformation1idle } RRCConnectionRequest-v4b0ext-IEs ::= -- User equipment IEs accessStratumReleaseIndicator } RRCConnectionRequest-v590ext-IEs ::= -- User equipment IEs predefinedConfigStatusInfo } RRCConnectionRequest-v690ext-IEs ::= -- User equipment IEs ueCapabilityIndication -- Measurement IEs measuredResultsOnRACHinterFreq domainIndicator cs-domain csCallType }, ps-domain } } RRCConnectionRequest-v6b0ext-IEs ::= -- MBMS IEs mbmsSelectedServices } RRCConnectionRequest-v6e0ext-IEs ::= -- User equipment IEs supportForFDPCH } SEQUENCE { AccessStratumReleaseIndicator
OPTIONAL
SEQUENCE { BOOLEAN
SEQUENCE { ENUMERATED { hsdch, hsdch-edch } OPTIONAL,
MeasuredResultsOnRACHinterFreq OPTIONAL, CHOICE { SEQUENCE { ENUMERATED {speech, video, other, spare } NULL
SEQUENCE { MBMS-SelectedServicesShort OPTIONAL
SEQUENCE { ENUMERATED { true } OPTIONAL
-- *************************************************** --- RRC CONNECTION SETUP --- *************************************************** RRCConnectionSetup ::= CHOICE { r3 SEQUENCE { rrcConnectionSetup-r3 RRCConnectionSetup-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionSetup-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v4b0ext RRCConnectionSetup-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v590ext RRCConnectionSetup-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v690ext RRCConnectionSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { initialUE-Identity InitialUE-Identity, rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { rrcConnectionSetup-r4 RRCConnectionSetup-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 rrcConnectionSetup-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v590ext RRCConnectionSetup-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v690ext RRCConnectionSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL
3GPP
Release 6
} OPTIONAL OPTIONAL
810
3GPP TS 25.331 V6.23.0 (2009-09)
}, criticalExtensions CHOICE { r5 SEQUENCE { rrcConnectionSetup-r5 RRCConnectionSetup-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 rrcConnectionSetup-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v690ext RRCConnectionSetup-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { rrcConnectionSetup-r6 RRCConnectionSetup-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 rrcConnectionSetup-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { rrcConnectionSetup-v6b0ext RRCConnectionSetup-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } RRCConnectionSetup-r3-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs initialUE-Identity InitialUE-Identity, rrc-TransactionIdentifier RRC-TransactionIdentifier, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI, new-c-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient, -- TABULAR: If capabilityUpdateRequirement is not present, the default value -- defined in 10.3.3.2 shall be used. capabilityUpdateRequirement CapabilityUpdateRequirement OPTIONAL, -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList2, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, -- NOTE: ul-AddReconfTransChInfoList should be optional in later versions of -- this message ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, -- NOTE: dl-AddReconfTransChInfoList should be optional in later versions -- of this message dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL } RRCConnectionSetup-v4b0ext-IEs ::= SEQUENCE { capabilityUpdateRequirement-r4-ext CapabilityUpdateRequirement-r4-ext -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } RRCConnectionSetup-v590ext-IEs ::= SEQUENCE { -- User equipment IEs systemSpecificCapUpdateReq SystemSpecificCapUpdateReq-v590ext -- Physical channel IEs dl-TPC-PowerOffsetPerRL-List DL-TPC-PowerOffsetPerRL-List
OPTIONAL,
OPTIONAL,
OPTIONAL
OPTIONAL, OPTIONAL
3GPP
Release 6
}
811
3GPP TS 25.331 V6.23.0 (2009-09)
RRCConnectionSetup-r4-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI, new-c-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient, -- TABULAR: If capabilityUpdateRequirement is not present, the default value -- defined in 10.3.3.2 shall be used. capabilityUpdateRequirement CapabilityUpdateRequirement-r4 OPTIONAL, -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList2, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r4 OPTIONAL } RRCConnectionSetup-r5-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI, new-c-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient, -- TABULAR: If capabilityUpdateRequirement is not present, the default value -- defined in 10.3.3.2 shall be used. capabilityUpdateRequirement CapabilityUpdateRequirement-r5 OPTIONAL, -- Specification mode information specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList2, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r5 } } } }, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, dl-CommonInformation DL-CommonInformation-r4 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5bis OPTIONAL } RRCConnectionSetup-v690ext-IEs ::= SEQUENCE { -- Physical Channel IEs beaconPLEst BEACON-PL-Est postVerificationPeriod ENUMERATED { true } }
OPTIONAL, OPTIONAL
RRCConnectionSetup-r6-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. activationTime ActivationTime OPTIONAL,
3GPP
Release 6
812
3GPP TS 25.331 V6.23.0 (2009-09)
new-U-RNTI U-RNTI, new-c-RNTI C-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, newPrimary-E-RNTI E-RNTI OPTIONAL, newSecondary-E-RNTI E-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient, -- TABULAR: If capabilityUpdateRequirement is not present, the default value -- defined in 10.3.3.2 shall be used. capabilityUpdateRequirement CapabilityUpdateRequirement-r5 OPTIONAL, -- Specification mode information specificationMode CHOICE { complete SEQUENCE { -- Radio bearer IEs srb-InformationSetupList SRB-InformationSetupList2-r6, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL }, preconfiguration SEQUENCE { -- All IEs that include an FDD/TDD choice are split in two IEs for this message, -- one for the FDD only elements and one for the TDD only elements, so that one -- FDD/TDD choice in this level is sufficient. preConfigMode CHOICE { predefinedConfigIdentity PredefinedConfigIdentity, defaultConfig SEQUENCE { defaultConfigMode DefaultConfigMode, defaultConfigIdentity DefaultConfigIdentity-r6 } } } }, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-DPCH-Info UL-DPCH-Info-r6 OPTIONAL, ul-EDCH-Information UL-EDCH-Information-r6 OPTIONAL, dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 OPTIONAL, dl-CommonInformation DL-CommonInformation-r6 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r6 OPTIONAL } RRCConnectionSetup-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext }
OPTIONAL
-- *************************************************** --- RRC CONNECTION SETUP COMPLETE --- *************************************************** RRCConnectionSetupComplete ::= SEQUENCE { -- TABULAR: Integrity protection shall not be performed on this message. -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, startList STARTList, ue-RadioAccessCapability UE-RadioAccessCapability OPTIONAL, -- Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList OPTIONAL, -- Non critical extensions v370NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v370ext RRCConnectionSetupComplete-v370ext, v380NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v380ext RRCConnectionSetupComplete-v380ext-IEs, -- Reserved for future non critical extension v3a0NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v3a0ext RRCConnectionSetupComplete-v3a0ext-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcConnectionSetupComplete-r3-add-ext BIT STRING (CONTAINING RRCConnectionSetupComplete-r3-add-ext-IEs) OPTIONAL, v3g0NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v3g0ext RRCConnectionSetupComplete-v3g0extIEs,
3GPP
Release 6
813
3GPP TS 25.331 V6.23.0 (2009-09)
v4b0NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v4b0ext RRCConnectionSetupComplete-v4b0extIEs, v590NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v590ext RRCConnectionSetupComplete-v590extIEs, v5c0NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v5c0ext RRCConnectionSetupComplete-v5c0extIEs, v690NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v690ext RRCConnectionSetupComplete-v690extIEs, nonCriticalExtensions OPTIONAL OPTIONAL OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL OPTIONAL } } SEQUENCE {}
} } }
RRCConnectionSetupComplete-v370ext ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v370ext UE-RadioAccessCapability-v370ext } RRCConnectionSetupComplete-v380ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v380ext UE-RadioAccessCapability-v380ext dl-PhysChCapabilityFDD-v380ext DL-PhysChCapabilityFDD-v380ext } RRCConnectionSetupComplete-v3a0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v3a0ext UE-RadioAccessCapability-v3a0ext } RRCConnectionSetupComplete-v3g0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v3g0ext UE-RadioAccessCapability-v3g0ext }
OPTIONAL
OPTIONAL,
OPTIONAL
OPTIONAL
RRCConnectionSetupComplete-r3-add-ext-IEs ::= SEQUENCE { rrcConnectionSetupComplete-v650ext RRCConnectionSetupComplete-v650ext-IEs OPTIONAL, v680NonCriticalExtensions SEQUENCE { rrcConnectionSetupComplete-v680ext RRCConnectionSetupComplete-v680ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } RRCConnectionSetupComplete-v4b0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v4b0ext UE-RadioAccessCapability-v4b0ext }
OPTIONAL
RRCConnectionSetupComplete-v590ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v590ext UE-RadioAccessCapability-v590ext OPTIONAL, -- Other IEs ue-RATSpecificCapability-v590ext InterRAT-UE-RadioAccessCapability-v590ext OPTIONAL } RRCConnectionSetupComplete-v5c0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v5c0ext UE-RadioAccessCapability-v5c0ext } RRCConnectionSetupComplete-v650ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v650ext UE-RadioAccessCapability-v650ext
OPTIONAL
3GPP
Release 6
}
814
3GPP TS 25.331 V6.23.0 (2009-09)
RRCConnectionSetupComplete-v680ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v680ext UE-RadioAccessCapability-v680ext } RRCConnectionSetupComplete-v690ext-IEs ::= SEQUENCE { -- User equipment IEs ueCapabilityContainer BIT STRING (CONTAINING UE-CapabilityContainer-IEs) OPTIONAL } -- *************************************************** --- RRC FAILURE INFO --- *************************************************** RRC-FailureInfo ::= CHOICE { r3 SEQUENCE { rRC-FailureInfo-r3 RRC-FailureInfo-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrc-FailureInfo-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } RRC-FailureInfo-r3-IEs ::= SEQUENCE { -- Non-RRC IEs failureCauseWithProtErr } -- *************************************************** --- RRC STATUS --- *************************************************** RRCStatus ::= SEQUENCE { -- Other IEs -- TABULAR: Identification of received message is nested in -- ProtocolErrorMoreInformation protocolErrorInformation ProtocolErrorMoreInformation, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions rrcStatus-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- SECURITY MODE COMMAND --- *************************************************** SecurityModeCommand ::= CHOICE { r3 SEQUENCE { securityModeCommand-r3 SecurityModeCommand-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions securityModeCommand-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } SecurityModeCommand-r3-IEs ::= SEQUENCE { -- TABULAR: Integrity protection shall always be performed on this message. -- User equipment IEs
FailureCauseWithProtErr
3GPP
Release 6
rrc-TransactionIdentifier securityCapability cipheringModeInfo integrityProtectionModeInfo -- Core network IEs cn-DomainIdentity -- Other IEs ue-SystemSpecificSecurityCap }
815
RRC-TransactionIdentifier, SecurityCapability, CipheringModeInfo IntegrityProtectionModeInfo CN-DomainIdentity, InterRAT-UE-SecurityCapList
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL, OPTIONAL,
OPTIONAL
-- *************************************************** --- SECURITY MODE COMPLETE --- *************************************************** SecurityModeComplete ::= SEQUENCE { -- TABULAR: Integrity protection shall always be performed on this message. -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo -- Radio bearer IEs rb-UL-CiphActivationTimeInfo RB-ActivationTimeInfoList laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions securityModeComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- SECURITY MODE FAILURE --- *************************************************** SecurityModeFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions securityModeFailure-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- SIGNALLING CONNECTION RELEASE --- *************************************************** SignallingConnectionRelease ::= CHOICE { r3 SEQUENCE { signallingConnectionRelease-r3 SignallingConnectionRelease-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions signallingConnectionRelease-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } SignallingConnectionRelease-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Core network IEs cn-DomainIdentity CN-DomainIdentity } -- *************************************************** --
OPTIONAL, OPTIONAL,
3GPP
Release 6
816
3GPP TS 25.331 V6.23.0 (2009-09)
-- SIGNALLING CONNECTION RELEASE INDICATION --- *************************************************** SignallingConnectionReleaseIndication ::= SEQUENCE { -- Core network IEs cn-DomainIdentity CN-DomainIdentity, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions signallingConnectionReleaseIndication-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- SYSTEM INFORMATION for BCH --- *************************************************** SystemInformation-BCH ::= SEQUENCE { -- Other information elements sfn-Prime payload noSegment firstSegment subsequentSegment lastSegmentShort lastAndFirst lastSegmentShort firstSegment }, lastAndComplete lastSegmentShort completeSIB-List }, lastAndCompleteAndFirst lastSegmentShort completeSIB-List firstSegment }, completeSIB-List completeAndFirst completeSIB-List firstSegment }, completeSIB lastSegment spare5 spare4 spare3 spare2 spare1 } }
OPTIONAL,
SFN-Prime, CHOICE { NULL, FirstSegment, SubsequentSegment, LastSegmentShort, SEQUENCE { LastSegmentShort, FirstSegmentShort SEQUENCE { LastSegmentShort, CompleteSIB-List SEQUENCE { LastSegmentShort, CompleteSIB-List, FirstSegmentShort CompleteSIB-List, SEQUENCE { CompleteSIB-List, FirstSegmentShort CompleteSIB, LastSegment, NULL, NULL, NULL, NULL, NULL
-- *************************************************** --- SYSTEM INFORMATION for FACH --- *************************************************** SystemInformation-FACH ::= SEQUENCE { -- Other information elements payload noSegment firstSegment subsequentSegment lastSegmentShort lastAndFirst lastSegmentShort firstSegment }, lastAndComplete lastSegmentShort completeSIB-List }, lastAndCompleteAndFirst
CHOICE { NULL, FirstSegment, SubsequentSegment, LastSegmentShort, SEQUENCE { LastSegmentShort, FirstSegmentShort SEQUENCE { LastSegmentShort, CompleteSIB-List SEQUENCE {
3GPP
Release 6
lastSegmentShort completeSIB-List firstSegment }, completeSIB-List completeAndFirst completeSIB-List firstSegment }, completeSIB lastSegment spare5 spare4 spare3 spare2 spare1 } }
817
LastSegmentShort, CompleteSIB-List, FirstSegmentShort CompleteSIB-List, SEQUENCE { CompleteSIB-List, FirstSegmentShort CompleteSIB, LastSegment, NULL, NULL, NULL, NULL, NULL
3GPP TS 25.331 V6.23.0 (2009-09)
-- *************************************************** --- First segment --- *************************************************** FirstSegment ::= -- Other information elements sib-Type seg-Count sib-Data-fixed } SEQUENCE { SIB-Type, SegCount, SIB-Data-fixed
-- *************************************************** --- First segment (short) --- *************************************************** FirstSegmentShort ::= -- Other information elements sib-Type seg-Count sib-Data-variable } SEQUENCE { SIB-Type, SegCount, SIB-Data-variable
-- *************************************************** --- Subsequent segment --- *************************************************** SubsequentSegment ::= -- Other information elements sib-Type segmentIndex sib-Data-fixed } SEQUENCE { SIB-Type, SegmentIndex, SIB-Data-fixed
-- *************************************************** --- Last segment --- *************************************************** LastSegment ::= SEQUENCE { -- Other information elements sib-Type SIB-Type, segmentIndex SegmentIndex, -- For sib-Data-fixed, in case the SIB data is less than 222 bits, padding -- shall be used. The same padding bits shall be used as defined in clause 12.1 sib-Data-fixed SIB-Data-fixed } LastSegmentShort ::= -- Other information elements sib-Type segmentIndex sib-Data-variable SEQUENCE { SIB-Type, SegmentIndex, SIB-Data-variable
3GPP
Release 6
}
818
3GPP TS 25.331 V6.23.0 (2009-09)
-- *************************************************** --- Complete SIB --- *************************************************** CompleteSIB-List ::= SEQUENCE (SIZE (1..maxSIBperMsg)) OF CompleteSIBshort
CompleteSIB ::= SEQUENCE { -- Other information elements sib-Type SIB-Type, -- For sib-Data-fixed, in case the SIB data is less than 226 bits, padding -- shall be used. The same padding bits shall be used as defined in clause 12.1 sib-Data-fixed BIT STRING (SIZE (226)) } CompleteSIBshort ::= -- Other information elements sib-Type sib-Data-variable } SEQUENCE { SIB-Type, SIB-Data-variable
-- *************************************************** --- SYSTEM INFORMATION CHANGE INDICATION --- *************************************************** SystemInformationChangeIndication ::= SEQUENCE { -- Other IEs bcch-ModificationInfo BCCH-ModificationInfo, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions systemInformationChangeIndication-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- TRANSPORT CHANNEL RECONFIGURATION --- *************************************************** TransportChannelReconfiguration ::= CHOICE { r3 SEQUENCE { transportChannelReconfiguration-r3 TransportChannelReconfiguration-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v3a0ext TransportChannelReconfiguration-v3a0ext, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions transportChannelReconfiguration-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v4b0ext TransportChannelReconfiguration-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v590ext TransportChannelReconfiguration-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v690ext TransportChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { transportChannelReconfiguration-r4
OPTIONAL,
3GPP
Release 6
819
3GPP TS 25.331 V6.23.0 (2009-09)
TransportChannelReconfiguration-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 transportChannelReconfiguration-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v590ext TransportChannelReconfiguration-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v690ext TransportChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { transportChannelReconfiguration-r5 TransportChannelReconfiguration-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 transportChannelReconfiguration-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v690ext TransportChannelReconfiguration-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { transportChannelReconfiguration-r6 TransportChannelReconfiguration-r6-IEs, -- Container for adding non critical extensions after freezing REL-7 transportChannelReconfiguration-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { transportChannelReconfiguration-v6b0ext TransportChannelReconfiguration-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } } TransportChannelReconfiguration-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL,
3GPP
Release 6
820
3GPP TS 25.331 V6.23.0 (2009-09)
maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-CommonInformation DL-CommonInformation OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List OPTIONAL } TransportChannelReconfiguration-v3a0ext ::= SEQUENCE { -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL } TransportChannelReconfiguration-v4b0ext-IEs ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-UL -- The order of the RLs in IE cell-id-PerRL-List is the same as -- in IE DL-InformationPerRL-List included in this message cell-id-PerRL-List CellIdentity-PerRL-List } TransportChannelReconfiguration-v590ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-TPC-PowerOffsetPerRL-List DL-TPC-PowerOffsetPerRL-List }
OPTIONAL,
OPTIONAL
OPTIONAL
TransportChannelReconfiguration-r4-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r4 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL
3GPP
Release 6
}, dl-CommonInformation dl-InformationPerRL-List }
821
3GPP TS 25.331 V6.23.0 (2009-09)
DL-CommonInformation-r4 DL-InformationPerRL-List-r4
OPTIONAL, OPTIONAL
TransportChannelReconfiguration-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, cipheringModeInfo CipheringModeInfo OPTIONAL, activationTime ActivationTime OPTIONAL, new-U-RNTI U-RNTI OPTIONAL, new-C-RNTI C-RNTI OPTIONAL, -- The IE new-DSCH-RNTI should not be included in FDD mode, and if received -- the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI OPTIONAL, new-H-RNTI H-RNTI OPTIONAL, rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient OPTIONAL, -- Core network IEs cn-InformationInfo CN-InformationInfo OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, -- Physical channel IEs frequencyInfo FrequencyInfo OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, ul-ChannelRequirement UL-ChannelRequirement-r5 OPTIONAL, modeSpecificPhysChInfo CHOICE { fdd SEQUENCE { -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy DL-PDSCH-Information OPTIONAL }, tdd NULL }, dl-HSPDSCH-Information DL-HSPDSCH-Information OPTIONAL, dl-CommonInformation DL-CommonInformation-r5 OPTIONAL, dl-InformationPerRL-List DL-InformationPerRL-List-r5 OPTIONAL } TransportChannelReconfiguration-v690ext-IEs ::= SEQUENCE { -- User Equipment IEs delayRestrictionFlag DelayRestrictionFlag OPTIONAL, -- Core network IEs primary-plmn-Identity PLMN-Identity OPTIONAL, -- Physical channel IEs -- The IE harq-Preamble-Mode should not be used in the r3 and r4 versions of the message -- If included in the r3 or r4 version of the message, the UE should ignore the IE harq-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, beaconPLEst BEACON-PL-Est OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL, dhs-sync DHS-Sync OPTIONAL, timingMaintainedSynchInd TimingMaintainedSynchInd OPTIONAL, -- MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6 OPTIONAL } TransportChannelReconfiguration-r6-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo activationTime ActivationTime delayRestrictionFlag DelayRestrictionFlag
3GPP
Release 6
822
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL, OPTIONAL,
-----
--
-}
new-U-RNTI U-RNTI new-C-RNTI C-RNTI -- The IE new-DSCH-RNTI should not be included in FDD mode, -- and if received the UE behaviour is unspecified new-DSCH-RNTI DSCH-RNTI new-H-RNTI H-RNTI newPrimary-E-RNTI E-RNTI newSecondary-E-RNTI E-RNTI rrc-StateIndicator RRC-StateIndicator, utran-DRX-CycleLengthCoeff UTRAN-DRX-CycleLengthCoefficient Core network IEs cn-InformationInfo CN-InformationInfo-r6 UTRAN mobility IEs ura-Identity URA-Identity Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo-r5 Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 ul-AddReconfTransChInfoList UL-AddReconfTransChInfoList-r6 dl-CommonTransChInfo DL-CommonTransChInfo-r4 dl-AddReconfTransChInfoList DL-AddReconfTransChInfoList-r5 Physical channel IEs frequencyInfo FrequencyInfo maxAllowedUL-TX-Power MaxAllowedUL-TX-Power ul-DPCH-Info UL-DPCH-Info-r6 ul-EDCH-Information UL-EDCH-Information-r6 dl-HSPDSCH-Information DL-HSPDSCH-Information-r6 dl-CommonInformation DL-CommonInformation-r6 dl-InformationPerRL-List DL-InformationPerRL-List-r6 MBMS IEs mbms-PL-ServiceRestrictInfo MBMS-PL-ServiceRestrictInfo-r6
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
TransportChannelReconfiguration-v6b0ext-IEs ::= SEQUENCE { -- Physical channel IEs dl-InformationPerRL-List-v6b0ext DL-InformationPerRL-List-v6b0ext } -- *************************************************** --- TRANSPORT CHANNEL RECONFIGURATION COMPLETE --- ***************************************************
OPTIONAL
TransportChannelReconfigurationComplete ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo OPTIONAL, -- TABULAR: UL-TimingAdvance is applicable for TDD mode only. ul-TimingAdvance UL-TimingAdvance OPTIONAL, -- Radio bearer IEs count-C-ActivationTime ActivationTime OPTIONAL, -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList OPTIONAL, ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions transportChannelReconfigurationComplete-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- TRANSPORT CHANNEL RECONFIGURATION FAILURE --- *************************************************** TransportChannelReconfigurationFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions transportChannelReconfigurationFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL
OPTIONAL,
3GPP
Release 6
}
823
3GPP TS 25.331 V6.23.0 (2009-09)
-- ********************************************************* --- TRANSPORT FORMAT COMBINATION CONTROL in AM or UM RLC mode --- ********************************************************* TransportFormatCombinationControl ::= SEQUENCE { -- rrc-TransactionIdentifier is always included in this version of the specification rrc-TransactionIdentifier RRC-TransactionIdentifier OPTIONAL, modeSpecificInfo CHOICE { fdd NULL, tdd SEQUENCE { tfcs-ID TFCS-Identity OPTIONAL } }, dpch-TFCS-InUplink TFC-Subset, activationTimeForTFCSubset ActivationTime OPTIONAL, tfc-ControlDuration TFC-ControlDuration OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions transportFormatCombinationControl-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- TRANSPORT FORMAT COMBINATION CONTROL FAILURE --- *************************************************** TransportFormatCombinationControlFailure ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions transportFormatCombinationControlFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- UE CAPABILITY ENQUIRY --- *************************************************** UECapabilityEnquiry ::= CHOICE { r3 SEQUENCE { ueCapabilityEnquiry-r3 UECapabilityEnquiry-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions ueCapabilityEnquiry-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { ueCapabilityEnquiry-v4b0ext UECapabilityEnquiry-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { ueCapabilityEnquiry-v590ext UECapabilityEnquiry-v590ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } UECapabilityEnquiry-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, capabilityUpdateRequirement CapabilityUpdateRequirement } UECapabilityEnquiry-v4b0ext-IEs ::= SEQUENCE {
OPTIONAL,
3GPP
Release 6
capabilityUpdateRequirement-r4-ext }
824
3GPP TS 25.331 V6.23.0 (2009-09)
CapabilityUpdateRequirement-r4-ext
UECapabilityEnquiry-v590ext-IEs ::= SEQUENCE { systemSpecificCapUpdateReq SystemSpecificCapUpdateReq-v590ext } -- *************************************************** --- UE CAPABILITY INFORMATION --- *************************************************** UECapabilityInformation ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier OPTIONAL, ue-RadioAccessCapability UE-RadioAccessCapability OPTIONAL, -- Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList OPTIONAL, v370NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v370ext UECapabilityInformation-v370ext, v380NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v380ext UECapabilityInformation-v380ext-IEs, v3a0NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v3a0ext UECapabilityInformation-v3a0ext-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions ueCapabilityInformation-r3-add-ext BIT STRING (CONTAINING UECapabilityInformation-r3-add-ext-IEs) OPTIONAL, -- Reserved for future non critical extension v4b0NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v4b0ext UECapabilityInformation-v4b0ext, v590NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v590ext UECapabilityInformation-v590ext, v5c0NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v5c0ext UECapabilityInformation-v5c0ext, v690NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v690ext UECapabilityInformation-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } UECapabilityInformation-v370ext ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v370ext }
UE-RadioAccessCapability-v370ext
OPTIONAL
UECapabilityInformation-v380ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v380ext UE-RadioAccessCapability-v380ext dl-PhysChCapabilityFDD-v380ext DL-PhysChCapabilityFDD-v380ext } UECapabilityInformation-v3a0ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v3a0ext UE-RadioAccessCapability-v3a0ext }
OPTIONAL,
OPTIONAL
UECapabilityInformation-r3-add-ext-IEs ::= SEQUENCE { ueCapabilityInformation-v650ext UECapabilityInformation-v650ext-IEs OPTIONAL, v680NonCriticalExtensions SEQUENCE { ueCapabilityInformation-v680ext UECapabilityInformation-v680ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } UECapabilityInformation-v4b0ext ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v4b0ext
UE-RadioAccessCapability-v4b0ext
OPTIONAL
3GPP
Release 6
}
825
3GPP TS 25.331 V6.23.0 (2009-09)
UECapabilityInformation-v590ext ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v3g0ext UE-RadioAccessCapability-v3g0ext ue-RadioAccessCapability-v590ext UE-RadioAccessCapability-v590ext -- Other IEs ue-RATSpecificCapability-v590ext InterRAT-UE-RadioAccessCapability-v590ext } UECapabilityInformation-v5c0ext ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v5c0ext }
UE-RadioAccessCapability-v5c0ext
OPTIONAL
UECapabilityInformation-v650ext-IEs ::= SEQUENCE { ue-RadioAccessCapability-v650ext UE-RadioAccessCapability-v650ext } UECapabilityInformation-v680ext-IEs ::= SEQUENCE { -- User equipment IEs ue-RadioAccessCapability-v680ext UE-RadioAccessCapability-v680ext } UECapabilityInformation-v690ext-IEs ::= SEQUENCE { -- User equipment IEs ueCapabilityContainer BIT STRING (CONTAINING UE-CapabilityContainer-IEs) OPTIONAL } -- *************************************************** --- UE CAPABILITY INFORMATION CONFIRM --- *************************************************** UECapabilityInformationConfirm ::= CHOICE { r3 SEQUENCE { ueCapabilityInformationConfirm-r3 UECapabilityInformationConfirm-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions ueCapabilityInformationConfirm-r3-add-ext BIT STRING OPTIONAL, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions SEQUENCE {} } } UECapabilityInformationConfirm-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier } -- *************************************************** --- UPLINK DIRECT TRANSFER --- *************************************************** UplinkDirectTransfer ::= SEQUENCE { -- Core network IEs cn-DomainIdentity CN-DomainIdentity, nas-Message NAS-Message, -- Measurement IEs measuredResultsOnRACH MeasuredResultsOnRACH OPTIONAL, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions uplinkDirectTransfer-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { uplinkDirectTransfer-v690ext UplinkDirectTransfer-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }
3GPP
Release 6
826
3GPP TS 25.331 V6.23.0 (2009-09)
UplinkDirectTransfer-v690ext-IEs ::= SEQUENCE { -- Measurement IEs measuredResultsOnRACHinterFreq MeasuredResultsOnRACHinterFreq } -- *************************************************** --- UPLINK PHYSICAL CHANNEL CONTROL --- ***************************************************
OPTIONAL
UplinkPhysicalChannelControl ::= CHOICE { r3 SEQUENCE { uplinkPhysicalChannelControl-r3 UplinkPhysicalChannelControl-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions uplinkPhysicalChannelControl-r3-add-ext BIT STRING OPTIONAL, v4b0NonCriticalExtensions SEQUENCE { uplinkPysicalChannelControl-v4b0ext UplinkPhysicalChannelControl-v4b0ext-IEs, -- Extension mechanism for non-release 4 information noncriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r4 SEQUENCE { uplinkPhysicalChannelControl-r4 UplinkPhysicalChannelControl-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { -- Container for adding non critical extensions after freezing REL-5 uplinkPhysicalChannelControl-r4-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { uplinkPhysicalChannelControl-v690ext UplinkPhysicalChannelControlv690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r5 SEQUENCE { uplinkPhysicalChannelControl-r5 UplinkPhysicalChannelControl-r5-IEs, -- Container for adding non critical extensions after freezing REL-6 uplinkPhysicalChannelControl-r5-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { uplinkPhysicalChannelControl-v690ext UplinkPhysicalChannelControl-v690ext-IEs, v6a0NonCriticalExtensions SEQUENCE { uplinkPhysicalChannelControl-v6a0ext UplinkPhysicalChannelControl-v6a0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } UplinkPhysicalChannelControl-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, -- Physical channel IEs ccTrCH-PowerControlInfo CCTrCH-PowerControlInfo timingAdvance UL-TimingAdvanceControl alpha Alpha specialBurstScheduling SpecialBurstScheduling prach-ConstantValue ConstantValueTdd pusch-ConstantValue ConstantValueTdd }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
UplinkPhysicalChannelControl-v4b0ext-IEs ::= SEQUENCE { -- In case of TDD, openLoopPowerControl-IPDL-TDD is included instead of IE -- up-IPDL-Parameters in up-OTDOA-AssistanceData openLoopPowerControl-IPDL-TDD OpenLoopPowerControl-IPDL-TDD-r4 OPTIONAL }
3GPP
Release 6
827
3GPP TS 25.331 V6.23.0 (2009-09)
UplinkPhysicalChannelControl-r4-IEs ::= SEQUENCE { -- Physical channel IEs ccTrCH-PowerControlInfo CCTrCH-PowerControlInfo-r4 OPTIONAL, specialBurstScheduling SpecialBurstScheduling OPTIONAL, tddOption CHOICE { tdd384 SEQUENCE { timingAdvance UL-TimingAdvanceControl-r4 OPTIONAL, alpha Alpha OPTIONAL, prach-ConstantValue ConstantValueTdd OPTIONAL, pusch-ConstantValue ConstantValueTdd OPTIONAL, openLoopPowerControl-IPDL-TDD OpenLoopPowerControl-IPDL-TDD-r4 OPTIONAL }, tdd128 SEQUENCE { ul-SynchronisationParameters UL-SynchronisationParameters-r4 OPTIONAL } } } UplinkPhysicalChannelControl-r5-IEs ::= SEQUENCE { -- Physical channel IEs ccTrCH-PowerControlInfo CCTrCH-PowerControlInfo-r5 OPTIONAL, specialBurstScheduling SpecialBurstScheduling OPTIONAL, tddOption CHOICE { tdd384 SEQUENCE { timingAdvance UL-TimingAdvanceControl-r4 OPTIONAL, alpha Alpha OPTIONAL, prach-ConstantValue ConstantValueTdd OPTIONAL, pusch-ConstantValue ConstantValueTdd OPTIONAL, openLoopPowerControl-IPDL-TDD OpenLoopPowerControl-IPDL-TDD-r4 OPTIONAL, hs-SICH-PowerControl HS-SICH-Power-Control-Info-TDD384 OPTIONAL }, tdd128 SEQUENCE { ul-SynchronisationParameters UL-SynchronisationParameters-r4 OPTIONAL } } } UplinkPhysicalChannelControl-v690ext-IEs ::= SEQUENCE { -- Physical Channel IEs beaconPLEst BEACON-PL-Est } UplinkPhysicalChannelControl-v6a0ext-IEs ::= SEQUENCE { -- Physical Channel IEs desired-HS-SICH-PowerLevel INTEGER (-120..-58) tpc-Step-Size ENUMERATED { s1, s2, s3, spare1 } } -- *************************************************** --- URA UPDATE --- *************************************************** URAUpdate ::= SEQUENCE { -- User equipment IEs u-RNTI ura-UpdateCause protocolErrorIndicator laterNonCriticalExtensions -- Container for additional uraUpdate-r3-add-ext nonCriticalExtensions } OPTIONAL }
OPTIONAL
OPTIONAL, OPTIONAL
U-RNTI, URA-UpdateCause, ProtocolErrorIndicatorWithMoreInfo, SEQUENCE { R99 extensions BIT STRING OPTIONAL, SEQUENCE {} OPTIONAL
-- *************************************************** --- URA UPDATE CONFIRM --- *************************************************** URAUpdateConfirm ::= CHOICE { r3 SEQUENCE { uraUpdateConfirm-r3 URAUpdateConfirm-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions uraUpdateConfirm-r3-add-ext BIT STRING OPTIONAL,
3GPP
Release 6
v690NonCriticalExtensions uraUpdateConfirm-v690ext nonCriticalExtensions } OPTIONAL OPTIONAL
828
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { URAUpdateConfirm-v690ext-IEs, SEQUENCE {} OPTIONAL
} }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r5 SEQUENCE { uraUpdateConfirm-r5 URAUpdateConfirm-r5-IEs, v690NonCriticalExtensions SEQUENCE { uraUpdateConfirm-v690ext URAUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } URAUpdateConfirm-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier integrityProtectionModeInfo cipheringModeInfo new-U-RNTI new-C-RNTI rrc-StateIndicator utran-DRX-CycleLengthCoeff -- CN information elements cn-InformationInfo -- UTRAN mobility IEs ura-Identity -- Radio bearer IEs dl-CounterSynchronisationInfo } URAUpdateConfirm-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo cipheringModeInfo new-U-RNTI new-C-RNTI rrc-StateIndicator utran-DRX-CycleLengthCoeff -- CN information elements cn-InformationInfo -- UTRAN mobility IEs ura-Identity -- Radio bearer IEs dl-CounterSynchronisationInfo }
RRC-TransactionIdentifier, IntegrityProtectionModeInfo CipheringModeInfo U-RNTI C-RNTI RRC-StateIndicator, UTRAN-DRX-CycleLengthCoefficient CN-InformationInfo URA-Identity DL-CounterSynchronisationInfo
IntegrityProtectionModeInfo CipheringModeInfo U-RNTI C-RNTI RRC-StateIndicator, UTRAN-DRX-CycleLengthCoefficient CN-InformationInfo URA-Identity DL-CounterSynchronisationInfo-r5
URAUpdateConfirm-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity PLMN-Identity } -- *************************************************** --- URA UPDATE CONFIRM for CCCH --- ***************************************************
OPTIONAL
URAUpdateConfirm-CCCH ::= CHOICE { r3 SEQUENCE { uraUpdateConfirm-CCCH-r3 URAUpdateConfirm-CCCH-r3-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions uraUpdateConfirm-CCCH-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { uraUpdateConfirm-v690ext URAUpdateConfirm-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE {
3GPP
Release 6
u-RNTI rrc-TransactionIdentifier criticalExtensions } }
829
U-RNTI, RRC-TransactionIdentifier, SEQUENCE {}
3GPP TS 25.331 V6.23.0 (2009-09)
URAUpdateConfirm-CCCH-r3-IEs ::= SEQUENCE { -- User equipment IEs u-RNTI U-RNTI, -- The rest of the message is identical to the one sent on DCCH. uraUpdateConfirm URAUpdateConfirm-r3-IEs } -- *************************************************** --- UTRAN MOBILITY INFORMATION --- *************************************************** UTRANMobilityInformation ::= CHOICE { r3 SEQUENCE { utranMobilityInformation-r3 UTRANMobilityInformation-r3-IEs, v3a0NonCriticalExtensions SEQUENCE { utranMobilityInformation-v3a0ext UTRANMobilityInformation-v3a0ext-IEs, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions utranMobilityInformation-r3-add-ext BIT STRING OPTIONAL, v690NonCriticalExtensions SEQUENCE { utranMobilityInformation-v690ext UtranMobilityInformation-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, later-than-r3 SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { r5 SEQUENCE { utranMobilityInformation-r5 UTRANMobilityInformation-r5-IEs, v690NonCriticalExtensions SEQUENCE { utranMobilityInformation-v690ext UtranMobilityInformation-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } UTRANMobilityInformation-r3-IEs ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo new-U-RNTI U-RNTI new-C-RNTI C-RNTI ue-ConnTimersAndConstants UE-ConnTimersAndConstants -- CN information elements cn-InformationInfo CN-InformationInfoFull -- UTRAN mobility IEs ura-Identity URA-Identity -- Radio bearer IEs dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} OPTIONAL }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
UTRANMobilityInformation-v3a0ext-IEs ::= SEQUENCE { ue-ConnTimersAndConstants-v3a0ext UE-ConnTimersAndConstants-v3a0ext } UTRANMobilityInformation-r5-IEs ::= SEQUENCE { -- User equipment IEs integrityProtectionModeInfo IntegrityProtectionModeInfo cipheringModeInfo CipheringModeInfo new-U-RNTI U-RNTI new-C-RNTI C-RNTI ue-ConnTimersAndConstants UE-ConnTimersAndConstants-r5
3GPP
Release 6
-- CN information elements cn-InformationInfo -- UTRAN mobility IEs ura-Identity -- Radio bearer IEs dl-CounterSynchronisationInfo }
830
3GPP TS 25.331 V6.23.0 (2009-09)
CN-InformationInfoFull URA-Identity DL-CounterSynchronisationInfo-r5
UtranMobilityInformation-v690ext-IEs ::= SEQUENCE { -- Core network IEs primary-plmn-Identity PLMN-Identity } -- *************************************************** --- UTRAN MOBILITY INFORMATION CONFIRM --- *************************************************** UTRANMobilityInformationConfirm ::= SEQUENCE { -- User equipment IEs rrc-TransactionIdentifier RRC-TransactionIdentifier, ul-IntegProtActivationInfo IntegrityProtActivationInfo -- Radio bearer IEs count-C-ActivationTime ActivationTime -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy RB-ActivationTimeInfoList ul-CounterSynchronisationInfo UL-CounterSynchronisationInfo laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions utranMobilityInformationConfirm-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- UTRAN MOBILITY INFORMATION FAILURE --- *************************************************** UTRANMobilityInformationFailure ::= SEQUENCE { -- UE information elements rrc-TransactionIdentifier RRC-TransactionIdentifier, failureCause FailureCauseWithProtErr, laterNonCriticalExtensions SEQUENCE { -- Container for additional R99 extensions utranMobilityInformationFailure-r3-add-ext BIT STRING nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } -- *************************************************** --- MBMS ACCESS INFORMATION --- *************************************************** MBMSAccessInformation ::= SEQUENCE { -- Access Information IEs mbms-ServiceAccessInfoList -- Non critical extensions nonCriticalExtensions }
OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
MBMS-ServiceAccessInfoList-r6, SEQUENCE {} OPTIONAL
-- *************************************************** --- MBMS COMMON PTM RB INFORMATION --- *************************************************** MBMSCommonPTMRBInformation ::= SEQUENCE -- Common PTM RB Information IEs mbms-CommonRBInformationList mbms-TranspChInfoForEachTrCh mbms-TranspChInfoForEachCCTrCh mbms-PhyChInformationList { MBMS-CommonRBInformationList-r6, MBMS-TranspChInfoForEachTrCh-r6, MBMS-TranspChInfoForEachCCTrCh-r6 MBMS-PhyChInformationList-r6,
OPTIONAL,
3GPP
Release 6
-- Non critical extensions nonCriticalExtensions }
831
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE {}
OPTIONAL
-- *************************************************** --- MBMS CURRENT CELL PTM RB INFORMATION --- *************************************************** MBMSCurrentCellPTMRBInformation ::= SEQUENCE { -- Current Cell PTM RB Information IEs mbms-CurrentCell-SCCPCHList MBMS-CurrentCell-SCCPCHList-r6 mbms-SIBType5-SCCPCHList MBMS-SIBType5-SCCPCHList-r6 -- Non critical extensions nonCriticalExtensions SEQUENCE {} OPTIONAL } -- *************************************************** --- MBMS GENERAL INFORMATION --- *************************************************** MBMSGeneralInformation ::= SEQUENCE { -- MBMS General Information IEs mbms-PreferredFrequencyInfo MBMS-PreferredFrequencyList-r6 OPTIONAL, mbms-TimersAndCounters MBMS-TimersAndCounters-r6, michConfigurationInfo MBMS-MICHConfigurationInfo-r6, cellGroupIdentity MBMS-CellGroupIdentity-r6, mschDefaultConfigurationInfo MBMS-MSCH-ConfigurationInfo-r6 OPTIONAL, -- Non critical extensions v6b0NonCriticalExtensions SEQUENCE { mbmsGeneralInformation-v6b0ext MBMSGeneralInformation-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } MBMSGeneralInformation-v6b0ext-IEs ::= SEQUENCE { indicateChangeInSelectedServices BOOLEAN } -- *************************************************** --- MBMS MODIFICATION REQUEST --- *************************************************** MBMSModificationRequest ::= SEQUENCE { -- MBMS Modification Request IEs mbms-PreferredFreqRequest MBMS-ServiceIdentity-r6 OPTIONAL, rb-InformationReleaseList RB-InformationReleaseList OPTIONAL, -- Non critical extensions v6b0NonCriticalExtensions SEQUENCE { mbmsModificationRequest-v6b0ext MBMSModificationRequest-v6b0ext-IEs, v6f0NonCriticalExtensions SEQUENCE { mbmsModificationRequest-v6f0ext MBMSModificationRequest-v6f0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } MBMSModificationRequest-v6b0ext-IEs ::= SEQUENCE { mbmsSelectedServiceInfo MBMS-SelectedServiceInfo } MBMSModificationRequest-v6f0ext-IEs ::= SEQUENCE { mbmsSupportOfServiceChangeForAPtpRB ENUMERATED { true } } -- *************************************************** --- MBMS MODIFIED SERVICES INFORMATION --- *************************************************** MBMSModifiedServicesInformation ::= SEQUENCE { -- MBMS Modified Services Information IEs
OPTIONAL, OPTIONAL,
OPTIONAL
3GPP
Release 6
modifedServiceList mbms-ReacquireMCCH mbms-DynamicPersistenceLevel endOfModifiedMCCHInformation mbmsNumberOfNeighbourCells mbms-AllUnmodifiedPTMServices mbms-PTMActivationTime -- Non critical extensions nonCriticalExtensions }
832
3GPP TS 25.331 V6.23.0 (2009-09)

MBMS-ModifedServiceList-r6 ENUMERATED { true } DynamicPersistenceLevel INTEGER (1..16) MBMS-NumberOfNeighbourCells-r6, ENUMERATED { true } MBMS-PTMActivationTime-r6 SEQUENCE {} OPTIONAL
-- *************************************************** --- MBMS NEIGHBOURING CELL PTM RB INFORMATION --- *************************************************** MBMSNeighbouringCellPTMRBInformation ::= SEQUENCE { -- MBMS Neighbouring Cell PTM RB Information IEs neighbouringCellIdentity IntraFreqCellID, neighbouringCellSCCPCHList MBMS-NeighbouringCellSCCPCHList-r6, -- Non critical extensions nonCriticalExtensions SEQUENCE {} OPTIONAL } -- *************************************************** --- MBMS SCHEDULING INFORMATION --- *************************************************** MBMSSchedulingInformation ::= SEQUENCE { -- MBMS Scheduling Information IEs serviceSchedulingInfoList MBMS-ServiceSchedulingInfoList-r6, -- Non critical extensions nonCriticalExtensions SEQUENCE {} OPTIONAL } -- *************************************************** --- MBMS UNMODIFIED SERVICES INFORMATION --- *************************************************** MBMSUnmodifiedServicesInformation ::= SEQUENCE { -- MBMS Unmodified Services Information IEs unmodifiedServiceList MBMS-UnmodifiedServiceList-r6 -- Non critical extensions nonCriticalExtensions SEQUENCE {} OPTIONAL } END
OPTIONAL,
11.3
Information element definitions
InformationElements DEFINITIONS AUTOMATIC TAGS ::= -- *************************************************** --CORE NETWORK INFORMATION ELEMENTS (10.3.1) --- *************************************************** BEGIN IMPORTS hiPDSCHidentities, hiPUSCHidentities, hiRM, maxAC, maxAdditionalMeas, maxASC, maxASCmap, maxASCpersist, maxCCTrCH, maxCellMeas,
3GPP
Release 6
maxCellMeas-1, maxCNdomains, maxCPCHsets, maxDPCH-DLchan, maxDPDCH-UL, maxDRACclasses, maxE-DCHMACdFlow, maxE-DCHMACdFlow-1, maxFACHPCH, maxFreq, maxFreqBandsFDD, maxFreqBandsFDD-ext, maxFreqBandsTDD, maxFreqBandsGSM, maxGERAN-SI, maxHProcesses, maxHSDSCHTBIndex, maxHSDSCHTBIndex-tdd384, maxHSSCCHs, maxInterSysMessages, maxLoCHperRLC, maxMAC-d-PDUsizes, maxMBMS-CommonCCTrCh, maxMBMS-CommonPhyCh, maxMBMS-CommonRB, maxMBMS-CommonTrCh, maxMBMS-Freq, maxMBMS-L1CP, maxMBMSservCount, maxMBMSservModif, maxMBMSservSched, maxMBMSservSelect, maxMBMSservUnmodif, maxMBMSTransmis, maxMeasEvent, maxMeasIntervals, maxMeasParEvent, maxNumCDMA2000Freqs, maxNumFDDFreqs, maxNumGSMFreqRanges, maxGSMTargetCells, maxNumTDDFreqs, maxOtherRAT, maxOtherRAT-16, maxPage1, maxPCPCH-APsig, maxPCPCH-APsubCh, maxPCPCH-CDsig, maxPCPCH-CDsubCh, maxPCPCH-SF, maxPCPCHs, maxPDCPAlgoType, maxPDSCH, maxPDSCH-TFCIgroups, maxPRACH, maxPRACH-FPACH, maxPredefConfig, maxPUSCH, maxQueueIDs, maxRABsetup, maxRAT, maxRB, maxRBallRABs, maxRBperTrCh, maxRBMuxOptions, maxRBperRAB, maxReportedGSMCells, maxRLCPDUsizePerLogChan, maxSRBsetup, maxRL, maxRL-1, maxEDCHRL, maxROHC-PacketSizes-r4, maxROHC-Profile-r4, maxSCCPCH, maxSat, maxSIB, maxSIB-FACH, maxSystemCapability,
833
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6
maxTF, maxTF-CPCH, maxTFC, maxTFCsub, maxTFCI-2-Combs, maxTGPS, maxTrCH, maxTrCHpreconf, maxTS, maxTS-1, maxTS-2, maxTS-LCR, maxTS-LCR-1, maxURA, maxURNTI-Group FROM Constant-definitions; Ansi-41-IDNNS ::= CN-DomainIdentity ::=
834
3GPP TS 25.331 V6.23.0 (2009-09)
BIT STRING (SIZE (14)) ENUMERATED { cs-domain, ps-domain } SEQUENCE { CN-DomainIdentity, NAS-SystemInformationGSM-MAP
CN-DomainInformation ::= cn-DomainIdentity cn-DomainSpecificNAS-Info } CN-DomainInformationFull ::= cn-DomainIdentity cn-DomainSpecificNAS-Info cn-DRX-CycleLengthCoeff } CN-DomainInformationList ::=
SEQUENCE { CN-DomainIdentity, NAS-SystemInformationGSM-MAP, CN-DRX-CycleLengthCoefficient
SEQUENCE (SIZE (1..maxCNdomains)) OF CN-DomainInformation SEQUENCE (SIZE (1..maxCNdomains)) OF CN-DomainInformationFull SEQUENCE { CN-DomainIdentity, CHOICE { NAS-SystemInformationGSM-MAP, NAS-SystemInformationANSI-41 CN-DRX-CycleLengthCoefficient
CN-DomainInformationListFull ::=
CN-DomainSysInfo ::= cn-DomainIdentity cn-Type gsm-MAP ansi-41 }, cn-DRX-CycleLengthCoeff } CN-DomainSysInfoList ::=
SEQUENCE (SIZE (1..maxCNdomains)) OF CN-DomainSysInfo SEQUENCE { PLMN-Identity NAS-SystemInformationGSM-MAP CN-DomainInformationList
CN-InformationInfo ::= plmn-Identity cn-CommonGSM-MAP-NAS-SysInfo cn-DomainInformationList } CN-InformationInfo-r6 ::= plmn-Identity cn-CommonGSM-MAP-NAS-SysInfo cn-DomainInformationList primary-plmn-Identity } CN-InformationInfoFull ::= plmn-Identity cn-CommonGSM-MAP-NAS-SysInfo cn-DomainInformationListFull } Digit ::= Gsm-map-IDNNS ::= routingbasis localPTMSI routingparameter },
SEQUENCE { PLMN-Identity NAS-SystemInformationGSM-MAP CN-DomainInformationList PLMN-Identity
SEQUENCE { PLMN-Identity NAS-SystemInformationGSM-MAP CN-DomainInformationListFull
INTEGER (0..9) SEQUENCE { CHOICE { SEQUENCE { RoutingParameter
3GPP
Release 6
tMSIofsamePLMN routingparameter }, tMSIofdifferentPLMN routingparameter }, iMSIresponsetopaging routingparameter }, iMSIcauseUEinitiatedEvent routingparameter }, iMEI routingparameter }, spare2 routingparameter }, spare1 routingparameter }
835
3GPP TS 25.331 V6.23.0 (2009-09)

SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter SEQUENCE { RoutingParameter
}, -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy BOOLEAN } IMEI ::= SEQUENCE (SIZE (15)) OF IMEI-Digit INTEGER (0..15) SEQUENCE (SIZE (6..21)) OF Digit SEQUENCE { CHOICE { SEQUENCE { CHOICE { Gsm-map-IDNNS, Ansi-41-IDNNS
IMEI-Digit ::= IMSI-GSM-MAP ::=
IntraDomainNasNodeSelector ::= version release99 cn-Type gsm-Map-IDNNS ansi-41-IDNNS } }, later futurecoding } } } LAI ::= plmn-Identity lac } MCC ::=
SEQUENCE { BIT STRING (SIZE (15))
SEQUENCE { PLMN-Identity, BIT STRING (SIZE (16))
SEQUENCE (SIZE (3)) OF Digit SEQUENCE (SIZE (2..3)) OF Digit SEQUENCE { BOOLEAN, SEQUENCE (SIZE (1..5)) OF PLMN-IdentityWithOptionalMCC-r6
MNC ::=
MultiplePLMN-List-r6 ::= mibPLMN-Identity multiplePLMNs } NAS-Message ::= NAS-Synchronisation-Indicator ::= NAS-SystemInformationGSM-MAP ::= P-TMSI-GSM-MAP ::= PagingRecordTypeID ::=
OCTET STRING (SIZE (1..4095)) BIT STRING(SIZE(4)) OCTET STRING (SIZE (1..8)) BIT STRING (SIZE (32)) ENUMERATED { imsi-GSM-MAP, tmsi-GSM-MAP-P-TMSI, imsi-DS-41,
3GPP
Release 6
836
tmsi-DS-41 }
3GPP TS 25.331 V6.23.0 (2009-09)
PLMN-Identity ::= mcc mnc }
SEQUENCE { MCC, MNC
PLMN-IdentityWithOptionalMCC-r6 ::= SEQUENCE { mcc MCC mnc MNC } PLMN-Type ::= gsm-MAP plmn-Identity }, ansi-41 p-REV min-P-REV sid nid }, gsm-MAP-and-ANSI-41 plmn-Identity p-REV min-P-REV sid nid }, spare } RAB-Identity ::= gsm-MAP-RAB-Identity ansi-41-RAB-Identity } RAI ::= lai rac } RoutingAreaCode ::= RoutingParameter ::= TMSI-GSM-MAP ::= CHOICE { SEQUENCE { PLMN-Identity SEQUENCE { P-REV, Min-P-REV, SID, NID SEQUENCE { PLMN-Identity, P-REV, Min-P-REV, SID, NID NULL
OPTIONAL,
CHOICE { BIT STRING (SIZE (8)), BIT STRING (SIZE (8))
SEQUENCE { LAI, RoutingAreaCode
BIT STRING (SIZE (8)) BIT STRING (SIZE (10)) BIT STRING (SIZE (32))
-- *************************************************** --UTRAN MOBILITY INFORMATION ELEMENTS (10.3.2) --- *************************************************** AccessClassBarred ::= ENUMERATED { barred, notBarred } SEQUENCE (SIZE (maxAC)) OF AccessClassBarred ENUMERATED { allowed, notAllowed }
AccessClassBarredList ::=
AllowedIndicator ::=
CellAccessRestriction ::= SEQUENCE { cellBarred CellBarred, cellReservedForOperatorUse ReservedIndicator, cellReservationExtension ReservedIndicator, -- NOTE: IE accessClassBarredList should not be included if the IE CellAccessRestriction -- is included in the IE SysInfoType4 accessClassBarredList AccessClassBarredList OPTIONAL } CellBarred ::= CHOICE { barred SEQUENCE { intraFreqCellReselectionInd AllowedIndicator, t-Barred T-Barred }, notBarred NULL
3GPP
Release 6
} CellIdentity ::= CellIdentity-PerRL-List ::=
837
3GPP TS 25.331 V6.23.0 (2009-09)
BIT STRING (SIZE (28)) SEQUENCE (SIZE (1..maxRL)) OF CellIdentity
CellSelectReselectInfoSIB-3-4 ::= SEQUENCE { mappingInfo MappingInfo cellSelectQualityMeasure CHOICE { cpich-Ec-N0 SEQUENCE { -- Default value for q-HYST-2-S is q-HYST-1-S q-HYST-2-S Q-Hyst-S -- Default value for q-HYST-2-S is q-HYST-1-S }, cpich-RSCP NULL }, modeSpecificInfo CHOICE { fdd SEQUENCE { s-Intrasearch S-SearchQual s-Intersearch S-SearchQual s-SearchHCS S-SearchRXLEV rat-List RAT-FDD-InfoList q-QualMin Q-QualMin, q-RxlevMin Q-RxlevMin }, tdd SEQUENCE { s-Intrasearch S-SearchRXLEV s-Intersearch S-SearchRXLEV s-SearchHCS S-SearchRXLEV rat-List RAT-TDD-InfoList q-RxlevMin Q-RxlevMin } }, q-Hyst-l-S Q-Hyst-S, t-Reselection-S T-Reselection-S, hcs-ServingCellInformation HCS-ServingCellInformation maxAllowedUL-TX-Power MaxAllowedUL-TX-Power }
OPTIONAL,
OPTIONAL
OPTIONAL,
DomainSpecificAccessRestrictionForSharedNetwork-v670ext ::= CHOICE { domainSpecificAccessRestictionList DomainSpecificAccessRestrictionListv670ext, domainSpecificAccessRestictionParametersForAll DomainSpecificAccessRestrictionParamv670ext } DomainSpecificAccessRestrictionList-v670ext ::= SEQUENCE { domainSpecificAccessRestrictionParametersForOperator1 DomainSpecificAccessRestrictionParam-v670ext domainSpecificAccessRestrictionParametersForOperator2 DomainSpecificAccessRestrictionParam-v670ext domainSpecificAccessRestrictionParametersForOperator3 DomainSpecificAccessRestrictionParam-v670ext domainSpecificAccessRestrictionParametersForOperator4 DomainSpecificAccessRestrictionParam-v670ext domainSpecificAccessRestrictionParametersForOperator5 DomainSpecificAccessRestrictionParam-v670ext }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
DomainSpecificAccessRestrictionParam-v670ext ::= SEQUENCE { cSDomainSpecificAccessRestriction DomainSpecificAccessRestriction-v670ext, pSDomainSpecificAccessRestriction DomainSpecificAccessRestriction-v670ext } DomainSpecificAccessRestriction-v670ext ::= CHOICE { noRestriction NULL, restriction SEQUENCE { domainSpecficAccessClassBarredList AccessClassBarredList } } MapParameter ::= Mapping ::= rat mappingFunctionParameterList } INTEGER (0..99) SEQUENCE { RAT, MappingFunctionParameterList
OPTIONAL
3GPP
Release 6
Mapping-LCR-r4 ::= mappingFunctionParameterList }
838
SEQUENCE { MappingFunctionParameterList
3GPP TS 25.331 V6.23.0 (2009-09)
MappingFunctionParameter ::= SEQUENCE { functionType MappingFunctionType, mapParameter1 MapParameter OPTIONAL, mapParameter2 MapParameter, -- The presence of upperLimit is conditional on the number of repetition upperLimit UpperLimit OPTIONAL } MappingFunctionParameterList ::= SEQUENCE (SIZE (1..maxMeasIntervals)) OF MappingFunctionParameter ENUMERATED { linear, functionType2, functionType3, functionType4 }
MappingFunctionType ::=
-- In MappingInfo list, mapping for FDD and 3.84Mcps TDD is defined. -- For 1.28Mcps TDD, Mapping-LCR-r4 is used instead. MappingInfo ::= SEQUENCE (SIZE (1..maxRAT)) OF Mapping -- Actual value Q-Hyst-S = IE value * 2 Q-Hyst-S ::= INTEGER (0..20) Q-Hyst-S-Fine ::= INTEGER (0..40) RAT ::= ENUMERATED { utra-FDD, utra-TDD, gsm, cdma2000 } SEQUENCE { RAT-Identifier, S-SearchQual, S-SearchRXLEV S-SearchQual
RAT-FDD-Info ::= rat-Identifier s-SearchRAT s-HCS-RAT s-Limit-SearchRAT } RAT-FDD-InfoList ::=
OPTIONAL,
SEQUENCE (SIZE (1..maxOtherRAT)) OF RAT-FDD-Info ENUMERATED { gsm, cdma2000 } SEQUENCE { RAT-Identifier, S-SearchRXLEV, S-SearchRXLEV S-SearchRXLEV
RAT-Identifier ::=
RAT-TDD-Info ::= rat-Identifier s-SearchRAT s-HCS-RAT s-Limit-SearchRAT } RAT-TDD-InfoList ::=
OPTIONAL,
SEQUENCE (SIZE (1..maxOtherRAT)) OF RAT-TDD-Info ENUMERATED { reserved, notReserved }
ReservedIndicator ::=
-- Actual value S-SearchQual = IE value * 2 S-SearchQual ::= INTEGER (-16..10) -- Actual value S-SearchRXLEV = (IE value * 2) + 1 S-SearchRXLEV ::= INTEGER (-53..45) -- Actual value ScalingFactor = IE value * 0.1 SpeedDependentScalingFactor ::= INTEGER (0..10) T-Barred ::= ENUMERATED { s10, s20, s40, s80, s160, s320, s640, s1280 } INTEGER (0..31)
T-Reselection-S ::=
3GPP
Release 6
839
3GPP TS 25.331 V6.23.0 (2009-09)
-- Actual value T-Reselection-S-Fine = IE value * 0.2 T-Reselection-S-Fine ::= INTEGER (0..31) -- Actual value ScalingFactor = IE value * 0.25 TreselectionScalingFactor ::= INTEGER (4..19) -- For UpperLimit, the used range depends on the RAT used. UpperLimit ::= INTEGER (1..91) URA-Identity ::= URA-IdentityList ::= BIT STRING (SIZE (16)) SEQUENCE (SIZE (1..maxURA)) OF URA-Identity
-- *************************************************** --USER EQUIPMENT INFORMATION ELEMENTS (10.3.3) --- *************************************************** AccessStratumReleaseIndicator ::= ENUMERATED { rel-4, rel-5, rel-6, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }
-- TABULAR : for ActivationTime, value 'now' always appear as default, and is encoded -- by absence of the field ActivationTime ::= INTEGER (0..255) BackoffControlParams ::= n-AP-RetransMax n-AccessFails nf-BO-NoAICH ns-BO-Busy nf-BO-AllBusy nf-BO-Mismatch t-CPCH } C-RNTI ::= SEQUENCE { N-AP-RetransMax, N-AccessFails, NF-BO-NoAICH, NS-BO-Busy, NF-BO-AllBusy, NF-BO-Mismatch, T-CPCH
BIT STRING (SIZE (16))
CapabilityUpdateRequirement ::= SEQUENCE { ue-RadioCapabilityFDDUpdateRequirement BOOLEAN, -- ue-RadioCapabilityTDDUpdateRequirement is for 3.84Mcps TDD update requirement ue-RadioCapabilityTDDUpdateRequirement BOOLEAN, systemSpecificCapUpdateReqList SystemSpecificCapUpdateReqList OPTIONAL } CapabilityUpdateRequirement-r4-ext ::= SEQUENCE { ue-RadioCapabilityUpdateRequirement-TDD128 BOOLEAN } CapabilityUpdateRequirement-r4 ::= SEQUENCE { ue-RadioCapabilityFDDUpdateRequirement-FDD BOOLEAN, ue-RadioCapabilityTDDUpdateRequirement-TDD384 BOOLEAN, ue-RadioCapabilityTDDUpdateRequirement-TDD128 BOOLEAN, systemSpecificCapUpdateReqList SystemSpecificCapUpdateReqList }
OPTIONAL
-- If the IE CellUpdateCause has the value 'cellUpdateCause-ext', the actual value is -- defined in the IE CellUpdateCause-ext. CellUpdateCause ::= ENUMERATED { cellReselection, periodicalCellUpdate, uplinkDataTransmission, utran-pagingResponse, re-enteredServiceArea, radiolinkFailure, rlc-unrecoverableError, cellUpdateCause-ext } -- The IE CellUpdateCause-ext shall be present, if the IE CellUpdateCause has the -- value 'cellUpdateCause-ext'. -- dummy is not used in this version of the specification, it should not be sent -- and if received it should be ignored by the receiver. CellUpdateCause-ext ::= ENUMERATED {
3GPP
Release 6
840
mbms-Reception, mbms-PTP-RB-Request, dummy, spare1 }
3GPP TS 25.331 V6.23.0 (2009-09)
ChipRateCapability ::=
ENUMERATED { mcps3-84, mcps1-28 } ENUMERATED { uea0, uea1 } CHOICE { CipheringAlgorithm, NULL
CipheringAlgorithm ::=
CipheringModeCommand ::= startRestart dummy }
CipheringModeInfo ::= SEQUENCE { -- TABULAR: The ciphering algorithm is included in the CipheringModeCommand. cipheringModeCommand CipheringModeCommand, activationTimeForDPCH ActivationTime OPTIONAL, rb-DL-CiphActivationTimeInfo RB-ActivationTimeInfoList OPTIONAL } CN-DRX-CycleLengthCoefficient ::= CN-PagedUE-Identity ::= imsi-GSM-MAP tmsi-GSM-MAP p-TMSI-GSM-MAP imsi-DS-41 tmsi-DS-41 spare3 spare2 spare1 } INTEGER (6..9) CHOICE { IMSI-GSM-MAP, TMSI-GSM-MAP, P-TMSI-GSM-MAP, IMSI-DS-41, TMSI-DS-41, NULL, NULL, NULL
CompressedModeMeasCapability ::= SEQUENCE { fdd-Measurements BOOLEAN, -- TABULAR: The IEs tdd-Measurements, gsm-Measurements and multiCarrierMeasurements -- are made optional since they are conditional based on another information element. -- Their absence corresponds to the case where the condition is not true. tdd-Measurements BOOLEAN OPTIONAL, gsm-Measurements GSM-Measurements OPTIONAL, multiCarrierMeasurements BOOLEAN OPTIONAL } CompressedModeMeasCapability-LCR-r4 ::= SEQUENCE { tdd128-Measurements BOOLEAN } CompressedModeMeasCapabFDDList ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF CompressedModeMeasCapabFDD
OPTIONAL
CompressedModeMeasCapabFDDList2 ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF CompressedModeMeasCapabFDD2 CompressedModeMeasCapabFDDList-ext ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF CompressedModeMeasCapabFDD-ext CompressedModeMeasCapabFDD ::= radioFrequencyBandFDD dl-MeasurementsFDD ul-MeasurementsFDD } SEQUENCE { RadioFrequencyBandFDD BOOLEAN, BOOLEAN
OPTIONAL,
CompressedModeMeasCapabFDD2 ::= SEQUENCE { -- UE may omit both IEs if this IE indicates the compressed mode capability within the same -- frequency band. Otherwise, the UE shall include either one of the following OPTIONAL IEs. radioFrequencyBandFDD RadioFrequencyBandFDD OPTIONAL, radioFrequencyBandFDD2 RadioFrequencyBandFDD2 OPTIONAL, dl-MeasurementsFDD BOOLEAN, ul-MeasurementsFDD BOOLEAN } CompressedModeMeasCapabFDD-ext ::= radioFrequencyBandFDD2 dl-MeasurementsFDD ul-MeasurementsFDD SEQUENCE { RadioFrequencyBandFDD2, BOOLEAN, BOOLEAN
3GPP
Release 6
} CompressedModeMeasCapabTDDList ::=
841
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxFreqBandsTDD)) OF CompressedModeMeasCapabTDD SEQUENCE { RadioFrequencyBandTDD, BOOLEAN, BOOLEAN
CompressedModeMeasCapabTDD ::= radioFrequencyBandTDD dl-MeasurementsTDD ul-MeasurementsTDD } CompressedModeMeasCapabGSMList ::=
SEQUENCE (SIZE (1..maxFreqBandsGSM)) OF CompressedModeMeasCapabGSM SEQUENCE { RadioFrequencyBandGSM, BOOLEAN, BOOLEAN
CompressedModeMeasCapabGSM ::= radioFrequencyBandGSM dl-MeasurementsGSM ul-MeasurementsGSM } CompressedModeMeasCapabMC ::= dl-MeasurementsMC ul-MeasurementsMC }
SEQUENCE { BOOLEAN, BOOLEAN
CPCH-Parameters ::= SEQUENCE { initialPriorityDelayList InitialPriorityDelayList backoffControlParams BackoffControlParams, -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm, dl-DPCCH-BER DL-DPCCH-BER } DL-CapabilityWithSimultaneousHS-DSCHConfig ::= DL-DPCCH-BER ::=
OPTIONAL,
ENUMERATED{kbps32, kbps64, kbps128, kbps384}
INTEGER (0..63)
DL-PhysChCapabilityFDD ::= SEQUENCE { -- The IE maxNoDPCH-PDSCH-Codes only gives information on the maximum number of DPCH Codes. maxNoDPCH-PDSCH-Codes INTEGER (1..8), maxNoPhysChBitsReceived MaxNoPhysChBitsReceived, supportForSF-512 BOOLEAN, -- dummy and dummy2 are not used in this version of the specification -- and if received they should be ignored. dummy BOOLEAN, dummy2 SimultaneousSCCPCH-DPCH-Reception } DL-PhysChCapabilityFDD-v380ext ::= SEQUENCE { -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SupportOfDedicatedPilotsForChEstimation } SupportOfDedicatedPilotsForChEstimation ::= DL-PhysChCapabilityTDD ::= maxTS-PerFrame maxPhysChPerFrame minimumSF supportOfPDSCH maxPhysChPerTS } DL-PhysChCapabilityTDD-LCR-r4 ::= maxTS-PerSubFrame maxPhysChPerFrame minimumSF supportOfPDSCH maxPhysChPerTS supportOf8PSK } DL-TransChCapability ::= maxNoBitsReceived maxConvCodeBitsReceived turboDecodingSupport maxSimultaneousTransChs ENUMERATED { true }
OPTIONAL
SEQUENCE { MaxTS-PerFrame, MaxPhysChPerFrame, MinimumSF-DL, BOOLEAN, MaxPhysChPerTS
SEQUENCE { MaxTS-PerSubFrame-r4, MaxPhysChPerSubFrame-r4, MinimumSF-DL, BOOLEAN, MaxPhysChPerTS, BOOLEAN
SEQUENCE { MaxNoBits, MaxNoBits, TurboSupport, MaxSimultaneousTransChsDL,
3GPP
Release 6
maxSimultaneousCCTrCH-Count maxReceivedTransportBlocks maxNumberOfTFC maxNumberOfTF } DRAC-SysInfo ::= transmissionProbability maximumBitRate } DRAC-SysInfoList ::=
842
MaxSimultaneousCCTrCH-Count, MaxTransportBlocksDL, MaxNumberOfTFC-DL, MaxNumberOfTF
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { TransmissionProbability, MaximumBitRate
SEQUENCE (SIZE (1..maxDRACclasses)) OF DRAC-SysInfo BIT STRING (SIZE (16)) ENUMERATED { true } BIT STRING (SIZE (16)) BIT STRING (SIZE (32)) ENUMERATED { originatingConversationalCall, originatingStreamingCall, originatingInteractiveCall, originatingBackgroundCall, originatingSubscribedTrafficCall, terminatingConversationalCall, terminatingStreamingCall, terminatingInteractiveCall, terminatingBackgroundCall, emergencyCall, interRAT-CellReselection, interRAT-CellChangeOrder, registration, detach, originatingHighPrioritySignalling, originatingLowPrioritySignalling, callRe-establishment, terminatingHighPrioritySignalling, terminatingLowPrioritySignalling, terminatingCauseUnknown, mbms-Reception, mbms-PTP-RB-Request, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }
DSCH-RNTI ::= DelayRestrictionFlag ::= E-RNTI ::= ESN-DS-41 ::= EstablishmentCause ::=
FailureCauseWithProtErr ::= CHOICE { configurationUnsupported NULL, physicalChannelFailure NULL, incompatibleSimultaneousReconfiguration NULL, compressedModeRuntimeError TGPSI, protocolError ProtocolErrorInformation, cellUpdateOccurred NULL, invalidConfiguration NULL, configurationIncomplete NULL, unsupportedMeasurement NULL, mbmsSessionAlreadyReceivedCorrectly NULL, lowerPriorityMBMSService NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL } FailureCauseWithProtErrTrId ::= rrc-TransactionIdentifier SEQUENCE { RRC-TransactionIdentifier,
3GPP
Release 6
failureCause } GroupIdentityWithReleaseInformation ::= rrc-ConnectionReleaseInformation groupReleaseInformation } GroupReleaseInformation ::= uRNTI-Group } GSM-Measurements ::= gsm900 dcs1800 gsm1900 } H-RNTI ::= HSDSCH-physical-layer-category ::=
843
FailureCauseWithProtErr
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { RRC-ConnectionReleaseInformation, GroupReleaseInformation
SEQUENCE { U-RNTI-Group
SEQUENCE { BOOLEAN, BOOLEAN, BOOLEAN
BIT STRING (SIZE (16)) INTEGER (1..64)
UESpecificBehaviourInformation1idle ::= BIT STRING (SIZE (4)) UESpecificBehaviourInformation1interRAT ::= BIT STRING (SIZE (8))
IMSI-and-ESN-DS-41 ::= imsi-DS-41 esn-DS-41 } IMSI-DS-41 ::= InitialPriorityDelayList ::=
SEQUENCE { IMSI-DS-41, ESN-DS-41
OCTET STRING (SIZE (5..7)) SEQUENCE (SIZE (1..maxASC)) OF NS-IP CHOICE { IMSI-GSM-MAP, TMSI-and-LAI-GSM-MAP, P-TMSI-and-RAI-GSM-MAP, IMEI, ESN-DS-41, IMSI-DS-41, IMSI-and-ESN-DS-41, TMSI-DS-41
InitialUE-Identity ::= imsi tmsi-and-LAI p-TMSI-and-RAI imei esn-DS-41 imsi-DS-41 imsi-and-ESN-DS-41 tmsi-DS-41 } IntegrityCheckInfo ::= messageAuthenticationCode rrc-MessageSequenceNumber } IntegrityProtActivationInfo ::= rrc-MessageSequenceNumberList } IntegrityProtectionAlgorithm ::=
SEQUENCE { MessageAuthenticationCode, RRC-MessageSequenceNumber
SEQUENCE { RRC-MessageSequenceNumberList
ENUMERATED { uia1 }
IntegrityProtectionModeCommand ::= CHOICE { startIntegrityProtection SEQUENCE { integrityProtInitNumber IntegrityProtInitNumber }, modify SEQUENCE { dl-IntegrityProtActivationInfo IntegrityProtActivationInfo } } IntegrityProtectionModeInfo ::= SEQUENCE { -- TABULAR: DL integrity protection activation info and Integrity -- protection intialisation number have been nested inside -- IntegrityProtectionModeCommand. integrityProtectionModeCommand IntegrityProtectionModeCommand, integrityProtectionAlgorithm IntegrityProtectionAlgorithm }
OPTIONAL
3GPP
Release 6
IntegrityProtInitNumber ::=
844
3GPP TS 25.331 V6.23.0 (2009-09)
-- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. MaxHcContextSpace ::= ENUMERATED { dummy, by1024, by2048, by4096, by8192 } MaxHcContextSpace-r5-ext ::= ENUMERATED { by16384, by32768, by65536, by131072 }
MaxROHC-ContextSessions-r4 ::=
ENUMERATED { s2, s4, s8, s12, s16, s24, s32, s48, s64, s128, s256, s512, s1024, s16384 } ENUMERATED { dummy, am4, am5, am6, am8, am16, am30 }
MaximumAM-EntityNumberRLC-Cap ::=
-- Actual value MaximumBitRate = IE value * 16 MaximumBitRate ::= INTEGER (0..32) MaximumRLC-WindowSize ::= MaxNoDPDCH-BitsTransmitted ::= ENUMERATED { mws2047, mws4095 } ENUMERATED { b600, b1200, b2400, b4800, b9600, b19200, b28800, b38400, b48000, b57600 } ENUMERATED { b640, b1280, b2560, b3840, b5120, b6400, b7680, b8960, b10240, b20480, b40960, b81920, b163840 } ENUMERATED { dummy, b1200, b2400, b3600, b4800, b7200, b9600, b14400, b19200, b28800, b38400, b48000, b57600, b67200, b76800 } ENUMERATED { rl1 } ENUMERATED { tf32, tf64, tf128, tf256, tf512, tf1024 } ENUMERATED { tfc16, tfc32, tfc48, tfc64, tfc96, tfc128, tfc256, tfc512, tfc1024 } ENUMERATED { dummy1, dummy2, tfc16, tfc32, tfc48, tfc64, tfc96, tfc128, tfc256, tfc512, tfc1024 }
MaxNoBits ::=
MaxNoPhysChBitsReceived ::=
MaxNoSCCPCH-RL ::=
MaxNumberOfTF ::=
MaxNumberOfTFC-DL ::=
MaxNumberOfTFC-UL ::=
-- the values 1 4 for MaxPhysChPerFrame are not used in this version of the protocol MaxPhysChPerFrame ::= INTEGER (1..224) MaxPhysChPerSubFrame-r4 ::= MaxPhysChPerTimeslot ::= INTEGER (1..96) ENUMERATED { ts1, ts2 }
-- the values 1 4 for MaxPhysChPerTS are not used in this version of the protocol MaxPhysChPerTS ::= INTEGER (1..16) MaxSimultaneousCCTrCH-Count ::= MaxSimultaneousTransChsDL ::= INTEGER (1..8) ENUMERATED { e4, e8, e16, e32 } ENUMERATED { dummy, e4, e8, e16, e32 } ENUMERATED { tb4, tb8, tb16, tb32, tb48, tb64, tb96, tb128, tb256, tb512 }
MaxSimultaneousTransChsUL ::=
MaxTransportBlocksDL ::=
3GPP
Release 6
845
3GPP TS 25.331 V6.23.0 (2009-09)
MaxTransportBlocksUL ::=
ENUMERATED { dummy, tb4, tb8, tb16, tb32, tb48, tb64, tb96, tb128, tb256, tb512 } INTEGER (1..14) INTEGER (1..6)
MaxTS-PerFrame ::= MaxTS-PerSubFrame-r4 ::=
-- TABULAR: MeasurementCapability contains dependencies to UE-MultiModeRAT-Capability, -- the conditional fields have been left mandatory for now. MeasurementCapability ::= SEQUENCE { downlinkCompressedMode CompressedModeMeasCapability, uplinkCompressedMode CompressedModeMeasCapability } MeasurementCapabilityExt ::= compressedModeMeasCapabFDDList compressedModeMeasCapabTDDList compressedModeMeasCapabGSMList compressedModeMeasCapabMC } MeasurementCapabilityExt2 ::= compressedModeMeasCapabFDDList compressedModeMeasCapabTDDList compressedModeMeasCapabGSMList compressedModeMeasCapabMC } SEQUENCE{ CompressedModeMeasCapabFDDList, CompressedModeMeasCapabTDDList OPTIONAL, CompressedModeMeasCapabGSMList OPTIONAL, CompressedModeMeasCapabMC OPTIONAL
SEQUENCE{ CompressedModeMeasCapabFDDList2, CompressedModeMeasCapabTDDList OPTIONAL, CompressedModeMeasCapabGSMList OPTIONAL, CompressedModeMeasCapabMC OPTIONAL
MeasurementCapability-r4-ext ::= downlinkCompressedMode-LCR uplinkCompressedMode-LCR } MessageAuthenticationCode ::= MinimumSF-DL ::=
SEQUENCE { CompressedModeMeasCapability-LCR-r4, CompressedModeMeasCapability-LCR-r4
BIT STRING (SIZE (32)) ENUMERATED { sf1, sf16 } ENUMERATED { sf1, sf2, sf4, sf8, dummy } ENUMERATED { tdd, fdd, fdd-tdd } SEQUENCE { BOOLEAN, BOOLEAN
MinimumSF-UL ::=
MultiModeCapability ::=
MultiRAT-Capability ::= supportOfGSM supportOfMulticarrier }
MultiModeRAT-Capability-v590ext ::= SEQUENCE { supportOfUTRAN-ToGERAN-NACC BOOLEAN } MultiModeRAT-Capability-v680ext ::= SEQUENCE { supportOfHandoverToGAN ENUMERATED { doesSupportHandoverToGAN } } N-300 ::= N-301 ::= N-302 ::= N-304 ::= N-308 ::= N-310 ::= N-312 ::= INTEGER (0..7) INTEGER (0..7) INTEGER (0..7) INTEGER (0..7) INTEGER (1..8) INTEGER (0..7) ENUMERATED { s1, s50, s100, s200, s400, s600, s800, s1000 } ENUMERATED { s2, s4, s10, s20 }
OPTIONAL
N-312ext ::=
3GPP
Release 6
846
3GPP TS 25.331 V6.23.0 (2009-09)
N-312-r5 ::=
ENUMERATED { s1, s2, s4, s10, s20, s50, s100, s200, s400, s600, s800, s1000 } ENUMERATED { s1, s2, s4, s10, s20, s50, s100, s200 } ENUMERATED { s1, s50, s100, s200, s400, s600, s800, s1000 } ENUMERATED { s2, s4, s10, s20 } ENUMERATED { s1, s2, s4, s10, s20, s50, s100, s200, s400, s600, s800, s1000 }
N-313 ::=
N-315 ::=
N-315ext ::=
N-315-r5 ::=
N-AccessFails ::= N-AP-RetransMax ::= NetworkAssistedGPS-Supported ::=
INTEGER (1..64) INTEGER (1..64) ENUMERATED { networkBased, ue-Based, bothNetworkAndUE-Based, noNetworkAssistedGPS } INTEGER (0..31) INTEGER (0..31) INTEGER (0..127) INTEGER (0..63) INTEGER (0..28) SEQUENCE { P-TMSI-GSM-MAP, RAI
NF-BO-AllBusy ::= NF-BO-NoAICH ::= NF-BO-Mismatch ::= NS-BO-Busy ::= NS-IP ::= P-TMSI-and-RAI-GSM-MAP ::= p-TMSI rai } PagingCause ::=
ENUMERATED { terminatingConversationalCall, terminatingStreamingCall, terminatingInteractiveCall, terminatingBackgroundCall, terminatingHighPrioritySignalling, terminatingLowPrioritySignalling, terminatingCauseUnknown, spare
} PagingRecord ::= CHOICE { cn-Identity SEQUENCE { pagingCause PagingCause, cn-DomainIdentity CN-DomainIdentity, cn-pagedUE-Identity CN-PagedUE-Identity }, utran-Identity SEQUENCE { u-RNTI U-RNTI, cn-OriginatedPage-connectedMode-UE SEQUENCE { pagingCause PagingCause, cn-DomainIdentity CN-DomainIdentity, pagingRecordTypeID PagingRecordTypeID } } } PagingRecord2-r5 ::= utran-SingleUE-Identity u-RNTI CHOICE { SEQUENCE { U-RNTI,
OPTIONAL
3GPP
Release 6
cn-OriginatedPage-connectedMode-UE pagingCause cn-DomainIdentity pagingRecordTypeID } rrc-ConnectionReleaseInformation }, utran-GroupIdentity } PagingRecordList ::=
847
SEQUENCE { PagingCause, CN-DomainIdentity, PagingRecordTypeID
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL, RRC-ConnectionReleaseInformation SEQUENCE ( SIZE (1 .. maxURNTI-Group) ) OF GroupIdentityWithReleaseInformation
SEQUENCE (SIZE (1..maxPage1)) OF PagingRecord SEQUENCE (SIZE (1..maxPage1)) OF PagingRecord2-r5
PagingRecord2List-r5 ::=
PDCP-Capability ::= SEQUENCE { losslessSRNS-RelocationSupport BOOLEAN, -- If present, the "maxHcContextSpace" in the IE "PDCP-Capability-r5-ext" overrides the -- "supported" value in this IE. The value in this IE may be used by a pre-REL-5 UTRAN. supportForRfc2507 CHOICE { notSupported NULL, supported MaxHcContextSpace } } PDCP-Capability-r4-ext ::= SEQUENCE { supportForRfc3095 CHOICE { notSupported NULL, supported SEQUENCE { maxROHC-ContextSessions MaxROHC-ContextSessions-r4 reverseCompressionDepth INTEGER (0..65535) } } } PDCP-Capability-r5-ext ::= SEQUENCE { supportForRfc3095ContextRelocation BOOLEAN, maxHcContextSpace MaxHcContextSpace-r5-ext } PDCP-Capability-r5-ext2 ::= losslessDLRLC-PDUSizeChange } SEQUENCE { ENUMERATED { true }
DEFAULT s16, DEFAULT 0
OPTIONAL
OPTIONAL
PhysicalChannelCapability ::= SEQUENCE { fddPhysChCapability SEQUENCE { downlinkPhysChCapability DL-PhysChCapabilityFDD, uplinkPhysChCapability UL-PhysChCapabilityFDD } OPTIONAL, -- tddPhysChCapability describes the 3.84Mcps TDD physical channel capability tddPhysChCapability SEQUENCE { downlinkPhysChCapability DL-PhysChCapabilityTDD, uplinkPhysChCapability UL-PhysChCapabilityTDD } OPTIONAL } -- PhysicalChannelCapability-LCR-r4 describes the 1.28Mcps TDD physical channel capability PhysicalChannelCapability-LCR-r4 ::= SEQUENCE { tdd128-PhysChCapability SEQUENCE { downlinkPhysChCapability DL-PhysChCapabilityTDD-LCR-r4, uplinkPhysChCapability UL-PhysChCapabilityTDD-LCR-r4 } OPTIONAL } -- PhysicalChannelCapability-hspdsch-r5 describes the HS-PDSCH physical channel capability PhysicalChannelCapability-hspdsch-r5 ::= SEQUENCE { fdd-hspdsch CHOICE { supported SEQUENCE { hsdsch-physical-layer-category HSDSCH-physical-layer-category, -- dummy and dummy2 are not used in this version of the specification -- and if received they should be ignored. dummy BOOLEAN, dummy2 BOOLEAN }, unsupported NULL },
3GPP
Release 6
tdd384-hspdsch supported unsupported }, tdd128-hspdsch supported unsupported } }
848
3GPP TS 25.331 V6.23.0 (2009-09)

CHOICE { HSDSCH-physical-layer-category, NULL CHOICE { HSDSCH-physical-layer-category, NULL
PNBSCH-Allocation-r4 ::= SEQUENCE { numberOfRepetitionsPerSFNPeriod ENUMERATED { c2, c3, c4, c5, c6, c7, c8, c9, c10, c12, c14, c16, c18, c20, c24, c28, c32, c36, c40, c48, c56, c64, c72, c80 } } ProtocolErrorCause ::= ENUMERATED { asn1-ViolationOrEncodingError, messageTypeNonexistent, messageNotCompatibleWithReceiverState, ie-ValueNotComprehended, informationElementMissing, messageExtensionNotComprehended, spare2, spare1 } ENUMERATED { noError, errorOccurred }
ProtocolErrorIndicator ::=
ProtocolErrorIndicatorWithMoreInfo ::= CHOICE { noError NULL, errorOccurred SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, protocolErrorInformation ProtocolErrorInformation } } ProtocolErrorMoreInformation ::= SEQUENCE { diagnosticsType CHOICE { type1 CHOICE { asn1-ViolationOrEncodingError NULL, messageTypeNonexistent NULL, messageNotCompatibleWithReceiverState IdentificationOfReceivedMessage, ie-ValueNotComprehended IdentificationOfReceivedMessage, conditionalInformationElementError IdentificationOfReceivedMessage, messageExtensionNotComprehended IdentificationOfReceivedMessage, spare1 NULL, spare2 NULL }, spare NULL } } RadioFrequencyBandFDD ::= ENUMERATED { -- fdd2100, fdd1900, fdd1800 correspond to Band I, Band II and Band III respectively fdd2100, fdd1900, fdd1800, bandVI, bandIV, bandV, bandVII, extension-indicator } RadioFrequencyBandFDD2 ::= ENUMERATED { bandVIII, bandIX, bandX, bandXI, bandXII, bandXIII, bandXIV, bandXV, bandXVI, bandXVII, bandXVIII,
3GPP
Release 6
849
bandXIX, bandXX, bandXXI, bandXXII, extension-indicator }
3GPP TS 25.331 V6.23.0 (2009-09)
RadioFrequencyBandTDDList ::=
ENUMERATED { a, b, c, ab, ac, bc, abc, spare } ENUMERATED {a, b, c, spare} ENUMERATED { gsm450, gsm480, gsm850, gsm900P, gsm900E, gsm1800, gsm1900, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} SEQUENCE { BOOLEAN, BOOLEAN } ENUMERATED { useT314, useT315
RadioFrequencyBandTDD ::= RadioFrequencyBandGSM ::=
Rb-timer-indicator ::= t314-expired t315-expired Re-EstablishmentTimer ::= } RedirectionInfo ::= frequencyInfo interRATInfo } RedirectionInfo-r6 ::= frequencyInfo interRATInfo } RejectionCause ::=
CHOICE { FrequencyInfo, InterRATInfo
CHOICE { FrequencyInfo, InterRATInfo-r6
ENUMERATED { congestion, unspecified } ENUMERATED { normalEvent, unspecified, pre-emptiveRelease, congestion, re-establishmentReject, directedsignallingconnectionre-establishment, userInactivity, spare }
ReleaseCause ::=
RF-Capability ::= SEQUENCE { fddRF-Capability SEQUENCE { ue-PowerClass UE-PowerClass, txRxFrequencySeparation TxRxFrequencySeparation } OPTIONAL, tddRF-Capability SEQUENCE { ue-PowerClass UE-PowerClass, radioFrequencyTDDBandList RadioFrequencyBandTDDList, chipRateCapability ChipRateCapability } OPTIONAL } RF-Capability-r4-ext ::= tddRF-Capability ue-PowerClass radioFrequencyBandTDDList chipRateCapability } } SEQUENCE { SEQUENCE { UE-PowerClass, RadioFrequencyBandTDDList, ChipRateCapability OPTIONAL
RLC-Capability ::= SEQUENCE { -- If present, the "totalRLC-AM-BufferSize" in the IE "RLC-Capability-r5-ext" overrides the -- corresponding value in this IE. The value in this IE may be used by a pre-REL-5 UTRAN. totalRLC-AM-BufferSize TotalRLC-AM-BufferSize,
3GPP
Release 6
maximumRLC-WindowSize maximumAM-EntityNumber } RLC-Capability-r5-ext ::= totalRLC-AM-BufferSize } RRC-ConnectionReleaseInformation ::= noRelease release releaseCause } } RRC-MessageSequenceNumber ::=
850
MaximumRLC-WindowSize, MaximumAM-EntityNumberRLC-Cap
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { TotalRLC-AM-BufferSize-r5-ext
OPTIONAL
CHOICE { NULL, SEQUENCE { ReleaseCause
INTEGER (0..15)
RRC-MessageSequenceNumberList ::=
SEQUENCE (SIZE (4..5)) OF RRC-MessageSequenceNumber ENUMERATED { cell-DCH, cell-FACH, cell-PCH, ura-PCH } INTEGER (0..3) BIT STRING (SIZE (20)) BIT STRING (SIZE (10))
RRC-StateIndicator ::=
RRC-TransactionIdentifier ::= S-RNTI ::= S-RNTI-2 ::= SecurityCapability ::= cipheringAlgorithmCap
SEQUENCE { BIT STRING { -- For each bit value 0 means false/ not supported spare15(0), spare14(1), spare13(2), spare12(3), spare11(4), spare10(5), spare9(6), spare8(7), spare7(8), spare6(9), spare5(10), spare4(11), spare3(12), spare2(13), uea1(14), uea0(15) } (SIZE (16)), integrityProtectionAlgorithmCap BIT STRING { -- For each bit value 0 means false/ not supported spare15(0), spare14(1), spare13(2), spare12(3), spare11(4), spare10(5), spare9(6), spare8(7), spare7(8), spare6(9), spare5(10), spare4(11), spare3(12), spare2(13), uia1(14), spare0(15) } (SIZE (16))
} Serving-HSDSCH-CellInformation ::= deltaACK deltaNACK harq-Preamble-Mode primaryCPICH-Info dl-hspdsch-Information harqInfo SEQUENCE { DeltaACK DeltaNACK HARQ-Preamble-Mode, PrimaryCPICH-Info DL-HSPDSCH-Information HARQ-Info
3GPP
Release 6
mac-hsResetIndicator }
851
ENUMERATED { true }
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
SimultaneousSCCPCH-DPCH-Reception ::= CHOICE { notSupported NULL, supported SEQUENCE { maxNoSCCPCH-RL MaxNoSCCPCH-RL, -- simultaneousSCCPCH-DPCH-DPDCH-Reception is applicable only if -- the IE Support of PDSCH = TRUE -- Note: the reference to DPDCH in the element name below is incorrect (see tabular). The -- name is not changed, to keep it aligned with R99. simultaneousSCCPCH-DPCH-DPDCH-Reception BOOLEAN } } SRNC-Identity ::= BIT STRING (SIZE (12))
START-Value ::= STARTList ::=
BIT STRING (SIZE (20)) SEQUENCE (SIZE (1..maxCNdomains)) OF STARTSingle SEQUENCE { CN-DomainIdentity, START-Value
STARTSingle ::= cn-DomainIdentity start-Value }
CapabilityUpdateRequirement-r5 ::= SEQUENCE { ue-RadioCapabilityFDDUpdateRequirement-FDD BOOLEAN, ue-RadioCapabilityTDDUpdateRequirement-TDD384 BOOLEAN, ue-RadioCapabilityTDDUpdateRequirement-TDD128 BOOLEAN, systemSpecificCapUpdateReqList SystemSpecificCapUpdateReqList-r5 } SystemSpecificCapUpdateReq ::= ENUMERATED { gsm } ENUMERATED { geranIu } ENUMERATED { gsm, geranIu }
OPTIONAL
SystemSpecificCapUpdateReq-v590ext ::=
SystemSpecificCapUpdateReq-r5 ::=
SystemSpecificCapUpdateReqList ::= SEQUENCE (SIZE (1..maxSystemCapability)) OF SystemSpecificCapUpdateReq SystemSpecificCapUpdateReqList-r5 ::= SEQUENCE (SIZE (1..maxSystemCapability)) OF SystemSpecificCapUpdateReq-r5 T-300 ::= ENUMERATED { ms100, ms200, ms400, ms600, ms800, ms1000, ms1200, ms1400, ms1600, ms1800, ms2000, ms3000, ms4000, ms6000, ms8000 } ENUMERATED { ms100, ms200, ms400, ms600, ms800, ms1000, ms1200, ms1400, ms1600, ms1800, ms2000, ms3000, ms4000, ms6000, ms8000, spare } ENUMERATED { ms100, ms200, ms400, ms600, ms800, ms1000, ms1200, ms1400, ms1600, ms1800, ms2000, ms3000, ms4000, ms6000, ms8000, spare } ENUMERATED { ms100, ms200, ms400, ms1000, ms2000, spare3, spare2, spare1 } ENUMERATED { noUpdate, m5, m10, m30, m60, m120, m360, m720 } ENUMERATED { s5, s10, s15, s20,
T-301 ::=
T-302 ::=
T-304 ::=
T-305 ::=
T-307 ::=
3GPP
Release 6
852
s30, s40, s50, spare }
3GPP TS 25.331 V6.23.0 (2009-09)
T-308 ::=
ENUMERATED { ms40, ms80, ms160, ms320 } INTEGER (1..8) ENUMERATED { ms40, ms80, ms120, ms160, ms200, ms240, ms280, ms320 } ENUMERATED { ms250, ms500, ms750, ms1000, ms1250, ms1500, ms1750, ms2000 }
T-309 ::= T-310 ::=
T-311 ::=
-- The value 0 for T-312 is not used in this version of the specification T-312 ::= INTEGER (0..15) T-313 ::= T-314 ::= INTEGER (0..15) ENUMERATED { s0, s2, s4, s6, s8, s12, s16, s20 } ENUMERATED { s0, s10, s30, s60, s180, s600, s1200, s1800 } ENUMERATED { s0, s10, s20, s30, s40, s50, s-inf, spare }
T-315 ::=
T-316 ::=
-- All the values are changed to "infinity" in Rel-5 T-317 ::= ENUMERATED { infinity0, infinity1, infinity2, infinity3, infinity4, infinity5, infinity6, infinity7} T-318 ::= ENUMERATED { ms250, ms500, ms750, ms1000, ms1250, ms1500, ms1750, ms2000, ms3000, ms4000, ms6000, ms8000, ms10000, ms12000, ms16000 } ENUMERATED { ct0, ct1 } SEQUENCE { TMSI-GSM-MAP, LAI
T-CPCH ::=
TMSI-and-LAI-GSM-MAP ::= tmsi lai } TMSI-DS-41 ::= TotalRLC-AM-BufferSize ::=
OCTET STRING (SIZE (2..17)) ENUMERATED { dummy, kb10, kb50, kb100, kb150, kb500, kb1000, spare } ENUMERATED { kb200, kb300, kb400, kb750 }
TotalRLC-AM-BufferSize-r5-ext ::=
-- Actual value TransmissionProbability = IE value * 0.125 TransmissionProbability ::= INTEGER (1..8) TransportChannelCapability ::= dl-TransChCapability ul-TransChCapability } TurboSupport ::= notSupported supported } SEQUENCE { DL-TransChCapability, UL-TransChCapability
CHOICE { NULL, MaxNoBits
-- Values defined as spare shall not be sent in this version of the protocol. If a spare value is -- received, it should be interpreted as 'default-RxTX-sparation'. TxRxFrequencySeparation ::= ENUMERATED { default-TxRx-separation, spare2, spare1 } U-RNTI ::= SEQUENCE {
3GPP
Release 6
srnc-Identity s-RNTI }
853
SRNC-Identity, S-RNTI
3GPP TS 25.331 V6.23.0 (2009-09)
U-RNTI-Group ::= CHOICE { -- TABULAR: not following the tabular strictly, but this all NULL, u-RNTI-BitMaskIndex-b1 BIT STRING (SIZE u-RNTI-BitMaskIndex-b2 BIT STRING (SIZE u-RNTI-BitMaskIndex-b3 BIT STRING (SIZE u-RNTI-BitMaskIndex-b4 BIT STRING (SIZE u-RNTI-BitMaskIndex-b5 BIT STRING (SIZE u-RNTI-BitMaskIndex-b6 BIT STRING (SIZE u-RNTI-BitMaskIndex-b7 BIT STRING (SIZE u-RNTI-BitMaskIndex-b8 BIT STRING (SIZE u-RNTI-BitMaskIndex-b9 BIT STRING (SIZE u-RNTI-BitMaskIndex-b10 BIT STRING (SIZE u-RNTI-BitMaskIndex-b11 BIT STRING (SIZE u-RNTI-BitMaskIndex-b12 BIT STRING (SIZE u-RNTI-BitMaskIndex-b13 BIT STRING (SIZE u-RNTI-BitMaskIndex-b14 BIT STRING (SIZE u-RNTI-BitMaskIndex-b15 BIT STRING (SIZE u-RNTI-BitMaskIndex-b16 BIT STRING (SIZE u-RNTI-BitMaskIndex-b17 BIT STRING (SIZE u-RNTI-BitMaskIndex-b18 BIT STRING (SIZE u-RNTI-BitMaskIndex-b19 BIT STRING (SIZE u-RNTI-BitMaskIndex-b20 BIT STRING (SIZE u-RNTI-BitMaskIndex-b21 BIT STRING (SIZE u-RNTI-BitMaskIndex-b22 BIT STRING (SIZE u-RNTI-BitMaskIndex-b23 BIT STRING (SIZE u-RNTI-BitMaskIndex-b24 BIT STRING (SIZE u-RNTI-BitMaskIndex-b25 BIT STRING (SIZE u-RNTI-BitMaskIndex-b26 BIT STRING (SIZE u-RNTI-BitMaskIndex-b27 BIT STRING (SIZE u-RNTI-BitMaskIndex-b28 BIT STRING (SIZE u-RNTI-BitMaskIndex-b29 BIT STRING (SIZE u-RNTI-BitMaskIndex-b30 BIT STRING (SIZE u-RNTI-BitMaskIndex-b31 BIT STRING (SIZE } U-RNTI-Short ::= srnc-Identity s-RNTI-2 } SEQUENCE { SRNC-Identity, S-RNTI-2
will most likely save bits (31)), (30)), (29)), (28)), (27)), (26)), (25)), (24)), (23)), (22)), (21)), (20)), (19)), (18)), (17)), (16)), (15)), (14)), (13)), (12)), (11)), (10)), (9)), (8)), (7)), (6)), (5)), (4)), (3)), (2)), (1))
UE-CapabilityContainer-IEs ::= SEQUENCE { -- Container for transparent transfer of capability information not related to -- features for which early implementation is desired ue-RadioAccessCapability-v690ext UE-RadioAccessCapability-v690ext, ue-RATSpecificCapability-v690ext InterRAT-UE-RadioAccessCapability-v690ext OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { ue-RadioAccessCapability-v6b0ext UE-RadioAccessCapability-v6b0ext-IEs, v6e0NonCriticalExtensions SEQUENCE { ue-RadioAccessCapability-v6e0ext UE-RadioAccessCapability-v6e0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } UE-RadioAccessCapability-v6b0ext-IEs ::= SEQUENCE { -- User equipment IEs supportForSIB11bis ENUMERATED { true } } UE-RadioAccessCapability-v6e0ext-IEs ::= SEQUENCE { -- User equipment IEs supportForFDPCH ENUMERATED { true } }
OPTIONAL
OPTIONAL
UE-ConnTimersAndConstants ::= SEQUENCE { -- Optional is used also for parameters for which the default value is the last one read in SIB1 -- t-301 and n-301 should not be used by the UE in this version of the specification t-301 T-301 DEFAULT ms2000, n-301 N-301 DEFAULT 2, t-302 T-302 DEFAULT ms4000, n-302 N-302 DEFAULT 3, t-304 T-304 DEFAULT ms2000, n-304 N-304 DEFAULT 2,
3GPP
Release 6
t-305 t-307 t-308 t-309 t-310 n-310 t-311 t-312 -- n-312 -- value n-312 t-313 n-313 t-314 t-315 -- n-315 -- value n-315 t-316 t-317 } UE-ConnTimersAndConstants-v3a0ext ::= n-312 n-315 }
854
3GPP TS 25.331 V6.23.0 (2009-09)

DEFAULT m30, DEFAULT s30, DEFAULT ms160, DEFAULT 5, DEFAULT ms160, DEFAULT 4, DEFAULT ms2000, DEFAULT 1, is present, and the DEFAULT s1, DEFAULT 3, DEFAULT s20, DEFAULT s12, DEFAULT s180, is present, and the DEFAULT s1, DEFAULT s30, DEFAULT infinity4
T-305 T-307 T-308 T-309 T-310 N-310 T-311 T-312 shall be ignored if n-312 in UE-ConnTimersAndConstants-v3a0ext of that element shall be used instead. N-312 T-313 N-313 T-314 T-315 shall be ignored if n-315 in UE-ConnTimersAndConstants-v3a0ext of that element shall be used instead. N-315 T-316 T-317
SEQUENCE { N-312ext N-315ext
OPTIONAL, OPTIONAL
UE-ConnTimersAndConstants-r5 ::= SEQUENCE { -- Optional is used also for parameters for which the default value is the last one read in SIB1 -- t-301 and n-301 should not be used by the UE in this version of the specification t-301 T-301 DEFAULT ms2000, n-301 N-301 DEFAULT 2, t-302 T-302 DEFAULT ms4000, n-302 N-302 DEFAULT 3, t-304 T-304 DEFAULT ms2000, n-304 N-304 DEFAULT 2, t-305 T-305 DEFAULT m30, t-307 T-307 DEFAULT s30, t-308 T-308 DEFAULT ms160, t-309 T-309 DEFAULT 5, t-310 T-310 DEFAULT ms160, n-310 N-310 DEFAULT 4, t-311 T-311 DEFAULT ms2000, t-312 T-312 DEFAULT 1, n-312 N-312-r5 DEFAULT s1, t-313 T-313 DEFAULT 3, n-313 N-313 DEFAULT s20, t-314 T-314 DEFAULT s12, t-315 T-315 DEFAULT s180, n-315 N-315-r5 DEFAULT s1, t-316 T-316 DEFAULT s30, t-317 T-317 DEFAULT infinity4 } UE-HSPA-Identities-r6 ::= SEQUENCE { new-H-RNTI H-RNTI newPrimary-E-RNTI E-RNTI newSecondary-E-RNTI E-RNTI }
UE-IdleTimersAndConstants ::= SEQUENCE { t-300 T-300, n-300 N-300, t-312 T-312, -- n-312 shall be ignored if n-312 in UE-IdleTimersAndConstants-v3a0ext is present, and the -- value of that element shall be used instead. n-312 N-312 } UE-IdleTimersAndConstants-v3a0ext ::= n-312 } UE-MultiModeRAT-Capability ::= multiRAT-CapabilityList multiModeCapability } SEQUENCE { N-312ext
OPTIONAL
SEQUENCE { MultiRAT-Capability, MultiModeCapability
3GPP
Release 6
UE-PowerClass ::= UE-PowerClassExt ::=
855
INTEGER (1..4)
3GPP TS 25.331 V6.23.0 (2009-09)
ENUMERATED {class1, class2, class3, class4, spare4, spare3, spare2, spare1 }
UE-RadioAccessCapability ::= SEQUENCE { -- UE-RadioAccessCapability is compatible with R99, although accessStratumReleaseIndicator -- is removed from this IE, since its encoding did not does in bits. The -- accessStratumReleaseIndicator is provided in the relevant REL-4 extension IEs. pdcp-Capability PDCP-Capability, rlc-Capability RLC-Capability, transportChannelCapability TransportChannelCapability, rf-Capability RF-Capability, physicalChannelCapability PhysicalChannelCapability, ue-MultiModeRAT-Capability UE-MultiModeRAT-Capability, securityCapability SecurityCapability, ue-positioning-Capability UE-Positioning-Capability, measurementCapability MeasurementCapability OPTIONAL } UE-RadioAccessCapabilityInfo ::= ue-RadioAccessCapability ue-RadioAccessCapability-v370ext } UE-RadioAccessCapability-v370ext ::= ue-RadioAccessCapabBandFDDList } UE-RadioAccessCapability-v380ext ::= ue-PositioningCapabilityExt-v380 } UE-RadioAccessCapability-v3a0ext ::= ue-PositioningCapabilityExt-v3a0 } UE-RadioAccessCapability-v3g0ext ::= ue-PositioningCapabilityExt-v3g0 } UE-RadioAccessCapability-v650ext ::= ue-RadioAccessCapabBandFDDList2 -- This IE shall be included if the ue-RadioAccessCapabBandFDDList-ext } SEQUENCE { UE-RadioAccessCapability, UE-RadioAccessCapability-v370ext
SEQUENCE { UE-RadioAccessCapabBandFDDList
SEQUENCE { UE-PositioningCapabilityExt-v380
SEQUENCE { UE-PositioningCapabilityExt-v3a0
SEQUENCE { UE-PositioningCapabilityExt-v3g0
SEQUENCE { UE-RadioAccessCapabBandFDDList2, UE also supports Band I-VII UE-RadioAccessCapabBandFDDList-ext
OPTIONAL
UE-RadioAccessCapability-v690ext ::= SEQUENCE { physicalchannelcapability-edch PhysicalChannelCapability-edch-r6, -- TABULAR: deviceType is MD in tabular description -- Default value is 'doesBenefitFromBatteryConsumptionOptimisation' deviceType ENUMERATED { doesNotBenefitFromBatteryConsumptionOptimisation } OPTIONAL } UE-RadioAccessCapabBandFDDList2 ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF UE-RadioAccessCapabBandFDD2 UE-RadioAccessCapabBandFDD2 ::= SEQUENCE { radioFrequencyBandFDD2 RadioFrequencyBandFDD2, fddRF-Capability SEQUENCE { ue-PowerClass UE-PowerClassExt, txRxFrequencySeparation TxRxFrequencySeparation } OPTIONAL, measurementCapability2 MeasurementCapabilityExt2 }
UE-PositioningCapabilityExt-v380 ::= rx-tx-TimeDifferenceType2Capable } UE-PositioningCapabilityExt-v3a0 ::= validity-CellPCH-UraPCH } UE-PositioningCapabilityExt-v3g0 ::= sfn-sfnType2Capability }
SEQUENCE { BOOLEAN
SEQUENCE { ENUMERATED { true }
SEQUENCE { ENUMERATED { true }
3GPP
Release 6
856
3GPP TS 25.331 V6.23.0 (2009-09)
UE-RadioAccessCapabBandFDDList ::=
SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF UE-RadioAccessCapabBandFDD
UE-RadioAccessCapabBandFDDList-ext ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF UE-RadioAccessCapabBandFDD-ext UE-RadioAccessCapabBandFDD ::= SEQUENCE{ radioFrequencyBandFDD RadioFrequencyBandFDD, fddRF-Capability SEQUENCE { ue-PowerClass UE-PowerClassExt, txRxFrequencySeparation TxRxFrequencySeparation } OPTIONAL, measurementCapability MeasurementCapabilityExt } UE-RadioAccessCapabBandFDD-ext ::= SEQUENCE { radioFrequencyBandFDD RadioFrequencyBandFDD, compressedModeMeasCapabFDDList-ext CompressedModeMeasCapabFDDList-ext } UE-RadioAccessCapability-v4b0ext ::= SEQUENCE { pdcp-Capability-r4-ext PDCP-Capability-r4-ext, tdd-CapabilityExt SEQUENCE { rf-Capability RF-Capability-r4-ext, physicalChannelCapability-LCR PhysicalChannelCapability-LCR-r4, measurementCapability-r4-ext MeasurementCapability-r4-ext } OPTIONAL, -- IE " AccessStratumReleaseIndicator" is not needed in RRC CONNECTION SETUP COMPLETE accessStratumReleaseIndicator AccessStratumReleaseIndicator OPTIONAL } UE-RadioAccessCapabilityComp ::= SEQUENCE { totalAM-RLCMemoryExceeds10kB BOOLEAN, rf-CapabilityComp RF-CapabilityComp } UE-RadioAccessCapabilityComp-ext ::= SEQUENCE { rf-CapabilityFDDComp RF-CapabBandListFDDComp-ext } UE-RadioAccessCapabilityComp2 ::= SEQUENCE { fddPhysicalChannelCapab-hspdsch-edch SEQUENCE { dl-CapabilityWithSimultaneousHS-DSCHConfig DL-CapabilityWithSimultaneousHS-DSCHConfig OPTIONAL, physicalChannelCapabComp-hspdsch-r6 HSDSCH-physical-layer-category, physicalChannelCapability-edch-r6 PhysicalChannelCapability-edch-r6 } OPTIONAL } RF-CapabilityComp ::= SEQUENCE { fdd CHOICE { notSupported supported }, tdd384-RF-Capability CHOICE { notSupported supported }, tdd128-RF-Capability CHOICE { notSupported supported } }
NULL, RF-CapabBandListFDDComp
NULL, RadioFrequencyBandTDDList
NULL, RadioFrequencyBandTDDList
-- NOTE: This IE defines the supported TX/RX frequency separation for the respective supported -- frequency band. Values defined as spare shall not be sent in this version of the protocol. -- If a spare value is received, it should be interpreted as 'default-RxTX-sparation'. RF-CapabBandFDDComp ::= ENUMERATED { notSupported, default-TxRx-separation, spare2, spare1 } RF-CapabBandListFDDComp ::= SEQUENCE (SIZE (1..maxFreqBandsFDD)) OF -- The first entry corresponds with the first value of IE RadioFrequencyBandFDD, -- fdd2100, and so on. No more than seven entries should be included in this IE. The -- 8'th entry, if present, shall be ignored. -- An extension of this IE may be provided using the IE 'RF-CapabBandListFDDComp-ext'. RF-CapabBandFDDComp
3GPP
Release 6
857
3GPP TS 25.331 V6.23.0 (2009-09)
RF-CapabBandListFDDComp-ext ::= SEQUENCE (SIZE (1..maxFreqBandsFDD-ext)) OF -- The first entry corresponds with the first value of IE RadioFrequencyBandFDD2, -- bandVIII, and so on. RF-CapabBandFDDComp UE-RadioAccessCapability-v590ext ::= SEQUENCE { dl-CapabilityWithSimultaneousHS-DSCHConfig DL-CapabilityWithSimultaneousHS-DSCHConfig OPTIONAL, pdcp-Capability-r5-ext PDCP-Capability-r5-ext, rlc-Capability-r5-ext RLC-Capability-r5-ext, physicalChannelCapability PhysicalChannelCapability-hspdsch-r5, multiModeRAT-Capability-v590ext MultiModeRAT-Capability-v590ext } UE-RadioAccessCapability-v5c0ext ::= SEQUENCE { pdcp-Capability-r5-ext2 PDCP-Capability-r5-ext2 } UE-RadioAccessCapability-v680ext ::= SEQUENCE { multiModeRAT-Capability-v680ext MultiModeRAT-Capability-v680ext } UL-PhysChCapabilityFDD ::= SEQUENCE { maxNoDPDCH-BitsTransmitted MaxNoDPDCH-BitsTransmitted, -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy BOOLEAN } UL-PhysChCapabilityFDD-r6 ::= maxNoDPDCH-BitsTransmitted physicalchannelcapability-edch } UL-PhysChCapabilityTDD ::= maxTS-PerFrame maxPhysChPerTimeslot minimumSF supportOfPUSCH } UL-PhysChCapabilityTDD-LCR-r4 ::= maxTS-PerSubFrame maxPhysChPerTimeslot minimumSF supportOfPUSCH supportOf8PSK } SEQUENCE { MaxNoDPDCH-BitsTransmitted, PhysicalChannelCapability-edch-r6
SEQUENCE { MaxTS-PerFrame, MaxPhysChPerTimeslot, MinimumSF-UL, BOOLEAN
SEQUENCE { MaxTS-PerSubFrame-r4, MaxPhysChPerTimeslot, MinimumSF-UL, BOOLEAN, BOOLEAN
PhysicalChannelCapability-edch-r6 ::= fdd-edch supported edch-PhysicalLayerCategory }, unsupported } }
SEQUENCE { CHOICE { SEQUENCE { INTEGER (1..16) NULL
UL-TransChCapability ::= SEQUENCE { maxNoBitsTransmitted MaxNoBits, maxConvCodeBitsTransmitted MaxNoBits, turboEncodingSupport TurboSupport, maxSimultaneousTransChs MaxSimultaneousTransChsUL, modeSpecificInfo CHOICE { fdd NULL, tdd SEQUENCE { maxSimultaneousCCTrCH-Count MaxSimultaneousCCTrCH-Count } }, maxTransmittedBlocks MaxTransportBlocksUL, maxNumberOfTFC MaxNumberOfTFC-UL, maxNumberOfTF MaxNumberOfTF } UE-Positioning-Capability ::= standaloneLocMethodsSupported ue-BasedOTDOA-Supported SEQUENCE { BOOLEAN, BOOLEAN,
3GPP
Release 6
networkAssistedGPS-Supported supportForUE-GPS-TimingOfCellFrames supportForIPDL } UE-SecurityInformation ::= start-CS } UE-SecurityInformation2 ::= start-PS } URA-UpdateCause ::=
858
3GPP TS 25.331 V6.23.0 (2009-09)
NetworkAssistedGPS-Supported, BOOLEAN, BOOLEAN
SEQUENCE { START-Value
SEQUENCE { START-Value
ENUMERATED { changeOfURA, periodicURAUpdate, dummy, spare1 }
UTRAN-DRX-CycleLengthCoefficient ::= INTEGER (3..9) WaitTime ::= INTEGER (0..15)
-- *************************************************** --RADIO BEARER INFORMATION ELEMENTS (10.3.4) --- *************************************************** AlgorithmSpecificInfo ::= rfc2507-Info } AlgorithmSpecificInfo-r4 ::= rfc2507-Info rfc3095-Info } CID-InclusionInfo-r4 ::= CHOICE { RFC2507-Info
CHOICE { RFC2507-Info, RFC3095-Info-r4
ENUMERATED { pdcp-Header, rfc3095-PacketFormat }
-- Upper limit of COUNT-C is 2^32 - 1 COUNT-C ::= INTEGER (0..4294967295) -- Upper limit of COUNT-C-MSB is 2^25 - 1 COUNT-C-MSB ::= INTEGER (0..33554431) DefaultConfigIdentity ::= DefaultConfigIdentity-r4 ::= DefaultConfigIdentity-r5 ::= INTEGER (0..10) INTEGER (0..12) INTEGER (0..13)
-- DefaultConfigIdentity-r6 values 23..31 are spare and shall not be used in this version of -- the protocol DefaultConfigIdentity-r6 ::= INTEGER (0..31) DefaultConfigMode ::= ENUMERATED { fdd, tdd } INTEGER (0..62) SEQUENCE { BOOLEAN, ReceivingWindowSize, DL-RLC-StatusInfo
DDI ::= DL-AM-RLC-Mode ::= inSequenceDelivery receivingWindowSize dl-RLC-StatusInfo } DL-AM-RLC-Mode-r5 ::= dl-RLC-PDU-size inSequenceDelivery receivingWindowSize dl-RLC-StatusInfo } DL-CounterSynchronisationInfo ::=
SEQUENCE { OctetModeRLC-SizeInfoType1, BOOLEAN, ReceivingWindowSize, DL-RLC-StatusInfo
SEQUENCE {
3GPP
Release 6
rB-WithPDCP-InfoList } DL-CounterSynchronisationInfo-r5 ::= rb-WithPDCP-InfoList rb-PDCPContextRelocationList }
859
RB-WithPDCP-InfoList
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
SEQUENCE { RB-WithPDCP-InfoList RB-PDCPContextRelocationList
OPTIONAL, OPTIONAL
DL-LogicalChannelMapping ::= SEQUENCE { -- TABULAR: DL-TransportChannelType contains TransportChannelIdentity as well. dl-TransportChannelType DL-TransportChannelType, logicalChannelIdentity LogicalChannelIdentity OPTIONAL } DL-LogicalChannelMapping-r5 ::= SEQUENCE { -- TABULAR: DL-TransportChannelType contains TransportChannelIdentity as well. dl-TransportChannelType DL-TransportChannelType-r5, logicalChannelIdentity LogicalChannelIdentity OPTIONAL } DL-LogicalChannelMappingList ::= SEQUENCE (SIZE (1..maxLoCHperRLC)) OF DL-LogicalChannelMapping
DL-LogicalChannelMappingList-r5 ::= SEQUENCE (SIZE (1..maxLoCHperRLC)) OF DL-LogicalChannelMapping-r5 DL-Reception-Window-Size-r6 ::= ENUMERATED { size32, size48, size64, size80, size96, size112 }
DL-RFC3095-r4 ::= SEQUENCE { -- dummy is not used in this version of the specification and should be ignored by the receiver. dummy CID-InclusionInfo-r4, max-CID INTEGER (1..16383) DEFAULT 15, reverseDecompressionDepth INTEGER (0..65535) DEFAULT 0 } DL-RLC-Mode ::= dl-AM-RLC-Mode dl-UM-RLC-Mode dl-TM-RLC-Mode } DL-RLC-Mode-r5 ::= dl-AM-RLC-Mode dl-UM-RLC-Mode dl-TM-RLC-Mode } DL-RLC-Mode-r6 ::= dl-AM-RLC-Mode dl-UM-RLC-Mode dl-TM-RLC-Mode } CHOICE { DL-AM-RLC-Mode, NULL, DL-TM-RLC-Mode
CHOICE { DL-AM-RLC-Mode-r5, DL-UM-RLC-Mode-r5, DL-TM-RLC-Mode
CHOICE { DL-AM-RLC-Mode-r5, DL-UM-RLC-Mode-r6, DL-TM-RLC-Mode
DL-RLC-StatusInfo ::= SEQUENCE { timerStatusProhibit TimerStatusProhibit OPTIONAL, -- dummy is not used in this version of the specification, it should not be sent -- and if received they should be ignored. dummy TimerEPC OPTIONAL, missingPDU-Indicator BOOLEAN, timerStatusPeriodic TimerStatusPeriodic OPTIONAL } DL-TM-RLC-Mode ::= segmentationIndication } SEQUENCE { BOOLEAN
DL-TransportChannelType ::= CHOICE { dch TransportChannelIdentity, fach NULL, -- The choice dsch should not be used in FDD mode, and if received -- the UE behaviour is unspecified. dsch TransportChannelIdentity, -- The choice dch-and-dsch should not be used in FDD mode, and if received the UE -- behaviour is unspecified dch-and-dsch TransportChannelIdentityDCHandDSCH } DL-TransportChannelType-r5 ::= CHOICE {
3GPP
Release 6
860
3GPP TS 25.331 V6.23.0 (2009-09)
dch TransportChannelIdentity, fach NULL, -- The choice dsch should not be used in FDD mode, and if received -- the UE behaviour is unspecified. dsch TransportChannelIdentity, -- The choice dch-and-dsch should not be used in FDD mode, and if received the UE -- behaviour is unspecified dch-and-dsch TransportChannelIdentityDCHandDSCH, hsdsch MAC-d-FlowIdentity, dch-and-hsdsch MAC-d-FlowIdentityDCHandHSDSCH } DL-UM-RLC-LI-size ::= ENUMERATED { size7, size15 } SEQUENCE { DL-UM-RLC-LI-size
DL-UM-RLC-Mode-r5 ::= dl-UM-RLC-LI-size } DL-UM-RLC-Mode-r6 ::= dl-UM-RLC-LI-size dl-Reception-Window-Size } ExpectReordering ::=
SEQUENCE { DL-UM-RLC-LI-size, DL-Reception-Window-Size-r6
OPTIONAL
ENUMERATED { reorderingNotExpected, reorderingExpected } SEQUENCE { TimerMRW, TimerDiscard, MaxMRW
ExplicitDiscard ::= timerMRW timerDiscard maxMRW } HeaderCompressionInfo ::= algorithmSpecificInfo } HeaderCompressionInfoList ::=
SEQUENCE { AlgorithmSpecificInfo
SEQUENCE (SIZE (1..maxPDCPAlgoType)) OF HeaderCompressionInfo SEQUENCE { AlgorithmSpecificInfo-r4
HeaderCompressionInfo-r4 ::= algorithmSpecificInfo } HeaderCompressionInfoList-r4 ::=
SEQUENCE (SIZE (1..maxPDCPAlgoType)) OF HeaderCompressionInfo-r4 INTEGER (1..15) CHOICE { MaxPDCP-SN-WindowSize, NULL
LogicalChannelIdentity ::= LosslessSRNS-RelocSupport ::= supported notSupported } MAC-d-HFN-initial-value ::= MAC-LogicalChannelPriority ::= MaxDAT ::=
BIT STRING (SIZE (24)) INTEGER (1..8) ENUMERATED { dat1, dat2, dat3, dat4, dat5, dat6, dat7, dat8, dat9, dat10, dat15, dat20, dat25, dat30, dat35, dat40 } SEQUENCE { MaxDAT, TimerMRW, MaxMRW
MaxDAT-Retransmissions ::= maxDAT timerMRW maxMRW } MaxMRW ::=
ENUMERATED { mm1, mm4, mm6, mm8, mm12, mm16, mm24, mm32 } ENUMERATED { sn255, sn65535 } ENUMERATED {
MaxPDCP-SN-WindowSize ::=
MaxRST ::=
3GPP
Release 6
861
rst1, rst4, rst6, rst8, rst12, rst16, rst24, rst32 }
3GPP TS 25.331 V6.23.0 (2009-09)
NoExplicitDiscard ::=
ENUMERATED { dt10, dt20, dt30, dt40, dt50, dt60, dt70, dt80, dt90, dt100 }
PDCP-Info ::= SEQUENCE { losslessSRNS-RelocSupport LosslessSRNS-RelocSupport OPTIONAL, -- TABULAR: pdcp-PDU-Header is MD in the tabular format and it can be encoded -- in one bit, so the OPTIONAL is removed for compactness. pdcp-PDU-Header PDCP-PDU-Header, headerCompressionInfoList HeaderCompressionInfoList OPTIONAL } PDCP-Info-r4 ::= SEQUENCE { losslessSRNS-RelocSupport LosslessSRNS-RelocSupport OPTIONAL, -- TABULAR: pdcp-PDU-Header is MD in the tabular format and it can be encoded -- in one bit, so the OPTIONAL is removed for compactness. pdcp-PDU-Header PDCP-PDU-Header, headerCompressionInfoList HeaderCompressionInfoList-r4 OPTIONAL } PDCP-InfoReconfig ::= SEQUENCE { pdcp-Info PDCP-Info, -- dummy is not used in this version of the specification and -- it should be ignored. dummy INTEGER (0..65535) } PDCP-InfoReconfig-r4 ::= pdcp-Info } PDCP-PDU-Header ::= SEQUENCE { PDCP-Info-r4
ENUMERATED { present, absent } ENUMERATED { o-Mode, r-Mode } INTEGER (0..65535) ENUMERATED { pdu1, pdu2, pdu4, pdu8, pdu16, pdu32, pdu64, pdu128 } ENUMERATED { sdu1, sdu4, sdu16, sdu64 } SEQUENCE { TimerPollProhibit TimerPoll Poll-PDU Poll-SDU BOOLEAN, BOOLEAN, PollWindow TimerPollPeriodic
PDCP-ROHC-TargetMode ::= PDCP-SN-Info ::= Poll-PDU ::=
Poll-SDU ::=
PollingInfo ::= timerPollProhibit timerPoll poll-PDU poll-SDU lastTransmissionPDU-Poll lastRetransmissionPDU-Poll pollWindow timerPollPeriodic } PollWindow ::=
OPTIONAL, OPTIONAL
ENUMERATED { pw50, pw60, pw70, pw80, pw85, pw90, pw95, pw99 } INTEGER (0..15) INTEGER (0..15) SEQUENCE { Re-EstablishmentTimer, SRB-InformationSetupList, RB-InformationSetupList
PredefinedConfigIdentity ::= PredefinedConfigValueTag ::= PredefinedRB-Configuration ::= re-EstablishmentTimer srb-InformationList rb-InformationList } PreDefRadioConfiguration ::= -- Radio bearer IEs predefinedRB-Configuration -- Transport channel IEs preDefTransChConfiguration
SEQUENCE { PredefinedRB-Configuration, PreDefTransChConfiguration,
3GPP
Release 6
-- Physical channel IEs preDefPhyChConfiguration } PredefinedConfigStatusList ::=
862
3GPP TS 25.331 V6.23.0 (2009-09)
PreDefPhyChConfiguration
SEQUENCE (SIZE (maxPredefConfig)) OF PredefinedConfigStatusInfo
PredefinedConfigStatusInfo ::= CHOICE { storedWithValueTagSameAsPrevius NULL, other CHOICE { notStored NULL, storedWithDifferentValueTag PredefinedConfigValueTag } } PredefinedConfigStatusListComp ::= SEQUENCE { setsWithDifferentValueTag PredefinedConfigSetsWithDifferentValueTag, otherEntries PredefinedConfigStatusListVarSz }
OPTIONAL
PredefinedConfigSetsWithDifferentValueTag ::= SEQUENCE (SIZE (1..2)) OF PredefinedConfigSetWithDifferentValueTag PredefinedConfigSetWithDifferentValueTag ::= SEQUENCE { startPosition INTEGER (0..10) DEFAULT 0, -- numberOfEntries INTEGER (6..16), -- numberOfEntries is covered by the size of the list in IE PredefinedConfigValueTagList valueTagList PredefinedConfigValueTagList }
PredefinedConfigValueTagList ::=
SEQUENCE (SIZE (1..maxPredefConfig)) OF PredefinedConfigValueTag SEQUENCE (SIZE (1..maxPredefConfig)) OF PredefinedConfigStatusInfo SEQUENCE { RAB-Identity, CN-DomainIdentity, NAS-Synchronisation-Indicator Re-EstablishmentTimer
PredefinedConfigStatusListVarSz ::=
RAB-Info ::= rab-Identity cn-DomainIdentity nas-Synchronisation-Indicator re-EstablishmentTimer } RAB-Info-r6-ext ::= mbms-SessionIdentity } RAB-Info-v6b0ext ::= mbms-ServiceIdentity } RAB-Info-r6 ::= rab-Identity mbms-SessionIdentity cn-DomainIdentity nas-Synchronisation-Indicator re-EstablishmentTimer } RAB-InformationList ::=
OPTIONAL,
SEQUENCE { MBMS-SessionIdentity
OPTIONAL
SEQUENCE { OCTET STRING (SIZE (3))
SEQUENCE { RAB-Identity, MBMS-SessionIdentity CN-DomainIdentity, NAS-Synchronisation-Indicator Re-EstablishmentTimer
OPTIONAL, OPTIONAL,
SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-Info SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-Info-r6 SEQUENCE (SIZE (1.. maxRABsetup)) OF RAB-InformationReconfig SEQUENCE { RAB-Identity, CN-DomainIdentity, NAS-Synchronisation-Indicator
RAB-InformationList-r6 ::=
RAB-InformationReconfigList ::=
RAB-InformationReconfig ::= rab-Identity cn-DomainIdentity nas-Synchronisation-Indicator } RAB-Info-Post ::= rab-Identity cn-DomainIdentity
SEQUENCE { RAB-Identity, CN-DomainIdentity,
3GPP
Release 6
nas-Synchronisation-Indicator } RAB-InformationMBMSPtp ::= rb-Identity mbms-ServiceIdentity mbms-SessionIdentity } RAB-InformationMBMSPtpList ::=
863
NAS-Synchronisation-Indicator
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
SEQUENCE { RB-Identity, OCTET STRING (SIZE (3)), MBMS-SessionIdentity
OPTIONAL
SEQUENCE (SIZE (1..maxMBMSservSelect)) OF RAB-InformationMBMSPtp SEQUENCE { RAB-Info, RB-InformationSetupList
RAB-InformationSetup ::= rab-Info rb-InformationSetupList } RAB-InformationSetup-r4 ::= rab-Info rb-InformationSetupList } RAB-InformationSetup-r5 ::= rab-Info rb-InformationSetupList } RAB-InformationSetup-r6-ext ::= rab-Info-r6-ext } RAB-InformationSetup-r6 ::= rab-Info rb-InformationSetupList } RAB-InformationSetup-v6b0ext ::= rab-Info-v6b0ext } RAB-InformationSetupList ::=
SEQUENCE { RAB-Info, RB-InformationSetupList-r4
SEQUENCE { RAB-Info, RB-InformationSetupList-r5
SEQUENCE { RAB-Info-r6-ext
SEQUENCE { RAB-Info-r6, RB-InformationSetupList-r6
SEQUENCE { RAB-Info-v6b0ext
OPTIONAL
SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup-r4 SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup-r5 SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup-r6
RAB-InformationSetupList-r4 ::=
-- The IE 'RAB-InformationSetupList-r6-ext' provides elements of extension information, which -- are added to the corresponding elements of the IE 'RAB-InformationSetupList/-r4/-r5'. RAB-InformationSetupList-r6-ext ::= SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup-r6-ext RAB-InformationSetupList-v6b0ext ::= SEQUENCE (SIZE (1..maxRABsetup)) OF RAB-InformationSetup-v6b0ext RB-ActivationTimeInfo ::= rb-Identity rlc-SequenceNumber } RB-ActivationTimeInfoList ::= SEQUENCE { RB-Identity, RLC-SequenceNumber
SEQUENCE (SIZE (1..maxRB)) OF RB-ActivationTimeInfo SEQUENCE { RB-Identity, COUNT-C, COUNT-C
RB-COUNT-C-Information ::= rb-Identity count-C-UL count-C-DL } RB-COUNT-C-InformationList ::=
SEQUENCE (SIZE (1..maxRBallRABs)) OF RB-COUNT-C-Information SEQUENCE {
RB-COUNT-C-MSB-Information ::=
3GPP
Release 6
rb-Identity count-C-MSB-UL count-C-MSB-DL } RB-COUNT-C-MSB-InformationList ::=
864
RB-Identity, COUNT-C-MSB, COUNT-C-MSB
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxRBallRABs)) OF RB-COUNT-C-MSB-Information INTEGER (1..32) SEQUENCE (SIZE (1..maxRB)) OF RB-Identity SEQUENCE { RB-Identity, RB-MappingInfo
RB-Identity ::= RB-IdentityList ::=
RB-InformationAffected ::= rb-Identity rb-MappingInfo } RB-InformationAffected-r5 ::= rb-Identity rb-MappingInfo } RB-InformationAffected-r6 ::= rb-Identity rb-MappingInfo } RB-InformationAffectedList ::=
SEQUENCE { RB-Identity, RB-MappingInfo-r5
SEQUENCE { RB-Identity, RB-MappingInfo-r6
SEQUENCE (SIZE (1..maxRB)) OF RB-InformationAffected SEQUENCE (SIZE (1..maxRB)) OF RB-InformationAffected-r5 SEQUENCE (SIZE (1..maxRB)) OF RB-InformationAffected-r6 SEQUENCE { RB-Identity, CHOICE { NULL, RB-Identity
RB-InformationAffectedList-r5 ::=
RB-InformationAffectedList-r6 ::=
RB-InformationChanged-r6 ::= rb-Identity rb-Change release re-mapToDefaultRb } } RB-InformationChangedList-r6 ::=
SEQUENCE (SIZE (1..maxRB)) OF RB-InformationChanged-r6 SEQUENCE { RB-Identity, PDCP-InfoReconfig PDCP-SN-Info RLC-Info RB-MappingInfo RB-StopContinue
RB-InformationReconfig ::= rb-Identity pdcp-Info pdcp-SN-Info rlc-Info rb-MappingInfo rb-StopContinue } RB-InformationReconfig-r4 ::= rb-Identity pdcp-Info pdcp-SN-Info rlc-Info rb-MappingInfo rb-StopContinue } RB-InformationReconfig-r5 ::= rb-Identity pdcp-Info pdcp-SN-Info rlc-Info rb-MappingInfo rb-StopContinue } RB-InformationReconfig-r6 ::= rb-Identity pdcp-Info
SEQUENCE { RB-Identity, PDCP-InfoReconfig-r4 PDCP-SN-Info RLC-Info RB-MappingInfo RB-StopContinue
SEQUENCE { RB-Identity, PDCP-InfoReconfig-r4 PDCP-SN-Info RLC-Info-r5 RB-MappingInfo-r5 RB-StopContinue
SEQUENCE { RB-Identity, PDCP-InfoReconfig-r4
OPTIONAL,
3GPP
Release 6
pdcp-SN-Info rlc-Info rb-MappingInfo rb-StopContinue } RB-InformationReconfigList ::=
865
PDCP-SN-Info RLC-Info-r6 RB-MappingInfo-r6 RB-StopContinue
3GPP TS 25.331 V6.23.0 (2009-09)

SEQUENCE (SIZE (1..maxRB)) OF RB-InformationReconfig SEQUENCE (SIZE (1..maxRB)) OF RB-InformationReconfig-r4 SEQUENCE (SIZE (1..maxRB)) OF RB-InformationReconfig-r5 SEQUENCE (SIZE (1..maxRB)) OF RB-InformationReconfig-r6 SEQUENCE (SIZE (1..maxRB)) OF RB-Identity SEQUENCE { RB-Identity, PDCP-Info RLC-InfoChoice, RB-MappingInfo
RB-InformationReconfigList-r4 ::=
RB-InformationReleaseList ::=
RB-InformationSetup ::= rb-Identity pdcp-Info rlc-InfoChoice rb-MappingInfo } RB-InformationSetup-r4 ::= rb-Identity pdcp-Info rlc-InfoChoice rb-MappingInfo } RB-InformationSetup-r5 ::= rb-Identity pdcp-Info rlc-InfoChoice rb-MappingInfo } RB-InformationSetup-r6 ::= rb-Identity pdcp-Info rlc-InfoChoice rb-MappingInfo } RB-InformationSetupList ::=
OPTIONAL,
SEQUENCE { RB-Identity, PDCP-Info-r4 RLC-InfoChoice, RB-MappingInfo
OPTIONAL,
SEQUENCE { RB-Identity, PDCP-Info-r4 RLC-InfoChoice-r5, RB-MappingInfo-r5
OPTIONAL,
SEQUENCE { RB-Identity, PDCP-Info-r4 RLC-InfoChoice-r6, RB-MappingInfo-r6
OPTIONAL,
SEQUENCE (SIZE (1..maxRBperRAB)) OF RB-InformationSetup SEQUENCE (SIZE (1..maxRBperRAB)) OF RB-InformationSetup-r4 SEQUENCE (SIZE (1..maxRBperRAB)) OF RB-InformationSetup-r5 SEQUENCE (SIZE (1..maxRBperRAB)) OF RB-InformationSetup-r6 SEQUENCE (SIZE (1..maxRBMuxOptions)) OF RB-MappingOption SEQUENCE (SIZE (1..maxRBMuxOptions)) OF RB-MappingOption-r5 SEQUENCE (SIZE (1..maxRBMuxOptions)) OF RB-MappingOption-r6 SEQUENCE { UL-LogicalChannelMappings DL-LogicalChannelMappingList
RB-InformationSetupList-r4 ::=
RB-MappingInfo ::=
RB-MappingInfo-r5 ::=
RB-MappingInfo-r6 ::=
RB-MappingOption ::= ul-LogicalChannelMappings dl-LogicalChannelMappingList } RB-MappingOption-r5 ::= ul-LogicalChannelMappings dl-LogicalChannelMappingList
OPTIONAL, OPTIONAL
SEQUENCE { UL-LogicalChannelMappings DL-LogicalChannelMappingList-r5
OPTIONAL, OPTIONAL
3GPP
Release 6
} RB-MappingOption-r6 ::= ul-LogicalChannelMappings dl-LogicalChannelMappingList } RB-PDCPContextRelocation ::= rb-Identity dl-RFC3095-Context-Relocation ul-RFC3095-Context-Relocation } RB-PDCPContextRelocationList ::=
866
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { UL-LogicalChannelMappings-r6 DL-LogicalChannelMappingList-r5
OPTIONAL, OPTIONAL
SEQUENCE { RB-Identity, BOOLEAN, BOOLEAN
SEQUENCE (SIZE (1..maxRBallRABs)) OF RB-PDCPContextRelocation ENUMERATED { stopRB, continueRB } SEQUENCE { RB-Identity, PDCP-SN-Info
RB-StopContinue ::=
RB-WithPDCP-Info ::= rb-Identity pdcp-SN-Info } RB-WithPDCP-InfoList ::=
SEQUENCE (SIZE (1..maxRBallRABs)) OF RB-WithPDCP-Info ENUMERATED { rw1, rw8, rw16, rw32, rw64, rw128, rw256, rw512, rw768, rw1024, rw1536, rw2047, rw2560, rw3072, rw3584, rw4095 }
ReceivingWindowSize ::=
RFC2507-Info ::= SEQUENCE { f-MAX-PERIOD INTEGER (1..65535) DEFAULT f-MAX-TIME INTEGER (1..255) DEFAULT max-HEADER INTEGER (60..65535) DEFAULT tcp-SPACE INTEGER (3..255) DEFAULT non-TCP-SPACE INTEGER (3..65535) DEFAULT -- TABULAR: expectReordering has only two possible values, so using Optional or -- would be wasteful expectReordering ExpectReordering } RFC3095-Info-r4 ::= rohcProfileList ul-RFC3095 dl-RFC3095 } RLC-Info ::= ul-RLC-Mode dl-RLC-Mode } RLC-Info-r5 ::= ul-RLC-Mode dl-RLC-Mode rlc-OneSidedReEst } RLC-Info-r6 ::= ul-RLC-Mode dl-RLC-Mode rlc-OneSidedReEst altE-bitInterpretation } RLC-Info-MCCH-r6 ::= dl-UM-RLC-LI-size dl-UM-RLC-OutOSeqDelivery-Info } RLC-Info-MSCH-r6 ::= dl-UM-RLC-LI-size } RLC-Info-MTCH-r6 ::= dl-UM-RLC-LI-size SEQUENCE { ROHC-ProfileList-r4, UL-RFC3095-r4 DL-RFC3095-r4
256, 5, 168, 15, 15, Default
OPTIONAL, OPTIONAL
SEQUENCE { UL-RLC-Mode DL-RLC-Mode
OPTIONAL, OPTIONAL
SEQUENCE { UL-RLC-Mode DL-RLC-Mode-r5 BOOLEAN
OPTIONAL, OPTIONAL,
SEQUENCE { UL-RLC-Mode DL-RLC-Mode-r6 BOOLEAN, ENUMERATED { true }
SEQUENCE { DL-UM-RLC-LI-size, UM-RLC-OutOSeqDelivery-Info-r6
OPTIONAL
SEQUENCE { DL-UM-RLC-LI-size
SEQUENCE { DL-UM-RLC-LI-size,
3GPP
Release 6
dl-UM-RLC-DuplAvoid-Reord-Info } RLC-InfoChoice ::= rlc-Info same-as-RB } RLC-InfoChoice-r5 ::= rlc-Info same-as-RB } RLC-InfoChoice-r6 ::= rlc-Info same-as-RB } RLC-PDU-Size ::= RLC-PDU-SizeList ::=
867
UM-RLC-DuplAvoid-Reord-Info-r6
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
CHOICE { RLC-Info, RB-Identity
CHOICE { RLC-Info-r5, RB-Identity
CHOICE { RLC-Info-r6, RB-Identity
OctetModeRLC-SizeInfoType1 SEQUENCE (SIZE (1..maxRLCPDUsizePerLogChan)) OF RLC-PDU-Size INTEGER (0..4095) SEQUENCE { INTEGER (1..maxTF)
RLC-SequenceNumber ::= RLC-SizeInfo ::= rlc-SizeIndex } RLC-SizeExplicitList ::=
SEQUENCE (SIZE (1..maxTF)) OF RLC-SizeInfo INTEGER (1..3) SEQUENCE (SIZE (1..maxROHC-Profile-r4)) ROHC-Profile-r4 INTEGER (2..1500) SEQUENCE (SIZE (1..maxROHC-PacketSizes-r4)) ROHC-PacketSize-r4 OF OF
ROHC-Profile-r4 ::= ROHC-ProfileList-r4 ::=
ROHC-PacketSize-r4 ::= ROHC-PacketSizeList-r4 ::=
SRB-InformationSetup ::= SEQUENCE { -- The default value for rb-Identity is the smallest value not used yet. rb-Identity RB-Identity OPTIONAL, rlc-InfoChoice RLC-InfoChoice, rb-MappingInfo RB-MappingInfo } SRB-InformationSetup-r5 ::= SEQUENCE { -- The default value for rb-Identity is the smallest value not used yet. rb-Identity RB-Identity OPTIONAL, rlc-InfoChoice RLC-InfoChoice-r5, rb-MappingInfo RB-MappingInfo-r5 } SRB-InformationSetup-r6 ::= SEQUENCE { -- The default value for rb-Identity is the smallest value not used yet. rb-Identity RB-Identity OPTIONAL, rlc-InfoChoice RLC-InfoChoice-r6, rb-MappingInfo RB-MappingInfo-r6 } SRB-InformationSetupList ::= SEQUENCE (SIZE (1..maxSRBsetup)) OF SRB-InformationSetup SEQUENCE (SIZE (1..maxSRBsetup)) OF SRB-InformationSetup-r5 SEQUENCE (SIZE (1..maxSRBsetup)) OF SRB-InformationSetup-r6 SEQUENCE (SIZE (3..4)) OF SRB-InformationSetup SEQUENCE (SIZE (3..4)) OF SRB-InformationSetup-r6
SRB-InformationSetupList-r5 ::=
SRB-InformationSetupList-r6 ::=
SRB-InformationSetupList2 ::=
SRB-InformationSetupList2-r6 ::=
3GPP
Release 6
TimerDAR-r6 ::=
868
3GPP TS 25.331 V6.23.0 (2009-09)
ENUMERATED { ms40, ms80, ms120, ms160, ms240, ms320, ms480, ms640, ms960, ms1280, ms1920, ms2560, ms3840, ms5120 } ENUMERATED { td0-1, td0-25, td0-5, td0-75, td1, td1-25, td1-5, td1-75, td2, td2-5, td3, td3-5, td4, td4-5, td5, td7-5 } ENUMERATED { te50, te60, te70, te80, te90, te100, te120, te140, te160, te180, te200, te300, te400, te500, te700, te900 } ENUMERATED { te50, te60, te70, te80, te90, te100, te120, te140, te160, te180, te200, te300, te400, te500, te700, te900 } ENUMERATED { ms40, ms80, ms120, ms160, ms240, ms320, ms480, ms640, ms960, ms1280, ms1920, ms2560, ms3840, ms5120 } ENUMERATED { tp10, tp20, tp30, tp40, tp50, tp60, tp70, tp80, tp90, tp100, tp110, tp120, tp130, tp140, tp150, tp160, tp170, tp180, tp190, tp200, tp210, tp220, tp230, tp240, tp250, tp260, tp270, tp280, tp290, tp300, tp310, tp320, tp330, tp340, tp350, tp360, tp370, tp380, tp390, tp400, tp410, tp420, tp430, tp440, tp450, tp460, tp470, tp480, tp490, tp500, tp510, tp520, tp530, tp540, tp550, tp600, tp650, tp700, tp750, tp800, tp850, tp900, tp950, tp1000 } ENUMERATED { tper100, tper200, tper300, tper400, tper500, tper750, tper1000, tper2000 } ENUMERATED { tpp10, tpp20, tpp30, tpp40, tpp50, tpp60, tpp70, tpp80, tpp90, tpp100, tpp110, tpp120, tpp130, tpp140, tpp150, tpp160, tpp170, tpp180, tpp190, tpp200, tpp210, tpp220, tpp230, tpp240, tpp250, tpp260, tpp270, tpp280, tpp290, tpp300, tpp310, tpp320, tpp330, tpp340, tpp350, tpp360, tpp370, tpp380, tpp390, tpp400, tpp410, tpp420, tpp430, tpp440, tpp450, tpp460, tpp470, tpp480, tpp490, tpp500, tpp510, tpp520, tpp530, tpp540, tpp550, tpp600, tpp650, tpp700, tpp750, tpp800, tpp850, tpp900, tpp950, tpp1000 } ENUMERATED { tr50, tr100, tr150, tr200, tr250, tr300, tr350, tr400, tr450, tr500, tr550, tr600, tr700, tr800, tr900, tr1000 } ENUMERATED { tsp100, tsp200, tsp300, tsp400, tsp500, tsp750, tsp1000, tsp2000 } ENUMERATED { tsp10,tsp20,tsp30,tsp40,tsp50, tsp60,tsp70,tsp80,tsp90,tsp100, tsp110,tsp120,tsp130,tsp140,tsp150, tsp160,tsp170,tsp180,tsp190,tsp200, tsp210,tsp220,tsp230,tsp240,tsp250, tsp260,tsp270,tsp280,tsp290,tsp300, tsp310,tsp320,tsp330,tsp340,tsp350, tsp360,tsp370,tsp380,tsp390,tsp400, tsp410,tsp420,tsp430,tsp440,tsp450,
TimerDiscard ::=
TimerEPC ::=
TimerMRW ::=
TimerOSD-r6 ::=
TimerPoll ::=
TimerPollPeriodic ::=
TimerPollProhibit ::=
TimerRST ::=
TimerStatusPeriodic ::=
TimerStatusProhibit ::=
3GPP
Release 6
869
3GPP TS 25.331 V6.23.0 (2009-09)
tsp460,tsp470,tsp480,tsp490,tsp500, tsp510,tsp520,tsp530,tsp540,tsp550, tsp600,tsp650,tsp700,tsp750,tsp800, tsp850,tsp900,tsp950,tsp1000 } TransmissionRLC-Discard ::= timerBasedExplicit timerBasedNoExplicit maxDAT-Retransmissions noDiscard } TransmissionWindowSize ::= CHOICE { ExplicitDiscard, NoExplicitDiscard, MaxDAT-Retransmissions, MaxDAT
ENUMERATED { tw1, tw8, tw16, tw32, tw64, tw128, tw256, tw512, tw768, tw1024, tw1536, tw2047, tw2560, tw3072, tw3584, tw4095 } SEQUENCE { TransmissionRLC-Discard, TransmissionWindowSize, TimerRST, MaxRST, PollingInfo
UL-AM-RLC-Mode ::= transmissionRLC-Discard transmissionWindowSize timerRST max-RST pollingInfo } UL-CounterSynchronisationInfo ::= rB-WithPDCP-InfoList startList }
OPTIONAL
SEQUENCE { RB-WithPDCP-InfoList STARTList
OPTIONAL,
UL-LogicalChannelMapping ::= SEQUENCE { -- TABULAR: UL-TransportChannelType contains TransportChannelIdentity as well. ul-TransportChannelType UL-TransportChannelType, logicalChannelIdentity LogicalChannelIdentity OPTIONAL, rlc-SizeList CHOICE { allSizes NULL, configured NULL, explicitList RLC-SizeExplicitList }, mac-LogicalChannelPriority MAC-LogicalChannelPriority } UL-LogicalChannelMapping-r6 ::= SEQUENCE { ul-TrCH-Type CHOICE { dch-rach-usch SEQUENCE { -- TABULAR: UL-TransportChannelType contains TransportChannelIdentity as well. ul-TransportChannelType UL-TransportChannelType, logicalChannelIdentity LogicalChannelIdentity OPTIONAL, rlc-SizeList CHOICE { allSizes NULL, configured NULL, explicitList RLC-SizeExplicitList } }, e-dch SEQUENCE { logicalChannelIdentity LogicalChannelIdentity, e-DCH-MAC-d-FlowIdentity E-DCH-MAC-d-FlowIdentity, ddi DDI, rlc-PDU-SizeList RLC-PDU-SizeList, includeInSchedulingInfo BOOLEAN } }, mac-LogicalChannelPriority MAC-LogicalChannelPriority } UL-LogicalChannelMappingList ::= SEQUENCE { -- rlc-LogicalChannelMappingIndicator shall be set to TRUE in this version -- of the specification rlc-LogicalChannelMappingIndicator BOOLEAN, ul-LogicalChannelMapping SEQUENCE (SIZE (maxLoCHperRLC)) OF UL-LogicalChannelMapping } UL-LogicalChannelMappingList-r6 ::= SEQUENCE { -- rlc-LogicalChannelMappingIndicator shall be set to TRUE in this version -- of the specification rlc-LogicalChannelMappingIndicator BOOLEAN, ul-LogicalChannelMapping SEQUENCE (SIZE (maxLoCHperRLC)) OF
3GPP
Release 6
870
3GPP TS 25.331 V6.23.0 (2009-09)
UL-LogicalChannelMapping-r6 } UL-LogicalChannelMappings ::= oneLogicalChannel twoLogicalChannels } UL-LogicalChannelMappings-r6 ::= oneLogicalChannel twoLogicalChannels } CHOICE { UL-LogicalChannelMapping, UL-LogicalChannelMappingList
CHOICE { UL-LogicalChannelMapping-r6, UL-LogicalChannelMappingList-r6
UL-RFC3095-r4 ::= SEQUENCE { -- dummy1 is not used in this version of the specification and -- should be ignored by the receiver. dummy1 CID-InclusionInfo-r4, max-CID INTEGER (1..16383) -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy ROHC-PacketSizeList-r4 } UL-RLC-Mode ::= ul-AM-RLC-Mode ul-UM-RLC-Mode ul-TM-RLC-Mode spare } UL-TM-RLC-Mode ::= transmissionRLC-Discard segmentationIndication } UL-UM-RLC-Mode ::= transmissionRLC-Discard } CHOICE { UL-AM-RLC-Mode, UL-UM-RLC-Mode, UL-TM-RLC-Mode, NULL
DEFAULT 15,
SEQUENCE { TransmissionRLC-Discard BOOLEAN
OPTIONAL,
SEQUENCE { TransmissionRLC-Discard
OPTIONAL
UL-TransportChannelType ::= CHOICE { dch TransportChannelIdentity, rach NULL, -- dummy is not used in this version of the specification and -- if received the UE behaviour is not specified. dummy NULL, usch TransportChannelIdentity } UM-RLC-DuplAvoid-Reord-Info-r6 ::= timer-DAR widowSize-DAR } UM-RLC-OutOSeqDelivery-Info-r6 ::= timer-OSD windowSize-OSD } WindowSizeDAR-r6 ::= SEQUENCE { TimerDAR-r6, WindowSizeDAR-r6
SEQUENCE { TimerOSD-r6 WindowSizeOSD-r6
OPTIONAL,
ENUMERATED { ws4, ws8, ws16, ws32, ws40, ws48, ws56, ws64 } ENUMERATED { ws8, ws16, ws32, ws40, ws48, ws56, ws64 }
WindowSizeOSD-r6 ::=
-- *************************************************** --TRANSPORT CHANNEL INFORMATION ELEMENTS (10.3.5) --- *************************************************** AddOrReconfMAC-dFlow ::= mac-hs-AddReconfQueue-List mac-hs-DelQueue-List } AllowedTFC-List ::= SEQUENCE { MAC-hs-AddReconfQueue-List OPTIONAL, MAC-hs-DelQueue-List OPTIONAL
SEQUENCE (SIZE (1..maxTFC)) OF
3GPP
Release 6
871
TFC-Value
3GPP TS 25.331 V6.23.0 (2009-09)
AllowedTFI-List ::=
SEQUENCE (SIZE (1..maxTF)) OF INTEGER (0..31) CHOICE { INTEGER (0..127), sizeType2 = (part1 * 8) + 128 + part2 SEQUENCE { INTEGER (0..15), INTEGER (1..7) sizeType3 = (part1 * 16) + 256 + part2 SEQUENCE { INTEGER (0..47), INTEGER (1..15) sizeType4 = (part1 * 64) + 1024 + part2 SEQUENCE { INTEGER (0..62), INTEGER (1..63) ::=
BitModeRLC-SizeInfo sizeType1 -- Actual value sizeType2 part1 part2 }, -- Actual value sizeType3 part1 part2 }, -- Actual value sizeType4 part1 part2 } }
OPTIONAL
OPTIONAL
OPTIONAL
-- Actual value BLER-QualityValue = IE value * 0.1 BLER-QualityValue ::= INTEGER (-63..0) ChannelCodingType ::= CHOICE { -- noCoding is only used for TDD in this version of the specification, -- otherwise it should be ignored noCoding NULL, convolutional CodingRate, turbo NULL } CodingRate ::= ENUMERATED { half, third }
CommonDynamicTF-Info ::= SEQUENCE { rlc-Size CHOICE { fdd SEQUENCE { octetModeRLC-SizeInfoType2 OctetModeRLC-SizeInfoType2 }, tdd SEQUENCE { commonTDD-Choice CHOICE { bitModeRLC-SizeInfo BitModeRLC-SizeInfo, octetModeRLC-SizeInfoType1 OctetModeRLC-SizeInfoType1 } } }, numberOfTbSizeList SEQUENCE (SIZE (1..maxTF)) OF NumberOfTransportBlocks, logicalChannelList LogicalChannelList } CommonDynamicTF-Info-DynamicTTI ::= SEQUENCE { commonTDD-Choice CHOICE { bitModeRLC-SizeInfo BitModeRLC-SizeInfo, octetModeRLC-SizeInfoType1 OctetModeRLC-SizeInfoType1 }, numberOfTbSizeAndTTIList NumberOfTbSizeAndTTIList, logicalChannelList LogicalChannelList } CommonDynamicTF-InfoList ::= SEQUENCE (SIZE (1..maxTF)) OF CommonDynamicTF-Info
CommonDynamicTF-InfoList-DynamicTTI ::= SEQUENCE (SIZE (1..maxTF)) OF CommonDynamicTF-Info-DynamicTTI CommonTransChTFS ::= tti tti10 tti20 tti40 tti80 dynamic SEQUENCE { CHOICE { CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList-DynamicTTI
3GPP
Release 6
}, semistaticTF-Information } CommonTransChTFS-LCR ::= tti tti5 tti10 tti20 tti40 tti80 dynamic }, semistaticTF-Information } CPCH-SetID ::= CRC-Size ::=
872
3GPP TS 25.331 V6.23.0 (2009-09)
SemistaticTF-Information
SEQUENCE { CHOICE { CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList, CommonDynamicTF-InfoList-DynamicTTI SemistaticTF-Information
INTEGER (1..maxCPCHsets) ENUMERATED { crc0, crc8, crc12, crc16, crc24 } SEQUENCE { CHOICE { BitModeRLC-SizeInfo, OctetModeRLC-SizeInfoType1 SEQUENCE (SIZE (1..maxTF)) OF LogicalChannelList
DedicatedDynamicTF-Info ::= rlc-Size bitMode octetModeType1 }, numberOfTbSizeList NumberOfTransportBlocks, logicalChannelList }
DedicatedDynamicTF-Info-DynamicTTI ::= SEQUENCE { rlc-Size CHOICE { bitMode BitModeRLC-SizeInfo, octetModeType1 OctetModeRLC-SizeInfoType1 }, numberOfTbSizeAndTTIList NumberOfTbSizeAndTTIList, logicalChannelList LogicalChannelList } DedicatedDynamicTF-InfoList ::= SEQUENCE (SIZE (1..maxTF)) OF DedicatedDynamicTF-Info
DedicatedDynamicTF-InfoList-DynamicTTI ::= SEQUENCE (SIZE (1..maxTF)) OF DedicatedDynamicTF-Info-DynamicTTI DedicatedTransChTFS ::= tti tti10 tti20 tti40 tti80 dynamic }, semistaticTF-Information } SEQUENCE { CHOICE { DedicatedDynamicTF-InfoList, DedicatedDynamicTF-InfoList, DedicatedDynamicTF-InfoList, DedicatedDynamicTF-InfoList, DedicatedDynamicTF-InfoList-DynamicTTI SemistaticTF-Information
-- The maximum allowed size of DL-AddReconfTransChInfo2List sequence is 16 DL-AddReconfTransChInfo2List ::= SEQUENCE (SIZE (1..maxTrCHpreconf)) OF DL-AddReconfTransChInformation2 -- The maximum allowed size of DL-AddReconfTransChInfoList sequence is 16 DL-AddReconfTransChInfoList ::= SEQUENCE (SIZE (1..maxTrCHpreconf)) OF DL-AddReconfTransChInformation -- The maximum allowed size of DL-AddReconfTransChInfoList-r4 sequence is 16 DL-AddReconfTransChInfoList-r4 ::= SEQUENCE (SIZE (1..maxTrCHpreconf)) OF DL-AddReconfTransChInformation-r4 -- The maximum allowed size of DL-AddReconfTransChInfoList-r5 sequence is 16 DL-AddReconfTransChInfoList-r5 ::= SEQUENCE (SIZE (1..maxTrCHpreconf)) OF DL-AddReconfTransChInformation-r5 -- ASN.1 for IE "Added or Reconfigured DL TrCH information" -- in case of messages other than: Radio Bearer Release message and -- Radio Bearer Reconfiguration message DL-AddReconfTransChInformation ::= SEQUENCE { dl-TransportChannelType DL-TrCH-Type,
3GPP
Release 6
873
3GPP TS 25.331 V6.23.0 (2009-09)
dl-transportChannelIdentity TransportChannelIdentity, tfs-SignallingMode CHOICE { explicit-config TransportFormatSet, sameAsULTrCH UL-TransportChannelIdentity }, dch-QualityTarget QualityTarget -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy TM-SignallingInfo } DL-AddReconfTransChInformation-r4 ::= dl-TransportChannelType dl-transportChannelIdentity tfs-SignallingMode explicit-config sameAsULTrCH }, dch-QualityTarget } DL-AddReconfTransChInformation-r5 ::= dl-TransportChannelType tfs-SignallingMode explicit-config sameAsULTrCH hsdsch }, dch-QualityTarget } SEQUENCE { DL-TrCH-Type, TransportChannelIdentity, CHOICE { TransportFormatSet, UL-TransportChannelIdentity QualityTarget
OPTIONAL,
OPTIONAL
OPTIONAL
SEQUENCE { DL-TrCH-TypeId1-r5, CHOICE { TransportFormatSet, UL-TransportChannelIdentity, HSDSCH-Info QualityTarget OPTIONAL
-- ASN.1 for IE "Added or Reconfigured DL TrCH information" -- in case of Radio Bearer Release message and -- Radio Bearer Reconfiguration message DL-AddReconfTransChInformation2 ::= SEQUENCE { dl-TransportChannelType DL-TrCH-Type, transportChannelIdentity TransportChannelIdentity, tfs-SignallingMode CHOICE { explicit-config TransportFormatSet, sameAsULTrCH UL-TransportChannelIdentity }, qualityTarget QualityTarget }
OPTIONAL
DL-CommonTransChInfo ::= SEQUENCE { sccpch-TFCS TFCS OPTIONAL, -- modeSpecificInfo should be optional. A new version of this IE should be defined -- to be used in later versions of messages using this IE modeSpecificInfo CHOICE { fdd SEQUENCE { dl-Parameters CHOICE { dl-DCH-TFCS TFCS, sameAsUL NULL } OPTIONAL }, tdd SEQUENCE { individualDL-CCTrCH-InfoList IndividualDL-CCTrCH-InfoList OPTIONAL } } } DL-CommonTransChInfo-r4 ::= SEQUENCE { sccpch-TFCS TFCS OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { dl-Parameters CHOICE { dl-DCH-TFCS SEQUENCE { tfcs TFCS OPTIONAL }, sameAsUL NULL } OPTIONAL }, tdd SEQUENCE { individualDL-CCTrCH-InfoList IndividualDL-CCTrCH-InfoList OPTIONAL } } OPTIONAL
3GPP
Release 6
} DL-DeletedTransChInfoList ::=
874
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxTrCH)) OF DL-TransportChannelIdentity SEQUENCE (SIZE (1..maxTrCH)) OF DL-TransportChannelIdentity-r5 SEQUENCE { DL-TrCH-Type, TransportChannelIdentity
DL-DeletedTransChInfoList-r5 ::=
DL-TransportChannelIdentity ::= dl-TransportChannelType dl-TransportChannelIdentity } DL-TransportChannelIdentity-r5 ::= dl-TransportChannelType }
SEQUENCE { DL-TrCH-TypeId2-r5
-- The choice dsch should not be used in FDD mode, and if received the UE behaviour is unspecified DL-TrCH-Type ::= ENUMERATED {dch, dsch} DL-TrCH-TypeId1-r5 ::= CHOICE { dch TransportChannelIdentity, -- The choice dsch should not be used in FDD mode, and if received -- the UE behaviour is unspecified. dsch TransportChannelIdentity, hsdsch NULL } DL-TrCH-TypeId2-r5 ::= CHOICE { dch TransportChannelIdentity, -- The choice dsch should not be used in FDD mode, and if received -- the UE behaviour is unspecified. dsch TransportChannelIdentity, hsdsch MAC-d-FlowIdentity } DRAC-ClassIdentity ::= DRAC-StaticInformation ::= transmissionTimeValidity timeDurationBeforeRetry drac-ClassIdentity } DRAC-StaticInformationList ::= INTEGER (1..maxDRACclasses) SEQUENCE { TransmissionTimeValidity, TimeDurationBeforeRetry, DRAC-ClassIdentity
SEQUENCE (SIZE (1..maxTrCH)) OF DRAC-StaticInformation
E-DCH-AddReconf-MAC-d-Flow ::= SEQUENCE { mac-d-FlowIdentity E-DCH-MAC-d-FlowIdentity, mac-d-FlowPowerOffset E-DCH-MAC-d-FlowPowerOffset mac-d-FlowMaxRetrans E-DCH-MAC-d-FlowMaxRetrans mac-d-FlowMultiplexingList E-DCH-MAC-d-FlowMultiplexingList transmissionGrantType CHOICE { non-ScheduledTransGrantInfo SEQUENCE { maxMAC-e-PDUContents INTEGER (1..19982), ms2-NonSchedTransmGrantHARQAlloc BIT STRING (SIZE (8)) }, scheduledTransmissionGrantInfo NULL } OPTIONAL }
OPTIONAL
E-DCH-AddReconf-MAC-d-FlowList ::= SEQUENCE (SIZE (1..maxE-DCHMACdFlow)) OF E-DCH-AddReconf-MAC-d-Flow E-DCH-MAC-d-FlowIdentity ::= E-DCH-MAC-d-FlowMaxRetrans ::= INTEGER (0..maxE-DCHMACdFlow-1) INTEGER (0..15)
E-DCH-MAC-d-FlowMultiplexingList ::= BIT STRING (SIZE (maxE-DCHMACdFlow)) E-DCH-MAC-d-FlowPowerOffset ::= E-DCH-TTI ::= ExplicitTFCS-Configuration ::= complete addition removal INTEGER (0..6) ENUMERATED { tti2, tti10 } CHOICE { TFCS-ReconfAdd, TFCS-ReconfAdd, TFCS-RemovalList,
3GPP
Release 6
replacement tfcsRemoval tfcsAdd } } GainFactor ::= GainFactorInformation ::= signalledGainFactors computedGainFactors } HSDSCH-Info ::= harqInfo addOrReconfMAC-dFlow } HARQ-Info ::= numberOfProcesses memoryPartitioning implicit explicit } } HARQMemorySize ::=
875
SEQUENCE { TFCS-RemovalList, TFCS-ReconfAdd
3GPP TS 25.331 V6.23.0 (2009-09)
INTEGER (0..15) CHOICE { SignalledGainFactors, ReferenceTFC-ID
SEQUENCE { HARQ-Info AddOrReconfMAC-dFlow
OPTIONAL, OPTIONAL
SEQUENCE { INTEGER (1..8), CHOICE { NULL, SEQUENCE (SIZE (1..maxHProcesses)) OF HARQMemorySize
ENUMERATED { hms800, hms1600, hms2400, hms3200, hms4000, hms4800, hms5600, hms6400, hms7200, hms8000, hms8800, hms9600, hms10400, hms11200, hms12000, hms12800, hms13600, hms14400, hms15200, hms16000, hms17600, hms19200, hms20800, hms22400, hms24000, hms25600, hms27200, hms28800, hms30400, hms32000, hms36000, hms40000, hms44000, hms48000, hms52000, hms56000, hms60000, hms64000, hms68000, hms72000, hms76000, hms80000, hms88000, hms96000, hms104000, hms112000, hms120000, hms128000, hms136000, hms144000, hms152000, hms160000, hms176000, hms192000, hms208000, hms224000, hms240000, hms256000, hms272000, hms288000, hms304000 } SEQUENCE { TFCS-Identity, CHOICE { TFCS, TFCS-Identity
IndividualDL-CCTrCH-Info ::= dl-TFCS-Identity tfcs-SignallingMode explicit-config sameAsUL } } IndividualDL-CCTrCH-InfoList ::=
SEQUENCE (SIZE (1..maxCCTrCH)) OF IndividualDL-CCTrCH-Info SEQUENCE { TFCS-Identity, TFCS , TFC-Subset
IndividualUL-CCTrCH-Info ::= ul-TFCS-Identity ul-TFCS tfc-Subset } IndividualUL-CCTrCH-InfoList ::=
SEQUENCE (SIZE (1..maxCCTrCH)) OF IndividualUL-CCTrCH-Info SEQUENCE { RB-Identity, INTEGER (0..1)
LogicalChannelByRB ::= rb-Identity logChOfRb } LogicalChannelList ::= allSizes configured explicitList } MAC-d-FlowIdentityDCHandHSDSCH ::= dch-transport-ch-id hsdsch-mac-d-flow-id }
OPTIONAL
CHOICE { NULL, NULL, SEQUENCE (SIZE (1..15)) OF LogicalChannelByRB
SEQUENCE { TransportChannelIdentity, MAC-d-FlowIdentity
3GPP
Release 6
876
3GPP TS 25.331 V6.23.0 (2009-09)
MAC-d-FlowIdentity ::= MAC-d-PDU-SizeInfo-List ::=
INTEGER (0..7) SEQUENCE (SIZE(1.. maxMAC-d-PDUsizes)) OF MAC-d-PDUsizeInfo
--MAC-d-Pdu sizes need to be defined MAC-d-PDUsizeInfo ::= SEQUENCE{ mac-d-PDU-Size INTEGER (1..5000), mac-d-PDU-Index INTEGER(0..7) } MAC-hs-AddReconfQueue-List ::= SEQUENCE (SIZE(1..maxQueueIDs)) OF MAC-hs-AddReconfQueue SEQUENCE { INTEGER(0..7), MAC-d-FlowIdentity, T1-ReleaseTimer, MAC-hs-WindowSize, MAC-d-PDU-SizeInfo-List
MAC-hs-AddReconfQueue ::= mac-hsQueueId mac-dFlowId reorderingReleaseTimer mac-hsWindowSize mac-d-PDU-SizeInfo-List } MAC-hs-DelQueue-List ::=
OPTIONAL
SEQUENCE (SIZE(1..maxQueueIDs)) OF MAC-hs-DelQueue SEQUENCE { INTEGER(0..7)
MAC-hs-DelQueue ::= mac-hsQueueId } MAC-hs-WindowSize ::=
ENUMERATED { mws4, mws6, mws8, mws12, mws16, mws24, mws32 } SEQUENCE (SIZE (1..maxTF)) OF SEQUENCE { NumberOfTransportBlocks, TransmissionTimeInterval
NumberOfTbSizeAndTTIList ::= numberOfTransportBlocks transmissionTimeInterval } MessType ::=
ENUMERATED { transportFormatCombinationControl } SEQUENCE (SIZE (1..maxTFC)) OF TFC-Value CHOICE { NULL, NULL, INTEGER (2..17), INTEGER (18..512)
Non-allowedTFC-List ::=
NumberOfTransportBlocks ::= zero one small large }
OctetModeRLC-SizeInfoType1 ::= CHOICE { -- Actual size = (8 * sizeType1) + 16 sizeType1 INTEGER (0..31), sizeType2 SEQUENCE { -- Actual size = (32 * part1) + 272 + (part2 * 8) part1 INTEGER (0..23), part2 INTEGER (1..3) }, sizeType3 SEQUENCE { -- Actual size = (64 * part1) + 1040 + (part2 * 8) part1 INTEGER (0..61), part2 INTEGER (1..7) } } OctetModeRLC-SizeInfoType2 ::= CHOICE { -- Actual size = (sizeType1 * 8) + 48 sizeType1 INTEGER (0..31), -- Actual size = (sizeType2 * 16) + 312 sizeType2 INTEGER (0..63), -- Actual size = (sizeType3 *64) + 1384 sizeType3 INTEGER (0..56) } PowerOffsetInfoShort ::= referenceTFC modeSpecificInfo SEQUENCE { TFC-Value, CHOICE {
OPTIONAL
OPTIONAL
3GPP
Release 6
fdd gainFactorBetaC }, tdd }, gainFactorBetaD }
877
SEQUENCE { GainFactor NULL GainFactor
3GPP TS 25.331 V6.23.0 (2009-09)
PowerOffsetInformation ::= SEQUENCE { gainFactorInformation GainFactorInformation, -- PowerOffsetPp-m is always absent in TDD powerOffsetPp-m PowerOffsetPp-m } PowerOffsetPp-m ::= PreDefTransChConfiguration ::= ul-CommonTransChInfo ul-AddReconfTrChInfoList dl-CommonTransChInfo dl-TrChInfoList } QualityTarget ::= bler-QualityValue } RateMatchingAttribute ::= INTEGER (-5..10) SEQUENCE { UL-CommonTransChInfo, UL-AddReconfTransChInfoList, DL-CommonTransChInfo, DL-AddReconfTransChInfoList
OPTIONAL
SEQUENCE { BLER-QualityValue
INTEGER (1..hiRM)
ReferenceTFC-ID ::= RestrictedTrChInfo ::= ul-TransportChannelType restrictedTrChIdentity allowedTFI-List } RestrictedTrChInfoList ::=
INTEGER (0..3) SEQUENCE { UL-TrCH-Type, TransportChannelIdentity, AllowedTFI-List
OPTIONAL
SEQUENCE (SIZE (1..maxTrCH)) OF RestrictedTrChInfo
SemistaticTF-Information ::= SEQUENCE { -- TABULAR: Transmission time interval has been included in the IE CommonTransChTFS. channelCodingType ChannelCodingType, rateMatchingAttribute RateMatchingAttribute, crc-Size CRC-Size } SignalledGainFactors ::= modeSpecificInfo fdd gainFactorBetaC }, tdd }, gainFactorBetaD referenceTFC-ID } SplitTFCI-Signalling ::= splitType tfci-Field2-Length tfci-Field1-Information tfci-Field2-Information } SplitType ::= SEQUENCE { CHOICE { SEQUENCE { GainFactor NULL GainFactor, ReferenceTFC-ID
OPTIONAL
SEQUENCE { SplitType INTEGER (1..10) ExplicitTFCS-Configuration TFCI-Field2-Information
ENUMERATED { hardSplit, logicalSplit } ENUMERATED { rt10, rt20, rt30, rt40, rt50, rt60, rt70, rt80, rt90, rt100, rt120, rt140, rt160, rt200, rt300, rt400 } CHOICE { TFC-Value, AllowedTFC-List,
T1-ReleaseTimer ::=
TFC-Subset ::= minimumAllowedTFC-Number allowedTFC-List
3GPP
Release 6
non-allowedTFC-List restrictedTrChInfoList fullTFCS } TFC-SubsetList ::= modeSpecificInfo fdd tdd tfcs-ID } }, tfc-Subset } TFC-Value ::= TFCI-Field2-Information ::= tfci-Range explicit-config } TFCI-Range ::= maxTFCIField2Value tfcs-InfoForDSCH } TFCI-RangeList ::=
878
Non-allowedTFC-List, RestrictedTrChInfoList, NULL
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1.. maxTFCsub)) OF SEQUENCE { CHOICE { NULL, SEQUENCE { TFCS-Identity OPTIONAL
TFC-Subset
INTEGER (0..1023) CHOICE { TFCI-RangeList, ExplicitTFCS-Configuration
SEQUENCE { INTEGER (1..1023), TFCS-InfoForDSCH
SEQUENCE (SIZE (1..maxPDSCH-TFCIgroups)) OF TFCI-Range
TFCS ::= CHOICE { normalTFCI-Signalling ExplicitTFCS-Configuration, -- dummy is not used in this version of specification, it should -- not be sent and if received the UE behaviour is not specified. dummy SplitTFCI-Signalling } TFCS-Identity ::= tfcs-ID sharedChannelIndicator } TFCS-IdentityPlain ::= TFCS-InfoForDSCH ::= ctfc2bit ctfc4bit ctfc6bit ctfc8bit ctfc12bit ctfc16bit ctfc24bit } TFCS-ReconfAdd ::= ctfcSize ctfc2Bit ctfc2 powerOffsetInformation }, ctfc4Bit ctfc4 powerOffsetInformation }, ctfc6Bit ctfc6 powerOffsetInformation }, ctfc8Bit ctfc8 powerOffsetInformation }, ctfc12Bit ctfc12 powerOffsetInformation }, ctfc16Bit ctfc16 SEQUENCE { TFCS-IdentityPlain BOOLEAN
DEFAULT 1,
INTEGER (1..8) CHOICE { INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER
(0..3), (0..15), (0..63), (0..255), (0..4095), (0..65535), (0..16777215)
SEQUENCE{ CHOICE{ SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER (0..3), PowerOffsetInformation OPTIONAL SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER (0..15), PowerOffsetInformation OPTIONAL SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER (0..63), PowerOffsetInformation OPTIONAL SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER (0..255), PowerOffsetInformation OPTIONAL SEQUENCE (SIZE(1..maxTFC)) OF SEQUENCE { INTEGER (0..4095), PowerOffsetInformation OPTIONAL SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER(0..65535),
3GPP
Release 6
powerOffsetInformation }, ctfc24Bit ctfc24 powerOffsetInformation } } } TFCS-Removal ::= tfci } TFCS-RemovalList ::=
879
PowerOffsetInformation
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
SEQUENCE (SIZE (1..maxTFC)) OF SEQUENCE { INTEGER(0..16777215), PowerOffsetInformation OPTIONAL
SEQUENCE { INTEGER (0..1023)
SEQUENCE (SIZE (1..maxTFC)) OF TFCS-Removal INTEGER (1..256)
TimeDurationBeforeRetry ::=
TM-SignallingInfo ::= SEQUENCE { messType MessType, tm-SignallingMode CHOICE { mode1 NULL, mode2 SEQUENCE { -- in ul-controlledTrChList, TrCH-Type is always DCH ul-controlledTrChList UL-ControlledTrChList } } } TransmissionTimeInterval ::= ENUMERATED { tti10, tti20, tti40, tti80 } INTEGER (1..256) INTEGER (1..32)
TransmissionTimeValidity ::= TransportChannelIdentity ::=
TransportChannelIdentityDCHandDSCH ::= SEQUENCE { dch-transport-ch-id TransportChannelIdentity, dsch-transport-ch-id TransportChannelIdentity }
TransportFormatSet ::= dedicatedTransChTFS commonTransChTFS } TransportFormatSet-LCR ::= dedicatedTransChTFS commonTransChTFS-LCR }
CHOICE { DedicatedTransChTFS, CommonTransChTFS
CHOICE { DedicatedTransChTFS, CommonTransChTFS-LCR
-- The maximum allowed size of UL-AddReconfTransChInfoList sequence is 16 UL-AddReconfTransChInfoList ::= SEQUENCE (SIZE (1..maxTrCHpreconf)) OF UL-AddReconfTransChInformation -- The maximum allowed size of UL-AddReconfTransChInfoList-r6 sequence is 32 UL-AddReconfTransChInfoList-r6 ::= SEQUENCE (SIZE (1..maxTrCH)) OF UL-AddReconfTransChInformation-r6 UL-AddReconfTransChInformation ::= SEQUENCE { ul-TransportChannelType UL-TrCH-Type, transportChannelIdentity TransportChannelIdentity, transportFormatSet TransportFormatSet } UL-AddReconfTransChInformation-r6 ::= CHOICE { dch-usch SEQUENCE { ul-TransportChannelType UL-TrCH-Type, transportChannelIdentity TransportChannelIdentity, transportFormatSet TransportFormatSet }, e-dch SEQUENCE { tti E-DCH-TTI, harq-Info ENUMERATED { rv0, rvtable }, addReconf-MAC-d-FlowList E-DCH-AddReconf-MAC-d-FlowList } }
OPTIONAL
3GPP
Release 6
880
3GPP TS 25.331 V6.23.0 (2009-09)
UL-CommonTransChInfo ::= SEQUENCE { -- TABULAR: tfc-subset is applicable to FDD only, TDD specifies tfc-subset in individual -- CCTrCH Info. tfc-Subset TFC-Subset OPTIONAL, prach-TFCS TFCS OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-TFCS TFCS }, tdd SEQUENCE { individualUL-CCTrCH-InfoList } } } UL-CommonTransChInfo-r4 ::= SEQUENCE { -- TABULAR: tfc-subset is applicable to FDD only, TDD specifies tfc-subset in individual -- CCTrCH Info. tfc-Subset TFC-Subset OPTIONAL, prach-TFCS TFCS OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { ul-TFCS TFCS }, tdd SEQUENCE { individualUL-CCTrCH-InfoList IndividualUL-CCTrCH-InfoList OPTIONAL } } OPTIONAL, tfc-SubsetList TFC-SubsetList OPTIONAL } -- In UL-ControlledTrChList, TrCH-Type is always DCH UL-ControlledTrChList ::= SEQUENCE (SIZE (1..maxTrCH)) OF TransportChannelIdentity UL-DeletedTransChInfoList ::= SEQUENCE (SIZE (1..maxTrCH)) OF UL-TransportChannelIdentity SEQUENCE (SIZE (1..maxTrCH)) OF UL-TransportChannelIdentity-r6 SEQUENCE { UL-TrCH-Type, TransportChannelIdentity OPTIONAL IndividualUL-CCTrCH-InfoList OPTIONAL
UL-DeletedTransChInfoList-r6 ::=
UL-TransportChannelIdentity ::= ul-TransportChannelType ul-TransportChannelIdentity }
UL-TransportChannelIdentity-r6 ::= CHOICE { dch-usch SEQUENCE { ul-TransportChannelType UL-TrCH-Type, ul-TransportChannelIdentity TransportChannelIdentity }, e-dch E-DCH-MAC-d-FlowIdentity } UL-TrCH-Type ::= USCH-TransportChannelsInfo ::= usch-TransportChannelIdentity usch-TFS ENUMERATED {dch, usch} SEQUENCE (SIZE (1..maxTrCH)) OF SEQUENCE { TransportChannelIdentity, TransportFormatSet
} -- *************************************************** --PHYSICAL CHANNEL INFORMATION ELEMENTS (10.3.6) --- *************************************************** ACK-NACK-repetitionFactor ::= AC-To-ASC-Mapping ::= AC-To-ASC-MappingTable ::= INTEGER(1..4) INTEGER (0..7) SEQUENCE (SIZE (maxASCmap)) OF AC-To-ASC-Mapping SEQUENCE {
AccessServiceClass-FDD ::=
3GPP
Release 6
availableSignatureStartIndex availableSignatureEndIndex assignedSubChannelNumber
881
INTEGER (0..15), INTEGER (0..15), BIT STRING { b3(0), b2(1), b1(2), b0(3) } (SIZE(4))
3GPP TS 25.331 V6.23.0 (2009-09)
} AccessServiceClass-TDD ::= channelisationCodeIndices SEQUENCE { BIT STRING { chCodeIndex7(0), chCodeIndex6(1), chCodeIndex5(2), chCodeIndex4(3), chCodeIndex3(4), chCodeIndex2(5), chCodeIndex1(6), chCodeIndex0(7) } (SIZE(8)) OPTIONAL, subchannelSize CHOICE { size1 NULL, size2 SEQUENCE { -- subch0 means bitstring '01' in the tabular, subch1 means bitsring '10' subchannels ENUMERATED { subch0, subch1 } OPTIONAL }, size4 SEQUENCE { subchannels BIT STRING { subCh3(0), subCh2(1), subCh1(2), subCh0(3) } (SIZE(4)) OPTIONAL }, size8 SEQUENCE { subchannels BIT STRING { subCh7(0), subCh6(1), subCh5(2), subCh4(3), subCh3(4), subCh2(5), subCh1(6), subCh0(7) } (SIZE(8)) OPTIONAL } }
} AccessServiceClass-TDD-LCR-r4 ::= availableSYNC-UlCodesIndics SEQUENCE { BIT STRING { sulCodeIndex7(0), sulCodeIndex6(1), sulCodeIndex5(2), sulCodeIndex4(3), sulCodeIndex3(4), sulCodeIndex2(5), sulCodeIndex1(6), sulCodeIndex0(7) } (SIZE(8)) OPTIONAL, subchannelSize CHOICE { size1 NULL, size2 SEQUENCE { -- subch0 means bitstring '01' in the tabular, subch1 means bitsring '10'. subchannels ENUMERATED { subch0, subch1 } OPTIONAL }, size4 SEQUENCE { subchannels BIT STRING { subCh3(0), subCh2(1), subCh1(2), subCh0(3) } (SIZE(4)) OPTIONAL }, size8 SEQUENCE { subchannels BIT STRING {
3GPP
Release 6
882
subCh7(0), subCh6(1), subCh5(2), subCh4(3), subCh3(4), subCh2(5), subCh1(6), subCh0(7) } (SIZE(8))
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
} } } AdditionalPRACH-TF-and-TFCS-CCCH-IEs ::= SEQUENCE { powerOffsetInformation PowerOffsetInformation, dynamicTFInformationCCCH DynamicTFInformationCCCH } AdditionalPRACH-TF-and-TFCS-CCCH ::= SEQUENCE { additionalPRACH-TF-and-TFCS-CCCH-IEs AdditionalPRACH-TF-and-TFCS-CCCH-IEs } -- The order is the same as in the PRACH-SystemInformationList AdditionalPRACH-TF-and-TFCS-CCCH-List ::= SEQUENCE (SIZE (1..maxPRACH)) OF AdditionalPRACH-TF-and-TFCS-CCCH AICH-Info ::= channelisationCode256 sttd-Indicator aich-TransmissionTiming } AICH-PowerOffset ::= AICH-TransmissionTiming ::= SEQUENCE { ChannelisationCode256, BOOLEAN, AICH-TransmissionTiming
OPTIONAL
INTEGER (-22..5) ENUMERATED { e0, e1 } SEQUENCE { INTEGER (0..255), INTEGER (1..256)
AllocationPeriodInfo ::= allocationActivationTime allocationDuration }
-- Actual value Alpha = IE value * 0.125 Alpha ::= INTEGER (0..8) AP-AICH-ChannelisationCode ::= AP-PreambleScramblingCode ::= AP-Signature ::= AP-Signature-VCAM ::= ap-Signature availableAP-SubchannelList } AP-Subchannel ::= INTEGER (0..255) INTEGER (0..79) INTEGER (0..15) SEQUENCE { AP-Signature, AvailableAP-SubchannelList OPTIONAL
INTEGER (0..11)
ASCSetting-FDD ::= SEQUENCE { -- TABULAR: accessServiceClass-FDD is MD in tabular description -- Default value is previous ASC -- If this is the first ASC, the default value is all available signature and sub-channels accessServiceClass-FDD AccessServiceClass-FDD OPTIONAL } ASCSetting-TDD ::= SEQUENCE { -- TABULAR: accessServiceClass-TDD is MD in tabular description -- Default value is previous ASC -- If this is the first ASC, the default value is all available channelisation codes and -- all available sub-channels with subchannelSize=size1. accessServiceClass-TDD AccessServiceClass-TDD OPTIONAL } ASCSetting-TDD-LCR-r4 ::= SEQUENCE { -- TABULAR: accessServiceClass-TDD-LCR is MD in tabular description -- Default value is previous ASC -- If this is the first ASC, the default value is all available SYNC_UL codes and
3GPP
Release 6
883
3GPP TS 25.331 V6.23.0 (2009-09)
-- all available sub-channels with subchannelSize=size1. accessServiceClass-TDD-LCR AccessServiceClass-TDD-LCR-r4 } AvailableAP-Signature-VCAMList ::= SEQUENCE (SIZE (1..maxPCPCH-APsig)) OF AP-Signature-VCAM SEQUENCE (SIZE (1..maxPCPCH-APsig)) OF AP-Signature SEQUENCE (SIZE (1..maxPCPCH-APsubCh)) OF AP-Subchannel SEQUENCE (SIZE (1..maxPCPCH-SF)) OF AvailableMinimumSF-VCAM SEQUENCE { MinimumSpreadingFactor, NF-Max, MaxAvailablePCPCH-Number, AvailableAP-Signature-VCAMList
OPTIONAL
AvailableAP-SignatureList ::=
AvailableAP-SubchannelList ::=
AvailableMinimumSF-ListVCAM ::=
AvailableMinimumSF-VCAM ::= minimumSpreadingFactor nf-Max maxAvailablePCPCH-Number availableAP-Signature-VCAMList } AvailableSignatures ::=
BIT STRING { signature15(0), signature14(1), signature13(2), signature12(3), signature11(4), signature10(5), signature9(6), signature8(7), signature7(8), signature6(9), signature5(10), signature4(11), signature3(12), signature2(13), signature1(14), signature0(15) } (SIZE(16)) BIT STRING { subCh11(0), subCh10(1), subCh9(2), subCh8(3), subCh7(4), subCh6(5), subCh5(6), subCh4(7), subCh3(8), subCh2(9), subCh1(10), subCh0(11) } (SIZE(12)) ENUMERATED { true } ENUMERATED { type1, type2 }
AvailableSubChannelNumbers ::=
BEACON-PL-Est ::= BurstType ::=
-- Actual value Bler-Target = IE value * 0.05 Bler-Target ::= INTEGER (-63..0) CCTrCH-PowerControlInfo ::= tfcs-Identity ul-DPCH-PowerControlInfo } CCTrCH-PowerControlInfo-r4 ::= tfcs-Identity ul-DPCH-PowerControlInfo } CCTrCH-PowerControlInfo-r5 ::= tfcs-Identity ul-DPCH-PowerControlInfo SEQUENCE { TFCS-Identity UL-DPCH-PowerControlInfo
OPTIONAL,
SEQUENCE { TFCS-Identity UL-DPCH-PowerControlInfo-r4
OPTIONAL,
SEQUENCE { TFCS-Identity UL-DPCH-PowerControlInfo-r5
OPTIONAL,
3GPP
Release 6
} CD-AccessSlotSubchannel ::= CD-AccessSlotSubchannelList ::=
884
3GPP TS 25.331 V6.23.0 (2009-09)
INTEGER (0..11) SEQUENCE (SIZE (1..maxPCPCH-CDsubCh)) OF CD-AccessSlotSubchannel INTEGER (0..255) INTEGER (0..79) INTEGER (0..15) SEQUENCE (SIZE (1..maxPCPCH-CDsig)) OF CD-SignatureCode
CD-CA-ICH-ChannelisationCode ::= CD-PreambleScramblingCode ::= CD-SignatureCode ::= CD-SignatureCodeList ::=
CellAndChannelIdentity ::= SEQUENCE { -- burstType may be set to either value and should be ignored by the receiver for 1.28 Mcps TDD. burstType BurstType, midambleShift MidambleShiftLong, timeslot TimeslotNumber, cellParametersID CellParametersID } CellParametersID ::= Cfntargetsfnframeoffset ::= ChannelAssignmentActive ::= notActive isActive } ChannelisationCode256 ::= ChannelReqParamsForUCSM ::= availableAP-SignatureList availableAP-SubchannelList } ClosedLoopTimingAdjMode ::= INTEGER (0..127) INTEGER(0..255) CHOICE { NULL, AvailableMinimumSF-ListVCAM
INTEGER (0..255) SEQUENCE { AvailableAP-SignatureList, AvailableAP-SubchannelList
OPTIONAL
ENUMERATED { slot1, slot2 } INTEGER (0..255) SEQUENCE { PDSCH-CodeMapList
CodeNumberDSCH ::= CodeRange ::= pdsch-CodeMapList } CodeWordSet ::=
ENUMERATED { longCWS, mediumCWS, shortCWS, ssdtOff }
CommonTimeslotInfo ::= SEQUENCE { -- TABULAR: secondInterleavingMode is MD, but since it can be encoded in a single -- bit it is not defined as OPTIONAL. secondInterleavingMode SecondInterleavingMode, tfci-Coding TFCI-Coding OPTIONAL, puncturingLimit PuncturingLimit, repetitionPeriodAndLength RepetitionPeriodAndLength OPTIONAL } CommonTimeslotInfoMBMS ::= SEQUENCE { -- TABULAR: secondInterleavingMode is MD, but since it can be encoded in a single -- bit it is not defined as OPTIONAL. secondInterleavingMode SecondInterleavingMode, tfci-Coding TFCI-Coding OPTIONAL, puncturingLimit PuncturingLimit } CommonTimeslotInfoSCCPCH ::= SEQUENCE { -- TABULAR: secondInterleavingMode is MD, but since it can be encoded in a single -- bit it is not defined as OPTIONAL. secondInterleavingMode SecondInterleavingMode, tfci-Coding TFCI-Coding OPTIONAL, puncturingLimit PuncturingLimit,
3GPP
Release 6
repetitionPeriodLengthAndOffset } ConstantValue ::= ConstantValueTdd ::= CPCH-PersistenceLevels ::= cpch-SetID dynamicPersistenceLevelTF-List } CPCH-PersistenceLevelsList ::=
885
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
RepetitionPeriodLengthAndOffset
INTEGER (-35..-10) INTEGER (-35..10) SEQUENCE { CPCH-SetID, DynamicPersistenceLevelTF-List
SEQUENCE (SIZE (1..maxCPCHsets)) OF CPCH-PersistenceLevels
CPCH-SetInfo ::= SEQUENCE { cpch-SetID CPCH-SetID, transportFormatSet TransportFormatSet, tfcs TFCS, ap-PreambleScramblingCode AP-PreambleScramblingCode, ap-AICH-ChannelisationCode AP-AICH-ChannelisationCode, cd-PreambleScramblingCode CD-PreambleScramblingCode, cd-CA-ICH-ChannelisationCode CD-CA-ICH-ChannelisationCode, cd-AccessSlotSubchannelList CD-AccessSlotSubchannelList cd-SignatureCodeList CD-SignatureCodeList deltaPp-m DeltaPp-m, ul-DPCCH-SlotFormat UL-DPCCH-SlotFormat, n-StartMessage N-StartMessage, n-EOT N-EOT, -- TABULAR: VCAM info has been nested inside ChannelAssignmentActive, -- which in turn is mandatory since it's only a binary choice. channelAssignmentActive ChannelAssignmentActive, cpch-StatusIndicationMode CPCH-StatusIndicationMode, pcpch-ChannelInfoList PCPCH-ChannelInfoList } CPCH-SetInfoList ::= SEQUENCE (SIZE (1..maxCPCHsets)) OF CPCH-SetInfo ENUMERATED { pa-mode, pamsf-mode } INTEGER(1..4) INTEGER (-10..5)
OPTIONAL, OPTIONAL,
CPCH-StatusIndicationMode ::=
CQI-RepetitionFactor ::= CSICH-PowerOffset ::=
-- DefaultDPCH-OffsetValueFDD and DefaultDPCH-OffsetValueTDD corresponds to -- IE "Default DPCH Offset Value" depending on the mode. -- Actual value DefaultDPCH-OffsetValueFDD = IE value * 512 DefaultDPCH-OffsetValueFDD ::= INTEGER (0..599) DefaultDPCH-OffsetValueTDD ::= DeltaPp-m ::= DeltaCQI ::= DeltaNACK ::= DeltaACK ::= INTEGER (0..7) INTEGER (-10..10) INTEGER (0..8) INTEGER (0..8) INTEGER (0..8)
-- Actual value DeltaSIR = IE value * 0.1 DeltaSIR ::= INTEGER (0..30) DHS-Sync ::= DL-CCTrCh ::= tfcs-ID timeInfo commonTimeslotInfo dl-CCTrCH-TimeslotsCodes ul-CCTrChTPCList } DL-CCTrCh-r4 ::= tfcs-ID timeInfo INTEGER (-20..10) SEQUENCE { TFCS-IdentityPlain TimeInfo, CommonTimeslotInfo DownlinkTimeslotsCodes UL-CCTrChTPCList
DEFAULT 1, OPTIONAL, OPTIONAL, OPTIONAL
SEQUENCE { TFCS-IdentityPlain TimeInfo,
DEFAULT 1,
3GPP
Release 6
commonTimeslotInfo tddOption tdd384 dl-CCTrCH-TimeslotsCodes }, tdd128 dl-CCTrCH-TimeslotsCodes } }, ul-CCTrChTPCList } DL-CCTrChList ::=
886
CommonTimeslotInfo CHOICE { SEQUENCE { DownlinkTimeslotsCodes
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL,
OPTIONAL
SEQUENCE { DownlinkTimeslotsCodes-LCR-r4
OPTIONAL
UL-CCTrChTPCList
OPTIONAL
SEQUENCE (SIZE (1..maxCCTrCH)) OF DL-CCTrCh SEQUENCE (SIZE (1..maxCCTrCH)) OF DL-CCTrCh-r4 SEQUENCE (SIZE (1..maxCCTrCH)) OF TFCS-IdentityPlain SEQUENCE (SIZE (0..maxCCTrCH)) OF TFCS-Identity SEQUENCE { SecondaryScramblingCode SF512-AndCodeNumber, ScramblingCodeChange
DL-CCTrChList-r4 ::=
DL-CCTrChListToRemove ::=
DL-CCTrChTPCList ::=
DL-ChannelisationCode ::= secondaryScramblingCode sf-AndCodeNumber scramblingCodeChange } DL-ChannelisationCodeList ::=
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxDPCH-DLchan)) OF DL-ChannelisationCode
DL-CommonInformation ::= SEQUENCE { dl-DPCH-InfoCommon DL-DPCH-InfoCommon OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { defaultDPCH-OffsetValue DefaultDPCH-OffsetValueFDD OPTIONAL, dpch-CompressedModeInfo DPCH-CompressedModeInfo OPTIONAL, tx-DiversityMode TX-DiversityMode OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-Information OPTIONAL }, tdd SEQUENCE { defaultDPCH-OffsetValue DefaultDPCH-OffsetValueTDD OPTIONAL } } } DL-CommonInformation-r4 ::= SEQUENCE { dl-DPCH-InfoCommon DL-DPCH-InfoCommon-r4 OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { defaultDPCH-OffsetValue DefaultDPCH-OffsetValueFDD OPTIONAL, dpch-CompressedModeInfo DPCH-CompressedModeInfo OPTIONAL, tx-DiversityMode TX-DiversityMode OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-Information-r4 OPTIONAL }, tdd SEQUENCE { tddOption CHOICE { tdd384 NULL, tdd128 SEQUENCE { tstd-Indicator BOOLEAN } }, defaultDPCH-OffsetValue DefaultDPCH-OffsetValueTDD OPTIONAL } } }
DL-CommonInformation-r5 ::= dl-DPCH-InfoCommon modeSpecificInfo fdd
SEQUENCE { DL-DPCH-InfoCommon-r4 CHOICE { SEQUENCE {
OPTIONAL,
3GPP
Release 6
887
3GPP TS 25.331 V6.23.0 (2009-09)
defaultDPCH-OffsetValue DefaultDPCH-OffsetValueFDD OPTIONAL, dpch-CompressedModeInfo DPCH-CompressedModeInfo OPTIONAL, tx-DiversityMode TX-DiversityMode OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-Information-r4 OPTIONAL }, tdd tddOption tdd384 tdd128 tstd-Indicator } }, defaultDPCH-OffsetValue } }, mac-hsResetIndicator } DL-CommonInformation-r6 ::= SEQUENCE { dl-dpchInfoCommon CHOICE { dl-DPCH-InfoCommon DL-DPCH-InfoCommon-r6, dl-FDPCH-InfoCommon DL-FDPCH-InfoCommon-r6 } OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { defaultDPCH-OffsetValue DefaultDPCH-OffsetValueFDD OPTIONAL, dpch-CompressedModeInfo DPCH-CompressedModeInfo OPTIONAL, tx-DiversityMode TX-DiversityMode OPTIONAL }, tdd SEQUENCE { tddOption CHOICE { tdd384 NULL, tdd128 SEQUENCE { tstd-Indicator BOOLEAN } }, defaultDPCH-OffsetValue DefaultDPCH-OffsetValueTDD OPTIONAL } }, mac-hsResetIndicator ENUMERATED { true } OPTIONAL, postVerificationPeriod ENUMERATED { true } OPTIONAL } DL-CommonInformationPost ::= dl-DPCH-InfoCommon } DL-CommonInformationPredef ::= dl-DPCH-InfoCommon } SEQUENCE { DL-DPCH-InfoCommonPost ENUMERATED { true } OPTIONAL SEQUENCE { CHOICE { NULL, SEQUENCE { BOOLEAN
DefaultDPCH-OffsetValueTDD
OPTIONAL
SEQUENCE { DL-DPCH-InfoCommonPredef
OPTIONAL
DL-CompressedModeMethod ::= ENUMERATED { -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. dummy, sf-2, higherLayerScheduling } DL-DPCH-InfoCommon ::= SEQUENCE { cfnHandling CHOICE { maintain NULL, initialise SEQUENCE { -- IE dummy is not used in this version of the specification -- The IE should not be sent and if received it should be ignored dummy Cfntargetsfnframeoffset OPTIONAL } }, modeSpecificInfo CHOICE { fdd SEQUENCE { dl-DPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL, powerOffsetPilot-pdpdch PowerOffsetPilot-pdpdch, dl-rate-matching-restriction Dl-rate-matching-restriction OPTIONAL, -- TABULAR: The number of pilot bits is nested inside the spreading factor. spreadingFactorAndPilot SF512-AndPilot, positionFixedOrFlexible PositionFixedOrFlexible, tfci-Existence BOOLEAN },
3GPP
Release 6
tdd dl-DPCH-PowerControlInfo } } }
888
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { DL-DPCH-PowerControlInfo
OPTIONAL
DL-DPCH-InfoCommon-r4 ::= SEQUENCE { cfnHandling CHOICE { maintain NULL, initialise SEQUENCE { -- IE dummy is not used in this version of the specification -- The IE should not be sent and if received it should be ignored dummy Cfntargetsfnframeoffset OPTIONAL } }, modeSpecificInfo CHOICE { fdd SEQUENCE { dl-DPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL, powerOffsetPilot-pdpdch PowerOffsetPilot-pdpdch, dl-rate-matching-restriction Dl-rate-matching-restriction OPTIONAL, -- TABULAR: The number of pilot bits is nested inside the spreading factor. spreadingFactorAndPilot SF512-AndPilot, positionFixedOrFlexible PositionFixedOrFlexible, tfci-Existence BOOLEAN }, tdd SEQUENCE { dl-DPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL } }, -- The IE mac-d-HFN-initial-value should be absent in the RRCConnectionSetup-r4-IEs or -- RRCConnectionSetup-r5-IEs or HandoverToUTRANCommand-r4-IEs or HandoverToUTRANCommand-r5-IEs and -- if the IE is included, the general error handling for conditional IEs applies. mac-d-HFN-initial-value MAC-d-HFN-initial-value OPTIONAL } DL-DPCH-InfoCommon-r6 ::= SEQUENCE { cfnHandling CHOICE { maintain SEQUENCE { timingmaintainedsynchind TimingMaintainedSynchInd OPTIONAL }, initialise NULL }, modeSpecificInfo CHOICE { fdd SEQUENCE { dl-DPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL, powerOffsetPilot-pdpdch PowerOffsetPilot-pdpdch, dl-rate-matching-restriction Dl-rate-matching-restriction OPTIONAL, -- TABULAR: The number of pilot bits is nested inside the spreading factor. spreadingFactorAndPilot SF512-AndPilot, positionFixedOrFlexible PositionFixedOrFlexible, tfci-Existence BOOLEAN }, tdd SEQUENCE { dl-DPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL } }, -- The IE mac-d-HFN-initial-value should be absent in the RRCConnectionSetup and the -- HandoverToUTRANCommand messages. If the IE is included, the general error handling -- for conditional IEs applies. mac-d-HFN-initial-value MAC-d-HFN-initial-value OPTIONAL } DL-DPCH-InfoCommonPost ::= dl-DPCH-PowerControlInfo } SEQUENCE { DL-DPCH-PowerControlInfo
OPTIONAL
DL-DPCH-InfoCommonPredef ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { -- TABULAR: The number of pilot bits is nested inside the spreading factor. spreadingFactorAndPilot SF512-AndPilot, positionFixedOrFlexible PositionFixedOrFlexible, tfci-Existence BOOLEAN }, tdd SEQUENCE { commonTimeslotInfo CommonTimeslotInfo }
3GPP
Release 6
} }
889
3GPP TS 25.331 V6.23.0 (2009-09)
DL-DPCH-InfoPerRL ::= CHOICE { fdd SEQUENCE { pCPICH-UsageForChannelEst PCPICH-UsageForChannelEst, dpch-FrameOffset DPCH-FrameOffset, secondaryCPICH-Info SecondaryCPICH-Info OPTIONAL, dl-ChannelisationCodeList DL-ChannelisationCodeList, tpc-CombinationIndex TPC-CombinationIndex, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-CellIdentity OPTIONAL, closedLoopTimingAdjMode ClosedLoopTimingAdjMode OPTIONAL }, tdd SEQUENCE { dl-CCTrChListToEstablish DL-CCTrChList OPTIONAL, dl-CCTrChListToRemove DL-CCTrChListToRemove OPTIONAL } } DL-DPCH-InfoPerRL-r4 ::= CHOICE { fdd SEQUENCE { pCPICH-UsageForChannelEst PCPICH-UsageForChannelEst, dpch-FrameOffset DPCH-FrameOffset, secondaryCPICH-Info SecondaryCPICH-Info OPTIONAL, dl-ChannelisationCodeList DL-ChannelisationCodeList, tpc-CombinationIndex TPC-CombinationIndex, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-CellIdentity OPTIONAL, closedLoopTimingAdjMode ClosedLoopTimingAdjMode OPTIONAL }, tdd SEQUENCE { dl-CCTrChListToEstablish DL-CCTrChList-r4 OPTIONAL, dl-CCTrChListToRemove DL-CCTrChListToRemove OPTIONAL } } DL-DPCH-InfoPerRL-r5 ::= CHOICE { fdd SEQUENCE { pCPICH-UsageForChannelEst PCPICH-UsageForChannelEst, dpch-FrameOffset DPCH-FrameOffset, secondaryCPICH-Info SecondaryCPICH-Info OPTIONAL, dl-ChannelisationCodeList DL-ChannelisationCodeList, tpc-CombinationIndex TPC-CombinationIndex, powerOffsetTPC-pdpdch PowerOffsetTPC-pdpdch OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SSDT-CellIdentity OPTIONAL, closedLoopTimingAdjMode ClosedLoopTimingAdjMode OPTIONAL }, tdd SEQUENCE { dl-CCTrChListToEstablish DL-CCTrChList-r4 OPTIONAL, dl-CCTrChListToRemove DL-CCTrChListToRemove OPTIONAL } } DL-DPCH-InfoPerRL-r6 ::= fdd pCPICH-UsageForChannelEst dpch-FrameOffset secondaryCPICH-Info dl-ChannelisationCodeList tpc-CombinationIndex powerOffsetTPC-pdpdch closedLoopTimingAdjMode }, tdd dl-CCTrChListToEstablish dl-CCTrChListToRemove } } DL-FDPCH-InfoPerRL-r6 ::= pCPICH-UsageForChannelEst fdpch-FrameOffset secondaryCPICH-Info CHOICE { SEQUENCE { PCPICH-UsageForChannelEst, DPCH-FrameOffset, SecondaryCPICH-Info DL-ChannelisationCodeList, TPC-CombinationIndex, PowerOffsetTPC-pdpdch ClosedLoopTimingAdjMode SEQUENCE { DL-CCTrChList-r4 DL-CCTrChListToRemove
OPTIONAL,
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
SEQUENCE { PCPICH-UsageForChannelEst, DPCH-FrameOffset, SecondaryCPICH-Info
OPTIONAL,
3GPP
Release 6
secondaryScramblingCode dl-ChannelisationCode tpc-CombinationIndex } DL-DPCH-InfoPerRL-PostFDD ::= pCPICH-UsageForChannelEst dl-ChannelisationCode tpc-CombinationIndex } DL-DPCH-InfoPerRL-PostTDD ::= dl-DPCH-TimeslotsCodes } DL-DPCH-InfoPerRL-PostTDD-LCR-r4 ::= dl-CCTrCH-TimeslotsCodes } DL-DPCH-PowerControlInfo ::= modeSpecificInfo fdd dpc-Mode }, tdd tpc-StepSizeTDD } } }
890
SecondaryScramblingCode INTEGER (0..255), TPC-CombinationIndex
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL,
SEQUENCE { PCPICH-UsageForChannelEst, DL-ChannelisationCode, TPC-CombinationIndex
SEQUENCE { DownlinkTimeslotsCodes
SEQUENCE { CHOICE { SEQUENCE { DPC-Mode SEQUENCE { TPC-StepSizeTDD
OPTIONAL
DL-FDPCH-InfoCommon-r6 ::= SEQUENCE { cfnHandling CHOICE { maintain SEQUENCE { timingmaintainedsynchind TimingMaintainedSynchInd OPTIONAL }, initialise NULL }, dl-FDPCH-PowerControlInfo DL-DPCH-PowerControlInfo OPTIONAL, -- Actual value dl-FDPCH-TPCcommandErrorRate = IE value * 0.01 -- dl-FDPCH-TPCcommandErrorRate values 11..16 are spare and shall not be used in this version of -- the protocol. -- In addition, this IE shall always be included otherwise the UE behaviour is unspecified. dl-FDPCH-TPCcommandErrorRate INTEGER (1..16) OPTIONAL } DL-FrameType ::= ENUMERATED { dl-FrameTypeA, dl-FrameTypeB }
DL-HSPDSCH-Information ::= SEQUENCE { hs-scch-Info HS-SCCH-Info OPTIONAL, measurement-feedback-Info Measurement-Feedback-Info OPTIONAL, modeSpecificInfo CHOICE { tdd CHOICE{ tdd384 SEQUENCE { dl-HSPDSCH-TS-Configuration DL-HSPDSCH-TS-Configuration }, tdd128 SEQUENCE { hs-PDSCH-Midamble-Configuration-tdd128 HS-PDSCH-Midamble-Configuration-TDD128 } }, fdd NULL } } DL-HSPDSCH-Information-r6 ::= SEQUENCE { hs-scch-Info HS-SCCH-Info-r6 measurement-feedback-Info Measurement-Feedback-Info modeSpecificInfo CHOICE { tdd CHOICE { tdd384 SEQUENCE { dl-HSPDSCH-TS-Configuration DL-HSPDSCH-TS-Configuration }, tdd128 SEQUENCE { hs-PDSCH-Midamble-Configuration-tdd128 HS-PDSCH-Midamble-Configuration-TDD128 } },
OPTIONAL
OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL
OPTIONAL
3GPP
Release 6
fdd } } NULL
891
3GPP TS 25.331 V6.23.0 (2009-09)
-- The IE 'DL-HSPDSCH-TS-Configuration' applies to tdd-384 REL-5 onward DL-HSPDSCH-TS-Configuration ::= SEQUENCE (SIZE (1..maxTS-1)) OF SEQUENCE { timeslot TimeslotNumber, midambleShiftAndBurstType MidambleShiftAndBurstType-DL } DL-InformationPerRL ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, -- dummy1 and dummy 2 are not used in this version of specification, they should -- not be sent and if received they should be ignored. dummy1 PDSCH-SHO-DCH-Info OPTIONAL, dummy2 PDSCH-CodeMapping OPTIONAL }, tdd PrimaryCCPCH-Info }, dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SCCPCH-InfoForFACH OPTIONAL } DL-InformationPerRL-r4 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, -- dummy1 and dummy 2 are not used in this version of specification, they should -- not be sent and if received they should be ignored. dummy1 PDSCH-SHO-DCH-Info OPTIONAL, dummy2 PDSCH-CodeMapping OPTIONAL }, tdd PrimaryCCPCH-Info-r4 }, dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL-r4 OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SCCPCH-InfoForFACH-r4 OPTIONAL, cell-id CellIdentity OPTIONAL } DL-InformationPerRL-r5 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, -- dummy1 and dummy 2 are not used in this version of specification, they should -- not be sent and if received they should be ignored. dummy1 PDSCH-SHO-DCH-Info OPTIONAL, dummy2 PDSCH-CodeMapping OPTIONAL, servingHSDSCH-RL-indicator BOOLEAN }, tdd PrimaryCCPCH-Info-r4 }, dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL-r5 OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SCCPCH-InfoForFACH-r4 OPTIONAL, cell-id CellIdentity OPTIONAL } DL-InformationPerRL-r5bis ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, -- dummy1 and dummy 2 are not used in this version of specification, they should -- not be sent and if received they should be ignored. dummy1 PDSCH-SHO-DCH-Info OPTIONAL, dummy2 PDSCH-CodeMapping OPTIONAL }, tdd PrimaryCCPCH-Info-r4 }, dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL-r5 OPTIONAL, -- dummy is not used in this version of the specification, it should
3GPP
Release 6
892
3GPP TS 25.331 V6.23.0 (2009-09)
-- not be sent and if received it should be ignored. dummy SCCPCH-InfoForFACH-r4 cell-id CellIdentity } DL-InformationPerRL-r6 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, servingHSDSCH-RL-indicator BOOLEAN, servingEDCH-RL-indicator BOOLEAN }, tdd PrimaryCCPCH-Info-r4 }, dl-dpchInfo CHOICE { dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL-r6, dl-FDPCH-InfoPerRL DL-FDPCH-InfoPerRL-r6 } e-AGCH-Information E-AGCH-Information e-HICH-Info CHOICE { e-HICH-Information E-HICH-Information, releaseIndicator NULL } OPTIONAL, e-RGCH-Info CHOICE { e-RGCH-Information E-RGCH-Information, releaseIndicator NULL } OPTIONAL, cell-id CellIdentity } DL-InformationPerRL-v6b0ext ::= sttdIndication } DL-InformationPerRL-List ::= SEQUENCE { STTDIndication
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL
OPTIONAL
SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-r4 SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-r5 SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-r6 SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-v6b0ext SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-r5bis
DL-InformationPerRL-List-r4 ::=
DL-InformationPerRL-List-v6b0ext ::=
DL-InformationPerRL-List-r5bis ::=
DL-InformationPerRL-ListPostFDD ::= SEQUENCE (SIZE (1..maxRL)) OF DL-InformationPerRL-PostFDD DL-InformationPerRL-PostFDD ::= primaryCPICH-Info dl-DPCH-InfoPerRL } DL-InformationPerRL-PostTDD ::= primaryCCPCH-Info dl-DPCH-InfoPerRL } SEQUENCE { PrimaryCPICH-Info, DL-DPCH-InfoPerRL-PostFDD
SEQUENCE { PrimaryCCPCH-InfoPost, DL-DPCH-InfoPerRL-PostTDD
DL-InformationPerRL-PostTDD-LCR-r4 ::= primaryCCPCH-Info dl-DPCH-InfoPerRL }
SEQUENCE { PrimaryCCPCH-InfoPostTDD-LCR-r4, DL-DPCH-InfoPerRL-PostTDD-LCR-r4
DL-PDSCH-Information ::= SEQUENCE { -- dummy1 and dummy 2 are not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy1 PDSCH-SHO-DCH-Info OPTIONAL, dummy2 PDSCH-CodeMapping OPTIONAL } Dl-rate-matching-restriction ::= SEQUENCE {
3GPP
Release 6
restrictedTrCH-InfoList } DL-TPC-PowerOffsetPerRL ::= powerOffsetTPC-pdpdch } SEQUENCE {
893
RestrictedTrCH-InfoList
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
PowerOffsetTPC-pdpdch
OPTIONAL
-- NOTE: The radio links in the following list have a one-to-one mapping with the -- radio links in the message. DL-TPC-PowerOffsetPerRL-List ::= SEQUENCE (SIZE (1..maxRL)) OF DL-TPC-PowerOffsetPerRL DL-TS-ChannelisationCode ::= ENUMERATED { cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 }
DL-TS-ChannelisationCodesShort ::= SEQUENCE { codesRepresentation CHOICE { consecutive SEQUENCE { firstChannelisationCode DL-TS-ChannelisationCode, lastChannelisationCode DL-TS-ChannelisationCode }, bitmap BIT STRING { chCode16-SF16(0), chCode15-SF16(1), chCode14-SF16(2), chCode13-SF16(3), chCode12-SF16(4), chCode11-SF16(5), chCode10-SF16(6), chCode9-SF16(7), chCode8-SF16(8), chCode7-SF16(9), chCode6-SF16(10), chCode5-SF16(11), chCode4-SF16(12), chCode3-SF16(13), chCode2-SF16(14), chCode1-SF16(15) } (SIZE (16)) } } DownlinkAdditionalTimeslots ::= SEQUENCE { parameters CHOICE { sameAsLast SEQUENCE { timeslotNumber TimeslotNumber }, newParameters SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo, dl-TS-ChannelisationCodesShort DL-TS-ChannelisationCodesShort } } } DownlinkAdditionalTimeslots-LCR-r4 ::= SEQUENCE { parameters CHOICE { sameAsLast SEQUENCE { timeslotNumber TimeslotNumber-LCR-r4 }, newParameters SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo-LCR-r4, dl-TS-ChannelisationCodesShort DL-TS-ChannelisationCodesShort } } } DownlinkTimeslotsCodes ::= SEQUENCE { firstIndividualTimeslotInfo IndividualTimeslotInfo, dl-TS-ChannelisationCodesShort DL-TS-ChannelisationCodesShort, moreTimeslots CHOICE { noMore NULL, additionalTimeslots CHOICE { consecutive INTEGER (1..maxTS-1), timeslotList SEQUENCE (SIZE (1..maxTS-1)) OF DownlinkAdditionalTimeslots
3GPP
Release 6
} } } DownlinkTimeslotsCodes-LCR-r4 ::= firstIndividualTimeslotInfo dl-TS-ChannelisationCodesShort moreTimeslots noMore additionalTimeslots consecutive timeslotList } } } DPC-Mode ::=
894
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { IndividualTimeslotInfo-LCR-r4, DL-TS-ChannelisationCodesShort, CHOICE { NULL, CHOICE { INTEGER (1..maxTS-LCR-1), SEQUENCE (SIZE (1..maxTS-LCR-1)) OF DownlinkAdditionalTimeslots-LCR-r4
ENUMERATED { singleTPC, tpcTripletInSoft }
-- Actual value DPCCH-PowerOffset = IE value * 2 DPCCH-PowerOffset ::= INTEGER (-82..-3) -- Actual value DPCCH-PowerOffset2 = 2 + (IE value * 4) DPCCH-PowerOffset2 ::= INTEGER (-28..-13) DPCH-CompressedModeInfo ::= tgp-SequenceList } DPCH-CompressedModeStatusInfo ::= tgps-Reconfiguration-CFN tgp-SequenceShortList } -- Actual value DPCH-FrameOffset = IE value * 256 DPCH-FrameOffset::= INTEGER (0..149) DSCH-Mapping ::= maxTFCI-Field2Value spreadingFactor codeNumber multiCodeInfo } DSCH-MappingList ::= SEQUENCE { MaxTFCI-Field2Value, SF-PDSCH, CodeNumberDSCH, MultiCodeInfo SEQUENCE { TGP-SequenceList
SEQUENCE { TGPS-Reconfiguration-CFN, SEQUENCE (SIZE (1..maxTGPS)) OF TGP-SequenceShort
SEQUENCE (SIZE (1..maxPDSCH-TFCIgroups)) OF DSCH-Mapping INTEGER (0..511)
DSCH-RadioLinkIdentifier ::= DSCH-TransportChannelsInfo ::=
SEQUENCE (SIZE (1..maxTrCH)) OF SEQUENCE { dsch-transport-channel-identity TransportChannelIdentity, dsch-TFS TransportFormatSet INTEGER (1..4096) INTEGER (1..8) SEQUENCE (SIZE (1..maxPRACH)) OF DynamicPersistenceLevel
} DurationTimeInfo ::= DynamicPersistenceLevel ::= DynamicPersistenceLevelList ::=
DynamicPersistenceLevelTF-List ::= SEQUENCE (SIZE (1..maxTF-CPCH)) OF DynamicPersistenceLevel DynamicTFInformationCCCH ::= octetModeRLC-SizeInfoType2 } E-AGCH-ChannelisationCode ::= E-AGCH-Information ::= e-AGCH-ChannelisationCode } E-DCH-MinimumSet-E-TFCI ::= SEQUENCE { OctetModeRLC-SizeInfoType2
INTEGER (0..255) SEQUENCE { E-AGCH-ChannelisationCode
INTEGER (0..127)
3GPP
Release 6
895
3GPP TS 25.331 V6.23.0 (2009-09)
E-DCH-ReconfigurationInfo ::= SEQUENCE { e-DCH-RL-InfoNewServingCell E-DCH-RL-InfoNewServingCell e-DCH-RL-InfoOtherCellList SEQUENCE (SIZE (1..maxEDCHRL)) OF E-DCH-RL-InfoOtherCell } E-DCH-RL-InfoNewServingCell ::= SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, e-AGCH-Information E-AGCH-Information, servingGrant SEQUENCE { value INTEGER (0..38) primary-Secondary-GrantSelector ENUMERATED { primary, secondary } } OPTIONAL, e-DPCCH-DPCCH-PowerOffset E-DPCCH-DPCCH-PowerOffset reference-E-TFCIs E-DPDCH-Reference-E-TFCIList powerOffsetForSchedInfo INTEGER (0..6) threeIndexStepThreshold INTEGER (0..37) twoIndexStepThreshold INTEGER (0..37) e-HICH-Information E-HICH-Information OPTIONAL, e-RGCH-Info CHOICE { e-RGCH-Information E-RGCH-Information, releaseIndicator NULL } OPTIONAL } E-DCH-RL-InfoOtherCell ::= primaryCPICH-Info e-HICH-Info e-HICH-Information releaseIndicator } OPTIONAL, e-RGCH-Info e-RGCH-Information releaseIndicator } OPTIONAL } E-DPCCH-Info ::= e-DPCCH-DPCCH-PowerOffset happyBit-DelayCondition } E-DPCCH-DPCCH-PowerOffset ::= E-DPDCH-Info ::= e-TFCI-TableIndex e-DCH-MinimumSet-E-TFCI reference-E-TFCIs maxChannelisationCodes pl-NonMax schedulingInfoConfiguration threeIndexStepThreshold twoIndexStepThreshold } E-DPDCH-PeriodicyOfSchedInfo ::= SEQUENCE { PrimaryCPICH-Info, CHOICE { E-HICH-Information, NULL CHOICE { E-RGCH-Information, NULL
OPTIONAL, OPTIONAL
OPTIONAL,
SEQUENCE { E-DPCCH-DPCCH-PowerOffset, HappyBit-DelayCondition
INTEGER (0..8) SEQUENCE { E-TFCI-TableIndex, E-DCH-MinimumSet-E-TFCI OPTIONAL, E-DPDCH-Reference-E-TFCIList, E-DPDCH-MaxChannelisationCodes, E-DPDCH-PL-NonMax, E-DPDCH-SchedulingInfoConfiguration, INTEGER (0..37) OPTIONAL, INTEGER (0..37) OPTIONAL
ENUMERATED { everyEDCHTTI, ms4, ms10, ms20, ms50, ms100, ms200, ms500, ms1000 }
-- The actual value of E-DPDCH-PL-NonMax is: IE value * 0.04 E-DPDCH-PL-NonMax ::= INTEGER (11..25) E-DPDCH-Reference-E-TFCI ::= reference-E-TFCI reference-E-TFCI-PO } E-DPDCH-Reference-E-TFCIList ::= SEQUENCE { INTEGER (0..127), INTEGER (0..29)
SEQUENCE (SIZE (1..8)) OF E-DPDCH-Reference-E-TFCI
E-DPDCH-SchedulingInfoConfiguration ::= SEQUENCE { periodicityOfSchedInfo-NoGrant E-DPDCH-PeriodicyOfSchedInfo periodicityOfSchedInfo-Grant E-DPDCH-PeriodicyOfSchedInfo powerOffsetForSchedInfo INTEGER (0..6) } E-DPDCH-SchedulingTransmConfiguration ::= SEQUENCE { ms2-SchedTransmGrantHARQAlloc BIT STRING (SIZE (8))
OPTIONAL, OPTIONAL,
OPTIONAL,
3GPP
Release 6
896
3GPP TS 25.331 V6.23.0 (2009-09)
servingGrant SEQUENCE { value INTEGER (0..38), primary-Secondary-GrantSelector ENUMERATED { primary, secondary } } OPTIONAL } E-DPDCH-MaxChannelisationCodes ::= sf4x2-and-sf2x2 } E-HICH-ChannelisationCode ::= E-HICH-Information ::= channelisationCode signatureSequence } E-HICH-RGCH-SignatureSequence ::= E-RGCH-CombinationIndex ::= E-RGCH-Information ::= signatureSequence rg-CombinationIndex } E-TFCI-TableIndex ::= FACH-PCH-Information ::= transportFormatSet transportChannelIdentity ctch-Indicator } FACH-PCH-InformationList ::= INTEGER (0..127) SEQUENCE { E-HICH-ChannelisationCode, E-HICH-RGCH-SignatureSequence ENUMERATED { sf256, sf128, sf64, sf32, sf16, sf8, sf4, sf4x2, sf2x2,
INTEGER (0..39) INTEGER (0..5) SEQUENCE { E-HICH-RGCH-SignatureSequence, E-RGCH-CombinationIndex
INTEGER (0..1) SEQUENCE { TransportFormatSet, TransportChannelIdentity, BOOLEAN
SEQUENCE (SIZE (1..maxFACHPCH)) OF FACH-PCH-Information ENUMERATED { fc0, fc2, fc4, fc8, fc10, fc20, fc40, fc80, fc160} SEQUENCE { TimeslotNumber-LCR-r4, TDD-FPACH-CCode16-r4, MidambleShiftAndBurstType-LCR-r4, Wi-LCR
Feedback-cycle ::=
FPACH-Info-r4 ::= timeslot channelisationCode midambleShiftAndBurstType wi } FrequencyInfo ::= modeSpecificInfo fdd tdd } FrequencyInfoFDD ::= uarfcn-UL uarfcn-DL } FrequencyInfoTDD ::= uarfcn-Nt } HappyBit-DelayCondition ::=
SEQUENCE { CHOICE { FrequencyInfoFDD, FrequencyInfoTDD
SEQUENCE { UARFCN UARFCN
OPTIONAL,
SEQUENCE { UARFCN
ENUMERATED { ms2, ms10, ms20, ms50, ms100, ms200, ms500, ms1000 } INTEGER (0..1) ENUMERATED { cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 }
HARQ-Preamble-Mode ::= HS-ChannelisationCode-LCR ::=
HS-PDSCH-Midamble-Configuration-TDD128 ::= SEQUENCE { midambleAllocationMode CHOICE{ defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble INTEGER (0..15)
3GPP
Release 6
897
3GPP TS 25.331 V6.23.0 (2009-09)
}, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8) } HS-SCCH-Info ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { hS-SCCHChannelisationCodeInfo SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-Codes, dl-ScramblingCode SecondaryScramblingCode OPTIONAL }, tdd CHOICE { tdd384 SEQUENCE { nack-ack-power-offset INTEGER (-7..8), hs-SICH-PowerControl-Info HS-SICH-Power-Control-Info-TDD384, hS-SCCH-SetConfiguration SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-TDD384 }, tdd128 SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-TDD128 } } } HS-SCCH-Info-r6 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { hS-SCCHChannelisationCodeInfo SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-Codes, dl-ScramblingCode SecondaryScramblingCode OPTIONAL }, tdd CHOICE { tdd384 SEQUENCE { nack-ack-power-offset INTEGER (-7..8), hs-SICH-PowerControl-Info HS-SICH-Power-Control-Info-TDD384, dhs-sync DHS-Sync OPTIONAL, bler-target Bler-Target, hS-SCCH-SetConfiguration SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-TDD384-r6 }, tdd128 SEQUENCE { nack-ack-power-offset INTEGER (-7..8), power-level-HSSICH INTEGER (-120..-58), tpc-step-size ENUMERATED { s1, s2, s3 , spare1 }, bler-target Bler-Target, hS-SCCH-SetConfiguration SEQUENCE (SIZE (1..maxHSSCCHs)) OF HS-SCCH-TDD128-r6 } } } } HS-SCCH-Codes ::= INTEGER (0..127)
HS-SCCH-TDD128 ::= SEQUENCE { timeslotNumber TimeslotNumber-LCR-r4, firstChannelisationCode HS-ChannelisationCode-LCR, secondChannelisationCode HS-ChannelisationCode-LCR, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble INTEGER(0..15) }, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8), bler-target Bler-Target, hs-sich-configuration HS-SICH-Configuration-TDD128 } HS-SCCH-TDD128-r6 ::= timeslotNumber firstChannelisationCode secondChannelisationCode midambleAllocationMode defaultMidamble commonMidamble ueSpecificMidamble SEQUENCE { TimeslotNumber-LCR-r4, HS-ChannelisationCode-LCR, HS-ChannelisationCode-LCR, CHOICE { NULL, NULL, INTEGER (0..15)
3GPP
Release 6
898
3GPP TS 25.331 V6.23.0 (2009-09)
}, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8), hs-sich-configuration HS-SICH-Configuration-TDD128-r6 } HS-SICH-Configuration-TDD128 ::= SEQUENCE { timeslotNumber TimeslotNumber-LCR-r4, channelisationCode HS-ChannelisationCode-LCR, midambleAllocationMode CHOICE { defaultMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftLong } }, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8), nack-ack-power-offset INTEGER (-7..8), power-level-HSSICH INTEGER (-120..-58), tpc-step-size ENUMERATED { s1, s2, s3 , spare1} } HS-SICH-Configuration-TDD128-r6 ::= SEQUENCE { timeslotNumber TimeslotNumber-LCR-r4, channelisationCode HS-ChannelisationCode-LCR, midambleAllocationMode CHOICE { defaultMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftLong } }, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8) } HS-SCCH-TDD384 ::= timeslotNumber channelisationCode midambleAllocationMode defaultMidamble commonMidamble ueSpecificMidamble midambleShift } }, midambleconfiguration bler-target hs-sich-configuration } HS-SCCH-TDD384-r6 ::= timeslotNumber channelisationCode midambleAllocationMode defaultMidamble commonMidamble ueSpecificMidamble midambleShift } }, midambleconfiguration hs-sich-configuration } HS-SICH-Configuration-TDD384 ::= timeslotNumber channelisationCode midambleAllocationMode defaultMidamble ueSpecificMidamble midambleShift } }, midambleconfiguration } SEQUENCE { TimeslotNumber, DL-TS-ChannelisationCode, CHOICE { NULL, NULL, SEQUENCE { MidambleShiftLong
MidambleConfigurationBurstType1and3, Bler-Target, HS-SICH-Configuration-TDD384
SEQUENCE { TimeslotNumber, DL-TS-ChannelisationCode, CHOICE { NULL, NULL, SEQUENCE { MidambleShiftLong
MidambleConfigurationBurstType1and3, HS-SICH-Configuration-TDD384
SEQUENCE { TimeslotNumber, DL-TS-ChannelisationCode, CHOICE { NULL, SEQUENCE { MidambleShiftLong
MidambleConfigurationBurstType1and3
HS-SICH-Power-Control-Info-TDD384 ::= SEQUENCE { -- Actual value ul-target-SIR = IE value * 0.5
3GPP
Release 6
ul-target-SIR hs-sich-ConstantValue }
899
INTEGER (-22..40), ConstantValue
3GPP TS 25.331 V6.23.0 (2009-09)
IndividualTimeslotInfo ::= timeslotNumber tfci-Existence midambleShiftAndBurstType } IndividualTimeslotInfo-LCR-r4 ::= timeslotNumber tfci-Existence midambleShiftAndBurstType modulation ss-TPC-Symbols additionalSS-TPC-Symbols }
SEQUENCE { TimeslotNumber, BOOLEAN, MidambleShiftAndBurstType
SEQUENCE { TimeslotNumber-LCR-r4, BOOLEAN, MidambleShiftAndBurstType-LCR-r4, ENUMERATED { mod-QPSK, mod-8PSK }, ENUMERATED { zero, one, sixteenOverSF }, INTEGER(1..15) OPTIONAL
IndividualTimeslotInfo-LCR-r4-ext ::= SEQUENCE { -- timeslotNumber and tfci-Existence is taken from IndividualTimeslotInfo. -- midambleShiftAndBurstType in IndividualTimeslotInfo shall be ignored. midambleShiftAndBurstType MidambleShiftAndBurstType-LCR-r4, modulation ENUMERATED { mod-QPSK, mod-8PSK }, ss-TPC-Symbols ENUMERATED { zero, one, sixteenOverSF } } IndividualTS-Interference ::= timeslot ul-TimeslotInterference } IndividualTS-InterferenceList ::= SEQUENCE { TimeslotNumber, TDD-UL-Interference
SEQUENCE (SIZE (1..maxTS)) OF IndividualTS-Interference ENUMERATED { mode0, mode1 }
ITP ::=
NidentifyAbort ::=
INTEGER (1..128) INTEGER (-50..33) INTEGER (1..64) INTEGER (0..3) INTEGER (1..1023) SEQUENCE { CHOICE { SEQUENCE { MeasurementPowerOffset, Feedback-cycle, CQI-RepetitionFactor, DeltaCQI NULL
MaxAllowedUL-TX-Power ::= MaxAvailablePCPCH-Number ::= MaxPowerIncrease-r4 ::= MaxTFCI-Field2Value ::= Measurement-Feedback-Info ::= modeSpecificInfo fdd measurementPowerOffset feedback-cycle cqi-RepetitionFactor deltaCQI }, tdd } }
MidambleConfigurationBurstType1and3 ::= ENUMERATED {ms4, ms8, ms16} MidambleConfigurationBurstType2 ::= ENUMERATED {ms3, ms6}
MidambleShiftAndBurstType ::= SEQUENCE { burstType CHOICE { type1 SEQUENCE { midambleConfigurationBurstType1and3 MidambleConfigurationBurstType1and3, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftLong } } }, type2 SEQUENCE {
3GPP
Release 6
midambleConfigurationBurstType2 midambleAllocationMode defaultMidamble commonMidamble ueSpecificMidamble midambleShift } }
900
3GPP TS 25.331 V6.23.0 (2009-09)
MidambleConfigurationBurstType2, CHOICE { NULL, NULL, SEQUENCE { MidambleShiftShort
}, type3 SEQUENCE { midambleConfigurationBurstType1and3 MidambleConfigurationBurstType1and3, midambleAllocationMode CHOICE { defaultMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftLong } } } } } MidambleShiftAndBurstType-DL ::= SEQUENCE { burstType CHOICE { type1 SEQUENCE { midambleConfigurationBurstType1and3 MidambleConfigurationBurstType1and3, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftLong } } }, type2 SEQUENCE { midambleConfigurationBurstType2 MidambleConfigurationBurstType2, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift MidambleShiftShort } } } } } MidambleShiftAndBurstType-LCR-r4 ::= SEQUENCE { midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble SEQUENCE { midambleShift INTEGER (0..15) } }, -- Actual value midambleConfiguration = IE value * 2 midambleConfiguration INTEGER (1..8) } MidambleShiftLong ::= INTEGER (0..15)
MidambleShiftShort ::= MinimumSpreadingFactor ::=
INTEGER (0..5) ENUMERATED { sf4, sf8, sf16, sf32, sf64, sf128, sf256 } INTEGER (1..16)
MultiCodeInfo ::=
N-EOT ::= N-GAP ::=
INTEGER (0..7) ENUMERATED { f2, f4, f8 } INTEGER (1..8) INTEGER (1..8)
N-PCH ::= N-StartMessage ::=
3GPP
Release 6
901
3GPP TS 25.331 V6.23.0 (2009-09)
NB01 ::= NF-Max ::= NumberOfDPDCH ::= NumberOfFBI-Bits ::=
INTEGER (0..50) INTEGER (1..64) INTEGER (1..maxDPDCH-UL) INTEGER (1..2)
OpenLoopPowerControl-TDD ::= SEQUENCE { primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power, -- alpha, prach-ConstantValue, dpch-ConstantValue and pusch-ConstantValue -- shall be ignored in 1.28Mcps TDD mode. alpha Alpha OPTIONAL, prach-ConstantValue ConstantValueTdd, dpch-ConstantValue ConstantValueTdd, pusch-ConstantValue ConstantValueTdd OPTIONAL } OpenLoopPowerControl-IPDL-TDD-r4 ::= ipdl-alpha maxPowerIncrease } PagingIndicatorLength ::= SEQUENCE { Alpha, MaxPowerIncrease-r4
ENUMERATED { pi4, pi8, pi16 } INTEGER (0..7) ENUMERATED { as0, as8 } SEQUENCE { INTEGER (0..79), INTEGER (0..511), SecondaryScramblingCode PCP-Length, UCSM-Info
PC-Preamble ::= PCP-Length ::=
PCPCH-ChannelInfo ::= pcpch-UL-ScramblingCode pcpch-DL-ChannelisationCode pcpch-DL-ScramblingCode pcp-Length ucsm-Info } PCPCH-ChannelInfoList ::=
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxPCPCHs)) OF PCPCH-ChannelInfo ENUMERATED { mayBeUsed, shallNotBeUsed }
PCPICH-UsageForChannelEst ::=
PDSCH-CapacityAllocationInfo ::= SEQUENCE { -- pdsch-PowerControlInfo is conditional on new-configuration branch below, if this -- selected the IE is OPTIONAL otherwise it should not be sent pdsch-PowerControlInfo PDSCH-PowerControlInfo OPTIONAL, pdsch-AllocationPeriodInfo AllocationPeriodInfo, configuration CHOICE { old-Configuration SEQUENCE { tfcs-ID TFCS-IdentityPlain DEFAULT 1, pdsch-Identity PDSCH-Identity }, new-Configuration SEQUENCE { pdsch-Info PDSCH-Info, pdsch-Identity PDSCH-Identity OPTIONAL } } } PDSCH-CapacityAllocationInfo-r4 ::= SEQUENCE { pdsch-AllocationPeriodInfo AllocationPeriodInfo, configuration CHOICE { old-Configuration SEQUENCE { tfcs-ID TFCS-IdentityPlain pdsch-Identity PDSCH-Identity }, new-Configuration SEQUENCE { pdsch-Info PDSCH-Info-r4, pdsch-Identity PDSCH-Identity pdsch-PowerControlInfo PDSCH-PowerControlInfo } } }
DEFAULT 1,
OPTIONAL, OPTIONAL
3GPP
Release 6
902
3GPP TS 25.331 V6.23.0 (2009-09)
PDSCH-CodeInfo ::= spreadingFactor codeNumber multiCodeInfo } PDSCH-CodeInfoList ::=
SEQUENCE { SF-PDSCH, CodeNumberDSCH, MultiCodeInfo
SEQUENCE (SIZE (1..maxTFCI-2-Combs)) OF PDSCH-CodeInfo SEQUENCE { SF-PDSCH, MultiCodeInfo, CodeNumberDSCH, CodeNumberDSCH
PDSCH-CodeMap ::= spreadingFactor multiCodeInfo codeNumberStart codeNumberStop } PDSCH-CodeMapList ::=
SEQUENCE (SIZE (1..maxPDSCH-TFCIgroups)) OF PDSCH-CodeMap SEQUENCE { SecondaryScramblingCode CHOICE { CodeRange, DSCH-MappingList, PDSCH-CodeInfoList, ReplacedPDSCH-CodeInfoList
PDSCH-CodeMapping ::= dl-ScramblingCode signallingMethod codeRange tfci-Range explicit-config replace } } PDSCH-Identity ::=
OPTIONAL,
INTEGER (1..hiPDSCHidentities)
PDSCH-Info ::= tfcs-ID commonTimeslotInfo pdsch-TimeslotsCodes } PDSCH-Info-r4 ::= tfcs-ID commonTimeslotInfo tddOption tdd384 pdsch-TimeslotsCodes }, tdd128 pdsch-TimeslotsCodes } } } PDSCH-Info-LCR-r4 ::= tfcs-ID commonTimeslotInfo pdsch-TimeslotsCodes } PDSCH-PowerControlInfo ::= tpc-StepSizeTDD ul-CCTrChTPCList } PDSCH-SHO-DCH-Info ::= dsch-RadioLinkIdentifier rl-IdentifierList } PDSCH-SysInfo ::= pdsch-Identity pdsch-Info dsch-TFS dsch-TFCS } PDSCH-SysInfo-HCR-r5 ::= pdsch-Identity pdsch-Info
SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo DownlinkTimeslotsCodes
DEFAULT 1, OPTIONAL, OPTIONAL
SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo CHOICE { SEQUENCE { DownlinkTimeslotsCodes
DEFAULT 1, OPTIONAL,
OPTIONAL
OPTIONAL
SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo DownlinkTimeslotsCodes-LCR-r4
SEQUENCE { TPC-StepSizeTDD UL-CCTrChTPCList
OPTIONAL, OPTIONAL
SEQUENCE { DSCH-RadioLinkIdentifier, RL-IdentifierList
OPTIONAL
SEQUENCE { PDSCH-Identity, PDSCH-Info, TransportFormatSet TFCS
OPTIONAL, OPTIONAL
SEQUENCE { PDSCH-Identity, PDSCH-Info,
3GPP
Release 6
dsch-TransportChannelsInfo dsch-TFCS } PDSCH-SysInfo-LCR-r4 ::= pdsch-Identity pdsch-Info dsch-TFS dsch-TFCS } PDSCH-SysInfoList ::=
903
DSCH-TransportChannelsInfo TFCS
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL, OPTIONAL
SEQUENCE { PDSCH-Identity, PDSCH-Info-LCR-r4, TransportFormatSet TFCS
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxPDSCH)) OF PDSCH-SysInfo SEQUENCE (SIZE (1..maxPDSCH)) OF PDSCH-SysInfo-HCR-r5 SEQUENCE (SIZE (1..maxPDSCH)) OF PDSCH-SysInfo-LCR-r4 SEQUENCE (SIZE (1..maxPDSCH)) OF SEQUENCE { PDSCH-SysInfo, SFN-TimeInfo
PDSCH-SysInfoList-HCR-r5 ::= PDSCH-SysInfoList-LCR-r4 ::=
PDSCH-SysInfoList-SFN ::= pdsch-SysInfo sfn-TimeInfo } PDSCH-SysInfoList-SFN-HCR-r5 ::= pdsch-SysInfo sfn-TimeInfo } PDSCH-SysInfoList-SFN-LCR-r4 ::= pdsch-SysInfo sfn-TimeInfo } PersistenceScalingFactor ::=
OPTIONAL
SEQUENCE (SIZE (1..maxPDSCH)) OF SEQUENCE { PDSCH-SysInfo-HCR-r5, SFN-TimeInfo OPTIONAL
SEQUENCE (SIZE (1..maxPDSCH)) OF SEQUENCE { PDSCH-SysInfo-LCR-r4, SFN-TimeInfo
OPTIONAL
ENUMERATED { psf0-9, psf0-8, psf0-7, psf0-6, psf0-5, psf0-4, psf0-3, psf0-2 } SEQUENCE (SIZE (1..maxASCpersist)) OF PersistenceScalingFactor ENUMERATED { e18, e36, e72, e144 } SEQUENCE (SIZE (1..2)) OF DL-TS-ChannelisationCode
PersistenceScalingFactorList ::=
PI-CountPerFrame ::=
PichChannelisationCodeList-LCR-r4 ::=
PICH-Info ::= CHOICE { fdd SEQUENCE { channelisationCode256 ChannelisationCode256, pi-CountPerFrame PI-CountPerFrame, sttd-Indicator BOOLEAN }, tdd SEQUENCE { channelisationCode TDD-PICH-CCode timeslot TimeslotNumber midambleShiftAndBurstType MidambleShiftAndBurstType, repetitionPeriodLengthOffset RepPerLengthOffset-PICH pagingIndicatorLength PagingIndicatorLength n-GAP N-GAP n-PCH N-PCH } }
OPTIONAL, OPTIONAL, OPTIONAL, DEFAULT pi4, DEFAULT f4, DEFAULT 2
PICH-Info-LCR-r4 ::= SEQUENCE { timeslot TimeslotNumber-LCR-r4 OPTIONAL, pichChannelisationCodeList-LCR-r4 PichChannelisationCodeList-LCR-r4, midambleShiftAndBurstType MidambleShiftAndBurstType-LCR-r4, repetitionPeriodLengthOffset RepPerLengthOffset-PICH OPTIONAL, pagingIndicatorLength PagingIndicatorLength DEFAULT pi4, n-GAP N-GAP DEFAULT f4, n-PCH N-PCH DEFAULT 2 } PICH-PowerOffset ::= INTEGER (-10..5)
3GPP
Release 6
904
3GPP TS 25.331 V6.23.0 (2009-09)
PilotBits128 ::=
ENUMERATED { pb4, pb8 } ENUMERATED { pb2, pb4, pb8 }
PilotBits256 ::=
-- Actual measurement power offset value = IE value * 0.5 MeasurementPowerOffset ::= INTEGER (-12..26) PositionFixedOrFlexible ::= ENUMERATED { fixed, flexible } CHOICE { TPC-StepSizeFDD, NULL
PowerControlAlgorithm ::= algorithm1 algorithm2 } PowerOffsetPilot-pdpdch ::= PowerOffsetTPC-pdpdch ::= PowerRampStep ::= PRACH-ChanCodes-LCR-r4 ::=
INTEGER (0..24) INTEGER (0..24) INTEGER (1..8) SEQUENCE (SIZE (1..4)) OF TDD-PRACH-CCode-LCR-r4 SEQUENCE { TimeslotNumber-PRACH-LCR-r4, PRACH-ChanCodes-LCR-r4, MidambleShiftAndBurstType-LCR-r4, FPACH-Info-r4
PRACH-Definition-LCR-r4 ::= timeslot prach-ChanCodes-LCR midambleShiftAndBurstType fpach-Info } PRACH-Midamble ::=
ENUMERATED { direct, direct-Inverted }
PRACH-Partitioning ::= CHOICE { fdd SEQUENCE (SIZE (1..maxASC)) OF -- TABULAR: If only "NumASC+1" (with, NumASC+1 < maxASC) ASCSetting-FDD are listed, -- the remaining (NumASC+2 through maxASC) ASCs are unspecified. ASCSetting-FDD, tdd SEQUENCE (SIZE (1..maxASC)) OF -- TABULAR: If only "NumASC+1" (with, NumASC+1 < maxASC) ASCSetting-TDD are listed, -- the remaining (NumASC+2 through maxASC) ASCs are unspecified. ASCSetting-TDD } PRACH-Partitioning-LCR-r4 ::= SEQUENCE (SIZE (1..maxASC)) OF -- TABULAR: If only "NumASC+1" (with, NumASC+1 < maxASC) ASCSetting-TDD-LCR-r4 are listed, -- the remaining (NumASC+2 through maxASC) ASCs are unspecified. ASCSetting-TDD-LCR-r4 PRACH-PowerOffset ::= powerRampStep preambleRetransMax } SEQUENCE { PowerRampStep, PreambleRetransMax
PRACH-RACH-Info ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { availableSignatures AvailableSignatures, availableSF SF-PRACH, preambleScramblingCodeWordNumber PreambleScramblingCodeWordNumber, puncturingLimit PuncturingLimit, availableSubChannelNumbers AvailableSubChannelNumbers }, tdd SEQUENCE { timeslot TimeslotNumber, channelisationCodeList TDD-PRACH-CCodeList, prach-Midamble PRACH-Midamble } } } PRACH-RACH-Info-LCR-r4 ::= SEQUENCE {
3GPP
Release 6
sync-UL-Info prach-DefinitionList }
905
3GPP TS 25.331 V6.23.0 (2009-09)
SYNC-UL-Info-r4, SEQUENCE (SIZE (1..maxPRACH-FPACH)) OF PRACH-Definition-LCR-r4
PRACH-SystemInformation ::= SEQUENCE { prach-RACH-Info PRACH-RACH-Info, transportChannelIdentity TransportChannelIdentity, rach-TransportFormatSet TransportFormatSet rach-TFCS TFCS prach-Partitioning PRACH-Partitioning persistenceScalingFactorList PersistenceScalingFactorList ac-To-ASC-MappingTable AC-To-ASC-MappingTable modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-TX-Power PrimaryCPICH-TX-Power constantValue ConstantValue prach-PowerOffset PRACH-PowerOffset rach-TransmissionParameters RACH-TransmissionParameters aich-Info AICH-Info }, tdd NULL } } PRACH-SystemInformation-LCR-r4 ::= prach-RACH-Info-LCR rach-TransportFormatSet-LCR prach-Partitioning-LCR } PRACH-SystemInformationList ::= SEQUENCE { PRACH-RACH-Info-LCR-r4, TransportFormatSet-LCR PRACH-Partitioning-LCR-r4
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxPRACH)) OF PRACH-SystemInformation SEQUENCE (SIZE (1..maxPRACH)) OF PRACH-SystemInformation-LCR-r4
PRACH-SystemInformationList-LCR-r4 ::=
PreambleRetransMax ::=
INTEGER (1..64) INTEGER (0..15)
PreambleScramblingCodeWordNumber ::= PreDefPhyChConfiguration ::= ul-DPCH-InfoPredef dl-CommonInformationPredef }
SEQUENCE { UL-DPCH-InfoPredef, DL-CommonInformationPredef
OPTIONAL
PrimaryCCPCH-Info ::= CHOICE { fdd SEQUENCE { tx-DiversityIndicator BOOLEAN }, tdd SEQUENCE { -- syncCase should be ignored for 1.28Mcps TDD mode syncCase CHOICE { syncCase1 SEQUENCE { timeslot TimeslotNumber }, syncCase2 SEQUENCE { timeslotSync2 TimeslotSync2 } } cellParametersID CellParametersID sctd-Indicator BOOLEAN } } PrimaryCCPCH-Info-r4 ::= CHOICE { fdd SEQUENCE { tx-DiversityIndicator BOOLEAN }, tdd SEQUENCE { tddOption CHOICE { tdd384 SEQUENCE { syncCase CHOICE { syncCase1 SEQUENCE { timeslot TimeslotNumber }, syncCase2 SEQUENCE { timeslotSync2 TimeslotSync2
OPTIONAL, OPTIONAL,
3GPP
Release 6
} } }, tdd128 tstd-Indicator } }, cellParametersID sctd-Indicator } } PrimaryCCPCH-Info-LCR-r4 ::= tstd-Indicator cellParametersID sctd-Indicator }
906
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL SEQUENCE { BOOLEAN
CellParametersID BOOLEAN
OPTIONAL,
SEQUENCE { BOOLEAN, CellParametersID BOOLEAN
OPTIONAL,
-- For 1.28Mcps TDD, the following IE includes elements for the PCCPCH Info additional to those -- in PrimaryCCPCH-Info PrimaryCCPCH-Info-LCR-r4-ext ::= SEQUENCE { tstd-Indicator BOOLEAN } PrimaryCCPCH-InfoPost ::= syncCase syncCase1 timeslot }, syncCase2 timeslotSync2 } }, cellParametersID sctd-Indicator } SEQUENCE { CHOICE { SEQUENCE { TimeslotNumber SEQUENCE { TimeslotSync2
CellParametersID, BOOLEAN
PrimaryCCPCH-InfoPostTDD-LCR-r4 ::= SEQUENCE { tstd-Indicator BOOLEAN, cellParametersID CellParametersID, sctd-Indicator BOOLEAN } PrimaryCCPCH-TX-Power ::= PrimaryCPICH-Info ::= primaryScramblingCode } PrimaryCPICH-TX-Power ::= PrimaryScramblingCode ::= PuncturingLimit ::= INTEGER (6..43) SEQUENCE { PrimaryScramblingCode
INTEGER (-10..50) INTEGER (0..511) ENUMERATED { pl0-40, pl0-44, pl0-48, pl0-52, pl0-56, pl0-60, pl0-64, pl0-68, pl0-72, pl0-76, pl0-80, pl0-84, pl0-88, pl0-92, pl0-96, pl1 }
PUSCH-CapacityAllocationInfo ::= SEQUENCE { pusch-Allocation CHOICE { pusch-AllocationPending NULL, pusch-AllocationAssignment SEQUENCE { pusch-AllocationPeriodInfo AllocationPeriodInfo, pusch-PowerControlInfo UL-TargetSIR configuration CHOICE { old-Configuration SEQUENCE { tfcs-ID TFCS-IdentityPlain pusch-Identity PUSCH-Identity }, new-Configuration SEQUENCE { pusch-Info PUSCH-Info, pusch-Identity PUSCH-Identity } } } } }
OPTIONAL,
DEFAULT 1,
OPTIONAL
3GPP
Release 6
907
3GPP TS 25.331 V6.23.0 (2009-09)
PUSCH-CapacityAllocationInfo-r4 ::= SEQUENCE { pusch-Allocation CHOICE { pusch-AllocationPending NULL, pusch-AllocationAssignment SEQUENCE { pusch-AllocationPeriodInfo AllocationPeriodInfo, pusch-PowerControlInfo PUSCH-PowerControlInfo-r4 configuration CHOICE { old-Configuration SEQUENCE { tfcs-ID TFCS-IdentityPlain pusch-Identity PUSCH-Identity }, new-Configuration SEQUENCE { pusch-Info PUSCH-Info-r4, pusch-Identity PUSCH-Identity } } } } } PUSCH-Identity ::= PUSCH-Info ::= tfcs-ID commonTimeslotInfo pusch-TimeslotsCodes } PUSCH-Info-r4 ::= tfcs-ID commonTimeslotInfo tddOption tdd384 pusch-TimeslotsCodes }, tdd128 pusch-TimeslotsCodes } } } PUSCH-Info-LCR-r4 ::= tfcs-ID commonTimeslotInfo pusch-TimeslotsCodes } PUSCH-PowerControlInfo-r4 ::= SEQUENCE { -- The IE ul-TargetSIR corresponds to PRX-PUSCHdes for 1.28Mcps TDD -- Actual value PRX-PUSCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR, tddOption CHOICE { tdd384 NULL, tdd128 SEQUENCE { tpc-StepSize TPC-StepSizeTDD } } } PUSCH-SysInfo ::= pusch-Identity pusch-Info usch-TFS usch-TFCS } PUSCH-SysInfo-HCR-r5 ::= pusch-Identity pusch-Info usch-TransportChannelsInfo usch-TFCS } PUSCH-SysInfo-LCR-r4 ::= pusch-Identity pusch-Info usch-TFS SEQUENCE { PUSCH-Identity, PUSCH-Info, TransportFormatSet TFCS INTEGER (1..hiPUSCHidentities) SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo UplinkTimeslotsCodes
OPTIONAL,
DEFAULT 1,
OPTIONAL
SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo CHOICE { SEQUENCE { UplinkTimeslotsCodes
OPTIONAL
SEQUENCE { UplinkTimeslotsCodes-LCR-r4 OPTIONAL
SEQUENCE { TFCS-IdentityPlain CommonTimeslotInfo UplinkTimeslotsCodes-LCR-r4
OPTIONAL
OPTIONAL, OPTIONAL
SEQUENCE { PUSCH-Identity, PUSCH-Info, USCH-TransportChannelsInfo TFCS
OPTIONAL, OPTIONAL
SEQUENCE { PUSCH-Identity, PUSCH-Info-LCR-r4, TransportFormatSet
OPTIONAL,
3GPP
Release 6
usch-TFCS } PUSCH-SysInfoList ::= TFCS
908
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
SEQUENCE (SIZE (1..maxPUSCH)) OF PUSCH-SysInfo SEQUENCE (SIZE (1..maxPUSCH)) OF PUSCH-SysInfo-HCR-r5 SEQUENCE (SIZE (1..maxPUSCH)) OF PUSCH-SysInfo-LCR-r4 SEQUENCE (SIZE (1..maxPUSCH)) OF SEQUENCE { PUSCH-SysInfo, SFN-TimeInfo
PUSCH-SysInfoList-HCR-r5 ::= PUSCH-SysInfoList-LCR-r4 ::=
PUSCH-SysInfoList-SFN ::= pusch-SysInfo sfn-TimeInfo } PUSCH-SysInfoList-SFN-HCR-r5 ::= pusch-SysInfo sfn-TimeInfo } PUSCH-SysInfoList-SFN-LCR-r4 ::= pusch-SysInfo sfn-TimeInfo } RACH-TransmissionParameters ::= mmax nb01Min nb01Max } ReducedScramblingCodeNumber ::=
OPTIONAL
SEQUENCE (SIZE (1..maxPUSCH)) OF SEQUENCE { PUSCH-SysInfo-HCR-r5, SFN-TimeInfo OPTIONAL
SEQUENCE (SIZE (1..maxPUSCH)) OF SEQUENCE { PUSCH-SysInfo-LCR-r4, SFN-TimeInfo
OPTIONAL
SEQUENCE { INTEGER (1..32), NB01, NB01
INTEGER (0..8191)
RepetitionPeriodAndLength ::= CHOICE { repetitionPeriod1 NULL, -- repetitionPeriod2 could just as well be NULL also. repetitionPeriod2 INTEGER (1..1), repetitionPeriod4 INTEGER (1..3), repetitionPeriod8 INTEGER (1..7), repetitionPeriod16 INTEGER (1..15), repetitionPeriod32 INTEGER (1..31), repetitionPeriod64 INTEGER (1..63) } RepetitionPeriodLengthAndOffset ::= CHOICE { repetitionPeriod1 NULL, repetitionPeriod2 SEQUENCE { length NULL, offset INTEGER }, repetitionPeriod4 SEQUENCE { length INTEGER offset INTEGER }, repetitionPeriod8 SEQUENCE { length INTEGER offset INTEGER }, repetitionPeriod16 SEQUENCE { length INTEGER offset INTEGER }, repetitionPeriod32 SEQUENCE { length INTEGER offset INTEGER }, repetitionPeriod64 SEQUENCE { length INTEGER offset INTEGER } } ReplacedPDSCH-CodeInfo ::= tfci-Field2
(0..1)
(1..3), (0..3)
(1..7), (0..7)
(1..15), (0..15)
(1..31), (0..31)
(1..63), (0..63)
SEQUENCE { MaxTFCI-Field2Value,
3GPP
Release 6
spreadingFactor codeNumber multiCodeInfo } ReplacedPDSCH-CodeInfoList ::=
909
SF-PDSCH, CodeNumberDSCH, MultiCodeInfo
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxTFCI-2-Combs)) OF ReplacedPDSCH-CodeInfo CHOICE { INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER
RepPerLengthOffset-PICH ::= rpp4-2 rpp8-2 rpp8-4 rpp16-2 rpp16-4 rpp32-2 rpp32-4 rpp64-2 rpp64-4 } RepPerLengthOffset-MICH ::= rpp4-2 rpp8-2 rpp8-4 rpp16-2 rpp16-4 rpp32-2 rpp32-4 rpp64-2 rpp64-4 } RestrictedTrCH ::= dl-restrictedTrCh-Type restrictedDL-TrCH-Identity allowedTFIList } RestrictedTrCH-InfoList ::=
(0..3), (0..7), (0..7), (0..15), (0..15), (0..31), (0..31), (0..63), (0..63)
CHOICE { INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER
(0..3), (0..7), (0..7), (0..15), (0..15), (0..31), (0..31), (0..63), (0..63)
SEQUENCE { DL-TrCH-Type, TransportChannelIdentity, AllowedTFI-List
SEQUENCE (SIZE(1..maxTrCH)) OF RestrictedTrCH
RL-AdditionInformation ::= SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info, dl-DPCH-InfoPerRL DL-DPCH-InfoPerRL, -- dummy and dummy2 are not used in this version of specification -- and the IEs should be ignored. dummy BOOLEAN, dummy2 SCCPCH-InfoForFACH } RL-AdditionInformation-r6 ::= primaryCPICH-Info cell-Id dl-dpchInfo dl-DPCH-InfoPerRL dl-FDPCH-InfoPerRL }, e-HICH-Information e-RGCH-Information } SEQUENCE { PrimaryCPICH-Info, CellIdentity CHOICE { DL-DPCH-InfoPerRL-r5, DL-FDPCH-InfoPerRL-r6 E-HICH-Information E-RGCH-Information
OPTIONAL
OPTIONAL,
OPTIONAL, OPTIONAL
RL-AdditionInformation-v6b0ext ::= SEQUENCE { sttdIndication STTDIndication } RL-AdditionInformationList ::=
OPTIONAL
SEQUENCE (SIZE (1..maxRL-1)) OF RL-AdditionInformation SEQUENCE (SIZE (1..maxRL-1)) OF RL-AdditionInformation-r6
RL-AdditionInformationList-r6 ::=
RL-AdditionInformation-list-v6b0ext ::= SEQUENCE (SIZE (1..maxRL)) OF RL-AdditionInformation-v6b0ext RL-IdentifierList ::= SEQUENCE (SIZE (1..maxRL)) OF PrimaryCPICH-Info SEQUENCE (SIZE (1..maxRL)) OF
RL-RemovalInformationList ::=
3GPP
Release 6
910
PrimaryCPICH-Info
3GPP TS 25.331 V6.23.0 (2009-09)
RPP ::=
ENUMERATED { mode0, mode1 } ENUMERATED { e1bit, e2bits } ENUMERATED { cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 } SEQUENCE (SIZE (1..16)) OF SCCPCH-ChannelisationCode
S-Field ::=
SCCPCH-ChannelisationCode ::=
SCCPCH-ChannelisationCodeList ::=
SCCPCH-InfoForFACH ::= SEQUENCE { secondaryCCPCH-Info SecondaryCCPCH-Info, tfcs TFCS, modeSpecificInfo CHOICE { fdd SEQUENCE { fach-PCH-InformationList FACH-PCH-InformationList, sib-ReferenceListFACH SIB-ReferenceListFACH }, tdd SEQUENCE { fach-PCH-InformationList FACH-PCH-InformationList } } } SCCPCH-InfoForFACH-r4 ::= secondaryCCPCH-Info tfcs fach-PCH-InformationList modeSpecificInfo fdd sib-ReferenceListFACH }, tdd } } SCCPCH-SystemInformation ::= secondaryCCPCH-Info tfcs fach-PCH-InformationList pich-Info } SEQUENCE { SecondaryCCPCH-Info-r4, TFCS, FACH-PCH-InformationList, CHOICE { SEQUENCE { SIB-ReferenceListFACH NULL
SEQUENCE { SecondaryCCPCH-Info, TFCS FACH-PCH-InformationList PICH-Info
SCCPCH-SystemInformation-LCR-r4-ext ::= SEQUENCE { secondaryCCPCH-LCR-Extensions SecondaryCCPCH-Info-LCR-r4-ext, -- pich-Info in the SCCPCH-SystemInformation IE shall be absent, -- and instead the following used. pich-Info PICH-Info-LCR-r4 } SCCPCH-SystemInformationList ::= SEQUENCE (SIZE (1..maxSCCPCH)) OF SCCPCH-SystemInformation
OPTIONAL
-- SCCPCH-SystemInformationList-LCR-r4-ext includes elements additional to those in -- SCCPCH-SystemInformationList for the 1.28Mcps TDD. The order of the IEs -- indicates which SCCPCH-SystemInformation-LCR-r4-ext IE extends which -- SCCPCH-SystemInformation IE. SCCPCH-SystemInformationList-LCR-r4-ext ::= SEQUENCE (SIZE (1..maxSCCPCH)) OF SCCPCH-SystemInformation-LCR-r4-ext -- The SCCPCH-SystemInformation-MBMS-r6 is used for an S-CCPCH dedicated for MBMS purposes. SCCPCH-SystemInformation-MBMS-r6 ::= SEQUENCE { secondaryCCPCHInfo-MBMS SecondaryCCPCHInfo-MBMS-r6, transportFormatCombinationSet TFCS, fachCarryingMCCH SEQUENCE { mcch-transportFormatSet TransportFormatSet, mcch-ConfigurationInfo MBMS-MCCH-ConfigurationInfo-r6 }, fachCarryingMTCH-List MBMS-FACHCarryingMTCH-List OPTIONAL, -- If schedulingInformation is provided fachCarryingMSCH SEQUENCE {
3GPP
Release 6
911
3GPP TS 25.331 V6.23.0 (2009-09)
} }
msch-transportFormatSet TransportFormatSet, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy MBMS-MSCH-ConfigurationInfo-r6 OPTIONAL
ScramblingCodeChange ::=
ENUMERATED { codeChange, noCodeChange } ENUMERATED { shortSC, longSC }
ScramblingCodeType ::=
SecondaryCCPCH-Info ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy1 is not used in this version of the specification and should be ignored. dummy1 PCPICH-UsageForChannelEst, -- dummy2 is not used in this version of the specification. It should not -- be sent and if received it should be ignored. dummy2 SecondaryCPICH-Info OPTIONAL, secondaryScramblingCode SecondaryScramblingCode OPTIONAL, sttd-Indicator BOOLEAN, sf-AndCodeNumber SF256-AndCodeNumber, pilotSymbolExistence BOOLEAN, tfci-Existence BOOLEAN, positionFixedOrFlexible PositionFixedOrFlexible, timingOffset TimingOffset DEFAULT 0 }, tdd SEQUENCE { -- TABULAR: the offset is included in CommonTimeslotInfoSCCPCH commonTimeslotInfo CommonTimeslotInfoSCCPCH, individualTimeslotInfo IndividualTimeslotInfo, channelisationCode SCCPCH-ChannelisationCodeList } } } SecondaryCCPCH-Info-r4 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { secondaryScramblingCode SecondaryScramblingCode OPTIONAL, sttd-Indicator BOOLEAN, sf-AndCodeNumber SF256-AndCodeNumber, pilotSymbolExistence BOOLEAN, tfci-Existence BOOLEAN, positionFixedOrFlexible PositionFixedOrFlexible, timingOffset TimingOffset DEFAULT 0 }, tdd SEQUENCE { -- TABULAR: the offset is included in CommonTimeslotInfoSCCPCH commonTimeslotInfo CommonTimeslotInfoSCCPCH, tddOption CHOICE { tdd384 SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo }, tdd128 SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo-LCR-r4 } }, channelisationCode SCCPCH-ChannelisationCodeList } } } SecondaryCCPCH-Info-LCR-r4-ext ::= individualTimeslotLCR-Ext } SEQUENCE { IndividualTimeslotInfo-LCR-r4-ext
SecondaryCCPCHInfo-MBMS-r6 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { secondaryScramblingCode SecondaryScramblingCode sttd-Indicator BOOLEAN, sf-AndCodeNumber SF256-AndCodeNumber, timingOffset TimingOffset },
OPTIONAL,
DEFAULT 0
3GPP
Release 6
tdd384 commonTimeslotInfoMBMS downlinkTimeslotsCodes }, tdd128 commonTimeslotInfoMBMS downlinkTimeslotsCodes } } } SecondaryCPICH-Info ::= secondaryDL-ScramblingCode channelisationCode } SecondaryScramblingCode ::= SecondInterleavingMode ::=
912
SEQUENCE { CommonTimeslotInfoMBMS, DownlinkTimeslotsCodes
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { CommonTimeslotInfoMBMS, DownlinkTimeslotsCodes-LCR-r4
SEQUENCE { SecondaryScramblingCode ChannelisationCode256
OPTIONAL,
INTEGER (1..15) ENUMERATED { frameRelated, timeslotRelated }
-- SF256-AndCodeNumber encodes both "Spreading factor" and "Code Number" SF256-AndCodeNumber ::= CHOICE { sf4 INTEGER (0..3), sf8 INTEGER (0..7), sf16 INTEGER (0..15), sf32 INTEGER (0..31), sf64 INTEGER (0..63), sf128 INTEGER (0..127), sf256 INTEGER (0..255) } -- SF512-AndCodeNumber encodes both "Spreading factor" and "Code Number" SF512-AndCodeNumber ::= CHOICE { sf4 INTEGER (0..3), sf8 INTEGER (0..7), sf16 INTEGER (0..15), sf32 INTEGER (0..31), sf64 INTEGER (0..63), sf128 INTEGER (0..127), sf256 INTEGER (0..255), sf512 INTEGER (0..511) } -- SF512-AndPilot encodes both "Spreading factor" and "Number of bits for Pilot bits" SF512-AndPilot ::= CHOICE { sfd4 NULL, sfd8 NULL, sfd16 NULL, sfd32 NULL, sfd64 NULL, sfd128 PilotBits128, sfd256 PilotBits256, sfd512 NULL } SF-PDSCH ::= ENUMERATED { sfp4, sfp8, sfp16, sfp32, sfp64, sfp128, sfp256 } SF-PRACH ::= ENUMERATED { sfpr32, sfpr64, sfpr128, sfpr256 } SEQUENCE { INTEGER (0..4095), DurationTimeInfo
value +1)
SFN-TimeInfo ::= activationTimeSFN physChDuration }
-- actual scheduling value = 2(signalled SpecialBurstScheduling ::= SpreadingFactor ::=
and is the periodicity of sending special burst frames INTEGER (0..7)
ENUMERATED { sf4, sf8, sf16, sf32, sf64, sf128, sf256 } INTEGER (0..7) ENUMERATED { ssdt-id-a, ssdt-id-b, ssdt-id-c,
SRB-delay ::= SSDT-CellIdentity ::=
3GPP
Release 6
913
3GPP TS 25.331 V6.23.0 (2009-09)
ssdt-id-d, ssdt-id-e, ssdt-id-f, ssdt-id-g, ssdt-id-h } SSDT-Information ::= s-Field codeWordSet } SSDT-Information-r4 ::= s-Field codeWordSet ssdt-UL-r4 } SSDT-UL ::= SEQUENCE { S-Field, CodeWordSet
SEQUENCE { S-Field, CodeWordSet, SSDT-UL
OPTIONAL
ENUMERATED { ul, ul-AndDL } ENUMERATED { true }
STTDIndication ::= SynchronisationParameters-r4 ::= sync-UL-CodesBitmap
SEQUENCE { BIT STRING { code7(0), code6(1), code5(2), code4(3), code3(4), code2(5), code1(6), code0(7) } (SIZE (8)), fpach-Info FPACH-Info-r4, -- Actual value prxUpPCHdes = IE value - 120 prxUpPCHdes INTEGER (0..62), sync-UL-Procedure SYNC-UL-Procedure-r4
OPTIONAL
} SYNC-UL-Procedure-r4 ::= max-SYNC-UL-Transmissions powerRampStep } SYNC-UL-Info-r4 ::= sync-UL-Codes-Bitmap SEQUENCE { ENUMERATED { tr1, tr2, tr4, tr8 }, INTEGER (0..3)
SEQUENCE { BIT STRING { code7(0), code6(1), code5(2), code4(3), code3(4), code2(5), code1(6), code0(7) } ( SIZE (8)), -- Actual value prxUpPCHdes = IE value - 120 prxUpPCHdes INTEGER (0..62), powerRampStep INTEGER (0..3), max-SYNC-UL-Transmissions ENUMERATED { tr1, tr2, tr4, tr8 } , mmax INTEGER(1..32)
} TDD-FPACH-CCode16-r4 ::= ENUMERATED { cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 } INTEGER (-110..-52) ENUMERATED { cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 } ENUMERATED { cc8-1, cc8-2, cc8-3, cc8-4, cc8-5, cc8-6, cc8-7, cc8-8 } ENUMERATED {
TDD-UL-Interference ::= TDD-PICH-CCode ::=
TDD-PRACH-CCode8 ::=
TDD-PRACH-CCode16 ::=
3GPP
Release 6
914
3GPP TS 25.331 V6.23.0 (2009-09)
cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 } TDD-PRACH-CCode-LCR-r4 ::= ENUMERATED { cc4-1, cc4-2, cc4-3, cc4-4, cc8-1, cc8-2, cc8-3, cc8-4, cc8-5, cc8-6, cc8-7, cc8-8, cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 }
TDD-PRACH-CCodeList ::= sf8
CHOICE { SEQUENCE (SIZE (1..8)) OF TDD-PRACH-CCode8, -- Channelisation codes cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, -- cc16-15 and cc16-16 shall not be used sf16 SEQUENCE (SIZE (1..8)) OF TDD-PRACH-CCode16 } TFC-ControlDuration ::= ENUMERATED { tfc-cd1, tfc-cd2, tfc-cd4, tfc-cd8, tfc-cd16, tfc-cd24, tfc-cd32, tfc-cd48, tfc-cd64, tfc-cd128, tfc-cd192, tfc-cd256, tfc-cd512 } ENUMERATED { tfci-bits-4, tfci-bits-8, tfci-bits-16, tfci-bits-32 } INTEGER (0..255)
TFCI-Coding ::=
TGCFN ::=
-- In TGD, value 270 represents "undefined" in the tabular description. TGD ::= INTEGER (15..270) TGL ::= TGMP ::= INTEGER (1..14) ENUMERATED { tdd-Measurement, fdd-Measurement, gsm-CarrierRSSIMeasurement, gsm-initialBSICIdentification, gsmBSICReconfirmation, multi-carrier } SEQUENCE { TGPSI, CHOICE { SEQUENCE { TGCFN NULL TGPS-ConfigurationParams OPTIONAL
TGP-Sequence ::= tgpsi tgps-Status activate tgcfn }, deactivate }, tgps-ConfigurationParams } TGPS-Reconfiguration-CFN ::= TGP-SequenceList ::=
INTEGER (0..255) SEQUENCE (SIZE (1..maxTGPS)) OF TGP-Sequence SEQUENCE { TGPSI, CHOICE { SEQUENCE { TGCFN NULL
TGP-SequenceShort ::= tgpsi tgps-Status activate tgcfn }, deactivate } } TGPL ::=
INTEGER (1..144)
-- TABULAR: In TGPRC, value 0 represents "infinity" in the tabular description. TGPRC ::= INTEGER (0..511) TGPS-ConfigurationParams ::= SEQUENCE {
3GPP
Release 6
915
3GPP TS 25.331 V6.23.0 (2009-09)
tgmp TGMP, tgprc TGPRC, tgsn TGSN, tgl1 TGL, tgl2 TGL OPTIONAL, tgd TGD, tgpl1 TGPL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it shall be ignored. dummy TGPL OPTIONAL, rpp RPP, itp ITP, -- TABULAR: Compressed mode method is nested inside UL-DL-Mode ul-DL-Mode UL-DL-Mode, dl-FrameType DL-FrameType, deltaSIR1 DeltaSIR, deltaSIRAfter1 DeltaSIR, deltaSIR2 DeltaSIR OPTIONAL, deltaSIRAfter2 DeltaSIR OPTIONAL, nidentifyAbort NidentifyAbort OPTIONAL, treconfirmAbort TreconfirmAbort OPTIONAL } TGPSI ::= TGSN ::= TimeInfo ::= activationTime durationTimeInfo } TimeslotList ::= INTEGER (1..maxTGPS) INTEGER (0..14) SEQUENCE { ActivationTime DurationTimeInfo
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxTS)) OF TimeslotNumber CHOICE { SEQUENCE (SIZE (1..maxTS)) OF TimeslotNumber, SEQUENCE (SIZE (1..maxTS-LCR)) OF TimeslotNumber-LCR-r4
TimeslotList-r4 ::= tdd384 tdd128 }
-- If TimeslotNumber is included for a 1.28Mcps TDD description, it shall take values from 0..6 TimeslotNumber ::= INTEGER (0..14) TimeslotNumber-LCR-r4 ::= TimeslotNumber-PRACH-LCR-r4 ::= TimeslotSync2 ::= INTEGER (0..6) INTEGER (1..6) INTEGER (0..6)
-- Actual value TimingOffset = IE value * 256 TimingOffset ::= INTEGER (0..149) TimingMaintainedSynchInd ::= TPC-CombinationIndex ::= ENUMERATED { false } INTEGER (0..5)
-- Actual value TPC-StepSizeFDD = IE value + 1 TPC-StepSizeFDD ::= INTEGER (0..1) TPC-StepSizeTDD ::= INTEGER (1..3)
-- Actual value TreconfirmAbort = IE value * 0.5 seconds TreconfirmAbort ::= INTEGER (1..20) TX-DiversityMode ::= ENUMERATED { noDiversity, sttd, closedLoopMode1, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy } INTEGER (0..16383) SEQUENCE { MinimumSpreadingFactor,
UARFCN ::= UCSM-Info ::= minimumSpreadingFactor
3GPP
Release 6
nf-Max channelReqParamsForUCSM } UL-CCTrCH ::= tfcs-ID ul-TargetSIR timeInfo commonTimeslotInfo ul-CCTrCH-TimeslotsCodes }
916
NF-Max, ChannelReqParamsForUCSM
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { TFCS-IdentityPlain UL-TargetSIR, TimeInfo, CommonTimeslotInfo UplinkTimeslotsCodes
DEFAULT 1,
OPTIONAL, OPTIONAL
UL-CCTrCH-r4 ::= SEQUENCE { tfcs-ID TFCS-IdentityPlain -- The IE ul-TargetSIR corresponds to PRX-DPCHdes for 1.28Mcps TDD -- Actual value PRX-DPCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR, timeInfo TimeInfo, commonTimeslotInfo CommonTimeslotInfo tddOption CHOICE { tdd384 SEQUENCE { ul-CCTrCH-TimeslotsCodes UplinkTimeslotsCodes }, tdd128 SEQUENCE { ul-CCTrCH-TimeslotsCodes UplinkTimeslotsCodes-LCR-r4 } } } UL-CCTrCHList ::= SEQUENCE (SIZE (1..maxCCTrCH)) OF UL-CCTrCH SEQUENCE (SIZE (1..maxCCTrCH)) OF UL-CCTrCH-r4 SEQUENCE (SIZE (1..maxCCTrCH)) OF TFCS-IdentityPlain SEQUENCE (SIZE (0..maxCCTrCH)) OF TFCS-Identity
DEFAULT 1,
OPTIONAL,
OPTIONAL
OPTIONAL
UL-CCTrCHList-r4 ::=
UL-CCTrCHListToRemove ::=
UL-CCTrChTPCList ::=
UL-ChannelRequirement ::= CHOICE { ul-DPCH-Info UL-DPCH-Info, -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. dummy CPCH-SetInfo } UL-ChannelRequirement-r4 ::= CHOICE { ul-DPCH-Info UL-DPCH-Info-r4, -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. dummy CPCH-SetInfo } UL-ChannelRequirement-r5 ::= CHOICE { ul-DPCH-Info UL-DPCH-Info-r5, -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. dummy CPCH-SetInfo } -- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. UL-ChannelRequirementWithCPCH-SetID ::= CHOICE { ul-DPCH-Info UL-DPCH-Info, -- dummy1 and dummy 2 are not used in this version of the specification, they should -- not be sent and if received the UE behaviour is not specified. dummy1 CPCH-SetInfo, dummy2 CPCH-SetID } -- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. UL-ChannelRequirementWithCPCH-SetID-r4 ::= CHOICE { ul-DPCH-Info UL-DPCH-Info-r4, -- dummy1 and dummy2 are not used in this version of the specification, they -- should not be sent and if received the UE behaviour is not specified.
3GPP
Release 6
dummy1 dummy2 }
917
CPCH-SetInfo, CPCH-SetID
3GPP TS 25.331 V6.23.0 (2009-09)
-- Note: the reference to CPCH in the element name below is incorrect. The name is not -- changed to keep it aligned with R99. UL-ChannelRequirementWithCPCH-SetID-r5 ::= CHOICE { ul-DPCH-Info UL-DPCH-Info-r5, -- dummy1 and dummy2 are not used in this version of the specification, they should -- not be sent and if received the UE behaviour is not specified. dummy1 CPCH-SetInfo, dummy2 CPCH-SetID } UL-CompressedModeMethod ::= ENUMERATED { sf-2, higherLayerScheduling } CHOICE { UL-CompressedModeMethod, DL-CompressedModeMethod, SEQUENCE { UL-CompressedModeMethod, DL-CompressedModeMethod
UL-DL-Mode ::= ul dl ul-and-dl ul dl }} UL-DPCCH-SlotFormat ::=
ENUMERATED { slf0, slf1, slf2 }
UL-DPCH-Info ::= SEQUENCE { ul-DPCH-PowerControlInfo UL-DPCH-PowerControlInfo modeSpecificInfo CHOICE { fdd SEQUENCE { scramblingCodeType ScramblingCodeType, scramblingCode UL-ScramblingCode, numberOfDPDCH NumberOfDPDCH spreadingFactor SpreadingFactor, tfci-Existence BOOLEAN, -- numberOfFBI-Bits is conditional based on history numberOfFBI-Bits NumberOfFBI-Bits puncturingLimit PuncturingLimit }, tdd SEQUENCE { ul-TimingAdvance UL-TimingAdvanceControl ul-CCTrCHList UL-CCTrCHList ul-CCTrCHListToRemove UL-CCTrCHListToRemove } } } UL-DPCH-Info-r4 ::= SEQUENCE { ul-DPCH-PowerControlInfo UL-DPCH-PowerControlInfo-r4 modeSpecificInfo CHOICE { fdd SEQUENCE { scramblingCodeType ScramblingCodeType, scramblingCode UL-ScramblingCode, numberOfDPDCH NumberOfDPDCH spreadingFactor SpreadingFactor, tfci-Existence BOOLEAN, -- numberOfFBI-Bits is conditional based on history numberOfFBI-Bits NumberOfFBI-Bits puncturingLimit PuncturingLimit }, tdd SEQUENCE { ul-TimingAdvance UL-TimingAdvanceControl-r4 ul-CCTrCHList UL-CCTrCHList-r4 ul-CCTrCHListToRemove UL-CCTrCHListToRemove } } } UL-DPCH-Info-r5 ::= ul-DPCH-PowerControlInfo modeSpecificInfo fdd scramblingCodeType scramblingCode numberOfDPDCH SEQUENCE { UL-DPCH-PowerControlInfo-r5 CHOICE { SEQUENCE { ScramblingCodeType, UL-ScramblingCode, NumberOfDPDCH
OPTIONAL,
DEFAULT 1,
OPTIONAL,
OPTIONAL,
DEFAULT 1,
OPTIONAL,
OPTIONAL,
DEFAULT 1,
3GPP
Release 6
918
spreadingFactor SpreadingFactor, tfci-Existence BOOLEAN, -- numberOfFBI-Bits is conditional based on history numberOfFBI-Bits NumberOfFBI-Bits puncturingLimit PuncturingLimit
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL,
}, tdd ul-TimingAdvance ul-CCTrCHList ul-CCTrCHListToRemove } } }
SEQUENCE { UL-TimingAdvanceControl-r4 UL-CCTrCHList-r4 UL-CCTrCHListToRemove
UL-DPCH-Info-r6 ::= SEQUENCE { ul-DPCH-PowerControlInfo UL-DPCH-PowerControlInfo-r6 modeSpecificInfo CHOICE { fdd SEQUENCE { scramblingCodeType ScramblingCodeType, scramblingCode UL-ScramblingCode, dpdchPresence CHOICE { present SEQUENCE { numberOfDPDCH NumberOfDPDCH spreadingFactor SpreadingFactor, tfci-Existence BOOLEAN, -- numberOfFBI-Bits is conditional based on history numberOfFBI-Bits NumberOfFBI-Bits puncturingLimit PuncturingLimit }, notPresent SEQUENCE { tfci-Existence BOOLEAN, -- numberOfFBI-Bits is conditional based on history numberOfFBI-Bits NumberOfFBI-Bits } } }, tdd SEQUENCE { ul-TimingAdvance UL-TimingAdvanceControl-r4 ul-CCTrCHList UL-CCTrCHList-r4 ul-CCTrCHListToRemove UL-CCTrCHListToRemove } } }
OPTIONAL,
DEFAULT 1,
OPTIONAL,
OPTIONAL
UL-DPCH-InfoPostFDD ::= SEQUENCE { ul-DPCH-PowerControlInfo UL-DPCH-PowerControlInfoPostFDD, scramblingCodeType ScramblingCodeType, reducedScramblingCodeNumber ReducedScramblingCodeNumber, spreadingFactor SpreadingFactor } UL-DPCH-InfoPostTDD ::= ul-DPCH-PowerControlInfo ul-TimingAdvance ul-CCTrCH-TimeslotsCodes } UL-DPCH-InfoPostTDD-LCR-r4 ::= ul-DPCH-PowerControlInfo ul-TimingAdvance ul-CCTrCH-TimeslotsCodes } UL-DPCH-InfoPredef ::= ul-DPCH-PowerControlInfo modeSpecificInfo fdd tfci-Existence puncturingLimit }, tdd commonTimeslotInfo } } } UL-DPCH-PowerControlInfo ::= SEQUENCE { UL-DPCH-PowerControlInfoPostTDD, UL-TimingAdvanceControl UplinkTimeslotsCodes
OPTIONAL,
SEQUENCE { UL-DPCH-PowerControlInfoPostTDD-LCR-r4, UL-TimingAdvanceControl-LCR-r4 UplinkTimeslotsCodes-LCR-r4
OPTIONAL,
SEQUENCE { UL-DPCH-PowerControlInfoPredef, CHOICE { SEQUENCE { BOOLEAN, PuncturingLimit SEQUENCE { CommonTimeslotInfo
CHOICE {
3GPP
Release 6
fdd
919
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { dpcch-PowerOffset DPCCH-PowerOffset, pc-Preamble PC-Preamble, sRB-delay SRB-delay, -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm SEQUENCE { ul-TargetSIR UL-TargetSIR OPTIONAL, ul-OL-PC-Signalling CHOICE { broadcast-UL-OL-PC-info NULL, individuallySignalled SEQUENCE { individualTS-InterferenceList IndividualTS-InterferenceList, dpch-ConstantValue ConstantValueTdd, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } OPTIONAL
}, tdd
} } UL-DPCH-PowerControlInfo-r4 ::= CHOICE { fdd SEQUENCE { dpcch-PowerOffset DPCCH-PowerOffset, pc-Preamble PC-Preamble, sRB-delay SRB-delay, -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm }, tdd SEQUENCE { -- The IE ul-TargetSIR corresponds to PRX-DPCHdes for 1.28Mcps TDD -- Actual value PRX-DPCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR OPTIONAL, ul-OL-PC-Signalling CHOICE { broadcast-UL-OL-PC-info NULL, individuallySignalled SEQUENCE { tddOption CHOICE { tdd384 SEQUENCE { individualTS-InterferenceList IndividualTS-InterferenceList, dpch-ConstantValue ConstantValue }, tdd128 SEQUENCE { tpc-StepSize TPC-StepSizeTDD } }, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } } UL-DPCH-PowerControlInfo-r5 ::= CHOICE { fdd SEQUENCE { dpcch-PowerOffset DPCCH-PowerOffset, pc-Preamble PC-Preamble, sRB-delay SRB-delay, -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm, deltaACK DeltaACK OPTIONAL, deltaNACK DeltaNACK OPTIONAL, ack-NACK-repetition-factor ACK-NACK-repetitionFactor OPTIONAL }, tdd SEQUENCE { -- The IE ul-TargetSIR corresponds to PRX-DPCHdes for 1.28Mcps TDD -- Actual value PRX-DPCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR OPTIONAL, ul-OL-PC-Signalling CHOICE { broadcast-UL-OL-PC-info NULL, individuallySignalled SEQUENCE { tddOption CHOICE { tdd384 SEQUENCE { individualTS-InterferenceList IndividualTS-InterferenceList, dpch-ConstantValue ConstantValue }, tdd128 SEQUENCE { tpc-StepSize TPC-StepSizeTDD } }, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power
3GPP
Release 6
} } } }
920
3GPP TS 25.331 V6.23.0 (2009-09)
UL-DPCH-PowerControlInfo-r6 ::= CHOICE { fdd SEQUENCE { dpcch-PowerOffset DPCCH-PowerOffset, pc-Preamble PC-Preamble, sRB-delay SRB-delay, -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm, deltaACK DeltaACK OPTIONAL, deltaNACK DeltaNACK OPTIONAL, ack-NACK-repetition-factor ACK-NACK-repetitionFactor OPTIONAL, harq-Preamble-Mode HARQ-Preamble-Mode }, tdd SEQUENCE { -- The IE ul-TargetSIR corresponds to PRX-DPCHdes for 1.28Mcps TDD -- Actual value PRX-DPCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR OPTIONAL, ul-OL-PC-Signalling CHOICE { broadcast-UL-OL-PC-info NULL, individuallySignalled SEQUENCE { tddOption CHOICE { tdd384 SEQUENCE { individualTS-InterferenceList IndividualTS-InterferenceList, dpch-ConstantValue ConstantValue }, tdd128 SEQUENCE { beaconPLEst BEACON-PL-Est OPTIONAL, tpc-StepSize TPC-StepSizeTDD } }, primaryCCPCH-TX-Power PrimaryCCPCH-TX-Power } } } } UL-DPCH-PowerControlInfoPostFDD ::= SEQUENCE { -- DPCCH-PowerOffset2 has a smaller range to save bits dpcch-PowerOffset DPCCH-PowerOffset2, pc-Preamble PC-Preamble, sRB-delay SRB-delay } UL-DPCH-PowerControlInfoPostTDD ::= SEQUENCE { ul-TargetSIR UL-TargetSIR, ul-TimeslotInterference TDD-UL-Interference } UL-DPCH-PowerControlInfoPostTDD-LCR-r4 ::= SEQUENCE { -- The IE ul-TargetSIR corresponds to PRX-DPCHdes for 1.28Mcps TDD -- Actual value PRX-DPCHdes = (value of IE "ul-TargetSIR" 120) ul-TargetSIR UL-TargetSIR } UL-DPCH-PowerControlInfoPredef ::= CHOICE { fdd SEQUENCE { -- TABULAR: TPC step size nested inside PowerControlAlgorithm powerControlAlgorithm PowerControlAlgorithm }, tdd SEQUENCE { -- dpch-ConstantValue shall be ignored if in 1.28Mcps TDD mode. dpch-ConstantValue ConstantValueTdd } } UL-EDCH-Information-r6 ::= mac-es-e-resetIndicator e-DPCCH-Info e-DPDCH-Info schedulingTransmConfiguration } UL-Interference ::= SEQUENCE { ENUMERATED { true } E-DPCCH-Info E-DPDCH-Info E-DPDCH-SchedulingTransmConfiguration
INTEGER (-110..-70)
3GPP
Release 6
UL-ScramblingCode ::=
921
INTEGER (0..16777215)
3GPP TS 25.331 V6.23.0 (2009-09)
UL-SynchronisationParameters-r4 ::= SEQUENCE { stepSize INTEGER (1..8), frequency INTEGER (1..8) } -- Actual value UL-TargetSIR = (IE value * 0.5) - 11 UL-TargetSIR ::= INTEGER (0..62) UL-TimingAdvance ::= UL-TimingAdvanceControl ::= disabled enabled ul-TimingAdvance activationTime } } INTEGER (0..63) CHOICE { NULL, SEQUENCE { UL-TimingAdvance ActivationTime
OPTIONAL, OPTIONAL
UL-TimingAdvanceControl-r4 ::= CHOICE { disabled NULL, enabled SEQUENCE { tddOption CHOICE { tdd384 SEQUENCE { ul-TimingAdvance UL-TimingAdvance activationTime ActivationTime }, tdd128 SEQUENCE { ul-SynchronisationParameters UL-SynchronisationParameters-r4 synchronisationParameters SynchronisationParameters-r4 } } } }
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
UL-TimingAdvanceControl-LCR-r4 ::= CHOICE { disabled NULL, enabled SEQUENCE { ul-SynchronisationParameters UL-SynchronisationParameters-r4 OPTIONAL, synchronisationParameters SynchronisationParameters-r4 OPTIONAL } } UL-TS-ChannelisationCode ::= ENUMERATED { cc1-1, cc2-1, cc2-2, cc4-1, cc4-2, cc4-3, cc4-4, cc8-1, cc8-2, cc8-3, cc8-4, cc8-5, cc8-6, cc8-7, cc8-8, cc16-1, cc16-2, cc16-3, cc16-4, cc16-5, cc16-6, cc16-7, cc16-8, cc16-9, cc16-10, cc16-11, cc16-12, cc16-13, cc16-14, cc16-15, cc16-16 } SEQUENCE (SIZE (1..2)) OF UL-TS-ChannelisationCode
UL-TS-ChannelisationCodeList ::=
UplinkAdditionalTimeslots ::= SEQUENCE { parameters CHOICE { sameAsLast SEQUENCE { timeslotNumber TimeslotNumber }, newParameters SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo, ul-TS-ChannelisationCodeList UL-TS-ChannelisationCodeList } } } UplinkAdditionalTimeslots-LCR-r4 ::= SEQUENCE { parameters CHOICE { sameAsLast SEQUENCE { timeslotNumber TimeslotNumber }, newParameters SEQUENCE { individualTimeslotInfo IndividualTimeslotInfo-LCR-r4, ul-TS-ChannelisationCodeList UL-TS-ChannelisationCodeList
3GPP
Release 6
} } }
922
3GPP TS 25.331 V6.23.0 (2009-09)
UplinkTimeslotsCodes ::= SEQUENCE { dynamicSFusage BOOLEAN, firstIndividualTimeslotInfo IndividualTimeslotInfo, ul-TS-ChannelisationCodeList UL-TS-ChannelisationCodeList, moreTimeslots CHOICE { noMore NULL, additionalTimeslots CHOICE { consecutive SEQUENCE { numAdditionalTimeslots INTEGER (1..maxTS-1) }, timeslotList SEQUENCE (SIZE (1..maxTS-1)) OF UplinkAdditionalTimeslots } } } UplinkTimeslotsCodes-LCR-r4 ::= SEQUENCE { dynamicSFusage BOOLEAN, firstIndividualTimeslotInfo IndividualTimeslotInfo-LCR-r4, ul-TS-ChannelisationCodeList UL-TS-ChannelisationCodeList, moreTimeslots CHOICE { noMore NULL, additionalTimeslots CHOICE { consecutive SEQUENCE { numAdditionalTimeslots INTEGER (1..maxTS-LCR-1) }, timeslotList SEQUENCE (SIZE (1..maxTS-LCR-1)) OF UplinkAdditionalTimeslots-LCR-r4 } } } Wi-LCR ::= -- *************************************************** --MEASUREMENT INFORMATION ELEMENTS (10.3.7) --- *************************************************** AcquisitionSatInfo ::= SEQUENCE { satID SatID, -- Actual value dopplerOthOrder = IE value * 2.5 doppler0thOrder INTEGER (-2048..2047), extraDopplerInfo ExtraDopplerInfo codePhase INTEGER (0..1022), integerCodePhase INTEGER (0..19), gps-BitNumber INTEGER (0..3), codePhaseSearchWindow CodePhaseSearchWindow, azimuthAndElevation AzimuthAndElevation } AcquisitionSatInfoList ::= SEQUENCE (SIZE (1..maxSat)) OF AcquisitionSatInfo INTEGER(1..4)
OPTIONAL,
OPTIONAL
AdditionalMeasurementID-List ::=
SEQUENCE (SIZE (1..maxAdditionalMeas)) OF MeasurementIdentity SEQUENCE { INTEGER (0..3), SatID, BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE BIT STRING (SIZE
AlmanacSatInfo ::= dataID satID e t-oa deltaI omegaDot satHealth a-Sqrt omega0 m0 omega af0 af1 }
(16)), (8)), (16)), (16)), (8)), (24)), (24)), (24)), (24)), (11)), (11))
3GPP
Release 6
923
3GPP TS 25.331 V6.23.0 (2009-09)
AlmanacSatInfoList ::=
SEQUENCE (SIZE (1..maxSat)) OF AlmanacSatInfo ENUMERATED { pla0, pla4, pla8, pla16, pla32, pla64, pla128, pla256, pla512, pla1024, pla2k, pla4k, pla8k, pla16k, pla32k, pla64k, pla128k, pla256k, pla512k, pla1024k, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }
AverageRLC-BufferPayload ::=
AzimuthAndElevation ::= SEQUENCE { -- Actual value azimuth = IE value * 11.25 azimuth INTEGER (0..31), -- Actual value elevation = IE value * 11.25 elevation INTEGER (0..7) } BadSatList ::= SEQUENCE (SIZE (1..maxSat)) OF INTEGER (0..63) ENUMERATED { dcs1800BandUsed, pcs1900BandUsed } INTEGER (0..1023) SEQUENCE { TransportChannelIdentity, DL-TransportChannelBLER
Frequency-Band ::=
BCCH-ARFCN ::= BLER-MeasurementResults ::= transportChannelIdentity dl-TransportChannelBLER } BLER-MeasurementResultsList ::=
OPTIONAL
SEQUENCE (SIZE (1..maxTrCH)) OF BLER-MeasurementResults SEQUENCE (SIZE (1..maxTrCH)) OF TransportChannelIdentity ENUMERATED { required, notRequired }
BLER-TransChIdList ::=
BSIC-VerificationRequired ::=
BSICReported ::= CHOICE { -- Value maxCellMeas is not allowed for verifiedBSIC verifiedBSIC INTEGER (0..maxCellMeas), nonVerifiedBSIC BCCH-ARFCN } BurstModeParameters ::= burstStart burstLength burstFreq } CellDCH-ReportCriteria ::= intraFreqReportingCriteria periodicalReportingCriteria } CellDCH-ReportCriteria-LCR-r4 ::= intraFreqReportingCriteria periodicalReportingCriteria } SEQUENCE { INTEGER (0..15), INTEGER (10..25), INTEGER (1..16)
CHOICE { IntraFreqReportingCriteria, PeriodicalReportingCriteria
CHOICE { IntraFreqReportingCriteria-LCR-r4, PeriodicalReportingCriteria
-- Actual value CellIndividualOffset = IE value * 0.5 CellIndividualOffset ::= INTEGER (-20..20)
CellInfo ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator },
SEQUENCE { CellIndividualOffset ReferenceTimeDifferenceToCell CHOICE { SEQUENCE { PrimaryCPICH-Info PrimaryCPICH-TX-Power BOOLEAN, BOOLEAN
OPTIONAL, OPTIONAL,
3GPP
Release 6
tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } } } CellInfo-r4 ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator }, tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } } } CellInfoSI-RSCP ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator }, tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } }, cellSelectionReselectionInfo } CellInfoSI-RSCP-LCR-r4 ::= cellIndividualOffset referenceTimeDifferenceToCell primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator cellSelectionReselectionInfo } CellInfoSI-ECN0 ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator }, tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } }, cellSelectionReselectionInfo }
924
SEQUENCE { PrimaryCCPCH-Info, PrimaryCCPCH-TX-Power TimeslotInfoList BOOLEAN
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL, OPTIONAL,
SEQUENCE { CellIndividualOffset ReferenceTimeDifferenceToCell CHOICE { SEQUENCE { PrimaryCPICH-Info PrimaryCPICH-TX-Power BOOLEAN, BOOLEAN SEQUENCE { PrimaryCCPCH-Info-r4, PrimaryCCPCH-TX-Power TimeslotInfoList-r4 BOOLEAN
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
SEQUENCE { CellIndividualOffset ReferenceTimeDifferenceToCell CHOICE { SEQUENCE { PrimaryCPICH-Info PrimaryCPICH-TX-Power BOOLEAN, BOOLEAN SEQUENCE { PrimaryCCPCH-Info, PrimaryCCPCH-TX-Power TimeslotInfoList BOOLEAN
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
CellSelectReselectInfoSIB-11-12-RSCP
OPTIONAL
SEQUENCE { CellIndividualOffset DEFAULT 0, ReferenceTimeDifferenceToCell OPTIONAL, PrimaryCCPCH-Info-LCR-r4, PrimaryCCPCH-TX-Power OPTIONAL, TimeslotInfoList-LCR-r4 OPTIONAL, BOOLEAN, CellSelectReselectInfoSIB-11-12-RSCP OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
CellSelectReselectInfoSIB-11-12-ECN0
OPTIONAL
3GPP
Release 6
925
3GPP TS 25.331 V6.23.0 (2009-09)
CellInfoSI-ECN0-LCR-r4 ::= cellIndividualOffset referenceTimeDifferenceToCell primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator cellSelectionReselectionInfo } CellInfoSI-HCS-RSCP ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator }, tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } }, cellSelectionReselectionInfo } CellInfoSI-HCS-RSCP-LCR-r4 ::= cellIndividualOffset referenceTimeDifferenceToCell primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator cellSelectionReselectionInfo } CellInfoSI-HCS-ECN0 ::= cellIndividualOffset referenceTimeDifferenceToCell modeSpecificInfo fdd primaryCPICH-Info primaryCPICH-TX-Power readSFN-Indicator tx-DiversityIndicator }, tdd primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator } }, cellSelectionReselectionInfo } CellInfoSI-HCS-ECN0-LCR-r4 ::= cellIndividualOffset referenceTimeDifferenceToCell primaryCCPCH-Info primaryCCPCH-TX-Power timeslotInfoList readSFN-Indicator cellSelectionReselectionInfo }
SEQUENCE { CellIndividualOffset DEFAULT 0, ReferenceTimeDifferenceToCell OPTIONAL, PrimaryCCPCH-Info-LCR-r4, PrimaryCCPCH-TX-Power OPTIONAL, TimeslotInfoList-LCR-r4 OPTIONAL, BOOLEAN, CellSelectReselectInfoSIB-11-12-ECN0 OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
CellSelectReselectInfoSIB-11-12-HCS-RSCP
OPTIONAL
SEQUENCE { CellIndividualOffset DEFAULT 0, ReferenceTimeDifferenceToCell OPTIONAL, PrimaryCCPCH-Info-LCR-r4, PrimaryCCPCH-TX-Power OPTIONAL, TimeslotInfoList-LCR-r4 OPTIONAL, BOOLEAN, CellSelectReselectInfoSIB-11-12-HCS-RSCP OPTIONAL
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
CellSelectReselectInfoSIB-11-12-HCS-ECN0
OPTIONAL
SEQUENCE { CellIndividualOffset DEFAULT 0, ReferenceTimeDifferenceToCell OPTIONAL, PrimaryCCPCH-Info-LCR-r4, PrimaryCCPCH-TX-Power OPTIONAL, TimeslotInfoList-LCR-r4 OPTIONAL, BOOLEAN, CellSelectReselectInfoSIB-11-12-HCS-ECN0 OPTIONAL
CellMeasuredResults ::= SEQUENCE { cellIdentity CellIdentity OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy SFN-SFN-ObsTimeDifference OPTIONAL, cellSynchronisationInfo CellSynchronisationInfo OPTIONAL, modeSpecificInfo CHOICE {
3GPP
Release 6
fdd primaryCPICH-Info cpich-Ec-N0 cpich-RSCP pathloss }, tdd cellParametersID proposedTGSN primaryCCPCH-RSCP pathloss timeslotISCP-List } } } CellMeasurementEventResults ::= fdd tdd } CellMeasurementEventResults-LCR-r4 ::=
926
SEQUENCE { PrimaryCPICH-Info, CPICH-Ec-N0 CPICH-RSCP Pathloss SEQUENCE { CellParametersID, TGSN PrimaryCCPCH-RSCP Pathloss TimeslotISCP-List
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE { SEQUENCE (SIZE (1..maxCellMeas)) OF PrimaryCPICH-Info, SEQUENCE (SIZE (1..maxCellMeas)) OF PrimaryCCPCH-Info
SEQUENCE (SIZE (1..maxCellMeas)) OF PrimaryCCPCH-Info-LCR-r4
CellReportingQuantities ::= SEQUENCE { -- dummy is not used in this version of the specification -- and if received it should be ignored. dummy SFN-SFN-OTD-Type, cellIdentity-reportingIndicator BOOLEAN, cellSynchronisationInfoReportingIndicator BOOLEAN, modeSpecificInfo CHOICE { fdd SEQUENCE { cpich-Ec-N0-reportingIndicator BOOLEAN, cpich-RSCP-reportingIndicator BOOLEAN, pathloss-reportingIndicator BOOLEAN }, tdd SEQUENCE { timeslotISCP-reportingIndicator BOOLEAN, proposedTGSN-ReportingRequired BOOLEAN, primaryCCPCH-RSCP-reportingIndicator BOOLEAN, pathloss-reportingIndicator BOOLEAN } } } CellSelectReselectInfoSIB-11-12 ::= SEQUENCE { q-Offset1S-N Q-OffsetS-N DEFAULT 0, q-Offset2S-N Q-OffsetS-N OPTIONAL, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, hcs-NeighbouringCellInformation-RSCP HCS-NeighbouringCellInformation-RSCP OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { q-QualMin Q-QualMin OPTIONAL, q-RxlevMin Q-RxlevMin OPTIONAL }, tdd SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL }, gsm SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL } } } CellSelectReselectInfoSIB-11-12-RSCP ::= SEQUENCE { q-OffsetS-N Q-OffsetS-N maxAllowedUL-TX-Power MaxAllowedUL-TX-Power modeSpecificInfo CHOICE { fdd SEQUENCE { q-QualMin Q-QualMin q-RxlevMin Q-RxlevMin }, tdd SEQUENCE { q-RxlevMin Q-RxlevMin },
OPTIONAL, OPTIONAL
OPTIONAL
3GPP
Release 6
gsm q-RxlevMin } } }
927
SEQUENCE { Q-RxlevMin
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
CellSelectReselectInfoSIB-11-12-ECN0 ::= SEQUENCE { q-Offset1S-N Q-OffsetS-N q-Offset2S-N Q-OffsetS-N maxAllowedUL-TX-Power MaxAllowedUL-TX-Power modeSpecificInfo CHOICE { fdd SEQUENCE { q-QualMin Q-QualMin q-RxlevMin Q-RxlevMin }, tdd SEQUENCE { q-RxlevMin Q-RxlevMin }, gsm SEQUENCE { q-RxlevMin Q-RxlevMin } } }
DEFAULT 0, DEFAULT 0, OPTIONAL,
OPTIONAL, OPTIONAL
OPTIONAL
OPTIONAL
CellSelectReselectInfoSIB-11-12-HCS-RSCP ::= SEQUENCE { q-OffsetS-N Q-OffsetS-N DEFAULT 0, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, hcs-NeighbouringCellInformation-RSCP HCS-NeighbouringCellInformation-RSCP OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { q-QualMin Q-QualMin OPTIONAL, q-RxlevMin Q-RxlevMin OPTIONAL }, tdd SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL }, gsm SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL } } } CellSelectReselectInfoSIB-11-12-HCS-ECN0 ::= SEQUENCE { q-Offset1S-N Q-OffsetS-N DEFAULT 0, q-Offset2S-N Q-OffsetS-N DEFAULT 0, maxAllowedUL-TX-Power MaxAllowedUL-TX-Power OPTIONAL, hcs-NeighbouringCellInformation-ECN0 HCS-NeighbouringCellInformation-ECN0 OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { q-QualMin Q-QualMin OPTIONAL, q-RxlevMin Q-RxlevMin OPTIONAL }, tdd SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL }, gsm SEQUENCE { q-RxlevMin Q-RxlevMin OPTIONAL } } } CellSelectReselectInfo-v590ext ::= SEQUENCE { deltaQrxlevmin DeltaQrxlevmin deltaQhcs DeltaRSCP } CellSelectReselectInfoPCHFACH-v5b0ext ::= SEQUENCE { q-Hyst-l-S-PCH Q-Hyst-S-Fine q-Hyst-l-S-FACH Q-Hyst-S-Fine q-Hyst-2-S-PCH Q-Hyst-S-Fine q-Hyst-2-S-FACH Q-Hyst-S-Fine t-Reselection-S-PCH T-Reselection-S t-Reselection-S-FACH T-Reselection-S-Fine } CellSelectReselectInfoTreselectionScaling-v5c0ext ::= SEQUENCE {
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
3GPP
Release 6
928
3GPP TS 25.331 V6.23.0 (2009-09)
-- For speed detection, the same HCS parameters are utilised non-HCS-t-CR-Max T-CRMax speedDependentScalingFactor SpeedDependentScalingFactor interFrequencyTreselectionScalingFactor TreselectionScalingFactor interRATTreselectionScalingFactor TreselectionScalingFactor } CellsForInterFreqMeasList ::= CellsForInterRATMeasList ::= CellsForIntraFreqMeasList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF InterFreqCellID SEQUENCE (SIZE (1..maxCellMeas)) OF InterRATCellID SEQUENCE (SIZE (1..maxCellMeas)) OF IntraFreqCellID
CellSynchronisationInfo ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { countC-SFN-Frame-difference CountC-SFN-Frame-difference tm INTEGER(0..38399) }, tdd SEQUENCE { countC-SFN-Frame-difference CountC-SFN-Frame-difference } } } CellToReport ::= bsicReported } CellToReportList ::= SEQUENCE { BSICReported
OPTIONAL,
OPTIONAL
SEQUENCE (SIZE (1..maxCellMeas)) OF CellToReport ENUMERATED { w1023, w1, w2, w3, w4, w6, w8, w12, w16, w24, w32, w48, w64, w96, w128, w192 }
CodePhaseSearchWindow ::=
CountC-SFN-Frame-difference ::= SEQUENCE { -- Actual value countC-SFN-High = IE value * 256 countC-SFN-High INTEGER(0..15), off INTEGER(0..255) } -- SPARE: CPICH-Ec-No, Max = 49 -- Values above Max are spare CPICH-Ec-N0 ::= -- SPARE: CPICH- RSCP, Max = 91 -- Values above Max are spare CPICH-RSCP ::=
INTEGER (0..63)
INTEGER (0..127)
DeltaPRC ::=
INTEGER (-127..127)
--Actual value DeltaQrxlevmin = IE value * 2 DeltaQrxlevmin ::= INTEGER (-2..-1) DeltaRSCP ::= INTEGER (-5..-1) DeltaRSCPPerCell ::= SEQUENCE { deltaRSCP }
DeltaRSCP
OPTIONAL
-- Actual value DeltaRRC = IE value * 0.032 DeltaRRC ::= INTEGER (-7..7) DGPS-CorrectionSatInfo ::= SEQUENCE { satID SatID, iode IODE, udre UDRE, prc PRC, rrc RRC, -- dummy1 and dummy2 are not used in this version of the specification and should be ignored. dummy1 DeltaPRC, dummy2 DeltaRRC, -- dummy3 and dummy4 are not used in this version of the specification. They should not -- be sent and if received they should be ignored.
3GPP
Release 6
dummy3 dummy4 } DGPS-CorrectionSatInfoList ::= DeltaPRC DeltaRRC
929
OPTIONAL, OPTIONAL
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxSat)) OF DGPS-CorrectionSatInfo ENUMERATED { udre-1-0, udre-0-75, udre-0-5, udre-0-3, udre-0-2, udre-0-1, noData, invalidData } INTEGER (0..63) ENUMERATED { hz12-5, hz25, hz50, hz100, hz200, spare3, spare2, spare1 }
DiffCorrectionStatus ::=
DL-TransportChannelBLER ::= DopplerUncertainty ::=
EllipsoidPoint ::= latitudeSign latitude longitude }
SEQUENCE { ENUMERATED { north, south }, INTEGER (0..8388607), INTEGER (-8388608..8388607)
EllipsoidPointAltitude ::= SEQUENCE { latitudeSign ENUMERATED { north, south }, latitude INTEGER (0..8388607), longitude INTEGER (-8388608..8388607), altitudeDirection ENUMERATED {height, depth}, altitude INTEGER (0..32767) }
EllipsoidPointAltitudeEllipsoide ::= SEQUENCE { latitudeSign ENUMERATED { north, south }, latitude INTEGER (0..8388607), longitude INTEGER (-8388608..8388607), altitudeDirection ENUMERATED {height, depth}, altitude INTEGER (0..32767), uncertaintySemiMajor INTEGER (0..127), uncertaintySemiMinor INTEGER (0..127), -- Actual value orientationMajorAxis = IE value * 2 orientationMajorAxis INTEGER (0..89), uncertaintyAltitude INTEGER (0..127), confidence INTEGER (0..100) }
EllipsoidPointUncertCircle ::= SEQUENCE { latitudeSign ENUMERATED { north, south }, latitude INTEGER (0..8388607), longitude INTEGER (-8388608..8388607), uncertaintyCode INTEGER (0..127) }
EllipsoidPointUncertEllipse ::= SEQUENCE { latitudeSign ENUMERATED { north, south }, latitude INTEGER (0..8388607), longitude INTEGER (-8388608..8388607), uncertaintySemiMajor INTEGER (0..127), uncertaintySemiMinor INTEGER (0..127), -- Actual value orientationMajorAxis = IE value * 2 orientationMajorAxis INTEGER (0..89), confidence INTEGER (0..100) }
EnvironmentCharacterisation ::=
ENUMERATED { possibleHeavyMultipathNLOS, lightMultipathLOS, notDefined, spare } SEQUENCE { TriggeringCondition2, ReportingRange, ForbiddenAffectCellList
Event1a ::= triggeringCondition reportingRange forbiddenAffectCellList
OPTIONAL,
3GPP
Release 6
w reportDeactivationThreshold reportingAmount reportingInterval } Event1a-r4 ::= triggeringCondition reportingRange forbiddenAffectCellList w reportDeactivationThreshold reportingAmount reportingInterval } Event1a-LCR-r4 ::= triggeringCondition reportingRange forbiddenAffectCellList w reportDeactivationThreshold reportingAmount reportingInterval } Event1b ::= triggeringCondition reportingRange forbiddenAffectCellList w } Event1b-r4 ::= triggeringCondition reportingRange forbiddenAffectCellList w } Event1b-LCR-r4 ::= triggeringCondition reportingRange forbiddenAffectCellList w } Event1c ::= replacementActivationThreshold reportingAmount reportingInterval } Event1d ::= triggeringCondition useCIO } Event1e ::= triggeringCondition thresholdUsedFrequency } Event1e-r6 ::= triggeringCondition thresholdUsedFrequency } Event1f ::= triggeringCondition thresholdUsedFrequency } Event1f-r6 ::= triggeringCondition thresholdUsedFrequency }
930
W, ReportDeactivationThreshold, ReportingAmount, ReportingInterval
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { TriggeringCondition2, ReportingRange, ForbiddenAffectCellList-r4 W, ReportDeactivationThreshold, ReportingAmount, ReportingInterval
OPTIONAL,
SEQUENCE { TriggeringCondition2, ReportingRange, ForbiddenAffectCellList-LCR-r4 W, ReportDeactivationThreshold, ReportingAmount, ReportingInterval
OPTIONAL,
SEQUENCE { TriggeringCondition1, ReportingRange, ForbiddenAffectCellList W
OPTIONAL,
SEQUENCE { TriggeringCondition1, ReportingRange, ForbiddenAffectCellList-r4 W
OPTIONAL,
SEQUENCE { TriggeringCondition1, ReportingRange, ForbiddenAffectCellList-LCR-r4 W
OPTIONAL,
SEQUENCE { ReplacementActivationThreshold, ReportingAmount, ReportingInterval
SEQUENCE { TriggeringCondition2 BOOLEAN
OPTIONAL, OPTIONAL
SEQUENCE { TriggeringCondition2, ThresholdUsedFrequency
SEQUENCE { TriggeringCondition2, ThresholdUsedFrequency-r6
SEQUENCE { TriggeringCondition1, ThresholdUsedFrequency
SEQUENCE { TriggeringCondition1, ThresholdUsedFrequency-r6
3GPP
Release 6
931
3GPP TS 25.331 V6.23.0 (2009-09)
Event1j-r6 ::= SEQUENCE { replacementActivationThreshold ReplacementActivationThreshold, reportingAmount ReportingAmount, reportingInterval ReportingInterval } Event2a ::= SEQUENCE { -- dummy is not used in this version of the specification and should be ignored dummy Threshold, usedFreqW W, hysteresis HysteresisInterFreq, timeToTrigger TimeToTrigger, reportingCellStatus ReportingCellStatus OPTIONAL, nonUsedFreqParameterList NonUsedFreqParameterList OPTIONAL } Event2a-r6 ::= usedFreqW hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2b ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2b-r6 ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2c ::= hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2c-r6 ::= hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2d ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus } Event2d-r6 ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus } Event2e ::= hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } SEQUENCE { W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqWList-r6
OPTIONAL, OPTIONAL
SEQUENCE { Threshold, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList
OPTIONAL, OPTIONAL
SEQUENCE { Threshold-r6, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList-r6
OPTIONAL, OPTIONAL
SEQUENCE { HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList
OPTIONAL, OPTIONAL
SEQUENCE { HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList-r6
OPTIONAL, OPTIONAL
SEQUENCE { Threshold, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Threshold-r6, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList
OPTIONAL, OPTIONAL
3GPP
Release 6
932
3GPP TS 25.331 V6.23.0 (2009-09)
Event2e-r6 ::= hysteresis timeToTrigger reportingCellStatus nonUsedFreqParameterList } Event2f ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus } Event2f-r6 ::= usedFreqThreshold usedFreqW hysteresis timeToTrigger reportingCellStatus } Event3a ::= thresholdOwnSystem w thresholdOtherSystem hysteresis timeToTrigger reportingCellStatus } Event3b ::= thresholdOtherSystem hysteresis timeToTrigger reportingCellStatus } Event3c ::= thresholdOtherSystem hysteresis timeToTrigger reportingCellStatus } Event3d ::= hysteresis timeToTrigger reportingCellStatus } EventIDInterFreq ::=
SEQUENCE { HysteresisInterFreq, TimeToTrigger, ReportingCellStatus NonUsedFreqParameterList-r6
OPTIONAL, OPTIONAL
SEQUENCE { Threshold, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Threshold-r6, W, HysteresisInterFreq, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Threshold, W, Threshold, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Threshold, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Threshold, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
ENUMERATED { e2a, e2b, e2c, e2d, e2e, e2f, spare2, spare1 } ENUMERATED { e3a, e3b, e3c, e3d } ENUMERATED { e1a, e1b, e1c, e1d, e1e, e1f, e1g, e1h, e1i, e1j, spare6, spare5, spare4, spare3, spare2, spare1 }
EventIDInterRAT ::=
EventIDIntraFreq ::=
EventResults ::= CHOICE { intraFreqEventResults IntraFreqEventResults, interFreqEventResults InterFreqEventResults, interRATEventResults InterRATEventResults, trafficVolumeEventResults TrafficVolumeEventResults, qualityEventResults QualityEventResults, ue-InternalEventResults UE-InternalEventResults, ue-positioning-MeasurementEventResults UE-Positioning-MeasurementEventResults, spare NULL } ExtraDopplerInfo ::= SEQUENCE {
3GPP
Release 6
933
3GPP TS 25.331 V6.23.0 (2009-09)
-- Actual value doppler1stOrder = IE value * 0.023 doppler1stOrder INTEGER (-42..21), dopplerUncertainty DopplerUncertainty } FACH-MeasurementOccasionInfo ::= SEQUENCE { fACH-meas-occasion-coeff INTEGER (1..12) OPTIONAL, inter-freq-FDD-meas-ind BOOLEAN, -- inter-freq-TDD-meas-ind is for 3.84Mcps TDD. For 1.28Mcps TDD, the IE in -- FACH-MeasurementOccasionInfo-LCR-r4-ext is used. inter-freq-TDD-meas-ind BOOLEAN, inter-RAT-meas-ind SEQUENCE (SIZE (1..maxOtherRAT)) OF RAT-Type OPTIONAL } FACH-MeasurementOccasionInfo-LCR-r4-ext ::= SEQUENCE { inter-freq-TDD128-meas-ind BOOLEAN } FilterCoefficient ::= ENUMERATED { fc0, fc1, fc2, fc3, fc4, fc5, fc6, fc7, fc8, fc9, fc11, fc13, fc15, fc17, fc19, spare1 }
-- Actual value FineSFN-SFN = IE value * 0.0625 FineSFN-SFN ::= INTEGER (0..15) ForbiddenAffectCell ::= fdd tdd } ForbiddenAffectCell-r4 ::= fdd tdd } ForbiddenAffectCell-LCR-r4 ::= tdd } ForbiddenAffectCellList ::= CHOICE { PrimaryCPICH-Info, PrimaryCCPCH-Info
CHOICE { PrimaryCPICH-Info, PrimaryCCPCH-Info-r4
SEQUENCE { PrimaryCCPCH-Info-LCR-r4
SEQUENCE (SIZE (1..maxCellMeas)) OF ForbiddenAffectCell SEQUENCE (SIZE (1..maxCellMeas)) OF ForbiddenAffectCell-r4 SEQUENCE (SIZE (1..maxCellMeas)) OF ForbiddenAffectCell-LCR-r4
ForbiddenAffectCellList-r4 ::=
ForbiddenAffectCellList-LCR-r4 ::=
FreqQualityEstimateQuantity-FDD ::= ENUMERATED { cpich-Ec-N0, cpich-RSCP } FreqQualityEstimateQuantity-TDD ::= ENUMERATED { primaryCCPCH-RSCP } GPS-MeasurementParam ::= satelliteID c-N0 doppler wholeGPS-Chips fractionalGPS-Chips multipathIndicator pseudorangeRMS-Error } GPS-MeasurementParamList ::= SEQUENCE { INTEGER (0..63), INTEGER (0..63), INTEGER (-32768..32768), INTEGER (0..1022), INTEGER (0..1023), MultipathIndicator, INTEGER (0..63)
SEQUENCE (SIZE (1..maxSat)) OF GPS-MeasurementParam BIT STRING (SIZE (6))
GSM-CarrierRSSI ::=
GSM-MeasuredResults ::= SEQUENCE { gsm-CarrierRSSI GSM-CarrierRSSI -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy INTEGER (46..173)
OPTIONAL,
OPTIONAL,
3GPP
Release 6
934
3GPP TS 25.331 V6.23.0 (2009-09)
bsicReported BSICReported, -- dummy2 is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy2 ObservedTimeDifferenceToGSM } GSM-MeasuredResultsList ::=
OPTIONAL
SEQUENCE (SIZE (1..maxReportedGSMCells)) OF GSM-MeasuredResults INTEGER (0..604799999) SEQUENCE { SatID, BIT STRING (SIZE (14)), BIT STRING (SIZE (2)), BOOLEAN, BOOLEAN
GPS-TOW-1msec ::= GPS-TOW-Assist ::= satID tlm-Message tlm-Reserved alert antiSpoof } GPS-TOW-AssistList ::=
SEQUENCE (SIZE (1..maxSat)) OF GPS-TOW-Assist
HCS-CellReselectInformation-RSCP ::= SEQUENCE { -- TABULAR: The default value for penaltyTime is "notUsed" -- Temporary offset is nested inside PenaltyTime-RSCP penaltyTime PenaltyTime-RSCP } HCS-CellReselectInformation-ECN0 ::= SEQUENCE { -- TABULAR: The default value for penaltyTime is "notUsed" -- Temporary offset is nested inside PenaltyTime-ECN0 penaltyTime PenaltyTime-ECN0 } HCS-NeighbouringCellInformation-RSCP ::= SEQUENCE { hcs-PRIO HCS-PRIO q-HCS Q-HCS hcs-CellReselectInformation HCS-CellReselectInformation-RSCP } HCS-NeighbouringCellInformation-ECN0 ::= SEQUENCE { hcs-PRIO HCS-PRIO q-HCS Q-HCS hcs-CellReselectInformation HCS-CellReselectInformation-ECN0 } HCS-PRIO ::= HCS-ServingCellInformation ::= hcs-PRIO q-HCS t-CR-Max } INTEGER (0..7) SEQUENCE { HCS-PRIO Q-HCS T-CRMax
DEFAULT 0, DEFAULT 0,
DEFAULT 0, DEFAULT 0,
DEFAULT 0, DEFAULT 0, OPTIONAL
-- Actual value Hysteresis = IE value * 0.5 Hysteresis ::= INTEGER (0..15) -- Actual value HysteresisInterFreq = IE value * 0.5 HysteresisInterFreq ::= INTEGER (0..29) InterFreqCell ::= frequencyInfo nonFreqRelatedEventResults } InterFreqCell-LCR-r4 ::= frequencyInfo nonFreqRelatedEventResults } InterFreqCellID ::= InterFreqCellInfoList ::= removedInterFreqCellList newInterFreqCellList cellsForInterFreqMeasList } SEQUENCE { FrequencyInfo, CellMeasurementEventResults
SEQUENCE { FrequencyInfo, CellMeasurementEventResults-LCR-r4
INTEGER (0..maxCellMeas-1) SEQUENCE { RemovedInterFreqCellList NewInterFreqCellList CellsForInterFreqMeasList
3GPP
Release 6
InterFreqCellInfoList-r4 ::= removedInterFreqCellList newInterFreqCellList cellsForInterFreqMeasList } InterFreqCellInfoSI-List-RSCP ::= removedInterFreqCellList newInterFreqCellList } InterFreqCellInfoSI-List-ECN0 ::= removedInterFreqCellList newInterFreqCellList } InterFreqCellInfoSI-List-HCS-RSCP ::= removedInterFreqCellList newInterFreqCellList } InterFreqCellInfoSI-List-HCS-ECN0 ::= removedInterFreqCellList newInterFreqCellList } InterFreqCellInfoSI-List-RSCP-LCR ::= removedInterFreqCellList newInterFreqCellList } InterFreqCellInfoSI-List-ECN0-LCR ::= removedInterFreqCellList newInterFreqCellList }
935
SEQUENCE { RemovedInterFreqCellList NewInterFreqCellList-r4 CellsForInterFreqMeasList
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { RemovedInterFreqCellList NewInterFreqCellSI-List-RSCP
OPTIONAL, OPTIONAL
SEQUENCE { RemovedInterFreqCellList NewInterFreqCellSI-List-ECN0
OPTIONAL, OPTIONAL
SEQUENCE { RemovedInterFreqCellList NewInterFreqCellSI-List-HCS-RSCP SEQUENCE { RemovedInterFreqCellList NewInterFreqCellSI-List-HCS-ECN0
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
SEQUENCE { RemovedInterFreqCellList OPTIONAL, NewInterFreqCellSI-List-RSCP-LCR-r4 OPTIONAL
SEQUENCE { RemovedInterFreqCellList OPTIONAL, NewInterFreqCellSI-List-ECN0-LCR-r4 OPTIONAL
InterFreqCellInfoSI-List-HCS-RSCP-LCR ::= SEQUENCE { removedInterFreqCellList RemovedInterFreqCellList OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-HCS-RSCP-LCR-r4 OPTIONAL } InterFreqCellInfoSI-List-HCS-ECN0-LCR ::= SEQUENCE { removedInterFreqCellList RemovedInterFreqCellList OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-HCS-ECN0-LCR-r4 OPTIONAL } InterFreqCellList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCell SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCell-LCR-r4
InterFreqCellList-LCR-r4-ext ::=
InterFreqCellMeasuredResultsList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF CellMeasuredResults InterFreqEvent ::= event2a event2b event2c event2d event2e event2f } InterFreqEvent-r6 ::= event2a event2b event2c event2d event2e event2f } InterFreqEventList ::= CHOICE { Event2a, Event2b, Event2c, Event2d, Event2e, Event2f
CHOICE { Event2a-r6, Event2b-r6, Event2c-r6, Event2d-r6, Event2e-r6, Event2f-r6
SEQUENCE (SIZE (1..maxMeasEvent)) OF InterFreqEvent SEQUENCE (SIZE (1..maxMeasEvent)) OF InterFreqEvent-r6
InterFreqEventList-r6 ::=
--Following IE shall be used regardless of CPICH RSCP(FDD) or Primary CCPCH RSCP(TDD)
3GPP
Release 6
936
3GPP TS 25.331 V6.23.0 (2009-09)
--The order of the list corresponds to the order of the cells in InterFrequencyMeasuredResultsList --The IE is only used for measured results and not for additional measured results. InterFrequencyMeasuredResultsList-v590ext ::= SEQUENCE (SIZE (1..maxCellMeas)) OF DeltaRSCPPerCell Inter-FreqEventCriteria-v590ext ::= SEQUENCE { threholdUsedFrequency-delta DeltaRSCP, threholdNonUsedFrequency-deltaList ThreholdNonUsedFrequency-deltaList }
OPTIONAL
--The order of the list corresponds to the order of the events in Inter-FreqEventList Inter-FreqEventCriteriaList-v590ext ::= SEQUENCE (SIZE (1..maxMeasEvent)) OF Inter-FreqEventCriteria-v590ext --The order of the list corresponds to the order of relevant events in Intra-FreqEventCriteriaList --i.e. the first element of the list corresponds to the first occurance of event 1e, 1f, 1h, 1i, --the second element of the list corresponds to the second occurance of event 1e, 1f, 1h, 1i Intra-FreqEventCriteriaList-v590ext ::= SEQUENCE (SIZE (1..maxMeasEvent)) OF DeltaRSCP --Following IE shall be used regardless of CPICH RSCP(FDD) or Primary CCPCH RSCP(TDD) --The order of the list corresponds to the order of the cells in IntraFrequencyMeasuredResultsList --The IE is only used for measured results and not for additional measured results. IntraFrequencyMeasuredResultsList-v590ext ::= SEQUENCE (SIZE (1..maxCellMeas)) OF DeltaRSCPPerCell IntraFreqReportingCriteria-1b-r5 ::= SEQUENCE { periodicReportingInfo-1b PeriodicReportingInfo-1b } PeriodicReportingInfo-1b ::= SEQUENCE { reportingAmount ReportingAmount, reportingInterval ReportingInterval } InterFreqEventResults ::= eventID interFreqCellList } SEQUENCE { EventIDInterFreq, InterFreqCellList
OPTIONAL
InterFreqEventResults-LCR-r4-ext ::= eventID interFreqCellList }
SEQUENCE { EventIDInterFreq, InterFreqCellList-LCR-r4-ext
OPTIONAL
InterFreqMeasQuantity ::= SEQUENCE { reportingCriteria CHOICE { intraFreqReportingCriteria SEQUENCE { intraFreqMeasQuantity IntraFreqMeasQuantity }, interFreqReportingCriteria SEQUENCE { filterCoefficient FilterCoefficient DEFAULT fc0, modeSpecificInfo CHOICE { fdd SEQUENCE { freqQualityEstimateQuantity-FDD FreqQualityEstimateQuantity-FDD }, tdd SEQUENCE { freqQualityEstimateQuantity-TDD FreqQualityEstimateQuantity-TDD } } } } } InterFreqMeasuredResults ::= SEQUENCE { frequencyInfo FrequencyInfo utra-CarrierRSSI UTRA-CarrierRSSI interFreqCellMeasuredResultsList InterFreqCellMeasuredResultsList } InterFreqMeasuredResultsList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqMeasuredResults
InterFreqMeasurementSysInfo-RSCP ::= interFreqCellInfoSI-List }
SEQUENCE { InterFreqCellInfoSI-List-RSCP
OPTIONAL
3GPP
Release 6
InterFreqMeasurementSysInfo-ECN0 ::= interFreqCellInfoSI-List }
937
SEQUENCE { InterFreqCellInfoSI-List-ECN0
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
InterFreqMeasurementSysInfo-HCS-RSCP ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-HCS-RSCP } InterFreqMeasurementSysInfo-HCS-ECN0 ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-HCS-ECN0 }
OPTIONAL
OPTIONAL
InterFreqMeasurementSysInfo-RSCP-LCR-r4 ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-RSCP-LCR } InterFreqMeasurementSysInfo-ECN0-LCR-r4 ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-ECN0-LCR } InterFreqMeasurementSysInfo-HCS-RSCP-LCR-r4 ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-HCS-RSCP-LCR } InterFreqMeasurementSysInfo-HCS-ECN0-LCR-r4 ::= SEQUENCE { interFreqCellInfoSI-List InterFreqCellInfoSI-List-HCS-ECN0-LCR } InterFreqRACHRepCellsList ::= InterFreqCellID SEQUENCE (SIZE (1..maxFreq)) OF
OPTIONAL
OPTIONAL
OPTIONAL
OPTIONAL
Dummy-InterFreqRACHReportingInfo ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { interFreqRepQuantityRACH-FDD InterFreqRepQuantityRACH-FDD }, tdd SEQUENCE { interFreqRepQuantityRACH-TDDList InterFreqRepQuantityRACH-TDDList }, interFreqRACHReportingThreshold Threshold, maxReportedCellsOnRACHinterFreq MaxReportedCellsOnRACHinterFreq } } InterFreqRACHReportingInfo ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { interFreqRepQuantityRACH-FDD InterFreqRepQuantityRACH-FDD }, tdd SEQUENCE { interFreqRepQuantityRACH-TDDList InterFreqRepQuantityRACH-TDDList } }, interFreqRACHReportingThreshold Threshold, maxReportedCellsOnRACHinterFreq MaxReportedCellsOnRACHinterFreq } InterFreqReportCriteria ::= intraFreqReportingCriteria interFreqReportingCriteria periodicalReportingCriteria noReporting } InterFreqReportCriteria-r4 ::= intraFreqReportingCriteria interFreqReportingCriteria periodicalReportingCriteria noReporting } InterFreqReportCriteria-r6 ::= intraFreqReportingCriteria interFreqReportingCriteria periodicalReportingCriteria noReporting } CHOICE { IntraFreqReportingCriteria, InterFreqReportingCriteria, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
CHOICE { IntraFreqReportingCriteria-r4, InterFreqReportingCriteria, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
CHOICE { IntraFreqReportingCriteria-r6, InterFreqReportingCriteria-r6, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
3GPP
Release 6
InterFreqReportingCriteria ::= interFreqEventList } InterFreqReportingCriteria-r6 ::= interFreqEventList } InterFreqReportingQuantity ::= utra-Carrier-RSSI frequencyQualityEstimate nonFreqRelatedQuantities } InterFreqRepQuantityRACH-FDD ::=
938
SEQUENCE { InterFreqEventList
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
SEQUENCE { InterFreqEventList-r6
OPTIONAL
SEQUENCE { BOOLEAN, BOOLEAN, CellReportingQuantities
ENUMERATED { cpich-EcN0, cpich-RSCP }
-- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. InterFreqRepQuantityRACH-TDD ::= ENUMERATED { dummy, primaryCCPCH-RSCP } InterFreqRepQuantityRACH-TDDList ::= SEQUENCE (SIZE (1..2)) OF InterFreqRepQuantityRACH-TDD InterFrequencyMeasurement ::= interFreqCellInfoList interFreqMeasQuantity interFreqReportingQuantity measurementValidity interFreqSetUpdate reportCriteria } InterFrequencyMeasurement-r4 ::= interFreqCellInfoList interFreqMeasQuantity interFreqReportingQuantity measurementValidity interFreqSetUpdate reportCriteria } InterFrequencyMeasurement-r6 ::= interFreqCellInfoList interFreqMeasQuantity interFreqReportingQuantity measurementValidity interFreqSetUpdate reportCriteria } InterRAT-TargetCellDescription ::= technologySpecificInfo gsm bsic frequency-band bcch-ARFCN ncMode }, is-2000 spare2 spare1 } } InterRATCellID ::= InterRATCellInfoIndication ::= SEQUENCE { InterFreqCellInfoList, InterFreqMeasQuantity InterFreqReportingQuantity MeasurementValidity UE-AutonomousUpdateMode InterFreqReportCriteria
SEQUENCE { InterFreqCellInfoList-r4, InterFreqMeasQuantity InterFreqReportingQuantity MeasurementValidity UE-AutonomousUpdateMode InterFreqReportCriteria-r4
SEQUENCE { InterFreqCellInfoList-r4, InterFreqMeasQuantity InterFreqReportingQuantity MeasurementValidity UE-AutonomousUpdateMode InterFreqReportCriteria-r6
SEQUENCE { CHOICE { SEQUENCE { BSIC, Frequency-Band, BCCH-ARFCN, NC-Mode NULL, NULL, NULL
OPTIONAL
INTEGER (0..maxCellMeas-1) INTEGER (0..3)
InterRATCellInfoList ::= SEQUENCE { removedInterRATCellList RemovedInterRATCellList, -- NOTE: Future revisions of dedicated messages including IE newInterRATCellList -- should use a corrected version of this IE newInterRATCellList NewInterRATCellList, cellsForInterRATMeasList CellsForInterRATMeasList OPTIONAL }
3GPP
Release 6
939
3GPP TS 25.331 V6.23.0 (2009-09)
InterRATCellInfoList-B ::= SEQUENCE { removedInterRATCellList RemovedInterRATCellList, -- NOTE: IE newInterRATCellList should be optional. However, system information -- does not support message versions. Hence, this can not be corrected newInterRATCellList NewInterRATCellList-B } InterRATCellInfoList-r4 ::= removedInterRATCellList newInterRATCellList cellsForInterRATMeasList } InterRATCellInfoList-r6 ::= removedInterRATCellList newInterRATCellList cellsForInterRATMeasList interRATCellInfoIndication-r6 } InterRATCellIndividualOffset ::= InterRATEvent ::= event3a event3b event3c event3d } InterRATEventList ::= SEQUENCE { RemovedInterRATCellList, NewInterRATCellList CellsForInterRATMeasList
OPTIONAL, OPTIONAL
SEQUENCE { RemovedInterRATCellList, NewInterRATCellList CellsForInterRATMeasList InterRATCellInfoIndication
INTEGER (-50..50)
CHOICE { Event3a, Event3b, Event3c, Event3d
SEQUENCE (SIZE (1..maxMeasEvent)) OF InterRATEvent SEQUENCE { EventIDInterRAT, CellToReportList
InterRATEventResults ::= eventID cellToReportList } InterRATInfo ::=
ENUMERATED { gsm } SEQUENCE { InterRATInfo, GSM-TargetCellInfoList
InterRATInfo-r6 ::= rat gsm-TargetCellInfoList }
OPTIONAL
InterRATMeasQuantity ::= measQuantityUTRAN-QualityEstimate ratSpecificInfo gsm measurementQuantity filterCoefficient bsic-VerificationRequired }, is-2000 tadd-EcIo tcomp-EcIo softSlope addIntercept } } } InterRATMeasuredResults ::= gsm spare }
SEQUENCE { IntraFreqMeasQuantity OPTIONAL, CHOICE { SEQUENCE { MeasurementQuantityGSM, FilterCoefficient DEFAULT fc0, BSIC-VerificationRequired SEQUENCE { INTEGER INTEGER INTEGER INTEGER
(0..63), (0..15), (0..63) (0..63)
OPTIONAL, OPTIONAL
CHOICE { GSM-MeasuredResultsList, NULL
InterRATMeasuredResultsList ::= SEQUENCE (SIZE (1..maxOtherRAT-16)) OF InterRATMeasuredResults InterRATMeasurement ::= interRATCellInfoList interRATMeasQuantity interRATReportingQuantity reportCriteria } SEQUENCE { InterRATCellInfoList InterRATMeasQuantity InterRATReportingQuantity InterRATReportCriteria
3GPP
Release 6
InterRATMeasurement-r4 ::= interRATCellInfoList interRATMeasQuantity interRATReportingQuantity reportCriteria } InterRATMeasurement-r6 ::= interRATCellInfoList interRATMeasQuantity interRATReportingQuantity reportCriteria } InterRATMeasurementSysInfo ::= interRATCellInfoList }
940
SEQUENCE { InterRATCellInfoList-r4 InterRATMeasQuantity InterRATReportingQuantity InterRATReportCriteria
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { InterRATCellInfoList-r6 InterRATMeasQuantity InterRATReportingQuantity InterRATReportCriteria
SEQUENCE { InterRATCellInfoList
OPTIONAL
InterRATMeasurementSysInfo-B ::= interRATCellInfoList }
SEQUENCE { InterRATCellInfoList-B
OPTIONAL
InterRATReportCriteria ::= CHOICE { interRATReportingCriteria InterRATReportingCriteria, periodicalReportingCriteria PeriodicalWithReportingCellStatus, noReporting ReportingCellStatusOpt } InterRATReportingCriteria ::= interRATEventList } SEQUENCE { InterRATEventList
OPTIONAL
InterRATReportingQuantity ::= SEQUENCE { utran-EstimatedQuality BOOLEAN, ratSpecificInfo CHOICE { gsm SEQUENCE { -- dummy and dummy2 are not used in this version of the specification -- and when received they should be ignored. dummy BOOLEAN, dummy2 BOOLEAN, gsm-Carrier-RSSI BOOLEAN } } } IntraFreqCellID ::= IntraFreqCellInfoList ::= removedIntraFreqCellList newIntraFreqCellList cellsForIntraFreqMeasList } IntraFreqCellInfoList-r4 ::= removedIntraFreqCellList newIntraFreqCellList cellsForIntraFreqMeasList } IntraFreqCellInfoSI-List-RSCP ::= removedIntraFreqCellList newIntraFreqCellList } IntraFreqCellInfoSI-List-ECN0 ::= removedIntraFreqCellList newIntraFreqCellList } IntraFreqCellInfoSI-List-HCS-RSCP ::= removedIntraFreqCellList newIntraFreqCellList } IntraFreqCellInfoSI-List-HCS-ECN0 ::= removedIntraFreqCellList newIntraFreqCellList } INTEGER (0..maxCellMeas-1) SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellList CellsForIntraFreqMeasList
SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellList-r4 CellsForIntraFreqMeasList
SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellSI-List-RSCP
OPTIONAL,
SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellSI-List-ECN0
OPTIONAL,
SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellSI-List-HCS-RSCP
OPTIONAL,
SEQUENCE { RemovedIntraFreqCellList NewIntraFreqCellSI-List-HCS-ECN0
OPTIONAL,
3GPP
Release 6
941
3GPP TS 25.331 V6.23.0 (2009-09)
IntraFreqCellInfoSI-List-RSCP-LCR-r4 ::= SEQUENCE { removedIntraFreqCellList RemovedIntraFreqCellList OPTIONAL, newIntraFreqCellList NewIntraFreqCellSI-List-RSCP-LCR-r4 } IntraFreqCellInfoSI-List-ECN0-LCR-r4 ::= SEQUENCE { removedIntraFreqCellList RemovedIntraFreqCellList OPTIONAL, newIntraFreqCellList NewIntraFreqCellSI-List-ECN0-LCR-r4 } IntraFreqCellInfoSI-List-HCS-RSCP-LCR-r4 ::= SEQUENCE { removedIntraFreqCellList RemovedIntraFreqCellList OPTIONAL, newIntraFreqCellList NewIntraFreqCellSI-List-HCS-RSCP-LCR-r4 } IntraFreqCellInfoSI-List-HCS-ECN0-LCR-r4 ::= SEQUENCE { removedIntraFreqCellList RemovedIntraFreqCellList OPTIONAL, newIntraFreqCellList NewIntraFreqCellSI-List-HCS-ECN0-LCR-r4 } IntraFreqEvent ::= e1a e1b e1c e1d e1e e1f e1g e1h e1i } IntraFreqEvent-r4 ::= e1a e1b e1c e1d e1e e1f e1g e1h e1i } IntraFreqEvent-LCR-r4 ::= e1a e1b e1c e1d e1e e1f e1g e1h e1i } IntraFreqEvent-r6 ::= e1a e1b e1c e1d e1e e1f e1g e1h e1i e1j } IntraFreqEvent-1d-r5 ::= triggeringCondition useCIO } IntraFreqEventCriteria ::= event hysteresis CHOICE { Event1a, Event1b, Event1c, NULL, Event1e, Event1f, NULL, ThresholdUsedFrequency, ThresholdUsedFrequency
CHOICE { Event1a-r4, Event1b-r4, Event1c, NULL, Event1e, Event1f, NULL, ThresholdUsedFrequency, ThresholdUsedFrequency
CHOICE { Event1a-LCR-r4, Event1b-LCR-r4, Event1c, NULL, Event1e, Event1f, NULL, ThresholdUsedFrequency, ThresholdUsedFrequency
CHOICE { Event1a-r4, Event1b-r4, Event1c, Event1d, Event1e-r6, Event1f-r6, NULL, ThresholdUsedFrequency-r6, ThresholdUsedFrequency-r6, Event1j-r6
SEQUENCE { TriggeringCondition2 BOOLEAN
OPTIONAL, OPTIONAL
SEQUENCE { IntraFreqEvent, Hysteresis,
3GPP
Release 6
timeToTrigger reportingCellStatus } IntraFreqEventCriteria-r4 ::= event hysteresis timeToTrigger reportingCellStatus } IntraFreqEventCriteria-LCR-r4 ::= event hysteresis timeToTrigger reportingCellStatus } IntraFreqEventCriteria-r6 ::= event hysteresis timeToTrigger reportingCellStatus } IntraFreqEventCriteriaList ::=
942
TimeToTrigger, ReportingCellStatus
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
SEQUENCE { IntraFreqEvent-r4, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { IntraFreqEvent-LCR-r4, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE { IntraFreqEvent-r6, Hysteresis, TimeToTrigger, ReportingCellStatus
OPTIONAL
SEQUENCE (SIZE (1..maxMeasEvent)) OF IntraFreqEventCriteria SEQUENCE (SIZE (1..maxMeasEvent)) OF IntraFreqEventCriteria-r4 SEQUENCE (SIZE (1..maxMeasEvent)) OF IntraFreqEventCriteria-LCR-r4 SEQUENCE (SIZE (1..maxMeasEvent)) OF IntraFreqEventCriteria-r6 SEQUENCE { EventIDIntraFreq, CellMeasurementEventResults
IntraFreqEventCriteriaList-r4 ::=
IntraFreqEventCriteriaList-LCR-r4 ::=
IntraFreqEventCriteriaList-r6 ::=
IntraFreqEventResults ::= eventID cellMeasurementEventResults }
IntraFreqMeasQuantity ::= SEQUENCE { filterCoefficient FilterCoefficient modeSpecificInfo CHOICE { fdd SEQUENCE { intraFreqMeasQuantity-FDD IntraFreqMeasQuantity-FDD }, tdd SEQUENCE { intraFreqMeasQuantity-TDDList IntraFreqMeasQuantity-TDDList } } } -- If IntraFreqMeasQuantity-FDD is used in InterRATMeasQuantity, then only -- cpich-Ec-N0 and cpich-RSCP are allowed. -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. IntraFreqMeasQuantity-FDD ::= ENUMERATED { cpich-Ec-N0, cpich-RSCP, pathloss, dummy } -- dummy is not used in this version of the specification, it should -- not be sent and if received the UE behaviour is not specified. IntraFreqMeasQuantity-TDD ::= ENUMERATED { primaryCCPCH-RSCP, pathloss, timeslotISCP, dummy } IntraFreqMeasQuantity-TDDList ::= SEQUENCE (SIZE (1..4)) OF IntraFreqMeasQuantity-TDD SEQUENCE (SIZE (1..maxCellMeas)) OF CellMeasuredResults
DEFAULT fc0,
IntraFreqMeasuredResultsList ::=
3GPP
Release 6
IntraFreqMeasurementSysInfo-RSCP ::= intraFreqMeasurementID intraFreqCellInfoSI-List intraFreqMeasQuantity intraFreqReportingQuantityForRACH maxReportedCellsOnRACH reportingInfoForCellDCH } IntraFreqMeasurementSysInfo-ECN0 ::= intraFreqMeasurementID intraFreqCellInfoSI-List intraFreqMeasQuantity intraFreqReportingQuantityForRACH maxReportedCellsOnRACH reportingInfoForCellDCH }
943
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { MeasurementIdentity DEFAULT IntraFreqCellInfoSI-List-RSCP IntraFreqMeasQuantity IntraFreqReportingQuantityForRACH MaxReportedCellsOnRACH ReportingInfoForCellDCH
1, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
SEQUENCE { MeasurementIdentity DEFAULT IntraFreqCellInfoSI-List-ECN0 IntraFreqMeasQuantity IntraFreqReportingQuantityForRACH MaxReportedCellsOnRACH ReportingInfoForCellDCH
IntraFreqMeasurementSysInfo-HCS-RSCP ::= SEQUENCE { intraFreqMeasurementID MeasurementIdentity DEFAULT intraFreqCellInfoSI-List IntraFreqCellInfoSI-List-HCS-RSCP intraFreqMeasQuantity IntraFreqMeasQuantity intraFreqReportingQuantityForRACH IntraFreqReportingQuantityForRACH maxReportedCellsOnRACH MaxReportedCellsOnRACH reportingInfoForCellDCH ReportingInfoForCellDCH } IntraFreqMeasurementSysInfo-HCS-ECN0 ::= SEQUENCE { intraFreqMeasurementID MeasurementIdentity DEFAULT intraFreqCellInfoSI-List IntraFreqCellInfoSI-List-HCS-ECN0 intraFreqMeasQuantity IntraFreqMeasQuantity intraFreqReportingQuantityForRACH IntraFreqReportingQuantityForRACH maxReportedCellsOnRACH MaxReportedCellsOnRACH reportingInfoForCellDCH ReportingInfoForCellDCH } IntraFreqMeasurementSysInfo-RSCP-LCR-r4 intraFreqMeasurementID intraFreqCellInfoSI-List intraFreqMeasQuantity intraFreqReportingQuantityForRACH maxReportedCellsOnRACH reportingInfoForCellDCH } IntraFreqMeasurementSysInfo-ECN0-LCR-r4 intraFreqMeasurementID intraFreqCellInfoSI-List intraFreqMeasQuantity intraFreqReportingQuantityForRACH maxReportedCellsOnRACH reportingInfoForCellDCH }
::= SEQUENCE { MeasurementIdentity DEFAULT 1, IntraFreqCellInfoSI-List-RSCP-LCR-r4 OPTIONAL, IntraFreqMeasQuantity OPTIONAL, IntraFreqReportingQuantityForRACH OPTIONAL, MaxReportedCellsOnRACH OPTIONAL, ReportingInfoForCellDCH-LCR-r4 OPTIONAL
::= SEQUENCE { MeasurementIdentity DEFAULT 1, IntraFreqCellInfoSI-List-ECN0-LCR-r4 OPTIONAL, IntraFreqMeasQuantity OPTIONAL, IntraFreqReportingQuantityForRACH OPTIONAL, MaxReportedCellsOnRACH OPTIONAL, ReportingInfoForCellDCH-LCR-r4 OPTIONAL
IntraFreqMeasurementSysInfo-HCS-RSCP-LCR-r4 ::= SEQUENCE { intraFreqMeasurementID MeasurementIdentity DEFAULT 1, intraFreqCellInfoSI-List IntraFreqCellInfoSI-List-HCS-RSCP-LCR-r4 OPTIONAL, intraFreqMeasQuantity IntraFreqMeasQuantity OPTIONAL, intraFreqReportingQuantityForRACH IntraFreqReportingQuantityForRACH OPTIONAL, maxReportedCellsOnRACH MaxReportedCellsOnRACH OPTIONAL, reportingInfoForCellDCH ReportingInfoForCellDCH-LCR-r4 OPTIONAL } IntraFreqMeasurementSysInfo-HCS-ECN0-LCR-r4 ::= SEQUENCE { intraFreqMeasurementID MeasurementIdentity DEFAULT 1, intraFreqCellInfoSI-List IntraFreqCellInfoSI-List-HCS-ECN0-LCR-r4 OPTIONAL, intraFreqMeasQuantity IntraFreqMeasQuantity OPTIONAL, intraFreqReportingQuantityForRACH IntraFreqReportingQuantityForRACH OPTIONAL, maxReportedCellsOnRACH MaxReportedCellsOnRACH OPTIONAL, reportingInfoForCellDCH ReportingInfoForCellDCH-LCR-r4 OPTIONAL } IntraFreqReportCriteria ::= intraFreqReportingCriteria periodicalReportingCriteria noReporting } CHOICE { IntraFreqReportingCriteria, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
3GPP
Release 6
IntraFreqReportCriteria-r4 ::= intraFreqReportingCriteria periodicalReportingCriteria noReporting } IntraFreqReportCriteria-r6 ::= intraFreqReportingCriteria periodicalReportingCriteria noReporting } IntraFreqReportingCriteria ::= eventCriteriaList } IntraFreqReportingCriteria-r4 ::= eventCriteriaList }
944
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE { IntraFreqReportingCriteria-r4, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
CHOICE { IntraFreqReportingCriteria-r6, PeriodicalWithReportingCellStatus, ReportingCellStatusOpt
SEQUENCE { IntraFreqEventCriteriaList
OPTIONAL
SEQUENCE { IntraFreqEventCriteriaList-r4
OPTIONAL
IntraFreqReportingCriteria-LCR-r4 ::= eventCriteriaList }
SEQUENCE { IntraFreqEventCriteriaList-LCR-r4
OPTIONAL
IntraFreqReportingCriteria-r6 ::= SEQUENCE { eventCriteriaList IntraFreqEventCriteriaList-r6 } IntraFreqReportingQuantity ::= SEQUENCE { activeSetReportingQuantities CellReportingQuantities, monitoredSetReportingQuantities CellReportingQuantities, detectedSetReportingQuantities CellReportingQuantities }
OPTIONAL
OPTIONAL
IntraFreqReportingQuantityForRACH ::= SEQUENCE { sfn-SFN-OTD-Type SFN-SFN-OTD-Type, modeSpecificInfo CHOICE { fdd SEQUENCE { intraFreqRepQuantityRACH-FDD IntraFreqRepQuantityRACH-FDD }, tdd SEQUENCE { intraFreqRepQuantityRACH-TDDList IntraFreqRepQuantityRACH-TDDList } } } IntraFreqRepQuantityRACH-FDD ::= ENUMERATED { cpich-EcN0, cpich-RSCP, pathloss, noReport } ENUMERATED { timeslotISCP, primaryCCPCH-RSCP, noReport }
IntraFreqRepQuantityRACH-TDD ::=
IntraFreqRepQuantityRACH-TDDList ::= SEQUENCE (SIZE (1..2)) OF IntraFreqRepQuantityRACH-TDD IntraFrequencyMeasurement ::= intraFreqCellInfoList intraFreqMeasQuantity intraFreqReportingQuantity measurementValidity reportCriteria } IntraFrequencyMeasurement-r4 ::= intraFreqCellInfoList intraFreqMeasQuantity intraFreqReportingQuantity measurementValidity reportCriteria } IntraFrequencyMeasurement-r6 ::= intraFreqCellInfoList intraFreqMeasQuantity intraFreqReportingQuantity SEQUENCE { IntraFreqCellInfoList IntraFreqMeasQuantity IntraFreqReportingQuantity MeasurementValidity IntraFreqReportCriteria
SEQUENCE { IntraFreqCellInfoList-r4 IntraFreqMeasQuantity IntraFreqReportingQuantity MeasurementValidity IntraFreqReportCriteria-r4
SEQUENCE { IntraFreqCellInfoList-r4 IntraFreqMeasQuantity IntraFreqReportingQuantity
3GPP
Release 6
945
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL,
measurementValidity MeasurementValidity -- reportCriteria is optional in later versions of this message reportCriteria IntraFreqReportCriteria-r6 } IODE ::= IP-Length ::= INTEGER (0..255) ENUMERATED { ipl5, ipl10 } BOOLEAN ENUMERATED { e5, e7, e10, e15, e20, e30, e40, e50 } ENUMERATED { e30, e40, e50, e70, e100} ENUMERATED { frequency, timeslot, colourcode, outputpower, pn-Offset } ENUMERATED { e1, e2, e3, e4, e5, e6}
IP-PCCPCH-r4 ::= IP-Spacing ::=
IP-Spacing-TDD ::=
IS-2000SpecificMeasInfo ::=
MaxNumberOfReportingCellsType1 ::=
ENUMERATED { e1, e2, e3, e4, e5, e6, e7, e8, e9, e10, e11, e12} ENUMERATED { viactCellsPlus1, viactCellsPlus2, viactCellsPlus3, viactCellsPlus4, viactCellsPlus5, viactCellsPlus6 } ENUMERATED { noReport, currentCell, currentAnd-1-BestNeighbour, currentAnd-2-BestNeighbour, currentAnd-3-BestNeighbour, currentAnd-4-BestNeighbour, currentAnd-5-BestNeighbour, currentAnd-6-BestNeighbour } INTEGER (1..8)
MaxReportedCellsOnRACH ::=
MaxReportedCellsOnRACHinterFreq ::=
MeasuredResults ::= CHOICE { intraFreqMeasuredResultsList IntraFreqMeasuredResultsList, interFreqMeasuredResultsList InterFreqMeasuredResultsList, interRATMeasuredResultsList InterRATMeasuredResultsList, trafficVolumeMeasuredResultsList TrafficVolumeMeasuredResultsList, qualityMeasuredResults QualityMeasuredResults, ue-InternalMeasuredResults UE-InternalMeasuredResults, ue-positioning-MeasuredResults UE-Positioning-MeasuredResults, spare NULL } MeasuredResults-v390ext ::= ue-positioning-MeasuredResults-v390ext } SEQUENCE { UE-Positioning-MeasuredResults-v390ext
MeasuredResults-v590ext ::= CHOICE { intraFrequencyMeasuredResultsList interFrequencyMeasuredResultsList }
IntraFrequencyMeasuredResultsList-v590ext, InterFrequencyMeasuredResultsList-v590ext
MeasuredResults-LCR-r4 ::= CHOICE { intraFreqMeasuredResultsList IntraFreqMeasuredResultsList, interFreqMeasuredResultsList InterFreqMeasuredResultsList, interRATMeasuredResultsList InterRATMeasuredResultsList, trafficVolumeMeasuredResultsList TrafficVolumeMeasuredResultsList, qualityMeasuredResults QualityMeasuredResults, ue-InternalMeasuredResults UE-InternalMeasuredResults-LCR-r4, ue-positioniing-MeasuredResults UE-Positioning-MeasuredResults,
3GPP
Release 6
spare } MeasuredResultsList ::= NULL
946
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE (SIZE (1..maxAdditionalMeas)) OF MeasuredResults SEQUENCE (SIZE (1..maxAdditionalMeas)) OF MeasuredResults-LCR-r4
MeasuredResultsList-LCR-r4-ext ::=
MeasuredResultsOnRACH ::= SEQUENCE { currentCell SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { measurementQuantity CHOICE { cpich-Ec-N0 CPICH-Ec-N0, cpich-RSCP CPICH-RSCP, pathloss Pathloss, spare NULL } }, tdd SEQUENCE { timeslotISCP TimeslotISCP-List primaryCCPCH-RSCP PrimaryCCPCH-RSCP } } }, monitoredCells MonitoredCellRACH-List } MeasuredResultsOnRACHinterFreq ::= interFreqCellIndication-SIB11 interFreqCellIndication-SIB12 interFreqRACHRepCellsList } MeasurementCommand ::= setup modify measurementType }, release } MeasurementCommand-r4 ::= setup modify measurementType }, release } MeasurementCommand-r6 ::= setup modify measurementType }, release } SEQUENCE { INTEGER (0..1), INTEGER (0..1), InterFreqRACHRepCellsList
OPTIONAL, OPTIONAL
OPTIONAL
CHOICE { MeasurementType, SEQUENCE { MeasurementType NULL
OPTIONAL
CHOICE { MeasurementType-r4, SEQUENCE { MeasurementType-r4 NULL
OPTIONAL
CHOICE { MeasurementType-r6, SEQUENCE { MeasurementType-r6 NULL
OPTIONAL
MeasurementControlSysInfo ::= SEQUENCE { -- CHOICE cellSelectQualityMeasure represents PCCPCH-RSCP in TDD mode. use-of-HCS CHOICE { hcs-not-used SEQUENCE { cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-RSCP OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-RSCP }, cpich-Ec-N0 SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-ECN0 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-ECN0 } }, interRATMeasurementSysInfo InterRATMeasurementSysInfo-B OPTIONAL }, hcs-used SEQUENCE {
OPTIONAL
OPTIONAL
3GPP
Release 6
947
3GPP TS 25.331 V6.23.0 (2009-09)
cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-HCS-RSCP OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-HCS-RSCP OPTIONAL }, cpich-Ec-N0 SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-HCS-ECN0 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-HCS-ECN0 OPTIONAL } }, interRATMeasurementSysInfo InterRATMeasurementSysInfo OPTIONAL } }, trafficVolumeMeasSysInfo TrafficVolumeMeasSysInfo OPTIONAL, -- dummy is not used in this version of specification and it shall be ignored by the UE. dummy UE-InternalMeasurementSysInfo OPTIONAL } MeasurementControlSysInfoExtension ::= SEQUENCE { -- CHOICE cellSelectQualityMeasure represents PCCPCH-RSCP in TDD mode. use-of-HCS CHOICE { hcs-not-used SEQUENCE { cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-RSCP OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-RSCP OPTIONAL }, cpich-Ec-N0 SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-ECN0 OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-ECN0 OPTIONAL } }, newInterRATCellList NewInterRATCellList OPTIONAL }, hcs-used SEQUENCE { cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-HCS-RSCP OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-HCS-RSCP OPTIONAL }, cpich-Ec-N0 SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-HCS-ECN0 OPTIONAL, newInterFreqCellList NewInterFreqCellSI-List-HCS-ECN0 OPTIONAL } }, newInterRATCellList NewInterRATCellList OPTIONAL } } } MeasurementControlSysInfoExtensionAddon-r5 ::= SEQUENCE { --The order of the list corresponds to the order of cell in newIntraFrequencyCellInfoList newIntraFrequencyCellInfoListAddon-r5 SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterFrequencyCellInfoList newInterFrequencyCellInfoListAddon-r5 SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterRATCellInfoList newInterRATCellInfoListAddon-r5 SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL } MeasurementControlSysInfoExtension-LCR-r4 ::= SEQUENCE { -- CHOICE cellSelectQualityMeasure represents PCCPCH-RSCP in TDD mode. use-of-HCS CHOICE { hcs-not-used SEQUENCE { cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-RSCP-LCR-r4 newInterFreqCellList NewInterFreqCellSI-List-RSCP-LCR-r4 }, cpich-Ec-N0 SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-ECN0-LCR-r4 newInterFreqCellList NewInterFreqCellSI-List-ECN0-LCR-r4
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
3GPP
Release 6
} }, newInterRATCellList
948
3GPP TS 25.331 V6.23.0 (2009-09)
NewInterRATCellList OPTIONAL }, hcs-used SEQUENCE { cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-HCS-RSCP-LCR-r4 newInterFreqCellList NewInterFreqCellSI-List-HCS-RSCP-LCR-r4 }, cpich-Ec-N0 SEQUENCE { newIntraFreqCellList NewIntraFreqCellSI-List-HCS-ECN0-LCR-r4 newInterFreqCellList NewInterFreqCellSI-List-HCS-ECN0-LCR-r4 } }, newInterRATCellList NewInterRATCellList OPTIONAL } } }
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
MeasurementControlSysInfo-LCR-r4-ext ::= SEQUENCE { -- CHOICE use-of-HCS shall have the same value as the use-of-HCS -- in MeasurementControlSysInfo -- CHOICE cellSelectQualityMeasure represents PCCPCH-RSCP in TDD mode. use-of-HCS CHOICE { hcs-not-used SEQUENCE { -- CHOICE cellSelectQualityMeasure shall have the same value as the -- cellSelectQualityMeasure in MeasurementControlSysInfo cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-RSCP-LCR-r4 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-RSCP-LCR-r4 OPTIONAL }, cpich-Ec-N0 SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-ECN0-LCR-r4 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-ECN0-LCR-r4 OPTIONAL } } }, hcs-used SEQUENCE { -- CHOICE cellSelectQualityMeasure shall have the same value as the -- cellSelectQualityMeasure in MeasurementControlSysInfo cellSelectQualityMeasure CHOICE { cpich-RSCP SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-HCS-RSCP-LCR-r4 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-HCS-RSCP-LCR-r4 OPTIONAL }, cpich-Ec-N0 SEQUENCE { intraFreqMeasurementSysInfo IntraFreqMeasurementSysInfo-HCS-ECN0-LCR-r4 OPTIONAL, interFreqMeasurementSysInfo InterFreqMeasurementSysInfo-HCS-ECN0-LCR-r4 OPTIONAL } } } } } MeasurementIdentity ::= MeasurementQuantityGSM ::= INTEGER (1..16) ENUMERATED { gsm-CarrierRSSI, dummy } SEQUENCE { TransferMode, PeriodicalOrEventTrigger
MeasurementReportingMode ::= measurementReportTransferMode periodicalOrEventTrigger } MeasurementType ::= intraFrequencyMeasurement interFrequencyMeasurement interRATMeasurement ue-positioning-Measurement trafficVolumeMeasurement qualityMeasurement ue-InternalMeasurement }
CHOICE { IntraFrequencyMeasurement, InterFrequencyMeasurement, InterRATMeasurement, UE-Positioning-Measurement, TrafficVolumeMeasurement, QualityMeasurement, UE-InternalMeasurement
3GPP
Release 6
949
3GPP TS 25.331 V6.23.0 (2009-09)
MeasurementType-r4 ::= intraFrequencyMeasurement interFrequencyMeasurement interRATMeasurement up-Measurement trafficVolumeMeasurement qualityMeasurement ue-InternalMeasurement } MeasurementType-r6 ::= intraFrequencyMeasurement interFrequencyMeasurement interRATMeasurement up-Measurement trafficVolumeMeasurement qualityMeasurement ue-InternalMeasurement } MeasurementValidity ::= ue-State } MonitoredCellRACH-List ::=
CHOICE { IntraFrequencyMeasurement-r4, InterFrequencyMeasurement-r4, InterRATMeasurement-r4, UE-Positioning-Measurement-r4, TrafficVolumeMeasurement, QualityMeasurement, UE-InternalMeasurement-r4
CHOICE { IntraFrequencyMeasurement-r6, InterFrequencyMeasurement-r6, InterRATMeasurement-r6, UE-Positioning-Measurement-r4, TrafficVolumeMeasurement, QualityMeasurement, UE-InternalMeasurement-r4
SEQUENCE { ENUMERATED { cell-DCH, all-But-Cell-DCH, all-States }
SEQUENCE (SIZE (1..8)) OF MonitoredCellRACH-Result SEQUENCE { SFN-SFN-ObsTimeDifference CHOICE { SEQUENCE { PrimaryCPICH-Info, CHOICE { CPICH-Ec-N0, CPICH-RSCP, Pathloss, NULL
MonitoredCellRACH-Result ::= sfn-SFN-ObsTimeDifference modeSpecificInfo fdd primaryCPICH-Info measurementQuantity cpich-Ec-N0 cpich-RSCP pathloss spare } }, tdd cellParametersID primaryCCPCH-RSCP } } } MultipathIndicator ::=
OPTIONAL,
OPTIONAL SEQUENCE { CellParametersID, PrimaryCCPCH-RSCP
ENUMERATED { nm, low, medium, high } SEQUENCE { INTEGER (1..16) T-CRMaxHyst
N-CR-T-CRMaxHyst ::= n-CR t-CRMaxHyst } NavigationModelSatInfo ::= satID satelliteStatus ephemerisParameter } NavigationModelSatInfoList ::=
DEFAULT 8,
SEQUENCE { SatID, SatelliteStatus, EphemerisParameter
OPTIONAL
SEQUENCE (SIZE (1..maxSat)) OF NavigationModelSatInfo SEQUENCE { BIT STRING (SIZE (2)), BIT STRING (SIZE (4)), BIT STRING (SIZE (6)), BIT STRING (SIZE (10)), BIT STRING (SIZE (1)), SubFrame1Reserved, BIT STRING (SIZE (8)), BIT STRING (SIZE (16)), BIT STRING (SIZE (8)),
EphemerisParameter ::= codeOnL2 uraIndex satHealth iodc l2Pflag sf1Revd t-GD t-oc af2
3GPP
Release 6
af1 af0 c-rs delta-n m0 c-uc e c-us a-Sqrt t-oe fitInterval aodo c-ic omega0 c-is i0 c-rc omega omegaDot iDot } NC-Mode ::= BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT BIT
950
STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (16)), (22)), (16)), (16)), (32)), (16)), (32)), (16)), (32)), (16)), (1)), (5)), (16)), (32)), (16)), (32)), (16)), (32)), (24)), (14))
3GPP TS 25.331 V6.23.0 (2009-09)
Neighbour ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { neighbourIdentity PrimaryCPICH-Info uE-RX-TX-TimeDifferenceType2Info UE-RX-TX-TimeDifferenceType2Info }, tdd SEQUENCE { neighbourAndChannelIdentity CellAndChannelIdentity } }, neighbourQuality NeighbourQuality, sfn-SFN-ObsTimeDifference2 SFN-SFN-ObsTimeDifference2} Neighbour-v390ext ::= modeSpecificInfo fdd frequencyInfo }, tdd } } NeighbourList ::= SEQUENCE { CHOICE { SEQUENCE { FrequencyInfo NULL
OPTIONAL, OPTIONAL
OPTIONAL
SEQUENCE (SIZE (1..maxCellMeas)) OF Neighbour
-- The order of the cells in IE NeighbourList-v390ext shall be the -- same as the order in IE NeighbourList NeighbourList-v390ext ::= SEQUENCE (SIZE (1..maxCellMeas)) OF Neighbour-v390ext NeighbourQuality ::= ue-Positioning-OTDOA-Quality } NewInterFreqCell ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCell-r4 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellList ::= SEQUENCE { UE-Positioning-OTDOA-Quality
SEQUENCE { InterFreqCellID FrequencyInfo CellInfo
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfo-r4
OPTIONAL, OPTIONAL,
SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCell SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCell-r4 SEQUENCE { InterFreqCellID FrequencyInfo
NewInterFreqCellList-r4 ::=
NewInterFreqCellSI-RSCP ::= interFreqCellID frequencyInfo
OPTIONAL, OPTIONAL,
3GPP
Release 6
cellInfo } NewInterFreqCellSI-ECN0 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-HCS-RSCP ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-HCS-ECN0 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-RSCP-LCR-r4 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-ECN0-LCR-r4 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-HCS-RSCP-LCR-r4 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-HCS-ECN0-LCR-r4 ::= interFreqCellID frequencyInfo cellInfo } NewInterFreqCellSI-List-ECN0 ::=
951
CellInfoSI-RSCP
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-ECN0
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-HCS-RSCP
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-HCS-ECN0
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-RSCP-LCR-r4
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-ECN0-LCR-r4
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-HCS-RSCP-LCR-r4
OPTIONAL, OPTIONAL,
SEQUENCE { InterFreqCellID FrequencyInfo CellInfoSI-HCS-ECN0-LCR-r4
OPTIONAL, OPTIONAL,
SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-ECN0 SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-HCS-RSCP SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-HCS-ECN0 SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-RSCP SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-ECN0-LCR-r4
NewInterFreqCellSI-List-HCS-RSCP ::=
NewInterFreqCellSI-List-HCS-ECN0 ::=
NewInterFreqCellSI-List-RSCP ::=
NewInterFreqCellSI-List-ECN0-LCR-r4 ::=
NewInterFreqCellSI-List-HCS-RSCP-LCR-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-HCS-RSCP-LCR-r4 NewInterFreqCellSI-List-HCS-ECN0-LCR-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-HCS-ECN0-LCR-r4 NewInterFreqCellSI-List-RSCP-LCR-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterFreqCellSI-RSCP-LCR-r4
NewInterRATCell ::= SEQUENCE { interRATCellID InterRATCellID OPTIONAL, technologySpecificInfo CHOICE { gsm SEQUENCE { cellSelectionReselectionInfo CellSelectReselectInfoSIB-11-12 interRATCellIndividualOffset InterRATCellIndividualOffset, bsic BSIC, frequency-band Frequency-Band, bcch-ARFCN BCCH-ARFCN,
OPTIONAL,
3GPP
Release 6
952
3GPP TS 25.331 V6.23.0 (2009-09)
-- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy NULL OPTIONAL }, is-2000 SEQUENCE { is-2000SpecificMeasInfo IS-2000SpecificMeasInfo }, -- ASN.1 inconsistency: NewInterRATCellList should be optional within -- InterRATCellInfoList. The UE shall consider IE NewInterRATCell with -- technologySpecificInfo set to "absent" as valid and handle the -- message as if the IE NewInterRATCell was absent absent NULL, spare1 NULL } } NewInterRATCell-B ::= SEQUENCE { interRATCellID InterRATCellID OPTIONAL, technologySpecificInfo CHOICE { gsm SEQUENCE { cellSelectionReselectionInfo CellSelectReselectInfoSIB-11-12 interRATCellIndividualOffset InterRATCellIndividualOffset, bsic BSIC, frequency-band Frequency-Band, bcch-ARFCN BCCH-ARFCN, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy NULL OPTIONAL }, is-2000 SEQUENCE { is-2000SpecificMeasInfo IS-2000SpecificMeasInfo }, -- ASN.1 inconsistency: NewInterRATCellList-B should be optional within -- InterRATCellInfoList-B. The UE shall consider IE NewInterRATCell-B with -- technologySpecificInfo set to "absent" as valid and handle the -- message as if the IE NewInterRATCell-B was absent absent NULL, spare1 NULL } } NewInterRATCellList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterRATCell SEQUENCE (SIZE (1..maxCellMeas)) OF NewInterRATCell-B SEQUENCE { IntraFreqCellID CellInfo
OPTIONAL,
NewInterRATCellList-B ::=
NewIntraFreqCell ::= intraFreqCellID cellInfo } NewIntraFreqCell-r4 ::= intraFreqCellID cellInfo } NewIntraFreqCellList ::=
OPTIONAL,
SEQUENCE { IntraFreqCellID CellInfo-r4
OPTIONAL,
SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCell SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCell-r4 SEQUENCE { IntraFreqCellID CellInfoSI-RSCP
NewIntraFreqCellList-r4 ::=
NewIntraFreqCellSI-RSCP ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-ECN0 ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-HCS-RSCP ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-HCS-ECN0 ::=
OPTIONAL,
SEQUENCE { IntraFreqCellID CellInfoSI-ECN0 SEQUENCE { IntraFreqCellID CellInfoSI-HCS-RSCP
OPTIONAL,
OPTIONAL,
SEQUENCE {
3GPP
Release 6
intraFreqCellID cellInfo } NewIntraFreqCellSI-RSCP-LCR-r4 ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-ECN0-LCR-r4 ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-HCS-RSCP-LCR-r4 ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-HCS-ECN0-LCR-r4 ::= intraFreqCellID cellInfo } NewIntraFreqCellSI-List-RSCP ::=
953
IntraFreqCellID CellInfoSI-HCS-ECN0
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL,
SEQUENCE { IntraFreqCellID CellInfoSI-RSCP-LCR-r4
OPTIONAL,
SEQUENCE { IntraFreqCellID CellInfoSI-ECN0-LCR-r4 SEQUENCE { IntraFreqCellID CellInfoSI-HCS-RSCP-LCR-r4
OPTIONAL,
OPTIONAL,
SEQUENCE { IntraFreqCellID CellInfoSI-HCS-ECN0-LCR-r4
OPTIONAL,
SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-RSCP SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-ECN0 SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-HCS-RSCP SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-HCS-ECN0 SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-RSCP-LCR-r4 SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-ECN0-LCR-r4
NewIntraFreqCellSI-List-ECN0 ::=
NewIntraFreqCellSI-List-HCS-RSCP ::=
NewIntraFreqCellSI-List-HCS-ECN0 ::=
NewIntraFreqCellSI-List-RSCP-LCR-r4 ::=
NewIntraFreqCellSI-List-ECN0-LCR-r4 ::=
NewIntraFreqCellSI-List-HCS-RSCP-LCR-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-HCS-RSCP-LCR-r4 NewIntraFreqCellSI-List-HCS-ECN0-LCR-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF NewIntraFreqCellSI-HCS-ECN0-LCR-r4 -- IE "nonUsedFreqThreshold" is not needed in case of event 2a -- In case of event 2a UTRAN should include value 0 within IE "nonUsedFreqThreshold" -- In case of event 2a, the UE shall be ignore IE "nonUsedFreqThreshold" -- In later versions of the message including this IE, a special version of -- IE "NonUsedFreqParameterList" may be defined for event 2a, namely a -- version not including IE "nonUsedFreqThreshold" NonUsedFreqParameter ::= SEQUENCE { nonUsedFreqThreshold Threshold, nonUsedFreqW W } NonUsedFreqParameter-r6 ::= nonUsedFreqThreshold nonUsedFreqW } NonUsedFreqParameterList ::= SEQUENCE { Threshold-r6, W
SEQUENCE (SIZE (1..maxFreq)) OF NonUsedFreqParameter SEQUENCE (SIZE (1..maxFreq)) OF NonUsedFreqParameter-r6
NonUsedFreqParameterList-r6 ::=
NonUsedFreqWList-r6 ::=
SEQUENCE (SIZE (1..maxFreq)) OF W INTEGER (0..4095) ENUMERATED { c20, c40, c80, c160, c320, c640, c1280, moreThan1280 }
ObservedTimeDifferenceToGSM ::= OTDOA-SearchWindowSize ::=
-- SPARE: Pathloss, Max = 158
3GPP
Release 6
-- Values above Max are spare Pathloss ::= PenaltyTime-RSCP ::= notUsed pt10 pt20 pt30 pt40 pt50 pt60 } PenaltyTime-ECN0 ::= notUsed pt10 pt20 pt30 pt40 pt50 pt60 } PendingTimeAfterTrigger ::=
954
3GPP TS 25.331 V6.23.0 (2009-09)
INTEGER (46..173) CHOICE { NULL, TemporaryOffset1, TemporaryOffset1, TemporaryOffset1, TemporaryOffset1, TemporaryOffset1, TemporaryOffset1
CHOICE { NULL, TemporaryOffsetList, TemporaryOffsetList, TemporaryOffsetList, TemporaryOffsetList, TemporaryOffsetList, TemporaryOffsetList
ENUMERATED { ptat0-25, ptat0-5, ptat1, ptat2, ptat4, ptat8, ptat16 } ENUMERATED { periodical, eventTrigger } SEQUENCE { ReportingAmount ReportingIntervalLong
PeriodicalOrEventTrigger ::=
PeriodicalReportingCriteria ::= reportingAmount reportingInterval }
DEFAULT ra-Infinity,
PeriodicalWithReportingCellStatus ::= SEQUENCE { periodicalReportingCriteria PeriodicalReportingCriteria, reportingCellStatus ReportingCellStatus } PLMNIdentitiesOfNeighbourCells ::= plmnsOfIntraFreqCellsList plmnsOfInterFreqCellsList plmnsOfInterRATCellsList } PLMNsOfInterFreqCellsList ::= plmn-Identity } PLMNsOfIntraFreqCellsList ::= plmn-Identity } PLMNsOfInterRATCellsList ::= plmn-Identity } PositionEstimate ::= ellipsoidPoint ellipsoidPointUncertCircle ellipsoidPointUncertEllipse ellipsoidPointAltitude ellipsoidPointAltitudeEllipse } PositioningMethod ::= CHOICE { EllipsoidPoint, EllipsoidPointUncertCircle, EllipsoidPointUncertEllipse, EllipsoidPointAltitude, EllipsoidPointAltitudeEllipsoide SEQUENCE { PLMNsOfIntraFreqCellsList PLMNsOfInterFreqCellsList PLMNsOfInterRATCellsList
OPTIONAL
SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE { PLMN-Identity OPTIONAL
ENUMERATED { otdoa, gps, otdoaOrGPS, cellID }
-- Actual value PRC = IE value * 0.32 PRC ::= INTEGER (-2047..2047)
3GPP
Release 6
955
3GPP TS 25.331 V6.23.0 (2009-09)
-- SPARE: PrimaryCCPCH-RSCP, Max = 91 -- Values above Max are spare PrimaryCCPCH-RSCP ::= INTEGER (0..127) Q-HCS ::= Q-OffsetS-N ::= Q-QualMin ::= INTEGER (0..99) INTEGER (-50..50) INTEGER (-24..0)
-- Actual value Q-RxlevMin = (IE value * 2) + 1 Q-RxlevMin ::= INTEGER (-58..-13) QualityEventResults ::= SEQUENCE (SIZE (1..maxTrCH)) OF TransportChannelIdentity SEQUENCE { BLER-MeasurementResultsList CHOICE { NULL, SEQUENCE { SIR-MeasurementList
QualityMeasuredResults ::= blerMeasurementResultsList modeSpecificInfo fdd tdd sir-MeasurementResults } } } QualityMeasurement ::= qualityReportingQuantity reportCriteria } QualityReportCriteria ::= qualityReportingCriteria periodicalReportingCriteria noReporting } QualityReportingCriteria ::=
OPTIONAL,
OPTIONAL
SEQUENCE { QualityReportingQuantity QualityReportCriteria
OPTIONAL,
CHOICE { QualityReportingCriteria, PeriodicalReportingCriteria, NULL
SEQUENCE (SIZE (1..maxTrCH)) OF QualityReportingCriteriaSingle SEQUENCE { TransportChannelIdentity, INTEGER (1..512), INTEGER (1..512), INTEGER (1..512)
QualityReportingCriteriaSingle ::= transportChannelIdentity totalCRC badCRC pendingAfterTrigger } QualityReportingQuantity ::= dl-TransChBLER bler-dl-TransChIdList modeSpecificInfo fdd tdd sir-TFCS-List } } } RAT-Type ::=
SEQUENCE { BOOLEAN, BLER-TransChIdList CHOICE { NULL, SEQUENCE { SIR-TFCS-List
OPTIONAL,
OPTIONAL
ENUMERATED { gsm, is2000 } CHOICE { EllipsoidPoint, EllipsoidPointAltitude
ReferenceCellPosition ::= ellipsoidPoint ellipsoidPointWithAltitude }
-- ReferenceLocation, as defined in 23.032 ReferenceLocation ::= SEQUENCE { ellipsoidPointAltitudeEllipsoide }
EllipsoidPointAltitudeEllipsoide
ReferenceTimeDifferenceToCell ::= CHOICE { -- Actual value accuracy40 = IE value * 40 accuracy40 INTEGER (0..960), -- Actual value accuracy256 = IE value * 256 accuracy256 INTEGER (0..150), -- Actual value accuracy2560 = IE value * 2560 accuracy2560 INTEGER (0..15)
3GPP
Release 6
} RemovedInterFreqCellList ::= removeAllInterFreqCells removeSomeInterFreqCells removeNoInterFreqCells } RemovedInterRATCellList ::= removeAllInterRATCells removeSomeInterRATCells removeNoInterRATCells } RemovedIntraFreqCellList ::= removeAllIntraFreqCells removeSomeIntraFreqCells removeNoIntraFreqCells } ReplacementActivationThreshold ::=
956
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE { NULL, SEQUENCE (SIZE (1..maxCellMeas)) OF InterFreqCellID, NULL
CHOICE { NULL, SEQUENCE (SIZE (1..maxCellMeas)) OF InterRATCellID, NULL
CHOICE { NULL, SEQUENCE (SIZE (1..maxCellMeas)) OF IntraFreqCellID, NULL
ENUMERATED { notApplicable, t1, t2, t3, t4, t5, t6, t7 } ENUMERATED { notApplicable, t1, t2, t3, t4, t5, t6, t7 } ENUMERATED { ra1, ra2, ra4, ra8, ra16, ra32, ra64, ra-Infinity }
ReportDeactivationThreshold ::=
ReportingAmount ::=
ReportingCellStatus ::= CHOICE{ withinActiveSet MaxNumberOfReportingCellsType1, withinMonitoredSetUsedFreq MaxNumberOfReportingCellsType1, withinActiveAndOrMonitoredUsedFreq MaxNumberOfReportingCellsType1, withinDetectedSetUsedFreq MaxNumberOfReportingCellsType1, withinMonitoredAndOrDetectedUsedFreq MaxNumberOfReportingCellsType1, allActiveplusMonitoredSet MaxNumberOfReportingCellsType3, allActivePlusDetectedSet MaxNumberOfReportingCellsType3, allActivePlusMonitoredAndOrDetectedSet MaxNumberOfReportingCellsType3, withinVirtualActSet MaxNumberOfReportingCellsType1, withinMonitoredSetNonUsedFreq MaxNumberOfReportingCellsType1, withinMonitoredAndOrVirtualActiveSetNonUsedFreq MaxNumberOfReportingCellsType1, allVirtualActSetplusMonitoredSetNonUsedFreq MaxNumberOfReportingCellsType3, withinActSetOrVirtualActSet-InterRATcells MaxNumberOfReportingCellsType2, withinActSetAndOrMonitoredUsedFreqOrVirtualActSetAndOrMonitoredNonUsedFreq MaxNumberOfReportingCellsType2 } ReportingCellStatusOpt ::= reportingCellStatus } SEQUENCE { ReportingCellStatus
OPTIONAL
ReportingInfoForCellDCH ::= intraFreqReportingQuantity measurementReportingMode reportCriteria } ReportingInfoForCellDCH-LCR-r4 ::= intraFreqReportingQuantity measurementReportingMode reportCriteria } ReportingInterval ::=
SEQUENCE { IntraFreqReportingQuantity, MeasurementReportingMode, CellDCH-ReportCriteria
SEQUENCE { IntraFreqReportingQuantity, MeasurementReportingMode, CellDCH-ReportCriteria-LCR-r4
ENUMERATED { noPeriodicalreporting, ri0-25, ri0-5, ri1, ri2, ri4, ri8, ri16 }
3GPP
Release 6
957
3GPP TS 25.331 V6.23.0 (2009-09)
ReportingIntervalLong ::=
ENUMERATED { ril0, ril0-25, ril0-5, ril1, ril2, ril3, ril4, ril6, ril8, ril12, ril16, ril20, ril24, ril28, ril32, ril64 } -- When the value ril0 is used, the UE behaviour is not -- defined.
-- Actual value ReportingRange = IE value * 0.5 ReportingRange ::= INTEGER (0..29) RL-AdditionInfoList ::= SEQUENCE (SIZE (1..maxRL)) OF PrimaryCPICH-Info SEQUENCE { RL-AdditionInfoList RL-RemovalInformationList
RL-InformationLists ::= rl-AdditionInfoList rL-RemovalInformationList } RLC-BuffersPayload ::=
OPTIONAL, OPTIONAL
ENUMERATED { pl0, pl4, pl8, pl16, pl32, pl64, pl128, pl256, pl512, pl1024, pl2k, pl4k, pl8k, pl16k, pl32k, pl64k, pl128k, pl256k, pl512k, pl1024k, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }
-- Actual value RRC = IE value * 0.032 RRC ::= INTEGER (-127..127) SatData ::= satID iode } SatDataList ::= SEQUENCE{ SatID, IODE
SEQUENCE (SIZE (0..maxSat)) OF SatData ENUMERATED { ns-NN-U, es-SN, es-NN-U, rev2, rev }
SatelliteStatus ::=
-- Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in [12]. SatID ::= INTEGER (0..63) SFN-Offset-Validity ::= SFN-SFN-Drift ::= ENUMERATED { false } ENUMERATED { sfnsfndrift0, sfnsfndrift1, sfnsfndrift2, sfnsfndrift3, sfnsfndrift4, sfnsfndrift5, sfnsfndrift8, sfnsfndrift10, sfnsfndrift15, sfnsfndrift25, sfnsfndrift35, sfnsfndrift50, sfnsfndrift65, sfnsfndrift80, sfnsfndrift100, sfnsfndrift-1, sfnsfndrift-2, sfnsfndrift-3, sfnsfndrift-4, sfnsfndrift-5, sfnsfndrift-8, sfnsfndrift-10, sfnsfndrift-15, sfnsfndrift-25, sfnsfndrift-35, sfnsfndrift-50, sfnsfndrift-65, sfnsfndrift-80, sfnsfndrift-100} CHOICE { SFN-SFN-ObsTimeDifference1, SFN-SFN-ObsTimeDifference2
SFN-SFN-ObsTimeDifference ::= type1 type2 }
-- SPARE: SFN-SFN-ObsTimeDifference1, Max = 9830399 -- For 1.28Mcps TDD, Max value of SFN-SFN-ObsTimeDifference1 is 3276799. -- Values above Max are spare SFN-SFN-ObsTimeDifference1 ::= INTEGER (0..16777215) -- SPARE: SFN-SFN-ObsTimeDifference2, Max = 40961 -- For 1.28Mcps TDD, Max value of SFN-SFN-ObsTimeDifference2 is 27649. -- Values above Max are spare SFN-SFN-ObsTimeDifference2 ::= INTEGER (0..65535)
3GPP
Release 6
958
3GPP TS 25.331 V6.23.0 (2009-09)
SFN-SFN-OTD-Type ::=
ENUMERATED { noReport, type1, type2 } SEQUENCE { INTEGER (0 .. 4095), INTEGER (0.. 38399)
SFN-SFN-RelTimeDifference1 ::= sfn-Offset sfn-sfn-Reltimedifference } SFN-TOW-Uncertainty ::=
ENUMERATED { lessThan10, moreThan10 }
SIR ::=
INTEGER (0..63)
SIR-MeasurementList ::=
SEQUENCE (SIZE (1..maxCCTrCH)) OF SIR-MeasurementResults
SIR-MeasurementResults ::= tfcs-ID sir-TimeslotList } SIR-TFCS ::=
SEQUENCE { TFCS-IdentityPlain, SIR-TimeslotList
TFCS-IdentityPlain
SIR-TFCS-List ::=
SEQUENCE (SIZE (1..maxCCTrCH)) OF SIR-TFCS SEQUENCE (SIZE (1..maxTS)) OF SIR GPS navigation message (23)), (24)), (24)), (16))
SIR-TimeslotList ::=
-- SubFrame1Reserved, reserved bits in subframe 1 of the SubFrame1Reserved ::= SEQUENCE { reserved1 BIT STRING (SIZE reserved2 BIT STRING (SIZE reserved3 BIT STRING (SIZE reserved4 BIT STRING (SIZE } T-ADVinfo ::= t-ADV sfn } T-CRMax ::= notUsed t30 t60 t120 t180 t240 } T-CRMaxHyst ::=
SEQUENCE { INTEGER(0..2047), INTEGER(0..4095)
CHOICE { NULL, N-CR-T-CRMaxHyst, N-CR-T-CRMaxHyst, N-CR-T-CRMaxHyst, N-CR-T-CRMaxHyst, N-CR-T-CRMaxHyst
ENUMERATED { notUsed, t10, t20, t30, t40, t50, t60, t70 } ENUMERATED { to3, to6, to9, to12, to15, to18, to21, infinite } ENUMERATED { to2, to3, to4, to6, to8, to10, to12, infinite } SEQUENCE { TemporaryOffset1, TemporaryOffset2
TemporaryOffset1 ::=
TemporaryOffset2 ::=
TemporaryOffsetList ::= temporaryOffset1 temporaryOffset2 } Threshold ::=
INTEGER (-115..0)
3GPP
Release 6
Threshold-r6 ::=
959
INTEGER (-120..0)
3GPP TS 25.331 V6.23.0 (2009-09)
-- The order of the list corresponds to the order of frequency defined in Inter-FreqEventCriteria ThreholdNonUsedFrequency-deltaList ::= SEQUENCE (SIZE (1..maxFreq)) OF DeltaRSCPPerCell ThresholdPositionChange ::= ENUMERATED { pc10, pc20, pc30, pc40, pc50, pc100, pc200, pc300, pc500, pc1000, pc2000, pc5000, pc10000, pc20000, pc50000, pc100000 } ENUMERATED { ms1, ms2, ms3, ms5, ms10, ms20, ms50, ms100 } ENUMERATED { c0-25, c0-5, c1, c2, c3, c4, c5, c10, c20, c50, c100, c200, c500, c1000, c2000, c5000 } INTEGER (-115..165) INTEGER (-120..165)
ThresholdSFN-GPS-TOW ::=
ThresholdSFN-SFN-Change ::=
ThresholdUsedFrequency ::= ThresholdUsedFrequency-r6 ::=
-- Actual value TimeInterval = IE value * 20. TimeInterval ::= INTEGER (1..13)
TimeslotInfo ::= timeslotNumber burstType } TimeslotInfo-LCR-r4 ::= timeslotNumber } TimeslotInfoList ::=
SEQUENCE { TimeslotNumber, BurstType
SEQUENCE { TimeslotNumber-LCR-r4
SEQUENCE (SIZE (1..maxTS)) OF TimeslotInfo SEQUENCE (SIZE (1..maxTS-LCR)) OF TimeslotInfo-LCR-r4 CHOICE { SEQUENCE (SIZE (1..maxTS)) OF TimeslotInfo, SEQUENCE (SIZE (1..maxTS-LCR)) OF TimeslotInfo-LCR-r4
TimeslotInfoList-LCR-r4 ::=
TimeslotInfoList-r4 ::= tdd384 tdd128 } -- SPARE: TimeslotISCP, Max = 91 -- Values above Max are spare TimeslotISCP ::=
INTEGER (0..127)
-- TimeslotISCP-List shall not include more than 6 elements in 1.28Mcps TDD mode. TimeslotISCP-List ::= SEQUENCE (SIZE (1..maxTS)) OF TimeslotISCP TimeslotListWithISCP ::= SEQUENCE (SIZE (1..maxTS)) OF TimeslotWithISCP SEQUENCE { TimeslotNumber, TimeslotISCP
TimeslotWithISCP ::= timeslot timeslotISCP } TimeToTrigger ::=
ENUMERATED { ttt0, ttt10, ttt20, ttt40, ttt60, ttt80, ttt100, ttt120, ttt160, ttt200, ttt240, tt320, ttt640, ttt1280, ttt2560, ttt5000 } SEQUENCE { TrafficVolumeEventType, TrafficVolumeThreshold, TimeToTrigger
TrafficVolumeEventParam ::= eventID reportingThreshold timeToTrigger
OPTIONAL,
3GPP
Release 6
pendingTimeAfterTrigger tx-InterruptionAfterTrigger }
960
PendingTimeAfterTrigger TX-InterruptionAfterTrigger
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL, OPTIONAL
TrafficVolumeEventResults ::= SEQUENCE { ul-transportChannelCausingEvent UL-TrCH-Identity, trafficVolumeEventIdentity TrafficVolumeEventType } TrafficVolumeEventType ::= ENUMERATED { e4a, e4b } CHOICE { NULL, TimeInterval, TimeInterval
TrafficVolumeMeasQuantity ::= rlc-BufferPayload averageRLC-BufferPayload varianceOfRLC-BufferPayload }
TrafficVolumeMeasSysInfo ::= SEQUENCE { trafficVolumeMeasurementID MeasurementIdentity DEFAULT trafficVolumeMeasurementObjectList TrafficVolumeMeasurementObjectList trafficVolumeMeasQuantity TrafficVolumeMeasQuantity trafficVolumeReportingQuantity TrafficVolumeReportingQuantity -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy TrafficVolumeReportingCriteria measurementValidity MeasurementValidity measurementReportingMode MeasurementReportingMode, reportCriteriaSysInf TrafficVolumeReportCriteriaSysInfo } TrafficVolumeMeasuredResults ::= rb-Identity rlc-BuffersPayload averageRLC-BufferPayload varianceOfRLC-BufferPayload } SEQUENCE { RB-Identity, RLC-BuffersPayload AverageRLC-BufferPayload VarianceOfRLC-BufferPayload
4, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
TrafficVolumeMeasuredResultsList ::= SEQUENCE (SIZE (1..maxRB)) OF TrafficVolumeMeasuredResults TrafficVolumeMeasurement ::= SEQUENCE { trafficVolumeMeasurementObjectList TrafficVolumeMeasurementObjectList trafficVolumeMeasQuantity TrafficVolumeMeasQuantity trafficVolumeReportingQuantity TrafficVolumeReportingQuantity measurementValidity MeasurementValidity reportCriteria TrafficVolumeReportCriteria } TrafficVolumeMeasurementObjectList ::= SEQUENCE (SIZE (1..maxTrCH)) OF UL-TrCH-Identity TrafficVolumeReportCriteria ::= trafficVolumeReportingCriteria periodicalReportingCriteria noReporting } CHOICE { TrafficVolumeReportingCriteria, PeriodicalReportingCriteria, NULL
TrafficVolumeReportCriteriaSysInfo ::= trafficVolumeReportingCriteria periodicalReportingCriteria }
CHOICE { TrafficVolumeReportingCriteria, PeriodicalReportingCriteria
TrafficVolumeReportingCriteria ::= SEQUENCE { -- NOTE: transChCriteriaList should be mandatory in later versions of this message transChCriteriaList TransChCriteriaList OPTIONAL } TrafficVolumeReportingQuantity ::= SEQUENCE { rlc-RB-BufferPayload BOOLEAN, rlc-RB-BufferPayloadAverage BOOLEAN, rlc-RB-BufferPayloadVariance BOOLEAN } TrafficVolumeThreshold ::= ENUMERATED { th8, th16, th32, th64, th128,
3GPP
Release 6
961
3GPP TS 25.331 V6.23.0 (2009-09)
th256, th512, th1024, th2k, th3k, th4k, th6k, th8k, th12k, th16k, th24k, th32k, th48k, th64k, th96k, th128k, th192k, th256k, th384k, th512k, th768k } TransChCriteria ::= ul-transportChannelID eventSpecificParameters } TransChCriteriaList ::= SEQUENCE (SIZE (1..maxTrCH)) OF TransChCriteria ENUMERATED { acknowledgedModeRLC, unacknowledgedModeRLC } INTEGER (-50..33) ENUMERATED { activeSetCellsOnly, monitoredSetCellsOnly, activeSetAndMonitoredSetCells } ENUMERATED { activeSetCellsOnly, monitoredSetCellsOnly, activeSetAndMonitoredSetCells, detectedSetCellsOnly, detectedSetAndMonitoredSetCells } ENUMERATED { txiat0-25, txiat0-5, txiat1, txiat2, txiat4, txiat8, txiat16 } ENUMERATED { lessThan1, between1-and-4, between4-and-8, over8 } SEQUENCE { TimeToTrigger, TransmittedPowerThreshold SEQUENCE { UL-TrCH-Identity OPTIONAL, SEQUENCE (SIZE (1..maxMeasParEvent)) OF TrafficVolumeEventParam OPTIONAL
TransferMode ::=
TransmittedPowerThreshold ::= TriggeringCondition1 ::=
TriggeringCondition2 ::=
TX-InterruptionAfterTrigger ::=
UDRE ::=
UE-6AB-Event ::= timeToTrigger transmittedPowerThreshold }
UE-6FG-Event ::= SEQUENCE { timeToTrigger TimeToTrigger, -- in 1.28 Mcps TDD ue-RX-TX-TimeDifferenceThreshold corresponds to TADV Threshold ue-RX-TX-TimeDifferenceThreshold UE-RX-TX-TimeDifferenceThreshold } -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received the UE behaviour is not specified. UE-AutonomousUpdateMode ::= CHOICE { dummy NULL, onWithNoReporting NULL, dummy2 RL-InformationLists } UE-InternalEventParam ::= event6a event6b event6c event6d event6e event6f event6g } UE-InternalEventParamList ::= CHOICE { UE-6AB-Event, UE-6AB-Event, TimeToTrigger, TimeToTrigger, TimeToTrigger, UE-6FG-Event, UE-6FG-Event
SEQUENCE (SIZE (1..maxMeasEvent)) OF UE-InternalEventParam CHOICE { NULL, NULL,
UE-InternalEventResults ::= event6a event6b
3GPP
Release 6
event6c event6d event6e event6f event6g spare } UE-InternalMeasQuantity ::= measurementQuantity filterCoefficient }
962
NULL, NULL, NULL, PrimaryCPICH-Info, PrimaryCPICH-Info, NULL
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { UE-MeasurementQuantity, FilterCoefficient
DEFAULT fc0
UE-InternalMeasuredResults ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { ue-TransmittedPowerFDD UE-TransmittedPower ue-RX-TX-ReportEntryList UE-RX-TX-ReportEntryList }, tdd SEQUENCE { ue-TransmittedPowerTDD-List UE-TransmittedPowerTDD-List appliedTA UL-TimingAdvance } } } UE-InternalMeasuredResults-LCR-r4 ::= ue-TransmittedPowerTDD-List t-ADVinfo } UE-InternalMeasurement ::= ue-InternalMeasQuantity ue-InternalReportingQuantity reportCriteria } UE-InternalMeasurement-r4 ::= ue-InternalMeasQuantity ue-InternalReportingQuantity reportCriteria } UE-InternalMeasurementSysInfo ::= ue-InternalMeasurementID ue-InternalMeasQuantity } UE-InternalReportCriteria ::= ue-InternalReportingCriteria periodicalReportingCriteria noReporting } UE-InternalReportingCriteria ::= ue-InternalEventParamList } SEQUENCE { UE-TransmittedPowerTDD-List T-ADVinfo
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
OPTIONAL, OPTIONAL
SEQUENCE { UE-InternalMeasQuantity UE-InternalReportingQuantity UE-InternalReportCriteria
OPTIONAL, OPTIONAL,
SEQUENCE { UE-InternalMeasQuantity UE-InternalReportingQuantity-r4 UE-InternalReportCriteria
OPTIONAL, OPTIONAL,
SEQUENCE { MeasurementIdentity UE-InternalMeasQuantity
DEFAULT 5,
CHOICE { UE-InternalReportingCriteria, PeriodicalReportingCriteria, NULL
SEQUENCE { UE-InternalEventParamList
OPTIONAL
UE-InternalReportingQuantity ::= SEQUENCE { ue-TransmittedPower BOOLEAN, modeSpecificInfo CHOICE { fdd SEQUENCE { ue-RX-TX-TimeDifference BOOLEAN }, tdd SEQUENCE { appliedTA BOOLEAN } } } UE-InternalReportingQuantity-r4 ::= SEQUENCE { ue-TransmittedPower BOOLEAN, modeSpecificInfo CHOICE { fdd SEQUENCE { ue-RX-TX-TimeDifference BOOLEAN }, tdd SEQUENCE { tddOption CHOICE {
3GPP
Release 6
tdd384 appliedTA }, tdd128 t-ADVinfo } } } } }
963
SEQUENCE { BOOLEAN SEQUENCE { BOOLEAN
3GPP TS 25.331 V6.23.0 (2009-09)
-- TABULAR: UE-MeasurementQuantity, for 3.84 Mcps TDD only the first two values -- ue-TransmittedPower and utra-Carrier-RSSI are used. -- For 1.28 Mcps TDD ue-RX-TX-TimeDifference corresponds to T-ADV in the tabular UE-MeasurementQuantity ::= ENUMERATED { ue-TransmittedPower, utra-Carrier-RSSI, ue-RX-TX-TimeDifference } UE-RX-TX-ReportEntry ::= primaryCPICH-Info ue-RX-TX-TimeDifferenceType1 } UE-RX-TX-ReportEntryList ::= SEQUENCE { PrimaryCPICH-Info, UE-RX-TX-TimeDifferenceType1
SEQUENCE (SIZE (1..maxRL)) OF UE-RX-TX-ReportEntry
-- SPARE: UE-RX-TX-TimeDifferenceType1, Max = 1280 -- Values above Max are spare UE-RX-TX-TimeDifferenceType1 ::= INTEGER (768..1791)
UE-RX-TX-TimeDifferenceType2 ::=
INTEGER (0..8191) SEQUENCE { UE-RX-TX-TimeDifferenceType2, NeighbourQuality
UE-RX-TX-TimeDifferenceType2Info ::= ue-RX-TX-TimeDifferenceType2 neighbourQuality }
-- In 1.28 Mcps TDD, actual value for -- T-ADV Threshold = (UE-RX-TX-TimeDifferenceThreshold - 768) * 0.125 UE-RX-TX-TimeDifferenceThreshold ::= INTEGER (768..1280) UE-TransmittedPower ::= UE-TransmittedPowerTDD-List ::= INTEGER (0..104) SEQUENCE (SIZE (1..maxTS)) OF UE-TransmittedPower
UL-TrCH-Identity ::= CHOICE{ dch TransportChannelIdentity, -- Note: the reference to CPCH in the element name below is incorrect. The name is not changed -- to keep it aligned with R99. rachorcpch NULL, usch TransportChannelIdentity } UE-Positioning-Accuracy ::= BIT STRING (SIZE (7))
UE-Positioning-CipherParameters ::= cipheringKeyFlag cipheringSerialNumber }
SEQUENCE { BIT STRING (SIZE (1)), INTEGER (0..65535)
UE-Positioning-Error ::= SEQUENCE { errorReason UE-Positioning-ErrorCause, ue-positioning-GPS-additionalAssistanceDataRequest UE-Positioning-GPSAdditionalAssistanceDataRequest OPTIONAL } UE-Positioning-ErrorCause ::= ENUMERATED { notEnoughOTDOA-Cells, notEnoughGPS-Satellites, assistanceDataMissing, notAccomplishedGPS-TimingOfCellFrames, undefinedError, requestDeniedByUser, notProcessedAndTimeout,
3GPP
Release 6
964
referenceCellNotServingCell }
3GPP TS 25.331 V6.23.0 (2009-09)
UE-Positioning-EventParam ::= reportingAmount reportFirstFix measurementInterval eventSpecificInfo } UE-Positioning-EventParamList ::=
SEQUENCE { ReportingAmount, BOOLEAN, UE-Positioning-MeasurementInterval, UE-Positioning-EventSpecificInfo
SEQUENCE (SIZE (1..maxMeasEvent)) OF UE-Positioning-EventParam CHOICE { ThresholdPositionChange, ThresholdSFN-SFN-Change, ThresholdSFN-GPS-TOW
UE-Positioning-EventSpecificInfo ::= e7a e7b e7c }
UE-Positioning-GPS-AcquisitionAssistance ::= SEQUENCE { gps-ReferenceTime INTEGER (0..604799999), utran-GPSReferenceTime UTRAN-GPSReferenceTime satelliteInformationList AcquisitionSatInfoList }
OPTIONAL,
UE-Positioning-GPS-AdditionalAssistanceDataRequest ::= SEQUENCE { almanacRequest BOOLEAN, utcModelRequest BOOLEAN, ionosphericModelRequest BOOLEAN, navigationModelRequest BOOLEAN, dgpsCorrectionsRequest BOOLEAN, referenceLocationRequest BOOLEAN, referenceTimeRequest BOOLEAN, aquisitionAssistanceRequest BOOLEAN, realTimeIntegrityRequest BOOLEAN, navModelAddDataRequest UE-Positioning-GPS-NavModelAddDataReq } UE-Positioning-GPS-Almanac ::= wn-a almanacSatInfoList sv-GlobalHealth } SEQUENCE { BIT STRING (SIZE (8)), AlmanacSatInfoList, BIT STRING (SIZE (364))
OPTIONAL
OPTIONAL
UE-Positioning-GPS-AssistanceData ::= SEQUENCE { ue-positioning-GPS-ReferenceTime UE-Positioning-GPS-ReferenceTime OPTIONAL, ue-positioning-GPS-ReferenceLocation ReferenceLocation OPTIONAL, ue-positioning-GPS-DGPS-Corrections UE-Positioning-GPS-DGPS-Corrections OPTIONAL, ue-positioning-GPS-NavigationModel UE-Positioning-GPS-NavigationModel OPTIONAL, ue-positioning-GPS-IonosphericModel UE-Positioning-GPS-IonosphericModel OPTIONAL, ue-positioning-GPS-UTC-Model UE-Positioning-GPS-UTC-Model OPTIONAL, ue-positioning-GPS-Almanac UE-Positioning-GPS-Almanac OPTIONAL, ue-positioning-GPS-AcquisitionAssistance UE-Positioning-GPS-AcquisitionAssistance OPTIONAL, ue-positioning-GPS-Real-timeIntegrity BadSatList OPTIONAL, -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy UE-Positioning-GPS-ReferenceCellInfo OPTIONAL } UE-Positioning-GPS-DGPS-Corrections ::= SEQUENCE { gps-TOW INTEGER (0..604799), statusHealth DiffCorrectionStatus, dgps-CorrectionSatInfoList DGPS-CorrectionSatInfoList } UE-Positioning-GPS-IonosphericModel ::= SEQUENCE { alfa0 BIT STRING (SIZE (8)), alfa1 BIT STRING (SIZE (8)), alfa2 BIT STRING (SIZE (8)), alfa3 BIT STRING (SIZE (8)), beta0 BIT STRING (SIZE (8)), beta1 BIT STRING (SIZE (8)),
3GPP
Release 6
beta2 beta3 }
965
BIT STRING (SIZE (8)), BIT STRING (SIZE (8))
3GPP TS 25.331 V6.23.0 (2009-09)
UE-Positioning-GPS-MeasurementResults ::= SEQUENCE { referenceTime CHOICE { utran-GPSReferenceTimeResult UTRAN-GPSReferenceTimeResult, gps-ReferenceTimeOnly INTEGER (0..604799999) }, gps-MeasurementParamList GPS-MeasurementParamList } UE-Positioning-GPS-NavigationModel ::= navigationModelSatInfoList } SEQUENCE { NavigationModelSatInfoList
UE-Positioning-GPS-NavModelAddDataReq ::= SEQUENCE { gps-Week INTEGER (0..1023), -- SPARE: gps-Toe, Max = 167 -- Values above Max are spare gps-Toe INTEGER (0..255), -- SPARE: tToeLimit, Max = 10 -- Values above Max are spare tToeLimit INTEGER (0..15), satDataList SatDataList } UE-Positioning-GPS-ReferenceCellInfo ::= SEQUENCE{ modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info }, tdd SEQUENCE { referenceIdentity CellParametersID } } } UE-Positioning-GPS-ReferenceTime ::= SEQUENCE { gps-Week INTEGER (0..1023), gps-tow-1msec GPS-TOW-1msec, utran-GPSReferenceTime GPSReferenceTime OPTIONAL, sfn-tow-Uncertainty SFN-TOW-Uncertainty OPTIONAL, utran-GPS-DriftRate UTRAN-GPS-DriftRate OPTIONAL, gps-TOW-AssistList GPS-TOW-AssistList OPTIONAL } UE-Positioning-GPS-UTC-Model ::= a1 a0 t-ot wn-t delta-t-LS wn-lsf dn delta-t-LSF } UE-Positioning-IPDL-Parameters ::= ip-Spacing ip-Length ip-Offset seed burstModeParameters } UE-Positioning-IPDL-Parameters-r4 ::= modeSpecificInfo fdd ip-Spacing ip-Length ip-Offset seed }, tdd ip-Spacing-TDD ip-slot ip-Start SEQUENCE STRING (SIZE STRING (SIZE STRING (SIZE STRING (SIZE STRING (SIZE STRING (SIZE STRING (SIZE STRING (SIZE { (24)), (32)), (8)), (8)), (8)), (8)), (8)), (8))
UTRAN-
BIT BIT BIT BIT BIT BIT BIT BIT
SEQUENCE { IP-Spacing, IP-Length, INTEGER (0..9), INTEGER (0..63), BurstModeParameters
OPTIONAL
SEQUENCE { CHOICE { SEQUENCE { IP-Spacing, IP-Length, INTEGER (0..9), INTEGER (0..63) SEQUENCE { IP-Spacing-TDD, INTEGER (0..14), INTEGER (0..4095),
3GPP
Release 6
ip-PCCPCG } }, burstModeParameters }
966
IP-PCCPCH-r4
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
BurstModeParameters
OPTIONAL
UE-Positioning-IPDL-Parameters-TDD-r4-ext ::= SEQUENCE { ip-Spacing IP-Spacing-TDD, ip-slot INTEGER (0..14), ip-Start INTEGER (0..4095), ip-PCCPCG IP-PCCPCH-r4 burstModeParameters BurstModeParameters } UE-Positioning-MeasuredResults ::= ue-positioning-OTDOA-Measurement OPTIONAL, ue-positioning-PositionEstimateInfo OPTIONAL, ue-positioning-GPS-Measurement OPTIONAL, ue-positioning-Error OPTIONAL } UE-Positioning-MeasuredResults-v390ext ::= ue-Positioning-OTDOA-Measurement-v390ext }
OPTIONAL,
SEQUENCE { UE-Positioning-OTDOA-Measurement UE-Positioning-PositionEstimateInfo UE-Positioning-GPS-MeasurementResults UE-Positioning-Error
SEQUENCE { UE-Positioning-OTDOA-Measurement-v390ext
UE-Positioning-Measurement ::= SEQUENCE { ue-positioning-ReportingQuantity UE-Positioning-ReportingQuantity, reportCriteria UE-Positioning-ReportCriteria, ue-positioning-OTDOA-AssistanceData UE-Positioning-OTDOA-AssistanceData OPTIONAL, ue-positioning-GPS-AssistanceData UE-Positioning-GPS-AssistanceData OPTIONAL } UE-Positioning-Measurement-v390ext ::= SEQUENCE { ue-positioning-ReportingQuantity-v390ext UE-Positioning-ReportingQuantity-v390ext OPTIONAL, measurementValidity MeasurementValidity OPTIONAL, ue-positioning-OTDOA-AssistanceData-UEB UE-Positioning-OTDOA-AssistanceData-UEB OPTIONAL } UE-Positioning-Measurement-r4 ::= ue-positioning-ReportingQuantity measurementValidity OPTIONAL, reportCriteria ue-positioning-OTDOA-AssistanceData OPTIONAL, ue-positioning-GPS-AssistanceData OPTIONAL } SEQUENCE { UE-Positioning-ReportingQuantity-r4, MeasurementValidity UE-Positioning-ReportCriteria, UE-Positioning-OTDOA-AssistanceData-r4 UE-Positioning-GPS-AssistanceData
UE-Positioning-MeasurementEventResults ::= CHOICE { event7a UE-Positioning-PositionEstimateInfo, event7b UE-Positioning-OTDOA-Measurement, event7c UE-Positioning-GPS-MeasurementResults, spare NULL } UE-Positioning-MeasurementInterval ::= ENUMERATED { e5, e15, e60, e300, e900, e1800, e3600, e7200 } ENUMERATED { ue-Assisted, ue-Based, ue-BasedPreferred, ue-AssistedPreferred } SEQUENCE { UE-Positioning-OTDOA-ReferenceCellInfo
UE-Positioning-MethodType ::=
UE-Positioning-OTDOA-AssistanceData ::= ue-positioning-OTDOA-ReferenceCellInfo OPTIONAL,
3GPP
Release 6
ue-positioning-OTDOA-NeighbourCellList OPTIONAL } UE-Positioning-OTDOA-AssistanceData-r4 ::= ue-positioning-OTDOA-ReferenceCellInfo OPTIONAL, ue-positioning-OTDOA-NeighbourCellList OPTIONAL }
967
3GPP TS 25.331 V6.23.0 (2009-09)

UE-Positioning-OTDOA-NeighbourCellList
SEQUENCE { UE-Positioning-OTDOA-ReferenceCellInfo-r4 UE-Positioning-OTDOA-NeighbourCellList-r4
UE-Positioning-OTDOA-AssistanceData-r4ext ::= SEQUENCE { -- In case of TDD these IPDL parameters shall be used for the reference cell instead of -- IPDL Parameters in IE UE-Positioning-OTDOA-ReferenceCellInfo ue-Positioning-IPDL-Parameters-TDD-r4-ext UE-Positioning-IPDL-Parameters-TDD-r4-ext OPTIONAL, -- These IPDL parameters shall be used for the neighbour cells in case of TDD instead of -- IPDL Parameters in IE UE-Positioning-OTDOA-NeighbourCellInfoList. The cells shall be -- listed in the same order as in IE UE-Positioning-OTDOA-NeighbourCellInfoList ue-Positioning-IPDL-Parameters-TDDList-r4-ext UE-Positioning-IPDL-Parameters-TDDList-r4-ext OPTIONAL } UE-Positioning-OTDOA-AssistanceData-UEB ::= ue-positioning-OTDOA-ReferenceCellInfo-UEB OPTIONAL, ue-positioning-OTDOA-NeighbourCellList-UEB UEB OPTIONAL } SEQUENCE { UE-Positioning-OTDOA-ReferenceCellInfo-UEB UE-Positioning-OTDOA-NeighbourCellList-
UE-Positioning-IPDL-Parameters-TDDList-r4-ext ::= SEQUENCE (SIZE (1..maxCellMeas)) OF UE-Positioning-IPDL-Parameters-TDD-r4-ext UE-Positioning-OTDOA-Measurement ::= SEQUENCE { sfn INTEGER (0..4095), modeSpecificInfo CHOICE { fdd SEQUENCE { referenceCellIDentity PrimaryCPICH-Info, ue-RX-TX-TimeDifferenceType2Info UE-RX-TX-TimeDifferenceType2Info }, tdd SEQUENCE { referenceCellIdentity CellParametersID } }, neighbourList NeighbourList OPTIONAL } UE-Positioning-OTDOA-Measurement-v390ext ::= neighbourList-v390ext } SEQUENCE { NeighbourList-v390ext
UE-Positioning-OTDOA-NeighbourCellInfo ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } }, frequencyInfo FrequencyInfo OPTIONAL, ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters OPTIONAL, sfn-SFN-RelTimeDifference SFN-SFN-RelTimeDifference1, sfn-SFN-Drift SFN-SFN-Drift OPTIONAL, searchWindowSize OTDOA-SearchWindowSize, positioningMode CHOICE{ ueBased SEQUENCE {}, ueAssisted SEQUENCE {} } } UE-Positioning-OTDOA-NeighbourCellInfo-r4 ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{
3GPP
Release 6
cellAndChannelIdentity }
968
CellAndChannelIdentity
3GPP TS 25.331 V6.23.0 (2009-09)
}, frequencyInfo FrequencyInfo ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters-r4 sfn-SFN-RelTimeDifference SFN-SFN-RelTimeDifference1, sfn-Offset-Validity SFN-Offset-Validity sfn-SFN-Drift SFN-SFN-Drift searchWindowSize OTDOA-SearchWindowSize, positioningMode CHOICE { ueBased SEQUENCE { relativeNorth INTEGER (-20000..20000) relativeEast INTEGER (-20000..20000) relativeAltitude INTEGER (-4000..4000) fineSFN-SFN FineSFN-SFN -- actual value roundTripTime = (IE value * 0.0625) + 876 roundTripTime INTEGER (0.. 32766) }, ueAssisted SEQUENCE {} } } UE-Positioning-OTDOA-NeighbourCellInfo-UEB ::= SEQUENCE { modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } }, frequencyInfo FrequencyInfo ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters sfn-SFN-RelTimeDifference SFN-SFN-RelTimeDifference1, sfn-SFN-Drift SFN-SFN-Drift searchWindowSize OTDOA-SearchWindowSize, relativeNorth INTEGER (-20000..20000) relativeEast INTEGER (-20000..20000) relativeAltitude INTEGER (-4000..4000) fineSFN-SFN FineSFN-SFN, -- actual value roundTripTime = (IE value * 0.0625) + 876 roundTripTime INTEGER (0..32766) }
OPTIONAL
UE-Positioning-OTDOA-NeighbourCellList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF UE-Positioning-OTDOA-NeighbourCellInfo UE-Positioning-OTDOA-NeighbourCellList-r4 ::= SEQUENCE (SIZE (1..maxCellMeas)) OF UE-Positioning-OTDOA-NeighbourCellInfo-r4 UE-Positioning-OTDOA-NeighbourCellList-UEB ::= SEQUENCE (SIZE (1..maxCellMeas)) OF UE-Positioning-OTDOA-NeighbourCellInfo-UEB UE-Positioning-OTDOA-Quality ::= stdResolution numberOfOTDOA-Measurements stdOfOTDOA-Measurements } SEQUENCE { BIT STRING (SIZE (2)), BIT STRING (SIZE (3)), BIT STRING (SIZE (5))
UE-Positioning-OTDOA-ReferenceCellInfo ::= SEQUENCE { sfn INTEGER (0..4095) OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } }, frequencyInfo FrequencyInfo OPTIONAL, positioningMode CHOICE { ueBased SEQUENCE {}, ueAssisted SEQUENCE {} }, ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters OPTIONAL }
3GPP
Release 6
969
3GPP TS 25.331 V6.23.0 (2009-09)
UE-Positioning-OTDOA-ReferenceCellInfo-r4 ::= SEQUENCE { sfn INTEGER (0..4095) OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } }, frequencyInfo FrequencyInfo OPTIONAL, positioningMode CHOICE { ueBased SEQUENCE { cellPosition ReferenceCellPosition OPTIONAL, -- actual value roundTripTime = (IE value * 0.0625) + 876 roundTripTime INTEGER (0..32766) OPTIONAL }, ueAssisted SEQUENCE {} }, ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters-r4 OPTIONAL } UE-Positioning-OTDOA-ReferenceCellInfo-UEB ::= SEQUENCE { sfn INTEGER (0..4095) modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } }, frequencyInfo FrequencyInfo cellPosition ReferenceCellPosition -- actual value roundTripTime = (IE value * 0.0625) + 876 roundTripTime INTEGER (0..32766) ue-positioning-IPDL-Paremeters UE-Positioning-IPDL-Parameters }
OPTIONAL,
UE-Positioning-PositionEstimateInfo ::= SEQUENCE { referenceTime CHOICE { utran-GPSReferenceTimeResult UTRAN-GPSReferenceTimeResult, gps-ReferenceTimeOnly INTEGER (0..604799999), cell-Timing SEQUENCE { sfn INTEGER (0..4095), modeSpecificInfo CHOICE { fdd SEQUENCE { primaryCPICH-Info PrimaryCPICH-Info }, tdd SEQUENCE{ cellAndChannelIdentity CellAndChannelIdentity } } } }, positionEstimate PositionEstimate } UE-Positioning-ReportCriteria ::= ue-positioning-ReportingCriteria periodicalReportingCriteria noReporting } CHOICE { UE-Positioning-EventParamList, PeriodicalReportingCriteria, NULL
UE-Positioning-ReportingQuantity ::= SEQUENCE { methodType UE-Positioning-MethodType, positioningMethod PositioningMethod, -- dummy1 is not used in this version of specification and it should -- be ignored. dummy1 UE-Positioning-ResponseTime, horizontal-Accuracy UE-Positioning-Accuracy gps-TimingOfCellWanted BOOLEAN, -- dummy2 is not used in this version of specification and it should -- be ignored. dummy2 BOOLEAN, additionalAssistanceDataRequest BOOLEAN, environmentCharacterisation EnvironmentCharacterisation
OPTIONAL,
OPTIONAL
3GPP
Release 6
} UE-Positioning-ReportingQuantity-v390ext ::= vertical-Accuracy }
970
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { UE-Positioning-Accuracy
UE-Positioning-ReportingQuantity-r4 ::= SEQUENCE { methodType UE-Positioning-MethodType, positioningMethod PositioningMethod, horizontalAccuracy UE-Positioning-Accuracy verticalAccuracy UE-Positioning-Accuracy gps-TimingOfCellWanted BOOLEAN, additionalAssistanceDataReq BOOLEAN, environmentCharacterisation EnvironmentCharacterisation } UE-Positioning-ResponseTime ::= ENUMERATED { s1, s2, s4, s8, s16, s32, s64, s128 }
OPTIONAL, OPTIONAL,
OPTIONAL
-- SPARE: UTRA-CarrierRSSI, Max = 76 -- Values above Max are spare UTRA-CarrierRSSI ::= INTEGER (0..127) UTRAN-GPS-DriftRate ::= ENUMERATED { utran-GPSDrift0, utran-GPSDrift1, utran-GPSDrift2, utran-GPSDrift5, utran-GPSDrift10, utran-GPSDrift15, utran-GPSDrift25, utran-GPSDrift50, utran-GPSDrift-1, utran-GPSDrift-2, utran-GPSDrift-5, utran-GPSDrift-10, utran-GPSDrift-15, utran-GPSDrift-25, utran-GPSDrift-50}
UTRAN-GPSReferenceTime ::= SEQUENCE { -- For utran-GPSTimingOfCell values above 2322431999999 are not -- used in this version of the specification -- Actual value utran-GPSTimingOfCell = (ms-part * 4294967296) + ls-part utran-GPSTimingOfCell SEQUENCE { ms-part INTEGER (0..1023), ls-part INTEGER (0..4294967295) }, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info }, tdd SEQUENCE { referenceIdentity CellParametersID } } OPTIONAL, sfn INTEGER (0..4095) } UTRAN-GPSReferenceTimeResult ::= SEQUENCE { -- For ue-GPSTimingOfCell values above 37158911999999 are not -- used in this version of the specification -- Actual value ue-GPSTimingOfCell = (ms-part * 4294967296) + ls-part ue-GPSTimingOfCell SEQUENCE { ms-part INTEGER (0.. 16383), ls-part INTEGER (0..4294967295) }, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info }, tdd SEQUENCE { referenceIdentity CellParametersID } }, sfn INTEGER (0..4095) } VarianceOfRLC-BufferPayload ::= ENUMERATED { plv0, plv4, plv8, plv16, plv32, plv64, plv128, plv256, plv512, plv1024, plv2k, plv4k, plv8k, plv16k, spare2, spare1 }
-- Actual value W = IE value * 0.1 W ::=
INTEGER (0..20)
-- ***************************************************
3GPP
Release 6
971
3GPP TS 25.331 V6.23.0 (2009-09)
--OTHER INFORMATION ELEMENTS (10.3.8) --- *************************************************** BCC ::= BCCH-ModificationInfo ::= mib-ValueTag bcch-ModificationTime } INTEGER (0..7) SEQUENCE { MIB-ValueTag, BCCH-ModificationTime
OPTIONAL
-- Actual value BCCH-ModificationTime = IE value * 8 BCCH-ModificationTime ::= INTEGER (0..511) BSIC ::= ncc bcc } CBS-DRX-Level1Information ::= ctch-AllocationPeriod cbs-FrameOffset } SEQUENCE { NCC, BCC
SEQUENCE { INTEGER (1..256), INTEGER (0..255)
CBS-DRX-Level1Information-extension-r6 ::= CDMA2000-Message ::= msg-Type payload } CDMA2000-MessageList ::=
ENUMERATED {p8, p16, p32, p64, p128, p256}
SEQUENCE { BIT STRING (SIZE (8)), BIT STRING (SIZE (1..512))
SEQUENCE (SIZE (1..maxInterSysMessages)) OF CDMA2000-Message SEQUENCE (SIZE (1..maxNumCDMA2000Freqs)) OF FrequencyInfoCDMA2000 INTEGER (1..4)
CDMA2000-UMTS-Frequency-List ::=
CellValueTag ::= --Actual value = 2^(IE value) ExpirationTimeFactor ::=
INTEGER (1..8)
-- For each extended SIB type the value tag information is added at the end ExtSIBTypeInfoSchedulingInfo-List ::= SEQUENCE (SIZE (1..maxSIB)) OF ExtSIBTypeInfoSchedulingInfo ExtSIBTypeInfoSchedulingInfo ::= extensionSIB-Type schedulingInfo valueTagInfo } FDD-UMTS-Frequency-List ::= SEQUENCE { SIB-TypeExt, SchedulingInformation, ValueTagInfo
SEQUENCE (SIZE (1..maxNumFDDFreqs)) OF -- NOTE1: The IE "UARFCN (Nlow)" corresponds to -- "uarfcn-DL" in FrequencyInfoFDD. -- NOTE2: The IE "UARFCN (Nupper)" corresponds to -- "uarfcn-UL" in FrequencyInfoFDD. FrequencyInfoFDD SEQUENCE { band-Class cdma-Freq
FrequencyInfoCDMA2000 ::=
BIT STRING (SIZE (5)), BIT STRING (SIZE(11))
} GERAN-SystemInfoBlock ::= GERAN-SystemInformation ::= GSM-BA-Range ::= OCTET STRING (SIZE (1..23)) SEQUENCE (SIZE (1..maxGERAN-SI)) OF GERAN-SystemInfoBlock SEQUENCE { gsmLowRangeUARFCN gsmUpRangeUARFCN
UARFCN, UARFCN
} GSM-BA-Range-List ::= SEQUENCE (SIZE (1..maxNumGSMFreqRanges)) OF GSM-BA-Range
3GPP
Release 6
972
3GPP TS 25.331 V6.23.0 (2009-09)
-- This IE is formatted as 'TLV' and is coded in the same way as the Mobile Station Classmark 2 -- information element in [5]. The first octet is the Mobile station classmark 2 IEI and its value -- shall be set to 33H. The second octet is the Length of mobile station classmark 2 and its value -- shall be set to 3. The octet 3 contains the first octet of the value part of the Mobile Station -- Classmark 2 information element, the octet 4 contains the second octet of the value part of the -- Mobile Station Classmark 2 information element and so on. For each of these octets, the first/ -- leftmost/ most significant bit of the octet contains b8 of the corresponding octet of the Mobile -- Station Classmark 2. GSM-Classmark2 ::= OCTET STRING (SIZE (5)) -- This IE is formatted as 'V' and is coded in the same way as the value part -- classmark 3 information element in [5] -- The value part is specified by means of CSN.1, which encoding results in a -- final padding may be appended upto the next octet boundary [5]. The first/ -- CSN.1 bit string is placed in the first/ leftmost/ most significant bit of -- octet. This continues until the last bit of the CSN.1 bit string, which is -- rightmost/ least significant bit of the last octet. GSM-Classmark3 ::= OCTET STRING (SIZE (1..32)) GSM-MessageList ::= in the Mobile station bit string, to which leftmost bit of the the first placed in the last/
SEQUENCE (SIZE (1..maxInterSysMessages)) OF BIT STRING (SIZE (1..512)) OCTET STRING (SIZE (1..64)) BIT STRING { -- For each bit value 0 means false/ not supported a5-7(0), a5-6(1), a5-5(2), a5-4(3), a5-3(4), a5-2(5), a5-1(6) } (SIZE (7)) SEQUENCE (SIZE (1..maxGSMTargetCells)) OF GSM-TargetCellInfo
GSM-MS-RadioAccessCapability ::= GsmSecurityCapability ::=
GSM-TargetCellInfoList ::=
GSM-TargetCellInfo ::= bcch-ARFCN frequency-band bsic }
SEQUENCE { BCCH-ARFCN, Frequency-Band, BSIC OPTIONAL
IdentificationOfReceivedMessage ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, receivedMessageType ReceivedMessageType } InterRAT-ChangeFailureCause ::= configurationUnacceptable physicalChannelFailure protocolError unspecified spare4 spare3 spare2 spare1 } GERANIu-MessageList ::= CHOICE { NULL, NULL, ProtocolErrorInformation, NULL, NULL, NULL, NULL, NULL
SEQUENCE (SIZE (1..maxInterSysMessages)) OF BIT STRING (SIZE (1..32768)) BIT STRING (SIZE (1..170))
GERANIu-RadioAccessCapability ::=
InterRAT-UE-RadioAccessCapability ::= CHOICE { gsm SEQUENCE { gsm-Classmark2 GSM-Classmark2, gsm-Classmark3 GSM-Classmark3 }, cdma2000 SEQUENCE { cdma2000-MessageList CDMA2000-MessageList } } InterRAT-UE-RadioAccessCapabilityList ::= SEQUENCE (SIZE(1..maxInterSysMessages)) OF InterRAT-UE-RadioAccessCapability
3GPP
Release 6
973
3GPP TS 25.331 V6.23.0 (2009-09)
InterRAT-UE-RadioAccessCapability-v590ext ::= SEQUENCE { geranIu-RadioAccessCapability GERANIu-RadioAccessCapability } InterRAT-UE-RadioAccessCapability-v690ext ::= SEQUENCE { supportOfInter-RAT-PS-Handover ENUMERATED { doesSupporInter-RAT-PS-Handover } gsm-MS-RadioAccessCapability GSM-MS-RadioAccessCapability } InterRAT-UE-SecurityCapability ::= CHOICE { gsm SEQUENCE { gsmSecurityCapability GsmSecurityCapability } } InterRAT-UE-SecurityCapList ::= SEQUENCE (SIZE(1..maxInterSysMessages)) OF InterRAT-UE-SecurityCapability CHOICE { NULL, NULL, ProtocolErrorInformation, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL
OPTIONAL,
InterRAT-HO-FailureCause ::= configurationUnacceptable physicalChannelFailure protocolError interRAT-ProtocolError unspecified spare11 spare10 spare9 spare8 spare7 spare6 spare5 spare4 spare3 spare2 spare1 }
MasterInformationBlock ::= SEQUENCE { mib-ValueTag MIB-ValueTag, -- TABULAR: The PLMN identity and ANSI-41 core network information -- are included in PLMN-Type. plmn-Type PLMN-Type, sibSb-ReferenceList SIBSb-ReferenceList, -- Extension mechanism for non- release99 information v690NonCriticalExtensions SEQUENCE { masterInformationBlock-v690ext MasterInformationBlock-v690ext, v6b0NoncriticalExtensions SEQUENCE { masterInformationBlock-v6b0ext MasterInformationBlock-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } MasterInformationBlock-v690ext ::= multiplePLMN-List } SEQUENCE { MultiplePLMN-List-r6
OPTIONAL
MasterInformationBlock-v6b0ext-IEs ::= SEQUENCE { extSIBTypeInfoSchedulingInfo-List ExtSIBTypeInfoSchedulingInfo-List } MIB-ValueTag ::= NCC ::= PLMN-ValueTag ::= INTEGER (1..8) INTEGER (0..7) INTEGER (1..256)
OPTIONAL
PredefinedConfigIdentityAndValueTag ::= SEQUENCE { predefinedConfigIdentity PredefinedConfigIdentity, predefinedConfigValueTag PredefinedConfigValueTag } ProtocolErrorInformation ::= diagnosticsType type1 protocolErrorCause SEQUENCE { CHOICE { SEQUENCE { ProtocolErrorCause
3GPP
Release 6
}, spare } } ReceivedMessageType ::=
974
3GPP TS 25.331 V6.23.0 (2009-09)
NULL
ENUMERATED { activeSetUpdate, cellChangeOrderFromUTRAN, cellUpdateConfirm, counterCheck, downlinkDirectTransfer, interRATHandoverCommand, measurementControl, pagingType2, physicalChannelReconfiguration, physicalSharedChannelAllocation, radioBearerReconfiguration, radioBearerRelease, radioBearerSetup, rrcConnectionRelease, rrcConnectionReject, rrcConnectionSetup, securityModeCommand, signallingConnectionRelease, transportChannelReconfiguration, transportFormatCombinationControl, ueCapabilityEnquiry, ueCapabilityInformationConfirm, uplinkPhysicalChannelControl, uraUpdateConfirm, utranMobilityInformation, assistanceDataDelivery, spare6, spare5, spare4, spare3, spare2, spare1
} Rplmn-Information ::= SEQUENCE { gsm-BA-Range-List GSM-BA-Range-List OPTIONAL, fdd-UMTS-Frequency-List FDD-UMTS-Frequency-List tdd-UMTS-Frequency-List TDD-UMTS-Frequency-List OPTIONAL, cdma2000-UMTS-Frequency-List List } OPTIONAL CDMA2000-UMTS-Frequency-
OPTIONAL,
Rplmn-Information-r4 ::= SEQUENCE { gsm-BA-Range-List GSM-BA-Range-List fdd-UMTS-Frequency-List FDD-UMTS-Frequency-List tdd384-UMTS-Frequency-List TDD-UMTS-Frequency-List tdd128-UMTS-Frequency-List TDD-UMTS-Frequency-List cdma2000-UMTS-Frequency-List CDMA2000-UMTS-Frequency-List }
SchedulingInformation ::= SEQUENCE { scheduling SEQUENCE { segCount SegCount DEFAULT 1, sib-Pos CHOICE { -- The element name indicates the repetition period and the value -- (multiplied by two) indicates the position of the first segment. rep4 INTEGER (0..1), rep8 INTEGER (0..3), rep16 INTEGER (0..7), rep32 INTEGER (0..15), rep64 INTEGER (0..31), rep128 INTEGER (0..63), rep256 INTEGER (0..127), rep512 INTEGER (0..255), rep1024 INTEGER (0..511), rep2048 INTEGER (0..1023), rep4096 INTEGER (0..2047) }, sib-PosOffsetInfo SibOFF-List OPTIONAL } } SchedulingInformationSIB ::= sib-Type SEQUENCE { SIB-TypeAndTag,
3GPP
Release 6
scheduling } SchedulingInformationSIBSb ::= sibSb-Type scheduling } SegCount ::= SegmentIndex ::=
975
SchedulingInformation
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { SIBSb-TypeAndTag, SchedulingInformation
INTEGER (1..16) INTEGER (1..15)
-- Actual value SFN-Prime = 2 * IE value SFN-Prime ::= INTEGER (0..2047)
SIB-Data-fixed ::=
SIB-Data-variable ::= SIBOccurIdentity ::=
BIT STRING (SIZE (1..214)) INTEGER (0..15)
SIBOccurrenceIdentityAndValueTag ::= SEQUENCE { sibOccurIdentity SIBOccurIdentity, sibOccurValueTag SIBOccurValueTag } SIBOccurValueTag ::= SIB-ReferenceList ::= INTEGER (0..15) SEQUENCE (SIZE (1..maxSIB)) OF SchedulingInformationSIB SEQUENCE (SIZE (1..maxSIB)) OF SchedulingInformationSIBSb SEQUENCE (SIZE (1..maxSIB-FACH)) OF SchedulingInformationSIB
SIBSb-ReferenceList ::=
SIB-ReferenceListFACH ::=
SIB-Type ::=
ENUMERATED { masterInformationBlock, systemInformationBlockType1, systemInformationBlockType2, systemInformationBlockType3, systemInformationBlockType4, systemInformationBlockType5, systemInformationBlockType6, systemInformationBlockType7, -- dummy, dummy2 and dummy3 are not used in this version of the specification, -- they should not be sent. If they are received they should be ignored dummy, dummy2, dummy3, systemInformationBlockType11, systemInformationBlockType12, systemInformationBlockType13, systemInformationBlockType13-1, systemInformationBlockType13-2, systemInformationBlockType13-3, systemInformationBlockType13-4, systemInformationBlockType14, systemInformationBlockType15, systemInformationBlockType15-1, systemInformationBlockType15-2, systemInformationBlockType15-3, systemInformationBlockType16, systemInformationBlockType17, systemInformationBlockType15-4, systemInformationBlockType18, schedulingBlock1, schedulingBlock2, systemInformationBlockType15-5, systemInformationBlockType5bis, extensionType } CHOICE { PLMN-ValueTag, CellValueTag,
SIB-TypeAndTag ::= sysInfoType1 sysInfoType2
3GPP
Release 6
sysInfoType3 sysInfoType4 sysInfoType5 sysInfoType6 sysInfoType7 -- dummy, dummy2 and dummy3 are not -- they should not be sent. If they dummy dummy2 dummy3 sysInfoType11 sysInfoType12 sysInfoType13 sysInfoType13-1 sysInfoType13-2 sysInfoType13-3 sysInfoType13-4 sysInfoType14 sysInfoType15 sysInfoType16 sysInfoType17 sysInfoType15-1 sysInfoType15-2 sysInfoType15-3 sysInfoType15-4 sysInfoType18 sysInfoType15-5 sysInfoType5bis spare4 spare3 spare2 spare1 } SIBSb-TypeAndTag ::= sysInfoType1 sysInfoType2 sysInfoType3 sysInfoType4 sysInfoType5 sysInfoType6 sysInfoType7 -- dummy, dummy2 and dummy3 are not -- they should not be sent. If they dummy dummy2 dummy3 sysInfoType11 sysInfoType12 sysInfoType13 sysInfoType13-1 sysInfoType13-2 sysInfoType13-3 sysInfoType13-4 sysInfoType14 sysInfoType15 sysInfoType16 sysInfoType17 sysInfoTypeSB1 sysInfoTypeSB2 sysInfoType15-1 sysInfoType15-2 sysInfoType15-3 sysInfoType15-4 sysInfoType18 sysInfoType15-5 sysInfoType5bis spare2 spare1 }
976
3GPP TS 25.331 V6.23.0 (2009-09)
CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, used in this version of the specification, are received the UE behaviour is not specified. CellValueTag, NULL, NULL, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, CellValueTag, PredefinedConfigIdentityAndValueTag, NULL, CellValueTag, SIBOccurrenceIdentityAndValueTag, SIBOccurrenceIdentityAndValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, NULL, NULL, NULL
CHOICE { PLMN-ValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, used in this version of the specification, are received the UE behaviour is not specified. CellValueTag, NULL, NULL, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, CellValueTag, PredefinedConfigIdentityAndValueTag, NULL, CellValueTag, CellValueTag, CellValueTag, SIBOccurrenceIdentityAndValueTag, SIBOccurrenceIdentityAndValueTag, CellValueTag, CellValueTag, CellValueTag, CellValueTag, NULL, NULL
SIB-TypeExt ::= CHOICE { systemInformationBlockType11bis NULL, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL,
3GPP
Release 6
spare2 spare1 } SibOFF ::= NULL, NULL
977
3GPP TS 25.331 V6.23.0 (2009-09)
ENUMERATED { so2, so4, so6, so8, so10, so12, so14, so16, so18, so20, so22, so24, so26, so28, so30, so32 } SEQUENCE (SIZE (1..15)) OF SibOFF
SibOFF-List ::=
SysInfoType1 ::= SEQUENCE { -- Core network IEs cn-CommonGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP, cn-DomainSysInfoList CN-DomainSysInfoList, -- User equipment IEs ue-ConnTimersAndConstants UE-ConnTimersAndConstants ue-IdleTimersAndConstants UE-IdleTimersAndConstants -- Extension mechanism for non- release99 information v3a0NonCriticalExtensions SEQUENCE { sysInfoType1-v3a0ext SysInfoType1-v3a0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } SysInfoType1-v3a0ext-IEs ::= SEQUENCE { ue-ConnTimersAndConstants-v3a0ext ue-IdleTimersAndConstants-v3a0ext }
OPTIONAL, OPTIONAL,
UE-ConnTimersAndConstants-v3a0ext, UE-IdleTimersAndConstants-v3a0ext
SysInfoType2 ::= SEQUENCE { -- UTRAN mobility IEs ura-IdentityList URA-IdentityList, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} }
OPTIONAL
SysInfoType3 ::= SEQUENCE { sib4indicator BOOLEAN, -- UTRAN mobility IEs cellIdentity CellIdentity, cellSelectReselectInfo CellSelectReselectInfoSIB-3-4, cellAccessRestriction CellAccessRestriction, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType3-v4b0ext SysInfoType3-v4b0ext-IEs, v590NonCriticalExtension SEQUENCE { sysInfoType3-v590ext SysInfoType3-v590ext, v5c0NoncriticalExtension SEQUENCE { sysInfoType3-v5c0ext SysInfoType3-v5c0ext-IEs, v670NonCriticalExtension SEQUENCE { sysInfoType3-v670ext SysInfoType3-v670ext, nonCriticalExtensions SEQUENCE {} } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType3-v4b0ext-IEs ::= SEQUENCE { mapping-LCR Mapping-LCR-r4 } SysInfoType3-v590ext ::= SEQUENCE { cellSelectReselectInfo-v590ext }
OPTIONAL
OPTIONAL
CellSelectReselectInfo-v590ext
OPTIONAL
SysInfoType3-v5c0ext-IEs ::= SEQUENCE { cellSelectReselectInfoTreselectionScaling-v5c0ext CellSelectReselectInfoTreselectionScaling-v5c0ext } SysInfoType3-v670ext ::= SEQUENCE { domainSpecificAccessRestrictionParametersForPLMNOfMIB DomainSpecificAccessRestrictionParam-v670ext domainSpecificAccessRestictionForSharedNetwork
OPTIONAL
OPTIONAL,
3GPP
Release 6
978
3GPP TS 25.331 V6.23.0 (2009-09)
DomainSpecificAccessRestrictionForSharedNetwork-v670ext OPTIONAL } SysInfoType4 ::= SEQUENCE { -- UTRAN mobility IEs cellIdentity CellIdentity, cellSelectReselectInfo CellSelectReselectInfoSIB-3-4, cellAccessRestriction CellAccessRestriction, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType4-v4b0ext SysInfoType4-v4b0ext-IEs, v590NonCriticalExtension SEQUENCE { sysInfoType4-v590ext SysInfoType4-v590ext, v5b0NonCriticalExtension SEQUENCE { sysInfoType4-v5b0ext SysInfoType4-v5b0ext-IEs, v5c0NonCriticalExtension SEQUENCE { sysInfoType4-v5c0ext SysInfoType4-v5c0ext-IEs, nonCriticalExtensions SEQUENCE {} } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType4-v4b0ext-IEs ::= SEQUENCE { mapping-LCR Mapping-LCR-r4 }
OPTIONAL
OPTIONAL
SysInfoType4-v590ext ::= SEQUENCE { cellSelectReselectInfo-v590ext }
CellSelectReselectInfo-v590ext
OPTIONAL
SysInfoType4-v5b0ext-IEs ::= SEQUENCE { cellSelectReselectInfoPCHFACH-v5b0ext }
CellSelectReselectInfoPCHFACH-v5b0ext
OPTIONAL
SysInfoType4-v5c0ext-IEs ::= SEQUENCE { cellSelectReselectInfoTreselectionScaling-v5c0ext CellSelectReselectInfoTreselectionScaling-v5c0ext }
OPTIONAL
SysInfoType5 ::= SEQUENCE { sib6indicator BOOLEAN, -- Physical channel IEs pich-PowerOffset PICH-PowerOffset, modeSpecificInfo CHOICE { fdd SEQUENCE { aich-PowerOffset AICH-PowerOffset }, tdd SEQUENCE { -- If PDSCH/PUSCH is configured for 1.28Mcps TDD, the following IEs should be absent -and the info included in the tdd128SpecificInfo instead. -- If PDSCH/PUSCH is configured for 3.84Mcps TDD in R5, HCR-r5-SpecificInfo should also be -- included. pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN OPTIONAL, pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN OPTIONAL, openLoopPowerControl-TDD OpenLoopPowerControl-TDD } }, primaryCCPCH-Info PrimaryCCPCH-Info OPTIONAL, prach-SystemInformationList PRACH-SystemInformationList, sCCPCH-SystemInformationList SCCPCH-SystemInformationList, -- cbs-DRX-Level1Information is conditional on any of the CTCH indicator IEs in -- sCCPCH-SystemInformationList cbs-DRX-Level1Information CBS-DRX-Level1Information OPTIONAL, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType5-v4b0ext SysInfoType5-v4b0ext-IEs OPTIONAL, -- Extension mechanism for non- rel-4 information v590NonCriticalExtensions SEQUENCE { sysInfoType5-v590ext SysInfoType5-v590ext-IEs OPTIONAL, v650NonCriticalExtensions SEQUENCE { sysInfoType5-v650ext SysInfoType5-v650ext-IEs OPTIONAL, v680NonCriticalExtensions SEQUENCE { sysInfoType5-v680ext SysInfoType5-v680ext-IEs OPTIONAL, v690NonCriticalExtensions SEQUENCE { sysInfoType5-v690ext SysInfoType5-v690ext-IEs,
3GPP
Release 6
979
nonCriticalExtensions OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL OPTIONAL }
3GPP TS 25.331 V6.23.0 (2009-09)

SEQUENCE {} OPTIONAL
} } }
SysInfoType5-v4b0ext-IEs ::= SEQUENCE { --The following IE PNBSCH-Allocation-r4 shall be used for 3.84Mcps TDD only. pNBSCH-Allocation-r4 PNBSCH-Allocation-r4 OPTIONAL, -- In case of TDD, the following IE is included instead of the -- IE up-IPDL-Parameter in up-OTDOA-AssistanceData. openLoopPowerControl-IPDL-TDD OpenLoopPowerControl-IPDL-TDD-r4 OPTIONAL, -- If SysInfoType5 is sent to describe a 1.28Mcps TDD cell, the IE PRACH-RACH-Info included in -- PRACH-SystemInformationList shall be ignored, the IE PRACH-Partitioning and the -- IE rach-TransportFormatSet shall be absent and the corresponding IE in the following -- PRACH-SystemInformationList-LCR-r4 shall be used prach-SystemInformationList-LCR-r4 PRACH-SystemInformationList-LCR-r4 OPTIONAL, tdd128SpecificInfo SEQUENCE { pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN-LCR-r4 OPTIONAL, pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN-LCR-r4 OPTIONAL, pCCPCH-LCR-Extensions PrimaryCCPCH-Info-LCR-r4-ext OPTIONAL, sCCPCH-LCR-ExtensionsList SCCPCH-SystemInformationList-LCR-r4-ext } OPTIONAL, frequencyBandIndicator RadioFrequencyBandFDD OPTIONAL } SysInfoType5-v590ext-IEs ::= SEQUENCE { hcr-r5-SpecificInfo SEQUENCE { pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN-HCR-r5 pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN-HCR-r5 } } SysInfoType5-v650ext-IEs ::= SEQUENCE { frequencyBandIndicator2 RadioFrequencyBandFDD2 } SysInfoType5-v680ext-IEs ::= SEQUENCE { -- TABULAR: HSDPA Cell Indicator is MD in tabular description -- Default value is HSDPA Capability not indicated hsdpa-CellIndicator ENUMERATED { hsdpa-CapableCell } }
OPTIONAL, OPTIONAL OPTIONAL
OPTIONAL
SysInfoType5-v690ext-IEs ::= SEQUENCE { -- TABULAR: E-DCH Cell Indicator is MD in tabular description -- Default value is E-DCH Capability not indicated edch-CellIndicator ENUMERATED { edch-CapableCell } OPTIONAL, sccpch-SystemInformation-MBMS CHOICE { mcchOnSCCPCHusedForNonMBMS MBMS-MCCH-ConfigurationInfo-r6, mcchOnSCCPCHusedOnlyForMBMS SCCPCH-SystemInformation-MBMS-r6 } OPTIONAL, additionalPRACH-TF-and-TFCS-CCCH-List AdditionalPRACH-TF-and-TFCS-CCCH-List OPTIONAL, cBS-DRX-Level1Information-extension CBS-DRX-Level1Information-extension-r6 OPTIONAL } -- SysInfoType5bis uses the same structure as SysInfoType5 SysInfoType5bis ::= SysInfoType5 SysInfoType6 ::= SEQUENCE { -- Physical channel IEs pich-PowerOffset PICH-PowerOffset, modeSpecificInfo CHOICE { fdd SEQUENCE { aich-PowerOffset AICH-PowerOffset, -- dummy is not used in this version of specification, it should -- not be sent and if received it should be ignored. dummy CSICH-PowerOffset OPTIONAL }, tdd SEQUENCE { -- If PDSCH/PUSCH is configured for 1.28Mcps TDD, pusch-SysInfoList-SFN, -- pdsch-SysInfoList-SFN and openLoopPowerControl-TDD should be absent -- and the info included in the tdd128SpecificInfo instead. -- If PDSCH/PUSCH is configured for 3.84Mcps TDD in R5, HCR-r5-SpecificInfo should -- also be included. pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN OPTIONAL, pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN OPTIONAL,
3GPP
Release 6
openLoopPowerControl-TDD }
980
3GPP TS 25.331 V6.23.0 (2009-09)
OpenLoopPowerControl-TDD
}, primaryCCPCH-Info PrimaryCCPCH-Info OPTIONAL, prach-SystemInformationList PRACH-SystemInformationList OPTIONAL, sCCPCH-SystemInformationList SCCPCH-SystemInformationList OPTIONAL, cbs-DRX-Level1Information CBS-DRX-Level1Information OPTIONAL, -- Conditional on any of the CTCH indicator IEs in -- sCCPCH-SystemInformationList -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType6-v4b0ext SysInfoType6-v4b0ext-IEs OPTIONAL, -- Extension mechanism for non- rel-4 information v590NonCriticalExtensions SEQUENCE { sysInfoType6-v590ext SysInfoType6-v590ext-IEs OPTIONAL, v650nonCriticalExtensions SEQUENCE { sysInfoType6-v650ext SysInfoType6-v650ext-IEs OPTIONAL, v690nonCriticalExtensions SEQUENCE { sysInfoType6-v690ext SysInfoType6-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType6-v4b0ext-IEs ::= SEQUENCE { -- openLoopPowerControl-IPDL-TDD is present only if IPDLs are applied for TDD openLoopPowerControl-IPDL-TDD OpenLoopPowerControl-IPDL-TDD-r4 OPTIONAL, -- If SysInfoType6 is sent to describe a 1.28Mcps TDD cell, the IE PRACH-RACH-Info included -- in PRACH-SystemInformationList shall be ignored, the IE PRACH-Partitioning and the -- IE rach-TransportFormatSet shall be absent and the corresponding IEs in the following -- PRACH-SystemInformationList-LCR-r4 shall be used prach-SystemInformationList-LCR-r4 PRACH-SystemInformationList-LCR-r4 OPTIONAL, tdd128SpecificInfo SEQUENCE { pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN-LCR-r4 OPTIONAL, pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN-LCR-r4 OPTIONAL, pCCPCH-LCR-Extensions PrimaryCCPCH-Info-LCR-r4-ext OPTIONAL, sCCPCH-LCR-ExtensionsList SCCPCH-SystemInformationList-LCR-r4-ext OPTIONAL } OPTIONAL, frequencyBandIndicator RadioFrequencyBandFDD OPTIONAL } SysInfoType6-v590ext-IEs ::= SEQUENCE { hcr-r5-SpecificInfo SEQUENCE { pusch-SysInfoList-SFN PUSCH-SysInfoList-SFN-HCR-r5 pdsch-SysInfoList-SFN PDSCH-SysInfoList-SFN-HCR-r5 } } SysInfoType6-v650ext-IEs ::= SEQUENCE { frequencyBandIndicator2 RadioFrequencyBandFDD2 } SysInfoType6-v690ext-IEs ::= SEQUENCE { additionalPRACH-TF-and-TFCS-CCCH-List }
AdditionalPRACH-TF-and-TFCS-CCCH-List
OPTIONAL
SysInfoType7 ::= SEQUENCE { -- Physical channel IEs modeSpecificInfo CHOICE { fdd SEQUENCE { ul-Interference UL-Interference }, tdd NULL }, prach-Information-SIB5-List DynamicPersistenceLevelList, prach-Information-SIB6-List DynamicPersistenceLevelList expirationTimeFactor ExpirationTimeFactor -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} }
-- This IE is not used in this version of the specification. -- It was kept only for backwards compatibility reasons SysInfoType8 ::= SEQUENCE { -- User equipment IEs -- dummy1, dummy2, dummy3 are not used in this version of the specification and
3GPP
Release 6
981
3GPP TS 25.331 V6.23.0 (2009-09)
-- they should be ignored by the receiver. dummy1 CPCH-Parameters, -- Physical channel IEs dummy2 CPCH-SetInfoList, dummy3 CSICH-PowerOffset, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } -- This IE is not used in this version of the specification. -- It was kept only for backwards compatibility reasons SysInfoType9 ::= SEQUENCE { -- Physical channel IEs -- dummy is not used in this version of the specification and -- it should be ignored by the receiver. dummy CPCH-PersistenceLevelsList, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} }
OPTIONAL
OPTIONAL
-- This IE is not used in this version of the specification. -- It was kept only for backwards compatibility reasons SysInfoType10 ::= SEQUENCE { -- User equipment IEs -- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. dummy DRAC-SysInfoList, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} OPTIONAL } SysInfoType11 ::= SEQUENCE { sib12indicator BOOLEAN, -- Measurement IEs fach-MeasurementOccasionInfo FACH-MeasurementOccasionInfo OPTIONAL, measurementControlSysInfo MeasurementControlSysInfo, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType11-v4b0ext SysInfoType11-v4b0ext-IEs OPTIONAL, v590NonCriticalExtension SEQUENCE { sysInfoType11-v590ext SysInfoType11-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { sysInfoType11-v690ext SysInfoType11-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { sysInfoType11-v6b0ext SysInfoType11-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType11-v4b0ext-IEs ::= SEQUENCE { fach-MeasurementOccasionInfo-LCR-Ext measurementControlSysInfo-LCR }
OPTIONAL
FACH-MeasurementOccasionInfo-LCR-r4-ext OPTIONAL, MeasurementControlSysInfo-LCR-r4-ext
SysInfoType11-v590ext-IEs ::= SEQUENCE { --The order of the list corresponds to the order of cell in newIntraFrequencyCellInfoList newIntraFrequencyCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterFrequencyCellInfoList newInterFrequencyCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterRATCellInfoList newInterRATCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, intraFreqEventCriteriaList-v590ext Intra-FreqEventCriteriaList-v590ext OPTIONAL, intraFreqReportingCriteria-1b-r5 IntraFreqReportingCriteria-1b-r5 OPTIONAL, intraFreqEvent-1d-r5 IntraFreqEvent-1d-r5 OPTIONAL } SysInfoType11-v690ext-IEs ::= SEQUENCE { -- dummy is not used in this version of the specification. If received, the UE behaviour -- is not specified. dummy Dummy-InterFreqRACHReportingInfo OPTIONAL }
3GPP
Release 6
982
3GPP TS 25.331 V6.23.0 (2009-09)
SysInfoType11-v6b0ext-IEs ::= SEQUENCE { -- Measurement IEs interFreqRACHReportingInfo InterFreqRACHReportingInfo }
OPTIONAL
SysInfoType11bis ::= SEQUENCE { -- Measurement IEs measurementControlSysInfo MeasurementControlSysInfoExtension measurementControlSysInfo-LCR MeasurementControlSysInfoExtension-LCR-r4 measurementControlSysInfoExtensionAddon-r5 MeasurementControlSysInfoExtensionAddon-r5 -- Extension mechanism for non-release99 information nonCriticalExtensions SEQUENCE {} OPTIONAL }
SysInfoType12 ::= SEQUENCE { -- Measurement IEs fach-MeasurementOccasionInfo FACH-MeasurementOccasionInfo OPTIONAL, measurementControlSysInfo MeasurementControlSysInfo, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType12-v4b0ext SysInfoType12-v4b0ext-IEs OPTIONAL, v590NonCriticalExtension SEQUENCE { sysInfoType12-v590ext SysInfoType12-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { sysInfoType12-v690ext SysInfoType12-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { sysInfoType12-v6b0ext SysInfoType12-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType12-v4b0ext-IEs ::= SEQUENCE { fach-MeasurementOccasionInfo-LCR-Ext measurementControlSysInfo-LCR }
OPTIONAL
FACH-MeasurementOccasionInfo-LCR-r4-ext OPTIONAL, MeasurementControlSysInfo-LCR-r4-ext
SysInfoType12-v590ext-IEs ::= SEQUENCE { --The order of the list corresponds to the order of cell in newIntraFrequencyCellInfoList newIntraFrequencyCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterFrequencyCellInfoList newInterFrequencyCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, --The order of the list corresponds to the order of cell in newInterRATCellInfoList newInterRATCellInfoList-v590ext SEQUENCE (SIZE (1..maxCellMeas)) OF CellSelectReselectInfo-v590ext OPTIONAL, intraFreqEventCriteriaList-v590ext Intra-FreqEventCriteriaList-v590ext OPTIONAL, intraFreqReportingCriteria-1b-r5 IntraFreqReportingCriteria-1b-r5 OPTIONAL, intraFreqEvent-1d-r5 IntraFreqEvent-1d-r5 OPTIONAL } SysInfoType12-v690ext-IEs ::= SEQUENCE { -- dummy is not used in this version of the specification. If received, the UE behaviour -- is not specified. dummy Dummy-InterFreqRACHReportingInfo OPTIONAL } SysInfoType12-v6b0ext-IEs ::= SEQUENCE { -- Measurement IEs interFreqRACHReportingInfo InterFreqRACHReportingInfo } SysInfoType13 ::= SEQUENCE { -- Core network IEs cn-DomainSysInfoList CN-DomainSysInfoList, -- User equipment IEs ue-IdleTimersAndConstants UE-IdleTimersAndConstants capabilityUpdateRequirement CapabilityUpdateRequirement -- Extension mechanism for non- release99 information v3a0NonCriticalExtensions SEQUENCE { sysInfoType13-v3a0ext SysInfoType13-v3a0ext-IEs, v4b0NonCriticalExtensions SEQUENCE { sysInfoType13-v4b0ext SysInfoType13-v4b0ext-IEs, -- Extension mechanism for non- release99 information
OPTIONAL
OPTIONAL, OPTIONAL,
3GPP
Release 6
nonCriticalExtensions } } } SysInfoType13-v3a0ext-IEs ::= SEQUENCE { ue-IdleTimersAndConstants-v3a0ext }
983
SEQUENCE {} OPTIONAL OPTIONAL
3GPP TS 25.331 V6.23.0 (2009-09)

OPTIONAL
UE-IdleTimersAndConstants-v3a0ext
SysInfoType13-v4b0ext-IEs ::= SEQUENCE { capabilityUpdateRequirement-r4Ext CapabilityUpdateRequirement-r4-ext } SysInfoType13-1 ::= SEQUENCE { -- ANSI-41 IEs ansi-41-RAND-Information ANSI-41-RAND-Information, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType13-2 ::= SEQUENCE { -- ANSI-41 IEs ansi-41-UserZoneID-Information ANSI-41-UserZoneID-Information, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType13-3 ::= SEQUENCE { -- ANSI-41 IEs ansi-41-PrivateNeighbourListInfo ANSI-41-PrivateNeighbourListInfo, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType13-4 ::= SEQUENCE { -- ANSI-41 IEs ansi-41-GlobalServiceRedirectInfo ANSI-41-GlobalServiceRedirectInfo, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType14 ::= SEQUENCE { -- Physical channel IEs individualTS-InterferenceList IndividualTS-InterferenceList, expirationTimeFactor ExpirationTimeFactor -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType15 ::= -- Measurement IEs SEQUENCE {
OPTIONAL
OPTIONAL
OPTIONAL
OPTIONAL
OPTIONAL
OPTIONAL, OPTIONAL
ue-positioning-GPS-CipherParameters ue-positioning-GPS-ReferenceLocation ue-positioning-GPS-ReferenceTime
UE-Positioning-CipherParameters ReferenceLocation, UE-Positioning-GPS-ReferenceTime,
OPTIONAL,
ue-positioning-GPS-Real-timeIntegrity BadSatList -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType15-v4b0ext SysInfoType15-v4b0ext-IEs, -- Extension mechanism for non- release4 information nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } SysInfoType15-v4b0ext-IEs ::= SEQUENCE { up-Ipdl-Parameters-TDD UE-Positioning-IPDL-Parameters-TDD-r4-ext } SysInfoType15-1 ::= SEQUENCE { -- DGPS corrections ue-positioning-GPS-DGPS-Corrections
OPTIONAL,
OPTIONAL
UE-Positioning-GPS-DGPS-Corrections,
-- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} }
OPTIONAL
3GPP
Release 6
984
3GPP TS 25.331 V6.23.0 (2009-09)
SysInfoType15-2 ::= SEQUENCE { -- Ephemeris and clock corrections transmissionTOW INTEGER (0..604799), satID SatID, ephemerisParameter EphemerisParameter, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} } SysInfoType15-3 ::= SEQUENCE { -- Almanac and other data transmissionTOW INTEGER (0.. 604799), ue-positioning-GPS-Almanac UE-Positioning-GPS-Almanac OPTIONAL, ue-positioning-GPS-IonosphericModel UE-Positioning-GPS-IonosphericModel OPTIONAL, ue-positioning-GPS-UTC-Model UE-Positioning-GPS-UTC-Model OPTIONAL, satMask BIT STRING (SIZE (1..32)) OPTIONAL, lsbTOW BIT STRING (SIZE (8)) OPTIONAL, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} OPTIONAL } SysInfoType15-4 ::= SEQUENCE { -- Measurement IEs ue-positioning-OTDOA-CipherParameters UE-Positioning-CipherParameters ue-positioning-OTDOA-AssistanceData UE-Positioning-OTDOA-AssistanceData, v3a0NonCriticalExtensions SEQUENCE { sysInfoType15-4-v3a0ext SysInfoType15-4-v3a0ext, -- Extension mechanism for non- release99 information v4b0NonCriticalExtensions SEQUENCE { sysInfoType15-4-v4b0ext SysInfoType15-4-v4b0ext, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } SysInfoType15-4-v3a0ext ::= SEQUENCE { sfn-Offset-Validity SFN-Offset-Validity } SysInfoType15-4-v4b0ext ::= SEQUENCE { ue-Positioning-OTDOA-AssistanceData-r4ext }
OPTIONAL
OPTIONAL,
OPTIONAL
UE-Positioning-OTDOA-AssistanceData-r4ext
OPTIONAL
SysInfoType15-5 ::= SEQUENCE { -- Measurement IEs ue-positioning-OTDOA-AssistanceData-UEB UE-Positioning-OTDOA-AssistanceData-UEB, v3a0NonCriticalExtensions SEQUENCE { sysInfoType15-5-v3a0ext SysInfoType15-5-v3a0ext, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } SysInfoType15-5-v3a0ext ::= SEQUENCE { sfn-Offset-Validity SFN-Offset-Validity }
OPTIONAL
SysInfoType16 ::= SEQUENCE { -- Radio bearer IEs preDefinedRadioConfiguration PreDefRadioConfiguration, -- Extension mechanism for non- release99 information nonCriticalExtensions SEQUENCE {} }
OPTIONAL
SysInfoType17 ::= SEQUENCE { -- Physical channel IEs -- If PDSCH/PUSCH is configured for 1.28Mcps TDD, pusch-SysInfoList and -- pdsch-SysInfoList should be absent and the info included in the -- tdd128SpecificInfo instead. -- If PDSCH/PUSCH is configured for 3.84Mcps TDD in R5, HCR-r5-SpecificInfo should also be -- included. pusch-SysInfoList PUSCH-SysInfoList OPTIONAL, pdsch-SysInfoList PDSCH-SysInfoList OPTIONAL, -- Extension mechanism for non- release99 information
3GPP
Release 6
985
3GPP TS 25.331 V6.23.0 (2009-09)
v4b0NonCriticalExtensions SEQUENCE { sysInfoType17-v4b0ext SysInfoType17-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { sysInfoType17-v590ext SysInfoType17-v590ext-IEs nonCriticalExtensions SEQUENCE {} } OPTIONAL } OPTIONAL } SysInfoType17-v4b0ext-IEs ::= SEQUENCE { tdd128SpecificInfo SEQUENCE { pusch-SysInfoList PUSCH-SysInfoList-LCR-r4 pdsch-SysInfoList PDSCH-SysInfoList-LCR-r4 } } SysInfoType17-v590ext-IEs ::= SEQUENCE { hcr-r5-SpecificInfo SEQUENCE { pusch-SysInfoList PUSCH-SysInfoList-HCR-r5 pdsch-SysInfoList PDSCH-SysInfoList-HCR-r5 } }
OPTIONAL, OPTIONAL
SysInfoType18 ::= SEQUENCE { idleModePLMNIdentities PLMNIdentitiesOfNeighbourCells connectedModePLMNIdentities PLMNIdentitiesOfNeighbourCells -- Extension mechanism for non- release99 information v6b0NonCriticalExtensions SEQUENCE { sysInfoType18-v6b0ext SysInfoType18-v6b0ext, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }
OPTIONAL, OPTIONAL,
SysInfoType18-v6b0ext ::= SEQUENCE { idleModePLMNIdentitiesSIB11bis PLMNIdentitiesOfNeighbourCells connectedModePLMNIdentitiesSIB11bis PLMNIdentitiesOfNeighbourCells } SysInfoTypeSB1 ::= SEQUENCE { -- Other IEs sib-ReferenceList SIB-ReferenceList, -- Extension mechanism for non- release99 information v6b0NonCriticalExtensions SEQUENCE { sysInfoTypeSB1-v6b0ext SysInfoTypeSB1-v6b0ext, nonCriticalExtensions SEQUENCE {} } OPTIONAL } SysInfoTypeSB1-v6b0ext ::= SEQUENCE { extSIBTypeInfoSchedulingInfo-List }
OPTIONAL, OPTIONAL
OPTIONAL
ExtSIBTypeInfoSchedulingInfo-List
OPTIONAL
SysInfoTypeSB2 ::= SEQUENCE { -- Other IEs sib-ReferenceList SIB-ReferenceList, -- Extension mechanism for non- release99 information v6b0NonCriticalExtensions SEQUENCE { sysInfoTypeSB2-v6b0ext SysInfoTypeSB2-v6b0ext, nonCriticalExtensions SEQUENCE {} } OPTIONAL } SysInfoTypeSB2-v6b0ext ::= SEQUENCE { extSIBTypeInfoSchedulingInfo-List } TDD-UMTS-Frequency-List ::=
OPTIONAL
ExtSIBTypeInfoSchedulingInfo-List
OPTIONAL
SEQUENCE (SIZE (1..maxNumTDDFreqs)) OF FrequencyInfoTDD
-- For systemInformationBlockType11bis the Value Tag Info "CellValueTag" is used ValueTagInfo ::= CHOICE { none NULL, cellValueTag CellValueTag, plmn-ValueTag PLMN-ValueTag, sIBOccurrenceIdentityAndValueTag SIBOccurrenceIdentityAndValueTag } -- ***************************************************
3GPP
Release 6
986
3GPP TS 25.331 V6.23.0 (2009-09)
--ANSI-41 INFORMATION ELEMENTS (10.3.9) --- *************************************************** ANSI-41-GlobalServiceRedirectInfo ::= ANSI-41-PrivateNeighbourListInfo ::= ANSI-41-RAND-Information ::= ANSI-41-UserZoneID-Information ::= ANSI-41-NAS-Parameter ::= Min-P-REV ::= NAS-SystemInformationANSI-41 ::= NID ::= P-REV ::= SID ::= ANSI-41-NAS-Parameter ANSI-41-NAS-Parameter ANSI-41-NAS-Parameter ANSI-41-NAS-Parameter BIT STRING (SIZE (1..2048)) BIT STRING (SIZE (8)) ANSI-41-NAS-Parameter BIT STRING (SIZE (16)) BIT STRING (SIZE (8)) BIT STRING (SIZE (15))
-- *************************************************** --MBMS INFORMATION ELEMENTS (10.3.9a) --- *************************************************** MBMS-AccessProbabilityFactor ::= ENUMERATED { apf0, apf32, apf64, apf96, apf128, apf160, apf192, apf224, apf256, apf288, apf320, apf352, apf384, apf416, apf448, apf480, apf512, apf544, apf576, apf608, apf640, apf672, apf704, apf736, apf768, apf800, apf832, apf864, apf896, apf928, apf960, apf1000 } BIT STRING (SIZE (12)) INTEGER (1..32) INTEGER (1..32) INTEGER (1..32) SEQUENCE { MBMS-CommonRBIdentity, PDCP-Info-r4, RLC-Info-MTCH-r6
MBMS-CellGroupIdentity-r6 ::= MBMS-CommonCCTrChIdentity ::= MBMS-CommonPhyChIdentity ::= MBMS-CommonRBIdentity ::= MBMS-CommonRBInformation-r6 ::= commonRBIdentity pdcp-Info rlc-Info }
MBMS-CommonRBInformationList-r6 ::= SEQUENCE (SIZE (1..maxMBMS-CommonRB)) OF MBMS-CommonRBInformation-r6 MBMS-CommonTrChIdentity ::= INTEGER (1..32)
MBMS-ConnectedModeCountingScope ::= SEQUENCE { countingForUraPCH countingForCellPCH countingForCellFACH }
BOOLEAN, BOOLEAN, BOOLEAN
MBMS-CurrentCell-SCCPCH-r6 ::= SEQUENCE { sccpchIdentity MBMS-SCCPCHIdentity OPTIONAL, secondaryCCPCH-Info MBMS-CommonPhyChIdentity, softComb-TimingOffset MBMS-SoftComb-TimingOffset OPTIONAL, -- If the IE transpCh-InfoCommonForAllTrCh is absent, the default TFCS as specified -- in 14.10.1 applies transpCh-InfoCommonForAllTrCh MBMS-CommonCCTrChIdentity OPTIONAL, transpCHInformation MBMS-TrCHInformation-CurrList } MBMS-CurrentCell-SCCPCHList-r6 ::= SEQUENCE (SIZE (1..maxSCCPCH)) OF MBMS-CurrentCell-SCCPCH-r6 SEQUENCE (SIZE (1..maxFACHPCH)) OF TransportFormatSet SEQUENCE { P-TMSI-GSM-MAP
MBMS-FACHCarryingMTCH-List ::=
MBMS-JoinedInformation-r6 ::= p-TMSI }
OPTIONAL
3GPP
Release 6
987
3GPP TS 25.331 V6.23.0 (2009-09)
MBMS-L1CombiningSchedule-32 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..7) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..7), periodDuration INTEGER (1..8) } } MBMS-L1CombiningSchedule-64 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..15) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..15), periodDuration INTEGER (1..16) } } MBMS-L1CombiningSchedule-128 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..31) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..31), periodDuration INTEGER (1..32) } } MBMS-L1CombiningSchedule-256 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..63) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..63), periodDuration INTEGER (1..64) } } MBMS-L1CombiningSchedule-512 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..127) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..127), periodDuration INTEGER (1..128) } } MBMS-L1CombiningSchedule-1024 ::= SEQUENCE { -- Actual L1 combining schedule values (offset, start, duration) = IE value * 4 cycleOffset INTEGER (0..255) OPTIONAL, mtch-L1CombiningPeriodList SEQUENCE (SIZE (1..maxMBMS-L1CP)) OF SEQUENCE { periodStart INTEGER (0..255), periodDuration INTEGER (1..256) } } MBMS-L1CombiningSchedule ::= cycleLength-32 cycleLength-64 cycleLength-128 cycleLength-256 cycleLength-512 cycleLength-1024 } MBMS-L1CombiningTransmTimeDiff ::= CHOICE { MBMS-L1CombiningSchedule-32, MBMS-L1CombiningSchedule-64, MBMS-L1CombiningSchedule-128, MBMS-L1CombiningSchedule-256, MBMS-L1CombiningSchedule-512, MBMS-L1CombiningSchedule-1024
INTEGER (0..3)
MBMS-L23Configuration ::= CHOICE { sameAsCurrent SEQUENCE { currentCell-SCCPCH MBMS-SCCPCHIdentity, msch-ConfigurationInfo MBMS-MSCH-ConfigurationInfo-r6 OPTIONAL }, different SEQUENCE { -- If the IE transpCh-InfoCommonForAllTrCh is absent, the default TFCS as specified -- in 14.10.1 applies transpCh-InfoCommonForAllTrCh MBMS-CommonCCTrChIdentity OPTIONAL, transpCHInformation MBMS-TrCHInformation-NeighbList } }
3GPP
Release 6
MBMS-LogicalChIdentity ::= MBMS-MCCH-ConfigurationInfo-r6 ::= accessInfoPeriodCoefficient repetitionPeriodCoefficient modificationPeriodCoefficient rlc-Info tctf-Presence }
988
INTEGER (1..15) SEQUENCE { INTEGER (0..3), INTEGER (0..3), INTEGER (7..10), RLC-Info-MCCH-r6, MBMS-TCTF-Presence
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL
MBMS-MICHConfigurationInfo-r6 ::= SEQUENCE { michPowerOffset MBMS-MICHPowerOffset, mode CHOICE { fdd SEQUENCE { channelisationCode256 ChannelisationCode256, ni-CountPerFrame MBMS-NI-CountPerFrame, sttd-Indicator BOOLEAN }, tdd384 SEQUENCE { timeslot TimeslotNumber, midambleShiftAndBurstType MidambleShiftAndBurstType, channelisationCode DL-TS-ChannelisationCode, repetitionPeriodLengthOffset RepPerLengthOffset-MICH OPTIONAL, mbmsNotificationIndLength MBMS-MICHNotificationIndLength DEFAULT mn4 }, tdd128 SEQUENCE { timeslot TimeslotNumber-LCR-r4, midambleShiftAndBurstType MidambleShiftAndBurstType-LCR-r4, channelisationCodeList SEQUENCE (SIZE (1..2)) OF DL-TS-ChannelisationCode, repetitionPeriodLengthOffset RepPerLengthOffset-MICH OPTIONAL, mbmsNotificationIndLength MBMS-MICHNotificationIndLength DEFAULT mn4 } } } MBMS-MICHNotificationIndLength ::= MBMS-MICHPowerOffset ::= ENUMERATED { mn4, mn8, mn16 } INTEGER (-10..5)
MBMS-ModifedService-r6 ::= SEQUENCE { mbms-TransmissionIdentity MBMS-TransmissionIdentity, mbms-RequiredUEAction MBMS-RequiredUEAction-Mod, mbms-PreferredFrequency CHOICE { mcch MBMS-PFLIndex, dcch MBMS-PFLInfo } OPTIONAL, -- dummy is not used. If received it shall be ignored. dummy ENUMERATED { true } continueMCCHReading BOOLEAN } MBMS-ModifedServiceList-r6 ::=
OPTIONAL,
SEQUENCE (SIZE (1..maxMBMSservModif)) OF MBMS-ModifedService-r6 SEQUENCE { MBMS-MSCHSchedulingInfo RLC-Info-MSCH-r6 MBMS-TCTF-Presence
MBMS-MSCH-ConfigurationInfo-r6 ::= mschShedulingInfo rlc-Info tctf-Presence } MBMS-MSCHSchedulingInfo ::= schedulingPeriod-32-Offset schedulingPeriod-64-Offset schedulingPeriod-128-Offset schedulingPeriod-256-Offset schedulingPeriod-512-Offset schedulingPeriod-1024-Offset }
CHOICE { INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER
(0..31), (0..63), (0..127), (0..255), (0..511), (0..1023)
MBMS-NeighbouringCellSCCPCH-r6 ::= SEQUENCE { secondaryCCPCH-Info MBMS-CommonPhyChIdentity, secondaryCCPCHPwrOffsetDiff MBMS-SCCPCHPwrOffsetDiff OPTIONAL, layer1Combining CHOICE { fdd SEQUENCE { softComb-TimingOffset MBMS-SoftComb-TimingOffset, mbms-L1CombiningTransmTimeDiff MBMS-L1CombiningTransmTimeDiff, mbms-L1CombiningSchedule MBMS-L1CombiningSchedule OPTIONAL
3GPP
Release 6
}, tdd } OPTIONAL, mbms-L23Configuration }
989
3GPP TS 25.331 V6.23.0 (2009-09)
NULL MBMS-L23Configuration
MBMS-NeighbouringCellSCCPCHList-r6 ::= SEQUENCE (SIZE (1..maxSCCPCH)) OF MBMS-NeighbouringCellSCCPCH-r6 MBMS-NI-CountPerFrame ::= MBMS-NumberOfNeighbourCells-r6 ::= MBMS-PFLIndex ::= MBMS-PFLInfo ::= MBMS-PhyChInformation-r6 ::= mbms-CommonPhyChIdentity secondaryCCPCHInfo-MBMS } MBMS-PhyChInformationList-r6 ::= ENUMERATED { ni18, ni36, ni72, ni144 } INTEGER (0..32) INTEGER (1..maxMBMS-Freq) FrequencyInfo SEQUENCE { MBMS-CommonPhyChIdentity, SecondaryCCPCHInfo-MBMS-r6
SEQUENCE (SIZE (1..maxMBMS-CommonPhyCh)) OF MBMS-PhyChInformation-r6 ENUMERATED { true } SEQUENCE { FrequencyInfo
MBMS-PL-ServiceRestrictInfo-r6 ::= MBMS-PreferredFreqRequest-r6 ::= preferredFreqRequest } MBMS-PreferredFrequencyInfo-r6 ::= mbmsPreferredFrequency layerConvergenceInformation mbms-Qoffset mbms-HCSoffset }, mbms-PL-ServiceRestrictInfo } MBMS-PreferredFrequencyList-r6 ::=
SEQUENCE { INTEGER (1..maxMBMS-Freq) CHOICE { MBMS-Qoffset, INTEGER (0..7) MBMS-PL-ServiceRestrictInfo-r6
OPTIONAL,
OPTIONAL
SEQUENCE (SIZE (1..maxMBMS-Freq)) OF MBMS-PreferredFrequencyInfo-r6 INTEGER (0..2047) SEQUENCE { MBMS-CommonRBIdentity, MBMS-ShortTransmissionID, MBMS-LogicalChIdentity
MBMS-PTMActivationTime-r6 ::= MBMS-PTM-RBInformation-C ::= rbInformation shortTransmissionID logicalChIdentity } MBMS-PTM-RBInformation-CList ::=
SEQUENCE (SIZE (1..maxRBperTrCh)) OF MBMS-PTM-RBInformation-C SEQUENCE { MBMS-ShortTransmissionID, MBMS-LogicalChIdentity, BOOLEAN} SEQUENCE (SIZE (1..maxRBperTrCh)) OF MBMS-PTM-RBInformation-N ENUMERATED { q4, q8, q12, q16, q20, q30, q40, qInfinity } ENUMERATED { none, acquireCountingInfo, acquireCountingInfoPTM-RBsUnmodified, acquirePTM-RBInfo, requestPTPRB, releasePTM-RB } ENUMERATED { none, acquirePTM-RBInfo, requestPTPRB } INTEGER (1..maxSCCPCH)
MBMS-PTM-RBInformation-N ::= shortTransmissionID logicalChIdentity layer1-CombiningStatus MBMS-PTM-RBInformation-NList ::=
MBMS-Qoffset ::= MBMS-RequiredUEAction-Mod ::=
MBMS-RequiredUEAction-UMod ::=
MBMS-SCCPCHIdentity ::=
3GPP
Release 6
990
3GPP TS 25.331 V6.23.0 (2009-09)
MBMS-SCCPCHPwrOffsetDiff ::= MBMS-SelectedServiceInfo ::= status none some } } MBMS-SelectedServicesListFull ::=
ENUMERATED { mcpo-minus6, mcpo-minus3, mcpo-plus3, mcpo-plus6 } SEQUENCE { CHOICE { NULL, MBMS-SelectedServicesListFull
SEQUENCE (SIZE (1..maxMBMSservSelect)) OF MBMS-ServiceIdentity-r6 SEQUENCE (SIZE (1..maxMBMSservSelect)) OF MBMS-ShortTransmissionID SEQUENCE { MBMS-SelectedServicesListShort, INTEGER (0..1)
MBMS-SelectedServicesListShort ::=
MBMS-SelectedServicesShort ::= mbms-SelectedServicesList modificationPeriodIdentity }
MBMS-ServiceAccessInfo-r6 ::= SEQUENCE { shortTransmissionID MBMS-ShortTransmissionID, accessprobabilityFactor-Idle MBMS-AccessProbabilityFactor, accessprobabilityFactor-Connected MBMS-AccessProbabilityFactor mbms-ConnectedModeCountingScope MBMS-ConnectedModeCountingScope } MBMS-ServiceAccessInfoList-r6 ::=
OPTIONAL,
SEQUENCE (SIZE (1..maxMBMSservCount)) OF MBMS-ServiceAccessInfo-r6
MBMS-ServiceIdentity-r6 ::= SEQUENCE { serviceIdentity OCTET STRING (SIZE (3)), plmn-Identity CHOICE { -- The 'sameAsMIB-PLMN-Id' choice refers to the 'PLMN Identity' (R99) in MIB. sameAsMIB-PLMN-Id NULL, other CHOICE { -- The 'sameAsMIB-MultiPLMN-Id' choice refers to one of the (1..5) PLMN Identities -- provided in the 'Multiple PLMN List' (REL-6) in MIB. sameAsMIB-MultiPLMN-Id INTEGER (1..5), explicitPLMN-Id PLMN-Identity } } } MBMS-ServiceSchedulingInfo-r6 ::= mbms-TransmissionIdentity mbms-ServiceTransmInfoList nextSchedulingperiod } SEQUENCE { MBMS-TransmissionIdentity, MBMS-ServiceTransmInfoList INTEGER (0..31)
OPTIONAL,
MBMS-ServiceSchedulingInfoList-r6 ::= SEQUENCE (SIZE (1..maxMBMSservSched)) OF MBMS-ServiceSchedulingInfo-r6 MBMS-ServiceTransmInfo ::= SEQUENCE { -- Actual values (start, duration) = IE values * 4 start INTEGER (0..255), duration INTEGER (1..256) } MBMS-ServiceTransmInfoList ::= SEQUENCE (SIZE (1..maxMBMSTransmis)) OF MBMS-ServiceTransmInfo OCTET STRING (SIZE (1)) INTEGER (1..maxMBMSservUnmodif) SEQUENCE { MBMS-SCCPCHIdentity, MBMS-TrCHInformation-SIB5List
MBMS-SessionIdentity ::= MBMS-ShortTransmissionID ::= MBMS-SIBType5-SCCPCH-r6 ::= sccpchIdentity transpCHInformation } MBMS-SIBType5-SCCPCHList-r6 ::=
SEQUENCE (SIZE (1..maxSCCPCH)) OF MBMS-SIBType5-SCCPCH-r6 ENUMERATED { ms0, ms10, ms20, ms40 } ENUMERATED { false }
MBMS-SoftComb-TimingOffset ::= MBMS-TCTF-Presence ::=
3GPP
Release 6
991
3GPP TS 25.331 V6.23.0 (2009-09)
MBMS-TimersAndCounters-r6 ::= t-318 } MBMS-TransmissionIdentity ::= mbms-ServiceIdentity mbms-SessionIdentity } MBMS-TranspChInfoForCCTrCh-r6 ::= commonCCTrChIdentity transportFormatCombinationSet }
SEQUENCE { T-318
DEFAULT ms1000
SEQUENCE { MBMS-ServiceIdentity-r6, MBMS-SessionIdentity
OPTIONAL
SEQUENCE { MBMS-CommonCCTrChIdentity, TFCS
MBMS-TranspChInfoForEachCCTrCh-r6 ::= SEQUENCE (SIZE (1..maxMBMS-CommonCCTrCh)) OF MBMS-TranspChInfoForCCTrCh-r6 MBMS-TranspChInfoForEachTrCh-r6 ::= SEQUENCE (SIZE (1..maxMBMS-CommonTrCh)) OF MBMS-TranspChInfoForTrCh-r6 MBMS-TranspChInfoForTrCh-r6 ::= commonTrChIdentity transportFormatSet } MBMS-TrCHInformation-Curr ::= transpCh-Info rbInformation msch-ConfigurationInfo } MBMS-TrCHInformation-CurrList ::= SEQUENCE { MBMS-CommonTrChIdentity, TransportFormatSet
SEQUENCE { MBMS-CommonTrChIdentity, MBMS-PTM-RBInformation-CList MBMS-MSCH-ConfigurationInfo-r6
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxFACHPCH)) OF MBMS-TrCHInformation-Curr SEQUENCE { MBMS-CommonTrChIdentity, BOOLEAN, MBMS-PTM-RBInformation-NList MBMS-MSCH-ConfigurationInfo-r6
MBMS-TrCHInformation-Neighb ::= transpCh-Info transpCh-CombiningStatus rbInformation msch-ConfigurationInfo }
OPTIONAL, OPTIONAL
MBMS-TrCHInformation-NeighbList ::= SEQUENCE (SIZE (1..maxFACHPCH)) OF MBMS-TrCHInformation-Neighb MBMS-TrCHInformation-SIB5 ::= transpCh-Identity rbInformation msch-ConfigurationInfo } MBMS-TrCHInformation-SIB5List ::= SEQUENCE { INTEGER (1..maxFACHPCH), MBMS-PTM-RBInformation-CList MBMS-MSCH-ConfigurationInfo-r6
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxFACHPCH)) OF MBMS-TrCHInformation-SIB5 SEQUENCE { MBMS-TransmissionIdentity, MBMS-RequiredUEAction-UMod, MBMS-PFLIndex
MBMS-UnmodifiedService-r6 ::= mbms-TransmissionIdentity mbms-RequiredUEAction mbms-PreferredFrequency } MBMS-UnmodifiedServiceList-r6 ::=
OPTIONAL
SEQUENCE (SIZE (1..maxMBMSservUnmodif)) OF MBMS-UnmodifiedService-r6
END
11.4
BEGIN
Constant definitions
Constant-definitions DEFINITIONS AUTOMATIC TAGS ::=
hiPDSCHidentities hiPUSCHidentities hiRM maxAC maxAdditionalMeas
INTEGER INTEGER INTEGER INTEGER INTEGER
::= ::= ::= ::= ::=
64 64 256 16 4
3GPP
Release 6
maxASC maxASCmap maxASCpersist maxCCTrCH maxCellMeas maxCellMeas-1 maxCNdomains maxCPCHsets maxDPCH-DLchan maxDPDCH-UL maxDRACclasses maxE-DCHMACdFlow maxE-DCHMACdFlow-1 maxEDCHRL maxFACHPCH maxFreq maxFreqBandsFDD maxFreqBandsFDD-ext maxFreqBandsTDD maxFreqBandsGSM maxGERAN-SI maxGSMTargetCells maxHProcesses maxHSDSCHTBIndex maxHSDSCHTBIndex-tdd384 maxHSSCCHs maxInterSysMessages maxLoCHperRLC maxMAC-d-PDUsizes maxMBMS-CommonCCTrCh maxMBMS-CommonPhyCh maxMBMS-CommonRB maxMBMS-CommonTrCh maxMBMS-Freq maxMBMS-L1CP maxMBMSservCount maxMBMSservModif maxMBMSservSched maxMBMSservSelect maxMBMSservUnmodif maxMBMSTransmis maxMeasEvent maxMeasIntervals maxMeasParEvent maxNumCDMA2000Freqs maxNumGSMFreqRanges maxNumFDDFreqs maxNumTDDFreqs maxNoOfMeas maxOtherRAT maxOtherRAT-16 maxPage1 maxPCPCH-APsig maxPCPCH-APsubCh maxPCPCH-CDsig maxPCPCH-CDsubCh maxPCPCH-SF maxPCPCHs maxPDCPAlgoType maxPDSCH maxPDSCH-TFCIgroups maxPRACH maxPRACH-FPACH maxPredefConfig maxPUSCH maxQueueIDs maxRABsetup maxRAT maxRB maxRBallRABs maxRBMuxOptions maxRBperRAB maxRBperTrCh maxReportedGSMCells maxRL maxRL-1 maxRLCPDUsizePerLogChan maxRFC3095-CID INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::=
992
3GPP TS 25.331 V6.23.0 (2009-09)
8 7 6 8 32 31 4 16 8 6 8 8 7 4 8 8 8 15 -- maxFreqBandsFDD-ext ::= 22 (maxFreqBandsFDD 1) 4 16 8 32 8 64 512 4 4 2 8 32 32 32 32 4 4 8 32 16 8 64 4 8 3 2 8 32 8 8 16 15 16 8 16 12 16 12 7 64 8 8 256 16 8 16 8 8 16 16 32 27 8 8 16 8 8 7 32 16384
3GPP
Release 6
993
3GPP TS 25.331 V6.23.0 (2009-09)
maxROHC-PacketSizes-r4 INTEGER ::= 16 maxROHC-Profile-r4 INTEGER ::= 8 maxSat INTEGER ::= 16 maxSCCPCH INTEGER ::= 16 maxSIB INTEGER ::= 32 maxSIB-FACH INTEGER ::= 8 maxSIBperMsg INTEGER ::= 16 maxSRBsetup INTEGER ::= 8 maxSystemCapability INTEGER ::= 16 maxTF INTEGER ::= 32 maxTF-CPCH INTEGER ::= 16 maxTFC INTEGER ::= 1024 maxTFCsub INTEGER ::= 1024 maxTFCI-2-Combs INTEGER ::= 512 maxTGPS INTEGER ::= 6 maxTrCH INTEGER ::= 32 -- maxTrCHpreconf should be 16 but has been set to 32 for compatibility maxTrCHpreconf INTEGER ::= 32 maxTS INTEGER ::= 14 maxTS-1 INTEGER ::= 13 maxTS-2 INTEGER ::= 12 maxTS-LCR INTEGER ::= 6 maxTS-LCR-1 INTEGER ::= 5 maxURA INTEGER ::= 8 maxURNTI-Group INTEGER ::= 8 END
11.5
BEGIN IMPORTS
RRC information between network nodes
Internode-definitions DEFINITIONS AUTOMATIC TAGS ::=
HandoverToUTRANCommand, MeasurementReport, PhysicalChannelReconfiguration, RadioBearerReconfiguration, RadioBearerRelease, RadioBearerSetup, RRCConnectionSetupComplete-r3-add-ext-IEs, RRC-FailureInfo, TransportChannelReconfiguration, UECapabilityInformation-r3-add-ext-IEs FROM PDU-definitions -- Core Network IEs : CN-DomainIdentity, CN-DomainInformationList, CN-DomainInformationListFull, CN-DRX-CycleLengthCoefficient, NAS-SystemInformationGSM-MAP, -- UTRAN Mobility IEs : CellIdentity, URA-Identity, -- User Equipment IEs : AccessStratumReleaseIndicator, C-RNTI, ChipRateCapability, DL-CapabilityWithSimultaneousHS-DSCHConfig, DL-PhysChCapabilityFDD-v380ext, DL-PhysChCapabilityTDD, DL-PhysChCapabilityTDD-LCR-r4, GSM-Measurements, HSDSCH-physical-layer-category, FailureCauseWithProtErr, MaxHcContextSpace, MaximumAM-EntityNumberRLC-Cap, MaximumRLC-WindowSize, MaxNoPhysChBitsReceived, MaxNoDPDCH-BitsTransmitted, MaxPhysChPerFrame, MaxPhysChPerSubFrame-r4, MaxPhysChPerTS, MaxROHC-ContextSessions-r4,
3GPP
Release 6
MaxTS-PerFrame, MaxTS-PerSubFrame-r4, MinimumSF-DL, MultiModeCapability, MultiRAT-Capability, NetworkAssistedGPS-Supported, PhysicalChannelCapability-edch-r6, RadioFrequencyBandTDDList, RLC-Capability, RRC-MessageSequenceNumber, SecurityCapability, SimultaneousSCCPCH-DPCH-Reception, STARTList, STARTSingle, START-Value, SupportOfDedicatedPilotsForChEstimation, TransportChannelCapability, TxRxFrequencySeparation, U-RNTI, UE-CapabilityContainer-IEs, UE-MultiModeRAT-Capability, UE-PowerClassExt, UE-RadioAccessCapabBandFDDList, UE-RadioAccessCapabBandFDDList2, UE-RadioAccessCapabBandFDDList-ext, UE-RadioAccessCapability, UE-RadioAccessCapability-v370ext, UE-RadioAccessCapability-v380ext, UE-RadioAccessCapability-v3a0ext, UE-RadioAccessCapability-v3g0ext, UE-RadioAccessCapability-v4b0ext, UE-RadioAccessCapability-v590ext, UE-RadioAccessCapability-v5c0ext, UL-PhysChCapabilityFDD, UL-PhysChCapabilityFDD-r6, UL-PhysChCapabilityTDD, UL-PhysChCapabilityTDD-LCR-r4, Radio Bearer IEs : PredefinedConfigStatusList, PredefinedConfigValueTag, RAB-InformationSetupList, RAB-InformationSetupList-r4, RAB-InformationSetupList-r5, RAB-InformationSetupList-r6-ext, RAB-InformationSetupList-r6, RAB-InformationSetupList-v6b0ext, RB-Identity, SRB-InformationSetupList, SRB-InformationSetupList-r5, SRB-InformationSetupList-r6, Transport Channel IEs : CPCH-SetID, DL-CommonTransChInfo, DL-CommonTransChInfo-r4, DL-AddReconfTransChInfoList, DL-AddReconfTransChInfoList-r4, DL-AddReconfTransChInfoList-r5, DRAC-StaticInformationList, UL-CommonTransChInfo, UL-CommonTransChInfo-r4, UL-AddReconfTransChInfoList, UL-AddReconfTransChInfoList-r6, Physical Channel IEs : PrimaryCPICH-Info, TPC-CombinationIndex, ScramblingCodeChange, TGCFN, TGPSI, TGPS-ConfigurationParams, Measurement IEs : Event1j-r6, Hysteresis, Inter-FreqEventCriteriaList-v590ext, Intra-FreqEventCriteriaList-v590ext, IntraFreqEvent-1d-r5, IntraFreqReportingCriteria-1b-r5, InterRATCellInfoIndication, MeasuredResultsOnRACHinterFreq,
994
3GPP TS 25.331 V6.23.0 (2009-09)
--
--
--
--
3GPP
Release 6
MeasurementIdentity, MeasurementReportingMode, MeasurementType, MeasurementType-r4, MeasurementType-r6, AdditionalMeasurementID-List, PositionEstimate, ReportingCellStatus, TimeToTrigger, -- MBMS IEs : MBMS-JoinedInformation-r6, MBMS-SelectedServiceInfo, -- Other IEs : GERANIu-RadioAccessCapability, GSM-MS-RadioAccessCapability, InterRAT-UE-RadioAccessCapabilityList, InterRAT-UE-RadioAccessCapability-v590ext, InterRAT-UE-RadioAccessCapability-v690ext, UESpecificBehaviourInformation1idle, UESpecificBehaviourInformation1interRAT FROM InformationElements maxCNdomains, maxNoOfMeas, maxRB, maxRBallRABs, maxRFC3095-CID, maxSRBsetup, maxRL, maxTGPS FROM Constant-definitions ;
995
3GPP TS 25.331 V6.23.0 (2009-09)
-- Part 1: Class definitions similar to what has been defined in 11.1 for RRC messages -- Information that is tranferred in the same direction and across the same path is grouped ------*************************************************** RRC information, to target RNC *************************************************** RRC Information to target RNC sent either from source RNC or from another RAT
ToTargetRNC-Container ::= CHOICE { interRATHandoverInfo srncRelocation rfc3095-ContextInfo extension }
InterRATHandoverInfoWithInterRATCapabilities-r3, SRNC-RelocationInfo-r3, RFC3095-ContextInfo-r5, NULL
-- *************************************************** --- RRC information, target RNC to source RNC --- ***************************************************
TargetRNC-ToSourceRNC-Container ::= CHOICE { radioBearerSetup RadioBearerSetup, radioBearerReconfiguration RadioBearerReconfiguration, radioBearerRelease RadioBearerRelease, transportChannelReconfiguration TransportChannelReconfiguration, physicalChannelReconfiguration PhysicalChannelReconfiguration, rrc-FailureInfo RRC-FailureInfo, -- IE dl-DCCHmessage consists of an octet string that includes the IE DL-DCCH-Message dL-DCCHmessage OCTET STRING, extension NULL } -- Part 2: Container definitions, similar to the PDU definitions in 11.2 for RRC messages -- In alphabetical order
-- *************************************************** --- Handover to UTRAN information
3GPP
Release 6
996
3GPP TS 25.331 V6.23.0 (2009-09)
--- *************************************************** InterRATHandoverInfoWithInterRATCapabilities-r3 ::= CHOICE { r3 SEQUENCE { -- IE InterRATHandoverInfoWithInterRATCapabilities-r3-IEs also -- includes non critical extensions interRATHandoverInfo-r3 InterRATHandoverInfoWithInterRATCapabilities-r3-IEs, v390NonCriticalExtensions SEQUENCE { interRATHandoverInfoWithInterRATCapabilities-v390ext InterRATHandoverInfoWithInterRATCapabilities-v390ext-IEs, -- Reserved for future non critical extension v690NonCriticalExtensions SEQUENCE { interRATHandoverInfoWithInterRATCapabilities-v690ext InterRATHandoverInfoWithInterRATCapabilities-v690ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } InterRATHandoverInfoWithInterRATCapabilities-r3-IEs ::= SEQUENCE { -- The order of the IEs may not reflect the tabular format -- but has been chosen to simplify the handling of the information in the BSC -- Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList OPTIONAL, -- interRATHandoverInfo, Octet string is used to obtain 8 bit length field prior to -- actual information. This makes it possible for BSS to transparently handle information -- received via GSM air interface even when it includes non critical extensions. -- The octet string shall include the InterRATHandoverInfo information -- The BSS can re-use the 44.018 length field received from the MS interRATHandoverInfo OCTET STRING (SIZE (0..255)) } InterRATHandoverInfoWithInterRATCapabilities-v390ext-IEs ::= SEQUENCE { -- User equipment IEs failureCauseWithProtErr FailureCauseWithProtErr }
OPTIONAL
InterRATHandoverInfoWithInterRATCapabilities-v690ext-IEs ::= SEQUENCE { -- Other IEs ue-RATSpecificCapability-v690ext InterRAT-UE-RadioAccessCapability-v690ext } -- *************************************************** --- RFC3095 context, source RNC to target RNC --- *************************************************** RFC3095-ContextInfo-r5 ::= CHOICE { r5 SEQUENCE { rFC3095-ContextInfoList-r5 RFC3095-ContextInfoList-r5, -- Reserved for future non critical extension nonCriticalExtensions SEQUENCE {} OPTIONAL }, criticalExtensions SEQUENCE {} } RFC3095-ContextInfoList-r5 ::= SEQUENCE (SIZE (1..maxRBallRABs)) OF RFC3095-ContextInfo
OPTIONAL
-- *************************************************** --- SRNC Relocation information --- *************************************************** SRNC-RelocationInfo-r3 ::= CHOICE { r3 SEQUENCE { sRNC-RelocationInfo-r3 SRNC-RelocationInfo-r3-IEs, v380NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v380ext SRNC-RelocationInfo-v380ext-IEs, -- Reserved for future non critical extension v390NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v390ext SRNC-RelocationInfo-v390ext-IEs,
3GPP
Release 6
997
3GPP TS 25.331 V6.23.0 (2009-09)
} }
v3a0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v3a0ext SRNC-RelocationInfo-v3a0ext-IEs, v3b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v3b0ext SRNC-RelocationInfo-v3b0ext-IEs, v3c0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v3c0ext SRNC-RelocationInfo-v3c0ext-IEs, laterNonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v3d0ext SRNC-RelocationInfo-v3d0ext-IEs, -- Container for additional R99 extensions sRNC-RelocationInfo-r3-add-ext BIT STRING (CONTAINING SRNC-RelocationInfo-v3h0ext-IEs) OPTIONAL, v3g0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v3g0ext SRNC-RelocationInfo-v3g0ext-IEs, v4b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v4b0ext SRNC-RelocationInfo-v4b0ext-IEs, v590NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v590ext SRNC-RelocationInfo-v590ext-IEs, v5a0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5a0ext SRNC-RelocationInfo-v5a0ext-IEs, v5b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5b0ext SRNC-RelocationInfo-v5b0ext-IEs, v5c0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5c0ext SRNC-RelocationInfo-v5c0ext-IEs, v690NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v690ext SRNC-RelocationInfo-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v6b0ext SRNC-RelocationInfo-v6b0ext-IEs, -- Reserved for future non critical -- extension nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL OPTIONAL OPTIONAL
}, later-than-r3 CHOICE { r4 SEQUENCE { sRNC-RelocationInfo-r4 SRNC-RelocationInfo-r4-IEs, v4d0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v4d0ext SRNC-RelocationInfo-v4d0ext-IEs, -- Container for adding non critical extensions after freezing REL-5 sRNC-RelocationInfo-r4-add-ext BIT STRING OPTIONAL, v590NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v590ext SRNC-RelocationInfo-v590ext-IEs, v5a0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5a0ext SRNC-RelocationInfo-v5a0ext-IEs, v5b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5b0ext SRNC-RelocationInfo-v5b0ext-IEs, v5c0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5c0ext SRNC-RelocationInfo-v5c0ext-IEs, v690NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v690ext SRNC-RelocationInfo-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v6b0ext SRNC-RelocationInfo-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL
3GPP
Release 6
} OPTIONAL OPTIONAL
998
3GPP TS 25.331 V6.23.0 (2009-09)
}, criticalExtensions CHOICE { r5 SEQUENCE { sRNC-RelocationInfo-r5 SRNC-RelocationInfo-r5-IEs, sRNC-RelocationInfo-r5-add-ext BIT STRING OPTIONAL, v5a0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5a0ext SRNC-RelocationInfo-v5a0ext-IEs, v5b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5b0ext SRNC-RelocationInfo-v5b0ext-IEs, v5c0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v5c0ext SRNC-RelocationInfo-v5c0ext-IEs, v690NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v690ext SRNC-RelocationInfo-v690ext-IEs, v6b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v6b0ext SRNC-RelocationInfo-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL }, criticalExtensions CHOICE { r6 SEQUENCE { sRNC-RelocationInfo-r6 SRNC-RelocationInfo-r6-IEs, sRNC-RelocationInfo-r6-add-ext BIT STRING OPTIONAL, v6b0NonCriticalExtensions SEQUENCE { sRNC-RelocationInfo-v6b0ext SRNC-RelocationInfo-v6b0ext-IEs, nonCriticalExtensions SEQUENCE {} OPTIONAL } OPTIONAL }, criticalExtensions SEQUENCE {} } } } } SRNC-RelocationInfo-r3-IEs ::= SEQUENCE { -- Non-RRC IEs stateOfRRC StateOfRRC, stateOfRRC-Procedure StateOfRRC-Procedure, -- Ciphering related information IEs -- If the extension v380 is included use the extension for the ciphering status per CN domain cipheringStatus CipheringStatus, -- If ciphering status is started and the IE latestConfiguredCN-Domain should be included, -- the IE cn-DomainIdentity (in SRNC-RelocationInfo-v380ext-IEs) shall be used instead. calculationTimeForCiphering CalculationTimeForCiphering OPTIONAL, -- The order of occurrence in the IE cipheringInfoPerRB-List is the -- same as the RBs in SRB-InformationSetupList in RAB-InformationSetupList. -- The signalling RBs are supposed to be listed -- first. Only UM and AM RBs that are ciphered are listed here cipheringInfoPerRB-List CipheringInfoPerRB-List OPTIONAL, count-C-List COUNT-C-List OPTIONAL, integrityProtectionStatus IntegrityProtectionStatus, -- In the IE srb-SpecificIntegrityProtInfo, the first information listed corresponds to -- signalling radio bearer RB0 and after the order of occurrence is the same as the SRBs in -- SRB-InformationSetupList -- The target RNC may ignore the IE srb-SpecificIntegrityProtInfo if the -- IE integrityProtectionStatus has the value "not started". srb-SpecificIntegrityProtInfo SRB-SpecificIntegrityProtInfoList, implementationSpecificParams ImplementationSpecificParams OPTIONAL, -- User equipment IEs u-RNTI U-RNTI, c-RNTI C-RNTI OPTIONAL, ue-RadioAccessCapability UE-RadioAccessCapability, ue-Positioning-LastKnownPos UE-Positioning-LastKnownPos OPTIONAL, -- Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Core network IEs cn-CommonGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP, cn-DomainInformationList CN-DomainInformationList OPTIONAL, -- Measurement IEs ongoingMeasRepList OngoingMeasRepList OPTIONAL, -- Radio bearer IEs
3GPP
Release 6
999
3GPP TS 25.331 V6.23.0 (2009-09)
predefinedConfigStatusList PredefinedConfigStatusList, srb-InformationList SRB-InformationSetupList, rab-InformationList RAB-InformationSetupList OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo OPTIONAL, ul-TransChInfoList UL-AddReconfTransChInfoList OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { -- dummy and dummy2 are not used in this version of the specification, they should -- not be sent and if received they should be ignored. dummy CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL }, dl-CommonTransChInfo DL-CommonTransChInfo OPTIONAL, dl-TransChInfoList DL-AddReconfTransChInfoList OPTIONAL, -- Measurement report measurementReport MeasurementReport OPTIONAL } SRNC-RelocationInfo-v380ext-IEs ::= SEQUENCE { -- Ciphering related information IEs -- In the SRNC-RelocationInfo-r3-IEs, the IE 'cn-DomainIdentity' is used to represent the -- IE 'Latest configured CN domain' in the tabular. cn-DomainIdentity CN-DomainIdentity, cipheringStatusList CipheringStatusList } SRNC-RelocationInfo-v390ext-IEs ::= SEQUENCE { cn-DomainInformationList-v390ext CN-DomainInformationList-v390ext ue-RadioAccessCapability-v370ext UE-RadioAccessCapability-v370ext ue-RadioAccessCapability-v380ext UE-RadioAccessCapability-v380ext dl-PhysChCapabilityFDD-v380ext DL-PhysChCapabilityFDD-v380ext, failureCauseWithProtErr FailureCauseWithProtErr } SRNC-RelocationInfo-v3a0ext-IEs ::= SEQUENCE { cipheringInfoForSRB1-v3a0ext CipheringInfoPerRB-List-v3a0ext, ue-RadioAccessCapability-v3a0ext UE-RadioAccessCapability-v3a0ext -- cn-domain identity for IE startValueForCiphering-v3a0ext is specified -- in subsequent extension (SRNC-RelocationInfo-v3b0ext-IEs) startValueForCiphering-v3a0ext START-Value }
OPTIONAL,
SRNC-RelocationInfo-v3b0ext-IEs ::= SEQUENCE { -- cn-domain identity for IE startValueForCiphering-v3a0ext included in previous extension cn-DomainIdentity CN-DomainIdentity, -- the IE startValueForCiphering-v3b0ext contains the start values for each CN Domain. The -- value of start indicated by the IE startValueForCiphering-v3a0ext should be set to the -- same value as the start-Value for the corresponding cn-DomainIdentity in the IE -- startValueForCiphering-v3b0ext startValueForCiphering-v3b0ext STARTList2 OPTIONAL } SRNC-RelocationInfo-v3c0ext-IEs ::= SEQUENCE { -- IE rb-IdentityForHOMessage includes the identity of the RB used by the source SRNC -- to send the message contained in the IE TargetRNC-ToSourceRNC-Container. -- Only included if type is UE involved rb-IdentityForHOMessage RB-Identity OPTIONAL } SRNC-RelocationInfo-v3d0ext-IEs ::= SEQUENCE { -- User equipment IEs uESpecificBehaviourInformation1idle UESpecificBehaviourInformation1idle OPTIONAL, uESpecificBehaviourInformation1interRAT UESpecificBehaviourInformation1interRAT OPTIONAL } SRNC-RelocationInfo-v3g0ext-IEs ::= SEQUENCE { ue-RadioAccessCapability-v3g0ext UE-RadioAccessCapability-v3g0ext } SRNC-RelocationInfo-v3h0ext-IEs ::= SEQUENCE { tpc-CombinationInfoList TPC-CombinationInfoList nonCriticalExtension SEQUENCE {} }
OPTIONAL
OPTIONAL, OPTIONAL
3GPP
Release 6
1000
3GPP TS 25.331 V6.23.0 (2009-09)
SRNC-RelocationInfo-v4d0ext-IEs ::= SEQUENCE { tpc-CombinationInfoList TPC-CombinationInfoList } TPC-CombinationInfoList ::= SEQUENCE (SIZE (1..maxRL)) OF TPC-Combination-Info STARTList2 ::=
OPTIONAL
SEQUENCE (SIZE (2..maxCNdomains)) OF STARTSingle
SRNC-RelocationInfo-v4b0ext-IEs ::= SEQUENCE { ue-RadioAccessCapability-v4b0ext UE-RadioAccessCapability-v4b0ext }
OPTIONAL
SRNC-RelocationInfo-v590ext-IEs ::= SEQUENCE { ue-RadioAccessCapability-v590ext UE-RadioAccessCapability-v590ext OPTIONAL, ue-RATSpecificCapability-v590ext InterRAT-UE-RadioAccessCapability-v590ext OPTIONAL } SRNC-RelocationInfo-v5a0ext-IEs ::= SEQUENCE { storedCompressedModeInfo StoredCompressedModeInfo } SRNC-RelocationInfo-v5b0ext-IEs ::= SEQUENCE { interRATCellInfoIndication InterRATCellInfoIndication }
OPTIONAL
OPTIONAL
SRNC-RelocationInfo-v5c0ext-IEs ::= SEQUENCE { ue-RadioAccessCapability-v5c0ext UE-RadioAccessCapability-v5c0ext } CipheringInfoPerRB-List-v3a0ext ::= SEQUENCE { dl-UM-SN BIT STRING (SIZE (7)) } CipheringStatusList ::= SEQUENCE (SIZE (1..maxCNdomains)) OF CipheringStatusCNdomain SEQUENCE { CN-DomainIdentity, CipheringStatus
OPTIONAL
CipheringStatusCNdomain ::= cn-DomainIdentity cipheringStatus }
CodeChangeStatusList ::= SEQUENCE (SIZE (1..maxRL)) OF CodeChangeStatus CodeChangeStatus ::= SEQUENCE { primaryCPICH-Info scramblingCodeChange }
PrimaryCPICH-Info, ScramblingCodeChange
StoredCompressedModeInfo ::= SEQUENCE { storedTGP-SequenceList StoredTGP-SequenceList, codeChangeStatusList CodeChangeStatusList OPTIONAL } StoredTGP-SequenceList ::= SEQUENCE (SIZE (1..maxTGPS)) OF StoredTGP-Sequence SEQUENCE { TGPSI, CHOICE { SEQUENCE { TGCFN NULL TGPS-ConfigurationParams OPTIONAL
StoredTGP-Sequence ::= tgpsi current-tgps-Status active tgcfn }, inactive }, tgps-ConfigurationParams }
SRNC-RelocationInfo-r4-IEs ::= SEQUENCE { -- Non-RRC IEs -- IE rb-IdentityForHOMessage includes the identity of the RB used by the source SRNC -- to send the message contained in the IE TargetRNC-ToSourceRNC-Container. -- Only included if type is UE involved rb-IdentityForHOMessage RB-Identity OPTIONAL, stateOfRRC StateOfRRC, stateOfRRC-Procedure StateOfRRC-Procedure,
3GPP
Release 6
1001
3GPP TS 25.331 V6.23.0 (2009-09)
-- Ciphering related information IEs cipheringStatusList CipheringStatusList-r4, latestConfiguredCN-Domain CN-DomainIdentity, calculationTimeForCiphering CalculationTimeForCiphering OPTIONAL, count-C-List COUNT-C-List OPTIONAL, cipheringInfoPerRB-List CipheringInfoPerRB-List-r4 OPTIONAL, -- Integrity protection related information IEs integrityProtectionStatus IntegrityProtectionStatus, -- The target RNC may ignore the IE srb-SpecificIntegrityProtInfo if the -- IE integrityProtectionStatus has the value "not started". srb-SpecificIntegrityProtInfo SRB-SpecificIntegrityProtInfoList, implementationSpecificParams ImplementationSpecificParams OPTIONAL, -- User equipment IEs u-RNTI U-RNTI, c-RNTI C-RNTI OPTIONAL, ue-RadioAccessCapability UE-RadioAccessCapability-r4, ue-RadioAccessCapability-ext UE-RadioAccessCapabBandFDDList OPTIONAL, ue-Positioning-LastKnownPos UE-Positioning-LastKnownPos OPTIONAL, uESpecificBehaviourInformation1idle UESpecificBehaviourInformation1idle OPTIONAL, uESpecificBehaviourInformation1interRAT UESpecificBehaviourInformation1interRAT OPTIONAL, -- Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList OPTIONAL, -- UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, -- Core network IEs cn-CommonGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP, cn-DomainInformationList CN-DomainInformationListFull OPTIONAL, -- Measurement IEs ongoingMeasRepList OngoingMeasRepList-r4 OPTIONAL, -- Radio bearer IEs predefinedConfigStatusList PredefinedConfigStatusList, srb-InformationList SRB-InformationSetupList, rab-InformationList RAB-InformationSetupList-r4 OPTIONAL, -- Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-TransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-TransChInfoList DL-AddReconfTransChInfoList-r4 OPTIONAL, -- Measurement report measurementReport MeasurementReport OPTIONAL, failureCause FailureCauseWithProtErr OPTIONAL } SRNC-RelocationInfo-r5-IEs ::= SEQUENCE { -- Non-RRC IEs -- IE rb-IdentityForHOMessage includes the identity of the RB used by the source SRNC -- to send the message contained in the IE TargetRNC-ToSourceRNC-Container. -- Only included if type is "UE involved" rb-IdentityForHOMessage RB-Identity OPTIONAL, stateOfRRC StateOfRRC, stateOfRRC-Procedure StateOfRRC-Procedure, -- Ciphering related information IEs cipheringStatusList CipheringStatusList-r4, latestConfiguredCN-Domain CN-DomainIdentity, calculationTimeForCiphering CalculationTimeForCiphering OPTIONAL, count-C-List COUNT-C-List OPTIONAL, cipheringInfoPerRB-List CipheringInfoPerRB-List-r4 OPTIONAL, -- Integrity protection related information IEs integrityProtectionStatus IntegrityProtectionStatus, srb-SpecificIntegrityProtInfo SRB-SpecificIntegrityProtInfoList OPTIONAL, implementationSpecificParams ImplementationSpecificParams OPTIONAL, -- User equipment IEs u-RNTI U-RNTI, c-RNTI C-RNTI OPTIONAL, ue-RadioAccessCapability UE-RadioAccessCapability-r5, ue-RadioAccessCapability-ext UE-RadioAccessCapabBandFDDList OPTIONAL, ue-Positioning-LastKnownPos UE-Positioning-LastKnownPos OPTIONAL,
3GPP
Release 6
1002
3GPP TS 25.331 V6.23.0 (2009-09)
----
---
--
---}
uESpecificBehaviourInformation1idle UESpecificBehaviourInformation1idle OPTIONAL, uESpecificBehaviourInformation1interRAT UESpecificBehaviourInformation1interRAT OPTIONAL, Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList-r5 OPTIONAL, UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, Core network IEs cn-CommonGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP, cn-DomainInformationList CN-DomainInformationListFull OPTIONAL, Measurement IEs ongoingMeasRepList OngoingMeasRepList-r5 OPTIONAL, Radio bearer IEs predefinedConfigStatusList PredefinedConfigStatusList, srb-InformationList SRB-InformationSetupList-r5, rab-InformationList RAB-InformationSetupList-r5 OPTIONAL, Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-TransChInfoList UL-AddReconfTransChInfoList OPTIONAL, -- 'dummy', 'dummy1' and 'dummy2' are not used in this version of the specification, -- they should not be sent and if received they should be ignored. dummy CHOICE { fdd SEQUENCE { dummy1 CPCH-SetID OPTIONAL, dummy2 DRAC-StaticInformationList OPTIONAL }, tdd NULL } OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-TransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, PhyCH IEs tpc-CombinationInfoList TPC-CombinationInfoList OPTIONAL, Measurement report measurementReport MeasurementReport OPTIONAL, Other IEs failureCause FailureCauseWithProtErr OPTIONAL
SRNC-RelocationInfo-v690ext-IEs ::= SEQUENCE { -- User equipment IEs -- IE ueCapabilityContainer is used for the transparent transfer of capability information -- received from the UE ueCapabilityContainer BIT STRING (CONTAINING UE-CapabilityContainer-IEs) OPTIONAL, -- IE ueCapabilityContainer-RSC and IE ueCapabilityContainer-UCI are used for the -- transparent transfer of capability information received from the UE that was introduced -- in a release independent manner, i.e., transferred within a VLEC. These UE capabilities -- are included both in the RRC CONNECTION SETUP COMPLETE and the UE CAPABILITY INFORMATION -- messages. Only the VLEC of one message needs to be included i.e. the one from these -- messages that was last received. -- Case 1: If the last received message was a RRC CONNECTION SETUP COMPLETE (RSC) ueCapabilityContainer-RSC BIT STRING (CONTAINING RRCConnectionSetupComplete-r3-add-ext-IEs) OPTIONAL, -- Case 2: If the last received message was a UE CAPABILITY INFORMATION (UCI) ueCapabilityContainer-UCI BIT STRING (CONTAINING UECapabilityInformation-r3-add-ext-IEs) OPTIONAL, -- Radio bearer IEs rab-InformationSetupList RAB-InformationSetupList-r6-ext OPTIONAL, -- Measurement report measuredResultsOnRACHinterFreq MeasuredResultsOnRACHinterFreq OPTIONAL, -- MBMS IEs mbms-JoinedInformation MBMS-JoinedInformation-r6 OPTIONAL, -- Measurement IEs intraFreqReportingCriteria IntraFreqReportingCriteria-r6-ext OPTIONAL } SRNC-RelocationInfo-r6-IEs ::= SEQUENCE { -- Non-RRC IEs -- IE rb-IdentityForHOMessage includes the identity of the RB used by the source SRNC -- to send the message contained in the IE TargetRNC-ToSourceRNC-Container. -- Only included if type is "UE involved" rb-IdentityForHOMessage RB-Identity OPTIONAL, stateOfRRC StateOfRRC, stateOfRRC-Procedure StateOfRRC-Procedure, -- Ciphering related information IEs cipheringStatusList CipheringStatusList-r4, latestConfiguredCN-Domain CN-DomainIdentity,
3GPP
Release 6
1003
3GPP TS 25.331 V6.23.0 (2009-09)
--
--
----
--
--
--
--
--
--}
calculationTimeForCiphering CalculationTimeForCiphering OPTIONAL, count-C-List COUNT-C-List OPTIONAL, cipheringInfoPerRB-List CipheringInfoPerRB-List-r4 OPTIONAL, Integrity protection related information IEs integrityProtectionStatus IntegrityProtectionStatus, srb-SpecificIntegrityProtInfo SRB-SpecificIntegrityProtInfoList OPTIONAL, implementationSpecificParams ImplementationSpecificParams OPTIONAL, User equipment IEs u-RNTI U-RNTI, c-RNTI C-RNTI OPTIONAL, ue-RadioAccessCapability UE-RadioAccessCapability-r6, ue-RadioAccessCapability-ext UE-RadioAccessCapabBandFDDList OPTIONAL, ue-Positioning-LastKnownPos UE-Positioning-LastKnownPos OPTIONAL, uESpecificBehaviourInformation1idle UESpecificBehaviourInformation1idle OPTIONAL, uESpecificBehaviourInformation1interRAT UESpecificBehaviourInformation1interRAT OPTIONAL, -- IE ueCapabilityContainer is used for the transparent transfer of capability information -- received from the UE ueCapabilityContainer BIT STRING (CONTAINING UE-CapabilityContainer-IEs) OPTIONAL, -- IE ueCapabilityContainer-RSC and IE ueCapabilityContainer-UCI are used for the -- transparent transfer of capability information received from the UE that was introduced -- in a release independent manner, i.e., transferred within a VLEC. These UE capabilities -- are included both in the RRC CONNECTION SETUP COMPLETE and the UE CAPABILITY INFORMATION -- messages. Only the VLEC of one message needs to be included i.e. the one from these -- messages that was last received. -- Case 1: If the last received message was a RRC CONNECTION SETUP COMPLETE (RSC) ueCapabilityContainer-RSC BIT STRING (CONTAINING RRCConnectionSetupComplete-r3-add-ext-IEs) OPTIONAL, -- Case 2: If the last received message was a UE CAPABILITY INFORMATION (UCI) ueCapabilityContainer-UCI BIT STRING (CONTAINING UECapabilityInformation-r3-add-ext-IEs) OPTIONAL, Other IEs ue-RATSpecificCapability InterRAT-UE-RadioAccessCapabilityList-r5 OPTIONAL, UTRAN mobility IEs ura-Identity URA-Identity OPTIONAL, Core network IEs cn-CommonGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP, cn-DomainInformationList CN-DomainInformationListFull OPTIONAL, Measurement IEs ongoingMeasRepList OngoingMeasRepList-r6 OPTIONAL, interRATCellInfoIndication InterRATCellInfoIndication OPTIONAL, Radio bearer IEs predefinedConfigStatusList PredefinedConfigStatusList, srb-InformationList SRB-InformationSetupList-r6, rab-InformationList RAB-InformationSetupList-r6 OPTIONAL, Transport channel IEs ul-CommonTransChInfo UL-CommonTransChInfo-r4 OPTIONAL, ul-TransChInfoList UL-AddReconfTransChInfoList-r6 OPTIONAL, dl-CommonTransChInfo DL-CommonTransChInfo-r4 OPTIONAL, dl-TransChInfoList DL-AddReconfTransChInfoList-r5 OPTIONAL, PhyCH IEs tpc-CombinationInfoList TPC-CombinationInfoList OPTIONAL, storedCompressedModeInfo StoredCompressedModeInfo OPTIONAL, Measurement report measurementReport BIT STRING (CONTAINING MeasurementReport) OPTIONAL, Other IEs failureCause FailureCauseWithProtErr OPTIONAL, MBMS IEs mbms-JoinedInformation MBMS-JoinedInformation-r6 OPTIONAL
SRNC-RelocationInfo-v6b0ext-IEs ::= SEQUENCE { -- The order of the RABs in IE rab-InformationSetupListExt is the same as -- in IE rab-InformationSetupList that is included in this message rab-InformationSetupListExt RAB-InformationSetupList-v6b0ext OPTIONAL, mbmsSelectedServiceInfo MBMS-SelectedServiceInfo } -- IE definitions CalculationTimeForCiphering ::= cell-Id sfn } SEQUENCE { CellIdentity, INTEGER (0..4095)
3GPP
Release 6
CipheringInfoPerRB ::= dl-HFN ul-HFN } CipheringInfoPerRB-r4 ::= rb-Identity dl-HFN dl-UM-SN ul-HFN }
1004
SEQUENCE { BIT STRING (SIZE (20..25)), BIT STRING (SIZE (20..25))
3GPP TS 25.331 V6.23.0 (2009-09)
SEQUENCE { RB-Identity, BIT STRING (SIZE (20..25)), BIT STRING (SIZE (7)) BIT STRING (SIZE (20..25))
OPTIONAL,
-- TABULAR: CipheringInfoPerRB-List, multiplicity value numberOfRadioBearers -- has been replaced with maxRB. CipheringInfoPerRB-List ::= SEQUENCE (SIZE (1..maxRB)) OF CipheringInfoPerRB CipheringInfoPerRB-List-r4 ::= SEQUENCE (SIZE (1..maxRB)) OF CipheringInfoPerRB-r4
CipheringStatus ::=
ENUMERATED { started, notStarted } SEQUENCE (SIZE (1..maxCNdomains)) OF CipheringStatusCNdomain-r4 SEQUENCE { CN-DomainIdentity, CipheringStatus, START-Value
CipheringStatusList-r4 ::=
CipheringStatusCNdomain-r4 ::= cn-DomainIdentity cipheringStatus start-Value } CN-DomainInformation-v390ext ::= cn-DRX-CycleLengthCoeff }
SEQUENCE { CN-DRX-CycleLengthCoefficient
CN-DomainInformationList-v390ext ::=
SEQUENCE (SIZE (1..maxCNdomains)) OF CN-DomainInformation-v390ext
CompressedModeMeasCapability-r4 ::= SEQUENCE { fdd-Measurements BOOLEAN, -- TABULAR: The IEs tdd-Measurements, gsm-Measurements and multiCarrierMeasurements -- are made optional since they are conditional based on another information element. -- Their absence corresponds to the case where the condition is not true. tdd384-Measurements BOOLEAN OPTIONAL, tdd128-Measurements BOOLEAN OPTIONAL, gsm-Measurements GSM-Measurements OPTIONAL, multiCarrierMeasurements BOOLEAN OPTIONAL } COUNT-C-List ::= SEQUENCE (SIZE (1..maxCNdomains)) OF COUNT-CSingle SEQUENCE { CN-DomainIdentity, BIT STRING (SIZE (32))
COUNT-CSingle ::= cn-DomainIdentity count-C }
DL-PhysChCapabilityFDD-r4 ::= SEQUENCE { -- The IE maxNoDPCH-PDSCH-Codes only gives information on the maximum number of DPCH Codes. maxNoDPCH-PDSCH-Codes INTEGER (1..8), maxNoPhysChBitsReceived MaxNoPhysChBitsReceived, supportForSF-512 BOOLEAN, -- dummy, dummy2 and dummy3 are not used in this version of the specification -- and if received they should be ignored. dummy BOOLEAN, dummy2 SimultaneousSCCPCH-DPCH-Reception, dummy3 SupportOfDedicatedPilotsForChEstimation OPTIONAL } DL-PhysChCapabilityFDD-r5 ::= SEQUENCE { -- The IE maxNoDPCH-PDSCH-Codes only gives information on the maximum number of DPCH Codes. maxNoDPCH-PDSCH-Codes INTEGER (1..8), maxNoPhysChBitsReceived MaxNoPhysChBitsReceived, supportForSF-512 BOOLEAN, -- dummy, dumy2 and dummy3 are not used in this version of the specification -- and if received they should be ignored.
3GPP
Release 6
1005
3GPP TS 25.331 V6.23.0 (2009-09)
dummy BOOLEAN, dummy2 SimultaneousSCCPCH-DPCH-Reception, dummy3 SupportOfDedicatedPilotsForChEstimation fdd-hspdsch CHOICE { supported SEQUENCE { hsdsch-physical-layer-category HSDSCH-physical-layer-category, -- dummy and dummy2 are not used in this version of the specification -- and if received they should be ignored. dummy BOOLEAN, dummy2 BOOLEAN }, unsupported NULL } } DL-PhysChCapabilityTDD-r5 ::= maxTS-PerFrame maxPhysChPerFrame minimumSF supportOfPDSCH maxPhysChPerTS tdd384-hspdsch supported unsupported } } DL-PhysChCapabilityTDD-LCR-r5 ::= maxTS-PerSubFrame maxPhysChPerFrame minimumSF supportOfPDSCH maxPhysChPerTS supportOf8PSK tdd128-hspdsch supported unsupported } } DL-RFC3095-Context ::= rfc3095-Context-Identity dl-mode dl-ref-ir dl-ref-time dl-curr-time dl-syn-offset-id dl-syn-slope-ts dl-dyn-changed } ImplementationSpecificParams ::= SEQUENCE { MaxTS-PerFrame, MaxPhysChPerFrame, MinimumSF-DL, BOOLEAN, MaxPhysChPerTS, CHOICE { HSDSCH-physical-layer-category, NULL
OPTIONAL,
SEQUENCE { MaxTS-PerSubFrame-r4, MaxPhysChPerSubFrame-r4, MinimumSF-DL, BOOLEAN, MaxPhysChPerTS, BOOLEAN, CHOICE { HSDSCH-physical-layer-category, NULL
SEQUENCE { INTEGER (0..16383), ENUMERATED {u, o, r}, OCTET STRING ( SIZE (1..3000)), INTEGER (0..4294967295) OPTIONAL, INTEGER (0..4294967295) OPTIONAL, INTEGER (0..65535) OPTIONAL, INTEGER (0..4294967295) OPTIONAL, BOOLEAN
BIT STRING (SIZE (1..512))
IntegrityProtectionStatus ::=
ENUMERATED { started, notStarted }
InterRAT-UE-RadioAccessCapabilityList-r5 ::= SEQUENCE { interRAT-UE-RadioAccessCapability InterRAT-UE-RadioAccessCapabilityList, geranIu-RadioAccessCapability GERANIu-RadioAccessCapability } IntraFreqReportingCriteria-r6-ext ::= SEQUENCE { -- The content of the v690 non-critical extension should be -- considered as an extension of IE IntraFreqEventCriteriaList event Event1j-r6, hysteresis Hysteresis, timeToTrigger TimeToTrigger, reportingCellStatus ReportingCellStatus }
OPTIONAL
OPTIONAL
-- dummy is not used in this version of the specification, it should -- not be sent and if received it should be ignored. MaxHcContextSpace-r5 ::= ENUMERATED { dummy, by1024, by2048, by4096, by8192, by16384, by32768, by65536, by131072 } MeasurementCapability-r4 ::= SEQUENCE {
3GPP
Release 6
downlinkCompressedMode uplinkCompressedMode } MeasurementCommandWithType ::= setup modify release } MeasurementCommandWithType-r4 ::= setup modify release } MeasurementCommandWithType-r6 ::= setup modify release }
1006
3GPP TS 25.331 V6.23.0 (2009-09)
CompressedModeMeasCapability-r4, CompressedModeMeasCapability-r4
CHOICE { MeasurementType, NULL, NULL
CHOICE { MeasurementType-r4, NULL, NULL
CHOICE { MeasurementType-r6, NULL, NULL
OngoingMeasRep ::= SEQUENCE { measurementIdentity MeasurementIdentity, -- TABULAR: The CHOICE Measurement in the tabular description is included -- in MeasurementCommandWithType measurementCommandWithType MeasurementCommandWithType, measurementReportingMode MeasurementReportingMode OPTIONAL, additionalMeasurementID-List AdditionalMeasurementID-List OPTIONAL } OngoingMeasRep-r4 ::= SEQUENCE { measurementIdentity MeasurementIdentity, -- TABULAR: The CHOICE Measurement in the tabular description is included -- in MeasurementCommandWithType-r4. measurementCommandWithType MeasurementCommandWithType-r4, measurementReportingMode MeasurementReportingMode OPTIONAL, additionalMeasurementID-List AdditionalMeasurementID-List OPTIONAL } OngoingMeasRep-r5 ::= SEQUENCE { measurementIdentity MeasurementIdentity, -- TABULAR: The CHOICE Measurement in the tabular description is included -- in MeasurementCommandWithType-r4. measurementCommandWithType MeasurementCommandWithType-r4, measurementReportingMode MeasurementReportingMode OPTIONAL, additionalMeasurementID-List AdditionalMeasurementID-List OPTIONAL, measurementCommand-v590ext CHOICE { -- the choice "intra-frequency" shall be used for the case of intra-frequency measurement, -- as well as when intra-frequency events are configured for inter-frequency measurement intra-frequency Intra-FreqEventCriteriaList-v590ext, inter-frequency Inter-FreqEventCriteriaList-v590ext } OPTIONAL, intraFreqReportingCriteria-1b-r5 IntraFreqReportingCriteria-1b-r5 OPTIONAL, intraFreqEvent-1d-r5 IntraFreqEvent-1d-r5 OPTIONAL } OngoingMeasRep-r6 ::= measurementIdentity measurementCommandWithType measurementReportingMode additionalMeasurementID-List } OngoingMeasRepList ::= SEQUENCE { MeasurementIdentity, MeasurementCommandWithType-r6, MeasurementReportingMode AdditionalMeasurementID-List
OPTIONAL, OPTIONAL
SEQUENCE (SIZE (1..maxNoOfMeas)) OF OngoingMeasRep SEQUENCE (SIZE (1..maxNoOfMeas)) OF OngoingMeasRep-r4 SEQUENCE (SIZE (1..maxNoOfMeas)) OF OngoingMeasRep-r5 SEQUENCE (SIZE (1..maxNoOfMeas)) OF OngoingMeasRep-r6 SEQUENCE { BOOLEAN,
OngoingMeasRepList-r4 ::=
PDCP-Capability-r4 ::= losslessSRNS-RelocationSupport
3GPP
Release 6
supportForRfc2507 notSupported supported }, supportForRfc3095 notSupported supported maxROHC-ContextSessions reverseCompressionDepth } } }
1007
CHOICE { NULL, MaxHcContextSpace
3GPP TS 25.331 V6.23.0 (2009-09)
CHOICE { NULL, SEQUENCE { MaxROHC-ContextSessions-r4 INTEGER (0..65535)
DEFAULT s16, DEFAULT 0
PDCP-Capability-r5 ::= SEQUENCE { losslessSRNS-RelocationSupport BOOLEAN, supportForRfc2507 CHOICE { notSupported NULL, supported MaxHcContextSpace-r5 }, supportForRfc3095 CHOICE { notSupported NULL, supported SEQUENCE { maxROHC-ContextSessions MaxROHC-ContextSessions-r4 reverseCompressionDepth INTEGER (0..65535) supportForRfc3095ContextRelocation BOOLEAN } } } PDCP-Capability-r6 ::= SEQUENCE { losslessSRNS-RelocationSupport BOOLEAN, losslessDLRLC-PDUSizeChange ENUMERATED { true } supportForRfc2507 CHOICE { notSupported NULL, supported MaxHcContextSpace-r5 }, supportForRfc3095 CHOICE { notSupported NULL, supported SEQUENCE { maxROHC-ContextSessions MaxROHC-ContextSessions-r4 reverseCompressionDepth INTEGER (0..65535) supportForRfc3095ContextRelocation BOOLEAN } } } PhysicalChannelCapability-r4 ::= fddPhysChCapability downlinkPhysChCapability uplinkPhysChCapability } tdd384-PhysChCapability downlinkPhysChCapability uplinkPhysChCapability } tdd128-PhysChCapability downlinkPhysChCapability uplinkPhysChCapability } } PhysicalChannelCapability-r5 ::= fddPhysChCapability downlinkPhysChCapability uplinkPhysChCapability } tdd384-PhysChCapability downlinkPhysChCapability uplinkPhysChCapability } tdd128-PhysChCapability downlinkPhysChCapability uplinkPhysChCapability } } RF-Capability-r4 ::= fddRF-Capability
DEFAULT s16, DEFAULT 0,
OPTIONAL,
DEFAULT s16, DEFAULT 0,
SEQUENCE { SEQUENCE { DL-PhysChCapabilityFDD-r4, UL-PhysChCapabilityFDD OPTIONAL, SEQUENCE { DL-PhysChCapabilityTDD, UL-PhysChCapabilityTDD OPTIONAL, SEQUENCE { DL-PhysChCapabilityTDD-LCR-r4, UL-PhysChCapabilityTDD-LCR-r4 OPTIONAL
SEQUENCE { SEQUENCE { DL-PhysChCapabilityFDD-r5, UL-PhysChCapabilityFDD OPTIONAL, SEQUENCE { DL-PhysChCapabilityTDD-r5, UL-PhysChCapabilityTDD OPTIONAL, SEQUENCE { DL-PhysChCapabilityTDD-LCR-r5, UL-PhysChCapabilityTDD-LCR-r4 OPTIONAL
SEQUENCE { SEQUENCE {
3GPP
Release 6
ue-PowerClass txRxFrequencySeparation } tdd384-RF-Capability ue-PowerClass radioFrequencyBandTDDList chipRateCapability } tdd128-RF-Capability ue-PowerClass radioFrequencyBandTDDList chipRateCapability } } RFC3095-ContextInfo ::= rb-Identity rfc3095-Context-List } RFC3095-Context-List ::= dl-RFC3095-Context ul-RFC3095-Context } RLC-Capability-r5 ::= totalRLC-AM-BufferSize maximumRLC-WindowSize maximumAM-EntityNumber }
1008
UE-PowerClassExt, TxRxFrequencySeparation
3GPP TS 25.331 V6.23.0 (2009-09)
OPTIONAL, SEQUENCE { UE-PowerClassExt, RadioFrequencyBandTDDList, ChipRateCapability OPTIONAL, SEQUENCE { UE-PowerClassExt, RadioFrequencyBandTDDList, ChipRateCapability OPTIONAL
SEQUENCE { RB-Identity, RFC3095-Context-List
SEQUENCE (SIZE (1..maxRFC3095-CID)) OF SEQUENCE { DL-RFC3095-Context OPTIONAL, UL-RFC3095-Context OPTIONAL
SEQUENCE { TotalRLC-AM-BufferSize-r5, MaximumRLC-WindowSize, MaximumAM-EntityNumberRLC-Cap
SRB-SpecificIntegrityProtInfo ::= ul-RRC-HFN dl-RRC-HFN ul-RRC-SequenceNumber dl-RRC-SequenceNumber }
SEQUENCE { BIT STRING (SIZE (28)), BIT STRING (SIZE (28)), RRC-MessageSequenceNumber, RRC-MessageSequenceNumber
SRB-SpecificIntegrityProtInfoList ::= SEQUENCE (SIZE (4..maxSRBsetup)) OF SRB-SpecificIntegrityProtInfo StateOfRRC ::= ENUMERATED { cell-DCH, cell-FACH, cell-PCH, ura-PCH } ENUMERATED { awaitNoRRC-Message, awaitRB-ReleaseComplete, awaitRB-SetupComplete, awaitRB-ReconfigurationComplete, awaitTransportCH-ReconfigurationComplete, awaitPhysicalCH-ReconfigurationComplete, awaitActiveSetUpdateComplete, awaitHandoverComplete, sendCellUpdateConfirm, sendUraUpdateConfirm, -- dummy is not used in this version of specification -- It should not be sent dummy, otherStates
StateOfRRC-Procedure ::=
} TotalRLC-AM-BufferSize-r5 ::= ENUMERATED { kb10, kb50, kb100, kb150, kb200, kb300, kb400, kb500, kb750, kb1000 }
TPC-Combination-Info ::= SEQUENCE { primaryCPICH-Info tpc-CombinationIndex } UE-MultiModeRAT-Capability-r5 ::= multiRAT-CapabilityList multiModeCapability supportOfUTRAN-ToGERAN-NACC }
PrimaryCPICH-Info, TPC-CombinationIndex
SEQUENCE { MultiRAT-Capability, MultiModeCapability, BOOLEAN
3GPP
Release 6
1009
3GPP TS 25.331 V6.23.0 (2009-09)
UE-Positioning-Capability-r4 ::= SEQUENCE { standaloneLocMethodsSupported BOOLEAN, ue-BasedOTDOA-Supported BOOLEAN, networkAssistedGPS-Supported NetworkAssistedGPS-Supported, supportForUE-GPS-TimingOfCellFrames BOOLEAN, supportForIPDL BOOLEAN, rx-tx-TimeDifferenceType2Capable BOOLEAN, validity-CellPCH-UraPCH ENUMERATED { true } OPTIONAL, sfn-sfnType2Capability ENUMERATED { true } OPTIONAL } UE-Positioning-LastKnownPos ::= sfn cell-id positionEstimate } UE-RadioAccessCapability-r4 ::= accessStratumReleaseIndicator pdcp-Capability rlc-Capability transportChannelCapability rf-Capability physicalChannelCapability ue-MultiModeRAT-Capability securityCapability ue-positioning-Capability measurementCapability } SEQUENCE { INTEGER (0..4095), CellIdentity, PositionEstimate
SEQUENCE { AccessStratumReleaseIndicator, PDCP-Capability-r4, RLC-Capability, TransportChannelCapability, RF-Capability-r4, PhysicalChannelCapability-r4, UE-MultiModeRAT-Capability, SecurityCapability, UE-Positioning-Capability-r4, MeasurementCapability-r4
OPTIONAL
UE-RadioAccessCapability-r5 ::= SEQUENCE { accessStratumReleaseIndicator AccessStratumReleaseIndicator, dl-CapabilityWithSimultaneousHS-DSCHConfig DL-CapabilityWithSimultaneousHS-DSCHConfig pdcp-Capability PDCP-Capability-r5, rlc-Capability RLC-Capability-r5, transportChannelCapability TransportChannelCapability, rf-Capability RF-Capability-r4, physicalChannelCapability PhysicalChannelCapability-r5, ue-MultiModeRAT-Capability UE-MultiModeRAT-Capability-r5, securityCapability SecurityCapability, ue-positioning-Capability UE-Positioning-Capability-r4, measurementCapability MeasurementCapability-r4 OPTIONAL } UE-RadioAccessCapability-r6 ::= SEQUENCE { accessStratumReleaseIndicator AccessStratumReleaseIndicator, dl-CapabilityWithSimultaneousHS-DSCHConfig DL-CapabilityWithSimultaneousHS-DSCHConfig pdcp-Capability PDCP-Capability-r6, rlc-Capability RLC-Capability-r5, transportChannelCapability TransportChannelCapability, rf-Capability RF-Capability-r4, physicalChannelCapability PhysicalChannelCapability-r5, ue-MultiModeRAT-Capability UE-MultiModeRAT-Capability-r5, securityCapability SecurityCapability, ue-positioning-Capability UE-Positioning-Capability-r4, measurementCapability MeasurementCapability-r4 OPTIONAL } UL-RFC3095-Context ::= rfc3095-Context-Identity ul-mode ul-ref-ir ul-ref-time ul-curr-time ul-syn-offset-id ul-syn-slope-ts ul-ref-sn-1 } END SEQUENCE { INTEGER (0..16383), ENUMERATED {u, o, r}, OCTET STRING ( SIZE (1..3000)), INTEGER (0..4294967295) OPTIONAL, INTEGER (0..4294967295) OPTIONAL, INTEGER (0..65535) OPTIONAL, INTEGER (0..4294967295) OPTIONAL, INTEGER (0..65535) OPTIONAL
OPTIONAL,
OPTIONAL,
3GPP
Release 6
1010
3GPP TS 25.331 V6.23.0 (2009-09)
12
Message transfer syntax
Transfer syntax for RRC PDUs is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned as specified in X.691 [49], and with adapted final padding. If special encoding is used, it is indicated in the ECN module defined for each ASN.1 module. The use of special encoding is defined in [14]. The following encoding rules apply in addition to what has been specified in X.691 [49]: When a bit string value is placed in a bit-field as specified in 15.6 to 15.11 in [11], the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field.
The terms "leading bit" and "trailing bit" are defined in ITU-T Rec. X.680 | ISO/IEC 8824-1. When using the "bstring" notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right.
NOTE:
12.1
Structure of encoded RRC messages
An RRC PDU, which is the bit string that is exchanged between peer entities/ across the radio interface, is the concatenation of a basic production, an extension and padding, in that order. RRC PDUs shall be mapped to and from RLC SDUs upon transmission and reception as follows: when delivering an RRC PDU as an RLC SDU to the RLC layer for transmission, the first bit of the RRC PDU shall be represented as the first bit in the RLC SDU and onwards; and upon reception of an RLC SDU from the RLC layer, the first bit of the RLC SDU shall represent the first bit of the RRC PDU and onwards.
12.1.1
Basic production
The 'basic production' is obtained by applying UNALIGNED PER to the abstract syntax value (the ASN.1 description) as specified in X.691, except for the 0 to 7 bits added at the end to produce a multiple of 8 bits. The basic production can have any positive number of bits, not necessarily a multiple of 8 bits.
12.1.2
Extension
Emitters compliant with this version of the specification of the protocol shall, unless indicated otherwise on a PDU type basis, set the extension part empty. Emitters compliant with a later version might send non-empty extensions.
12.1.3
Padding
Emitters compliant with this version of the specification of the protocol shall, unless indicated otherwise on a PDU type basis, pad the basic production with the smallest number of bits required to meet the size constraints of the lower layers. Padding bits shall be set to 0. Receivers compliant with this version of the specification have no need to distinguish the extension and padding parts, and shall, unless indicated otherwise on a PDU type basis, accept RRC PDUs with any bit string in the extension and padding parts.
3GPP
Release 6
1011
3GPP TS 25.331 V6.23.0 (2009-09)
RRC- ASN.1
R99 part
Extension
ASN.1 encoder
Encoder added padding (0..7 bits) Basic production Extension
RRC padding encoder

RRC- PDU
RRC added padding
Figure 12.1.3-1: Padding When using AM or UM mode, RLC requires that the RRC PDU length is a multiple of 8 bits. When using Tr mode, RLC does neither impose size requirements nor perform padding. This implies that RRC has to take into account the transport format set defined for the transport channel across which the message is to be sent. RRC shall add the lowest number of padding bits required to fit the size specified for the selected transport format. For system information blocks, building the PDU involves two steps. The first step is the building of the System Information Blocks, in which step padding is not applied (the rules for extension apply). The second step is the building of the RRC PDUs, involving segmentation and concatenation of System Information Blocks, and then padding as described above for Tr mode. The procedure is shown by means of an example as described in Figure 12.1.3-2. The example includes two System Information Blocks, SIBn and SIBn+1, of which only SIBn includes a protocol extension. The two System Information Blocks used in the example do not require segmentation and are concatenated into one SYSTEM INFORMATION message.
3GPP
Release 6
1012
3GPP TS 25.331 V6.23.0 (2009-09)
SIBn- ASN.1
SIBn, r99 part
Extension
ASN.1 encoding
Encoder added padding (0..7 bits)
SIBn, r99 part
Extension
Segmentation & concatenation,
PCI
SIBn
PCI ASN.1 encoding
SIBn+1
PCI
SIBn
PCI
SIBn+1
RRC padding
RRC added padding SI- PDU
PCI SIBn, complete_Seg
PCI SIBn+1,first_Seg ASN.1
Figure 12.1.3-2: Padding for System Information PCI: Protocol control information at SYSTEM INFORMATION message level SI: SYSTEM INFORMATION message For system information blocks, RRC may also add padding information at the end of IE "SIB data fixed", used both within IE "Last segment" and IE "Complete SIB". The IE "SIB data fixed" has a fixed length i.e. no length denominator used. In case the remaining amount of "SIB data" information is insufficient to fill the IE completely, RRC includes padding bits. Since no length denominator is included, the receiving RRC cannot remove the padding added by the sender. However, since the padding used is the same as the padding added by the PER encoder to achieve octet alignment, the receiver can handle it. NOTE 1 The mechanism described above implies that the PDU provided to the ASN.1 decoder may have more than 7 padding bits included. For a complete System Information Block of length 215 bits, 11 padding bits are added by RRC. Since the decoder requires an octet aligned input, 6 additional bits need to be added. In this (worst) case, a total of 17 padding bits is included. NOTE 2 For the above cases, use of padding bits is possible and more efficient than including a length denominator.
3GPP
Release 6
1013
3GPP TS 25.331 V6.23.0 (2009-09)
When using the RRC padding described above, the segment has a fixed length, which completely fills the transport block. Therefore, in this case no RRC padding is added within the SYSTEM INFORMATION message. This is illustrated by means of the following figure.
SIBn- ASN.1
SIBn, r99 part
Extension
ASN.1 encoding
SIBn, r99 part
Extension
Segmentation & concatenation,
PCI
SIBn First segment
PCI
SIBn Last segment
ASN.1 encoding
RRC-PDU
PCI
SIBn Last segment
Figure 12.1.3-3: No RRC padding for System Information
12.2
ECN link module for RRC
RRC-ECN-Link-Module LINK-DEFINITIONS ::= BEGIN IMPORTS RRC-encodings FROM RRC-Encoding-Definitions;
-- Encoding objects for RRC messages
ENCODE Class-definitions WITH RRC-encodings COMPLETED BY PER-BASIC-UNALIGNED ENCODE PDU-definitions WITH RRC-encodings COMPLETED BY PER-BASIC-UNALIGNED ENCODE InformationElements WITH RRC-encodings COMPLETED BY PER-BASIC-UNALIGNED ENCODE Internode-definitions WITH RRC-encodings COMPLETED BY PER-BASIC-UNALIGNED END
3GPP
Release 6
1014
3GPP TS 25.331 V6.23.0 (2009-09)
12.3
ECN modules for RRC
The encoding definition module "RRC-Encoding-Definitions" contains definition of the encoding object set "RRC-encodings". The encoding object set contains all the specialized encoding for RRC.
RRC-Encoding-Definitions ENCODING-DEFINITIONS ::= BEGIN EXPORTS RRC-encodings; RRC-encodings #ENCODINGS ::= { -- Trailing bits outer-encoding } --************************************************************** --- The trailing bits in all RRC messages shall be ignored -- (including unknown message contents & unknown extensions). -- This overrides the default PER behaviour which pads the last -- octet with zero bits. ---************************************************************** outer-encoding #OUTER ::= { ENCODER-DECODER { } DECODE AS IF { POST-PADDING encoder-option } } END Class-definitions-ECN-Module ENCODING-DEFINITIONS ::= BEGIN END PDU-definitions-ECN-Module ENCODING-DEFINITIONS ::= BEGIN END InformationElements-ECN-Module ENCODING-DEFINITIONS ::= BEGIN END
Internode-definitions-ECN-Module ENCODING-DEFINITIONS ::= BEGIN END
12.4
NOTE:
RRC messages encoded otherwise

The messages included in this section are not specified by means of ASN.1.
12.4.1
Messages using tabular encoding specification
The encoding of the message is specified by means of a table listing the information elements known in the message and their order of their appearance in the message. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field.
3GPP
Release 6
1015
3GPP TS 25.331 V6.23.0 (2009-09)
12.4.1.1
TRANSPORT FORMAT COMBINATION CONTROL using transparent DCCH

TRANSPORT FORMAT COMBINATION CONTROL, 3 bit format
12.4.1.1.1
The 3 bit format is as follows:

3 0 0 0 1 2 0 0 1 1 1 0 1 0 1 Transport Format Combination Set Identity value 0 1 2 7
12.4.1.1.2
Void
12.4.1.1.3
Void
3GPP
Release 6
1016
3GPP TS 25.331 V6.23.0 (2009-09)
13
Protocol timers, counters, other parameters and default configurations
The information provided in subclauses 13.1 and 13.2 shall be treated as informative. The normative text is specified in the relevant subclauses in clause 8 and clause 8 shall prevail.
13.1
Timer T300
Timers for UE
Start Transmission of RRC CONNECTION REQUEST in case of connection establishment for reasons other than MBMS reception Transmission of CELL UPDATE/URA UPDATE Transmission of UE CAPABILITY INFORMATION Entering CELL_FACH or URA_PCH or CELL_PCH state. Reception of CELL UDPATE CONFIRM/URA UPDATE CONFIRM. When the timer T305 has expired and the UE detects "out of service area". Transmission of RRC CONNECTION RELEASE COMPLETE Upon reception of CELL CHANGE ORDER FROM UTRAN message Transmission of PUSCH CAPACITY REQUEST Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with the CHOICE "PUSCH allocation" set to "PUSCH allocation pending". When the UE starts to establish dedicated CH When the UE detects consecutive N313 "out of sync" indication from L1. When the criteria for radio link failure are fulfilled. The timer is started if radio bearer(s) that are associated with T314 exist of if only RRC connection exists. Stop Reception of RRC CONNECTION SETUP At expiry Retransmit RRC CONNECTION REQUEST if V300 =< N300, else go to Idle mode
T302
T304
Reception of CELL UPDATE CONFIRM/URA UPDATE CONFIRM Reception of UE CAPABILITY INFORMATION CONFIRM
T305
Entering another state.
T307
When the UE detects "in service area".
Retransmit CELL UPDATE/URA UPDATE if V302 =< N302, else, go to Idle mode Retransmit UE CAPABILITY INFORMATION if V304 =< N304, else initiate a cell update procedure Transmit CELL UPDATE if T307 is not activated and the UE detects "in service area". Otherwise, if T307 is not active, start T307. Transit to idle mode
T308
Not stopped
T309
T310
T311
Successful response to a connection establishment request in the new cell. Reception of PHYSICAL SHARED CHANNEL ALLOCATION Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with CHOICE "PUSCH allocation" set to "PUSCH allocation assignment". When the UE detects N312 "in sync" indication from L1. When the UE detects consecutive N315 "in sync" indication from L1. When the Cell Update procedure has been completed.
Transmit RRC CONNECTION RELEASE COMPLETE if V308 <=N308, else go to idle mode. Resume the connection to UTRAN Transmit PUSCH CAPACITY REQUEST if V310 =< N310, else procedure stops. UE may initiate a PUSCH capacity request procedure.
T312 T313
The criteria for physical channel establishment failure is fulfilled The criteria for Radio Link failure is fulfilled. See subclause 8.3.1.13.
T314
3GPP
Release 6 Timer T315 Start When the criteria for radio link failure are fulfilled. The timer is started only if radio bearer(s) that are associated with T315 exist. When the UE detects "out of service area" in URA_PCH or CELL_PCH state
1017 Stop When the Cell Update procedure has been completed.
3GPP TS 25.331 V6.23.0 (2009-09) At expiry See subclause 8.3.1.14.
T316
T317
T318
When the T316 expires or when in CELL_FACH state, the UE detects "out of service area". Transmission of RRC CONNECTION REQUEST in case of connection establishment for MBMS reception
Initiate cell update procedure if in service area is detected. Otherwise start timer T317, transit to CELL_FACH state and initiate cell update procedure when the UE detects "in service area". T317 never expires.
Reception of RRC CONNECTION SETUP
Enter idle mode
13.2
Counters for UE
Reset When initiating the procedure RRC connection establishment When initiating the procedure Cell update or URA update When sending the first UE CAPABILITY INFORMATION message. When sending the first RRC CONNECTION RELEASE COMPLETE message in a RRC connection release procedure. When sending the first PUSCH CAPACITY REQUEST message in a PUSCH capacity request procedure Incremented Upon expiry of T300. When reaching max value When V300 > N300, the UE enters idle mode. When V302 > N302 the UE enters idle mode. When V304 > N304 the UE initiates the Cell update procedure When V308 > N308 the UE stops re-transmitting the RRC CONNECTION RELEASE COMPLETE message.
Counter V300
V302
Upon expiry of T302
V304
Upon expiry of T304
V308
Upon expiry of T308
V310
Upon expiry of T310
When V310 > N310 the UE stops re-transmitting the PUSCH CAPACITY REQUEST message.
3GPP
Release 6
1018
3GPP TS 25.331 V6.23.0 (2009-09)
13.3
UE constants and parameters

Usage Maximum number of retransmissions of the RRC CONNECTION REQUEST message Maximum number of retransmissions of the CELL UPDATE / URA UPDATE message Maximum number of retransmissions of the UE CAPABILITY INFORMATION message Maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message Maximum number of retransmission of the PUSCH CAPACITY REQUEST message Maximum number of "in sync" received from L1. Maximum number of successive "out of sync" received from L1. Maximum number of successive "in sync" received from L1 during T313 is activated.
Constant N300 N302 N304 N308 N310 N312 N313 N315
13.4
UE variables
13.4.ob AM_RLC_ERROR_PENDING_RB234
This variable indicates whether an AM RLC unrecoverable error has been detected during the current cell update procedure on RB 2, 3, or 4.
Information Element/Group name AM RLC error pending Need MP Multi Type and reference Boolean Semantics description TRUE means an unrecoverable error was detected on AM RLC during the current cell update procedure.. Set to FALSE when the cell update procedure is completed.
13.4.oc AM_RLC_ERROR_PENDING_RB5_AND_UP
This variable indicates whether an AM RLC unrecoverable error has been detected during the current cell update procedure on RB 5 or above.
Information Element/Group name AM RLC error pending Need MP Multi Type and reference Boolean Semantics description TRUE means an unrecoverable error was detected on AM RLC during the current cell update procedure.. Set to FALSE when the cell update procedure is completed.
13.4.0
CELL_INFO_LIST
This variable contains cell information on intra-frequency, inter-frequency and inter-RAT cells, as received in messages System Information Block Type 11, System Information Block Type 12, and MEASUREMENT CONTROL. The first position in Intra-frequency cell info list corresponds to Intra-frequency cell id 0, the second to Intra-frequency cell id 1, etc. The first position in Inter-frequency cell info list corresponds to Inter-frequency cell id 0, the second to Inter-frequency cell id 1, etc.
3GPP
Release 6
1019
3GPP TS 25.331 V6.23.0 (2009-09)
The first position in Inter-RAT cell info list corresponds to Intra-frequency cell id 0, the second to Inter-RAT cell id 1, etc. This variable shall be cleared at cell re-selection, when leaving UTRA RRC connected mode, when switched off as well as at selection of a new PLMN.
Information Element/Group name Intra-frequency cell info >CHOICE position status >>Occupied >>>Cell info >>Vacant Inter-frequency cell info >CHOICE position status >>Occupied >>>Frequency info Need OP MP MP Cell info 10.3.7.2 No data OP MP MP Frequency info 10.3.6.36 Cell info 10.3.7.2 No data OP OP MP REL-5 1..<maxCel lMeas> 1..<maxCel lMeas> Multi 1..<maxCel lMeas> Type and reference Semantics description Version
>>>Cell info >>Vacant Inter-RAT cell info list >Inter-RAT cell info >>CHOICE position status >>>Occupied >>>>CHOICE Radio Access Technology >>>>>GSM >>>>>>Cell selection and reselection info
MP
MP
>>>>>>BSIC >>>>>>BCCH ARFCN >>>>>IS-2000 >>>>>>System specific measurement info
MP MP
Cell selection and reselection info for SIB11/12 10.3.2.4 BSIC 10.3.8.2 Integer (0..1023) enumerated (frequency, timeslot, colour code, output power, PN offset)
[43]
For IS-2000, use fields from TIA/EIA/IS-2000.5, subclause 3. 7.3.3.2.27, Candidate Frequency Neighbour List Message
>>>Vacant >CHOICE indication status >>Present >>>Inter-RAT cell info indication >>Not present
No data MP OP Integer (0..3) No data REL-5 REL-5 REL-5 REL-5
13.4.00 Void
13.4.0a CELL_UPDATE_STARTED
This variable indicates whether a cell update or URA update procedure is in progress.
3GPP
Release 6 Information Element/Group name Cell update started Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE means a cell or URA update procedure is in progress. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.1
CIPHERING_STATUS
Need MP Multi <1 to maxCNDo mains> CN domain identity 10.3.1.1 Enumerated( Not started, Started) Type and reference Semantics description
This variable contains information about the current status of ciphering in the UE.
Information Element/Group name Status for each CN domain
>CN domain identity
MP
>Status
MP
Reconfiguration
MP
Boolean
Set to "Not started" when entering UTRA RRC connected mode. Set to "Not started" when leaving UTRA RRC connected mode. TRUE means an RRC procedure performing reconfiguration of ciphering is ongoing. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.2
Void
13.4.2a CONFIGURATION_INCOMPLETE
This variable indicates whether a received measurement control message contains invalid an incomplete measurement configuration.
Information Element/Group name Configuration incomplete Need MP Multi Type and reference Boolean Semantics description TRUE: An incomplete configuration has been detected. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.3
C_RNTI
This variable stores the assigned C-RNTI for this UE when in CELL_FACH state.
3GPP
Release 6 Information Element/Group name C-RNTI Need OP
1021 Multi Type and reference C-RNTI 10.3.3.8
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode.
13.4.3o DSAC_PARAM
This variable contains Domain Specific Access Restriction Parameters during the connected mode.
Information Element/Group name CS Domain Specific Access Restriction Need MP Multi Type and reference Domain Access Restriction 10.3.1.3b Domain Access Restriction 10.3.1.3b Semantics description This IE contains CS Domain Specific Access Restriction Parameters Version REL-6
PS Domain Specific Access Restriction
MP
This IE contains PS Domain Specific Access Restriction Parameters
REL-6
13.4.3a DSCH_RNTI
In TDD this variable stores the assigned DSCH-RNTI for this UE when in CELL_DCH state.
Information Element/Group name DSCH-RNTI Need OP Multi Type and reference DSCH-RNTI 10.3.3.9a Semantics description Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode.
13.4.4
Void
13.4.4o E_DCH_TRANSMISSION
This variable indicates whether E-DPDCH and E-DPCCH transmission procedures are ongoing. See subclause 8.5.28 for actions related to the setting of this variable.
3GPP
Release 6 Information Element/Group name E-DCH transmission Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE: E-DCH transmission is ongoing. Set to FALSE when entering UTRA RRC connected mode when not otherwise stated in the procedure. Set to FALSE when leaving UTRA RRC connected mode. Version REL-6
13.4.4a E_RNTI
Information Element/Group name Primary E-RNTI Need OP Multi Type and reference E-RNTI 10.3.3.10a Semantics description Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode. Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode. Version REL-6
Secondary E-RNTI
OP
E-RNTI 10.3.3.10a
REL-6
13.4.5
ESTABLISHED_RABS
This variable is used to store information about the established radio access bearers and signalling radio bearers in the UE.
Information Element/Group name RAB information Need OP Multi 1 to <maxRABs etup> Type and reference Semantics description For each RAB established. Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode. RAB info 10.3.4.8 1 to <maxRBpe r RAB> RB identity 10.3.4.16 Integer(0..< For each RB belonging to the RAB
>RAB info >RB information
MP MP
>>RB identity >>Subflow
MP MP
Reference to the RAB subflow
3GPP
1023 Multi Type and reference maxSubflow count>) Enumerated( stopped, started)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description implemented by this RB Default value is started
>>RB started
MD
Signalling radio bearer information
OP
1 to < maxSRBse tup> Enumerated( stopped, started)
>RB started
MD
In the order of RB0 and upwards. Cleared when leaving UTRA RRC connected mode. Default value is started
13.4.5a ESTABLISHED_SIGNALLING_CONNECTIONS
This variable is used to store information about established signalling connections.
Information Element/Group name Signalling connection list Need OP Multi 1 to <maxCNdo mains> Type and reference Semantics description For each established signalling connection. Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode. CN domain identity 10.3.1.1
>Signalling connection identity
MP
13.4.6
ESTABLISHMENT_CAUSE
This variable is used to store the cause for establishment of a signalling connection received by upper layers, to be used at RRC connection establishment or Initial Direct Transfer.
Information Element/Group name Establishment cause Need OP Multi Type and reference Establishme nt cause 10.3.3.11 Semantics description Cleared when leaving UTRA RRC connected mode.
13.4.7
FAILURE_CAUSE
Need OP Multi Type and reference Failure cause 10.3.3.13 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
This variable contains the cause for failure of a UE initiated procedure, to be reported in a retransmitted message.
Information Element/Group name Failure cause
13.4.8
FAILURE_INDICATOR
This variable indicates whether the procedure has failed for a UE initiated procedure.
3GPP
Release 6 Information Element/Group name Failure indicator Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE: Procedure has failed. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.8o H_RNTI
This variable stores the assigned H-RNTI for this UE when in CELL-DCH state and a HS-DSCH transport channel has been allocated.
Information Element/Group name H-RNTI Need OP Multi Type and reference H-RNTI 10.3.3.14a Semantics description Cleared when entering UTRA RRC connected mode when not otherwise stated in the procedure. Cleared when leaving UTRA RRC connected mode. Version REL-5
13.4.8oo HS_DSCH_RECEPTION
This variable indicates whether HS-SCCH and HS-DSCH reception procedures are ongoing. See subclause 8.5.25 for actions related to the setting of this variable.
Information Element/Group name HS-DSCH reception Need MP Multi Type and reference Boolean Semantics description TRUE: HS-DSCH reception is ongoing. Set to FALSE when entering UTRA RRC connected mode when not otherwise stated in the procedure. Set to FALSE when leaving UTRA RRC connected mode. Version REL-5
13.4.8a INCOMPATIBLE_SECURITY_RECONFIGURATION
This variable indicates whether an incompatible simultaneous reconfiguration of a security function has been received.
3GPP
Release 6 Information Element/Group name Incompatible security reconfiguration Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description TRUE: An incompatible simultaneous security reconfiguration has been detected. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.9
INITIAL_UE_IDENTITY
Need OP Multi Type and reference Initial UE identity 10.3.3.15 Semantics description Cleared when leaving UTRA RRC connected mode.
In this variable the identity used by the UE when establishing an RRC connection is stored.
Information Element/Group name Initial UE identity
13.4.9a INTEGRITY_PROTECTION_ACTIVATION_INFO
This variable contains information to be sent to UTRAN about when a new integrity protection configuration shall be activated in the uplink for signalling radio bearers in case of modification of integrity protection.
Information Element/Group name Uplink Integrity protection activation info Need OP Multi Type and reference Integrity protection activation info 10.3.3.17 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.10 INTEGRITY_PROTECTION_INFO
This variable contains information about the current status of the integrity protection in the UE.
Information Element/Group name Status Need MP Multi Type and reference Enumerated( Not started, Started) Semantics description Set to "Not started" when entering UTRA RRC connected mode. Set to "Not started" when leaving UTRA RRC connected mode. TRUE means a reconfiguration of integrity protection is ongoing. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode. When integrity protection is started, status information for RB0- RB4 in that order. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
Reconfiguration
MP
Boolean
Signalling radio bearer specific integrity protection information
OP
1 to <maxSRBs etup>
>Uplink RRC HFN
MP
Bit string (28)
3GPP
Release 6 Information Element/Group name >Downlink RRC HFN >Uplink RRC Message sequence number >Downlink RRC Message sequence number Need MP MP OP
1026 Multi Type and reference Bit string (28) Integer (0.. 15) Integer (0.. 15)
13.4.10a INTER_RAT_HANDOVER_INFO_TRANSFERRED
This variable stores information about the inter RAT handover info that has been transferred to another RAT.
3GPP
1027 Type and referenc e Predefin ed configura tion status informati on 10.3.4.5 a Predefin ed configura tion status informati on compres sed 10.3.4.5 b UE security informati on 10.3.3.4 2b UE security informati on2 10.3.3.4 2c UE radio access capabilit y 10.3.3.4 2 UE radio access capabilit y extensio n 10.3.3.4 2a UE radio access capabilit y compres sed 10.3.3.4 2o InterRAT UE radio access capabilit y 10.3.8.7 InterRAT UE radio
Predefined configuration status information
OP
Cleared upon entering connected mode in another RAT
OP
REL-5
OP
OP
REL-6
OP
OP
OP
REL-5
UE system specific capability
OP
1 to <maxSyst emCapab ility>
MP
3GPP
Release 6
1028 access capabilit y 10.3.8.7
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.11 INVALID_CONFIGURATION
This variable indicates whether a received message contained an invalid configuration, by means of invalid values or invalid combinations of information elements.
Information Element/Group name Invalid configuration Need MP Multi Type and reference Boolean Semantics description TRUE: An invalid configuration has been detected. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.11a LATEST_CONFIGURED_CN_DOMAIN
This variable stores the CN-domain that was most recently configured to be used for ciphering and integrity protection.
Information Element/Group name Latest configured CN domain Need OP Multi Type and reference CN domain identity 10.3.1.1 Semantics description Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when leaving UTRA RRC connected mode.
13.4.11b LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE
This variable stores the SRB delay and PC preamble to be used for establishing the DPCH after failure of hard handover, inter-RAT handover from UTRAN, or cell change order from UTRAN.
Information Element/Group name SRB delay Need OP Multi Type and reference Integer (0..7) Semantics description Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure.
PC preamble
OP
Integer (0..7)
13.4.11c MBMS_ACTIVATED_SERVICES
This variable stores the MBMS multicast services the UE has joined as well as the MBMS broadcast services the UE is interested to receive. Whenever the list of joined multicast services and/ or interested broadcast services changes, upper layers provide an indication upon which the UE shall update the variable accordingly. In case upper layers de-select an MBMS Selected Services, the UE shall remove the concerned service from the variable. Likewise, when upper layers select an MBMS Selected Services, the UE shall add the concerned service to the variable.
3GPP
Release 6 Information Element/Group name Activated service list Need OP
1029 Multi 1 to <maxMBM SServices> MBMS Service identity 10.3.9a.8 Enumerated (Multicast, Broadcast) Boolean Type and reference
>Service Identity
MP
>Service type
MP
>MBMS Selected Services Indicator
CVBroadcast
TRUE means that the service is currently a MBMS Selected Service
Condition Broadcast
Explanation This IE is mandatory present if the IE "Service type" is set to Broadcast and not needed otherwise.
13.4.11d MBMS_PREV_FREQUENCY_INFO
This variable stores the frequency information of the cell the UE is camped on, upon moving to the MBMS preferred layer indicated MBMS FLC preferred frequency information.
Information Element/Group name PREV Frequency Information CHOICE mode >FDD cell >>UARFCN downlink (Nd) >3.84 Mcps TDD cell >>UARFCN (Nt) >1.28 Mcps TDD cell list >>UARFCN (Nt) Need Multi Type and reference Semantics description Version
MP
Integer(0 .. 16383) Integer(0 .. 16383) Integer(0 .. 16383)
[21]
MP
[22]
MP
[22]
13.4.11e MBMS_PL_SERVICE_RESTRICTION_INFO_DEDICATED
This variable stores the value of the IE "MBMS PL Service Restriction Information" restriction applicable to preferred frequency received in the latest Radio Bearer Control or Cell Update Confirm message.
Information Element/Group name MBMS_PL_SERVICE_RESTRI CTION_INFO_DEDICATED Need MP Multi Type and reference Enumerated( TRUE, FALSE) Semantics description Set to FALSE when entering UTRA connected mode. Version REL-6
13.4.12 MEASUREMENT_IDENTITY
This variable stores the measurements configured in the UE. For each configured measurement, the information below shall be stored.
3GPP
Release 6 Information Element/Group name MEASUREMENT CONTROL Need OP
1030 Multi Type and reference MEASUREM ENT CONTROL 10.2.17, System Information Block type 11 10.2.48.8.12, System Information Block type 12 10.2.48.8.13
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Information as contained in these messages. Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure (8.4.1.8-8.4.1.9). Cleared when leaving UTRA RRC connected mode when not stated otherwise in the procedure (8.4.1.9a).
13.4.13 Void
13.4.14 ORDERED_RECONFIGURATION
This variable stores information about an ongoing Reconfiguration procedure.
Information Element/Group name Ordered reconfiguration Need MP Multi Type and reference Boolean Semantics description TRUE means that a Reconfiguration procedure is ongoing. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.14a PDCP_ROHC_TARGET_MODE
This variable contains the ROHC target mode.
Information Element/Group name Target Mode Need OP Multi Type and reference Enumerated (O-mode, Rmode) Semantics description The UE shall only transit to the signalled mode for operation of ROHC as decribed in [36]. Version REL-5
13.4.15 PDCP_SN_INFO
This variable contains PDCP receive sequence numbers for one or several radio bearers to be included in a response message to UTRAN.
3GPP
Release 6 Information Element/Group name RB with PDCP information list Need OP
1031 Multi 1 to <maxRBall RABs> RB with PDCP information 10.3.4.22 Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>RB with PDCP information
MP
13.4.15a PHYSICAL_SHARED_CHANNEL_CONFIGURATION
This variable is used only for TDD to store information about the physical shared channel configuration in the UE.
Information Element/Group name PUSCH configuration Need OP Multi Type and reference Semantics description Cleared when entering and leaving UTRA RRC connected mode. PUSCH info 10.3.6.63 Integer(1.. hiPUSCHide ntities) PUSCH power control info 10.3.6.65 Cleared when entering and leaving UTRA RRC connected mode. PDSCH Info 10.3.6.44 Integer(1..hi PDSCHident ities) PDSCH power control info 10.3.6.45 1 to maxTS Timeslot number 10.3.6.84 Cleared when entering and leaving UTRA RRC connected mode. Timeslot numbers, for which the UE shall report the timeslot ISCP in PUSCH CAPACITY REQUEST message
>PUSCH info >PUSCH Identity
MP OP
>PUSCH power control info
OP
PDSCH configuration
OP
>PDSCH Info >PDSCH Identity
MP OP
>PDSCH power control info
OP
ISCP Timeslot list
OP
>Timeslot number
MP
13.4.16 PROTOCOL_ERROR_INDICATOR
This variable indicates whether there exist a protocol error that is to be reported to UTRAN.
Information Element/Group name Protocol error indicator Need MP Multi Type and reference Protocol error indicator 10.3.3.27 Semantics description Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
3GPP
Release 6
1032
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.17 PROTOCOL_ERROR_INFORMATION
This variable contains diagnostics to be reported to UTRAN for a message that was not completely understood.
Information Element/Group name Protocol error information Need OP Multi Type and reference Protocol error information 10.3.8.12 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.18 PROTOCOL_ERROR_REJECT
This variable indicates whether there has occurred a severe protocol error causing the ongoing procedure to fail.
Information Element/Group name Protocol error reject Need MP Multi Type and reference Boolean Semantics description TRUE: a severe protocol error has occurred. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.19 RB_TIMER_INDICATOR
This variable contains information to be sent to UTRAN if any of the timers T314 or T315 has expired when the UE sends a cell update with cause RL failure.
Information Element/Group name RB timer indicator Need OP Multi Type and reference RB timer indicator 10.3.3.28 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.20 RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO
This variable contains information to be sent to UTRAN about when a new ciphering configuration shall be activated in the uplink for radio bearers using RLC-AM or RLC-UM.
Information Element/Group name RB uplink ciphering activation time info Need OP Multi Type and reference RB activation time info 10.3.4.13 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.20a SECURITY_MODIFICATION
This variable contains information on which CN domain is affected by the ongoing security reconfiguration.
Information Element/Group name Need Multi Type and reference Semantics description
3GPP
Release 6 Status for each CN domain MP
1033 <1 to maxCNDo mains> CN domain identity 10.3.1.1 Enumerated( Affected, Not Affected)
3GPP TS 25.331 V6.23.0 (2009-09)
>CN domain identity
MP
>Status
MP
13.4.21 Void
13.4.22 START_THRESHOLD
This variable contains information about the maximum allowed value of the START for a CN domain.
Information Element/Group name THRESHOLD Need OP Multi Type and reference Integer (0..1048576) Semantics description 20 bits. Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when leaving UTRA RRC connected mode.
13.4.23 START_VALUE_TO_TRANSMIT
This variable contains the value of START for new radio bearer(s) to be transmitted in a response message.
Information Element/Group name START Need OP Multi Type and reference START 10.3.3.38 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.24 TFC_SUBSET
This variable contains information about the TFC subset(s) applicable to the UE.
Information Element/Group name CHOICE mode >FDD >>Current TFC subset Need MP MP Transport Format Combinati on Subset 10.3.5.22 TFC Control duration 10.3.6.80 Transport Format Combinati Set to "Full transport format set" when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. The TFC subset to go back to when any temporary limitation is Multi Type and reference Semantics description Version
>>Duration
OP
>>Default TFC subset
OP
3GPP
1034 Type and reference on Subset 10.3.5.22
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description released. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. REL-4 Version
>>TFC subset list
MP
1 to <maxTF Csub> Transport Format Combinati on Subset 10.3.5.22 1 to < maxCCT rCH > One TFCS is created when entering UTRA RRC connected mode when not stated otherwise in the procedure. "TFCS ID" is set to 1 when entering UTRA RRC connected mode when not stated otherwise in the procedure. "Shared channel indicator" is set to FALSE when entering UTRA RRC connected mode when not stated otherwise in the procedure. Set to "Full transport format set" when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. The TFC subset to go back to when any temporary limitation is released. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>>>TFC subset
MP
REL-4
>TDD >>TFCS list
MP
>>>TFCS identity
MP
Transport Format Combinati on Set Identity 10.3.5.21
>>>Current TFC subset
MP
Transport Format Combinati on Subset 10.3.5.22 TFC Control duration 10.3.6.80 Transport Format Combinati on Subset 10.3.5.22
>>>>Duration
OP
>>>>Default TFC subset
OP
3GPP
Release 6 Information Element/Group name >>TFC subset list Need MP Multi 1 to <maxTF Csub2>
>>>TFCS identity
MP
>>>TFC subset
MP
Transport Format Combinati on Set Identity 10.3.5.21 Transport Format Combinati on Subset 10.3.5.22
REL-4
REL-4
13.4.25 TGPS_IDENTITY
This variable contains the configuration parameters of all the configured compressed mode transmission gap pattern sequences.
Information Element/Group name Transmission gap pattern sequence Need OP Multi 1 to <maxTGP S> TGPSI 10.3.6.82 Enumerated( activate, deactivate) Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>TGPSI >TGPS Status Flag
MP MP
This flag indicates whether the Transmission Gap Pattern Sequence shall be activated or deactivated.
> Current TGPS Status Flag
MP
Enumerated( active, inactive) Integer (0..255)
>TGCFN
CV-Active
>Transmission gap pattern sequence configuration parameters
MP
This flag indicates the current status of the Transmission Gap Pattern Sequence, whether it is active or inactive Connection Frame Number of the first frame of the first pattern within the Transmission Gap Pattern Sequence. Information as contained in the IE group "Transmission gap pattern sequence configuration parameters" in IE "DPCH compressed mode info" 10.3.6.33.
Condition Active
Explanation This IE is mandatory present when the value of the IE "TGPS Status Flag" is "Activate" and not needed otherwise.
13.4.26 TGSN_REPORTED
This variable specifies whether an IE "Proposed TGSN" was reported to the UTRAN
3GPP
Release 6 Information Element/Group name Proposed TGSN reported Need MP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.26a TIMERS_AND_CONSTANTS
This variable contains the values for all timers and constants used in connected mode.
Information Element/Group name UE Timers and constants in connected mode Need MD Multi Type and reference UE Timers and constants in connected mode 10.3.3.43 Semantics description Default value means that for all timers and constants for parameters with need MD, the defaults specified in 10.3.3.43 apply and for parameters with need OP, the parameters are absent. All parameters are set to the default value when leaving UTRA RRC connected mode to another RAT.
13.4.27 TRANSACTIONS
This variable stores the identifications of the ongoing RRC procedure transactions.
Information Element/Group name Accepted transactions Need OP Multi 1 to <maxtrans actions> Message Type RRC transaction identifier 10.3.3.36 1 to <maxtrans actions> Message Type RRC transaction identifier 10.3.3.36 Cleared when leaving UTRA RRC connected mode. Type and reference Semantics description Cleared when leaving UTRA RRC connected mode.
>Message type >RRC transaction identifier
MP MP
Rejected transactions
OP
>Message type >RRC transaction identifier
MP MP
13.4.27a TRIGGERED_1A_EVENT
This variable contains information about a 1a event that has been triggered in the UE. There is one such variable per 1a event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe Type and reference Semantics description Cleared when entering UTRA RRC connected mode.
3GPP
1037 Multi as> Type and reference
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Cleared when leaving UTRA RRC connected mode. Primary CPICH info 10.3.6.60 Integer(1..Inf inity)
>primary CPICH
MP
>sent reports
MP
Number of reports sent to UTRAN in case of event triggered periodical reporting
Cells recently triggered
OP
1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Integer(1..Inf inity) Boolean
>primary CPICH
MP
>sent reports
MP
Periodical reporting running
MP
13.4.27b TRIGGERED_1B_EVENT
This variable contains information about a 1b event that has been triggered in the UE. There is one such variable per 1b event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCell Meas> Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. Primary CPICH info 10.3.6.60 Integer(1.. Infinity) Version
>primary CPICH
MP
>sent reports
MP
REL-5
OP
1 to < maxCell Meas> Primary CPICH info 10.3.6.60 Integer(1.. Infinity)
REL-5
>primary CPICH
MP
REL-5
>sent reports
MP
Number of reports sent to UTRAN in case of event triggered periodical reporting.
REL-5
MP
Boolean
REL-5
3GPP
Release 6
1038
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.27c TRIGGERED_1C_EVENT
This variable contains information about a 1c event that has been triggered in the UE. There is one such variable per 1c event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Integer(1..Inf inity) 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Integer(1..Inf inity) Boolean Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>primary CPICH
MP
>sent reports
MP
OP
>primary CPICH
MP
>sent reports
MP
MP
13.4.27d BEST_CELL_1D_EVENT
This variable contains information about a 1d event that has been triggered in the UE. There is one such variable per 1d event configured in the UE.
Information Element/Group name Best cell Need OP Multi Type and reference Primary CPICH info 10.3.6.60 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.27e TRIGGERED_1E_EVENT
This variable contains information about a 1e event that has been triggered in the UE. There is one such variable per 1e event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>primary CPICH
MP
OP
>primary CPICH
MP
3GPP
Release 6
1039
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.27f TRIGGERED_1F_EVENT
This variable contains information about a 1f event that has been triggered in the UE. There is one such variable per 1f event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
>primary CPICH
MP
OP
>primary CPICH
MP
13.4.27f1 TRIGGERED_1G_EVENT
This variable contains information about a 1g event that has been triggered in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe as> Primary CCPCH info 10.3.6.57 Type and reference Semantics description
>Primary CCPCH info
MP
13.4.27f2 TRIGGERED_1H_EVENT
This variable contains information about a 1h event that has been triggered in the UE.
>Primary CCPCH info
MP
13.4.27f3 TRIGGERED_1I_EVENT
This variable contains information about a 1i event that has been triggered in the UE.
>Primary CCPCH info
MP
3GPP
Release 6
1040
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.27f4 BEST_FREQUENCY_2A_EVENT
This variable contains information about a 2a event that has been configured in the UE. There is one such variable per 2a event configured in the UE.
Information Element/Group name Best frequency Need MP Multi Type and reference Frequency info 10.3.6.36 Semantics description
13.4.27f5 TRIGGERED_2B_EVENT
This variable contains information about a 2b event that has been configured in the UE. There is one such variable per 2b event configured in the UE.
Information Element/Group name Frequency triggered Need OP Multi 1 to < maxCellMe as> Frequency info 10.3.6.36 Type and reference Semantics description
>Frequency
MP
13.4.27f6 TRIGGERED_2C_EVENT
This variable contains information about a 2c event that has been configured in the UE. There is one such variable per 2c event configured in the UE.
>Frequency
MP
13.4.27f7 TRIGGERED_2D_EVENT
This variable contains information about a 2d event that has been configured in the UE. There is one such variable per 2d event configured in the UE.
Information Element/Group name Event triggered Need OP Multi Type and reference Boolean Semantics description
3GPP
Release 6
1041
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.27f8 TRIGGERED_2E_EVENT
This variable contains information about a 2e event that has been configured in the UE. There is one such variable per 2e event configured in the UE.
>Frequency
MP
13.4.27f9 TRIGGERED_2F_EVENT
This variable contains information about a 2f event that have been configured in the UE. There is one such variable per 2f event configured in the UE.
13.4.27f10 TRIGGERED_3A_EVENT
This variable contains information about a 3a event that has been configured in the UE. There is one such variable per event 3a configured in the UE.
Information Element/Group name CHOICE system >GSM >>CHOICE BSIC >>>Verified BSIC Need OP MP 0 to <maxCellM eas> MP Integer(0..< maxCellMea s>-1) 0 to <maxCellM eas> MP Integer (0..1023) Multi Type and reference Semantics description
>>>>Inter-RAT cell id
>>>Non verified BSIC
>>>>BCCH ARFCN
3GPP
Release 6
1042
3GPP TS 25.331 V6.23.0 (2009-09)
This variable contains information about a 3b event that has been configured in the UE. There is one such variable per event 3b configured in the UE.
>>>>BCCH ARFCN
This variable contains information about a 3c event that has been configured in the UE. There is one such variable per event 3c configured in the UE.
>>>>BCCH ARFCN
13.4.27f13 BEST_CELL_3D_EVENT
This variable contains information about a 3d event that has been configured in the UE. There is one such variable per event 3a configured in the UE.
Information Element/Group name CHOICE system >GSM >>CHOICE BSIC >>>Verified BSIC >>>>Inter-RAT cell id Need Multi Type and reference Semantics description
MP MP Integer(0..< maxCellMea s>-1) Integer (0..1023)
>>>Non verified BSIC >>>>BCCH ARFCN
MP
3GPP
Release 6
1043
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.27f14 TRIGGERED_6A_EVENT
This variable contains information about a 6a event that has been configured in the UE. There is one such variable per 6a event configured in the UE.
This variable contains information about a 6b event that has been configured in the UE. There is one such variable per 6b event configured in the UE.
This variable contains information about a 6c event that has been configured in the UE. There is one such variable per 6c event configured in the UE.
13.4.27f17 TRIGGERED_6D_EVENT
This variable contains information about a 6d event that has been configured in the UE. There is one such variable per 6d event configured in the UE.
13.4.27f18 TRIGGERED_6E_EVENT
This variable contains information about a 6e event that has been configured in the UE. There is one such variable per 6e event configured in the UE.
13.4.27f19 TRIGGERED_6F_EVENT
This variable contains information about a 6f event that has been configured in the UE. There is one such variable per 6f event configured in the UE.
3GPP
Release 6 Information Element/Group name CHOICE mode >FDD Event triggered_RL >1.28 Mcps TDD >>TADV Need Multi
OP
<maxRL >
Boolean REL-4 REL-4
MP
TADV info 10.3.7.11 2
13.4.27f20 TRIGGERED_6G_EVENT
This variable contains information about a 6g event that has been configured in the UE. There is one such variable per 6g event configured in the UE.
Information Element/Group name Event triggered_RL Need OP Multi <maxRL> Type and reference Boolean Semantics description
13.4.27f21 TRIGGERED_1J_EVENT
This variable contains information about a 1j event that has been triggered in the UE. There is one such variable per 1j event configured in the UE.
Information Element/Group name Cells triggered Need OP Multi 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Integer(1..Inf inity) 1 to < maxCellMe as> Primary CPICH info 10.3.6.60 Integer(1..Inf inity) Boolean Type and reference Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. Version REL-6
>primary CPICH
MP
REL-6
>sent reports
MP
REL-6
OP
REL-6
>primary CPICH
MP
REL-6
>sent reports
MP
REL-6
MP
REL-6
13.4.27g UE_CAPABILITY_REQUESTED
This variable stores information about the UE capabilities that have been requested by UTRAN but that have not yet been transferred to UTRAN.
3GPP
Release 6 Information Element/Group name UE radio access capability Need OP
1045 Multi Type and reference UE radio access capability 10.3.3.42 UE radio access capability extension 10.3.3.42a
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
OP
OP
1 to < maxInterSy sMessages > Inter-RAT UE radio access capability 10.3.8.7 Includes inter-RAT classmark. Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
MP
13.4.28 UE_CAPABILITY_TRANSFERRED
This variable stores information about which UE capabilities that have been transferred to UTRAN.
Information Element/Group name UE radio access capability Need OP Multi Type and reference UE radio access capability 10.3.3.42 Semantics description Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when leaving UTRA RRC connected mode. Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when leaving UTRA RRC connected mode. Version
OP
UE radio access capability extension 10.3.3.42a 1 to <maxSyste mCapabilit y> Inter-RAT UE radio access capability 10.3.8.7
OP
MP
Includes inter-RAT classmark. Cleared when entering UTRA RRC connected mode when not stated otherwise in the procedure. Cleared when leaving UTRA RRC connected mode. REL-5
OP
UE radio access capability compressed 10.3.3.42o Security capability 10.3.3.37
Security capability
OP
REL-5
13.4.28a UE_POSITIONING_GPS_DATA
3GPP
Release 6 Information Element/Group name GPS Data ciphering info Need OP
1046 Multi Type and reference UE positioning Ciphering info 10.3.7.86 Bit string(56) Bit string(56) UE positioning GPS reference time 10.3.7.96 Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c UE positioning GPS DGPS corrections 10.3.7.91 1 to <maxSat> Enumerated( 0..63) UE positioning GPS Ephemeris and Clock Correction parameters 10.3.7.91a UE positioning GPS ionospheric model 10.3.7.92 UE positioning GPS UTC model 10.3.7.97 1 to <maxSatAl manacStor age>
GPS Deciphering Keys >Current deciphering key >Next deciphering key UE positioning GPS reference time
OP MP MP OP
UE positioning GPS reference UE position
OP
A priori knowledge of UE 3-D position.
OP
UE positioning GPS navigation model >SatID >GPS Ephemeris and Clock Correction parameters
OP MP MP
Satellite ID
OP
OP
UE positioning GPS almanac >SatID
OP MP
>>WNa >>DataID >>e >>toa >>I >>OMEGADOT >>SV Health 1/2 >>A >>OMEGA0 >>M0 >> >>af0
MP MP MP MP MP MP MP MP MP MP MP MP
Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 Same as IE in 10.3.7.89
3GPP
Release 6 Information Element/Group name >>af1 >SV Global Health UE positioning GPS acquisition assistance Need MP OP OP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Same as IE in 10.3.7.89 Same as IE in 10.3.7.89 UE positioning GPS acquisition assistance 10.3.7.88 UE positioning GPS realtime integrity 10.3.7.95
OP
13.4.28b UE_POSITIONING_OTDOA_DATA_UE_ASSISTED
Information Element/Group name UE positioning OTDOA reference cell info for UEassisted Need OP Multi Type and reference UE positioning OTDOA reference cell info 10.3.7.108 Semantics description
UE positioning OTDOA neighbour cell list for UEassisted >UE positioning OTDOA neighbour cell info for UEassisted
OP
1 to <maxCellM eas> UE positioning OTDOA neighbour cell info 10.3.7.106
MP
3GPP
Release 6
1048
3GPP TS 25.331 V6.23.0 (2009-09)
13.4.28c UE_POSITIONING_OTDOA_DATA_UE_BASED
Information Element/Group name OTDOA Deciphering Keys >Current deciphering key >Next deciphering key OTDOA Data ciphering info Need OP MP MP OP Multi Type and reference Bit string(56) Bit string(56) UE positioning Ciphering info 10.3.7.86 UE positioning OTDOA reference cell info for UE-based 10.3.7.108a 1 to <maxCellM eas> UE positioning OTDOA neighbour cell info for UE-based 10.3.7.106 Semantics description
UE positioning OTDOA reference cell info for UE-based
OP
UE positioning OTDOA neighbour cell list for UE-based >UE positioning OTDOA neighbour cell info for UE-based
OP
MP
13.4.29 UNSUPPORTED_CONFIGURATION
This variable indicates whether a received message contained a configuration that is not supported by the UE.
Information Element/Group name Unsupported configuration Need MP Multi Type and reference Boolean Semantics description TRUE: An unsupported configuration has been detected. Set to FALSE when entering UTRA RRC connected mode. Set to FALSE when leaving UTRA RRC connected mode.
13.4.30 URA_IDENTITY
This variable stores the assigned URA identity for this UE when in URA_PCH state.
Information Element/Group name URA identity Need OP Multi Type and reference URA identity 10.3.2.6 Semantics description Cleared when entering UTRA RRC connected mode. Cleared when leaving UTRA RRC connected mode.
13.4.31 U_RNTI
This variable stores the assigned U-RNTI for this UE.
3GPP
Release 6 Information Element/Group name U-RNTI Need OP
1049 Multi Type and reference U-RNTI 10.3.3.47
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Cleared when leaving UTRA RRC connected mode.
13.4.32 VALUE_TAG
This variable contains information about the value tag for the last received system information block of a given type, for all system information blocks using value tags. The UE shall maintain one instance of this variable for the current selected cell. The UE may store several instances of this variable, one for each cell, to be used if the UE returns to these cells. All IEs in this variable shall be cleared when switched off. All IEs in this variable except for the IE "SIB 16 value tag list" shall be cleared at selection of a new cell and this cell broadcasts an IE "PLMN Identity" in the MIB which is different from the IE "PLMN Identity" broadcast in the MIB in the previously selected cell. The IE "SIB 16 value tag list" is cleared when NAS informs AS about a new selected PLMN.
Information Element/Group name MIB value tag Need OP Multi Type and reference MIB value tag 10.3.8.9 Cell value tag 10.3.8.4 Cell value tag 10.3.8.4 PLMN value tag 10.3.8.10 Semantics description Value tag for the master information block Value tag for the scheduling block type 1 Value tag for the scheduling block type 2 Value tag for the system information block type 1 Value tag for the system information block type 2 Value tag for the system information block type 3 Value tag for the system information block type 4 Value tag for the system information block type 5 or 5bis Value tag for the system information block type 6 Version
SB 1 value tag
OP
SB 2 value tag
OP
SIB 1 value tag
CV-GSM
SIB 2 value tag
OP
Cell value tag 10.3.8.4
SIB 3 value tag
OP
SIB 4 value tag
OP
SIB 5 value tag
OP
SIB 6 value tag
OP
CHOICE mode >FDD >TDD SIB 11 value tag
MP (no data) Value tag for the system information block type 11 Value tag for the system information block type 11bis Value tag for the system
OP
SIB 11bis value tag
OP
REL-6
SIB 12 value tag
OP
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description information block type 12 Value tag for the system information block type 13 Value tag for the system information block type 13.1 Value tag for the system information block type 13.2 Value tag for the system information block type 13.3 Value tag for the system information block type 13.4 Value tag for the system information block type 15 Value tag for the system information block type 15.1 List of value tags for all stored occurrences of system information block type 15.2 Version
SIB 13 value tag
CV-ANSI
SIB 13.1 value tag
CV-ANSI
SIB 13.2 value tag
CV-ANSI
SIB 13.3 value tag
CV-ANSI
SIB 13.4 value tag
CV-ANSI
SIB 15 value tag
OP
SIB 15.1 value tag
OP
SIB 15.2 value tag list
OP
1 to <maxSat>
>SIB 15.2 value tag >SIB occurrence identity and value tag
MP MP
Cell value tag 10.3.8.4 SIB occurrence identity and value tag 10.3.8.20b 1 to <maxSat> List of value tags for all stored occurrences of system information block type 15.3 Value tag for the system information block type 15.3
SIB 15.3 value tag list
OP
>SIB 15.3 value tag
MP
PLMN value tag 10.3.8.10
>SIB occurrence identity and value tag
MP
SIB 15.4 value tag
OP
SIB occurrence identity and value tag 10.3.8.20b Cell value tag 10.3.8.4
Value tag for the system information block type 15.4
3GPP
Release 6 Information Element/Group name SIB 15.5 value tag Need OP
1051 Multi Type and reference Cell value tag 10.3.8.4
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description Value tag for the system information block type 15.5 List of value tags for all stored occurrences of the system information block type 16 Version
SIB 16 value tag list
OP
1 to <maxPred efConfig>
>Predefined configuration identity and value tag
MP
SIB 18 value tag
OP
Predefined configuration identity and value tag 10.3.8.11 Cell value tag 10.3.8.4
Value tag for the system information block type 18
Condition GSM ANSI
Explanation This information is optional when the UE is operating in "GSM-MAP mode" and never stored otherwise. This information is optional when the UE is operating in "ANSI-41 mode" and never stored otherwise.
13.5
UE RRC Procedure Performance
This subclause defines the performance requirements related to RRC procedures in the UE. Where the total delay is impacted by processing of variable length on the physical layer (e.g. physical layer synchronisation), references to appropriate specifications are given.
13.5.1
Definitions
The following definitions of N1 and N2 are valid only for this UE RRC Procedure Performance specification. N1 = upper limit on the time required to execute modifications in UE after the reception of a UTRAN -> UE message has been completed. Where applicable (e.g. the physical layer transmission is impacted), the changes shall be adopted in the beginning of the next TTI starting after N1. N1 is specified as a multiple of 10 ms. N2 = number of 10 ms radio frames from end of reception of UTRAN -> UE message on UE physical layer before the transmission of the UE -> UTRAN response message must be ready to start on a transport channel with no access delay other than the TTI alignment (e.g. DCH, therefore excluding delays caused by RACH procedure etc). The UE response message transmission from the physical layer shall begin at the latest (N2*10)+TTI ms after completion of the reception of the last TTI carrying the triggering UTRAN -> UE message. When Target State is CELL_DCH, the UE response message transmission from the physical layer may be additionally delayed by the value of IE "SRB delay". N1 and N2 are independent (e.g. N2-N1 is not restricted to being less than or equal to 10ms).
13.5.2
RRC procedure performance values

UTRAN -> UE UE -> UTRAN N1 N2 Notes
NOTE: Times indicated in the table do not include cell reselection.

Procedure title: RRC Connection Management Procedures
3GPP
Release 6 Procedure title: Broadcast of system information UTRAN -> UE SYSTEM INFORMATION
1052 UE -> UTRAN N1 N2
3GPP TS 25.331 V6.23.0 (2009-09) Notes N2 is not applicable for any system information messages, because there is no response message from the UE. No system information data shall be lost due to processing of a MIB received with no detectable errors. This means that the UE shall buffer all system information data received after the MIB until the data can be processed according to the information in the MIB, unless the MIB was received erroneously.
Master Information Block
SYSTEM INFORMATION
NA
System Information Block type 1 System Information Block type 2 System Information Block type 3 System Information Block type 4 System Information Block type 5 or System Information Block type 5bis System Information Block type 6 System Information Block type 7 System Information Block type 11 System Information Block type 12 System Information Block type 13 System Information Block type 14 System Information Block type 15 System Information Block type 16 System Information Block type 18 RRC connection establishment Target state CELL_DCH
SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION SYSTEM INFORMATION RRC CONNECTION SETUP
10 10 10 10 10
NA NA NA NA NA
10 5 10 10 10 10 10 10 10 RRC CONNECTION SETUP COMPLETE 10
NA NA NA NA NA NA NA NA NA NA N1 measures time to the start of tx / rx on DPCH. N2 cannot be specified, because RRC CONNECTION SETUP COMPLETE message is transmitted only after physical layer synchronisation, which also depends on the Node B. The performance of the physical layer synchronisation procedure is specified in [19] and [20] N1 and N2 applicable as defined (N2 can be tested from the initiation of the power ramp on RACH).
RRC connection establishment Target state CELL_FACH
RRC CONNECTION SETUP
RRC CONNECTION SETUP COMPLETE
10
11
3GPP
Release 6 Procedure title: RRC connection release From CELL_DCH state UTRAN -> UE RRC CONNECTION RELEASE
1053 UE -> UTRAN RRC CONNECTION RELEASE COMPLETE N1 5 N2 8
3GPP TS 25.331 V6.23.0 (2009-09) Notes N1 sets the requirement for the time from the completion of the last repetition of the RRC CONNECTION RELEASE COMPLETE message to the release of the physical channel. N2 sets the requirement from the end of successful reception of the RRC CONNECTION RELEASE message to the start of the first transmission of the RRC CONNECTION RELEASE COMPLETE message. N1 represents UE internal configuration that cannot be externally observed. T is the repetition period of SIB7 (applicable for FDD) and SIB14 (applicable for TDD) N1 is not applicable because the UE configuration does not change.
RRC connection release From CELL_FACH state
RRC CONNECTION RELEASE PAGING TYPE 1 UE CAPABILITY ENQUIRY SECURITY MODE COMMAND SIGNALLING CONNECTION RELEASE COUNTER CHECK
Paging
RRC CONNECTION RELEASE COMPLETE CELL UPDATE
NA
11
10
11+ T 8
UE capability enquiry
UE CAPABILITY INFORMATION SECURITY MODE COMPLETE
NA
Security mode control
Signalling connection release procedure Counter check
NA
N2 is not applicable because there is no response message. N1 is not applicable because the UE configuration does not change.
COUNTER CHECK RESPONSE
NA
Radio Bearer control procedures Radio bearer establishment Target state CELL_DCH
RADIO BEARER SETUP
RADIO BEARER SETUP COMPLETE / FAILURE
10
NA
N2 cannot be specified, because the RADIO BEARER SETUP COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
Radio bearer establishment From state CELL_FACH to state CELL_FACH Radio bearer establishment From CELL_DCH to CELL_FACH Radio bearer reconfiguration Target state CELL_DCH
RADIO BEARER SETUP RADIO BEARER SETUP
RADIO BEARER SETUP COMPLETE / FAILURE RADIO BEARER SETUP COMPLETE
10
11
NA
NA
RADIO BEARER RECONFIGURA TION
RADIO BEARER RECONFIGURAT ION COMPLETE / FAILURE
5 or 10
NA
N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER SETUP COMPLETE N2 cannot be specified, because the RADIO BEARER RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
Radio bearer reconfiguration From state CELL_FACH to state CELL_FACH
RADIO BEARER RECONFIGURA TION
RADIO BEARER RECONFIGURAT ION COMPLETE / FAILURE
10
11
3GPP
Release 6 Procedure title: Radio bearer reconfiguration From state CELL_DCH to state CELL_FACH UTRAN -> UE RADIO BEARER RECONFIGURA TION
1054 UE -> UTRAN RADIO BEARER RECONFIGURAT ION COMPLETE N1 NA N2 NA
3GPP TS 25.331 V6.23.0 (2009-09) Notes N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER RECONFIGURATION COMPLETE
Radio bearer release Target state CELL_DCH
RADIO BEARER RELEASE RADIO BEARER RELEASE RADIO BEARER RELEASE
Radio bearer release From state CELL_FACH to state CELL_FACH Radio bearer release From state CELL_DCH to state CELL_FACH
RADIO BEARER RELEASE COMPLETE / FAILURE RADIO BEARER RELEASE COMPLETE / FAILURE RADIO BEARER RELEASE COMPLETE
10
11
10
11
NA
NA
Transport channel reconfiguration Target state CELL_DCH
TRANSPORT CHANNEL RECONFIGURA TION
TRANSPORT CHANNEL RECONFIGURAT ION COMPLETE / FAILURE
5 or 10
NA
N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending RADIO BEARER RECONFIGURATION COMPLETE N2 cannot be specified, because the TRANSPORT CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
Transport channel reconfiguration From state CELL_FACH to state CELL_FACH Transport channel reconfiguration From state CELL_DCH to state CELL_FACH
TRANSPORT CHANNEL RECONFIGURA TION TRANSPORT CHANNEL RECONFIGURA TION
TRANSPORT CHANNEL RECONFIGURAT ION COMPLETE / FAILURE TRANSPORT CHANNEL RECONFIGURAT ION COMPLETE
10
11
NA
NA
N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending TRANSPORT CHANNEL RECONFIGURATION COMPLETE
Transport format combination control AM or UM RLC mode Transport format combination control Transparent mode Physical channel reconfiguration Target state CELL_DCH
TRANSPORT FORMAT COMBINATION CONTROL TRANSPORT FORMAT COMBINATION CONTROL PHYSICAL CHANNEL RECONFIGURA TION
TRANSPORT FORMAT COMBINATION CONTROL FAILURE
NA
N2 is not applicable because no response message is defined. N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B. NOTE 1
PHYSICAL CHANNEL RECONFIGURAT ION COMPLETE / FAILURE
5 or 8
NA
Physical channel reconfiguration From state CELL_FACH to state CELL_FACH
PHYSICAL CHANNEL RECONFIGURA TION
PHYSICAL CHANNEL RECONFIGURAT ION COMPLETE / FAILURE
3GPP
Release 6 Procedure title: Physical channel reconfiguration From state CELL_DCH to state CELL_FACH UTRAN -> UE PHYSICAL CHANNEL RECONFIGURA TION
1055 UE -> UTRAN PHYSICAL CHANNEL RECONFIGURAT ION COMPLETE N1 NA N2 NA
3GPP TS 25.331 V6.23.0 (2009-09) Notes N1 and N2 cannot be specified, because UE need to read SIBs on BCH before sending PHYSICAL CHANNEL RECONFIGURATION COMPLETE N2 is not applicable because no response message is defined. Requirements for outer loop and timing advance adjustments are defined in [22] and [20]. N2 is not applicable because there is no response message.
Physical Shared Channel Allocation [TDD only]
Uplink Physical Channel Control [TDD only]
PHYSICAL SHARED CHANNEL ALLOCATION UPLINK PHYSICAL CHANNEL CONTROL
NA
NA
RRC connection mobility procedures Cell update
CELL UPDATE CONFIRM
UTRAN MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURAT ION COMPLETE Target state CELL_FACH PHYSICAL CHANNEL RECONFIGURAT ION COMPLETE Target state CELL_DCH
NA
N2 cannot be specified, because the PHYSICAL CHANNEL RECONFIGURATION COMPLETE / FAILURE message is transmitted only after physical layer synchronisation, which depends also on Node B.
TRANSPORT CHANNEL RECONFIGURAT ION COMPLETE Target state CELL_FACH TRANSPORT CHANNEL RECONFIGURAT ION COMPLETE Target state CELL_DCH
10
11
10
NA
RADIO BEARER RECONFIGURAT ION COMPLETE Target state CELL_FACH RADIO BEARER RECONFIGURAT ION COMPLETE Target state CELL_DCH
10
11
10
NA
3GPP
Release 6 Procedure title: UTRAN -> UE
1056 UE -> UTRAN RADIO BEARER RELEASE COMPLETE Target state CELL_DCH UTRAN MOBILITY INFORMATION CONFIRM UTRAN MOBILITY INFORMATION CONFIRM / FAILURE ACTIVE SET UPDATE COMPLETE / FAILURE N1 10 N2 11
3GPP TS 25.331 V6.23.0 (2009-09) Notes
URA update
URA UPDATE CONFIRM
UTRAN mobility information
UTRAN MOBILITY INFORMATION
Active set update
ACTIVE SET UPDATE
NA
The requirements on UE combining and power control performance for both UL and DL are specified by RAN WG4 in [21] and [19]. Also in case of branch addition the COMPLETE / FAILURE message is transmitted without waiting for the new branch to stabilise, therefore N2 is specified.
Inter-RAT handover to UTRAN
Inter-RAT handover from UTRAN Measurement procedures Measurement control
HANDOVER TO UTRAN COMMAND (other system) HANDOVER FROM UTRAN COMMAND MEASUREMEN T CONTROL
HANDOVER TO UTRAN COMPLETE HANDOVER FROM UTRAN FAILURE MEASUREMENT CONTROL FAILURE
NA
NA
The performance of this procedure is specified in 05.10. The performance of this procedure is specified in [19] and [20]. Response to measurement inquiry depends on physical layer measurement. Response time is defined in [19] and [20]. N1 and N2 only define the processing of the message.
NA
NA
NOTE 1: The lower value applies when the UE is ordered to do a serving HS-DSCH cell change, changing no other information than contained in the IE "H-RNTI", the IE "Downlink HS-PDSCH information", the IE "Uplink DPCH power control info" and/or the IE "Serving HS-DSCH radio link indicator" (FDD only).
3GPP
Release 6
1057
3GPP TS 25.331 V6.23.0 (2009-09)
13.6
RB information parameters for signalling radio bearer RB 0

Value TM omitted FALSE UM Comment
The following Radio Bearer parameter values apply for signalling radio bearer RB0:
Information element/ Group name RLC info >Uplink RLC mode >>Transmission RLC discard >>Segmentation indication >Downlink RLC mode RB mapping info >Uplink mapping info >>UL transport channel >>RLC size list
Neither discard is used, nor will there be a reset
Single multiplexing option RACH N/A RACH corresponding with selected PRACH If available the size in the IE Additional Dynamic Transport Format Information for CCCH for the transport channel used. Else the first TF defined in the Transport Format Set for the transport channel is used.
>>MAC logical channel priority >Downlink mapping info >>DL transport channel
1 FACH
Procedure descriptions in subclause 8.6.4.8 shall not be applied for the IE "RB mapping info" that is used for signalling radio bearer RB0.
13.6a
RB information parameters for SHCCH

Value TM omitted FALSE UM Comment
The following Radio Bearer parameter values apply for SHCCH:

Information element/ Group name RLC info >Uplink RLC mode >>Transmission RLC discard >>Segmentation indication >Downlink RLC mode RB mapping info >Uplink mapping info >>UL transport channel >>RLC size list >>MAC logical channel priority >Downlink mapping info >>DL transport channel >Uplink mapping info >>UL transport channel >>UL Transport Channel Identity >>MAC logical channel priority >>RLC size list >Downlink mapping info >>DL transport channel >>DL Transport Channel Identity
Neither discard is used, nor will there be a reset
RACH N/A 1 FACH
Option 1 RACH corresponding with selected PRACH The first TF defined in the Transport Format Set for the transport channel that is used
Option 2 USCH 1 1 N/A
The first TF defined in the Transport Format Set for the transport channel that is used
DSCH 1
13.6b
RB information parameters for BCCH mapped to FACH

Value TM FALSE Comment
The following Radio Bearer parameter values apply for BCCH mapped to FACH:
Information element/ Group name Downlink RLC mode Segmentation indication
3GPP
Release 6
1058
3GPP TS 25.331 V6.23.0 (2009-09)
13.6c
RB information parameters for PCCH mapped to PCH

Value TM FALSE Comment
The following Radio Bearer parameter values apply for PCCH mapped to PCH:
Information element/ Group name Downlink RLC mode Segmentation indication
13.6d
Parameters for BCCH mapped to BCH
The transport format parameters for BCH are specified in [34].
13.7
Parameter values for default radio configurations
The UE shall support the use of the default radio configurations that are specified in the following. NOTE 1: These configurations are based on [41] and cover a number of RAB and signalling connection configurations. In the table that is used to specify the parameter values for these default configurations, the following principles are used: Optional IEs that are not used are omitted; In case no parameter value is specified in a column, this means the value given the previous (left side) column applies.
NOTE 2: If needed, signalling radio bearer RB4 is established after the completion of handover. NOTE 3: For each default configuration, the value of FDD, 3.84 Mcps TDD and 1.28 Mcps TDD parameters are specified. All parameters apply to FDD, 3.84 Mcps TDD and 1.28 Mcps TDD modes, unless explicitly stated otherwise. It should be noted that in this respect default configurations differ from pre-defined configurations, which only include parameter values for one mode. NOTE 4: The transport format sizes, indicated in the following table, concern the RLC PDU size, since all configurations concern dedicated channels. The transport block sizes indicated in TS 34.108 are different since these include the size of the MAC header. NOTE 5: The tabular values included in this subclause, represent the actual IE values as in clause 10, and not the ASN.1 representation of these values.
Configuration 3.4 kbps signalling 13.6 kbps signalling Unused configuration 12.2 kbps speech + 3.4 kbps signalling 4 3
Ref 34.108 Default configuration identity RB INFORMATION rb-Identity
2 0
3 1
RB1: 1, RB2: 2, RB3: 3 Rlc-info RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: NoDiscard
RB1: 1, RB2: 2, RB3: 3 Rlc-info RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: NoDiscard
rlc-InfoChoice >ul-RLC-Mode
>>transmissionRLCDiscardMode
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A
3GPP
Release 6 Configuration 3.4 kbps signalling
1059 13.6 kbps signalling
3GPP TS 25.331 V6.23.0 (2009-09) Unused configuration 12.2 kbps speech + 3.4 kbps signalling RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: 300 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A
>>>maxDat
RB1: N/A RB2- RB3: 15 RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB1: N/A RB2- RB3: 300 RB1: N/A RB2- RB3: 1 RB1: N/A RB2- RB3: as below RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: TRUE RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A
RB1: N/A RB2- RB3: 15 RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB1: N/A RB2- RB3: 300 RB1: N/A RB2- RB3: 1 RB1: N/A RB2- RB3: as below RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 100 RB1- RB3: N/A RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: TRUE RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 100 RB1- RB3: N/A
>>transmissionWindowSiz e
>>timerRST
>>max-RST
>>pollingInfo
>>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>timerPollPeriodic >>segmentationIndication >dl-RLC-Mode
>>inSequenceDelivery
>>receivingWindowSize
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity
OneLogicalChannel Dch RB1- RB3: 1
OneLogicalChannel Dch RB1- RB3: 1
RB1: 1, RB2: 2, RB3: 3 RB1- RB3: configured
RB1: 1, RB2: 2, RB3: 3 RB1- RB3: configured
>>rlc-SizeList
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Unused configuration 12.2 kbps speech + 3.4 kbps signalling RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
>>macLogicalChannelPriority >DLlogicalChannelMappingList >>Mapping option 1 >>>dlTransportChannelType >>>>transportChannelIden tity >>>logicalChannelIdentity
RB1: 1, RB2: 2, RB3: 3
RB1: 1, RB2: 2, RB3: 3
One mapping option Dch RB1- RB3: 1
One mapping option Dch RB1- RB3: 1
One mapping option Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A
RB1: 1, RB2: 2, RB3: 3
RB1: 1, RB2: 2, RB3: 3
TrCH INFORMATION PER TrCH ULAddReconfTransChInfoList >Uplink transport channel type >transportChannelIdentity >transportFormatSet >>dynamicTF-information >>>tf0/ tf0,1
dch TrCH1: 1 DedicatedTransChT FS TrCH1: (0x144, 1x144)
dch TrCH1: 1 DedicatedTransChT FS TrCH1: (0x144, 1x144)
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 DedicatedTransChT FS TrCH1: (0x81) TrCH2: (0x 103, 1x103) TrCH3: (0x 60, 1x60) TrCH4: (0x144, 1x144) BitMode TrCH1: type 1: 81 TrCH2: type 1: 103 TrCH3: type 1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero TrCH2-4: Zero, one All TrCH1: (1x39) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: 1: 39 TrCH1: One TrCH1: all TrCH1: (1x81) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 81 TrCH1: One TrCH1: all
>>>>rlcSize >>>>>sizeType
BitMode TrCH1: type 2, part1= 2, part2= 0 (144)
BitMode TrCH1: type 2, part1= 2, part2= 0 (144)
>>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 1 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 2 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType
TrCH1: Zero, one All N/A
TrCH1: Zero, one All N/A
N/A
N/A
TrCH1: 40 Convolutional
TrCH1: 10 Convolutional
TrCH1- TrCH3: 20 TrCH4: 40 Convolutional
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Unused configuration 12.2 kbps speech + 3.4 kbps signalling TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16
>>>>codingRate
TrCH1: Third
TrCH1: Third
>>>rateMatchingAttribute
TrCH1: 160
TrCH1: 160
>>>crc-Size
TrCH1: 16
TrCH1: 16
DLAddReconfTransChInfoList >Downlink transport channel type >dlTransportChannelIdentity (should be as for UL) >tfs-SignallingMode
dch TrCH1: 1
dch TrCH1: 1
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 Explicit <Only tf0 on TrCH1 is different and shown below> DedicatedTransChT FS TrCH1: (1x0) bitMode TrCH1: type 1: 0 TrCH1: One All TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4
-2
SameAsUL
SameAsUL
>>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue
TrCH1: 1
TrCH1: 1
TrCH1: 5x10
-2
TrCH1: 5x10
TrCH1: 7x10 TrCH2- TrCH4: Absent
-3
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0) 0 Computed 0 (TF1) 1 Signalled
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0) 0 Computed 0 (TF1) 1 Signalled
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Unused configuration 12.2 kbps speech + 3.4 kbps signalling N/A N/A 0 (TF2, TF1, TF1, TF0) 11 Computed 0 (TF0, TF0, TF0, TF1) 12 Computed N/A N/A 0 (TF1, TF0, TF0, TF1) 13 Computed 0 (TF2, TF1, TF1, TF1) 23 Signalled 11 15 0
>>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit
11 15 0
11 15 0
Same as UL
Same as UL
Same as UL
Algorithm 1 1 dB TRUE 1
Algorithm 1 1 dB TRUE 0.88
256 FALSE 4 N/A
128 FALSE 4 N/A
128 FALSE 4 Fixed
0 frameRelated 4 1
0 frameRelated 4 0.92
0 frameRelated 16 0.88
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Unused configuration 12.2 kbps speech + 3.4 kbps signalling repetitionPeriod1
>>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
repetitionPeriod1
repetitionPeriod1
frameRelated 4 1 repetitionPeriod1
frameRelated 4 0.92 repetitionPeriod1
Configuration
28.8 kbps conv. CS- data + 3.4 kbps signalling 12 4
32 kbps conv. CSdata + 3.4 kbps signalling 14 5
64kbps conv. CSdata + 3.4 kbps signalling 13 6
Ref 34.108 Default configuration identity RB INFORMATION rb-Identity rlc-InfoChoice >ul-RLC-Mode
14.4 kbps streaming CSdata + 3.4 kbps signalling 15 7
>>>maxDat
RB1: 1, RB2: 2, RB3: 3, RB5: 5 Rlc-info RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: NoDiscard RB5: N/A RB1: N/A RB2- RB3: 15 RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A
3GPP
Release 6 Configuration 28.8 kbps conv. CS- data + 3.4 kbps signalling RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5
1064 32 kbps conv. CSdata + 3.4 kbps signalling RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5
3GPP TS 25.331 V6.23.0 (2009-09) 64kbps conv. CSdata + 3.4 kbps signalling RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5 14.4 kbps streaming CSdata + 3.4 kbps signalling RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5
>>timerRST
>>max-RST
>>pollingInfo
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdenti ty >>logicalChannelIdentity
>>rlc-SizeList
>>macLogicalChannelPriority >DLlogicalChannelMappingList >>Mapping option 1 >>>dlTransportChannelType >>>>transportChannelIden tity
One mapping option Dch RB1- RB3: 2 RB5: 1
3GPP
Release 6 Configuration 28.8 kbps conv. CS- data + 3.4 kbps signalling RB1: 1, RB2: 2, RB3: 3 RB5: N/A
1065 32 kbps conv. CSdata + 3.4 kbps signalling RB1: 1, RB2: 2, RB3: 3 RB5: N/A
3GPP TS 25.331 V6.23.0 (2009-09) 64kbps conv. CSdata + 3.4 kbps signalling RB1: 1, RB2: 2, RB3: 3 RB5: N/A 14.4 kbps streaming CSdata + 3.4 kbps signalling RB1: 1, RB2: 2, RB3: 3 RB5: N/A
>>>logicalChannelIdentity
TrCH INFORMATION PER TrCH ULAddReconfTransChInfoLis t >Uplink transport channel type >transportChannelIdentity >transportFormatSet >>dynamicTF-information >>>tf0/ tf0,1
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS TrCH1: (0x576, 1x576, 2x576) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 9, part2= 2 (576) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero,1, 2 TrCH2: Zero, one All
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS TrCH1: (0x640, 1x640) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 11, part2= 2 (640) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, one TrCH2: Zero, one All
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS TrCH1: (0x640, 2x640) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 11, part2= 2 (640) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, 2 TrCH2: Zero, one All
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS TrCH1: (0x576, 1x576) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 9, part2= 2 (576) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, one, TrCH2: Zero, one All
>>>>numberOfTbSizeList >>>>logicalChannelList >>semiStaticTFInformation >>>tti >>>channelCodingType
>>>>codingRate >>>rateMatchingAttribute >>>crc-Size DLAddReconfTransChInfoLis t >Downlink transport channel type >dlTransportChannelIdentity (should be as for UL) >tfs-SignallingMode >>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue
TrCH1: 40 TrCH2: 40 TrCH1: Turbo TrCH2: Convolutional TrCH1: N/A TrCH2: Third TrCH1: 180 TrCH2: 160 TrCH1: 16 TrCH2: 16
dch TrCH1: 1, TrCH2: 2
SameAsUL
SameAsUL
SameAsUL
SameAsUL
TrCH1: 1, TrCH2: 2 TrCH1: 2x10 TrCH2: Absent

-3

-3

-3

-2
3GPP
Release 6 Configuration 28.8 kbps conv. CS- data + 3.4 kbps signalling
1066 32 kbps conv. CSdata + 3.4 kbps signalling
3GPP TS 25.331 V6.23.0 (2009-09) 64kbps conv. CSdata + 3.4 kbps signalling 14.4 kbps streaming CSdata + 3.4 kbps signalling
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc4Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF2, TF0) 2 Computed 0 (TF0, TF1) 3 Computed N/A N/A 0 (TF1, TF1) 4 Computed 0 (TF2, TF1) 5 Signalled 8 15 0
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF0, TF1) 2 Computed 0 (TF1, TF1) 3 Signalled 8 15 0 N/A
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF0, TF1) 2 Computed 0 (TF1, TF1) 3 Signalled 8 15 0 N/A
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc4Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF0, TF1) 2 Computed 0 (TF1, TF1) 3 Signalled 11 15 0
N/A
N/A
3GPP
Release 6 Configuration 28.8 kbps conv. CS- data + 3.4 kbps signalling
1067 32 kbps conv. CSdata + 3.4 kbps signalling
3GPP TS 25.331 V6.23.0 (2009-09) 64kbps conv. CSdata + 3.4 kbps signalling 14.4 kbps streaming CSdata + 3.4 kbps signalling
>>>>>>TFCS 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPrede f >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMod e >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo
Same as UL
Same as UL
Same as UL
Same as UL
64 TRUE 8 Flexible
64 TRUE 8 Flexible
32 TRUE 8 Flexible
128 TRUE 8 Flexible
0 frameRelated 16 0.44 repetitionPeriod1
3GPP
Release 6 Configuration 28.8 kbps conv. CS- data + 3.4 kbps signalling frameRelated 16 0.64 repetitionPeriod1
1068 32 kbps conv. CSdata + 3.4 kbps signalling frameRelated 8 0.60 repetitionPeriod1
3GPP TS 25.331 V6.23.0 (2009-09) 64kbps conv. CSdata + 3.4 kbps signalling frameRelated 8 0.64 repetitionPeriod1 14.4 kbps streaming CSdata + 3.4 kbps signalling frameRelated 8 1 repetitionPeriod1
>>secondInterleavingMod e >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
Configuration
12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling 4a 10
RB1: 1, RB2: 2, RB3: 3, RB5: 5 Rlc-info RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: NoDiscard RB5: N/A RB1: N/A RB2- RB3: 15 RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300
RB1: 1, RB2: 2, RB3: 3, RB5: 5 Rlc-info RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: NoDiscard RB5: N/A RB1: N/A RB2- RB3: 15 RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: 300 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300
>>>maxDat
>>timerRST
>>max-RST
>>pollingInfo
>>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>timerPollPeriodic
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: 300 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5
1069 57.6 kbps streaming CSdata + 3.4 kbps signalling RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
>>segmentationIndication >dl-RLC-Mode
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdenti ty >>logicalChannelIdentity
>>rlc-SizeList
One mapping option Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A
One mapping option Dch RB1- RB3: 2 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A
TrCH INFORMATION PER TrCH ULAddReconfTransChInfoLis t >Uplink transport channel type >transportChannelIdentity >transportFormatSet
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS
dch TrCH1: 1, TrCH2: 2 DedicatedTransChT FS
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 DedicatedTransChT FS
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling TrCH1: (0x576, 1x576, 2x576) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 9, part2= 2 (576) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, one, 2 TrCH2: Zero, one All
1070 57.6 kbps streaming CSdata + 3.4 kbps signalling TrCH1: (0x576, 1x576, 2x576, 3x576, 4x576) TrCH2: (0x144, 1x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 9, part2= 2 (576) TrCH2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, one, 2, 3, 4 TrCH2: Zero, one All
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling
>>dynamicTF-information >>>tf0/ tf0,1
TrCH1: (0x81) TrCH2: (0x 103 TrCH3: (0x 60) TrCH4: (0x144) BitMode TrCH1: type 1: 81 TrCH2: type 1: 103 TrCH3: type 1: 60 TrCH4: type 2, part1= 2, part2= 0 (144) TrCH1-4: Zero
>>>>numberOfTbSizeList
>>>>logicalChannelList >>>tf 1
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType
All TrCH1: (1x39) TrCH2: (1x53) TrCH3: (1x60) TrCH4: (1x144) TrCH1-4: One TrCH1-3: BitMode TrCH1: type 1: 39 TrCH2: type 1: 53 TrCH3: type 1: 60 TrCH4: type 2, part1= 2, part2= 0 (144) TrCH1-4: One TrCH1-4: all TrCH1: (1x42) TrCH2: (1x63) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 42 TrCH2: type 1: 63 TrCH1-2: One TrCH1: all TrCH1: (1x55) TrCH2: (1x84) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 55 TrCH2: type 1: 84 TrCH1-2: One TrCH1: all TrCH1: (1x75) TrCH2: (1x103) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 75 TrCH2: type 1: 103 TrCH1-2: One
>>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 2
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 3
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling
1071 57.6 kbps streaming CSdata + 3.4 kbps signalling
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling TrCH1: all TrCH1: (1x81) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 81 TrCH1: One TrCH1: all
>>>>logicalChannelList >>>tf 5 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semiStaticTFInformation >>>tti >>>channelCodingType
>>>>codingRate
TrCH1: 40 TrCH2: 40 TrCH1: Turbo TrCH2: Convolutional TrCH1: N/A TrCH2: Third
TrCH1: 40 TrCH2: 40 TrCH1: Turbo TrCH2: Convolutional TrCH1: N/A TrCH2: Third
TrCH1- TrCH3: 20 TrCH4: 40 Convolutional
TrCH1: 155 TrCH2: 160
TrCH1: 145 TrCH2: 160
>>>crc-Size
TrCH1: 16 TrCH2: 16
TrCH1: 16 TrCH2: 16
TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16
DLAddReconfTransChInfoLis t >Downlink transport channel type >dlTransportChannelIdentity (should be as for UL) >tfs-SignallingMode
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 Independent <Only tf0 on TrCH1 is different and shown below> DedicatedTransChT FS TrCH1: (1x0) bitMode TrCH1: type 1: 0 TrCH1: One All TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 TrCH1: 7x10 TrCH2- TrCH4: Absent
-3
SameAsUL
SameAsUL
TrCH1: 1, TrCH2: 2
TrCH1: 1, TrCH2: 2
TrCH1: 1x10 TrCH2: Absent
-2
-2
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS
1 FALSE Absent, not required Normal TFCI signalling
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling Complete Ctfc4Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF2, TF0) 2 Computed 0 (TF0, TF1) 3 Computed N/A N/A 0 (TF1, TF1) 4 Computed 0 (TF2, TF1) 5 Signalled 8 15 0
1072 57.6 kbps streaming CSdata + 3.4 kbps signalling Complete Ctfc4Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF2, TF0) 2 Computed 0 (TF3, TF0) 3 Computed N/A N/A 0 (TF4, TF0) 4 Computed 0 (TF0, TF1) 5 Computed N/A N/A 0 (TF1, TF1) 6 Computed 0 (TF2, TF1) 7 Computed 0 (TF3, TF1) 8
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 8 Computed 0 (TF3, TF2, TF0, TF0) 15 Computed N/A N/A 0 (TF4, TF3, TF0, TF0) 22 Computed 0 (TF5, TF4, TF1, TF0) 59 Computed N/A N/A 0 (TF0,TF0,TF0,TF1) 60 Computed 0 (TF1,TF0,TF0,TF1) 61 Computed 0 (TF2,TF1,TF0,TF1) 68
>>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 9 >>>>>>>ctfc
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling
1073 57.6 kbps streaming CSdata + 3.4 kbps signalling Computed 0 (TF4, TF1) 9 Signalled 8 15 0
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling Computed 0 (TF3,TF2,TF0,TF1) 75 Computed N/A N/A 0 (TF4,TF3,TF0,TF1) 82 Computed 0 (TF5,TF4,TF1,TF1) 119 Signalled 11 15 0
>>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 11 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 12 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPrede f >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMod e >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo
Same as UL
Same as UL
Same as UL
64 TRUE 8 Flexible
32 TRUE 8 Flexible
128 FALSE 4 Fixed
3GPP
Release 6 Configuration 28.8 kbps streaming CSdata + 3.4 kbps signalling frameRelated 16 0.44 repetitionPeriod1
1074 57.6 kbps streaming CSdata + 3.4 kbps signalling frameRelated 16 0.48 repetitionPeriod1
3GPP TS 25.331 V6.23.0 (2009-09) 12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling frameRelated 16 0.92 repetitionPeriod1
>>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMod e >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
3GPP
Release 6 Configuration 10.2/6.7/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 5a 11
1075 7.4/6.7/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 7a 12
3GPP TS 25.331 V6.23.0 (2009-09)
>>>maxDat
>>timerRST
>>max-RST
>>pollingInfo
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7, RB8: 8 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: 300 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB8: TM RB1: N/A RB2- RB3: TRUE RB5- RB8: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB8: N/A RB1: N/A RB2- RB3: as below RB5- RB8: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB6: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB6: N/A RB1: N/A RB2- RB3: 15 RB5- RB6: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB6: N/A RB1: N/A RB2- RB3: 300 RB5- RB6: N/A RB1: N/A RB2- RB3: 1 RB5- RB6: N/A RB1: N/A RB2- RB3: as below RB5- RB6: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB6: FALSE RB1: UM RB2- RB3: AM RB5- RB6: TM RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic
3GPP
Release 6 >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity RB1- RB3: N/A RB5- RB8: FALSE OneLogicalChannel Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3, RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1076 RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 3 RB5: 1, RB6: 2 RB1: 1, RB2: 2, RB3: 3 RB5- RB6: N/A RB1- RB3: configured RB5- RB6: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB6: 5
3GPP TS 25.331 V6.23.0 (2009-09)
>>rlc-SizeList
One mapping option Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3, RB8: 5 RB1: 1, RB2: 2, RB3: 3 RB5- RB8: N/A
One mapping option Dch RB1- RB3: 3 RB5: 1, RB6: 2, RB7:4 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 DedicatedTransChT FS TrCH1: (0x65) TrCH2: (0x 99) TrCH3: (0x 40, 1x40) TrCH4: (0x144, 1x144) BitMode TrCH1: type 1: 65 TrCH2: type 1: 99 TrCH3: type 1: 40 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-2: Zero TrCH3-4: Zero, one All TrCH1: (1x39) TrCH2: (1x 53) TrCH3- TrCH4: N/A TrCH1: One TrCH2: One TrCH1-2: BitMode TrCH1: 1: 39 TrCH2: 1: 53 TrCH1-2: One
dch TrCH1: 1, TrCH2: 2, TrCH3: 3 DedicatedTransChT FS TrCH1: (0x61) TrCH2: (0x 87) TrCH3: (0x 144, 1x144)
BitMode TrCH1: type 1: 61 TrCH2: type 1: 87 TrCH3: 2: type 2, part1= 2, part2= 0 (144) TrCH1-2: Zero TrCH3: Zero, one All TrCH1: (1x39) TrCH2: (1x53) TrCH3: N/A TrCH1: One TrCH2: One TrCH1-2: BitMode TrCH1: 1: 39 TrCH1: 1: 53 TrCH1-2: One
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList
3GPP
Release 6 >>>>logicalChannelList >>>tf 2 TrCH1: all TrCH1: (1x42) TrCH2: (1x63) TrCH3- TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 42 TrCH2: type 1: 63 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x55) TrCH2: (1x76) TrCH3- TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 55 TrCH2: type 1: 76 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x58) TrCH2: (1x99) TrCH3- TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 58 TrCH2: type 1: 99 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x65) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 65 TrCH1: One TrCH1: all TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16
1077 TrCH1: all TrCH1: (1x42) TrCH2: (1x63) TrCH3: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 42 TrCH2: type 1: 63 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x55) TrCH2: (1x76) TrCH3: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 55 TrCH2: type 1: 76 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x58) TrCH2: (1x87) TrCH3: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 58 TrCH2: type 1: 87 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x61) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 61 TrCH1: One TrCH1: all TrCH1- TrCH2: 20 TrCH3: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Third TrCH1: 200 TrCH2: 190 TrCH3: 160 TrCH1: 12 TrCH2: 0 TrCH3: 16
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 5 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType >>>>codingRate
>>>crc-Size
DLAddReconfTransChInfoList >Downlink transport channel type
dch
dch
3GPP
Release 6 >dlTransportChannelIdentity >tfs-SignallingMode TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4, TrCH5: 5 Independent <Only tf0 on TrCH1 and tf0/tf1 on TrCH5 are different and shown below>
1078 TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 Independent <Only tf0 on TrCH1 and tf0/tf1 on TrCH4 are different and shown below>
3GPP TS 25.331 V6.23.0 (2009-09)
>>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>semistaticTFInformation >>>>tti >>>>channelCodingType >>>>>codingRate >>>>rateMatchingAttribute >>>>crc-Size >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue
TrCH1: (1x0) TrCH5: (0x3, 1x3) BitMode TrCH1: type 1: 0 TrCH5: type 1: 3 TrCH1: One TrCH5: Zero, one All same as UL except for TrCH5 TrCH5: 20 Convolutional TrCH5: Third TrCH5: 200 TrCH5: 12 TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4, TrCH1: 7x10 TrCH2- TrCH5: Absent
-3
TrCH1: (1x0) TrCH4: (0x3, 1x3) bitMode TrCH1: type 1: 0 TrCH4: type 1: 3 TrCH1: One TrCH4: Zero, one All same as UL except for TrCH4 TrCH4: 20 Convolutional TrCH4: Third TrCH4: 200 TrCH4: 12 TrCH1: 1, TrCH2: 2, TrCH3: 3 TrCH1: 7x10 TrCH2- TrCH4: Absent
-3
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFC list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 8 Computed 0
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition (TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0) 8 Computed 0
3GPP
Release 6 >>>>>>TFC 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 11 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 12 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d (TF3, TF2, TF0, TF0) 15 Computed
1079 (TF3, TF2, TF0) 15 Computed
3GPP TS 25.331 V6.23.0 (2009-09)
0 (TF4, TF3, TF0, TF0) 22 Computed 0 (TF5, TF4, TF1, TF0) 59 Computed
0 (TF4, TF3, TF0) 22 Computed 0 (TF5, TF4, TF0) 29 Computed
0 (TF0, TF0, TF0, TF1) 60 Computed 0 (TF1, TF0, TF0, TF1) 61 computed
0 (TF0, TF0, TF1) 30 Computed 0 (TF1, TF0, TF1) 31 computed
0 (TF2, TF1, TF0, TF1) 68 computed 0 (TF3, TF2, TF0, TF1) 75 computed
0 (TF2, TF1, TF1) 38 computed 0 (TF3, TF2, TF1) 45 computed
0 (TF4, TF3, TF0, TF1) 82 computed 0 (TF5, TF4, TF1, TF1) 119 signalled 11 15
0 (TF4, TF3, TF1) 52 computed 0 (TF5, TF4, TF1) 59 signalled 11 15
3GPP
Release 6 >>>>>>>>referenceTFCId > TFC subset list >>TFC subset 1 >>> Allowed transport format combination list 0 (speech rate 10.2) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC7, TFC8, TFC6, TFC9, TFC10, TFC11, TFC12) (speech rate 6.7) (TFC1, TFC2, TFC3, TFC4, TFC7, TFC8, TFC5, TFC9, TFC10, TFC11) (speech rate 5.9) (TFC1, TFC2, TFC3,TFC7, TFC8, TFC4, TFC9, TFC10) (speech rate 4.75) (TFC1, TFC2, TFC7, TFC8, TFC3, TFC9) Independent 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0, TF0) 0 (TF1, TF0, TF0, TF0, TF0) 1 (TF2, TF1, TF0, TF0, TF0) 8 (TF3, TF2, TF0, TF0, TF0) 15 (TF4, TF3, TF0, TF0, TF0) 22 (TF5, TF4, TF1, TF0, TF0) 59 (TF0, TF0, TF0, TF1, TF0) 60 (TF1, TF0, TF0, TF1, TF0) 61 (TF2, TF1, TF0, TF1, TF0) 68 (TF3, TF2, TF0, TF1, TF0) 75 0
1080
3GPP TS 25.331 V6.23.0 (2009-09)
>>TFC subset 2 >>> Allowed transport format combination list
>>TFC subset 4 >>> Allowed transport format combination list dl-CommonTransChInfo >tfcs-SignallingMode >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >dl-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>TFC 2 >>>>>>>ctfc >>>>>>TFC 3 >>>>>>>ctfc >>>>>>TFC 4 >>>>>>>ctfc >>>>>>TFC 5 >>>>>>>ctfc >>>>>>TFC 6 >>>>>>>ctfc >>>>>>TFC 7 >>>>>>>ctfc >>>>>>TFC 8 >>>>>>>ctfc >>>>>>TFC 9 >>>>>>>ctfc >>>>>>TFC 10 >>>>>>>ctfc
(speech rate 7.4) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC7, TFC8, TFC6, TFC9, TFC10, TFC11, TFC12) (speech rate 6.7) (TFC1, TFC2, TFC3, TFC4, TFC7, TFC8, TFC5, TFC9, TFC10, TFC11) (speech rate 5.9) (TFC1, TFC2, TFC3, TFC7, TFC8, TFC4, TFC9, TFC10) (speech rate 4.75) (TFC1, TFC2, TFC7, TFC8, TFC3, TFC9) Independent 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0) 0 (TF1, TF0, TF0, TF0) 1 (TF2, TF1, TF0, TF0) 8 (TF3, TF2, TF0, TF0) 15 (TF4, TF3, TF0, TF0) 22 (TF5, TF4, TF0, TF0) 29 (TF0, TF0, TF1, TF0) 30 (TF1, TF0, TF1, TF0) 31 (TF2, TF1, TF1, TF0) 38 (TF3, TF2, TF1, TF0) 45
3GPP
Release 6 >>>>>>TFC 11 >>>>>>>ctfc >>>>>>TFC 12 >>>>>>>ctfc >>>>>>TFC 13 >>>>>>>ctfc >>>>>>TFC 14 >>>>>>>ctfc >>>>>>TFC 15 >>>>>>>ctfc >>>>>>TFC 16 >>>>>>>ctfc >>>>>>TFC 17 >>>>>>>ctfc >>>>>>TFC 18 >>>>>>>ctfc >>>>>>TFC 19 >>>>>>>ctfc >>>>>>TFC 20 >>>>>>>ctfc >>>>>>TFC 21 >>>>>>>ctfc >>>>>>TFC 22 >>>>>>>ctfc >>>>>>TFC 23 >>>>>>>ctfc >>>>>>TFC 24 >>>>>>>ctfc PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue (TF4, TF3, TF0, TF1, TF0) 82 (TF5, TF4, TF1, TF1, TF0) 119 (TF0, TF0, TF0, TF0, TF1) 120 (TF1, TF0, TF0, TF0, TF1) 121 (TF2, TF1, TF0, TF0, TF1) 128 (TF3, TF2, TF0, TF0, TF1) 135 (TF4, TF3, TF0, TF0, TF1) 142 (TF5, TF4, TF1, TF0, TF1) 179 (TF0, TF0, TF0, TF1, TF1) 180 (TF1, TF0, TF0, TF1, TF1) 181 (TF2, TF1, TF0, TF1, TF1) 188 (TF3, TF2, TF0, TF1, TF1) 195 (TF4, TF3, TF0, TF1, TF1) 202 (TF5, TF4, TF1, TF1, TF1) 239
1081 (TF4, TF3, TF1, TF0) 52 (TF5, TF4, TF1, TF0) 59 (TF0, TF0, TF0, TF1) 60 (TF1, TF0, TF0, TF1) 61 (TF2, TF1, TF0, TF1) 68 (TF3, TF2, TF0, TF1) 75 (TF4, TF3, TF0, TF1) 82 (TF5, TF4, TF0, TF1) 89 (TF0, TF0, TF1, TF1) 90 (TF1, TF0, TF1, TF1) 91 (TF2, TF1, TF1, TF1) 98 (TF3, TF2, TF1, TF1) 105 (TF4, TF3, TF1, TF1) 112 (TF5, TF4, TF1, TF1) 119
3GPP TS 25.331 V6.23.0 (2009-09)
128 FALSE 4 Fixed
128 FALSE 4 Fixed
3GPP
Release 6 >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
1082
3GPP TS 25.331 V6.23.0 (2009-09)
frame Related 16 0.64 repetitionPeriod1
NOTE :
Default configuration identity 11 can not be used with release 4 UEs.
3GPP
Release 6 Configuration 12.65/8.85/6.6 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 62 13
1083
3GPP TS 25.331 V6.23.0 (2009-09)
>>>maxDat
>>timerRST
>>max-RST
>>pollingInfo
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7, RB8: 8 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB1: N/A RB2- RB3: 300 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB8: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB8: N/A RB1: N/A RB2- RB3: 128 for UEs with more than 10 kbyte "total RLC AM buffer size" and 32 otherwise RB5- RB7: N/A RB8: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB8: N/A
>>dl-RLC-StatusInfo
3GPP
Release 6 >>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic >>segmentationIndication RB2- RB3: 100 RB2- RB3: FALSE RB2- RB3: 300 RB1- RB3: N/A RB5- RB7: FALSE RB8: FALSE OneLogicalChannel Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3. RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1084
3GPP TS 25.331 V6.23.0 (2009-09)
rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity
>>rlc-SizeList
One mapping option Dch RB1- RB3: 4 RB5: 1, RB6: 2, RB7: 3, RB8: 5 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB8: N/A
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4 DedicatedTransChT FS TrCH1: (0x72) TrCH2: (0x 181) TrCH3: (0x60) TrCH4: (0x144, 1x144) BitMode TrCH1: type 1: 72 TrCH2: type 2: part1= 6, part2= 5 TrCH3: type1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-3: Zero TrCH4: Zero, one All TrCH1: (1x40) TrCH2: (1x 78) TrCH3: N/A TrCH4: N/A
3GPP
Release 6 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 2 TrCH1: One TrCH2: One TrCH1-2: BitMode TrCH1: 1: 40 TrCH2: 1: 78 TrCH1-2: One TrCH1: all TrCH1: (1x54) TrCH2: (1x113) TrCH3: N/A TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 54 TrCH2: type 1: 113 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x64) TrCH2: (1x181) TrCH3: N/A TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 64 TrCH2: type 2: part1=6, part2= 5 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x72) TrCH2: N/A TrCH3: N/A TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 72 TrCH1: One TrCH1: all TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH3: Third TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 256 TrCH4: 170 TrCH1: 12 TrCH2: 0 TrCH3: 0 TrCH4: 16
1085
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType >>>>codingRate
>>>crc-Size
DLAddReconfTransChInfoList >Downlink transport channel type >dlTransportChannelIdentity
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4, TrCH5: 5
3GPP
Release 6 >tfs-SignallingMode Independent <Only tf0 on TrCH1 and tf0/tf1 on TrCH5 are different and shown below>
1086
3GPP TS 25.331 V6.23.0 (2009-09)
TrCH1: (1x0) TrCH5: (0x3, 1x3) BitMode TrCH1: type 1: 0 TrCH5: type 1: 3 TrCH1: One TrCH5: Zero, one All same as UL except for TrCH5 TrCH5: 20 Convolutional TrCH5: Third TrCH5: 205 TrCH5: 8 TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 4, TrCH1: 7x10 TrCH2: Absent TrCH3: Absent TrCH4- TrCH5: Absent
-3
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFC list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 7 Computed 0
3GPP
Release 6 >>>>>>TFC 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId > TFC subset list >>TFC subset 1 >>> Allowed transport format combination list >>TFC subset 2 >>> Allowed transport format combination list >>TFC subset 3 >>> Allowed transport format combination list (TF3, TF2, TF0, TF0) 13 Computed
1087
3GPP TS 25.331 V6.23.0 (2009-09)
0 (TF1, TF0, TF0, TF1) 21 Computed 0 (TF2, TF1, TF0, TF1) 27 computed
0 (TF3, TF2, TF0, TF1) 33 computed 0 (TF4, TF3, TF0, TF1) 39 signalled 11 15 0 (speech rate 6.6) (TFC1, TFC2, TFC3, TFC6, TFC7, TFC8) (speech rate 8.85) (TFC1, TFC2, TFC3, TFC4, TFC6, TFC7, TFC8, TFC9) (speech rate 12.65) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC6, TFC7, TFC8, TFC9, TFC10)
3GPP
Release 6 dl-CommonTransChInfo >tfcs-SignallingMode ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >dl-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>TFC 2 >>>>>>>ctfc >>>>>>TFC 3 >>>>>>>ctfc >>>>>>TFC 4 >>>>>>>ctfc >>>>>>TFC 5 >>>>>>>ctfc >>>>>>TFC 6 >>>>>>>ctfc >>>>>>TFC 7 >>>>>>>ctfc >>>>>>TFC 8 >>>>>>>ctfc >>>>>>TFC 9 >>>>>>>ctfc >>>>>>TFC 10 >>>>>>>ctfc >>>>>>TFC 11 >>>>>>>ctfc >>>>>>TFC 12 >>>>>>>ctfc >>>>>>TFC 13 >>>>>>>ctfc >>>>>>TFC 14 >>>>>>>ctfc >>>>>>TFC 15 >>>>>>>ctfc >>>>>>TFC 16 >>>>>>>ctfc >>>>>>TFC 17 >>>>>>>ctfc
1088
3GPP TS 25.331 V6.23.0 (2009-09)
Independent 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0, TF0) 0 (TF1, TF0, TF0, TF0, TF0) 1 (TF2, TF1, TF0, TF0, TF0) 7 (TF3, TF2, TF0, TF0, TF0) 13 (TF4, TF3, TF0, TF0, TF0) 19 (TF0, TF0, TF0, TF1, TF0) 20 (TF1, TF0, TF0, TF1, TF0) 21 (TF2, TF1, TF0, TF1, TF0) 27 (TF3, TF2, TF0, TF1, TF0) 33 (TF4, TF3, TF0, TF1, TF0) 39 (TF0, TF0, TF0, TF0, TF1) 40 (TF1, TF0, TF0, TF0, TF1) 41 (TF2, TF1, TF0, TF0, TF1) 47 (TF3, TF2, TF0, TF0, TF1) 53 (TF4, TF3, TF0, TF0, TF1) 59 (TF0, TF0, TF0, TF1, TF1) 60 (TF1, TF0, TF0, TF1, TF1) 61
3GPP
Release 6 >>>>>>TFC 18 >>>>>>>ctfc >>>>>>TFC 19 >>>>>>>ctfc >>>>>>TFC 20 >>>>>>>ctfc PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed (TF2, TF1, TF0, TF1, TF1) 67 (TF3, TF2, TF0, TF1, TF1) 73 (TF4, TF3, TF0, TF1, TF1) 79
1089
3GPP TS 25.331 V6.23.0 (2009-09)
128 FALSE 4 Fixed
Configuration
12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 4b 14
>>>maxDat
>>transmissionWindowSiz e >>timerRST
>>max-RST
>>pollingInfo
>>>TimerPoll >>>PollPDU >>>PollSDU
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7, RB8: 8 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 25 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 200 RB2- RB3: n/a RB2- RB3: 1
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB8: TM RB1: N/A RB2- RB3: TRUE RB5- RB8: N/A RB1: N/A RB2- RB3: 32 RB5- RB8: N/A RB1: N/A RB2- RB3: as below RB5- RB8: N/A RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A RB5- RB8: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3. RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1090
3GPP TS 25.331 V6.23.0 (2009-09)
>>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>segmentationIndication >dl-RLC-Mode
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdenti ty >>logicalChannelIdentity
>>rlc-SizeList
One mapping option Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3, RB8: 5 RB1: 1, RB2: 2, RB3: 3 RB5- RB8: N/A
TrCH INFORMATION PER TrCH ULAddReconfTransChInfoLis t >Uplink transport channel type >transportChannelIdentity
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 DedicatedTransChT FS TrCH1: (0x81) TrCH2: (0x 103) TrCH3: (0x60) TrCH4: (0x144, 1x144) BitMode TrCH1: type 1: 81 TrCH2: type 1: 103 TrCH3: type1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-3: Zero TrCH4: Zero, one All TrCH1: (1x39) TrCH2: (1x53) TrCH3: (1x60) TrCH4: (1x144) TrCH1-3: One TrCH1-3: BitMode TrCH1: 1: 39 TrCH2: 1: 53 TrCH3: 1: 60 TrCH1-3: One TrCH1-3: all TrCH1: (1x42) TrCH2: (1x63) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 42 TrCH2: type 1: 63 TrCH1-2: One TrCH1: all TrCH1: (1x55) TrCH2: (1x87) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 55 TrCH2: type 1: 87 TrCH1-2: One TrCH1: all TrCH1: (1x61) TrCH2: (1x103) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 61 TrCH2: type 1: 103 TrCH1-2: One TrCH1: all TrCH1: (1x81) TrCH2- TrCH4: N/A
1091
3GPP TS 25.331 V6.23.0 (2009-09)
>transportFormatSet >>dynamicTF-information >>>tf0/ tf0,1
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 TrCH1: One TrCH1: BitMode TrCH1: type 1: 81 TrCH1: One TrCH1: all
1092
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semiStaticTFInformation >>>tti >>>channelCodingType >>>>codingRate
>>>crc-Size
TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16
DLAddReconfTransChInfoLis t >Downlink transport channel type >dlTransportChannelIdentity >tfs-SignallingMode
TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9, TrCH5: 5 Independent <Only tf0 on TrCH1 and tf0/tf1 on TrCH5 are different and shown below>
TrCH1: (1x0) TrCH5: (0x3, 1x3) bitMode TrCH1: type 1: 0 TrCH5: type 1: 3 TrCH1: One TrCH5: Zero, one all same as UL except for TrCH5 TrCH5: 20 Convolutional TrCH5: Third TrCH5: 205 TrCH5: 8 TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 TrCH1: 7x10 TrCH2: Absent TrCH3: Absent TrCH4- TrCH5: Absent
-3
TrCH INFORMATION, COMMON
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 8 Computed 0 (TF3, TF2, TF0, TF0) 15 Computed N/A N/A 0 (TF4, TF3, TF0, TF0) 22 Computed 0 (TF5, TF4, TF1, TF0) 59 Computed N/A N/A 0 (TF0,TF0,TF0,TF1) 60 Computed 0 (TF1,TF0,TF0,TF1)
1093
3GPP TS 25.331 V6.23.0 (2009-09)
ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 8
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 61 Computed 0 (TF2,TF1,TF0,TF1) 68 Computed 0 (TF3,TF2,TF0,TF1) 75 Computed N/A N/A 0 (TF4,TF3,TF0,TF1) 82 Computed 0 (TF5,TF4,TF1,TF1) 119 Signalled 11 15 0 (speech rate 4.75) (TFC1, TFC2, TFC3, TFC7, TFC8, TFC9) (speech rate 5.9) (TFC1, TFC2, TFC3, TFC4, TFC7, TFC8, TFC9, TFC10) (speech rate 7.4) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC7, TFC8, TFC9, TFC10, TFC11) (speech rate 12.2) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC6, TFC7, TFC8, TFC9, TFC10, TFC11, TFC12) Independent 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit
1094
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 11 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 12 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId > TFC subset list >>TFC subset 1 >>> Allowed transport format combination list >>TFC subset 2 >>> Allowed transport format combination list
dl-CommonTransChInfo >tfcs-SignallingMode ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >dl-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 Addition (TF0, TF0, TF0, TF0, TF0) 0 (TF1, TF0, TF0, TF0, TF0) 1 (TF2, TF1, TF0, TF0, TF0) 8 (TF3, TF2, TF0, TF0, TF0) 15 (TF4, TF3, TF0, TF0, TF0) 22 (TF5,TF4,TF1,TF0, TF0) 59 (TF0, TF0, TF0, TF1, TF0) 60 (TF1, TF0, TF0, TF1, TF0) 61 (TF2, TF1, TF0, TF1, TF0) 68 (TF3, TF2, TF0, TF1, TF0) 75 (TF4, TF3, TF0, TF1, TF0) 82 (TF5,TF4,TF1,TF1, TF0) 119 (TF0, TF0, TF0, TF0, TF1) 120 (TF1, TF0, TF0, TF0, TF1) 121 (TF2, TF1, TF0, TF0, TF1) 128 (TF3, TF2, TF0, TF0, TF1) 135 (TF4, TF3, TF0, TF0, TF1) 142 (TF5,TF4,TF1,TF0, TF1) 179 (TF0, TF0, TF0, TF1, TF1) 180 (TF1, TF0, TF0, TF1, TF1)
1095
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>TFCS representation >>>>>TFCS list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>TFC 2 >>>>>>>ctfc >>>>>>TFC 3 >>>>>>>ctfc >>>>>>TFC 4 >>>>>>>ctfc >>>>>>TFC 5 >>>>>>>ctfc >>>>>>TFC 6 >>>>>>>ctfc >>>>>>TFC 7 >>>>>>>ctfc >>>>>>TFC 8 >>>>>>>ctfc >>>>>>TFC 9 >>>>>>>ctfc >>>>>>TFC 10 >>>>>>>ctfc >>>>>>TFC 11 >>>>>>>ctfc >>>>>>TFC 12 >>>>>>>ctfc >>>>>>TFC 13 >>>>>>>ctfc >>>>>>TFC 14 >>>>>>>ctfc >>>>>>TFC 15 >>>>>>>ctfc >>>>>>TFC 16 >>>>>>>ctfc >>>>>>TFC 17 >>>>>>>ctfc >>>>>>TFC 18 >>>>>>>ctfc >>>>>>TFC 19 >>>>>>>ctfc >>>>>>TFC 20
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5 181 (TF2, TF1, TF0, TF1, TF1) 188 (TF3, TF2, TF0, TF1, TF1) 195 (TF4, TF3, TF0, TF1, TF1) 202 (TF5,TF4,TF1,TF1, TF1) 239
1096
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>>>ctfc >>>>>>TFC 21 >>>>>>>ctfc >>>>>>TFC 22 >>>>>>>ctfc >>>>>>TFC 23 >>>>>>>ctfc >>>>>>TFC 24 >>>>>>>ctfc PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPrede f >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMod e >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMod e >>tfci-Coding
128 FALSE 4 Fixed
3GPP
Release 6 Configuration 12.2/7.4/5.9/4.75 kbps speech + 3.4 kbps signalling + 0.15 kbps SRB#5
1097
3GPP TS 25.331 V6.23.0 (2009-09)
>>puncturingLimit >>repetitionPeriodAndLen gth DLCommonInformationPrede f >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMo de >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
Configuration
7.95 kbps speech + 3.4 kbps signalling 6 15
>>>maxDat
>>max-RST
>>pollingInfo
>>>TimerPoll >>>PollPDU >>>PollSDU >>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>segmentationIndication
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 25 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 200 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB5- RB7: FALSE
3GPP
Release 6 Configuration 7.95 kbps speech + 3.4 kbps signalling RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1098
3GPP TS 25.331 V6.23.0 (2009-09)
>dl-RLC-Mode
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity
>>rlc-SizeList
dch TrCH1: 1, TrCH2: 2, TrCH3:3, TrCH4: 9 DedicatedTransChT FS TrCH1: (0x75) TrCH2: (0x 84 1x84) TrCH3: (0x 60) TrCH4: (0x144, 1x144) BitMode
>>>>rlcSize
3GPP
Release 6 Configuration 7.95 kbps speech + 3.4 kbps signalling TrCH1: type 1: 75 TrCH2: type 1: 84 TrCH3: type 1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero TrCH2-4: Zero, one All TrCH1: (1x39) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: 1: 39 TrCH1: One TrCH1: all TrCH1: (1x75) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 75 TrCH1: One TrCH1: all TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2-TrCH3: 0 TrCH4: 16
1099
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>sizeType
>>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 1 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 2 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType >>>>codingRate
>>>crc-Size
Dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 Explicit <Only tf0 on TrCH1 is different and shown below> DedicatedTransChT FS TrCH1: (1x0) BitMode TrCH1: type 1: 0 TrCH1: One All TrCH1: 1, TrCH2: 2, TrCH3:3, TrCH4: 9
>>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>ULTrCH-Id >dch-QualityTarget
3GPP
Release 6 Configuration 7.95 kbps speech + 3.4 kbps signalling TrCH1: 7x10-3 TrCH2- TrCH4: Absent
1100
3GPP TS 25.331 V6.23.0 (2009-09)
>>bler-QualityValue
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFCS 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId dl-CommonTransChInfo
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc4Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 5 Computed 0 (TF0, TF0, TF0, TF1) 6 Computed N/A N/A 0 (TF1, TF0, TF0, TF1) 7 Computed 0 (TF2, TF1, TF0, TF1) 11 Signalled 11 15 0
3GPP
Release 6 Configuration 7.95 kbps speech + 3.4 kbps signalling Same as UL
1101
3GPP TS 25.331 V6.23.0 (2009-09)
>tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth
128 FALSE 4 Fixed
3GPP
Release 6
1102
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6 Configuration 12.65/8.85/6.6 kbps speech + 3.4 kbps signalling (without SRB#5) 7.1.106 16
1103
3GPP TS 25.331 V6.23.0 (2009-09)
>>>maxDat
>>max-RST
>>pollingInfo
>>>TimerPoll >>>PollPDU >>>PollSDU >>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>segmentationIndication >dl-RLC-Mode
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7, Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 25 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 200 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType
3GPP
Release 6 >>>transportChannelIdentit y >>logicalChannelIdentity RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3. RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1104
3GPP TS 25.331 V6.23.0 (2009-09)
>>rlc-SizeList
One mapping option Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3, RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A
Dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 DedicatedTransChT FS TrCH1: (0x72) TrCH2: (0x 181) TrCH3: (0x60) TrCH4: (0x144, 1x144) BitMode TrCH1: type 1: 72 TrCH2: type 2: part1= 6, part2= 5 TrCH3: type1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-3: Zero TrCH4: Zero, one All TrCH1: (1x40) TrCH2: (1x 78) TrCH3: N/A TrCH4: N/A TrCH1: One TrCH2: One TrCH1-2: BitMode TrCH1: 1: 40 TrCH2: 1: 78 TrCH1-2: One TrCH1: all TrCH1: (1x54) TrCH2: (1x113) TrCH3: N/A TrCH4: N/A
3GPP
Release 6 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 3 TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 54 TrCH2: type 1: 113 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x64) TrCH2: (1x181) TrCH3: N/A TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 64 TrCH2: type 2: part1=6, part2= 5 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x72) TrCH2: N/A TrCH3: N/A TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 72 TrCH1: One TrCH1: all TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH3: Third TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 256 TrCH4: 170 TrCH1: 12 TrCH2: 0 TrCH3: 0 TrCH4: 16
1105
3GPP TS 25.331 V6.23.0 (2009-09)
>>>crc-Size
DLAddReconfTransChInfoList >Downlink transport channel type >dlTransportChannelIdentity >tfs-SignallingMode
Dch
Independent <Only tf0 on TrCH1 is different and shown below>
>>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList
TrCH1: (1x0) BitMode TrCH1: type 1: 0 TrCH1: One All
3GPP
Release 6 >>>semistaticTFInformation >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue same as UL TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9, TrCH1: 7x10 TrCH2: Absent TrCH3: Absent TrCH4: Absent
-3
1106
3GPP TS 25.331 V6.23.0 (2009-09)
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFC list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 7 Computed 0 (TF3, TF2, TF0, TF0) 13 Computed
3GPP
Release 6 >>>>>>>>referenceTFCId >>>>>>TFC 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 10 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId > TFC subset list >>TFC subset 1 >>> Allowed transport format combination list >>TFC subset 2 >>> Allowed transport format combination list >>TFC subset 3 >>> Allowed transport format combination list 0 (TF1, TF0, TF0, TF1) 21 Computed 0 (TF2, TF1, TF0, TF1) 27 computed
1107
3GPP TS 25.331 V6.23.0 (2009-09)
0 (TF3, TF2, TF0, TF1) 33 computed 0 (TF4, TF3, TF0, TF1) 39 signalled 11 15 0 (speech rate 6.6) (TFC1, TFC2, TFC3, TFC6, TFC7, TFC8) (speech rate 8.85) (TFC1, TFC2, TFC3, TFC4, TFC6, TFC7, TFC8, TFC9) (speech rate 12.65) (TFC1, TFC2, TFC3, TFC4, TFC5, TFC6, TFC7, TFC8, TFC9, TFC10) Same as UL 1 FALSE
dl-CommonTransChInfo >tfcs-SignallingMode ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits
128 FALSE 4
3GPP
Release 6 >>positionFixed Fixed
1108
3GPP TS 25.331 V6.23.0 (2009-09)
Configuration
Ref 25.993 Default configuration identity RB INFORMATION rb-Identity rlc-InfoChoice >ul-RLC-Mode >>transmissionRLCDiscardMode >>>maxDat >>transmissionWindowSiz e >>timerRST >>max-RST >>pollingInfo >>>TimerPoll >>>PollPDU >>>PollSDU >>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>segmentationIndication >dl-RLC-Mode >>DL RLC PDU size >>inSequenceDelivery >>receivingWindowSize >>dl-RLC-StatusInfo >>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication >>dl-UM-RLC-LI-size Rb-MappingInfo >ULLogicalChannelMappings >>UplinkTransport ChannelTypeChoice >>ulTransportChannelType >>>logicalChannelIdentity >>>E-DCH MAC-d flow identity >>>DDI >>>>RLC PDU size >>macLogicalChannelPriority
Signalling on E-DCH on UL depending based on minimum EDCH UE category + Signalling on HSDSCH based minimum HS-DSCH UE category 7.5.10 17
RB1: 1, RB2: 2, RB3: 3 Rlc-info RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: NoDiscard RB1: N/A RB2- RB3: 25 RB1: N/A RB2- RB3: 128 RB1: N/A RB2- RB3: 200 RB1: N/A RB2- RB3: 1 RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: FALSE RB2- RB3: 99 RB1- RB3: N/A RB1: UM RB2- RB3: AM RB1-RB3: 144 RB1: N/A RB2- RB3: TRUE RB1: N/A RB2- RB3: 128 RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A 7 OneLogicalChannel
E-DCH RB1: 1, RB2: 2, RB3: 3 RB1-RB3:0 RB1: 1, RB2: 2, RB3: 3 144 RB1: 1, RB2: 2, RB3: 3
3GPP
Release 6 Configuration
1109 Signalling on E-DCH on UL depending based on minimum EDCH UE category + Signalling on HSDSCH based minimum HS-DSCH UE category OneLogicalChannel One mapping option HS-DSCH RB1- RB3: 0 RB1: 1, RB2: 2, RB3: 3
3GPP TS 25.331 V6.23.0 (2009-09)
>DLlogicalChannelMappings >>Mapping option 1 >>>dlTransportChannelType >>>>Mac-d flow identity >>>logicalChannelIdentity TrCH INFORMATION PER TrCH ULAddReconfTransChInfoList >Uplink transport channel type >UL Transport channel identity > UL-ParametersChoice >> E-DCH Transmission Time Interval >> HARQ info for E-DCH >>> HARQ RV Configuration >> Added or reconfigured E-DCH MAC-d flow >>> E-DCH MAC-d flow identity >>> E-DCH MAC-d flow power offset >>> E-DCH MAC-d flow maximum number of retransmissions >>> E-DCH MAC-d flow multiplexing list >>> transmission grant typeChoice >>>> Non-scheduled transmission grant info >>>>> Max MAC-e PDU contents size DLAddReconfTransChInfoList >Downlink transport channel type >DL-ParametersChoice >>HARQ Info >>>Number of Processes >>>Memory PartitioningChoice >>>>Implicit >>Added or reconfigured MAC-d flow >>> MAC-hs queue to add or reconfigure list >>>>MAC-hs queue Id >>>>MAC-d Flow Identity >>>>T1 >>>>MAC-hs window size >>>>MAC-d PDU size info >>>>>MAC-d PDU size >>>>>MAC-d PDU size index
E-DCH
10
Rvtable One MAC-d flow 0 4 5
Non-scheduled 162
HS-DSCH
0 0 100 12 148 0
3GPP
1110 Signalling on E-DCH on UL depending based on minimum EDCH UE category + Signalling on HSDSCH based minimum HS-DSCH UE category Null
3GPP TS 25.331 V6.23.0 (2009-09)
TrCH INFORMATION, COMMON
Configuration
12.2 kbps speech + 13.6 kbps signalling 7.1.131 18
12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling 7.1.132 19
>>>maxDat
>>max-RST
>>pollingInfo
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB2- RB3: n/a RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A
RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7 Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 15 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB2- RB3: n/a RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A
>>>TimerPoll >>>PollPDU >>>PollSDU >>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>>timerPollPeriodic >>segmentationIndication >dl-RLC-Mode
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: TRUE RB2- RB3: n/a RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
1111 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: TRUE RB2- RB3: n/a RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3 RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5
3GPP TS 25.331 V6.23.0 (2009-09)
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>>timerStatusPeriodic >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity
>>rlc-SizeList
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 DedicatedTransChT FS TrCH1: (0x81) TrCH2: (0x 103, 1x103) TrCH3: (0x 60, 1x60) TrCH4: (0x144, 1x144, 2x144, 3x144, 4x144) BitMode
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 DedicatedTransChT FS TrCH1: (0x 81) TrCH2: (0x 103) TrCH3: (0x 60) TrCH4: (0x144)
>>>>rlcSize
BitMode
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling TrCH1: type 1: 81 TrCH2: type 1: 103 TrCH3: type 1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1: Zero TrCH2-3: Zero, One TrCH4: Zero, one, 2, 3, 4 All TrCH1: (1x39) TrCH2- TrCH4: N/A
1112 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling TrCH1: type 1: 81 TrCH2: type 1: 103 TrCH3: type 1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-4: Zero
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>sizeType
TrCH1: One TrCH1: BitMode TrCH1: 1: 39
TrCH1: One TrCH1: all TrCH1: (1x81) TrCH2- TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 81 TrCH1: One TrCH1: all
All TrCH1: (1x39) TrCH2: (1x53) TrCH3: (1x60) TrCH4: (1x144, 2x144, 3x144, 4x144) TrCH1-3: One TrCH4: One, 2, 3, 4 TrCH1: BitMode TrCH1: 1: 39 TrCH2: 1: 53 TrCH3: 1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1: One TrCH1: all TrCH1: (1x42) TrCH2: (1x63) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 42 TrCH2: type 1: 63 TrCH1: One TrCH1: all TrCH1: (1x55) TrCH2: (1x84) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 55 TrCH2: type 1: 84 TrCH1-2: One TrCH1: all TrCH1: (1x75) TrCH2: (1x103) TrCH3- TrCH4: N/A TrCH1-2: One TrCH1: BitMode TrCH1: type 1: 75 TrCH2: type 1: 103 TrCH1-2: One TrCH1: all TrCH1: (1x81) TrCH2- TrCH4: N/A
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling
1113 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling TrCH1: One TrCH1: BitMode TrCH1: type 1: 81 TrCH1: One TrCH1: all TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16 TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH2: Third TrCH3: Half TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 235 TrCH4: 160 TrCH1: 12 TrCH2- TrCH3: 0 TrCH4: 16
3GPP TS 25.331 V6.23.0 (2009-09)
>>>crc-Size
dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 Explicit <Only tf0 on TrCH1 is different and shown below> DedicatedTransChT FS TrCH1: (1x0) bitMode TrCH1: type 1: 0 TrCH1: One All TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 TrCH1: 7x10 TrCH2- TrCH4: Absent
-3
TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 Explicit <Only tf0 on TrCH1 is different and shown below> DedicatedTransChT FS TrCH1: (1x0) bitMode TrCH1: type 1: 0 TrCH1: One All TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 TrCH1: 7x10 TrCH2- TrCH4: Absent
-3
TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc8Bit Addition
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed 0 (TF2, TF1, TF1, TF0) 11 Computed 0 (TF0, TF0, TF0, TF1) 12 Computed 0 (TF1, TF0, TF0, TF1) 13 Computed 0 (TF2, TF1, TF1, TF1) 23 Signalled 10 15 0 (TF0, TF0, TF0, TF2) 24 Computed 0 (TF1, TF0, TF0, TF2) 25 Computed 0 (TF0, TF0, TF0, TF3) 36 Computed 0 (TF1, TF0, TF0, TF3) 37
1114 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed 0 (TF2, TF1, TF0, TF0) 8 Computed 0 (TF3, TF2, TF0, TF0) 15 Computed 0 (TF4, TF3, TF0, TF0) 22 Computed 0 (TF5, TF4, TF1, TF0) 59 Computed N/A N/A 0 (TF0,TF0,TF0,TF1) 60 Computed 0 (TF1,TF0,TF0,TF1) 61 Computed 0 (TF2,TF1,TF0,TF1) 68 Computed 0 (TF3,TF2,TF0,TF1) 75
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>>TFC 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 3 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 4 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 5 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 6 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 7 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 8 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 9 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 10 >>>>>>>ctfc
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling Computed 0 (TF0, TF0, TF0, TF4) 48 Computed 0
1115 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling Computed 0 (TF4,TF3,TF0,TF1) 82 Computed 0 (TF5,TF4,TF1,TF1) 119 Signalled 10 15 0 (TF0,TF0,TF0,TF2) 120 Computed 0 (TF1, TF0, TF0, TF2) 121 Computed 0 (TF0,TF0,TF0,TF3) 180 Computed 0 (TF1, TF0, TF0, TF3) 181 Computed 0 (TF0,TF0,TF0,TF4) 240 Computed 0 Same as UL Same as UL
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 11 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 12 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 13 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 14 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 15 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 16 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFC 17 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits
128 TRUE 4
128 TRUE 4
3GPP
Release 6 Configuration 12.2 kbps speech + 13.6 kbps signalling Flexible
1116 12.2/7.95/5.9/4.75 kbps speech + 13.6 kbps signalling Flexible
3GPP TS 25.331 V6.23.0 (2009-09)
>>positionFixed
3GPP
1117 64kbps conv. CSdata + 13.6 kbps signalling 7.1.133 20 RB1: 1, RB2: 2, RB3: 3, RB5: 5 Rlc-info RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: NoDiscard RB5: N/A RB1: N/A RB2- RB3: 25 RB5: N/A RB1: N/A RB2- RB3: 32 RB5: N/A RB1: N/A RB2- RB3: 200 RB5: N/A RB1: N/A RB2- RB3: 1 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB5: FALSE RB1: UM RB2- RB3: AM RB5: TM RB1: N/A RB2- RB3: TRUE RB5: N/A RB1: N/A RB2- RB3: 32 RB5: N/A RB1: N/A RB2- RB3: as below RB5: N/A RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A RB5: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A 12.65/8.85/6.6 kbps speech + 13.6 kbps signalling (without SRB#5) 7.1.134 21 RB1: 1, RB2: 2, RB3: 3, RB5: 5, RB6: 6, RB7: 7, Rlc-info RB1: UM RB2- RB3: AM RB5-RB7: TM RB1: N/A RB2- RB3: NoDiscard RB5- RB7: N/A RB1: N/A RB2- RB3: 25 RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: 200 RB5- RB7: N/A RB1: N/A RB2- RB3: 1 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1 RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB5- RB7: FALSE RB1: UM RB2- RB3: AM RB5- RB7: TM RB1: N/A RB2- RB3: TRUE RB5- RB7: N/A RB1: N/A RB2- RB3: 32 RB5- RB7: N/A RB1: N/A RB2- RB3: as below RB5- RB7: N/A RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A RB5- RB7: FALSE OneLogicalChannel Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3. RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A
3GPP TS 25.331 V6.23.0 (2009-09)
Ref 25.993 Default configuration identity RB INFORMATION Rb-Identity
>>transmissionRLC-DiscardMode
>>>maxDat
>>transmissionWindowSize
>>timerRST
>>max-RST
>>pollingInfo
>>>TimerPoll >>>PollPDU >>>PollSDU >>>lastTransmissionPDU-Poll >>>lastRetransmissionPDU-Poll >>>PollWindow >>segmentationIndication >dl-RLC-Mode
>>dl-RLC-StatusInfo
>>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication rb-MappingInfo >UL-LogicalChannelMappings >>ul-TransportChannelType >>>transportChannelIdentity
>>logicalChannelIdentity
3GPP
Release 6 >>rlc-SizeList >>mac-LogicalChannelPriority
1118 RB1- RB3: configured RB5: N/A RB1: 1, RB2: 2, RB3: 3 RB5: 5 One mapping option Dch RB1- RB3: 9 RB5: 1 RB1: 1, RB2: 2, RB3: 3 RB5: N/A RB1- RB3: configured RB5- RB7: N/A RB1: 1, RB2: 2, RB3: 3 RB5- RB7: 5 One mapping option Dch RB1- RB3: 9 RB5: 1, RB6: 2, RB7: 3, RB1: 1, RB2: 2, RB3: 3 RB5- RB7: N/A
3GPP TS 25.331 V6.23.0 (2009-09)
>DL-logicalChannelMappingList >>Mapping option 1 >>>dl-TransportChannelType >>>>transportChannelIdentity
>>>logicalChannelIdentity
TrCH INFORMATION PER TrCH UL-AddReconfTransChInfoList >Uplink transport channel type >transportChannelIdentity >transportFormatSet >>dynamicTF-information >>>tf0/ tf0,1,2,3,4
dch TrCH1: 1, TrCH2: 9 DedicatedTransChTF S TrCH1: (0x640, 2x640) TrCH2: (0x144, 1x144, 2x144, 3x144, 4x144) TrCH1: OctetMode TrCH2:BitMode TrCH1: type 2, part1= 11, part2= 2 (640) TrCH2: type 2, part1= 2, part2= 0 (144)
Dch TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9 DedicatedTransChTF S TrCH1: (0x72) TrCH2: (0x 181) TrCH3: (0x60) TrCH4: (0x144, 1x144, 2x144, 3x144, 4x144) BitMode TrCH1: type 1: 72 TrCH2: type 2: part1= 6, part2= 5 TrCH3: type1: 60 TrCH4: 2: type 2, part1= 2, part2= 0 (144) TrCH1-3: Zero TrCH4: Zero, one, 2, 3, 4 All TrCH1: (1x40) TrCH2: (1x 78) TrCH3: N/A TrCH4: N/A TrCH1: One TrCH2: One TrCH1-2: BitMode TrCH1: 1: 40 TrCH2: 1: 78 TrCH1-2: One TrCH1: all TrCH1: (1x54) TrCH2: (1x113) TrCH3: N/A TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 54 TrCH2: type 1: 113 TrCH1: One TrCH2: One TrCH1: all TrCH2: all
TrCH1: Zero, 2 TrCH2: Zero, one, 2, 3, 4 All
>>>>numberOfTransportBlocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 2
>>>>numberOfTransportBlocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList
3GPP
Release 6 >>>tf 3
1119 TrCH1: (1x64) TrCH2: (1x181) TrCH3: N/A TrCH4: N/A TrCH1: One TrCh2: One TrCH1: BitMode TrCH1: type 1: 64 TrCH2: type 2: part1=6, part2= 5 TrCH1: One TrCH2: One TrCH1: all TrCH2: all TrCH1: (1x72) TrCH2: N/A TrCH3: N/A TrCH4: N/A TrCH1: One TrCH1: BitMode TrCH1: type 1: 72 TrCH1: One TrCH1: all TrCH1: 20 TrCH2: 40 TrCH1: Turbo TrCH2: Convolutional TrCH1: N/A TrCH1- TrCH3: 20 TrCH4: 40 Convolutional TrCH1- TrCH3: Third TrCH4: Third TrCH1: 200 TrCH2: 190 TrCH3: 256 TrCH4: 170 TrCH1: 12 TrCH2: 0 TrCH3: 0 TrCH4: 16
3GPP TS 25.331 V6.23.0 (2009-09)
>>>>numberOfTransportBlocks >>>>rlc-Size >>>>>sizeType
>>>>numberOfTransportBlocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType >>>>codingRate
TrCH2: Third
TrCH1: 170 TrCH2: 160
>>>crc-Size
TrCH1: 16 TrCH2: 16
DL-AddReconfTransChInfoList >Downlink transport channel type >dl-TransportChannelIdentity >tfs-SignallingMode
dch TrCH1: 1, TrCH2: 9 SameAsUL
Dch Independent <Only tf0 on TrCH1 is different and shown below>
>>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>>semistaticTF-Information >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue
TrCH1: 1, TrCH2: 9
TrCH1: (1x0) BitMode TrCH1: type 1: 0 TrCH1: One All same as UL TrCH1: 1, TrCH2: 2, TrCH3: 3, TrCH4: 9, TrCH1: 7x10 TrCH2: Absent TrCH3: Absent TrCH4: Absent
-3
-3
TrCH INFORMATION, COMMON ul-CommonTransChInfo
3GPP
Release 6 >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFC list >>>>>>TFC 1 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 2 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 3 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 4 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>> c (FDD only) >>>>>>>> d 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0, TF0) 0 Computed 0 (TF1, TF0) 1 Computed N/A N/A 0 (TF0, TF1) 2 Computed 0 (TF1, TF1) 3 Signalled 8 15
1120 1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc6Bit Addition (TF0, TF0, TF0, TF0) 0 Computed 0 (TF1, TF0, TF0, TF0) 1 Computed N/A N/A 0 (TF2, TF1, TF0, TF0) 7 Computed 0 (TF3, TF2, TF0, TF0) 13 Computed N/A N/A
3GPP TS 25.331 V6.23.0 (2009-09)
3GPP
Release 6 >>>>>>>>referenceTFCId >>>>>>TFC 5 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 6 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 7 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 8 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 9 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 10 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId >>>>>>TFC 11 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 12 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 13 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 14 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId >>>>>>TFC 15 >>>>>>>ctfc >>>>>>>gainFactorInformation >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) > tfc-Subset PhyCH INFORMATION FDD UL-DPCH-InfoPredef >ul-DPCH-PowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DL-CommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor 0 (TF0, TF2) 4 Computed 0 (TF0, TF3) 6 Computed 0 (TF0, TF4) 8 Computed 0
1121 0 (TF4, TF3, TF0, TF0) 19 Computed 0 (TF0, TF0, TF0, TF1) 20 Computed 0 (TF1, TF0, TF0, TF1) 21 Computed 0 (TF2, TF1, TF0, TF1) 27 computed 0 (TF3, TF2, TF0, TF1) 33 computed 0 (TF4, TF3, TF0, TF1) 39 signalled 10 15 0 (TF0, TF0, TF0, TF2) 40 Computed 0 (TF1, TF0, TF0, TF2) 41 Computed 0 (TF0, TF0, TF0, TF3) 60 Computed 0 (TF1, TF0, TF0, TF3) 61 Computed 0 (TF0, TF0, TF0, TF4) 80 Computed 0 Same as UL 1 FALSE Absent, not required
3GPP TS 25.331 V6.23.0 (2009-09)
Same as UL
32
128
3GPP
Release 6 >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 Mcps TDD UL-DPCH-InfoPredef >ul-DPCH-PowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLength DL-CommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMode >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLength PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLength DL-CommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMode >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLength TRUE 8 Flexible
1122 TRUE 4 Flexible
3GPP TS 25.331 V6.23.0 (2009-09)
Configuration Ref 34.108 Default configuration identity RB INFORMATION rb-Identity 3 22
13.6 kbps signalling
RB1: 1, RB2: 2, RB3: 3 Rlc-info RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: NoDiscard RB1: N/A RB2- RB3: 25 RB1: N/A RB2- RB3: 32 RB1: N/A RB2- RB3: 200 RB1: N/A RB2- RB3: 1 RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: n/a RB2- RB3: 1
rlc-InfoChoice >ul-RLC-Mode >>transmissionRLCDiscardMode >>>maxDat >>transmissionWindowSiz e >>timerRST >>max-RST >>pollingInfo >>>TimerPoll >>>PollPDU >>>PollSDU
3GPP
Release 6 Configuration >>>lastTransmissionPDUPoll >>>lastRetransmissionPD U-Poll >>>PollWindow >>segmentationIndication >dl-RLC-Mode >>inSequenceDelivery >>receivingWindowSize >>dl-RLC-StatusInfo >>>timerStatusProhibit >>>missingPDU-Indicator >>segmentationIndication rb-MappingInfo >ULLogicalChannelMappings >>ulTransportChannelType >>>transportChannelIdentit y >>logicalChannelIdentity >>rlc-SizeList >>macLogicalChannelPriority >DLlogicalChannelMappingList >>Mapping option 1 >>>dlTransportChannelType >>>>transportChannelIden tity >>>logicalChannelIdentity TrCH INFORMATION PER TrCH ULAddReconfTransChInfoList >Uplink transport channel type >transportChannelIdentity >transportFormatSet >>dynamicTF-information >>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType 13.6 kbps signalling RB2- RB3: FALSE RB2- RB3: TRUE RB2- RB3: 99 RB1- RB3: N/A RB1: UM RB2- RB3: AM RB1: N/A RB2- RB3: TRUE RB1: N/A RB2- RB3: 32 RB1: N/A RB2- RB3: as below RB2- RB3: 100 RB2- RB3: TRUE RB1- RB3: N/A OneLogicalChannel Dch RB1- RB3:9 RB1: 1, RB2: 2, RB3: 3 RB1- RB3: configured RB1: 1, RB2: 2, RB3: 3
1123
3GPP TS 25.331 V6.23.0 (2009-09)
One mapping option Dch RB1- RB3: 9 RB1: 1, RB2: 2, RB3: 3
Dch TrCH1: 9 DedicatedTransChT FS TrCH1: (0x144, 1x144) BitMode TrCH1: type 2, part1= 2, part2= 0 (144) TrCH1: Zero, one All N/A
>>>>numberOfTbSizeList >>>>logicalChannelList >>>tf 1 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList
3GPP
Release 6 Configuration >>>tf 2 >>>>numberOfTransportBl ocks >>>>rlc-Size >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>semistaticTF-Information >>>tti >>>channelCodingType >>>>codingRate >>>rateMatchingAttribute >>>crc-Size DLAddReconfTransChInfoList >Downlink transport channel type >dlTransportChannelIdentity (should be as for UL) >tfs-SignallingMode >>transportFormatSet >>>dynamicTF-information >>>>tf0/ tf0,1 >>>>rlcSize >>>>>sizeType >>>>numberOfTbSizeList >>>>logicalChannelList >>ULTrCH-Id >dch-QualityTarget >>bler-QualityValue TrCH INFORMATION, COMMON ul-CommonTransChInfo >tfcs-ID (TDD only) >sharedChannelIndicator (TDD only) >tfc-Subset >ul-TFCS >>explicitTFCSConfigurationMode >>>ctfcSize >>>>TFCS representation >>>>>TFCS list >>>>>>TFCS 1 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>>referenceTFCId >>>>>>TFCS 2 >>>>>>>ctfc >>>>>>>gainFactorInform ation >>>>>>>> c (FDD only) >>>>>>>> d >>>>>>>>referenceTFCId dl-CommonTransChInfo >tfcs-SignallingMode PhyCH INFORMATION FDD UL-DPCH-InfoPredef N/A 13.6 kbps signalling
1124
3GPP TS 25.331 V6.23.0 (2009-09)
TrCH1: 10 Convolutional TrCH1: Third TrCH1: 160 TrCH1: 16
Dch TrCH1: 9
SameAsUL
TrCH1: 9 TrCH1: 1x10

-2
1 FALSE Absent, not required Normal TFCI signalling Complete Ctfc2Bit Addition (TF0) 0 Computed 0 (TF1) 1 Signalled 11 15 0 Same as UL
3GPP
Release 6 Configuration >ul-DPCHPowerControlInfo >>powerControlAlgorithm >>>tpcStepSize >tfci-Existence >puncturingLimit DLCommonInformationPredef >dl-DPCH-InfoCommon >>spreadingFactor >>tfci-Existence >>pilotBits >>positionFixed PhyCH INFORMATION 3.84 / 7.68 Mcps TDD UL-DPCH-InfoPredef >ul-DPCHPowerControlInfo >>dpch-ConstantValue >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth PhyCH INFORMATION 1.28 Mcps TDD UL-DPCH-InfoPredef >commonTimeslotInfo >>secondInterleavingMode >>tfci-Coding >>puncturingLimit >>repetitionPeriodAndLeng th DLCommonInformationPredef >dl-DPCH-InfoCommon >>commonTimeslotInfo >>>secondInterleavingMod e >>>tfci-Coding >>>puncturingLimit >>>repetitionPeriodAndLe ngth 13.6 kbps signalling
1125
3GPP TS 25.331 V6.23.0 (2009-09)
128 FALSE 4 N/A
NOTE:
The difference between default configuration #22 and default configuration #1 (13.6kbps signalling) resides in the RLC configuration and the DCH quality target.
3GPP
Release 6
1126
3GPP TS 25.331 V6.23.0 (2009-09)
14
14.1
14.1.1
Specific functions
Intra-frequency measurements
Intra-frequency measurement quantities
A measurement quantity is used to evaluate whether an intra-frequency event has occurred or not. It can be: 1 Downlink Ec/N0. 2 Downlink path loss. For FDD: Pathloss in dB = Primary CPICH Tx power - CPICH RSCP. For Primary CPICH Tx power the IE "Primary CPICH Tx power" shall be used. The unit is dBm. CPICH RSCP is the result of the CPICH RSCP measurement. The unit is dBm. For TDD: Pathloss in dB = Primary CCPCH TX power - Primary CCPCH RSCP. For Primary CCPCH TX power the IE "Primary CCPCH TX Power" shall be used. The unit is dBm. Primary CCPCH RSCP is the result of the Primary CCPCH RSCP measurement. The unit is dBm. If necessary Pathloss shall be rounded up to the next higher integer. Results higher than 158 shall be reported as 158. Results lower than 46 shall be reported as 46. 3 Downlink received signal code power (RSCP) after despreading. 4 ISCP measured on Timeslot basis. A description of those values can be found in [7] and [8].
14.1.2
Intra-frequency reporting events for FDD
Within the measurement reporting criteria field in the Measurement Control message the UTRAN notifies the UE which events should trigger a measurement report. The listed events are the toolbox from which the UTRAN can choose the reporting events that are needed for the implemented handover evaluation function, or other radio network functions. All the specified events are measured with respect to any of the measurement quantities given in subclause 14.1.1. The measurement quantities are measured on the monitored primary common pilot channels (CPICH) of the cell defined in the measurement object. Special mechanisms for the events are illustrated in subclause 14.1.4 and 14.1.5. NOTE: The events below are numbered 1A, 1B, 1C, since all intra-frequency reporting events would be labelled 1X, inter-frequency reporting events would be labelled 2X, and so on for the other measurement types.
When one intra-frequency measurement identity corresponds to multiple intra-frequency events with identical event identities, the UE behaviour is not specified.
14.1.2.1
Reporting event 1A: A Primary CPICH enters the reporting range
When an intra-frequency measurement configuring event 1a is set up, the UE shall:
3GPP
Release 6
1127
3GPP TS 25.331 V6.23.0 (2009-09)
1> create a variable TRIGGERED_1A_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1A is configured in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell; and 2> if the equations have been fulfilled for a time period indicated by "Time to trigger", and if that primary CPICH is part of cells allowed to trigger the event according to "Triggering condition 2", and if that primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1A_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1A_EVENT. 1> if the value of "Reporting deactivations threshold" for this event is greater than or equal to the current number of cells in the active set or equal to 0 and any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1A_EVENT: 2> if "Reporting interval" for this event is not equal to 0: 3> if the IE "Periodical reporting running" in the variable TRIGGERED_1A_EVENT is set to FALSE: 4> start a timer with the value of "Reporting interval" for this event and set the IE "Periodical reporting running" in the variable TRIGGERED_1A_EVENT to TRUE; 3> set "sent reports" for the primary CPICHs in "cells recently triggered" in the variable TRIGGERED_1A_EVENT to 1. 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1a"; and 3> include in "cell measurement event results" all entries of the "cells recently triggered" in the variable TRIGGERED_1A_EVENT in descending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 2> move all entries from "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1A_EVENT. 1> if the timer for the periodical reporting has expired: 2> if any primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1A_EVENT: 3> if "Reporting interval" for this event is not equal to 0, and if "Amount of reporting" is greater than "sent reports" stored for any of these primary CPICHs, in "cells triggered" in the variable TRIGGERED_1A_EVENT: 4> increment the stored counter "sent reports" for all CPICHs in "cell triggered" in variable TRIGGERED_1A_EVENT; 4> start a timer with the value of "Reporting interval" for this event; 4> send a measurement report with IEs set as below: 5> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1a"; and 5> include in "cell measurement event results" all entries of the variable TRIGGERED_1A_EVENT with value of IE "sent reports" equal to or smaller than value of "Amount of reporting" in descending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells;
3GPP
Release 6
1128
3GPP TS 25.331 V6.23.0 (2009-09)
5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 4> if "sent reports" in variable TRIGGERED_1A_EVENT is equal to "Amount of reporting" for all entries: 5> set the IE "Periodical Reporting running" in the variable TRIGGERED_1A_EVENT to FALSE and disable the timer for the periodical reporting. 1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH; or 1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the "Triggering condition 2": 2> if that primary CPICH is included in the "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1A_EVENT: 3> remove the entry of that primary CPICH from "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1A_EVENT. 3> if no entry in the variable TRIGGERED_1A_EVENT has a value of "sent reports" smaller than "Amount of reporting"; or 3> if there is no entry in the variable TRIGGERED_1A_EVENT: 4> if the reporting interval timer is running: 5> stop the reporting interval timer; 5> set the IE "Periodical reporting running" in the variable TRIGGERED_1A_EVENT to FALSE. This event is only applicable to the CELL_DCH state. When the measurement is setup in CELL_DCH or upon transition to CELL_DCH the UE shall: 1> if the "Triggering condition 2" includes active set cells: 2> include the primary CPICH of all cells in the current active set into the "cells triggered" in the variable TRIGGERED_1A_EVENT with the counter "sent reports" set to "Amount of reporting". Equation 1 (Triggering condition for pathloss)
NA 10 LogM New + CIONew W 10 Log 1 / (1 / M i ) + (1 W ) 10 LogM Best + ( R1a H1a / 2), i =1
Equation 2 (Triggering condition for all the other measurement quantities)

NA 10 LogM New + CIONew W 10 Log M i + (1 W ) 10 LogM Best ( R1a H1a / 2), i =1
Equation 3 (Leaving triggering condition for pathloss)

NA 10 LogM New + CIONew > W 10 Log 1 / (1 / M i ) + (1 W ) 10 LogM Best + ( R1a + H1a / 2), i =1
Equation 4 (Leaving triggering condition for all the other measurement quantities)
NA 10 LogM New + CIONew < W 10 Log M i + (1 W ) 10 LogM Best ( R1a + H1a / 2), i =1
The variables in the formula are defined as follows: MNew is the measurement result of the cell entering the reporting range.
3GPP
Release 6
1129
3GPP TS 25.331 V6.23.0 (2009-09)
CIONew is the individual cell offset for the cell entering the reporting range if an individual cell offset is stored for that cell. Otherwise it is equal to 0. Mi is a measurement result of a cell not forbidden to affect reporting range in the active set. NA is the number of cells not forbidden to affect reporting range in the current active set. For pathloss MBest is the measurement result of the cell not forbidden to affect reporting range in the active set with the lowest measurement result, not taking into account any cell individual offset. for other measurements quantities. MBest is the measurement result of the cell not forbidden to affect reporting range in the active set with the highest measurement result, not taking into account any cell individual offset. W is a parameter sent from UTRAN to UE. R1a is the reporting range constant. H1a is the hysteresis parameter for the event 1a. If the measurement results are pathloss or CPICH-Ec/No then MNew, Mi and MBest are expressed as ratios. If the measurement result is CPICH-RSCP then MNew, Mi and MBest are expressed in mW.
14.1.2.2
Reporting event 1B: A primary CPICH leaves the reporting range
When an intra-frequency measurement configuring event 1b is set up, the UE shall: 1> create a variable TRIGGERED_1B_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1B is configures in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell, and if the equations have been fulfilled for a time period indicated by "Time to trigger", and if that primary CPICH is part of cells allowed to trigger the event according to "Triggering condition 1", and if that primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1B_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1B_EVENT. 1> if any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1B_EVENT: 2> if "Periodic reporting info-1b" is present, and "Reporting interval" for this event is not equal to 0: 3> if the IE "Periodical reporting running" in the variable TRIGGERED_1B_EVENT is set to FALSE: 4> start a timer with the value of "Reporting interval" for this event and set the IE "Periodical reporting running" in the variable TRIGGERED_1B_EVENT to TRUE; 3> set "sent reports" for the primary CPICHs in "cells recently triggered" in the variable TRIGGERED_1B_EVENT to 1. 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1b"; and 3> include in "cell measurement event results" all entries of "cells recently triggered" in the variable TRIGGERED_1B_EVENT in ascending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells;
3GPP
Release 6
1130
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 2> move all entries from IE "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1B_EVENT. 1> if the timer for the periodical reporting has expired: 2> if any primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1B_EVENT: 3> if "Periodic reporting info-1b" is present: 4> if "Reporting interval" is not equal to 0, and if "Amount of reporting" is greater than "sent reports" stored for any of these primary CPICHs, in "cells triggered" in the variable TRIGGERED_1B_EVENT: 5> increment the stored counter "sent reports" for all CPICHs in "cell triggered" in variable TRIGGERED_1B_EVENT; 5> start a timer with the value of "Reporting interval-1b" for this event; 5> send a measurement report with IEs set as below: 6> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1b"; and 6> include in "cell measurement event results" all entries of the variable TRIGGERED_1B_EVENT with value of IE "sent reports" equal to or smaller than value of "Amount of reporting" in ascending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells; 6> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 5> if "sent reports" in variable TRIGGERED_1B_EVENT is equal to "Amount of reporting" for all entries: 6> set the IE "Periodical Reporting running" in the variable TRIGGERED_1B_EVENT to FALSE and disable the timer for the periodical reporting. 1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH; or 1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the "Triggering condition 1": 2> if that primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1B_EVENT: 3> remove the entry of that primary CPICH from "cells triggered" in the variable TRIGGERED_1B_EVENT; 3> if there is no entry in the variable TRIGGERED_1B_EVENT: 4> if the reporting interval timer is running: 5> stop the reporting interval timer; 5> set the IE "Periodical reporting running" in the variable TRIGGERED_1B_EVENT to FALSE. Equation 1 (Triggering condition for pathloss)
NA 10 LogM Old + CIOOld W 10 Log 1 / (1 / M i ) + (1 W ) 10 LogM Best + ( R1b + H 1b / 2), Equation 2 (Triggering condition i =1
for all the other measurement quantities)
3GPP
Release 6
1131
3GPP TS 25.331 V6.23.0 (2009-09)
NA 10 LogM Old + CIOOld W 10 Log M i + (1 W ) 10 LogM Best ( R1b + H 1b / 2), Equation 3 (Leaving triggering i =1
condition for pathloss)

NA 10 LogM Old + CIOOld < W 10 Log 1 / (1 / M i ) + (1 W ) 10 LogM Best + ( R1b H 1b / 2), Equation 4 (Leaving triggering i =1
condition for all the other measurement quantities)

NA 10 LogM Old + CIOOld > W 10 Log M i + (1 W ) 10 LogM Best ( R1b H 1b / 2), The variables in the formula are i =1
defined as follows: MOld is the measurement result of the cell leaving the reporting range. CIOOld is the individual cell offset for the cell leaving the reporting range if an individual cell offset is stored for that cell. Otherwise it is equal to 0. Mi is a measurement result of a cell not forbidden to affect reporting range in the active set. NA is the number of cells not forbidden to affect reporting range in the current active set. For pathloss MBest is the measurement result of the cell not forbidden to affect reporting range in the active set with the lowest measurement result, not taking into account any cell individual offset. for other measurements quantities. MBest is the measurement result of the cell not forbidden to affect reporting range in the active set with the highest measurement result, not taking into account any cell individual offset. W is a parameter sent from UTRAN to UE. R1b is the reporting range constant. H1b is the hysteresis parameter for the event 1b. If the measurement results are pathloss or CPICH-Ec/No then MOld, Mi and MBest are expressed as ratios. If the measurement result is CPICH-RSCP then MOld, Mi and MBest are expressed in mW.
14.1.2.3
Reporting event 1C: A non-active primary CPICH becomes better than an active primary CPICH
When an intra-frequency measurement configuring event 1c is set up, the UE shall: 1> create a variable TRIGGERED_1C_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1C is configured in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell; and 2> if the equations have been fulfilled for a time period indicated by "Time to trigger", and if the primary CPICH that is better is not included in the active set but the other primary CPICH is any of the primary CPICHs included in the active set, and if that first primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1C_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1C_EVENT.
3GPP
Release 6
1132
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the value of "Replacement activation threshold" for this event is less than or equal to the current number of cells in the active set or equal to 0 and if any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1C_EVENT: 2> if "Reporting interval" for this event is not equal to 0: 3> if the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT is set to FALSE: 4> start a timer for with the value of "Reporting interval" for this event and set the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT to TRUE. 3> set "sent reports" for that primary CPICH in the variable TRIGGERED_1C_EVENT to 1. 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1c"; and 3> include in "cell measurement event results" all entries of the "cells recently triggered" in the variable TRIGGERED_1C_EVENT not in the active set as well as the "primary CPICH info" of all the primary CPICHs in the active set for which the measured value is worse (i.e. greater for pathloss and less for the other measurement quantities) than the one of the entry in "cell recently triggered" that has the best measured value taking into account their cell individual offset. The "primary CPICH info" for those cells shall be ordered according to their measured value taking into account their cell individual offset, beginning with the best cell to the worst one; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 2> move all entries from "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1C_EVENT. 1> if the timer for the periodical reporting has expired: 2> if any primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1C_EVENT, and not included in the current active set: 3> if "Reporting interval" for this event is not equal to 0, and if "Amount of reporting" is greater than "sent reports" stored for that primary CPICH, in "cells triggered" in the variable TRIGGERED_1C_EVENT: 4> increment the stored counter "sent reports" for all CPICH in "cell triggered" in variable TRIGGERED_1C_EVENT; 4> start a timer with the value of "Reporting interval" for this event; 4> send a measurement report with IEs set as below: 5> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1c"; and 5> include in "cell measurement event results" all entries of the variable TRIGGERED_1C_EVENT with value of IE "sent report" equal to or smaller than value of "Amount of reporting" and that are not part of the active set as well as the "primary CPICH info" of all the primary CPICHs in the active set for which the measured value is worse (i.e. greater for pathloss and less for the other measurement quantities) than the one of the entry in "cell triggered" that has the best measured value, ordering the "primary CPICH info" according to their measured value beginning with the best cell to the worst one, taking into account the cell individual offset for each cell; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 4> if "sent reports" in variable TRIGGERED_1C_EVENT is equal to "Amount of reporting" for all entries: 5> set the IE "Periodical Reporting running" in the variable TRIGGERED_1C_EVENT to FALSE and disable the timer for the periodical reporting.
3GPP
Release 6
1133
3GPP TS 25.331 V6.23.0 (2009-09)
1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH or; 1> if a primary CPICH is added to the active set: 2> if that primary CPICH is included in the "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1C_EVENT: 3> remove the entry of that primary CPICH from "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1C_EVENT. 3> if no entry in the variable TRIGGERED_1C_EVENT has a value of "sent reports" smaller than "Amount of reporting" or 3> if there is no entry in the variable TRIGGERED_1C_EVENT: 4> if the reporting interval timer is running: 5> stop the reporting interval timer; 5> set the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT to FALSE. Equation 1 (Triggering condition for pathloss)
10 LogM +CIO 10 LogM +CIO H1c / 2, New New InAS InAS

10 LogM +CIO 10 LogM +CIO + H1c / 2, New New InAS InAS

10 LogM +CIO >10 LogM +CIO + H1c / 2, New New InAS InAS
10 LogM +CIO <10 LogM +CIO H1c / 2, New New InAS InAS
The variables in the formula are defined as follows: MNew is the measurement result of the cell not included in the active set. CIONew is the individual cell offset for the cell becoming better than the cell in the active set if an individual cell offset is stored for that cell. Otherwise it is equal to 0. For pathloss: MInAS is the measurement result of the cell in the active set with the highest measurement result. For other measurement quantities: MInAS is the measurement result of the cell in the active set with the lowest measurement result. CIOInAS is the individual cell offset for the cell in the active set that is becoming worse than the new cell. H1c is the hysteresis parameter for the event 1c. If the measurement results are pathloss or CPICH-Ec/No then MNew and MinAS are expressed as ratios. If the measurement result is CPICH-RSCP then MNew and MinAS are expressed in mW.
3GPP
Release 6
1134
3GPP TS 25.331 V6.23.0 (2009-09)
Measurement quantity P CPICH 1
P CPICH 2
P CPICH 3 P CPICH 4
Reporting event 1C Reporting event 1C
Time
Figure 14.1.2.3-1 [Informative]: A primary CPICH that is not included in the active set becomes better than a primary CPICH that is in the active set In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all cells are equal to 0. In this example the cells belonging to primary CPICH 1 and 2 are in the active set, but the cells transmitting primary CPICH 3 and CPICH 4 are not (yet) in the active set. The first measurement report is sent when primary CPICH 4 becomes better than primary CPICH 2. The "cell measurement event result" of the measurement report contains the information of primary CPICH 4 and CPICH 2. Assuming that the active set has been updated after the first measurement report (active set is now primary CPICH 1 and primary CPICH 4), the second report is sent when primary CPICH 3 becomes better than primary CPICH 1. The "cell measurement event result" of the second measurement report contains the information of primary CPICH 3 and primary CPICH 1.
14.1.2.4
Reporting event 1D: Change of best cell
When an intra-frequency measurement configuring event 1d is set up, the UE shall: 1> create a variable TRIGGERED_1D_EVENT related to that measurement, which shall initially contain the best cell in the active set when the measurement is initiated; 1> delete this variable when the measurement is released. 1> As soon as the best cell in the active set has been evaluated by the UE (and stored in the TRIGGERED_1D_EVENT variable) and provided that there is more than one cell in the active set, trigger an immediate measurement report with IEs set as below: 2> set in "intra-frequency measurement event results"; "Intrafrequency event identity" to "1d" and "cell measurement event results" to the CPICH info of the primary CPICH stored in the TRIGGERED_1D_EVENT variable; 2> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2 When event 1D is configured in the UE, the UE shall: 1> if IE "useCIO" is present and its value is TRUE, take into account the Cell Individual Offset for evaluation of the Equation 1 and 2, otherwise do not take it into account. 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for a primary CPICH that is not stored in "Best cell" in variable BEST_CELL_1D_EVENT, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for a primary CPICH that is not stored in "Best cell" in variable BEST_CELL_1D_EVENT: NOTE: If the equations are simultaneously fulfilled for more than one primary CPICH, the UE should report only one event 1D, triggered by the best primary CPICH.
3GPP
Release 6
1135
3GPP TS 25.331 V6.23.0 (2009-09)
2> if all required reporting quantities are available for that cell, and if the equations have been fulfilled for a time period indicated by "Time to trigger" and if IE "Triggering condition 2" is absent or if it is present and that primary CPICH is part of cells allowed to trigger the event according to "Triggering condition 2": 3> set "best cell" in the variable BEST_CELL_1D_EVENT to that primary CPICH that triggered the event; 3> send a measurement report with IEs set as below: 4> set in "intra-frequency measurement event results"; "Intrafrequency event identity" to "1d" and "cell measurement event results" to the CPICH info of the primary CPICH that triggered the report. 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2. This event is only applicable to the CELL_DCH state. Upon transition to CELL_DCH the UE shall: 1> set "best cell" in the variable BEST_CELL_1D_EVENT to the best cell of the primary CPICHs included in the active set. Equation 1 (Triggering condition for pathloss)
10 LogM +CIO 10 LogM +CIO H1d / 2, NotBest NotBest Best Best

10 LogM +CIO 10 LogM +CIO +H1d / 2, NotBest NotBest Best Best

The variables in the formula are defined as follows: MNotBest is the measurement result of a cell not stored in "best cell" in the variable BEST_CELL_1D_EVENT. CIONotBest is the cell individual offset of a cell not stored in "best cell" in the variable BEST_CELL_1D_EVENT. MBest is the measurement result of the cell stored in "best cell" in variable BEST_CELL_1D_EVENT. CIOBest is the cell individual offset of a cell stored in "best cell" in the variable BEST_CELL_1D_EVENT. H1d is the hysteresis parameter for the event 1d. If the measurement results are pathloss or CPICH-Ec/No then MNot Best and MBest are expressed as ratios. If the measurement result is CPICH-RSCP then MNot Best and MBest are expressed in mW.
P CPICH 2
P CPICH3
Reporting event 1D
Time
Figure 14.1.2.4-1 [Informative]: A primary CPICH becomes better than the previously best primary CPICH In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all cells are equal to 0.
3GPP
Release 6
1136
3GPP TS 25.331 V6.23.0 (2009-09)
14.1.2.5
Reporting event 1E: A Primary CPICH becomes better than an absolute threshold
When an intra-frequency measurement configuring event 1e is set up, the UE shall: 1> create a variable TRIGGERED_1E_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1E is configured in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell, and if the equations have been fulfilled for a time period indicated by "Time to trigger", and if that primary CPICH is part of cells allowed to trigger the event according to "Triggering condition 2", and that primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1E_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1E_EVENT. 1> if any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1E_EVENT: 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1e"; and 3> include in "cell measurement event results" all entries of the "cells recently triggered" in the variable TRIGGERED_1E_EVENT in descending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 2> move all entries from "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1E_EVENT. 1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH; or 1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the "Triggering condition 2": 2> if that primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1E_EVENT: 3> remove that primary CPICH and sent reports from "cells triggered" in the variable TRIGGERED_1E_EVENT. This event is only applicable to the CELL_DCH state. When the measurement is setup in CELL_DCH or upon transition to CELL_DCH the UE shall: 1> if the "Triggering condition 2" includes active set cells: 2> include the primary CPICH of all cells in the current active set that fulfil the equations 1 or 2 according to the "Measurement quantity" of event 1e into the "cells triggered" in the variable TRIGGERED_1E_EVENT. Equation 1 (Triggering condition for pathloss)
10 LogM +CIO Te H1e / 2, New New 1

10 LogM +CIO Te + H1e / 2, New New 1
3GPP
Release 6
1137
3GPP TS 25.331 V6.23.0 (2009-09)
10 LogM +CIO >Te + H1e / 2, New New 1

10 LogM +CIO <Te H1e / 2, New New 1

The variables in the formula are defined as follows: MNew is the measurement result of a cell that becomes better than an absolute threshold. CIONew is the individual cell offset for the cell becoming better than the absolute threshold. Otherwise it is equal to 0. T1e is an absolute threshold. H1e is the hysteresis parameter for the event 1e. If the measurement results are pathloss or CPICH-Ec/No then MNew is expressed as ratios. If the measurement result is CPICH-RSCP then MNew is expressed in mW.
P CPICH 2 Absolute threshold
P CPICH 3
Reporting event 1E
Time
Figure 14.1.2.5-1 [Informative]: Event-triggered report when a Primary CPICH becomes better than an absolute threshold In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all cells are equal to 0.
14.1.2.6
Reporting event 1F: A Primary CPICH becomes worse than an absolute threshold
When an intra-frequency measurement configuring event 1F is set up, the UE shall: 1> create a variable TRIGGERED_1F_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1F is configured in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell, and if the equations have been fulfilled for a time period indicated by "Time to trigger", and if that primary CPICH is part of cells allowed to trigger the event
3GPP
Release 6
1138
3GPP TS 25.331 V6.23.0 (2009-09)
according to "Triggering condition 1", and that primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1F_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1F_EVENT. 1> if any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1F_EVENT: 2> send a measurement report with IEs set as below: 3> set in "intra-frequency event measurement results": "Intrafrequency event identity" to "1f"; and 3> include in "cell measurement event results" all entries of the "cells recently triggered" in the variable TRIGGERED_1F_EVENT in descending order according to the configured measurement quantity taking into account the cell individual offset for each of those cells; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell; 2> move all entries from "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1F_EVENT. 1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH; or 1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the "Triggering condition 1": 2> if that primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1F_EVENT: 3> remove that primary CPICH from "cells triggered" in the variable TRIGGERED_1F_EVENT.
Equation 1 (Triggering condition for pathloss)
10 LogM +CIO T f + H1f / 2, Old Old 1

10 LogM +CIO T f H1f / 2, Old Old 1

10 LogM +CIO <T f H1f / 2, Old Old 1

10 LogM +CIO >T f + H1f / 2, Old Old 1

The variables in the formula are defined as follows: MOld is the measurement result of a cell that becomes worse than an absolute threshold CIOOld is the individual cell offset for the cell becoming worse than the absolute threshold. Otherwise it is equal to 0. T1f is an absolute threshold H1f is the hysteresis parameter for the event 1f. If the measurement results are pathloss or CPICH-Ec/No then MOld is expressed as ratios. If the measurement result is CPICH-RSCP then MOld is expressed in mW.
3GPP
Release 6
1139
3GPP TS 25.331 V6.23.0 (2009-09)
P CPICH 2 Absolute threshold P CPICH 3
Reporting event 1F
Time
Figure 14.1.2.6-1 [Informative]: Event-triggered report when a Primary CPICH becomes worse than an absolute threshold In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all cells are equal to 0.
14.1.2.7
Reporting event 1J: A non-active E-DCH but active DCH primary CPICH becomes better than an active E-DCH primary CPICH
When an intra-frequency measurement configuring event 1j is set up, the UE shall: 1> create a variable TRIGGERED_1J_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 1J is configured in the UE, the UE shall: 1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primary CPICHs: 2> if all required reporting quantities are available for that cell; and 2> if the equations have been fulfilled for a time period indicated by "Time to trigger", and if the primary CPICH that is better is not included in the E-DCH active set but included in DCH active set and the other primary CPICH is any of the primary CPICHs included in the E-DCH active set, and if that first primary CPICH is not included in the "cells triggered" in the variable TRIGGERED_1J_EVENT: 3> include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1J_EVENT. 1> if the value of "Replacement activation threshold" for this event is less than or equal to the current number of cells in the E-DCH active set or equal to 0 and if any primary CPICHs are stored in the "cells recently triggered" in the variable TRIGGERED_1J_EVENT: 2> if "Reporting interval" for this event is not equal to 0: 3> if the IE "Periodical reporting running" in the variable TRIGGERED_1J_EVENT is set to FALSE: 4> start a timer for with the value of "Reporting interval" for this event and set the IE "Periodical reporting running" in the variable TRIGGERED_1J_EVENT to TRUE. 3> set "sent reports" for that primary CPICH in the variable TRIGGERED_1J_EVENT to 1. 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1J"; and
3GPP
Release 6
1140
3GPP TS 25.331 V6.23.0 (2009-09)
3> include in "cell measurement event results" all entries of the "cells recently triggered" in the variable TRIGGERED_1J_EVENT not in the E-DCH active set but included in DCH active set as well as the "primary CPICH info" of all the primary CPICHs in the E-DCH active set for which the measured value is worse (i.e. greater for pathloss and less for the other measurement quantities) than the one of the entry in "cell recently triggered" that has the best measured value taking into account their cell individual offset. The "primary CPICH info" for those cells shall be ordered according to their measured value taking into account their cell individual offset, beginning with the best cell to the worst one; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 2> move all entries from "cells recently triggered" to "cells triggered" in the variable TRIGGERED_1J_EVENT. 1> if the timer for the periodical reporting has expired: 2> if any primary CPICH is included in the "cells triggered" in the variable TRIGGERED_1J_EVENT, and not included in the current E-DCH active set but included in DCH active set: 3> if "Reporting interval" for this event is not equal to 0, and if "Amount of reporting" is greater than "sent reports" stored for that primary CPICH, in "cells triggered" in the variable TRIGGERED_1J_EVENT: 4> increment the stored counter "sent reports" for all CPICH in "cell triggered" in variable TRIGGERED_1J_EVENT; 4> start a timer with the value of "Reporting interval" for this event; 4> send a measurement report with IEs set as below: 5> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1J"; and 5> include in "cell measurement event results" all entries of the variable TRIGGERED_1J_EVENT with value of IE "sent report" equal to or smaller than value of "Amount of reporting" and that are not part of the E-DCH active set but included in DCH active set as well as the "primary CPICH info" of all the primary CPICHs in the E-DCH active set for which the measured value is worse (i.e. greater for pathloss and less for the other measurement quantities) than the one of the entry in "cell triggered" that has the best measured value, ordering the "primary CPICH info" according to their measured value beginning with the best cell to the worst one, taking into account the cell individual offset for each cell; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 4> if "sent reports" in variable TRIGGERED_1J_EVENT is equal to "Amount of reporting" for all entries: 5> set the IE "Periodical Reporting running" in the variable TRIGGERED_1J_EVENT to FALSE and disable the timer for the periodical reporting. 1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is fulfilled for a primary CPICH or; 1> if a primary CPICH is added to the E-DCH active set: 2> if that primary CPICH is included in the "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1J_EVENT: 3> remove the entry of that primary CPICH from "cells triggered" or "cells recently triggered" in the variable TRIGGERED_1J_EVENT. 3> if no entry in the variable TRIGGERED_1J_EVENT has a value of "sent reports" smaller than "Amount of reporting" or 3> if there is no entry in the variable TRIGGERED_1J_EVENT: 4> if the reporting interval timer is running:
3GPP
Release 6
1141
3GPP TS 25.331 V6.23.0 (2009-09)
5> stop the reporting interval timer; 5> set the IE "Periodical reporting running" in the variable TRIGGERED_1J_EVENT to FALSE. Equation 1 (Triggering condition for pathloss)
10 LogM +CIO 10 LogM +CIO H1j / 2, New New InAS InAS

10 LogM +CIO 10 LogM +CIO +H1j / 2, New New InAS InAS

10 LogM +CIO >10 LogM +CIO +H1j / 2, New New InAS InAS
10 LogM +CIO <10 LogM +CIO H1j / 2, New New InAS InAS
The variables in the formula are defined as follows: MNew is the measurement result of the cell not included in the E-DCH active set but included in DCH active set. CIONew is the individual cell offset for the cell not included in the E-DCH active set but included in DCH active set becoming better than the cell in the E-DCH active set if an individual cell offset is stored for that cell. Otherwise it is equal to 0. For pathloss: MInAS is the measurement result of the cell in the E-DCH active set with the highest measurement result. For other measurement quantities: MInAS is the measurement result of the cell in the E-DCH active set with the lowest measurement result. CIOInAS is the individual cell offset for the cell in the E-DCH active set that is becoming worse than the new cell. H1J is the hysteresis parameter for the event 1J. If the measurement results are pathloss or CPICH-Ec/No then MNew and MinAS are expressed as ratios. If the measurement result is CPICH-RSCP then MNew and MinAS are expressed in mW.
P CPICH 2
P CPICH 3 P CPICH 4
Reporting event 1J Reporting event 1J
Time
Figure 14.1.2.7-1 [Informative]: A primary CPICH that is not included in the E-DCH active set but included in DCH active set becomes better than a primary CPICH that is in the E-DCH active set
3GPP
Release 6
1142
3GPP TS 25.331 V6.23.0 (2009-09)
In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all cells are equal to 0 and replacement activation threshold is equal to 0 or 1 or 2. In this example the cells belonging to primary CPICH 1 and 2 are in the E-DCH active set, but the cells transmitting primary CPICH 3 and CPICH 4 are not (yet) in the E-DCH active set but included in DCH active set. The first measurement report is sent when primary CPICH 4 becomes better than primary CPICH 2. The "cell measurement event result" of the measurement report contains the information of primary CPICH 4 and CPICH 2. Assuming that the E-DCH active set has been updated after the first measurement report (E-DCH active set is now primary CPICH 1 and primary CPICH 4), the second report is sent when primary CPICH 3 becomes better than primary CPICH 1. The "cell measurement event result" of the second measurement report contains the information of primary CPICH 3 and primary CPICH 1.
14.1.3
14.1.3.1
Intra-frequency reporting events for TDD

Reporting event 1G: Change of best cell (TDD)
When event 1G is configured in the UE, the UE shall: 1> if the equation 1 is fulfilled for a P-CCPCHs during the time "Time to trigger" and if that P-CCPCH is not included in the "primary CCPCH info" in the variable TRIGGERED_1G_EVENT: 2> include that P-CCPCH in "cells triggered" in the variable TRIGGERED_1G_EVENT; 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1g"; 3> set the first entry in "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH which was stored in the variable TRIGGERED_1G_EVENT; 3> include all entries in "cells triggered" in variable TRIGGERED_1G_EVENT in "cell measurement event results" in the measurement report in descending order according to:
10 LogM + O
where M is the P-CCPCH RSCP and O the individual offset of a cell; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 1> if Equation 2 below is fulfilled for a primary CCPCH: 2> if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1G_EVENT: 3> remove the entry of that primary CCPCH from "cells triggered" in the variable TRIGGERED_1G_EVENT; The UE shall use the equations below for evaluation of reporting event 1g: Equation 1
10 LogM + Oi H1g > 10 LogM _ best + Oprevious best, previous _ i

The variables in the formula are defined as follows: Mprevious_best is the current P-CCPCH RSCP of the previous best cell expressed in mW Oprevious_best is the cell individual offset of the previous best cell Mi is the current P-CCPCH RSCP of the currently evaluated cell i expressed in mW Oi is the cell individual offset of the currently evaluated cell i H1g is the hysteresis parameter for the event 1g.
3GPP
Release 6
1143
3GPP TS 25.331 V6.23.0 (2009-09)
Equation 2
10 LogM + Oi + H1g < 10 LogM _ best + Oprevious best, previous _ i

The variables in the formula are defined as follows: Mprevious_best is the current P-CCPCH RSCP of the previous best cell expressed in mW Oprevious_best is the cell individual offset of the previous best cell Mi is the current P-CCPCH RSCP of the currently evaluated cell i expressed in mW Oi is the cell individual offset of the currently evaluated cell i H1g is the hysteresis parameter for the event 1g.
Measurement quantity P-CCPCH RSCP 1
P-CCPCH RSCP 2
Reporting Event 1G
Time
Figure 14.1.3.1-1: A P-CCPCH RSCP becomes better than the previous best P-CCPCH RSCP
14.1.3.2
Reporting event 1H: Timeslot ISCP below a certain threshold (TDD)
When event 1h is configured in the UE, the UE shall: 1> if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH is not included in the IE "cells triggered" in the variable TRIGGERED_1H_EVENT: 2> include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1H_EVENT; 2> send a measurement report with the IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1h" and in "cell measurement event results" the "Cell parameters ID" of the P-CCPCH that triggered the report; 3> include in "Cell measured results" the "Timeslot ISCP" of those cells that are included in the variable TRIGGERED_1H_EVENT. 1> if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1H_EVENT: 2> send a measurement report with IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1h" and "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH that triggered the report; 3> set in "measured results " the "Timeslot ISCP" of those cells that are included in the variable TRIGGERED_1H_EVENT and "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset for each cell. 1> if Equation 2 below is fulfilled for a primary CCPCH:
3GPP
Release 6
1144
3GPP TS 25.331 V6.23.0 (2009-09)
2> if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1H_EVENT: 3> remove the entry of that primary CCPCH from "cells triggered" in the variable TRIGGERED_1H_EVENT. The UE shall use the equations below for evaluation of reporting event 1h: Equation 1
10 LogM i + H 1h + Oi < T1h ,
Equation 2
10 LogM i H 1h + Oi > T1h ,
The variables in the formula are defined as follows: Mi is the Timeslot ISCP of the currently evaluated cell i expressed in mW Oi is the cell individual offset of the currently evaluated cell i T1h is the Threshold for event 1h H1h is the hysteresis parameter for the event 1h. Before any evaluation is done, the Timeslot ISCP expressed in mW is filtered according to subclause 8.6.7.2.
Timeslot ISCP
ISCP Threshold TS 1
Reporting Event 1H
Time
Figure 14.1.3.2-1: An ISCP value of a timeslot drops below an absolute threshold
14.1.3.3
Reporting event 1I: Timeslot ISCP above a certain threshold (TDD)
When event 1i is configured in the UE, the UE shall: 1> if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH is not included in the IE "cells triggered" in the variable TRIGGERED_1I_EVENT: 2> include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1I_EVENT; 2> send a measurement report with the IEs set as below: 3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1i" and in "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH that triggered the report; 3> include in "measured results" the "Timeslot ISCP" of those cells that are included in the variable TRIGGERED_1I_EVENT and "additional measured results" according to 8.4.2, not taking into account the cell individual offset for each cell.
3GPP
Release 6
1145
3GPP TS 25.331 V6.23.0 (2009-09)
1> if Equation 2 below is fulfilled for a primary CCPCH: 2> if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1I_EVENT: 3> remove the entry of that primary CCPCH from "cells triggered" in the variable TRIGGERED_1I_EVENT. The UE shall use the equation below for evaluation of reporting event 1i: Equation 1
10 LogM i H 1i + Oi > T1i ,
Equation 2
10 LogM i H 1i + Oi < T1i ,
The variables in the formula are defined as follows: Mi is the Timeslot ISCP of the currently evaluated cell i expressed in mW Oi is the cell individual offset of the currently evaluated cell i T1i is the Threshold for event 1i H1i is the hysteresis parameter for the event 1i. Before any evaluation is done, the Timeslot ISCP expressed in mW is filtered according to subclause 8.6.7.2.
Timeslot ISCP
TS 1
ISCP Threshold
Reporting Event 1I
Time
Figure 14.1.3.3-1: An ISCP value of a timeslot exceeds a certain threshold
3GPP
Release 6
1146
3GPP TS 25.331 V6.23.0 (2009-09)
14.1.4
14.1.4.1
Event-triggered periodic intra-frequency measurement reports (informative)

Cell addition failure (FDD only)
Reporting range
PCPICH 1
PCPICH 2
Reporting terminated Periodic report Event-triggered report Periodic report PCPICH 3
Figure 14.1.4.1-1: Periodic reporting triggered by event 1A When a cell enters the reporting range and triggers event 1A, the UE shall transmit a MEASUREMENT REPORT to the UTRAN and typically this may result in an update of the active set. However, in some situations the UTRAN may be unable to add a strong cell to the active set typically due to capacity shortage for example. The UE shall continue reporting after the initial report by reverting to periodical measurement reporting if the reported cell is not added to the active set. This is illustrated in Figure 14.1.4.1-1. During periodic reporting the UE shall transmit MEASUREMENT REPORT messages to the UTRAN at predefined intervals. The reports shall include reporting information of the cells in the current active set and of the monitored cell(s) in the reporting range. Event-triggered periodic measurement reporting shall be terminated if: 1> there are no longer any monitored cell(s) within the reporting range; or 1> the UTRAN has added cells to the active set so that it includes the maximum number of cells (defined by the reporting deactivation threshold parameter), which are allowed for event 1A to be triggered; or 1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the amount of reporting parameter). The reporting period is assigned by the UTRAN (with the Reporting interval parameter). If the reporting interval is set to zero event-triggered periodic measurement reporting shall not be applied.
3GPP
Release 6
1147
3GPP TS 25.331 V6.23.0 (2009-09)
14.1.4.1a
Cell removal failure (FDD only)
PCPICH 1
Reporting terminated
PCPICH 2 Event-triggered report Periodic report Periodic report
Figure 14.1.4.1a: Periodic reporting triggered by event 1B When a cell enters the removal range and triggers event 1B, the UE shall transmit a MEASUREMENT REPORT to the UTRAN and typically this may result in the removal of the weakest active cell. If the UTRAN is unable to receive MEASUREMENT REPORT after the maximum retransmission, it is beneficial to receive continuous reports in this case as well. The UE shall revert to periodical measurement reporting if the UTRAN does not update the active set after the transmission of the measurement report. This is illustrated in Figure 14.1.4.1a. During periodic reporting the UE shall transmit MEASUREMENT REPORT messages to the UTRAN at predefined intervals. Event-triggered periodic measurement reporting shall be terminated if: 1> there are no longer any monitored cell(s) within the removal range; or 1> the UTRAN has removed cells from the active set so that there are no longer the minimum amount of active cells for event 1B to be triggered; or 1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the "amount of reporting" parameter). The reporting period is assigned by the UTRAN (with the "Reporting interval" parameter). If the reporting interval is set to zero, event-triggered periodic measurement reporting shall not be applied.
3GPP
Release 6
1148
3GPP TS 25.331 V6.23.0 (2009-09)
14.1.4.2
Cell replacement failure (FDD only)
PCPICH 1 PCPICH 2
Periodic report Event-triggered report
Periodic report
Reporting terminated
PCPICH 4
PCPICH 3
Figure 14.1.4.1-2: Periodic reporting triggered by event 1C When a cell enters the replacement range and triggers event 1C, the UE shall transmit a MEASUREMENT REPORT to the UTRAN and typically this may result in the replacement of the weakest active cell. If the UTRAN is unable to replace the cell due to for example capacity shortage, it is beneficial to receive continuous reports in this case as well. The UE shall revert to periodical measurement reporting if the UTRAN does not update the active set after the transmission of the measurement report. This is illustrated in Figure 14.1.4.1-2. During periodic reporting the UE shall transmit MEASUREMENT REPORT messages to the UTRAN at predefined intervals. The reports shall include reporting information of the cells in the current active set and of the monitored cell(s) in the replacement range. Event-triggered periodic measurement reporting shall be terminated if: 1> there are no longer any monitored cell(s) within the replacement range; or 1> the UTRAN has removed cells from the active set so that there are no longer the minimum amount of active cells for event 1C to be triggered (as defined by the replacement activation threshold parameter); or 1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the amount of reporting parameter). The reporting period is assigned by the UTRAN (with the Reporting interval parameter). If the reporting interval is set to zero, event-triggered periodic measurement reporting shall not be applied.
14.1.5
14.1.5.1
Mechanisms available for modifying intra-frequency measurement reporting behaviour (informative)

Hysteresis
To limit the amount of event-triggered reports, a hysteresis parameter may be connected with each reporting event given above. The value of the hysteresis is given to the UE in the Reporting criteria field of the Measurement Control message. In the example in Figure 14.1.5.1-1, the hysteresis ensures that the event 1D (FDD) or IG(TDD) (primary CPICH(FDD)/CCPCH(TDD) 2 becomes the best cell) is not reported until the difference is equal to the hysteresis value. The fact that primary CPICH(FDD)/CCPCH(TDD) 1 becomes best afterwards is not reported at all in the example since the primary CPICH(FDD)/CCPCH(TDD) 1 does not become sufficiently better than the primary CPICH(FDD)/CCPCH(TDD) 2.
3GPP
Release 6
1149
3GPP TS 25.331 V6.23.0 (2009-09)
Measurement quantity P CCPCH 1 Hysteresis
P CCPCH 2 Hysteresis
Reporting event 1D
Time
Figure 14.1.5.1-1: Hysteresis limits the amount of measurement reports
14.1.5.2
Time-to-trigger
To limit the measurement signalling load, a time-to-trigger parameter could be connected with each reporting event given above. The value of the time-to-trigger is given to the UE in the Reporting criteria field of the Measurement Control message. The effect of the time-to-trigger is that the report is triggered only after the conditions for the event have existed for the specified time-to-trigger. In the following FDD example in Figure 14.1.5.2-1, the use of time-to-trigger means that the event (primary CPICH 3 enters the reporting range) is not reported until is has been within the range for the time given by the time-to-trigger parameter.
Measurement quantity P CPICH 1 Reporting range
P CPICH 2
P CPICH 3
Time-to-trigger
Reporting event 1A
Time
Figure 14.1.5.2-1: Time-to-trigger limits the amount of measurement reports In the following TDD example in Figure 14.1.5.2-2, the use of time-to-trigger means that the event (Timeslot ISCP upon certain threshold) is not reported until it has been upon the threshold for the time given by the time-to trigger parameter.
3GPP
Release 6
1150
3GPP TS 25.331 V6.23.0 (2009-09)
Timeslot ISCP
TS 1 ISCP Threshold
Time-to-trigger
Reporting Event 1J
Time
Figure 14.1.5.2-2: Time-to-trigger limits the amount of measurement reports NOTE: The time-to-trigger could be combined with hysteresis, i.e. a hysteresis value is added to the measurement quantity before evaluating if the time-to-trigger timer should be started.
14.1.5.3
Cell individual offsets
For each cell that is monitored, an offset can be assigned with inband signalling. The offset can be either positive or negative. The offset is added to the measurement quantity before the UE evaluates if an event has occurred. The UE receives the cell individual offsets for each primary CPICH(FDD)/CCPCH(TDD) in the IE "Cell individual offset" included in the IE "Cell info" associated with each measurement object included in the MEASUREMENT CONTROL message. For the FDD example, in Figure 14.1.5.3-1, since an offset is added to primary CPICH 3, it is the dotted curve that is used to evaluate if an event occurs. Hence, this means that measurement reports from UE to UTRAN are triggered when primary CPICH plus the corresponding offset, i.e. the dotted curve, leaves and enters the reporting range and when it gets better than primary CPICH 1 (if these events have been ordered by UTRAN). This offset mechanism provides the network with an efficient tool to change the reporting of an individual primary CPICH. By applying a positive offset, as in Figure 14.1.5.3-1, the UE will send measurement reports as if the primary CPICH is offset x dB better than what it really is. This could be useful if the operator knows that a specific cell is interesting to monitor more carefully, even though it is not so good for the moment. In the example in Figure 14.1.5.3-1, the operator might know by experience that in this area primary CPICH 3 can become good very quickly (e.g. due to street corners) and therefore that it is worth reporting more intensively. Depending on the implemented handover evaluation algorithm, this may result in the cell with primary CPICH 3 being included in the active set earlier than would have been the case without the positive offset.
3GPP
Release 6
1151
3GPP TS 25.331 V6.23.0 (2009-09)
Measurement quantity P CPICH 1 Reporting range
P CPICH 2
Offset for P CPICH 3 P CPICH 3

Reporting event 1B Reporting event 1A
Time
Figure 14.1.5.3-1: A positive offset is applied to primary CPICH 3 before event evaluation in the UE For the TDD example, in Figure 14.1.5.3-2, an offset is added to primary CCPCH2, it is the dotted curve that is used to evaluate if the primary CCPCH2 becomes better than primary CCPCH1 (ordered by the UTRAN).
Measurement quantity PCCPCH 1
Offset for PCCPCH 2
Reporting Event 1G
Time
Figure 14.1.5.3-2: A positive offset is applied to primary CCPCH 2 Correspondingly, the operator can choose to apply a negative offset to a primary CCPCH. Then the reporting on that primary CCPCH is limited and the corresponding cell may be, at least temporarily excluded from the active set or as a target cell for handover. It is important to note that the offset is added before triggering events, i.e. the offset is added by the UE before evaluating if a measurement report should be sent as opposed to offsets that are applied in the network and used for the actual handover evaluation. It should also be noted that the cell individual offset is not used in all measurement reporting events, and that it is not applied to all events in the same way.
14.1.5.4
Forbid a Primary CPICH to affect the reporting range (FDD only)
The reporting range affects the reporting events 1A and 1B presented above. The reporting range is defined as a function of all the Primary CPICHs in the active set (see 14.1.2.1 and 14.1.2.2). If the parameter W is set to 0, the reporting range is defined relative to the best Primary CPICH. However, there could be cases where it is good to forbid a specific Primary CPICH to affect the reporting range. For example in Figure 14.1.5.4-1 the network has requested the UE to not let Primary CPICH 3 affect the reporting range. This mechanism could be effective if the operator knows by experience that the quality of Primary CPICH 3 is very unstable in a specific area and therefore should not affect the reporting of the other Primary CPICHs.
3GPP
Release 6
1152
3GPP TS 25.331 V6.23.0 (2009-09)
The UE shall ignore that a Primary CPICH is forbidden to affect the reporting range if all of the following conditions are fulfilled: the Primary CPICH is included in active set; and all cells in active set are defined as Primary CPICHs forbidden to affect the reporting range.
Measurement quantity P CPICH 1 Reporting range Reporting Range Constant
P CPICH 2
P CPICH 3
Time
Figure 14.1.5.4-1: Primary CPICH 3 is forbidden to affect the reporting range
14.1.6
Report quantities in intra-frequency measurements
The quantities that the UE shall report to UTRAN when the event is triggered for an intra-frequency measurement are given by the IE "Intra-frequency reporting quantity" stored for this measurement and can be the following: 1 SFN-SFN observed time difference 2 Cell synchronisation information 3 Cell Identity 4 Downlink Ec/N0 (FDD). 5 Downlink path loss. For FDD: Pathloss in dB = Primary CPICH Tx power - CPICH RSCP. For Primary CPICH Tx power the IE "Primary CPICH Tx power" shall be used. The unit is dBm. CPICH RSCP is the result of the CPICH RSCP measurement. The unit is dBm.
For TDD: Pathloss in dB = Primary CCPCH TX power - Primary CCPCH RSCP. For Primary CCPCH TX power the IE "Primary CCPCH TX Power" shall be used. The unit is dBm. Primary CCPCH RSCP is the result of the Primary CCPCH RSCP measurement. The unit is dBm.
If necessary Pathloss shall be rounded up to the next higher integer. Results higher than 158 shall be reported as 158. Results lower than 46 shall be reported as 46. 6 Downlink received signal code power (RSCP) after despreading (of a primary CPICH for FDD, and of a primary CCPCH for TDD). 7 ISCP measured on Timeslot basis. (TDD)
3GPP
Release 6
1153
3GPP TS 25.331 V6.23.0 (2009-09)
8 Proposed TGSN (TDD) A description of those values can be found in [7] and [8].
14.2
Inter-frequency measurements
14.2.0a Inter-frequency measurement quantities

The two first measurement quantities listed below are used by the UE to evaluate whether an inter-frequency measurement event has occurred or not, through the computation of a frequency quality estimate. The quantity to use to compute the frequency quality estimate for an inter-frequency measurement is given in the "Inter-frequency measurement quantity" stored for that measurement. 1 Downlink Ec/No (FDD) 2 Downlink received signal code power (RSCP) after despreading. 3 Downlink path loss. For FDD: Pathloss in dB = Primary CPICH Tx power - CPICH RSCP. For Primary CPICH Tx power the IE "Primary CPICH Tx power" shall be used. The unit is dBm. CPICH RSCP is the result of the CPICH RSCP measurement. The unit is dBm.
A description of those values can be found in [7] and [8].
14.2.0b Frequency quality estimate

14.2.0b.1 FDD cells
The frequency quality estimate used in events 2a, 2b 2c, 2d, 2e and 2f is defined as:
NA j Q frequencyj = 10 LogM frequency j = W j 10 Log M i j + (1 W j ) 10 LogM Best j , i =1

The variables in the formula are defined as follows ("the virtual active set on frequency j" should be understood as the active set if frequency j is the used frequency. If frequency j is a non-used frequency, the way the virtual active set is initiated and updated is described in subclause 14.11): Qfrequency j is the estimated quality of the virtual active set on frequency j. Mfrequency j is the estimated quality of the virtual active set on frequency j. Mi j is a measurement result of cell i in the virtual active set on frequency j. NA j is the number of cells in the virtual active set on frequency j. MBest j is the measurement result of the cell in the virtual active set on frequency j with the highest measurement result.
3GPP
Release 6
1154
3GPP TS 25.331 V6.23.0 (2009-09)
Wj is a parameter sent from UTRAN to UE and used for frequency j. If the measurement result is CPICH-Ec/No then MFrequency, Mi j and MBest are expressed as ratios. If the measurement result is CPICH-RSCP or PCCPCH-RSCP then MFrequency, Mi j and MBest are expressed in mW.
14.2.0b.2
TDD cells
j
Q i , frequency
= 10 LogM
i , frequency j
+ Oi, j
Qi ,frequency j is the estimated quality of cell i on frequency j. Mfrequency j is the measurement result for Primary CCPCH RSCP of cell i on frequency j expressed in mW. Oi,j is the cell individual offset of the currently evaluated cell i on frequency j. Oij is set by IE " Cell individual offset"
14.2.0c Inter-frequency reporting quantities

The quantities that the UE shall report for each cell to UTRAN when the event is triggered for an inter-frequency measurement is given by the "Inter-frequency reporting quantity" IE stored for this measurement and can be the following, from 1 to 8. The quantity number 9 can be reported for each frequency that triggered the report. 1 Cell identity 2 SFN-SFN observed time difference 3 Cell synchronisation information 4 Downlink Ec/No (FDD) 5 Downlink path loss. For FDD: Pathloss in dB = Primary CPICH Tx power - CPICH RSCP. For Primary CPICH Tx power the IE "Primary CPICH Tx power" shall be used. The unit is dBm. CPICH RSCP is the result of the CPICH RSCP measurement. The unit is dBm.
If necessary Pathloss shall be rounded up to the next higher integer. Results higher than 158 shall be reported as 158. Results lower than 46 shall be reported as 46. 6 Downlink received signal code power (RSCP) after despreading (of a primary CPICH for FDD, and of a primary CCPCH for TDD). 7 ISCP measured on Timeslot basis. (TDD) 8 Proposed TGSN (TDD) 9 UTRA carrier RSSI A description of those values can be found in [7] and [8].
3GPP
Release 6
1155
3GPP TS 25.331 V6.23.0 (2009-09)
14.2.1
Inter-frequency reporting events
Within the measurement reporting criteria field in the MEASUREMENT CONTROL message UTRAN notifies the UE which events should trigger the UE to send a MEASUREMENT REPORT message. The listed events are the toolbox from which the UTRAN can choose the reporting events that are needed for the implemented handover evaluation function, or other radio network functions. All events are evaluated with respect to one of the measurement quantities given in subclause 14.2.0a. The measurement quantities are measured on the monitored primary common pilot channels (CPICH) in FDD mode and the monitored primary common control channels (PCCPCH) in TDD mode of the cell defined in the measurement object. A "non-used frequency" is a frequency that the UE has been ordered to measure upon but is not used for the connection. A "used frequency" is a frequency that the UE has been ordered to measure upon and is also currently used for the connection. The "monitored set on non-used frequency" consists of cells in "cells for measurement" (or all cells in CELL_INFO_LIST if "cells for measurement" is not present) that are not part of the virtual active set on that non-used frequency. When one inter-frequency measurement identity corresponds to multiple inter-frequency events with identical event identities, the UE behaviour is not specified.
14.2.1.1
Event 2a: Change of best frequency.
When event 2a is configured in the UE within a measurement, the UE shall: 1> when the measurement is initiated or resumed: 2> store the used frequency in the variable BEST_FREQUENCY_2A_EVENT. 1> if equation 1 below has been fulfilled for a time period indicated by "Time to trigger" for a frequency included for that event and which is not stored in the variable BEST_FREQUENCY_2A_EVENT: 2> send a measurement report with IEs set as below: 3> set in "inter-frequency measurement event results": 4> "inter-frequency event identity" to "2a"; and 4> "Frequency info" to the frequency that triggered the event; and 4> "Non frequency related measurement event results" to the "Primary CPICH info" of the best primary CPICH for FDD cells or "Primary CCPCH info" to the "Cells parameters ID" of the best primary CCPCH for TDD cells on that frequency, not taking into account the cell individual offset. 3> if a non-used frequency triggered the measurement report: 4> include in IE "Inter-frequency measured results list" the measured results for the non-used frequency that triggered the event, not taking into account the cell individual offset. 3> if the used frequency triggered the measurement report: 4> do not include the IE "Inter-frequency measured results list" in the measurement report. 3> set the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset; 2> update the variable BEST_FREQUENCY_2A_EVENT with that frequency. Equation 1:
QNotBest QBest+H2a / 2
The variables in the formula are defined as follows:
3GPP
Release 6
1156
3GPP TS 25.331 V6.23.0 (2009-09)
QNot Best is the quality estimate of a frequency not stored the "best frequency" in the variable BEST_FREQUENCY_2A_EVENT. QBest is the quality estimate of the frequency stored in "best frequency" in the variable BEST_FREQUENCY_2A_EVENT. H2a is the hysteresis parameter for the event 2a in that measurement.
14.2.1.2
Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold.
When an inter-frequency measurement configuring event 2b is set up, the UE shall: 1> create a variable TRIGGERED_2B_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 2b is configured in the UE within a measurement, the UE shall: 1> if equations 1 and 2 below have been fulfilled for a time period indicated by "Time to Trigger" from the same instant, respectively for one or several non-used frequencies included for that event and for the used frequency: 2> if any of those non-used frequency is not stored in the variable TRIGGERED_2B_EVENT: 3> store the non-used frequencies that triggered the event and that were not previously stored in the variable TRIGGERED_2B_EVENT into that variable; 3> send a measurement report with IEs set as below: 4> set in "inter-frequency measurement event results": 5> "inter-frequency event identity" to "2b"; and 5> for each non-used frequency that triggered the event, beginning with the best frequency: 6> "Frequency info" to that non-used frequency; and 6> "Non frequency related measurement event results" to the "Primary CPICH info" of the best primary CPICH for FDD cells or "Primary CCPCH info" to the "Cell parameters ID" of the best primary CCPCH for TDD cells on that non-used frequency, not taking into account the cell individual offset. 4> include in IE "Inter-frequency measured results list" the measured results for each non-used frequency that triggered the event, not taking into account the cell individual offset; 4> set the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset. 1> if equation 3 below is fulfilled for a non-used frequency stored in the variable TRIGGERED_2B_EVENT: 2> remove that non-used frequency from the variable TRIGGERED_2B_EVENT. 1> if equation 4 below is fulfilled for the used frequency: 2> clear the variable TRIGGERED_2B_EVENT. Triggering conditions: Equation 1:
QNonusedTNonused2b +H2b / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency that becomes better than an absolute threshold.
3GPP
Release 6
1157
3GPP TS 25.331 V6.23.0 (2009-09)
TNon used 2b is the absolute threshold that applies for this non-used frequency in that measurement. H2b is the hysteresis parameter for the event 2b. Equation 2:
Q T 2b H2b / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2b is the absolute threshold that applies for the used frequency in that measurement. H2b is the hysteresis parameter for the event 2b. Leaving triggered state condition: Equation 3:
QNonused<TNonused2b H2b / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency that is stored in the variable TRIGGERED_2B_EVENT. TNon used 2b is the absolute threshold that applies for this non-used frequency in that measurement. H2b is the hysteresis parameter for the event 2b. Equation 4:
Q >T 2b +H2b / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2b is the absolute threshold that applies for the used frequency in that measurement. H2b is the hysteresis parameter for the event 2b.
14.2.1.3
Event 2c: The estimated quality of a non-used frequency is above a certain threshold
When an inter-frequency measurement configuring event 2c is set up, the UE shall: 1> create a variable TRIGGERED_2C_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 2c is configured in the UE within a measurement, the UE shall: 1> if equation 1 below has been fulfilled for one or several non-used frequencies included for that event during the time "Time to trigger": 2> if any of those non-used frequencies is not stored in the variable TRIGGERED_2C_EVENT: 3> store the non-used frequencies that triggered the event and that were not previously stored in the variable TRIGGERED_2C_EVENT into that variable; 3> send a measurement report with IEs set as below: 4> set in "inter-frequency measurement event results": 5> "inter-frequency event identity" to "2c"; and
3GPP
Release 6
1158
3GPP TS 25.331 V6.23.0 (2009-09)
5> for each non-used frequency that triggered the event, beginning with the best frequency: 6> "Frequency info" to that non-used frequency; and 6> "Non frequency related measurement event results" to the "Primary CPICH info" of the best primary CPICH for FDD cells or "Primary CCPCH info" to the "Cell parameters ID" of the best primary CCPCH for TDD cells on that non-used frequency, not taking into account the cell individual offset. 4> include in IE "Inter-frequency measured results list" the measured results for each non-used frequency that triggered the event, not taking into account the cell individual offset; 4> set the IE "additional measured results" according to subclause 8.4.2 not taking into account the cell individual offset. 1> if equation 2 below is fulfilled for a non-used frequency stored in the variable TRIGGERED_2C_EVENT: 2> remove that non-used frequency from the variable TRIGGERED_2C_EVENT. Triggering condition: Equation 1:
QNonusedTNonused2c +H2c / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency that becomes better than an absolute threshold. TNon used 2c is the absolute threshold that applies for this non-used frequency in that measurement. H2c is the hysteresis parameter for the event 2c. Leaving triggered state condition: Equation 2:
QNonused<TNonused2c H2c / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency stored in the variable TRIGGERED_2C_EVENT. TNon used 2c is the absolute threshold that applies for this non-used frequency in that measurement. H2c is the hysteresis parameter for the event 2c.
14.2.1.4
Event 2d: The estimated quality of the currently used frequency is below a certain threshold
A UE shall be able to perform this measurement and the corresponding event reporting without requiring compressed mode. When an inter-frequency measurement configuring event 2d is set up, the UE shall: 1> create a variable TRIGGERED_2D_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When event 2d is configured in the UE within a measurement, the UE shall: 1> if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger": 2> if the variable TRIGGERED_2D_EVENT is set to FALSE: 3> set the variable TRIGGERED_2D_EVENT to TRUE;
3GPP
Release 6
1159
3GPP TS 25.331 V6.23.0 (2009-09)
3> send a measurement report with IEs set as below: 4> set in "inter-frequency event results": "inter-frequency event identity" to "2d" and no IE "Interfrequency cells", not taking into account the cell individual offset; 4> include in IE "Inter-frequency measured results list" the measured results for the used frequency, not taking into account the cell individual offset; 4> set the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset. 1> if the variable TRIGGERED_2D_EVENT is set to TRUE and if equation 2 is fulfilled for the used frequency: 2> set the variable TRIGGERED_2D_EVENT to FALSE. Triggering condition: Equation 1:
Q T 2d H2d / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2d is the absolute threshold that applies for the used frequency and event 2d. H2d is the hysteresis parameter for the event 2d. Leaving triggered state condition: Equation 2:
Q >T 2d + H2d / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2d is the absolute threshold that applies for the used frequency and event 2d. H2d is the hysteresis parameter for the event 2d.
14.2.1.5
Event 2e: The estimated quality of a non-used frequency is below a certain threshold
When an inter-frequency measurement configuring event 2e is set up, the UE shall: 1> create a variable TRIGGERED_2E_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 2e is configured in the UE within a measurement, the UE shall: 1> if equation 1 below has been fulfilled for one or several non-used frequencies included for that event during the time "Time to trigger": 2> if any of those non-used frequencies is not stored in the variable TRIGGERED_2E_EVENT: 3> store the non-used frequencies that triggered the event and that were not previously stored in the variable TRIGGERED_2E_EVENT into that variable; 3> send a measurement report with IEs set as below: 4> set in "inter-frequency measurement event results":
3GPP
Release 6
1160
3GPP TS 25.331 V6.23.0 (2009-09)
5> "inter-frequency event identity" to "2e"; and 5> for each non-used frequency that triggered the event, beginning with the best frequency: 6> "Frequency info" to that non-used frequency; and 6> "Non frequency related measurement event results" to the "Primary CPICH info" of the best primary CPICH for FDD cells or "Primary CCPCH info" to the "Cell parameters ID" of the best primary CCPCH for TDD cells on that non-used frequency, not taking into account the cell individual offset. 4> include in the IE "Inter-frequency measured results list" the measured results for each non-used frequency that triggered the event, not taking into account the cell individual offset; 4> set the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset. 1> if equation 2 below is fulfilled for a non-used frequency stored in the variable TRIGGERED_2E_EVENT: 2> remove that non-used frequency from the variable TRIGGERED_2E_EVENT. Triggering condition: Equation 1:
QNonusedTNonused2e H2e / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency that becomes worse than an absolute threshold. TNon used 2e is the absolute threshold that applies for that non-used frequency for that event. H2e is the hysteresis parameter for the event 2e. Leaving triggered state condition: Equation 2:
QNonused>TNonused2e +H2e / 2
The variables in the formula are defined as follows: QNon used is the quality estimate of a non-used frequency stored in the variable TRIGGERED_2E_EVENT. TNon used 2e is the absolute threshold that applies for that non-used frequency for that event. H2e is the hysteresis parameter for the event 2e.
14.2.1.6
Event 2 f: The estimated quality of the currently used frequency is above a certain threshold
A UE shall be able to perform this measurement and the corresponding event reporting without requiring compressed mode. When an inter-frequency measurement configuring event 2f is set up, the UE shall: 1> create a variable TRIGGERED_2F_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When event 2f is configured in the UE within a measurement, the UE shall: 1> if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger": 2> if the variable TRIGGERED_2F_EVENT is set to FALSE:
3GPP
Release 6
1161
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the variable TRIGGERED_2F_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "inter-frequency event results": "inter-frequency event identity" to "2f", and no IE "Interfrequency cells"; 4> include in IE "Inter-frequency measured results list" the measured results for the used frequency, not taking into account the cell individual offset; 4> set the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset. 1> if the variable TRIGGERED_2F_EVENT is set to TRUE and if equation 2 is fulfilled for the used frequency: 2> set the variable TRIGGERED_2F_EVENT to FALSE. Triggering condition: Equation 1:
Q T 2 f +H2f / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2f is the absolute threshold that applies for the used frequency and event 2f. H2f is the hysteresis parameter for the event 2f. Leaving triggered state condition: Equation 2:
Q <T 2 f H2f / 2 Used Used

The variables in the formula are defined as follows: QUsed is the quality estimate of the used frequency. TUsed 2f is the absolute threshold that applies for the used frequency and event 2f. H2f is the hysteresis parameter for the event 2f.
14.3
Inter-RAT measurements
14.3.0a Inter-RAT measurement quantities

A measurement quantity is used by the UE to evaluate whether an inter-RAT measurement event has occurred or not. The measurement quantity for UTRAN is used to compute the frequency quality estimate for the active set, as described in the next subclause, and can be: 1 Downlink Ec/No. 2 Downlink received signal code power (RSCP) after despreading. The measurement quantity for GSM can be: 1 GSM Carrier RSSI A description of those values can be found in [7] and [8].
3GPP
Release 6
1162
3GPP TS 25.331 V6.23.0 (2009-09)
14.3.0b Frequency quality estimate of the UTRAN frequency

The estimated quality of the active set in UTRAN in event 3a is defined as:
NA QUTRAN = 10 LogM UTRAN = W 10 Log M i + (1 W ) 10 LogM Best , i =1

The variables in the formula are defined as follows: QUTRAN is the estimated quality of the active set on the currently used UTRAN frequency. MUTRAN is the estimated quality of the active set on currently used UTRAN frequency expressed in another unit. Mi is the measurement result of cell i in the active set, according to what is indicated in the IE "Measurement quantity for UTRAN quality estimate". NA is the number of cells in the active set. MBest is the measurement result of the cell in the active set with the highest measurement result. W is a parameter sent from UTRAN to UE. If the measurement result is CPICH-Ec/No MUTRAN, Mi and MBest are expressed as ratios. If the measurement result is CPICH-RSCP or PCCPCH-RSCP, MUTRAN, Mi and MBest are expressed in mW.
14.3.0c Inter-RAT reporting quantities

The quantities that the UE shall report to UTRAN when the event is triggered for an inter-RAT measurement are given by the IE "Inter-RAT reporting quantity" stored for that measurement, and can be the following: In the case the other RAT is GSM: 1 GSM carrier RSSI A description of those values can be found in [7] and [8].
14.3.1
Inter-RAT reporting events
Within the measurement reporting criteria field in the MEASUREMENT CONTROL message the UTRAN notifies the UE which events should trigger the UE to send a MEASUREMENT REPORT message. The listed events are the toolbox from which the UTRAN can choose the reporting events that are needed for the implemented handover evaluation function, or other radio network functions. All events are measured with respect to one of the measurement quantities given in subclause 14.3.0a, and of the frequency quality estimate given in subclause 14.3.0b. For UTRAN the measurement quantities are measured on the monitored primary common pilot channels (CPICH) in FDD mode and the monitored primary common control channels (PCCPCH) in TDD mode of the cell defined in the measurement object. For other RATs the measurement quantities are system-specific. A "used UTRAN frequency" is a frequency that the UE have been ordered to measure upon and is also currently used for the connection to UTRAN. "Other system" is e.g. GSM. In the text below describing the events: "The BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement" shall be understood as the BCCH ARFCN and BSIC combinations of the inter-RAT cells pointed at in the IE "Cells for measurement" if it has been received for that inter-RAT measurement, or otherwise of the cells included in the "inter-RAT cell info" part of the variable CELL_INFO LIST. "The BCCH ARFCNs considered in that inter-RAT measurement" shall be understood as the BCCH ARFCNs of the inter-RAT cells pointed at in the IE "Cells for measurement" if it has been received for that inter-RAT measurement, or otherwise of the cells included in the "inter-RAT cell info" part of the variable CELL_INFO LIST.
3GPP
Release 6
1163
3GPP TS 25.331 V6.23.0 (2009-09)
When one inter-RAT measurement identity corresponds to multiple inter-RAT events with identical event identities, the UE behaviour is not specified.
14.3.1.1
Event 3a: The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold.
When an inter-RAT measurement configuring event 3a is set up, the UE shall: 1> create a variable TRIGGERED_3A_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 3a is configured in the UE within a measurement, the UE shall: 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "required": 2> if equations 1 and 2 below have both been fulfilled for a time period indicated by "Time to trigger" from the same instant, respectively for the used UTRAN frequency and for one or several GSM cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement: 3> if the Inter-RAT cell id of any of those GSM cells is not stored in the variable TRIGGERED_3A_EVENT: 4> store the Inter-RAT cell ids of the GSM cells that triggered the event and that were not previously stored in the variable TRIGGERED_3A_EVENT into that variable. 4> send a measurement report with IEs set as below: 5> in "inter-RAT measurement event result": "inter-RAT event identity" to "3a", "CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells that triggered the event (best one first), taking into account the cell individual offset of the GSM cells; 5> "measured results" and possible "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 4 is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variable TRIGGERED_3A_EVENT: 3> remove the inter-RAT cell id of that GSM cell from the variable TRIGGERED_3A_EVENT. 2> if equation 3 is fulfilled for the used frequency in UTRAN: 3> clear the variable TRIGGERED_3A_EVENT. 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required": 2> if equations 1 and 2 below have been fulfilled for a time period indicated by "Time to trigger" from the same instant, respectively for the used UTRAN frequency and for one or several BCCH ARFCNs considered in that inter-RAT measurement: 3> if any of those BCCH ARFCNs is not stored into the variable TRIGGERED_3A_EVENT: 4> store the BCCH ARFCNs that triggered the event and that were not previously stored in the variable TRIGGERED_3A_EVENT into that variable; 4> send a measurement report with IEs set as below: 5> in "inter-RAT measurement event result": "inter-RAT event identity" to "3a", "CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH ARFCNs that triggered the event (best one first), taking into account the cell individual offset of the GSM cells; 5> "measured results" and possible "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 4 is fulfilled for a BCCH ARFCN that is stored in the variable TRIGGERED_3A_EVENT:
3GPP
Release 6
1164
3GPP TS 25.331 V6.23.0 (2009-09)
3> remove that BCCH ARFCN from the variable TRIGGERED_3A_EVENT. 2> if equation 3 is fulfilled for the used frequency in UTRAN: 3> clear the variable TRIGGERED_3A_EVENT. Triggering conditions: Equation 1:
Q T H3a / 2 Used Used

QUsed is the quality estimate of the used UTRAN frequency. TUsed is the absolute threshold that applies for the used frequency in that measurement. H3a is the hysteresis parameter for event 3a.
Equation 2:
MOther RAT+CIO RAT TOther RAT+H3a / 2 Other

MOther RAT is the measurement quantity for the cell of the other system.
CIOOther RAT is the cell individual offset for the cell of the other system.
TOther RAT is the absolute threshold that applies for the other system in that measurement. H3a is the hysteresis parameter for event 3a.
Leaving triggered state conditions: Equation 3:
Q >T +H3a / 2 Used Used

QUsed is the quality estimate of the used UTRAN frequency. TUsed is the absolute threshold that applies for the used frequency in that measurement. H3a is the hysteresis parameter for event 3a.
Equation 4:
MOther RAT+CIO RAT <TOther RATH3a / 2 Other

MOther RAT is the measurement quantity for the cell of the other system. MOther RAT is expressed in dBm.
TOther RAT is the absolute threshold that applies for the other system in that measurement. H3a is the hysteresis parameter for event 3a.
3GPP
Release 6
1165
3GPP TS 25.331 V6.23.0 (2009-09)
14.3.1.2
Event 3b: The estimated quality of other system is below a certain threshold
When an inter-RAT measurement configuring event 3b is set up, the UE shall: 1> create a variable TRIGGERED_3B_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 3b is configured in the UE within a measurement, the UE shall: 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "required": 2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several GSM cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement: 3> if the inter-RAT cell id of any of those GSM cell is not stored in the variable TRIGGERED_3B_EVENT: 4> store the inter-RAT cell ids of the GSM cells that triggered the event and that were not previously stored in the variable TRIGGERED_3B_EVENT into that variable; 4> send a measurement report with IEs set as below: 5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b", "CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells that triggered the event (worst one first), taking into account the cell individual offset of the GSM cells; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variable TRIGGERED_3B_EVENT: 3> remove the inter-RAT cell id of that GSM cell from the variable TRIGGERED_3B_EVENT. 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required": 2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several of the BCCH ARFCNs considered in that inter-RAT measurement: 3> if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3B_EVENT: 4> store the BCCH ARFCNs that triggered the event and that were not previously stored in the variable TRIGGERED_3B_EVENT into that variable; 4> send a measurement report with IEs set as below: 5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b", "CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH ARFCNs that triggered the event (worst one first), taking into account the cell individual offset of the GSM cells; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 2 below is fulfilled for a BCCH ARFCN that is stored in the variable TRIGGERED_3B_EVENT: 3> remove that BCCH ARFCN from the variable TRIGGERED_3B_EVENT. Triggering condition: Equation 1:
MOther RAT+CIO RATTOther RATH3b / 2 Other

MOther RAT is the measurement quantity for the cell of the other system.
3GPP
Release 6
1166
3GPP TS 25.331 V6.23.0 (2009-09)
TOther RAT is the absolute threshold that applies for the other system in that measurement. H3b is the hysteresis parameter for event 3b.
Leaving triggered state condition: Equation 2:
MOther RAT+CIO RAT>T RAT+ H3b / 2 Other Other

TOther RAT is the absolute threshold that applies for the other system in that measurement. H3b is the hysteresis parameter for event 3b. 14.3.1.3 Event 3c: The estimated quality of other system is above a certain threshold
When an inter-RAT measurement configuring event 3c is set up, the UE shall: 1> create a variable TRIGGERED_3C_EVENT related to that measurement, which shall initially be empty; 1> delete this variable when the measurement is released. When event 3c is configured in the UE within a measurement, the UE shall: 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "required": 2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several GSM cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement: 3> if the inter-RAT cell id of any of those GSM cell is not stored in the variable TRIGGERED_3C_EVENT: 4> store the Inter-RAT cell ids of the GSM cells that triggered the event and that were not previously stored in the variable TRIGGERED_3C_EVENT into that variable; 4> send a measurement report with IEs set as below: 5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c", "CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells that triggered the event (best one first), taking into account the cell individual offset of the GSM cells; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variable TRIGGERED_3C_EVENT: 3> remove the inter-RAT cell id of that GSM cell from the variable TRIGGERED_3C_EVENT. 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required": 2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several of the BCCH ARFCNs considered in that inter-RAT measurement: 3> if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3C_EVENT:
3GPP
Release 6
1167
3GPP TS 25.331 V6.23.0 (2009-09)
4> store the BCCH ARFCNs that triggered the event and that were not previously stored in the variable TRIGGERED_3C_EVENT into that variable; 4> send a measurement report with IEs set as below: 5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c", "CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH ARFCNs that triggered the event (best one first), taking into account the cell individual offset of the GSM cells; 5> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 2 is fulfilled for a BCCH ARFCN that is stored in the variable TRIGGERED_3C_EVENT: 3> remove that BCCH ARFCN from the variable TRIGGERED_3C_EVENT. Triggering condition: Equation 1:
MOther RAT+CIO RATTOther RAT+ H3c / 2 Other

TOther RAT is the absolute threshold that applies for the other system in that measurement. H3c is the hysteresis parameter for event 3c.
Leaving triggered state condition: Equation 2:
MOther RAT+CIO RAT<TOther RAT H3c / 2 Other

TOther RAT is the absolute threshold that applies for the other system in that measurement. H3c is the hysteresis parameter for event 3c. 14.3.1.4 Event 3d: Change of best cell in other system
When an inter-RAT measurement configuring event 3d is set up, the UE shall: 1> create a variable BEST_CELL_3D_EVENT related to that measurement; 1> delete this variable when the measurement is released.
3GPP
Release 6
1168
3GPP TS 25.331 V6.23.0 (2009-09)
When event 3d is configured in the UE within a measurement, the UE shall: 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "required": 2> when the measurement is initiated or resumed: 3> store in the variable BEST_CELL_3D_EVENT the Inter-RAT cell id of the GSM cell that has the best measured quantity among the GSM cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement, not taking into account the cell individual offset of the GSM cells; 3> send a measurement report with IE set as below: 4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d", "CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cell that is stored in the variable BEST_CELL_3D_EVENT; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 1 has been fulfilled for a time period indicated by "time to trigger" for a GSM cell that is different from the one stored in BEST_CELL_3D_EVENT and that matches any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement: 3> store the Inter-RAT cell id of that GSM cell in the variable BEST_CELL_3D_EVENT; 3> send a measurement report with IEs set as below: 4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d", "CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cell is now stored in BEST_CELL_3D_EVENT; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required": 2> when the measurement is initiated or resumed: 3> store in the variable BEST_CELL_3D_EVENT the BCCH ARFCN of the GSM cell that has the best measured quantity among the BCCH ARFCNs considered in that inter-RAT measurement; 3> send a measurement report with IE set as below: 4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d", "CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to the BCH ARFCN that is stored in the variable BEST_CELL_3D_EVENT; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual offset. 2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one of the BCCH ARFCNs considered in that inter-RAT measurement and different from the one stored in BEST_CELL_3D_EVENT: 3> store the BCCH ARFCN of that GSM cell in the variable BEST_CELL_3D_EVENT; 3> send a measurement report with IEs set as below: 4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d", "CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to the BCCH ARFCN that is now stored in the variable BEST_CELL_3D_EVENT; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not taking into account the cell individual offset. Equation 1:
3GPP
Release 6
1169
3GPP TS 25.331 V6.23.0 (2009-09)
MNewMBest+H3d / 2
MNew is the measurement quantity for a GSM cell that is not stored in the variable BEST_CELL_3D_EVENT. MBest is the measurement quantity for a GSM cell that is stored in the variable BEST_CELL_3D_EVENT. H3d is the hysteresis parameter for event 3d.
14.3.2
14.3.2.1
GSM measurements in compressed mode

GSM RSSI measurements
The UE shall perform GSM RSSI measurements in the gaps of compressed mode pattern sequence specified for GSM RSSI measurement purpose.
14.3.2.2
Initial BSIC identification
The UE shall perform Initial BSIC identification in compressed mode pattern sequence specified for Initial BSIC identification measurement purpose. The parameter "N identify abort" in the IE "DPCH compressed mode info" indicates the maximum number of patterns that the UE shall use to attempt to decode the unknown BSIC of the GSM cell in the initial BSIC identification procedure. The BSIC identification procedure is defined in detail in [19].
14.3.2.3
BSIC re-confirmation
The UE shall perform BSIC re-confirmation in compressed mode pattern sequence specified for BSIC re-confirmation measurement purpose. The parameter "T reconfirm abort" in the IE "DPCH compressed mode info" indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure. The BSIC re-confirmation procedure is defined in detail in [19].
14.4
14.4.1
Traffic Volume Measurements

Traffic Volume Measurement Quantity
Traffic volume measurements may be configured by RRC to assist with dynamic radio bearer control. The reported quantities that can be configured are: 1 Buffer Occupancy. 2 Average of Buffer Occupancy. 3 Variance of Buffer Occupancy. A description of these values can be found in [15]. When a report is triggered, the UE shall provide the requested quantities for the acknowledged and unacknowledged mode RBs mapped onto the transport channels identified. When the RLC buffer payload, Average of RLC buffer payload or Variance of RLC buffer payload is reported, the measured quantity shall be rounded upwards to the closest higher value possible to report.
3GPP
Release 6
1170
3GPP TS 25.331 V6.23.0 (2009-09)
14.4.2
Traffic Volume reporting triggers
Traffic volume measurement reports can be triggered using two different mechanisms, periodical and event triggered. The reporting criteria are specified in the measurement control message. All the specified events are evaluated with respect to the Transport Channel Traffic Volume (TCTV). This quantity is equal to the sum of the Buffer Occupancy for all logical channels mapped onto a transport channel. The events on a given transport channel shall be evaluated at least at every TTI (may be more often) as described in [15]. When one traffic volume measurement identity corresponds to multiple traffic volume events with identical event identities for the same transport channel, the UE behaviour is not specified. When a traffic volume measurement is set up, the UE shall: 1> if the IE "report criteria" is set to "Traffic volume measurement reporting criteria": 2> for each IE "Parameters sent for each transport channel": 3> if the IE "Uplink transport channel type" is not included; or 3> if the IE "Uplink Transport Channel Type" has the value "DCH" or "USCH" and the IE "UL transport channel id" is not included: 4> for each IE "Parameters required for each Event": 5> for each uplink transport channel on which the UE is supposed to report (see below): 6> configure an event trigger defined by the values in the IEs "Measurement Identity", "Traffic volume event identity", "Reporting threshold", "Time to trigger", "Pending time after trigger" and "Tx Interruption after trigger". 3> else: 4> for each IE "Parameters required for each Event": 5> for the uplink transport channel defined by the IEs "Uplink transport channel type" and "UL transport channel id": 6> configure an event trigger defined by the values in the IEs "Measurement Identity", "Traffic volume event identity", "Reporting threshold", "Time to trigger", "Pending time after trigger" and "Tx Interruption after trigger". 1> else: 2> if the IE "report criteria" is set to "Periodical reporting criteria": 2> configure periodical triggers with period equal to the value in the IE "Reporting Interval" and with number of transmissions equal to the value in the IE "Amount of reporting" for the measurement identified by the IE "Measurement Identity". For each transport channel for which an event trigger has been configured, the UE shall: 1> for each event configured for this transport channel: 2> if the TCTV is larger than the threshold in IE "Reporting threshold" at TVM setup or modify; or 2> if the TCTV becomes larger than the threshold in IE "Reporting threshold" while the event is configured: 3> if the IE "Traffic volume event identity" has value "4a": 4> if the IE "Time to trigger" is not present; and 4> if the Pending-time-after-trigger timer for this event is not active: 5> if the IE "Pending time after trigger" is included: 6> start the Pending-time-after-trigger timer for this event with the value in this IE.
3GPP
Release 6
1171
3GPP TS 25.331 V6.23.0 (2009-09)
5> trigger a report for the measurement identified by the IE "Measurement Identity". 4> else: 5> start the Time-to-trigger timer for this event with the value in the IE "Time to trigger". 3> if the IE "Traffic volume event identity" has value "4b": 4> if the Time-to-trigger timer for this event is active: 5> stop this timer. 2> if the TCTV is smaller than the threshold in IE "Reporting threshold" at TVM setup or modify; or 2> if the TCTV becomes smaller than the threshold in IE "Reporting threshold" while the event is configured: 3> if the IE "Traffic volume event identity" has value "4a": 4> if the Time-to-trigger timer for this event is active: 5> stop this timer. 3> if the IE "Traffic volume event identity" has value "4b": 4> if the IE "Time to trigger" is not present; and 4> if the Pending-time-after-trigger timer for this event is not active: 5> if the IE "Pending time after trigger" is included: 6> start the Pending-time-after-trigger timer for this event with the value in this IE. 5> trigger a report for the measurement identified by the IE "Measurement Identity". 4> else: 5> start the Time-to-trigger timer for this event with the value in the IE "Time to trigger". When the Time-to-trigger timer for an event elapses: 1> if the Pending-time-after-trigger timer for this event is not active: 2> trigger a report for the measurement identified by the IE "Measurement Identity" corresponding to this event; 2> if the IE "Pending time after trigger" is included: 3> start the Pending-time-after-trigger timer for this event with the value in this IE. When the Pending-time-after-trigger for an event elapses: 1> if the IE "Traffic volume event identity" has value "4a": 2> if the TCTV is larger than the threshold in IE "Reporting threshold": 3> if the IE "Time to trigger" is not present: 4> trigger a report for the measurement identified by the IE "Measurement Identity" corresponding to this event; 4> start the Pending-time-after-trigger timer for this event with the value in the IE "Pending time after trigger". 3> else: 4> start the Time-to-trigger timer for this event with the value in the IE "Time to trigger". 1> if the IE "Traffic volume event identity" has value "4b": 2> if the TCTV is smaller than the threshold in IE "Reporting threshold":
3GPP
Release 6
1172
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the IE "Time to trigger" is not present: 4> trigger a report for the measurement identified by the IE "Measurement Identity" corresponding to this event; 4> start the Pending-time-after-trigger timer for this event with the value in the IE "Pending time after trigger". 3> else: 4> start the Time-to-trigger timer for this event with the value in the IE "Time to trigger". When a periodical trigger elapses, the UE shall: 1> trigger a report for the measurement identified by the IE "Measurement Identity"; 1> if the number of reports triggered by this periodical trigger reaches the value in the IE "Amount of reporting": 2> disable this periodical trigger. When a report is triggered for a given IE "Measurement Identity", the UE shall: 1> consider the variable MEASUREMENT_IDENTITY corresponding to this measurement identity; 1> if the report is triggered by an event trigger: 2> include the IE "Event results"; 2> set the IE "Uplink transport channel type causing the event" to the type of the transport channel which triggered the report; 2> if the transport channel type is "DCH" or "USCH": 3> include the IE "UL Transport Channel identity" and set it to the identity of the transport channel which triggered the report. 2> else: 3> not include the IE "UL Transport Channel identity". 2> set the IE "Traffic volume event identity" to the identity of the event that triggered the report; 2> if the IE "Tx interruption after trigger" for the event that triggered the report is included: 3> if the UE is in CELL_FACH state: 4> prohibit DTCH transmissions on the RACH; 4> if the Tx interruption timer is not running; or 4> if the Tx interruption timer is running and still has a value larger than the IE "Tx interruption after trigger" for the event, i.e. it was started earlier by another event with a larger value in IE "Tx interruption after trigger": 5> start the Tx interruption timer with the value in the IE "Tx interruption after trigger" for this event. 4> when it receives from the UTRAN a message causing the transition to CELL_DCH state; or 4> when the Tx interruption timer elapses: 5> stop the timer; 5> resume these transmissions. 1> if the IE "Traffic volume measurement object" is not included: 2> report on all the uplink transport channels as specified below.
3GPP
Release 6
1173
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the IE "Traffic volume measurement object" is included: 2> report on the uplink transport channels identified in this IE as specified below. 1> for each UM or AM RB mapped onto a transport channel on which the UE is expected to report: 2> add an element in the IE "Traffic volume measurement results"; 2> set the value of the IE "RB Identity" to the identity of the considered radio bearer; 2> if the RB is mapped onto one logical channel: 3> if the IE "RLC Buffer Payload for each RB" is set to TRUE: 4> include the IE "RLC Buffers Payload" and set it to the Buffer Occupancy value for this logical channel, rounded up to the next allowed value. 3> if the IE "Average of RLC Buffer Payload for each RB" is set to TRUE: 4> include and set the IE "Average of RLC Buffer Payload" to the Buffer Occupancy for this logical channel averaged over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]), rounded up to the next allowed value. 3> if the IE "Variance of RLC Buffer Payload for each RB" is set to TRUE: 4> include and set the IE "Variance of RLC Buffer Payload" to the variance of the Buffer Occupancy for this logical channel computed over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]), rounded up to the next allowed value. 2> if the RB is mapped onto two logical channels: 3> if one logical channel is mapped onto transport channels on which the UE is supposed to report: 4> if the IE "RLC Buffer Payload for each RB" is set to TRUE: 5> include and set the IE "RLC Buffers Payload" to the Buffer Occupancy value for this logical channel, rounded up to the next allowed value. 4> if the IE "Average of RLC Buffer Payload for each RB" is set to TRUE: 5> include and set the IE "Average of RLC Buffer Payload" to the Buffer Occupancy for this logical channel averaged over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]), rounded up to the next allowed value. 4> if the IE "Variance of RLC Buffer Payload for each RB" is set to TRUE: 5> include and set the IE "Variance of RLC Buffer Payload" to the variance of the Buffer Occupancy for this logical channel computed over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]), rounded up to the next allowed value. 3> if both logical channels are mapped onto transport channels on which the UE is supposed to report: 4> if the IE "RLC Buffer Payload for each RB" is set to TRUE: 5> include and set the IE "RLC Buffers Payload" to the sum of the Buffer Occupancy values for the two logical channels, rounded up to the next allowed value. 4> if the IE "Average of RLC Buffer Payload for each RB" is set to TRUE: 5> include and set the IE "Average of RLC Buffer Payload" to the sum of the Buffer Occupancy for the two logical channels averaged over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]) and rounded up to the next allowed value. 4> if the IE "Variance of RLC Buffer Payload for each RB" is set to TRUE:
3GPP
Release 6
1174
3GPP TS 25.331 V6.23.0 (2009-09)
5> include and set the IE "Variance of RLC Buffer Payload" to the variance of the sum of the Buffer Occupancy for the two logical channels, computed over the interval specified in the IE "Time Interval to take an average or a variance" (see [15]) and rounded up to the next allowed value.
14.4.2.1
Reporting event 4 A: Transport Channel Traffic Volume becomes larger than an absolute threshold
Transport Channel Traffic Volume Threshold
Time
Reporting event 4A
Reporting event 4A
Figure 14.4.2.1-1: Event triggered report when Transport Channel Traffic Volume becomes larger than a certain threshold If the monitored Transport Channel Traffic Volume (TCTV) [15] is larger than an absolute threshold at TVM setup or modify, or is larger at activation of the monitored transport channel, or becomes larger than an absolute threshold while the event is configured i.e. if TCTV>Reporting threshold, this event could trigger a report. The event could be triggered again only if TCTV becomes smaller than the Reporting threshold and later TCTV>Reporting threshold is verified again.
14.4.2.2
Reporting event 4 B: Transport Channel Traffic Volume becomes smaller than an absolute threshold
Transport Channel Traffic Volume
Threshold Time
Reporting event 4B
Reporting event 4B
Reporting event 4B
Figure 14.4.2.1-2: Event triggered report when Transport Channel Traffic Volume becomes smaller than certain threshold If the monitored Transport Channel Traffic Volume (TCTV) [15] is smaller than an absolute threshold at TVM setup or modify, or is smaller at activation of the monitored transport channel, or becomes smaller than an absolute threshold while the event is configured i.e. if TCTV<Reporting threshold, this event could trigger a report. The event could be
3GPP
Release 6
1175
3GPP TS 25.331 V6.23.0 (2009-09)
triggered again only if TCTV becomes bigger than the Reporting threshold and later TCTV<Reporting threshold is verified again.
14.4.3
Traffic volume reporting mechanisms
Traffic volume measurement triggering could be associated with both a time-to-trigger and a pending time after trigger. The time-to-trigger is used to get time domain hysteresis, i.e. the condition must be fulfilled during the time-to-trigger time before a report is sent. Pending time after trigger is used to limit consecutive reports when one traffic volume measurement report already has been sent and enables periodic reporting while the TCTV remains above(4a) or below(4b) the threshold. This is described in detail below.
14.4.3.1
Pending time after trigger
This timer is started in the UE when a measurement report has been triggered by a given event. The UE is then forbidden to send new measurement reports triggered by the same event during this time period. Instead the UE waits until the timer has expired. If the Transport Channel Traffic Volume [15] is still above the threshold for event 4a, or below the threshold for event 4b when the timer expires, the UE sends a new measurement report, and the timer is restarted. Otherwise it waits for a new triggering.
Short pending time after trigger
Transport Channel Traffic Volume Threshold Time
Long pending time after trigger
Time
Reporting event 4a
Reporting event 4a
Reporting event 4a
Figure 14.4.3.1-1: Pending time after trigger limits the amount of consecutive measurement reports Figure 14.4.3.1-1 shows that by increasing the pending time after trigger a triggered second event does not result in a measurement report. The figure assumes absence of the IE "Time to trigger".
14.4.3.2
Time-to-trigger
The timer is started in the UE when the Transport Channel Traffic Volume triggers the event. If the TCTV crosses the threshold before the timer expires, the timer is stopped. If the timer expires then a report is triggered.
3GPP
Release 6
1176
3GPP TS 25.331 V6.23.0 (2009-09)
Short time-to-trigger
Transport Channel Traffic Volume Threshold Time
Long time-to-trigger
Time
Report 1
No Report
Time-to-trigger
Time-to-trigger
Figure 14.4.3.1-2: Time-to-trigger is used to achieve time hysteresis Figure 14.4.3.1-2 shows that by increasing the time-to-trigger the report is not triggered.
14.4.4
Interruption of user data transmission
By including the IE "Tx Interruption after trigger", a UE in CELL_FACH state may be instructed by the UTRAN to prohibit transmission of user data on the RACH temporarily after a measurement report has been triggered. The UE shall only resume transmission of user data, when: 1> it receives from the UTRAN a message allocating a dedicated physical channel, leading to the transition to CELL_DCH state; or 1> the time period indicated by the IE "Tx Interruption after trigger" elapses. The transmission on signalling radio bearers shall not be interrupted.
14.5
14.5.1
Quality Measurements
Quality reporting measurement quantities
For quality measurements, the following measurement quantities are used: 1. Downlink transport channel BLER 2. Timeslot SIR (TDD only)
14.5.2
Quality reporting events
When one measurement identity corresponds to multiple quality events for the same transport channel, the UE behaviour is not specified.
14.5.2.1
Reporting event 5A: A predefined number of bad CRCs is exceeded
When this event is ordered by UTRAN in a measurement control message, the UE shall send a measurement report when the amount of bad CRCs during a predefined sliding window exceeds a predefined number. The following three parameters are used in the scheme: Total CRC = the length of the sliding window over which the number of bad CRCs are counted.
3GPP
Release 6
1177
3GPP TS 25.331 V6.23.0 (2009-09)
Bad CRC = the number of bad CRC that is required within the latest "Total CRC" received CRCs for the event to be triggered. Pending after trigger = a new event can not be triggered until "Pending after trigger" CRCs have been received,
When a DCH is established, the UE shall begin to count the number of bad CRCs within the last "Total CRC" received CRCs. No event can be triggered until at least "Total CRC" CRCs have been received. For each new received CRC, the UE shall compare the number of bad CRCs within the latest "Total CRC" received CRCs with the parameter "Bad CRC". An event shall be triggered if the number of bad CRCs is equal or larger than "Bad CRC". At the time when the event is triggered a pending time after trigger timer is started with the length of "Pending after trigger" CRCs. A new event can not be triggered until Pending after trigger" CRCs have been received. When Pending after trigger" CRCs have been received the event evaluation start again and a new event can be triggered.
Total CRC Total CRC Total CRC Total CRC
No reports Good CRC Bad CRC Pending after trigger Report 1 Report 2
No reports Report 3
Pending after trigger
Figure 14.5.2.1-1: Event triggered CRC error reporting
14.6
14.6.1
UE internal measurements
UE internal measurement quantities
For UE internal measurements the following measurement quantities exist: 1. UE transmission (Tx) power, for TDD measured on a timeslot basis. 2. UE received signal strength power (RSSI). 3. UE Rx-Tx time difference (FDD only). 4. TADV (1.28 Mcps TDD).
14.6.2
UE internal measurement reporting events
In the Measurement reporting criteria field in the Measurement Control messages, the UTRAN notifies the UE of which events should trigger a measurement report. UE internal measurement reporting events that can trigger a report are given below. The reporting events are marked with vertical arrows in the figures below. All events can be combined with time-to-trigger. NOTE: The reporting events are numbered 6A, 6B, 6C,.. where 6 denotes that the event belongs to the type UE internal measurements.
When one measurement identity corresponds to multiple internal events with identical event identities, the UE behaviour is not defined.
14.6.2.1
Reporting event 6A: The UE Tx power becomes larger than an absolute threshold
When a UE internal measurement configuring event 6a is set up, the UE shall:
3GPP
Release 6
1178
3GPP TS 25.331 V6.23.0 (2009-09)
1> create a variable TRIGGERED_6A_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Tx power (for TDD within a single TS) is greater than the value in IE "UE Transmitted Power Tx power threshold" stored for this event in the variable MEASUREMENT_IDENTITY for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6A_EVENT is set to FALSE: 3> set the variable TRIGGERED_6A_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6a"; 4> set the IE "measured results" and the IE "additional measured results" according to 8.4.2. 1> if the variable TRIGGERED_6A_EVENT is set to TRUE and if the UE Tx power (for TDD within a single TS) is less or equal the value in IE "UE Transmitted Power Tx power threshold" stored for this event in the variable MEASUREMENT_IDENTITY: 2> set the variable TRIGGERED_6A_EVENT to FALSE.
14.6.2.2
Reporting event 6B: The UE Tx power becomes less than an absolute threshold
When a UE internal measurement configuring event 6b is set up, the UE shall: 1> create a variable TRIGGERED_6B_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Tx power (for TDD within a single TS) is less than the value in IE "UE Transmitted Power Tx power threshold" stored for this event in the variable MEASUREMENT_IDENTITY for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6B_EVENT is set to FALSE: 3> set the variable TRIGGERED_6B_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6b"; 4> set the IE "measured results" and the IE "additional measured results" according to 8.4.2. 1> if the variable TRIGGERED_6B_EVENT is set to TRUE and if the UE Tx power (for TDD within a single TS) is greater or equal the value in IE "UE Transmitted Power Tx power threshold" stored for this event in the variable MEASUREMENT_IDENTITY: 2> set the variable TRIGGERED_6B_EVENT to FALSE.
3GPP
Release 6
1179
3GPP TS 25.331 V6.23.0 (2009-09)
UE Tx power
Tx power threshold 6A1 Tx power threshold 6B1
Tx power threshold 6A2 Tx power threshold 6B2

Reporting event 6A Reporting event 6B Reporting event 6B Reporting event 6A
Time
Figure 14.6.2.2-1: Event-triggered measurement reports when the UE Tx power becomes larger or less than absolute thresholds
14.6.2.3
Reporting event 6C: The UE Tx power reaches its minimum value
When a UE internal measurement configuring event 6c is set up, the UE shall: 1> create a variable TRIGGERED_6C_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Tx power is equal its minimum value (for TDD its minimum value on a single TS) for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6C_EVENT is set to FALSE: 3> set the variable TRIGGERED_6C_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6c"; 4> set the IE "measured results" and the IE "additional measured results" according to 8.4.2. 1> if the variable TRIGGERED_6C_EVENT is set to TRUE and if the UE Tx power is greater than its minimum value: 2> set the variable TRIGGERED_6C_EVENT to FALSE.
3GPP
Release 6
1180
3GPP TS 25.331 V6.23.0 (2009-09)
UE Tx power
Minimum UE Tx power
Reporting event 6C
Time
Figure 14.6.2.3-1: Event-triggered measurement report when the UE Tx power reaches its minimum value
14.6.2.4
Reporting event 6D: The UE Tx power reaches its maximum value
When a UE internal measurement configuring event 6d is set up, the UE shall: 1> create a variable TRIGGERED_6D_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Tx power equals the maximum UE TX power (for TDD its maximum value on a single TS) for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6D_EVENT is set to FALSE: 3> set the variable TRIGGERED_6D_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6d"; 4> set the IE "measured results" and the IE "additional measured results" according to 8.4.2. 1> if the variable TRIGGERED_6D_EVENT is set to TRUE and if the UE Tx power is less than the maximum UE TX power: 2> set the variable TRIGGERED_6D_EVENT to FALSE. NOTE: The maximum UE TX power is defined in subclause 8.6.6.8.
3GPP
Release 6
1181
3GPP TS 25.331 V6.23.0 (2009-09)
UE Tx power
Maximum UE Tx power
Reporting event 6D
Time
Figure 14.6.2.4-1: Event-triggered report when the UE Tx power reaches its maximum value
14.6.2.5
Reporting event 6E: The UE RSSI reaches the UE's dynamic receiver range
When a UE internal measurement configuring event 6e is set up, the UE shall: 1> create a variable TRIGGERED_6E_EVENT related to that measurement, which shall initially be set to FALSE; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE RSSI is greater or equal the UE's dynamic receiver range for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6E_EVENT is set to FALSE: 3> set the variable TRIGGERED_6E_EVENT to TRUE; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6e"; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2. 1> if the variable TRIGGERED_6E_EVENT is set to TRUE and if the UE RSSI is less than the UE's dynamic receiver range: 2> set the variable TRIGGERED_6E_EVENT to FALSE.
14.6.2.6
Reporting event 6F (FDD): The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold
When a UE internal measurement configuring event 6f is set up, the UE shall: 1> create a variable TRIGGERED_6F_EVENT related to that measurement, which shall initially be set to FALSE for each RL; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Rx-Tx time difference for a RL included in the active set is greater than the value in the IE "UE Rx-Tx time difference threshold" stored for this event in the variable MEASUREMENT_IDENTITY for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6F_EVENT is set to FALSE for this RL:
3GPP
Release 6
1182
3GPP TS 25.331 V6.23.0 (2009-09)
3> set the variable TRIGGERED_6F_EVENT to TRUE for this RL; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6f"; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2. 1> if the variable TRIGGERED_6F_EVENT is set to TRUE for a RL and if the UE RX-Tx time difference for this RL included in the active set is less than or equal to the value in the IE "UE Rx-Tx time difference threshold" stored for this event in the variable MEASUREMENT_IDENTITY: 2> set the variable TRIGGERED_6F_EVENT to FALSE for this RL.
14.6.2.6a
Reporting event 6F (1.28 Mcps TDD): The time difference indicated by TADV becomes larger than an absolute threshold
When a UE internal measurement configuring event 6f is set up, the UE shall: 1> create a variable TRIGGERED_6F_EVENT related to that measurement, which shall initially be set to the currently measured TADV; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the absolute value of the difference between the measured TADV and the TADV stored in the variable TRIGGERED_6F_EVENT is greater than the predefined threshold configured with the IE "TADV Threshold" for this event in the variable MEASUREMENT_IDENTITY for a time period indicated by the IE "time_to_trigger": 2> set the variable TRIGGERED_6F_EVENT to the currently measured TADV; 2> send a measurement report with IEs set as below: 3> set the IE "TADV" to the measured value, and the IE "SFN" to the SFN during which the latest measurement was performed, in the IE "TADV Info"; 3> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2.
14.6.2.7
Reporting event 6G: The UE Rx-Tx time difference for a RL included in the active set becomes less than an absolute threshold
When a UE internal measurement configuring event 6g is set up, the UE shall: 1> create a variable TRIGGERED_6G_EVENT related to that measurement, which shall initially be set to FALSE for each RL; 1> delete this variable when the measurement is released. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE Rx-Tx time difference for a RL included in the active set is less than the value in IE "UE Rx-Tx time difference threshold" stored for this event in the variable MEASUREMENT_IDENTITY for a time period indicated by the IE "time_to_trigger": 2> if the variable TRIGGERED_6G_EVENT is set to FALSE for this RL: 3> set the variable TRIGGERED_6G_EVENT to TRUE for this RL; 3> send a measurement report with IEs set as below: 4> set in "UE internal measurement event results": "UE internal event identity" to "6g"; 4> set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2.
3GPP
Release 6
1183
3GPP TS 25.331 V6.23.0 (2009-09)
1> if the variable TRIGGERED_6G_EVENT is set to TRUE for a RL and if the UE RX-Tx time difference for this RL included in the active set is greater or equal the value in IE "UE Rx-Tx time difference threshold" stored for this event in the variable MEASUREMENT_IDENTITY: 2> set the variable TRIGGERED_6G_EVENT to FALSE for this RL.
14.7
14.7.1
UE positioning measurements
UE positioning measurement quantities
The quantity to measure for UE positioning is dependent on the positioning method and the method type requested in the IE "UE positioning reporting quantity". 1 SFN-SFN observed time difference type 2, optional. 2 Rx-Tx time difference type 2, optional. 3 GPS timing of cell fames, optional. The definition of other GPS measurements is not within the scope of this specification.
14.7.2 14.7.3
Void UE positioning reporting events
In the IE "UE positioning reporting criteria" in the Measurement Control messages, the UTRAN notifies the UE of which events should trigger a measurement report. UE positioning reporting events that can trigger a report are given below. The content of the measurement report is dependant on the positioning method and method type requested in the IE "UE positioning reporting quantity" of the Measurement Control message and is described in detail in [18]. When one measurement identity corresponds to multiple positioning events with identical event identities, the UE behaviour is not defined.
14.7.3.1
Reporting Event 7a: The UE position changes more than an absolute threshold
This event is used for UE-based methods only. When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> if the UE changes its position compared to the last reported position by more than the threshold defined by the IE "Threshold position change"; or 1> if no position has been reported since the event was configured and the UE changes its position compared to the first position estimate obtained after the event was configured by more than the threshold defined by the IE "Threshold position change": 2> send a measurement report as specified in subclause 8.6.7.19.1b; 2> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is greater than zero: 3> decrease IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event by one. 2> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is equal to zero: 3> delete this event from the list of events in variable MEASUREMENT_IDENTITY. 1> if the UE is unable to evaluate the event because a position measurement is not available: 2> not send a report.
3GPP
Release 6
1184
3GPP TS 25.331 V6.23.0 (2009-09)
14.7.3.2
Reporting Event 7b: SFN-SFN measurement changes more than an absolute threshold
When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> send a measurement report when the SFN-SFN time difference measurement type 2 of any measured cell changes more than the threshold defined by the IE "Threshold SFN-SFN change"; and 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE-based": 2> act as specified in subclause 8.6.7.19.1b. 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE-assisted": 2> act as specified in subclause 8.6.7.19.1a. 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE-assisted preferred but UE-based allowed" or "UE-based preferred but UE-assisted allowed": 2> the UE may choose to act according to either subclause 8.6.7.19.1a or 8.6.7.19.1b. 1> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is greater than zero: 2> decrease IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event by one. 1> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is equal to zero: 2> delete this event from the list of events in variable MEASUREMENT_IDENTITY.
14.7.3.3
Reporting Event 7c: GPS time and SFN time have drifted apart more than an absolute threshold
When this event is ordered by UTRAN in a measurement control message, the UE shall: 1> send a measurement report when the GPS Time Of Week and the SFN timer have drifted apart more than the threshold defined by the IE "Threshold SFN-GPS TOW"; and 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE based": 2> act as specified in subclause 8.6.7.19.1b. 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE assisted": 2> act as specified in subclause 8.6.7.19.1a. 1> if UTRAN set IE "Method Type" in "UE positioning reporting quantity" in the MEASUREMENT CONTROL message to "UE assisted preferred but UE based allowed" or "UE based preferred but UE assisted allowed": 2> act as specified in subclause 8.6.7.19.1a or in subclause 8.6.7.19.1b depending on the method type chosen by the UE. 1> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is greater than zero: 2> decrease IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event by one. 1> if the value of IE "Amount of Reporting" in variable MEASUREMENT_IDENTITY for this event is equal to zero: 2> delete this event from the list of events in variable MEASUREMENT_IDENTITY.
3GPP
Release 6
1185
3GPP TS 25.331 V6.23.0 (2009-09)
14.8
Void
14.9
14.9.1
Downlink power control

Generalities
This function is implemented in the UE in order to set the SIR target value on each CCTrCH used for the downlink power control. This SIR value shall be adjusted according to an autonomous function in the UE in order to achieve the same measured quality as the quality target set by UTRAN. The quality target is set as the transport channel BLER value for each transport channel as signalled by UTRAN. When transport channel BLER is used the UE shall run a quality target control loop such that the quality requirement is met for each transport channel, which has been assigned a BLER target. The UE shall set the SIR target when the physical channel has been set up or reconfigured. It shall not increase the SIR target value before the power control has converged on the current value. The UE may estimate whether the power control has converged on the current value, by comparing the averaged measured SIR to the SIR target value. NOTE: The power control function for F-DPCH is specified in [29].
14.9.2
Downlink power control in compressed mode
In compressed mode, the target SIR needs to be changed in several frames compared to normal mode. For this purpose, four values DeltaSIR1, DeltaSIRafter1, DeltaSIR2 and DeltaSIRafter2 are signalled by the UTRAN to the UE (see subclause 10.2.9). For each frame, the target SIR offset during compressed mode, compared to normal mode is: SIR = max (SIR1_compression, , SIRn_compression) + SIR1_coding + SIR2_coding where n is the number of TTI lengths for all TrChs of the CCTrCh, Fi is the length in number of frames of the i-th TTI and where SIR_coding fulfils: SIR1_coding= DeltaSIR1 if the start of the first transmission gap in the transmission gap pattern is within the current frame. SIR1_coding= DeltaSIRafter1 if the current frame just follows a frame containing the start of the first transmission gap in the transmission gap pattern. SIR2_coding= DeltaSIR2 if the start of the second transmission gap in the transmission gap pattern is within the current frame. SIR2_coding= DeltaSIRafter2 if the current frame just follows a frame containing the start of the second transmission gap in the transmission gap pattern. SIR1_coding= 0 and SIR2_coding= 0 otherwise.
and SIRi_compression is defined by : SIRi_compression = 3 dB for downlink frames compressed by reducing the spreading factor by 2. SIRi_compression = 0 dB in all other cases.
Several compressed mode patterns applying to the same frames should be avoided as much as possible. In case several compressed mode patterns are used simultaneously, a SIR offset is computed for each compressed mode pattern and the sum of all SIR offsets is applied to the frame.
3GPP
Release 6
1186
3GPP TS 25.331 V6.23.0 (2009-09)
14.10
Calculated Transport Format Combination
The Calculated Transport Format Combination (CTFC) is a tool for efficient signalling of transport format combinations. Let I be the number of transport channels that are included in the transport format combination. For DCHs, all configured DCHs are included in the transport format combination. Each transport channel TrCHi, i = 1, 2, , I, has Li transport formats, i.e. the transport format indicator TFIi can take Li values, TFI i {0,1,2,..., Li 1} . Define
Pi = L j , where i = 1, 2, , I, and L0 = 1.
j =0
i 1
Let TFC(TFI1, TFI2, , TFII) be the transport format combination for which TrCH1 has transport format TFI1, TrCH2 has transport format TFI2, etc. The corresponding CTFC(TFI1, TFI2, , TFII) is then computed as:
CTFC (TFI1 , TFI 2 ,K, TFI I ) = TFI i Pi .

i =1
For FACH and PCH transport channels, "TrCH1" corresponds to the transport channel listed at the first position in IE "FACH/PCH information" in IE "Secondary CCPCH System Information", "TrCH2" corresponds to the transport channel listed at the second position in IE "FACH/PCH information" and so on. For all other transport channels in FDD and for all configured transport channels of the same transport channel type (i.e. DCH, DSCH, USCH) in TDD, "TrCH1" corresponds to the transport channel having the lowest transport channel identity in the transport format combination mapped to the TFCI field. "TrCH2" corresponds to the transport channel having the next lowest transport channel identity, and so on.
14.10.1 Default TFCS for MBMS

14.10.1.1 S-CCPCH configuration including a FACH carrying MSCH
In case the S-CCPCH configuration includes a FACH carrying MSCH, the default TFCS is defined according to the following: Let TrCH 1 be the FACH carrying MSCH, TrCH 2 be the first TrCH carrying MTCH listed in the IE "TrCh information list", TrCH 3 be the second TrCH carrying MTCH listed in the IE "TrCh information list" etc. and let TrCH I be the last TrCH carrying MTCH listed in the IE "TrCh information list". Each transport channel TrCHi, i = 1, 2, , I, has Li transport formats, i.e. the transport format indicator TFIi can take Li values. Each transport format combination set is defined by the transport formats of each transport channel mapped on this SCCPCH: TFC = (TFI1, TFI2, , TFII). The "MBMS implicit TFCS" contains then the following set of TFCs: TFCS = {(0,0,,0),(0,1,,0),,(0,L2,,0),(0,0,1,,0),,(0,0,L3,,0),,(0,0,0,,1),,(0,0,0,,LI), (1,0,,0),(1,1,,0),,(1,L2,,0),(1,0,1,,0),,(1,0,L3,,0),,(1,0,0,,1),,(1,0,0,,LI), (2,0,,0),,(L1,0,,0)}
14.10.1.2
S-CCPCH configuration not including a FACH carrying MSCH
In case the S-CCPCH configuration does not include a FACH carrying MSCH, the default TFCS is defined according to the following: Let TrCH 1 be the first TrCH listed in the IE "TrCh information list", TrCH 2 be the second TrCH listed in the IE "TrCh information list" etc. and let TrCH I be the last TrCH listed in the IE "TrCh information list".
3GPP
Release 6
1187
3GPP TS 25.331 V6.23.0 (2009-09)
Each transport channel TrCHi, i = 1, 2, , I, has Li transport formats, i.e. the transport format indicator TFIi can take Li values. Each transport format combination set is defined by the transport formats of each transport channel mapped on this SCCPCH: TFC = (TFI1, TFI2, , TFII). The "MBMS implicit TFCS" contains then the following set of TFCs: TFCS = {(0,,0), (1,,0),,(L1,,0),(0,1,,0),,(0,L2,,0),,(0,0,,1),,(0,0,,LI)}
14.11
UE autonomous update of virtual active set on non-used frequency (FDD only)
In the text that follows: a "non-used frequency" is a frequency that the UE has been ordered to measure upon but is not used for the connection. A "used frequency" is a frequency that the UE has been ordered to measure upon and is also currently used for the connection; a "non-used frequency (resp. cell) considered in an inter-frequency measurement" shall be understood as a nonused frequency (resp. cell) included in the list of cells pointed at in the IE "cells for measurement" if it was received for that measurement, or otherwise as a non-used frequency (resp. cell) included in the "Inter-frequency cell info" part of the variable CELL_INFO_LIST.
For event-triggered inter frequency measurements it is possible to use intra-frequency measurement reporting events for support of maintenance of an active set associated with a non-used frequency considered in that measurement, a "virtual active set" and used in the evaluation of the frequency quality estimates. The "initial virtual active set" for a frequency is the virtual active set that is associated to that frequency just after a message was received that sets up or modifies the inter-frequency measurement. The way the virtual active sets are initiated and updated for the non-used frequencies considered in an inter-frequency measurement is described in the two subclauses below. The UE shall support a single virtual active set per non-used frequency. The virtual active set is not initialised and maintained for an inter frequency measurement with periodic reporting. A virtual active set initialised and maintained by another inter-frequency measurement does not affect reporting of the periodic inter-frequency measurement.
14.11.1 Initial virtual active set

If the UE receives a MEASUREMENT CONTROL message that sets up or modifies an inter-frequency measurement and includes the IE "Inter-frequency set update"; or If at least one cell can be measured on a non-used frequency for which the current virtual active set is empty (see subclause 14.11.2), the UE shall: 1> for each non-used frequency Fi considered in the measurement where cells can be measured: 2> if event 1a is configured for the used frequency in an intra-frequency measurement: 3> include in the initial virtual active set the Ni cells that have either the greatest downlink Ec/N0 or the greatest downlink RSCP after despreading or the lowest pathloss (the measurement quantity to be used is determined by the IE "intra-frequency measurement quantity" of the intra-frequency measurement from which the event 1a configuration is taken), among the cells on frequency Fi considered in that interfrequency measurement, where:
Ni =min(N1a , NCells Fi) if N1a0 and Ni = NCells Fi otherwise.
3GPP
Release 6
1188
3GPP TS 25.331 V6.23.0 (2009-09)
where:
N1a is the "Reporting deactivation threshold" included in the intra-frequency measurement for the first event 1a defined in the intra-frequency measurement with the lowest identity at the time the interfrequency measurement was received with the IE "Inter-frequency set update" present. NCells Fi is the number of cells on frequency Fi considered in that inter-frequency measurement.
2> else:
Ni = NCells Fi
where:
NCells Fi is the number of cells on frequency Fi considered in that inter-frequency measurement.

NOTE1: The UE initialises the virtual active set with up to the maximum number of inter-frequency cells supported by the UE as defined in [19]. NOTE2: If the UTRAN configures more than one measurement using events 2A, 2B, 2C or 2E the UE measurement capabilities may be exceeded due to the necessary copying of 1A, 1B, 1C criteria. To avoid this the UTRAN may configure one measurement to apply to multiple frequencies so that the 1A, 1B, and 1C criteria will only be copied once. NOTE3: After a hard handover (see subclause 8.3.5), if the MEASUREMENT CONTROL message that restarts an inter-frequency measurement using the virtual active set does not include the IE "Inter-frequency set update", the UE behaviour regarding the virtual active set is not specified.
14.11.2 Virtual active set update during an inter-frequency measurement

For an inter-frequency measurement, the UE shall: 1> apply the events of type 1a, 1b and 1c that were defined for the used frequency in other stored measurements of type "intra-frequency" at the time the inter-frequency measurement was last received with the IE "Interfrequency set update" present; and 1> update the virtual active set for the non-used frequencies considered in that measurement according to the following rules: 2> if several events of type 1a (resp. 1b,1c) were defined for the used frequency when the inter-frequency measurement was last received with the IE "Inter-frequency set update" present, only the first 1a event (resp 1b, 1c) that was defined in the measurement with the lowest measurement identity shall apply to the non-used frequencies; 2> all the cells considered in the inter-frequency measurements shall be able to affect the reporting range for event 1a and 1b. (i.e. the IE "Cells forbidden to affect reporting range" possibly stored for the intra-frequency measurements on the used frequency does not apply to the non-used frequencies considered in the interfrequency measurement); 2> the IEs "amount of reporting" and "reporting interval" that were stored for the intra-frequency measurements on the used frequency shall not be considered if reports of the virtual active set updates are needed. 2> the measurement quantity and filter coefficient to be used is determined by the IE "intra-frequency measurement quantity" of the intra-frequency measurement from which the intra-frequency event configuration configuration is taken. NOTE: If the measurement quantity and filter coefficients to be used differ for the 1a, 1b, and 1c events applied then the UE behaviour is unspecified.
1> if event 1a is applicable to the non-used frequencies considered in the inter-frequency measurement, always only consider monitored cells that are not in the virtual active set for this event, and: 2> when this event is triggered (according to the criteria described in subclause 14.1.2.1) by a cell for a non-used frequency considered in that measurement:
3GPP
Release 6
1189
3GPP TS 25.331 V6.23.0 (2009-09)
3> if the "Reporting deactivation threshold" is equal to 0, or if the "Reporting deactivation threshold" is different from 0 and the number of cells included in the virtual active set for that frequency is less than or equal to the "Reporting deactivation threshold": 4> add the primary CPICH that enters the reporting range to the "virtual active set". 2> if event 1b is applicable for the non-used frequencies considered in that inter-frequency measurement, always only consider cells in the virtual active set for this event, and when this event is triggered (according to the criteria described in subclause 14.1.2.2) by a cell for a non-used frequency considered in that measurement: 3> if the number of cells included in the virtual active set is greater than 1: 4> remove the primary CPICH that leaves the reporting range from the "virtual active set". 2> if event 1c is applicable for the non-used frequencies considered in that inter-frequency measurement, always only consider monitored cells for this event, and when this event is triggered (according to the criteria described in subclause 14.1.2.3) by a cell for a non-used frequency considered in that measurement: 3> if the "Reporting activation threshold" is equal to 0, or if the "Reporting activation threshold" is different from 0 and the number of cells included in the virtual active set for that frequency is greater than or equal to the "Reporting activation threshold": 4> rank all active and non-active primary CPICHs and take the n best cells to create a new "virtual active set", where n is the number of active primary CPICHs in the "virtual active set". 1> if Event 1a is not defined for the used frequency in other stored measurements of type "intra-frequency" at the time the inter-frequency measurement was set up: 2> the UE shall continuously update the virtual active set to consist of all cells on frequency Fi considered in that inter-frequency measurement. NOTE: The UE needs to only update the virtual active set with up to the maximum number of interfrequency cells supported by the UE as defined in [19].
If none of the cells that are considered in the measurement on this frequency were measured, the UE may treat the virtual active set as empty and follow the appropriate initialisation procedured in subclause 14.11.1 when any relevant cell can first be measured. If a cell is a member of the virtual active set and is removed from the variable CELL_INFO_LIST or removed from the list of cells pointed at by the IE "Cells for measurement" for the inter-frequency measurement then the UE shall remove the cell from the virtual active set. If an inter-frequency measurement that initialised a virtual active set is released, then any virtual active set associated with this measurement shall also be released.
14.12
Provision and reception of RRC information between network nodes
14.12.0 General
In certain cases, e.g., when performing handover to UTRAN or when performing SRNC relocation, RRC information may need to be transferred between UTRAN nodes, between UTRAN and another RAT, between nodes within another RAT or between the UE and another RAT. The RRC information exchanged between network nodes or between the UE and another RAT is typically transferred by means of RRC information containers. An RRC information container is a self-contained and extensible RRC information unit that may be used to transfer a number of different RRC messages, one at a time. As stated before, RRC information containers may be used to transfer RRC messages across interfaces other than the Uu interface. The RRC messages that may be included in RRC information containers have similar characteristics as the RRC messages that are transferred across the Uu interface.
3GPP
Release 6
1190
3GPP TS 25.331 V6.23.0 (2009-09)
The RRC messages that are sent to/ from the UE, e.g., HANDOVER TO UTRAN COMMAND, INTER RAT HANDOVER INFO are covered by (sub)clauses 8, 9, 10, 11.0-11.4 and 12 of this specification. The following subclauses concern RRC messages exchanged between network nodes. In future versions of this specification, it is possible to extend the RRC messages transferred across interfaces other than Uu. For these RRC messages the same extension mechanism applies as defined for RRC messages transferred across the Uu interface, as is specified in subclause 10.1, i.e., both critical and non-critical extensions may be added. The transfer syntax for RRC information containers and RRC messages transferred between network nodes is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned (X.691). It should be noted that the encoder adds final padding to achieve octet alignment. The resulting octet string is, carried in a container, transferred between the network nodes. When using a separate RRC information container for each endpoint, the receiving RRC protocol entity is able to interpret the received container; this means that the receiver need not take into account information about the (network interface) message used in transferring the container. The following encoding rules apply in addition to what has been specified in X.691 [49]: 1> When a bit string value is placed in a bit-field as specified in 15.6 to 15.11 in [11], the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field.
NOTE: The terms "leading bit" and "trailing bit" are defined in ITU-T Rec. X.680 | ISO/IEC 8824-1. When using the "bstring" notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right.
14.12.0a General error handling for RRC messages exchanged between network nodes
The error handling for RRC messages that are exchanged between network nodes applies the same principles as defined for other RRC messages. Although the same principles apply for network nodes receiving unknown, unforeseen and erroneous RRC messages received in RRC information containers, the notification of the error should be done in a different manner, as specified in the following: The network node receiving an invalid RRC message from another network node should: 1> if the received RRC message was unknown, unforeseen or erroneous: 2> prepare an RRC FAILURE INFO message, including the IE "Failure cause" set to "Protocol error" and the IE "Protocol error information" including an IE "Protocol error cause" which should be set as follows: 3> to "ASN.1 violation or encoding error" upon receiving an RRC message for which the encoded message does not result in any valid abstract syntax value; 3> to "Message type non-existent or not implemented" upon receiving an unknown RRC message type; 3> to "Message extension not comprehended" upon receiving an RRC message including an undefined critical message extension; 3> to "Information element value not comprehended" upon receiving an RRC message including an mandatory IE for which no default value is defined and for which either the value is set to spare or for which the encoded IE does not result in a valid transfer syntax. The same applies for conditional IEs, for which the conditions for presence are met, the IE is present but has a value set to spare or for which the encoded IE does not result in a valid transfer syntax; 3> to "Information element missing" upon receiving an RRC information container with an absent conditional IE for which the conditions for presence are met. 1> if there was another failure to perform the operation requested by the received RRC message:
3GPP
Release 6
1191
3GPP TS 25.331 V6.23.0 (2009-09)
2> prepare an RRC FAILURE INFO message, including the IE "Failure cause" set to a value that reflects the failure cause. 1> send the RRC FAILURE INFO message to the network node from which the invalid RRC protocol information was received. NOTE 1: The appropriate (failure) messages used across the network interfaces may not support the inclusion of a RRC information container. In this case, the information contained in the RRC FAILURE INFO message may need to be transferred otherwise e.g. by mapping to a cause value (e.g. a cause value in the RRHANDOVER FAILURE message when there is a error associated with the RRC-HANDOVER TO UTRAN COMMAND message). NOTE 2 In case the RRC procedure used to perform SRNS relocation fails e.g. due to non comprehension, the source RNC may notify the target RNC by including the diagnostics information (IEs "Protocol error" and "Protocol error information") in the "RRC message "SRNS Relocation" Info sent in the RRC information container" used for a subsequent relocation request.
14.12.1 RRC Information to target RNC

The RRC information container "RRC Information to target RNC" may either be sent from source RNC or from another RAT. In case of handover to UTRAN, this information originates from another RAT, while in case of SRNC relocation the RRC information originates from the source RNC. In case of handover to UTRAN, the RRC information transferred may provide UTRAN specific information, as defined in the INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES message, that the target RNC needs when preparing the handover command message. In case of SRNC relocation and handover/cell reselection from GERAN Iu mode, the RRC information transferred specifies the configuration of RRC and the lower layers it controls, e.g., including the radio bearer and transport channel configuration. It is used by the target RNC to initialise RRC and the lower layer protocols to facilitate SRNC relocation and handover/cell reselection from GERAN Iu mode in a manner transparent to the UE. RFC 3095 CONTEXT INFO is used to transfer the compressor and decompressor context information of the RFC 3095 protocol from source RNC to target RNC.
Information Element/Group Name CHOICE case Need MP Multi Type and reference Semantics description At least one spare choice, Criticality: Reject, is needed Version
>Handover to UTRAN
>SRNC relocation
>RFC 3095 context info
INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITI ES 14.12.4.1 SRNS RELOCATIO N INFO 14.12.4.2 RFC 3095 CONTEXT INFO 14.12.4.4
REL-5
14.12.2 RRC information, target RNC to source RNC

There are 2 possible cases for RNC relocation: 1. The UE is already under control of target RNC; and 2. The SRNC Relocation with Hard Handover (UE still under control of SRNC), but UE is moving to a location controlled by the target RNC (based on measurement information).
3GPP
Release 6
1192
3GPP TS 25.331 V6.23.0 (2009-09)
In case 1 the relocation is transparent to the UE and there is no "reverse" direction container. The SRNC just assigns the 'serving' function to the target RNC, which then becomes the Serving RNC. In case 2 the relocation is initiated by SRNC, which also provides the RRC Initialisation Information to the target RNC. Base on this information, the target RNC prepares the Hard Handover Message ( "Physical channel reconfiguration" (subclause 8.2.6), "radio bearer establishment" (subclause 8.2.1), "Radio bearer reconfiguration" (subclause 8.2.2), "Radio bearer release" (subclause 8.2.3) or "Transport channel reconfiguration" (subclause 8.2.4). In case 2 two possibilities are defined in order to transmit the relocation message from the target RNC to the source RNC which can be chosen by the source RNC by including or not including the IE "RB Id for handover message" in the IE "SRNS Relocation Info". In case the IE "RB Id for handover message" has been received by the target RNC in the IE "SRNS Relocation Info", the target RNC should choose the IE "DL DCCH message" and include the DL DCCH message that should be transmitted transparently to the UE by the source RNC. In that case, the target RNC is integrity protecting the message if applicable. If the target RNC did not receive the IE "RB Id for handover message" in the IE "SRNS Relocation Info" the target RNC should use another choice. In that case, the source RNC should integrity protect the message before transmitting it to the UE if applicable. The source RNC then transmits the Handover Message to the UE, which then performs the handover. In the successful case, the UE transmits an XXX COMPLETE message, using the new configuration, to the target RNC. In case of failure, the UE transmits an XXX FAILURE, using the old configuration, to the source RNC and the RRC context remains unchanged (has to be confirmed and checked with the SRNS relocation procedure).
Information Element/Group name CHOICE RRC message >RADIO BEARER SETUP Need MP RADIO BEARER SETUP 10.2.31 RADIO BEARER RECONFIG URATION 10.2.25 RADIO BEARER RELEASE 10.2.28 TRANSPOR T CHANNEL RECONFIG URATION 10.2.51 PHYSICAL CHANNEL RECONFIG URATION 10.2.20 RRC FAILURE INFO 10.2.41 a OCTET STRING Multi Type and reference Semantics description At least one spare choice, Criticality: Reject, is needed
>RADIO BEARER RECONFIGURATION
>RADIO BEARER RELEASE
>TRANSPORT CHANNEL RECONFIGURATION
>PHYSICAL CHANNEL RECONFIGURATION
>RRC FAILURE INFO
>DL DCCH message
3GPP
Release 6
1193
3GPP TS 25.331 V6.23.0 (2009-09)
14.12.3 Void
14.12.4 RRC messages exchanged between network nodes

14.12.4.0 HANDOVER TO UTRAN COMMAND
This RRC message is sent between network nodes to transfer the actual handover command including the details of the radio configuration to be used upon handover to UTRAN as compiled by the target RNC. Direction: target RNC source RAT The message is exactly the same as the HANDOVER TO UTRAN COMMAND defined in subclause 10.2.16a.
14.12.4.0a
INTER RAT HANDOVER INFO
This RRC message is sent between network nodes to transfer information relevant for the target RNC when preparing for handover to UTRAN. Direction: source RNC/RATtarget RAT The message is exactly the same as the INTER RAT HANDOVER INFO defined in subclause 10.2.16d
14.12.4.1
INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES
This RRC message is sent between network nodes when preparing for an inter RAT handover to UTRAN. Direction: source RATtarget RNC
Information Element/Group Name UE Information elements Predefined configuration status information Need Multi Type and reference Predefined configuration status information 10.3.4.5a Predefined configuration status information compressed 10.3.4.5b UE security information 10.3.3.42b UE security information2 10.3.3.42c UE Specific Behaviour Information 1 interRAT 10.3.3.52 UE radio access capability 10.3.3.42 UE radio access capability extension Semantics description
OP
OP
REL-5
OP
OP
REL-6
OP
This IE shall not be included in this version of the protocol
UE capability container >UE radio access capability
OP MP
MP
Although this IE is not always required, the need has been set to MP to align with the ASN.1
3GPP
Release 6 Information Element/Group Name UE radio access capability compressed Need
1194 Multi Type and reference 10.3.3.42a UE radio access capability compressed 10.3.3.42o UE radio access capability comp 2 10.3.3.42oa
OP
REL-5
UE radio access capability comp 2
OP
REL-6
Other Information elements UE system specific capability
OP
1 to <maxSyste mCapabilit y> Inter-RAT UE radio access capability 10.3.8.7 Failure cause 10.3.3.13 Protocol error information 10.3.8.12
MP
Failure cause
OP
Diagnostics information related to an earlier handover to UTRAN request
CV-ProtErr
Condition ProtErr
Explanation This IE is mandatory present if the IE "Protocol error indicator" is included and has the value "TRUE". Otherwise it is not needed.
NOTE1: To facilitate that network nodes can transparently forward the RRC information received, the INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES should include the entire INTER RAT HANDOVER INFO message. The network node, which may not be able to decode the information received, may only append some information to what was received. NOTE2: The above table does not need to reflect the order of the information elements in the actual encoded message. The order, that is reflected in the ASN.1, should be chosen in a manner that avoids that network nodes need to perform reordering of information elements.
14.12.4.2
SRNS RELOCATION INFO
This RRC message is sent between network nodes when preparing for an SRNS relocation or a handover/cell reselection from GERAN Iu mode. With the presence or absence of the IE "RB identity for Hard Handover message" the source RNC indicates to the target SRNC whether the source RNC expects to receive the choice "DL DCCH message" in the IE "RRC information, target RNC to source RNC" in case the SRNS relocation is of type "UE involved". Furthermore the target RNC uses this information for the calculation of the MAC-I. Direction: source RNC/RATtarget RNC
Information Element/Group Name Non RRC IEs >RB identity for Handover message Need Multi Type and reference RB identity 10.3.4.16 Semantics description Version
OP
Gives the id of the radio bearer on which the source RNC will transmit the RRC message in the case the relocation is of
3GPP
Release 6 Information Element/Group Name Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description type "UE involved". In handover from GERAN Iu mode this IE is always set to 2. Version
>State of RRC
MP
>State of RRC procedure
MP
RRC state indicator, 10.3.3.35a Enumerated (await no RRC message, await RB Release Complete, await RB Setup Complete, await RB Reconfigurat ion Complete, await Transport CH Reconfigurat ion Complete, await Physical CH Reconfigurat ion Complete, await Active Set Update Complete, await Handover Complete, send Cell Update Confirm, send URA Update Confirm, , others) <1 to maxCNDo mains> CN domain identity 10.3.1.1 Enumerated( Not started, Started) START 10.3.3.38 CN domain identity 10.3.1.1
Ciphering related information >Ciphering status for each CN domain >>CN domain identity
MP
MP
>>Ciphering status
MP
>>START >Latest configured CN domain
MP MP
START value to be used in this CN domain. Value contained in the variable of the same name. In case this variable is empty, the source RNC can set any CN domain identity. In that case, the Ciphering status and the Integrity protection status should be Not started and the target RNC should not initialise the variable Latest configured
3GPP
Release 6 Information Element/Group Name >Calculation time for ciphering related information Need
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description CN domain. Time when the ciphering information of the message were calculated, relative to a cell of the target RNC. In handover and cell reselection from GERAN Iu mode this field is not present. Identity of one of the cells under the target RNC and included in the active set of the current call Version
CVCiphering
>>Cell Identity
MP
Cell Identity 10.3.2.2
>>SFN >COUNT-C list
MP OP 1 to <maxCNdo mains>
Integer(0..40 95) COUNT-C values for radio bearers using transparent mode RLC CN domain identity 10.3.1.1 Bit string(32) 1 to <maxRB> RB identity 10.3.4.16 Bit string(20..25 ) Bit String(7) Bit string(20..25 ) For signalling radio bearers this IE is mandatory.
MP
>>COUNT-C >Ciphering info per radio bearer >>RB identity >>Downlink HFN
MP OP MP MP
>>Downlink SN >>Uplink HFN
CV-SRB1 MP
This IE is either RLC AM HFN (20 bits) or RLC UM HFN (25 bits) VT(US) of RLC UM This IE is either RLC AM HFN (20 bits) or RLC UM HFN (25 bits)
Integrity protection related information >Integrity protection status
MP
Enumerated( Not started, Started) 4 to <maxSRBs etup> Bit string (28) For each SRB, in the case activation times for the next IP configuration to be applied on this SRB have already been reached this IE corresponds to the last value used. Else this value corresponds to the value the source would have initalized the HFN to at the activation time, not considering any increment of HFN due to RRC SN roll over. Increment of HFN due to RRC SN roll over is taken care of by target based on value sent by the source. For each SRB, in the case activation times for the next IP configuration to be applied on this SRB have already been reached this IE corresponds to the last value used. Else this value corresponds to the value the source would have initalized the HFN to at the activation time, not considering
>Signalling radio bearer specific integrity protection information >>Uplink RRC HFN
CV-IP
MP
>>Downlink RRC HFN
MP
Bit string (28)
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description any increment of HFN due to RRC SN roll over. Increment of HFN due to RRC SN roll over is taken care of by target based on value sent by the source. In particular, for SRB2, this IE should not take into account the RRC message that will trigger the relocation. NOTE: In order to have the possibility of sending downlink messages after the construction of the IE "SRNS RELOCATION INFO", the source may choose a value ahead of the last value used. For each SRB, this IE corresponds to the last value received or in the case activation time was not reached for a configuration the value equals (activation time 1). For each SRB, this IE corresponds to the last value used or in the case activation time was not reached for a configuration the value equals (activation time -1). In particular, for SRB2, this IE should not take into account the RRC message that will trigger the relocation. NOTE: In order to have the possibility of sending downlink messages after the construction of the IE "SRNS RELOCATION INFO", the source may choose a value ahead of the last value used for SRB3 and SRB4. Version
>>Uplink RRC Message sequence number
MP
Integer (0.. 15)
>>Downlink RRC Message sequence number
MP
Integer (0.. 15)
>Implementation specific parameters RRC IEs UE Information elements >U-RNTI
OP
Bit string (1..512)
MP
U-RNTI 10.3.3.47
G-RNTI is placed in this field when performing handover or cell reselection from GERAN Iu mode.
>C-RNTI >UE radio access Capability
OP MP
OP
C-RNTI 10.3.3.8 UE radio access capability 10.3.3.42 UE radio access capability extension 10.3.3.42a Integer (0..4095) Cell identity; 10.3.2.2 Time when position was estimated Indicates the cell, the SFN is valid for.
>Last known UE position >>SFN >>Cell ID >>CHOICE Position estimate
OP MP MP MP
3GPP
Release 6 Information Element/Group Name >>>Ellipsoid Point Need
1198 Multi Type and reference Ellipsoid Point; 10.3.8.4a Ellipsoid point with uncertainty circle 10.3.8.4d Ellipsoid point with uncertainty ellipse 10.3.8.4e Ellipsoid point with altitude 10.3.8.4b Ellipsoid point with altitude and uncertainty ellipsoid 10.3.8.4c UE Specific Behaviour Information idle 1 10.3.3.51
>>>Ellipsoid point with uncertainty circle
>>>Ellipsoid point with uncertainty ellipse
>>>Ellipsoid point with altitude
>>>Ellipsoid point with altitude and uncertainty ellipsoid
>UE Specific Behaviour Information 1 idle
OP
>UE Specific Behaviour Information 1 interRAT
OP
UE Specific Behaviour Information 1 interRAT 10.3.3.52
This IE should be included if received via the "INTER RAT HANDOVER INFO", the "RRC CONNECTION REQUEST", the IE "SRNS RELOCATION INFO" or the "Inter RAT Handover Info with Inter RAT Capabilities" This IE should be included if received via the "INTER RAT HANDOVER INFO", the "RRC CONNECTION REQUEST", the IE "SRNS RELOCATION INFO" or the "Inter RAT Handover Info with Inter RAT Capabilities"
Other Information elements >UE system specific capability
OP
1 to <maxSyste mCapabilit y> Inter-RAT UE radio access capability 10.3.8.7
>>Inter-RAT UE radio access capability
MP
UTRAN Mobility Information elements >URA Identifier CN Information Elements >CN common GSM-MAP NAS system information
OP
URA identity 10.3.2.6 NAS system information (GSM-MAP) 10.3.1.9 1 to <MaxCNdo mains> NAS system information (GSM-MAP) 10.3.1.9 CN related information to be provided for each CN domain
MP
>CN domain related information
OP
>>CN domain identity >>CN domain specific GSMMAP NAS system info
MP MP
3GPP
Release 6 Information Element/Group Name >>CN domain specific DRX cycle length coefficient Need MP
1199 Multi Type and reference CN domain specific DRX cycle length coefficient, 10.3.3.6
Measurement Related Information elements >For each ongoing measurement reporting
OP
1 to <MaxNoOf Meas>
The source RNC should include the measurement IEs for each measurement configured and ongoing in the UE. Measuremen t identity 10.3.7.48 Measuremen t command 10.3.7.46 Measuremen t type 10.3.7.50 Measuremen t reporting mode 10.3.7.49 Additional measuremen ts list 10.3.7.1
>>Measurement Identity
MP
>>Measurement Command
MP
This IE should have the value Setup.
>>Measurement Type
CV-Setup
>>Measurement Reporting Mode
OP
>>Additional Measurements list
OP
>>CHOICE Measurement >>>Intra-frequency >>>>Intra-frequency cell info
CV-Setup OP Intrafrequency cell info list 10.3.7.33 Intrafrequency measuremen t quantity 10.3.7.38 Intrafrequency reporting quantity 10.3.7.41 Reporting cell status 10.3.7.61 Measuremen t validity 10.3.7.51 Intrafrequency measuremen t reporting criteria 10.3.7.39 Periodical reporting criteria 10.3.7.53 NULL
>>>>Intra-frequency measurement quantity
OP
>>>>Intra-frequency reporting quantity
OP
>>>>Reporting cell status
OP
>>>>Measurement validity
OP
>>>>CHOICE report criteria >>>>>Intra-frequency measurement reporting criteria
OP
>>>>>Periodical reporting
>>>>>No reporting >>>Inter-frequency
3GPP
Release 6 Information Element/Group Name >>>>Inter-frequency cell info Need OP
1200 Multi Type and reference Interfrequency cell info list 10.3.7.13 Interfrequency measuremen t quantity 10.3.7.18 Interfrequency reporting quantity 10.3.7.21 Reporting cell status 10.3.7.61 Measuremen t validity 10.3.7.51 Interfrequency set update 10.3.7.22 Intrafrequency measuremen t reporting criteria 10.3.7.39 Interfrequency measuremen t reporting criteria 10.3.7.19 Periodical reporting criteria 10.3.7.53 NULL OP Inter-RAT cell info list 10.3.7.23 Inter-RAT measuremen t quantity 10.3.7.29 Inter-RAT reporting quantity 10.3.7.32 Reporting cell status 10.3.7.61 Measuremen t validity 10.3.7.51 Inter-RAT measuremen t reporting criteria 10.3.7.30
>>>>Inter-frequency measurement quantity
OP
>>>>Inter-frequency reporting quantity
OP
OP
OP
>>>>Inter-frequency set update
OP
>>>>CHOICE report criteria >>>>>Intra-frequency measurement reporting criteria
OP
>>>>>Inter-frequency measurement reporting criteria
>>>>>No reporting >>>Inter-RAT >>>>Inter-RAT cell info
>>>>Inter-RAT measurement quantity
OP
>>>>Inter-RAT reporting quantity
OP
OP
OP
>>>>CHOICE report criteria >>>>>Inter-RAT measurement reporting criteria
OP
3GPP
Release 6 Information Element/Group Name >>>>>Periodical reporting Need
1201 Multi Type and reference Periodical reporting criteria 10.3.7.53 NULL Traffic volume measuremen t object 10.3.7.70 Traffic volume measuremen t quantity 10.3.7.71 Traffic volume reporting quantity 10.3.7.74 Measuremen t validity 10.3.7.51 Traffic volume measuremen t reporting criteria 10.3.7.72 Periodical reporting criteria 10.3.7.53 NULL OP Quality measuremen t quantity 10.3.7.59 Quality measuremen t reporting criteria 10.3.7.58 Periodical reporting criteria 10.3.7.53 NULL OP UE internal measuremen t quantity 10.3.7.79 UE internal reporting quantity 10.3.7.82 UE internal measuremen t reporting
>>>>>No reporting >>>Traffic Volume >>>>Traffic volume measurement Object
OP
>>>>Traffic volume measurement quantity
OP
>>>>Traffic volume reporting quantity
OP
OP
>>>>CHOICE report criteria >>>>>Traffic volume measurement reporting criteria
OP
>>>>>No reporting >>>Quality >>>>Quality measurement quantity
>>>>CHOICE report criteria >>>>>Quality measurement reporting criteria
OP
>>>>>No reporting >>>UE internal >>>>UE internal measurement quantity
>>>>UE internal reporting quantity
OP
>>>>CHOICE report criteria >>>>>UE internal measurement reporting criteria
OP
3GPP
1202 Multi Type and reference criteria 10.3.7.80 Periodical reporting criteria 10.3.7.53 NULL LCS reporting quantity 10.3.7.111 LCS reporting criteria 10.3.7.110 Periodical reporting criteria 10.3.7.53
>>>>>No reporting >>>UE positioning >>>>LCS reporting quantity
OP
>>>>CHOICE report criteria >>>>>LCS reporting criteria
OP
>>>>>No reporting Radio Bearer Information Elements >Predefined configuration status information
OP
Predefined configuration status information 10.3.4.5a 1 to <maxSRBs etup> Signalling RB information to setup 10.3.4.24 1 to <maxRABs etup> RAB information to setup 10.3.4.10 Information for each RAB For each signalling radio bearer
>Signalling RB information list
MP
>>Signalling RB information
MP
>RAB information list
OP
>>RAB information
MP
Transport Channel Information Elements Uplink transport channels >UL Transport channel information common for all transport channels
OP
UL Transport channel information common for all transport channels 10.3.5.24 1 to <MaxTrCH > Added or reconfigured UL TrCH information 10.3.5.2 DL Transport channel
>UL transport channel information list >>UL transport channel information
OP
MP
Downlink transport channels >DL Transport channel information common for all
OP
3GPP
Release 6 Information Element/Group Name transport channels Need
1203 Multi Type and reference information common for all transport channels 10.3.5.6
>DL transport channel information list >>DL transport channel information
OP
1 to <MaxTrCH > Added or reconfigured DL TrCH information 10.3.5.1
MP
3GPP
Release 6 Information Element/Group Name PhyCH information elements >TPC Combination Info list >>Primary CPICH info Need
OP MP
1 to <maxRL> Primary CPICH info 10.3.6.60 TPC combination index 10.3.6.85 1 to <maxTGP S> TGPSI 10.3.6.82 Enumerated( active, inactive) Integer (0..255) REL-5
MP
>Transmission gap pattern sequence >>TGPSI >> Current TGPS Status Flag
OP
MP MP
REL-5 This flag indicates the current status of the Transmission Gap Pattern Sequence, whether it is active or inactive Connection Frame Number of the latest past frame of the first pattern within the Transmission Gap Pattern Sequence. REL-5
>>TGCFN
CV-Active
REL-5
>>Transmission gap pattern sequence configuration parameters >>>TGMP
OP
REL-5
MP
>>>TGPRC
MP
Enumerated( TDD measuremen t, FDD measuremen t, GSM carrier RSSI measuremen t, GSM Initial BSIC identification, GSM BSIC reconfirmation, Multi-carrier measuremen t) Integer (1..511, Infinity) Integer (0..14)
Transmission Gap pattern sequence Measurement Purpose.
REL-5
>>>TGSN
MP
>>>TGL1
MP
Integer(1..14 )
>>>TGL2
MD
Integer (1..14)
>>>TGD
MP
Integer(15..2 69,
The number of remaining transmission gap patterns within the Transmission Gap Pattern Sequence. Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN. The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1. The value of TGL2 shall be ignored if TGD is set to undefined Transmission gap distance indicates the number of slots
REL-5
REL-5
REL-5
REL-5
REL-5
3GPP
1205 Multi Type and reference undefined)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description between starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to undefined. The duration of transmission gap pattern 1. Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. Indicates whether normal PC mode or compressed PC mode is applied Initial Transmit Power is the uplink power control method to be used to compute the initial transmit power after the compressed mode gap. Compressed mode used in DL only Method for generating downlink compressed mode gap Compressed mode used in UL only Method for generating uplink compressed mode gap REL-5 REL-5 Version
>>>TGPL1 >>>RPP
MP MP
Integer (1..144) Enumerated (mode 0, mode 1).
>>>ITP
MP
Enumerated (mode 0, mode 1).
REL-5
>>>CHOICE UL/DL mode >>>>DL only >>>>>Downlink compressed mode method
MP
REL-5 REL-5 REL-5
MP
Enumerated (SF/2, higher layer scheduling)
>>>>UL only >>>>>Uplink compressed mode method MP Enumerated (SF/2, higher layer scheduling)
REL-5 REL-5
>>>>UL and DL >>>>>Downlink compressed mode method MP Enumerated (SF/2, higher layer scheduling) Enumerated (SF/2, higher layer scheduling) Enumerated (A, B) Real(0..3 by step of 0.1)
Compressed mode used in UL and DL Method for generating downlink compressed mode gap Method for generating uplink compressed mode gap
REL-5 REL-5
>>>>>Uplink compressed mode method
MP
REL-5
>>>Downlink frame type >>>DeltaSIR1
MP MP
REL-5 Delta in DL SIR target value to be set in the UE during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the first transmission gap in the transmission gap pattern. Delta in DL SIR target value to be set in the UE during the frame containing the start of the second transmission gap in the transmission gap pattern REL-5
>>>DeltaSIRafter1
MP
REL-5
>>>DeltaSIR2
OP
REL-5
3GPP
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description (without including the effect of the bit-rate increase) When omitted, DeltaSIR2 = DeltaSIR1. Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the second transmission gap in the transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1. Indicates the maximum number of repeats of patterns that the UE shall use to attempt to decode the unknown BSIC of the GSM cell in the initial BSIC identification procedure Indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure. The time is given in steps of 0.5 seconds. Version
>>>DeltaSIRafter2
OP
REL-5
>>>N Identify abort
CV-Initial BSIC
Integer(1..12 8)
REL-5
>>>T Reconfirm abort
CV-Reconfirm BSIC
Real(0.5..10. 0 by step of 0.5)
REL-5
>Scrambling Code Change List >>Primary CPICH info
CH-SF/2 MP
1 to <maxRL> Primary CPICH info 10.3.6.60 Enumerated (code change, no code change) MEASUREM ENT REPORT 10.2.19
REL-5 REL-5
>>Scrambling code change
MP
REL-5
Other Information elements >Measurement report
OP
>Failure cause
OP
Failure cause 10.3.3.13 Protocol error information 10.3.8.12
The source RNC should include the Measurement report the UE sent that triggered the SRNS relocation. This information could e.g. be used by the target RNC to set initial power when establishing a DCH. Diagnostics information related to an earlier SRNC Relocation request (see NOTE 2 in 14.12.0a)
>Protocol error information
CV-ProtErr
MBMS joined information >P-TMSI
OP OP P-TMSI (GSM-MAP) 10.3.1.13 MBMS Selected Services Info 10.3.9a.7b
Included if the UE has joined one or more MBMS services In case the UE is in PMM-Idle
REL-6 REL-6
OP
REL-6
3GPP
Release 6 Multi Bound MaxNoOfMeas
1207
3GPP TS 25.331 V6.23.0 (2009-09)
Explanation Maximum number of active measurements, upper limit 16
Condition Setup
Ciphering
IP
ProtErr
SRB1 Active
Initial BSIC
Re-confirm BSIC
SF/2
Explanation The IE is mandatory present when the IE Measurement command has the value "Setup", otherwise the IE is not needed. The IE is mandatory present when the IE Ciphering Status has the value "started" and the ciphering counters need not be reinitialised, otherwise the IE is not needed. The IE is mandatory present when the IE Integrity protection status has the value "started" and the integrity protection counters need not be reinitialised, otherwise the IE is not needed. This IE is mandatory present if the IE "Protocol error indicator" is included and has the value "TRUE". Otherwise it is not needed. The IE is mandatory present for RB1. Otherwise it is not needed. This IE is mandatory present when the value of the IE "Current TGPS Status Flag" is "Active" and not needed otherwise. This IE is mandatory present when the value of the IE "TGMP" is set to "GSM Initial BSIC identification" and not needed otherwise. This IE is mandatory present when the value of the IE "TGMP" is set to "GSM BSIC re-confirmation" and not needed otherwise. The IE is mandatory present if the IE Transmission Gap Pattern Sequence is included and has the value SF/2 as the compressed mode method, and already sent the UE the IE Scrambling Code Change for each RL in the active set. Otherwise the IE is not needed.
14.12.4.3
Void
14.12.4.4
RFC 3095 CONTEXT INFO
This RRC message is sent between network nodes in SRNS relocation. It is used to transfer the compressor and decompressor context information of the RFC 3095 protocol. Direction: source RNC target RNC
3GPP
Release 6 Information Element/Group name RFC 3095 context Need MP
1208 Multi 1 to <maxRBall RABs> RB identity 10.3.4.16 1 to <maxRFC3 095-CID> Integer (0..16383) Enumerated (u, o, r) Octet string (1..3000) Type and reference
>RB identity >RFC 3095 context list
MP MP
REL-5 REL-5
>>Downlink RFC 3095 context >>>Downlink RFC 3095 context identity >>>DL_MODE
OP MP MP
REL-5 REL-5 RFC 3095 mode in downlink before SRNS relocation. The RTP IR header (see section 5.7.7 of RFC3095 for detailed format) corresponding to the oldest header in the compressor sliding window. Arrival time (at the compressor) of REF_IR in milliseconds. See sections 4.5.4 and 6.5.1 of RFC3095. Current time in milliseconds. See section 6.5.1 of RFC3095. Last synchronized offset of IP-ID. See section 4.5.5 and 6.5.1 of RFC3095 (termed "Offset_I"). It is related to the compression and decompression of IP-ID and is the synchronized offset between the IP-ID value and the SN value (in the same header) during the last SO state before the relocation procedure. Last synchronized slope of TS. See sections 5.5.1.2 and 5.7 of RFC3095. In SO state, TS(n) = TS(m) + (n-m) * SYN_SLOPE_TS, where n and m are, the RTP SN of the current and REL-5
>>>REF_IR
MP
REL-5
>>>REF_TIME
OP
Integer (0..4294967 295)
REL-5
>>>CURR_TIME
OP
Integer (0..4294967 295) Integer (0..65535)
REL-5
>>>SYN_OFFSET_ID
OP
REL-5
>>>SYN_SLOPE_TS
OP
Integer (0..4294967 295)
REL-5
3GPP
Release 6
1209
3GPP TS 25.331 V6.23.0 (2009-09) the reference packet, respectively. The unit of SYN_SLOPE_TS depends on whether TS is scaled before compression or not. Information whether dynamic fields other than RTP SN, RTP TS and IP-ID have changed in the headers that are stored in the sliding window. Set to TRUE if changed and FALSE if not changed.
>>>DYN_CHANGED
MP
Boolean
REL-5
>>Uplink RFC 3095 context >>>Uplink RFC 3095 context identity >>>UL_MODE >>>REF_IR
OP MP MP MP
Integer (0..16383) Enumerated (u, o, r) Octet string (1..3000)
REL-5 REL-5 RFC 3095 mode in uplink The RTP IR header (see section 5.7.7 of IETF RFC3095 for detailed format) corresponding to the last correctly decompressed header. Arrival time (at the decompressor) of REF_IR in milliseconds. See sectionss 4.5.4 and 6.5.1 of RFC3095. Current time in milliseconds. See section 6.5.1 of RFC3095. Last synchronized offset of IP-ID. See sectionss 4.5.5 and 6.5.1 of RFC3095 (termed"Offset_I") . It is related to the compression and decompression of IP-ID and is the synchronized offset between the IP-ID value and the SN value (in the same header) during the last SO state before the relocation REL-5 REL-5
>>>REF_TIME
OP
Integer (0..4294967 295)
REL-5
>>>CURR_TIME
OP
Integer (0..4294967 295) Integer (0..65535)
REL-5
>>>SYN_OFFSET_ID
OP
REL-5
3GPP
Release 6
1210
3GPP TS 25.331 V6.23.0 (2009-09) procedure. Last synchronized slope of TS. See sectionss 5.5.1.2 and 5.7 of RFC3095. In SO state, TS(n) = TS(m) + (n-m) * SYN_SLOPE_TS, where n and m are, the RTP SN of the current and the reference packet, respectively. The unit of SYN_SLOPE_TS depends on whether TS is scaled before compression or not. Corresponds to the RTP Sequence Number of the predecessor of the latest RTP packet. This could be used to perform local repair of context by decompressor in U or O mode (see ref - 1 in section5.3.2.2.5 in IETF RFC3095 for further explanation).
>>>SYN_SLOPE_TS
OP
Integer (0..4294967 295)
REL-5
>>>REF_SN_1
OP
Integer (0..65535)
REL-5
14.13
Void
14.14
Void
3GPP
Release 6
1211
3GPP TS 25.331 V6.23.0 (2009-09)
Annex A (informative): USIM parameters

A.1 Introduction
This annex contains recommendations about the RRC parameters to be stored in the USIM.
A.2
Ciphering information
Need MP Multi <1 to maxCNDo mains> Bit string (128) <1 to maxCNDo mains> Bit string (128) Bit string (20) <1 to maxCNDo mains> Bit string (20) <1 to maxCNDo mains> Bit string (3) Key set identifier is described in [40]. START value is described in [40]. Integrity key is described in [40]. Type and reference Semantics description Cipher key is described in [40].
Information Element/Group name Cipher key for each CN domain
>CK Integrity key for each CN domain >IK THRESHOLD START value for each CN domain >START KSI, Key set identifier for each CN domain >KSI
MP MP
MP MP MP
MP MP
MP
A.3
Frequency information
Need OP Multi <1 to maxFDDFr eqList> Integer(0 .. 16383) Primary CPICH info 10.3.6.60 [21] Type and reference Semantics description Version
Neighbour cell list.

Information Element/Group name FDD cell list
>UARFCN downlink (Nd) >Primary scrambling code
MP OP <1 to maxFDDFr eqCellList> <1 to maxTDDFr eqList>
3.84 Mcps TDD cell list
OP
>UARFCN (Nt) >Cell parameters ID
MP OP <1 to maxTDDFr eqCellList> <1 to maxTDDFr eqList>
Integer(0 .. 16383) Integer (0..127)
[22] The Cell parameters ID is described in [32]. REL-4
1.28 Mcps TDD cell list
OP
>UARFCN (Nt)
MP
Integer(0 ..
[22]
REL-4
3GPP
Release 6 Information Element/Group name >Cell parameters ID Need
1212 Multi Type and reference 16383) Integer (0..127)
3GPP TS 25.331 V6.23.0 (2009-09) Semantics description The Cell parameters ID is described in [32]. Version
OP
<1 to maxTDDFr eqCellList> <1 to maxGSMC ellList>
REL-4
GSM Neighbour cell list >GSM neighbour cell info
OP MP
>>BSIC >>BCCH ARFCN
MP MP
A.4
Multiplicity values and type constraint values

Explanation Maximum number of CN domains Maximum number of FDD carrier frequencies to be stored in USIM Maximum number of TDD carrier frequencies to be stored in USIM Maximum number of neighbouring FDD cells on one carrier to be stored in USIM Maximum number of neighbouring TDD cells on one carrier to be stored in USIM Maximum number of GSM cells to be stored in USIM 4 4 4 32 32 32 Value
Constant Ciphering information maxCNDomains Frequency information maxFDDFreqList maxTDDFreqList maxFDDFreqCellList maxTDDFreqCellList maxGSMCellList
3GPP
Release 6
1213
3GPP TS 25.331 V6.23.0 (2009-09)
Annex B (informative): Description of RRC state transitions

This annex contains Stage 2 description of RRC states and state transitions.
B.1
RRC states and state transitions including GSM
After power on, the UE stays in Idle Mode until it transmits a request to establish an RRC Connection. In Idle Mode the connection of the UE is closed on all layers of the access stratum. In Idle Mode the UE is identified by non-access stratum identities such as IMSI, TMSI and P-TMSI. In addition, the UTRAN has no own information about the individual Idle Mode UEs, and it can only address e.g. all UEs in a cell or all UEs monitoring a paging occasion. The UE behaviour within this mode is described in [4]. The UTRA RRC Connected Mode is entered when the RRC Connection is established. The UE is assigned a radio network temporary identity (RNTI) to be used as UE identity on common transport channels. The RRC states within UTRA RRC Connected Mode reflect the level of UE connection and which transport channels that can be used by the UE. For inactive stationary data users the UE may fall back to PCH on both the Cell and URA levels. That is, upon the need for paging, the UTRAN checks the current level of connection of the given UE, and decides whether the paging message is sent within the URA, or should it be sent via a specific cell.
B.2
Transition from Idle Mode to UTRA RRC Connected Mode
The transition to the UTRA RRC Connected Mode from the Idle Mode can only be initiated by the UE by transmitting a request for an RRC Connection. The event is triggered either by a paging request from the network or by a request from upper layers in the UE. When the UE receives a message from the network that confirms the RRC connection establishment, the UE enters the CELL_FACH or CELL_DCH state of UTRA RRC Connected Mode. In the case of a failure to establish the RRC Connection the UE goes back to Idle Mode. Possible causes are radio link failure, a received reject response from the network or lack of response from the network (timeout).
B.2.1
Transitions for Emergency Calls
Refer to [4] for all states and procedures referred to in this subclause. When UE leaves idle mode from state Camped on any cell in order to make an emergency call, moving to state Connected mode (emergency calls only), the UE shall attempt to access the current serving cell. If the access attempt to the serving cell fails the UE shall use the Cell Reselection procedure. If no acceptable cell is found, the UE shall use the Any cell selection. When returning to idle mode, the UE shall use the procedure Cell selection when leaving connected mode in order to find an acceptable cell to camp on, state Camped on any cell.
B.3
B.3.1
-
UTRA RRC Connected Mode States and Transitions

CELL_DCH state
The CELL_DCH state is characterised by For 3.84 Mcps TDD: A dedicated physical channel is allocated to the UE in uplink and downlink or a dedicated physical channel is allocated to the UE in the uplink and HS_DSCH_RECEPTION is set to TRUE.
3GPP
Release 6
1214
3GPP TS 25.331 V6.23.0 (2009-09)
A dedicated physical channel is allocated to the UE in uplink and downlink. The UE is known on cell level according to its current active set. Dedicated transport channels, downlink and uplink (TDD) shared transport channels, and a combination of these transport channels can be used by the UE.
The CELL_DCH-state is entered from the Idle Mode through the setup of an RRC connection, or by establishing a dedicated physical channel from the CELL_FACH state. In TDD a PDSCH may be assigned to the UE in this state, to be used for a DSCH. A PUSCH may also be assigned to the UE in this state, to be used for a USCH. If PDSCH or PUSCH are used for TDD, a FACH transport channel may be assigned to the UE for reception of physical shared channel allocation messages.
B.3.1.1
Transition from CELL_DCH to Idle Mode
Transition to Idle Mode is realised through the release of the RRC connection.
B.3.1.2
Transition from CELL_DCH to CELL_FACH state
Transition to CELL_FACH state occurs when all dedicated channels have been released, which may be a) via explicit signalling (e.g. PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, etc.). at the end of the time period for which the dedicated channel was allocated (TDD)
B.3.1.3
Transition from CELL_DCH to CELL_PCH state
Transition to CELL_PCH state occurs via explicit signalling (e.g. PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, etc.).
B.3.1.4
Transition from CELL_DCH to URA_PCH state
Transition to URA_PCH state occurs via explicit signalling (e.g. PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, etc.).
B.3.1.5
Radio Resource Allocation tasks (CELL_DCH)
For the DCH, several physical channel allocation strategies may be applied. The allocations can be either permanent (needing a DCH release message) or based on time or amount-of-data. Resource allocation can be done separately for each packet burst with fast signalling on the DCH For each radio frame the UE and the network indicate the current data rate (in uplink and downlink respectively) using the transport format combination indicator (TFCI). However, in TDD, DCH and DSCH or USCH may be mapped on different CCTrCHs, their TFCI are totally independent. DCH transmission is not modified by the simultaneous existence of DSCH/USCH. If the configured set of combinations (i.e. transport format set for one transport channel) are found to be insufficient to retain the QoS requirements for a transport channel, the network initiates a reconfiguration of the transport format set (TFS) for that transport channel. This reconfiguration can be done during or in between data transmission. Further, the network can reconfigure the physical channel allowing an increase or decrease of the peak data rate. For the uplink data transmission, the UE reports the observed traffic volume to the network in order for the network to re-evaluate the current allocation of resources. This report contains e.g. the amount of data to be transmitted or the buffer status in the UE.
3GPP
Release 6
1215
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.1.6
RRC Connection mobility tasks (CELL_DCH)
Depending on the amount and frequency of data macrodiversity (soft handover) may or may not be applied. The RRC Connection mobility is handled by measurement reporting, soft handover and Timing re-initialised or Timingmaintained hard handover procedures.
B.3.1.7
UE Measurements (CELL_DCH)
The UE performs measurements and transmit measurement reports according to the measurement control information. The UE uses the connected mode measurement control information received in other states until new measurement control information has been assigned to the UE.
B.3.1.8
Acquisition of system information (CELL_DCH)
FDD UEs with certain capabilities reads system information broadcast on FACH. TDD UEs reads the BCH to acquire valid system information. For each acquisition, the UE may need different combinations of system information broadcast on BCH. The scheduling on the broadcast channel is done in such way that the UE knows when the requested information can be found.
B.3.2
-
CELL_FACH state
The CELL_FACH state is characterised by: No dedicated physical channel is allocated to the UE. The UE continuously monitors a FACH in the downlink. The UE is assigned a default common or shared transport channel in the uplink (e.g. RACH) that it can use anytime according to the access procedure for that transport channel. The position of the UE is known by UTRAN on cell level according to the cell where the UE last made a cell update. In TDD mode, one or several USCH or DSCH transport channels may have been established.
B.3.2.1
Transition from CELL_FACH to CELL_DCH state
A transition occurs, when a dedicated physical channel is established via explicit signalling (e.g. PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, etc.).
B.3.2.2
Transition from CELL_FACH to CELL_PCH state
The transition occurs when UTRAN orders the UE to move to CELL_PCH state, which is done via explicit signalling (e.g. CELL UPDATE CONFIRM, RADIO BEARER RECONFIGURATION, etc.).
B.3.2.3
Transition from CELL_FACH to Idle Mode
Upon release of the RRC connection, the UE moves to the idle mode.
B.3.2.4
Transition from CELL_FACH to URA_PCH State
The transition occurs when UTRAN orders the UE to move to URA _PCH state, which is done via explicit signalling (e.g. URA UPDATE CONFIRM, RADIO BEARER RECONFIGURATION, etc.).
3GPP
Release 6
1216
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.2.5
Radio Resource Allocation Tasks (CELL_FACH)
In the CELL_ FACH state the UE will monitor an FACH. It is enabled to transmit uplink control signals and it may be able to transmit small data packets on the RACH. The network can assign the UE transport channel parameters (e.g. transport format sets) in advance, to be used when a DCH is used. Upon assignment of the physical channel for DCH, the UE moves to CELL_DCH state and uses the preassigned TFS for the DCH. If no UE dedicated physical channel or transport channel configuration has been assigned, the UE uses the common physical channel and transport channel configuration according to the system information. For the uplink data transmission, the UE reports the observed traffic volume to the network in order for the network to re-evaluate the current allocation of resources. This report contains e.g. the amount of data to be transmitted or the buffer status in the UE. When there is either user or control data to transmit, a selection procedure determines whether the data should be transmitted on a common transport channel, or if a transition to CELL_DCH should be executed. The selection is dynamic and depends on e.g. traffic parameters (amount of data, packet burst frequency). In the TDD mode, the UTRAN can assign USCH / DSCH resources to the UE in CELL_FACH state. When USCH / DSCH resources are assigned, the UE will continue to monitor FACHs, depending on the UE capability. The UE may use the USCH / DSCH to transmit signalling messages or user data in the uplink and / or the downlink using USCH and / or DSCH when resources are allocated to cell and UE is assigned use of those USCH / DSCH. For the uplink data transmission on USCH the UE reports to the network the traffic volume (current size of RLC data buffers), The UTRAN can use these measurement reports to re-evaluate the current allocation of the USCH / DSCH resources.
B.3.2.6
RRC Connection mobility tasks (CELL_FACH)
In this state the location of the UE is known on cell level. A cell update procedure is used to report to the UTRAN, when the UE selects a new cell to observe the common downlink channels of a new cell. Downlink data transmission on the FACH can be started without prior paging. The UE monitors the broadcast channel and system information on BCCH of its own and neighbour cells and from this the need for the updating of cell location is identified. The UE performs cell reselection and upon selecting a new UTRA cell, it initiates a cell update procedure. Upon selecting a new cell belonging to another radio access system than UTRA, the UE enters idle mode and makes an access to that system according to its specifications.
B.3.2.7
UE Measurements (CELL_FACH)
The UE performs measurements and transmit measurement reports according to the measurement control information. By default, the UE uses the measurement control information broadcast within the system information. However, for measurements for which the network also provides measurement control information within a MEASUREMENT CONTROL message, the latter information takes precedence.
B.3.2.8
Transfer and update of system information (CELL_FACH)
The UE reads the BCH to acquire valid system information. For each acquisition, the UE may need different combinations of system information broadcast on BCH. The scheduling on the broadcast channel is done in such way that the UE knows when the requested information can be found. When the system information is modified, the scheduling information is updated to reflect the changes in system information transmitted on BCH. The new scheduling information is broadcast on FACH in order to inform UEs about the changes. If the changes are applicable for the UE, the modified system information is read on BCH.
3GPP
Release 6
1217
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.3
-
CELL_PCH state
The CELL_PCH state is characterised by: No dedicated physical channel is allocated to the UE. The UE selects a PCH with the algorithm specified in subclause 8.5.19, and uses DRX for monitoring the selected PCH via an associated PICH. No uplink activity is possible. The position of the UE is known by UTRAN on cell level according to the cell where the UE last made a cell update in CELL_FACH state.
The DCCH logical channel cannot be used in this state. If the network wants to initiate any activity, it needs to make a paging request on the PCCH logical channel in the known cell to initiate any downlink activity.
B.3.3.1
Transition from CELL_PCH to CELL_FACH state
The UE is transferred to CELL_FACH state: a) by paging from UTRAN (PAGING TYPE1 message) b) through any uplink access
B.3.3.2
Radio Resource Allocation Tasks (CELL_PCH)
In CELL_PCH state no resources have been granted for data transmission. For this purpose, a transition to another state has to be executed. The UE may use Discontinuous Reception (DRX) in order to reduce power consumption. When DRX is used the UE needs only to receive at one paging occasion per DRX cycle. The UE may be instructed to use a specific DRX cycle length by the network. The UE determines its paging occasions in the same way as for Idle Mode, see [4].
B.3.3.3
RRC Connection mobility tasks (CELL_PCH)
In the CELL_PCH state, the UE mobility is performed through cell reselection procedures, which may differ from the one defined in [4]. The UE performs cell reselection and upon selecting a new UTRA cell, it moves to CELL_FACH state and initiates a cell update procedure in the new cell. After the cell update procedure has been performed, the UE changes its state back to CELL_PCH state if neither the UE nor the network has any more data to transmit. Upon selecting a new cell belonging to another radio access system than UTRA, the UE enters idle mode and make an access to that system according to its specifications. In case of low UE activity, UTRAN may want to reduce the cell-updating overhead by ordering the UE to move to the URA_PCH State. This transition is made via the CELL_FACH state. UTRAN may apply an inactivity timer, and optionally, a counter, which counts the number of cell updates e.g. UTRAN orders the UE to move to URA_PCH when the number of cell updates has exceeded certain limits (network parameter).
B.3.3.4
UE Measurements (CELL_PCH)
The UE performs measurements and transmit measurement reports according to the measurement control information. The UE uses the measurement control information according to the system information when no UE dedicated measurement control information has been assigned.
B.3.3.5
Transfer and update of system information (CELL_PCH)
The UE reads the BCH to acquire valid system information. For each acquisition, the UE may need different combinations of system information broadcast on BCH. The scheduling on the broadcast channel is done in such way that the UE knows when the requested information can be found.
3GPP
Release 6
1218
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.4
-
URA_PCH State
The URA_PCH state is characterised by: No dedicated channel is allocated to the UE. The UE selects a PCH with the algorithm specified in subclause 8.5.19, and uses DRX for monitoring the selected PCH via an associated PICH. No uplink activity is possible. The location of the UE is known on UTRAN Registration area level according to the URA assigned to the UE during the last URA update in CELL_FACH state.
The DCCH logical channel cannot be used in this state. If the network wants to initiate any activity, it needs to make a paging request on the PCCH logical channel within the URA where the location of the UE is known. If the UE needs to transmit anything to the network, it goes to the CELL_FACH state. The transition to URA_PCH State can be controlled with an inactivity timer, and optionally, with a counter that counts the number of cell updates. When the number of cell updates has exceeded certain limits (a network parameter), then the UE changes to the URA_PCH State. URA updating is initiated by the UE, which, upon the detection of the Registration area, sends the network the Registration area update information on the RACH of the new cell.
B.3.4.1
Transition from URA_PCH State to CELL_FACH State (URA_PCH)
Any activity causes the UE to be transferred to CELL_ FACH State. a) Uplink access is performed by RACH. b) by paging from UTRAN ( PAGING TYPE1 message ). NOTE: The release of an RRC connection is not possible in the URA_PCH State. The UE will first move to CELL_FACH State to perform the release signalling.
B.3.4.2
Radio Resource Allocation Tasks (URA_PCH)
In URA_PCH State no resources have been granted for data transmission. For this purpose, a transition to CELL_FACH State has to be executed. The UE may use Discontinuous Reception (DRX) in order to reduce power consumption. When DRX is used the UE needs only to receive at one paging occasion per DRX cycle. The UE may be instructed to use a specific DRX cycle length by the network. The UE determines its paging occasions in the same way as for Idle Mode, see [4].
B.3.4.3
RRC Connection mobility tasks (URA_PCH)
In URA_PCH State the location of a UE is known on UTRAN Registration area level. In this state, the UE mobility is performed through URA reselection procedures, which may differ from the definitions in [4]. The UE performs cell reselection and upon selecting a new UTRA cell belonging to a URA that does not match the URA used by the UE, the UE moves to CELL_FACH state and initiates a URA update towards the network. After the URA update procedure has been performed, the UE changes its state back to URA_PCH state if neither the UE nor the network has any more data to transmit. Upon selecting a new cell belonging to another radio access system than UTRA, the UE enters idle mode and makes an access to that system according to its specifications.
B.3.4.4
UE Measurements (URA_PCH)
The UE performs measurements and transmit measurement reports according to the measurement control information. The UE uses the measurement control information according to the system information when no UE dedicated measurement control information has been assigned.
3GPP
Release 6
1219
3GPP TS 25.331 V6.23.0 (2009-09)
B.3.4.5
Transfer and update of system information (URA_PCH)
The same mechanisms to transfer and update system information as for state CELL_PCH are applicable for UEs in URA_PCH state.
B.3.5
States and Transitions for Cell Reselection in URA_PCH, CELL_PCH, and CELL_FACH
See Idle Mode figure in 3GPP TS 25.304
Cell Selection when leaving connected mode
Camped Normally
go here from idle mode
return to idle mode no suitable cell found trigger suitable cell selected Initial Cell Reselection
UTRA RRC Connected Mode
trigger
suitable cell selected
Cell Reselection
no suitable cell found suitable cell in other RAT found
Figure B.3.5-1: UTRA RRC Connected mode cell reselection for URA_PCH, CELL_PCH, and CELL_FACH In some states the UE performs cell reselection procedures. The UE selects a suitable cell (defined in [4]) and radio access technology based on connected mode radio measurements and cell reselection criteria. Figure B.3.5-1 shows the states and procedures in the cell reselection process in connected mode. When a cell reselection is triggered, the UE evaluates the cell reselection criteria based on radio measurements, and if a better cell is found that cell is selected, procedure Cell reselection (see [4]). If the change of cell implies a change of radio access technology, the RRC connection is released, and the UE enters idle mode of the other RAT. If no suitable cell is found in the cell reselection procedure, the UE eventually enters idle mode. When an Initial cell reselection is triggered, the UE shall use the Initial cell reselection procedure (see [4]) to find a suitable cell. One example where this procedure is triggered is at radio link failure, where the UE may trigger an initial cell reselection in order to request re-establishment of the RRC connection. If the UE is unable to find a suitable cell, the UE eventually enters idle mode.
B.4
Inter-RAT handover with CS domain services
When using CS domain services, UTRAN is using an Inter-Radio access system Handover Procedure and GSM is using a Handover procedure for the transition from UTRA RRC Connected Mode to GSM Connected Mode.
3GPP
Release 6
1220
3GPP TS 25.331 V6.23.0 (2009-09)
B.5
Inter-RAT handover with PS domain services
When using PS domain services, the UE can initiate cell reselection from a GSM/GPRS cell to a UTRAN cell and then uses the RRC Connection Establishment procedure for the transition to UTRA RRC Connected mode. It is also possible for the BSS to initiate a UTRA Inter-RAT Handover to seamlessly relocate the UE to UTRAN. In this latter case there is no need to return the UE to Idle Mode (GPRS Packet Idle Mode) and the UE immediately moves to RRC connected state in the UTRAN. In the case that cell reselection is used, when the RRC Connection is established from Idle Mode (GPRS Packet Idle Mode) the RRC CONNECTION REQUEST message contains an indication, that UTRAN needs to continue an already established GPRS UE context from the CN. This indication allows UTRAN to e.g. prioritise the RRC CONNECTION REQUEST from the UE. In UTRA RRC connected mode UTRAN may use UE or network initiated cell reselection to change from a UTRAN cell to a GSM/GPRS cell. If the cell reselection was successful the UE enters Idle Mode (GPRS Packet Idle Mode). The UE sends a packet channel request from Idle Mode (GPRS Packet Idle mode) to establish a Temporary Block flow and enter GPRS Packet Transfer Mode. In the GPRS Packet Transfer Mode the UE sends a RA Update request message. The RA Update Request message sent from the UE contains an indication that GSM/GPRS need to continue an already established UTRAN UE context from the CN. This means that the RA Update request is always sent for the transition from UTRA RRC Connected Mode to GSM/GPRS regardless if the RA is changed or not. Alternatively, the UTRAN may use an Inter-System Relocation (PS Handover) to relocate a UTRA RRC connected UE directly to GPRS Packet Transfer Mode in GERAN. NOTE: The reason for using RA update instead of a new message is to reduce the impact on the existing GSM/GPRS specification.
B.6
B.6.1
Inter-RAT handover with simultaneous PS and CS domain services

Inter-RAT handover UTRAN to GSM / BSS
For a UE in CELL_DCH state using both CS and PS Domain services the Inter-RAT handover procedure is based on measurement reports from the UE but initiated from UTRAN. The UE performs the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. When the UE has sent handover complete message to GSM / BSS the UE initiates a temporary block flow towards GPRS and sends a RA update request. If the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode was successful the handover is considered as successful regardless if the UE was able to establish a temporary block flow or not towards GPRS. In case of Inter-RAT handover failure the UE has the possibility to go back to UTRA RRC Connected Mode and reestablish the connection in the state it originated from.
B.6.2
Inter-RAT handover GSM / BSS to UTRAN
For a UE in GSM Connected Mode using both CS and PS domain services the Inter-RAT handover procedure is based on measurement reports from the UE but initiated from GSM / BSS. The UE performs the Inter-RAT handover from GSM Connected Mode to UTRA RRC Connected Mode. In UTRA RRC Connected Mode both services are established in parallel. If the Inter-RAT handover from GSM Connected mode to UTRA RRC Connected Mode was successful the handover is considered as successful. In case of Inter-RAT handover failure the UE has the possibility to go back to GSM Connected Mode and re-establish the connection in the state it originated from.
3GPP
Release 6
1221
3GPP TS 25.331 V6.23.0 (2009-09)
Annex C (informative): Description for the Compressed Coding of Pre-defined configurations included in the INTER RAT HANDOVER INFO message
This annex contains a description of the compressed coding of the IE "Predefined configuration status information compressed" (see subclause 10.3.4.5b) included in the INTER RAT HANDOVER INFO message.
C.1
Definitions
Pre-defined configuration set with different value tags: This is a set of consecutive positions for which pre-defined configurations are stored with different value tags. The set cannot include positions for which no pre-defined configuration is stored. Pre-defined configuration list with variable size: This is the variable sized list consisting of the value tags corresponding to the remaining positions after the "Pre-defined configuration sets with different value tags" have been formed. This will also indicate not stored pre-defined configurations, either explicitly or implicitly (i.e. in the case that there are no more stored configurations until the end of the variable sized list). This is highlighted in figures C.2-1 and C.2-2.
C.2
Examples of the methodology
From figure C.2-1 it can be seen that there are two "Pre-defined configuration sets with different value tags". The start position of Set1 is "1" with a list of 7 pre-defined configurations {1, 2, 3, 4, 5, 6, 7}. The start position of Set2 is "10" with a list of 6 pre-defined configurations {10, 11, 12, 13, 14, 15}. The "Pre-defined configurations list with variable size" has a start position of 0, and includes all of the pre-defined configurations not included in the sets {0, 8, 9}. The value tag at position 9 is not stored. This does not need to be explicitly indicated in the coding as "not stored" because there are no stored pre-defined configurations positioned after this in the list.
3GPP
Release 6
1222
3GPP TS 25.331 V6.23.0 (2009-09)
10
11
12
13
14
15
Pre-defined configuration set1 with different value tags
Not explicitly indicated
Pre-defined configurations list with variable size
Figure C.2-1: Example scenario where non-stored pre-defined configurations do not need to be explicitly indicated
Figure C.2-2 is similar to Figure C.2-1. However in this case for the "Pre-defined configurations list with variable size", the pre-defined configuration in position 8 is not stored. This needs to be explicitly indicated in the coding as "not stored" because there is a stored pre-defined configuration (position 9) positioned after this in the list.
3GPP
Release 6
1223
3GPP TS 25.331 V6.23.0 (2009-09)
10
11
12
13
14
15
Pre-defined configurations list with variable size
Figure C.2-2: Example scenario where non-stored pre-defined configurations need to be explicitly indicated
3GPP
Release 6
1224
3GPP TS 25.331 V6.23.0 (2009-09)
Annex D (Normative): Implementation of Domain Specific Access Control (DSAC) in UEs of 3GPP Release 5
UEs of 3GPP Release 5 implementing the domain specific access class control feature but not implementing the network sharing feature shall act on the domain specific access class restriction indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB" if present, and otherwise apply the access restrictions indicated by the IE "Cell Access Restriction".
3GPP
Release 6
1225
3GPP TS 25.331 V6.23.0 (2009-09)
Annex E (informative): Change history

Change history
Date 10/1999 12/1999 TSG # RP-05 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 TSG Doc. RP-99524 RP-99650 RP-99654 RP-99654 RP-99656 RP-99656 RP-99656 RP-99656 RP-99656 RP-99656 RP-99656 RP-99656 RP-99652 RP-99651 RP-99654 RP-99651 RP-99719 RP-99654 RP-99651 RP-99654 RP-99656 RP-99652 RP-99651 RP-99656 RP-99656 RP-99654 RP-99656 RP-99656 CR 001 005 007 009 010 011 012 013 014 015 016 017 018 019 025 026 027 028 029 034 038 039 040 042 044 045 046 2 1 1 1 1 1 1 Rev Subject/Comment Approved at TSG-RAN #5 and placed under Change Control Modification of RRC procedure specifications 1 Introduction of Information Element for Power Control Algorithm 1 1 2 3 2 1 1 3 2 RRC parameters for SSDT Inclusion of information elements for integrity protection Security mode control procedure Updates of the system information procedure Inter-frequency measurements and reporting Inter-system measurements and reporting Additional measurements in RRC measurement messages Value range for Measurement Information Elements Message contents for inter system handover to UTRAN Inclusion of ciphering information elements Corrections and editorial changes Algorithm for CTCF Calculation Logical CH for RRC Connection Re-establishment (RRC Connection Re-establishment deleted in RAN_10, RP-000715) Gain Factors Parameters for CELL UPDATE CONFIRM message Cell Update Cause RRC Initialisation Information Open loop power control for PRACH Addition of the UE controlled AMR mode adaptation Information elements for RLC reset Support for DS-41 Initial UE Identity Integration of Cell Broadcast Service (CBS) Old 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 New 3.0.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
Gated transmission of DPCCH 3.0.0 Modification to the Transport Format Combination Control message 3.0.0 New Information elements and modifications to messages required 3.0.0 in order to support configuration and re-configuration of the DSCH in FDD mode Editorial Corrections and Alignments with Layer 1 specifications 3.0.0 Information elements for TDD shared channel operation 3.0.0 Description of CN dependent IEs in Master Information Block UE capability information elements 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0
RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06
047 048 049 050 051 052 053 054 055 056 057 061 062 063 064 066 067 069 070 071 072
1 1
3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
UTRAN response time to uplink feedback commands of TX diversity control New and corrected CPCH parameters Compressed mode parameters without gating
1 1 2 1 1
Transport format combination set and transport format combination 3.0.0 subset Information elements for cell selection and reselection 3.0.0 Corrections and Alignments of the RRC to the L1 for TDD 3.0.0 Introduction of a SCCH procedure Support for DS-41 Paging UE Identity Support for cdma2000 Hard Handover Provide necessary signalling to support FDD DSCH RRC procedure interactions Transfer of UE capabilities Selection of initial UE identity UE capability verification in the security mode control procedure 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0
DPCH initial power Actions when entering idle mode Specification of inter-frequency and inter-system reporting events for FDD
3GPP
Release 6
1226 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06 RP-06
TSG Doc. RP-99657 RP-99654 RP-99654 RP-99657 RP-99654 RP-99657 RP-99654 RP-99654 RP-99657 RP-99657 RP-99655 RP-99657 RP-99657 RP-99653 RP-99655 RP-99655 RP-99657 RP-99655 RP-99657 RP-99657 RP-99655 RP-99657 RP-99657 RP-99655 RP-99657 RP-99653 RP-99657
CR 073 074 076 077 078 079 080 081 082 083 085 092 095 096 097 098 100 102 106 108 109 110 113 116 117 120 121
Rev Subject/Comment 1 Signalling radio bearers CN information elements UE information elements 1 Radio bearer, transport channel and physical channel information elements Other information elements RRC signalling for PDCP Content of Measurement Control Messages RRC Information Elements to support Block STTD transmission diversity in TDD Signalling connection release Addition of cell access restriction information elements to System Information RRC Connection Establishment parameters Support of UE autonomous update of a active set on a non-used frequency TPC combining for power control Editorial Modification of IEs in RRC messages Selection of SCCPCH 1 1 1 1 1 1 1 1 3 1 1 RRC Initialisation Information
Old 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0
New 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
1 1 1 1 1 1
Support of physical channel establishment and failure criteria in the 3.0.0 UE RRC Connection Re-establishment (Message deleted in RAN_10, 3.0.0 RP-000715) System information on FACH 3.0.0 SAPs and Primitives for DS-41 mode TX Diversity Mode for Dedicated Channel RACH message length signalling on System Information Routing of NAS messages in UTRAN TBS Identification in TFS Merging the hard handover and some radio bearer control procedures Selected RRC message transfer syntax Efficient rate command signalling TDD Mode BCH Reception in Cell DCH State Uplink Outer Loop Power Control in TDD Mode 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
03/2000
RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07
RP-000043 122 RP-000043 123 RP-000043 124 RP-000043 125 RP-000043 126 RP-000043 131 RP-000043 132 RP-000043 133 RP-000043 134 RP-000043 137 RP-000043 138 RP-000043 139 RP-000043 140 RP-000043 141 RP-000043 142 RP-000043 143 RP-000043 144 RP-000043 145 RP-000043 146 RP-000043 147 RP-000044 148 RP-000044 149 RP-000044 150 RP-000044 152 2 3 4 1 3 2 1 2 1 1 1 2 1
TFS TB Size Calculation with Bit Aligned TDD MAC Headers Grouping of DRAC IEs, and detailed definitions of these IEs Correction of specifications for the 'Dynamic Resource Allocation Control of Uplink DCH' Procedure Clarification of PDCP info and PDCP capability IEs Editorial change to "Specification of system information block characteristics" Additions of CBS related Information Elements Signalling for computed gain factors General error handling procedures RRC message extensions Padding of RRC messages using RLC transparent mode UE information elements Other information elements Integrity protection function RAB-RB relations Inter-system handover from UTRAN Handover to UTRAN including procedure for preconfiguration RRC measurement filtering parameters New event "RL out of UE Rx window" Access control on RACH cdma2000 Hard Handover CPCH parameters with corrections U-plane AM RLC reconfiguration by cell update procedure
3GPP
Release 6
1227 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07
TSG Doc. CR RP-000044 154 RP-000044 155 RP-000044 156 RP-000044 157 RP-000044 159 RP-000044 160 RP-000044 162 RP-000044 163 RP-000044 164 RP-000044 165 RP-000044 166 RP-000044 167 RP-000044 168 RP-000044 169 RP-000044 170 RP-000044 171 RP-000045 172 RP-000045 173 RP-000045 174 RP-000045 175 RP-000045 176 RP-000045 177 RP-000045 178 RP-000045 179 RP-000045 180 RP-000045 183 RP-000045 184 RP-000045 188 RP-000045 189 RP-000045 192 RP-000045 193 RP-000045 194 RP-000045 201 RP-000045 202 RP-000045 203 RP-000045 204 RP-000046 205 RP-000046 206 RP-000046 207 RP-000046 208 RP-000046 209 RP-000046 210 RP-000046 212 RP-000046 213 RP-000046 215 RP-000046 220 RP-000046 229 RP-000046 234 RP-000046 236 RP-000046 252 RP-000046 254
Rev Subject/Comment 3 CPCH 1 2 Information elements for ASC in TDD Addition of timing advance value in handover related messages Physical channel description for TDD Message contents for the intersystem command message to UTRAN operating in TDD mode Corrections on use of PUSCH power control info and minor corrections UE individual DRX cycles in CELL_PCH and URA_PCH states Correction to Transport Format Combination Control procedure 3 2 2 Downlink outer loop power control Redirection of RRC connection setup Inter-frequency measurements in CELL_FACH state List of found editorial mistakes in the Dec99 version of 25.331 (V3.1.0) Transport block size Cell Access Restriction Editorial modification Modification of DPCH info 1 2 Measurement control message Reporting cell status Additional IE for RB release Available SF in PRACH info Traffic volume measurement event Report of multiple cells on an event result Editorial modification on Direct Transfer Correction of the Security Mode Control procedure 1 1 1 1 1 1 1 1 1 1 1 1 Maximum calculated Transport Format Combination Additional DPCH IEs to align 25.331 with 25.214 RB DCH mapping Modifications related to FDD mode DSCH Identification of Shared Channel Physical Configuration in TDD Mode Uplink Outer Loop Power Control During Hard Handover Support of Multiple CCTrCH's in TDD Mode Uplink Physical Channel Control in TDD Mode Transfer of initial information from UE to target RNC prior to handover to UTRAN CN information elements UTRAN mobility information elements RB information elements Physical channel information elements UE capability information elements UE variables Actions when entering idle mode Usage of pilot bits System information procedure corrections Reconfiguration of ciphering 1
Old 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
New 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
1 1
1 1 2 1 1 1
Enhancements to RRC connection re-establishment procedure 3.1.0 (Message subsequently deleted in RAN_!), RP-000715) Updates to RRC Initialisation Information transparent container and 3.1.0 addition of reverse direction container description Changes in RRC messages to support lossless SRNC relocation 3.1.0 Measurements of unlisted neighbouring cells Inclusion of Location Services Application of Access Service Classes and relation to Access Classes DRX indicator presence and state entering mechanism at the end of a procedure Physical shared channel allocation procedure 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
3GPP
Release 6
1228 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07 RP-07
TSG Doc. CR RP-000046 255 RP-000046 256 RP-000046 259 RP-000046 263 RP-000046 267 RP-000047 268 RP-000047 271 RP-000047 272 RP-000047 273 RP-000222 228 RP-000222 260 RP-000222 261 RP-000222 262 RP-000222 265 RP-000222 269 RP-000222 275 RP-000222 279 RP-000222 280 RP-000222 281 RP-000222 282 RP-000222 283 RP-000222 285 RP-000222 286 RP-000222 287 RP-000222 288 RP-000222 289 RP-000222 291 RP-000222 292 RP-000222 293 RP-000223 294 RP-000223 296 RP-000223 297 RP-000223 298 RP-000223 300 RP-000223 301 RP-000223 304 RP-000223 305 RP-000223 306 RP-000223 307 RP-000223 309 RP-000223 310 RP-000223 311 RP-000223 312 RP-000223 313 RP-000223 314 RP-000223 315 RP-000223 318 RP-000223 319 RP-000223 320 RP-000224 323 RP-000224 324 RP-000224 325 RP-000224 326 RP-000224 328 RP-000224 329
Rev Subject/Comment Corrections to TDD specific parameters in PICH info Editorial modifications 2 Introduction of mapping function information in Cell selection and Ciphering and integrity HFN New SIB for UP Removal of synchronization Case 3 TX Diversity Update of tabular format clause 10 ASN.1 description 5 1 4 4 3 1 Downlink power control in compressed mode Clarification on physical channel allocations in TDD TDD Measurements and Reporting Signalling of IEs related to System Information on FACH Transport Format Combination Control Signalling of partial failure in radio bearer related procedures Clarification on PDCP info Editorial modification on Transport Ch capability 3 1 1 2 1 1 1 2 1 1 1 1 3 1 2 1 1 Editorial modification on CN IE Editorial modification on Physical CH IE Editorial modification on ASN.1 description IEs on SIB5/6 Re-establishment timer CN DRX cycle coefficient Cell Access Restriction Cell selection and re-selection parameters Modification on Measurement IE RACH Transmission parameters SCCPCH System Info Addition of HFN for RRC CONNECTION RE-ESTABLISHMENT COMPLETE RLC reconfiguration indicator RLC Info Usage of Transport CH ID Transport format combination set Usage of U-RNTI and C-RNTI in DL DCCH message Description of Cell Update Procedure System information modification procedure Functional descriptions of the RRC messages Clarification of CTFC calculation 3 2 5 2 1 2 1 1 1 1 3 1 Compressed mode parameters Signalling procedure for periodic local authentication Editorial corrections on security Security capability Corrections on ASN.1 definitions DRX cycle lower limit Removal of CPICH SIR measurement quantity Signalling connection release request Change to IMEI coding from BCD to hexadecimal Removal of RLC sequence numbers from RRC initialisation information Addition of the length of PDCP sequence numbers into PDCP info BSIC verification of GSM cells Reporting cell status RRC measurement filtering parameters Cell-reselection parameter signalling 3 Multiplicity values Quality measurements
Old 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
New 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0
06/2000
RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08
3GPP
Release 6
1229 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08
TSG Doc. CR RP-000224 330 RP-000224 331 RP-000224 332 RP-000224 333 RP-000224 334 RP-000224 335 RP-000224 336 RP-000224 337 RP-000224 339 RP-000224 340 RP-000224 342 RP-000224 344 RP-000224 345 RP-000224 346 RP-000225 347 RP-000225 348 RP-000225 350 RP-000225 351 RP-000225 352 RP-000225 353 RP-000225 354 RP-000225 355 RP-000225 357 RP-000225 358 RP-000225 359 RP-000225 360 RP-000225 361 RP-000225 362 RP-000225 363 RP-000225 364 RP-000225 368 RP-000225 371 RP-000225 372 RP-000225 373 RP-000226 375 RP-000226 377 RP-000226 378 RP-000226 379 RP-000226 380 RP-000226 382 RP-000226 383 RP-000226 384 RP-000226 385 RP-000226 387 RP-000226 388 RP-000226 389 RP-000226 390 RP-000226 391 RP-000226 392 RP-000226 393 RP-000226 394 RP-000226 395
Rev Subject/Comment 4 CPCH Status Indication mode correction 4 End of CPCH transmission Handover to UTRAN procedure Harmonization of access service classes in FDD and TDD 1 Correction to usage of primary CCPCH info and primary CPICH info Corrections and clarifications on system information handling Editorial corrections 1 Editorial corrections on uplink timing advance Correction of Transport Format Combination tabular format and ASN.1 UE variables General error handling System Information extensibility in ASN.1 definitions Usage of pilot bits 3 1 1 2 3 2 2 2 3 1 1 1 1 2 1 RRC connection release procedure Alignment of Section 10.3 on methodology defined in 25.921 Modifications of cell (re)selection parameters GPS time-of-week represented as seconds and fractions of seconds CPCH corrections PLMN type selection Paging and establishment cause values Common channel configurations Clarification of prioritization of logical channels in UE UE capability corrections Clarification of HFN Clarification of Integrity Protection RRC message size optimization regarding TrCH parameters Protocol extensions in ASN Downloading of predefined configurations via SIB 16 Optimization of System Information CPCH gain factor SFN Transmission Rate in TDD Mode Integrity Control Modification to measurement event evaluation System Information related parameters 1 Changes in RB mapping info Editorial corrections to PRACH system information and Cell info 1 1 1 Editorial Corrections to 25.331 Procedures and Tabular Format Corrections to figures and procedures for the failure cases Corrections on use of ORDERED_CONFIG Corrections to Transport Channel and RB Reconfiguration procedures Corrections to INITIAL DIRECT TRANSFER and UE CAPABILITY INFORMATION CONFIRM procedures Corrections to Transparent mode signalling info Tabular format and ASN.1 Corrections to Soft Handover messages and procedures Corrections to RRC CONNECTION REJECT procedures 1 1 1 1 1 1 Transport format combination in TDD and Transport channel ID Signalling for dynamic TTI in TDD Usage of DCCH for Shared Channel Allocation message Correction to physical channel IEs in TDD TDD preconfiguration for Handover to UTRAN Corrections to measurement control descriptions and messages Corrections on ASN.1 definitions Addition of the Segmentation indication field for transparent mode RLC in the RLC Info
Old 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
New 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0
1 1 1
3GPP
Release 6
1230 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08 RP-08
TSG Doc. CR RP-000226 396 RP-000226 397 RP-000227 398 RP-000227 399 RP-000227 400 RP-000227 401 RP-000227 402 RP-000227 404 RP-000227 408 RP-000227 409 RP-000227 410 RP-000227 412 RP-000227 414 RP-000227 415 RP-000361 356 RP-000361 403 RP-000361 413 RP-000361 416 RP-000361 417 RP-000361 418 RP-000361 419 RP-000361 420 RP-000361 421 RP-000361 422 RP-000361 424 RP-000361 425 RP-000361 426 RP-000361 427 RP-000361 428 RP-000361 430 RP-000361 431 RP-000361 432 RP-000361 434 RP-000361 435 RP-000362 437 RP-000362 438 RP-000362 439 RP-000362 440 RP-000362 441 RP-000362 442 RP-000362 444 RP-000362 445 RP-000362 448 RP-000362 449 RP-000362 450 RP-000362 451 RP-000362 452 RP-000362 453 RP-000362 454 RP-000362 455 RP-000362 456 RP-000362 457 RP-000362 459
Rev Subject/Comment 1 Radio Bearer identity for CCCH 1 1 2 ASN.1 definitions for RRC information between network nodes NAS Routing DPCCH power control preamble Modifications of Assisted GPS Messages Choice of Initial UE Identity ANSI-41 information elements 1 1 1 1 1 1 3 3 3 2 2 RLC value ranges HFN Reset Clarification on ciphering parameters and integrity protection procedure in case of SRNS relocation Clarification of compressed mode activation and configuration failure Modification of the RLC Size IE CPCH DL Power control SFN measurements in TDD Clarification on multiplicity of PCH and PICH and S-CCPCH selection Parameters to be stored in the USIM Optimization of Inter-system handover message Timing Advance in Handover Procedures Synchronization of Timing Advance and Timing Deviation Measurement Downlink Physical Channels Per Timeslot TDD Mode DCH Reception in Cell DCH State 2 1 Downlink Power Control During DTX in TDD Mode Paging Indicator Length Definition Updating & alignment of RRC containers & handover to UTRAN information transfer Default values for UE timers and counters 1 1 Security mode control Corrections and Editorial updates to chapter 8 Corrections and editorial updates to chapter 10 Transition from CELL_DCH to CELL_PCH and URA_PCH state Assisted GPS Messaging and Procedures 2 4 3 Corrections to Activation Time use Editorial Corrections to measurement reporting range Default DPCH offset value and DPCH offset RLC info Clarification of the description of IE semantics in "RB with PDCP information" Editorial corrections on security Editorial correction to RB mapping info 1 Compressed mode configuration failure Gain factors for TDD Introduction of Default DPCH Offset Value in TDD 1 1 2 Optimization of handover to UTRAN command Editorial corrections Mapping of channelisation code DL TFCS Limitation SIB offset RRC CONNECTION RELEASE cause Addition of RACH TFCS 2 1 1 2 Cell Identity Editorial Modifications TDD PRACH Power Control for Spreading Factor 8/16 TDD CCTrCH Repetition Length Definition Reporting threshold of traffic volume measurements UP GPS assistance data for SIB
Old 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0
New 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0
09/2000
RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09
3GPP
Release 6
1231 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09
TSG Doc. CR RP-000362 461 RP-000363 462 RP-000363 463 RP-000363 464 RP-000363 465 RP-000363 466 RP-000363 467 RP-000363 469 RP-000363 470 RP-000363 471 RP-000363 472 RP-000363 474 RP-000363 476 RP-000363 477 RP-000363 478 RP-000363 479 RP-000363 480 RP-000363 481 RP-000363 483 RP-000363 485 RP-000363 486 RP-000364 487 RP-000364 490 RP-000364 492 RP-000364 494 RP-000364 496 RP-000364 497 RP-000364 498 RP-000364 499 RP-000364 500 RP-000364 501 RP-000364 502 RP-000364 503 RP-000364 504 RP-000364 505 RP-000364 506 RP-000364 507 RP-000364 508 RP-000364 509 RP-000364 510 RP-000364 511 RP-000365 512 RP-000365 513
Rev Subject/Comment 1 Support of cell update confirm on CCCH 1 3 1 1 1 1 2 Max Window Size in RLC capabilities UE handling of CFN Correction of padding description in clause 12 Window size in RLC info TFC Control Duration System Information Block Tabular Information Frequency encoding in inter-system handover messages RRC message size optimization regarding TFS parameters RACH selection DRX cycle lower limit 1 1 1 1 1 1 1 1 1 1 3 1 2 1 1 1 1
Old 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0
New 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0
Rx window size in RLC info 3.3.0 Corrections & optimizations regarding system information blocks of 3.3.0 length 215..221 Corrections on 8.1.1 resulting from RRC review at R2#14 3.3.0 Corrections to the RRC connection release procedure New release cause for signalling connection re-establishment Correction to IE midamble shift and burst type Correction in RLC info Description of CTCH occasions TDD CCTrCH UL/DL Pairing for Inner Loop Power Control DCCH and BCCH Signalling of TDD UL OL PC Information Broadcast SIBs for TDD UL OL PC Information CPCH corrections Corrections to Security IEs Corrections to parameters to be stored in the USIM Editorial corrections Physical Shared Channel Allocation procedure Correction to Transport Format Combination Control Message Usage of Cell Parameter ID RB description for SHCCH Use of LI in UM Minor Corrections to RRC Protocol Specification Correction to Cell Update Cause Correction on T307 definition Corrections to relative priorities in RRC Protocol Unification of Reconfiguration Procedures 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0
1 1
Changes to section 8.2 proposed at Paris RRC Ad Hoc Establishment Cause PRACH partitioning Editorial Correction on Active Set Update Editorial Correction regarding system information Clarification on Reporting Cell Status
1 1
RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09
RP-000365 514 RP-000365 515 RP-000365 516 RP-000365 517 RP-000365 518 RP-000365 519 RP-000365 520 1 1
Editorial corrections on RRC Connection Establishment and 3.3.0 Release procedures NOTE: In subclause 8.1.4.6, the change from "decrease" to "increase" for V308 was decided to be incorrect after discussion on the TSG-RAN WG2 reflector and was not implemented Gated Transmission Control Info 3.3.0 Cell selection/reselection parameters for SIB 3/4 3.3.0 Implementation of Ec/N0 parameters and optimization of SIB 11/12 3.3.0 PRACH Info Uplink DPCH power control info AICH power offset value range Direct paging of RRC connected UE in CELL_PCH/URA_PCH NOTE: This CR was postponed in TSG-RAN #9 and was wrongly included in v3.4.0. This was corrected in v3.4.1 Corrections to Sections 1-7 Error handling for Uplink Physical Channel Control procedure 3.3.0 3.3.0 3.3.0 3.3.0
3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0
RP-09 RP-09
RP-000365 521 RP-000365 522
3.3.0 3.3.0
3.4.0 3.4.0
3GPP
Release 6
1232 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 RP-09 -
TSG Doc. CR RP-000365 523 RP-000365 524 RP-000365 525 RP-000365 526 RP-000365 528 RP-000365 530 RP-000365 532 RP-000365 533 RP-000365 534 RP-000365 535 -
Rev Subject/Comment Corrections to downlink outer loop power control in compressed mode 1 Clarification on measurement procedure using compressed mode 1 1 1 1 1 1 1 Updates to cell and URA update procedures based on RRC Ad Hoc Updates to RNTI allocation procedure based on RRC Ad Hoc PRACH constant value Corrections to the paging procedure Moving of text from 25.304 Message extensibility Additions to "State of RRC Procedure" in RRC Initialisation information, source RNC to target RNC Support of codec negotiation Removal of contents of CR 520 from v3.4.0, because it was postponed at TSG-RAN #9 and by accident included anyway. Downlink outer-loop power control in compressed mode Correction in the use of "U-RNTI Short" Corrections related to UE Timing Corrections to SFN-SFN definition 1 1 1 1 1 1 Corrections to definition and use of Activation Time Corrections to logical channel priorities Correction to codec negotiation CFN-SFN observed time difference measurement Correction to timing indication for hard handover UE Radio Access Capability Corrections RRC establishment and paging causes for NAS signalling Corrections to Intra-frequency measurements and Traffic volume measurements PRACH/RACH System information GSM Measurement reporting BLER measurement and quality target Clarification of PDCP sequence number window terminology Clarification on Error Handling Removal of compressed mode measurement purpose "other" Clarification of compressed mode measurement purpose "GSM" 2 1 1 3 1 4 2 1 1 Reporting multiple GSM cells Number of RLs that can be removed in Active Set update Clarification on Segment Index
Old 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.4.0 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1
New 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.1 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0
12/2000
RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10
RP-000570 536 RP-000570 537 RP-000570 538 RP-000570 539 RP-000570 541 RP-000570 542 RP-000570 543 RP-000570 544 RP-000570 545 RP-000570 546 RP-000570 548 RP-000570 549 RP-000570 551 RP-000570 553 RP-000570 554 RP-000570 556 RP-000570 559 RP-000570 560 RP-000570 561 RP-000570 564 RP-000571 566 RP-000571 568 RP-000571 571 RP-000571 572 RP-000571 573 RP-000571 574 RP-000571 575 RP-000571 576 RP-000571 577 RP-000571 578 RP-000571 580 RP-000571 581 RP-000574 583 RP-000571 584 RP-000571 585 RP-000571 586 RP-000571 587 RP-000571 590 RP-000571 592 RP-000571 595 RP-000571 596
1 1 1 1 1
RRC procedure performance requirements 3.4.1 Correction of newInterSystemCellList and 3.4.1 MeasurementControlSysInfo in ASN.1 Removal of Flow Id concept while maintaining Iu interface flexibility 3.4.1 Ciphering and reset Corrections and clarifications concerning inter-RAT change procedures General Security Clarifications Clarification on RB 0 Clarification on the transition of RRC state 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1
1 1 1
UP measurements for RRC information to target RNC Correction on LCS reporting criteria CSICH Corrections Clarification to handling of satellite health issues Clarification on activation time Clarification on activation time for ciphering in TM
2 1 1 4 1
Measurement procedures and messages Inter-RAT UE radio access capability Clarification on cell update/URA update procedures Protocol States and Process System Information
3GPP
Release 6
1233 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10 RP-10
Rev Subject/Comment 5 RRC Connection Management Procedures, Generic procedures and actions 1 Paging Procedures NAS signalling Procedures 3 1 2 1 1 2 2 1 2 Radio Bearer Control Procedures Corrections to the Counter Check Procedure Tabular Information and ASN.1 Corrections to Measurement Occasion concept Corrections concerning optimisation of RB information Corrections to security Ciphering activation time for DPCH Confirmation of signalling connection establishment RACH Sub-channel signalling Assistance data delivery for UP Clarification of LCS measurements Configuration of RLC PDU sizes for logical channels PICH power offset for TDD Correction for PDSCH power control for TDD Usage of dynamic spreading factor in uplink Correction of Midamble Shift for Burst Type 3 Correction of text concerning Scheduling of System Information 1 1 1 Clarification of RB mapping info Correction to UE multi-RAT capability Correction to PDCP sequence number exchange during hard handover DCH Quality Target Simultaneous release of RBs and signalling connection Correction on Transport Channel Reconfiguration Limitation of DRX cycle length Signalling of the alpha value in TDD for open loop power control Support for improved compressed mode handling for TDD measurements Usage of secondary CPICH and secondary scrambling code Expiration time of SIB type 7, 14 Correction to integrity protection Downlink Outer Loop Control 2 1 2 2 RL Failure in cell update procedure Clarification on COUNTER CHECK Traffic Volume Measurement corrections Reserved TFCI for the TDD Special Burst Correction to description of RRC state transitions RLC re-establish correction 1 1 Removal of RLC logical channel mapping indicator New paging and establishment cause "Unknown" Miscellaneous procedure corrections Corrections to compressed mode pattern sequence handling Inter-system change clarifications 1 1 2 4 2 1 2 1 RLC status transmission in CELL_PCH and URA_PCH Clarification of RB information parameter values for SRB0 Encoding for RRC- container Update of message extension and encoding descriptions Introduction of default pre-defined configurations Security corrections Clarifications on Blind Handover Support Missing descriptions of UE actions Corrections on UE Positioning information Security related corrections to SRNS
Old 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.4.1 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0
New 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0
Alignment of GSM'99 BA Range concept and its inclusion in UTRA 3.4.1
2 1
03/2001
3GPP
Release 6
1234 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11 RP-11
TSG Doc. CR RP-010032 675 RP-010274 676 RP-010030 678 RP-010030 679 RP-010030 680 RP-010030 681 RP-010030 682 RP-010030 684 RP-010030 685 RP-010030 686 RP-010030 687 RP-010030 688 RP-010030 689 RP-010030 690 RP-010030 691 RP-010030 693 RP-010030 694 RP-010030 696 RP-010030 698 RP-010030 700 RP-010030 701 RP-010030 702 RP-010031 703 RP-010031 704 RP-010031 705 RP-010031 710 RP-010031 711 RP-010031 712 RP-010031 713 RP-010031 714 RP-010031 715 RP-010031 716 RP-010031 717 RP-010031 718 RP-010031 719 RP-010031 720 RP-010031 721 RP-010031 723 RP-010031 724 RP-010031 725 RP-010042 683 RP-010041 692 RP-010037 706 RP-010037 707 RP-010037 708 RP-010037 709 RP-010040 722 RP-010039 726 RP-010311 731 RP-010311 733 RP-010311 735 RP-010311 738
Rev Subject/Comment 2 Downlink power offsets 2 1 1 2 2 1 1 1 1 Checking the integrity of UE security capabilities Clarification to Secondary CCPCH info Miscellaneous corrections Removal of Layer 3 filtering for RACH Correction of compressed mode parameters Removal of immediate cell evaluation Scheduling of SIB 15.2 and SIB 15.3 Correction to ECN modules Improvement of the description of timing advance for TDD Correction on timing advance and allocation for shared channels Clarification on SF 1 signalling Correction to power control in TDD Midamble - Channelisation code association for TDD System Information 1 1 2 1 2 2 1 2 1 1 1 1 Clarification on Transport Channel Identity Editorial Correction Correction to add coding of intra domain NAS node selector Corrections to system information block characteristics in TDD ASN.1 corrections Measurement related corrections Clarifications on TFC Control procedure Association of PLMN ID to neighbour cells TFCS Selection Guidelines Special Burst Scheduling During DTX in TDD Radio Link Failure Criteria in TDD Correction & Clarification to TDD RACH Subchannels Number of retransmission of RRC CONNECTION REQUEST Uplink Frequency Notification Clarification of Radio Bearer Mapping for DCH/DSCH Transport Channels Correction of mismatches between tabular and ASN.1 Correction to discontinuous reception in TDD Power control preamble 1 3 1 Maximum number of AM entity Real-time Integrity Broadcast Moving Real-time Integrity description to different chapter Removal of the payload unit concept Security related corrections to SRNS Periodic PLMN selection correction 1 1 1 2 1 Modification of "SSDT Information" IE parameters to indicate if SSDT is used in the UL only Idle allocation for Node B synchronisation
Old 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.6.0 3.6.0
New 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 3.6.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.1.0 4.1.0 4.1.0 4.1.0
Network requested reporting for physical shared channel allocation 3.5.0
Physical channel configuration information elements for 1.28 Mcps 3.6.0 TDD Changes to Measurement Related Signalling and Introduction of 3.6.0 Cell (Re)selection Parameters for 1.28Mcps TDD Introduction of RACH Parameters for 1.28 Mcps TDD 3.6.0 Introduction of UE radio access capability Parameters for 1.28 Mcps TDD Introduction of IPDLs for TDD ROHC updates to RRC Clarification of the IE 'spreading factor' in Uplink DPCH info for FDD mode Correction of UE Radio Access Capability depending on UTRAN FDD bands Clarification on Security mode control Correction of TrCH parameter handling 3.6.0 3.6.0 3.6.0 4.0.0 4.0.0 4.0.0 4.0.0
1 1
06/2001
RP-12 RP-12 RP-12 RP-12
3GPP
Release 6
1235 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12 RP-12
Rev Subject/Comment TFC Subsets in TDD RRC containers Various corrections General error handling for system information Order of elements in strings Configuration consistency checks Compressed mode corrections Correction concerning inter-RAT procedures Measurement corrections RLC Tr Discard Annex B CPCH Correction SIB Correction for CSICH Power Offset Transfer of Last known position in case of SRNS relocation Corrections to UE Positioning measurements GSM measurements in compressed mode Correction of Activation Time in Inter-Rat HO Commands Clarification of FRESH in SRNS relocation Correction to UE timers and constants in idle mode Clarification on multiframe allocation in TDD Predefined parameters for logical channels Pathloss calculation Clarification on periodic measurement reporting 1
Old 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0
New 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0
Handling of IE PRACH TFCS and Primary CPICH/Primary CCPCH 4.0.0 info Correction to FACH measurement occasion in TDD 4.0.0 Clarification of L1 synchronization procedures Correction of Activation Time definition Corrections to RRC procedure performance Removal of mapping function Security clarifications Corrections to UE Positioning Definition of DPCH numbering Corrections to System Information Procedure Relation between DOFF and DPCH Frame Offset Procedures for "same as UL" Editorial and minor corrections Editorial Correction Corrections on OTDOA-IPDL specific burst parameter semantic description Error handling for messages sent from another RAT Needed TFC in the TFCS for TDD Clarification of TFCS selection guidelines Clarification of Traffic Volume measurements CFN synchronisation problems at timing re-initialised hard handover Corrections on UP Assistance Message Descriptions Correction on Area Scope of SIB 15.3 Correction to AICH power offset Clarification on IE 'Downlink rate matching restriction information' Corrections on Tabular/ASN.1 Corrections on Tabular and ASN.1 inconsistencies Editorial corrections on Tabular and ASN.1 inconsistencies UE Positioning corrections to ASN.1 and tabular UE positioning OTDOA Neighbour Cell Info DRAC corrections ASN.1 Correction of IE TFCS ID Correction of IE IODE range in AGPS Positioning 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0
Corrections to resolve inconsistencies between Tabular and ASN.1 4.0.0
3GPP
Release 6
1236 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG Doc. CR RP-010317 897 RP-010317 899 RP-010317 901 RP-010317 904 RP-010317 906 RP-010323 773 RP-010323 850 RP-010323 851 RP-010323 902 RP-010544 0870 RP-010544 0908 RP-010544 0910 RP-010544 0912 RP-010544 0914 RP-010544 0916 RP-010544 0918 RP-010544 0920 RP-010544 0922 RP-010544 0924
Rev Subject/Comment Correction to BurstModeParameters in IPDL Corrections on inconsistencies between Tabular and ASN.1 Naming of message abstract types in ASN.1 Information elements outside the extension container Correction concerning DRX cycle upon inter-RAT change towards UTRAN Corrections to IPDLs for TDD 2 1 Correction to 1.28Mcps TDD RACH parameters and operation TFCI coding in case of 8PSK Structure and naming of information elements UL Transport Channel Type Correction Guidelines concerning conditions, spares, defaults and correction of inconsistencies Correction to TDD DL DPCH Common Timeslot Info TDD System Information Update in Cell_DCH Editorial Corrections UL DPCH Power Control Info in TDD CN-originated paging in CELL_PCH and URA_PCH state Corrections to UE variable handling Inter-frequency measurements Inter-RAT measurements Intra-frequency measurements Multiplexing configuration corrections Reception of non-dedicated control channels mapped on FACH in CELL_FACH state Removal of C-RNTI when entering CELL_DCH TF and TFC set definition Correction of remaining ASN.1/Tabular inconsistencies CPICH Ec/N0 Range Priorities for IDNNS coding Dedicated pilots and S-CPICH specification related to UE specific beamforming Security corrections Intra-frequency measurement events for TDD corrections Inconsistencies between ASN.1 and tabular format TDD PICH corrections and clarifications Messages on CCCH Clarification of Parameter Values for Default Radio Configurations Clarification to usage of default values in "Cell Selection and Reselection for SIB11/12Info" Clarification of handling of System information block 14
Old 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0
New 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0
09/2001
RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13
RP-010671 0926 1 RP-010545 0928 RP-010545 0930 RP-010545 0932 RP-010545 0935 RP-010545 0937 RP-010545 0939 RP-010545 0941 RP-010545 0943 RP-010545 0945 RP-010546 0953 RP-010546 0955 RP-010546 0957 RP-010546 0959 RP-010546 0961 RP-010546 0963 RP-010546 0965 RP-010546 0967 RP-010546 0982 RP-010546 0984 RP-010547 0986 RP-010547 0988 RP-010547 0990 RP-010547 0992 RP-010547 0994 RP-010547 0996 RP-010547 0998 1 RP-010547 1000 RP-010547 1004 RP-010547 1006 RP-010548 1008 RP-010548 1010
Description of UE behaviour when receiving UE positioning related 4.1.0 information Clarification on periodic measurement reporting 4.1.0 Corrections and clarifications on Measurement procedures description Lossless Criteria in PDCP Info Corrections to cell reselection parameter values Correction to signalling connection release Corrections to cell update procedures PDCP configuration and PS domain configuration checks Correction to handling of RRC transaction identifier for Cell Update, URA Update and RRC connection setup Correction of UE capabilities regarding Rx-Tx time difference type 2 measurement Correction to handling of IE 'Downlink info for each radio link' Redundant IE in Traffic volume measurement system information Editorial corrections MAC logical channel priority added to definition of RB0 and SHCCH Control of primary CCPCH RSCP measurement in PUSCH 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0
3GPP
Release 6
1237 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13 RP-13
TSG Doc.
CR
Rev Subject/Comment CAPACITY REQUEST message Various minor corrections Range of T312 Bitstring of channelisationCodeIndices Transmission of UE CAPABILITY INFORMATION message
Old 4.1.0 4.1.0 4.1.0 4.1.0
New 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.1 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0
RP-010548 1014 RP-010548 1016 RP-010548 1018 RP-010548 1020 RP-010548 1022 RP-010548 1024 RP-010548 1026 RP-010548 1028 RP-010549 1030 RP-010549 1034 RP-010549 1036 RP-010549 1038 RP-010549 1048 RP-010549 1050 RP-010549 1052 RP-010549 1062 RP-010549 1066 RP-010549 1068 RP-010550 1076 RP-010550 1082 RP-010550 1086 RP-010554 0933 RP-010554 0946 RP-010554 0970 RP-010554 0971 1 RP-010554 0972 RP-010554 0973 RP-010554 0974 -
Multiple UE capabilities procedures 4.1.0 Corrections to information elements outside the extension container 4.1.0 SFN reporting TFCI combining indicator RLC reset on a Signalling Radio Bearer Quality Indication for UE Positioning Parameters Editorial Correction for UE Positioning Clarification on the current status of ciphering Clarification on HFN initialization at SRB and RB setup Clarification on Inter-RAT measurement Clarification on re-assembly of segments Minor Corrections Support of dedicated pilots for channel estimation Correction to SRNS relocation handling Correction to RLC state variables Reading of CN information in SIB 1 inRRC Connected Mode Restricting the maximum amount of preconfigurations in case of equivalent PLMNs Order of bits in bitstrings Selection of the RFC3095 CID transmission Correction of IPDL parameters for TDD enhancements in ASN.1 description 1.28 Mcps TDD PICH, Midamble and UL timing advance control corrections Introduction of 1.28 Mcps TDD Mode in clause 13.7 Tadv in 1.28 Mcps TDD Correction and clarification to PRACH in 1.28 Mcps TDD 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0
10/2001 12/2001
RP-010763 1088 RP-010763 1090 RP-010763 1098 RP-010763 1100 RP-010763 1102 RP-010763 1104 RP-010763 1109 RP-010763 1111 RP-010763 1113 RP-010763 1115 RP-010764 1117 RP-010764 1119 RP-010764 1124 RP-010764 1126 RP-010764 1132 RP-010764 1134 RP-010764 1136 RP-010764 1138 RP-010764 1142 RP-010765 1144 RP-010765 1146
Replacement of incorrect (R'99) version of ASN.1 by correct (Rel-4) 4.2.0 version of ASN.1. Corrections to RRC information containers 4.2.1 Removal of Block SSTD COUNT-C-SFN frame difference measurement Trigger for deletion of ciphering and integrity keys Preconfigurations in case of equivalent PLMNs Handling of DRX cycle and U-RNTI in RRC connection setup and handling of TrCH information Correction to Information Element names Correction of Description of IE "SSDT Information" 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1
Correction to P_compensation calculation for GSM neighbour cells 4.2.1
Clarification on Cell Identity and correction to reference to 4.2.1 BAND_INDICATOR Clarification to Measured Results on RACH and Measurement 4.2.1 Events Inconsistency between ASN.1 and tabular wrt. RPLMN information 4.2.1 General clarification on Establishment of Access Service Classes Clarification on TX diversity indicator IE and STTD indicator IE Different diversity modes used in the same active set Issues regarding signalling connection establishment and RRC connection release Presence of AC to ASC mapping in SIB5 and SIB6 RRC establishment cause at inter-RAT cell change order to UTRAN Start of timers at radio link failure Handling of the number of FBI bits sent in Uplink DPCH info Bit string order when using PER 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1
3GPP
Release 6
1238 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14 RP-14
TSG Doc. CR Rev Subject/Comment RP-010765 1148 Clarification on DRX cycle length in connected mode RP-010765 1152 RP-010765 1154 RP-010765 1156 RP-010765 1158 RP-010765 1166 RP-010765 1168 RP-010765 1170 RP-010766 1172 RP-010766 1174 RP-010940 1178 1 RP-010766 1180 RP-010766 1182 RP-010766 1184 RP-010941 1186 1 RP-010766 1203 RP-010766 1214 RP-010766 1220 RP-010767 1222 RP-010773 1096 RP-010773 1120 RP-010773 1199 RP-010773 1200 RP-010773 1201 RP-010773 1206 RP-020070 1229 RP-020070 1231 RP-020070 1233 RP-020070 1237 RP-020070 1239 RP-020070 1241 RP-020070 1243 RP-020070 1245 RP-020070 1247 RP-020070 1249 RP-020071 1251 RP-020239 1253 1 RP-020071 1258 RP-020071 1260 RP-020071 1262 RP-020071 1268 RP-020071 1271 RP-020071 1273 RP-020071 1275 RP-020071 1277 RP-020072 1279 RP-020072 1281 RP-020205 1283 1 RP-020072 1285 RP-020072 1287
Old 4.2.1
New 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0
Correction to error condition on downlink information for each radio 4.2.1 link Correction of inconsistencies between tabular and ASN.1 4.2.1 Measurement related corrections Inconsistency between hard-coded preconfigurations parameters and procedure text PLMN search in CELL_PCH/URA_PCH states with 80ms DRX cycle Correction to CFN calculation for FDD Correction to radio bearer control Handling of IE "frequency info" Correction to Radio Bearer Release Correction to RACH reporting Correction to URA/Cell update and other minor corrections Correction to Active Set Update Correction of Traffic Volume Measurement Criteria Correction of UE Positioning Invalid RRC CONNECTION REJECT Security baseline for corrections Pending integrity protection activation time for UL RB0 Correction of rate matching restriction function Usage of UM RLC Special Length Indicator Corrections to REL-4 LCR Tabular Description and ASN1 Code Correction of FPACH parameter definition for 1.28Mcps TDD Correction of 1.28Mcps TDD Correction and Clarification to Open Loop Power Control in 1.28 Mcps TDD Extensions of IE value ranges in tabular Constant value range correction for DPCH and PUSCH in TDD mode Corrections to open loop power control for TDD and RB information parameters for SHCCH Removal of unnecessary replication of TFCS ID in Physical Shared Channel Allocation message Correction to TF selection when using UL RLC TM Correction to the UE behaviour in case of SRNS relocation Header Compression protocols re-initialisation during SRNS Relocation Misalignments between tabular and ASN.1 related to UE Positioning, tabular correction Corrections to comments in ASN.1 Correction to restarting of T308 Clarification of the use of T309 during inter-RAT cell reselections Measurement Corrections Existence of TFCI bits Corrections of inconsistency between procedural description, tabular and ASN.1 Corrections to Expiration Time Factor and Expiration Time formula for SIB 7 and SIB 14 Corrections to Reporting Cell Status Correction to inter frequency measurements Actions at reception of system information block type 1 Tx diversity and no diversity in the same active set Correction to cell update Successful and unsuccessful procedures Measurement related corrections Clarifications on Event 1D Security corrections Transition from CELL_DCH to CELL_FACH state Corrections and clarifications of Radio link timing 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0
03/2002
RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15
3GPP
Release 6
1239 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15 RP-15
TSG Doc. CR Rev Subject/Comment RP-020072 1289 Spare values in ASN.1 RP-020072 1294 RP-020231 1296 1 RP-020072 1298 RP-020072 1307 RP-020072 1313 RP-020072 1317 RP-020073 1319 RP-020073 1323 RP-020250 1331 1 RP-020249 1333 1 RP-020073 1337 RP-020073 1339 RP-020074 1343 RP-020074 1345 RP-020073 1347 RP-020073 1349 RP-020073 1351 RP-020073 1353 RP-020073 1358 RP-020074 1360 RP-020074 1362 RP-020210 1364 RP-020228 1366 RP-020233 1368 RP-020238 1370 RP-020082 1122 2 RP-020082 1187 2 RP-020082 1188 2 RP-020082 1223 1 RP-020082 1254 RP-020082 1290 RP-020082 1335 RP-020084 1129 2 RP-020090 1225 1 RP-020085 1291 1 RP-020094 1305 2 RP-020330 1373 RP-020330 1376 RP-020330 1379 RP-020330 1382 RP-020330 1385 1 RP-020330 1388 RP-020331 1392 RP-020331 1395 RP-020331 1398 RP-020331 1401 RP-020331 1404 RP-020331 1407 RP-020332 1410 Actions on reception of measurement related IEs Removal of channel coding option "no coding" for FDD and 3.84 Mcps TDD Timing Indication when moving to CELL_DCH state Correction to processing RB mapping info RRC Connection Release following network authentication failure Clarification on serving cell in SIB11 Treatment of optional elements in RB control messages Procedure Performance for TDD UL physical Channel Control Clarification to physical channel establishment criteria OTDOA Assistance Data Retransmission of uplink direct transfer at RLC re-establishment and inter-RAT change Correction to IE "UL interference" for UTRA TDD Corrections of UE Positioning requirements Multimode speech in default configurations Correction to UE Id for DSCH Corrections to support combined Cell/URA update and SRNS relocation Number of UTRAN and Inter-RAT frequencies Abortion of signalling connection establishment Modification of GPS timing representation to avoid large integers Additional TFCS selection guidelines Clarification of layer 3 filtering of measurements in the UE Improved readability of procedural text Clarification on ICS version within UE radio access capabilities Clarification of Maximum number of TFC in the TFCS Support of UP measurement reporting in CELL_PCH/URA_PCH Correction to include Cell ID for Cell_DCH state Correction of Transparent mode signalling for UL rate control Introduction of default radio configurations for UMTS_AMR2 with four speech modes Acquisition of PLMN identity of neighbour cells via SIB 18 Various ASN.1 Corrections Handover from UTRAN failure Corrections to indicate that SIB 14 is not used by 1.28 TDD Support of flexible hard split mode Introduction of the parameters of OTDOA with IPDL for 1.28 Mcps TDD Radio link timing Introduction of HSDPA ASN.1 Corrections Clarification of unnecessary MP IEs in RADIO BEARER RECONFIGURATION Correction on SIB type
Old 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.4.0 4.4.0 4.4.0 4.4.0 5.0.0 5.0.0 5.0.0
New 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 5.0.0 5.0.0 5.0.0 5.0.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0
06/2002
RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16
Clarification to the handling of IE "Cells for measurement" received 5.0.0 in SIB 11/12 Correction to Cell Update procedure 5.0.0 Correction to handling of FACH measurement occasion info in SIB12 Actions when optional IE "Maximum allowed UL TX power" is missing Corrections concerning default configurations Correction concerning when hard handover specific handling applies Handling of variables CELL_INFO_LIST and MEASUREMENT_IDENTITY IE "Cell Synchronisation Information" Corrections to Cell Individual Offset Clarification to Compressed Mode Status Info 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0
3GPP
Release 6
1240 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16
TSG Doc. CR Rev Subject/Comment RP-020332 1413 Clarification of OTDOA quality figure RP-020332 1416 RP-020332 1419 RP-020332 1423 RP-020332 1426 1 RP-020333 1429 1 RP-020333 1432 RP-020333 1435 RP-020333 1438 RP-020333 1441 RP-020333 1444 1 RP-020334 1447 RP-020334 1450 RP-020334 1453 RP-020334 1456 RP-020334 1459 1 RP-020334 1462 RP-020335 1465 RP-020335 1468 1 RP-020335 1471 RP-020382 1480 1 RP-020363 1483 RP-020381 1486 1 RP-020335 1489 RP-020336 1492 Correction to Cell Access Restriction for SIB4 Corrections concerning spare values and comments Variable for shared channel configurations Integrity protection on RB0 Periodic cell update clarifications Multiple cells triggering event 1D Disjoint Active Sets in the Active Set Update procedure Deletion on compressed mode patterns when moving to CELL_FACH state TDD C-RNTI in Cell DCH CCTrCH Release in TDD Layer 3 retransmission of SIGNALLING CONNECTION RELEASE INDICATION Alignment of tabular and ASN.1 for UTRAN GPS timing of cell frames resolution Correction to Default Radio Configuration Timers Clarification to number of L3 filters Correction to 3G to 2G Inter-RAT handover for multi-domain RABs DCH quality target Correction to RB Mapping Info Ciphering activation for TM bearers TFCS selection guideline correction Clarification of Measurement Validity and Valid Measurement Objects Remaining clarification of Measurement Validity and Valid Measurement Objects Traffic Volume Measurement clarifications Correction to handling of IE 'Downlink information for each RL' Corrections to Security procedure on Missing integrity protection reset on relocation and counter check response actions for asymmetric bearer configurations Corrections to cell update interactions with security and SRNS Relocation "Out of service" area definition RRC connection release procedure in CELL_DCH state Correction to DL TM DCCH TF size for Default Configurations Corrections in ASN.1 related to SRNS relocation HS-DSCH related corrections RFC 3095 context relocation UE behaviour when active set cells are not included in CELL_INFO_LIST Corrections to handling of IE "Cells for measurement" Clarification on the use of UE radio access capability extensions within the INTER RAT HANDOVER INFO message Correction to RRC connection procedure Correction to the variable TGPS_IDENTITY Missing IEs in RLC info Corrections of UE internal measurement reporting events UE behaviour upon reception of reconfiguration
Old 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0
New 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0
RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 RP-16 09/2002 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17
RP-020336 1495 RP-020336 1498 RP-020339 1473 RP-020339 1475 RP-020339 1477 RP-020341 1499 RP-020341 1500 RP-020345 1501 RP-020541 1504 1 RP-020541 1507 1 RP-020541 1510 RP-020541 1513 RP-020541 1516 RP-020541 1522 RP-020542 1528 1 RP-020542 1531 2 RP-020542 1534 RP-020542 1537 1 RP-020542 1540 RP-020542 1543 RP-020543 1546 RP-020543 1551 RP-020543 1554 RP-020543 1557
5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0
5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0
Removal of BLER threshold from IE "Measurement Feedback info" 5.0.0
Application of integrity keys in case of a pending CN domain switch 5.1.0 during a SRNS relocation Clarifications on Quality Measurements 5.1.0 Correction of DPCH constant value in TDD default radio configurations Handling of UE internal measurement information in broadcast Observed time difference to GSM reporting indicator Corrections on Security relative to ciphering of TM bearers and to SRNS relocation Coding of IE NC mode Clarification to filtered measurement quantities 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0
3GPP
Release 6
1241 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17 RP-17
TSG Doc. CR Rev Subject/Comment RP-020543 1560 Inconsistencies in triggering and reporting for events 1a, 1b,1c, 1e and 1f RP-020543 1563 1 Optional and Mandatory fields in Measurement Control RP-020544 1566 RP-020544 1569 RP-020544 1572 RP-020544 1578 2 RP-020544 1581 RP-020544 1584 RP-020545 1587 RP-020545 1590 RP-020545 1593 RP-020545 1596 RP-020630 1599 1 RP-020545 1602 RP-020546 1605 RP-020546 1608 RP-020654 1611 1 RP-020546 1614 RP-020546 1617 RP-020546 1620 1 RP-020547 1623 RP-020547 1626 RP-020547 1629 RP-020547 1632 RP-020547 1635 RP-020547 1638 RP-020548 1641 RP-020548 1644 RP-020548 1647 RP-020548 1650 1 RP-020548 1655 RP-020548 1670 RP-020631 1673 1 RP-020549 1676 RP-020549 1679 RP-020549 1682 RP-020558 1575 1 RP-020559 1661 RP-020553 1657 RP-020553 1659 RP-020553 1663 RP-020553 1665 RP-020553 1667 RP-020557 1547 RP-020662 1651 2 RP-020557 1652 RP-020590 1683 RP-020557 1684 RP-020721 1687 Clarifications to Reporting Cell Status Clarification to minimum SF Clarifications to inter-frequency measurements Ciphering when HO to UMTS of signalling only connection Inter RAT handover from UTRAN Correction to Cell Update procedure with cause "Radio link failure" Correction to the handling of IE "UTRAN DRX cycle length coefficient" in CELL/URA UPDATE procedure Correction to RLC unrecoverable error occurs in CELL_DCH state Use of scrambling change when activating CM pattern using SF/2 by MEASUREMENT CONTROL Actions when optional IE "Maximum allowed UL TX power" is missing IP_offset correction Clarification on the IE "Frequency Info"
Old 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0
New 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.3.0
Correction of RNTI used in PUSCH capacity request and physical 5.1.0 shared channel allocation Correction to allowed logical channel list choice for RACH transport 5.1.0 channels Clarification of SRNS Relocation Info 5.1.0 DCH quality target Handling of variables CELL_INFO_LIST and MEASUREMENT_IDENTITY(2) Correction of secondary CCPCH selection and PRACH selection RRC TVM Corrections Correction of Transmission Gap Distance semantics description UE behaviour following RLC size change RRC SN in uplink Multiplexing of Tr mode RBs of different CN domains on the same transport channel Security clarifications Correction to the actions of "out of service area" and "in service area" TVM: pending time after trigger and initial conditions Handling of Downlink information for each RL in reconfiguration messages Corrections to Cell Update/URA Update Procedure in case of nested cell updates and simultaneous SRNS relocation Corrections to security SRNS relocation with integrity Reception of MEASUREMENT CONTROL in state CELL_FACH Unsupported configuration Handover corrections Correction of SFN-SFN Measurement Corrections to Synchronisation for 1.28 Mcps TDD Corrections on Power Control for 1.28 Mcps TDD Correction to RLC entity re-establishment during SRNS relocation Reintroduction of IE "SRB delay" in Rel-4 ASN.1 Corrections to ASN.1 for SRNC relocation container Unused elements in ASN.1 Correction on Radio link timing Physical layer IEs for HSDPA Transport channel information elements for HSDPA TX diversity on radio links in the active set Mandatory Support of dedicated pilots for channel estimation Corrections to IEs "Ellipsoid point with Altitude and uncertainty Ellipsoid" and "Ellipsoid point with uncertainty Ellipse" 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.2.0
Corrections to Active Set Update and simultaneous reconfiguration 5.1.0
12/2002
RP-18
3GPP
Release 6
1242 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18 RP-18
TSG Doc. CR Rev Subject/Comment RP-020721 1690 1 Handling of Ciphering and integrity protection activation times RP-020721 1693 RP-020721 1696 2 RP-020721 1699 RP-020721 1710 1 RP-020722 1713 RP-020892 1716 1 RP-020722 1719 RP-020722 1722 RP-020722 1725 RP-020722 1728 RP-020723 1731 RP-020723 1803 RP-020723 1742 RP-020723 1745 RP-020723 1748 RP-020723 1751 RP-020724 1754 RP-020724 1757 1 RP-020724 1766 RP-020724 1769 RP-020724 1772 RP-020724 1779 2 RP-020903 1734 3 RP-020727 1776 RP-020893 1810 RP-020726 1760 2 RP-020858 1701 RP-020858 1703 RP-020858 1705 RP-020858 1781 RP-020858 1783 RP-020858 1785 RP-020859 1787 RP-020859 1802 RP-020859 1805 RP-020859 1807 RP-020736 1707 RP-020736 1791 RP-020736 1792 RP-020736 1794 RP-020736 1795 RP-020736 1796 RP-020736 1797 RP-020736 1798 RP-020896 1793 2 RP-030103 1813 RP-030103 1816 RP-030103 1819 1 RP-030103 1822 RP-030103 1825 Handling of measurements at state transitions to/from DCH state. Measurement related corrections ASN.1 of the SRNS relocation info Corrections to PRACH selection TDD Downlink Path Loss for interfrequency measurement Correction on coding of GSM Classmark 2 and 3 Correction on Frame Allocation Calculation Inter-frequency measurements Maximum Allowed UL TX Power START values for the initialisation of SRB counters and UTRAN incorrect actions Correction to the RRC transaction table management Use of DCH Quality Target with Blind Transport Format Detection
Old 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0
New 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0
Correction to storing current TFC subset in variable TFC_SUBSET 5.2.0 for TDD Security at inter-RAT handover 5.2.0 Integrity protection activations times Additional measurements 5.2.0 5.2.0
DPCH compressed mode info in Downlink information common for 5.2.0 all RLs Handling of RB mapping 5.2.0 RLC window size in default configurations Corrections to Activation time Numbering of "ASC Setting" IEs included in "PRACH partitioning" IE Correction on support for compressed mode Introduction of backwards compatible correction mechanism Signalling of the timing adjustment mode for closed loop Tx diversity Handling of hyper frame numbers Early UE Specific Behaviour Information in RRC Connection Request / interRAT info Correction of ASN1 IE "InterFreqCellInfoList-r4" Correction of Special Burst Scheduling for TDD Correction of measurement reporting event 6f for 1.28 Mcps TDD Ciphering during SRNS relocation without reuse of COUNT-C Correction to IE Intra Domain NAS Node Selector Correction to PRACH selection Correction to reporting event 6f for FDD ASN.1 corrections Asymmetric ROHC Configuration Reference Cell for GSM OTD Measurement RRC container for RFC3095 context Correction to IE Access stratum release indicator RLC capability for HSDPA Dedicated pilot bits for HS-DSCH Expansion of CPICH RSCP range L3 Retransmission of event 1b DPC mode change in ACTIVE SET UPDATE message Correction to handling of IE 'Downlink information for each RL' HSDPA parameter value ranges ASN.1 of the SRNS relocation Info Correction to procedural text for Physical Shared Channel Allocation (TDD only) CM and state transition related to measurements, additional measurements, virtual active set and periodic measurements Physical channel failure and radio link re-establishment Correction concerning bit numbering convention 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0
03/2003
RP-19 RP-19 RP-19 RP-19 RP-19
3GPP
Release 6
1243 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-19 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20
TSG Doc. CR Rev Subject/Comment RP-030104 1831 Additional Measurement reporting list RP-030104 1834 2 RP-030104 1837 RP-030104 1840 RP-030104 1843 1 RP-030105 1846 RP-030105 1849 RP-030105 1855 RP-030082 1858 RP-030111 1860 RP-030111 1862 RP-030111 1864 3 RP-030111 1866 RP-030111 1868 RP-030117 1872 RP-030117 1873 RP-030119 1874 RP-030117 1875 RP-030117 1877 1 RP-030117 1878 1 RP-030117 1879 RP-030120 1880 RP-030105 1884 RP-030106 1887 RP-030106 1890 RP-030106 1893 1 RP-030106 1896 RP-030117 1897 RP-030111 1899 RP-030117 1900 RP-030105 1902 1 RP-030117 1903 RP-030187 1909 RP-030201 1910 RP-030293 1913 RP-030293 1916 1 RP-030293 1919 RP-030293 1922 RP-030293 1926 RP-030293 1929 RP-030294 1932 RP-030294 1937 RP-030294 1940 RP-030294 1943 1 RP-030294 1946 1 RP-030295 1949 RP-030295 1952 1 RP-030295 1955 RP-030374 1958 2 RP-030369 1978 4 Correction on RRC integrity protection procedure Reporting Cell Status and Event 2A Correction to the handling of variable TGPS_IDENTITY and IE Triggering condition 1/2 Hard handover with pending ciphering activation times Correction of default configurations Correction to UE behaviour on entering RRC Connected mode Update of Start values in USIM on inter-RAT transitions and transitions to idle mode Corrections to Channelisation Code TFCI Mapping for TDD Correction of PNBSCH for 1.28Mcps TDD Correction of SFN-SFN observed time difference for 1.28Mcps TDD ASN.1 corrections concerning missing UE capability extensions Extensions for 1.28 Mcps specific elements in system information Corrections to power control parameter signalling for 1.28 Mcps TDD TDD HS-SICH Power Control Usage of separate scrambling code for HSDPA TDD HS-DSCH midamble shift and burst type
Old 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0
New 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0
Corrections to the IE "Added or Reconfigured MAC-d flow" and the 5.3.0 associated table in 10.3.10 Network Assisted Cell Change from UTRAN to GERAN 5.3.0 Defining more than one DSCH / USCH transport channel in PDSCH and PUSCH system information (TDD only) Introducing the use of pre-defined configurations within UTRA Group release (without security Correction to Inter-RAT Measurement Report Correction of signalling of transport block size for DSCH PS service continuity when moving between 3G and 2G Multiple activations of the same compressed mode pattern Setting of ciphering activation time for TM bearers Correction of shadow CR implementation Removal of MRRU parameter in PDCP info Measurement event for evaluation of best HS-DSCH cel NAS and Integrity procedure interaction Correction to USBI GPS navigation model update mechanism Layer 3 filtering definition Handling of UP Assistance Data Concerns on Procedures for Cell-ID Positioning Method Inconsistency between Procedural, ASN.1, and Tabular Aspects of UE Positioning Error Removal of FFS (For further Study) and references to other working groups Key handling when entering idle mode and coding of security capabilities Security actions when SIM is present on RRC Connection Request Update of interfrequency measurement cell info list, reading of SIB11/12, inclusion of Measured Results on RACH Additional measurements without measurement validity Handover to UTRAN in macrodiversity TVM Reporting in CELL_PCH state Initialisation of the Virtual Active Set IE Tx diversity mode in ACTIVE SET UPDATE message Correction to transport channel traffic volume measurement events 4a and 4b Maximum Number of GPS Almanac Messages to be Stored in UE_POSITIONING_GPS_DATA Stopping of RLC entities at relocation Ciphering Mode info IE in 2G-3G Handover 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0
3GPP
Release 6
1244 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20 RP-20
TSG Doc. CR Rev Subject/Comment RP-030295 1981 START values on 2G-3G handover RP-030298 1983 RP-030298 1959 1 RP-030350 1987 2 RP-030371 1990 RP-030303 1960 RP-030303 1961 RP-030303 1963 RP-030484 1993 RP-030484 1996 RP-030520 2003 2 RP-030506 2000 1 RP-030484 2006 RP-030484 2009 RP-030485 2015 RP-030485 2018 RP-030485 2025 RP-030485 2033 RP-030485 2044 RP-030486 2048 RP-030486 2051 RP-030486 2054 RP-030486 2057 RP-030478 2064 RP-030486 2069 RP-030505 2072 1 RP-030491 2020 RP-030491 2022 1 RP-030491 2027 RP-030495 1997 RP-030495 2029 RP-030495 2030 RP-030495 2035 1 RP-030495 2039 RP-030495 2040 RP-030495 2041 RP-030449 2028 RP-030462 2061 RP-030503 2066 RP-030617 2075 RP-030625 2076 RP-030617 2079 RP-030617 2085 RP-030617 2091 3 RP-030621 2093 RP-030621 2095 RP-030617 2102 1 RP-030625 2103 RP-030611 2106 1 RP-030610 2112 2 RP-030618 2115 ROHC profile signalling Optimisation of the INTER RAT HANDOVER INFO message Corrections to security procedures in case of pending security configurations at SRNS Relocation Setting of T317 to infinity and out of service behaviour Correction to the IE HS-DSCH capability class Correction of RB mapping info in case HS-DSCH + DCH Explanation of CV-UE for the IE MidambleShift in the tabular Handling of key sets at Inter-RAT Handover to UTRAN Correction to UE Positioning privacy procedures START calculation in connected mode Reconfiguration with state transition to an indicated cell on a different frequency PRACH channelisation code list limitation to align with TS 25.221 Handling of transport channel information at radio bearer release Corrections for TDD for the IEs Downlink DPCH info common for all radio links TFCS selection guidelines for TFC Subset Value range of UE Rx-Tx time difference type 2 measurement Activation Time for DSCH Correction of PDCP Configuration for RFC 2507 Corrections to event list handling Corrections to RACH reporting Corrections to modification of Additional Measurement lists UE positioning support in the UE Elimination of EPC mechanism UE behaviour in transition from CELL_DCH to CELL_FACH/ CELL_PCH/URA_PCH and Out of Service is detected Radio link failure during reconfiguration procedure Ciphering of TM SRBs Correction on PDCP Header compression Configuration Corrections for TDD PUSCH Correction to UE behaviour on T317 expiry Correcting value range of MAC-hs buffer ID Correction of handling of IE "MAC-hs reset indicator" in Added or Reconfigured DL TrCH information UE capability signalling for UMTS1800 Handover between UTRAN and GERAN Iu mode Updated references to the RRC State Indicator IE Corrections to Event 1D Reconfiguration of MAC-d flow HS-SCCH transmit diversity mode Scrambling code & phase reference combinations for HS-DSCH (solution 2) Unsuccessful security mode control procedure and Integrity Protection START value calculation for RLC size change UE Positioning UE based assisted GPS Handling of zero-rate TrCHs in TFCS Measurement control for A-GPS Corrections to 1.28 Mcps TDD power control: ASN1/Tabular consistency, correction of omissions UpPCH power control for 1.28Mcps Interaction between compressed mode pattern activation and message activation time Initialisation of virtual active set Correction to Redirection procedure at RRC Connection Setup SFN associated with GPS timing of cell frame Correction to Handling SIB1
Old 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0
New 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.5.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0
09/2003
RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21 RP-21
12/2003
RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22
3GPP
Release 6
1245 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-22 RP-21
TSG Doc. CR Rev Subject/Comment RP-030618 2118 Measurement Handling In State Transition for UE Positioning RP-030618 2124 RP-030662 2127 1 RP-030662 2130 RP-030621 2132 1 RP-030621 2136 RP-030621 2138 RP-030625 2139 1 RP-030625 2140 RP-030713 2141 1 RP-030625 2142 RP-030625 2143 1 RP-030629 2144 RP-030625 2145 RP-030662 2148 RP-030625 2149 RP-030722 2152 3 RP-030612 2158 4 RP-030625 2159 RP-030548 2034 1 Corrections to UE positioning reporting for UE assisted and UE based methods SIB 7 reading
Old 5.6.0 5.6.0 5.6.0
New 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 5.7.0 6.0.0
HFN initialisation in case of pending security configurations 5.6.0 General protocol error handling failure for DL CCCH messages due 5.6.0 to ASN.1 error Corrections relating to 1.28 Mcps TDD 5.6.0 Missing CHOICE RLC Info type in the ASN.1 IE RBInformationSetup-r4 RRM in PCH/FACH Correction of operating band reference Re-ordering Queue and HARQ Ids 5.6.0 5.6.0 5.6.0 5.6.0
Correction to the procedural description: Reconfiguration of MAC-d 5.6.0 flow Enhancement of RRC transaction identifier for measurement 5.6.0 control message Inclusion of a default configuration identity for AMR-WB 5.6.0 TDD C-RNTI in Cell DCH Additional Measurements List Modify IP activation time for RB0 Minimum UE capability class Measured results on RACH 5.6.0 5.6.0 5.6.0 5.6.0 5.6.0
COUNT-I reverting in case Security Mode Control procedure failure 5.6.0 Maintaining the RRC Connection while Emergency camped on a F- 5.5.0 PLMN during OOS (note: it was decided that this CR would not be implemented until the Rel-6 would be created) Introduction of UMTS800 5.7.0 AS capability indication Introduction of new bands Repair of corrupted figures Response on SRNS Relocation with Cell Update TPC Combination Index in SRNC relocation Correction to "Current TGPS Status Flag" Invalidation of START value in USIM/UE. Uplink Integrity protection handling in case of N302 increment Amount of reporting for UE-based and UE assisted A-GPS Ensuring decoding possibility related to Introduction of new bands Clarification to multimode indication Correction for 1.28 Mcps TDD Power Control Missing "pdcp-SN-info" in ASN.1 IE "RB-InformationReconfig-r4" Correction to HS-SCCH info Correction to HS-SCCH info Correction to activation time for HS-DSCH reconfiguration in TDD Connected mode handling IE 'CN domain system information' in SIB1 Correction to event 6D Correction to UE positioning reporting for GPS standalone operation mode Frequency band alignment with 25.101 UTRAN setting of the activation time for TM bearers in Ciphering Mode info IE Corrections to "Entered parameter" Corrections to TFC Subset Functionality Waiting for RLC-ACK on UMI Invalid Simultaneous Reconfiguration Criteria General correction and alignment of the ASN.1 and tabular Introduction of UMTS1700/2100 (Band IV) Introduction of UMTS850 (Band V) Introduction of VLEC in every message branch Simultaneous Reception of S-CCPCH and HS-DSCH 5.7.0 5.7.0 6.0.0 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1
RP-22 RP-22 RP-22 03/2004 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23
RP-030630 2133 RP-030721 2134 1 RP-030630 2160 Editorial RP-040095 2168 2 RP-040095 2172 RP-040107 2176 1 RP-040095 2180 1 RP-040095 2184 1 RP-040095 2188 1 RP-040101 2191 1 RP-040101 2197 2 RP-040101 2200 RP-040101 2203 RP-040107 2207 RP-040107 2209 RP-040107 2213 RP-040131 2217 3 RP-040096 2221 RP-040096 2225 1 RP-040092 2229 RP-040096 2235 RP-040096 2239 RP-040097 2243 RP-040097 2247 1 RP-040105 2249 RP-040101 2252 1 RP-040121 2253 1 RP-040091 2254 RP-040101 2257 RP-040107 2259
6.0.0 6.0.0 6.0.0 6.0.1 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0
3GPP
Release 6
1246 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-23 RP-23
TSG Doc. CR Rev Subject/Comment RP-040107 2261 Cell reselection between UTRAN and GERAN Iu mode RP-040108 2263 HSDPA related corrections on buffer flushing on state transitions, RAT transitions, error cases, MAC-hs reconfiguration and readiness to receive HS-PDSCH Signalling of MAC-hs Reset Modification of Inter-frequency CELL_INFO_LIST [VAS] 1B-1C conflicts when 1A is not configured Handling of wait time in RRC connection reject Misalignments between R'99 and Rel-5 procedures Issues related to Inter-RAT and Inter-frequency handovers Corrections to reconfiguration scenarios and ciphering of TM RBs Addition of "cell selection indication" for cell selection at release of RRC connection and RRC connection reject with re-direction HSDPA capability for multimode FDD-TDD terminals Response on SRNS Relocation with Cell Update Empty non-critical extensions Missing v3g0 extension in the UE CAPABILITY INFORMATION Correction on System Information in TDD Corrections to Cell Change Order from UTRAN procedure
Old 6.0.1 6.0.1
New 6.1.0 6.1.0
RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 RP-23 06/2004 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24
RP-040106 2265 2 RP-040131 2267 2 RP-040131 2269 1 RP-040131 2271 1 RP-040108 2274 RP-040097 2281 RP-040097 2285 1 RP-040110 2286 4 RP-040129 2288 RP-040095 2168 2 RP-040203 2292 RP-040211 2294 1 RP-040203 2303 RP-040236 2305 RP-040206 2308 RP-040207 2311 RP-040210 2313 RP-040207 2316 RP-040210 2318 RP-040211 2320 1 RP-040207 2323 RP-040210 2325 RP-040210 2327 RP-040210 2329 RP-040207 2332 RP-040210 2334 RP-040236 2336 RP-040236 2338
6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.0.1 6.1.0 6.1.0 6.1.0 6.1.0
6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.3.0
Correction on SFN-SFN time difference misalignment in 1.28 Mcps 6.1.0 TDD ASN.1 correction leftovers 6.1.0 Closing the REL-5 extensions in the ASN.1 6.1.0 Incorrect presence of UE-RadioAccessCapability extension in RRC 6.1.0 CONNECTION SETUP COMPLETE Unnecessary MAC-d flow identity in the IE DL-TrCH-Type-r5 6.1.0 UE capability enquiry for GERAN Iu mode Clean up of SRNS Relocation Info REL-4 version Tabular correction for RADIO BEARER RELEASE message Misalignments betwen R99 and Rel-5 procedures Erroneous setting of Re-establsish Indicator in case of SRNS relocation Correction to IE Cell Info Correction Concerning UE Positioning Measurement Pending compressed mode reconfigurations Active compressed mode patterns with same measurement purpose Correction to Information Elements for UE Rx-Tx time difference Naming correction in the HS-DSCH IE Measurement Feedback Information Clarification about open loop power control in 1.28Mcps TDD Clarification about measurement control system information in TDD mode Correction to timing-maintained hard handover regarding the UL transmission timing Selection of suitable cell Check of the PLMN identity in the MIB when selecting a new cell Compressed INTER RAT HANDOVER INFO message modifications/corrections The ASN.1 definition of IE SysInfoType5bis RLC size handling and RLC re-establishment Restrict operation of the virtual active set Usage of different RB mapping info Clarification on UE procedure in case of HHO failure TDD misalignment between tabular and ASN.1 definitions of UL Transport channel information common for all transport channels and special burst scheduling Definition of parameters for UE-assisted A-GPS Addition of UMTS850 (Band V) in the tabular Default Configurations for multiple AMR Rate Configurations Correction on PRACH selection in 1.28Mcps TDD 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.1.0 6.2.0
RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 RP-24 09/2004 RP-25
RP-040211 2340 RP-040210 2342 RP-040206 2345 RP-040206 2348 RP-040211 2350 RP-040236 2354 2 RP-040236 2356 RP-040211 2358 RP-040215 2359 RP-040224 2361 RP-040212 2363 RP-040213 2365 RP-040256 2367 1 RP-040327 2373
RP-25 RP-25 RP-25 RP-25
RP-040327 2377 RP-040339 2378 2 RP-040360 2381 RP-040319 2384
6.2.0 6.2.0 6.2.0 6.2.0
6.3.0 6.3.0 6.3.0 6.3.0
3GPP
Release 6
1247 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25 RP-25
TSG Doc. CR Rev Subject/Comment RP-040334 2386 Inconsistency in UE action for HFN initialisation RP-040334 2388 RP-040334 2390 RP-040334 2392 RP-040348 2394 1 RP-040334 2396 RP-040334 2398 RP-040334 2400 RP-040335 2402 RP-040335 2404 RP-040335 2406 RP-040335 2408 RP-040335 2410 RP-040335 2412 RP-040335 2414 RP-040335 2416 RP-040328 2418 RP-040336 2420 RP-040336 2422 1 RP-040328 2428 RP-040336 2430 RP-040336 2432 RP-040481 2434 RP-040481 2436 RP-040481 2438 RP-040476 2442 RP-040481 2444 RP-040474 2448 RP-040477 2451 RP-040481 2453 RP-040481 2455 1 RP-040526 2457 2 RP-040482 2459 1 RP-040482 2461 RP-040482 2463 1 RP-040482 2465 RP-040477 2468 1 RP-040482 2470 2 RP-040520 2472 2 RP-040505 2474 RP-040505 2476 RP-040505 2478 RP-040522 2480 2 RP-040505 2482 RP-040505 2484 RP-040495 2487 1 RP-040505 2493 RP-040491 2494 RP-040491 2495 1 RP-040543 2496 2 Usage of different RB mapping info for TDD TDD HS-DSCH Corrections Alignment of Tabular Definition with ASN.1 for HS-SCCH Info Correction to HS-DSCH reception conditions Correction to RB mapping check Position Timestamp for A-GPS Pending compressed mode reconfigurations Predefined configurations for the RRC connection request UE actions for Delta_ACK/NACK and repetition factor Calculation of UL transmit power for HS-SICH (TDD) Handling of Timer T302 Expiry Correct naming for HS-DSCH with DCH multiplexing option
Old 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0
New 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0
Cell update during reconfiguration from CELL_FACH to CELL_PCH 6.2.0
Compressed Pre-defined configurations description in new Annex 6.2.0 C Integration between integrity protection and the sending of downlink 6.2.0 messages during SRNS relocation Corrections to restrictions of operation of the virtual active set 6.2.0 UE actions for received new keys Scrambling Code Change Clarifications to VAS functionality UE security capability in INTER_RAT handover Correction to the Radio Link Failure behaviour Correction to measured results on RACH T305 handling upon a state transition 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.3.0 6.3.0
12/2004
RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26 RP-26
Handling of pending AM RLC unrecoverable errors signalled by cell 6.3.0 update Correction to maximum length of CTCH period 6.3.0 TPC step size in default configurations References to ITU-T Recommendations on ASN.1 ASN.1 clarification on Measurement Report for 1.28 Mcps TDD Correction to HS-DSCH reception conditions MAC-hs Reset procedure Cell selection and reselection parameters Clarification the PDCP capability- Max HC context space Corrections to IE WAIT TIME = 0 RRC transaction identifier in the MEASUREMENT CONTROL message Correction to intra-frequency measurement handling in SIB11 Missing OTDOA TDD related v4b0 extension in MEASUREMENT CONTROL Clarification of Radio Bearer Downlink Ciphering Activation Time Info TFC Subset Variable Usage and Application of Transport Format Combination Subset Use of preconfiguration in the RADIO BEARER RECONFIGURATION message UTRAN setting of ciphering activation time for SRB2 Correction to ASN1 IE srb-SpecificIntegrityProtInfo Criteria for initiating cell update on receiving Frequency info IE in CELL UPDATE CONFIRM message Traffic volume measurements in PCH states Failure cause indication on Cell Update Network Sharing and multiple PLMN identities Inter-RAT measurement control information used ASN.1 update for the introduction of MBMS Introduction of MBMS Preamble and Postamble to reduce HS-DPCCH transmit power 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0
3GPP
Release 6
1248 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date 03/2005
TSG # RP-26 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27 RP-27
TSG Doc. CR Rev Subject/Comment RP-040507 2497 Introduction of E-DCH RP-050038 2491 2 RP-050069 2499 RP-050169 2501 RP-050069 2503 RP-050089 2504 RP-050114 2506 RP-050069 2508 RP-050070 2510 RP-050070 2513 RP-050070 2515 1 RP-050067 2517 3 RP-050069 2519 RP-050070 2521 RP-050070 2523 RP-050086 2524 RP-050086 2525 RP-050110 2526 1 RP-050081 2527 RP-050074 2528 RP-050084 2529 RP-050079 2530 2 RP-050087 2532 RP-050084 2534 RP-050097 2535 RP-050079 2536 1 RP-050128 2538 1 RP-050253 2539 3 RP-050339 2540 3 RP-050320 2541 1 RP-050329 2542 RP-050302 2545 RP-050302 2547 RP-050316 2548 2 RP-050316 2549 1 RP-050316 2550 1 RP-050316 2551 RP-050303 2553 2 RP-050320 2554 2 RP-050324 2555 RP-050322 2556 RP-050320 2557 1 RP-050320 2558 RP-050320 2559 RP-050316 2560 1 RP-050316 2561 1 RP-050320 2562 RP-050320 2564 RP-050320 2566 1 Removal of TGPL2 Minor HSDPA related corrections Integrity protection related information in the SRNS relocation info Number of timeslots that can be used for HS-PDSCH resource for 3.84 Mcps TDD HS-DSCH operation without a DL DPCH for 3.84 Mcps TDD
Old 6.3.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0
New 6.4.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0
Removal of unnecessary cell updates on receiving Frequency info 6.4.0 IE in CELL UPDATE CONFIRM message ASN.1 clarification on Cell and Channel Identity info for 1.28 Mcps 6.4.0 TDD Handling of TM SRBs at radio link failure 6.4.0 Removal of the UARFCN uplink (Nu) in the informative Annex A.3 Correction on PRACH selection Lossless DL RLC PDU size change Clarification of GERAN (P)SI message coding in NACC Unsupported RLC mode reconfigurations Correction to Inter RAT cell info indication Correction to network sharing functionality Network sharing corrections CN domain specific Access Class Barring Corrections to "selected PLMN" in access stratum Introduction of F-DPCH Minor E-DCH related corrections Miscellaneous MBMS corrections Additional Frequency Bands Introduction of E-DCH in the ASN.1 Improvements to uplink closed loop power control for 1.28 Mcps TDD MBMS Corrections to 25.331 ASN.1 Correction to cell selection and reselection parameters to enable enhanced cell reselection Faster L1 DCH synchronization Timing maintained hard handover Removal of unnecessary Start values Merged CR alignement w.r.t. network sharing functionality Timing Reinitialized Handover & Radio Link Timing Adjustmen Addition of omitted IE report criteria in MEASUREMENT CONTROL message modify command Miscellaneous MBMS corrections (set II) Correction to MBMS notification procedure FACH Measurement Occasion when UE receives MBMS Frequency layer dispersion Signalling of target mode for ROHC operation Introduction of inter-frequency RACH measurement reporting Closed-Loop Power Control Improvements for 1.28 Mcps TDD ASN1 Corrections Release 6 HS-DSCH operation without a DL DPCH for 3.84 Mcps TDD Setting of Dhs-sync Correction to the Amount of Reporting Measurement report message definition when Inter-RAT cell info indication is used Direct transition to DCH Addition of the number of MBMS Neighbour Cell PTM Information messages to the MBMS Modified Services Information message Addition of MBMS counting for UEs in Cell_PCH and Cell_FACH states and addition of UE requested p-t-p bearer establishmen Introduction of IE RB information to reconfigure in RB SETUP, RB RELEASE messages Including HS-DSCH serving cell change in ASU Detection of Activation CFN wraparound in the UE during HS6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0
06/2005
RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28
3GPP
Release 6
1249 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28 RP-28
TSG Doc.
CR
Rev Subject/Comment DSCH cell change Correction to handling of keys at inter-RAT handove CTFC calculation for DCH Default RB identity in IE 'Signalling RB information to setup Default configuration 13 UE L3 requirements for HS-DSCH mobility Support for out-of-sequence PDUs in RLC-UM Feature Clean Up: Removal of 80 ms TTI for DCH for all other cases but when the UE supports SF512 Feature Clean Up: Removal of observed time difference to GSM cell Feature Clean Up: Removal of SSDT Feature Clean-up: Removal of DSCH (FDD) Feature Clean Up: Removal of CPCH Feature Clean Up: Removal of dedicated pilot as sole phase reference Feature Clean Up: Removal of DRAC Feature Clean Up: Removal of TX diversity closed loop mode 2 Feature Clean Up: Removal of Compressed mode by puncturing Alignment of EUDCH RRC Stage-3 to Stage-2 status, including handling of 2 E-RNTIs Radio link failure in F-DPCH Setting up F-DPCH and E-DCH in RRC connection setup Validity of PtM configurations CCCH message enhancements Quality measurement corrections Clean-up of R6 ASN.1 leftovers UE behaviour for DCH SIR target setting for Downlink power control RLC LI Optimization for VoiP
Old 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0
New 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0
RP-050304 2568 RP-050302 2572 RP-050302 2574 RP-050302 2576 RP-050320 2577 RP-050374 2579 3 RP-050305 2581 RP-050306 2583 RP-050307 2585 RP-050308 2586 RP-050309 2589 RP-050310 2591 RP-050311 2593 RP-050312 2595 RP-050313 2597 RP-050327 2598 2 RP-050336 2599 RP-050323 2600 1 RP-050316 2601 1 RP-050392 2602 1 RP-050320 2604 RP-050328 2605 RP-050346 2607 2 RP-050317 2608 RP-050316 2609 2 RP-050320 2610 RP-050329 2611 RP-050316 2613 RP-050316 2614 RP-050316 2615 RP-050486 2616 RP-050465 2619 RP-050465 2621 1 RP-050465 2623 RP-050465 2626 RP-050587 2628 3 RP-050465 2630 RP-050465 2632 RP-050482 2633 RP-050458 2635 RP-050458 2637 RP-050458 2639 RP-050458 2641 1 RP-050482 2642 RP-050482 2643 RP-050482 2644 RP-050482 2645 RP-050482 2646 RP-050482 2648 RP-050482 2649
Introduction of an S-CCPCH power offset difference in order to 6.5.0 improve cell selection for soft and selective combining Erroneous implementation of CR#2501 in RRC specification v6.5.0. 6.5.0 Correction to network sharing MBMS asn1 issues SCCPCH timing offset information for FDD MBMS soft combining MBMS corrections on signalling optimization Support of Domain Specific Access control in Rel-5 Ues ASN1 update for InterRATReportingQuantity IE RB information to reconfigure for RADIO BEARER RECONFIGURATION message Size of TFC Subset List for Transport Format Combination Control RB mapping rules Rules for triggering hard handover RSCP value range extension H-RNTI validity Removal RLC-SDU alignment capability Feature Clean Up: Removal of DRAC DRAC & Dedicated pilots removal leftovers (asn1) DRAC & CPCH removal leftovers (sib8,9,10) Feature remove (Tabular/asn1 alignment) Correction to UE L3 requirements for HS-DSCH mobility Rate Control Correction 6.5.0 6.5.0 6.5.0 6.5.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0
09/2005
RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29
Introduction of container to facilitate transparent transfer of UE 6.6.0 capabilities Minor ASN.1 correction for TDD IEs Beacon PL Est and DHS-Sync 6.6.0 Addition of ongoing reconfiguration indicator in cell update Faster L1 DCH synchronization Direct transition to DCH 6.6.0 6.6.0 6.6.0
3GPP
Release 6
1250 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG Doc. CR Rev Subject/Comment RP-050482 2650 PSI messages in CELL CHANGE ORDER FROM UTRAN RP-050482 2651 RP-050482 2652 RP-050482 2653 RP-050482 2654 RP-050483 2655 RP-050483 2656 RP-050483 2657 SRNS relocation info Correction to UE-assisted OTDOA support
Old 6.6.0 6.6.0 6.6.0
New 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0
Correction to undefined UE behaviour in case of Cell-ID positioning 6.6.0 with method type UE-based Receiving "Frequency info" IE in CELL UPDATE CONFIRM 6.6.0 message Re-entry in service in CELL_PCH before T316 expiry 6.6.0 ASN.1 alignment to Rel-5 of InterRATCellInfoIndication Addition of Inter-frequency measurements reporting on RACH reporting in the ASN.1 of RRC CONNECTION REQUEST and CELL UPDATE messages Correction to the Amount of Reporting Minor correction of HS-DSCH/ E-DCH capability indication Modification of TPC command error rate granularity and range Introduction of PS handover between UTRAN and GERAN Including HS-DPCCH power offset and HARQ preamble mode in active set update Minor MBMS corrections (set IV) Clarification on MBMS modified services information IE MBMS correction for recounting MBMS asn1 issues E-DCH corrections and additions E-DCH corrections E-DCH additions to active set update UE capabilities for E-DCH in 25.331 Conditional suspension of CELL_FACH measurements to enable reception of MCCH MBMS message order on MCCH MSCH configuration information in case of soft combining Timing Offset Removal of fixed position for S-CCPCHs carrying MBMS channels Introduction of Band VII Introducing preconfiguration upon radio bearer establishment Introduction of the device type indication in UE capability E-DCH TTI Reconfiguration Maximum number of reference ETFCIs F-DPCH power control Introduction of UMTS1700 Introduction of the HSDPA and E-DCH Capable Cell Indicator PRACH for CCCH in SIB 6 Tx/Rx frequency separation capability (FDD) E-DCH mobility corrections and multi-step handling for E-RGCH L1 synchronisation at HHO Correction to UE positioning measurements in CELL_PCH/URA_PCH state Clarification of Delta in Inter/Intra-frequency measurement reporting criteria Clarification of the usage of "Ack-Nack Power Offset" in HSDPA for TDD Modification of WB-AMR default configuration Serving E-DCH radio link indication Introduction of UMTS 900 (Band VIII) MCCH configuration information Correction of default TFCS for MBMS Unidirectional RLC reconfiguration Misalignments for E-DCH Update for E-DCH Serving Grant IE value range Clarification on MAC-d flow multiplexing list Addition of E-DCH power offsets to active set update 6.6.0 6.6.0
RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 RP-29 12/2005 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30 RP-30
RP-050483 2658 RP-050483 2659 RP-050476 2660 RP-050473 2661 1 RP-050483 2662 RP-050468 2663 RP-050468 2664 RP-050468 2665 RP-050468 2666 1 RP-050471 2667 RP-050471 2668 RP-050472 2669 4 RP-050471 2670 1 RP-050468 2671 RP-050468 2672 RP-050468 2673 RP-050469 2674 1 RP-050467 2675 RP-050483 2676 RP-050484 2677 1 RP-050471 2680 RP-050483 2681 RP-050561 2682 RP-050801 2617 2 RP-050787 2683 4 RP-050785 2685 1 RP-050796 2686 1 RP-050827 2687 1 RP-050797 2688 1 RP-050786 2690 RP-050785 2692 RP-050785 2694 RP-050785 2696 RP-050785 2698 RP-050800 2699 RP-050788 2700 RP-050788 2701 RP-050797 2702 RP-050793 2703 1 RP-050793 2704 RP-050793 2705 RP-050793 2706
6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.6.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0
6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0
3GPP
Release 6
1251 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG Doc. CR Rev Subject/Comment RP-050793 2707 E-RNTI validity RP-050793 2708 RP-050793 2709 1 RP-050793 2710 RP-050793 2711 1 RP-050788 2714 1 RP-050831 2717 1 RP-050861 2718 1 RP-060087 2716 5 RP-060083 2720 RP-060081 2722 1 RP-060091 2723 RP-060087 2724 RP-060087 2725 RP-060087 2726 2 RP-060087 2727 RP-060087 2728 RP-060087 2729 RP-060087 2730 RP-060087 2731 RP-060087 2732 RP-060087 2733 RP-060120 2734 1 RP-060091 2735 RP-060091 2736 RP-060091 2737 RP-060093 2738 RP-060092 2739 1 RP-060091 2740 RP-060091 2741 RP-060091 2742 RP-060091 2743 RP-060083 2746 1 RP-060091 2747 RP-060092 2748 1 RP-060095 2749 1 RP-060091 2751 RP-060091 2752 RP-060088 2753 RP-060091 2754 RP-060091 2755 RP-060091 2756 RP-060091 2757 RP-060086 2760 1 RP-060088 2761 RP-060093 2764 RP-060095 2765 RP-060362 2766 RP-060374 2768 1 Clarification of bit strings for EUL Modification of SI periodicity E-DCH PO signalling MAC es/e reset indicator MBMS corrections on default TFCS, service identity and PL Service Information Corrections of inconsistencies in Rel-6 RRC messages (ASN.1 review) Introduction of Support of Handover to GAN E-DCH Measurement Event 1J Default configuration 11 for multirate AMR with SRB5 Addition of synchronization parameters in RRC for HS-SICH in 1.28Mcps TDD Integrity Protection check for NAS messages E-DCH radio link addition using ASU of RL already in DCH active set Addition of SF128 and SF256 in E-DCH maximum channelisation codes RRC signaling efficiency changes for E-DCH E-DCH HARQ Info signalling Secondary Scrambling Code in F-DPCH RL information Correction to E-DCH IEs Non-scheduled grant IE handling for E-DCH E-RNTI handling in Active Set Update procedure Editorial correction on E-DCH information Corrections of inconsistencies in Rel-6 RRC messages (ASN.1 review) Correction to Modifying Integrity Protection Configuration for TM SRB Correction to Security Mode Control Procedure Resolving problems from CR implementation Removal of GPRS encryption algorithm info Default configurations for Multi-mode AMR Periodic URA Update in OOS Correction in IE UE positioning capability
Old 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.7.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0
New 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.10.0 6.10.0
03/2006
RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31 RP-31
F-DPCH, HSDPA and E-DCH in HANDOVER TO UTRAN 6.8.0 COMMAND (Rel-6 ASN.1 review issue 013) Representation of IE "latestConfiguredCN-Domain" in the r3 branch 6.8.0 of SRNS Relocation Info 7.95kbps NB AMR Default Configuration removal 6.8.0 Periodic BMC Schedule Message Introduction of additional Default configuration identities PS default configurations Configuration of DL TFCS as 'Same as UL' NAS synchronization indicator in RB setup General error handling in case of ASN.1 violation and for MBMS channels Clarification of UE action upon receiving the IE RB information to change list Removal of unnecessary checking for HS-DSCH and E-DCH configuration Introduction of WB-AMR default configuration without SRB#5 Initial DPCH frame offset for F-DPCH Support for different E-DCH and HS-DSCH serving cells Correction to S-CCPCH power offset for MBMS Inter-RAT PS Handover capability Indication of HSPA capability and conversation call type for CS Measurement control ASN.1 error RoHC Segmentation, padding and Packet_sizes_allowed 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.9.0 6.9.0
06/2006
RP-32 RP-32
3GPP
Release 6
1252 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG Doc.
CR
Rev Subject/Comment parameter removal
Old
New 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0
RP-060360 2771 1 RP-060361 2773 1 RP-060368 2777 RP-060368 2779 RP-060368 2781 RP-060368 2783 RP-060354 2785 RP-060361 2787 RP-060361 2789
Correction of procedures dealing with "Serving HS-DSCH radio link 6.9.0 indicator" and "Serving E-DCH radio link indicator" MAC-HS handling for 'return in case of failure' 6.9.0 Clarification on IE MBMS re-acquire MCCH Clarification on MCCH Acquisition Initiation Clarification of encoding of TB size for FDD common transport channels HCS parameters for MBMS cell reselection Clarification on MAC-e/es reset 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0
RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 RP-32 09/2006 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33 RP-33
RP-060364 2791 RP-060364 2793 RP-060358 2795 RP-060364 2797 RP-060364 2799 RP-060364 2801 RP-060364 2803 RP-060365 2805 RP-060365 2807 RP-060365 2809 RP-060365 2811 RP-060365 2813 RP-060366 2815 RP-060366 2817 RP-060366 2819 RP-060366 2821 RP-060366 2823 RP-060366 2825 RP-060368 2832 RP-060354 2834 RP-060366 2836 RP-060366 2838 RP-060573 2847 RP-060574 2851 RP-060575 2853 RP-060574 2855 RP-060597 2857 2 RP-060576 2860 RP-060576 2864 RP-060576 2866 1 RP-060576 2868 RP-060575 2870 RP-060575 2872 RP-060575 2876 RP-060575 2878 RP-060593 2880 RP-060593 2882 RP-060593 2884 -
Modification to the BLER targetconfiguration method in RRC spec 6.9.0 for 3.84Mcps TDD Add some IEs for HS-SICH power control parameter updating in 6.9.0 UPLINK PHYSICAL CHANNEL CONTROL message in 1.28Mcps TDD mode Correction on Inter-RAT cell info indication 6.9.0 Clarifications regarding virtual active set PS Handover Capability Handling of System Information Block type 5bis. Introducing container for Measurement Report informaton within SRNS relocation Removal of GSM OTD reference cell Error handling for 'dummy' IEs introduced in ASN.1 by recent feature removal START value in Cell Update Default configurations 10 and 13 Inter-frequency measurement reporting on RACH Radio bearer mapping for SRBs Correction to RLC default configuration New standalone SRB default configurations Introduction of default configurations with flexible TFCS Small IE corrections: 'RB information to change list', 'Access Class Barred' Correction to IE Default Configuration Identity Correction to TFC subset for default configurations 11&12 HSDPA/E-DCH info in INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES Clarification on MBMS Radio Bearer Release Correction on E-DCH DL Scrambling Code Reinstatement of missing IE "Periodic and Reporting information 1b" in ASN.1 SRB2 suspension Removal of CID indication in PDCP PID Correction to the tabulars for Serving Grant value Range of the encoding of E-DCH physical layer category and HSDSCH physical layer category 3-index step 2-index step clarifications Introduction of SIB 11bis Corrections to MBMS Downlink Timeslots and Codes for TDD Clarification on MBMS notification for UEs in CELL_DCH state Clarification on MBMS p-t-m activation time IE Access probability factor Modification to the HS-SCCH set configuration method in RRC spec for 1.28Mcps TDD Correction to tabular for IE Delay restriction Flag. Corretion on 3G-2G Handover Pending security configuration for SRB2 UE radio access capability for Single-band UE Inter-RAT handover to UTRAN (HSPA) Tabular & reference corrections 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0
6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0 6.10.0
6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0
3GPP
Release 6
1253 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG Doc. CR Rev Subject/Comment RP-060593 2886 F-DPCH Tx Diversity RP-060593 2888 1 RP-060573 2896 1 RP-060573 2899 1 RP-060624 2905 3 RP-060593 2906 RP-060574 2912 RP-060593 2914 RP-060578 2918 RP-060717 2921 1 RP-060716 2924 RP-060804 2926 2 RP-060718 2930 RP-060718 2932 RP-060718 2934 RP-060719 2937 RP-060716 2939 RP-060719 2942 RP-060716 2944 RP-060719 2946 1 RP-060718 2950 RP-060718 2952 RP-060718 2955 1 RP-070151 2965 RP-070151 2967 RP-070151 2969 RP-070151 2971 1 RP-070153 2974 RP-070154 2978 RP-070153 2980 RP-070151 2988 1 RP-070401 3005 RP-070401 3006 RP-070416 3007 RP-070401 3009 RP-070401 3011 Expiration of RRC timer T314/T315 associated to CS/PS RABs Use of CM_PATTERN_ACTIVATION_ABORTED flag Corrections of procedures dealing with Hard Handover Enhancing MBMS support for Mobile TV
Old New 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0 6.10.0 6.11.0
ASN1 correction on Inter-frequency RACH measurement reporting, 6.10.0 6.11.0 backward compatible solution E-DCH gain factor computation 6.10.0 6.11.0 Correction to default configuration #22 MAC-hs reset Correction on acceptable configurations for compression entities Grant and MAC-e/es headers for E-DCH and References Correction to E-DCH reconfiguration Removal of MSCH configuration information from S-CCPCH system information Correction relating to the formation of a list of services Indentation error in handling MBMS establishment cause values Tabular/ASN.1 mismatch for IE "UE radio access capability comp 2" Correction to Radio Bearer Mapping for UE in CELL_DCH state Usage of Band Indicator in Inter-RAT cell info list Correction for support of HS-DSCH in RRC Connection Setup ASN.1 correction to ACTIVE SET UPDATE for F-DPCH Tx Diversity RAB ID for mobile TV MBMS PL Service Restriction Information and preferred frequency layer MBMS short transmission ID and Mobile TV Correction of MBMS MODIFICATION REQUEST 6.10.0 6.11.0 6.10.0 6.11.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.11.0 6.12.0 6.12.0 6.13.0
12/2006
RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34 RP-34
03/2007
RP-35 RP-35 RP-35 RP-35 RP-35 RP-35 RP-35 RP-35
Wording of MBMS PL Service Restriction Information and preferred 6.12.0 6.13.0 frequency layer maxMBMS-Services definition 6.12.0 6.13.0 MBMS selected services indication Tabular Alignment for Uplink DPCH Info Absence of MS Classmark 2 and 3 in IE "Inter-RAT UE radio access capability" Handling of TFCS with no DCH configured MICH reception for services scheduled with MSCH MBMS Scheduling Information Minor correction on text Maintenance of PMM connection for MBMS PTP reception Content of MSI message when sent on DCCH Relative ordering of MBMS Selected Services when indicated to the network Default MBMS activation time and 'MBMS all unmodified p-t-m services' Problem with the IE 'MBMS service identity' included in the IE 'RAB info' Correction of SRB delay Incorrect reference to 25.993 for default configuration 17 Correction to CTFC for default configuration 12 MBMS Notification Indication for F-DPCH support status Correction to E-DCH STTD operation START values in cell update before security is enabled MBMS Counting completion in RRC MBMS ptp service change Clarification on logical channel multiplexing Integrity Protection and MBMS: Correction to Procedural Text (alignment with ASN.1) 6.12.0 6.13.0 6.12.0 6.13.0 6.12.0 6.13.0 6.12.0 6.13.0 6.12.0 6.13.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.13.0 6.14.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0
06/2007
RP-36 RP-36 RP-36 RP-36 RP-36 RP-36
RP-070401 3014 RP-36 RP-070401 3016 RP-36 RP-36 RP-36 RP-36 RP-36 09/2007 RP-37 RP-37 RP-37 RP-37 RP-37 RP-37 RP-070625 3071 RP-070406 3018 RP-070406 3020 RP-070406 3023 RP-070401 3033 1 RP-070504 3042 2 RP-070623 3046 1 RP-070624 3049 RP-070625 3063 1 RP-070625 3065 1 RP-070623 3067 1
3GPP
Release 6
1254 Change history
3GPP TS 25.331 V6.23.0 (2009-09)
Date
TSG # RP-37 RP-37 RP-37 RP-37 RP-37 RP-37 RP-37
TSG Doc.
CR
Rev Subject/Comment MBMS services naming F-DPCH TPC error rate target Correction to CTFC for default configuration 14 Correction to default configuration 16 Security correction on PS handover to UTRAN Corrections in the default radio configurations 11/12/13 Miscellaneous corrections in the default radio configurations UE setting for the Extension indicator in the frequency band IEs Corrections on IE 'Report criteria' Correction on MMSI reception on DCCH RADIO BEARER SETUP using default configurations
RP-070625 3073 RP-070624 3095 RP-070624 3097 RP-070624 3099 RP-070624 3101 RP-070624 3119 RP-070624 3121 RP-071011 3124 2 RP-070894 3130 RP-070895 3149 RP-070894 3152 2 RP-070895 3155 RP-070892 3160 RP-070894 3182 RP-070895 3199 RP-070895 3204 1 RP-080178 3229 RP-080177 3248 RP-080179 3251 RP-080178 3268 RP-080390 3280 1 RP-080390 3283 RP-080393 3296 RP-080442 3338 RP-080678 3374 RP-080999 3417 RP-081000 3464 RP-080998 3497 RP-090115 3533 1 RP-090115 3536 RP-090115 3581 RP-090498 3627 1 RP-090499 3669 RP-090900 3791 RP-090900 3799 RP-090900 3805 -
Old New 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.14.0 6.15.0 6.15.0 6.16.0 6.15.0 6.16.0 6.15.0 6.16.0 6.15.0 6.16.0
12/2007
RP-38 RP-38 RP-38 RP-38 RP-38 RP-38 RP-38 RP-38 RP-38
Correction of integrity protection and checking of MBMS MODIFIED 6.15.0 6.16.0 SERVICES INFORMATION message on DCCH Use of default configuration 12 6.15.0 6.16.0 Wrong UL Puncturing Limits for default configurations #15, #18, #19, #20 and #21 Procedure text concerning MBMS offsets and tabular/ASN.1 description are not aligned Correction on MBMS Frequency Layer Dispersion (FLD) Clarification on MAX_CID L2-combining in MBMS CURRENT CELL P-T-M RB INFORMATION message Correction to SIB extension multiplexing Correction to default configuration 17 Interpretation of the "Neighbouring cell identity" in MBMS NEIGHBOURING CELL PTM RB INFO Clarification on MBMS dispersion Correction to the calcuration of DPCH frame offset for F-DPCH on timing re-initialised hard handover Correction to note on reference E-TFCI configuration Fix Word problem Clarification of the UE behavior on DSAC Typo in IE 'Domain Specific Access Restriction' MBMS frequency selection Correction of measurement event 1I UMTS frequency information in IE Rplmn information CN system information after PS HO Corrections for PS handover to UTRAN Removal of description of CPCH feature Clarification to the support of 2 different layer 3 filters per measurement type Clarification on Inter-frequency RACH reporting quantity for TDD RLC Size - SizeInfoType2 correction E-AGCH channel and E_RNTI variable corrections 6.15.0 6.16.0 6.15.0 6.16.0 6.15.0 6.16.0 6.16.0 6.17.0 6.16.0 6.17.0 6.16.0 6.17.0 6.16.0 6.17.0 6.17.0 6.18.0 6.17.0 6.18.0 6.17.0 6.18.0 6.17.0 6.18.0 6.18.0 6.18.1 6.18.1 6.19.0 6.19.0 6.20.0 6.19.0 6.20.0 6.19.0 6.20.0 6.20.0 6.21.0 6.20.0 6.21.0 6.20.0 6.21.0 6.21.0 6.22.0 6.21.0 6.22.0 6.22.0 6.23.0 6.22.0 6.23.0 6.22.0 6.23.0
03/2008
RP-39 RP-39 RP-39 RP-39
05/2008
RP-40 RP-40 RP-40 RP-40
08/2008 09/2008 12/2008
RP-41 RP-42 RP-42 RP-42
03/2009
RP-43 RP-43 RP-43
06/2009
RP-44 RP-44
09/2009
RP-45 RP-45 RP-45
3GPP

RRC 6n0

Uploaded by

Copyright:

Available Formats

RRC 6n0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RRC 6n0

Uploaded by

Copyright:

Available Formats

3GPP TS 25.331 V6.23.

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP Postal address

3GPP support office address

3GPP TS 25.331 V6.23.0 (2009-09)

RRC Functions and Services provided to upper layers .......................................................................... 39

Services expected from lower layers ...................................................................................................... 40

Protocol states ........................................................................................................................................ 41

RRC procedures ..................................................................................................................................... 44

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

Handling of unknown, unforeseen and erroneous protocol data .......................................................... 387

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

Message transfer syntax ..................................................................................................................... 1010

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

Specific functions ............................................................................................................................... 1126

14.1 14.1.1 14.1.2 14.1.2.1 14.1.2.2 14.1.2.3 14.1.2.4 14.1.2.5 14.1.2.6

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

14.6.2 14.6.2.1 14.6.2.2 14.6.2.3 14.6.2.4 14.6.2.5 14.6.2.6

USIM parameters ...................................................................................... 1211

Description of RRC state transitions ....................................................... 1213

3GPP TS 25.331 V6.23.0 (2009-09)

Annex D (Normative): Annex E (informative):

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

[51] [52] [53] [54] [55] [56] [57] [58]

Definitions and abbreviations

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

3GPP TS 25.331 V6.23.0 (2009-09)

Overview of the specification

This specification is organised as follows:

3GPP TS 25.331 V6.23.0 (2009-09)

UE Idle 3GPP TS 25.304 TS 23.122

UE connected 3GPP TS 25.331

GSM connected GSM TS 04.18

GPRS Packet Transfer GSM TS 04.60

GSM idle GSM TS 05.08