3GPP TS 25.423 V11.2.

0 (2012-06)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling (Release 11)

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 Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational 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 Organisational Partners Publications Offices.

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

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

UMTS is a Trade MarkCopyright Notification 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 may be Mark of ETSIexcept as being registered writtenbenefit of its Members and of the 3GPP No part a Trade reproduced currently authorized by for the permission. Organizational Partners The copyright and the foregoing restriction extend to reproduction in all GSM and the GSM logo are registered and owned by the GSM Association

media.

2012, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

Contents
Contents....................................................................................................................................................3 Foreword.................................................................................................................................................24 1 Scope....................................................................................................................................................25 2 References............................................................................................................................................25 3 Definitions, Symbols and Abbreviations..............................................................................................27
3.1 Definitions............................................................................................................................................................27 3.2 Symbols................................................................................................................................................................28 3.3 Abbreviations.......................................................................................................................................................28

4 General.................................................................................................................................................31
4.1 Procedure Specification Principles......................................................................................................................31 4.2 Forwards and Backwards Compatibility..............................................................................................................32 4.3 Source Signalling Address Handling...................................................................................................................32 4.4 Specification Notations........................................................................................................................................32

5 RNSAP Services..................................................................................................................................33
5.1 RNSAP Procedure Modules.................................................................................................................................33 5.2 Parallel Transactions............................................................................................................................................33

6 Services Expected from Signalling Transport......................................................................................34 7 Functions of RNSAP............................................................................................................................34

7.1 RNSAP functions and elementary procedures for Iur-g......................................................................................38

8 RNSAP Procedures..............................................................................................................................39
8.1 Elementary Procedures.........................................................................................................................................39 8.2 Basic Mobility Procedures...................................................................................................................................41 8.2.1 Uplink Signalling Transfer................................................................................................................................41 8.2.1.1 General 41 8.2.1.2 Successful Operation......................................................................................................................................41 8.2.1.3 Abnormal Conditions.....................................................................................................................................43 8.2.1A GERAN Uplink Signalling Transfer..............................................................................................................43 8.2.1A.1 General 43 8.2.1A.2 Successful Operation...................................................................................................................................43 8.2.1A.3 Abnormal Conditions..................................................................................................................................44 8.2.2 Downlink Signalling Transfer...........................................................................................................................44 8.2.2.1 General 44 8.2.2.1.1 Downlink Signalling Transfer for Iur-g......................................................................................................44 8.2.2.2 Successful Operation......................................................................................................................................44 8.2.2.2.1 Successful Operation for Iur-g....................................................................................................................45 8.2.2.3 Abnormal Conditions.....................................................................................................................................45 8.2.2.3.1 Abnormal Conditions for Iur-g...................................................................................................................45 8.2.3 Relocation Commit...........................................................................................................................................45 8.2.3.1 General 45 8.2.3.2 Successful Operation......................................................................................................................................45 8.2.3.2.1 Successful Operation for Iur-g....................................................................................................................46 8.2.3.3 Abnormal Conditions.....................................................................................................................................46 8.2.4 Paging 46 8.2.4.1 General 46 8.2.4.2 Successful Operation......................................................................................................................................46 8.2.4.2.1 Successful Operation for Iur-g....................................................................................................................47 8.2.4.3 Abnormal Conditions.....................................................................................................................................47 8.2.4.3.1 Abnormal Conditions for Iur-g...................................................................................................................47 8.2.5 MBSFN MCCH Information............................................................................................................................47 8.2.5.1 General 47 8.2.5.2 Successful Operation......................................................................................................................................47 8.2.5.3 Abnormal Conditions.....................................................................................................................................48

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

8.2.6 Enhanced Relocation Resource Allocation[1.28Mcps TDD]...........................................................................48 8.2.6.1 General 48 8.2.6.2 Successful Operation......................................................................................................................................48 8.2.6.3 Unsuccessful Operation.................................................................................................................................48 8.2.6.4 Abnormal Conditions.....................................................................................................................................48 8.2.7 Enhanced Relocation Resource Release[1.28Mcps TDD]................................................................................48 8.2.7.1 General 48 8.2.7.2 Successful Operation......................................................................................................................................49 8.2.7.3 Abnormal Conditions.....................................................................................................................................49 8.3 Dedicated Procedures...........................................................................................................................................49 8.3.1 Radio Link Setup...............................................................................................................................................49 8.3.1.1 General 49 8.3.1.2 Successful Operation......................................................................................................................................49 8.3.1.3 Unsuccessful Operation.................................................................................................................................78 8.3.1.4 Abnormal Conditions.....................................................................................................................................80 8.3.2 Radio Link Addition.........................................................................................................................................83 8.3.2.1 General 83 8.3.2.2 Successful Operation......................................................................................................................................83 8.3.2.3 Unsuccessful Operation...............................................................................................................................114 8.3.2.4 Abnormal Conditions...................................................................................................................................115 8.3.3 Radio Link Deletion........................................................................................................................................119 8.3.3.1 General 119 8.3.3.2 Successful Operation....................................................................................................................................119 8.3.3.3 Unsuccessful Operation...............................................................................................................................119 8.3.3.4 Abnormal Conditions...................................................................................................................................119 8.3.4 Synchronised Radio Link Reconfiguration Preparation.................................................................................120 8.3.4.1 General 120 8.3.4.2 Successful Operation....................................................................................................................................120 8.3.4.3 Unsuccessful Operation...............................................................................................................................165 8.3.4.4 Abnormal Conditions...................................................................................................................................166 8.3.5 Synchronised Radio Link Reconfiguration Commit.......................................................................................171 8.3.5.1 General 171 8.3.5.2 Successful Operation....................................................................................................................................171 8.3.5.3 Abnormal Conditions...................................................................................................................................172 8.3.6 Synchronised Radio Link Reconfiguration Cancellation................................................................................172 8.3.6.1 General 172 8.3.6.2 Successful Operation....................................................................................................................................173 8.3.6.3 Abnormal Conditions...................................................................................................................................173 8.3.7 Unsynchronised Radio Link Reconfiguration.................................................................................................173 8.3.7.1 General 173 8.3.7.2 Successful Operation....................................................................................................................................173 8.3.7.3 Unsuccessful Operation...............................................................................................................................211 8.3.7.4 Abnormal Conditions...................................................................................................................................212 8.3.8 Physical Channel Reconfiguration..................................................................................................................217 8.3.8.1 General 217 8.3.8.2 Successful Operation....................................................................................................................................217 8.3.8.3 Unsuccessful Operation...............................................................................................................................218 8.3.8.4 Abnormal Conditions...................................................................................................................................218 8.3.9 Radio Link Failure..........................................................................................................................................218 8.3.9.1 General 218 8.3.9.2 Successful Operation....................................................................................................................................219 8.3.9.3 Abnormal Conditions...................................................................................................................................220 8.3.10 Radio Link Restoration.................................................................................................................................220 8.3.10.1 General 220 8.3.10.2 Successful Operation..................................................................................................................................220 8.3.10.3 Abnormal Conditions.................................................................................................................................220 8.3.11 Dedicated Measurement Initiation................................................................................................................220 8.3.11.1 General 220 8.3.11.2 Successful Operation..................................................................................................................................221 8.3.11.3 Unsuccessful Operation.............................................................................................................................224 8.3.11.4 Abnormal Conditions.................................................................................................................................224

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.12 Dedicated Measurement Reporting...............................................................................................................225 8.3.12.1 General 225 8.3.12.2 Successful Operation..................................................................................................................................225 8.3.12.3 Abnormal Conditions.................................................................................................................................226 8.3.13 Dedicated Measurement Termination...........................................................................................................226 8.3.13.1 General 226 8.3.13.2 Successful Operation..................................................................................................................................226 8.3.13.3 Abnormal Conditions.................................................................................................................................226 8.3.14 Dedicated Measurement Failure...................................................................................................................227 8.3.14.1 General 227 8.3.14.2 Successful Operation..................................................................................................................................227 8.3.14.3 Abnormal Conditions.................................................................................................................................227 8.3.15 Downlink Power Control [FDD]...................................................................................................................227 8.3.15.1 General 227 8.3.15.2 Successful Operation..................................................................................................................................228 8.3.15.3 Abnormal Conditions.................................................................................................................................228 8.3.16 Compressed Mode Command [FDD]...........................................................................................................229 8.3.16.1 General 229 8.3.16.2 Successful Operation..................................................................................................................................229 8.3.16.3 Abnormal Conditions.................................................................................................................................229 8.3.17 Downlink Power Timeslot Control [TDD]...................................................................................................229 8.3.17.1 General 229 8.3.17.2 Successful Operation..................................................................................................................................230 8.3.17.3 Abnormal Conditions.................................................................................................................................230 8.3.18 Radio Link Pre-emption................................................................................................................................230 8.3.18.1 General 230 8.3.18.2 Successful Operation..................................................................................................................................230 8.3.18.3 Abnormal Conditions.................................................................................................................................231 8.3.19 Radio Link Congestion.................................................................................................................................231 8.3.19.1 General 231 8.3.19.2 Successful Operation..................................................................................................................................231 8.3.19.3 Abnormal Conditions.................................................................................................................................232 8.3.20 Radio Link Activation...................................................................................................................................232 8.3.20.1 General 232 8.3.20.2 Successful Operation..................................................................................................................................232 8.3.20.3 Abnormal Conditions ................................................................................................................................233 8.3.21 Radio Link Parameter Update.......................................................................................................................233 8.3.21.1 General 233 8.3.21.2 Successful Operation..................................................................................................................................233 8.3.21.3 Abnormal Conditions.................................................................................................................................235 8.3.22 UE Measurement Initiation [TDD]...............................................................................................................235 8.3.22.1 General 235 8.3.22.2 Successful Operation..................................................................................................................................235 8.3.22.3 Unsuccessful Operation.............................................................................................................................236 8.3.22.4 Abnormal Conditions.................................................................................................................................236 8.3.23 UE Measurement Reporting [TDD]..............................................................................................................237 8.3.23.1 General 237 8.3.23.2 Successful Operation..................................................................................................................................237 8.3.23.3 Abnormal Conditions.................................................................................................................................237 8.3.24 UE Measurement Termination [TDD]..........................................................................................................237 8.3.24.1 General 237 8.3.24.2 Successful Operation..................................................................................................................................238 8.3.24.3 Abnormal Conditions.................................................................................................................................238 8.3.25 UE Measurement Failure [TDD]..................................................................................................................238 8.3.25.1 General 238 8.3.25.2 Successful Operation..................................................................................................................................238 8.3.25.3 Abnormal Conditions.................................................................................................................................238 8.3.26 Iur Invoke Trace............................................................................................................................................239 8.3.26.1 General 239 8.3.26.2 Successful Operation..................................................................................................................................239 8.3.26.3 Abnormal Conditions.................................................................................................................................239

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.27 Iur Deactivate Trace......................................................................................................................................240 8.3.27.1 General 240 8.3.27.2 Successful Operation..................................................................................................................................240 8.3.27.3 Abnormal Conditions.................................................................................................................................240 8.3.28 Enhanced Relocation.....................................................................................................................................240 8.3.28.1 General.......................................................................................................................................................240 8.3.28.2 Successful Operation..................................................................................................................................240 8.3.28.3 Unsuccessful Operation.............................................................................................................................241 8.3.28.4 Abnormal Conditions.................................................................................................................................241 8.3.29 Enhanced Relocation Cancel.........................................................................................................................241 8.3.29.1 General.......................................................................................................................................................241 8.3.29.2 Successful Operation..................................................................................................................................241 8.3.29.3 Unsuccessful Operation.............................................................................................................................242 8.3.29.4 Abnormal Conditions.................................................................................................................................242 8.3.30 Enhanced Relocation Signalling Transfer.....................................................................................................242 8.3.30.1 General 242 8.3.30.2 Successful Operation..................................................................................................................................242 8.3.30.3 Abnormal Conditions.................................................................................................................................242 8.3.31 Enhanced Relocation Release.......................................................................................................................242 8.3.31.1 General 242 8.3.31.2 Successful Operation..................................................................................................................................242 8.3.31.3 Abnormal Conditions.................................................................................................................................243 8.3.32 Secondary UL Frequency Reporting [FDD].................................................................................................243 8.3.32.1 General 243 8.3.32.2 Successful Operation..................................................................................................................................243 8.3.32.3 Abnormal Conditions ................................................................................................................................243 8.3.33 Secondary UL Frequency Update [FDD] ....................................................................................................243 8.3.33.1 General 243 8.3.33.2 Successful Operation..................................................................................................................................243 8.3.33.3 Abnormal Conditions.................................................................................................................................244 8.4 Common Transport Channel Procedures...........................................................................................................244 8.4.1 Common Transport Channel Resources Initialisation....................................................................................244 8.4.1.1 General 244 8.4.1.2 Successful Operation....................................................................................................................................244 8.4.1.3 Unsuccessful Operation...............................................................................................................................246 8.4.1.4 Abnormal Conditions...................................................................................................................................246 8.4.2 Common Transport Channel Resources Release............................................................................................246 8.4.2.1 General 246 8.4.2.2 Successful Operation....................................................................................................................................247 8.4.2.3 Abnormal Conditions...................................................................................................................................247 8.5 Global Procedures..............................................................................................................................................247 8.5.1 Error Indication...............................................................................................................................................247 8.5.1.1 General 247 8.5.1.2 Successful Operation....................................................................................................................................247 8.5.1.2.1 Successful Operation for Iur-g..................................................................................................................248 8.5.1.3 Abnormal Conditions...................................................................................................................................248 8.5.2 Common Measurement Initiation...................................................................................................................248 8.5.2.1 General 248 8.5.2.2 Successful Operation....................................................................................................................................248 8.5.2.2.1 Successful Operation for Iur-g..................................................................................................................255 8.5.2.3 Unsuccessful Operation...............................................................................................................................256 8.5.2.4 Abnormal Conditions...................................................................................................................................256 8.5.2.4.1 Abnormal Conditions for Iur-g.................................................................................................................257 8.5.3 Common Measurement Reporting..................................................................................................................258 8.5.3.1 General 258 8.5.3.2 Successful Operation....................................................................................................................................258 8.5.3.2.1 Successful Operation for Iur-g..................................................................................................................259 8.5.3.3 Abnormal Conditions...................................................................................................................................259 8.5.4 Common Measurement Termination..............................................................................................................259 8.5.4.1 General 259 8.5.4.2 Successful Operation....................................................................................................................................259

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.4.2.1 Successful Operation for Iur-g..................................................................................................................260 8.5.4.3 Abnormal Conditions...................................................................................................................................260 8.5.5 Common Measurement Failure.......................................................................................................................260 8.5.5.1 General 260 8.5.5.2 Successful Operation....................................................................................................................................260 8.5.5.2.1 Successful Operation for Iur-g..................................................................................................................260 8.5.5.3 Abnormal Conditions...................................................................................................................................260 8.5.6 Information Exchange Initiation.....................................................................................................................260 8.5.6.1 General 260 8.5.6.2 Successful Operation....................................................................................................................................261 8.5.6.2.1 Successful Operation for Iur-g..................................................................................................................264 8.5.6.3 Unsuccessful Operation...............................................................................................................................265 8.5.6.4 Abnormal Conditions...................................................................................................................................265 8.5.6.4.1 Abnormal Conditions for Iur-g.................................................................................................................266 8.5.7 Information Reporting.....................................................................................................................................266 8.5.7.1 General 266 8.5.7.2 Successful Operation....................................................................................................................................267 8.5.7.2.1 Successful Operation for Iur-g..................................................................................................................267 8.5.7.3 Abnormal Conditions...................................................................................................................................267 8.5.8 Information Exchange Termination................................................................................................................267 8.5.8.1 General 267 8.5.8.2 Successful Operation....................................................................................................................................267 8.5.8.2.1 Successful Operation for Iur-g..................................................................................................................267 8.5.8.3 Abnormal Conditions...................................................................................................................................267 8.5.9 Information Exchange Failure.........................................................................................................................268 8.5.9.1 General 268 8.5.9.2 Successful Operation....................................................................................................................................268 8.5.9.2.1 Successful Operation for Iur-g..................................................................................................................268 8.5.10 Reset 268 8.5.10.1 General 268 8.5.10.2 Successful Operation..................................................................................................................................268 8.5.10.3 Abnormal Conditions.................................................................................................................................269 8.5.11 Direct Information Transfer..........................................................................................................................269 8.5.11.1 General 269 8.5.11.2 Successful Operation..................................................................................................................................269 8.5.12 Information Transfer Control........................................................................................................................270 8.5.12.1 General 270 8.5.12.2 Successful Operation..................................................................................................................................270 8.5.12.3 Abnormal Conditions.................................................................................................................................271 8.6 MBMS Procedures.............................................................................................................................................271 8.6.1 MBMS Attach.................................................................................................................................................271 8.6.1.1 General 271 8.6.1.2 Successful Operation....................................................................................................................................271 8.6.1.3 Abnormal Conditions...................................................................................................................................271 8.6.2 MBMS Detach................................................................................................................................................271 8.6.2.1 General 271 8.6.2.2 Successful Operation....................................................................................................................................272 8.6.2.3 Abnormal Conditions...................................................................................................................................272

9 Elements for RNSAP Communication...............................................................................................272

9.1 Message Functional Definition and Content......................................................................................................272 9.1.1 General 272 9.1.2 Message Contents............................................................................................................................................272 9.1.2.1 Presence 272 9.1.2.2 Criticality273 9.1.2.3 Range 273 9.1.2.4 Assigned Criticality......................................................................................................................................273 9.1.3 RADIO LINK SETUP REQUEST.................................................................................................................274 9.1.3.1 FDD Message...............................................................................................................................................274 9.1.3.2 TDD Message...............................................................................................................................................279 9.1.4 RADIO LINK SETUP RESPONSE...............................................................................................................283 9.1.4.1 FDD Message...............................................................................................................................................283

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.4.2 TDD Message...............................................................................................................................................287 9.1.5 RADIO LINK SETUP FAILURE..................................................................................................................295 9.1.5.1 FDD Message...............................................................................................................................................295 9.1.5.2 TDD Message...............................................................................................................................................299 9.1.6 RADIO LINK ADDITION REQUEST..........................................................................................................300 9.1.6.1 FDD Message...............................................................................................................................................300 9.1.6.2 TDD Message...............................................................................................................................................304 9.1.7 RADIO LINK ADDITION RESPONSE........................................................................................................307 9.1.7.1 FDD Message...............................................................................................................................................307 9.1.7.2 TDD Message...............................................................................................................................................311 9.1.8 RADIO LINK ADDITION FAILURE...........................................................................................................319 9.1.8.1 FDD Message...............................................................................................................................................319 9.1.8.2 TDD Message...............................................................................................................................................322 9.1.9 RADIO LINK DELETION REQUEST..........................................................................................................322 9.1.10 RADIO LINK DELETION RESPONSE......................................................................................................323 9.1.11 RADIO LINK RECONFIGURATION PREPARE......................................................................................324 9.1.11.1 FDD Message.............................................................................................................................................324 9.1.11.2 TDD Message.............................................................................................................................................330 9.1.12 RADIO LINK RECONFIGURATION READY..........................................................................................337 9.1.12.1 FDD Message.............................................................................................................................................337 9.1.12.2 TDD Message.............................................................................................................................................340 9.1.13 RADIO LINK RECONFIGURATION COMMIT.......................................................................................346 9.1.14 RADIO LINK RECONFIGURATION FAILURE.......................................................................................346 9.1.15 RADIO LINK RECONFIGURATION CANCEL........................................................................................347 9.1.16 RADIO LINK RECONFIGURATION REQUEST......................................................................................348 9.1.16.1 FDD Message.............................................................................................................................................348 9.1.16.2 TDD Message.............................................................................................................................................353 9.1.17 RADIO LINK RECONFIGURATION RESPONSE....................................................................................357 9.1.17.1 FDD Message.............................................................................................................................................357 9.1.17.2 TDD Message.............................................................................................................................................360 9.1.18 RADIO LINK FAILURE INDICATION.....................................................................................................363 9.1.19 RADIO LINK RESTORE INDICATION....................................................................................................363 9.1.20 DL POWER CONTROL REQUEST [FDD]................................................................................................364 9.1.21 PHYSICAL CHANNEL RECONFIGURATION REQUEST.....................................................................364 9.1.21.1 FDD Message.............................................................................................................................................364 9.1.21.2 TDD Message.............................................................................................................................................365 9.1.22 PHYSICAL CHANNEL RECONFIGURATION COMMAND..................................................................368 9.1.23 PHYSICAL CHANNEL RECONFIGURATION FAILURE......................................................................368 9.1.24 UPLINK SIGNALLING TRANSFER INDICATION.................................................................................368 9.1.24.1 FDD Message.............................................................................................................................................368 9.1.24.2 TDD Message.............................................................................................................................................370 9.1.24A GERAN UPLINK SIGNALLING TRANSFER INDICATION...............................................................372 9.1.25 DOWNLINK SIGNALLING TRANSFER REQUEST...............................................................................373 9.1.26 RELOCATION COMMIT............................................................................................................................373 9.1.27 PAGING REQUEST.....................................................................................................................................374 9.1.28 DEDICATED MEASUREMENT INITIATION REQUEST.......................................................................375 9.1.29 DEDICATED MEASUREMENT INITIATION RESPONSE.....................................................................376 9.1.30 DEDICATED MEASUREMENT INITIATION FAILURE........................................................................379 9.1.31 DEDICATED MEASUREMENT REPORT................................................................................................380 9.1.32 DEDICATED MEASUREMENT TERMINATION REQUEST.................................................................380 9.1.33 DEDICATED MEASUREMENT FAILURE INDICATION......................................................................381 9.1.34 COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST..........................................381 9.1.35 COMMON TRANSPORT CHANNEL RESOURCES REQUEST.............................................................382 9.1.36 COMMON TRANSPORT CHANNEL RESOURCES RESPONSE...........................................................384 9.1.36.1 FDD Message.............................................................................................................................................384 9.1.36.2 TDD Message.............................................................................................................................................387 9.1.37 COMMON TRANSPORT CHANNEL RESOURCES FAILURE..............................................................389 9.1.38 COMPRESSED MODE COMMAND [FDD]..............................................................................................389 9.1.39 ERROR INDICATION.................................................................................................................................390 9.1.40 DL POWER TIMESLOT CONTROL REQUEST [TDD]...........................................................................390 9.1.41 RADIO LINK PREEMPTION REQUIRED INDICATION........................................................................391

3GPP

Release 11

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.42 RADIO LINK CONGESTION INDICATION............................................................................................391 9.1.43 COMMON MEASUREMENT INITIATION REQUEST...........................................................................392 9.1.44 COMMON MEASUREMENT INITIATION RESPONSE.........................................................................395 9.1.45 COMMON MEASUREMENT INITIATION FAILURE............................................................................396 9.1.46 COMMON MEASUREMENT REPORT.....................................................................................................396 9.1.47 COMMON MEASUREMENT TERMINATION REQUEST.....................................................................397 9.1.48 COMMON MEASUREMENT FAILURE INDICATION..........................................................................397 9.1.49 INFORMATION EXCHANGE INITIATION REQUEST..........................................................................398 9.1.50 INFORMATION EXCHANGE INITIATION RESPONSE........................................................................399 9.1.51 INFORMATION EXCHANGE INITIATION FAILURE...........................................................................400 9.1.52 INFORMATION REPORT..........................................................................................................................401 9.1.53 INFORMATION EXCHANGE TERMINATION REQUEST....................................................................402 9.1.54 INFORMATION EXCHANGE FAILURE INDICATION.........................................................................402 9.1.55 RESET REQUEST........................................................................................................................................402 9.1.56 RESET RESPONSE......................................................................................................................................405 9.1.57 RADIO LINK ACTIVATION COMMAND................................................................................................405 9.1.57.1 FDD Message.............................................................................................................................................405 9.1.57.2 TDD Message.............................................................................................................................................405 9.1.58 RADIO LINK PARAMETER UPDATE INDICATION ............................................................................406 9.1.58.1 FDD Message.............................................................................................................................................406 9.1.58.2 TDD Message.............................................................................................................................................406 9.1.59 UE MEASUREMENT INITIATION REQUEST [TDD]............................................................................407 9.1.60 UE MEASUREMENT INITIATION RESPONSE [TDD]..........................................................................407 9.1.61 UE MEASUREMENT INITIATION FAILURE [TDD].............................................................................407 9.1.62 UE MEASUREMENT REPORT [TDD]......................................................................................................407 9.1.63 UE MEASUREMENT TERMINATION REQUEST [TDD]......................................................................408 9.1.64 UE MEASUREMENT FAILURE INDICATION [TDD]............................................................................408 9.1.65 IUR INVOKE TRACE.................................................................................................................................408 9.1.66 IUR DEACTIVATE TRACE.......................................................................................................................408 9.1.67 MBMS ATTACH COMMAND...................................................................................................................409 9.1.68 MBMS DETACH COMMAND...................................................................................................................410 9.1.69 DIRECT INFORMATION TRANSFER......................................................................................................411 9.1.70 ENHANCED RELOCATION REQUEST...................................................................................................412 9.1.71 ENHANCED RELOCATION RESPONSE.................................................................................................412 9.1.72 ENHANCED RELOCATION FAILURE....................................................................................................413 9.1.73 ENHANCED RELOCATION CANCEL.....................................................................................................413 9.1.74 ENHANCED RELOCATION SIGNALLING TRANSFER........................................................................413 9.1.75 ENHANCED RELOCATION RELEASE....................................................................................................413 9.1.76 MBSFN MCCH INFORMATION (FDD)....................................................................................................414 9.1.77 SECONDARY UL FREQUENCY REPORT...............................................................................................414 9.1.77.1 FDD Message.............................................................................................................................................414 9.1.78 SECONDARY UL FREQUENCY UPDATE INDICATION......................................................................414 9.1.78.1 FDD Message.............................................................................................................................................414 9.1.79 ENHANCED RELOCATION RESOURCE REQUEST [TDD].................................................................415 9.1.80 ENHANCED RELOCATION RESOURCE RESPONSE [TDD]...............................................................415 9.1.81 ENHANCED RELOCATION RESOURCE FAILURE [TDD]...................................................................415 9.1.82 ENHANCED RELOCATION RESOURCE RELEASE COMMAND [TDD]............................................415 9.1.83 ENHANCED RELOCATION RESOURCE RELEASE COMPLETE [TDD]............................................416 9.1.84 INFORMATION TRANSFER CONTROL REQUEST..............................................................................416 9.2 Information Element Functional Definition and Contents.................................................................................416 9.2.0 General 416 9.2.1 Common Parameters.......................................................................................................................................416 9.2.1.1 Allocation/Retention Priority.......................................................................................................................416 9.2.1.2 Allowed Queuing Time................................................................................................................................417 9.2.1.2A Allowed Rate Information.........................................................................................................................417 9.2.1.2B Altitude and Direction...............................................................................................................................417 9.2.1.2C Antenna Co-location Indicator..................................................................................................................418 9.2.1.2D Alternative Format Reporting Indicator....................................................................................................418 9.2.1.3 Binding ID....................................................................................................................................................418 9.2.1.4 BLER 418 9.2.1.4A Block STTD Indicator...............................................................................................................................419

3GPP

Release 11

10

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.4B Burst Mode Parameters.............................................................................................................................419 9.2.1.5 Cause 419 9.2.1.5A Cell Geographical Area Identity (Cell GAI).............................................................................................425 9.2.1.5B Cell Geographical Area Additional Shapes (Cell GAI Additional Shapes)..............................................426 9.2.1.5C Cell Capacity Class Value.........................................................................................................................426 9.2.1.5D Cell Global Identifier (CGI)......................................................................................................................427 9.2.1.6 Cell Identifier (C-ID)...................................................................................................................................427 9.2.1.7 Cell Individual Offset...................................................................................................................................428 9.2.1.8 Cell Parameter ID.........................................................................................................................................428 9.2.1.9 CFN 428 9.2.1.10 CFN Offset.................................................................................................................................................428 9.2.1.11 CN CS Domain Identifier...........................................................................................................................428 9.2.1.11A CN Domain Type....................................................................................................................................429 9.2.1.12 CN PS Domain Identifier...........................................................................................................................429 9.2.1.12A Common Measurement Accuracy...........................................................................................................430 9.2.1.12B Common Measurement Object Type.......................................................................................................430 9.2.1.12C Common Measurement Type..................................................................................................................430 9.2.1.12D Common Measurement Value.................................................................................................................430 9.2.1.12E Common Measurement Value Information.............................................................................................431 9.2.1.12F Common Transport Channel Resources Initialisation Not Required......................................................432 9.2.1.12G Coverage Indicator..................................................................................................................................432 9.2.1.13 Criticality Diagnostics................................................................................................................................432 9.2.1.14 C-RNTI 434 9.2.1.14A CTFC 434 9.2.1.15 DCH Combination Indicator......................................................................................................................435 9.2.1.16 DCH ID 435 9.2.1.16A DCH Information Response....................................................................................................................435 9.2.1.17 Dedicated Measurement Object Type........................................................................................................436 9.2.1.18 Dedicated Measurement Type....................................................................................................................436 9.2.1.19 Dedicated Measurement Value..................................................................................................................436 9.2.1.19A Dedicated Measurement Value Information...........................................................................................438 9.2.1.19Aa Delayed Activation................................................................................................................................438 9.2.1.19Ab Delayed Activation Update...................................................................................................................439 9.2.1.19B DGPS Corrections...................................................................................................................................439 9.2.1.19C Discard Timer..........................................................................................................................................440 9.2.1.20 Diversity Control Field..............................................................................................................................441 9.2.1.21 Diversity Indication....................................................................................................................................441 9.2.1.21A DL Power................................................................................................................................................441 9.2.1.22 Downlink SIR Target.................................................................................................................................441 9.2.1.23 DPCH Constant Value...............................................................................................................................441 9.2.1.24 D-RNTI 442 9.2.1.25 D-RNTI Release Indication........................................................................................................................442 9.2.1.26 DRX Cycle Length Coefficient..................................................................................................................442 9.2.1.26A DSCH ID.................................................................................................................................................442 9.2.1.26Aa DSCH Initial Window Size...................................................................................................................442 9.2.1.26B DSCH Flow Control Information............................................................................................................442 9.2.1.26Ba DSCH-RNTI..........................................................................................................................................442 9.2.1.26Bb Extended GSM Cell Individual Offset..................................................................................................442 9.2.1.26C FACH Flow Control Information............................................................................................................443 9.2.1.27 FACH Initial Window Size........................................................................................................................443 9.2.1.28 FACH Priority Indicator............................................................................................................................443 9.2.1.28A FN Reporting Indicator...........................................................................................................................443 9.2.1.29 Frame Handling Priority............................................................................................................................444 9.2.1.30 Frame Offset...............................................................................................................................................444 9.2.1.30A GA Point with Uncertainty......................................................................................................................444 9.2.1.30B GA Ellipsoid Point with Uncertainty Ellipse..........................................................................................444 9.2.1.30C GA Ellipsoid Point with Altitude............................................................................................................444 9.2.1.30D GA Ellipsoid Point with Altitude and Uncertainty Ellipsoid..................................................................444 9.2.1.30E GA Ellipsoid Arc.....................................................................................................................................445 9.2.1.30F Geographical Coordinates........................................................................................................................445 9.2.1.30Fa GERAN Cell Capability.........................................................................................................................445

3GPP

Release 11

11

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.30Fb GERAN Classmark................................................................................................................................446 9.2.1.30Fc GERAN System Information.................................................................................................................446 9.2.1.30G GPS Almanac..........................................................................................................................................446 9.2.1.30H GPS Ionospheric Model..........................................................................................................................447 9.2.1.30I GPS Navigation Model and Time Recovery............................................................................................448 9.2.1.30J GPS Real-Time Integrity..........................................................................................................................449 9.2.1.30K GPS Receiver Geographical Position (GPS RX Pos).............................................................................450 9.2.1.30L GPS UTC Model......................................................................................................................................450 9.2.1.30M Guaranteed Rate Information.................................................................................................................450 9.2.1.30N HCS Prio.................................................................................................................................................450 9.2.1.30NA HS-DSCH Information To Modify Unsynchronised...........................................................................451 9.2.1.30Na HS-DSCH Initial Capacity Allocation..................................................................................................452 9.2.1.30Nb HS-DSCH Initial Window Size.............................................................................................................454 9.2.1.30O HS-DSCH MAC-d Flow ID....................................................................................................................454 9.2.1.30OA HS-DSCH MAC-d Flows Information.................................................................................................454 9.2.1.30OB HS-DSCH MAC-d Flows To Delete....................................................................................................456 9.2.1.30OC HS-DSCH MAC-d PDU Size Format..................................................................................................456 9.2.1.30Oa HS-DSCH Physical Layer Category.....................................................................................................456 9.2.1.30P HS-DSCH-RNTI......................................................................................................................................457 9.2.1.30Q HS-DSCH Information To Modify.........................................................................................................458 9.2.1.30R HS-SCCH Code Change Indicator..........................................................................................................462 9.2.1.30S HS-SCCH Code Change Grant................................................................................................................462 9.2.1.30T IMEI 463 9.2.1.30U IMEISV...................................................................................................................................................463 9.2.1.30V HS-PDSCH Code Change Indicator [FDD]............................................................................................463 9.2.1.30W HS-PDSCH Code Change Grant [FDD]................................................................................................463 9.2.1.31 IMSI 464 9.2.1.31A Information Exchange ID........................................................................................................................464 9.2.1.31B Information Exchange Object Type........................................................................................................464 9.2.1.31C Information Report Characteristics.........................................................................................................464 9.2.1.31D Information Threshold.............................................................................................................................464 9.2.1.31E Information Type.....................................................................................................................................465 9.2.1.31F IPDL Parameters......................................................................................................................................469 9.2.1.31G Inter-frequency Cell Information............................................................................................................469 9.2.1.32 L3 Information...........................................................................................................................................470 9.2.1.33 Limited Power Increase..............................................................................................................................470 9.2.1.33A Load Value..............................................................................................................................................470 9.2.1.34 MAC-c/sh SDU Length..............................................................................................................................470 9.2.1.34A MAC-d PDU Size....................................................................................................................................470 9.2.1.34Aa MAC-hs Guaranteed Bit Rate...............................................................................................................470 9.2.1.34Ab MAC-hs Reordering Buffer Size for RLC-UM....................................................................................471 9.2.1.34B MAC-hs Reset Indicator..........................................................................................................................471 9.2.1.34C MAC-hs Window Size ...........................................................................................................................471 9.2.1.34D MAC PDU Size Extended.......................................................................................................................471 9.2.1.35 Maximum Allowed UL Tx Power.............................................................................................................471 9.2.1.35A Measurement Availability Indicator........................................................................................................472 9.2.1.35B Measurement Change Time.....................................................................................................................472 9.2.1.36 Measurement Filter Coefficient.................................................................................................................472 9.2.1.36A Measurement Hysteresis Time................................................................................................................472 9.2.1.37 Measurement ID.........................................................................................................................................472 9.2.1.38 Measurement Increase/Decrease Threshold...............................................................................................472 9.2.1.38A Measurement Recovery Behavior...........................................................................................................474 9.2.1.38B Measurement Recovery Reporting Indicator...........................................................................................474 9.2.1.38C Measurement Recovery Support Indicator..............................................................................................474 9.2.1.39 Measurement Threshold.............................................................................................................................474 9.2.1.39A Message Structure...................................................................................................................................476 9.2.1.40 Message Type.............................................................................................................................................477 9.2.1.41 Multiple URAs Indicator............................................................................................................................480 9.2.1.41a NACC Related Data.................................................................................................................................480 9.2.1.41A Neighbouring UMTS Cell Information...................................................................................................480 9.2.1.41B Neighbouring FDD Cell Information......................................................................................................481

3GPP

Release 11

12

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.41C Neighbouring GSM Cell Information.....................................................................................................483 9.2.1.41D Neighbouring TDD Cell Information......................................................................................................485 9.2.1.41Dd Neighbouring TDD Cell Measurement Information LCR....................................................................486 9.2.1.41De Neighbouring E-UTRA Cell Information.............................................................................................486 9.2.1.41Df EARFCN................................................................................................................................................487 9.2.1.41E Paging Cause...........................................................................................................................................487 9.2.1.41F Paging Record Type.................................................................................................................................487 9.2.1.41Fa Partial Reporting Indicator....................................................................................................................487 9.2.1.41G Neighbouring FDD Cell Measurement Information...............................................................................488 9.2.1.41H Neighbouring TDD Cell Measurement Information...............................................................................488 9.2.1.41I NRT Load Information Value...................................................................................................................488 9.2.1.42 Payload CRC Present Indicator..................................................................................................................489 9.2.1.43 PCCPCH Power.........................................................................................................................................489 9.2.1.44 Primary CPICH Power...............................................................................................................................489 9.2.1.45 Primary Scrambling Code..........................................................................................................................490 9.2.1.45A Priority Queue ID....................................................................................................................................490 9.2.1.45B Process Memory Size..............................................................................................................................490 9.2.1.46 Puncture Limit............................................................................................................................................490 9.2.1.46A QE-Selector.............................................................................................................................................491 9.2.1.47 RANAP Relocation Information................................................................................................................491 9.2.1.48 Report Characteristics................................................................................................................................491 9.2.1.48a Report Periodicity.....................................................................................................................................493 9.2.1.48A Requested Data Value.............................................................................................................................493 9.2.1.48B Requested Data Value Information.........................................................................................................495 9.2.1.48C Restriction State Indicator.......................................................................................................................495 9.2.1.48D RLC Mode...............................................................................................................................................495 9.2.1.49 RL ID 495 9.2.1.49A RL Specific DCH Information................................................................................................................496 9.2.1.50 RNC-ID 496 9.2.1.50a Extended RNC-ID....................................................................................................................................496 9.2.1.50A SAT ID....................................................................................................................................................496 9.2.1.50B RT Load Value........................................................................................................................................497 9.2.1.51 SCH Time Slot...........................................................................................................................................497 9.2.1.51A Scheduling Priority Indicator..................................................................................................................497 9.2.1.52 Service Area Identifier (SAI).....................................................................................................................497 9.2.1.52A SFN 498 9.2.1.52B SFN-SFN Measurement Threshold Information.....................................................................................498 9.2.1.52C SFN-SFN Measurement Value Information............................................................................................498 9.2.1.52Ca Shared Network Area (SNA) Information.............................................................................................499 9.2.1.52D SID 500 9.2.1.53 S-RNTI 500 9.2.1.53a S-RNTI Group..........................................................................................................................................500 9.2.1.54 Sync Case...................................................................................................................................................501 9.2.1.54A T1 501 9.2.1.55 TFCI Presence............................................................................................................................................501 9.2.1.56 Time Slot....................................................................................................................................................501 9.2.1.56A TNL QoS ................................................................................................................................................501 9.2.1.57 ToAWE .....................................................................................................................................................502 9.2.1.58 ToAWS 502 9.2.1.58a Trace Depth..............................................................................................................................................502 9.2.1.58b Trace Recording Session Reference.........................................................................................................502 9.2.1.58c Trace Reference........................................................................................................................................503 9.2.1.58A Traffic Class............................................................................................................................................503 9.2.1.59 Transaction ID............................................................................................................................................503 9.2.1.59A Transmitted Carrier Power......................................................................................................................503 9.2.1.59B TUTRAN-GPS Accuracy Class..............................................................................................................504 9.2.1.59C TUTRAN-GPS Measurement Threshold Information............................................................................504 9.2.1.59D TUTRAN-GPS Measurement Value Information...................................................................................504 9.2.1.60 Transport Bearer ID...................................................................................................................................505 9.2.1.61 Transport Bearer Request Indicator...........................................................................................................505 9.2.1.62 Transport Layer Address............................................................................................................................506

3GPP

Release 11

13

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.63 Transport Format Combination Set (TFCS)..............................................................................................506 9.2.1.64 Transport Format Set..................................................................................................................................507 9.2.1.65 TrCH Source Statistics Descriptor.............................................................................................................509 9.2.1.66 UARFCN....................................................................................................................................................509 9.2.1.66A UE Identity..............................................................................................................................................509 9.2.1.67 UL FP Mode...............................................................................................................................................509 9.2.1.68 UL Interference Level................................................................................................................................509 9.2.1.68A Uncertainty Ellipse..................................................................................................................................510 9.2.1.68B Unidirectional DCH Indicator.................................................................................................................510 9.2.1.69 Uplink SIR.................................................................................................................................................510 9.2.1.70 URA ID 510 9.2.1.70A UTRAN Access Point Position...............................................................................................................510 9.2.1.70B URA Information.....................................................................................................................................511 9.2.1.70C User Plane Congestion Fields Inclusion..................................................................................................511 9.2.1.71 UTRAN Cell Identifier (UC-ID)................................................................................................................511 9.2.1.72 Neighbouring TDD Cell Information LCR................................................................................................512 9.2.1.73 Permanent NAS UE Identity......................................................................................................................512 9.2.1.74 SFN-SFN Measurement Reference Point Position....................................................................................513 9.2.1.75 UTRAN Access Point Position with Altitude............................................................................................513 9.2.1.76 SFN-SFN Measurement Time Stamp........................................................................................................513 9.2.1.77 SFN-SFN Value.........................................................................................................................................513 9.2.1.78 SCTD Indicator..........................................................................................................................................513 9.2.1.79 Congestion Cause.......................................................................................................................................514 9.2.1.80 TMGI 514 9.2.1.81 Transmission Mode....................................................................................................................................514 9.2.1.82 Access Point Name....................................................................................................................................515 9.2.1.83 IP Multicast Address..................................................................................................................................515 9.2.1.84 MBMS Bearer Service Full Address..........................................................................................................515 9.2.1.85 Provided Information.................................................................................................................................515 9.2.1.86 MBMS Channel Type Information............................................................................................................516 9.2.1.87 MBMS Preferred Frequency Layer Information........................................................................................518 9.2.1.88 E-DCH DDI Value.....................................................................................................................................519 9.2.1.89 E-DCH MAC-d Flow Multiplexing List....................................................................................................519 9.2.1.90 E-DCH MAC-d Flows To Delete..............................................................................................................519 9.2.1.91 E-DCH MAC-d Flow ID............................................................................................................................519 9.2.1.91A E-DCH MAC-d PDU Size Format..........................................................................................................520 9.2.1.92 E-DCH Logical Channel Information........................................................................................................520 9.2.1.93 E-DCH Logical Channel To Modify..........................................................................................................521 9.2.1.94 E-RNTI 522 9.2.1.95 E-DCH Processing Overload Level...........................................................................................................522 9.2.1.96 E-DCH Power Offset for Scheduling Info.................................................................................................523 9.2.1.97 Logical channel ID.....................................................................................................................................523 9.2.1.98 MAC-es Guaranteed Bit Rate....................................................................................................................523 9.2.1.99 MAC-e Reset Indicator..............................................................................................................................523 9.2.1.100 Maximum Number of Retransmissions for E-DCH.................................................................................523 9.2.1.101 Scheduling Information............................................................................................................................524 9.2.1.102 DGANSS Corrections..............................................................................................................................524 9.2.1.103 GANSS Almanac.....................................................................................................................................526 9.2.1.104 GANSS Clock Model...............................................................................................................................531 9.2.1.104a GANSS Additional Clock Models.........................................................................................................532 9.2.1.105 GANSS Ionospheric Model.....................................................................................................................535 9.2.1.105a GANSS Additional Ionospheric Model.................................................................................................535 9.2.1.106 GANSS Navigation Model......................................................................................................................535 9.2.1.107 GANSS Orbit Model................................................................................................................................535 9.2.1.107a GANSS Additional Orbit Models..........................................................................................................536 9.2.1.108 GANSS Real Time Integrity....................................................................................................................540 9.2.1.109 GANSS Receiver Geographical Position (GANSS RX Pos)...................................................................541 9.2.1.110 GANSS Time Model................................................................................................................................541 9.2.1.110a GANSS Additional Time Models..........................................................................................................542 9.2.1.111 GANSS UTC Model................................................................................................................................542 9.2.1.111a GANSS Additional UTC Models...........................................................................................................542

3GPP

Release 11

14

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.112 TUTRAN-GANSS Accuracy Class.........................................................................................................544 9.2.1.113 TUTRAN-GANSS Measurement Threshold Information.......................................................................544 9.2.1.114 TUTRAN-GANSS Measurement Value Information..............................................................................545 9.2.1.115 GANSS Reference Time..........................................................................................................................547 9.2.1.116 HARQ Memory Partitioning....................................................................................................................548 9.2.1.117 Multiple PLMN List.................................................................................................................................549 9.2.1.118 GANSS Data Bit Assistance....................................................................................................................549 9.2.1.119 GANSS ID...............................................................................................................................................550 9.2.1.119a GANSS Time ID....................................................................................................................................550 9.2.1.120 GANSS Navigation Model And Time Recovery.....................................................................................550 9.2.1.120a GANSS Additional Navigation Models And Time Recovery...............................................................551 9.2.1.121 GANSS Signal ID....................................................................................................................................552 9.2.1.122 GANSS Transmission Time.....................................................................................................................552 9.2.1.122a GANSS Earth Orientation Parameters...................................................................................................552 9.2.1.122b SBAS ID.................................................................................................................................................553 9.2.1.122c GANSS Auxiliary Information..............................................................................................................554 9.2.1.122d Additional Ionospheric Model Request.................................................................................................554 9.2.1.122e Earth Orientation Parameters Request...................................................................................................554 9.2.1.122f GANSS Additional Navigation Models And Time Recovery Request..................................................554 9.2.1.122g GANSS Additional UTC Models Request.............................................................................................555 9.2.1.122h GANSS Auxiliary Information Request................................................................................................555 9.2.1.123 SixtyfourQAM DL Support Indicator......................................................................................................555 9.2.1.124 RANAP Enhanced Relocation Information Request...............................................................................555 9.2.1.125 RANAP Enhanced Relocation Information Response.............................................................................555 9.2.1.126 Released CN Domain...............................................................................................................................555 9.2.1.127 Secondary CCPCH system information MBMS......................................................................................556 9.2.1.128 MBSFN Cluster Identity..........................................................................................................................556 9.2.1.129 MBSFN Scheduling Transmission Time Interval....................................................................................556 9.2.1.130 MAC-ehs Reset Timer.............................................................................................................................556 9.2.1.131 Enhanced FACH Support Indicator.........................................................................................................556 9.2.1.132 Enhanced PCH Capability........................................................................................................................556 9.2.1.133 Priority Queue Information for Enhanced FACH/PCH...........................................................................557 9.2.1.134 MIMO Activation Indicator.....................................................................................................................557 9.2.1.135 MIMO Mode Indicator.............................................................................................................................557 9.2.1.136 DL RLC PDU Size Format......................................................................................................................557 9.2.1.137 UE Aggregate Maximum Bit Rate...........................................................................................................558 9.2.1.138 DGNSS Validity Period...........................................................................................................................558 9.2.1.139 MDT Configuration.................................................................................................................................559 9.2.1.140 MDT Report parameters..........................................................................................................................561 9.2.1.141 Neighbouring UMTS Cell Information Extension...................................................................................561 9.2.1.142 Source ID.................................................................................................................................................562 9.2.1.143 Target ID..................................................................................................................................................562 9.2.1.144 MS Classmark 2.......................................................................................................................................562 9.2.1.145 MS Classmark 3.......................................................................................................................................562 9.2.1.146 Speech Version.........................................................................................................................................563 9.2.1.147 Controlled Object Scope..........................................................................................................................563 9.2.1.148 ANR Report Indication............................................................................................................................563 9.2.1.149 ANR Cell Information..............................................................................................................................564 9.2.1.150 ANR FDD Cell Information.....................................................................................................................564 9.2.1.151 ANR TDD Cell Information....................................................................................................................565 9.2.1.152 ANR TDD Cell Information LCR............................................................................................................565 9.2.1.153 ANR Multiple PLMN List.......................................................................................................................566 9.2.1.154 Extended RNTI........................................................................................................................................566 9.2.1.155 Extended S-RNTI Group..........................................................................................................................566 9.2.2 FDD Specific Parameters................................................................................................................................567 9.2.2.a ACK-NACK Repetition Factor....................................................................................................................567 9.2.2.b ACK Power Offset.......................................................................................................................................567 9.2.2.A Active Pattern Sequence Information.........................................................................................................567 9.2.2.B Adjustment Period.......................................................................................................................................568 9.2.2.C Adjustment Ratio.........................................................................................................................................568 9.2.2.Ca Bundling Mode Indicator...........................................................................................................................569

3GPP

Release 11

15

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.D Cell Capability Container FDD...................................................................................................................569 9.2.2.E Cell Portion ID.............................................................................................................................................572 9.2.2.1 Chip Offset...................................................................................................................................................572 9.2.2.2 Closed Loop Mode1 Support Indicator........................................................................................................572 9.2.2.3 Closed Loop Mode2 Support Indicator........................................................................................................572 9.2.2.3A Closed Loop Timing Adjustment Mode....................................................................................................572 9.2.2.4 Compressed Mode Method..........................................................................................................................572 9.2.2.4A DCH FDD Information.............................................................................................................................572 9.2.2.4B E-DCH FDD Information..........................................................................................................................573 9.2.2.4C E-DCH FDD Information Response.........................................................................................................574 9.2.2.4D E-DCH FDD DL Control Channel Information........................................................................................575 9.2.2.4E E-DCH RL Indication................................................................................................................................577 9.2.2.4F E-DCH FDD Information To Modify........................................................................................................577 9.2.2.4G E-DCH Transport Format Combination Set Information (E-TFCS Information)....................................580 9.2.2.4J E-TTI 582 9.2.2.4K E-DPCCH Power Offset............................................................................................................................582 9.2.2.4KA Void 582 9.2.2.4L E-DCH HARQ Power Offset FDD............................................................................................................582 9.2.2.4M Void 582 9.2.2.4MA Void 582 9.2.2.4MB Void 582 9.2.2.4MC E-DCH MAC-d Flows Information.......................................................................................................582 9.2.2.4MD Void 584 9.2.2.4ME Void 584 9.2.2.4MF Void 584 9.2.2.4MG E-DCH Maximum Bitrate......................................................................................................................584 9.2.2.4MH Void 584 9.2.2.4MI E-DCH Reference Power Offset.............................................................................................................584 9.2.2.4MJ Void 584 9.2.2.4N Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission.......................................584 9.2.2.4O HARQ Process Allocation For 2ms TTI...................................................................................................585 9.2.2.4P Reference E-TFCI Power Offset................................................................................................................585 9.2.2.4Q Extended Reference E-TFCI Power Offset...............................................................................................585 9.2.2.4R Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission.......................585 9.2.2.4S Transport Bearer Not Requested Indicator................................................................................................586 9.2.2.4T Transport Bearer Not Setup Indicator........................................................................................................586 9.2.2.5 D-Field Length.............................................................................................................................................586 9.2.2.6 Diversity Control Field................................................................................................................................586 9.2.2.7 Diversity Indication......................................................................................................................................586 9.2.2.8 Diversity Mode.............................................................................................................................................586 9.2.2.9 DL DPCH Slot Format.................................................................................................................................586 9.2.2.9A DL DPCH Timing Adjustment.................................................................................................................587 9.2.2.10 DL Power...................................................................................................................................................587 9.2.2.10A DL Power Balancing Information...........................................................................................................587 9.2.2.10B DL Power Balancing Activation Indicator..............................................................................................587 9.2.2.10C DL Reference Power Information...........................................................................................................588 9.2.2.10D DL Power Balancing Updated Indicator.................................................................................................588 9.2.2.11 DL Scrambling Code..................................................................................................................................588 9.2.2.12 Downlink Frame Type...............................................................................................................................588 9.2.2.12A DPC Mode...............................................................................................................................................588 9.2.2.13 DRAC Control...........................................................................................................................................589 9.2.2.13A DSCH FDD Information.........................................................................................................................589 9.2.2.13B DSCH FDD Information Response.........................................................................................................589 9.2.2.13Bb DSCH-RNTI..........................................................................................................................................589 9.2.2.13C FDD DCHs To Modify............................................................................................................................589 9.2.2.13D Enhanced DSCH PC................................................................................................................................590 9.2.2.13E Enhanced DSCH PC Counter..................................................................................................................590 9.2.2.13F Enhanced DSCH PC Indicator.................................................................................................................590 9.2.2.13G Enhanced DSCH PC Wnd.......................................................................................................................590 9.2.2.13H Enhanced DSCH Power Offset...............................................................................................................590 9.2.2.13I Enhanced Primary CPICH Ec/No.............................................................................................................590

3GPP

Release 11

16

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.14 FDD DL Channelisation Code Number.....................................................................................................591 9.2.2.14A FDD DL Code Information.....................................................................................................................591 9.2.2.15 FDD S-CCPCH Offset...............................................................................................................................591 9.2.2.16 FDD TPC Downlink Step Size..................................................................................................................591 9.2.2.16A First RLS Indicator..................................................................................................................................591 9.2.2.17 Gap Position Mode.....................................................................................................................................592 9.2.2.18 Gap Period (TGP)......................................................................................................................................592 9.2.2.19 Gap Starting Slot Number (SN).................................................................................................................592 9.2.2.19a HS-DSCH FDD Information....................................................................................................................592 9.2.2.19aa HS-DSCH FDD Secondary Serving Information...................................................................................594 9.2.2.19b HS-DSCH FDD Information Response...................................................................................................595 9.2.2.19ba HS-DSCH FDD Secondary Serving Information Response..................................................................596 9.2.2.19bb HS-DSCH FDD Secondary Serving Information To Modify................................................................597 9.2.2.19bc HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised.....................................598 9.2.2.19c HS-DSCH FDD Update Information ......................................................................................................599 9.2.2.19ca HS-DSCH FDD Secondary Serving Update Information......................................................................599 9.2.2.19C HS-DSCH configured indicator..............................................................................................................600 9.2.2.19d HS-SCCH Power Offset...........................................................................................................................600 9.2.2.19e E-DCH FDD Update Information............................................................................................................600 9.2.2.19f HS-DSCH Serving Cell Change Information...........................................................................................600 9.2.2.19g HS-DSCH Serving Cell Change Information Response..........................................................................601 9.2.2.19ga HS-DSCH Secondary Serving Cell Change Information Response......................................................601 9.2.2.19G HS-DSCH TB Size Table Indicator........................................................................................................601 9.2.2.19h E-DCH Serving Cell Change Information Response...............................................................................602 9.2.2.20 IB_SG_POS...............................................................................................................................................602 9.2.2.21 IB_SG_REP...............................................................................................................................................602 9.2.2.21a Inner Loop DL PC Status.........................................................................................................................602 9.2.2.21b Initial DL DPCH Timing Adjustment Allowed.......................................................................................602 9.2.2.21A Limited Power Increase...........................................................................................................................602 9.2.2.21B IPDL FDD Parameters............................................................................................................................603 9.2.2.21C Length of TFCI2......................................................................................................................................603 9.2.2.21D Void 603 9.2.2.21E Void 603 9.2.2.21F Void 603 9.2.2.22 Max Adjustment Period.............................................................................................................................603 9.2.2.23 Max Adjustment Step.................................................................................................................................603 9.2.2.24 Max Number of UL DPDCHs....................................................................................................................603 9.2.2.24a CQI Feedback Cycle k.............................................................................................................................603 9.2.2.24b CQI Power Offset.....................................................................................................................................604 9.2.2.24c CQI Repetition Factor..............................................................................................................................604 9.2.2.24d Measurement Power Offset......................................................................................................................604 9.2.2.24e Maximum Set of E-DPDCHs...................................................................................................................604 9.2.2.24f Void 604 9.2.2.24A Min DL Channelisation Code Length.....................................................................................................604 9.2.2.25 Min UL Channelisation Code Length........................................................................................................605 9.2.2.26 Multiplexing Position.................................................................................................................................605 9.2.2.26a NACK Power Offset................................................................................................................................605 9.2.2.26A Number of DL Channelisation Codes.....................................................................................................605 9.2.2.27 Pattern Duration (PD)................................................................................................................................605 9.2.2.27a PC Preamble.............................................................................................................................................605 9.2.2.27A PDSCH Code Mapping...........................................................................................................................605 9.2.2.27B Phase Reference Update Indicator...........................................................................................................606 9.2.2.28 Power Adjustment Type.............................................................................................................................606 9.2.2.29 Power Control Mode (PCM)......................................................................................................................606 9.2.2.30 Power Offset...............................................................................................................................................606 9.2.2.31 Power Resume Mode (PRM).....................................................................................................................606 9.2.2.31A Preamble Signatures................................................................................................................................606 9.2.2.32 Primary CPICH Ec/No...............................................................................................................................606 9.2.2.32A Primary CPICH Usage For Channel Estimation.....................................................................................607 9.2.2.33 Propagation Delay (PD).............................................................................................................................607 9.2.2.33a Extended Propagation Delay....................................................................................................................607

3GPP

Release 11

17

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.33A PRACH Minimum Spreading Factor......................................................................................................607 9.2.2.34 QE-Selector................................................................................................................................................607 9.2.2.34a Qth Parameter...........................................................................................................................................607 9.2.2.34A RACH Sub Channel Numbers.................................................................................................................607 9.2.2.35 RL Set ID...................................................................................................................................................607 9.2.2.35a RL Specific E-DCH Information.............................................................................................................608 9.2.2.35A Received Total Wide Band Power..........................................................................................................608 9.2.2.36 S-Field Length............................................................................................................................................608 9.2.2.36A Void 608 9.2.2.37 Scrambling Code Change...........................................................................................................................608 9.2.2.37A Scrambling Code Number.......................................................................................................................608 9.2.2.37B Secondary CCPCH Info..........................................................................................................................608 9.2.2.38 Secondary CCPCH Slot Format.................................................................................................................609 9.2.2.38A Secondary CPICH Information...............................................................................................................609 9.2.2.38B Secondary CPICH Information Change..................................................................................................609 9.2.2.38C Serving E-DCH RL.................................................................................................................................609 9.2.2.39 Slot Number (SN)......................................................................................................................................609 9.2.2.39a Split Type.................................................................................................................................................609 9.2.2.39A SRB Delay...............................................................................................................................................609 9.2.2.40 SSDT Cell Identity.....................................................................................................................................610 9.2.2.40A SSDT Cell Identity for EDSCHPC.........................................................................................................610 9.2.2.41 SSDT Cell Identity Length.........................................................................................................................610 9.2.2.42 SSDT Indication.........................................................................................................................................610 9.2.2.43 SSDT Support Indicator.............................................................................................................................610 9.2.2.44 STTD Indicator..........................................................................................................................................610 9.2.2.45 STTD Support Indicator.............................................................................................................................610 9.2.2.45A Synchronisation Indicator.......................................................................................................................610 9.2.2.46 TFCI Signalling Mode ..............................................................................................................................610 9.2.2.46A TFCI PC Support Indicator.....................................................................................................................611 9.2.2.47 Transmission Gap Distance (TGD)............................................................................................................611 9.2.2.47A Transmission Gap Pattern Sequence Information...................................................................................611 9.2.2.47B Transmission Gap Pattern Sequence Scrambling Code Information......................................................613 9.2.2.48 Transmit Diversity Indicator......................................................................................................................613 9.2.2.49 Transmit Gap Length (TGL)......................................................................................................................613 9.2.2.50 Tx Diversity Indicator................................................................................................................................614 9.2.2.50A UE Support Of Dedicated Pilots For Channel Estimation......................................................................614 9.2.2.50B UE Support Of Dedicated Pilots For Channel Estimation Of HS-DSCH...............................................614 9.2.2.51 UL/DL Compressed Mode Selection.........................................................................................................614 9.2.2.52 UL DPCCH Slot Format............................................................................................................................614 9.2.2.52A UL DPDCH Indicator for E-DCH operation...........................................................................................614 9.2.2.53 UL Scrambling Code..................................................................................................................................614 9.2.2.54 Uplink Delta SIR........................................................................................................................................615 9.2.2.55 Uplink Delta SIR After..............................................................................................................................615 9.2.2.56 DPC Mode Change Support Indicator.......................................................................................................615 9.2.2.57 HARQ Preamble Mode..............................................................................................................................615 9.2.2.58 HARQ Preamble Mode Activation Indicator.............................................................................................615 9.2.2.59 Frequency Band Indicator..........................................................................................................................615 9.2.2.60 E-RGCH Release Indicator........................................................................................................................616 9.2.2.61 E-AGCH Power Offset..............................................................................................................................616 9.2.2.61A E-AGCH Table Choice...........................................................................................................................616 9.2.2.62 E-RGCH Power Offset...............................................................................................................................617 9.2.2.63 E-HICH Power Offset................................................................................................................................617 9.2.2.64 E-RGCH 2-Index-Step Threshold..............................................................................................................617 9.2.2.65 E-RGCH 3-Index-Step Threshold..............................................................................................................617 9.2.2.66 HARQ Info for E-DCH..............................................................................................................................617 9.2.2.67 DCH Indicator For E-DCH-HSDPA Operation.........................................................................................618 9.2.2.68 E-RGCH and E-HICH Channelisation Code Validity Indicator................................................................618 9.2.2.69 E-DCH Minimum Set E-TFCI Validity Indicator.....................................................................................618 9.2.2.70 Fast Reconfiguration Mode........................................................................................................................618 9.2.2.71 Fast Reconfiguration Permission...............................................................................................................619 9.2.2.72 Continuous Packet Connectivity DTX-DRX Information ........................................................................619

3GPP

Release 11

18

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.73 Continuous Packet Connectivity DTX-DRX Information To Modify......................................................620 9.2.2.74 Continuous Packet Connectivity HS-SCCH less Information ..................................................................621 9.2.2.75 Continuous Packet Connectivity HS-SCCH less Information Response...................................................621 9.2.2.75A Continuous Packet Connectivity HS-SCCH Less Deactivate Indicator.................................................621 9.2.2.76 MIMO Activation Indicator.......................................................................................................................622 9.2.2.77 MIMO Mode Indicator...............................................................................................................................622 9.2.2.78 MIMO Information Response....................................................................................................................622 9.2.2.79 SixtyfourQAM DL Support Indicator........................................................................................................622 9.2.2.79A Sixtyfour QAM Usage Allowed Indicator..............................................................................................622 9.2.2.79B SixtyfourQAM DL Usage Indicator........................................................................................................622 9.2.2.80 Enhanced FACH Support Indicator...........................................................................................................622 9.2.2.81 Enhanced PCH Support Indicator..............................................................................................................623 9.2.2.82 Priority Queue Information for Enhanced FACH/PCH.............................................................................623 9.2.2.83 SixteenQAM UL Information....................................................................................................................623 9.2.2.84 SixteenQAM UL Information To Modify..................................................................................................623 9.2.2.85 F-DPCH Slot Format..................................................................................................................................623 9.2.2.86 F-DPCH Slot Format Support Request......................................................................................................623 9.2.2.87 Max UE DTX Cycle ..................................................................................................................................623 9.2.2.88 Enhanced PCH Capability..........................................................................................................................623 9.2.2.89 MAC-ehs Reset Timer...............................................................................................................................623 9.2.2.90 SixteenQAM UL Operation Indicator........................................................................................................623 9.2.2.91 E-TFCI Boost Information.........................................................................................................................624 9.2.2.92 Common E-DCH Support Indicator...........................................................................................................624 9.2.2.93 Common E-DCH MAC-d Flow Specific Information...............................................................................624 9.2.2.94 Counting Information.................................................................................................................................624 9.2.2.95 Transmission Mode Information................................................................................................................625 9.2.2.96 MBMS Neighbouring Cell Information.....................................................................................................625 9.2.2.97 RLC Sequence Number..............................................................................................................................626 9.2.2.98 Time Stamp................................................................................................................................................626 9.2.2.99 HS-DSCH Preconfiguration Info...............................................................................................................626 9.2.2.100 HS-DSCH Preconfiguration Setup...........................................................................................................628 9.2.2.101 Secondary Serving Cell List.....................................................................................................................630 9.2.2.102 Minimum Reduced E-DPDCH Gain Factor............................................................................................630 9.2.2.103 UE Support Indicator Extension..............................................................................................................630 9.2.2.104 Power Offset For S-CPICH for MIMO....................................................................................................631 9.2.2.105 Power Offset For S-CPICH for MIMO Request Indicator......................................................................631 9.2.2.106 Single Stream MIMO Activation Indicator..............................................................................................631 9.2.2.107 Single Stream MIMO Mode Indicator.....................................................................................................632 9.2.2.108 HS-DSCH MAC-ehs Format...................................................................................................................632 9.2.2.109 Activation Information.............................................................................................................................632 9.2.2.110 Additional E-DCH FDD Setup Information............................................................................................632 9.2.2.111 Additional E-DCH Configuration Change Information...........................................................................633 9.2.2.112 Additional E-DCH FDD Information......................................................................................................633 9.2.2.113 Multicell E-DCH Transport Bearer Mode...............................................................................................634 9.2.2.114 Multicell E-DCH Information..................................................................................................................634 9.2.2.115 Additional E-DCH RL Specific Information To Setup............................................................................634 9.2.2.116 Additional E-DCH RL Specific Information To Add..............................................................................635 9.2.2.117 Additional E-DCH RL Specific Information To Modify.........................................................................635 9.2.2.118 Additional E-DCH MAC-d Flow Specific Information...........................................................................636 9.2.2.119 Multicell E-DCH RL Specific Information..............................................................................................636 9.2.2.120 Additional E-DCH FDD Information Response......................................................................................636 9.2.2.121 Additional Modified E-DCH FDD Information Response......................................................................637 9.2.2.122 Additional E-DCH FDD Update Information..........................................................................................638 9.2.2.123 Cell Capability Container Extension FDD...............................................................................................639 9.2.2.124 Non-Serving RL Preconfiguration Setup.................................................................................................642 9.2.2.125 Non-Serving RL Preconfiguration Info...................................................................................................642 9.2.2.126 Void 644 9.2.2.127 Usefulness of Battery Optimization.........................................................................................................644 9.2.2.128 M1 Report................................................................................................................................................644 9.2.2.129 Support of Dynamic DTXDRX Related HS-SCCH Order......................................................................644 9.2.2.130 UL CLTD Information Reconf................................................................................................................644

3GPP

Release 11

19

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.131 UL CLTD Information.............................................................................................................................645 9.2.2.132 UL CLTD Information To Modify..........................................................................................................645 9.2.2.133 UL CLTD Information Removal.............................................................................................................645 9.2.2.134 UL CLTD State Update Information.......................................................................................................646 9.2.2.135 F-TPICH Slot Format...............................................................................................................................646 9.2.2.136 F-TPICH Offset........................................................................................................................................646 9.2.2.137 S-DPCCH Power Offset Infomation........................................................................................................646 9.2.2.138 UL CLTD Activation Information...........................................................................................................646 9.2.2.139 F-TPICH Information...............................................................................................................................646 9.2.2.140 F-TPICH Information To Modify............................................................................................................647 9.2.2.141 F-TPICH Information Removal...............................................................................................................647 9.2.2.142 F-TPICH Information Reconf..................................................................................................................647 9.2.3 TDD Specific Parameters................................................................................................................................647 9.2.3.a Alpha Value..................................................................................................................................................647 9.2.3.A Block STTD Indicator.................................................................................................................................648 9.2.3.1 Burst Type....................................................................................................................................................648 9.2.3.1a Cell Capability Container TDD..................................................................................................................648 9.2.3.1b Cell Capability Container TDD LCR.........................................................................................................648 9.2.3.2 CCTrCH ID..................................................................................................................................................649 9.2.3.2A DCH TDD Information.............................................................................................................................649 9.2.3.2B DCH TDD Information Response.............................................................................................................650 9.2.3.2C DL Timeslot Information..........................................................................................................................650 9.2.3.2D DL Time Slot ISCP Info............................................................................................................................651 9.2.3.2E DL Timeslot Information LCR..................................................................................................................651 9.2.3.2F DL Time Slot ISCP Info LCR...................................................................................................................652 9.2.3.3 DPCH ID 652 9.2.3.3a DSCH TDD Information............................................................................................................................652 9.2.3.3aa HS-DSCH TDD Information....................................................................................................................653 9.2.3.3ab HS-DSCH TDD Information Response...................................................................................................655 9.2.3.3ac HS-DSCH TDD Update Information ......................................................................................................659 9.2.3.3ad HS-SICH ID.............................................................................................................................................659 9.2.3.3ae DSCH ID..................................................................................................................................................659 9.2.3.3af DSCH Initial Window Size.......................................................................................................................660 9.2.3.3ag DSCH Flow Control Information.............................................................................................................660 9.2.3.3ah DSCH-RNTI.............................................................................................................................................660 9.2.3.3ai TSN-Length...............................................................................................................................................660 9.2.3.3A Maximum Number of Timeslots...............................................................................................................661 9.2.3.3B Maximum Number of UL Physical Channels per Timeslot......................................................................661 9.2.3.3C Maximum Number of DL Physical Channels...........................................................................................661 9.2.3.3D Maximum Number of DL Physical Channels per Timeslot......................................................................661 9.2.3.4 Midamble Shift And Burst Type..................................................................................................................661 9.2.3.4A Minimum Spreading Factor......................................................................................................................662 9.2.3.4B IPDL TDD parameters..............................................................................................................................662 9.2.3.4Bb IPDL TDD parameters LCR....................................................................................................................663 9.2.3.4C Midamble shift LCR..................................................................................................................................663 9.2.3.4D Neighbouring TDD Cell Information LCR...............................................................................................664 9.2.3.5 Primary CCPCH RSCP................................................................................................................................664 9.2.3.5a Primary CCPCH RSCP Delta.....................................................................................................................664 9.2.3.5A PRACH Midamble....................................................................................................................................664 9.2.3.5B RB Identity................................................................................................................................................664 9.2.3.6 Repetition Length.........................................................................................................................................664 9.2.3.7 Repetition Period..........................................................................................................................................665 9.2.3.7A Rx Timing Deviation.................................................................................................................................665 9.2.3.7B Secondary CCPCH Info TDD...................................................................................................................665 9.2.3.7C Secondary CCPCH TDD Code Information.............................................................................................666 9.2.3.7D Special Burst Scheduling..........................................................................................................................666 9.2.3.7E Synchronisation Configuration..................................................................................................................666 9.2.3.7F Secondary CCPCH Info TDD LCR...........................................................................................................666 9.2.3.7G Secondary CCPCH TDD Code Information LCR....................................................................................667 9.2.3.7H Support of 8PSK........................................................................................................................................667 9.2.3.7I TDD ACK NACK Power Offset................................................................................................................668

3GPP

Release 11

20

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.8 TDD Channelisation Code...........................................................................................................................668 9.2.3.8a TDD Channelisation Code LCR.................................................................................................................668 9.2.3.8A TDD DPCH Offset....................................................................................................................................668 9.2.3.8B TDD DCHs To Modify.............................................................................................................................669 9.2.3.8C TDD DL Code Information.......................................................................................................................669 9.2.3.8D TDD DL Code Information LCR..............................................................................................................670 9.2.3.8E TDD DL DPCH Time Slot Format LCR...................................................................................................670 9.2.3.9 TDD Physical Channel Offset......................................................................................................................670 9.2.3.10 TDD TPC Downlink Step Size..................................................................................................................670 9.2.3.10a TDD TPC Uplink Step Size.....................................................................................................................671 9.2.3.10A TDD UL Code Information.....................................................................................................................671 9.2.3.10B TDD UL Code Information LCR............................................................................................................671 9.2.3.10C TDD UL DPCH Time Slot Format LCR.................................................................................................671 9.2.3.10D 1.28 Mcps TDD uplink physical channel capability...............................................................................672 9.2.3.11 TFCI Coding..............................................................................................................................................672 9.2.3.12 DL Timeslot ISCP......................................................................................................................................672 9.2.3.12a Time Slot LCR.........................................................................................................................................672 9.2.3.12A Timing Advance Applied........................................................................................................................672 9.2.3.13 Transport Format Management..................................................................................................................673 9.2.3.13A UL Timeslot ISCP...................................................................................................................................673 9.2.3.13B UL PhysCH SF Variation........................................................................................................................673 9.2.3.13C UL Timeslot Information........................................................................................................................673 9.2.3.13D UL Time Slot ISCP Info..........................................................................................................................673 9.2.3.13E TSTD Indicator........................................................................................................................................674 9.2.3.13F TSTD Support Indicator..........................................................................................................................674 9.2.3.13Fa UE Measurement Hysteresis Time.........................................................................................................674 9.2.3.13Fb UE Measurement Parameter Modification Allowed..............................................................................674 9.2.3.13Fc UE Measurement Report Characteristics...............................................................................................675 9.2.3.13Fd UE Measurement Threshold..................................................................................................................675 9.2.3.13Fe UE Measurement Timeslot Information HCR.......................................................................................676 9.2.3.13Ff UE Measurement Timeslot Information LCR........................................................................................676 9.2.3.13Fg UE Measurement Time to Trigger.........................................................................................................676 9.2.3.13Fh UE Measurement Type..........................................................................................................................677 9.2.3.13Fi UE Measurement Value..........................................................................................................................677 9.2.3.13Fj UE Measurement Value Information......................................................................................................678 9.2.3.13G UL Timeslot Information LCR...............................................................................................................678 9.2.3.13H UL Time Slot ISCP Info LCR.................................................................................................................678 9.2.3.13I Uplink Synchronisation Frequency..........................................................................................................679 9.2.3.13J Uplink Synchronisation Step Size............................................................................................................679 9.2.3.13K Uplink Timing Advance Control LCR....................................................................................................679 9.2.3.13L USCH ID.................................................................................................................................................680 9.2.3.14 USCH Information.....................................................................................................................................680 9.2.3.16 Support of PLCCH.....................................................................................................................................681 9.2.3.17 PLCCH Information...................................................................................................................................681 9.2.3.18 PLCCH Sequence Number........................................................................................................................682 9.2.3.19 Minimum Spreading Factor 7.68Mcps......................................................................................................682 9.2.3.20 Maximum Number of DL Physical Channels 7.68Mcps...........................................................................682 9.2.3.21 Maximum Number of DL Physical Channels per Timeslot 7.68Mcps......................................................682 9.2.3.22 Secondary CCPCH Info 7.68Mcps TDD...................................................................................................682 9.2.3.23 Midamble Shift And Burst Type 7.68Mcps...............................................................................................683 9.2.3.24 Secondary CCPCH TDD Code Information 7.68Mcps.............................................................................684 9.2.3.25 TDD Channelisation Code 7.68Mcps........................................................................................................684 9.2.3.26 UL Timeslot Information 7.68Mcps..........................................................................................................685 9.2.3.27 TDD UL Code Information 7.68Mcps.......................................................................................................685 9.2.3.28 DL Timeslot Information 7.68Mcps..........................................................................................................685 9.2.3.29 TDD DL Code Information 7.68Mcps.......................................................................................................686 9.2.3.30 Rx Timing Deviation 7.68Mcps.................................................................................................................686 9.2.3.31 Cell Capability Container 7.68 Mcps TDD................................................................................................686 9.2.3.32 Neighbouring TDD Cell Measurement Information 7.68Mcps.................................................................687 9.2.3.33 UE Measurement Timeslot Information 7.68Mcps...................................................................................687 9.2.3.34 DPCH ID 7.68Mcps...................................................................................................................................688

3GPP

Release 11

21

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.35 Rx Timing Deviation 3.84Mcps Extended.................................................................................................688 9.2.3.36 E-PUCH Information.................................................................................................................................688 9.2.3.36a E-PUCH Information LCR.......................................................................................................................688 9.2.3.37 E-TFCS Information TDD.........................................................................................................................689 9.2.3.38 E-DCH MAC-d Flows Information TDD..................................................................................................690 9.2.3.39 E-DCH Non-scheduled Grant Information TDD.......................................................................................691 9.2.3.39a E-DCH Non-scheduled Grant Information LCR TDD............................................................................692 9.2.3.40 E-DCH TDD Information..........................................................................................................................692 9.2.3.40a E-DCH TDD Information LCR................................................................................................................692 9.2.3.41 E-DCH TDD Information Response..........................................................................................................694 9.2.3.41a E-DCH TDD Information Response 1.28Mcps.......................................................................................694 9.2.3.42 E-DCH TDD Information to Modify.........................................................................................................695 9.2.3.43 E-DCH Grant Type....................................................................................................................................696 9.2.3.44 Timeslot Resource Related Information....................................................................................................697 9.2.3.44a Timeslot Resource Related Information LCR..........................................................................................697 9.2.3.45 Power Resource Related Information........................................................................................................697 9.2.3.46 E-PUCH Offset..........................................................................................................................................697 9.2.3.47 E-DCH TDD Maximum Bitrate.................................................................................................................697 9.2.3.48 E-HICH Time Offset..................................................................................................................................697 9.2.3.48a E-HICH Time Offset LCR.......................................................................................................................698 9.2.3.49 E-DCH HARQ Power Offset TDD............................................................................................................698 9.2.3.49a E-DCH MAC-d Flow Retransmission Timer...........................................................................................698 9.2.3.50 E-DCH Non-scheduled Grant Information 7.68Mcps TDD......................................................................698 9.2.3.51 E-DCH TDD Information 7.68Mcps.........................................................................................................698 9.2.3.52 E-DCH TDD Information Response 7.68Mcps.........................................................................................699 9.2.3.53 E-DCH TDD Maximum Bitrate 7.68Mcps................................................................................................699 9.2.3.54 E-DCH Physical Layer Category LCR......................................................................................................700 9.2.3.54A Extended E-DCH Physical layer Category LCR.....................................................................................700 9.2.3.54B Multi-Carrier E-DCH Physical Layer Category LCR.............................................................................700 9.2.3.55 UpPCH Information LCR..........................................................................................................................700 9.2.3.56 UpPCH Position LCR................................................................................................................................700 9.2.3.57 Common E-DCH MAC-d Flow ID............................................................................................................700 9.2.3.58 Common E-DCH MAC-d Flow Specific Information LCR......................................................................701 9.2.3.59 MAC-es Maximum Bit Rate LCR.............................................................................................................701 9.2.3.60 Idle Interval Information............................................................................................................................701 9.2.3.61 Continuous Packet Connectivity DRX Information LCR..........................................................................702 9.2.3.62 Continuous Packet Connectivity DRX Information To Modify LCR.......................................................702 9.2.3.63 Continuous Packet Connectivity DRX Information Response LCR.........................................................703 9.2.3.64 HS-DSCH Semi-Persistent scheduling Information LCR.........................................................................704 9.2.3.65 HS-DSCH Semi-Persistent scheduling Information to modify LCR.........................................................705 9.2.3.66 E-DCH Semi-Persistent scheduling Information LCR..............................................................................706 9.2.3.67 E-DCH Semi-Persistent scheduling Information to modify LCR..............................................................707 9.2.3.68 HS-DSCH Semi-Persistent scheduling Information Response LCR.........................................................708 9.2.3.69 E-DCH Semi-Persistent scheduling Information Response LCR..............................................................709 9.2.3.70 HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR............................................................710 9.2.3.71 E-DCH Semi-Persistent scheduling Deactivate Indicator LCR.................................................................710 9.2.3.72 HS-SICH Reference Signal Information....................................................................................................710 9.2.3.73 Cell Portion LCR ID .................................................................................................................................710 9.2.3.74 TS0 HS-PDSCH Indication LCR...............................................................................................................711 9.2.3.75 DCH Measurement Occasion Information.................................................................................................711 9.2.3.76 DCH Measurement Type Indicator............................................................................................................712 9.2.3.77 Multi-Carrier E-DCH Information LCR....................................................................................................713 9.2.3.78 Multi-Carrier E-DCH Information Response LCR....................................................................................714 9.2.3.79 Multi-Carrier E-DCH Transport Bearer Mode LCR..................................................................................714 9.2.3.80 Cell Capability Container Extension TDD LCR........................................................................................714 9.2.3.81 MU-MIMO Information.............................................................................................................................715 9.2.3.82 MU-MIMO Indicator.................................................................................................................................716 9.2.3.83 M2 Report..................................................................................................................................................716 9.2.3.84 UE RF Band Capability LCR.....................................................................................................................716 9.3 Message and Information Element Abstract Syntax (with ASN.1)...................................................................717 9.3.0 General 717

3GPP

Release 11

22

3GPP TS 25.423 V11.2.0 (2012-06)

9.3.1 Usage of Private Message Mechanism for Non-standard Use........................................................................717 9.3.2 Elementary Procedure Definitions..................................................................................................................717 9.3.3 PDU Definitions..............................................................................................................................................733 9.3.4 Information Element Definitions....................................................................................................................911 9.3.5 Common Definitions.....................................................................................................................................1126 9.3.6 Constant Definitions......................................................................................................................................1127 9.3.7 Container Definitions....................................................................................................................................1146 9.4 Message Transfer Syntax.................................................................................................................................1151 9.5 Timers..............................................................................................................................................................1151

10 Handling of Unknown, Unforeseen and Erroneous Protocol Data.................................................1151

10.1 General...........................................................................................................................................................1151 10.2 Transfer Syntax Error.....................................................................................................................................1151 10.3 Abstract Syntax Error.....................................................................................................................................1152 10.3.1 General........................................................................................................................................................1152 10.3.2 Criticality Information................................................................................................................................1152 10.3.3 Presence Information..................................................................................................................................1153 10.3.4 Not Comprehended IE/IE Group................................................................................................................1153 10.3.4.1 Procedure ID............................................................................................................................................1153 10.3.4.1A Type of Message...................................................................................................................................1153 10.3.4.2 IEs Other Than the Procedure ID and Type of Message.........................................................................1153 10.3.5 Missing IE or IE Group...............................................................................................................................1154 10.3.6 IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present.....1156 10.4 Logical Error..................................................................................................................................................1156 10.5 Exceptions......................................................................................................................................................1157

Annex A (normative): Allocation and Pre-emption of Radio Links in the DRNS..............1158 A.1 Deriving Allocation Information for a Radio Link.......................................................................1158
A.1.1 Establishment of a New Radio Link............................................................................................................1158 A.1.2 Modification of an Existing Radio Link......................................................................................................1158

A.2 Deriving Retention Information for a Radio Link........................................................................1159 A.3 The Allocation/Retention Process................................................................................................1159 A.4 The Pre-emption Process..............................................................................................................1160 Annex B (informative): Measurement Reporting...................................................................1160 Annex C (informative): Guidelines for Usage of the Criticality Diagnostics IE...................1165
C.1 EXAMPLE MESSAGE Layout......................................................................................................................1165 C.2 Example on a Received EXAMPLE MESSAGE............................................................................................1166 C.3 Content of Criticality Diagnostics...................................................................................................................1167 C.3.1 Example 1.....................................................................................................................................................1167 C.3.2 Example 2.....................................................................................................................................................1168 C.3.3 Example 3.....................................................................................................................................................1169 C.3.4 Example 4.....................................................................................................................................................1170 C.3.5 Example 5.....................................................................................................................................................1171 C.4 ASN.1 of EXAMPLE MESSAGE..................................................................................................................1171

Annex D (normative): DRNS Behaviour at SRNC or RNSAP Signalling Bearer Failure.1174

D.1 Detection of SRNC or RNSAP Signalling Bearer/Connection Failure..........................................................1174 D.1.1 Termination of all UE Contexts Related to a Specific SRNC......................................................................1174 D.1.2 Termination of Specific UE Context............................................................................................................1174 D.2 DRNC Actions at UE Context Termination....................................................................................................1174

3GPP

Release 11

23

3GPP TS 25.423 V11.2.0 (2012-06)

Annex E (informative): Change History..................................................................................1175

3GPP

Release 11

24

3GPP TS 25.423 V11.2.0 (2012-06)

Foreword
This Technical Specification (TS) 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. Ythe 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 11

25

3GPP TS 25.423 V11.2.0 (2012-06)

Scope

The present document specifies the radio network layer signalling procedures of the control plane between RNCs in UTRAN, between RNC in UTRAN and BSS in GERAN Iu mode and between BSSs in GERAN Iu mode.

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] 3GPP TS 23.003: Numbering, addressing and identification. 3GPP TS 25.413: UTRAN Iu Interface RANAP Signalling. 3GPP TS 25.426: UTRAN Iur and Iub Interface Data Transport & Transport Layer Signalling for DCH Data Streams. 3GPP TS 25.427: UTRAN Iur and Iub Interface User Plane Protocols for DCH Data Streams. 3GPP TS 25.435: UTRAN Iub interface User Plane Protocols for Common Transport Channel Data Streams. 3GPP TS 25.104: UTRA (BS) FDD; Radio transmission and Reception. 3GPP TS 25.105: UTRA (BS) TDD; Radio Transmission and Reception. 3GPP TS 25.211: Physical Channels and Mapping of Transport Channels onto Physical Channels (FDD). 3GPP TS 25.212: Multiplexing and Channel Coding (FDD).

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

[10] 3GPP TS 25.214: Physical Layer Procedures (FDD). [11] 3GPP TS 25.215: Physical Layer Measurements (FDD). [12] 3GPP TS 25.221: Physical Channels and Mapping of Transport Channels onto Physical Channels (TDD). [13] 3GPP TS 25.223: Spreading and Modulation (TDD). [14] 3GPP TS 25.225: Physical Layer Measurements (TDD). [15] 3GPP TS 25.304: UE Procedures in Idle Mode [16] 3GPP TS 25.331: RRC Protocol Specification. [17] 3GPP TS 25.402: Synchronisation in UTRAN, Stage 2. [18] ITU-T Recommendation X.680 (2002-07): Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation. [19] ITU-T Recommendation X.681 (2002-07): Information technology Abstract Syntax Notation One (ASN.1): Information object specification. [20] ITU-T Recommendation X.691 (2002-07): Information technology ASN.1 encoding rules Specification of Packed Encoding Rules (PER).

3GPP

Release 11

26

3GPP TS 25.423 V11.2.0 (2012-06)

[21] 3GPP TS 25.213: Spreading and modulation (FDD). [22] 3GPP TS 25.224: Physical Layer Procedures (TDD). [23] 3GPP TS 25.133: Requirements for support of Radio Resource management (FDD). [24] 3GPP TS 25.123: Requirements for support of Radio Resource management (TDD). [25] 3GPP TS 23.032: Universal Graphical Area Description (GAD). [26] 3GPP TS 25.302: Services Provided by the Physical Layer. [27] 3GPP TS 25.213: Spreading and modulation (FDD). [28] 3GPP TR 25.921 (version.7.0.0): Guidelines and Principles for Protocol Description and Error Handling. [29] Void [30] ICD-GPS-200: Navstar GPS Space Segment/Navigation User Interface. [31] RTCM-SC104: RTCM Recommended Standards for Differential GNSS Service (v.2.2). [32] 3GPP TS 25.425: UTRAN Iur and Iub Interface User Plane Protocols for Common Transport Channel data streams . [33] IETF RFC 2460 (1998-12): Internet Protocol, Version 6 (Ipv6) Specification. [34] IETF RFC 768 (1980-08): User Datagram Protocol. [35] 3GPP TS 25.424: UTRAN Iur Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams . [36] 3GPP TS 44.118: Mobile radio interface layer 3 specification; Radio Resource Control (RRC) Protocol Iu mode. [37] Void [38] 3GPP TS 48.008: Mobile-services Switching Centre Base Station System (MSC BSS) interface; Layer 3 specification. [39] 3GPP TS 43.051: GSM/EGDE Radio Access Network; Overall description Stage 2. [40] 3GPP TS 25.401: UTRAN Overall Description. [41] 3GPP TS 25.321: MAC protocol specification. [42] 3GPP TS 25.306: UE Radio Access capabilities. [43] 3GPP TS 25.101: User Equipment (UE) radio transmission and reception (FDD). [44] IETF RFC 2474 (1998-12): Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers. [45] IETF RFC 2475 (1998-12): An Architecture for Differentiated Services. [46] 3GPP TS 25.222: Multiplexing and Channel Coding (TDD). [47] 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. [48] 3GPP TS 32.421: Subscriber and equipment trace: Trace concepts and requirements. [49] 3GPP TS 32.422: Subscriber and equipment trace: Trace control and Configuration Management. [50] 3GPP TS 25.346: Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (Stage-2) . [51] 3GPP TS 23.246: Multimedia Broadcast Multicast Service; Architecture and Functional Description.

3GPP

Release 11

27

3GPP TS 25.423 V11.2.0 (2012-06)

[52] 3GPP TS 25.319: Enhanced Uplink; Overall description; Stage 2. [53] Galileo OS Signal in Space ICD (OS SIS ICD), Draft 0, Galileo Joint Undertaking, May 23rd, 2006. [54] 3GPP TS 23.251: Network Sharing: Architecture and functional description. [55] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. [56] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. [57] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008. [58] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. [59] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008. [60] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002. [61] 3GPP TS 36.401: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture Description. [62] 3GPP TS 36.104: Base Station (BS) radio transmission and reception . [63] 3GPP TS 25.308: High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2. [64] 3GPP TS 36.133: Requirements for support of radio resource management. [65] 3GPP TS 23.195: Provision of UE Specific Behaviour Information to Network Entities. [66] 3GPP TS 24.008: Mobile radio interface Layer 3 specification; Core network protocols; Stage 3. [67] 3GPP TS 44.108: Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol. [68] 3GPP TS 25.422: UTRAN Iur interface signalling transport. [69] 3GPP TS 45.005: Technical Specification Group GSM/EDGE Radio Access Network; Radio transmission and reception

Definitions, Symbols and Abbreviations

3.1 Definitions

For the purposes of the present document, the following terms and definitions apply: Elementary Procedure: RNSAP protocol consists of Elementary Procedures (Eps). An Elementary Procedure is a unit of interaction between two RNCs. An EP consists of an initiating message and possibly a response message. Two kinds of Eps are used: Class 1: Elementary Procedures with response (success or failure); Class 2: Elementary Procedures without response.

For Class 1 Eps, the types of responses can be as follows: Successful - A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response. Unsuccessful - A signalling message explicitly indicates that the EP failed. Class 2 Eps are considered always successful.

3GPP

Release 11

28

3GPP TS 25.423 V11.2.0 (2012-06)

Prepared Reconfiguration: A Prepared Reconfiguration exists when the Synchronised Radio Link Reconfiguration Preparation procedure has been completed successfully. The Prepared Reconfiguration does not exist anymore only after either of the procedures Synchronised Radio Link Reconfiguration Commit or Synchronised Radio Link Reconfiguration Cancellation has been completed. In particular, the Prepared Reconfiguration still exists if the object (e.g. Radio Link) concerned by the Synchronised Radio Link Reconfiguration (e.g. in the case of an HS-DSCH Setup) is removed, but the UE Context still exists. UE Context: The UE Context contains the necessary information for the DRNC/DBSS to communicate with a specific UE. The UE Context is created by the Radio Link Setup procedure or by the Uplink Signalling Transfer procedure when the UE makes its first access in a cell controlled by the DRNS/DBSS or by Enhanced Relocation procedure when the procedure is the first dedicated RNSAP procedure for the UE. The UE Context is deleted by the Radio Link Deletion procedure, by the Common Transport Channel Resources Release procedure, or by the Downlink Signalling Transfer procedure when neither any Radio Links nor any common transport channels are established towards the concerned UE. The UE Context is identified by the SCCP Connection for messages using connection oriented mode of the signalling bearer and the D-RNTI for messages using connectionless mode of the signalling bearer, unless specified otherwise in the procedure text. Distant RNC Context: The Distant RNC context is created by the first Common Measurement Initiation Procedure or Information Exchange Initiation Procedure initiated by one RNC/BSS and requested from another RNC/BSS. The Distant RNC Context is deleted after the Common Measurement Termination, the Common Measurement Failure, the Information Exchange Termination or the Information Exchange Failure procedure when there is no more Common Measurement and no more Information to be provided by the requested RNC/BSS to the requesting RNC/BSS. The Distant RNC Context is identified by a connection oriented signalling bearer (See TS 25.422 [68]) as, for common measurements and information exchange, only the connection oriented mode of the signalling bearer is used. Signalling radio bearer 2: The signalling radio bearer 2 is used by the UE to access a GERAN cell in order to perform RRC procedures (TS 44.118 [36]). UE Link: see definition in TS 25.346 [50]. URA Link: see definition in TS 25.346 [50]. MBMS Bearer Service: see defintion in TS 23.246 [51]. MBMS session: see defintion in TS 25.346 [50]. MBMS session start: see defintion in TS 25.346 [50]. MBMS session stop: see defintion in TS 25.346 [50]. MBMS Selected Services: see defintion in TS 25.346 [50]. PUESBINE feature: as defined in TS 23.195 [65].

3.2 Symbols
Void.

3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply: A-GPS Assisted-GPS ALCAP Access Link Control Application Part APN Access Point Name ASN.1 Abstract Syntax Notation One BER Bit Error Rate BLER Block Error Rate BSS Base Station Subsystem CBSS Controlling BSS CCCH Common Control Channel CCPCH Common Control Physical Channel CCTrCH Coded Composite Transport Channel CFN Connection Frame Number

3GPP

Release 11

29

3GPP TS 25.423 V11.2.0 (2012-06)

C-ID Cell Identifier CM Compressed Mode CN Core Network CPICH Common Pilot Channel CRNC Controlling RNC CLTD Closed Loop Transmit Diversity DBSS Drift BSS C-RNTI Cell Radio Network Temporary Identifier CS Circuit Switched CTFC Calculated Transport Format Combination DCH Dedicated Channel DGANSS Differential GANSS DGPS Differential GPS DL Downlink DPC Downlink Power Control DPCCH Dedicated Physical Control Channel DPCH Dedicated Physical Channel DPDCH Dedicated Physical Data Channel DRNC Drift RNC DRNS Drift RNS D-RNTI Drift Radio Network Temporary Identifier DRXDiscontinuous Reception DSCH Downlink Shared Channel Ec Energy in single Code E-AGCH E-DCH Absolute Grant Channel E-DCH Enhanced UL DCH E-HICH E-DCH HARQ Acknowledgement Indicator Channel E-PUCH Enhanced Uplink Physical Channel (TDD only) E-RNTI E-DCH RNTI E-RUCCH E-DCH Random Access Uplink Control Channel (TDD only) E-TFCI E-DCH Transport Format Combination Indicator E-UCCH E-DCH Uplink Control Channel (TDD only) E-UTRA Evolved UTRA EDSCHPC Enhanced Downlink Shared Channel Power Control EGNOS European Geostationary Navigation Overlay Service EP Elementary Procedure FACH Forward Access Channel FDD Frequency Division Duplex F-DPCH Fractional DPCH FN Frame Number FP Frame Protocol F-TPICH Fractional Transmitted Precoding Indicator Channel GANSS Galileo and Additional Navigation Satellite Systems GERAN GSM EDGE Radio Access Network GA Geographical Area GAGAN GPS Aided Geo Augmented Navigation GAI Geographical Area Identifier GLONASS GLObalnaya Navigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) GNSS Global Navigation Satellite System GPS Global Positioning System GRAGERAN Registration Area GSMGlobal System Mobile GWCN Gateway Core Network HSDPA High Speed Downlink Packet Access HW Hardware IB Information Block ICD Interface Control Document ID Identity or Identifier IE Information Element IMSIInternational Mobile Subscriber Identity IP Internet Protocol IPDL Idle Period DownLink

3GPP

Release 11

30

3GPP TS 25.423 V11.2.0 (2012-06)

ISCPInterference Signal Code Power LAC Location Area Code LCR Low Chip Rate (1.28 Mcps) LCS Location Services MAC Medium Access Control MBMS Multimedia Broadcast Multicast Service MDT Minimization of Drive Tests MOCN Multi-Operator Core Network MRNC MBMS Master RNC MS Mobile Station MSAS Multi-functional Satellite Augmentation System NACC Network Assissted Cell Change NAS Non Access Stratum No Reference Noise NRT Non Real Time O&M Operation and Maintenance P(-)CCPCH Primary CCPCH PCH Paging Channel OTD Observed Time Difference P(-)CPICH Primary CPICH PCS Personal Communication Services PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PhCH Physical Channel PICH Paging Indication Channel PLCCH Physical Layer Common Control Channel Pos Position or Positioning PRACH Physical Random Access Channel PTP Point To Point PTM Point To Multipoint PS Packet Switched PUESBINE Provision of UE Specific Behaviour Information to Network Entities QE Quality Estimate QZSS Quasi-Zenith Satellite System RAC Routing Area Code RACH Random Access Channel RANRadio Access Network RANAP Radio Access Network Application Part RB Radio Bearer RL Radio Link RLC Radio Link Control RLS Radio Link Set RM Rate Matching RNC Radio Network Controller RNS Radio Network Subsystem RNSAP Radio Network Subsystem Application Part RNTI Radio Network Temporary Identifier RRC Radio Resource Control RT Real Time RSCP Received Signal Code Power SBAS Satellite Based Augmentation System SBSS Serving BSS Rx Receive or Reception Sat Satellite SCCP Signalling Connection Control Part S(-)CCPCH Secondary CCPCH SCH Synchronisation Channel SCTD Space Code Transmit Diversity S-DPCCH Secondary Dedicated Physical Control Channel SDU Service Data Unit SF System Frame

3GPP

Release 11

31

3GPP TS 25.423 V11.2.0 (2012-06)

SFN System Frame Number SHCCH Shared Control Channel SIR Signal-to-Interference Ratio SNA Shared Network Area SRB2 Signalling radio bearer 2 SRNC Serving RNC SRNS Serving RNS S-RNTI Serving Radio Network Temporary Identifier STTD Space Time Transmit Diversity TDD Time Division Duplex TF Transport Format TFCITransport Format Combination Indicator TFCS Transport Format Combination Set TFS Transport Format Set TGCFN Transmission Gap Connection Frame Number TMGI Temporary Mobile Group Identity ToAWE Time of Arrival Window Endpoint ToAWS Time of Arrival Window Startpoint TPC Transmit Power Control TrCH Transport Channel TS Time Slot TSG Technical Specification Group TSTD Time Switched Transmit Diversity TTI Transmission Time Interval TX Transmit or Transmission UARFCN UTRA Absolute Radio Frequency Channel Number UDP User Datagram Protocol UC-ID UTRAN Cell Identifier UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System URAUTRAN Registration Area U-RNTI UTRAN Radio Network Temporary Identifier USCH Uplink Shared Channel UTC Universal Coordinated Time UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WAAS Wide Area Augmentation System

General
4.1 Procedure Specification Principles

The principle for specifying the procedure logic is to specify the functional behaviour of the DRNC/CRNC exactly and completely. The SRNC functional behaviour is left unspecified. The Physical Channel Reconfiguration procedure, [TDD the UE Measurement Inititation, the UE Measurement Reporting, UE Measurement Termination, UE Measurement Failure,] and the Reset procedure are an exception from this principle. The following specification principles have been applied for the procedure text in subclause 8: The procedure text discriminates between: 1) Functionality which shall be executed The procedure text indicates that the receiving node shall perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
4.

Functionality which shall, if supported be executed

3GPP

Release 11

32

3GPP TS 25.423 V11.2.0 (2012-06)

The procedure text indicates that the receiving node shall, if supported, perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements for including Criticality Diagnostics IE, see section 10. For examples on how to use the Criticality Diagnostics IE, see Annex C.

4.2 Forwards and Backwards Compatibility

The forwards and backwards compatibility of the protocol is assured by a mechanism in which all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3 Source Signalling Address Handling

The sender of an RNSAP messages shall include the Source Signalling Address, i.e. the Signalling Address of the sending node.

4.4 Specification Notations

For the purposes of the present document, the following notations apply: [FDD] This tagging of a word indicates that the word preceding the tag [FDD] applies only to FDD. This tagging of a heading indicates that the heading preceding the tag [FDD] and the section following the heading applies only to FDD. This tagging of a word indicates that the word preceding the tag [TDD] applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag [TDD] and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a word indicates that the word preceding the tag [3.84Mcps TDD] applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag [3.84Mcps TDD] and the section following the heading applies only to 3.84Mcps TDD. This tagging of a word indicates that the word preceding the tag [1.28Mcps TDD] applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag [1.28Mcps TDD] and the section following the heading applies only to 1.28Mcps TDD. This tagging of a word indicates that the word preceding the tag [7.68Mcps TDD] applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag [7.68Mcps TDD] and the section following the heading applies only to 7.68Mcps TDD. This tagging indicates that the enclosed text following the [FDD applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. This tagging indicates that the enclosed text following the [TDD applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.

[TDD]

[3.84Mcps TDD]

[1.28Mcps TDD]

[7.68Mcps TDD]

[FDD - ]

[TDD - ]

[3.84Mcps TDD - ] This tagging indicates that the enclosed text following the [3.84Mcps TDD applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.

3GPP

Release 11

33

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD - ] This tagging indicates that the enclosed text following the [1.28Mcps TDD applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. [7.68Mcps TDD - ] This tagging indicates that the enclosed text following the [7.68Mcps TDD applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. Procedure When referring to an elementary procedure in the specification, the Procedure Name is written with the first letters in each word in upper case characters followed by the word procedure, e.g. Radio Link Setup procedure. When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word message, e.g. RADIO LINK SETUP REQUEST message.

Message

IE

When referring to an information element (IE) in the specification, the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation IE, e.g. Transport Format Set IE. When referring to the value of an information element (IE) in the specification, the Value is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. Abstract Syntax Error (Reject).

Value of an IE

RNSAP Services
5.1 RNSAP Procedure Modules

The Iur interface RNSAP procedures are divided into five modules as follows: 1. RNSAP Basic Mobility Procedures; 2. RNSAP Dedicated Procedures; 3. RNSAP Common Transport Channel Procedures; 4. RNSAP Global Procedures; 5. RNSAP MBMS Procedures. The Basic Mobility Procedures module contains procedures used to handle the mobility within UTRAN, within GERAN and between UTRAN and GERAN. The Dedicated Procedures module contains procedures that are used to handle DCHs, [FDD F-DPCH,] [TDD DSCHs, USCHs], HS-DSCH and E-DCH between two RNSs. If procedures from this module are not used in a specific Iur, then the usage of DCH, [FDD F-DPCH,] [TDD DSCH, USCH,] HS-DSCH and E-DCH traffic between corresponding RNSs is not possible. The Common Transport Channel Procedures module contains procedures that are used to control common transport channel data streams (excluding the DSCH, HS-DSCH and USCH) over Iur interface. The Global Procedures module contains procedures that are not related to a specific UE. The procedures in this module are in contrast to the above modules involving two peer CRNCs/CBSSs. The MBMS Procedures module contains procedures that are specific to MBMS and used for cases that cannot be handled by other modules.

5.2 Parallel Transactions

Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer shall have a maximum of one ongoing RNSAP Dedicated procedure related to a certain UE.

3GPP

Release 11

34

3GPP TS 25.423 V11.2.0 (2012-06)

Services Expected from Signalling Transport

1. Connection oriented data transfer service. This service is supported by a signalling connection between two RNCs. It shall be possible to dynamically establish and release signalling connections based on the need. Each active UE shall have its own signalling connection. The signalling connection shall provide in sequence delivery of RNSAP messages. RNSAP shall be notified if the signalling connection breaks. 2. Connectionless data transfer service. RNSAP shall be notified in case a RNSAP message did not reach the intended peer RNSAP entity.

The signalling transport shall provide two different service modes for the RNSAP.

7
-

Functions of RNSAP
Radio Link Management. This function allows the SRNC to manage radio links using dedicated resources in a DRNS; Physical Channel Reconfiguration. This function allows the DRNC to reallocate the physical channel resources for a Radio Link; Radio Link Supervision. This function allows the DRNC to report failures and restorations of a Radio Link; Compressed Mode Control [FDD]. This function allows the SRNC to control the usage of compressed mode within a DRNS; Measurements on Dedicated Resources. This function allows the SRNC to initiate measurements on dedicated resources in the DRNS. The function also allows the DRNC to report the result of the measurements; DL Power Drifting Correction [FDD]. This function allows the SRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links; DCH Rate Control. This function allows the DRNC to limit the rate of each DCH configured for the Radio Link(s) of a UE in order to avoid congestion situations in a cell; CCCH Signalling Transfer. This function allows the SRNC and DRNC to pass information between the UE and the SRNC on a CCCH controlled by the DRNS; GERAN Signalling Transfer. This function allows the SBSS and DBSS, the SRNC and DBSS or the SBSS and DRNC to pass information between the UE/MS and the SRNC/SBSS on an SRB2/CCCH controlled by the DBSS/DRNC; Paging. This function allows the SRNC/SBSS to page a UE in a URA/GRA or a cell in the DRNS; Common Transport Channel Resources Management. This function allows the SRNC to utilise Common Transport Channel Resources within the DRNS; Relocation Execution. This function allows the SRNC/SBSS to finalise a Relocation previously prepared via other interfaces; Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined. DL Power Timeslot Correction [TDD]. This function enables the DRNS to apply an individual offset to the transmission power in each timeslot according to the downlink interference level at the UE. Measurements on Common Resources. This function allows an RNC/BSS to request from another RNC/BSS to initiate measurements on Common Resources. The function also allows the requested RNC/BSS to report the result of the measurements. Information Exchange. This function allows an RNC to request from another RNC the transfer of information. The function also allows the requested RNC to report the requested information.

The RNSAP protocol provides the following functions:

3GPP

Release 11 -

35

3GPP TS 25.423 V11.2.0 (2012-06)

Resetting the Iur. This function is used to completely or partly reset the Iur interface. UE Measurement Forwarding[TDD]. This function allows the DRNC to request and receive UE measurements from the SRNC. Tracing. This function allows the SRNC to activate or deactivate trace in a DRNC. MDT function. This function allows the SRNC to enable the transfer of MDT measurements collected by the UE. MBMS UE Linking/De-linking. This function allows the SRNC to provide/update/remove the UE Link to/in/from the DRNC. MBMS URA Linking/De-linking. This function allows the SRNC to provide/update/remove the URA Link to/in/from the DRNC. MBMS Channel Type Indication. This function allows the DRNC to indicate to the SRNC the selected channel type for an MBMS bearer service within certain cells in the DRNS. MBMS Preferred Frequency Layer Indication. This function allows the DRNC to indicate to the SRNC the preferred frequency layer for an MBMS bearer service within certain cells in the DRNS. MBMS MCCH Information Control. This function allows an MRNC to distribute the MCCH Information to CRNC within the MBSFN cluster. Direct Information Transfer. This function allows an RNC to transfer information to another RNC. Relocating serving RNC. This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another. Exchanging information about the secondary UL frequency. This function allows the SRNC to transfer information about the secondary UL frequency to the DRNS and the DRNS to transfer information about the secondary UL frequency to SRNC in Dual-Cell E-DCH operation. Radio Resource Reserve Handover [1.28Mcps TDD]. This function allows the SRNC to request allocation of radio resources in the target BSS prior to the HANDOVER REQUEST message is received from the Core Network. Automatic Neighbour Relation Management: This function enables RNC to distribute ANR reports, configure ANR neighbour relations, and control the ANR report distribution.

The mapping between the above functions and RNSAP elementary procedures is shown in the Table 1.

3GPP

Release 11

36

3GPP TS 25.423 V11.2.0 (2012-06)

Table 1: Mapping between functions and RNSAP elementary procedures

3GPP

Release 11
Function Radio Link Management

37

3GPP TS 25.423 V11.2.0 (2012-06)

Elementary Procedure(s) a) Radio Link Setup b) Radio Link Addition c) Radio Link Deletion d) Unsynchronised Radio Link Reconfiguration e) Synchronised Radio Link Reconfiguration Preparation f) Synchronised Radio Link Reconfiguration Commit g) Synchronised Radio Link Reconfiguration Cancellation h) Radio Link Pre-emptioni) Radio Link Activation j) Radio Link Parameter Update Physical Channel Reconfiguration a) Radio Link Failure b) Radio Link Restoration a) Radio Link Setup b) Radio Link Addition c) Compressed Mode Command d) Unsynchronised Radio Link Reconfiguration e) Synchronised Radio Link Reconfiguration Preparation f) Synchronised Radio Link Reconfiguration Commit g) Synchronised Radio Link Reconfiguration Cancellation a) Dedicated Measurement Initiation b) Dedicated Measurement Reporting c) Dedicated Measurement Termination d) Dedicated Measurement Failure Downlink Power Control a) Radio Link Setup b) Radio Link Addition c) Unsynchronised Radio Link Reconfiguration d) Synchronised Radio Link Reconfiguration Preparation e) Radio Link Congestion a) Uplink Signalling Transfer b) Downlink Signalling Transfer a) GERAN Uplink Signalling Transfer b) Downlink Signalling Transfer Paging a) Common Transport Channel Resources Initiation b) Common Transport Channel Resources Release Relocation Commit Error Indication a) Common Measurement Initiation b) Common Measurement Reporting c) Common Measurement Termination d) Common Measurement Failure a) Information Exchange Initiation b) Information Reporting c) Information Exchange Termination d) Information Exchange Failure Downlink Power Timeslot Control Reset a) UE Measurement Initiation b) UE Measurement Reporting c) UE Measurement Termination d) UE Measurement Failure a) Iur Invoke Trace b) Iur Deactivate Trace

Physical Channel Reconfiguration Radio Link Supervision Compressed Mode Control [FDD]

Measurements on Dedicated Resources

DL Power Drifting Correction [FDD] DCH Rate Control

CCCH Signalling Transfer GERAN Signalling Transfer Paging Common Transport Channel Resources Management Relocation Execution Reporting of General Error Situations Measurements on Common Resources

Information Exchange

DL Power Timeslot Correction [TDD] Reset UE Measurement Forwarding[TDD]

Trace

3GPP

Release 11
Function MBMS UE Linking/De-linking

38

3GPP TS 25.423 V11.2.0 (2012-06)

Elementary Procedure(s) a) Common Transport Channel Resources Initiation b) Radio Link Setup c) Downlink Signalling Transfer d) MBMS Attach e) MBMS Detach a) Direct Information Transfer b) Uplink Signalling Transfer c) Radio Link Setup d) Radio Link Addition e) Common Transport Channel Resources Initiation a) Direct Information Transfer b) Radio Link Setup d) Radio Link Addition a) Downlink Signalling Transfer b) MBMS Attach c) MBMS Detach a) MBSFN MCCH Information a) Direct Information Transfer a) Enhanced Relocation b) Enhanced Relocation Cancel c) Enhanced Relocation Signalling Transfer d) Enhanced Relocation Release a) Secondary UL Frequency Reporting b) Secondary UL Frequency Update a) Enhanced Relocation Resource Allocation b) Enhanced Relocation Resource Release a) Direct Information Transfer b) Information Exchange Initiation c) Information Reporting d) Information Exchange Termination e) Information Exchange Failure f) Information Transfer Control

MBMS Channel Type Indication

MBMS Preferred Frequency Layer Indication MBMS URA Linking/De-linking MBMS MCCH Information Control Direct Information Transfer Relocating serving RNC

Exchanging information about the secondary UL frequency [FDD] Radio Resource Reserve Handover [1.28Mcps TDD] Automatic Neighbour Relation Management

7.1 RNSAP functions and elementary procedures for Iur-g.

The functions and RNSAP elementary procedures, which are applicable on the Iur-g interface are shown in the Table 1A. Table 1A: RNSAP elementary procedures applicable on the Iur-g interface
Function GERAN Signalling Transfer Paging Relocation Execution Reporting of General Error Situations Measurements on Common Resources Elementary Procedure(s) a) GERAN Uplink Signalling Transfer b) Downlink Signalling Transfer Paging Relocation Commit Error Indication a) Common Measurement Initiation b) Common Measurement Reporting c) Common Measurement Termination d) Common Measurement Failure a) Information Exchange Initiation b) Information Reporting c) Information Exchange Termination d) Information Exchange Failure a) Enhanced Relocation Resource Allocation b) Enhanced Relocation Resource Release

Information Exchange

Radio Resource Reserve Handover [1.28Mcps TDD]

NOTE:

In the connection with the functions related to the GERAN and UTRAN, the term RNC shall refer to RNC/BSS.

3GPP

Release 11

39

3GPP TS 25.423 V11.2.0 (2012-06)

RNSAP Procedures
8.1 Elementary Procedures

In the following tables, all Eps are divided into Class 1 and Class 2 Eps. Table 2: Class 1 Elementary Procedures
Elementary Procedure Radio Link Setup Radio Link Addition Radio Link Deletion Synchronised Radio Link Reconfiguration Preparation Unsynchronised Radio Link Reconfiguration Physical Channel Reconfiguration Dedicated Measurement Initiation Common Transport Channel Resources Initialisation Common Measurement Initiation Information Exchange Initiation Reset UE Measurement Initiation[TDD] Enhanced Relocation Enhanced Relocation Resource Allocation[1.28Mc ps TDD] Enhanced Relocation Resource Release[1.28Mcp s TDD] Initiating Message RADIO LINK SETUP REQUEST RADIO LINK ADDITION REQUEST RADIO LINK DELETION REQUEST RADIO LINK RECONFIGURATION PREPARE RADIO LINK RECONFIGURATION REQUEST PHYSICAL CHANNEL RECONFIGURATION REQUEST DEDICATED MEASUREMENT INITIATION REQUEST COMMON TRANSPORT CHANNEL RESOURCES REQUEST COMMON MEASUREMENT INITIATION REQUEST INFORMATION EXCHANGE INITIATION REQUEST RESET REQUEST UE MEASUREMENT INITIATION REQUEST ENHANCED RELOCATION REQUEST ENHANCED RELOCATION RESOURCE REQUEST ENHANCED RELOCATION RESOURCE RELEASE COMMAND Successful Outcome Response message RADIO LINK SETUP RESPONSE RADIO LINK ADDITION RESPONSE RADIO LINK DELETION RESPONSE RADIO LINK RECONFIGURATION READY RADIO LINK RECONFIGURATION RESPONSE PHYSICAL CHANNEL RECONFIGURATION COMMAND DEDICATED MEASUREMENT INITIATION RESPONSE COMMON TRANSPORT CHANNEL RESOURCES RESPONSE COMMON MEASUREMENT INITIATION RESPONSE INFORMATION EXCHANGE INITIATION RESPONSE RESET RESPONSE UE MEASUREMENT INITIATION RESPONSE ENHANCED RELOCATION RESPONSE ENHANCED RELOCATION RESOURCE RESPONSE ENHANCED RELOCATION RESOURCE RELEASE COMPLETE Unsuccessful Outcome Response message RADIO LINK SETUP FAILURE RADIO LINK ADDITION FAILURE

RADIO LINK RECONFIGURATION FAILURE RADIO LINK RECONFIGURATION FAILURE PHYSICAL CHANNEL RECONFIGURATION FAILURE DEDICATED MEASUREMENT INITIATION FAILURE COMMON TRANSPORT CHANNEL RESOURCES FAILURE COMMON MEASUREMENT INITIATION FAILURE INFORMATION EXCHANGE INITIATION FAILURE UE MEASUREMENT INITIATION FAILURE ENHANCED RELOCATION FAILURE ENHANCED RELOCATION RESOURCE FAILURE

3GPP

Release 11

40 Table 3: Class 2 Elementary Procedures

3GPP TS 25.423 V11.2.0 (2012-06)

Elementary Procedure Uplink Signalling Transfer GERAN Uplink Signalling Transfer Downlink Signalling Transfer Relocation Commit Paging Synchronised Radio Link Reconfiguration Commit Synchronised Radio Link Reconfiguration Cancellation Radio Link Failure Radio Link Restoration Dedicated Measurement Reporting Dedicated Measurement Termination Dedicated Measurement Failure Downlink Power Control [FDD] Compressed Mode Command [FDD] Common Transport Channel Resources Release Error Indication Downlink Power Timeslot Control [TDD] Radio Link Pre-emption Radio Link Congestion Common Measurement Reporting Common Measurement Termination Common Measurement Failure Information Reporting Information Exchange Termination Information Exchange Failure MBMS Attach MBMS Detach Radio Link Parameter Update UE Measurement Reporting [TDD] UE Measurement Termination [TDD] UE Measurement Failure [TDD] Iur Invoke Trace Iur Deactivate Trace Direct Information Transfer Enhanced Relocation Cancel Enhanced Relocation Signalling Transfer Enhanced Relocation Release MBSFN MCCH Information Secondary UL Frequency Reporting [FDD] Secondary UL Frequency Update[FDD] Information Transfer Control

Initiating Message UPLINK SIGNALLING TRANSFER INDICATION GERAN UPLINK SIGNALLING TRANSFER INDICATION DOWNLINK SIGNALLING TRANSFER REQUEST RELOCATION COMMIT PAGING REQUEST RADIO LINK RECONFIGURATION COMMIT RADIO LINK RECONFIGURATION CANCEL RADIO LINK FAILURE INDICATION RADIO LINK RESTORE INDICATION DEDICATED MEASUREMENT REPORT DEDICATED MEASUREMENT TERMINATION REQUEST DEDICATED MEASUREMENT FAILURE INDICATION DL POWER CONTROL REQUEST COMPRESSED MODE COMMAND COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST ERROR INDICATION DL POWER TIMESLOT CONTROL REQUEST RADIO LINK PREEMPTION REQUIRED INDICATION RADIO LINK CONGESTION INDICATION COMMON MEASUREMENT REPORT COMMON MEASUREMENT TERMINATION REQUEST COMMON MEASUREMENT FAILURE INDICATION INFORMATION REPORT INFORMATION EXCHANGE TERMINATION REQUEST INFORMATION EXCHANGE FAILURE INDICATION MBMS ATTACH COMMAND MBMS DETACH COMMAND RADIO LINK PARAMETER UPDATE INDICATION UE MEASUREMENT REPORT UE MEASUREMENT TERMINATION REQUEST UE MEASUREMENT FAILURE INDICATION IUR INVOKE TRACE IUR DEACTIVATE TRACE DIRECT INFORMATION TRANSFER ENHANCED RELOCATION CANCEL ENHANCD RELOCATION SIGNALLING TRANSFER ENHANCD RELOCATION RELEASE MBSFN MCCH INFORMATION SECONDARY UL FREQUENCY REPORT SECONDARY UL FREQUENCY UPDATE INDICATION INFORMATION TRANSFER CONTROL REQUEST

3GPP

Release 11

41

3GPP TS 25.423 V11.2.0 (2012-06)

8.2 Basic Mobility Procedures

8.2.1 Uplink Signalling Transfer
8.2.1.1 General
The procedure is used by the DRNC to forward a Uu message received on the CCCH to the SRNC. This procedure shall use the connectionless mode of the signalling bearer.

8.2.1.2

Successful Operation
DRNC
Uu message received from UE containing S-RNTI and SRNC ID as addressing information

SRNC Layer

UPLINK SIGNALLING TRANSFER INDICATION

Figure 1: Uplink Signalling Transfer procedure, Successful Operation When the DRNC receives an Uu message on the CCCH in which the UE addressing information is U-RNTI, i.e. SRNTI and SRNC-ID, DRNC shall send the UPLINK SIGNALLING TRANSFER INDICATION message to the SRNC identified by the SRNC-ID received from the UE. If at least one URA Identity is being broadcast in the cell where the Uu message was received (the accessed cell), the DRNC shall include a URA Identity for this cell in the URA ID IE, the Multiple URAs Indicator IE indicating whether or not multiple URA Identities are being broadcast in the accessed cell, and the RNC Identity of all other RNCs that are having at least one cell within the URA where the Uu message was received in the URA Information IE in the UPLINK SIGNALLING TRANSFER INDICATION message. The DRNC shall include in the message the C-RNTI that it allocates to identify the UE in the radio interface in the accessed cell. If there is no valid C-RNTI for the UE in the accessed cell, the DRNS shall allocate a new C-RNTI for the UE [FDD and in case Enhanced FACH operation is activated in the accessed cell the DRNC shall allocate the HSDSCH-RNTI to the UE and shall include the HS-DSCH-RNTI IE in the message. And in case Common E-DCH operation is activated in the accessed cell the DRNC shall include the E-RNTI received from Node B and shall include the E-RNTI IE in the message]. [1.28Mcps TDD and in case Enhanced FACH operation is activated in the accessed cell the DRNC shall allocate the HS-DSCH-RNTI to the UE and shall include the HS-DSCH-RNTI IE in the message and the DRNC shall include the E-RNTI received from Node B and shall include the E-RNTI IE in the message]. If the DRNS allocates a new C-RNTI it shall also release any C-RNTI previously allocated for the UE. If the DRNS has any RACH and/or FACH resources allocated for the UE identified by the U-RNTI in another cell than the accessed cell in which the Mac SDU sizes, flow control settings (including credits) and/or transport bearer are different from those in the old cell, then the DRNS shall not include the Common Transport Channel Resources Initialisation Not Required IE in the UPLINK SIGNALLING TRANSFER INDICATION message. In addition the DRNS shall release these RACH and/or FACH resources in old cell. If the DRNS has any RACH and/or FACH resources allocated for the UE identified by the U-RNTI in another cell than the accessed cell in which the Mac SDU sizes, flow control settings (including credits) and transport bearer are the same as in the old cell, there is no need for Common Transport Channel Resources Initialisation to be initiated. In that case, DRNC may include the Common Transport Channel Resources Initialisation Not Required IE in the UPLINK SIGNALLING TRANSFER INDICATION message. In addition, the DRNS shall move these RACH and/or FACH resources to the new cell. If no Common Transfer Channel Resources Initialisation procedure is executed, the currently applicable Mac SDU sizes, flow control settings (including credits) and transport bearer shall continue to be used while the UE is in the new cell.

3GPP

Release 11

42

3GPP TS 25.423 V11.2.0 (2012-06)

If no context exists for this UE in the DRNC, the DRNC shall create a UE Context for this UE, allocate a D-RNTI for the UE Context, and include the D-RNTI IE and the identifiers for the CN CS Domain and CN PS Domain that the DRNC is connected to in the UPLINK SIGNALLING TRANSFER INDICATION message. These CN Domain Identifiers shall be based on the LAC and RAC respectively of the cell where the message was received from the UE. Depending on local configuration in the DRNS, it may include the geographical co-ordinates of the cell, represented either by the Cell GAI IE or by the Cell GA Additional Shapes IE, in which the Uu message was received in the UPLINK SIGNALLING TRANSFER INDICATION message. If the DRNC includes the Cell GA Additional Shapes IE in the UPLINK SIGNALLING TRANSFER INDICATION message, it shall also include the Cell GAI IE. [FDD The DRNC shall include the DPC Mode Change Support Indicator IE in the UPLINK SIGNALLING TRANSFER INDICATION message if the accessed cell supports DPC mode change.] The DRNC shall include [FDD the Cell Capability Container FDD IE] [3.84Mcps TDD the Cell Capability Container TDD IE] [1.28Mcps TDD the Cell Capability Container TDD LCR IE] [7.68Mcps TDD the Cell Capability Container 7.68Mcps TDD IE] [FDD and/or the Cell Capability Container Extension FDD IE] in the UPLINK SIGNALLING TRANSFER INDICATION message if the accessed cell supports any functionalities listed in [FDD 9.2.2.D] [3.84Mcps TDD 9.2.3.1a] [1.28Mcps TDD 9.2.3.1b] [7.68Mcps TDD 9.2.3.31] [FDD 9.2.2.123]. [FDD If the cell is multicell adjacent and/or non-adjacent carrier operation capable and if the cell can be the serving HS-DSCH then the possible cells to serve multicell adjacent and/or non-adjacent carrier operation (same or adjacent sector in the same Node B) that can act as secondary serving HS-DSCH shall be listed in the Secondary Serving Cell List IE. For each cell in the Secondary Serving Cell List IE that is Multi Cell E-DCH capable, indicated in the Cell Capability Container Extension FDD IE by the Multi Cell E-DCH Support Indicator bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the accessed cell as the corresponding cell of the primary uplink frequency, the DRNS shall, if supported, include the Multicell E-DCH Restriction IE set to "TRUE". If the Secondary Serving Cell List IE is not present, the multicell (adjacent or non-adjacent carrier operation) capable cell can only serve as a secondary serving HS-DSCH cell in single band operation.] [FDD If the cell is dual band capable and if the cell can be the serving HS-DSCH then the possible cells to serve dual band carrier operation (same sector) that can act as secondary serving HS-DSCH shall be listed in the Dual Band Secondary Serving Cell List IE. If the Dual Band Secondary Serving Cell List IE is not present, the dual band capable cell can only serve as a secondary serving HS-DSCH cell in dual band operation.] If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of the concerned cell in the Multiple PLMN List IE in the UPLINK SIGNALLING TRANSFER INDICATION message. If available, the DRNC shall include the SNA Information IE for the concerned cell. When receiving the SNA Information IE, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control. [FDD The DRNC shall include the Cell Portion ID IE in the UPLINK SIGNALLING TRANSFER INDICATION message if available.] [1.28 Mcps TDD The DRNC shall include the Cell Portion LCR ID IE in the UPLINK SIGNALLING TRANSFER INDICATION message if available.] [FDD If the propagation delay value exceeds the range of the Propagation Delay IE then the DRNC shall if supported include the Extended Propagation Delay IE and set the Propagation Delay IE to its maximum value.] If the D-RNTI IE is not to be included in the UPLINK SIGNALLING TRANSFER INDICATION message and the UE Link is currently stored in the UE Context in the DRNC, the DRNC shall assume that the UE changes the cell under which it camps in the DRNS (see TS 25.346 [50], section 5.1.6 on intra-DRNC cell change). In this case, if an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in the cell identified by the UC-ID IE, the DRNC shall include in the Active MBMS Bearer Service List IE the Transmission Mode IE for each of these active MBMS bearer services. Or else, if the DRNC receives a Uu message on the CCCH in which the short identities for MBMS Selected Services are included, and the Uu message requests for MBMS PtP radio bearer establishment, the DRNC shall determine which TMGIs correspond with the short identities and shall include in the Active MBMS Bearer Service List IE the TMGI IE together with the Transmission Mode IE for each of these MBMS Selected Services.

3GPP

Release 11

43

3GPP TS 25.423 V11.2.0 (2012-06)

If the CCCH message contains Measurement results for monitored cells on non-used frequencies IE in Measured Result on RACH IE, the DRNC may include in the UPLINK SIGNALLING TRANSFER INDICATION message the Interfrequency Cell List IE for each of the measured inter-freqeuncy cells. The order of cells in Measurement results for monitored cells on non-used frequencies IE in the CCCH message shall be preserved in Inter-frequency Cell List IE. If the UL UARFCN IE in the Inter-frequency Cell List IE is not present, the default duplex distance defined for the operating frequency band shall be used in the SRNC (see TS 25.101 [43]). [3.84 Mcps TDD the DRNC shall include the Rx Timing Deviation IE unless the cell to which the CCCH message was sent is configured to use the extended timing advance in which case Rx Timing Deviation 3.84Mcps Extended IE shall be included.] [7.68 Mcps TDD the DRNC shall include the Rx Timing Deviation 7.68Mcps IE.]

8.2.1.3
-

Abnormal Conditions

8.2.1A GERAN Uplink Signalling Transfer

8.2.1A.1 General
The procedure is used by the DBSS to forward an Um message received on the SRB2 to the SBSS/SRNC. The procedure is also used by the DRNC to forward a Uu message received on the CCCH to the SBSS. This procedure shall use the connectionless mode of the signalling bearer.

8.2.1A.2

Successful Operation
DBSS/DRNC
Um/Uu message received from UE/MS containing S-RNTI and RNC/BSC ID as addressing information

SBSS/SRNC Layer

GERAN UPLINK SIGNALLING TRANSFER INDICATION

Figure 1A: GERAN Uplink Signalling Transfer procedure, Successful Operation When the DBSS receives an Um message on the SRB2 in which the MS addressing information is G-RNTI, i.e. SRNTI and BSC-ID, DBSS shall send the GERAN UPLINK SIGNALLING TRANSFER INDICATION message to the SBSS/SRNC identified by the BSC-ID received from the MS. Alternatively, when the DRNC receives an Uu message on the CCCH in which the UE addressing information is URNTI, i.e. S-RNTI and SRNC-ID, and in which the SRNC-ID points to a GERAN BSS, the DRNC shall send the GERAN UPLINK SIGNALLING TRANSFER INDICATION message to the SBSS identified by SRNC-ID received from the UE. If at least one GRA/URA Identity is being broadcast in the cell where the Um/Uu message was received (the accessed cell), the DBSS/DRNC shall include a GRA/URA Identity for this cell in the URA ID IE, the Multiple URAs Indicator IE indicating whether or not multiple GRA/URA Identities are being broadcast in the accessed cell, and the RNC/BSS Identity of all other RNC/BSSs that are having at least one cell within the GRA/URA where the Um/Uu message was received in the URA Information IE in the GERAN UPLINK SIGNALLING TRANSFER INDICATION message. If no context exists for this UE/MS in the DBSS/DRNC, the DBSS/DRNC shall create a UE Context for this UE/MS, allocate a D-RNTI for the UE Context, and include the D-RNTI IE and the identifiers for the CN CS Domain and CN PS Domain that the DBSS/DRNC is connected to in the GERAN UPLINK SIGNALLING TRANSFER INDICATION message. These CN Domain Identifiers shall be based on the LAC and RAC respectively of the cell where the message was received from the UE/MS.

3GPP

Release 11

44

3GPP TS 25.423 V11.2.0 (2012-06)

8.2.1A.3
-

Abnormal Conditions

8.2.2 Downlink Signalling Transfer

8.2.2.1 General
The procedure is used by the SRNC to request to the DRNC the transfer of a Uu message on the CCCH in a cell. When used, the procedure is in response to a received Uplink Signalling Transfer procedure. This procedure shall use the connectionless mode of the signalling bearer.

8.2.2.1.1

Downlink Signalling Transfer for Iur-g

The procedure is used by the SRNC/SBSS to request to the DBSS the transfer of an Um message on the SRB2 in a cell. The procedure is used by the SBSS to request to the DRNC the transfer of a Uu message on the CCCH in a cell.

8.2.2.2

Successful Operation
DRNC Layer
DOWNLINK SIGNALLING TRANSFER REQUEST

SRNC Layer

Figure 2: Downlink Signalling Transfer procedure, Successful Operation The procedure consists of the DOWNLINK SIGNALLING TRANSFER REQUEST message sent by the SRNC to the DRNC. The message contains the Cell Identifier (C-ID) contained in the received UPLINK SIGNALLING TRANSFER INDICATION message and the D-RNTI. Upon receipt of the message, the DRNC shall send the L3 Information on the CCCH in the cell indicated by the C-ID IE to the UE identified by the D-RNTI IE. If the D-RNTI Release Indication IE is set to Release D-RNTI and the DRNS has no dedicated resources (DCH, [TDD USCH and/or DSCH]) allocated for the UE, the DRNS shall release the D-RNTI, the UE Context and any RACH and FACH resources and any C-RNTI allocated to the UE Context upon receipt of the DOWNLINK SIGNALLING TRANSFER REQUEST message. If a UE Link is currently stored in the UE Context, the DRNC shall perform UE De-linking as specified in TS 25.346 [50], section 5.1.6. If the D-RNTI Release Indication IE is set to Release D-RNTI and the DRNS has dedicated resources allocated for the UE, the DRNS shall only release any RACH and FACH resources and any C-RNTI allocated to the UE Context upon receipt of the DOWNLINK SIGNALLING TRANSFER REQUEST message. If the MBMS Bearer Service List IE is included and URA-ID IE is not included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If the MBMS Bearer Service List IE is included and the URA-ID IE is included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform the URA Linking as specified in TS 25.346 [50], section 5.1.10. If the MBMS Bearer Service List IE is included and the Old URA-ID IE is included in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the DRNC shall perform URA De-linking for the URA identified by the Old URAID IE as specified in TS 25.346 [50], section 5.1.10.

3GPP

Release 11

45

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Enhanced PCH Capability IE is included in the message, the DRNC should store the information. If the Enhanced PCH Capability IE is not included in the message, the DRNC shall use the information to release an RRC Connection for the UE in cells supporting Enhanced PCH.] [1.28Mcps TDD If the Enhanced PCH Capability IE is included in the message, the DRNC should store the information. If the Enhanced PCH Capability IE is not included in the message, the DRNC shall use the information to release an RRC Connection for the UE in cells supporting Enhanced PCH.]

8.2.2.2.1

Successful Operation for Iur-g

The procedure consists of the DOWNLINK SIGNALLING TRANSFER REQUEST message sent by the SRNC/SBSS to the DBSS or by the SBSS to the DRNC. The message contains the Cell Identifier (C-ID) contained in the received UPLINK SIGNALLING TRANSFER INDICATION message and the D-RNTI. Upon receipt of the message, the DBSS shall send the L3 Information on the SRB2 in the cell indicated by the C-ID IE to the UE/MS identified by the D-RNTI IE. Upon receipt of the message, the DRNC shall send the L3 Information on the CCCH in the cell indicated by the C-ID IE to the UE/MS identified by the D-RNTI IE.

8.2.2.3

Abnormal Conditions

If the user identified by the D-RNTI IE has already accessed another cell controlled by the DRNC than the cell identified by the C-ID IE in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the message shall be ignored.

8.2.2.3.1

Abnormal Conditions for Iur-g

If the user identified by the D-RNTI IE has already accessed another cell controlled by the DRNC/DBSS than the cell identified by the C-ID IE in the DOWNLINK SIGNALLING TRANSFER REQUEST message, the message shall be ignored. If the DRNC receives from the SBSS the DOWNLINK SIGNALLING TRANSFER REQUEST message, in which the D-RNTI Release Indication IE is set to not Release D-RNTI, the DRNC shall ignore this IE and release the D-RNTI. If the DBSS receives from the SBSS/SRNC the DOWNLINK SIGNALLING TRANSFER REQUEST message, in which the D-RNTI Release Indication IE is set to not Release D-RNTI, the DBSS shall ignore this IE and release the D-RNTI.

8.2.3 Relocation Commit

8.2.3.1 General
The Relocation Commit procedure is used by source RNC to execute the Relocation. This procedure supports the Relocation procedures described in TS 25.413 [2]. This procedure shall use the signalling bearer mode specified below.

8.2.3.2

Successful Operation
Source RNC
RELOCATION COMMIT

Target RNC

Figure 3: Relocation Commit procedure, Successful Operation The source RNC sends the RELOCATION COMMIT message to the target RNC to request the target RNC to proceed with the Relocation. When the UE is utilising one or more radio links in the DRNC the message shall be sent using the

3GPP

Release 11

46

3GPP TS 25.423 V11.2.0 (2012-06)

connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the D-RNTI IE shall be included in the message to identify the UE Context in the DRNC. Upon receipt of the RELOCATION COMMIT message from the source RNC the target RNC finalises the Relocation. If the message contains the transparent RANAP Relocation Information IE the target RNC shall use this information when finalising the Relocation.

8.2.3.2.1

Successful Operation for Iur-g

The source RNC/BSS sends the RELOCATION COMMIT message to the target RNC/BSS to request the target RNC/BSS to proceed with the Relocation. The message shall be sent using the connectionless service of the signalling bearer and the D-RNTI IE shall be included in the message to identify the UE/MS context in the DBSS. Upon receipt of the RELOCATION COMMIT message from the source RNC/BSS, the target RNC/BSS finalises the Relocation. If the message contains the transparent RANAP Relocation Information IE the target RNC/BSS shall use this information when finalising the Relocation.

8.2.3.3
-

Abnormal Conditions

8.2.4 Paging
8.2.4.1 General
This procedure is used by the SRNC to indicate to a CRNC that a UE shall be paged in a cell or URA that is under the control of the CRNC. This procedure shall use the connectionless mode of the signalling bearer.

8.2.4.2

Successful Operation
SRNC Layer CRNC Layer

PAGING REQUEST

Figure 4: Paging procedure, Successful Operation The procedure is initiated with a PAGING REQUEST message sent from the SRNC to the CRNC. If the message contains the C-ID IE, the CRNC shall page in the indicated cell. Alternatively, if the message contains the URA-ID IE, the CRNC shall page in all cells that it controls in the indicated URA. If the PAGING REQUEST message includes the CN Originated Page to Connected Mode UE IE, the CRNC shall include the information contained in the CN Originated Page to Connected Mode UE IE when paging the UE. The CRNC shall calculate the Paging Occasions from the IMSI IE and the DRX Cycle Length Coefficient IE according to specification in TS 25.304 [15] and apply transmission on PICH and PCH [FDD or HS-DSCH] [1.28Mcps TDD or HS-DSCH] accordingly. [FDD If the PAGING REQUEST message includes the Enhanced PCH Capability IE, the CRNC shall use the information to page the UE in cells supporting Enhanced PCH.] [1.28Mcps TDD If the PAGING REQUEST message includes the Enhanced PCH Capability IE, the CRNC shall use the information to page the UE in cells supporting Enhanced PCH.]

3GPP

Release 11

47

3GPP TS 25.423 V11.2.0 (2012-06)

8.2.4.2.1

Successful Operation for Iur-g

The procedure is initiated with a PAGING REQUEST message sent from the SBSS to the CRNC/CBSS or from the SRNC to the CBSS. If the message contains the URA-ID IE, the CRNC/CBSS shall page in all cells that it controls in the indicated URA/GRA. If the PAGING REQUEST message includes the CN Originated Page to Connected Mode UE IE, the CRNC/CBSS shall include the information contained in the CN Originated Page to Connected Mode UE IE when paging the UE. The CBSS shall calculate the Paging Occasions from the IMSI IE and the GERAN DRX Cycle Length Coefficient IE according to specification in TS 44.118 [36] and apply transmission on PCCCH or PACCH accordingly.

8.2.4.3
8.2.4.3.1

Abnormal Conditions
Abnormal Conditions for Iur-g

If the DRNC receives a PAGING REQUEST message from the SBSS, which contains the C-ID IE, the message shall be ignored. If the DBSS receives a PAGING REQUEST message from the SBSS/SRNC, which contains the C-ID IE, the message shall be ignored.

8.2.5 MBSFN MCCH Information

8.2.5.1 General
The procedure is used by the MRNC to inform the CRNC of the MCCH configuration and scheduling information used in MRNC. This procedure shall use the connectionless mode of the signalling bearer.

8.2.5.2

Successful Operation

CRNC
MBSFN MCCH INFORMATION

MRNC

Figure 4A: MBSFN MCCH Information procedure, Successful Operation The procedure is used for MBSFN operation when a MRNC is used. The message contains the MCCH message list sent on the MRNC and the MCCH configuration information of the MRNC. Upon receipt of the message, if the MCCH Configuration IE exists, the CRNC shall setup or reconfigure the MCCH of all cells in the MBSFN cluster with the configuration contained in this IE, and update the System Information of these cells. The CRNC shall decode the L3 Information IE contained in the MCCH Message List IE and apply the RLC/MAC/PHY configuration specified by relative MCCH Message to setup the RB information of MTCH, and then send the L3 Information IE on the MCCH in the receiving sequence at the beginning of the first MCCH modification period following the CFN indicated by the CFN IE. In case MRNC is used and TDM multiplexing is used over air interface, the MBSFN Scheduling Transmission Time Interval info List IE shall be contained to show the scheduling transmission time interval for MBMS service which is configured with MBSFN TDM multiplexing. The CRNC shall schedule received data packets in the scheduling transmission time interval following the time point indicated by the timestamp.

3GPP

Release 11

48

3GPP TS 25.423 V11.2.0 (2012-06)

8.2.5.3
-

Abnormal Conditions

8.2.6 Enhanced Relocation Resource Allocation[1.28Mcps TDD]

8.2.6.1 General
The purpose of this procedure is to inform the BSS to pre-allocate resource for UE relocation from UTRAN to GERAN. This procedure shall use the signalling bearer connection for the relevant UE context.

8.2.6.2

Successful Operation
RNC
ENHANCED RELOCATION RESOURCE REQUEST ENHANCED RELOCATION RESOURCE RESPONSE

BSS

Figure 4B: Enhanced Relocation Resource Allocation Procedure, Successful Operation The RNC initiates the Enhanced Relocation Resource Allocation procedure by sending the ENHANCED RELOCATION RESOURCE REQUEST message to the BSS to request the BSS to prepare resource for the relocation. Upon receipt of the ENHANCED RELOCATION RESOURCE REQUEST message form the RNC, the BSS finalises the relocation resource preparation and sends ENHANCED RELOCATION RESOURCE RESPONSE message to the RNC.

8.2.6.3

Unsuccessful Operation
RNC
ENHANCED RELOCATION RESOURCE REQUEST ENHANCED RELOCATION RESOURCE FAILURE

BSS

Figure 4C: Enhanced Relocation Resource Allocation Procedure, Unsuccessful Operation If the BSS is not able to finalise the relocation resource preparation or can not accept the relocation resource request during the handover procedure, the BSS shall send the ENHANCED RELOCATION RESOURCE FAILURE message to the RNC.

8.2.6.4
-

Abnormal Conditions

8.2.7 Enhanced Relocation Resource Release[1.28Mcps TDD]

8.2.7.1 General
This procedure is used by the RNC to infom BSS that related resource pre-allocated for UE shall be released due to failure of the enhanced relocation from UTRAN TDD to GERAN. This procedure shall use the signalling bearer connection for the relevant UE context.

3GPP

Release 11

49

3GPP TS 25.423 V11.2.0 (2012-06)

8.2.7.2

Successful Operation
RNC
ENHANCED RELOCATIONRESOURCE RELEASE COMMAND ENHANCED RELOCATIONRESOURCE RELEASE COMPLETE

BSS

Figure 4D: Enhanced Relocation Resource Release Procedure, Successful Operation The Enhanced Relocation Resource Release procedure is initiated by sending the ENHANCED RELOCATION RESOURCE RELEASE COMMAND message from the RNC to the BSS. Upon reception of the ENHANCED RELOCATION RESOURCE RELEASE COMMAND message, the BSS shall release related resource pre-allocated for UE, and then responsed with the ENHANCD RELOCATION RESOURCE RELEASE COMPLETE meassage.

8.2.7.3
-

Abnormal Conditions

8.3 Dedicated Procedures

8.3.1 Radio Link Setup
8.3.1.1 General
This procedure is used for establishing the necessary resources in the DRNS for one or more radio links. The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure.

8.3.1.2

Successful Operation
SRNC Layer DRNC Layer

RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE

Figure 5: Radio Link Setup procedure: Successful Operation When the SRNC makes an algorithmic decision to add the first cell or set of cells from a DRNS to the active set of a specific UE-UTRAN connection, the RADIO LINK SETUP REQUEST message is sent to the corresponding DRNC to request establishment of the radio link(s). The Radio Link Setup procedure is initiated with this RADIO LINK SETUP REQUEST message sent from the SRNC to the DRNC. Upon receipt of the RADIO LINK SETUP REQUEST message, the DRNS shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. The DRNS shall prioritise resource allocation for the RL(s) to be established according to Annex A. If the RADIO LINK SETUP REQUEST message includes the Allowed Queuing Time IE the DRNS may queue the request for a time period not to exceed the value of the Allowed Queuing Time IE before starting to execute the request.

3GPP

Release 11

50

3GPP TS 25.423 V11.2.0 (2012-06)

If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK SETUP REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. If the Usefulness of Battery Optimization IE is contained in the RADIO LINK SETUP REQUEST message, the DRNC may store the received value and use it to determine whether this UE can benefit from battery optimization techniques. Transport Channels Handling: DCH(s): [TDD If the DCH Information IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new DCHs according to the parameters given in the message.] If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs, then the DRNS shall treat the DCHs in the DCH Information IE as a set of co-ordinated DCHs. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Uplink DCH only, the DRNS shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Downlink DCH only, the DRNS shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. [FDD For each DCH which do not belong to a set of co-ordinated DCHs, and which includes a QESelector IE set to selected, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the QE-Selector IE is set to non-selected, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].] For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the QESelector IE set to selected for the QE in the UL data frames, TS 25.427 [4]. [FDD If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have QE-Selector IE set to non-selected, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].] The DRNS shall use the included UL DCH FP Mode IE for a DCH or a set of co-ordinated DCHs as the DCH FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs. The DRNS shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs. The DRNS shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs as the Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs. The Frame Handling Priority IE defines the priority level that should be used by the DRNS to prioritise between different frames of the data frames of the DCHs in the downlink on the radio interface in congestion situations once the new RL(s) have been activated. The Traffic Class IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE indicates the value RRC. If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs. If the DCH Information IE contains a DCH Specific Info IE which includes the Guaranteed Rate Information IE, the DRNS shall treat the included IEs according to the following: If the Guaranteed Rate Information IE includes the Guaranteed UL Rate IE, the DRNS shall apply the Guaranteed Rate in the uplink of this DCH. The DRNS may decide to request the SRNC to limit the

3GPP

Release 11

51

3GPP TS 25.423 V11.2.0 (2012-06)

user rate of the uplink of the DCH at any point in time. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to only reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCH Information IE does not include the Guaranteed UL Rate IE, the DRNS shall not limit the user rate of the uplink of the DCH. If the Guaranteed Rate Information IE includes the Guaranteed DL Rate IE, the DRNS shall apply the Guaranteed Rate in the downlink of this DCH. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to only reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCH Information IE does not include the Guaranteed DL Rate IE, the DRNS shall not limit the user rate of the downlink of the DCH.

[FDD If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer shall not be Established for a DCH, then the DRNC shall not establish a transport bearer for the concerned DCH and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for a DCH and:] [FDD if the DRNC establishes a transport bearer for the concerned DCH, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH being established.] [FDD if the DRNC does not establish a transport bearer for the concerned DCH, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK SETUP RESPONSE message.]

[TDD DSCH(s):] [TDD If the DSCH Information IE is included in the RADIO LINK SETUP REQUEST message, the DRNC shall establish the requested DSCHs. If the Transport Layer Address IE and Binding ID IE are included in the DSCH Information IE the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DSCH. In addition, the DRNC shall send a valid set of DSCH Scheduling Priority IE and MAC-c/sh SDU Length IE parameters to the SRNC in the RADIO LINK SETUP RESPONSE message. If the PDSCH RL ID IE indicates a radio link in the DRNS, then the DRNC shall allocate a DSCH-RNTI to the UE Context and include the DSCH-RNTI IE in the RADIO LINK SETUP RESPONSE message.] [TDD If the DSCH Information IE is included in the RADIO LINK SETUP REQUEST message, the DRNS may use the Traffic Class IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.] [TDD The DRNC shall include the DSCH Initial Window Size IE in the RADIO LINK SETUP RESPONSE message for each DSCH, if the DRNS allows the SRNC to start transmission of MAC-c/sh SDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32].] [TDD If the RADIO LINK SETUP REQUEST message includes the TNL QoS IE in the DSCH TDD Information IE and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.] [TDD USCH(s):] [TDD The DRNS shall use the list of RB Identities in the RB Info IE in the USCH information IE to map each RB Identity IE to the corresponding USCH. If the Transport Layer Address IE and Binding ID IE are included in the USCH Information IE the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the USCH.] [TDD If the USCH Information IE is included in the RADIO LINK SETUP REQUEST message, the DRNS may use the Traffic Class IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.]

3GPP

Release 11

52

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD If the USCH Information IE is included in the RADIO LINK SETUP REQUEST message and contains the TNL QoS IE, and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related USCH.] [TDD If the USCH Information IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall establish the requested USCHs, and the DRNC shall provide the [3.84 Mcps TDD USCH Information Response IE] [1.28 Mcps TDD USCH Information Response LCR IE] [7.68 Mcps TDD USCH Information Response 7.68 Mcps IE] in the RADIO LINK SETUP RESPONSE message.] [TDD CCTrCH Handling:] [TDD If the UL CCTrCH Information IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new UL CCTrCH(s) according to the parameters given in the message.] [1.28Mcps TDD If the UL CCTrCH Information LCR IE includes the TDD TPC Uplink Step Size IE, the DRNS shall configure the uplink TPC step size according to the parameters given in the message.] [TDD If the DL CCTrCH Information IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the new DL CCTrCH(s) according to the parameters given in the message.] [TDD If the TPC CCTrCH List IE is present in the RADIO LINK SETUP REQUEST message, the DRNS shall configure the identified UL CCTrCHs with TPC according to the parameters given in the message.] HS-DSCH: If the HS-DSCH Information IE is present in the RADIO LINK SETUP REQUEST message, then: The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. The DRNC shall include the HARQ Memory Partitioning IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK SETUP RESPONSE message. [FDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.] [1.28Mcps TDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.] The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK SETUP RESPONSE message. The DRNC shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established. If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the HS-DSCH Information IE for an HS-DSCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HS-DSCH Information Response IE. If the RADIO LINK SETUP REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.

3GPP

Release 11 -

53

3GPP TS 25.423 V11.2.0 (2012-06)

If the RADIO LINK SETUP REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK SETUP RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK SETUP REQUEST message includes HSDSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to the value Flexible MACd PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK SETUP REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE. [FDD If the RADIO LINK SETUP REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68 Mcps TDD HS-SCCH Specific Information Response 7.68 Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [TDD The DRNC shall include the [3.84 Mcps TDD HS-PDSCH Timeslot Specific Information Response IE] [1.28 Mcps TDD HS-PDSCH Timeslot Specific Information Response LCR IE] [7.68 Mcps TDD HS-PDSCH Timeslot Specific Information Response IE] in the HS-DSCH Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HSDSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK SETUP RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the RADIO LINK SETUP RESPONSE message.] If the RADIO LINK SETUP REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). [FDD If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.]

3GPP

Release 11 -

54

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then] [FDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] [FDD The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[1.28 Mcps TDD If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then] [1.28 Mcps TDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] [1.28 Mcps TDD The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.]

[FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HSDSCH Radio Link.] [FDD If the RADIO LINK SETUP REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may use:] [FDD a different HS-SCCH in consecutive TTIs for this UE] [FDD HS-SCCH orders for the case of HS-SCCH-less operation to this UE]

[FDD If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNS shall include the SixtyfourQAM DL Support Indicator IE in the RADIO LINK SETUP RESPONSE message. This SixtyfourQAM DL Support Indicator IE is related to the HSDSCH Radio Link.] [1.28 Mcps TDD The DRNS shall include the SixtyfourQAM DL Support Indicator IE in the RADIO LINK SETUP RESPONSE message.]

3GPP

Release 11 -

55

3GPP TS 25.423 V11.2.0 (2012-06)

If the RADIO LINK SETUP REQUEST message includes the DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD If the RADIO LINK SETUP REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.] [1.28 Mcps TDD If the UE TS0 Capability LCR IE is included in the HS-DSCH TDD Information IE, then the DRNC may include the TS0 HS-PDSCH Indication LCR IE in the RADIO LINK SETUP RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]

[FDD Secondary Serving HS-DSCH:] [FDD If the Additional HS Cell Information RL Setup IE is present in the RADIO LINK SETUP REQUEST message, then:] [FDD The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HSDSCH cell.] [FDD The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCHRNTI IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Secondary Serving Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HSSCCH transmission to this UE.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HSDSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO for the secondary serving HS-DSCH Radio Link and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a

3GPP

Release 11

56

3GPP TS 25.423 V11.2.0 (2012-06)

non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and more than one secondary serving HS-DSCH Radio Link is setup, then the DRNS shall use this value in the physical layer.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If Sixtyfour QAM will not be used for the secondary serving HS-DCSH, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for the secondary serving HS-DSCH Transport Block Size signalling.] [FDD The DRNS shall include the SixtyfourQAM DL Support Indicator IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.]

[FDD E-DCH:] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DCH Minimum Set ETFCI Validity Indicator IE the DRNS shall ignore the value in E-DCH Minimum Set E-TFCI IE. If the EDCH Minimum Set E-TFCI validity indicator IE is absent DRNS shall use the value for the related resource allocation operation.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the DRNS shall use the EDPDCH power extrapolation formula defined in TS 25.214 [10].] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the DRNS shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the DRNS shall use the value 127 in the algorithm defined in TS 25.214 [10].] [FDD If the RADIO LINK SETUP REQUEST message includes the E-DPCH Information IE, which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the DRNS shall use the value to determine the applicable minimum gain factor (ed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK SETUP REQUEST message then:] [FDD The DRNS shall setup the requested E-DCH resources on the Radio Links indicated by the EDCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD If the RADIO LINK SETUP REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.]

3GPP

Release 11 -

57

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the RL specific E-DCH Information IE for an E-DCH MAC-d flow, then if the Transport Bearer Not Requested Indicator IE is not included for this E-DCH MAC-d flow, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. The DRNC shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the Transport Bearer Not Requested Indicator IE was not included.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer shall not be Established for an E-DCH MAC-d flow, then the DRNC shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for an E-DCH MAC-d flow and:] [FDD if the DRNC establishes a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.] [FDD if the DRNC does not establish a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding EDCH MAC-d flow in the RADIO LINK SETUP RESPONSE message.]

[FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [FDD If the RADIO LINK SETUP REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK SETUP REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [FDD If the RADIO LINK SETUP REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]

- [FDD If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.]

3GPP

Release 11 -

58

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the TNL QoS IE is included for a E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD The DRNC may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNC may include the corresponding E-RGCH Signature Sequence IE in the EDCH FDD DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message, for every RL indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD If the RADIO LINK SETUP REQUEST message includes the E-DCH ReferencePower Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]

[FDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK SETUP REQUEST message contains the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this DRNS:] [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both and include these E-RNTI identifiers and the Channelisation Code of the corresponding EAGCH in the E-DCH FDD DL Control Channel Information IE in the RL Information Response IE for the indicated RL in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK SETUP RESPONSE message for the initial grant for the serving E-DCH RL.] [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If a serving cell change is performed the RADIO LINK SETUP RESPONSE message may contain invalid data (see 9.2.2.4C).]

[FDD If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the EDCH FDD DL Control Channel Information IE in the RADIO LINK SETUP RESPONSE message, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the EDCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD The DRNS may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK SETUP RESPONSE message for the serving E-DCH RL.] [FDD If the RADIO LINK SETUP REQUEST message includes the Bundling Mode Indicator IE for a E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] [FDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.]

3GPP

Release 11 -

59

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK SETUP REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK SETUP REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK SETUP REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC.] [FDD If the RADIO LINK SETUP REQUEST message includes the SixteenQAM UL Operation Indicator IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.] [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]

[FDD Additional E-DCH Setup:] [FDD If the Additional E-DCH Cell Information RL Setup Req IE is present in the RADIO LINK SETUP REQUEST message, then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:] [FDD The DRNS shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional EDCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and FDPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] -[FDD If the UL SIR Target IE in the UL DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE and/or the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE are present, the DRNS shall use the information in the same same way as for the information used on Primary uplink frequency.] -[FDD If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] -[FDD If the Propagation Delay IE, the Initial DL Tx Power IE, Primary CPICH Ec/No IE, the EAGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] -[FDD If the Extended Propagation Delay IE and/or Enhanced Primary CPICH Ec/No IE is included in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH Secondary RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]

3GPP

Release 11

60

3GPP TS 25.423 V11.2.0 (2012-06)

-[FDD If the F-DPCH Slot Format Support Request IE in the F-DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Respone IE in the RADIO LINK SETUP RESPONSE message. If the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE includes the F-DPCH Slot Format IE, the DRNS may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.] -[FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Processing Overload Level IE are present in the Additional E-DCH FDD Information IE in the Additional EDCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in same way as for the information used on Primary uplink frequency.] [FDD If the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to Separate Iur Transport Bearer Mode the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to UL Flow Multiplexing Mode the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] [FDD if Separate Iur Transport Bearer Mode is used in the new configuration, then:] [FDD The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information IE in the RL Information IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] [FDD If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned EDCH MAC-d flow the DRNS shall include in the RADIO LINK SETUP RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

[FDD If activation of power balancing for the Additional E-DCH RL by the RADIO LINK SETUP REQUEST message is supported by the DRNS, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of EHICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE message. This value shall uniquely identify these Additional EDCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the

3GPP

Release 11

61

3GPP TS 25.423 V11.2.0 (2012-06)

Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the DRNS may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the EDCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message and if DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:] [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK SETUP REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC. If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link]

[FDD If the D-RNTI IE was included in the RADIO LINK SETUP REQUEST message the DRNS shall include in the RADIO LINK SETUP RESPONSE message the Primary Scrambling Code IE, the UL UARFCN IE and the DL UARFCN IE for the secondary UL frequency in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE RADIO LINK SETUP RESPONSE message.] [FDD If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Secondary CPICH Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK SETUP RESPONSE message. If the DRNS doesnt include the Secondary CPICH Information IE, it shall not include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used.]

[FDD E-DCH HS-DSCH:] [FDD If the RADIO LINK SETUP REQUEST message includes the DCH Indicator For E-DCH-HSDPA Operation IE, then the DRNS shall ignore the DCH Information IE in the RADIO LINK SETUP REQUEST message.]

3GPP

Release 11

62

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28 Mcps TDD - Multi-Carrier E-DCH Setup:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information IE is present in the RADIO LINK SETUP REQUEST message, then the Multi-Carrier E-DCH Information IE defines the new configuration and then:] [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.] [1.28Mcps TDD - The DRNS shall use the corresponding PRXdes_base IE for power control on each uplink frequency according to TS 25.331 [16].] [1.28Mcps TDD - If the SNPL Carrier Group Indicator IE is present in the Multi-Carrier E-DCH Information LCR IE, the DRNS shall use the information to determine which SNPL Carrier Group each frequency indicated by the UARFCN IE belongs to.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iur transport bearer mode", the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "E-DCH UL flow multiplexing mode", the DRNS shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iur transport bearer.] [1.28Mcps TDD - If the Separate Iur transport bearer mode is used in the new configuration, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response 1.28Mcps IE in the RADIO LINK SETUP RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

Physical Channels Handling: [FDD Compressed Mode:] [FDD If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE, the DRNS shall store the information about the Transmission Gap Pattern Sequences to be used in the Compressed Mode Configuration. This Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or the last Radio Link is deleted.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE and the Active Pattern Sequence Information IE, the DRNS shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received CM Configuration Change CFN IE refers to latest passed CFN with that value. The DRNS shall treat the received TGCFN IEs as follows:] [FDD If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] [FDD If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] [FDD For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the DRNS shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]

[FDD If the Downlink Compressed Mode Method IE in one or more Transmission Gap Pattern Sequence is set to SF/2 in the RADIO LINK SETUP REQUEST message and the UE Context is configured to use DPCH in the downlink, the DRNS shall include the Transmission Gap Pattern Sequence Scrambling Code

3GPP

Release 11

63

3GPP TS 25.423 V11.2.0 (2012-06)

Information IE in the RADIO LINK SETUP RESPONSE message indicating for each DL Channelisation Code whether the alternative scrambling code shall be used or not.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transmission Gap Pattern Sequence Information IE and the Active Pattern Sequence Information IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the information provided by the Downlink Compressed Mode Method IE if included for the concerned Transmission Gap Pattern Sequence(s).] [FDD - If the RADIO LINK SETUP REQUEST message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.] [FDD DL Code Information:] [FDD When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to PhCH number 1, the second to PhCH number 2, and so on until the pth to PhCH number p.] [FDD Phase Reference Handling:] [FDD If Primary CPICH is not to be used as a Phase Reference for this Radio Link, the DRNC shall include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the RADIO LINK SETUP RESPONSE message.] [FDD If Secondary CPICH may be used as a Phase Reference for this Radio Link, the DRNC shall include the Secondary CPICH Information IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the DRNC doesnt include the Secondary CPICH Information IE in the RADIO LINK SETUP RESPONSE message, it shall not include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the RADIO LINK SETUP RESPONSE message.] [FDD - UL CLTD Handling]: [FDD - If the UL CLTD Information IE is present in the RADIO LINK SETUP REQUEST message, then the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights and then :] [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the C-ID IE shall be included in the UL CLTD Information IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.] [FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]

General: [FDD If the Propagation Delay IE and optionally the Extended Propagation Delay IE are included, the DRNS may use this information to speed up the detection of UL synchronisation on the Uu interface.] [FDD If the received Limited Power Increase IE is set to Used, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control.] [TDD If the RADIO LINK SETUP REQUEST message includes the [1.28 Mcps TDD and 3.84 Mcps TDD Maximum Number of DL Physical Channels per Timeslot IE] [7.68 Mcps TDD Maximum Number of DL Physical Channels per Timeslot 7.68 Mcps IE] the DRNC shall take this value into account when allocating physical resources, otherwise the DRNC can assume that this UE capability is consistent with the other signalled UE capabilities.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Support for 8PSK IE within the DL Physical Channel Information IE or UL Physical Channel Information IE, the DRNC shall take this

3GPP

Release 11

64

3GPP TS 25.423 V11.2.0 (2012-06)

into account in the specified direction when allocating physical resources, otherwise the DRNC can assume that this UE does not support 8PSK resource allocation.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Support for PLCCH IE within the DL Physical Channel Information IE , the DRNC shall take this into account when allocating PLCCH sequence numbers, otherwise the DRNC can assume that this UE does not support PLCCH.] [FDD If the RADIO LINK SETUP REQUEST message includes the DL DPCH Information IE, then the DRNS shall configure the concerned UE Context to use DPCH in the downlink, i.e. with a DL DPCCH and a DL DPDCH.] [FDD If the RADIO LINK SETUP REQUEST message includes the F-DPCH Information IE, then:] [FDD The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink, i.e. with transmission of only the TPC field.] [FDD If the F-DPCH Information IE includes the F-DPCH Slot Format Support Request IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the RADIO LINK SETUP RESPONSE message. If the F-DPCH Information IE includes the F-DPCH Slot Format IE, the DRNC may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.]

[FDD E-DPCH Handling:] [FDD If the UL DPDCH Indicator for E-DCH operation IE is included in the UL DPCH Information IE and set to UL-DPDCH not present the Min UL Channelisation Code Length IE, the Puncture Limit IE and the TFCS IE, within the UL DPCH Information IE shall be ignored and no UL DPDCH resources shall be allocated.] [FDD Continuous Packet Connectivity Handling:] [FDD If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:] [FDD The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].] [FDD If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

[FDD If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity HSSCCH less Information IE, then:] [FDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].] [FDD The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If at least one of HS-PDSCH Second Code Support IE is set to True, then the DRNC shall include HS-PDSCH Second Code Index IE in the RADIO LINK SETUP RESPONSE message.]

[1.28 Mcps TDD Continuous Packet Connectivity Handling:] [1.28 Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].]

3GPP

Release 11

65

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28 Mcps TDD If the RADIO LINK SETUP REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HSPDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH SemiPersistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated HSPDSCH Semi-persistent resource IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD The DRNS shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD The DRNS shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.]

[1.28 Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the EDCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.]

[1.28 Mcps TDD - MU-MIMO Handling:] [1.28Mcps TDD - If the RADIO LINK SETUP REQUEST message includes the MU-MIMO Indicator IE, then:] [1.28 Mcps TDD - The DRNS may use the MU-MIMO for the radio link according to the MU-MIMO Usage Indicator IE and shall include the MU-MIMO Information IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the Standalone Midamble Channel Indicator IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK SETUP RESPONSE message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK SETUP RESPONSE message.]

Radio Link Handling: Diversity Combination Control: [FDD The Diversity Control Field IE indicates for each RL except for the first RL whether the DRNS shall combine the RL with any of the other RLs or not.] [FDD If the Diversity Control Field IE is set to May (be combined with another RL), the DRNS shall decide for any of the alternatives.] [FDD If the Diversity Control Field IE is set to Must, the DRNS shall combine the RL with one of the other RL.]

3GPP

Release 11 -

66

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Diversity Control Field IE is set to Must not, the DRNS shall not combine the RL with any other existing RL.]

[FDD When an RL is to be combined, the DRNS shall choose which RL(s) to combine it with.] [FDD The Diversity Control Field IE is only applicable for DCHs, in case of E-DCH it shall always be assumed to be set to May.] [FDD In the RADIO LINK SETUP RESPONSE message, the DRNC shall indicate for each RL with the Diversity Indication in the RL Information Response IE whether the RL is combined or not.] [FDD In case of not combining with a RL previously listed in the RADIO LINK SETUP RESPONSE message or for the first RL in the RADIO LINK SETUP RESPONSE message, the DRNC shall] [FDD in case of requested DCHs, include in the DCH Information Response IE in the RADIO LINK SETUP RESPONSE message for which the Transport Bearer Not Requested Indicator IE was not included the Binding ID IE and Transport Layer Address IE for the transport bearer to be established for each DCH of this RL.] [FDD in case of requested DCHs, include in the RADIO LINK SETUP RESPONSE message the Transport Bearer Not Setup Indicator IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK SETUP REQUEST message.] [FDD in case of a requested E-DCH, include in the E-DCH FDD Information Response IE in the RADIO LINK SETUP RESPONSE for which the Transport Bearer Not Requested Indicator IE was not included message the Binding ID IE and the Transport Layer Address IE for the establishment of transport bearers for every E-DCH MAC-d flow being established.] [FDD in case of a requested E-DCH, include in the RADIO LINK SETUP RESPONSE message the Transport Bearer Not Setup Indicator IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK SETUP REQUEST message.]

[FDD Otherwise in case of combining, the RL ID IE indicates (one of) the RL(s) previously listed in this RADIO LINK SETUP RESPONSE message with which the concerned RL is combined and if the ALCAP is not used and the transport bearer for the DCH is already established, the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used. In case of combining an E-DCH RL, one of the RLs previously listed in this RADIO LINK SETUP RESPONSE message including the E-DCH FDD Information Response IE and part of the same Radio Link Set shall be regarded as the RL with which the concerned E-DCH RL is combined and if the ALCAP is not used, the Transport Layer Address IE and the Binding ID IE in the RL SpecificE- DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK SETUP REQUEST message, shall not be used.]

[TDD The DRNC shall always include in the RADIO LINK SETUP RESPONSE message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DCH, DSCH and USCH of the RL.] In the case of a set of co-ordinated DCHs requiring a new transport bearer the Binding ID IE and the Transport Layer Address IE shall be included in the RADIO LINK SETUP RESPONSE message for only one of the DCHs in the set of co-ordinated DCHs [FDD where the Transport Bearer Not Requested Indicator IE was not included]. [FDD Transmit Diversity:] [FDD If the cell in which the RL is being set up is capable to provide Close loop Tx diversity, the DRNC shall include the Closed Loop Timing Adjustment Mode IE in the RADIO LINK SETUP RESPONSE message indicating the configured Closed loop timing adjustment mode of the cell.] [FDD When the Diversity Mode IE is set to STTD, or Closed loop mode1, the DRNC shall activate/deactivate the Transmit Diversity for each Radio Link in accordance with the Transmit Diversity Indicator IE.]

3GPP

Release 11

67

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE in the RADIO LINK SETUP REQUEST message, the DRNS shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to None the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.] DL Power Control: [FDD If both the Initial DL TX Power IE and Uplink SIR Target IE are included in the message, the DRNS shall use the indicated DL TX Power and Uplink SIR Target as initial value. If the value of the Initial DL TX Power IE is outside the configured DL TX power range, the DRNS shall apply these constraints when setting the initial DL TX power. The DRNS shall also include the configured DL TX power range defined by Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK SETUP RESPONSE message. The DRNS shall not transmit with a power higher than indicated by the Maximum DL TX Power IE or lower than indicated by the Minimum DL TX Power IE on any DL DPCH or on the F-DPCH of the RL except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the Pcurr, as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] [FDD If both the Initial DL TX Power and the Uplink SIR Target IEs are not included in the RADIO LINK SETUP REQUEST message, then DRNC shall determine the initial Uplink SIR Target and include it in the Uplink SIR Target IE in the RADIO LINK SETUP RESPONSE message.] [TDD The DRNC shall use the Uplink SIR Target CCTrCH IEs in the RADIO LINK SETUP RESPONSE message to indicate for any UL CCTrCH an Uplink SIR Target value in case this is deviating from the value included in the Uplink SIR Target IE specified for the Radio Link. If in any [3.84Mcps TDD UL CCTrCH Information IE] [1.28Mcps TDD UL CCTrCH Information LCR IE] [7.68Mcps TDD UL CCTrCH Information 7.68 Mcps IE] the Uplink SIR Target CCTrCH IE is not included, the value of the Uplink SIR Target IE shall apply to the respective UL CCTrCH.] [FDD If the Primary CPICH Ec/No IE is present, the DRNC should use the indicated value when deciding the Initial DL TX Power. If the Enhanced Primary CPICH Ec/No IE is present, the DRNC should use the indicated value when deciding the Initial DL Tx Power.] [TDD If [3.84Mcps TDD and 7.68 Mcps TDD the DL Time Slot ISCP Info IE] [1.28Mcps TDD the DL Time Slot ISCP Info LCR IE] is present, the DRNSshould use the indicated value when deciding the Initial DL TX Power for the Radio Link. The DRNS shall use the indicated DL Timeslot ISCP when determining the initial DL power per timeslot as specified in TS 25.224 [22], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.] [TDD If the Primary CCPCH RSCP Delta IE is included, the DRNS should assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included and the Primary CCPCH RSCP IE is included, the DRNS should assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP IE. The DRNS should use the indicated value when deciding the Initial DL TX Power for the Radio Link.] [3.84 Mcps TDD and 7.68 Mcps TDD The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK SETUP RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the value(s) for that CCTrCH in the CCTrCH Maximum DL TX Power IE and CCTrCH Minimum DL TX Power IE. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE/CCTrCH Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE on any DL DPCH within each CCTrCH of the RL.]

[1.28 Mcps TDD The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK SETUP RESPONSE message. If the maximum or minimum power needs to be different for

3GPP

Release 11

68

3GPP TS 25.423 V11.2.0 (2012-06)

particular timeslots within a DCH type CCTrCH, the DRNC shall include the value(s) for that timeslot in the Maximum DL TX Power IE and Minimum DL TX Power IE within the DL Timeslot Information LCR IE. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE on any DL DPCH within each timeslot of the RL.] [1.28McpsTDD If the TSTD Support Indicator IE is present, the DRNS shall apply this information when configuring the transmit diversity for the new radio link.] [FDD The DRNS shall start any DL transmission using the indicated DL TX power level (if received) or the decided DL TX power level on each DL channelisation code or on the F-DPCH of a RL until UL synchronisation is achieved on the Uu interface for the concerned RLS or Power Balancing is activated. No inner loop power control or power balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10] subclause 5.2.1.2) and the power control procedure (see 8.3.15).] [TDD The DRNS shall start any DL transmission using the decided DL TX power level on each DL channelisation code and on each Time Slot of a RL until UL synchronisation is achieved on the Uu interface for the concerned RL. No inner loop power control shall be performed during this period. Then after UL synchronisation, the DL power shall vary according to the inner loop power control (see TS 25.224 [22] subclause 4.2.3.3).] [FDD If the received Inner Loop DL PC Status IE is set to Active, the DRNS shall activate the inner loop DL power control for all RLs. If Inner Loop DL PC Status IE is set to Inactive, the DRNS shall deactivate the inner loop DL power control for all RLs according to TS 25.214 [10].] [FDD If the DPC Mode IE is present in the RADIO LINK SETUP REQUEST message, the DRNC shall apply the DPC mode indicated in the message, and be prepared that the DPC mode may be changed during the lifetime of the RL. If the DPC Mode IE is not present in the RADIO LINK SETUP REQUEST message, DPC mode 0 shall be applied (see TS 25.214 [10]).] [FDD If the RADIO LINK SETUP REQUEST message includes the DL Power Balancing Information IE and the Power Adjustment Type IE is set to Common or Individual, the DRNS shall activate the power balancing, if activation of power balancing by the RADIO LINK SETUP REQUEST message is supported, according to subclause 8.3.15, using the DL Power Balancing Information IE. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing i.e. Pinit shall be set to the power level indicated by the Initial DL TX Power IE (if received) or the decided DL TX power level on each DL channelisation code of a RL based on the Primary CPICH Ec/No IE or the Enhanced Primary CPICH Ec/No IE.] [FDD If activation of power balancing by the RADIO LINK SETUP REQUEST message is supported by the DRNS, the DRNC shall include the DL Power Balancing Activation Indicator IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message.] Neighbouring Cell Handling: If there are UMTS neighbouring cell(s) to the cell in which a Radio Link was established then: The DRNC shall include in the RADIO LINK SETUP RESPONSE message the Neighbouring FDD Cell Information IE and/or Neighbouring TDD Cell Information IE in the Neighbouring UMTS Cell Information IE for each neighbouring FDD cell and/or TDD cell respectively. In addition, if the information is available, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Frame Offset IE, Primary CPICH Power IE, Cell Individual Offset IE, STTD Support Indicator IE, Closed Loop Mode1 Support Indicator IE, Coverage Indicator IE, Antenna Co-location Indicator IE and HCS Prio IE in the Neighbouring FDD Cell Information IE, and the Frame Offset IE, Cell Individual Offset IE, DPCH Constant Value IE, the PCCPCH Power IE, Coverage Indicator IE, Antenna Colocation Indicator IE and HCS Prio IE in the Neighbouring TDD Cell Information IE or the Neighbouring TDD Cell Information LCR IE. If the Neighbouring TDD Cell Information IE includes the Sync Case IE for the set to Case1, the DRNC shall include the Time Slot For SCH IE in the Neighbouring TDD Cell Information IE. If the Neighbouring TDD Cell Information IE includes Sync Case IE set to Case2, the DRNC shall include the SCH Time Slot IE in the Neighbouring TDD Cell Information IE.

3GPP

Release 11 -

69

3GPP TS 25.423 V11.2.0 (2012-06)

If a UMTS neighbouring cell is not controlled by the same DRNC, the DRNC shall also include in the RADIO LINK SETUP RESPONSE message the CN PS Domain Identifier IE and/or CN CS Domain Identifier IE which are the identifiers of the CN nodes connected to the RNC controlling the UMTS neighbouring cell. If the information is available, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the DPC Mode Change Support Indicator IE for each neighbour cell in the Neighbouring FDD Cell Information IE The DRNC shall include the Cell Capability Container FDD IE, the Cell Capability Container TDD IE, the Cell Capability Container TDD LCR IE and/or the Cell Capability Container Extension FDD IE if the DRNC is aware that the neighbouring cell supports any functionality listed in 9.2.2.D, 9.2.3.1a, 9.2.3.1b and/or the Cell Capability Container Extension FDD IE. [FDD The DRNC shall, if supported, include the Cell List Validity Indicator IE if the neighbouring cell is multi cell capable and/or dual band capable but the cell can not be the serving HS-DSCH in a multicell and/or dual band configuration. Hence the cell can only serve as the secondary serving HS-DSCH cell. When Cell List Validity Indicator IE is included the SRNC should ignore the indicated cell list(s).] [FDD For each cell in the Secondary Serving Cell List IE that is Multi Cell E-DCH capable, indicated in the Cell Capability Container Extension FDD IE by the "Multi Cell E-DCH Support Indicator" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the cell identified by the C-ID IE as the corresponding cell of the primary uplink frequency, the DRNS shall, if supported, include the Multicell E-DCH Restriction IE set to "TRUE".] For the UMTS neighbouring cells which are controlled by the DRNC, the DRNC shall report in the RADIO LINK SETUP RESPONSE message the restriction state of those cells, otherwise the Restriction State Indicator IE may be absent. The DRNC shall include in the RADIO LINK SETUP RESPONSE message the Restriction State Indicator IE for the neighbouring cells which are controlled by the DRNC in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of the concerned neighbouring cells in the Multiple PLMN List IE in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If available, the DRNC shall include the SNA Information IE for the concerned neighbouring cells in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If available, the DRNC shall include the Frequency Band Indicator IE for the concerned neighbouring cells in the Neighbouring FDD Cell Information IE. If the number of neighbouring UMTS RNCs is beyond the predefined maximum number, the DRNC shall, if supported, include the remaining neighbouring information in the Neighbouring UMTS Cell Information Extension IE. The IE filling rules in the Neighbouring UMTS Cell Information shall also apply to the Neighbouring UMTS Cell Information Extension IE.

If there are GSM neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Neighbouring GSM Cell Information IE for each of the GSM neighbouring cells. If available the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Cell Individual Offset IE, and if the Cell Individual Offset IE alone cannot represent the value of the offset, the DRNC shall also include the Extended GSM Cell Individual Offset IE in the Neighbouring GSM Cell Information IE. If available the DRNC shall also include in the RADIO LINK SETUP RESPONSE message the Coverage Indicator IE, Antenna Co-location Indicator IE and HCS Prio IE in the Neighbouring GSM Cell Information IE. If available, the DRNC shall also include the SNA Information IE for the concerned neighbouring cells in the Neighbouring GSM Cell Information IE. When receiving the SNA Information IE in the RADIO LINK SETUP RESPONSE message, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control.

3GPP

Release 11

70

3GPP TS 25.423 V11.2.0 (2012-06)

If there are GERAN neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include the GERAN Cell Capability IE in the Neighbouring GSM Cell Information IE that is included in the RADIO LINK SETUP RESPONSE message for each of the GERAN cells. If there are GERAN Iu-mode neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include, if available, the GERAN Classmark IE in the Neighbouring GSM Cell Information IE that is included in the RADIO LINK SETUP RESPONSE message for each of the GERAN Iu-mode neighbouring cells. TS 43.051 [39] defines when the transmission of the GERAN Classmark IE will be required at the initiation of the Relocation Preparation procedure. If there are E-UTRA neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Neighbouring E-UTRA Cell Information IE for each of the E-UTRA neighbouring cells. [1.28Mcps TDD Uplink Synchronisation Parameters LCR:] [1.28Mcps TDD If the Uplink Synchronisation Parameters LCR IE is present, the DRNC shall use the indicated values of Uplink synchronisation stepsize IE and Uplink synchronisation frequency IE when evaluating the timing of the UL synchronisation.] [1.28Mcps TDD Shared physical channels Synchronisation Detection:] [1.28Mcps TDD If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall also include the Out-of-sync Detection Window IE in the HS-DSCH TDD Information Response IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD Uplink Timing Advance Control LCR:] [1.28Mcps TDD The DRNC shall include the Uplink Timing Advance Control LCR IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD PowerControl GAP:] [1.28Mcps TDD If applied in the DRNS, the DRNC may include the PowerControl GAP IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD E-UTRAN Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Idle Interval Configuration Indicator IE, if supported, the DRNC shall include the Idle Interval Information IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD RNTI Allocation Indicator:] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the RNTI Allocation Indicator IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL_FACH state.] [1.28Mcps TDD Inter-frequency/ Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the DCH Measurement Type indicator IE, if supported, the DRNS shall include the Measurement purpose IE and the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE in the RADIO LINK SETUP RESPONSE message to configure the measurement occasion pattern(s) indicated by the DCH Measurement Type indicator IE.] MBMS Handling: If the MBMS Bearer Service List IE is included in the RADIO LINK SETUP REQUEST message, the DRNC shall, if supported, perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If the UE Link is currently stored in the UE Context or the MBMS Bearer Service List IE is included in the RADIO LINK SETUP REQUEST message and if an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in some of the cells identified by the C-ID IEs in the RADIO LINK SETUP REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the Active MBMS Bearer Service List IE the Transmission Mode IE in the concerned RL Information Response IEs in the RADIO LINK SETUP RESPONSE message.

3GPP

Release 11

71

3GPP TS 25.423 V11.2.0 (2012-06)

If the UE Link is currently stored in the UE Context or the MBMS Bearer Service List IE is included in the RADIO LINK SETUP REQUEST message and if an MBMS preferred frequency layer for some active MBMS bearer services contained in the UE Link is set in some of the cells identified by the C-ID IEs in the RADIO LINK SETUP REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the Active MBMS Bearer Service List IE the Preferred Frequency Layer IE in the concerned RL Information Response IEs in the RADIO LINK SETUP RESPONSE message. [FDD HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] [FDD If the RADIO LINK SETUP REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE for a Radio Link not indicated by the HS-PDSCH RL ID IE the DRNS shall if supported preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [63]: ] [FDD The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK SETUP REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-ID IEs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK SETUP REQUEST message. ] [FDD The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ] [FDD by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell] [FDD by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]

[FDD If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ] [FDD The DRNS shall return these codes in the Sets of HS-SCCH Codes IE along with the corresponding per-cell HS-DSCH-RNTI IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message. ] [FDD The DRNS shall use the first in the numbered list of the primary serving HS-DSCH cells HSSCCH codes in the HS-SCCH Preconfigured Codes IE sent to the SRNC to signal the Target Cell HSSCCH Order defined in TS 25.331 [16].] [FDD The DRNS shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message, IEs according to the rules defined for HSDSCH setup and: ] [FDD if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE] [FDD if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the Pilot Configuration and MIMO N/M Ratio in MIMO Information Response IE] [FDD if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used in the preconfiguration, the HS-DSCH TB Size Table Indicator IE for each preconfigured cell] [FDD if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell] [FDD if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE]

3GPP

Release 11 -

72

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS shall store this information in the preconfigured configuration.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.] [FDD the SixtyfourQAM DL Support Indicator IE shall be included] [FDD if the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS may store this information in the preconfigured configuration.] [FDD the DRNS shall, if supported, include in the Sets of HS-SCCH Codes IE the Measurement Power Offset IE for each preconfigured cell.]

[FDD The DRNS shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows: ] [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these ERNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.] [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

[FDD If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the DRNS shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK SETUP RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK SETUP FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the EDCH FDD DL Control Channel Information IE. ] [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

[FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where HS-DSCH / secondary HS-DSCH is preconfigured, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH Preconfiguration Info IE or in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE for each preconfigured cell in the RADIO LINK SETUP RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD If the RADIO LINK SETUP REQUEST message includes the Non-Serving RL Preconfiguration Setup IE in the RL Information IE and:] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-

3GPP

Release 11

73

3GPP TS 25.423 V11.2.0 (2012-06)

DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK SETUP RESPONSE message.] [FDD if the choice of new Serving RL is "New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK SETUP RESPONSE message.] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New nonserving RL E-DCH FDD DL Control Channel Information C IE for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.]

[FDD if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New nonserving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving EDCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK SETUP RESPONSE message.] General: If the RADIO LINK SETUP REQUEST message includes the RL Specific DCH Information IE, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD for every DCH being established for which the Transport Bearer Not Requested Indicator IE was not included]. If no D-RNTI IE was included in the RADIO LINK SETUP REQUEST message, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the D-RNTI IE, the CN PS Domain Identifier IE and/or the CN CS Domain Identifier IE for the CN domains (using LAC and RAC of the current cell) to which the DRNC is connected. [1.28 Mcps TDD If no D-RNTI IE was included in the RADIO LINK SETUP REQUEST message, the DRNC could include in the RADIO LINK SETUP RESPONSE message the UARFCN IE.] [FDD If the D-RNTI IE was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Primary Scrambling Code IE, the UL UARFCN IE and the DL UARFCN IE.] [TDD If the D-RNTI IE was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the UARFCN IE, the Cell Parameter ID IE and the SCTD Indicator IE.] [3.84Mcps TDD and 7.68 Mcps TDD If the D-RNTI IE was included in the RADIO LINK SETUP REQUEST message the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Sync Case IE and if the Sync Case IE is set to Case 2, the DRNC shall also include the SCH Time Slot IE in the RADIO LINK SETUP RESPONSE message. If the included Sync Case IE is set to Case1, the DRNC shall also include the Time Slot For SCH IE.] [3.84Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response IE or USCH Information Response IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info TDD IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response IE or USCH Information Response IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [1.28 Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response LCR IE or USCH Information Response LCR IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response LCR IE or USCH Information Response

3GPP

Release 11

74

3GPP TS 25.423 V11.2.0 (2012-06)

LCR IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [7.68 Mcps TDD The DRNC shall include the Secondary CCPCH Info 7.68Mcps TDD IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response 7.68 Mcps IE or USCH Information Response 7.68 Mcps IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info 7.68Mcps TDD IE in the RADIO LINK SETUP RESPONSE message if at least one DSCH Information Response 7.68 Mcps IE or USCH Information Response 7.68 Mcps IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] For each Radio Link established in a cell in which at least one URA Identity is being broadcast, the DRNC shall include in the URA Information IE within the RADIO LINK SETUP RESPONSE message URA Innformation for this cell including the URA ID IE, the Multiple URAs Indicator IE indicating whether or not multiple URA Identities are being broadcast in the cell, and the RNC-ID Iesof all other RNCs that have at least one cell within the URA identified by the URA ID IE. Depending on local configuration in the DRNS, the DRNC may include in the RADIO LINK SETUP RESPONSE message the UTRAN Access Point Position IE and the geographical co-ordinates of the cell, represented either by the Cell GAI IE or by the Cell GA Additional Shapes IE. If the DRNC includes the Cell GA Additional Shapes IE in the RADIO LINK SETUP RESPONSE message, it shall also include the Cell GAI IE. If the DRNS need to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Allowed UL Rate IE in the DCH Information Response IE for this Radio Link. If the DRNS need to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK SETUP RESPONSE message the Allowed DL Rate IE in the DCH Information Response IE for this Radio Link. If the Permanent NAS UE Identity IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall store the information for the considered UE Context for the life-time of the UE Context. If the RADIO LINK SETUP REQUEST message includes the Permanent NAS UE Identity IE and a C-ID IE corresponding to a cell reserved for operator use, the DRNS shall use this information to determine whether it can set up a Radio Link on this cell or not for the considered UE Context. If the HCS priority information is available in the DRNS, it shall include the HCS Prio IE for each of the established RLs in the RADIO LINK SETUP RESPONSE message. The DRNS shall start receiving on the new RL(s) after the RLs are successfully established. [FDD If the RADIO LINK SETUP REQUEST message includes the Cell Portion ID IE, the DRNS shall use this information when it decides to use beamforming for the new RL.] [1.28 Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Cell Portion LCR ID IE, the DRNS shall use this information when it decides to allocate physical resource for the new RL.] [FDD If the RADIO LINK SETUP REQUEST message includes the Initial DL DPCH Timing Adjustment Allowed IE, then the DRNS may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the DRNS shall include, for the concerned Radio Link(s), the Initial DL DPCH Timing Adjustment IE in the Radio Link Information Response IE in the RADIO LINK SETUP RESPONSE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the D-RNTI IE which already has a RL and Synchonisation Indicator IE, the DRNC shall ignore the value in the Frame Offset IE and Chip Offset IE in the RADIO LINK SETUP REQUEST message and shall include in the Frame Offset IE and Chip Offset IE the values used for already established RL in the RADIO LINK SETUP RESPONSE message.]

3GPP

Release 11

75

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD - If the RADIO LINK SETUP REQUEST message includes the F-TPICH Information IE in the RL Information IE, the DRNS shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] [FDD Radio Link Set Handling:] [FDD The First RLS Indicator IE indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The DRNS shall use the First RLS Indicator IE to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.] [FDD For each RL not having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to the RL a unique value for the RL Set ID IE which uniquely identifies the RL as an RL Set within the UE Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Set(s) shall not be common.] [FDD For all RLs having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to each RL the same value for the RL Set ID IE which uniquely identifies these RLs as members of the same RL Set within the UE Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.] [FDD The UL oout-of-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.] [FDD For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the E-DCH RL Set ID IE in the RADIO LINK SETUP RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] [TDD- E-DCH:] [TDD If the [3.84Mcps E-DCH Information IE][1.28Mcps E-DCH Information 1.28Mcps IE][7.68Mcps TDD E-DCH Information 7.68Mcps IE] is present in the RADIO LINK SETUP REQUEST message:] [TDD The DRNS shall setup the requested E-DCH resources on the Radio Link indicated by the E-DCH Serving RL IE.] [TDD If the TNL QoS IE is included in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [TDD If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and Binding ID IE in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.] [TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flows Information TDD IE, the DRNS shall use this information for the related resource allocation operation.] [TDD If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to Non-scheduled for an E-DCH MAC-d flow the DRNS shall assume nonscheduled grants are configured for that E-DCH MAC-d flow.] [TDD If in the RADIO LINK SETUP REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to Scheduled the DRNS shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.] [TDD If the RADIO LINK SETUP REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions for the related queue.]

3GPP

Release 11 -

76

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [TDD If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [3.84Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH TDD Maximum Bitrate IE in the E-DCH TDD Information IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [7.68Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE in the E-DCH TDD Information 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [3.84Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [7.68Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information 7.68Mcps IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information LCR IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [TDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B.] [TDD If the RADIO LINK SETUP REQUEST message includes the [3.84Mcps TDD E-DCH TDD Information IE][1.28Mcps TDD E-DCH TDD Information LCR IE] in the E-DCH MAC-d Flows Information TDD IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE in the E-DCH TDD Information LCR IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] [3.84Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information TDD IE in the E-DCH Information Response IE in the RADIO LINK SETUP RESPONSE message.] [3.84Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the EAGCH(s) assigned in the E-DCH Information Response IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information LCR TDD IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK ADDITION RESPONSE message.]

3GPP

Release 11 -

77

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier, the EAGCH(s) and E-HICH(s) assigned in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK SETUP RESPONSE message.] [7.68Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information7.68Mcps TDD IE in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK SETUP RESPONSE message.] [7.68Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the EAGCH(s) assigned in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK SETUP RESPONSE message.] [1.28Mcps TDD If the RADIO LINK SETUP REQUEST message includes the Multi-Carrier E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present and if the RADIO LINK SETUP REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]

Response Message: Upon receipt of the RADIO LINK SETUP REQUEST message, the DRNS allocates the requested type of channelisation codes and other physical channel resources for each RL and assigns a binding identifier and a transport layer address for each DCH, for each set of co-ordinated DCHs [TDD and for each DSCH and USCH]. This information shall be sent to the SRNC in the RADIO LINK SETUP RESPONSE message when all the RLs have been successfully established. [1.28 Mcps TDD if the DRNS assigns one or more PLCCH sequence numbers to the radio link, then the PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK SETUP RESPONSE message.] After sending the RADIO LINK SETUP RESPONSE message the DRNS shall continuously attempt to obtain UL synchronisation on the Uu interface and start reception on the new RL. For each RL for which the Delayed Activation IE is not included in the RADIO LINK SETUP REQUEST message the DRNS shall: [FDD start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4].] [TDD start transmission on the new RL immediately as specified in TS 25.427 [4].]

For each RL for which the Delayed Activation IE is included in the RADIO LINK SETUP REQUEST message, the DRNS shall: if the Delayed Activation IE indicates Separate Indication: - not start any DL transmission for the concerned RL on the Uu interface; if the Delayed Activation IE indicates CFN: - [FDD start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4], however never before the CFN indicated in the Activation CFN IE.] - [TDD start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [4].]

3GPP

Release 11

78

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.1.3

Unsuccessful Operation
SRNC Layer DRNC Layer

RADIO LINK SETUP REQUEST RADIO LINK SETUP FAILURE

Figure 6: Radio Link Setup procedure: Unsuccessful Operation If the establishment of at least one radio link is unsuccessful, the DRNC shall respond with a RADIO LINK SETUP FAILURE message. The DRNC shall include in the RADIO LINK SETUP FAILURE message a general Cause IE or a Cause IE for each failed radio link. The Cause IE indicates the reason for failure. [FDD If some radio links were established successfully, the DRNC shall indicate this in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message.] If the RADIO LINK SETUP REQUEST message includes a C-ID IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity IE is not present, the DRNC shall reject the procedure and send the RADIO LINK SETUP FAILURE message. [FDD If the RL identified by the HS-PDSCH RL ID IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE, the HS-DSCH FDD Information Response IE and the SixtyfourQAM DL Support Indicator IE in the RADIO LINK SETUP FAILURE message. This SixtyfourQAM DL Support Indicator IE is related to the HS-DSCH Radio Link.] [FDD If the RL identified by the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Setup IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE, the HS-DSCH FDD Secondary Serving Information Response IE and the SixtyfourQAM DL Support Indicator IE in the Additional HS Cell Information Response IE in the RADIO LINK SETUP FAILURE message. If the establishment of the RL identified by the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Setup IE, i.e secondary serving HS-DSCH Radio Link is unsuccessful but the establishment of the RL identified by the HS-PDSCH RL ID IE for the serving HS-DSCH Radio Link is successful, then the DRNC shall indicate the unsuccessful secondary serving HS-DSCH Radio Link in the Unsuccessful RL Information Response IE in the RADIO LINK SETUP FAILURE message by setting the RL ID IE to the same value as the unsuccessful HSPDSCH RL ID IE in the Additional HS Cell Information RL Setup IE.] [1.28 Mcps TDD If the RL identified by the HS-PDSCH RL ID IE is a radio link in the DRNS and this RL is successfully established, then the DRNC shall allocate a HS-DSCH-RNTI to the UE Context and include the HSDSCH-RNTI IE, the HS-DSCH TDD Information Response IE and the SixtyfourQAM DL Support Indicator IE in the RADIO LINK SETUP FAILURE message.] [FDD If the MIMO Activation Indicator IE is included and the Power Offset For S-CPICH for MIMO Request Indicator IE is not included in the HS-DSCH FDD Information IE in the RADIO LINK SETUP REQUEST message but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK SETUP FAILURE message the Cause IE.] [FDD If the RL identified by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE is a radio link in the DRNS and this RL is successfully established, then the DRNS shall include the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response IE in the RADIO LINK SETUP FAILURE message in the same way as in the RADIO LINK SETUP RESPONSE message. If the establishment of the RL identified by the E-DCH Additional RL ID IE is unsuccessful, then the DRNS shall indicate the unsuccessful setup of the Additional E-DCH Radio Link in the Unsuccessful RL Information Response IE in the RADIO LINK SETUP FAILURE message by setting the RL ID IE to the same value as the unsuccessful E-DCH Additional RL ID IE in the Additional E-DCH Cell Information Setup IE.] Typical cause values are: Radio Network Layer Causes:

3GPP

Release 11

79

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD UL Scrambling Code Already in Use;] DL Radio Resources not Available; UL Radio Resources not Available; [FDD Combining Resources not available;] Combining not Supported Requested Configuration not Supported; Cell not Available; [FDD Requested Tx Diversity Mode not Supported;] Power Level not Supported; Number of DL codes not supported; Number of UL codes not supported; Dedicated Transport Channel Type not Supported; DL Shared Channel Type not Supported; [TDD UL Shared Channel Type not Supported;] [FDD UL Spreading Factor not Supported;] [FDD DL Spreading Factor not Supported;] CM not Supported; [FDD DPC mode change not Supported;] Cell reserved for operator use; Delayed Activation not supported; E-DCH not supported; [FDD F-DPCH not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not Supported;] [FDD Continuous Packet Connectivity HS-SCCH less operation not Supported;] [FDD MIMO not supported;] [FDD E-DCH TTI2ms not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not available;] [FDD Continuous Packet Connectivity UE DTX Cycle not available;] [FDD MIMO not available;] [FDD SixteenQAM UL not Supported;] HS-DSCH MAC-d PDU Size Format not supported; [FDD F-DPCH Slot Format operation not supported;] E-DCH MAC-d PDU Size Format not available; [FDD E-DPCCH Power Boosting not supported;] [FDD SixtyfourQAM DL and MIMO Combined not available;] [FDD Multi Cell operation not available;] [FDD Multi Cell operation not supported;] [FDD Multi Cell operation with MIMO not available;] [FDD Multi Cell operation with MIMO not supported;] [FDD Single Stream MIMO not supported;] [FDD Single Stream MIMO not available;] [FDD TX diversity for MIMO UE on DL Control Channels not available;] [FDD Multi Cell E-DCH Operation not supported;] [FDD Multi Cell E-DCH Operation not available;] [FDD Multi Cell operation with Single Stream MIMO not available;] [FDD Multi Cell operation with Single Stream MIMO not supported;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;] [FDD Frequency Specific Compressed Mode Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Supported.] Transport Layer Causes: Transport Resource Unavailable. Miscellaneous Causes: Control Processing Overload; HW Failure; Not enough User Plane Processing Resources.

3GPP

Release 11

80

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.1.4

Abnormal Conditions

If the DRNC receives either an S-RNTI or a D-RNTI which already has RL(s) established [FDD and the Synchronisation Indicator IE is not included in the RADIO LINK SETUP message,] the DRNC shall send the RADIO LINK SETUP FAILURE message to the SRNC, indicating the reason for failure. [FDD If the RADIO LINK SETUP REQUEST message includes the Active Pattern Sequence Information IE, but the Transmission Gap Pattern Sequence Information IE is not present, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message includes both the Initial DL TX Power IE and the Primary CPICH Ec/No IE or does not include either of these IEs, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected [TDD or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected] the DRNS shall reject the Radio Link Setup procedure and shall respond with a RADIO LINK SETUP FAILURE message. [FDD If only the Initial DL TX Power IE or the Uplink SIR Target IE is included in the RADIO LINK SETUP REQUEST message, then DRNC shall reject the Radio Link Setup procedure and shall respond with the RADIO LINK SETUP FAILURE message.] If the RADIO LINK SETUP REQUEST message includes a DCH Information IE with multiple DCH Specific Info IEs, and if the DCHs in the DCH Information IE do not have the same Transmission Time Interval IE in the Semi-static Transport Format Information IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. [FDD If the RADIO LINK SETUP REQUEST message includes the Enhanced Primary CPICH Ec/No IE, but not the Primary CPICH Ec/No IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE [FDD or in the RL Specific E-DCH Information IE] included in the RL Information IE for a specific RL and the Diversity Control Field IE is set to Must [FDD- or the RL is combined with an E-DCH RL previously listed in the RADIO LINK SETUP RESPONSE message in the DRNS], the DRNC shall reject the Radio Link Setup procedure and the DRNC shall respond with the RADIO LINK SETUP FAILURE message. If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE nor RL Specific E-DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to May, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to Must Not, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for the first RL and/or [FDD in the RL Specific E-DCH Information IE in the RL Information IE for the first E-DCH RL][TDD in the E-DCH MAC-d Flows Information TDD IE], the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for an HS-DSCH MAC-d Flow in the HS-DSCH MAC-d Flows Information IE, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message. [TDD If ALCAP is not used, if the RADIO LINK SETUP REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for a DSCH in the DSCH TDD Information IE and/or for an USCH in the USCH Information IE, the DRNC shall reject the Radio Link Setup procedure and respond with the RADIO LINK SETUP FAILURE message.]

3GPP

Release 11

81

3GPP TS 25.423 V11.2.0 (2012-06)

If the RADIO LINK SETUP REQUEST message includes the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport bearer intended to be established, the DRNC shall reject the Radio Link Setup procedure and the DRNC shall respond with the RADIO LINK SETUP FAILURE message. If the RADIO LINK SETUP REQUEST message includes an HS-PDSCH RL-ID IE not referring to one of the radio links to be established, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. If the RADIO LINK SETUP REQUEST message contains the HS-DSCH Information IE and if the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. If the RADIO LINK SETUP REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE has the value Indexed MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. If the RADIO LINK SETUP REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE has the value Flexible MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. [FDD If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [TDD If the RADIO LINK SETUP REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE is not present, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the F-DPCH Information IE and the DL DPCH Information IE, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the E-DCH RL Indication IE set to E-DCH, but does not contain the E-DCH FDD Information IE, or if the message contains the E-DCH FDD Information IE, but does not contain the E-DCH RL Indication IE set to E-DCH, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] If the RADIO LINK SETUP REQUEST message contains the HS-PDSCH RL ID IE and the Serving E-DCH RL IE but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not configured to be in the same cell then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. [FDD If the RADIO LINK SETUP REQUEST message contains the HS-PDSCH RL ID IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as HS-DSCH not configured then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the E-DPCH Information IE but does not contain the UL DPDCH Indicator for E-DCH operation IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Serving Cell Change CFN IE, but neither the Serving E-DCH RL IE nor HS-DSCH Information IE is included, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH, but does not contain the Unidirectional DCH indicator IE set to Uplink DCH only in the DCH Specific Info IE for the DCH, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Synchronisation Indicator IE for a RL, but does not contain the D-RNTI IE which already has the RL, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.]

3GPP

Release 11

82

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains the UL DPCCH Slot Format set to 4 but does not contain the F-DPCH Information IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains the UL DPCCH Slot Format set to 0 or 2 and the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the UL DPCH Information IE in the RADIO LINK SETUP REQUEST message contains Diversity Mode IE set to Closed loop mode 1and UL DPCCH Slot Format not set to 2 or 3, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the MIMO Activation Indicator IE, Sixtyfour QAM Usage Allowed Indicator IE set to Allowed, the Additional HS Cell Information RL Setup IE and/or the Single Stream MIMO Activation Indicator IE, but does not contain the HS-DSCH MAC-d PDU Size Format IE set to Flexible MACd PDU Size, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Continuous Packet Connectivity DTX-DRX Information IE but does not contain the F-DPCH Information IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message] [FDD If the RADIO LINK SETUP REQUEST message contains the Serving E-DCH RL ID IE but contains the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information for the new Serving E-DCH RL, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with RL which the transport bearer is configured to be established for the DCH or the E-DCH MAC-d Flow, previously listed in the RADIO LINK SETUP RESPONSE message in the DRNS, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE indicating a seconadry serving cell that is not in the same Node B as the new serving HS-DSCH cell, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message] [FDD If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE and if the HS-DSCH Information IE is not present, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] If the RADIO LINK SETUP REQUEST message includes the DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE set to Flexible RLC PDU Size, and the HSDSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE has the value Indexed MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. If the RADIO LINK SETUP REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, and the DL RLC PDU Size Format IE in the HS-DSCH Information IE has the value Flexible RLC PDU Size, the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message. [FDD If the RADIO LINK SETUP REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE, then the DRNC shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and if the E-DPCH Information IE is not present, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.]

3GPP

Release 11

83

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK SETUP REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD If the RADIO LINK SETUP REQUEST message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Setup IE the Diversity Mode IE not set to None but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to None, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD - If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE containing more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are received in the Ordinal Number Of Frequency IE in the in the HS-DSCH FDD Secondary Serving Information IE, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD - If the RADIO LINK SETUP REQUEST message contains the Additional HS Cell Information RL Setup IE containing more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value 1, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD - If the RADIO LINK SETUP REQUEST message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message with the cause value Invalid CM settings.]

8.3.2 Radio Link Addition

8.3.2.1 General
This procedure is used for establishing the necessary resources in the DRNS for one [FDD or more] additional RLs towards a UE when there is already at least one RL established to the concerned UE via this DRNS. This procedure shall use the signalling bearer connection for the relevant UE Context. The Radio Link Addition procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1. [TDD The Radio Link Addition procedure serves to establish a new Radio Link with the DSCH and USCH included, if they existed before.]

8.3.2.2

Successful Operation
SRNC
RADIO LINK ADDITION REQUEST

DRNC

RADIO LINK ADDITION RESPONSE

Figure 7: Radio Link Addition procedure: Successful Operation The procedure is initiated with a RADIO LINK ADDITION REQUEST message sent from the SRNC to the DRNC. Upon receipt, the DRNS shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. The DRNS shall prioritise resource allocation for the RL(s) to be established according to Annex A.

3GPP

Release 11

84

3GPP TS 25.423 V11.2.0 (2012-06)

If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK ADDITION REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. Transport Channel Handling: [3.84 Mcps TDD The DRNC shall include the UL/DL DPCH Information IE within the UL/DL CCTrCH Information IE for each CCTrCH that requires DPCHs.] [1.28 Mcps TDD The DRNC shall include the UL/DL DPCH Information LCR IE within the UL/DL CCTrCH Information LCR IE for each CCTrCH that requires DPCHs.] [7.68 Mcps TDD The DRNC shall include the UL/DL DPCH Information 7.68 Mcps IE within the UL/DL CCTrCH Information 7.68 Mcps IE for each CCTrCH that requires DPCHs.] [TDD DSCH:] [3.84 Mcps TDD If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a DSCH Information Response IE for each DSCH.] [1.28 Mcps TDD If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a DSCH Information Response LCR IE for each DSCH.] [7.68 Mcps TDD If the radio link to be added includes a DSCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a DSCH Information Response 7.68 Mcps IE for each DSCH.] [TDD USCH:] [3.84 Mcps TDD If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a USCH Information Response IE for each USCH.] [1.28 Mcps TDD If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a USCH Information Response LCR IE for each USCH.] [7.68 Mcps TDD If the radio link to be added includes any USCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a USCH Information Response 7.68 Mcps IE for each USCH.] Physical Channels Handling: [FDD Compressed Mode:] [FDD If the RADIO LINK ADDITION REQUEST message includes the Active Pattern Sequence Information IE, the DRNS shall use the information to activate the indicated (all ongoing) Transmission Gap Pattern Sequence(s) in the new RL. The received CM Configuration Change CFN IE refers to the latest passed CFN with that value. The DRNS shall treat the received TGCFN IEs as follows:] [FDD If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] [FDD If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the DRNS shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.] [FDD For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the DRNS shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]

[FDD If the RADIO LINK ADDITION REQUEST message includes the Active Pattern Sequence Information IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.]

3GPP

Release 11

85

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Active Pattern Sequence Information IE is not included, the DRNS shall not activate the ongoing compressed mode pattern in the new RLs, but the ongoing pattern in the existing RL shall be maintained.] [FDD If some Transmission Gap Pattern sequences using SF/2 method are initialised in the DRNS and the UE Context is configured to use DPCH in the downlink, the DRNC shall include the Transmission Gap Pattern Sequence Scrambling Code Information IE in the DL Code Information IE in the RADIO LINK ADDITION RESPONSE message to indicate the Scrambling code change method that it selects for each channelisation code.] [FDD - If the RADIO LINK ADDITION REQUEST message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.] [FDD DL Code Information:] [FDD When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to PhCH number 1, the second to PhCH number 2, and so on until the pth to PhCH number p.] [TDD CCTrCH Handling:] [TDD If theUL CCTrCH Information IE is present, the DRNS shall configure the new UL CCTrCH(s) according to the parameters given in the message.] [1.28Mcps TDD If the UL CCTrCH Information IE includes the TDD TPC Uplink Step Size IE, the DRNS shall configure the uplink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.] [TDD If the DL CCTrCH Information IE is present, the DRNS shall configure the new DL CCTrCH(s) according to the parameters given in the message.] [TDD If the DL CCTrCH Information IE includes the TDD TPC Downlink Step Size IE, the DRNS shall configure the downlink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.] [FDD - UL CLTD Handling]: [FDD - If the UL CLTD Information IE is present in the RADIO LINK ADDITION REQUEST message, then the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights and then :] [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the C-ID IE shall be included in the UL CLTD Information IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.] [FDD - If there is a HS-DSCH RL configuration in the concerned UE Context, the UL CLTD Activation Information IE shall be included in the UL CLTD Information IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]

General: [FDD The DRNS shall use the provided Uplink SIR Target value as the current target for the inner-loop power control.] Radio Link Handling: Diversity Combination Control: The Diversity Control Field IE indicates for each RL whether the DRNS shall combine the new RL with existing RL(s) or not on the Iur.

3GPP

Release 11 -

86

3GPP TS 25.423 V11.2.0 (2012-06)

If the Diversity Control Field IE is set to May (be combined with another RL), the DRNS shall decide for any of the alternatives. If the Diversity Control Field IE is set to Must, the DRNS shall combine the RL with one of the other RL. When a new RL is to be combined the DRNS shall choose which RL(s) to combine it with. If the Diversity Control Field IE is set to Must not, the DRNS shall not combine the RL with any other existing RL.

[FDD The Diversity Control Field IE is only applicable for DCHs, in case of E-DCH it shall always be assumed to be set to May.] In the case of not combining a RL with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or a RL previously listed in the RADIO LINK ADDITION RESPONSE message, the DRNC shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that no combining is done. In this case the DRNC shall: include in the DCH Information Response IE both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DCH of the RL in the RADIO LINK ADDITION RESPONSE message [FDD for which the Transport Bearer Not Requested Indicator IE was not included]. [FDD include in the RADIO LINK ADDITION RESPONSE the Transport Bearer Not Setup Indicator IE for every DCH or set of co-ordinated DCHs for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK ADDITION REQUEST message.]

[FDD In case of not combining E-DCH, the E-DCH FDD Information Response IE shall be included in the RADIO LINK ADDITION RESPONSE message containing the Binding ID IE and the Transport Layer Address IE for the establishment of transport bearers for every E-DCH MAC-d flow being established for which the Transport Bearer Not Requested Indicator IE was not included.] [FDD In case of not combining E-DCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE the Transport Bearer Not Setup Indicator IE for every E-DCH MAC-d flow for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK ADDITION REQUEST message.] In the case of combining with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, the DRNC shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that the RL is combined. In this case, the RL ID IE indicates (one of) the previously established RL(s) or a RL previously listed in this RADIO LINK ADDITION RESPONSE message with which the new RL is combined and if the ALCAP is not used [FDD and the transport bearer for this DCH is already established], the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. [FDD In the case of combining with an E-DCH RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, one of the previously established RLs or a RL previously listed in this RADIO LINK ADDITION RESPONSE message including the E-DCH FDD Information Response IE and part of the same Radio Link Set shall be regarded as the RL with which the concerned E-DCH RL is combined and if the ALCAP is not used, the Transport Layer Address IE and the Binding ID IE in the RL Specific E-DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. In case E-DCH RL is established for the first time, the DRNC shall include E-DCH FDD Information Response IE instead of using the Diversity Indication of DCH RL in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. It shall include in the E-DCH FDD Information Response IE the Binding ID IE and Transport Layer Address IE for the transport bearers to be established for each E-DCH MAC-d flow of this E-DCH RL for which the Transport Bearer Not Requested Indicator IE was not included.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information RL Add Req IE, then:]

3GPP

Release 11 -

87

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to Separate Iur Transport Bearer Mode the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to UL Flow Multiplexing Mode the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] [FDD if Separate Iur Transport Bearer Mode is used in the new configuration, then:] [FDD the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information IE in the RL Information IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] [FDD If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional EDCH Cell Information Setup IE or in the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH Cell Information Addition IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MAC-d flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE for establishment of the transport bearer.]

[TDD The DRNC shall always include in the RADIO LINK ADDITION RESPONSE message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DSCH and USCH of the RL.] In the case of a set of co-ordinated DCHs, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and the Transport Layer Address IE for only one of the DCHs in the set of co-ordinated DCHs [FDD for which the Transport Bearer Not Requested Indicator IE was not included]. If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Allowed UL Rate IE in the DCH Information Response IE for this Radio Link. If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) when starting to utilise a new Radio Link, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Allowed DL Rate IE in the DCH Information Response IE for this Radio Link. [FDD Transmit Diversity:] [FDD The DRNS shall activate any feedback mode diversity according to the received settings.] [FDD If the cell in which the RL is being added is capable to provide Close loop Tx diversity, the DRNC shall indicate the Closed loop timing adjustment mode of the cell by including the Closed Loop Timing Adjustment Mode IE in the RADIO LINK ADDITION RESPONSE message.] [FDD When the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE is present the DRNS shall activate/deactivate the Transmit Diversity for each new Radio Link and/or secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE using the diversity mode of the existing Radio Link(s) and/or existing secondary serving HS-DSCH Radio Link.] DL Power Control:

3GPP

Release 11

88

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Primary CPICH Ec/No IE or the Primary CPICH Ec/No IE and the Enhanced Primary CPICH Ec/No IE measured by the UE are included for an RL in the RADIO LINK ADDITION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this RL. If the Primary CPICH Ec/No IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.] [TDD If [3.84Mcps TDD and 7.68 Mcps TDD the DL Time Slot ISCP Info IE] [1.28Mcps TDD the DL Time Slot ISCP Info LCR IE] is included in the RADIO LINK ADDITION REQUEST message, the DRNS shall use it in the calculation of the Initial DL TX Power.] [TDD If the Primary CCPCH RSCP Delta IE is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included and the Primary CCPCH RSCP IE is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP IE. The DRNS shall use it in the calculation of the Initial DL TX Power.] [TDD If the Primary CCPCH RSCP IE, Primary CCPCH RSCP Delta IE, [3.84Mcps TDD and 7.68 Mcps TDD and the DL Time Slot ISCP Info IE] [1.28Mcps TDD and the DL Time Slot ISCP Info LCR IE] are not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CCPCH power used by the existing RL.] [FDD The Initial DL TX Power shall be applied until UL synchronisation is achieved on the Uu interface for that RLS or Power Balancing is activated. No inner loop power control or power balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10] subclause 5.2.1.2) and the power control procedure (see 8.3.7).] [TDD The Initial DL TX Power shall be applied until UL synchronisation is achieved on the Uu interface for that RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.224 [22] subclause 4.2.3.3).] [3.84 Mcps TDD and 7.68 Mcps TDD The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK ADDITION RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the value(s) for that CCTrCH in the CCTrCH Maximum DL TX Power IE and CCTrCH Minimum DL TX Power. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE/CCTrCH Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE on any DL DPCH within each CCTrCH of the RL.] [1.28 Mcps TDD The DL TX power upper and lower limit is configured in the following way: The DRNC shall include the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK ADDITION RESPONSE message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the value(s) for that timeslot in the Maximum DL TX Power IE and Minimum DL TX Power within the DL Timeslot Information LCR IE. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE on any DL DPCH within each timeslot of the RL.] [FDD If the DPC Mode IE is present in the RADIO LINK ADDITION REQUEST message, the DRNC shall apply the DPC mode indicated in the message, and be prepared that the DPC mode may be changed during the lifetime of the RL. If the DPC Mode IE is not present in the RADIO LINK ADDITION REQUEST message, DPC mode 0 shall be applied (see TS 25.214 [10]).] The DRNC shall provide the configured Maximum DL TX Power IE and Minimum DL TX Power IE for every new RL to the SRNC in the RADIO LINK ADDITION RESPONSE message. The DRNS shall not transmit with a power higher than indicated by the Maximum DL TX Power IE or lower than indicated by the Minimum DL TX Power IE on any DL DPCH [FDD or on the F-DPCH] of the RL [FDD except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the Pcurr, as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL

3GPP

Release 11

89

3GPP TS 25.423 V11.2.0 (2012-06)

Reference Power IE, the DRNS shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported by the DRNS, according to subclause 8.3.15. In this case, the DRNC shall include the DL Power Balancing Activation Indicator IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level which is calculated based on the Primary CPICH Ec/No IE or the Enhanced Primary CPICH Ec/No IE (if received), or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing RLs.] UL Power Control: The DRNC shall also provide the configured UL Maximum SIR and UL Minimum SIR for every new RL to the SRNC in the RADIO LINK ADDITION RESPONSE message. These values are taken into consideration by DRNS admission control and shall be used by the SRNC as limits for the UL inner-loop power control target. Neighbouring Cell Handling: If there are UMTS neighbouring cell(s) to the cell in which a Radio Link was established then: The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Neighbouring FDD Cell Information IE and/or Neighbouring TDD Cell Information IE in the Neighbouring UMTS Cell Information IE for each neighbouring FDD cell and/or TDD cell respectively. In addition, if the information is available, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Frame Offset IE, Primary CPICH Power IE, Cell Individual Offset IE, STTD Support Indicator IE, Closed Loop Mode1 Support Indicator IE, Coverage Indicator IE, Antenna Co-location Indicator IE and HCS Prio IE in the Neighbouring FDD Cell Information IE, and the Frame Offset IE, Cell Individual Offset IE, DPCH Constant Value IE and the PCCPCH Power IE, Coverage Indicator IE, Antenna Colocation Indicator IE and HCS Prio IE in the Neighbouring TDD Cell Information IE or the Neighbouring TDD Cell Information LCR IE. If the Neighbouring TDD Cell Information IE includes the Sync Case IE set to Case1, the DRNC shall include the Time SlotFor SCH IE in the Neighbouring TDD Cell Information IE. If the Neighbouring TDD Cell Information IE includes the Sync Case IE set to Case2, the DRNC shall include the SCH Time Slot IE in the Neighbouring TDD Cell Information IE. If a UMTS neighbouring cell is not controlled by the same DRNC, the DRNC shall also include in the RADIO LINK ADDITION RESPONSE message the CN PS Domain Identifier IE and/or CN CS Domain Identifier IE which are the identifiers of the CN nodes connected to the RNC controlling the UMTS neighbouring cell. [FDD The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the DPC Mode Change Support Indicator IE for each neighbour cell in the Neighbouring FDD Cell Information IE if this information is available.] The DRNC shall include the Cell Capability Container FDD IE, the Cell Capability Container TDD IE, Cell Capability Container 7.68Mcps TDD IE, the Cell Capability Container TDD LCR IE and/or the Cell Capability Container Extension FDD IE if the DRNC is aware that the neighbouring cell supports any functionality listed in 9.2.2.D, 9.2.3.1a, 9.2.3.1b and 9.2.2.123. [FDD The DRNC shall, if supported, include the Cell List Validity Indicator IE if the neighbouring cell is multi cell capable and/or dual band capable but the cell can not be the serving HS-DSCH in a multicell and/or dual band configuration. Hence the cell can only serve as the secondary serving HS-DSCH cell. When Cell List Validity Indicator IE is included the SRNC should ignore the indicated cell list(s).] [FDD For each cell in the Secondary Serving Cell List IE that is Multi Cell E-DCH capable, indicated in the Cell Capability Container Extension FDD IE by the "Multi Cell E-DCH Support Indicator" bit = "1", and is restricted for use as an Additional E-DCH on the secondary uplink frequency with the cell identified by the C-ID IE as the corresponding cell of the Primary uplink frequency, the DRNS shall, if supported, include the Multicell E-DCH Restriction IE set to "TRUE".] For the UMTS neighbouring cells which are controlled by the DRNC, the DRNC shall report in the RADIO LINK ADDITION RESPONSE message the restriction state of those cells, otherwise Restriction State Indicator IE may be absent. The DRNC shall include the Restriction State Indicator IE for the

3GPP

Release 11

90

3GPP TS 25.423 V11.2.0 (2012-06)

neighbouring cells which are controlled by the DRNC in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If available, the DRNC shall include the SNA Information IE for the concerned neighbouring cells in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If MOCN or GWCN network sharing configuration is used then the DRNC shall include the broadcasted PLMN identities of concerned neighbouring cells in the Multiple PLMN List IE in the Neighbouring FDD Cell Information IE, the Neighbouring TDD Cell Information IE and the Neighbouring TDD Cell Information LCR IE. If available, the DRNC shall include the Frequency Band Indicator IE for the concerned neighbouring cells in the Neighbouring FDD Cell Information IE. If the number of neighbouring UMTS RNCs is beyond the predefined maximum number, the DRNC shall, if supported, include the remaining neighbouring information in the Neighbouring UMTS Cell Information Extension IE. The IE filling rules in the Neighbouring UMTS Cell Information shall also apply to the Neighbouring UMTS Cell Information Extension IE.

If there are GSM neighbouring cells to the cell(s) in which a radio link is established, the DRNC shall include the Neighbouring GSM Cell Information IE in the RADIO LINK ADDITION RESPONSE message for each of the GSM neighbouring cells. If available the DRNC shall include the Cell Individual Offset IE, and if the Cell Individual Offset IE alone cannot represent the value of the offset, the DRNC shall also include the Extended GSM Cell Individual Offset IE in the Neighbouring GSM Cell Information IE. If available the DRNC shall also include the Coverage Indicator IE, Antenna Co-location Indicator IE and HCS Prio IE in the Neighbouring GSM Cell Information IE. If available, the DRNC shall also include the SNA Information IE for the concerned neighbouring cells in the Neighbouring GSM Cell Information IE. When receiving the SNA Information IE in the RADIO LINK ADDITION RESPONSE message, the SRNC should use it to restrict cell access based on SNA information. See also TS 25.401 [40] for a broader description of the SNA access control. If there are GERAN neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include the GERAN Cell Capability IE in the Neighbouring GSM Cell Information IE that is included in the RADIO LINK ADDITION RESPONSE message for each of the GERAN cells. If there are GERAN Iu-mode neighbouring cells to the cell(s) where a radio link is established, the DRNC shall include, if available, the GERAN Classmark IE in the Neighbouring GSM Cell Information IE that is included in the RADIO LINK ADDITION RESPONSE message for each of the GERAN Iu-mode neighbouring cells. TS 43.051 [39] defines when the transmission of the GERAN Classmark IE will be required at the initiation of the Relocation Preparation procedure. If there are E-UTRA neighbouring cells to the cell(s) in which a radio link is established, the DRNC shall include the Neighbouring E-UTRA Cell Information IE in the RADIO LINK ADDITION RESPONSE message for each of the E-UTRA neighbouring cells. [1.28Mcps TDD Uplink Synchronisation Parameters LCR:] [1.28Mcps TDD If the Uplink Synchronisation Parameters LCR IE is present, the DRNC shall use the indicated values of Uplink synchronisation stepsize IE and Uplink synchronisation frequency IE when evaluating the timing of the UL synchronisation.] [1.28Mcps TDD Shared physical channels Synchronisation Detection:] [1.28Mcps TDD If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the Out-of-sync Detection Window IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITON RESPONSE message.] [1.28Mcps TDD Uplink Timing Advance Control LCR:] [1.28Mcps TDD The DRNC shall include the Uplink Timing Advance Control LCR IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD PowerControl GAP:]

3GPP

Release 11

91

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD If applied in the DRNS, the DRNC may include the PowerControl GAP IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD E-UTRAN Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the Idle Interval Configuration Indicator IE, if supported, the DRNC shall include the Idle Interval Information IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD Inter-frequency/ Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK ADDTION REQUEST message includes the DCH Measurement Type indicator IE, if supported, the DRNS shall include the Measurement purpose IE and the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE in the RADIO LINK ADDTION RESPONSE message to configure the measurement occasion pattern(s) indicated by the DCH Measurement Type indicator IE.] MBMS Handling: If the UE Link is currently stored in the UE Context and an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in some of the cells identified by the C-ID IEs in the RADIO LINK ADDITION REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the Active MBMS Bearer Service List IE the Transmission Mode IE in the concerned RL Information Response IEs in the RADIO LINK ADDITION RESPONSE message. If the UE Link is currently stored in the UE Context and an MBMS preferred frequency layer for some active MBMS bearer services contained in the UE Link is set in some of the cells identified by the C-ID IEs in the RADIO LINK ADDITION REQUEST message, the DRNC shall include for each of these active MBMS bearer services in the Active MBMS Bearer Service List IE the Preferred Frequency Layer IE in the concerned RL Information Response IEs in the RADIO LINK ADDITION RESPONSE message. [FDD HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE for a Radio Link not indicated by the HS-PDSCH RL ID IE in the HSDSCH Serving Cell Change Information IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [63]:] [FDD The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-ID Iesin the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message. ] [FDD The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ] [FDD by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell] [FDD by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]

[FDD If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ] [FDD The DRNS shall return these codes in the Sets of HS-SCCH Codes IE along with the corresponding per- cell HS-DSCH-RNTI IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message. ] [FDD The DRNS shall use the first in the numbered list the primary serving HS-DSCH cells of HSSCCH codes in the HS-SCCH Preconfigured Codes IE sent to the SRNC to signal the Target Cell HSSCCH Order defined in TS 25.331 [16]].

3GPP

Release 11 -

92

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD The DRNS shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:] [FDD if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE] [FDD if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the Pilot Configuration and MIMO N/M Ratio in MIMO Information Response IE] [FDD if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used for the cell in the preconfiguration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell.] [FDD if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell] [FDD if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE] [FDD if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS shall store this information in the preconfigured configuration.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.] [FDD the SixtyfourQAM DL Support Indicator IE may be included] [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS may store this information in the preconfigured configuration.] [FDD the DRNS shall, if supported, include in the Sets of HS-SCCH Codes IE the Measurement Power Offset IE for each preconfigured cell.]

[FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where HS-DSCH / secondary HS-DSCH is preconfigured, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH Preconfiguration Info IE or in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE for each preconfigured cell in the RADIO LINK ADDITION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD The DRNS shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.] [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

3GPP

Release 11

93

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the DRNS shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information IE containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:] [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE. ] [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

[FDD If the RADIO LINK ADDITION REQUEST message includes the Non-Serving RL Preconfiguration Setup IE in the RL Information IE and:] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL EDCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.] [FDD if the choice of new Serving RL is "New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving E-DCH FDD DL Control Channel Information B IE and/or the New nonserving E-DCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New nonserving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional EDCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.] General: If the RADIO LINK ADDITION REQUEST message includes the RL Specific DCH Information IE, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD for which the Transport Bearer Not Requested Indicator IE was not included]. [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer shall not be Established for a DCH, then the DRNC shall not establish a transport bearer for the concerned DCH and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for a DCH and:] [FDD if the DRNC establishes a transport bearer for the concerned DCH, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH being established.]

3GPP

Release 11 -

94

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD if the DRNC does not establish a transport bearer for the concerned DCH, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]

Depending on local configuration in the DRNS, the DRNC may include in the RADIO LINK ADDITION RESPONSE message the UTRAN Access Point Position IE and the geographical co-ordinates of the cell, represented either by the Cell GAI IE or by the Cell GA Additional Shapes IE. If the DRNC includes the Cell GA Additional Shapes IE in the RADIO LINK ADDITION RESPONSE message, it shall also include the Cell GAI IE. For each Radio Link established in a cell in which at least one URA Identity is being broadcast, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message a URA Information for this cell including the URA ID IE, the Multiple URAs Indicator IE indicating whether or not multiple URA Identities are being broadcast in the cell, and the RNC-ID IEs of all other RNCs that have at least one cell within the URA identified by the URA ID IE. [3.84Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response IE or USCH Information Response IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info TDD IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response IE or USCH Information Response IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [1.28 Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response LCR IE or USCH Information Response LCR IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response LCR IE or USCH Information Response LCR IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [7.68 Mcps TDD The DRNC shall include the Secondary CCPCH Info 7.68 Mcps TDD IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response 7.68 Mcps IE or USCH Information Response 7.68 Mcps IE is included in the message and at least one DCH is configured for the radio link. The DRNC shall also include the Secondary CCPCH Info 7.68 Mcps TDD IE in the RADIO LINK ADDITION RESPONSE message if at least one DSCH Information Response 7.68 Mcps IE or USCH Information Response 7.68 Mcps IE is included in the message and the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] If the Permanent NAS UE Identity IE is present in the RADIO LINK ADDITION REQUEST message, the DRNS shall store the information for the considered UE Context for the lifetime of the UE Context. If the RADIO LINK ADDITION REQUEST message includes a C-ID IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is available in the DRNC for the considered UE Context, the DRNC shall use this information to determine whether it can add the Radio Link on this cell or not. If the HCS priority information is available in the DRNS, it shall include the HCS Prio IE for each of the established RLs in the RADIO LINK ADDITION RESPONSE message. The DRNS shall start receiving on the new RL(s) after the RLs are successfully established. [FDD If the RADIO LINK ADDITION REQUEST message includes the Initial DL DPCH Timing Adjustment Allowed IE, then the DRNS may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the DRNS shall include, for the concerned Radio Link(s), the Initial DL DPCH Timing Adjustment IE in the Radio Link Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Synchronisation Indicator IE, set to Timing Maintained Synchronisation, the DRNS shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10]. The DRNS shall select the TPC pattern as if first RLS indicator is set to first RLS according to subclause 5.1.2.2.1.2 in TS 25.214 [10].]

3GPP

Release 11

95

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the UE Context is configured for F-DPCH Slot Format operation, then the DRNS shall include the F-DPCH Slot Format IE in the RADIO LINK ADDITION RESPONSE message.] [FDD - If the RADIO LINK ADDITION REQUEST message includes the F-TPICH Information IE in the RL Information IE, the DRNS shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] [FDD Radio Link Set Handling:] [FDD For each RL not having a common generation of the TPC commands in the DL with another RL, the DRNS shall assign to the RL a unique value for the RL Set ID IE which uniquely identifies the RL as an RL Set within the UE Context. In case of E-DCH, the generation of E-HICH information for RLs in different RL Sets shall not be common.] [FDD For all RLs having a common generation of the TPC commands in the DL with another new or existing RL, the DRNS shall assign to each RL the same value for the RL Set ID IE which uniquely identifies these RLs as members of the same RL Set within the UE Context. In case of E-DCH, the generation of EHICH related information for all RLs in a RL Set shall be common.] [FDD After addition of the new RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the previously existing and newly established RL Set(s), use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.] [FDD For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the E-DCH RL Set ID IE in the RADIO LINK ADDITION RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.] [FDD Serving HS-DSCH Radio Link Change:] [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE, then the HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:] [FDD In the new configuration the DRNS shall allocate the HS-PDSCH resources for the new Serving HSPDSCH Radio Link.] [FDD The DRNS may include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [FDD If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HSDSCH Information Response IE.] [FDD The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If a reset of the MAC-hs is not required the DRNS shall include the MAC-hs Reset Indicator IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

3GPP

Release 11 -

96

3GPP TS 25.423 V11.2.0 (2012-06)

If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. [FDD If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity HSSCCH less Information IE, then:] - [FDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for Continuous Packet Connectiviy HS-SCCH less operation according to TS 25.214 [10].] - [FDD The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK ADDITION RESPONSE message.] - [FDD If at least one of HS-PDSCH Second Code Support IE is set to True, then the DRNC shall include HS-PDSCH Second Code Index IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity DTX-DRX Information IE, then:] - [FDD The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].] - [FDD If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

[FDD - If the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the HSDSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:] [FDD If the HS-DSCH Information IE is present in the HS-DSCH Serving Cell Change Information IE, then:] [FDD The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.] [FDD the HS-DSCH Information IE defines the new HS-DSCH configuration in the DRNS to be used on the new HS-DSCH Radio Link.] [FDD The DRNC shall include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HSDSCH Information IE.] [FDD The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.] [FDD If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE,

3GPP

Release 11

97

3GPP TS 25.423 V11.2.0 (2012-06)

then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.] [FDD The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK ADDITION REQUEST message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to Flexible MAC-d PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]).] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then ] [FDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] [FDD The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.]

3GPP

Release 11 -

98

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may use:] [FDD a different HS-SCCH in consecutive TTIs for this UE] [FDD HS-SCCH orders for the case of HS-SCCH-less operation to this UE]

[FDD If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the D shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HSDSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].] [FDD If the RADIO LINK ADDITION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall, if supported, consider the data of the HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.]

[FDD The DRNC may include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HSPDSCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC. ] [FDD If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.] [FDD If the requested Serving HS-DSCH Radio Link Change was successful or unsucessful, the DRNS shall indicate this in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD Secondary Serving HS-DSCH Radio Link Change:] [FDD If the RADIO LINK ADDITION REQUEST message includes the Additional HS Cell Information RL Addition IE, then the HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:] [FDD In the new configuration the DRNS shall allocate the HS-PDSCH resources for the new secondary serving HS-PDSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]

3GPP

Release 11 -

99

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD - If the UE Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for the secondary serving HS-DSCH Transport Block Size signalling.] [FDD Secondary Serving HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:] [FDD The DRNS shall setup the requested HS-PDSCH resources on the Secondary Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.] [FDD The HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HSDSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HSDSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

3GPP

Release 11 -

100

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If Sixtyfour QAM will not be used for the secondary serving cell, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.] [FDD If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE in the RADIO LINK ADDITION REQUEST message the DRNS shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to None the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]

[FDD If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the HS-PDSCH resources of the old secondary serving HS-PDSCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC. ] [FDD If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new secondary serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous secondary serving HS-PDSCH Radio Link.] [FDD If the requested secondary serving HS-DSCH Radio Link Change was successful or unsuccessful, the DRNS shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD Additional Serving E-DCH Radio Link Change:] [FDD If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information Addition IE in the Additional E-DCH Cell Information RL Add Req IE and the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Addition IE, the HS-PDSCH RL ID IE indicates the new Additional Serving EDCH Radio Link:] [FDD In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving EDCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] [FDD If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

3GPP

Release 11 -

101

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional EDCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE] [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional EDCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other EDCH Radio Links in the DRNS Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.] [FDD- If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link, and shall keep active the resources that are allocated for the previous additional serving E-DCH Radio Link.] [FDD If the addition of the requested Additional Serving E-DCH Radio Link was successful but the Additional Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD E-DCH:] [FDD If the RADIO LINK ADDITION REQUEST message contains the E-DCH RL Indication IE, set to EDCH,in the RL Information IE, then for every such RL.] [FDD The DRNS shall setup the E-DCH resources as configured in the UE context.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the RL specific E-DCH Information IE for an E-DCH MAC-d flow, then if the Transport Bearer Not Requested Indicator IE is not included for this E-DCH MAC-d flow, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.] [FDD The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for every E-DCH MAC-d flow being established for which the Transport Bearer Not Requested Indicator IE was not included.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer Shall not be Established for an E-DCH MAC-d flow, then the DRNC shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for an E-DCH MAC-d flow and:] - [FDD if the DRNC establishes a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]

3GPP

Release 11

102

3GPP TS 25.423 V11.2.0 (2012-06)

- [FDD if the DRNC does not establish a transport bearer for the concerned E-DCH MAC-d flow, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.] [FDD The DRNC may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNC may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message, for every RL indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the E-DCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.]

[FDD Serving E-DCH Radio Link Change:] [FDD If the RADIO LINK ADDITION REQUEST message contains the Serving E-DCH RL IE, this indicates the new Serving E-DCH Radio Link:] [FDD If the new Serving E-DCH RL is in this DRNS:] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both and include these E-RNTI identifiers and the Channelisation Code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE for the indicated RL in the RADIO LINK ADDITION RESPONSE message.] - [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the new serving E-DCH RL.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] - [FDD If a serving cell change is performed the RADIO LINK ADDITION RESPONSE message may contain invalid data (see 9.2.2.4C).] - [FDD The DRNS may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK ADDITION RESPONSE message for the new serving E-DCH RL.] [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Link in the DRNS Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE.] [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC, or earlier. In this case, in the new configuration the DRNS shall, if applicable, de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link. The DRNS shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]

3GPP

Release 11 -

103

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD- If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new serving E-DCH Radio Link, and shall keep active the resources that are allocated for the previous serving E-DCH Radio Link.] [FDD If the addition of the requested Serving E-DCH Radio Link was successful but the Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD E-DPCH Handling:] [FDD If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE it defines the new E-DPCH configuration in the DRNS to be used on the new E-DCH Radio Link and the DRNS shall use the new parameters for the related resource allocation operations.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the DRNS shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the DRNS shall use the value 127 in the algorithm defined in TS 25.214 [10].] [FDD If the E-DPCH Information IE includes the E-TFCS Information IE, the DRNS shall use the E-TFCS Information IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the E-TFCS Information IE contains the E-DCH Minimum Set E-TFCI Validity Indicator IE the DRNS shall ignore the value in E-DCH Minimum Set E-TFCI IE. If the E-DCH Minimum Set E-TFCI validity indicator IE is absent DRNS shall use the value for the related resource allocation operation.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the EDPDCH Power Interpolation IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].] [FDD If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE, which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the DRNS shall use the value to determine the applicable minimum gain factor (ed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ] [FDD E-DCH Setup on a new Radio Link:] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message then:] [FDD the E-DCH FDD Information IE defines the new E-DCH FDD configuration in the DRNS to be used on the new E-DCH Radio Link.] [FDD If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK ADDITION REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, then the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If the RADIO LINK ADDITION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.]

3GPP

Release 11 -

104

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume nonscheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.] [FDD If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.] [FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [FDD If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Bundling Mode Indicator IE for a EDCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Reference Power Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The EAGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK ADDITION REQUEST message includes the SixteenQAM UL Operation Indicator IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.] [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]

[FDD Additional E-DCH Setup:]

3GPP

Release 11

105

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is Setup, then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:] [FDD If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup] - [FDD The DRNS shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.] [FDD If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the Additional E-DCH shall be setup.] - [FDD The DRNS shall setup the Additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE] [FDD The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific EDPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.] [FDD If the UL SIR Target IE in the UL DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE and/or the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE are present, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] [FDD If the Initial DL Tx Power IE, the Primary CPICH Ec/No IE, the E-AGCH Power Offset IE, the ERGCH Power Offset IE and/or the E-HICH Power Offset IE, is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the Enhanced Primary CPICH Ec/No IE is included in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH Secondary RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] If the F-DPCH Slot Format Support Request IE in the F-DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the FDPCH Slot Format IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message. If the Multicell EDCH Information IE in the Additional E-DCH FDD Setup Information IE includes the F-DPCH Slot Format IE, the DRNS may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.] [FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Processing Overload Level IE are present in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If activation of power balancing for the Additional E-DCH RL by the RADIO LINK ADDITION REQUEST message is supported by the DRNS, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

3GPP

Release 11 -

106

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the DRNS may include the E-AGCH And E-RGCH/EHICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message and if DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding EAGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.] - [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional EDCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message the the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant E-DCH FDD Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK ADDITION RESPONSE message.] - [FDD If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the DRNS shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the SRNC. If the Serving Cell Change CFN IE is not included then the DRNS shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link]

[FDD If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RL Add IE RADIO LINK ADDITION RESPONSE message.] [FDD If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Secondary CPICH Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message. If the DRNS doesnt include the Secondary CPICH Information IE, it shall

3GPP

Release 11

107

3GPP TS 25.423 V11.2.0 (2012-06)

not include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used.] [FDD Additional E-DCH RL Addition:] [FDD If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is Addition, then the Additional E-DCH Cell Information Addition IE defines the new configuration and then:] [FDD The DRNS shall setup the requested E-DCH resources as requested, or as configured in the UE context , on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Add IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] [FDD if the Multicell E-DCH Information IE is included and contains the Minimum Reduced E-DPDCH Gain Factor IE, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.] [FDD if the Additional E-DCH FDD Information IE is included and contains the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Processing Overload Level IE, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.] [FDD If the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE is included in the Additional E-DCH RL Specific Information To Add IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing Additional E-DCH RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE in the Multicell E-DCH RL Specific Information IE in the Additional EDCH RL Specific Information To Add IE, the DRNS shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.15. In this case, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level which is calculated based on the following IEs in the Additional E-DCH RL Specific Information To Add IE (if received): Primary CPICH Ec/No IE or the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set the same value for the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE the DRNS may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-

3GPP

Release 11

108

3GPP TS 25.423 V11.2.0 (2012-06)

RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message and if DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD If in the Additional E-DCH RL Specific Information To Add IE the Primary CPICH Ec/No IE or the Primary CPICH Ec/No IE and the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE measured by the UE are included for an RL in the RADIO LINK ADDITION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the Primary CPICH Ec/No IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]

[TDD HS-DSCH Setup:] [TDD If the HS-DSCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then:] [TDD The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.] [TDD The DRNC shall include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [TDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). ] [TDD The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [TDD The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK ADDITION RESPONSE message.] [TDD The DRNC shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.] [TDD If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the HS-DSCH Information IE for an HS-DSCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow.] [TDD If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.] [TDD If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.] [TDD If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNC shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.] [TDD If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC

3GPP

Release 11

109

3GPP TS 25.423 V11.2.0 (2012-06)

PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32].] [TDD The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK ADDITION REQUEST message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to Flexible MAC-d PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.] [TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link. The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD If the UE TS0 Capability LCR IE is included in the HS-DSCH TDD Information IE, then the DRNC may include the TS0 HS-PDSCH Indication LCR IE in the RADIO LINK ADDITION RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]

[TDD Intra-Node B Serving HS-DSCH Radio Link Change:] [TDD If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link:] [TDD The DRNC shall include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[TDD E-DCH:] [3.84Mcps TDD, 1.28Mcps TDD and 7.68Mcps TDD If the [3.84Mcps TDD E-DCH Information IE][1.28Mcps TDD E-DCH Information 1.28Mcps IE] [7.68Mcps TDD E-DCH Information 7.68Mcps IE] is present in the RADIO LINK ADDITION REQUEST message:] [TDD The DRNS shall setup the requested E-DCH resources on the Radio Link indicated by the E-DCH Serving RL IE.] [TDD If the TNL QoS IE is included in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [TDD If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow, then the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.] [TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flows Information TDD IE, the DRNS shall use this information for the related resource allocation operation.]

3GPP

Release 11 -

110

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to Non-scheduled for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants are configured for that E-DCH MAC-d flow.] [TDD If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to Scheduled the DRNS shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.] [TDD If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions for the related queue.] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for EDCH scheduling.] [TDD If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [3.84Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate IE in the E-DCH TDD Information IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [7.68Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE in the E-DCH TDD Information 7.68Mcps IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [3.84Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [7.68Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information 7.68Mcps IE, then if the DRNS could not decode the EPUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE in the E-DCH TDD Information LCR IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [TDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B.] [TDD If the RADIO LINK ADDITION REQUEST message includes the [3.84Mcps TDD E-DCH TDD Information IE][1.28Mcps TDD E-DCH TDD Information LCR IE] in the E-DCH MAC-d Flows Information TDD IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE in the E-DCH TDD Information LCR IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]

3GPP

Release 11 -

111

3GPP TS 25.423 V11.2.0 (2012-06)

[3.84Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information TDD IE in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [3.84Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the EAGCH(s) assigned in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information LCR TDD IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier, the EAGCH(s) and E-HICH(s) assigned in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK ADDITION RESPONSE message.] [7.684Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK ADDITION RESPONSE message.] [7.68Mcps TDD The DRNS shall allocate an E-RNTI identifier and include the E-RNTI identifier and the EAGCH(s) assigned in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK ADDITION RESPONSE message.] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the Multi-Carrier E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present and if the RADIO LINK ADDITION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]

[3.84Mcps TDD Intra-Node B Serving E-DCH Radio Link Change:] [3.84Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:] [3.84Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[1.28Mcps TDD Intra-Node B Serving E-DCH Radio Link Change:] [1.28Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:] [1.28Mcps TDD The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE and the E-HICH Specific Information Response IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK ADDITION RESPONSE message.]

[7.68Mcps TDD Intra-Node B Serving E-DCH Radio Link Change:] [7.68Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:] [7.68Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response 7.68Mcps TDD IE in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK ADDITION RESPONSE message.]

[1.28 Mcps TDD Continuous Packet Connectivity Handling:] [1.28 Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS shall take account into these parameters to decide the DRX operation related

3GPP

Release 11

112

3GPP TS 25.423 V11.2.0 (2012-06)

parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].] [1.28 Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK ADDITON RESPONSE message.] [1.28 Mcps TDD The DRNS shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD The DRNS shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK ADDITION RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall apply this information for HSDSCH Semi-Persistent scheduling operation.]

[1.28 Mcps TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK ADDITON RESPONSE message.] [1.28 Mcps TDD If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH SemiPersistent scheduling Information LCR IE, then the DRNS shall apply this information for E-DCH SemiPersistent scheduling operation.]

[1.28 Mcps TDD Multi-Carrier E-DCH:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Multi-Carrier E-DCH Information IE defines the new configuration and then:] [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequecies indicated by the the Multi-Carrier E-DCH Information LCR IE.] [1.28Mcps TDD - The DRNS shall use the corresponding PRXdes_base IE for power control on each uplink frequency according to TS 25.331 [16].] [1.28Mcps TDD - If the SNPL Carrier Group Indicator IE is present in the Multi-Carrier E-DCH Information LCR IE, the DRNS shall use the information to determine which SNPL Carrier Group each frequency indicated by the UARFCN IE belongs to.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iur transport bearer mode", the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]

3GPP

Release 11 -

113

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "E-DCH UL flow multiplexing mode", the DRNS shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iur transport bearer.] [1.28Mcps TDD - If the Separate Iur transport bearer mode is used in the new configuration, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response 1.28Mcps IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

[1.28 Mcps TDD - MU-MIMO Handling:] [1.28Mcps TDD - If the RADIO LINK ADDITION REQUEST message includes the MU-MIMO Indicator IE, then:] [1.28 Mcps TDD the DRNS may use the MU-MIMO for the radio link according to the MU-MIMO Usage Indicator IE and shall include the MU-MIMO Information IE in the RADIO LINK SETUP RESPONSE message.] [1.28 Mcps TDD If the Standalone Midamble Channel Indicator IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK ADDITION RESPONSE message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK ADDITION RESPONSE message.

Response message: If all requested RLs are successfully added, the DRNC shall respond with a RADIO LINK ADDITION RESPONSE message. After sending the RADIO LINK ADDITION RESPONSE message the DRNS shall continuously attempt to obtain UL synchronisation on the Uu interface. For each RL for which the Delayed Activation IE is not included in the RADIO LINK ADDITION REQUEST message the DRNS shall: [FDD start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4].] [TDD start transmission on the new RL immediately as specified in TS 25.427 [4].]

For each RL for which the Delayed Activation IE is included in the RADIO LINK ADDITION REQUEST message, the DRNS shall: if the Delayed Activation IE indicates Separate Indication: - not start any DL transmission for the concerning RL on the Uu interface; if the Delayed Activation IE indicates CFN: - [FDD start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [4], however never before the CFN indicated in the Activation CFN IE.] [TDD start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [4].]

[1.28 Mcps TDD if the DRNS assigns one or more PLCCH sequence numbers to the radio link, then the PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK ADDITION RESPONSE message.]

3GPP

Release 11

114

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.2.3

Unsuccessful Operation
SRNC
RADIO LINK ADDITION REQUEST

DRNC

RADIO LINK ADDITION FAILURE

Figure 8: Radio Link Addition procedure: Unsuccessful Operation If the establishment of at least one RL is unsuccessful, the DRNC shall respond with a RADIO LINK ADDITION FAILURE message. DRNC shall include in the RADIO LINK ADDITION FAILURE message a general Cause IE or a Cause IE for each failed radio link. The Cause IE indicates the reason for failure. [FDD If some RL(s) were established successfully, the DRNC shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as in the RADIO LINK ADDITION RESPONSE message.] [FDD If the requested Serving HS-DSCH Radio Link Change was successful, or if the addition of the requested serving HS-DSCH Radio Link was successful or existed already but the Serving HS-DSCH Radio Link change was unsuccessful, the DRNS shall indicate this in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message] [FDD If the requested secondary serving HS-DSCH Radio Link Change was successful, or if the addition of the requested secondary serving HS-DSCH Radio Link was successful or existed already but the secondary serving HSDSCH Radio Link change was unsuccessful, the DRNS shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK ADDITION FAILURE message.] [FDD If the requested Serving E-DCH Radio Link Change was successful, or if the addition of the requested serving E-DCH Radio Link was successful or existed already but the Serving E-DCH Radio Link change was unsuccessful, the DRNS shall indicate this in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.] [FDD If the MIMO Activation Indicator IE is included and the Power Offset For S-CPICH for MIMO Request Indicator IE is not included in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE in the RADIO LINK ADDITION REQUEST message or the power offset for S-CPICH for MIMO Request indicator has not been configured in the UE Context but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link shall be reported as failed and the DRNC shall include in the RADIO LINK ADDITION FAILURE message the Cause IE.] [FDD If the requested additional serving E-DCH Radio Link Change was successful, or if the addition of the requested additional serving E-DCH Radio Link was successful or existed already but the additional serving E-DCH Radio Link change was unsucessful, the DRNS shall indicate this in the Additional E-DCH Secondary Serving Cell Change Information Response IE in the Additional E-DCH Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.] Typical cause values are: Radio Network Layer Causes: DL Radio Resources not Available; UL Radio Resources not Available; Combining Resources not Available; Combining not Supported Cell not Available; [FDD Requested Tx Diversity Mode not Supported;] Power Level not Supported; CM not Supported; Reconfiguration CFN not Elapsed; Number of DL Codes not Supported;

3GPP

Release 11

115

3GPP TS 25.423 V11.2.0 (2012-06)

Number of UL codes not Supported; [FDD DPC mode change not Supported;] Cell reserved for operator use; Delayed Activation not supported; [FDD F-DPCH not supported;] E-DCH not supported; [FDD MIMO not supported;] [FDD E-DCH TTI2ms not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not available;] [FDD Continuous Packet Connectivity UE DTX Cycle not available;] [FDD MIMO not available;] [FDD F-DPCH Slot Format operation not supported;] [FDD E-DPCCH Power Boosting not supported;] [FDD SixtyfourQAM DL and MIMO Combined not available;] [FDD Multi Cell operation not available;] [FDD Multi Cell operation not supported;] [1.28Mcps TDD MIMO not supported;] [1.28Mcps TDD MIMO not available;] [1.28Mcps TDD SixtyfourQAM DL and MIMO Combined not available;] [FDD TX diversity for MIMO UE on DL Control Channels not available;] [FDD Single Stream MIMO not available;] [FDD Multi Cell operation with MIMO not available;] [FDD Multi Cell operation with MIMO not supported;] [FDD Multi Cell E-DCH Operation not supported;] [FDD Multi Cell E-DCH Operation not available;] [FDD Multi Cell operation with Single Stream MIMO not available;] [FDD Multi Cell operation with Single Stream MIMO not supported;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;] [FDD Frequency Specific Compressed Mode Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Supported.] Transport Layer Causes: Transport Resource Unavailable. Miscellaneous Causes: Control Processing Overload; HW Failure; Not enough User Plane Processing Resources.

8.3.2.4

Abnormal Conditions

If the RADIO LINK ADDITION REQUEST message includes a C-ID IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is not available in the DRNC for the considered UE Context, the DRNC shall reject the procedure for this particular Radio Link and send the RADIO LINK ADDITION FAILURE message. [FDD If the RADIO LINK ADDITION REQUEST message includes the Transmission Gap Pattern Sequence Status IEs in the Active Pattern Sequence Information IE and it does not address exactly all ongoing compressed mode patterns and frequency specific compressed mode is not supported, the DRNS shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the Cause IE value Invalid CM settings.] [FDD If the RADIO LINK ADDITION REQUEST message is used to establish a new RL without compressed mode when compressed mode is active for the existing RL(s) (as specified in subclause 8.3.2.2), and if at least one of the new RLs is to be established in a cell that has the same UARFCN (both UL and DL) as at least one cell with an already existing RL and frequency specific compressed mode is not supported,, the DRNS shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value Invalid CM settings.]

3GPP

Release 11

116

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing RL(s) and if the DL Reference Power IEs are included in the RL Information IE but the DL Reference Power IE is not present for each RL in the RL Information IE, the DRNC shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IEs in the RL Information IE but the power balancing is not active in the existing RL(s) or the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Common in the existing RL(s), the DRNC shall reject the Radio Link Addition procedure and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value Power Balancing status not compatible.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Enhanced Primary CPICH Ec/No IE, but not the Primary CPICH Ec/No IE, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE [FDD or for an E-DCH MAC-d flow in RL Specific E-DCH Information IE] included in the RL Information IE for a specific RL and the Diversity Control Field IE is set to Must [FDD or the RL is combined with existing E-DCH RL which transport bearer is not established in the DRNS], the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE nor RL Specific E-DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to May, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to Must Not, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in [FDD the RL Specific E-DCH Information IE in the RL Information IE for the first E-DCH RL][TDD the E-DCH MAC-d Flows Information TDD IE], the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for an HS-DSCH MAC-d Flow in the HS-DSCH MAC-d Flows Information IE, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport bearer intended to be established, the DRNC shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message. [FDD If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE but not the HS-DSCH FDD Information IE and the UE Context is not configured for HS-DSCH, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Serving Cell Change CFN IE but neither the Serving E-DCH RL IE nor the HS-DSCH Serving Cell Change Information IE, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE but the UE Context is not configured for E-DCH, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message, but the EDPCH Information IE is not present, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH RL Indication IE set to E-DCH, but no E-DCH FDD Information IE, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

3GPP

Release 11

117

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to E-DCH, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [TDD If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL-ID IE not equal to the RL ID IE, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [TDD If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE not equal to the RL ID IE, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] If the RADIO LINK ADDITION REQUEST message contains the HS-PDSCH RL ID IE [FDD in the HS-DSCH Serving Cell Change Information IE] and/or Serving E-DCH RL IE and if both HS-DSCH and E-DCH are configured in the DRNS but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message. [FDD If the RADIO LINK ADDITION REQUEST message contains the HS-DSCH Serving Cell Change Information IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as HSDSCH not configured then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD in the HSDSCH Serving Cell Change Information] and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD in the HS-DSCH Serving Cell Change Information] has the value Indexed MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message. If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD in the HSDSCH Serving Cell Change Information] and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD in the HS-DSCH Serving Cell Change Information] has the value Flexible MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message. [FDD If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [TDD If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE is not present, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH but the DCH is configured to be included as a part of the downlink CCTrCH, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the MIMO Activation Indicator IE, Sixtyfour QAM Usage Allowed Indicator IE set to Allowed, the Additional HS Cell Information RL Addition IE and/or the Single Stream MIMO Activation Indicator IE, but does not contain the HS-DSCH MAC-d PDU Size Format IE set to Flexible MAC-d PDU Size, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Serving E-DCH RL ID IE but contains the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information for the new Serving E-DCH RL or there is at least one E-DCH MAC-d flow which transport bearer was not configured in the existing E-DCH RL to be combined with the Serving E-DCH RL, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with the existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in DRNS, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

3GPP

Release 11

118

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE indicating a seconadry serving cell that is not in the same Node B as the new serving HS-DSCH cell, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message] [FDD If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and if the HS-DSCH is not configured in the DRNS Communication Context and the HS-DSCH Information IE is not present, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD in the HS-DSCH Serving Cell Change Information IE] set to Flexible RLC PDU Size, HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD in the HS-DSCH Serving Cell Change Information IE] has the value Indexed MAC-d PDU Size, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message. If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD in the HSDSCH Serving Cell Change Information IE] and the DL RLC PDU Size Format IE in the HS-DSCH Information IE [FDD in the HS-DSCH Serving Cell Change Information IE] has the value Flexible RLC PDU Size, the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message. [FDD If the RADIO LINK ADDITION REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE, then the DRNC shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Setup Req IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, but the Radio Link indicated by the E-DCH Additional RL ID IE is not configured in the current UE context as a Secondary Serving HSDSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the RADIO LINK ADDITION REQUEST message contains the Diversity Mode IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE and the secondary serving HSDSCH is already configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD If the secondary serving HS-DSCH is not configured in the UE Context and if the RADIO LINK ADDITION REQUEST message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE the Diversity Mode IE not set to None but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to None, then the DRNS shall reject the procedure using the RADIO LINK SETUP FAILURE message.] [FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL and all secondary serving HSDSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD - If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is

3GPP

Release 11

119

3GPP TS 25.423 V11.2.0 (2012-06)

configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message.] [FDD - If the RADIO LINK ADDITION REQUEST message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall reject the procedure using the RADIO LINK ADDITION FAILURE message with the cause value Invalid CM settings.]

8.3.3 Radio Link Deletion

8.3.3.1 General
The Radio Link Deletion procedure is used to release the resources in a DRNS for one or more established radio links towards a UE. This procedure shall use the signalling bearer connection for the relevant UE Context. The Radio Link Deletion procedure may be initiated by the SRNC at any time after establishing a Radio Link.

8.3.3.2

Successful Operation
SRNC
RADIO LINK DELETION REQUEST

DRNC

RADIO LINK DELETION RESPONSE

Figure 9: Radio Link Deletion procedure, Successful Operation The procedure is initiated with a RADIO LINK DELETION REQUEST message sent from the SRNC to the DRNC. Upon receipt of this message, the DRNS shall delete the radio link(s) identified by the RL ID IE(s) in the message, shall release all associated resources and shall respond to the SRNC with a RADIO LINK DELETION RESPONSE message. If the radio link(s) to be deleted represent the last radio link(s) for the UE in the DRNS and if the UE is not using any common resources in the DRNS, then the DRNC shall release the UE Context. [FDD After deletion of the RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall for each of the remaining RL Set(s) use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall for each of the remaining RL Set(s) use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.] [FDD If the RL indicated by the RL ID IE in the RADIO LINK DELETION REQUEST message is the serving HSDSCH Radio link and a related secondary serving HS-DSCH Radio Link exists in the DRNS, the DRNC shall delete the secondary serving HS-DSCH Radio Link.] [FDD If the RL indicated by the RL ID IE in the RADIO LINK DELETION REQUEST message is the secondary serving HS-DSCH Radio link, the DRNC shall delete the secondary serving HS-DSCH Radio Link.]

8.3.3.3
-

Unsuccessful Operation Abnormal Conditions

8.3.3.4

If the RL indicated by the RL ID IE does not exist, the DRNC shall respond with the RADIO LINK DELETION RESPONSE message.

3GPP

Release 11

120

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.4 Synchronised Radio Link Reconfiguration Preparation

8.3.4.1 General
The Synchronised Radio Link Reconfiguration Preparation procedure is used to prepare a new configuration of Radio Link(s) related to one UE-UTRAN connection within a DRNS. This procedure shall use the signalling bearer connection for the relevant UE Context. The Synchronised Radio Link Reconfiguration Preparation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.4.2

Successful Operation
SRNC DRNC Layer RADIO LINK RECONFIGURATION PREPARELayer
RADIO LINK RECONFIGURATION READY

Figure 10: Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation The Synchronised Radio Link Reconfiguration Preparation procedure is initiated by the SRNC by sending the RADIO LINK RECONFIGURATION PREPARE message to the DRNC. Upon receipt, the DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. If the RADIO LINK RECONFIGURATION PREPARE message includes the Allowed Queuing Time IE the DRNS may queue the request the time corresponding to the value of the Allowed Queuing Time IE before starting to execute the request. The DRNS shall prioritise resource allocation for the RL(s) to be modified according to Annex A. If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK RECONFIGURATION PREPARE message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. DCH Modification: If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs To Modify IEs, the DRNS shall treat them each as follows: If the DCHs To Modify IE includes multiple DCH Specific Info IEs then the DRNS shall treat the DCHs in the DCHs To Modify IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration. If the DCHs To Modify IE includes the UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE includes the ToAWS IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE includes the ToAWE IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Frame Handling Priority IE for a DCH to be modified, the DRNS should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the DRNS once the new configuration has been activated.

3GPP

Release 11 -

121

3GPP TS 25.423 V11.2.0 (2012-06)

If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Traffic Class IE for a DCH to be modified, the DRNS should store this information for this DCH in the new configuration. The Traffic Class IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this DCH indicates the value RRC. [FDD If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to Uplink DCH only, the DRNS shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.] [FDD If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to Downlink DCH only, the DRNS shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.] If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Transport Format Set IE for the UL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration. If the DCHs to Modify IE includes the TNL QoS IE for a DCH or a set of co-ordinated DCHs to be modified and if ALCAP is not used, the DRNS may store this information for this DCH in the new configuration. The TNL QoS IE may be used to determine the transport bearer characteristics to apply in the uplink for the related DCH or set of co-ordinated DCHs. If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Transport Format Set IE for the DL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration. If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A. [TDD If the DCHs To Modify IE includes the CCTrCH ID IE for the UL, the DRNS shall map the DCH onto the referenced UL CCTrCH in the new configuration.] [TDD If the DCHs To Modify IE includes the CCTrCH ID IE for the DL, the DRNS shall map the DCH onto the referenced DL CCTrCH in the new configuration.] If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Guaranteed Rate Information IE, the DRNS shall treat the included IEs according to the following: - If the Guaranteed Rate Information IE includes the Guaranteed UL Rate IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. - If the Guaranteed Rate Information IE includes the Guaranteed DL Rate IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate.

DCH Addition: If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs To Add IEs, the DRNS shall treat them each as follows: The DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCH in the new configuration. If the DCH Information IE includes a DCHs To Add IE with multiple DCH Specific Info IEs, the DRNS shall treat the DCHs in the DCHs To Add IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration.

3GPP

Release 11 -

122

3GPP TS 25.423 V11.2.0 (2012-06)

If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Uplink DCH only, the DRNS shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Downlink DCH only, the DRNS shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. [FDD For each DCH which do not belong to a set of co-ordinated DCHs and which includes a QE-Selector IE set to selected, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the QE-Selector IE is set to non-selected, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].] For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the QESelector IE set to selected for the QE in the UL data frames, TS 25.427 [4]. [FDD If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have the QE-Selector IE set to non-selected, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].] The DRNS should store the Frame Handling Priority IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the DRNS once the new configuration has been activated. If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs. The DRNS should store the Traffic Class IE received for a DCH to be added in the new configuration. The Traffic Class IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE indicates the value RRC. The DRNS shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. The DRNS shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. The DRNS shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. [3.84Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.] [1.28Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.] [7.68Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD 7.68Mcps IE in the RADIO LINK RECONFIGURATION READY message if at least one DSCH or USCH exists in the new configuration.] If the DCHs To Add IE contains a DCH Specific Info IE which includes the Guaranteed Rate Information IE, the DRNS shall treat the included IEs according to the following: - If the Guaranteed Rate Information IE includes the Guaranteed UL Rate IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate

3GPP

Release 11

123

3GPP TS 25.423 V11.2.0 (2012-06)

between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCHs To Add IE does not include the Guaranteed UL Rate IE, the DRNS shall not limit the user rate of the uplink of the DCH. - If the Guaranteed Rate Information IE includes the Guaranteed DL Rate IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCHs To Add IE does not include the Guaranteed DL Rate IE, the DRNS shall not limit the user rate of the downlink of the DCH. [TDD The DRNS shall apply the CCTrCH ID IE (for the DL) in the Downlink of this DCH in the new configuration.] [TDD The DRNS shall apply the CCTrCH ID IE (for the UL) in the Uplink of this DCH in the new configuration.]

DCH Deletion: If the RADIO LINK RECONFIGURATION PREPARE message includes any DCH To Delete, the DRNS shall not include the referenced DCHs in the new configuration. If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the DRNS shall not include this set of co-ordinated DCHs in the new configuration. Physical Channel Modification: [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes an UL DPCH Information IE, the DRNS shall apply the parameters to the new configuration as follows:] [FDD If the UL DPCH Information IE includes the Uplink Scrambling Code IE, the DRNS shall apply this Uplink Scrambling Code to the new configuration.] [FDD If the UL DPCH Information IE includes the Min UL Channelisation Code Length IE, the DRNS shall apply the new Min UL Channelisation Code Length in the new configuration. The DRNS shall apply the contents of the Max Number of UL DPDCHs IE (if it is included) in the new configuration.] [FDD If the UL DPCH Information IE includes the TFCS IE, the DRNS shall use the TFCS IE for the UL when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration.] [FDD If the UL DPCH Information IE includes the UL DPCCH Slot Format IE, the DRNS shall apply the new Uplink DPCCH Slot Format to the new configuration.] [FDD If the UL DPCH Information IE includes the UL SIR Target IE, the DRNS shall use the value for the UL inner loop power control when the new configuration is being used.] [FDD If the UL DPCH Information IE includes the Puncture Limit IE, the DRNS shall apply the value in the uplink of the new configuration.] [FDD If the UL DPCH Information IE includes the Diversity Mode IE, the DRNS shall apply diversity according to the given value.] [FDD If the UL DPCH Information IE includes the UL DPDCH Indicator For E-DCH Operation IE and it is set to UL DPDCH not present, the UL DPDCH resources shall be removed from the configuration.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes a DL DPCH Information IE and the concerned UE Context is configured to use F-DPCH in the downlink in the old configuration, the DRNS shall configure the concerned UE Context to use DPCH in the downlink in the new configuration. In this case, if at least one Transmission Gap Pattern Sequence is configured with an SF/2 downlink compressed mode method in the new configuration, the DRNC shall include the Transmission Gap Pattern Sequence Scrambling Code Information IE in the RADIO LINK RECONFIGURATION READY message indicating for each Channelisation Code whether the alternative scrambling code shall be used or not.]

3GPP

Release 11 -

124

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the DL DPCH Power Information IE, the DRNS shall use the information contained in it for the power settings of the DL DPCH. In particular, if the received Inner Loop DL PC Status IE is set to Active, the DRNS shall activate the inner loop DL power control for all RLs. If Inner Loop DL PC Status IE is set to Inactive, the DRNS shall deactivate the inner loop DL power control for all RLs according to TS 25.214 [10]. Furthermore, the DRNC shall include the DL Code Information IE in the RADIO LINK RECONFIGURATION READY.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes a DL DPCH Information IE, the DRNS shall apply the parameters to the new configuration as follows:] [FDD If the DL DPCH Information IE includes the Number of DL Channelisation Codes IE, the DRNS shall allocate given number of Downlink Channelisation Codes per Radio Link and apply the new Downlink Channelisation Code(s) to the new configuration. Each Downlink Channelisation Code allocated for the new configuration shall be included in the RADIO LINK RECONFIGURATION READY message within the DL Code Information IE as a FDD DL Channelisation Code Number IE when sent to the SRNC. If some Transmission Gap Pattern sequences using SF/2 method are already initialised in the DRNS, DRNC shall include the Transmission Gap Pattern Sequence Scrambling Code Information IE in the RADIO LINK RECONFIGURATION READY message in case the DRNS selects to change the Scrambling code change method for one or more DL Channelisation Code.] [FDD When more than one DL DPDCH are assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to TS 25.211 [8]. When p number of DL DPDCHs are assigned to each RL, the first pair of DL Scrambling Code and FDD DL Channelisation Code Number corresponds to PhCH number 1, the second to PhCH number 2, and so on until the pth to PhCH number p.] [FDD If the DL DPCH Information IE includes the TFCS IE, the DRNS shall use the TFCS IE for the DL when reserving resources for the downlink of the new configuration. The DRNS shall apply the new TFCS in the Downlink of the new configuration.] [FDD If the DL DPCH Information IE includes the DL DPCH Slot Format IE, the DRNS shall apply the new slot format used in DPCH in DL.] [FDD If the DL DPCH Information IE includes the TFCI Signalling Mode IE, the DRNS shall apply the new signalling mode of the TFCI.] [FDD If the DL DPCH Information IE includes the Multiplexing Position IE, the DRNS shall apply the new parameter to define whether fixed or flexible positions of transport channels shall be used in the physical channel.] [FDD If the DL DPCH Information IE includes the Limited Power Increase IE set to Used, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.] [FDD If the DL DPCH Information IE includes the Limited Power Increase IE set to Not Used, the DRNS shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the F-DPCH Information IE, then:] [FDD The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink in the new configuration.] [FDD If the F-DPCH Information IE includes the F-DPCH Slot Format Support Request IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the RADIO LINK RECONFIGURATION READY message. If the FDPCH Information IE includes the F-DPCH Slot Format IE, the DRNC may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Transmission Gap Pattern Sequence Information IE, the DRNS shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode Configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode Configuration has been activated or once the previous Compressed Mode Configuration has been deactivated. This new Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or until the last Radio Link is deleted.]

3GPP

Release 11

125

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Transmission Gap Pattern Sequence Information IE and the Downlink Compressed Mode Method IE in one or more Transmission Gap Pattern Sequence within the Transmission Gap Pattern Sequence Information IE is set to SF/2 and the UE Context is configured to use DPCH in the downlink in the new configuration, the DRNC shall include the Transmission Gap Pattern Sequence Scrambling Code Information IE in the RADIO LINK RECONFIGURATION READY message indicating for each Channelisation Code whether the alternative scrambling code shall be used or not.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DPCH Information IE, the DRNS shall apply the parameters to the new configuration as follows:] [FDD If the E-DPCH Information IE includes the Maximum Set of E-DPDCHs IE, the DRNS shall aplly the contents of the Maximum Set in the new configuration.] [FDD If the E-DPCH Information IE includes the Puncture Limit IE, the DRNS shall apply the value in the uplink of the new configuration] [FDD If the E-DPCH Information IE includes the E-TFCS Information IE, the DRNS shall use the E-TFCS Information IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the E-TFCS Information IE contains the EDCH Minimum Set E-TFCI Validity Indicator IE the DRNS shall ignore the value in E-DCH Minimum Set ETFCI IE. If the E-DCH Minimum Set E-TFCI validity indicator IE is absent DRNS shall use the value for the related resource allocation operation.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION PREPARE message.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the DRNS shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the DRNS shall use the value 127 in the algorithm defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION PREPARE message.] [FDD If the E-DPCH Information IE includes the E-TTI IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the E-DPCCH Power Offset IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the E-RGCH 2-Index-Step IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the E-RGCH 3-Index-Step IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the E-DCH HARQ Info IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the HS-DSCH Configured Indicator IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the E-DPCH Information IE includes the Minimum Reduced E-DPDCH Gain Factor IE , then the DRNS shall use the value to determine the applicable minimum gain factor (ed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ]

[FDD If the RADIO LINK RECONFIGURATION PREPAR message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:] [FDD The DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]

3GPP

Release 11 -

126

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then:] -[FDD If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.] -[FDD If the Enabling Delay IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10].] -[FDD If the DTX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of DTX Information To Modify IE is Deactivate, then DRX should be deactived together with DTX.] -[FDD If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:] [FDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].] [FDD The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If at least one of HS-PDSCH Second Code Support IE is set to True, then the DRNC shall include HSPDSCH Second Code Index IE in the RADIO LINK RECONFIGURATION READY message.]

[FDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE, then the DRNS shall deactive the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.] [FDD - UL CLTD Setup:] [FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Setup", then: the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights according the new configuration defined in the UL CLTD Information IE and then:] [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the C-ID IE shall be included in the UL CLTD Information IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.] [FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.] [FDD - UL CLTD Modification:] [FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Configuration Change", then: the UL CLTD Information To Modify IE defines the new configuration and then:] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE in the UL CLTD Information To Modify IE, then the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context. Otherwise the DRNS shall configure the serving E-DCH cell or the HS_DSCH serving

3GPP

Release 11

127

3GPP TS 25.423 V11.2.0 (2012-06)

cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the S-DPCCH Power Offset information IE in the UL CLTD Information To Modify IE, then the DRNS shall use this value to determine the S-DPCCH power.] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the UL CLTD State Activation Information IE in the UL CLTD Information To Modify IE, then the DRNS shall use this value to update the local state of UL CLTD for the concerned UE Context. If the UL CLTD Activation Information IE is set to "De-activated", the DRNS should release the F-TPICH resource configured for the concerned UE Context.]]

[FDD - UL CLTD Removal:] [FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Removal", then the configured UL CLTD for the concerned UE Context shall be removed.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DRX Information To Modify LCR IE, then:] -[1.28 Mcps TDD If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.] -[1.28 Mcps TDD If the Enabling Delay IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [22].] -[1.28 Mcps TDD If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH SemiPersistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH SemiPersistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].]

3GPP

Release 11 -

128

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allocated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH SemiPersistent scheduling Information to modify LCR IE, then:] [1.28 Mcps TDD If the Transport Block Size List IE or/and Repetition Period list IE is/are included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, the DRNS shall modifiy the configuration of Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22]. [1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall include Allcoated HSPDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.] [1.28 Mcps TDD If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION READY message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH SemiPersistent scheduling Information to modify LCR IE, then:] [1.28 Mcps TDD If the Repetition Period list IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, the DRNS shall modifiy the configuration of Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22]. [1.28 Mcps TDD If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH SemiPersistent scheduling Information to modify LCR IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.] [1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall include Allocated E-DCH Semipersistent resource IE in the RADIO LINK RECONFIGURATION READY message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH SemiPersistent scheduling Deactivate Indicator LCR IE, then the DRNS shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH SemiPersistent scheduling Deactivate Indicator LCR IE, then the DRNS shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.] [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the MU-MIMO Indicator IE, then:] [1.28 Mcps TDD - The DRNS may use the MU-MIMO for the radio link according to the MU-MIMO Usage Indicator IE and shall include the MU-MIMO Information IE in the RADIO LINK RECONFIGURATION READY message.] [1.28 Mcps TDD - If the Standalone Midamble Channel Indicator IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION READY

3GPP

Release 11

129

3GPP TS 25.423 V11.2.0 (2012-06)

message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION READY message.] [TDD UL/DL CCTrCH Modification] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any UL CCTrCH To Modify IEs or DL CCTrCH To Modify IEs, then the DRNS shall treat them each as follows:] [TDD If any of the UL CCTrCH To Modify IEs or DL CCTrCH To Modify IEs includes any of the TFCS IE, TFCI coding IE, Puncture limit IE, or TPC CCTrCH ID IEs the DRNS shall apply these as the new values, otherwise the previous values specified for this CCTrCH are still applicable.] [TDD If any of the following listed DPCH information IEs are modified in the new prepared configuration, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the IEs indicating the new values: Repetition Period IE, Repetition Length IE, TDD DPCH Offset IE, [3.84Mcps TDD UL Timeslot Information IE,] [1.28Mcps TDD UL Timeslot Information LCR IE,] [7.68 Mcps TDD UL Timeslot Information 7.68 Mcps IE,] [3.84Mcps TDD DL Timeslot Information IE,] [1.28Mcps TDD DL Timeslot Information LCR IE,] [7.68 Mcps TDD DL Timeslot Information 7.68 Mcps IE,] [3.84Mcps TDD Midamble Shift And Burst Type IE,] [1.28Mcps TDD Midamble Shift LCR IE,] [7.68 Mcps TDD Midamble Shift And Burst Type 7.68 Mcps IE,] TFCI Presence IE, [3.84Mcps TDD TDD Channelisation Code IE,] [1.28Mcps TDD and/or TDD Channelisation Code LCR IE,] [7.68 Mcps TDD TDD Channelisation Code 7.68 Mcps IE,] [1.28Mcps TDD TDD UL DPCH Time Slot Format LCR IE or TDD DL DPCH Time Slot Format LCR IE].] [1.28Mcps TDD If the UL CCTrCH To Modify IE includes the UL SIR Target IE, the DRNS shall use the value for the UL inner loop power control according to TS 25.221 [12] and TS 25.224 [22] in the new configuration.] [TDD If any of the DL CCTrCH To Modify IEs includes any TPC CCTrCH ID IEs, the DRNS shall apply these as the new values, otherwise the previous values specified for this CCTrCH are still applicable.] [1.28Mcps TDD If the UL CCTrCH to Modify IE includes the TDD TPC Uplink Step Size IE, the DRNS shall apply this value to the uplink TPC step size in the new configuration.] [TDD If the DL CCTrCH to Modify IE includes the TDD TPC Downlink Step Size IE, the DRNS shall apply this value to the downlink TPC step size in the new configuration.] [1.28 Mcps TDD if the DRNS modifies, deletes or grants a new PLCCH assignment(s) to the UL CCTrCH, then the resulting PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK RECONFIGURATION READY message.]

[TDD UL/DL CCTrCH Addition] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any UL CCTrCH To Add IEs or DL CCTrCH To Add IEs, the DRNS shall include this CCTrCH in the new configuration.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any DCHs to Add IEs, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the DPCH information in [3.84Mcps TDD UL DPCH to be Added IE/DL DPCH to be Added IEs] [1.28Mcps TDD UL DPCH to be Added LCR IE/DL DPCH to be Added LCR IEs] [7.68 Mcps TDD UL DPCH to be Added 7.68 Mcps IE/DL DPCH to be Added 7.68 Mcps IEs]. [3.84Mcps TDD If no UL DPCH is active before a reconfiguration which adds an UL DPCH, and if a valid Rx Timing Deviation measurement is known in DRNC, then the DRNC shall include the Rx Timing Deviation IE (or the Rx Timing Deviation 3.84 Mcps Extended IE if the cell containing the radio link is configured for extended timing advance) in the RADIO LINK RECONFIGURATION READY message]. [7.68 Mcps TDD If no UL DPCH is active before a reconfiguration which adds an UL DPCH, and if a valid Rx Timing Deviation measurement is known in DRNC, then the DRNC shall include the Rx Timing Deviation 7.68 Mcps IE in the RADIO LINK RECONFIGURATION READY message].] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the TDD TPC Downlink Step Size IE within a DL CCTrCH To Add IE, the DRNS shall set the TPC step size of that CCTrCH to that value, otherwise the DRNS shall use the same value as the lowest numbered DL CCTrCH in the current configuration.] [1.28Mcps TDD The DRNS shall use the UL SIR Target IE in the UL CCTrCH To Add IE as the UL SIR value for the inner loop power control for this CCTrCH according to TS 25.221 [12] and TS 25.224 [22] in the new configuration.]

3GPP

Release 11

130

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD If any of the DL CCTrCH To Add IEs includes any TPC CCTrCH ID IEs, the DRNS shall configure the identified UL CCTrCHs with TPC according to the parameters given in the message.] [1.28Mcps TDD If the UL CCTrCH To Add IE includes TDD TPC Uplink Step Size IE, the DRNS shall apply the uplink TPC step size in the new configuration.] [1.28 Mcps TDD if the DRNS grants a PLCCH assignment(s) to the UL CCTrCH, then the resulting PLCCH assignment(s) shall be sent to the SRNC in the RADIO LINK RECONFIGURATION READY message.] [TDD UL/DL CCTrCH Deletion] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any UL CCTrCH To Delete IEs or DL CCTrCH To Delete IEs, the DRNS shall remove this CCTrCH in the new configuration, and the DRNC shall include in the RADIO LINK RECONFIGURATION READY message corresponding UL DPCH to be Deleted IEs and DL DPCH to be Deleted IEs.] DL Power Control: [FDD If the RL Information IE includes the DL Reference Power IEs and power balancing is active, DRNS shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported, when the new configuration has been activated, according to subclause 8.3.15, using the DL Reference Power IE. If the CFN modulo the value of the Adjustment Period IE is not equal to 0, the power balancing continues with the old reference power until the end of the current adjustment period, and the updated reference power shall be used from the next adjustment period.] [FDD If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNC shall include the DL Power Balancing Updated Indicator IE in the RL Information Response IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.] [TDD DSCH Addition/Modification/Deletion:] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any DSCH To Add, DSCH To Modify or DSCH To Delete IEs, then the DRNS shall use this information to add/modify/delete the indicated DSCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any DSCH To Add IE, then the DRNS shall use the Allocation/Retention Priority IE, Scheduling Priority Indicator IE and TrCH Source Statistics Descriptor IE to define a set of DSCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.] [TDD The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each added DSCH.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any DSCH To Add IE, then the DRNS may use the Traffic Class IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the TNL QoS IE in the DSCH TDD Information IE and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any DSCH To Modify IE, then the DRNS shall treat them each as follows:] [TDD The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for any new transport bearer to be established for each modified DSCH.] [TDD If the DSCHs To Modify IE includes the CCTrCH ID IE, then the DRNS shall map the DSCH onto the referenced DL CCTrCH.] [TDD If the DSCHs To Modify IE includes any of the Allocation/Retention Priority IE, Scheduling Priority Indicator IE or TrCH Source Statistics Descriptor IE, the DNRS shall use them to update the set of DSCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.]

3GPP

Release 11 -

131

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD If the DSCHs To Modify IE includes any of the Transport Format Set IE or BLER IE, the DRNS shall apply the parameters to the new configuration.] [TDD If the DSCHs To Modify IE includes the Traffic Class IE, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related DSCHs.] [TDD If the DSCHs To Modify IE includes the TNL QoS IE and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply in the uplink for the related DSCH.]

[3.84 Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info TDD IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [1.28 Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [7.68 Mcps TDD The DRNC shall include the Secondary CCPCH Info 7.68 Mcps TDD IE in the RADIO LINK RECONFIGURATION READY message if a DSCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info 7.68 Mcps TDD IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [TDD The DRNC shall include the DSCH Initial Window Size IE in the RADIO LINK RECONFIGURATION READY message for each DSCH, if the DRNS allows the SRNC to start transmission of MAC-c/sh SDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32].] [TDD USCH Addition/Modification/Deletion] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any USCH To Modify, USCH To Add or USCH To Delete IEs, then the DRNS shall use this information to add/modify/delete the indicated USCH channels to/from the radio link, in the same way as the DCH info is used to add/modify/release DCHs.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any USCH To Add IE, then, the DRNS shall use the Allocation/Retention Priority IE, Scheduling Priority Indicator IE and TrCH Source Statistics Descriptor IE to define a set of USCH Priority classes each of which is associated with a set of supported MAC-c/sh SDU lengths.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any USCH To Add IE, then the DRNS may use the Traffic Class IE to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any USCH To Add IE, if the TNL QoS IE is included and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply for the related USCHs.] [TDD The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each added USCH.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes any USCH To Modify IE, then the DRNS shall treat them each as follows:] [TDD If the USCH To Modify IE includes any of the Allocation/Retention Priority IE, Scheduling Priority Indicator IE or TrCH Source Statistics Descriptor IE, the DNRS shall use them to update the set of USCH Priority classes.] [TDD If the USCH To Modify IE includes any of the CCTrCH ID IE, Transport Format Set IE, BLER IE or RB Info IE, the DRNS shall apply the parameters to the new configuration.] [TDD If the USCHs To Modify IE includes the Traffic Class IE, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related USCHs.]

3GPP

Release 11 -

132

3GPP TS 25.423 V11.2.0 (2012-06)

[3.84Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info TDD IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [1.28Mcps TDD The DRNC shall include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info TDD LCR IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [7.68Mcps TDD The DRNC shall include the Secondary CCPCH Info 7.68Mcps TDD IE in the RADIO LINK RECONFIGURATION READY message if a USCH is added and at least one DCH exists in the new configuration. The DRNC shall also include the Secondary CCPCH Info 7.68Mcps TDD IE in the RADIO LINK RECONFIGURATION READY message if the SHCCH messages for this radio link will be transmitted over a different secondary CCPCH than selected by the UE from system information.] [TDD if the TNL QoS IE is included and if ALCAP is not used, the DRNS may use the TNL QoS IE to determine the transport bearer characteristics to apply for the related USCHs.] [TDD The DRNC shall include in the RADIO LINK RECONFIGURATION READY message both the Transport Layer Address IE and the Binding ID IE for any new transport bearer to be established for each modified USCH.]

RL Information: [FDD If the RL Information IE includes the DL DPCH Timing Adjustment IE, the DRNS shall adjust the timing of the radio link accordingly in the new configuration. If the UE Context is configured to use F-DPCH in the downlink in the new configuration, the DRNC may include the DL Code Information IE in the RADIO LINK RECONFIGURATION READY message.] [FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Setup", then the DRNS shall use the information in F-TPICH Information IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] [FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Configuration Change", then: the F-TPICH Information To Modify IE defines the new configuration and then:] [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Slot Format IE, then the DRNS shall use this information to configure the F-TPICH slot format according to TS 25.211 [7]. [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Offset IE, the DRNS shall use this information to configure the time offset of F-TPICH.] [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Channelisation Code Number IE, the DRNS shall use this information to configure the channelization code of F-TPICH.]

[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Removal", then the DRNS shall remove the configured F-TPICH for the RL.] HS-DSCH Setup: If the HS-DSCH Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message, then: -The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. -The DRNC shall include the HARQ Memory Partitioning IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message. [FDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.]

3GPP

Release 11

133

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.] -The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK RECONFIGURATION READY message. -The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. -If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HS-DSCH Information Response IE. -If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. -The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32] If RADIO LINK RECONFIGURATION PREPARE message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to Flexible MAC-d PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION PREPARE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE. -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] -[FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -[FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -[TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68 Mcps TDD HS-SCCH Specific Information Response 7.68 Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]

3GPP

Release 11

134

3GPP TS 25.423 V11.2.0 (2012-06)

-[FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then:] - [FDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] - [FDD The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where the Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [1.28 Mcps TDD If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then:] - [1.28 Mcps TDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] - [1.28 Mcps TDD The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format IE set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may use:] - [FDD a different HS-SCCH in consecutive TTIs for this UE] - [FDD HS-SCCH orders for the case of HS-SCCH-less operation to this UE] [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported,

3GPP

Release 11

135

3GPP TS 25.423 V11.2.0 (2012-06)

include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.] [1.28 Mcps TDD If the UE TS0 Capability LCR IE is included in the HS-DSCH TDD Information IE, then the DRNC may include the TS0 HS-PDSCH Indication LCR IE in the RADIO LINK RECONFIGURATION READY message if HS-PDSCH resources could be allocated on TS0 for the UE]

[FDD Secondary Serving HS-DSCH Setup:] [FDD If the C-ID IE is present in the Additional HS Cell Information RL Reconf Prep IE in the RADIO LINK RECONFIGURATION PREPARE message, and no secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE or in the HS-DSCH FDD Secondary Serving Information To Modify IE for each instance of the Additional HS Cell Information RL Reconf Prep IE, indicate that new secondary serving HS-DSCH Radio Link(s) shall be setup, then:] [FDD The DRNS shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] [FDD The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-

3GPP

Release 11

136

3GPP TS 25.423 V11.2.0 (2012-06)

zero power offset where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HSDSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondaery serving HS-DSCH, then the DRNC shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.] [FDD If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE, the DRNS shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to None the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.]

Intra-DRNS Serving HS-DSCH Radio Link Change: If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link: The DRNS shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HSPDSCH resources on the new Serving HS-DSCH Radio Link. The DRNC may include the HARQ Memory Partitioning IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message. [FDD The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [1.28Mcps TDD The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HS-DSCH Information Response IE. The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK RECONFIGURATION READY message. If a reset of the MAC-hs is not required the DRNS shall include the MAC-hs Reset Indicator IE in the RADIO LINK RECONFIGURATION READY message. [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.]

3GPP

Release 11

137

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68 Mcps TDD HS-SCCH Specific Information Response 7.68 Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [TDD The DRNC shall include the [3.84 Mcps TDD HS-PDSCH Timeslot Specific Information IE] [1.28 Mcps TDD HS-PDSCH Timeslot Specific Information LCR IE] [7.68 Mcps TDD HS-PDSCH Timeslot Specific Information 7.68 Mcps IE] in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] The DRNC may include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION READY message. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. [FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE and the value is set to "allowed" or if HS-DSCH Information To Modify IE is not included and the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD Intra-DRNS Secondary Serving HS-DSCH Radio Link Change:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE for each instance of the Additional HS Cell Information RL Reconf Prep IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-DRNS secondary serving HS-DSCH Radio Link change, then the HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:] [FDD The DRNS shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The DRNS shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] [FDD The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.]

3GPP

Release 11 -

138

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE and the value is set to "allowed" or if HS-DSCH FDD Secondary Serving Information To Modify IE is not included and the UE Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.] [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link, and then:] - [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] - [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] - [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] - [FDD If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE, the DRNS shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to

3GPP

Release 11

139

3GPP TS 25.423 V11.2.0 (2012-06)

None the DRNS shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.] [FDD - If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured for the secondary serving HS-DSCH radio link in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the Power Offset For SCPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE and an additional non serving E-DCH RL exists in the cell indicated by the C-ID IE, the HS-PDSCH RL ID IE in the Additional HS Cell Information RL Reconf Prep IE indicates the new Additional Serving E-DCH Radio Link.] - [FDD If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the EAGCH resources of the old Serving Additional E-DCH Radio Link at the activation of the new configuration.] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message] - [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Link on secondary UL frequency in the DRNS. If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the E-DCH FDD DL Control Channel Information IE then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the E-DCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD Additional Serving E-DCH Radio Link Change to a new RL:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information RL Reconf Prep IE and the C-ID IE in the Additional HS Cell Information RL Reconf Prep IE and there is no radio links in the cell indicated by the C-ID IE for the UE context, the HSPDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.] [FDD If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the EAGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]

3GPP

Release 11 -

140

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE] [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.]

HS-DSCH Modification: If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information To Modify IE, then: -The DRNC shall include the HS-DSCH Initial Capacity Allocation IE for each HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the DRNS allows the SRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK RECONFIGURATION PREPARE message includes HS-DSCH MAC-d PDU Size Format IE in the HSDSCH Information To Modify IE set to Flexible MAC-d PDU Size, then DRNC shall only set in the HSDSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION PREPARE in the HS-DSCH Information To Modify IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE. -If the RADIO LINK RECONFIGURATION PREPARE message includes the Traffic Class IE in the HS-DSCH Information To Modify IE for a specific HS-DSCH MAC-d flow, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this specific HS-DSCH MAC-d flow indicates the value RRC. -If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. -If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH Information To Modify IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH Information To Modify IE, then the DRNS shall use this information to discard outof-date MAC-hs SDUs from the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE in the HS-DSCH Information To Modify IE, then the DRNS shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Window Size IE or T1 IE in the HS-DSCH Information To Modify IE, then the DRNS shall use the indicated values in the new configuration for the related HSDPA Priority Queue.

3GPP

Release 11

141

3GPP TS 25.423 V11.2.0 (2012-06)

-If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-d PDU Size Index IE in the Modify Priority Queue choice, the DRNS shall delete the previous list of MAC-d PDU Size Index values for the related HSDPA Priority Queue and use the MAC-d PDU Size Index values indicated in the MAC-d PDU Size Index IE in the new configuration. -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the CQI Feedback Cycle k IE, the CQI Repetition Factor IE, the ACK-NACK Repetition Factor IE, the ACK Power Offset IE, the NACK Power Offset IE or the CQI Power Offset IE in the HS-DSCH Information To Modify IE, then the DRNS shall use the indicated CQI Feedback Cycle k value, the CQI Repetition Factor or the ACK-NACK Repetition Factor, ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.] -[FDD If the HS-SCCH Power Offset IE is included in the HS-DSCH Information To Modify IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] -[TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the TDD ACK NACK Power Offset IE in the HS-DSCH Information To Modify IE, the DRNS shall use the indicated power offset in the new configuration.] -[FDD If the HS-DSCH Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the DRNS may modify the HS-SCCH codes corresponding to the HS-DSCH. The DRNC shall then report the codes which are used in the new configuration specified in the HS-SCCH Specific Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -[FDD If the HS-DSCH Information To Modify IE includes the HS-PDSCH Code Change Grant IE, then the DRNS may modify the HS-PDSCH codes corresponding to the HS-DSCH. The DRNC shall then report the codes which are used in the new configuration specified in the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the concerned DRNS is not in Continuous Packet Connectivity HS-SCCH less mode, the SRNC shall not include the HS-PDSCH Code Change Grant IE in the HS-DSCH Information To Modify IE.] -[TDD If the HS-DSCH Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the DRNS may modify the HS-SCCH parameters corresponding to the HS-DSCH. The DRNC shall then report the values for the parameters which are used in the new configuration specified in the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68 Mcps TDD HS-SCCH Specific Information Response 7.68 Mcps IE] in the RADIO LINK RECONFIGURATION READY message.] -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Preamble Mode IE in the HS-DSCH Information To Modify IE, then the DRNS shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the HSDSCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.] -If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information To Modify IE, then the DRNS shall use, in the new configuration, the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Physical Layer Category IE in the HS-DSCH Information To Modify IE, the DRNS shall use this information in the new configuration.] [FDD If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then:] [FDD The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the MIMO Mode Indicator IE.] [FDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and

3GPP

Release 11

142

3GPP TS 25.423 V11.2.0 (2012-06)

include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the MIMO Mode Indicator IE is set to Activate and Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HSDSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For SCPICH for MIMO IE.]

[FDD The DRNC may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.] [FDD If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [1.28Mcps TDD If the MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then:] [1.28Mcps TDD The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the MIMO Mode Indicator IE.] [1.28 Mcps TDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]

[1.28Mcps TDD The DRNC may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [FDD Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.] [FDD If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH Information To Modify IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify IE, then the DRNS shall activate/deactivate the Single Stream MIMO for the HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]

3GPP

Release 11 [FDD Secondary Serving HS-DSCH Modification:]

143

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH FDD Secondary Serving Information To Modify IE, then:] [FDD If the HS-SCCH Power Offset IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] [FDD If the HS-DSCH FDD Secondary Serving Information To Modify IE includes the HS-SCCH Code Change Grant IE, then the DRNS may modify the HS-SCCH codes corresponding to the secondary serving HSDSCH. The DRNC shall then report the codes which are used in the new configuration specified in the HSSCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the DRNS shall activate/deactivate the MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.] [FDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the MIMO Mode Indicator IE is set to Activate and Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the DRNS shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HSDSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondaery serving HS-DSCH, then the DRNC shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.] [FDD If the Diversity Mode IE is included, then:] [FDD- the DRNS shall apply cell specific transmit diversity configuration for the secondary serving HSDSCH radio link according to Diversity Mode IE and Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information To Modify IE,]

3GPP

Release 11 -

144

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Diversity Mode IE is not set to None, the DRNS shall apply diversity for the secondary serving HS-DSCH radio link according to the value given in the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information To Modify IE.]

[FDD If the Non Cell Specific Tx Diversity IE equals Tx Diversity is included, the DRNS shall apply non cell specific transmit diversity configuration and reconfigure the transmit diversity setting for the secondary serving HS-DSCH radio link to the same value as defined for the serving HS-DSCH radio link in the new configuration.]

[FDD Secondary Serving HS-DSCH Removal:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Secondary Serving Remove IE in the Additional HS Cell Information RL Reconf Prep IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.] HS-DSCH MAC-d Flow Addition/Deletion: If the RADIO LINK RECONFIGURATION PREPARE message includes any HS-DSCH MAC-d Flows To Add or HSDSCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed. If the RADIO LINK RECONFIGURATION PREPARE message includes an HS-DSCH MAC-d Flows To Delete IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the UE Context, then the DRNC shall delete the HS-DSCH configuration from the UE Context and release the HS-PDSCH resources. If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH MAC-d Flows To Add IE, then: The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. The DRNC shall include the HS-DSH Initial Capacity Allocation IE in the RADIO LINK RECONFIGURATION READY message for every HS-DSCH MAC-d flow being added, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If the UE context is configured to use the Flexible MAC-d PDU Size format for the HS-DSCH, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION PREPARE message in the HS-DSCH MAC-d Flows To Add IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE. If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. If the RADIO LINK RECONFIGURATION PREPARE message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the DRNS shall use this information to discard out-ofdate MAC-hs SDUs from the related HSDPA Priority Queue. If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the DRNC shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. The DRNC may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION READY message. [FDD The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]

3GPP

Release 11 -

145

3GPP TS 25.423 V11.2.0 (2012-06)

If the RADIO LINK RECONFIGURATION PREPARE message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]

[FDD HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [63]:] [FDD The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HSDSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK RECONFIGURATION PREPARE message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-ID IEsin the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK RECONFIGURATION PREPARE message.] [FDD The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ] - [FDD by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell.] - [FDD by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells.] [FDD If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ] [FDD The DRNS shall return these codes in the Sets of HS-SCCH Codes IE along with the corresponding percell HS-DSCH-RNTI IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK RECONFIGURATION READY.] [FDD The DRNS shall use the first in the numbered list the primary serving HS-DSCH cells of HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16].] [FDD The DRNS shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION READY message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:] - [FDD if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE.] - [FDD if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE.] - [FDD if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfiguration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell.] - [FDD if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell.] - [FDD if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE.] - [FDD if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS shall store this information in the preconfigured configuration.]

3GPP

Release 11

146

3GPP TS 25.423 V11.2.0 (2012-06)

- [FDD the SixtyfourQAM DL Support Indicator IE may be included.] - [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS may store this information in the preconfigured configuration.] - [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD the DRNS shall, if supported, include in the Sets of HS-SCCH Codes IE the Measurement Power Offset IE for each preconfigured cell.] [FDD The DRNS shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION READY message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] - [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.] - [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where HS-DSCH / secondary HS-DSCH is preconfigured, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH Preconfiguration Info IE or in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE for each preconfigured cell in the RADIO LINK RECONFIGURATION READY message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Non-Serving RL Preconfiguration Setup IE in the RL Information IE and:] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION READY message.] [FDD if the choice of new Serving RL is "New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION READY message.] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL EDCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.] [FDD if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION READY message.]

[FDD Enhanced HS Serving Cell Change:]

3GPP

Release 11

147

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD -Upon receipt of the RADIO LINK RECONFIGURATION PREPARE message, if the Enhanced HS Serving Cell Change is preconfigured in the DRNS for the UE context, the DRNS may execute the Enhanced HS Serving Cell Change procedure according to [63.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Enhanced HS Serving CC Abort IE in the HS-DSCH Information To Modify IE or the HS-DSCH FDD Information IE then the DRNS shall not execute the synchronized Enhanced HS Serving Cell Change procedure when performing the Serving HS-DSCH Radio Link Change or the HS-DSCH Setup.] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Non-Serving RL Preconfiguration Removal IE, the DRNS shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.] [FDD E-DCH Setup:] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message then:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, then the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.] [FDD If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume nonscheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.] [FDD If in the RADIO LINK RECONFIGURATION PREPARE message the E-DCH Grant Type is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.] [FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [FDD If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Bundling Mode Indicator IE for a E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then

3GPP

Release 11

148

3GPP TS 25.423 V11.2.0 (2012-06)

the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH ReferencePower Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the SixteenQAM UL Operation Indicator IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.] - [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].] [FDD E-DCH Radio Link Handling:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH RL Indication IE in the RL Information IE:] [FDD The DRNC shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD The DRNC may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNC may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every RL indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD The DRNC shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the EDCH RL Indication IE set to Non E-DCH, in the RL Information IE.] [FDD For each RL for which the E-DCH RL Indication IE is set to E-DCH, and which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the E-DCH RL Set ID IE in the RADIO LINK RECONFIGURATION READY message. The value of the E-DCH RL Set ID IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]

[FDD Serving E-DCH Radio Link Change:]

3GPP

Release 11

149

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Serving E-DCH RL ID IE, this indicates the new Serving E-DCH Radio Link:] [FDD If the old Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link at the activation of the new configuration.] [FDD If the new Serving E-DCH RL is within this DRNS:] - [FDD the DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RL Information Response IE for the indicated RL in the RADIO LINK RECONFIGURATION READY message.] - [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the new serving E-DCH RL.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD If a serving cell change is performed the RADIO LINK RECONFIGURATION READY message may contain invalid data (see 9.2.2.4C).] - [FDD The DRNS may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION READY message for the new serving E-DCH RL.] [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message for every E-DCH Radio Links in the DRNS.] [FDD If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION READY message, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the E-DCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.]

[FDD E-DCH Modification:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information To Modify IE, then:] [FDD If the E-DCH FDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d PDU Size Format IE in the E-DCH FDD Information To Modify IE, then the DRNS shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [FDD If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD If the Traffic Class IE is included for an E-DCH MAC-d flow then the DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this specific E-DCH MAC-d flow indicates the value RRC.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Data Description Indicator IE, the DRNC shall use the DDI values indicated in the Data Description Indicator IE in the new configuration.]

3GPP

Release 11 -

150

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH FDD Information To Modify IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information To Modify IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow in the E-DCH FDD Information To Modify IE, then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH HARQ Power Offset FDD IE in the E-DCH FDD Information To Modify IE for an E-DCH MAC-d flow the DRNS shall use this information for calculating the unquantised gain factor for an E-TFC (ed,j,uq)as defined in TS 25.214 [10].] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Grant Type and it is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the DRNS shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Logical Channel To Modify IE, the DRNS shall use this information to modify the indicated logical channels:] - [FDD If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the DRNS shall apply the values in the new configuration.] - [FDD If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the DRNS shall apply the values in the new configuration.] - [FDD If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the DRNS shall apply the value in the new configuration.]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information To Modify IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.] [FDD If the E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.]

3GPP

Release 11 -

151

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH ReferencePower Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-e Reset Indicator IE in the E-DCH FDD Information To Modify IE, then the DRNS shall use this value to determine whether MACe(or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the SixteenQAM UL Operation Indicator IE in the E-DCH FDD Information To Modify IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE] - [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].]

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH DL Control Channel Grant Information IE in the E-DCH FDD Information To Modify IE, the DRNS may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the E-DCH RL ID IE. The DRNC shall then report the modified configuration which is used in the new configuration specified in the E-DCH FDD DL Control Channel Information IE for each E-DCH RL in the RADIO LINK RECONFIGURATION READY message.]

[FDD E-DCH MAC-d Flow Addition:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Add IE, then the DRNS shall use this information to add the indicated E-DCH MAC-d flows.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH MAC-d Flows To Add IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flows To Add IE, then:] -[FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is

3GPP

Release 11

152

3GPP TS 25.423 V11.2.0 (2012-06)

present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] -[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] [FDD E-DCH MAC-d Flow Deletion:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration shall also be removed.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNC shall delete the EDCH configuration from the UE Context and release the E-DCH resources.] [FDD Additional E-DCH Setup:] [FDD If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Setup, then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:] [FDD If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup] - [FDD The DRNS shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.] [FDD If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the Additional E-DCH shall be setup.] - [FDD The DRNS shall setup the additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE] [FDD The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific EDPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.] [FDD If the UL SIR Target IE in the UL DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE and/or the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE are present, the DRNS shall use the information in the same same way as for the information used on Primary uplink frequency.] [FDD If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] [FDD If the Initial DL Tx Power IE, the Primary CPICH Ec/No IE, the E-AGCH Power Offset IE, the ERGCH Power Offset IE and/or the E-HICH Power Offset IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.]

3GPP

Release 11 -

153

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Enhanced Primary CPICH Ec/No IE is included in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH Secondary RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the F-DPCH Slot Format Support Request IE in the F-DPCH Information IE in the Additional EDCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Reconf IE in the RADIO RECONFIGURATION READY message. If the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE includes the F-DPCH Slot Format IE, the DRNS may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.] [FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE , the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Processing Overload Level IE are present in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the AdditionalE-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the DRNS may include the E-AGCH And E-RGCH/EHICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the AdditionalE-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message and if DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding EAGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional EDCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message the Serving Grant Value IE and

3GPP

Release 11

154

3GPP TS 25.423 V11.2.0 (2012-06)

Primary/Secondary Grant Selector IE for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE RADIO LINK RECONFIGURATION READY message.] [FDD If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Secondary CPICH Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message. If the DRNS doesnt include the Secondary CPICH Information IE, it shall not include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used.]

[FDD Additional E-DCH Configuration Change] [FDD If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Configuration Change, then the Additional E-DCH Cell Information Configuration Change IE defines the new configuration and then:] [FDD If the UL Scrambling Code IE and/or the UL SIR Target IE are present in the UL DPCH Information IE in the Additional E-DCH Configuration Change Information IE and/or id the Minimum Reduced E-DPDCH Gain Factor IE is present in the Multicell E-DCH Information IE in the Additional E-DCH Configuration Change Information IE, the DRNS shall use the information in the same way as for the information that is used on the Primary uplink frequency.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the F-DPCH Information IE in the Additional E-DCH Configuration Change Information IE, then:] - [FDD The DRNS shall configure the concerned UE Context to use F-DPCH in the downlink in the new configuration.] - [FDD If the F-DPCH Information IE includes the F-DPCH Slot Format Support Request IE, then the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the Additional E-DCH FDD Information Response IE for new RLs on the secondary UL frequency or in the Additional Modified E-DCH FDD Information Response IE for modified RLs in the RADIO LINK RECONFIGURATION READY message. If the Multicell E-DCH Information IE in the Additional E-DCH Configuration Change Information IE includes the F-DPCH Slot Format IE, the DRNS may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.] [FDD Additional E-DCH RL Addition:] [FDD If the Additional E-DCH RL Specific Information To Add IE is present in the Additional E-DCH Configuration Change Information IE, then:] [FDD The DRNS shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the E-DCH Additional RL ID IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] [FDD If the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE is included, the DRNS shall use the information in the same way as for information is used on the Primary uplink frequency.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing Additional E-DCH RL(s) and the RADIO LINK

3GPP

Release 11

155

3GPP TS 25.423 V11.2.0 (2012-06)

RECONFIGURATION PREPARE message includes the DL Reference Power IE in the Multicell EDCH RL Specific Information IE, the DRNS shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION PREPARE message at RL addition on secondary UL frequency is supported, according to subclause 8.3.15. In this case, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level which is calculated based on the following IEs (if received): Primary CPICH Ec/No IE or the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of EHICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE, the DRNS may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message and if DRNS has no valid data for the E-RGCH/ E-HICH Channelisation Code IE, then it shall insert the E-RGCH/ E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/ E-HICH Channelisation Code IE contains invalid data.] [FDD If the Primary CPICH Ec/No IE or the Primary CPICH Ec/No IE and the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE measured by the UE are included for a RL in the RADIO LINK RECONFIGURATION PREPARE message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the Primary CPICH Ec/No IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]

[FDD Additional E-DCH RL Modification:] [FDD If the Additional E-DCH RL Specific Information To Modify IE is present in the Additional EDCH Configuration Change Information IE, then the RL indicated by the E-DCH Additional RL ID IE indicates the RL on which E-DCH resources shall be modified:] -[FDD If the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE, and/or the E-DCH DL Control Channel Grant IE in the Multicell E-DCH RL Specific Information IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.]

3GPP

Release 11

156

3GPP TS 25.423 V11.2.0 (2012-06)

-[FDD If the DL Reference Power IEs is included in the Multicell E-DCH RL Specific Information IE and power balancing is active, DRNS shall apply DL power Control in the same way as defined for the Primary uplink frequency.] -[FDD If updating of power balancing parameters by the RADIO LINK RECONFIGURATION PREPARE message is supported by the DRNS, the DRNS shall include the DL Power Balancing Updated Indicator IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE for each affected RL in the RADIO LINK RECONFIGURATION READY message.] [FDD If the Phase Reference Update Indicator IE is included in the Multicell E-DCH RL Specific Information IE, DRNS shall modify the channel estimation information according to TS 25.214 [10] subclause 4.3.2.1 and set the value(s) in Primary CPICH Usage For Channel Estimation IE and/or Secondary CPICH Information Change IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message accordingly.] [FDD If the RADIO LINK RECONFIGURATION READY message includes the Primary CPICH Usage For Channel Estimation IE and/or the Secondary CPICH Information Change IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE, the DRNS shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.]

[FDD Additional E-DCH Modification:] [FDD If the Additional E-DCH FDD Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then:] -[FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Maximum Bitrate IE is included, the DRNS shall use this information for the related resource allocation operation.] -[FDD If the E-DCH Processing Overload Level IE is included, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the RNC by initiating the Radio Link Failure procedure.] -[FDD If the DL TX power upper or lower limit has been re-configured for the secondary UL frequency, the DRNS shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] -[FDD The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNS shall include in the RADIO LINK RECONFIGURATION READY message the Maximum Uplink SIR IE and Minimum Uplink SIR IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE for each Radio Link when these values are changed.] -[FDD If the Additional E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [FDD Additional E-DCH Removal] [FDD If the Additional E-DCH Cell Information RL Reconf Prep IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Removal, then the additional E-DCH on the secondary uplink frequency shall be removed.] [1.28Mcps TDD Uplink Synchronisation Parameters LCR:]

3GPP

Release 11

157

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD If the Uplink Synchronisation Parameters LCR IE is present, the DRNC shall use the indicated values of Uplink synchronisation stepsize IE and Uplink synchronisation frequency IE when evaluating the timing of the UL synchronisation.] [1.28Mcps TDD Shared physical channels Synchronisation Detection:] [1.28Mcps TDD If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the Out-of-sync Detection Window IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [1.28Mcps TDD Uplink Timing Advance Control LCR:] [1.28Mcps TDD The DRNC shall include the Uplink Timing Advance Control LCR IE in the RADIO LINK RECONFIGURATION READY message, if the Uplink Timing Advance Control parameters have been changed.] [1.28Mcps TDD PowerControl GAP:] [1.28Mcps TDD If applied in the DRNS, the DRNC may include the PowerControl GAP IE in the RADIO LINK RECONFIGURATION READY message.] [1.28Mcps TDD E-UTRAN Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Need for Idle Interval IE set to TRUE, if supported, the DRNC shall include the Idle Interval Information IE in the RADIO LINK RECONFIGURATION READY message. If the Need for Idle Interval IE is set to FALSE, the DRNC shall delete the configuration related to E-UTRAN Inter-RAT measurement ] [1.28Mcps TDD RNTI Allocation Indicator:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the RNTI Allocation Indicator IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL_FACH state.] [1.28Mcps TDD Inter-frequency/ Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the DCH Measurement Type indicator IE, if supported, the DRNS shall include the Measurement purpose IE and the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE in the RADIO LINK RECONFIGURATION READY message to configure the measurement occasion pattern(s) indicated by the DCH Measurement Type indicator IE.] [TDD DSCH RNTI Addition/Deletion:] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the PDSCH RL ID IE, then the DRNS shall use it as the new RL identifier for PDSCH and PUSCH.] [TDD If the indicated PDSCH RL ID is in the DRNS and there was no DSCH-RNTI allocated to the UE Context, the DRNC shall allocate a DSCH-RNTI to the UE Context and include the DSCH-RNTI IE in the RADIO LINK RECONFIGURATION READY message.] [TDD If the indicated PDSCH RL ID is in the DRNS and there was a DSCH-RNTI allocated to the UE Context, the DRNC shall allocate a new DSCH-RNTI to the UE Context, release the old DSCH-RNTI and include the DSCH-RNTI IE in the RADIO LINK RECONFIGURATION READY message.] [TDD If the indicated PDSCH RL ID is not in the DRNS and there was a DSCH-RNTI allocated to the UE Context, the DRNC shall release this DSCH-RNTI.]

[TDD If the RADIO LINK RECONFIGURATION PREPARE message includes a DSCHs To Delete IE and/or a USCHs To Delete IE which results in the deletion of all DSCH and USCH resources for the UE Context, then the DRNC shall release the DSCH-RNTI allocated to the UE Context, if there was one.] [FDD Phase Reference Handling:] [FDD If Primary CPICH usage for channel estimation information has been reconfigured, the DRNC shall include the Primary CPICH Usage For Channel Estimation IE in the RADIO LINK RECONFIGURATION READY message.]

3GPP

Release 11

158

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If Secondary CPICH information for channel estimation has been reconfigured, the DRNC shall include the Secondary CPICH Information Change IE in the RADIO LINK RECONFIGURATION READY message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes Phase Reference Update Indicator IE, DRNC shall modify the channel estimation information according to TS 25.214 [10] subclause 4.3.2.1 and set the value(s) in Primary CPICH Usage For Channel Estimation IE and/or Secondary CPICH Information Change IE in the RADIO LINK RECONFIGURATION READY message accordingly.] [FDD If the RADIO LINK RECONFIGURATION READY message includes the Primary CPICH Usage For Channel Estimation IE and/or the Secondary CPICH Information Change IE, the DRNC shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.] [FDD Fast Reconfiguration:] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Fast Reconfiguration Mode IE, the DRNS shall, if supported, and if it is possible to base the synchronization of the reconfiguration on the detection of the change in the uplink scrambling code for this reconfiguration, include the Fast ReconfigurationPermission IE in the RADIO LINK RECONFIGURATION READY message.] [TDD Intra- DRNS Serving E-DCH Radio Link Change:] TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:] [TDD In the new configuration the DRNS shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.] [3.84Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [1.28Mcps TDD The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE and the E-HICH Specific Information Response IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION READY message.] [7.68Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response 7.68Mcps IE in the E-DCH TDD Information Response 7.68Mcps IE in the RADIO LINK RECONFIGURATION READY message.] [TDD If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]

[TDD E-PUCH Handling:] [3.84Mcps TDD and 7.68Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes an EPUCH Information IE, the DRNS shall apply the parameters to the new configuration.] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E-PUCH Information LCR IE, the DRNS shall apply the parameters to the new configuration] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes an E- TFCS Information IE, the DRNS shall apply the beta parameters to the new configuration.] [3.84Mcps TDD E-DCH Setup:] [3.84Mcps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information IE.] [1.28Mcps TDD E-DCH Setup:]

3GPP

Release 11

159

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28cps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH informationelements: E-DCH Serving RL IE, E-PUCH Information LCR IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information LCR IE.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].] [7.68Mcps TDD E-DCH Setup:] [7.68Mcps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information 7.68Mcps IE.] [TDD- E-DCH MAC-d Flow Addition/Deletion:] [TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH MAC-d Flows To Add IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNS shall delete the EDCH configuration from the UE Context and release the E-DCH resources.] [TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d Flows To Add IE, then:] [TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for EDCH scheduling.]

[3.84Mcps TDD E-DCH Non-scheduled allocations:] [3.84Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information TDD IE in the E-DCH Information Response IE in the RADIO LINK RECONFIGURATION READY message.] [1.28Mcps TDD E-DCH Non-scheduled allocations:] [1.28Mcps The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information LCR TDD IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION READY message.] [7.68Mcps TDD E-DCH Non-scheduled allocations:] [7.68Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK RECONFIGURATION READY message.] [TDD E-DCH Modification:] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH TDD

3GPP

Release 11

160

3GPP TS 25.423 V11.2.0 (2012-06)

Information To Modify IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH MAC-d PDU Size Format IE in the E-DCH TDD Information To Modify IE, then the DRNS shall use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [3.84Mcps TDD E-DCH Modification:] [3.84Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH TDD Information IE, then:] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH TDD Maximum Bitrate IE for an EDCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

[1.28Mcps TDD E-DCH Modification:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH TDD Information LCR IE, then:] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Processing Overload Level IE for an E-DCH, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the Multi-Carrier E-DCH Physical Layer Category LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION PREPARE message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]

[7.68Mcps TDD E-DCH Modification:] [7.68Mcps TDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH TDD Information 7.68Mcps IE, then:] [7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

3GPP

Release 11 -

161

3GPP TS 25.423 V11.2.0 (2012-06)

[7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the EDCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

[TDD- If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH TDD Information To Modify IE, then:] [TDD- If the E-DCH TDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] [TDD- If the E-DCH TDD Information To Modify IE contains a TNL QoS IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [TDD- If the E-DCH TDD Information To Modify IE includes the Maximum Number of Retransmissions for EDCH IE for an E-DCH MAC-d flow then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.] [1.28Mcps TDD If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Retransmission Timer IE for an E-DCH MAC-d flow then the DRNS shall use this information to set the retransmission timer.] [TDD If the TNL QoS IE is included in the E-DCH TDD Information to Modify IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH HARQ Power Offset TDD IE for an EDCH MAC-d flow the DRNS shall use this new power offset value.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [TDD- If the E-DCH TDD Information To Modify IE contains the E-DCH Grant Type IE, the DRNS shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the DRNS shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Modify IE, the DRNS shall use this information to modify the indicated logical channels:] - [TDD If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the DRNS shall apply the values in the new configuration.] - [1.28Mcps TDD If the E-DCH Logical Channel To Modify IE includes MAC-es Maximum Bit Rate LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for EDCH scheduling.]

3GPP

Release 11

162

3GPP TS 25.423 V11.2.0 (2012-06)

- [TDD If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the DRNS shall apply the value in the new configuration.] [TDD If the E-DCH TDD Information To Modify IE includes the MAC-e Reset Indicator IE, then the DRNS shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]

[1.28Mcps TDD Multi-Carrier E-DCH Continue:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.] [1.28Mcps TDD Multi-Carrier E-DCH Setup:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Setup", then the MultiCarrier E-DCH Information LCR IE defines the new configuration and then:] [1.28Mcps TDD - The DRNS shall use the Multi-Carrier E-DCH Transport Bearer Mode LCR IE to decide the transport bearer mode in the new configuration.] [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]

[1.28Mcps TDD Multi-Carrier E-DCH Change:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Change", then: the MultiCarrier E-DCH Information LCR IE defines the new configuration and then:] [1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is different from current configured frequencies, then the DRNS shall setup the E-DCH resources, as requested in the DRNS Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.] [1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is the same as any current configured frequency, then the DRNS shall reconfigure the E-DCH resources, as requested or as configured in the DRNS Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]

[1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION PREPARE message and the choice of Continue, Setup or Change is "Change" and the Removal UL Multi-Carrier info IE is included, then the DRNS shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the UARFCN IE in the Removal UL Multi-Carrier info IE.] General If the requested modifications are allowed by the DRNC and the DRNC has successfully reserved the required resources for the new configuration of the Radio Link(s), it shall respond to the SRNC with the RADIO LINK RECONFIGURATION READY message. When this procedure has been completed successfully there exists a Prepared Reconfiguration, as defined in subclause 3.1. If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Layer Address IE and Binding ID IE in the [TDD DSCHs To Modify IE, DSCHs To Add IE, USCHs To Modify IE, USCHs To Add IE], HS-DSCH Information IE, HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE, [FDD RL Specific E-DCH Information IE,] [TDD E-DCH MAC-d Flows to Add IE,] [TDD E-DCH TDD Information to Modify IE,] or in the RL Specific DCH Information IEs, the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE is not included] being added, or any Transport Channel, HSDSCH MAC-d flow or E-DCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE.

3GPP

Release 11

163

3GPP TS 25.423 V11.2.0 (2012-06)

The DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Transport Layer Address IE and the Binding ID IE for any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE is not included] being added, or any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE was not included], HS-DSCH MAC-d flow or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE. In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iur interface, the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE shall be included [FDD if the Transport Bearer Not Requested Indicator IE is not included for the corresponding DCH,] for only one of the DCHs in the set of co-ordinated DCHs. [FDD If the RADIO LINK RECONDIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer Shall not be Established for a DCH or an E-DCH MAC-d flow, then the DRNC shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.] [FDD If the RADIO LINK RECONDIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for a DCH or an E-DCH MAC-d flow and:] [FDD if the DRNC establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.] [FDD if the DRNC does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION READY message.]

In the case of a Radio Link being combined with another Radio Link within the DRNS, the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE shall be included for only one of the combined Radio Links [FDD if the Transport Bearer Not Requested Indicator IE is not included for this DCH of the Radio Link]. [FDD In the case of an E-DCH RL being combined with another E-DCH RL within the DRNS, the E-DCH FDD Information Response IE shall be included only for one of the combined E-DCH RLs.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Additional E-DCH Cell Information RL Reconf Prep IE, then:] - [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to Separate Iur Transport Bearer Mode the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to UL Flow Multiplexing Mode the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] [FDD if Separate Iur Transport Bearer Mode is used in the new configuration, then:] - [FDD the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information IE in the RL Information IE and/or the Transport Bearer Request Indicator IE in the E-DCH FDD Information To Modify IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] - [FDD If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE or in the Additional E-DCH RL Specific Information To Add IE and/or the Additional E-DCH RL Specific Information To Modify IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information Configuration Change IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MACd flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION READY message in the Additional E-DCH Cell Information Response RLReconf IE

3GPP

Release 11

164

3GPP TS 25.423 V11.2.0 (2012-06)

the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE for new E-DCH radio links on the Secondary UL frequency and/or include the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional Modified E-DCH FDD Information Response IE for radio links on the Secondary UL frequency that has been modified.] [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION PREPARE message includes the Multi-Carrier E-DCH Information Reconf IE, then:] [1.28Mcps TDD - If the Multi-carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iur Transport Bearer Mode" the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "UL Flow Multiplexing Mode" the DRNS shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.] [1.28Mcps TDD - If the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf IE is "Setup" and the Separate Iur transport bearer mode is used in the new configuration, or if the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf IE is "Change" and the Transport Bearer Mode is changed to "Separate Iur Transport Bearer Mode" indicated by Multi-carrier EDCH Transport Bearer Mode LCR IE, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] [1.28Mcps TDD - The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Request Indicator IE in the E-DCH TDD Information to Modify IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.] [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the Transport Bearer Request Indicator IE is set to " Bearer Requested ", then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION READY message for establishment of a transport bearer for every E-DCH MACd flow being established.]

Any allowed rate for the uplink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Allowed UL Rate IE in the DCH Information Response IE for this Radio Link. Any allowed rate for the downlink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Allowed DL Rate IE in the DCH Information Response IE for this Radio Link. The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s) and the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Maximum Uplink SIR IE and Minimum Uplink SIR IE for each Radio Link when these values are changed. [FDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include in the RADIO LINK RECONFIGURATION READY message the Maximum DL TX Power IE and Minimum DL TX Power IE respectively. The DRNS shall not transmit with a higher power than indicated by the Maximum DL TX Power IE or lower than indicated by the Minimum DL TX Power IE on any DL DPCH or on the F-DPCH of the RL except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the Pcurr, as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] [3.84 Mcps TDD and 7.68 Mcps TDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK RECONFIGURATION READY message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the new value(s) for that CCTrCH in the CCTrCH Maximum DL TX Power IE

3GPP

Release 11

165

3GPP TS 25.423 V11.2.0 (2012-06)

and CCTrCH Minimum DL TX Power. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE/CCTrCH Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE on any DL DPCH within each CCTrCH of the RL.] [1.28 Mcps TDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK RECONFIGURATION READY message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the new value(s) for that timeslot in the Maximum DL TX Power IE and Minimum DL TX Power within the DL Timeslot Information LCR IE. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE on any DL DPCH within each timeslot of the RL.] [TDD If the [3.84Mcps TDD and 7.68 Mcps TDD DL Time Slot ISCP Info IE][1.28Mcps TDD DL Time Slot ISCP Info LCR IE] is present, the DRNS should use the indicated values when deciding the Initial DL TX Power.] [TDD If the Primary CCPCH RSCP Delta IE is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included and the Primary CCPCH RSCP IE is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP IE. The DRNS shall use the indicated values when deciding the Initial DL TX Power.]

8.3.4.3

Unsuccessful Operation
SRNC DRNC Layer RADIO LINK RECONFIGURATION PREPARELayer
RADIO LINK RECONFIGURATION FAILURE

Figure 11: Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation If the DRNS cannot reserve the necessary resources for all the new DCHs of a set of co-ordinated DCHs requested to be added, it shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed. If the requested Synchronised Radio Link Reconfiguration Preparation procedure fails for one or more RLs, the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC, indicating the reason for failure for each failed radio link in a Cause IE. [FDD If the MIMO Activation Indicator IE is included and the Power Offset For S-CPICH for MIMO Request Indicator IE is not included in the HS-DSCH FDD Information IE in the HS-DSCH FDD Information IE in the RADIO LINK RECONFIGURATION PREPARE message or MIMO is activated and the power offset for S-CPICH for MIMO Request indicator has not been configured in the new configuration but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the Cause IE.] Typical cause values are: Radio Network Layer Causes: UL Scrambling Code Already in Use; DL Radio Resources not Available; UL Radio Resources not Available; Requested Configuration not Supported; Number of DL Codes not Supported; Number of UL Codes not Supported; Dedicated Transport Channel Type not Supported; DL Shared Channel Type not Supported; [TDD UL Shared Channel Type not Supported;] [FDD UL Spreading Factor not Supported;] [FDD DL Spreading Factor not Supported;] CM not Supported; RL Timing Adjustment not Supported;

3GPP

Release 11

166

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH not supported; [FDD F-DPCH not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not Supported;] [FDD Continuous Packet Connectivity HS-SCCH less operation not Supported;] [FDD MIMO not supported;] [FDD E-DCH TTI2ms not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not available;] [FDD Continuous Packet Connectivity UE DTX Cycle not available;] [FDD MIMO not available;] [FDD SixteenQAM UL not Supported;] HS-DSCH MAC-d PDU Size Format not supported; [FDD F-DPCH Slot Format operation not supported;] E-DCH MAC-d PDU Size Format not available; [FDD E-DPCCH Power Boosting not supported;] [FDD SixtyfourQAM DL and MIMO Combined not available;] [FDD Multi Cell operation not available;] [FDD Multi Cell operation not supported;] [FDD SixtyfourQAM DL and MIMO Combined not supported;] [1.28Mcps TDD- MIMO not supported;] [1.28Mcps TDD MIMO not available;] [1.28Mcps TDD SixtyfourQAM DL and MIMO Combined not available;] [FDD TX diversity for MIMO UE on DL Control Channels not available;] [FDD Single Stream MIMO not supported;] [FDD Single Stream MIMO not available;] [FDD Multi Cell operation with MIMO not available;] [FDD Multi Cell operation with MIMO not supported;] [FDD Multi Cell E-DCH Operation not supported;] [FDD Multi Cell E-DCH Operation not available;] [FDD Multi Cell operation with Single Stream MIMO not available;] [FDD Multi Cell operation with Single Stream MIMO not supported;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available;] [FDD Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Supported.] Miscellaneous Causes: Control Processing Overload; Not enough User Plane Processing Resources.

8.3.4.4

Abnormal Conditions

If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC. If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected [TDD or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected] the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message includes a DCHs To Modify IE or DCHs To Add IE with multiple DCH Specific Info IEs, and if the DCHs in the DCHs To Modify IE or DCHs To Add IE do not have the same Transmission Time Interval IE in the Semi-static Transport Format Information IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RL Information IE includes the DL Reference Power IE, but the power balancing is not active in the indicated RL(s), the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value Power Balancing status not compatible.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Common in the existing RL(s) but the RADIO LINK RECONFIGURATION PREPARE message includes more than

3GPP

Release 11

167

3GPP TS 25.423 V11.2.0 (2012-06)

one DL Reference Power IE, the DRNS shall reject the Synchronised Radio Link Reconfiguration Preparation procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value Power Balancing status not compatible.] If the RADIO LINK RECONFIGURATION PREPARE message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE., and not both are present for a transport bearer intended to be established, the DRNC shall reject the Synchronised Radio Link Reconfiguration Preparation procedure and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE or HS-DSCH MAC-d Flows To Delete IE in addition to the HS-DSCH Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE, HS-DSCH MAC-d Flows To Delete IE or HS-PDSCH RL ID IE and the Serving HS-DSCH Radio Link is not in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information IE and does not include the HS-PDSCH RL-ID IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-DSCH Information To Modify IE deleting the last remaining Priority Queue of an HS-DSCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message includes the HS-PDSCH RL-ID IE indicating a Radio Link not existing in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION PREPARE message contains any of the HS-DSCH Information IE, HSDSCH Information To Modify IE, or HS-DSCH MAC-d Flows To Add IE and if in the new configuration the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Indexed MAC-d PDU Size for an HSDSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MACd PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Flexible MAC-d PDU Size for an HSDSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Fixed MAC-d PDU Size for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Flexible MAC-d PDU Size for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the F-DPCH Information IE and the DL DPCH Information IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If the RADIO LINK RECONFIGURATION PREPARE message includes HS-DSCH Information IE and the HS-DSCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.

3GPP

Release 11

168

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the concerned UE Context is configured to use DPCH in the downlink in the old configuration and if the RADIO LINK RECONFIGURATION PREPARE message includes the DL DPCH Power Information IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to use F-DPCH in the downlink in the old configuration and the RADIO LINK RECONFIGURATION PREPARE message includes at least one but not all of the TFCS IE, DL DPCH Slot Format IE, TFCI Signalling Mode IE, Multiplexing Position IE, Limited Power Increase IE and DL DPCH Power Information IE in the DL DPCH Information IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION PREPARE message, but the E-DPCH Information IE is not present or if any of the Maximum Set of E-DPDCHs IE, Puncture Limit IE, ETFCS Information IE, E-TTI IE, E-DPCCH Power Offset IE, E-RGCH 2-Index-Step Threshold IE, E-RGCH 3-IndexStep Threshold IE, HARQ Info for E-DCH IE or HS-DSCH Configured Indicator IE are not present in the E-DPCH Information IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH RL Indication IE set to E-DCH, but no E-DCH FDD Information IE, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If the RADIO LINK RECONFIGURATION PREPARE message contains the HS-PDSCH RL ID IE and/or the Serving E-DCH RL IE and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the HS-PDSCH RL ID IE and the EDPCH Information IE which includes the HS-DSCH Configured Indicator IE set as HS-DSCH not configured then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE or E-DCH MAC-d Flows To Delete IE in addition to the E-DCH FDD Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE, E-DCH MAC-d Flows To Delete IE and the UE Context is not configured for E-DCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the E-DCH FDD Information To Modify IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes E-DCH FDD Information IE and the E-DCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION PREPARE message and the UL Scrambling Code IE does not indicate an uplink scrambling code different from the currently used uplink scrambling code the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE in addition to the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE in addition to the Continuous Packet Connectivity HS-SCCH less Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. ]

3GPP

Release 11

169

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE while the Continuous Packet Connectivity HS-SCCH less configuration isnt configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DTX-DRX configuration isnt configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the DRX Information To Modify IE in Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DRX configuration is not configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to Uplink DCH only but no Transport Format Set IE for the uplink for this DCH and the DRNC had ignored the configuration of Transport Format Set for uplink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to Downlink DCH only but no Transport Format Set IE for the downlink for this DCH and the DRNC had ignored the configuration of Transport Format Set for downlink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d flow but does not contain the corresponding DCH ID IE and the Unidirectional DCH indicator IE set to Uplink DCH only for the DCH in DCH Information To Add IE or does not contain the corresponding E-DCH MAC-d Flow ID IE in E-DCH MAC-d Flows Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply UL DPCCH Slot Format 4 but is not configured to use FDPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply the Closed loop mode 1 and if the concerned UE Context is not configured to apply UL DPCCH Slot Format 2 or 3, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply MIMO, allowed to apply 64QAM, establish the secondary serving HS-DSCH Radio Link or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE for a DCH in the RL Specific DCH Information IE but does not include the DCH ID IE for the DCH in the DCHs to Add IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE for an E-DCH MAC-d flow in the RL Specific E-DCH Information IE but does not include the E-DCH MAC-d flow ID IE for the E-DCH MAC-d flow in the E-DCH MAC-d flows Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Continuous Packet Connectivity DTX-DRX Information IE but does not contain the F-DPCH Information IE and the concerned UE Context is not previously configured to use F-DPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message]

3GPP

Release 11

170

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the concerned UE Context is configured to have the Serving E-DCH Radio Link but there is at least one EDCH MAC-d flow which the transport bearer is not configured for the Serving E-DCH Radio Link in DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message includes the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional HS Cell Information RL Reconf Prep IE indicating a new seconadry serving cell that is not in the same Node B as the serving HS-DSCH cell (or new serving in case of simultaneous serving HS-DSCH cell change), then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message] If ALCAP is not used, if the concerned UE Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION PREPARE message does not include the Transport Layer Address IE and the Binding ID IE for the DCH, the E-DCH MAC-d flow and/or the HS-DSCH MACd flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [TDD If ALCAP is not used, if the concerned UE Context is configured to establish a DSCH and/or a USCH but the RADIO LINK RECONFIGURATION PREPARE message does not include the Transport Layer Address IE and the Binding ID IE for the DSCH and/or the USCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Flexible RLC PDU Size for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Flexible RLC PDU Size, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH Cell Information RL Reconf Prep IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH Cell Information RL Reconf Prep IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE in the Additional E-DCH Cell Information RL Reconf Prep IE and the C-ID IE is not included but the RL indicated by the E-DCH Additional RL ID IE is not configured in the current UE context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Diversity Mode IE in the HSDSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE and the secondary serving HS-DSCH is already configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]

3GPP

Release 11

171

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the secondary serving HS-DSCH is not configured in the UE Context and if the RADIO LINK RECONFIGURATION PREPARE message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Prep IE the Diversity Mode IE not set to None but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to None, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION PREPARE message contains the Diversity Mode IE in the Secondary Serving Information To Modify IE in the Additional HS Cell Information RL Reconf Prep IE and the Non Cell Specific Tx Diversity IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional HS Cell Information RL Reconf Prep IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE or the HS-DSCH FDD Secondary Serving Information To Modify IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD - If the RADIO LINK RECONFIGURATION PREPARE message contains the Additional HS Cell Information RL Reconf Prep IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]

8.3.5 Synchronised Radio Link Reconfiguration Commit

8.3.5.1 General
This procedure is used to order the DRNS to switch to the new configuration for the Radio Link(s) within the DRNS, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context.

8.3.5.2

Successful Operation
SRNC Layer DRNC Layer

RADIO LINK RECONFIGURATION COMMIT

Figure 12: Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation The DRNS shall switch to the new configuration previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure at the configuration switching point occurring: [TDD at the next coming CFN with a value equal to the value requested by the SRNC in the CFN IE (see TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the SRNC.] [FDD if the Fast Reconfiguration IE is not included in the RADIO LINK RECONFIGURATION COMMIT message at the next coming CFN with a value equal to the value requested by the SRNC in the CFN IE (see TS 25.402 [17] subclause 9.4) when receiving the RADIO LINK RECONFIGURATION COMMIT message from the SRNC.] [FDD if the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION COMMIT message as soon as the DRNS detects that the UE uses the new configuration in the uplink (e.g. the NodeB indicates that the UE uses the new scrambling code used for the uplink by sending the RADIO LINK RESTORATION message). In order to limit the period for the detection in the DRNS the CFN in the RADIO LINK RECONFIGURATION COMMIT message indicates the earliest possible time instant at which the UE might use the new configuration.]

3GPP

Release 11

172

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Active Pattern Sequence Information IE is included in the RADIO LINK RECONFIGURATION COMMIT message, the CM Configuration Change CFN IE in the Active Pattern Sequence Information IE shall be ignored by the DRNS.] [FDD If the Active Pattern Sequence Information IE is not included in the RADIO LINK RECONFIGURATION COMMIT message and a new Compressed Mode Configuration exists in the prepared configuration, the DRNS shall behave as if an Active Pattern Sequence Information IE with an empty Transmission Gap Pattern Sequence Status IE was included.] When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1. In the case of a Transport Channel or MAC-d flow modification for which a new transport bearer was requested and established, the switch to the new transport bearer shall also take place at the configuration switching point (defined above) indicated CFN. The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [4], subclause 5.10.1, and in TS 25.425 [32], subclauses 5.3.1 and 5.3.2. [FDD If the RADIO LINK RECONFIGURATION COMMIT includes the Active Pattern Sequence Information IE, the DRNS shall deactivate all the ongoing Transmission Gap Pattern Sequences at the configuration switching point (defined above). From that moment on all Transmission Gap Pattern Sequences included in Transmission Gap Pattern Sequence Status IE repetitions shall be started when the indicated TGCFN IE elapses. The CFN IE and TGCFN IE for each sequence refer to the next coming CFN with that value. If the values of the CFN IE and the TGCFN IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the CFN IE.] [FDD If the RADIO LINK RECONFIGURATION COMMIT message includes the Active Pattern Sequence Information IE and the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.] [FDD - If the RADIO LINK RECONFIGURATION COMMIT message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]

8.3.5.3

Abnormal Conditions

If a new transport bearer is required for the new configuration and it is not available at the requested configuration switching point (defined in sub-clause 8.3.3.2), the DRNS shall initiate the Radio Link Failure procedure. [FDD If the Fast Reconfiguration IE is included in the RADIO LINK RECONFIGURATION COMMIT message and the DRNC did not include the Fast ReconfigurationPermission IE in the RADIO LINK RECONFIGURATION READY message, the DRNC shall initiate the Radio Link Failure procedure.] [FDD - If the RADIO LINK RECONFIGURATION COMMIT message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and theTransmission Gap Pattern Sequence for affected HSDSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall initiate the Radio Link Failure procedure with the cause value Invalid CM Settings.]

8.3.6 Synchronised Radio Link Reconfiguration Cancellation

8.3.6.1 General
This procedure is used to order the DRNS to release the new configuration for the Radio Link(s) within the DRNS, previously prepared by the Synchronised Radio Link Reconfiguration Preparation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context.

3GPP

Release 11

173

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.6.2

Successful Operation

Figure 13: Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation Upon receipt of the RADIO LINK RECONFIGURATION CANCEL message from the SRNC, the DRNS shall release the new configuration ([FDD including the new Transmission Gap Pattern Sequence parameters (if existing)]) previously prepared by the Synchronised RL Reconfiguration Preparation procedure and continue using the old configuration. When this procedure has been completed the Prepared Reconfiguration does not exist any more, see subclause 3.1.

8.3.6.3
-

Abnormal Conditions

8.3.7 Unsynchronised Radio Link Reconfiguration

8.3.7.1 General
The Unsynchronised Radio Link Reconfiguration procedure is used to reconfigure Radio Link(s) related to one UE-UTRAN connection within a DRNS. The procedure is used when there is no need to synchronise the time of the switching from the old to the new radio link configuration in the cells used by the UE-UTRAN connection within the DRNS. This procedure shall use the signalling bearer connection for the relevant UE Context. The Unsynchronised Radio Link Reconfiguration procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.7.2

Successful Operation
SRNC DRNC Layer Layer RADIO LINK RECONFIGURATION REQUEST
RADIO LINK RECONFIGURATION RESPONSE

Figure 14: Unsynchronised Radio Link Reconfiguration procedure, Successful Operation The Unsynchronised Radio Link Reconfiguration procedure is initiated by the SRNC by sending the RADIO LINK RECONFIGURATION REQUEST message to the DRNC. Upon receipt, the DRNS shall modify the configuration of the Radio Link(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications. If the RADIO LINK RECONFIGURATION REQUEST message includes the Allowed Queuing Time IE the DRNS may queue the request the time corresponding to the value of the Allowed Queuing Time IE before starting to execute the request. The DRNS shall prioritise resource allocation for the RL to be modified according to Annex A. If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK RECONFIGURATION REQUEST message, the DRNS shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE. DCH Modification:

3GPP

Release 11

174

3GPP TS 25.423 V11.2.0 (2012-06)

If the RADIO LINK RECONFIGURATION REQUEST message includes any DCHs To Modify IEs, then the DRNS shall treat them as follows: If the DCHs To Modify IE includes multiple DCH Specific Info IEs, then the DRNS shall treat the DCHs as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if it can include all of them in the new configuration. If the DCHs To Modify IE includes the UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE includes the ToAWS IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWS in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE includes the ToAWE IE for a DCH or a set of co-ordinated DCHs to be modified, the DRNS shall apply the new ToAWE in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCHs To Modify IE contains a DCH Specific Info IE which includes a Transport Format Set IE for the UL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Uplink of this DCH in the new configuration. If the DCHs To Modify IE contains a DCH Specific Info IE which includes a Transport Format Set IE for the DL of a DCH to be modified, the DRNS shall apply the new Transport Format Set in the Downlink of this DCH in the new configuration. If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Frame Handling Priority IE, the DRNS should store this information for this DCH in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the radio interface in congestion situations within the DRNS once the new configuration has been activated. If the DCH Specific Info IE includes the Traffic Class IE, the DRNC may use this information to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this DCH indicates the value RRC. [FDD If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to Uplink DCH only, the DRNS shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH.] [FDD If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH indicator IE set to Downlink DCH only, the DRNS shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH.] If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs. If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this DCH in the new configuration according to Annex A. [TDD If the DCHs To Modify IE contains a DCH Specific Info IE which includes the CCTrCH ID IE for the UL, the DRNS shall map the DCH onto the referenced UL CCTrCH in the new configuration.] [TDD If the DCHs To Modify IE contains a DCH Specific Info IE which includes the CCTrCH ID IE for the DL, the DRNS shall map the DCH onto the referenced DL CCTrCH in the new configuration.] If the DCHs To Modify IE contains a DCH Specific Info IE which includes the Guaranteed Rate Information IE, the DRNS shall treat the included IEs according to the following: - If the Guaranteed Rate Information IE includes the Guaranteed UL Rate IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate in the uplink of the DCH at any point in time after activating the new

3GPP

Release 11

175

3GPP TS 25.423 V11.2.0 (2012-06)

configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. - If the Guaranteed Rate Information IE includes the Guaranteed DL Rate IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user in the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. DCH Addition: If the RADIO LINK RECONFIGURATION REQUEST message includes any DCHs To Add IEs, then the DRNS shall treat them each as follows: The DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message and include these DCH in the new configuration. If the DCHs To Add IE includes multiple DCH Specific Info IEs then the DRNS shall treat the DCHs in the DCHs To Add IE as a set of co-ordinated DCHs. The DRNS shall include these DCHs in the new configuration only if all of them can be in the new configuration. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Uplink DCH only, the DRNS shall ignore the Transport Format Set IE for the downlink for this DCH. As a consequence this DCH is not included as a part of the downlink CCTrCH. If the DCH Specific Info IE includes the Unidirectional DCH Indicator IE set to Downlink DCH only, the DRNS shall ignore the Transport Format Set IE for the uplink for this DCH. As a consequence this DCH is not included as a part of the uplink CCTrCH. [FDD For each DCH which does not belong to a set of co-ordinated DCHs, and which includes a QE-Selector IE set to selected, the DRNS shall use the Transport channel BER from that DCH for the QE in the UL data frames. If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If the QE-Selector IE is set to non-selected, the DRNS shall use the Physical channel BER for the QE in the UL data frames, TS 25.427 [4].] For a set of co-ordinated DCHs, the DRNS shall use the Transport channel BER from the DCH with the QE-Selector IE set to selected for the QE in the UL data frames, TS 25.427 [4]. [FDD If no Transport channel BER is available for the selected DCH, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4]. If all DCHs have the QE-Selector IE set to non-selected, the DRNS shall use the Physical channel BER for the QE, TS 25.427 [4].] [TDD If no Transport channel BER is available for the selected DCH, the DRNS shall use 0 for the QE, TS 25.427 [4].] The DRNS should store the Frame Handling Priority IE received for a DCH to be added in the new configuration. The received Frame Handling Priority should be used when prioritising between different frames in the downlink on the Uu interface in congestion situations within the DRNS once the new configuration has been activated. The Traffic Class IE may be used to determine the transport bearer characteristics to apply between DRNC and Node B for the related DCH or set of co-ordinated DCHs. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE indicates the value RRC. If the TNL QoS IE is included for a DCH or a set of co-ordinated DCHs and if ALCAP is not used, the DRNS may use this information to determine the transport bearer characteristics to apply for the uplink for the related DCH or set of co-ordinated DCHs. The DRNS shall use the included UL FP Mode IE for a DCH or a set of co-ordinated DCHs to be added as the new FP Mode in the Uplink of the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. The DRNS shall use the included ToAWS IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Startpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration.

3GPP

Release 11 -

176

3GPP TS 25.423 V11.2.0 (2012-06)

The DRNS shall use the included ToAWE IE for a DCH or a set of co-ordinated DCHs to be added as the new Time of Arrival Window Endpoint in the user plane for the DCH or the set of co-ordinated DCHs in the new configuration. If the DCH Specific Info IE includes the Guaranteed Rate Information IE, the DRNS shall treat the included IEs according to the following: - If the Guaranteed Rate Information IE includes the Guaranteed UL Rate IE, the DRNS shall apply the new Guaranteed Rate in the uplink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the uplink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the uplink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCH Information IE does not include the Guaranteed UL Rate IE, the DRNS shall not limit the user rate of the uplink of the DCH. - If the Guaranteed Rate Information IE includes the Guaranteed DL Rate IE, the DRNS shall apply the new Guaranteed Rate in the downlink of this DCH in the new configuration. The DRNS may decide to request the SRNC to limit the user rate of the downlink of the DCH at any point in time after activating the new configuration. The DRNS may request the SRNC to reduce the user rate of the downlink of the DCH below the guaranteed bit rate, however, whenever possible the DRNS should request the SRNC to reduce the user rate between the maximum bit rate and the guaranteed bit rate. If the DCH Specific Info IE in the DCH Information IE does not include the Guaranteed DL Rate IE, the DRNS shall not limit the user rate of the uplink of the DCH.

DCH Deletion: If the RADIO LINK RECONFIGURATION REQUEST message includes any DCHs To Delete IEs, the DRNS shall not include the referenced DCHs in the new configuration. If all of the DCHs belonging to a set of co-ordinated DCHs are requested to be deleted, the DRNS shall not include this set of co-ordinated DCHs in the new configuration. [FDD Physical Channel Modification:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an UL DPCH Information IE, then the DRNS shall apply the parameters to the new configuration as follows: ] [FDD If the UL DPCH Information IE includes the TFCS IE for the UL, the DRNS shall apply the new TFCS in the Uplink of the new configuration.] [FDD If the UL DPCH Information IE includes the UL DPDCH Indicator For E-DCH Operation IE set to UL DPDCH not present, the UL DPDCH resources shall be removed from the configuration.]

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes a DL DPCH Information IE, then the DRNS shall apply the parameters to the new configuration as follows:] [FDD If the DL DPCH Information IE includes the TFCS IE for the DL, the DRNS shall apply the new TFCS in the Downlink of the new configuration.] [FDD If the DL DPCH Information IE includes the TFCI Signalling Mode IE for the DL, the DRNS shall apply the new TFCI Signalling Mode in the Downlink of the new configuration.] [FDD If the DL DPCH Information IE includes the Limited Power Increase IE and the IE is set to Used, the DRNS shall, if supported, use Limited Power Increase according to TS 25.214 [10] subclause 5.2.1 for the inner loop DL power control in the new configuration.] [FDD If the DL DPCH Information IE includes the Limited Power Increase IE and the IE is set to Not Used, the DRNS shall not use Limited Power Increase for the inner loop DL power control in the new configuration.]

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transmission Gap Pattern Sequence Information IE, the DRNS shall store the new information about the Transmission Gap Pattern Sequences to be used in the new Compressed Mode configuration. Any Transmission Gap Pattern Sequences already existing in the previous Compressed Mode Configuration are replaced by the new sequences once the new Compressed Mode

3GPP

Release 11

177

3GPP TS 25.423 V11.2.0 (2012-06)

Configuration has been activated. This new Compressed Mode Configuration shall be valid in the DRNS until the next Compressed Mode Configuration is configured in the DRNS or last Radio Link is deleted.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transmission Gap Pattern Sequence Information IE, and if the Downlink Compressed Mode Method in one or more Transmission Gap Pattern Sequence within the Transmission Gap Pattern Sequence Information IE is set to SF/2, the DRNC shall include the DL Code Information IE in the RADIO LINK RECONFIGURATION RESPONSE message, without changing any of the DL Channelisation Codes or DL Scrambling Codes, indicating for each DL Channelisation Code whether the alternative scrambling code shall be used or not.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DPCH Information IE which contains the E-TFCS Information IE, the DRNS shall use the E-TFCS Information IE for the E-DCH when reserving resources for the uplink of the new configuration. The DRNS shall apply the new TFCS in the uplink of the new configuration. If the E-TFCS Information IE contains the E-DCH Minimum Set E-TFCI Validity Indicator IE the DRNS shall ignore the value in E-DCH Minimum Set E-TFCI IE. If the E-DCH Minimum Set E-TFCI validity indicator IE is absent DRNS shall use the value for the related resource allocation operation.] [FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the DRNS shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the EDPDCH Power Interpolation IE is not present, the DRNS shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION REQUEST message.] FDD If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the DRNS shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the DRNS shall use the value 127 in the algorithm defined in TS 25.214 [10] if the E-DCH FDD Information IE is included in the RADIO LINK RECONFIGURATION REQUEST message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-DPCCH Power Offset IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-RGCH 2-Index-Step IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the E-RGCH 3-Index-Step IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the HARQ Info for E-DCH IE, the DRNS shall use the value when the new configuration is being used.] [FDD If the RADIO LINK RECONFIGURATION REQUEST includes an E-DPCH Information IE which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the DRNS shall use the value to determine the applicable minimum gain factor (ed,k,reduced,min) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the UE Context, the DRNS may use the default value defined in TS 25.331 [16]. ] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information IE, then:] [FDD The DRNS shall configure the concerned UE Context for Continuous Packet Connectiviy DTX operation according to TS 25.214 [10].] [FDD If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNS shall configure the concerned UE Context for Continuous Packet Connectiviy DRX operation according to TS 25.214 [10].]

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then:] -[FDD If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.]

3GPP

Release 11

178

3GPP TS 25.423 V11.2.0 (2012-06)

-[FDD If the Enabling Delay IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.214 [10] .] -[FDD If the DTX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this information to modify the indicated DTX Information parameter in the new configuration. If the choice of DTX Information To Modify IE is Deactivate, then DRX should be deactived together with DTX.] -[FDD If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DTX-DRX Information To Modify IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:] [FDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for Continuous Packet Connectiviy HS-SCCH less operation according to TS 25.214 [10].] [FDD The DRNS shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If at least one of HS-PDSCH Second Code Support IE is set to True, then the DRNC shall include HSPDSCH Second Code Index IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[FDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE, then the DRNS shall deactive the Continuous Packet Connectivity HS-SCCH less operation for the HS-DSCH Radio Link.] [FDD - UL CLTD Setup:] [FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Setup", then: the DRNS shall setup the requested UL CLTD resources for the concerned UE Context in the cell to determine the precoding weights according the new configuration defined in the UL CLTD Information IE and then:] [FDD - If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the UE Context, the C-ID IE shall be included in the UL CLTD Information IE, and the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context.] [FDD - If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the DRNS shall use this value to configure the state of UL CLTD for the concerned UE Context.]

[FDD - UL CLTD Modification:] [FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Configuration Change", then: the UL CLTD Information To Modify IE defines the new configuration and then:] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE in the UL CLTD Information To Modify IE, then the DRNS shall configure this cell to determine the precoding weights for the concerned UE Context. Otherwise the DRNS shall configure the serving E-DCH cell or the HS_DSCH serving cell to determine the precoding weights as specified in TS 25.319[38]. The UL CLTD configuration is only valid for the cell to determine the precoding weights.] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the S-DPCCH Power Offset Information IE in the UL CLTD Information To Modify IE, then the DRNS shall use this value to determine the S-DPCCH power.] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the UL CLTD State Activation Information IE in the UL CLTD Information To Modify IE, then the DRNS shall use this value to update the local state of UL CLTD for the concerned UE Context. If the UL CLTD Activation Information IE is set to "De-activated", the DRNS should release the F-TPICH resource configured for the concerned UE Context.]]

3GPP

Release 11 [FDD - UL CLTD Removal:]

179

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD - If the UL CLTD Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of UL CLTD is "Removal", then the configured UL CLTD for the concerned UE Context shall be removed.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS shall take account into these parameters to decide the DRX operation related parameters and configure the concerned UE Context for DRX operation according to TS 25.224 [22] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD - If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the DRNS may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [22].] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DRX Information To Modify LCR IE, then:] -[1.28 Mcps TDD If the UE DTX DRX Offset IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall apply the indicated Offset in UE DTX DRX Cycle IE in the new configuration.] -[1.28 Mcps TDD If the Enabling Delay IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [22].] -[1.28 Mcps TDD If the DRX Information To Modify IE is included in the Continuous Packet Connectivity DRX Information To Modify LCR IE, then the DRNS shall use this information to modify the indicated DRX Information in the new configuration.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH SemiPersistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH SemiPersistent scheduling Information LCR IE, then:] [1.28 Mcps TDD The DRNS shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22].] [1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the DRNS shall include Allocated E-DCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH SemiPersistent scheduling Information to modify LCR IE, then:] [1.28 Mcps TDD If the Transport Block Size List IE or/and Repetition Period list IE is/are included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, the DRNS shall modifiy the configuration of Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [22].

3GPP

Release 11 -

180

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28 Mcps TDD The DRNS shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall include Allcoated HSPDSCH Semi-persistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD If the HS-DSCH Semi-Persistent scheduling operation Indicator IE is included in the HSDSCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall apply this information for HS-DSCH Semi-Persistent scheduling operation.] [1.28 Mcps TDD If the buffer size for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD If the number of processes for HS-DSCH Semi-Persistent scheduling needs to be modified, then the DRNS shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION RQUEST message includes the E-DCH SemiPersistent scheduling Information to modify LCR IE, then:] [1.28 Mcps TDD If the Repetition Period list IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, the DRNS shall modifiy the configuration of Serving HS-DSCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [22]. [1.28 Mcps TDD If the E-DCH Semi-Persistent scheduling Indicator IE is included in the E-DCH SemiPersistent scheduling Information to modify LCR IE, then the DRNS shall apply this information for E-DCH Semi-Persistent scheduling operation.] [1.28 Mcps TDD - If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information to modify LCR IE, then the DRNS shall include Allocated E-DCH Semipersistent resource IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH SemiPersistent scheduling Deactivate Indicator LCR IE, then the DRNS shall deactivate the HS-DSCH Semi-Persistent scheduling operation for the HS-DSCH Radio Link.] [1.28 Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH SemiPersistent scheduling Deactivate Indicator LCR IE, then the DRNS shall deactivate the E-DCH Semi-Persistent scheduling operation for the E-DCH Radio Link.] [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the MU-MIMO Indicator IE, then:] [1.28 Mcps TDD the DRNS may use the MU-MIMO for the radio link according to the MU-MIMO Usage Indicator IE and shall include the MU-MIMO Information IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28 Mcps TDD If the Standalone Midamble Channel Indicator IE is set to "Used", then the DRNS shall include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION RESPONSE message. Else, the DRNS shall not include Standalone Midamble Channel information in the RADIO LINK RECONFIGURATION RESPONSE message.]

[TDD UL/DL CCTrCH Modification] [TDD If the RADIO LINK RECONFIGURATION REQUEST message includes any UL CCTrCH To Modify IE or DL CCTrCH To Modify IE, the DRNS shall reserve necessary resources for the new configuration of the Radio Link(s) according to the parameters given in the message.] [TDD If the RADIO LINK RECONFIGURATION REQUEST message includes any UL CCTrCH Information To Modify IEs or DL CCTrCH Information To Modify IEs which contain a TFCS IE, the DRNS shall apply the included

3GPP

Release 11

181

3GPP TS 25.423 V11.2.0 (2012-06)

TFCS IE as the new value(s) to the referenced CCTrCH. Otherwise the DRNS shall continue to apply the previous value(s) specified for this CCTrCH.] [1.28Mcps TDD If the UL CCTrCH To Modify IE includes UL SIR Target IE, the DRNS shall apply this value as the new configuration and use it for the UL inner loop power control according to TS 25.221 [12] and TS 25.224 [22].] [TDD UL/DL CCTrCH Deletion] [TDD If the RADIO LINK RECONFIGURATION REQUEST message includes any UL CCTrCH Information To Delete IEs or DL CCTrCH Information To Delete IEs, the DRNS shall not include the referenced CCTrCH in the new configuration.] DL Power Control: [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the DL Reference Power Information IE and the power balancing is active, the DRNS shall update the reference power of the power balancing in the indicated RL(s), if updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported, using the DL Reference Power Information IE in the RADIO LINK RECONFIGURATION REQUEST message. The updated reference power shall be used from the next adjustment period.] [FDD If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNC shall include the DL Power Balancing Updated Indicator IE in the RL Information Response IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28Mcps TDD Uplink Synchronisation Parameters LCR:] [1.28Mcps TDD If the Uplink Synchronisation Parameters LCR IE is present, the DRNC shall use the indicated values of Uplink synchronisation stepsize IE and Uplink synchronisation frequency IE when evaluating the timing of the UL synchronisation.] [1.28Mcps TDD Shared physical channels Synchronisation Detection:] [1.28Mcps TDD If HS-PDSCH and E-PUCH are configured but no DPCH is configured for the UE, then the DRNS shall include the Out-of-sync Detection Window IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28Mcps TDD Uplink Timing Advance Control LCR:] [1.28Mcps TDD The DRNC shall include the Uplink Timing Advance Control LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message, if the Uplink Timing Advance Control parameters have been changed.] [1.28Mcps TDD PowerControl GAP:] [1.28Mcps TDD If applied in the DRNS, the DRNC may include the PowerControl GAP IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28Mcps TDD E-UTRAN Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Need for Idle Interval IE set to TRUE, if supported, the DRNC shall include the Idle Interval Information IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the Need for Idle Interval IE is set to FALSE, the DRNC shall delete the configuration related to E-UTRAN Inter-RAT measurement ] [1.28Mcps TDD Inter-frequency/ Inter-RAT measurement:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUESTmessage includes the DCH Measurement Type indicator IE, if supported, the DRNS shall include the Measurement purpose IE and the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE in the RADIO LINK RECONFIGURATION RESPONSE message to configure the measurement occasion pattern(s) indicated by the DCH Measurement Type indicator IE.] [1.28Mcps TDD RNTI Allocation Indicator:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the RNTI Allocation Indicator IE, if supported, the DRNS may allocate an E-RNTI and/or an H-RNTI for UE to use in CELL_FACH state.]

3GPP

Release 11 RL Information:

182

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD - If the UE Context is configured for F-DPCH Slot Format operation, the DRNS shall include the F-DPCH Slot Format IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Setup", then the DRNS shall use the information in F-TPICH Information IE to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].] [FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Configuration Change", then: the F-TPICH Information To Modify IE defines the new configuration and then:] [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Slot Format IE, then the DRNS shall use this information to configure the F-TPICH slot format according to TS 25.211 [7]. [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Offset IE, the DRNS shall use this information to configure the time offset of F-TPICH.] [FDD - If the F-TPICH Information To Modify IE includes the F-TPICH Channelisation Code Number IE, the DRNS shall use this information to configure the channelization code of F-TPICH.]

[FDD - If the RL Information IE includes the F-TPICH Information Reconf IE and the choice of Setup, Configuration Change or Removal of F-TPICH Information is "Removal", then the DRNS shall remove the configured F-TPICH for the RL.] HS-DSCH Setup: If the HS-DSCH Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message, then: -The DRNS shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. -The DRNC shall include the HARQ Memory Partitioning IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.] [1.28Mcps TDD The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than 8, if the MIMO Activation Indicator IE is included in the HS-DSCH Information IE.] -The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK RECONFIGURATION RESPONSE message. -The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. -If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HS-DSCH Information Response IE. -If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.

3GPP

Release 11

183

3GPP TS 25.423 V11.2.0 (2012-06)

-If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the DRNS shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. -The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being established, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If RADIO LINK RECONFIGURATION REQUESTmessage includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to Flexible MAC-d PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer I in RADIO LINK RECONFIGURATION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE. -[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] -[FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the DRNS shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the DRNS shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.425 [32]) and MAC-hs (TS 25.321 [41]). -[FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then] - [FDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] - [FDD The DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

3GPP

Release 11

184

3GPP TS 25.423 V11.2.0 (2012-06)

- [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [1.28 Mcps TDD If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then] - [1.28 Mcps TDD The DRNS shall activate the MIMO mode for the HS-DSCH Radio Link.] - [1.28 Mcps TDD The DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to Flexible MAC-d PDU Size and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS may use:] - [FDD a different HS-SCCH in consecutive TTIs for this UE] - [FDD HS-SCCH orders for the case of HS-SCCH-less operation to this UE] [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] If the RADIO LINK RECONFIGURATION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the DRNS shall activate the Single Stream MIMO for the HS-DSCH Radio Link.] [1.28 Mcps TDD If the UE TS0 Capability LCR IE is included in the HS-DSCH TDD Information IE, then the DRNC may include the TS0 HS-PDSCH Indication LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message if HS-PDSCH resources could be allocated on TS0 for the UE.]

3GPP

Release 11 [FDD Secondary Serving HS-DSCH Setup:]

185

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the C-ID IE is present in the RADIO LINK RECONFIGURATION REQUEST message, no secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS or if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE or in the HS-DSCH FDD Secondary Serving Information To ModifyUnsynchronised IE for each instance of the Additional HS Cell Information RL Reconf Req IE, indicate that new secondary serving HSDSCH Radio Link(s) shall be setup, then:] [FDD The DRNS shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] [FDD The DRNC shall allocate an HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HSDSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

3GPP

Release 11 -

186

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]

Intra-DRNS Serving HS-DSCH Radio Link Change: If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link: -The DRNS shall release the HS-PDSCH resources on the old Serving HS-DSCH Radio Link and setup the HSPDSCH resources on the new Serving HS-DSCH Radio Link. If fields are to be included in the User Plane by the SRNC to handle TNL Congestion Control for HSDPA in the DRNS, then the DRNC shall include the User Plane Congestion Fields Inclusion IE in the HS-DSCH Information Response IE. -The DRNC may include the HARQ Memory Partitioning IE in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message. [FDD The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] [1.28Mcps TDD The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.] -The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the RADIO LINK RECONFIGURATION RESPONSE message. -If a reset of the MAC-hs is not required the DRNS shall include the MAC-hs Reset Indicator IE in the RADIO LINK RECONFIGURATION RESPONSE message. -[FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[FDD The DRNS shall allocate HS-SCCH codes corresponding to the HS-DSCH and the DRNC shall include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[TDD The DRNS shall allocate HS-SCCH parameters corresponding to the HS-DSCH and the DRNC shall include the [3.84Mcps TDD HS-SCCH Specific Information Response IE] [1.28Mcps TDD HS-SCCH Specific Information Response LCR IE] [7.68 Mcps TDD HS-SCCH Specific Information Response 7.68 Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[TDD The DRNC shall include the [3.84 Mcps TDD HS-PDSCH Timeslot Specific Information IE] [1.28 Mcps TDD HS-PDSCH Timeslot Specific Information LCR IE] [7.68 Mcps TDD HS-PDSCH Timeslot Specific Information 7.68 Mcps IE]in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] -[FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] The DRNC may include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow in the [FDD HS-DSCH FDD Information Response IE] [TDD HS-DSCH TDD Information Response IE] in the RADIO LINK RECONFIGURATION RESPONSE message. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. [FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE and the value is set to "allowed" or if HS-DSCH Information To Modify Unsynchronized IE

3GPP

Release 11

187

3GPP TS 25.423 V11.2.0 (2012-06)

is not included and the UE Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [FDD If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the DRNC shall include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD Intra-DRNS Secondary Serving HS-DSCH Radio Link Change:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE in the Additional HS Cell Information RL Reconf Req IE, one or more secondary serving HS-DSCH Radio Link(s) has been configured in the DRNS and if the new configuration contains more than one secondary serving HS-DSCH Radio Link, then if the Ordinal Number Of Frequency IEs, in the HS-DSCH FDD Secondary Serving Information IE for each instance of the Additional HS Cell Information RL Reconf Req IE, indicate that existing secondary serving HS-DSCH Radio Links shall be subject to intra-DRNS secondary serving HS-DSCH Radio Link change, then the HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:] [FDD The DRNS shall release the HS-PDSCH resources on the old secondary serving HS-DSCH Radio Link and setup the HS-PDSCH resources on the new secondary serving HS-DSCH Radio Link. The DRNS shall remove the old secondary serving HS-PDSCH Radio Link if no E-DCH resources are allocated to the RL. Non cell specific secondary serving Radio Link and non cell specific secondary serving HS-DSCH parameters take the same values as for the serving HS-DSCH cell.] [FDD The DRNC shall allocate a new HS-DSCH-RNTI to the UE Context and include the HS-DSCH-RNTI IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD The DRNC shall include the Measurement Power Offset IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD The DRNS shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and the DRNC shall include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD The DRNC shall include the HS-PDSCH And HS-SCCH Scrambling Code IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD - If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE and the value is set to "allowed" or if HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE is not included and the UE context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the DRNS decides to use 64 QAM for the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If, in the new configuration, the UE context is configured not to use Sixtyfour QAM for the secondary serving HS-DSCH, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD

3GPP

Release 11

188

3GPP TS 25.423 V11.2.0 (2012-06)

Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.] [FDD - If the old and/or new configuration contains more than one Secondary Serving HS-DSCH Radio Link the HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the DRNS to be used on the new secondary serving HS-DSCH Radio Link, and then:] - [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] - [FDD If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.] - [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If the power offset for S-CPICH for MIMO Request indicator and MIMO activation indicator have been configured in the new configuration and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, the DRNC shall include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Secondary Serving Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD Additional Serving E-DCH Radio Link Change to an existing additional non serving E-DCH RL:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the C-ID IE in the Additional HS Cell Information RL Reconf Req IE and an additional non serving E-DCH RL exists in the cell indicated by the C-ID IE, the HS-PDSCH RL ID IE in the HS Cell Information RL Reconf Req IE indicates the new Additional Serving E-DCH Radio Link.] - [FDD If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the EAGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message] - [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]

3GPP

Release 11

189

3GPP TS 25.423 V11.2.0 (2012-06)

- [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION READY message.] - [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Link on secondary UL frequency in the DRNS. If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the E-DCH FDD DL Control Channel Information IE then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the E-DCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD Additional Serving E-DCH Radio Link Change to a new RL:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information RL Reconf Req IE and the C-ID IE in the Additional HS Cell Information RL Reconf Req IE and there is no radio links in the cell indicated by the C-ID IE for the UE context, the HSPDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link on secondary UL frequency.] [FDD If the old Additional Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the EAGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.] [FDD In the new configuration the DRNS shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.] [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE] [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. ]

HS-DSCH Modification: If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Information To Modify Unsynchronised IE, then: -The DRNC shall include the HS-DSCH Initial Capacity Allocation IE for each HS-DSCH MAC-d flow being modified for which the establishment of one or several new Priority Queues was requested, if the DRNS allows the SRNC to start the transmission of MAC-d PDUs for the Priority Queue(s) being established before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If UE context is configured to use Flexible MAC-d PDU Size, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer for the Priority Queue of UE context.

3GPP

Release 11

190

3GPP TS 25.423 V11.2.0 (2012-06)

-If the RADIO LINK RECONFIGURATION REQUEST message includes the Traffic Class IE in the HSDSCH Information To Modify Unsynchronised IE for a specific HS-DSCH MAC-d flow, the DRNS may use this information to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this specific HS-DSCH MAC-d flow indicates the value RRC. -If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. -If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH Information To Modify Unsynchronised IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. -If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH Information To Modify Unsynchronised IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. -[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the ACK Power Offset IE, the NACK Power Offset IE or the CQI Power Offset IE in the HS-DSCH Information To Modify Unsynchronised IE, then the DRNS shall use the indicated ACK Power Offset, the NACK Power Offset or the CQI Power Offset in the new configuration.] -[FDD If the HS-SCCH Power Offset IE is included in the HS-DSCH Information To Modify Unsynchronised IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.] -[TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the TDD ACK NACK Power Offset IE in the HS-DSCH Information To Modify Unsynchronised IE, the DRNS shall use the indicated power offset in the new configuration.] -[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information To ModifyUnsynchronised IE, then the DRNS shall use the indicated HARQ Preamble Mode in the new configuration as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the DRNC shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the DRNC shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the MIMO Mode Indicator To Modify IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then] [FDD The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the MIMO Mode Indicator IE.] [FDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the MIMO Mode Indicator IE is set to Activate and Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HSDSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD Information Response IE. If zero power offset the DRNC may include the Power Offset For SCPICH for MIMO IE.]

[FDD The DRNC may include the HARQ Memory Partitioning IE in the RADIO LINK RECONFIGURATION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]

3GPP

Release 11 -

191

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the DRNS may if the value is set to allowed use 64 QAM for the HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE with value set to not allowed, then the DRNS shall not use 64 QAM for the HS-DSCH Radio Link.] [FDD If MAC-ehs is applied in the new configuration, and if Sixtyfour QAM will not be used, the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for HS-DSCH Transport Block Size signalling.] [1.28Mcps TDD- If the MIMO Mode Indicator To Modify IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then] - [1.28Mcps TDD- The DRNS shall activate/deactivate the MIMO mode for the HS-DSCH Radio Link in the new configuration in accordance with the MIMO Mode Indicator IE.] - [1.28 Mcps TDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HSDSCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[FDD Any secondary serving HS-DSCH that was applied in the old configuration shall remain in the new configuration unless it is explicitly removed.] [FDD If secondary serving HS-DSCH is applied also in the new configuration, then any changes related to parameters that are common for both the serving and the secondary serving HS-DSCH should be applied also for the secondary serving HS-DSCH.] [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify Unsynchronised IE the DRNS may use the supported HSDPA functions for this UE.] [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Information To Modify IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH Information To Modify Unsynchronised IE, then the DRNS shall activate/deactivate the Single Stream MIMO for the HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.]

[FDD Secondary Serving HS-DSCH Modification:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE in the Additional HS Cell Information RL Reconf Req IE, then:] [FDD If the HS-SCCH Power Offset IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, the DRNS may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.] [FDD If the MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the DRNS shall activate/deactivate the MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the MIMO Mode Indicator IE.] [FDD If the MIMO Mode Indicator IE is set to Activate, then the DRNS shall decide the pilot configuration and the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the MIMO Mode Indicator IE is set to Activate and Power Offset For S-CPICH for MIMO Request Indicator IE is included, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Secondary Serving HS-DSCH Radio Link is established, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH FDD

3GPP

Release 11

192

3GPP TS 25.423 V11.2.0 (2012-06)

Secondary Serving Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.] [FDD If the Single Stream MIMO Mode Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the Node B shall activate/deactivate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link in accordance with the Single Stream MIMO Mode Indicator IE.] [FDD - If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the DRNS shall use this value in the physical layer.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, then the DRNS may if the value is set to allowed use 64 QAM for the secondary serving HS-DSCH Radio Link, and the DRNS shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE with value set to not allowed, then the DRNS shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.] [FDD If, in the new configuration, the UE context is configured to use the Flexible MAC-d PDU Size format and if Sixtyfour QAM will not be used for the secondaery serving HS-DSCH, then the DRNS shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [41] for secondary serving HS-DSCH Transport Block Size signalling.]

[FDD Secondary Serving HS-DSCH Removal:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Secondary Serving Remove IE in the Additional HS Cell Information RL Reconf Req IE, then the indicated secondary serving HS-DSCH Radio Link shall be removed.] HS-DSCH MAC-d Flow Addition/Deletion: If the RADIO LINK RECONFIGURATION REQUEST message includes any HS-DSCH MAC-d Flows To Add or HSDSCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to add/delete the indicated HS-DSCH MAC-d flows on the Serving HS-DSCH Radio Link. When an HS-DSCH MAC-d flow is deleted, all its associated Priority Queues shall also be removed. If the RADIO LINK RECONFIGURATION REQUEST message includes an HS-DSCH MAC-d Flows To Delete IE requesting the deletion of all remaining HS-DSCH MAC-d flows for the UE Context, then the DRNC shall delete the HS-DSCH configuration from the UE Context and release the HS-PDSCH resources. If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH MAC-d Flows To Add IE, then: The DRNS may use the Traffic Class IE for a specific HS-DSCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the HS-DSCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related MAC-d flow. The DRNC shall include the HS-DSCH Initial Capacity Allocation IE in the RADIO LINK RECONFIGURATION RESPONSE message for every HS-DSCH MAC-d flow being added, if the DRNS allows the SRNC to start transmission of MAC-d PDUs before the DRNS has allocated capacity on user plane as described in TS 25.425 [32]. If the UE context is configured to use the Flexible MAC-d PDU Size format for the HS-DSCH, then DRNC shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the

3GPP

Release 11

193

3GPP TS 25.423 V11.2.0 (2012-06)

corresponding peer I in RADIO LINK RECONFIGURATION REQUEST message in the HS-DSCH MAC-d Flows To Add IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE in the HS-DSCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue. If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the DRNC shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue. If the RADIO LINK RECONFIGURATION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the DL RLC PDU Size Format IE may be used by the DRNS to determine the allocated capacity on user plane as described in TS 25.425 [32]. [FDD FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, the DRNS shall, if supported, consider the data of the related HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]

If the RADIO LINK RECONFIGURATION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows To Add IE, then the DRNS shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue. [FDD HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE the DRNS shall, if supported, preconfigure the indicated cells for Enhanced HS Serving Cell Change acoording to TS 25.308 [63]:] [FDD The DRNS shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HSDSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK RECONFIGURATION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-ID IEsin the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK RECONFIGURATION REQUEST message.] [FDD The number of HS-SCCH codes to preconfigure for each cell may be optionally specified: ] - [FDD by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell.] - [FDD by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells.] [FDD If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10]. ] [FDD The DRNS shall return these codes in the Sets of HS-SCCH Codes IE along with the corresponding percell HS-DSCH-RNTI IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK RECONFIGURATION RESPONSE.] [FDD The DRNS shall use the first in the numbered list the primary serving HS-DSCH cells of HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the SRNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [16].] [FDD The DRNS shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message, IEs according to the rules defined for HSDSCH Setup at Serving HS-DSCH Radio Link Change and:] - [FDD if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE.]

3GPP

Release 11

194

3GPP TS 25.423 V11.2.0 (2012-06)

- [FDD if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE.] - [FDD if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfiguration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell.] - [FDD if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell.] - [FDD if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE.] - [FDD if the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS shall store this information in the preconfigured configuration.] - [FDD the SixtyfourQAM DL Support Indicator IE may be included.] - [FDD If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the DRNS may store this information in the preconfigured configuration.] - [FDD - If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the DRNS shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD the DRNS shall, if supported, include in the Sets of HS-SCCH Codes IE the Measurement Power Offset IE for each preconfigured cell.] [FDD The DRNS shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:] - [FDD The DRNS shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.] - [FDD The DRNS may preconfigure the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.] [FDD If the Power Offset For S-CPICH for MIMO Request Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, the DRNC shall, if supported and MIMO pilot configuration with Primary and Secondary CPICH is set up on the cell with a non-zero power offset where HS-DSCH / secondary HS-DSCH is preconfigured, include the Power Offset For S-CPICH for MIMO IE in the HS-DSCH Preconfiguration Info IE or in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE for each preconfigured cell in the RADIO LINK RECONFIGURATION RESPONSE message. If zero power offset the DRNC may include the Power Offset For S-CPICH for MIMO IE.]

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Non-Serving RL Preconfiguration Setup IE in the RL Information IE and:] [FDD if the choice of new Serving RL is "New Serving RL in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD if the choice of new Serving RL is "New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK RECONFIGURATION RESPONSE message.]

3GPP

Release 11 -

195

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD if the choice of new Serving RL is "New Serving RL in the DRNS or New Serving RL Not in the DRNS", the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL EDCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the DRNC may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK RECONFIGURATION RESPONSE message.]

[FDD Enhanced HS Serving Cell Change:] [FDD -Upon receipt of the RADIO LINK RECONFIGURATION REQUEST message, if the Enhanced HS Serving Cell Change is preconfigured in the DRNS for the UE context, the DRNS may execute the Enhanced HS Serving Cell Change procedure according to TS 25.308 [63] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Enhanced HS Serving CC Abort IE in the HS-DSCH Information To Modify Unsynchronised IE or the HS-DSCH FDD Information IE then the DRNS shall not execute the unsynchronized Enhanced HS Serving Cell Change procedure when performing the Serving HSDSCH Radio Link Change or the HS-DSCH Setup.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the No of Target Cell HS-SCCH Order IE then the DRNS shall repeat the Target Cell HS-SCCH Order on the HS-SCCH the number of times defined in the IE.] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Non-Serving RL Preconfiguration Removal IE, the DRNC shall remove the corresponding preconfigured E-DCH DL Control Channel Information according to the information.] [FDD E-DCH Setup:] [FDD If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message then:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel information IE in the E-DCH FDD Information IE, then the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH FDD Information IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH Information IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.425 [32]) and MAC (TS 25.321 [41]).] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.] [FDD If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume nonscheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ

3GPP

Release 11

196

3GPP TS 25.423 V11.2.0 (2012-06)

Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.] [FDD If in the RADIO LINK RECONFIGURATION REQUEST message the E-DCH Grant Type is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.] [FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [FDD If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Bundling Mode Indicator IE for a E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related Mac-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related Mac-d flow.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH ReferencePower Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DPCH Information IE which contains the HS-DSCH Configured Indicator IE and/or the Maximum Set of E-DPDCHs IE, and/or the Puncture Limit IE and/or the E-TTI IE, the DRNS shall use and apply the value(s) in the new configuration.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the SixteenQAM UL Operation Indicator IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.] - [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].] [FDD E-DCH Radio Link Handling:]

3GPP

Release 11

197

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH RL Indication IE in the RL Information IE:] [FDD The DRNC shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD The DRNC may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNC may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to E-DCH, in the RL Information IE.] [FDD The DRNC shall remove the E-DCH resources, if any, on the Radio Links, that are indicated by the EDCH RL Indication set to Non E-DCH.] [FDD For each RL for which the E-DCH RL Indication IE is set to E-DCH, and which has or can have a common generation of E-RGCH information with another RL (current or future) when the DRNS would contain the E-DCH serving RL, the DRNS shall include the E-DCH RL Set ID IE in the RADIO LINK RECONFIGURATION RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the SRNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]

[FDD Serving E-DCH Radio Link Change:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Serving E-DCH RL IE, this indicates the new Serving E-DCH Radio Link:] [FDD If the old Serving E-DCH RL is within this DRNS, the DRNS shall de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link.] [FDD If the new Serving E-DCH RL is within this DRNS:] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the RL Information Response IE for the indicated RL in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD The DRNS may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the RADIO LINK RECONFIGURATION RESPONSE message for the initial grant for the new serving E-DCH RL.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD If a serving cell change is performed the RADIO LINK RECONFIGURATION RESPONSE message may contain invalid data (see 9.2.2.4C).] - [FDD The DRNS may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK RECONFIGURATION RESPONSE message for the new serving E-DCH RL.] [FDD The DRNS may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message for every E-DCH Radio Links in the DRNS.] [FDD If the DRNS has no valid data for the E-RGCH/E-HICH Channelisation Code IE in the E-DCH FDD DL Control Channel Information IE in the RADIO LINK RECONFIGURATION RESPONSE message, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE in the E-DCH FDD DL Control Channel Information IE, to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.]

[FDD E-DCH Modification:]

3GPP

Release 11

198

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information To Modify IE, then:] [FDD If the E-DCH FDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] [FDD If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [FDD If Traffic Class IE is included for an E-DCH MAC-d flow the DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. The DRNC should ignore the Traffic Class IE if the TrCH Source Statistics Descriptor IE for this specific EDCH MAC-d flow indicates the value RRC.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Data Description Indicator IE, the DRNC shall use the DDI values indicated in the Data Description Indicator IE in the new configuration.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH FDD Information To Modify IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum Number of Retransmissions for E-DCH IE for an E-DCH MAC-d flow in the E-DCH FDD Information To Modify IE, then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH HARQ Power Offset FDD IE in the E-DCH FDD Information To Modify IE for an E-DCH MAC-d flow the DRNS shall use this information for calculating the unquantised gain factor for an E-TFC (ed,j,uq)as defined in TS 25.214 [10].] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being E-DCH Non-Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Grant Type and it is indicated as being E-DCH Scheduled Transmission Grant for an E-DCH MAC-d flow the DRNS shall assume scheduled grants being configured for that E-DCH MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION RE QUEST message includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the DRNS shall use this information to add/delete the indicated logical channels. When an logical channel is deleted, all its associated configuration data shall also removed.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Logical Channel To Modify IE, the DRNS shall use this information to modify the indicated logical channels.] - [FDD If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the DRNS shall apply the values in the new configuration.] - [FDD If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the DRNS shall apply the values in the new configuration.] - [FDD If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the DRNC shall apply the value in the new configuration.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD

3GPP

Release 11

199

3GPP TS 25.423 V11.2.0 (2012-06)

Information To Modify IE and the Bundling Mode Indicator IE is set to Bundling and the E-TTI IE is set to 2ms, then the DRNS shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the DRNS shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the DRNS shall use this information for the related resource allocation operation.] [FDD If the E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH ReferencePower Offset IE, then the DRNS may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the DRNS may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the SixteenQAM UL Operation Indicator IE in the E-DCH FDD Information To Modify IE, the DRNS shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.] - [FDD If SixteenQAM UL Operation is activated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to TS 25.321 [41]. If SixteenQAM UL Operation is deactivated, then the DRNS shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to TS 25.321 [41].] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH DL Control Channel Grant Information IE in the E-DCH FDD Information To Modify IE, the DRNS may modify E-AGCH Channelisation Code, E-RGCH/E-HICH Channelisation Code, E-RGCH Signature Sequence and/or E-HICH Signature Sequence for the E-DCH RL indicated by the E-DCH RL ID IE. The DRNC shall then report the modified configuration which is used in the new configuration specified in the E-DCH FDD DL Control Channel Information IE for each E-DCH RL in the RADIO LINK RECONFIGURATION RESPONSE message.]

[FDD E-DCH MAC-d Flow Addition:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Add IE, then the DRNS shall use this information to add the indicated E-DCH MAC-d flows.]

3GPP

Release 11

200

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH MAC-d Flows To Add IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flows To Add IE, then:] [FDD The DRNS may use the Traffic Class IE for a specific E-DCH MAC-d flow to determine the transport bearer characteristics to apply between DRNC and Node B. If TrCH Source Statistics Descriptor IE is present with the value RRC in the E-DCH MAC-d Flows Information IE, then the DRNC should ignore the Traffic Class IE.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]

[FDD E-DCH MAC-d Flow Deletion:] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration shall also be removed.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNC shall delete the EDCH configuration from the UE Context and release the E-DCH resources.] [FDD Additional E-DCH Setup:] [FDD If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Setup, then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:] [FDD If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup] - [FDD The DRNS shall setup the E-DCH on the secondary uplink frequency and setup the requested E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.] [FDD If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the additional E-DCH shall be setup.] - [FDD The DRNS shall setup the additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE] [FDD The DRNS shall use for the non cell specific Radio Link related parameters and non cell specific EDPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency.] [FDD If the UL SIR Target IE in the UL DPCH Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE and/or the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE are present, the DRNS shall use the information in the same same way as for the information used on Primary uplink frequency.]

3GPP

Release 11 -

201

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the DRNS shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.] [FDD If the Initial DL Tx Power IE, the Primary CPICH Ec/No IE, the E-AGCH Power Offset IE, the ERGCH Power Offset IE and/or the E-HICH Power Offset IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the Enhanced Primary CPICH Ec/No IE is included in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH Secondary RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If the F-DPCH Slot Format Support Request IE in the F-DPCH Information IE in the Additional EDCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE is included, the DRNS shall configure the concerned UE Context for F-DPCH Slot Format operation according to TS 25.211 [8] and include the F-DPCH Slot Format IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconfIE in the RADIO LINK RECONFIGURATION RESPONSE message. If the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE includes the F-DPCH Slot Format IE, the DRNS may use the F-DPCH Slot Format IE to determine the F-DPCH slot format.] [FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Processing Overload Level IE are present in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, the DRNS shall use the information in the same way as for the information used on Primary uplink frequency.] [FDD If activation of power balancing for the Additional E-DCH RL by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the DRNS may include the E-AGCH And E-RGCH/EHICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message and if DRNS has no valid data

3GPP

Release 11

202

3GPP TS 25.423 V11.2.0 (2012-06)

for the E-RGCH/E-HICH Channelisation Code IE, then it shall insert the E-RGCH and E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/E-HICH Channelisation Code IE contains invalid data.] [FDD If the Additional Serving E-DCH Radio Link is configured in the DRNS, then:] - [FDD The DRNS shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding EAGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message.] - [FDD The DRNS may include in the E-DCH FDD DL Control Channel Information IE in the Additional EDCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.] - [FDD If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If Primary CPICH is not to be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If Secondary CPICH may be used as a Phase Reference for this Radio Link on the secondary UL frequency, the DRNS shall include the Secondary CPICH Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the DRNS doesnt include the Secondary CPICH Information IE, it shall not include the Primary CPICH Usage For Channel Estimation IE set to the value Primary CPICH shall not be used.]

[FDD Additional E-DCH Configuration Change] [FDD If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Configuration Change, then the Additional E-DCH Cell Information Configuration Change IE defines the new configuration and then:] [FDD If the Minimum Reduced E-DPDCH Gain Factor IE and/or the Common DL Reference Power IE is present in the Multicell E-DCH Information IE in the Additional E-DCH Configuration Change Information IE IE the DRNS shall use the information in the same way as for the information that is used on the Primary uplink frequency.] [FDD. If the UE Context is configured for F-DPCH Slot Format operation, the DRNS shall include the F-DPCH Slot Format IE in the Additional E-DCH FDD Information Response IE for new RLs on the secondary UL frequency or in the Additional Modified E-DCH FDD Information Response IE for modified RLs in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD Additional E-DCH RL Addition:] [FDD If the Additional E-DCH RL Specific Information To Add IE is present in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Configuration Change Information IE, then:] [FDD The DRNS shall setup the E-DCH resources, as requested or as configured in the UE context, on the Radio Links indicated by the E-DCH Additional RL ID IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]

3GPP

Release 11 -

203

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing Additional E-DCH RL(s) and the RADIO LINK RECONFIGURATION REQUEST message includes the DL Reference Power IE in the Multicell EDCH RL Specific Information IE, the DRNS shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional RL(s), if activation of power balancing by the RADIO LINK RECONFIGURATION REQUEST message at RL addition on secondary UL frequency is supported, according to subclause 8.3.15. In this case, the DRNS shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the DRNS starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. Pinit shall be set to the power level which is calculated based on the following IEs (if received): Primary CPICH Ec/No IE or the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE or to the power level which is calculated based on the power relative to the Primary CPICH power used by the existing Additional RLs.] [FDD For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall set the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message to a value that uniquely identifies the RL as a RL Set within the UE Context. The generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.] [FDD For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the DRNS shall assign to each Additional E-DCH RL the same value for the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message. This value shall uniquely identify these Additional E-DCH RLs as members of the same RL Set within the UE Context. The generation of EHICH information for all Additional E-DCH RLs in a RL Set shall be common.] [FDD For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the DRNS would contain the Additional E-DCH serving RL, the DRNS shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional EDCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message] [FDD For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE, the DRNS may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the DRNS may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message and if DRNS has no valid data for the E-RGCH/ EHICH Channelisation Code IE, then it shall insert the E-RGCH/ E-HICH Channelisation Code Validity Indicator IE to indicate that the E-RGCH/ E-HICH Channelisation Code IE contains invalid data.] [FDD If the Primary CPICH Ec/No IE or the Primary CPICH Ec/No IE and the Enhanced Primary CPICH Ec/No IE in the Multicell E-DCH RL Specific Information IE measured by the UE are included for a RL in the RADIO LINK RECONFIGURATION REQUEST message, the DRNS shall use this in the calculation of the Initial DL TX Power for this additional RL. If the Primary CPICH Ec/No IE is not present, the DRNS shall set the Initial DL TX Power based on the power relative to the Primary CPICH power used by the existing RLs.]

[FDD Additional E-DCH RL Modification:]

3GPP

Release 11

204

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the Additional E-DCH RL Specific Information To Modify IE is present in the Additional EDCH Configuration Change Information IE, then the additional E-DCH RL indicated by the E-DCH Additional RL ID IE indicates the RL on which E-DCH resources shall be modified:] -[FDD If the E-AGCH Power Offset IE, the E-RGCH Power Offset IE, the E-HICH Power Offset IE, and/or the E-DCH DL Control Channel Grant IE in the Multicell E-DCH RL Specific Information IE is included, the DRNS shall use the information in the same way as for the information used on the Primary uplink frequency.] -[FDD If the DL Reference Power IEs is included in the Multicell E-DCH RL Specific Information IE and power balancing is active, DRNS shall apply DL power Control in the same way as defined for the Primary uplink frequency.] -[FDD If updating of power balancing parameters by the RADIO LINK RECONFIGURATION REQUEST message is supported by the DRNS, the DRNS shall include the DL Power Balancing Updated Indicator IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE for each affected RL in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the RADIO LINK RECONFIGURATION RESPONSE message includes the Primary CPICH Usage For Channel Estimation IE and/or the Secondary CPICH Information Change IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE, the DRNS shall avoid the new configuration in which neither the Primary CPICH nor the Secondary CPICH is used as a Phase Reference for this Radio Link.]

[FDD Additional E-DCH Modification:] [FDD If the Additional E-DCH FDD Information To Modify IE is present in the Additional E-DCH Configuration Change Information IE, then:] -[FDD If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Minimum Set E-TFCI IE and/or the E-DCH Maximum Bitrate IE is included, the DRNS shall use this information for the related resource allocation operation.] -[FDD If the E-DCH Processing Overload Level IE is included, then if the DRNS could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the DRNS shall notify the RNC by initiating the Radio Link Failure procedure.] -[FDD If the DL TX power upper or lower limit has been re-configured for the secondary UL frequency, the DRNS shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE in the RADIO LINK RECONFIGURATION RESPONSE message. -[FDD The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNS shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Maximum Uplink SIR IE and Minimum Uplink SIR IE in the Additional Modified E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RLReconf IE for each Radio Link when these values are changed.] -[FDD If the Additional E-DCH serving RL is in this DRNS, the DRNS may choose to change the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission. In this case the DRNS shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional Modified E-DCH FDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD Additional E-DCH Removal] [FDD If the Additional E-DCH Cell Information RL Reconf Req IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency is Removal, then the additional E-DCH on the secondary uplink frequency shall be removed.]

3GPP

Release 11

205

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD Intra- DRNS Serving E-DCH Radio Link Change:] [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link:] [TDD In the new configuration the DRNS shall de-allocate the E-DCH resources of the old Serving E-DCH Radio Link and allocate the E-DCH resources for the new Serving E-DCH Radio Link.] [3.84Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE in the E-DCH TDD Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28Mcps TDD The DRNS shall allocate E-AGCH parameters and E-HICH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response IE and the E-HICH Specific Information Response IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [7.68Mcps TDD The DRNS shall allocate E-AGCH parameters corresponding to the E-DCH and include the E-AGCH Specific Information Response 7.68Mcps IE in the E-DCH TDD Information Response 7.68Mcps IE in the RADIO LINK RECONFIGURATION READY message.] [TDD If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]

[TDD E-PUCH Handling:] [3.84Mcps TDD and 7.68Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-PUCH Information IE, the DRNS shall apply the parameters to the new configuration.] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E-PUCH Information LCR IE, the DRNS shall apply the parameters to the new configuration] [TDD If the RADIO LINK RECONFIGURATION REQUEST message includes an E- TFCS Information IE, the DRNS shall apply the beta parameters to the new configuration.] [3.84Mcps TDD E-DCH Setup:] [3.84Mcps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information IE.] [1.28Mcps TDD E-DCH Setup:] [1.28cps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information LCR IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information LCR IE.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].] [7.68Mcps TDD E-DCH Setup:] [7.68Mcps TDD the radio link may be reconfigured to support E-DCH by including the appropriate E-DCH information elements: E-DCH Serving RL IE, E-PUCH Information IE, E-TFCS Information TDD IE, E-DCH MAC-d Flows to Add IE and E-DCH TDD Information 7.68Mcps IE.] [TDD- E-DCH MAC-d Flow Addition/Deletion:] [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes any E-DCH MAC-d Flows To Add or E-DCH MAC-d Flows To Delete IEs, then the DRNS shall use this information to add/delete the indicated E-DCH MAC-d flows. When an E-DCH MAC-d flow is deleted, all its associated configuration data shall also be removed.]

3GPP

Release 11

206

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH TDD Information To Add IE, then the DRNS shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel.] [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes an E-DCH MAC-d Flows To Delete IE requesting the deletion of all remaining E-DCH MAC-d flows for the UE Context, then the DRNS shall delete the EDCH configuration from the UE Context and release the E-DCH resources.] [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH MAC-d Flows To Add IE, then:] [TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information to optimise MAC-e scheduling decisions.] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows To Add IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for EDCH scheduling.]

[3.84Mcps TDD E-DCH Non-scheduled allocations:] [3.84Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information TDD IE in the E-DCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [1.28Mcps TDD E-DCH Non-scheduled allocations:] [1.28Mcps The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information LCR TDD IE in the E-DCH Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [7.68Mcps TDD E-DCH Non-scheduled allocations:] [7.68Mcps TDD The DRNS shall determine any non-scheduled resource to be granted for the radio link, and return this in the E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE in the E-DCH Information Response 7.68Mcps IE in the RADIO LINK RECONFIGURATION RESPONSE message.] [3.84Mcps TDD E-DCH Modification:] [3.84Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH TDD Information IE, then:] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH TDD Maximum Bitrate IE for an EDCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [3.84Mcps TDD If the E-DCH TDD Information IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

[1.28Mcps TDD E-DCH Modification:] [1.28Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH TDD Information LCR IE, then:] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

3GPP

Release 11 -

207

3GPP TS 25.423 V11.2.0 (2012-06)

[1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the EDCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE, then the DRNS shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.] [1.28Mcps TDD If the E-DCH TDD Information LCR IE includes the Multi-Carrier E-DCH Physical Layer Category LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.] [1.28Mcps TDD - If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information To Modify IE is not present, or if the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present, and if the RADIO LINK RECONFIGURATION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the DRNS can use this information to allocate the downlink resources for the UE according to TS 25.306 [42].]

[7.68Mcps TDD E-DCH Modification:] [7.68Mcps TDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH TDD Information 7.68Mcps IE, then:] [7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE for an E-DCH, the DRNS shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.] [7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH Processing Overload Level IE, then if the DRNS could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the EDCH Processing Overload Level IE, because of a processing issue, the DRNS shall notify the SRNC by initiating the Radio Link Failure procedure.] [7.68Mcps TDD If the E-DCH TDD Information 7.68Mcps IE includes the E-DCH Power Offset for Scheduling Info IE, then the DRNS shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

[TDD- If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH TDD Information To Modify IE, then:] [TDD- If the E-DCH TDD Information To Modify IE contains a E-DCH MAC-d Flow Specific Information IE which includes the Allocation/Retention Priority IE, the DRNS shall apply the new Allocation/Retention Priority to this E-DCH in the new configuration according to Annex A.] [TDD- If the E-DCH TDD Information To Modify IE contains a TNL QoS IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.] [TDD- If the E-DCH TDD Information To Modify IE includes the Maximum Number of Retransmissions for EDCH IE for an E-DCH MAC-d flow then the DRNS shall use this information to report if the maximum number of retransmissions has been exceeded.] [1.28Mcps TDD If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Retransmission Timer IE for an E-DCH MAC-d flow then the DRNS shall use this information to set the retransmission timer.] [TDD If the TNL QoS IE is included in the E-DCH TDD Information to Modify IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the DRNS to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]

3GPP

Release 11 -

208

3GPP TS 25.423 V11.2.0 (2012-06)

[TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH HARQ Power Offset TDD IE for an EDCH MAC-d flow the DRNS shall use this new power offset value.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the DRNS shall use this information for the related resource allocation operation.] [TDD- If the E-DCH TDD Information To Modify IE contains the E-DCH Grant Type IE, the DRNS shall treat the E-DCH MAC-d flow as Scheduled or Non-scheduled accordingly.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Add or E-DCH Logical Channel To Delete IEs, the DRNS shall use this information to add/delete the indicated logical channels. When a logical channel is deleted, all its associated configuration data shall also removed.] [TDD- If the E-DCH TDD Information To Modify IE includes the E-DCH Logical Channel To Modify IE, the DRNS shall use this information to modify the indicated logical channels:] - [TDD If the E-DCH Logical Channel To Modify IE includes Scheduling Priority Indicator IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes Scheduling Information IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes MAC-es Guaranteed Bit Rate IE, the DRNS shall apply the values in the new configuration.] - [TDD If the E-DCH Logical Channel To Modify IE includes E-DCH DDI Value IE, the DRNS shall apply the values in the new configuration.] - [1.28Mcps TDD If the E-DCH Logical Channel To Modify IE includes MAC-es Maximum Bit Rate LCR IE, the DRNS shall use this information for the related resource allocation operation, and when applicable, for EDCH scheduling.] - [TDD If the E-DCH Logical Channel To Modify IE includes the Maximum MAC-d PDU Size Extended IE, the DRNC shall apply the value in the new configuration.]

[TDD If the E-DCH TDD Information To Modify IE includes the MAC-e Reset Indicator IE, then the DRNS shall use this value to determine whether MAC-e (or MAC-i) Reset is performed in the UE for sending the HARQ Failure Indication.]

[1.28Mcps TDD Multi-Carrier E-DCH Continue:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Continue", then the current Multi-Carrier E-DCH configuration shall not be changed.] [1.28Mcps TDD Multi-Carrier E-DCH Setup:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Setup", then the MultiCarrier E-DCH Information LCR IE defines the new configuration and then:] [1.28Mcps TDD - The DRNS shall use the Multi-Carrier E-DCH Transport Bearer Mode LCR IE to decide the transport bearer mode in the new configuration.] [1.28Mcps TDD - The DRNS shall setup the requested E-DCH resource on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.]

[1.28Mcps TDD Multi-Carrier E-DCH Change:] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Change", then the Multi-Carrier E-DCH Information LCR IE defines the new configuration and then:] - [1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is different from current configured frequencies, then the DRNS shall setup the E-DCH resources, as requested in the DRNS

3GPP

Release 11

209

3GPP TS 25.423 V11.2.0 (2012-06)

Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.] - [1.28Mcps TDD - If the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE is the same as any current configured frequency, then the DRNS shall reconfigure the E-DCH resources, as requested or as configured in the DRNS Communication Context, on the uplink frequecies indicated by the UARFCN IE in the Multi-Carrier E-DCH Information LCR IE.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Information Reconf IE is present in the RADIO LINK RECONFIGURATION REQUEST message and the choice of Continue, Setup or Change is "Change" and the Removal UL Multi-Carrier info IE is included, then the DRNS shall remove the corresponding E-DCH configuration on the uplink frequencies indicated by the UARFCN IE in the Removal UL Multi-Carrier info IE.] General: If the requested modifications are allowed by the DRNS, and if the DRNS has successfully allocated the required resources and changed to the new configuration, the DRNC shall respond to the SRNC with the RADIO LINK RECONFIGURATION RESPONSE message. If the RADIO LINK RECONFIGURATION REQUEST message includes the RL Specific DCH Information IE, HSDSCH Information IE, HS-DSCH Information To Modify Unsynchronised IE, HS-DSCH MAC-d Flows To Add IE, [FDD RL Specific E-DCH Information IE] [TDD E-DCH MAC-d Flows to Add IE], the DRNC may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE is not included] being added, or any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE was not included] or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE. The DRNC shall include the Transport Layer Address IE and the Binding ID IE in the RADIO LINK RECONFIGURATION RESPONSE message for any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE is not included], HS-DSCH MAC-d flow being added or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE is not included] being added, or any Transport Channel [FDD for which the Transport Bearer Not Requested Indicator IE was not included], HS-DSCH MAC-d flow or E-DCH MAC-d flow [FDD for which the Transport Bearer Not Requested Indicator IE was not included] being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE. The detailed frame protocol handling during transport bearer replacement is described in TS 25.427 [4], subclause 5.10.1, and in TS 25.425 [32], subclause 5.3.2. [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer Shall not be Established for a DCH or an E-DCH MAC-d flow being added, then the DRNC shall not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to Transport Bearer may not be Established for a DCH or an E-DCH MAC-d flow being added and:] - [FDD if the DRNC establishes a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH or E-DCH MAC-d flow being established.] - [FDD if the DRNC does not establish a transport bearer for the concerned DCH or E-DCH MAC-d flow, the DRNC shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH or E-DCH MAC-d flow in the RADIO LINK RECONFIGURATION RESPONSE message.] In the case of a set of co-ordinated DCHs requiring a new transport bearer on the Iur interface, the DRNC shall include the Transport Layer Address IE and the Binding ID IE in the DCH Information Response IE only for one of the DCHs [FDD for which the Transport Bearer Not Requested Indicator IE is not included] in the set of co-ordinated DCHs. In the case of a Radio Link being combined with another Radio Link within the DRNS, the DRNC shall include the Transport Layer Address IE and the Binding ID IE [FDD for the concerned DCH for which the Transport Bearer Not

3GPP

Release 11

210

3GPP TS 25.423 V11.2.0 (2012-06)

Requested Indicator IE is not included]in the DCH Information Response IE in the RADIO LINK RECONFIGURATION RESPONSE message for only one of the combined Radio Links. [FDD In the case of an E-DCH RL being combined with another E-DCH RL within the DRNS, the E-DCH FDD Information Response IE shall be included only for one of the combined E-DCH RLs.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Additional E-DCH Cell Information RL Reconf Req IE, then:] [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to Separate Iur Transport Bearer Mode the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [FDD if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to UL Flow Multiplexing Mode the DRNS shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.] [FDD if Separate Iur Transport Bearer Mode is used in the new configuration, then:] - [FDD the DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Not Requested Indicator IE in the RL Specific E-DCH Information IE in the RL Information IE and/or the Transport Bearer Request Indicator IE in the E-DCH FDD Information To Modify IE received for the corresponding Radio Link(s) of the Primary Uplink Frequency to determine the transport bearer configuration in the new configuration for the radio links of the Secondary Uplink Frequency.] - [FDD If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE or in the Additional E-DCH RL Specific Information To Add IE and/or the Additional E-DCH RL Specific Information To Modify IE in the Additional E-DCH Configuration Change Information IE in the Additional E-DCH Cell Information Configuration Change IE, then the DRNS may use the transport layer address and the binding identifier received from the SRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the DRNS establishes a transport bearer for the concerned E-DCH MACd flow the DRNS shall, for establishment of the transport bearer, include in the RADIO LINK RECONFIGURATION RESPONSE message in the Additional E-DCH Cell Information Response RLReconf IE the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE for new E-DCH radio links on the Secondary UL frequency and/or include the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional Modified E-DCH FDD Information Response IE for radio links on the Secondary UL frequency that has been modified.] [1.28Mcps TDD - If the RADIO LINK RECONFIGURATION REQUEST message includes the Multi-Carrier E-DCH Information Reconf IE, then:] [1.28Mcps TDD - If the Multi-carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iur Transport Bearer Mode" the DRNS shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.] [1.28Mcps TDD - If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "UL Flow Multiplexing Mode" the DRNS shall use this mode in the new configuration and multiplex each MAC-d flow on one transport bearer.] [1.28Mcps TDD - If the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf IE is "Setup" and the Separate Iur transport bearer mode is used in the new configuration, or if the choice of Continue, Setup or Change in the the Multi-Carrier E-DCH Information Reconf IE is "Change" and the Transport Bearer Mode is changed to "Separate Iur Transport Bearer Mode" indicated by Multi-carrier EDCH Transport Bearer Mode LCR IE, then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.] [1.28Mcps TDD - The DRNS shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow, use the Transport Bearer Request Indicator IE in the

3GPP

Release 11

211

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH TDD Information to Modify IE received for the corresponding Radio Link to determine the transport bearer configuration in the new configuration for the all Uplink Frequencies.] [1.28Mcps TDD - If the E-DCH UL flow multiplexing mode is used in the new configuration and if the Transport Bearer Request Indicator IE is set to " Bearer Requested ", then the DRNS shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response 1.28Mcps IE in the RADIO LINK RECONFIGURATION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

Any allowed rate for the uplink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the uplink of a DCH due to congestion caused by the UL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Allowed UL Rate IE in the DCH Information Response IE for this Radio Link. Any allowed rate for the downlink of a modified DCH provided for the old configuration will not be valid for the new configuration. If the DRNS needs to limit the user rate in the downlink of a DCH due to congestion caused by the DL UTRAN Dynamic Resources (see subclause 9.2.1.79) in the new configuration for a Radio Link, the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Allowed DL Rate IE in the DCH Information Response IE for this Radio Link. The DRNS decides the maximum and minimum SIR for the uplink of the Radio Link(s), and the DRNC shall include in the RADIO LINK RECONFIGURATION RESPONSE message the Maximum Uplink SIR IE and Minimum Uplink SIR IE for each Radio Link when these values are changed. [FDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK RECONFIGURATION RESPONSE message. The DRNS shall not transmit with a higher power than indicated by the Maximum DL TX Power IE or lower than indicated by the Minimum DL TX Power IE on any DL DPCH or on the F-DPCH of the RL except, if the UE Context is configured to use DPCH in the downlink, during compressed mode, when the Pcurr, as described in TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.] [3.84 Mcps TDD and 7.68 Mcps TDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the maximum or minimum power needs to be different for particular DCH type CCTrCHs, the DRNC shall include the new value(s) for that CCTrCH in the CCTrCH Maximum DL TX Power IE and CCTrCH Minimum DL TX Power. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE/CCTrCH Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE/CCTrCH Minimum DL TX Power IE on any DL DPCH within each CCTrCH of the RL.] [1.28 Mcps TDD If the DL TX power upper or lower limit has been re-configured, the DRNC shall include the new value(s) in the Maximum DL TX Power IE and Minimum DL TX Power IE in the RADIO LINK RECONFIGURATION RESPONSE message. If the maximum or minimum power needs to be different for particular timeslots within a DCH type CCTrCH, the DRNC shall include the new value(s) for that timeslot in the Maximum DL TX Power IE and Minimum DL TX Power within the DL Timeslot Information LCR IE. The DRNS shall not transmit with a higher power than indicated by the appropriate Maximum DL TX Power IE or lower than indicated by the appropriate Minimum DL TX Power IE on any DL DPCH within each timeslot of the RL.]

8.3.7.3

Unsuccessful Operation

Figure 15: Unsynchronised Radio Link Reconfiguration procedure, Unsuccessful Operation If the DRNS cannot allocate the necessary resources for all the new DCHs in a set of co-ordinated DCHs requested to be added, it shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed.

3GPP

Release 11

212

3GPP TS 25.423 V11.2.0 (2012-06)

If the requested Unsynchronised Radio Link Reconfiguration procedure fails for one or more Radio Link(s), the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC, indicating the reason for failure. [FDD If the MIMO Activation Indicator IE is included and the Power Offset For S-CPICH for MIMO Request Indicator IE is not included in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE in the RADIO LINK RECONFIGURATION REQUEST message or MIMO is activated and the power offset for SCPICH for MIMO Request indicator has not been configured in the UE Context but MIMO pilot configuration with Primary and Secondary CPICH is set up with a non-zero power offset on the cell where the Serving HS-DSCH Radio Link is established, the setup of the serving HS-DSCH Radio Link, and/or activation of MIMO, shall be reported as failed and the DRNC shall include in the RADIO LINK RECONFIGURATION FAILURE message the Cause IE.] Typical cause values are: Radio Network Layer Causes: UL Scrambling Code Already in Use; DL Radio Resources not Available; UL Radio Resources not Available; Requested Configuration not Supported; CM not Supported; E-DCH not supported; [FDD Continuous Packet Connectivity DTX-DRX operation not Supported;] [FDD Continuous Packet Connectivity HS-SCCH less operation not Supported;] [FDD MIMO not supported;] [FDD E-DCH TTI2ms not supported;] [FDD Continuous Packet Connectivity DTX-DRX operation not available;] [FDD Continuous Packet Connectivity UE DTX Cycle not available;] [FDD MIMO not available;] [FDD SixteenQAM UL not Supported;] HS-DSCH MAC-d PDU Size Format not supported; E-DCH MAC-d PDU Size Format not available; [FDD E-DPCCH Power Boosting not supported;] [FDD SixtyfourQAM DL and MIMO Combined not available;] [FDD Multi Cell operation not available;] [FDD Multi Cell operation not supported;] [FDD SixtyfourQAM DL and MIMO Combined not supported;] [1.28Mcps TDD MIMO not available;] [1.28Mcps TDD- SixteenQAM UL not Supported;] [1.28Mcps TDD SixtyfourQAM DL and MIMO Combined not available;] [FDD Single Stream MIMO not supported;] [FDD Single Stream MIMO not available;] [FDD Multi Cell operation with MIMO not available;] [FDD Multi Cell operation with MIMO not supported;] [FDD Multi Cell E-DCH Operation not supported;] [FDD Multi Cell E-DCH Operation not available;] [FDD Multi Cell operation with Single Stream MIMO not available;] [FDD Multi Cell operation with Single Stream MIMO not supported;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Available;] [FDD Uplink Closed Loop Transmit Diversity Operation Not Supported.] Miscellaneous Causes: Control Processing Overload; Not enough User Plane Processing Resources.

8.3.7.4

Abnormal Conditions

If only a subset of all the DCHs belonging to a set of co-ordinated DCHs is requested to be deleted, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed, and the DRNC shall send the RADIO LINK RECONFIGURATION FAILURE message to the SRNC. If more than one DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected [TDD or no DCH of a set of co-ordinated DCHs has the QE-Selector IE set to selected], the DRNS shall reject the Unsynchronised Radio

3GPP

Release 11

213

3GPP TS 25.423 V11.2.0 (2012-06)

Link Reconfiguration procedure, and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message includes a DCHs To Modify IE or DCHs To Add IE with multiple DCH Specific Info IEs, and if the DCHs in the DCHs To Modify IE or DCHs To Add IE do not have the same Transmission Time Interval IE in the Semi-static Transport Format Information IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the DL Reference Power Information IE, but the power balancing is not active in the indicated RL(s), the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond the RADIO LINK RECONFIGURATION FAILURE message with the cause value Power Balancing status not compatible.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Common in the existing RL(s) but the DL Reference Power Information IE includes the Individual DL Reference Power Information IE, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value Power Balancing status not compatible.] [FDD If the power balancing is active with the Power Balancing Adjustment Type of the UE Context set to Individual in the existing RL(s) but the DL Reference Power Information IE includes the Common DL Reference Power IE, the DRNS shall reject the Unsynchronised Radio Link Reconfiguration procedure as having failed and the DRNC shall respond with the RADIO LINK RECONFIGURATION FAILURE message with the cause value Power Balancing status not compatible.] If the RADIO LINK RECONFIGURATION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for any Transport Channel or HS-DSCH MAC-d flow being added, or any Transport Channel or HS-DSCH MAC-d flow being modified for which a new transport bearer was requested with the Transport Bearer Request Indicator IE., and not both are present for a transport bearer intended to be established, the DRNC shall reject the Unsynchronised Radio Link Reconfiguration procedure, and the DRNC shall respond with a RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE or HS-DSCH MAC-d Flows To Delete IE in addition to the HS-DSCH Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information To Modify IE, HS-DSCH MAC-d Flows To Add IE, HS-DSCH MAC-d Flows To Delete IE or HS-PDSCH RL ID IE and the Serving HS-DSCH Radio Link is not in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-DSCH Information IE and does not include the HS-PDSCH RL-ID IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message includes the HS-PDSCH RL-ID IE indicating a Radio Link not existing in the UE Context, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message contains any of the HS-DSCH Information IE, HSDSCH Information To Modify IE, or HS-DSCH MAC-d Flows To Add IE and if in the new configuration the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Indexed MAC-d PDU Size for an HSDSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Maximum MACd PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Flexible MAC-d PDU Size for an HSDSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use MAC-d PDU Size Index, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.

3GPP

Release 11

214

3GPP TS 25.423 V11.2.0 (2012-06)

If, in the new configuration, the UE Context is configured to use Fixed MAC-d PDU Size for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use Flexible MAC-d PDU Size for an E-DCH and there exist a Logical Channel of the MAC-d flows of the E-DCH that is configured to use MAC-d PDU Size List, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the RADIO LINK RECONFIGURATION REQUEST message includes HS-DSCH Information IE and the HSDSCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the E-DCH FDD Information IE is present in the RADIO LINK RECONFIGURATION REQUEST message, but the E-DPCH Information IE is not present or if any of the Maximum Set of E-DPDCHs IE, Puncture Limit IE, E-TFCS Information IE, E-TTI IE, E-DPCCH Power Offset IE, E-RGCH 2-Index-Step Threshold IE, E-RGCH 3Index-Step Threshold IE, HARQ Info for E-DCH IE or HS-DSCH Configured Indicator IE are not present in the EDPCH Information IE, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If any of the HS-DSCH Configured Indicator IE, Maximum Set of E-DPDCHs IE, Puncture Limit IE or E-TTI IE are present in the E-DPCH Information IE and the E-DCH FDD Information IE is not present in the RADIO LINK RECONFIGURATION REQUEST message, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH RL Indication IE set to E-DCH, but no E-DCH FDD Information IE, and the UE Context is not configured for E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to E-DCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If the RADIO LINK RECONFIGURATION REQUEST message contains the HS-PDSCH RL ID IE and/or the Serving E-DCH RL IE and if both HS-DSCH and E-DCH are configured in the new configuration but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the HS-PDSCH RL ID IE and the EDPCH Information IE which includes the HS-DSCH Configured Indicator IE set as HS-DSCH not configured then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE or E-DCH MAC-d Flows To Delete IE in addition to the EDCH FDD Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains any of the E-DCH FDD Information To Modify IE, E-DCH MAC-d Flows To Add IE, E-DCH MAC-d Flows To Delete IE and the UE Context is not configured for E-DCH, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the E-DCH FDD Information To Modify IE deleting the last remaining E-DCH Logical Channel of an E-DCH MAC-d Flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes E-DCH FDD Information IE and the E-DCH is already configured in the UE Context, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE in addition to the Continuous Packet Connectivity DTX-DRX Information IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]

3GPP

Release 11

215

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE in addition to the Continuous Packet Connectivity HS-SCCH less Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. ] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity HS-SCCH less Deactivate Indicator IE while the Continuous Packet Connectivity HS-SCCH less configuration isnt configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DTX-DRX configuration isnt configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the DRX Information To Modify IE in Continuous Packet Connectivity DTX-DRX Information To Modify IE while the Continuous Packet Connectivity DRX configuration is not configured in the DRNC, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to Uplink DCH only but no Transport Format Set IE for the uplink for this DCH and the DRNC had ignored the configuration of Transport Format Set for uplink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If the DCHs to Modify IE contains a DCH Specific Info IE which includes the Unidirectional DCH Indicator IE set to Downlink DCH only but no Transport Format Set IE for the downlink for this DCH and the DRNC had ignored the configuration of Transport Format Set for downlink, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d flow but does not contain the corresponding DCH ID IE and the Unidirectional DCH indicator IE set to Uplink DCH only for the DCH in DCH Information To Add IE or does not contain the corresponding E-DCH MAC-d Flow ID IE in E-DCH MAC-d Flows Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply UL DPCCH Slot Format 0 or 2 and execute Continuous Packet Connectivity DTX-DRX operation, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply MIMO, allowed to apply 64QAM, establish the secondary serving HS-DSCH Radio Link or apply Single Stream MIMO in the new configuration but is not configured to use flexible MAC-d PDU Size, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional HS Cell Information RL Reconf Req IE indicating a new seconadry serving cell that is not in the same Node B as the serving HS-DSCH cell (or new serving in case of simultaneous serving HS-DSCH cell change), then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH in the RL Specific DCH Information IE but does not include the DCH ID IE for the DCH in the DCHs to Add IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE for an E-DCH MAC-d flow in the RL Specific E-DCH Information IE but does not include the E-DCH MAC-d flow ID IE for the E-DCH MAC-d flow in the E-DCH MAC-d flows Information IE, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Continuous Packet Connectivity DTX-DRX Information IE but the concerned UE Context is not previously configured to use F-DPCH, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message]

3GPP

Release 11

216

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the concerned UE Context is configured to have the Serving E-DCH Radio Link but there is at least one EDCH MAC-d flow which the transport bearer is not configured for the Serving E-DCH Radio Link in DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH or an E-DCH MAC-d Flow for a specific RL and the specific RL is combined with existing RL which the transport bearer is established for the DCH or the E-DCH MAC-d Flow in the DRNS, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] If ALCAP is not used, if the concerned UE Context is configured to establish a DCH, an E-DCH MAC-d flow and/or an HS-DSCH MAC-d flow but the RADIO LINK RECONFIGURATION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for the DCH, the E-DCH MAC-d flow and/or HS-DSCH MAC-d flow, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Flexible RLC PDU Size for an HS-DSCH but is not configured to use Maximum MAC-d PDU Size Extended, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. If, in the new configuration, the concerned UE Context is configured to use MAC-d PDU Size Index for an HS-DSCH but there exist a priority queue of the MAC-d flows of the HS-DSCH that is configured to use Flexible RLC PDU Size, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message. [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Reconf Req IE, then the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the concerned UE Context is configured to apply MIMO and Single Stream MIMO for the HS-DSCH Radio Link or the Secondary Serving Radio link, the DRNC shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH Cell Information RL Reconf Req IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the UE Context, then the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH Cell Information RL Reconf Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE in the Additional E-DCH Cell Information RL Reconf Req IE and the C-ID IE is not included but the RL indicated by the E-DCH Additional RL ID IE is not configured in the current UE context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional HS Cell Information RL Reconf Req IE and the new configuration contains more than one secondary serving HS-DSCH RL, and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1"which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE or the HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE, the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.] [FDD - If the RADIO LINK RECONFIGURATION REQUEST message contains the Additional HS Cell Information RL Reconf Req IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value "1", the DRNS shall reject the procedure using the RADIO LINK RECONFIGURATION FAILURE message.]

3GPP

Release 11

217

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.8 Physical Channel Reconfiguration

8.3.8.1 General
The Physical Channel Reconfiguration procedure is used by the DRNS to request the SRNC to reconfigure one of the configured physical channels. This procedure shall use the signalling bearer connection for the relevant UE Context. The DRNS shall not initiate the Physical Channel Reconfiguration procedure if a Prepared Reconfiguration exists as defined in subclause 3.1, or if a Synchronised Radio Link Reconfiguration Preparation procedure, Unsynchronised Radio Link Reconfiguration procedure or Radio Link Deletion procedure is ongoing for the relevant UE context.

8.3.8.2

Successful Operation
SRNC DRNC Layer Layer PHYSICAL CHANNEL RECONFIGURATION REQUEST
PHYSICAL CHANNEL RECONFIGURATION COMMAND

Figure 16: Physical Channel Reconfiguration procedure, Successful Operation When the DRNC detects the need to modify one of its physical channels, it shall send a PHYSICAL CHANNEL RECONFIGURATION REQUEST to the SRNC. The PHYSICAL CHANNEL RECONFIGURATION REQUEST message contains the new value(s) of the physical channel parameter(s) of the radio link for which the DRNC is requesting the reconfiguration. [FDD If compressed mode is prepared or active and at least one of the downlink compressed mode methods is SF/2, the DRNC shall include the Transmission Gap Pattern Sequence Scrambling Code Information IE in the DL Code Information IE in the PHYSICAL CHANNEL RECONFIGURATION REQUEST message indicating for each DL Channelisation Code whether the alternative scrambling code will be used or not if the downlink compressed mode methods SF/2 is activated.] [TDD The SRNC shall apply the new values for any of [3.84Mcps TDD UL Code Information IE, Midamble Shift And Burst Type IE,] [1.28Mcps TDD UL Code Information LCR IE, Midamble Shift LCR IE,] [7.68 Mcps TDD UL Code Information 7.68 Mcps IE, Midamble Shift And Burst Type 7.68 Mcps IE,] TDD DPCH Offset IE, Repetition Period IE, Repetition Length IE, or TFCI presence IE included in the UL DPCH Information IE within the PHYSICAL CHANNEL RECONFIGURATION REQUEST message, otherwise the previous values specified for this DPCH shall still apply.] [TDD The SRNC shall apply the new values for any of [3.84Mcps TDD DL Code Information IE, Midamble Shift And Burst Type IE,] [1.28Mcps TDD DL Code Information LCR IE, Midamble Shift LCR IE,] [7.68 Mcps TDD DL Code Information 7.68 Mcps IE, Midamble Shift And Burst Type 7.68 Mcps IE,] TDD DPCH Offset IE Repetition Period IE, Repetition Length IE, or TFCI presence IE included in the DL DPCH Information IE within the PHYSICAL CHANNEL RECONFIGURATION REQUEST message, otherwise the previous values specified for this DPCH shall still apply.] [3.84 Mcps TDD If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes HS-PDSCH Timeslot Specific Information IE the SRNC shall apply the values of the Midamble Shift And Burst Type IE for each HS-PDSCH timeslot.] [1.28 Mcps TDD If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes HS-PDSCH Timeslot Specific Information LCR IE the SRNC shall apply the values of the Midamble Shift LCR IE for each HS-PDSCH timeslot.] [1.28 Mcps TDD if the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes the PLCCH Information IE the SRNC shall modify, delete or grant a new PLCCH assignment to the indicated timeslot of the indicated UL DCH-type CCTrCH according to its content.]

3GPP

Release 11

218

3GPP TS 25.423 V11.2.0 (2012-06)

[7.68 Mcps TDD If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes HS-PDSCH Timeslot Specific Information 7.68 Mcps IE the SRNC shall apply the values of the Midamble Shift And Burst Type 7.68 Mcps IE for each HS-PDSCH timeslot.] [FDD If the PHYSICAL CHANNEL RECONFIGURATION REQUEST includes F-DPCH Slot Format IE the SRNC shall apply the values of the F-DPCH Slot Formats IE for F-DPCH Slot Format operation.] Upon receipt of the PHYSICAL CHANNEL RECONFIGURATION REQUEST, the SRNC shall decide an appropriate execution time for the change. The SRNC shall respond with a PHYSICAL CHANNEL RECONFIGURATION COMMAND message to the DRNC that includes the CFN IE indicating the execution time. At the CFN, the DRNS shall switch to the new configuration that has been requested, and release the resources related to the old physical channel configuration.

8.3.8.3

Unsuccessful Operation
SRNC Layer DRNC Layer

PHYSICAL CHANNEL RECONFIGURATION REQUEST PHYSICAL CHANNEL RECONFIGURATION FAILURE

Figure 17: Physical Channel Reconfiguration procedure, Unsuccessful Operation If the SRNC cannot accept the reconfiguration request it shall send the PHYSICAL CHANNEL RECONFIGURATION FAILURE message to the DRNC, including the reason for the failure in the Cause IE. Typical cause values are: Radio Network Layer Causes: Reconfiguration not Allowed.

8.3.8.4

Abnormal Conditions

While waiting for the PHYSICAL CHANNEL RECONFIGURATION COMMAND message, if the DRNC receives any of the RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION REQUEST, or RADIO LINK DELETION REQUEST messages, the DRNC shall abort the Physical Channel Reconfiguration procedure. These messages thus override the DRNC request for physical channel reconfiguration. When the SRNC receives a PHYSICAL CHANNEL RECONFIGURATION REQUEST message while a Synchronised Radio Link Reconfiguration procedure, Unsynchronised Radio Link Reconfiguration procedure or Radio Link Deletion procedure is ongoing, the SRNC shall ignore the request message and assume that receipt of any of the messages RADIO LINK RECONFIGURATION PREPARE, RADIO LINK RECONFIGURATION REQUEST or RADIO LINK DELETION REQUEST by the DRNC has terminated the Physical Channel Reconfiguration procedure. In this case the SRNC shall not send a PHYSICAL CHANNEL RECONFIGURATION FAILURE message to the DRNC.

8.3.9 Radio Link Failure

8.3.9.1 General
This procedure is started by the DRNS when one or more Radio Links [FDD or Radio Link Sets][TDD or CCTrCHs within a Radio Link] are no longer available. This procedure shall use the signalling bearer connection for the relevant UE Context. The DRNS may initiate the Radio Link Failure procedure at any time after establishing a Radio Link.

3GPP

Release 11

219

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.9.2

Successful Operation
SRNC Layer DRNC Layer RL unavailable
RADIO LINK FAILURE INDICATION

Figure 18: Radio Link Failure procedure, Successful Operation When the DRNC detects that one or more Radio Link(s) [FDD or Radio Link Set(s)] [TDD or CCTrCHs within a Radio Link] are no longer available, it shall send the RADIO LINK FAILURE INDICATION message to the SRNC. The message indicates the failed Radio Link(s) [FDD or Radio Link Set(s)] [TDD or CCTrCHs] with the most appropriate cause values defined in the Cause IE. If the failure concerns one or more individual Radio Links the DRNC shall include the affected Radio Link(s) using the RL Information IE. [FDD If the failure concerns one or more Radio Link Set(s) the DRNC shall include the affected Radio Link Set(s) using the RL Set Information IE.] [TDD If the failure concerns only the failure of one or more CCTrCHs within in a radio link the DRNC shall include the affected CCTrCHs using the CCTrCH ID IE.] When the RL Failure procedure is used to notify loss of UL synchronisation of a [FDD Radio Link Set] [TDD Radio Link or CCTrCHs within a Radio Link] on the Uu interface, the RADIO LINK FAILURE INDICATION message shall be sent with the Cause IE set to Synchronisation Failure when indicated by the UL synchronisation detection algorithm defined in TS 25.214 [10] subclause 4.3 and TS 25.224 [22] subclause 4.4.2. [FDD When the Radio Link Failure procedure is used to indicate permanent failure in one or more Radio Link(s)/Radio Link Set(s) due to the occurrence of an UL or DL frame with more than one transmission gap caused by one or more compressed mode pattern sequences, the DL transmission shall be stopped and the RADIO LINK FAILURE INDICATION message shall be sent with the Cause Value IE set to Invalid CM Settings. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the DRNS shall not remove the Radio Link(s)/Radio Link Set(s) from the UE Context, or remove the UE Context itself.] [FDD When the Radio Link Failure Procedure is used to indicate E-DCH non serving cell processing issue, the RADIO LINK FAILURE INDICATION shall be sent, with the Cause IE set to Not enough user plane processing resources.] In the other cases the Radio Link Failure procedure is used to indicate that one or more Radio Link(s) [FDD or Radio Link Set(s)] are permanently unavailable and cannot be restored. After sending the RADIO LINK FAILURE INDICATION message to notify the permanent failure, the DRNS shall not remove the Radio Link from the UE Context, or remove the UE Context itself. When applicable, the allocation retention priorities associated with the transport channels shall be used by the DRNS to prioritise which Radio Links to indicate as unavailable to the SRNC. Typical cause values are: Radio Network Layer Causes: Synchronisation Failure; Invalid CM Settings. Transport Layer Causes: Transport Resources Unavailable. Miscellaneous Causes: Control Processing Overload; HW Failure; O&M Intervention; Not enough user plane processing resources.

3GPP

Release 11

220

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.9.3
-

Abnormal Conditions

8.3.10 Radio Link Restoration

8.3.10.1 General
This procedure is used to notify establishment and re-establishment of UL synchronisation of one or more [FDD RL Set(s)] [TDD Radio Links or CCTrCH(s) in a Radio Link] on the Uu interface. This procedure shall use the signalling bearer connection for the relevant UE Context. The DRNC may initiate the Radio Link Restoration procedure at any time after establishing a Radio Link.

8.3.10.2

Successful Operation

Figure 19: Radio Link Restoration procedure, Successful Operation The DRNC shall send the RADIO LINK RESTORE INDICATION message to the SRNC when and as specified by the UL Uu synchronisation detection algorithm defined in TS 25.214 [10] subclause 4.3 and TS 25.224 [22] subclause 4.4.2 [FDD -, or when the Fast Reconfiguration Mode IE has been included in the RADIO LINK RECONFIGURATION COMMIT message and the DRNS has detected that the UE has changed to the new configuration. The algorithm in TS 25.214 [10] shall use the minimum value of the parameters N_INSYNC_IND that are configured in the cells supporting the radio links of the RL Set.] [TDD If the re-established UL Uu synchronisation concerns one or more individual Radio Links the DRNC shall include in the RADIO LINK RESTORE INDICATION message the RL Information IE to indicate the affected Radio Link(s). If the re-established synchronisation concerns one or more individual CCTrCHs within a radio link the DRNS shall include in the RADIO LINK RESTORE INDICATION message the RL Information IE to indicate the affected CCTrCHs.] [FDD If the re-established UL Uu synchronisation concerns one or more Radio Link Sets the DRNC shall include in the RADIO LINK RESTORE INDICATION message the RL Set Information IE to indicate the affected Radio Link Set(s).] [FDD The DRNC shall send the RADIO LINK RESTORE INDICATION message when the E-DCH processing issue condition has ceased.]

8.3.10.3
-

Abnormal Conditions

8.3.11 Dedicated Measurement Initiation

8.3.11.1 General
This procedure is used by an SRNS to request the initiation of dedicated measurements in a DRNS. This procedure shall use the signalling bearer connection for the relevant UE Context. The Dedicated Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

3GPP

Release 11

221

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.11.2

Successful Operation
SRNC DRNC

DEDICATED MEASUREMENT INITIATION REQUEST DEDICATED MEASUREMENT INITIATION RESPONSE

Figure 20: Dedicated Measurement Initiation procedure, Successful Operation The procedure is initiated with a DEDICATED MEASUREMENT INITIATION REQUEST message sent from the SRNC to the DRNC. Upon receipt, the DRNC shall initiate the requested dedicated measurement according to the parameters given in the DEDICATED MEASUREMENT INITIATION REQUEST message. If the Dedicated Measurement Object Type is indicated as being RL in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the indicated Radio Links. [FDD If the Dedicated Measurement Object Type is indicated as being RLS in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the indicated Radio Link Sets.] [FDD If the Dedicated Measurement Object Type is indicated as being ALL RL in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all current and future Radio Links within the UE Context.] [TDD If the Dedicated Measurement Object Type is indicated as being ALL RL in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for one existing DPCH per CCTrCH in each used time slot of current and future Radio Links within the UE Context, provided the measurement type is applicable to the respective DPCH.] [FDD If the Dedicated Measurement Object Type is indicated as being ALL RLS in the DEDICATED MEASUREMENT INITIATION REQUEST message, measurement results shall be reported for all the existing and future Radio Link Sets within the UE Context.] [TDD If the DPCH ID IE or DPCH ID 7.68Mcps IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually. If no DPCH ID IE, DPCH ID 7.68Mcps IE or HS-SICH ID IE is provided within the RL Information the measurement request shall apply for one existing DPCH per CCTrCH in each used time slot of the Radio Link, provided the measurement type is applicable to this DPCH.] [TDD If the HS-SICH Information IE is provided within the RL Information, the measurement request shall apply for the requested physical channel individually.] [TDD If the Dedicated Measurement Type IE is set to HS-SICH reception quality , the DRNS shall initiate measurements of the failed, missed and total HS-SICH transmissions on all of the HS-SICH assigned to this UE Context. If either the failed or missed HS-SICH transmission satisfies the requested report characteristics, the DRNS shall report the result of both failed and missed transmission measurements along with the total number of transmissions.] Report characteristics The Report Characteristics IE indicates how the reporting of the dedicated measurement shall be performed. See also Annex B. If the Report Characteristics IE is set to On Demand and if the CFN IE is not provided, the DRNS shall report the measurement result immediately in the DEDICATED MEASUREMENT INITIATION RESPONSE message. If the CFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]).

3GPP

Release 11

222

3GPP TS 25.423 V11.2.0 (2012-06)

If the Report Characteristics IE is set to Periodic and if the CFN IE is not provided, the DRNS shall immediately and periodically initiate the Dedicated Measurement Reporting procedure for this measurement, with a frequency as specified by the Report Periodicity IE. If the CFN IE is provided, the DRNS shall initiate a Dedicated Measurement Reporting procedure for this measurement at the CFN indicated in the CFN IE, and shall repeat this initiation periodically thereafter with a frequency as specified by the Report Periodicity IE. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the Report Characteristics IE is set to Event A, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the requested threshold, as specified by the Measurement Threshold IE, and then stays above the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the DRNC shall use the value zero for the hysteresis time. If the Report Characteristics IE is set to Event B, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the requested threshold, as specified by the Measurement Threshold IE, and then stays below the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the DRNC shall use the value zero for the hysteresis time. If the Report Characteristics IE is set to Event C, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this rise occurs within the requested rising time specified by the Measurement Change Time IE. After reporting this type of event, DRNS shall not initiate the next C event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE. If the Report Characteristics IE is set to Event D, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this falls occurs within the requested falling time specified by the Measurement Change Time IE. After reporting this type of event, the DRNS shall not initiate the next D event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE. If the Report Characteristics IE is set to Event E, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity rises above the Measurement Threshold 1 IE and stays above the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the DRNS shall initiate the Dedicated Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity falls below the Measurement Threshold 2 IE and stays below the threshold for the Measurement Hysteresis Time IE, the DRNS shall initiate the Dedicated Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the DRNS shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the DRNC shall use the value zero as hysteresis times for both Report A and Report B. If the Report Characteristics IE is set to Event F, the DRNS shall initiate the Dedicated Measurement Reporting procedure when the measured entity falls below the Measurement Threshold 1 IE and stays below the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the DRNS shall initiate the Dedicated Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity rises above the Measurement Threshold 2 IE and stays above the threshold for the Measurement Hysteresis Time IE, the DRNS shall initiate the Dedicated Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the DRNS shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the DRNC shall use the value zero as hysteresis times for both Report A and Report B. If the Report Characteristics IE is not set to On Demand, the DRNS is required to perform reporting for a dedicated measurement object, in accordance with the conditions provided in the DEDICATED MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no dedicated measurement object(s) for which a measurement is defined exists any more, the DRNS shall terminate the measurement locally without reporting this to the SRNC. If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the DRNS shall initiate the Dedicated Measurement Reporting procedure immediately, and then continue with the measurements as specified in the DEDICATED MEASUREMENT INITIATION REQUEST message. Higher layer filtering The Measurement Filter Coefficient IE indicates how filtering of the dedicated measurement values shall be performed before measurement event evaluation and reporting.

3GPP

Release 11

223

3GPP TS 25.423 V11.2.0 (2012-06)

The averaging 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 DEDICATED MEASUREMENT INITIATION RESPONSE, DEDICATED MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn). A = (k/2) , where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no 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. Measurement Recovery Behavior: If the Measurement Recovery Behavior IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNS shall, if Measurement Recovery Behavior is supported, include the Measurement Recovery Support Indicator IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.3.12.2. Response message If the DRNS was able to initiate the measurement requested by the SRNS it shall respond with the DEDICATED MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message. In the case in which the Report Characteristics IE is set to On Demand: The DRNC shall include the measurement result in the Dedicated Measurement Value IE within the DEDICATED MEASUREMENT INITIATION RESPONSE message. If the CFN Reporting Indicator IE is set to FN Reporting Required, the CFN IE shall be included in the DEDICATED MEASUREMENT INITIATION RESPONSE message. The reported CFN shall be the CFN at the time when the dedicated measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). [TDD If the measurement was made on a particular DPCH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the DPCH ID of that DPCH in the [1.28Mcps TDD and 3.84Mcps TDD DPCH ID IE] [7.68Mcps TDD DPCH ID 7.68Mcps IE].] [TDD If the measurement was made on a particular HS-SICH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the ID of that HS-SICH in the HS-SICH ID IE.]

[FDD If the Alternative Format Reporting Indicator IE is set to Alternative format is allowed in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNC may include the Extended Round Trip Time IE in the DEDICATED MEASUREMENT INITIATION RESPONSE message.]

3GPP

Release 11

224

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.11.3

Unsuccessful Operation
SRNC DRNC

DEDICATED MEASUREMENT INITIATION REQUEST DEDICATED MEASUREMENT INITIATION FAILURE

Figure 21: Dedicated Measurement Initiation procedure, Unsuccessful Operation If the requested measurement cannot be initiated for one of the RL/RLS, the DRNC shall send a DEDICATED MEASUREMENT INITIATION FAILURE message. The message shall include the same Measurement ID IE that was used in the DEDICATED MEASUREMENT INITIATION REQUEST message and shall include the Cause IE set to an appropriate value. If the DEDICATED MEASUREMENT INITIATION REQUEST message includes the Partial Reporting Indicator IE, the DRNS shall, if partial reporting is supported, separate the unsuccessful measurement initiations from the successful measurement initiations. For the successful measurement initiations on a RL or an RLS, the DRNS shall include the Successful RL Information IE or the Successful RL Set Information IE for the concerned RL or RLS if the Report Characteristics IE in the DEDICATED MEASUREMENT INITIATION REQUEST message was set to On Demand. For the unsuccessful measurement initiations, the DRNS shall include the Individual Cause IE set to an appropriate value if it differs from the value of the Cause IE. Typical cause values are: Radio Network Layer Causes: Measurement not Supported For The Object Measurement Temporarily not Available Miscellaneous Causes: Control Processing Overload HW Failure

8.3.11.4

Abnormal Conditions

The allowed combinations of the Dedicated Measurement Type and Report Characteristics Type are shown in the table below marked with X. For not allowed combinations, the DRNS shall reject the Dedicated Measurement Initiation procedure using the DEDICATED MEASUREMENT INITIATION FAILURE message.

3GPP

Release 11

225

3GPP TS 25.423 V11.2.0 (2012-06)

Table 4: Allowed Dedicated Measurement Type and Report Characteristics Type combinations
Dedicated Measurement Type SIR SIR Error Transmitted Code Power RSCP Rx Timing Deviation Round Trip Time Rx Timing Deviation LCR HS-SICH Reception Quality Angle Of Arrival LCR Rx Timing Deviation 7.68Mcps Rx Timing Deviation 3.84Mcps Extended On Demand X X X X X X X X X X X Periodic X X X X X X X X X X X Report Characteristics Type Event A Event B Event C Event D Event E Event F X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X On Modification

If the Dedicated Measurement Type received in the Dedicated Measurement Type IE is not defined in TS 25.215 [11] or TS 25.225 [14] to be measured on the Dedicated Measurement Object Type received in the DEDICATED MEASUREMENT INITIATION REQUEST message, the DRNS shall reject the Dedicated Measurement Initiation procedure. If the CFN IE is included in the DEDICATED MEASUREMENT INITIATION REQUEST message and the Report Characteristics IE is other than Periodic or On Demand, the DRNS shall reject the Dedicated Measurement Initiation procedure, and the DRNC shall send a DEDICATED MEASUREMENT INITIATION FAILURE message.

8.3.12 Dedicated Measurement Reporting

8.3.12.1 General
This procedure is used by the DRNS to report the results of the successfully initiated measurements requested by the SRNS with the Dedicated Measurement Initiation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context. The DRNC may initiate the Dedicated Measurement Reporting procedure at any time after establishing a Radio Link.

8.3.12.2

Successful Operation
SRNC DRNC

DEDICATED MEASUREMENT REPORT

Figure 22: Dedicated Measurement Reporting procedure, Successful Operation If the requested measurement reporting criteria are met, the DRNS shall initiate the Dedicated Measurement Reporting procedure. If the measurement was initiated (by the Dedicated Measurement Initiation procedure) for multiple dedicated measurement objects, the DRNC may include dedicated measurement values in the Dedicated Measurement Value Information IE for multiple objects in the DEDICATED MEASUREMENT REPORT message. The Measurement ID IE shall be set to the Measurement ID provided by the SRNC when initiating the measurement with the Dedicated Measurement Initiation procedure.

3GPP

Release 11

226

3GPP TS 25.423 V11.2.0 (2012-06)

If the achieved measurement accuracy does not fulfil the given accuracy requirement specified in TS 25.133 [23] and TS 25.123 [24] or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Measurement not available shall be reported in the Dedicated Measurement Value Information IE in the DEDICATED MEASUREMENT REPORT message, otherwise the DRNC shall include the Dedicated Measurement Value IE within the Dedicated Measurement Value Information IE. If the DRNC was configured to perform the Measurement Recovery Behavior, the DRNC shall indicate Measurement Available to the SRNC when the achieved measurement accuracy again fullfils the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) and include the Measurement Recovery Report Indicator IE in the DEDICATED MEASUREMENT REPORT message if the requested measurement reporting criteria are not met. If the CFN Reporting Indicator when initiating the measurement with the Dedicated Measurement Initiation procedure was set to FN Reporting Required, the DRNC shall include the CFN IE in the DEDICATED MEASUREMENT REPORT message. The reported CFN shall be the CFN at the time when the dedicated measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). [TDD If the measurement was made on a particular DPCH, the DEDICATED MEASUREMENT REPORT message shall include the DPCH ID of that DPCH in the [1.28Mcps TDD and 3.84Mcps TDD DPCH ID IE] [7.68Mcps TDD DPCH ID 7.68Mcps IE].] [TDD If the measurement was made on a particular HS-SICH, the DEDICATED MEASUREMENT INITIATION RESPONSE message shall include the ID of that HS-SICH in the HS-SICH ID IE.] [FDD If the Alternative Format Reporting Indicator IE was set to Alternative format is allowed in the DEDICATED MEASUREMENT INITIATION REQUEST message setting up the measurement to be reported, the DRNC may include the Extended Round Trip Time IE in the DEDICATED MEASUREMENT REPORT message.]

8.3.12.3
-

Abnormal Conditions

8.3.13 Dedicated Measurement Termination

8.3.13.1 General
This procedure is used by the SRNS to terminate a measurement previously requested by the Dedicated Measurement Initiation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context. The Dedicated Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.13.2

Successful Operation
SRNC
DEDICATED MEASUREMENT TERMINATION REQUEST

DRNC

Figure 23: Dedicated Measurement Termination procedure, Successful Operation This procedure is initiated with a DEDICATED MEASUREMENT TERMINATION REQUEST message, sent from the SRNC to the DRNC. Upon receipt, the DRNS shall terminate reporting of dedicated measurements corresponding to the received Measurement ID IE.

8.3.13.3
-

Abnormal Conditions

3GPP

Release 11

227

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.14 Dedicated Measurement Failure

8.3.14.1 General
This procedure is used by the DRNS to notify the SRNS that a measurement previously requested by the Dedicated Measurement Initiation procedure can no longer be reported. When partial reporting is allowed and supported, this procedure shall be used to report that measurement for one or more RL/RLS can no longer be reported. This procedure shall use the signalling bearer connection for the relevant UE Context. The DRNC may initiate the Dedicated Measurement Failure procedure at any time after establishing a Radio Link.

8.3.14.2

Successful Operation

Figure 24: Dedicated Measurement Failure procedure, Successful Operation This procedure is initiated with a DEDICATED MEASUREMENT FAILURE INDICATION message, sent from the DRNC to the SRNC, to inform the SRNC that a previously requested dedicated measurement can no longer be reported. The DRNC has locally terminated the indicated measurement. The DRNC shall include in the DEDICATED MEASUREMENT FAILURE INDICATION message the reason for the failure in the Cause IE. The DRNS shall include Unsuccessful RL Information IE or the Unsuccessful RL Set Information IE for the concerned RL or RLS if partial reporting is allowed and it is supported. The DRNS shall include the Individual Cause IE set to an appropriate value if it differs from the value of the Cause IE. Typical cause values are: Miscellaneous Causes: Control Processing Overload HW Failure O&M Intervention

8.3.14.3
-

Abnormal Conditions

8.3.15 Downlink Power Control [FDD]

8.3.15.1 General
The purpose of this procedure is to balance the DL transmission powers of one or more radio links for one UE. This procedure shall use the signalling bearer connection for the relevant UE Context. The Downlink Power Control procedure may be initiated by the SRNC at any time after establishing a Radio Link. If the SRNC has initiated in this DRNS the deletion of the last Radio Link for this UE context, the Downlink Power Control procedure shall not be initiated.

3GPP

Release 11

228

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.15.2

Successful Operation
SRNC Layer
DL POWER CONTROL REQUEST

DRNC Layer

Figure 25: Downlink Power Control procedure, Successful Operation The Downlink Power Control procedure is initiated by the SRNC sending a DL POWER CONTROL REQUEST message to the DRNC. The Power Adjustment Type IE defines the characteristic of the power adjustment. If the value of the Power Adjustment Type IE is Common, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to Common. As long as the Power Balancing Adjustment Type of the UE Context is set to Common, the DRNS shall perform the power adjustment (see below) for all existing and future radio links for the UE Context and use a common DL reference power level. If the value of the Power Adjustment Type IE is Individual, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to Individual. The DRNS shall perform the power adjustment (see below) for all radio links addressed in the message using the given DL Reference Power per RL. If the Power Balancing Adjustment Type of the UE Context was set to Common before this message was received, power balancing on all radio links not addressed by the DL POWER CONTROL REQUEST message shall remain to be executed in accordance with the existing power balancing parameters which are now considered RL individual parameters. Power balancing will not be started on future radio links without a specific request. If the value of the Power Adjustment Type IE is None, the DRNS shall set the Power Balancing Adjustment Type of the UE Context set to None and the DRNS shall suspend on going power adjustments for all radio links for the UE Context. If the Inner Loop DL PC Status IE is present and set to Active, the DRNS shall activate inner loop DL power control for all radio links for the UE Context. If the Inner Loop DL PC Status IE is present and set to Inactive, the DRNS shall deactivate inner loop DL power control for all radio links for the UE Context according to TS 25.214 [10]. Power Adjustment The power balancing adjustment shall be superimposed on the inner loop power control adjustment (see TS 25.214 [10]) if activated. The power balancing adjustment shall be such that:

bal

= (1 r )( Pref + PP CPICH Pinit ) with an accuracy of 0.5 dB

where the sum is performed over an adjustment period corresponding to a number of frames equal to the value of the Adjustment Period IE, Pref is the value of the DL Reference Power IE, PP-CPICH is the power used on the primary CPICH, Pinit is the code power of the last slot of the previous adjustment period and r is given by the Adjustment Ratio IE. If the last slot of the previous adjustment period is within a transmission gap due to compressed mode, Pinit shall be set to the same value as the code power of the slot just before the transmission gap. The adjustment within one adjustment period shall in any case be performed with the constraints given by the Max Adjustment Step IE and the DL TX power range set by the DRNC. The power adjustments shall be started at the first slot of a frame with CFN modulo the value of Adjustment Period IE equal to 0 and shall be repeated for every adjustment period and shall be restarted at the first slot of a frame with CFN=0, until a new DL POWER CONTROL REQUEST message is received or the RL is deleted.

8.3.15.3
-

Abnormal Conditions

3GPP

Release 11

229

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.16 Compressed Mode Command [FDD]

8.3.16.1 General
The Compressed Mode Command procedure is used to activate or deactivate the compressed mode in the DRNS for one UE-UTRAN connection. This procedure shall use the signalling bearer connection for the relevant UE Context. The Compressed Mode Command procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.16.2

Successful Operation

Figure 26: Compressed Mode Command procedure, Successful Operation The procedure is initiated by the SRNC sending a COMPRESSED MODE COMMAND message to the DRNC. Upon receipt of the COMPRESSED MODE COMMAND message from the SRNC and at the CFN indicated in the CM Configuration Change CFN IE, the DRNS shall deactivate all the ongoing Transmission Gap Pattern Sequences. From that moment on all Transmission Gap Pattern Sequences included in Transmission Gap Pattern Sequence Status IE repetitions (if present) shall be started when the indicated TGCFN IE elapses. The CM Configuration Change CFN IE in the Active Pattern Sequence Information IE and TGCFN IE for each sequence refer to the next coming CFN with that value. If the values of the CM Configuration Change CFN IE and the TGCFN IE are equal, the concerned Transmission Gap Pattern Sequence shall be started immediately at the CFN with a value equal to the value received in the CM Configuration Change CFN IE. If the Affected HS-DSCH serving cell List IE is included, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells. If the concerned UE Context is configured to use F-DPCH in the downlink, the DRNS shall ignore, when activating the Transmission Gap Pattern Sequence(s), the downlink compressed mode method information, if existing, for the concerned Transmission Gap Pattern Sequence(s) in the Compressed Mode Configuration.

8.3.16.3

Abnormal Conditions

[FDD - If the Affected HS-DSCH serving cell List IE is included in the Active Pattern Sequence Information IE, and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the DRNS shall initiate the Radio Link Failure procedure with the cause value Invalid CM Settings.]

8.3.17 Downlink Power Timeslot Control [TDD]

8.3.17.1 General
The purpose of this procedure is to provide the DRNS with updated DL Timeslot ISCP values to use when deciding the DL TX Power for each timeslot. This procedure shall use the signalling bearer connection for the relevant UE Context. The Downlink Power Timeslot Control procedure can be initiated by the SRNC at any time after establishing a Radio Link. If the SRNC has initiated deletion of the last Radio Link in this DRNS, the Downlink Power Timeslot Control procedure shall not be initiated.

3GPP

Release 11

230

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.17.2

Successful Operation
SRNC Layer
DL POWER TIMESLOT CONTROL REQUEST

DRNC Layer

Figure 26A: Downlink Power Timeslot Control procedure, Successful Operation The Downlink Power Timeslot Control procedure is initiated by the SRNC sending a DL POWER TIMESLOT CONTROL REQUEST message to the DRNC. Upon receipt of the DL POWER TIMESLOT CONTROL REQUEST message, the DRNS shall use the included [3.84Mcps TDD and 7.68 Mcps TDD DL Timeslot ISCP Info IE] [1.28Mcps TDD DL Timeslot ISCP Info LCR IE] value when deciding the DL TX Power for each timeslot as specified in TS 25.224 [22], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link in which the interference is low, and increase the DL TX power in those timeslots in which the interference is high, while keeping the total downlink power in the radio link unchanged. If the Primary CCPCH RSCP Delta IE is included, the DRNS shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included and the Primary CCPCH RSCP IE is included, the DRNS shall assume that the reported value is in the non-negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP IE. The DRNS should use the indicated value for HS-DSCH scheduling and transmit power adjustment.

8.3.17.3
-

Abnormal Conditions

8.3.18 Radio Link Pre-emption

8.3.18.1 General
This procedure is started by the DRNS when resources need to be freed. This procedure shall use the signalling bearer connection for the UE Context associated with the RL to be pre-empted. The DRNS may initiate the Radio Link Pre-emption procedure at any time after establishing a Radio Link.

8.3.18.2

Successful Operation
SRNC Layer DRNC Layer RL to be preempted

RADIO LINK PREEMPTION REQUIRED INDICATION

Figure 26B: Radio Link Pre-emption procedure, Successful Operation When DRNC detects that one or more Radio Link(s) should be pre-empted (see Annex A), it shall send the RADIO LINK PREEMPTION REQUIRED INDICATION message to the SRNC. If all Radio Links for a UE Context should be pre-empted, the RL Information IE shall not be included in the message. If one or several but not all Radio Link(s) should be pre-empted for an UE Context, the Radio Link(s) that should be pre-empted shall be indicated in the RL Information IE. The Radio Link(s) that should be pre-empted, should be deleted by the SRNC.

3GPP

Release 11

231

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If only the E-DCH traffic on a Radio Link should be pre-empted, the DRNC shall indicate the EDCH MAC-d flows that should be pre-empted by including the E-DCH MAC-d Flow Specific Information IE in the RADIO LINK PREEMPTION REQUIRED INDICATION message.] When only the HS-DSCH traffic on a Radio Link should be pre-empted, the DRNC shall indicate the HS-DSCH MACd flow(s) that should be pre-empted by including the HS-DSCH MAC-d Flow Specific Information IE in the RADIO LINK PREEMPTION REQUIRED INDICATION message.

8.3.18.3
-

Abnormal Conditions

8.3.19 Radio Link Congestion

8.3.19.1 General
This procedure is started by the DRNS when resource congestion is detected and the rate of one or more DCHs, corresponding to one or more radio links, is preferred to be limited in the UL and/or DL. This procedure is also used by the DRNC to indicate to the SRNC any change of the UL/DL resource congestion situation, affecting these radio links. This procedure shall use the signalling bearer connection for the relevant UE Context. The Radio Link Congestion procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.19.2

Successful Operation

Figure 26C: Radio Link Congestion procedure, Successful Operation Start of an UL/DL Resource Congestion Situation When the DRNC detects the start of a UL/DL resource congestion situation and prefers the rate of one or more DCHs for one or more Radio Link(s) to be limited below the maximum rate currently configured in the UL/DL TFS, it shall send the RADIO LINK CONGESTION INDICATION message to the SRNC. The DRNC shall indicate the cause of the congestion in the Congestion Cause IE and shall indicate all the Radio Links for which the rate of a DCH needs to be reduced. For each DCH within the RL with UL congestion, the DRNC shall indicate the desired maximum UL data rate with the Allowed UL Rate IE in the Allowed Rate Information IE. For each DCH within the RL with DL congestion, the DRNC shall indicate the desired maximum DL data rate with the Allowed DL Rate IE in the Allowed Rate Information IE. [FDD For each E-DCH MAC-d flow within the RL with UL congestion, the DRNC shall indicate all the MAC-d flows for which the rate cannot be fullfilled.] When receiving the RADIO LINK CONGESTION INDICATION message the SRNC should reduce the rate in accordance with the Congestion Cause IE and the indicated Allowed DL Rate IE and/or Allowed UL Rate IE for a DCH. [FDD If the RADIO LINK CONGESTION INDICATION message includes the DCH Indicator For E-DCH-HSDPA Operation IE, then the SRNS shall ignore the DCH Rate Information IE in the RADIO LINK CONGESTION INDICATION message.] Change of UL/DL Resource Congestion Situation The DRNC shall indicate any change of the UL/DL resource congestion situation by sending the RADIO LINK CONGESTION INDICATION message in which the new allowed rate(s) of the DCHs are indicated by the Allowed Rate Information IE. In the case that for at least one DCH the new allowed rate is lower than the previously indicated allowed rate for that DCH, the Congestion Cause IE, indicating the cause of the congestion, shall also be included.

3GPP

Release 11

232

3GPP TS 25.423 V11.2.0 (2012-06)

When receiving a RADIO LINK CONGESTION INDICATION message indicating a further rate decrease on any DCH(s) on any RL, the SRNC should reduce the rate in accordance with the indicated congestion cause and the indicated allowed rate(s) for the DCH(s). End of UL/DL Resource Congestion Situation The end of an UL resource congestion situation, affecting a specific RL, shall be indicated by including the TF corresponding to the highest data rate in the Allowed UL Rate IE in the Allowed Rate Information IE for the concerned RL. The end of a DL resource congestion situation, affecting a specific RL, shall be indicated by including the TF with the highest data rate in the Allowed DL Rate IE in the Allowed Rate Information IE for the concerned RL.

8.3.19.3
-

Abnormal Conditions

8.3.20 Radio Link Activation

8.3.20.1 General
This procedure is used to activate or de-activate the DL transmission on the Uu interface regarding selected RLs.

8.3.20.2

Successful Operation

Figure 26D: Radio Link Activation procedure This procedure is initiated by sending the RADIO LINK ACTIVATION COMMAND message from the SRNC to the DRNC. This procedure shall use the signalling bearer connection for the relevant UE Context. Upon receipt, the DRNS shall for each concerned RL: if the Delayed Activation Update IE indicates Activate: - if the Activation Type IE equals Unsynchronised: [FDD start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [4].] [TDD start transmission on the new RL immediately as specified in TS 25.427 [4].]

- if the Activation Type IE equals Synchronised: [FDD start transmission on the new RL after synchronisation is achieved in the DL user plane as specified in TS 25.427 [4], however never before the CFN indicated in the Activation CFN IE.] [TDD start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [4].]

- [FDD the DRNS shall apply the power level indicated in the Initial DL Tx Power IE to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or power balancing is activated. During this period no inner loop power control shall be performed and, unless activated by the DL POWER CONTROL REQUEST message, no power balancing shall be performed. The DL power shall then vary according to the inner loop power control (see TS 25.214 [10], subclause 5.2.1.2) and downlink power balancing adjustments (see 8.3.7).] - [TDD the DRNS shall apply the power level indicated in the Initial DL Tx Power IE to the transmission on each DL DPCH and on each Time Slot of the RL when starting transmission until the UL synchronisation on

3GPP

Release 11

233

3GPP TS 25.423 V11.2.0 (2012-06)

the Uu interface is achieved for the RL. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see TS 25.224 [22], subclause 4.2.3.3).] - [FDD if the Propagation Delay IE and optionally the Extended Propagation Delay IE are included, the DRNS may use this information to speed up the detection of UL synchronisation on the Uu interface.] - [FDD if the First RLS Indicator IE is included, it indicates if the concerned RL shall be considered part of the first RLS established towards this UE. The First RLS Indicator IE shall be used by the DRNS to determine the initial TPC pattern in the DL of the concerned RL and all RLs which are part of the same RLS, as described in TS 25.214 [10], section 5.1.2.2.1.2.] if the Delayed Activation Update IE indicates Deactivate: - stop DL transmission immediately if the Deactivation Type IE equals Unsynchronised, or at the CFN indicated by the Deactivation CFN IE if the Deactivation Type IE equals Synchronised.

8.3.20.3

Abnormal Conditions

[FDD If the Delayed Activation Update IE is included in the RADIO LINK ACTIVATION COMMAND message, it indicates Activate and the First RLS Indicator IE is not included, the DRNC shall initiate the ERROR INDICATION procedure.]

8.3.21 Radio Link Parameter Update

8.3.21.1 General
The Radio Link Parameter Update procedure is executed by the DRNS to update parameters related to HS-DSCH [FDD - or E-DCH or UL CLTD] on a radio link for a UE-UTRAN connection or to update phase reference on a list of the radio links. This procedure shall use the signalling bearer connection for the relevant UE context. The Radio Link Parameter Update procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.21.2

Successful Operation
SRNC
RADIO LINK PARAMETER UPDATE INDICATION

DRNC

Figure 26E: Radio Link Parameter Update Indication, Successful Operation The Radio Link Parameter Update procedure is initiated by the DRNS by sending the RADIO LINK PARAMETER UPDATE INDICATION message to the SRNC. HS-DSCH related Parameter(s) Updating: If RADIO LINK PARAMETER UPDATE INDICATION message is used to update the parameters related to HSDSCH, it contains suggested value(s) of the HS-DSCH related parameter(s) that should be reconfigured on the radio link. If the DRNS needs to update HS-DSCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including [FDD HS-DSCH FDD Update Information IE] [TDD HS-DSCH TDD Update Information IE]. If the DRNS needs to allocate new HS-SCCH Codes, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including HS-SCCH Code Change Indicator IE. [FDD If the DRNS needs to allocate new HS-PDSCH Codes, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including HS-PDSCH Code Change Indicator IE.]

3GPP

Release 11

234

3GPP TS 25.423 V11.2.0 (2012-06)

[FDD If the DRNS needs to update the CQI Feedback Cycle k, CQI Repetition Factor, ACK-NACK Repetition Factor, CQI Power Offset, ACK Power Offset and/or NACK Power Offset, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including CQI Feedback Cycle k IE, CQI Repetition Factor IE, ACK-NACK Repetition Factor IE, CQI Power Offset IE, ACK Power Offset IE and/or NACK Power Offset IE.] [TDD If the DRNS needs to update the TDD ACK-NACK Power Offset the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including TDD ACK-NACK Power Offset IE.] [FDD Secondary Serving HS-DSCH related Parameter(s) Updating:] [FDD If RADIO LINK PARAMETER UPDATE INDICATION message is used to update the parameters related to secondary serving HS-DSCH, it contains suggested value(s) of the secondary serving HS-DSCH related parameter(s) that should be reconfigured on the radio link.] [FDD If the DRNS needs to update secondary serving HS-DSCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message and include the Additional HS Cell Information RL Param Upd IE.] [FDD If the DRNS needs to allocate new secondary serving HS-SCCH Codes, the DRNS shall include the HSSCCH Code Change Indicator IE in the HS-DSCH FDD Secondary Serving Update Information IE.]

[FDD Phase Reference Handling:] [FDD If DRNS needs to update phase reference for the channel estimation for one or several Radio Links, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Phase Reference Update Information IE for the concerned RL(s).] [FDD E-DCH:] [FDD If DRNS needs to update E-DCH related parameters, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including E-DCH FDD Update Information IE.] [FDD If the DRNS needs to update the HARQ process allocation for non-scheduled transmission and/or HARQ process allocation for scheduled Transmission, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE for the concerned MAC-d Flows and/or HARQ Process Allocation For 2ms Scheduled Transmission Grant IE.] [FDD If the DRNS needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including E-DCH DL Control Channel Change Information IE.] [FDD If the DRNS needs to update Additional E-DCH related parameters, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Additional E-DCH Cell Information RL Param Upd IE.] [FDD If the DRNS needs to update the HARQ process allocation for scheduled Transmission, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including the HARQ Process Allocation For 2ms Scheduled Transmission Grant .] [FDD If the DRNS needs to allocate new E-AGCH Channelisation Code, new E-RGCH/E-HICH Channelisation Code, new E-RGCH Signature Sequence and/or new E-HICH Signature Sequence, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including Additional E-DCH DL Control Channel Change Information IE.]

[FDD UL CLTD:] [FDD - If the DRNS needs to update the local activation state of UL CLTD of the UE in UL CLTD operation, the DRNS shall initiate RADIO LINK PARAMETER UPDATE INDICATION including the UL CLTD State Update Information IE.] [FDD CPC Recovery:] [FDD If the DRNS needs to indicate that the CPC Recovery has been initiated, the DRNC shall initiate RADIO LINK PARAMETER UPDATE INDICATION message including CPC Recovery Report IE.]

3GPP

Release 11

235

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.21.3
-

Abnormal Conditions

8.3.22 UE Measurement Initiation [TDD]

8.3.22.1 General
This procedure is used by a DRNC to request the initiation of UE measurements by the SRNC. This procedure shall use the signalling bearer connection for the relevant UE Context. The UE Measurement Initiation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.22.2

Successful Operation
SRNC DRNC

UE MEASUREMENT INITIATION REQUEST

UE MEASUREMENT INITIATION RESPONSE

Figure 26F: UE Measurement Initiation procedure, Successful Operation The procedure is initiated with a UE MEASUREMENT INITIATION REQUEST message sent from the DRNC to the SRNC. Upon receipt the SRNC shall, provided that it determines that the measurement can be performed by the UE, initiate and forward the requested UE measurement according to the parameters given in the UE MEASUREMENT INITIATION REQUEST message. If the UE MEASUREMENT INITIATION REQUEST message includes the UE Measurement Parameter Modification Allowed IE with a value of Parameter Modification Allowed the UE Measurement Report Characteristics IE and the Measurement Filter Coefficient IE, if it is included, are suggested values, otherwise the values of these parameters must be fulfilled. [3.84 Mcps TDD If the UE Measurement Timeslot Information HCR IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the UE Measurement Timeslot Information HCR IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.] [1.28 Mcps TDD If the UE Measurement Timeslot Information LCR IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the UE Measurement Timeslot Information LCR IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.] [7.68 Mcps TDD If the UE Measurement Timeslot Information 7.68 Mcps IE is provided, the measurement request shall apply for the requested timeslot(s) individually. If the UE Measurement Timeslot Information 7.68 Mcps IE are not provided the SRNC may choose the timeslots for measurements that apply to individual timeslots.] If the UE MEASUREMENT INITIATION REQUEST message includes the Allowed Queuing Time IE the SRNC may queue the request for a time period not to exceed the value of the Allowed Queuing Time IE before starting to execute the request. The SRNC is required to perform reporting for a UE measurement object, in accordance with the conditions provided in the UE MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no UE measurement object(s) for which a measurement is defined exists any more, the SRNC shall terminate the measurement locally without reporting this to the DRNC. If at the start of the measurement, the reporting criteria are fulfilled for any of Event 1h, Event 1i,Event 6a, Event 6b, Event 6c, or Event 6d, the SRNC shall initiate the UE Measurement Reporting procedure immediately, and then continue with the measurements as specified in the UE MEASUREMENT INITIATION REQUEST message

3GPP

Release 11

236

3GPP TS 25.423 V11.2.0 (2012-06)

At the start of a periodic measurement, the SRNC shall not initiate UE Measurement Reporting procedure until the next measurement is received from the UE, even if measurement data is available. Report characteristics The UE Measurement Report Characteristics IE indicates how the reporting of the dedicated measurement shall be performed. See TS 25.331 [16]. Higher layer filtering The Measurement Filter Coefficient IE indicates how filtering of the dedicated measurement values shall be performed before measurement event evaluation and reporting. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering). The use of the Measurement Filter Coefficient IE is shown in TS 25.331 [16]. Response message If the SRNC was able to initiate the measurement requested by the DRNC it shall respond with the UE MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the UE MEASUREMENT INITIATION REQUEST message. If the DRNC allowed parameter modification and the SRNC modified the Measurement Filter Coefficient IE the SRNC shall include the modified value in the UE MEASUREMENT INTIATION RESPONSE message. If the DRNC allowed parameter modification and the SRNC modified the UE Measurement Report Characteristics IE the SRNC shall include the modified value in the UE MEASUREMENT INTIATION RESPONSE message.

8.3.22.3

Unsuccessful Operation
SRNC DRNC

UE MEASUREMENT INITIATION REQUEST

UE MEASUREMENT INITIATION FAILURE

Figure 26G: UE Measurement Initiation procedure, Unsuccessful Operation If the requested measurement cannot be initiated, the SRNC shall send a UE MEASUREMENT INITIATION FAILURE message. The message shall include the same Measurement ID IE that was used in the UE MEASUREMENT INITIATION REQUEST message and shall include the Cause IE set to an appropriate value. Typical cause values are: Radio Network Layer Causes: Measurement not Supported For The Object Measurement Temporarily not Available Measurement Repetition Rate not Compatible with Current Measurements UE not Capable to Implement Measurement Miscellaneous Causes: Control Processing Overload HW Failure

8.3.22.4
-

Abnormal Conditions

3GPP

Release 11

237

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.23 UE Measurement Reporting [TDD]

8.3.23.1 General
This procedure is used by the SRNC to report the results of the successfully initiated measurements requested by the DRNC with the UE Measurement Initiation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context. The SRNC may initiate the UE Measurement Reporting procedure at any time after establishing a Radio Link.

8.3.23.2

Successful Operation
SRNC DRNC

UE MEASUREMENT REPORT

Figure 26H: UE Measurement Reporting procedure, Successful Operation If the requested measurement reporting criteria was met in the UE and reported to the SRNC, the SRNC shall initiate the UE Measurement Reporting procedure. The Measurement ID IE shall be set to the Measurement ID provided by the DRNC when initiating the measurement with the UE Measurement Initiation procedure. If Primary CCPCH RSCP is being reported: If the Primary CCPCH RSCP Delta IE is included, the DRNC shall assume that the reported value for Primary CCPCH RSCP is in the negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP Delta IE. If the Primary CCPCH RSCP Delta IE is not included the DRNC shall assume that the reported value is in the non negative range as per TS 25.123 [24], and the value is equal to the Primary CCPCH RSCP IE

If the achieved measurement accuracy does not fulfil the given accuracy requirement specified in TS 25.123 [24], the Measurement not available shall be reported in the UE Measurement Value Information IE in the UE MEASUREMENT REPORT message, otherwise the SRNC shall include the UE Measurement Value IE within the UE Measurement Value Information IE.

8.3.23.3
-

Abnormal Conditions

8.3.24 UE Measurement Termination [TDD]

8.3.24.1 General
This procedure is used by the DRNC to terminate a measurement previously requested by the UE Measurement Initiation procedure. This procedure shall use the signalling bearer connection for the relevant UE Context. The UE Measurement Termination procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

3GPP

Release 11

238

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.24.2

Successful Operation
SRNC
UE MEASUREMENT TERMINATION REQUEST

DRNC

Figure 26I: UE Measurement Termination procedure, Successful Operation This procedure is initiated with a UE MEASUREMENT TERMINATION REQUEST message, sent from the DRNC to the SRNC. Upon receipt, the SRNC shall terminate forwarding of UE measurements corresponding to the received Measurement ID IE.

8.3.24.3
-

Abnormal Conditions

8.3.25 UE Measurement Failure [TDD]

8.3.25.1 General
This procedure is used by the SRNC to notify the DRNC that a measurement previously requested by the UE Measurement Initiation procedure can no longer be reported. This procedure shall use the signalling bearer connection for the relevant UE Context. The SRNC may initiate the UE Measurement Failure procedure at any time after establishing a Radio Link.

8.3.25.2

Successful Operation
SRNC DRNC

UE MEASUREMENT FAILURE INDICATION

Figure 26J: UE Measurement Failure procedure, Successful Operation This procedure is initiated with a UE MEASUREMENT FAILURE INDICATION message, sent from the SRNC to the DRNC, to inform the DRNC that a previously requested UE measurement can no longer be reported. The SRNC has locally terminated the forwarding of the indicated measurement. The SRNC shall include in the UE MEASUREMENT FAILURE INDICATION message the reason for the failure in the Cause IE. Typical cause values are: Miscellaneous Causes: Control Processing Overload HW Failure O&M Intervention

8.3.25.3
-

Abnormal Conditions

3GPP

Release 11

239

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.26 Iur Invoke Trace

8.3.26.1 General
The purpose of the Iur Invoke Trace procedure is to inform the DRNC that it should begin a Trace Session for a given UE Context according to the Trace Parameters indicated by the SRNC. This procedure is used for Trace Parameter Propagation in the Signalling Based Activation mechanism as defined in TS 32.421 [48] and TS 32.422 [49]. This procedure shall use the signalling bearer mode specified below.

8.3.26.2

Successful Operation
SRNC Layer DRNC Layer

IUR INVOKE TRACE

Figure 26K: Iur Invoke Trace procedure, Successful Operation The Iur Invoke Trace procedure is invoked by the SRNC by sending an IUR INVOKE TRACE message to the DRNC. When the concerned UE is utilising one or more radio links in the DRNC the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the D-RNTI IE shall be included in the message to identify the UE Context in the DRNC. Upon receiving the IUR INVOKE TRACE message, the DRNC should begin a Trace Recording Session according to the parameters indicated in the IUR INVOKE TRACE message. If the List Of Interfaces To Trace IE is included in the IUR INVOKE TRACE message, the DRNC shall trace, for the concerned UE Context, the interfaces indicated by the List Of Interfaces To Trace IE. Otherwise, the DRNC shall trace, for the concerned UE Context, the Iur and Iub interfaces. The values of the UE Identity IE, Trace Reference IE and Trace Recording Session Reference IE are used to tag the Trace Record to allow simpler construction of the total record by the entity which combines Trace Records. If the DRNC does not support the requested value Minimum or Medium of the Trace Depth IE, the DRNC should begin a Trace Recording Session with maximum Trace Depth. The DRNC may not start a Trace Recording Session if there are insufficient resources available within the DRNC. If the MDT Configuration IE is included and the MDT Activation IE is set to MDT and Trace then the DRNC shall, if supported, initiate the requested trace function and MDT function as described in TS 32.422 [49]. If the MDT Configuration IE is included and the MDT Activation IE is set to MDT Only then the DRNC shall, if supported, initiate the requested MDT function as described in TS 32.422 [49] and shall ignore the List of Interfaces to Trace IE and the Trace Depth IE. If Trace Collection Entity IP Address IE is included and if the MDT Configuration IE is also included then the DRNC shall, if supported, store the Trace Collection Entity IP address and use it when transferring Trace records, otherwise if MDT Configuration IE is not included, the DRNC may use the Trace Collection Entity IP address when transferring trace records.

8.3.26.3

Abnormal Conditions

If the MDT Configuration IE is included in the IUR INVOKE TRACE message and the Trace Collection Entity IP Address IE is not included, the DRNC shall ignore the MDT Configuration.

3GPP

Release 11

240

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.27 Iur Deactivate Trace

8.3.27.1 General
The purpose of the Iur Deactivate Trace procedure is to inform the DRNC that it should stop a Trace Session for the concerned UE Context and the indicated Trace Reference. This procedure is used for the Signalling Based Deactivation mechanism as defined in TS 32.421 [48] and TS 32.422 [49]. This procedure shall use the signalling bearer mode specified below.

8.3.27.2

Successful Operation
SRNC Layer DRNC Layer

IUR DEACTIVATE TRACE

Figure 26L: Iur Invoke Trace procedure, Successful Operation The Iur Deactivate Trace procedure is invoked by the SRNC by sending an IUR DEACTIVATE TRACE message to the DRNC. When the concerned UE is utilising one or more radio links in the DRNC the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If on the other hand, the UE is not utilising any radio link the message shall be sent using the connectionless service of the signalling bearer and the D-RNTI IE shall be included in the message to identify the UE Context in the DRNC. Upon receiving the IUR DEACTIVATE TRACE message, the DRNC shall stop for the concerned UE Context any ongoing Trace Recording Session for the Trace Session identified by the Trace Reference IE.

8.3.27.3
-

Abnormal Conditions

8.3.28 Enhanced Relocation

8.3.28.1 General
This procedure is used for relocation of SRNS in case the SRNC and DRNC connect to same CN node. The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure in case the relevant UE Context does not exist for the UE. This procedure shall use the signalling bearer connection for the relevant UE Context in the UE Context exists. The Enhanced Relocation procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.28.2

Successful Operation
SRNC Layer DRNC Layer

ENHANCED RELOCATION REQUEST ENHANCED RELOCATION RESPONSE

Figure 26M: Enhanced Relocation procedure: Successful Operation The SRNC initiates the procedure by sending an ENHANCED RELOCATION REQUEST message. When the SRNC sends the ENHANCED RELOCATION REQUEST message, it shall start the timer TRELOCprep. The ENHANCED RELOCATION REQUEST message shall contain the Cause IE with an appropriate value e.g.: Time critical

3GPP

Release 11

241

3GPP TS 25.423 V11.2.0 (2012-06)

Relocation, Resource optimisation relocation, Relocation desirable for radio reasons , Directed Retry, Reduce Load in Serving Cell, No Iu CS UP relocation. If the ENHANCED RELOCATION REQUEST message includes SRNC-ID, the DRNC shall create a UE Context for this UE, allocate a D-RNTI for the UE Context.

8.3.28.3

Unsuccessful Operation
SRNC Layer DRNC Layer

ENHANCED RELOCATION REQUEST ENHANCED RELOCATION FAILURE

Figure 26N: Enhanced Relocation procedure: Unsuccessful Operation If the DRNC is not able to accept any of the RABs or a failure occurs during the procedure, the DRNC shall send the ENHANCED RELOCATION FAILURE message to the SRNC. The message shall contain the Cause IE with an appropriate value. Interactions with Enhanced Relocation Cancel procedure: If there is no response from the DRNC to the ENHANCED RELOCATION REQUEST message before timer TRELOCprep expires in the DRNC, the SRNC should cancel the Enhanced Relocation procedure towards the DRNC by initiating the Enhanced Relocation Cancel procedure with the appropriate value for the Cause IE, e.g. TRELOCprep expiry. The SRNC shall ignore any ENHANCED RELOCATION RESPONSE or ENHANCED RELOCATION FAILURE message received after the initiation of the Enhanced Relocation Cancel procedure and remove any reference and release any resources related to the concerned UE Context.

8.3.28.4
-

Abnormal Conditions

8.3.29 Enhanced Relocation Cancel

8.3.29.1 General
This procedure is used to cancel an ongoing enhanced relocation or an already prepared relocation. This procedure shall use the signalling bearer connection for the relevant UE Context.

8.3.29.2

Successful Operation
SRNC Layer DRNC Layer

ENHANCED RELOCATION CANCEL

Figure 26O: Enhanced Relocation Cancel procedure: Successful Operation The SRNC initiates the procedure by sending the ENHANCED RELOCATION CANCEL message to the DRNC. The SRNC shall indicate the reason for cancelling the relocation by means of an appropriate cause value. Typical cause values are TRELOCprepExpiry, Relocation Cancelled, Traffic Load In The Target Cell Higher Than In The Source Cell. At the reception of the ENHANCED RELOCATION CANCEL message, the DRNC shall remove any reference to, and release any resources previously reserved to the concerned UE context.

3GPP

Release 11

242

3GPP TS 25.423 V11.2.0 (2012-06)

8.3.29.3
Not applicable.

Unsuccessful Operation Abnormal Conditions

8.3.29.4
-

8.3.30 Enhanced Relocation Signalling Transfer

8.3.30.1 General
The procedure is used by the SRNC to transfer DL L3 information to DRNC during enhanced relocation. This procedure shall use the signalling bearer connection for the relevant UE Context.

8.3.30.2

Successful Operation
SRNC Layer DRNC Layer
ENHANCED RELOCATION SIGNALLING TRANSFER

Figure 26P: Enhanced Relocation Signalling Transfer procedure, Successful Operation The procedure consists of the ENHANCED RELOCATION SIGNALLING TRANSFER message sent by the SRNC to the DRNC. The ENHANCED RELOCATION SIGNALLING TRANSFER message contains the L3 Information and after the receipt of the message, the DRNC shall send the L3 Information on the DCCH.

8.3.30.3
-

Abnormal Conditions

8.3.31 Enhanced Relocation Release

8.3.31.1 General
The procedure is used by the DRNC to signal to the SRNC that resource for CN domain is released due to failure of the enhanced relocation. This procedure shall use the signalling bearer connection for the relevant UE Context.

8.3.31.2

Successful Operation
SRNC Layer
ENHANCED RELOCATION RELEASE

DRNC Layer

Figure 26Q: Enhanced Relocation Signalling Transfer procedure, Successful Operation The procedure consists of the ENHANCED RELOCATION RELEASE message sent by the DRNC to the SRNC.

3GPP

Release 11

243

3GPP TS 25.423 V11.2.0 (2012-06)

Upon reception of the ENHANCED RELOCATION RELEASE message, the SRNC shall release related resources associated to indicated CN domain(s) by the Released CN Domain IE in the message for the UE context.

8.3.31.3
-

Abnormal Conditions

8.3.32 Secondary UL Frequency Reporting [FDD]

8.3.32.1 General
The purpose of this procedure is to inform the DRNS about the activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation. This procedure shall use the signalling bearer connection for the relevant UE Context.

8.3.32.2

Successful Operation
SRNC DRNC

SECONDARY UL FREQUENCY REPORT

Figure 26R: Secondary UL Frequency Reporting procedure The Secondary UL Frequency Reporting procedure is initiated by sending the SECONDARY UL FREQUENCY REPORT message from the SRNC to the DRNC. The Activation Information IE defines the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation. - If the value of Uu Activation State IE is Activated: the DRNS shall if supported use this information for resource allocation operation of the secondary E-DCH radio link(s), F-DPCH transmission and DPCCH detection. - If the value of Uu Activation State IE is De-Activated: the DRNS shall if supported use this information for release of the related resources for the secondary E-DCH radio link(s), cease of F-DPCH transmission and DPCCH detection.

8.3.32.3
-

Abnormal Conditions

8.3.33 Secondary UL Frequency Update [FDD]

8.3.33.1 General
The purpose of this procedure is to inform the SRNC about updates to activation state of the secondary UL frequency of the UE in Dual Cell E-DCH operation . This procedure shall use the signalling bearer connection for the relevant UE context.

8.3.33.2

Successful Operation
SRNC DRNC
SECONDARY UL FREQUENCY UPDATE INDICATION

Figure 26S: Secondary UL Frequency Update procedure

3GPP

Release 11

244

3GPP TS 25.423 V11.2.0 (2012-06)

The Secondary UL Frequency Update procedure is initiated by the DRNS by sending the SECONDARY UL FREQUENCY UPDATE INDICATION message to the SRNC. If the DRNS needs to update the local activation state of the Secondary uplink frequency of the UE in Dual Cell E-DCH operation, the DRNS shall send SECONDARY UL FREQUENCY UPDATE INDICATION message and include the Activation Information IE.

8.3.33.3
-

Abnormal Conditions

8.4 Common Transport Channel Procedures

8.4.1 Common Transport Channel Resources Initialisation
8.4.1.1 General
The Common Transport Channel Resources Initialisation procedure is used by the SRNC for the initialisation of the Common Transport Channel user plane towards the DRNC and/or for the initialisation of the Common Transport Channel resources in the DRNC to be used by a UE. This procedure shall use the connectionless mode of the signalling bearer.

8.4.1.2

Successful Operation
SRNC Layer DRNC Layer

COMMON TRANSPORT CHANNEL RESOURCES REQUEST COMMON TRANSPORT CHANNEL RESOURCES RESPONSE

Figure 27: Common Transport Channel Resources Initialisation procedure, Successful Operation The SRNC initiates the procedure by sending the message COMMON TRANSPORT CHANNEL RESOURCES REQUEST message to the DRNC. If the value of the Transport Bearer Request Indicator IE is set to Bearer Requested, the DRNC shall store the received Transport Bearer ID IE. The DRNC may use the Transport Layer Address and Binding ID IEs included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message received from the SRNC when establishing a transport bearer for the common transport channel. In addition, the DRNC shall include its own Binding ID IE and Transport Layer Address IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the TNL QoS IE is included and if ALCAP is not used, the TNL QoS IE may be used by the DRNC to determine the transport bearer characteristics to apply in the uplink between the DRNS and the SRNC for the related common transport channels. If the value of the Transport Bearer Request Indicator IE is set to Bearer not Requested, the DRNC shall use the transport bearer indicated by the Transport Bearer ID IE. If the C-ID IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall allocate a C-RNTI for the indicated cell and include the C-RNTI IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the C-ID IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall include the FACH Info for UE Selected S-CCPCH IE valid for the cell indicated by the C-ID IE and the corresponding C-ID IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the C-ID IE is not included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall include the FACH Info for UE Selected S-CCPCH IE valid for the cell where the UE is located and the corresponding

3GPP

Release 11

245

3GPP TS 25.423 V11.2.0 (2012-06)

C-ID IE. The DRNC shall include the FACH Scheduling Priority IE and FACH Initial Window Size IE in the FACH Flow Control Information IE of the FACH Info for UE Selected S-CCPCH IE for each priority class that the DRNC has determined shall be used. The DRNC may include several MAC-c/sh SDU Length IEs for each priority class. If the DRNS has any RACH and/or FACH [FDD and/or HS-DSCH] [1.28Mcps TDD and/or HS-DSCH] resources previously allocated for the UE in another cell than the cell in which resources are currently being allocated, the DRNS shall release the previously allocated RACH and/or FACH resources [FDD and/or HS-DSCH] [1.28Mcps TDD and/or HS-DSCH]. If the DRNS has successfully reserved the required resources, the DRNC shall respond to the SRNC with the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the Permanent NAS UE Identity IE is present in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNS shall store the information for the considered UE Context for the lifetime of the UE Context. If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes a C-ID IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is available in the DRNC for the considered UE Context, the DRNC shall use this information to determine whether it can reserve resources on a common transport channel in this cell or not. If the MBMS Bearer Service List IE is included in the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message, the DRNC shall, if supported, perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If an MBMS session for some MBMS bearer services contained in the UE Link is ongoing in the cell identified by the C-ID IE, the DRNC shall include in the Active MBMS Bearer Service List IE the Transmission Mode IE for each of these active MBMS bearer services in the COMMON TRANPORT CHANNEL RESOURCES RESPONSE message. [FDD If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an Enhanced FACH Support Indicator IE, the DRNC may include the Enhanced FACH Information Response IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If a HS-DSCH RNTI was not previously allocated to the UE or a new HS-DSCH RNTI is allocated to the UE, the DRNC shall include the HS-DSCH-RNTI IE in the Enhanced FACH Information Response IE. And if Enhanced PCH operation is activated in the cell indicated by the CID IE, the DRNC shall include the Priority Queue Information for Enhanced PCH IE in the Enhanced FACH Information Response IE.] [1.28Mcps TDD If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an Enhanced FACH Support Indicator IE, the DRNC may include the Enhanced FACH Information Response IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If a HS-DSCH RNTI was not previously allocated to the UE or a new HS-DSCH RNTI is allocated to the UE, the DRNC shall include the HS-DSCH-RNTI IE in the Enhanced FACH Information Response IE. And if Enhanced PCH operation is activated in the cell indicated by the C-ID IE, the DRNC shall include the Priority Queue Information for Enhanced PCH IE in the Enhanced FACH Information Response IE.] [FDD If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an Common E-DCH Support Indicator IE, the DRNC may include the Common E-DCH MAC-d Flow Specific Information IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the E-DCH MAC-d Flow Multiplexing List for a Common E-DCH MAC-d Flow is configured in DRNC, the DRNC shall include the E-DCH MAC-d Flow Multiplexing List IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message. If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes the C-ID IE and the Common EDCH Support Indicator IE, the DRNC may include the E-RNTI IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.] [1.28Mcps TDD If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes a Enhanced FACH Support Indicator IE, the DRNC may include the Common E-DCH MAC-d Flow Specific Information LCR IE in the COMMON TRANSPORT CHANNEL RESOURCES RESPONSE message.] If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message includes an HS-DSCH physical layer category IE, the DRNC may store the information for the considered UE Context for the lifetime of the UE Context. [FDD If the COMMON TRANSPORT CHANNEL RESOURES REQUEST message includes an UE with enhanced HS-SCCH support indicator IE, the DRNC may store the information for the considered UE Context for the lifetime of the UE context.]

3GPP

Release 11

246

3GPP TS 25.423 V11.2.0 (2012-06)

8.4.1.3

Unsuccessful Operation
SRNC Layer DRNC Layer

COMMON TRANSPORT CHANNEL RESOURCES REQUEST COMMON TRANSPORT CHANNEL RESOURCES FAILURE

Figure 28: Common Transport Channel Resources Initialisation procedure, Unsuccessful Operation If the Transport Bearer Request Indicator IE is set to Bearer Requested and the DRNC is not able to provide a Transport Bearer, the DRNC shall reject the procedure and respond to the SRNC with the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message, including the reason for the failure in the Cause IE. If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains a C-ID IE corresponding to a cell reserved for operator use and the Permanent NAS UE Identity is not available for the considered UE Context, the DRNC shall reject the procedure and send the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message, including the reason for the failure in the Cause IE. Typical cause values are: Radio Network Layer Causes: Common Transport Channel Type not Supported; Cell reserved for operator use.

Transport Layer Causes: Transport Resource Unavailable.

8.4.1.4

Abnormal Conditions

If the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport channel intended to be established, the DRNC shall reject the procedure using the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message. If ALCAP is not used, if the COMMON TRANSPORT CHANNEL RESOURCES REQUEST message contains the Transport Bearer Request Indicator IE set to Bearer Requested but does not contain the Transport Layer Address IE and the Binding ID IE, the DRNC shall reject the procedure using the COMMON TRANSPORT CHANNEL RESOURCES FAILURE message.

8.4.2 Common Transport Channel Resources Release

8.4.2.1 General
This procedure is used by the SRNC to request release of Common Transport Channel Resources for a given UE in the DRNS. The SRNC uses this procedure either to release the UE Context from the DRNC (and thus both the D-RNTI and the C-RNTI) or to release only the C-RNTI. This procedure shall use the connectionless mode of the signalling bearer.

3GPP

Release 11

247

3GPP TS 25.423 V11.2.0 (2012-06)

8.4.2.2

Successful Operation SRNC Layer

COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST

DRNC Layer

Figure 29: Common Transport Channel Resources Release procedure, Successful Operation The SRNC initiates the Common Transport Channel Resources Release procedure by sending the COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST message to the DRNC. Upon receipt of the message the DRNC shall release the UE Context identified by the D-RNTI and all its related RACH and/or FACH resources, unless the UE is using dedicated resources (DCH, [TDD USCH and/or DSCH]) in the DRNS in which case the DRNC shall release only the C-RNTI and all its related RACH and/or FACH [FDD and/or HS-DSCH] [1.28Mcps TDD and/or HS-DSCH] resources allocated for the UE.

8.4.2.3
-

Abnormal Conditions

8.5 Global Procedures

8.5.1 Error Indication
8.5.1.1 General
The Error Indication procedure is initiated by a node to report detected errors in a received message, provided they cannot be reported by an appropriate response message. This procedure shall use the signalling bearer mode specified below.

8.5.1.2

Successful Operation
RNC1 Layer
ERROR INDICATION

RNC2 Layer

Figure 30: Error Indication procedure, Successful Operation When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. This message shall use the same mode of the signalling bearer and the same signalling bearer connection (if connection oriented) as the message that triggers the procedure. When the ERROR INDICATION message is sent from a DRNC to an SRNC using connectionless mode of the signalling bearer, the S-RNTI IE shall be included in the message if the UE Context addressed by the D-RNTI IE which was received in the message triggering the Error Indication procedure exists. When the ERROR INDICATION message is sent from an SRNC to a DRNC using connectionless mode of the signalling bearer, the D-RNTI IE shall be included in the message if available. When a message using connectionless mode of the signalling bearer is received in the DRNC and there is no UE Context in the DRNC as indicated by the D-RNTI IE, the DRNC shall include the D-RNTI from the received message in the D-RNTI IE and set the Cause IE to Unknown RNTI in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.

3GPP

Release 11

248

3GPP TS 25.423 V11.2.0 (2012-06)

When a message using connectionless mode of the signalling bearer is received in the SRNC and there is no UE in the SRNC as indicated by the S-RNTI IE, the SRNC shall include the S-RNTI from the received message in the S-RNTI IE and set the Cause IE to Unknown RNTI in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure. The ERROR INDICATION message shall include either the Cause IE, or the Criticality Diagnostics IE, or both the Cause IE and the Criticality Diagnostics IE to indicate the reason for the error indication. Typical cause values for the ERROR INDICATION message are: Protocol Causes: Transfer Syntax Error Abstract Syntax Error (Reject) Abstract Syntax Error (Ignore and Notify) Message not Compatible with Receiver State Unspecified

8.5.1.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the error indication procedure as specified in section 8.5.1.2.

8.5.1.3
-

Abnormal Conditions

8.5.2 Common Measurement Initiation

8.5.2.1 General
This procedure is used by an RNC to request the initiation of measurements of common resources to another RNC. The requesting RNC is referred to as RNC1 and the RNC to which the request is sent is referred to as RNC2. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.2.2

Successful Operation
RNC1 RNC2

COMMON MEASUREMENT INITIATION REQUEST COMMON MEASUREMENT INITIATION RESPONSE

Figure 30A: Common Measurement Initiation procedure, Successful Operation The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC1 to the RNC2. Upon receipt, the RNC2 shall initiate the requested measurement according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications. [TDD If the [3.84 Mcps TDD and 7.68 Mcps TDD Time Slot IE] [1.28 Mcps Time Slot LCR IE] is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested time slot individually.] Common measurement type

3GPP

Release 11

249

3GPP TS 25.423 V11.2.0 (2012-06)

If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then: The RNC2 shall initiate the SFN-SFN Observed Time Difference measurements between the reference cell identified by the Reference Cell Identifier IE and the neighbouring cells identified by the UTRAN Cell Identifier IE (UC-ID) in the Neighbouring Cell Measurement Information IE. [3.84 Mcps TDD The RNC2 shall perform the measurement using the time slot specified in the Time Slot IE in the Neighbouring TDD Cell Measurement Information IE and using the midamble shift and burst type specified in the Midamble Shift And Burst Type IE in the Neighbouring TDD Cell Measurement Information IE. If Time Slot IE and Midamble Shift And Burst Type IE are not available in the Neighbouring TDD Cell Measurement Information IE, the RNC2 may use any appropriate time slots, midamble shifts and burst types to make the measurement.] [7.68 Mcps TDD The RNC2 shall perform the measurement using the time slot specified in the Time Slot IE in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE and using the midamble shift and burst type specified in the Midamble Shift And Burst Type 7.68 Mcps IE in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE. If Time Slot IE and Midamble Shift And Burst Type 7.68 Mcps IE are not available in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE, the RNC2 may use any appropriate time slots, midamble shifts and burst types to make the measurement.]

If the Common Measurement Type IE is set to load, the RNC2 shall initiate measurements of uplink and downlink load on the measured object identified by the Reference Cell Identifier IE. If either uplink or downlink load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements. If the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE Positioning, UTRAN GANSS Timing of Cell Frames for UE Positioning, transmitted carrier power, received total wide band power, or UL timeslot ISCP the RNC2 shall initiate measurements on the measured object identified by the Reference Cell Identifier IE. If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning, then the RNC2 shall initiate the UTRAN GANSS Timing of Cell Frames measurements using the GNSS system time identified by GANSS Time ID IE included in the COMMON MEASUREMENT INITIATION REQUEST message. If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning and the GANSS Time ID IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall assume that the corresponding GANSS time is Galileo system time.

If the Common Measurement Type IE is set to RT load, the RNC2 shall initiate measurements of uplink and downlink estimated share of RT (Real Time) traffic of the load of the measured object. If either uplink or downlink RT load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements. If the Common Measurement Type IE is set to NRT load Information, the RNC2 shall initiate measurements of uplink and downlink NRT (Non Real Time) load situation on the measured object. If either uplink or downlink NRT load satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink measurements. Report characteristics The Report Characteristics IE indicates how the reporting of the measurement shall be performed. See also Annex B. If the Report Characteristics IE is set to On Demand and if the SFN IE is not provided, the RNC2 shall report the result of the requested measurement immediately in the COMMON MEASUREMENT INITIATION RESPONSE message. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to SFNSFN Observed Time Difference , then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE. If the Report Characteristics IE is set to Periodic and if the SFN IE is not provided, the RNC2 shall immediately and periodically initiate a Common Measurement Reporting procedure for this measurement, with a frequency as specified by the Report Periodicity IE. If the SFN IE is provided, the RNC2 shall initiate a Common Measurement Reporting procedure for this measurement at the SFN indicated in the SFN IE, and shall repeat this initiation periodically thereafter with a frequency as specified by the Report Periodicity IE. The provided measurement value shall be the one

3GPP

Release 11

250

3GPP TS 25.423 V11.2.0 (2012-06)

reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to SFN-SFN Observed Time Difference , then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE. If the Report Characteristics IE is set to Event A, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity rises above the requested threshold, as specified by the Measurement Threshold IE, and then stays above the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the RNC2 shall use the value zero for the hysteresis time. If the Report Characteristics IE is set to Event B, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls below the requested threshold, as specified by the Measurement Threshold IE, and then stays below the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the RNC2 shall use the value zero for the hysteresis time. If the Report Characteristics IE is set to Event C, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity rises more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this rise occurs within the requested rising time specified by the Measurement Change Time IE. After reporting this type of event, the RNC2 shall not initiate the next C event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE. If the Report Characteristics IE is set to Event D, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this fall occurs within the requested falling time specified by the Measurement Change Time IE. After reporting this type of event,, the RNC2 shall not initiate the next D event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE. If the Report Characteristics IE is set to Event E, the RNC2shall initiate the Common Measurement Reporting procedure when the measured entity rises above the Measurement Threshold 1 IE and stays above the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the RNC2 shall initiate the Common Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity falls below the Measurement Threshold 2 IE and stays below the threshold for the Measurement Hysteresis Time IE, the RNC2 shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the RNC2 shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the RNC2 shall use the value zero as hysteresis times for both Report A and Report B. If the Report Characteristics IE is set to Event F, the RNC2 shall initiate the Common Measurement Reporting procedure when the measured entity falls below the Measurement Threshold 1 IE and stays below the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the RNC2 shall initiate the Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity rises above the Measurement Threshold 2 IE and stays above the threshold for the Measurement Hysteresis Time IE, the RNC2 shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the RNC2 shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the RNC2 shall use the value zero as hysteresis times for both Report A and Report B. [1.28Mcps TDD-If the Report Characteristics IE is set to Event H (figure B.7), the Measurement Reporting procedure (Report A) is initiated when the measurement value of measured entity rises above the Measurement Threshold 1 and stays above the threshold for the Measurement Hysteresis Time (T1 in figure B.7).] The measurement value of measured entity in Report A substitutes the Measurement Base value for the consequent measurement reporting. When the Report A conditions has been met and the measurement value of measured entity rises above or falls below the Measurement Base Value by Measurement Fluctuation Range (H1 in figure B.7), and stays there for the Measurement Hysteresis Time (Th in figure B.7) counting from the beginning of every Report Periodicity, the Measurement Reporting procedure (Report B or Report C) is initiated. The the measurement value of measured entity in (Report B or Report C) substitutes the Measurement Base value for the consequent measurement reporting. When the Report A conditions have been met and the measurement value of measured entity falls below the Measurement Threshold 2 and stays there for the Measurement Hysteresis Time (Th in figure B.7), the Measurement Reporting procedure (Report D) is initiated and the reporting is terminated.]

3GPP

Release 11

251

3GPP TS 25.423 V11.2.0 (2012-06)

If the Report Characteristics IE is set to On Modification and if the SFN IE is not provided, the RNC2 shall report the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the first measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE. Following the first measurement report, the RNC2 shall initiate the Common Measurement Reporting procedure in accordance to the following conditions: 1. If the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE Positioning: - If the TUTRAN-GPS Change Limit IE is included in the TUTRAN-GPS Measurement Threshold Information IE, the RNC2 shall calculate the change of TUTRAN-GPS value (Fn) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the TUTRAN-GPS Change Limit IE. The change of TUTRAN-GPS value (Fn) is calculated according to the following: Fn=0 for n=0 Fn = (Mn Mn-1) mod 37158912000000 ((SFNn SFNn-1) mod 4096) *10*3.84*10^3*16 + Fn-1 for n>0

Fn is the change of the TUTRAN-GPS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn. Mn-1 is the previous measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn-1. M1 is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered. M0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered. - If the Predicted TUTRAN-GPS Deviation Limit IE is included in the TUTRAN-GPS Measurement Threshold Information IE, the RNC2 shall update the Pn and F each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when Fn rises above the threshold indicated by the Predicted TUTRAN-GPS Deviation Limit IE. The Pn and Fn are calculated according to the following: Pn=b for n=0 Pn = ((a/16) * ((SFNn SFNn-1) mod 4096) /100 +((SFNn SFNn-1) mod 4096)*10*3.84*10^3*16 + Pn-1 ) mod 37158912000000 for n>0 Fn = min((Mn Pn) mod 37158912000000, (Pn Mn) mod 37158912000000) for n>0

Pn is the predicted TUTRAN-GPS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. A is the last reported TUTRAN-GPS Drift Rate value. B is the last reported TUTRAN-GPS value. Fn is the deviation of the last measurement result from the predicted TUTRAN-GPS value (Pn ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn . M1 is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.

3GPP

Release 11

252

3GPP TS 25.423 V11.2.0 (2012-06)

The TUTRAN-GPS Drift Rate is determined by the RNS2 in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])). 2. If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference: - If the SFN-SFN Change Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the RNC2 shall calculate the change of SFN-SFN value (Fn) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the SFN-SFN Change Limit IE. The change of the SFN-SFN value is calculated according to the following: Fn=0 for n=0 [FDD Fn = (Mn a) mod 614400 for n>0] [TDD Fn = (Mn a) mod 40960 for n>0]

Fn is the change of the SFN-SFN value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. A is the last reported SFN-SFN. Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFNn. M1 is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after the first Common Measurement Reporting at initiation or after the last event was triggered. - If the Predicted SFN-SFN Deviation Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the RNC2 shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]), update the Pn and Fn. The RNC2 shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when Fn rises above the threshold indicated by the Predicted SFN-SFN Deviation Limit IE. The Pn and Fn are calculated according to the following: Pn=b for n=0 [FDD Pn = ((a/16) * ((SFNn SFNn-1) mod 4096)/100 + Pn-1 ) mod 614400 [FDD Fn = min((Mn Pn) mod 614400, (Pn Mn) mod 614400) for n>0] [TDD Pn =((a/16) * (15*(SFNn SFNn-1)mod 4096 + (TSn TSn-1))/1500 + Pn-1 ) mod 40960 for n>0] [TDD Fn = min((Mn Pn) mod 40960, (Pn Mn) mod 40960) for n>0] for n>0]

Pn is the predicted SFN-SFN value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. A is the last reported SFN-SFN Drift Rate value. B is the last reported SFN-SFN value. Fn is the deviation of the last measurement result from the predicted SFN-SFN value (Pn ) when n measurements have been received after first Common Measurement Reporting at initiation or after the last event was triggered. Mn is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at the [TDD the Time Slot TSn of] the Frame SFNn. M1 is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered. The SFN-SFN Drift Rate is determined by the RNS2 in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).

3GPP

Release 11 3.

253

3GPP TS 25.423 V11.2.0 (2012-06)

If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning: - If the TUTRAN-GANSS Change Limit IE is included in the TUTRAN-GANSS Measurement Threshold Information IE, the RNC2 shall calculate the change of TUTRAN-GANSS value (Fn) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of Fn rises above the threshold indicated by the TUTRAN-GANSS Change Limit IE. The change of TUTRAN-GANSS value (Fn) is calculated according to the following: Fn=0 for n=0 Fn = (GAMn GAMn-1) mod 5308416000000 ((SFNn SFNn-1) mod 4096) *10*3.84*10^3*16 + Fn-1 for n>0 Fn is the change of the TUTRAN-GANSS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. GAMn is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn. GAMn-1 is the previous GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn-1. GAM1 is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered. GAM0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered. GANSS measurement model is the timing between cell j and GANSS Time Of Day. TUE-GANSSj is defined as the time of occurrence of a specified UTRAN event according to GANSS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for TUE-GANSSj shall be the antenna connector of the UE. - If the Predicted TUTRAN-GANSS Deviation Limit IE is included in the TUTRAN-GANSS Measurement Threshold Information IE, the RNC2 shall update the Pn and F each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC2 shall initiate the Common Measurement Reporting procedure and set n equal to zero when Fn rises above the threshold indicated by the Predicted TUTRAN-GANSS Deviation Limit IE. The Pn and Fn are calculated according to the following: Pn=b for n=0 Pn = ((a/16) * ((SFNn SFNn-1) mod 4096)/100 +((SFNn SFNn-1) mod 4096)*10*3.84*10^3*16 + Pn-1 ) mod 5308416000000 for n>0 Fn = min((GAMn Pn) mod 5308416000000, (Pn GAMn) mod 5308416000000) for n>0

Pn is the predicted TUTRAN-GANSS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. A is the last reported TUTRAN-GANSS Drift Rate value. B is the last reported TUTRAN-GANSS value. Fn is the deviation of the last measurement result from the predicted TUTRAN-GANSS value (Pn ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered. GAMn is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn. GAM1 is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.

3GPP

Release 11

254

3GPP TS 25.423 V11.2.0 (2012-06)

The TUTRAN-GANSSS Drift Rate is determined by the RNS2 in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])). If the Report Characteristics IE is not set to On Demand, the RNC2 is required to perform reporting for a common measurement object, in accordance with the conditions provided in the COMMON MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no common measurement object(s) for which a measurement is defined exists any more, the RNC2 shall terminate the measurement locally without reporting this to RNC1. If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the RNC2 shall initiate a Measurement Reporting procedure immediately, and then continue with the measurements as specified in the COMMON MEASUREMENT INITIATION REQUEST message. Common measurement accuracy If the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE Positioning, then the RNC2 shall use the TUTRAN-GPS Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following:. If the TUTRAN-GPS Measurement Accuracy Class IE indicates Class A, then the concerned RNC2 shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C. If the TUTRAN-GPS Measurement Accuracy Class IE indicates the Class B, then the concerned RNC2 shall perform the measurements with the highest supported accuracy within the accuracy classes B and C. If the TUTRAN-GPS Measurement Accuracy Class IE indicates Class C, then the concerned RNC2 shall perform the measurements with the highest supported accuracy according to class C.

If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then the concerned RNC2 shall initiate the SFN-SFN observed Time Difference measurements between the reference cell identified by UC-ID IE and the neighbouring cells identified by their UC-ID. The Report Characteristics IE applies to each of these measurements. If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE positioning, then the RNC2 shall use the TUTRAN-GANSS Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following: If the TUTRAN-GANSS Measurement Accuracy Class IE indicates Class A, then the concerned RNC2 shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C. If the TUTRAN-GANSS Measurement Accuracy Class IE indicates the Class B, then the concerned RNC2 shall perform the measurements with the highest supported accuracy within the accuracy classes B and C. If the TUTRAN-GANSS Measurement Accuracy Class IE indicates Class C, then the concerned RNC2 shall perform the measurements with the highest supported accuracy according to class C.

Higher layer filtering The Measurement Filter Coefficient IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting. The averaging shall be performed according to the following formula.

Fn = (1 a ) Fn 1 + 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 COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn). A = (k/2) -, where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering).

3GPP

Release 11

255

3GPP TS 25.423 V11.2.0 (2012-06)

In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received. Measurement Recovery Behavior: If the Measurement Recovery Behavior IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall, if Measurement Recovery Behavior is supported, include the Measurement Recovery Support Indicator IE in the COMMON MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.5.3.2. Response message If the RNC2 was able to initiate the measurement requested by RNC, it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the COMMON MEASUREMENT INITIATION REQUEST message. In the case in which the Report Characteristics IE is set to On Demand or On Modification: The COMMON MEASUREMENT INITIATION RESPONSE message shall include the Common Measurement Object Type IE containing the measurement result. It shall also include the Common Measurement Achieved Accuracy IE if the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE positioning or UTRAN GANSS Timing of Cell Frames for UE positioning. If the Common Measurement Type IE is not set to SFN-SFN Observed Time Difference and if the SFN Reporting Indicator IE is set to FN Reporting Required, then the RNC2 shall include the SFN IE in the COMMON MEASUREMENT INITIATION RESPONSE message,. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then the SFN Reporting Indicator IE is ignored. If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then the RNC2 shall report all the available measurements in the Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE, and the RNC2 shall report the neighbouring cells with no measurement result available in the Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE. For all available measurement results, the RNC2 shall include in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE, if available.

If the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE Positioning and the Report Characteristics IE is set to On Demand or On Modification, the RNC2 shall include in the TUTRAN-GPS Measurement Value Information IE the TUTRAN-GPS Quality IE and the TUTRAN-GPS Drift Rate Quality IE, if available. If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning and the Report Characteristics IE is set to On Demand or On Modification, the RNC2 shall include in the TUTRAN-GANSS Measurement Value Information IE, the TUTRAN-GANSS Quality IE and the TUTRAN-GANSS Drift Rate Quality IE, if available.

8.5.2.2.1

Successful Operation for Iur-g

The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC1 to the BSS2 or from the BSS1 to the RNC2/BSS2. Upon receipt, the RNC2 /BSS2 shall initiate the requested measurement according to the parameters given in the request. [1.28Mcps TDD-The procedure is also initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the TDD RNC1 to the BSS2 for multiple GERAN cells measurements by allocating unique Measurement ID for each GERAN cell. Upon receipt, the BSS2 shall initiate the requeted measurement according to the parameters given in the request.] Common measurement type on Iur-g If the Common Measurement Type IE is set to load, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2. If the Common Measurement Type IE is set to RT load, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2.

3GPP

Release 11

256

3GPP TS 25.423 V11.2.0 (2012-06)

If the Common Measurement Type IE is set to NRT load Information, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.2.2. Report characteristics on Iur-g The Report Characteristics IE indicates how the reporting of the measurement shall be performed. This IE is used as described in section 8.5.2.2. Response message for Iur-g If the RNC2/BSS2 was able to initiate the measurement requested by RNC1/BSS1 it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message sent. The message shall include the same Measurement ID that was used in the measurement request. Only in the case when the Report Characteristics IE is set to On Demand, the COMMON MEASUREMENT INITIATION RESPONSE message shall contain the measurement result. [1.28Mcps TDD- If the BSS2 was able to initiate the measurement requested by RNC1, it shall respond with one or more COMMON MEASUREMENT INITIATION RESPONSE messages sent. The message(s) should include the same Measurement ID that was used in the mesasurement request.

8.5.2.3

Unsuccessful Operation
RNC1 RNC2

COMMON MEASUREMENT INITIATION REQUEST COMMON MEASUREMENT INITIATION FAILURE

Figure 30B: Common Measurement Initiation procedure, Unsuccessful Operation If the requested measurement cannot be initiated, the RNC2 shall send a COMMON MEASUREMENT INITIATION FAILURE message. The message shall include the same Measurement ID IE that was used in the COMMON MEASUREMENT INITIATION REQUEST message and shall include the Cause IE set to an appropriate value. Typical cause values are as follows: Radio Network Layer Cause Measurement not supported for the object. Measurement Temporarily not Available

8.5.2.4

Abnormal Conditions

If the COMMON MEASUREMENT INITIATION REQUEST message contains the SFN-SFN Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the COMMON MEASUREMENT INITIATION REQUEST message contains the TUTRAN-GPS Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the COMMON MEASUREMENT INITIATION REQUEST message contains the TUTRAN-GANSS Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC2 shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the Common Measurement Type IE is set to UTRAN GPS Timing of Cell Frames for UE positioning, but the TUTRAN-GPS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON

3GPP

Release 11

257

3GPP TS 25.423 V11.2.0 (2012-06)

MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the Common Measurement Type IE is set to UTRAN GANSS Timing of Cell Frames for UE positioning, but the TUTRAN-GANSS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the Common Measurement Type received in the Common Measurement Type IE is not load, RT load or NRT load Information, and if the Common Measurement Type received in the Common Measurement Type IE is not defined in TS 25.215 [11] or TS 25.225 [14] to be measured on the Common Measurement Object Type indicated in the COMMON MEASUREMENT INITIATION REQUEST message the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message. If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, but the Neighbouring Cell Measurement Information IE is not received in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message. The allowed combinations of the Common Measurement Type and Report Characteristics Type are shown in the table below marked with X. For not allowed combinations, the RNC2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message. Table 5: Allowed Common Measurement Type and Report Characteristics Type Combinations
Common measurement type On Demand Received total wide X band power Transmitted Carrier X Power UL Timeslot ISCP X Load X UTRAN GPS X Timing of Cell Frames for UE Positioning SFN-SFN X Observed Time Difference RT load X NRT load X Information UpPTS interference X UTRAN GANSS X Timing of Cell Frames for UE Positioning X X X X X X X X X Report characteristics type Periodic Event A Event B Event C Event D Event E Event F Event-H X X X X X X X X X X X X X X X X X X X X X X On Modification

X X X X X X X X X X X X X X X X X X X X X X X

[TDD If the Common Measurement Type requires the Time Slot Information but the [3.84Mcps TDD and 7.68 Mcps TDD Time Slot IE] [1.28Mcps TDD Time Slot LCR IE] is not provided in the COMMON MEASUREMENT INITIATION REQUEST message the RNS2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.] If the SFN IE is included in the COMMON MEASUREMENT INITIATION REQUEST message and the Report Characteristics IE is other than Periodic, On Demand or On Modification, the RNS2 shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

8.5.2.4.1

Abnormal Conditions for Iur-g

The measurements which can be requested on the Iur and Iur-g interfaces are shown in the table below marked with X.

3GPP

Release 11

258

3GPP TS 25.423 V11.2.0 (2012-06)

Table 6: Allowed Common measurement type on Iur and Iur-g interfaces

Common Measurement Type Received total wide band power Transmitted Carrier Power UL Timeslot ISCP Load UTRAN GPS Timing of Cell Frames for LCS SFN-SFN Observed Time Difference RT load NRT load Information UTRAN GANSS Timing of Cell Frames for UE Positioning Iur X X X X X X X X X X X Interface Iur-g

If the RNC2 receives from the BSS1 a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the RNC2 shall reject the Common Measurement Initiation procedure. If the BSS2 receives from the BSS1 / RNC1 a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the BSS2 shall reject the Common Measurement Initiation procedure. If the RNC2 receives from the BSS1 a COMMON MEASUREMENT INITIATION REQUEST message in which the SFN reporting indicator IE is set to FN Reporting Required, the RNC2 shall ignore that IE. If the BSS2 receives from the BSS1 / RNC1 a COMMON MEASUREMENT INITIATION REQUEST message in which the SFN reporting indicator IE is set to FN Reporting Required, the BSS2 shall ignore that IE. The allowed combinations of the Common measurement type and Report characteristics type are shown in the table in section 8.5.2.4 marked with X. For not allowed combinations, the RNC2/BSS2 shall reject the Common Measurement Initiation procedure.

8.5.3 Common Measurement Reporting

8.5.3.1 General
This procedure is used by an RNC to report the result of measurements requested by another RNC using the Common Measurement Initiation. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.3.2

Successful Operation
RNC1 RNC2

COMMON MEASUREMENT REPORT

Figure 30C: Common Measurement Reporting procedure, Successful Operation If the requested measurement reporting criteria are met, the RNC2 shall initiate the Common Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications. The Measurement ID IE shall be set to the Measurement ID provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure.

3GPP

Release 11

259

3GPP TS 25.423 V11.2.0 (2012-06)

If the achieved measurement accuracy does not fulfil the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Common Measurement Value Information IE shall indicate Measurement not Available. If the RNC2 was configured to perform the Measurement Recovery Behavior, the RNC2 shall indicate Measurement Available to the RNC1 when the achieved measurement accuracy again fulfils the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) and include the Measurement Recovery Report Indicator IE in the COMMON MEASUREMENT REPORT message if the requested measurement reporting criteria are not met. For measurements included in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE, the RNC2 shall include the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE if available. If the Common Measurement Type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was UTRAN GPS Timing of Cell Frames for UE Positioning, then the RNC2 shall include in the TUTRAN-GPS Measurement Value Information IE the TUTRAN-GPS Quality IE and the TUTRAN-GPS Drift Rate Quality IE, if available. If the Common Measurement Type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was UTRAN GANSS Timing of Cell Frames for UE Positioning, then the RNC2 shall include in the TUTRAN-GANSS Measurement Value Information IE the TUTRAN-GANSS Quality IE and the TUTRAN-GANSS Drift Rate Quality IE, if available.

8.5.3.2.1

Successful Operation for Iur-g

If the requested measurement reporting criteria are met, the RNC2/BSS2 shall initiate a Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications. The Common Measurement ID IE shall be set to the Common Measurement ID provided by RNC1/BSS1 when initiating the measurement with the Common Measurement Initiation procedure. If the Common measurement type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was SFN-SFN Observed Time Difference, then RNC2 shall include in the COMMON MEASUREMENT REPORT all the available measurements in the Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE and shall include the neighbouring cells with no measurement result available in the Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE. If the Common measurement type provided by RNC1 when initiating the measurement with the Common Measurement Initiation procedure was not set to SFN-SFN Observed Time Difference and the SFN Reporting Indicator when initiating the measurement was set to FN Reporting Required, the RNC2 shall include the SFN IE in the COMMON MEASUREMENT REPORT message. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the Common Measurement Type IE is set to SFN-SFN Observed Time Difference, then the SFN Reporting Indicator IE is ignored.

8.5.3.3
-

Abnormal Conditions

8.5.4 Common Measurement Termination

8.5.4.1 General
This procedure is used by an RNC to terminate a measurement previously requested by the Common Measurement Initiation procedure. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.4.2

Successful Operation

Figure 30D: Common Measurement Termination procedure, Successful Operation

3GPP

Release 11

260

3GPP TS 25.423 V11.2.0 (2012-06)

This procedure is initiated with a COMMON MEASUREMENT TERMINATION REQUEST message. Upon receipt, RNC2 shall terminate reporting of common measurements corresponding to the received Measurement ID IE.

8.5.4.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the Common Measurement Termination procedure as specified in section 8.5.4.2.

8.5.4.3
-

Abnormal Conditions

8.5.5 Common Measurement Failure

8.5.5.1 General
This procedure is used by an RNC to notify another RNC that a measurement previously requested by the Common Measurement Initiation procedure can no longer be reported. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.5.2

Successful Operation

Figure 30E: Common Measurement Failure procedure, Successful Operation This procedure is initiated with a COMMON MEASUREMENT FAILURE INDICATION message, sent from RNC2 to RNC1 to inform the RNC1 that a previously requested measurement can no longer be reported. RNC2 has locally terminated the indicated measurement. The RNC2 shall include in the COMMON MEASUREMENT FAILURE INDICATION message the reason for the failure in the Cause IE.

8.5.5.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the Common Measurement Failure procedure as specified in section 8.5.5.2.

8.5.5.3
-

Abnormal Conditions

8.5.6 Information Exchange Initiation

8.5.6.1 General
This procedure is used by an RNC to request the initiation of an information exchange with another RNC. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

3GPP

Release 11

261

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.6.2

Successful Operation
RNC1 RNC2

INFORMATION EXCHANGE INITIATION REQUEST INFORMATION EXCHANGE INITIATION RESPONSE

Figure 30F: Information Exchange Initiation procedure, Successful Operation The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from RNC1 to RNC2. Upon receipt, the RNC2 shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications. If the Information Exchange Object Type is set to MBMS Bearer Service and the Information Type Item IE is set to MBMS Bearer Service Full Address, the RNC2 shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE, the Access Point Name and the IP Multicast Address corresponding to this TMGI in the MBMS Bearer Service Identifiers List IE in the INFORMATION EXCHANGE INITIATION RESPONSE message. [FDD If the Information Exchange Object Type is set to MBMS Bearer Service in MBMS Cell and the Information Type Item IE is set to MBMS Counting Information, the RNC2 shall perform counting in cells as defined in TS 25.346 [50] and report in the Counting Result IE for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE either the counting information or, if relevant counting information is not available in RNC2 (TS 25.346 [50]), the value 0 in the INFORMATION EXCHANGE INITIATION RESPONSE message.] [FDD If the Information Exchange Object Type is set to MBMS Bearer Service in MBMS Cell and the Information Type Item IE is set to MBMS Transmission Mode, the RNC2 shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE, the transmission mode for each TMGI in the cells of RNC2 that have a neighbour relation to the cells received in MBMS Cell List IE as defined in TS 25.346 [50] in the INFORMATION EXCHANGE INITIATION RESPONSE message. If no cells of RNC2 have a neighbour relation to a cell received in MBMS Cell List IE for a TMGI the value Not Provided shall be used] [FDD If the Information Exchange Object Type is set to MBMS Cell and the Information Type Item IE is set to MBMS Neighbouring Cell Information, the RNC2 shall report for each cell included in the received MBMS Cell List IE, the MBMS radio bearer information for each cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.] [FDD If the Information Exchange Object Type is set to MBMS Bearer Service in MBMS Cell and the Information Type Item IE is set to MBMS RLC Sequence Number, the RNC2 shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE, the RLC sequence number for each TMGI for the indicated cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.] If the Information Exchange Object Type is set to ANR Cell and the Information Type Item IE is set to ANR Cell Information, the RNC2 shall, if supported, for each cell in the ANR Cell List IE that is controlled by RNC2, report the ANR Cell Information in the INFORMATION EXCHANGE INITIATION RESPONSE message. If the Information Type IE contains a GANSS Generic Data IE, at least one of the GANSS Navigation Model And Time Recovery, GANSS Time Model GNSS-GNSS, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, GANSS Auxiliary Information IEs shall be present in the GANSS Generic Data IE. If the GANSS Generic Data IE does not contain the GANSS ID IE, the RNC2 shall assume that the corresponding GANSS is Galileo.

Information Report Characteristics:

3GPP

Release 11

262

3GPP TS 25.423 V11.2.0 (2012-06)

The Information Report Characteristics IE indicates how the reporting of the information shall be performed. If the Information Report Characteristics IE is set to On Demand, the RNC2 shall report the requested information immediately. If the Information Report Characteristics IE is set to Periodic, the RNC2 shall report the requested information immediately and then shall periodically initiate the Information Reporting procedure for all the requested information, with the report frequency indicated by the Information Report Periodicity IE. If the Information Report Characteristics IE is set to On Modification, the RNC2 shall report the requested information immediately if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the RNC2 shall initiate the Information Reporting procedure when the requested information becomes available. The RNC2 shall then initiate the Information Reporting procedure in accordance to the following conditions: If the Information Type Item IE is set to IPDL Parameters, the RNC2 shall initiate the Information Reporting procedure when any change in the parameters occurs. If the Information Type Item IE is set to DGPS Corrections, the RNC2 shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IODE. If the Information Type Item IE is set to GPS Information and the GPS Information Item IE includes GPS Navigation Model & Recovery Assistance, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred regarding either the IODC or the list of visible satellites, identified by the Sat ID IEs. If the Information Type Item IE is set to GPS Information and the GPS Information Item IE includes GPS Ionospheric Model, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred. If the Information Type Item IE is set to GPS Information and the GPS Information Item IE includes GPS UTC Model, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred in the tot or WNt parameter. If the Information Type Item IE is set to GPS Information and the GPS Information Item IE includes GPS Almanac, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when a change in the toa or WNa parameter has occurred. If the Information Type Item IE is set to GPS Information and the GPS Information Item IE includes GPS Real-Time Integrity, the RNC2 shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred. If the Information Type IE is set to Cell Capacity Class, the RNC2 shall initiate the Information Reporting procedure for uplink and downlink cell capacity class when any change has occurred. If either uplink or downlink cell capacity class satisfies the requested report characteristics, the RNC2 shall report the result of both uplink and downlink cell capacity information. If any of the above Information Type IEs becomes temporarily unavailable, the RNC2 shall initiate the Information Reporting procedure for this specific Information Item by indicating Information Not Available in the Requested Data Value Information IE. If the Information becomes available again, the RNC2 shall initiate the Information Reporting procedure for this specific Information. If the Information Type IE is set to NACC related data, the RNC2 shall initiate the Information Reporting procedure for NACC related data if any change has occurred. If the Information Type IE is set to Inter-frequency Cell Information, the RNC2 shall initiate the Information Reporting procedure for this specific Information Item when any change has occurred to the inter-frequency cell information broadcasted in the SIB11 or SIB12. If the Information Type Item IE is set to DGANSS Corrections, the RNC2 shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IODE.

3GPP

Release 11 -

263

3GPP TS 25.423 V11.2.0 (2012-06)

If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Navigation Model And Time Recovery IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Ionospheric Model IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS UTC Model IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred in the tot or WNt parameter. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Almanac IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change in the Toa, IODa, or Week Number parameter has occurred. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Real Time Integrity IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Data Bit Assistance IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred. If the Information Type Item IE is set to MBMS Transmission Mode, the RNC2 shall initiate the Information Reporting procedure when any change in the parameter occurs. If the Information Type Item IE is set to MBMS Neighbouring Cell Information, the RNC2 shall initiate the Information Reporting procedure when any change in the parameters occurs. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Additional Navigation Models And Time Recovery IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Additional Ionospheric Model IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Additional UTC Models IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the tot,WNot, WNt, or NA parameter. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Earth Orientation Parameters IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the tEOP parameter. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Auxiliary Information IE, the RNC2 shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the Signals Available or Channel Number IE parameter.

Response message: If the RNC2 is able to determine the information requested by the RNC1, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message. The message shall include the Information Exchange ID IE set to the same value that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the Report Characteristics IE is set to or On Modification or Periodic, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the Requested Data Value IE if the data are available. When the Report Characteristics IE is set to On Demand, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the Requested Data Value IE. If the Requested DataValue IE contains the GANSS Common Data IE, at least one of the GANSS Ionospheric Model, GANSS RX Pos, GANSS Additional Ionospheric Model, or GANSS Earth Orientation Parameters IEs shall be present.

3GPP

Release 11

264

3GPP TS 25.423 V11.2.0 (2012-06)

Any GANSS Generic Data IE associated with a given GANSS included in the Requested DataValue IE shall contain at least one of the DGANSS Corrections, GANSS Navigation Model And Time Recovery, GANSS Time Model, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Time Models, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, or GANSS Auxiliary Information IEs. If the GANSS Generic Data IE does not contain the GANSS ID IE, the corresponding GANSS is Galileo. The DGANSS Corrections IE contains one or several DGANSS Information IE(s), each of them associated with a GANSS Signal. A DGANSS Information IE for a particular GANSS that does not contain the GANSS Signal ID IE is by default associated with the default signal defined in TS 25.331 [16], clause 10.3.3.45a. The GANSS Real Time Integrity IE contains one or several Satellite Information IEs, each of them associated with a satellite and a GANSS Signal. A Satellite Information IE for a particular GANSS that does not contain the Bad GANSS Signal ID IE is by default associated with all the signals of the corresponding satellite (see [53], ISGPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], DTFA01-96-C-00025 [58], IS-QZSS [59], [60]).

If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS IE with exactly one bit set to value 1, the RNC2 shall include the GANSS Time Model IE in the Requested Data Value IE with the requested time information. If the Information Type Item IE is set to GANSS Information and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS IE with more than one bit set to value 1, the RNC2 shall include the GANSS Additional Time Models IE in Requested Data Value IE with the requested time information for each GANSS. If the Information Type Item IE is set to DGPS Corrections, the RNC2 shall include the DGPS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available. If the Information Type Item IE is set to DGANSS Corrections, the RNC2 shall include the DGANSS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available. If the Information Type Item IE is set to "GPS Almanac", the RNC2 shall include the GPS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available. If the Information Type Item IE is set to "GANSS Almanac", the RNC2 shall include the GANSS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available. If the Information Type Item IE is set to "GANSS Time Model GNSS-GNSS", the RNC2 shall include the GANSS Time Model IE in Requested Data Value IE with the Delta_T IE included, if available.

8.5.6.2.1

Successful Operation for Iur-g

The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from BSS1 to BSS2/RNC2 or by RNC1 to BSS2. Upon receipt, the BSS2/RNC2 shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications. Information Report Characteristics on Iur-g: If the Information Type Item IE is set to Cell Capacity Class, the RNC2/BSS2 shall initiate measurements and report results as described in section 8.5.6.2. The Information Report Characteristics IE indicates how the reporting of the information shall be performed. This IE is used as described in section 8.5.6.2.

3GPP

Release 11

265

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.6.3

Unsuccessful Operation
RNC1 RNC2

INFORMATION EXCHANGE INITIATION REQUEST INFORMATION EXCHANGE INITIATION FAILURE

Figure 30G: Information Exchange Initiation procedure, Unsuccessful Operation If the requested Information Type received in the Information Type IE indicates a type of information that RNC2 cannot provide, the RNC2 shall reject the Information Exchange Initiation procedure. If the requested information provision cannot be accessed, the RNC2 shall reject the procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. The message shall include the Information Exchange ID IE set to the same value that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the Cause IE set to an appropriate value. Typical cause values are as follows: Radio Network Layer Cause: Information temporarily not available. Information Provision not supported for the object.

8.5.6.4

Abnormal Conditions

If the Information Report Characteristics IE is set to On Modification, and the Information Type Item IE is set to DGPS Corrections, but the Information Threshold IE is not received in the INFORMATION EXCHANGE INITIATION REQUEST message, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. If the Information Exchange Object Type IE is set to a value other than GSM Cell and the Information Type Item IE set to NACC related data the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. If the Information Type Item IE is set to the value MBMS Bearer Service Full Address and the Information Exchange Object Type IE is not set to MBMS Bearer Service, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. If the Information Type Item IE is set to the value ANR Cell Information and the Information Exchange Object Type IE is not set to ANR Cell, the RNC2 shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. If the Information Type Item IE is set to the value ANR Cell Information and the Information Exchange Object Type IE is set to ANR Cell, but the RNC2 can only collect the Requested Data Value for the subset of the cells requested, RNC2 shall not reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION RESPONSE message with the information it could obtain. The allowed combinations of the Information type and Information Report Characteristics type are shown in the table below marked with X. For not allowed combinations, the RNC2 shall reject the Information Exchange Initiation procedure using the INFORMATION EXCHANGE INITIATION FAILURE message. Table 6a: Allowed Information Type and Information Report Characteristics type combinations

3GPP

Release 11
Type UTRAN Access Point Position with Altitude Information UTRAN Access Point Position IPDL Parameters GPS Information DGPS Corrections GPS RX Pos SFN-SFN Measurement Reference Point Position Cell Capacity Class NACC related data MBMS Bearer Service Full Address Inter-frequency Cell Information GANSS Information DGANSS Corrections GANSS RX Pos MBMS Counting Information [FDD only] MBMS Transmission Mode [FDD only] MBMS Neighbouring Cell Information [FDD only] MBMS RLC Sequence Number [FDD only] ANR Cell Information

266

3GPP TS 25.423 V11.2.0 (2012-06)

Information Report Characteristics Type On Demand Periodic On Modification X X X X X X X X X X X X X X X X X X X X X X X X

X X X X X X X X X

8.5.6.4.1

Abnormal Conditions for Iur-g

The information types that can be requested on the Iur and Iur-g interfaces are shown in the table below marked with X. For information types that are not applicable on the Iur-g interface, the BSS shall reject the Information Exchange Initiation procedure. Table 7: Allowed Information types on Iur and Iur-g interfaces
Information Type UTRAN Access Point Position with Altitude Information UTRAN Access Point Position IPDL Parameters DGPS Corrections GPS Information GPS RX Pos SFN-SFN Measurement Reference Point Position Cell Capacity Class NACC related data MBMS Bearer Service Full Address Inter-frequency Cell Information DGANSS Corrections GANSS Information GANSS RX Pos MBMS Counting Information [FDD only] MBMS Transmission Mode [FDD only] MBMS Neighbouring Cell Information [FDD only] MBMS RLC Sequence Number [FDD only] Iur X X X X X X X X X X X X X X X X X X Interface Iur-g

8.5.7 Information Reporting

8.5.7.1 General
This procedure is used by a RNC to report the result of information requested by another RNC using the Information Exchange Initiation. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

3GPP

Release 11

267

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.7.2

Successful Operation
RNC1 RNC2

INFORMATION REPORT

Figure 30H: Information Reporting procedure, Successful Operation If the requested information reporting criteria are met, the RNC2 shall initiate an Information Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications. The Information Exchange ID IE shall be set to the Information Exchange ID provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure. The Requested Data Value IE shall include at least one IE containing the data to be reported.

8.5.7.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the Information Reporting procedure as specified in section 8.5.7.2.

8.5.7.3
-

Abnormal Conditions

8.5.8 Information Exchange Termination

8.5.8.1 General
This procedure is used by a RNC to terminate the information exchange requested using the Information Exchange Initiation. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.8.2

Successful Operation

Figure 30I: Information Exchange Termination procedure, Successful Operation This procedure is initiated with a INFORMATION EXCHANGE TERMINATION REQUEST message. Upon receipt, the RNC2 shall terminate the information exchange corresponding to the Information Exchange ID IE provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure.

8.5.8.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the Information Exchange Termination procedure as specified in section 8.5.8.2.

8.5.8.3
-

Abnormal Conditions

3GPP

Release 11

268

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.9 Information Exchange Failure

8.5.9.1 General
This procedure is used by a RNC to notify another that the information exchange it previously requested using the Information Exchange Initiation can no longer be reported. This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.9.2

Successful Operation
RNC1
INFORMATION EXCHANGE FAILURE INDICATION

RNC2

Figure 30J: Information Exchange Failure procedure, Successful Operation This procedure is initiated with a INFORMATION EXCHANGE FAILURE INDICATION message, sent from the RNC2 to the RNC1, to inform the RNC1 that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The RNC2 shall include in the INFORMATION EXCHANGE FAILURE INDICATION message the Information Exchange ID IE set to the same value provided by the RNC1 when initiating the information exchange with the Information Exchange Initiation procedure, and the RNC2 shall include the Cause IE set to an appropriate value. Typical cause values are as follows: Radio Network Layer Cause: Information temporarily not available.

8.5.9.2.1

Successful Operation for Iur-g

The RNC1/BSS1 and RNC2/BSS2 shall use the Information Exchange Failure procedure as specified in section 8.5.9.2.

8.5.10 Reset
8.5.10.1 General
The purpose of the reset procedure is to align the resources in RNC1 and RNC2 in the event of an abnormal failure. The procedure uses connectionless signalling.

8.5.10.2

Successful Operation

Figure 30K: Reset procedure, Successful Operation The procedure is initiated with a RESET REQUEST message sent from the RNC1 to the RNC2. If the Reset Indicator IE is set to Context, then: For all indicated UE Contexts identified by the S-RNTI IE, the RNC2 in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2.

3GPP

Release 11 -

269

3GPP TS 25.423 V11.2.0 (2012-06)

For all indicated UE Contexts identified by the D-RNTI IE, the RNC2 in the role of SRNC, shall remove the information related to the RNC1 for all indicated UE Contexts and the radio resources allocated for these UE Contexts.

If the Reset Indicator IE is set to Context Group, then: For all indicated UE Context Groups identified by the S-RNTI Group IE, the RNC2 in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2.

If the Reset Indicator IE is set to All Contexts, then the RNC2 shall: In the role of DRNC, remove all the UE Contexts for which the RNC1 is the SRNC and all the radio resources allocated for these UE Contexts. In addition, the RNC2 shall take actions according to Annex D.2. In the role of SRNC, remove the information related to the RNC1 for all the UE Contexts and all the radio resources allocated for these UE Contexts.

For all the removed UE Contexts and for all the UE Contexts for which the RNC2 has removed information related to the RNC1, the RNC2 shall also initiate release of the dedicated or common user plane resources that were involved in these UE Contexts. After clearing all related resources, the RNC2 shall return the RESET RESPONSE message to the RNC1.

8.5.10.3

Abnormal Conditions

If the RESET message is received, any other ongoing procedure (except another Reset procedure) on same Iur interface related to a context indicated explicitly or implicitly in the message shall be aborted.

8.5.11 Direct Information Transfer

8.5.11.1 General
This procedure is used by an RNC to transfer information to another RNC spontaneously. This procedure shall use the connectionless mode of signalling bearer.

8.5.11.2

Successful Operation
RNC1
DIRECT INFORMATION TRANSFER

RNC2

Figure 30L: Direct Information Transfer procedure, Successful Operation The procedure is initiated with an DIRECT INFORMATION TRANSFER message sent from RNC1 to RNC2. If the initiating RNC of this procedure is RNC1, RNC1 shall provide appropriate information in the Provided Information IE. MBMS Channel Type Indication: At the start time of a session for an MBMS bearer service, if the RNC1 is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2 and if the channel type is determined by the RNC1 for certain cells in the DRNS, the procedure shall be initiated by the RNC1 to the RNC2. In this case, the RNC1 shall include in the Provided Information IE the Channel Type Information IE in the DIRECT INFORMATION TRANSFER message. During a session of an MBMS bearer service, if the RNC1 is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2, then the RNC1 may initiate this procedure to indicate

3GPP

Release 11

270

3GPP TS 25.423 V11.2.0 (2012-06)

channel type change for the MBMS bearer service in certain cells. In this case, the RNC1 shall include in the Provided Information IE the Channel Type Information IE in the DIRECT INFORMATION TRANSFER message. The RNC1 shall include the available information within the PTM Cell List IE, the PTP Cell List IE and/or the Not Provided Cell List IE in the Channel Type Information IE. MBMS Preferred Frequency Layer Indication: At the start time of a session for an MBMS bearer service, if the RNC1 is in the DRNC role for at least one CELL_DCH UE whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC2 and if the preferred frequency layer is determined by the RNC1 for certain cells that host at least one of these CELL_DCH Ues whose SRNC is RNC2, the procedure shall be initiated by the RNC1 to the RNC2. In this case, the RNC1 shall include in the Provided Information IE the Preferred Frequency Layer Information IE in the DIRECT INFORMATION TRANSFER message. If some of the cells controlled by RNC1 that host at least one of these CELL_DCH Ues whose SRNC is RNC2 are configured with different preferred frequencies, the Additional Preferred Frequency IE as well as Default Preferred Frequency IE shall be included in the Preferred Frequency Layer Information IE. In this case, for each preferred frequency different from the Default Preferred Frequency IE, one Additional Preferred Frequency IE shall be included containing at least one Corresponding Cells IE. ANR Report Indication: The message contains ANR Report Indication IE if the initiating RNC (RNC1) has decided to forward a logged ANR report received over Uu to RNC2. On reception of the ANR Report Indication IE, RNC2 may use the information to configure neighbour relations.

8.5.12 Information Transfer Control

8.5.12.1 General
This procedure is used by an RNC to control transfer of information (e.g. log information related to ANR) from an RNC to any other RNC. This procedure is initiated by an RNC to suspend or resume transfer of information. This procedure shall use the connectionless mode of signalling bearer.

8.5.12.2

Successful Operation
RNC1 RNC2

INFORMATION TRANSFER CO NTROL REQ UEST

Figure 30M: Information Transfer Control procedure, Successful Operation The RNC1 initiates the procedure by sending the INFORMATION TRANSFER CONTROL REQUEST message to the RNC2. The Control Type IE within the INFORMATION TRANSFER CONTROL REQUEST message shall be used to either suspend or to resume (respectively indicated by Suspension IE or Resume IE in Control Type IE) the transfer of information for the specified scope of objects indicated by Controlled Object Scope IE. If the control of information transfer is intended for individual cells, those cells shall be indicated in the UMTS Cell Information IE within the Controlled Object Scope IE. If the UMTS Cell Information IE is not included, the procedure is intended for the whole entity indicated in RNC-ID IE or Extended RNC-ID IE. In shared network configurations, PLMN identities shall be indicated with Multiple PLMN List IE.

3GPP

Release 11

271

3GPP TS 25.423 V11.2.0 (2012-06)

8.5.12.3
-

Abnormal Conditions

8.6 MBMS Procedures

8.6.1 MBMS Attach
8.6.1.1 General
The MBMS Attach procedure is used by the SRNC to either create a UE Link/URA Link in the DRNC or inform the DRNC about any addition of one or several MBMS bearer services in an already stored UE Link or URA Link. This procedure shall use the signalling bearer mode specified below.

8.6.1.2

Successful Operation
SRNC Layer DRNC Layer

MBMS ATTACH COMMAND

Figure 31: MBMS Attach procedure, Successful Operation The SRNC initiates the procedure by sending the message MBMS ATTACH COMMAND message to the DRNC. When the UE is utilising one or more radio links in the DRNC, the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If the UE is not utilising any radio link, the message shall be sent using the connectionless service of the signalling bearer. If no UE State IE is included in the message or the UE State IE is set to CELL_FACH/CELL_PCH, the DRNC shall perform the UE Linking as specified in TS 25.346 [50], section 5.1.6. If the UE State IE is set to URA_PCH, the DRNC shall perform the URA Linking as specified in TS 25.346 [50], section 5.1.10.

8.6.1.3
-

Abnormal Conditions

8.6.2 MBMS Detach

8.6.2.1 General
The MBMS Detach procedure is used by the SRNC to either delete a UE Link/URA Link in the DRNC or to inform DRNC about any removal of one or several MBMS bearer services in an already stored UE link or URA Link. This procedure shall use the signalling bearer mode specified below.

3GPP

Release 11

272

3GPP TS 25.423 V11.2.0 (2012-06)

8.6.2.2

Successful Operation
SRNC Layer DRNC Layer

MBMS DETACH COMMAND

Figure 32: MBMS Detach procedure, Successful Operation The SRNC initiates the procedure by sending the message MBMS DETACH COMMAND message to the DRNC. When the UE is utilising one or more radio links in the DRNC, the message shall be sent using the connection oriented service of the signalling bearer and no further identification of the UE Context in the DRNC is required. If the UE is not utilising any radio link, the message shall be sent using the connectionless service of the signalling bearer. If no UE State IE is included in the message or the UE State IE is set to CELL_FACH/CELL_PCH, the DRNC shall perform the UE De-linking as specified in TS 25.346 [50], section 5.1.6. If the UE State IE is set to URA_PCH, the DRNC shall perform the URA De-linking as specified in TS 25.346 [50], section 5.1.10.

8.6.2.3
-

Abnormal Conditions

Elements for RNSAP Communication

9.1 Message Functional Definition and Content
9.1.1 General

This subclause defines the structure of the messages required for the RNSAP protocol in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is contradiction between the tabular format in subclause 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, in which the tabular format shall take precedence. NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [28].

9.1.2 Message Contents

9.1.2.1 Presence
An information element can be of the following types:
M O C IEs marked as Mandatory (M) shall always be included in the message. IEs marked as Optional (O) may or may not be included in the message. IEs marked as Conditional I shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included.

In the case of an Information Element group, the group is preceded by a name for the info group (in bold). It is also indicated how many times a group may be repeated in the message and whether the group is conditional. Each group may be also repeated within one message. The presence field of the Information Elements inside one group defines if the Information Element is mandatory, optional or conditional if the group is present.

3GPP

Release 11

273

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.2.2

Criticality

Each information element or Group of information elements may have criticality information applied to it. Following cases are possible:
YES GLOBAL EACH No criticality information is applied explicitly. Criticality information is applied. YES is usable only for non-repeatable information elements. The information element and all its repetitions together have one common criticality information. GLOBAL is usable only for repeatable information elements. Each repetition of the information element has its own criticality information. It is not allowed to assign different criticality values to the repetitions. EACH is usable only for repeatable information elements.

9.1.2.3

Range

The Range column indicates the allowed number of copies of repetitive IEs/IE groups.

9.1.2.4

Assigned Criticality

This column provides the actual criticality information as defined in subclause 10.3.2, if applicable.

3GPP

Release 11

274

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.3 RADIO LINK SETUP REQUEST

9.1.3.1 FDD Message

3GPP

Release 11

275

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID SRNC-ID

Presence M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 RNC-ID 9.2.1.50

Semantics Description

Criticality YES YES

Assigned Criticality reject reject

S-RNTI

9.2.1.53

If the Extended SRNC-ID IE is included in the message, the SRNCID IE shall be ignored. If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

YES

reject

D-RNTI Allowed Queuing Time UL DPCH Information >UL Scrambling Code >Min UL Channelisation Code Length >Max Number of UL DPDCHs >Puncture Limit >TFCS >UL DPCCH Slot Format >Uplink SIR Target >Diversity mode >Not Used >Not Used >DPC Mode >UL DPDCH Indicator for EDCH operation

O O 1 M M C CodeLen M M M O M O O O O

9.2.1.24 9.2.1.2 9.2.2.53 9.2.2.25 9.2.2.24 9.2.1.46 9.2.1.63 9.2.2.52 Uplink SIR 9.2.1.69 9.2.2.8 NULL NULL 9.2.2.12A 9.2.2.52A For the UL.

YES YES YES YES YES

reject reject reject

This IE may be present without the presence of the E-DPCH Information IE

reject reject

DL DPCH Information >TFCS >DL DPCH Slot Format >Number of DL Channelisation Codes >TFCI Signalling Mode >TFCI Presence >Multiplexing Position >Power Offset Information >>PO1 >>PO2

0..1 M M M M CSlotFormat M 1 M M Power Offset 9.2.2.30 Power Offset 9.2.2.30 Power offset for the TFCI bits. Power offset for the TPC bits. 9.2.1.63 9.2.2.9 9.2.2.26A 9.2.2.46 9.2.1.55 9.2.2.26

YES

reject

3GPP

Release 11

276

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>PO3 >FDD TPC Downlink Step Size >Limited Power Increase >Inner Loop DL PC Status DCH Information RL Information >RL ID >C-ID >First RLS Indicator >Frame Offset >Chip Offset >Propagation Delay >Diversity Control Field >Initial DL TX Power >Primary CPICH Ec/No >Not Used >Transmit Diversity Indicator >Enhanced Primary CPICH Ec/No >RL Specific DCH Information >Delayed Activation >Cell Portion ID >RL specific E-DCH Information >E-DCH RL Indication >Extended Propagation Delay >Synchronisation Indicator >HS-DSCH Preconfiguration Setup >Non-Serving RL Preconfiguration Setup >F-TPICH Information Transmission Gap Pattern Sequence Information Active Pattern Sequence Information Permanent NAS UE Identity DL Power Balancing Information HS-DSCH Information

Presence M M M M M

Range

IE Type and Reference Power Offset 9.2.2.30 9.2.2.16 9.2.2.21A 9.2.2.21a DCH FDD Information 9.2.2.4A

Semantics Description Power offset for the pilot bits.

Criticality YES EACH

Assigned Criticality

reject notify

1..<maxno ofRLs> M M M M M O C NotFirstRL O O O C Diversity mode O O O O O O O O O O O O O O O O 9.2.1.49 9.2.1.6 9.2.2.16A 9.2.1.30 9.2.2.1 9.2.2.33 9.2.1.20 DL Power 9.2.1.21A 9.2.2.32 NULL 9.2.2.48 9.2.2.13I 9.2.1.49A 9.2.1.19Aa 9.2.2.E 9.2.2.35a 9.2.2.4E 9.2.2.33a 9.2.2.45A 9.2.2.100 9.2.2.124 9.2.2.139 9.2.2.47A 9.2.2.A 9.2.1.73 9.2.2.10A HS-DSCH FDD Information 9.2.2.19a RL ID 9.2.1.49 0..<maxno ofMBMS> M 0..1 9.2.1.80

YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES ignore ignore reject ignore reject reject ignore reject ignore ignore ignore reject reject ignore ignore reject

HS-PDSCH RL ID MBMS Bearer Service List >TMGI E-DPCH Information

C InfoHSDS CH

YES GLOBAL YES

reject notify reject

3GPP

Release 11

277

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >Maximum Set of EDPDCHs >Puncture Limit >E-TFCS Information >E-TTI >E-DPCCH Power Offset >E-RGCH 2-Index-Step Threshold >E-RGCH 3-Index-Step Threshold >HARQ Info for E-DCH >HS-DSCH Configured Indicator > Minimum Reduced EDPDCH Gain Factor E-DCH FDD Information Serving E-DCH RL F-DPCH Information >Power Offset Information >>PO2 >FDD TPC Downlink Step Size >Limited Power Increase >Inner Loop DL PC Status >F-DPCH Slot Format Support Request >F-DPCH Slot Format Initial DL DPCH Timing Adjustment Allowed DCH Indicator For E-DCHHSDPA Operation Serving Cell Change CFN Continuous Packet Connectivity DTX-DRX Information Continuous Packet Connectivity HS-SCCH less Information Extended SRNC-ID

Presence M M M M M M M M M O CEDCHInfo O

Range

IE Type and Reference 9.2.2.24e 9.2.1.46 9.2.2.4G 9.2.2.4J 9.2.2.4K 9.2.2.64 9.2.2.65 9.2.2.66 9.2.2.19C 9.2.2.102 9.2.2.4B 9.2.2.38C

Semantics Description

Criticality YES YES YES YES _ YES YES YES YES YES YES YES

Assigned Criticality

ignore reject reject reject

0..1 1 M M M M O O O O O O O O Power Offset 9.2.2.30 9.2.2.16 9.2.2.21A 9.2.2.21a 9.2.2.86 9.2.2.85 9.2.2.21b 9.2.2.67 CFN 9.2.1.9 9.2.2.72 9.2.2.74 Extended RNC-ID 9.2.1.50a The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. For secondary serving HSDSCH cell. Max 7 in this 3GPP release. This IE shall be ignored by DRNS.

reject Ignore ignore reject reject reject reject reject

YES

Additional HS Cell Information RL Setup

0..<maxno ofHSDSC H-1>

EACH

reject

>HS-PDSCH RL ID >C-ID >HS-DSCH Secondary Serving Information

M M M

RL ID 9.2.1.49 9.2.1.6 9.2.2.19aa

3GPP

Release 11

278

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name UE Aggregate Maximum Bit Rate Additional E-DCH Cell Information RL Setup Req

Presence O

Range

IE Type and Reference 9.2.1.137

Semantics Description

Criticality YES

Assigned Criticality ignore reject

0..1

For E-DCH on multiple frequencies in this DRNS. 9.2.2.113 E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.110 9.2.2.127 9.2.2.131 9.2.1.154 The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES

>Multicell E-DCH Transport Bearer Mode >Additional E-DCH Cell Information Setup

M 1..<maxno ofEDCH1>

>>Additional E-DCH FDD Setup Information Usefulness of Battery Optimization UL CLTD Information Extended S-RNTI

M O O O

YES YES YES ignore reject reject

Condition CodeLen SlotFormat NotFirstRL Diversity mode InfoHSDSCH EDCHInfo Range bound maxnoofRLs maxnoofMBMS maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation The IE shall be present if Min UL Channelisation Code length IE equals to 4 The IE shall be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. The IE shall be present if the RL is not the first one in the RL Information IE. The IE shall be present if Diversity Mode IE in UL DPCH Information IE is not equal to none. This IE shall be present if HS-DSCH Information IE is present. This IE shall be present if E-DPCH Information IE is present. Explanation Maximum number of RLs for one UE. Maximum number of MBMS bearer services that a UE can join. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

279

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.3.2

TDD Message
Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 RNC-ID 9.2.1.50 Semantics Description Criticality YES YES Assigned Criticality reject reject

IE/Group Name Message Type Transaction ID SRNC-ID

S-RNTI

9.2.1.53

If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

YES

reject

D-RNTI UL Physical Channel Information >Maximum Number of Timeslots >Minimum Spreading Factor >Maximum Number of UL Physical Channels per Timeslot >Support of 8PSK >Minimum Spreading Factor 7.68Mcps DL Physical Channel Information >Maximum Number of Timeslots >Minimum Spreading Factor >Maximum Number of DL Physical Channels >Maximum Number of DL Physical Channels per Timeslot >Support of 8PSK >Support of PLCCH

O 1 M M M O O 1 M M M O O O

9.2.1.24 9.2.3.3A 9.2.3.4A 9.2.3.3B 9.2.3.7H 9.2.3.19 Applicable to 1.28Mcps TDD only Applicable to 7.68Mcps TDD only For the DL For the DL For the UL For the UL

YES YES YES YES YES

reject reject

ignore ignore reject

9.2.3.3A 9.2.3.4A 9.2.3.3C 9.2.3.3D 9.2.3.7H 9.2.3.16

YES ignore ignore ignore

Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only

YES YES

3GPP

Release 11

280

3GPP TS 25.423 V11.2.0 (2012-06)

>Minimum Spreading Factor 7.68Mcps >Maximum Number of DL Physical Channels 7.68Mcps >Maximum Number of DL Physical Channels per Timeslot 7.68Mcps Allowed Queuing Time UL CCTrCH Information >CCTrCH ID >TFCS >TFCI Coding >Puncture Limit >TDD TPC Uplink Step Size

O O O O 0..<maxn oofCCTr CHs> M M M M O

9.2.3.19 9.2.3.20 9.2.3.21 9.2.1.2

Applicable to 7.68Mcps TDD only Applicable to 7.68Mcps TDD only Applicable to 7.68Mcps TDD only For DCH and USCH

YES YES YES YES EACH YES

ignore ignore ignore reject notify

9.2.3.2 9.2.1.63 9.2.3.11 9.2.1.46 9.2.3.10a

For the UL. Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD For DCH and DSCH For the DL.

reject

DL CCTrCH Information >CCTrCH ID >TFCS >TFCI Coding >Puncture Limit >TDD TPC Downlink Step Size >TPC CCTrCH List M M M M M

0..<maxn oofCCTr CHs> 9.2.3.2 9.2.1.63 9.2.3.11 9.2.1.46 9.2.3.10 0..<maxn oCCTrC Hs> M O O O 1 M M M M O O 9.2.1.49 9.2.1.6 9.2.1.30 9.2.3.7D 9.2.3.5 9.2.3.2D CCTrCH ID 9.2.3.2 DCH TDD Information 9.2.3.2A DSCH TDD Information 9.2.3.3a 9.2.3.15

EACH

notify

List of uplink CCTrCH which provide TPC

>>TPC CCTrCH ID DCH Information DSCH Information USCH Information RL Information >RL ID >C-ID >Frame Offset >Special Burst Scheduling >Primary CCPCH RSCP >DL Time Slot ISCP Info

YES YES YES YES reject reject reject reject

>DL Time Slot ISCP Info LCR >TSTD Support Indicator >RL Specific DCH Information

O O O

9.2.3.2F 9.2.3.13F 9.2.1.49A

Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only

YES YES YES

reject ignore ignore

3GPP

Release 11

281

3GPP TS 25.423 V11.2.0 (2012-06)

>Delayed Activation >UL Synchronisation Parameters LCR

O 0..1

9.2.1.19Aa Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. 9.2.3.13J 9.2.3.13I 9.2.3.5a NULL 9.2.3.73 9.2.1.73 HS-DSCH TDD Information 9.2.3.3aa RL ID 9.2.1.49 RL ID 9.2.1.49 0..<maxn oofMBM S> TDD only Applicable to 1.28Mcps TDD only

YES YES

reject reject

>>Uplink Synchronisation Step Size >>Uplink Synchronisation Frequency >Primary CCPCH RSCP Delta >Idle Interval Configuration Indicator >Cell Portion LCR ID Permanent NAS UE Identity HS-DSCH Information

M M O O O O O

YES YES YES YES YES ignore ignore ignore ignore reject

HS-PDSCH RL ID PDSCH-RL-ID MBMS Bearer Service List >TMGI E-DCH Information >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows Information TDD >E-DCH TDD Information E-DCH Serving RL E-DCH Information 7.68Mcps >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows Information TDD >E-DCH TDD Information 7.68Mcps E-DCH Information 1.28Mcps >E-PUCH Information LCR >E-TFCS Information TDD >E-DCH MAC-d Flows Information TDD >E-DCH TDD Information LCR Extended SRNC-ID

C InfoHSDSC H O

YES YES GLOBAL

reject ignore notify

M 0..1 M M M M O 0..1 M M M M 0..1 M M M M O

9.2.1.80 3.84Mcps TDD only 9.2.3.36 9.2.3.37 9.2.3.38 9.2.3.40 9.2.1.49 9.2.3.36 9.2.3.37 9.2.3.38 9.2.3.51 1.28Mcps TDD only 9.2.3.36a 9.2.3.37 9.2.3.38 9.2.3.40a Extended RNC-ID 9.2.1.50a The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. TDD only 7.68Mcps TDD only

YES YES YES YES YES

reject

reject reject

reject

reject

3GPP

Release 11

282

3GPP TS 25.423 V11.2.0 (2012-06)

Continuous Packet Connectivity DRX Information LCR HS-DSCH Semi-Persistent scheduling Information LCR E-DCH Semi-Persistent scheduling Information LCR RNTI Allocation Indicator DCH Measurement Type indicator Multi-Carrier E-DCH Information

O O O O O 0..1

9.2.3.61 9.2.3.64 9.2.3.66 ENUMERA TED (True) 9.2.3.76

1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only The Extended S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES YES YES YES YES YES

reject reject reject ignore reject reject

>Multi-Carrier E-DCH Transport Bearer Mode LCR >Multi-Carrier E-DCH Information LCR MU-MIMO Indicator Extended S-RNTI

M M O O

9.2.3.79 9.2.3.77 9.2.3.82 9.2.1.154

YES YES reject reject

Condition InfoHSDSCH Range bound maxnoofCCTrCHs maxnoofMBMS

Explanation This IE shall be present if HS-DSCH Information IE is present. Explanation Maximum number of CCTrCH for one UE. Maximum number of MBMS bearer services that a UE can join.

3GPP

Release 11

283

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.4 RADIO LINK SETUP RESPONSE

9.1.4.1 FDD Message

3GPP

Release 11

284

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID D-RNTI CN PS Domain Identifier CN CS Domain Identifier RL Information Response >RL ID >RL Set ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >Received Total Wide Band Power >Not Used >DL Code Information

Presence M M O O O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.12 9.2.1.11 9.2.1.49 9.2.2.35 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.2.35A NULL FDD DL Code Information 9.2.2.14A

Semantics Description

Criticality YES YES YES YES EACH

Assigned Criticality reject ignore ignore ignore ignore

1..<maxno ofRLs> M M O M O O M O M

>CHOICE Diversity Indication >>Combining >>>RL ID >>>DCH Information Response >>>E-DCH FDD Information Response >>Non Combining or First RL >>>DCH Information Response >>>E-DCH FDD Information Response >SSDT Support Indicator >Maximum Uplink SIR >Minimum Uplink SIR >Closed Loop Timing Adjustment Mode >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >Primary Scrambling Code >UL UARFCN >DL UARFCN >Primary CPICH Power >Not Used >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information

M M O O 9.2.1.49 9.2.1.16A 9.2.2.4C Reference RL ID for the combining

YES YES ignore ignore

M O M M M O M M M O O O M O O O

9.2.1.16A 9.2.2.4C 9.2.2.43 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.2.3A 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.45 UARFCN 9.2.1.66 UARFCN 9.2.1.66 9.2.1.44 NULL 9.2.1.41A 9.2.1.41C

YES Corresponds to Nu in TS 25.104 [6] Corresponds to Nd in TS 25.104 [6] ignore

3GPP

Release 11

285

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >PC Preamble >SRB Delay >Cell GA Additional Shapes >DL Power Balancing Activation Indicator >HCS Prio >Primary CPICH Usage For Channel Estimation >Secondary CPICH Information >Active MBMS Bearer Service List >>TMGI >>Transmission Mode >>Preferred Frequency Layer >E-DCH RL Set ID >E-DCH FDD DL Control Channel Information >Initial DL DPCH Timing Adjustment >F-DPCH Slot Format >Frame Offset >Chip Offset >Neighbouring E-UTRA Cell Information >HS-DSCH Preconfiguration Info >Non-Serving RL Preconfiguration Info >Neighbouring UMTS Cell Information Extension Uplink SIR Target Criticality Diagnostics HS-DSCH-RNTI HS-DSCH Information Response

Presence M M O O O O O

Range

IE Type and Reference 9.2.2.27a 9.2.2.39A 9.2.1.5B 9.2.2.10B 9.2.1.30N 9.2.2.32A 9.2.2.38A

Semantics Description

Criticality YES YES YES YES YES GLOBAL

Assigned Criticality

ignore ignore ignore ignore ignore ignore

0..<maxno ofActiveM BMS> M O O O O O 9.2.1.80 9.2.1.81 UARFCN 9.2.1.66 RL Set ID 9.2.2.35 9.2.2.4D DL DPCH Timing Adjustment 9.2.2.9A 9.2.2.85 9.2.1.30 9.2.2.1 9.2.1.41De 9.2.2.99 9.2.2.125 9.2.1.141 Uplink SIR 9.2.1.69 9.2.1.13 9.2.1.30P HS-DSCH FDD Information Response 9.2.2.19b 9.2.2.75 9.2.1.123 0..<maxno ofHSDSC H-1> For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.1.30P 9.2.2.19ba

YES YES YES ignore ignore ignore

O O O O O O O O O O O

YES YES YES YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

Continuous Packet Connectivity HS-SCCH less Information Response SixtyfourQAM DL Support Indicator Additional HS Cell Information Response

O O

YES YES EACH

ignore ignore ignore

>HS-PDSCH RL ID >HS-DSCH-RNTI >HS-DSCH FDD Secondary Serving Information Response

M M M

3GPP

Release 11

286

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >SixtyfourQAM DL Support Indicator Additional E-DCH Cell Information Response

Presence O

Range

IE Type and Reference 9.2.1.123

Semantics Description

Criticality

Assigned Criticality

0..<maxno ofEDCH1>

E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.120

EACH

ignore

>Additional E-DCH FDD Information Response Range bound maxnoofRLs maxnoofActiveMBMS maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of RLs for one UE. Maximum number of MBMS bearer services that are active in parallel. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

287

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.4.2

TDD Message

3GPP

Release 11

288

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID D-RNTI CN PS Domain Identifier CN CS Domain Identifier RL Information Response

Presence M M O O O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.12 9.2.1.11

Semantics Description

Criticality YES YES YES YES YES

Assigned Criticality reject ignore ignore ignore ignore

0..1

Mandatory for 3.84Mcps TDD , not applicable to 1.28Mcps TDD or 7.68Mcps TDD 9.2.1.49 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.3.13D Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.66 9.2.1.8 9.2.1.54 9.2.1.51 9.2.1.78 9.2.1.43 9.2.3.12A 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.7B

>RL ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >UL Time Slot ISCP Info >Maximum Uplink SIR >Minimum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >UARFCN >Cell Parameter ID >Sync Case >SCH Time Slot >SCTD Indicator >PCCPCH Power >Timing Advance Applied >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info TDD >UL CCTrCH Information >>CCTrCH ID >>UL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information >>Uplink SIR Target CCTrCH >DL CCTrCH Information >>CCTrCH ID >>DL DPCH Information >>>Repetition Period

M O M O O M M M M M M O O O C-Case2 O M M M M M O 0..<maxno ofCCTrCH s> M 0..1 M M M M O 0..<maxno ofCCTrCH s> M 0..1 M

Corresponds to Nt in TS 25.105 [7] For DCH GLOBAL YES YES For DCH GLOBAL YES ignore

9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.13C Uplink SIR 9.2.1.69

ignore

ignore ignore

9.2.3.2 9.2.3.7

ignore

3GPP

Release 11

289

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information >>CCTrCH Maximum DL TX Power >>CCTrCH Minimum DL TX Power >DCH Information Response >DSCH Information Response >>DSCH ID >>DSCH Flow Control Information >>Binding ID >>Transport Layer Address >>Transport Format Management >USCH Information Response >>USCH ID >>Binding ID >>Transport Layer Address >>Transport Format Management >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >Cell GA Additional Shapes >HCS Prio >Time Slot for SCH >Neighbouring E-UTRA Cell Information >Neighbouring UMTS Cell Information Extension Uplink SIR Target Criticality Diagnostics RL Information Response LCR

Presence M M M O O O

Range

IE Type and Reference 9.2.3.6 9.2.3.8A 9.2.3.2C DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.16A

Semantics Description

Criticality

Assigned Criticality

Maximum allowed power on DPCH Minimum allowed power on DPCH

YES YES YES GLOBAL

ignore ignore ignore ignore

0 .. <maxnoof DSCHs> M M O O M 0 .. <maxnoof USCHs> M O O M O O O O C-Case1 O O M O 0..1 9.2.3.14 9.2.1.3 9.2.1.62 9.2.3.13 9.2.1.41A 9.2.1.41C 9.2.1.5B 9.2.1.30N Time Slot 9.2.1.56 9.2.1.41De 9.2.1.141 Uplink SIR 9.2.1.69 9.2.1.13 Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD 9.2.1.49 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.3.13H 9.2.3.3ae 9.2.3.3ag 9.2.1.3 9.2.1.62 9.2.3.13

GLOBAL YES YES YES YES YES YES YES YES ignore ignore ignore ignore ignore ignore ignore ignore ignore

>RL ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >UL Time Slot ISCP Info LCR

M M M O O M

3GPP

Release 11

290

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >Maximum Uplink SIR >Minimum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >UARFCN >Cell Parameter ID >SCTD Indicator >PCCPCH Power >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info TDD LCR >UL CCTrCH Information LCR >>CCTrCH ID >>UL DPCH Information LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information LCR >>Uplink SIR Target CCTrCH >DL CCTrCH Information LCR >>CCTrCH ID >>DL DPCH Information LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information LCR >>>TSTD Indicator >DCH Information Response >DSCH Information Response LCR >>DSCH ID >>DSCH Flow Control Information >>Binding ID >>Transport Layer Address >>Transport Format Management

Presence M M M M M O O O M M M M O

Range

IE Type and Reference Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.66 9.2.1.8 9.2.1.78 9.2.1.43 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.7F

Semantics Description

Criticality

Assigned Criticality

Corresponds to Nt in TS 25.105 [7]

0..<maxno ofCCTrCH sLCR> M 0..1 M M M M O 0..<maxno ofCCTrCH sLCR> M 0..1 M M M M M O 0 .. <maxnoof DSCHsLC R> M M O O M 9.2.3.3ae 9.2.3.3ag 9.2.1.3 9.2.1.62 9.2.3.13 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.2E 9.2.3.13E 9.2.1.16A 9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.13G Uplink SIR 9.2.1.69 9.2.3.2

For DCH

GLOBAL YES YES

ignore

ignore

ignore ignore

For DCH

GLOBAL YES YES GLOBAL

ignore

ignore ignore

3GPP

Release 11

291

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >USCH Information Response LCR >>USCH ID >>Binding ID >>Transport Layer Address >>Transport Format Management >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >HCS Prio >Cell GA Additional Shapes >Uplink Timing Advance Control LCR >PowerControl GAP

Presence

Range 0 .. <maxnoof USCHsLC R>

IE Type and Reference

Semantics Description

Criticality GLOBAL

Assigned Criticality ignore

M O O M O O O O M O

9.2.3.14 9.2.1.3 9.2.1.62 9.2.3.13 9.2.1.41A 9.2.1.41C 9.2.1.30N 9.2.1.5B 9.2.3.13K INTEGER (1..255) Unit: umber of subframes Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only TDD only

YES YES YES YES ignore ignore ignore ignore

>SixtyfourQAM DL Support Indicator >Neighbouring E-UTRA Cell Information >Idle Interval Information >Neighbouring UMTS Cell Information Extension HS-DSCH-RNTI HS-DSCH Information Response

O O O O O O

9.2.1.123 9.2.1.41De 9.2.3.60 9.2.1.141 9.2.1.30P HS-DSCH TDD Information Response 9.2.3.3ab 9.2.3.3ah 0..<maxno ofActiveM BMS>

YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore

DSCH-RNTI Active MBMS Bearer Service List >TMGI >Transmission Mode >Preferred Frequency Layer RL Information Response 7.68Mcps

YES GLOBAL Mandatory for 7.68Mcps TDD , not applicable to 1.28Mcps TDD or 3.84Mcps TDD YES

ignore ignore

M O O 0..1

9.2.1.80 9.2.1.81 UARFCN 9.2.1.66

ignore

>RL ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >UL Time Slot ISCP Info >Maximum Uplink SIR

M O M O O M M

9.2.1.49 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.3.13D Uplink SIR 9.2.1.69

3GPP

Release 11

292

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >Minimum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >UARFCN >Cell Parameter ID >Sync Case >SCH Time Slot >SCTD Indicator >PCCPCH Power >Timing Advance Applied >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info 7.68Mcps TDD >UL CCTrCH Information 7.68 Mcps >>CCTrCH ID >>UL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information 7.68Mcps >>Uplink SIR Target CCTrCH >DL CCTrCH Information 7.68 Mcps >>CCTrCH ID >>DL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information 7.68Mcps >>CCTrCH Maximum DL TX Power >>CCTrCH Minimum DL TX Power >DCH Information Response >DSCH Information Response 7.68 Mcps >>DSCH ID >>DSCH Flow Control Information >>Binding ID >>Transport Layer Address

Presence M M M M O O O C-Case2 O M M M M M O

Range

IE Type and Reference Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A UARFCN 9.2.1.66 9.2.1.8 9.2.1.54 9.2.1.51 9.2.1.78 9.2.1.43 9.2.3.12A 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.22

Semantics Description

Criticality

Assigned Criticality

Corresponds to Nt in TS 25.105 [7]

0..<maxno ofCCTrCH s> M 0..1 M M M M O 0..<maxno ofCCTrCH s> M 0..1 M M M M O O O 0 .. <maxnoof DSCHs> M M O O 9.2.3.3ae 9.2.3.3ag 9.2.1.3 9.2.1.62 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.28 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.16A 9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.26 Uplink SIR 9.2.1.69 9.2.3.2

For DCH

GLOBAL YES

ignore

ignore

For DCH

GLOBAL YES

ignore

ignore

Maximum allowed power on DPCH Minimum allowed power on DPCH

YES GLOBAL ignore ignore

3GPP

Release 11

293

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>Transport Format Management >USCH Information Response 7.68 Mcps >>USCH ID >>Binding ID >>Transport Layer Address >>Transport Format Management >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >Cell GA Additional Shapes >HCS Prio >Time Slot for SCH >Neighbouring E-UTRA Cell Information >Neighbouring UMTS Cell Information Extension E-DCH Information Response

Presence M

Range

IE Type and Reference 9.2.3.13

Semantics Description

Criticality GLOBAL

Assigned Criticality

0 .. <maxnoof USCHs> M O O M O O O O C-Case1 O O O 9.2.3.14 9.2.1.3 9.2.1.62 9.2.3.13 9.2.1.41A 9.2.1.41C 9.2.1.5B 9.2.1.30N Time Slot 9.2.1.56 9.2.1.41De 9.2.1.141 E-DCH TDD Information Response 9.2.3.41 E-DCH TDD Information Response 7.68Mcps 9.2.3.52 E-DCH TDD Information Response 1.28Mcps 9.2.3.41a 9.2.3.63 9.2.3.68 9.2.3.69 E-RNTI 9.2.1.94 HS-DSCHRNTI 9.2.1.30P 9.2.3.75 9.2.3.78 9.2.3.81 3.84Mcps TDD only

ignore

YES YES YES ignore ignore ignore

E-DCH Information Response 7.68Mcps

7.68Mcps TDD only

YES

ignore

E-DCH Information Response 1.28Mcps

1.28Mcps TDD only

YES

ignore

Continuous Packet Connectivity DRX Information Response LCR HS-DSCH Semi-Persistent scheduling Information Response LCR E-DCH Semi-Persistent scheduling Information Response LCR E-RNTI for FACH H-RNTI for FACH DCH Measurement Occasion Information Multi-Carrier E-DCH Information Response LCR MU-MIMO Information

O O O O O O O O

1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only

YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore reject ignore reject

3GPP

Release 11

294

3GPP TS 25.423 V11.2.0 (2012-06)

Condition Case2 Case1 Range bound maxnoofDSCHs maxnoofUSCHs maxnoofCCTrCHs maxnoofDSCHsLCR maxnoofUSCHsLCR maxnoofCCTrCHsLCR maxnoofActiveMBMS

Explanation The IE shall be present if Sync Case IE is equal to Case2. This IE shall be present if Sync Case IE is equal to Case1. Explanation Maximum number of DSCHs for one UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of USCHs for one UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of CCTrCH for one UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of DSCHs for one UE for 1.28Mcps TDD. Maximum number of USCHs for one UE for 1.28Mcps TDD. Maximum number of CCTrCH for one UE for 1.28Mcps TDD. Maximum number of MBMS bearer services that are active in parallel.

3GPP

Release 11

295

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.5 RADIO LINK SETUP FAILURE

9.1.5.1 FDD Message

3GPP

Release 11

296

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID D-RNTI CN PS Domain Identifier CN CS Domain Identifier CHOICE Cause Level >General >>Cause >RL Specific >>Unsuccessful RL Information Response >>>RL ID >>>Cause >>>Max UE DTX Cycle >>Successful RL Information Response >>>RL ID >>>RL Set ID >>>URA Information >>>SAI >>>Cell GAI >>>UTRAN Access Point Position >>>Received Total Wide Band Power >>>Not Used >>>DL Code Information

Presence M M O O O M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.12 9.2.1.11

Semantics Description

Criticality YES YES YES YES YES EACH YES EACH

Assigned Criticality reject ignore ignore ignore ignore

9.2.1.5 1..<maxno ofRLs>

ignore

M M C-DTXCycleNotA vailable 0..<maxno ofRLs-1> M M O M O O M O M

9.2.1.49 9.2.1.5 9.2.2.87

ignore ignore

9.2.1.49 9.2.2.35 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.2.35A NULL FDD DL Code Information 9.2.2.14A

>>>CHOICE Diversity Indication >>>>Combining >>>>>RL ID >>>>>DCH Information Response >>>>>E-DCH FDD Information Response >>>>Non Combining or First RL >>>>>DCH Information Response >>>>>E-DCH FDD Information Response >>>SSDT Support Indicator >>>Maximum Uplink SIR >>>Minimum Uplink SIR >>>Closed Loop Timing Adjustment Mode >>>Maximum Allowed UL Tx Power >>>Maximum DL TX Power >>>Minimum DL TX Power

M M O O 9.2.1.49 9.2.1.16A 9.2.2.4C Reference RL ID for the combining

YES YES ignore ignore

M O M M M O M M M

9.2.1.16A 9.2.2.4C 9.2.2.43 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.2.3A 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A

YES ignore

3GPP

Release 11

297

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>Primary CPICH Power >>>Primary Scrambling Code >>>UL UARFCN

Presence M O O

Range

IE Type and Reference 9.2.1.44 9.2.1.45 UARFCN 9.2.1.66 UARFCN 9.2.1.66 NULL 9.2.1.41A 9.2.1.41C 9.2.2.27a 9.2.2.39A 9.2.1.5B 9.2.2.10B 9.2.1.30N 9.2.2.32A 9.2.2.38A

Semantics Description

Criticality

Assigned Criticality

Corresponds to Nu in TS 25.104 [6] Corresponds to Nd in TS 25.104 [6]

>>>DL UARFCN >>>Not Used >>>Neighbouring UMTS Cell Information >>>Neighbouring GSM Cell Information >>>PC Preamble >>>SRB Delay >>>Cell GA Additional Shapes >>>DL Power Balancing Activation Indicator >>>HCS Prio >>>Primary CPICH Usage For Channel Estimation >>>Secondary CPICH Information >>>Active MBMS Bearer Service List >>>>TMGI >>>>Transmission Mode >>>>Preferred Frequency Layer >>>E-DCH RL Set ID >>>E-DCH FDD DL Control Channel Information >>>Initial DL DPCH Timing Adjustment >>>Neighbouring EUTRA Cell Information >>> HS-DSCH Preconfiguration Info >>>F-DPCH Slot Format >>>Non-Serving RL Preconfiguration Info >>>Neighbouring UMTS Cell Information Extension >>HS-DSCH-RNTI >>HS-DSCH Information Response

O O O O M M O O O O O 0..<maxno ofActiveM BMS> M O O O O O

YES YES YES YES YES GLOBAL

ignore ignore ignore ignore ignore ignore

9.2.1.80 9.2.1.81 UARFCN 9.2.1.66 RL Set ID 9.2.2.35 9.2.2.4D DL DPCH Timing Adjustment 9.2.2.9A 9.2.1.41De 9.2.2.99 9.2.2.85 9.2.2.125 9.2.1.141 9.2.1.30P HS-DSCH FDD Information Response 9.2.2.19b

YES YES YES ignore ignore ignore

O O O O O O O

YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore

3GPP

Release 11

298

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>Continuous Packet Connectivity HS-SCCH less Information Response >>SixtyfourQAM DL Support Indicator >>Additional HS Cell Information Response

Presence O O O

Range

IE Type and Reference 9.2.2.75 9.2.1.123

Semantics Description

Criticality YES YES

Assigned Criticality ignore ignore ignore

0..<maxno ofHSDSC H-1>

For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.1.30P 9.2.2.19ba 9.2.1.123

EACH

>>>HS-PDSCH RL ID >>>HS-DSCH-RNTI >>>HS-DSCH FDD Secondary Serving Information Response >>>SixtyfourQAM DL Support Indicator >>Additional E-DCH Cell Information Response

M M M O 0..<maxno ofEDCH1>

E-DCH on Secondary uplink frequency max 1 in this 3GPP release. EACH ignore

>>>Additional E-DCH FDD Information Response Uplink SIR Target Criticality Diagnostics Condition DTX-CycleNotAvailable

M O O

9.2.2.120 Uplink SIR 9.2.1.69 9.2.1.13

YES YES ignore ignore

Explanation The IE shall be present if the Cause IE is set to Continuous Packet Connectivity UE DTX Cycle not Available . Explanation Maximum number of RLs for one UE. Maximum number of MBMS bearer services that are active in parallel. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

Range bound maxnoofRLs maxnoofActiveMBMS maxnoofHSDSCH-1 maxnoofEDCH-1

3GPP

Release 11

299

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.5.2

TDD Message
Presence M M M M 1 M M O O 9.2.1.49 9.2.1.5 9.2.1.123 9.2.1.13 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 Semantics Description Criticality YES YES YES YES YES Assigned Criticality reject ignore

IE/Group Name Message Type Transaction ID CHOICE Cause Level >General >>Cause >RL Specific >>Unsuccessful RL Information Response >>>RL ID >>>Cause >>SixtyfourQAM DL Support Indicator Criticality Diagnostics

ignore

ignore ignore

3GPP

Release 11

300

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.6 RADIO LINK ADDITION REQUEST

9.1.6.1 FDD Message

3GPP

Release 11

301

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Uplink SIR Target RL Information >RL ID >C-ID >Frame Offset >Chip Offset >Diversity Control Field >Primary CPICH Ec/No >Not Used >Transmit Diversity Indicator >DL Reference Power >Enhanced Primary CPICH Ec/No >RL Specific DCH Information >Delayed Activation >RL specific E-DCH Information >E-DCH RL Indication >Synchronisation Indicator >HS-DSCH Preconfiguration Setup >Non-Serving RL Preconfiguration Setup >F-TPICH Information Active Pattern Sequence Information

Presence M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 Uplink SIR 9.2.1.69

Semantics Description

Criticality YES YES EACH

Assigned Criticality reject reject notify

1..<max noofRLs1> M M M M M O O O O O O O O O O O O O O 9.2.1.49 9.2.1.6 9.2.1.30 9.2.2.1 9.2.1.20 9.2.2.32 NULL 9.2.2.48 DL Power 9.2.1.21A 9.2.2.13I 9.2.1.49A 9.2.1.19Aa 9.2.2.35a 9.2.2.4E 9.2.2.45A 9.2.2.100 9.2.2.124 9.2.2.139 9.2.2A Either all the already active Transmissio n Gap Sequence(s) are addressed (Transmissio n Gap Pattern sequence shall overlap with the existing one) or none of the transmission gap sequences is activated.

Power on DPCH or on F-DPCH

YES YES YES YES YES YES YES YES YES YES YES

ignore ignore ignore reject reject reject ignore Ignore Ignore ignore reject

DPC Mode Permanent NAS UE Identity Serving E-DCH RL Initial DL DPCH Timing Adjustment Allowed HS-DSCH Serving Cell Change Information Serving Cell Change CFN E-DPCH Information

O O O O O O 0..1

9.2.2.12A 9.2.1.73 9.2.2.38C 9.2.2.21b 9.2.2.19f CFN 9.2.1.9

YES YES YES YES YES YES YES

reject ignore reject ignore reject reject reject

3GPP

Release 11

302

3GPP TS 25.423 V11.2.0 (2012-06)

>Maximum Set of EDPDCHs >Puncture Limit >E-TFCS Information >E-TTI >E-DPCCH Power Offset >E-RGCH 2-Index-Step Threshold >E-RGCH 3-Index-Step Threshold >HARQ Info for E-DCH >HS-DSCH Configured Indicator > Minimum Reduced EDPDCH Gain Factor E-DCH FDD Information Additional HS Cell Information RL Addition

M M M M M M M M M O CEDCHInfo 0..<max noofHSD SCH-1>

9.2.2.24e 9.2.1.46 9.2.2.4G 9.2.2.4J 9.2.2.4K 9.2.2.64 9.2.2.65 9.2.2.66 9.2.2.19C 9.2.2.102 9.2.2.4B For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.1.6 9.2.2.19aa 9.2.1.137 0..1 For E-DCH on multiple frequencies in this DRNS.

YES YES YES EACH reject ignore reject reject

>HS-PDSCH RL ID >C-ID >HS-DSCH FDD Secondary Serving Information UE Aggregate Maximum Bit Rate Additional E-DCH Cell Information RL Add Req

M M M O

YES YES ignore reject

>CHOICE Setup Or Addition Of E-DCH On Secondary UL Frequency >> Setup

M Used when the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context M 1..<max noofEDC H-1> 9.2.2.113 E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.110 Used when there exist additional E-

YES

reject

>>>Multicell E-DCH Transport Bearer Mode >>>Additional E-DCH Cell Information Setup

>>>> Additional EDCH FDD Setup Information >> Addition

3GPP

Release 11

303

3GPP TS 25.423 V11.2.0 (2012-06)

>>>Additional E-DCH Cell Information Addition

1..<max noofEDC H-1>

DCH RLs in the current UE context E-DCH on Secondary uplink frequency max 1 in this 3GPP release. Uplink SIR 9.2.1.69 9.2.2.116 9.2.2.112 9.2.2.114 9.2.2.131

>>>>UL DPCH Information >>>>> Uplink SIR Target >>>> Additional E-DCH RL Specific Information To Add >>>> Additional E-DCH FDD Information >>>> Multicell E-DCH Information UL CLTD Information Condition EDCHInfo

1 M M O O O

YES YES ignore reject

Explanation This IE shall be present if E-DPCH Information IE is present. Explanation Maximum number of radio links for one UE. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

Range bound maxnoofRLs maxnoofHSDSCH-1 maxnoofEDCH-1

3GPP

Release 11

304

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.6.2

TDD Message

3GPP

Release 11

305

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information >RL ID >C-ID >Frame Offset >Diversity Control Field >Primary CCPCH RSCP >DL Time Slot ISCP Info

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49 9.2.1.6 9.2.1.30 9.2.1.20 9.2.3.5 9.2.3.2D

Semantics Description

Criticality YES YES

Assigned Criticality reject reject

1 M M M M O O

>DL Time Slot ISCP Info LCR >RL Specific DCH Information >Delayed Activation >UL Synchronisation Parameters LCR

O O O 0..1

9.2.3.2F 9.2.1.49A 9.2.1.19Aa

Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Applicable to 1.28Mcps TDD only

YES YES

reject ignore reject reject

Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. 9.2.3.13J 9.2.3.13I 9.2.3.5a NULL 9.2.1.73 TDD only

YES YES

>>Uplink Synchronisation Step Size >>Uplink Synchronisation Frequency > Primary CCPCH RSCP Delta > Idle Interval Configuration Indicator Permanent NAS UE Identity UL CCTrCH Information

M M O O O 0..< maxno ofCCTr CHs > M O 0..< maxno ofCCTr CHs > M O O

YES YES YES EACH ignore ignore ignore notify

>CCTrCH ID >TDD TPC Uplink Step Size DL CCTrCH Information

9.2.3.2 9.2.3.10a

Applicable to 1.28Mcps TDD only

EACH notify

>CCTrCH ID >TDD TPC Downlink Step Size HS-DSCH Information

9.2.3.2 9.2.3.10 HS-DSCH TDD Information 9.2.3.3aa RL ID 9.2.1.49 0..1 3.84Mcps TDD only 9.2.3.36 9.2.3.37

YES reject

HS-PDSCH RL ID E-DCH Information >E-PUCH Information >E-TFCS Information TDD

YES YES

reject reject

M M

3GPP

Release 11

306

3GPP TS 25.423 V11.2.0 (2012-06)

>E-DCH MAC-d Flows Information TDD >E-DCH TDD Information E-DCH Serving RL E-DCH Information 7.68Mcps >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows Information TDD >E-DCH TDD Information 7.68Mcps E-DCH Information 1.28Mcps >E-PUCH Information LCR >E-TFCS Information TDD >E-DCH MAC-d Flows Information TDD >E-DCH TDD Information LCR Continuous Packet Connectivity DRX Information LCR HS-DSCH Semi-Persistent scheduling Information LCR E-DCH Semi-Persistent scheduling Information LCR DCH Measurement Type indicator Multi-Carrier E-DCH Information

M M O 0..1 M M M M 0..1 M M M M O O O O 0..1

9.2.3.38 9.2.3.40 9.2.1.49 3.84Mcps TDD only 7.68Mcps TDD only

YES YES 1.28Mcps TDD only YES 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only Applicable for MultiCarrier EDCH Operation in 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only YES YES YES YES YES reject reject reject reject reject reject reject reject

9.2.3.36 9.2.3.37 9.2.3.38 9.2.3.51

9.2.3.36a 9.2.3.37 9.2.3.38 9.2.3.40a 9.2.3.61 9.2.3.64 9.2.3.66 9.2.3.76

>Multi-Carrier E-DCH Transport Bearer Mode LCR >Multi-Carrier E-DCH Information LCR MU-MIMO Indicator

M M O

9.2.3.79 9.2.3.77 9.2.3.82

YES reject

Range bound maxnoofCCTrCHs

Explanation Maximum number of CCTrCH for one UE.

3GPP

Release 11

307

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.7 RADIO LINK ADDITION RESPONSE

9.1.7.1 FDD Message

3GPP

Release 11

308

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response >RL ID >RL Set ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >Received Total Wide Band Power >Not Used >DL Code Information

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49 9.2.2.35 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.2.35A NULL FDD DL Code Information 9.2.2.14A

Semantics Description

Criticality YES EACH YES

Assigned Criticality reject ignore

1..<maxnoof RLs-1> M M O M O O M O M

ignore

>CHOICE Diversity Indication >>Combining >>>RL ID >>>DCH Information Response >>>E-DCH FDD Information Response >>Non Combining >>>DCH Information Response >>>E-DCH FDD Information Response >SSDT Support Indicator >Minimum Uplink SIR >Maximum Uplink SIR >Closed Loop Timing Adjustment Mode >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >PC Preamble >SRB Delay >Primary CPICH Power >Cell GA Additional Shapes >DL Power Balancing Activation Indicator >HCS Prio >Active MBMS Bearer Service List >>TMGI >>Transmission Mode

M M O O M O M M M O M M M O O M M M O O O 0..<maxnoof ActiveMBM S> M O 9.2.1.80 9.2.1.81 9.2.1.49 9.2.1.16A 9.2.2.4C 9.2.1.16A 9.2.2.4C 9.2.2.43 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.2.3A 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.41A 9.2.1.41C 9.2.2.27a 9.2.2.39A 9.2.1.44 9.2.1.5B 9.2.2.10B 9.2.1.30N Reference RL ID

YES YES YES YES YES YES GLOBAL ignore ignore ignore

ignore ignore ignore ignore

3GPP

Release 11

309

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>Preferred Frequency Layer >E-DCH RL Set ID >E-DCH FDD DL Control Channel Information >Initial DL DPCH Timing Adjustment >F-DPCH Slot Format >Neighbouring E-UTRA Cell Information >HS-DSCH Preconfiguration Info >Non-Serving RL Preconfiguration Info >Neighbouring UMTS Cell Information Extension Criticality Diagnostics HS-DSCH Serving Cell Change Information Response E-DCH Serving Cell Change Information Response MAC-hs Reset Indicator Additional HS Cell Change Information Response

Presence O O O O

Range

IE Type and Reference UARFCN 9.2.1.66 RL Set ID 9.2.2.35 9.2.2.4D DL DPCH Timing Adjustment 9.2.2.9.A 9.2.2.85 9.2.1.41De 9.2.2.99 9.2.2.125 9.2.1.141 9.2.1.13 9.2.2.19g 9.2.2.19h 9.2.1.34B

Semantics Description

Criticality YES YES YES

Assigned Criticality

ignore ignore ignore

O O O O O O O O O 0..<maxnoof HSDSCH1>

YES YES YES YES YES YES YES YES For secondary serving HSDSCH cell. Max 7 in this 3GPP release. YES EACH

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

>HS-PDSCH RL ID >HS-DSCH Secondary Serving Cell Change Information Response Additional E-DCH Cell Information Response RL Add

M M 0..<maxnoof EDCH-1>

RL ID 9.2.1.49 9.2.2.19ga E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.120 E-DCH Serving Cell Change Information Response 9.2.2.19h

EACH ignore

>Additional E-DCH FDD Information Response >Additional E-DCH Serving Cell Change Information response

O O

3GPP

Release 11

310

3GPP TS 25.423 V11.2.0 (2012-06)

Range bound maxnoofRLs maxnoofActiveMBMS maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of radio links for one UE. Maximum number of MBMS bearer services that are active in parallel. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

311

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.7.2

TDD Message

3GPP

Release 11

312

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59

Semantics Description

Criticality YES YES

Assigned Criticality reject ignore

0..1

Mandatory for 3.84Mcps TDD, not applicable to 1.28Mcps TDD or 7.68Mcps TDD 9.2.1.49 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.3.13D Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.43 9.2.3.12A 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.7B

>RL ID >URA Information >SAI >Cell GAI >UTRAN Access Point Position >UL Time Slot ISCP Info >Minimum Uplink SIR >Maximum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >PCCPCH Power >Timing Advance Applied >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info TDD >UL CCTrCH Information >>CCTrCH ID >>UL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information >DL CCTrCH Information >>CCTrCH ID >>DL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information >>CCTrCH Maximum DL TX Power >>CCTrCH Minimum DL TX Power

M O M O O M M M M M M M M M M M O 0..<maxnoof CCTrCHs> M 0..1 M M M M 0..<maxnoof CCTrCHs> M 0..1 M M M M O

For DCH GLOBAL YES For DCH GLOBAL YES Maximum allowed power on DPCH Minimum allowed power on DPCH YES ignore ignore ignore ignore ignore

9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.13C

9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.2C DL Power 9.2.1.21A DL Power 9.2.1.21A

YES

ignore

3GPP

Release 11

313

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >DCH Information >>CHOICE Diversity Indication >>>Combining >>>>RL ID >>>>DCH Information Response >>>Non Combining >>>>DCH Information Response >DSCH Information Response >>DSCH ID >>Transport Format Management >>DSCH Flow Control Information >>CHOICE Diversity Indication >>>Non Combining >>>>Binding ID >>>>Transport Layer Address >USCH Information Response >>USCH ID >>Transport Format Management >>CHOICE Diversity Indication >>>Non Combining >>>>Binding ID >>>>Transport Layer Address >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >Cell GA Additional Shapes >HCS Prio >Neighbouring E-UTRA Cell Information >Neighbouring UMTS Cell Information Extension Criticality Diagnostics RL Information Response LCR

Presence

Range 0..1

IE Type and Reference

Semantics Description

Criticality

Assigned Criticality

M M O 9.2.1.49 9.2.1.16A Reference RL

YES GLOBAL ignore ignore

M 0 .. <maxnoof DSCHs> M M M O O O 0 .. <maxnoof USCHs> M M O O O O O O O O O O 0..1

9.2.1.16A

9.2.3.3ae 9.2.3.13 9.2.3.3ag

9.2.1.3 9.2.1.62

GLOBAL ignore

9.2.3.14 9.2.3.13

9.2.1.3 9.2.1.62 9.2.1.41A 9.2.1.41C 9.2.1.5B 9.2.1.30N 9.2.1.41De 9.2.1.141 9.2.1.13 Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD 9.2.1.49 9.2.1.70B 9.2.1.52 9.2.1.5A

YES YES YES YES YES YES ignore ignore ignore ignore ignore ignore

>RL ID >URA Information >SAI >Cell GAI

M M M O

3GPP

Release 11

314

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >UTRAN Access Point Position >UL Time Slot ISCP Info LCR >Maximum Uplink SIR >Minimum Uplink SIR >PCCPCH Power >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info TDD LCR >UL CCTrCH Information LCR >>CCTrCH ID >>UL DPCH Information LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information LCR >DL CCTrCH Information LCR >>CCTrCH ID >>DL DPCH Information LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information LCR >>>TSTD Indicator >DCH Information Response >DSCH Information Response LCR >>DSCH ID >>DSCH Flow Control Information >>Binding ID >>Transport Layer Address >>Transport Format Management >USCH Information Response LCR >>USCH ID

Presence O M M M M M M M M M M O

Range

IE Type and Reference 9.2.1.70A 9.2.3.13H Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.43 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.7F

Semantics Description

Criticality

Assigned Criticality

0..<maxnoof CCTrCHsL CR> M 0..1 M M M M 0..<maxnoof CCTrCHsL CR> M 0..1 M M M M M M 0 .. <maxnoof DSCHsLCR > M M O O M 0 .. <maxnoof USCHsLCR > M 9.2.3.14 9.2.3.3ae 9.2.3.3ag 9.2.1.3 9.2.1.62 9.2.3.13 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.2E 9.2.3.13E 9.2.1.16A 9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.13G 9.2.3.2

For DCH

GLOBAL YES

ignore

ignore

For DCH

GLOBAL YES GLOBAL

ignore

ignore

ignore

GLOBAL ignore

3GPP

Release 11

315

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>Transport Format Management >>CHOICE Diversity Indication >>>Non Combining >>>>Binding ID >>>>Transport Layer Address >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >Cell GA Additional Shapes >HCS Prio >Uplink Timing Advance Control LCR >PowerControl GAP

Presence M O O O O O O O M O

Range

IE Type and Reference 9.2.3.13

Semantics Description

Criticality

Assigned Criticality

9.2.1.3 9.2.1.62 9.2.1.41A 9.2.1.41C 9.2.1.5B 9.2.1.30N 9.2.3.13K INTEGER (1..255) Unit: number of subframes Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only. Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt 3GPP TS 25.105. TDD only

YES YES YES YES ignore ignore ignore ignore

>UARFCN

9.2.1.66

YES

ignore

>Neighbouring E-UTRA Cell Information >Idle Interval Information >Neighbouring UMTS Cell Information Extension Active MBMS Bearer Service List >TMGI >Transmission Mode >Preferred Frequency Layer HS-DSCH Information Response

O O O 0..<maxnoo fActiveMBM S> M O O O

9.2.1.41De 9.2.3.60 9.2.1.141

YES YES YES GLOBAL

ignore ignore ignore ignore

HS-DSCH-RNTI RL Information Response 7.68Mcps

O 0..1

9.2.1.80 9.2.1.81 UARFCN 9.2.1.66 HS-DSCH TDD Information Response 9.2.3.3ab 9.2.1.30P Mandatory for 7.68Mcps TDD, not applicable to 1.28Mcps TDD or 3.84Mcps TDD 9.2.1.49 9.2.1.70B

YES ignore

YES YES

ignore ignore

>RL ID >URA Information

M O

3GPP

Release 11

316

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >SAI >Cell GAI >UTRAN Access Point Position >UL Time Slot ISCP Info >Minimum Uplink SIR >Maximum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >PCCPCH Power >Timing Advance Applied >Alpha Value >UL PhysCH SF Variation >Synchronisation Configuration >Secondary CCPCH Info 7.68Mcps TDD >UL CCTrCH Information 7.68 Mcps >>CCTrCH ID >>UL DPCH Information 7.68 Mcps >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information 7.68Mcps >DL CCTrCH Information 7.68 Mcps >>CCTrCH ID >>DL DPCH Information 7.68 Mcps >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information 7.68Mcps >>CCTrCH Maximum DL TX Power >>CCTrCH Minimum DL TX Power >DCH Information >>CHOICE Diversity Indication >>>Combining >>>>RL ID >>>>DCH Information Response >>>Non Combining

Presence M O O M M M M M M M M M M M O

Range

IE Type and Reference 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.3.13D Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.43 9.2.3.12A 9.2.3.a 9.2.3.13B 9.2.3.7E 9.2.3.22

Semantics Description

Criticality

Assigned Criticality

0..<maxnoof CCTrCHs> M 0..1 M M M M 0..<maxnoof CCTrCHs> M 0..1 M M M M O 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.28 DL Power 9.2.1.21A DL Power 9.2.1.21A 0..1 M M O 9.2.1.49 9.2.1.16A 9.2.3.2 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.26 9.2.3.2

For DCH

GLOBAL YES

ignore ignore

For DCH

GLOBAL YES

ignore ignore

Maximum allowed power on DPCH Minimum allowed power on DPCH

Reference RL YES ignore

3GPP

Release 11

317

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>>DCH Information Response >DSCH Information Response 7.68 Mcps >>DSCH ID >>Transport Format Management >>DSCH Flow Control Information >>CHOICE Diversity Indication >>>Non Combining >>>>Binding ID >>>>Transport Layer Address >USCH Information Response 7.68 Mcps >>USCH ID >>Transport Format Management >>CHOICE Diversity Indication >>>Non Combining >>>>Binding ID >>>>Transport Layer Address >Neighbouring UMTS Cell Information >Neighbouring GSM Cell Information >Cell GA Additional Shapes >HCS Prio >Neighbouring E-UTRA Cell Information >Neighbouring UMTS Cell Information Extension E-DCH Information Response

Presence M

Range

IE Type and Reference 9.2.1.16A

Semantics Description

Criticality GLOBAL

Assigned Criticality

0 .. <maxnoof DSCHs> M M M O O O 0 .. <maxnoof USCHs> M M O O O O O O O O O O 9.2.1.3 9.2.1.62 9.2.1.41A 9.2.1.41C 9.2.1.5B 9.2.1.30N 9.2.1.41De 9.2.1.141 E-DCH TDD Information Response 9.2.3.41 E-DCH TDD Information Response 7.68Mcps 9.2.3.52 E-DCH TDD Information Response 1.28Mcps 9.2.3.41a 9.2.3.63 9.2.3.68 3.84Mcps TDD only 9.2.3.14 9.2.3.13 9.2.1.3 9.2.1.62 9.2.3.3ae 9.2.3.13 9.2.3.3ag

ignore

GLOBAL YES YES YES ignore ignore ignore ignore

E-DCH Information Response 7.68Mcps

7.68Mcps TDD only

YES

ignore

E-DCH Information Response 1.28Mcps

1.28Mcps TDD only

YES

ignore

Continuous Packet Connectivity DRX Information Response LCR HS-DSCH Semi-Persistent scheduling Information Response LCR

O O

1.28 Mcps TDD only 1.28 Mcps TDD only

YES YES

ignore ignore

3GPP

Release 11

318

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name E-DCH Semi-Persistent scheduling Information Response LCR DCH Measurement Occasion Information Multi-Carrier E-DCH Information Response LCR MU-MIMO Information

Presence O O O O

Range

IE Type and Reference 9.2.3.69 9.2.3.75 9.2.3.78 9.2.3.81

Semantics Description 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only

Criticality YES YES YES YES

Assigned Criticality ignore reject ignore reject

Range Bound maxnoofDSCHs maxnoofUSCHs maxnoofCCTrCHs maxnoofDSCHsLCR maxnoofUSCHsLCR maxnoofCCTrCHsLCR maxnoofActiveMBMS

Explanation Maximum number of DSCHs for one UE for 3.84Mcps TDD. Maximum number of USCHs for one UE for 3.84Mcps TDD. Maximum number of CCTrCHs for one UE for 3.84Mcps TDD. Maximum number of DSCHs for one UE for 1.28Mcps TDD. Maximum number of USCHs for one UE for 1.28Mcps TDD. Maximum number of CCTrCH for one UE for 1.28Mcps TDD. Maximum number of MBMS bearer services that are active in parallel.

3GPP

Release 11

319

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.8 RADIO LINK ADDITION FAILURE

9.1.8.1 FDD Message

3GPP

Release 11

320

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID CHOICE Cause Level >General >>Cause >RL Specific >>Unsuccessful RL Information Response >>>RL ID >>>Cause >>Successful RL Information Response >>>RL ID >>>RL Set ID >>>URA Information >>>SAI >>>Cell GAI >>>UTRAN Access Point Position >>>Received Total Wide Band Power >>>Not Used >>>DL Code Information >>>CHOICE Diversity Indication >>>>Combining >>>>>RL ID >>>>>DCH Information Response >>>>>E-DCH FDD Information Response >>>>Non Combining >>>>>DCH Information Response >>>>>E-DCH FDD Information Response >>>SSDT Support Indicator >>>Minimum Uplink SIR >>>Maximum Uplink SIR >>>Closed Loop Timing Adjustment Mode >>>Maximum Allowed UL Tx Power >>>Maximum DL TX Power >>>Minimum DL TX Power >>>Neighbouring UMTS Cell Information >>>Neighbouring GSM Cell Information

Presence M M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5

Semantics Description

Criticality YES YES EACH EACH YES

Assigned Criticality reject ignore

1..<maxnoof RLs-1> M M 0..<maxnoof RLs-2> M M O M O O M O M 9.2.1.49 9.2.2.35 9.2.1.70B 9.2.1.52 9.2.1.5A 9.2.1.70A 9.2.2.35A NULL FDD DL Code Information 9.2.2.14A 9.2.1.49 9.2.1.5

ignore

ignore

ignore

M M O O 9.2.1.49 9.2.1.16A 9.2.2.4C Reference RL ID

YES YES YES ignore ignore ignore

M O M M M O M M M O O

9.2.1.16A 9.2.2.4C 9.2.2.43 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.2.3A 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.41A 9.2.1.41C

3GPP

Release 11

321

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>Primary CPICH Power >>>PC Preamble >>>SRB Delay >>>Cell GA Additional Shapes >>>DL Power Balancing Activation Indicator >>>HCS Prio >>>Active MBMS Bearer Service List >>>>TMGI >>>>Transmission Mode >>>>Preferred Frequency Layer >>>E-DCH RL Set ID >>>E-DCH FDD DL Control Channel Information >>>Initial DL DPCH Timing Adjustment >>>Neighbouring EUTRA Cell Information >>>HS-DSCH Preconfiguration Info >>>F-DPCH Slot Format >>>Non-Serving RL Preconfiguration Info >>>Neighbouring UMTS Cell Information Extension Criticality Diagnostics HS-DSCH Serving Cell Change Information Response E-DCH Serving Cell Change Information Response Additional HS Cell Change Information Response

Presence M M M O O O

Range

IE Type and Reference 9.2.1.44 9.2.2.27a 9.2.2.39A 9.2.1.5B 9.2.2.10B 9.2.1.30N

Semantics Description

Criticality YES YES YES GLOBAL YES YES YES

Assigned Criticality

ignore ignore ignore ignore

0..<maxnoof ActiveMBM S> M O O O O O 9.2.1.80 9.2.1.81 UARFCN 9.2.1.66 RL Set ID 9.2.2.35 9.2.2.4D DL DPCH Timing Adjustment 9.2.2.9.A 9.2.1.41De 9.2.2.99 9.2.2.85 9.2.2.125 9.2.1.141 9.2.1.13 9.2.2.19g 9.2.2.19h 0..<maxnoof HSDSCH1> For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.2.19ga 9.2.1.34B

ignore ignore ignore

O O O O O O O O

YES YES YES YES YES YES YES YES EACH

ignore ignore ignore ignore ignore ignore Ignore Ignore Ignore

>HS-PDSCH RL ID >HS-DSCH Secondary Serving Cell Change Information Response MAC-hs Reset Indicator

M M O

YES ignore

3GPP

Release 11

322

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Additional E-DCH Cell Information Response RL Add

Presence

Range 0..<maxnoof EDCH-1>

IE Type and Reference

Semantics Description E-DCH on Secondary uplink frequency max 1 in this 3GPP release.

Criticality EACH

Assigned Criticality ignore

>Additional E-DCH FDD Information Response >Additional E-DCH Serving Cell Change Information response

O O

9.2.2.120 E-DCH Serving Cell Change Information Response 9.2.2.19h

Range bound maxnoofRLs maxnoofActiveMBMS maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of radio links for one UE. Maximum number of MBMS bearer services that are active in parallel. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.8.2

TDD Message
Presence M M M M 1 M M O 9.2.1.49 9.2.1.5 9.2.1.13 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES YES YES YES Assigned Criticality reject ignore

IE/Group Name Message Type Transaction ID CHOICE Cause Level >General >>Cause >RL Specific >>Unsuccessful RL Information Response >>>RL ID >>>Cause Criticality Diagnostics

9.2.1.5

ignore

ignore

9.1.9 RADIO LINK DELETION REQUEST

IE/Group Name Message Type Transaction ID RL Information >RL ID Presence M M 1..<maxno ofRLs> M Range bound maxnoofRLs 9.2.1.49 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES EACH Assigned Criticality reject notify

Explanation Maximum number of radio links for one UE

3GPP

Release 11

323

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.10 RADIO LINK DELETION RESPONSE

IE/Group Name Message Type Transaction ID Criticality Diagnostics Presence M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.13 Semantics Description Criticality YES YES Assigned Criticality reject ignore

3GPP

Release 11

324

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.11 RADIO LINK RECONFIGURATION PREPARE

9.1.11.1 FDD Message

3GPP

Release 11

325

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Allowed Queuing Time UL DPCH Information >UL Scrambling Code >UL SIR Target >Min UL Channelisation Code Length >Max Number of UL DPDCHs >Puncture Limit >TFCS >UL DPCCH Slot Format >Diversity Mode >Not Used >Not Used >UL DPDCH Indicator For E-DCH Operation DL DPCH Information >TFCS >DL DPCH Slot Format >Number of DL Channelisation Codes >TFCI Signalling Mode >TFCI Presence >Multiplexing Position >Limited Power Increase >DL DPCH Power Information >>Power Offset Information >>>PO1 >>>PO2 >>>PO3 >>FDD TPC Downlink Step Size >>Inner Loop DL PC Status DCHs To Modify DCHs To Add DCHs To Delete >DCH ID RL Information >RL ID >Not Used

Presence M M O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.2 9.2.2.53 Uplink SIR 9.2.1.69 9.2.2.25 9.2.2.24 9.2.1.46 9.2.1.63 9.2.2.52 9.2.2.8 NULL NULL 9.2.2.52A

Semantics Description

Criticality YES YES YES

Assigned Criticality reject reject reject

0..1 O O O C CodeLen O O O O O O O 0..1 O O O O CSlotFormat O O 0..1 1 M M M M M O O 0..<maxnoof DCHs> M 0..<maxnoof RLs> M O 9.2.1.49 NULL 9.2.1.16 Power Offset 9.2.2.30 Power Offset 9.2.2.30 Power Offset 9.2.2.30 9.2.2.16 9.2.2.21a FDD DCHs To Modify 9.2.2.13C DCH FDD Information 9.2.2.4A Power offset for the TFCI bits Power offset for the TPC bits Power offset for the pilot bits 9.2.1.63 9.2.2.9 9.2.2.26A 9.2.2.46 9.2.1.55 9.2.2.26 9.2.2.21A TFCS for the DL.

For the UL. TFCS for the UL.

YES YES YES _ YES YES GLOBAL EACH reject

reject reject

reject
reject reject reject

3GPP

Release 11

326

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >Not Used >Transmit Diversity Indicator >DL Reference Power >RL Specific DCH Information >DL DPCH Timing Adjustment >Phase Reference Update Indicator >RL specific E-DCH Information >E-DCH RL Indication >HS-DSCH Preconfiguration Setup >Non-Serving RL Preconfiguration Setup >Non-Serving RL Preconfiguration Removal

Presence O C Diversity mode O O O O O O O O O

Range

IE Type and Reference NULL 9.2.2.48 DL Power 9.2.1.21A 9.2.1.49A 9.2.2.9A 9.2.2.27B 9.2.2.35a 9.2.2.4E 9.2.2.100 9.2.2.124 NonServing RL Preconfigu ration Setup 9.2.2.124 9.2.2.142 9.2.2.47A HS-DSCH FDD Information 9.2.2.19a 9.2.1.30Q HS-DSCH MAC-d Flows Information 9.2.1.30OA 9.2.1.30OB RL ID 9.2.1.49

Semantics Description

Criticality

Assigned Criticality

Power on DPCH Required RL Timing Adjustment

YES YES YES YES YES YES YES YES YES

ignore ignore reject ignore reject reject ignore ignore ignore

>F-TPICH Information Reconf Transmission Gap Pattern Sequence Information HS-DSCH Information

O O O

YES YES YES

ignore reject reject

HS-DSCH Information To Modify HS-DSCH MAC-d Flows To Add

O O

YES YES

reject reject

HS-DSCH MAC-d Flows To Delete HS-PDSCH RL ID E-DPCH Information >Maximum Set of EDPDCHs >Puncture Limit >E-TFCS Information >E-TTI >E-DPCCH Power Offset >E-RGCH 2-Index-Step Threshold >E-RGCH 3-Index-Step Threshold >HARQ Info for E-DCH >HS-DSCH Configured Indicator > Minimum Reduced EDPDCH Gain Factor E-DCH FDD Information

O O 0..1 O O O O O O O O O O O

YES YES YES YES YES

reject reject reject

9.2.2.24e 9.2.1.46 9.2.2.4G 9.2.2.4J 9.2.2.4K 9.2.2.64 9.2.2.65 9.2.2.66 9.2.2.19C 9.2.2.102 9.2.2.4B

ignore reject

3GPP

Release 11

327

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name E-DCH FDD Information to Modify E-DCH MAC-d Flows to Add

Presence O O

Range

IE Type and Reference 9.2.2.4F E-DCH MAC-d flows Information 9.2.2.4MC 9.2.1.90 9.2.2.38C

Semantics Description

Criticality YES YES

Assigned Criticality reject reject

E-DCH MAC-d Flows to Delete Serving E-DCH RL F-DPCH Information >Power Offset Information >>PO2 >FDD TPC Downlink Step Size >Limited Power Increase >Inner Loop DL PC Status >F-DPCH Slot Format Support Request >F-DPCH Slot Format Fast Reconfiguration Mode CPC Information >Continuous Packet Connectivity DTX-DRX Information >Continuous Packet Connectivity DTX-DRX Information To Modify >Continuous Packet Connectivity HS-SCCH less Information >Continuous Packet Connectivity HS-SCCH less Deactivate Indicator Additional HS Cell Information RL Reconf Prep

O O 0..1 1 M M M M O O O 0..1 O O O O 0..<maxnoof HSDSCH1>

YES YES YES This IE shall be ignored by DRNS. _ YES YES YES YES YES For secondary serving HSDSCH cell. Max 7 in this 3GPP release. EACH

reject reject reject

Power Offset 9.2.2.30 9.2.2.16 9.2.2.21A 9.2.2.21a 9.2.2.86 9.2.2.85 9.2.2.70 9.2.2.72 9.2.2.73 9.2.2.74 9.2.2.75A

reject Ignore ignore reject

reject reject

>HS-PDSCH RL ID >C-ID >HS-DSCH FDD Secondary Serving Information >HS-DSCH FDD Secondary Serving Information To Modify >HS-DSCH Secondary Serving Remove UE Aggregate Maximum Bit Rate Additional E-DCH Cell Information RL Reconf Prep

M O O O O O 0..1

RL ID 9.2.1.49 9.2.1.6 9.2.2.19aa 9.2.2.19bb NULL 9.2.1.137 For E-DCH on multiple frequencies in this DRNS.

YES YES ignore reject

3GPP

Release 11

328

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency >>Setup

Presence M

Range

IE Type and Reference

Semantics Description

Criticality YES

Assigned Criticality reject

Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context M 1..<maxnoof EDCH-1> 9.2.2.113 E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.110 Used when RLs with additional EDCH on the secondary UL frequency exist in the current UE context and the configuration is modified (adding new RLs or modification of existing RLs) E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.111

>>>Multicell E-DCH Transport Bearer Mode >>>Additional EDCH Cell Information Setup

>>>>Additional EDCH FDD Setup Information >>Configuration Change

>>>Additional EDCH Cell Information Configuration Change >>>>Additional EDCH Configuration Change Information M

1..<maxnoof EDCH-1>

3GPP

Release 11

329

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>Removal

Presence

Range

IE Type and Reference

Semantics Description Used when all RLs on the indicated secondary UL frequency is removed. E-DCH on Secondary uplink frequency max 1 in this 3GPP release. Removal of all RL on secondary UL frequency

Criticality

Assigned Criticality

>>>Additional EDCH Cell Information Removal

1..<maxnoof EDCH-1>

>>>>RL on Secondary UL Frequency UL CLTD Information Reconf

ENUMERA TED (Remove, . ..) 9.2.2.130

YES

reject

Condition CodeLen SlotFormat Diversity mode

Explanation The IE shall be present only if the Min UL Channelisation Code length IE equals to 4. The IE shall only be present if the DL DPCH Slot Format IE is equal to any of the values from 12 to 16. The IE shall be present if Diversity Mode IE is present in the UL DPCH Information IE and is not equal to none. Explanation Maximum number of DCHs for a UE. Maximum number of RLs for a UE. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

Range bound maxnoofDCHs maxnoofRLs maxnoofHSDSCH-1 maxnoofEDCH-1

3GPP

Release 11

330

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.11.2

TDD Message

3GPP

Release 11

331

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Allowed Queuing Time UL CCTrCH To Add >CCTrCH ID >TFCS >TFCI Coding >Puncture Limit >UL SIR Target

Presence M M O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.2

Semantics Description

Criticality YES YES EACH YES

Assigned Criticality reject reject notify

0..<maxn oofCCTr CHs> M M M M O 9.2.3.2 9.2.1.63 9.2.3.11 9.2.1.46 Uplink SIR 9.2.1.69

For DCH and USCH For the UL. Mandatory for 1.28Mcps TDD; not applicable to 3.84Mcps TDD or 7.68Mcps TDD Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD

reject

>TDD TPC Uplink Step Size

9.2.3.10a

YES

reject

UL CCTrCH To Modify >CCTrCH ID >TFCS >TFCI Coding >Puncture Limit >UL SIR Target >TDD TPC Uplink Step Size UL CCTrCH to Delete >CCTrCH ID DL CCTrCH To Add >CCTrCH ID >TFCS >TFCI Coding >Puncture Limit >TPC CCTrCH List M M O O O O O

0..<maxn oofCCTr CHs> 9.2.3.2 9.2.1.63 9.2.3.11 9.2.1.46 Uplink SIR 9.2.1.69 9.2.3.10a 0..<maxn oofCCTr CHs> 9.2.3.2 0..<maxn oofCCTr CHs> M M M M 0..<maxn oCCTrC Hs> M O 0..<maxn oofCCTr CHs> M O 9.2.3.2 9.2.1.63 For the DL. CCTrCH ID 9.2.3.2 9.2.3.10 9.2.3.2 9.2.1.63 9.2.3.11 9.2.1.46 For DCH and DSCH For the DL. List of uplink CCTrCH which provide TPC For the UL.

EACH YES YES EACH EACH

notify

Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only

reject reject notify

notify

>>TPC CCTrCH ID >TDD TPC Downlink Step Size DL CCTrCH To Modify >CCTrCH ID >TFCS

YES EACH reject notify

3GPP

Release 11

332

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >TFCI Coding >Puncture Limit >TPC CCTrCH List

Presence O O

Range

IE Type and Reference 9.2.3.11 9.2.1.46

Semantics Description

Criticality

Assigned Criticality

0..<maxn oCCTrC Hs> M O 0..<maxn oofCCTr CHs> M O O 0..<maxn oofDCHs > M 0..<maxn oofDSCH s> M O 9.2.3.3ae 9.2.3.2 9.2.1.16 9.2.3.2 TDD DCHs To Modify 9.2.3.8B DCH TDD Information 9.2.3.2A CCTrCH ID 9.2.3.2 9.2.3.10

List of uplink CCTrCH which provide TPC

>>TPC CCTrCH ID >TDD TPC Downlink Step Size DL CCTrCH to Delete >CCTrCH ID DCHs To Modify DCHs To Add DCHs to Delete >DCH ID DSCHs To Modify >DSCH ID >CCTrCH ID

YES EACH YES YES GLOBAL GLOBAL reject notify

reject reject reject

reject

DL CCTrCH in which the DSCH is mapped.

>TrCH Source Statistics Descriptor >Transport Format Set >Allocation/Retention Priority >Scheduling Priority Indicator >BLER >Transport Bearer Request Indicator >Traffic Class >Binding ID

O O O O O M O O

9.2.1.65 9.2.1.64 9.2.1.1 9.2.1.51A 9.2.1.4 9.2.1.61 9.2.1.58A 9.2.1.3 Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP.

YES YES ignore ignore

>Transport Layer Address

9.2.1.62

YES

ignore

>TNL QoS

9.2.1.56A

YES

ignore

DSCHs To Add

DSCH TDD Information 9.2.3.3a

YES

reject

3GPP

Release 11

333

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name DSCHs to Delete >DSCH ID USCHs To Modify >USCH ID >CCTrCH ID

Presence

Range 0..<maxn oofDSCH s>

IE Type and Reference

Semantics Description

Criticality GLOBAL

Assigned Criticality reject

M 0..<maxn oofUSCH s> M O

9.2.3.3ae

GLOBAL

reject

9.2.3.14 9.2.3.2

UL CCTrCH in which the USCH is mapped.

>TrCH Source Statistics Descriptor >Transport Format Set >Allocation/Retention Priority >Scheduling Priority Indicator >BLER >Transport Bearer Request Indicator >RB Info >>RB Identity >Traffic class >Binding ID

O O O O O M 0..<maxn oofRB> M O O

9.2.1.65 9.2.1.64 9.2.1.1 9.2.1.51A 9.2.1.4 9.2.1.61 All Radio Bearers using this USCH 9.2.3.5B 9.2.1.58A 9.2.1.3

YES YES

>Transport Layer Address

9.2.1.62

Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP.

ignore ignore

YES

ignore

>TNL QoS

9.2.1.56A

YES

ignore

3GPP

Release 11

334

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name USCHs To Add USCHs to Delete >USCH ID Primary CCPCH RSCP DL Time Slot ISCP Info

Presence O

Range

IE Type and Reference USCH Information 9.2.3.15

Semantics Description

Criticality YES GLOBAL

Assigned Criticality reject reject

0..<maxn oofUSCH s> M O O 9.2.3.14 9.2.3.5 9.2.3.2D Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Applicable to 1.28Mcps TDD only

YES YES

ignore ignore

DL Time Slot ISCP Info LCR HS-DSCH Information

O O

9.2.3.2F HS-DSCH TDD Information 9.2.3.3aa 9.2.1.30Q HS-DSCH MAC-d Flows Information 9.2.1.30OA 9.2.1.30OB RL ID 9.2.1.49 RL ID 9.2.1.49 0..1

YES YES

ignore reject

HS-DSCH Information To Modify HS-DSCH MAC-d Flows To Add

O O

YES YES

reject reject

HS-DSCH MAC-d Flows To Delete HS-PDSCH RL ID PDSCH-RL-ID UL Synchronisation Parameters LCR

O O O

YES YES YES Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. YES

reject reject ignore ignore

>Uplink Synchronisation Step Size >Uplink Synchronisation Frequency RL Information >RL ID >RL Specific DCH Information Primary CCPCH RSCP Delta E-DCH Information >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information >E-DCH TDD Information to Modify

M M 0..<maxn oofRLs. M O O 0..1 O O O O O O

9.2.3.13J 9.2.3.13I

YES ignore

9.2.1.49 9.2.1.49A 9.2.3.5a 3.84Mcps TDD only 9.2.3.36 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.40 9.2.3.42

YES YES ignore reject

3GPP

Release 11

335

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name E-DCH Serving RL E-DCH Information 7.68Mcps >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information 7.68Mcps >E-DCH TDD Information to Modify E-DCH Information 1.28Mcps >E-PUCH Information LCR >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information LCR >E-DCH TDD Information to Modify Need for Idle Interval CPC Information >Continuous Packet Connectivity DRX Information LCR >Continuous Packet Connectivity DRX Information To Modify LCR >HS-DSCH Semi-Persistent scheduling Information LCR >HS-DSCH Semi-Persistent scheduling Information to modify LCR >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR >E-DCH Semi-Persistent scheduling Information LCR >E-DCH Semi-Persistent scheduling Information to modify LCR >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR RNTI Allocation Indicator DCH Measurement Type indicator Multi-Carrier E-DCH Information Reconf

Presence O

Range

IE Type and Reference 9.2.1.49

Semantics Description 3.84Mcps TDD only 7.68Mcps TDD only

Criticality YES YES

Assigned Criticality reject reject

0..1 O O O O O O 0..1 O O O O O O O 0..1 O O O O O O O O O O 0..1 9.2.3.61 9.2.3.62 9.2.3.64 9.2.3.65 9.2.3.70 9.2.3.66 9.2.3.67 9.2.3.71 ENUMERA TED (True) 9.2.3.76 9.2.3.36a 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.40a 9.2.3.42 ENUMERA TED (True, False) 9.2.3.36 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.51 9.2.3.42

1.28Mcps TDD only

YES

reject

TDD only 1.28Mcps TDD only

YES YES _ _ _ _ _ _ _ _

ignore reject

1.28 Mcps TDD only 1.28 Mcps TDD only Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only

YES YES YES

ignore reject reject

3GPP

Release 11

336

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >CHOICE continue,Setup or Change >>continue >>Setup >>>Multi-Carrier E-DCH Transport Bearer Mode LCR >>>Multi-Carrier E-DCH Information LCR >>change >>>MultiCarrier E-DCH Transport Bearer Mode >>>Multi-Carrier E-DCH Information LCR >>>Removal UL MultiCarrier info >>>>UARFCN MU-MIMO Indicator

Presence M

Range

IE Type and Reference

Semantics Description

Criticality

Assigned Criticality

M M O O 0..<maxn oofUL12 8Carriers -1> M O

9.2.3.79 9.2.3.77 9.2.3.79 9.2.3.77

9.2.1.65 9.2.3.82

Corresponds to Nt TS 25.105 [17] 1.28 Mcps TDD only

YES reject

Range bound maxnoofDCHs maxnoofCCTrCHs maxnoofDSCHs maxnoofUSCHs maxnoofRLs maxnoofUL128Carriers

Explanation Maximum number of DCHs for a UE. Maximum number of CCTrCHs for a UE. Maximum number of DSCHs for one UE. Maximum number of USCHs for one UE. Maximum number of RLs for one UE Maximum number of uplink frequencies in MultiCarrier E-DCH Operation

3GPP

Release 11

337

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.12 RADIO LINK RECONFIGURATION READY

9.1.12.1 FDD Message

3GPP

Release 11

338

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response >RL ID >Maximum Uplink SIR >Minimum Uplink SIR >Maximum DL TX Power >Minimum DL TX Power >Not Used >DL Code Information

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 DL Power 9.2.1.21A DL Power 9.2.1.21A NULL FDD DL Code Information 9.2.2.14A 9.2.1.16A NULL 9.2.2.10D 9.2.2.32A 9.2.2.38B 9.2.2.4C RL Set ID 9.2.2.35 9.2.2.4D 9.2.2.85 9.2.2.99 9.2.2.125 9.2.1.13 9.2.1.30P HS-DSCH FDD Information Response 9.2.2.19b 9.2.1.34B 9.2.2.71 9.2.2.75

Semantics Description

Criticality YES EACH YES

Assigned Criticality reject ignore

0..<maxno ofRLs> M O O O O O O

ignore

>DCH Information Response >Not Used >DL Power Balancing Updated Indicator >Primary CPICH Usage For Channel Estimation >Secondary CPICH Information Change >E-DCH FDD Information Response >E-DCH RL Set ID >E-DCH FDD DL Control Channel Information >F-DPCH Slot Format >HS-DSCH Preconfiguration Info >Non-Serving RL Preconfiguration Info Criticality Diagnostics HS-DSCH-RNTI HS-DSCH Information Response

O O O O O O O O O O O O O O

YES YES YES YES YES YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

MAC-hs Reset Indicator Fast Reconfiguration Permission Continuous Packet Connectivity HS-SCCH less Information Response Additional HS Cell Information Response

O O O 0..<maxno ofHSDSC H-1>

FDD only

YES YES YES

ignore ignore ignore ignore

For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.1.30P

EACH

>HS-PDSCH RL ID >HS-DSCH-RNTI

M M

3GPP

Release 11

339

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >HS-DSCH FDD Secondary Serving Information Response Additional E-DCH Cell Information Response RLReconf

Presence M

Range

IE Type and Reference 9.2.2.19ba

Semantics Description

Criticality

Assigned Criticality

0..<maxno ofEDCH1>

>Additional E-DCH FDD Information Response

9.2.2.120

E-DCH on Secondary uplink frequency max 1 in this 3GPP release. For new EDCH Radio Links on secondary carrier

EACH

ignore

>Additional Modified EDCH FDD Information Response

9.2.2.121

Range bound maxnoofRLs maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of RLs for a UE. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

340

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.12.2

TDD Message

3GPP

Release 11

341

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response >RL ID >Maximum Uplink SIR >Minimum Uplink SIR >Maximum DL TX Power >Minimum DL TX Power >Secondary CCPCH Info TDD >UL CCTrCH Information >>CCTrCH ID >>UL DPCH to be Added >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>> Rx Timing Deviation >>>UL Timeslot Information >>> Rx Timing Deviation 3.84 Mcps Extended >>UL DPCH to be Modified >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information >>>>Time Slot >>>>Midamble Shift And Burst Type >>>>TFCI Presence >>>>UL Code Information >>>>>DPCH ID >>>>>TDD Channelisation Code >>>UL Timeslot Information LCR >>>>Time Slot LCR >>>>Midamble Shift LCR

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.3.7B

Semantics Description

Criticality YES YES

Assigned Criticality reject ignore

0..<maxn oofRLs> M O O O O O 0..<maxn oofCCTr CHs> M 0..1 M M M O M O 0..1 O O O 0..<maxn oOfTS> M O O 0..<maxn oOfDPC Hs> M O 0..<maxn oOfTSLC R> M O 9.2.3.12a 9.2.3.4C 9.2.3.3 9.2.3.8 9.2.1.56 9.2.3.4 9.2.1.55 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.7A 9.2.3.13C 9.2.3.35 9.2.3.2

See Note 1 below

Applicable to 3.84Mcps TDD only For DCH

GLOBAL YES YES YES Ignore ignore ignore

Applicable to 3.84Mcps TDD only

ignore

Applicable to 3.84Mcps TDD only

Applicable to 1.28Mcps TDD only

GLOBAL

ignore

3GPP

Release 11

342

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>>TFCI Presence >>>>UL Code Information LCR >>>>>DPCH ID >>>>>TDD Channelisation Code LCR >>>>> TDD UL DPCH Time Slot Format LCR >>>UL Timeslot Information 7.68Mcps >>>>Time Slot >>>>Midamble Shift And Burst Type 7.68Mcps >>>>TFCI Presence >>>>UL Code Information 7.68Mcps >>>>>DPCH ID >>>>>TDD Channelisation Code 7.68Mcps >>UL DPCH to be Deleted >>>DPCH ID >>UL DPCH to be Added LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information LCR >>UL DPCH to be Added 7.68Mcps >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>> Rx Timing Deviation 7.68Mcps >>>UL Timeslot Information 7.68Mcps >DL CCTrCH Information >>CCTrCH ID >>DL DPCH to be Added >>>Repetition Period >>>Repetition Length

Presence O

Range

IE Type and Reference 9.2.1.55

Semantics Description

Criticality GLOBAL

Assigned Criticality

0..<maxn oOfDPC HLCR> M O O 9.2.3.3 9.2.3.8a 9.2.3.10C

ignore

YES reject

0..<maxn oOfTS> M O O 0..<maxn oOfDPC Hs768> M O 9.2.3.3 9.2.3.25 9.2.1.56 9.2.3.23 9.2.1.55

Applicable to 7.68Mcps TDD only

GLOBAL GLOBAL

ignore

ignore

0..<maxn oofDPCH s> M 0..1 M M M M 0..1 M M M O M 0..<maxn oofCCTr CHs> M 0..1 M M 9.2.3.7 9.2.3.6 9.2.3.2 Applicable to 3.84Mcps TDD only 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.30 9.2.3.26 For DCH 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.13G Applicable to 7.68Mcps TDD only 9.2.3.3 Applicable to 1.28Mcps TDD only

GLOBAL YES YES GLOBAL YES

ignore

ignore

ignore

ignore

ignore

3GPP

Release 11

343

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>>TDD DPCH Offset >>>DL Timeslot Information >>DL DPCH to be Modified >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information >>>>Time Slot >>>>Midamble Shift And Burst Type >>>>TFCI Presence >>>>DL Code Information >>>>>DPCH ID >>>>>TDD Channelisation Code >>>DL Timeslot Information LCR >>>>Time Slot LCR >>>>Midamble Shift LCR >>>>TFCI Presence >>>>DL Code Information LCR >>>>>DPCH ID >>>>>TDD Channelisation Code LCR >>>>> TDD DL DPCH Time Slot Format LCR >>>>Maximum DL TX Power >>>>Minimum DL TX Power >>>DL Timeslot Information 7.68Mcps >>>>Time Slot >>>>Midamble Shift And Burst Type 7.68Mcps >>>>TFCI Presence >>>>DL Code Information >>>>>DPCH ID 7.68Mcps >>>>>TDD Channelisation Code 7.68Mcps

Presence M M

Range

IE Type and Reference 9.2.3.8A 9.2.3.2C

Semantics Description

Criticality YES

Assigned Criticality

0..1 O O O 0..<maxn oOfTS> M O O 0..<maxn oOfDPC Hs> M O 0..<maxn oOfTSLC R> M O O 0..<maxn oOfDPC HLCR> M O O O O 0..<maxn oOfTS> M O O 0..<maxn oOfDPC Hs768> M O 9.2.3.34 9.2.3.25 9.2.1.56 9.2.3.23 9.2.1.55 9.2.3.3 9.2.3.8a 9.2.3.8E DL Power 9.2.1.21A DL Power 9.2.1.21A Maximum allowed power on DPCH Minimum allowed power on DPCH Applicable to 7.68Mcps TDD only 9.2.3.12a 9.2.3.4C 9.2.1.55 9.2.3.3 9.2.3.8 Applicable to 1.28Mcps TDD only 9.2.1.56 9.2.3.4 9.2.1.55 9.2.3.7 9.2.3.6 9.2.3.8A Applicable to 3.84Mcps TDD only

ignore

GLOBAL GLOBAL YES YES YES GLOBAL reject ignore ignore ignore ignore ignore

3GPP

Release 11

344

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >>DL DPCH to be Deleted >>>DPCH ID >>DL DPCH to be Deleted 7.68Mcps TDD >>>DPCH ID 7.68Mcps >>DL DPCH to be Added LCR >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information LCR >>DL DPCH to be Added 7.68Mcps >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information 7.68Mcps >>CCTrCH Maximum DL TX Power

Presence

Range 0..<maxn oofDPCH s>

IE Type and Reference

Semantics Description

Criticality GLOBAL

Assigned Criticality ignore

M 0..<maxn oofDPCH s768> M 0..1 M M M M 0..1 M M M M O

9.2.3.3

GLOBAL YES Applicable to 7.68Mcps TDD only YES Maximum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Minimum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only YES

ignore

9.2.3.34 Applicable to 1.28Mcps TDD only 9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.2E

ignore

ignore

9.2.3.7 9.2.3.6 9.2.3.8A 9.2.3.28 DL Power 9.2.1.21A

ignore

>>CCTrCH Minimum DL TX Power

DL Power 9.2.1.21A

YES

ignore

>DCH Information Response >DSCH to be Added or Modified >>DSCH ID >>Transport Format Management >>DSCH Flow Control Information >>Binding ID >>Transport Layer Address >USCH to be Added or Modified >>USCH ID >>Transport Format Management >>Binding ID >>Transport Layer Address

O 0 .. <maxnoo f DSCHs> M M M O O 0 .. <maxnoo f USCHs> M M O O

9.2.1.16A

YES GLOBAL

ignore ignore

9.2.3.3ae 9.2.3.13 9.2.3.3ag 9.2.1.3 9.2.1.62

GLOBAL ignore

9.2.3.14 9.2.3.13 9.2.1.3 9.2.1.62

3GPP

Release 11

345

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name >Uplink Timing Advance Control LCR >Secondary CCPCH Info TDD LCR >Secondary CCPCH Info 7.68Mcps TDD >UARFCN

Presence O O O O

Range

IE Type and Reference 9.2.3.13K 9.2.3.7F 9.2.3.22 9.2.1.66

Semantics Description Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only Applicable to 7.68Mcps TDD only Applicable to 1.28Mcps TDD only. Mandatory for 1.28Mcps TDD when using multiple frequencies. Corresponds to Nt (3GPP TS 25.105)

Criticality YES YES YES YES

Assigned Criticality ignore ignore ignore ignore

Criticality Diagnostics HS-DSCH-RNTI HS-DSCH Information Response

O O O

DSCH-RNTI MAC-hs Reset Indicator E-DCH Information Response

O O O

E-DCH Information Response 7.68Mcps

E-DCH Information Response 1.28Mcps

PowerControl GAP Idle Interval Information Continuous Packet Connectivity DRX Information Response LCR HS-DSCH Semi-Persistent scheduling Information Response LCR E-DCH Semi-Persistent scheduling Information Response LCR E-RNTI for FACH H-RNTI for FACH

O O O O O O O

9.2.1.13 9.2.1.30P HS-DSCH TDD Information Response 9.2.3.3ab 9.2.3.3ah 9.2.1.34B E-DCH TDD Information Response 9.2.3.41 E-DCH TDD Information Response 7.68Mcps 9.2.3.52 E-DCH TDD Information Response 1.28Mcps 9.2.3.41a INTEGER (1..255) 9.2.3.60 9.2.3.63 9.2.3.68 9.2.3.69 E-RNTI 9.2.1.94 HS-DSCHRNTI 9.2.1.30P

YES YES YES

ignore ignore ignore

3.84Mcps TDD only

YES YES YES

ignore ignore ignore

7.68Mcps TDD only

YES

ignore

1.28Mcps TDD only

YES

ignore

1.28Mcps TDD only TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only

YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore

3GPP

Release 11

346

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name DCH Measurement Occasion Information Multi-Carrier E-DCH Information Response LCR MU-MIMO Information

Presence O

Range

1.28 Mcps TDD YES reject only O 9.2.3.78 1.28 Mcps TDD YES ignore only O 9.2.3.81 1.28 Mcps TDD YES reject only Note 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxnoofRLs are represented by separate ASN.1 structures with different criticalities. Range bound maxnoofDSCHs maxnoofUSCHs maxnoofCCTrCHs maxnoofTS maxnoofDPCHs maxnoofTSLCRs maxnoofDPCHLCRs maxnoofRLs maxnoofDPCHs768 Explanation Maximum number of DSCHs for one UE. Maximum number of USCHs for one UE. Maximum number of CCTrCHs for a UE. Maximum number of Timeslots for a UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of DPCH for a UE for 3.84Mcps TDD. Maximum number of Timeslots for a UE for 1.28Mcps TDD. Maximum number of DPCH for a UE for 1.28Mcps TDD. Maximum number of RLs for one UE Maximum number of DPCH for a UE for 7.68Mcps TDD.

IE Type and Reference 9.2.3.75

Semantics Description

Criticality

Assigned Criticality

9.1.13 RADIO LINK RECONFIGURATION COMMIT

IE/Group Name Message Type Transaction ID CFN Active Pattern Sequence Information Fast Reconfiguration Mode Presence M M M O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.9 9.2.2.A 9.2.2.70 Semantics Description Criticality YES YES YES YES Assigned Criticality ignore ignore ignore reject

FDD only FDD only

9.1.14 RADIO LINK RECONFIGURATION FAILURE

IE/Group Name Message Type Transaction ID CHOICE Cause Level >General >>Cause >RL Specific >>RLs Causing Reconfiguration Failure >>>RL ID >>>Cause >>>Max UE DTX Cycle Criticality Diagnostics Presence M M M M 0..<maxnoof RLs> M M C-DTXCycleNotA vailable O 9.2.1.49 9.2.1.5 9.2.2.87 9.2.1.13 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 Semantics Description Criticality YES YES EACH YES YES Assigned Criticality reject ignore

ignore

ignore ignore

3GPP

Release 11

347

3GPP TS 25.423 V11.2.0 (2012-06)

Condition DTX-CycleNotAvailable

Explanation The IE shall be present if the Cause IE is set to Continuous Packet Connectivity UE DTX Cycle not Available . Explanation Maximum number of RLs for a UE.

Range bound maxnoofRLs

9.1.15 RADIO LINK RECONFIGURATION CANCEL

IE/Group Name Message Type Transaction ID Presence M M Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES Assigned Criticality ignore

3GPP

Release 11

348

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.16 RADIO LINK RECONFIGURATION REQUEST

9.1.16.1 FDD Message

3GPP

Release 11

349

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID

Presence M M O

Range

Allowed Queuing Time

UL DPCH Information >TFCS >UL DPDCH Indicator For E-DCH Operation DL DPCH Information >TFCS >TFCI Signalling Mode >Limited Power Increase DCHs To Modify DCHs To Add DCHs To Delete >DCH ID Transmission Gap Pattern Sequence Information RL Information >RL ID >RL Specific DCH Information >RL specific E-DCH Information >E-DCH RL Indication >HS-DSCH Preconfiguration Setup >Non-Serving RL Preconfiguration Setup >Non-Serving RL Preconfiguration Removal

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.2 9.2.1.63 9.2.2.52A

Semantics Description

Criticality YES YES YES YES

Assigned Criticality reject reject reject reject reject

0..1 O O 0..1 O O O O O 0..<maxno ofDCHs> M O 0..<maxno ofRLs> M O O O O O O 9.2.1.49 9.2.1.49A 9.2.2.35a 9.2.2.4E 9.2.2.100 9.2.2.124 NonServing RL Preconfigu ration Setup 9.2.2.124 9.2.2.142 9.2.2.10C HS-DSCH FDD Information 9.2.2.19a 9.2.1.30NA HS-DSCH MAC-d Flows Information 9.2.1.30OA 9.2.1.30OB RL ID 9.2.1.49 9.2.1.16 9.2.2.47A 9.2.1.63 9.2.2.46 9.2.2.21A FDD DCHs To Modify 9.2.2.13C DCH FDD Information 9.2.2.4A TFCS for the DL. TFCS for the UL.

YES YES YES GLOBAL YES EACH YES YES YES YES YES

reject
reject reject reject ignore

reject reject ignore ignore ignore

>F-TPICH Information Reconf DL Reference Power Information HS-DSCH Information

O O O

YES YES YES

ignore ignore reject

HS-DSCH Information To Modify Unsynchronised HS-DSCH MAC-d Flows To Add

O O

YES YES

reject reject

HS-DSCH MAC-d Flows To Delete HS-PDSCH RL ID

O O

YES YES

reject reject

3GPP

Release 11

350

3GPP TS 25.423 V11.2.0 (2012-06)

E-DPCH Information >Maximum Set of EDPDCHs >Puncture Limit >E-TFCS Information >E-TTI >E-DPCCH Power Offset >E-RGCH 2-Index-Step Threshold >E-RGCH 3-Index-Step Threshold >HARQ Info for E-DCH > Minimum Reduced EDPDCH Gain Factor >HS-DSCH Configured Indicator E-DCH FDD Information E-DCH FDD Information to Modify E-DCH MAC-d Flows to Add

0..1 O O
O 9.2.2.24e 9.2.1.46 9.2.2.4G 9.2.2.4J 9.2.2.4K 9.2.2.64 9.2.2.65 9.2.2.66 9.2.2.102 9.2.2.19C 9.2.2.4B 9.2.2.4F E-DCH MAC-d flows Information 9.2.2.4MC 9.2.1.90 9.2.2.38C 0..1 O O O O O 0..<maxno ofHSDSC H-1> 9.2.2.72 9.2.2.73 9.2.2.74 9.2.2.75A INTEGER (1..30) For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.1.6 9.2.2.19aa 9.2.2.19bc

YES YES YES YES YES

reject

O
O O O O O O O O O

ignore

reject reject reject

E-DCH MAC-d Flows to Delete Serving E-DCH RL CPC Information >Continuous Packet Connectivity DTX-DRX Information >Continuous Packet Connectivity DTX-DRX Information To Modify >Continuous Packet Connectivity HS-SCCH less Information >Continuous Packet Connectivity HS-SCCH less Deactivate Indicator No of Target Cell HS-SCCH Order Additional HS Cell Information RL Reconf Req

O O

YES YES YES YES YES EACH

reject reject reject

reject ignore reject

>HS-PDSCH RL ID >C-ID >HS-DSCH FDD Secondary Serving Information >HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised >HS-DSCH Secondary Serving Remove

M O O O

NULL

3GPP

Release 11

351

3GPP TS 25.423 V11.2.0 (2012-06)

UE Aggregate Maximum Bit Rate Additional E-DCH Cell Information RL Reconf Req

O 0..1

9.2.1.137 For E-DCH on multiple frequencies in this DRNS.

YES YES

ignore reject

>CHOICE Setup, Configuration Change or Removal of E-DCH On Secondary UL Frequency >>Setup

YES

reject

Used when RLs on the secondary UL frequency does not exist or is not configured with E-DCH in the current UE context M 1..<maxno ofEDCH1> 9.2.2.113 E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.110 Used when RLs with additional EDCH on the secondary UL frequency exist in the current UE context and the configuration is modified (adding new RLs or modification of existing RLs) E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.111

>>>Multicell E-DCH Transport Bearer Mode >>>Additional E-DCH Cell Information Setup

>>>>Additional EDCH FDD Setup Information >>Configuration Change

>>>Additional E-DCH Cell Information Configuration Change

1..<maxno ofEDCH1>

>>>> Additional EDCH Configuration Change Information

3GPP

Release 11

352

3GPP TS 25.423 V11.2.0 (2012-06)

>>Removal

>>>Additional E-DCH Cell Information Removal

1..<maxno ofEDCH1>

>>>>RL on Secondary UL Frequency UL CLTD Information Reconf

ENUMERA TED (Remove, . ..) 9.2.2.130

Used when all RLs on the indicated secondary UL frequency is removed. E-DCH on Secondary uplink frequency max 1 in this 3GPP release. Removal of all RL on secondary UL frequency

YES

reject

Range Bound maxnoofDCHs maxnoofRLs maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of DCHs for one UE. Maximum number of RLs for a UE. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

353

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.16.2

TDD Message

3GPP

Release 11

354

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Allowed Queuing Time UL CCTrCH Information To Modify >CCTrCH ID >TFCS >UL SIR Target UL CCTrCH Information to Delete >CCTrCH ID DL CCTrCH Information To Modify >CCTrCH ID >TFCS DL CCTrCH Information to Delete >CCTrCH ID DCHs To Modify DCHs To Add DCHs to Delete >DCH ID RL Information >RL ID >RL Specific DCH Information UL Synchronisation Parameters LCR

Presence M M O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.2

Semantics Description

Criticality YES YES EACH YES EACH

Assigned Criticality reject reject notify

0..<maxn oofCCTr CHs> M O O 0..<maxn oofCCTr CHs> M 0..<maxn oofCCTr CHs> M O 0..<maxn oofCCTr CHs> M O O 0..<maxn oofDCHs > M 0..<maxn oofRLs> M O 0..1 9.2.1.49 9.2.1.49A Mandatory for 1.28Mcps TDD. Not Applicable to 3.84Mcps TDD. 9.2.3.13J 9.2.3.13I HS-DSCH TDD Information9. 2.3.3aa 9.2.1.30NA HS-DSCH MAC-d Flows Information 9.2.1.30OA 9.2.1.30OB RL ID 9.2.1.49 9.2.1.16 9.2.3.2 TDD DCHs To Modify 9.2.3.8B DCH TDD Information 9.2.3.2A 9.2.3.2 9.2.1.63 9.2.3.2 9.2.3.2 9.2.1.63 Uplink SIR 9.2.1.69

Applicable to 1.28Mcps TDD only

reject notify

EACH EACH YES YES GLOBAL YES YES

notify

notify

reject reject reject

ignore

ignore

>Uplink Synchronisation Step Size >Uplink Synchronisation Frequency HS-DSCH Information

M M O

YES reject

HS-DSCH Information To Modify Unsynchronised HS-DSCH MAC-d Flows To Add HS-DSCH MAC-d Flows To Delete HS-PDSCH RL ID

O O

YES YES

reject reject

O O

YES YES

reject reject

3GPP

Release 11

355

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name E-DCH Information >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information >E-DCH TDD Information to Modify E-DCH Serving RL E-DCH Information 7.68Mcps >E-PUCH Information >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information 7.68Mcps >E-DCH TDD Information to Modify E-DCH Information 1.28Mcps >E-PUCH Information LCR >E-TFCS Information TDD >E-DCH MAC-d Flows to Add >E-DCH MAC-d Flows to Delete >E-DCH TDD Information LCR >E-DCH TDD Information to Modify Need for Idle Interval CPC Information >Continuous Packet Connectivity DRX Information LCR >Continuous Packet Connectivity DRX Information To Modify LCR >HS-DSCH Semi-Persistent scheduling Information LCR >HS-DSCH Semi-Persistent scheduling Information to modify LCR >HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR >E-DCH Semi-Persistent scheduling Information LCR >E-DCH Semi-Persistent scheduling Information to modify LCR >E-DCH Semi-Persistent scheduling Deactivate Indicator LCR

Presence

Range 0..1

IE Type and Reference 9.2.3.36 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.40 9.2.3.42 9.2.1.49

Semantics Description 3.84Mcps TDD only

Criticality YES

Assigned Criticality reject

O O O O O O O 0..1 O O O O O O 0..1 O O O O O O O 0..1 O O O O O O O O

3.84Mcps TDD only 7.68Mcps TDD only

YES YES

reject reject

9.2.3.36 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.51 9.2.3.42 1.28Mcps TDD only 9.2.3.36a 9.2.3.37 9.2.3.38 9.2.1.90 9.2.3.40a 9.2.3.42 ENUMERAT ED (True, False) 9.2.3.61 9.2.3.62 9.2.3.64 9.2.3.65 9.2.3.70 9.2.3.66 9.2.3.67 9.2.3.71 TDD only

YES YES YES _ _ _ _ _ _ _ _

reject

ignore reject

3GPP

Release 11

356

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name RNTI Allocation Indicator DCH Measurement Type indicator Multi-Carrier E-DCH Information Reconf

Presence O O

Range

IE Type and Reference ENUMERAT ED (True) 9.2.3.76

0..1

Semantics Description 1.28 Mcps TDD only 1.28 Mcps TDD only Applicable for Multi-Carrier E-DCH Operation in 1.28 Mcps TDD only

Criticality YES YES YES

Assigned Criticality ignore reject reject

>CHOICE continue,Setup or Change >>continue >>Setup >>>Multi-Carrier E-DCH Transport Bearer Mode LCR >>>Multi-Carrier E-DCH Information LCR >>Change >>>Multi-Carrier E-DCH Transport Bearer Mode >>>Multi-Carrier E-DCH Information LCR >>>Removal UL MultiCarrier info >>>>UARFCN MU-MIMO Indicator

M M O O 0..<maxn oofUL12 8Carriers -1> M O

9.2.3.79 9.2.3.77 9.2.3.79 9.2.3.77

9.2.1.65 9.2.3.82

Corresponds to Nt TS 25.105 [17] 1.28 Mcps TDD only

YES reject

Range Bound maxnoofCCTrCHs maxnoofDCHs maxnoofRLs maxnoofUL1.28Carriers

Explanation Maximum number of CCTrCHs for a UE. Maximum number of DCHs for one UE. Maximum number of RLs for one UE Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation

3GPP

Release 11

357

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.17 RADIO LINK RECONFIGURATION RESPONSE

9.1.17.1 FDD Message

3GPP

Release 11

358

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response >RL ID >Maximum Uplink SIR >Minimum Uplink SIR >Maximum DL TX Power >Minimum DL TX Power >Not Used >DCH Information Response >DL Code Information

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 DL Power 9.2.1.21A DL Power 9.2.1.21A NULL 9.2.1.16A FDD DL Code Information 9.2.2.14A 9.2.2.10D 9.2.2.4C RL Set ID 9.2.2.35 9.2.2.4D 9.2.2.85 9.2.2.99 9.2.2.125 9.2.1.13 9.2.1.30P HS-DSCH FDD Information Response 9.2.2.19b 9.2.1.34B 9.2.2.75

Semantics Description

Criticality YES EACH YES YES

Assigned Criticality reject ignore

0..<maxno ofRLs> M O O O O O O O

ignore ignore

>DL Power Balancing Updated Indicator >E-DCH FDD Information Response >E-DCH RL Set ID >E-DCH FDD DL Control Channel Information >F-DPCH Slot Format >HS-DSCH Preconfiguration Info >Non-Serving RL Preconfiguration Info Criticality Diagnostics HS-DSCH-RNTI HS-DSCH Information Response

O O O O O O O O O O

YES YES YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

MAC-hs Reset Indicator Continuous Packet Connectivity HS-SCCH less Information Response Additional HS Cell Information Response

O O 0..<maxno ofHSDSC H-1>

YES YES For secondary serving HSDSCH cell. Max 7 in this 3GPP release. EACH

ignore Ignore ignore

>HS-PDSCH RL ID >HS-DSCH-RNTI >HS-DSCH FDD Secondary Serving Information Response

M M M

RL ID 9.2.1.49 9.2.1.30P 9.2.2.19ba

3GPP

Release 11

359

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Additional E-DCH Cell Information Response RLReconf

Presence

Range 0..<maxno ofEDCH1>

IE Type and Reference

Semantics Description E-DCH on Secondary uplink frequency max 1 in this 3GPP release. For new EDCH Radio Links on secondary carrier

Criticality EACH

Assigned Criticality ignore

>Additional E-DCH FDD Information Response

9.2.2.120

>Additional Modified EDCH FDD Information Response

9.2.2.121

Range Bound maxnoofRLs maxnoofHSDSCH-1 maxnoofEDCH-1

Explanation Maximum number of RLs for a UE. Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

3GPP

Release 11

360

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.17.2

TDD Message

3GPP

Release 11

361

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information Response >RL ID >Maximum Uplink SIR >Minimum Uplink SIR >Maximum DL TX Power >Minimum DL TX Power >DCH Information Response >DL CCTrCH Information >>CCTrCH ID >>DL DPCH To Modify LCR >>>DL Timeslot Information LCR >>>>Time Slot LCR >>>>Maximum DL TX Power >>>>Minimum DL TX Power >>CCTrCH Maximum DL TX Power

Presence M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59

Semantics Description

Criticality YES YES YES

Assigned Criticality reject ignore

0..<max noofRL s> M O O O O O 0..<max noofCC TrCHs> M 0..1 0..<max noOfTS LCR> M O O O 9.2.3.12a DL Power 9.2.1.21A DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.3.2 9.2.1.49 Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.16A

See note 1 below

ignore ignore

For DCH

GLOBAL YES YES

Applicable to 1.28Mcps TDD only

ignore

>>CCTrCH Minimum DL TX Power

DL Power 9.2.1.21A

>Uplink Timing Advance Control LCR Criticality Diagnostics HS-DSCH-RNTI HS-DSCH Information Response

O O O O

9.2.3.13K 9.2.1.13 9.2.1.30P HS-DSCH TDD Information Response 9.2.3.3ab 9.2.1.34B E-DCH TDD Information Response 9.2.3.41

Maximum allowed power on DPCH Minimum allowed power on DPCH Maximum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Minimum allowed power on DPCH Applicable to 3.84Mcps TDD and 7.68Mcps TDD only Applicable to 1.28Mcps TDD only

ignore

YES

ignore

YES YES YES YES

ignore ignore ignore ignore

MAC-hs Reset Indicator E-DCH Information Response

O O

3.84Mcps TDD only

YES YES

ignore ignore

3GPP

Release 11

362

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name E-DCH Information Response 7.68Mcps

Presence O

Range

E-DCH Information Response 1.28Mcps

PowerControl GAP Idle Interval Information Continuous Packet Connectivity DRX Information Response LCR HS-DSCH Semi-Persistent scheduling Information Response LCR E-DCH Semi-Persistent scheduling Information Response LCR E-RNTI for FACH H-RNTI for FACH DCH Measurement Occasion Information Multi-Carrier E-DCH Information Response LCR MU-MIMO Information

O O O O O O O O

IE Type and Reference E-DCH TDD Information Response 7.68Mcps 9.2.3.52 E-DCH TDD Information Response 1.28Mcps 9.2.3.41a INTEGER (1..255) 9.2.3.60 9.2.3.63 9.2.3.68 9.2.3.69 E-RNTI 9.2.1.94 HS-DSCHRNTI 9.2.1.30P 9.2.3.75

Semantics Description 7.68Mcps TDD only

Criticality YES

Assigned Criticality ignore

1.28Mcps TDD only

YES

ignore

1.28Mcps TDD only TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only 1.28 Mcps TDD only

YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore

1.28 Mcps YES reject TDD only O 9.2.3.78 1.28 Mcps YES ignore TDD only O 9.2.3.81 1.28 Mcps YES reject TDD only Note 1: This information element is a simplified representation of the ASN.1. Repetition 1 and repetition 2 through maxnoofRLs are represented by separate ASN.1 structures with different criticalities. Range bound maxnoofCCTrCHs maxnoofTSLCRs maxnoofRLs Explanation Maximum number of CCTrCHs for a UE. Maximum number of Timeslots for a UE for 1.28Mcps TDD. Maximum number of RLs for one UE

3GPP

Release 11

363

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.18 RADIO LINK FAILURE INDICATION

IE/Group Name Message Type Transaction ID CHOICE Reporting Object Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

Object for which the Failure shall be reported. 1..<maxnoof RLs>

>RL >>RL Information >>>RL ID >>>Cause >RLS >>RL Set Information >>>RL Set ID >>>Cause >CCTrCH >>RL ID >>CCTrCH List >>>CCTrCH ID >>>Cause M M

EACH 9.2.1.49 9.2.1.5 FDD only EACH TDD only EACH

ignore

1..<maxnoof RLSets> M M M 1..<maxnoC CTrCHs> M M 9.2.3.2 9.2.1.5 Explanation Maximum number of RLs for one UE. Maximum number of RL Sets for one UE. Maximum number of CCTrCHs for a UE. 9.2.2.35 9.2.1.5 9.2.1.49

ignore

ignore

Range bound maxnoofRLs maxnoofRLSets maxnoofCCTrCHs

9.1.19 RADIO LINK RESTORE INDICATION

IE/Group Name Message Type Transaction ID CHOICE Reporting Object Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

>RL >>RL Information >>>RL ID >RLS >>RL Set Information >>>RL Set ID >CCTrCH >>RL ID >>CCTrCH List >>>CCTrCH ID M

Object for which the Restoration shall be reported. TDD only 1..<max noofRL s> 9.2.1.49 FDD only 1..<max noofRL Sets>

EACH EACH

ignore

ignore

M M 1..<max noCCTr CHs> M

9.2.2.35 TDD only 9.2.1.49

EACH

ignore

9.2.3.2

3GPP

Release 11

364

3GPP TS 25.423 V11.2.0 (2012-06)

Range bound maxnoofRLs maxnoofRLSets maxnoofCCTrCHs

Explanation Maximum number of RLs for one UE. Maximum number of RL Sets for one UE. Maximum number of CCTrCHs for a UE.

9.1.20 DL POWER CONTROL REQUEST [FDD]

IE/Group Name Message Type Transaction ID Power Adjustment Type DL Reference Power Inner Loop DL PC Status DL Reference Power Information >RL ID >DL Reference Power Max Adjustment Step Adjustment Period Adjustment Ratio Presence M M M CCommon O CIndividual M M CCommonO rIndividual CCommonO rIndividual CCommonO rIndividual Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.2.28 DL Power 9.2.1.21A 9.2.2.21a 9.2.1.49 DL Power 9.2.1.21A 9.2.2.23 9.2.2.B 9.2.2.C Semantics Description Criticality YES YES YES YES EACH YES YES YES ignore ignore ignore Assigned Criticality ignore ignore ignore ignore ignore

1..<maxno ofRLs>

Condition Common Individual CommonOrIndividual

Explanation The IE shall be present if the Power Adjustment Type IE is set to Common. The IE shall be present if the Power Adjustment Type IE is set to Individual. The IE shall be present if the Power Adjustment Type IE is set to Common or Individual. Explanation Maximum number of RLs for one UE.

Range Bound maxnoofRLs

9.1.21 PHYSICAL CHANNEL RECONFIGURATION REQUEST

9.1.21.1 FDD Message
Presence M M 1 M M 9.2.1.49 FDD DL Code Information 9.2.2.14A 9.2.2.85 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES YES YES Assigned Criticality reject reject notify IE/Group Name Message Type Transaction ID RL Information >RL ID >DL Code Information

>F-DPCH Slot Format

YES

Ignore

3GPP

Release 11

365

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.21.2

TDD Message

3GPP

Release 11

366

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID RL Information >RL ID >UL CCTrCH Information

Presence M M 1 M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.49

Semantics Description

Criticality YES YES GLOBAL

Assigned Criticality reject reject reject

0.. <maxnoof CCTrCHs > M 1 O O O 0..<maxno OfTS> M O O O 9.2.1.56 9.2.3.4 9.2.1.55 TDD UL Code Information 9.2.3.10A 0..<maxno OfTSLCR > M O O O 9.2.3.12a 9.2.3.4C 9.2.1.55 TDD UL Code Information LCR 9.2.3.10B 9.2.3.17 0..<maxno OfTS> M O O O 9.2.1.56 9.2.3.23 9.2.1.55 TDD UL Code Information 9.2.3.27 0..<maxno ofCCTrCH s> M 1 O O O 0..<maxno OfTS> M 9.2.1.56 9.2.3.7 9.2.3.6 9.2.3.8A Applicable to 3.84Mcps TDD only 9.2.3.2 Applicable to 7.68Mcps TDD only Applicable to 1.28Mcps TDD only 9.2.3.7 9.2.3.6 9.2.3.8A Applicable to 3.84Mcps TDD only 9.2.3.2

>>CCTrCH ID >>UL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>UL Timeslot Information >>>>Time Slot >>>>Midamble Shift And Burst Type >>>>TFCI Presence >>>>UL Code Information >>>UL Timeslot Information LCR >>>>Time Slot LCR >>>>Midamble Shift LCR >>>>TFCI Presence >>>>UL Code Information LCR

YES

notify

GLOBAL

reject

>>>>PLCCH Information >>>UL Timeslot Information 7.68Mcps >>>>Time Slot >>>>Midamble Shift And Burst Type 7.68Mcps >>>>TFCI Presence >>>>UL Code Information 7.68Mcps >DL CCTrCH Information >>CCTrCH ID >>DL DPCH Information >>>Repetition Period >>>Repetition Length >>>TDD DPCH Offset >>>DL Timeslot Information >>>>Time Slot

YES GLOBAL

Reject reject

GLOBAL YES

reject

notify

3GPP

Release 11

367

3GPP TS 25.423 V11.2.0 (2012-06)

>>>>Midamble Shift And Burst Type >>>>TFCI Presence >>>>DL Code Information >>>DL Timeslot Information LCR >>>>Time Slot LCR >>>>Midamble Shift LCR >>>>TFCI Presence >>>>DL Code Information LCR

O O O

9.2.3.4 9.2.1.55 TDD DL Code Information 9.2.3.8C 0..<maxno OfTSLCR > Applicable to 1.28Mcps TDD only 9.2.3.12a 9.2.3.4C 9.2.1.55 TDD DL Code Information LCR 9.2.3.8D 0..<maxno OfTS> Applicable to 7.68Mcps TDD only 9.2.1.56 9.2.3.23 9.2.1.55 TDD DL Code Information 7.68Mcps 9.2.3.29 0..<maxno ofDLts> Applicable to 3.84Mcps TDD only. 9.2.1.56 9.2.3.4 0..<maxno ofDLtsLCR > Applicable to 1.28Mcps TDD only 9.2.3.12a 9.2.3.4C 0..<maxno ofDLts> Applicable to 7.68Mcps TDD only. 9.2.1.56 9.2.3.23 9.2.1.66 Applicable to 1.28Mcps TDD only. Explanation

GLOBAL

reject

M O O O

>>>DL Timeslot Information 7.68Mcps >>>>Time Slot >>>>Midamble Shift And Burst Type 7.68Mcps >>>>TFCI Presence >>>>DL Code Information 7.68Mcps M O O O

GLOBAL

reject

>HS-PDSCH Timeslot Specific Information >>Time Slot >>Midamble Shift And Burst Type >HS-PDSCH Timeslot Specific Information LCR >>Time Slot LCR >>Midamble Shift LCR >HS-PDSCH Timeslot Specific Information 7.68Mcps >>Time Slot >>Midamble Shift And Burst Type 7.68Mcps >UARFCN M M

GLOBAL GLOBAL GLOBAL YES

reject

reject

M M

reject

M M O

ignore

Range bound maxnoofCCTrCHs maxnoofTS maxnoofTSLCR maxnoofDLts maxnoofDLtsLCR

Maximum number of CCTrCHs for a UE. Maximum number of Timeslots for a UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of Timeslots for a UE for 1.28Mcps TDD. Maximum number of downlink time slots per Radio Link for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD.

3GPP

Release 11

368

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.22 PHYSICAL CHANNEL RECONFIGURATION COMMAND

IE/Group Name Message Type Transaction ID CFN Criticality Diagnostics Presence M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.9 9.2.1.13 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore ignore

9.1.23 PHYSICAL CHANNEL RECONFIGURATION FAILURE

IE/Group Name Message Type Transaction ID Cause Criticality Diagnostics Presence M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore ignore

9.1.24 UPLINK SIGNALLING TRANSFER INDICATION

9.1.24.1 FDD Message
Presence M M M M O M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.71 9.2.1.52 9.2.1.5A 9.2.1.14 9.2.1.53 Semantics Description Criticality YES YES YES YES YES YES Assigned Criticality ignore ignore ignore ignore ignore ignore IE/Group Name Message Type Transaction ID UC-ID SAI Cell GAI C-RNTI S-RNTI

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

D-RNTI Propagation Delay STTD Support Indicator Closed Loop Mode1 Support Indicator L3 Information CN PS Domain Identifier CN CS Domain Identifier URA Information Cell GA Additional Shapes DPC Mode Change Support Indicator Common Transport Channel Resources Initialisation Not Required

O M M M M O O O O O O

9.2.1.24 9.2.2.33 9.2.2.45 9.2.2.2 9.2.1.32 9.2.1.12 9.2.1.11 9.2.1.70B 9.2.1.5B 9.2.2.56 9.2.1.12F

YES YES YES YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore Ignore

3GPP

Release 11

369

3GPP TS 25.423 V11.2.0 (2012-06)

Cell Capability Container FDD SNA Information Cell Portion ID Active MBMS Bearer Service List >TMGI >Transmission Mode Inter-frequency Cell List >DL UARFCN >UL UARFCN >Primary Scrambling Code Extended Propagation Delay HS-DSCH-RNTI Multiple PLMN List E-RNTI Max UE DTX Cycle Cell Capability Container FDD Extension Secondary Serving Cell List Dual Band Secondary Serving Cell List Extended S-RNTI

O O O 0..<max noofActi veMBM S> M M 0..<max CellsMe as> M O M O O O O C-DTXDRXCapab ility O O O

9.2.2.D 9.2.1.52Ca 9.2.2.E

YES YES YES GLOBAL

ignore ignore ignore ignore

9.2.1.80 9.2.1.81

GLOBAL YES YES YES YES YES YES YES YES

ignore

UARFCN 9.2.1.66 UARFCN 9.2.1.66 9.2.1.45 9.2.2.33a 9.2.1.30P 9.2.1.117 9.2.1.94 9.2.2.87 9.2.2.123 9.2.2.101 Secondary Serving Cell List 9.2.2.101 9.2.1.154

ignore ignore ignore ignore ignore ignore ignore ignore

The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES

ignore

Condition DTX-DRXCapability

Explanation The IE shall be present if the Continuous Packet Connectivity DTX-DRX Support Indicator IE in Cell Capability Container FDD IE is set to 1. Explanation Maximum number of MBMS bearer services that are active in parallel. Maximum number of inter-frequency cells measured by a UE.

Range bound maxnoofActiveMBMS maxCellsMeas

3GPP

Release 11

370

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.24.2

TDD Message

3GPP

Release 11

371

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID UC-ID SAI Cell GAI C-RNTI S-RNTI

Presence M M M M O M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.71 9.2.1.52 9.2.1.5A 9.2.1.14 9.2.1.53

Semantics Description

Criticality YES YES YES YES YES YES

Assigned Criticality ignore ignore ignore Ignore ignore ignore

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

D-RNTI Rx Timing Deviation L3 Information CN PS Domain Identifier CN CS Domain Identifier URA Information Cell GA Additional Shapes Common Transport Channel Resources Initialisation Not Required Cell Capability Container TDD Cell Capability Container TDD LCR SNA Information Active MBMS Bearer Service List >TMGI >Transmission Mode Cell Capability Container 7.68Mcps TDD Rx Timing Deviation 7.68Mcps Rx Timing Deviation 3.84Mcps Extended Multiple PLMN List HS-DSCH-RNTI E-RNTI Cell Portion LCR ID Cell Capability Container Extension TDD LCR

O M M O O O O O O O O 0..<max noofActi veMBM S> M M O O O O O O O O

9.2.1.24 9.2.3.7A 9.2.1.32 9.2.1.12 9.2.1.11 9.2.1.70B 9.2.1.5B 9.2.1.12F 9.2.3.1a 9.2.3.1b 9.2.1.52Ca Applicable to 3.84Mcps TDD only Applicable to 1.28Mcps TDD only

YES YES YES YES YES YES YES YES YES YES YES GLOBAL

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

9.2.1.80 9.2.1.81 9.2.3.31 9.2.3.30 9.2.3.35 9.2.1.117 9.2.1.30P 9.2.1.94 9.2.3.73 9.2.3.80

Applicable to 7.68Mcps TDD only Applicable to 7.68Mcps TDD only Applicable to 3.84Mcps TDD only

YES YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore ignore

Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only

3GPP

Release 11

372

3GPP TS 25.423 V11.2.0 (2012-06)

Extended S-RNTI

9.2.1.154

The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES

ignore

Range bound maxnoofActiveMBMS

Explanation Maximum number of MBMS bearer services that are active in parallel.

9.1.24A GERAN UPLINK SIGNALLING TRANSFER INDICATION

IE/Group Name Message Type Transaction ID UC-ID SAI S-RNTI Presence M M M M M Range IE type and reference 9.2.1.40 9.2.1.59 9.2.1.71 9.2.1.52 9.2.1.53 Semantics description Criticality YES YES YES YES Assigned Criticality ignore ignore ignore ignore

UC-ID may be a GERAN cell identifier. If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

D-RNTI L3 Information CN PS Domain Identifier CN CS Domain Identifier URA Information

O M O O O

9.2.1.24 9.2.1.32 9.2.1.12 9.2.1.11 9.2.1.70B

Extended S-RNTI

9.2.1.154

URA information may be GRA information The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES YES YES YES YES

ignore ignore ignore ignore ignore

YES

ignore

3GPP

Release 11

373

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.25 DOWNLINK SIGNALLING TRANSFER REQUEST

IE/Group Name Message Type Transaction ID C-ID D-RNTI L3 Information D-RNTI Release Indication URA-ID MBMS Bearer Service List >TMGI Old URA-ID SRNC-ID Presence M M M M M M O 0..<maxno ofMBMS> M O C-URA 9.2.1.80 URA-ID 9.2.1.70 RNC-ID 9.2.1.50 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.6 9.2.1.24 9.2.1.32 9.2.1.25 9.2.1.70 Semantics Description Criticality YES YES YES YES YES YES GLOBAL YES If the Extended SRNC-ID IE is included in the message, the SRNCID IE shall be ignored. The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. FDD and 1.28Mcps TDD only YES Assigned Criticality ignore ignore ignore ignore ignore ignore ignore ignore ignore

May be a GERAN cell identifier

Extended SRNC-ID

Extended RNC-ID 9.2.1.50a

YES

reject

Enhanced PCH Capability

9.2.1.132

YES

Ignore

Condition URA Range bound maxnoofMBMS

Explanation The IE shall be present if the URA-ID IE or Old URA-ID IE is present. Explanation Maximum number of MBMS bearer services that a UE can join.

9.1.26 RELOCATION COMMIT

IE/Group Name Message Type Transaction ID D-RNTI RANAP Relocation Information Presence M M O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.47 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

3GPP

Release 11

374

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.27 PAGING REQUEST

IE/Group Name Message Type Transaction ID CHOICE Paging Area >URA >>URA-ID >Cell >>C-ID SRNC-ID Presence M M M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.70 9.2.1.6 RNC-ID 9.2.1.50 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore

May be a GRA-ID. UTRAN only May be a BSC-ID. If the Extended SRNC-ID IE is included in the message, the SRNCID IE shall be ignored. If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

ignore

S-RNTI

9.2.1.53

YES

ignore

IMSI DRX Cycle Length Coefficient CN Originated Page to Connected Mode UE >Paging Cause >CN Domain Type >Paging Record Type Extended SRNC-ID

M M 0..1 M M M O

9.2.1.31 9.2.1.26 9.2.1.41E 9.2.1.11A 9.2.1.41F Extended RNC-ID 9.2.1.50a

YES YES YES YES

ignore ignore ignore

Enhanced PCH Capability Extended S-RNTI

O O

9.2.1.132 9.2.1.154

The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. FDD and 1.28Mcps TDD only The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

reject

YES YES

Ignore ignore

3GPP

Release 11

375

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.28 DEDICATED MEASUREMENT INITIATION REQUEST

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Dedicated Measurement Object Type >RL >>RL Information >>>RL-ID >>>DPCH ID >>>DPCH ID 7.68Mcps >>>HS-SICH Information >>>>HS-SICH ID >RLS >>RL Set Information >>>RL-Set-ID >ALL RL >ALL RLS Dedicated Measurement Type Measurement Filter Coefficient Report Characteristics CFN reporting indicator M 1..<maxn oofRLSet s> M 9.2.2.35 NULL NULL 9.2.1.18 9.2.1.36 9.2.1.48 FN reporting indicator 9.2.1.28A 9.2.1.9 9.2.1.41Fa 9.2.1.38A 9.2.1.2D FDD only Presence M M M M 1..<maxn oofRLs> M O O 0..<maxn oofHSSI CHs> 9.2.3.3ad FDD only 9.2.1.49 9.2.3.3 9.2.3.34 TDD only 7.68Mcps TDD only TDD only Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES YES EACH GLOBAL EACH YES YES YES YES reject Assigned Criticality reject reject reject reject

reject

M O M M

reject reject reject reject

CFN Partial Reporting Indicator Measurement Recovery Behavior Alternative Format Reporting Indicator Range bound maxnoofRLs maxnoofRLSets

O O O O

YES YES YES YES

reject ignore ignore ignore

Explanation Maximum number of individual RLs a measurement can be started on. Maximum number of individual RL Sets a measurement can be started on.

3GPP

Release 11

376

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.29 DEDICATED MEASUREMENT INITIATION RESPONSE

3GPP

Release 11

377

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Dedicated Measurement Object Type

Presence M M M O

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37

Semantics Description

Criticality YES YES YES

Assigned Criticality reject ignore ignore

>RL or ALL RL >>RL Information >>>RL ID >>>DPCH ID >>>DPCH ID 7.68Mcps >>>Dedicated Measurement Value >>>CFN M O O M O

Dedicated Measurement Object Type the measurement was initiated with See Note 1 1..<maxno ofRLs> 9.2.1.49 9.2.3.3 9.2.3.34 9.2.1.19 9.2.1.9 Dedicated Measuremen t Time Reference TDD only Applicable to 3.84Mcps TDD only TDD only 7.68Mcps TDD only

EACH _

ignore

>>>HS-SICH ID >>>Multiple Dedicated Measurement Value Information >>>>DPCH ID >>>>Dedicated Measurement Value >>>Multiple Dedicated Measurement Value Information LCR >>>>DPCH ID >>>>Dedicated Measurement Value >>>Multiple HS-SICH Measurement Value Information >>>>HS-SICH ID >>>>Dedicated Measurement Value >>>Multiple Dedicated Measurement Value Information 7.68Mcps >>>>DPCH ID 7.68Mcps >>>>Dedicated Measurement Value >RLS or ALL RLS >>RL Set Information >>>RL Set ID >>>Dedicated Measurement Value

O 0..<maxno ofDPCHsP erRL-1> M M 0..<maxno ofDPCHsL CRPerRL1> M M 0..<maxno ofHSSICH s -1> M M 0..<maxno ofDPCHs7 68PerRL1> M M

9.2.3.3ad

YES GLOBAL

reject ignore

9.2.3.3 9.2.1.19 Applicable to 1.28McpsTD D only 9.2.3.3 9.2.1.19 TDD only

GLOBAL ignore

GLOBAL ignore

9.2.3.3ad 9.2.1.19 Applicable to 7.68Mcps TDD only 9.2.3.34 9.2.1.19 FDD only See Note 2 1..<maxno ofRLSets>

GLOBAL ignore

EACH ignore

M M

9.2.2.35 9.2.1.19

3GPP

Release 11

378

3GPP TS 25.423 V11.2.0 (2012-06)

>>>CFN

9.2.1.9

Dedicated Measuremen t Time Reference

Criticality Diagnostics O 9.2.1.13 YES Ignore Measurement Recovery O 9.2.1.38C YES ignore Support Indicator Note 1: This is a simplified representation of the ASN.1: there are two different choice tags RL and ALL RL in the ASN.1, each having exactly the same structure. Note 2: This is a simplified representation of the ASN.1: there are two different choice tags RLS and ALL RLS in the ASN.1, each having exactly the same structure. Range bound maxnoofRLs maxnoofRLSets maxnoofDPCHsPerRL maxnoofDPCHsLCRPerRL maxnoofHSSICHs maxnoofDPCHs768PerRL
Explanation

Maximum number of individual RLs the measurement can be started on. Maximum number of individual RL Sets the measurement can be started on. Maximum number of DPCHs per RL a measurement can be started on for 3.84Mcps TDD Maximum number of DPCHs per RL a measurement can be started on for 1.28Mcps TDD Maximum number of HSSICHs per RL a measurement can be started on Maximum number of DPCHs per RL a measurement can be started on for 7.68Mcps TDD

3GPP

Release 11

379

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.30 DEDICATED MEASUREMENT INITIATION FAILURE

IE/Group Name Message Type Transaction ID Measurement ID Cause Criticality Diagnostics CHOICE Dedicated Measurement Object Type Presence M M M M O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES YES YES Assigned Criticality reject ignore ignore ignore ignore

Dedicated Measuremen t Object Type the measuremen t was initiated with 1..<maxno ofRLs>

>RL or ALL RL >>Unsuccessful RL Information >>>RL ID >>>Individual Cause >>Successful RL Information >>>RL ID >>>DPCH ID >>>Dedicated Measurement Value >>>CFN

EACH 9.2.1.49 Cause 9.2.1.5 EACH 9.2.1.49 9.2.3.3 9.2.1.19 9.2.1.9 TDD only Dedicated Measuremen t Time Reference TDD only FDD only _

ignore

M O 0..<maxno ofRLs-1> M O M O

ignore

>>>HS-SICH ID >RLS or ALL RLS >>Unsuccessful RL Set Information >>>RL Set ID >>>Individual Cause >>Successful RL Set Information >>>RL Set ID >>>Dedicated Measurement Value >>>CFN

O 1..<maxno ofRLSets> M O 0..<maxno ofRLSets1> M M O

9.2.3.3ad

YES EACH EACH

reject ignore

9.2.2.35 Cause 9.2.1.5

ignore

9.2.2.35 9.2.1.19 9.2.1.9 Dedicated Measuremen t Time Reference

Explanation

Range bound maxnoofRLs maxnoofRLSets

Maximum number of individual RLs the measurement can be started on. Maximum number of individual RL Sets the measurement can be started on.

3GPP

Release 11

380

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.31 DEDICATED MEASUREMENT REPORT

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Dedicated Measurement Object Type Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

>RL or ALL RL >>RL Information >>>RL-ID >>>DPCH ID >>>DPCH ID 7.68Mcps >>>Dedicated Measurement Value Information >>>HS-SICH ID >RLS or ALL RLS >>RL Set Information M O O M O

Dedicated Measuremen t Object Type the measuremen t was initiated with See Note 1 1..<maxnoo fRLs> 9.2.1.49 9.2.3.3 9.2.3.34 9.2.1.19A 9.2.3.3ad TDD only FDD only See Note 2 TDD only 7.68Mcps TDD only

EACH YES EACH

ignore

ignore

1..<maxnoo fRLSets>

ignore

>>>RL Set ID M 9.2.2.35 >>>Dedicated M 9.2.1.19A Measurement Value Information Measurement Recovery O 9.2.1.38B YES ignore Reporting Indicator Note 1: This is a simplified representation of the ASN.1: there are two different choice tags RL and ALL RL in the ASN.1, each having exactly the same structure. Note 2: This is a simplified representation of the ASN.1: there are two different choice tags RLS and ALL RLS in the ASN.1, each having exactly the same structure. Range bound maxnoofRLs maxnoofRLSets Explanation Maximum number of individual RLs the measurement can be started on. Maximum number of individual RL Sets the measurement can be started on.

9.1.32 DEDICATED MEASUREMENT TERMINATION REQUEST

IE/Group Name Message Type Transaction ID Measurement ID Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

3GPP

Release 11

381

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.33 DEDICATED MEASUREMENT FAILURE INDICATION

IE/Group Name Message Type Transaction ID Measurement ID Cause CHOICE Dedicated Measurement Object Type Presence M M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 Semantics Description Criticality YES YES YES YES Assigned Criticality ignore ignore ignore ignore

Dedicated Measuremen t Object Type the measuremen t was initiated with 1..<maxnoof RLs>

>RL or ALL RL >>Unsuccessful RL Information >>>RL ID >>>Individual Cause >RLS or ALL RLS >>Unsuccessful RL Set Information >>>RL Set ID >>>Individual Cause

EACH 9.2.1.49 Cause 9.2.1.5 FDD only EACH

ignore

M O 1..<maxnoof RLSets> M O

ignore

9.2.2.35 Cause 9.2.1.5

Explanation

Range bound maxnoofRLs maxnoofRLSets

Maximum number of individual RLs the measurement can be started on. Maximum number of individual RL Sets the measurement can be started on.

9.1.34 COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST

IE/Group Name Message Type Transaction ID D-RNTI Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

3GPP

Release 11

382

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.35 COMMON TRANSPORT CHANNEL RESOURCES REQUEST

IE/Group Name Message Type Transaction ID D-RNTI C-ID Transport Bearer Request Indicator Presence M M M O M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.6 9.2.1.61 Semantics Description Criticality YES YES YES YES Assigned Criticality reject reject reject reject

Transport Bearer ID

9.2.1.60

Request a new transport bearer or to use an existing bearer for the user plane. Indicates the Iur transport bearer to be used for the user plane. Shall be ignored if bearer establishme nt with ALCAP. Shall be ignored if bearer establishme nt with ALCAP.

YES

reject

Permanent NAS UE Identity Binding ID

O O

9.2.1.73 9.2.1.3

YES YES

ignore ignore

Transport Layer Address

9.2.1.62

YES

ignore

MBMS Bearer Service List >TMGI TNL QoS M O

0..<max noofMB MS> 9.2.1. 80 9.2.1.56A Shall be ignored if bearer establishme nt with ALCAP. FDD and 1.28Mcps TDD only FDD only

GLOBAL YES

notify

ignore

Enhanced FACH Support Indicator Common E-DCH Support Indicator HS-DSCH Physical Layer Category UE with enhanced HSSCCH support indicator

O O O O

9.2.1.131 9.2.2.92 9.2.1.30Oa NULL

YES YES Yes

Ignore Ignore Ignore ignore

UE supports enhanced HS-SCCH functionality: - UE supports different HSSCCH in consecutive TTIs

YES

3GPP

Release 11

383

3GPP TS 25.423 V11.2.0 (2012-06)

Range bound maxnoofMBMS

Explanation Maximum number of MBMS bearer services that a UE can join.

3GPP

Release 11

384

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.36 COMMON TRANSPORT CHANNEL RESOURCES RESPONSE

9.1.36.1 FDD Message

3GPP

Release 11

385

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID S-RNTI

Presence M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.53

Semantics Description

Criticality YES YES

Assigned Criticality reject ignore

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

C-RNTI FACH Info for UE Selected S-CCPCH >FACH Flow Control Information

O 1 M

9.2.1.14 9.2.1.26C If the Enhanced FACH Information Response IE is included in the message, the FACH Flow Control Information IE shall be ignored.

YES YES YES

ignore ignore ignore

Transport Layer Address Binding Identity Criticality Diagnostics C-ID Active MBMS Bearer Service List >TMGI >Transmission Mode Enhanced FACH Information Response >Common HS-DSCHRNTI Priority Queue Information for Enhanced FACH

O O O M 0..<maxno ofActiveMB MS> M M 0..1 M

9.2.1.62 9.2.1.3 9.2.1.13 9.2.1.6

YES YES YES YES GLOBAL YES

ignore ignore ignore ignore ignore

9.2.1.80 9.2.1.81 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 9.2.1.30Na

ignore

>Dedicated HS-DSCHRNTI Priority Queue Information for Enhanced FACH

>Priority Queue Information for Enhanced PCH

>HS-DSCH Initial Capacity Allocation

3GPP

Release 11

386

3GPP TS 25.423 V11.2.0 (2012-06)

>HS-DSCH-RNTI Common E-DCH MAC-d Flow Specific Information E-RNTI Extended S-RNTI

O O O O

9.2.1.30P 9.2.2.93 9.2.1.94 9.2.1.154 The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES YES ignore ignore

Range bound maxnoofActiveMBMS

Explanation Maximum number of MBMS bearer services that are active in parallel.

3GPP

Release 11

387

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.36.2

TDD Message

3GPP

Release 11

388

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID S-RNTI

Presence M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.53

Semantics Description

Criticality YES YES

Assigned Criticality reject ignore

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored.

C-RNTI FACH Info for UE Selected S-CCPCHs >FACH Flow Control Information

O 1 M

9.2.1.14 9.2.1.26C If the Enhanced FACH Information Response IE is included in the message, the FACH Flow Control Information IE shall be ignored.

YES YES YES

ignore ignore ignore

Transport Layer Address Binding Identity Criticality Diagnostics C-ID Active MBMS Bearer Service List >TMGI >Transmission Mode Enhanced FACH Information Response >Common HS-DSCHRNTI Priority Queue Information for Enhanced FACH

O O O M 0..<maxno ofActiveMB MS> M M 0.. 1 M

9.2.1.62 9.2.1.3 9.2.1.13 9.2.1.6

YES YES YES YES GLOBAL YES

ignore ignore ignore ignore ignore

9.2.1.80 9.2.1.81 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 Priority Queue Information for Enhanced FACH/PC H 9.2.1.133 9.2.1.30Na

ignore

>Dedicated HS-DSCHRNTI Priority Queue Information for Enhanced FACH

>Priority Queue Information for Enhanced PCH

>HS-DSCH Initial Capacity Allocation

3GPP

Release 11

389

3GPP TS 25.423 V11.2.0 (2012-06)

>HS-DSCH-RNTI Common E-DCH MAC-d Flow Specific Information LCR Extended S-RNTI

O O O

9.2.1.30P 9.2.3.58 9.2.1.154 The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES YES

ignore ignore

Range bound maxnoofActiveMBMS

Explanation Maximum number of MBMS bearer services that are active in parallel.

9.1.37 COMMON TRANSPORT CHANNEL RESOURCES FAILURE

IE/Group Name Message Type Transaction ID S-RNTI Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.53 Semantics Description Criticality YES YES Assigned Criticality reject ignore

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored. The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

Cause Criticality Diagnostics Extended S-RNTI

M O O

9.2.1.5 9.2.1.13 9.2.1.154

YES YES YES

ignore ignore ignore

9.1.38 COMPRESSED MODE COMMAND [FDD]

IE/Group Name Message Type Transaction ID Active Pattern Sequence Information Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.2.A Semantics Description Criticality YES YES Assigned Criticality ignore ignore

3GPP

Release 11

390

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.39 ERROR INDICATION

IE/Group Name Message Type Transaction ID Cause Criticality Diagnostics S-RNTI Presence M M O O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 9.2.1.13 9.2.1.53 Semantics Description Criticality YES YES YES YES Assigned Criticality ignore ignore ignore ignore

If the Extended SRNTI IE is included in the message, the S-RNTI IE shall not be included. The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

D-RNTI Extended S-RNTI

O O

9.2.1.24 9.2.1.154

YES YES

ignore ignore

9.1.40 DL POWER TIMESLOT CONTROL REQUEST [TDD]

IE/Group Name Message Type Transaction ID DL Time Slot ISCP Info Presence M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.3.2D Semantics Description Criticality YES YES Assigned Criticality ignore ignore

DL Time Slot ISCP Info LCR

9.2.3.2F

Mandatory for 3.84Mcps TDD and 7.68Mcps TDD, not applicable to 1.28Mcps TDD Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD

YES

ignore

Primary CCPCH RSCP Primary CCPCH RSCP Delta

O O

9.2.3.5 9.2.3.5a

YES YES

ignore ignore

3GPP

Release 11

391

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.41 RADIO LINK PREEMPTION REQUIRED INDICATION

IE/Group Name Message Type Transaction ID RL Information >RL ID >E-DCH MAC-d Flow Specific Information >>E-DCH MAC-d Flow ID HS-DSCH MAC-d Flow Specific Information >HS-DSCH MAC-d Flow ID Presence M M 0..<maxno ofRLs> M 0..<maxno ofEDCHM ACdFlows > M 0..<maxno ofMACdFl ows> M 9.2.1.30O 9.2.1.91 9.2.1.49 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES EACH EACH Assigned Criticality ignore ignore ignore

EACH

ignore

Range bound maxnoofRLs maxnoofMACdFlows maxnoofEDCHMACdFlows

Explanation Maximum number of radio links for one UE Maximum number of HS-DSCH MAC-d flows Maximum number of E-DCH MAC-d flows

9.1.42 RADIO LINK CONGESTION INDICATION

IE/Group Name Message Type Transaction ID Congestion Cause RL Information >RL ID >DCH Rate Information >>DCH ID >>Allowed Rate Information >E-DCH MAC-d Flow Specific Information >>E-DCH MAC-d Flow ID >DCH Indicator For EDCH-HSDPA Operation Presence M M O 1..<maxno ofRLs> M 1..<maxno ofDCHs> M O 0..<maxno ofEDCHM ACdFlows > M O 9.2.1.91 9.2.2.67 9.2.1.16 9.2.1.2A 9.2.1.49 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.79 Semantics Description Criticality YES YES EACH EACH EACH ignore Assigned Criticality ignore ignore ignore ignore

YES

ignore

Range bound maxnoofRLs maxnoofDCHs maxnoofEDCHMACdFlows

Explanation Maximum number of Radio Links for one UE Maximum number of DCHs for one UE. Maximum number of E-DCH MAC-d flows

3GPP

Release 11

392

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.43 COMMON MEASUREMENT INITIATION REQUEST

3GPP

Release 11

393

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Common Measurement Object Type >Cell >>Reference Cell Identifier >>Time Slot

Presence M M M M M

Range

IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37

Semantics Description

Criticality YES YES YES

Assigned Criticality reject reject reject

UTRAN Cell Identifier 9.2.1.71 9.2.1.56

May be a GERAN Cell Identifier 3.84Mcps TDD and 7.68 Mcps TDD only 1.28Mcps TDD only UTRAN only

>>Time Slot LCR >>Neighbouring Cell Measurement Information >>>CHOICE Neighbouring Cell Measurement Information >>>>Neighbourin g FDD Cell Measurement Information >>>>>Neighbo uring FDD Cell Measurement Information >>>>Neighbourin g TDD Cell Measurement Information >>>>>Neighbo uring TDD Cell Measurement Information >>>>Additional Neighbouring Cell Measurement Information >>>>>Neighbo uring TDD Cell Measurement InformationLC R >>>>>>Neig hbouring TDD Cell Measureme nt InformationL CR >>>>Additional Neighbouring Cell Measurement Information 7.68Mcps

O 0..<maxnoof MeasNCells >

9.2.3.12a

FDD only

9.2.1.41G

3.84Mcps TDD only M 9.2.1.41H

1.28Mcps TDD only

9.2.1.41Dd

YES

reject

3GPP

Release 11

394

3GPP TS 25.423 V11.2.0 (2012-06)

>>>>>Neighbo uring TDD Cell Measurement Information 7.68 Mcps >>>>>>Neig hbouring TDD Cell Measureme nt Information 7.68 Mcps >>UARFCN >>UpPCH Position LCR >Additional Common Measurement Object Types >>GSM Cell >>>CGI Common Measurement Type Measurement Filter Coefficient Report Characteristics SFN reporting indicator

7.68Mcps TDD only

9.2.3.32

YES

reject

O O

9.2.1.66 9.2.3.56

Applicable to 1.28Mcps TDD only. Applicable to 1.28Mcps TDD only. Applicable to 1.28Mcps TDD only

YES YES YES YES

ignore ignore

ignore reject reject reject reject

M M O M M

9.2.1.5D 9.2.1.12C 9.2.1.36 9.2.1.48 FN reporting indicator 9.2.1.28A 9.2.1.52A 9.2.1.12A 9.2.1.38A 9.2.1.119a UTRAN only

YES YES YES

SFN Common Measurement Accuracy Measurement Recovery Behavior GANSS Time ID

O O O O

UTRAN only UTRAN only UTRAN only This IE may only be present if the Common Measureme nt Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning. If the Common Measureme nt Type IE is set to UTRAN GANSS Timing of Cell Frames for UE Positioning and this IE is absent, the GANSS time is Galileo system time.

YES YES YES YES

reject reject ignore ignore

3GPP

Release 11

395

3GPP TS 25.423 V11.2.0 (2012-06)

Extension Common Measurement Object Type >GsmCellList >>Measurement ID >>GSM Cell >>>CGI

O 1..<maxNoO fGsmCell> M M 9.2.1.37 9.2.1.5D

Applicable to 1.28Mcps TDD only

YES YES

ignore ignore

Range bound maxnoofMeasNCell maxNoOfGsmCell

Explanation Maximum number of neighbouring cells on which measurements can be performed. Maximum number of GSM Cells in one message

9.1.44 COMMON MEASUREMENT INITIATION RESPONSE

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Common Measurement Object Type Presence M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore ignore

Common Measuremen t Object Type that the measuremen t was initiated with. 9.2.1.12D 9.2.1.52A Common Measuremen t Time Reference, UTRAN only. UTRAN only

>Cell >>Common Measurement value SFN

M O

YES ignore

Criticality Diagnostics Common Measurement Achieved Accuracy

O O

Measurement Recovery Support Indicator Extension Common Measurement Object Type >GsmCellList >>Measurement ID >>Common Measurement value

O O 1..<maxNoO fGsmCell> M O

9.2.1.13 Common Measurem ent Accuracy 9.2.1.12A 9.2.1.38C

YES YES

ignore ignore

UTRAN only Applicable to 1.28Mcps TDD only

YES YES YES

ignore ignore ignore

9.2.1.37 9.2.1.12D

Range bound maxNoOfGsmCell

Explanation Maximum number of GSM Cells in one message

3GPP

Release 11

396

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.45 COMMON MEASUREMENT INITIATION FAILURE

IE/Group Name Message Type Transaction ID Measurement ID Cause Criticality Diagnostics Extension Measurement IdList >Measurement ID >Cause Presence M M M M O 0..<maxNoO fGsmCell> M M 9.2.1.37 9.2.1.5 Explanation Maximum number of GSM Cells in one message Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES YES YES Assigned Criticality reject ignore ignore ignore ignore

Applicable to 1.28Mcps TDD only

Range bound maxNoOfGsmCell

9.1.46 COMMON MEASUREMENT REPORT

IE/Group Name Message Type Transaction ID Measurement ID CHOICE Common Measurement Object Type Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

Common Measuremen t Object Type that the measuremen t was initiated with. 9.2.1.12E 9.2.1.52A Common Measuremen t Time Reference, UTRAN only. UTRAN only Applicable to 1.28Mcps TDD only 1..<maxNoO fGsmCell> 9.2.1.37 9.2.1.12D

>Cell >>Common Measurement Value Information SFN

M O

YES ignore

Measurement Recovery Reporting Indicator Extension Common Measurement Object Type >GsmCellList >>Measurement ID >>Common Measurement value

O O

9.2.1.38B

YES YES YES

ignore ignore ignore

M O

Range bound maxNoOfGsmCell

Explanation Maximum number of GSM Cells in one message

3GPP

Release 11

397

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.47 COMMON MEASUREMENT TERMINATION REQUEST

IE/Group Name Presence M M M 0..<maxNoO fGsmCell> M 9.2.1.37 Explanation Maximum number of GSM Cells in one message Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

Message Type Transaction ID Measurement ID Extension Measurement IdList >Measurement ID

Applicable to 1.28Mcps TDD only

Range bound maxNoOfGsmCell

9.1.48 COMMON MEASUREMENT FAILURE INDICATION

IE/Group Name Presence M M M M 0..<maxNoO fGsmCell> M M 9.2.1.37 9.2.1.5 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 Semantics Description Criticality YES YES YES YES Assigned Criticality ignore ignore ignore ignore

Message Type Transaction ID Measurement ID Cause Extension Measurement IdList >Measurement ID >Cause

Applicable to 1.28Mcps TDD only

Range bound maxNoOfGsmCell

Explanation Maximum number of GSM Cells in one message

3GPP

Release 11

398

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.49 INFORMATION EXCHANGE INITIATION REQUEST

IE/Group Name Message Type Transaction ID Information Exchange ID CHOICE Information Exchange Object Type >Cell >>C-ID >Additional Information Exchange Object Types >>GSM Cell >>>CGI >>MBMS Bearer Service >>>MBMS Bearer Service List >>>>TMGI >>MBMS Bearer Service in MBMS Cell >>>MBMS Cell List >>>>C-ID Presence M M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A Semantics Description Criticality YES YES YES May be a GERAN cell identifier M 1..<maxno ofMBMS> M 1..<maxno ofcell> M 9.2.1.6 Cell identifier of cell in RNC initiating Information Exchange Initiation procedure 9.2.1.80 FDD only 9.2.1.5D GLOBAL GLOBAL reject reject Assigned Criticality reject reject reject

9.2.1.6

>>>>MBMS Bearer Service List >>>>>TMGI >>MBMS Cell >>>MBMS Cell List >>>>C-ID

1..<maxno ofMBMS> M 1..<maxno ofcell> M 9.2.1.6 Cell identifier of cell in receiving RNC not initiating Information Exchange Initiation procedure 9.2.1.80 FDD only

GLOBAL reject

>>ANR Cell >>>ANR Cell List >>>>C-ID Information Type Information Report Characteristics M M M

1..<maxno ofanrcelll> 9.2.1.6 9.2.1.31E 9.2.1.31C

YES YES reject reject

Range bound maxnoofMBMS Maxnoofcell maxnoofanrcell

Explanation Maximum number of MBMS bearer services that a UE can join. Maximum number of cells that can be indicated in the corresponding IE. Maximum number of ANR neighbour cells

3GPP

Release 11

399

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.50 INFORMATION EXCHANGE INITIATION RESPONSE

IE/Group Name Message Type Transaction ID Information Exchange ID CHOICE Information Exchange Object Type >Cell >>Requested Data Value >Additional Information Exchange Object Types >>MBMS Bearer Service >>>MBMS Bearer Service List >>>>TMGI >>>>Requested Data Value >>MBMS Bearer Service in MBMS Cell >>>MBMS Cell List >>>>C-ID Presence M M M O M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A Semantics Description Criticality YES YES YES 1..<maxno ofMBMS> M M 9.2.1.80 9.2.1.48A FDD only 1..<maxno ofcell> M 9.2.1.6 Cell identifier of cell in RNC initiating Information Exchange Initiation procedure GLOBAL GLOBAL ignore ignore Assigned Criticality reject ignore ignore

9.2.1.48A

>>>>MBMS Bearer Service List >>>>>TMGI >>>>>Requested Data Value >>MBMS Cell >>>MBMS Cell List >>>>C-ID M M M

1..<maxno ofMBMS> 9.2.1.80 9.2.1.48A FDD only 1..<maxno ofcell> 9.2.1.6 Cell identifier of cell in sending RNC not initiating Information Exchange Initiation procedure

GLOBAL ignore

>>>>Requested Data Value

9.2.1.48A

3GPP

Release 11

400

3GPP TS 25.423 V11.2.0 (2012-06)

>>ANR Cell >>>ANR Cell List >>>>C-ID >>>>Requested Data Value Criticality Diagnostics M M O

1..<maxno ofanrcell> 9.2.1.6 9.2.1.48A 9.2.1.13

YES ignore

Range bound maxnoofMBMS Maxnoofcell maxnoofanrcell

Explanation Maximum number of MBMS bearer services that a UE can join. Maximum number of cells that can be indicated in the corresponding IE. Maximum number of ANR neighbour cells

9.1.51 INFORMATION EXCHANGE INITIATION FAILURE

IE/Group Name Message Type Transaction ID Information Exchange ID Cause Criticality Diagnostics Presence M M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES YES Assigned Criticality reject ignore ignore ignore

3GPP

Release 11

401

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.52 INFORMATION REPORT

IE/Group Name Message Type Transaction ID Information Exchange ID CHOICE Information Exchange Object Type >Cell >>Requested Data Value Information >Additional Information Exchange Object Types >>MBMS Bearer Service in MBMS Cell >>>MBMS Cell List >>>>C-ID Presence M M M M M 9.2.1.48B Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A Semantics Description Criticality YES YES YES FDD only 1..<maxno ofcell> M 9.2.1.6 Cell identifier of cell in receiving RNC initiating Information Exchange Initiation procedure GLOBAL ignore Assigned Criticality ignore ignore ignore

>>>>MBMS Bearer Service List >>>>>TMGI >>>>>Requested Data Value Information >>MBMS Cell >>>MBMS Cell List >>>>C-ID

1..<maxno ofMBMS> M M 9.2.1.80 9.2.1.48B FDD only 1..<maxno ofcell> M 9.2.1.6 Cell identifier of cell in sending RNC not initiating Information Exchange Initiation procedure

GLOBAL ignore

>>>>Requested Data Value Information

9.2.1.48B

Range bound maxnoofMBMS Maxnoofcell

Explanation Maximum number of MBMS bearer services that a UE can join. Maximum number of cells that can be indicated in the corresponding IE.

3GPP

Release 11

402

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.53 INFORMATION EXCHANGE TERMINATION REQUEST

IE/Group Name Message Type Transaction ID Information Exchange ID Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A Semantics Description Criticality YES YES Assigned Criticality ignore ignore

9.1.54 INFORMATION EXCHANGE FAILURE INDICATION

IE/Group Name Message Type Transaction ID Information Exchange ID Cause Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31A 9.2.1.5 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

9.1.55 RESET REQUEST

IE/Group Name Presence Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantic s Descripti on Criticality Assigned Criticality reject

Message Type Transaction ID

M M

YES

3GPP

Release 11

403

3GPP TS 25.423 V11.2.0 (2012-06)

RNC-ID

9.2.1.50

Identity of the sending RNC. If the Extended RNC-ID IE is included in the message, the RNCID IE shall be ignored.

YES

reject

CHOICE Reset Indicator >Context >>Context Information >>>CHOICE Context Type >>>>SRNTI >>>>>S-RNTI

M 1..<maxRe setContext > M M 9.2.1.53 If the Extended S-RNTI IE is included in the message, the SRNTI IE shall not be included.

YES EACH

reject reject

>>>>DRNTI >>>>>D-RNTI >>>>>Additional Context Type >>>>>Extended SRNTI

M M

9.2.1.24 9.2.1.154 See Note 1 The Extende S-RNTI IE shall be used if the SRNTI identity has a value larger than 1048575

YES reject

>All Contexts >Context Group >>Context Group Information

NULL 1..<maxRe setContext Groups>

_ EACH

reject

3GPP

Release 11

404

3GPP TS 25.423 V11.2.0 (2012-06)

If the Extended S-RNTI Group IE is included in the message, the SRNTI Group IE shall be ignored. >>>Extended S-RNTI O 9.2.1.155 The YES reject Group Extended SRNTI Group IE shall be used for S-RNTI identities that have values larger than 1048575 O 9.2.1.50a Identity of YES reject Extended RNC-ID the sending RNC. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. Note 1: This information element is a simplified representation of the ASN.1. The choice is performed through the use of a ProtocolIE-Single-Container and a ProtocolExtensionContainer within the ASN.1. Range bound maxResetContext maxResetContextGroups Explanation Maximum number of contexts that can be reset by one RESET message. Maximum number of context groups that can be reset by one RESET message.

>>>S-RNTI Group

9.2.1.53a

3GPP

Release 11

405

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.56 RESET RESPONSE

IE/Group Name Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.50 Identity of the sending RNC. If the Extended RNC-ID IE is included in the message, the RNC-ID IE shall be ignored. Identity of the sending RNC. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. Semantics Description Criticality YES YES ignore Assigned Criticality reject

Message Type Transaction ID RNC-ID

Criticality Diagnostics Extended RNC-ID

O O

9.2.1.13 9.2.1.50a

YES YES

ignore reject

9.1.57 RADIO LINK ACTIVATION COMMAND

9.1.57.1 FDD Message
Presence M M 1..<maxnoofRL s> M M 9.2.1.49 9.2.1.19Ab Range IE Type and Reference 9.2.1.46 9.2.1.62 Semantics Description Criticality YES EACH Assigned Criticality ignore ignore IE/Group Name Message Type Transaction ID Delayed activation Information >RL ID >Delayed Activation Update

9.1.57.2

TDD Message
Presence M M 1..<maxnoofRL s> M M 9.2.1.49 9.2.1.19Ab Range IE Type and Reference 9.2.1.46 9.2.1.62 Semantics Description Criticality YES EACH Assigned Criticality ignore ignore

IE/Group Name Message Type Transaction ID Delayed activation Information >RL ID >Delayed Activation Update

3GPP

Release 11

406

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.58 RADIO LINK PARAMETER UPDATE INDICATION

9.1.58.1 FDD Message
Presence M M O 0..<max noofRL s> M O O 0..<max noofHS DSCH1> 9.2.1.49 9.2.2.27B 9.2.2.19e For secondary serving HSDSCH cell. Max 7 in this 3GPP release. RL ID 9.2.1.49 9.2.2.19ca 0..<max noofED CH-1> For E-DCH on multiple frequencies in this DRNS. E-DCH on Secondary uplink frequency max 1 in this 3GPP release. 9.2.2.122 ENUMERA TED(Initiat ed, ) 9.2.2.134 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.2.19c Semantic Description Criticality YES YES EACH YES EACH ignore ignore Assigned Criticality ignore ignore ignore IE/Group name Message type Transaction ID HS-DSCH FDD Update Information RL Information >RL Id >Phase Reference Update Indicator E-DCH FDD Update Information Additional HS Cell Information RL Param Upd

>HS-PDSCH RL ID >HS-DSCH FDD Secondary Serving Update Information Additional E-DCH Cell Information RL Param Upd

M O

EACH ignore

>Additional E-DCH FDD Update Information CPC Recovery Report UL CLTD State Update Information Range bound maxnoofHSDSCH-1 maxnoofEDCH-1

M O O

YES YES ignore ignore

Explanation Maximum number of Secondary Serving HS-DSCH cells for one UE. Maximum number of uplink frequencies -1 for E-DCH for one UE

9.1.58.2

TDD Message
Presence M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.3.3ac Semantic Description Criticality YES YES Assigned Criticality ignore ignore

IE/Group name Message type Transaction ID HS-DSCH TDD Update Information

3GPP

Release 11

407

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.59 UE MEASUREMENT INITIATION REQUEST [TDD]

IE/Group Name Message Type Transaction ID Allowed Queing Time Measurement ID UE Measurement Type UE Measurement Timeslot information HCR UE Measurement Timeslot information LCR UE Measurement Timeslot information 7.68Mcps Measurement Filter Coefficient UE Measurement Report Characteristics UE Measurement Parameter Modification Allowed Presence M M O M M O O O O M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.2 9.2.1.37 9.2.3.13Fh 9.2.3.13Fe 9.2.3.13Ff 9.2.3.33 9.2.1.36 9.2.3.13Fc 9.2.3.13Fb Semantics Description Criticality YES YES YES YES YES YES YES YES YES YES Assigned Criticality reject reject reject reject reject reject reject reject reject reject

3.84 Mcps TDD only 1.28 Mcps TDD only 7.68 Mcps TDD only

9.1.60 UE MEASUREMENT INITIATION RESPONSE [TDD]

IE/Group Name Message Type Transaction ID Measurement ID Measurement Filter Coefficient UE Measurement Report Characteristics Criticality Diagnostics Presence M M M O O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.36 9.2.3.13Fc 9.2.1.13 Semantics Description Criticality YES YES YES YES YES Assigned Criticality reject ignore reject reject ignore

9.1.61 UE MEASUREMENT INITIATION FAILURE [TDD]

IE/Group Name Message Type Transaction ID Measurement ID Cause Criticality Diagnostics Presence M M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES YES Assigned Criticality reject ignore ignore ignore

9.1.62 UE MEASUREMENT REPORT [TDD]

IE/Group Name Message Type Transaction ID Measurement ID UE Measurement Value Information Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.3.13Fj Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

3GPP

Release 11

408

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.63 UE MEASUREMENT TERMINATION REQUEST [TDD]

IE/Group Name Message Type Transaction ID Measurement ID Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

9.1.64 UE MEASUREMENT FAILURE INDICATION [TDD]

IE/Group Name Message Type Transaction ID Measurement ID Cause Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.37 9.2.1.5 Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

9.1.65 IUR INVOKE TRACE

IE/Group Name Message Type Transaction ID D-RNTI Trace Reference UE Identity Trace Recording Session Reference List Of Interfaces To Trace >Interface Trace Depth MDT Configuration Trace Collection Entity IP Address Presence M M O M M M 0..maxnoo fInterfaces M M O O ENUMERA TED (Iub, Iur,) 9.2.1.58a 9.2.1.139 9.2.1.62 Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.58c 9.2.1.66A 9.2.1.58b Semantics Description Criticality YES YES YES YES YES EACH YES YES YES ignore ignore ignore Assigned Criticality ignore ignore ignore ignore ignore ignore

Range bound maxnoofInterfaces

Explanation Maximum of Interfaces to be traced.

9.1.66 IUR DEACTIVATE TRACE

IE/Group Name Message Type Transaction ID D-RNTI Trace Reference Presence M M O M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.58c Semantics Description Criticality YES YES YES Assigned Criticality ignore ignore ignore

3GPP

Release 11

409

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.67 MBMS ATTACH COMMAND

IE/Group Name Message Type Transaction ID MBMS Bearer Service List >TMGI CHOICE UE State >CELL_FACH/CELL_PCH >>D-RNTI >URA_PCH >>SRNC-ID Presence M M 1..<maxno ofMBMS> M O M M 9.2.1.80 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES GLOBAL YES Assigned Criticality ignore ignore ignore

9.2.1.24 RNC-ID 9.2.1.50 If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095.

>>URA-ID >>Extended SRNC-ID

M O

9.2.1.70 Extended RNC-ID 9.2.1.50a

YES

reject

Range bound maxnoofMBMS

Explanation Maximum number of MBMS bearer services that a UE can join.

3GPP

Release 11

410

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.68 MBMS DETACH COMMAND

IE/Group Name Message Type Transaction ID MBMS Bearer Service List >TMGI CHOICE UE State >CELL_FACH/CELL_PCH >>D-RNTI >URA_PCH >>SRNC-ID Presence M M 1..<maxno ofMBMS> M O M M 9.2.1.80 Range IE Type and Reference 9.2.1.40 9.2.1.59 Semantics Description Criticality YES GLOBAL YES Assigned Criticality ignore ignore ignore

9.2.1.24 RNC-ID 9.2.1.50 If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095.

>>URA-ID >>Extended SRNC-ID

M O

9.2.1.70 Extended RNC-ID 9.2.1.50a

YES

reject

Range bound maxnoofMBMS

Explanation Maximum number of MBMS bearer services that a UE can join.

3GPP

Release 11

411

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.69 DIRECT INFORMATION TRANSFER

IE/Group Name Message Type Transaction ID RNC-ID Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.50 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

ID of an RNC which initiates the procedure. If the Extended RNC-ID IE is included in the message, the RNC-ID IE shall be ignored. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

Provided Information Extended RNC-ID

M O

9.2.1.85 9.2.1.50a

YES YES

ignore reject

3GPP

Release 11

412

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.70 ENHANCED RELOCATION REQUEST

IE/Group Name Message Type Transaction ID Cause Permanent NAS UE Identity SRNC-ID Presence M M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 9.2.1.73 RNC-ID 9.2.1.50 Semantics Description Criticality YES YES YES YES Assigned Criticality reject reject reject reject

Extended SRNC-ID

Extended RNC-ID 9.2.1.50a

S-RNTI

9.2.1.53

If the Extended SRNC-ID IE is included in the message, the SRNC-ID IE shall be ignored. The Extended SRNC-ID IE shall be used if the RNC identity has a value larger than 4095. If the Extended SRNTI IE is included in the message, the S-RNTI IE shall be ignored. The Extended SRNTI IE shall be used if the S-RNTI identity has a value larger than 1048575.

YES

reject

YES

reject

RANAP Enhanced Relocation Information Request Extended S-RNTI

M O

9.2.1.124 9.2.1.154

YES YES

reject reject

9.1.71 ENHANCED RELOCATION RESPONSE

IE/Group Name Message Type Transaction ID RANAP Enhanced Relocation Information Response Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.125 Semantics Description Criticality YES YES Assigned Criticality reject ignore

3GPP

Release 11

413

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.72 ENHANCED RELOCATION FAILURE

IE/Group Name Message Type Transaction ID Cause Criticality Diagnostics Presence M M M O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 9.2.1.13 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore ignore

9.1.73 ENHANCED RELOCATION CANCEL

IE/Group Name Message Type Transaction ID Cause Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

9.1.74 ENHANCED RELOCATION SIGNALLING TRANSFER

IE/Group Name Message Type Transaction ID L3 Information Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.32 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

9.1.75 ENHANCED RELOCATION RELEASE

IE/Group Name Message Type Transaction ID Released CN Domain Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.126 Semantics Description Criticality YES YES Assigned Criticality ignore ignore

3GPP

Release 11

414

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.76 MBSFN MCCH INFORMATION (FDD)

IE/Group Name Message Type Transaction ID MBSFN Cluster Identity MCCH Message List >L3 Information Presence M M M 1..<maxno ofMCCHM essages> M 9.2.1.32 See Note1 below. Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.128 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore reject

CFN M 9.2.1.9 YES reject MCCH Configuration Info 0..1 YES ignore >Secondary CCPCH M 9.2.1.127 system information MBMS MBSFN Scheduling 0..< YES ignore Transmission Time Interval maxNrOf info List MBMSL3> >TMGI M 9.2.1.80 >MBSFN Scheduling M 9.2.1.129 Transmission Time Interval Note 1: The IE Contains one of the following messages defined in TS 25.331 [16]: MBMS MODIFIED SERVICES INFORMATION, MBMS UNMODIFIED SERVICES INFORMATION, MBMS GENERAL INFORMATION, MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT Cell PTM RB INFORMATION. Range bound maxnoofMCCHMessages maxNrOfMBMSL3 Explanation Maximum number of MCCH Messages simultaneous sent on MCCH Maximum number of MBMS service in L3 information

9.1.77 SECONDARY UL FREQUENCY REPORT

9.1.77.1 FDD Message
Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.2.109 Semantics Description Criticality YES YES Assigned Criticality ignore ignore IE/Group Name Message Type Transaction ID Activation Information

9.1.78 SECONDARY UL FREQUENCY UPDATE INDICATION

9.1.78.1 FDD Message
Presence M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.2.109 Semantics Description Criticality YES YES Assigned Criticality ignore ignore IE/Group Name Message Type Transaction ID Activation Information

3GPP

Release 11

415

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.79 ENHANCED RELOCATION RESOURCE REQUEST [TDD]

IE/Group Name Message Type Transaction ID IMSI Source ID Target ID MS Classmark 2 MS Classmark 3 Speech Version Presence M M O M M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.31 9.2.1.142 9.2.1.143 9.2.1.144 9.2.1.145 9.2.1.146 Semantics Description Criticality YES YES YES YES YES YES YES Assigned Criticality reject reject ignore reject reject ignore ignore

9.1.80 ENHANCED RELOCATION RESOURCE RESPONSE [TDD]

IE/Group Name Message Type Transaction ID D-RNTI L3 Information Presence M M M M Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.24 9.2.1.32 Semantics Description Criticality YES YES YES Assigned Criticality reject ignore ignore

The IE contains HANDOVER COMMAND message defined in TS 44.018 [67]

Cell Capacity Class Value Load Value

O O

9.2.1.5C 9.2.1.33A

YES YES

ignore ignore

9.1.81 ENHANCED RELOCATION RESOURCE FAILURE [TDD]

IE/Group Name Message Type Transaction ID Cause Cell Capacity Class Value Load Value Presence M M M O O Range IE Type and Reference 9.2.1.40 9.2.1.59 9.2.1.5 9.2.1.5C 9.2.1.33A Semantics Description Criticality YES YES YES YES Assigned Criticality reject ignore ignore ignore

9.1.82 ENHANCED RELOCATION RESOURCE RELEASE COMMAND [TDD]

IE/Group Name Message Type Transaction ID Cause Presence M M M Range IE type and reference 9.2.1.40 9.2.1.59 9.2.1.5 Semantics description Criticality YES YES Assigned Criticality reject

ignore

3GPP

Release 11

416

3GPP TS 25.423 V11.2.0 (2012-06)

9.1.83 ENHANCED RELOCATION RESOURCE RELEASE COMPLETE [TDD]

IE/Group Name Message Type Transaction ID Presence M M Range IE type and reference 9.2.1.40 9.2.1.59 Semantics description Criticality YES Assigned Criticality reject

9.1.84 INFORMATION TRANSFER CONTROL REQUEST

IE/Group Name Message Type Transaction ID CHOICE Control Type >Suspension >>Controlled Object Scope >Resume >>Controlled Object Scope M 9.2.1.147 M 9.2.1.147 Presence M M M Range IE type and reference 9.2.1.40 9.2.1.59 Semantics description Criticality YES YES ignore Assigned Criticality ignore

9.2 Information Element Functional Definition and Contents

9.2.0 General
Subclause 9.2 presents the RNSAP IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 9.3. In case there is a contradiction between the tabular format in subclause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take precedence. When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: The first bit (leftmost bit) contains the most significant bit (MSB); The last bit (rightmost bit) contains the least significant bit (LSB); When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information;

9.2.1 Common Parameters

This subclause contains parameters that are common to FDD and TDD.

9.2.1.1

Allocation/Retention Priority

This parameter indicates the priority level in the allocation and retention of transport channel resources in DRNS. DRNS may use the Allocation/Retention priority information of the transport channels composing the RL to prioritise requests for RL Setup/addition and reconfiguration. In similar way, DRNS may use the allocation/Retention priority

3GPP

Release 11

417

3GPP TS 25.423 V11.2.0 (2012-06)

information of the transport channels composing the RL to prioritise which RL shall be set to failure, in case prioritisation is possible. See Annex A.
IE/Group Name Priority Level Presence M Range IE Type and Reference INTEGER(0. .15) Semantics Description This IE indicates the priority of the request. Usage: Value 0 means Spare; It shall be treated as a logical error if received. Values between 1 and 14 are ordered in decreasing order of priority, 1 being the highest and 14 the lowest. Value 15 means No Priority.

Pre-emption Capability

Pre-emption Vulnerability

ENUMERAT ED(shall not trigger preemption, may trigger pre-emption) ENUMERAT ED(not preemptable, preemptable)

9.2.1.2

Allowed Queuing Time

This parameter specifies the maximum queuing time that is allowed in the DRNS until the DRNS must start to execute the request.
IE/Group Name Allowed Queuing Time Presence Range IE Type and Reference INTEGER(1. .60) Semantics Description Unit: Seconds

9.2.1.2A

Allowed Rate Information

The Allowed Rate Information IE indicates the TFI corresponding to the highest allowed bit rate for the uplink and/or the downlink of a DCH. The SRNC is allowed to use any rate being lower than or equal to the rate corresponding to the indicated TFI.
IE/Group Name Allowed UL Rate Presence O Range IE Type and Reference INTEGER(1. .maxTFcount ) INTEGER(1. .maxTFcount ) Semantics Description 1: TFI 0, 2: TFI 1, 3: TFI 2, 1: TFI 0, 2: TFI 1, 3: TFI 2,

Allowed DL Rate

9.2.1.2B

Altitude and Direction

This IE contains a description of Altitude and Direction.

3GPP

Release 11

418

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Direction of Altitude

Presence M

Range

IE Type and Reference ENUMERAT ED(Height, Depth) INTEGER( 0..215-1)

Semantics Description

Altitude

The relation between the value (N) and the altitude (a) in meters it describes is N a <N+1, except for N=215-1 for which the range is extended to include all grater values of (a).

9.2.1.2C

Antenna Co-location Indicator

The Antenna Co-location Indicator indicates whether the antenna of the serving and neighbouring cells are approximately co-located.
IE/Group Name Antenna Co-location Indicator Presence Range IE Type and Reference ENUMERAT ED(colocated,) Semantics Description

9.2.1.2D

Alternative Format Reporting Indicator

This IE indicates if DRNS may report a measurement using an alternative format.

IE/Group Name Alternative Format Reporting Indicator Presence Range IE Type and Reference ENUMERAT ED (Alternative format is allowed, ) Semantics Description

9.2.1.3

Binding ID

The Binding ID is the identifier of a user data stream. In case of transport bearer establishment with ALCAP (TS 25.426 [3]TS 25.424 [35]), this IE contains the identifier that is allocated at the DRNS and that is unique for each transport bearer under establishment to/from the DRNS. If the Transport Layer Address contains an IP address (IETF RFC 2460 [33]), this IE contains the UDP port (IETF RFC 768 [34]) intended to be used for the user plane transport.
IE/Group Name Binding ID Presence Range IE Type and Reference OCTET STRING (1..4,) Semantics Description If the Binding ID includes an UDP port, the UDP port is included in octet 1 and 2. The first octet of the UDP port field shall be included in the first octet of the Binding ID.

9.2.1.4

BLER

This Block Error Rate defines the target radio interface Transport Block Error Rate of the transport channel . BLER is used by the DRNS to determine the needed SIR targets, for admission control and power management reasons.

3GPP

Release 11

419

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name BLER

Presence

Range

IE Type and Reference INTEGER(63..0)

Semantics Description Step 0.1. (Range 6.30). It is the Log10 of the BLER

9.2.1.4A
Void.

Block STTD Indicator

9.2.1.4B

Burst Mode Parameters

The Burst Mode Parameters IE provides all the relevant information in order to able IPDL in the Burst mode.
IE/Group name Burst Start Burst Length Burst freq Presence M M M Range IE Type and Reference INTEGER(0. .15) INTEGER(1 0..25) INTEGER(1. .16) Semantics Description See TS 25.214 [10] and TS 25.224 [22] See TS 25.214 [10] and TS 25.224 [22] See TS 25.214 [10] and TS 25.224 [22]

9.2.1.5

Cause

The purpose of the cause information element is to indicate the reason for a particular event for the whole protocol.

3GPP

Release 11

420

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE Cause Group >Radio Network Layer

Presence M

Range

IE Type and Reference

Semantics Description

3GPP

Release 11

421

3GPP TS 25.423 V11.2.0 (2012-06)

>>Radio Network Layer Cause

ENUMERATED (Unknown C-ID, Cell not Available, Power Level not Supported, UL Scrambling Code Already in Use, DL Radio Resources not Available, UL Radio Resources not Available, Measurement not Supported For The Object, Combining Resources Not Available, Combining not Supported, Reconfiguration not Allowed, Requested Configuration not Supported, Synchronisation Failure, Requested Tx Diversity Mode not Supported, Measurement Temporarily not Available, Unspecified, Invalid CM Settings, Reconfiguration CFN not Elapsed, Number of DL Codes Not Supported, Dedicated Transport Channel Type not Supported, DL Shared Channel Type not Supported, UL Shared Channel Type not Supported, Common Transport Channel Type not Supported, UL Spreading Factor not Supported, DL Spreading Factor not Supported, CM not Supported, Transaction not Supported by Destination Node B, RL Already Activated/Allocated, ..., Number of UL Codes Not Supported, Cell reserved for operator use, DPC Mode Change not Supported, Information temporarily not available, Information Provision not supported for the object, Power Balancing status not compatible, Delayed Activation not Supported, RL Timing Adjustment Not Supported, Unknown RNTI, Measurement Repetition Rate not Compatible with Current Measurements, UE not Capable to Implement Measurement, F-DPCH not supported, E-DCH not supported, Continuous Packet Connectivity DTXDRX operation not supported, Continuous Packet Connectivity HSSCCH less operation not supported, MIMO not supported, E-DCH TTI2ms not supported, Continuous Packet Connectivity DTXDRX operation not available, Continuous Packet Connectivity UE DTX Cycle not available, MIMO not available, SixteenQAM UL not supported, HS-DSCH MAC-d PDU Size Format not supported, F-DPCH Slot Format operation not supported, E-DCH MAC-d PDU Size Format not available, E-DPCCH Power Boosting not supported, Trelocprep Expiry,

3GPP

Release 11

422

3GPP TS 25.423 V11.2.0 (2012-06)

>Transport Layer >>Transport Layer Cause

ENUMERATED (Transport Resource Unavailable, Unspecified, ...) ENUMERATED (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Unspecified, Abstract Syntax Error (Falsely Constructed Message),...) ENUMERATED (Control Processing Overload, Hardware Failure, O&M Intervention, Not enough User Plane Processing Resources, Unspecified,...)

>Protocol >>Protocol Cause

>Misc >>Miscellaneous Cause

The meaning of the different cause values is described in the following table. In general, not supported cause values indicate that the concerned capability is missing. On the other hand, not available cause values indicate that the concerned capability is present, but insufficient resources were available to perform the requested action.

3GPP

Release 11

423

3GPP TS 25.423 V11.2.0 (2012-06)

Radio Network Layer cause Cell not Available Cell reserved for operator use Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available Cell Specific Tx Diversity Handling For Multi Cell Operation Not Supported CM not Supported Combining not Supported Combining Resources Not Available Common Transport Channel Type not Supported Continuous Packet Connectivity DTX-DRX operation not available Continuous Packet Connectivity DRX not available Continuous Packet Connectivity DRX not supported Continuous Packet Connectivity DTX-DRX operation not Supported Continuous Packet Connectivity HS-SCCH less operation not Supported Continuous Packet Connectivity UE DTX Cycle not available Dedicated Transport Channel Type not Supported Delayed Activation not Supported Directed Retry DL Radio Resources not Available DL SF not Supported DL Shared Channel Type not Supported DPC Mode Change not Supported E-DCH MAC-d PDU Size Format not available E-DCH not supported E-DCH TTI2ms not supported E-DPCCH Power Boosting not supported Enhanced Relocation not Supported F-DPCH not supported F-DPCH Slot Format operation not supported Frequency Specific Compressed Mode not available HS-DSCH MAC-d PDU Size Format not supported Information Provision not supported for the object Information temporarily not available Invalid CM Settings Measurement not Supported For The Object Measurement Repetition Rate not Compatible with Current Measurements Measurement Temporarily not Available MIMO not available

Meaning The concerned cell is not available The concerned cell is reserved for operator use Cell specific tx diversity handling for multi cell operation not available in the concerned cell(s) The concerned cell(s) do not support the cell specific tx diversity handling for multi cell operation The concerned cell(s) do not support Compressed Mode The DRNS does not support the RL combining for the concerned cells The value of the received Diversity Control Field IE was set to Must, but the DRNS cannot perform the requested combining The concerned cell(s) do not support the RACH and/or FACH Common Transport Channel Type CPC resources for DTX-DRX operation not available in the concerned cell(s). HSPA resources for DRX operation not available in the concerned cell(s). (for 1.28Mcps TDD only) The concerned cell(s) do not support the Continuous Packet Connectivity DRX operation (for 1.28Mcps TDD only) The concerned cell(s) do not support the Continuous Packet Connectivity DTX-DRX operation The concerned cell(s) do not support the Continuous Packet Connectivity HS-SCCH less operation CPC resources for the UE DTX Cycle not available in the concerned cell(s). The concerned cell(s) do not support the Dedicated Transport Channel Type The concerned cell(s) do not support delayed activation of RLs The reason for action is Directed Retry The DRNS does not have sufficient DL radio resources available The concerned cell(s) do not support the requested DL SF The concerned cell(s) do not support the Downlink Shared Channel Type The concerned cells do not support the DPC mode changes The selected E-DCH MAC-d PDU Size Format is not available in the concerned cell(s). The concerned cell(s) do not support E-DCH The concerned cell(s) do not support the E-DCH 2ms TTI operation The concerned cell(s) do not support the E-DPCCH Power Boosting. The DRNS does not support the Enhanced Relocation. The concerned cell(s) do not support the Fractional DPCH The concerned cell(s) do not support the F-DPCH Slot Format operation Frequency Specific Compressed Mode is not available in the concerned cell(s) The concerned cell(s) do not support the selected HS-DSCH MAC-d PDU Size Format The RNS doesnt support provision of the requested information for the concerned object types The RNS can temporarily not provide the requested information The concerned cell(s) consider the requested Compressed Mode settings invalid At least one of the concerned cell(s) does not support the requested measurement on the concerned object type The requested parameters for a forwarded UE measurement are not compatible with the current measurement schedule in the SRNC. The DRNS can temporarily not provide the requested measurement value MIMO resources not available in the concerned cell(s).

3GPP

Release 11

424

3GPP TS 25.423 V11.2.0 (2012-06)

MIMO not supported Multi Cell E-DCH operation not available Multi Cell E-DCH operation not supported Multi Cell operation not available Multi Cell operation not supported Multi Cell operation with MIMO not available Multi Cell operation with MIMO not supported Multi Cell operation with Single Stream MIMO not available Multi Cell operation with Single Stream MIMO not supported No Iu CS UP relocation Number of DL Codes not Supported Number of UL Codes not Supported Power Balancing status not compatible Power Level not Supported Reconfiguration CFN not Elapsed Reconfiguration not Allowed Reduce Load in Serving Cell Relocation Cancelled Relocation Desirable For Radio Reasons Relocation Failure In Target RNC Relocation Not Supported Due To PUESBINE Feature Relocation Target not allowed Requested Ciphering And/Or Integrity Protection Algorithms Not Supported Requested Configuration not Supported Requested Tx Diversity mode not Supported Resource Optimisation Relocation RL Already Activated/ Allocated RL Timing Adjustment not Supported Semi-Persistent scheduling not supported SixteenQAM UL not Supported SixtyfourQAM DL and MIMO Combined not available SixtyfourQAM DL and MIMO Combined not supported Synchronisation Failure Time Critical Relocation Traffic Load In The Target Cell Higher Than In The Source Cell Transaction not Supported by Destination Node B

The concerned cell(s) do not support the MIMO operation Multi cell E-DCH operation is not available in the concerned cell(s). The concerned cell(s) do not support Multi cell E-DCH operation Multi Cell operation resources not available in the concerned cell(s). The concerned cell(s) do not support Multi Cell operation Multi Cell operation with MIMO resources not available in the concerned cell(s). The concerned cell(s) do not support Multi Cell operationwith MIMO Multi Cell operation with Single Stream MIMO resources not available in the concerned cell(s). The concerned cell(s) do not support Multi Cell operationwith Single Stream MIMO The relocation is triggered by CS call and the source RNC has no Iu CS user plane. The concerned cell(s) do not support the requested number of DL codes The concerned cell(s) do not support the requested number of UL codes The power balancing status in the SRNC is not compatible with that of the DRNC. A DL power level was requested which the concerned cell(s) do not support The requested action cannot be performed due to that a COMMIT message was received previously, but the concerned CFN has not yet elapsed The SRNC does currently not allow the requested reconfiguration Load on serving cell needs to be reduced. The reason for the action is relocation cancellation. The reason for requesting relocation is radio related. Relocation failed due to a failure in target RNC. The DRNS can not support the relocation due to the PUESBINE Feature. Relocation to the indicated target cell is not allowed for the UE in question. The DRNS does not support the requested ciphering and/or integrity protection algorithms. The concerned cell(s) do not support the requested configuration i.e. power levels, Transport Formats, physical channel parameters,.. The concerned cell(s) do not support the requested transmit diversity mode The reason for requesting relocation is resource optimisation. The DRNS has already allocated an RL with the requested RL ID for this UE Context The concerned cell(s) do not support adjustments of the RL timing The concerned cell(s) do not support the Semi-Persistent scheduling operation (for 1.28Mcps TDD only) The concerned cell(s) do not support the 16 QAM UL SixtyfourQAM DL and MIMO Combined not available in the concerned cell(s) The DRNS does not support SixtyfourQAM DL and MIMO Combined for the concerned cells. Loss of UL Uu synchronisation Relocation is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if relocation is not performed. Relocation to reduce load in the source cell is rejected, as the target cells traffic load is higher than that in the source cell. The requested action cannot be performed due to lack of support of the corresponding action in the destination Node B

3GPP

Release 11

425

3GPP TS 25.423 V11.2.0 (2012-06)

TRELOCprep Expiry Single Stream MIMO not supported Single Stream MIMO not available TX diversity for MIMO UE on DL Control Channels not available UE not Capable to Implement Measurement UL Radio Resources not Available UL Scrambling Code Already in Use UL SF not Supported UL Shared Channel Type not Supported Unknown C-ID Unknown RNTI Unspecified

Relocation Preparation procedure is cancelled when timer TRELOCprep expires. The concerned cell(s) do not support the Single Stream MIMO. Single Stream MIMO resources not available in the concerned cell(s). The DRNS does not have sufficient radio resources available to support transmit diversity on downlink control channels when the UE is configured in MIMO mode with P-CPICH & S-CPICH as phase references (TS 25.211 [8]) The UE is not capable to initiate/report a requested measurement due to its current state or capabilities. The DRNS does not have sufficient UL radio resources available The concerned UL scrambling code is already in use for another UE The concerned cell(s) do not support the requested minimum UL SF The concerned cell(s) do not support the Uplink Shared Channel Type The DRNS is not aware of a cell with the provided C-ID The SRNC or DRNC is not aware of a UE indicated with the provided RNTI Sent when none of the above cause values applies but still the cause is Radio Network Layer related Meaning The required transport resources are not available Sent when none of the above cause values applies but still the cause is Transport Network Layer related Meaning The received message included an abstract syntax error and the concerned criticality indicated reject (see subclause 10.3) The received message included an abstract syntax error and the concerned criticality indicated ignore and notify (see subclause 10.3) The received message contained IEs or IE groups in wrong order or with too many occurrences (see subclause 10.3) The received message was not compatible with the receiver state (see subclause 10.4) The received message included a semantic error (see subclause 10.4) The received message included a transfer syntax error (see subclause 10.2) Sent when none of the above cause values applies but still the cause is Protocol related Meaning DRNS control processing overload DRNS hardware failure DRNS has insufficient user plane processing resources available Operation and Maintenance intervention related to DRNS equipment Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol.

Transport Network Layer cause Transport resource unavailable Unspecified

Protocol cause Abstract Syntax Error (Reject) Abstract Syntax Error (Ignore and Notify) Abstract syntax error (falsely constructed message) Message not Compatible with Receiver State Semantic Error Transfer Syntax Error Unspecified

Miscellaneous cause Control Processing Overload Hardware Failure Not enough User Plane Processing Resources O&M Intervention Unspecified

9.2.1.5A

Cell Geographical Area Identity (Cell GAI)

The Cell Geographical Area is used to identify the geographical area of a cell. The area is represented as a polygon. See TS 23.032 [25].

3GPP

Release 11

426

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Cell GAI Geographical Co-ordinates >Latitude Sign >Degrees of Latitude

Presence

Range 1 .. <maxnoofPoints>

IE Type and Reference ENUMERAT ED(North, South) INTEGER( 0..223-1)

Semantics Description

M M

>Degrees of Longitude

INTEGER( -223..223-1)

The IE value (N) is derived by this formula: N 223 X /90 < N+1 X being the latitude in degree (0.. 90) The IE value (N) is derived by this formula: N 224 X /360 < N+1 X being the longitude in degree (-180..+180)

Range bound maxnoofPoints

Explanation Maximum no. of points in polygon.

9.2.1.5B

Cell Geographical Area Additional Shapes (Cell GAI Additional Shapes)

This IE is used to provide several descriptions of the geographical area of a cell.

IE/Group Name CHOICE Cell GAI Additional Shapes >GA Point With Uncertainty >>GA Point With Uncertainty >GA Ellipsoid point with uncertainty Ellipse >>GA Ellipsoid point with uncertainty Ellipse >GA Ellipsoid point with altitude >>GA Ellipsoid point with altitude >GA Ellipsoid point with altitude and uncertainty Ellipsoid >>GA Ellipsoid point with altitude and uncertainty Ellipsoid >GA Ellipsoid Arc >>GA Ellipsoid Arc Presence Range IE Type and Reference Semantics Description

9.2.1.30A

Ellipsoid point with uncertainty circle

9.2.1.30B

Ellipsoid point with uncertainty Ellipse

9.2.1.30C

Ellipsoid point with altitude

9.2.1.30D

Ellipsoid point with altitude and uncertainty Ellipsoid

9.2.1.30E

Ellipsoid Arc

9.2.1.5C

Cell Capacity Class Value

The Cell Capacity Class Value IE contains the capacity class for both the uplink and downlink. Cell Capacity Class Value IE is the value that classifies the cell capacity with regards to the other cells. Cell Capacity Class Value IE only indicates resources that are configured for traffic purposes.

3GPP

Release 11

427

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Uplink Cell Capacity Class Value

Presence M

Range

IE Type and Reference INTEGER(1. .100,)

Semantics Description Value 1 shall indicate the minimum uplink cell capacity, and 100 shall indicate the maximum uplink cell capacity. . There should be linear relation between uplink cell capacity and Uplink Cell Capacity Class Value. Value 1 shall indicate the minimum downlink cell capacity, and 100 shall indicate the maximum downlink cell capacity. There should be linear relation between downlink cell capacity and Downlink Cell Capacity Class Value.

Downlink Cell Capacity Class Value

INTEGER(1. .100,)

NOTE:

Cell capacity class for GERAN cells is defined by the number of configured carriers in specific GERAN cells which ranges from integer 1 to 100. The value 1 shall indicate the minimum cell capacity and the value 100 shall indicate the maximum cell capacity.

9.2.1.5D

Cell Global Identifier (CGI)

The Cell Global Identifier IE contains the Cell Global Identity as defined in TS 23.003 [1].
IE/Group Name LAI >PLMN Identity Presence 1 M OCTET STRING (3) - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed Range IE Type and Reference Semantics Description

>LAC CI

M M

OCTET STRING (2) OCTET STRING (2)

9.2.1.6

Cell Identifier (C-ID)

The C-ID (Cell Identifier) is the identifier of a cell in one RNS.

IE/Group Name C-ID Presence Range IE Type and Reference INTEGER (0..65535) Semantics Description

3GPP

Release 11

428

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.7

Cell Individual Offset

Cell individual offset is an offset that will be applied by UE to the measurement results for a Primary-CPICH[FDD]/ Primary-CCPCH[TDD] or for GSM Carrier RSSI according to TS 25.331 [16].
IE/Group Name Cell Individual Offset Presence Range IE Type and Reference INTEGER( -20..+20) Semantics Description -20 -> -10dB -19 -> -9.5dB +20 -> +10dB

9.2.1.8

Cell Parameter ID

The Cell Parameter ID identifies unambiguously the [3.84 Mcps TDD and 7.68Mcps TDD Code Groups, Scrambling Codes, Midambles and Toffset] [1.28 Mcps TDD SYNC-DL and SYNC-UL sequences, the scrambling codes and the midamble codes] (see TS 25.223 [13]).
IE/Group Name Cell Parameter ID Presence Range IE Type and Reference INTEGER(0. .127,) Semantics Description

9.2.1.9

CFN

Connection Frame Number for the radio connection, see TS 25.402 [17].
IE/Group Name CFN Presence Range IE Type and Reference INTEGER(0. . 255) Semantics Description

9.2.1.10
Void

CFN Offset

9.2.1.11

CN CS Domain Identifier

Identification of the CN node in the CS Domain.

3GPP

Release 11

429

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name PLMN Identity

Presence M

Range

IE Type and Reference OCTET STRING (3)

Semantics Description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed

LAC

OCTET STRING (2)

9.2.1.11A

CN Domain Type

Identifies the type of core network domain.

IE/Group Name CN Domain Type Presence Range IE Type and Reference ENUMERAT ED(CS domain, PS domain, Dont care, ) Semantics Description See in TS 25.331 [16]

9.2.1.12

CN PS Domain Identifier

Identification of the CN Node in the PS Domain.

IE/Group Name PLMN Identity Presence M Range IE Type and Reference OCTET STRING (3) Semantics Description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed

LAC RAC

M M

OCTET STRING (2) OCTET STRING (1)

3GPP

Release 11

430

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.12A

Common Measurement Accuracy

The Common Measurement Accuracy IE indicates the accuracy of the common measurement.
IE/Group Name CHOICE Common Measurement Accuracy >TUTRAN-GPS Measurement Accuracy Class >>TUTRAN-GPS Measurement Accuracy Class >TUTRAN-GANSS Measurement Accuracy Class >>TUTRAN-GANSS Measurement Accuracy Class Presence M Range IE Type and Reference Semantics Description

TUTRAN-GPS Accuracy Class 9.2.1.59B

TUTRAN-GANSS Accuracy Class 9.2.1.112

9.2.1.12B
Void.

Common Measurement Object Type

9.2.1.12C

Common Measurement Type

The Common Measurement Type identifies which measurement that shall be performed.
IE/Group Name Common Measurement Type Presence Range IE Type and Reference ENUMERATED (UTRAN GPS Timing of Cell Frames for UE Positioning , SFN-SFN Observed Time Difference, load, transmitted carrier power, received total wide band power, UL timeslot ISCP, , RT Load, NRT Load Information, UpPTS interference, UTRAN GANSS Timing of Cell Frames for UE Positioning) Semantics Description UL timeslot ISCP shall only be used by TDD. For measurements, which are requested on the Iur-g interface, only load, RT Load and NRT Load information are used. UpPTS interference is used by 1.28Mcps TDD only UpPTS interference means UpPCH interference in the whole 25.423, refer to TS 25.225 [14] and TS 25.224 [22].

9.2.1.12D

Common Measurement Value

The Common Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met.

3GPP

Release 11

431

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE Common Measurement Value > TUTRAN-GPS Measurement Value Information >>TUTRAN-GPS Measurement Value Information > SFN-SFN Measurement Value Information >>SFN-SFN Measurement Value Information >Load Value >>Load Value >Transmitted Carrier Power Value >>Transmitted Carrier Power Value >Received Total Wide Band Power Value >>Received Total Wide Band Power Value >UL Timeslot ISCP Value >>UL Timeslot ISCP Value >Additional Common Measurement Values >>RT Load Value >>>RT Load Value >>NRT Load Information Value >>>NRT Load Information Value >>UpPTS interference >>>UpPTS interference Value >> TUTRAN-GANSS Measurement Value Information >>>TUTRAN-GANSS Measurement Value Information

Presence M

Range

IE Type and Reference

Semantics Description UTRAN only

Criticality

Assigned Criticality

9.2.1.59D UTRAN only

9.2.1.52C

M M

9.2.1.33A UTRAN only Transmitted Carrier Power 9.2.1.59A UTRAN only

Received Total Wide Band Power 9.2.2.35A TDD Only UL Timeslot ISCP 9.2.3.13A

9.2.1.50B

YES

ignore

9.2.1.41I 1.28Mcps TDD Only

YES YES YES

ignore

INTEGER (0..127,)

According to mapping in TS 25.123 [24] UTRAN only

reject

9.2.1.114

reject

9.2.1.12E

Common Measurement Value Information

The Common Measurement Value Information IE provides information both on whether the Common Measurement Value is provided in the message or not and if provided also the Common Measurement Value itself.

3GPP

Release 11

432

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE Measurement Availability >Measurement Available >>Common Measurement Value >Measurement not Available

Presence M M

Range

IE Type and Reference

Semantics Description

9.2.1.12D NULL

9.2.1.12F

Common Transport Channel Resources Initialisation Not Required

If present, this IE indicates that as far as the DRNC is concerned, there is no need to initiate a Common Transport Channel Resources Initialisation procedure if the SRNC wants to allocate common transport channel resources in the new cell.
IE/Group Name Common Transport Channel Resources Initialisation Not Required Presence Range IE Type and Reference ENUMERAT ED(Not Required) Semantics Description

9.2.1.12G

Coverage Indicator

The Coverage Indicator indicates whether the serving and the neighbouring cell are overlapped, i.e. the cells have approximately same coverage area or whether the neighbouring cell covers or contained in the serving cell.
IE/Group Name Coverage Indicator Presence Range IE Type and Reference ENUMERAT ED(Overlap, Covers, Contained in,) Semantics Description

9.2.1.13

Criticality Diagnostics

The Criticality Diagnostics IE is sent by an RNC when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs that were not comprehended or were missing. For further details on how to use the Criticality Diagnostics IE, see Annex C.

3GPP

Release 11

433

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Procedure ID

Presence

Range 0..1

IE Type and Reference

Semantics Description Procedure ID is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error Common = common to FDD and TDD. Common Ddmode is also applicable for Iurg procedures listed in section 7. The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication.

Criticality

Assigned Criticality

>Procedure Code >Ddmode

M M

INTEGER(0..255 ) ENUMERATED( FDD, TDD, Common)

Triggering Message

Procedure Criticality

ENUMERATED(i nitiating message, successful outcome, unsuccessful outcome, outcome) ENUMERATED(r eject, ignore, notify)

This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure).

Transaction ID Information Element Criticality Diagnostics >IE Criticality

O 0..<max noof errors> M

Transaction ID

The IE Criticality is used for reporting the criticality of the triggering IE. The value Ignore shall never be used. The IE ID of the not understood or missing IE as defined in the ASN.1 part of the specification.

ENUMERATED(r eject, ignore, notify)

>IE ID

INTEGER(0..655 35)

3GPP

Release 11

434

3GPP TS 25.423 V11.2.0 (2012-06)

>Repetition Number

INTEGER(0..255 )

>Message Structure

9.2.1.39A

The Repetition Number IE gives in case of a not understood IE: The number of occurrences of the reported IE up to and including the not understood occurrence in case of a missing IE: The number of occurrences up to but not including the missing occurrence. Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them. The Message Structure IE describes the structure in which the not understood or missing IE was detected. This IE is included if the not understood IE is not the top level of the message.

YES

ignore

>Type of Error

ENUMERATED( not understood, missing, )

YES

ignore

Range bound maxnooferrors

Explanation Maximum number of IE errors allowed to be reported with a single message.

9.2.1.14

C-RNTI

C-RNTI (Cell RNTI) is the UE identifier allocated by the DRNS to be used over the radio interface. It is unique in the cell. One UE Context has one unique C-RNTI value allocated in the DRNS.
IE/Group Name C-RNTI Presence Range IE Type and Reference INTEGER(0. .65535) Semantics Description

9.2.1.14A

CTFC

The CTFC is an integer number calculated in accordance with TS 25.331 [16], subclause 14.10. Regarding the channel ordering, for all transport channels, TrCH1 corresponds to the transport channel having the lowest transport channel identity among all configured transport channels on this CCTrCH. TrCH2 corresponds to the transport channel having the next lowest transport channel identity, and so on.

3GPP

Release 11

435

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE CTFC Format >2 bits long >>CTFC value >4 bits long >>CTFC value >6 bits long >>CTFC value >8 bits long >>CTFC value >12 bits long >>CTFC value >16 bits long >>CTFC value >max nb bits long >>CTFC value

Presence

Range

IE Type and Reference

Semantics Description

M M M M M M M

INTEGER (0..3) INTEGER (0..15) INTEGER (0..63) INTEGER (0..255) INTEGER (0..4095) INTEGER (0..65535) INTEGER (0..maxCTFC) Explanation Maximum number of the CTFC value is calculated according to the following:

Range Bound MaxCTFC

( L 1) P
i i =1

with the notation according to TS 25.331 [16]

9.2.1.15
Void

DCH Combination Indicator DCH ID

9.2.1.16

The DCH ID is the identifier of an active dedicated transport channel. It is unique for each active DCH among the active DCHs simultaneously allocated for the same UE.
IE/Group Name DCH ID Presence Range IE Type and Reference INTEGER (0..255) Semantics Description

9.2.1.16A

DCH Information Response

The DCH Information IE provides information for DCHs that have been established or modified.

3GPP

Release 11

436

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name DCH Information Response

Presence

Range 1..<maxno ofDCHs>

IE Type and Reference

Semantics Description Several DCHs belonging to the same set of coordinated DCHs may be included.

Criticality

Assigned Criticality

>DCH ID >Binding ID >Transport Layer Address >Allowed Rate Information >Transport Bearer Not Setup Indicator Range bound maxnoofDCHs

M O O O O

9.2.1.16 9.2.1.3 9.2.1.62 9.2.1.2A 9.2.2.4T

FDD Only

YES YES

ignore Ignore

Explanation Maximum number of DCHs for one UE.

9.2.1.17
Void.

Dedicated Measurement Object Type

9.2.1.18

Dedicated Measurement Type

The Dedicated Measurement Type identifies the type of measurement that shall be performed.
IE/Group Name Dedicated Measurement Type Presence Range IE Type and Reference ENUMERAT ED(SIR, SIR Error, Transmitted Code Power, RSCP, Rx Timing Deviation, Round Trip Time, , Rx Timing Deviation LCR, Angle Of Arrival LCR, HS-SICH Reception Quality, Rx Timing Deviation 768, Rx Timing Deviation 384 Extended) Semantics Description RSCP and HS-SICH Receptions Quality are used by TDD only, Rx Timing Deviation and Rx Timing Deviation 384 Extended are used by 3.84 Mcps TDD only, Rx Timing Deviation LCR is used by 1.28 TDD only, Round Trip Time, SIR Error are used by FDD only. Angle Of Arrival LCR is used by 1.28Mcps TDD only. Rx Timing Deviation 768 is used by 7.68Mcps TDD only.

NOTE:

For definitions of the measurement types refer to TS 25.215 [11] and TS 25.225 [14].

9.2.1.19

Dedicated Measurement Value

The Dedicated Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met.

3GPP

Release 11

437

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE Dedicated Measurement Value >SIR Value >>SIR Value

Presence M M

Range

IE Type and Reference

Semantics Description

Criticality

Assigned Criticality

INTEGER( 0..63)

>SIR Error Value >>SIR Error Value

INTEGER( 0..125)

According to mapping in TS 25.133 [23] and TS 25.123 [24] FDD Only According to mapping in TS 25.133 [23] According to mapping in TS 25.133 [23] and TS 25.123 [24] Values 0 to 9 and 123 to 127 shall not be used. TDD Only According to mapping in TS 25.123 [24] 3.84Mcps TDD Only According to mapping in TS 25.123 [24] FDD Only According to mapping in TS 25.133 [23] 1.28Mcps TDD Only According to mapping in TS 25.123 [24] 1.28Mcps TDD only According to mapping in TS 25.123 [24] According to mapping in TS 25.123 [24] Applicable to TDD only

>Transmitted Code Power Value >>Transmitted Code Power Value

M INTEGER( 0..127)

>RSCP >>RSCP

INTEGER( 0..127)

>Rx Timing Deviation Value >>Rx Timing Deviation M INTEGER( 0..8191)

>Round Trip Time >>Round Trip Time

INTEGER( 0..32767)

>Additional Dedicated Measurement Values >>Rx Timing Deviation Value LCR >>>Rx Timing Deviation LCR >>Angle of Arrival Value LCR >>>AOA LCR

YES reject

INTEGER( 0..511)

YES

reject

INTEGER( 0..719) ENUMER ATED(A, B, C, D, E, F, G, H,...) 1

>>>AOA LCR Accuracy Class >>HS-SICH reception quality >>>HS-SICH reception quality Value

YES reject

3GPP

Release 11

438

3GPP TS 25.423 V11.2.0 (2012-06)

>>>>Failed HS-SICH

INTEGER (0..20) INTEGER (0..20) INTEGER (0..20)

>>>Missed HS-SICH

>>>Total HS-SICH

>>Rx Timing Deviation Value 7.68Mcps >>>Rx Timing Deviation 7.68Mcps >>Rx Timing Deviation Value 3.84Mcps Extended >>>Rx Timing Deviation 3.84Mcps Extended >>Extended Round Trip Time >>>Extended Round Trip Time Value

INTEGER( 0..65535)

According to mapping in TS 25.123 [24] According to mapping in TS 25.123 [24] According to mapping in TS 25.123 [24] 7.68Mcps TDD Only According to mapping in TS 25.123 [24] 3.84 Mcps TDD Only According to mapping in TS 25.123 [24] FDD Only Continuation of intervals with step size as defined in TS 25.133 [23].

YES

reject

YES

reject

INTEGER( 0..32767)

YES

ignore

INTEGER (32767..10 3041)

9.2.1.19A

Dedicated Measurement Value Information

The Dedicated Measurement Value Information IE provides information both on whether or not the Dedicated Measurement Value is provided in the message and if provided also the Dedicated Measurement Value itself.
IE/Group Name CHOICE Measurement Availability Indicator >Measurement Available >>Dedicated Measurement Value >>CFN Presence M M O 9.2.1.19 9.2.1.9 Dedicated Measuremen t Time Reference Range IE Type and Reference Semantics Description Criticality _ Assigned Criticality

>Measurement not Available

NULL

9.2.1.19Aa

Delayed Activation

The Delayed Activation IE indicates that the activation of the DL power shall be delayed until an indicated CFN or until a separate activation indication is received.

3GPP

Release 11

439

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name CHOICE Delayed Activation >CFN >>Activation CFN >Separate Indication

Presence M M

Range

IE Type and Reference

Semantics Description

CFN 9.2.1.7 NULL

9.2.1.19Ab

Delayed Activation Update

The Delayed Activation Update IE indicates a change of the activation of the DL power for a specific RL.
IE/Group Name CHOICE Delayed Activation Update >Activate >>CHOICE Activation Type >>>Synchronised >>>>Activation CFN >>>Unsynchronised >>Initial DL TX Power >>First RLS Indicator >>Propagation Delay >>Extended Propagation Delay >Deactivate >>CHOICE Deactivation type >>>Synchronised >>>>Deactivation CFN >>>Unsynchronised Presence M M M M O O O M M CFN 9.2.1.7 NULL CFN 9.2.1.7 NULL DL Power 9.2.1.21 9.2.2.16A 9.2.2.35 9.2.2.33a Range IE Type and Reference Semantics Description

FDD Only FDD Only FDD Only

9.2.1.19B

DGPS Corrections

The DGPS Corrections IE contains DGPS information used by the UE Positioning A-GPS method. For further details on the meaning of parameters, see RTCM-SC104 [31].

3GPP

Release 11

440

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name GPS TOW

Presence M

Range

IE Type and Reference INTEGER(0..60479 9) ENUMERATED (UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.1, no data, invalid data)

Semantics Description Time in seconds. This field indicates the baseline time for which the corrections are valid This field indicates the status of the differential corrections

Criticality -

Assigned Criticality

Status/Health

Satellite DGPS Corrections Information >SatID >IODE

1..<ma xNoSa t> M M SAT ID 9.2.1.50A BIT STRING(8) This IE is the sequence number for the ephemeris for the particular satellite. It can be used to determine if new ephemeris is used for calculating the corrections that are provided. This eight-bit IE is incremented for each new set of ephemeris for the satellite and may occupy the numerical range of [0, 239] during normal operations. User Differential Range Error. This field provides an estimate of the uncertainty (1-) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the common Corrections Status/Health field to determine the final UDRE estimate for the particular satellite Scaling factor 0.32 meters Scaling factor 0.032 m/s

>UDRE

ENUMERATED (UDRE 1.0m, 1.0m < UDRE 4.0m, 4.0m < UDRE 8.0m, 8.0m < UDRE,...) INTEGER( -2047..2047) INTEGER(-127.. 127) 9.2.1.138

>PRC >Range Correction Rate >DGNSS Validity Period

M M O

YES ignore

Range Bound maxNoSat

Explanation Maximum number of satellites for which information can be provided

9.2.1.19C

Discard Timer

The Discard Timer IE defines the time to live for a MAC-hs SDU starting from the instant of its arrival into an HSDPA Priority Queue. The DRNS shall use this information to discard out-of-date MAC-hs SDUs from the HSDPA Priority Queues.

3GPP

Release 11

441

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Discard Timer

Presence

Range

IE type and reference ENUMERAT ED (20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 250, 300, 400, 500, 750, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 7500, )

Semantics description Unit: ms

9.2.1.20

Diversity Control Field

The Diversity Control Field indicates if the current RL may, must or must not be combined with the already existing RLs.
IE/Group Name Diversity Control Field Presence Range IE Type and Reference ENUMERAT ED(May, Must, Must not, ) Semantics Description

9.2.1.21
Void.

Diversity Indication DL Power

9.2.1.21A

The DL Power IE indicates a power level relative to the [FDD primary CPICH power] [TDD PCCPCH power] configured in a cell. [FDD If referred to a DPCH, it indicates the power of the transmitted DPDCH symbols. If referred to an F-DPCH, it indicates the Reference F-DPCH TX Power.] If Transmit Diversity is applied to a downlink physical channel, the DL Power IE indicates the power offset between the linear sum of the power for this downlink physical channel on all branches and the [FDD primary CPICH power] [TDD PCCPCH power] configured in a cell. [TDD If referred to a DPCH, it indicates the power of a spreading factor 16 code, the power for a spreading factor 1 code would be 12 dB higher.]
IE/Group Name DL Power Presence Range IE Type and Reference INTEGER (350..150) Semantics Description Value = DL Power /10 Unit dB Range 35.0 .. +15.0 Step 0.1dB

9.2.1.22
Void

Downlink SIR Target

9.2.1.23

DPCH Constant Value

DPCH Constant Value is the power margin used by a UE to set the proper uplink power.

3GPP

Release 11

442

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name DPCH Constant Value

Presence

Range

IE Type and Reference INTEGER (10..10)

Semantics Description Unit dB Granularity 1 dB.

9.2.1.24

D-RNTI

The D-RNTI identifies the UE Context in the DRNC.

IE/Group Name D-RNTI Presence Range IE Type and Reference INTEGER(0. .2^20 1) Semantics Description

9.2.1.25

D-RNTI Release Indication

The D-RNTI Release Indication indicates whether or not a DRNC shall release the D-RNTI allocated for a particular UE.
IE/Group Name D-RNTI Release Indication Presence Range IE Type and Reference ENUMERAT ED(Release D-RNTI, not Release D-RNTI) Semantics Description

9.2.1.26

DRX Cycle Length Coefficient

The DRX Cycle Length Coefficient is used as input for the formula to establish the paging occasions to be used in DRX.
IE/Group Name DRX Cycle Length Coefficient Presence Range IE Type and Reference INTEGER (3..9) Semantics Description Refers to k in the formula as specified in TS 25.304 [15], Discontinuous Reception.

9.2.1.26A
Void.

DSCH ID

9.2.1.26Aa
Void.

DSCH Initial Window Size DSCH Flow Control Information

9.2.1.26B
Void.

9.2.1.26Ba
Void.

DSCH-RNTI Extended GSM Cell Individual Offset

9.2.1.26Bb

Extended GSM Cell individual offset is an offset that will be applied by UE to the measurement results for GSM carrier RSSI according to TS 25.331 [16]. It shall be used when the offset exceeds the range of values that can be indicated using the Cell Individual Offset IE (Subclause 9.2.1.7).

3GPP

Release 11

443

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Extended GSM Cell Individual Offset

Presence

Range

IE Type and Reference INTEGER (50..-11 | 11..50)

Semantics Description Unit in dB. Step size is 1 dB.

9.2.1.26C

FACH Flow Control Information

The FACH Flow Control Information IE provides flow control information for each scheduling priority class for the FACH FP over Iur.
IE/Group Name FACH Flow Control Information >FACH Scheduling Priority Presence Range 1..16 M Scheduling Priority Indicator 9.2.1.51A 1..<maxN bMACc/shSDUL ength> M M 9.2.1.34 9.2.1.27 IE Type and Reference Semantics Description Criticality Assigned Criticality

>MAC-c/sh SDU Length

>>MAC-c/sh SDU Length >FACH Initial Window Size Range bound maxNbMAC-c/shSDULength

Explanation Maximum number of different MAC-c/sh SDU lengths.

9.2.1.27

FACH Initial Window Size

Indicates the initial number of MAC-c/sh SDUs that may be transmitted before an acknowledgement is received from the DRNC.
IE/Group Name FACH Initial Window Size Presence Range IE Type and Reference INTEGER(0. .255) Semantics Description Number of frames (MAC-c/sh SDUs.) 255 = Unlimited number of FACH data frames.

9.2.1.28
Void

FACH Priority Indicator FN Reporting Indicator

9.2.1.28A

Frame Number reporting indicator. Indicates if the SFN or CFN shall be included together with the reported measurement value.
IE/Group Name FN reporting indicator Presence Range IE Type and Reference ENUMERAT ED(FN reporting required, FN reporting not required) Semantics Description

3GPP

Release 11

444

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.29

Frame Handling Priority

This parameter indicates the priority level to be used during the lifetime of the DCH, [TDD DSCH] for temporary restriction of the allocated resources due overload reason.
IE/Group Name Frame Handling Priority Presence Range IE Type and Reference INTEGER (0..15) Semantics Description 0=Lowest Priority, 15=Highest Priority

9.2.1.30

Frame Offset

Frame Offset is the required offset between the dedicated channel downlink transmission frames (CFN, Connection Frame Number) and the broadcast channel frame offset (Cell Frame Number). The Frame Offset is used in the translation between Connection Frame Number (CFN) on Iub/Iur and least significant 8 bits of SFN (System Frame Number) on Uu. The Frame Offset is UE and cell specific.
IE/Group Name Frame Offset Presence Range IE Type and Reference INTEGER (0..255) Semantics Description Frames

9.2.1.30A

GA Point with Uncertainty

This IE contains one of the possible descriptions of a Cell Geographical Area.

IE/Group Name Geographical Coordinates Uncertainty Code Presence M M Range IE Type and Reference 9.2.1.30F INTEGER( 0..127) Semantics Description The uncertainty r is derived from the uncertainty code k by r = 10x(1.1k-1)

9.2.1.30B

GA Ellipsoid Point with Uncertainty Ellipse

This IE contains one of the possible descriptions of a Cell Geographical Area.

IE/Group Name Geographical Coordinates Uncertainty Ellipse Confidence Presence M M M Range IE Type and Reference 9.2.1.30F 9.2.1.68A INTEGER( 0..127) Semantics Description

9.2.1.30C

GA Ellipsoid Point with Altitude

This IE contains one of the possible descriptions of a Cell Geographical Area.

IE/Group Name Geographical Coordinates Altitude and direction Presence M M Range IE Type and Reference 9.2.1.30F 9.2.1.2B Semantics Description

9.2.1.30D

GA Ellipsoid Point with Altitude and Uncertainty Ellipsoid

This IE contains one of the possible descriptions of a Cell Geographical Area.

3GPP

Release 11

445

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Geographical Coordinates Altitude and direction Uncertainty Ellipse Uncertainty Altitude Confidence

Presence M M M M M

Range

IE Type and Reference 9.2.1.30F 9.2.1.2B 9.2.1.68A INTEGER( 0..127) INTEGER( 0..127)

Semantics Description

9.2.1.30E

GA Ellipsoid Arc

This IE contains one of the possible descriptions of a Cell Geographical Area.

IE/Group Name Geographical Coordinates Inner radius Presence M M Range IE Type and Reference 9.2.1.30F INTEGER( 0..216-1) Semantics Description The relation between the value (N) and the radius I in meters it describes is 5N r <5(N+1), except for N=216-1 for which the range is extended to include all grater values of I. The uncertainty r is derived from the uncertainty code k by r = 10x(1.1k-1) The relation between the value (N) and the angle (a) in degrees it describes is 2N a <2(N+1) The relation between the value (N) and the angle (a) in degrees it describes is 2N< a 2(N+1)

Uncertainty radius

INTEGER( 0..127) INTEGER( 0..179) INTEGER( 0..179) INTEGER( 0..127)

Offset angle

Included angle

Confidence

9.2.1.30F

Geographical Coordinates

This IE contains the description of geographical coordinates.

IE/Group Name Latitude Sign Presence M Range IE Type and Reference ENUMERAT ED(North, South) INTEGER( 0..223-1) Semantics Description

Degrees Of Latitude

Degrees Of Longitude

INTEGER( -223..223-1)

The IE value (N) is derived by this formula: N 223 X /90 < N+1 X being the latitude in degree (0.. 90) The IE value (N) is derived by this formula: N 224 X /360 < N+1 X being the longitude in degree (-180..+180)

9.2.1.30Fa

GERAN Cell Capability

The GERAN Cell Capability IE is used to transfer the capabilities of a certain GERAN cell via the Iur interface.

3GPP

Release 11

446

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name GERAN Cell Capability

Presence M

Range

IE type and reference BIT STRING (16)

Semantics description Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: A/Gb mode. The second bit: Iu mode. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.1.30Fb

GERAN Classmark

The GERAN Classmark IE is used to transfer the capabilities of a certain GERAN Iu-mode capable cell via the Iur interface.
IE/Group Name GERAN Classmark Presence M Range IE type and reference OCTET STRING Semantics description Contents defined in TS 48.008 [38]

9.2.1.30Fc

GERAN System Information

The GERAN System Information IE provides GERAN specific information.

IE/Group Name GERAN System Info >GERAN System Info Block M Presence Range 1..<maxNrOfGER ANSI> 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. IE Type and Reference Semantics Description

Range bound maxNrOfGERANSI

Explanation Maximum number of GERAN SI blocks that can be provided as part of NACC information

9.2.1.30G

GPS Almanac

This IE provides the information regarding the GPS Almanac. For further details on the meaning of parameters, see ICD-GPS-200 [30].

3GPP

Release 11

447

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group name WNa Satellite Almanac Information >DataID >SatID >e >toa >i >OMEGADOT >SV Health >A1/2 >OMEGA0 >M0 > >af0 >af1 SV Global Health Complete Almanac Provided

Presence M M

Range 1..<max NoOfSat Almanac >

IE Type and Reference BIT STRING(8)

Semantics Description See Note 1.

Criticality

Assigned Criticality

M M M M M M M M M M M M M O O

This field indicates whether almanac is provided for the full GPS constellation or not. TRUE means complete GPS almanac is provided. Note 1: This information element is a simplified representation of the ASN.1 description. Repetitions 1 through maxNoSat and repetitions maxNoSat+1 through maxNoOfSatAlmanac are represented by separate ASN.1 structures with different criticality. Range Bound maxNoOfSatAlmanac

INTEGER (0..3) SAT ID 9.2.1.50A BIT STRING(16) BIT STRING(8) BIT STRING(16) BIT STRING(16) BIT STRING(8) BIT STRING(24) BIT STRING(24) BIT STRING(24) BIT STRING(24) BIT STRING(11) BIT STRING(11) BIT STRING(364) BOOLEAN

YES ignore

Explanation Maximum number of satellite almanacs for which information can be provided

9.2.1.30H

GPS Ionospheric Model

This IE provides the information regarding the GPS Ionospheric Model. For further details on the meaning of parameters, see ICD-GPS-200 [30].

3GPP

Release 11

448

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name 0 1 2 3 0 1 2 3

Presence M M M M M M M M

Range

IE 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

9.2.1.30I

GPS Navigation Model and Time Recovery

This IE contains subframes 1 to 3 of the GPS navigation message. For further details on the meaning of parameters, see ICD-GPS-200 [30].

3GPP

Release 11

449

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name Navigation Message 1to3 >Transmission TOW >SatID >TLM Message >Tlm Revd I >HO-Word >WN >C/A or P on L2 >User Range Accuracy Index >SV Health >IODC >L2 P Data Flag >SF 1 Reserved >TGD >toc >af2 >af1 >af0 >Crs >n >M0 >Cuc >e >Cus >(A)1/2 >toe >Fit Interval Flag >AODO >Cic >OMEGA0 >Cis >i0 >Crc > >OMEGAdot >Idot >Spare/zero fill

Presence M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M

Range 1..<maxNoSat>

IE Type and Reference INTEGER0..10485 75) SAT ID 9.2.1.50A BIT STRING(14) BIT STRING(2) BIT STRING(22) BIT STRING(10) 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) BIT STRING(16) BIT STRING(22) BIT STRING(16) BIT STRING(16) BIT STRING(32) BIT STRING(16) BIT STRING(32) BIT STRING(16) BIT STRING(32) BIT STRING(16) BIT STRING(1) BIT STRING(5) BIT STRING(16) BIT STRING(32) BIT STRING(16) BIT STRING(32) BIT STRING(16) BIT STRING(32) BIT STRING(24) BIT STRING(14) BIT STRING(20)

Semantics Description Time of the Week when the message is broadcast.

Range Bound maxNoSat

Explanation Maximum number of satellites for which information can be provided

9.2.1.30J

GPS Real-Time Integrity

This IE provides the information regarding the status of the GPS constellation. For further details on the meaning of parameters, see ICD-GPS-200 [30].
IE/Group name CHOICE Bad Satellites Presence >Bad Satellites >>Satellite Information >>>BadSatID >No Bad Satellites Presence M 1..<max NoSat> M SAT ID 9.2.1.50A NULL Range IE Type and Reference Semantics Description

3GPP

Release 11

450

3GPP TS 25.423 V11.2.0 (2012-06)

Range Bound MaxNoSat

Explanation Maximum number of satellites for which information can be provided

9.2.1.30K

GPS Receiver Geographical Position (GPS RX Pos)

The GPS Receiver Geographical Position is used to identify the geographical coordinates of a GPS receiver relevant for a certain Information Exchange Object.
IE/Group Name Geographical Coordinates Altitude and direction Presence M M Range IE Type and Reference 9.2.1.30F 9.2.1.2B Semantics Description

9.2.1.30L

GPS UTC Model

This IE provides the information regarding the GPS UTC Model. For further details on the meaning of parameters, see ICD-GPS-200 [30].
IE/Group name A1 A0 tot tLS WNt WNLSF DN tLSF Presence M M M M M M M M Range IE 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

9.2.1.30M

Guaranteed Rate Information

The Guaranteed Rate Information IE indicates the TFI corresponding to the guaranteed bit rate for the uplink and/or the downlink of a DCH.
IE/Group Name Guaranteed UL Rate Presence O Range IE Type and Reference INTEGER(1. .maxTFcount ) INTEGER(1. .maxTFcount ) Semantics Description 1: TFI 0, 2: TFI 1, 3: TFI 2, 1: TFI 0, 2: TFI 1, 3: TFI 2,

Guaranteed DL Rate

9.2.1.30N

HCS Prio

The HCS Prio is the characteristics of the cell as defined in TS 25.304 [15].

3GPP

Release 11

451

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name HCS Prio

Presence

Range

IE Type and Reference INTEGER (0..7)

Semantics Description 0=Lowest Priority, 7=Highest Priority

9.2.1.30NA HS-DSCH Information To Modify Unsynchronised

The HS-DSCH Information To Modify Unsynchronised IE is used for modification of HS-DSCH information in a UE Context with the Unsynchronised Radio Link Reconfiguration procedure.

3GPP

Release 11

452

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name HS-DSCH MAC-d Flow Specific Information >HS-DSCH MAC-d Flow ID >Allocation/Retention Priority >Transport Bearer Request Indicator >Traffic Class >Binding ID

Presence

Range 0..<maxn oofMACd Flows>

IE Type and Reference

Semantics Description

Criticality

Assigned Criticality

M O M O O

9.2.1.30O 9.2.1.1 9.2.1.61 9.2.1.58A 9.2.1.3 Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP.

>Transport Layer Address

9.2.1.62

>TNL QoS

9.2.1.56A

YES

ignore

Priority Queue Information >Priority Queue ID >Scheduling Priority Indicator >Discard Timer >MAC-hs Guaranteed Bit Rate CQI Power Offset ACK Power Offset NACK Power Offset HS-SCCH Power Offset TDD ACK NACK Power Offset HARQ Preamble Mode MIMO Mode Indicator Sixtyfour QAM Usage Allowed Indicator Enhanced HS Serving CC Abort M O O O O O O O O O O O O

0..<maxn oofPrioQ ueues> 9.2.1.45A 9.2.1.51A 9.2.1.19C 9.2.1.34Aa 9.2.2.24b 9.2.2.b 9.2.2.26a 9.2.2.19d 9.2.3.7I 9.2.2.57 9.2.1.135 9.2.2.79A ENUMERAT ED (Abort Enhanced HS Serving CC, ) 9.2.2.103 9.2.2.105 9.2.2.107 For FDD only For FDD only For FDD only For FDD only For TDD only For FDD only For FDD and 1.28Mcps TDD only For FDD only For FDD only

YES YES YES YES ignore reject ignore reject

UE Support Indicator Extension Power Offset For S-CPICH for MIMO Request Indicator Single Stream MIMO Mode Indicator

O O O

YES For FDD only For FDD only YES YES

ignore ignore reject

9.2.1.30Na

HS-DSCH Initial Capacity Allocation

The HS-DSCH Initial Capacity Allocation IE provides flow control information for each scheduling priority class for the HS-DSCH FP over Iur.

3GPP

Release 11

453

3GPP TS 25.423 V11.2.0 (2012-06)

IE/Group Name HS-DSCH Initial Capacity Allocation >Scheduling Priority Indicator >Maximum MAC-d PDU Size

Presence

Range 1..< maxnoof PrioQueu es>

IE Type and Reference

Semantics Description

Criticality

Assigned Criticality

M M

9.2.1.51A MAC-d PDU Size 9.2.1.34A Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.

>HS-DSCH Initial Window Size >Maximum MAC-d PDU Size Extended

M O

9.2.1.30Nb MAC PDU Size Extended 9.2.1.34D Explanation Maximum number of Priority Queues

YES ignore

Range Bound maxnoofPrioQueuess

3GPP

Release 11

454

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.30Nb

HS-DSCH Initial Window Size

Indicates the initial number of MAC-d PDUs (or octets in case HS-DSCH MAC-d PDU Size Format = Flexible MACd PDU Size) that may be transmitted before new credits are received from the DRNC.
IE/Group Name HS-DSCH Initial Window Size Presence Range IE type and reference INTEGER (1..255) Semantics description Number of MAC-d PDUs If HS-DSCH MAC-d PDU Size Format = Flexible MAC-d PDU Size the credit shall be determined in octets: credit (in octets) = Maximum MAC-d PDU Size extended * HS-DSCH Initial Window Size

9.2.1.30O

HS-DSCH MAC-d Flow ID

HS-DSCH MAC-d Flow ID is the unique identifier for one MAC-d flow.
IE/Group Name HS-DSCH MAC-d Flow ID Presence Range IE Type and Reference INTEGER (0..7) Semantics Description

9.2.1.30OA HS-DSCH MAC-d Flows Information

The HS-DSCH MAC-d Flows Information IE is used for the establishment of HS-DSCH MAC-d flows for a UE Context.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flow Specific Information >HS-DSCH MAC-d Flow ID >Allocation/Retention Priority >Traffic Class >Binding ID M M M O Presence Range 1..<maxn oofMACd Flows>

455
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.30O 9.2.1.1 9.2.1.58A 9.2.1.3 Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP.

>Transport Layer Address

9.2.1.62

>TNL QoS

9.2.1.56A

YES

ignore

>TrCH Source Statistics Descriptor Priority Queue Information >Priority Queue ID >Associated HS-DSCH MAC-d Flow

O 1..<maxn oofPrioQ ueues> M M

9.2.1.65

YES

ignore

9.2.1.45A HS-DSCH MAC-d Flow ID 9.2.1.30O

The HS-DSCH MAC-d Flow ID shall be one of the flow IDs defined in the HS-DSCH MAC-d Flow Specific Information of this IE. Multiple Priority Queues can be associated with the same HSDSCH MAC-d Flow ID.

>Scheduling Priority Indicator >T1 >Discard Timer >MAC-hs Window Size >MAC-hs Guaranteed Bit Rate >MAC-d PDU Size Index >>SID

M M O M O 1..<maxn oofMACd PDUinde xes> M

9.2.1.51A 9.2.1.54A 9.2.1.19C 9.2.1.34C 9.2.1.34Aa

9.2.1.52D

Shall be ignored if Maximum MAC-d PDU Size extended IE is present.

3GPP

Release 11
>>MAC-d PDU Size M

456
9.2.1.34A

3GPP TS 25.423 V11.2.0 (2012-06)

Shall be ignored if Maximum MAC-d PDU Size extended IE is present.

>RLC Mode >Maximum MAC-d PDU Size extended >DL RLC PDU Size Format >UE Aggregate Maximum Bit Rate Enforcement Indicator Range Bound maxnoofMACdFlows maxnoofPrioQueues maxnoofMACdPDUindexes

M O

O O

9.2.1.48D MAC PDU Size Extended 9.2.1.34D 9.2.1.136 NULL

YES

reject

YES YES

ignore ignore

Explanation Maximum number of HS-DSCH MAC-d flows Maximum number of Priority Queues Maximum number of different MAC-d PDU SIDs

9.2.1.30OB HS-DSCH MAC-d Flows To Delete

The HS-DSCH MAC-d Flows To Delete IE is used for the removal of HS-DSCH MAC-d flows from a UE Context.
IE/Group Name HS-DSCH MAC-d Flows To Delete >HS-DSCH MAC-d Flow ID Range Bound maxnoofMACdFlows M Presence Range 1..<maxno ofMACdFl ows> 9.2.1.30O IE Type and Reference Semantics Description

Explanation Maximum number of HS-DSCH MAC-d flows

9.2.1.30OC HS-DSCH MAC-d PDU Size Format

The HS-DSCH MAC-d PDU Size Format IE provides information about the type of MAC-d PDU Size Format used for HS-DSCH. Indexed MAC-d PDU Size uses MAC-d PDU sizes based on SID IE and MAC-d PDU Size IE of MAC-d PDU Size Index IE. Flexible MAC-d PDU Size uses a flexible MAC-d PDU size with a maximum PDU size as defined by Maximum MAC-d PDU Size extended IE of Priority Queue Information IE. The actual MAC-d PDU size is determined as specified in TS 25.425 [32] and TS 25.321 [41].
IE/Group Name HS-DSCH MAC-d PDU Size Format Presence Range IE Type and Reference ENUMERATED (Indexed MAC-d PDU Size, Flexible MAC-d PDU Size) Semantics Description

9.2.1.30Oa HS-DSCH Physical Layer Category

The HS-DSCH Physical Layer Category IE defines a set of UE radio access capabilities related to HSDPA, as defined in TS 25.306 [42].

3GPP

Release 11
IE/Group Name HS-DSCH Physical Layer Category Presence Range

457

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference INTEGER (1..64,)

9.2.1.30P

HS-DSCH-RNTI

The HS-DSCH-RNTI is needed for the UE-specific CRC in HS-SCCH and HS-DSCH.
IE/Group Name HS-DSCH-RNTI Presence Range IE Type and Reference INTEGER (0..65535) Semantics Description

3GPP

Release 11

458

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.30Q

HS-DSCH Information To Modify

The HS-DSCH Information To Modify IE is used for modification of HS-DSCH information in a UE Context.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flow Specific Information >HS-DSCH MAC-d Flow ID >Allocation/Retention Priority >Transport Bearer Request Indicator >Traffic Class >Binding ID M O M O O Presence

459
Range 0..<maxn oofMACd Flows> 9.2.1.30O 9.2.1.1 9.2.1.61 9.2.1.58A 9.2.1.3 IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. Assigned Criticality

>Transport Layer Address

9.2.1.62

>TNL QoS

9.2.1.56A

YES

ignore

Priority Queue Information >CHOICE Priority Queue >>Add Priority Queue >>>Priority Queue ID >>>Associated HS-DSCH MAC-d Flow M M M

0..<maxn oofPrioQ ueues>

9.2.1.45A HS-DSCH MAC-d Flow ID 9.2.1.30O

Shall only refer to a HSDSCH MAC-d flow already existing in the old configuration. Multiple Priority Queues can be associated with the same HS-DSCH MAC-d Flow ID.

>>>Scheduling Priority Indicator >>>T1 >>>Discard Timer >>>MAC-hs Window Size >>>MAC-hs Guaranteed Bit Rate >>>MAC-d PDU Size Index >>>>SID

M M O M O 1..<maxn oofMACd PDUinde xes> M

9.2.1.51A 9.2.1.54A 9.2.1.19C 9.2.1.34C 9.2.1.34Aa

9.2.1.52D

Shall be ignored if Maximum MAC-d PDU Size extended IE is present.

3GPP

Release 11
IE/Group Name >>>>MAC-d PDU Size Presence M

460
Range IE Type and Reference 9.2.1.34A

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Shall be ignored if Maximum MAC-d PDU Size extended IE is present. Criticality Assigned Criticality

>>>RLC Mode >>>Maximum MAC-d PDU Size extended >>>DL RLC PDU Size Format >>Modify Priority Queue >>>Priority Queue ID

M O

O M

9.2.1.48D MAC PDU Size Extended 9.2.1.34D 9.2.1.136 9.2.1.45A Shall only refer to a Priority Queue already existing in the old configuration.

YES

reject

Yes

ignore

>>>Scheduling Priority Indicator >>>T1 >>>Discard Timer >>>MAC-hs Window Size >>>MAC-hs Guaranteed Bit Rate >>>MAC-d PDU Size Index >>>>SID

O O O O O 0..<maxn oofMACd PDUinde xes> M

9.2.1.51A 9.2.1.54A 9.2.1.19C 9.2.1.34C 9.2.1.34Aa

9.2.1.52D

>>>>MAC-d PDU Size

9.2.1.34A

Shall be ignored if Maximum MAC-d PDU Size extended IE is present. Shall be ignored if Maximum MAC-d PDU Size extended IE is present.

>>>Maximum MAC-d PDU Size extended >>>DL RLC PDU Size Format >>Delete Priority Queue >>>Priority Queue ID

O M

MAC PDU Size Extended 9.2.1.34D 9.2.1.136 9.2.1.45A Shall only refer to a Priority Queue already existing in the old configuration. For FDD only For FDD only For FDD only For FDD only

YES

reject

Yes

ignore

MAC-hs Reordering Buffer Size for RLC-UM CQI Feedback Cycle k CQI Repetition Factor ACK-NACK Repetition Factor CQI Power Offset

O O O O O

9.2.1.34Ab 9.2.2.24a 9.2.2.24c 9.2.2.a 9.2.2.24b

3GPP

Release 11
IE/Group Name ACK Power Offset NACK Power Offset HS-SCCH Power Offset HS-SCCH Code Change Grant TDD ACK NACK Power Offset HARQ Preamble Mode HS-PDSCH Code Change Grant MIMO Mode Indicator HS-DSCH MAC-d PDU Size Format Sixtyfour QAM Usage Allowed Indicator UE Capabilities Information >HS-DSCH Physical Layer Category >1.28 Mcps TDD uplink physical channel capability >Number of Supported Carriers Presence O O O O O O O O O O O M O O

461
Range IE Type and Reference 9.2.2.b 9.2.2.26a 9.2.2.19d 9.2.1.30S 9.2.3.7I 9.2.2.57 9.2.1.30W 9.2.1.135 9.2.1.30O C 9.2.2.79A 9.2.1.30O a 9.2.3.10D ENUMER ATED ( One-one carrier, One-three carrier, Threethree carrier, One-six carrier, Tree-six carrier, Six-six carrier, ..., One-Two carrier Discontigu ous, TwoTwo carrier Discontigu ous, OneTwo carrier Contiguou s, TwoTwo carrier Contiguou s)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description For FDD only For FDD only For FDD only For TDD only For FDD only For FDD only For FDD and 1.28Mcps TDD only For FDD only Criticality YES YES YES YES YES YES Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only This IE indicates the number of carrier that UE can support at the same time,where One-three carrier means the number of supported carrier is one for the uplink,and three for the downlink. One-Two carrier Discontiguous and Two-Two carrier Discontiguous mean that the UE is capable of supporting two nonadjacent carriers. One-Two carrier Contiguous and Two-Two carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers. YES YES Assigned Criticality

ignore ignore reject reject ignore ignore ignore reject

3GPP

Release 11
IE/Group Name >Multi-carrier HS-DSCH Physical Layer Category >MIMO SF Mode Supported For HS-PDSCH dual stream Presence O O

462
Range IE Type and Reference 9.2.1.30O a ENUMER ATED (SF1, SF1/SF16) ENUMER ATED (TS0 Capable, TS0 NonCapable) 9.2.3.84 ENUMER ATED (Abort Enhanced HS Serving CC, ) 9.2.2.103 9.2.2.105 9.2.2.107

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only Criticality YES YES Assigned Criticality ignore ignore

>UE TS0 Capability LCR

Applicable to 1.28Mcps TDD only

YES

ignore

>UE RF Band Capability LCR Enhanced HS Serving CC Abort

CNofSupport edCarriers O

Applicable to 1.28Mcps TDD only. For FDD only

YES
YES

ignore
reject

UE Support Indicator Extension Power Offset For S-CPICH for MIMO Request Indicator Single Stream MIMO Mode Indicator Condition NofSupportedCarriers

O O O

For FDD only For FDD only

YES YES YES

ignore ignore reject

Explanation This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band. Explanation Maximum number of MAC-d flows. Maximum number of Priority Queues. Maximum number of MAC-d PDU Size Indexes (SIDs).

Range bound maxnoofMACdFlows maxnoofPrioQueues maxnoofMACdPDUindexes

9.2.1.30R

HS-SCCH Code Change Indicator

The HS-SCCH Code Change Indicator indicates whether the HS-SCCH Code change is needed or not.
IE/Group Name HS-SCCH Code Change Indicator Presence Range IE type and reference ENUMERAT ED (HSSCCH Code Change needed) Semantics description

9.2.1.30S

HS-SCCH Code Change Grant

The HS-SCCH Code Change Grant IE indicates that modification of HS-SCCH Codes is granted.

3GPP

Release 11
IE/Group Name HS-SCCH Code Change Grant Presence

463
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(Change Granted) Semantics Description

9.2.1.30T

IMEI

The IMEI is a permanent UE Equipment Identity, see TS 23.003 [1].

IE/Group Name IMEI Presence Range IE Type and Reference OCTET STRING (SIZE (8)) Semantics Description - hexadecimal digits 0 to F, two hexadecimal digits per octet, - each hexadecimal digit encoded 0000 to 1111, - 1111 used as filler for bits 8 to 5 of last octet - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n Number of hexadecimal digits shall be 15.

9.2.1.30U

IMEISV

The IMEISV is a permanent UE Equipment Identity, see TS 23.003 [1].

IE/Group Name IMEISV Presence Range IE Type and Reference OCTET STRING (SIZE (8)) Semantics Description - hexadecimal digits 0 to F, two hexadecimal digits per octet, - each hexadecimal digit encoded 0000 to 1111, - 1111 used as filler for bits 8 to 5 of last octet - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n Number of hexadecimal digits shall be 16.

9.2.1.30V

HS-PDSCH Code Change Indicator [FDD]

The HS-PDSCH Code Change Indicator indicates whether the HS-PDSCH Code change is needed or not.
IE/Group Name HS-PDSCH Code Change Indicator Presence Range IE Type and Reference ENUMERATED (HSPDSCH Code Change needed) Semantics Description

9.2.1.30W

HS-PDSCH Code Change Grant [FDD]

The HS-PDSCH Code Change Grant IE indicates that modification of HS-PDSCH Codes is granted.

3GPP

Release 11
IE/Group Name HS-PDSCH Code Change Grant Presence Range

464

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference ENUMERATED(Chan ge Granted)

9.2.1.31

IMSI

The IMSI is the permanent UE user Identity, see TS 23.003 [1].

IE/Group Name IMSI Presence Range IE Type and Reference OCTET STRING (SIZE(3..8)) Semantics Description -Decimal digits coded in BCD -1111 used as filler -bit 4 to 1 of octet n is encoding digit 2n-1 -bit 8 to 5 of octet n is encoding digit 2n

9.2.1.31A

Information Exchange ID

The Information Exchange ID uniquely identifies any requested information per RNS.
IE/Group Name Information Exchange ID Presence M Range IE Type and Reference INTEGER(0 .. 2^20-1) Semantics Description

9.2.1.31B
Void.

Information Exchange Object Type Information Report Characteristics

9.2.1.31C

The information report characteristics define how the reporting shall be performed.
IE/Group Name CHOICE Information Report Characteristics Type >On Demand >Periodic >>CHOICE Information Report Periodicity Scale >>>minute >>>>Report Periodicity Value >>>hour >>>>Report Periodicity Value >On Modification >>Information Threshold Presence M NULL M The frequency with which the Node B shall send information reports. INTEGER (1..60,) INTEGER (1..24,) 9.2.1.31D Range IE Type and Reference Semantics Description

M M O

9.2.1.31D

Information Threshold

The Information Threshold indicates which kind of information shall trigger the Information Reporting procedure.

3GPP

Release 11
IE/Group Name CHOICE Information Type Item >DGPS Corrections >>PRC Deviation Presence M Range

465
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

ENUMERATED( 1, 2, 5, 10, )

PRC deviation in meters from the previously reported value, which shall trigger a report PRC deviation in meters from the previously reported value, which shall trigger a report

>DGANSS >>PRC Deviation

ENUMERATED (1, 2, 5, 10, )

9.2.1.31E

Information Type

The Information Type indicates which kind of information the RNS shall provide.

3GPP

Release 11
IE/Group Name Information Type Item Presence M Range

466
IE Type and Reference ENUMERATED (UTRAN Access Point Position with Altitude, UTRAN Access Point Position, IPDL Parameters, GPS Information, DGPS Corrections, GPS RX Pos, SFN-SFN Measurement Reference Point Position,, Cell Capacity Class, NACC Related Data, MBMS Bearer Service Full Address, Inter-frequency Cell Information, GANSS Information, DGANSS Corrections, GANSS RX Pos, MBMS Counting Information, MBMS Transmission Mode, MBMS Neighbouring Cell Information, MBMS RLC Sequence Number, ANR Cell Information)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description For information exchange on the Iur-g interface, only the Cell Capacity Class is used. MBMS Counting Information, MBMS Transmission Mode, MBMS Neighbouring Cell Information and MBMS RLC Sequence Numbe shall only be used by FDD. Criticality Assigned Criticality

GPS Information >GPS Information Item

C-GPS

1..<maxn oofGPST ypes>

ENUMERATED (GPS Navigation Model and Time Recovery, GPS Ionospheric Model, GPS UTC Model, GPS Almanac, GPS Real-Time Integrity, )

GANSS Information >GANSS Common Data >>Ionospheric Model >>Additional Ionospheric Model

C-GANSS 0..1 O O BOOLEAN Additional Ionospheric Model Request 9.2.1.122d True means requested Presence means requested.

YES YES

Ignore

Ignore

3GPP

Release 11
>>Earth Orientation Parameters >GANSS Generic Data >>GANSS ID >>GANSS Navigation Model And Time Recovery >>GANSS Time Model GNSSGNSS O O O

467
Earth Orientation Parameters Request 9.2.1.122e
0..<maxn oofGAN SS>

3GPP TS 25.423 V11.2.0 (2012-06)

YES Ignore

9.2.1.119 BOOLEAN

True means requested Defines the time model required. Bit 1 is the MSB and bit 9 is the LSB (see section 9.2.0). Bit 1:GPS, Bit 2:Galileo, Bit 3:QZSS, Bit 4:GLONASS. Other bits are reserved. True means requested True means requested True means requested The GANSS Time Of Day for which the data bits are requested Defined in TS 25.331 [16] Defined in TS 25.331 [16]

BIT STRING(9)

>>GANSS UTC Model >>GANSS Almanac >>GANSS Real Time Integrity >>GANSS Data Bit Assistance >>>GANSS TOD >>>Data Bit Assistance >>>>DGANS S Signal ID >>>>GANSS Data Bit Interval >>>>Satellite Information >>>>Sat ID >>GANSS Additional Navigation Models And Time Recovery >>GANSS Additional UTC Models >>GANSS Auxiliary Information

O O O 0..1 M

BOOLEAN BOOLEAN BOOLEAN

INTEGER (0..86399) 1

BIT STRING(8) INTEGER (0..15) INTEGER(0..63) GANSS Additional Navigation Models And Time Recovery Request 9.2.1.122f GANSS Additional UTC Models Request 9.2.1.122g GANSS Auxiliary Information Request 9.2.1.122h Identifies the satellite and is equal to (SV ID No 1) YES Ignore

M M 0..<max GANSS Sat> M O

YES

Ignore

YES

Ignore

3GPP

Release 11
>>SBAS ID DGANSS Corrections Req >DGANSS Signal ID >GANSS ID MBMS RLC Sequence Number Information >MBMS Cell List >>C-ID >>MBMS Bearer Service List >>>TMGI >>>Time Stamp M 1..<max noofMB MS> M M 9.2.1.80 9.2.2.98 CGANSSID CDGANSS Correction s M O CMBMSRL CSequenc eNumber 1..<max noofcell > 9.2.1.6

468
9.2.1.122b 1

3GPP TS 25.423 V11.2.0 (2012-06)

YES YES Ignore ignore

BIT STRING(8) 9.2.1.119

Defined in TS 25.331 [16] FDD only

YES YES Ignore Ignore

Condition DGANSSCorrections GPS GANSS GANSS-ID MBMSRLCSequenceNumber

Explanation The IE shall be present if the Information Type Item IE indicates DGANSS Corrections. This IE shall be present if the Information Type Item IE indicates GPS Information. This IE shall be present if the Information Type Item IE indicates GANSS Information. This IE shall be present if the GANSS ID IE indicates SBAS. This IE shall be present if the Information Type Item IE indicates MBMS RLC Sequence Number . Explanation Maximum number of satellites for which data is included in the IE Maximum number of GPS Information Types supported in one Information Exchange. Maximum number of GANSS Systems. Maximum number of MBMS bearer services that a UE can join. Maximum number of cells that can be indicated in the corresponding IE.

Range Bound maxGANSSSat maxnoofGPSTypes maxnoofGANSS maxnoofMBMS Maxnoofcell

3GPP

Release 11

469

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.31F

IPDL Parameters
Presence Range IE Type and Reference 9.2.2.21B Applicable to 3.84Mcps TDD and 7.68Mcps TDD only M 9.2.3.4B Applicable to 1.28Mcps TDD only M 9.2.3.4Bb YES reject Semantics Description Criticality M Assigned Criticality

IE/Group Name CHOICE IPDL Parameters >IPDL FDD Parameters >>IPDL FDD parameters >IPDL TDD Parameters

>>IPDL TDD parameters >Additional IPDL Parameters >>IPDL TDD Parameters LCR >>>IPDL TDD parameters LCR

9.2.1.31G

Inter-frequency Cell Information

This IE contains the inter-frequency cell information of a cell in the DRNS broadcased in SIB11 or SIB12.
IE/Group Name SIB11 >Inter-frequency Cell Indication- SIB11 >Inter-frequency Cell List in SIB11 >>Inter-frequency Cell Id >>DL UARFCN >>UL UARFCN Presence 0..2 M 0..<maxCellSIB11 OrSIB12> M M O Integer(0..31) UARFCN 9.2.1.66 UARFCN 9.2.1.66 The order of the interfrequency cell in SIB11. If this IE is not present, the default duplex distance defined for the operating frequency band shall be used (TS 25.101 [43]) Integer(0..1) Value tag in 10.3.7.45 in TS 25.331 [16] with the same IE name. Range IE Type and Reference Semantics Description

>>Primary Scrambling Code SIB12 >Inter-frequency Cell Indication- SIB12 >Inter-frequency Cell List in SIB12 >>Inter-frequency Cell Id >>DL UARFCN >>UL UARFCN

M 0..2 M 0..<maxCellSIB11 OrSIB12>

9.2.1.45 Value tag in 10.3.7.45 in TS 25.331 [16] with the same IE name. Integer(0..31) The order of the interfrequency cell in SIB12. If this IE is not present, the default duplex distance defined for the operating frequency band shall be used (TS 25.101 [43])

M O

UARFCN 9.2.1.66 UARFCN 9.2.1.66

>>Primary Scrambling Code

9.2.1.45

3GPP

Release 11
Range bound maxCellSIB11OrSIB12

470

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of inter-frequency cells broadcased in SIB11 or SIB12.

9.2.1.32

L3 Information

This parameter contains the Layer 3 Information from a Uu message as received from the UE over the Uu interface or the Layer 3 Information for a Uu message to be sent to a UE by the DRNC, as defined in TS 25.331 [16].
IE/Group Name L3 Information Presence Range IE Type and Reference BIT STRING Semantics Description The content is defined in TS 25.331 [16]

9.2.1.33
Void.

Limited Power Increase

9.2.1.33A

Load Value

The Load Value IE contains the total load on the measured object relative to the maximum planned load for both the uplink and downlink. It is defined as the load percentage of the Cell Capacity Class.
IE/Group Name Uplink Load Value Presence M Range IE Type and Reference INTEGER(0. .100) Semantics Description Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load should be measured on a linear scale. Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load should be measured on a linear scale.

Downlink Load Value

INTEGER(0. .100)

9.2.1.34

MAC-c/sh SDU Length

Indicates the MAC-c/sh SDU Length. Which is used for FACH, [TDD DSCH and USCH]. There may be multiple MAC-c/sh SDU Lengths per priority class.
IE/Group Name MAC-c/sh SDU Length Presence Range IE Type and Reference INTEGER(1. .5000) Semantics Description Size of the MAC-c/sh SDU in number of bits.

9.2.1.34A

MAC-d PDU Size

The MAC-d PDU Size IE provides the size in bits of the MAC-d PDU.
IE/Group Name MAC-d PDU Size Presence Range IE Type and Reference INTEGER (1..5000,) Semantics Description In case of E-DCH, value 8 and values not multiple of 8 shall not be used.

9.2.1.34Aa

MAC-hs Guaranteed Bit Rate

The MAC-hs Guaranteed Bit Rate IE indicates the guaranteed number of bits per second that Node B should deliver over the air interface under normal operating conditions (provided there is data to deliver). If the MAC-hs Guaranteed Bit Rate IE is received with the value set to 0 during RL set up or modification, no guarantee is applied.

3GPP

Release 11
IE/Group Name MAC-hs Guaranteed Bit Rate Presence Range

471

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics description Unit: bit/s

IE type and reference INTEGER (0..2^24-1, , 2^24..1,000,000,000)

9.2.1.34Ab

MAC-hs Reordering Buffer Size for RLC-UM

The MAC-hs Reordering Buffer Size for RLC-UM IE indicates the portion of the buffer in the UE that can be used for RLC-UM traffic (i.e. for Priority Queues whose RLC Mode IE is set to RLC-UM).
IE/Group Name MAC-hs Reordering Buffer Size for RLC-UM Presence Range IE Type and Reference INTEGER (0..300,) Semantics Description Unit: kBytes And N kBytes = N*1024 Bytes. The shall use this value to avoid the overflow of the UE buffer.

9.2.1.34B

MAC-hs Reset Indicator

The MAC-hs Reset Indicator IE indicates that a reset of the MAC-hs is not required.
IE/Group Name MAC-hs Reset Indicator Presence Range IE Type and Reference ENUMERATED (MAC-hs Not Reset) Semantics Description

9.2.1.34C

MAC-hs Window Size

The MAC-hs Window Size IE is used for MAC-hs/MAC-ehs PDU retransmission as defined in TS 25.321 [41]. [FDD the values 64, 128 and 256 is only allowed when the MAC header type is MAC-ehs and under conditions defined in TS 25.425 [32]].
IE/Group Name MAC-hs Window Size Presence Range IE type and reference ENUMERAT ED (4, 6, 8, 12, 16, 24, 32,64, 128, 256) Semantics description

9.2.1.34D

MAC PDU Size Extended

The MAC PDU Size Extended IE provides the size in octets of the MAC level PDU when an extended MAC level PDU size is required.
IE/Group Name MAC PDU Size Extended Presence Range IE Type and Reference INTEGER (1..1504, ,1505) Semantics Description In case of E-DCH, value 1 shall not be used

9.2.1.35

Maximum Allowed UL Tx Power

Maximum Allowed UL Tx Power is the maximum power that a UE in a particular cell is allowed to transmit.
IE/Group Name Maximum Allowed UL Tx Power Presence Range IE Type and Reference INTEGER(50..+33) Semantics Description dBm

3GPP

Release 11

472

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.35A
Void

Measurement Availability Indicator Measurement Change Time

Presence M Range IE Type and Reference INTEGER (1..6000, ) Semantics Description Unit: ms Range: 10..60000 ms Step: 10 ms

9.2.1.35B

IE/Group Name Measurement Change Time

9.2.1.36

Measurement Filter Coefficient

The Measurement Filter Coefficient determines the amount of filtering to be applied for measurements.
IE/Group Name Measurement Filter Coefficient Presence Range IE Type and Reference ENUMERAT ED(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19, ) Semantics Description

9.2.1.36A

Measurement Hysteresis Time

The Measurement Hysteresis Time provides the duration during which a reporting criterion has to be fulfilled for the Measurement Reporting procedure to be triggered.
IE/Group Name Measurement Hysteresis Time Presence Range IE Type and Reference INTEGER (1..6000, ) Semantics Description Unit: ms Range: 10..60000 ms Step: 10 ms

9.2.1.37

Measurement ID

The Measurement ID uniquely identifies a dedicated measurement within a UE Context or a common measurement within a Distant RNC Context [TDD or a UE measurement within a UE Context].
IE/Group Name Measurement ID Presence Range IE Type and Reference INTEGER(0 .. 2^20-1) Semantics Description

9.2.1.38

Measurement Increase/Decrease Threshold

The Measurement Increase/Decrease Threshold defines the threshold that shall trigger Event C or D.

3GPP

Release 11
IE/Group Name CHOICE Measurement Increase/Decrease Threshold >SIR >>SIR Presence M Range

473
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

INTEGER(0..62)

>SIR Error >>SIR Error

INTEGER(0..124 )

0: 0 dB 1: 0.5 dB 2: 1 dB 62: 31dB FDD Only 0: 0 dB 1: 0.5 dB 2: 1 dB 124: 62 dB 0: 0 dB 1: 0.5 dB 2: 1 dB 112: 56 dB TDD Only 0: 0 dB 1: 0.5 dB 2: 1 dB 126: 63 dB FDD Only 0: 0 chips 1: 0.0625 chips 2: 0.1250 chips 32766: 2047.875 chips

>Transmitted Code Power >>Transmitted Code Power

INTEGER(0..112 ,...)

>RSCP >>RSCP

INTEGER(0..126 )

>Round Trip Time >>Round Trip Time

INTEGER(0..327 66)

>Additional Measurement Thresholds >>Load >>>Load

INTEGER(0..100 )

Units are the same as for the Uplink Load Value IE and Downlink Load Value IE. According to mapping in TS 25.133 [23] and TS 25.123 [24].

>>Transmitted Carrier Power >>>Transmitted Carrier Power >>Received Total Wide Band Power >>>Received Total Wide Band Power >>UL Timeslot ISCP >>>UL Timeslot ISCP

INTEGER(0..100 )

YES

reject

INTEGER(0..620 )

0: 0dB 1: 0.1dB 2: 0.2dB ... 620: 62dB TDD Only 0: 0dB 1: 0.5dB 2: 1dB ... 126: 63dB

YES

reject

INTEGER(0..126 )

YES

reject

3GPP

Release 11
>>RT Load >>>RT Load

474

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER(0..100 )

Units are the same as for the Uplink RT Load Value IE and Downlink RT Load Value IE.

YES

reject

>>NRT Load Information >>>NRT Load Information >>UpPTS interference >>>UpPTS interference Value

INTEGER(0..3) 1.28Mcps TDD Only

YES

reject

INTEGER (0..127,)

According to mapping in TS 25.123 [24]

YES

reject

9.2.1.38A

Measurement Recovery Behavior

This IE controls the Measurement Recovery Behavior.

IE/Group Name Measurement Recovery Behavior Presence Range IE Type and Reference NULL Semantics Description

9.2.1.38B

Measurement Recovery Reporting Indicator

This IE indicates the Measurement Recovery Reporting.

IE/Group Name Measurement Recovery Reporting Indicator Presence Range IE Type and Reference NULL Semantics Description

9.2.1.38C

Measurement Recovery Support Indicator

This IE indicates the Measurement Recovery Support.

IE/Group Name Measurement Recovery Support Indicator Presence Range IE Type and Reference NULL Semantics Description

9.2.1.39

Measurement Threshold

The Measurement Threshold defines which threshold that shall trigger Event A, B, E, F or On Modification.

3GPP

Release 11
IE/Group Name CHOICE Measurement Threshold >SIR >>SIR >SIR Error >>SIR Error >Transmitted Carrier Power >>Transmitted Code Power >RSCP >>RSCP >Rx Timing Deviation >>Rx Timing Deviation >Round Trip Time >>Round Trip Time >Additional Measurement Thresholds >>TUTRAN-GPS Measurement Threshold Information >>>TUTRAN-GPS Measurement Threshold Information >>SFN-SFN Measurement Threshold Information >>>SFN-SFN Measurement Threshold Information >>Load >>>Load Presence Range

475
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

INTEGER(0..63)

INTEGER(0..125 ) INTEGER(0..127 ) INTEGER(0..127 ) INTEGER(0..819 1) INTEGER(0..327 67)

According to mapping in TS 25.133 [23] and TS 25.123 [24]. FDD Only According to mapping in TS 25.133 [23] According to mapping in TS 25.133 [23] and TS 25.123 [24]. TDD Only According to mapping in TS 25.123 [24] Applicable to 3.84Mcps TDD Only According to mapping in TS 25.123 [24] FDD Only According to mapping in TS 25.133 [23]

M M

9.2.1.59C

YES

reject

9.2.1.52B

YES

reject

INTEGER(0..100 )

0 is the minimum indicated load, and 100 is the maximum indicated load. According to mapping in TS 25.133 [23] and TS 25.123 [24].

YES

reject

>>Transmitted Carrier Power >>>Transmitted Carrier Power >>Received Total Wide Band Power >>>Received Total Wide Band Power >>UL Timeslot ISCP >>>UL Timeslot ISCP >>RT Load

INTEGER(0..100 )

YES

reject

INTEGER(0..621 )

According to mapping in TS 25.133 [23] and TS 25.123 [24]. TDD Only According to mapping in TS 25.123 [24]

YES

reject

INTEGER(0..127 )

YES

reject

3GPP

Release 11
>>>RT Load >>NRT Load Information >>>NRT Load Information >>Rx Timing Deviation LCR >>>Rx Timing Deviation LCR >>HS-SICH reception quality >>>HS-SICH reception quality >>UpPTS interference >>>UpPTS interference Value >>Rx Timing Deviation 768 >>>Rx Timing Deviation 768 >>Rx Timing Deviation 384 Extended >>>Rx Timing Deviation 384 Extended >>Extended Round Trip Time >>>Extended Round Trip Time Value >>TUTRAN-GANSS Measurement Threshold Information >>>TUTRAN-GANSS Measurement Threshold Information M

476
INTEGER(0..100 ) INTEGER(0..3)

3GPP TS 25.423 V11.2.0 (2012-06)

YES reject

YES Applicable to 1.28Mcps TDD Only

reject

INTEGER(0..511 ) INTEGER (0..20)

According to mapping in TS 25.123 [24] Applicable to TDD Only According to mapping in TS 25.123 [24] 1.28Mcps TDD Only

YES

reject

YES

reject

INTEGER (0..127,)

According to mapping in TS 25.123 [24] Applicable to 7.68Mcps TDD Only According to mapping in TS 25.123 [24] Applicable to 3.84Mcps TDD Only According to mapping in TS 25.123 [24] FDD Only

YES

reject

INTEGER(0..655 35)

YES

reject

INTEGER(0..327 67)

YES

reject

INTEGER (32767..103041)

Continuation of intervals with step size as defined in TS 25.133 [23].

YES

reject

9.2.1.113

YES

reject

9.2.1.39A

Message Structure

The Message Structure IE gives information for each level with assigned criticality in an hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the Information Element Criticality Diagnostics IE).

3GPP

Release 11
IE/Group Name Message structure Presence Range 1..<maxno oflevels>

477
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message. The IE ID of this levels IE containing the not understood or missing IE. The Repetition Number IE gives, if applicable, the number of occurrences of this levels reported IE up to and including the occurrence containing the not understood or missing IE. Note: All the counted occurrences of the reported IE must have the same topdown hierarchical message structure of IEs with assigned criticality above them. Criticality Assigned Criticality

>IE ID

INTEGER( 0..65535) INTEGER( 1..256)

>Repetition Number

Range bound maxnooflevels

Explanation Maximum no. of message levels to report. The value for maxnooflevels is 256.

9.2.1.40

Message Type

The Message Type uniquely identifies the message being sent.

3GPP

Release 11
IE/Group Name Procedure ID Presence Range 1

478
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

3GPP

Release 11
>Procedure Code M

479
INTEGER (0..255)

3GPP TS 25.423 V11.2.0 (2012-06)

0 = Common Transport Channel Resources Initialisation 1 = Common Transport Channel Resources Release 2 = Compressed Mode Command 3 = Downlink Power Control 4 = Downlink Power Timeslot Control 5 = Downlink Signalling Transfer 6 = Error Indication 7 = Dedicated Measurement Failure 8 = Dedicated Measurement Initiation 9 = Dedicated Measurement Reporting 10 = Dedicated Measurement Termination 11 = Paging 12 = Physical Channel Reconfiguration 14 = Radio Link Addition 15 = Radio Link Deletion 16 = Radio Link Failure 17 = Radio Link Preemption 18 = Radio Link Restoration 19 = Radio Link Setup 20 = Relocation Commit 21 = Synchronised Radio Link Reconfiguration Cancellation 22 = Synchronised Radio Link Reconfiguration Commit 23 = Synchronised Radio Link Reconfiguration Preparation 24 = UnSynchronised Radio Link Reconfiguration 25 = Uplink Signalling Transfer 26 = Common Measurement Failure 27 = Common Measurement Initiation 28 = Common Measurement Reporting 29 = Common Measurement Termination 30 = Information Exchange Failure 31 = Information Exchange Initiation 32 = Information Reporting 33 = Information Exchange Termination 34 = Radio Link Congestion 35 = Reset 36 = Radio Link Activation 37 = GERAN Uplink Signalling Transfer 38 = Radio Link Parameter Update 39 = UE Measurement Failure 40 = UE Measurement Initiation 41 = UE Measurement Reporting 42 = UE Measurement Termination 43 = Iur Deactivate Trace 44 = Iur Invoke Trace 45 = MBMS Attach 46 = MBMS Detach 48 = Direct Information Transfer 49 = Enhanced Relocation 50 = Enhanced Relocation Cancel 51 = Enhanced Relocation Signalling Transfer 52 = Enhanced Relocation Release 53 = MBSFN MCCH Information 54 = Secondary UL Frequency Reporting 55 = Secondary UL Frequency Update 56 = Information Transfer Control 60 = Enhanced Relocation Resource Allocation 61 = Enhanced Relocation Resource

3GPP

Release 11
>Ddmode Type of Message M M

480
ENUMERATED(FDD, TDD, Common, ) ENUMERATED(Initiati ng Message, Successful Outcome, Unsuccessful Outcome, Outcome)

3GPP TS 25.423 V11.2.0 (2012-06)

Common = common to FDD and TDD.

9.2.1.41

Multiple URAs Indicator

The Multiple URAs Indicator indicates whether the accessed cell has multiple URAs.
IE/Group Name Multiple URAs Indicator Presence Range IE Type and Reference ENUMERAT ED(Multiple URA s exist, Single URA Exists) Semantics Description

9.2.1.41a

NACC Related Data

The NACC related data IE provides NACC related information for the indicated GSM cell.
IE/Group Name CHOICE GERAN System Info Type >SI >>SI >PSI >>PSI Presence M M 9.2.1.30Fc GERAN system information SI3, SI13, SI1 (TS 44.060 [47]) GERAN system information PSI1, PSI2, PSI4 (TS 44.060 [47]) Range IE Type and Reference Semantics Description

9.2.1.30Fc

9.2.1.41A

Neighbouring UMTS Cell Information

The Neighbouring UMTS Cell Information IE provides information for UMTS Cells that are neighbouring cells to a cell in the DRNC. The neighbouring cell information is provided for each RNC (including the DRNC) that has cells that are neighbouring cells to the cell in the DRNC.

3GPP

Release 11
IE/Group Name Neighbouring UMTS Cell Information >RNC-ID M Presence Range
1..<maxnoo fneighbouri ngRNCs>

481
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality EACH Assigned Criticality ignore

9.2.1.50

If the Extended RNC-ID IE is included in the Neighbourin g UMTS Cell Information IE, the RNCID IE shall be ignored.

>CN PS Domain Identifier >CN CS Domain Identifier >Neighbouring FDD Cell Information >Neighbouring TDD Cell Information >Neighbouring TDD Cell Information LCR >Extended RNC-ID

O O O O O O

9.2.1.12 9.2.1.11 9.2.1.41B 9.2.1.41D 9.2.1.72 9.2.1.50a The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

YES YES ignore reject

Range bound maxnoofneighbouringRNCs

Explanation Maximum number of neighbouring RNCs.

9.2.1.41B

Neighbouring FDD Cell Information

The Neighbouring FDD Cell Information IE provides information for FDD cells that are neighbouring cells to a cell in the DRNC.

3GPP

Release 11
IE/Group Name Neighbouring FDD Cell Information >C-ID >UL UARFCN >DL UARFCN >Frame Offset >Primary Scrambling Code >Primary CPICH Power >Cell Individual Offset >Tx Diversity Indicator >STTD Support Indicator >Closed Loop Mode1 Support Indicator >Not Used >Restriction State Indicator >DPC Mode Change Support Indicator >Coverage Indicator >Antenna Co-location Indicator >HCS Prio >Cell Capability Container FDD >SNA Information >Frequency Band Indicator >Max UE DTX Cycle M M M O M O O M O O O O O O O O O O O C-CPCDTXDRXCapab le O C-MCCapable C-DBCapable O O Presence Range 1..<max noofFDD neighbo urs>

482
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.6 UARFCN 9.2.1.66 UARFCN 9.2.1.66 9.2.1.30 9.2.1.45 9.2.1.44 9.2.1.7 9.2.2.50 9.2.2.45 9.2.2.2 NULL 9.2.1.48C 9.2.2.56 9.2.1.12G 9.2.1.2C 9.2.1.30N 9.2.2.D 9.2.1.52Ca 9.2.2.59 9.2.2.87

Corresponds to Nu in TS 25.104 [6] Corresponds to Nd in TS 25.104 [6]

YES YES YES YES YES YES YES YES YES ignore ignore ignore ignore ignore ignore ignore ignore ignore

>Multiple PLMN List >Secondary Serving Cell List >Dual Band Secondary Serving Cell List >Cell Capability Container Extension FDD >Cell List Validity Indicator

9.2.1.117 9.2.2.101 Secondary Serving Cell List 9.2.2.101 9.2.2.123 ENUMERAT ED (Ignore Secondary Serving Cell List, Ignore Dual Band Secondary Serving Cell List, Ignore Both)

YES YES YES

ignore ignore ignore

YES YES

ignore ignore

Range bound maxnoofFDDneighbours

Explanation Maximum number of neighbouring FDD cell for one cell.

3GPP

Release 11
Condition CPC-DTX-DRXCapable

483

3GPP TS 25.423 V11.2.0 (2012-06)

MC-Capable DB-Capable

Explanation The IE shall be present if the the fifteenth bit Continuous Packet Connectivity DTX-DRX Support Indicator in the Cell Capability Container FDD IE is set to the value 1. The IE shall be present if the the Multi Cell Support Indicator in the Cell Capability Container FDD IE is set to the value 1. The IE shall be present if the the Dual Band Support Indicator in the Cell Capability Container FDD IE is set to the value 1.

9.2.1.41C

Neighbouring GSM Cell Information

The Neighbouring GSM Cell Information IE provides information for all GSM Cells that are a neighbouring cell to a cell in the DRNC.

3GPP

Release 11
IE/Group Name Neighbouring GSM Cell Information >CGI >>LAI >>>PLMN Identity Presence Range 1..<max noofGS Mneighb ours> 1 1 M

484
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality GLOBAL Assigned Criticality ignore

Cell Global Identity as defined in TS 23.003 [1]. OCTET STRING (3) - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed The Cell Individual Offset to be used for Ues using DCHs. If the Extended GSM Cell Individual Offset IE is present, the Cell Individual Offset IE shall be set to a) 10dB if the Extended GSM Cell Individual Offset IE is < -10dB and b) 10dB if the Extended GSM Cell Individual Offset IE is > 10dB. Base Station Identity Code as defined in TS 23.003 [1]. Network Colour Code. Base Station Colour Code. Indicates whether or not the BCCH ARFCN belongs to the 1800 band or 1900 band of GSM frequencies. BCCH Frequency as defined in TS 45.005 [69].

>>>LAC >>CI >Cell Individual Offset

M M O

OCTET STRING (2) OCTET STRING (2) 9.2.1.7

>BSIC >>NCC >>BCC >Band Indicator M M M

1 BIT STRING(3) BIT STRING(3) ENUMERAT ED(DCS 1800 band, PCS 1900 band, ) INTEGER(0. .1023) 9.2.1.12G

>BCCH ARFCN >Coverage Indicator

M O

YES ignore

3GPP

Release 11
>Antenna Co-location Indicator >HCS Prio > SNA Information >GERAN Cell Capability >GERAN Classmark >Extended GSM Cell Individual Offset O O O O O O

485
9.2.1.2C 9.2.1.30N 9.2.1.52Ca 9.2.1.30Fa 9.2.1.30Fb 9.2.1.26Bb

3GPP TS 25.423 V11.2.0 (2012-06)

YES YES YES YES YES YES ignore ignore ignore ignore ignore ignore

The Extended GSM Cell Individual Offset to be used for Ues using DCHs, for values that exceed the range of the Cell Individual Offset IE.

Range bound maxnoofGSMneighbours

Explanation Maximum number of neighbouring GSM cells for one cell.

9.2.1.41D

Neighbouring TDD Cell Information

The Neighbouring TDD Cell Information IE provides information for 3.84Mcps TDD or 7.68Mcps TDD cells that are neighbouring cells to a cell in the DRNC.
IE/Group Name Neighbouring TDD Cell Information >C-ID >UARFCN >Frame Offset >Cell Parameter ID >Sync Case >Time Slot For SCH >SCH Time Slot >SCTD Indicator >Cell Individual Offset >DPCH Constant Value >PCCPCH Power >Restriction State Indicator >Coverage Indicator >Antenna Co-location Indicator >HCS Prio >Cell Capability Container TDD >Cell Capability Container 7.68Mcps TDD > SNA Information >Multiple PLMN List Condition Case1 Case2 Range bound maxnoofTDDneighbours M M O M M C-Case1 C-Case2 M O O O O O O O O O O O Presence Range 1..<maxnoo fTDDneigh bours> 9.2.1.6 9.2.1.66 9.2.1.30 9.2.1.8 9.2.1.54 Time Slot 9.2.1.56 9.2.1.51 9.2.1.78 9.2.1.7 9.2.1.23 9.2.1.43 9.2.1.48C 9.2.1.12G 9.2.1.2C 9.2.1.30N 9.2.3.1a 9.2.3.31 9.2.1.52Ca 9.2.1.117 Corresponds to Nt in TS 25.105 [7] IE Type and Reference Semantics Description Criticality YES YES YES YES YES YES YES YES Assigned Criticality

ignore ignore ignore ignore ignore ignore ignore ignore

Explanation The IE shall be present if the Sync Case IE is set to Case1. The IE shall be present if the Sync Case IE is set to Case2. Explanation Maximum number of neighbouring 3.84Mcps TDD or 7.68Mcps TDD cell for one cell.

3GPP

Release 11

486

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.41Dd

Neighbouring TDD Cell Measurement Information LCR

This IE provides information on the 1.28Mcps TDD neighbouring cells used for the purpose of Measurements. Since the measurement can be performed on every time slot and midamble shift, the Time slot LCR IE and Midamble shift LCR IE shall be included if available.
IE/Group Name UTRAN Cell Identifier UARFCN Cell Parameter ID Time Slot LCR Midamble shift LCR Presence M M M O O Range IE Type and Reference 9.2.1.71 9.2.1.66 9.2.1.8 9.2.3.12a 9.2.3.4C Semantics Description Corresponds to Nt TS 25.105 [7]

9.2.1.41De

Neighbouring E-UTRA Cell Information

The Neighbouring E-UTRA Cell Information IE provides information for all E-UTRA Cells that are a neighbouring cell to a cell in the DRNC.
IE/Group Name Neighbouring E-UTRA Cell Information >ECGI >>PLMN Identity M Presence Range 1..<max noofEUT RAneigh bours> 1 OCTET STRING (3) IE Type and Reference Semantics Description Criticality Assigned Criticality

>>E-UTRAN Cell Identifier

BIT STRING (28)

EUTRAN Cell Global Identity as defined in TS 36.401 [61]. - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). The leftmost bits of the E-UTRAN Cell Identifier IE value correspond to the value of the eNB ID.

>CHOICE EARFCN Information >>FDD >>>EARFCN-FDD >>>UL EARFCN >>>DL EARFCN >>TDD >>> EARFCN

M 1 M M M 9.2.1.41Df EARFCN 9.2.1.41Df EARFCN 9.2.1.41Df EARFCN Corresponds to NuL in TS 36.104 [62] Corresponds to NdL in TS 36.104 [62] Corresponds to NdL in TS 36.104 [62]

3GPP

Release 11
Range bound maxnoofLTEneighbours

487

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of neighbouring LTE cells for one cell.

9.2.1.41Df

EARFCN

The EARFCN (E-UTRA Absolute Radio Frequency Channel Number) defines the carrier.
IE/Group Name EARFCN Presence Range IE Type and Reference INTEGER (0..maxEAR FCN) Semantics Description Defined in TS 36.104 [62].

9.2.1.41E

Paging Cause

Cause for a CN originated page.

IE/Group Name Paging Cause Presence Range IE Type and Reference ENUMERAT ED( Terminating Conversatio nal Call, Terminating Streaming Call, Terminating Interactive Call, Terminating Background Call, Terminating Low Priority Signalling, , Terminating High Priority Signalling, Terminating cause unknown ) Semantics Description See in TS 25.331 [16]

9.2.1.41F

Paging Record Type

Presence Range IE Type and Reference ENUMERAT ED(IMSI (GSM-MAP), TMSI (GSMMAP), PTMSI (GSMMAP), IMSI (DS-41), TMSI (DS41),...) Semantics Description See TS 25.331 [16]

IE/Group Name Paging Record Type

9.2.1.41Fa

Partial Reporting Indicator

This IE indicates if DRNS may report partially successful measurements.

3GPP

Release 11
IE/Group Name Partial Reporting Indicator Presence

488
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference ENUMERAT ED(partial reporting allowed) Semantics description

9.2.1.41G

Neighbouring FDD Cell Measurement Information

This IE provides information on the FDD neighbouring cells used for the purpose of Measurements.
IE/Group Name UTRAN Cell Identifier UARFCN Primary Scrambling Code Presence M M M Range IE Type and Reference 9.2.1.71 9.2.1.66 9.2.1.45 Semantics Description

Corresponds to Nd TS 25.104 [6]

9.2.1.41H

Neighbouring TDD Cell Measurement Information

This IE provides information on the 3.84Mcps TDD neighbouring cells used for the purpose of Measurements. Since the measurement can be performed on every time slot and midamble shift, the Time slot IE and Midamble shift and burst type IE shall be included if available.
IE/Group Name UTRAN Cell Identifier UARFCN Cell Parameter ID Time slot Midamble Shift And Burst Type Presence M M M O O Range IE Type and Reference 9.2.1.71 9.2.1.66 9.2.1.8 9.2.1.56 9.2.3.4 Semantics Description Corresponds to Nt TS 25.105 [7]

9.2.1.41I

NRT Load Information Value

The NRT Load Information IE indicates the load situation on the cell for the Non Real-Time traffic. Non Real Time traffic corresponds to the Interactive and Background traffic classes.

3GPP

Release 11
IE/Group Name Uplink NRT Load Information Value Presence M

489
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER(0. .3) Semantics Description Mapping of the status: 0: low: The Uplink NRT load is low. 1: medium: The Uplink NRT load is medium. 2: high: Uplink NRT load is high. Probability to admit a new user is low. 3: overloaded: Uplink NRT overload. The probability to admit a new user is low, packets are discarded and the source is recommended to reduce the data flow. Mapping of the status: 0: low: The Downlink NRT load is low. 1: medium: The Downlink NRT load is medium. 2: high: Downlink NRT load is high. Probability to admit a new user is low. 3: overloaded: Downlink NRT overload. The probability to admit a new user is low, packets are discarded and the source is recommended to reduce the data flow.

Downlink NRT Load Information Value

INTEGER(0. .3)

9.2.1.42

Payload CRC Present Indicator

This parameter indicates whether FP payload 16 bit CRC is used or not.

IE/Group Name Payload CRC Presence Indicator Presence Range IE Type and Reference ENUMERAT ED(CRC Included, CRC not included) Semantics Description

9.2.1.43

PCCPCH Power

Primary CCPCH power is the power that shall be used for reference power value in a TDD cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CCPCH, the PCCPCH Power is the linear sum of the power that is used for transmitting the PCCPCH on all branches.
IE/Group Name PCCPCH Power Presence Range IE Type and Reference NTEGER (150..400,...) Semantics Description Unit dBm Range 15.0 to 40.0 dBm, Step size 0.1 dB. -15.0 shall indicate P< -15dBm +40.0 shall indicate P> 40dBm.

9.2.1.44

Primary CPICH Power

Primary CPICH power is the power that is used for transmitting the Primary CPICH in a cell. The reference point is the antenna connector. If Transmit Diversity is applied to the Primary CPICH, the Primary CPICH Power is the linear sum of the power that is used for transmitting the Primary CPICH on all branches.

3GPP

Release 11
IE/Group Name Primary CPICH Power Presence

490
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (100..500) Semantics Description Value = Primary CPICH Power/10 Unit dBm Range 10.0..+50.0 Step 0.1 dB

9.2.1.45

Primary Scrambling Code

The Primary scrambling code to be used in the cell.

IE/Group Name Primary Scrambling Code Presence Range IE Type and Reference INTEGER(0 .. 511) Semantics Description

9.2.1.45A

Priority Queue ID

The Priority Queue ID IE provides the identity of the Priority Queue. The Priority Queue ID is unique across all MACd flows that are currently allocated for one UE Context or across all Common MAC flows within a cell.
IE/Group Name Priority Queue ID Presence Range IE Type and Reference INTEGER (0..7) Semantics Description

9.2.1.45B

Process Memory Size

The Process Memory Size IE is the size of an HARQ process in the DRNS expressed in bits. It provides the maximum number of soft channel bits in the virtual IR buffer (TS 25.212 [9]) or (TS 25.222 [46]).
IE/Group Name Process Memory Size Presence Range IE Type and Reference ENUMERATED ( 800, 1600, 2400, 3200, 4000, 4800, 5600, 6400, 7200, 8000, 8800, 9600, 10400, 11200, 12000, 12800, 13600, 14400, 15200, 16000, 17600, 19200, 20800, 22400, 24000, 25600, 27200, 28800, 30400, 32000, 36000, 40000, 44000, 48000, 52000, 56000, 60000, 64000, 68000, 72000, 76000, 80000, 88000, 96000, 104000, 112000, 120000, 128000, 136000, 144000, 152000, 160000, 176000, 192000, 208000, 224000, 240000, 256000, 272000, 288000, 304000,) Semantics Description

9.2.1.46

Puncture Limit

The maximum amount of puncturing for a transport channel in rate matching.

3GPP

Release 11
IE/Group Name Puncture Limit Presence

491
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..15) Semantics Description 0: 40% 1: 44 % 14: 96% 15: 100% (no puncturing) [FDD Value 0 is not applicable for E-DPCH.]

9.2.1.46A

QE-Selector

The QE-Selector indicates from which source the value for the quality estimate (QE) shall be taken.
IE/Group Name QE-Selector Presence Range IE Type and Reference ENUMERAT ED(selected, nonselected) Semantics Description

9.2.1.47

RANAP Relocation Information

This parameter is transparent to the RNSAP. The parameter contains information for the Relocation procedure as defined in TS 25.413 [2].
IE/Group Name RANAP Relocation Information Presence Range IE Type and Reference BIT STRING Semantics Description The content is defined in TS 25.413 [2].

9.2.1.48

Report Characteristics

The Report Characteristics, defines how the reporting shall be performed.

3GPP

Release 11
IE/Group Name CHOICE Report Characteristics >On Demand >Periodic >>Report Periodicity Presence M Range

492
IE Type and Reference NULL M 9.2.1.48a

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality The periodicity with which the DRNS shall send measurement reports. The threshold for which the DRNS shall trigger a measurement report. Assigned Criticality

>Event A >>Measurement Threshold

9.2.1.39

>>Measurement Hysteresis Time >Event B >>Measurement Threshold

O M

9.2.1.36A 9.2.1.39 The threshold for which the DRNS shall trigger a measurement report.

>>Measurement Hysteresis Time >Event C >>Measurement Increase/Decrease Threshold >>Measurement Change Time

O M M

9.2.1.36A 9.2.1.38 9.2.1.35B The time within which the measurement entity shall rise, in order to trigger a measurement report.

>Event D >>Measurement Increase/Decrease Threshold >>Measurement Change Time

M M

9.2.1.38 9.2.1.35B The time within which the measurement entity shall fall, in order to trigger a measurement report.

>Event E >>Measurement Threshold 1 >>Measurement Threshold 2 >>Measurement Hysteresis Time >>Report Periodicity

M O O O

Measureme nt Threshold 9.2.1.39 Measureme nt Threshold 9.2.1.39 9.2.1.36A 9.2.1.48a

The hysteresis time in ms The periodicity with which the DRNS shall send measurement reports.

>Event F >>Measurement Threshold 1

Measureme nt Threshold 9.2.1.39

3GPP

Release 11
IE/Group Name >>Measurement Threshold 2 >>Measurement Hysteresis Time >>Report Periodicity Presence O O O Range

493
IE Type and Reference Measureme nt Threshold 9.2.1.39 9.2.1.36A 9.2.1.48a

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality The hysteresis time in ms The periodicity with which the DRNS shall send measurement reports. Assigned Criticality

>Additional Report Characteristics >>On Modification >>>On Modification >>>>Measurem ent Threshold >>Event H >>>Event H >>>>Measurem ent Threshold 1 >>>>Measurem ent Threshold 2 >>>>Measurem ent Hysteresis Time >>>>Report Periodicity

1 M 1 M O O O Measureme nt Threshold 9.2.1.39 Measureme nt Threshold 9.2.1.39 9.2.1.36A 9.2.1.48a 9.2.1.39

YES

reject

YES The hysteresis time in ms The periodicity with which the DRNS shall send measurement reports.

reject

>>>>Measurem ent Fluctuation Range

0-100

9.2.1.48a

Report Periodicity

The Report Periodicity defines the frequency at which the Node B shall send measurement reports.
IE/Group Name CHOICE Report Periodicity Scale >millisecond >>Report Periodicity Value >minute >>Report Periodicity Value Presence M M INTEGER (1..6000, ) INTEGER (1..60,) Unit: ms Range: 10..60000 ms Step: 10 ms Unit: min Range: 1..60 min Step: 1 min Range IE Type and Reference Semantics Description

9.2.1.48A

Requested Data Value

The Requested Data Value contains the relevant data concerned the ongoing information exchange. Requested Data Value IE shall include at least one of the following IE.

3GPP

Release 11
IE/Group Name UTRAN Access Point Position with Altitude IPDL Parameters DGPS Corrections GPS Navigation Model and Time Recovery GPS Ionospheric Model GPS UTC Model GPS Almanac GPS Real-Time Integrity GPS RX Pos SFN-SFN Measurement Reference Point Position Cell Capacity Class Value NACC Related Data MBMS Bearer Service Full Address Inter-frequency Cell Information GANSS Common Data >GANSS Ionospheric Model >GANSS RX Pos >GANSS Additional Ionospheric Model >GANSS Earth Orientation Parameters GANSS Generic Data >GANSS ID >DGANSS Corrections >GANSS Navigation Model And Time Recovery >GANSS Time Model >GANSS UTC Model >GANSS Almanac >GANSS Real Time Integrity >GANSS Data Bit Assistance >GANSS Additional Time Models >GANSS Additional Navigation Models And Time Recovery >GANSS Additional UTC Models >GANSS Auxiliary Information >SBAS ID Counting Information Transmission Mode Information MBMS Neighbouring Cell Information RLC Sequene Number ANR Cell Information Condition GANSS-ID Presence O O O O O O O O O O O O O O 0..1 O O O O 0..<maxno ofGANSS > O O O O O O O O O O O O C-GANSSID O O O O O Range

494
IE Type and Reference 9.2.1.75 9.2.1.31F 9.2.1.19B 9.2.1.30I 9.2.1.30H 9.2.1.30L 9.2.1.30G 9.2.1.30J 9.2.1.30K 9.2.1.74 9.2.1.5C 9.2.1.41a 9.2.1.84 9.2.1.31G 9.2.1.105 9.2.1.109 9.2.1.105a 9.2.1.122a

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality YES YES YES YES YES YES YES GLOBAL ignore ignore ignore ignore ignore Ignore Ignore ignore Assigned Criticality

9.2.1.119 9.2.1.102 9.2.1.120 9.2.1.110 9.2.1.111 9.2.1.103 9.2.1.108 9.2.1.118 9.2.1.110a 9.2.1.120a 9.2.1.111a 9.2.1.122c 9.2.1.122b 9.2.2.94 9.2.2.95 9.2.2.96 9.2.2.97 9.2.1.149 FDD only FDD only FDD only FDD only

YES YES YES YES YES YES YES YES YES YES Ignore Ignore Ignore Ignore Ignore ignore ignore ignore ignore ignore

Explanation This IE shall be present if the GANSS ID IE indicates SBAS.

3GPP

Release 11
Range Bound maxnoofGANSS

495

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of GANSS Systems

9.2.1.48B

Requested Data Value Information

The Requested Data Value Information IE provides information on whether or not the Requested Data Value is available in the message and also the Requested Data Value itself if available. In case of Periodic and On Modification reporting, Information Not Available shall be used when at least one part of the requested information was not available at the moment of initiating the Information Reporting procedure.
IE/Group Name CHOICE Information Availability Indicator >Information Available >>Requested Data Value >Information not Available Presence M M 9.2.1.48A NULL Range IE Type and Reference Semantics Description Criticality Assigned Criticality

9.2.1.48C

Restriction State Indicator

The Restriction state indicator is the identifier indicates whether the cell is Cell Reserved for Operator Use or not. It is provided by DRNS and reported to SRNC.
IE/Group Name Restriction state indicator Presence Range IE Type and Reference ENUMERAT ED(Cell Not Reserved for Operator Use, Cell Reserved for Operator Use, ) Semantics Description

9.2.1.48D

RLC Mode

The RLC Mode IE indicates the RLC Mode used for a Priority Queue.
IE/Group Name RLC Mode Presence Range IE Type and Reference ENUMERAT ED ( RLC-AM, RLC-UM,) Semantics Description

9.2.1.49

RL ID

The RL ID is the unique identifier for one RL associated with a UE.

IE/Group Name RL ID Presence Range IE Type and Reference INTEGER (0..31) Semantics Description

3GPP

Release 11

496

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.49A

RL Specific DCH Information

The RL Specific DCH Information IE provides RL Specific DCH Information for DCHs. In case of a set of co-ordinated DCHs requiring a new transport bearer on Iur, the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE shall be included only for one of the DCHs in the set of co-ordinated DCHs.
IE/Group Name RL Specific DCH Information >DCH ID >Binding ID M O Presence Range 1..<maxno ofDCHs> 9.2.1.16 9.2.1.3 Shall be ignored if bearer establishme nt with ALCAP. Shall be ignored if bearer establishme nt with ALCAP. FDD Only IE Type and Reference Semantics Description Criticality Assigned Criticality

>Transport Layer Address

9.2.1.62

>Transport Bearer Not Requested Indicator Range bound maxnoofDCHs

9.2.2.4S

YES

Ignore

Explanation Maximum number of DCHs for one UE.

9.2.1.50

RNC-ID

This is the identifier of one RNC in UTRAN.

IE/Group Name RNC-ID Presence Range IE Type and Reference INTEGER(0. .4095) Semantics Description

9.2.1.50a

Extended RNC-ID

This is the identifier of one RNC in UTRAN.

IE/Group Name Extended RNC-ID Presence Range IE Type and Reference INTEGER(4 096..65535) Semantics Description Note: Application of the Extended RNC-ID IE to very large networks is FFS.

9.2.1.50A

SAT ID

The SAT ID indicates the identity of the satellite.

IE/Group Name SAT ID Presence Range IE Type and Reference INTEGER(0. .63) Semantics Description Identifies the satellite and is equal to (SV ID No 1) where SV ID No is defined in ICD-GPS200 [30].

3GPP

Release 11

497

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.50B

RT Load Value

The RT Load Value IE indicates in percents the ratio of the load generated by Real Time traffic, relative to the measured Load Value. Real Time traffic corresponds to the Conversational and Streaming traffic classes.
IE/Group Name Uplink RT Load Value Downlink RT Load Value Presence M M Range IE Type and Reference INTEGER(0. .100) INTEGER(0. .100) Semantics Description

9.2.1.51

SCH Time Slot

The SCH Time Slot IE represents the first time slot (k) of a pair of time slots inside a Radio Frame that is assigned to the Physical Channel SCH. The SCH Time Slot IE is only applicable if the value of Sync Case IE is Case 2 since in this case the SCH is allocated in TS#k and TS#k+8.
IE/Group Name SCH Time Slot Presence Range IE Type and Reference INTEGER(0. .6) Semantics Description

9.2.1.51A

Scheduling Priority Indicator

Indicates the relative priority of the FACH, [TDD DSCH, USCH,] HS-DSCH [FDD or E-DCH] data frame. Used by the DRNC when scheduling FACH, [TDD DSCH, USCH,] HS-DSCH [FDD or E-DCH] traffic.
IE/Group Name Scheduling Priority Indicator Presence Range IE Type and Reference INTEGER(0. .15) Semantics Description Relative priority of the FACH, [TDD DSCH, USCH,] HSDSCH [FDD or E-DCH] data frame: 0=Lowest Priority 15=Highest Priority

9.2.1.52

Service Area Identifier (SAI)

This information element is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. For this protocol, only a Service Area that is defined to be applicable to the PS and CS domains shall be used.

3GPP

Release 11
IE/Group Name PLMN Identity Presence M

498
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference OCTET STRING (3) Semantics Description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed

LAC SAC

M M

OCTET STRING (2) OCTET STRING (2)

9.2.1.52A

SFN

System Frame Number of the cell, see TS 25.402 [17].

IE/Group Name SFN Presence Range IE Type and Reference INTEGER(0. .4095) Semantics Description

9.2.1.52B

SFN-SFN Measurement Threshold Information

The SFN-SFN Measurement Threshold Information defines the related thresholds SFN-SFN Observed Time Difference measurements which shall trigger the Event On Modification.
IE/Group Name SFN-SFN Change Limit Presence O Range IE Type and Reference INTEGER(1. .256) Semantics Description Change of SFN-SFN value compared to previously reported value, which shall trigger a new report. Unit in 1/16 chip. Deviation the Predicted SFNSFN from the latest measurement result, which shall trigger a new report. Unit in 1/16 chip.

Predicted SFN-SFN Deviation Limit

INTEGER(1. .256)

9.2.1.52C

SFN-SFN Measurement Value Information

The SFN-SFN Measurement Value Information IE indicates the measurement result related to SFN-SFN Observed Time Difference measurements as well as other related information.

3GPP

Release 11
IE/Group Name Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information >UTRAN Cell Identifier >SFN-SFN Value >SFN-SFN Quality Presence

499
Range
1..<maxnoofMeasN Cell>

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

M M O

9.2.1.71 9.2.1.77 INTEGER(0. .255) Indicates the standard deviation (std) of the SFN-SFN otd (observed time difference) measurements in 1/16 chip. SFN-SFN Quality = E[(x-)2] = std of reported SFN-SFN Value, where x is the reported SFNSFN Value and = E[x] is the expectation value of x. Indicates the SFN-SFN drift rate in 1/256 chip per second. A positive value indicates that the Reference cell clock is running at a greater frequency than the measured neighbouring cell. Indicates the standard deviation (std) of the SFN-SFN drift rate measurements in 1/256 chip per second. SFN-SFN Drift Rate Quality = E[(x-)2] = std of reported SFN-SFN Drift Rate, where x is the reported SFNSFN Drift Rate and = E[x] is the expectation value of x.

>SFN-SFN Drift Rate

INTEGER(100..100)

>SFN-SFN Drift Rate Quality

INTEGER(0. .100)

>SFN-SFN Measurement Time Stamp Unsuccessful Neighbouring cell SFNSFN Observed Time Difference Measurement Information >UTRAN Cell Identifier

M
0..<maxnoofMeasN Cell-1>

9.2.1.76

9.2.1.71

Range bound maxnoofMeasNCell

Explanation Maximum number of neighbouring cells on which measurements can be performed.

9.2.1.52Ca

Shared Network Area (SNA) Information

This information element contains a list of Shared Network Areas, identified by the Shared Network Area Code (SNAC, see TS 23.003 [1]) which a certain cell belongs to. For a broader description of the SNA access control see TS 25.401 [40].

3GPP

Release 11
IE/Group Name PLMN Identity Presence M

500
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference OCTET STRING (3) Semantics description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC).

List of SNAs > SNAC M

0..<maxnoofSNAs > INTEGER (0.. 65535) Explanation Maximum number of SNAs one cell can be part of.

Range bound maxnoofSNAs

9.2.1.52D

SID

The SID IE provides the identity of the Size Index.

IE/Group Name SID Presence Range IE Type and Reference INTEGER (0..7) Semantics Description

9.2.1.53

S-RNTI

The S-RNTI identifies the UE in the SRNC.

IE/Group Name S-RNTI Presence Range IE Type and Reference INTEGER(0. .2^20 1) Semantics Description

9.2.1.53a

S-RNTI Group

The S-RNTI Group identifies a group of Ues in the SRNC.

IE/Group Name S-RNTI S-RNTI bit mask index Presence M M Range IE Type and Reference 9.2.1.53 Enumerated( b1, b2,..b19, ) Semantics Description

The S-RNTI group is identified by all S-RNTI values whose bits starting from the most significant bit down to, and including, the bit indicated by S-RNTI bit mask index, are equal to the corresponding bits of the S-RNTI in this IE. The bits of the S-RNTI in this IE that are less significant than the bit position indicated by the S-RNTI bit mask index shall be ignored.

3GPP

Release 11

501

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.54

Sync Case

The SCH and PCCPCH in a TDD cell are mapped on one or two downlink slots per frame. There are two cases of Sync Case as follows: Case 1) Case 2) SCH and PCCPCH allocated in a single TS#k SCH allocated in two TS: TS#k and TS#k+8 PCCPCH allocated in TS#k

[1.28Mcps TDD There is no Sync Case indication needed for 1.28Mcps TDD. If the Sync Case IE must be included in a message from DRNC to SRNC used for 1.28Mcps TDD, the DRNC shall indicate Sync Case 1 and the SRNC shall ignore it.]
IE/Group Name Sync Case Presence Range IE Type and Reference INTEGER (1..2,...) Semantics Description

9.2.1.54A

T1

The T1 IE is used as described in TS 25.321 [41] subclause 11.6.2.3.

IE/Group Name T1 Presence Range IE type and reference ENUMERAT ED (10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 120, 140, 160, 200, 300, 400, ) Semantics description Unit: ms Node B may use this value to stop the re-transmission of the corresponding MAC-hs PDU.

9.2.1.55

TFCI Presence

The TFCI Presence parameter indicates whether the TFCI shall be included. [TDD If it is present in the timeslot, it will be mapped to the channelisation code defined by TS 25.221 [12].]

IE/Group Name TFCI Presence

Presence

Range

IE Type and Reference ENUMERATE D(Present, not present)

Semantics Description

9.2.1.56

Time Slot

The Time Slot represents the time interval assigned to a Physical Channel referred to the start of a Radio Frame.
IE/Group Name Time Slot Presence Range IE Type and Reference INTEGER (0..14) Semantics Description

9.2.1.56A

TNL QoS

This IE indicates the TNL QoS characteristics of the transport bearer for the uplink data traffic. When the DS field IE is used, the value of this IE is configurable by the operator.

3GPP

Release 11

502

3GPP TS 25.423 V11.2.0 (2012-06)

When the Generic Traffic Category IE is used, generic traffic categories are implementation-specific (e.g. they may be determined by the sender from the application parameters). The value assigned to each of these categories and sent in the Generic Traffic Category IE is configurable by the operator, as well as the mapping of this value to DS field (IETF RFC 2474 [44]) at the DRNS side.
IE/Group Name CHOICE TNL QoS type >DS Field >>DS field Presence M M BIT STRING (8)
DS field as defined in IETF RFC 2474 [44]. Typically used when the DRNS and its SRNC are in the same DS domain as defined in IETF RFC 2475 [45].

Range

IE Type and Reference

Semantics Description

>Generic Traffic Category >>Generic Traffic Category

BIT STRING (8)

9.2.1.57

ToAWE

ToAWE is the window endpoint. DL data frames are expected to be received before this window endpoint. ToAWE is defined with a positive value relative Latest Time of Arrival (LtoA). A data frame arriving after ToAWE gives a Timing Adjustment Control frame response.
IE/Group Name ToAWE Presence Range IE Type and Reference INTEGER (0..2559) Semantics Description Unit: msec.

9.2.1.58

ToAWS

ToAWS is the window startpoint. DL data frames are expected to be received after this window startpoint. ToAWS is defined with a positive value relative Time of Arrival Window Endpoint (ToAWE). A data frame arriving before ToAWS gives a Timing Adjustment Control frame response.
IE/Group Name ToAWS Presence Range IE Type and Reference INTEGER (0..1279) Semantics Description Unit: msec.

9.2.1.58a

Trace Depth

The Trace Depth IE is Trace Configuration Parameter what should be traced by the DRNC on the indicated interfaces.
IE/Group Name Trace Depth Presence Range IE Type and Reference ENUMERATED ( Minimum, Medium, Maximum,) Semantics Description Meaning of this parameter is described in TS 32.422 [49]

9.2.1.58b

Trace Recording Session Reference

The Trace Recording Session Reference IE provides a Trace Recording Session Reference allocated by the triggering entity.

3GPP

Release 11
IE/Group Name Trace Recording Session Reference Presence Range

503

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference INTEGER (0..65535)

9.2.1.58c

Trace Reference

The Trace Reference IE provides a Trace Reference allocated by the triggering entity.
IE/Group Name Trace Reference Presence Range IE Type and Reference OCTET STRING (SIZE(2..3)) Semantics Description

9.2.1.58A

Traffic Class

This IE indicates the type of application the Radio Bearer is optimised for.
IE/Group Name Traffic Class Presence Range IE Type and Reference ENUMERATED (conversational, streaming, interactive, background, ...) Semantics Description

9.2.1.59

Transaction ID

The Transaction ID is used to associate all the messages belonging to the same procedure. Messages belonging to the same procedure shall use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure. For procedures addressed to a specific UE Context, the Transaction ID shall uniquely identify a procedure among all ongoing parallel procedures for the same UE using the same procedure code, and initiated by the same protocol peer. For procedures not addressed to a specific UE Context, the Transaction ID shall uniquely identify a procedure among all ongoing parallel procedures using the same procedure code, and initiated by the same protocol peer.
IE/Group Name CHOICE Transaction ID Length >Short >>Transaction ID Value >Long >>Transaction ID Value Presence Range IE Type and Reference Semantics Description The Transaction ID shall be interpreted for its integer value, not for the type of encoding (short or long). M M INTEGER (0..127) INTEGER (0..32767)

9.2.1.59A

Transmitted Carrier Power

The Transmitted Carrier Power IE contains the Transmitted Carrier Power in a cell, as defined in TS 25.215 [11] & TS 25.225 [14].

3GPP

Release 11
IE/Group Name Transmitted Carrier Power Presence

504
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER(0. .100) Semantics Description According to mapping in TS 25.133 [23] and TS 25.123 [24].

9.2.1.59B

TUTRAN-GPS Accuracy Class

Presence Range IE Type and Reference ENUMERAT ED(Accuracy Class A, Accuracy Class B, Accuracy Class C,) Semantics Description More information about Measurement Accuracy Class is included in TS 25.133 [23].

IE/Group Name TUTRAN-GPS Accuracy Class

9.2.1.59C

TUTRAN-GPS Measurement Threshold Information

The TUTRAN-GPS Measurement Threshold Information defines the related thresholds for UTRAN GPS Timing of Cell Frames for UE Positioning measurements shall trigger the Event On Modification.
IE/Group Name TUTRAN-GPS Change Limit Presence O Range IE Type and Reference INTEGER(1. .256) Semantics Description Change of TUTRAN-GPS value compared to previously reported value, which shall trigger a new report. Unit in 1/16 chip. Deviation of the Predicted TUTRAN-GPS from the latest measurement result, which shall trigger a new report. Unit in 1/16 chip.

Predicted TUTRAN-GPS Deviation Limit

INTEGER(1. .256)

9.2.1.59D

TUTRAN-GPS Measurement Value Information

The TUTRAN-GPS Measurement Value Information IE indicates the measurement results related to the UTRAN GPS Timing of Cell Frames for UE Positioning measurements.

3GPP

Release 11
IE/Group Name TUTRAN-GPS Presence 1

505
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description Indicates the UTRAN GPS Timing of Cell Frames for UE Positioning. According to mapping in TS 25.133 [23] and TS 25.123 [24]; significant values range from 0 to 37158911999999. Most Significant Part Least Significant Part Indicates the standard deviation (std) of the TUTRAN-GPS measurements in 1/16 chip. TUTRAN-GPS Quality = E[(x-)2] = std of reported TUTRAN-GPS Value, where x is the reported TUTRANGPS Value and = E[x] is the expectation value of x. Indicates the TUTRAN-GPS drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GPS clock. Indicates the standard deviation (std) of the TUTRAN-GPS drift rate measurements in 1/256 chip per second. TUTRAN-GPS Drift Rate Quality = E[(x-)2] = std of reported TUTRAN-GPS Drift Rate, where x is the reported TUTRANGPS Drift Rate and = E[x] is the expectation value of x.

>MS >LS TUTRAN-GPS Quality

M M O

INTEGER (0..16383) INTEGER (0..4294967 295) INTEGER(0. .255)

TUTRAN-GPS Drift Rate

INTEGER(50..50)

TUTRAN-GPS Drift Rate Quality

INTEGER(0. .50)

9.2.1.60

Transport Bearer ID

The Transport Bearer ID uniquely identifies an Iur transport bearer.

IE/Group Name Transport Bearer ID Presence Range IE Type and Reference INTEGER(0. .4095) Semantics Description

9.2.1.61

Transport Bearer Request Indicator

Indicates whether a new Iur transport bearer needs to be established for carrying the corresponding data stream(s), or whether an existing transport bearer will be used.
IE/Group Name Transport Bearer Request Indicator Presence Range IE Type and Reference ENUMERAT ED(Bearer Requested, Bearer not Requested, ) Semantics Description

3GPP

Release 11

506

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.62

Transport Layer Address

In case of transport bearer establishment with ALCAP (TS 25.426 [3] TS 25.424 [35]), this IE contains the address to be used for Transport Network Control Plane signalling to establish the transport bearer according to TS 25.426 [3], TS 25.424 [35]. In order to allow transport bearer establishment without ALCAP, this IE contains the address of the transport bearer to be used for the user plane transport. For details on the Transport Address used see TS 25.426 [3].
IE/Group Name Transport Layer Address Presence Range IE Type and Reference BIT STRING(1..1 60, ) Semantics Description

9.2.1.63

Transport Format Combination Set (TFCS)

The Transport Format Combination Set is defined as a set of Transport Format Combinations on a Coded Composite Transport Channel. It is the allowed Transport Format Combinations of the corresponding Transport Channels. The DL Transport Format Combination Set is applicable to DL Transport Channels.

3GPP

Release 11
IE/Group Name CHOICE TFCS Values >Always Used >>TFCS Presence M

507
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

1..<maxnoofTFCs >

This choice is always made. The first instance of the parameter corresponds to TFCI zero, the second to 1 and so on. [TDD The first entry (for TFCI 0) should be ignored by the receiver.] 9.2.1.14A

>>>CTFC >>>CHOICE Gain Factors >>>>Signalled Gain Factors >>>>>Gain Factor C

M CPhysChan M

INTEGER(0 ..15)

>>>>>Gain Factor D

INTEGER(0 ..15)

>>>>>Reference TFC nr >>>>Computed Gain Factors >>>>>Reference TFC nr >Not Used

INTEGER(0 ..15)

[FDD For UL DPCCH or control part of PRACH TS 25.213 [21].] [TDD - for UL DPCH mapping in accordance to TS 25.223 [13].] [FDD For UL DPDCH or data part of PRACH TS 25.213 [21].] [TDD Should be set to 0 by the sender, and shall be ignored by the receiver.] If this TFC is a reference TFC, this IE indicates the reference number Indicates the reference TFC to be used to calculate the gain factors for this TFC This choice shall never be made by the SRNC and the DRNC shall consider the procedure as failed if it is received.

INTEGER(0 ..15) NULL

Condition PhysChan

Explanation The choice shall be present if the TFCS concerns a UL DPCH [FDD or PRACH channel]. Explanation The maximum number of Transport Format Combinations.

Range bound maxnoofTFCs

9.2.1.64

Transport Format Set

The Transport Format Set is defined as the set of Transport Formats associated to a Transport Channel, e.g. DCH. [TDD The Transport Format Set for each transport channel within the same CCTrCH shall have the same value for the 2nd Interleaving Mode IE.]

3GPP

Release 11
IE/Group Name Dynamic Transport Format Information >Number of Transport Blocks >Transport Block Size >CHOICE Mode >>TDD >>>Transmission Time Interval Information >>>>Transmission Time Interval Semi-static Transport Format Information >Transmission Time Interval M C Blocks M CTTIdynamic M 1 M Presence

508
Range 1..<maxTFcount>

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description The first instance of the parameter corresponds to TFI zero, the second to 1 and so on. INTEGER (0..512) INTEGER (0..5000) Unit: Bits

1..<maxTTIcount> ENUMERAT ED(10, 20, 40, 80,) ENUMERAT ED (10, 20, 40, 80, dynamic, ) ENUMERAT ED (No codingTDD, Convolutiona l, Turbo,) ENUMERAT ED (1/2, 1/3,) INTEGER (1..maxRM) ENUMERAT ED (0, 8, 12, 16, 24,) Unit: msec

>Type of Channel Coding

Unit: msec Value dynamic for TDD only. For FDD DCH, the value 80 is applicable only when DL DPCH Slot Format IE indicates a slot format with SF=512. [FDD The value No codingTDD shall be treated as logical error if received]

>Coding Rate >Rate Matching Attribute >CRC size

C Coding M M

>CHOICE Mode >>TDD >>>2nd Interleaving Mode

M M ENUMERAT ED(Frame related, Timeslot related,) Explanation The IE shall be present if the Number of Transport Blocks IE is set to a value greater than 0. The IE shall be present if Type of Channel Coding IE is set to Convolutional or Turbo. The IE shall be present if the Transmission Time Interval IE in the Semi-static Transport Format Information IE is set to dynamic.

Condition Blocks Coding TTIdynamic

3GPP

Release 11
Range bound maxTFcount maxRM maxTTIcount

509

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation The maximum number of different transport formats that can be included in the Transport format set for one transport channel. The maximum number that could be set as rate matching attribute for a transport channel. The amount of different TTI that are possible for that transport format is.

9.2.1.65

TrCH Source Statistics Descriptor

Defines the statistics of the data transmitted in the transport channel. This information may be used in reserving resources in the DRNS.
IE/Group Name TrCH Source Statistics Descriptor Presence Range IE Type and Reference ENUMERAT ED(Speech, RRC, Unknown, ) Semantics Description Speech = Statistics of the data corresponds to speech. RRC = Statistics of the data corresponds to RRC signalling Unknown = The statistics of the data is unknown

9.2.1.66

UARFCN

The UTRA Absolute Radio Frequency Channel Number defines the carrier.
IE/Group Name UARFCN Presence Range IE Type and Reference INTEGER(0. .16383, ) Semantics Description Corresponds to: 0.0Hz.. 3276.6MHz see TS 25.104 [6] and TS 25.105 [7].

9.2.1.66A

UE Identity

The UE Identity IE identifies the UE by one of its Permanent NAS Identifier.

IE/Group Name CHOICE UE Identity >IMSI >>IMSI >IMEI >>IMEI >IMEISV >>IMEISV Presence M M M M 9.2.1.31 9.2.1.30T 9.2.1.30U Range IE Type and Reference Semantics Description

9.2.1.67

UL FP Mode

This parameter defines if normal or silent mode of the Frame Protocol shall be used for the UL.
IE/Group Name UL FP Mode Presence Range IE Type and Reference ENUMERAT ED(Normal, Silent,) Semantics Description

9.2.1.68
Void

UL Interference Level

3GPP

Release 11

510

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.68A

Uncertainty Ellipse

This IE contains the uncertainty ellipse used to describe a possible shape of the geographical area of a cell.
IE/Group Name Uncertainty semi-major Presence M Range IE Type and Reference INTEGER( 0..127) INTEGER( 0..127) INTEGER( 0..179) Semantics Description The uncertainty r is derived from the uncertainty code k by r = 10x(1.1k-1) The uncertainty r is derived from the uncertainty code k by r = 10x(1.1k-1) The relation between the IE value (N) and the angle (a) in degrees it describes is 2N a <2(N+1). The values 90..179 shall not be used.

Uncertainty semi-minor

Orientation of major axis

9.2.1.68B

Unidirectional DCH Indicator

The Unidirectional DCH Indicator IE indicates that the DCH is unidirectional.

IE/Group Name Unidirectional DCH Indicator Presence Range IE Type and Reference ENUMERATED (Downlink DCH only, Uplink DCH only) Semantics Description

9.2.1.69

Uplink SIR

The UL SIR indicates a received UL SIR.

IE/Group Name Uplink SIR Presence Range IE Type and Reference INTEGER (82..173) Semantics Description Value = Uplink SIR/10 Unit dB Range -8.2..+17.3 Step 0.1 dB

9.2.1.70

URA ID
Presence Range IE Type and Reference INTEGER(0. .65 535) Semantics Description

IE/Group Name URA ID

9.2.1.70A

UTRAN Access Point Position

The UTRAN Access Point Position indicates the exact geographical position of the base station antenna.

3GPP

Release 11
IE/Group Name Latitude Sign Degrees of Latitude Presence M M Range

511

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(North, South) INTEGER( 0..223-1) Semantics Description

Degrees of Longitude

INTEGER( -223..223-1)

The IE value (N) is derived by this formula: N 223 X /90 < N+1 X being the latitude in degree (0.. 90) The IE value (N) is derived by this formula: N 224 X /360 < N+1 X being the longitude in degree (-180..+180)

9.2.1.70B

URA Information

The URA Information IE contains URA Information for one cell.

IE/Group Name URA ID Multiple URAs Indicator RNCs with Cells in the Accessed URA Presence M M 0 .. <maxRNCin URA-1> Range IE Type and Reference 9.2.1.70 9.2.1.41 Semantics Description Criticality Other RNCs having at least one cell in the URA identified by the URA ID IE. If the Extended RNC-ID IE is included in the URA Information IE, the RNC-ID IE shall be ignored. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. Assigned Criticality

>RNC-ID

9.2.1.50

>Extended RNC-ID

9.2.1.50a

YES

reject

Range Bound maxRNCinURA

Explanation Maximum number of RNC in one URA.

9.2.1.70C

User Plane Congestion Fields Inclusion

The User Plane Congestion Fields Inclusion IE is used by the DRNC to indicate to the SRNC to include in the HSDSCH Data Frames the User Plane fields related to TNL Congestion Control for HSDPA (namely the Frame Sequence Number and the DRT, see TS 25.425 [32]).
IE/Group Name User Plane Congestion Fields Inclusion Presence Range IE Type and Reference ENUMERATED ( Shall be included) Semantics Description

9.2.1.71

UTRAN Cell Identifier (UC-ID)

The UC-ID (UTRAN Cell identifier) is the identifier of a cell in one UTRAN.

3GPP

Release 11
IE/Group Name RNC-ID C-ID Extended RNC-ID Presence M M O

512
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.1.50 9.2.1.6 9.2.1.50a Semantics Description If the Extended RNC-ID IE is included in the UC-ID IE, the RNC-ID IE shall be ignored. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095.

9.2.1.72

Neighbouring TDD Cell Information LCR

The Neighbouring TDD Cell Information LCR IE provides information for 1.28Mcps TDD cells that are neighbouring cells to a cell in the DRNC.
IE/Group Name Neighbouring TDD Cell Information LCR >C-ID >UARFCN >Frame Offset >Cell Parameter ID >SCTD Indicator >Cell Individual Offset >DPCH Constant Value >PCCPCH Power >Restriction State Indicator >Coverage Indicator >Antenna Co-location Indicator >HCS Prio >Cell Capability Container TDD LCR >SNA Information >Multiple PLMN List >Cell Capability Container Extension TDD LCR Range bound maxnoofLCRTDDneighbours M M O M M O O O O O O O O O O O Presence Range 1..<maxno ofLCRTD Dneighbo urs> 9.2.1.6 9.2.1.66 9.2.1.30 9.2.1.8 9.2.1.78 9.2.1.7 9.2.1.23 9.2.1.43 9.2.1.48C 9.2.1.12G 9.2.1.2C 9.2.1.30N 9.2.3.1b 9.2.1.52Ca 9.2.1.117 9.2.3.80 Corresponds to Nt in TS 25.105 [7] IE Type and Reference Semantics Description Criticality Assigned Criticality

YES YES YES YES YES YES YES

ignore ignore ignore ignore ignore ignore ignore

Explanation Maximum number of neighbouring 1.28Mcps TDD cell for one cell.

9.2.1.73

Permanent NAS UE Identity

This element is used to identify the UE in UTRAN.

IE/Group Name Choice Permanent NAS UE Identity >IMSI >>IMSI Presence Range IE Type and Reference Semantics Description

9.2.1.31

3GPP

Release 11

513

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.74

SFN-SFN Measurement Reference Point Position

The SFN-SFN Measurement Reference Point Position indicates the exact geographical position of the SFN-SFN measurement reference point. The altitude shall be included when available.
IE/Group Name Geographical Coordinates Altitude and direction Presence M O Range IE Type and Reference 9.2.1.30F 9.2.1.2B Semantics Description

9.2.1.75

UTRAN Access Point Position with Altitude

The UTRAN Access Point Position with Altitude indicates the exact geographical position of the base station antenna. The altitude shall be included when available.
IE/Group Name Geographical Coordinates Altitude and direction Presence M O Range IE Type and Reference 9.2.1.30F 9.2.1.2B Semantics Description

9.2.1.76

SFN-SFN Measurement Time Stamp

Presence M M 9.2.1.52A Indicates the SFN of the reference cell at which the measurement has been performed. Indicates the SFN of the reference cell at which the measurement has been performed. Indicates the Time Slot of the reference cell at which this measurement has been performed. Range IE Type and Reference Semantics Description

IE/Group Name CHOICE Mode >FDD >>SFN

>TDD >>SFN

9.2.1.52A

>>Time Slot

9.2.1.56

9.2.1.77

SFN-SFN Value
Presence M M M M INTEGER(0. . 614399) INTEGER(0. . 40961) INTEGER(0. . 81923) According to mapping in TS 25.133 [23]. 1.28Mcps or 3.84Mcps TDD According to mapping in TS 25.123 [24]. According to mapping in TS 25.123 [24]. Range IE Type and Reference Semantics Description

IE/Group Name CHOICE Mode >FDD >>SFN-SFN >TDD >>SFN-SFN >TDD 7.68Mcps >>SFN-SFN

9.2.1.78

SCTD Indicator

Indicates if SCTD antenna diversity is applied or not to the PCCPCH and PICH [3.84Mcps TDD].

3GPP

Release 11
IE/Group Name SCTD Indicator Presence

514
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(active, inactive) Semantics Description

9.2.1.79

Congestion Cause

The Congestion Cause IE indicates the cause of a congestion situation:

IE/Group Name Congestion Cause Presence Range IE Type and Reference ENUMERATED (UTRAN Dynamic Resources, UTRAN Semistatic Resources, ) Semantics Description

The meaning of the different congestion cause values is described in the following table:
Congestion cause UTRAN Dynamic Resources Meaning UL and/or DL resource congestion situation mainly caused by the UL and/or DL UTRAN Dynamic Resources. This type of congestion situation is, e.g. related to the limitation of the DL transmitted carrier power of the cell(s), or the UL Interference situation in the concerned cell(s). UL and/or DL resource congestion situation mainly related to UTRAN Semistatic Resources (e.g. channelisation codes, Node-B resources, ..).

UTRAN Semistatic Resources

9.2.1.80

TMGI

The TMGI is the unique identifier for an MBMS bearer service, see TS 23.003 [1].
IE/Group Name PLMN Identity Presence M Range IE Type and Reference OCTET STRING (3) Semantics Description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC).

Service ID

OCTET STRING (3)

9.2.1.81

Transmission Mode

The Transmission Mode IE indicates the transmission mode used for MBMS data transmission in one cell.

3GPP

Release 11
IE/Group Name Transmission Mode Presence

515
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(PTP, PTM, Not Provided). Semantics Description PTP: The MBMS data is transmitted through point to point channel. PTM: The MBMS data is transmitted through point to multipoint channel. Not Provided: The MBMS data is not transmitted in the DRNC.

9.2.1.82

Access Point Name

The APN and IP Multicast Address uniquely identify an MBMS bearer service.
IE/Group Name APN Presence M Range IE Type and Reference OCTET STRING (1..255) Semantics Description

9.2.1.83

IP Multicast Address

The APN and IP Multicast Address uniquely identify an MBMS bearer service.
IE/Group Name IP Multicast Address Presence M Range IE Type and Reference OCTET STRING (4..16) Semantics Description

9.2.1.84

MBMS Bearer Service Full Address

This IE provides the full address of an MBMS Bearer Service otherwise identified by its TMGI.
IE/Group Name Access Point Name IP Multicast Address Presence M M Range IE Type and Reference 9.2.1.82 9.2.1.83 Semantics Description

9.2.1.85

Provided Information

This IE contains the relevant data concerned the direct information transfer procedure. Provided Information IE shall include at least one of the following IEs.
IE/Group Name MBMS Channel Type Information MBMS Preferred Frequency Layer Information UpPCH Information LCR ANR Report Indication Presence O O O O Range IE Type and Reference 9.2.1.86 9.2.1.87 9.2.3.55 9.2.1.148 Applicable to 1.28Mcps TDD only . YES YES ignore ignore Semantics Description Criticality Assigned Criticality

3GPP

Release 11

516

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.86

MBMS Channel Type Information

This IE contains the channel types of a MBMS Bearer Service indicated by TMGI IE in one or more cells. MBMS Channel Type Information IE shall include at least one C-ID IE and Affected UE Information for MBMS IE in the PTM Cell List IE, the PTP Cell List IE and/or Not Provided Cell List IE.

3GPP

Release 11
IE/Group Name TMGI PTM Cell List >C-ID >Affected UE Information for MBMS Presence M

517
Range 0..<maxnoofCells> M 0..<maxnoofUEs>

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.1.80 9.2.1.6 This IE should not be included if the ExtendedAff ected UE Information for MBMS IE is included in the message. 9.2.1.53 The ExtendedAff ected UE Information S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. 9.2.1.154 YES This IE should not be included if the ExtendedAff ected UE Information for MBMS IE is included in the message. 9.2.1.53 The ExtendedAff ected UE Information S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. 9.2.1.154 YES ignore ignore 9.2.1.6 Semantics Description Criticality Assigned Criticality

>>S-RNTI >Extended Affected UE Information for MBMS

M 0..<maxnoofUEs>

>>Extended S-RNTI PTP Cell List >C-ID >Affected UE Information for MBMS

M 0.. <maxnoofCells> M 0..<maxnoofUEs>

>>S-RNTI >Extended Affected UE Information for MBMS

M 0..<maxnoofUEs>

>>Extended S-RNTI Not Provided Cell List >C-ID

M 0.. <maxnoofCells> M

9.2.1.6

3GPP

Release 11
IE/Group Name TMGI >Affected UE Information for MBMS Presence M

518
Range 0..<maxnoofUEs>

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.1.80 Semantics Description This IE should not be included if the ExtendedAff ected UE Information for MBMS IE is included in the message. 9.2.1.53 The ExtendedAff ected UE Information S-RNTI IE shall be used if the S-RNTI identity has a value larger than 1048575. 9.2.1.154 YES ignore Criticality Assigned Criticality

>>S-RNTI >Extended Affected UE Information for MBMS

M 0..<maxnoofUEs>

>>Extended S-RNTI Range Bound maxnoofCells maxnoofUEs

Explanation Maximum number of cells that can be indicated in the corresponding IE. Maximum number of S-RNTIs that can be indicated per cell in the respective IEs.

9.2.1.87

MBMS Preferred Frequency Layer Information

This IE contains the preferred frequency layer of a MBMS Bearer Service indicated by TMGI IE in one or more cells that host at least one CELL_DCH UE whose UE Link contains the concerned MBMS Bearer Service and whose SRNC is different from the CRNC.
IE/Group Name TMGI Preferred Frequency Layer Information >Default Preferred Frequency >Additional Preferred Frequency >>DL UARFCN >>Corresponding Cells >>>C-ID Range Bound maxnoofAddFreq maxnoofCellsPerFreq M Presence M M 0..<maxnoofAddFr eq> M 1..<maxnoofCellsP erFreq> 9.2.1.6 Explanation Maximum number of additional preferred frequencies different from default preferred frequency in an RNC. Maximum number of cells whose preferred frequency is the same. UARFCN 9.2.1.66 Range IE Type and Reference 9.2.1.80 UARFCN 9.2.1.66 Preferred frequencies different from default preferred frequency Semantics Description

3GPP

Release 11

519

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.88

E-DCH DDI Value

The E-DCH DDI Value IE is the Data Description Indicator value identifying a unique combination of E-DCH MAC-d Flow ID and MAC-d PDU Size.
IE/Group Name E-DCH DDI Value Presence Range IE Type and Reference INTEGER (0..62) Semantics Description

9.2.1.89

E-DCH MAC-d Flow Multiplexing List

The E-DCH MAC-d Flow Multiplexing List indicates which E-DCH MAC-d flows are allowed to be multiplexed within a MAC-e PDU with the MAC-d flow it is associated to. If the E-DCH MAC-d Flow Multiplexing List is signalled for an E-DCH MAC-d flow it indicates that E-DCH MAC-d PDUs of this E-DCH MAC-d flow are the first EDCH MAC-d PDU in the MAC-e PDU. If an E-DCH MAC-d Flow Multiplexing List was already received within a previous Radio Link related procedure and no E-DCH MAC-d Flow Multiplexing List is signalled for a E-DCH MAC-d flow, the DRNS shall continue to use the previously received one. If no E-DCH MAC-d Flow Multiplexing List was ever received for an E-DCH MAC-d flow no restrictions shall be assumed for the related E-DCH MAC-d flow for multiplexing E-DCH MAC-d flows.
IE/Group Name E-DCH MAC-d Flow Multiplexing List Presence Range IE Type and Reference BIT STRING (8) Semantics Description The first Bit corresponds to E-DCH MAC-d flow 0, the second bit corresponds to E-DCH MAC-d flow 1, etc. For 1.28Mcps TDD, if the IE is included in the IE Common E-DCH MAC-d Flow Specific Information LCR, the first Bit corresponds to E-DCH MAC-d with the lowest EDCH MAC-d Flow ID within the same frequency, the second bit corresponds to E-DCH MAC-d flow with the second lowest E-DCH MAC-d Flow ID within the same frequency, etc.

9.2.1.90

E-DCH MAC-d Flows To Delete

The E-DCH MAC-d Flows To Delete IE is used for the removal of E-DCH MAC-d flows.
IE/Group Name E-DCH MAC-d Flows To Delete >E-DCH MAC-d Flow ID Range Bound maxnoofEDCHMACdFlows Presence Range 1..<maxnoofEDCH MACdFlows> M 9.2.1.91 Explanation Maximum number of E-DCH MAC-d flows IE Type and Reference Semantics Description

9.2.1.91

E-DCH MAC-d Flow ID

The E-DCH MAC-d Flow ID IE is the unique identifier for one MAC-d flow on E-DCH.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow ID Presence

520
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0.. maxnoofEDC HMACdFlow s-1) Semantics Description

Range Bound maxnoofEDCHMACdFlows

Explanation Maximum number of E-DCH MAC-d flows

9.2.1.91A

E-DCH MAC-d PDU Size Format

The E-DCH MAC-d PDU Size Format IE provides information about the type of MAC-d PDU Size Format thet shall be used for the E-DCH in the new configuration. Fixed MAC-d PDU Size uses MAC-d PDU sizes defined in MAC-d PDU Size List IE of the E-DCH Logical Channel Information IE. Flexible MAC-d PDU Size uses a flexible MAC-d PDU size with a maximum PDU size as defined by Maximum MAC-d PDU Size Extended IE of E-DCH Logical Channel Information IE. The actual MAC-d PDU size is determined as specified in TS 25.123 [24] and TS 25.425 [32].
IE/Group Name E-DCH MAC-d PDU Size Format Presence Range IE Type and Reference ENUMERATED (Fixed MAC-d PDU Size, Flexible MAC-d PDU Size) Semantics Description

9.2.1.92

E-DCH Logical Channel Information

The E-DCH Logical Channel Information IE is used for the establishment of E-DCH Logical Channels.

3GPP

Release 11
IE/Group Name E-DCH Logical Channel Information >Logical Channel ID >Scheduling Priority Indicator >Scheduling Information >MAC-es Guaranteed Bit Rate >E-DCH DDI Value M M M O M Presenc e Range 1..<maxnoofl ogicalchanne ls>

521
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.97 9.2.1.51A 9.2.1.101 9.2.1.98 9.2.1.88 If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value. Value 0x3F is reserved. Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.

>MAC-d PDU Size List >>MAC-d PDU Size M

1..< maxnoofMA CdPDUSize 9.2.1.34A Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.

>Maximum MAC-d PDU Size Extended >MAC-es Maximum Bit Rate LCR >UE Aggregate Maximum Bit Rate Enforcement Indicator Range Bound maxnooflogicalchannels maxnoofMACdPDUSize

O O

MAC PDU Size Extended 9.2.1.34D 9.2.3.59 NULL

YES

reject

1.28Mcps TDD only

YES YES

ignore ignore

Explanation Maximum number of logical channels Maximum number of MAC-d PDU size per Logical Channels

9.2.1.93

E-DCH Logical Channel To Modify

The E-DCH Logical Channel To Modify IE is used for the reconfiguration of E-DCH Logical Channels.

3GPP

Release 11
IE/Group Name E-DCH Logical Channel Information >Logical Channel ID >Scheduling Priority Indicator >Scheduling Information >MAC-es Guaranteed Bit Rate >E-DCH DDI Value M O O O O Presenc e Range 1..<maxnoofl ogicalchanne ls>

522
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.97 9.2.1.51A 9.2.1.101 9.2.1.98 9.2.1.88 If more than 1 MAC-d PDU size is configured for this Logical Channel, the different sizes will use subsequent DDI values starting from this DDI value. Value 0x3F is reserved. Shall be ignored if Maximum MAC-d PDU Size Extended IE is present.

>MAC-d PDU Size List >>MAC-d PDU Size >Maximum MAC-d PDU Size Extended >MAC-es Maximum Bit Rate LCR Range Bound maxnooflogicalchannels maxnoofMACdPDUSize M O

0..< maxnoofMA CdPDUSize 9.2.1.34A MAC PDU Size Extended 9.2.1.34D 9.2.3.59

YES

reject

1.28Mcps TDD only

YES

ignore

Explanation Maximum number of logical channels Maximum number of MAC-d PDU size per Logical Channels

9.2.1.94

E-RNTI

The E-RNTI IE is needed for the UE (or UE group) specific CRC in E-AGCH, see TS 25.319 [52].
IE/Group Name E-RNTI Presence Range IE Type and Reference INTEGER (0..65535) Semantics Description

9.2.1.95

E-DCH Processing Overload Level

The E-DCH Processing Overload Level IE defines the threshold that determines when DRNS shall indicate processing issue problems to the SRNC.

3GPP

Release 11
IE/Group Name E-DCH Processing Overload Level Presence

523
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference INTEGER (0..10,) Semantics description Number of consecutive TTIs. The value 0 is a special value, that means infinity, i.e. when this value is used, the DRNS shall never indicate processing issue to the RNC.

9.2.1.96

E-DCH Power Offset for Scheduling Info

The E-DCH Power Offset for Scheduling Info is used to calculate the [FDD E-DPDCH][TDD E-PUCH] power for transmision of scheduling information without any MAC-d PDUs.
IE/Group Name E-DCH Power Offset for Scheduling Info Presence Range IE Type and Reference INTEGER (0..6) Semantics Description Unit: dB Step: 1 dB

9.2.1.97

Logical channel ID

The Logical Channel ID IE is used to identify a E-DCH logical channel in Scheduling Information that is sent over Uu.
IE/Group Name Logical Channel ID Presence Range INTEGER (1..15) IE Type and Reference Semantics Description

9.2.1.98

MAC-es Guaranteed Bit Rate

The MAC-es Guaranteed Bit Rate IE indicates the guaranteed number of bits per second to be delivered over the air interface under normal operating conditions (provided there is data to deliver) for which the Node B shall provide sufficient UL resources. If the MAC-es Guaranteed Bit Rate IE is received with the value set to 0 during RL set up or modification, no guarantee is applied.
IE/Group Name MAC-es Guaranteed Bit Rate Presence Range IE type and reference INTEGER (0..2^24-1, , 2^24..256,000, 000) Semantics description Unit: bit/s

9.2.1.99

MAC-e Reset Indicator

Indicates the MAC-e (or MAC-i) Reset is performed in UE.

IE/Group Name MAC-e Reset Indicator Presence Range IE Type and Reference ENUMERAT ED (MAC-e Reset) Semantics Description Means MAC-I Reset in case Maximum MAC-d PDU Size Extended is configured for an E-DCH Logical Channel.

9.2.1.100

Maximum Number of Retransmissions for E-DCH

The Maximum Number of Retransmissions for E-DCH IE specifies the upper boundary for retransmissions for a single MAC-d flow.

3GPP

Release 11
IE/Group Name Maximum Number of Retransmissions for E-DCH Presence

524
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..15) Semantics Description

9.2.1.101

Scheduling Information

The Scheduling Information IE indicates whether the scheduling information is included for the E-DCH logical channel or not.
IE/Group Name Scheduling Information Presence Range IE Type and Reference ENUMERAT ED ( Included, Not Included) Semantics Description

9.2.1.102

DGANSS Corrections

This IE contains DGANSS corrections.

IE/Group name DGANSS Reference Time Presence M Range IE Type and Reference INTEGER(0..35 70 by step of 30) Semantics description Seconds. Time in GNSS system time (modulo 3600 s) when the DGANSS corrections were calculated Criticality Assigned Criticality

DGANSS Information >GANSS Signal ID >Status/Health O M

1 to <maxSg nType> 9.2.1.121 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 <maxG ANSSS at> INTEGER(0..63 ) BIT STRING(10) ENUMERATED (UDRE 1.0 m, 1.0m < UDRE 4.0m, 4.0m < UDRE 8.0m, 8.0m < UDRE) If the Cipher information is included these fields are ciphered Defined in TS 25.331 [16]. 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.

>DGANSS Signal Information >>Sat ID >>IOD >>UDRE

CStatus/He alth M M M

3GPP

Release 11
IE/Group name >>PRC >>RRC >>DGNSS Validity Period Presence M M O Range

525
IE Type and Reference INTEGER(2047..2047) INTEGER(127..127) 9.2.1.138

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics description Scaling factor 0.32 meters Scaling factor 0.032 meters/sec Criticality YES ignore Assigned Criticality

Condition Status/Health

Explanation This IE shall be present if the Status/Health IE value is not equal to no data or invalid data. Explanation Maximum number of satellites for which data is included in the IE Maximum number of signals for which data is included in the IE

Range Bound maxGANSSSat maxSgnType

3GPP

Release 11

526

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.103

GANSS Almanac

This IE contains a reduced-precision subset of the ephemeris and clock correction parameters.

3GPP

Release 11
IE/Group name Week Number Presence M

527
Range IE Type and Reference INTEGER(0..2 55)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics description Almanac reference week , number of weeks since the beginning of GANSS specific system time (mod 256) Model 1 Scaling factor 212 s Reference time of almanac within week in GANSS TOD time base Issue-Of Data, common to all satellites Almanacs are in the order of the SV IDs, the smallest ID first. Defined in TS 25.331 [16]. Eccentricity, dimensionless (OS SIS ICD [53]) semi-circles (OS SIS ICD [53]) Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semicircles/sec) (OS SIS ICD [53]) dimensionless Semi-Major Axis delta (meters) (OS SIS ICD [53]) Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (OS SIS ICD [53]) Mean Anomaly at Reference Time (semi-circles) (OS SIS ICD [53]) Argument of Perigee (semi-circles) (OS SIS ICD [53]) Seconds (OS SIS ICD [53]) sec/sec (OS SIS ICD [53]) Model 2
1/2

Criticality

Assigned Criticality

CHOICE Almanac Model >Keplerian Parameters >>Toa

M M INTEGER(0..2 55)

>>IODa >>Satellite Information KP >>>Sat ID >>>e >>>i >>>OMEGADOT

M 1 to <maxGA NSSSatA lmanac> M M M M

INTEGER(0..3 )

INTEGER(0..6 3) BIT STRING(11) BIT STRING(11) BIT STRING(11)

>>>SV Health KP >>>delta A1/2

M M

BIT STRING(4) BIT STRING(17) BIT STRING(16)

>>>OMEGA0

>>>M0

BIT STRING(16) BIT STRING(16) BIT STRING(14) BIT STRING(11)

>>> >>>af0 >>>af1 >NAV Keplerian Parameters >>Keplerian NAV Almanac >>>Toa

M M M

M M INTEGER(0..2 55) Scaling factor 212 s Reference time of almanac within week in GANSS TOD time base

YES

ignore

3GPP

Release 11
>>>Satellite information NAV-KP >>>>Sat ID >>>>e >>>>i M M M

528
1.. <maxGA NSSSatA lmanac> INTEGER (0..63) BIT STRING(16) BIT STRING (16) BIT STRING (16) BIT STRING (8) BIT STRING (24) BIT STRING (24)

3GPP TS 25.423 V11.2.0 (2012-06)

>>>>OMEGADOT

>>>>SV Health >>>>A1/2

M M

>>>>OMEGA0

>>>> >>>>M0

M M

BIT STRING (24) BIT STRING (24) BIT STRING (11) BIT STRING (11)

>>>>af0

>>>>af1

>Reduced Keplerian Parameters >>Keplerian Reduced Almanac >>>Toa

Defined in TS 25.331 [16]. Eccentricity, dimensionless (ISQZSS [59]) Correction to inclination, semi-circles (IS-QZSS [59]) Rate of right ascension, semi-circles/sec (ISQZSS [59]) Satellite health (ISQZSS [59]) Square root of the semi-major axis, meters1/2 (IS-QZSS [59]) Longitude of ascending node of orbit plane at weekly epoch, semi-circles (IS-QZSS [59]) Argument of perigee semi-circles (IS-QZSS [59]) Mean anomaly at reference time semi-circles (IS-QZSS [59]) Apparent satellite clock correction seconds (IS-QZSS [59]) Apparent satellite clock correction sec/sec (IS-QZSS [59]) Model 3

M M INTEGER(0..2 55) Scaling factor 212 s Reference time of almanac within week in GANSS TOD time base

YES

ignore

>>>Satellite information RED-KP >>>>Sat ID >>>> A M M

1.. <maxGA NSSSatA lmanac> INTEGER (0..63) BIT STRING(8) BIT STRING (7) Defined in TS 25.331 [16]. meters (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], ISQZSS [59]) semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59])

>>>>0

3GPP

Release 11
>>>>0 M

529
BIT STRING (7) BIT STRING (1)

3GPP TS 25.423 V11.2.0 (2012-06)

semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) Model 4

>>>>L1 Health

>>>>L2 Health

BIT STRING (1)

>>>>L5 Health

BIT STRING (1)

>Midi Keplerian Parameters >> Keplerian Midi Almanac >>>Toa

M M INTEGER(0..2 55) Scaling factor 212 s Reference time of almanac within week in GANSS TOD time base

YES

ignore

>>>Satellite information MIDI-KP >>>>Sat ID >>>>e M M

1.. <maxGA NSSSatA lmanac> INTEGER (0..63) BIT STRING(11) Defined in TS 25.331 [16]. dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) semi-circles/sec (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) meters1/2 (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], ISQZSS [59]) semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) semi-circles (IS-GPS200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) seconds (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], ISQZSS [59])

>>>> i

BIT STRING (11) BIT STRING (11)

>>>>_dot

>>>>sqrtA

BIT STRING (17) BIT STRING (16) BIT STRING (16) BIT STRING (16) BIT STRING (11)

>>>>0

>>>>

>>>>M0

>>>>afo

3GPP

Release 11
>>>>af1 M

530
BIT STRING (10) BIT STRING (1)

3GPP TS 25.423 V11.2.0 (2012-06)

sec/sec (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], ISQZSS [59]) Dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) dimensionless (ISGPS-200 [55], ISGPS-705 [56], ISGPS-800 [57], ISQZSS [59]) Model 5

>>>>L1 Health

>>>>L2 Health

BIT STRING (1)

>>>>L5 Health

BIT STRING (1)

>GLONASS Keplerian Parameters >> Keplerian GLONASS >>>Satellite information GLO-KP >>>>NA >>>>nA >>>>HnA >>>>nA >>>>tnA >>>>inA >>>>TnA >>>>T_DOTnA >>>>nA >>>> nA >>>>nA >>>>I >>>>MnA >SBAS ECEF Parameters >> ECEF SBAS Almanac >>>Satellite information SBASECEF >>>>Data ID >>>>SV ID >>>>Health

M 1.. <maxGA NSSSatA lmanac> M M M M M M M M M M M M O M 1.. <maxGA NSSSatA lmanac> M M M BIT STRING(2) INTEGER (0..63) BIT STRING (8) Dimensionless (DTFA01-96-C-00025 [58]) Defined in TS 25.331 [16]. Dimensionless (DTFA01-96-C-00025 [58]) BIT STRING(11) BIT STRING (5) BIT STRING (5) BIT STRING (21) BIT STRING (21) BIT STRING (18) BIT STRING (22) BIT STRING (7) BIT STRING (15) BIT STRING (16) BIT STRING (10) BIT STRING (1) BIT STRING (2) days [60] dimensionless [60] dimensionless [60] semi-circles [60] seconds [60] semi-circles [60] sec/orbit period [60] sec/orbit period2 [60] dimensionless [60] semi-circles [60] seconds [60] dimensionless [60] dimensionless [60] Model 6

YES

ignore

YES ignore

3GPP

Release 11
>>>>XG >>>>YG >>>>ZG >>>>XG Rate-ofChange >>>>YG Rate-ofChange >>>>ZG Rate-ofChange >>>>t0 Complete Almanac Provided M M M M M M M O

531
BIT STRING (15) BIT STRING (15) BIT STRING (9) BIT STRING (3) BIT STRING (3) BIT STRING (4) BIT STRING (11) BOOLEAN

3GPP TS 25.423 V11.2.0 (2012-06)

meters (DTFA01-96C-00025 [58]) meters (DTFA01-96C-00025 [58]) meters (DTFA01-96C-00025 [58]) meters/sec (DTFA0196-C-00025 [58]) meters/sec (DTFA0196-C-00025 [58]) meters/sec (DTFA0196-C-00025 [58]) seconds (DTFA01-96C-00025 [58]) This field indicates whether almanac is provided for the full GANSS constellation or not. TRUE means complete GANSS almanac is provided. YES ignore

Range Bound maxGANSSSatAlmanac

Explanation Maximum number of satellites for which data is included in the IE

9.2.1.104

GANSS Clock Model

The IE contains fields needed to model the GANSS clock parameters.

IE/Group name Satellite Clock Model Presence Range 1 to <maxGAN SSClockM od> M M M M O O BIT STRING(14) BIT STRING(12) BIT STRING(18) BIT STRING(28) BIT STRING(10) INTEGER(0. .1) IE Type and Reference Semantics description Model -1 There may be more than one clock model included if defined in SIS ICD (e.g. two for Galileo) defined in OS SIS ICD [53] defined in OS SIS ICD [53] defined in OS SIS ICD [53] defined in OS SIS ICD [53] defined in OS SIS ICD [53] Coded as defined in TS 25.331 [16].

>toc >ai2 >ai1 >ai0 >TGD >Model ID

Range bound maxGANSSClockMod

Explanation Maximum number of satellite clock models for which data is included in the IE.

3GPP

Release 11

532

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.104a

GANSS Additional Clock Models

The IE contains fields needed to model the GANSS clock parameters.

3GPP

Release 11
IE/Group name CHOICE Additional Clock Models >NAV-Clock Model >>toc >>af2 >>af1 >>af0 >>TGD >CNAV/CNAV-2 Clock Model Presence

533
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics description

M M M M M M

BIT STRING(16) BIT STRING (8) BIT STRING (16) BIT STRING (22) BIT STRING (8) BIT STRING (11)

>>toc

>>top

BIT STRING (11)

>>URAoc Index

BIT STRING (5) BIT STRING (3)

>>URAoc1 Index

>>URAoc2 Index

BIT STRING (3)

>>af2-n

BIT STRING (10)

>>af1-n

BIT STRING (20)

>>af0-n

BIT STRING (26)

>>TGD

BIT STRING (13) BIT STRING (13)

>>ISCL1CP

Model-2 Time of clock (seconds) (IS-QZSS [59]) Clock correction polynomial coefficient (sec/sec2) (IS-QZSS [59]) Clock correction polynomial coefficient (sec/sec) (IS-QZSS [59]) Clock correction polynomial coefficient (seconds) (IS-QZSS [59]) Group delay (seconds) (IS-QZSS [59]) Model-3 Clock data reference time of week (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Clock data predict time of week (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) SV clock accuracy index (dimensionless) (IS-GPS-200 [55], IS-GPS-705 [56], ISGPS-800 [57], IS-QZSS [59]) SV clock accuracy change index (dimensionless) (IS-GPS-200 [55], IS-GPS-705 [56], ISGPS-800 [57], IS-QZSS [59]) SV clock accuracy change rate index (dimensionless) (IS-GPS-200 [55], IS-GPS-705 [56], ISGPS-800 [57], IS-QZSS [59]) SV clock drift rate correction coefficient (sec/sec2) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) SV clock drift correction coefficient (sec/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) SV clock bias correction coefficient (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Group delay correction (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Inter signal group delay correction (seconds) (IS-GPS-800 [57], IS-QZSS [59])

3GPP

Release 11
IE/Group name >>ISCL1CD Presence O

534
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (13) BIT STRING (13) Semantics description Inter signal group delay correction (seconds) (IS-GPS-800 [57], IS-QZSS [59]) Inter signal group delay correction (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-QZSS [59]) Inter signal group delay correction (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-QZSS [59]) Inter signal group delay correction (seconds) (IS-GPS-705 [56], IS-QZSS [59]) Inter signal group delay correction (seconds) (IS-GPS-705 [56], IS-QZSS [59]) Model-4 Satellite clock offset (seconds) [60] Relative frequency offset from nominal value (dimensionless) [60] Time difference between transmission in G2 and G1 (seconds) [60] Model-5 (seconds) (DTFA01-96-C00025 [58]) (seconds) (DTFA01-96-C00025 [58]) (sec/sec) (DTFA01-96-C00025 [58])

>>ISCL1C/A

>>ISCL2C

BIT STRING (13)

>>ISCL5I5

BIT STRING (13) BIT STRING (13)

>>ISCL5Q5

>GLONASS Satellite Clock Model > n(tb) > n(tb) > n >SBAS Satellite Clock Model >t0 >aGfo >aGf1

M M O

BIT STRING (22) BIT STRING (11) BIT STRING (5)

M M M

BIT STRING (13) BIT STRING (12) BIT STRING (8)

3GPP

Release 11

535

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.105

GANSS Ionospheric Model

The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere.
IE/Group name ai0 ai1 ai2 GANSS Ionosphere Regional Storm Flags >Storm Flag 1 >Storm Flag 2 >Storm Flag 3 >Storm Flag 4 >Storm Flag 5 Presence M M M 0..1 M M M M M BOOLEAN BOOLEAN BOOLEAN BOOLEAN BOOLEAN This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53] Range IE Type and Reference BIT STRING(12) BIT STRING(12) BIT STRING(12) Semantics description This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53] This parameter is used as defined in OS SIS ICD [53]

9.2.1.105a

GANSS Additional Ionospheric Model

The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere.
IE/Group name Data ID 0 1 2 3 0 1 2 3 Presence M M M M M M M M M Range IE Type and Reference BIT STRING(2) 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 Coded as defined in TS 25.331 [16] seconds (IS-QZSS [59]) sec/semi-circle (IS-QZSS [59]) sec/(semi-circle)2 (IS-QZSS [59]) sec/(semi-circle)3 (IS-QZSS [59]) seconds (IS-QZSS [59]) sec/semi-circle (IS-QZSS [59]) sec/(semi-circle)2 (IS-QZSS [59]) sec/(semi-circle)3 (IS-QZSS [59])

9.2.1.106
Void.

GANSS Navigation Model GANSS Orbit Model

9.2.1.107

This IE contains information for GANSS orbit model parameters.

IE/Group name CHOICE Orbit Model >Keplerian Parameters >>toe Presence M M BIT STRING(14) Model-1 Time-of-Ephemeris in seconds, scale factor 60 (OS SIS ICD [53]) Range IE Type and Reference Semantics description

3GPP

Release 11
IE/Group name >> >>n >>M0 >>OMEGAdot Presence M M M M

536
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING(32) BIT STRING(16) BIT STRING(32) BIT STRING(24) BIT STRING(32) BIT STRING(14) BIT STRING(32) Semantics description Argument of Perigee (semicircles) (OS SIS ICD [53]) Mean Motion Difference From Computed Value (semicircles/sec) (OS SIS ICD [53]) Mean Anomaly at Reference Time (semi-circles) (OS SIS ICD [53]) Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles/sec) (OS SIS ICD [53]) Eccentricity, scale factor 2-33 (OS SIS ICD [53]) Rate of Inclination Angle (semi-circles/sec) (OS SIS ICD [53]) Least significant bits of SemiMajor Axis in (meters) , scale factor 2-19 (OS SIS ICD [53]) Inclination Angle at Reference Time (semi-circles) (OS SIS ICD [53]) Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (OS SIS ICD [53]) Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [53]) Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [53]) Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [53]) Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [53]) Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [53]) Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [53])
1/2

>>e >>Idot >>sqrtA

M M M

>>i0 >>OMEGA0

M M

BIT STRING (32) BIT STRING(32) BIT STRING(16) BIT STRING(16) BIT STRING(16) BIT STRING(16) BIT STRING(16) BIT STRING(16)

>>Crs

>>Cis

>>Cus

>>Crc

>>Cic

>>Cuc

9.2.1.107a

GANSS Additional Orbit Models

This IE contains information for GANSS orbit model parameters.

IE/Group name CHOICE Additional Orbit Models Presence Range IE Type and Reference Semantics description

3GPP

Release 11
IE/Group name >NAV-Keplerian Parameters >>URA Index >>Fit Interval Flag >>toe >> >>n Presence M M M M M

537
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING(4) BIT STRING (1) BIT STRING(16) BIT STRING (32) BIT STRING (16) BIT STRING (32) BIT STRING (24) BIT STRING (32) BIT STRING (14) BIT STRING (32) BIT STRING (32) BIT STRING (32) BIT STRING (16) BIT STRING (16) BIT STRING (16) BIT STRING (16) BIT STRING (16) BIT STRING (16) Semantics description Model-2 SV accuracy (dimensionless) (IS-QZSS [59]) Fit interval indication (dimensionless) (IS-QZSS [59]) Time of ephemeris (seconds) (IS-QZSS [59]) Argument of perigee (semi-circles) (IS-QZSS [59]) Mean motion difference from computed value (semi-circles/sec) (IS-QZSS [59]) Mean anomaly at reference time (semi-circles) (IS-QZSS [59]) Rate of right ascension (semi-circles/sec) (IS-QZSS [59]) Eccentricity (dimensionless) (IS-QZSS [59]) Rate of inclination angle (semi-circles/sec) (IS-QZSS [59]) Square root of semi-major axis (meters1/2) (IS-QZSS [59]) Inclination angle at reference time (semi-circles) (IS-QZSS [59]) Longitude of ascending node of orbit plane at weekly epoch (semi-circles) (IS-QZSS [59]) Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-QZSS [59]) Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-QZSS [59]) Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-QZSS [59]) Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-QZSS [59]) Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-QZSS [59]) Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-QZSS [59])

>>M0 >>OMEGAdot >>e >>Idot >>sqrtA >>i0 >>OMEGA0 >>Crs

M M M M M M M M

>>Cis

>>Cus

>>Crc

>>Cic

>>Cuc

3GPP

Release 11
IE/Group name >CNAV/CNAV-2 Keplerian Parameters >>top Presence

538
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (11) BIT STRING (5) BIT STRING (26) Semantics description Model-3

>>URAoe Index

>>A

>>A_dot

BIT STRING (25) BIT STRING (17)

>>n0

>>n0_dot

BIT STRING (23)

>>M0-n

Bit String(33)

>>en

BIT STRING (33) Bit String(33)

>> n

>>0-n

BIT STRING (33)

>>_dot

BIT STRING (17)

>>io-n

BIT STRING (33)

>>I0-n_dot

BIT STRING (15)

Data predict time of week (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) SV accuracy (dimensionless) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Semi-major axis difference at reference time (meters) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Chane rate in semi-major axis (meters/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Mean motion difference from computed value at reference time (semi-circles/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Rate of mean motion difference from computed value (semi-circles/sec2) (IS-GPS200 [55], IS-GPS-705 [56], ISGPS-800 [57], IS-QZSS [59]) Mean anomaly at reference time (semi-circles) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Eccentricity (dimensionless) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Argument of perigee (semi-circles) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Reference right ascension angle (semi-circles) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Rate of right ascension difference (semi-circles/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Inclination angle at reference time (semi-circles) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59]) Rate of inclination angle (semi-circles/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS800 [57], IS-QZSS [59])

3GPP

Release 11
IE/Group name >>Cis-n Presence M

539
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (16) Semantics description Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Model-4 Age of data (days) [60] Time interval between two adjacent values of tb (minutes) [60] Change of tb flag (dimensionless) [60] Type of satellite (dimensionless) [60] x-coordinate of satellite at time tb (kilometers) [60] x-coordinate of satellite velocity at time tb (kilometers/sec) [60] x-coordinate of satellite acceleration at time tb (kilometers/sec2) [60] y-coordinate of satellite at time tb (kilometers) [60] y-coordinate of satellite velocity at time tb (kilometers/sec) [60] y-coordinate of satellite acceleration at time tb (kilometers/sec2) [60]

>>Cic-n

BIT STRING (16)

>>Crs-n

BIT STRING (24)

>>Crc-n

BIT STRING (24)

>>Cus-n

BIT STRING (21)

>>Cuc-n

BIT STRING (21)

>GLONASS Earth-Centered, Earth-fixed Parameters >>En >>P1 >>P2 >>M >> x n (t b )

M M M O M M M M M M

BIT STRING (5) BIT STRING (2) BIT STRING (1) BIT STRING (2) BIT STRING (27) BIT STRING (24) BIT STRING (5) BIT STRING (27) BIT STRING (24) BIT STRING (5)

>> x n (t b ) x >> n (t b )
>> >>

y n (t b ) y n (t b )

y >> n (t b )

3GPP

Release 11
IE/Group name >> z n (t b ) Presence M M M

540
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (27) BIT STRING (24) BIT STRING (5) Semantics description z-coordinate of satellite at time tb (kilometers) [60] z-coordinate of satellite velocity at time tb (kilometers/sec) [60] z-coordinate of satellite acceleration at time tb (kilometers/sec2) [60] Model-5 Time of applicability (seconds) (DTFA01-96-C00025 [58]) (dimensionless) (DTFA01-96C-00025 [58]) (meters) (DTFA01-96-C-00025 [58]) (meters) (DTFA01-96-C-00025 [58]) (meters) (DTFA01-96-C-00025 [58]) (meters/sec) (DTFA01-96-C00025 [58]) (meters/sec) (DTFA01-96-C00025 [58]) (meters/sec) (DTFA01-96-C00025 [58]) (meters/sec2) (DTFA01-96-C00025 [58]) meters/sec2) (DTFA01-96-C00025 [58]) meters/sec2) (DTFA01-96-C00025 [58])

>> z n (t b ) z >> n (t b )
>SBAS Earth-Centered, Earth-fixed Parameters >>t0 >>Accuracy >>XG >>YG >>ZG >>XG Rate-of-Change >>YG Rate-of-Change >>ZG Rate-of-Change >>XG Acceleration >>YG Acceleration >>ZG Acceleration

C-ClockMo del M M M M M M M M M M

BIT STRING (13) BIT STRING (4) BIT STRING (30) BIT STRING (30) BIT STRING (25) BIT STRING (17) BIT STRING (17) BIT STRING (18) BIT STRING (10) BIT STRING (10) BIT STRING (10)

Condition ClockModel

Explanation This IE shall be present if SBAS Earth-Centered, Earth-fixed Parameters (Model-5) in IE GANSS Additional Clock Models is not included in GANSS Additional Navigation Models IE.

9.2.1.108

GANSS Real Time Integrity

This IE contains parameters that describe the real-time status of the GANSS constellation.
IE/Group name Satellite Information >Bad GANSS Sat ID >Bad GANSS Signal ID M O Presence Range 1 to <maxGAN SSSat> INTEGER(0. .63) BIT STRING(8) Defined in TS 25.331 [16]. Coded as defined in TS 25.331 [16]. IE Type and Reference Semantics description

Range Bound maxGANSSSat

Explanation Maximum number of satellites for which data is included in the IE

3GPP

Release 11

541

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.109

GANSS Receiver Geographical Position (GANSS RX Pos)

The GANSS Receiver Geographical Position IE is used to identify the geographical coordinates of a GANSS receiver relevant for a certain Information Exchange Object.
IE/Group Name Latitude Sign Degrees of Latitude Presence M M Range IE Type and Reference ENUMERATED ( North, South) INTEGER (0..231-1) Semantics Description

Degrees of Longitude

INTEGER (-231..231-1)

The IE value (N) is derived by this formula: N 231 X /90 < N+1 X being the latitude in degree (0.. 90) The IE value (N) is derived by this formula: N 232 X /360 < N+1 X being the longitude in degree (-180..+180)

Direction of Altitude Altitude

M M

ENUMERATED ( Height, Depth) INTEGER (0..215-1)

The relation between the value (N) and the altitude (a) in meters it describes is N a <N+1, except for N=215-1 for which the range is extended to include all greater values of (a).

9.2.1.110

GANSS Time Model

The GANSS Time Model IE contains a set of parameters needed to relate GANSS time to selected time reference indicated by GNSS_TO_ID.
IE/Group name GANSS Time Model Reference Time TA0 TA1 TA2 GNSS_TO_ID Presence M Range IE Type and Reference INTEGER(0..377 99) INTEGER(2147483648..21 47483647) INTEGER (8388608..83886 07) INTEGER (64..63) ENUMERATED( GPS, , Galileo, QZSS, GLONASS) INTEGER(0..819 1) INTEGER (128..127) Semantics description GANSS reference time (modulo 1 week) in seconds. The scale factor is 24 Seconds, scale factor 235

Criticality

Assigned Criticality

M O O M

sec/sec, scale factor 2-51 sec/sec2 , scale factor 268

Week Number Delta_T

O O

Reference week of GANSS Time Model This field specifies the integer seconds of the GNSS-GNSS Time Offset. Scale factor 1 second.

YES ignore

3GPP

Release 11

542

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.110a

GANSS Additional Time Models

The GANSS Additional Time Models IE contains a set of parameters needed to relate GANSS time to selected time references.
IE/Group name GNSS-GNSS Time Model >GANSS Time Model Presence Range 1..<maxGA NSS-1> 9.2.1.110 IE Type and Reference Semantics description

Range Bound maxGANSS-1

Explanation Maximum number of GANSS systems for which data is included in this IE.

9.2.1.111

GANSS UTC Model

The GANSS UTC Model IE contains a set of parameters needed to relate GANSS time to Universal Time Coordinate (UTC).
IE/Group name A1 A0 tot WNt tLS WNLSF DN tLSF Presence M M M M M M M M Range IE 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 (OS SIS ICD [53]) seconds (OS SIS ICD [53]) seconds (OS SIS ICD [53]) weeks (OS SIS ICD [53]) seconds (OS SIS ICD [53]) weeks (OS SIS ICD [53]) days (OS SIS ICD [53]) seconds (OS SIS ICD [53])

9.2.1.111a

GANSS Additional UTC Models

The GANSS Additional UTC Models IE contains several sets of parameters needed to relate GANSS time to Universal Time Coordinate (UTC), as defined in IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], DTFA01-96-C-00025 [58], IS-QZSS [59], [60].

3GPP

Release 11
IE/Group name CHOICE Additional UTC Models >Model Set 1 >A0-n Presence

543
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics description

BIT STRING(16)

>A1-n

BIT STRING (13)

>A2-n

BIT STRING (7)

>tLS

BIT STRING (8)

>tot

BIT STRING (16)

>WNot

BIT STRING (13)

>WNLSF

BIT STRING (8)

>DN

BIT STRING (4)

>tLSF

BIT STRING (8)

Bias coefficient of GNSS time scale relative to UTC time scale (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Drift coefficient of GNSS time scale relative to UTC time scale (sec/sec) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Drift rate correction coefficient of GNSS time scale relative to UTC time scale (sec/sec2) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Current or past leap second count (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Time data reference time of week (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Time data reference week number (weeks) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Leap second reference week number (weeks) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Leap second reference day number (days) (IS-GPS-200 [55], ISGPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Current or future leap second count (seconds) (IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], IS-QZSS [59]) Callendar day number within four-year period beginning since the leap year (days) [60] GLONASS time scale correction to UTC(SU) (seconds) [60] Coefficient to determine UT1 (seconds) [60] Coefficient to determine UT1 (seconds/msd) [60]

>Model Set 2 >NA

BIT STRING (11) BIT STRING (32) BIT STRING (11) BIT STRING (10)

> c >Delta UT1 >>B1 >>B2

M O M M

3GPP

Release 11
IE/Group name >KP >Model Set 3 >A1WNT >A0WNT >tot >WNt >tLS >WNLSF >DN >tLSF >UTC Standard ID Presence O

544
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (2) BIT STRING (24) BIT STRING (32) BIT STRING (8) BIT STRING (8) BIT STRING (8) BIT STRING (8) BIT STRING (8) BIT STRING (8) BIT STRING (3) Semantics description Notification of expected leap second correction (dimensionless) [60] sec/sec (DTFA01-96-C-00025 [58], Message Type 12) seconds (DTFA01-96-C-00025 [58], Message Type 12) seconds (DTFA01-96-C-00025 [58], Message Type 12) weeks (DTFA01-96-C-00025 [58], Message Type 12) seconds (DTFA01-96-C-00025 [58], Message Type 12) weeks (DTFA01-96-C-00025 [58], Message Type 12) days (DTFA01-96-C-00025 [58], Message Type 12) seconds (DTFA01-96-C-00025 [58], Message Type 12) dimensionless Coded as defined in TS 25.331 [16]

M M M M M M M M M

9.2.1.112

TUTRAN-GANSS Accuracy Class

The TUTRAN-GANSS Accuracy Class IE indicates the accuracy class of the UTRAN GANSS Timing of Cell Frames for UE Positioning measurement.
IE/Group Name TUTRAN-GANSS Accuracy Class Presence Range IE Type and Reference ENUMERAT ED (Accuracy Class A, Accuracy Class B, Accuracy Class C,) Semantics Description More information about Measurement Accuracy Class is included in TS 25.133 [23].

9.2.1.113

TUTRAN-GANSS Measurement Threshold Information

The TUTRAN-GANSS Measurement Threshold Information IE defines the related thresholds for UTRAN GANSS Timing of Cell Frames for UE Positioning measurements shall trigger the Event On Modification.

3GPP

Release 11
IE/Group Name TUTRAN-GANSS Change Limit Presence O

545
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER(1. .256) Semantics Description Change of TUTRAN-GANSS value compared to previously reported value, which shall trigger a new report. Unit in 1/16 chip. Deviation of the Predicted TUTRAN-GANSS from the latest measurement result, which shall trigger a new report. Unit in 1/16 chip.

Predicted TUTRAN-GANSS Deviation Limit

INTEGER(1. .256)

9.2.1.114

TUTRAN-GANSS Measurement Value Information

The TUTRAN-GANSS Measurement Value Information IE indicates the measurement results related to the UTRAN GANSS Timing of Cell Frames for UE Positioning measurements.

3GPP

Release 11
IE/Group Name TUTRAN-GANSS Presence M Range

546
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Indicates the UTRAN GANSS Timing of Cell Frames for UE Positioning. According to mapping in TS 25.133 [23] and TS 25.123 [24]; significant values range from 0 to 371589119999 99. Most Significant Part Least Significant Part Indicates the standard deviation (std) of the TUTRANGANSS

Criticality

Assigned Criticality

>MS >LS TUTRAN-GANSS Quality

M M O

INTEGER(0 ..16383) INTEGER(0 ..42949672 95) INTEGER(0 ..255)

TUTRAN-GANSS Drift Rate

INTEGER(50..50)

measurements in 1/16 chip. TUTRAN- GANSS Quality = E[(x)2] = std of reported TUTRANGANSS Value, where x is the reported TUTRANGANSS Value and = E[x] is the expectation value of x. Indicates the TUTRAN- GANSS drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GANSS clock.

3GPP

Release 11
TUTRAN-GANSS Drift Rate Quality O

547
INTEGER(0 ..50)

3GPP TS 25.423 V11.2.0 (2012-06)

Indicates the standard deviation (std) of the TUTRANGANSS drift rate measurements in 1/256 chip per second. TUTRAN- GANSS Drift Rate Quality = E[(x-)2] = std of reported TUTRAN- GANSS Drift Rate, where x is the reported TUTRAN- GANSS Drift Rate and = E[x] is the expectation value of x. Absence of this IE means Galileo system time.

GANSS Time ID

9.2.1.119a

YES

ignore

9.2.1.115
Void.

GANSS Reference Time

3GPP

Release 11

548

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.116

HARQ Memory Partitioning

Presence 1 M INTEGER (1..8,...12,1 4,16) For HARQ process IDs going from 0 to Number of Processes 1 the Total number of soft channel bits (TS 25.306 [42]) is partitioned equally between all HARQ processes according to the rules in TS 25.331 [16]. The first instance of the parameter corresponds to HARQ process with identifier 0, the second instance to HARQ process with identifier 1, and so on. See TS 25.331 [16] FDD and 1.28Mcps TDD only The 1st instance corresponds to HARQ process with identifier set to maxnoofHARQp rocesses, the 2nd instance to HARQ process with identifier set to maxnoofHARQp rocesses+1, and so on. See TS 25.331 [16] Range IE Type and Reference Semantics Description Criticality Assigned Criticality

IE/Group Name CHOICE HARQ Memory Partitioning >Implicit >>Number of Processes

>Explicit >>HARQ Memory Partitioning I

1..<maxno ofHARQpr ocesses>

>>>Process Memory Size >>HARQ Memory Partitioning Information Extension For MIMO

M 0, 4, 6 or 8

9.2.1.49D

GLOBAL ignore

>>>Process Memory Size

9.2.1.49D

Range Bound MaxnoofHARQprocesses

Explanation Maximum number of HARQ processes for one UE [FDD per stream (the maximum number of HARQ processes per UE is 2 * MaxnoofHARQprocesses in dual stream transmission mode)]

3GPP

Release 11

549

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.117

Multiple PLMN List

This information element contains a list of PLMN identities, which identifies the broadcasted PLMN Identities in MOCN and GWCN shared network configurations. The mandatory PLMN Identity in the MIB (called common PLMN in TS 23.251 [54]) is the first PLMN.
IE/Group Name PLMN Identity Presence M Range IE type and reference OCTET STRING (SIZE (3)) Semantics description - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). List of PLMNs >PLMN Identity M 0 .. <maxNrOfBroadc astPLMNs> OCTET STRING (SIZE (3)) - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). Range bound maxNrOfBroadcastPLMNs Explanation Maximum number of additional PLMN identitys that can be broadcasted in a cell involved in a MOCN or GWCN Shared Network configuration. The value for maxNrOfBroadcastPLMNs is 5.

9.2.1.118

GANSS Data Bit Assistance

3GPP

Release 11
IE/Group Name GANSS TOD Presence M Range

550

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER(0..59,) Semantics Description Refererence time (modulo 1 minute) of the first bit of the data in Data Bits IE, in seconds. Defined in TS 25.331 [16].

Data Bit Assistance List >Sat ID >Data Bit Assistance Sgn List >>GANSS Signal ID >>Data Bits

1..<maxGANS SSat> M 1..<maxSgnTy pe> M M 9.2.1.121 BIT STRING(1..1024) Raw data bits as transmitted from a specific satellite at the time indicated by GANSS_TOD. See TS 25.331 [16]. INTEGER(0..63)

Range Bound maxGANSSSat maxSgnType

Explanation Maximum number of satellites for which data is included in the IE Maximum number of GANSS signals included in the IE

9.2.1.119

GANSS ID

This IE defines a particular GANSS.

IE/Group Name GANSS ID Presence M Range IE Type and Reference INTEGER(0..7 ,) Semantics Description Defines the GANSS and is coded as defined in TS 25.331 [16].

9.2.1.119a

GANSS Time ID

This IE defines a particular GANSS system time.

IE/Group Name GANSS Time ID Presence M Range IE Type and Reference INTEGER(0..7 ,) Semantics Description Defines the GANSS system time for the UTRAN GANSS Timing of Cell Frames for UE Positioning. Coded as defined in TS 25.331 [16], subclause 10.3.7.93a.

9.2.1.120

GANSS Navigation Model And Time Recovery

This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE.

3GPP

Release 11
IE/Group name GANSS Transmission Time Non-Broadcast Indication Presence M O

551
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.1.122 ENUMERAT ED(true) Semantics description GANSS Time when the Navigation model has been retrieved If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1

Satellite Information >Sat ID M

1 to <maxGAN SSSat>

INTEGER(0. Defined in TS 25.331 [16]. .63) >SV Health M BIT Coded as defined in OS SIS STRING(5) ICD [53] >IOD M BIT STRING(10) >GANSS Clock Model M 9.2.1.104 >GANSS Orbit Model M 9.2.1.107 NOTE 1: The Non-Broadcast Indication allows to inform that the navigation model is not bit-to-bit the one broadcast by the satellite. If it is set to 1, the UE is informed that techniques such as data wiping off applied to the navigation model may not work for instance. Condition Orbit model Explanation The IE shall be present if the GANSS Orbit Model IE indicates Keplerian Parameters. Explanation Maximum number of satellites for which data is included in the IE.

Range bound maxGANSSSat

9.2.1.120a

GANSS Additional Navigation Models And Time Recovery

This IE contain information required to manage the transfer of precise navigation data to the GANSS-capable UE.
IE/Group name GANSS Transmission Time Non-Broadcast Indication Presence M O Range IE Type and Reference 9.2.1.122 ENUMERAT ED(true) 1..<maxGA NSSSat> M M M M INTEGER(0. .63) BIT STRING(6) BIT STRING(11) GANSS I Clock Models 9.2.1.104a GANSS Additional Orbit Models 9.2.1.107a Defined in TS 25.331 [16]. Coded as defined in TS 25.331 [16]. Coded as defined in TS 25.331 [16]. Semantics description GANSS Time when the Navigation model has been retrieved If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 in 9.2.1.120.

Satellite Information >Sat ID >SV Health >IOD >GANSS Additional Clock Models >GANSS Additional Orbit Models

3GPP

Release 11
Range bound maxGANSSSat

552

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64

9.2.1.121

GANSS Signal ID

This IE defines a specific signal within a particular GANSS.

IE/Group Name GANSS Signal ID Presence M Range IE Type and Reference INTEGER(0..7,) Semantics Description Coded as defined in TS 25.331 [16].

9.2.1.122

GANSS Transmission Time

This IE indicates the GANSS Transmission Time.

IE/Group name GANSS Day Presence O Range IE Type and Reference INTEGER(0.. 8191) Semantics description The sequential number of days from the origin of the GNSS system time (indicated by the GANSS_ID given in the Requested Data Value IE) modulo 8192 days (about 22 years). GANSS Time of Day in seconds

GANSS TOD

INTEGER(0.. 86399)

9.2.1.122a

GANSS Earth Orientation Parameters

3GPP

Release 11
IE/Group Name tEOP PM_X Presence M M

553
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING(16) BIT STRING (21) Semantics Description EOP data reference time (seconds) (IS-GPS-200 [55]) X-axis polar motion value at reference time (arc-seconds) (IS-GPS-200 [55]) X-axis polar motion drift at reference time (arc-seconds/day) (IS-GPS200 [55])

PM_X_dot

BIT STRING (15)

PM_Y

BIT STRING (21)

Y-axis polar motion value at reference time (arc-seconds) (IS-GPS-200 [55])

PM_Y_dot

BIT STRING (15)

Y-axis polar motion drift at reference time (arc-seconds/day) (IS-GPS200 [55])

UT1

BIT STRING (31)

UT1-UTC difference at reference time (seconds) (IS-GPS-200 [55])

UT1_dot

BIT STRING (19)

Rate of UT1-UTC difference at reference time (seconds/day) (IS-GPS-200 [55])

9.2.1.122b

SBAS ID

This IE defines a specific SBAS.

IE/Group Name SBAS ID Presence M Range IE Type and Reference ENUMERATED( WAAS, EGNOS, MSAS, GAGAN, ) Semantics Description

3GPP

Release 11

554

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.122c

GANSS Auxiliary Information

Presence Range IE Type and Reference Semantics description This choice may only be present if GANSS ID indicated Modernized GPS 1 .. <maxGAN SSSat> M M INTEGER(0. .63) BIT STRING(8) Defined in TS 25.331 [16]. Coded as defined in TS 25.331 [16]. This choice may be present if GANSS ID indicated GLONASS

IE/Group name CHOICE GANSS-ID >GANSS-ID-1 >>Aux Info List >>>Sat ID >>>Signals Available >GANSS-ID-3 >>Aux Info List >>>Sat ID >>>Signals Available >>>Channel Number

1 .. <maxGAN SSSat> M M M INTEGER(0. .63) BIT STRING(8) INTEGER (-7..13) Defined in TS 25.331 [16]. Coded as defined in TS 25.331 [16]. This field indicates the GLONASS carrier frequency number of the satellite identified by Sat ID, as defined in [60].

Range Bound maxGANSSSat

Explanation Maximum number of GANSS satellites for which data is included in this IE.

9.2.1.122d

Additional Ionospheric Model Request

Presence M Range IE Type and Reference BIT STRING(2) Semantics Description Data ID for GANSS Additional Ionospheric Model as defined in TS 25.331 [16], subclause 10.3.7.92b.

IE/Group Name Additional Ionospheric Model Request

9.2.1.122e

Earth Orientation Parameters Request

Presence M Range IE Type and Reference BOOLEAN Semantics Description True means requested.

IE/Group Name Earth Orientation Parameters Request

9.2.1.122f

GANSS Additional Navigation Models And Time Recovery Request

Presence M Range IE Type and Reference BOOLEAN Semantics Description True means requested.

IE/Group Name GANSS Additional Navigation Models And Time Recovery Request

3GPP

Release 11

555

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.122g

GANSS Additional UTC Models Request

Presence M Range IE Type and Reference BOOLEAN Semantics Description True means requested.

IE/Group Name GANSS Additional UTC Models Request

9.2.1.122h

GANSS Auxiliary Information Request

Presence M Range IE Type and Reference BOOLEAN Semantics Description True means requested.

IE/Group Name GANSS Auxiliary Information Request

9.2.1.123

SixtyfourQAM DL Support Indicator

The SixtyfourQAM DL Support Indicator indicates whether the particular cell is capable to support Sixtyfour QAM in DL or not.
IE/Group Name SixtyfourQAM DL Support Indicator Presence Range IE Type and Reference ENUMERAT ED (SixtyfourQA M DL Supported, SixtyfourQA M DL Not Supported) Semantics Description

9.2.1.124

RANAP Enhanced Relocation Information Request

This parameter is transparent to the RNSAP. The parameter contains information for the Enhanced Relocation procedure as defined in TS 25.413 [2].
IE/Group Name RANAP Enhanced Relocation Information Request Presence Range IE Type and Reference BIT STRING Semantics Description The content is defined in TS 25.413 [2].

9.2.1.125

RANAP Enhanced Relocation Information Response

This parameter is transparent to the RNSAP. The parameter contains information for the Enhanced Relocation procedure as defined in TS 25.413 [2].
IE/Group Name RANAP Enhanced Relocation Information Response Presence Range IE Type and Reference BIT STRING Semantics Description The content is defined in TS 25.413 [2].

9.2.1.126

Released CN Domain

The parameter indicates the CD Domain(s) which the RNC shall release the related resource for.
IE/Group Name CHOICE Released CN Domain >PS Domain >CS Domain >PS and CS Domain Presence M NULL NULL NULL Range IE Type and Reference Semantics Description

3GPP

Release 11

556

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.127

Secondary CCPCH system information MBMS

The parameter contains information for the Secondary CCPCH system information MBMS as defined in TS 25.331 [16].
IE/Group Name Secondary CCPCH system information MBMS Presence Range IE Type and Reference BIT STRING Semantics Description The content is defined in TS 25.331 [16].

9.2.1.128

MBSFN Cluster Identity

The parameter is the identifier of a MBSFN cluster in one PLMN.

IE/Group Name MBSFN Cluster Identity Presence Range IE Type and Reference INTEGER (0..65535) Semantics Description the identifier of a MBSFN cluster in one PLMN

9.2.1.129

MBSFN Scheduling Transmission Time Interval

The parameter is the identifier of an MBSFN Scheduling Transmission Time Interval.

IE/Group Name MBSFN Scheduling Transmission Time Interval Presence Range IE Type and Reference INTEGER (4,8,16,32, 64,128,256) Semantics Description Number of TTIs

9.2.1.130

MAC-ehs Reset Timer

The MAC-ehs Reset Timer IE is used as Reset Timer(Treset) described in TS 25.321 [41] subclause 11.6.4.5.
IE/Group Name MAC-ehs Reset Timer Presence Range IE type and reference ENUMERAT ED (1, 2, 3, 4, ) Semantics description Timer in multiples of T1 values (milliseconds). Used when MAC-ehs reordering queue is reset in CELL_FACH and CELL_PCH

9.2.1.131

Enhanced FACH Support Indicator

This IE indicates the Enhanced FACH Support. [1.28Mcps TDD This IE indicates the Enhanced FACH Support in both downlink and uplink.]
IE/Group Name Enhanced FACH Support Indicator Presence Range IE Type and Reference NULL Semantics Description

9.2.1.132

Enhanced PCH Capability

This IE indicates the UE is capable of Enhanced PCH or not.

3GPP

Release 11
IE/Group Name Enhanced PCH Capability Presence

557
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED (Enhanced PCH Capable, Enhanced PCH Not Capable) Semantics Description

9.2.1.133

Priority Queue Information for Enhanced FACH/PCH

The Priority Queue Information for Enhanced FACH/PCH IE provides information associated to HSDPA Priority Queue used for Enhanced FACH and/or Enhanced PCH.
IE/Group Name Priority Queue Information >Priority Queue ID >Scheduling Priority Indicator >T1 >MAC-ehs Reset Timer >Discard Timer >MAC-hs Window Size >Maximum MAC-d PDU Size M M M M O M M Presence Range 1..<maxnoo fPrioQueue s> 9.2.1.45A 9.2.1.51A 9.2.1.54A 9.2.1.130 9.2.1.19C 9.2.1.34C MAC PDU Size Extended 9.2.1.34D Explanation Maximum number of Priority Queues IE Type and Reference Semantics Description

Range Bound maxnoofPrioQueues

9.2.1.134

MIMO Activation Indicator

Presence M Range IE Type and Reference NULL Semantics Description

IE/Group Name MIMO Activation Indicator

9.2.1.135

MIMO Mode Indicator

Presence Range IE Type and Reference ENUMERATED (Activate, Deactivate) Semantics Description

IE/Group Name MIMO Mode Indicator

9.2.1.136

DL RLC PDU Size Format

The DL RLC PDU Size Format IE indicates the downlink RLC PDU size format used for a Priority Queue.
IE/Group Name DL RLC PDU Size Format Presence Range IE Type and Reference ENUMERATED ( Fixed RLC PDU size, Flexible RLC PDU size ,...) Semantics Description

3GPP

Release 11

558

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.137

UE Aggregate Maximum Bit Rate

The UE Aggregate Maximum Bitrate IE is applicable for all Non-GBR bearers per UE which is defined for the Downlink and the Uplink direction and provided by the CN to the RNC. At least one of the UE Aggregate Maximum Bit Rate Downlink IE and UE Aggregate Maximum Bit Rate Uplink IE shall be included in the UE Aggregate Maximum Bit Rate IE.
IE/Group Name UE Aggregate Maximum Bit Rate >UE Aggregate Maximum Bit Rate Downlink O INTEGER (1..1,000,00 0,000) Presence Range IE type and reference Semantics description Desc: Applicable for non-GBR bearers

Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in DL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present. Desc.: This IE indicates the aggregated maximum number of bits delivered by UTRAN and to UTRAN in UL within a period of time, divided by the duration of the period for all non-GBR bearers in one UE. The MBR of non-GBR bearers shall be ignored if this IE present.

>UE Aggregate Maximum Bit Rate Uplink

INTEGER (1..1,000,00 0,000)

9.2.1.138

DGNSS Validity Period

This IE defines the validity period of the GNSS differential corrections provided in DGPS corrections and DGANSS corrections IEs.
IE/Group Name UDRE Growth Rate Presence M Range IE Type and Reference Enumerated( UDRE growth 1.5, UDRE growth 2, UDRE growth 4, UDRE growth 6, UDRE growth 8, UDRE growth 10, UDRE growth 12, UDRE growth 16) Enumerated( val20sec, val40sec, val80sec, val160sec, val320sec, val640sec, val1280sec, val2560sec) Semantics Description This field provides an estimate of the growth rate of uncertainty (1-) in the corrections. The UDRE at time value specified in the Time of Validity for UDRE Growth Rate field is the value of this field times the value of UDRE provided in DGPS Corrections or DGANSS corrections IE (TS 25.331 [16]). This field specifies the time when the UDRE Growth Rate field applies (TS 25.331 [16]).

Time of Validity for UDRE Growth Rate

3GPP

Release 11

559

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.139

MDT Configuration

The IE defines the MDT function parameters.

3GPP

Release 11
IE/Group Name MDT Activation CHOICE MDT Area Scope >Cell based >>Cell ID List >>>Cell-ID Presence M M

560
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference ENUMERATED(MDT Only, MDT and Trace, ) Semantics description

1 to <maxnoofCe llID> INTEGER (0..2684354 55)

This information element identifies a cell uniquely within UTRAN and consists of RNC-ID and C-ID as defined in TS 25.401 [40].

>LA Based >>LAI List >>>LAI >>>>PLMN Identity M M

1 to <maxnoofLA Is> OCTET STRING (3) - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed

>>>>LAC >RA Based >>RAI List >>>RAI >>>>PLMN Identity

M 0 to <maxnoofR AIs>

OCTET STRING (2)

OCTET STRING (3)

>>>>LAC >>>>RAC >PLMN Area Based

M M

OCTET STRING (2) OCTET STRING (1) NULL

This element identifies an area in which the MDT Configuration applies. - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). 0000 and FFFE not allowed

3GPP

Release 11
M1 Report O

561
9.2.2.128

3GPP TS 25.423 V11.2.0 (2012-06)

M1: FDD only CPICH RSCP and CPICH Ec/No measurement by UE. This information element shall not be sent, ignored if received. M2: P-CCPCH RSCP and Timeslot ISCP for UTRA 1.28 TDD. This information element shall not be sent, ignored if received.

M2 Report

9.2.3.83

M3 Report Range bound maxnoofCellID maxnoofLAIs maxnoofRAIs

NULL Explanation Maximum no. of Cell ID subject for MDT scope. Value is 32. Maximum no. of LAI subject for MDT scope. Value is 8. Maximum no of RAI subject for MDT scope. Value is 8.

9.2.1.140

MDT Report parameters

This IE defines the report parameters for MDT periodic reports.

IE/Group Name MDT Report Parameters >Report interval Presence M Range IE type and reference ENUMERATED ( ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ms12000, ms16000, ms20000, ms24000, ms32000, ms64000, ... ) ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity, ... ) Semantics description This IE is defined in TS25.331[10]

>Report amount

9.2.1.141

Neighbouring UMTS Cell Information Extension

The Neighbouring UMTS Cell Information Extension IE is an extension IE to the Neighbouring UMTS Cell Information IE and indicates the UMTS neigbouring cells in the same way as in the Neighbouring UMTS Cell Information IE. The DRNC may use the Neighbouring UMTS Cell Information Extension IE to indicate remaining UMTS neighbouring cells if the number of neighbouring RNCs exceeds the predefined maximum number of neighbouring RNCs (maxnoofneighbouringRNCs).

3GPP

Release 11
IE/Group Name Neighbouring UMTS Cell Information Extension >RNC-ID >CN PS Domain Identifier >CN CS Domain Identifier >Neighbouring FDD Cell Information >Neighbouring TDD Cell Information >Neighbouring TDD Cell Information LCR >Extended RNC-ID M O O O O O O Presence Range

562
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

1..<maxno ofextended neighbouri ngRNCs> 9.2.1.50 9.2.1.12 9.2.1.11 9.2.1.41B 9.2.1.41D 9.2.1.72 9.2.1.50a The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. If the Extended RNC-ID IE is included in the Neighbouring UMTS Cell Information IE, the RNC-ID IE shall be ignored.

Range bound maxnoofextendedneighbouringRNCs

Explanation Maximum number of extended neighbouring RNCs.

9.2.1.142

Source ID

The Source ID IE identifies the source for the relocation of SRNS. The Source ID shall be the SAI of the relocation source.
IE/Group Name SAI Presence M Range IE type and reference 9.2.1.52 Semantics description

9.2.1.143

Target ID

The Target ID IE identifies the target for the relocation of SRNS. The target ID shall be the Cell Global ID of the relocation target.
IE/Group Name CGI Presence M Range IE type and reference 9.2.1.5D Semantics description

9.2.1.144

MS Classmark 2

The coding of this element is described in TS 24.008 [66].

IE/Group Name MS Classmark 2 Presence M Range IE type and reference OCTET STRING Semantics description Coded same way as the Mobile Station Classmark 2 IE defined in TS 24.008 [66]..

9.2.1.145

MS Classmark 3

The coding of this element is described in TS 24.008 [66].

3GPP

Release 11
IE/Group Name MS Classmark 3 Presence M

563
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference OCTET STRING Semantics description Coded same way as the Mobile Station Classmark 3 IE defined in TS 24.008 [66].

9.2.1.146

Speech Version

The Speech Version IE identifies the speech version supported.

IE/Group Name Speech Version Presence M Range IE type and reference BIT STRING (4) Semantics description The coding of this IE is described in TS 24.008 [66].

9.2.1.147

Controlled Object Scope

Controlled Object Scope IE indicates the scope of objects which the control of information transfer shall be performed.
IE/Group Name RNC-ID Extended RNC-ID Multiple PLMN List UMTS Cell Information >C-ID Presence M O O O M Range bound maxnoofCells Range IE Type and Reference 9.2.1.50 9.2.1.50a 9.2.1.1 0..<maxnoofC ells> 9.2.1.6 Explanation Maximum number of cells that can be indicated in the corresponding IE. Semantics Description If the Extended RNC-ID IE is included, the RNC-ID IE shall be ignored. The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095

9.2.1.148

ANR Report Indication

ANR Report Indication IE contains information about neighbour cells detected by the ANR function in UE and sent to the initiating RNC (RNC1) over Uu.

3GPP

Release 11
IE/Group Name PLMN Identity Presence M Range

564
IE Type and Reference OCTET STRING (3)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description The registed PLMN of UE when the ANR result was logged. - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN Identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). The IE Contains UE INFORMATION RESPONSE defined in ref. TS 25.331 [16].

L3 Information

9.2.1.32

9.2.1.149

ANR Cell Information

The ANR Cell Information IE provides information about an UTRAN Cell.

IE/Group Name RNC-ID LAC RAC ANR FDD Cell Information ANR TDD Cell Information ANR TDD Cell Information LCR Extended RNC-ID Presence M O O O O O O OCTET STRING (2) OCTET STRING (1) 9.2.1.150 9.2.1.151 9.2.1.152 9.2.1.50a The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. Range IE Type and Reference 9.2.1.50 Semantics Description If the Extended RNC-ID IE is included in the ANR Cell Information IE, the RNC-ID IE shall be ignored. 0000 and FFFE not allowed

9.2.1.150

ANR FDD Cell Information

The ANR FDD Cell Information IE provides information for FDD cell that is neighbouring cell to the Base UTRAN cell in ANR neighbouring relation..

3GPP

Release 11
IE/Group Name Primary CPICH Power Tx Diversity Indicator STTD Support Indicator Closed Loop Mode1 Support Indicator Restriction State Indicator DPC Mode Change Support Indicator Cell Capability Container FDD SNA Information Frequency Band Indicator Max UE DTX Cycle ANR Multiple PLMN List Secondary Serving Cell List Dual Band Secondary Serving Cell List Cell Capability Container Extension FDD Presence O M O O O O O O O O O O O Range

565
IE Type and Reference 9.2.1.44 9.2.2.50 9.2.2.45 9.2.2.2 9.2.1.48C 9.2.2.56 9.2.2.D 9.2.1.52Ca 9.2.2.59 9.2.2.87 9.2.1.153 9.2.2.101 Secondary Serving Cell List 9.2.2.101 9.2.2.123

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

9.2.1.151

ANR TDD Cell Information

The ANR TDD Cell Information IE provides information for 3.84Mcps TDD or 7.68Mcps TDD cell that is neighbouring cell to the Base UTRAN cell in ANR neighbouring relation..
IE/Group Name Sync Case Time Slot For SCH SCH Time Slot SCTD Indicator DPCH Constant Value PCCPCH Power Restriction State Indicator Cell Capability Container TDD Cell Capability Container 7.68Mcps TDD SNA Information ANR Multiple PLMN List Presence M O O M O O O O O O O Range IE Type and Reference 9.2.1.54 Time Slot 9.2.1.56 9.2.1.51 9.2.1.78 9.2.1.23 9.2.1.43 9.2.1.48C 9.2.3.1a 9.2.3.31 9.2.1.52Ca 9.2.1.153 Semantics Description

9.2.1.152

ANR TDD Cell Information LCR

The ANR TDD Cell Information LCR IE provides information for 1.28Mcps TDD cell that is neighbouring cell to the Base UTRAN cell in ANR neighbouring relation..
IE/Group Name SCTD Indicator DPCH Constant Value PCCPCH Power Restriction State Indicator Cell Capability Container TDD LCR SNA Information ANR Multiple PLMN List Cell Capability Container Extension TDD LCR Presence M O O O O O O O Range IE Type and Reference 9.2.1.78 9.2.1.23 9.2.1.43 9.2.1.48C 9.2.3.1b 9.2.1.52Ca 9.2.1.153 9.2.3.80 Semantics Description

3GPP

Release 11

566

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.1.153

ANR Multiple PLMN List

This information element contains a list of PLMN identities, which identifies the broadcasted PLMN Identities in MOCN and GWCN shared network configurations. The common PLMN Identify (mandatory PLMN Identity that is broascasted in the MIB) is not included in the list.
IE/Group Name List of PLMNs >PLMN Identity M Presence Range 1 .. <maxNrOfBroadc astPLMNs> OCTET STRING (SIZE (3)) - digits 0 to 9, two digits per octet, - each digit encoded 0000 to 1001, - 1111 used as filler - bit 4 to 1 of octet n encoding digit 2n-1 - bit 8 to 5 of octet n encoding digit 2n -The PLMN identity consists of 3 digits from MCC followed by either -a filler plus 2 digits from MNC (in case of 2 digit MNC) or -3 digits from MNC (in case of a 3 digit MNC). Range bound maxNrOfBroadcastPLMNs Explanation Maximum number of additional PLMN identitys that can be broadcasted in a cell involved in a MOCN or GWCN Shared Network configuration. The value for maxNrOfBroadcastPLMNs is 5. IE type and reference Semantics description

9.2.1.154

Extended RNTI

The Extended RNTI identifies the UE in the RNC.

IE/Group Name Extended RNTI Presence Range IE Type and Reference INTEGER(1 048576..419 4303,) Semantics Description

9.2.1.155

Extended S-RNTI Group

The Extended S-RNTI Group identifies a group of UEs in the SRNC.

IE/Group Name Extended S-RNTI Extended S-RNTI bit mask index Presence M M Range IE Type and Reference 9.2.1.154 Enumerated(b1, b2,..b21,) Semantics Description

The Extended S-RNTI group is identified by all Extended S-RNTI values whose bits starting from the most significant bit down to, and including, the bit indicated by Extended S-RNTI bit mask index, are equal to the corresponding bits of the Extended S-RNTI in this IE. The bits of the Extended S-RNTI in this IE that are less significant than the bit position indicated by the Extended SRNTI bit mask index shall be ignored.

3GPP

Release 11

567

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2 FDD Specific Parameters

This subclause contains parameters that are specific to FDD.

9.2.2.a

ACK-NACK Repetition Factor

The ACK-NACK Repetition Factor IE indicates the consecutive repetition of the ACK and NACK.
IE/Group Name ACK-NACK Repetition Factor Presence Range IE type and reference INTEGER (1..,4,...) Semantics description Step: 1

9.2.2.b

ACK Power Offset

The ACK Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ ACK information and the associated DPCCH.
IE/Group Name ACK Power Offset Presence Range IE type and reference INTEGER (0..8,) Semantics description According to mapping in TS 25.213 [21] subclause 4.2.1.

9.2.2.A

Active Pattern Sequence Information

Defines the parameters for the compressed mode gap pattern sequence activation. For details see TS 25.331 [16].

3GPP

Release 11
IE/Group Name CM Configuration Change CFN Transmission Gap Pattern Sequence Status >TGPSI Identifier Presence M 0.. <maxTGP S> M Range

568
IE Type and Reference CFN 9.2.1.9

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description If the group is not present, none of the pattern sequences are activated. Establish a reference to the compressed mode pattern sequence. Up to <MaxTGPS> simultaneous compressed mode pattern sequences can be activated. The number of transmission gap patterns within the Transmission Gap Pattern Sequence. 0=Infinity. Connection Frame Number of the first frame of the first pattern 1 within the Transmission Gap Pattern Sequence. The HS-DSCH serving cells affected by the TGPS when activating frequency specific compressed mode. Max 4 in this 3GPP release. Criticality Assigned Criticality

INTEGER(1..< MaxTGPS>)

>TGPRC

INTEGER(0..5 11)

>TGCFN

CFN 9.2.1.9

>Affected HSDSCH serving cell List

0..<maxno ofHSDSC H>

EACH

reject

>>C-ID

9.2.1.6

Range bound maxTGPS maxnoofHSDSCH

Explanation Maximum number of active pattern sequences. Value 6. Maximum number of Primary Serving plus Secondary Serving HSDSCH cells for one UE

9.2.2.B

Adjustment Period

Adjustment Period IE defines the period to be used for power balancing.

IE/Group Name Adjustment Period Presence Range IE Type and Reference INTEGER (1 .. 256) Semantics Description Unit: Frames

9.2.2.C

Adjustment Ratio

Adjustment Ratio IE (Radj) defines the convergence rate used for the associated Adjustment Period.

3GPP

Release 11
IE/Group Name Adjustment Ratio Presence

569
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0 .. 100) Semantics Description The Adjustment Ratio is given with a granularity of 0.01 0 -> 0.00 1 -> 0.01 ... 100 -> 1.00

9.2.2.Ca

Bundling Mode Indicator

The Bundling Mode Indicator indicates whether the bundling shall be done or shall not be done for Iur.
IE/Group Name Bundling Mode Indicator Presence Range IE Type and Reference ENUMERATED ( Bundling, No bundling) Semantics Description The value Bundling is applicable only when E-TTI indicates 2ms.

9.2.2.D

Cell Capability Container FDD

The Cell Capability Container FDD indicates which functionalities a cell supports.

3GPP

Release 11
IE/Group Name Presence

570
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

3GPP

Release 11
Cell Capability Container FDD

571

3GPP TS 25.423 V11.2.0 (2012-06)

BIT STRING (32) Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit:Reserved. The second bit: Delayed Activation Support Indicator. The third bit: HS-DSCH Support Indicator. The fourth bit:Reserved. The fifth bit: F-DPCH Support Indicator. The sixth bit: E-DCH Support Indicator. The seventh bit: E-DCH TTI2ms Support Indicator. The eighth bit: E-DCH 2sf2and2sf4 and all inferior SFs Support Indicator. The ninth bit: E-DCH 2sf2 and all inferior SFs Support Indicator. The tenth bit: E-DCH 2sf4 and all inferior SFs Support Indicator. The eleventh bit: E-DCH sf4 and all inferior SFs Support Indicator. The twelveth bit: E-DCH sf8 and all inferior SFs Support Indicator. The thirteenth bit: E-DCH HARQ IR Combining Support Indicator. The fourteenth bit: E-DCH HARQ Chase Combining Support Indicator. The fifteenth bit: Continuous Packet Connectivity DTXDRX Support Indicator. The sixteenth bit: Continuous Packet Connectivity HSSCCH less Support Indicator. The seventeenth bit: MIMO Support Indicator. The eighteenth bit: SixteenQAM UL Support Indicator. The nineteenth bit: Flexible MAC-d PDU Size Support Indicator. The twentieth bit: F-DPCH Slot Format Support Indicator. The twentyfirst bit: SixtyfourQAM DL Support Indicator. The twentysecond bit: Flexible E-DCH MAC-d PDU Size Support Indicator. The twentythird bit: E-

3GPP

Release 11

572

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.E

Cell Portion ID

Cell Portion ID is the unique identifier for a cell portion within a cell. See TS 25.215 [11].
IE/Group Name Cell Portion ID Presence Range IE Type and Reference INTEGER (0..63,) Semantics Description

9.2.2.1

Chip Offset

The Chip Offset is defined as the radio timing offset inside a radio frame. The Chip Offset is used as offset for the DL DPCH relative to the Primary CPICH timing for the DL DPCH or for the F-DPCH.
IE/Group Name Chip Offset Presence Range IE Type and Reference INTEGER (0..38399) Semantics Description Unit: Chips

9.2.2.2

Closed Loop Mode1 Support Indicator

The Closed Loop Mode1 Support Indicator indicates whether the particular cell is capable to support Closed loop mode1 or not
IE/Group Name Closed Loop Mode1 Support Indicator Presence Range IE Type and Reference ENUMERAT ED(Closed loop mode1 Supported, Closed loop mode1 not supported). Semantics Description

9.2.2.3
Void.

Closed Loop Mode2 Support Indicator Closed Loop Timing Adjustment Mode

9.2.2.3A

Indicates when the phase/amplitude adjustment is performed in the DL in relation to the receipt of the UL feedback command in case of closed loop mode transmit diversity on DPCH.
IE/Group Name Closed Loop Timing Adjustment Mode Presence Range IE Type and Reference ENUMERAT ED(Offset1, Offset2,) Semantics Description According to TS 25.214 [10] subclause 7.1: Offset1 = slot(j+1)mod15 Offset2 = slot(j+2)mod15

9.2.2.4
Void

Compressed Mode Method DCH FDD Information

9.2.2.4A

The DCH FDD Information IE provides information for DCHs to be established.

3GPP

Release 11
IE/Group Name DCH FDD Information >Payload CRC Presence Indicator >UL FP Mode >ToAWS >ToAWE >DCH Specific Info >>DCH ID >>TrCH Source Statistics Descriptor >>Transport Format Set >>Transport Format Set >>BLER >>BLER >>Allocation/Retention Priority >>Frame Handling Priority >>QE-Selector >>DRAC control >>Guaranteed Rate Information >>Traffic Class >>Unidirectional DCH Indicator >TNL QoS Range bound maxnoofDCHs M M M M 1..<maxno ofDCHs> M M M M M M M M M M O M O O Presence Range 1..<maxno ofDCHs>

573
IE Type and Reference 9.2.1.42 9.2.1.67 9.2.1.58 9.2.1.57 9.2.1.16 9.2.1.65 9.2.1.64 9.2.1.64 9.2.1.4 9.2.1.4 9.2.1.1 9.2.1.29 9.2.1.46A 9.2.2.13 9.2.1.30M 9.2.1.58A 9.2.1.68B 9.2.1.56A

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality For the UL. For the DL. For the UL. For the DL. YES YES YES YES Assigned Criticality

ignore ignore reject ignore

Explanation Maximum number of DCHs for one UE.

9.2.2.4B

E-DCH FDD Information

The E-DCH FDD Information IE provides information for an E-DCH to be established.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flows Information HARQ Process Allocation For 2ms Scheduled Transmission Grant Presence M O Range

574
IE Type and Reference 9.2.2.4MC HARQ Process Allocation for 2ms TTI 9.2.2.4O 9.2.2.4MG 9.2.1.95 9.2.2.4MI 9.2.1.96 9.2.2.90 9.2.2.61A

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality If this IE is not included, scheduled transmission in all HARQ processes is allowed. Assigned Criticality

E-DCH Maximum Bitrate E-DCH Processing Overload Level E-DCH Reference Power Offset E-DCH Power Offset for Scheduling Info SixteenQAM UL Operation Indicator E-AGCH Table Choice

O O O O O CSixteenQA M UL Operation

YES YES If the SixteenQAM UL operation is not configured for this UE, Table 16B for EAGCH in TS 25.212 [9] shall be used. YES ignore reject ignore

Condition SixteenQAM UL Operation

Explanation The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to Activate.

9.2.2.4C

E-DCH FDD Information Response

The E-DCH FDD Information Response IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the DRNS.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information Response >E-DCH MAC-d Flow ID M Presence Range 1..<maxno ofEDCHM ACdFlows >

575
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.91

If only HARQ Process Allocation For 2ms Scheduled Transmissio n Grant IE and this IE (E-DCH MAC-d Flow ID) are present in the E-DCH FDD Information Response IE, the content of this IE shall be considered invalid

>Binding ID >Transport Layer Address >HARQ Process Allocation For 2ms NonScheduled Transmission Grant >Transport Bearer Not Setup Indicator HARQ Process Allocation For 2ms Scheduled Transmission Grant

O O O

9.2.1.3 9.2.1.62 HARQ Process Allocation for 2ms TTI 9.2.2.4O 9.2.2.4T HARQ Process Allocation for 2ms TTI 9.2.2.4O

O O

YES

ignore

Range bound maxnoofEDCHMACdFlows

Explanation Maximum number of E-DCH MAC-d flows.

9.2.2.4D

E-DCH FDD DL Control Channel Information

The E-DCH FDD DL Control Channel Information IE provides information for E-DCH specific DL Control Channels to be provided to UE via RRC signalling.

3GPP

Release 11
IE/Group Name E-AGCH And E-RGCH/EHICH FDD Scrambling Code Presence O Range

576
IE Type and Reference DL Scrambling Code 9.2.2.11

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Scrambling code on which E-AGCH, ERGCH and EHICH are transmitted. 0= Primary scrambling code of the cell 115 = Secondary scrambling code Criticality Assigned Criticality

E-AGCH Channelisation Code

Primary E-RNTI Secondary E-RNTI E-RGCH/E-HICH Channelisation Code

O O M

E-RGCH Signature Sequence E-HICH Signature Sequence Serving Grant Value

FDD DL Channelisat ion Code Number 9.2.2.14 E-RNTI 9.2.1.94 E-RNTI 9.2.1.94 FDD DL Channelisat ion Code Number 9.2.2.14 INTEGER (0..maxnoof SigSeqERG HICH-1) INTEGER (0..maxnoof SigSeqERG HICH-1) INTEGER (0..37,38)

Primary/Secondary Grant Selector

ENUMERA TED (Primary, Secondary)

(0..37) indicates EDCH serving grant index as defined in TS 25.321 [41]; index 38 means zero grant Indicates whether the Serving Grant Value is granted with a primary ERNTI or a secondary ERNTI Indicates whether the value of ERGCH and EHICH Channelisatio n Code is invalid

E-RGCH Release Indicator E-RGCH and E-HICH Channelisation Code Validity Indicator

O O

9.2.2.60 9.2.2.68

YES ignore

3GPP

Release 11
Default Serving Grant in DTX Cycle 2 O

577
INTEGER (0..37,38)

3GPP TS 25.423 V11.2.0 (2012-06)

Serving Grant value to be used in DTXCycle-2. (0..37) indicates EDCH serving grant index as defined in TS 25.425 [32]; index 38 means zero grant YES ignore

Range bound maxnoofSigSeqERGHICH

Explanation Maximum number Signature Sequences for ERGCH / E-HICH

9.2.2.4E

E-DCH RL Indication

Indicates whether a RL is an E-DCH RL.

IE/Group Name E-DCH RL Indication Presence Range IE Type and Reference ENUMERAT ED(E-DCH, non E-DCH) Semantics Description

9.2.2.4F

E-DCH FDD Information To Modify

The E-DCH FDD Information IE provides information for an E-DCH to be modified.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information >E-DCH MAC-d Flow ID >Allocation/Retention Priority >Transport Bearer Request Indicator >TNL QoS >Maximum Number of Retransmissions for EDCH >Traffic Class >E-DCH HARQ Power Offset FDD >E-DCH MAC-d Flow Multiplexing List > CHOICE E-DCH grant type >>E-DCH NonScheduled Transmission Grant >>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission M O M O O O O O O Presence Range 1..<maxno ofEDCHM ACdFlows >

578
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description See Note1 below. Criticality Assigned Criticality

9.2.1.91 9.2.1.1 9.2.1.61 9.2.1.56A 9.2.1.100 9.2.1.58A 9.2.2.4L 9.2.1.89

9.2.2.4N

If the Extended Maximum Number of Bits per MACe PDU for Nonscheduled Transmission IE is present, this IE shall be ignored. When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-I PDU.

>>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant

HARQ Process Allocation for 2ms TTI 9.2.2.4O

3GPP

Release 11
>>>Extended Maximum Number of Bits per MAC-e PDU for Nonscheduled Transmission O

579
9.2.2.4R

3GPP TS 25.423 V11.2.0 (2012-06)

When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-I PDU. YES reject

>>E-DCH Scheduled Transmission Grant >Bundling Mode Indicator >E-DCH Logical Channel To Add

NULL O O 9.2.2.Ca E-DCH Logical Channel Information 9.2.1.92 9.2.1.93 0..< maxnooflo gicalchan nels> M O 9.2.1.97 HARQ Process Allocation for 2ms TTI 9.2.2.4O 9.2.2.4MG 9.2.1.95 9.2.2.4MI 9.2.1.99 9.2.1.96 9.2.2.90 9.2.1.91A 0..<maxno ofEDCHR Ls> M CSixteenQA M UL Operation RL ID 9.2.1.49 9.2.2.61A

>E-DCH Logical Channel To Modify >E-DCH Logical Channel To Delete >>Logical Channel ID HARQ Process Allocation For 2ms Scheduled Transmission Grant E-DCH Maximum Bitrate E-DCH Processing Overload Level E-DCH Reference Power Offset MAC-e Reset Indicator E-DCH Power Offset for Scheduling Info SixteenQAM UL Operation Indicator E-DCH MAC-d PDU Size Format E-DCH DL Control Channel Grant Information >E-DCH RL ID E-AGCH Table Choice

O O O O O O O

YES YES YES GLOBAL ignore reject reject ignore

If sixteenQAM YES ignore UL operation is not used in the new configuration for this UE, Table 16B for E-AGCH in TS 25.212 [9] shall be used in the new configuration. Note 1: Even if no E-DCH MAC-d Flow Specific Information needs to be modified, one E-DCH MAC-d Flow Information shall be included, which only contains the E-DCH MAC-d Flow ID IE and the Transport BearerRequest Indicator IE set to Bearer not Requested.

3GPP

Release 11

580

3GPP TS 25.423 V11.2.0 (2012-06)

Condition SixteenQAM UL Operation

Explanation The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to Activate. Explanation Maximum number of E-DCH MAC-d flows. Maximum number of Logical Channels Maximum number of E-DCH RLs for one UE

Range bound maxnoofEDCHMACdFlows Maxnooflogicalchannels maxnoofEDCHRLs

9.2.2.4G

E-DCH Transport Format Combination Set Information (E-TFCS Information)

Whereas the related Transport Block sizes are standardised in TS 25.321 [41] this IE gives details on the referenced Transport Block Size Table, the E-DCH Minimum Set E-TFCI, the Reference E-TFCIs and configuration parameters used for the calculation of the gain factors ec and ed defined in TS 25.214 [10].

3GPP

Release 11
IE/Group Name E-TFCI Table Index Presence M Range

581
IE Type and Reference INTEGER (0..1,..., 2..7)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in TS 25.321 [41]. For the concept of EDCH Minimum Set of TFCs see TS 25.321 [41] and TS 25.331 [16]. Criticality Assigned Criticality

E-DCH Minimum Set ETFCI

INTEGER (0..127)

Reference E-TFCI Information >Reference E-TFCI >Reference E-TFCI Power Offset M M

1..<maxno ofRefETF CIs> INTEGER (0..127) 9.2.2.4P If the Extended Reference ETFCI Power Offset IE is present, this IE shall be ignored Indicates whether the value of EDCH Minimum Set E-TFCI is invalid True means that the EDPDCH power interpolation formula shall be applied, False means that the EDPDCH power extrapolation formula shall be applied for the computation of the gain factor ed according to TS 25.214 [10]

>Extended Reference ETFCI Power Offset E-DCH Minimum Set ETFCI Validity Indicator

O O

9.2.2.4Q 9.2.2.69

YES YES

reject reject

E-TFCI Boost Informatiion E-DPDCH Power Interpolation

O O

9.2.2.91 BOOLEAN

YES YES

reject reject

Range Bound maxnoofRefETFCIs

Explanation Maximum number of signalled reference E-TFCIs

3GPP

Release 11

582

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.4J

E-TTI

The E-TTI parameter indicates the Transmission Time Interval for E-DPCH operation.
IE/Group Name E-TTI Presence Range IE Type and Reference ENUMERAT ED (2ms, 10ms) Semantics Description

9.2.2.4K

E-DPCCH Power Offset

The E-DPCCH Power Offset is used to calculate the E-DPCCH gain factor ec as defined in TS 25.214 [10], whereas ec is related to the power difference between DPCCH and E-DPCCH.
IE/Group Name E-DPCCH Power Offset Presence Range IE Type and Reference INTEGER (0..8) Semantics Description According to mapping in TS 25.213 [21] subclause 4.2.1.3

9.2.2.4KA 9.2.2.4L

Void E-DCH HARQ Power Offset FDD

The E-DCH HARQ Power Offset FDD is used to calculate the unquantised gain factor for an E-TFC (ed,j,uq)as defined in TS 25.214 [10].
IE/Group Name E-DCH HARQ Power Offset FDD Presence Range IE Type and Reference INTEGER (0..6) Semantics Description According to mapping in TS 25.213 [21] subclause 4.2.1.3.

9.2.2.4M 9.2.2.4MA 9.2.2.4MB 9.2.2.4MC

Void Void Void E-DCH MAC-d Flows Information

The E-DCH MAC-d Flows Information IE is used for the establishment of E-DCH MAC-d flows.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information >E-DCH MAC-d Flow ID >Allocation/Retention Priority >TNL QoS >Payload CRC Presence Indicator >Maximum Number of Retransmissions for EDCH >Traffic Class >E-DCH HARQ Power Offset FDD >E-DCH MAC-d Flow Multiplexing List >CHOICE E-DCH grant type >>E-DCH NonScheduled Transmission Grant >>>Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission M O O M M M M O M Presence Range 1..<maxno ofEDCHM ACdFlows >

583
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.91 9.2.1.1 9.2.1.56A 9.2.1.42 9.2.1.100 9.2.1.58A 9.2.2.4L 9.2.1.89

9.2.2.4N

>>>HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant

HARQ Process Allocation for 2ms TTI 9.2.2.4O

If the Extended Maximum Number of Bits per MACe PDU for Nonscheduled Transmission IE is present, this IE shall be ignored. When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the maximum number of bits per MAC-I PDU. If this IE is not included, transmission in all HARQ processes is allowed.

3GPP

Release 11
>>>Extended Maximum Number of Bits per MAC-e PDU for Nonscheduled Transmission O

584
9.2.2.4R

3GPP TS 25.423 V11.2.0 (2012-06)

When Maximum MAC-d PDU Size Extended IE is configured for an E-DCH Logical Channel this IE indicates the extended maximum number of bits per MAC-I PDU. YES reject

>>E-DCH Scheduled Transmission Grant >Bundling Mode Indicator >E-DCH Logical Channel Information >TrCH Source Statistics Descriptor

NULL O M O 9.2.2.Ca 9.2.1.92 9.2.1.65 YES ignore

Range bound maxnoofEDCHMACdFlows

Explanation Maximum number of E-DCH MAC-d flows.

9.2.2.4MD 9.2.2.4ME 9.2.2.4MF 9.2.2.4MG

Void Void Void E-DCH Maximum Bitrate

The E-DCH Maximum Bitrate parameter indicates the Maximum Bitrate for an E-DCH.
IE/Group Name E-DCH Maximum Bitrate Presence Range IE Type and Reference INTEGER (0..5742, , 5743..11498) Semantics Description Bitrate on transport block level. Unit is kbits per second.

9.2.2.4MH 9.2.2.4MI

Void E-DCH Reference Power Offset

The E-DCH Reference Power Offset is used to estimate the E-DPDCH power from E-TFCI without decoding MAC-e PDUs.
IE/Group Name E-DCH Reference Power Offset Presence Range IE Type and Reference INTEGER (0..6) Semantics Description According to mapping in TS 25.213 [21] subclause 4.2.1.3.

9.2.2.4MJ 9.2.2.4N

Void Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission

The Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission indicates the maximum numbers of bits allowed to be included in a MAC-e (or MAC-i) PDU per E-DCH MAC-d flow configured for non- scheduled transmissions. If the range of the Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE is insufficient to represent the value to be sent to the DRNS, the Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE shall be used to represent the value to be sent to the DRNS, see section 9.2.2.4R.

3GPP

Release 11
IE/Group Name Maximum Number of Bits per MAC-e PDU for NonScheduled Transmission Presence Range

585

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference INTEGER (1..19982)

9.2.2.4O

HARQ Process Allocation For 2ms TTI

The HARQ Process Allocation for 2ms TTI indicates those HARQ processes that are allowed. MAC-d PDUs for a MAC-d flow are only allowed to be transmitted in those processes for which the bit is set to 1.
IE/Group Name HARQ Process Allocation For 2ms TTI Presence Range IE Type and Reference BIT STRING (8) Semantics Description The first Bit corresponds to HARQ process ID = 0, the second bit corresponds to HARQ process ID = 1, etc. The HARQ process ID for 2ms TTI is defined in TS 25.321 [41], chapter 11.8.1.3.

9.2.2.4P

Reference E-TFCI Power Offset

The Reference E-TFCI Power Offset is used to calculate the reference E-TFC gain factor ed,ref as defined in TS 25.214 [10]. If the range of the Reference E-TFCI Power Offset IE is insufficient to represent the value to be sent to the DRNS, the Extended Reference E-TFCI Power Offset IE shall be used to represent the value to be sent to the DRNS, see section 9.2.2.4Q.
IE/Group Name Reference E-TFCI Power Offset Presence Range IE Type and Reference INTEGER (0..29) Semantics Description According to mapping in TS 25.213 [21] subclause 4.2.1.3

9.2.2.4Q

Extended Reference E-TFCI Power Offset

The Extended Reference E-TFCI Power Offset IE shall be used if the range of the Reference E-TFCI Power Offset IE (see section 9.2.2.4P) is insufficient to represent the value of the Reference E-TFCI Power Offset to be sent to the DRNS.
IE/Group Name Extended Reference E-TFCI Power Offset Presence Range IE Type and Reference INTEGER (30..31, ) Semantics Description According to mapping in TS 25.213 [21] subclause 4.2.1.3

9.2.2.4R

Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission

The Extended Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE shall be used if the range of the Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission IE (see section 9.2.2.4N) is insufficient to represent the value of the Maximum Number of Bits per MAC-e (or MAC-i) PDU for Non-scheduled Transmission to be sent to the DRNS.
IE/Group Name Extended Maximum Number of Bits per MAC-e PDU for Nonscheduled Transmission Presence Range IE Type and Reference INTEGER (19983..22978,) Semantics Description

3GPP

Release 11

586

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.4S

Transport Bearer Not Requested Indicator

The Transport Bearer Not Requested Indicator parameter indicates that a transport bearer shall not be established or may not to be established for DCH or an E-DCH MAC-d flow.
IE/Group Name Transport Bearer Not Requested Indicator Presence Range IE Type and Reference ENUMERATED (Transport Bearer shall not be Established, Transport Bearer may not be Established) Semantics Description

9.2.2.4T

Transport Bearer Not Setup Indicator

The Transport Bearer Not Setup Indicator parameter indicates that a transport bearer will not be established for a DCH or an E-DCH MAC-d flow.
IE/Group Name Transport Bearer Not Setup Indicator Presence Range IE Type and Reference ENUMERATED (Transport Bearer Not Setup) Semantics Description

9.2.2.5
Void

D-Field Length Diversity Control Field

9.2.2.6
Void.

9.2.2.7
Void.

Diversity Indication Diversity Mode

9.2.2.8

Define the diversity mode to be applied.

IE/Group Name Diversity Mode Presence Range IE Type and Reference ENUMERAT ED(None, STTD, Closed loop mode 1, Not Used,) Semantics Description The Diversity Mode IE shall never be set to Not Used. If received it shall be rejected.

9.2.2.9

DL DPCH Slot Format

Indicates the slot format used in DPCH in DL, according to TS 25.211 [8].
IE/Group Name DL DPCH Slot Format Presence Range IE Type and Reference INTEGER (0..16,) Semantics Description

3GPP

Release 11

587

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.9A

DL DPCH Timing Adjustment

The DL DPCH Timing Adjustment indicates that a timing adjustment of the related radio link is required or that an Initial DL DPCH Timing Adjustment has been performed by the DRNS. It also indicates whether the timing adjustment consists of a timing advance or a timing delay with respect to the SFN timing. The adjustment always consists of 256 chips.
IE/Group Name DL DPCH Timing Adjustment Presence Range IE Type and Reference ENUMERAT ED(timing advance, timing delay) Semantics Description The size of the timing adjustment is 256 chips.

9.2.2.10
Void

DL Power

9.2.2.10A

DL Power Balancing Information

The DL Power Balancing Information IE provides information for power balancing to be activated in the relevant RL(s).
IE/Group Name Power Adjustment Type DL Reference Power DL Reference Power Information >RL ID >DL Reference Power Max Adjustment Step Adjustment Period Adjustment Ratio Presence M C-Common C-Individual M M CCommonOrIn dividual CCommonOrIn dividual CCommonOrIn dividual 1..<maxnoo fRLs> 9.2.1.49 DL power 9.2.1.21A 9.2.2.23 9.2.2.B 9.2.2.C Power on DPCH or on F-DPCH Range IE Type and Reference 9.2.2.28 DL power 9.2.1.21A Semantics Description Power on DPCH or on F-DPCH Criticality Assigned Criticality

Condition Common Individual CommonOrIndividual

Explanation The IE shall be present if the Power Adjustment Type IE is set to Common. The IE shall be present if the Power Adjustment Type IE is set to Individual. The IE shall be present if the Power Adjustment Type IE is set to Common or Individual. Explanation Maximum number of Radio Links for a UE.

Range Bound maxnoofRLs

9.2.2.10B

DL Power Balancing Activation Indicator

The DL Power Balancing Activation Indicator IE indicates that the power balancing is activated in the RL.

3GPP

Release 11
IE/Group Name DL Power Balancing Activation Indicator Presence

588
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERATED(DL Power Balancing Activated). Semantics Description

9.2.2.10C

DL Reference Power Information

The DL Reference Power Information IE provides reference power of the power balancing to be used in the relevant RL(s).
IE/Group Name Common DL Reference Power Individual DL Reference Power Information >RL ID >DL Reference Power O 0..<maxnoo fRLs> M M 9.2.1.49 DL power 9.2.1.21A Power on DPCH or on F-DPCH Presence Range IE Type and Reference DL power 9.2.1.21A Semantics Description Power on DPCH or on F-DPCH Criticality Assigned Criticality

Range bound maxnoofRLs

Explanation Maximum number of RLs for a UE.

9.2.2.10D

DL Power Balancing Updated Indicator

The DL Power Balancing Updated Indicator IE indicates that the power balancing related parameters is updated in the RL.
IE/Group Name DL Power Balancing Updated Indicator Presence Range IE Type and Reference ENUMERATED(DL Power Balancing Updated). Semantics Description

9.2.2.11

DL Scrambling Code

DL Scrambling code to be used by the RL. One cell may have multiple DL Scrambling codes available.
IE/Group Name DL Scrambling Code Presence Range IE Type and Reference INTEGER (0..15) Semantics Description 0= Primary scrambling code of the cell 115= Secondary scrambling code

9.2.2.12
Void

Downlink Frame Type DPC Mode

9.2.2.12A

The DPC Mode IE indicates the DPC mode to be applied TS 25.214 [10].

3GPP

Release 11
IE/Group Name DPC Mode Presence

589
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT TED (Mode0, Mode1, ) Semantics Description Mode0: The DRNS shall estimate the UE transmitted TPC command and update the DL power in every slot Mode1: The DRNS shall estimate the UE transmitted TPC command over three slots and shall update the DL power in every three slots

9.2.2.13

DRAC Control

The possibility to use DRAC control has been removed.

IE/Group Name DRAC Control Presence Range IE Type and Reference ENUMERAT ED (Not Used, NotRequested) Semantics Description The DRAC Control IE shall never be set to Not Used.

9.2.2.13A
Void.

DSCH FDD Information DSCH FDD Information Response

9.2.2.13B
Void.

9.2.2.13Bb
Void.

DSCH-RNTI FDD DCHs To Modify

9.2.2.13C

The FDD DCHs To Modify IE provides information for DCHs to be modified.

3GPP

Release 11
IE/Group Name FDD DCHs To Modify >UL FP Mode >ToAWS >ToAWE >Transport Bearer Request Indicator >DCH Specific Info >>DCH ID >>Transport Format Set >>Transport Format Set >>Allocation/Retention Priority >>Frame Handling Priority >>Not Used >>Guaranteed Rate Information >>Traffic Class >>Unidirectional DCH Indicator >TNL QoS Range bound maxnoofDCHs O O O M 1..<maxno ofDCHs> M O O O O O O O O O Presence Range 1..<maxno ofDCHs>

590
IE Type and Reference 9.2.1.67 9.2.1.58 9.2.1.57 9.2.1.61

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.16 9.2.1.64 9.2.1.64 9.2.1.1 9.2.1.29 NULL 9.2.1.30M 9.2.1.58A 9.2.1.68B 9.2.1.56A

For the UL. For the DL.

YES YES YES YES

ignore ignore reject ignore

Explanation Maximum number of DCHs for one UE.

9.2.2.13D
Void.

Enhanced DSCH PC

9.2.2.13E
Void.

Enhanced DSCH PC Counter Enhanced DSCH PC Indicator

9.2.2.13F
Void.

9.2.2.13G
Void.

Enhanced DSCH PC Wnd Enhanced DSCH Power Offset

9.2.2.13H
Void.

9.2.2.13I

Enhanced Primary CPICH Ec/No

Energy per PN chip divided by the total received power spectral density measured on the Primary CPICH by the UE.
IE/Group Name Enhanced Primary CPICH Ec/No Presence Range IE Type and Reference INTEGER(0. .49) Semantics Description According to the mapping of the Primary CPICH Ec/Io UE measurement defined in TS 25.133 [23] and TS 25.123 [24]

3GPP

Release 11

591

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.14

FDD DL Channelisation Code Number

The DL Channelisation Code Number indicates the DL Channelisation Code number for a specific DL physical channel.
IE/Group Name FDD DL Channelisation Code Number Presence Range IE Type and Reference INTEGER(0. . 511) Semantics Description According to the mapping in TS 25.213 [27]. The maximum value is equal to the DL spreading factor 1

9.2.2.14A

FDD DL Code Information

The FDD DL Code Information IE provides FDD DL Code information for all DPCHs or for the F-DPCH of one Radio Link.
IE/Group Name FDD DL Code Information >DL Scrambling Code >FDD DL Channelisation Code Number >Transmission Gap Pattern Sequence Scrambling Code Information M M O Presence Range 1.. <maxnoof DLCodes 9.2.2.11 9.2.2.14 9.2.2.47B IE Type and Reference Semantics Description Criticality Assigned Criticality

Range bound maxnoofDLCodes

Explanation Maximum number of DL Channelisation Codes for one UE.

9.2.2.15
Void.

FDD S-CCPCH Offset FDD TPC Downlink Step Size

9.2.2.16

This parameter indicates step size for the DL power adjustment.

IE/Group Name FDD TPC Downlink Step Size Presence Range IE Type and Reference ENUMERAT ED(0.5, 1, 1.5, 2,) Semantics Description

9.2.2.16A

First RLS Indicator

The First RLS Indicator IE indicates if a specific Radio Link and all Radio Links which are part of the same Radio Link Set, shall be considered as the first radio links established towards the UE or not.
IE/Group Name First RLS Indicator Presence Range IE Type and Reference ENUMERAT ED(first RLS, not first RLS) Semantics Description

3GPP

Release 11

592

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.17
Void.

Gap Position Mode Gap Period (TGP)

9.2.2.18
Void.

9.2.2.19
Void

Gap Starting Slot Number (SN) HS-DSCH FDD Information

9.2.2.19a

The HS-DSCH FDD Information IE is used for initial addition of HS-DSCH information to UE Context.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flows Information UE Capabilities Information >HS-DSCH Physical Layer Category >1.28 Mcps TDD uplink physical channel capability >Number of Supported Carriers Presence M 1 M O O Range

593
IE Type and Reference 9.2.1.30OA

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.30Oa 9.2.3.10D ENUMERATE D( One-one carrier, Onethree carrier, Three-three carrier, Onesix carrier, Tree-six carrier, Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, OneTwocarrier Contiguous, Two-Two carrier Contiguous) 9.2.1.30Oa 9.2.3.84 9.2.1.34Ab 9.2.2.24a 9.2.2.24c 9.2.2.a 9.2.2.24b 9.2.2.b 9.2.2.26a 9.2.2.19d 9.2.2.57 9.2.1.134 9.2.1.30OC Not to be used. Not to be used.

YES YES ignore reject

>Multi-carrier HS-DSCH Physical Layer Category >UE RF Band Capability LCR MAC-hs Reordering Buffer Size for RLC-UM CQI Feedback Cycle k CQI Repetition Factor ACK-NACK Repetition Factor CQI Power Offset ACK Power Offset NACK Power Offset HS-SCCH Power Offset HARQ Preamble Mode MIMO Activation Indicator HS-DSCH MAC-d PDU Size Format

O CNofSupport edCarriers M M CCQICyclek M M M M O O O O

Not to be used. Not to be used.

YES YES YES YES YES

ignore ignore

If not present, Indexed MAC-d PDU Size shall be used.

ignore reject reject

Sixtyfour QAM Usage Allowed Indicator

9.2.2.79A

YES

ignore

3GPP

Release 11
UE with enhanced HSSCCH support indicator O

594
NULL

3GPP TS 25.423 V11.2.0 (2012-06)

UE supports enhanced HSSCCH functionality: - UE supports different HSSCCH in consecutive TTIs and, - in HS-SCCHless operation mode the UE supports HSSCCH orders Shall be ignored in Radio Link Setup and Radio Link Addition procedures. YES ignore

Enhanced HS Serving CC Abort

ENUMERATE D (Abort Enhanced HS Serving CC, ) 9.2.2.103 9.2.2.105 9.2.2.106

YES

reject

UE Support Indicator Extension Power Offset For S-CPICH for MIMO Request Indicator Single Stream MIMO Activation Indicator Condition CQICyclek

O O O

YES YES YES

ignore ignore reject

Explanation The IE shall be present if the CQI Feedback Cycle k IE is set to

a value greater than 0.

9.2.2.19aa

HS-DSCH FDD Secondary Serving Information

The HS-DSCH FDD Secondary Serving Information IE is used for initial addition of Secondary Serving HS-DSCH information to UE Context and defines the cell specific parameters for the secondary serving HS-DSCH Radio Link.

3GPP

Release 11
IE/Group Name HS-SCCH Power Offset Sixtyfour QAM Usage Allowed Indicator MIMO Activation Indicator Single Stream MIMO Activation Indicator Diversity Mode Presence O O O O O Range

595
IE Type and Reference 9.2.2.19d 9.2.2.79A 9.2.1.119 9.2.2.106 9.2.2.8

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality YES YES If Diversity mode = Closed loop mode 1 the procedure shall be rejected. YES reject reject reject Assigned Criticality

Transmit Diversity Indicator Power Offset For S-CPICH for MIMO Request Indicator Ordinal Number Of Frequency

O O O

9.2.2.48 9.2.2.105 INTEGER (1..32,...) Value = "1" indicates 1st secondary serving HSDSCH cell, Value = "2" indicates 2nd secondary serving HSDSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the DRNS if the new configuration contains one secondary serving radio link.

YES YES YES

reject ignore reject

9.2.2.19b

HS-DSCH FDD Information Response

The HS-DSCH FDD Information Response IE provides information for HS-DSCH MAC-d flows that have been established or modified. It also provides additional HS-DSCH information determined within the DRNS.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flow Specific Information Response >HS-DSCH MAC-d Flow ID >Binding ID >Transport Layer Address >HS-DSCH Initial Capacity Allocation HS-SCCH Specific Information Response >Code Number HS-PDSCH And HSSCCH Scrambling Code Measurement Power Offset HARQ Memory Partitioning User Plane Congestion Fields Inclusion HARQ Preamble Mode Activation Indicator MIMO Information Response SixtyfourQAM DL Usage Indicator HS-DSCH TB Size Table Indicator Power Offset For SCPICH for MIMO Support of dynamic DTXDRX related HSSCCH order Presence Range 0..<max noofMA CdFlow s> M O O O 0..<max noofHS SCCHc odes> M O O O O O O O O O O

596
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.30O 9.2.1.3 9.2.1.62 9.2.1.30Na

INTEGER (0..127) DL Scrambling Code 9.2.2.11 9.2.2.24d 9.2.1.116 9.2.1.70C 9.2.2.58 9.2.2.78 9.2.2.79B 9.2.2.19G 9.2.2.104 9.2.2.129

YES YES YES YES YES YES YES ignore ignore Ignore Ignore ignore ignore ignore

Range bound maxnoofMACdFlows maxnoofHSSCCHcodes

Explanation Maximum number of MAC-d flows. Maximum number of HS-SCCH codes.

9.2.2.19ba

HS-DSCH FDD Secondary Serving Information Response

The HS-DSCH FDD Secondary Serving Information Response IE provides Secondary Serving HS-DSCH information determined within the DRNS.

3GPP

Release 11
IE/Group Name HS-SCCH Specific Secondary Serving Information Response >Code Number HS-PDSCH And HSSCCH Scrambling Code Measurement Power Offset SixtyfourQAM DL Usage Indicator HS-DSCH TB Size Table Indicator MIMO Information Response Power Offset For SCPICH for MIMO Presence Range 0..<maxn oofHSSC CHcodes > M O O O O O O

597
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

INTEGER (0..127) DL Scrambling Code 9.2.2.11 9.2.2.24d 9.2.2.79B 9.2.2.19G 9.2.2.78 9.2.2.104

YES YES ignore ignore

Range bound maxnoofHSSCCHcodes

Explanation Maximum number of HS-SCCH codes.

9.2.2.19bb

HS-DSCH FDD Secondary Serving Information To Modify

The HS-DSCH FDD Secondary Serving Information To Modify IE is used for modification of cell specific Secondary Serving HS-DSCH information in a UE Context.

3GPP

Release 11
IE/Group Name HS-SCCH Power Offset HS-SCCH Code Change Grant Sixtyfour QAM Usage Allowed Indicator MIMO Mode Indicator Single Stream MIMO Mode Indicator Diversity Mode Presence O O O O O O Range

598
IE Type and Reference 9.2.2.19d 9.2.1.30S 9.2.2.79A 9.2.1.135 9.2.2.107 9.2.2.8

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality YES YES If Diversity mode = Closed loop mode 1 the procedure shall be rejected. YES reject reject reject Assigned Criticality

Transmit Diversity Indicator Non Cell Specific Tx Diversity

CDiversityM ode O

9.2.2.48 ENUMERAT ED (Tx Diversity, ...) Value = Tx Diversity: Diversity Mode and Transmit Diversity Indicator shall be non cell specific. Value = "1" indicates 1st secondary serving HSDSCH cell, Value = "2" indicates 2nd secondary serving HSDSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the DRNS if the new configuration contains one secondary serving radio link.

YES YES

reject reject

Power Offset For S-CPICH for MIMO Request Indicator Ordinal Number Of Frequency

O O

9.2.2.105 INTEGER (1..32,...)

YES YES

ignore reject

Condition DiversityMode

Explanation The IE shall be present if Diversity Mode IE is present and not set to None.

9.2.2.19bc

HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised

The HS-DSCH FDD Secondary Serving Information To Modify Unsynchronised IE is used for modification of Secondary Serving HS-DSCH information in a UE Context with the Unsynchronised Radio Link Reconfiguration procedure.

3GPP

Release 11
IE/Group Name HS-SCCH Power Offset Sixtyfour QAM Usage Allowed Indicator MIMO Mode Indicator Single Stream MIMO Mode Indicator Power Offset For SCPICH for MIMO Request Indicator Ordinal Number Of Frequency Presence O O O O O O Range

599
IE Type and Reference 9.2.2.19d 9.2.2.79A 9.2.1.135 9.2.2.107 9.2.2.105 INTEGER (1..32,...)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality YES YES YES Value = "1" indicates 1st secondary serving HSDSCH cell, Value = "2" indicates 2nd secondary serving HSDSCH cell etc. TS 25.214 [10]. The IE shall be ignored by the DRNS if the new configuration contains one secondary serving radio link. YES reject reject ignore reject Assigned Criticality

9.2.2.19c

HS-DSCH FDD Update Information

The HS-DSCH FDD Update Information IE provides information for HS-DSCH to be updated. At least one IE shall be presented.
IE/Group name HS-SCCH Code Change Indicator CQI Feedback Cycle k CQI Repetition Factor ACK-NACK Repetition Factor CQI Power Offset ACK Power Offset NACK Power Offset HS-PDSCH Code Change Indicator Presence O O O O O O O O Range IE Type and Reference 9.2.1.30R 9.2.2.24a 9.2.2.24c 9.2.2.a 9.2.2.24b 9.2.2.b 9.2.2.26a 9.2.1.30V Semantic Description Criticality YES Assigned Criticality

ignore

9.2.2.19ca

HS-DSCH FDD Secondary Serving Update Information

The HS-DSCH FDD Secondary Serving Update Information IE provides information for HS-DSCH to be updated. At least one IE shall be presented.
IE/Group name HS-SCCH Code Change Indicator HS-PDSCH Code Change Indicator Presence O O Range IE Type and Reference 9.2.1.30R 9.2.1.30V Semantic Description

This IE shall never be included. If received it shall be ignored.

3GPP

Release 11

600

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.19C

HS-DSCH configured indicator

The HS-DSCH Configured Indicator IE indicates the configuration of HS-DSCH for the UE. The HS-DSCH Configured Indicator IE shall be used for the configuration of the E-DPDCH IQ branch mapping (TS 25.213 [21]).
IE/Group Name HS-DSCH Configured Indicator Presence Range IE type and reference ENUMERATED (HSDSCH configured, HS-DSCH not configured) Semantics description Indicator of the HS-DSCH configuration for configuration of the E-DPDCHs IQ branch mapping (TS 25.213 [21]).

9.2.2.19d

HS-SCCH Power Offset

The HS-SCCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the HS-SCCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name HS-SCCH Power Offset Presence Range IE type and reference INTEGER (0..255) Semantics description Step 0.25 dB, range -32+31.75 dB

9.2.2.19e

E-DCH FDD Update Information

The E-DCH FDD Update Information IE provides information for E-DCH to be updated. At least one IE shall be present.
IE/Group Name E-DCH MAC-d Flow Specific Update Information >E-DCH MAC-d Flow ID >HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant HARQ Process Allocation For 2ms Scheduled Transmission Grant E-DCH DL Control Channel Change Information >E-DCH RL ID M O Presence Range 0..<maxn oofEDCH MACdFlo ws> 9.2.1.91 HARQ Process Allocation for 2ms TTI 9.2.2.4O HARQ Process Allocation for 2ms TTI 9.2.2.4O 0..<maxn oofEDCH RLs> M RL ID 9.2.1.49 IE Type and Reference Semantics Description Criticality Assigned Criticality

GLOBAL

ignore

Range bound maxnoofEDCHMACdFlows maxnoofEDCHRLs

Explanation Maximum number of E-DCH MAC-d flows. Maximum number of E-DCH RLs for one UE

9.2.2.19f

HS-DSCH Serving Cell Change Information

The HS-DSCH Serving Cell Change Information IE contains information which is used in HS-DSCH Serving Cell change.

3GPP

Release 11
IE/Group Name HS-PDSCH RL ID HS-DSCH Information Presence M O Range

601
IE Type and Reference RL ID 9.2.1.49 HS-DSCH FDD Information 9.2.2.19a 9.2.2.74 9.2.2.72

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

Continuous Packet Connectivity HS-SCCH less Information Continuous Packet Connectivity DTX-DRX Information

O O

YES YES

reject reject

9.2.2.19g

HS-DSCH Serving Cell Change Information Response

The HS-DSCH Serving Cell Change Information Response IE contains information which is used in HS-DSCH Serving Cell change.
IE/Group Name CHOICE Serving Cell Change >Successful >>HS-DSCH FDD Information Response >>HS-DSCH-RNTI >>Continuous Packet Connectivity HS-SCCH less Information Response >Unsuccessful >>Cause Presence Range IE Type and Reference Semantics Description Criticality M M O 9.2.2.19b 9.2.1.30P 9.2.2.75 YES Ignore Assigned Criticality

9.2.1.5

9.2.2.19ga

HS-DSCH Secondary Serving Cell Change Information Response

The HS-DSCH Secondary Serving Cell Change Information Response IE contains information which is used in HSDSCH Secondary Serving Cell change.
IE/Group Name CHOICE Secondary Serving Cell Change >Successful >>HS-DSCH FDD Secondary Serving Information Response >>HS-DSCH-RNTI >Unsuccessful >>Cause Presence Range IE Type and Reference Semantics Description

M M M

9.2.2.19ba 9.2.1.30P 9.2.1.5

9.2.2.19G

HS-DSCH TB Size Table Indicator

The HS-DSCH TB Size Table Indicator IE is used to indicate that octet aligned table (TS 25.321 [41]) shall be used.
IE/Group Name HS-DSCH TB Size Table Indicator Presence Range IE Type and Reference ENUMERATED (octet aligned) Semantics Description

3GPP

Release 11

602

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.19h

E-DCH Serving Cell Change Information Response

The E-DCH Serving Cell Change Information Response IE contains information which is used in E-DCH Serving Cell change.
IE/Group Name CHOICE Serving Cell Change >Successful >>RL Information Response >>>RL ID >>>E-DCH FDD DL Control Channel Information >Unsuccessful >>Cause Presence Range IE Type and Reference Semantics Description

0..<maxno ofRLs> M M 9.2.1.49 9.2.2.4D

9.2.1.5 Explanation Maximum number of RLs for one UE

Range bound maxnoofRLs

9.2.2.20
Void.

IB_SG_POS IB_SG_REP

9.2.2.21
Void.

9.2.2.21a

Inner Loop DL PC Status

The Inner Loop DL PC Status IE indicates whether inner loop DL control shall be active or inactive for all radio links for the UE Context.
IE/Group Name Inner Loop DL PC Status Presence Range IE Type and Reference ENUMERAT ED(Active, Inactive) Semantics Description

9.2.2.21b

Initial DL DPCH Timing Adjustment Allowed

The Initial DL DPCH Timing Adjustment Allowed IE indicates that the DRNS is allowed to perform a timing adjustment (either a timing advance or a timing delay with respect to the SFN timing) when establishing a radio link.
IE/Group Name Initial DL DPCH Timing Adjustment Allowed Presence Range IE Type and Reference ENUMERATED ( initial DL DPCH Timing Adjustment Allowed) Semantics Description

9.2.2.21A

Limited Power Increase

The parameter is used for a more efficient use of the inner loop DL power control for non real time data. If the limited power increase is used, DRNS shall use the limited power increase algorithm as specified in TS 25.214 [10], subclause 5.2.

3GPP

Release 11
IE/Group Name Limited Power Increase Presence

603
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(Used, Not used , ) Semantics Description

9.2.2.21B

IPDL FDD Parameters

The IPDL FDD Parameters IE provides the information for the IPDL Configuration applied in FDD mode.
IE/Group name IP spacing FDD Presence M Range IE Type and Reference ENUMERAT ED(5,7,10,1 5,20,30,40,5 0,) ENUMERAT ED(5,10,) INTEGER(0. .9) INTEGER(0. .63) 9.2.1.4B Semantics Description See TS 25.214 [10]

IP length IP offset Seed Burst mode parameters

M M M O

See TS 25.214 [10] See TS 25.214 [10] See TS 25.214 [10]

9.2.2.21C
Void.

Length of TFCI2

9.2.2.21D 9.2.2.21E 9.2.2.21F 9.2.2.22

Void.

Void Void Void Max Adjustment Period Max Adjustment Step

9.2.2.23

Defines the maximum allowed value for the change of DL power level during a certain number of slots that can be utilised by the downlink power balancing algorithm. Max Adjustment Step IE defines a time period, in terms of number of slots, in which the accumulated power adjustments shall be maximum 1 dB. This value does not include the DL inner loop PC adjustment.
IE/Group Name Max Adjustment Step Presence Range IE Type and Reference INTEGER (1..10) Semantics Description Slots

9.2.2.24

Max Number of UL DPDCHs

Maximum number of uplink DPDCHs during the connection. Needed by the rate matching algorithm.
IE/Group Name Max Number of UL DPDCHs Presence Range IE Type and Reference INTEGER (1..6) Semantics Description

9.2.2.24a

CQI Feedback Cycle k

The CQI Feedback Cycle k IE provides the duration of the CQI feedback cycle.

3GPP

Release 11
IE/Group Name CQI Feedback Cycle k Presence

604
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED (0, 2, 4, 8, 10, 20, 40, 80, 160,, 16, 32, 64) Semantics Description Unit ms The allowed values for this IE depend on the configured CQI Repetition Factor and the HS-DSCH configuration as defined in TS 25.214 [10].

9.2.2.24b

CQI Power Offset

The CQI Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slots carrying CQI information and the associated DPCCH.
IE/Group Name CQI Power Offset Presence Range IE type and reference INTEGER (0..8,) Semantics description According to mapping in TS 25.213 [21] subclause 4.2.1.

9.2.2.24c

CQI Repetition Factor

The CQI Repetition Factor IE indicates the consecutive repetition of the CQI.
IE/Group Name CQI Repetition Factor Presence Range IE type and reference INTEGER (1..,4,...) Semantics description Step: 1

9.2.2.24d

Measurement Power Offset

The Measurement Power Offset IE is used as defined in TS 25.214 [10] subclause 6A.2.
IE/Group Name Measurement Power Offset Presence Range IE Type and Reference INTEGER (-12..26) Semantics Description Unit: dB Range: -6..13dB Step: 0.5dB

9.2.2.24e

Maximum Set of E-DPDCHs

The Maximum Set of E-DPDCHs as defined in TS 25.212 [9]. Needed by rate matching algorithm.
IE/Group Name Maximum Set of E-DPDCHs Presence Range IE Type and Reference ENUMERATED (vN256, vN128, vN64, vN32, vN16, vN8, vN4, v2xN4, v2xN2, v2xN2plus2xN4,, v2xM2plus2xM4) Semantics Description

9.2.2.24f 9.2.2.24A
Void

Void Min DL Channelisation Code Length

3GPP

Release 11

605

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.25

Min UL Channelisation Code Length

Minimum UL channelisation code length (spreading factor) of a DPDCH during the connection. Needed by rate matching algorithm.
IE/Group Name Min UL Channelisation Code Length Presence Range IE Type and Reference ENUMERAT ED(4,8,16, 32,64,128, 256) Semantics Description

9.2.2.26

Multiplexing Position

Multiplexing Position specifies whether fixed or flexible positions of transport channels shall be used in the physical channel.
IE/Group Name Multiplexing Position Presence Range IE Type and Reference ENUMERAT ED(Fixed, Flexible) Semantics Description

9.2.2.26a

NACK Power Offset

The NACK Power Offset IE indicates Power offset used in the UL between the HS-DPCCH slot carrying HARQ NACK information and the associated DPCCH.
IE/Group Name NACK Power Offset Presence Range IE type and reference INTEGER (0..8,) Semantics description According to mapping in TS 25.213 [21] subclause 4.2.1.

9.2.2.26A

Number of DL Channelisation Codes

This parameter notifies DRNS of the number of DL channelisation codes required for the Radio Link(s).
IE/Group Name Number of DL Channelisation Codes Presence Range IE Type and Reference INTEGER (1..8) Semantics Description

9.2.2.27
Void

Pattern Duration (PD) PC Preamble

9.2.2.27a

Indicates DPDCH power control preamble length see TS 25.105 [7].

IE/Group Name PCP Preamble Presence Range IE Type and Reference INTEGER (0..7,) Semantics Description In number of frames.

9.2.2.27A
Void.

PDSCH Code Mapping

3GPP

Release 11

606

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.27B

Phase Reference Update Indicator

The Phase Reference Update Indicator IE indicates that the phase reference for the radio link needs to be changed.
IE/Group Name Phase Reference Update indicator Presence Range IE Type and Reference ENUMERATED (Phase Reference needs to be changed) Semantics Description

9.2.2.28

Power Adjustment Type

Defines the characteristic of the power adjustment.

IE/Group Name Power Adjustment Type Presence Range IE Type and Reference ENUMERAT ED(None, Common, Individual) Semantics Description

9.2.2.29
Void.

Power Control Mode (PCM)

9.2.2.30

Power Offset

This IE defines a power offset relative to the Downlink transmission power of a DPCH in case the UE Context is configured to use DPCH in the downlink.
IE/Group Name Power Offset Presence Range IE Type and Reference INTEGER (0..24) Semantics Description Unit dB, Step 0.25 dB, Range 0..6 dB

9.2.2.31
Void.

Power Resume Mode (PRM) Preamble Signatures

9.2.2.31A
Void.

9.2.2.32

Primary CPICH Ec/No

Energy per chip divided by the power density per band measured on the Primary CPICH by the terminal.
IE/Group Name Primary CPICH Ec/No Presence Range IE Type and Reference INTEGER (-30..+30) Semantics Description Unit dB, step 1 dB The value range is typically within the range of -24 dB to 0 dB according to the CPICH Ec/Io UE measurement defined in TS 25.133 [23].

3GPP

Release 11

607

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.32A

Primary CPICH Usage For Channel Estimation

The Primary CPICH Usage For Channel Estimation IE indicates whether the Primary CPICH may be used for channel estimation or not.
IE/Group Name Primary CPICH Usage For Channel Estimation Presence Range IE Type and Reference ENUMERATED (Primary CPICH may be used, Primary CPICH shall not be used) Semantics Description

9.2.2.33

Propagation Delay (PD)

Propagation delay is the one-way propagation delay of the radio signal from the UE to the Node B. If the range of the Propagation Delay IE is insufficient to represent the measured value, it shall be set to its maximum value, and the Extended Propagation Delay IE (see 9.2.2.33a) shall be used to represent the propagation delay value.
IE/Group Name Propagation Delay Presence Range IE Type and Reference INTEGER (0..255) Semantics Description Unit: Chips. Step: 3 chips. 0=0 chips, 1=3 chips,

9.2.2.33a

Extended Propagation Delay

The Extended Propagation delay is the one-way propagation delay of the radio signal from the MS to the Node B. It shall be used if the Propagation Delay IE (see 9.2.2.33) cannot represent the measured value, due to range limitation.
IE/Group Name Extended Propagation Delay Presence Range IE Type and Reference INTEGER (255..1023) Semantics Description Continuation of intervals as defined in TS 25.133 [23]. Unit: chip Range: 765..3069 chips Step: 3 chips

9.2.2.33A
Void.

PRACH Minimum Spreading Factor QE-Selector

9.2.2.34
Void.

9.2.2.34a
Void.

Qth Parameter RACH Sub Channel Numbers

9.2.2.34A
Void.

9.2.2.35

RL Set ID

The RL Set ID uniquely identifies one RL Set within a UE Context.

3GPP

Release 11
IE/Group Name RL Set ID Presence

608
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..31) Semantics Description

9.2.2.35a

RL Specific E-DCH Information

The RL Specific E-DCH Information IE provides RL specific E-DCH Information.

IE/Group Name RL Specific E-DCH Information >E-DCH MAC-d Flow ID >Binding ID M O Presence Range 1..<maxnoof EDCHMACd Flows> 9.2.1.91 9.2.1.3 Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP. IE Type and Reference Semantics Description Criticality Assigned Criticality

>Transport Layer Address >Transport Bearer Not Requested Indicator E-AGCH Power Offset E-RGCH Power Offset E-HICH Power Offset Range Bound maxnoofEDCHMACdFlows

9.2.1.62

O O O O

9.2.2.4S 9.2.2.61 9.2.2.62 9.2.2.63 Explanation Maximum number of E-DCH MAC-d flows

YES

ignore

9.2.2.35A

Received Total Wide Band Power

The parameter indicates the Received total wide band power in a cell, see TS 25.215 [11].
IE/Group Name Received Total Wide Band Power Presence Range IE Type and Reference INTEGER(0. .621) Semantics Description According to mapping in TS 25.133 [23].

9.2.2.36
Void.

S-Field Length

9.2.2.36A 9.2.2.37
Void.

Void Scrambling Code Change Scrambling Code Number

9.2.2.37A
Void.

9.2.2.37B
Void.

Secondary CCPCH Info

3GPP

Release 11

609

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.38
Void.

Secondary CCPCH Slot Format Secondary CPICH Information

9.2.2.38A

The Secondary CPICH Information IE provides the information on the Secondary CPICH when it can be used for channel estimation.
IE/Group Name DL Scrambling Code FDD DL Channelisation Code Number Presence M M Range IE Type and Reference 9.2.2.11 9.2.2.14 Semantics Description

9.2.2.38B

Secondary CPICH Information Change

The Secondary CPICH Information Change IE indicates modification of information of the Secondary CPICH for channel estimation.
IE/Group Name CHOICE Secondary CPICH Information Change >New Secondary CPICH >>Secondary CPICH Information >Secondary CPICH Shall Not Be Used Presence M M 9.2.2.38A NULL Range IE Type and Reference Semantics Description

9.2.2.38C

Serving E-DCH RL

The Serving E-DCH RL IE indicates whether the Serving E-DCH RL is in the DRNS.
IE/Group Name CHOICE Serving E-DCH RL >Serving E-DCH RL in this DRNS >>Serving E-DCH RL ID >Serving E-DCH RL not in this DRNS Presence M M RL ID 9.2.1.49 NULL Range IE Type and Reference Semantics Description

9.2.2.39
Void

Slot Number (SN) Split Type

9.2.2.39a
Void.

9.2.2.39A

SRB Delay

Indicates the number of frames after the PC Preamble period during which transmission of data on some RRC Signalling Bearers shall be prohibited by UE in accordance with TS 25.331 [16].
IE/Group Name SRB Delay Presence Range IE Type and Reference INTEGER(0. .7,) Semantics Description In number of frames.

3GPP

Release 11

610

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.40
Void.

SSDT Cell Identity SSDT Cell Identity for EDSCHPC

9.2.2.40A
Void.

9.2.2.41
Void.

SSDT Cell Identity Length SSDT Indication

9.2.2.42
Void.

9.2.2.43

SSDT Support Indicator

The possibility to use SSDT Support Indicator has been removed.

IE/Group Name SSDT Support Indicator Presence Range IE Type and Reference ENUMERAT ED(Not Used, SSDT not supported). Semantics Description The SSDT Support Indicator IE shall never be set to Not Used.

9.2.2.44
Void.

STTD Indicator

9.2.2.45

STTD Support Indicator

The STTD Support Indicator indicates whether the STTD can be applied to DL DPCH and F-DPCH in the cell or not.
IE/Group Name STTD Support Indicator Presence Range IE Type and Reference ENUMERAT ED(STTD Supported, STTD not Supported). Semantics Description

9.2.2.45A

Synchronisation Indicator

The Synchronisation Indicator IE indicates that Timing Maintained Synchronisation shall be used at start of Radio Link, see also [10].
IE/Group Name Synchronisation Indicator Presence Range IE Type and Reference ENUMERATED (Timing Maintained Synchronisation,) Semantics Description

9.2.2.46

TFCI Signalling Mode

This parameter indicates has only one value with any meaning.

3GPP

Release 11
IE/Group Name TFCI Signalling Mode Presence

611
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(Normal, Not Used) Semantics Description The value Not Used shall not be used by the SRNC. The procedure shall be rejected by the DRNC if the value Not Used is received.

9.2.2.46A
Void.

TFCI PC Support Indicator Transmission Gap Distance (TGD)

9.2.2.47
Void.

9.2.2.47A

Transmission Gap Pattern Sequence Information

Defines the parameters for the compressed mode gap pattern sequence. For details see TS 25.331 [16].

3GPP

Release 11
IE/Group Name Transmission Gap Pattern Sequence Information >TGPSI Identifier Presence

612
Range 1..<maxTGPS> M

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER(1..< MaxTGPS>) Semantics Description

>TGSN

INTEGER(0..1 4)

>TGL1

INTEGER(1..1 4) INTEGER(1..1 4) INTEGER (0, 15.. 269)

>TGL2

>TGD

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. 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. Transmission gap distance indicates the number of slots between the 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 0 (0 =undefined). The duration of transmission gap pattern 1 in frames. This IE shall never be included in the IE group. If received it shall be ignored. Defines whether only DL, only UL, or combined UL/DL compressed mode is used. Method for generating downlink compressed mode gap The Downlink Compressed Mode Method IE shall never be set to not Used. Method for generating uplink compressed mode gap. Defines if frame type A or B shall be used in downlink compressed mode. Delta in SIR target value to be set in the DRNS 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) Step 0.1 dB, Range 0-3dB

>TGPL1 >Not-to-be-used-1 >UL/DL mode

M O M

INTEGER(1.. 144,) INTEGER(1.. 144,) ENUMERATE D(UL only, DL only, UL/DL) ENUMERATE D(not Used, SF/2, higher layer scheduling,) ENUMERATE D(SF/2, higher layer scheduling,) ENUMERATE D(A, B,...) INTEGER(0..3 0)

>Downlink Compressed Mode Method

C-DL

>Uplink Compressed Mode Method >Downlink Frame Type >DeltaSIR1

C-UL

M M

3GPP

Release 11
>DeltaSIRafter1 M

613

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER (0..30) Delta in SIR target value to be set in the DRNS one frame after the frame containing the start of the first transmission gap in the transmission gap pattern,. Step 0.1 dB, Range 0-3dB Delta in SIR target value to be set in the DRNS 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. Step 0.1 dB, Range 0-3dB Delta in SIR target value to be set in the DRNS one frame after the frame containing the start of the second transmission gap in the transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1. Step 0.1 dB, Range 0-3dB

>DeltaSIR2

INTEGER (0..30)

>DeltaSIRafter2

INTEGER (0..30)

Condition UL DL

Explanation The IE shall be present if the UL/DL mode IE is set to UL only or UL/DL. The IE shall be present if the UL/DL mode IE is set to DL only or UL/DL. Explanation Maximum number of transmission gap pattern sequences.

Range bound maxTGPS

9.2.2.47B

Transmission Gap Pattern Sequence Scrambling Code Information

This IE indicates whether or not the alternative scrambling code will be used in the DRNS for the Downlink compressed mode method SF/2 in the Transmission Gap Pattern Sequence. For details see TS 25.331 [16].
IE/Group Name Transmission Gap Pattern Sequence Scrambling Code Information Presence Range IE Type and Reference ENUMERAT ED(code change, no code change) Semantics Description Code change = alternative scrambling code will be used.

9.2.2.48

Transmit Diversity Indicator

The Transmit Diversity Indicator indicates whether Transmit Diversity shall be active or not.
IE/Group Name Transmit Diversity Indicator Presence Range IE Type and Reference ENUMERAT ED(active, inactive) Semantics Description

9.2.2.49
Void

Transmit Gap Length (TGL)

3GPP

Release 11

614

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.50
-

Tx Diversity Indicator

The Tx Diversity Indicator indicates if the following conditions are satisfied: Primary CPICH is broadcast from two antennas STTD is applied to Primary CCPCH TSTD is applied to Primary SCH and Secondary SCH
IE/Group Name Tx Diversity Indicator Presence Range IE Type and Reference ENUMERAT ED(true, false). Semantics Description

9.2.2.50A
Void.

UE Support Of Dedicated Pilots For Channel Estimation UE Support Of Dedicated Pilots For Channel Estimation Of HS-DSCH

9.2.2.50B
Void.

9.2.2.51
Void

UL/DL Compressed Mode Selection UL DPCCH Slot Format

9.2.2.52

Indicates the slot format used in DPCCH in UL, according to TS 25.211 [8].
IE/Group Name UL DPCCH Slot Format Presence Range IE Type and Reference INTEGER (0..5,) Semantics Description Value 5 shall not be used. If value 5 is received, the procedure shall be rejected.

9.2.2.52A

UL DPDCH Indicator for E-DCH operation

This IE indicated whether the requested configuration actually contain an UL DPDCH.

IE/Group Name UL DPDCH Indicator for EDCH operation Presence Range IE Type and Reference ENUMERAT ED (ULDPDCH present, ULDPDCH not present) Semantics Description

9.2.2.53

UL Scrambling Code

The UL Scrambling Code is the scrambling code used by UE. Every UE has its specific UL Scrambling Code.
IE/Group Name UL Scrambling Code Number UL Scrambling Code Length Presence M M Range IE Type and Reference INTEGER (0.. 224-1) ENUMERAT ED(Short, Long) Semantics Description

3GPP

Release 11

615

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.54
Void

Uplink Delta SIR Uplink Delta SIR After

9.2.2.55
Void

9.2.2.56

DPC Mode Change Support Indicator

The DPC Mode Change Support Indicator IE indicates that the particular cell is capable to support DPC mode change.
IE/Group Name DPC Mode Change Support Indicator Presence Range IE Type and Reference ENUMERATTE D (DPC Mode Change Supported) Semantics Description

9.2.2.57

HARQ Preamble Mode

The HARQ Preamble Mode IE is used as described as described in TS 25.214 [10].

IE/Group Name HARQ Preamble Mode Presence Range IE Type and Reference ENUMERATED(mod e0, mode1) Semantics Description mode0 means HARQ Preamble Mode =0 mode1 means HARQ Preamble Mode =1

9.2.2.58

HARQ Preamble Mode Activation Indicator

The HARQ Preamble Activation Indicator indicates if the configured HARQ Preamble Mode has been activated in the DRNS.
IE/Group Name HARQ Preamble Mode Activation Indicator Presence Range IE Type and Reference ENUMERAT ED(HARQ Preamble Mode Activated). Semantics Description

9.2.2.59

Frequency Band Indicator

The Frequency Band Indicator IE indicates frequency band as defined in TS 25.104 [6].

3GPP

Release 11
IE/Group Name Frequency Band Indicator Presence

616
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference ENUMERAT ED (Band I, Band II, Band III, Band IV, Band V, Band VI, Band VII, Band VIII, Band IX, Band X, Band XI, Band XII, Band XIII, Band XIV, Band XV, Band XVI, Band XVII, Band XVIII, Band XIX, Band XX, Band XXI, Band XXII, , Reserved23, Reserved24, Band XXV, Band XXVI) Semantics description

9.2.2.60

E-RGCH Release Indicator

Indicates that the E-RGCH is released..

IE/Group Name E-RGCH Release Indicator Presence Range IE Type and Reference ENUMERATED (ERGCH released) Semantics Description

9.2.2.61

E-AGCH Power Offset

The E-AGCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the E-AGCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name E-AGCH Power Offset Presence Range IE Type and Reference INTEGER (0..255, ) Semantics Description Unit: dB Range: -32 .. +31.75 dB Step: 0.25 dB

9.2.2.61A

E-AGCH Table Choice

The E-AGCH Table Choice IE indicates the choice of the E-AGCH table in TS 25.212 [9].

3GPP

Release 11
IE/Group Name E-AGCH Table Choice Presence M Range

617

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Table 16B indicates the Table 16B: Mapping of Absolute Grant Value in [9] and Table 16B-1 indicates the Table 16B.1: Alternative Mapping of Absolute Grant Value in TS 25.212 [9].

IE Type and Reference ENUMERATED (Table 16B, Table 16B-1, )

9.2.2.62

E-RGCH Power Offset

The E-RGCH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the E-RGCH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name E-RGCH Power Offset Presence Range IE Type and Reference INTEGER (0..255, ) Semantics Description Unit: dB Range: -32 .. +31.75 dB Step: 0.25 dB

9.2.2.63

E-HICH Power Offset

The E-HICH Power Offset IE indicates the Power offset relative to the pilot bits on the DL DPCCH except when FDPCH is configured. When F-DPCH is configured, the E-HICH Power Offset IE indicates the Power offset relative to the power of transmitted TPC bits on the F-DPCH.
IE/Group Name E-HICH Power Offset Presence Range IE Type and Reference INTEGER (0..255, ) Semantics Description Unit: dB Range: -32 .. +31.75 dB Step: 0.25 dB

9.2.2.64

E-RGCH 2-Index-Step Threshold

The E-RGCH 2-index-step-threshold IE is used to determine the Serving Grant.

IE/Group Name E-RGCH 2-Index-Step Threshold Presence Range IE Type and Reference INTEGER Semantics Description Refers to an index in the SGTable (see TS 25.321 [41]).

(0..37)

9.2.2.65

E-RGCH 3-Index-Step Threshold

The E-RGCH 3-index-step-threshold IE is used to determine the Serving Grant.

IE/Group Name E-RGCH 3-Index-Step Threshold Presence Range IE Type and Reference INTEGER Semantics Description Refers to an index in the SGTable (see TS 25.321 [41]).

(0..37)

9.2.2.66

HARQ Info for E-DCH

The HARQ Info for E-DCH is used to indicate the use of redundancy version (RV) for the EDCH HARQ transmissions.

3GPP

Release 11
IE/Group name HARQ Info for E-DCH Presence Range

618

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics description rv0 indicates that the UE will only use E_DCH RV index 0. rvtable indicates that the UE will use an RSN based RV index as specified in TS 25.212 [9]

IE Type and Reference ENUMERATED (rv0, rvtable)

9.2.2.67

DCH Indicator For E-DCH-HSDPA Operation

The DCH Indicator For E-DCH-HSDPA Operation parameter indicates whether DCH Information IE should be ignored in the message in which the DCH Indicator For E-DCH-HSDPA Operation IE is included.

IE/Group Name DCH Indicator For E-DCHHSDPA Operation

Presence

Range

IE Type and Reference ENUMERATED (DCH not present)

Semantics Description

9.2.2.68

E-RGCH and E-HICH Channelisation Code Validity Indicator

The E-RGCH and E-HICH Channelisation Code Validity Indicator parameter indicates if the E-RGCH/E-HICH Channelisation Code IE shall be ignored in the E-DCH FDD DL Control Channel Information IE in which the ERGCH and E-HICH Channelisation Code Validity Indicator IE was included.

IE/Group Name E-RGCH and E-HICH Channelisation Code Validity Indicator

Presence

Range

IE Type and Reference ENUMERATED (E-RGCH and EHICH Channelisation Code not valid)

Semantics Description

9.2.2.69

E-DCH Minimum Set E-TFCI Validity Indicator

The E-DCH Minimum Set E-TFCI Validity Indicator parameter indicates if the E-DCH Minimum Set E-TFCI IE shall be ignored in the E-DCH Transport Format Combination Set Information IE in which the E-DCH Minimum Set ETFCI Validity Indicator IE was included.
IE/Group Name E-DCH Minimum Set E-TFCI Validity Indicator Presence Range IE Type and Reference ENUMERATED (E-DCH Minimum Set E-TFCI not valid) Semantics Description

9.2.2.70

Fast Reconfiguration Mode

The Fast Reconfiguration Mode IE is used to notify the DRNS that the SRNC would like to use the activation time when the UE is detected on the new configuration as the timing for the reconfiguration.
IE/Group Name Fast Reconfiguration Mode Presence Range IE Type and Reference ENUMERATED ( Fast) Semantics Description

3GPP

Release 11

619

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.71

Fast Reconfiguration Permission

The Fast Reconfiguration Permission IE is used to indicate to the SRNC that the DRNS can apply the activation time when the UE is detected on the new configuration for this reconfiguration.
IE/Group Name Fast Reconfiguration Permission Presence Range IE Type and Reference ENUMERATED ( Allowed) Semantics Description

9.2.2.72

Continuous Packet Connectivity DTX-DRX Information

The Continuous Packet Connectivity DTX-DRX Information IE defines the parameters used for Continuos Packet Connectivity DTX-DRX operation (see TS 25.214 [10]).
IE/Group Name UE DTX DRX Offset Enabling Delay DTX Information >CHOICE E-DCH TTI Length >>2ms >>>UE DTX Cycle 1 >>>UE DTX Cycle 2 >>>MAC DTX Cycle >>10ms >>>UE DTX Cycle 1 >>>UE DTX Cycle 2 >>>MAC DTX Cycle >Inactivity Threshold for UE DTX Cycle 2 >UE DTX Long Preamble >MAC Inactivity Threshold Presence M M 1 M M M M M M M M M M ENUMERATED (1, 4, 5, 8, 10, 16, 20) ENUMERATED (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160) ENUMERATED (1, 4, 5, 8, 10, 16, 20) ENUMERATED (1, 5, 10, 20) ENUMERATED (5, 10, 20, 40, 80, 160) ENUMERATED (5, 10, 20) ENUMERATED (1, 4, 8, 16, 32, 64, 128, 256) ENUMERATED (2,4,15) ENUMERATED (1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) ENUMERATED (1, 2, 5) ENUMERATED (1, 2, 5) Units of subframes Units of subframes Units of subframes Units of subframes Units of subframes Units of subframes Units of E-DCH TTIs Units of slots Units of E-DCH TTIs Range IE Type and Reference INTEGER (0..159) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) Semantics Description Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI Units of radio frames

>CQI DTX Timer

Units of subframes

>UE DPCCH burst1 >UE DPCCH burst2 DRX Information >UE DRX Cycle >Inactivity Threshold for UE DRX Cycle >Inactivity Threshold for UE Grant Monitoring

M M

Units of subframes Units of subframes

0..1
M M M ENUMERATED (4, 5, 8, 10, 16, 20) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, Units of subframes Units of subframes Units of E-DCH TTIs

3GPP

Release 11

620
128, 256) BOOLEAN

3GPP TS 25.423 V11.2.0 (2012-06)

>UE DRX Grant Monitoring

True: DRX Grant Monitoring shall be applied. False: DRX Grant Monitoring shall not be applied.

9.2.2.73

Continuous Packet Connectivity DTX-DRX Information To Modify

The Continuous Packet Connectivity DTX-DRX Information To Modify IE is used for modification of Continuous Packet Connectivity DTX-DRX information in a UE Context. The Continuous Packet Connectivity DTX-DRX Information To Modify IE shall include at least one of the following IE.
IE/Group Name UE DTX DRX Offset Enabling Delay CHOICE DTX Information To Modify >Modify >>CHOICE E-DCH TTI Length >>>2ms >>>>UE DTX Cycle 1 >>>>UE DTX Cycle 2 >>>>MAC DTX Cycle >>>10ms >>>>UE DTX Cycle 1 >>>>UE DTX Cycle 2 >>>>MAC DTX Cycle >>Inactivity Threshold for UE DTX Cycle 2 >>UE DTX Long Preamble >>MAC Inactivity Threshold >>CQI DTX Timer Presence O O O O O O O O O O O O O ENUMERATED (1, 4, 5, 8, 10, 16, 20) ENUMERATED (4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160) ENUMERATED (1, 4, 5, 8, 10, 16, 20) ENUMERATED (1, 5, 10, 20) ENUMERATED (5, 10, 20, 40, 80, 160) ENUMERATED (5, 10, 20) ENUMERATED (1, 4, 8, 16, 32, 64, 128, 256) ENUMERATED (2,4,15) ENUMERATED (1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, Infinity) ENUMERATED (1, 2, 5) ENUMERATED (1, 2, 5) Units of subframes Units of subframes Units of subframes Units of subframes Units of subframes Units of subframes Units of E-DCH TTIs Units of slots Units of E-DCH TTIs Range IE Type and Reference INTEGER (0..159) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) Semantics Description Units of subframes. Offset of the UE DTX and DRX cycles at the given TTI Units of radio frames

Units of subframes

>>UE DPCCH burst1 >>UE DPCCH burst2 >Deactivate CHOICE DRX Information To Modify >Modify >>UE DRX Cycle >>Inactivity Threshold for UE DRX Cycle

O O O

Units of subframes Units of subframes

O O

ENUMERATED (4, 5, 8, 10, 16, 20) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512)

Units of subframes Units of subframes

3GPP

Release 11
>>Inactivity Threshold for UE Grant Monitoring >>UE DRX Grant Monitoring >Deactivate O O

621

3GPP TS 25.423 V11.2.0 (2012-06)

Units of E-DCH TTIs True = DRX Grant Monitoring shall be applied. False = DRX Grant Monitoring shall not be applied.

ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256) BOOLEAN

NULL

9.2.2.74

Continuous Packet Connectivity HS-SCCH less Information

The Continuous Packet Connectivity HS-SCCH less Information IE defines the parameters used for Continuos Packet Connectivity HS-SCCH less operation (see TS 25.214 [10]).
IE/Group Name Transport Block Size List Presence Range IE Type and Reference Semantics Description

1..<maxn oofHSDSCHTBS sHSSCCHless >

M M INTEGER (1..maxnoofHS-DSC HTBSs) BOOLEAN

>Transport Block Size Index >HS-PDSCH Second Code Support

True = The second HSPDSCH code shall also be used False = The second HSPDSCH code shall not be used

Range Bound maxnoofHS-DSCHTBSsHS-SCCHless maxnoofHS-DSCHTBSs

Explanation Maximum number of HS-DSCH Transport Block Sizes used for HSSCCH-less operation Maximum number of HS-DSCH Transport Block Sizes

9.2.2.75

Continuous Packet Connectivity HS-SCCH less Information Response

The Continuous Packet Connectivity HS-SCCH less Information Response IE provides information for HS-SCCH less operation determined within the Node B (see TS 25.214 [10]).
IE Type and Semantics Description Reference HS-PDSCH First Code Index M INTEGER Index of first HS-PDSCH code (1..maxHS-PDSCHC odeNrComp-1) HS-PDSCH Second Code O INTEGER Index of second HS-PDSCH Index (1..maxHS-PDSCHC code. See Note 1. odeNrComp-1) NOTE 1: The HS-PDSCH second code index value is the value of IE HS-PDSCH First Code Index incremented by 1. Range Bound maxHS-PDSCHCodeNrComp Explanation Maximum number of codes at the defined spreading factor, within the complete code tree IE/Group Name Presence Range

9.2.2.75A

Continuous Packet Connectivity HS-SCCH Less Deactivate Indicator

The Continuous Packet Connectivity HS-SCCH Less Deactivate Indicator IE is used to deactive HS-SCCH less operation.

3GPP

Release 11
IE/Group Name Continuous Packet Connectivity HS-SCCH Less Deactivate Indicator Presence M Range

622

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference NULL

9.2.2.76
Void

MIMO Activation Indicator MIMO Mode Indicator

9.2.2.77
Void

9.2.2.78

MIMO Information Response

Presence M M INTEGER (0..255) NULL M ENUMERATED (1/2, 2/3, , 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 1/1, ) Range IE Type and Reference Semantics Description

IE/Group Name CHOICE Pilot Configuration >Primary and Secondary CPICH >>MIMO S-CPICH Channelisation Code >Normal and Diversity Primary CPICH MIMO N/M Ratio

9.2.2.79
Void.

SixtyfourQAM DL Support Indicator Sixtyfour QAM Usage Allowed Indicator

9.2.2.79A

The Sixtyfour QAM Usage Allowed Indicator IE indicates whether the Node B is allowed to use 64 QAM modulation for HS-DSCH transmission or not.
IE/Group Name Sixtyfour QAM Usage Allowed Indicator Presence M Range IE Type and Reference ENUMERATED (Allowed, NotAllowed) Semantics Description

9.2.2.79B

SixtyfourQAM DL Usage Indicator

The SixtyfourQAM DL Usage Indicator IE indicates if the Node B is using 64 QAM modulation for the HS-DSCH transmission, or if the Node B is not using 64 QAM modulation.
IE/Group Name SixtyfourQAM DL Usage Indicator Presence Range IE Type and Reference ENUMERATED (SixtyfourQAM DL Used, SixtyfourQAM DL Not Used) Semantics Description

9.2.2.80
Void.

Enhanced FACH Support Indicator

3GPP

Release 11

623

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.81
Void.

Enhanced PCH Support Indicator Priority Queue Information for Enhanced FACH/PCH

9.2.2.82
Void.

9.2.2.83
Void.

SixteenQAM UL Information SixteenQAM UL Information To Modify

9.2.2.84
Void.

9.2.2.85

F-DPCH Slot Format

The F-DPCH Slot Format IE defines the F-DPCH slot format for the TPC bits, as defined in TS 25.211 [8].
IE/Group Name F-DPCH Slot Format Presence Range IE Type and Reference INTEGER (0..9) Semantics Description

9.2.2.86

F-DPCH Slot Format Support Request

Presence Range IE Type and Reference NULL Semantics Description

IE/Group Name F-DPCH Slot Format Support Request

9.2.2.87

Max UE DTX Cycle

The Max UE DTX Cycle IE defines the maximum UE DTX cycle supported by the Node B for Continuous Packet Connectivity DTX-DRX operation.
IE/Group Name Max UE DTX Cycle Presence M Range IE Type and Reference ENUMERATED (v5, v10, v20, v40, v64, v80, v128, v160,) Semantics Description Units of subframes

9.2.2.88
Void.

Enhanced PCH Capability MAC-ehs Reset Timer

9.2.2.89
Void.

9.2.2.90

SixteenQAM UL Operation Indicator

Presence O Range IE Type and Reference ENUMERATED (Activate, Deactivate) Semantics Description

IE/Group Name SixteenQAM UL Operation Indicator

3GPP

Release 11

624

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.91

E-TFCI Boost Information

Presence M C-ETFCIboost 127 Range IE Type and Reference INTEGER (0..127, ) INTEGER (0..6,) Semantics Description E-TFCI threshold beyond which boosting of E-DPCCH is enabled

IE/Group Name E-TFCI BetaEC Boost UL Delta T2TP

Total E-DPDCH power across all codes to the combined power of DPCCH and E-DPCCH

Condition E-TFCIboost127

Explanation The IE shall be present if the E-TFCI BetaEC Boost IE value is not set o 127.

9.2.2.92

Common E-DCH Support Indicator

This IE indicates the Common E-DCH Support.

IE/Group Name Common E-DCH Support Indicator Presence Range IE Type and Reference NULL Semantics Description

9.2.2.93

Common E-DCH MAC-d Flow Specific Information

The Common E-DCH MAC-d Flow Specific Information IE provides information associated to Common E-DCH MACd Flow used for Common E-DCH.
IE/Group Name Common E-DCH MAC-d Flow Specific Information >Common E-DCH MAC-d Flow ID >Maximum Number Of Retransmissions For E-DCH >E-DCH HARQ Power Offset FDD >E-DCH MAC-d Flow Multiplexing List >Common E-DCH Logical Channel information >>Logical Channel ID >>Maximum MAC-d PDU Size Extended M M M O M M M 1..<maxno oflogicalch annels> 9.2.1.97 MAC PDU Size Extended 9.2.1.34D Explanation Maximum number of E-DCH MAC-d Flows Maximum number of logical channels Presence Range 1..<maxno ofEDCHM ACdFlows > IE Type and Reference Semantics Description

E-DCH MAC-d flow

9.2.1.91 9.2.1.100 9.2.2.4L 9.2.1.89

Range bound maxnoofEDCHMACdFlows maxnooflogicalchannels

9.2.2.94

Counting Information

The Counting Information IE provides counting result for MBMS service for each cell.

3GPP

Release 11
IE/Group Name Counting Information >C-ID >Counting Result M M Presence Range 1..<maxno ofFDDneig hbours>

625

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

9.2.1.6 INTEGER (0..63)

The number of Ues listen to the MBMS Service. If the number of the UE is more than 63, this IE set to 63.

Range bound maxnoofFDDneighbours

Explanation Maximum number of neighbouring FDD cell for one cell.

9.2.2.95

Transmission Mode Information

The Transmission Mode Information IE provides transmission mode for MBMS service for each cell.
IE/Group Name Counting Information >C-ID >Transmission Mode Range bound maxnoofFDDneighbours M M Presence Range 1..<maxno ofFDDneig hbours> 9.2.1.6 9.2.1.81 Explanation Maximum number of neighbouring FDD cell for one cell. IE Type and Reference Semantics Description

9.2.2.96

MBMS Neighbouring Cell Information

The parameter contains information for the MBMS p-t-m radio bearer configuration procedure as defined in TS 25.331 [16].
IE/Group Name MBMS Neighbouring Cell Information >MBMS Concatenated Service List Presence Range IE Type and Reference Semantics Description

1..<maxlen gthMBMSc oncatservlis ts > M O 9.2.1.80 9.2.1.32

TMGI shall be uniquely defined by a reference to this index from the MBMS short transmission identity IE (TS 25.331 [16]) in the L3 Information IE. The IE Contains MBMS COMMON P-T-M RB INFORMATION defined in TS 25.331 [16]. The IE Contains MBMS CURRENT CELL P-TM RB INFORMATION defined in TS 25.331 [16].

>>TMGI >L3 Information

>L3 Information

9.2.1.32

Range bound maxlengthMBMSconcatservlists

Explanation Maximum length of the concatenated service lists contained in MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages defined in TS 25.331 [16]

3GPP

Release 11

626

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.97

RLC Sequence Number

This parameter indicates the RLC Sequence Number.

IE/Group Name RLC Sequence Number Presence Range IE Type and Reference INTEGER (0..127) Semantics Description

9.2.2.98

Time Stamp

This parameter indicates the Time Stamp used for Inter-RNC MBMS synchronisation.
IE/Group Name Time Stamp Presence Range IE Type and Reference INTEGER (0..9999) Semantics Description Units: 10ms

9.2.2.99

HS-DSCH Preconfiguration Info

The HS-DSCH Preconfiguration Info IE provides information of the target cell preconfiguration in the DRNS as defined in TS 25.331 [16].

3GPP

Release 11
IE/Group Name Sets of HS-SCCH Codes Presence Range 1 <maxnoo fHSDSC H>

627
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Index 1 refers to the serving HS-DSCH cell Index 2 <maxnoofHSDSCH> refer to secondary serving HSDSCH cells in the order as listed in 9.2.2.100 HSDSCH Preconfiguration Setup. Max index is 4 in this 3GPP release. Criticality Assigned Criticality

>HS-SCCH Preconfigured Codes >>Code Number >HS-DSCHRNTI >HS-PDSCH And HS-SCCH Scrambling Code >SixtyfourQAM DL Support Indicator >SixtyfourQAM DL Usage Indicator >HS-DSCH TB Size Table Indicator >MIMO Information Response >Power Offset For S-CPICH for MIMO M M M

1..<maxn oofHSSC CHcodes > INTEGER (0..127) 9.2.1.31J DL Scramblin g Code 9.2.2.11 9.2.1.123 9.2.2.79B 9.2.2.19G 9.2.2.78 9.2.2.104 Applicable for multicarrier mode of operation. Applicable for multicarrier mode of operation. The "Power Offset For SCPICH for MIMO" in the index 1 of "Sets of HSSCCH Codes" shall be ignored.

O O O O O

YES YES ignore ignore

>Measurement Power Offset HARQ Memory Partitioning E-DCH FDD DL Control Channel Information HARQ Preamble Mode Activation Indicator MIMO Information Response

O M O O O

9.2.2.24d 9.2.1.116 9.2.2.4D 9.2.2.58 9.2.2.78 Only applicable for MIMO in singe carrier mode of operation. Shall be ignored in multicarrier mode of operation. For the primary UL frequency in Dual-cell EDCH mode of operation.

YES

ignore

Continuous Packet Connectivity HSSCCH less Information Response

9.2.2.75

3GPP

Release 11
Power Offset For SCPICH for MIMO O 9.2.2.104

628

3GPP TS 25.423 V11.2.0 (2012-06)

For the serving HS-DSCH cell in both the single carrier mode and multicarrier mode of operation. For E-DCH on multiple frequencies in this DRNS. E-DCH on Secondary uplink frequency max 1 in this 3GPP release. Index 1 correspond to the secondary serving HSDSCH cells with index 2 in the IE Sets of HSSCCH Codes. The list is in the order as listed in 9.2.2.100 HS-DSCH Preconfiguration Setup. For the secondary UL frequency In Dual-cell EDCH mode of operation. YES ignore

Additional E-DCH Preconfiguration Information

0..<maxn oofEDCH -1>

EACH

ignore

>E-DCH FDD DL Control Channel Information Support of dynamic DTXDRX related HS-SCCH order

M O

9.2.2.4D 9.2.2.129

YES ignore

Range bound maxnoofHSSCCHcodes maxnoofHSDSCH maxnoofEDCH-1

Explanation Maximum number of HS-SCCH codes Maximum number of Primary Serving plus Secondary Serving HSDSCH cells for one UE Maximum number of uplink frequencies -1 for E-DCH for one UE

9.2.2.100

HS-DSCH Preconfiguration Setup

The HS-DSCH Preconfiguration Setup IE indicates that the DRNS shall preconfigure set(s) of HS-SCCH codes and may contain a list of secondary serving HS-DSCH cells to be preconfigured for Enhanced Service Cell Change. The Cell Change procedure for Dual Cell operation is described in TS 25.308 [63]

3GPP

Release 11
IE/Group Name MAC-hs/ehs reset scheme Prese nce M Range

629
IE Type and Reference ENUMERAT ED (Always, Inter NodeB Change)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description MAC-hs/ehs reset handling at enhanced HS serving cell change: Always means always reset Inter NodeB Change means Only reset at inter Node B cell change Criticality Assigned Criticality

HS-DSCH Physical Layer Category MAC-hs Reordering Buffer Size for RLC-UM Secondary Cells

M M 0..<maxn oofHSDS CH-1>

9.2.1.30Oa 9.2.1.34Ab Preconfigured secondary serving HS-DSCH cell. maxnoofHSDSCH-1 is max 3 in this 3GPP release. C-ID of the preconfigured secondary serving HS-DSCH cell For the secondary serving HS-DSCH cell For the secondary serving HS-DSCH cell For the secondary serving HS-DSCH cell The secondary serving HS-DSCH cell shall be preconfigured with EDCH. For the secondary serving HS-DSCH cell For the primary serving HS-DSCH cell

>Secondary C-ID

9.2.1.9

>Num Secondary HSSCCH Codes >Sixtyfour QAM Usage Allowed Indicator >MIMO Activation Indicator >E-DCH Indicator

O O O

INTEGER (1..maxnoof HSSCCHcod es) 9.2.2.79A 9.2.1.134 NULL

YES YES ignore ignore

>Power Offset For SCPICH for MIMO Request Indicator Num Primary HS-SCCH Codes HARQ Preamble Mode MIMO Activation Indicator

O O

9.2.2.105 INTEGER (1.. maxnoofHSS CCHcodes) 9.2.1.134 9.2.1.134

YES

ignore

O O

HS-DSCH MAC-d PDU Size Format Sixtyfour QAM Usage Allowed Indicator UE with enhanced HSSCCH support indicator

9.2.1.30OC

O O

9.2.2.79A NULL

In multicarrier mode of operation the IE is for the serving HSDSCH cell If not present, Indexed MAC-d PDU Size shall be assumed. For the serving HSDSCH cell UE supports enhanced HS-SCCH functionality: - UE supports different HS-SCCH in consecutive TTIs and, - in HS-SCCH-less operation mode the UE supports HSSCCH orders

3GPP

Release 11
Continuous Packet Connectivity HS-SCCH less Information UE Support Indicator Extension Power Offset For SCPICH for MIMO Request Indicator O O O

630
9.2.2.74 9.2.2.103 9.2.2.105

3GPP TS 25.423 V11.2.0 (2012-06)

YES For the serving HSDSCH cell in both the single carrier mode and multicarrier mode of operation. YES ignore ignore

Range bound maxnoofHSDSCH-1 maxnoofHSSCCHcodes

Explanation Maximum number of Secondary Serving HS-DSCH cells for one UE Maximum number of HS-SCCH codes

9.2.2.101

Secondary Serving Cell List

This Secondary Serving Cell List IE identifies the possible secondary serving HS-DSCH cells for a Multi Cell/DualBand capable cell that is able to serve as a serving HS-DSCH cell.
IE/Group Name Possible Secondary Serving Cell List >Possible Secondary Serving Cell >Multicell E-DCH Restriction M O Presence Range 1..<maxnoof HSDSCH-1> C-ID 9.2.1.9 BOOLEAN IE Type and Reference Semantics Description For secondary serving HS-DSCH cell. TRUE means restricted FALSE or not included means no restrictions

Criticality
YES

Assigned Criticality

ignore

Range bound maxnoofHSDSCH-1

Explanation Maximum number of Secondary Serving HS-DSCH cells for one UE. See NOTE below. NOTE: In this case, maxnoofHSDSCH-1 represents the maximum number of possible secondary serving cells for a Multi Cell/Dual-Band capable cell.

9.2.2.102

Minimum Reduced E-DPDCH Gain Factor

The minimum gain factor (ed,k,reduced,min) defined in TS 25.214 [10].

IE/Group Name Minimum Reduced E-DPDCH Gain Factor Presence Range IE Type and Reference ENUMERATED (8/15, 11/15, 15/15, 21/15, 30/15, 42/15, 60/15, 84/15, ...) Semantics Description

9.2.2.103

UE Support Indicator Extension

The UE Support Indicator Extension IE is used to indicate the support level in the UE for optional HSDPA functions to the DRNS.

3GPP

Release 11
IE/Group Name UE support indicator extension Presence Range

631

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Each bit indicates whether the UE supports a particular HSDPA function or not. The value 1 of a bit indicates that the corresponding functionality is supported in the UE and value 0 indicates that the corresponding functionality is not supported in the UE. Each bit is defined as follows: the first bit: Different HS-SCCH In Consecutive TTIs Support Indicator, the second bit: HS-SCCH orders in HS-SCCH-less Operation Support Indicator, the third bit: RRC Rel-9 (onwards) handling of DL secondary HS-DSCH (de)activation state Support Indicator, the fourth bit: UE DTXDRX related HS-SCCH orders uniform behavior indicator. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

IE Type and Reference BIT STRING (32)

9.2.2.104

Power Offset For S-CPICH for MIMO

The Power Offset For S-CPICH for MIMO IE indicates the the relative transmit power of the S-CPICH compared to the primary CPICH transmit power, when S-CPICH is used as a phase reference for a second transmit antenna in MIMO mode TS 25.214 [10].
IE/Group Name Power Offset For S-CPICH for MIMO Presence Range IE Type and Reference INTEGER(-6 .. 0) Semantics Description Offset in dB

9.2.2.105

Power Offset For S-CPICH for MIMO Request Indicator

The Power Offset For S-CPICH for MIMO Request Indicator IE is present when the SRNC needs the DRNS to supply, if possible, the Power Offset For S-CPICH for MIMO IE when S-CPICH is used as a phase reference for a second transmit antenna in MIMO mode TS 25.214 [10].
IE/Group Name Power Offset For S-CPICH for MIMO Request Indicator Presence Range IE Type and Reference NULL Semantics Description

9.2.2.106

Single Stream MIMO Activation Indicator

Presence M Range IE Type and Reference NULL Semantics Description

IE/Group Name Single Stream MIMO Activation Indicator

3GPP

Release 11

632

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.107

Single Stream MIMO Mode Indicator

Presence Range IE Type and Reference ENUMERATED (Activate, Deactivate) Semantics Description

IE/Group Name Single Stream MIMO Mode Indicator

9.2.2.108
Void.

HS-DSCH MAC-ehs Format Activation Information

9.2.2.109

The Activation Information IE defines the local activation state of the secondary uplink frequency of the UE in Dual Cell E-DCH operation.
IE/Group Name Activation Information >Uu Activation State M Presence Range 1..<maxnoo fEDCH-1> IE Type and Reference For secondary EDCH. Max 1 in this 3GPP release. ENUMERATED (Activated, De-activated, ...) Semantics Description

The activation state of the secondary UL frequency

Range Bound maxnoofEDCH-1

Explanation Maximum number of uplink frequencies -1 for E-DCH for one UE

9.2.2.110
IE/Group Name

Additional E-DCH FDD Setup Information

Presence Range 1 M O M O 1 M M M O O 9.2.2.16 9.2.2.21A 9.2.2.21a 9.2.2.86 9.2.2.114 9.2.2.53 UL SIR 9.2.1.69 9.2.2.115 9.2.2.112 IE Type and Reference Semantics Description Criticality YES ignore Assigned Criticality

UL DPCH Information >UL Scrambling Code >UL SIR Target Additional E-DCH RL Specific Information To Setup Additional E-DCH FDD Information F-DPCH Information >FDD TPC DL Step Size >Limited Power Increase >Inner Loop DL PC Status >F-DPCH Slot Format Support Request Multicell E-DCH Information

3GPP

Release 11

633

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.111
IE/Group Name

Additional E-DCH Configuration Change Information

Presence Range 0..1 O O O 9.2.2.53 UL SIR 9.2.1.69 9.2.2.116 IE Type and Reference Semantics Description Criticality Used when the E-DCH RL to add does not exist in the current UE context on the secondary UL frequency. Used when an existing EDCH RL on the secondary UL frequency is modified. Used to modify the current additional EDCH configuration with or without a new RL added in this procedure Assigned Criticality

UL DPCH Information >UL Scrambling Code >UL SIR Target Additional E-DCH RL Specific Information To Add

Additional E-DCH RL Specific Information To Modify

9.2.2.117

Additional E-DCH FDD Information To Modify

Additional EDCH FDD Information 9.2.2.112

F-DPCH Information >FDD TPC DL Step Size >Limited Power Increase >Inner Loop DL PC Status >F-DPCH Slot Format Support Request Multicell E-DCH Information

0..1 M M M O O 9.2.2.16 9.2.2.21A 9.2.2.21a 9.2.2.86 9.2.2.114

YES ignore

9.2.2.112

Additional E-DCH FDD Information

Presence Range IE Type and Reference HARQ Process Allocation for 2ms TTI 9.2.2.4O 9.2.2.4MG 9.2.1.95 INTEGER (0..127) For the concept of E-DCH Minimum Set of TFCs see TS 25.321 [41] and TS 25.331 [16]. Semantics Description

IE/Group Name Additional E-DCH FDD Information >HARQ Process Allocation For 2ms Scheduled Transmission Grant >E-DCH Maximum Bitrate >E-DCH Processing Overload Level >E-DCH Minimum Set ETFCI

O O O

3GPP

Release 11

634

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.113

Multicell E-DCH Transport Bearer Mode

This parameter indicates the Multicell E-DCH Transport Bearer Mode. For Multicell E-DCH Transport Bearer Mode = Separate Iur Transport Bearer Mode the Mac-d flows from each carrier uses different Iur transport bearers, for Multicell E-DCH Transport Bearer Mode = UL Flow Multiplexing Mode the Mac-d flows received on the different carriers in the DRNS is multiplexed on one Iur transport bearer (per Mac-d flow). The SRNC should apply the stored cell capabilities for the cell on primary UL frequency for the capabilities related to Multicell E-DCH Transport Bearer Mode.
IE/Group Name Multicell E-DCH Transport Bearer Mode Presence Range IE Type and Reference ENUMERATED (Separate Iur Transport Bearer Mode, UL Flow Multiplexing Mode) Semantics Description

9.2.2.114

Multicell E-DCH Information

Presence O O O O O Range IE Type and Reference 9.2.2.10A 9.2.2.102 ENUMERATED (Activated, Deactivated,...) 9.2.2.85 DL power 9.2.1.21A Semantics Description

IE/Group Name DL Power Balancing Information Minimum Reduced E-DPDCH Gain Factor Secondary UL Frequency Activation State F-DPCH Slot Format Common DL Reference Power

Power on F-DPCH

9.2.2.115
IE/Group Name

Additional E-DCH RL Specific Information To Setup

Presence Range 1..<maxn oofEDC HRLs> M O M O O O O O O O RL ID 9.2.1.49 9.2.1.6 9.2.2.16A 9.2.2.33 DL Power 9.2.1.21A 9.2.2.32 9.2.2.61 9.2.2.62 9.2.2.63 9.2.2.118 IE Type and Reference Semantics Description Criticality Assigned Criticality

E-DCH Additional RL Specific Information >E-DCH Additional RL ID >C-ID >First RLS Indicator >Propagation Delay >Initial DL Tx Power >Primary CPICH Ec/No >E-AGCH Power Offset >E-RGCH Power Offset >E-HICH Power Offset >Additional E-DCH MAC-d Flow Specific Information >Multicell E-DCH RL Specific Information

9.2.2.119

YES

ignore

Range bound maxnoofEDCHRLs

Explanation Maximum number of E-DCH RLs for one UE

3GPP

Release 11

635

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.116
IE/Group Name

Additional E-DCH RL Specific Information To Add

Presence Range 1..<maxn oofEDC HRLs> M M O O O O O O 9.2.2.119 RL ID 9.2.1.49 9.2.1.6 9.2.2.32 9.2.2.61 9.2.2.62 9.2.2.63 9.2.2.118 IE Type and Reference Semantics Description Criticality Assigned Criticality

E-DCH Additional RL Specific Information To Add >E-DCH Additional RL ID >C-ID >Primary CPICH Ec/No >E-AGCH Power Offset >E-RGCH Power Offset >E-HICH Power Offset >Additional E-DCH MAC-d Flow Specific Information >Multicell E-DCH RL Specific Information

YES ignore

Range bound maxnoofEDCHRLs

Explanation Maximum number of E-DCH RLs for one UE

9.2.2.117
IE/Group Name

Additional E-DCH RL Specific Information To Modify

Presence Range 1..<maxno ofEDCHRL s> M O O O O O RL ID 9.2.1.49 9.2.2.61 9.2.2.62 9.2.2.63 9.2.2.118 9.2.2.119 IE Type and Reference Semantics Description Criticality Assigned Criticality

E-DCH Additional RL Specific Information to Modify >E-DCH Additional RL ID >E-AGCH Power Offset >E-RGCH Power Offset >E-HICH Power Offset >Additional E-DCH MAC-d Flow Specific Information >Multicell E-DCH RL Specific Information Range bound maxnoofEDCHRLs

YES ignore

Explanation Maximum number of E-DCH RLs for one UE

3GPP

Release 11

636

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.118
IE/Group Name

Additional E-DCH MAC-d Flow Specific Information

Presence Range 1..<maxno ofEDCHM ACdFlows > M O O 9.2.1.91 9.2.1.3 9.2.1.62 IE Type and Reference Semantics Description

Additional E-DCH MAC-d Flow Specific Information

>E-DCH MAC-d Flow ID >Binding ID >Transport Layer Address Range Bound maxnoofEDCHMACdFlows

Explanation Maximum number of E-DCH MAC-d flows

9.2.2.119
IE/Group Name

Multicell E-DCH RL Specific Information

Presence O O O O O Range IE Type and Reference 9.2.2.33a 9.2.2.13I DL power 9.2.1.21A 9.2.2.27B NULL Semantics Description

Extended Propagation Delay Enhanced Primary CPICH Ec/No DL Reference Power Phase Reference Update Indicator E-DCH DL Control Channel Grant

9.2.2.120

Additional E-DCH FDD Information Response

The Additional E-DCH FDD Information Response IE provides information for new E-DCH radio links on the secondary UL frequency.

3GPP

Release 11
IE/Group Name Additional E-DCH RL Information Response >E-DCH Additional RL ID >Received Total Wide Band Power >DL Power Balancing Activation Indicator >RL Set ID >E-DCH RL Set ID >E-DCH FDD DL Control Channel Information >DL Code Information >Additional E-DCH MAC-d Flow Specific Information Response >>E-DCH MAC-d Flow ID >>Binding ID >>Transport Layer Address >HARQ Process Allocation For 2ms Scheduled Transmission Grant >Maximum Uplink SIR >Minimum Uplink SIR >Maximum Allowed UL Tx Power >Maximum DL TX Power >Minimum DL TX Power >Primary Scrambling Code >UL UARFCN >DL UARFCN >Primary CPICH Power >PC Preamble >Primary CPICH Usage For Channel Estimation >Secondary CPICH Information >F-DPCH Slot Format Range bound maxnoofEDCHRLs M O O O M M O M M M M 0..<maxno ofEDCHM ACdFlows > Presence Range 1..<maxno ofEDCHR Ls>

637

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

RL ID 9.2.1.49 9.2.2.35A 9.2.2.10B 9.2.2.35 RL Set ID 9.2.2.35 9.2.2.4D FDD DL Code Information 9.2.2.14A

M M M M M O O O M M O O O

9.2.1.91 9.2.1.3 9.2.1.62 HARQ Process Allocation for 2ms TTI 9.2.2.4O Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 9.2.1.35 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.1.45 UARFCN 9.2.1.66 UARFCN 9.2.1.66 9.2.1.44 9.2.2.27a 9.2.2.32A 9.2.2.38A 9.2.2.85

Corresponds to Nu in TS 25.104 [6] Corresponds to Nd in TS 25.104 [6]

Explanation Maximum number of E-DCH RLs for one UE

9.2.2.121

Additional Modified E-DCH FDD Information Response

The Additional Modified E-DCH RL Information Response IE provides information for RLs on the secondary UL frequency that has been modified and existied in the UE Context configuration before the reconfiguration procedure.

3GPP

Release 11
IE/Group Name Additional Modified E-DCH RL Information Response >E-DCH Additional RL ID >DL Power Balancing Updated Indicator >E-DCH FDD DL Control Channel Information >Additional E-DCH MAC-d Flow Specific Information Response >>E-DCH MAC-d Flow ID >>Binding ID >>Transport Layer Address >HARQ Process Allocation For 2ms Scheduled Transmission Grant >Maximum Uplink SIR >Minimum Uplink SIR >Maximum DL TX Power >Minimum DL TX Power >Primary CPICH Usage For Channel Estimation >Secondary CPICH Information Change >F-DPCH Slot Format Range bound maxnoofEDCHRLs M O O 0..<maxno ofEDCHM ACdFlows > M O O O Presence Range 1..<maxno ofEDCHR Ls>>

638

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

RL ID 9.2.1.49 9.2.2.10D 9.2.2.4D

O O O O O O O

9.2.1.91 9.2.1.3 9.2.1.62 HARQ Process Allocation for 2ms TTI 9.2.2.4O Uplink SIR 9.2.1.69 Uplink SIR 9.2.1.69 DL Power 9.2.1.21A DL Power 9.2.1.21A 9.2.2.32A 9.2.2.38B 9.2.2.85

Explanation Maximum number of E-DCH RLs for one UE

9.2.2.122

Additional E-DCH FDD Update Information

Presenc e O Range IE Type and Reference HARQ Process Allocation for 2ms TTI 9.2.2.4O Semantics Description

IE/Group Name HARQ Process Allocation For 2ms Scheduled Transmission Grant Additional E-DCH DL Control Channel Change Information > E-DCH Additional RL ID

0..<max noofED CHRLs > M RL ID 9.2.1.49 Explanation Maximum number of E-DCH RLs for one UE

Range bound maxnoofEDCHRLs

3GPP

Release 11

639

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.123

Cell Capability Container Extension FDD

The Cell Capability Container Extension FDD IE is an extension to the Cell Capability Container FDD IE and indicates the cell capability in the same way as Cell Capability Container Extension FDD IE. The cell capability of multi-cell related functions may depend on that the cell is multi-cell capable (adjacent and/or nonadjacent carrier) or Dual Band capable. Such support indicators in this Cell Capability Container Extension FDD IE shall be ignored by the SRNC if the cell does not have the required support indicated in the Cell Capability Container FDD IE: Multi Cell Support Indicator = "1" and/or Dual Band Support Indicator = "1". Support indicators that depend on multi-cell (adjacent and/or non-adjacent carrier) support are indicated in the table below with /Adjacent-carrier/. Support indicators that depend on Dual Band support are indicated in the table below with /Dual-band/. Support indicators that depend on that the cell supports one or both of multi-cell (adjacent and/or non-adjacent carrier) and Dual Band are indicated in the table below with /Multi-cell/. The marked support indicators indicate the support regardless of the supported multi-cell type in a multicell configuration: supported multi-cell type is - both serving HS-DSCH and secondary serving HS-DSCH, - secondary serving HS-DSCH or - serving HS-DSCH.

3GPP

Release 11
IE/Group Name Presence

640
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

3GPP

Release 11
Cell Capability Container Extension FDD

641

3GPP TS 25.423 V11.2.0 (2012-06)

BIT STRING (128) Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: Cell Specific Tx Diversity Handling For Multi Cell Operation Support Indicator, /Multi-cell/. The second bit: Multi Cell and MIMO Support Indicator, /Adjacent-carrier/. The third bit: Multi Cell and Single Stream MIMO Support Indicator, /Adjacentcarrier/. The fourth bit: Multi Cell EDCH Support Indicator, /Adjacent-carrier/. This bit shall be ignored by the SRNC if the fifth bit: Separate Iur Transport Bearer Support Indicator = 0 and the sixth bit: E-DCH UL Flow Multiplexing Support Indicator = 0 The fifth bit: Separate Iur Transport Bearer Support Indicator, /Adjacent-carrier/. This bit shall be ignored by the SRNC if the fourth bit: Multi Cell E-DCH Support Indicator = 0 The sixth bit: E-DCH UL Flow Multiplexing Support Indicator, /Adjacent-carrier/. This bit shall be ignored by the SRNC if the fourth bit: Multi Cell E-DCH Support Indicator = 0 The seventh to eleventh bit: Maximum No of HSDPA Frequencies Support Indicator, /Multi-cell/. This support indicator is coded as the binary representation of the maximum number of HSDPA frequencies, with the seventh bit as the MSB and the eleventh bit as the LSB. Hexadecimal digit 0 means no support for 3 or more HSDPA carriers. Hexadecimal digits 1 and 2 are reserved. The twelfth bit: Dual Band and MIMO Support Indicator, /Dual Band/. The thirteenth bit: HSDPA 3 or more Carrier and MIMO Single Band Support Indicator, /Adjacent-carrier/

3GPP

Release 11

642

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.124

Non-Serving RL Preconfiguration Setup

The Non-Serving RL Preconfiguration Setup IE indicates that the DRNS may preconfigure E-DCH DL Code Information configured for new non-serving RL for Enhanced Service Cell Change and contains the information for the location of new serving RL after the Enhanced Serving Cell Change.
IE/Group Name CHOICE new Serving RL >New Serving RL in the DRNS >New Serving RL Not in the DRNS >New Serving RL in the DRNS or New Serving RL Not in the DRNS Additional E-DCH NonServing RL Preconfiguration Setup Presence M NULL NULL NULL O NULL Range IE Type and Reference Semantics Description Criticality YES ignore Assigned Criticality

9.2.2.125

Non-Serving RL Preconfiguration Info

The Non-Serving RL Preconfiguration Info IE provides information for the new non-serving RL after Enhanced Serving Cell Change.

3GPP

Release 11
IE/Group Name New non-serving RL E-DCH FDD DL Control Channel Information A Presence O Range

643
IE Type and Reference 9.2.2.4D E-DCH FDD DL Control Channel Information 9.2.2.4D E-DCH FDD DL Control Channel Information

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description E-DCH FDD DL Control Channel Information for nonserving RL in Serving EDCH RLS E-DCH FDD DL Control Channel Information for nonserving RL in non serving E-DCH RLS in in case serving RL is in the DRNS E-DCH FDD DL Control Channel Information for nonserving RL in case serving RL is not in the DRNS E-DCH on Secondary uplink frequency max 1 in this 3GPP release. E-DCH FDD DL Control Channel Information for Additional non-serving RL in Serving EDCH RLS E-DCH FDD DL Control Channel Information for Additional non-serving RL in non serving EDCH RLS in case Additional serving RL is in the DRNS Criticality Assigned Criticality

New non-serving RL E-DCH FDD DL Control Channel Information B

New non-serving RL E-DCH FDD DL Control Channel Information C

9.2.2.4D E-DCH FDD DL Control Channel Information

Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information

0..<maxno ofEDCH1>

EACH

ignore

>New non-serving RL EDCH FDD DL Control Channel Information A

9.2.2.13Dc E-DCH FDD DL Control Channel Information

>New non-serving RL EDCH FDD DL Control Channel Information B

9.2.2.13Dc E-DCH FDD DL Control Channel Information

3GPP

Release 11
>New non-serving RL EDCH FDD DL Control Channel Information C O

644
9.2.2.13Dc E-DCH FDD DL Control Channel Information

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH FDD DL Control Channel Information for Additional non-serving RL in case Additional serving RL is not in the DRNS

9.2.2.126 9.2.2.127

Void Usefulness of Battery Optimization

This IE, when present, indicates whether the device can benefit from UTRAN-based battery consumption optimisation.
IE/Group Name Usefulness of Battery Optimization Presence Range IE Type and Reference Enumerated ( CanBenefit, CannotBenefit ) Semantics Description

9.2.2.128

M1 Report

This IE defines the parameters for M1 report, FDD report of UE radio measurements
IE/Group Name M1 Report >CHOICE Report trigger >>Periodic >>>MDT Report Parameters >>Event1F >>>Measurement quantity >>>threshold Presence M M M 9.2.1.140 ENUMERATED( CPICH Ec/N0, CPICH RSCP, Pathloss, ...) INTEGER(-120165) Range IE type and reference Semantics description

Range used depends on measurement quantity. CPICH RSCP -120..-25 dBm CPICH Ec/No -24..0 dB Pathloss 30..165dB

9.2.2.129

Support of Dynamic DTXDRX Related HS-SCCH Order

The Support of dynamic DTXDRX related HS-SCCH order IE is to indicate if DRNS supports the DRX/DTX related HS-SCCH order for CPC non-uniform UE.
IE/Group Name Support of dynamic DTXDRX related HS-SCCH order Presence Range IE Type and Reference ENUMERATED (Supported, Not Supported) Semantics Description

9.2.2.130

UL CLTD Information Reconf

The UL CLTD Information Reconf IE is used for the reconfiguration of the UL CLTD operation in a UE context.

3GPP

Release 11
IE/Group Name CHOICE Setup, Configuration Change or Removal of UL CLTD >Setup >>UL CLTD Information >Configuration Change >>UL CLTD information To Modify >Removal >>UL CLTD information Removal M Presence 1 Range

645

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

Used when UL CLTD is not configured in the current UE Context 9.2.2.131 Used when the existing UL CLTD configuration in the current UE context is modified M 9.2.2.132 Used when the existing UL CLTD configuration in the current UE context is removed. M 9.2.2.133

9.2.2.131

UL CLTD Information

The UL CLTD Information IE defines the parameters used for UL CLTD operation.
IE/Group Name S-DPCCH Power Offset Information C-ID UL CLTD Activation Information Presence M CDCHonly O Range IE Type and Reference 9.2.2.137 9.2.1.6 9.2.2.138 Semantics Description

Condition DCHonly

Explanation The IE shall be present only if there is no serving EDCH RL or HS-DSCH RL configuration in the concerned UE context.

9.2.2.132

UL CLTD Information To Modify

The UL CLTD information To Modify IE is used for modification of UL CLTD information in a UE Context.
IE/Group Name S-DPCCH Power Offset Information UL CLTD Activation Information Presence O O Range IE Type and Reference 9.2.2.137 9.2.2.138 Semantics Description

9.2.2.133

UL CLTD Information Removal

The UL CLTD Information Removal IE is used for removal of UL CLTD information in a UE Context.
IE/Group Name UL CLTD Information Removal Presence Range IE Type and Reference ENUMERATED (Remove, ...) Semantics Description

3GPP

Release 11

646

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.2.134

UL CLTD State Update Information

The UL CLTD Update Information IE provides information for the activation state of UL CLTD of the UE to be updated.
IE/Group Name UL CLTD State Update Information Presenc e Range IE Type and Reference ENUMERATED (Activate,Deactivate, ...) Semantics Description The suggested UL CLTD activation state.

9.2.2.135

F-TPICH Slot Format

Indicates the slot format used in F-TPICH in DL, accordingly to ref. TS 25.211 [8].
IE/Group Name F-TPICH Slot Format Presence Range IE Type and Reference INTEGER (0..9,) Semantics Description

9.2.2.136

F-TPICH Offset

The F-TPICH Offset is defined as the time offset towards the Primary CCPCH in the cell. The offset is a multiple of 256 chips.
IE/Group Name F-TPICH Offset Presence Range IE Type and Reference INTEGER (0..149) Semantics Description Range: 0..38144 chips Step: 256 chips See ref. TS 25.211 [8]

9.2.2.137

S-DPCCH Power Offset Infomation

The S-DPCCH Power Offset is used to calculate the S-DPCCH gain factor, sc, as defined in TS 25.214 [10], whereas sc is related to the power difference between DPCCH and S-DPCCH.
IE/Group Name S-DPCCH Power Offset Information Presence Range IE Type and Reference INTEGER (0..6,..) Semantics Description According to mapping in ref. TS 25.213 [21] subclause 4.2.1.4.

9.2.2.138

UL CLTD Activation Information

The UL CLTD Activation Information IE defines the activation state of the UE in UL CLTD operation.
IE/Group Name >UL CLTD Activation State Presenc e M Range IE Type and Reference ENUMERATED (Activated, De-activated, ...) Semantics Description The activation state of the UL CLTD.

9.2.2.139

F-TPICH Information

The F-TPICH Information IE defines the parameters used for F-TPICH configuration.

3GPP

Release 11
IE/Group Name F-TPICH Slot Format F-TPICH Offset F-TPICH Channelisation Code Number Presence M M M Range

647

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description

IE Type and Reference 9.2.2.135 9.2.2.136 FDD DL Channelisation Code Number 9.2.2.14

9.2.2.140

F-TPICH Information To Modify

The F-TPICH Information To Modify IE is used for modification of F-TPICH configuration.

IE/Group Name F-TPICH Slot Format F-TPICH Offset F-TPICH Channelisation Code Number Presence O O O Range IE Type and Reference 9.2.2.135 9.2.2.136 FDD DL Channelisation Code Number 9.2.2.14 Semantics Description

9.2.2.141

F-TPICH Information Removal

The F-TPICH Information Removal IE is used for removal of F-TPICH information of a RL.
IE/Group Name F-TPICH Information Removal Presence Range IE Type and Reference ENUMERATED (Remove, ...) Semantics Description

9.2.2.142

F-TPICH Information Reconf

The F-TPICH Information Reconf IE is used for the reconfiguration of the UL CLTD operation of a RL.
IE/Group Name CHOICE Setup, Configuration Change or Removal of FTPICH Information >Setup >>F-TPICH Information >Configuration Change >>F-TPICH Information To Modify >Removal >>F-TPICH information Removal M Presence 1 Used when F-TPICH is not configured in the current RL 9.2.2.139 Used when the existing UL FTPICH configuration in the current RL is modified M 9.2.2.140 Used when the existing UL FTPICH in the current RL is removed. M 9.2.2.141 Range IE Type and Reference Semantics Description

9.2.3 TDD Specific Parameters

This subclause contains parameters that are specific to TDD.

9.2.3.a

Alpha Value

Used to support signalling of cell specific Alpha Value to SRNS.

3GPP

Release 11
IE/Group Name Alpha Value Presence

648
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(0, 1/8, 2/8, 3/8, 4/8, 5/8, 6/8, 7/8, 1) Semantics Description

9.2.3.A
Void.

Block STTD Indicator Burst Type

9.2.3.1
Void.

9.2.3.1a

Cell Capability Container TDD

The Cell Capability Container TDD indicates which functionalities a 3.84Mcps TDD cell supports.
IE/Group Name Cell Capability Container TDD Presence Range IE Type and Reference BIT STRING (32) Semantics Description Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: Delayed Activation Support Indicator. The second bit: HS-DSCH Support Indicator. The third bit: DSCH Support Indicator. The fourth bit: Flexible MACd PDU Size Support Indicator. The fifth: MBMS Support Indicator. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.1b

Cell Capability Container TDD LCR

The Cell Capability Container TDD LCR indicates which functionalities a cell supports.

3GPP

Release 11
IE/Group Name Cell Capability Container TDD LCR Presence

649
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (32) Semantics Description Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: Delayed Activation Support Indicator. The second bit: HS-DSCH Support Indicator. The third bit: DSCH Support Indicator. The fourth bit: Flexible MACd PDU Size Support Indicator. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.2

CCTrCH ID

The CCTrCH ID identifies unambiguously a CCTrCH inside a Radio Link.

IE/Group Name CCTrCH ID Presence Range IE Type and Reference INTEGER (0..15) Semantics Description

9.2.3.2A

DCH TDD Information

The DCH TDD Information IE provides information for DCHs to be established.

3GPP

Release 11
IE/Group Name DCH Information >Payload CRC Presence Indicator >UL FP Mode >ToAWS >ToAWE >DCH Specific Info >>DCH ID >>CCTrCH ID M M M M 1..<maxno ofDCHs> M M Presence Range 1..<maxno ofDCHs>

650
IE Type and Reference 9.2.1.42 9.2.1.67 9.2.1.58 9.2.1.57 9.2.1.16 9.2.3.2

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality UL CCTrCH in which the DCH is mapped DL CCTrCH in which the DCH is mapped For the UL. For the DL. For the UL. For the DL. Assigned Criticality

>>CCTrCH ID

9.2.3.2

>>TrCH Source Statistics Descriptor >>Transport Format Set >>Transport Format Set >>BLER >>BLER >>Allocation/Retention Priority >>Frame Handling Priority >>QE-Selector >>Guaranteed Rate Information >>Traffic Class >>Unidirectional DCH Indicator >TNL QoS Condition CoorDCH

M M M M M M M CCoorDCH O M O O

9.2.1.65 9.2.1.64 9.2.1.64 9.2.1.4 9.2.1.4 9.2.1.1 9.2.1.29 9.2.1.46A 9.2.1.30M 9.2.1.58A 9.2.1.68B 9.2.1.56A

YES YES YES YES ignore ignore reject ignore

Explanation The IE shall be present if this DCH is part of a set of coordinated DCHs (number of instances of the DCH Specific Info IE is greater than 1). Explanation Maximum number of DCHs for one UE.

Range bound maxnoofDCHs

9.2.3.2B
Void

DCH TDD Information Response

9.2.3.2C

DL Timeslot Information

The DL Timeslot Information IE provides information on the time slot allocation for a DL DPCH at 3.84Mcps.

3GPP

Release 11
IE/Group Name DL Timeslot Information >Time Slot >Midamble Shift And Burst Type >TFCI Presence >DL Code Information M M M M Presence Range 1..<maxno OfTS>

651
IE Type and Reference 9.2.1.56 9.2.3.4 9.2.1.55 TDD DL Code Information 9.2.3.8C

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

Range bound maxnoofTSs

Explanation Maximum number of Timeslots for a UE.

9.2.3.2D

DL Time Slot ISCP Info

The DL Time Slot ISCP Info IE gives interference level for each DL time slot within the Radio Link.
IE/Group Name DL Time Slot ISCP Info >Time Slot >DL Timeslot ISCP Range bound maxnoofDLts M M Presence Range 1..<maxno ofDLts> 9.2.1.56 9.2.3.12 IE Type and Reference Semantics Description Criticality Assigned Criticality

Explanation Maximum number of downlink time slots per Radio Link for 3.84Mcps TDD.

9.2.3.2E

DL Timeslot Information LCR

The DL Timeslot Information LCR IE provides information for DL Timeslot to be established for 1.28Mcps TDD.
IE/Group Name Presence Range 1 .. <maxnoof DLtsLCR> M M M M 9.2.3.12a 9.2.3.4C 9.2.1.57 TDD DL Code Information LCR 9.2.3.8D DL Power 9.2.1.21A DL Power 9.2.1.21A IE Type and Reference Semantics Description Criticality Assigned Criticality

DL Timeslot Information LCR >Time Slot LCR >Midamble Shift LCR >TFCI Presence >DL Code Information LCR

>Maximum DL TX Power

>Minimum DL TX Power

Maximum allowed power on DPCH Minimum allowed power on DPCH

YES

ignore

YES

ignore

3GPP

Release 11
Range bound maxnoofDLtSLCR

652

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD.

9.2.3.2F

DL Time Slot ISCP Info LCR

The DL Time Slot ISCP Info LCR IE provides information for DL Interference level for each time slot within the Radio Link for 1.28Mcps TDD.
IE/Group Name Presence Range 1 .. <maxnoofU LtsLCR> M M 9.2.3.12a 9.2.3.12 IE Type and Reference Semantics Description Criticality Assigned Criticality

DL Time Slot ISCP Info LCR >Time Slot LCR >DL Timeslot ISCP

Range bound maxnoofULtsLCR

Explanation Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD

9.2.3.3

DPCH ID

The DPCH ID identifies unambiguously a DPCH inside a Radio Link.

IE/Group Name DPCH ID Presence Range IE Type and Reference INTEGER (0..239) Semantics Description

9.2.3.3a

DSCH TDD Information

The DSCH TDD Information IE provides information for DSCHs to be established.

3GPP

Release 11
IE/Group Name DSCH TDD Information >DSCH ID >CCTrCH ID M M Presence Range 1..<maxno ofDSCHs>

653
IE Type and Reference 9.2.3.3ae 9.2.3.2

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality DL CCTrCH in which the DSCH is mapped. Assigned Criticality

>TrCH Source Statistics Descriptor >Transport Format Set >Allocation/Retention Priority >Scheduling Priority Indicator >BLER >Traffic Class >Binding ID

M M M M M M O

9.2.1.65 9.2.1.64 9.2.1.1 9.2.1.51A 9.2.1.4 9.2.1.58A 9.2.1.3

YES YES

>Transport Layer Address

9.2.1.62

>TNL QoS

9.2.1.56A

Shall be ignored if bearer establishme nt with ALCAP. Shall be ignored if bearer establishme nt with ALCAP. Shall be ignored if bearer establishme nt with ALCAP.

ignore ignore

YES

ignore

YES

ignore

Range bound maxnoofDSCHs

Explanation Maximum number of DSCHs for one UE.

9.2.3.3aa

HS-DSCH TDD Information

The HS-DSCH TDD Information IE is used for initial addition of HS-DSCH information to a UE Context.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flows Information UE Capabilities Information >HS-DSCH Physical Layer Category >1.28 Mcps TDD uplink physical channel capability >Number of Supported Carriers Presence M 1 M O O Range

654
IE Type and Reference 9.2.1.30OA 9.2.1.30Oa 9.2.3.10D ENUMERATE D( One-one carrier, Onethree carrier, Three-three carrier, Onesix carrier, Tree-six carrier, Six-six carrier, ..., One-Two carrier Discontiguous, Two-Two carrier Discontiguous, One-Two carrier Contiguous, Two-Two carrier Contiguous)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only This IE indicates the number of carrier that UE can support at the same time,where One-three carrier means the number of supported carrier is one for the uplink,and three for the downlink. One-Two carrier Discontiguou s and TwoTwo carrier Discontiguou s mean that the UE is capable of supporting two nonadjacent carriers. One-Two carrier Contiguous and TwoTwo carrier Contiguous mean that the UE is only capable of supporting two adjacent carriers. Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only YES YES ignore reject Assigned Criticality

>Multi-carrier HS-DSCH Physical Layer Category >MIMO SF Mode Supported For HS-PDSCH dual stream >UE TS0 Capability LCR

O O O

9.2.1.30Oa Enumerated (SF1, SF1/SF16) ENUMERATE D (TS0 Capable, TS0 Non-Capable)

YES YES YES

ignore ignore ignore

3GPP

Release 11
>UE RF Band Capability LCR MAC-hs Reordering Buffer Size for RLC-UM TDD ACK NACK Power Offset HS-DSCH MAC-d PDU Size Format CNofSupport edCarriers M M O

655
9.2.3.84 9.2.1.34Ab 9.2.3.7I 9.2.1.30OC

3GPP TS 25.423 V11.2.0 (2012-06)

Applicable to 1.28Mcps TDD only. YES If not present, Indexed MAC-d PDU Size shall be used. Applicable to 1.28Mcps TDD only Applicable to 1.28Mcps TDD only Applicable for 1.28Mcps TDD when using multiple frequencies YES reject ignore

HS-SICH SIR Target HS-SICH TPC step size TSN-Length

O O O

UL SIR 9.2.1.69 9.2.3.10a 9.2.3.3ai

YES YES YES

ignore ignore reject

MIMO Activation Indicator Condition NofSupportedCarriers

9.2.1.134

YES

reject

Explanation This IE shall be present if the Number of Supported Carriers IE is equal to "One-Two carrier Discontiguous" or "Two-Two carrier Discontiguous" and the concerned cell and the UE support more than one RF band.

9.2.3.3ab

HS-DSCH TDD Information Response

The HS-DSCH TDD Information Response IE provides information for HS-DSCH that have been established or modified. It also provides additional HS-DSCH information determined within the DRNS.

3GPP

Release 11
IE/Group Name HS-DSCH MAC-d Flow Specific Information Response >HS-DSCH MAC-d Flow ID >Binding ID >Transport Layer Address >HS-DSCH Initial Capacity Allocation HS-SCCH Specific Information Response Presence

656
Range 0..<maxno ofMACdFl ows> M O O O 0..<maxno ofHSSCC Hcodes> 9.2.1.30O 9.2.1.3 9.2.1.62 9.2.1.30Na IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Not applicable to 1.28 Mcps TDD or 7.68Mcps TDD 9.2.1.56 9.2.3.4 9.2.3.8 GLOBAL reject Assigned Criticality

>Time Slot >Midamble Shift And Burst Type >TDD Channelisation Code >HS-SICH Information >>HS SICH ID >>Time Slot >>Midamble Shift And Burst Type >>TDD Channelisation Code HS-SCCH Specific Information Response LCR

M M M 1 M M M M 0..<maxno ofHSSCC Hcodes>

Not applicable to 3.84 Mcps TDD or 7.68Mcps TDD GLOBAL reject

9.2.3.3ad 9.2.1.56 9.2.3.4 9.2.3.8

>Time Slot LCR >Midamble shift LCR >First TDD Channelisation Code >Second TDD Channelisation Code >HS-SICH Information LCR >>HS SICH ID >>Time Slot LCR >>Midamble shift LCR >>TDD Channelisation Code >Used Frequency

M M M

9.2.3.12a 9.2.3.4C TDD Channelisa tion Code 9.2.3.8 TDD Channelisa tion Code 9.2.3.8 1 9.2.3.3ad 9.2.3.12a 9.2.3.4C 9.2.3.8 UARFCN 9.2.1.66 Applicable for 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency which is actually used by the HSSCCH.

M M M M O

YES reject

3GPP

Release 11
IE/Group Name >UARFCN Presence O

657
Range IE Type and Reference 9.2.1.66

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Corresponds to Nt (3GPP TS 25.105) Applicable for 1.28Mcps TDD when using multiple frequencies. See note1 below Applicable to 7.68 Mcps TDD only Criticality YES Assigned Criticality ignore

HS-SCCH Specific Information Response 7.68 Mcps >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TDD Channelisation Code 7.68Mcps >HS-SICH Information >>HS SICH ID >>Time Slot >>Midamble Shift And Burst Type 7.68Mcps >>TDD Channelisation Code 7.68Mcps HS-PDSCH Timeslot Specific Information Response

0..<maxno ofHSSCC Hcodes> M M M 1 M M M M 0..<maxno ofDLts> 9.2.3.3ad 9.2.1.56 9.2.3.23 9.2.3.25 9.2.1.56 9.2.3.23 9.2.3.25

YES

ignore

Not Applicable to 1.28Mcps TDD or 7.68Mcps TDD. 9.2.1.56 9.2.3.4

GLOBAL

reject

>Time Slot >Midamble Shift And Burst Type HS-PDSCH Timeslot Specific Information Response LCR

M M 0..<maxno ofDLtsLC R>

Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. GLOBAL reject

>Time Slot LCR >Midamble Shift LCR HS-PDSCH Timeslot Specific Information Response 7.68Mcps >Time Slot >Midamble Shift And Burst Type 7.68Mcps HARQ Memory Partitioning User Plane Congestion Fields Inclusion HS-SCCH Specific Information Response LCR per UARFCN >HS-SCCH Specific Information Response LCR >>Time Slot LCR >>Midamble Shift LCR >>First TDD Channelisation Code

M M 0..<maxno ofDLts> M M O O 0..<maxH SDPAFreq uency-1> 1..<maxN oOfHSSC CHcodes> M M M

9.2.3.12a 9.2.3.4C Applicable to 7.68Mcps TDD only. 9.2.1.56 9.2.3.23 9.2.1.116 9.2.1.70C Applicable for 1.28Mcps TDD

YES YES GLOBAL

Ignore

ignore reject

9.2.3.12a 9.2.3.4C TDD Channelisa tion Code 9.2.3.8

3GPP

Release 11
IE/Group Name >>Second TDD Channelisation Code >>HS-SICH Information LCR >>>HS SICH ID >>>Time Slot LCR >>>Midamble Shift LCR >>>TDD Channelisation Code >>Used Frequency Presence M

658
Range IE Type and Reference TDD Channelisa tion Code 9.2.3.8 9.2.3.3ad 9.2.3.12a 9.2.3.4C 9.2.3.8 UARFCN 9.2.1.66

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

1 M M M M O

Applicable for 1.28Mcps TDD when using multiple frequencies. This IE indicates the frequency which is actually used by the HSSCCH. Corresponds to Nt 3GPP TS 25.105 Applicable for 1.28Mcps TDD when using multiple frequencies. See note 1 below YES reject

>UARFCN

9.2.1.66

YES

ignore

>HARQ Memory Partitioning per UARFCN >>HARQ Memory Partitioning >UARFCN O O

0..<maxH SDPAFreq uency-1> 9.2.1.116 9.2.1.66 Corresponds to Nt 3GPP TS 25.105 Applicable for 1.28Mcps TDD when using multiple frequencies. See note 1 below 1.28Mcps TDD only Applicable for 1.28Mcps TDD when using multiple frequencies. YES ignore

>TS0 HS-PDSCH Indication LCR Multi-Carrier number

O O

9.2.3.74 Integer(1.. maxHSDP AFrequenc y)

YES YES

ignore ignore

3GPP

Release 11
IE/Group Name MIMO SF Mode for HSPDSCH dual stream Presence O

659
Range IE Type and Reference Enumerate d (SF1, SF1/SF16)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Applicable for 1.28Mcps TDD when MIMO is configured Applicable for 1.28Mcps TDD when MIMO is configured Criticality YES Assigned Criticality reject

MIMO Reference Signal Information

0..<maxNo OfHSSCC Hcodes> 9.2.3.72

YES

reject

>HS-SICH Reference Signal Information Out-of-sync Detection Window

M O

YES YES reject

ENUMERA Unit: ms TED (40, Applicable to 80, 160, 1.28Mcps 320, 640, TDD. ) Note 1: This information element is a simplified representation of the ASN.1 description. Range bound maxnoofMACdFlows maxnoofHSSCCHcodes maxnoofDLts maxnoofDLtsLCR maxHSDPAFrequency

Explanation Maximum number of MAC-d flows. Maximum number of HS-SCCH codes. Maximum number of downlink time slots per Radio Link for 3.84Mcps TDD. Maximum number of Downlink time slots per Radio Link for 1.28Mcps TDD. Maximum number of Frequency that UE can support HSDPA

9.2.3.3ac

HS-DSCH TDD Update Information

The HS-DSCH TDD Update Information IE provides information for HS-DSCH to be updated. At least one IE shall be presented.
IE/Group name HS-SCCH Code Change Indicator TDD ACK NACK Power Offset Presence O O Range IE Type and Reference 9.2.1.30R 9.2.3.7I Semantic Description Criticality Assigned Criticality

9.2.3.3ad

HS-SICH ID

The HS-SICH ID identifies unambiguously a HS-SICH.

IE/Group Name HS SICH ID Presence Range IE Type and Reference INTEGER (0..31) Semantics Description For 1.28Mcps TDD, the IE is INTEGER (0..255). In ASN.1, it is presented by another IE for the value beyond the 31.

9.2.3.3ae

DSCH ID

The DSCH ID is the identifier of an active downlink shared channel. It is unique for each active DSCH among the active DSCHs simultaneously allocated for the same UE.

3GPP

Release 11
IE/Group Name DSCH ID Presence

660
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..255) Semantics Description

9.2.3.3af

DSCH Initial Window Size

Indicates the initial number of MAC-c/sh SDUs that may be transmitted before new credits are received from the DRNC.
IE/Group Name DSCH Initial Window Size Presence Range IE type and reference INTEGER (1..255) Semantics description Number of MAC-c/sh SDUs: 255 = Unlimited number of MAC-c/sh SDUs.

9.2.3.3ag

DSCH Flow Control Information

The DSCH Flow Control Information IE provides flow control information for each scheduling priority class for the DSCH FP over Iur.
IE/Group Name DSCH Flow Control Information >DSCH Scheduling Priority Presence Range 1..16 M Scheduling Priority Indicator 9.2.1.51A 1..<maxN bMACc/shSDUL ength> M O 9.2.1.34 9.2.3.3af IE Type and Reference Semantics Description Criticality Assigned Criticality

>MAC-c/sh SDU Length

>>MAC-c/sh SDU Length >DSCH Initial Window Size Range bound maxNbMAC-c/shSDULength

YES

ignore

Explanation Maximum number of different MAC-c/sh SDU lengths.

9.2.3.3ah

DSCH-RNTI

DSCH-RNTI is the UE identifier allocated by DRNS to be used over the radio interface by Ues having one or several DSCHs and/or USCHs. It is unique within a cell.
IE/Group Name DSCH-RNTI Presence Range IE type and reference INTEGER(0. .65535) Semantics description

9.2.3.3ai

TSN-Length

The IE indicates the TSN length.

IE/Group Name TSN-Length Presence Range IE Type and Reference ENUMERATED (tsn-6bits, tsn-9bits) Semantics Description

3GPP

Release 11

661

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.3A

Maximum Number of Timeslots

Defines the maximum number of timeslots the UE has the capability of receiving or transmitting. [3.84Mcps TDD and 7.68Mcps TDD in a frame] [1.28Mcps TDD in a subframe]
IE/Group Name Maximum Number of Timeslots Presence Range IE Type and Reference INTEGER (1..14) Semantics Description For 1.28Mcps TDD the values 7 through 14 are not used.

9.2.3.3B

Maximum Number of UL Physical Channels per Timeslot

Defines the maximum number of physical channels [3.84Mcps TDD and 7.68Mcps TDD per frame] [1.28Mcps TDD per subframe] that the UE is capable to transmit.
IE/Group Name Maximum Number of UL Physical Channels per Timeslot Presence Range IE Type and Reference INTEGER (1..2) Semantics Description

9.2.3.3C

Maximum Number of DL Physical Channels

Defines the maximum number of physical channels [3.84Mcps TDD per frame] [1.28Mcps TDD per subframe] that the UE is capable to receive.
IE/Group Name Maximum Number of DL Physical Channels Presence Range IE Type and Reference INTEGER (1..224) Semantics Description For 1.28Mcps TDD the values 97 through 224 are not used.

9.2.3.3D

Maximum Number of DL Physical Channels per Timeslot

Defines the maximum number of physical channels per timeslot that the UE is capable to receive.
IE/Group Name Maximum Number of DL Physical Channels per Timeslot Presence Range IE Type and Reference INTEGER (1..16) Semantics Description

9.2.3.4

Midamble Shift And Burst Type

This information element indicates burst type and midamble allocation. Three different midamble allocation schemes exist: Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL); Common midamble: the midamble is allocated 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).

3GPP

Release 11
IE/Group Name CHOICE Burst Type >Type 1 >> Midamble Configuration Burst Type 1 And 3 >>Midamble Allocation Mode Presence

662
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

M M

ENUMERATED(4, 8, 16) ENUMERATED(Defa ult midamble, Common midamble, UE specific midamble) INTEGER(0..15) ENUMERATED (3, 6) ENUMERATED(Defa ult midamble, Common midamble, UE specific midamble) INTEGER (0..15) ENUMERATED (4, 8, 16) ENUMERATED(Defa ult midamble, UE specific midamble) INTEGER(0..15)

As defined in TS 25.221 [12]

>>Midamble Shift Long >Type 2 >> Midamble Configuration Burst Type 2 >>Midamble Allocation Mode

C-UE M M

As defined in TS 25.221 [12]

>>Midamble Shift Short >Type 3 >> Midamble Configuration Burst Type 1 And 3 >>Midamble Allocation Mode >>Midamble Shift Long

C-UE M M C-UE

UL only As defined in TS 25.221 [12]

Condition UE

Explanation The IE shall be present if the Midamble Allocation Mode IE is set to UE-specific midamble.

9.2.3.4A

Minimum Spreading Factor

Defines the minimum spreading factor the UE has the capability of receiving or transmitting.
IE/Group Name Minimum Spreading Factor Presence Range IE Type and Reference INTEGER (1..16) Semantics Description

9.2.3.4B

IPDL TDD parameters

The IPDL TDD Parameters IE provides the information for the IPDL Configuration applied in 3.84Mcps TDD mode.

3GPP

Release 11
IE/Group name IP Spacing TDD IP Start IP Slot IP P-CCPCH Presence M M M M

663
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERAT ED(30,40,50 , 70, 100,) INTEGER(0. .4095) INTEGER(0. .14) ENUMERAT ED(Switch off 1 frame, Switch off 2 frames) 9.2.1.4B Semantics Description See TS 25.224 [22] See TS 25.224 [22] See TS 25.224 [22] See TS 25.224 [22]

Burst mode parameters

9.2.3.4Bb

IPDL TDD parameters LCR

The IPDL TDD Parameters LCR IE provides the information for the IPDL Configuration applied in 1.28Mcps TDD mode.
IE/Group name IP Spacing TDD IP Start IP_Sub Burst mode parameters Presence M M M O Range IE Type and Reference ENUMERAT ED(30,40,50 , 70, 100,) INTEGER(0. .4095) ENUMERAT ED(First,Sec ond,Both) 9.2.1.4B Semantics Description See TS 25.224 [22] See TS 25.224 [22] See TS 25.224 [22]

9.2.3.4C

Midamble shift LCR

This information element indicates midamble allocation in 1.28Mcps TDD. Three different midamble allocation schemes exist: Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL); Common midamble: the midamble is allocated 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).
IE/Group name Midamble Allocation Mode Presence M Range IE Type and Reference ENUMERAT ED(Default midamble, Common midamble, UE specific midamble,...) INTEGER(0. .15) ENUMERAT ED (2, 4, 6, 8, 10, 12, 14, 16, ...) Semantics Description

Midamble Shift Long Midamble Configuration LCR

C-UE M

As defined in TS 25.221 [12]

3GPP

Release 11
Condition UE

664

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation The IE shall be present if the Midamble Allocation Mode IE is set to UE-specific midamble.

9.2.3.4D
Void

Neighbouring TDD Cell Information LCR Primary CCPCH RSCP

9.2.3.5

Received Signal Code Power is the received power on PCCPCH of the target cell after despreading. The reference point for the RSCP is the antenna connector at the UE, see TS 25.225 [14].
IE/Group Name Primary CCPCH RSCP Presence Range IE Type and Reference INTEGER( 0..91) Semantics Description According to mapping of the non-negative values in TS 25.123 [24].

9.2.3.5a

Primary CCPCH RSCP Delta

Primary CCPCH RSCP Delta is the offset used to report the negative reporting range of P-CCPCH RSCP as per TS 25.123 [24].
IE/Group Name Primary CCPCH RSCP Delta Presence Range IE Type and Reference INTEGER( -5..-1,) Semantics Description If present, the actual value of Primary CCPCH RSCP = Primary CCPCH RSCP Delta

9.2.3.5A
Void.

PRACH Midamble

9.2.3.5B

RB Identity

The RB Identity is the identifier of a radio bearer. It is unique for each active Radio bearer among the active radio bearers simultaneously allocated for the same UE.
IE/Group Name RB Identity Presence Range IE Type and Reference INTEGER (0..31) Semantics Description In line with TS 25.331 [16], ch. 10.3.4.11

9.2.3.6

Repetition Length

The Repetition Length represents the number of consecutive Radio Frames inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see TS 25.331 [16]. [1.28Mcps TDD- When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Length represents the number of consecutive Subframes, i.e. 5ms inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see TS 25.331 [16].]
IE/Group Name Repetition Length Presence Range IE Type and Reference INTEGER(1..63 ) Semantics Description

3GPP

Release 11

665

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.7

Repetition Period

The Repetition Period represents the number of consecutive Radio Frames after which the same assignment scheme of Time Slots to a Physical Channel is repeated. This means that if the Time Slot K is assigned to a physical channel in the Radio Frame J, it is assigned to the same physical channel also in all the Radio Frames J+n*Repetition Period (where n is an integer) see TS 25.331 [16]. [1.28Mcps TDD- When applied to configure the E-DCH Non-scheduled Grant Information, the Repetition Period represents the number of consecutiveSubframes, i.e. 5ms after which the same assignment scheme of Time Slots to a Physical Channel is repeated see TS 25.331 [16].]
IE/Group Name Repetition Period Presence Range IE Type and Reference ENUMERATED (1,2,4,8,16,32,6 4) Semantics Description

9.2.3.7A

Rx Timing Deviation

Measured Rx Timing Deviation as a basis for timing advance, either measured directly from a RACH burst, or calculated from the Rx Timing Deviation measurement on the USCH by adding the current Timing Advance value. For 1.28Mcps TDD this IE must be set to 0.
IE/Group Name Rx Timing Deviation Presence Range IE Type and Reference INTEGER (0..127) Semantics Description As specified in TS 25.435 [5], ch. 6.2.7.6

9.2.3.7B

Secondary CCPCH Info TDD

The Secondary CCPCH Info TDD IE provides information on the Secondary CCPCH that carries the logical channel SHCCH for the UE.
IE/Group Name TFCS TFCI Coding Secondary CCPCH >Time Slot >Midamble Shift And Burst Type >TFCI Presence >Secondary CCPCH TDD Code Information >TDD Physical Channel Offset >Repetition Length >Repetition Period FACH >TFS PCH >TFS Range bound maxnoofSCCPCHs maxnoofFACHs Presence M M 0..<maxno ofSCCPC Hs> M M M M M M M 0..maxnoo fFACHs M 0..1 M 9.2.1.64 For the DL. 9.2.1.64 For the DL. 9.2.1.56 9.2.3.4 9.2.1.55 9.2.3.7C 9.2.3.9 9.2.3.6 9.2.3.7 Range IE Type and Reference 9.2.1.63 9.2.3.11 Semantics Description For the DL. Criticality Assigned Criticality

Explanation Maximum number of Secondary CCPCHs per CCTrCH. Maximum number of FACHs mapped onto a Secondary CCPCH.

3GPP

Release 11

666

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.7C

Secondary CCPCH TDD Code Information

The Secondary CCPCH TDD Code Information IE provides TDD Channelisation Code information for all SCCPCHs of one Time Slot.
IE/Group Name Secondary CCPCH TDD Code Information >TDD Channelisation Code Range bound maxnoofSCCPCHs M Presence Range 1..<maxno OfSCCPC Hs> 9.2.3.8 IE Type and Reference Semantics Description Criticality Assigned Criticality

Explanation Maximum number of SCCPCHs for one CCTrCH.

9.2.3.7D

Special Burst Scheduling

The number of frames between special burst transmissions during DTX.

IE/Group Name Special Burst Scheduling Presence Range IE Type and Reference INTEGER(1, 2, .., 256) Semantics Description Number of frames between special burst transmissions during DTX

9.2.3.7E

Synchronisation Configuration

The Synchronisation Configuration parameters that are used by the DRNS in the Radio Link Failure/Restore procedure.
IE/Group Name N_INSYNC_IND N_OUTSYNC_IND T_RLFAILURE Presence M M M Range IE Type and Reference INTEGER(1, 2, .., 256) INTEGER(1, 2, .., 256) ENUMERAT ED(0, 0.1, 0.2, .., 25.5) Semantics Description

Unit: seconds

9.2.3.7F

Secondary CCPCH Info TDD LCR

The Secondary CCPCH Info TDD LCR IE provides information on the Secondary CCPCH that carries the logical channel SHCCH for the UE.

3GPP

Release 11
IE/Group Name TFCS TFCI Coding Secondary CCPCH >Time Slot LCR >Midamble Shift LCR >TFCI Presence >Secondary CCPCH TDD Code Information LCR >TDD Physical Channel Offset >Repetition Length >Repetition Period FACH >TFS PCH >TFS Range bound maxnoofSCCPCHs maxnoofFACHs Presence M M 0..<maxno ofSCCPC Hs> M M M M M M M 0..<maxno ofFACHs> M 0..1 M Range

667
IE Type and Reference 9.2.1.63 9.2.3.11

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description For the DL. Criticality For the DL. For the DL. Assigned Criticality

9.2.3.12a 9.2.3.4C 9.2.1.55 9.2.3.7G 9.2.3.9 9.2.3.6 9.2.3.7 9.2.1.64 9.2.1.64

Explanation Maximum number of Secondary CCPCHs per CCTrCH. Maximum number of FACHs mapped onto a Secondary CCPCH.

9.2.3.7G

Secondary CCPCH TDD Code Information LCR

The Secondary CCPCH TDD Code Information LCR IE provides LCR TDD Channelisation Code information for all SCCPCHs of one Time Slot.
IE/Group Name Secondary CCPCH TDD Code Information >TDD Channelisation Code LCR >SCCPCH Time Slot Format LCR M M Presence Range 1..<maxno OfSCCPC Hs> 9.2.3.8a TDD DL DPCH Time Slot Format LCR 9.2.3.8E IE Type and Reference Semantics Description Criticality Assigned Criticality

Range bound maxnoofSCCPCHs

Explanation Maximum number of SCCPCHs for one CCTrCH.

9.2.3.7H

Support of 8PSK

The Support of 8PSK IE indicates whether 8PSK is supported or not.

IE/Group Name Support of 8PSK Presence Range IE Type and Reference ENUMERAT ED(supported ) Semantics Description

3GPP

Release 11

668

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.7I

TDD ACK NACK Power Offset

The TDD ACK NACK Power Offset IE indicates Power offset used in the UL in the HS-SICH between transmissions carrying positive and negative acknowledgements as per TS 25.331 [16].
IE/Group Name TDD ACK NACK Power Offset Presence Range IE type and reference INTEGER (7..8,) Semantics description Unit: dB Range: -7..+8 dB Step: 1 dB

9.2.3.8

TDD Channelisation Code

The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code that can have a spreading factor of 1, 2, 4, 8 or 16.
IE/Group Name TDD Channelisation Code Presence Range IE Type and Reference ENUMERATED ((1/1), (2/1), (2/2), (4/1), .. (4/4), (8/1), .. (8/8), (16/1), .. (16/16), ) Semantics Description

9.2.3.8a

TDD Channelisation Code LCR

The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 1.28Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16 and there is a choice between QPSK and 8PSK modulation.
IE/Group Name TDD Channelisation Code Presence M Range IE Type and Reference ENUMERAT ED((1/1), (2/1), (2/2), (4/1),..(4/4), (8/1), .. (8/8), (16/1).. (16/16) , ) ENUMERAT ED(QPSK, 8PSK, ) Semantics Description

Modulation

Modulation options for 1.28Mcps TDD in contrast to 3.84Mcps TDD

9.2.3.8A

TDD DPCH Offset

The Offset represents the phase information for the allocation of a group of dedicated physical channels. The Offset Type IE = No Initial Offset is used when a starting offset is not required and the TDD Physical channel offset for each DPCH in the CCTrCH shall be directly determined from the TDD DPCH Offset. The Offset Type IE = Initial Offset is used when a starting offset is required. The TDD DPCH Offset shall map to the CFN and the TDD Physical Channel Offset for each DPCH in this CCTrCH shall calculated by TDD DPCH Offset mod Repetition period, see TS 25.331 [16].

3GPP

Release 11
IE/Group Name CHOICE Offset Type >Initial Offset >>TDD DPCH Offset Value >No Initial Offset >>TDD DPCH Offset Value Presence

669
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

M M

INTEGER (0..255) INTEGER (0..63)

9.2.3.8B

TDD DCHs To Modify

The TDD DCHs To Modify IE provides information for DCHs to be modified.

IE/Group Name TDD DCHs To Modify >UL FP Mode >ToAWS >ToAWE >Transport Bearer Request Indicator >DCH Specific Info >>DCH ID >>CCTrCH ID O O O M 1..<maxno ofDCHs> M O 9.2.1.16 9.2.3.2 UL CCTrCH in which the DCH is mapped. DL CCTrCH in which the DCH is mapped For the UL. For the DL. Presence Range 1..<maxno ofDCHs> 9.2.1.67 9.2.1.58 9.2.1.57 9.2.1.61 IE Type and Reference Semantics Description Criticality Assigned Criticality

>>CCTrCH ID

9.2.3.2

>>Transport Format Set >>Transport Format Set >>Allocation/Retention Priority >>Frame Handling Priority >>Guaranteed Rate Information >>Traffic Class >TNL QoS Range bound maxnoofDCHs

O O O O O O O

9.2.1.64 9.2.1.64 9.2.1.1 9.2.1.29 9.2.1.30M 9.2.1.58A 9.2.1.56A

YES YES YES ignore ignore ignore

Explanation Maximum number of DCHs for one UE.

9.2.3.8C

TDD DL Code Information

The TDD DL Code Information IE provides TDD DL Code information for all DPCHs of one DL Time Slot.
IE/Group Name TDD DL Code Information >DPCH ID >TDD Channelisation Code M M Presence Range 1..<maxno OfDPCHs > 9.2.3.3 9.2.3.8 IE Type and Reference Semantics Description Criticality Assigned Criticality

3GPP

Release 11
Range bound maxnoofDPCHs

670

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation Maximum number of DPCHs for one CCTrCH.

9.2.3.8D

TDD DL Code Information LCR

The TDD DL Code Information LCR IE provides DL Code information for the RL for 1.28Mcps TDD.
IE/Group Name Presence Range 1 .. <maxnoOf DPCHLC R> M M M 9.2.3.5 9.2.3.8a 9.2.3.8E IE Type and Reference Semantics Description Criticality Assigned Criticality

TDD DL Code Information LCR >DPCH ID >TDD Channelisation Code LCR > TDD DL DPCH Time Slot Format LCR

Range bound maxnoOfDPCHLCR

Explanation Maximum number of DPCH in one CCTrCH for 1.28Mcps TDD

9.2.3.8E

TDD DL DPCH Time Slot Format LCR

TDD DL DPCH Time Slot Format LCR indicates the time slot formats used in DL DPCH for 1.28Mcps TDD (see TS 25.221 [12]).
IE/Group Name CHOICE Modulation > QPSK >>QPSK TDD DL DPCH TimeSlot Format LCR > 8PSK >>8PSK TDD DL DPCH TimeSlot Format LCR Presence Range IE type and reference Semantics description

M M

INTEGER (0..24,) INTEGER (0..24,)

9.2.3.9

TDD Physical Channel Offset

The TDD Physical Channel Offset represents the phase information for the allocation of a non DPCH physical channel. (CFN mod Repetition Period = TDD Physical Channel Offset) see TS 25.331 [16].
IE/Group Name TDD Physical Channel Offset Presence Range IE Type and Reference INTEGER (0..63) Semantics Description

9.2.3.10

TDD TPC Downlink Step Size

This parameter indicates step size for the DL power adjustment (see TS 25.224 [22]).
IE/Group Name TDD TPC Downlink Step Size Presence Range IE Type and Reference ENUMERAT ED(1, 2, 3, ) Semantics Description Unit: dB

3GPP

Release 11

671

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.10a

TDD TPC Uplink Step Size

This parameter indicates step size for the UL power adjustment (see TS 25.224 [22]).
IE/Group Name TDD TPC Uplink Step Size Presence Range IE Type and Reference ENUMERAT ED (1, 2, 3,) Semantics Description Unit: dB

9.2.3.10A

TDD UL Code Information

The TDD UL Code Information IE provides TDD UL Code information for all DPCHs of one UL Time Slot.
IE/Group Name TDD UL Code Information >DPCH ID >TDD Channelisation Code Range bound maxnoofDPCHs M M Presence Range 1..<maxno OfDPCHs > 9.2.3.3 9.2.3.8 Explanation Maximum number of DPCHs for one CCTrCH. IE Type and Reference Semantics Description Criticality Assigned Criticality

9.2.3.10B

TDD UL Code Information LCR

The TDD UL Code Information LCR IE provides information for UL Code to be established for 1.28Mcps TDD.
IE/Group Name Presence Range 1 .. <maxno OfDPCH LCR> M M M 9.2.3.5 9.2.3.8a 9.2.3.10C IE Type and Reference Semantics Description Criticality Assigned Criticality

TDD UL Code Information LCR >DPCH ID >TDD Channelisation Code LCR > TDD UL DPCH Time Slot Format LCR Range bound maxnoOfDPCHLCR

Explanation Maximum number of DPCH in one CCTrCH for 1.28Mcps TDD.

9.2.3.10C

TDD UL DPCH Time Slot Format LCR

TDD UL DPCH Time Slot Format LCR indicates the time slot formats used in UL DPCH for 1.28Mcps TDD (see TS 25.221 [12]).

3GPP

Release 11
IE/Group Name CHOICE Modulation > QPSK >>QPSK TDD UL DPCH Time Slot Format LCR > 8PSK >>8PSK TDD UL DPCH Time Slot Format LCR Presence

672
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE type and reference Semantics description

M M

INTEGER (0..69,) INTEGER (0..24,)

9.2.3.10D

1.28 Mcps TDD uplink physical channel capability

1.28 Mcps TDD uplink physical channel capability IE defines the UE uplink physical channel capability for 1.28 Mcps TDD.
IE/Group Name Maximum Number of timeslots per subframe Maximum number of physical channels per timeslot Presence M M Range IE Type and Reference INTEGER (1..6) ENUMERATED (1,2,3,4...) Semantics Description

9.2.3.11

TFCI Coding

The TFCI Coding describes how the TFCI bits are coded. By default 1 TFCI bit is coded with 4 bits, 2 TFCI bits are coded with 8 bits, 3-5 TFCI bits are coded with 16 bits and 6-10 TFCI bits are coded with 32 bits.
IE/Group Name TFCI Coding Presence Range IE Type and Reference ENUMERATE D(4, 8, 16, 32, ) Semantics Description

9.2.3.12

DL Timeslot ISCP

DL Timeslot ISCP is the measured interference in a downlink timeslot at the UE, see TS 25.225 [14].
IE/Group Name DL Timeslot ISCP Presence Range IE Type and Reference INTEGER( 0..91) Semantics Description According to mapping in TS 25.123 [24].

9.2.3.12a

Time Slot LCR

The Time Slot LCR is the number of the traffic time slot within a 5 ms subframe of LCR TDD.
IE/Group Name Time Slot LCR Presence Range IE Type and Reference INTEGER (0..6) Semantics Description

9.2.3.12A

Timing Advance Applied

Defines the need for Timing Advance functions such as Rx Timing Deviation measurement in a particular cell.
IE/Group Name Timing Advance Applied Presence Range IE Type and Reference ENUMERAT ED(Yes, No) Semantics Description

3GPP

Release 11

673

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.13

Transport Format Management

Defines whether the cell transmits the transport format information via broadcast or whether the transport format information is transmitted to the UE using dedicated RRC procedures
IE/Group Name Transport Format Management Presence Range IE Type and Reference ENUMERAT ED(Cell Based, UE Based,) Semantics Description

9.2.3.13A

UL Timeslot ISCP

UL Timeslot ISCP is the measured interference in a uplink timeslot at the DRNS, see TS 25.225 [14].
IE/Group Name UL Timeslot ISCP Presence Range IE Type and Reference INTEGER( 0..127) Semantics Description According to mapping in TS 25.123 [24].

9.2.3.13B

UL PhysCH SF Variation

Indicates whether variation of SF in UL is supported by Radio Link or not.

IE/Group Name UL PhysCH SF Variation Presence Range IE Type and Reference ENUMERAT ED(SF_Vari ation_suppor ted, SF_Variation _NOT_supp orted) Semantics Description

9.2.3.13C

UL Timeslot Information

The UL Timeslot Information IE provides information on the time slot allocation for a UL DPCH.
IE/Group Name UL Timeslot Information >Time Slot >Midamble Shift And Burst Type >TFCI Presence >UL Code Information M M M M Presence Range 1..<maxno OfTS> 9.2.1.56 9.2.3.4 9.2.1.55 TDD UL Code Information 9.2.3.10A Explanation Maximum number of Timeslots for a UE. IE Type and Reference Semantics Description Criticality Assigned Criticality

Range bound maxnoofTSs

9.2.3.13D

UL Time Slot ISCP Info

The UL Time Slot ISCP Info IE gives interference level for each UL time slot within the Radio Link.

3GPP

Release 11
IE/Group Name UL Time Slot ISCP Info >Time Slot >UL Timeslot ISCP Range bound maxnoofULts M M Presence Range 1 .. <maxnoof ULts>

674
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.56 9.2.3.13A

Explanation Maximum number of uplink time slots per Radio Link.

9.2.3.13E

TSTD Indicator

Indicates if TSTD shall be active or not for the DL DPCH.

IE/Group Name TSTD Indicator Presence Range IE Type and Reference ENUMERAT ED(active, inactive) Semantics Description

9.2.3.13F

TSTD Support Indicator

Indicates if UE support TSTD or not for DL DPCH.

IE/Group Name TSTD Support Indicator Presence Range IE Type and Reference ENUMERAT ED(TSTD supported, TSTD not supported) Semantics Description

9.2.3.13Fa

UE Measurement Hysteresis Time

The UE Measurement Hysteresis Time provides the duration during which a reporting criterion has to be fulfilled for the UE Measurement Reporting procedure to be triggered, see TS 25.331 [16]..
IE/Group Name UE Measurement Hysteresis Time Presence Range IE Type and Reference INTEGER(0.. 15) Semantics Description Unit: dB Range: 0..7.5 dB Step: 0.5 dB

9.2.3.13Fb

UE Measurement Parameter Modification Allowed

Indicates if the SRNC may modify the UE measurement parameters based on its existing measurement schedule.
IE/Group Name UE Measurement Parameter Modification Allowed Presence Range IE Type and Reference ENUMERAT ED (Parameter Modification Allowed, ) Semantics Description

3GPP

Release 11

675

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.13Fc

UE Measurement Report Characteristics

The UE Measurement Report Characteristics, defines how the reporting shall be performed. For definition of the event criteria see TS 25.331 [16].
IE/Group Name CHOICE UE Report Characteristics >Periodic >>Amount of Reporting Presence Range IE Type and Reference Semantics Description

>>Reporting Interval

ENUMERAT ED(1, 2, 4, 8, 16, 32, 64, infinity) ENUMERAT ED (250, 500, 1000, 2000, 3000, 4000, 6000, 8000, 12000, 16000, 20000, 24000, 28000, 32000, 64000) 9.2.3.13Fd 9.2.3.13Fg 9.2.3.13Fa 9.2.3.13Fd 9.2.3.13Fg 9.2.3.13Fa 9.2.3.13Fd 9.2.3.13Fg 9.2.3.13Fd 9.2.3.13Fg 9.2.3.13Fg 9.2.3.13Fg

Indicates the interval of periodical report interval in milliseconds

>Event 1h >>UE Measurement Threshold >>UE Measurement Time to Trigger >>Hysteresis >Event 1i >>UE Measurement Threshold >>UE Measurement Time to Trigger >>Hysteresis >Event 6a >>UE Measurement Threshold >>UE Measurement Time to Trigger >Event 6b >>UE Measurement Threshold >>UE Measurement Time to Trigger >Event 6c >>UE Measurement Time to Trigger >Event 6d >>UE Measurement Time to Trigger

M M M M M M M M M M M M

The threshold for which the DRNS shall trigger a measurement report.

The threshold for which the DRNS shall trigger a measurement report.

9.2.3.13Fd

UE Measurement Threshold

The Measurement Threshold defines which threshold that shall trigger Event 1h, 1i, 6a or 6b, see TS 25.331 [16].

3GPP

Release 11
IE/Group Name CHOICE UE Measurement Threshold >Timeslot ISCP >>Timeslot ISCP >UE Tx Power >>UE Transmitted Power Presence

676
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

M M

INTEGER (-115..-25) INTEGER(50..33)

In dBm In dBm

9.2.3.13Fe

UE Measurement Timeslot Information HCR

The UE Measurement Time Slot Information IE provides information for DL timeslots for the UE to measure, see TS 25.331 [16].
IE/Group Name UE Measurement Timeslot Information >Time Slot >Burst Type Presence Range 1..<maxnoOfTS> M M 9.2.1.56 ENUMERAT ED(Type1, Type 2, Type 3,) Explanation Maximum number of Timeslots for a UE for 3.84Mcps TDD. IE Type and Reference Semantics Description

Range bound maxnoofTSs

9.2.3.13Ff

UE Measurement Timeslot Information LCR

The UE Measurement Time Slot Information LCR IE provides information for DL timeslots for the UE to measure, see TS 25.331 [16].
IE/Group Name UE Measurement Time Slot Information LCR >Time Slot LCR Range bound maxnoOfTSLCR M Presence Range 1 .. <maxnoOfTSLCR > 9.2.3.12a IE Type and Reference Semantics Description

Explanation Maximum number of Timeslots for a UE for 1.28Mcps TDD

9.2.3.13Fg

UE Measurement Time to Trigger

The UE time to trigger indicates the period of time between the timing of event detection and the timing of sending Measurement Report, see TS 25.331 [16].
IE/Group Name UE Measurement Time to trigger Presence M Range IE Type and Reference ENUMERAT ED(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000) Semantics Description Time in ms.

3GPP

Release 11

677

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.13Fh

UE Measurement Type

The UE Measurement Type identifies the type of measurement that shall be performed see TS 25.331 [16].
IE/Group Name UE Measurement Type Presence M Range IE Type and Reference ENUMERAT ED(Primary CCPCH RSCP , DL Timeslot ISCP, UE Transmitted Power,) Semantics Description

9.2.3.13Fi

UE Measurement Value

The UE Measurement Value shall be the most recent value for this measurement, for which the reporting criteria were met.
IE/Group Name CHOICE UE Measurement Value >UE Transmitted Power >>UE Transmitted Power list HCR >>>Time Slot >>>UE Transmitted Power >>UE Transmitted Power list LCR >>>Time Slot LCR >>>UE Transmitted Power >>UE Transmitted Power list 768 >>>Time Slot >>>UE Transmitted Power >P-CCPCH RSCP >>Primary CCPCH RSCP >>Primary CCPCH RSCP Delta >DL Timeslot ISCP >>Timeslot list HCR >>>Time Slot >>>Timeslot ISCP >>Timeslot list LCR >>>Time Slot LCR >>>Timeslot Presence M 0..<maxnoOfTS> M M 0..< maxnoOfTSLCR> M M 0..<maxnoOfTS> M M 9.2.1.56 INTEGER (0..104) 9.2.3.5 9.2.3.5a 0..<maxnoOfTS> M M 0..<maxnoOfTSL CR> M M 9.2.3.12a 9.2.3.12 9.2.1.56 9.2.3.12 Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD 9.2.3.12a INTEGER (0..104) According to mapping in TS 25.123 [24] Values 0..20 are not used Mandatory for 7.68Mcps TDD, not applicable to 1.28Mcps TDD or 3.84Mcps TDD According to mapping in TS 25.123 [24] Values 0..20 are not used According to mapping in TS 25.123 [24] According to mapping in TS 25.123 [24] Mandatory for 3.84Mcps TDD, not applicable to 1.28Mcps TDD or 7.68Mcps TDD 9.2.1.56 INTEGER (0..104) Mandatory for 3.84Mcps TDD, not applicable to 1.28Mcps TDD or 7.68Mcps TDD According to mapping in TS 25.123 [24] Values 0..20 are not used Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD Range IE Type and Reference Semantics Description

O O

3GPP

Release 11
ISCP >>Timeslot list 768 >>>Time Slot >>>Timeslot ISCP Range bound maxnoOfTS maxnoofTSLCR M M

678

3GPP TS 25.423 V11.2.0 (2012-06)

0..<maxnoOfTS> 9.2.1.56 9.2.3.12

Mandatory for 7.68Mcps TDD, not applicable to 1.28Mcps TDD or 3.84Mcps TDD

Explanation Maximum number of Timeslots for a UE for 3.84Mcps TDD or 7.68Mcps TDD. Maximum number of Timeslots for a UE for 1.28Mcps TDD.

9.2.3.13Fj

UE Measurement Value Information

The UE Measurement Value Information IE provides information both on whether or not the UE Measurement Value is provided in the message and if provided also the UE Measurement Value itself.
IE/Group Name CHOICE Measurement Availability Indicator >Measurement Available >>UE Measurement Value >Measurement not Available Presence M M 9.2.3.13Fi NULL Range IE Type and Reference Semantics Description

9.2.3.13G

UL Timeslot Information LCR

The UL Timeslot Information LCR IE provides information on the timeslot allocation for an UL DPCH.
IE/Group Name Presence Range 1 .. <maxn oofULt sLCR> M M M M 9.2.3.12a 9.2.3.4C 9.2.1.57 TDD UL Code Information LCR 9.2.3.10B 9.2.3.17 IE Type and Reference Semantics Description Criticality Assigned Criticality

UL Timeslot Information LCR

>Time Slot LCR >Midamble Shift LCR >TFCI Presence >UL Code Information LCR

>PLCCH Information Range bound maxnoofULtsLCR

YES

ignore

Explanation Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD.

9.2.3.13H

UL Time Slot ISCP Info LCR

The UL Time Slot ISCP Info LCR IE provides information for UL Interference level for each time slot within the Radio Link for 1.28Mcps TDD.

3GPP

Release 11
IE/Group Name Presence Range 1 .. <maxnoofU LtsLCR> M M

679
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

UL Time Slot ISCP Info >Time Slot LCR >UL Timeslot ISCP

9.2.3.12a 9.2.3.26A

Range bound maxnoofULtsLCR

Explanation Maximum number of Uplink time slots per Radio Link for 1.28Mcps TDD

9.2.3.13I

Uplink Synchronisation Frequency

The UL Synchronisation Frequency IE specifies the frequency of the adjustment of the uplink transmission timing.
IE/Group Name Uplink synchronisation frequency Presence Range IE Type and Reference INTEGER (1..8) Semantics Description Unit: subframe, step: 1

9.2.3.13J

Uplink Synchronisation Step Size

The UL Synchronisation Step Size IE specifies the step size to be used for the adjustment of the uplink transmission timing.
IE/Group Name Uplink synchronisation step size Presence Range IE Type and Reference INTEGER (1..8) Semantics Description Unit: 1/8 chip, step: 1.

9.2.3.13K

Uplink Timing Advance Control LCR

The Uplink Timing Advance Control LCR indicates the parameters which are used to support Uplink Synchronisation for the UE in 1.28Mcps TDD.

3GPP

Release 11
IE/Group Name SYNC UL codes bitmap FPACH info >Time Slot LCR >TDD Channelisation Code LCR >Midamble Shift LCR >WT PRXupPCHdes Presence M 1 M M M M M Range

680

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BITSTRING (8) Semantics Description Each bit indicates the availability of a SYNC_UL code.

9.2.3.12a 9.2.3.8a 9.2.3.4C INTEGER (1..4) INTEGER (-120 .. 58, ...) 1 Maximum number of subframes to wait for transmission of FPACH. Desired UpPCH receive power. Unit: dBm Step size: 1

SYNC UL procedure parameters >Maximum Sync UL transmissions >Power Ramp Step Mmax

M M M

ENUMERATED (1,2,4,8,...) INTEGER (0..3, ...) INTEGER (1..32)

Maximum number of synchronisation attempts

9.2.3.13L

USCH ID

The USCH ID is the identifier of an uplink shared channel. It is unique among the USCHs simultaneously allocated for the same UE.
IE/Group Name USCH ID Presence Range IE Type and Reference INTEGER (0..255) Semantics Description

9.2.3.14

USCH Information

The USCH Information IE provides information for USCHs to be established.

3GPP

Release 11
IE/Group Name USCH Information >USCH ID >CCTrCH ID M M Presenc e Range 1 to <maxnoofU SCHs>

681
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.3.14 9.2.3.2

UL CCTrCH in which the USCH is mapped For USCH

>TrCH Source Statistics Descriptor >Transport Format Set >Allocation/Retention Priority >Scheduling Priority Indicator >RB Info

M M M M 1..<maxnoo fRB> M M O

9.2.1.65 9.2.1.64 9.2.1.1 9.2.1.51A

All Radio Bearers using this USCH 9.2.3.5B 9.2.1.58A 9.2.1.3 Shall be ignored if bearer establishme nt with ALCAP. Shall be ignored if bearer establishme nt with ALCAP.

>>RB Identity >Traffic class >Binding ID

YES YES

ignore ignore

>Transport Layer Address

9.2.1.62

YES

ignore

>TNL QoS Range bound maxnoofUSCHs maxnoofRBs

9.2.1.56A

YES

ignore

Explanation Maximum number of USCHs for one UE. Maximum number of Radio Bearers for one UE.

9.2.3.16

Support of PLCCH

The Support of PLCCH IE indicates whether PLCCH is supported or not.

IE/Group Name Support of PLCCH Presence Range IE Type and Reference ENUMERAT ED(supported ) Semantics Description

9.2.3.17

PLCCH Information

The PLCCH Information IE carres a PLCCH assignment for a timeslot of an UL DCH-type CCTrCH.
IE/Group Name TDD Channelisation Code Time Slot LCR Midamble Shift LCR PLCCH Sequence Number Presence M M M M Range IE Type and Reference 9.2.3.8 9.2.3.12a 9.2.3.4C 9.2.3.18 Semantics Description Only QPSK modulation is used with PLCCH

3GPP

Release 11

682

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.18

PLCCH Sequence Number

This sequence number represents a portion of a PLCCH used to signal TPC / SS bits to a single UE. A value of zero indicates that the PLCCH assignment has been deleted.
IE/Group Name PLCCH Sequence Number Presence Range IE Type and Reference INTEGER (0..14) Semantics Description

9.2.3.19

Minimum Spreading Factor 7.68Mcps

Defines the minimum spreading factor the UE has the capability of receiving or transmitting for 7.68Mcps TDD.
IE/Group Name Minimum Spreading Factor 768 Presence Range IE Type and Reference INTEGER (1..32) Semantics Description

9.2.3.20

Maximum Number of DL Physical Channels 7.68Mcps

Defines the maximum number of physical channels for 7.68Mcps TDD per frame that the UE is capable to receive.
IE/Group Name Maximum Number of DL Physical Channels 768 Presence Range IE Type and Reference INTEGER (1..448) Semantics Description

9.2.3.21

Maximum Number of DL Physical Channels per Timeslot 7.68Mcps

Defines the maximum number of physical channels per timeslot that the UE is capable to receive for 7.68 Mcps TDD.
IE/Group Name Maximum Number of DL Physical Channels per Timeslot 768 Presence Range IE Type and Reference INTEGER (1..32) Semantics Description

9.2.3.22

Secondary CCPCH Info 7.68Mcps TDD

The Secondary CCPCH Info 7.68Mcps TDD IE provides information on the Secondary CCPCH that carries the logical channel SHCCH for the UE for 7.68Mcps TDD.

3GPP

Release 11
IE/Group Name TFCS TFCI Coding Secondary CCPCH >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TFCI Presence >Secondary CCPCH TDD Code Information 7.68Mcps >TDD Physical Channel Offset >Repetition Length >Repetition Period FACH >TFS PCH >TFS Range bound maxnoofSCCPCHs768 maxnoofFACHs Presence M M 0..<maxno ofSCCPC Hs768> M M M M M M M 0..maxnoo fFACHs M 0..1 M Range

683
IE Type and Reference 9.2.1.63 9.2.3.11

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description For the DL. Criticality For the DL. For the DL. Assigned Criticality

9.2.1.56 9.2.3.23 9.2.1.55 9.2.3.24 9.2.3.9 9.2.3.6 9.2.3.7 9.2.1.64 9.2.1.64

Explanation Maximum number of Secondary CCPCHs per CCTrCH. Maximum number of FACHs mapped onto a Secondary CCPCH.

9.2.3.23

Midamble Shift And Burst Type 7.68Mcps

This information element indicates burst type and midamble allocation for 7.68Mcps TDD. Three different midamble allocation schemes exist: Default midamble: the midamble is allocated by layer 1 depending on the associated channelisation code (DL and UL); Common midamble: the midamble is allocated 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).

3GPP

Release 11
IE/Group Name CHOICE Burst Type >Type 1 >> Midamble Configuration Burst Type 1 And 3 >>Midamble Allocation Mode Presence Range

684

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

M M

ENUMERATED(4, 8, 16) ENUMERATED(Defa ult midamble, Common midamble, UE specific midamble) INTEGER(0..15) ENUMERATED (4, 8) ENUMERATED(Defa ult midamble, Common midamble, UE specific midamble) INTEGER (0..7) ENUMERATED (4, 8, 16) ENUMERATED(Defa ult midamble, UE specific midamble) INTEGER(0..15)

As defined in TS 25.221 [12]

>>Midamble Shift Long >Type 2 >> Midamble Configuration Burst Type 2 >>Midamble Allocation Mode

C-UE M M

As defined in TS 25.221 [12]

>>Midamble Shift Short >Type 3 >> Midamble Configuration Burst Type 1 And 3 >>Midamble Allocation Mode >>Midamble Shift Long

C-UE M M C-UE

UL only As defined in TS 25.221 [12]

Condition UE

Explanation The IE shall be present if the Midamble Allocation Mode IE is set to UE-specific midamble.

9.2.3.24

Secondary CCPCH TDD Code Information 7.68Mcps

The Secondary CCPCH TDD Code Information 7.68Mcps IE provides TDD Channelisation Code information for all SCCPCHs of one Time Slot for 7.68Mcps TDD.
IE/Group Name Secondary CCPCH TDD Code Information 7.68Mcps >TDD Channelisation Code 7.68Mcps Range bound maxnoofSCCPCHs768 M Presence Range 1..<maxno OfSCCPC Hs768> 9.2.3.25 IE Type and Reference Semantics Description Criticality Assigned Criticality

Explanation Maximum number of SCCPCHs for one CCTrCH.

9.2.3.25

TDD Channelisation Code 7.68Mcps

The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In 7.68Mcps TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code that can have a spreading factor of 1, 2, 4, 8, 16 or 32.

3GPP

Release 11
IE/Group Name TDD Channelisation Code Presence Range

685

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERATED((1/1) , (2/1), (2/2), (4/1), .. (4/4), (8/1), .. (8/8), (16/1), .. (16/16), (32/1), .. (32,32), ) Semantics Description

9.2.3.26

UL Timeslot Information 7.68Mcps

The UL Timeslot Information IE provides information on the time slot allocation for a UL DPCH for 7.68Mcps TDD.
IE/Group Name UL Timeslot Information >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TFCI Presence >UL Code Information 7.68Mcps M M M M Presence Range 1..<maxno OfTS> 9.2.1.56 9.2.3.23 9.2.1.55 TDD UL Code Information 7.68Mcps 9.2.3.27 Explanation Maximum number of Timeslots for a UE. IE Type and Reference Semantics Description Criticality Assigned Criticality

Range bound maxnoofTSs

9.2.3.27

TDD UL Code Information 7.68Mcps

The TDD UL Code Information 7.68Mcps IE provides TDD UL Code information for all DPCHs of one UL Time Slot for 7.68Mcps TDD.
IE/Group Name TDD UL Code Information >DPCH ID >TDD Channelisation Code 7.68Mcps Range bound maxnoofDPCHs768 M M Presence Range 1..<maxno OfDPCHs 768> 9.2.3.3 9.2.3.25 IE Type and Reference Semantics Description Criticality Assigned Criticality

Explanation Maximum number of DPCHs for one CCTrCH.

9.2.3.28

DL Timeslot Information 7.68Mcps

The DL Timeslot Information 7.68Mcps IE provides information on the time slot allocation for a DL DPCH for 7.68Mcps TDD.

3GPP

Release 11
IE/Group Name DL Timeslot Information >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TFCI Presence >DL Code Information 7.68Mcps M M M M Presence Range 1..<maxno OfTS>

686
IE Type and Reference 9.2.1.56 9.2.3.23 9.2.1.55 TDD DL Code Information 7.68Mcps 9.2.3.29

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

Range bound maxnoofTSs

Explanation Maximum number of Timeslots for a UE.

9.2.3.29

TDD DL Code Information 7.68Mcps

The TDD DL Code Information IE provides TDD DL Code information for all DPCHs of one DL Time Slot for 7.68Mpcs TDD.
IE/Group Name TDD DL Code Information >DPCH ID >TDD Channelisation Code 7.68Mcps Range bound maxnoofDPCHs768 M M Presence Range 1..<maxno OfDPCHs 768> 9.2.3.3 9.2.3.25 IE Type and Reference Semantics Description Criticality Assigned Criticality

Explanation Maximum number of DPCHs for one CCTrCH.

9.2.3.30

Rx Timing Deviation 7.68Mcps

Measured Rx Timing Deviation as a basis for timing advance, either measured directly from a RACH burst, or calculated from the Rx Timing Deviation measurement on the USCH by adding the current Timing Advance value..
IE/Group Name Rx Timing Deviation Presence Range IE Type and Reference INTEGER (0..1023) Semantics Description As specified in TS 25.435 [5]

9.2.3.31

Cell Capability Container 7.68 Mcps TDD

The Cell Capability Container 7.68 McpsTDD indicates which functionalities a cell supports.

3GPP

Release 11
IE/Group Name Cell Capability Container TDD Presence

687
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference BIT STRING (32) Semantics Description Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: Delayed Activation Support Indicator. The second bit: HS-DSCH Support Indicator. The third bit: DSCH Support Indicator. The fourth bit: Flexible MACd PDU Size Support Indicator. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.32

Neighbouring TDD Cell Measurement Information 7.68Mcps

This IE provides information on the 7.68Mcps TDD neighbouring cells used for the purpose of Measurements. Since the measurement can be performed on every time slot and midamble shift, the Time slot IE and Midamble shift and burst type IE shall be included if available.
IE/Group Name UTRAN Cell Identifier UARFCN Cell Parameter ID Time slot Midamble Shift And Burst Type 7.68Mcps Presence M M M O O Range IE Type and Reference 9.2.1.71 9.2.1.66 9.2.1.8 9.2.1.56 9.2.3.23 Semantics Description Corresponds to Nt TS 25.105 [7]

9.2.3.33

UE Measurement Timeslot Information 7.68Mcps

The UE Measurement Time Slot Information IE provides information for DL timeslots for the UE to measure, see TS 25.331 [16].
IE/Group Name UE Measurement Timeslot Information >Time Slot >Burst Type Presence Range 1..<maxnoOfTS> M M 9.2.1.56 ENUMERATED (Type1, Type 2, Type 3,) Explanation Maximum number of Timeslots for a UE for 7.68Mcps TDD. IE Type and Reference Semantics Description

Range bound maxnoofTSs

3GPP

Release 11

688

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.34

DPCH ID 7.68Mcps

The DPCH ID 7.68Mcps identifies unambiguously a DPCH inside a downlink Radio Link for 7.68Mcps TDD.
IE/Group Name DPCH ID Presence Range IE Type and Reference INTEGER (0..479) Semantics Description

9.2.3.35

Rx Timing Deviation 3.84Mcps Extended

Measured Rx Timing Deviation as a basis for timing advance, either measured directly from a RACH burst, or calculated from the Rx Timing Deviation measurement on the USCH by adding the current Timing Advance value. This is used when the extended timing advance is in use at 3.84 Mcps.
IE/Group Name Rx Timing Deviation Presence Range IE Type and Reference INTEGER (0..511) Semantics Description As specified in TS 25.435 [5]

9.2.3.36

E-PUCH Information

The E-PUCH Information IE provides parameters to configure the E-PUCH physical channel for 3.84Mcps TDD and 7.68 Mcps TDD.
IE/Group Name Minimum code rate Presence M Range IE Type and Reference INTEGER (0..63) INTEGER (0..63) ENUMERATED (rv0, rvtable) Semantics Description Unit: Range: 0.055 ..1 Step: 0.015 Unit: Range: 0.055 ..1 Step: 0.015 rv0 indicates that the UE will only use E_DCH RV index 0. rvtable indicates that the UE will use an RSN based RV index as specified in TS 25.211 [8] Number of slots that are required to carry TPC and TFCI (consecutively allocated slots beginning with the first).

Maximum code rate

HARQ Info for E-DCH

NE-UCCH

INTEGER (1..12)

9.2.3.36a

E-PUCH Information LCR

The E-PUCH Information LCR IE provides parameters to configure the E-PUCH physical channel for 1.28Mcps TDD.

3GPP

Release 11
IE/Group Name Minimum code rate Presence M Range

689
IE Type and Reference INTEGER (0..63) INTEGER (0..63) ENUMERAT ED (rv0, rvtable)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Unit: Range: 0.055 ..1 Step: 0.015 Unit: Range: 0.055..1 Step: 0.015 rv0 indicates that the UE will only use E_DCH RV index 0. rvtable indicates that the UE will use an RSN based RV index as specified in TS 25.211 [8] dBm. Reference Desired RX power level for E-PUCH Number of EUCCH and TPC instances within an EDCH TTI. Details are described in TS 25.221 [12]. Unit: Number of subframes. Reference to E-PUCH Power Control for 1.28Mcps TDD in TS 25.224 [22]. If it is not present, UE shall deem it to be infinite in which case closed loop power control shall always be used. Criticality Assigned Criticality

Maximum code rate

HARQ Info for E-DCH

PRXdes_base

INTEGER (-112..-50)

E-PUCH TPC Step Size NE-UCCH

M M

9.2.3.10a INTEGER (1..8)

E-PUCH Power Control GAP

INTEGER (1..255)

YES

ignore

9.2.3.37

E-TFCS Information TDD

Whereas the related E-DCH Transport Block sizes are standardised in TS 25.425 [32] this IE gives details on the Reference Betas.

3GPP

Release 11
IE/Group Name Reference Beta Information QPSK >Reference Code Rate >Reference Beta Reference Beta Information 16QAM >Reference Code Rate >Reference Beta Presence

690
Range 1..<maxnoofRefb etas> M M 1..<maxnoofRefbe tas> M M

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..10) INTEGER( -15..16) Semantics Description

Unit: Range: 0..1 Step: 0.1 Unit: Range: -15..+16 Step: 1 dB Unit: Range: 0..1 Step: 0.1 Unit: Range: -15..+16 Step: 1 dB

INTEGER (0..10) INTEGER( -15..16)

Range Bound maxnoofRefbetas

Explanation Maximum number of signalled reference betas

9.2.3.38

E-DCH MAC-d Flows Information TDD

The E-DCH MAC-d Flows Information TDD IE is used for the establishment of E-DCH MAC-d flows for TDD.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information >E-DCH MAC-d Flow ID >Allocation/Retentio n Priority >TNL QoS >Binding ID M M O O Presence Range 1..<maxno ofEDCHM ACdFlows >

691
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.91 9.2.1.1 9.2.1.56A 9.2.1.3 Shall be ignored if bearer establishmen t with ALCAP. Shall be ignored if bearer establishmen t with ALCAP.

>Transport Layer Address

9.2.1.62

>Payload CRC Presence Indicator >Maximum Number Of Retransmissions For E-DCH >E-DCH HARQ Power Offset TDD >E-DCH MAC-d Flow Multiplexing List >E-DCH Grant Type >E-DCH Logical Channel Information >E-DCH MAC-d Flow Retransmission Timer

M M M O M M O

9.2.1.42 9.2.1.100 9.2.3.49 9.2.1.89 9.2.3.43 9.2.1.92 9.2.3.49a Mandatory for LCR TDD. Not applicable for 3.84Mcps TDD and 7.68Mcps TDD.

YES YES

>Traffic Class

9.2.1.58A Explanation Maximum number of E-DCH MAC-d flows

YES

ignore

Range Bound maxnoofEDCHMACdFlows

9.2.3.39

E-DCH Non-scheduled Grant Information TDD

The E-DCH Non-scheduled Grant Information TDD IE is used to specify the details of an non-scheduled grant for 3.84Mcps and 7.68Mcps TDD.

3GPP

Release 11
IE/Group Name Timeslot Resource Related Information Power Resource Related Information Repetition Period Repetition Length TDD E-PUCH Offset TDD Channelisation Code Presence M M M M M M

692
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.3.44 9.2.3.45 9.2.3.6 9.2.3.7 9.2.3.46 9.2.3.8 Semantics Description

9.2.3.39a

E-DCH Non-scheduled Grant Information LCR TDD

The E-DCH Non-scheduled Grant Information LCR TDD IE is used to specify the details of an non-scheduled grant for 1.28Mcps TDD.
IE/Group Name Timeslot Resource Related Information LCR Power Resource Related Information Repetition Period Repetition Length Subframe Number Presence M M M M M Range IE Type and Reference 9.2.3.44a 9.2.3.45 9.2.3.6 9.2.3.7 ENUMERATED (0,1) Semantics Description

Used to indicate from which subframe of the Radio Frame indicated by TDD EPUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant.

TDD E-PUCH Offset TDD Channelisation Code

M M

9.2.3.46 9.2.3.8

9.2.3.40

E-DCH TDD Information

The E-DCH TDD Information specifies the details of the maximum bit rate and processing overload level.
IE/Group Name E-DCH TDD Maximum Bitrate E-DCH Processing Overload Level E-DCH Power Offset for Scheduling Info Presence O O O Range IE Type and Reference 9.2.3.47 9.2.1.95 9.2.1.96 Semantics Description

9.2.3.40a

E-DCH TDD Information LCR

The E-DCH TDD Information LCR IE specifies the details of UE physical layer category, NodeB processing overload level and power offset, Maximum Number of Retransmission and E-DCH Retransmission timer for scheduling info. The E-AGCH Inactivity Monitor Threshold IE is used for E-AGCH channel monitoring control for scheduled transmission.

3GPP

Release 11
IE/Group Name E-DCH Physical Layer Category LCR Presenc e O Range

693
IE Type and Reference 9.2.3.54

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description If the Extended E-DCH Physical Layer Category LCR IE is included in the E-DCH TDD Information LCR IE, the E-DCH Physical Layer Category LCR IE shall be ignored. In case of multicarrier E-DCH, this IE indicates the capability for each carrier. Criticality Assigned Criticality

E-DCH Processing Overload Level E-DCH Power Offset for Scheduling Info Extended E-DCH Physical Layer Category LCR

O O O

9.2.1.95 9.2.1.96 9.2.3.54A The Extended EDCH Physical Layer Category LCR IE shall be used if the EDCH Physical Layer Category has a value larger than 5. In case of multicarrier E-DCH, this IE indicates the capability for each carrier.

YES reject

Maximum Number of Retransmission for Scheduling Info LCR E-DCH Retransmission timer for Scheduling Info LCR E-AGCH Inactivity Monitor Threshold

O O O

9.2.1.100 9.2.3.49a Enumerated (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, spare5, , infinity) INTEGER (1..3) Units of subframes.

YES YES YES

ignore ignore ignore

SNPL Carrier Group Indicator

Applicable to 1.28Mcps TDD in multi-carrier EDCH operation only. The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. The SNPL carrier group is defined in [16].

YES

reject

3GPP

Release 11
Multi-Carrier E-DCH Physical Layer Category LCR UE TS0 Capability LCR O

694
9.2.3.54B

3GPP TS 25.423 V11.2.0 (2012-06)

Applicable to 1.28Mcps TDD in multi-carrier EDCH operation only. Applicable to 1.28Mcps TDD only. YES reject

ENUMERAT ED (TS0 Capable, TS0 NonCapable)

YES

ignore

9.2.3.41

E-DCH TDD Information Response

The E-DCH TDD Information Response IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B.
IE/Group Name E-DCH MAC-d Flow Specific Information Response >E-DCH MAC-d Flow ID >Binding ID >Transport Layer Address E-AGCH Specific Information Response >Time Slot >Midamble Shift And Burst Type >TDD Channelisation Code E-HICH Information Response >Time Slot >Midamble Shift And Burst Type >TDD Channelisation Code >E-HICH Time Offset E-DCH Non-scheduled Grant Information TDD E-RNTI Range bound maxnoofEDCHMACdFlows maxnoofEAGCHcodes Presence Range 0..<maxnoofEDC HMACdFlows> M O O 0..<maxNoOfEAG CHcodes> M M M 0..1 M M M M O O 9.2.1.56 9.2.3.4 9.2.3.8 9.2.3.48 9.2.3.39 9.2.1.94 Explanation Maximum number of MAC-d flows Maximum number of E-AGCHs assigned to one UE 9.2.1.56 9.2.3.4 9.2.3.8 9.2.1.91 9.2.1.3 9.2.1.62 IE Type and Reference Semantics Description

9.2.3.41a

E-DCH TDD Information Response 1.28Mcps

Only for 1.28Mcps TDD. The E-DCH TDD Information Response 1.28Mcps IE provides information for E-DCH MAC-d flows that have been established or modified. It also provides additional E-DCH information determined within the Node B.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information Response >E-DCH MAC-d Flow ID >Binding ID >Transport Layer Address E-AGCH Specific Information Response >Time Slot LCR >Midamble Shift LCR >TDD Channelisation Code E-HICH Scheduled specific Information Response >Scheduled >>EI Presence Range

695

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

0..<maxnoofEDC HMACdFlows> M O O 0..<maxNoOfEAG CHcodes> M M M 0..1 0..< maxNoOfEHICHc odes> M INTEGER (0..3) E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried. 9.2.3.12a 9.2.3.4C 9.2.3.8 9.2.1.91 9.2.1.3 9.2.1.62

>>Time Slot LCR >>Midamble Shift LCR >>TDD Channelisation Code >Non-Scheduled >>Time Slot LCR >>Midamble Shift LCR >>TDD Channelisation Code >>Signature Sequence Group Index >E-HICH time offset LCR E-DCH Non-scheduled Grant Information LCR TDD E-RNTI Range bound maxnoofEDCHMACdFlows maxnoofEAGCHcodes maxnoofEHICHcodes

M M M 0..1 M M M M M O O

9.2.3.12a 9.2.3.4C 9.2.3.8 9.2.3.12a 9.2.3.4C 9.2.3.8 INTEGER (0..19) 9.2.3.48a 9.2.3.39a 9.2.1.94 Explanation Maximum number of MAC-d flows Maximum number of E-AGCHs assigned to one UE Maximum number of E-HICHs assigned to one UE

9.2.3.42

E-DCH TDD Information to Modify

The E-DCH MAC-d Flows Information TDD IE is used for the establishment of E-DCH MAC-d flows for TDD.

3GPP

Release 11
IE/Group Name E-DCH MAC-d Flow Specific Information >E-DCH MAC-d Flow ID >Allocation/Retention Priority >Transport Bearer Request Indicator >Binding ID M O M O Presence Range 1..<maxno ofEDCHM ACdFlows >

696
IE Type and Reference

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Criticality Assigned Criticality

9.2.1.91 9.2.1.1 9.2.1.61 9.2.1.3 Shall be ignored if bearer establishment with ALCAP. Shall be ignored if bearer establishment with ALCAP.

>Transport Layer Address >TNL QoS >Maximum Number Of Retransmissions For E-DCH >E-DCH HARQ Power Offset TDD >E-DCH MAC-d Flow Multiplexing List >E-DCH Grant Type >E-DCH Logical Channel To Add

9.2.1.62

O O O O O O

9.2.1.56A 9.2.1.100 9.2.3.49 9.2.1.89 9.2.3.43 E-DCH Logical Channel Information 9.2.1.92 9.2.1.93 0..< maxnooflo gicalchann els>

>E-DCH Logical Channel To Modify >E-DCH Logical Channel To Delete >>Logical Channel ID >E-DCH MAC-d Flow Retransmission Timer >Traffic Class MAC-e Reset Indicator E-DCH MAC-d PDU Size Format UE TS0 Capability LCR

M O O O O O

9.2.1.97 9.2.3.49a 9.2.1.58A 9.2.1.99 9.2.1.91A ENUMERATE D (TS0 Capable, TS0 Non-Capable) Applicable to 1.28Mcps TDD only. Applicable for 1.28Mcps TDD only

YES YES YES YES ignore ignore reject ignore

Range Bound maxnoofEDCHMACdFlows maxnooflogicalchannels

Explanation Maximum number of E-DCH MAC-d flows Maximum number of logical channels

9.2.3.43

E-DCH Grant Type

The E-DCH Grant Type identifies whether a MAC-d flow is scheduled or non-scheduled.

3GPP

Release 11
IE/Group Name E-DCH Grant Type Presence

697
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference ENUMERATED (Scheduled, Non-scheduled) Semantics Description

9.2.3.44

Timeslot Resource Related Information

The Timeslot Resource Related Information is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions.
IE/Group Name Timeslot Resource Related Information Presence Range IE Type and Reference BIT STRING (13) Semantics Description

9.2.3.44a

Timeslot Resource Related Information LCR

The Timeslot Resource Related Information LCR IE is a bitmap indicating which of the timeslots configured for E-DCH are allocated for non-scheduled transmissions.
IE/Group Name Timeslot Resource Related Information LCR Presence Range IE Type and Reference BIT STRING (5) Semantics Description

9.2.3.45

Power Resource Related Information

The Power Resource Related Information specifies the maximum allowed E-PUCH power resource (dB relative to Pebase) that the UE may use for non-scheduled transmissions.
IE/Group Name Power Resource Related Information Presence Range IE Type and Reference INTEGER (1..32) Semantics Description

9.2.3.46

E-PUCH Offset

The E-PUCH Offset represents the CFN offset at which an non-scheduled E-DCH grant begins.
IE/Group Name E-PUCH Offset Presence Range IE Type and Reference INTEGER (0..255) Semantics Description

9.2.3.47

E-DCH TDD Maximum Bitrate

The E-DCH TDD Maximum Bitrate parameter indicates the Maximum Bitrate for an E-DCH in TDD mode.
IE/Group Name E-DCH TDD Maximum Bitrate Presence Range IE Type and Reference INTEGER (0..9201,) Semantics Description Bitrate on transport block level. Unit is kbits per second.

9.2.3.48

E-HICH Time Offset

The E-HICH Time Offset ( aka nE-HICH (TS 25.221 [12]))is determined by the Node B.

3GPP

Release 11
IE/Group Name E-HICH Time Offset Presence

698
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (4..44) Semantics Description

9.2.3.48a

E-HICH Time Offset LCR

The E-HICH Time Offset LCR IE(aka nE-HICH (TS 25.221 [12]))is determined by the Node B.
IE/Group Name E-HICH Time Offset LCR Presence Range IE Type and Reference INTEGER (4..15) Semantics Description

9.2.3.49

E-DCH HARQ Power Offset TDD

The E-DCH HARQ Power Offset TDD is the power offset measured in dB.
IE/Group Name E-DCH HARQ Power Offset TDD Presence Range IE Type and Reference INTEGER (0..6) Semantics Description

9.2.3.49a

E-DCH MAC-d Flow Retransmission Timer

The E-DCH MAC-d Flow Retransmission Timer IE is used in the E-DCH retransmission control as defined in TS 25.425 [32].
IE/Group Name E-DCH MAC-d Flow Retransmission Timer Presence Range IE Type and Reference ENUMERATED (10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 140, 160, 200, 240, 280, 320, 400, 480, 560,) Semantics Description Unit: ms Node B may use this value to stop the re-transmission of the corresponding MAC-e PDU.

9.2.3.50

E-DCH Non-scheduled Grant Information 7.68Mcps TDD

The E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE is used to specify the details of an non-scheduled grant for TDD.
IE/Group Name Timeslot Resource Related Information Power Resource Related Information Repetition Period Repetition Length TDD E-PUCH Offset TDD Channelisation Code 7.68Mcps Presence M M M M M M Range IE Type and Reference 9.2.3.44 9.2.3.45 9.2.3.6 9.2.3.7 9.2.3.46 9.2.3.25 Semantics Description

9.2.3.51

E-DCH TDD Information 7.68Mcps

The E-DCH TDD Information 7.68Mcps specifies the details of the maximum bit rate and processing overload level for 7.68Mcps TDD.

3GPP

Release 11
IE/Group Name E-DCH TDD Maximum Bitrate 7.68Mcps E-DCH Processing Overload Level E-DCH Power Offset for Scheduling Info Presence O O O

699
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference 9.2.3.53 9.2.1.95 9.2.1.96 Semantics Description

9.2.3.52

E-DCH TDD Information Response 7.68Mcps

The E-DCH TDD Information Response 7.68Mcps IE provides information for E-DCH MAC-d flows that have been established or modified for 7.68Mcps TDD. It also provides additional E-DCH information determined within the Node B.
IE/Group Name E-DCH MAC-d Flow Specific Information Response >E-DCH MAC-d Flow ID >Binding ID >Transport Layer Address E-AGCH Specific Information Response 7.68Mcps >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TDD Channelisation Code 7.68Mcps E-HICH Information Response 7.68Mcps >Time Slot >Midamble Shift And Burst Type 7.68Mcps >TDD Channelisation Code 7.68Mcps >E-HICH Time Offset E-DCH Non-scheduled Grant Information 7.68Mcps TDD E-RNTI Range Bound maxnoofEDCHMACdFlows maxnoofEAGCHcodes Presence Range 0..<maxnoofEDC HMACdFlows> M O O 0..<maxNoOfEAG CHcodes> M M M 0..1 M M M M O O 9.2.1.56 9.2.3.23 9.2.3.25 9.2.3.48 9.2.3.50 9.2.1.94 Explanation Maximum number of E-DCH MAC-d flows Maximum number of E-AGCHs assigned to one UE 9.2.1.56 9.2.3.23 9.2.3.25 9.2.1.91 9.2.1.3 9.2.1.62 IE Type and Reference Semantics Description

9.2.3.53

E-DCH TDD Maximum Bitrate 7.68Mcps

The E-DCH TDD Maximum Bitrate 7.68Mcps parameter indicates the Maximum Bitrate for an E-DCH in 7.68Mcps TDD mode.
IE/Group Name E-DCH TDD Maximum Bitrate 7.68Mcps Presence Range IE Type and Reference INTEGER (0..17713,) Semantics Description Bitrate on transport block level. Unit is kbits per second.

3GPP

Release 11

700

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.54

E-DCH Physical Layer Category LCR

Only for 1.28Mcps TDD. The E-DCH Physical Layer Category LCR IE parameter indicates the E-DCH physical layer capability of UE in LCR TDD mode.
IE/Group Name E-DCH Physical Layer Category LCR Presence Range IE Type and Reference INTEGER (1..5) Semantics Description As defined in TS 25.306 [42]

9.2.3.54A

Extended E-DCH Physical layer Category LCR

Only for 1.28Mcps TDD. The Extended E-DCH Physical Layer Category LCR IE parameter indicates the E-DCH physical layer capability of UE in LCR TDD mode.
IE/Group Name Extended E-DCH Physical Layer Category LCR Presence Range IE Type and Reference INTEGER(6,...) Semantics Description As defined in TS 25.306 [42]

9.2.3.54B

Multi-Carrier E-DCH Physical Layer Category LCR

Only for 1.28Mcps TDD. The Multi-Carrier E-DCH Physical Layer Category LCR IE parameter indicates the E-DCH physical layer capability of UE in multi-carrier E-DCH operation mode.
IE/Group Name Multi-Carrier E-DCH Physical Layer Category LCR Presence Range IE Type and Reference INTEGER (1..8,) Semantics Description As defined in [42]

9.2.3.55

UpPCH Information LCR

Only for 1.28Mcps TDD.

IE/Group Name UpPCH Information LCR >UARFCN >UpPCH Position LCR O O Presence Range 1..<maxFr equencyin Cell> 9.2.1.66 9.2.3.56 IE Type and Reference Semantics Description Criticality EACH Assigned Criticality ignore

Range Bound maxFrequencyinCell

Explanation Maximum number of Frequency that can be defined in a Cell

9.2.3.56

UpPCH Position LCR

Only for 1.28Mcps TDD.

IE/Group Name UpPCH Position LCR Presence Range IE Type and Reference INTEGER (1..127) Semantics Description

9.2.3.57

Common E-DCH MAC-d Flow ID

The Common E-DCH MAC-d Flow ID IE is the unique identifier for one MAC-d flow on E-DCH.

3GPP

Release 11
IE/Group Name Common E-DCH MAC-d Flow ID Presence

701
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference INTEGER (0..255) Semantics Description

9.2.3.58

Common E-DCH MAC-d Flow Specific Information LCR

The Common E-DCH MAC-d Flow Specific Information LCR IE provides information associated to Common E-DCH MAC-d Flow used for Common E-DCH.
IE/Group Name Common E-DCH MAC-d Flow Specific Information LCR >Common E-DCH MACd Flow ID >Maximum Number Of Retransmissions For EDCH >E-DCH HARQ Power Offset TDD >E-DCH MAC-d Flow Multiplexing List >Common E-DCH Logical Channel information >>Logical Channel ID >>Maximum MAC-d PDU Size Extended Presence Range 1..<maxnoofEDC HMACdFlowsLCR > M M M O M M M 1..<maxnooflogic alchannelsLCR> 9.2.1.97 MAC PDU Size Extended 9.2.1.34D Explanation Maximum number of E-DCH MAC-d Flows for 1.28Mcps TDD Maximum number of logical channels 9.2.3.57 9.2.1.100 9.2.3.49 9.2.1.89 IE Type and Reference Semantics Description

Range bound maxnoofEDCHMACdFlowsLCR maxnooflogicalchannelsLCR

9.2.3.59

MAC-es Maximum Bit Rate LCR

The MAC-es Maximum Bit Rate LCR IE indicates the maximum number of bits per second to be delivered over the air interface.
IE/Group Name MAC-es Maximum Bit Rate LCR Presence Range IE Type and Reference INTEGER (0.. 256,000,000, ) Semantics Description Unit: bit/s

9.2.3.60

Idle Interval Information

The Idle Interval Information IE indicates the idle interval used for E-UTRAN measurements by a multi-RAT UE in CELL_DCH state. See TS 36.133 [64].
IE/Group Name K Offset Presence M M Range IE Type and Reference INTEGER (2..3) INTEGER (0..7) Semantics Description The actual idle interval period = 2^k. The idle interval position in the period.

3GPP

Release 11

702

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.61

Continuous Packet Connectivity DRX Information LCR

The Continuous Packet Connectivity DRX Information LCR IE defines the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name Enabling Delay HS-SCCH DRX Information >UE DRX Cycle >Inactivity Threshold for UE DRX Cycle >UE DRX Offset >Inactivity Threshold for UE DRX Cycle Ext E-AGCH DRX Information CHOICE E-AGCH DRX information type >Same as HS-SCCH Presence M 1 M O M O 0..1 M NULL Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the EAGCH Inactivity Monitor Threshold is absent Units of subframes. Units of subframes. ENUMERATED(1,2,4 ,8,16,32,64,) ENUMERATED(1,2,4 ,8,16,32,64,) INTEGER (0..63) ENUMERATED(128, 256,512,) Units of subframes Units of subframes Units of subframes. Offset of the UE DRX cycles at the given TTI Units of subframes YES ignore Range IE Type and Reference ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) Semantics Description Units of radio frames Criticality Assigned Criticality

>E-AGCH DRX parameters >>E-AGCH DRX cycle >>E-AGCH Inactivity Monitor Threshold >>E-AGCH DRX Offset

M O

ENUMERATED (1, 2, 4, 8, 16 ,32 ,64,) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity, ) INTEGER (0.. 63)

Units of subframes. Offset of the E-AGCH DRX cycles.

9.2.3.62

Continuous Packet Connectivity DRX Information To Modify LCR

The Continuous Packet Connectivity DRX Information To Modify LCR IE is used for modification of Continuous Packet Connectivity DRX information in a Node B Communication Context. The Continuous Packet Connectivity DRX Information To Modify LCR IE shall include at least one of the following IE.

3GPP

Release 11
IE/Group Name Enabling Delay CHOICE DRX Information To Modify >Modify >>HS-SCCH DRX Information >>>UE DRX Cycle >>>Inactivity Threshold for UE DRX Cycle >>>UE DRX Offset >>>Inactivity Threshold for UE DRX Cycle Ext >>E-AGCH DRX Information >>>CHOICE E-AGCH DRX information type >>>>Same as HSSCCH Presence O O 0..1 M O M O 0..1 M Range

703
IE Type and Reference ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Units of radio frames Criticality Assigned Criticality

ENUMERATED(1,2,4 ,8,16,32,64,) ENUMERATED(1,2,4 ,8,16,32,64,) INTEGER (0..63) ENUMERATED(128, 256,512,)

Units of subframes Units of subframes Units of subframes. Offset of the UE DRX cycles at the given TTI Units of subframes.

YES ignore

NULL Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the EAGCH Inactivity Monitor Threshold is absent Units of subframes. Units of subframes. -

>>>>E-AGCH DRX parameters >>>>>E-AGCH DRX cycle >>>>>E-AGCH Inactivity Monitor Threshold >>>>>E-AGCH DRX Offset >Deactivate

M O

ENUMERATED (1,2,4,8,16,32,64,) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity, ) INTEGER (0.. 63) NULL

Units of subframes. Offset of the E-AGCH DRX cycles.

9.2.3.63

Continuous Packet Connectivity DRX Information Response LCR

DRNS uses the Continuous Packet Connectivity DRX Information Response LCR IE to inform the SRNS the parameters used for Continuous Packet Connectivity DRX operation for 1.28 Mcps TDD (see TS 25.224 [22]). Continuous Packet Connectivity DRX related parameters shall be configured by SRNS. For the parameters which can be accepted by DRNS, the DRNS shall not included the related IEs in the Continuous Packet Connectivity DRX Information Response LCR IE. For the parameters which can be not accepted by DRNS, the DRNS shall included the related IEs in the Continuous Packet Connectivity DRX Information Response LCR IE.

3GPP

Release 11
IE/Group Name Enabling Delay HS-SCCH DRX Information >UE DRX Cycle >Inactivity Threshold for UE DRX Cycle >UE DRX Offset >Inactivity Threshold for UE DRX Cycle Ext Presence O 0..1 O O O O Range

704
IE Type and Reference ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128) ENUMERATED(1,2,4 ,8,16,32,64,) ENUMERATED(1,2,4 ,8,16,32,64,) INTEGER (0..63) ENUMERATED(128, 256,512,)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Units of radio frames Criticality Assigned Criticality

Units of subframes Units of subframes Units of subframes. Offset of the UE DRX cycles at the given TTI Units of subframes. This IE can only be used when the Inactivity Threshold for UE DRX Cycle Ext is included in the request message, otherwise, the IE shall not be used

YES ignore

E-AGCH DRX Information CHOICE E-AGCH DRX information type >Same as HS-SCCH

0..1 M NULL Indicate the E-AGCH DRX Cycle and Offset are the same as the HS-SCCH DRX Cycle and Offset, and the EAGCH Inactivity Monitor Threshold is absent Units of subframes. Units of subframes. -

>E-AGCH DRX parameters >>E-AGCH DRX cycle >>E-AGCH Inactivity Monitor Threshold >>E-AGCH DRX Offset

O O

ENUMERATED (1,2,4,8,16,32,64,) ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, infinity, ) INTEGER (0.. 63)

Units of subframes. Offset of the E-AGCH DRX cycles.

9.2.3.64

HS-DSCH Semi-Persistent scheduling Information LCR

The HS-DSCH Semi-Persistent scheduling Information LCR IE defines the parameters used for HS-DSCH semiPersistent scheduling for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name Transport Block Size List Presence Range 1..< maxnoofT BSsMappi ng > M INTEGER (0.. maxnoofTBSsMappi ng-1) INTEGER (1.. maxnoofHSDSCHTBSsLCR) 1..<maxno ofRepetitio nPeriodLC Corresponds to the Transportblock size information field carried on HS-SCCH (see TS 25.222 [46]). Corresponds to the TB index in the related Transport Block Size table (see TS 25.425 [32]). IE Type and Reference Semantics Description

>Transport Block Size maping Index >Transport Block Size Index

Repetition Period list

3GPP

Release 11
R> >Repetition Period Index M

705

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER (0.. maxnoofRepetitionP eriodLCR-1) ENUMERATED (1, 2, 4, 8, 16, 32, 64,) INTEGER (1..63)) ENUMERATED(Res erve)

>Repetition Period >Repetition Length HS-DSCH Semi-Persistent Resource Reservation Indicator HS-DSCH Semi-Persistent scheduling operation Indicator >CHOICE configuration >>Logical Channel level

M O O

Corresponds to the Resource repetition period index field carried on HS-SCCH (see TS 25.222 [46]). Units of subframes Absence means Repetition Length equal to 1. Reserve means the HS-DSCH Semi-Persistent Resource is required to be reserved and be informed via response message.

BIT STRING (16)

>> Priority Queue level

BIT STRING (8)

Available when MAC-ehs is configured. Indicates the logical channels for which the HS-DSCH SemiPersistent operation is intended to be used. Bit 0 is for logical channel 0, Bit 1 is for logical channel 1, Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string. Indicates the Priority Queues for which the HS-DSCH SemiPersistent operation is intended to be used. Bit 0 is for priority queue 0, Bit 1 is for priority queue 1, ... Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string.

Range Bound maxnoofHS-DSCHTBSsLCR maxnoofRepetitionPeriodLCR maxnoofTBSsMapping

Explanation Maximum number of HS-DSCH Transport Block Sizes Maximum number of Repetition Period for 1.28Mcps TDD Maximum number of Transport Block Size mapping index on HSSCCH.

9.2.3.65

HS-DSCH Semi-Persistent scheduling Information to modify LCR

The HS-PSCH Semi-Persistent scheduling Information to modify LCR IE is used for the modification of HS-DSCH Semi-Persistent scheduling information for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name Transport Block Size List Presence Range 0..< maxnoofT BSsMappi ng > M INTEGER (0.. maxnoofTBSsMappi ng-1) Corresponds to the Transportblock size information field carried on HS-SCCH (see TS 25.222 [46]). IE Type and Reference Semantics Description

> Transport Block Size maping Index

3GPP

Release 11
>Transport Block Size Index M

706

3GPP TS 25.423 V11.2.0 (2012-06)

Corresponds to the TB index in the related Transport Block Size table (see TS 25.425 [32]).

INTEGER (1.. maxnoofHSDSCHTBSsLCR) 0..<maxno ofRepetitio nPeriodLC R>

Repetition Period list

>Repetition Period Index

INTEGER (0.. maxnoofRepetitionP eriodLCR) ENUMERATED (1, 2, 4, 8, 16, 32, 64,) INTEGER (1..63)) ENUMERATED(Res erve)

>Repetition Period >Repetition Length HS-DSCH Semi-Persistent Resource Reservation Indicator HS-DSCH Semi-Persistent scheduling operation Indicator >CHOICE configuration >>Logical Channel level

M O O

Corresponds to the Resource repetition period index field carried on HS-SCCH (see TS 25.222 [46]). Units of subframes Absence means Repetition Length equal to 1. Reserve means the SemiPersistent HS-DSCH Resource is required to be reserved and be informed via response message.

0..1

BIT STRING (16)

>> Priority Queue level

BIT STRING (8)

Available when MAC-ehs is configured. Indicates the logical channels for which the HS-DSCH SemiPersistent operation is intended to be used. Bit 0 is for logical channel 0, Bit1 is for logical channel 1, ... Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string. Indicates the Priority Queues for which the HS-DSCH SemiPersistent operation is intended to be used. Bit 0 is for prority queue 0, Bit1 is for priority queue 1, ... Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string.

Range Bound maxnoofHS-DSCHTBSsLCR maxnoofRepetitionPeriodLCR maxnoofTBSsMapping

Explanation Maximum number of HS-DSCH Transport Block Sizes Maximum number of Repetition Period for 1.28Mcps TDD Maximum number of Transport Block Size mapping index on HSSCCH.

9.2.3.66

E-DCH Semi-Persistent scheduling Information LCR

The E-DCH Semi-Persistent scheduling Information LCR IE defines the parameters used for E-DCH semi-Persistent scheduling for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name Repetition Period list Presence Range IE Type and Reference Semantics Description

1..<maxn

3GPP

Release 11 oofRepetit ionPeriod LCR>

>Repetition Period Index >Repetition Period >Repetition Length E-DCH Semi-Persistent scheduling Indicator M M O M

707

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER (0.. maxnoofRepetitionP eriodLCR-1) ENUMERATED (1, 2, 4, 8, 16, 32, 64,) INTEGER (1..63)) BIT STRING (16)

Units of subframes Absence means Repetition Length equal to 1. Indicates the logical channels for which the E-DCH SemiPersistent operation is intended to be used. Bit 0 is for logical channel 0, Bit1 is for logical channel 1, ... Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string. Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response message.

E-DCH Semi-Persistent Resource Reservation Indicator

ENUMERATED(Res erve)

Range Bound maxnoofRepetitionPeriodLCR

Explanation Maximum number of Repetition Period for 1.28Mcps TDD

9.2.3.67

E-DCH Semi-Persistent scheduling Information to modify LCR

The E-DCH Semi-Persistent scheduling Information to modify LCR IE is used for the modification of E-DCH SemiPersistent scheduling information for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name Repetition Period list Presence Range IE Type and Reference Semantics Description

0..<maxn oofRepetit ionPeriod LCR>

M M O O INTEGER (0.. maxnoofRepetitionP eriodLCR-1) ENUMERATED (1, 2, 4, 8, 16, 32, 64,) INTEGER (1..63)) BIT STRING (16)

>Repetition Period Index >Repetition Period >Repetition Length E-DCH Semi-Persistent scheduling Indicator

Units of subframes Absence means Repetition Length equal to 1. Indicates the logical channels for which the E-DCH SemiPersistent operation is intended to be used. Bit 0 is for logical channel 0, Bit1 is for logical channel 1, ... Value 1 for a bit means that the HS-DSCH Semi-Persistent operation is allowed. Bit 0 is the first/leftmost bit of the bit string. Reserve means the E-DCH Semi-Persistent Resource is required to be reserved and be informed via response

E-DCH Semi-Persistent Resource Reservation Indicator

ENUMERATED(Res erve)

3GPP

Release 11

708

3GPP TS 25.423 V11.2.0 (2012-06)

message.

Range Bound maxnoofRepetitionPeriodLCR

Explanation Maximum number of Repetition Period for 1.28Mcps TDD

9.2.3.68

HS-DSCH Semi-Persistent scheduling Information Response LCR

The HS-DSCH Semi-Persistent scheduling Information Response LCR IE provides information for HS-DSCH SemiPersistent scheduling determined within the Node B (see TS 25.224 [22]).
IE/Group Name HS-SICH information for HSDSCH Semi-Persistent Scheduling operation >HS-SICH mapping index >CHIOCE HS-SICH type >>HS-SCCH associated HS-SICH >>>HS-SICH ID >>Non-HS-SCCH associated HS-SICH >>>Time Slot LCR >>>Midamble shift LCR >>>TDD Channelisation Code Allcoated HS-PDSCH Semipersistent resource >Repetition Period Index >Repetition Length for HSPDSCH Semi-persistent Resouce >HS-PDSCH offset >HS-PDSCH Midamble Configuation >Timeslot Resource Related Information M Presence Range 1..< maxnoofH SSICHforS PS> INTEGER (0.. maxnoofHSSICHforSPS-1) IE Type and Reference Semantics Description

HS SICH ID 9.2.3.3ad 9.2.3.12a 9.2.3.4C 9.2.3.8 0..1

M M M

M O M M M

INTEGER (0.. maxnoofRepetitionP eriodLCR-1) INTEGER (1..63)) INTEGER (0..63)) Midamble Shift LCR 9.2.3.7A BIT STRING(5)

Absence means Repetition Length equal to 1. Units of subframes

Each bit indicates availability of a timeslot, where the bit 0 corresponds to TS2, the bit 1 is TS3, the bit 3 is TS4 bit 5 corresponds to TS6. The value 1 of a bit indicates that the corresponding timeslot is available. Bit 0 is the first/leftmost bit of the bit string.

>Start Code >End Code >Transport Block Size Index >Modulation type >HS-SICH mapping index

M M M M M

TDD Channelisation Code 9.2.3.19 TDD Channelisation Code 9.2.3.19 INTEGER (0.. maxnoofTBSsMappi ng-1) ENUMERATED (QPSK, 16QAM) INTEGER (0.. maxnoofHSSICHforSPS-1)

3GPP

Release 11
Buffer Size for HS-DSCH Semi-Persistent scheduling O

709

3GPP TS 25.423 V11.2.0 (2012-06)

Indicats the buffer size that shall be reserved for HSDSCH semi-persistent scheduling operation. 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

ENUMERATED (800..304000,)

Number of Processes for HSDSCH Semi-Persistent scheduling Range Bound maxnoofHS-SICHforSPS maxnoofTBSsMapping

INTEGER (1..16)

Explanation Maximum number of HS-SICH for HS-DSCH Semi-Persistent scheduling operation Maximum number of Transport Block Size mapping index on HSSCCH.

9.2.3.69

E-DCH Semi-Persistent scheduling Information Response LCR

The E-DCH Semi-Persistent scheduling Information Response LCR IE provides information for E-DCH SemiPersistent scheduling information determined within the Node B (see TS 25.2243 [22]).
IE/Group Name Allcoated E-DCH Semipersistent resource >Timeslot Resource Related Information LCR >Power Resource Related Information >Repetition Period Index >Repetition Length >Subframe Number Presence Range IE Type and Reference 9.2.3.54a 9.2.3.55 INTEGER (0.. maxnoofRepetitionP eriodLCR-1) INTEGER (1..63)) ENUMERATED ( 0,1) Semantics Description

0..1
M M M M M

Absence means Repetition Length equal to 1. Used to indicate from which subframe of the Radio Frame indicated by TDD E-PUCH Offset IE the physical resources are assigned to the E-DCH Non-scheduled Grant.

>TDD E-PUCH Offset >TDD Channelisation Code >NE-UCCH

M M M

9.2.3.56 9.2.3.19 INTEGER (1..8)

Number of E-UCCH and TPC instances within an E-DCH TTI. Details are described in TS 25.221 [12].

E-DCH SPS E-HICH information

0..1

3GPP

Release 11
>CHOICE E-HICH configuration >>same as scheduled E-HICH >>> EI >>explicit >>>Time Slot LCR >>>Midamble Shift LCR >>>TDD Channelisation Code >Signature Sequence Group Index M

710

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER (0..3) M M M M 9.2.3.12a 9.2.3.4C 9.2.3.8 INTEGER (0..19)

9.2.3.70

HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR

The HS-DSCH Semi-Persistent scheduling Deactivate Indicator LCR IE is used to deactivate HS-DSCH SemiPersistent scheduling operation for 1.28 Mcps TDD.
IE/Group Name HS-DSCH Semi-Persistent scheduling Deactivate Indicator Presence M Range IE Type and Reference NULL Semantics Description

9.2.3.71

E-DCH Semi-Persistent scheduling Deactivate Indicator LCR

The E-DCH Semi-Persistent scheduling Deactivate Indicator LCR IE is used to deactivate E-DCH Semi-Persistent schedulung operation for 1.28 Mcps TDD.
IE/Group Name E-DCH Semi-Persistent scheduling Deactivate Indicator Presence M Range IE Type and Reference NULL Semantics Description

9.2.3.72

HS-SICH Reference Signal Information

Presence M Range IE Type and Reference ENUMERATE D (2, 4, 6, 8, 10, 12, 14, 16, ...) INTEGER (0..15) 9.2.3.12a Semantics Description As defined in TS 25.221 [12] Criticality Assigned Criticality

IE/Group Name Midamble Configuration LCR Midamble Shift Time Slot LCR

M M

9.2.3.73

Cell Portion LCR ID

Cell Portion LCR ID is the unique identifier for a cell portion within a cell for 1.28 Mcps TDD. See TS 25.225 [14].
IE/Group Name Cell Portion LCR ID Presence Range IE Type and Reference INTEGER (0..255, ) Semantics Description

3GPP

Release 11

711

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.74

TS0 HS-PDSCH Indication LCR

Only for 1.28Mcps TDD. The TS0 HS-PDSCH Indication LCR IE indicates the first bit of timeslot information included in the HS-SCCH can be used to allocate the HS-PDSCH resources on TS0.
IE/Group Name TS0 HS-PDSCH Indication LCR Presence Range IE Type and Reference NULL Semantics Description

9.2.3.75

DCH Measurement Occasion Information

The DCH Measurement Occasion Information IE indicates Measurement Occasion Information used for interfrequency/ inter-RAT measurements in CELL_DCH state for 1.28Mcps TDD.
IE/Group Name Presence Range IE Type and Reference Semantics Description

CELL_DCH measurement occasion pattern sequence

1 to <maxD CHMeas urement Occasio nPattern Sequenc e> M Integer(1.. maxDCHMeas urementOccasi onPatternSequ ence) Enumerated(ac tivate, deactivate) This flag indicates whether the measurement occasion pattern sequence shall be activated or deactivated.
Measurement Purpose. Bit 0 is for Interfrequency measurement. Bit 1 is for GSM carrier RSSI measurement. Bit 2 is for Initial BSIC identification. Bit 3 is for BSIC reconfirmation. Bit 4 is for E-UTRA measurement.

>Pattern sequence identifier

>Status Flag

>Measurement purpose

BIT STRING (5)

The value 1 of a bit means that the measurement occasion pattern sequence is applicable for the corresponding type of measurement. Bit 0 is the first/leftmost bit of the bit string. >Measurement occasion pattern sequence parameters O

3GPP

Release 11
IE/Group Name Presence

712
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description

>>k

Integer(1..9)

CELL_DCH measurement occasion cycle length coefficient. The actual measurement occasion period equal to 2k radio frames. Value 0 indicates continuous allocation. In frames. The measurement occasion position in the measurement period. The measurement occasion length in frames starting from the Offset. Bitmap indicating which of the timeslot(s) is/are allocated for measurement. Bit 0 is for timeslot 0. Bit 1 is for timeslot 1. Bit 2 is for timeslot 2. Bit 3 is for timeslot 3. Bit 4 is for timeslot 4. Bit 5 is for timeslot 5. Bit 6 is for timeslot 6. The value 0 of a bit means the corresponding timeslot is not used for measurement. The value 1 of a bit means the corresponding timeslot is used for measurement. Bit 0 is the first/leftmost bit of the bit string.

>>Offset

Integer(0..511)

>>M_Length

Integer(1..512)

>>Timeslot Bitmap

Bit string (7)

Condition Measurementoccasionpatternsequence parameters

Explanation

The IE shall be present if Measurement occasion pattern sequence parameters IE is present.

Range Bound maxDCHMeasurementOccasionPatternSequence

Explanation

Maximum number of measurement occasion pattern sequence

9.2.3.76

DCH Measurement Type Indicator

The DCH Measurement Type Indicator IE indicates the measurement type(s) which the DRNS shall configured for the UE in CELL_DCH state for 1.28Mcps TDD.

3GPP

Release 11
IE/Group Name Presence

713
Range

3GPP TS 25.423 V11.2.0 (2012-06)

IE Type and Reference Semantics Description Measurement type. Bit 0 is for Inter-frequency measurement. Bit 1 is for GSM carrier RSSI measurement. Bit 2 is for Initial BSIC identification. Bit 3 is for BSIC reconfirmation. Bit 4 is for E-UTRA measurement.

Measurement type

BIT STRING (5)

The value 1 of a bit means that the measurement occasion pattern sequence should be configured for the corresponding type of measurement. Bit 0 is the first/leftmost bit of the bit string.

9.2.3.77

Multi-Carrier E-DCH Information LCR

The Multi-Carrier E-DCH Information LCR IE defines the parameters used for Multi-Carrier E-DCH operation for 1.28 Mcps TDD.
IE/Group Name Multi-Carrier E-DCH Information >UARFCN >SNPL Carrier Group Indicator Presence Range 1..<maxTDD1 28Carrier-1> M O 9.2.1.66 INTEGER (1..3) Corresponds to Nt (3GPP TS 25.105) Indicates to which SNPL carrier Group this frequency belongs. The absence of this IE indicates the corresponding frequency belongs to a separate SNPL carrier group which only contains this carrier. The SNPL carrier Group is defined in TS 25.331 [16]. dBm. Reference Desired RX power level for E-PUCH. Shall be ignored if bearer establishment with ALCAP. Shall be present only if the Separate Iur transport bearer mode is used. >>E-DCH MAC-d Flow ID >>Binding ID >>Transport Layer Address Range Bound maxTDD128Carrier maxnoofEDCHMACdFlows M M M 9.2.1.91 9.2.1.3 9.2.1.62 Explanation Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation Maximum number of MAC-d flows. IE Type and Reference Semantics Description

>PRXdes_base > Multi-Carrier E-DCH TDD MAC-d Flow Specific Information

M 0..<maxnoofE DCHMACdFlo ws>

INTEGER (-112..-50)

3GPP

Release 11

714

3GPP TS 25.423 V11.2.0 (2012-06)

9.2.3.78

Multi-Carrier E-DCH Information Response LCR

The Multi-Carrier E-DCH Information Response LCR IE provides information for E-DCH MAC-d flows that determined within the DRNS.
IE/Group Name Multi-Carrier E-DCH Information Response >UARFCN >E-DCH TDD MAC-d Flow Specific Information Response >>E-DCH MAC-d Flow ID >>Binding ID >>Transport Layer Address >E-AGCH Specific Information Response >>Time Slot LCR >>Midamble Shift LCR >>TDD Channelisation Code >E-HICH Scheduled specific Information Response >>EI >>Time Slot LCR >>Midamble Shift LCR >>TDD Channelisation Code Range bound maxTDD128Carrier maxnoofEDCHMACdFlows maxNoofEAGCHcodes maxNoofEHICHcodes Presence Range 1..<maxTDD1 28Carrier-1> M 0..<maxnoofE DCHMACdFlo ws> M O O 0..<maxNoOfE AGCHcodes> M M M 0..< maxNoOfEHIC Hcodes> M M M M INTEGER (0..3) 9.2.3.12a 9.2.3.4C 9.2.3.8 Explanation Maximum number of uplink frequencis in Multi-Carrier E-DCH Operation Maximum number of MAC-d flows. Maximum number of E-AGCHs assigned to one UE Maximum number of E-HICHs assigned to one UE E-HICH indication which is used to indicate UE on which E-HICH the feedback info is carried. 9.2.3.12a 9.2.3.4C 9.2.3.8 9.2.1.91 9.2.1.3 9.2.1.62 9.2.1.66 Corresponds to Nt (3GPP TS 25.105) IE Type and Reference Semantics Description

9.2.3.79

Multi-Carrier E-DCH Transport Bearer Mode LCR

This parameter indicates the Multicarrier E-DCH Transport Bearer Mode. For Multi-Carrier E-DCH Transport Bearer Mode LCR = " Separate Iur transport bearer mode" the Mac-d flows from each carrier uses different Iur transport bearers, for Multi-Carrier E-DCH Transport Bearer Mode LCR = " E-DCH UL flow multiplexing mode " the Mac-d flow received on the different carriers in the DRNS is multiplexed on one Iur transport bearer.
IE/Group Name Multicarrier E-DCH Transport Bearer Mode Presence Range IE Type and Reference ENUMERATED (Separate Iur transport bearer mode,E-DCH UL flow multiplexing mode,) Semantics Description

9.2.3.80

Cell Capability Container Extension TDD LCR

The Cell Capability Container Extension TDD LCR IE is an extension to the Cell Capability Container TDD LCR IE and indicates the cell capability in the same way as Cell Capability Container TDD LCR IE. The Cell Capability Container Extension TDD LCR IE indicates the cell capability of Multi-Carrier related functions.

3GPP

Release 11
IE/Group Name Cell Capability Container Extension TDD LCR Presence Range

715
IE Type and Reference BIT STRING (32)

3GPP TS 25.423 V11.2.0 (2012-06)

Semantics Description Each bit indicates whether a cell supports a particular functionality or not. The value 1 of a bit indicates that the corresponding functionality is supported in a cell and value 0 indicates that the corresponding functionality is not supported in a cell. Each bit is defined as follows. The first bit: Multi-Carrier E-DCH Operation Support Indicator. This bit shall be ignored by the SRNC if the second bit: Separate Iur Transport Bearer Support Indicator = 0 and the third bit: E-DCH UL Flow Multiplexing Support Indicator = 0. The second bit: Separate Iur Transport Bearer Support Indicator, /Multicarrier/. This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = 0. The third bit: E-DCH UL flow multiplexing mode Indicator, /Multicarrier/. This bit shall be ignored by the SRNC if the first bit: Multi-Carrier E-DCH Operation Support Indicator = 0. Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. Note that Reserved bits are not considered as a spare bit. They shall however be set to 0 by the transmitter and shall be ignored by the receiver.

9.2.3.81

MU-MIMO Information

The MU-MIMO Information IE defines the parameters used for MU-MIMO operation for 1.28 Mcps TDD (see TS 25.224 [22]).
IE/Group Name MU-MIMO Operation Presence M Range IE Type and Reference ENUMERATED (MU-MIMO Used, MU-MIMO Not Used) ENUMERATED (2, 4, 6, 8, 10, 12, 14, 16, ...) INTEGER (0..15) 9.2.3.12a ENUMERATED (1, 2,4, 8, 16, 32, 64) INTEGER (0..63) INTEGER (-15..16) Semantics Description

Standalone Midamble Channel Information >Standalone Midamble Configuration >Standalone Midamble Shift >Timeslot >Repetition Period >Offset >Reference Beta

0..1 M M M M M C-E-DCH As defined in TS 25.221 [12]

Units of subframes. Units of subframes. Unit range -15db to +16db

3GPP

Release 11
Condition E-DCH

716

3GPP TS 25.423 V11.2.0 (2012-06)

Explanation This IE shall be present if IE "E-DCH Information 1.28Mcps" is present. Otherwise it is not needed.

9.2.3.82

MU-MIMO Indicator

The MU-MIMO Indicator IE indicates the DRNC can use MU-MIMO on UL and/or DL. It also indicates that whether Standalone Midamble Channel should be used or not.
IE/Group Name MU-MIMO Usage Indicator Standalone Midamble Channel indicator Presence M M Range IE Type and Reference ENUMERATED (UL Only, DL Only, UL and DL) ENUMERATED (Used, Not Used) Semantics Description

9.2.3.83

M2 Report

This IE defines the parameters for a M2 report, TDD report of UE radio measurements
IE/Group Name M2 Report >CHOICE Report trigger >>Periodic >>>MDT Report Parameters >>Event1I >>>threshold Presence M M M 9.2.1.140 INTEGER(-120..-25) Range IE type and reference Semantics description

9.2.3.84

UE RF Band Capability LCR

Presence Range 1..< maxFreqB andsTDD> M ENUMERATED (a,b,c,d,e,f,g,h,i,j,k,l, m,n,o,p,) Corresponds to the radio bands definition (TS 25.105 [7]). IE Type and Reference Semantics Description

IE/Group Name UE RF Band Capability Info >UE RF Band Capability

3GPP

Release 11

717

3GPP TS 25.423 V11.2.0 (2012-06)

9.3 Message and Information Element Abstract Syntax (with ASN.1)

9.3.0 General
RNSAP ASN.1 definition conforms with ITU-T Rec. X.680 [18] and ITU-T Rec. X.681 [19]. Subclause 9.3 presents the Abstract Syntax of RNSAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this subclause and the tabular format in subclause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take precedence. The ASN.1 definition specifies the structure and content of RNSAP messages. RNSAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a RNSAP message according to the PDU definitions module and with the following additional rules: IEs shall be ordered (in an IE container) in the order they appear in object set definitions. Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value mandatory. An IE may appear at most once if the presence field in an object has value optional or conditional. If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list in which the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.

NOTE: In the above IE means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences have different IE IDs. If a RNSAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in subclause 10.3.6.

9.3.1 Usage of Private Message Mechanism for Non-standard Use

The private message mechanism for non-standard use may be used: for special operator (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor inter-operability. by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.

The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.

9.3.2 Elementary Procedure Definitions

-- **************************************************************

3GPP

Release 11
--- Elementary Procedure definitions --- **************************************************************

718

3GPP TS 25.423 V11.2.0 (2012-06)

RNSAP-PDU-Descriptions { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-PDU-Descriptions (0) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** --- IE parameter types from other modules. --- ************************************************************** IMPORTS Criticality, ProcedureID, TransactionID FROM RNSAP-CommonDataTypes CommonMeasurementFailureIndication, CommonMeasurementInitiationFailure, CommonMeasurementInitiationRequest, CommonMeasurementInitiationResponse, CommonMeasurementReport, CommonMeasurementTerminationRequest, CommonTransportChannelResourcesFailure, CommonTransportChannelResourcesRequest, CommonTransportChannelResourcesReleaseRequest, CommonTransportChannelResourcesResponseFDD, CommonTransportChannelResourcesResponseTDD, CompressedModeCommand, DedicatedMeasurementFailureIndication, DedicatedMeasurementInitiationFailure, DedicatedMeasurementInitiationRequest, DedicatedMeasurementInitiationResponse, DedicatedMeasurementReport, DedicatedMeasurementTerminationRequest, DirectInformationTransfer, DL-PowerControlRequest, DL-PowerTimeslotControlRequest, DownlinkSignallingTransferRequest, ErrorIndication, EnhancedRelocationCancel, EnhancedRelocationFailure, EnhancedRelocationRequest,

3GPP

Release 11
EnhancedRelocationResponse, EnhancedRelocationSignallingTransfer, EnhancedRelocationRelease, EnhancedRelocationResourceRequest, EnhancedRelocationResourceResponse, EnhancedRelocationResourceFailure, EnhancedRelocationResourceReleaseCommand, EnhancedRelocationResourceReleaseComplete, InformationExchangeFailureIndication, InformationExchangeInitiationFailure, InformationExchangeInitiationRequest, InformationExchangeInitiationResponse, InformationExchangeTerminationRequest, InformationReport, InformationTransferControlRequest, IurDeactivateTrace, IurInvokeTrace, MBMSAttachCommand, MBMSDetachCommand, MBSFNMCCHInformation, PagingRequest, PhysicalChannelReconfigurationCommand, PhysicalChannelReconfigurationFailure, PhysicalChannelReconfigurationRequestFDD, PhysicalChannelReconfigurationRequestTDD, PrivateMessage, RadioLinkActivationCommandFDD, RadioLinkActivationCommandTDD, RadioLinkAdditionFailureFDD, RadioLinkAdditionFailureTDD, RadioLinkAdditionRequestFDD, RadioLinkAdditionRequestTDD, RadioLinkAdditionResponseFDD, RadioLinkAdditionResponseTDD, RadioLinkCongestionIndication, RadioLinkDeletionRequest, RadioLinkDeletionResponse, RadioLinkFailureIndication, RadioLinkParameterUpdateIndicationFDD, RadioLinkParameterUpdateIndicationTDD, RadioLinkPreemptionRequiredIndication, RadioLinkReconfigurationCancel, RadioLinkReconfigurationCommit, RadioLinkReconfigurationFailure, RadioLinkReconfigurationPrepareFDD, RadioLinkReconfigurationPrepareTDD, RadioLinkReconfigurationReadyFDD, RadioLinkReconfigurationReadyTDD, RadioLinkReconfigurationRequestFDD, RadioLinkReconfigurationRequestTDD, RadioLinkReconfigurationResponseFDD,

719

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
RadioLinkReconfigurationResponseTDD, RadioLinkRestoreIndication, RadioLinkSetupFailureFDD, RadioLinkSetupFailureTDD, RadioLinkSetupRequestFDD, RadioLinkSetupRequestTDD, RadioLinkSetupResponseFDD, RadioLinkSetupResponseTDD, RelocationCommit, ResetRequest, ResetResponse, UEMeasurementFailureIndication, UEMeasurementInitiationFailure, UEMeasurementInitiationRequest, UEMeasurementInitiationResponse, UEMeasurementReport, UEMeasurementTerminationRequest, SecondaryULFrequencyReport, SecondaryULFrequencyUpdateIndication, UplinkSignallingTransferIndicationFDD, UplinkSignallingTransferIndicationTDD, GERANUplinkSignallingTransferIndication FROM RNSAP-PDU-Contents id-commonMeasurementFailure, id-commonMeasurementInitiation, id-commonMeasurementReporting, id-commonMeasurementTermination, id-commonTransportChannelResourcesInitialisation, id-commonTransportChannelResourcesRelease, id-compressedModeCommand, id-downlinkPowerControl, id-downlinkSignallingTransfer, id-downlinkPowerTimeslotControl, id-enhancedRelocation, id-enhancedRelocationCancel, id-enhancedRelocationSignallingTransfer, id-enhancedRelocationRelease, id-errorIndication, id-informationExchangeFailure, id-informationExchangeInitiation, id-informationReporting, id-informationExchangeTermination, id-informationTransferControl, id-iurDeactivateTrace, id-iurInvokeTrace, id-dedicatedMeasurementFailure, id-dedicatedMeasurementInitiation, id-dedicatedMeasurementReporting, id-dedicatedMeasurementTermination, id-directInformationTransfer,

720

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-mBMSAttach, id-mBMSDetach, id-mBSFNMCCHInformation, id-paging, id-physicalChannelReconfiguration, id-privateMessage, id-radioLinkActivation, id-radioLinkAddition, id-radioLinkCongestion, id-radioLinkDeletion, id-radioLinkFailure, id-radioLinkParameterUpdate, id-radioLinkPreemption, id-radioLinkRestoration, id-radioLinkSetup, id-relocationCommit, id-reset, id-synchronisedRadioLinkReconfigurationCancellation, id-synchronisedRadioLinkReconfigurationCommit, id-synchronisedRadioLinkReconfigurationPreparation, id-uEMeasurementFailure, id-uEMeasurementInitiation, id-uEMeasurementReporting, id-uEMeasurementTermination, id-secondaryULFrequencyReporting, id-secondaryULFrequencyUpdate, id-unSynchronisedRadioLinkReconfiguration, id-uplinkSignallingTransfer, id-gERANuplinkSignallingTransfer, id-enhancedRelocationResourceAllocation, id-enhancedRelocationResourceRelease FROM RNSAP-Constants; -- ************************************************************** --- Interface Elementary Procedure Class --- ************************************************************** RNSAP-ELEMENTARY-PROCEDURE ::= CLASS { &InitiatingMessage , &SuccessfulOutcome OPTIONAL, &UnsuccessfulOutcome OPTIONAL, &Outcome OPTIONAL, &procedureID ProcedureID UNIQUE, &criticality Criticality DEFAULT ignore } WITH SYNTAX { INITIATING MESSAGE &InitiatingMessage [SUCCESSFUL OUTCOME &SuccessfulOutcome]

721

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] [OUTCOME &Outcome] PROCEDURE ID &procedureID [CRITICALITY &criticality] } -- ************************************************************** --- Interface PDU Definition --- ************************************************************** RNSAP-PDU ::= CHOICE { initiatingMessage InitiatingMessage, successfulOutcome SuccessfulOutcome, unsuccessfulOutcome UnsuccessfulOutcome, outcome Outcome, ... }

722

3GPP TS 25.423 V11.2.0 (2012-06)

InitiatingMessage ::= SEQUENCE { procedureID RNSAP-ELEMENTARY-PROCEDURE.&procedureID ({RNSAP-ELEMENTARY-PROCEDURES}), criticality RNSAP-ELEMENTARY-PROCEDURE.&criticality ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}), transactionID TransactionID, value RNSAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}) } SuccessfulOutcome ::= SEQUENCE { procedureID RNSAP-ELEMENTARY-PROCEDURE.&procedureID ({RNSAP-ELEMENTARY-PROCEDURES}), criticality RNSAP-ELEMENTARY-PROCEDURE.&criticality ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}), transactionID TransactionID, value RNSAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}) } UnsuccessfulOutcome ::= SEQUENCE { procedureID RNSAP-ELEMENTARY-PROCEDURE.&procedureID ({RNSAP-ELEMENTARY-PROCEDURES}), criticality RNSAP-ELEMENTARY-PROCEDURE.&criticality ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}), transactionID TransactionID, value RNSAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}) } Outcome ::= SEQUENCE { procedureID RNSAP-ELEMENTARY-PROCEDURE.&procedureID ({RNSAP-ELEMENTARY-PROCEDURES}), criticality RNSAP-ELEMENTARY-PROCEDURE.&criticality ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}), transactionID TransactionID, value RNSAP-ELEMENTARY-PROCEDURE.&Outcome ({RNSAP-ELEMENTARY-PROCEDURES}{@procedureID}) } -- ************************************************************** --- Interface Elementary Procedure List

3GPP

Release 11
--- ************************************************************** RNSAP-ELEMENTARY-PROCEDURES RNSAP-ELEMENTARY-PROCEDURE ::= { RNSAP-ELEMENTARY-PROCEDURES-CLASS-1 | RNSAP-ELEMENTARY-PROCEDURES-CLASS-2 | RNSAP-ELEMENTARY-PROCEDURES-CLASS-3 , ... } RNSAP-ELEMENTARY-PROCEDURES-CLASS-1 RNSAP-ELEMENTARY-PROCEDURE ::= { radioLinkSetupFDD | radioLinkSetupTDD | radioLinkAdditionFDD | radioLinkAdditionTDD | radioLinkDeletion | synchronisedRadioLinkReconfigurationPreparationFDD | synchronisedRadioLinkReconfigurationPreparationTDD | unSynchronisedRadioLinkReconfigurationFDD | unSynchronisedRadioLinkReconfigurationTDD | physicalChannelReconfigurationFDD | physicalChannelReconfigurationTDD | dedicatedMeasurementInitiation | commonTransportChannelResourcesInitialisationFDD | commonTransportChannelResourcesInitialisationTDD , ..., commonMeasurementInitiation | informationExchangeInitiation | reset | uEMeasurementInitiation | enhancedRelocation | enhancedRelocationResourceAllocation | enhancedRelocationResourceRelease } RNSAP-ELEMENTARY-PROCEDURES-CLASS-2 RNSAP-ELEMENTARY-PROCEDURE ::= { uplinkSignallingTransferFDD | uplinkSignallingTransferTDD | downlinkSignallingTransfer | relocationCommit | paging | synchronisedRadioLinkReconfigurationCommit | synchronisedRadioLinkReconfigurationCancellation | radioLinkFailure | radioLinkPreemption | radioLinkRestoration | dedicatedMeasurementReporting | dedicatedMeasurementTermination | dedicatedMeasurementFailure | downlinkPowerControlFDD | downlinkPowerTimeslotControl |

723

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
compressedModeCommandFDD commonTransportChannelResourcesRelease errorIndication privateMessage ..., radioLinkCongestion commonMeasurementFailure commonMeasurementReporting commonMeasurementTermination informationExchangeFailure informationExchangeTermination informationReporting radioLinkActivationFDD radioLinkActivationTDD gERANuplinkSignallingTransfer radioLinkParameterUpdateFDD radioLinkParameterUpdateTDD uEMeasurementReporting uEMeasurementTermination uEMeasurementFailure iurInvokeTrace iurDeactivateTrace mBMSAttach mBMSDetach directInformationTransfer enhancedRelocationCancel enhancedRelocationSignallingTransfer enhancedRelocationRelease mBSFNMCCHInformation secondaryULFrequencyReportingFDD secondaryULFrequencyUpdateFDD informationTransferControl | | | , | | | | | | | | | | | | | | | | | | | | | | | | | |

724

3GPP TS 25.423 V11.2.0 (2012-06)

} RNSAP-ELEMENTARY-PROCEDURES-CLASS-3 RNSAP-ELEMENTARY-PROCEDURE ::= { ... } -- ************************************************************** --- Interface Elementary Procedures --- ************************************************************** radioLinkSetupFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkSetupRequestFDD SUCCESSFUL OUTCOME RadioLinkSetupResponseFDD

3GPP

Release 11
UNSUCCESSFUL OUTCOME RadioLinkSetupFailureFDD PROCEDURE ID { procedureCode id-radioLinkSetup, ddMode fdd } CRITICALITY reject

725

3GPP TS 25.423 V11.2.0 (2012-06)

radioLinkSetupTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkSetupRequestTDD SUCCESSFUL OUTCOME RadioLinkSetupResponseTDD UNSUCCESSFUL OUTCOME RadioLinkSetupFailureTDD PROCEDURE ID { procedureCode id-radioLinkSetup, ddMode tdd } CRITICALITY reject } radioLinkAdditionFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkAdditionRequestFDD SUCCESSFUL OUTCOME RadioLinkAdditionResponseFDD UNSUCCESSFUL OUTCOME RadioLinkAdditionFailureFDD PROCEDURE ID { procedureCode id-radioLinkAddition , ddMode fdd } CRITICALITY reject } radioLinkAdditionTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkAdditionRequestTDD SUCCESSFUL OUTCOME RadioLinkAdditionResponseTDD UNSUCCESSFUL OUTCOME RadioLinkAdditionFailureTDD PROCEDURE ID { procedureCode id-radioLinkAddition , ddMode tdd } CRITICALITY reject } radioLinkDeletion RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkDeletionRequest SUCCESSFUL OUTCOME RadioLinkDeletionResponse PROCEDURE ID { procedureCode id-radioLinkDeletion, ddMode common } CRITICALITY reject } synchronisedRadioLinkReconfigurationPreparationFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationPrepareFDD SUCCESSFUL OUTCOME RadioLinkReconfigurationReadyFDD UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationPreparation, ddMode fdd } CRITICALITY reject } synchronisedRadioLinkReconfigurationPreparationTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationPrepareTDD SUCCESSFUL OUTCOME RadioLinkReconfigurationReadyTDD UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationPreparation, ddMode tdd } CRITICALITY reject }

3GPP

Release 11

726

3GPP TS 25.423 V11.2.0 (2012-06)

unSynchronisedRadioLinkReconfigurationFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationRequestFDD SUCCESSFUL OUTCOME RadioLinkReconfigurationResponseFDD UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure PROCEDURE ID { procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode fdd } CRITICALITY reject } unSynchronisedRadioLinkReconfigurationTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationRequestTDD SUCCESSFUL OUTCOME RadioLinkReconfigurationResponseTDD UNSUCCESSFUL OUTCOME RadioLinkReconfigurationFailure PROCEDURE ID { procedureCode id-unSynchronisedRadioLinkReconfiguration, ddMode tdd } CRITICALITY reject } physicalChannelReconfigurationFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PhysicalChannelReconfigurationRequestFDD SUCCESSFUL OUTCOME PhysicalChannelReconfigurationCommand UNSUCCESSFUL OUTCOME PhysicalChannelReconfigurationFailure PROCEDURE ID { procedureCode id-physicalChannelReconfiguration, ddMode fdd } CRITICALITY reject } physicalChannelReconfigurationTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PhysicalChannelReconfigurationRequestTDD SUCCESSFUL OUTCOME PhysicalChannelReconfigurationCommand UNSUCCESSFUL OUTCOME PhysicalChannelReconfigurationFailure PROCEDURE ID { procedureCode id-physicalChannelReconfiguration, ddMode tdd } CRITICALITY reject } dedicatedMeasurementInitiation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DedicatedMeasurementInitiationRequest SUCCESSFUL OUTCOME DedicatedMeasurementInitiationResponse UNSUCCESSFUL OUTCOME DedicatedMeasurementInitiationFailure PROCEDURE ID { procedureCode id-dedicatedMeasurementInitiation, ddMode common } CRITICALITY reject } commonTransportChannelResourcesInitialisationFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonTransportChannelResourcesRequest SUCCESSFUL OUTCOME CommonTransportChannelResourcesResponseFDD UNSUCCESSFUL OUTCOME CommonTransportChannelResourcesFailure PROCEDURE ID { procedureCode id-commonTransportChannelResourcesInitialisation, ddMode fdd } CRITICALITY reject } commonTransportChannelResourcesInitialisationTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonTransportChannelResourcesRequest

3GPP

Release 11

727

3GPP TS 25.423 V11.2.0 (2012-06)

SUCCESSFUL OUTCOME CommonTransportChannelResourcesResponseTDD UNSUCCESSFUL OUTCOME CommonTransportChannelResourcesFailure PROCEDURE ID { procedureCode id-commonTransportChannelResourcesInitialisation, ddMode tdd } CRITICALITY reject } uplinkSignallingTransferFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UplinkSignallingTransferIndicationFDD PROCEDURE ID { procedureCode id-uplinkSignallingTransfer, ddMode fdd } CRITICALITY ignore } uplinkSignallingTransferTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UplinkSignallingTransferIndicationTDD PROCEDURE ID { procedureCode id-uplinkSignallingTransfer, ddMode tdd } CRITICALITY ignore } downlinkSignallingTransfer RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DownlinkSignallingTransferRequest PROCEDURE ID { procedureCode id-downlinkSignallingTransfer, ddMode common } CRITICALITY ignore } relocationCommit RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RelocationCommit PROCEDURE ID { procedureCode id-relocationCommit, ddMode common } CRITICALITY ignore } paging RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PagingRequest PROCEDURE ID { procedureCode id-paging, ddMode common } CRITICALITY ignore } synchronisedRadioLinkReconfigurationCommit RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationCommit PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationCommit, ddMode common } CRITICALITY ignore } synchronisedRadioLinkReconfigurationCancellation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkReconfigurationCancel PROCEDURE ID { procedureCode id-synchronisedRadioLinkReconfigurationCancellation, ddMode common } CRITICALITY ignore } radioLinkFailure RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkFailureIndication PROCEDURE ID { procedureCode id-radioLinkFailure, ddMode common }

3GPP

Release 11
} CRITICALITY ignore

728

3GPP TS 25.423 V11.2.0 (2012-06)

radioLinkPreemption RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkPreemptionRequiredIndication PROCEDURE ID { procedureCode id-radioLinkPreemption, ddMode common } CRITICALITY ignore } radioLinkRestoration RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkRestoreIndication PROCEDURE ID { procedureCode id-radioLinkRestoration, ddMode common } CRITICALITY ignore } dedicatedMeasurementReporting RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DedicatedMeasurementReport PROCEDURE ID { procedureCode id-dedicatedMeasurementReporting, ddMode common } CRITICALITY ignore } dedicatedMeasurementTermination RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DedicatedMeasurementTerminationRequest PROCEDURE ID { procedureCode id-dedicatedMeasurementTermination, ddMode common } CRITICALITY ignore } dedicatedMeasurementFailure RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DedicatedMeasurementFailureIndication PROCEDURE ID { procedureCode id-dedicatedMeasurementFailure, ddMode common } CRITICALITY ignore } radioLinkCongestion RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkCongestionIndication PROCEDURE ID { procedureCode id-radioLinkCongestion, ddMode common } CRITICALITY ignore } downlinkPowerControlFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DL-PowerControlRequest PROCEDURE ID { procedureCode id-downlinkPowerControl, ddMode fdd } CRITICALITY ignore } downlinkPowerTimeslotControl RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DL-PowerTimeslotControlRequest PROCEDURE ID { procedureCode id-downlinkPowerTimeslotControl, ddMode tdd } CRITICALITY ignore }

3GPP

Release 11

729

3GPP TS 25.423 V11.2.0 (2012-06)

compressedModeCommandFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CompressedModeCommand PROCEDURE ID { procedureCode id-compressedModeCommand, ddMode fdd } CRITICALITY ignore } commonTransportChannelResourcesRelease RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonTransportChannelResourcesReleaseRequest PROCEDURE ID { procedureCode id-commonTransportChannelResourcesRelease, ddMode common } CRITICALITY ignore } errorIndication RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ErrorIndication PROCEDURE ID { procedureCode id-errorIndication, ddMode common } CRITICALITY ignore } commonMeasurementInitiation INITIATING MESSAGE SUCCESSFUL OUTCOME UNSUCCESSFUL OUTCOME PROCEDURE ID CRITICALITY } RNSAP-ELEMENTARY-PROCEDURE ::= { CommonMeasurementInitiationRequest CommonMeasurementInitiationResponse CommonMeasurementInitiationFailure { procedureCode id-commonMeasurementInitiation, ddMode common } reject

commonMeasurementReporting RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonMeasurementReport PROCEDURE ID { procedureCode id-commonMeasurementReporting, ddMode common } CRITICALITY ignore } commonMeasurementTermination RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonMeasurementTerminationRequest PROCEDURE ID { procedureCode id-commonMeasurementTermination, ddMode common } CRITICALITY ignore } commonMeasurementFailure RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE CommonMeasurementFailureIndication PROCEDURE ID { procedureCode id-commonMeasurementFailure, ddMode common } CRITICALITY ignore } informationExchangeInitiation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InformationExchangeInitiationRequest SUCCESSFUL OUTCOME InformationExchangeInitiationResponse UNSUCCESSFUL OUTCOME InformationExchangeInitiationFailure PROCEDURE ID { procedureCode id-informationExchangeInitiation, ddMode common } CRITICALITY reject }

3GPP

Release 11

730

3GPP TS 25.423 V11.2.0 (2012-06)

informationReporting RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InformationReport PROCEDURE ID { procedureCode id-informationReporting, ddMode common } CRITICALITY ignore } informationExchangeTermination RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InformationExchangeTerminationRequest PROCEDURE ID { procedureCode id-informationExchangeTermination, ddMode common } CRITICALITY ignore } informationExchangeFailure RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InformationExchangeFailureIndication PROCEDURE ID { procedureCode id-informationExchangeFailure, ddMode common } CRITICALITY ignore } privateMessage RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PrivateMessage PROCEDURE ID { procedureCode id-privateMessage, ddMode common } CRITICALITY ignore } reset RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ResetRequest SUCCESSFUL OUTCOME ResetResponse PROCEDURE ID { procedureCode id-reset, ddMode common } CRITICALITY reject } radioLinkActivationFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkActivationCommandFDD PROCEDURE ID { procedureCode id-radioLinkActivation, ddMode fdd } CRITICALITY ignore } radioLinkActivationTDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RadioLinkActivationCommandTDD PROCEDURE ID { procedureCode id-radioLinkActivation, ddMode tdd } CRITICALITY ignore } gERANuplinkSignallingTransfer RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE GERANUplinkSignallingTransferIndication PROCEDURE ID { procedureCode id-gERANuplinkSignallingTransfer, ddMode common } CRITICALITY ignore }

3GPP

Release 11
radioLinkParameterUpdateFDD INITIATING MESSAGE PROCEDURE ID CRITICALITY } radioLinkParameterUpdateTDD INITIATING MESSAGE PROCEDURE ID CRITICALITY }

731
RNSAP-ELEMENTARY-PROCEDURE ::= { RadioLinkParameterUpdateIndicationFDD { procedureCode id-radioLinkParameterUpdate, ddMode fdd } ignore RNSAP-ELEMENTARY-PROCEDURE ::= { RadioLinkParameterUpdateIndicationTDD { procedureCode id-radioLinkParameterUpdate, ddMode tdd } ignore

3GPP TS 25.423 V11.2.0 (2012-06)

uEMeasurementInitiation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEMeasurementInitiationRequest SUCCESSFUL OUTCOME UEMeasurementInitiationResponse UNSUCCESSFUL OUTCOME UEMeasurementInitiationFailure PROCEDURE ID { procedureCode id-uEMeasurementInitiation, ddMode tdd } CRITICALITY reject } uEMeasurementReporting RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEMeasurementReport PROCEDURE ID { procedureCode id-uEMeasurementReporting, ddMode tdd } CRITICALITY ignore } uEMeasurementTermination RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEMeasurementTerminationRequest PROCEDURE ID { procedureCode id-uEMeasurementTermination, ddMode tdd } CRITICALITY ignore } uEMeasurementFailure RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE UEMeasurementFailureIndication PROCEDURE ID { procedureCode id-uEMeasurementFailure, ddMode tdd } CRITICALITY ignore } iurInvokeTrace RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE IurInvokeTrace PROCEDURE ID { procedureCode id-iurInvokeTrace, ddMode common } CRITICALITY ignore } iurDeactivateTrace RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE IurDeactivateTrace PROCEDURE ID { procedureCode id-iurDeactivateTrace, ddMode common } CRITICALITY ignore } mBMSAttach RNSAP-ELEMENTARY-PROCEDURE ::= {

3GPP

Release 11
INITIATING MESSAGE PROCEDURE ID CRITICALITY MBMSAttachCommand { procedureCode id-mBMSAttach, ddMode common } ignore

732

3GPP TS 25.423 V11.2.0 (2012-06)

mBMSDetach RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE MBMSDetachCommand PROCEDURE ID { procedureCode id-mBMSDetach, ddMode common } CRITICALITY ignore } directInformationTransfer RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DirectInformationTransfer PROCEDURE ID { procedureCode id-directInformationTransfer, ddMode common } CRITICALITY ignore } enhancedRelocation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationRequest SUCCESSFUL OUTCOME EnhancedRelocationResponse UNSUCCESSFUL OUTCOME EnhancedRelocationFailure PROCEDURE ID { procedureCode id-enhancedRelocation, ddMode common } CRITICALITY reject } enhancedRelocationCancel RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationCancel PROCEDURE ID { procedureCode id-enhancedRelocationCancel, ddMode common } CRITICALITY ignore } enhancedRelocationSignallingTransfer RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationSignallingTransfer PROCEDURE ID { procedureCode id-enhancedRelocationSignallingTransfer, ddMode common } CRITICALITY ignore } enhancedRelocationRelease RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationRelease PROCEDURE ID { procedureCode id-enhancedRelocationRelease, ddMode common } CRITICALITY ignore } mBSFNMCCHInformation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE MBSFNMCCHInformation PROCEDURE ID { procedureCode id-mBSFNMCCHInformation, ddMode common } CRITICALITY reject } secondaryULFrequencyReportingFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SecondaryULFrequencyReport

3GPP

Release 11
PROCEDURE ID CRITICALITY }

733
{ procedureCode id-secondaryULFrequencyReporting, ddMode fdd } ignore

3GPP TS 25.423 V11.2.0 (2012-06)

secondaryULFrequencyUpdateFDD RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE SecondaryULFrequencyUpdateIndication PROCEDURE ID { procedureCode id-secondaryULFrequencyUpdate, ddMode fdd } CRITICALITY ignore } enhancedRelocationResourceAllocation RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationResourceRequest SUCCESSFUL OUTCOME EnhancedRelocationResourceResponse UNSUCCESSFUL OUTCOME EnhancedRelocationResourceFailure PROCEDURE ID { procedureCode id-enhancedRelocationResourceAllocation, ddMode tdd } CRITICALITY reject } enhancedRelocationResourceRelease RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE EnhancedRelocationResourceReleaseCommand SUCCESSFUL OUTCOME EnhancedRelocationResourceReleaseComplete PROCEDURE ID { procedureCode id-enhancedRelocationResourceRelease, ddMode tdd } CRITICALITY reject } informationTransferControl RNSAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE InformationTransferControlRequest PROCEDURE ID { procedureCode id-informationTransferControl, ddMode common } CRITICALITY ignore } END

9.3.3 PDU Definitions

-- ************************************************************** --- PDU definitions for RNSAP. --- ************************************************************** RNSAP-PDU-Contents { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-PDU-Contents (1) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** --

3GPP

Release 11
-- IE parameter types from other modules. --- ************************************************************** IMPORTS Active-Pattern-Sequence-Information, Active-MBMS-Bearer-Service-ListFDD, Active-MBMS-Bearer-Service-ListFDD-PFL, Active-MBMS-Bearer-Service-ListTDD, Active-MBMS-Bearer-Service-ListTDD-PFL, AllocationRetentionPriority, AllowedQueuingTime, Allowed-Rate-Information, AlphaValue, AlternativeFormatReportingIndicator, AntennaColocationIndicator, BLER, SCTD-Indicator, BindingID, C-ID, C-RNTI, CCTrCH-ID, CFN, CGI, ClosedLoopMode1-SupportIndicator, Closedlooptimingadjustmentmode, CN-CS-DomainIdentifier, CN-PS-DomainIdentifier, CNDomainType, Cause, CellCapabilityContainer-FDD, CellCapabilityContainerExtension-FDD, CellCapabilityContainer-TDD, CellCapabilityContainer-TDD-LCR, CellCapabilityContainer-TDD768, CellParameterID, CellPortionID, ChipOffset, CommonMeasurementAccuracy, CommonMeasurementType, CommonMeasurementValue, CommonMeasurementValueInformation, CommonTransportChannelResourcesInitialisationNotRequired, Common-EDCH-MAC-d-Flow-Specific-InformationFDD, Common-EDCH-Support-Indicator, CongestionCause, Continuous-Packet-Connectivity-DTX-DRX-Information, Continuous-Packet-Connectivity-HS-SCCH-Less-Information, Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response, CPC-Information, CoverageIndicator,

734

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
CriticalityDiagnostics, CellPortionLCRID, D-RNTI, D-RNTI-ReleaseIndication, DCH-FDD-Information, DCH-ID, DCH-Indicator-For-E-DCH-HSDPA-Operation, DPCH-ID768, DCH-InformationResponse, DCH-TDD-Information, DL-DPCH-SlotFormat, DL-TimeslotISCP, DL-Power, DL-PowerBalancing-Information, DL-PowerBalancing-ActivationIndicator, DL-PowerBalancing-UpdatedIndicator, DL-ReferencePowerInformation, DL-ScramblingCode, DL-Timeslot-Information, DL-Timeslot-Information768, DL-TimeslotLCR-Information, DL-TimeSlot-ISCP-Info, DL-TimeSlot-ISCP-LCR-Information, DPC-Mode, DPC-Mode-Change-SupportIndicator, DPCH-ID, DL-DPCH-TimingAdjustment, DRXCycleLengthCoefficient, DedicatedMeasurementType, DedicatedMeasurementValue, DedicatedMeasurementValueInformation, DelayedActivation, DelayedActivationUpdate, DiversityControlField, DiversityMode, DSCH-FlowControlInformation, DSCH-FlowControlItem, DSCH-TDD-Information, DSCH-ID, DSCH-RNTI, EDCH-FDD-Information, EDCH-FDD-InformationResponse, EDCH-FDD-Information-To-Modify, EDCH-FDD-DL-ControlChannelInformation, EDCH-DDI-Value, EDCH-MACdFlow-ID, EDCH-MACdFlow-Specific-InfoList, EDCH-MACdFlows-To-Delete, EDCH-MACdFlows-Information, EDCH-RL-Indication, EDCH-Serving-RL,

735

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
E-DCH-Serving-cell-change-informationResponse, EDPCH-Information-FDD, EDPCH-Information-RLReconfPrepare-FDD, EDPCH-Information-RLReconfRequest-FDD, E-DCH-FDD-Update-Information, E-DPCCH-PO, E-RGCH-2-IndexStepThreshold, E-RGCH-3-IndexStepThreshold, E-RNTI, E-TFCS-Information, E-TTI, Enhanced-FACH-Support-Indicator, Enhanced-FACH-Information-ResponseFDD, Enhanced-PCH-Capability, ExtendedPropagationDelay, Extended-RNC-ID, Extended-RNTI, Extended-S-RNTI-Group, SchedulingPriorityIndicator, Enhanced-PrimaryCPICH-EcNo, F-DPCH-SlotFormat, F-DPCH-SlotFormatSupportRequest, FACH-FlowControlInformation, Fast-Reconfiguration-Mode, Fast-Reconfiguration-Permission, FDD-DCHs-to-Modify, FDD-DL-ChannelisationCodeNumber, FDD-DL-CodeInformation, FDD-TPC-DownlinkStepSize, FirstRLS-Indicator, FNReportingIndicator, FrameHandlingPriority, FrameOffset, GA-AccessPointPosition, GA-Cell, GA-CellAdditionalShapes, HARQ-Info-for-E-DCH, HCS-Prio, HSDSCH-Configured-Indicator, HSDSCH-FDD-Information, HSDSCH-FDD-Information-Response, HSDSCH-FDD-Update-Information, HSDSCH-TDD-Update-Information, HSDSCH-Information-to-Modify, HSDSCH-Information-to-Modify-Unsynchronised, HSDSCH-MACdFlow-ID, HSDSCH-MACdFlows-Information, HSDSCH-MACdFlows-to-Delete, HSDSCH-Physical-Layer-Category, HSDSCH-RNTI, HS-DSCH-serving-cell-change-information,

736

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
HS-DSCH-serving-cell-change-informationResponse, HSDSCH-TDD-Information, HSDSCH-TDD-Information-Response, HS-SICH-ID, IMSI, InformationExchangeID, InformationReportCharacteristics, InformationType, Initial-DL-DPCH-TimingAdjustment-Allowed, InnerLoopDLPCStatus, Inter-Frequency-Cell-List, L3-Information, LimitedPowerIncrease, MaximumAllowedULTxPower, MaxNrDLPhysicalchannels, MaxNrDLPhysicalchannelsTS, MaxNrDLPhysicalchannels768, MaxNrDLPhysicalchannelsTS768, MaxNrOfUL-DPCHs, MaxNrTimeslots, MaxNrULPhysicalchannels, MACes-Guaranteed-Bitrate, MaxNr-Retransmissions-EDCH, Max-Set-E-DPDCHs, Max-UE-DTX-Cycle, MeasurementFilterCoefficient, MeasurementID, MeasurementRecoveryBehavior, MeasurementRecoveryReportingIndicator, MeasurementRecoverySupportIndicator, MBMS-Bearer-Service-List, MBSFN-Cluster-Identity, MCCH-Configuration-Info, MCCH-Message-List, MBSFN-Scheduling-Transmission-Time-Interval-Info-List, MidambleAllocationMode, MidambleShiftAndBurstType, MidambleShiftAndBurstType768, MidambleShiftLCR, MinimumSpreadingFactor, MinimumSpreadingFactor768, MinUL-ChannelisationCodeLength, Multiple-PLMN-List, MultiplexingPosition, NeighbouringFDDCellMeasurementInformation, NeighbouringTDDCellMeasurementInformation, NeighbouringTDDCellMeasurementInformation768, Neighbouring-GSM-CellInformation, Neighbouring-UMTS-CellInformation, NeighbouringTDDCellMeasurementInformationLCR, Neighbouring-E-UTRA-CellInformation,

737

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
NrOfDLchannelisationcodes, PagingCause, PagingRecordType, PartialReportingIndicator, PayloadCRC-PresenceIndicator, PCCPCH-Power, PC-Preamble, Permanent-NAS-UE-Identity, Phase-Reference-Update-Indicator, PowerAdjustmentType, PowerOffset, PrimaryCCPCH-RSCP, PrimaryCPICH-EcNo, PrimaryCPICH-Power, Primary-CPICH-Usage-For-Channel-Estimation, PrimaryScramblingCode, PropagationDelay, ProvidedInformation, PunctureLimit, QE-Selector, RANAP-EnhancedRelocationInformationRequest, RANAP-EnhancedRelocationInformationResponse, RANAP-RelocationInformation, RB-Info, Released-CN-Domain, RL-ID, RL-Set-ID, RL-Specific-EDCH-Information, RNC-ID, RepetitionLength, RepetitionPeriod, ReportCharacteristics, Received-total-wide-band-power, RequestedDataValue, RequestedDataValueInformation, RxTimingDeviationForTA, RxTimingDeviationForTA768, S-RNTI, S-RNTI-Group, SCH-TimeSlot, SAI, SFN, Secondary-CCPCH-Info-TDD, Secondary-CCPCH-Info-TDD768, Secondary-CCPCH-System-Information-MBMS, Secondary-CPICH-Information, Secondary-CPICH-Information-Change, Secondary-LCR-CCPCH-Info-TDD, Secondary-Serving-Cell-List, SNA-Information, SpecialBurstScheduling,

738

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
SSDT-SupportIndicator, STTD-SupportIndicator, AdjustmentPeriod, ScaledAdjustmentRatio, MaxAdjustmentStep, SRB-Delay, Support-8PSK, SyncCase, SynchronisationConfiguration, SixtyfourQAM-DL-SupportIndicator, TDD-ChannelisationCode, TDD-ChannelisationCode768, TDD-DCHs-to-Modify, TDD-DL-Code-Information, TDD-DPCHOffset, TDD-PhysicalChannelOffset, TDD-TPC-DownlinkStepSize, TDD-ChannelisationCodeLCR, TDD-DL-Code-LCR-Information, TDD-DL-Code-Information768, TDD-UL-Code-Information, TDD-UL-Code-LCR-Information, TDD-UL-Code-Information768, TFCI-Coding, TFCI-Presence, TFCI-SignallingMode, TimeSlot, TimeSlotLCR, TimingAdvanceApplied, TMGI, TnlQos, ToAWE, ToAWS, TraceDepth, TraceRecordingSessionReference, TraceReference, TrafficClass, TransmitDiversityIndicator, TransportBearerID, TransportBearerRequestIndicator, TFCS, Transmission-Gap-Pattern-Sequence-Information, TransportFormatManagement, TransportFormatSet, TransportLayerAddress, TrCH-SrcStatisticsDescr, TSTD-Indicator, TSTD-Support-Indicator, UARFCN, UC-ID, UE-AggregateMaximumBitRate,

739

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
UEIdentity, UEMeasurementType, UEMeasurementTimeslotInfoHCR, UEMeasurementTimeslotInfoLCR, UEMeasurementTimeslotInfo768, UEMeasurementReportCharacteristics, UEMeasurementParameterModAllow, UEMeasurementValueInformation, UE-State, UL-DPCCH-SlotFormat, UL-DPDCHIndicatorEDCH, UL-SIR, UL-FP-Mode, UL-PhysCH-SF-Variation, UL-ScramblingCode, UL-Timeslot-Information, UL-Timeslot-Information768, UL-TimeslotLCR-Information, UL-TimeSlot-ISCP-Info, UL-TimeSlot-ISCP-LCR-Info, URA-ID, URA-Information, USCH-ID, USCH-Information, UL-Synchronisation-Parameters-LCR, TDD-DL-DPCH-TimeSlotFormat-LCR, TDD-UL-DPCH-TimeSlotFormat-LCR, MAChs-ResetIndicator, UL-TimingAdvanceCtrl-LCR, TDD-TPC-UplinkStepSize-LCR, PrimaryCCPCH-RSCP-Delta, SynchronisationIndicator, Support-PLCCH, PLCCHinformation, RxTimingDeviationForTAext, E-DCH-Information, E-DCH-Information-Reconfig, E-DCH-Information-Response, E-DCH-768-Information, E-DCH-768-Information-Reconfig, E-DCH-768-Information-Response, E-DCH-LCR-Information, E-DCH-LCR-Information-Reconfig, E-DCH-LCR-Information-Response, ControlGAP, IdleIntervalInformation, NeedforIdleInterval, HS-SICH-ID-Extension, TSN-Length, UPPCHPositionLCR, Common-EDCH-MAC-d-Flow-Specific-InformationLCR,

740

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11

741

3GPP TS 25.423 V11.2.0 (2012-06)

Enhanced-FACH-Information-ResponseLCR, HSDSCH-PreconfigurationSetup, HSDSCH-PreconfigurationInfo, NoOfTargetCellHS-SCCH-Order, EnhancedHSServingCC-Abort, GANSS-Time-ID, HS-DSCH-FDD-Secondary-Serving-Update-Information, HS-DSCH-Secondary-Serving-Remove, HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised, HS-DSCH-Secondary-Serving-Information-To-Modify, HS-DSCH-Secondary-Serving-Cell-Change-Information-Response, HS-DSCH-FDD-Secondary-Serving-Information-Response, HS-DSCH-FDD-Secondary-Serving-Information, MinimumReducedE-DPDCH-GainFactor, ContinuousPacketConnectivity-DRX-InformationLCR, ContinuousPacketConnectivity-DRX-Information-ResponseLCR, CPC-InformationLCR, E-DCH-Semi-PersistentScheduling-Information-LCR, HS-DSCH-Semi-PersistentScheduling-Information-LCR, HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR, E-DCH-Semi-PersistentScheduling-Information-ResponseLCR, RNTI-Allocation-Indicator, ActivationInformation, Additional-EDCH-Setup-Info, Additional-EDCH-Cell-Information-Response-List, Additional-EDCH-FDD-Update-Information, Additional-EDCH-Cell-Information-To-Add-List, Additional-EDCH-Cell-Information-Response-RLReconf-List, DCH-MeasurementOccasion-Information, DCH-MeasurementType-Indicator, Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency, Additional-EDCH-Cell-Information-Response-RLAddList, Non-Serving-RL-Preconfig-Setup, Non-Serving-RL-Preconfig-Info, CellCapabilityContainerExtension-TDD-LCR, Multi-Carrier-EDCH-Info, Multi-Carrier-EDCH-Reconfigure, Multi-Carrier-EDCH-Information-Response, MU-MIMO-InformationLCR, MU-MIMO-Indicator, Usefulness-Of-Battery-Optimization, MDT-Configuration, Neighbouring-UMTS-CellInformation-Ext, SourceID, TargetID, ClassmarkInformation2, ClassmarkInformation3, SpeechVersion, Cell-Capacity-Class-Value, LoadValue, Controlled-Object-Scope,

3GPP

Release 11
CPC-RecoveryReport, UL-CLTD-Information, UL-CLTD-Information-Reconf, UL-CLTD-State-Update-Information, FTPICH-Information, FTPICH-Information-Reconf

742

3GPP TS 25.423 V11.2.0 (2012-06)

FROM RNSAP-IEs PrivateIE-Container{}, ProtocolExtensionContainer{}, ProtocolIE-ContainerList{}, ProtocolIE-ContainerPair{}, ProtocolIE-ContainerPairList{}, ProtocolIE-Container{}, ProtocolIE-Single-Container{}, RNSAP-PRIVATE-IES, RNSAP-PROTOCOL-EXTENSION, RNSAP-PROTOCOL-IES, RNSAP-PROTOCOL-IES-PAIR FROM RNSAP-Containers maxCellsMeas, maxNoOfDSCHs, maxNoOfUSCHs, maxNrOfCCTrCHs, maxNrOfDCHs, maxNrOfTS, maxNrOfDPCHs, maxNrOfDPCHs768, maxNrOfDPCHsPerRL-1, maxNrOfDPCHs768PerRL-1, maxNrOfInterfaces, maxNrOfRLs, maxNrOfRLSets, maxNrOfRLSets-1, maxNrOfRLs-1, maxNrOfRLs-2, maxNrOfULTs, maxNrOfDLTs, maxResetContext, maxResetContextGroup, maxNoOfDSCHsLCR, maxNoOfUSCHsLCR, maxNrOfCCTrCHsLCR, maxNrOfTsLCR, maxNrOfDLTsLCR, maxNrOfULTsLCR, maxNrOfDPCHsLCR,

3GPP

Release 11
maxNrOfDPCHsLCRPerRL-1, maxNrOfLCRTDDNeighboursPerRNC, maxNrOfMeasNCell, maxNrOfMACdFlows, maxNrOfMACdPDUSize, maxNrOfMCCHMessages, maxNrOfMBMSL3, maxNrOfEDCHMACdFlows, maxNrOfMBMSServices, maxNrOfCells, maxNrOfHSDSCH-1, maxNrOfEDCH-1, maxNrOfULCarriersLCR-1, maxNoOfGsmCell, maxNrOfANRCells, id-Active-MBMS-Bearer-ServiceFDD, id-Active-MBMS-Bearer-ServiceFDD-PFL, id-Active-MBMS-Bearer-ServiceTDD, id-Active-MBMS-Bearer-ServiceTDD-PFL, id-Active-Pattern-Sequence-Information, id-AdjustmentRatio, id-AllowedQueuingTime, id-AlternativeFormatReportingIndicator, id-AntennaColocationIndicator, id-BindingID, id-C-ID, id-C-RNTI, id-CFN, id-CFNReportingIndicator, id-CN-CS-DomainIdentifier, id-CN-PS-DomainIdentifier, id-Cause, id-CauseLevel-RL-AdditionFailureFDD, id-CauseLevel-RL-AdditionFailureTDD, id-CauseLevel-RL-ReconfFailure, id-CauseLevel-RL-SetupFailureFDD, id-CauseLevel-RL-SetupFailureTDD, id-CCTrCH-InformationItem-RL-FailureInd, id-CCTrCH-InformationItem-RL-RestoreInd, id-CellCapabilityContainer-FDD, id-CellCapabilityContainerExtension-FDD, id-CellCapabilityContainer-TDD, id-CellCapabilityContainer-TDD-LCR, id-CellPortionID, id-ChipOffset, id-ClosedLoopMode1-SupportIndicator, id-CNOriginatedPage-PagingRqst, id-CommonMeasurementAccuracy, id-CommonMeasurementObjectType-CM-Rprt, id-CommonMeasurementObjectType-CM-Rqst,

743

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-CommonMeasurementObjectType-CM-Rsp, id-CommonMeasurementType, id-CommonTransportChannelResourcesInitialisationNotRequired, id-Common-EDCH-MAC-d-Flow-Specific-InformationFDD, id-Common-EDCH-Support-Indicator, id-CongestionCause, id-Continuous-Packet-Connectivity-DTX-DRX-Information, id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information, id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response, id-CPC-Information, id-CoverageIndicator, id-CriticalityDiagnostics, id-CellPortionLCRID, id-D-RNTI, id-D-RNTI-ReleaseIndication, id-DCHs-to-Add-FDD, id-DCHs-to-Add-TDD, id-DCH-DeleteList-RL-ReconfPrepFDD, id-DCH-DeleteList-RL-ReconfPrepTDD, id-DCH-DeleteList-RL-ReconfRqstFDD, id-DCH-DeleteList-RL-ReconfRqstTDD, id-DCH-FDD-Information, id-DCH-TDD-Information, id-DCH-Indicator-For-E-DCH-HSDPA-Operation, id-FDD-DCHs-to-Modify, id-TDD-DCHs-to-Modify, id-DCH-InformationResponse, id-DCH-Rate-InformationItem-RL-CongestInd, id-DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationListIE-RL-ReconfReadyTDD, id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD, id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD, id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD, id-DL-CCTrCH-InformationListIE-PhyChReconfRqstTDD, id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD, id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD, id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD, id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD, id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD, id-DL-CCTrCH-InformationList-RL-SetupRqstTDD, id-FDD-DL-CodeInformation, id-DL-DPCH-Information-RL-ReconfPrepFDD, id-DL-DPCH-Information-RL-SetupRqstFDD, id-DL-DPCH-Information-RL-ReconfRqstFDD, id-DL-DPCH-InformationItem-PhyChReconfRqstTDD, id-DL-DPCH-InformationItem-RL-AdditionRspTDD, id-DL-DPCH-InformationItem-RL-SetupRspTDD,

744

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD, id-DL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD, id-DL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD, id-DL-DPCH-TimingAdjustment, id-DL-DPCH-Power-Information-RL-ReconfPrepFDD, id-DL-Physical-Channel-Information-RL-SetupRqstTDD, id-DL-PowerBalancing-Information, id-DL-PowerBalancing-ActivationIndicator, id-DL-PowerBalancing-UpdatedIndicator, id-DL-ReferencePowerInformation, id-DLReferencePower, id-DLReferencePowerList-DL-PC-Rqst, id-DL-ReferencePowerInformation-DL-PC-Rqst, id-DRXCycleLengthCoefficient, id-DedicatedMeasurementObjectType-DM-Fail, id-DedicatedMeasurementObjectType-DM-Fail-Ind, id-DedicatedMeasurementObjectType-DM-Rprt, id-DedicatedMeasurementObjectType-DM-Rqst, id-DedicatedMeasurementObjectType-DM-Rsp, id-DedicatedMeasurementType, id-DelayedActivation, id-DelayedActivationList-RL-ActivationCmdFDD, id-DelayedActivationList-RL-ActivationCmdTDD, id-DelayedActivationInformation-RL-ActivationCmdFDD, id-DelayedActivationInformation-RL-ActivationCmdTDD, id-DPC-Mode, id-DPC-Mode-Change-SupportIndicator, id-DSCHs-to-Add-TDD, id-DSCH-DeleteList-RL-ReconfPrepTDD, id-DSCH-InformationListIE-RL-AdditionRspTDD, id-DSCH-InformationListIEs-RL-SetupRspTDD, id-DSCH-TDD-Information, id-DSCH-ModifyList-RL-ReconfPrepTDD, id-DSCH-RNTI, id-DSCHToBeAddedOrModifiedList-RL-ReconfReadyTDD, id-Dual-Band-Secondary-Serving-Cell-List, id-EDPCH-Information, id-EDCH-RL-Indication, id-EDCH-FDD-Information, id-Serving-EDCHRL-Id, id-EDCH-FDD-DL-ControlChannelInformation, id-EDCH-FDD-InformationResponse, id-E-DCH-FDD-Update-Information, id-EDCH-MACdFlows-To-Add, id-EDCH-FDD-Information-To-Modify, id-EDCH-MACdFlows-To-Delete, id-EDPCH-Information-RLReconfRequest-FDD, id-EDPCH-Information-RLAdditionReq-FDD, id-EDCH-MacdFlowSpecificInformationList-RL-PreemptRequiredInd, id-EDCH-MacdFlowSpecificInformationItem-RL-PreemptRequiredInd, id-EDCH-MacdFlowSpecificInformationList-RL-CongestInd,

745

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-EDCH-MacdFlowSpecificInformationItem-RL-CongestInd, id-Enhanced-FACH-Support-Indicator, id-Enhanced-FACH-Information-ResponseFDD, id-Enhanced-PCH-Capability, id-ExtendedPropagationDelay, id-Extended-SRNC-ID, id-Extended-RNC-ID, id-Extended-S-RNTI, id-Extended-S-RNTI-Group, id-Serving-cell-change-CFN, id-E-DCH-Serving-cell-change-informationResponse, id-E-RNTI-For-FACH, id-H-RNTI-For-FACH, id-RNTI-Allocation-Indicator, id-Enhanced-PrimaryCPICH-EcNo, id-E-RNTI, id-F-DPCH-SlotFormat, id-F-DPCH-SlotFormatSupportRequest, id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD, id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD, id-Fast-Reconfiguration-Mode, id-Fast-Reconfiguration-Permission, id-FrameOffset, id-F-DPCH-Information-RL-ReconfPrepFDD, id-F-DPCH-Information-RL-SetupRqstFDD, id-GA-Cell, id-GA-CellAdditionalShapes, id-GSM-Cell-InfEx-Rqst, id-HCS-Prio, id-HSDSCH-Configured-Indicator, id-HSDSCH-FDD-Information, id-HSDSCH-FDD-Information-Response, id-HSDSCH-FDD-Update-Information, id-HSDSCH-TDD-Update-Information, id-HSDSCH-Information-to-Modify, id-HSDSCH-Information-to-Modify-Unsynchronised, id-HSDSCH-MACdFlows-to-Add, id-HSDSCH-MACdFlows-to-Delete, id-HSDSCHMacdFlowSpecificInformationList-RL-PreemptRequiredInd, id-HSDSCHMacdFlowSpecificInformationItem-RL-PreemptRequiredInd, id-HSDSCH-Physical-Layer-Category, id-HSDSCH-RNTI, id-HS-DSCH-serving-cell-change-information, id-HS-DSCH-serving-cell-change-informationResponse, id-HSDSCH-TDD-Information, id-HSDSCH-TDD-Information-Response, id-HSPDSCH-RL-ID, id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD, id-HSPDSCH-Timeslot-InformationListLCR-PhyChReconfRqstTDD, id-HSSICH-Info-DM-Rprt, id-HSSICH-Info-DM-Rqst,

746

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-HSSICH-Info-DM, id-IMSI, id-InformationExchangeID, id-InformationExchangeObjectType-InfEx-Rprt, id-InformationExchangeObjectType-InfEx-Rqst, id-InformationExchangeObjectType-InfEx-Rsp, id-InformationReportCharacteristics, id-InformationType, id-Initial-DL-DPCH-TimingAdjustment, id-Initial-DL-DPCH-TimingAdjustment-Allowed, id-InnerLoopDLPCStatus, id-InterfacesToTraceItem, id-Inter-Frequency-Cell-List, id-L3-Information, id-AdjustmentPeriod, id-ListOfInterfacesToTrace, id-MaxAdjustmentStep, id-Max-UE-DTX-Cycle, id-MBMS-Bearer-Service-List, id-MBMS-Bearer-Service-List-InfEx-Rsp, id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rqst, id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rsp, id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rprt, id-MBMS-Cell-InfEx-Rqst, id-MBMS-Cell-InfEx-Rsp, id-MBMS-Cell-InfEx-Rprt, id-MBSFN-Cluster-Identity, id-MBSFN-Scheduling-Transmission-Time-Interval-Info-List, id-MCCH-Configuration-Info, id-MCCH-Message-List, id-MeasurementFilterCoefficient, id-MeasurementID, id-MeasurementRecoveryBehavior, id-MeasurementRecoveryReportingIndicator, id-MeasurementRecoverySupportIndicator, id-Multiple-PLMN-List, id-Multiple-RL-InformationResponse-RL-ReconfReadyTDD, id-NACC-Related-Data, id-Neighbouring-E-UTRA-CellInformation, id-Old-URA-ID, id-PagingArea-PagingRqst, id-PartialReportingIndicator, id-PDSCH-RL-ID, id-Permanent-NAS-UE-Identity, id-Phase-Reference-Update-Indicator, id-FACH-FlowControlInformation, id-PLCCH-Information-PhyChReconfRqstTDD, id-PowerAdjustmentType, id-PrimCCPCH-RSCP-DL-PC-RqstTDD, id-Primary-CPICH-Usage-For-Channel-Estimation, id-PropagationDelay,

747

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-ProvidedInformation, id-RANAP-EnhancedRelocationInformationRequest, id-RANAP-EnhancedRelocationInformationResponse, id-RANAP-RelocationInformation, id-ResetIndicator, id-Released-CN-Domain, id-EDCH-RLSet-Id, id-RL-Information-PhyChReconfRqstFDD, id-RL-Information-PhyChReconfRqstTDD, id-RL-Information-RL-AdditionRqstFDD, id-RL-Information-RL-AdditionRqstTDD, id-RL-Information-RL-DeletionRqst, id-RL-Information-RL-FailureInd, id-RL-Information-RL-ReconfPrepFDD, id-RL-Information-RL-ReconfPrepTDD, id-RL-Information-RL-RestoreInd, id-RL-Information-RL-SetupRqstFDD, id-RL-Information-RL-SetupRqstTDD, id-RL-InformationItem-RL-CongestInd, id-RL-InformationItem-DM-Rprt, id-RL-InformationItem-DM-Rqst, id-RL-InformationItem-DM-Rsp, id-RL-InformationItem-RL-PreemptRequiredInd, id-RL-InformationItem-RL-SetupRqstFDD, id-RL-InformationList-RL-CongestInd, id-RL-InformationList-RL-AdditionRqstFDD, id-RL-InformationList-RL-DeletionRqst, id-RL-InformationList-RL-PreemptRequiredInd, id-RL-InformationList-RL-ReconfPrepFDD, id-RL-InformationResponse-RL-AdditionRspTDD, id-RL-InformationResponse-RL-ReconfReadyTDD, id-RL-InformationResponse-RL-ReconfRspTDD, id-RL-InformationResponse-RL-SetupRspTDD, id-RL-InformationResponseItem-RL-AdditionRspFDD, id-RL-InformationResponseItem-RL-ReconfReadyFDD, id-RL-InformationResponseItem-RL-ReconfRspFDD, id-RL-InformationResponseItem-RL-SetupRspFDD, id-RL-InformationResponseList-RL-AdditionRspFDD, id-RL-InformationResponseList-RL-ReconfReadyFDD, id-RL-InformationResponseList-RL-ReconfRspFDD, id-RL-InformationResponseList-RL-SetupRspFDD, id-RL-ParameterUpdateIndicationFDD-RL-Information-Item, id-RL-ParameterUpdateIndicationFDD-RL-InformationList, id-RL-ReconfigurationFailure-RL-ReconfFail, id-RL-ReconfigurationRequestFDD-RL-InformationList, id-RL-ReconfigurationRequestFDD-RL-Information-IEs, id-RL-ReconfigurationResponseTDD-RL-Information, id-RL-Specific-DCH-Info, id-RL-Specific-EDCH-Information, id-RL-Set-InformationItem-DM-Rprt, id-RL-Set-InformationItem-DM-Rqst,

748

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-RL-Set-InformationItem-DM-Rsp, id-RL-Set-Information-RL-FailureInd, id-RL-Set-Information-RL-RestoreInd, id-RL-Set-Successful-InformationItem-DM-Fail, id-RL-Set-Unsuccessful-InformationItem-DM-Fail, id-RL-Set-Unsuccessful-InformationItem-DM-Fail-Ind, id-RL-Successful-InformationItem-DM-Fail, id-RL-Unsuccessful-InformationItem-DM-Fail, id-RL-Unsuccessful-InformationItem-DM-Fail-Ind, id-ReportCharacteristics, id-Reporting-Object-RL-FailureInd, id-Reporing-Object-RL-RestoreInd, id-RNC-ID, id-RxTimingDeviationForTA, id-S-RNTI, id-SAI, id-Secondary-CPICH-Information, id-Secondary-CPICH-Information-Change, id-Secondary-Serving-Cell-List, id-Dual-Band-Secondary-Serving-Cell-List, id-SixtyfourQAM-DL-SupportIndicator, id-SFN, id-SFNReportingIndicator, id-SNA-Information, id-SRNC-ID, id-STTD-SupportIndicator, id-SuccessfulRL-InformationResponse-RL-AdditionFailureFDD, id-SuccessfulRL-InformationResponse-RL-SetupFailureFDD, id-TDD-maxNrDLPhysicalchannels, id-TDD-Support-8PSK, id-TDD-Support-PLCCH, id-timeSlot-ISCP, id-TimeSlot-RL-SetupRspTDD, id-TnlQos, id-TraceDepth, id-TraceRecordingSessionReference, id-TraceReference, id-TransportBearerID, id-TransportBearerRequestIndicator, id-TransportLayerAddress, id-UC-ID, id-ContextInfoItem-Reset, id-ContextGroupInfoItem-Reset, id-Transmission-Gap-Pattern-Sequence-Information, id-UE-AggregateMaximumBitRate, id-UEIdentity, id-UEMeasurementType, id-UEMeasurementTimeslotInfoHCR, id-UEMeasurementTimeslotInfoLCR, id-UEMeasurementReportCharacteristics, id-UEMeasurementParameterModAllow,

749

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-UEMeasurementValueInformation, id-UE-State, id-UE-with-enhanced-HS-SCCH-support-indicator, id-UL-CCTrCH-AddInformation-RL-ReconfPrepTDD, id-UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD, id-UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD, id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD, id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD, id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD, id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD, id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD, id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD, id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD, id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD, id-UL-CCTrCH-InformationList-RL-SetupRqstTDD, id-UL-CCTrCH-InformationListIE-PhyChReconfRqstTDD, id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD, id-UL-CCTrCH-InformationListIE-RL-ReconfReadyTDD, id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD, id-UL-DPCH-Information-RL-ReconfPrepFDD, id-UL-DPCH-Information-RL-ReconfRqstFDD, id-UL-DPCH-Information-RL-SetupRqstFDD, id-UL-DPDCHIndicatorEDCH, id-UL-DPCH-InformationItem-PhyChReconfRqstTDD, id-UL-DPCH-InformationItem-RL-AdditionRspTDD, id-UL-DPCH-InformationItem-RL-SetupRspTDD, id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD, id-UL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD, id-UL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD, id-UL-Physical-Channel-Information-RL-SetupRqstTDD, id-UL-SIRTarget, id-URA-ID, id-URA-Information, id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD, id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD, id-UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD, id-UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD, id-USCHs-to-Add, id-USCH-DeleteList-RL-ReconfPrepTDD, id-USCH-InformationListIE-RL-AdditionRspTDD, id-USCH-InformationListIEs-RL-SetupRspTDD, id-USCH-Information, id-USCH-ModifyList-RL-ReconfPrepTDD, id-USCHToBeAddedOrModifiedList-RL-ReconfReadyTDD, id-DL-Timeslot-ISCP-LCR-Information-RL-SetupRqstTDD, id-RL-LCR-InformationResponse-RL-SetupRspTDD, id-UL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD, id-UL-DPCH-LCR-InformationItem-RL-SetupRspTDD, id-DL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD, id-DL-DPCH-LCR-InformationItem-RL-SetupRspTDD, id-DSCH-LCR-InformationListIEs-RL-SetupRspTDD,

750

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11

751

3GPP TS 25.423 V11.2.0 (2012-06)

id-USCH-LCR-InformationListIEs-RL-SetupRspTDD, id-DL-Timeslot-ISCP-LCR-Information-RL-AdditionRqstTDD, id-RL-LCR-InformationResponse-RL-AdditionRspTDD, id-UL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD, id-UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD, id-DL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD, id-DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD, id-DSCH-LCR-InformationListIEs-RL-AdditionRspTDD, id-USCH-LCR-InformationListIEs-RL-AdditionRspTDD, id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD, id-UL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD, id-DL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD, id-DL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD, id-UL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD, id-DL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD, id-timeSlot-ISCP-LCR-List-DL-PC-Rqst-TDD, id-TSTD-Support-Indicator-RL-SetupRqstTDD, id-PrimaryCCPCH-RSCP-RL-ReconfPrepTDD, id-DL-TimeSlot-ISCP-Info-RL-ReconfPrepTDD, id-DL-Timeslot-ISCP-LCR-Information-RL-ReconfPrepTDD, id-neighbouringTDDCellMeasurementInformationLCR, id-UL-SIR-Target-CCTrCH-InformationItem-RL-SetupRspTDD, id-UL-SIR-Target-CCTrCH-LCR-InformationItem-RL-SetupRspTDD, id-TrafficClass, id-UL-Synchronisation-Parameters-LCR, id-TDD-DL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD, id-TDD-UL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD, id-MAChs-ResetIndicator, id-UL-TimingAdvanceCtrl-LCR, id-CCTrCH-Maximum-DL-Power-RL-SetupRspTDD, id-CCTrCH-Minimum-DL-Power-RL-SetupRspTDD, id-CCTrCH-Maximum-DL-Power-RL-AdditionRspTDD, id-CCTrCH-Minimum-DL-Power-RL-AdditionRspTDD, id-CCTrCH-Maximum-DL-Power-RL-ReconfReadyTDD, id-CCTrCH-Minimum-DL-Power-RL-ReconfReadyTDD, id-Maximum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD, id-Minimum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD, id-DL-CCTrCH-InformationList-RL-ReconfRspTDD, id-DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD, id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD, id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD, id-UL-CCTrCH-InformationItem-RL-AdditionRqstTDD, id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD, id-DL-CCTrCH-InformationItem-RL-AdditionRqstTDD, id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD, id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD, id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD, id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD, id-PrimaryCCPCH-RSCP-Delta, id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp, id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp,

3GPP

Release 11
id-SynchronisationIndicator, id-secondary-LCR-CCPCH-Info-TDD, id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp, id-CellCapabilityContainer-TDD768, id-neighbouringTDDCellMeasurementInformation768, id-RL-InformationResponse-RL-SetupRspTDD768, id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD768, id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD768, id-UL-DPCH-InformationItem-RL-SetupRspTDD768, id-DL-DPCH-InformationItem-RL-SetupRspTDD768, id-TDD768-minimumSpreadingFactor-UL, id-TDD768-minimumSpreadingFactor-DL, id-TDD768-maxNrDLPhysicalchannels, id-TDD768-maxNrDLPhysicalchannelsTS, id-RL-InformationResponse-RL-AdditionRspTDD768, id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD768, id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD768, id-UL-DPCH-InformationItem-RL-AdditionRspTDD768, id-DL-DPCH-InformationItem-RL-AdditionRspTDD768, id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768, id-UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768, id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768, id-DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768, id-secondary-CCPCH-Info-RL-ReconfReadyTDD768, id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD768, id-UL-Timeslot-InformationList-PhyChReconfRqstTDD768, id-DL-Timeslot-InformationList-PhyChReconfRqstTDD768, id-multiple-DedicatedMeasurementValueList-TDD768-DM-Rsp, id-UEMeasurementTimeslotInfo768, id-DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD, id-DPCH-ID768-DM-Rsp, id-DPCH-ID768-DM-Rqst, id-DPCH-ID768-DM-Rprt, id-RxTimingDeviationForTAext, id-RxTimingDeviationForTA768, id-E-DCH-Information, id-E-DCH-Information-Reconfig, id-E-DCH-Serving-RL-ID, id-E-DCH-Information-Response, id-E-DCH-768-Information, id-E-DCH-768-Information-Reconfig, id-E-DCH-768-Information-Response, id-E-DCH-LCR-Information, id-E-DCH-LCR-Information-Reconfig, id-E-DCH-LCR-Information-Response, id-PowerControlGAP, id-IdleIntervalInformation, id-NeedforIdleInterval, id-IdleIntervalConfigurationIndicator, id-UARFCNforNt, id-HS-SICH-ID-Extension,

752

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-HSSICH-Info-DM-Rqst-Extension, id-UPPCHPositionLCR, id-Common-EDCH-MAC-d-Flow-Specific-InformationLCR, id-Enhanced-FACH-Information-ResponseLCR, id-HSDSCH-PreconfigurationSetup, id-HSDSCH-PreconfigurationInfo, id-NoOfTargetCellHS-SCCH-Order, id-EnhancedHSServingCC-Abort, id-GANSS-Time-ID, id-Additional-HS-Cell-Information-RL-Setup, id-Additional-HS-Cell-Information-Response, id-Additional-HS-Cell-Information-RL-Addition, id-Additional-HS-Cell-Change-Information-Response, id-Additional-HS-Cell-Information-RL-Reconf-Prep, id-Additional-HS-Cell-Information-RL-Reconf-Req, id-Additional-HS-Cell-RL-Reconf-Response, id-Additional-HS-Cell-Information-RL-Param-Upd, id-MinimumReducedE-DPDCH-GainFactor, id-ContinuousPacketConnectivity-DRX-InformationLCR, id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR, id-CPC-InformationLCR, id-E-DCH-Semi-PersistentScheduling-Information-LCR, id-HS-DSCH-Semi-PersistentScheduling-Information-LCR, id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR, id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR, id-ActivationInformation, id-Additional-EDCH-Cell-Information-RL-Setup-Req, id-Additional-EDCH-Cell-Information-Response, id-Additional-EDCH-Cell-Information-RL-Add-Req, id-Additional-EDCH-Cell-Information-Response-RLAdd, id-Additional-EDCH-Cell-Information-RL-Reconf-Prep, id-Additional-EDCH-Cell-Information-RL-Reconf-Req, id-Additional-EDCH-Cell-Information-RL-Param-Upd, id-Additional-EDCH-Cell-Information-ResponseRLReconf, id-DCH-MeasurementOccasion-Information, id-DCH-MeasurementType-Indicator, id-Non-Serving-RL-Preconfig-Info, id-Non-Serving-RL-Preconfig-Setup, id-Non-Serving-RL-Preconfig-Removal, id-CellCapabilityContainerExtension-TDD-LCR, id-Multi-Carrier-EDCH-Setup, id-Multi-Carrier-EDCH-Reconfigure, id-Multi-Carrier-EDCH-Response, id-MU-MIMO-InformationLCR, id-MU-MIMO-Indicator, id-Usefulness-Of-Battery-Optimization, id-MDT-Configuration, id-Neighbouring-UMTS-CellInformation-Ext, id-Extension-CommonMeasurementObjectType-CM-Rprt, id-Extension-CommonMeasurementObjectType-CM-Rqst, id-Extension-CommonMeasurementObjectType-CM-Rsp,

753

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-Extension-FailureIndicationMeasurementList, id-Extension-FailureMeasurementList, id-Extension-TerminationMeasurementList, id-GsmCellList-CM-Rprt, id-GsmCellList-CM-Rqst, id-GsmCellList-CM-Rsp, id-GSM-Cell-InfEx-Rqst, id-SpeechVersion, id-SourceID, id-TargetID, id-ClassmarkInformation2, id-ClassmarkInformation3, id-GSM-Cell-CM-Rqst, id-LoadValue, id-EventH, id-Cell-Capacity-Class-Value, id-Control-Type-InformationTransferControlReq, id-ANR-Cell-InfEx-Rqst, id-ANR-Cell-InfEx-Rsp, id-Trace-Collection-Entity-IP-Address, id-CPC-RecoveryReport, id-UL-CLTD-Information, id-UL-CLTD-Information-Reconf, id-UL-CLTD-State-Update-Information, id-FTPICH-Information, id-FTPICH-Information-Reconf FROM RNSAP-Constants; -- ************************************************************** --- RADIO LINK SETUP REQUEST FDD --- **************************************************************

754

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkSetupRequestFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupRequestFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupRequestFDD-Extensions}} ... } RadioLinkSetupRequestFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-SRNC-ID CRITICALITY reject TYPE RNC-ID PRESENCE mandatory} | { ID id-S-RNTI CRITICALITY reject TYPE S-RNTI PRESENCE mandatory } | { ID id-D-RNTI CRITICALITY reject TYPE D-RNTI PRESENCE optional } | { ID id-AllowedQueuingTime CRITICALITY reject TYPE AllowedQueuingTime PRESENCE optional { ID id-UL-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject TYPE UL-DPCH-Information-RL-SetupRqstFDD { ID id-DL-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject TYPE DL-DPCH-Information-RL-SetupRqstFDD { ID id-DCH-FDD-Information CRITICALITY reject TYPE DCH-FDD-Information PRESENCE mandatory } | { ID id-RL-Information-RL-SetupRqstFDD CRITICALITY notify TYPE RL-InformationList-RL-SetupRqstFDD

OPTIONAL,

} | PRESENCE mandatory PRESENCE optional PRESENCE mandatory

} | } | }|

3GPP

Release 11

755

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

{ ID id-Transmission-Gap-Pattern-Sequence-Information CRITICALITY reject TYPE Transmission-Gap-Pattern-Sequence-Information optional } | { ID id-Active-Pattern-Sequence-Information CRITICALITY reject TYPE Active-Pattern-Sequence-Information PRESENCE optional }, ... } UL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { ul-ScramblingCode UL-ScramblingCode, minUL-ChannelisationCodeLength MinUL-ChannelisationCodeLength, maxNrOfUL-DPCHs MaxNrOfUL-DPCHs OPTIONAL -- This IE shall be present if minUL-ChannelisationCodeLength equals to 4 -- , ul-PunctureLimit PunctureLimit, ul-TFCS TFCS, ul-DPCCH-SlotFormat UL-DPCCH-SlotFormat, ul-SIRTarget UL-SIR OPTIONAL, diversityMode DiversityMode, not-Used-sSDT-CellIdLength NULL OPTIONAL, not-Used-s-FieldLength NULL OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-Information-RL-SetupRqstFDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-Information-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DPC-Mode CRITICALITY reject EXTENSION DPC-Mode PRESENCE optional }| { ID id-UL-DPDCHIndicatorEDCH CRITICALITY reject EXTENSION UL-DPDCHIndicatorEDCH PRESENCE optional }, ... } DL-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { tFCS TFCS, dl-DPCH-SlotFormat DL-DPCH-SlotFormat, nrOfDLchannelisationcodes NrOfDLchannelisationcodes, tFCI-SignallingMode TFCI-SignallingMode, tFCI-Presence TFCI-Presence OPTIONAL -- This IE shall be present if DL DPCH Slot Format IE is equal to any of the values from 12 to 16 --, multiplexingPosition MultiplexingPosition, powerOffsetInformation PowerOffsetInformation-RL-SetupRqstFDD, fdd-dl-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, limitedPowerIncrease LimitedPowerIncrease, innerLoopDLPCStatus InnerLoopDLPCStatus, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-Information-RL-SetupRqstFDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-Information-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PowerOffsetInformation-RL-SetupRqstFDD ::= SEQUENCE { po1-ForTFCI-Bits PowerOffset, po2-ForTPC-Bits PowerOffset,

3GPP

Release 11
po3-ForPilotBits iE-Extensions ...

756

3GPP TS 25.423 V11.2.0 (2012-06)

PowerOffset, ProtocolExtensionContainer { { PowerOffsetInformation-RL-SetupRqstFDD-ExtIEs} } OPTIONAL,

PowerOffsetInformation-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-RL-SetupRqstFDD SetupRqstFDD} } ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationItemIEs-RL-

RL-InformationItemIEs-RL-SetupRqstFDD RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-RL-SetupRqstFDD CRITICALITY notify }

TYPE RL-InformationItem-RL-SetupRqstFDD

PRESENCE mandatory

RL-InformationItem-RL-SetupRqstFDD ::= SEQUENCE { rL-ID RL-ID, c-ID C-ID, firstRLS-indicator FirstRLS-Indicator, frameOffset FrameOffset, chipOffset ChipOffset, propagationDelay PropagationDelay OPTIONAL, diversityControlField DiversityControlField OPTIONAL -- This IE shall be present if the RL is not the first one in the RL-InformationList-RL-SetupRqstFDD --, dl-InitialTX-Power DL-Power OPTIONAL, primaryCPICH-EcNo PrimaryCPICH-EcNo OPTIONAL, not-Used-sSDT-CellID NULL OPTIONAL, transmitDiversityIndicator TransmitDiversityIndicator OPTIONAL, -- This IE shall be present unless Diversity Mode IE in UL DPCH Information group is none iE-Extensions ProtocolExtensionContainer { {RL-InformationItem-RL-SetupRqstFDD-ExtIEs} } OPTIONAL, ... } RL-InformationItem-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Enhanced-PrimaryCPICH-EcNo CRITICALITY ignore EXTENSION Enhanced-PrimaryCPICH-EcNo { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info { ID id-DelayedActivation CRITICALITY reject EXTENSION DelayedActivation { ID id-CellPortionID CRITICALITY ignore EXTENSION CellPortionID { ID id-RL-Specific-EDCH-Information CRITICALITY reject EXTENSION RL-Specific-EDCH-Information { ID id-EDCH-RL-Indication CRITICALITY reject EXTENSION EDCH-RL-Indication { ID id-ExtendedPropagationDelay CRITICALITY ignore EXTENSION ExtendedPropagationDelay { ID id-SynchronisationIndicator CRITICALITY reject EXTENSION SynchronisationIndicator { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore EXTENSION HSDSCH-PreconfigurationSetup { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Setup { ID id-FTPICH-Information CRITICALITY ignore EXTENSION FTPICH-Information ... } RadioLinkSetupRequestFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Permanent-NAS-UE-Identity CRITICALITY ignore EXTENSION Permanent-NAS-UE-Identity PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional optional optional optional optional optional }| }| }| }| }| }| }| }| }| }| },

PRESENCE optional}|

3GPP

Release 11

757

3GPP TS 25.423 V11.2.0 (2012-06)

{ ID id-DL-PowerBalancing-Information CRITICALITY ignore EXTENSION DL-PowerBalancing-Information PRESENCE optional}| { ID id-HSDSCH-FDD-Information CRITICALITY reject EXTENSION HSDSCH-FDD-Information PRESENCE optional}| { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE conditional}| -- This IE shall be present if HS-DSCH Information IE is present. { ID id-MBMS-Bearer-Service-List CRITICALITY notify EXTENSION MBMS-Bearer-Service-List PRESENCE optional}| { ID id-EDPCH-Information CRITICALITY reject EXTENSION EDPCH-Information-FDD PRESENCE optional}| { ID id-EDCH-FDD-Information CRITICALITY reject EXTENSION EDCH-FDD-Information PRESENCE conditional}| -- This IE is present if E-DPCH Information IE is present. { ID id-Serving-EDCHRL-Id CRITICALITY reject EXTENSION EDCH-Serving-RL PRESENCE optional}| -- This IE is present if E-DCHInformation IE is present. { ID id-F-DPCH-Information-RL-SetupRqstFDD CRITICALITY reject EXTENSION F-DPCH-Information-RL-SetupRqstFDD PRESENCE optional}| { ID id-Initial-DL-DPCH-TimingAdjustment-Allowed CRITICALITY ignore EXTENSION Initial-DL-DPCH-TimingAdjustment-Allowed PRESENCE optional}| { ID id-DCH-Indicator-For-E-DCH-HSDPA-Operation CRITICALITY reject EXTENSION DCH-Indicator-For-E-DCH-HSDPA-Operation PRESENCE optional}| { ID id-Serving-cell-change-CFN CRITICALITY reject EXTENSION CFN PRESENCE optional}| { ID id-Continuous-Packet-Connectivity-DTX-DRX-Information CRITICALITY reject EXTENSION Continuous-Packet-Connectivity-DTX-DRX-Information PRESENCE optional}| { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information CRITICALITY reject EXTENSION Continuous-Packet-Connectivity-HS-SCCH-LessInformation PRESENCE optional}| { ID id-Extended-SRNC-ID CRITICALITY reject EXTENSION Extended-RNC-ID PRESENCE optional}| { ID id-Additional-HS-Cell-Information-RL-Setup CRITICALITY reject EXTENSION Additional-HS-Cell-Information-RL-Setup-List PRESENCE optional}| { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate PRESENCE optional}| { ID id-Additional-EDCH-Cell-Information-RL-Setup-Req CRITICALITY reject EXTENSION Additional-EDCH-Setup-Info PRESENCE optional}| { ID id-Usefulness-Of-Battery-Optimization CRITICALITY ignore EXTENSION Usefulness-Of-Battery-Optimization PRESENCE optional}| { ID id-UL-CLTD-Information CRITICALITY reject EXTENSION UL-CLTD-Information PRESENCE optional}| { ID id-Extended-S-RNTI CRITICALITY reject EXTENSION Extended-RNTI PRESENCE optional}, ... } Additional-HS-Cell-Information-RL-Setup-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Setup-ItemIEs

Additional-HS-Cell-Information-RL-Setup-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, c-ID C-ID, hS-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Setup-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Information-RL-Setup-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

F-DPCH-Information-RL-SetupRqstFDD ::= SEQUENCE { powerOffsetInformation PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD, fdd-dl-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, limitedPowerIncrease LimitedPowerIncrease, innerLoopDLPCStatus InnerLoopDLPCStatus, iE-Extensions ProtocolExtensionContainer { { F-DPCH-Information-RL-SetupRqstFDD-ExtIEs} }

OPTIONAL,

3GPP

Release 11
} ...

758

3GPP TS 25.423 V11.2.0 (2012-06)

F-DPCH-Information-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-F-DPCH-SlotFormatSupportRequest CRITICALITY reject EXTENSION F-DPCH-SlotFormatSupportRequest }| { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION F-DPCH-SlotFormat PRESENCE optional}, ... } PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD ::= SEQUENCE { po2-ForTPC-Bits PowerOffset, --This IE shall be ignored by DRNS iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD-ExtIEs} } ... } PowerOffsetInformation-F-DPCH-RL-SetupRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK SETUP REQUEST TDD --- ************************************************************** RadioLinkSetupRequestTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupRequestTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupRequestTDD-Extensions}} ... } RadioLinkSetupRequestTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-SRNC-ID { ID id-S-RNTI { ID id-D-RNTI { ID id-UL-Physical-Channel-Information-RL-SetupRqstTDD PRESENCE mandatory } | { ID id-DL-Physical-Channel-Information-RL-SetupRqstTDD PRESENCE mandatory } | { ID id-AllowedQueuingTime { ID id-UL-CCTrCH-InformationList-RL-SetupRqstTDD { ID id-DL-CCTrCH-InformationList-RL-SetupRqstTDD { ID id-DCH-TDD-Information { ID id-DSCH-TDD-Information { ID id-USCH-Information { ID id-RL-Information-RL-SetupRqstTDD ... } CRITICALITY CRITICALITY CRITICALITY CRITICALITY reject reject reject reject TYPE TYPE TYPE TYPE

PRESENCE optional

OPTIONAL,

OPTIONAL,

RNC-ID PRESENCE mandatory } | S-RNTI PRESENCE mandatory } | D-RNTI PRESENCE optional } | UL-Physical-Channel-Information-RL-SetupRqstTDD

CRITICALITY reject CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY reject notify notify reject reject reject reject

TYPE DL-Physical-Channel-Information-RL-SetupRqstTDD TYPE TYPE TYPE TYPE TYPE TYPE TYPE AllowedQueuingTime PRESENCE optional UL-CCTrCH-InformationList-RL-SetupRqstTDD DL-CCTrCH-InformationList-RL-SetupRqstTDD DCH-TDD-Information PRESENCE optional DSCH-TDD-Information PRESENCE optional USCH-Information PRESENCE optional RL-Information-RL-SetupRqstTDD } | PRESENCE optional } | PRESENCE optional } | } | } | } | PRESENCE mandatory },

3GPP

Release 11

759

3GPP TS 25.423 V11.2.0 (2012-06)

UL-Physical-Channel-Information-RL-SetupRqstTDD ::= SEQUENCE { maxNrTimeslots-UL MaxNrTimeslots, minimumSpreadingFactor-UL MinimumSpreadingFactor, maxNrULPhysicalchannels MaxNrULPhysicalchannels, iE-Extensions ProtocolExtensionContainer { {UL-Physical-Channel-InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, ... } UL-Physical-Channel-InformationItem-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-Support-8PSK CRITICALITY ignore EXTENSION Support-8PSK PRESENCE optional }| -- Applicable to 1.28Mcps TDD only { ID id-TDD768-minimumSpreadingFactor-UL CRITICALITY ignore EXTENSION MinimumSpreadingFactor768 }, ... }

PRESENCE optional

DL-Physical-Channel-Information-RL-SetupRqstTDD ::= SEQUENCE { maxNrTimeslots-DL MaxNrTimeslots, minimumSpreadingFactor-DL MinimumSpreadingFactor, maxNrDLPhysicalchannels MaxNrDLPhysicalchannels, iE-Extensions ProtocolExtensionContainer { {DL-Physical-Channel-InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, ... } DL-Physical-Channel-InformationItem-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-maxNrDLPhysicalchannels CRITICALITY ignore EXTENSION optional }| { ID id-TDD-Support-8PSK CRITICALITY ignore EXTENSION PRESENCE optional }| -- Applicable to 1.28Mcps TDD only { ID id-TDD-Support-PLCCH CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-TDD768-minimumSpreadingFactor-DL CRITICALITY ignore EXTENSION optional }| { ID id-TDD768-maxNrDLPhysicalchannels CRITICALITY ignore EXTENSION }| { ID id-TDD768-maxNrDLPhysicalchannelsTS CRITICALITY ignore EXTENSION }, ... } UL-CCTrCH-InformationList-RL-SetupRqstTDD InformationItemIEs-RL-SetupRqstTDD} } MaxNrDLPhysicalchannelsTS Support-8PSK Support-PLCCH MinimumSpreadingFactor768 MaxNrDLPhysicalchannels768 MaxNrDLPhysicalchannelsTS768 PRESENCE PRESENCE optional PRESENCE optional PRESENCE

::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-

UL-CCTrCH-InformationItemIEs-RL-SetupRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD CRITICALITY notify } UL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-TFCS TFCS,

TYPE UL-CCTrCH-InformationItem-RL-SetupRqstTDD

PRESENCE mandatory

3GPP

Release 11
tFCI-Coding ul-PunctureLimit iE-Extensions ... }

760

3GPP TS 25.423 V11.2.0 (2012-06)

TFCI-Coding, PunctureLimit, ProtocolExtensionContainer { {UL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL,

UL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD CRITICALITY reject optional }, -- Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD ... } DL-CCTrCH-InformationList-RL-SetupRqstTDD InformationItemIEs-RL-SetupRqstTDD} }

EXTENSION

TDD-TPC-UplinkStepSize-LCR

PRESENCE

::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-

DL-CCTrCH-InformationItemIEs-RL-SetupRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD CRITICALITY notify } }

TYPE DL-CCTrCH-InformationItem-RL-SetupRqstTDD

PRESENCE mandatory

DL-CCTrCH-InformationItem-RL-SetupRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-TFCS TFCS, tFCI-Coding TFCI-Coding, dl-PunctureLimit PunctureLimit, tdd-TPC-DownlinkStepSize TDD-TPC-DownlinkStepSize, cCTrCH-TPCList CCTrCH-TPCList-RL-SetupRqstTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationItem-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CCTrCH-TPCList-RL-SetupRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCItem-RL-SetupRqstTDD CCTrCH-TPCItem-RL-SetupRqstTDD cCTrCH-ID iE-Extensions ... } ::= SEQUENCE { CCTrCH-ID, ProtocolExtensionContainer { { CCTrCH-TPCItem-RL-SetupRqstTDD-ExtIEs} } OPTIONAL,

CCTrCH-TPCItem-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Information-RL-SetupRqstTDD ::= SEQUENCE { rL-ID RL-ID, c-ID C-ID,

3GPP

Release 11

761

3GPP TS 25.423 V11.2.0 (2012-06)

frameOffset FrameOffset, specialBurstScheduling SpecialBurstScheduling, primaryCCPCH-RSCP PrimaryCCPCH-RSCP OPTIONAL, dL-TimeSlot-ISCP DL-TimeSlot-ISCP-Info OPTIONAL, --for 3.84Mcps TDD and 7.68Mcps TDD only iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-SetupRqstTDD-ExtIEs} } OPTIONAL, ...

RL-Information-RL-SetupRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-Timeslot-ISCP-LCR-Information-RL-SetupRqstTDD CRITICALITY reject EXTENSION DL-TimeSlot-ISCP-LCR-Information PRESENCE optional }| { ID id-TSTD-Support-Indicator-RL-SetupRqstTDD CRITICALITY ignore EXTENSION TSTD-Support-Indicator PRESENCE optional }| --for 1.28Mcps TDD only { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info PRESENCE optional }| { ID id-DelayedActivation CRITICALITY reject EXTENSION DelayedActivation PRESENCE optional }| { ID id-UL-Synchronisation-Parameters-LCR CRITICALITY reject EXTENSION UL-Synchronisation-Parameters-LCR PRESENCE optional }| -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD { ID id-PrimaryCCPCH-RSCP-Delta CRITICALITY ignore EXTENSION PrimaryCCPCH-RSCP-Delta PRESENCE optional }| { ID id-IdleIntervalConfigurationIndicator CRITICALITY ignore EXTENSION NULL PRESENCE optional }| { ID id-CellPortionLCRID CRITICALITY ignore EXTENSION CellPortionLCRID PRESENCE optional }, ... } RadioLinkSetupRequestTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Permanent-NAS-UE-Identity CRITICALITY { ID id-HSDSCH-TDD-Information CRITICALITY { ID id-HSPDSCH-RL-ID CRITICALITY -- This IE shall be present if HS-DSCH Information IE is present. { ID id-PDSCH-RL-ID CRITICALITY { ID id-MBMS-Bearer-Service-List CRITICALITY { ID id-E-DCH-Information CRITICALITY { ID id-E-DCH-Serving-RL-ID CRITICALITY { ID id-E-DCH-768-Information CRITICALITY { ID id-E-DCH-LCR-Information CRITICALITY { ID id-Extended-SRNC-ID CRITICALITY { ID id-ContinuousPacketConnectivity-DRX-InformationLCR CRITICALITY PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR CRITICALITY PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-LCR CRITICALITY optional}| { ID id-RNTI-Allocation-Indicator CRITICALITY { ID id-DCH-MeasurementType-Indicator CRITICALITY { ID id-Multi-Carrier-EDCH-Setup CRITICALITY { ID id-MU-MIMO-Indicator CRITICALITY { ID id-Extended-S-RNTI CRITICALITY ... } ignore reject reject ignore notify reject reject reject reject reject reject reject reject ignore reject reject reject reject EXTENSION Permanent-NAS-UE-Identity EXTENSION HSDSCH-TDD-Information EXTENSION RL-ID EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION PRESENCE optional}| PRESENCE optional}| PRESENCE conditional}|

RL-ID PRESENCE optional}| MBMS-Bearer-Service-List PRESENCE optional}| E-DCH-Information PRESENCE optional}| RL-ID PRESENCE optional}| E-DCH-768-Information PRESENCE optional}| E-DCH-LCR-Information PRESENCE optional}| Extended-RNC-ID PRESENCE optional}| ContinuousPacketConnectivity-DRX-InformationLCR

EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-LCR EXTENSION E-DCH-Semi-PersistentScheduling-Information-LCR PRESENCE EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION RNTI-Allocation-Indicator DCH-MeasurementType-Indicator Multi-Carrier-EDCH-Info MU-MIMO-Indicator Extended-RNTI PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional}| optional}| optional}| optional}| optional},

3GPP

Release 11
-- ************************************************************** --- RADIO LINK SETUP RESPONSE FDD --- **************************************************************

762

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkSetupResponseFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupResponseFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupResponseFDD-Extensions}} ... } RadioLinkSetupResponseFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI { ID id-CN-PS-DomainIdentifier { ID id-CN-CS-DomainIdentifier { ID id-RL-InformationResponseList-RL-SetupRspFDD { ID id-UL-SIRTarget { ID id-CriticalityDiagnostics ... } RL-InformationResponseList-RL-SetupRspFDD SetupRspFDD} } CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY ignore ignore ignore ignore ignore ignore TYPE TYPE TYPE TYPE TYPE TYPE

OPTIONAL,

D-RNTI CN-PS-DomainIdentifier CN-CS-DomainIdentifier RL-InformationResponseList-RL-SetupRspFDD UL-SIR CriticalityDiagnostics

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

optional }| optional }| optional }| mandatory }| optional }| optional },

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationResponseItemIEs-RL-

RL-InformationResponseItemIEs-RL-SetupRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseItem-RL-SetupRspFDD CRITICALITY ignore } RL-InformationResponseItem-RL-SetupRspFDD ::= SEQUENCE { rL-ID RL-ID, rL-Set-ID RL-Set-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, received-total-wide-band-power Received-total-wide-band-power, not-Used-secondary-CCPCH-Info NULL OPTIONAL, dl-CodeInformation FDD-DL-CodeInformation, diversityIndication DiversityIndication-RL-SetupRspFDD, sSDT-SupportIndicator SSDT-SupportIndicator, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, closedlooptimingadjustmentmode Closedlooptimingadjustmentmode maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, primaryScramblingCode PrimaryScramblingCode uL-UARFCN UARFCN dL-UARFCN UARFCN

TYPE RL-InformationResponseItem-RL-SetupRspFDD

PRESENCE mandatory

OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11

763

3GPP TS 25.423 V11.2.0 (2012-06)

primaryCPICH-Power PrimaryCPICH-Power, not-Used-dSCHInformationResponse NULL OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, pC-Preamble PC-Preamble, sRB-Delay SRB-Delay, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponseItem-RL-SetupRspFDD-ExtIEs} } OPTIONAL, ... } RL-InformationResponseItem-RL-SetupRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION optional }| { ID id-HCS-Prio CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Primary-CPICH-Usage-For-Channel-Estimation CRITICALITY ignore EXTENSION optional }| { ID id-Secondary-CPICH-Information CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Active-MBMS-Bearer-ServiceFDD-PFL CRITICALITY ignore EXTENSION optional }| { ID id-EDCH-RLSet-Id CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-EDCH-FDD-DL-ControlChannelInformation CRITICALITY ignore EXTENSION optional }| { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-FrameOffset CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-ChipOffset CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION PRESENCE optional }, ... } DiversityIndication-RL-SetupRspFDD ::= CHOICE { combining Combining-RL-SetupRspFDD, nonCombiningOrFirstRL NonCombiningOrFirstRL-RL-SetupRspFDD } GA-CellAdditionalShapes DL-PowerBalancing-ActivationIndicator HCS-Prio Primary-CPICH-Usage-For-Channel-Estimation Secondary-CPICH-Information Active-MBMS-Bearer-Service-ListFDD-PFL RL-Set-ID EDCH-FDD-DL-ControlChannelInformation DL-DPCH-TimingAdjustment F-DPCH-SlotFormat FrameOffset ChipOffset Neighbouring-E-UTRA-CellInformation HSDSCH-PreconfigurationInfo Non-Serving-RL-Preconfig-Info Neighbouring-UMTS-CellInformation-Ext PRESENCE PRESENCE PRESENCE PRESENCE

3GPP

Release 11

764

3GPP TS 25.423 V11.2.0 (2012-06)

Combining-RL-SetupRspFDD ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL-SetupRspFDD-ExtIEs} } OPTIONAL, ... } CombiningItem-RL-SetupRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DCH-InformationResponse CRITICALITY ignore EXTENSION DCH-InformationResponse }| { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } PRESENCE optional PRESENCE optional },

NonCombiningOrFirstRL-RL-SetupRspFDD ::= SEQUENCE { dCH-InformationResponse DCH-InformationResponse, iE-Extensions ProtocolExtensionContainer { { NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs} } OPTIONAL, ... } NonCombiningOrFirstRLItem-RL-SetupRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } PRESENCE optional},

RadioLinkSetupResponseFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional }| { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD-Information-Response PRESENCE optional }| { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response CRITICALITY ignore EXTENSION Continuous-PacketConnectivity-HS-SCCH-Less-Information-Response PRESENCE optional }| { ID id-SixtyfourQAM-DL-SupportIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-DL-SupportIndicator PRESENCE optional }| { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-HS-Cell-Information-Response-List PRESENCE optional }| { ID id-Additional-EDCH-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-EDCH-Cell-Information-Response-List PRESENCE optional }, ... } Additional-HS-Cell-Information-Response-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-Response-ItemIEs

Additional-HS-Cell-Information-Response-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, hSDSCH-RNTI HSDSCH-RNTI, hS-DSCH-FDD-Secondary-Serving-Information-Response HS-DSCH-FDD-Secondary-Serving-Information-Response, sixtyfourQAM-DL-SupportIndicator SixtyfourQAM-DL-SupportIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-Response-ItemIEs-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11
Additional-HS-Cell-Information-Response-ItemIEs-ExtIEs ... }

765
RNSAP-PROTOCOL-EXTENSION ::= {

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- RADIO LINK SETUP RESPONSE TDD --- ************************************************************** RadioLinkSetupResponseTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupResponseTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupResponseTDD-Extensions}} ... } RadioLinkSetupResponseTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY { ID id-CN-PS-DomainIdentifier CRITICALITY { ID id-CN-CS-DomainIdentifier CRITICALITY { ID id-RL-InformationResponse-RL-SetupRspTDD CRITICALITY --Mandatory for 3.84Mcps TDD only { ID id-UL-SIRTarget CRITICALITY { ID id-CriticalityDiagnostics CRITICALITY ... } ignore ignore ignore ignore ignore ignore TYPE TYPE TYPE TYPE D-RNTI CN-PS-DomainIdentifier CN-CS-DomainIdentifier RL-InformationResponse-RL-SetupRspTDD

OPTIONAL,

PRESENCE PRESENCE PRESENCE PRESENCE

optional optional optional optional

} } } }

| | | |

TYPE UL-SIR TYPE CriticalityDiagnostics

PRESENCE mandatory } | PRESENCE optional },

RL-InformationResponse-RL-SetupRspTDD ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-Info UL-TimeSlot-ISCP-Info, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, uARFCNforNt UARFCN OPTIONAL, cellParameterID CellParameterID OPTIONAL, syncCase SyncCase OPTIONAL, sCH-TimeSlot SCH-TimeSlot OPTIONAL, -- This IE shall be present if Sync Case IE is equal to Case2. -sCTD-Indicator SCTD-Indicator OPTIONAL, pCCPCH-Power PCCPCH-Power, timingAdvanceApplied TimingAdvanceApplied, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-CCPCH-Info-TDD Secondary-CCPCH-Info-TDD OPTIONAL,

3GPP

Release 11

766

3GPP TS 25.423 V11.2.0 (2012-06)

ul-CCTrCHInformation UL-CCTrCHInformationList-RL-SetupRspTDD OPTIONAL, dl-CCTrCHInformation DL-CCTrCHInformationList-RL-SetupRspTDD OPTIONAL, dCH-InformationResponse DCH-InformationResponseList-RL-SetupRspTDD OPTIONAL, dsch-InformationResponse DSCH-InformationResponse-RL-SetupRspTDD OPTIONAL, usch-InformationResponse USCH-InformationResponse-RL-SetupRspTDD OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponse-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ...

RL-InformationResponse-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION { ID id-HCS-Prio CRITICALITY ignore EXTENSION { ID id-TimeSlot-RL-SetupRspTDD CRITICALITY ignore EXTENSION -- This IE shall be present if Sync Case IE is Case1. -{ ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION ... }

GA-CellAdditionalShapes HCS-Prio TimeSlot Neighbouring-E-UTRA-CellInformation Neighbouring-UMTS-CellInformation-Ext

PRESENCE optional }| PRESENCE optional }| PRESENCE conditional }| PRESENCE optional }| PRESENCE optional },

UL-CCTrCHInformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{UL-CCTrCHInformationListIEs-RL-SetupRspTDD}} UL-CCTrCHInformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD CRITICALITY ignore TYPE UL-CCTrCHInformationListIE-RL-SetupRspTDD mandatory } } UL-CCTrCHInformationListIE-RL-SetupRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCHInformationItem-RL-SetupRspTDD UL-CCTrCHInformationItem-RL-SetupRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-Information UL-DPCH-InformationList-RL-SetupRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-UL-SIR-Target-CCTrCH-InformationItem-RL-SetupRspTDD CRITICALITY ignore ... } EXTENSION UL-SIR PRESENCE optional}, PRESENCE

UL-DPCH-InformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container { {UL-DPCH-InformationListIEs-RL-SetupRspTDD} } UL-DPCH-InformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationItem-RL-SetupRspTDD CRITICALITY ignore } UL-DPCH-InformationItem-RL-SetupRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, TYPE UL-DPCH-InformationItem-RL-SetupRspTDD PRESENCE mandatory }

3GPP

Release 11
repetitionLength tDD-DPCHOffset uL-Timeslot-Information iE-Extensions ...

767

3GPP TS 25.423 V11.2.0 (2012-06)

RepetitionLength, TDD-DPCHOffset, UL-Timeslot-Information, ProtocolExtensionContainer { {UL-DPCH-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL,

UL-DPCH-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCHInformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{DL-CCTrCHInformationListIEs-RL-SetupRspTDD}} DL-CCTrCHInformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD CRITICALITY ignore TYPE DL-CCTrCHInformationListIE-RL-SetupRspTDD } PRESENCE mandatory }

DL-CCTrCHInformationListIE-RL-SetupRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCHInformationItem-RL-SetupRspTDD DL-CCTrCHInformationItem-RL-SetupRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-Information DL-DPCH-InformationList-RL-SetupRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-CCTrCH-Maximum-DL-Power-RL-SetupRspTDD CRITICALITY ignore EXTENSION { ID id-CCTrCH-Minimum-DL-Power-RL-SetupRspTDD CRITICALITY ignore EXTENSION ... } DL-Power PRESENCE optional }| -- this is a DCH type CCTrCH power DL-Power PRESENCE optional }, -- this is a DCH type CCTrCH power

DL-DPCH-InformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container { {DL-DPCH-InformationListIEs-RL-SetupRspTDD} } DL-DPCH-InformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationItem-RL-SetupRspTDD CRITICALITY ignore } TYPE DL-DPCH-InformationItem-RL-SetupRspTDD PRESENCE mandatory }

DL-DPCH-InformationItem-RL-SetupRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-Information DL-Timeslot-Information, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

768

3GPP TS 25.423 V11.2.0 (2012-06)

DCH-InformationResponseList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{DCH-InformationResponseListIEs-RL-SetupRspTDD}} DCH-InformationResponseListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse } PRESENCE mandatory }

DSCH-InformationResponse-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{DSCH-InformationList-RL-SetupRspTDD}} DSCH-InformationList-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DSCH-InformationListIEs-RL-SetupRspTDD CRITICALITY ignore } TYPE DSCH-InformationListIEs-RL-SetupRspTDD PRESENCE mandatory }

DSCH-InformationListIEs-RL-SetupRspTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHs)) OF DSCHInformationItem-RL-SetupRspTDD DSCHInformationItem-RL-SetupRspTDD ::= SEQUENCE { dsch-ID DSCH-ID, dSCH-FlowControlInformation DSCH-FlowControlInformation, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, transportFormatManagement TransportFormatManagement, iE-Extensions ProtocolExtensionContainer { {DSCHInformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } DSCHInformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-InformationResponse-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{USCH-InformationList-RL-SetupRspTDD}} USCH-InformationList-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-USCH-InformationListIEs-RL-SetupRspTDD CRITICALITY ignore } TYPE USCH-InformationListIEs-RL-SetupRspTDD PRESENCE mandatory }

USCH-InformationListIEs-RL-SetupRspTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHs)) OF USCHInformationItem-RL-SetupRspTDD USCHInformationItem-RL-SetupRspTDD ::= SEQUENCE { usch-ID USCH-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, transportFormatManagement TransportFormatManagement, iE-Extensions ProtocolExtensionContainer { {USCHInformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } USCHInformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkSetupResponseTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RL-LCR-InformationResponse-RL-SetupRspTDD CRITICALITY ignore EXTENSION RL-LCR-InformationResponse-RL-SetupRspTDD PRESENCE optional}|

3GPP

Release 11

769

3GPP TS 25.423 V11.2.0 (2012-06)

--Mandatory for 1.28Mcps TDD only { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD-Information-Response PRESENCE optional}| { ID id-DSCH-RNTI CRITICALITY ignore EXTENSION DSCH-RNTI PRESENCE optional}| { ID id-Active-MBMS-Bearer-ServiceTDD-PFL CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListTDD-PFL PRESENCE optional}| { ID id-RL-InformationResponse-RL-SetupRspTDD768 CRITICALITY ignore EXTENSION RL-InformationResponse-RL-SetupRspTDD768 PRESENCE optional}| { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH-Information-Response PRESENCE optional}| { ID id-E-DCH-768-Information-Response CRITICALITY ignore EXTENSION E-DCH-768-Information-Response PRESENCE optional}| { ID id-E-DCH-LCR-Information-Response CRITICALITY ignore EXTENSION E-DCH-LCR-Information-Response PRESENCE optional}| { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore EXTENSION ContinuousPacketConnectivity-DRX-InformationResponseLCR PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION HS-DSCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION E-DCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-RNTI-For-FACH CRITICALITY ignore EXTENSION E-RNTI PRESENCE optional}| { ID id-H-RNTI-For-FACH CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH-MeasurementOccasion-Information PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier-EDCH-Information-Response PRESENCE optional}| { ID id-MU-MIMO-InformationLCR CRITICALITY reject EXTENSION MU-MIMO-InformationLCR PRESENCE optional}, ... } RL-LCR-InformationResponse-RL-SetupRspTDD ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-LCR-Info UL-TimeSlot-ISCP-LCR-Info, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, uARFCNforNt UARFCN OPTIONAL, cellParameterID CellParameterID OPTIONAL, sCTD-Indicator SCTD-Indicator OPTIONAL, pCCPCH-Power PCCPCH-Power, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-LCR-CCPCH-Info-TDD Secondary-LCR-CCPCH-Info-TDD OPTIONAL, ul-LCR-CCTrCHInformation UL-LCR-CCTrCHInformationList-RL-SetupRspTDD OPTIONAL, dl-LCR-CCTrCHInformation DL-LCR-CCTrCHInformationList-RL-SetupRspTDD OPTIONAL, dCH-InformationResponse DCH-InformationResponseList-RL-SetupRspTDD OPTIONAL, dsch-LCR-InformationResponse DSCH-LCR-InformationResponse-RL-SetupRspTDD OPTIONAL, usch-LCR-InformationResponse USCH-LCR-InformationResponse-RL-SetupRspTDD OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-LCR-InformationResponseList-RL-SetupRspTDD-ExtIEs} }

OPTIONAL,

3GPP

Release 11
} ...

770

3GPP TS 25.423 V11.2.0 (2012-06)

RL-LCR-InformationResponseList-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION { ID id-HCS-Prio CRITICALITY ignore EXTENSION { ID id-UL-TimingAdvanceCtrl-LCR CRITICALITY ignore EXTENSION --Mandatory for 1.28Mcps TDD only { ID id-PowerControlGAP CRITICALITY ignore EXTENSION -- Applicable to 1.28Mcps TDD only { ID id-SixtyfourQAM-DL-SupportIndicator CRITICALITY ignore EXTENSION -- Applicable to 1.28Mcps TDD only { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION ... }

{ GA-CellAdditionalShapes HCS-Prio UL-TimingAdvanceCtrl-LCR ControlGAP SixtyfourQAM-DL-SupportIndicator Neighbouring-E-UTRA-CellInformation IdleIntervalInformation Neighbouring-UMTS-CellInformation-Ext

PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional },

UL-LCR-CCTrCHInformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{UL-LCR-CCTrCHInformationListIEs-RL-SetupRspTDD}} UL-LCR-CCTrCHInformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD CRITICALITY ignore TYPE UL-LCR-CCTrCHInformationListIE-RL-SetupRspTDD mandatory } } UL-LCR-CCTrCHInformationListIE-RL-SetupRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHsLCR)) OF UL-LCR-CCTrCHInformationItem-RL-SetupRspTDD UL-LCR-CCTrCHInformationItem-RL-SetupRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-LCR-Information UL-DPCH-LCR-InformationList-RL-SetupRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-LCR-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } UL-LCR-CCTrCHInformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-UL-SIR-Target-CCTrCH-LCR-InformationItem-RL-SetupRspTDD CRITICALITY ignore ... } EXTENSION UL-SIR PRESENCE optional}, PRESENCE

UL-DPCH-LCR-InformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container { {UL-DPCH-LCR-InformationListIEs-RL-SetupRspTDD} } UL-DPCH-LCR-InformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-LCR-InformationItem-RL-SetupRspTDD CRITICALITY ignore } TYPE UL-DPCH-LCR-InformationItem-RL-SetupRspTDD PRESENCE mandatory }

UL-DPCH-LCR-InformationItem-RL-SetupRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-TimeslotLCR-Information UL-TimeslotLCR-Information, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL,

3GPP

Release 11
} ...

771

3GPP TS 25.423 V11.2.0 (2012-06)

UL-DPCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-LCR-CCTrCHInformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{DL-LCR-CCTrCHInformationListIEs-RL-SetupRspTDD}} DL-LCR-CCTrCHInformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD CRITICALITY ignore TYPE DL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD } } PRESENCE mandatory

DL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHsLCR)) OF DL-CCTrCH-LCR-InformationItem-RL-SetupRspTDD DL-CCTrCH-LCR-InformationItem-RL-SetupRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-LCR-Information DL-DPCH-LCR-InformationList-RL-SetupRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-LCR-InformationList-RL-SetupRspTDD ::= ProtocolIE-Single-Container { {DL-DPCH-LCR-InformationListIEs-RL-SetupRspTDD} } DL-DPCH-LCR-InformationListIEs-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-LCR-InformationItem-RL-SetupRspTDD CRITICALITY ignore } TYPE DL-DPCH-LCR-InformationItem-RL-SetupRspTDD PRESENCE mandatory }

DL-DPCH-LCR-InformationItem-RL-SetupRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-LCR-Information DL-TimeslotLCR-Information, tSTD-Indicator TSTD-Indicator, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DSCH-LCR-InformationResponse-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{DSCH-LCR-InformationList-RL-SetupRspTDD}} DSCH-LCR-InformationList-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DSCH-LCR-InformationListIEs-RL-SetupRspTDD CRITICALITY ignore } TYPE DSCH-LCR-InformationListIEs-RL-SetupRspTDD PRESENCE mandatory }

3GPP

Release 11

772

3GPP TS 25.423 V11.2.0 (2012-06)

DSCH-LCR-InformationListIEs-RL-SetupRspTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHsLCR)) OF DSCH-LCR-InformationItem-RL-SetupRspTDD DSCH-LCR-InformationItem-RL-SetupRspTDD dsch-ID dSCH-FlowControlInformation bindingID transportLayerAddress transportFormatManagement iE-Extensions ... } ::= SEQUENCE { DSCH-ID, DSCH-FlowControlInformation, BindingID OPTIONAL, TransportLayerAddress OPTIONAL, TransportFormatManagement, ProtocolExtensionContainer { {DSCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL,

DSCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-LCR-InformationResponse-RL-SetupRspTDD ::= ProtocolIE-Single-Container {{USCH-LCR-InformationList-RL-SetupRspTDD}} USCH-LCR-InformationList-RL-SetupRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-USCH-LCR-InformationListIEs-RL-SetupRspTDD CRITICALITY ignore } TYPE USCH-LCR-InformationListIEs-RL-SetupRspTDD PRESENCE mandatory }

USCH-LCR-InformationListIEs-RL-SetupRspTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHsLCR)) OF USCH-LCR-InformationItem-RL-SetupRspTDD USCH-LCR-InformationItem-RL-SetupRspTDD ::= SEQUENCE { usch-ID USCH-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, transportFormatManagement TransportFormatManagement, iE-Extensions ProtocolExtensionContainer { {USCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs} } OPTIONAL, ... } USCH-LCR-InformationItem-RL-SetupRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationResponse-RL-SetupRspTDD768 ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-Info UL-TimeSlot-ISCP-Info, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, uARFCNforNt UARFCN OPTIONAL,

3GPP

Release 11

773

3GPP TS 25.423 V11.2.0 (2012-06)

cellParameterID CellParameterID OPTIONAL, syncCase SyncCase OPTIONAL, sCH-TimeSlot SCH-TimeSlot OPTIONAL, -- This IE shall be present if Sync Case IE is equal to Case2. -sCTD-Indicator SCTD-Indicator OPTIONAL, pCCPCH-Power PCCPCH-Power, timingAdvanceApplied TimingAdvanceApplied, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-CCPCH-Info-TDD768 Secondary-CCPCH-Info-TDD768 OPTIONAL, ul-CCTrCHInformation768 UL-CCTrCHInformationList-RL-SetupRspTDD768 OPTIONAL, dl-CCTrCHInformation768 DL-CCTrCHInformationList-RL-SetupRspTDD768 OPTIONAL, dCH-InformationResponse DCH-InformationResponseList-RL-SetupRspTDD OPTIONAL, dsch-InformationResponse DSCH-InformationResponse-RL-SetupRspTDD OPTIONAL, usch-InformationResponse USCH-InformationResponse-RL-SetupRspTDD OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, gA-CellAdditionalShapes GA-CellAdditionalShapes OPTIONAL, hCS-Prio HCS-Prio OPTIONAL, timeSlot-RL-SetupRspTDD TimeSlot OPTIONAL, -- This IE shall be present if Sync Case IE is Case1. -iE-Extensions ... ProtocolExtensionContainer { {RL-InformationResponse-RL-SetupRspTDD768-ExtIEs} } OPTIONAL,

RL-InformationResponse-RL-SetupRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION Neighbouring-E-UTRA-CellInformation { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION Neighbouring-UMTS-CellInformation-Ext ... } UL-CCTrCHInformationList-RL-SetupRspTDD768 ::= ProtocolIE-Single-Container {{UL-CCTrCHInformationListIEs-RL-SetupRspTDD768}} UL-CCTrCHInformationListIEs-RL-SetupRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD768 CRITICALITY ignore mandatory } }

PRESENCE optional }| PRESENCE optional },

TYPE UL-CCTrCHInformationListIE-RL-SetupRspTDD768

PRESENCE

UL-CCTrCHInformationListIE-RL-SetupRspTDD768 ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCHInformationItem-RL-SetupRspTDD768 UL-CCTrCHInformationItem-RL-SetupRspTDD768 ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-Information768 UL-DPCH-InformationList-RL-SetupRspTDD768 OPTIONAL, uL-SIR-Target-CCTrCH-InformationItem-RL-SetupRspTDD768 UL-SIR OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCHInformationItem-RL-SetupRspTDD768-ExtIEs} } OPTIONAL, ... } UL-CCTrCHInformationItem-RL-SetupRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

774

3GPP TS 25.423 V11.2.0 (2012-06)

UL-DPCH-InformationList-RL-SetupRspTDD768 ::= ProtocolIE-Single-Container { {UL-DPCH-InformationListIEs-RL-SetupRspTDD768} } UL-DPCH-InformationListIEs-RL-SetupRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationItem-RL-SetupRspTDD768 CRITICALITY ignore } TYPE UL-DPCH-InformationItem-RL-SetupRspTDD768 PRESENCE mandatory }

UL-DPCH-InformationItem-RL-SetupRspTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-Timeslot-Information768 UL-Timeslot-Information768, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationItem-RL-SetupRspTDD768-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationItem-RL-SetupRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCHInformationList-RL-SetupRspTDD768 ::= ProtocolIE-Single-Container {{DL-CCTrCHInformationListIEs-RL-SetupRspTDD768}} DL-CCTrCHInformationListIEs-RL-SetupRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD768 CRITICALITY ignore } TYPE DL-CCTrCHInformationListIE-RL-SetupRspTDD768 PRESENCE mandatory }

DL-CCTrCHInformationListIE-RL-SetupRspTDD768 ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCHInformationItem-RL-SetupRspTDD768 DL-CCTrCHInformationItem-RL-SetupRspTDD768 ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-Information768 DL-DPCH-InformationList-RL-SetupRspTDD768 OPTIONAL, cCTrCH-Maximum-DL-Power DL-Power OPTIONAL, -- this is a DCH type CCTrCH power cCTrCH-Minimum-DL-Power DL-Power OPTIONAL, -- this is a DCH type CCTrCH power iE-Extensions ProtocolExtensionContainer { {DL-CCTrCHInformationItem-RL-SetupRspTDD768-ExtIEs} } OPTIONAL, ... } DL-CCTrCHInformationItem-RL-SetupRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationList-RL-SetupRspTDD768 ::= ProtocolIE-Single-Container { {DL-DPCH-InformationListIEs-RL-SetupRspTDD768} } DL-DPCH-InformationListIEs-RL-SetupRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationItem-RL-SetupRspTDD768 CRITICALITY ignore } DL-DPCH-InformationItem-RL-SetupRspTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, TYPE DL-DPCH-InformationItem-RL-SetupRspTDD768 PRESENCE mandatory }

3GPP

Release 11
repetitionLength tDD-DPCHOffset dL-Timeslot-Information768 iE-Extensions ...

775

3GPP TS 25.423 V11.2.0 (2012-06)

RepetitionLength, TDD-DPCHOffset, DL-Timeslot-Information768, ProtocolExtensionContainer { {DL-DPCH-InformationItem-RL-SetupRspTDD768-ExtIEs} } OPTIONAL,

DL-DPCH-InformationItem-RL-SetupRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK SETUP FAILURE FDD --- ************************************************************** RadioLinkSetupFailureFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupFailureFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupFailureFDD-Extensions}} ... } RadioLinkSetupFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY { ID id-CN-PS-DomainIdentifier CRITICALITY { ID id-CN-CS-DomainIdentifier CRITICALITY { ID id-CauseLevel-RL-SetupFailureFDD CRITICALITY { ID id-UL-SIRTarget CRITICALITY { ID id-CriticalityDiagnostics CRITICALITY ... } ignore ignore ignore ignore ignore ignore TYPE TYPE TYPE TYPE TYPE TYPE D-RNTI CN-PS-DomainIdentifier CN-CS-DomainIdentifier CauseLevel-RL-SetupFailureFDD UL-SIR CriticalityDiagnostics PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional mandatory optional optional

OPTIONAL,

} | } | } | }| } | },

CauseLevel-RL-SetupFailureFDD ::= CHOICE { generalCause GeneralCauseList-RL-SetupFailureFDD, rLSpecificCause RLSpecificCauseList-RL-SetupFailureFDD, ... } GeneralCauseList-RL-SetupFailureFDD ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-SetupFailureFDD-ExtIEs} } ... } GeneralCauseItem-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RLSpecificCauseList-RL-SetupFailureFDD ::= SEQUENCE { unsuccessful-RL-InformationRespList-RL-SetupFailureFDD UnsuccessfulRL-InformationResponseList-RL-SetupFailureFDD,

OPTIONAL,

3GPP

Release 11

776

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

successful-RL-InformationRespList-RL-SetupFailureFDD SuccessfulRL-InformationResponseList-RL-SetupFailureFDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RLSpecificCauseItem-RL-SetupFailureFDD-ExtIEs} } ...

RLSpecificCauseItem-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional }| { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD-Information-Response PRESENCE optional }| { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response CRITICALITY ignore EXTENSION Continuous-PacketConnectivity-HS-SCCH-Less-Information-Response PRESENCE optional }| { ID id-SixtyfourQAM-DL-SupportIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-DL-SupportIndicator PRESENCE optional }| { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-HS-Cell-Information-Response-List PRESENCE optional }| { ID id-Additional-EDCH-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-EDCH-Cell-Information-Response-List PRESENCE optional}, ... } UnsuccessfulRL-InformationResponseList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {UnsuccessfulRLInformationResponse-RL-SetupFailureFDD-IEs} } UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD CRITICALITY ignore PRESENCE mandatory } } TYPE UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD

UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, ... } UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle PRESENCE conditional }, -- This IE shall be present if the Cause IE is set to Continuous Packet Connectivity UE DTX Cycle not Available. ... } SuccessfulRL-InformationResponseList-RL-SetupFailureFDD ::= SEQUENCE (SIZE (0..maxNrOfRLs-1)) OF ProtocolIE-Single-Container { {SuccessfulRLInformationResponse-RL-SetupFailureFDD-IEs} } SuccessfulRL-InformationResponse-RL-SetupFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-SuccessfulRL-InformationResponse-RL-SetupFailureFDD CRITICALITY ignore PRESENCE mandatory } } SuccessfulRL-InformationResponse-RL-SetupFailureFDD ::= SEQUENCE { rL-ID RL-ID, rL-Set-ID RL-Set-ID, TYPE SuccessfulRL-InformationResponse-RL-SetupFailureFDD

3GPP

Release 11

777

3GPP TS 25.423 V11.2.0 (2012-06)

uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, received-total-wide-band-power Received-total-wide-band-power, not-Used-secondary-CCPCH-Info NULL OPTIONAL, dl-CodeInformation FDD-DL-CodeInformation, diversityIndication DiversityIndication-RL-SetupFailureFDD, sSDT-SupportIndicator SSDT-SupportIndicator, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, closedlooptimingadjustmentmode Closedlooptimingadjustmentmode OPTIONAL, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, primaryCPICH-Power PrimaryCPICH-Power, primaryScramblingCode PrimaryScramblingCode OPTIONAL, uL-UARFCN UARFCN OPTIONAL, dL-UARFCN UARFCN OPTIONAL, not-Used-dSCH-InformationResponse-RL-SetupFailureFDD NULL OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, pC-Preamble PC-Preamble, sRB-Delay SRB-Delay, iE-Extensions ProtocolExtensionContainer { {SuccessfulRL-InformationResponse-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, ... } SuccessfulRL-InformationResponse-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION GA-CellAdditionalShapes PRESENCE optional { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL-PowerBalancing-ActivationIndicator PRESENCE optional { ID id-HCS-Prio CRITICALITY ignore EXTENSION HCS-Prio PRESENCE optional { ID id-Primary-CPICH-Usage-For-Channel-Estimation CRITICALITY ignore EXTENSION Primary-CPICH-Usage-For-Channel-Estimation PRESENCE optional }| { ID id-Secondary-CPICH-Information CRITICALITY ignore EXTENSION Secondary-CPICH-Information PRESENCE optional { ID id-Active-MBMS-Bearer-ServiceFDD-PFL CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListFDD-PFL PRESENCE optional { ID id-EDCH-RLSet-Id CRITICALITY ignore EXTENSION RL-Set-ID PRESENCE optional { ID id-EDCH-FDD-DL-ControlChannelInformation CRITICALITY ignore EXTENSION EDCH-FDD-DL-ControlChannelInformation PRESENCE optional { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH-TimingAdjustment PRESENCE optional { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION Neighbouring-E-UTRA-CellInformation PRESENCE optional { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION HSDSCH-PreconfigurationInfo PRESENCE optional { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION F-DPCH-SlotFormat PRESENCE optional { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Info PRESENCE optional { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION Neighbouring-UMTS-CellInformation-Ext PRESENCE optional ... } DiversityIndication-RL-SetupFailureFDD ::= CHOICE { combining Combining-RL-SetupFailureFDD, nonCombiningOrFirstRL NonCombiningOrFirstRL-RL-SetupFailureFDD } }| }| }| }| }| }| }| }| }| }| }| }| },

3GPP

Release 11

778

3GPP TS 25.423 V11.2.0 (2012-06)

Combining-RL-SetupFailureFDD ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, ... } CombiningItem-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DCH-InformationResponse CRITICALITY ignore EXTENSION DCH-InformationResponse { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } PRESENCE optional }| PRESENCE optional

},

NonCombiningOrFirstRL-RL-SetupFailureFDD ::= SEQUENCE { dCH-InformationResponse DCH-InformationResponse, iE-Extensions ProtocolExtensionContainer { { NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs} } OPTIONAL, ... } NonCombiningOrFirstRLItem-RL-SetupFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } RadioLinkSetupFailureFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK SETUP FAILURE TDD --- ************************************************************** RadioLinkSetupFailureTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkSetupFailureTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkSetupFailureTDD-Extensions}} ... } RadioLinkSetupFailureTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CauseLevel-RL-SetupFailureTDD CRITICALITY ignore { ID id-CriticalityDiagnostics CRITICALITY ignore ... } CauseLevel-RL-SetupFailureTDD ::= CHOICE { generalCause GeneralCauseList-RL-SetupFailureTDD, rLSpecificCause RLSpecificCauseList-RL-SetupFailureTDD, ... } TYPE CauseLevel-RL-SetupFailureTDD TYPE CriticalityDiagnostics PRESENCE optional },

OPTIONAL,

PRESENCE mandatory }| PRESENCE optional },

3GPP

Release 11

779

3GPP TS 25.423 V11.2.0 (2012-06)

GeneralCauseList-RL-SetupFailureTDD ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-SetupFailureTDD-ExtIEs} } ... } GeneralCauseItem-RL-SetupFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RLSpecificCauseList-RL-SetupFailureTDD ::= SEQUENCE { unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD iE-Extensions OPTIONAL, ... }

OPTIONAL,

Unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD, ProtocolExtensionContainer { { RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs} }

RLSpecificCauseItem-RL-SetupFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-SixtyfourQAM-DL-SupportIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-DL-SupportIndicator ... }

PRESENCE optional },

Unsuccessful-RL-InformationRespItem-RL-SetupFailureTDD ::= ProtocolIE-Single-Container { {Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD} } Unsuccessful-RL-InformationRespItemIE-RL-SetupFailureTDD RNSAP-PROTOCOL-IES ::= { { ID id-UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD CRITICALITY ignore SetupFailureTDD PRESENCE mandatory } } TYPE UnsuccessfulRL-InformationResponse-RL-

UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD-ExtIEs} } OPTIONAL, ... } UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkSetupFailureTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK ADDITION REQUEST FDD --- **************************************************************

3GPP

Release 11

780

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RadioLinkAdditionRequestFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionRequestFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionRequestFDD-Extensions}} ... }

RadioLinkAdditionRequestFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-SIRTarget CRITICALITY reject TYPE UL-SIR PRESENCE mandatory } | { ID id-RL-InformationList-RL-AdditionRqstFDD CRITICALITY notify TYPE RL-InformationList-RL-AdditionRqstFDD PRESENCE mandatory { ID id-Active-Pattern-Sequence-Information CRITICALITY reject TYPE Active-Pattern-Sequence-Information PRESENCE optional }, ... } RL-InformationList-RL-AdditionRqstFDD AdditionRqstFDD-IEs} } ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container { {RL-Information-RL-

}|

RL-Information-RL-AdditionRqstFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-AdditionRqstFDD CRITICALITY notify }

TYPE RL-Information-RL-AdditionRqstFDD

PRESENCE mandatory

RL-Information-RL-AdditionRqstFDD ::= SEQUENCE { rL-ID RL-ID, c-ID C-ID, frameOffset FrameOffset, chipOffset ChipOffset, diversityControlField DiversityControlField, primaryCPICH-EcNo PrimaryCPICH-EcNo OPTIONAL, not-Used-sSDT-CellID NULL OPTIONAL, transmitDiversityIndicator TransmitDiversityIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-AdditionRqstFDD-ExtIEs} } OPTIONAL, ... } RL-Information-RL-AdditionRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DLReferencePower CRITICALITY ignore { ID id-Enhanced-PrimaryCPICH-EcNo CRITICALITY ignore { ID id-RL-Specific-DCH-Info CRITICALITY ignore { ID id-DelayedActivation CRITICALITY reject { ID id-RL-Specific-EDCH-Information CRITICALITY reject { ID id-EDCH-RL-Indication CRITICALITY reject { ID id-SynchronisationIndicator CRITICALITY ignore { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore { ID id-FTPICH-Information CRITICALITY ignore ... } RadioLinkAdditionRequestFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ID id-DPC-Mode CRITICALITY { ID id-Permanent-NAS-UE-Identity CRITICALITY { ID id-Serving-EDCHRL-Id CRITICALITY EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION DL-Power Enhanced-PrimaryCPICH-EcNo RL-Specific-DCH-Info DelayedActivation RL-Specific-EDCH-Information EDCH-RL-Indication SynchronisationIndicator HSDSCH-PreconfigurationSetup Non-Serving-RL-Preconfig-Setup FTPICH-Information PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional optional optional optional optional }| }| }| }| }| }| }| }| }| },

{ reject ignore reject

EXTENSION DPC-Mode EXTENSION Permanent-NAS-UE-Identity EXTENSION EDCH-Serving-RL

PRESENCE optional}| PRESENCE optional}| PRESENCE optional}|

3GPP

Release 11
{ ID id-Initial-DL-DPCH-TimingAdjustment-Allowed CRITICALITY { ID id-HS-DSCH-serving-cell-change-information CRITICALITY { ID id-Serving-cell-change-CFN CRITICALITY { ID id-EDPCH-Information CRITICALITY { ID id-EDCH-FDD-Information CRITICALITY { ID id-Additional-HS-Cell-Information-RL-Addition CRITICALITY optional}| -- This IE shall be present if E-DPCH Information is present { ID id-UE-AggregateMaximumBitRate CRITICALITY { ID id-Additional-EDCH-Cell-Information-RL-Add-Req CRITICALITY optional}| { ID id-UL-CLTD-Information CRITICALITY ... } ignore reject reject reject reject reject ignore reject reject

781
EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION

3GPP TS 25.423 V11.2.0 (2012-06)

Initial-DL-DPCH-TimingAdjustment-Allowed PRESENCE optional}| HS-DSCH-serving-cell-change-information PRESENCE optional}| CFN PRESENCE optional}| EDPCH-Information-RLAdditionReq-FDD PRESENCE optional}| EDCH-FDD-Information PRESENCE optional}| Additional-HS-Cell-Information-RL-Addition-List PRESENCE

EXTENSION UE-AggregateMaximumBitRate PRESENCE optional}| EXTENSION Additional-EDCH-Cell-Information-RL-Add-Req PRESENCE EXTENSION UL-CLTD-Information PRESENCE optional},

Additional-HS-Cell-Information-RL-Addition-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Addition-ItemIEs

Additional-HS-Cell-Information-RL-Addition-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, c-ID C-ID, hS-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Addition-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Information-RL-Addition-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-Cell-Information-RL-Add-Req ::=SEQUENCE{ setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency Setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Add-Req-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-RL-Add-Req-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Setup-Or-Addition-Of-EDCH-On-secondary-UL-Frequency::= CHOICE { setup Additional-EDCH-Setup-Info, addition Additional-EDCH-Cell-Information-To-Add-List, ... } EDPCH-Information-RLAdditionReq-FDD::= SEQUENCE { maxSet-E-DPDCHs Max-Set-E-DPDCHs, ul-PunctureLimit PunctureLimit, e-TFCS-Information E-TFCS-Information,

3GPP

Release 11
e-TTI e-DPCCH-PO e-RGCH-2-IndexStepThreshold e-RGCH-3-IndexStepThreshold hARQ-Info-for-E-DCH iE-Extensions ...

782

3GPP TS 25.423 V11.2.0 (2012-06)

E-TTI, E-DPCCH-PO, E-RGCH-2-IndexStepThreshold, E-RGCH-3-IndexStepThreshold, HARQ-Info-for-E-DCH, ProtocolExtensionContainer { { EDPCH-Information-RLAdditionReq-FDD-ExtIEs} }

OPTIONAL,

EDPCH-Information-RLAdditionReq-FDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-Configured-Indicator CRITICALITY reject EXTENSION HSDSCH-Configured-Indicator -- This shall be present for EDPCH configuration with HSDCH { ID id-MinimumReducedE-DPDCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE-DPDCH-GainFactor ... } -- ************************************************************** --- RADIO LINK ADDITION REQUEST TDD --- ************************************************************** RadioLinkAdditionRequestTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionRequestTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionRequestTDD-Extensions}} ... } RadioLinkAdditionRequestTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-AdditionRqstTDD CRITICALITY reject ... } TYPE RL-Information-RL-AdditionRqstTDD

PRESENCE mandatory}| PRESENCE optional },

OPTIONAL,

PRESENCE mandatory

},

RL-Information-RL-AdditionRqstTDD ::= SEQUENCE { rL-ID RL-ID, c-ID C-ID, frameOffset FrameOffset, diversityControlField DiversityControlField, primaryCCPCH-RSCP PrimaryCCPCH-RSCP OPTIONAL, dL-TimeSlot-ISCP-Info DL-TimeSlot-ISCP-Info OPTIONAL, --for 3.84Mcps TDD only iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-AdditionRqstTDD-ExtIEs} } OPTIONAL, ... } RL-Information-RL-AdditionRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-Timeslot-ISCP-LCR-Information-RL-AdditionRqstTDD CRITICALITY reject EXTENSION DL-TimeSlot-ISCP-LCR-Information PRESENCE optional }| --for 1.28Mcps TDD only { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info PRESENCE optional }| { ID id-DelayedActivation CRITICALITY reject EXTENSION DelayedActivation PRESENCE optional }|

3GPP

Release 11

783
EXTENSION UL-Synchronisation-Parameters-LCR TDD EXTENSION PrimaryCCPCH-RSCP-Delta EXTENSION NULL

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional }| PRESENCE optional }| PRESENCE optional },

{ ID id-UL-Synchronisation-Parameters-LCR CRITICALITY reject -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps { ID id-PrimaryCCPCH-RSCP-Delta CRITICALITY ignore { ID id-IdleIntervalConfigurationIndicator CRITICALITY ignore ...

RadioLinkAdditionRequestTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Permanent-NAS-UE-Identity CRITICALITY ignore EXTENSION Permanent-NAS-UE-Identity PRESENCE optional}| { ID id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD CRITICALITY notify EXTENSION UL-CCTrCH-InformationList-RL-AdditionRqstTDD PRESENCE optional}| { ID id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD CRITICALITY notify EXTENSION DL-CCTrCH-InformationList-RL-AdditionRqstTDD PRESENCE optional}| { ID id-HSDSCH-TDD-Information CRITICALITY reject EXTENSION HSDSCH-TDD-Information PRESENCE optional}| { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE optional}| { ID id-E-DCH-Information CRITICALITY reject EXTENSION E-DCH-Information PRESENCE optional}| { ID id-E-DCH-Serving-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE optional}| { ID id-E-DCH-768-Information CRITICALITY reject EXTENSION E-DCH-768-Information PRESENCE optional}| { ID id-E-DCH-LCR-Information CRITICALITY reject EXTENSION E-DCH-LCR-Information PRESENCE optional}| { ID id-ContinuousPacketConnectivity-DRX-InformationLCR CRITICALITY reject EXTENSION ContinuousPacketConnectivity-DRX-InformationLCR PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION HS-DSCH-Semi-PersistentScheduling-Information-LCR PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-LCR CRITICALITY reject EXTENSION E-DCH-Semi-PersistentScheduling-Information-LCR PRESENCE optional}| { ID id-DCH-MeasurementType-Indicator CRITICALITY reject EXTENSION DCH-MeasurementType-Indicator PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Setup CRITICALITY reject EXTENSION Multi-Carrier-EDCH-Info PRESENCE optional}| { ID id-MU-MIMO-Indicator CRITICALITY reject EXTENSION MU-MIMO-Indicator PRESENCE optional}, ... } UL-CCTrCH-InformationList-RL-AdditionRqstTDD RL-AdditionRqstTDD} } ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-InformationItemIEs-

UL-CCTrCH-InformationItemIEs-RL-AdditionRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationItem-RL-AdditionRqstTDD CRITICALITY notify optional}, ... }

TYPE UL-CCTrCH-InformationItem-RL-AdditionRqstTDD

PRESENCE

UL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, uplinkStepSizeLCR TDD-TPC-UplinkStepSize-LCR OPTIONAL, -- Applicable to 1.28Mcps TDD only iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
DL-CCTrCH-InformationList-RL-AdditionRqstTDD RL-AdditionRqstTDD} }

784

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-InformationItemIEs-

DL-CCTrCH-InformationItemIEs-RL-AdditionRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationItem-RL-AdditionRqstTDD CRITICALITY notify optional}, ... }

TYPE DL-CCTrCH-InformationItem-RL-AdditionRqstTDD

PRESENCE

DL-CCTrCH-InformationItem-RL-AdditionRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, downlinkStepSize TDD-TPC-DownlinkStepSize OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationItem-RL-AdditionRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK ADDITION RESPONSE FDD --- ************************************************************** RadioLinkAdditionResponseFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionResponseFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionResponseFDD-Extensions}} ... }

OPTIONAL,

RadioLinkAdditionResponseFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseList-RL-AdditionRspFDD CRITICALITY ignore TYPE RL-InformationResponseList-RL-AdditionRspFDD mandatory } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } RL-InformationResponseList-RL-AdditionRspFDD InformationResponseItemIEs-RL-AdditionRspFDD} } ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container { {RL-

PRESENCE

RL-InformationResponseItemIEs-RL-AdditionRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseItem-RL-AdditionRspFDD CRITICALITY ignore mandatory } } RL-InformationResponseItem-RL-AdditionRspFDD ::= SEQUENCE { rL-ID RL-ID, rL-Set-ID RL-Set-ID,

TYPE RL-InformationResponseItem-RL-AdditionRspFDD

PRESENCE

3GPP

Release 11
uRA-Information sAI gA-Cell gA-AccessPointPosition received-total-wide-band-power not-Used-secondary-CCPCH-Info dl-CodeInformation diversityIndication

785
URA-Information OPTIONAL, SAI, GA-Cell OPTIONAL, GA-AccessPointPosition OPTIONAL, Received-total-wide-band-power, NULL OPTIONAL, DL-CodeInformationList-RL-AdditionRspFDD, DiversityIndication-RL-AdditionRspFDD,

3GPP TS 25.423 V11.2.0 (2012-06)

sSDT-SupportIndicator minUL-SIR maxUL-SIR closedlooptimingadjustmentmode maximumAllowedULTxPower maximumDLTxPower minimumDLTxPower neighbouring-UMTS-CellInformation neighbouring-GSM-CellInformation pC-Preamble sRB-Delay primaryCPICH-Power iE-Extensions ...

SSDT-SupportIndicator, UL-SIR, UL-SIR, Closedlooptimingadjustmentmode OPTIONAL, MaximumAllowedULTxPower, DL-Power, DL-Power, Neighbouring-UMTS-CellInformation OPTIONAL, Neighbouring-GSM-CellInformation OPTIONAL, PC-Preamble, SRB-Delay, PrimaryCPICH-Power, ProtocolExtensionContainer { {RL-InformationResponseItem-RL-AdditionRspFDD-ExtIEs} } OPTIONAL,

RL-InformationResponseItem-RL-AdditionRspFDD-ExtIEs { ID id-GA-CellAdditionalShapes { ID id-DL-PowerBalancing-ActivationIndicator { ID id-HCS-Prio { ID id-Active-MBMS-Bearer-ServiceFDD-PFL { ID id-EDCH-RLSet-Id { ID id-EDCH-FDD-DL-ControlChannelInformation { ID id-Initial-DL-DPCH-TimingAdjustment { ID id-F-DPCH-SlotFormat { ID id-Neighbouring-E-UTRA-CellInformation { ID id-HSDSCH-PreconfigurationInfo { ID id-Non-Serving-RL-Preconfig-Info { ID id-Neighbouring-UMTS-CellInformation-Ext ... }

RNSAP-PROTOCOL-EXTENSION ::= { CRITICALITY ignore EXTENSION GA-CellAdditionalShapes CRITICALITY ignore EXTENSION DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION HCS-Prio CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListFDD-PFL CRITICALITY ignore EXTENSION RL-Set-ID CRITICALITY ignore EXTENSION EDCH-FDD-DL-ControlChannelInformation CRITICALITY ignore EXTENSION DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION F-DPCH-SlotFormat CRITICALITY ignore EXTENSION Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION Neighbouring-UMTS-CellInformation-Ext

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

optional optional optional optional optional optional optional optional optional optional optional optional

}| }| }| }| }| }| }| }| }| }| }| },

DL-CodeInformationList-RL-AdditionRspFDD ::= ProtocolIE-Single-Container {{ DL-CodeInformationListIEs-RL-AdditionRspFDD }} DL-CodeInformationListIEs-RL-AdditionRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-FDD-DL-CodeInformation CRITICALITY ignore TYPE FDD-DL-CodeInformation } DiversityIndication-RL-AdditionRspFDD ::= CHOICE { combining Combining-RL-AdditionRspFDD, nonCombining NonCombining-RL-AdditionRspFDD } PRESENCE mandatory }

3GPP

Release 11

786

3GPP TS 25.423 V11.2.0 (2012-06)

Combining-RL-AdditionRspFDD ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL-AdditionRspFDD-ExtIEs} } OPTIONAL, ... } CombiningItem-RL-AdditionRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DCH-InformationResponse CRITICALITY ignore EXTENSION DCH-InformationResponse { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } PRESENCE optional }| PRESENCE optional

},

NonCombining-RL-AdditionRspFDD ::= SEQUENCE { dCH-InformationResponse DCH-InformationResponse, iE-Extensions ProtocolExtensionContainer { { NonCombiningItem-RL-AdditionRspFDD-ExtIEs} } OPTIONAL, ... } NonCombiningItem-RL-AdditionRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } RadioLinkAdditionResponseFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-DSCH-serving-cell-change-informationResponse CRITICALITY PRESENCE optional}| { ID id-E-DCH-Serving-cell-change-informationResponse CRITICALITY PRESENCE optional}| { ID id-MAChs-ResetIndicator CRITICALITY PRESENCE optional}| { ID id-Additional-HS-Cell-Change-Information-Response CRITICALITY PRESENCE optional}| { ID id-Additional-EDCH-Cell-Information-Response-RLAdd CRITICALITY optional }, ... } ignore ignore ignore ignore ignore PRESENCE optional },

EXTENSION HS-DSCH-serving-cell-change-informationResponse EXTENSION E-DCH-Serving-cell-change-informationResponse EXTENSION MAChs-ResetIndicator EXTENSION Additional-HS-Cell-Change-Information-Response-List EXTENSION Additional-EDCH-Cell-Information-Response-RLAddList PRESENCE

Additional-HS-Cell-Change-Information-Response-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Change-Information-Response-ItemIEs

Additional-HS-Cell-Change-Information-Response-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, hSDSCH-RNTI HSDSCH-RNTI, hS-DSCH-Secondary-Serving-Cell-Change-Information-Response HS-DSCH-Secondary-Serving-Cell-Change-Information-Response, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Change-Information-Response-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Change-Information-Response-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

787

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- RADIO LINK ADDITION RESPONSE TDD --- ************************************************************** RadioLinkAdditionResponseTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionResponseTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionResponseTDD-Extensions}} ... } RadioLinkAdditionResponseTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponse-RL-AdditionRspTDD CRITICALITY ignore TYPE RL-InformationResponse-RL-AdditionRspTDD | --Mandatory for 3.84Mcps TDD only { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... }

OPTIONAL,

PRESENCE optional

RL-InformationResponse-RL-AdditionRspTDD ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-Info UL-TimeSlot-ISCP-Info, minUL-SIR UL-SIR, maxUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, pCCPCH-Power PCCPCH-Power, timingAdvanceApplied TimingAdvanceApplied, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-CCPCH-Info-TDD Secondary-CCPCH-Info-TDD OPTIONAL, ul-CCTrCHInformation UL-CCTrCHInformationList-RL-AdditionRspTDD OPTIONAL, dl-CCTrCHInformation DL-CCTrCHInformationList-RL-AdditionRspTDD OPTIONAL, dCH-Information DCH-Information-RL-AdditionRspTDD OPTIONAL, dSCH-InformationResponse DSCH-InformationResponse-RL-AdditionRspTDD OPTIONAL, uSCH-InformationResponse USCH-InformationResponse-RL-AdditionRspTDD OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponse-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ...

3GPP

Release 11
}

788

3GPP TS 25.423 V11.2.0 (2012-06)

RL-InformationResponse-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION { ID id-HCS-Prio CRITICALITY ignore EXTENSION { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION ... }

GA-CellAdditionalShapes HCS-Prio Neighbouring-E-UTRA-CellInformation Neighbouring-UMTS-CellInformation-Ext

PRESENCE PRESENCE PRESENCE PRESENCE

optional optional optional optional

}| }| }| },

UL-CCTrCHInformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{UL-CCTrCHInformationListIEs-RL-AdditionRspTDD}} UL-CCTrCHInformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE UL-CCTrCHInformationListIE-RL-AdditionRspTDD PRESENCE

UL-CCTrCHInformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCHInformationItem-RL-AdditionRspTDD UL-CCTrCHInformationItem-RL-AdditionRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-Information UL-DPCH-InformationList-RL-AdditionRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCHInformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCHInformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container { {UL-DPCH-InformationListIEs-RL-AdditionRspTDD} } UL-DPCH-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationItem-RL-AdditionRspTDD CRITICALITY ignore } TYPE UL-DPCH-InformationItem-RL-AdditionRspTDD PRESENCE mandatory }

UL-DPCH-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-Timeslot-Information UL-Timeslot-Information, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCHInformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{DL-CCTrCHInformationListIEs-RL-AdditionRspTDD}}

3GPP

Release 11

789

3GPP TS 25.423 V11.2.0 (2012-06)

TYPE DL-CCTrCHInformationListIE-RL-AdditionRspTDD PRESENCE

DL-CCTrCHInformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD CRITICALITY ignore mandatory } }

DL-CCTrCHInformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCHInformationItem-RL-AdditionRspTDD DL-CCTrCHInformationItem-RL-AdditionRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-Information DL-DPCH-InformationList-RL-AdditionRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCHInformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCHInformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-CCTrCH-Maximum-DL-Power-RL-AdditionRspTDD CRITICALITY ignore CCTrCH power { ID id-CCTrCH-Minimum-DL-Power-RL-AdditionRspTDD CRITICALITY ignore CCTrCH power ... } EXTENSION EXTENSION DL-Power DL-Power PRESENCE optional PRESENCE optional }| -- this is a DCH type }, -- this is a DCH type

DL-DPCH-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container { {DL-DPCH-InformationListIEs-RL-AdditionRspTDD} } DL-DPCH-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationItem-RL-AdditionRspTDD CRITICALITY ignore } TYPE DL-DPCH-InformationItem-RL-AdditionRspTDD PRESENCE mandatory }

DL-DPCH-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-Information DL-Timeslot-Information, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-Information-RL-AdditionRspTDD ::= SEQUENCE { diversityIndication DiversityIndication-RL-AdditionRspTDD, iE-Extensions ... } DCH-Information-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ProtocolExtensionContainer { { DCH-Information-RL-AdditionRspTDD-ExtIEs} } OPTIONAL,

3GPP

Release 11
DiversityIndication-RL-AdditionRspTDD ::= CHOICE { combining Combining-RL-AdditionRspTDD, nonCombining NonCombining-RL-AdditionRspTDD }

790

3GPP TS 25.423 V11.2.0 (2012-06)

Combining-RL-AdditionRspTDD ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } CombiningItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DCH-InformationResponse CRITICALITY ignore EXTENSION DCH-InformationResponse ... } NonCombining-RL-AdditionRspTDD dCH-InformationResponse iE-Extensions ... } PRESENCE optional },

::= SEQUENCE { DCH-InformationResponse, ProtocolExtensionContainer { { NonCombiningItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL,

NonCombiningItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DSCH-InformationResponse-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{DSCH-InformationListIEs-RL-AdditionRspTDD}} DSCH-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DSCH-InformationListIE-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE DSCH-InformationListIE-RL-AdditionRspTDD PRESENCE

DSCH-InformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHs)) OF DSCHInformationItem-RL-AdditionRspTDD DSCHInformationItem-RL-AdditionRspTDD ::= SEQUENCE { dsch-ID DSCH-ID, transportFormatManagement TransportFormatManagement, dSCH-FlowControlInformation DSCH-FlowControlInformation, diversityIndication DiversityIndication-RL-AdditionRspTDD2 OPTIONAL, -- diversityIndication present, if CHOICE = nonCombining iE-Extensions ProtocolExtensionContainer { {DSCHInformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } DSCHInformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DiversityIndication-RL-AdditionRspTDD2 ::= SEQUENCE {

3GPP

Release 11
bindingID transportLayerAddress iE-Extensions ...

791
BindingID OPTIONAL, TransportLayerAddress OPTIONAL, ProtocolExtensionContainer { {DiversityIndication-RL-AdditionRspTDD2-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

} DiversityIndication-RL-AdditionRspTDD2-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-InformationResponse-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{USCH-InformationListIEs-RL-AdditionRspTDD}} USCH-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-USCH-InformationListIE-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE USCH-InformationListIE-RL-AdditionRspTDD PRESENCE

USCH-InformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHs)) OF USCHInformationItem-RL-AdditionRspTDD USCHInformationItem-RL-AdditionRspTDD ::= SEQUENCE { uSCH-ID USCH-ID, transportFormatManagement TransportFormatManagement, diversityIndication DiversityIndication-RL-AdditionRspTDD2 OPTIONAL, -- diversityIndication present, if CHOICE = nonCombining iE-Extensions ProtocolExtensionContainer { {USCHInformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } USCHInformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkAdditionResponseTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RL-LCR-InformationResponse-RL-AdditionRspTDD CRITICALITY ignore EXTENSION RL-LCR-InformationResponse-RL-AdditionRspTDD PRESENCE optional}| --Mandatory for 1.28Mcps TDD only { ID id-Active-MBMS-Bearer-ServiceTDD-PFL CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListTDD-PFL PRESENCE optional}| { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD-Information-Response PRESENCE optional}| { ID id-DSCH-RNTI CRITICALITY ignore EXTENSION DSCH-RNTI PRESENCE optional}| { ID id-RL-InformationResponse-RL-AdditionRspTDD768 CRITICALITY ignore EXTENSION RL-InformationResponse-RL-AdditionRspTDD768 PRESENCE optional}| { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH-Information-Response PRESENCE optional}| { ID id-E-DCH-768-Information-Response CRITICALITY ignore EXTENSION E-DCH-768-Information-Response PRESENCE optional}| { ID id-E-DCH-LCR-Information-Response CRITICALITY ignore EXTENSION E-DCH-LCR-Information-Response PRESENCE optional}| { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore EXTENSION ContinuousPacketConnectivity-DRX-InformationResponseLCR PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION HS-DSCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION E-DCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH-MeasurementOccasion-Information PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier-EDCH-Information-Response PRESENCE optional}|

3GPP

Release 11
{ ID id-MU-MIMO-InformationLCR ... } CRITICALITY reject

792
EXTENSION MU-MIMO-InformationLCR

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional},

RL-LCR-InformationResponse-RL-AdditionRspTDD ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-LCR-Info UL-TimeSlot-ISCP-LCR-Info, maxUL-SIR UL-SIR, minUL-SIR UL-SIR, pCCPCH-Power PCCPCH-Power, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-LCR-CCPCH-Info-TDD Secondary-LCR-CCPCH-Info-TDD OPTIONAL, ul-CCTrCH-LCR-Information UL-CCTrCH-LCR-InformationList-RL-AdditionRspTDD OPTIONAL, dl-CCTrCH-LCR-Information DL-CCTrCH-LCR-InformationList-RL-AdditionRspTDD OPTIONAL, dCH-InformationResponse DCH-InformationResponseList-RL-AdditionRspTDD OPTIONAL, dsch-LCR-InformationResponse DSCH-LCR-InformationResponse-RL-AdditionRspTDD OPTIONAL, usch-LCR-InformationResponse USCH-LCR-InformationResponse-RL-AdditionRspTDD OPTIONAL, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-LCR-InformationResponseList-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } RL-LCR-InformationResponseList-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION GA-CellAdditionalShapes { ID id-HCS-Prio CRITICALITY ignore EXTENSION HCS-Prio { ID id-UL-TimingAdvanceCtrl-LCR CRITICALITY ignore EXTENSION UL-TimingAdvanceCtrl-LCR --Mandatory for 1.28Mcps TDD only { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP -- Applicable to 1.28Mcps TDD only { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN -- Applicable to 1.28Mcps TDD only { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION Neighbouring-E-UTRA-CellInformation { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION IdleIntervalInformation { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION Neighbouring-UMTS-CellInformation-Ext ... } PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional },

UL-CCTrCH-LCR-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{UL-CCTrCH-LCR-InformationListIEs-RL-AdditionRspTDD }} UL-CCTrCH-LCR-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= {

3GPP

Release 11
{ ID id-UL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD PRESENCE mandatory } }

793
CRITICALITY ignore

3GPP TS 25.423 V11.2.0 (2012-06)

TYPE UL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD

UL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHsLCR)) OF UL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD UL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-LCR-Information UL-DPCH-LCR-InformationList-RL-AdditionRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-LCR-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container { {UL-DPCH-LCR-InformationListIEs-RL-AdditionRspTDD} } UL-DPCH-LCR-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD PRESENCE

UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-TimeslotLCR-Information UL-TimeslotLCR-Information, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-LCR-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{DL-CCTrCH-LCR-InformationListIEs-RL-AdditionRspTDD}} DL-CCTrCH-LCR-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE DL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD PRESENCE

DL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHsLCR)) OF DL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD DL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-LCR-Information DL-DPCH-LCR-InformationList-RL-AdditionRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ...

3GPP

Release 11
}

794

3GPP TS 25.423 V11.2.0 (2012-06)

DL-CCTrCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-LCR-InformationList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container { {DL-DPCH-LCR-InformationListIEs-RL-AdditionRspTDD} } DL-DPCH-LCR-InformationListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD PRESENCE

DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-TimeslotLCR-Information DL-TimeslotLCR-Information, tSTD-Indicator TSTD-Indicator, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-InformationResponseList-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{DCH-InformationResponseListIEs-RL-AdditionRspTDD}} DCH-InformationResponseListIEs-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse } PRESENCE mandatory }

DSCH-LCR-InformationResponse-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{DSCH-LCR-InformationList-RL-AdditionRspTDD}} DSCH-LCR-InformationList-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DSCH-LCR-InformationListIEs-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE DSCH-LCR-InformationListIEs-RL-AdditionRspTDD PRESENCE

DSCH-LCR-InformationListIEs-RL-AdditionRspTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHsLCR)) OF DSCH-LCR-InformationItem-RL-AdditionRspTDD DSCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { dsch-ID DSCH-ID, dSCH-FlowControlInformation DSCH-FlowControlInformation, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, transportFormatManagement TransportFormatManagement, iE-Extensions ProtocolExtensionContainer { {DSCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

795

3GPP TS 25.423 V11.2.0 (2012-06)

DSCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-LCR-InformationResponse-RL-AdditionRspTDD ::= ProtocolIE-Single-Container {{USCH-LCR-InformationList-RL-AdditionRspTDD}} USCH-LCR-InformationList-RL-AdditionRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-USCH-LCR-InformationListIEs-RL-AdditionRspTDD CRITICALITY ignore mandatory } } TYPE USCH-LCR-InformationListIEs-RL-AdditionRspTDD PRESENCE

USCH-LCR-InformationListIEs-RL-AdditionRspTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHsLCR)) OF USCH-LCR-InformationItem-RL-AdditionRspTDD USCH-LCR-InformationItem-RL-AdditionRspTDD ::= SEQUENCE { usch-ID USCH-ID, transportFormatManagement TransportFormatManagement, diversityIndication DiversityIndication-RL-AdditionRspTDD2 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {USCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs} } OPTIONAL, ... } USCH-LCR-InformationItem-RL-AdditionRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationResponse-RL-AdditionRspTDD768 ::= SEQUENCE { rL-ID RL-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, ul-TimeSlot-ISCP-Info UL-TimeSlot-ISCP-Info, minUL-SIR UL-SIR, maxUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, pCCPCH-Power PCCPCH-Power, timingAdvanceApplied TimingAdvanceApplied, alphaValue AlphaValue, ul-PhysCH-SF-Variation UL-PhysCH-SF-Variation, synchronisationConfiguration SynchronisationConfiguration, secondary-CCPCH-Info-TDD768 Secondary-CCPCH-Info-TDD768 ul-CCTrCHInformation768 UL-CCTrCHInformationList-RL-AdditionRspTDD768 dl-CCTrCHInformation768 DL-CCTrCHInformationList-RL-AdditionRspTDD768 dCH-Information DCH-Information-RL-AdditionRspTDD dSCH-InformationResponse DSCH-InformationResponse-RL-AdditionRspTDD uSCH-InformationResponse USCH-InformationResponse-RL-AdditionRspTDD neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11
gA-CellAdditionalShapes hCS-Prio iE-Extensions ... }

796

3GPP TS 25.423 V11.2.0 (2012-06)

GA-CellAdditionalShapes OPTIONAL, HCS-Prio OPTIONAL, ProtocolExtensionContainer { {RL-InformationResponse-RL-AdditionRspTDD768-ExtIEs} } OPTIONAL,

RL-InformationResponse-RL-AdditionRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Neighbouring-E-UTRA-CellInformation CRITICALITY ignore EXTENSION Neighbouring-E-UTRA-CellInformation { ID id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY ignore EXTENSION Neighbouring-UMTS-CellInformation-Ext ... }

PRESENCE optional }| PRESENCE optional },

UL-CCTrCHInformationList-RL-AdditionRspTDD768 ::= ProtocolIE-Single-Container {{UL-CCTrCHInformationListIEs-RL-AdditionRspTDD768}} UL-CCTrCHInformationListIEs-RL-AdditionRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD768 CRITICALITY ignore PRESENCE mandatory } } TYPE UL-CCTrCHInformationListIE-RL-AdditionRspTDD768

UL-CCTrCHInformationListIE-RL-AdditionRspTDD768 ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCHInformationItem-RL-AdditionRspTDD768 UL-CCTrCHInformationItem-RL-AdditionRspTDD768 ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-Information768 UL-DPCH-InformationList-RL-AdditionRspTDD768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCHInformationItem-RL-AdditionRspTDD768-ExtIEs} } OPTIONAL, ... } UL-CCTrCHInformationItem-RL-AdditionRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-InformationList-RL-AdditionRspTDD768 ::= ProtocolIE-Single-Container { {UL-DPCH-InformationListIEs-RL-AdditionRspTDD768} } UL-DPCH-InformationListIEs-RL-AdditionRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationItem-RL-AdditionRspTDD CRITICALITY ignore } TYPE UL-DPCH-InformationItem-RL-AdditionRspTDD768 PRESENCE mandatory }

UL-DPCH-InformationItem-RL-AdditionRspTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-Timeslot-Information768 UL-Timeslot-Information768, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationItem-RL-AdditionRspTDD768-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationItem-RL-AdditionRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

797

3GPP TS 25.423 V11.2.0 (2012-06)

DL-CCTrCHInformationList-RL-AdditionRspTDD768 ::= ProtocolIE-Single-Container {{DL-CCTrCHInformationListIEs-RL-AdditionRspTDD768}} DL-CCTrCHInformationListIEs-RL-AdditionRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD768 CRITICALITY ignore PRESENCE mandatory } } TYPE DL-CCTrCHInformationListIE-RL-AdditionRspTDD768

DL-CCTrCHInformationListIE-RL-AdditionRspTDD768 ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCHInformationItem-RL-AdditionRspTDD768 DL-CCTrCHInformationItem-RL-AdditionRspTDD768 ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-Information768 DL-DPCH-InformationList-RL-AdditionRspTDD768 OPTIONAL, cCTrCH-Maximum-DL-Power DL-Power OPTIONAL,-- this is a DCH type CCTrCH power cCTrCH-Minimum-DL-Power DL-Power OPTIONAL, -- this is a DCH type CCTrCH power iE-Extensions ProtocolExtensionContainer { {DL-CCTrCHInformationItem-RL-AdditionRspTDD768-ExtIEs} } OPTIONAL, ... } DL-CCTrCHInformationItem-RL-AdditionRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationList-RL-AdditionRspTDD768 ::= ProtocolIE-Single-Container { {DL-DPCH-InformationListIEs-RL-AdditionRspTDD768} } DL-DPCH-InformationListIEs-RL-AdditionRspTDD768 RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationItem-RL-AdditionRspTDD768 CRITICALITY ignore mandatory } } TYPE DL-DPCH-InformationItem-RL-AdditionRspTDD768 PRESENCE

DL-DPCH-InformationItem-RL-AdditionRspTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-Information768 DL-Timeslot-Information768, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationItem-RL-AdditionRspTDD768-ExtIEs} } OPTIONAL, ... } DL-DPCH-InformationItem-RL-AdditionRspTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK ADDITION FAILURE FDD --- ************************************************************** RadioLinkAdditionFailureFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionFailureFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionFailureFDD-Extensions}}

OPTIONAL,

3GPP

Release 11
} ...

798

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkAdditionFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CauseLevel-RL-AdditionFailureFDD PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore ... }

CRITICALITY

ignore

TYPE CauseLevel-RL-AdditionFailureFDD PRESENCE optional },

TYPE CriticalityDiagnostics

CauseLevel-RL-AdditionFailureFDD ::= CHOICE { generalCause GeneralCauseList-RL-AdditionFailureFDD, rLSpecificCause RLSpecificCauseList-RL-AdditionFailureFDD, ... } GeneralCauseList-RL-AdditionFailureFDD ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-AdditionFailureFDD-ExtIEs} } ... } GeneralCauseItem-RL-AdditionFailureFDD-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

RLSpecificCauseList-RL-AdditionFailureFDD ::= SEQUENCE { unsuccessful-RL-InformationRespList-RL-AdditionFailureFDD UnsuccessfulRL-InformationResponseList-RL-AdditionFailureFDD, successful-RL-InformationRespList-RL-AdditionFailureFDD SuccessfulRL-InformationResponseList-RL-AdditionFailureFDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RLSpecificCauseItem-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, ... } RLSpecificCauseItem-RL-AdditionFailureFDD-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

UnsuccessfulRL-InformationResponseList-RL-AdditionFailureFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container { {UnsuccessfulRLInformationResponse-RL-AdditionFailureFDD-IEs} } UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD CRITICALITY ignore AdditionFailureFDD PRESENCE mandatory } } TYPE UnsuccessfulRL-InformationResponse-RL-

UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, ...

3GPP

Release 11
}

799

3GPP TS 25.423 V11.2.0 (2012-06)

UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SuccessfulRL-InformationResponseList-RL-AdditionFailureFDD ::= SEQUENCE (SIZE (0..maxNrOfRLs-2)) OF ProtocolIE-Single-Container { {SuccessfulRLInformationResponse-RL-AdditionFailureFDD-IEs} } SuccessfulRL-InformationResponse-RL-AdditionFailureFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-SuccessfulRL-InformationResponse-RL-AdditionFailureFDD CRITICALITY ignore PRESENCE mandatory } } TYPE SuccessfulRL-InformationResponse-RL-AdditionFailureFDD

SuccessfulRL-InformationResponse-RL-AdditionFailureFDD ::= SEQUENCE { rL-ID RL-ID, rL-Set-ID RL-Set-ID, uRA-Information URA-Information OPTIONAL, sAI SAI, gA-Cell GA-Cell OPTIONAL, gA-AccessPointPosition GA-AccessPointPosition OPTIONAL, received-total-wide-band-power Received-total-wide-band-power, not-Used-secondary-CCPCH-Info NULL OPTIONAL, dl-CodeInformation DL-CodeInformationList-RL-AdditionFailureFDD, diversityIndication DiversityIndication-RL-AdditionFailureFDD, -- This IE represents both the Diversity Indication IE and the choice based on the diversity indication as described in -- the tabular message format in subclause 9.1. sSDT-SupportIndicator SSDT-SupportIndicator, minUL-SIR UL-SIR, maxUL-SIR UL-SIR, closedlooptimingadjustmentmode Closedlooptimingadjustmentmode OPTIONAL, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDLTxPower DL-Power, minimumDLTxPower DL-Power, neighbouring-UMTS-CellInformation Neighbouring-UMTS-CellInformation OPTIONAL, neighbouring-GSM-CellInformation Neighbouring-GSM-CellInformation OPTIONAL, primaryCPICH-Power PrimaryCPICH-Power, pC-Preamble PC-Preamble, sRB-Delay SRB-Delay, iE-Extensions ProtocolExtensionContainer { {SuccessfulRL-InformationResponse-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, ... } SuccessfulRL-InformationResponse-RL-AdditionFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION GA-CellAdditionalShapes { ID id-DL-PowerBalancing-ActivationIndicator CRITICALITY ignore EXTENSION DL-PowerBalancing-ActivationIndicator { ID id-HCS-Prio CRITICALITY ignore EXTENSION HCS-Prio { ID id-Active-MBMS-Bearer-ServiceFDD-PFL CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListFDD-PFL { ID id-EDCH-RLSet-Id CRITICALITY ignore EXTENSION RL-Set-ID { ID id-EDCH-FDD-DL-ControlChannelInformation CRITICALITY ignore EXTENSION EDCH-FDD-DL-ControlChannelInformation { ID id-Initial-DL-DPCH-TimingAdjustment CRITICALITY ignore EXTENSION DL-DPCH-TimingAdjustment PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional optional }| }| }| }| }| }| }|

3GPP

Release 11
{ ID { ID { ID { ID { ID ... } id-Neighbouring-E-UTRA-CellInformation id-HSDSCH-PreconfigurationInfo id-F-DPCH-SlotFormat id-Non-Serving-RL-Preconfig-Info id-Neighbouring-UMTS-CellInformation-Ext CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY ignore ignore ignore ignore ignore

800
EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION

3GPP TS 25.423 V11.2.0 (2012-06)

Neighbouring-E-UTRA-CellInformation HSDSCH-PreconfigurationInfo F-DPCH-SlotFormat Non-Serving-RL-Preconfig-Info Neighbouring-UMTS-CellInformation-Ext PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional }| }| }| }| },

DL-CodeInformationList-RL-AdditionFailureFDD ::= ProtocolIE-Single-Container {{ DL-CodeInformationListIEs-RL-AdditionFailureFDD }} DL-CodeInformationListIEs-RL-AdditionFailureFDD RNSAP-PROTOCOL-IES ::= { { ID id-FDD-DL-CodeInformation CRITICALITY ignore TYPE FDD-DL-CodeInformation } DiversityIndication-RL-AdditionFailureFDD ::= CHOICE { combining Combining-RL-AdditionFailureFDD, nonCombining NonCombining-RL-AdditionFailureFDD } Combining-RL-AdditionFailureFDD ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { CombiningItem-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, ... } CombiningItem-RL-AdditionFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DCH-InformationResponse CRITICALITY ignore EXTENSION DCH-InformationResponse { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } PRESENCE optional }| PRESENCE optional PRESENCE mandatory }

},

NonCombining-RL-AdditionFailureFDD ::= SEQUENCE { dCH-InformationResponse DCH-InformationResponse, iE-Extensions ProtocolExtensionContainer { { NonCombiningItem-RL-AdditionFailureFDD-ExtIEs} } OPTIONAL, ... } NonCombiningItem-RL-AdditionFailureFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION EDCH-FDD-InformationResponse ... } RadioLinkAdditionFailureFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-DSCH-serving-cell-change-informationResponse CRITICALITY PRESENCE optional}| { ID id-E-DCH-Serving-cell-change-informationResponse CRITICALITY PRESENCE optional}| { ID id-Additional-HS-Cell-Change-Information-Response CRITICALITY PRESENCE optional}| { ID id-MAChs-ResetIndicator CRITICALITY PRESENCE optional}| ignore ignore ignore ignore PRESENCE optional },

EXTENSION HS-DSCH-serving-cell-change-informationResponse EXTENSION E-DCH-Serving-cell-change-informationResponse EXTENSION Additional-HS-Cell-Change-Information-Response-List EXTENSION MAChs-ResetIndicator

3GPP

Release 11

801

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION Additional-EDCH-Cell-Information-Response-RLAddList

{ ID id-Additional-EDCH-Cell-Information-Response-RLAdd CRITICALITY ignore PRESENCE optional }, ...

-- ************************************************************** --- RADIO LINK ADDITION FAILURE TDD --- ************************************************************** RadioLinkAdditionFailureTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkAdditionFailureTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkAdditionFailureTDD-Extensions}} ... }

OPTIONAL,

RadioLinkAdditionFailureTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CauseLevel-RL-AdditionFailureTDD CRITICALITY ignore TYPE CauseLevel-RL-AdditionFailureTDD PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } CauseLevel-RL-AdditionFailureTDD ::= CHOICE { generalCause GeneralCauseList-RL-AdditionFailureTDD, rLSpecificCause RLSpecificCauseList-RL-AdditionFailureTDD, ... } GeneralCauseList-RL-AdditionFailureTDD ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-AdditionFailureTDD-ExtIEs} } ... } GeneralCauseItem-RL-AdditionFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RLSpecificCauseList-RL-AdditionFailureTDD ::= SEQUENCE { unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD iE-Extensions OPTIONAL, ... } Unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD, ProtocolExtensionContainer { { RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs} }

OPTIONAL,

RLSpecificCauseItem-RL-AdditionFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

802

3GPP TS 25.423 V11.2.0 (2012-06)

Unsuccessful-RL-InformationRespItem-RL-AdditionFailureTDD ::= ProtocolIE-Single-Container { {Unsuccessful-RL-InformationRespItemIE-RLAdditionFailureTDD} } Unsuccessful-RL-InformationRespItemIE-RL-AdditionFailureTDD RNSAP-PROTOCOL-IES ::= { { ID id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD CRITICALITY ignore AdditionFailureTDD PRESENCE mandatory} } TYPE UnsuccessfulRL-InformationResponse-RL-

UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD-ExtIEs} } OPTIONAL, ... } UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkAdditionFailureTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK DELETION REQUEST --- ************************************************************** RadioLinkDeletionRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkDeletionRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkDeletionRequest-Extensions}} ... } RadioLinkDeletionRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationList-RL-DeletionRqst CRITICALITY notify ... } RL-InformationList-RL-DeletionRqst TYPE RL-InformationList-RL-DeletionRqst

OPTIONAL,

PRESENCE mandatory

},

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-RL-DeletionRqst-IEs} } TYPE RL-Information-RL-DeletionRqst PRESENCE mandatory }

RL-Information-RL-DeletionRqst-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-DeletionRqst CRITICALITY notify }

RL-Information-RL-DeletionRqst ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-DeletionRqst-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11
RL-Information-RL-DeletionRqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkDeletionRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK DELETION RESPONSE --- **************************************************************

803

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkDeletionResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkDeletionResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkDeletionResponse-Extensions}} ... } RadioLinkDeletionResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CriticalityDiagnostics CRITICALITY ignore ... } TYPE CriticalityDiagnostics PRESENCE optional

OPTIONAL,

},

RadioLinkDeletionResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION PREPARE FDD --- ************************************************************** RadioLinkReconfigurationPrepareFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationPrepareFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationPrepareFDD-Extensions}} ... } RadioLinkReconfigurationPrepareFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-AllowedQueuingTime CRITICALITY reject TYPE AllowedQueuingTime PRESENCE optional } | { ID id-UL-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject TYPE UL-DPCH-Information-RL-ReconfPrepFDD optional } | { ID id-DL-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject TYPE DL-DPCH-Information-RL-ReconfPrepFDD optional } | { ID id-FDD-DCHs-to-Modify CRITICALITY reject TYPE FDD-DCHs-to-Modify PRESENCE optional } | { ID id-DCHs-to-Add-FDD CRITICALITY reject TYPE DCH-FDD-Information PRESENCE optional } | { ID id-DCH-DeleteList-RL-ReconfPrepFDD CRITICALITY reject TYPE DCH-DeleteList-RL-ReconfPrepFDD PRESENCE optional

OPTIONAL,

PRESENCE PRESENCE

} |

3GPP

Release 11

804

3GPP TS 25.423 V11.2.0 (2012-06)

}| PRESENCE

{ ID id-RL-InformationList-RL-ReconfPrepFDD CRITICALITY reject TYPE RL-InformationList-RL-ReconfPrepFDD PRESENCE optional { ID id-Transmission-Gap-Pattern-Sequence-Information CRITICALITY reject TYPE Transmission-Gap-Pattern-Sequence-Information optional }, ... } UL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { ul-ScramblingCode UL-ScramblingCode OPTIONAL, ul-SIRTarget UL-SIR OPTIONAL, minUL-ChannelisationCodeLength MinUL-ChannelisationCodeLength OPTIONAL, maxNrOfUL-DPDCHs MaxNrOfUL-DPCHs OPTIONAL -- This IE shall be present if minUL-ChannelisationCodeLength equals to 4 --, ul-PunctureLimit PunctureLimit OPTIONAL, tFCS TFCS OPTIONAL, ul-DPCCH-SlotFormat UL-DPCCH-SlotFormat OPTIONAL, diversityMode DiversityMode OPTIONAL, not-Used-sSDT-CellIDLength NULL OPTIONAL, not-Used-s-FieldLength NULL OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-DPDCHIndicatorEDCH CRITICALITY reject EXTENSION UL-DPDCHIndicatorEDCH PRESENCE optional ... } },

DL-DPCH-Information-RL-ReconfPrepFDD ::= SEQUENCE { tFCS TFCS OPTIONAL, dl-DPCH-SlotFormat DL-DPCH-SlotFormat OPTIONAL, nrOfDLchannelisationcodes NrOfDLchannelisationcodes OPTIONAL, tFCI-SignallingMode TFCI-SignallingMode OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL -- This IE shall be present if DL DPCH Slot Format IE is from 12 to 16 --, multiplexingPosition MultiplexingPosition OPTIONAL, limitedPowerIncrease LimitedPowerIncrease OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-Information-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-DPCH-Power-Information-RL-ReconfPrepFDD CRITICALITY reject optional }, ... } EXTENSION DL-DPCH-Power-Information-RL-ReconfPrepFDD PRESENCE

DL-DPCH-Power-Information-RL-ReconfPrepFDD ::= SEQUENCE { powerOffsetInformation PowerOffsetInformation-RL-ReconfPrepFDD, fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, innerLoopDLPCStatus InnerLoopDLPCStatus, iE-Extensions ProtocolExtensionContainer { { DL-DPCH-Power-Information-RL-ReconfPrepFDD-ExtIEs } }

OPTIONAL,

3GPP

Release 11
} ...

805

3GPP TS 25.423 V11.2.0 (2012-06)

DL-DPCH-Power-Information-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PowerOffsetInformation-RL-ReconfPrepFDD ::= SEQUENCE { pO1-ForTFCI-Bits PowerOffset, pO2-ForTPC-Bits PowerOffset, pO3-ForPilotBits PowerOffset, iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation-RL-ReconfPrepFDD-ExtIEs} } ... } PowerOffsetInformation-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-DeleteList-RL-ReconfPrepFDD ::= SEQUENCE (SIZE (0..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfPrepFDD

OPTIONAL,

DCH-DeleteItem-RL-ReconfPrepFDD ::= SEQUENCE { dCH-ID DCH-ID, iE-Extensions ProtocolExtensionContainer { {DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, ... } DCH-DeleteItem-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-RL-ReconfPrepFDD IEs} } ::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-RL-ReconfPrepFDD-

RL-Information-RL-ReconfPrepFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-ReconfPrepFDD CRITICALITY reject }

TYPE RL-Information-RL-ReconfPrepFDD

PRESENCE mandatory

RL-Information-RL-ReconfPrepFDD ::= SEQUENCE { rL-ID RL-ID, not-Used-sSDT-Indication NULL OPTIONAL, not-Used-sSDT-CellIdentity NULL OPTIONAL, transmitDiversityIndicator TransmitDiversityIndicator OPTIONAL, -- This IE shall be present if Diversity Mode IE is present in UL DPCH Information IE and is not equal to none iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-ReconfPrepFDD-ExtIEs} } OPTIONAL, ... } RL-Information-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DLReferencePower CRITICALITY ignore EXTENSION DL-Power { ID id-RL-Specific-DCH-Info CRITICALITY ignore EXTENSION RL-Specific-DCH-Info PRESENCE optional }| PRESENCE optional }|

3GPP

Release 11
{ ID { ID { ID { ID { ID { ID { ID { ID ... id-DL-DPCH-TimingAdjustment id-Phase-Reference-Update-Indicator id-RL-Specific-EDCH-Information id-EDCH-RL-Indication id-HSDSCH-PreconfigurationSetup id-Non-Serving-RL-Preconfig-Setup id-Non-Serving-RL-Preconfig-Removal id-FTPICH-Information-Reconf CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY reject ignore reject reject ignore ignore ignore ignore

806
EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION DL-DPCH-TimingAdjustment Phase-Reference-Update-Indicator RL-Specific-EDCH-Information EDCH-RL-Indication HSDSCH-PreconfigurationSetup Non-Serving-RL-Preconfig-Setup Non-Serving-RL-Preconfig-Setup FTPICH-Information-Reconf

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional optional optional }| }| }| }| }| }| }| },

RadioLinkReconfigurationPrepareFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-FDD-Information CRITICALITY reject { ID id-HSDSCH-Information-to-Modify CRITICALITY reject { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject { ID id-HSPDSCH-RL-ID CRITICALITY reject { ID id-EDPCH-Information CRITICALITY reject { ID id-EDCH-FDD-Information CRITICALITY reject { ID id-EDCH-FDD-Information-To-Modify CRITICALITY reject { ID id-EDCH-MACdFlows-To-Add CRITICALITY reject { ID id-EDCH-MACdFlows-To-Delete CRITICALITY reject { ID id-Serving-EDCHRL-Id CRITICALITY reject { ID id-F-DPCH-Information-RL-ReconfPrepFDD CRITICALITY reject { ID id-Fast-Reconfiguration-Mode CRITICALITY ignore { ID id-CPC-Information CRITICALITY reject { ID id-Additional-HS-Cell-Information-RL-Reconf-Prep CRITICALITY reject optional}| { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore { ID id-Additional-EDCH-Cell-Information-RL-Reconf-Prep CRITICALITY reject optional}| { ID id-UL-CLTD-Information-Reconf CRITICALITY reject ... } Additional-HS-Cell-Information-RL-Reconf-Prep

EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION

HSDSCH-FDD-Information PRESENCE HSDSCH-Information-to-Modify PRESENCE HSDSCH-MACdFlows-Information PRESENCE HSDSCH-MACdFlows-to-Delete PRESENCE RL-ID PRESENCE EDPCH-Information-RLReconfPrepare-FDD PRESENCE EDCH-FDD-Information PRESENCE EDCH-FDD-Information-To-Modify PRESENCE EDCH-MACdFlows-Information PRESENCE EDCH-MACdFlows-To-Delete PRESENCE EDCH-Serving-RL PRESENCE F-DPCH-Information-RL-ReconfPrepFDD PRESENCE Fast-Reconfiguration-Mode PRESENCE CPC-Information PRESENCE Additional-HS-Cell-Information-RL-Reconf-Prep

optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| PRESENCE

EXTENSION UE-AggregateMaximumBitRate PRESENCE optional}| EXTENSION Additional-EDCH-Cell-Information-RL-Reconf-Prep PRESENCE EXTENSION UL-CLTD-Information-Reconf PRESENCE optional},

::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs

Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, c-ID C-ID OPTIONAL, hS-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information OPTIONAL, hS-DSCH-Secondary-Serving-Information-To-Modify HS-DSCH-Secondary-Serving-Information-To-Modify OPTIONAL, hS-HS-DSCH-Secondary-Serving-Remove HS-DSCH-Secondary-Serving-Remove OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Information-RL-Reconf-Prep-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11

807

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-Cell-Information-RL-Reconf-Prep ::=SEQUENCE{ setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency Setup-Or-ConfigurationChange-Or-Removal-OfEDCH-On-secondary-UL-Frequency, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Reconf-Prep-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-RL-Reconf-Prep-ExtIEs ... } F-DPCH-Information-RL-ReconfPrepFDD powerOffsetInformation fdd-dl-TPC-DownlinkStepSize limitedPowerIncrease innerLoopDLPCStatus iE-Extensions ... } RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE { PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD, FDD-TPC-DownlinkStepSize, LimitedPowerIncrease, InnerLoopDLPCStatus, ProtocolExtensionContainer { { F-DPCH-Information-RL-ReconfPrepFDD-ExtIEs} }

OPTIONAL,

F-DPCH-Information-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-F-DPCH-SlotFormatSupportRequest CRITICALITY reject EXTENSION F-DPCH-SlotFormatSupportRequest }| { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION F-DPCH-SlotFormat PRESENCE optional}, ... } PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD ::= SEQUENCE { po2-ForTPC-Bits PowerOffset, --This IE shall be ignored by DRNS iE-Extensions ProtocolExtensionContainer { { PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD-ExtIEs} } ... } PowerOffsetInformation-F-DPCH-RL-ReconfPrepFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION PREPARE TDD --- ************************************************************** RadioLinkReconfigurationPrepareTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationPrepareTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationPrepareTDD-Extensions}} ... }

PRESENCE optional

OPTIONAL,

OPTIONAL,

3GPP

Release 11

808

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkReconfigurationPrepareTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-AllowedQueuingTime CRITICALITY reject TYPE AllowedQueuingTime PRESENCE optional } | { ID id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD CRITICALITY notify TYPE UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD CRITICALITY notify TYPE UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD CRITICALITY notify TYPE UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD CRITICALITY notify TYPE DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD CRITICALITY notify TYPE DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD CRITICALITY notify TYPE DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-TDD-DCHs-to-Modify CRITICALITY reject TYPE TDD-DCHs-to-Modify PRESENCE optional } | { ID id-DCHs-to-Add-TDD CRITICALITY reject TYPE DCH-TDD-Information PRESENCE optional } | { ID id-DCH-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE DCH-DeleteList-RL-ReconfPrepTDD PRESENCE optional }| { ID id-DSCH-ModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE DSCH-ModifyList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-DSCHs-to-Add-TDD CRITICALITY reject TYPE DSCH-TDD-Information PRESENCE optional } | { ID id-DSCH-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE DSCH-DeleteList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-USCH-ModifyList-RL-ReconfPrepTDD CRITICALITY reject TYPE USCH-ModifyList-RL-ReconfPrepTDD PRESENCE optional } | { ID id-USCHs-to-Add CRITICALITY reject TYPE USCH-Information PRESENCE optional } | { ID id-USCH-DeleteList-RL-ReconfPrepTDD CRITICALITY reject TYPE USCH-DeleteList-RL-ReconfPrepTDD PRESENCE optional }, ... } UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD RL-ReconfPrepTDD-IEs} } ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-AddInformation-

UL-CCTrCH-AddInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-AddInformation-RL-ReconfPrepTDD CRITICALITY notify }

TYPE UL-CCTrCH-AddInformation-RL-ReconfPrepTDD

PRESENCE mandatory

UL-CCTrCH-AddInformation-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS, tFCI-Coding TFCI-Coding, punctureLimit PunctureLimit, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-AddInformation-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-AddInformation-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR PRESENCE optional}| -- This IE shall be mandatory for 1.28Mcps TDD, not applicable for 3.84Mcps TDD or 7.68Mcps TDD. { ID id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD CRITICALITY reject EXTENSION TDD-TPC-UplinkStepSize-LCR optional }, -- Mandatory for 1.28Mcps TDD, not applicable to 3.84Mcps TDD or 7.68Mcps TDD ... }

PRESENCE

3GPP

Release 11
UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ModifyInformation-RL-ReconfPrepTDD-IEs} }

809

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-

UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD CRITICALITY notify mandatory } }

TYPE UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD

PRESENCE

UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS OPTIONAL, tFCI-Coding TFCI-Coding OPTIONAL, punctureLimit PunctureLimit OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR PRESENCE optional}| -- This IE shall be applicable for 1.28Mcps TDD only. { ID id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD CRITICALITY reject EXTENSION PRESENCE optional }, -- Applicable to 1.28Mcps TDD only ... } UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD DeleteInformation-RL-ReconfPrepTDD-IEs} }

TDD-TPC-UplinkStepSize-LCR

::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-

UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD CRITICALITY notify mandatory } }

TYPE UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD

PRESENCE

UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD RL-ReconfPrepTDD-IEs} } ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-AddInformation-

DL-CCTrCH-AddInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD CRITICALITY notify mandatory } }

TYPE DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD

PRESENCE

3GPP

Release 11

810

3GPP TS 25.423 V11.2.0 (2012-06)

DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS, tFCI-Coding TFCI-Coding, punctureLimit PunctureLimit, cCTrCH-TPCList CCTrCH-TPCAddList-RL-ReconfPrepTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD CRITICALITY reject optional }, ... } EXTENSION TDD-TPC-DownlinkStepSize PRESENCE

CCTrCH-TPCAddList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCAddItem-RL-ReconfPrepTDD CCTrCH-TPCAddItem-RL-ReconfPrepTDD cCTrCH-ID iE-Extensions ... } ::= SEQUENCE { CCTrCH-ID, ProtocolExtensionContainer { { CCTrCH-TPCAddItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL,

CCTrCH-TPCAddItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD ModifyInformation-RL-ReconfPrepTDD-IEs} } ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-

DL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD CRITICALITY notify mandatory } }

TYPE DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD

PRESENCE

DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS OPTIONAL, tFCI-Coding TFCI-Coding OPTIONAL, punctureLimit PunctureLimit OPTIONAL, cCTrCH-TPCList CCTrCH-TPCModifyList-RL-ReconfPrepTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD CRITICALITY reject optional}, ... EXTENSION TDD-TPC-DownlinkStepSize PRESENCE

3GPP

Release 11
}

811

3GPP TS 25.423 V11.2.0 (2012-06)

CCTrCH-TPCModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF CCTrCH-TPCModifyItem-RL-ReconfPrepTDD CCTrCH-TPCModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { { CCTrCH-TPCModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } CCTrCH-TPCModifyItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD DeleteInformation-RL-ReconfPrepTDD-IEs} } ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-

DL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD CRITICALITY notify mandatory } }

TYPE DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD

PRESENCE

DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (0..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfPrepTDD

DCH-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { dCH-ID DCH-ID, iE-Extensions ProtocolExtensionContainer { {DCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DSCH-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHs)) OF DSCH-ModifyItem-RL-ReconfPrepTDD DSCH-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { dSCH-ID DSCH-ID, dl-ccTrCHID CCTrCH-ID OPTIONAL, trChSourceStatisticsDescriptor TrCH-SrcStatisticsDescr OPTIONAL, transportFormatSet TransportFormatSet OPTIONAL,

3GPP

Release 11

812

3GPP TS 25.423 V11.2.0 (2012-06)

allocationRetentionPriority AllocationRetentionPriority OPTIONAL, schedulingPriorityIndicator SchedulingPriorityIndicator OPTIONAL, bLER BLER OPTIONAL, transportBearerRequestIndicator TransportBearerRequestIndicator, iE-Extensions ProtocolExtensionContainer { {DSCH-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DSCH-ModifyItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TrafficClass CRITICALITY ignore EXTENSION TrafficClass { ID id-BindingID CRITICALITY ignore EXTENSION BindingID -- Shall be ignored if bearer establishment with ALCAP. { ID id-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress -- Shall be ignored if bearer establishment with ALCAP. { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos -- Shall be ignored if bearer establishment with ALCAP. ... } DSCH-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE(0..maxNoOfDSCHs)) OF DSCH-DeleteItem-RL-ReconfPrepTDD DSCH-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { dSCH-ID DSCH-ID, iE-Extensions ProtocolExtensionContainer { {DSCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } DSCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-ModifyList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHs)) OF USCH-ModifyItem-RL-ReconfPrepTDD USCH-ModifyItem-RL-ReconfPrepTDD ::= SEQUENCE { uSCH-ID USCH-ID, ul-ccTrCHID CCTrCH-ID OPTIONAL, trChSourceStatisticsDescriptor TrCH-SrcStatisticsDescr OPTIONAL, transportFormatSet TransportFormatSet OPTIONAL, allocationRetentionPriority AllocationRetentionPriority OPTIONAL, schedulingPriorityIndicator SchedulingPriorityIndicator OPTIONAL, bLER BLER OPTIONAL, transportBearerRequestIndicator TransportBearerRequestIndicator, rb-Info RB-Info OPTIONAL, iE-Extensions ProtocolExtensionContainer { {USCH-ModifyItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } USCH-ModifyItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TrafficClass CRITICALITY ignore EXTENSION TrafficClass { ID id-BindingID CRITICALITY ignore EXTENSION BindingID -- Shall be ignored if bearer establishment with ALCAP. PRESENCE optional optional }| PRESENCE optional PRESENCE optional }| PRESENCE optional }| }, }|

PRESENCE optional

PRESENCE

}|

3GPP

Release 11
{ ID id-TransportLayerAddress CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. { ID id-TnlQos CRITICALITY ignore ... }

813
EXTENSION EXTENSION TransportLayerAddress TnlQos PRESENCE PRESENCE optional

3GPP TS 25.423 V11.2.0 (2012-06)

optional }, }|

USCH-DeleteList-RL-ReconfPrepTDD ::= SEQUENCE (SIZE(0..maxNoOfUSCHs)) OF USCH-DeleteItem-RL-ReconfPrepTDD USCH-DeleteItem-RL-ReconfPrepTDD ::= SEQUENCE { uSCH-ID USCH-ID, iE-Extensions ProtocolExtensionContainer { {USCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs} } OPTIONAL, ... } USCH-DeleteItem-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkReconfigurationPrepareTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-PrimaryCCPCH-RSCP-RL-ReconfPrepTDD CRITICALITY ignore EXTENSION PrimaryCCPCH-RSCP PRESENCE optional}| { ID id-DL-TimeSlot-ISCP-Info-RL-ReconfPrepTDD CRITICALITY ignore EXTENSION DL-TimeSlot-ISCP-Info PRESENCE optional}| { ID id-DL-Timeslot-ISCP-LCR-Information-RL-ReconfPrepTDD CRITICALITY ignore EXTENSION DL-TimeSlot-ISCP-LCR-Information PRESENCE optional}| { ID id-HSDSCH-TDD-Information CRITICALITY reject EXTENSION HSDSCH-TDD-Information PRESENCE optional}| { ID id-HSDSCH-Information-to-Modify CRITICALITY reject EXTENSION HSDSCH-Information-to-Modify PRESENCE optional}| { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject EXTENSION HSDSCH-MACdFlows-Information PRESENCE optional}| { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION HSDSCH-MACdFlows-to-Delete PRESENCE optional}| { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE optional}| { ID id-PDSCH-RL-ID CRITICALITY ignore EXTENSION RL-ID PRESENCE optional}| { ID id-UL-Synchronisation-Parameters-LCR CRITICALITY ignore EXTENSION UL-Synchronisation-Parameters-LCR PRESENCE optional}| -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD { ID id-RL-Information-RL-ReconfPrepTDD CRITICALITY ignore EXTENSION RL-Information-RL-ReconfPrepTDD PRESENCE optional}| { ID id-PrimaryCCPCH-RSCP-Delta CRITICALITY ignore EXTENSION PrimaryCCPCH-RSCP-Delta PRESENCE optional}| { ID id-E-DCH-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-Information-Reconfig PRESENCE optional}| { ID id-E-DCH-Serving-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE optional}| { ID id-E-DCH-768-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-768-Information-Reconfig PRESENCE optional}| { ID id-E-DCH-LCR-Information-Reconfig CRITICALITY reject EXTENSION E-DCH-LCR-Information-Reconfig PRESENCE optional}| { ID id-NeedforIdleInterval CRITICALITY ignore EXTENSION NeedforIdleInterval PRESENCE optional}| { ID id-CPC-InformationLCR CRITICALITY reject EXTENSION CPC-InformationLCR PRESENCE optional}| { ID id-RNTI-Allocation-Indicator CRITICALITY ignore EXTENSION RNTI-Allocation-Indicator PRESENCE optional}| { ID id-DCH-MeasurementType-Indicator CRITICALITY reject EXTENSION DCH-MeasurementType-Indicator PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Reconfigure CRITICALITY reject EXTENSION Multi-Carrier-EDCH-Reconfigure PRESENCE optional}| { ID id-MU-MIMO-Indicator CRITICALITY reject EXTENSION MU-MIMO-Indicator PRESENCE optional}, ... } RL-Information-RL-ReconfPrepTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF RL-InformationIE-RL-ReconfPrepTDD RL-InformationIE-RL-ReconfPrepTDD ::= SEQUENCE { rL-ID RL-ID, rL-Specific-DCH-Info RL-Specific-DCH-Info

OPTIONAL,

3GPP

Release 11
iE-Extensions ... } RL-InformationIE-RL-ReconfPrepTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION READY FDD --- **************************************************************

814
ProtocolExtensionContainer { { RL-InformationIE-RL-ReconfPrepTDD-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RadioLinkReconfigurationReadyFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationReadyFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationReadyFDD-Extensions}} ... } RadioLinkReconfigurationReadyFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseList-RL-ReconfReadyFDD CRITICALITY ignore TYPE RL-InformationResponseList-RL-ReconfReadyFDD optional } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } RL-InformationResponseList-RL-ReconfReadyFDD ReconfReadyFDD-IEs} }

OPTIONAL,

PRESENCE

::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationResponse-RL-

RL-InformationResponse-RL-ReconfReadyFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseItem-RL-ReconfReadyFDD CRITICALITY ignore mandatory } }

TYPE RL-InformationResponseItem-RL-ReconfReadyFDD

PRESENCE

RL-InformationResponseItem-RL-ReconfReadyFDD ::= SEQUENCE { rL-ID RL-ID, max-UL-SIR UL-SIR min-UL-SIR UL-SIR maximumDLTxPower DL-Power minimumDLTxPower DL-Power not-Used-secondary-CCPCH-Info NULL dl-CodeInformationList DL-CodeInformationList-RL-ReconfReadyFDD dCHInformationResponse DCH-InformationResponseList-RL-ReconfReadyFDD not-Used-dSCHsToBeAddedOrModified NULL iE-Extensions ProtocolExtensionContainer { {RL-InformationResponseItem-RL-ReconfReadyFDD-ExtIEs} } ... } RL-InformationResponseItem-RL-ReconfReadyFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11
{ ID id-DL-PowerBalancing-UpdatedIndicator PRESENCE optional }| { ID id-Primary-CPICH-Usage-For-Channel-Estimation optional }| { ID id-Secondary-CPICH-Information-Change PRESENCE optional }| { ID id-EDCH-FDD-InformationResponse PRESENCE optional }| { ID id-EDCH-RLSet-Id PRESENCE optional }| { ID id-EDCH-FDD-DL-ControlChannelInformation optional }| { ID id-F-DPCH-SlotFormat PRESENCE optional }| { ID id-HSDSCH-PreconfigurationInfo PRESENCE optional }| { ID id-Non-Serving-RL-Preconfig-Info PRESENCE optional }, ... } CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore

815
EXTENSION DL-PowerBalancing-UpdatedIndicator

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

EXTENSION Primary-CPICH-Usage-For-Channel-Estimation EXTENSION Secondary-CPICH-Information-Change EXTENSION EDCH-FDD-InformationResponse EXTENSION RL-Set-ID EXTENSION EDCH-FDD-DL-ControlChannelInformation EXTENSION F-DPCH-SlotFormat EXTENSION HSDSCH-PreconfigurationInfo EXTENSION Non-Serving-RL-Preconfig-Info

PRESENCE

DL-CodeInformationList-RL-ReconfReadyFDD ::= ProtocolIE-Single-Container {{ DL-CodeInformationListIEs-RL-ReconfReadyFDD }} DL-CodeInformationListIEs-RL-ReconfReadyFDD RNSAP-PROTOCOL-IES ::= { { ID id-FDD-DL-CodeInformation CRITICALITY ignore TYPE FDD-DL-CodeInformation } DCH-InformationResponseList-RL-ReconfReadyFDD PRESENCE mandatory }

::= ProtocolIE-Single-Container { {DCH-InformationResponseListIEs-RL-ReconfReadyFDD} } PRESENCE mandatory }

DCH-InformationResponseListIEs-RL-ReconfReadyFDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse }

RadioLinkReconfigurationReadyFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional }| { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD-Information-Response PRESENCE optional }| { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs-ResetIndicator PRESENCE optional }| { ID id-Fast-Reconfiguration-Permission CRITICALITY ignore EXTENSION Fast-Reconfiguration-Permission PRESENCE optional }| { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response CRITICALITY ignore EXTENSION Continuous-PacketConnectivity-HS-SCCH-Less-Information-Response PRESENCE optional }| { ID id-Additional-HS-Cell-RL-Reconf-Response CRITICALITY ignore EXTENSION Additional-HS-Cell-RL-Reconf-Response PRESENCE optional }| { ID id-Additional-EDCH-Cell-Information-ResponseRLReconf CRITICALITY ignore EXTENSION Additional-EDCH-Cell-Information-Response-RLReconfList PRESENCE optional }, ... } Additional-HS-Cell-RL-Reconf-Response ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-RL-Reconf-Response-ItemIEs

3GPP

Release 11

816

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-HS-Cell-RL-Reconf-Response-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, hSDSCH-RNTI HSDSCH-RNTI, hS-DSCH-FDD-Secondary-Serving-Information-Response HS-DSCH-FDD-Secondary-Serving-Information-Response, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-RL-Reconf-Response-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-RL-Reconf-Response-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

-- ************************************************************** --- RADIO LINK RECONFIGURATION READY TDD --- ************************************************************** RadioLinkReconfigurationReadyTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationReadyTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationReadyTDD-Extensions}} ... } RadioLinkReconfigurationReadyTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponse-RL-ReconfReadyTDD CRITICALITY ignore TYPE RL-InformationResponse-RL-ReconfReadyTDD PRESENCE optional --This RL-InformationResponse-RL-ReconfReadyTDD is for the first RL repetition in the list. --Repetitions 2 and on are defined in Multiple-RL-InformationResponse-RL-ReconfReadyTDD. { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional ... } RL-InformationResponse-RL-ReconfReadyTDD ::= SEQUENCE { rL-ID RL-ID, max-UL-SIR UL-SIR OPTIONAL, min-UL-SIR UL-SIR OPTIONAL, maximumDLTxPower DL-Power OPTIONAL, minimumDLTxPower DL-Power OPTIONAL, secondary-CCPCH-Info-TDD Secondary-CCPCH-Info-TDD OPTIONAL, ul-CCTrCH-Information UL-CCTrCH-InformationList-RL-ReconfReadyTDD OPTIONAL, dl-CCTrCH-Information DL-CCTrCH-InformationList-RL-ReconfReadyTDD OPTIONAL, dCHInformationResponse DCH-InformationResponseList-RL-ReconfReadyTDD OPTIONAL, dSCHsToBeAddedOrModified DSCHToBeAddedOrModified-RL-ReconfReadyTDD OPTIONAL, uSCHsToBeAddedOrModified USCHToBeAddedOrModified-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponse-RL-ReconfReadyTDD-ExtIEs} } ... } RL-InformationResponse-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

} | },

OPTIONAL,

3GPP

Release 11
{ ID id-UL-TimingAdvanceCtrl-LCR optional }| --For 1.28Mcps TDD only { ID id-secondary-LCR-CCPCH-Info-TDD optional }| --For 1.28Mcps TDD only { ID id-secondary-CCPCH-Info-RL-ReconfReadyTDD768 optional }| { ID id-UARFCNforNt optional }, -- Applicable to 1.28Mcps TDD only ... } UL-CCTrCH-InformationList-RL-ReconfReadyTDD

817
CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore EXTENSION UL-TimingAdvanceCtrl-LCR EXTENSION Secondary-LCR-CCPCH-Info-TDD EXTENSION Secondary-CCPCH-Info-TDD768 EXTENSION UARFCN

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE PRESENCE PRESENCE PRESENCE

::= ProtocolIE-Single-Container {{UL-CCTrCHInformationListIEs-RL-ReconfReadyTDD}} TYPE UL-CCTrCHInformationListIE-RL-ReconfReadyTDD PRESENCE

UL-CCTrCHInformationListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-RL-ReconfReadyTDD CRITICALITY ignore mandatory } }

UL-CCTrCHInformationListIE-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationItem-RL-ReconfReadyTDD UL-CCTrCH-InformationItem-RL-ReconfReadyTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-AddInformation UL-DPCH-InformationAddList-RL-ReconfReadyTDD OPTIONAL, --For 3.84Mcps TDD only ul-DPCH-ModifyInformation UL-DPCH-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, ul-DPCH-DeleteInformation UL-DPCH-InformationDeleteList-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-InformationItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-InformationItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE optional }| --For 1.28Mcps TDD only { ID id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768 CRITICALITY ignore PRESENCE optional }, --For 7.68Mcps TDD only ... } EXTENSION UL-DPCH-LCR-InformationAddList-RL-ReconfReadyTDD EXTENSION UL-DPCH-InformationAddList-RL-ReconfReadyTDD768

UL-DPCH-LCR-InformationAddList-RL-ReconfReadyTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, uL-TimeslotLCR-Info UL-TimeslotLCR-Information, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-LCR-InformationAddItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

818

3GPP TS 25.423 V11.2.0 (2012-06)

UL-DPCH-LCR-InformationAddItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-InformationAddList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{UL-DPCH-InformationAddListIEs-RL-ReconfReadyTDD}} UL-DPCH-InformationAddListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD CRITICALITY ignore TYPE UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD optional } } UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, rxTimingDeviationForTA RxTimingDeviationForTA OPTIONAL, uL-Timeslot-Information UL-Timeslot-Information, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationAddItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationAddItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RxTimingDeviationForTAext CRITICALITY ignore EXTENSION RxTimingDeviationForTAext ... } PRESENCE optional }, PRESENCE

UL-DPCH-InformationAddList-RL-ReconfReadyTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, rxTimingDeviationForTA768 RxTimingDeviationForTA768 OPTIONAL, uL-Timeslot-Information768 UL-Timeslot-Information768, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationAddItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationAddItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-InformationModifyList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{UL-DPCH-InformationModifyListIEs-RL-ReconfReadyTDD}} UL-DPCH-InformationModifyListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE mandatory } } UL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD::= SEQUENCE { repetitionPeriod RepetitionPeriod OPTIONAL, repetitionLength RepetitionLength OPTIONAL, TYPE UL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD

3GPP

Release 11

819

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

tDD-DPCHOffset TDD-DPCHOffset OPTIONAL, uL-Timeslot-InformationModifyList-RL-ReconfReadyTDD UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD --For 3.84Mcps TDD only iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ...

UL-DPCH-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD CRITICALITY ignore EXTENSION UL-TimeslotLCR-InformationModifyList-RLReconfReadyTDD PRESENCE optional }| --For 1.28Mcps TDD only { ID id-UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768 CRITICALITY ignore EXTENSION UL-Timeslot-InformationModifyList-RLReconfReadyTDD768 PRESENCE optional }, --For 7.68Mcps TDD only ... } UL-TimeslotLCR-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfTsLCR)) OF UL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD UL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, tDD-uL-Code-LCR-Information TDD-UL-Code-LCR-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-LCR-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfDPCHsLCR)) OF TDD-UL-Code-LCR-InformationModifyItem-RLReconfReadyTDD TDD-UL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-UL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-UL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD CRITICALITY reject optional}, ... } UL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { EXTENSION TDD-UL-DPCH-TimeSlotFormat-LCR PRESENCE

3GPP

Release 11
timeSlot midambleShiftAndBurstType tFCI-Presence uL-Code-Information iE-Extensions ... } TimeSlot,

820

3GPP TS 25.423 V11.2.0 (2012-06)

MidambleShiftAndBurstType OPTIONAL, TFCI-Presence OPTIONAL, TDD-UL-Code-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, ProtocolExtensionContainer { {UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL,

UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-UL-Code-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfDPCHs)) OF TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode TDD-ChannelisationCode OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768 UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768 OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, uL-Code-Information768 TDD-UL-Code-InformationModifyList-RL-ReconfReadyTDD768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL, ... } UL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-UL-Code-InformationModifyList-RL-ReconfReadyTDD768::= SEQUENCE ( SIZE (1..maxNrOfDPCHs768)) OF TDD-UL-Code-InformationModifyItem-RLReconfReadyTDD768 TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD768 ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode768 TDD-ChannelisationCode768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

821

3GPP TS 25.423 V11.2.0 (2012-06)

UL-DPCH-InformationDeleteList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{UL-DPCH-InformationDeleteListIEs-RL-ReconfReadyTDD}} UL-DPCH-InformationDeleteListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE mandatory } } TYPE UL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD

UL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNrOfDPCHs)) OF UL-DPCH-InformationDeleteItem-RL-ReconfReadyTDD UL-DPCH-InformationDeleteItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationDeleteList-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationDeleteList-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{DL-CCTrCHInformationListIEs-RL-ReconfReadyTDD}} TYPE DL-CCTrCHInformationListIE-RL-ReconfReadyTDD PRESENCE

DL-CCTrCHInformationListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-RL-ReconfReadyTDD CRITICALITY ignore mandatory } }

DL-CCTrCHInformationListIE-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationItem-RL-ReconfReadyTDD DL-CCTrCH-InformationItem-RL-ReconfReadyTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-AddInformation DL-DPCH-InformationAddList-RL-ReconfReadyTDD OPTIONAL, --For 3.84Mcps TDD only dl-DPCH-ModifyInformation DL-DPCH-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, dl-DPCH-DeleteInformation DL-DPCH-InformationDeleteList-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD CRITICALITY ignore ReconfReadyTDD PRESENCE optional}| --For 1.28Mcps TDD only { ID id-CCTrCH-Maximum-DL-Power-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE optional }| -- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only, this is a DCH type CCTrCH power { ID id-CCTrCH-Minimum-DL-Power-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE optional }| EXTENSION DL-DPCH-LCR-InformationAddList-RL-

EXTENSION DL-Power EXTENSION DL-Power

3GPP

Release 11

822

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION DL-DPCH-InformationAddList-RL-ReconfReadyTDD768 EXTENSION DL-DPCH-InformationDeleteList768-RL-

-- Applicable to 3.84Mcps TDD and 7.68Mcps TDD only, this is a DCH type CCTrCH power { ID id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768 CRITICALITY ignore PRESENCE optional}| --For 7.68Mcps TDD only { ID id-DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD CRITICALITY ignore ReconfReadyTDD PRESENCE optional}, ... }

DL-DPCH-LCR-InformationAddList-RL-ReconfReadyTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-TimeslotLCR-Info DL-TimeslotLCR-Information, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-LCR-InformationAddItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-LCR-InformationAddItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationAddList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{DL-DPCH-InformationAddListIEs-RL-ReconfReadyTDD}} DL-DPCH-InformationAddListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD CRITICALITY ignore TYPE DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD mandatory } } DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-Information DL-Timeslot-Information, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationAddItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-InformationAddItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationAddList-RL-ReconfReadyTDD768 ::= SEQUENCE { repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength, tDD-DPCHOffset TDD-DPCHOffset, dL-Timeslot-Information768 DL-Timeslot-Information768, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationAddItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL, ... } PRESENCE

3GPP

Release 11

823

3GPP TS 25.423 V11.2.0 (2012-06)

DL-DPCH-InformationAddItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationModifyList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{DL-DPCH-InformationModifyListIEs-RL-ReconfReadyTDD}} DL-DPCH-InformationModifyListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE mandatory } } TYPE DL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD

DL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod OPTIONAL, repetitionLength RepetitionLength OPTIONAL, tDD-DPCHOffset TDD-DPCHOffset OPTIONAL, dL-Timeslot-InformationModifyList-RL-ReconfReadyTDD DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD --For 3.84Mcps TDD only iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... }

OPTIONAL,

DL-DPCH-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD CRITICALITY ignore EXTENSION DL-TimeslotLCR-InformationModifyList-RLReconfReadyTDD PRESENCE optional }| --For 1.28Mcps TDD only { ID id-DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768 CRITICALITY ignore EXTENSION DL-Timeslot-InformationModifyList-RLReconfReadyTDD768 PRESENCE optional }, --For 7.68Mcps TDD only ... } DL-TimeslotLCR-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfTsLCR)) OF DL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD DL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, tDD-dL-Code-LCR-Information TDD-DL-Code-LCR-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } TDD-DL-Code-LCR-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfDPCHsLCR)) OF TDD-DL-Code-LCR-InformationModifyItem-RLReconfReadyTDD TDD-DL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-DL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

824

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR

TDD-DL-Code-LCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-DL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD CRITICALITY reject PRESENCE optional}, ... } DL-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Maximum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD CRITICALITY ignore optional }| { ID id-Minimum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD CRITICALITY ignore optional }, ... }

EXTENSION EXTENSION

DL-Power DL-Power

PRESENCE PRESENCE

DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, dL-Code-Information TDD-DL-Code-InformationModifyList-RL-ReconfReadyTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-DL-Code-InformationModifyList-RL-ReconfReadyTDD::= SEQUENCE ( SIZE (1..maxNrOfDPCHs)) OF TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode TDD-ChannelisationCode OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TDD-DL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD CRITICALITY reject optional}, -- This IE shall not be used ... } EXTENSION TDD-DL-DPCH-TimeSlotFormat-LCR PRESENCE

DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768 DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768

OPTIONAL,

3GPP

Release 11
tFCI-Presence dL-Code-Information768 iE-Extensions ... }

825

3GPP TS 25.423 V11.2.0 (2012-06)

TFCI-Presence OPTIONAL, TDD-DL-Code-InformationModifyList-RL-ReconfReadyTDD768 OPTIONAL, ProtocolExtensionContainer { {DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL,

DL-Timeslot-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-DL-Code-InformationModifyList-RL-ReconfReadyTDD768::= SEQUENCE ( SIZE (1..maxNrOfDPCHs768)) OF TDD-DL-Code-InformationModifyItem-RLReconfReadyTDD768 TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD768 ::= SEQUENCE { dPCH-ID768 DPCH-ID768, tDD-ChannelisationCode768 TDD-ChannelisationCode768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs} } OPTIONAL, ... } TDD-DL-Code-InformationModifyItem-RL-ReconfReadyTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationDeleteList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container {{DL-DPCH-InformationDeleteListIEs-RL-ReconfReadyTDD}} DL-DPCH-InformationDeleteListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD CRITICALITY ignore PRESENCE mandatory } } TYPE DL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD

DL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNrOfDPCHs)) OF DL-DPCH-InformationDeleteItem-RL-ReconfReadyTDD DL-DPCH-InformationDeleteItem-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID DPCH-ID, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationDeleteList-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-InformationDeleteList-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNrOfDPCHs768)) OF DL-DPCH-InformationDeleteItem768-RL-ReconfReadyTDD DL-DPCH-InformationDeleteItem768-RL-ReconfReadyTDD ::= SEQUENCE { dPCH-ID768 DPCH-ID768, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

826

3GPP TS 25.423 V11.2.0 (2012-06)

DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-InformationResponseList-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container { {DCH-InformationResponseListIEs-RL-ReconfReadyTDD} } PRESENCE mandatory }

DCH-InformationResponseListIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse } DSCHToBeAddedOrModified-RL-ReconfReadyTDD

::= ProtocolIE-Single-Container { {DSCHToBeAddedOrModifiedIEs-RL-ReconfReadyTDD} } TYPE DSCHToBeAddedOrModifiedList-RL-ReconfReadyTDD PRESENCE

DSCHToBeAddedOrModifiedIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-DSCHToBeAddedOrModifiedList-RL-ReconfReadyTDD CRITICALITY ignore mandatory } }

DSCHToBeAddedOrModifiedList-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNoOfDSCHs)) OF DSCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD DSCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD ::= SEQUENCE { dsch-ID DSCH-ID, transportFormatManagement TransportFormatManagement, dSCH-FlowControlInformation DSCH-FlowControlInformation, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DSCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } DSCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCHToBeAddedOrModified-RL-ReconfReadyTDD ::= ProtocolIE-Single-Container { {USCHToBeAddedOrModifiedIEs-RL-ReconfReadyTDD} } USCHToBeAddedOrModifiedIEs-RL-ReconfReadyTDD RNSAP-PROTOCOL-IES ::= { { ID id-USCHToBeAddedOrModifiedList-RL-ReconfReadyTDD CRITICALITY ignore TYPE USCHToBeAddedOrModifiedList-RL-ReconfReadyTDD mandatory } } USCHToBeAddedOrModifiedList-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (0..maxNoOfUSCHs)) OF USCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD USCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD ::= SEQUENCE { uSCH-ID USCH-ID, transportFormatManagement TransportFormatManagement, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { {USCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD-ExtIEs} } OPTIONAL, ... } USCHToBeAddedOrModifiedItem-RL-ReconfReadyTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

PRESENCE

3GPP

Release 11
} ...

827

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkReconfigurationReadyTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-DSCH-RNTI CRITICALITY ignore EXTENSION DSCH-RNTI PRESENCE optional}| { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD-Information-Response PRESENCE optional}| { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs-ResetIndicator PRESENCE optional}| { ID id-Multiple-RL-InformationResponse-RL-ReconfReadyTDD CRITICALITY ignore EXTENSION Multiple-RL-InformationResponse-RL-ReconfReadyTDD PRESENCE optional}| -- This is for RL repetitions 2 and on in RL list. { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH-Information-Response PRESENCE optional}| { ID id-E-DCH-768-Information-Response CRITICALITY ignore EXTENSION E-DCH-768-Information-Response PRESENCE optional}| { ID id-E-DCH-LCR-Information-Response CRITICALITY ignore EXTENSION E-DCH-LCR-Information-Response PRESENCE optional}| { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP PRESENCE optional}| -- Applicable to 1.28Mcps TDD only { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION IdleIntervalInformation PRESENCE optional}| { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore EXTENSION ContinuousPacketConnectivity-DRX-InformationResponseLCR PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION HS-DSCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION E-DCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-RNTI-For-FACH CRITICALITY ignore EXTENSION E-RNTI PRESENCE optional}| { ID id-H-RNTI-For-FACH CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH-MeasurementOccasion-Information PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier-EDCH-Information-Response PRESENCE optional}| { ID id-MU-MIMO-InformationLCR CRITICALITY reject EXTENSION MU-MIMO-InformationLCR PRESENCE optional}, ... } Multiple-RL-InformationResponse-RL-ReconfReadyTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF RL-InformationResponse-RL-ReconfReadyTDD -- ************************************************************** --- RADIO LINK RECONFIGURATION COMMIT --- ************************************************************** RadioLinkReconfigurationCommit ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationCommit-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationCommit-Extensions}} ... } RadioLinkReconfigurationCommit-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CFN CRITICALITY ignore TYPE CFN { ID id-Active-Pattern-Sequence-Information CRITICALITY ignore only ... PRESENCE mandatory }| TYPE Active-Pattern-Sequence-Information

OPTIONAL,

PRESENCE optional

},--FDD

3GPP

Release 11
}

828

3GPP TS 25.423 V11.2.0 (2012-06)

RadioLinkReconfigurationCommit-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Fast-Reconfiguration-Mode CRITICALITY reject EXTENSION Fast-Reconfiguration-Mode ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION FAILURE --- **************************************************************

PRESENCE optional },--FDD only

RadioLinkReconfigurationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationFailure-Extensions}} ... } RadioLinkReconfigurationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CauseLevel-RL-ReconfFailure CRITICALITY ignore { ID id-CriticalityDiagnostics CRITICALITY ignore ... } CauseLevel-RL-ReconfFailure ::= CHOICE { generalCause GeneralCauseList-RL-ReconfFailure, rLSpecificCause RLSpecificCauseList-RL-ReconfFailure, ... } GeneralCauseList-RL-ReconfFailure ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { GeneralCauseItem-RL-ReconfFailure-ExtIEs} } ... } GeneralCauseItem-RL-ReconfFailure-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= { TYPE CauseLevel-RL-ReconfFailure PRESENCE mandatory } | TYPE CriticalityDiagnostics PRESENCE optional },

OPTIONAL,

OPTIONAL,

RLSpecificCauseList-RL-ReconfFailure ::= SEQUENCE { rL-ReconfigurationFailureList-RL-ReconfFailure iE-Extensions OPTIONAL, ... } RLSpecificCauseItem-RL-ReconfFailure-ExtIEs ... }

RL-ReconfigurationFailureList-RL-ReconfFailure OPTIONAL, ProtocolExtensionContainer { { RLSpecificCauseItem-RL-ReconfFailure-ExtIEs} }

RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11

829

3GPP TS 25.423 V11.2.0 (2012-06)

RL-ReconfigurationFailureList-RL-ReconfFailure ::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-ReconfigurationFailure-RLReconfFailure-IEs} } RL-ReconfigurationFailure-RL-ReconfFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-ReconfigurationFailure-RL-ReconfFail CRITICALITY ignore TYPE RL-ReconfigurationFailure-RL-ReconfFail } PRESENCE mandatory }

RL-ReconfigurationFailure-RL-ReconfFail ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {RL-ReconfigurationFailure-RL-ReconfFailure-ExtIEs} } OPTIONAL, ... } RL-ReconfigurationFailure-RL-ReconfFailure-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle PRESENCE conditional }, -- This IE shall be present if the Cause IE is set to Continuous Packet Connectivity UE DTX Cycle not Available. ... } RadioLinkReconfigurationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION CANCEL --- ************************************************************** RadioLinkReconfigurationCancel ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationCancel-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationCancel-Extensions}} ... } RadioLinkReconfigurationCancel-IEs RNSAP-PROTOCOL-IES ::= { ... } RadioLinkReconfigurationCancel-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION REQUEST FDD --- **************************************************************

OPTIONAL,

3GPP

Release 11

830

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RadioLinkReconfigurationRequestFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationRequestFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationRequestFDD-Extensions}} ... } RadioLinkReconfigurationRequestFDD-IEs RNSAP-PROTOCOL-IES { ID id-AllowedQueuingTime | { ID id-UL-DPCH-Information-RL-ReconfRqstFDD | { ID id-DL-DPCH-Information-RL-ReconfRqstFDD | { ID id-FDD-DCHs-to-Modify | { ID id-DCHs-to-Add-FDD | { ID id-DCH-DeleteList-RL-ReconfRqstFDD | { ID id-Transmission-Gap-Pattern-Sequence-Information ... } ::= { CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject TYPE AllowedQueuingTime TYPE UL-DPCH-Information-RL-ReconfRqstFDD TYPE DL-DPCH-Information-RL-ReconfRqstFDD TYPE FDD-DCHs-to-Modify TYPE DCH-FDD-Information TYPE DCH-DeleteList-RL-ReconfRqstFDD TYPE Transmission-Gap-Pattern-Sequence-Information

PRESENCE optional PRESENCE optional PRESENCE optional PRESENCE optional PRESENCE optional PRESENCE optional

} } } } } }

PRESENCE optional },

UL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE { tFCS TFCS OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-DPDCHIndicatorEDCH CRITICALITY reject EXTENSION UL-DPDCHIndicatorEDCH ... } PRESENCE optional },

DL-DPCH-Information-RL-ReconfRqstFDD ::= SEQUENCE { tFCS TFCS OPTIONAL, tFCI-SignallingMode TFCI-SignallingMode OPTIONAL, limitedPowerIncrease LimitedPowerIncrease OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs} } OPTIONAL, ... } DL-DPCH-Information-RL-ReconfRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-DeleteList-RL-ReconfRqstFDD ::= SEQUENCE (SIZE (0..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfRqstFDD

DCH-DeleteItem-RL-ReconfRqstFDD ::= SEQUENCE { dCH-ID DCH-ID, iE-Extensions ProtocolExtensionContainer { {DCH-DeleteItem-RL-ReconfRqstFDD-ExtIEs} } OPTIONAL,

3GPP

Release 11
} ...

831

3GPP TS 25.423 V11.2.0 (2012-06)

DCH-DeleteItem-RL-ReconfRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkReconfigurationRequestFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RL-ReconfigurationRequestFDD-RL-InformationList CRITICALITY ignore EXTENSION RL-ReconfigurationRequestFDD-RL-InformationList PRESENCE optional}| { ID id-DL-ReferencePowerInformation CRITICALITY ignore EXTENSION DL-ReferencePowerInformation PRESENCE optional}| { ID id-HSDSCH-FDD-Information CRITICALITY reject EXTENSION HSDSCH-FDD-Information PRESENCE optional}| { ID id-HSDSCH-Information-to-Modify-Unsynchronised CRITICALITY reject EXTENSION HSDSCH-Information-to-Modify-Unsynchronised PRESENCE optional}| { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject EXTENSION HSDSCH-MACdFlows-Information PRESENCE optional}| { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject EXTENSION HSDSCH-MACdFlows-to-Delete PRESENCE optional}| { ID id-HSPDSCH-RL-ID CRITICALITY reject EXTENSION RL-ID PRESENCE optional}| { ID id-EDPCH-Information-RLReconfRequest-FDD CRITICALITY reject EXTENSION EDPCH-Information-RLReconfRequest-FDD PRESENCE optional}| { ID id-EDCH-FDD-Information CRITICALITY reject EXTENSION EDCH-FDD-Information PRESENCE optional}| { ID id-EDCH-FDD-Information-To-Modify CRITICALITY reject EXTENSION EDCH-FDD-Information-To-Modify PRESENCE optional}| { ID id-EDCH-MACdFlows-To-Add CRITICALITY reject EXTENSION EDCH-MACdFlows-Information PRESENCE optional}| { ID id-EDCH-MACdFlows-To-Delete CRITICALITY reject EXTENSION EDCH-MACdFlows-To-Delete PRESENCE optional}| { ID id-Serving-EDCHRL-Id CRITICALITY reject EXTENSION EDCH-Serving-RL PRESENCE optional}| { ID id-CPC-Information CRITICALITY reject EXTENSION CPC-Information PRESENCE optional}| { ID id-NoOfTargetCellHS-SCCH-Order CRITICALITY ignore EXTENSION NoOfTargetCellHS-SCCH-Order PRESENCE optional}| { ID id-Additional-HS-Cell-Information-RL-Reconf-Req CRITICALITY reject EXTENSION Additional-HS-Cell-Information-RL-Reconf-Req PRESENCE optional}| { ID id-UE-AggregateMaximumBitRate CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate PRESENCE optional}| { ID id-Additional-EDCH-Cell-Information-RL-Reconf-Req CRITICALITY reject EXTENSION Additional-EDCH-Cell-Information-RL-Reconf-Req PRESENCE optional}| { ID id-UL-CLTD-Information-Reconf CRITICALITY reject EXTENSION UL-CLTD-Information-Reconf PRESENCE optional}, ... } Additional-HS-Cell-Information-RL-Reconf-Req ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs

Additional-HS-Cell-Information-RL-Reconf-Req-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, c-ID C-ID OPTIONAL, hS-DSCH-FDD-Secondary-Serving-Information HS-DSCH-FDD-Secondary-Serving-Information OPTIONAL, hS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised OPTIONAL, hS-DSCH-Secondary-Serving-Remove HS-DSCH-Secondary-Serving-Remove OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Reconf-Req-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Information-RL-Reconf-Req-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Additional-EDCH-Cell-Information-RL-Reconf-Req ::=SEQUENCE{

3GPP

Release 11

832

3GPP TS 25.423 V11.2.0 (2012-06)

setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-ULFrequency, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-RL-Reconf-Req-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-RL-Reconf-Req-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

RL-ReconfigurationRequestFDD-RL-InformationList ::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-ReconfigurationRequestFDD-RL-Information-ListItem} } RL-ReconfigurationRequestFDD-RL-Information-ListItem RNSAP-PROTOCOL-IES ::= { { ID id-RL-ReconfigurationRequestFDD-RL-Information-IEs CRITICALITY ignore optional } } TYPE RL-ReconfigurationRequestFDD-RL-Information-IEs PRESENCE

RL-ReconfigurationRequestFDD-RL-Information-IEs ::= SEQUENCE { rL-ID RL-ID, rL-Specific-DCH-Info RL-Specific-DCH-Info OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-ReconfigurationRequestFDD-RL-Information-ExtIEs} } OPTIONAL, ... } RL-ReconfigurationRequestFDD-RL-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RL-Specific-EDCH-Information CRITICALITY reject EXTENSION RL-Specific-EDCH-Information { ID id-EDCH-RL-Indication CRITICALITY reject EXTENSION EDCH-RL-Indication { ID id-HSDSCH-PreconfigurationSetup CRITICALITY ignore EXTENSION HSDSCH-PreconfigurationSetup { ID id-Non-Serving-RL-Preconfig-Setup CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Setup { ID id-Non-Serving-RL-Preconfig-Removal CRITICALITY ignore EXTENSION Non-Serving-RL-Preconfig-Setup { ID id-FTPICH-Information-Reconf CRITICALITY ignore EXTENSION FTPICH-Information-Reconf ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION REQUEST TDD --- ************************************************************** RadioLinkReconfigurationRequestTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationRequestTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationRequestTDD-Extensions}} ... } PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional }| }| }| }| }| },

OPTIONAL,

RadioLinkReconfigurationRequestTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-AllowedQueuingTime CRITICALITY reject TYPE AllowedQueuingTime PRESENCE optional } | { ID id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD CRITICALITY notify TYPE UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD optional } |

PRESENCE

3GPP

Release 11
{ ID optional { ID optional { ID optional { ID { ID { ID ... }

833

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE PRESENCE PRESENCE

id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD CRITICALITY notify TYPE UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD } | id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD CRITICALITY notify TYPE DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD } | id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD CRITICALITY notify TYPE DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD } | id-TDD-DCHs-to-Modify CRITICALITY reject TYPE TDD-DCHs-to-Modify PRESENCE optional } | id-DCHs-to-Add-TDD CRITICALITY reject TYPE DCH-TDD-Information PRESENCE optional } | id-DCH-DeleteList-RL-ReconfRqstTDD CRITICALITY reject TYPE DCH-DeleteList-RL-ReconfRqstTDD PRESENCE optional },

UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD InformationModifyList-RL-ReconfRqstTDD-IEs} }

::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-

UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD CRITICALITY notify mandatory } }

TYPE UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD

PRESENCE

UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-SIRTarget CRITICALITY reject EXTENSION UL-SIR PRESENCE -- Applicable to 1.28Mcps TDD only ... } UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD InformationDeleteList-RL-ReconfRqstTDD-IEs} } optional },

::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {UL-CCTrCH-

UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD CRITICALITY notify mandatory } }

TYPE UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD

PRESENCE

UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD InformationModifyList-RL-ReconfRqstTDD-IEs} }

834

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-

DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD CRITICALITY notify mandatory } }

TYPE DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD

PRESENCE

DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, tFCS TFCS OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD InformationDeleteList-RL-ReconfRqstTDD-IEs} } ::= SEQUENCE (SIZE (0..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container { {DL-CCTrCH-

DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD CRITICALITY notify mandatory } }

TYPE DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD

PRESENCE

DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs} } OPTIONAL, ... } DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-DeleteList-RL-ReconfRqstTDD ::= SEQUENCE (SIZE(0..maxNrOfDCHs)) OF DCH-DeleteItem-RL-ReconfRqstTDD

DCH-DeleteItem-RL-ReconfRqstTDD ::= SEQUENCE { dCH-ID DCH-ID, iE-Extensions ProtocolExtensionContainer { {DCH-DeleteItem-RL-ReconfRqstTDD-ExtIEs} } OPTIONAL, ... } DCH-DeleteItem-RL-ReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkReconfigurationRequestTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
{ ID id-RL-ReconfigurationRequestTDD-RL-Information CRITICALITY optional}| { ID id-HSDSCH-TDD-Information CRITICALITY reject { ID id-HSDSCH-Information-to-Modify-Unsynchronised CRITICALITY optional}| { ID id-HSDSCH-MACdFlows-to-Add CRITICALITY reject { ID id-HSDSCH-MACdFlows-to-Delete CRITICALITY reject { ID id-HSPDSCH-RL-ID CRITICALITY reject { ID id-E-DCH-Information-Reconfig CRITICALITY reject { ID id-E-DCH-Serving-RL-ID CRITICALITY reject { ID id-E-DCH-768-Information-Reconfig CRITICALITY reject { ID id-E-DCH-LCR-Information-Reconfig CRITICALITY reject { ID id-CPC-InformationLCR CRITICALITY reject { ID id-RNTI-Allocation-Indicator CRITICALITY ignore { ID id-DCH-MeasurementType-Indicator CRITICALITY reject { ID id-Multi-Carrier-EDCH-Reconfigure CRITICALITY reject { ID id-MU-MIMO-Indicator CRITICALITY reject ... } ignore

835

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

EXTENSION Multiple-RL-ReconfigurationRequestTDD-RL-Information

EXTENSION HSDSCH-TDD-Information PRESENCE optional}| reject EXTENSION HSDSCH-Information-to-Modify-Unsynchronised PRESENCE EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION HSDSCH-MACdFlows-Information HSDSCH-MACdFlows-to-Delete RL-ID E-DCH-Information-Reconfig RL-ID E-DCH-768-Information-Reconfig E-DCH-LCR-Information-Reconfig CPC-InformationLCR RNTI-Allocation-Indicator DCH-MeasurementType-Indicator Multi-Carrier-EDCH-Reconfigure MU-MIMO-Indicator PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional}| optional},

Multiple-RL-ReconfigurationRequestTDD-RL-Information ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF RL-ReconfigurationRequestTDD-RL-Information RL-ReconfigurationRequestTDD-RL-Information ::= SEQUENCE { rL-ID RL-ID, rL-Specific-DCH-Info RL-Specific-DCH-Info OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-ReconfigurationRequestTDD-RL-Information-ExtIEs} } OPTIONAL, ... } RL-ReconfigurationRequestTDD-RL-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-Synchronisation-Parameters-LCR CRITICALITY ignore EXTENSION UL-Synchronisation-Parameters-LCR optional }| -- Mandatory for 1.28Mcps TDD, Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD { ID id-NeedforIdleInterval CRITICALITY ignore EXTENSION NeedforIdleInterval optional }, ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION RESPONSE FDD --- ************************************************************** RadioLinkReconfigurationResponseFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationResponseFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationResponseFDD-Extensions}} ... } RadioLinkReconfigurationResponseFDD-IEs RNSAP-PROTOCOL-IES ::= { PRESENCE PRESENCE

OPTIONAL,

3GPP

Release 11

836

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

{ ID id-RL-InformationResponseList-RL-ReconfRspFDD CRITICALITY ignore TYPE RL-InformationResponseList-RL-ReconfRspFDD optional } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } RL-InformationResponseList-RL-ReconfRspFDD ReconfRspFDD-IEs} }

::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationResponse-RL-

RL-InformationResponse-RL-ReconfRspFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponseItem-RL-ReconfRspFDD CRITICALITY ignore mandatory } }

TYPE RL-InformationResponseItem-RL-ReconfRspFDD

PRESENCE

RL-InformationResponseItem-RL-ReconfRspFDD ::= SEQUENCE { rL-ID RL-ID, max-UL-SIR UL-SIR OPTIONAL, min-UL-SIR UL-SIR OPTIONAL, maximumDLTxPower DL-Power OPTIONAL, minimumDLTxPower DL-Power OPTIONAL, not-Used-secondary-CCPCH-Info NULL OPTIONAL, dCHsInformationResponseList DCH-InformationResponseList-RL-ReconfRspFDD OPTIONAL, dL-CodeInformationList-RL-ReconfResp DL-CodeInformationList-RL-ReconfRspFDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponseItem-RL-ReconfRspFDD-ExtIEs} } OPTIONAL, ... } RL-InformationResponseItem-RL-ReconfRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-PowerBalancing-UpdatedIndicator CRITICALITY ignore EXTENSION optional }| { ID id-EDCH-FDD-InformationResponse CRITICALITY ignore EXTENSION optional }| { ID id-EDCH-RLSet-Id CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-EDCH-FDD-DL-ControlChannelInformation CRITICALITY ignore EXTENSION { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-HSDSCH-PreconfigurationInfo CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Non-Serving-RL-Preconfig-Info CRITICALITY ignore EXTENSION optional }, ... } DCH-InformationResponseList-RL-ReconfRspFDD DL-PowerBalancing-UpdatedIndicator EDCH-FDD-InformationResponse RL-Set-ID EDCH-FDD-DL-ControlChannelInformation F-DPCH-SlotFormat HSDSCH-PreconfigurationInfo Non-Serving-RL-Preconfig-Info PRESENCE PRESENCE optional }| PRESENCE PRESENCE

::= ProtocolIE-Single-Container { {DCH-InformationResponseListIEs-RL-ReconfRspFDD} } PRESENCE mandatory }

DCH-InformationResponseListIEs-RL-ReconfRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse }

DL-CodeInformationList-RL-ReconfRspFDD ::= ProtocolIE-Single-Container {{ DL-CodeInformationListIEs-RL-ReconfRspFDD }}

3GPP

Release 11

837
PRESENCE optional }

3GPP TS 25.423 V11.2.0 (2012-06)

DL-CodeInformationListIEs-RL-ReconfRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-FDD-DL-CodeInformation CRITICALITY ignore TYPE FDD-DL-CodeInformation }

RadioLinkReconfigurationResponseFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional }| { ID id-HSDSCH-FDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-FDD-Information-Response PRESENCE optional }| { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs-ResetIndicator PRESENCE optional }| { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response CRITICALITY ignore EXTENSION Continuous-PacketConnectivity-HS-SCCH-Less-Information-Response PRESENCE optional }| { ID id-Additional-HS-Cell-Information-Response CRITICALITY ignore EXTENSION Additional-HS-Cell-Information-Response-List PRESENCE optional }| { ID id-Additional-EDCH-Cell-Information-ResponseRLReconf CRITICALITY ignore EXTENSION Additional-EDCH-Cell-Information-Response-RLReconfList PRESENCE optional }, ... } -- ************************************************************** --- RADIO LINK RECONFIGURATION RESPONSE TDD --- ************************************************************** RadioLinkReconfigurationResponseTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkReconfigurationResponseTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkReconfigurationResponseTDD-Extensions}} ... } RadioLinkReconfigurationResponseTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationResponse-RL-ReconfRspTDD CRITICALITY ignore TYPE RL-InformationResponse-RL-ReconfRspTDD optional } | --This RL-InformationResponse-RL-ReconfRspTDD is for the first RL repetition in the list. --Repetitions 2 and on are defined in Multiple-RL-InformationResponse-RL-ReconfRspTDD. { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } RL-InformationResponse-RL-ReconfRspTDD ::= SEQUENCE { rL-ID RL-ID, max-UL-SIR UL-SIR OPTIONAL, min-UL-SIR UL-SIR OPTIONAL, maximumDLTxPower DL-Power OPTIONAL, minimumDLTxPower DL-Power OPTIONAL, dCHsInformationResponseList DCH-InformationResponseList-RL-ReconfRspTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationResponse-RL-ReconfRspTDD-ExtIEs} } OPTIONAL, ... }

OPTIONAL,

PRESENCE

3GPP

Release 11

838

3GPP TS 25.423 V11.2.0 (2012-06)

RL-InformationResponse-RL-ReconfRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-CCTrCH-InformationList-RL-ReconfRspTDD CRITICALITY ignore EXTENSION DL-CCTrCH-InformationList-RL-ReconfRspTDD PRESENCE optional }| { ID id-UL-TimingAdvanceCtrl-LCR CRITICALITY ignore EXTENSION UL-TimingAdvanceCtrl-LCR PRESENCE optional }, --For 1.28Mcps TDD only ... } DL-CCTrCH-InformationList-RL-ReconfRspTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationItem-RL-ReconfRspTDD DL-CCTrCH-InformationItem-RL-ReconfRspTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-ModifyInformation-LCR DL-DPCH-InformationModifyList-LCR-RL-ReconfRspTDD OPTIONAL, --For 1.28Mcps TDD only cCTrCH-Maximum-DL-Power DL-Power OPTIONAL, --For 3.84Mcps TDD and 7.68Mcps TDD only, this is a DCH type CCTrCH power cCTrCH-Minimum-DL-Power DL-Power OPTIONAL, --For 3.84Mcps TDD and 7.68Mcps TDD only, this is a DCH type CCTrCH power iE-Extensions ProtocolExtensionContainer { { DL-CCTrCH-InformationItem-RL-ReconfRspTDD-ExtIEs} } ... } DL-CCTrCH-InformationItem-RL-ReconfRspTDD-ExtIEs ... } DL-DPCH-InformationModifyList-LCR-RL-ReconfRspTDD RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

::= ProtocolIE-Single-Container {{ DL-DPCH-InformationModifyListIEs-LCR-RL-ReconfRspTDD }} TYPE DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD

DL-DPCH-InformationModifyListIEs-LCR-RL-ReconfRspTDD RNSAP-PROTOCOL-IES ::= { {ID id-DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD CRITICALITY ignore PRESENCE optional }, ... }

DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD ::= SEQUENCE { dL-Timeslot-LCR-InformationModifyList-RL-ReconfRqstTDD DL-Timeslot-LCR-InformationModifyList-RL-ReconfRspTDD iE-ExtensionsProtocolExtensionContainer { { DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD-ExtIEs} } ... } DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

OPTIONAL,

DL-Timeslot-LCR-InformationModifyList-RL-ReconfRspTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTsLCR)) OF DL-Timeslot-LCR-InformationModifyItem-RL-ReconfRspTDD DL-Timeslot-LCR-InformationModifyItem-RL-ReconfRspTDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, maxPowerLCR DL-Power OPTIONAL, minPowerLCR DL-Power OPTIONAL,

3GPP

Release 11
iE-Extensions OPTIONAL, ...

839

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { DL-Timeslot-LCR-InformationModifyItem-RL-ReconfRspTDD-ExtIEs} }

DL-Timeslot-LCR-InformationModifyItem-RL-ReconfRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-InformationResponseList-RL-ReconfRspTDD ::= ProtocolIE-Single-Container { {DCH-InformationResponseListIEs-RL-ReconfRspTDD} } PRESENCE optional }

DCH-InformationResponseListIEs-RL-ReconfRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-DCH-InformationResponse CRITICALITY ignore TYPE DCH-InformationResponse }

RadioLinkReconfigurationResponseTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-HSDSCH-TDD-Information-Response CRITICALITY ignore EXTENSION HSDSCH-TDD-Information-Response PRESENCE optional}| { ID id-MAChs-ResetIndicator CRITICALITY ignore EXTENSION MAChs-ResetIndicator PRESENCE optional}| { ID id-RL-ReconfigurationResponseTDD-RL-Information CRITICALITY ignore EXTENSION Multiple-RL-InformationResponse-RL-ReconfRspTDD PRESENCE optional}| { ID id-E-DCH-Information-Response CRITICALITY ignore EXTENSION E-DCH-Information-Response PRESENCE optional}| { ID id-E-DCH-768-Information-Response CRITICALITY ignore EXTENSION E-DCH-768-Information-Response PRESENCE optional}| { ID id-E-DCH-LCR-Information-Response CRITICALITY ignore EXTENSION E-DCH-LCR-Information-Response PRESENCE optional}| { ID id-PowerControlGAP CRITICALITY ignore EXTENSION ControlGAP PRESENCE optional}| -- Applicable to 1.28Mcps TDD only { ID id-IdleIntervalInformation CRITICALITY ignore EXTENSION IdleIntervalInformation PRESENCE optional}| { ID id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR CRITICALITY ignore EXTENSION ContinuousPacketConnectivity-DRX-InformationResponseLCR PRESENCE optional}| { ID id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION HS-DSCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR CRITICALITY ignore EXTENSION E-DCH-Semi-PersistentScheduling-InformationResponseLCR PRESENCE optional}| { ID id-E-RNTI-For-FACH CRITICALITY ignore EXTENSION E-RNTI PRESENCE optional}| { ID id-H-RNTI-For-FACH CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional}| { ID id-DCH-MeasurementOccasion-Information CRITICALITY reject EXTENSION DCH-MeasurementOccasion-Information PRESENCE optional}| { ID id-Multi-Carrier-EDCH-Response CRITICALITY ignore EXTENSION Multi-Carrier-EDCH-Information-Response PRESENCE optional}| { ID id-MU-MIMO-InformationLCR CRITICALITY reject EXTENSION MU-MIMO-InformationLCR PRESENCE optional}, ... } Multiple-RL-InformationResponse-RL-ReconfRspTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF RL-InformationResponse-RL-ReconfRspTDD --Includes the 2nd through the max number of radio link information repetitions. -- ************************************************************** --- RADIO LINK FAILURE INDICATION --- ************************************************************** RadioLinkFailureIndication ::= SEQUENCE {

3GPP

Release 11
protocolIEs protocolExtensions ...

840
ProtocolIE-Container {{RadioLinkFailureIndication-IEs}}, ProtocolExtensionContainer {{RadioLinkFailureIndication-Extensions}}

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RadioLinkFailureIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Reporting-Object-RL-FailureInd CRITICALITY ignore ... } Reporting-Object-RL-FailureInd ::= CHOICE { rL RL-RL-FailureInd, rL-Set RL-Set-RL-FailureInd, --FDD only ..., cCTrCH CCTrCH-RL-FailureInd --TDD only } RL-RL-FailureInd ::= SEQUENCE { rL-InformationList-RL-FailureInd iE-Extensions ... }

TYPE Reporting-Object-RL-FailureInd

PRESENCE mandatory

},

RL-InformationList-RL-FailureInd, ProtocolExtensionContainer { { RLItem-RL-FailureInd-ExtIEs} } OPTIONAL,

RLItem-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-RL-FailureInd ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-RL-FailureInd-IEs} } TYPE RL-Information-RL-FailureInd PRESENCE mandatory }

RL-Information-RL-FailureInd-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-FailureInd CRITICALITY ignore }

RL-Information-RL-FailureInd ::= SEQUENCE { rL-ID RL-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-FailureInd-ExtIEs} } OPTIONAL, ... } RL-Information-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-RL-FailureInd ::= SEQUENCE { rL-Set-InformationList-RL-FailureInd RL-Set-InformationList-RL-FailureInd, iE-Extensions ProtocolExtensionContainer { { RL-SetItem-RL-FailureInd-ExtIEs} } OPTIONAL, ... } RL-SetItem-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

841

3GPP TS 25.423 V11.2.0 (2012-06)

RL-Set-InformationList-RL-FailureInd FailureInd-IEs} }

::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-Information-RL-

RL-Set-Information-RL-FailureInd-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-Information-RL-FailureInd CRITICALITY ignore }

TYPE RL-Set-Information-RL-FailureInd

PRESENCE mandatory

RL-Set-Information-RL-FailureInd ::= SEQUENCE { rL-Set-ID RL-Set-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { {RL-Set-Information-RL-FailureInd-ExtIEs} } OPTIONAL, ... } RL-Set-Information-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkFailureIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } CCTrCH-RL-FailureInd ::= SEQUENCE { rL-ID cCTrCH-InformationList-RL-FailureInd iE-Extensions ... } RL-ID, CCTrCH-InformationList-RL-FailureInd, ProtocolExtensionContainer { { CCTrCHItem-RL-FailureInd-ExtIEs } }

OPTIONAL,

CCTrCHItem-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CCTrCH-InformationList-RL-FailureInd ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ CCTrCH-InformationItemIE-RL-FailureInd}} CCTrCH-InformationItemIE-RL-FailureInd RNSAP-PROTOCOL-IES ::= { { ID id-CCTrCH-InformationItem-RL-FailureInd CRITICALITY PRESENCE mandatory} } ignore TYPE CCTrCH-InformationItem-RL-FailureInd

CCTrCH-InformationItem-RL-FailureInd ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, cause Cause, iE-Extensions ProtocolExtensionContainer { { CCTrCH-InformationItem-RL-FailureInd-ExtIEs } } ... } CCTrCH-InformationItem-RL-FailureInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

3GPP

Release 11
} ...

842

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- RADIO LINK PREEMPTION REQUIRED INDICATION --- ************************************************************** RadioLinkPreemptionRequiredIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkPreemptionRequiredIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkPreemptionRequiredIndication-Extensions}} ... } RadioLinkPreemptionRequiredIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationList-RL-PreemptRequiredInd CRITICALITY ignore optional }, ... } RL-InformationList-RL-PreemptRequiredInd PreemptRequiredInd} } TYPE RL-InformationList-RL-PreemptRequiredInd

OPTIONAL,

PRESENCE

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationItemIEs-RL-

RL-InformationItemIEs-RL-PreemptRequiredInd RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-RL-PreemptRequiredInd CRITICALITY ignore mandatory } }

TYPE RL-InformationItem-RL-PreemptRequiredInd

PRESENCE

RL-InformationItem-RL-PreemptRequiredInd::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-PreemptRequiredInd-ExtIEs} } OPTIONAL, ... } RL-Information-RL-PreemptRequiredInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-EDCH-MacdFlowSpecificInformationList-RL-PreemptRequiredInd CRITICALITY ignore PreemptRequiredInd PRESENCE optional }, ... } EXTENSION EDCH-MacdFlowSpecificInformationList-RL-

RadioLinkPreemptionRequiredIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCHMacdFlowSpecificInformationList-RL-PreemptRequiredInd CRITICALITY ignore EXTENSION HSDSCHMacdFlowSpecificInformationList-RLPreemptRequiredInd PRESENCE optional }, ... } HSDSCHMacdFlowSpecificInformationList-RL-PreemptRequiredInd ::= SEQUENCE (SIZE (1.. maxNrOfMACdFlows)) OF ProtocolIE-Single-Container { {HSDSCHMacdFlowSpecificInformationItemIEs-RL-PreemptRequiredInd} } HSDSCHMacdFlowSpecificInformationItemIEs-RL-PreemptRequiredInd RNSAP-PROTOCOL-IES ::= {

3GPP

Release 11
{ ID id-HSDSCHMacdFlowSpecificInformationItem-RL-PreemptRequiredInd PreemptRequiredInd PRESENCE mandatory } }

843
CRITICALITY ignore

3GPP TS 25.423 V11.2.0 (2012-06)

TYPE HSDSCHMacdFlowSpecificInformationItem-RL-

HSDSCHMacdFlowSpecificInformationItem-RL-PreemptRequiredInd ::= SEQUENCE { hSDSCH-MACdFlow-ID HSDSCH-MACdFlow-ID, iE-Extensions ProtocolExtensionContainer { { HSDSCHMacdFlowSpecificInformation-RL-PreemptRequiredInd-ExtIEs} } OPTIONAL, ... } HSDSCHMacdFlowSpecificInformation-RL-PreemptRequiredInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-MacdFlowSpecificInformationList-RL-PreemptRequiredInd ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF ProtocolIE-Single-Container { {EDCHMacdFlowSpecificInformationItemIEs-RL-PreemptRequiredInd} } EDCH-MacdFlowSpecificInformationItemIEs-RL-PreemptRequiredInd RNSAP-PROTOCOL-IES ::= { { ID id-EDCH-MacdFlowSpecificInformationItem-RL-PreemptRequiredInd CRITICALITY ignore PreemptRequiredInd PRESENCE mandatory } } TYPE EDCH-MacdFlowSpecificInformationItem-RL-

EDCH-MacdFlowSpecificInformationItem-RL-PreemptRequiredInd ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, iE-Extensions ProtocolExtensionContainer { { EDCH-MacdFlowSpecificInformation-RL-PreemptRequiredInd-ExtIEs} } OPTIONAL, ... } EDCH-MacdFlowSpecificInformation-RL-PreemptRequiredInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK RESTORE INDICATION --- ************************************************************** RadioLinkRestoreIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkRestoreIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkRestoreIndication-Extensions}} ... } RadioLinkRestoreIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Reporing-Object-RL-RestoreInd CRITICALITY ignore ... } Reporting-Object-RL-RestoreInd ::= CHOICE { TYPE Reporting-Object-RL-RestoreInd

OPTIONAL,

PRESENCE mandatory

},

3GPP

Release 11
rL rL-Set ..., cCTrCH } RL-RL-RestoreInd ::= SEQUENCE { rL-InformationList-RL-RestoreInd iE-Extensions ... } RL-RL-RestoreInd, --TDD only RL-Set-RL-RestoreInd, --FDD only CCTrCH-RL-RestoreInd --TDD only

844

3GPP TS 25.423 V11.2.0 (2012-06)

RL-InformationList-RL-RestoreInd, ProtocolExtensionContainer { { RLItem-RL-RestoreInd-ExtIEs} } OPTIONAL,

RLItem-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-RL-RestoreInd ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-RL-RestoreInd-IEs} } TYPE RL-Information-RL-RestoreInd PRESENCE mandatory }

RL-Information-RL-RestoreInd-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-RL-RestoreInd CRITICALITY ignore }

RL-Information-RL-RestoreInd ::= SEQUENCE { rL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-RestoreInd-ExtIEs} } OPTIONAL, ... } RL-Information-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-RL-RestoreInd ::= SEQUENCE { rL-Set-InformationList-RL-RestoreInd iE-Extensions ... } RL-Set-InformationList-RL-RestoreInd, ProtocolExtensionContainer { { RL-SetItem-RL-RestoreInd-ExtIEs} } OPTIONAL,

RL-SetItem-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-InformationList-RL-RestoreInd RestoreInd-IEs} } ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-Information-RL-

RL-Set-Information-RL-RestoreInd-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-Information-RL-RestoreInd CRITICALITY ignore } RL-Set-Information-RL-RestoreInd ::= SEQUENCE { rL-Set-ID RL-Set-ID,

TYPE RL-Set-Information-RL-RestoreInd

PRESENCE mandatory

3GPP

Release 11
iE-Extensions ... } RL-Set-Information-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkRestoreIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } CCTrCH-RL-RestoreInd ::= SEQUENCE { rL-ID cCTrCH-InformationList-RL-RestoreInd iE-Extensions ... }

845
ProtocolExtensionContainer { {RL-Set-Information-RL-RestoreInd-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

RL-ID, CCTrCH-InformationList-RL-RestoreInd, ProtocolExtensionContainer { { CCTrCHItem-RL-RestoreInd-ExtIEs } }

OPTIONAL,

CCTrCHItem-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CCTrCH-InformationList-RL-RestoreInd ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF ProtocolIE-Single-Container {{ CCTrCH-InformationItemIE-RL-RestoreInd}} CCTrCH-InformationItemIE-RL-RestoreInd RNSAP-PROTOCOL-IES ::= { { ID id-CCTrCH-InformationItem-RL-RestoreInd CRITICALITY PRESENCE mandatory} } ignore TYPE CCTrCH-InformationItem-RL-RestoreInd

CCTrCH-InformationItem-RL-RestoreInd ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, iE-Extensions ProtocolExtensionContainer { { CCTrCH-InformationItem-RL-RestoreInd-ExtIEs } } ... } CCTrCH-InformationItem-RL-RestoreInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- DOWNLINK POWER CONTROL REQUEST --- ************************************************************** DL-PowerControlRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DL-PowerControlRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{DL-PowerControlRequest-Extensions}} ... }

OPTIONAL,

OPTIONAL,

3GPP

Release 11
DL-PowerControlRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-PowerAdjustmentType CRITICALITY ignore { ID id-DLReferencePower CRITICALITY ignore -- This IE shall be present if Power Adjustment Type IE equals { ID id-InnerLoopDLPCStatus CRITICALITY ignore { ID id-DLReferencePowerList-DL-PC-Rqst CRITICALITY ignore -- This IE shall be present if Power Adjustment Type IE equals { ID id-MaxAdjustmentStep CRITICALITY ignore -- This IE shall be present if Power Adjustment Type IE equals { ID id-AdjustmentPeriod CRITICALITY ignore -- This IE shall be present if Power Adjustment Type IE equals { ID id-AdjustmentRatio CRITICALITY ignore -- This IE shall be present if Power Adjustment Type IE equals ... } DL-ReferencePowerInformationList-DL-PC-Rqst DL-PC-Rqst-IEs} }

846

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory} | PRESENCE conditional} | PRESENCE optional } | PRESENCE conditional} | PRESENCE conditional } | PRESENCE conditional }| PRESENCE conditional },

to to to to to

TYPE PowerAdjustmentType TYPE DL-Power Common TYPE InnerLoopDLPCStatus TYPE DL-ReferencePowerInformationList-DL-PC-Rqst Individual TYPE MaxAdjustmentStep Common or Individual TYPE AdjustmentPeriod Common or Individual TYPE ScaledAdjustmentRatio Common or Individual

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {DL-ReferencePowerInformation-

DL-ReferencePowerInformation-DL-PC-Rqst-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DL-ReferencePowerInformation-DL-PC-Rqst CRITICALITY ignore }

TYPE DL-ReferencePowerInformation-DL-PC-Rqst

PRESENCE mandatory

DL-ReferencePowerInformation-DL-PC-Rqst ::= SEQUENCE { rL-ID RL-ID, dl-Reference-Power DL-Power, iE-Extensions ProtocolExtensionContainer { {DL-ReferencePowerInformation-DL-PC-Rqst-ExtIEs} } OPTIONAL, ... } DL-ReferencePowerInformation-DL-PC-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-PowerControlRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- DOWNLINK POWER TIMESLOT CONTROL REQUEST TDD --- ************************************************************** DL-PowerTimeslotControlRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DL-PowerTimeslotControlRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{DL-PowerTimeslotControlRequest-Extensions}} ... }

OPTIONAL,

3GPP

Release 11
DL-PowerTimeslotControlRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-timeSlot-ISCP CRITICALITY ignore TYPE DL-TimeSlot-ISCP-Info --Mandatory for 3.84Mcps TDD and 7.68 Mcps TDD only ... } DL-PowerTimeslotControlRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-timeSlot-ISCP-LCR-List-DL-PC-Rqst-TDD CRITICALITY ignore --Mandatory for 1.28Mcps TDD only { ID id-PrimCCPCH-RSCP-DL-PC-RqstTDD CRITICALITY ignore PRESENCE optional }| { ID id-PrimaryCCPCH-RSCP-Delta CRITICALITY ignore optional }, ... } -- ************************************************************** --- PHYSICAL CHANNEL RECONFIGURATION REQUEST FDD --- **************************************************************

847
PRESENCE optional},

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION

DL-TimeSlot-ISCP-LCR-Information PRESENCE optional}|

EXTENSION PrimaryCCPCH-RSCP EXTENSION PrimaryCCPCH-RSCP-Delta PRESENCE

PhysicalChannelReconfigurationRequestFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{PhysicalChannelReconfigurationRequestFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{PhysicalChannelReconfigurationRequestFDD-Extensions}} ... } PhysicalChannelReconfigurationRequestFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-PhyChReconfRqstFDD CRITICALITY reject TYPE RL-Information-PhyChReconfRqstFDD ... } RL-Information-PhyChReconfRqstFDD ::= SEQUENCE { rL-ID RL-ID, dl-CodeInformation DL-CodeInformationList-PhyChReconfRqstFDD, iE-Extensions ProtocolExtensionContainer { {RL-Information-PhyChReconfRqstFDD-ExtIEs} } OPTIONAL, ... } RL-Information-PhyChReconfRqstFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-F-DPCH-SlotFormat CRITICALITY ignore EXTENSION F-DPCH-SlotFormat ... } DL-CodeInformationList-PhyChReconfRqstFDD PRESENCE optional},

OPTIONAL,

PRESENCE mandatory

},

::= ProtocolIE-Single-Container { {DL-CodeInformationListIEs-PhyChReconfRqstFDD} } }

DL-CodeInformationListIEs-PhyChReconfRqstFDD RNSAP-PROTOCOL-IES ::= { { ID id-FDD-DL-CodeInformation CRITICALITY notify TYPE FDD-DL-CodeInformation PRESENCE mandatory }

3GPP

Release 11

848

3GPP TS 25.423 V11.2.0 (2012-06)

PhysicalChannelReconfigurationRequestFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- PHYSICAL CHANNEL RECONFIGURATION REQUEST TDD --- ************************************************************** PhysicalChannelReconfigurationRequestTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{PhysicalChannelReconfigurationRequestTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{PhysicalChannelReconfigurationRequestTDD-Extensions}} ... } PhysicalChannelReconfigurationRequestTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Information-PhyChReconfRqstTDD CRITICALITY reject TYPE RL-Information-PhyChReconfRqstTDD ... } RL-Information-PhyChReconfRqstTDD ::= SEQUENCE { rL-ID RL-ID, ul-CCTrCH-Information UL-CCTrCH-InformationList-PhyChReconfRqstTDD OPTIONAL, dl-CCTrCH-Information DL-CCTrCH-InformationList-PhyChReconfRqstTDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Information-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... } RL-Information-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD CRITICALITY reject PhyChReconfRqstTDD PRESENCE optional } | --For 3.84Mcps TDD only { ID id-HSPDSCH-Timeslot-InformationListLCR-PhyChReconfRqstTDD CRITICALITY reject PhyChReconfRqstTDD PRESENCE optional }| --For 1.28Mcps TDD only { ID id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD768 CRITICALITY reject PhyChReconfRqstTDD768 PRESENCE optional }| --For 7.68Mcps TDD only { ID id-UARFCNforNt CRITICALITY ignore -- Applicable to 1.28Mcps TDD only ... } UL-CCTrCH-InformationList-PhyChReconfRqstTDD EXTENSION HSPDSCH-Timeslot-InformationListEXTENSION HSPDSCH-Timeslot-InformationListLCREXTENSION HSPDSCH-Timeslot-InformationListEXTENSION UARFCN PRESENCE optional },

OPTIONAL,

PRESENCE mandatory

},

::= ProtocolIE-Single-Container { {UL-CCTrCH-InformationListIEs-PhyChReconfRqstTDD} } TYPE UL-CCTrCH-InformationListIE-PhyChReconfRqstTDD

UL-CCTrCH-InformationListIEs-PhyChReconfRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-CCTrCH-InformationListIE-PhyChReconfRqstTDD CRITICALITY reject PRESENCE mandatory } }

3GPP

Release 11

849

3GPP TS 25.423 V11.2.0 (2012-06)

UL-CCTrCH-InformationListIE-PhyChReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF UL-CCTrCH-InformationItem-PhyChReconfRqstTDD UL-CCTrCH-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, ul-DPCH-Information UL-DPCH-InformationList-PhyChReconfRqstTDD, iE-Extensions ProtocolExtensionContainer { {UL-CCTrCH-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... } UL-CCTrCH-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-DPCH-InformationList-PhyChReconfRqstTDD ::= ProtocolIE-Single-Container {{UL-DPCH-InformationListIEs-PhyChReconfRqstTDD}} UL-DPCH-InformationListIEs-PhyChReconfRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-UL-DPCH-InformationItem-PhyChReconfRqstTDD CRITICALITY notify TYPE UL-DPCH-InformationItem-PhyChReconfRqstTDD mandatory } } UL-DPCH-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod OPTIONAL, repetitionLength RepetitionLength OPTIONAL, tDD-DPCHOffset TDD-DPCHOffset OPTIONAL, uL-Timeslot-InformationList-PhyChReconfRqstTDD UL-Timeslot-InformationList-PhyChReconfRqstTDD OPTIONAL, --For 3.84Mcps TDD only iE-Extensions ProtocolExtensionContainer { {UL-DPCH-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... } UL-DPCH-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD CRITICALITY reject PRESENCE optional }| --For 1.28Mcps TDD only { ID id-UL-Timeslot-InformationList-PhyChReconfRqstTDD768 CRITICALITY reject PRESENCE optional }, --For 7.68Mcps TDD only ... } EXTENSION EXTENSION UL-TimeslotLCR-InformationList-PhyChReconfRqstTDD UL-Timeslot-InformationList-PhyChReconfRqstTDD768 PRESENCE

UL-TimeslotLCR-InformationList-PhyChReconfRqstTDD::= SEQUENCE ( SIZE (1..maxNrOfTsLCR)) OF UL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD UL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, uL-Code-LCR-Information TDD-UL-Code-LCR-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

850

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional },

UL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-PLCCH-Information-PhyChReconfRqstTDD CRITICALITY reject EXTENSION PLCCHinformation ... }

UL-Timeslot-InformationList-PhyChReconfRqstTDD::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationItem-PhyChReconfRqstTDD UL-Timeslot-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, uL-Code-Information TDD-UL-Code-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... } UL-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-Timeslot-InformationList-PhyChReconfRqstTDD768::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationItem-PhyChReconfRqstTDD768 UL-Timeslot-InformationItem-PhyChReconfRqstTDD768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768 OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, uL-Code-Information768 TDD-UL-Code-Information768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {UL-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs} } OPTIONAL, ... } UL-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-CCTrCH-InformationList-PhyChReconfRqstTDD ::= ProtocolIE-Single-Container { {DL-CCTrCH-InformationListIEs-PhyChReconfRqstTDD} } TYPE DL-CCTrCH-InformationListIE-PhyChReconfRqstTDD

DL-CCTrCH-InformationListIEs-PhyChReconfRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-CCTrCH-InformationListIE-PhyChReconfRqstTDD CRITICALITY reject PRESENCE mandatory } }

DL-CCTrCH-InformationListIE-PhyChReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfCCTrCHs)) OF DL-CCTrCH-InformationItem-PhyChReconfRqstTDD DL-CCTrCH-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { cCTrCH-ID CCTrCH-ID, dl-DPCH-Information DL-DPCH-InformationList-PhyChReconfRqstTDD, iE-Extensions ProtocolExtensionContainer { {DL-CCTrCH-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

851

3GPP TS 25.423 V11.2.0 (2012-06)

DL-CCTrCH-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-DPCH-InformationList-PhyChReconfRqstTDD ::= ProtocolIE-Single-Container {{DL-DPCH-InformationListIEs-PhyChReconfRqstTDD}} DL-DPCH-InformationListIEs-PhyChReconfRqstTDD RNSAP-PROTOCOL-IES ::= { { ID id-DL-DPCH-InformationItem-PhyChReconfRqstTDD CRITICALITY notify TYPE DL-DPCH-InformationItem-PhyChReconfRqstTDD mandatory } } DL-DPCH-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { repetitionPeriod RepetitionPeriod repetitionLength RepetitionLength tDD-DPCHOffset TDD-DPCHOffset dL-Timeslot-InformationList-PhyChReconfRqstTDD DL-Timeslot-InformationList-PhyChReconfRqstTDD iE-Extensions ProtocolExtensionContainer { {DL-DPCH-InformationItem-PhyChReconfRqstTDD-ExtIEs} } ... } DL-DPCH-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD CRITICALITY reject PRESENCE optional }| --For 1.28Mcps TDD only { ID id-DL-Timeslot-InformationList-PhyChReconfRqstTDD768 CRITICALITY reject PRESENCE optional }, --For 7.68Mcps TDD only ... } PRESENCE

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

EXTENSION DL-TimeslotLCR-InformationList-PhyChReconfRqstTDD EXTENSION DL-Timeslot-InformationList-PhyChReconfRqstTDD768

DL-TimeslotLCR-InformationList-PhyChReconfRqstTDD::= SEQUENCE ( SIZE (1..maxNrOfTsLCR)) OF DL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD DL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, dL-Code-LCR-Information TDD-DL-Code-LCR-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL, ... } DL-TimeslotLCR-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-Timeslot-InformationList-PhyChReconfRqstTDD::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationItem-PhyChReconfRqstTDD DL-Timeslot-InformationItem-PhyChReconfRqstTDD ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType tFCI-Presence TFCI-Presence OPTIONAL,

OPTIONAL,

3GPP

Release 11
dL-Code-Information iE-Extensions ...

852

3GPP TS 25.423 V11.2.0 (2012-06)

TDD-DL-Code-Information OPTIONAL, ProtocolExtensionContainer { {DL-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs} } OPTIONAL,

DL-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-Timeslot-InformationList-PhyChReconfRqstTDD768::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationItem-PhyChReconfRqstTDD768 DL-Timeslot-InformationItem-PhyChReconfRqstTDD768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768 OPTIONAL, tFCI-Presence TFCI-Presence OPTIONAL, dL-Code-Information768 TDD-DL-Code-Information768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DL-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs} } OPTIONAL, ... } DL-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD ::= SEQUENCE (SIZE (1..maxNrOfDLTs)) OF HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs } } OPTIONAL, ... } HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSPDSCH-Timeslot-InformationListLCR-PhyChReconfRqstTDD::= SEQUENCE (SIZE (1..maxNrOfDLTsLCR)) OF HSPDSCH-Timeslot-InformationItemLCR-PhyChReconfRqstTDD HSPDSCH-Timeslot-InformationItemLCR-PhyChReconfRqstTDD::= SEQUENCE { timeslotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-Timeslot-InformationItemLCR-PhyChReconfRqstTDD-ExtIEs } } OPTIONAL, ... } HSPDSCH-Timeslot-InformationItemLCR-PhyChReconfRqstTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

853

3GPP TS 25.423 V11.2.0 (2012-06)

HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD768 ::= SEQUENCE (SIZE (1..maxNrOfDLTs)) OF HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD768 HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD768::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs } } OPTIONAL, ... } HSPDSCH-Timeslot-InformationItem-PhyChReconfRqstTDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PhysicalChannelReconfigurationRequestTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- PHYSICAL CHANNEL RECONFIGURATION COMMAND --- ************************************************************** PhysicalChannelReconfigurationCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container {{PhysicalChannelReconfigurationCommand-IEs}}, protocolExtensions ProtocolExtensionContainer {{PhysicalChannelReconfigurationCommand-Extensions}} ... } PhysicalChannelReconfigurationCommand-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CFN CRITICALITY ignore TYPE CFN PRESENCE mandatory } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional ... } PhysicalChannelReconfigurationCommand-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- PHYSICAL CHANNEL RECONFIGURATION FAILURE --- ************************************************************** PhysicalChannelReconfigurationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{PhysicalChannelReconfigurationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{PhysicalChannelReconfigurationFailure-Extensions}} ...

OPTIONAL,

},

OPTIONAL,

3GPP

Release 11
}

854

3GPP TS 25.423 V11.2.0 (2012-06)

PhysicalChannelReconfigurationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional ... } PhysicalChannelReconfigurationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK CONGESTION INDICATION --- ************************************************************** RadioLinkCongestionIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkCongestionIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkCongestionIndication-Extensions}} ... } RadioLinkCongestionIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-CongestionCause CRITICALITY ignore { ID id-RL-InformationList-RL-CongestInd CRITICALITY ignore ... } RL-InformationList-RL-CongestInd CongestInd} } TYPE CongestionCause TYPE RL-InformationList-RL-CongestInd

},

OPTIONAL,

PRESENCE optional }| PRESENCE mandatory },

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-InformationItemIEs-RL-

RL-InformationItemIEs-RL-CongestInd RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-RL-CongestInd CRITICALITY ignore }

TYPE RL-InformationItem-RL-CongestInd

PRESENCE mandatory

RL-InformationItem-RL-CongestInd ::= SEQUENCE { rL-ID RL-ID, dCH-Rate-Information DCH-Rate-Information-RL-CongestInd, iE-Extensions ProtocolExtensionContainer { {RL-Information-RL-CongestInd-ExtIEs} } OPTIONAL, ... } DCH-Rate-Information-RL-CongestInd ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF ProtocolIE-Single-Container { {DCH-Rate-InformationItemIEs-RL-CongestInd} } DCH-Rate-InformationItemIEs-RL-CongestInd RNSAP-PROTOCOL-IES ::= { { ID id-DCH-Rate-InformationItem-RL-CongestInd CRITICALITY ignore } DCH-Rate-InformationItem-RL-CongestInd ::= SEQUENCE { TYPE DCH-Rate-InformationItem-RL-CongestInd PRESENCE mandatory }

3GPP

Release 11
dCH-ID allowed-Rate-Information iE-Extensions ... }

855
DCH-ID, Allowed-Rate-Information OPTIONAL, ProtocolExtensionContainer { {DCH-Rate-InformationItem-RL-CongestInd-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

DCH-Rate-InformationItem-RL-CongestInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Information-RL-CongestInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-EDCH-MacdFlowSpecificInformationList-RL-CongestInd CRITICALITY ignore EXTENSION EDCH-MacdFlowSpecificInformationList-RL-CongestInd PRESENCE optional }| { ID id-DCH-Indicator-For-E-DCH-HSDPA-Operation CRITICALITY ignore EXTENSION DCH-Indicator-For-E-DCH-HSDPA-Operation PRESENCE optional }, ... } RadioLinkCongestionIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-MacdFlowSpecificInformationList-RL-CongestInd ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF ProtocolIE-Single-Container { {EDCHMacdFlowSpecificInformationItemIEs-RL-CongestInd} } EDCH-MacdFlowSpecificInformationItemIEs-RL-CongestInd RNSAP-PROTOCOL-IES ::= { { ID id-EDCH-MacdFlowSpecificInformationItem-RL-CongestInd CRITICALITY ignore PRESENCE mandatory } } TYPE EDCH-MacdFlowSpecificInformationItem-RL-CongestInd

EDCH-MacdFlowSpecificInformationItem-RL-CongestInd ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, iE-Extensions ProtocolExtensionContainer { { EDCH-MacdFlowSpecificInformation-RL-CongestInd-ExtIEs} } OPTIONAL, ... } EDCH-MacdFlowSpecificInformation-RL-CongestInd-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- UPLINK SIGNALLING TRANSFER INDICATION FDD --- ************************************************************** UplinkSignallingTransferIndicationFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UplinkSignallingTransferIndicationFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{UplinkSignallingTransferIndicationFDD-Extensions}} ... }

OPTIONAL,

3GPP

Release 11
UplinkSignallingTransferIndicationFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UC-ID CRITICALITY | { ID id-SAI CRITICALITY | { ID id-GA-Cell CRITICALITY | { ID id-C-RNTI CRITICALITY | { ID id-S-RNTI CRITICALITY | { ID id-D-RNTI CRITICALITY | { ID id-PropagationDelay CRITICALITY | { ID id-STTD-SupportIndicator CRITICALITY { ID id-ClosedLoopMode1-SupportIndicator CRITICALITY { ID id-L3-Information CRITICALITY | { ID id-CN-PS-DomainIdentifier CRITICALITY | { ID id-CN-CS-DomainIdentifier CRITICALITY | { ID id-URA-Information CRITICALITY }, ... }

856
ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore TYPE UC-ID TYPE SAI TYPE GA-Cell TYPE C-RNTI TYPE S-RNTI TYPE D-RNTI TYPE PropagationDelay TYPE STTD-SupportIndicator TYPE ClosedLoopMode1-SupportIndicator TYPE L3-Information TYPE CN-PS-DomainIdentifier TYPE CN-CS-DomainIdentifier TYPE URA-Information

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory PRESENCE mandatory PRESENCE optional PRESENCE mandatory PRESENCE mandatory PRESENCE optional PRESENCE mandatory PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE mandatory PRESENCE optional PRESENCE optional PRESENCE optional } } } } } } }

} } }

UplinkSignallingTransferIndicationFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION GA-CellAdditionalShapes PRESENCE optional }| { ID id-DPC-Mode-Change-SupportIndicator CRITICALITY ignore EXTENSION DPC-Mode-Change-SupportIndicator PRESENCE optional }| { ID id-CommonTransportChannelResourcesInitialisationNotRequired CRITICALITY ignore EXTENSION CommonTransportChannelResourcesInitialisationNotRequired PRESENCE optional }| { ID id-CellCapabilityContainer-FDD CRITICALITY ignore EXTENSION CellCapabilityContainer-FDD PRESENCE optional }| { ID id-SNA-Information CRITICALITY ignore EXTENSION SNA-Information PRESENCE optional }| { ID id-CellPortionID CRITICALITY ignore EXTENSION CellPortionID PRESENCE optional }| { ID id-Active-MBMS-Bearer-ServiceFDD CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListFDD PRESENCE optional}| { ID id-Inter-Frequency-Cell-List CRITICALITY ignore EXTENSION Inter-Frequency-Cell-List PRESENCE optional }| { ID id-ExtendedPropagationDelay CRITICALITY ignore EXTENSION ExtendedPropagationDelay PRESENCE optional }| { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI PRESENCE optional }| { ID id-Multiple-PLMN-List CRITICALITY ignore EXTENSION Multiple-PLMN-List PRESENCE optional }| { ID id-E-RNTI CRITICALITY ignore EXTENSION E-RNTI PRESENCE optional }| { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle PRESENCE conditional }| -- This IE shall be present if the Continuous Packet Connectivity DTX-DRX Support Indicator IE in Cell Capability Container FDD IE is set to 1. { ID id-CellCapabilityContainerExtension-FDD CRITICALITY ignore EXTENSION CellCapabilityContainerExtension-FDD PRESENCE optional }| { ID id-Secondary-Serving-Cell-List CRITICALITY ignore EXTENSION Secondary-Serving-Cell-List PRESENCE optional }| { ID id-Dual-Band-Secondary-Serving-Cell-List CRITICALITY ignore EXTENSION Secondary-Serving-Cell-List PRESENCE optional }| { ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION Extended-RNTI PRESENCE optional }, ... }

3GPP

Release 11
-- ************************************************************** --- UPLINK SIGNALLING TRANSFER INDICATION TDD --- **************************************************************

857

3GPP TS 25.423 V11.2.0 (2012-06)

UplinkSignallingTransferIndicationTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UplinkSignallingTransferIndicationTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{UplinkSignallingTransferIndicationTDD-Extensions}} ... } UplinkSignallingTransferIndicationTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UC-ID CRITICALITY ignore { ID id-SAI CRITICALITY ignore { ID id-GA-Cell CRITICALITY ignore { ID id-C-RNTI CRITICALITY ignore { ID id-S-RNTI CRITICALITY ignore { ID id-D-RNTI CRITICALITY ignore { ID id-RxTimingDeviationForTA CRITICALITY ignore { ID id-L3-Information CRITICALITY ignore { ID id-CN-PS-DomainIdentifier CRITICALITY ignore { ID id-CN-CS-DomainIdentifier CRITICALITY ignore { ID id-URA-Information CRITICALITY ignore ... } TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE UC-ID SAI GA-Cell C-RNTI S-RNTI D-RNTI RxTimingDeviationForTA L3-Information CN-PS-DomainIdentifier CN-CS-DomainIdentifier URA-Information

OPTIONAL,

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

mandatory } | mandatory } | optional } | mandatory } | mandatory } | optional } | mandatory } | mandatory } | optional } | optional } | optional },

UplinkSignallingTransferIndicationTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GA-CellAdditionalShapes CRITICALITY ignore EXTENSION GA-CellAdditionalShapes { ID id-CommonTransportChannelResourcesInitialisationNotRequired CRITICALITY ignore EXTENSION CommonTransportChannelResourcesInitialisationNotRequired { ID id-CellCapabilityContainer-TDD CRITICALITY ignore EXTENSION CellCapabilityContainer-TDD -- Applicable to 3.84Mcps TDD only { ID id-CellCapabilityContainer-TDD-LCR CRITICALITY ignore EXTENSION CellCapabilityContainer-TDD-LCR -- Applicable to 1.28Mcps TDD only { ID id-SNA-Information CRITICALITY ignore EXTENSION SNA-Information { ID id-Active-MBMS-Bearer-ServiceTDD CRITICALITY ignore EXTENSION Active-MBMS-Bearer-Service-ListTDD { ID id-CellCapabilityContainer-TDD768 CRITICALITY ignore EXTENSION CellCapabilityContainer-TDD768 -- Applicable to 7.68Mcps TDD only { ID id-RxTimingDeviationForTA768 CRITICALITY ignore EXTENSION RxTimingDeviationForTA768 { ID id-RxTimingDeviationForTAext CRITICALITY ignore EXTENSION RxTimingDeviationForTAext { ID id-Multiple-PLMN-List CRITICALITY ignore EXTENSION Multiple-PLMN-List { ID id-HSDSCH-RNTI CRITICALITY ignore EXTENSION HSDSCH-RNTI { ID id-E-RNTI CRITICALITY ignore EXTENSION E-RNTI { ID id-CellPortionLCRID CRITICALITY ignore EXTENSION CellPortionLCRID { ID id-CellCapabilityContainerExtension-TDD-LCR CRITICALITY ignore EXTENSION CellCapabilityContainerExtension-TDD-LCR { ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION Extended-RNTI ... }

PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional optional optional optional optional optional optional optional }| }| }| }| }| }| }| },

3GPP

Release 11
-- ************************************************************** --- DOWNLINK SIGNALLING TRANSFER REQUEST --- **************************************************************

858

3GPP TS 25.423 V11.2.0 (2012-06)

DownlinkSignallingTransferRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DownlinkSignallingTransferRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{DownlinkSignallingTransferRequest-Extensions}} ... } DownlinkSignallingTransferRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-C-ID CRITICALITY ignore TYPE -- May be a GERAN cell identifier { ID id-D-RNTI CRITICALITY ignore TYPE { ID id-L3-Information CRITICALITY ignore TYPE { ID id-D-RNTI-ReleaseIndication CRITICALITY ignore TYPE ... } C-ID D-RNTI L3-Information D-RNTI-ReleaseIndication PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE mandatory },

OPTIONAL,

DownlinkSignallingTransferRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-URA-ID CRITICALITY ignore EXTENSION URA-ID { ID id-MBMS-Bearer-Service-List CRITICALITY ignore EXTENSION MBMS-Bearer-Service-List { ID id-Old-URA-ID CRITICALITY ignore EXTENSION URA-ID { ID id-SRNC-ID CRITICALITY ignore EXTENSION RNC-ID -- This IE shall be present if the URA-ID IE or Old URA-ID IE is present. { ID id-Extended-SRNC-ID CRITICALITY reject EXTENSION Extended-RNC-ID { ID id-Enhanced-PCH-Capability CRITICALITY ignore EXTENSION Enhanced-PCH-Capability -- FDD and 1.28Mcps TDD only ... } -- ************************************************************** --- RELOCATION COMMIT --- ************************************************************** RelocationCommit ::= SEQUENCE { protocolIEs protocolExtensions ... } ProtocolIE-Container {{RelocationCommit-IEs}}, ProtocolExtensionContainer {{RelocationCommit-Extensions}}

PRESENCE PRESENCE PRESENCE PRESENCE

optional}| optional}| optional}| conditional}|

PRESENCE optional}| PRESENCE optional},

OPTIONAL,

RelocationCommit-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY ignore TYPE D-RNTI PRESENCE optional { ID id-RANAP-RelocationInformation CRITICALITY ignore TYPE RANAP-RelocationInformation ...

} | PRESENCE optional

},

3GPP

Release 11
} RelocationCommit-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- PAGING REQUEST --- ************************************************************** PagingRequest ::= SEQUENCE { protocolIEs protocolExtensions ... }

859

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolIE-Container {{PagingRequest-IEs}}, ProtocolExtensionContainer {{PagingRequest-Extensions}}

OPTIONAL,

PagingRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-PagingArea-PagingRqst { ID id-SRNC-ID { ID id-S-RNTI { ID id-IMSI { ID id-DRXCycleLengthCoefficient { ID id-CNOriginatedPage-PagingRqst ... }

CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY

ignore ignore ignore ignore ignore ignore

TYPE TYPE TYPE TYPE TYPE TYPE

PagingArea-PagingRqst RNC-ID S-RNTI IMSI DRXCycleLengthCoefficient CNOriginatedPage-PagingRqst

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

mandatory mandatory mandatory mandatory mandatory optional

} | } | -- May be a BSC-Id. } | } | }| },

PagingArea-PagingRqst ::= CHOICE { uRA URA-PagingRqst, -- May be a GRA-ID. cell Cell-PagingRqst, -- UTRAN only ... } URA-PagingRqst ::= SEQUENCE { uRA-ID iE-Extensions ... } URA-ID, ProtocolExtensionContainer { { URAItem-PagingRqst-ExtIEs} } OPTIONAL,

URAItem-PagingRqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Cell-PagingRqst ::= SEQUENCE { c-ID iE-Extensions ... } C-ID, ProtocolExtensionContainer { { CellItem-PagingRqst-ExtIEs} } OPTIONAL,

CellItem-PagingRqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

860

3GPP TS 25.423 V11.2.0 (2012-06)

CNOriginatedPage-PagingRqst::= SEQUENCE { pagingCause PagingCause, cNDomainType CNDomainType, pagingRecordType PagingRecordType, iE-Extensions ProtocolExtensionContainer { { CNOriginatedPage-PagingRqst-ExtIEs} } OPTIONAL, ... } CNOriginatedPage-PagingRqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PagingRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-SRNC-ID CRITICALITY reject { ID id-Enhanced-PCH-Capability CRITICALITY ignore -- FDD and 1.28Mcps TDD only { ID id-Extended-S-RNTI CRITICALITY ignore ... } EXTENSION Extended-RNC-ID EXTENSION Enhanced-PCH-Capability EXTENSION Extended-RNTI PRESENCE optional}| PRESENCE optional}| PRESENCE optional},

-- ************************************************************** --- DEDICATED MEASUREMENT INITIATION REQUEST --- ************************************************************** DedicatedMeasurementInitiationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementInitiationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementInitiationRequest-Extensions}} ... } DedicatedMeasurementInitiationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY reject TYPE MeasurementID PRESENCE mandatory } | { ID id-DedicatedMeasurementObjectType-DM-Rqst CRITICALITY reject TYPE DedicatedMeasurementObjectType-DM-Rqst { ID { ID { ID { ID { ID ... id-DedicatedMeasurementType id-MeasurementFilterCoefficient id-ReportCharacteristics id-CFNReportingIndicator id-CFN CRITICALITY CRITICALITY CRITICALITY CRITICALITY CRITICALITY reject reject reject reject reject TYPE TYPE TYPE TYPE TYPE DedicatedMeasurementType MeasurementFilterCoefficient ReportCharacteristics FNReportingIndicator CFN PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

OPTIONAL,

PRESENCE mandatory } |

mandatory } | optional } | mandatory }| mandatory }| optional },

DedicatedMeasurementObjectType-DM-Rqst ::= CHOICE { rL RL-DM-Rqst, rLS RL-Set-DM-Rqst, allRL All-RL-DM-Rqst,

3GPP

Release 11
allRLS ... } RL-DM-Rqst ::= SEQUENCE { rL-InformationList-DM-Rqst iE-Extensions ... } All-RL-Set-DM-Rqst,

861

3GPP TS 25.423 V11.2.0 (2012-06)

RL-InformationList-DM-Rqst, ProtocolExtensionContainer { { RLItem-DM-Rqst-ExtIEs} } OPTIONAL,

RLItem-DM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-DM-Rqst ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-DM-Rqst-IEs} } TYPE RL-InformationItem-DM-Rqst PRESENCE mandatory }

RL-Information-DM-Rqst-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-DM-Rqst CRITICALITY reject }

RL-InformationItem-DM-Rqst ::= SEQUENCE { rL-ID RL-ID, dPCH-ID DPCH-ID OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationItem-DM-Rqst-ExtIEs} } OPTIONAL, ... } RL-InformationItem-DM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSSICH-Info-DM-Rqst CRITICALITY reject optional}| -- TDD only { ID id-DPCH-ID768-DM-Rqst CRITICALITY reject PRESENCE optional}| { ID id-HSSICH-Info-DM-Rqst-Extension CRITICALITY reject optional}, -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... } HSSICH-Info-DM-Rqst ::= SEQUENCE (SIZE (1..maxNrOfHSSICHs)) OF HS-SICH-ID HSSICH-Info-DM-Rqst-Extension ::= SEQUENCE (SIZE (1..maxNrOfHSSICHs)) OF HS-SICH-ID-Extension RL-Set-DM-Rqst ::= SEQUENCE { rL-Set-InformationList-DM-Rqst iE-Extensions ... } RL-Set-InformationList-DM-Rqst, ProtocolExtensionContainer { { RL-SetItem-DM-Rqst-ExtIEs} } OPTIONAL, EXTENSION HSSICH-Info-DM-Rqst EXTENSION DPCH-ID768 EXTENSION HSSICH-Info-DM-Rqst-Extension PRESENCE PRESENCE

RL-SetItem-DM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
} RL-Set-InformationList-DM-Rqst IEs} }

862

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-Information-DM-Rqst-

RL-Set-Information-DM-Rqst-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-InformationItem-DM-Rqst CRITICALITY reject }

TYPE RL-Set-InformationItem-DM-Rqst

PRESENCE mandatory

RL-Set-InformationItem-DM-Rqst ::= SEQUENCE { rL-Set-ID RL-Set-ID, iE-Extensions ProtocolExtensionContainer { {RL-Set-InformationItem-DM-Rqst-ExtIEs} } OPTIONAL, ... } RL-Set-InformationItem-DM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } All-RL-DM-Rqst ::= NULL All-RL-Set-DM-Rqst ::= NULL DedicatedMeasurementInitiationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-PartialReportingIndicator CRITICALITY ignore EXTENSION optional }| { ID id-MeasurementRecoveryBehavior CRITICALITY ignore EXTENSION optional }| { ID id-AlternativeFormatReportingIndicator CRITICALITY ignore EXTENSION ... } -- ************************************************************** --- DEDICATED MEASUREMENT INITIATION RESPONSE --- ************************************************************** DedicatedMeasurementInitiationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementInitiationResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementInitiationResponse-Extensions}} ... } DedicatedMeasurementInitiationResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore PRESENCE mandatory } | { ID id-DedicatedMeasurementObjectType-DM-Rsp CRITICALITY ignore { ID id-CriticalityDiagnostics CRITICALITY ignore PRESENCE optional }, ... TYPE MeasurementID TYPE DedicatedMeasurementObjectType-DM-Rsp TYPE CriticalityDiagnostics PRESENCE optional } | PartialReportingIndicator MeasurementRecoveryBehavior PRESENCE PRESENCE

AlternativeFormatReportingIndicator PRESENCE optional },

OPTIONAL,

3GPP

Release 11
} DedicatedMeasurementObjectType-DM-Rsp ::= CHOICE { rLs RL-DM-Rsp, rLS RL-Set-DM-Rsp, allRL RL-DM-Rsp, allRLS RL-Set-DM-Rsp, ... } RL-DM-Rsp ::= SEQUENCE { rL-InformationList-DM-Rsp iE-Extensions ... }

863

3GPP TS 25.423 V11.2.0 (2012-06)

RL-InformationList-DM-Rsp, ProtocolExtensionContainer { { RLItem-DM-Rsp-ExtIEs} } OPTIONAL,

RLItem-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-DM-Rsp ::= SEQUENCE { rL-Set-InformationList-DM-Rsp iE-Extensions ... } RL-Set-InformationList-DM-Rsp, ProtocolExtensionContainer { { RL-SetItem-DM-Rsp-ExtIEs} } OPTIONAL,

RL-SetItem-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-DM-Rsp ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-DM-Rsp-IEs} } TYPE RL-InformationItem-DM-Rsp PRESENCE mandatory }

RL-Information-DM-Rsp-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-DM-Rsp CRITICALITY ignore }

RL-InformationItem-DM-Rsp ::= SEQUENCE { rL-ID RL-ID, dPCH-ID DPCH-ID OPTIONAL, dedicatedMeasurementValue DedicatedMeasurementValue, cFN CFN OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-InformationItem-DM-Rsp-ExtIEs} } OPTIONAL, ... } RL-InformationItem-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-HSSICH-Info-DM CRITICALITY reject EXTENSION HS-SICH-ID -- TDD only { ID id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp CRITICALITY ignore PRESENCE optional }| PRESENCE optional}| EXTENSION Multiple-DedicatedMeasurementValueList-TDD-DM-Rsp

3GPP

Release 11

864

3GPP TS 25.423 V11.2.0 (2012-06)

-- Applicable to 3.84Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported. { ID id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp CRITICALITY ignore EXTENSION Multiple-DedicatedMeasurementValueList-LCR-TDDDM-Rsp PRESENCE optional }| -- Applicable to 1.28Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported. { ID id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp CRITICALITY ignore EXTENSION Multiple-HSSICHMeasurementValueList-TDD-DM-Rsp PRESENCE optional }| -- TDD only. This list of HS-SICH measurement values is used for the 2nd and beyond measurements of a RL when multiple HS-SICH measurement values need to be reported. { ID id-multiple-DedicatedMeasurementValueList-TDD768-DM-Rsp CRITICALITY ignore EXTENSION Multiple-DedicatedMeasurementValueList-TDD768-DMRsp PRESENCE optional }| -- Applicable to 7.68Mcps TDD only. This list of dedicated measurement values is used for the 2nd and beyond measurements of a RL when multiple dedicated measurement values need to be reported. { ID id-DPCH-ID768-DM-Rsp CRITICALITY ignore EXTENSION DPCH-ID768 PRESENCE optional}| { ID id-HS-SICH-ID-Extension CRITICALITY ignore EXTENSION HS-SICH-ID-Extension PRESENCE optional}, -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... } RL-Set-InformationList-DM-Rsp ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-Information-DM-Rsp-IEs} } TYPE RL-Set-InformationItem-DM-Rsp PRESENCE mandatory }

RL-Set-Information-DM-Rsp-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-InformationItem-DM-Rsp CRITICALITY ignore }

RL-Set-InformationItem-DM-Rsp ::= SEQUENCE { rL-Set-ID RL-Set-ID, dedicatedMeasurementValue DedicatedMeasurementValue, cFN CFN OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Set-InformationItem-DM-Rspns-ExtIEs} } ... } RL-Set-InformationItem-DM-Rspns-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DedicatedMeasurementInitiationResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MeasurementRecoverySupportIndicator CRITICALITY ignore EXTENSION optional }, ... }

OPTIONAL,

MeasurementRecoverySupportIndicator

PRESENCE

Multiple-DedicatedMeasurementValueList-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHsPerRL-1)) OF Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp ::= SEQUENCE { dPCH-ID DPCH-ID,

3GPP

Release 11
dedicatedMeasurementValue iE-Extensions ... }

865

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

DedicatedMeasurementValue, ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp-ExtIEs} }

Multiple-DedicatedMeasurementValueItem-TDD-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHsLCRPerRL-1)) OF Multiple-DedicatedMeasurementValueItem-LCRTDD-DM-Rsp Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp ::= SEQUENCE { dPCH-ID DPCH-ID, dedicatedMeasurementValue DedicatedMeasurementValue, iE-Extensions ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp-ExtIEs} } ... } Multiple-DedicatedMeasurementValueItem-LCR-TDD-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Multiple-HSSICHMeasurementValueList-TDD-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfHSSICHs-1)) OF Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp ::= SEQUENCE { hsSICH-ID HS-SICH-ID, dedicatedMeasurementValue DedicatedMeasurementValue, iE-Extensions ProtocolExtensionContainer { { Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp-ExtIEs} } ... } Multiple-HSSICHMeasurementValueItem-TDD-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-SICH-ID-Extension CRITICALITY ignore EXTENSION HS-SICH-ID-Extension -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... }

OPTIONAL,

OPTIONAL,

PRESENCE optional},

Multiple-DedicatedMeasurementValueList-TDD768-DM-Rsp ::= SEQUENCE (SIZE (1.. maxNrOfDPCHs768PerRL-1)) OF Multiple-DedicatedMeasurementValueItem-TDD768DM-Rsp Multiple-DedicatedMeasurementValueItem-TDD768-DM-Rsp ::= SEQUENCE { dPCH-ID768 DPCH-ID768, dedicatedMeasurementValue DedicatedMeasurementValue, iE-Extensions ProtocolExtensionContainer { { Multiple-DedicatedMeasurementValueItem-TDD768-DM-Rsp-ExtIEs} } ... }

OPTIONAL,

3GPP

Release 11

866

3GPP TS 25.423 V11.2.0 (2012-06)

Multiple-DedicatedMeasurementValueItem-TDD768-DM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- DEDICATED MEASUREMENT INITIATION FAILURE --- ************************************************************** DedicatedMeasurementInitiationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementInitiationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementInitiationFailure-Extensions}} ... } DedicatedMeasurementInitiationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID PRESENCE mandatory } | { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional ... } DedicatedMeasurementInitiationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DedicatedMeasurementObjectType-DM-Fail CRITICALITY ignore EXTENSION DedicatedMeasurementObjectType-DM-Fail }, ... } DedicatedMeasurementObjectType-DM-Fail ::= CHOICE { rL RL-DM-Fail, rLS RL-Set-DM-Fail, allRL RL-DM-Fail, allRLS RL-Set-DM-Fail, ... } RL-DM-Fail ::= SEQUENCE { rL-unsuccessful-InformationRespList-DM-Fail RL-Unsuccessful-InformationRespList-DM-Fail, rL-successful-InformationRespList-DM-Fail RL-Successful-InformationRespList-DM-Fail iE-Extensions ProtocolExtensionContainer { { RLItem-DM-Fail-ExtIEs} } OPTIONAL, ... } RLItem-DM-Fail-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-DM-Fail ::= SEQUENCE { rL-Set-unsuccessful-InformationRespList-DM-Fail RL-Set-Unsuccessful-InformationRespList-DM-Fail, rL-Set-successful-InformationRespList-DM-Fail RL-Set-Successful-InformationRespList-DM-Fail

OPTIONAL,

},

PRESENCE optional

OPTIONAL,

OPTIONAL,

3GPP

Release 11
iE-Extensions ... } RL-SetItem-DM-Fail-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Unsuccessful-InformationRespList-DM-Fail InformationResp-DM-Fail-IEs} }

867
ProtocolExtensionContainer { { RL-SetItem-DM-Fail-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Unsuccessful-

RL-Unsuccessful-InformationResp-DM-Fail-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Unsuccessful-InformationItem-DM-Fail CRITICALITY ignore mandatory } }

TYPE RL-Unsuccessful-InformationItem-DM-Fail

PRESENCE

RL-Unsuccessful-InformationItem-DM-Fail ::= SEQUENCE { rL-ID RL-ID, individualcause Cause OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Unsuccessful-InformationItem-DM-Fail-ExtIEs} } OPTIONAL, ... } RL-Unsuccessful-InformationItem-DM-Fail-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Successful-InformationRespList-DM-Fail InformationResp-DM-Fail-IEs} } ::= SEQUENCE (SIZE (1..maxNrOfRLs-1)) OF ProtocolIE-Single-Container { {RL-Successful-

RL-Successful-InformationResp-DM-Fail-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Successful-InformationItem-DM-Fail CRITICALITY ignore }

TYPE RL-Successful-InformationItem-DM-Fail

PRESENCE mandatory

RL-Successful-InformationItem-DM-Fail ::= SEQUENCE { rL-ID RL-ID, dPCH-ID DPCH-ID OPTIONAL, dedicatedMeasurementValue DedicatedMeasurementValue, cFN CFN OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Successful-InformationItem-DM-Fail-ExtIEs} } OPTIONAL, ... } RL-Successful-InformationItem-DM-Fail-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-HSSICH-Info-DM CRITICALITY reject EXTENSION HS-SICH-ID -- TDD only { ID id-HS-SICH-ID-Extension CRITICALITY ignore EXTENSION HS-SICH-ID-Extension -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... } PRESENCE optional}| PRESENCE optional},

3GPP

Release 11
RL-Set-Unsuccessful-InformationRespList-DM-Fail Unsuccessful-InformationResp-DM-Fail-IEs} }

868

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-

RL-Set-Unsuccessful-InformationResp-DM-Fail-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-Unsuccessful-InformationItem-DM-Fail CRITICALITY ignore mandatory } }

TYPE RL-Set-Unsuccessful-InformationItem-DM-Fail

PRESENCE

RL-Set-Unsuccessful-InformationItem-DM-Fail ::= SEQUENCE { rL-Set-ID RL-Set-ID, individualcause Cause OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Set-Unsuccessful-InformationItem-DM-Failns-ExtIEs} } OPTIONAL, ... } RL-Set-Unsuccessful-InformationItem-DM-Failns-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-Successful-InformationRespList-DM-Fail Successful-InformationResp-DM-Fail-IEs} } ::= SEQUENCE (SIZE (1..maxNrOfRLSets-1)) OF ProtocolIE-Single-Container { {RL-Set-

RL-Set-Successful-InformationResp-DM-Fail-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-Successful-InformationItem-DM-Fail CRITICALITY ignore mandatory } }

TYPE RL-Set-Successful-InformationItem-DM-Fail

PRESENCE

RL-Set-Successful-InformationItem-DM-Fail ::= SEQUENCE { rL-Set-ID RL-Set-ID, dedicatedMeasurementValue DedicatedMeasurementValue, cFN CFN OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Set-Successful-InformationItem-DM-Failns-ExtIEs} } OPTIONAL, ... } RL-Set-Successful-InformationItem-DM-Failns-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- DEDICATED MEASUREMENT REPORT --- ************************************************************** DedicatedMeasurementReport ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementReport-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementReport-Extensions}} ... }

OPTIONAL,

3GPP

Release 11

869

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory },

DedicatedMeasurementReport-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID PRESENCE mandatory } | { ID id-DedicatedMeasurementObjectType-DM-Rprt CRITICALITY ignore TYPE DedicatedMeasurementObjectType-DM-Rprt ... } DedicatedMeasurementObjectType-DM-Rprt ::= CHOICE { rLs RL-DM-Rprt, rLS RL-Set-DM-Rprt, allRL RL-DM-Rprt, allRLS RL-Set-DM-Rprt, ... } RL-DM-Rprt ::= SEQUENCE { rL-InformationList-DM-Rprt iE-Extensions ... } RL-InformationList-DM-Rprt, ProtocolExtensionContainer { { RLItem-DM-Rprt-ExtIEs} } OPTIONAL,

RLItem-DM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-DM-Rprt ::= SEQUENCE { rL-Set-InformationList-DM-Rprt iE-Extensions ... } RL-Set-InformationList-DM-Rprt, ProtocolExtensionContainer { { RL-SetItem-DM-Rprt-ExtIEs} } OPTIONAL,

RL-SetItem-DM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-InformationList-DM-Rprt ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Information-DM-Rprt-IEs} } TYPE RL-InformationItem-DM-Rprt PRESENCE mandatory }

RL-Information-DM-Rprt-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-InformationItem-DM-Rprt CRITICALITY ignore }

RL-InformationItem-DM-Rprt ::= SEQUENCE { rL-ID RL-ID, dPCH-ID DPCH-ID OPTIONAL, dedicatedMeasurementValueInformation DedicatedMeasurementValueInformation, iE-Extensions ProtocolExtensionContainer { {RL-InformationItem-DM-Rprt-ExtIEs} } OPTIONAL, ... } RL-InformationItem-DM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-HSSICH-Info-DM-Rprt CRITICALITY ignore -- TDD only EXTENSION HS-SICH-ID PRESENCE optional}|

3GPP

Release 11

870

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional}| PRESENCE

{ ID id-DPCH-ID768-DM-Rprt CRITICALITY ignore EXTENSION DPCH-ID768 { ID id-HS-SICH-ID-Extension CRITICALITY ignore EXTENSION HS-SICH-ID-Extension optional}, -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... } RL-Set-InformationList-DM-Rprt IEs} }

::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-Information-DM-Rprt-

RL-Set-Information-DM-Rprt-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-InformationItem-DM-Rprt CRITICALITY ignore }

TYPE RL-Set-InformationItem-DM-Rprt

PRESENCE mandatory

RL-Set-InformationItem-DM-Rprt ::= SEQUENCE { rL-Set-ID RL-Set-ID, dedicatedMeasurementValueInformation DedicatedMeasurementValueInformation, iE-Extensions ProtocolExtensionContainer { {RL-Set-InformationItem-DM-Rprt-ExtIEs} } OPTIONAL, ... } RL-Set-InformationItem-DM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DedicatedMeasurementReport-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MeasurementRecoveryReportingIndicator CRITICALITY ignore optional }, ... } -- ************************************************************** --- DEDICATED MEASUREMENT TERMINATION REQUEST --- ************************************************************** DedicatedMeasurementTerminationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementTerminationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementTerminationRequest-Extensions}} ... } DedicatedMeasurementTerminationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID ... } DedicatedMeasurementTerminationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } PRESENCE mandatory }, EXTENSION MeasurementRecoveryReportingIndicator PRESENCE

OPTIONAL,

3GPP

Release 11
-- ************************************************************** --- DEDICATED MEASUREMENT FAILURE INDICATION --- **************************************************************

871

3GPP TS 25.423 V11.2.0 (2012-06)

DedicatedMeasurementFailureIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{DedicatedMeasurementFailureIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{DedicatedMeasurementFailureIndication-Extensions}} ... } DedicatedMeasurementFailureIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID { ID id-Cause CRITICALITY ignore TYPE Cause ... } PRESENCE mandatory PRESENCE mandatory }, } |

OPTIONAL,

DedicatedMeasurementFailureIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DedicatedMeasurementObjectType-DM-Fail-Ind CRITICALITY ignore EXTENSION DedicatedMeasurementObjectType-DM-Fail-Ind optional }, ... } DedicatedMeasurementObjectType-DM-Fail-Ind ::= CHOICE { rL RL-DM-Fail-Ind, rLS RL-Set-DM-Fail-Ind, allRL RL-DM-Fail-Ind, allRLS RL-Set-DM-Fail-Ind, ... } RL-DM-Fail-Ind ::= SEQUENCE { rL-unsuccessful-InformationRespList-DM-Fail-Ind iE-Extensions ... } RL-Unsuccessful-InformationRespList-DM-Fail-Ind, ProtocolExtensionContainer { { RLItem-DM-Fail-Ind-ExtIEs} } OPTIONAL,

PRESENCE

RLItem-DM-Fail-Ind-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-DM-Fail-Ind ::= SEQUENCE { rL-Set-unsuccessful-InformationRespList-DM-Fail-Ind iE-Extensions ... } RL-Set-Unsuccessful-InformationRespList-DM-Fail-Ind, ProtocolExtensionContainer { { RL-SetItem-DM-Fail-Ind-ExtIEs} } OPTIONAL,

RL-SetItem-DM-Fail-Ind-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
} RL-Unsuccessful-InformationRespList-DM-Fail-Ind InformationResp-DM-Fail-Ind-IEs} }

872

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { {RL-Unsuccessful-

RL-Unsuccessful-InformationResp-DM-Fail-Ind-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Unsuccessful-InformationItem-DM-Fail-Ind CRITICALITY ignore mandatory } }

TYPE RL-Unsuccessful-InformationItem-DM-Fail-Ind

PRESENCE

RL-Unsuccessful-InformationItem-DM-Fail-Ind ::= SEQUENCE { rL-ID RL-ID, individualcause Cause OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Unsuccessful-InformationItem-DM-Fail-Ind-ExtIEs} } OPTIONAL, ... } RL-Unsuccessful-InformationItem-DM-Fail-Ind-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Set-Unsuccessful-InformationRespList-DM-Fail-Ind Unsuccessful-InformationResp-DM-Fail-Ind-IEs} } ::= SEQUENCE (SIZE (1..maxNrOfRLSets)) OF ProtocolIE-Single-Container { {RL-Set-

RL-Set-Unsuccessful-InformationResp-DM-Fail-Ind-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-Set-Unsuccessful-InformationItem-DM-Fail-Ind CRITICALITY ignore PRESENCE mandatory } }

TYPE RL-Set-Unsuccessful-InformationItem-DM-Fail-Ind

RL-Set-Unsuccessful-InformationItem-DM-Fail-Ind ::= SEQUENCE { rL-Set-ID RL-Set-ID, individualcause Cause OPTIONAL, iE-Extensions ProtocolExtensionContainer { {RL-Set-Unsuccessful-InformationItem-DM-Fail-Indns-ExtIEs} } OPTIONAL, ... } RL-Set-Unsuccessful-InformationItem-DM-Fail-Indns-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON TRANSPORT CHANNEL RESOURCES RELEASE REQUEST --- ************************************************************** CommonTransportChannelResourcesReleaseRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonTransportChannelResourcesReleaseRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelResourcesReleaseRequest-Extensions}} ... }

OPTIONAL,

3GPP

Release 11
CommonTransportChannelResourcesReleaseRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY ignore TYPE D-RNTI ... }

873
PRESENCE mandatory },

3GPP TS 25.423 V11.2.0 (2012-06)

CommonTransportChannelResourcesReleaseRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON TRANSPORT CHANNEL RESOURCES REQUEST --- ************************************************************** CommonTransportChannelResourcesRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonTransportChannelResourcesRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelResourcesRequest-Extensions}} ... } CommonTransportChannelResourcesRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY reject { ID id-C-ID CRITICALITY reject { ID id-TransportBearerRequestIndicator CRITICALITY reject { ID id-TransportBearerID CRITICALITY reject ... } TYPE TYPE TYPE TYPE D-RNTI C-ID TransportBearerRequestIndicator TransportBearerID PRESENCE PRESENCE PRESENCE PRESENCE

OPTIONAL,

mandatory } | optional } | mandatory } | mandatory },

CommonTransportChannelResourcesRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Permanent-NAS-UE-Identity CRITICALITY ignore EXTENSION Permanent-NAS-UE-Identity { ID id-BindingID CRITICALITY ignore EXTENSION BindingID -- Shall be ignored if bearer establishment with ALCAP. { ID id-TransportLayerAddress CRITICALITY ignore EXTENSION TransportLayerAddress -- Shall be ignored if bearer establishment with ALCAP. { ID id-MBMS-Bearer-Service-List CRITICALITY notify EXTENSION MBMS-Bearer-Service-List { ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos { ID id-Enhanced-FACH-Support-Indicator CRITICALITY ignore EXTENSION Enhanced-FACH-Support-Indicator -- FDD and 1.28Mcps TDD only { ID id-Common-EDCH-Support-Indicator CRITICALITY ignore EXTENSION Common-EDCH-Support-Indicator -- FDD only { ID id-HSDSCH-Physical-Layer-Category CRITICALITY ignore EXTENSION HSDSCH-Physical-Layer-Category { ID id-UE-with-enhanced-HS-SCCH-support-indicator CRITICALITY ignore EXTENSION NULL ... } -- ************************************************************** --- COMMON TRANSPORT CHANNEL RESOURCES RESPONSE FDD --

PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional },

3GPP

Release 11
-- **************************************************************

874

3GPP TS 25.423 V11.2.0 (2012-06)

CommonTransportChannelResourcesResponseFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonTransportChannelResourcesResponseFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelResourcesResponseFDD-Extensions}} ... } CommonTransportChannelResourcesResponseFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-S-RNTI CRITICALITY ignore TYPE S-RNTI PRESENCE mandatory } | { ID id-C-RNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional } | { ID id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD CRITICALITY ignore TYPE FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD PRESENCE mandatory } | { ID id-TransportLayerAddress CRITICALITY ignore TYPE TransportLayerAddress PRESENCE optional } | { ID id-BindingID CRITICALITY ignore TYPE BindingID PRESENCE optional } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD ::= SEQUENCE { fACH-FlowControlInformation FACH-FlowControlInformation-CTCH-ResourceRspFDD, -- If the Enhanced FACH Information Response IE is included in the message, the FACH Flow Control Information IE shall be ignored. iE-Extensions ProtocolExtensionContainer { {FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD-ExtIEs} } OPTIONAL, ... } FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FACH-FlowControlInformation-CTCH-ResourceRspFDD ::= ProtocolIE-Single-Container {{ FACH-FlowControlInformationIEs-CTCH-ResourceRspFDD }} FACH-FlowControlInformationIEs-CTCH-ResourceRspFDD RNSAP-PROTOCOL-IES ::= { { ID id-FACH-FlowControlInformation CRITICALITY ignore TYPE FACH-FlowControlInformation PRESENCE mandatory } CommonTransportChannelResourcesResponseFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-C-ID CRITICALITY ignore EXTENSION { ID id-Active-MBMS-Bearer-ServiceFDD CRITICALITY ignore EXTENSION { ID id-Enhanced-FACH-Information-ResponseFDD CRITICALITY ignore EXTENSION { ID id-Common-EDCH-MAC-d-Flow-Specific-InformationFDD CRITICALITY ignore EXTENSION PRESENCE optional}| { ID id-E-RNTI CRITICALITY ignore EXTENSION { ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION ... } -- ************************************************************** --- COMMON TRANSPORT CHANNEL RESOURCES RESPONSE TDD -}

OPTIONAL,

C-ID PRESENCE mandatory}| Active-MBMS-Bearer-Service-ListFDD PRESENCE optional}| Enhanced-FACH-Information-ResponseFDD PRESENCE optional}| Common-EDCH-MAC-d-Flow-Specific-InformationFDD E-RNTI Extended-RNTI PRESENCE optional}| PRESENCE optional},

3GPP

Release 11
-- **************************************************************

875

3GPP TS 25.423 V11.2.0 (2012-06)

CommonTransportChannelResourcesResponseTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonTransportChannelResourcesResponseTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelResourcesResponseTDD-Extensions}} ... } CommonTransportChannelResourcesResponseTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-S-RNTI CRITICALITY ignore TYPE S-RNTI PRESENCE mandatory } | { ID id-C-RNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional } | { ID id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD CRITICALITY ignore TYPE FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD PRESENCE mandatory } | { ID id-TransportLayerAddress CRITICALITY ignore TYPE TransportLayerAddress PRESENCE optional } | { ID id-BindingID CRITICALITY ignore TYPE BindingID PRESENCE optional } | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD ::= SEQUENCE { fACH-FlowControlInformation FACH-FlowControlInformation-CTCH-ResourceRspTDD, iE-Extensions ProtocolExtensionContainer { {FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD-ExtIEs} } OPTIONAL, ... } FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FACH-FlowControlInformation-CTCH-ResourceRspTDD ::= ProtocolIE-Single-Container {{ FACH-FlowControlInformationIEs-CTCH-ResourceRspTDD }} FACH-FlowControlInformationIEs-CTCH-ResourceRspTDD RNSAP-PROTOCOL-IES ::= { { ID id-FACH-FlowControlInformation CRITICALITY ignore TYPE FACH-FlowControlInformation PRESENCE mandatory } CommonTransportChannelResourcesResponseTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-C-ID CRITICALITY ignore EXTENSION { ID id-Active-MBMS-Bearer-ServiceTDD CRITICALITY ignore EXTENSION { ID id-Enhanced-FACH-Information-ResponseLCR CRITICALITY ignore EXTENSION { ID id-Common-EDCH-MAC-d-Flow-Specific-InformationLCR CRITICALITY ignore EXTENSION optional}| { ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION ... } -- ************************************************************** --- COMMON TRANSPORT CHANNEL RESOURCES FAILURE --- ************************************************************** }

OPTIONAL,

C-ID PRESENCE mandatory}| Active-MBMS-Bearer-Service-ListTDD PRESENCE optional}| Enhanced-FACH-Information-ResponseLCR PRESENCE optional}| Common-EDCH-MAC-d-Flow-Specific-InformationLCR PRESENCE Extended-RNTI PRESENCE optional},

3GPP

Release 11

876

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

CommonTransportChannelResourcesFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonTransportChannelResourcesFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonTransportChannelResourcesFailure-Extensions}} ... } CommonTransportChannelResourcesFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-S-RNTI CRITICALITY ignore TYPE S-RNTI { ID id-Cause CRITICALITY ignore TYPE Cause { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics ... } CommonTransportChannelResourcesFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION Extended-RNTI ... } -- ************************************************************** --- COMPRESSED MODE COMMAND --- ************************************************************** CompressedModeCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CompressedModeCommand-IEs}}, protocolExtensions ProtocolExtensionContainer {{CompressedModeCommand-Extensions}} ... } CompressedModeCommand-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Active-Pattern-Sequence-Information ... } CRITICALITY ignore TYPE Active-Pattern-Sequence-Information PRESENCE mandatory } | PRESENCE mandatory } | PRESENCE optional },

PRESENCE optional},

OPTIONAL,

PRESENCE mandatory

},

CompressedModeCommand-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ERROR INDICATION --- ************************************************************** ErrorIndication ::= SEQUENCE { protocolIEs protocolExtensions ... } ProtocolIE-Container {{ErrorIndication-IEs}}, ProtocolExtensionContainer {{ErrorIndication-Extensions}}

OPTIONAL,

3GPP

Release 11

877

3GPP TS 25.423 V11.2.0 (2012-06)

},

ErrorIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional} | { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional ... } ErrorIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ID id-S-RNTI CRITICALITY ignore { ID id-D-RNTI CRITICALITY ignore { ID id-Extended-S-RNTI CRITICALITY ignore ... } { EXTENSION S-RNTI EXTENSION D-RNTI EXTENSION Extended-RNTI PRESENCE optional}| PRESENCE optional}| PRESENCE optional},

-- ************************************************************** --- COMMON MEASUREMENT INITIATION REQUEST --- ************************************************************** CommonMeasurementInitiationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementInitiationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementInitiationRequest-Extensions}} ... } CommonMeasurementInitiationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY reject TYPE MeasurementID mandatory }| { ID id-CommonMeasurementObjectType-CM-Rqst CRITICALITY reject TYPE CommonMeasurementObjectType-CM-Rqst { ID id-CommonMeasurementType CRITICALITY reject TYPE CommonMeasurementType mandatory }| { ID id-MeasurementFilterCoefficient CRITICALITY reject TYPE MeasurementFilterCoefficient optional }| -- UTRAN only { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics mandatory }| { ID id-SFNReportingIndicator CRITICALITY reject TYPE FNReportingIndicator mandatory } | { ID id-SFN CRITICALITY reject TYPE SFN optional }| -- UTRAN only { ID id-CommonMeasurementAccuracy CRITICALITY reject TYPE CommonMeasurementAccuracy optional }, -- UTRAN only ... } CommonMeasurementInitiationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MeasurementRecoveryBehavior CRITICALITY ignore EXTENSION MeasurementRecoveryBehavior }| -- UTRAN only

OPTIONAL,

PRESENCE PRESENCE mandatory }| PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

PRESENCE optional

3GPP

Release 11

878

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

{ ID id-GANSS-Time-ID CRITICALITY ignore EXTENSION GANSS-Time-ID PRESENCE optional}| { ID id-Extension-CommonMeasurementObjectType-CM-Rqst CRITICALITY ignore EXTENSION Extension-CommonMeasurementObjectType-CM-Rqst optional}, ... } CommonMeasurementObjectType-CM-Rqst ::= CHOICE { cell Cell-CM-Rqst, ..., additional-CommonMeasurementObjectType-CM-Rqst }

Additional-CommonMeasurementObjectType-CM-Rqst

Cell-CM-Rqst ::= SEQUENCE { uC-ID UC-ID, -- May be a GERAN cell identifier timeSlot TimeSlot OPTIONAL, --3.84Mcps TDD and 7.68Mcps TDD only timeSlotLCR TimeSlotLCR OPTIONAL, --1.28Mcps TDD only neighbouringCellMeasurementInformation NeighbouringCellMeasurementInfo OPTIONAL, -- UTRAN only iE-Extensions ProtocolExtensionContainer { { CellItem-CM-Rqst-ExtIEs} } OPTIONAL, ... } NeighbouringCellMeasurementInfo ::= SEQUENCE (SIZE (1..maxNrOfMeasNCell)) OF CHOICE { neighbouringFDDCellMeasurementInformation NeighbouringFDDCellMeasurementInformation, neighbouringTDDCellMeasurementInformation NeighbouringTDDCellMeasurementInformation, ..., extension-neighbouringCellMeasurementInformation Extension-neighbouringCellMeasurementInformation, extension-neighbouringCellMeasurementInformation768 Extension-neighbouringCellMeasurementInformation768 } Extension-neighbouringCellMeasurementInformation ::= ProtocolIE-Single-Container {{ Extension-neighbouringCellMeasurementInformationIE }} TYPE NeighbouringTDDCellMeasurementInformationLCR PRESENCE

Extension-neighbouringCellMeasurementInformationIE RNSAP-PROTOCOL-IES ::= { { ID id-neighbouringTDDCellMeasurementInformationLCR CRITICALITY reject mandatory }, ... }

Extension-neighbouringCellMeasurementInformation768 ::= ProtocolIE-Single-Container {{ Extension-neighbouringCellMeasurementInformation768IE }} Extension-neighbouringCellMeasurementInformation768IE RNSAP-PROTOCOL-IES ::= { { ID id-neighbouringTDDCellMeasurementInformation768 CRITICALITY reject mandatory }, ... } CellItem-CM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN TYPE NeighbouringTDDCellMeasurementInformation768 PRESENCE

PRESENCE optional }|

3GPP

Release 11
-- Applicable to 1.28Mcps TDD only { ID id-UPPCHPositionLCR -- Applicable to 1.28Mcps TDD only ... CRITICALITY reject

879
EXTENSION UPPCHPositionLCR PRESENCE optional},

3GPP TS 25.423 V11.2.0 (2012-06)

} Additional-CommonMeasurementObjectType-CM-Rqst ::= ProtocolIE-Single-Container {{ Additional-CommonMeasurementObjectType-CM-RqstIE }} Additional-CommonMeasurementObjectType-CM-RqstIE RNSAP-PROTOCOL-IES ::= { { ID id-GSM-Cell-CM-Rqst CRITICALITY ignore TYPE GSM-Cell-CM-Rqst ... } GSM-Cell-CM-Rqst ::= SEQUENCE { cGI CGI, iE-Extensions ProtocolExtensionContainer ... } PRESENCE mandatory },

{ { GSMCell-CM-Rqst-ExtIEs} }

OPTIONAL,

GSMCell-CM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Extension-CommonMeasurementObjectType-CM-Rqst ::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RqstIE }} Extension-CommonMeasurementObjectType-CM-RqstIE RNSAP-PROTOCOL-IES ::= { { ID id-GsmCellList-CM-Rqst CRITICALITY ignore TYPE GsmCellList-CM-Rqst ... } GsmCellList-CM-Rqst ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF GsmCellItem-CM-Rqst GsmCellItem-CM-Rqst ::= SEQUENCE { measurementID MeasurementID, gsmCell GSM-Cell-CM-Rqst, iE-Extensions ProtocolExtensionContainer ... } PRESENCE mandatory },

{ { GsmCellItem-CM-Rqst-ExtIEs} }

OPTIONAL,

GsmCellItem-CM-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON MEASUREMENT INITIATION RESPONSE --- ************************************************************** CommonMeasurementInitiationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementInitiationResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementInitiationResponse-Extensions}}

OPTIONAL,

3GPP

Release 11
} ...

880

3GPP TS 25.423 V11.2.0 (2012-06)

CommonMeasurementInitiationResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore { ID id-CommonMeasurementObjectType-CM-Rsp CRITICALITY ignore { ID id-SFN CRITICALITY ignore -- UTRAN only { ID id-CriticalityDiagnostics CRITICALITY ignore { ID id-CommonMeasurementAccuracy CRITICALITY reject -- UTRAN only ... }

TYPE MeasurementID TYPE CommonMeasurementObjectType-CM-Rsp TYPE SFN TYPE CriticalityDiagnostics TYPE CommonMeasurementAccuracy

PRESENCE mandatory }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional }| PRESENCE optional },

CommonMeasurementInitiationResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MeasurementRecoverySupportIndicator CRITICALITY ignore EXTENSION MeasurementRecoverySupportIndicator PRESENCE optional }| -- UTRAN only { ID id-Extension-CommonMeasurementObjectType-CM-Rsp CRITICALITY ignore EXTENSION Extension-CommonMeasurementObjectType-CM-Rsp PRESENCE optional}, ... } CommonMeasurementObjectType-CM-Rsp ::= CHOICE { cell Cell-CM-Rsp, ... } Cell-CM-Rsp ::= SEQUENCE { commonMeasurementValue iE-Extensions ... } CommonMeasurementValue, ProtocolExtensionContainer

{ { CellItem-CM-Rsp-ExtIEs} }

OPTIONAL,

CellItem-CM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Extension-CommonMeasurementObjectType-CM-Rsp ::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RspIE }} Extension-CommonMeasurementObjectType-CM-RspIE RNSAP-PROTOCOL-IES ::= { { ID id-GsmCellList-CM-Rsp CRITICALITY ignore TYPE GsmCellList-CM-Rsp PRESENCE mandatory }, ... } GsmCellList-CM-Rsp ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF GsmCellItem-CM-Rsp GsmCellItem-CM-Rsp ::= SEQUENCE { measurementID commonMeasurementValue iE-Extensions ... } MeasurementID, CommonMeasurementValue ProtocolExtensionContainer

OPTIONAL, { { GsmCellItem-CM-Rsp-ExtIEs} }

OPTIONAL,

3GPP

Release 11
GsmCellItem-CM-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON MEASUREMENT INITIATION FAILURE --- **************************************************************

881

3GPP TS 25.423 V11.2.0 (2012-06)

CommonMeasurementInitiationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementInitiationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementInitiationFailure-Extensions}} ... } CommonMeasurementInitiationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID { ID id-Cause CRITICALITY ignore TYPE Cause { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics ... } PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE optional },

OPTIONAL,

CommonMeasurementInitiationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extension-FailureMeasurementList CRITICALITY ignore EXTENSION Extension-FailureMeasurementList ... } Extension-FailureMeasurementList ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF Extension-FailureMeasurementItem Extension-FailureMeasurementItem ::= SEQUENCE { measurementID MeasurementID, cause Cause, iE-Extensions ProtocolExtensionContainer { { Extension-FailureMeasurementItem-ExtIEs} } ... } Extension-FailureMeasurementItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON MEASUREMENT REPORT --- ************************************************************** CommonMeasurementReport ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementReport-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementReport-Extensions}}

PRESENCE optional },

OPTIONAL,

OPTIONAL,

3GPP

Release 11
} ...

882

3GPP TS 25.423 V11.2.0 (2012-06)

CommonMeasurementReport-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore { ID id-CommonMeasurementObjectType-CM-Rprt CRITICALITY ignore { ID id-SFN CRITICALITY ignore -- UTRAN only ... }

TYPE MeasurementID TYPE CommonMeasurementObjectType-CM-Rprt TYPE SFN

PRESENCE mandatory }| PRESENCE mandatory }| PRESENCE optional },

CommonMeasurementReport-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MeasurementRecoveryReportingIndicator CRITICALITY ignore EXTENSION MeasurementRecoveryReportingIndicator PRESENCE optional }| -- UTRAN only { ID id-Extension-CommonMeasurementObjectType-CM-Rprt CRITICALITY ignore EXTENSION Extension-CommonMeasurementObjectType-CM-Rprt PRESENCE optional }, ... } CommonMeasurementObjectType-CM-Rprt ::= CHOICE { cell Cell-CM-Rprt, ... } Cell-CM-Rprt ::= SEQUENCE { commonMeasurementValueInformation CommonMeasurementValueInformation, iE-Extensions ProtocolExtensionContainer {{ CellItem-CM-Rprt-ExtIEs }} ... } CellItem-CM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Extension-CommonMeasurementObjectType-CM-Rprt ::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementObjectType-CM-RprtIE }} Extension-CommonMeasurementObjectType-CM-RprtIE RNSAP-PROTOCOL-IES ::= { { ID id-GsmCellList-CM-Rprt CRITICALITY ignore TYPE GsmCellList-CM-Rprt ... } GsmCellList-CM-Rprt ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF GsmCellItem-CM-Rprt GsmCellItem-CM-Rprt ::= SEQUENCE { measurementID commonMeasurementValueInformation iE-Extensions ... } MeasurementID, CommonMeasurementValueInformation, ProtocolExtensionContainer { { GsmCellItem-CM-Rprt-ExtIEs} } PRESENCE mandatory },

OPTIONAL,

OPTIONAL,

GsmCellItem-CM-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

883

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- COMMON MEASUREMENT TERMINATION REQUEST --- ************************************************************** CommonMeasurementTerminationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementTerminationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementTerminationRequest-Extensions}} ... } CommonMeasurementTerminationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore ... } TYPE MeasurementID

OPTIONAL,

PRESENCE

mandatory},

CommonMeasurementTerminationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extension-TerminationMeasurementList CRITICALITY ignore EXTENSION Extension-TerminationMeasurementList ... } Extension-TerminationMeasurementList ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF Extension-TerminationMeasurementItem Extension-TerminationMeasurementItem ::= SEQUENCE { measurementID MeasurementID, iE-Extensions ProtocolExtensionContainer ... }

PRESENCE optional },

{ { Extension-TerminationMeasurementItem-ExtIEs} }

OPTIONAL,

Extension-TerminationMeasurementItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- COMMON MEASUREMENT FAILURE INDICATION --- ************************************************************** CommonMeasurementFailureIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{CommonMeasurementFailureIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{CommonMeasurementFailureIndication-Extensions}} ... } CommonMeasurementFailureIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID PRESENCE mandatory }|

OPTIONAL,

3GPP

Release 11
{ ID ... } id-Cause CRITICALITY ignore TYPE

884
Cause PRESENCE mandatory

3GPP TS 25.423 V11.2.0 (2012-06)

},

CommonMeasurementFailureIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extension-FailureIndicationMeasurementList CRITICALITY ignore EXTENSION Extension-FailureIndicationMeasurementList optional }, ... } Extension-FailureIndicationMeasurementList ::= SEQUENCE (SIZE (1..maxNoOfGsmCell)) OF Extension-FailureIndicationMeasurementItem Extension-FailureIndicationMeasurementItem ::= SEQUENCE { measurementID MeasurementID, cause Cause, iE-Extensions ProtocolExtensionContainer ... }

PRESENCE

{ { Extension-FailureIndicationMeasurementItem-ExtIEs} }

OPTIONAL,

Extension-FailureIndicationMeasurementItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- INFORMATION EXCHANGE INITIATION REQUEST --- ************************************************************** InformationExchangeInitiationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationExchangeInitiationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationRequest-Extensions}} ... } InformationExchangeInitiationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID CRITICALITY reject PRESENCE mandatory }| { ID id-InformationExchangeObjectType-InfEx-Rqst CRITICALITY reject mandatory }| { ID id-InformationType PRESENCE mandatory }| { ID id-InformationReportCharacteristics mandatory }, ... } InformationExchangeInitiationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } CRITICALITY reject CRITICALITY reject TYPE TYPE TYPE TYPE InformationExchangeID InformationExchangeObjectType-InfEx-Rqst InformationType InformationReportCharacteristics PRESENCE PRESENCE

OPTIONAL,

3GPP

Release 11
InformationExchangeObjectType-InfEx-Rqst ::= CHOICE { cell ..., extension-InformationExchangeObjectType-InfEx-Rqst } Cell-InfEx-Rqst ::= SEQUENCE { c-ID iE-Extensions ... }

885
Cell-InfEx-Rqst, Extension-InformationExchangeObjectType-InfEx-Rqst

3GPP TS 25.423 V11.2.0 (2012-06)

C-ID, --May be a GERAN cell identifier ProtocolExtensionContainer { { CellItem-InfEx-Rqst-ExtIEs} }

OPTIONAL,

CellItem-InfEx-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Extension-InformationExchangeObjectType-InfEx-Rqst ::= ProtocolIE-Single-Container {{ Extension-InformationExchangeObjectType-InfEx-RqstIE }} ::= { reject reject reject reject reject TYPE GSM-Cell-InfEx-Rqst PRESENCE mandatory}| TYPE MBMS-Bearer-Service-List PRESENCE mandatory}| TYPE MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rqst PRESENCE TYPE MBMS-Cell-InfEx-Rqst TYPE ANR-Cell-InfEx-Rqst PRESENCE mandatory}| PRESENCE mandatory}

Extension-InformationExchangeObjectType-InfEx-RqstIE RNSAP-PROTOCOL-IES { ID id-GSM-Cell-InfEx-Rqst CRITICALITY { ID id-MBMS-Bearer-Service-List CRITICALITY { ID id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rqst CRITICALITY mandatory}| { ID id-MBMS-Cell-InfEx-Rqst CRITICALITY { ID id-ANR-Cell-InfEx-Rqst CRITICALITY } GSM-Cell-InfEx-Rqst ::= SEQUENCE { cGI iE-Extensions ... } CGI, ProtocolExtensionContainer

{ { GSMCellItem-InfEx-Rqst-ExtIEs} }

OPTIONAL,

GSMCellItem-InfEx-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rqst ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rqst MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rqst ::= SEQUENCE { c-ID C-ID, mBMS-Bearer-Service-List-InfEx-Rqst MBMS-Bearer-Service-List-InfEx-Rqst, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rqst-ExtIEs} } ... } MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rqst-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

3GPP

Release 11
} ...

886

3GPP TS 25.423 V11.2.0 (2012-06)

MBMS-Bearer-Service-List-InfEx-Rqst ::= SEQUENCE (SIZE (1..maxNrOfMBMSServices)) OF TMGI MBMS-Cell-InfEx-Rqst ANR-Cell-InfEx-Rqst ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF C-ID ::= SEQUENCE (SIZE (1..maxNrOfANRCells)) OF C-ID

-- ************************************************************** --- INFORMATION EXCHANGE INITIATION RESPONSE --- ************************************************************** InformationExchangeInitiationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationExchangeInitiationResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationResponse-Extensions}} ... } InformationExchangeInitiationResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID CRITICALITY ignore mandatory }| { ID id-InformationExchangeObjectType-InfEx-Rsp CRITICALITY ignore optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore optional }, ... } TYPE TYPE TYPE InformationExchangeID InformationExchangeObjectType-InfEx-Rsp CriticalityDiagnostics

OPTIONAL,

PRESENCE PRESENCE PRESENCE

InformationExchangeInitiationResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } InformationExchangeObjectType-InfEx-Rsp ::= CHOICE { cell Cell-InfEx-Rsp, ..., extension-InformationExchangeObjectType-InfEx-Rsp } Cell-InfEx-Rsp ::= SEQUENCE { requestedDataValue iE-Extensions ... }

Extension-InformationExchangeObjectType-InfEx-Rsp

RequestedDataValue, ProtocolExtensionContainer

{ { CellItem-InfEx-Rsp-ExtIEs} }

OPTIONAL,

CellItem-InfEx-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
Extension-InformationExchangeObjectType-InfEx-Rsp

887

3GPP TS 25.423 V11.2.0 (2012-06)

::= ProtocolIE-Single-Container {{ Extension-InformationExchangeObjectType-InfEx-RspIE }} TYPE TYPE TYPE TYPE MBMS-Bearer-Service-List-InfEx-Rsp MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rsp MBMS-Cell-InfEx-Rsp ANR-Cell-InfEx-Rsp PRESENCE PRESENCE PRESENCE PRESENCE mandatory}| mandatory}| mandatory}| mandatory}

Extension-InformationExchangeObjectType-InfEx-RspIE RNSAP-PROTOCOL-IES ::= { { ID id-MBMS-Bearer-Service-List-InfEx-Rsp CRITICALITY ignore { ID id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rsp CRITICALITY ignore { ID id-MBMS-Cell-InfEx-Rsp CRITICALITY ignore { ID id-ANR-Cell-InfEx-Rsp CRITICALITY ignore } MBMS-Bearer-Service-List-InfEx-Rsp

::= SEQUENCE (SIZE (1..maxNrOfMBMSServices)) OF MBMS-Bearer-ServiceItemIEs-InfEx-Rsp

MBMS-Bearer-ServiceItemIEs-InfEx-Rsp ::=SEQUENCE{ tmgi TMGI, requestedDataValue RequestedDataValue, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-ServiceItem-InfEx-Rsp-ExtIEs} } OPTIONAL, ... } MBMS-Bearer-ServiceItem-InfEx-Rsp-ExtIEs ... } MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rsp RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rsp

MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rsp ::= SEQUENCE { c-ID C-ID, mBMS-Bearer-Service-List-InfEx-Rsp iE-Extensions ProtocolExtensionContainer ... }

MBMS-Bearer-Service-List-InfEx-Rsp, { { MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rsp-ExtIEs} }

OPTIONAL,

MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Cell-InfEx-Rsp ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-Cell-Item-InfEx-Rsp MBMS-Cell-Item-InfEx-Rsp c-ID requestedDataValue iE-Extensions ... } ::= SEQUENCE { C-ID, RequestedDataValue, ProtocolExtensionContainer

{ { MBMS-Cell-Item-InfEx-Rsp-ExtIEs} }

OPTIONAL,

MBMS-Cell-Item-InfEx-Rsp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
ANR-Cell-InfEx-Rsp

888
::= SEQUENCE (SIZE (1..maxNrOfANRCells)) OF ANR-Cell-ItemIEs-InfEx-Rsp ::=SEQUENCE{ C-ID, RequestedDataValue, ProtocolExtensionContainer { { ANR-Cell-ItemIEs-InfEx-Rsp-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

ANR-Cell-ItemIEs-InfEx-Rsp c-ID requestedDataValue iE-Extensions ... }

ANR-Cell-ItemIEs-InfEx-Rsp-ExtIEs ... }

RNSAP-PROTOCOL-EXTENSION ::= {

-- ************************************************************** --- INFORMATION EXCHANGE INITIATION FAILURE --- ************************************************************** InformationExchangeInitiationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationExchangeInitiationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationFailure-Extensions}} ... } InformationExchangeInitiationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID CRITICALITY mandatory }| { ID id-Cause CRITICALITY PRESENCE mandatory }| { ID id-CriticalityDiagnostics CRITICALITY optional }, ... } ignore ignore ignore TYPE TYPE TYPE InformationExchangeID Cause CriticalityDiagnostics PRESENCE

OPTIONAL,

PRESENCE

InformationExchangeInitiationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- INFORMATION REPORT --- ************************************************************** InformationReport ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationReport-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationReport-Extensions}} ... }

OPTIONAL,

3GPP

Release 11
InformationReport-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID PRESENCE mandatory }| { ID id-InformationExchangeObjectType-InfEx-Rprt PRESENCE mandatory }, ... } InformationReport-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } InformationExchangeObjectType-InfEx-Rprt ::= CHOICE { cell Cell-InfEx-Rprt, ..., extension-InformationExchangeObjectType-InfEx-Rprt } Extension-InformationExchangeObjectType-InfEx-Rprt

889
CRITICALITY ignore CRITICALITY ignore TYPE TYPE InformationExchangeID

3GPP TS 25.423 V11.2.0 (2012-06)

InformationExchangeObjectType-InfEx-Rprt

Extension-InformationExchangeObjectType-InfEx-Rprt

::= ProtocolIE-Single-Container {{ Extension-InformationExchangeObjectType-InfEx-RprtIE }} TYPE TYPE MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rprt MBMS-Cell-InfEx-Rprt

Extension-InformationExchangeObjectType-InfEx-RprtIE RNSAP-PROTOCOL-IES ::= { { ID id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rprt CRITICALITY ignore PRESENCE mandatory}| { ID id-MBMS-Cell-InfEx-Rprt CRITICALITY ignore PRESENCE mandatory} } Cell-InfEx-Rprt ::= SEQUENCE { requestedDataValueInformation iE-Extensions ... } CellItem-InfEx-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

RequestedDataValueInformation, ProtocolExtensionContainer {{ CellItem-InfEx-Rprt-ExtIEs }}

OPTIONAL,

MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rprt ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rprt MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rprt ::= SEQUENCE { c-ID C-ID, mBMS-Bearer-Service-List-InfEx-Rprt MBMS-Bearer-Service-List-InfEx-Rprt, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rprt-ExtIEs} } ... }

OPTIONAL,

3GPP

Release 11

890

3GPP TS 25.423 V11.2.0 (2012-06)

MBMS-Bearer-Service-in-MBMS-Cell-Item-InfEx-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-Service-List-InfEx-Rprt ::= SEQUENCE (SIZE (1..maxNrOfMBMSServices)) OF MBMS-Bearer-Service-List-Item-InfEx-Rprt MBMS-Bearer-Service-List-Item-InfEx-Rprt ::= SEQUENCE { tmgi TMGI, requestedDataValueInformation RequestedDataValueInformation, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-Service-List-Item-InfEx-Rprt-ExtIEs} } ... } MBMS-Bearer-Service-List-Item-InfEx-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Cell-InfEx-Rprt ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-Cell-Item-InfEx-Rprt

OPTIONAL,

MBMS-Cell-Item-InfEx-Rprt ::= SEQUENCE { c-ID C-ID, requestedDataValueInformation RequestedDataValueInformation, iE-Extensions ProtocolExtensionContainer { { MBMS-Cell-Item-InfEx-Rprt-ExtIEs} } ... } MBMS-Cell-Item-InfEx-Rprt-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- INFORMATION EXCHANGE TERMINATION REQUEST --- ************************************************************** InformationExchangeTerminationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationExchangeTerminationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationExchangeTerminationRequest-Extensions}} ... } InformationExchangeTerminationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID CRITICALITY ignore mandatory}, ... } InformationExchangeTerminationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... TYPE

OPTIONAL,

OPTIONAL,

InformationExchangeID

PRESENCE

3GPP

Release 11
} -- ************************************************************** --- INFORMATION EXCHANGE FAILURE INDICATION --- **************************************************************

891

3GPP TS 25.423 V11.2.0 (2012-06)

InformationExchangeFailureIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{InformationExchangeFailureIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{InformationExchangeFailureIndication-Extensions}} ... } InformationExchangeFailureIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-InformationExchangeID CRITICALITY ignore }| { ID id-Cause CRITICALITY ignore mandatory }, ... } TYPE TYPE InformationExchangeID Cause

OPTIONAL,

PRESENCE

mandatory

PRESENCE

InformationExchangeFailureIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RESET REQUEST --- ************************************************************** ResetRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{ResetRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{ResetRequest-Extensions}} ... } ResetRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RNC-ID CRITICALITY reject { ID id-ResetIndicator CRITICALITY reject ... }

OPTIONAL,

TYPE RNC-ID PRESENCE mandatory} | TYPE ResetIndicator PRESENCE

mandatory},

ResetRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-RNC-ID CRITICALITY reject ... } ResetIndicator ::= CHOICE {

EXTENSION Extended-RNC-ID

PRESENCE optional},

3GPP

Release 11
context all-contexts ..., contextGroup } ContextList-Reset ::= SEQUENCE { contextInfoList-Reset ContextInfoList-Reset, iE-Extensions ProtocolExtensionContainer ... } ContextItem-Reset-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContextList-Reset, NULL, ContextGroupList-Reset

892

3GPP TS 25.423 V11.2.0 (2012-06)

{ {ContextItem-Reset-ExtIEs} }

OPTIONAL,

ContextInfoList-Reset ::= SEQUENCE (SIZE (1.. maxResetContext)) OF ProtocolIE-Single-Container {{ ContextInfoItemIE-Reset }} ContextInfoItemIE-Reset RNSAP-PROTOCOL-IES ::= { {ID id-ContextInfoItem-Reset CRITICALITY reject } ContextInfoItem-Reset ::= SEQUENCE { contextType-Reset ContextType-Reset, iE-Extensions ProtocolExtensionContainer ... } ContextInfoItem-Reset-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContextType-Reset ::= CHOICE { sRNTI S-RNTI, dRNTI D-RNTI, ..., extension-ContextType-Reset Extension-ContextType-Reset } Extension-ContextType-Reset ::= ProtocolIE-Single-Container {{ Extension-ContextType-ResetIE }} Extension-ContextType-ResetIE RNSAP-PROTOCOL-IES ::= { { ID id-Extended-S-RNTI CRITICALITY reject TYPE Extended-RNTI ... } PRESENCE mandatory }, TYPE ContextInfoItem-Reset PRESENCE mandatory}

{ { ContextInfoItem-Reset-ExtIEs} }

OPTIONAL,

ContextGroupList-Reset ::= SEQUENCE { contextGroupInfoList-Reset ContextGroupInfoList-Reset, iE-Extensions ProtocolExtensionContainer { {ContextGroupItem-Reset-ExtIEs} } ... }

OPTIONAL,

3GPP

Release 11
ContextGroupItem-Reset-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContextGroupInfoList-Reset ::= SEQUENCE (SIZE (1.. maxResetContextGroup)) ContextGroupInfoItemIE-Reset RNSAP-PROTOCOL-IES ::= { {ID id-ContextGroupInfoItem-Reset CRITICALITY reject } ContextGroupInfoItem-Reset ::= SEQUENCE { s-RNTI-Group S-RNTI-Group, iE-Extensions ProtocolExtensionContainer ... }

893

3GPP TS 25.423 V11.2.0 (2012-06)

OF ProtocolIE-Single-Container {{ ContextGroupInfoItemIE-Reset }} PRESENCE mandatory}

TYPE ContextGroupInfoItem-Reset

{ { ContextGroupInfoItem-Reset-ExtIEs} }

OPTIONAL,

ContextGroupInfoItem-Reset-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-S-RNTI-Group CRITICALITY reject EXTENSION Extended-S-RNTI-Group ... } -- ************************************************************** --- RESET RESPONSE --- ************************************************************** ResetResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{ResetResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{ResetResponse-Extensions}} ... } ResetResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RNC-ID CRITICALITY ignore TYPE RNC-ID { ID id-CriticalityDiagnostics CRITICALITY ignore ... } ResetResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-RNC-ID CRITICALITY reject ... }

PRESENCE optional},

OPTIONAL,

PRESENCE mandatory} | TYPE CriticalityDiagnostics

PRESENCE

optional},

EXTENSION Extended-RNC-ID

PRESENCE optional},

-- ************************************************************** --- RADIO LINK ACTIVATION COMMAND FDD --- **************************************************************

3GPP

Release 11

894

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RadioLinkActivationCommandFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkActivationCommandFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkActivationCommandFDD-Extensions}} ... } RadioLinkActivationCommandFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DelayedActivationList-RL-ActivationCmdFDD PRESENCE mandatory }, ... } CRITICALITY ignore TYPE

DelayedActivationInformationList-RL-ActivationCmdFDD

RadioLinkActivationCommandFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } DelayedActivationInformationList-RL-ActivationCmdFDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { { DelayedActivationInformation-RL-ActivationCmdFDD-IEs} } DelayedActivationInformation-RL-ActivationCmdFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DelayedActivationInformation-RL-ActivationCmdFDD CRITICALITY ignore optional } } TYPE DelayedActivationInformation-RL-ActivationCmdFDD PRESENCE

DelayedActivationInformation-RL-ActivationCmdFDD ::= SEQUENCE { rL-ID RL-ID, delayed-activation-update DelayedActivationUpdate, iE-Extensions ProtocolExtensionContainer { { DelayedActivationInformation-RL-ActivationCmdFDD-ExtIEs} } OPTIONAL, ... } DelayedActivationInformation-RL-ActivationCmdFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- RADIO LINK ACTIVATION COMMAND TDD --- ************************************************************** RadioLinkActivationCommandTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkActivationCommandTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkActivationCommandTDD-Extensions}} ... } RadioLinkActivationCommandTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DelayedActivationList-RL-ActivationCmdTDD PRESENCE mandatory }, ... CRITICALITY ignore TYPE

OPTIONAL,

DelayedActivationInformationList-RL-ActivationCmdTDD

3GPP

Release 11
} RadioLinkActivationCommandTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... }

895

3GPP TS 25.423 V11.2.0 (2012-06)

DelayedActivationInformationList-RL-ActivationCmdTDD ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { { DelayedActivationInformation-RL-ActivationCmdTDD-IEs} } DelayedActivationInformation-RL-ActivationCmdTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-DelayedActivationInformation-RL-ActivationCmdTDD CRITICALITY ignore optional } } TYPE DelayedActivationInformation-RL-ActivationCmdTDD PRESENCE

DelayedActivationInformation-RL-ActivationCmdTDD ::= SEQUENCE { rL-ID RL-ID, delayed-activation-update DelayedActivationUpdate, iE-Extensions ProtocolExtensionContainer { { DelayedActivationInformation-RL-ActivationCmdTDD-ExtIEs} } OPTIONAL, ... } DelayedActivationInformation-RL-ActivationCmdTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- GERAN UPLINK SIGNALLING TRANSFER INDICATION --- ************************************************************** GERANUplinkSignallingTransferIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{GERANUplinkSignallingTransferIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{GERANUplinkSignallingTransferIndication-Extensions}} ... } GERANUplinkSignallingTransferIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UC-ID CRITICALITY ignore TYPE UC-ID -- UC-Id may be GERAN cell identifier. { ID id-SAI CRITICALITY ignore TYPE SAI { ID id-S-RNTI CRITICALITY ignore TYPE S-RNTI { ID id-D-RNTI CRITICALITY ignore TYPE D-RNTI { ID id-L3-Information CRITICALITY ignore TYPE L3-Information { ID id-CN-PS-DomainIdentifier CRITICALITY ignore TYPE CN-PS-DomainIdentifier { ID id-CN-CS-DomainIdentifier CRITICALITY ignore TYPE CN-CS-DomainIdentifier { ID id-URA-Information CRITICALITY ignore TYPE URA-Information -- URA information may be GRA information ... } PRESENCE mandatory PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE mandatory mandatory optional mandatory optional optional optional

OPTIONAL,

} } } } } } } },

| | | | | | |

3GPP

Release 11

896

3GPP TS 25.423 V11.2.0 (2012-06)

GERANUplinkSignallingTransferIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Extended-S-RNTI CRITICALITY ignore EXTENSION Extended-RNTI PRESENCE optional}, ... } -- ************************************************************** --- RADIO LINK PARAMETER UPDATE INDICATION FDD --- ************************************************************** RadioLinkParameterUpdateIndicationFDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkParameterUpdateIndicationFDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkParameterUpdateIndicationFDD-Extensions}} ... } RadioLinkParameterUpdateIndicationFDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-HSDSCH-FDD-Update-Information optional}| { ID id-RL-ParameterUpdateIndicationFDD-RL-InformationList PRESENCE optional }, ... } CRITICALITY ignore CRITICALITY ignore TYPE TYPE

OPTIONAL,

HSDSCH-FDD-Update-Information

PRESENCE

RL-ParameterUpdateIndicationFDD-RL-InformationList

RL-ParameterUpdateIndicationFDD-RL-InformationList ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF ProtocolIE-Single-Container { { RLParameterUpdateIndicationFDD-RL-InformationList-IEs} } RL-ParameterUpdateIndicationFDD-RL-InformationList-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RL-ParameterUpdateIndicationFDD-RL-Information-Item CRITICALITY ignore PRESENCE mandatory } } TYPE RL-ParameterUpdateIndicationFDD-RL-Information-Item

RL-ParameterUpdateIndicationFDD-RL-Information-Item::= SEQUENCE { rL-ID RL-ID, phase-Reference-Update-Indicator Phase-Reference-Update-Indicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-ParameterUpdateIndicationFDD-RL-Information-ExtIEs} } OPTIONAL, ... } RL-ParameterUpdateIndicationFDD-RL-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RadioLinkParameterUpdateIndicationFDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-FDD-Update-Information CRITICALITY ignore EXTENSION E-DCH-FDD-Update-Information PRESENCE optional}| { ID id-Additional-HS-Cell-Information-RL-Param-Upd CRITICALITY ignore EXTENSION Additional-HS-Cell-Information-RL-Param-Upd PRESENCE optional}| { ID id-Additional-EDCH-Cell-Information-RL-Param-Upd CRITICALITY ignore EXTENSION Additional-EDCH-Cell-Information-RL-Param-Upd PRESENCE optional}| { ID id-CPC-RecoveryReport CRITICALITY ignore EXTENSION CPC-RecoveryReport PRESENCE optional}|

3GPP

Release 11
{ ID id-UL-CLTD-State-Update-Information ... } CRITICALITY ignore

897
EXTENSION UL-CLTD-State-Update-Information

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional},

Additional-HS-Cell-Information-RL-Param-Upd ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Additional-HS-Cell-Information-RL-Param-Upd-ItemIEs

Additional-HS-Cell-Information-RL-Param-Upd-ItemIEs ::=SEQUENCE{ hSPDSCH-RL-ID RL-ID, hS-DSCH-FDD-Secondary-Serving-Update-Information HS-DSCH-FDD-Secondary-Serving-Update-Information, iE-Extensions ProtocolExtensionContainer { { Additional-HS-Cell-Information-RL-Setup-ExtIEs} } OPTIONAL, ... } Additional-HS-Cell-Information-RL-Setup-ExtIEs ... } Additional-EDCH-Cell-Information-RL-Param-Upd RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs

Additional-EDCH-Cell-Information-RL-Param-Upd-ItemIEs ::=SEQUENCE{ additional-EDCH-FDD-Update-Information Additional-EDCH-FDD-Update-Information, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-FDD-Update-Information-ExtIEs} } OPTIONAL, ... } Additional-EDCH-FDD-Update-Information-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

-- ************************************************************** --- RADIO LINK PARAMETER UPDATE INDICATION TDD --- ************************************************************** RadioLinkParameterUpdateIndicationTDD ::= SEQUENCE { protocolIEs ProtocolIE-Container {{RadioLinkParameterUpdateIndicationTDD-IEs}}, protocolExtensions ProtocolExtensionContainer {{RadioLinkParameterUpdateIndicationTDD-Extensions}} ... } RadioLinkParameterUpdateIndicationTDD-IEs RNSAP-PROTOCOL-IES ::= { { ID id-HSDSCH-TDD-Update-Information CRITICALITY optional}, ... } ignore TYPE HSDSCH-TDD-Update-Information

OPTIONAL,

PRESENCE

RadioLinkParameterUpdateIndicationTDD-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
} -- ************************************************************** --- UE MEASUREMENT INITIATION REQUEST --- **************************************************************

898

3GPP TS 25.423 V11.2.0 (2012-06)

UEMeasurementInitiationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UEMeasurementInitiationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{UEMeasurementInitiationRequest-Extensions}} ... } UEMeasurementInitiationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-AllowedQueuingTime CRITICALITY } | { ID id-MeasurementID CRITICALITY | { ID id-UEMeasurementType CRITICALITY | { ID id-UEMeasurementTimeslotInfoHCR CRITICALITY | { ID id-UEMeasurementTimeslotInfoLCR CRITICALITY | { ID id-MeasurementFilterCoefficient CRITICALITY | { ID id-UEMeasurementReportCharacteristics CRITICALITY { ID id-UEMeasurementParameterModAllow CRITICALITY ... } reject reject reject reject reject reject reject reject TYPE AllowedQueuingTime TYPE MeasurementID TYPE UEMeasurementType TYPE UEMeasurementTimeslotInfoHCR TYPE UEMeasurementTimeslotInfoLCR TYPE MeasurementFilterCoefficient TYPE UEMeasurementReportCharacteristics TYPE UEMeasurementParameterModAllow

OPTIONAL,

PRESENCE optional PRESENCE mandatory PRESENCE mandatory PRESENCE optional PRESENCE optional PRESENCE optional PRESENCE mandatory } | PRESENCE mandatory }, } } } } }

UEMeasurementInitiationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UEMeasurementTimeslotInfo768 CRITICALITY reject ... } -- ************************************************************** --- UE MEASUREMENT INITIATION RESPONSE --- **************************************************************

EXTENSION UEMeasurementTimeslotInfo768

PRESENCE optional},

UEMeasurementInitiationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UEMeasurementInitiationResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{UEMeasurementInitiationResponse-Extensions}} ... } UEMeasurementInitiationResponse-IEs RNSAP-PROTOCOL-IES ::= {

OPTIONAL,

3GPP

Release 11
| | { ID id-MeasurementID { ID id-MeasurementFilterCoefficient { ID id-UEMeasurementReportCharacteristics { ID id-CriticalityDiagnostics }, ... } UEMeasurementInitiationResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- UE MEASUREMENT INITIATION FAILURE --- ************************************************************** CRITICALITY ignore CRITICALITY reject CRITICALITY reject CRITICALITY ignore

899
TYPE MeasurementID TYPE MeasurementFilterCoefficient TYPE UEMeasurementReportCharacteristics TYPE CriticalityDiagnostics

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory PRESENCE optional PRESENCE optional } | PRESENCE optional } }

UEMeasurementInitiationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UEMeasurementInitiationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{UEMeasurementInitiationFailure-Extensions}} ... } UEMeasurementInitiationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore { ID id-Cause CRITICALITY ignore { ID id-CriticalityDiagnostics CRITICALITY ignore ... } TYPE MeasurementID TYPE Cause TYPE CriticalityDiagnostics PRESENCE mandatory PRESENCE mandatory PRESENCE optional

OPTIONAL,

} | } | },

UEMeasurementInitiationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- UE MEASUREMENT REPORT --- ************************************************************** UEMeasurementReport ::= SEQUENCE { protocolIEs protocolExtensions ... } ProtocolIE-Container {{UEMeasurementReport-IEs}}, ProtocolExtensionContainer {{UEMeasurementReport-Extensions}}

OPTIONAL,

UEMeasurementReport-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore

TYPE MeasurementID

PRESENCE mandatory

} |

3GPP

Release 11
{ ID id-UEMeasurementValueInformation ... } UEMeasurementReport-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- UE MEASUREMENT TERMINATION REQUEST --- ************************************************************** CRITICALITY ignore

900
TYPE UEMeasurementValueInformation

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory },

UEMeasurementTerminationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UEMeasurementTerminationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{UEMeasurementTerminationRequest-Extensions}} ... } UEMeasurementTerminationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID ... } UEMeasurementTerminationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- UE MEASUREMENT FAILURE INDICATION --- ************************************************************** UEMeasurementFailureIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{UEMeasurementFailureIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{UEMeasurementFailureIndication-Extensions}} ... } UEMeasurementFailureIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MeasurementID CRITICALITY ignore TYPE MeasurementID { ID id-Cause CRITICALITY ignore TYPE Cause ... } UEMeasurementFailureIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } PRESENCE mandatory PRESENCE mandatory } | }, PRESENCE mandatory },

OPTIONAL,

OPTIONAL,

3GPP

Release 11
-- ************************************************************** --- IUR INVOKE TRACE --- ************************************************************** IurInvokeTrace ::= SEQUENCE { protocolIEs protocolExtensions ... } IurInvokeTrace-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI }| { ID id-TraceReference }| { ID id-UEIdentity }| { ID id-TraceRecordingSessionReference { ID id-ListOfInterfacesToTrace }| { ID id-TraceDepth }, ... } ProtocolIE-Container ProtocolExtensionContainer

901

3GPP TS 25.423 V11.2.0 (2012-06)

{{IurInvokeTrace-IEs}}, {{IurInvokeTrace-Extensions}}

OPTIONAL,

CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore

TYPE D-RNTI TYPE TraceReference TYPE UEIdentity TYPE TraceRecordingSessionReference TYPE ListOfInterfacesToTrace TYPE TraceDepth

PRESENCE optional PRESENCE mandatory PRESENCE mandatory PRESENCE mandatory }| PRESENCE optional PRESENCE mandatory

ListOfInterfacesToTrace ::= SEQUENCE (SIZE (1..maxNrOfInterfaces)) OF ProtocolIE-Single-Container {{ InterfacesToBeTracedItemIE }} InterfacesToBeTracedItemIE RNSAP-PROTOCOL-IES ::= { { ID id-InterfacesToTraceItem CRITICALITY ignore } TYPE InterfacesToTraceItem PRESENCE mandatory }

InterfacesToTraceItem ::= SEQUENCE { interface ENUMERATED {iub,iur,...}, iE-Extensions ProtocolExtensionContainer { {InterfacesToTraceItem-ExtIEs} } ... } InterfacesToTraceItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } IurInvokeTrace-Extensions RNSAP-PROTOCOL-EXTENSION ::= { -- Extension for Release 10 to support MDT {ID id-MDT-Configuration CRITICALITY ignore -- Extension for Release 10 to support MDT {ID id-Trace-Collection-Entity-IP-Address CRITICALITY ignore ... }

OPTIONAL,

EXTENSION MDT-Configuration EXTENSION TransportLayerAddress

PRESENCE optional}| PRESENCE optional},

3GPP

Release 11
-- ************************************************************** --- IUR DEACTIVATE TRACE --- ************************************************************** IurDeactivateTrace ::= SEQUENCE { protocolIEs protocolExtensions ... } ProtocolIE-Container ProtocolExtensionContainer

902

3GPP TS 25.423 V11.2.0 (2012-06)

{{IurDeactivateTrace-IEs}}, {{IurDeactivateTrace-Extensions}}

OPTIONAL,

IurDeactivateTrace-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY ignore }| { ID id-TraceReference CRITICALITY ignore }, ... } IurDeactivateTrace-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- MBMS ATTACH COMMAND --- **************************************************************

TYPE D-RNTI TYPE TraceReference

PRESENCE optional PRESENCE mandatory

MBMSAttachCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container {{MBMSAttachCommand-IEs}}, protocolExtensions ProtocolExtensionContainer {{MBMSAttachCommand-Extensions}} ... } MBMSAttachCommand-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MBMS-Bearer-Service-List CRITICALITY { ID id-UE-State CRITICALITY ... } MBMSAttachCommand-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- MBMS DETACH COMMAND -ignore ignore

OPTIONAL,

TYPE MBMS-Bearer-Service-List PRESENCE mandatory} | TYPE UE-State PRESENCE optional},

3GPP

Release 11
-- **************************************************************

903

3GPP TS 25.423 V11.2.0 (2012-06)

MBMSDetachCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container {{MBMSDetachCommand-IEs}}, protocolExtensions ProtocolExtensionContainer {{MBMSDetachCommand-Extensions}} ... } MBMSDetachCommand-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MBMS-Bearer-Service-List CRITICALITY { ID id-UE-State CRITICALITY ... } ignore ignore

OPTIONAL,

TYPE MBMS-Bearer-Service-List PRESENCE TYPE UE-State PRESENCE

mandatory} | optional},

MBMSDetachCommand-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- DIRECT INFORMATION TRANSFER --- ************************************************************** DirectInformationTransfer ::= SEQUENCE { protocolIEs ProtocolIE-Container protocolExtensions ProtocolExtensionContainer ... } {{DirectInformationTransfer-IEs}}, {{DirectInformationTransfer-Extensions}}

OPTIONAL,

DirectInformationTransfer-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RNC-ID CRITICALITY ignore { ID id-ProvidedInformation CRITICALITY ignore ... }

TYPE RNC-ID TYPE ProvidedInformation

PRESENCE mandatory} | PRESENCE mandatory} ,

DirectInformationTransfer-Extensions RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-RNC-ID CRITICALITY reject EXTENSION Extended-RNC-ID ... } -- ************************************************************** --- ENHANCED RELOCATION REQUEST --- **************************************************************

PRESENCE optional },

EnhancedRelocationRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationRequest-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationRequest-Extensions}} ...

OPTIONAL,

3GPP

Release 11
}

904

3GPP TS 25.423 V11.2.0 (2012-06)

EnhancedRelocationRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory } | { ID id-Permanent-NAS-UE-Identity CRITICALITY reject TYPE Permanent-NAS-UE-Identity PRESENCE mandatory } | { ID id-SRNC-ID CRITICALITY reject TYPE RNC-ID PRESENCE optional }| -- This IE shall be present if the Relocation type IE is set to UE involved in relocation of SRNS -{ ID id-Extended-SRNC-ID CRITICALITY reject TYPE Extended-RNC-ID PRESENCE optional }| { ID id-S-RNTI CRITICALITY reject TYPE S-RNTI PRESENCE mandatory }| { ID id-RANAP-EnhancedRelocationInformationRequest CRITICALITY reject TYPE RANAP-EnhancedRelocationInformationRequest mandatory }, ... } EnhancedRelocationRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Extended-S-RNTI CRITICALITY reject EXTENSION Extended-RNTI ... } -- ************************************************************** --- ENHANCED RELOCATION RESPONSE --- ************************************************************** EnhancedRelocationResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationResponse-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationResponse-Extensions}} ... } EnhancedRelocationResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-RANAP-EnhancedRelocationInformationResponse mandatory }, ... } CRITICALITY ignore PRESENCE optional},

PRESENCE

OPTIONAL,

TYPE RANAP-EnhancedRelocationInformationResponse

PRESENCE

EnhancedRelocationResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION FAILURE --- ************************************************************** EnhancedRelocationFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationFailure-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationFailure-Extensions}} ...

OPTIONAL,

3GPP

Release 11
} EnhancedRelocationFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause { ID id-CriticalityDiagnostics CRITICALITY ignore ... }

905

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE mandatory }| TYPE CriticalityDiagnostics

PRESENCE optional

},

EnhancedRelocationFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION CANCEL --- ************************************************************** EnhancedRelocationCancel ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationCancel-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationCancel-Extensions}} ... } EnhancedRelocationCancel-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause ... } EnhancedRelocationCancel-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION SIGNALLING TRANSFER --- ************************************************************** EnhancedRelocationSignallingTransfer ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationSignallingTransfer-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationSignallingTransfer-Extensions}} ... } EnhancedRelocationSignallingTransfer-IEs RNSAP-PROTOCOL-IES ::= { { ID id-L3-Information CRITICALITY ignore TYPE L3-Information ... } EnhancedRelocationSignallingTransfer-Extensions RNSAP-PROTOCOL-EXTENSION ::= { PRESENCE mandatory }, PRESENCE mandatory },

OPTIONAL,

OPTIONAL,

3GPP

Release 11
} ...

906

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- ENHANCED RELOCATION RELEASE --- ************************************************************** EnhancedRelocationRelease ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationRelease-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationRelease-Extensions}} ... } EnhancedRelocationRelease-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Released-CN-Domain CRITICALITY ignore ... } TYPE Released-CN-Domain PRESENCE mandatory

OPTIONAL,

},

EnhancedRelocationRelease-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- MBSFN MCCH INFORMATION --- ************************************************************** MBSFNMCCHInformation ::= SEQUENCE { protocolIEs ProtocolIE-Container {{MBSFNMCCHInformation-IEs}}, protocolExtensions ProtocolExtensionContainer {{MBSFNMCCHInformation-Extensions}} ... }

OPTIONAL,

MBSFNMCCHInformation-IEs RNSAP-PROTOCOL-IES ::= { { ID id-MBSFN-Cluster-Identity CRITICALITY ignore TYPE MBSFN-Cluster-Identity PRESENCE mandatory} | { ID id-MCCH-Message-List CRITICALITY reject TYPE MCCH-Message-List PRESENCE mandatory} | { ID id-CFN CRITICALITY reject TYPE CFN PRESENCE mandatory}| { ID id-MCCH-Configuration-Info CRITICALITY ignore TYPE MCCH-Configuration-Info PRESENCE optional}| { ID id-MBSFN-Scheduling-Transmission-Time-Interval-Info-List CRITICALITY ignore TYPE MBSFN-Scheduling-Transmission-Time-Interval-InfoList PRESENCE optional}, ... } MBSFNMCCHInformation-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
-- ************************************************************** --- SECONDARY UL FREQUENCY REPORT --- **************************************************************

907

3GPP TS 25.423 V11.2.0 (2012-06)

SecondaryULFrequencyReport ::= SEQUENCE { protocolIEs ProtocolIE-Container {{SecondaryULFrequencyReport-IEs}}, protocolExtensions ProtocolExtensionContainer {{SecondaryULFrequencyReport-Extensions}} ... } SecondaryULFrequencyReport-IEs RNSAP-PROTOCOL-IES ::= { { ID id-ActivationInformation CRITICALITY ignore ... } TYPE ActivationInformation

OPTIONAL,

PRESENCE mandatory },

SecondaryULFrequencyReport-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- SECONDARY UL FREQUENCY UPDATE INDICATION --- ************************************************************** SecondaryULFrequencyUpdateIndication ::= SEQUENCE { protocolIEs ProtocolIE-Container {{SecondaryULFrequencyUpdateIndication-IEs}}, protocolExtensions ProtocolExtensionContainer {{SecondaryULFrequencyUpdateIndication-Extensions}} ... } SecondaryULFrequencyUpdateIndication-IEs RNSAP-PROTOCOL-IES ::= { { ID id-ActivationInformation CRITICALITY ignore TYPE ActivationInformation ... } SecondaryULFrequencyUpdateIndication-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION RESOURCE REQUEST --- ************************************************************** EnhancedRelocationResourceRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container {{ EnhancedRelocationResourceRequest-IEs}},

OPTIONAL,

PRESENCE mandatory },

3GPP

Release 11
protocolExtensions ... } ProtocolExtensionContainer

908
{{ EnhancedRelocationResourceRequest-Extensions}} OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

EnhancedRelocationResourceRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-IMSI CRITICALITY reject TYPE IMSI { ID id-SourceID CRITICALITY ignore TYPE SourceID { ID id-TargetID CRITICALITY reject TYPE TargetID { ID id-ClassmarkInformation2 CRITICALITY reject TYPE ClassmarkInformation2 { ID id-ClassmarkInformation3 CRITICALITY ignore TYPE ClassmarkInformation3 { ID id-SpeechVersion CRITICALITY ignore TYPE SpeechVersion ... } EnhancedRelocationResourceRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION RESOURCE RESPONSE --- ************************************************************** EnhancedRelocationResourceResponse ::= SEQUENCE { protocolIEs ProtocolIE-Container protocolExtensions ProtocolExtensionContainer ... }

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

optional}| mandatory}| mandatory}| mandatory}| mandatory}| mandatory},

{{EnhancedRelocationResourceResponse-IEs}}, {{EnhancedRelocationResourceResponse-Extensions}}

OPTIONAL,

EnhancedRelocationResourceResponse-IEs RNSAP-PROTOCOL-IES ::= { { ID id-D-RNTI CRITICALITY ignore { ID id-L3-Information CRITICALITY ignore { ID id-Cell-Capacity-Class-Value CRITICALITY ignore { ID id-LoadValue CRITICALITY ignore ... }

TYPE TYPE TYPE TYPE

D-RNTI L3-Information Cell-Capacity-Class-Value LoadValue

PRESENCE PRESENCE PRESENCE PRESENCE

mandatory }| mandatory }| optional }| optional },

EnhancedRelocationResourceResponse-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION RESOURCE FAILURE --- ************************************************************** EnhancedRelocationResourceFailure ::= SEQUENCE { protocolIEs ProtocolIE-Container protocolExtensions ProtocolExtensionContainer ... {{EnhancedRelocationResourceFailure-IEs}}, {{EnhancedRelocationResourceFailure-Extensions}}

OPTIONAL,

3GPP

Release 11
}

909

3GPP TS 25.423 V11.2.0 (2012-06)

EnhancedRelocationResourceFailure-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause { ID id-Cell-Capacity-Class-Value CRITICALITY ignore TYPE Cell-Capacity-Class-Value { ID id-LoadValue CRITICALITY ignore TYPE LoadValue ... } EnhancedRelocationResourceFailure-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION RESOURCE RELEASE COMMAND --- **************************************************************

PRESENCE mandatory }| PRESENCE optional }| PRESENCE optional },

EnhancedRelocationResourceReleaseCommand ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationResourceReleaseCommand-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationResourceReleaseCommand-Extensions}} OPTIONAL, ... } EnhancedRelocationResourceReleaseCommand-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}, ... } EnhancedRelocationResourceReleaseCommand-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } -- ************************************************************** --- ENHANCED RELOCATION RESOURCE RELEASE COMPLETE --- ************************************************************** EnhancedRelocationResourceReleaseComplete ::= SEQUENCE { protocolIEs ProtocolIE-Container {{EnhancedRelocationResourceReleaseComplete-IEs}}, protocolExtensions ProtocolExtensionContainer {{EnhancedRelocationResourceReleaseComplete-Extensions}} ... } EnhancedRelocationResourceReleaseComplete-IEs RNSAP-PROTOCOL-IES ::= { ... } EnhancedRelocationResourceReleaseComplete-Extensions RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

3GPP

Release 11
} ...

910

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- PRIVATE MESSAGE --- ************************************************************** PrivateMessage ::= SEQUENCE { privateIEs PrivateIE-Container ... } {{PrivateMessage-IEs}},

PrivateMessage-IEs RNSAP-PRIVATE-IES ::= { ... } -- ************************************************************** --- INFORMATION TRANSFER CONTROL REQUEST --- ************************************************************** InformationTransferControlRequest ::= SEQUENCE { protocolIEs ProtocolIE-Container protocolExtensions ProtocolExtensionContainer ... } {{ InformationTransferControlRequest-IEs}}, {{ InformationTransferControlRequest-Extensions}}

OPTIONAL,

InformationTransferControlRequest-IEs RNSAP-PROTOCOL-IES ::= { { ID id-Control-Type-InformationTransferControlReq CRITICALITY ignore ... } InformationTransferControlRequest-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... } Control-Type-InformationTransferControlReq ::= CHOICE { suspension Suspension-Control-Type, resume Resume-Control-Type, ... }

TYPE Control-Type-InformationTransferControlReq

PRESENCE mandatory },

Suspension-Control-Type ::= SEQUENCE { controlled-Object-Scope Controlled-Object-Scope, iE-Extensions ProtocolExtensionContainer {{ Suspension-Control-Type-ExtIEs}}, ... }

3GPP

Release 11
Suspension-Control-Type-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

911

3GPP TS 25.423 V11.2.0 (2012-06)

Resume-Control-Type ::= SEQUENCE { controlled-Object-Scope Controlled-Object-Scope, iE-Extensions ProtocolExtensionContainer { { Resume-Control-Type-ExtIEs}}, ... } Resume-Control-Type-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } END

9.3.4 Information Element Definitions

-- ************************************************************** --- Information Element Definitions --- ************************************************************** RNSAP-IEs { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-IEs (2) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS maxCellSIB11OrSIB12, maxNrOfFACHs, maxIBSEG, maxCellsMeas, maxNoOfDSCHs, maxNoOfUSCHs, maxNrOfDCHs, maxNrOfDL-Codes, maxNrOfDLTs, maxNrOfDLTsLCR, maxNrOfDPCHs, maxNrOfDPCHs768, maxNrOfDPCHsLCR, maxNrOfEDCH-HARQ-PO-QUANTSTEPs, maxNrOfBits-MACe-PDU-non-scheduled, maxNrOfEDPCCH-PO-QUANTSTEPs, maxNrOfRefETFCI-PO-QUANTSTEPs,

3GPP

Release 11
maxNrOfRefETFCIs, maxNrOfErrors, maxNrOfFDDNeighboursPerRNC, maxNrOfMACcshSDU-Length, maxNrOfNeighbouringRNCs, maxNrOfTDDNeighboursPerRNC, maxNrOfLCRTDDNeighboursPerRNC, maxNrOfTS, maxNrOfTsLCR, maxNrOfULTs, maxNrOfULTsLCR, maxNrOfGSMNeighboursPerRNC, maxRateMatching, maxNrOfPoints, maxNoOfRB, maxNrOfRLs, maxNrOfTFCs, maxNrOfTFs, maxCTFC, maxRNCinURA-1, maxNrOfSCCPCHs, maxNrOfSCCPCHs768, maxTGPS, maxTTI-Count, maxNoGPSTypes, maxNoSat, maxNrOfActiveMBMSServices, maxNrOfCells, maxNrOfSNAs, maxNrOfHARQProc, maxNrOfHSSCCHCodes, maxNrOfMACdFlows, maxNrOfMACdFlows-1, maxNrOfMACdPDUSize, maxNrOfMBMSL3, maxNrOfMCCHMessages, maxNrOfEDCHMACdFlows, maxNrOfEDCHMACdFlows-1, maxNrOfEDCHMACdFlowsLCR, maxNrOfEDCHMACdFlowsLCR-1, maxNrOfMBMSServices, maxNrOfPDUIndexes, maxNrOfPDUIndexes-1, maxNrOfPrioQueues, maxNrOfPrioQueues-1, maxNrOfSatAlmanac-maxNoSat, maxNrOfGERANSI, maxNrofSigSeqERGHICH-1, maxNrOfAddFreq, maxNrOfCellsPerFreq, maxNoOfLogicalChannels,

912

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
maxNrOfRefBetas, maxNrOfEAGCHCodes, maxNrOfHS-DSCHTBSs, maxNrOfHS-DSCHTBSs-HS-SCCHless, maxHS-PDSCHCodeNrComp-1, maxNrOfEHICHCodes, maxGANSSSat, maxNoGANSS, maxSgnType, maxNrOfBroadcastPLMNs, maxHSDPAFrequency, maxHSDPAFrequency-1, maxFrequencyinCell, maxFrequencyinCell-1, maxGANSSSatAlmanac, maxGANSSClockMod, maxNrOfEDCHRLs, maxNrOfEUTRANeighboursPerRNC, maxEARFCN, maxNrOfPreconfiguredNeighbours, maxNrOfHSDSCH-1, maxNrOfHSDSCH, maxGANSS-1, maxlengthMBMSconcatservlists, maxNoOfTBSs-Mapping-HS-DSCH-SPS, maxNoOfTBSs-Mapping-HS-DSCH-SPS-1, maxNoOfHS-DSCH-TBSsLCR, maxNoOfRepetition-Period-LCR, maxNoOfRepetitionPeriod-SPS-LCR-1, maxNoOf-HS-SICH-SPS, maxNoOf-HS-SICH-SPS-1, maxNoOfNon-HS-SCCH-Assosiated-HS-SICH, maxNrOfEDCH-1, maxNrOfDCHMeasurementOccasionPatternSequence, maxNrOfULCarriersLCR-1, maxNrOfCellIds, maxNrOfRAIs, maxNrOfLAIs, maxNrOfExtendedNeighbouringRNCs, maxFreqBandsTDD, id-Allowed-Rate-Information, id-AntennaColocationIndicator, id-Cell-Capacity-Class-Value, id-CellCapabilityContainer-FDD, id-CellCapabilityContainer-TDD, id-CellCapabilityContainer-TDD-LCR, id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information, id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response, id-Counting-Information, id-CoverageIndicator,

913

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-DPC-Mode-Change-SupportIndicator, id-E-DCH-Minimum-Set-E-TFCIValidityIndicator, id-E-RGCH-E-HICH-ChannelisationCodeValidityIndicator, id-Extended-Round-Trip-Time-Value, id-ExtendedPropagationDelay, id-Extended-SRNC-ID, id-Extended-RNC-ID, id-ExtendedAffectedUEInformationForMBMS, id-GERAN-Cell-Capability, id-GERAN-Classmark, id-Guaranteed-Rate-Information, id-HARQ-Preamble-Mode-Activation-Indicator, id-HCS-Prio, id-Inter-Frequency-Cell-Information, id-Load-Value, id-Load-Value-IncrDecrThres, id-Neighbouring-GSM-CellInformation, id-Neighbouring-UMTS-CellInformationItem, id-neighbouring-LCR-TDD-CellInformation, id-NRT-Load-Information-Value, id-NRT-Load-Information-Value-IncrDecrThres, id-OnModification, id-Received-Total-Wideband-Power-Value, id-Received-Total-Wideband-Power-Value-IncrDecrThres, id-RT-Load-Value, id-RT-Load-Value-IncrDecrThres, id-SFNSFNMeasurementThresholdInformation, id-SNA-Information, id-TrafficClass, id-Transmitted-Carrier-Power-Value, id-Transmitted-Carrier-Power-Value-IncrDecrThres, id-TUTRANGPSMeasurementThresholdInformation, id-UL-Timeslot-ISCP-Value, id-UL-Timeslot-ISCP-Value-IncrDecrThres, maxNrOfLevels, maxNrOfMeasNCell, maxNrOfMeasNCell-1, id-MessageStructure, id-RestrictionStateIndicator, id-Rx-Timing-Deviation-Value-LCR, id-Transmission-Mode-Information, id-TypeOfError, id-Angle-Of-Arrival-Value-LCR, id-IPDL-TDD-ParametersLCR, id-DSCH-InitialWindowSize, id-Maximum-DL-Power-TimeslotLCR-InformationItem, id-MBMS-Bearer-Service-Full-Address, id-MBMS-Neighbouring-Cell-Information, id-MBMS-RLC-Sequence-Number-Information, id-MBSFN-Cluster-Identity, id-MBSFN-Scheduling-Transmission-Time-Interval-Info-List,

914

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-MCCH-Configuration-Info, id-MCCH-Message-List, id-Minimum-DL-Power-TimeslotLCR-InformationItem, id-HS-SICH-Reception-Quality, id-HS-SICH-Reception-Quality-Measurement-Value, id-HS-PDSCH-Code-Change-Grant, id-HS-PDSCH-Code-Change-Indicator, id-ExtendedGSMCellIndividualOffset, id-Unidirectional-DCH-Indicator, id-RTLoadValue, id-RLC-Sequence-Number, id-NRTLoadInformationValue, id-Satellite-Almanac-Information-ExtItem, id-TnlQos, id-UpPTSInterferenceValue, id-NACC-Related-Data, id-HARQ-Preamble-Mode, id-User-Plane-Congestion-Fields-Inclusion, id-FrequencyBandIndicator, id-PLCCH-Information-UL-TimeslotLCR-Info, id-CellCapabilityContainer-TDD768, id-hSSCCH-TDD-Specific-InfoList-Response768, id-hSPDSCH-TDD-Specific-InfoList-Response768, id-Rx-Timing-Deviation-Value-768, id-UEMeasurementValueTransmittedPowerList768, id-UEMeasurementValueTimeslotISCPList768, id-E-DCH-PowerOffset-for-SchedulingInfo, id-Rx-Timing-Deviation-Value-ext, id-TrCH-SrcStatisticsDescr, id-eDCH-MACdFlow-Retransmission-Timer-LCR, id-MIMO-ActivationIndicator, id-MIMO-InformationResponse, id-MIMO-Mode-Indicator, id-MIMO-N-M-Ratio, id-SixteenQAM-UL-Operation-Indicator, id-E-AGCH-Table-Choice, id-E-TFCI-Boost-Information, id-E-DPDCH-PowerInterpolation, id-HSDSCH-MACdPDUSizeFormat, id-MaximumMACdPDU-SizeExtended, id-GANSS-Common-Data, id-GANSS-Information, id-GANSS-Generic-Data, id-TUTRANGANSSMeasurementThresholdInformation, id-TUTRANGANSSMeasurementValueInformation, id-HARQ-MemoryPartitioningInfoExtForMIMO, id-Ext-Reference-E-TFCI-PO, id-Ext-Max-Bits-MACe-PDU-non-scheduled, id-Multiple-PLMN-List, id-TransportBearerNotSetupIndicator, id-TransportBearerNotRequestedIndicator,

915

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-UARFCNforNt, id-LCRTDD-uplink-Physical-Channel-Capability, id-number-Of-Supported-Carriers, id-HSSICH-SIRTarget, id-HSSICH-TPC-StepSize, id-tSN-Length, id-HS-SICH-ID-Extension, id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR, id-multicarrier-number, id-UpPCH-InformationList-LCRTDD, id-UpPCH-InformationItem-LCRTDD, id-Max-UE-DTX-Cycle, id-Default-Serving-Grant-in-DTX-Cycle2, id-SixtyfourQAM-UsageAllowedIndicator, id-SixtyfourQAM-DL-UsageIndicator, id-UE-Capabilities-Info, id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory, id-Continuous-Packet-Connectivity-HS-SCCH-Less-Deactivate-Indicator, id-E-DCH-MACdPDUSizeFormat, id-E-PUCH-PowerControlGAP, id-MaximumNumber-Of-Retransmission-For-SchedulingInfo-LCRTDD, id-E-DCH-RetransmissionTimer-For-SchedulingInfo-LCRTDD, id-HSDSCH-TBSizeTableIndicator, id-E-DCH-DL-Control-Channel-Change-Information, id-E-DCH-DL-Control-Channel-Grant-Information, id-DGANSS-Corrections-Req, id-UE-with-enhanced-HS-SCCH-support-indicator, id-EnhancedHSServingCC-Abort, id-GANSS-Time-ID, id-GANSS-AddIonoModelReq, id-GANSS-EarthOrientParaReq, id-GANSS-AddNavigationModelsReq, id-GANSS-AddUTCModelsReq, id-GANSS-AuxInfoReq, id-GANSS-SBAS-ID, id-GANSS-ID, id-GANSS-Additional-Ionospheric-Model, id-GANSS-Earth-Orientation-Parameters, id-GANSS-Additional-Time-Models, id-GANSS-Additional-Navigation-Models, id-GANSS-Additional-UTC-Models, id-GANSS-Auxiliary-Information, id-GANSS-alm-keplerianNAVAlmanac, id-GANSS-alm-keplerianReducedAlmanac, id-GANSS-alm-keplerianMidiAlmanac, id-GANSS-alm-keplerianGLONASS, id-GANSS-alm-ecefSBASAlmanac, id-Secondary-Serving-Cell-List, id-MinimumReducedE-DPDCH-GainFactor, id-E-AGCH-UE-Inactivity-Monitor-Threshold,

916

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11

917

3GPP TS 25.423 V11.2.0 (2012-06)

id-MACes-Maximum-Bitrate-LCR, id-MultiCarrier-HSDSCH-Physical-Layer-Category, id-MIMO-SFMode-For-HSPDSCHDualStream, id-MIMO-SFMode-Supported-For-HSPDSCHDualStream, id-MIMO-ReferenceSignal-InformationListLCR, id-DL-RLC-PDU-Size-Format, id-UE-SupportIndicatorExtension, id-power-offset-for-S-CPICH-for-MIMO, id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator, id-Dual-Band-Secondary-Serving-Cell-List, id-Single-Stream-MIMO-ActivationIndicator, id-Single-Stream-MIMO-Mode-Indicator, id-Additional-EDCH-Preconfiguration-Information, id-MulticellEDCH-Information, id-EDCH-Indicator, id-DiversityMode, id-TransmitDiversityIndicator, id-NonCellSpecificTxDiversity, id-CellCapabilityContainerExtension-FDD, id-HSDSCH-Physical-Layer-Category, id-TS0-HS-PDSCH-Indication-LCR, id-UE-TS0-CapabilityLCR, id-DGNSS-ValidityPeriod, id-UE-AggregateMaximumBitRate-Enforcement-Indicator, id-Out-of-Sychronization-Window, id-MulticellEDCH-RL-SpecificInformation, id-Continuous-Packet-Connectivity-DTX-DRX-Information, id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup, id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList, id-OrdinalNumberOfFrequency, id-Multicell-EDCH-Restriction, id-CellListValidityIndicator, id-completeAlmanacProvided, id-ganss-Delta-T, id-CellCapabilityContainerExtension-TDD-LCR, id-SNPL-Carrier-Group-Indicator, id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext, id-Measurement-Power-Offset, id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory, id-Neighbouring-UMTS-CellInformationExtensionItem, id-EventH, id-UMTS-Cells-Info, id-ANRReportIndication, id-ANR-Cell-Information, id-Affected-HSDSCH-Serving-Cell-List, id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order, id-UE-RF-Band-CapabilityLCR

FROM RNSAP-Constants

3GPP

Release 11
Criticality, ProcedureID, ProtocolIE-ID, TransactionID, TriggeringMessage FROM RNSAP-CommonDataTypes ProtocolIE-Single-Container{}, ProtocolExtensionContainer{}, RNSAP-PROTOCOL-IES, RNSAP-PROTOCOL-EXTENSION FROM RNSAP-Containers; -- A AccessPointName ::= OCTET STRING (SIZE (1..255))

918

3GPP TS 25.423 V11.2.0 (2012-06)

AckNack-RepetitionFactor ::= INTEGER (1..4,...) -- Step: 1 Ack-Power-Offset ::= INTEGER (0..8,...) -- According to mapping in TS 25.213 [21] subclause 4.2.1 ActivationInformation ::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF ActivationInformationItem ActivationInformationItem ::= SEQUENCE { uU-ActivationState Uu-ActivationState, iE-Extensions ... }

ProtocolExtensionContainer { { ActivationInformationItem-ExtIEs} }

OPTIONAL,

ActivationInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Active-MBMS-Bearer-Service-ListFDD ::= SEQUENCE (SIZE (1..maxNrOfActiveMBMSServices)) OF MBMS-Bearer-ServiceItemFDD ::= SEQUENCE (SIZE (1..maxNrOfActiveMBMSServices)) OF MBMS-Bearer-ServiceItemFDD-PFL

Active-MBMS-Bearer-Service-ListFDD-PFL Active-MBMS-Bearer-Service-ListTDD

::= SEQUENCE (SIZE (1..maxNrOfActiveMBMSServices)) OF MBMS-Bearer-ServiceItemTDD ::= SEQUENCE (SIZE (1..maxNrOfActiveMBMSServices)) OF MBMS-Bearer-ServiceItemTDD-PFL

Active-MBMS-Bearer-Service-ListTDD-PFL

Active-Pattern-Sequence-Information ::= SEQUENCE { cMConfigurationChangeCFN CFN, transmission-Gap-Pattern-Sequence-Status Transmission-Gap-Pattern-Sequence-Status-List OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Active-Pattern-Sequence-Information-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11
Active-Pattern-Sequence-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

919

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-Cell-Information-Response-RLAddList ::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-Response-RLAdd-ItemIEs Additional-EDCH-Cell-Information-Response-RLAdd-ItemIEs ::=SEQUENCE{ additional-EDCH-FDD-Information-Response Additional-EDCH-FDD-Information-Response-ItemIEs OPTIONAL, additional-EDCH-Serving-Cell-Change-Information-Response-RLAdd E-DCH-Serving-cell-change-informationResponse OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-Response-RLAdd-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-Response-RLAdd-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-Setup-Info ::=SEQUENCE{ multicell-EDCH-Transport-Bearer-Mode Multicell-EDCH-Transport-Bearer-Mode, additional-EDCH-Cell-Information-Setup Additional-EDCH-Cell-Information-Setup, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Setup-Info-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Setup-Info-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

ANRReportIndication ::= SEQUENCE { pLMN-Identity PLMN-Identity, l3-Information L3-Information, iE-Extensions ProtocolExtensionContainer { {ANRReportIndication-ExtIEs} } OPTIONAL, ... } ANRReportIndication-ExtIEs RNSAP-PROTOCOL-EXTENSION ::={ ... } Multicell-EDCH-Transport-Bearer-Mode ::= ENUMERATED { separate-Iur-Transport-Bearer-Mode, uL-Flow-Multiplexing-Mode } Additional-EDCH-Cell-Information-Setup ::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Setup-Cell-Information Additional-EDCH-UL-DPCH-Information-Setup, Additional-EDCH-RL-Specific-Information-To-Setup-List, Additional-EDCH-FDD-Information OPTIONAL, Additional-EDCH-F-DPCH-Information,

Additional-EDCH-FDD-Setup-Cell-Information ::=SEQUENCE{ additional-EDCH-UL-DPCH-Information-Setup additional-EDCH-RL-Specific-Information-To-Setup additional-EDCH-FDD-Information additional-EDCH-F-DPCH-Information-Setup

3GPP

Release 11
multicellEDCH-Information iE-Extensions ...

920

3GPP TS 25.423 V11.2.0 (2012-06)

MulticellEDCH-Information OPTIONAL, ProtocolExtensionContainer { { Additional-EDCH-FDD-Setup-Cell-Information-ExtIEs} } OPTIONAL,

Additional-EDCH-FDD-Setup-Cell-Information-ExtIEs ... }

RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-UL-DPCH-Information-Setup ::=SEQUENCE{ ul-ScramblingCode UL-ScramblingCode, ul-SIR-Target UL-SIR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-UL-DPCH-Information-Setup-ExtIEs} } OPTIONAL, ... } Additional-EDCH-UL-DPCH-Information-Setup-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-F-DPCH-Information ::=SEQUENCE{ fdd-TPC-DownlinkStepSize FDD-TPC-DownlinkStepSize, limitedPowerIncrease LimitedPowerIncrease, innerLoopDLPCStatus InnerLoopDLPCStatus, f-DPCH-SlotFormatSupportRequest F-DPCH-SlotFormatSupportRequest OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-F-DPCH-Information-ExtIEs} } OPTIONAL, ... } Additional-EDCH-F-DPCH-Information-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-RL-Specific-Information-To-Setup-List ItemIEs

::= SEQUENCE (SIZE (1.. maxNrOfEDCHRLs)) OF Additional-EDCH-RL-Specific-Information-To-Setup-

Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, c-ID C-ID OPTIONAL, firstRLS-indicator FirstRLS-Indicator, propagationDelay PropagationDelay OPTIONAL, initialDL-transmissionPower DL-Power OPTIONAL, primaryCPICH-EcNo PrimaryCPICH-EcNo OPTIONAL, e-AGCH-PowerOffset E-AGCH-PowerOffset OPTIONAL, e-RGCH-PowerOffset E-RGCH-PowerOffset OPTIONAL, e-HICH-PowerOffset E-HICH-PowerOffset OPTIONAL, additional-EDCH-MAC-d-Flows-Specific-Info-List Additional-EDCH-MAC-d-Flows-Specific-Info-List OPTIONAL, multicellEDCH-RL-SpecificInformation MulticellEDCH-RL-SpecificInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11

921

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-RL-Specific-Information-To-Setup-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Additional-EDCH-Cell-Information-To-Add-List ::= SEQUENCE (SIZE (1.. maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-To-Add-ItemIEs

Additional-EDCH-Cell-Information-To-Add-ItemIEs::=SEQUENCE{ additional-EDCH-UL-DPCH-Information-Setup Additional-EDCH-UL-DPCH-Information-Addition, additional-EDCH-RL-Specific-Information-To-Add-List Additional-EDCH-RL-Specific-Information-To-Add-List, additional-EDCH-FDD-Information Additional-EDCH-FDD-Information OPTIONAL, multicellEDCH-Information MulticellEDCH-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-To-Add-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-To-Add-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-UL-DPCH-Information-Addition ::=SEQUENCE{ ul-SIR-Target UL-SIR, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-UL-DPCH-Information-Addition-ExtIEs} } OPTIONAL, ... } Additional-EDCH-UL-DPCH-Information-Addition-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Additional-EDCH-RL-Specific-Information-To-Add-List ItemIEs ::= SEQUENCE (SIZE (1.. maxNrOfEDCHRLs)) OF Additional-EDCH-RL-Specific-Information-To-Add-

Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, c-ID C-ID, primaryCPICH-EcNo PrimaryCPICH-EcNo OPTIONAL, e-AGCH-PowerOffset E-AGCH-PowerOffset OPTIONAL, e-RGCH-PowerOffset E-RGCH-PowerOffset OPTIONAL, e-HICH-PowerOffset E-HICH-PowerOffset OPTIONAL, additional-EDCH-MAC-d-Flows-Specific-Info-List Additional-EDCH-MAC-d-Flows-Specific-Info-List OPTIONAL, multicellEDCH-RL-SpecificInformation MulticellEDCH-RL-SpecificInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-RL-Specific-Information-To-Add-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
Additional-EDCH-RL-Specific-Information-To-Modify-List ItemIEs

922

3GPP TS 25.423 V11.2.0 (2012-06)

::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF Additional-EDCH-RL-Specific-Information-To-Modify-

Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, e-AGCH-PowerOffset E-AGCH-PowerOffset OPTIONAL, e-RGCH-PowerOffset E-RGCH-PowerOffset OPTIONAL, e-HICH-PowerOffset E-HICH-PowerOffset OPTIONAL, additional-EDCH-MAC-d-Flows-Specific-Info-List Additional-EDCH-MAC-d-Flows-Specific-Info-List OPTIONAL, multicellEDCH-RL-SpecificInformation MulticellEDCH-RL-SpecificInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-RL-Specific-Information-To-Modify-ItemIEs-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-FDD-Information ::=SEQUENCE{ hARQ-Process-Allocation-Scheduled-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH OPTIONAL, e-DCH-Maximum-Bitrate E-DCH-Maximum-Bitrate OPTIONAL, e-DCH-Processing-Overload-Level E-DCH-Processing-Overload-Level OPTIONAL, e-DCH-Min-Set-E-TFCI E-TFCI OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-ExtIEs} } OPTIONAL, ... } Additional-EDCH-FDD-Information-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Additional-EDCH-MAC-d-Flows-Specific-Info-List ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF Additional-EDCH-MAC-d-Flows-Specific-Info Additional-EDCH-MAC-d-Flows-Specific-Info ::= SEQUENCE { e-DCH-MACdFlow-ID EDCH-MACdFlow-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-MAC-d-Flows-Specific-Info-ExtIEs} } OPTIONAL, ... } Additional-EDCH-MAC-d-Flows-Specific-Info-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11

923

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF Additional-EDCH-MAC-d-Flows-SpecificInfo-Response Additional-EDCH-MAC-d-Flows-Specific-Info-Response ::= SEQUENCE { e-DCH-MACdFlow-ID EDCH-MACdFlow-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-MAC-d-Flows-Specific-Info-Response-ExtIEs} } OPTIONAL, ... } Additional-EDCH-MAC-d-Flows-Specific-Info-Response-ExtIEs ... } Additional-EDCH-Cell-Information-Response-List RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Information-Response-ItemIEs

Additional-EDCH-FDD-Information-Response-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-Specific-Information-Response EDCH-Additional-RL-Specific-Information-Response-List, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-Response-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-FDD-Information-Response-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-Additional-RL-Specific-Information-Response-List ItemIEs ::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF EDCH-Additional-RL-Specific-Information-Response-

EDCH-Additional-RL-Specific-Information-Response-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, received-total-wide-band-power Received-total-wide-band-power, dL-PowerBalancing-ActivationIndicator DL-PowerBalancing-ActivationIndicator rL-Set-ID RL-Set-ID, e-DCH-RL-Set-ID RL-Set-ID, eDCH-FDD-DL-ControlChannelInformation EDCH-FDD-DL-ControlChannelInformation, dl-CodeInformation FDD-DL-CodeInformation, additional-EDCH-MAC-d-Flow-Specific-Information-Response-List Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List OPTIONAL, hARQ-Process-Allocation-Scheduled-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH maxUL-SIR UL-SIR, minUL-SIR UL-SIR, maximumAllowedULTxPower MaximumAllowedULTxPower, maximumDL-power DL-Power, minimumDL-power DL-Power, primaryScramblingCode PrimaryScramblingCode uL-UARFCN UARFCN dL-UARFCN UARFCN

OPTIONAL,

OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11

924

3GPP TS 25.423 V11.2.0 (2012-06)

primaryCPICH-Power PrimaryCPICH-Power, pC-Preamble PC-Preamble, primary-CPICH-Usage-For-Channel-Estimation Primary-CPICH-Usage-For-Channel-Estimation OPTIONAL, secondary-CPICH-Information Secondary-CPICH-Information OPTIONAL, f-DPCH-SlotFormat F-DPCH-SlotFormat OPTIONAL, iE-Extensions ProtocolExtensionContainer { { EDCH-Additional-RL-Specific-Information-Response-ItemIEs-ExtIEs} } OPTIONAL, ...

EDCH-Additional-RL-Specific-Information-Response-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Additional-EDCH-Cell-Information-Response-RLReconf-List::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-FDD-Information-Response-RLReconfItems Additional-EDCH-FDD-Information-Response-RLReconf-Items::=SEQUENCE{ eDCH-Additional-RL-Specific-Information-Response EDCH-Additional-RL-Specific-Information-Response-List OPTIONAL, eDCH-Additional-RL-Specific-Modified-Information-Response EDCH-Additional-RL-Specific-Modified-Information-Response-List OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-FDD-Information-Response-RLReconf-Items-ExtIEs} } OPTIONAL, ... } Additional-EDCH-FDD-Information-Response-RLReconf-Items-ExtIEs ... } EDCH-Additional-RL-Specific-Modified-Information-Response-List Information-Response-ItemIEs RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF EDCH-Additional-RL-Specific-Modified-

EDCH-Additional-RL-Specific-Modified-Information-Response-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, dL-PowerBalancing-UpdatedIndicator DL-PowerBalancing-UpdatedIndicator OPTIONAL, eDCH-FDD-DL-ControlChannelInformation EDCH-FDD-DL-ControlChannelInformation OPTIONAL, additional-EDCH-MAC-d-Flow-Specific-Information-Response-List Additional-EDCH-MAC-d-Flow-Specific-Information-Response-List OPTIONAL, hARQ-Process-Allocation-Scheduled-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH OPTIONAL, maxUL-SIR UL-SIR OPTIONAL, minUL-SIR UL-SIR OPTIONAL, maximumDL-power DL-Power OPTIONAL, minimumDL-power DL-Power OPTIONAL, primary-CPICH-Usage-For-Channel-Estimation Primary-CPICH-Usage-For-Channel-Estimation OPTIONAL, secondary-CPICH-Information-Change Secondary-CPICH-Information-Change OPTIONAL, f-DPCH-SlotFormat F-DPCH-SlotFormat OPTIONAL, iE-Extensions ProtocolExtensionContainer { { EDCH-Additional-RL-Specific-Modified-Information-Response-ItemIEs-ExtIEs} } OPTIONAL, ... } EDCH-Additional-RL-Specific-Modified-Information-Response-ItemIEs-ExtIEs ... RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
}

925

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-Cell-Information-ConfigurationChange-List ::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-ConfigurationChange-Info-ItemIEs Additional-EDCH-ConfigurationChange-Info-ItemIEs ::=SEQUENCE{ additional-EDCH-UL-DPCH-Information-Modify Additional-EDCH-UL-DPCH-Information-Modify OPTIONAL, additional-EDCH-RL-Specific-Information-To-Add Additional-EDCH-RL-Specific-Information-To-Add-List OPTIONAL, additional-EDCH-RL-Specific-Information-To-Modify Additional-EDCH-RL-Specific-Information-To-Modify-List OPTIONAL, additional-EDCH-FDD-Information-To-Modify Additional-EDCH-FDD-Information OPTIONAL, additional-EDCH-F-DPCH-Information-Modify Additional-EDCH-F-DPCH-Information OPTIONAL, multicellEDCH-Information MulticellEDCH-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-ConfigurationChange-Info-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-ConfigurationChange-Info-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Additional-EDCH-UL-DPCH-Information-Modify ul-ScramblingCode ul-SIR-Target iE-Extensions ... } ::=SEQUENCE{ UL-ScramblingCode OPTIONAL, UL-SIR OPTIONAL, ProtocolExtensionContainer { { Additional-EDCH-UL-DPCH-Information-Modify-ExtIEs} } OPTIONAL,

Additional-EDCH-UL-DPCH-Information-Modify-ExtIEs ... } Additional-EDCH-Cell-Information-Removal-List

RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Cell-Information-Removal-Info-ItemIEs

Additional-EDCH-Cell-Information-Removal-Info-ItemIEs ::=SEQUENCE{ rL-on-Secondary-UL-Frequency RL-on-Secondary-UL-Frequency, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Cell-Information-Removal-Info-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Cell-Information-Removal-Info-ItemIEs-ExtIEs ... } RL-on-Secondary-UL-Frequency ::= ENUMERATED { remove, ... } Additional-EDCH-FDD-Update-Information ::=SEQUENCE{ hARQ-Process-Allocation-Scheduled-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH additional-EDCH-DL-Control-Channel-Change-Information Additional-EDCH-DL-Control-Channel-Change-Information-List iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-FDD-Update-Information-ExtIEs} } OPTIONAL, ... OPTIONAL, OPTIONAL, RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} Additional-EDCH-FDD-Update-Information-ExtIEs ... }

926
RNSAP-PROTOCOL-EXTENSION ::= {

3GPP TS 25.423 V11.2.0 (2012-06)

Additional-EDCH-DL-Control-Channel-Change-Information-List ItemIEs

::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF Additional-EDCH-DL-Control-Channel-Change-Info-

Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs ::=SEQUENCE{ eDCH-Additional-RL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-DL-Control-Channel-Change-Info-ItemIEs-ExtIEs ... } AdditionalPreferredFrequency RNSAP-PROTOCOL-EXTENSION ::= {

::= SEQUENCE (SIZE (1..maxNrOfAddFreq)) OF AdditionalPreferredFrequencyItem

AdditionalPreferredFrequencyItem ::= SEQUENCE { dL-UARFCN UARFCN, correspondingCells CorrespondingCells , iE-Extensions ProtocolExtensionContainer { { AdditionalPreferredFrequencyItem-ExtIEs} } OPTIONAL, ... } AdditionalPreferredFrequencyItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } AdjustmentPeriod -- Unit Frame ::= INTEGER(1..256) ::= SEQUENCE (SIZE (1..maxNrOfUEs)) OF S-RNTI

AffectedUEInformationForMBMS

AllocationRetentionPriority ::= SEQUENCE { priorityLevel PriorityLevel, pre-emptionCapability Pre-emptionCapability, pre-emptionVulnerability Pre-emptionVulnerability, iE-Extensions ProtocolExtensionContainer { {AllocationRetentionPriority-ExtIEs} } OPTIONAL, ... } AllocationRetentionPriority-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
Allowed-Rate-Information allowed-UL-Rate allowed-DL-Rate iE-Extensions ... }

927
::= SEQUENCE { Allowed-Rate OPTIONAL, Allowed-Rate OPTIONAL, ProtocolExtensionContainer { {Allowed-Rate-Information-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

Allowed-Rate-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Allowed-Rate ::= INTEGER (1..maxNrOfTFs) -- 1: TFI 0, 2: TFI 1, 3: TFI 2, ... AllowedQueuingTime -- seconds ::= INTEGER (1..60)

AlphaValue ::= INTEGER (0..8) -- Actual value = Alpha / 8 AlternativeFormatReportingIndicator ::= ENUMERATED { alternativeFormatAllowed,... } Angle-Of-Arrival-Value-LCR ::= SEQUENCE { aOA-LCR AOA-LCR, aOA-LCR-Accuracy-Class AOA-LCR-Accuracy-Class, iE-Extensions ProtocolExtensionContainer { {Angle-Of-Arrival-Value-LCR-ExtIEs} } OPTIONAL, ... } Angle-Of-Arrival-Value-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ANR-Cell-Information ::= SEQUENCE { rNC-ID RNC-ID, lAC LAC OPTIONAL, rAC RAC OPTIONAL, aNR-FDD-CellInformation ANR-FDD-CellInformation OPTIONAL, aNR-TDD-CellInformation ANR-TDD-CellInformation OPTIONAL, aNR-LCR-TDD-CellInformation ANR-LCR-TDD-CellInformation OPTIONAL, extended-RNC-ID Extended-RNC-ID OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ANR-Cell-Information-ExtIEs} } OPTIONAL, ... } ANR-Cell-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
ANR-FDD-CellInformation ::= SEQUENCE { primaryCPICH-Power txDiversityIndicator sTTD-SupportIndicator closedLoopMode1-SupportIndicator restrictionStateIndicator dpc-ModeChangeSupportIndicator cellCapabilityContainerFDD sNA-Information frequencyBandIndicator max-UE-DTX-Cycle aNR-Multiple-PLMN-List secondaryServingCellList dualBandSecondaryServingCellList cellCapabilityContainerExtensionFDD iE-Extensions ... }

928

3GPP TS 25.423 V11.2.0 (2012-06)

PrimaryCPICH-Power OPTIONAL, TxDiversityIndicator, STTD-SupportIndicator OPTIONAL, ClosedLoopMode1-SupportIndicator OPTIONAL, RestrictionStateIndicator OPTIONAL, DPC-Mode-Change-SupportIndicator OPTIONAL, CellCapabilityContainer-FDD OPTIONAL, SNA-Information OPTIONAL, FrequencyBandIndicator OPTIONAL, Max-UE-DTX-Cycle OPTIONAL, ANR-Multiple-PLMN-List OPTIONAL, Secondary-Serving-Cell-List OPTIONAL, Secondary-Serving-Cell-List OPTIONAL, CellCapabilityContainerExtension-FDD OPTIONAL, ProtocolExtensionContainer { { ANR-FDD-CellInformation-ExtIEs} } OPTIONAL,

ANR-FDD-CellInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ANR-TDD-CellInformation ::= SEQUENCE { syncCase SyncCase, timeSlot TimeSlot OPTIONAL -- This IE shall be present if Sync Case = Case1 -- , sCH-TimeSlot SCH-TimeSlot OPTIONAL -- This IE shall be present if Sync Case = Case2 -- , sCTD-Indicator SCTD-Indicator, dPCHConstantValue DPCHConstantValue OPTIONAL, pCCPCH-Power PCCPCH-Power OPTIONAL, restrictionStateIndicator RestrictionStateIndicator OPTIONAL, cellCapabilityContainerTDD CellCapabilityContainer-TDD OPTIONAL, -- Applicable to 3.84Mcps TDD only cellCapabilityContainerTDD768 CellCapabilityContainer-TDD768 OPTIONAL, -- Applicable to 7.68Mcps TDD only sNA-Information SNA-Information OPTIONAL, aNR-Multiple-PLMN-List ANR-Multiple-PLMN-List OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ANR-TDD-CellInformation-ExtIEs} } OPTIONAL, ... } ANR-TDD-CellInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ANR-LCR-TDD-CellInformation ::= SEQUENCE {

3GPP

Release 11
sCTD-Indicator dPCHConstantValue pCCPCH-Power restrictionStateIndicator cellCapabilityContainerTDD-LCR -- Applicable to 1.28Mcps TDD only sNA-Information aNR-Multiple-PLMN-List cellCapabilityContainerExternsionTDD-LCR iE-Extensions ...

929
SCTD-Indicator, DPCHConstantValue PCCPCH-Power RestrictionStateIndicator CellCapabilityContainer-TDD-LCR OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

SNA-Information OPTIONAL, ANR-Multiple-PLMN-List OPTIONAL, CellCapabilityContainerExtension-TDD-LCR OPTIONAL, ProtocolExtensionContainer { { ANR-LCR-TDD-CellInformation-ExtIEs} } OPTIONAL,

ANR-LCR-TDD-CellInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

ANR-Multiple-PLMN-List ::= SEQUENCE { list-Of-PLMNs List-Of-PLMNs OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ANR-Multiple-PLMN-List-ExtIEs} } OPTIONAL, ... } ANR-Multiple-PLMN-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } AOA-LCR ::= INTEGER (0..719) -- Angle Of Arrival for 1.28Mcps TDD AOA-LCR-Accuracy-Class ::= ENUMERATED {a,b,c,d,e,f,g,h,...}

AntennaColocationIndicator ::= ENUMERATED { co-located, ... } -- B BadSatellites ::= SEQUENCE { badSatelliteInformation SEQUENCE { badSAT-ID iE-Extensions ... }, iE-Extensions ... SEQUENCE (SIZE (1..maxNoSat)) OF SAT-ID, ProtocolExtensionContainer { { BadSatelliteInformation-ExtIEs} } ProtocolExtensionContainer { { BadSatellites-ExtIEs} } OPTIONAL, OPTIONAL,

3GPP

Release 11
} BadSatelliteInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } BadSatellites-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Band-Indicator ::= ENUMERATED { dcs1800Band, pcs1900Band, ... } BCC ::= BIT STRING (SIZE (3)) BCCH-ARFCN ::= INTEGER (0..1023) BetaCD ::= INTEGER (0..15)

930

3GPP TS 25.423 V11.2.0 (2012-06)

BindingID ::= OCTET STRING (SIZE (1..4,...)) -- If the Binding ID includes an UDP port, the UDP port is included in octet 1 and 2. BLER ::= INTEGER (-63..0) -- Step 0.1 (Range -6.3..0). It is the Log10 of the BLER SCTD-Indicator active, inactive } ::= ENUMERATED {

BSIC ::= SEQUENCE { nCC NCC, bCC BCC } BundlingModeIndicator ::= ENUMERATED { bundling, no-bundling } BurstModeParameters burstStart burstLength burstFreq iE-Extensions ... } ::= SEQUENCE { INTEGER (0..15), INTEGER (10..25), INTEGER (1..16), ProtocolExtensionContainer { { BurstModeParameters-ExtIEs} }

OPTIONAL,

3GPP

Release 11
BurstModeParameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- C Cause ::= CHOICE { radioNetwork transport protocol misc ... } CauseRadioNetwork, CauseTransport, CauseProtocol, CauseMisc,

931

3GPP TS 25.423 V11.2.0 (2012-06)

CauseMisc ::= ENUMERATED { control-processing-overload, hardware-failure, om-intervention, not-enough-user-plane-processing-resources, unspecified, ... } CauseProtocol ::= ENUMERATED { transfer-syntax-error, abstract-syntax-error-reject, abstract-syntax-error-ignore-and-notify, message-not-compatible-with-receiver-state, semantic-error, unspecified, abstract-syntax-error-falsely-constructed-message, ... } CauseRadioNetwork ::= ENUMERATED { unknown-C-ID, cell-not-available, power-level-not-supported, ul-scrambling-code-already-in-use, dl-radio-resources-not-available, ul-radio-resources-not-available, measurement-not-supported-for-the-object, combining-resources-not-available, combining-not-supported, reconfiguration-not-allowed, requested-configuration-not-supported, synchronisation-failure, requested-tx-diversity-mode-not-supported, measurement-temporaily-not-available, unspecified, invalid-CM-settings,

3GPP

Release 11
reconfiguration-CFN-not-elapsed, number-of-DL-codes-not-supported, dedicated-transport-channel-type-not-supported, dl-shared-channel-type-not-supported, ul-shared-channel-type-not-supported, common-transport-channel-type-not-supported, ul-spreading-factor-not-supported, dl-spreading-factor-not-supported, cm-not-supported, transaction-not-supported-by-destination-node-b, rl-already-activated-or-alocated, ..., number-of-UL-codes-not-supported, cell-reserved-for-operator-use, dpc-mode-change-not-supported, information-temporarily-not-available, information-provision-not-supported-for-the-object, power-balancing-status-not-compatible, delayed-activation-not-supported, rl-timing-adjustment-not-supported, unknown-RNTI, measurement-repetition-rate-not-compatible, ue-not-capable-of-support, f-dpch-not-supported, e-dch-not-supported, continuous-packet-connectivity-dtx-drx-operation-not-supported, continuous-packet-connectivity-hs-scch-less-operation-not-supported, mimo-not-supported, e-dch-tti2ms-not-supported, continuous-packet-connectivity-DTX-DRX-operation-not-available, continuous-packet-connectivity-UE-DTX-Cycle-not-available, mimo-not-available, sixteenQAM-UL-not-Supported, hSDSCH-MACdPDU-SizeFormatNotSupported, f-dpch-slot-format-operation-not-supported, e-DCH-MACdPDU-SizeFormat-not-available, e-DPCCH-Power-Boosting-not-supported, trelocprep-expiry, directed-retry, no-Iu-CS-UP-relocation, reduce-load-in-serving-cell, relocation-cancelled, relocation-desirable-for-radio-reasons, resource-optimisation-relocation, time-critical-relocation, traffic-load-in-the-target-cell-higher-than-in-the-source-cell, sixtyfourQAM-DL-and-MIMO-Combined-not-available, multi-Cell-operation-not-available, multi-Cell-operation-not-supported, semi-Persistent-scheduling-not-supported, continuous-Packet-Connectivity-DRX-not-supported,

932

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11

933

3GPP TS 25.423 V11.2.0 (2012-06)

continuous-Packet-Connectivity-DRX-not-available, enhanced-relocation-not-supported, relocation-not-supported-due-to-PUESBINE-feature, relocation-failure-in-target-RNC, relocation-target-not-allowed, requested-ciphering-and-or-integrity-protection-algorithms-not-supported, sixtyfourQAM-DL-and-MIMO-Combined-not-supported, tx-diversity-for-mimo-on-DL-control-channels-not-available, single-Stream-MIMO-not-supported, single-Stream-MIMO-not-available, multi-Cell-operation-with-MIMO-not-supported, multi-Cell-operation-with-MIMO-not-available, multi-Cell-EDCH-operation-not-supported, multi-Cell-EDCH-operation-not-available, multi-Cell-operation-with-Single-Stream-MIMO-not-supported, multi-Cell-operation-with-Single-Stream-MIMO-not-available, cellSpecificTxDiversityHandlingForMultiCellOperationNotAvailable, cellSpecificTxDiversityHandlingForMultiCellOperationNotSupported, frequencySpecificCompressedModeNotAvailable } CauseTransport ::= ENUMERATED { transport-resource-unavailable, unspecified, ... } CellBased::= SEQUENCE { cellIdList CellIdList, iE-Extensions ProtocolExtensionContainer { {CellBased-ExtIEs} } OPTIONAL, ... } CellBased-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CellIdList ::= SEQUENCE (SIZE (1..maxNrOfCellIds)) OF Cell-Id Cell-Id ::= INTEGER (0..268435455)

CellCapabilityContainer-FDD ::= BIT STRING (SIZE (32)) -- First bit: Flexible Hard Split Support Indicator -- Second bit: Delayed Activation Support Indicator -- Third bit: HS-DSCH Support Indicator -- Fourth bit: DSCH Support Indicator -- Fifth bit: F-DPCH Support Indicator -- sixth bit: E-DCH Support Indicator

3GPP

Release 11
--------------------------

934

3GPP TS 25.423 V11.2.0 (2012-06)

Seventh bit: E-DCH TTI2ms Support Indicator Eighth bit: E-DCH 2sf2and2sf4 and all inferior SFs Support Indicator Ninth bit: E-DCH 2sf2 and all inferior SFs Support Indicator Tenth bit: E-DCH 2sf4 and all inferior SFs Support Indicator Eleventh bit: E-DCH sf4 and all inferior SFs Support Indicator Twelveth bit: E-DCH sf8 and all inferior SFs Support Indicator Thirteenth bit: E-DCH HARQ IR Combining Support Indicator Fourteenth bit: E-DCH HARQ Chase Combining Support Indicator Fifteenth bit: Continuous Packet Connectivity DTX-DRX Support Indicator Sixteenth bit: Continuous Packet Connectivity HS-SCCH less Support Indicator Seventeenth bit: MIMO Support Indicator Eighteenth bit: SixteenQAM UL Support Indicator Nineteenth bit: Flexible MAC-d PDU Size Support Indicator Twentieth bit: F-DPCH Slot Format Support Indicator Twentyfirst bit: SixtyfourQAM DL Support Indicator Twentysecond bit: Flexible E-DCH MAC-d PDU Size Support Indicator Twentythird bit: E-DPCCH Power Boosting Support Indicator Twentyfourth bit: SixtyfourQAM DL and MIMO Combined Support Indicator Twentyfifth bit: Multi Cell Support Indicator Support Indicator Twentysixth bit: MBMS Support Indicator Twentyseventh bit: DRNS Support STTD on DL ctrl ch when the RL is in MIMO P-CPICH + S-CPICH cell Twentyeighth bit: Dual Band Support Indicator Twentyninth bit: Single Stream MIMO Support Indicator Thirtieth bit: Preferred Precoding Weight Set Restriction Support Indicator Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver.

CellCapabilityContainerExtension-FDD ::= BIT STRING (SIZE (128)) -- First bit: Cell Specific Tx Diversity Handling For Multi Cell Operation Support Indicator -- Second bit: Multi Cell and MIMO Support Indicator -- Third bit: Multi Cell and Single Stream MIMO Support Indicator -- Fourth bit: Multi Cell E-DCH Support Indicator -- Fifth bit: Separate Iub Transport Bearer Support Indicator -- Sixth bit: E-DCH UL Flow Multiplexing Support Indicator -- Seventh to eleventh bit: Maximum No of HSDPA Frequencies Support Indicator -- Twelfth bit: Dual Band and MIMO Support Indicator -- Thirteenth bit: 3 or more carrier HSDPA and MIMO Single Band Support Indicator -- Fourteenth bit: 3 or more carrier HSDPA and MIMO Dual Band Support Indicator -- Fifteenth bit : Dual Band and Single Stream MIMO Support Indicator -- Sixteenth bit : 3 or more carrier HSDPA and Single Stream MIMO Single Band Support Indicator -- Seventeenth bit : 3 or more carrier HSDPA and Single Stream MIMO Dual Band Support Indicator -- Eighteenth bit: Frequency specific Compressed Mode Support Indicator -- Nineteenth bit: UL CLTD Capability -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. CellCapabilityContainer-TDD ::= BIT STRING (SIZE (32)) -- First bit: Delayed Activation Support Indicator -- Second bit: HS-DSCH Support Indicator -- Third bit: DSCH Support Indicator -- The fourth bit: Flexible MAC-d PDU Size Support Indicator

3GPP

Release 11

935

3GPP TS 25.423 V11.2.0 (2012-06)

-- Fifth bit: MBMS Support Indicator -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. CellCapabilityContainer-TDD-LCR ::= BIT STRING (SIZE (32)) -- First bit: Delayed Activation Support Indicator -- Second bit: HS-DSCH Support Indicator -- Third bit: DSCH Support Indicator -- The fourth bit: Flexible MAC-d PDU Size Support Indicator -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. CellCapabilityContainerExtension-TDD-LCR ::= BIT STRING (SIZE (32)) -- First bit: Multi-Carrier E-DCH Operation Support Indicator -- Second bit: Separate Iur Transport Bearer Support Indicator -- Third bit: E-DCH UL flow Multiplexing Support Indicator -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. CellCapabilityContainer-TDD768 ::= BIT STRING (SIZE (32)) -- First bit: Delayed Activation Support Indicator -- Second bit: HS-DSCH Support Indicator -- Third bit: DSCH Support Indicator -- The fourth bit: Flexible MAC-d PDU Size Support Indicator -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. C-ID CCTrCH-ID ::= INTEGER (0..65535) ::= INTEGER (0..15) INTEGER(1..100,...), INTEGER(1..100,...)

Cell-Capacity-Class-Value ::= SEQUENCE { uplinkCellCapacityClassValue downlinkCellCapacityClassValue } CellIndividualOffset

::= INTEGER (-20..20)

CellListValidityIndicator ::= ENUMERATED { ignoreSecondaryServingCellList, ignoreDualBandSecondaryServingCellList, ignoreBoth } CellParameterID CellPortionID ::= INTEGER (0..127,...) ::= INTEGER (0..63,...) ::= INTEGER (0..255,...) ::= INTEGER (0..255) LAI,

CellPortionLCRID CFN CGI ::= SEQUENCE { lAI

3GPP

Release 11
cI iE-Extensions } LAI-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CGI-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ChannelCodingType ::= ENUMERATED { no-codingTDD, convolutional-coding, turbo-coding, ... } ChipOffset CI ::= INTEGER (0..38399) ::= OCTET STRING (SIZE (2)) ::= OCTET STRING ::= OCTET STRING ::= ENUMERATED { CI, ProtocolExtensionContainer { {CGI-ExtIEs} } OPTIONAL

936

3GPP TS 25.423 V11.2.0 (2012-06)

ClassmarkInformation2 ClassmarkInformation3

ClosedLoopMode1-SupportIndicator closedLoop-Mode1-Supported, closedLoop-Mode1-not-Supported } Closedlooptimingadjustmentmode adj-1-slot, adj-2-slot, ... } CodingRate ::= ENUMERATED { half, third, ... }

::= ENUMERATED {

CommonMeasurementAccuracy ::= CHOICE { tUTRANGPSMeasurementAccuracyClass ..., tUTRANGANSSMeasurementAccuracyClass }

TUTRANGPSAccuracyClass, TUTRANGANSSAccuracyClass

3GPP

Release 11

937

3GPP TS 25.423 V11.2.0 (2012-06)

CommonMeasurementType ::= ENUMERATED { uTRAN-GPS-timing-of-cell-frames-for-UE-Positioning, sFN-SFN-observerd-time-difference, load, transmitted-carrier-power, received-total-wide-band-power, uplink-timeslot-iscp, ..., rT-load, nRT-load-Information, upPTSInterference, uTRAN-GANSS-timing-of-cell-frames-for-UE-Positioning } -- For measurements on the Iur-g interface, only load, RT Load and NRT Load information are requested. CommonMeasurementValue ::= CHOICE { tUTRANGPSMeasurementValueInformation sFNSFNMeasurementValueInformation loadValue transmittedCarrierPowerValue receivedTotalWideBandPowerValue uplinkTimeslotISCPValue ..., extension-CommonMeasurementValue } Extension-CommonMeasurementValue TUTRANGPSMeasurementValueInformation, SFNSFNMeasurementValueInformation, LoadValue, INTEGER(0..100), INTEGER(0..621), UL-TimeslotISCP, Extension-CommonMeasurementValue

::= ProtocolIE-Single-Container {{ Extension-CommonMeasurementValueIE }} ignore ignore reject reject TYPE RTLoadValue TYPE NRTLoadInformationValue TYPE UpPTSInterferenceValue TYPE TUTRANGANSSMeasurementValueInformation PRESENCE mandatory } PRESENCE

Extension-CommonMeasurementValueIE RNSAP-PROTOCOL-IES ::= { { ID id-RTLoadValue CRITICALITY PRESENCE mandatory }| { ID id-NRTLoadInformationValue CRITICALITY mandatory }| { ID id-UpPTSInterferenceValue CRITICALITY PRESENCE mandatory }| { ID id-TUTRANGANSSMeasurementValueInformation CRITICALITY }

-- For measurements on the Iur-g interface, only load, RT Load and NRT Load values are reported. CommonMeasurementValueInformation ::= CHOICE { measurementAvailable CommonMeasurementAvailable, measurementnotAvailable NULL } CommonMeasurementAvailable::= SEQUENCE { commonMeasurementValue CommonMeasurementValue, iE-Extensions ProtocolExtensionContainer { { CommonMeasurementAvailableItem-ExtIEs} } ... }

OPTIONAL,

3GPP

Release 11
CommonMeasurementAvailableItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CongestionCause ::= ENUMERATED { uTRAN-dynamic-resources, uTRAN-semistatic-resources, ... } CommonTransportChannelResourcesInitialisationNotRequired ::= ENUMERATED { not-Required }

938

3GPP TS 25.423 V11.2.0 (2012-06)

Common-EDCH-MAC-d-Flow-Specific-InformationFDD ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF Common-EDCH-MAC-d-Flow-Specific-InformationFDDItem Common-EDCH-MAC-d-Flow-Specific-InformationFDDItem ::= SEQUENCE { common-EDCH-MACdFlow-ID EDCH-MACdFlow-ID, maximum-Number-of-Retransmissions-For-E-DCH MaxNr-Retransmissions-EDCH, eDCH-HARQ-PO-FDD E-DCH-HARQ-PO-FDD, eDCH-MACdFlow-Multiplexing-List E-DCH-MACdFlow-Multiplexing-List OPTIONAL, common-E-DCHLogicalChannelInformation Common-E-DCH-LogicalChannelInformation, iE-Extensions ProtocolExtensionContainer { { Common-EDCH-MAC-d-Flow-Specific-InformationFDDItem-ExtIEs} } OPTIONAL, ... } Common-EDCH-MAC-d-Flow-Specific-InformationFDDItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Common-EDCH-MAC-d-Flow-Specific-InformationLCR ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlowsLCR)) OF Common-EDCH-MAC-d-Flow-Specific-InformationItemLCR Common-EDCH-MAC-d-Flow-Specific-InformationItemLCR ::= SEQUENCE { common-EDCH-MACdFlow-ID-LCR EDCH-MACdFlow-ID-LCR, maximum-Number-of-Retransmissions-For-E-DCH MaxNr-Retransmissions-EDCH, eDCH-HARQ-PO-TDD E-DCH-HARQ-PO-TDD, eDCH-MACdFlow-Multiplexing-List E-DCH-MACdFlow-Multiplexing-List OPTIONAL, common-E-DCHLogicalChannelInformation Common-E-DCH-LogicalChannelInformation, iE-Extensions ProtocolExtensionContainer { { Common-EDCH-MAC-d-Flow-Specific-InformationItemLCR-ExtIEs} } OPTIONAL, ... } Common-EDCH-MAC-d-Flow-Specific-InformationItemLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Common-E-DCH-LogicalChannelInformation ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF Common-E-DCH-LogicalChannelInformationItem

3GPP

Release 11

939

3GPP TS 25.423 V11.2.0 (2012-06)

Common-E-DCH-LogicalChannelInformationItem ::= SEQUENCE { logicalChannelId LogicalChannelID, maximumMACdPDU-SizeExtended MAC-PDU-SizeExtended, iE-Extensions ProtocolExtensionContainer { { Common-E-DCH-LogicalChannelInformationItem-ExtIEs } } ... } Common-E-DCH-LogicalChannelInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Common-EDCH-Support-Indicator ::= NULL CompleteAlmanacProvided ::= BOOLEAN Continuous-Packet-Connectivity-DTX-DRX-Information ::= SEQUENCE { uE-DTX-DRX-Offset UE-DTX-DRX-Offset, enabling-Delay Enabling-Delay, dTX-Information DTX-Information, dRX-Information DRX-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Continuous-Packet-Connectivity-DTX-DRX-Information-ExtIEs } } OPTIONAL, ... } Continuous-Packet-Connectivity-DTX-DRX-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

Continuous-Packet-Connectivity-DTX-DRX-Information-to-Modify ::= SEQUENCE { uE-DTX-DRX-Offset UE-DTX-DRX-Offset OPTIONAL, enabling-Delay Enabling-Delay OPTIONAL, dTX-Information-to-Modify DTX-Information-to-Modify OPTIONAL, dRX-Information-to-Modify DRX-Information-to-Modify OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Continuous-Packet-Connectivity-DTX-DRX-Information-to-Modify-ExtIEs } } OPTIONAL, ... } Continuous-Packet-Connectivity-DTX-DRX-Information-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Continuous-Packet-Connectivity-HS-SCCH-Less-Information ::= SEQUENCE (SIZE (1..maxNrOfHS-DSCHTBSs-HS-SCCHless)) OF Continuous-Packet-Connectivity-HSSCCH-Less-InformationItem Continuous-Packet-Connectivity-HS-SCCH-Less-InformationItem ::= SEQUENCE { transport-Block-Size-Index Transport-Block-Size-Index, hSPDSCH-Second-Code-Support HSPDSCH-Second-Code-Support,

3GPP

Release 11
iE-Extensions OPTIONAL, ...

940

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { Continuous-Packet-Connectivity-HS-SCCH-Less-InformationItem-ExtIEs } }

Continuous-Packet-Connectivity-HS-SCCH-Less-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response ::= SEQUENCE { hSPDSCH-First-Code-Index HSPDSCH-First-Code-Index, hSPDSCH-Second-Code-Index HSPDSCH-Second-Code-Index OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response-ExtIEs } } OPTIONAL, ... } Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CorrespondingCells ::= SEQUENCE (SIZE (1..maxNrOfCellsPerFreq)) OF C-ID

CoverageIndicator ::= ENUMERATED { overlap, covers, containedIn, ... }

CPC-Information ::= SEQUENCE { continuous-Packet-Connectivity-DTX-DRX-Information OPTIONAL, continuous-Packet-Connectivity-DTX-DRX-Information-to-Modify OPTIONAL, continuous-Packet-Connectivity-HS-SCCH-Less-Information OPTIONAL, iE-Extensions OPTIONAL, ... }

Continuous-Packet-Connectivity-DTX-DRX-Information Continuous-Packet-Connectivity-DTX-DRX-Information-to-Modify Continuous-Packet-Connectivity-HS-SCCH-Less-Information ProtocolExtensionContainer { { CPC-Information-ExtIEs} }

CPC-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Deactivate-Indicator CRITICALITY reject Packet-Connectivity-HS-SCCH-less-Deactivate-Indicator PRESENCE optional}, ... }

EXTENSION Continuous-

3GPP

Release 11
CPC-RecoveryReport ::= ENUMERATED { initiated, ... } Continuous-Packet-Connectivity-HS-SCCH-less-Deactivate-Indicator ::= NULL

941

3GPP TS 25.423 V11.2.0 (2012-06)

Counting-Information ::= SEQUENCE ( SIZE (1..maxNrOfFDDNeighboursPerRNC,...)) OF Counting-Information-List Counting-Information-List ::= SEQUENCE { c-ID C-ID, counting-Result Counting-Result, iE-Extensions ProtocolExtensionContainer { { Counting-Information-List-ExtIEs} } OPTIONAL, ... } Counting-Information-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Counting-Result ::= INTEGER (0..63) CRC-Size v0, v8, v12, v16, v24, ... } ::= ENUMERATED {

CriticalityDiagnostics ::= SEQUENCE procedureID triggeringMessage procedureCriticality transactionID iEsCriticalityDiagnostics iE-Extensions ... }

{ ProcedureID OPTIONAL, TriggeringMessage OPTIONAL, Criticality OPTIONAL, TransactionID OPTIONAL, CriticalityDiagnostics-IE-List OPTIONAL, ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,

CriticalityDiagnostics-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF SEQUENCE { iECriticality Criticality, iE-ID ProtocolIE-ID, repetitionNumber RepetitionNumber0 OPTIONAL,

3GPP

Release 11
iE-Extensions ... }

942
ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

CriticalityDiagnostics-IE-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MessageStructure CRITICALITY ignore EXTENSION MessageStructure { ID id-TypeOfError CRITICALITY ignore EXTENSION TypeOfError ... }

PRESENCE optional PRESENCE mandatory

}| },

MessageStructure ::= SEQUENCE (SIZE (1..maxNrOfLevels)) OF SEQUENCE { iE-ID ProtocolIE-ID, repetitionNumber RepetitionNumber1 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {MessageStructure-ExtIEs} } OPTIONAL, ... } MessageStructure-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CN-CS-DomainIdentifier ::= SEQUENCE { pLMN-Identity PLMN-Identity, lAC LAC, iE-Extensions ProtocolExtensionContainer { {CN-CS-DomainIdentifier-ExtIEs} } OPTIONAL } CN-CS-DomainIdentifier-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CN-PS-DomainIdentifier ::= SEQUENCE { pLMN-Identity PLMN-Identity, lAC LAC, rAC RAC, iE-Extensions ProtocolExtensionContainer { {CN-PS-DomainIdentifier-ExtIEs} } OPTIONAL } CN-PS-DomainIdentifier-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } CNDomainType ::= ENUMERATED { cs-domain, ps-domain, i-care, ... } -- See in TS 25.331 [16]

3GPP

Release 11

943

3GPP TS 25.423 V11.2.0 (2012-06)

CQI-DTX-Timer ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity} -- Unit subframe ControlGAP ::= INTEGER (1..255) CQI-Feedback-Cycle ::= ENUMERATED {v0, v2, v4, v8, v10, v20, v40, v80, v160,..., v16, v32, v64} CQI-Power-Offset ::= INTEGER (0..8,...) -- According to mapping in TS 25.213 [21] subclause 4.2.1 CQI-RepetitionFactor ::= INTEGER (1..4,...) -- Step: 1 C-RNTI ::= INTEGER (0..65535)

CodeRate ::= INTEGER (0..63) CodeRate-short ::= INTEGER (0..10) CPC-InformationLCR ::= SEQUENCE { continuousPacketConnectivity-DRX-InformationLCR OPTIONAL, continuousPacketConnectivity-DRX-Information-to-Modify-LCR hS-DSCH-Semi-PersistentScheduling-Information-LCR OPTIONAL, hS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR hS-DSCH-SPS-Deactivate-Indicator-LCR e-DCH-Semi-PersistentScheduling-Information-LCR OPTIONAL, e-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR e-DCH-SPS-Deactivate-Indicator-LCR iE-Extensions ... } CPC-InformationLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContinuousPacketConnectivity-DRX-InformationLCR ::= SEQUENCE { enabling-Delay Enabling-Delay, hS-SCCH-DRX-Information-LCR HS-SCCH-DRX-Information-LCR, e-AGCH-DRX-Information-LCR E-AGCH-DRX-Information-LCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-InformationLCR-ExtIEs } } ... } ContinuousPacketConnectivity-DRX-InformationLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContinuousPacketConnectivity-DRX-InformationLCR ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR HS-DSCH-Semi-PersistentScheduling-Information-LCR HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR NULL OPTIONAL, E-DCH-Semi-PersistentScheduling-Information-LCR E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR NULL OPTIONAL, ProtocolExtensionContainer { { CPC-InformationLCR-ExtIEs} } OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL,

OPTIONAL,

3GPP

Release 11

944

3GPP TS 25.423 V11.2.0 (2012-06)

HS-SCCH-DRX-Information-LCR ::= SEQUENCE { hS-SCCH-UE-DRX-Cycle-LCR UE-DRX-Cycle-LCR, hS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR Inactivity-Threshold-for-UE-DRX-Cycle-LCR hS-SCCH-UE-DRX-Offset-LCR UE-DRX-Offset-LCR, iE-Extensions ProtocolExtensionContainer { { HS-SCCH-DRX-Information-LCR-ExtIEs} } OPTIONAL, ... } HS-SCCH-DRX-Information-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext PRESENCE optional }, ... } E-AGCH-DRX-Information-LCR ::= CHOICE { sameAsHS-SCCH NULL, e-AGCH-DRX-Parameters E-AGCH-DRX-Parameters, ... } E-AGCH-DRX-Parameters ::= SEQUENCE { e-AGCH-UE-DRX-Cycle-LCR e-AGCH-UE-Inactivity-Monitor-Threshold e-AGCH-UE-DRX-Offset-LCR iE-Extensions ... } CRITICALITY ignore

OPTIONAL,

EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext

UE-DRX-Cycle-LCR, E-AGCH-UE-Inactivity-Monitor-Threshold OPTIONAL, UE-DRX-Offset-LCR, ProtocolExtensionContainer { { E-AGCH-DRX-Parameters-ExtIEs} } OPTIONAL,

E-AGCH-DRX-Parameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UE-DRX-Cycle-LCR ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64,...} -- Unit subframe UE-DRX-Offset-LCR ::= INTEGER (0..63) -- Unit subframe Inactivity-Threshold-for-UE-DRX-Cycle-LCR ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64,...} -- Unit subframe Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext ::= ENUMERATED {v128, v256, v512,...} -- Unit subframe E-AGCH-UE-Inactivity-Monitor-Threshold ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity,...} -- Unit subframe ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR ::= SEQUENCE { enabling-Delay Enabling-Delay dRX-Information-to-Modify-LCR DRX-Information-to-Modify-LCR

OPTIONAL, OPTIONAL,

3GPP

Release 11
iE-Extensions OPTIONAL, ...

945

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR-ExtIEs } }

ContinuousPacketConnectivity-DRX-Information-to-Modify-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DRX-Information-to-Modify-LCR ::= CHOICE { modify DRX-Information-to-Modify-Items-LCR, deactivate NULL, ... } DRX-Information-to-Modify-Items-LCR ::= SEQUENCE { hS-SCCH-DRX-Information-LCR HS-SCCH-DRX-Information-LCR OPTIONAL, e-AGCH-DRX-Information-LCR E-AGCH-DRX-Information-LCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DRX-Information-to-Modify-Items-LCR-ExtIEs} } OPTIONAL, ... } DRX-Information-to-Modify-Items-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ContinuousPacketConnectivity-DRX-Information-ResponseLCR ::= SEQUENCE { enabling-Delay Enabling-Delay OPTIONAL, hS-SCCH-DRX-Information-ResponseLCR HS-SCCH-DRX-Information-ResponseLCR OPTIONAL, e-AGCH-DRX-Information-ResponseLCR E-AGCH-DRX-Information-ResponseLCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ContinuousPacketConnectivity-DRX-Information-ResponseLCR-ExtIEs } } OPTIONAL, ... } ContinuousPacketConnectivity-DRX-Information-ResponseLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-SCCH-DRX-Information-ResponseLCR ::= SEQUENCE { hS-SCCH-UE-DRX-Cycle-LCR UE-DRX-Cycle-LCR OPTIONAL, hS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR Inactivity-Threshold-for-UE-DRX-Cycle-LCR OPTIONAL, hS-SCCH-UE-DRX-Offset-LCR UE-DRX-Offset-LCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HS-SCCH-DRX-Information-ResponseLCR-ExtIEs} } OPTIONAL, ... } HS-SCCH-DRX-Information-ResponseLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext CRITICALITY ignore PRESENCE optional }, ... EXTENSION Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext

3GPP

Release 11
} E-AGCH-DRX-Information-ResponseLCR ::= CHOICE { sameAsHS-SCCH NULL, e-AGCH-DRX-Parameters-Response E-AGCH-DRX-Parameters-Response, ... } E-AGCH-DRX-Parameters-Response ::= SEQUENCE { e-AGCH-UE-DRX-Cycle-LCR e-AGCH-UE-Inactivity-Monitor-Threshold e-AGCH-UE-DRX-Offset-LCR iE-Extensions ... }

946

3GPP TS 25.423 V11.2.0 (2012-06)

UE-DRX-Cycle-LCR OPTIONAL, E-AGCH-UE-Inactivity-Monitor-Threshold OPTIONAL, UE-DRX-Offset-LCR OPTIONAL, ProtocolExtensionContainer { { E-AGCH-DRX-Parameters-Response-ExtIEs} } OPTIONAL,

E-AGCH-DRX-Parameters-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Controlled-Object-Scope ::= SEQUENCE{ rNC-ID extended-RNC-ID multiple-PLMN-List umts-cell-Info iE-Extensions ... } RNC-ID, Extended-RNC-ID OPTIONAL, Multiple-PLMN-List OPTIONAL, UMTS-Cells-Info-List OPTIONAL, ProtocolExtensionContainer { {Controlled-Object-Scope-ExtIEs} } OPTIONAL,

Controlled-Object-Scope-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- D DATA-ID ::= INTEGER (0..3) DCH-FDD-Information ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-FDD-InformationItem PayloadCRC-PresenceIndicator, UL-FP-Mode, ToAWS, ToAWE, DCH-Specific-FDD-InformationList, ProtocolExtensionContainer { {DCH-FDD-InformationItem-ExtIEs} } OPTIONAL,

DCH-FDD-InformationItem ::= SEQUENCE { payloadCRC-PresenceIndicator ul-FP-Mode toAWS toAWE dCH-SpecificInformationList iE-Extensions ... }

DCH-FDD-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
{ ID id-TnlQos ... } CRITICALITY ignore EXTENSION TnlQos

947
PRESENCE optional },

3GPP TS 25.423 V11.2.0 (2012-06)

DCH-MeasurementOccasion-Information ::= SEQUENCE (SIZE (1.. maxNrOfDCHMeasurementOccasionPatternSequence)) OF DchMeasurementOccasionInformation-Item DchMeasurementOccasionInformation-Item ::= SEQUENCE { pattern-Sequence-Identifier Pattern-Sequence-Identifier, status-Flag Status-Flag, measurement-Occasion-Pattern-Sequence-parameters Measurement-Occasion-Pattern-Sequence-parameters iE-Extensions ProtocolExtensionContainer { { DCH-MeasurementOccasion-Information-ExtIEs } } ... } DCH-MeasurementOccasion-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Measurement-Occasion-Pattern-Sequence-parameters ::= SEQUENCE { measurement-Occasion-Pattern-Sequence-parameters-k INTEGER(1..9), measurement-Occasion-Pattern-Sequence-parameters-offset INTEGER(0..511), measurement-Occasion-Pattern-Sequence-parameters-M-Length INTEGER(1..512), measurement-Occasion-Pattern-Sequence-parameters-Timeslot-Bitmap BIT STRING (SIZE (7)), iE-Extensions ProtocolExtensionContainer { { Measurement-Occasion-Pattern-Sequence-parameters-ExtIEs } } OPTIONAL, ... } Measurement-Occasion-Pattern-Sequence-parameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DCH-MeasurementType-Indicator ::= BIT STRING (SIZE (5)) DCH-Specific-FDD-InformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-Specific-FDD-Item DCH-Specific-FDD-Item ::= SEQUENCE { dCH-ID trCH-SrcStatisticsDescr ul-transportFormatSet dl-transportFormatSet ul-BLER dl-BLER allocationRetentionPriority frameHandlingPriority qE-Selector dRACControl iE-Extensions ... } DCH-ID, TrCH-SrcStatisticsDescr, TransportFormatSet, TransportFormatSet, BLER, BLER, AllocationRetentionPriority, FrameHandlingPriority, QE-Selector, DRACControl, ProtocolExtensionContainer { {DCH-FDD-SpecificItem-ExtIEs} } OPTIONAL,

OPTIONAL, OPTIONAL,

3GPP

Release 11
DCH-FDD-SpecificItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Guaranteed-Rate-Information CRITICALITY ignore { ID id-TrafficClass CRITICALITY ignore { ID id-Unidirectional-DCH-Indicator CRITICALITY reject ... } DCH-Indicator-For-E-DCH-HSDPA-Operation ::= ENUMERATED { dch-not-present } DCH-ID ::= INTEGER (0..255)

948
EXTENSION Guaranteed-Rate-Information EXTENSION TrafficClass PRESENCE mandatory}| EXTENSION Unidirectional-DCH-Indicator

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional PRESENCE optional }| },

DCH-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-InformationResponseItem DCH-InformationResponseItem ::= SEQUENCE { dCH-ID DCH-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DCH-InformationResponseItem-ExtIEs} } OPTIONAL, ... } DCH-InformationResponseItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Allowed-Rate-Information CRITICALITY ignore optional }| { ID id-TransportBearerNotSetupIndicator CRITICALITY ignore only ... } DCH-TDD-Information EXTENSION Allowed-Rate-Information EXTENSION TransportBearerNotSetupIndicator PRESENCE PRESENCE optional }, -- FDD

::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-TDD-InformationItem PayloadCRC-PresenceIndicator, UL-FP-Mode, ToAWS, ToAWE, DCH-Specific-TDD-InformationList, ProtocolExtensionContainer { {DCH-TDD-InformationItem-ExtIEs} } OPTIONAL,

DCH-TDD-InformationItem ::= SEQUENCE { payloadCRC-PresenceIndicator ul-FP-Mode toAWS toAWE dCH-SpecificInformationList iE-Extensions ... }

DCH-TDD-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TnlQos CRITICALITY ignore ... }

EXTENSION

TnlQos

PRESENCE

optional

},

DCH-Specific-TDD-InformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF DCH-Specific-TDD-Item DCH-Specific-TDD-Item ::= SEQUENCE {

3GPP

Release 11

949

3GPP TS 25.423 V11.2.0 (2012-06)

dCH-ID DCH-ID, ul-cCTrCH-ID CCTrCH-ID, -- UL CCTrCH in which the DCH is mapped dl-cCTrCH-ID CCTrCH-ID, -- DL CCTrCH in which the DCH is mapped trCH-SrcStatisticsDescr TrCH-SrcStatisticsDescr, ul-transportFormatSet TransportFormatSet, dl-transportFormatSet TransportFormatSet, ul-BLER BLER, dl-BLER BLER, allocationRetentionPriority AllocationRetentionPriority, frameHandlingPriority FrameHandlingPriority, qE-Selector QE-Selector OPTIONAL, -- This IE shall be present if DCH is part of set of Co-ordinated DCHs iE-Extensions ProtocolExtensionContainer { {DCH-Specific-TDD-Item-ExtIEs} } OPTIONAL, ... } DCH-Specific-TDD-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Guaranteed-Rate-Information CRITICALITY ignore { ID id-TrafficClass CRITICALITY ignore { ID id-Unidirectional-DCH-Indicator CRITICALITY reject ... } DedicatedMeasurementType ::= ENUMERATED { sir, sir-error, transmitted-code-power, rSCP, rx-timing-deviation, round-trip-time, ..., rx-timing-deviation-LCR, angle-Of-Arrival-LCR, hs-sich-quality, rx-timing-deviation-768, rx-timing-deviation-ext } DedicatedMeasurementValue ::= CHOICE { sIR-Value SIR-Value, sIR-ErrorValue SIR-Error-Value, transmittedCodePowerValue Transmitted-Code-Power-Value, rSCP RSCP-Value, -- TDD only rxTimingDeviationValue Rx-Timing-Deviation-Value, -- 3.84Mcps TDD only roundTripTime Round-Trip-Time-Value, -- FDD only ..., extension-DedicatedMeasurementValue Extension-DedicatedMeasurementValue } Extension-DedicatedMeasurementValue ::= ProtocolIE-Single-Container {{ Extension-DedicatedMeasurementValueIE }} EXTENSION Guaranteed-Rate-Information EXTENSION TrafficClass PRESENCE mandatory}| EXTENSION Unidirectional-DCH-Indicator PRESENCE optional PRESENCE optional }| },

3GPP

Release 11
Extension-DedicatedMeasurementValueIE RNSAP-PROTOCOL-IES ::= { { ID id-Rx-Timing-Deviation-Value-LCR CRITICALITY reject { ID id-Angle-Of-Arrival-Value-LCR CRITICALITY reject { ID id-HS-SICH-Reception-Quality CRITICALITY reject { ID id-Rx-Timing-Deviation-Value-768 CRITICALITY reject { ID id-Rx-Timing-Deviation-Value-ext CRITICALITY reject { ID id-Extended-Round-Trip-Time-Value CRITICALITY reject ... } DedicatedMeasurementValueInformation ::= CHOICE { measurementAvailable DedicatedMeasurementAvailable, measurementnotAvailable DedicatedMeasurementnotAvailable } TYPE TYPE TYPE TYPE TYPE TYPE

950

3GPP TS 25.423 V11.2.0 (2012-06)

Rx-Timing-Deviation-Value-LCR PRESENCE mandatory }| Angle-Of-Arrival-Value-LCR PRESENCE mandatory }| HS-SICH-Reception-Quality-Value PRESENCE mandatory }| Rx-Timing-Deviation-Value-768 PRESENCE mandatory }| Rx-Timing-Deviation-Value-ext PRESENCE mandatory }| Extended-Round-Trip-Time-Value PRESENCE mandatory },

DedicatedMeasurementAvailable::= SEQUENCE { dedicatedmeasurementValue DedicatedMeasurementValue, cFN CFN OPTIONAL, ie-Extensions ProtocolExtensionContainer { { DedicatedMeasurementAvailableItem-ExtIEs} } ... } DedicatedMeasurementAvailableItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DedicatedMeasurementnotAvailable ::= NULL DelayedActivation ::= CHOICE { cfn CFN, separate-indication NULL } DelayedActivationUpdate ::= CHOICE { activate Activate-Info, deactivate Deactivate-Info } Activate-Info ::= SEQUENCE { activation-type Execution-Type, initial-dl-tx-power DL-Power, firstRLS-Indicator FirstRLS-Indicator propagation-delay PropagationDelay iE-Extensions ProtocolExtensionContainer { { Activate-Info-ExtIEs} } ... } Activate-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-ExtendedPropagationDelay CRITICALITY ignore ...

OPTIONAL,

OPTIONAL, --FDD Only OPTIONAL, --FDD Only OPTIONAL,

EXTENSION ExtendedPropagationDelay

PRESENCE optional

},

3GPP

Release 11
}

951

3GPP TS 25.423 V11.2.0 (2012-06)

Deactivate-Info ::= SEQUENCE { deactivation-type Execution-Type, iE-Extensions ProtocolExtensionContainer { { Deactivate-Info-ExtIEs} } ... } Deactivate-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Execution-Type ::= CHOICE { synchronised CFN, unsynchronised NULL } DeltaSIR ::= INTEGER (0..30) -- Step 0.1 dB, Range 0..3 dB.

OPTIONAL,

DGANSSCorrections ::= SEQUENCE { dGANSS-ReferenceTime INTEGER(0..119), dGANSS-Information SEQUENCE (SIZE (1..maxSgnType)) OF SEQUENCE { gANSS-SignalId GANSS-Signal-ID OPTIONAL, gANSS-StatusHealth GANSS-StatusHealth, -- The following IE shall be present if the StatusHealth IE value is not equal to no data or invalid data dGANSS-SignalInformation SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { satId INTEGER(0..63), gANSS-iod BIT STRING (SIZE (10)), udre UDRE, ganss-prc INTEGER(-2047..2047), ganss-rrc INTEGER(-127..127), ie-Extensions ProtocolExtensionContainer { { DGANSS-SignalInformationItem-ExtIEs } } OPTIONAL, ... } OPTIONAL, ie-Extensions ProtocolExtensionContainer { { DGANSS-InformationItem-ExtIEs } } OPTIONAL, ... }, ie-Extensions ProtocolExtensionContainer { { DGANSSCorrections-ExtIEs } } OPTIONAL, ... } DGANSSCorrections-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
DGANSS-Corrections-Req ::= SEQUENCE { dGANSS-Signal-ID ie-Extensions ... }

952
BIT STRING (SIZE (8)), ProtocolExtensionContainer { { DGANSS-Corrections-Req-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

DGANSS-Corrections-Req-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-GANSS-ID CRITICALITY ignore EXTENSION ... } DGANSS-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

GANSS-ID

PRESENCE

optional},

DGANSS-SignalInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-DGNSS-ValidityPeriod CRITICALITY ignore EXTENSION DGNSS-ValidityPeriod ... } DGANSSThreshold ::= SEQUENCE { pRCDeviation PRCDeviation, ... } DGNSS-ValidityPeriod ::= udreGrowthRate udreValidityTime iE-Extensions ... }

PRESENCE

optional},

SEQUENCE { UDREGrowthRate, UDREValidityTime, ProtocolExtensionContainer { { DGNSS-ValidityPeriod-ExtIEs } }

OPTIONAL,

DGNSS-ValidityPeriod-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DGPSCorrections ::= SEQUENCE { gPSTOW gPS-Status-Health satellite-DGPSCorrections-Information SEQUENCE { sAT-ID iode-dgps uDRE pRC GPSTOW, GPS-Status-Health, SEQUENCE (SIZE (1..maxNoSat)) OF SAT-ID, BIT STRING (SIZE (8)), UDRE, PRC,

3GPP

Release 11
range-Correction-Rate iE-Extensions ...

953

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

Range-Correction-Rate, ProtocolExtensionContainer { { Satellite-DGPSCorrections-Information-ExtIEs} }

}, iE-Extensions ... }

ProtocolExtensionContainer { { DGPSCorrections-ExtIEs} }

OPTIONAL,

Satellite-DGPSCorrections-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-DGNSS-ValidityPeriod CRITICALITY ignore EXTENSION DGNSS-ValidityPeriod ... } DGPSCorrections-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DGPSThreshold ::= SEQUENCE { pRCDeviation PRCDeviation, iE-Extensions ProtocolExtensionContainer { { DGPSThreshold-ExtIEs} } ... } DGPSThreshold-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

PRESENCE optional},

OPTIONAL,

DiscardTimer ::= ENUMERATED {v20,v40,v60,v80,v100,v120,v140,v160,v180,v200,v250,v300,v400,v500,v750,v1000,v1250,v1500,v1750,v2000,v2500,v3000,v3500,v4000,v4500,v5000,v7500, ... } DiversityControlField may, must, must-not } ::= ENUMERATED {

DiversityMode ::= ENUMERATED { none, sTTD, closedLoopMode1, not-used-closedLoopMode2, ... } DL-DPCH-SlotFormat ::= INTEGER (0..16,...)

3GPP

Release 11
DL-DPCH-TimingAdjustment ::= ENUMERATED { timing-advance, timing-delay } DL-Power ::= INTEGER (-350..150) -- Value = DL-Power / 10 -- Unit dB, Range 35dB .. +15dB, Step 0.1dB

954

3GPP TS 25.423 V11.2.0 (2012-06)

DL-PowerBalancing-Information ::= SEQUENCE { powerAdjustmentType PowerAdjustmentType, dLReferencePower DL-Power OPTIONAL, -- This IE shall be present if Power Adjustment Type IE equals to Common dLReferencePowerList DL-ReferencePowerInformationList OPTIONAL, -- This IE shall be present if Power Adjustment Type IE equals to Individual maxAdjustmentStep MaxAdjustmentStep OPTIONAL, -- This IE shall be present if Power Adjustment Type IE equals to Common or Individual adjustmentPeriod AdjustmentPeriod OPTIONAL, -- This IE shall be present if Power Adjustment Type IE equals to Common or Individual adjustmentRatio ScaledAdjustmentRatio OPTIONAL, -- This IE shall be present if Power Adjustment Type IE equals to Common or Individual iE-Extensions ProtocolExtensionContainer { { DL-PowerBalancing-Information-ExtIEs } } OPTIONAL, ... } DL-PowerBalancing-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-ReferencePowerInformationList ::= SEQUENCE (SIZE (1..maxNrOfRLs)) OF DL-ReferencePowerInformationItem

DL-ReferencePowerInformationItem ::= SEQUENCE { rL-ID RL-ID, dl-Reference-Power DL-Power, iE-Extensions ProtocolExtensionContainer { {DL-ReferencePowerInformationItem-ExtIEs} } OPTIONAL, ... } DL-ReferencePowerInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-PowerBalancing-ActivationIndicator dL-PowerBalancing-Activated } DL-PowerBalancing-UpdatedIndicator dL-PowerBalancing-Updated } ::= ENUMERATED {

::= ENUMERATED {

3GPP

Release 11
DL-ReferencePowerInformation ::= SEQUENCE { common-DL-ReferencePowerInformation individual-DL-ReferencePowerInformation iE-Extensions ... }

955

3GPP TS 25.423 V11.2.0 (2012-06)

DL-Power OPTIONAL, DL-ReferencePowerInformationList OPTIONAL, ProtocolExtensionContainer { { DL-ReferencePowerInformation-ExtIEs } } OPTIONAL,

DL-ReferencePowerInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } D-RNTI ::= INTEGER (0..1048575)

D-RNTI-ReleaseIndication ::= ENUMERATED { release-D-RNTI, not-release-D-RNTI } DL-ScramblingCode ::= INTEGER (0..15)

DL-FrameType ::= ENUMERATED { typeA, typeB, ... } DL-Timeslot-Information ::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationItem DL-Timeslot-InformationItem ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, tFCI-Presence TFCI-Presence, dL-Code-Information TDD-DL-Code-Information, iE-Extensions ProtocolExtensionContainer { {DL-Timeslot-InformationItem-ExtIEs} } OPTIONAL, ... } DL-Timeslot-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-TimeslotLCR-Information ::= SEQUENCE (SIZE (1.. maxNrOfDLTsLCR)) OF DL-TimeslotLCR-InformationItem DL-TimeslotLCR-InformationItem timeSlotLCR midambleShiftLCR tFCI-Presence dL-Code-LCR-Information iE-Extensions ... } ::= SEQUENCE { TimeSlotLCR, MidambleShiftLCR, TFCI-Presence, TDD-DL-Code-LCR-Information, ProtocolExtensionContainer { { DL-TimeslotLCR-InformationItem-ExtIEs} }

OPTIONAL,

3GPP

Release 11

956
EXTENSION DL-Power EXTENSION DL-Power

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional PRESENCE optional }| },

DL-TimeslotLCR-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Maximum-DL-Power-TimeslotLCR-InformationItem CRITICALITY ignore -- Applicable to 1.28Mcps TDD only { ID id-Minimum-DL-Power-TimeslotLCR-InformationItem CRITICALITY ignore -- Applicable to 1.28Mcps TDD only ... }

DL-Timeslot-Information768 ::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF DL-Timeslot-InformationItem768 DL-Timeslot-InformationItem768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, tFCI-Presence TFCI-Presence, dL-Code-Information768 TDD-DL-Code-Information768, iE-Extensions ProtocolExtensionContainer { {DL-Timeslot-InformationItem768-ExtIEs} } OPTIONAL, ... } DL-Timeslot-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-TimeSlot-ISCP-Info ::= SEQUENCE (SIZE (1..maxNrOfDLTs)) OF DL-TimeSlot-ISCP-InfoItem DL-TimeSlot-ISCP-InfoItem ::= SEQUENCE { timeSlot TimeSlot, dL-TimeslotISCP DL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { DL-TimeSlot-ISCP-InfoItem-ExtIEs} } OPTIONAL, ... } DL-TimeSlot-ISCP-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-TimeSlot-ISCP-LCR-Information ::= SEQUENCE (SIZE (1..maxNrOfDLTsLCR)) OF DL-TimeSlot-ISCP-LCR-InfoItem DL-TimeSlot-ISCP-LCR-InfoItem ::= SEQUENCE { timeSlotLCR TimeSlotLCR, dL-TimeslotISCP DL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { DL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs} } ... } DL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DL-TimeslotISCP ::= INTEGER (0..91)

OPTIONAL,

3GPP

Release 11
-- According to mapping in TS 25.123 [24] Downlink-Compressed-Mode-Method not-Used-puncturing, sFdiv2, higher-layer-scheduling, ... } DPC-Mode ::= ENUMERATED { mode0, mode1, ... } DPC-Mode-Change-SupportIndicator ::= ENUMERATED { dPC-ModeChangeSupported } DPCH-ID ::= INTEGER (0..239) ::= ENUMERATED {

957

3GPP TS 25.423 V11.2.0 (2012-06)

DPCH-ID768 ::= INTEGER (0..479) DPCHConstantValue ::= INTEGER (-10..10) -- Unit dB, Step 1dB DRACControl ::= ENUMERATED { not-Used-requested, not-requested } DRXCycleLengthCoefficient -- See in TS 25.331 [16] ::= INTEGER (3..9)

DRX-Information ::= SEQUENCE { uE-DRX-Cycle UE-DRX-Cycle, inactivity-Threshold-for-UE-DRX-Cycle Inactivity-Threshold-for-UE-DRX-Cycle, inactivity-Threshold-for-UE-Grant-Monitoring Inactivity-Threshold-for-UE-Grant-Monitoring, uE-DRX-Grant-Monitoring UE-DRX-Grant-Monitoring, iE-Extensions ProtocolExtensionContainer { {DRX-Information-ExtIEs} } OPTIONAL, ... } DRX-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DRX-Information-to-Modify ::= CHOICE { modify DRX-Information-to-Modify-Items, deactivate NULL,

3GPP

Release 11
} ...

958

3GPP TS 25.423 V11.2.0 (2012-06)

DRX-Information-to-Modify-Items ::= SEQUENCE { uE-DRX-Cycle UE-DRX-Cycle OPTIONAL, inactivity-Threshold-for-UE-DRX-Cycle Inactivity-Threshold-for-UE-DRX-Cycle inactivity-Threshold-for-UE-Grant-Monitoring Inactivity-Threshold-for-UE-Grant-Monitoring uE-DRX-Grant-Monitoring UE-DRX-Grant-Monitoring OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DRX-Information-to-Modify-Items-ExtIEs} } OPTIONAL, ... } DRX-Information-to-Modify-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DSCH-RNTI ::= INTEGER (0..65535) DSCH-FlowControlInformation ::= SEQUENCE (SIZE(1..16)) OF DSCH-FlowControlItem SchedulingPriorityIndicator, MAC-c-sh-SDU-LengthList, ProtocolExtensionContainer { {DSCH-FlowControlItem-ExtIEs} } OPTIONAL,

OPTIONAL, OPTIONAL,

DSCH-FlowControlItem ::= SEQUENCE { dSCH-SchedulingPriority mAC-c-sh-SDU-Lengths iE-Extensions ... }

DSCH-FlowControlItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-DSCH-InitialWindowSize CRITICALITY ignore EXTENSION ... } DSCH-ID ::= INTEGER (0..255)

DSCH-InitialWindowSize

PRESENCE optional },

DSCH-InitialWindowSize ::= INTEGER (1..255) -- Number of MAC-c/sh SDUs. -- 255 = Unlimited number of MAC-c/sh SDUs DSCH-TDD-Information ::= SEQUENCE (SIZE (1..maxNoOfDSCHs)) OF DSCH-TDD-InformationItem

DSCH-TDD-InformationItem ::= SEQUENCE { dSCH-ID DSCH-ID, dl-ccTrCHID CCTrCH-ID, -- DL CCTrCH in which the DSCH is mapped trChSourceStatisticsDescriptor TrCH-SrcStatisticsDescr, transportFormatSet TransportFormatSet, allocationRetentionPriority AllocationRetentionPriority, schedulingPriorityIndicator SchedulingPriorityIndicator, bLER BLER, iE-Extensions ProtocolExtensionContainer { {DSCH-TDD-InformationItem-ExtIEs} } OPTIONAL, ...

3GPP

Release 11
} DSCH-TDD-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TrafficClass CRITICALITY ignore { ID id-BindingID CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. { ID id-TransportLayerAddress CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. { ID id-TnlQos CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. ... } DsField ::= BIT STRING (SIZE (8)) DTX-Cycle-2ms-Items ::= SEQUENCE { uE-DTX-Cycle1-2ms uE-DTX-Cycle2-2ms mAC-DTX-Cycle-2ms iE-Extensions ... }

959

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION TrafficClass EXTENSION BindingID EXTENSION EXTENSION TransportLayerAddress TnlQos

PRESENCE mandatory}| PRESENCE optional }| PRESENCE optional PRESENCE optional }, }|

UE-DTX-Cycle1-2ms, UE-DTX-Cycle2-2ms, MAC-DTX-Cycle-2ms, ProtocolExtensionContainer { { DTX-Cycle-2ms-Items-ExtIEs} }

OPTIONAL,

DTX-Cycle-2ms-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DTX-Cycle-2ms-to-Modify-Items ::= SEQUENCE { uE-DTX-Cycle1-2ms UE-DTX-Cycle1-2ms OPTIONAL, uE-DTX-Cycle2-2ms UE-DTX-Cycle2-2ms OPTIONAL, mAC-DTX-Cycle-2ms MAC-DTX-Cycle-2ms OPTIONAL, iE-Extensions ProtocolExtensionContainer { { DTX-Cycle-2ms-to-Modify-Items-ExtIEs} } ... } DTX-Cycle-2ms-to-Modify-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DTX-Cycle-10ms-Items ::= SEQUENCE { uE-DTX-Cycle1-10ms UE-DTX-Cycle1-10ms, uE-DTX-Cycle2-10ms UE-DTX-Cycle2-10ms, mAC-DTX-Cycle-10ms MAC-DTX-Cycle-10ms, iE-Extensions ProtocolExtensionContainer { { DTX-Cycle-10ms-Items-ExtIEs} } ... } DTX-Cycle-10ms-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL,

3GPP

Release 11

960

3GPP TS 25.423 V11.2.0 (2012-06)

DTX-Cycle-10ms-to-Modify-Items ::= SEQUENCE { uE-DTX-Cycle1-10ms UE-DTX-Cycle1-10ms OPTIONAL, uE-DTX-Cycle2-10ms UE-DTX-Cycle2-10ms OPTIONAL, mAC-DTX-Cycle-10ms MAC-DTX-Cycle-10ms iE-Extensions ProtocolExtensionContainer { { DTX-Cycle-10ms-to-Modify-Items-ExtIEs} } ... } DTX-Cycle-10ms-to-Modify-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DTX-Information ::= SEQUENCE { e-DCH-TTI-Length E-DCH-TTI-Length, inactivity-Threshold-for-UE-DTX-Cycle2 Inactivity-Threshold-for-UE-DTX-Cycle2, uE-DTX-Long-Preamble UE-DTX-Long-Preamble, mAC-Inactivity-Threshold MAC-Inactivity-Threshold , cQI-DTX-Timer CQI-DTX-Timer, uE-DPCCH-burst1 UE-DPCCH-burst1, uE-DPCCH-burst2 UE-DPCCH-burst2, iE-Extensions ProtocolExtensionContainer { {DTX-Information-ExtIEs} } OPTIONAL, ... } DTX-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } DTX-Information-to-Modify ::= CHOICE { modify DTX-Information-to-Modify-Items, deactivate NULL, ... } DTX-Information-to-Modify-Items ::= SEQUENCE { e-DCH-TTI-Length-to-Modify E-DCH-TTI-Length-to-Modify OPTIONAL, inactivity-Threshold-for-UE-DTX-Cycle2 Inactivity-Threshold-for-UE-DTX-Cycle2 uE-DTX-Long-Preamble UE-DTX-Long-Preamble OPTIONAL, mAC-Inactivity-Threshold MAC-Inactivity-Threshold OPTIONAL, cQI-DTX-Timer CQI-DTX-Timer OPTIONAL, uE-DPCCH-burst1 UE-DPCCH-burst1 OPTIONAL, uE-DPCCH-burst2 UE-DPCCH-burst2 OPTIONAL, iE-Extensions ProtocolExtensionContainer { {DTX-Information-to-Modify-Items-ExtIEs} } OPTIONAL, ... } DTX-Information-to-Modify-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL, OPTIONAL,

OPTIONAL,

3GPP

Release 11
-- E EARFCN ::= INTEGER (0..maxEARFCN) EARFCN-Information ::= CHOICE { fDD EARFCN-FDD, tDD EARFCN, ... } EARFCN-FDD ::= SEQUENCE { uL-EARFCN EARFCN, dL-EARFCN EARFCN } E-AGCH-Table-Choice ::= ENUMERATED{table16B, table16B-1, ...} ECGI ::= SEQUENCE { pLMN-Identity e-UTRAN-Cell-ID iE-Extensions ... }

961

3GPP TS 25.423 V11.2.0 (2012-06)

PLMN-Identity, BIT STRING (SIZE (28)), ProtocolExtensionContainer { {ECGI-ExtIEs} } OPTIONAL,

ECGI-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-DDI-Value ::= INTEGER (0..62) EDCH-FDD-DL-ControlChannelInformation ::= SEQUENCE { eAGCH-ERGCH-EHICH-FDD-ScramblingCode eAGCH-ChannelisationCode primary-e-RNTI secondary-e-RNTI eRGCH-EHICH-ChannelisationCode eRGCH-SignatureSequence eHICH-SignatureSequence serving-Grant-Value primary-Secondary-Grant-Selector e-RGCH-Release-Indicator iE-Extensions OPTIONAL, ... } DL-ScramblingCode OPTIONAL, FDD-DL-ChannelisationCodeNumber OPTIONAL, E-RNTI OPTIONAL, E-RNTI OPTIONAL, FDD-DL-ChannelisationCodeNumber, ERGCH-SignatureSequence OPTIONAL, EHICH-SignatureSequence OPTIONAL, E-Serving-Grant-Value OPTIONAL, E-Primary-Secondary-Grant-Selector OPTIONAL, E-RGCH-Release-Indicator OPTIONAL, ProtocolExtensionContainer { { EDCH-FDD-DL-ControlChannelInformation-ExtIEs } }

EDCH-FDD-DL-ControlChannelInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-RGCH-E-HICH-ChannelisationCodeValidityIndicator CRITICALITY ignore PRESENCE optional }|

EXTENSION E-RGCH-E-HICH-ChannelisationCodeValidityIndicator

3GPP

Release 11
{ ID id-Default-Serving-Grant-in-DTX-Cycle2 PRESENCE optional }, ...

962
CRITICALITY ignore EXTENSION E-Serving-Grant-Value

3GPP TS 25.423 V11.2.0 (2012-06)

} E-RGCH-E-HICH-ChannelisationCodeValidityIndicator ::= ENUMERATED { e-RGCH-E-HICH-Channelisation-Code-response-not-valid } EDCH-FDD-Information ::= SEQUENCE { eDCH-MACdFlows-Information hARQ-Process-Allocation-Scheduled-2ms-EDCH OPTIONAL, e-DCH-Maximum-Bitrate e-DCH-Processing-Overload-Level e-DCH-Reference-Power-Offset iE-Extensions ... } EDCH-MACdFlows-Information, HARQ-Process-Allocation-2ms-EDCH E-DCH-Maximum-Bitrate E-DCH-Processing-Overload-Level E-DCH-Reference-Power-Offset ProtocolExtensionContainer { { EDCH-FDD-Information-ExtIEs } } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

EDCH-FDD-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-PowerOffset-for-SchedulingInfo CRITICALITY ignore EXTENSION E-DCH-PowerOffset-for-SchedulingInfo PRESENCE optional}| { ID id-SixteenQAM-UL-Operation-Indicator CRITICALITY reject EXTENSION SixteenQAM-UL-Operation-Indicator PRESENCE optional}| { ID id-E-AGCH-Table-Choice CRITICALITY ignore EXTENSION E-AGCH-Table-Choice PRESENCE conditional}, -- The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to Activate-... } EDCH-FDD-InformationResponse ::= SEQUENCE { eDCH-MACdFlow-Specific-InformationResponse hARQ-Process-Allocation-Scheduled-2ms-EDCH OPTIONAL, iE-Extensions OPTIONAL, ... } EDCH-MACdFlow-Specific-InformationResponse, HARQ-Process-Allocation-2ms-EDCH ProtocolExtensionContainer { { EDCH-FDD-InformationResponse-ExtIEs } }

EDCH-FDD-InformationResponse-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-MACdFlow-Specific-InformationResponse ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF EDCH-MACdFlow-Specific-InformationResponseItem EDCH-MACdFlow-Specific-InformationResponseItem ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL,

3GPP

Release 11

963

3GPP TS 25.423 V11.2.0 (2012-06)

hARQ-Process-Allocation-NonSched-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH OPTIONAL, iE-Extensions ProtocolExtensionContainer { {EDCH-MACdFlow-Specific-InformationResponseItem-ExtIEs} } OPTIONAL, ... } EDCH-MACdFlow-Specific-InformationResponseItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TransportBearerNotSetupIndicator CRITICALITY ignore EXTENSION TransportBearerNotSetupIndicator only ... } EDCH-FDD-Information-To-Modify ::= SEQUENCE { eDCH-MACdFlow-Specific-Information hARQ-Process-Allocation-Scheduled-2ms-EDCH OPTIONAL, e-DCH-Maximum-Bitrate OPTIONAL, e-DCH-Processing-Overload-Level OPTIONAL, e-DCH-Reference-Power-Offset OPTIONAL, mACeReset-Indicator OPTIONAL, iE-Extensions ... } EDCH-MACdFlow-Specific-InfoToModifyList, HARQ-Process-Allocation-2ms-EDCH E-DCH-Maximum-Bitrate E-DCH-Processing-Overload-Level E-DCH-Reference-Power-Offset MACeReset-Indicator ProtocolExtensionContainer { { EDCH-FDD-Information-To-Modify-ExtIEs } } OPTIONAL, PRESENCE optional }, -- FDD

EDCH-FDD-Information-To-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-PowerOffset-for-SchedulingInfo CRITICALITY ignore EXTENSION E-DCH-PowerOffset-for-SchedulingInfo PRESENCE optional}| { ID id-SixteenQAM-UL-Operation-Indicator CRITICALITY reject EXTENSION SixteenQAM-UL-Operation-Indicator PRESENCE optional}| { ID id-E-DCH-MACdPDUSizeFormat CRITICALITY reject EXTENSION E-DCH-MACdPDUSizeFormat PRESENCE optional}| { ID id-E-DCH-DL-Control-Channel-Grant-Information CRITICALITY ignore EXTENSION E-DCH-DL-Control-Channel-Grant-Information PRESENCE optional}| { ID id-E-AGCH-Table-Choice CRITICALITY ignore EXTENSION E-AGCH-Table-Choice PRESENCE conditional}, -- The IE shall be present if the SixteenQAM UL Operation Indicator IE is set to Activate-... } E-DCH-FDD-Update-Information ::= SEQUENCE { e-DCH-MACdFlow-Specific-UpdateInformation E-DCH-MACdFlow-Specific-UpdateInformation OPTIONAL, hARQ-Process-Allocation-Scheduled-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-FDD-Update-Information-ExtIEs } } OPTIONAL, ... }

3GPP

Release 11

964
EXTENSION

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-DL-Control-Channel-Change-Information

E-DCH-FDD-Update-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-DL-Control-Channel-Change-Information CRITICALITY ignore PRESENCE optional}, ... }

E-DCH-MACdFlow-Specific-UpdateInformation ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-Specific-UpdateInformation-Item E-DCH-MACdFlow-Specific-UpdateInformation-Item ::= SEQUENCE { e-DCH-MACdFlow-ID EDCH-MACdFlow-ID, hARQ-Process-Allocation-NonSched-2ms-EDCH HARQ-Process-Allocation-2ms-EDCH OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-MACdFlow-Specific-UpdateInformation-Item-ExtIEs} } ... } E-DCH-MACdFlow-Specific-UpdateInformation-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-DL-Control-Channel-Change-Information ::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF E-DCH-DL-Control-Channel-Change-Information-Item E-DCH-DL-Control-Channel-Change-Information-Item ::= SEQUENCE { e-DCH-RL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { E-DCH-DL-Control-Channel-Change-Information-Item-ExtIEs} } ... } E-DCH-DL-Control-Channel-Change-Information-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-DL-Control-Channel-Grant-Information ::= SEQUENCE (SIZE (1..maxNrOfEDCHRLs)) OF E-DCH-DL-Control-Channel-Grant-Information-Item E-DCH-DL-Control-Channel-Grant-Information-Item ::= SEQUENCE { e-DCH-RL-ID RL-ID, iE-Extensions ProtocolExtensionContainer { { E-DCH-DL-Control-Channel-Grant-Information-Item-ExtIEs} } ... } E-DCH-DL-Control-Channel-Grant-Information-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL,

OPTIONAL,

E-DCH-Grant-Type-Information ::= CHOICE { e-DCH-Non-Scheduled-Transmission-Grant e-DCH-Scheduled-Transmission-Grant ...

E-DCH-Non-Scheduled-Transmission-Grant-Items, NULL,

3GPP

Release 11
} E-DCH-HARQ-PO-FDD ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs)

965

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-LogicalChannelInformation ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelInformationItem E-DCH-LogicalChannelInformationItem logicalChannelId schedulingPriorityIndicator schedulingInformation mACes-GuaranteedBitRate eDCH-DDI-Value mACd-PDU-Size-List iE-Extensions ... } ::= SEQUENCE { LogicalChannelID, SchedulingPriorityIndicator, SchedulingInformation, MACes-Guaranteed-Bitrate OPTIONAL, EDCH-DDI-Value, E-DCH-MACdPDU-SizeList, ProtocolExtensionContainer { { E-DCH-LogicalChannelInformationItem-ExtIEs } }

OPTIONAL,

E-DCH-LogicalChannelInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY reject EXTENSION MAC-PDU-SizeExtended PRESENCE optional}| { ID id-MACes-Maximum-Bitrate-LCR CRITICALITY ignore EXTENSION MACes-Maximum-Bitrate-LCR PRESENCE optional}| --1.28Mcps TDD only { ID id-UE-AggregateMaximumBitRate-Enforcement-Indicator CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate-Enforcement-Indicator PRESENCE optional}, ... } E-DCH-Maximum-Bitrate ::= INTEGER (0..5742,...,5743..11498) E-DCH-PowerOffset-for-SchedulingInfo ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs) E-DCH-Processing-Overload-Level ::= INTEGER (0..10,...) E-DCH-Reference-Power-Offset ::= INTEGER (0.. maxNrOfEDCH-HARQ-PO-QUANTSTEPs) E-DCH-MACdPDU-SizeList ::= SEQUENCE (SIZE (1..maxNrOfMACdPDUSize)) OF E-DCH-MACdPDU-SizeListItem E-DCH-MACdPDU-SizeListItem ::= SEQUENCE { mACdPDU-Size MACdPDU-Size, iE-Extensions ProtocolExtensionContainer { { E-DCH-MACdPDU-SizeListItem-ExtIEs } } ... } E-DCH-MACdPDU-SizeListItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-MACdPDUSizeFormat ::= ENUMERATED { fixedMACdPDU-Size, flexibleMACdPDU-Size }

OPTIONAL,

3GPP

Release 11

966

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-LogicalChannelToModify ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelToModifyItem E-DCH-LogicalChannelToModifyItem ::= SEQUENCE { logicalChannelId LogicalChannelID, schedulingPriorityIndicator SchedulingPriorityIndicator OPTIONAL, schedulingInformation SchedulingInformation OPTIONAL, mACes-GuaranteedBitRate MACes-Guaranteed-Bitrate OPTIONAL, eDCH-DDI-Value EDCH-DDI-Value OPTIONAL, mACd-PDU-Size-List E-DCH-MACdPDU-SizeToModifyList, iE-Extensions ProtocolExtensionContainer { { E-DCH-LogicalChannelToModifyItem-ExtIEs } } ... } E-DCH-LogicalChannelToModifyItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY reject EXTENSION { ID id-MACes-Maximum-Bitrate-LCR CRITICALITY ignore EXTENSION TDD only ... }

OPTIONAL,

MAC-PDU-SizeExtended PRESENCE optional}| MACes-Maximum-Bitrate-LCR PRESENCE optional},--1.28Mcps

E-DCH-MACdPDU-SizeToModifyList ::= SEQUENCE (SIZE (0..maxNrOfMACdPDUSize)) OF E-DCH-MACdPDU-SizeListItem

E-DCH-LogicalChannelToDelete ::= SEQUENCE (SIZE (1..maxNoOfLogicalChannels)) OF E-DCH-LogicalChannelToDeleteItem E-DCH-LogicalChannelToDeleteItem ::= SEQUENCE { logicalChannelId LogicalChannelID, iE-Extensions ProtocolExtensionContainer { { E-DCH-LogicalChannelToDeleteItem-ExtIEs } } ... } E-DCH-LogicalChannelToDeleteItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } LogicalChannelID ::= INTEGER (1..15)

OPTIONAL,

EDCH-MACdFlow-ID ::= INTEGER (0..maxNrOfEDCHMACdFlows-1) EDCH-MACdFlow-ID-LCR ::= INTEGER (0..maxNrOfEDCHMACdFlowsLCR-1) EDCH-MACdFlows-Information ::= SEQUENCE { eDCH-MACdFlow-Specific-Information iE-Extensions ... } EDCH-MACdFlow-Specific-InfoList, ProtocolExtensionContainer { { EDCH-MACdFlow-Information-ExtIEs } }

OPTIONAL,

3GPP

Release 11

967

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-MACdFlow-Multiplexing-List ::= BIT STRING ( SIZE(maxNrOfEDCHMACdFlows) ) EDCH-MACdFlow-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-MACdFlow-Specific-InfoList ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF EDCH-MACdFlow-Specific-InfoItem EDCH-MACdFlow-Specific-InfoItem ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, allocationRetentionPriority AllocationRetentionPriority OPTIONAL, tnlQoS TnlQos OPTIONAL, payloadCRC-PresenceIndicator PayloadCRC-PresenceIndicator, maxNr-Retransmissions-EDCH MaxNr-Retransmissions-EDCH, trafficClass TrafficClass, eDCH-HARQ-PO-FDD E-DCH-HARQ-PO-FDD, eDCH-MACdFlow-Multiplexing-List E-DCH-MACdFlow-Multiplexing-List OPTIONAL, eDCH-Grant-Type-Information E-DCH-Grant-Type-Information OPTIONAL, bundlingModeIndicator BundlingModeIndicator OPTIONAL, eDCHLogicalChannelInformation E-DCH-LogicalChannelInformation, iE-Extensions ProtocolExtensionContainer { { EDCH-MACdFlow-Specific-InfoItem-ExtIEs } } ... } EDCH-MACdFlow-Specific-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-TrCH-SrcStatisticsDescr CRITICALITY ignore EXTENSION TrCH-SrcStatisticsDescr PRESENCE optional }, ... } EDCH-MACdFlow-Specific-InfoToModifyList ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF EDCH-MACdFlow-Specific-InfoToModifyItem EDCH-MACdFlow-Specific-InfoToModifyItem eDCH-MACdFlow-ID allocationRetentionPriority transportBearerRequestIndicator tnlQoS maxNr-Retransmissions-EDCH trafficClass eDCH-HARQ-PO-FDD eDCH-MACdFlow-Multiplexing-List eDCH-Grant-Type-Information bundlingModeIndicator eDCH-LogicalChannelToAdd eDCH-LogicalChannelToModify eDCH-LogicalChannelToDelete iE-Extensions ... } ::= SEQUENCE { EDCH-MACdFlow-ID, AllocationRetentionPriority OPTIONAL, TransportBearerRequestIndicator, TnlQos OPTIONAL, MaxNr-Retransmissions-EDCH OPTIONAL, TrafficClass OPTIONAL, E-DCH-HARQ-PO-FDD OPTIONAL, E-DCH-MACdFlow-Multiplexing-List OPTIONAL, E-DCH-Grant-Type-Information OPTIONAL, BundlingModeIndicator OPTIONAL, E-DCH-LogicalChannelInformation OPTIONAL, E-DCH-LogicalChannelToModify OPTIONAL, E-DCH-LogicalChannelToDelete OPTIONAL, ProtocolExtensionContainer { { EDCH-MACdFlow-Specific-InfoToModifyItem-ExtIEs } }

OPTIONAL,

OPTIONAL,

EDCH-MACdFlow-Specific-InfoToModifyItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

968

3GPP TS 25.423 V11.2.0 (2012-06)

EDCH-MACdFlows-To-Delete ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF EDCH-MACdFlows-To-Delete-Item EDCH-MACdFlows-To-Delete-Item ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, iE-Extensions ProtocolExtensionContainer { { EDCH-MACdFlows-To-Delete-Item-ExtIEs } } ... } EDCH-MACdFlows-To-Delete-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EDCH-RL-Indication ::= ENUMERATED { eDCH, non-EDCH } E-DCH-Non-Scheduled-Transmission-Grant-Items ::= SEQUENCE { -- The following IE shall be ignored if id-Ext-Max-Bits-MACe-PDU-non-scheduled is present in E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs maxBits-MACe-PDU-non-scheduled Max-Bits-MACe-PDU-non-scheduled, hARQ-Process-Allocation-NonSched-2ms HARQ-Process-Allocation-2ms-EDCH OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs} } OPTIONAL, ... } E-DCH-Non-Scheduled-Transmission-Grant-Items-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { -- The following IE shall be present if the maximum number of bits to be signalled exceeds maxNrOfBits-MACe-PDU-non-scheduled { ID id-Ext-Max-Bits-MACe-PDU-non-scheduled CRITICALITY reject EXTENSION Ext-Max-Bits-MACe-PDU-non-scheduled optional}, ... } E-DCH-TFCI-Table-Index ::= INTEGER (0..1,...,2..7) E-DCH-Serving-cell-change-informationResponse ::= SEQUENCE { e-DCH-serving-cell-outcome-choice E-DCH-serving-cell-change-choice, iE-Extensions ProtocolExtensionContainer { { E-DCH-serving-cell-change-informationResponse-ExtIEs} } OPTIONAL, ... } E-DCH-serving-cell-change-informationResponse-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-serving-cell-change-choice ::= CHOICE { e-DCH-serving-cell-change-successful E-DCH-serving-cell-change-successful,

OPTIONAL,

PRESENCE

3GPP

Release 11
e-DCH-serving-cell-change-unsuccessful ... }

969
E-DCH-serving-cell-change-unsuccessful,

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-serving-cell-change-successful ::= SEQUENCE { e-DCH-RL-InformationList-Rsp E-DCH-RL-InformationList-Rsp, iE-Extensions ProtocolExtensionContainer { { E-DCH-serving-cell-change-successful-ExtIEs} } OPTIONAL, ... } E-DCH-serving-cell-change-successful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-RL-InformationList-Rsp ::= SEQUENCE (SIZE (0..maxNrOfRLs)) OF E-DCH-RL-InformationList-Rsp-Item E-DCH-RL-InformationList-Rsp-Item ::= SEQUENCE { e-DCH-reconfigured-RL-Id RL-ID, e-DCH-FDD-DL-Control-Channel-Info EDCH-FDD-DL-ControlChannelInformation, iE-Extensions ProtocolExtensionContainer { { E-DCH-RL-InformationList-Rsp-Item-ExtIEs} } ... } E-DCH-RL-InformationList-Rsp-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

E-DCH-serving-cell-change-unsuccessful ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { E-DCH-serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL, ... } E-DCH-serving-cell-change-unsuccessful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TTI-Length ::= CHOICE { two-ms DTX-Cycle-2ms-Items, ten-ms DTX-Cycle-10ms-Items, ... } E-DCH-TTI-Length-to-Modify ::= CHOICE { two-ms DTX-Cycle-2ms-to-Modify-Items, ten-ms DTX-Cycle-10ms-to-Modify-Items, ... }

3GPP

Release 11
EDPCH-Information-FDD ::= SEQUENCE { maxSet-E-DPDCHs punctureLimit e-TFCS-Information e-TTI e-DPCCH-PO e-RGCH-2-IndexStepThreshold e-RGCH-3-IndexStepThreshold hARQ-Info-for-E-DCH hSDSCH-Configured-Indicator iE-Extensions ... }

970
Max-Set-E-DPDCHs, PunctureLimit, E-TFCS-Information, E-TTI, E-DPCCH-PO, E-RGCH-2-IndexStepThreshold, E-RGCH-3-IndexStepThreshold, HARQ-Info-for-E-DCH, HSDSCH-Configured-Indicator, ProtocolExtensionContainer { { EDPCH-Information-FDD-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

EDPCH-Information-FDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MinimumReducedE-DPDCH-GainFactor CRITICALITY ignore ... }

EXTENSION MinimumReducedE-DPDCH-GainFactor

PRESENCE optional },

EDPCH-Information-RLReconfPrepare-FDD ::= SEQUENCE { maxSet-E-DPDCHs Max-Set-E-DPDCHs OPTIONAL, punctureLimit PunctureLimit OPTIONAL, e-TFCS-Information E-TFCS-Information OPTIONAL, e-TTI E-TTI OPTIONAL, e-DPCCH-PO E-DPCCH-PO OPTIONAL, e-RGCH-2-IndexStepThreshold E-RGCH-2-IndexStepThreshold OPTIONAL, e-RGCH-3-IndexStepThreshold E-RGCH-3-IndexStepThreshold OPTIONAL, hARQ-Info-for-E-DCH HARQ-Info-for-E-DCH OPTIONAL, hSDSCH-Configured-Indicator HSDSCH-Configured-Indicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { EDPCH-Information-RLReconfPrepare-FDD-ExtIEs } } ... } EDPCH-Information-RLReconfPrepare-FDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MinimumReducedE-DPDCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE-DPDCH-GainFactor ... } EDPCH-Information-RLReconfRequest-FDD ::= SEQUENCE { maxSet-E-DPDCHs OPTIONAL, punctureLimit OPTIONAL, e-TFCS-Information OPTIONAL, e-TTI OPTIONAL, e-DPCCH-PO e-RGCH-2-IndexStepThreshold e-RGCH-3-IndexStepThreshold OPTIONAL, Max-Set-E-DPDCHs PunctureLimit E-TFCS-Information E-TTI E-DPCCH-PO E-RGCH-2-IndexStepThreshold E-RGCH-3-IndexStepThreshold

OPTIONAL,

PRESENCE optional },

OPTIONAL, OPTIONAL,

3GPP

Release 11
hARQ-Info-for-E-DCH OPTIONAL, hSDSCH-Configured-Indicator OPTIONAL, iE-Extensions ... }

971
HARQ-Info-for-E-DCH HSDSCH-Configured-Indicator ProtocolExtensionContainer { { EDPCH-Information-RLReconfRequest-FDD-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

EDPCH-Information-RLReconfRequest-FDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MinimumReducedE-DPDCH-GainFactor CRITICALITY ignore EXTENSION MinimumReducedE-DPDCH-GainFactor ... } E-DPCCH-PO ::= INTEGER (0..maxNrOfEDPCCH-PO-QUANTSTEPs) E-DPDCH-PowerInterpolation ::= BOOLEAN E-Primary-Secondary-Grant-Selector ::= ENUMERATED { primary, secondary } EHICH-SignatureSequence ::= INTEGER (0..maxNrofSigSeqERGHICH-1)

PRESENCE optional },

E-RGCH-Release-Indicator ::= ENUMERATED {e-RGCHreleased} ERGCH-SignatureSequence ::= INTEGER (0..maxNrofSigSeqERGHICH-1)

E-Serving-Grant-Value ::= INTEGER (0..38) E-RGCH-2-IndexStepThreshold ::= INTEGER (0..37) E-RGCH-3-IndexStepThreshold ::= INTEGER (0..37) EDCH-Serving-RL ::= CHOICE { e-DCH-Serving-RL-in-this-DRNS e-DCH-Serving-RL-not-in-this-DRNS ... }

EDCH-Serving-RL-in-this-DRNS, NULL,

EDCH-Serving-RL-in-this-DRNS ::= SEQUENCE { e-DCH-Serving-RL-Id RL-ID, iE-Extensions ProtocolExtensionContainer { { EDCH-Serving-RL-in-this-DRNS-ExtIEs} } ... } EDCH-Serving-RL-in-this-DRNS-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

3GPP

Release 11

972

3GPP TS 25.423 V11.2.0 (2012-06)

Enhanced-FACH-Information-ResponseFDD ::= SEQUENCE { common-HS-DSCH-RNTI-priorityQueueInfo-EnhancedFACH PriorityQueue-InfoList-EnhancedFACH-PCH, dedicated-HS-DSCH-RNTI-priorityQueueInfo-EnhancedFACH PriorityQueue-InfoList-EnhancedFACH-PCH, priorityQueueInfo-EnhancedPCH PriorityQueue-InfoList-EnhancedFACH-PCH OPTIONAL, hSDSCH-Initial-Capacity-Allocation HSDSCH-Initial-Capacity-Allocation, hSDSCH-RNTI HSDSCH-RNTI OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Enhanced-FACH-Information-ResponseFDD-ExtIEs } } ... } Enhanced-FACH-Information-ResponseFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Enhanced-FACH-Information-ResponseLCR ::= SEQUENCE { common-HS-DSCH-RNTI-priorityQueueInfo-EnhancedFACH PriorityQueue-InfoList-EnhancedFACH-PCH, dedicated-HS-DSCH-RNTI-priorityQueueInfo-EnhancedFACH PriorityQueue-InfoList-EnhancedFACH-PCH, priorityQueueInfo-EnhancedPCH PriorityQueue-InfoList-EnhancedFACH-PCH OPTIONAL, hSDSCH-Initial-Capacity-Allocation HSDSCH-Initial-Capacity-Allocation, hSDSCH-RNTI HSDSCH-RNTI OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Enhanced-FACH-Information-ResponseLCR-ExtIEs } } ... } Enhanced-FACH-Information-ResponseLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Enhanced-FACH-Support-Indicator ::= NULL EnhancedHSServingCC-Abort ::= ENUMERATED {abortEnhancedHSServingCC,...} Enhanced-PCH-Capability ::= ENUMERATED { enhanced-pch-capable, enhanced-pch-not-capable } E-RNTI ::= INTEGER (0..65535) E-TFCI ::= INTEGER (0..127) E-TFCI-BetaEC-Boost ::= INTEGER (0..127,...) E-TFCI-Boost-Information ::= SEQUENCE { e-TFCI-BetaEC-Boost

OPTIONAL,

OPTIONAL,

E-TFCI-BetaEC-Boost,

3GPP

Release 11

973

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

uL-Delta-T2TP UL-Delta-T2TP OPTIONAL, -- This IE shall be present if the E-TFCI BetaEC Boost IE value is not set to 127. iE-Extensions ProtocolExtensionContainer { { E-TFCI-Boost-Information-ExtIEs} } ...

E-TFCI-Boost-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-TFCS-Information ::= SEQUENCE { e-DCH-TFCI-Table-Index e-DCH-Min-Set-E-TFCI reference-E-TFCI-Information iE-Extensions ... } E-TFCS-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-Minimum-Set-E-TFCIValidityIndicator CRITICALITY reject optional }| { ID id-E-TFCI-Boost-Information CRITICALITY reject PRESENCE optional }| { ID id-E-DPDCH-PowerInterpolation CRITICALITY reject PRESENCE optional }, ... } E-DCH-Minimum-Set-E-TFCIValidityIndicator ::= ENUMERATED { e-DCH-Minimum-Set-E-TFCI-response-not-valid } E-TTI ::= ENUMERATED { tti10, tti2 -- 10ms TTI, 2ms TTI } E-AGCH-PowerOffset ::= INTEGER (0..255,...) -- PowerOffset = -32 + offset * 0.25 -- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB E-RGCH-PowerOffset ::= INTEGER (0..255,...) -- PowerOffset = -32 + offset * 0.25 -- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB E-HICH-PowerOffset ::= INTEGER (0..255,...) -- PowerOffset = -32 + offset * 0.25 -- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB EXTENSION E-DCH-Minimum-Set-E-TFCIValidityIndicator EXTENSION E-TFCI-Boost-Information EXTENSION E-DPDCH-PowerInterpolation PRESENCE E-DCH-TFCI-Table-Index, E-TFCI, Reference-E-TFCI-Information, ProtocolExtensionContainer { {E-TFCS-Information-ExtIEs} }

OPTIONAL,

3GPP

Release 11
Enhanced-PrimaryCPICH-EcNo ::= INTEGER (0..49)

974

3GPP TS 25.423 V11.2.0 (2012-06)

EventA ::= SEQUENCE { measurementTreshold MeasurementThreshold, measurementHysteresisTime MeasurementHysteresisTime OPTIONAL, iE-Extensions ProtocolExtensionContainer { {EventA-ExtIEs} } OPTIONAL, ... } EventA-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventB ::= SEQUENCE { measurementTreshold MeasurementThreshold, measurementHysteresisTime MeasurementHysteresisTime OPTIONAL, iE-Extensions ProtocolExtensionContainer { {EventB-ExtIEs} } OPTIONAL, ... } EventB-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventC ::= SEQUENCE { measurementIncreaseDecreaseThreshold MeasurementIncreaseDecreaseThreshold, measurementChangeTime MeasurementChangeTime, iE-Extensions ProtocolExtensionContainer { {EventC-ExtIEs} } OPTIONAL, ... } EventC-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventD ::= SEQUENCE { measurementIncreaseDecreaseThreshold MeasurementIncreaseDecreaseThreshold, measurementChangeTime MeasurementChangeTime, iE-Extensions ProtocolExtensionContainer { {EventD-ExtIEs} } OPTIONAL, ... } EventD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventE ::= SEQUENCE { measurementThreshold1 measurementThreshold2 measurementHysteresisTime MeasurementThreshold, MeasurementThreshold MeasurementHysteresisTime

OPTIONAL, OPTIONAL,

3GPP

Release 11
reportPeriodicity iE-Extensions ...

975
ReportPeriodicity OPTIONAL, ProtocolExtensionContainer { {EventE-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

EventE-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventF ::= SEQUENCE { measurementThreshold1 MeasurementThreshold, measurementThreshold2 MeasurementThreshold OPTIONAL, measurementHysteresisTime MeasurementHysteresisTime OPTIONAL, reportPeriodicity ReportPeriodicity OPTIONAL, iE-Extensions ProtocolExtensionContainer { {EventF-ExtIEs} } OPTIONAL, ... } EventF-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } EventH ::= SEQUENCE { measurementThreshold1 measurementThreshold2 measurementHysteresisTime reportPeriodicity measurementFluctuationRange iE-Extensions ... } MeasurementThreshold, MeasurementThreshold OPTIONAL, MeasurementHysteresisTime OPTIONAL, ReportPeriodicity OPTIONAL, INTEGER (0..100) OPTIONAL, ProtocolExtensionContainer { {EventH-ExtIEs} } OPTIONAL,

EventH-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Event1F-Parameters ::= SEQUENCE { measurementQuantity MeasurementQuantity, threshold INTEGER(-120..165), ... } Event1I-Parameters threshold ... } ::= SEQUENCE { INTEGER(-120..-25),

ExtendedGSMCellIndividualOffset ::= INTEGER (-50..-11|11..50) E-DCH-Information ::= SEQUENCE { e-PUCH-Information E-PUCH-Information,

3GPP

Release 11
e-TFCS-Information-TDD e-DCH-MACdFlows-Information-TDD e-DCH-TDD-Information iE-Extensions ...

976
E-TFCS-Information-TDD, E-DCH-MACdFlows-Information-TDD, E-DCH-TDD-Information, ProtocolExtensionContainer { { E-DCH-Information-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

E-DCH-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-PUCH-Information minCR maxCR harqInfo n-E-UCCH iE-Extensions ... } ::= SEQUENCE { CodeRate, CodeRate, HARQ-Info-for-E-DCH, N-E-UCCH, ProtocolExtensionContainer { { E-PUCH-Information-ExtIEs } }

OPTIONAL,

E-PUCH-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-TFCS-Information-TDD ::= SEQUENCE { e-DCH-QPSK-RefBetaInfo e-DCH-sixteenQAM-RefBetaInfo iE-Extensions ... } E-DCH-QPSK-RefBetaInfo, E-DCH-sixteenQAM-RefBetaInfo, ProtocolExtensionContainer { { E-TFCS-Information-TDD-ExtIEs } }

OPTIONAL,

E-TFCS-Information-TDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-QPSK-RefBetaInfo ::= SEQUENCE (SIZE (1..maxNrOfRefBetas)) OF E-DCH-RefBeta-Item E-DCH-sixteenQAM-RefBetaInfo ::= SEQUENCE (SIZE (1..maxNrOfRefBetas)) OF E-DCH-RefBeta-Item E-DCH-RefBeta-Item refCodeRate refBeta } ::= SEQUENCE { CodeRate-short, RefBeta ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-InfoTDDItem EDCH-MACdFlow-ID, AllocationRetentionPriority, TnlQos OPTIONAL, BindingID OPTIONAL,

E-DCH-MACdFlows-Information-TDD

E-DCH-MACdFlow-InfoTDDItem ::= SEQUENCE { e-DCH-MACdFlow-ID allocationRetentionPriority tnlQos bindingID

3GPP

Release 11
transportLayerAddress payloadCRC-PresenceIndicator maximum-Number-of-Retransmissions-For-E-DCH eDCH-HARQ-PO-TDD eDCH-MACdFlow-Multiplexing-List eDCH-Grant-TypeTDD eDCHLogicalChannelInformation iE-Extensions ...

977

3GPP TS 25.423 V11.2.0 (2012-06)

TransportLayerAddress OPTIONAL, PayloadCRC-PresenceIndicator, MaxNr-Retransmissions-EDCH, E-DCH-HARQ-PO-TDD, E-DCH-MACdFlow-Multiplexing-List OPTIONAL, E-DCH-Grant-TypeTDD, E-DCH-LogicalChannelInformation, ProtocolExtensionContainer { { E-DCH-MACdFlow-InfoTDDItem-ExtIEs} }

OPTIONAL,

E-DCH-MACdFlow-InfoTDDItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-eDCH-MACdFlow-Retransmission-Timer-LCR CRITICALITY ignore optional }| { ID id-TrafficClass CRITICALITY ignore PRESENCE mandatory}, ... }

EXTENSION E-DCH-MACdFlow-Retransmission-Timer-LCR EXTENSION TrafficClass

PRESENCE

E-DCH-MACdFlow-Retransmission-Timer-LCR ::= ENUMERATED { ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms140, ms160, ms200, ms240, ms280, ms320, ms400, ms480, ms560,... } E-DCH-HARQ-PO-TDD ::= INTEGER (0..6) E-DCH-Grant-TypeTDD ::= ENUMERATED { scheduled, non-scheduled } E-DCH-TimeslotResource ::= BIT STRING (SIZE (13)) E-DCH-PowerResource ::= INTEGER(1..32) TddE-PUCH-Offset ::= INTEGER(0..255) E-DCH-TDD-Information ::= SEQUENCE { e-DCH-TDD-Maximum-Bitrate e-DCH-Processing-Overload-Level e-DCH-PowerOffset-for-SchedulingInfo iE-Extensions ... } E-DCH-TDD-Maximum-Bitrate E-DCH-Processing-Overload-Level E-DCH-PowerOffset-for-SchedulingInfo ProtocolExtensionContainer { { E-DCH-TDD-Information-ExtIEs } } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

E-DCH-TDD-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TDD-Maximum-Bitrate ::= INTEGER (0..9201,...)

3GPP

Release 11
E-DCH-Information-Reconfig ::= SEQUENCE { e-PUCH-Information e-TFCS-Information-TDD e-DCH-MACdFlows-to-Add e-DCH-MACdFlows-to-Delete e-DCH-Non-Scheduled-Grant-Info e-DCH-TDD-Information e-DCH-TDD-Information-to-Modify iE-Extensions ... }

978
E-PUCH-Information E-TFCS-Information-TDD E-DCH-MACdFlows-Information-TDD EDCH-MACdFlows-To-Delete E-DCH-Non-Scheduled-Grant-Info E-DCH-TDD-Information E-DCH-TDD-Information-to-Modify ProtocolExtensionContainer { { E-DCH-Information-Reconfig-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

E-DCH-Information-Reconfig-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TDD-Information-to-Modify ::= SEQUENCE { e-DCH-TDD-Information-to-Modify-List E-DCH-TDD-Information-to-Modify-List OPTIONAL, mACeReset-Indicator MACeReset-Indicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-TDD-Information-to-Modify-ExtIEs } } ... }

OPTIONAL,

E-DCH-TDD-Information-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-DCH-MACdPDUSizeFormat CRITICALITY reject EXTENSION E-DCH-MACdPDUSizeFormat PRESENCE optional}| { ID id-UE-TS0-CapabilityLCR CRITICALITY ignore EXTENSION UE-TS0-CapabilityLCR PRESENCE optional}, ... } E-DCH-TDD-Information-to-Modify-List ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-MACdFlow-ModifyTDDItem E-DCH-MACdFlow-ModifyTDDItem ::= SEQUENCE { e-DCH-MACdFlow-ID allocationRetentionPriority transportBearerRequestIndicator bindingID transportLayerAddress tnlQos maximum-Number-of-Retransmissions-For-E-DCH eDCH-HARQ-PO-TDD eDCH-MACdFlow-Multiplexing-List eDCH-Grant-TypeTDD e-DCH-LogicalChannelToAdd e-DCH-LogicalChannelToModify e-DCH-LogicalChannelToDelete iE-Extensions ... } EDCH-MACdFlow-ID, AllocationRetentionPriority OPTIONAL, TransportBearerRequestIndicator, BindingID OPTIONAL, TransportLayerAddress OPTIONAL, TnlQos OPTIONAL, MaxNr-Retransmissions-EDCH OPTIONAL, E-DCH-HARQ-PO-TDD OPTIONAL, E-DCH-MACdFlow-Multiplexing-List OPTIONAL, E-DCH-Grant-TypeTDD OPTIONAL, E-DCH-LogicalChannelInformation OPTIONAL, E-DCH-LogicalChannelToModify OPTIONAL, E-DCH-LogicalChannelToDelete OPTIONAL, ProtocolExtensionContainer { {E-DCH-MACdFlow-ModifyTDDItem-ExtIEs } }

OPTIONAL,

E-DCH-MACdFlow-ModifyTDDItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
{ ID id-eDCH-MACdFlow-Retransmission-Timer-LCR PRESENCE optional }| { ID id-TrafficClass PRESENCE optional}, ... CRITICALITY ignore CRITICALITY ignore

979
EXTENSION TrafficClass

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION E-DCH-MACdFlow-Retransmission-Timer-LCR

E-DCH-Information-Response ::= SEQUENCE { e-DCH-TDD-MACdFlow-Specific-InformationResp e-AGCH-Specific-Information-ResponseTDD e-HICH-Information-Response e-DCH-Non-Scheduled-Grant-Info e-RNTI iE-Extensions ... }

E-DCH-TDD-MACdFlow-Specific-InformationResp OPTIONAL, E-AGCH-Specific-InformationRespListTDD OPTIONAL, E-HICH-InformationResp OPTIONAL, E-DCH-Non-Scheduled-Grant-Info OPTIONAL, E-RNTI, ProtocolExtensionContainer { { E-DCH-Information-Response-ExtIEs } }

OPTIONAL,

E-DCH-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TDD-MACdFlow-Specific-InformationResp ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF E-DCH-TDD-MACdFlow-Specific-InformationResp-Item E-DCH-TDD-MACdFlow-Specific-InformationResp-Item ::= SEQUENCE { e-DCH-MacdFlow-Id EDCH-MACdFlow-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-TDD-MACdFlow-Specific-InformationRespItem-ExtIEs } } OPTIONAL, ... } E-DCH-TDD-MACdFlow-Specific-InformationRespItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-AGCH-Specific-InformationRespListTDD ::= SEQUENCE (SIZE (1..maxNrOfEAGCHCodes)) OF E-AGCH-Specific-InformationResp-ItemTDD E-AGCH-Specific-InformationResp-ItemTDD ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { { E-AGCH-Specific-InformationResp-ItemTDD-ExtIEs } } ... } E-AGCH-Specific-InformationResp-ItemTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-InformationResp::= SEQUENCE {

OPTIONAL,

3GPP

Release 11
timeslot midambleShiftAndBurstType tDD-ChannelisationCode e-HICH-TimeOffset iE-Extensions ... } E-HICH-InformationResp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-TimeOffset ::= INTEGER (4..44) E-DCH-Non-Scheduled-Grant-Info timeslotResource powerResource repetitionPeriod repetitionLength tddE-PUCH-Offset tdd-ChannelisationCode iE-Extensions ... } ::= SEQUENCE {

980
TimeSlot, MidambleShiftAndBurstType, TDD-ChannelisationCode, E-HICH-TimeOffset, ProtocolExtensionContainer { { E-HICH-InformationResp-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

E-DCH-TimeslotResource, E-DCH-PowerResource, RepetitionPeriod, RepetitionLength, TddE-PUCH-Offset, TDD-ChannelisationCode, ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-Info-ExtIEs } }

OPTIONAL,

E-DCH-Non-Scheduled-Grant-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-768-Information ::= SEQUENCE { e-PUCH-Information e-TFCS-Information-TDD e-DCH-MACdFlows-Information-TDD e-DCH-TDD-Information768 iE-Extensions ... }

E-PUCH-Information, E-TFCS-Information-TDD, E-DCH-MACdFlows-Information-TDD, E-DCH-TDD-Information768, ProtocolExtensionContainer { { E-DCH-768-Information-ExtIEs} }

OPTIONAL,

E-DCH-768-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TDD-Information768 ::= SEQUENCE { e-DCH-TDD-Maximum-Bitrate768 e-DCH-Processing-Overload-Level e-DCH-PowerOffset-for-SchedulingInfo iE-Extensions ... } E-DCH-TDD-Maximum-Bitrate768 E-DCH-Processing-Overload-Level E-DCH-PowerOffset-for-SchedulingInfo ProtocolExtensionContainer { { E-DCH-TDD-Information768-ExtIEs } } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11
E-DCH-TDD-Information768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-TDD-Maximum-Bitrate768 ::= INTEGER (0..17713,...) E-DCH-768-Information-Reconfig ::= SEQUENCE { e-PUCH-Information e-TFCS-Information-TDD e-DCH-MACdFlows-to-Add e-DCH-MACdFlows-to-Delete e-DCH-Non-Scheduled-Grant-Info768 e-DCH-TDD-Information768 e-DCH-TDD-Information-to-Modify iE-Extensions ... }

981

3GPP TS 25.423 V11.2.0 (2012-06)

E-PUCH-Information OPTIONAL, E-TFCS-Information-TDD OPTIONAL, E-DCH-MACdFlows-Information-TDD OPTIONAL, EDCH-MACdFlows-To-Delete OPTIONAL, E-DCH-Non-Scheduled-Grant-Info768 OPTIONAL, E-DCH-TDD-Information768 OPTIONAL, E-DCH-TDD-Information-to-Modify OPTIONAL, ProtocolExtensionContainer { { E-DCH-768-Information-Reconfig-ExtIEs} }

OPTIONAL,

E-DCH-768-Information-Reconfig-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-768-Information-Response ::= SEQUENCE { e-DCH-TDD-MACdFlow-Specific-InformationResp E-DCH-TDD-MACdFlow-Specific-InformationResp OPTIONAL, e-AGCH-Specific-Information-Response768TDD E-AGCH-Specific-InformationRespList768TDD OPTIONAL, e-HICH-Information-Response768 E-HICH-InformationResp768 OPTIONAL, e-DCH-Non-Scheduled-Grant-Info768 E-DCH-Non-Scheduled-Grant-Info768 OPTIONAL, e-RNTI E-RNTI, iE-Extensions ProtocolExtensionContainer { { E-DCH-768-Information-Response-ExtIEs } } ... } E-DCH-768-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-AGCH-Specific-InformationRespList768TDD ::= SEQUENCE (SIZE (1..maxNrOfEAGCHCodes)) OF E-AGCH-Specific-InformationResp-Item768TDD

OPTIONAL,

E-AGCH-Specific-InformationResp-Item768TDD ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, tDD-ChannelisationCode768 TDD-ChannelisationCode768, iE-Extensions ProtocolExtensionContainer { { E-AGCH-Specific-InformationResp-Item768TDD-ExtIEs } } OPTIONAL, ... } E-AGCH-Specific-InformationResp-Item768TDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-InformationResp768::= SEQUENCE {

3GPP

Release 11
timeslot midambleShiftAndBurstType768 tDD-ChannelisationCode768 e-HICH-TimeOffset iE-Extensions ... } E-HICH-InformationResp768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-Non-Scheduled-Grant-Info768 timeslotResource powerResource repetitionPeriod repetitionLength tddE-PUCH-Offset tdd-ChannelisationCode768 iE-Extensions ... }

982
TimeSlot, MidambleShiftAndBurstType768, TDD-ChannelisationCode768, E-HICH-TimeOffset, ProtocolExtensionContainer { { E-HICH-InformationResp768-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

::= SEQUENCE { E-DCH-TimeslotResource, E-DCH-PowerResource, RepetitionPeriod, RepetitionLength, TddE-PUCH-Offset, TDD-ChannelisationCode768, ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-Info768-ExtIEs } }

OPTIONAL,

E-DCH-Non-Scheduled-Grant-Info768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-LCR-Information ::= SEQUENCE { e-PUCH-LCR-Information e-TFCS-Information-TDD e-DCH-MACdFlows-Information-TDD e-DCH-LCR-TDD-Information iE-Extensions ... } E-PUCH-LCR-Information, E-TFCS-Information-TDD, E-DCH-MACdFlows-Information-TDD, E-DCH-LCR-TDD-Information, ProtocolExtensionContainer { { E-DCH-Information-LCR-ExtIEs} }

OPTIONAL,

E-DCH-Information-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-PUCH-LCR-Information ::= SEQUENCE { minCR maxCR harqInfo pRxdesBase e-PUCH-TPC-Step-Size n-E-UCCH-LCR iE-Extensions ... } CodeRate, CodeRate, HARQ-Info-for-E-DCH, E-PUCH-PRXdesBase, TDD-TPC-UplinkStepSize-LCR, N-E-UCCH-LCR, ProtocolExtensionContainer { { E-PUCH-Information-LCR-ExtIEs } }

OPTIONAL,

3GPP

Release 11
E-PUCH-Information-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-E-PUCH-PowerControlGAP CRITICALITY ignore ... } E-PUCH-PRXdesBase --SETP=1 ::= INTEGER(-112..-50)

983
EXTENSION ControlGAP PRESENCE optional },

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-LCR-TDD-Information ::= SEQUENCE { e-DCH-Physical-Layer-Category-LCR e-DCH-Processing-Overload-Level e-DCH-PowerOffset-for-SchedulingInfo iE-Extensions ... }

E-DCH-Physical-Layer-Category-LCR OPTIONAL, E-DCH-Processing-Overload-Level OPTIONAL, E-DCH-PowerOffset-for-SchedulingInfo OPTIONAL, ProtocolExtensionContainer { { E-DCH-LCR-TDD-Information-ExtIEs } } OPTIONAL,

E-DCH-LCR-TDD-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory CRITICALITY reject EXTENSION Extended-E-DCH-LCRTDD-PhysicalLayerCategory PRESENCE optional }| -- This IE shall be used if the E-DCH Physical Layer Category has a value larger than 5. { ID id-MaximumNumber-Of-Retransmission-For-SchedulingInfo-LCRTDD CRITICALITY ignore EXTENSION MaxNr-Retransmissions-EDCH PRESENCE optional }| { ID id-E-DCH-RetransmissionTimer-For-SchedulingInfo-LCRTDD CRITICALITY ignore EXTENSION E-DCH-MACdFlow-Retransmission-Timer-LCR PRESENCE optional }| { ID id-E-AGCH-UE-Inactivity-Monitor-Threshold CRITICALITY ignore EXTENSION E-AGCH-UE-Inactivity-Monitor-Threshold PRESENCE optional }| { ID id-SNPL-Carrier-Group-Indicator CRITICALITY reject EXTENSION SNPL-Carrier-Group-Indicator PRESENCE optional }| { ID id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory CRITICALITY reject EXTENSION Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory PRESENCE optional }| { ID id-UE-TS0-CapabilityLCR CRITICALITY ignore EXTENSION UE-TS0-CapabilityLCR PRESENCE optional }, ... } E-DCH-Physical-Layer-Category-LCR ::= INTEGER (1..5) Extended-E-DCH-LCRTDD-PhysicalLayerCategory ::= INTEGER (6,...) Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory ::= INTEGER (1..8,...) E-DCH-LCR-Information-Reconfig ::= SEQUENCE { e-PUCH-LCR-Information e-TFCS-Information-TDD e-DCH-MACdFlows-to-Add e-DCH-MACdFlows-to-Delete e-DCH-LCR-TDD-Information e-DCH-TDD-Information-to-Modify iE-Extensions ... } E-PUCH-LCR-Information OPTIONAL, E-TFCS-Information-TDD OPTIONAL, E-DCH-MACdFlows-Information-TDD OPTIONAL, EDCH-MACdFlows-To-Delete OPTIONAL, E-DCH-LCR-TDD-Information OPTIONAL, E-DCH-TDD-Information-to-Modify OPTIONAL, ProtocolExtensionContainer { { E-DCH-Information-Reconfig-LCR-ExtIEs} }

OPTIONAL,

3GPP

Release 11
E-DCH-Information-Reconfig-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-LCR-Information-Response ::= SEQUENCE { e-DCH-TDD-MACdFlow-Specific-InformationResp e-AGCH-Specific-Information-Response-LCR-TDD e-HICH-Specific-Information-Response-LCR e-DCH-Non-Scheduled-Grant-Info-LCR e-RNTI iE-Extensions ... }

984

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-TDD-MACdFlow-Specific-InformationResp OPTIONAL, E-AGCH-Specific-InformationRespList-LCR-TDD OPTIONAL, E-HICH-Specific-InformationResp-LCR OPTIONAL, E-DCH-Non-Scheduled-Grant-Info-LCR OPTIONAL, E-RNTI OPTIONAL, ProtocolExtensionContainer { { E-DCH-Information-Response-LCR-ExtIEs } }

OPTIONAL,

E-DCH-Information-Response-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-AGCH-Specific-InformationRespList-LCR-TDD ::= SEQUENCE (SIZE (1..maxNrOfEAGCHCodes)) OF E-AGCH-Specific-InformationResp-Item-LCR-TDD E-AGCH-Specific-InformationResp-Item-LCR-TDD ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { { E-AGCH-Specific-InformationResp-ItemTDD-LCR-ExtIEs } } OPTIONAL, ... } E-AGCH-Specific-InformationResp-ItemTDD-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-Specific-InformationResp-LCR::= SEQUENCE { e-HICH-Scheduled-InformationResp-LCR e-HICH-non-Scheduled-InformationResp-LCR e-HICH-TimeOffset-lcr iE-Extensions ... } E-HICH-Scheduled-InformationRespList-LCR-TDD OPTIONAL, E-HICH-InformationResp-LCR OPTIONAL, E-HICH-TimeOffset-LCR, ProtocolExtensionContainer { { E-HICH-Specific-InformationResp-LCR-ExtIEs } }

OPTIONAL,

E-HICH-Specific-InformationResp-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-Scheduled-InformationRespList-LCR-TDD ::= SEQUENCE (SIZE (1..maxNrOfEHICHCodes)) OF E-HICH-Scheduled-InformationResp-Item-LCR-TDD E-HICH-Scheduled-InformationResp-Item-LCR-TDD ::= SEQUENCE { e-HICH-EI E-HICH-EI,

3GPP

Release 11
e-HICH-Scheduled-InformationResp-LCR iE-Extensions ...

985

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

E-HICH-InformationResp-LCR, ProtocolExtensionContainer { { E-HICH-Scheduled-InformationResp-LCR-ExtIEs } }

E-HICH-Scheduled-InformationResp-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-EI ::= INTEGER (0..3) E-HICH-InformationResp-LCR::= SEQUENCE { timeSlotLCR midambleShiftLCR tDD-ChannelisationCode signatureSequenceGroupIndex iE-Extensions ... } TimeSlotLCR, MidambleShiftLCR, TDD-ChannelisationCode, SignatureSequenceGroupIndex, ProtocolExtensionContainer { { E-HICH-InformationResp-LCR-ExtIEs } }

OPTIONAL,

E-HICH-InformationResp-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-HICH-TimeOffset-LCR ::= INTEGER (4..15) E-DCH-SubframeNumber-LCR ::= ENUMERATED{s0,s1} E-DCH-TimeslotResource-LCR ::= BIT STRING (SIZE (5)) E-DCH-Non-Scheduled-Grant-Info-LCR timeslotResource-LCR powerResource repetitionPeriod repetitionLength subframenumber tddE-PUCH-Offset tdd-ChannelisationCode iE-Extensions ... } ::= SEQUENCE { E-DCH-TimeslotResource-LCR, E-DCH-PowerResource, RepetitionPeriod, RepetitionLength, E-DCH-SubframeNumber-LCR, TddE-PUCH-Offset, TDD-ChannelisationCode, ProtocolExtensionContainer { { E-DCH-Non-Scheduled-Grant-Info-LCR-ExtIEs } }

OPTIONAL,

E-DCH-Non-Scheduled-Grant-Info-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Enabling-Delay ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128}

3GPP

Release 11
-- Unit radio frame Ext-Reference-E-TFCI-PO ::= INTEGER(30..31,...) ExtendedPropagationDelay ::= INTEGER(255..1023) Extended-RNC-ID Extended-RNTI -- From 2^20 to 2^22-1 ::= INTEGER (4096..65535) ::= INTEGER (1048576..4194303,...)

986

3GPP TS 25.423 V11.2.0 (2012-06)

Extended-Round-Trip-Time-Value ::= INTEGER(32767..103041) -- See also mapping in TS 25.133 [23] Extended-S-RNTI-Group ::= SEQUENCE { extended-sRNTI Extended-RNTI, extended-sRNTI-BitMaskIndex ENUMERATED { b1, b2, b3, b4, b5, b6, b7, b8, b9, b10, b11, b12, b13, b14, b15, b16, b17, b18, b19, b20, b21,... } } ExtendedAffectedUEInformationForMBMS ::= SEQUENCE (SIZE (0..maxNrOfUEs)) OF Extended-RNTI

Ext-Max-Bits-MACe-PDU-non-scheduled ::= INTEGER(19983..22978,...) E-DCH-Semi-PersistentScheduling-Information-LCR ::= SEQUENCE { repetition-Period-List-LCR Repetition-Period-List-LCR, e-DCH-SPS-Indicator E-DCH-SPS-Indicator, e-DCH-SPS-Reservation-Indicator SPS-Reservation-Indicator

OPTIONAL,

3GPP

Release 11
iE-Extensions OPTIONAL, ...

987

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-LCR-ExtIEs } }

E-DCH-Semi-PersistentScheduling-Information-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-SPS-Indicator ::= BIT STRING (SIZE (16)) E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR ::= SEQUENCE { repetition-Period-List-LCR Repetition-Period-List-LCR OPTIONAL, e-DCH-SPS-Indicator E-DCH-SPS-Indicator OPTIONAL, e-DCH-SPS-Reservation-Indicator SPS-Reservation-Indicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs } } OPTIONAL, ... } E-DCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-DCH-Semi-PersistentScheduling-Information-ResponseLCR ::= SEQUENCE { initial-E-DCH-SPS-resource Initial-E-DCH-SPS-resource OPTIONAL, e-DCH-SPS-HICH-Information E-DCH-SPS-HICH-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { E-DCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs } } OPTIONAL, ... } E-DCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Initial-E-DCH-SPS-resource ::= SEQUENCE { timeslot-Resource-Related-Information powerResource repetitionPeriodIndex repetitionLength subframeNumber tddE-PUCH-Offset tdd-ChannelisationCode n-E-UCCHLCR iE-Extensions ... } E-DCH-TimeslotResource-LCR, E-DCH-PowerResource, RepetitionPeriodIndex, RepetitionLength, ENUMERATED {v0, v1}, TddE-PUCH-Offset, TDD-ChannelisationCode, N-E-UCCH-LCR, ProtocolExtensionContainer { { Initial-E-DCH-SPS-resource-ExtIEs } }

OPTIONAL,

Initial-E-DCH-SPS-resource-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
}

988

3GPP TS 25.423 V11.2.0 (2012-06)

E-DCH-SPS-HICH-Information ::= SEQUENCE { e-HICH-Configuration signatureSequenceGroupIndex iE-Extensions ... }

E-HICH-Configuration, SignatureSequenceGroupIndex, ProtocolExtensionContainer { { E-DCH-SPS-HICH-Information-ExtIEs } }

OPTIONAL,

E-DCH-SPS-HICH-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

E-HICH-Configuration ::= CHOICE { same-As-Scheduled-E-HICH explicit ... }

Same-As-Scheduled-E-HICH, E-HICH-InformationResp-ExplicitConfiguration-LCR,

Same-As-Scheduled-E-HICH ::= SEQUENCE { e-HICH-EI ... }

E-HICH-EI,

E-HICH-InformationResp-ExplicitConfiguration-LCR ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { { E-HICH-InformationResp-ExplicitConfiguration-LCR-ExtIEs } } OPTIONAL, ... } E-HICH-InformationResp-ExplicitConfiguration-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- F FACH-FlowControlInformation ::= SEQUENCE (SIZE (1..16)) OF FACH-FlowControlInformationItem FACH-FlowControlInformationItem ::= SEQUENCE { fACH-SchedulingPriority SchedulingPriorityIndicator, mAC-c-sh-SDU-Lengths MAC-c-sh-SDU-LengthList, fACH-InitialWindowSize FACH-InitialWindowSize, iE-Extensions ProtocolExtensionContainer { {FACH-FlowControlInformationItem-ExtIEs} } OPTIONAL,

3GPP

Release 11
} ...

989

3GPP TS 25.423 V11.2.0 (2012-06)

FACH-FlowControlInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FACH-InitialWindowSize ::= INTEGER { unlimited(255) } (0..255) -- Number of frames MAC-c-sh SDUs. -- 255 = Unlimited number of FACH data frames FACH-InformationList ::= SEQUENCE (SIZE(0.. maxNrOfFACHs)) OF FACH-InformationItem FACH-InformationItem ::= SEQUENCE { transportFormatSet TransportFormatSet, iE-Extensions ProtocolExtensionContainer { { FACH-InformationItem-ExtIEs} } OPTIONAL, ... } FACH-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Fast-Reconfiguration-Mode ::= ENUMERATED {fast,...} Fast-Reconfiguration-Permission ::= ENUMERATED {allowed,...} FDD-DCHs-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF FDD-DCHs-to-ModifyItem UL-FP-Mode OPTIONAL, ToAWS OPTIONAL, ToAWE OPTIONAL, TransportBearerRequestIndicator, FDD-DCHs-to-ModifySpecificInformationList, ProtocolExtensionContainer { {FDD-DCHs-to-ModifyItem-ExtIEs} } OPTIONAL,

FDD-DCHs-to-ModifyItem ::= SEQUENCE { ul-FP-Mode toAWS toAWE transportBearerRequestIndicator dCH-SpecificInformationList iE-Extensions ... }

FDD-DCHs-to-ModifyItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TnlQos CRITICALITY ignore ... }

EXTENSION

TnlQos

PRESENCE optional

},

FDD-DCHs-to-ModifySpecificInformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF FDD-DCHs-to-ModifySpecificItem FDD-DCHs-to-ModifySpecificItem ::= dCH-ID ul-TransportformatSet dl-TransportformatSet allocationRetentionPriority SEQUENCE { DCH-ID, TransportFormatSet OPTIONAL, TransportFormatSet OPTIONAL, AllocationRetentionPriority OPTIONAL,

3GPP

Release 11
frameHandlingPriority not-Used-dRACControl iE-Extensions ... } FDD-DCHs-to-ModifySpecificItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Guaranteed-Rate-Information CRITICALITY ignore }| { ID id-TrafficClass CRITICALITY ignore { ID id-Unidirectional-DCH-Indicator CRITICALITY reject ... }

990
FrameHandlingPriority OPTIONAL, NULL OPTIONAL, ProtocolExtensionContainer { {FDD-DCHs-to-ModifySpecificItem-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION Guaranteed-Rate-Information EXTENSION TrafficClass EXTENSION Unidirectional-DCH-Indicator

PRESENCE optional PRESENCE optional }| PRESENCE optional},

FDD-DL-ChannelisationCodeNumber ::= INTEGER (0..511) -- According to the mapping in TS 25.213 [27]. The maximum value is equal to the DL spreading factor -1-FDD-DL-CodeInformation ::= SEQUENCE (SIZE (1..maxNrOfDL-Codes)) OF FDD-DL-CodeInformationItem FDD-DL-CodeInformationItem ::= SEQUENCE { dl-ScramblingCode DL-ScramblingCode, fDD-DL-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber, transmission-Gap-Pattern-Sequence-ScramblingCode-Information Transmission-Gap-Pattern-Sequence-ScramblingCode-Information iE-Extensions ProtocolExtensionContainer { {FDD-DL-CodeInformationItem-ExtIEs} } OPTIONAL, ... } FDD-DL-CodeInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FDD-TPC-DownlinkStepSize ::= ENUMERATED { step-size0-5, step-size1, step-size1-5, step-size2, ... } SchedulingPriorityIndicator F-DPCH-SlotFormat ::= INTEGER (0..9) F-DPCH-SlotFormatSupportRequest ::= NULL FirstRLS-Indicator ::= ENUMERATED { first-RLS, not-first-RLS } FNReportingIndicator ::= ENUMERATED { ::= INTEGER { lowest(0), highest(15) } (0..15)

OPTIONAL,

3GPP

Release 11
fN-reporting-required, fN-reporting-not-required } FPACH-Information ::= SEQUENCE { timeSlotLCR TimeSlotLCR, tDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, midambleShiftLCR MidambleShiftLCR, wT INTEGER (1..4), ... } FTPICH-Information ::= SEQUENCE { fTPICH-SlotFormat fTPICH-Offset fTPICH-ChannelisationCodenumber iE-Extensions ... }

991

3GPP TS 25.423 V11.2.0 (2012-06)

FTPICH-SlotFormat, FTPICH-Offset, FDD-DL-ChannelisationCodeNumber, ProtocolExtensionContainer { { FTPICH-Information-ExtIEs } }

OPTIONAL,

FTPICH-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FTPICH-SlotFormat ::= INTEGER (0..9,...) FTPICH-Offset ::= INTEGER (0..149) FTPICH-Information-Removal ::= ENUMERATED { remove, ... } FTPICH-Information-To-Modify ::= SEQUENCE { fTPICH-SlotFormat FTPICH-SlotFormat OPTIONAL, fTPICH-Offset FTPICH-Offset OPTIONAL, fTPICH-ChannelisationCodeNumber FDD-DL-ChannelisationCodeNumber OPTIONAL, iE-Extensions ProtocolExtensionContainer { { FTPICH-Information-To-Modify-ExtIEs } } ... } FTPICH-Information-To-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } FTPICH-Information-Reconf ::=SEQUENCE{ setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information iE-Extensions ... } Setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information, ProtocolExtensionContainer { { FTPICH-Information-Reconf-ExtIEs} } OPTIONAL,

OPTIONAL,

3GPP

Release 11
FTPICH-Information-Reconf-ExtIEs ... } FrameHandlingPriority FrameOffset -- Frames FrequencyBandIndicator bandI, bandII, bandIII, bandIV, bandV, bandVI, bandVII, bandVIII, bandIX, bandX, bandXI, bandXII, bandXIII, bandXIV, bandXV, bandXVI, bandXVII, bandXVIII, bandXIX, bandXX, bandXXI, bandXXII, ..., reserved23, reserved24, bandXXV, bandXXVI } -- G GapLength -- Unit Slot GapDuration -- Unit Frame ::= INTEGER (1..14) ::= INTEGER (1..144,...) RNSAP-PROTOCOL-EXTENSION ::= {

992

3GPP TS 25.423 V11.2.0 (2012-06)

::= INTEGER { lowest(0), highest(15) } (0..15) ::= INTEGER (0..255) ::= ENUMERATED {

GA-Cell ::= SEQUENCE (SIZE (1..maxNrOfPoints)) OF SEQUENCE { cell-GAIgeographicalCoordinate GeographicalCoordinate,

3GPP

Release 11
iE-Extensions ... } GA-Cell-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GA-CellAdditionalShapes ::= CHOICE { pointWithUncertainty pointWithUncertaintyEllipse pointWithAltitude pointWithAltitudeAndUncertaintyEllipsoid ellipsoidArc ... }

993
ProtocolExtensionContainer { {GA-Cell-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

GA-PointWithUnCertainty, GA-PointWithUnCertaintyEllipse, GA-PointWithAltitude, GA-PointWithAltitudeAndUncertaintyEllipsoid, GA-EllipsoidArc,

GA-AltitudeAndDirection ::= SEQUENCE { directionOfAltitude ENUMERATED {height, depth}, altitude INTEGER (0..32767), ... } GA-EllipsoidArc ::= SEQUENCE { geographicalCoordinates innerRadius uncertaintyRadius offsetAngle includedAngle confidence iE-Extensions ... } GeographicalCoordinate, INTEGER (0..65535), INTEGER (0..127), INTEGER (0..179), INTEGER (0..179), INTEGER (0..127), ProtocolExtensionContainer { { GA-EllipsoidArc-ExtIEs} } OPTIONAL,

GA-EllipsoidArc-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-AddClockModels ::= CHOICE { navClockModel cnavClockModel glonassClockModel sbasClockModel ... } GANSS-NAVclockModel, GANSS-CNAVclockModel, GANSS-GLONASSclockModel, GANSS-SBASclockModel,

GANSS-AddIonoModelReq ::= BIT STRING (SIZE(2)) GANSS-AddNavigationModelsReq ::= BOOLEAN GANSS-AddOrbitModels ::= CHOICE {

3GPP

Release 11
navKeplerianSet cnavKeplerianSet glonassECEF sbasECEF ... } GANSS-AddUTCModelsReq ::= BOOLEAN GANSS-NavModel-NAVKeplerianSet, GANSS-NavModel-CNAVKeplerianSet, GANSS-NavModel-GLONASSecef, GANSS-NavModel-SBASecef,

994

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-Additional-Ionospheric-Model ::= SEQUENCE { dataID BIT STRING (SIZE(2)), alpha-beta-parameters GPS-Ionospheric-Model, ie-Extensions ProtocolExtensionContainer { { GANSS-Additional-Ionospheric-Model-ExtIEs } } ... } GANSS-Additional-Ionospheric-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Additional-Navigation-Models ::= SEQUENCE { ganss-Transmission-Time GANSS-Transmission-Time, non-broadcastIndication ENUMERATED { true } ganssSatInfoNavList Ganss-Sat-Info-AddNavList, ie-Extensions ProtocolExtensionContainer { { GANSS-Additional-Navigation-Models-ExtIEs } } OPTIONAL, ... } GANSS-Additional-Navigation-Models-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Additional-Time-Models ::= SEQUENCE (SIZE (1..maxGANSS-1)) OF GANSS-Time-Model GANSS-Additional-UTC-Models ::= CHOICE { utcModel1 GANSS-UTCmodelSet1, utcModel2 GANSS-UTCmodelSet2, utcModel3 GANSS-UTCmodelSet3, ... } GANSS-Almanac ::= SEQUENCE{ ganss-wk-number INTEGER(0..255), gANSS-AlmanacModel CHOICE { gANSS-keplerianParameters SEQUENCE { t-oa INTEGER(0..255), iod-a INTEGER(0..3), gANSS-SatelliteInformationKP GANSS-SatelliteInformationKP,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
ie-Extensions ... }, ..., extension-GANSS-AlmanacModel }, ie-Extensions ... } GANSS-KeplerianParametersAlm-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Extension-GANSS-AlmanacModel

995

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { GANSS-KeplerianParametersAlm-ExtIEs } } OPTIONAL,

Extension-GANSS-AlmanacModel OPTIONAL,

ProtocolExtensionContainer { { GANSS-Almanac-ExtIEs } }

::= ProtocolIE-Single-Container {{ Extension-GANSS-AlmanacModel-IE }} ignore ignore ignore ignore ignore TYPE TYPE TYPE TYPE TYPE GANSS-alm-keplerianNAVAlmanac GANSS-alm-keplerianReducedAlmanac GANSS-alm-keplerianMidiAlmanac GANSS-alm-keplerianGLONASS GANSS-alm-ecefSBASAlmanac PRESENCE PRESENCE PRESENCE

Extension-GANSS-AlmanacModel-IE RNSAP-PROTOCOL-IES ::= { { ID id-GANSS-alm-keplerianNAVAlmanac CRITICALITY mandatory}| { ID id-GANSS-alm-keplerianReducedAlmanac CRITICALITY mandatory}| { ID id-GANSS-alm-keplerianMidiAlmanac CRITICALITY mandatory}| { ID id-GANSS-alm-keplerianGLONASS CRITICALITY PRESENCE mandatory}| { ID id-GANSS-alm-ecefSBASAlmanac CRITICALITY PRESENCE mandatory} }

GANSS-alm-keplerianNAVAlmanac ::= SEQUENCE { t-oa INTEGER (0..255), sat-info-NAVkpList GANSS-SAT-Info-Almanac-NAVkpList, ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-NAVKeplerianSet-ExtIEs } } ... } GANSS-ALM-NAVKeplerianSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-alm-keplerianReducedAlmanac ::= SEQUENCE { t-oa INTEGER (0..255),

OPTIONAL,

3GPP

Release 11
sat-info-REDkpList ie-Extensions ... }

996
GANSS-SAT-Info-Almanac-REDkpList, ProtocolExtensionContainer { { GANSS-ALM-ReducedKeplerianSet-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GANSS-ALM-ReducedKeplerianSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-alm-keplerianMidiAlmanac ::= SEQUENCE { t-oa INTEGER (0..255), sat-info-MIDIkpList GANSS-SAT-Info-Almanac-MIDIkpList, ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-MidiAlmanacSet-ExtIEs } } ... } GANSS-ALM-MidiAlmanacSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-alm-keplerianGLONASS ::= SEQUENCE { sat-info-GLOkpList GANSS-SAT-Info-Almanac-GLOkpList, ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-GlonassAlmanacSet-ExtIEs } } ... } GANSS-ALM-GlonassAlmanacSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-alm-ecefSBASAlmanac ::= SEQUENCE { sat-info-SBASecefList GANSS-SAT-Info-Almanac-SBASecefList, ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs } } ... } GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
GANSS-Almanac-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-completeAlmanacProvided CRITICALITY ignore ... } GANSS-Auxiliary-Information ::= CHOICE { ganssID1 GANSS-AuxInfoGANSS-ID1, ganssID3 GANSS-AuxInfoGANSS-ID3, ... EXTENSION

997
CompleteAlmanacProvided PRESENCE

3GPP TS 25.423 V11.2.0 (2012-06)

optional},

-- This choice may only be present if GANSS ID indicates Modernized GPS -- This choice may only be present if GANSS ID indicates GLONASS

}
GANSS-AuxInfoGANSS-ID1 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF SEQUENCE { svID INTEGER(0..63), signalsAvailable BIT STRING (SIZE(8)), ie-Extensions ProtocolExtensionContainer { { GANSS-AuxInfoGANSS-ID1-element-ExtIEs } } OPTIONAL, ... } GANSS-AuxInfoGANSS-ID1-element-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-AuxInfoGANSS-ID3 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF SEQUENCE { svID INTEGER(0..63), signalsAvailable BIT STRING (SIZE(8)), channelNumber INTEGER (-7..13), ie-Extensions ProtocolExtensionContainer { { GANSS-AuxInfoGANSS-ID3-element-ExtIEs } } OPTIONAL, ... } GANSS-AuxInfoGANSS-ID3-element-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-AuxInfoReq ::= BOOLEAN GANSS-Clock-Model ::= SEQUENCE (SIZE (1..maxGANSSClockMod)) OF SEQUENCE { t-oc BIT STRING (SIZE (14)), a-i2 BIT STRING (SIZE (12)), a-i1 BIT STRING (SIZE (18)), a-i0 BIT STRING (SIZE (28)), t-gd BIT STRING (SIZE (10)) model-id INTEGER(0..1,...) ie-Extensions ProtocolExtensionContainer { { GANSS-ClockModelItem-ExtIEs } } ... }

OPTIONAL, OPTIONAL, OPTIONAL,

3GPP

Release 11
GANSS-ClockModelItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

998

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-CNAVclockModel ::= SEQUENCE { cnavToc BIT STRING (SIZE (11)), cnavTop BIT STRING (SIZE (11)), cnavURA0 BIT STRING (SIZE (5)), cnavURA1 BIT STRING (SIZE (3)), cnavURA2 BIT STRING (SIZE (3)), cnavAf2 BIT STRING (SIZE (10)), cnavAf1 BIT STRING (SIZE (20)), cnavAf0 BIT STRING (SIZE (26)), cnavTgd BIT STRING (SIZE (13)), cnavISCl1cp BIT STRING (SIZE (13)) cnavISCl1cd BIT STRING (SIZE (13)) cnavISCl1ca BIT STRING (SIZE (13)) cnavISCl2c BIT STRING (SIZE (13)) cnavISCl5i5 BIT STRING (SIZE (13)) cnavISCl5q5 BIT STRING (SIZE (13)) ie-Extensions ProtocolExtensionContainer { { GANSS-CNAVclockModel-ExtIEs } } ... } GANSS-CNAVclockModel-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Common-Data ::= SEQUENCE { ganss-Ionospheric-Model ganss-Rx-Pos ie-Extensions ... }

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

GANSS-Ionospheric-Model GANSS-RX-Pos ProtocolExtensionContainer { { GANSS-Common-Data-ExtIEs } }

OPTIONAL, OPTIONAL, OPTIONAL,

GANSS-Common-Data-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GANSS-Additional-Ionospheric-Model CRITICALITY ignore { ID id-GANSS-Earth-Orientation-Parameters CRITICALITY ignore ... } GANSS-CommonDataInfoReq ::= SEQUENCE { ionospheric-Model ie-Extensions ... }

EXTENSION GANSS-Additional-Ionospheric-Model EXTENSION GANSS-Earth-Orientation-Parameters

PRESENCE optional }| PRESENCE optional },

BOOLEAN ProtocolExtensionContainer { { GANSS-CommonDataInfoReq-ExtIEs } }

OPTIONAL, OPTIONAL,

3GPP

Release 11
GANSS-CommonDataInfoReq-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-GANSS-AddIonoModelReq CRITICALITY ignore EXTENSION optional} | {ID id-GANSS-EarthOrientParaReq ... } CRITICALITY ignore EXTENSION

999
GANSS-AddIonoModelReq GANSS-EarthOrientParaReq

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE PRESENCE optional} ,

GANSS-Data-Bit-Assistance ::= SEQUENCE { ganssTod INTEGER (0..59,...), dataBitAssistancelist GANSS-DataBitAssistanceList, ie-Extensions ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ExtIEs } } ... } GANSS-Data-Bit-Assistance-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-DataBitAssistanceList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-DataBitAssistanceItem GANSS-DataBitAssistanceItem ::= SEQUENCE { satId INTEGER(0..63), dataBitAssistanceSgnList GANSS-DataBitAssistanceSgnList, ie-Extensions ProtocolExtensionContainer { { GANSS-DataBitAssistanceItem-ExtIEs } } ... } GANSS-DataBitAssistanceItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-DataBitAssistanceSgnList ::= SEQUENCE (SIZE (1..maxSgnType)) OF GANSS-DataBitAssistanceSgnItem GANSS-DataBitAssistanceSgnItem ::= SEQUENCE { ganss-SignalId GANSS-Signal-ID, ganssDataBits BIT STRING (SIZE (1..1024)), ie-Extensions ProtocolExtensionContainer { { GANSS-DataBitAssistanceSgnItem-ExtIEs } } ... } GANSS-DataBitAssistanceSgnItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Data-Bit-Assistance-ReqItem ::= SEQUENCE { ganssTod INTEGER (0..86399), ganss-Data-Bit-Assistance-ReqList GANSS-Data-Bit-Assistance-ReqList,

OPTIONAL,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
iE-Extensions ... } GANSS-Data-Bit-Assistance-ReqItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1000

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ReqItem-ExtIEs } } OPTIONAL,

GANSS-Data-Bit-Assistance-ReqList ::= SEQUENCE { dGANSS-Signal-ID BIT STRING (SIZE (8)), ganss-DataBitInterval INTEGER(0..15), ganss-SatelliteInfo SEQUENCE (SIZE (1..maxGANSSSat)) OF INTEGER(0..63) OPTIONAL, iE-Extensions ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ReqList-ExtIEs } } OPTIONAL, ... } GANSS-Data-Bit-Assistance-ReqList-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Delta-T ::= INTEGER(-128..127)

GANSS-DeltaUT1 ::= SEQUENCE { b1 BIT STRING (SIZE(11)), b2 BIT STRING (SIZE(10)), ie-Extensions ProtocolExtensionContainer { { GANSS-DeltaUT1-ExtIEs } } ... } GANSS-DeltaUT1-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

GANSS-Earth-Orientation-Parameters ::= SEQUENCE { teop BIT STRING (SIZE (16)), pmX BIT STRING (SIZE (21)), pmXdot BIT STRING (SIZE (15)), pmY BIT STRING (SIZE (21)), pmYdot BIT STRING (SIZE (15)), deltaUT1 BIT STRING (SIZE (31)), deltaUT1dot BIT STRING (SIZE (19)), ie-Extensions ProtocolExtensionContainer { { GANSS-Earth-Orientation-Parameters-ExtIEs } } ... } GANSS-Earth-Orientation-Parameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-EarthOrientParaReq ::= BOOLEAN

OPTIONAL,

3GPP

Release 11

1001

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-GenericDataInfoReqList ::= SEQUENCE (SIZE(1..maxNoGANSS)) OF GANSS-GenericDataInfoReqItem GANSS-GenericDataInfoReqItem ::= SEQUENCE { ganss-Id OPTIONAL, ganss-Navigation-Model-And-Time-Recovery ganss-Time-Model-GNSS-GNSS ganss-UTC-Model ganss-Almanac ganss-Real-Time-Integrity ganss-Data-Bit-Assistance-Req ie-Extensions ... } GANSS-ID BOOLEAN BIT STRING (SIZE (9)) BOOLEAN BOOLEAN BOOLEAN GANSS-Data-Bit-Assistance-ReqItem ProtocolExtensionContainer { { GANSS-GenericDataInfoReqItem-ExtIEs } } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

GANSS-GenericDataInfoReqItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-GANSS-AddNavigationModelsReq CRITICALITY ignore EXTENSION GANSS-AddNavigationModelsReq {ID id-GANSS-AddUTCModelsReq CRITICALITY ignore EXTENSION GANSS-AddUTCModelsReq {ID id-GANSS-AuxInfoReq CRITICALITY ignore EXTENSION GANSS-AuxInfoReq -- The following IE shall be present if GANSS-ID in GANSS-GenericDataInfoReqItem is 0 (SBAS) {ID id-GANSS-SBAS-ID CRITICALITY ignore EXTENSION GANSS-SBAS-ID PRESENCE ... } GANSS-Generic-Data ::= SEQUENCE (SIZE(1..maxNoGANSS)) OF GANSS-Generic-DataItem GANSS-Generic-DataItem ::= SEQUENCE { ganss-Id OPTIONAL, dganss-Correction OPTIONAL, ganss-Navigation-Model-And-Time-Recovery OPTIONAL, ganss-Time-Model OPTIONAL, ganss-UTC-TIME OPTIONAL, ganss-Almanac OPTIONAL, ganss-Real-Time-Integrity OPTIONAL, ganss-Data-Bit-Assistance OPTIONAL, ie-Extensions ... } GANSS-ID DGANSSCorrections GANSS-Navigation-Model-And-Time-Recovery GANSS-Time-Model GANSS-UTC-Model GANSS-Almanac GANSS-Real-Time-Integrity GANSS-Data-Bit-Assistance ProtocolExtensionContainer { { GANSS-Generic-DataItem-ExtIEs } }

PRESENCE PRESENCE PRESENCE optional} ,

optional} | optional} | optional} |

OPTIONAL,

3GPP

Release 11

1002

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional }| PRESENCE optional }| PRESENCE PRESENCE

GANSS-Generic-DataItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GANSS-Additional-Time-Models CRITICALITY ignore EXTENSION GANSS-Additional-Time-Models { ID id-GANSS-Additional-Navigation-Models CRITICALITY ignore EXTENSION GANSS-Additional-Navigation-Models { ID id-GANSS-Additional-UTC-Models CRITICALITY ignore EXTENSION GANSS-Additional-UTC-Models optional }| { ID id-GANSS-Auxiliary-Information CRITICALITY ignore EXTENSION GANSS-Auxiliary-Information optional }| -- The following element shall be present if GANSS-ID in GANSS-Generic-DataItem is 0 (SBAS) { ID id-GANSS-SBAS-ID CRITICALITY ignore EXTENSION GANSS-SBAS-ID ... } GANSS-GLONASSclockModel ::= SEQUENCE { gloTau BIT STRING (SIZE (22)), gloGamma BIT STRING (SIZE (11)), gloDeltaTau BIT STRING (SIZE (5)) ie-Extensions ProtocolExtensionContainer { { GANSS-GLONASSclockModel-ExtIEs } } ... } GANSS-GLONASSclockModel-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-ID ::= INTEGER(0..7,...) GANSS-Information ::= SEQUENCE { gANSS-CommonDataInfoReq gANSS-GenericDataInfoReqList ie-Extensions ... } GANSS-CommonDataInfoReq GANSS-GenericDataInfoReqList ProtocolExtensionContainer { { GANSS-Information-ExtIEs } }

PRESENCE optional },

OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL,

GANSS-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Ionospheric-Model ::= SEQUENCE { alpha-zero-ionos alpha-one-ionos alpha-two-ionos gANSS-IonosphereRegionalStormFlags ie-Extensions ... }

BIT STRING (SIZE (12)), BIT STRING (SIZE (12)), BIT STRING (SIZE (12)), GANSS-IonosphereRegionalStormFlags ProtocolExtensionContainer { { GANSS-Ionospheric-Model-ExtIEs } }

OPTIONAL, OPTIONAL,

3GPP

Release 11
GANSS-Ionospheric-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1003

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-IonosphereRegionalStormFlags ::= SEQUENCE { storm-flag-one BOOLEAN, storm-flag-two BOOLEAN, storm-flag-three BOOLEAN, storm-flag-four BOOLEAN, storm-flag-five BOOLEAN, ie-Extensions ProtocolExtensionContainer { { GANSS-IonosphereRegionalStormFlags-ExtIEs } } OPTIONAL, ... } GANSS-IonosphereRegionalStormFlags-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-NAVclockModel ::= SEQUENCE { navToc BIT STRING (SIZE (16)), navaf2 BIT STRING (SIZE (8)), navaf1 BIT STRING (SIZE (16)), navaf0 BIT STRING (SIZE (22)), navTgd BIT STRING (SIZE (8)), ie-Extensions ProtocolExtensionContainer { { GANSS-NAVclockModel-ExtIEs } } ... } GANSS-NAVclockModel-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Navigation-Model-And-Time-Recovery ::= SEQUENCE { ganss-Transmission-Time GANSS-Transmission-Time, non-broadcastIndication ENUMERATED{true} OPTIONAL, ganssSatInfoNav GANSS-Sat-Info-Nav, ie-Extensions ProtocolExtensionContainer { { GANSS-Navigation-Model-And-Time-Recovery-ExtIEs } } OPTIONAL, ... } GANSS-Navigation-Model-And-Time-Recovery-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-NavModel-CNAVKeplerianSet ::= SEQUENCE { cnavTop BIT STRING (SIZE (11)), cnavURAindex BIT STRING (SIZE (5)),

OPTIONAL,

3GPP

Release 11
cnavDeltaA cnavAdot cnavDeltaNo cnavDeltaNoDot cnavMo cnavE cnavOmega cnavOMEGA0 cnavDeltaOmegaDot cnavIo cnavIoDot cnavCis cnavCic cnavCrs cnavCrc cnavCus cnavCuc ie-Extensions ... } GANSS-NavModel-CNAVKeplerianSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1004
BIT STRING (SIZE (26)), BIT STRING (SIZE (25)), BIT STRING (SIZE (17)), BIT STRING (SIZE (23)), BIT STRING (SIZE (33)), BIT STRING (SIZE (33)), BIT STRING (SIZE (33)), BIT STRING (SIZE (33)), BIT STRING (SIZE (17)), BIT STRING (SIZE (33)), BIT STRING (SIZE (15)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (24)), BIT STRING (SIZE (24)), BIT STRING (SIZE (21)), BIT STRING (SIZE (21)), ProtocolExtensionContainer { { GANSS-NavModel-CNAVKeplerianSet-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GANSS-NavModel-GLONASSecef ::= SEQUENCE { gloEn BIT STRING (SIZE (5)), gloP1 BIT STRING (SIZE(2)), gloP2 BIT STRING (SIZE (1)), gloM BIT STRING (SIZE (2)) gloX BIT STRING (SIZE (27)), gloXdot BIT STRING (SIZE (24)), gloXdotdot BIT STRING (SIZE (5)), gloY BIT STRING (SIZE (27)), gloYdot BIT STRING (SIZE (24)), gloYdotdot BIT STRING (SIZE (5)), gloZ BIT STRING (SIZE (27)), gloZdot BIT STRING (SIZE (24)), gloZdotdot BIT STRING (SIZE (5)), ie-Extensions ProtocolExtensionContainer { { GANSS-NavModel-GLONASSecef-ExtIEs } } ... } GANSS-NavModel-GLONASSecef-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL,

GANSS-NavModel-NAVKeplerianSet ::= SEQUENCE { navURA BIT STRING (SIZE (4)),

3GPP

Release 11
navFitFlag navToe navOmega navDeltaN navM0 navOmegaADot navE navIDot navAPowerHalf navI0 navOmegaA0 navCrs navCis navCus navCrc navCic navCuc ie-Extensions ... } GANSS-NavModel-NAVKeplerianSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1005
BIT STRING (SIZE (1)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (24)), BIT STRING (SIZE (32)), BIT STRING (SIZE (14)), BIT STRING (SIZE (32)), BIT STRING (SIZE (32)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), ProtocolExtensionContainer { { GANSS-NavModel-NAVKeplerianSet-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GANSS-NavModel-SBASecef ::= SEQUENCE { -- the following IE shall be present if GANSS-SBASclockModel in GANSS-AddClockModels is not included in Ganss-Sat-Info-AddNavList sbasTo BIT STRING (SIZE (13)) OPTIONAL, sbasAccuracy BIT STRING (SIZE (4)), sbasXg BIT STRING (SIZE (30)), sbasYg BIT STRING (SIZE (30)), sbasZg BIT STRING (SIZE (25)), sbasXgDot BIT STRING (SIZE (17)), sbasYgDot BIT STRING (SIZE (17)), sbasZgDot BIT STRING (SIZE (18)), sbasXgDotDot BIT STRING (SIZE (10)), sbagYgDotDot BIT STRING (SIZE (10)), sbasZgDotDot BIT STRING (SIZE (10)), ie-Extensions ProtocolExtensionContainer { { GANSS-NavModel-SBASecef-ExtIEs } } OPTIONAL, ... }

GANSS-NavModel-SBASecef-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Orbit-Model ::= CHOICE { gANSS-keplerianParameters

SEQUENCE {

3GPP

Release 11
toe-nav ganss-omega-nav delta-n-nav m-zero-nav omegadot-nav ganss-e-nav idot-nav a-sqrt-nav i-zero-nav omega-zero-nav c-rs-nav c-is-nav c-us-nav c-rc-nav c-ic-nav c-uc-nav ie-Extensions ... }, ... } GANSS-KeplerianParametersOrb-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1006
BIT STRING (SIZE (14)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (24)), BIT STRING (SIZE (32)), BIT STRING (SIZE (14)), BIT STRING (SIZE (32)), BIT STRING (SIZE (32)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), ProtocolExtensionContainer { { GANSS-KeplerianParametersOrb-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GANSS-Real-Time-Integrity ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { bad-ganss-satId INTEGER(0..63), bad-ganss-signalId BIT STRING(SIZE(8)) ie-Extensions ProtocolExtensionContainer { { GANSS-RealTimeInformationItem-ExtIEs } } ... } GANSS-RealTimeInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-RX-Pos ::= SEQUENCE { latitudeSign ENUMERATED{north,south}, degreesOfLatitude INTEGER(0..2147483647), degreesOfLongitude INTEGER(-2147483648..2147483647), directionOfAltitude ENUMERATED{height,depth}, altitude INTEGER(0..32767), ie-Extensions ProtocolExtensionContainer { { GANSS-RX-Pos-ExtIEs } } ...

OPTIONAL, OPTIONAL,

OPTIONAL,

3GPP

Release 11
} GANSS-RX-Pos-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1007

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-SatelliteInformationKP ::= SEQUENCE (SIZE (1..maxGANSSSatAlmanac)) OF SEQUENCE { satId INTEGER(0..63), ganss-e-alm BIT STRING (SIZE (11)), ganss-delta-I-alm BIT STRING (SIZE (11)), ganss-omegadot-alm BIT STRING (SIZE (11)), ganss-svhealth-alm BIT STRING (SIZE (4)), ganss-delta-a-sqrt-alm BIT STRING (SIZE (17)), ganss-omegazero-alm BIT STRING (SIZE (16)), ganss-m-zero-alm BIT STRING (SIZE (16)), ganss-omega-alm BIT STRING (SIZE (16)), ganss-af-zero-alm BIT STRING (SIZE (14)), ganss-af-one-alm BIT STRING (SIZE (11)), ie-Extensions ProtocolExtensionContainer { { GANSS-SatelliteInformationKPItem-ExtIEs } } OPTIONAL, ... } GANSS-SatelliteInformationKPItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Ganss-Sat-Info-AddNavList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { satId INTEGER (0..63), svHealth BIT STRING (SIZE (6)), iod BIT STRING (SIZE (11)), ganssAddClockModels GANSS-AddClockModels, ganssAddOrbitModels GANSS-AddOrbitModels, ie-Extensions ProtocolExtensionContainer { { Ganss-Sat-Info-AddNavList-ExtIEs } } OPTIONAL, ... } Ganss-Sat-Info-AddNavList-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-SAT-Info-Almanac-GLOkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF SEQUENCE { gloAlmNA BIT STRING (SIZE(11)), gloAlmnA BIT STRING (SIZE(5)), gloAlmHA BIT STRING (SIZE(5)), gloAlmLambdaA BIT STRING (SIZE(21)), gloAlmTlambdaA BIT STRING (SIZE(21)), gloAlmDeltaIA BIT STRING (SIZE(18)),

3GPP

Release 11
gloAkmDeltaTA gloAlmDeltaTdotA gloAlmEpsilonA gloAlmOmegaA gloAlmTauA gloAlmCA gloAlmMA ie-Extensions ... } GANSS-SAT-Info-Almanac-GLOkp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1008
BIT STRING (SIZE(22)), BIT STRING (SIZE(7)), BIT STRING (SIZE(15)), BIT STRING (SIZE(16)), BIT STRING (SIZE(10)), BIT STRING (SIZE(1)), BIT STRING (SIZE(2)) ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-GLOkp-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL, OPTIONAL,

GANSS-SAT-Info-Almanac-MIDIkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF SEQUENCE { svID INTEGER(0..63), midiAlmE BIT STRING (SIZE (11)), midiAlmDeltaI BIT STRING (SIZE (11)), midiAlmOmegaDot BIT STRING (SIZE (11)), midiAlmSqrtA BIT STRING (SIZE (17)), midiAlmOmega0 BIT STRING (SIZE (16)), midiAlmOmega BIT STRING (SIZE (16)), midiAlmMo BIT STRING (SIZE (16)), midiAlmaf0 BIT STRING (SIZE (11)), midiAlmaf1 BIT STRING (SIZE (10)), midiAlmL1Health BIT STRING (SIZE (1)), midiAlmL2Health BIT STRING (SIZE (1)), midiAlmL5Health BIT STRING (SIZE (1)), ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs } } ... } GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-SAT-Info-Almanac-NAVkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF SEQUENCE { svID INTEGER(0..63), navAlmE BIT STRING (SIZE (16)), navAlmDeltaI BIT STRING (SIZE (16)), navAlmOMEGADOT BIT STRING (SIZE (16)), navAlmSVHealth BIT STRING (SIZE (8)), navAlmSqrtA BIT STRING (SIZE (24)), navAlmOMEGAo BIT STRING (SIZE (24)), navAlmOmega BIT STRING (SIZE (24)), navAlmMo BIT STRING (SIZE (24)),

OPTIONAL,

3GPP

Release 11
navAlmaf0 navAlmaf1 ie-Extensions ...

1009
BIT STRING (SIZE (11)), BIT STRING (SIZE (11)), ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-NAVkp-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GANSS-SAT-Info-Almanac-NAVkp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-SAT-Info-Almanac-REDkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF SEQUENCE { svID INTEGER(0..63), redAlmDeltaA BIT STRING (SIZE (8)), redAlmOmega0 BIT STRING (SIZE (7)), redAlmPhi0 BIT STRING (SIZE (7)), redAlmL1Health BIT STRING (SIZE (1)), redAlmL2Health BIT STRING (SIZE (1)), redAlmL5Health BIT STRING (SIZE (1)), ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-REDkp-ExtIEs } } ... } GANSS-SAT-Info-Almanac-REDkp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-SAT-Info-Almanac-SBASecefList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF SEQUENCE { sbasAlmDataID BIT STRING (SIZE(2)), svID INTEGER(0..63), sbasAlmHealth BIT STRING (SIZE(8)), sbasAlmXg BIT STRING (SIZE(15)), sbasAlmYg BIT STRING (SIZE(15)), sbasAlmZg BIT STRING (SIZE(9)), sbasAlmXgdot BIT STRING (SIZE(3)), sbasAlmYgDot BIT STRING (SIZE(3)), sbasAlmZgDot BIT STRING (SIZE(4)), sbasAlmTo BIT STRING (SIZE(11)), ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-SBASecef-ExtIEs } } ... } GANSS-SAT-Info-Almanac-SBASecef-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL,

3GPP

Release 11

1010

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-Sat-Info-Nav ::= SEQUENCE (SIZE(1..maxGANSSSat)) OF SEQUENCE { satId INTEGER(0..63), svHealth BIT STRING (SIZE(5)), iod BIT STRING (SIZE(10)), ganssClockModel GANSS-Clock-Model, ganssOrbitModel GANSS-Orbit-Model, ie-Extensions ProtocolExtensionContainer { { GANSS-Sat-Info-Nav-ExtIEs } } OPTIONAL, ... } GANSS-Sat-Info-Nav-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-SBAS-ID ::= ENUMERATED { waas, egnos, msas, gagan, ... }

GANSS-SBASclockModel ::= SEQUENCE { sbasTo BIT STRING (SIZE (13)), sbasAgfo BIT STRING (SIZE (12)), sbasAgf1 BIT STRING (SIZE (8)), ie-Extensions ProtocolExtensionContainer { { GANSS-SBASclockModel-ExtIEs } } ... } GANSS-SBASclockModel-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-Signal-ID ::= INTEGER(0..7,...) GANSS-StatusHealth ::= ENUMERATED { udre-scale-1dot0, udre-scale-0dot75, udre-scale-0dot5, udre-scale-0dot3, udre-scale-0dot2, udre-scale-0dot1, no-data, invalid-data } GANSS-Time-ID ::= INTEGER(0..7,...)

OPTIONAL,

3GPP

Release 11
GANSS-Time-Model ::= SEQUENCE { ganss-time-model-Ref-Time ganss-t-a0 ganss-t-a1 ganss-t-a2 gnss-to-id ganss-wk-number ie-Extensions ... }

1011

3GPP TS 25.423 V11.2.0 (2012-06)

INTEGER(0..37799), INTEGER(-2147483648..2147483647), INTEGER(-8388608..8388607) INTEGER(-64..63) ENUMERATED{gps,...,galileo,qzss,glonass}, INTEGER(0..8191) ProtocolExtensionContainer { { GANSS-Time-Model-ExtIEs } }

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

GANSS-Time-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-ganss-Delta-T CRITICALITY ignore EXTENSION ... }

GANSS-Delta-T

PRESENCE

optional},

GANSS-Transmission-Time ::= SEQUENCE { ganssDay INTEGER(0..8191) ganssTod INTEGER(0..86399), ie-Extensions ProtocolExtensionContainer { { GANSS-Transmission-Time-ExtIEs } } ... } GANSS-Transmission-Time-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-UTC-Model ::= SEQUENCE { a-one-utc a-zero-utc t-ot-utc w-n-t-utc delta-t-ls-utc w-n-lsf-utc dn-utc delta-t-lsf-utc ie-Extensions ... } BIT STRING (SIZE (24)), BIT STRING (SIZE (32)), BIT STRING (SIZE (8)), BIT STRING (SIZE (8)), BIT STRING (SIZE (8)), BIT STRING (SIZE (8)), BIT STRING (SIZE (8)), BIT STRING (SIZE (8)), ProtocolExtensionContainer { { GANSS-UTC-Model-ExtIEs } }

OPTIONAL, OPTIONAL,

OPTIONAL,

GANSS-UTC-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1012

3GPP TS 25.423 V11.2.0 (2012-06)

GANSS-UTCmodelSet1 ::= SEQUENCE { utcA0 BIT STRING (SIZE(16)), utcA1 BIT STRING (SIZE(13)), utcA2 BIT STRING (SIZE(7)), utcDeltaTls BIT STRING (SIZE(8)), utcTot BIT STRING (SIZE(16)), utcWNot BIT STRING (SIZE(13)), utcWNlsf BIT STRING (SIZE(8)), utcDN BIT STRING (SIZE(4)), utcDeltaTlsf BIT STRING (SIZE(8)), ie-Extensions ProtocolExtensionContainer { { GANSS-UTCmodelSet1-ExtIEs } } ... } GANSS-UTCmodelSet1-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-UTCmodelSet2 ::= SEQUENCE { nA BIT STRING (SIZE(11)), tauC BIT STRING (SIZE(32)), deltaUT1 GANSS-DeltaUT1 kp BIT STRING (SIZE(2)) ie-Extensions ProtocolExtensionContainer { { GANSS-UTCmodelSet2-ExtIEs } } ... } GANSS-UTCmodelSet2-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GANSS-UTCmodelSet3 ::= SEQUENCE { utcA1wnt BIT STRING (SIZE(24)), utcA0wnt BIT STRING (SIZE(32)), utcTot BIT STRING (SIZE(8)), utcWNt BIT STRING (SIZE(8)), utcDeltaTls BIT STRING (SIZE(8)), utcWNlsf BIT STRING (SIZE(8)), utcDN BIT STRING (SIZE(8)), utcDeltaTlsf BIT STRING (SIZE(8)), utcStandardID BIT STRING (SIZE(3)), ie-Extensions ProtocolExtensionContainer { { GANSS-UTCmodelSet3-ExtIEs } } ... } GANSS-UTCmodelSet3-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL,

OPTIONAL,

3GPP

Release 11

1013

3GPP TS 25.423 V11.2.0 (2012-06)

GA-PointWithAltitude ::= SEQUENCE { geographicalCoordinates GeographicalCoordinate, altitudeAndDirection GA-AltitudeAndDirection, iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitude-ExtIEs} } OPTIONAL, ... } GA-PointWithAltitude-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GA-PointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE { geographicalCoordinates GeographicalCoordinate, altitudeAndDirection GA-AltitudeAndDirection, uncertaintyEllipse GA-UncertaintyEllipse, uncertaintyAltitude INTEGER (0..127), confidence INTEGER (0..127), iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs} } OPTIONAL, ... } GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GA-PointWithUnCertaintyEllipse ::= SEQUENCE { geographicalCoordinates GeographicalCoordinate, uncertaintyEllipse GA-UncertaintyEllipse, confidence INTEGER (0..127), iE-Extensions ProtocolExtensionContainer { { GA-PointWithUnCertaintyEllipse-ExtIEs} } OPTIONAL, ... } GA-PointWithUnCertaintyEllipse-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GA-UncertaintyEllipse ::= SEQUENCE { uncertaintySemi-major INTEGER (0..127), uncertaintySemi-minor INTEGER (0..127), orientationOfMajorAxis INTEGER (0..179), ... }

-- The values 90..179 shall not be used.

GA-PointWithUnCertainty ::=SEQUENCE { geographicalCoordinates GeographicalCoordinate, uncertaintyCode INTEGER (0..127), iE-Extensions ProtocolExtensionContainer { {GA-PointWithUnCertainty-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11
GA-PointWithUnCertainty-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1014

3GPP TS 25.423 V11.2.0 (2012-06)

GA-AccessPointPosition ::= SEQUENCE { geographicalCoordinate GeographicalCoordinate, iE-Extensions ProtocolExtensionContainer { {GA-AccessPoint-ExtIEs} } OPTIONAL, ... } GA-AccessPoint-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GeographicalCoordinate ::= SEQUENCE { latitudeSign ENUMERATED { north, south }, latitude INTEGER (0..8388607), longitude INTEGER (-8388608..8388607), iE-Extensions ProtocolExtensionContainer { {GeographicalCoordinate-ExtIEs} } OPTIONAL, ... } GeographicalCoordinate-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GERAN-Cell-Capability ::= BIT STRING (SIZE (16)) -- First bit: A/Gb mode --- Second bit: Iu mode --- Note: undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. GERAN-Classmark ::= OCTET STRING -- GERAN Classmark as defined in (38) -GERAN-SI-Type ::= CHOICE { sI pSI ... } GERAN-SystemInfo, GERAN-SystemInfo,

GERAN-SystemInfo ::= SEQUENCE (SIZE (1..maxNrOfGERANSI)) OF SEQUENCE { gERAN-SI-block OCTET STRING (SIZE (1..23)), iE-Extensions ProtocolExtensionContainer { { GERAN-SystemInfo-ExtIEs } } ... } GERAN-SystemInfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

3GPP

Release 11
GenericTrafficCategory ::= BIT STRING (SIZE (8))

1015

3GPP TS 25.423 V11.2.0 (2012-06)

GPS-Almanac ::= SEQUENCE { wna-alm BIT STRING (SIZE (8)), satellite-Almanac-Information SEQUENCE (SIZE (1..maxNoSat)) OF SEQUENCE { dATA-ID DATA-ID, sAT-ID SAT-ID, gps-e-alm BIT STRING (SIZE (16)), gps-toa-alm BIT STRING (SIZE (8)), gps-delta-I-alm BIT STRING (SIZE (16)), omegadot-alm BIT STRING (SIZE (16)), svhealth-alm BIT STRING (SIZE (8)), gps-a-sqrt-alm BIT STRING (SIZE (24)), omegazero-alm BIT STRING (SIZE (24)), m-zero-alm BIT STRING (SIZE (24)), gps-omega-alm BIT STRING (SIZE (24)), gps-af-zero-alm BIT STRING (SIZE (11)), gps-af-one-alm BIT STRING (SIZE (11)), iE-Extensions ProtocolExtensionContainer { { Satellite-Almanac-Information-ExtIEs} } ... }, -- This GPS-Almanac-Information is for the 1st 16 satellites sVGlobalHealth-alm BIT STRING (SIZE (364)) OPTIONAL, iE-Extensions ProtocolExtensionContainer { { GPS-Almanac-ExtIEs} } OPTIONAL, ... } Satellite-Almanac-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPS-Almanac-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Satellite-Almanac-Information-ExtItem CRITICALITY ignore optional}| { ID id-completeAlmanacProvided CRITICALITY ignore PRESENCE optional}, ... } EXTENSION EXTENSION

OPTIONAL,

Satellite-Almanac-Information-ExtItem CompleteAlmanacProvided

PRESENCE

Satellite-Almanac-Information-ExtItem ::= SEQUENCE (SIZE (1..maxNrOfSatAlmanac-maxNoSat)) OF SEQUENCE { dATA-ID DATA-ID, sAT-ID SAT-ID, gps-e-alm BIT STRING (SIZE (16)), gps-toa-alm BIT STRING (SIZE (8)), gps-delta-I-alm BIT STRING (SIZE (16)), omegadot-alm BIT STRING (SIZE (16)), svhealth-alm BIT STRING (SIZE (8)), gps-a-sqrt-alm BIT STRING (SIZE (24)), omegazero-alm BIT STRING (SIZE (24)),

3GPP

Release 11
m-zero-alm gps-omega-alm gps-af-zero-alm gps-af-one-alm iE-Extensions ... --

1016
BIT STRING (SIZE (24)), BIT STRING (SIZE (24)), BIT STRING (SIZE (11)), BIT STRING (SIZE (11)), ProtocolExtensionContainer { { Satellite-Almanac-Information-ExtItemIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

} Includes the GPS-Almanac-Information for the 17th through 32nd satellites.

Satellite-Almanac-Information-ExtItemIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPSInformation ::= SEQUENCE (SIZE (1..maxNoGPSTypes)) OF SEQUENCE { gPSInformationItem ENUMERATED { gPS-NavigationModel-and-TimeRecovery, gPS-Ionospheric-Model, gPS-UTC-Model, gPS-Almanac, gPS-RealTime-Integrity, ... }, iE-Extensions ProtocolExtensionContainer { { GPSInformation-ExtIEs} } ... } -- This IE shall be present if the Information Type IE indicates GPS Information GPSInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPS-Ionospheric-Model ::= SEQUENCE { alpha-zero-ionos BIT STRING (SIZE (8)), alpha-one-ionos BIT STRING (SIZE (8)), alpha-two-ionos BIT STRING (SIZE (8)), alpha-three-ionos BIT STRING (SIZE (8)), beta-zero-ionos BIT STRING (SIZE (8)), beta-one-ionos BIT STRING (SIZE (8)), beta-two-ionos BIT STRING (SIZE (8)), beta-three-ionos BIT STRING (SIZE (8)), iE-Extensions ProtocolExtensionContainer { { GPS-Ionospheric-Model-ExtIEs} } ... } GPS-Ionospheric-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPS-NavigationModel-and-TimeRecovery ::= SEQUENCE (SIZE (1..maxNoSat)) OF SEQUENCE {

OPTIONAL,

OPTIONAL,

3GPP

Release 11
tx-tow-nav sAT-ID tlm-message-nav tlm-revd-c-nav ho-word-nav w-n-nav ca-or-p-on-l2-nav user-range-accuracy-index-nav sv-health-nav iodc-nav l2-p-dataflag-nav sf1-reserved-nav t-gd-nav t-oc-nav a-f-2-nav a-f-1-nav a-f-zero-nav c-rs-nav delta-n-nav m-zero-nav c-uc-nav gps-e-nav c-us-nav a-sqrt-nav t-oe-nav fit-interval-flag-nav aodo-nav c-ic-nav omega-zero-nav c-is-nav i-zero-nav c-rc-nav gps-omega-nav omegadot-nav idot-nav spare-zero-fill iE-Extensions ... }

1017
INTEGER (0..1048575), SAT-ID, BIT STRING (SIZE (14)), BIT STRING (SIZE (2)), BIT STRING (SIZE (22)), BIT STRING (SIZE (10)), BIT STRING (SIZE (2)), BIT STRING (SIZE (4)), BIT STRING (SIZE (6)), BIT STRING (SIZE (10)), BIT STRING (SIZE (1)), BIT STRING (SIZE (87)), BIT STRING (SIZE (8)), BIT STRING (SIZE (16)), BIT STRING (SIZE (8)), BIT STRING (SIZE (16)), BIT STRING (SIZE (22)), BIT STRING (SIZE (16)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (1)), BIT STRING (SIZE (5)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (16)), BIT STRING (SIZE (32)), BIT STRING (SIZE (24)), BIT STRING (SIZE (14)), BIT STRING (SIZE (20)), ProtocolExtensionContainer { { GPS-NavigationModel-and-TimeRecoveryItem-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

GPS-NavigationModel-and-TimeRecoveryItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPS-RealTime-Integrity ::= CHOICE { badSatellites BadSatellites, noBadSatellite NULL } GPS-RX-POS ::= SEQUENCE { geographicalCoordinate GeographicalCoordinate,

3GPP

Release 11
altitudeAndDirection iE-Extensions ...

1018
GA-AltitudeAndDirection, ProtocolExtensionContainer { { GPS-RX-POS-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

GPS-RX-POS-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } GPS-Status-Health ::= ENUMERATED { udre-1-0, udre-0-75, udre-0-5, udre-0-3, udre-0-1, no-data, invalid-data } GPSTOW ::= INTEGER (0..604799) GPS-UTC-Model ::= SEQUENCE { a-one-utc BIT STRING (SIZE (24)), a-zero-utc BIT STRING (SIZE (32)), t-ot-utc BIT STRING (SIZE (8)), delta-t-ls-utc BIT STRING (SIZE (8)), w-n-t-utc BIT STRING (SIZE (8)), w-n-lsf-utc BIT STRING (SIZE (8)), dn-utc BIT STRING (SIZE (8)), delta-t-lsf-utc BIT STRING (SIZE (8)), iE-Extensions ProtocolExtensionContainer { { GPS-UTC-Model-ExtIEs} } ... } GPS-UTC-Model-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Guaranteed-Rate-Information ::= SEQUENCE { guaranteed-UL-Rate Guaranteed-Rate OPTIONAL, guaranteed-DL-Rate Guaranteed-Rate OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Guaranteed-Rate-Information-ExtIEs} } OPTIONAL, ... } Guaranteed-Rate-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Guaranteed-Rate ::= INTEGER (1..maxNrOfTFs) -- 1: TFI 0, 2: TFI 1, 3: TFI 2, ...

OPTIONAL,

3GPP

Release 11
-- H HARQ-Info-for-E-DCH ::= ENUMERATED { rv0, rvtable } HARQ-MemoryPartitioning ::= CHOICE { implicit HARQ-MemoryPartitioning-Implicit, explicit HARQ-MemoryPartitioning-Explicit, ... }

1019

3GPP TS 25.423 V11.2.0 (2012-06)

HARQ-MemoryPartitioning-Implicit ::= SEQUENCE { number-of-Processes INTEGER (1..8,...,12|14|16), iE-Extensions ProtocolExtensionContainer { { HARQ-MemoryPartitioning-Implicit-ExtIEs } } ... } HARQ-MemoryPartitioning-Implicit-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HARQ-MemoryPartitioning-Explicit hARQ-MemoryPartitioningList iE-Extensions ... } ::= SEQUENCE { HARQ-MemoryPartitioningList, ProtocolExtensionContainer { { HARQ-MemoryPartitioning-Explicit-ExtIEs } }

OPTIONAL,

OPTIONAL,

HARQ-MemoryPartitioning-Explicit-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-HARQ-MemoryPartitioningInfoExtForMIMO CRITICALITY ignore ... }

EXTENSION HARQ-MemoryPartitioningInfoExtForMIMO PRESENCE optional},

HARQ-MemoryPartitioningList ::= SEQUENCE (SIZE (1..maxNrOfHARQProc)) OF HARQ-MemoryPartitioningItem HARQ-MemoryPartitioningInfoExtForMIMO ::= SEQUENCE (SIZE (4|6|8)) OF HARQ-MemoryPartitioningItem HARQ-MemoryPartitioningItem ::= SEQUENCE { process-Memory-Size 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,

3GPP

Release 11

1020
hms152000, hms160000, hms176000, hms192000, hms208000, hms224000, hms240000, hms256000, hms272000, hms288000, hms304000,...}, ProtocolExtensionContainer { { HARQ-MemoryPartitioningItem-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

iE-Extensions ...

OPTIONAL,

HARQ-MemoryPartitioningItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HARQ-Preamble-Mode ::= ENUMERATED { mode0, mode1 } HARQ-Process-Allocation-2ms-EDCH ::= BIT STRING ( SIZE(maxNrOfEDCHHARQProcesses2msEDCH) ) HARQ-Preamble-Mode-Activation-Indicator ::=ENUMERATED harqPreambleModeSupported } HCS-Prio ::= INTEGER (0..7) -- 0 = lowest priority, ...7 = highest priority HSDSCH-Configured-Indicator ::= ENUMERATED { configured-HS-DSCH, no-configured-HS-DSCH } HSDSCH-FDD-Information ::= SEQUENCE { hSDSCH-MACdFlows-Information HSDSCH-MACdFlows-Information, uE-Capabilities-Info UE-Capabilities-Info, mAChs-Reordering-Buffer-Size-for-RLC-UM MAChsReorderingBufferSize-for-RLC-UM, cqiFeedback-CycleK CQI-Feedback-Cycle, cqiRepetitionFactor CQI-RepetitionFactor OPTIONAL, -- This IE shall be present if the CQI Feedback Cycle k IE is set to a value greater than 0. ackNackRepetitionFactor AckNack-RepetitionFactor, cqiPowerOffset CQI-Power-Offset, ackPowerOffset Ack-Power-Offset, nackPowerOffset Nack-Power-Offset, hsscch-PowerOffset HSSCCH-PowerOffset OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HSDSCH-FDD-Information-ExtIEs } } ... } HSDSCH-FDD-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HARQ-Preamble-Mode CRITICALITY ignore optional}| { ID id-MIMO-ActivationIndicator CRITICALITY reject PRESENCE optional}| EXTENSION EXTENSION HARQ-Preamble-Mode MIMO-ActivationIndicator {

OPTIONAL,

PRESENCE

3GPP

Release 11

1021

3GPP TS 25.423 V11.2.0 (2012-06)

{ ID id-HSDSCH-MACdPDUSizeFormat CRITICALITY reject EXTENSION HSDSCH-MACdPDUSizeFormat PRESENCE optional}| { ID id-SixtyfourQAM-UsageAllowedIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-UsageAllowedIndicator PRESENCE optional}| { ID id-UE-with-enhanced-HS-SCCH-support-indicator CRITICALITY ignore EXTENSION NULL PRESENCE optional}| { ID id-EnhancedHSServingCC-Abort CRITICALITY reject EXTENSION EnhancedHSServingCC-Abort PRESENCE optional}| { ID id-UE-SupportIndicatorExtension CRITICALITY ignore EXTENSION UE-SupportIndicatorExtension PRESENCE optional}| { ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}| { ID id-Single-Stream-MIMO-ActivationIndicator CRITICALITY reject EXTENSION Single-Stream-MIMO-ActivationIndicator PRESENCE optional}, ... } HSDSCH-FDD-Information-Response ::= SEQUENCE { hSDSCH-MACdFlow-Specific-InfoList-Response OPTIONAL, hSSCCH-Specific-InfoList-Response OPTIONAL, hSPDSCH-and-HSSCCH-ScramblingCode measurement-Power-Offset OPTIONAL, hARQ-MemoryPartitioning OPTIONAL, iE-Extensions ... } HSDSCH-MACdFlow-Specific-InfoList-Response HSSCCH-FDD-Specific-InfoList-Response DL-ScramblingCode Measurement-Power-Offset HARQ-MemoryPartitioning ProtocolExtensionContainer { { HSDSCH-FDD-Information-Response-ExtIEs } } OPTIONAL, OPTIONAL,

HSDSCH-FDD-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-User-Plane-Congestion-Fields-Inclusion CRITICALITY ignore EXTENSION User-Plane-Congestion-Fields-Inclusion PRESENCE optional}| { ID id-HARQ-Preamble-Mode-Activation-Indicator CRITICALITY ignore EXTENSION HARQ-Preamble-Mode-Activation-Indicator PRESENCE optional}| { ID id-MIMO-InformationResponse CRITICALITY ignore EXTENSION MIMO-InformationResponse PRESENCE optional}| { ID id-SixtyfourQAM-DL-UsageIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-DL-UsageIndicator PRESENCE optional}| { ID id-HSDSCH-TBSizeTableIndicator CRITICALITY ignore EXTENSION HSDSCH-TBSizeTableIndicator PRESENCE optional}| { ID id-power-offset-for-S-CPICH-for-MIMO CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMO PRESENCE optional}| { ID id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order CRITICALITY ignore EXTENSION Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order PRESENCE optional}, ... } HS-DSCH-FDD-Secondary-Serving-Information ::= SEQUENCE { hsscch-PowerOffset HSSCCH-PowerOffset OPTIONAL, sixtyfourQAM-UsageAllowedIndicator SixtyfourQAM-UsageAllowedIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-ExtIEs } } OPTIONAL, ... }

3GPP

Release 11

1022

3GPP TS 25.423 V11.2.0 (2012-06)

HS-DSCH-FDD-Secondary-Serving-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-ActivationIndicator CRITICALITY reject EXTENSION MIMO-ActivationIndicator PRESENCE optional}| {ID id-Single-Stream-MIMO-ActivationIndicator CRITICALITY reject EXTENSION Single-Stream-MIMO-ActivationIndicator PRESENCE optional}| {ID id-DiversityMode CRITICALITY reject EXTENSION DiversityMode PRESENCE optional}| {ID id-TransmitDiversityIndicator CRITICALITY reject EXTENSION TransmitDiversityIndicator PRESENCE optional}| {ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}| {ID id-OrdinalNumberOfFrequency CRITICALITY reject EXTENSION OrdinalNumberOfFrequency PRESENCE optional}, ... } HS-DSCH-FDD-Secondary-Serving-Information-Response ::= SEQUENCE { hSSCCH-Specific-InfoList-Response HSSCCH-FDD-Specific-InfoList-Response OPTIONAL, hSPDSCH-and-HSSCCH-ScramblingCode DL-ScramblingCode OPTIONAL, measurement-Power-Offset Measurement-Power-Offset OPTIONAL, sixtyfourQAM-DL-UsageIndicator SixtyfourQAM-DL-UsageIndicator OPTIONAL, hSDSCH-TBSizeTableIndicator HSDSCH-TBSizeTableIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-Respons-ExtIEs } } OPTIONAL, ... } HS-DSCH-FDD-Secondary-Serving-Information-Respons-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-InformationResponse CRITICALITY ignore EXTENSION MIMO-InformationResponse {ID id-power-offset-for-S-CPICH-for-MIMO CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMO ... } HS-DSCH-Secondary-Serving-Information-To-Modify hsscch-PowerOffset hSSCCH-CodeChangeGrant sixtyfourQAM-UsageAllowedIndicator iE-Extensions OPTIONAL, ... } PRESENCE optional}| PRESENCE optional},

::= SEQUENCE { HSSCCH-PowerOffset OPTIONAL, HSSCCH-Code-Change-Grant OPTIONAL, SixtyfourQAM-UsageAllowedIndicator OPTIONAL, ProtocolExtensionContainer { { HS-DSCH-Secondary-Serving-Information-To-Modify-ExtIEs } }

HS-DSCH-Secondary-Serving-Information-To-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-Mode-Indicator CRITICALITY reject EXTENSION MIMO-Mode-Indicator PRESENCE optional}| {ID id-Single-Stream-MIMO-Mode-Indicator CRITICALITY reject EXTENSION Single-Stream-MIMO-Mode-Indicator PRESENCE optional}| {ID id-DiversityMode CRITICALITY reject EXTENSION DiversityMode PRESENCE optional}| {ID id-TransmitDiversityIndicator CRITICALITY reject EXTENSION TransmitDiversityIndicator PRESENCE optional}| -- This IE shall be present if Diversity Mode IE is present and is not set to none {ID id-NonCellSpecificTxDiversity CRITICALITY reject EXTENSION NonCellSpecificTxDiversity PRESENCE optional}| {ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}| {ID id-OrdinalNumberOfFrequency CRITICALITY reject EXTENSION OrdinalNumberOfFrequency PRESENCE optional}, ... } HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised ::= SEQUENCE {

3GPP

Release 11

1023

3GPP TS 25.423 V11.2.0 (2012-06)

hsscch-PowerOffset HSSCCH-PowerOffset OPTIONAL, sixtyfourQAM-UsageAllowedIndicator SixtyfourQAM-UsageAllowedIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised-ExtIEs } } OPTIONAL, ...

HS-DSCH-FDD-Secondary-Serving-Information-To-Modify-Unsynchronised-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-Mode-Indicator CRITICALITY reject EXTENSION MIMO-Mode-Indicator PRESENCE optional}| {ID id-Single-Stream-MIMO-Mode-Indicator CRITICALITY reject EXTENSION Single-Stream-MIMO-Mode-Indicator PRESENCE optional}| {ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}| {ID id-OrdinalNumberOfFrequency CRITICALITY reject EXTENSION OrdinalNumberOfFrequency PRESENCE optional}, ... } HS-DSCH-FDD-Secondary-Serving-Update-Information ::= SEQUENCE { hsSCCHCodeChangeIndicator HSSCCH-CodeChangeIndicator OPTIONAL, hS-PDSCH-Code-Change-Indicator HS-PDSCH-Code-Change-Indicator OPTIONAL, -- This IE shall never be included. If received it shall be ignored. iE-Extensions ProtocolExtensionContainer { { HS-DSCH-FDD-Secondary-Serving-Update-Information-ExtIEs } } OPTIONAL, ... } HS-DSCH-FDD-Secondary-Serving-Update-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-Secondary-Serving-Cell-Change-Information-Response ::= SEQUENCE { hS-DSCH-Secondary-Serving-cell-choice HS-DSCH-Secondary-Serving-cell-change-choice, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-Secondary-Serving-Cell-Change-Information-Response-ExtIEs } } OPTIONAL, ... } HS-DSCH-Secondary-Serving-Cell-Change-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-Secondary-Serving-cell-change-choice ::= CHOICE { hS-Secondary-Serving-cell-change-successful HS-Secondary-Serving-cell-change-successful, hS-Secondary-Serving-cell-change-unsuccessful HS-Secondary-Serving-cell-change-unsuccessful, ... } HS-Secondary-Serving-cell-change-successful ::= SEQUENCE { hS-DSCH-FDD-Secondary-Serving-Information-Response HS-DSCH-FDD-Secondary-Serving-Information-Response, hSDSCH-RNTI HSDSCH-RNTI, iE-Extensions ProtocolExtensionContainer { { HS-Secondary-Serving-cell-change-successful-ExtIEs} } OPTIONAL, ...

3GPP

Release 11
}

1024

3GPP TS 25.423 V11.2.0 (2012-06)

HS-Secondary-Serving-cell-change-successful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-Secondary-Serving-cell-change-unsuccessful ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { HS-Secondary-Serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL, ... } HS-Secondary-Serving-cell-change-unsuccessful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-Secondary-Serving-Remove ::= NULL HSDSCH-Information-to-Modify ::= SEQUENCE { hSDSCH-MACdFlow-Specific-InfoList-to-Modify priorityQueue-Info-to-Modify mAChs-Reordering-Buffer-Size-for-RLC-UM cqiFeedback-CycleK cqiRepetitionFactor ackNackRepetitionFactor cqiPowerOffset ackPowerOffset nackPowerOffset hsscch-PowerOffset hSSCCH-CodeChangeGrant tDDAckNackPowerOffset iE-Extensions ... }

HSDSCH-MACdFlow-Specific-InfoList-to-Modify OPTIONAL, PriorityQueue-InfoList-to-Modify OPTIONAL, MAChsReorderingBufferSize-for-RLC-UM OPTIONAL, CQI-Feedback-Cycle OPTIONAL, -CQI-RepetitionFactor OPTIONAL, -AckNack-RepetitionFactor OPTIONAL, -CQI-Power-Offset OPTIONAL, -Ack-Power-Offset OPTIONAL, -Nack-Power-Offset OPTIONAL, -HSSCCH-PowerOffset OPTIONAL, -HSSCCH-Code-Change-Grant OPTIONAL, TDD-AckNack-Power-Offset OPTIONAL, -ProtocolExtensionContainer { { HSDSCH-Information-to-Modify-ExtIEs } }

For For For For For For For

FDD FDD FDD FDD FDD FDD FDD

only only only only only only only OPTIONAL,

For TDD only

HSDSCH-Information-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HARQ-Preamble-Mode CRITICALITY ignore EXTENSION HARQ-Preamble-Mode PRESENCE optional}| { ID id-HS-PDSCH-Code-Change-Grant CRITICALITY ignore EXTENSION HS-PDSCH-Code-Change-Grant PRESENCE optional}| -- Applicable to FDD only { ID id-MIMO-Mode-Indicator CRITICALITY reject EXTENSION MIMO-Mode-Indicator PRESENCE optional}| { ID id-HSDSCH-MACdPDUSizeFormat CRITICALITY reject EXTENSION HSDSCH-MACdPDUSizeFormat PRESENCE optional}| { ID id-SixtyfourQAM-UsageAllowedIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-UsageAllowedIndicator PRESENCE optional}| { ID id-UE-Capabilities-Info CRITICALITY ignore EXTENSION UE-Capabilities-Info PRESENCE optional}| { ID id-EnhancedHSServingCC-Abort CRITICALITY reject EXTENSION EnhancedHSServingCC-Abort PRESENCE optional}| { ID id-UE-SupportIndicatorExtension CRITICALITY ignore EXTENSION UE-SupportIndicatorExtension PRESENCE optional}|

3GPP

Release 11
{ ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator PRESENCE optional}| { ID id-Single-Stream-MIMO-Mode-Indicator CRITICALITY reject ... }

1025
CRITICALITY ignore EXTENSION Single-Stream-MIMO-Mode-Indicator

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional},

HSDSCH-Information-to-Modify-Unsynchronised ::= SEQUENCE { hSDSCH-MACdFlow-Specific-InfoList-to-Modify HSDSCH-MACdFlow-Specific-InfoList-to-Modify OPTIONAL, priorityQueueInfotoModifyUnsynchronised PriorityQueue-InfoList-to-Modify-Unsynchronised OPTIONAL, cqiPowerOffset CQI-Power-Offset OPTIONAL, -- For FDD only ackPowerOffset Ack-Power-Offset OPTIONAL, -- For FDD only nackPowerOffset Nack-Power-Offset OPTIONAL, -- For FDD only hsscch-PowerOffset HSSCCH-PowerOffset OPTIONAL, -- Only for FDD tDDAckNackPowerOffset TDD-AckNack-Power-Offset OPTIONAL, -- For TDD only iE-Extensions ProtocolExtensionContainer { { HSDSCH-Information-to-Modify-Unsynchronised-ExtIEs } } OPTIONAL, ... } HSDSCH-Information-to-Modify-Unsynchronised-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HARQ-Preamble-Mode CRITICALITY ignore EXTENSION HARQ-Preamble-Mode PRESENCE optional}| { ID id-MIMO-Mode-Indicator CRITICALITY reject EXTENSION MIMO-Mode-Indicator PRESENCE optional}| { ID id-SixtyfourQAM-UsageAllowedIndicator CRITICALITY ignore EXTENSION SixtyfourQAM-UsageAllowedIndicator PRESENCE optional}| { ID id-EnhancedHSServingCC-Abort CRITICALITY reject EXTENSION EnhancedHSServingCC-Abort PRESENCE optional}| { ID id-UE-SupportIndicatorExtension CRITICALITY ignore EXTENSION UE-SupportIndicatorExtension PRESENCE optional}| { ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}| { ID id-Single-Stream-MIMO-Mode-Indicator CRITICALITY reject EXTENSION Single-Stream-MIMO-Mode-Indicator PRESENCE optional}, ... } HSDSCH-MACdFlow-ID ::= INTEGER (0..maxNrOfMACdFlows-1) HSDSCH-MACdFlow-Specific-InfoList ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InfoItem HSDSCH-MACdPDUSizeFormat ::= ENUMERATED { indexedMACdPDU-Size, flexibleMACdPDU-Size } HSDSCH-MACdFlow-Specific-InfoItem ::= SEQUENCE { hSDSCH-MACdFlow-ID HSDSCH-MACdFlow-ID, allocationRetentionPriority AllocationRetentionPriority, trafficClass TrafficClass, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InfoItem-ExtIEs } } ... }

OPTIONAL,

3GPP

Release 11

1026

3GPP TS 25.423 V11.2.0 (2012-06)

HSDSCH-MACdFlow-Specific-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }| {ID id-TrCH-SrcStatisticsDescr CRITICALITY ignore EXTENSION TrCH-SrcStatisticsDescr PRESENCE optional }, ... } HSDSCH-MACdFlow-Specific-InfoList-Response ::= SEQUENCE (SIZE (0..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InfoItem-Response HSDSCH-MACdFlow-Specific-InfoItem-Response ::= SEQUENCE { hSDSCH-MACdFlow-ID HSDSCH-MACdFlow-ID, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, hSDSCH-Initial-Capacity-Allocation HSDSCH-Initial-Capacity-Allocation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InfoItem-Response-ExtIEs } } ... } HSDSCH-MACdFlow-Specific-InfoItem-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSDSCH-MACdFlow-Specific-InfoList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlow-Specific-InfoItem-to-Modify HSDSCH-MACdFlow-Specific-InfoItem-to-Modify ::= SEQUENCE { hSDSCH-MACdFlow-ID HSDSCH-MACdFlow-ID, allocationRetentionPriority AllocationRetentionPriority OPTIONAL, transportBearerRequestIndicator TransportBearerRequestIndicator, trafficClass TrafficClass OPTIONAL, bindingID BindingID OPTIONAL, transportLayerAddress TransportLayerAddress OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HSDSCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs } } ... } HSDSCH-MACdFlow-Specific-InfoItem-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-TnlQos CRITICALITY ignore EXTENSION TnlQos PRESENCE optional }, ... } HSDSCH-MACdFlows-Information ::= SEQUENCE { hSDSCH-MACdFlow-Specific-Info priorityQueue-Info iE-Extensions ... } HSDSCH-MACdFlow-Specific-InfoList, PriorityQueue-InfoList, ProtocolExtensionContainer { { HSDSCH-MACdFlows-Information-ExtIEs } }

OPTIONAL,

OPTIONAL,

OPTIONAL,

HSDSCH-MACdFlows-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1027

3GPP TS 25.423 V11.2.0 (2012-06)

HSDSCH-MACdFlows-to-Delete ::= SEQUENCE (SIZE (1..maxNrOfMACdFlows)) OF HSDSCH-MACdFlows-to-Delete-Item HSDSCH-MACdFlows-to-Delete-Item ::= SEQUENCE { hsDSCH-MACdFlow-ID HSDSCH-MACdFlow-ID, iE-Extensions ProtocolExtensionContainer { { HSDSCH-MACdFlows-to-Delete-Item-ExtIEs} } ... } HSDSCH-MACdFlows-to-Delete-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSDSCH-Initial-Capacity-Allocation::= SEQUENCE (SIZE (1..maxNrOfPrioQueues)) OF HSDSCH-Initial-Capacity-AllocationItem HSDSCH-Initial-Capacity-AllocationItem ::= SEQUENCE { schedulingPriorityIndicator SchedulingPriorityIndicator, maximum-MACdPDU-Size MACdPDU-Size, hSDSCH-InitialWindowSize HSDSCH-InitialWindowSize, iE-Extensions ProtocolExtensionContainer { {HSDSCH-Initial-Capacity-AllocationItem-ExtIEs} } OPTIONAL, ... } HSDSCH-Initial-Capacity-AllocationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY ignore EXTENSION MAC-PDU-SizeExtended PRESENCE optional}, ... } HSDSCH-InitialWindowSize -- Number of MAC-d PDUs. ::= INTEGER (1..255)

OPTIONAL,

HSDSCH-PreconfigurationInfo ::= SEQUENCE { setsOfHS-SCCH-Codes SetsOfHS-SCCH-Codes, hARQ-MemoryPartitioning HARQ-MemoryPartitioning, eDCH-FDD-DL-ControlChannelInformation EDCH-FDD-DL-ControlChannelInformation OPTIONAL, hARQ-Preamble-Mode-Activation-Indicator HARQ-Preamble-Mode-Activation-Indicator OPTIONAL, mIMO-N-M-Ratio MIMO-InformationResponse OPTIONAL, continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HSDSCH-PreconfigurationInfo-ExtIEs} } OPTIONAL, ... } HSDSCH-PreconfigurationInfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-power-offset-for-S-CPICH-for-MIMO CRITICALITY ignore optional}| { ID id-Additional-EDCH-Preconfiguration-Information CRITICALITY ignore optional}| EXTENSION PowerOffsetForSecondaryCPICHforMIMO EXTENSION Additional-EDCH-Preconfiguration-Information PRESENCE PRESENCE

3GPP

Release 11
{ ID id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order optional}, ... } Additional-EDCH-Preconfiguration-Information

1028
CRITICALITY ignore

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order PRESENCE

::= SEQUENCE (SIZE (1..maxNrOfEDCH-1)) OF Additional-EDCH-Preconfiguration-Information-ItemIEs

Additional-EDCH-Preconfiguration-Information-ItemIEs ::= SEQUENCE { eDCH-FDD-DL-ControlChannelInformation EDCH-FDD-DL-ControlChannelInformation, iE-Extensions ProtocolExtensionContainer { { Additional-EDCH-Preconfiguration-Information-ItemIEs-ExtIEs} } OPTIONAL, ... } Additional-EDCH-Preconfiguration-Information-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSDSCH-PreconfigurationSetup ::= SEQUENCE { mAChsResetScheme MAChsResetScheme, hSDSCH-Physical-Layer-Category INTEGER (1..64,...), mAChs-Reordering-Buffer-Size-for-RLC-UM MAChsReorderingBufferSize-for-RLC-UM, secondaryServingCells SecondaryServingCells OPTIONAL, numPrimaryHS-SCCH-Codes NumHS-SCCH-Codes OPTIONAL, hARQ-Preamble-Mode HARQ-Preamble-Mode OPTIONAL, mIMO-ActivationIndicator MIMO-ActivationIndicator OPTIONAL, hSDSCH-MACdPDUSizeFormat HSDSCH-MACdPDUSizeFormat OPTIONAL, sixtyfourQAM-UsageAllowedIndicator SixtyfourQAM-UsageAllowedIndicator OPTIONAL, uE-with-enhanced-HS-SCCH-support-indicator NULL OPTIONAL, continuous-Packet-Connectivity-HS-SCCH-Less-Information Continuous-Packet-Connectivity-HS-SCCH-Less-Information iE-Extensions ProtocolExtensionContainer { { HSDSCHPreconfigurationSetup-ExtIEs } } ... }

OPTIONAL, OPTIONAL,

HSDSCHPreconfigurationSetup-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UE-SupportIndicatorExtension CRITICALITY ignore EXTENSION UE-SupportIndicatorExtension PRESENCE optional}| { ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE optional}, ... } HS-SCCH-PreconfiguredCodes ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HS-SCCH-PreconfiguredCodesItem

HS-SCCH-PreconfiguredCodesItem ::= SEQUENCE { hS-SCCH-CodeNumber HS-SCCH-CodeNumber, iE-Extensions ProtocolExtensionContainer { { HS-SCCH-PreconfiguredCodesItem-ExtIEs} } OPTIONAL, ... } HS-SCCH-PreconfiguredCodesItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

1029

3GPP TS 25.423 V11.2.0 (2012-06)

HS-SCCH-CodeNumber ::= INTEGER (0..127) HSDSCH-RNTI ::= INTEGER (0..65535) HS-DSCH-serving-cell-change-information ::= SEQUENCE { hS-PDSCH-RLID RL-ID, hSDSCH-FDD-Information HSDSCH-FDD-Information iE-Extensions ProtocolExtensionContainer { { HS-DSCH-serving-cell-change-information-ExtIEs} } ... }

OPTIONAL, OPTIONAL,

HS-DSCH-serving-cell-change-information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information CRITICALITY reject EXTENSION Continuous-Packet-Connectivity-HS-SCCH-Less-Information PRESENCE optional}| { ID id-Continuous-Packet-Connectivity-DTX-DRX-Information CRITICALITY reject EXTENSION Continuous-Packet-Connectivity-DTX-DRX-Information PRESENCE optional}, ... } HS-DSCH-serving-cell-change-informationResponse ::= SEQUENCE { hS-DSCH-serving-cell-choice HS-DSCH-serving-cell-change-choice, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-serving-cell-change-informationResponse-ExtIEs} } OPTIONAL, ... } HS-DSCH-serving-cell-change-informationResponse-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-serving-cell-change-choice ::= CHOICE { hS-serving-cell-change-successful HS-serving-cell-change-successful, hS-serving-cell-change-unsuccessful HS-serving-cell-change-unsuccessful, ... } HSDSCH-TBSizeTableIndicator ::= ENUMERATED { octet-aligned } HS-serving-cell-change-successful ::= SEQUENCE { hSDSCH-FDD-Information-Response HSDSCH-FDD-Information-Response, hSDSCH-RNTI HSDSCH-RNTI, iE-Extensions ProtocolExtensionContainer { { HS-serving-cell-change-successful-ExtIEs} } OPTIONAL, ... }

3GPP

Release 11
HS-serving-cell-change-successful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response Information-Response PRESENCE optional}, ... }

1030
CRITICALITY ignore

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION Continuous-Packet-Connectivity-HS-SCCH-Less-

HS-serving-cell-change-unsuccessful ::= SEQUENCE { cause Cause, iE-Extensions ProtocolExtensionContainer { { HS-serving-cell-change-unsuccessful-ExtIEs} } OPTIONAL, ... } HS-serving-cell-change-unsuccessful-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSPDSCH-First-Code-Index ::= INTEGER (1..maxHS-PDSCHCodeNrComp-1) -- index of first HS-PDSCH code HSPDSCH-Second-Code-Index ::= INTEGER (1..maxHS-PDSCHCodeNrComp-1) -- index of second HS-PDSCH code HSPDSCH-Second-Code-Support ::= BOOLEAN -- true: applied, false: not applied HSDSCH-TDD-Information ::= SEQUENCE { hSDSCH-MACdFlows-Information uE-Capabilities-Info mAChs-Reordering-Buffer-Size-for-RLC-UM tDD-AckNack-Power-Offset iE-Extensions ... }

HSDSCH-MACdFlows-Information, UE-Capabilities-Info, MAChsReorderingBufferSize-for-RLC-UM, TDD-AckNack-Power-Offset, ProtocolExtensionContainer { { HSDSCH-TDD-Information-ExtIEs } }

OPTIONAL,

HSDSCH-TDD-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HSDSCH-MACdPDUSizeFormat CRITICALITY reject EXTENSION HSDSCH-MACdPDUSizeFormat PRESENCE optional}| { ID id-HSSICH-SIRTarget CRITICALITY ignore EXTENSION UL-SIR optional}| -- Applicable to 1.28Mcps TDD only { ID id-HSSICH-TPC-StepSize CRITICALITY ignore EXTENSION TDD-TPC-UplinkStepSize-LCR PRESENCE optional}| -- Mandatory for 1.28Mcps TDD only { ID id-tSN-Length CRITICALITY reject EXTENSION TSN-Length PRESENCE optional }| -- Applicable for 1.28Mcps TDD when using multiple frequencies { ID id-MIMO-ActivationIndicator CRITICALITY reject EXTENSION MIMO-ActivationIndicator PRESENCE optional}, ... } HSDSCH-TDD-Information-Response ::= SEQUENCE { hSDSCH-MACdFlow-Specific-InfoList-Response HSDSCH-MACdFlow-Specific-InfoList-Response OPTIONAL,

PRESENCE

3GPP

Release 11

1031

3GPP TS 25.423 V11.2.0 (2012-06)

hSSCCH-TDD-Specific-InfoList-Response HSSCCH-TDD-Specific-InfoList-Response OPTIONAL, -- Not Applicable to 1.28Mcps TDD hSSCCH-TDD-Specific-InfoList-Response-LCR HSSCCH-TDD-Specific-InfoList-Response-LCR OPTIONAL, -- Not Applicable to 3.84Mcps TDD or 7.68Mcps TDD. This HSSCCH Specific Information is for the first Frequency repetition, HSSCCH Specific Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR hSPDSCH-TDD-Specific-InfoList-Response HSPDSCH-TDD-Specific-InfoList-Response OPTIONAL, hSPDSCH-TDD-Specific-InfoList-Response-LCR HSPDSCH-TDD-Specific-InfoList-Response-LCR OPTIONAL, hARQ-MemoryPartitioning HARQ-MemoryPartitioning OPTIONAL, -- For 1.28Mcps TDD, this HARQ Memory Partitioning Information is for the first Frequency repetition, HARQ Memory Partitioning Information for Frequency repetitions 2 and on, should be defined in MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR iE-Extensions ProtocolExtensionContainer { { HSDSCH-TDD-Information-Response-ExtIEs } } OPTIONAL, ... } HSDSCH-TDD-Information-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-User-Plane-Congestion-Fields-Inclusion CRITICALITY ignore EXTENSION User-Plane-Congestion-Fields-Inclusion PRESENCE optional}| { ID id-hSSCCH-TDD-Specific-InfoList-Response768 CRITICALITY ignore EXTENSION HSSCCH-TDD-Specific-InfoList-Response768 PRESENCE optional}| { ID id-hSPDSCH-TDD-Specific-InfoList-Response768 CRITICALITY ignore EXTENSION HSPDSCH-TDD-Specific-InfoList-Response768 PRESENCE optional}| { ID id-UARFCNforNt CRITICALITY ignore EXTENSION UARFCN PRESENCE optional}| -- Applicable to 1.28Mcps TDD when using multiple frequencies ,This is the UARFCN for the first Frequency repetition { ID id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR CRITICALITY ignore EXTENSION MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR PRESENCE optional }| -- Applicable to 1.28Mcps TDD when using multiple frequencies ,This MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR is the HS-SCCH and HARQ Memory Partitioning information for the 2nd and beyond HS-PDSCH frequencies { ID id-multicarrier-number CRITICALITY ignore EXTENSION Multicarrier-Number PRESENCE optional }| -- Applicable for 1.28Mcps TDD when using multiple frequencies {ID id-MIMO-SFMode-For-HSPDSCHDualStream CRITICALITY reject EXTENSION MIMO-SFMode-For-HSPDSCHDualStream PRESENCE optional}| {ID id-MIMO-ReferenceSignal-InformationListLCR CRITICALITY reject EXTENSION MIMO-ReferenceSignal-InformationListLCR PRESENCE optional}| { ID id-TS0-HS-PDSCH-Indication-LCR CRITICALITY ignore EXTENSION TS0-HS-PDSCH-Indication-LCR PRESENCE optional }| { ID id-Out-of-Sychronization-Window CRITICALITY reject EXTENSION Out-of-Sychronization-Window PRESENCE optional}, ... } Multicarrier-Number ::= INTEGER (1..maxHSDPAFrequency) HSPDSCH-TDD-Specific-InfoList-Response ::= SEQUENCE (SIZE (0..maxNrOfDLTs)) OF HSPDSCH-TDD-Specific-InfoItem-Response HSPDSCH-TDD-Specific-InfoItem-Response ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-TDD-Specific-InfoItem-Response-ExtIEs } } OPTIONAL, ...

3GPP

Release 11
}

1032

3GPP TS 25.423 V11.2.0 (2012-06)

HSPDSCH-TDD-Specific-InfoItem-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSPDSCH-TDD-Specific-InfoList-Response-LCR ::= SEQUENCE (SIZE (1.. maxNrOfDLTsLCR)) OF HSPDSCH-TDD-Specific-InfoItem-Response-LCR HSPDSCH-TDD-Specific-InfoItem-Response-LCR ::= SEQUENCE { timeslotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-TDD-Specific-InfoItem-Response-LCR-ExtIEs } } OPTIONAL, ... } HSPDSCH-TDD-Specific-InfoItem-Response-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSPDSCH-TDD-Specific-InfoList-Response768 ::= SEQUENCE (SIZE (0..maxNrOfDLTs)) OF HSPDSCH-TDD-Specific-InfoItem-Response768 HSPDSCH-TDD-Specific-InfoItem-Response768 ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, iE-Extensions ProtocolExtensionContainer { { HSPDSCH-TDD-Specific-InfoItem-Response-768-ExtIEs } } OPTIONAL, ... } HSPDSCH-TDD-Specific-InfoItem-Response-768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSCCH-FDD-Specific-InfoList-Response ::= SEQUENCE (SIZE (0..maxNrOfHSSCCHCodes)) OF HSSCCH-FDD-Specific-InfoItem-Response HSSCCH-FDD-Specific-InfoItem-Response ::= SEQUENCE { code-Number INTEGER (0..127), iE-Extensions ProtocolExtensionContainer { { HSSCCH-FDD-Specific-InfoItem-Response-ExtIEs } } OPTIONAL, ... } HSSCCH-FDD-Specific-InfoItem-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSCCH-PowerOffset ::= INTEGER (0..255) -- PowerOffset = -32 + offset * 0.25 -- Unit dB, Range -32dB .. +31.75dB, Step +0.25dB

3GPP

Release 11

1033

3GPP TS 25.423 V11.2.0 (2012-06)

HSSCCH-TDD-Specific-InfoList-Response ::= SEQUENCE (SIZE (0..maxNrOfHSSCCHCodes)) OF HSSCCH-TDD-Specific-InfoItem-Response HSSCCH-TDD-Specific-InfoItem-Response ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, tDD-ChannelisationCode TDD-ChannelisationCode, hSSICH-Info HSSICH-Info, iE-Extensions ProtocolExtensionContainer { { HSSCCH-TDD-Specific-InfoItem-Response-ExtIEs } } OPTIONAL, ... } HSSCCH-TDD-Specific-InfoItem-Response-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSCCH-TDD-Specific-InfoList-Response-LCR ::= SEQUENCE (SIZE (0..maxNrOfHSSCCHCodes)) OF HSSCCH-TDD-Specific-InfoItem-Response-LCR HSSCCH-TDD-Specific-InfoItem-Response-LCR ::= SEQUENCE { timeslotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, first-TDD-ChannelisationCode TDD-ChannelisationCode, second-TDD-ChannelisationCode TDD-ChannelisationCode, hSSICH-InfoLCR HSSICH-InfoLCR, iE-Extensions ProtocolExtensionContainer { { HSSCCH-TDD-Specific-InfoItem-Response-LCR-ExtIEs } } OPTIONAL, ... } HSSCCH-TDD-Specific-InfoItem-Response-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSCCH-TDD-Specific-InfoList-Response768 ::= SEQUENCE (SIZE (0..maxNrOfHSSCCHCodes)) OF HSSCCH-TDD-Specific-InfoItem-Response768 HSSCCH-TDD-Specific-InfoItem-Response768 ::= SEQUENCE { timeslot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, tDD-ChannelisationCode768 TDD-ChannelisationCode768, hSSICH-Info768 HSSICH-Info768, iE-Extensions ProtocolExtensionContainer { { HSSCCH-TDD-Specific-InfoItem-Response768-ExtIEs } } OPTIONAL, ... } HSSCCH-TDD-Specific-InfoItem-Response768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSICH-Info ::= SEQUENCE { hsSICH-ID HS-SICH-ID,

3GPP

Release 11
timeslot midambleShiftAndBurstType tDD-ChannelisationCode iE-Extensions ...

1034
TimeSlot, MidambleShiftAndBurstType, TDD-ChannelisationCode, ProtocolExtensionContainer { { HSSICH-Info-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

HSSICH-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSSICH-InfoLCR ::= SEQUENCE { hsSICH-ID timeslotLCR midambleShiftLCR tDD-ChannelisationCode iE-Extensions ... } HS-SICH-ID, TimeSlotLCR, MidambleShiftLCR, TDD-ChannelisationCode, ProtocolExtensionContainer { { HSSICH-Info-LCR-ExtIEs } }

OPTIONAL,

HSSICH-Info-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-HS-SICH-ID-Extension CRITICALITY ignore EXTENSION HS-SICH-ID-Extension -- Applicable for 1.28Mcps TDD only when the HS-SICH ID IE is more than 31 ... } HSSICH-Info768 ::= SEQUENCE { hsSICH-ID timeslot midambleShiftAndBurstType768 tDD-ChannelisationCode768 iE-Extensions ... }

PRESENCE optional},

HS-SICH-ID, TimeSlot, MidambleShiftAndBurstType768, TDD-ChannelisationCode768, ProtocolExtensionContainer { { HSSICH-Info-768-ExtIEs } }

OPTIONAL,

HSSICH-Info-768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-SICH-Reception-Quality-Value failed-HS-SICH missed-HS-SICH total-HS-SICH iE-Extensions ... } ::= SEQUENCE { HS-SICH-failed, HS-SICH-missed, HS-SICH-total, ProtocolExtensionContainer { { HS-SICH-Reception-Quality-Value-ExtIEs} } OPTIONAL,

HS-SICH-Reception-Quality-Value-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
HS-SICH-failed ::= INTEGER (0..20) HS-SICH-missed ::= INTEGER (0..20) HS-SICH-total ::= INTEGER (0..20) HS-SICH-Reception-Quality-Measurement-Value ::= INTEGER (0..20) -- According to mapping in TS 25.133 [23] HS-SICH-ID ::= INTEGER (0..31) HS-SICH-ID-Extension ::= INTEGER (32..255,...) HSSCCH-CodeChangeIndicator hsSCCHCodeChangeNeeded } HSSCCH-Code-Change-Grant changeGranted } ::= ENUMERATED {

1035

3GPP TS 25.423 V11.2.0 (2012-06)

::= ENUMERATED {

HS-PDSCH-Code-Change-Indicator hsPDSCHCodeChangeNeeded } HS-PDSCH-Code-Change-Grant changeGranted }

::= ENUMERATED {

::= ENUMERATED {

HSDSCH-FDD-Update-Information ::= SEQUENCE { hsSCCHCodeChangeIndicator cqiFeedback-CycleK cqiRepetitionFactor ackNackRepetitionFactor cqiPowerOffset ackPowerOffset nackPowerOffset iE-Extensions ... }

HSSCCH-CodeChangeIndicator OPTIONAL, CQI-Feedback-Cycle OPTIONAL, CQI-RepetitionFactor OPTIONAL, AckNack-RepetitionFactor OPTIONAL, CQI-Power-Offset OPTIONAL, Ack-Power-Offset OPTIONAL, Nack-Power-Offset OPTIONAL, ProtocolExtensionContainer { { HSDSCH-FDD-Update-Information-ExtIEs } }

OPTIONAL,

HSDSCH-FDD-Update-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-HS-PDSCH-Code-Change-Indicator CRITICALITY ignore EXTENSION ... } HSDSCH-TDD-Update-Information ::= SEQUENCE { hsSCCHCodeChangeIndicator tDDAckNackPowerOffset iE-Extensions ...

HS-PDSCH-Code-Change-Indicator

PRESENCE optional },

HSSCCH-CodeChangeIndicator OPTIONAL, TDD-AckNack-Power-Offset OPTIONAL, ProtocolExtensionContainer { { HSDSCH-TDD-Update-Information-ExtIEs } }

OPTIONAL,

3GPP

Release 11
} HSDSCH-TDD-Update-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

1036

3GPP TS 25.423 V11.2.0 (2012-06)

MIMO-ReferenceSignal-InformationListLCR ::= SEQUENCE (SIZE (1..maxNrOfHSSCCHCodes)) OF HSSICH-ReferenceSignal-InformationLCR HSSICH-ReferenceSignal-InformationLCR ::= SEQUENCE { midambleConfigurationLCR MidambleConfigurationLCR, midambleShift INTEGER (0..15), timeSlotLCR TimeSlotLCR, iE-Extensions ProtocolExtensionContainer { { HSSICH-ReferenceSignal-InformationLCR-ExtIEs } } ... } HSSICH-ReferenceSignal-InformationLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-Semi-PersistentScheduling-Information-LCR ::= SEQUENCE { transport-Block-Size-List Transport-Block-Size-List-LCR, repetition-Period-List-LCR Repetition-Period-List-LCR, hS-DSCH-SPS-Reservation-Indicator SPS-Reservation-Indicator OPTIONAL, hS-DSCH-SPS-Operation-Indicator HS-DSCH-SPS-Operation-Indicator, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-LCR-ExtIEs } } OPTIONAL, ... } HS-DSCH-Semi-PersistentScheduling-Information-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HSDSCH-Physical-Layer-Category ::= INTEGER (1..64) Transport-Block-Size-List-LCR ::= SEQUENCE (SIZE (1..maxNoOfTBSs-Mapping-HS-DSCH-SPS)) OF Transport-Block-Size-Item-LCR Transport-Block-Size-Item-LCR ::= SEQUENCE { transport-Block-Size-maping-Index-LCR transport-Block-Size-Index-LCR iE-Extensions ... } Transport-Block-Size-maping-Index-LCR, Transport-Block-Size-Index-LCR, ProtocolExtensionContainer { { Transport-Block-Size-Item-LCR-ExtIEs } }

OPTIONAL,

OPTIONAL,

Transport-Block-Size-Item-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Transport-Block-Size-maping-Index-LCR ::= INTEGER (0..maxNoOfTBSs-Mapping-HS-DSCH-SPS-1)

3GPP

Release 11
Transport-Block-Size-Index-LCR ::= INTEGER (1..maxNoOfHS-DSCH-TBSsLCR) TS0-HS-PDSCH-Indication-LCR ::= NULL

1037

3GPP TS 25.423 V11.2.0 (2012-06)

Repetition-Period-List-LCR ::= SEQUENCE (SIZE (1..maxNoOfRepetition-Period-LCR)) OF Repetition-Period-Item-LCR Repetition-Period-Item-LCR ::= SEQUENCE { repetitionPeriodIndex RepetitionPeriodIndex, repetitionPeriod RepetitionPeriod, repetitionLength RepetitionLength OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Repetition-Period-Item-LCR-ExtIEs } } ... } Repetition-Period-Item-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RepetitionPeriodIndex ::= INTEGER (0..maxNoOfRepetitionPeriod-SPS-LCR-1) SPS-Reservation-Indicator ::= ENUMERATED { reserve } HS-DSCH-SPS-Operation-Indicator ::= CHOICE { logicalChannellevel LogicalChannellevel, priorityQueuelevel PriorityQueuelevel, ... } LogicalChannellevel ::= BIT STRING (SIZE (16)) PriorityQueuelevel ::= BIT STRING (SIZE (8)) HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR ::= SEQUENCE { transport-Block-Size-List Transport-Block-Size-List-LCR OPTIONAL, repetition-Period-List-LCR Repetition-Period-List-LCR OPTIONAL, hS-DSCH-SPS-Reservation-Indicator SPS-Reservation-Indicator OPTIONAL, hS-DSCH-SPS-Operation-Indicator HS-DSCH-SPS-Operation-Indicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs } } OPTIONAL, ... } HS-DSCH-Semi-PersistentScheduling-Information-to-Modify-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR ::= SEQUENCE { hS-SICH-InformationList-for-HS-DSCH-SPS HS-SICH-InformationList-for-HS-DSCH-SPS, initial-HS-PDSCH-SPS-Resource Initial-HS-PDSCH-SPS-Resource OPTIONAL,

OPTIONAL,

3GPP

Release 11
buffer-Size-for-HS-DSCH-SPS number-of-Processes-for-HS-DSCH-SPS iE-Extensions OPTIONAL, ...

1038

3GPP TS 25.423 V11.2.0 (2012-06)

Process-Memory-Size OPTIONAL, Number-of-Processes-for-HS-DSCH-SPS OPTIONAL, ProtocolExtensionContainer { { HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs } }

HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-SICH-InformationList-for-HS-DSCH-SPS ::= SEQUENCE (SIZE (1..maxNoOf-HS-SICH-SPS)) OF HS-SICH-InformationItem-for-HS-DSCH-SPS HS-SICH-InformationItem-for-HS-DSCH-SPS ::= SEQUENCE { hS-SICH-Mapping-Index HS-SICH-Mapping-Index OPTIONAL, hS-SICH-Type HS-SICH-Type, iE-Extensions ProtocolExtensionContainer { { HS-SICH-InformationItem-for-HS-DSCH-SPS-ExtIEs } } ... } HS-SICH-InformationItem-for-HS-DSCH-SPS-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-SICH-Mapping-Index ::= INTEGER (0..maxNoOf-HS-SICH-SPS-1) HS-SICH-Type ::= CHOICE { hS-SCCH-Associated-HS-SICH non-HS-SCCH-Associated-HS-SICH ... } HS-SCCH-Associated-HS-SICH, Non-HS-SCCH-Associated-HS-SICH,

OPTIONAL,

HS-SCCH-Associated-HS-SICH ::= SEQUENCE { hsSICH-ID HS-SICH-ID, extended-HS-SICH-ID HS-SICH-ID-Extension ... }

OPTIONAL,

Non-HS-SCCH-Associated-HS-SICH::= SEQUENCE { non-HS-SCCH-Aassociated-HS-SICH-ID Non-HS-SCCH-Aassociated-HS-SICH-ID, ... } Non-HS-SCCH-Aassociated-HS-SICH-ID ::= INTEGER (0..255) Initial-HS-PDSCH-SPS-Resource::= SEQUENCE { repetitionPeriodIndex repetitionLength hS-PDSCH-Offset RepetitionPeriodIndex, RepetitionLength TDD-PhysicalChannelOffset,

OPTIONAL,

3GPP

Release 11
hS-PDSCH-Midamble-Configuation timeslot-Resource-Related-Information startCode endCode transport-Block-Size-Index modulationType hS-SICH-Mapping-Index iE-Extensions ... } Initial-HS-PDSCH-SPS-Resource-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } HS-DSCH-TimeslotResourceLCR ::= BIT STRING (SIZE (5)) ModulationSPS-LCR ::= ENUMERATED { qPSK, sixteenQAM, ... } Number-of-Processes-for-HS-DSCH-SPS ::= INTEGER (1..16) -- I IMEI IMEISV IMSI ::= OCTET STRING (SIZE(8)) ::= OCTET STRING (SIZE(8)) ::= OCTET STRING (SIZE(3..8))

1039
MidambleShiftLCR, HS-DSCH-TimeslotResourceLCR, TDD-ChannelisationCode, TDD-ChannelisationCode, Transport-Block-Size-Index-LCR, ModulationSPS-LCR, HS-SICH-Mapping-Index, ProtocolExtensionContainer { { Initial-HS-PDSCH-SPS-Resource-ExtIEs } }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

Inactivity-Threshold-for-UE-DTX-Cycle2 ::= ENUMERATED {v1, v4, v8, v16, v32, v64, v128, v256} -- Unit E-DCH TTI Inactivity-Threshold-for-UE-DRX-Cycle ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256, v512} -- Unit subframe Inactivity-Threshold-for-UE-Grant-Monitoring ::= ENUMERATED {v0, v1, v2, v4, v8, v16, v32, v64, v128, v256} -- Unit E-DCH TTI

InformationAvailable::= SEQUENCE { requestedDataValue RequestedDataValue, iE-Extensions ProtocolExtensionContainer { { InformationAvailable-ExtIEs} } ... } InformationAvailable-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

3GPP

Release 11
} ...

1040

3GPP TS 25.423 V11.2.0 (2012-06)

InformationExchangeID ::= INTEGER (0..1048575) InformationNotAvailable ::= NULL InformationReportCharacteristics ::= CHOICE { onDemand NULL, periodic PeriodicInformation, onModification OnModificationInformation, ... } InformationReportPeriodicity ::= CHOICE { min INTEGER (1..60,...), -- Unit min, Step 1min hour INTEGER (1..24,...), -- Unit hour, Step 1hour ... } InformationThreshold ::= CHOICE { dGPSThreshold DGPSThreshold, ..., dGANSSThreshold DGANSSThreshold } InformationType ::= SEQUENCE { informationTypeItem ENUMERATED { gA-AccessPointPositionwithAltitude, gA-AccessPointPosition, iPDLParameters, gPSInformation, dGPSCorrections, gPS-RX-POS, sFNSFN-GA-AccessPointPosition, ..., cell-Capacity-Class, nACC-Related-Data, mBMSBearerServiceFullAddress, interFrequencyCellInformation, gANSSInformation, dGANSSCorrections, gANSS-RX-Pos, mBMS-Counting-Information, mBMS-Transmission-Mode, mBMS-Neighbouring-Cell-Information, mBMS-RLC-Sequence-Number, aNR-Cell-Information

3GPP

Release 11
}, gPSInformation iE-Extensions ... }

1041
GPSInformation OPTIONAL, ProtocolExtensionContainer { { InformationType-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

-- The GPS Information IE shall be present if the Information Exchange Type IE indicates GPS Information -- For information exchange on the Iur-g interface, only the Cell Capacity Class is used. InformationType-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { -- The following IE shall be present if the Information Type Item IE indicates GANSS Information { ID id-GANSS-Information CRITICALITY ignore EXTENSION GANSS-Information PRESENCE conditional }| -- The following IE shall be present if the Information Type Item IE indicates DGANSS Corrections { ID id-DGANSS-Corrections-Req CRITICALITY ignore EXTENSION DGANSS-Corrections-Req PRESENCE conditional }| -- The following IE shall be present if the Information Type Item IE indicates MBMS RLC Sequence Number { ID id-MBMS-RLC-Sequence-Number-Information CRITICALITY ignore EXTENSION MBMS-RLC-Sequence-Number-Information ... } Initial-DL-DPCH-TimingAdjustment-Allowed ::= ENUMERATED { initial-DL-DPCH-TimingAdjustment-Allowed } InnerLoopDLPCStatus ::= ENUMERATED {active, inactive} IPDL-FDD-Parameters, IPDL-TDD-Parameters,

PRESENCE conditional },

IPDLParameters ::= CHOICE { iPDL-FDD-Parameters iPDL-TDD-Parameters ..., extension-IPDLParameters } Extension-IPDLParameters

--3.84Mcps TDD and 7.68Mcps TDD only

Extension-IPDLParameters

::= ProtocolIE-Single-Container {{ Extension-IPDLParametersIE }} TYPE IPDL-TDD-ParametersLCR PRESENCE mandatory },

Extension-IPDLParametersIE RNSAP-PROTOCOL-IES ::= { { ID id-IPDL-TDD-ParametersLCR CRITICALITY reject ... } Inter-Frequency-Cell-List

::= SEQUENCE (SIZE (0..maxCellsMeas)) OF Inter-Frequency-Cell

Inter-Frequency-Cell ::= SEQUENCE { dL-UARFCN UARFCN, uL-UARFCN UARFCN OPTIONAL, primaryScramblingCode PrimaryScramblingCode, iE-Extensions ProtocolExtensionContainer { {Inter-Frequency-Cell-ExtIEs} } ... } Inter-Frequency-Cell-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

OPTIONAL,

3GPP

Release 11
}

1042

3GPP TS 25.423 V11.2.0 (2012-06)

Inter-Frequency-Cell-Information ::= SEQUENCE { inter-Frequency-Cell-Information-SIB11 Inter-Frequency-Cell-Information-SIB11, inter-Frequency-Cell-Information-SIB12 Inter-Frequency-Cell-Information-SIB12, iE-Extensions ProtocolExtensionContainer { {Inter-Frequency-Cell-Information-ExtIEs } } ... } Inter-Frequency-Cell-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

Inter-Frequency-Cell-Information-SIB11 ::= SEQUENCE (SIZE (0..2)) OF Inter-Frequency-Cells-Information-SIB11-Per-Indication Inter-Frequency-Cell-Information-SIB12 ::= SEQUENCE (SIZE (0..2)) OF Inter-Frequency-Cells-Information-SIB12-Per-Indication Inter-Frequency-Cells-Information-SIB11-Per-Indication ::= SEQUENCE { inter-Frequency-Cell-Indication-SIB11 Inter-Frequency-Cell-Indication, inter-Frequency-Cell-List-SIB11 Inter-Frequency-Cell-SIB11-or-SIB12-List, iE-Extensions ProtocolExtensionContainer { { Inter-Frequency-Cells-Information-SIB11-Per-Indication-ExtIEs } } ... } Inter-Frequency-Cells-Information-SIB11-Per-Indication-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Inter-Frequency-Cells-Information-SIB12-Per-Indication ::= SEQUENCE { inter-Frequency-Cell-Indication-SIB12 Inter-Frequency-Cell-Indication, inter-Frequency-Cell-List-SIB12 Inter-Frequency-Cell-SIB11-or-SIB12-List, iE-Extensions ProtocolExtensionContainer { { Inter-Frequency-Cells-Information-SIB12-Per-Indication-ExtIEs } } ... } Inter-Frequency-Cells-Information-SIB12-Per-Indication-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Inter-Frequency-Cell-Indication ::= INTEGER (0..1) Inter-Frequency-Cell-SIB11-or-SIB12-List ::= SEQUENCE (SIZE (0..maxCellSIB11OrSIB12)) OF Inter-Frequency-Cell-SIB11-or-SIB12 Inter-Frequency-Cell-SIB11-or-SIB12 ::= SEQUENCE { interFrequencyCellID InterFrequencyCellID, dL-UARFCN UARFCN, uL-UARFCN UARFCN OPTIONAL, primaryScramblingCode PrimaryScramblingCode, iE-Extensions ProtocolExtensionContainer { {Inter-Frequency-Cell-ExtIEs} } ... }

OPTIONAL,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
InterFrequencyCellID ::= INTEGER (0..31)

1043

3GPP TS 25.423 V11.2.0 (2012-06)

IPDL-FDD-Parameters ::= SEQUENCE { iPSpacingFDD IPSpacingFDD, iPLength IPLength, iPOffset IPOffset, seed Seed, burstModeParameters BurstModeParameters OPTIONAL, iE-Extensions ProtocolExtensionContainer { { IPDL-FDD-Parameters-ExtIEs} } ... } IPDL-FDD-Parameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } IPDL-TDD-Parameters ::= SEQUENCE { iPSpacingTDD IPSpacingTDD, iPStart IPStart, iPSlot IPSlot, iP-P-CCPCH IP-P-CCPCH, burstModeParameters BurstModeParameters OPTIONAL, iE-Extensions ProtocolExtensionContainer { { IPDL-TDD-Parameters-ExtIEs} } ... } -- The BurstModeParameters IE shall be included if the Idle Periods are arranged in Burst Mode. IPDL-TDD-Parameters-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } IPDL-TDD-ParametersLCR ::= SEQUENCE { iPSpacingTDD IPSpacingTDD, iPStart IPStart, iPSub IPSub, burstModeParameters BurstModeParameters OPTIONAL, iE-Extensions ProtocolExtensionContainer { { IPDL-TDD-ParametersLCR-ExtIEs} } ... } -- The BurstModeParameters IE shall be included if the Idle Periods are arranged in Burst Mode. IPDL-TDD-ParametersLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } IPLength ::= ENUMERATED { ipl5,

OPTIONAL,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
ipl10, ... } IPMulticastAddress ::= OCTET STRING (SIZE (4..16))

1044

3GPP TS 25.423 V11.2.0 (2012-06)

IPOffset ::= INTEGER (0..9) IP-P-CCPCH ::= ENUMERATED { switchOff-1-Frame, switchOff-2-Frames } IPSlot ::= INTEGER (0..14) IPSpacingFDD ::= ENUMERATED { ipsF5, ipsF7, ipsF10, ipsF15, ipsF20, ipsF30, ipsF40, ipsF50, ... } IPSpacingTDD ::= ENUMERATED { ipsT30, ipsT40, ipsT50, ipsT70, ipsT100, ... } IPStart ::= INTEGER (0..4095) IPSub ::= ENUMERATED { first, second, both } IdleIntervalInformation ::= SEQUENCE { idleIntervalInfo-k idleIntervalInfo-offset ... } -- J INTEGER(2..3), INTEGER(0..7),

3GPP

Release 11
-- K -- L LABased ::= SEQUENCE { laiList iE-Extensions ... }

1045

3GPP TS 25.423 V11.2.0 (2012-06)

LAI-List, ProtocolExtensionContainer { {LABased-ExtIEs} } OPTIONAL,

LABased-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } LAI-List LAI LAC LAI ::= SEQUENCE (SIZE (1..maxNrOfLAIs)) OF ::= OCTET STRING (SIZE (2)) --(EXCEPT (0000H|FFFEH)) ::= SEQUENCE { pLMN-Identity lAC iE-Extensions ... PLMN-Identity, LAC, ProtocolExtensionContainer { {LAI-ExtIEs} } OPTIONAL,

LimitedPowerIncrease ::= ENUMERATED { used, not-used } List-Of-PLMNs ::= SEQUENCE (SIZE (1..maxNrOfBroadcastPLMNs)) OF PLMN-Identity L3-Information ::= BIT STRING

Load-Value-IncrDecrThres ::= INTEGER(0..100) Load-Value ::= INTEGER(0..100) LoadValue ::= SEQUENCE { uplinkLoadValue downlinkLoadValue } INTEGER(0..100), INTEGER(0..100)

LCRTDD-Uplink-Physical-Channel-Capability ::= SEQUENCE { maxTimeslotsPerSubFrame INTEGER(1..6), maxPhysChPerTimeslot ENUMERATED{ts1, ts2, ts3, ts4,...}, iE-Extensions ProtocolExtensionContainer { { LCRTDD-Uplink-Physical-Channel-Capability-ExtIEs} } OPTIONAL, ... } LCRTDD-Uplink-Physical-Channel-Capability-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
... } -- M M1Report ::= CHOICE { periodic MDT-Report-Parameters, event1F Event1F-Parameters, ... } M2Report ::= CHOICE { periodic MDT-Report-Parameters, event1I Event1I-Parameters, ... } MDT-Activation ::= ENUMERATED { mdt-only, mdt-and-trace, ... }

1046

3GPP TS 25.423 V11.2.0 (2012-06)

MDTAreaScope ::= CHOICE { cellbased CellBased, labased LABased, rabased RABased, plmn-area-based NULL, ... } MDT-Configuration ::= SEQUENCE { mdtActivation MDT-Activation, mdtAreaScope MDTAreaScope, m1report M1Report OPTIONAL, m2report M2Report OPTIONAL, m3report NULL OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MDT-Configuration-ExtIEs} } OPTIONAL, ... } MDT-Configuration-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MDT-Report-Parameters reportInterval reportAmount ... } MeasurementQuantity ::= SEQUENCE { ReportInterval, ReportAmount,

::= ENUMERATED {

3GPP

Release 11
cpichEcNo, cpichRSCP, pathloss, ... } MaxNrOfUL-DPCHs MAC-c-sh-SDU-Length ::= INTEGER (1..6) ::= INTEGER (1..5000)

1047

3GPP TS 25.423 V11.2.0 (2012-06)

MAC-c-sh-SDU-LengthList ::= SEQUENCE(SIZE(1..maxNrOfMACcshSDU-Length)) OF MAC-c-sh-SDU-Length MAC-DTX-Cycle-2ms ::= ENUMERATED {v1, v4, v5, v8, v10, v16, v20} MAC-DTX-Cycle-10ms ::= ENUMERATED {v5, v10, v20} MAC-ehs-Reset-Timer ::= ENUMERATED {v1, v2, v3, v4,...} MAC-Inactivity-Threshold ::= ENUMERATED {v1, v2, v4, v8, v16, v32, v64, v128, v256, v512, infinity} -- Unit subframe MACdPDU-Size ::= INTEGER (1..5000,...) -- In case of E-DCH value 8 and values not multiple of 8 shall not be used MAC-PDU-SizeExtended ::= INTEGER (1..1504,...,1505) -- In case of E-DCH value 1 shall not be used MACdPDU-Size-IndexList ::= SEQUENCE (SIZE (1..maxNrOfPDUIndexes)) OF MACdPDU-Size-IndexItem MACdPDU-Size-IndexItem ::= SEQUENCE { sID mACdPDU-Size iE-Extensions ... } SID, MACdPDU-Size, ProtocolExtensionContainer { { MACdPDU-Size-IndexItem-ExtIEs } }

OPTIONAL,

MACdPDU-Size-IndexItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MACdPDU-Size-IndexList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfPDUIndexes)) OF MACdPDU-Size-IndexItem-to-Modify MACdPDU-Size-IndexItem-to-Modify ::= SEQUENCE { sID SID, mACdPDU-Size MACdPDU-Size, iE-Extensions ProtocolExtensionContainer { { MACdPDU-Size-IndexItem-to-Modify-ExtIEs } } ... } MACdPDU-Size-IndexItem-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

OPTIONAL,

3GPP

Release 11
}

1048

3GPP TS 25.423 V11.2.0 (2012-06)

MACes-Guaranteed-Bitrate ::= INTEGER (0..16777215,...,16777216..256000000) MACes-Maximum-Bitrate-LCR ::= INTEGER (0..256000000,...) MACeReset-Indicator ::= ENUMERATED {mACeReset} MAChsGuaranteedBitRate ::= INTEGER (0..16777215,...,16777216..1000000000) MAChsReorderingBufferSize-for-RLC-UM ::= INTEGER (0..300,...) -- Unit kBytes MAC-hsWindowSize ::= ENUMERATED {v4, v6, v8, v12, v16, v24, v32,... , v64, v128, v256}

MAChsResetScheme ::= ENUMERATED { always, interNodeB-change } MaximumAllowedULTxPower ::= INTEGER (-50..33)

Max-Bits-MACe-PDU-non-scheduled ::= INTEGER(1..maxNrOfBits-MACe-PDU-non-scheduled) MaxNrDLPhysicalchannels ::= INTEGER (1..224) -- 1.28Mcps TDD 97 224 are unused MaxNrDLPhysicalchannels768 MaxNrDLPhysicalchannelsTS ::= INTEGER (1..448) ::= INTEGER (1..16) ::= INTEGER (1..32) ::= INTEGER (0..15)

MaxNrDLPhysicalchannelsTS768 MaxNr-Retransmissions-EDCH

MaxNrTimeslots ::= INTEGER (1..14) -- 1.28Mcps values 7-14 are unused MaxNrULPhysicalchannels ::= INTEGER (1..2)

Max-Set-E-DPDCHs ::= ENUMERATED { vN256, vN128, vN64, vN32, vN16, vN8, vN4, v2xN4, v2xN2, v2xN2plus2xN4, ..., v2xM2plus2xM4 } -- Values releated to TS 25.212 [9] Max-UE-DTX-Cycle ::= ENUMERATED { v5, v10, v20, v40, v64, v80, v128, v160,

3GPP

Release 11
... }

1049

3GPP TS 25.423 V11.2.0 (2012-06)

MBMS-Bearer-Service-Full-Address ::= SEQUENCE { accessPointName AccessPointName, iPMulticastAddress IPMulticastAddress, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-Service-Full-Address-ExtIEs } } ... } MBMS-Bearer-Service-Full-Address-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-Service-List ::= SEQUENCE (SIZE (1..maxNrOfMBMSServices)) OF TMGI

OPTIONAL,

MBMS-Bearer-ServiceItemFDD ::=SEQUENCE{ tmgi TMGI, transmissionMode TransmissionMode, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-ServiceItemFDD-ExtIEs} } OPTIONAL, ... } MBMS-Bearer-ServiceItemFDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-ServiceItemFDD-PFL ::=SEQUENCE{ tmgi TMGI, transmissionMode TransmissionMode OPTIONAL, preferredFrequencyLayer UARFCN OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-ServiceItemFDD-PFL-ExtIEs} } OPTIONAL, ... } MBMS-Bearer-ServiceItemFDD-PFL-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-ServiceItemTDD ::=SEQUENCE{ tmgi TMGI, transmissionMode TransmissionMode, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-ServiceItemTDD-ExtIEs} } OPTIONAL, ... } MBMS-Bearer-ServiceItemTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1050

3GPP TS 25.423 V11.2.0 (2012-06)

MBMS-Bearer-ServiceItemTDD-PFL ::=SEQUENCE{ tmgi TMGI, transmissionMode TransmissionMode OPTIONAL, preferredFrequencyLayer UARFCN OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MBMS-Bearer-ServiceItemTDD-PFL-ExtIEs} } OPTIONAL, ... } MBMS-Bearer-ServiceItemTDD-PFL-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMSChannelTypeInfo ::= SEQUENCE { tMGI TMGI, pTM-Cell-List PTMCellList OPTIONAL, pTP-Cell-List PTPCellList OPTIONAL, not-Provided-Cell-List NotProvidedCellList OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MBMSChannelTypeInfo-ExtIEs} } OPTIONAL, ... } MBMSChannelTypeInfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMSChannelTypeCellList ::= SEQUENCE { c-ID affectedUEInformationForMBMS iE-Extensions ... } C-ID, AffectedUEInformationForMBMS OPTIONAL, ProtocolExtensionContainer { { MBMSChannelTypeCellList-ExtIEs} } OPTIONAL,

MBMSChannelTypeCellList-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-ExtendedAffectedUEInformationForMBMS CRITICALITY ignore ... }

EXTENSION ExtendedAffectedUEInformationForMBMS

PRESENCE optional},

MBMSPreferredFreqLayerInfo ::= SEQUENCE { tMGI TMGI, preferredFrequencyLayerInfo PreferredFrequencyLayerInfo, iE-Extensions ProtocolExtensionContainer { { MBMSPreferredFreqLayerInfo-ExtIEs} } OPTIONAL, ... } MBMSPreferredFreqLayerInfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Neighbouring-Cell-Information ::= SEQUENCE { mBMS-ConcatenatedServiceList MBMS-ConcatenatedServiceList, l3-Information-1 L3-Information OPTIONAL, -- This IE contains MBMS COMMON P-T-M RB INFORMATION defined in TS 25.331 [16] l3-Information-2 L3-Information OPTIONAL,

3GPP

Release 11

1051

3GPP TS 25.423 V11.2.0 (2012-06)

-- This IE contains MBMS CURRENT CELL P-T-M RB INFORMATION defined in TS 25.331 [16] iE-Extensions ProtocolExtensionContainer { { MBMS-Neighbouring-Cell-Information-ExtIEs} } OPTIONAL, ... } MBMS-Neighbouring-Cell-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-ConcatenatedServiceList ::= SEQUENCE (SIZE (1..maxlengthMBMSconcatservlists)) OF TMGI MBMS-RLC-Sequence-Number-Information ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMS-RLC-Sequence-Number-Information-List

MBMS-RLC-Sequence-Number-Information-List ::= SEQUENCE { c-ID C-ID, mBMS-Bearer-Service-List-RLC MBMS-Bearer-Service-List-RLC, iE-Extensions ProtocolExtensionContainer { { MBMS-RLC-Sequence-Number-Information-List-ExtIEs} } ... } MBMS-RLC-Sequence-Number-Information-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBMS-Bearer-Service-List-RLC::= SEQUENCE (SIZE (1..maxNrOfMBMSServices)) OF MBMS-Bearer-Service-List-RLCinfo MBMS-Bearer-Service-List-RLCinfo tmgi time-Stamp iE-Extensions ... } ::= SEQUENCE { TMGI, Time-Stamp, ProtocolExtensionContainer

OPTIONAL,

{ { MBMS-Bearer-Service-List-RLCinfo-ExtIEs} }

OPTIONAL,

MBMS-Bearer-Service-List-RLCinfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MBSFN-Cluster-Identity MCCH-Message-List ::= INTEGER (0..65535)

::= SEQUENCE (SIZE (1.. maxNrOfMCCHMessages)) OF L3-Information Secondary-CCPCH-System-Information-MBMS, ProtocolExtensionContainer { {MCCH-Configuration-Info-ExtIEs } }

MCCH-Configuration-Info ::= SEQUENCE { secondaryCCPCHSystemInformationMBMS ie-Extensions ... }

OPTIONAL,

MCCH-Configuration-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
} Secondary-CCPCH-System-Information-MBMS ::= BIT STRING ::=

1052

3GPP TS 25.423 V11.2.0 (2012-06)

MBSFN-Scheduling-Transmission-Time-Interval-Info-List

SEQUENCE (SIZE (1.. maxNrOfMBMSL3)) OF MBSFN-Scheduling-Transmission-Time-Interval-Item

MBSFN-Scheduling-Transmission-Time-Interval-Item ::= SEQUENCE { tMGI TMGI, mbsfnSchedulingTransmissionTimeInterval MbsfnSchedulingTransmissionTimeInterval, ie-Extensions ProtocolExtensionContainer { { MBSFN-Scheduling-Transmission-Time-Interval-Item-ExtIEs } } ... } MBSFN-Scheduling-Transmission-Time-Interval-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL,

MbsfnSchedulingTransmissionTimeInterval ::= ENUMERATED {tti4, tti8, tti16, tti32, tti64, tti128, tti256} MeasurementFilterCoefficient ::= ENUMERATED{k0, k1, k2, k3, k4, k5, k6, k7, k8, k9, k11, k13, k15, k17, k19,...} -- Measurement Filter Coefficient to be used for measurement MeasurementID ::= INTEGER (0..1048575)

Measurement-Power-Offset ::= INTEGER(-12 .. 26) -- Actual value = IE value * 0.5 MinimumSpreadingFactor MinimumSpreadingFactor768 ::= INTEGER (1..16) ::= INTEGER (1..32)

MultipleURAsIndicator ::= ENUMERATED { multiple-URAs-exist, single-URA-exists } MaxAdjustmentStep -- Unit Slot ::= INTEGER(1..10)

MeasurementChangeTime ::= INTEGER (1..6000,...) -- The MeasurementChangeTime gives the MeasurementChangeTime -- in number of 10 ms periods. -- E.g. Value 6000 means 60000ms(1min) -- Unit is ms, Step is 10 ms MeasurementHysteresisTime ::= INTEGER (1..6000,...) -- The MeasurementHysteresisTime gives the -- MeasurementHysteresisTime in number of 10 ms periods.

3GPP

Release 11
-- E.g. Value 6000 means 60000ms(1min) -- Unit is ms, Step is 10ms

1053

3GPP TS 25.423 V11.2.0 (2012-06)

MeasurementIncreaseDecreaseThreshold ::= CHOICE { sir SIR-Value-IncrDecrThres, sir-error SIR-Error-Value-IncrDecrThres, transmitted-code-power Transmitted-Code-Power-Value-IncrDecrThres, rscp RSCP-Value-IncrDecrThres, round-trip-time Round-Trip-Time-IncrDecrThres, ..., extension-MeasurementIncreaseDecreaseThreshold Extension-MeasurementIncreaseDecreaseThreshold } Extension-MeasurementIncreaseDecreaseThreshold ::= ProtocolIE-Single-Container {{ Extension-MeasurementIncreaseDecreaseThresholdIE }}

Extension-MeasurementIncreaseDecreaseThresholdIE RNSAP-PROTOCOL-IES ::= { { ID id-Load-Value-IncrDecrThres CRITICALITY reject TYPE Load-Value-IncrDecrThres PRESENCE mandatory }| { ID id-Transmitted-Carrier-Power-Value-IncrDecrThres CRITICALITY reject TYPE Transmitted-Carrier-Power-Value-IncrDecrThres PRESENCE mandatory }| { ID id-Received-Total-Wideband-Power-Value-IncrDecrThres CRITICALITY reject TYPE Received-Total-Wideband-Power-Value-IncrDecrThres PRESENCE mandatory }| { ID id-UL-Timeslot-ISCP-Value-IncrDecrThres CRITICALITY reject TYPE UL-Timeslot-ISCP-Value-IncrDecrThres PRESENCE mandatory }| { ID id-RT-Load-Value-IncrDecrThres CRITICALITY reject TYPE RT-Load-Value-IncrDecrThres PRESENCE mandatory }| { ID id-NRT-Load-Information-Value-IncrDecrThres CRITICALITY reject TYPE NRT-Load-Information-Value-IncrDecrThres PRESENCE mandatory }| { ID id-UpPTSInterferenceValue CRITICALITY reject TYPE UpPTSInterferenceValue PRESENCE mandatory } } MeasurementRecoveryBehavior ::= NULL MeasurementRecoveryReportingIndicator ::= NULL MeasurementRecoverySupportIndicator ::= NULL MeasurementThreshold ::= sir sir-error transmitted-code-power rscp rx-timing-deviation round-trip-time ..., extension-MeasurementThreshold } Extension-MeasurementThreshold CHOICE { SIR-Value, SIR-Error-Value, Transmitted-Code-Power-Value, RSCP-Value, Rx-Timing-Deviation-Value, Round-Trip-Time-Value, Extension-MeasurementThreshold

::= ProtocolIE-Single-Container {{ Extension-MeasurementThresholdIE }} TYPE TUTRANGPSMeasurementThresholdInformation TYPE SFNSFNMeasurementThresholdInformation PRESENCE PRESENCE

Extension-MeasurementThresholdIE RNSAP-PROTOCOL-IES ::= { { ID id-TUTRANGPSMeasurementThresholdInformation CRITICALITY reject mandatory }| { ID id-SFNSFNMeasurementThresholdInformation CRITICALITY reject mandatory }|

3GPP

Release 11
{ ID id-Load-Value PRESENCE mandatory }| { ID id-Transmitted-Carrier-Power-Value mandatory }| { ID id-Received-Total-Wideband-Power-Value mandatory }| { ID id-UL-Timeslot-ISCP-Value PRESENCE mandatory }| { ID id-RT-Load-Value PRESENCE mandatory }| { ID id-NRT-Load-Information-Value PRESENCE mandatory }| { ID id-Rx-Timing-Deviation-Value-LCR mandatory}| { ID id-HS-SICH-Reception-Quality-Measurement-Value { ID id-UpPTSInterferenceValue PRESENCE mandatory }| { ID id-Rx-Timing-Deviation-Value-768 mandatory}| { ID id-Rx-Timing-Deviation-Value-ext mandatory}| { ID id-Extended-Round-Trip-Time-Value mandatory }| { ID id-TUTRANGANSSMeasurementThresholdInformation } MidambleConfigurationBurstType1And3 ::= MidambleConfigurationBurstType2 ::= MidambleConfigurationLCR ::=

1054
CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject CRITICALITY reject TYPE Load-Value TYPE Transmitted-Carrier-Power-Value TYPE Received-Total-Wideband-Power-Value TYPE UL-Timeslot-ISCP-Value TYPE RT-Load-Value TYPE NRT-Load-Information-Value TYPE Rx-Timing-Deviation-Value-LCR

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE PRESENCE

PRESENCE PRESENCE mandatory}| PRESENCE PRESENCE PRESENCE PRESENCE mandatory }

TYPE HS-SICH-Reception-Quality-Measurement-Value TYPE UpPTSInterferenceValue TYPE Rx-Timing-Deviation-Value-768 TYPE Rx-Timing-Deviation-Value-ext TYPE Extended-Round-Trip-Time-Value TYPE TUTRANGANSSMeasurementThresholdInformation

ENUMERATED {v4, v8, v16} ENUMERATED {v3, v6}

ENUMERATED {v2, v4, v6, v8, v10, v12, v14, v16, ...}

MidambleShiftAndBurstType ::= CHOICE { type1 SEQUENCE { midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble MidambleShiftLong, ... }, ... }, type2 SEQUENCE { midambleConfigurationBurstType2 MidambleConfigurationBurstType2, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble MidambleShiftShort, ... },

3GPP

Release 11
...

1055

3GPP TS 25.423 V11.2.0 (2012-06)

}, type3 SEQUENCE { midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, midambleAllocationMode CHOICE { defaultMidamble NULL, ueSpecificMidamble MidambleShiftLong, ... }, ... }, ... } MidambleShiftLong ::= MidambleShiftShort ::= INTEGER (0..15) INTEGER (0..5)

MidambleShiftLCR ::= SEQUENCE { midambleAllocationMode MidambleAllocationMode, midambleShift MidambleShiftLong OPTIONAL, -- The IE shall be present if the Midamble Allocation Mode IE is set to UE specific midamble. midambleConfigurationLCR MidambleConfigurationLCR, iE-Extensions ProtocolExtensionContainer { {MidambleShiftLCR-ExtIEs} } OPTIONAL, ... } MidambleAllocationMode ::= ENUMERATED { defaultMidamble, commonMidamble, uESpecificMidamble, ... } MidambleShiftLCR-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

MidambleShiftAndBurstType768 ::= CHOICE { type1 SEQUENCE { midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, midambleAllocationMode CHOICE { defaultMidamble NULL, commonMidamble NULL, ueSpecificMidamble MidambleShiftLong, ... }, ... }, type2 SEQUENCE { midambleConfigurationBurstType2-768 MidambleConfigurationBurstType2-768,

3GPP

Release 11
midambleAllocationMode defaultMidamble commonMidamble ueSpecificMidamble ... }, ... CHOICE { NULL, NULL, MidambleShiftShort768,

1056

3GPP TS 25.423 V11.2.0 (2012-06)

}, type3 SEQUENCE { midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, midambleAllocationMode CHOICE { defaultMidamble NULL, ueSpecificMidamble MidambleShiftLong, ... }, ... }, ... } MidambleConfigurationBurstType2-768 ::= MidambleShiftShort768 ::= MIMO-ActivationIndicator ::= NULL MIMO-PilotConfiguration, MIMO-N-M-Ratio, ProtocolExtensionContainer { { MIMO-InformationResponse-ExtIEs } } ENUMERATED {v4, v8} INTEGER (0..7)

MIMO-InformationResponse ::= SEQUENCE { mIMO-PilotConfiguration mIMO-N-M-Ratio iE-Extensions ... }

OPTIONAL,

MIMO-InformationResponse-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MIMO-Mode-Indicator ::= ENUMERATED { activate, deactivate } MIMO-N-M-Ratio ::= ENUMERATED {v1-2, v2-3, v3-4, v4-5, v5-6, v6-7, v7-8, v8-9, v9-10, v1-1,...} MIMO-PilotConfiguration ::= CHOICE { primary-and-secondary-CPICH normal-and-diversity-primary-CPICH ... } MIMO-S-CPICH-Channelisation-Code, NULL,

3GPP

Release 11
MIMO-S-CPICH-Channelisation-Code ::= INTEGER (0..255) MinUL-ChannelisationCodeLength v4, v8, v16, v32, v64, v128, v256 } ::= ENUMERATED {

1057

3GPP TS 25.423 V11.2.0 (2012-06)

MinimumReducedE-DPDCH-GainFactor ::= ENUMERATED {m8-15, m11-15, m15-15, m21-15, m30-15, m42-15, m60-15, m84-15,...} ModifyPriorityQueue ::= CHOICE { addPriorityQueue PriorityQueue-InfoItem-to-Add, modifyPriorityQueue PriorityQueue-InfoItem-to-Modify, deletePriorityQueue PriorityQueue-Id, ... } Modulation ::= ENUMERATED { qPSK, eightPSK, ... } MulticellEDCH-Information ::= ProtocolIE-Single-Container { {MulticellEDCH-InformationItem} } TYPE MulticellEDCH-InformationItemIEs PRESENCE mandatory }

MulticellEDCH-InformationItem RNSAP-PROTOCOL-IES ::= { { ID id-MulticellEDCH-Information CRITICALITY ignore }

MulticellEDCH-InformationItemIEs::= SEQUENCE { dL-PowerBalancing-Information DL-PowerBalancing-Information OPTIONAL, minimumReducedE-DPDCH-GainFactor MinimumReducedE-DPDCH-GainFactor OPTIONAL, secondary-UL-Frequency-Activation-State Secondary-UL-Frequency-Activation-State OPTIONAL, f-DPCH-SlotFormat F-DPCH-SlotFormat OPTIONAL, common-DL-ReferencePowerInformation DL-Power OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MulticellEDCH-InformationItemIEs-ExtIEs } } OPTIONAL, ... } MulticellEDCH-InformationItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MulticellEDCH-RL-SpecificInformation ::= ProtocolIE-Single-Container { {MulticellEDCH-RL-SpecificInformationItem} }

3GPP

Release 11
MulticellEDCH-RL-SpecificInformationItem RNSAP-PROTOCOL-IES ::= { { ID id-MulticellEDCH-RL-SpecificInformation CRITICALITY ignore mandatory } }

1058
TYPE MulticellEDCH-RL-SpecificInformationItemIEs

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE

MulticellEDCH-RL-SpecificInformationItemIEs::= SEQUENCE { extendedPropagationDelay ExtendedPropagationDelay OPTIONAL, enhanced-PrimaryCPICH-EcNo Enhanced-PrimaryCPICH-EcNo OPTIONAL, dl-Reference-Power DL-Power OPTIONAL, phase-Reference-Update-Indicator Phase-Reference-Update-Indicator OPTIONAL, additional-e-DCH-DL-Control-Channel-Grant NULL OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MulticellEDCH-RL-SpecificInformationItemIEs-ExtIEs } } OPTIONAL, ... } MulticellEDCH-RL-SpecificInformationItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Multicell-EDCH-Restriction ::= BOOLEAN Multiple-PLMN-List ::= SEQUENCE { pLMN-Identity PLMN-Identity, list-Of-PLMNs List-Of-PLMNs OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Multiple-PLMN-List-ExtIEs} } OPTIONAL, ... } Multiple-PLMN-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MultiplexingPosition ::= ENUMERATED { fixed, flexible } MAChs-ResetIndicator ::= ENUMERATED{ mAChs-NotReset } MultipleFreq-HSPDSCH-InformationList-ResponseTDDLCR ::= SEQUENCE (SIZE (1.. maxHSDPAFrequency-1)) OF MultipleFreq-HSPDSCH-InformationItemResponseTDDLCR --Includes the 2nd through the max number of frequency repetitions MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR hSSCCH-TDD-Specific-InfoList-Response-LCR hARQ-MemoryPartitioning uARFCN ::= SEQUENCE{ HSSCCH-TDD-Specific-InfoList-Response-LCR HARQ-MemoryPartitioning UARFCN, OPTIONAL, OPTIONAL,

3GPP

Release 11

1059

3GPP TS 25.423 V11.2.0 (2012-06)

-- This is the UARFCN for the second and beyond Frequency repetition. iE-Extensions ProtocolExtensionContainer { { MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR-ExtIEs } } OPTIONAL, ... } MultipleFreq-HSPDSCH-InformationItem-ResponseTDDLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MIMO-SFMode-For-HSPDSCHDualStream ::= ENUMERATED { sF1, sF1SF16 } Multi-Carrier-EDCH-Info ::= SEQUENCE{ multicarrier-EDCH-Transport-Bearer-Mode Multicarrier-EDCH-Transport-Bearer-Mode, multi-carrier-EDCH-Information Multi-Carrier-EDCH-Information, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-Info-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-Info-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Multicarrier-EDCH-Transport-Bearer-Mode ::= ENUMERATED { separate-Iur-Transport-Bearer-Mode, shared-Iur-Transport-Bearer-Mode } Multi-Carrier-EDCH-Information ::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-LCR-InformationItem

Multi-Carrier-EDCH-LCR-InformationItem ::=SEQUENCE{ uARFCNforNt UARFCN, sNPL-carrier-group-indicator SNPL-Carrier-Group-Indicator OPTIONAL, pRxdesBase E-PUCH-PRXdesBase, multi-Carrier-EDCH-MACdFlows-Information-TDD Multi-Carrier-EDCH-MACdFlows-Information-TDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-LCR-InformationItem-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-LCR-InformationItem-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

SNPL-Carrier-Group-Indicator ::= INTEGER (1..3) -- for multi-carrier E-DCH operation 1.28Mcps TDD only Multi-Carrier-EDCH-MACdFlows-Information-TDD ::= SEQUENCE (SIZE (1.. maxNrOfEDCHMACdFlows)) OF Multi-Carrier-EDCH-MACdFlows-Specific-Info

3GPP

Release 11

1060

3GPP TS 25.423 V11.2.0 (2012-06)

Multi-Carrier-EDCH-MACdFlows-Specific-Info ::= SEQUENCE { e-DCH-MACdFlow-ID EDCH-MACdFlow-ID, bindingID BindingID, transportLayerAddress TransportLayerAddress, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-MACdFlows-Specific-Info-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-MACdFlows-Specific-Info-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Multi-Carrier-EDCH-Reconfigure ::=SEQUENCE{ continue-setup-change-Of-Multi-Carrier-EDCH Continue-Setup-Change-Multi-Carrier-EDCH, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-Reconfigure-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-Reconfigure-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Continue-Setup-Change-Multi-Carrier-EDCH ::= CHOICE { continue NULL, setup Multi-Carrier-EDCH-Info, change Multi-Carrier-EDCH-Change-Info, ... } Multi-Carrier-EDCH-Change-Info ::=SEQUENCE{ multicarrier-EDCH-Transport-Bearer-Mode Multicarrier-EDCH-Transport-Bearer-Mode OPTIONAL, multi-carrier-EDCH-Information Multi-Carrier-EDCH-Information OPTIONAL, multi-Carrier-EDCH-Information-Removal-List Multi-Carrier-EDCH-Information-Removal-List OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-Change-Info-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-Change-Info-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Multi-Carrier-EDCH-Information-Removal-List ::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs ::=SEQUENCE{ uARFCNforNt UARFCN, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-Information-Removal-Info-ItemIEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

1061

3GPP TS 25.423 V11.2.0 (2012-06)

Multi-Carrier-EDCH-Information-Response ::= SEQUENCE (SIZE (1..maxNrOfULCarriersLCR-1)) OF Multi-Carrier-EDCH-LCR-Information-ResponseItem Multi-Carrier-EDCH-LCR-Information-ResponseItem ::=SEQUENCE{ uARFCNforNt UARFCN, e-DCH-TDD-MACdFlow-Specific-InformationResp E-DCH-TDD-MACdFlow-Specific-InformationResp OPTIONAL, e-AGCH-Specific-Information-Response-LCR-TDD E-AGCH-Specific-InformationRespList-LCR-TDD OPTIONAL, e-HICH-Scheduled-InformationResp-LCR E-HICH-Scheduled-InformationRespList-LCR-TDD OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Multi-Carrier-EDCH-LCR-Information-ResponseItem-ExtIEs} } OPTIONAL, ... } Multi-Carrier-EDCH-LCR-Information-ResponseItem-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

MU-MIMO-InformationLCR ::= SEQUENCE { mU-MIMO-Operation MU-MIMO-Operation, standalone-Midamble-Channel-Information Standalone-Midamble-Channel-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { MU-MIMO-InformationLCR-ExtIEs} } OPTIONAL, ... } MU-MIMO-Operation ::= ENUMERATED { mU-MIMO-Used, mU-MIMO-Not-Used, ... } MU-MIMO-Usage-Indicator ::= ENUMERATED { ul-Only, dl-Only, ul-and-dl } Standalone-Midamble-Channel-Information standalone-Midamble-Configuratnion standalone-MidambleShift timeslotLCR repetitionPeriod offset referenceBeta iE-Extensions ... } ::= SEQUENCE { Standalone-Midamble-Configuratnion, Standalone-MidambleShift, TimeSlotLCR, Standalone-Midamble-RepetitionPeriod, Standalone-Midamble-Offset, ReferenceBeta OPTIONAL, ProtocolExtensionContainer { { Standalone-Midamble-Channel-Information-ExtIEs} } OPTIONAL,

Standalone-Midamble-Configuratnion::= ENUMERATED { v2, v4,

3GPP

Release 11
v6, v8, v10, v12, v14, v16, ...

1062

3GPP TS 25.423 V11.2.0 (2012-06)

Standalone-MidambleShift ::= INTEGER (0..15) Standalone-Midamble-RepetitionPeriod ::= ENUMERATED { v1, v2, v4, v8, v16, v32, v64, ... } Standalone-Midamble-Offset ::= INTEGER (0..63) ReferenceBeta ::= INTEGER (-15..16) Standalone-Midamble-Channel-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MU-MIMO-InformationLCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } MU-MIMO-Indicator ::= SEQUENCE { mU-MIMO-Usage-Indicator standalone-Midamble-Channel-Indicator iE-Extensions ... }

MU-MIMO-Usage-Indicator, Standalone-Midamble-Channel-Indicator, ProtocolExtensionContainer { { MU-MIMO-Indicator-ExtIEs} } OPTIONAL,

MU-MIMO-Indicator-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } -- N NACC-Related-Data ::= SEQUENCE { gERAN-SI-Type GERAN-SI-Type, iE-Extensions ProtocolExtensionContainer { {NACC-Related-Data-ExtIEs} }

OPTIONAL,

3GPP

Release 11
... } NACC-Related-Data-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Nack-Power-Offset ::= INTEGER (0..8,...) -- According to mapping in TS 25.213 [21] subclause 4.2.1 NCC ::= BIT STRING (SIZE (3))

1063

3GPP TS 25.423 V11.2.0 (2012-06)

Neighbouring-UMTS-CellInformation ::= SEQUENCE (SIZE (1..maxNrOfNeighbouringRNCs)) OF ProtocolIE-Single-Container {{ Neighbouring-UMTSCellInformationItemIE }} Neighbouring-UMTS-CellInformation-Ext ::= SEQUENCE (SIZE (1..maxNrOfExtendedNeighbouringRNCs)) OF ProtocolIE-Single-Container {{ Neighbouring-UMTSCellInformationExtensionItemIE }} Neighbouring-UMTS-CellInformationExtensionItemIE RNSAP-PROTOCOL-IES ::= { { ID id-Neighbouring-UMTS-CellInformationExtensionItem CRITICALITY ignore mandatory } } TYPE Neighbouring-UMTS-CellInformationExtensionItem PRESENCE

Neighbouring-UMTS-CellInformationExtensionItem ::= SEQUENCE { rNC-ID RNC-ID, cN-PS-DomainIdentifier CN-PS-DomainIdentifier OPTIONAL, cN-CS-DomainIdentifier CN-CS-DomainIdentifier OPTIONAL, neighbouring-FDD-CellInformation Neighbouring-FDD-CellInformation OPTIONAL, neighbouring-TDD-CellInformation Neighbouring-TDD-CellInformation OPTIONAL, neighbouring-LCR-TDD-CellInformation Neighbouring-LCR-TDD-CellInformation OPTIONAL, extended-RNC-ID Extended-RNC-ID OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Neighbouring-UMTS-CellInformationExtensionItem-ExtIEs} } OPTIONAL, ... } Neighbouring-UMTS-CellInformationExtensionItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Neighbouring-UMTS-CellInformationItemIE RNSAP-PROTOCOL-IES ::= { { ID id-Neighbouring-UMTS-CellInformationItem CRITICALITY ignore } TYPE Neighbouring-UMTS-CellInformationItem PRESENCE mandatory }

Neighbouring-UMTS-CellInformationItem ::= SEQUENCE { rNC-ID RNC-ID, cN-PS-DomainIdentifier CN-PS-DomainIdentifier OPTIONAL, cN-CS-DomainIdentifier CN-CS-DomainIdentifier OPTIONAL, neighbouring-FDD-CellInformation Neighbouring-FDD-CellInformation OPTIONAL, neighbouring-TDD-CellInformation Neighbouring-TDD-CellInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Neighbouring-UMTS-CellInformationItem-ExtIEs} } OPTIONAL,

3GPP

Release 11
} ...

1064

3GPP TS 25.423 V11.2.0 (2012-06)

Neighbouring-UMTS-CellInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-neighbouring-LCR-TDD-CellInformation CRITICALITY ignore EXTENSION PRESENCE optional }| { ID id-Extended-RNC-ID CRITICALITY reject EXTENSION Extended-RNC-ID PRESENCE optional }, ... }

Neighbouring-LCR-TDD-CellInformation

Neighbouring-FDD-CellInformation ::= SEQUENCE ( SIZE (1..maxNrOfFDDNeighboursPerRNC,...)) OF Neighbouring-FDD-CellInformationItem Neighbouring-FDD-CellInformationItem ::= SEQUENCE { c-ID C-ID, uARFCNforNu UARFCN, uARFCNforNd UARFCN, frameOffset FrameOffset OPTIONAL, primaryScramblingCode PrimaryScramblingCode, primaryCPICH-Power PrimaryCPICH-Power OPTIONAL, cellIndividualOffset CellIndividualOffset OPTIONAL, txDiversityIndicator TxDiversityIndicator, sTTD-SupportIndicator STTD-SupportIndicator OPTIONAL, closedLoopMode1-SupportIndicator ClosedLoopMode1-SupportIndicator OPTIONAL, not-used-closedLoopMode2-SupportIndicator NULL OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Neighbouring-FDD-CellInformationItem-ExtIEs} } OPTIONAL, ... } Neighbouring-FDD-CellInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-RestrictionStateIndicator CRITICALITY ignore EXTENSION RestrictionStateIndicator PRESENCE optional }| { ID id-DPC-Mode-Change-SupportIndicator CRITICALITY ignore EXTENSION DPC-Mode-Change-SupportIndicator PRESENCE optional }| { ID id-CoverageIndicator CRITICALITY ignore EXTENSION CoverageIndicator PRESENCE optional }| { ID id-AntennaColocationIndicator CRITICALITY ignore EXTENSION AntennaColocationIndicator PRESENCE optional }| { ID id-HCS-Prio CRITICALITY ignore EXTENSION HCS-Prio PRESENCE optional }| { ID id-CellCapabilityContainer-FDD CRITICALITY ignore EXTENSION CellCapabilityContainer-FDD PRESENCE optional }| { ID id-SNA-Information CRITICALITY ignore EXTENSION SNA-Information PRESENCE optional }| { ID id-FrequencyBandIndicator CRITICALITY ignore EXTENSION FrequencyBandIndicator PRESENCE optional }| { ID id-Max-UE-DTX-Cycle CRITICALITY ignore EXTENSION Max-UE-DTX-Cycle PRESENCE conditional }| -- This IE shall be present if the the fifteenth bit Continuous Packet Connectivity DTX-DRX Support Indicator in the Cell Capability Container FDD IE is set to the value 1. { ID id-Multiple-PLMN-List CRITICALITY ignore EXTENSION Multiple-PLMN-List PRESENCE optional }| { ID id-Secondary-Serving-Cell-List CRITICALITY ignore EXTENSION Secondary-Serving-Cell-List PRESENCE optional }| { ID id-Dual-Band-Secondary-Serving-Cell-List CRITICALITY ignore EXTENSION Secondary-Serving-Cell-List PRESENCE optional }| -- This IE shall be present if the twenty-eighth bit Dual Band Support Indicator in the Cell Capability Container FDD IE is set to the value 1. { ID id-CellCapabilityContainerExtension-FDD CRITICALITY ignore EXTENSION CellCapabilityContainerExtension-FDD PRESENCE optional }|

3GPP

Release 11
{ ID id-CellListValidityIndicator ... } CRITICALITY ignore

1065
EXTENSION CellListValidityIndicator

3GPP TS 25.423 V11.2.0 (2012-06)

PRESENCE optional },

NeighbouringFDDCellMeasurementInformation ::= SEQUENCE { uC-ID UC-ID, uARFCN UARFCN, primaryScramblingCode PrimaryScramblingCode, iE-Extensions ProtocolExtensionContainer { { NeighbouringFDDCellMeasurementInformationItem-ExtIEs} } OPTIONAL, ... } NeighbouringFDDCellMeasurementInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Neighbouring-GSM-CellInformation ::= ProtocolIE-Single-Container {{ Neighbouring-GSM-CellInformationIE }} Neighbouring-GSM-CellInformationIE RNSAP-PROTOCOL-IES ::= { { ID id-Neighbouring-GSM-CellInformation CRITICALITY ignore } TYPE Neighbouring-GSM-CellInformationIEs PRESENCE mandatory }

Neighbouring-GSM-CellInformationIEs ::= SEQUENCE ( SIZE (1..maxNrOfGSMNeighboursPerRNC,...)) OF Neighbouring-GSM-CellInformationItem Neighbouring-GSM-CellInformationItem ::= SEQUENCE { cGI CGI, cellIndividualOffset CellIndividualOffset OPTIONAL, bSIC BSIC, band-Indicator Band-Indicator, bCCH-ARFCN BCCH-ARFCN, iE-Extensions ProtocolExtensionContainer { { Neighbouring-GSM-CellInformationItem-ExtIEs} } OPTIONAL, ... } Neighbouring-GSM-CellInformationItem-ExtIEs { ID id-CoverageIndicator optional } | { ID id-AntennaColocationIndicator | { ID id-HCS-Prio optional } | { ID id-SNA-Information optional } | { ID id-GERAN-Cell-Capability optional } | { ID id-GERAN-Classmark optional } | { ID id-ExtendedGSMCellIndividualOffset ... } RNSAP-PROTOCOL-EXTENSION ::= { CRITICALITY ignore EXTENSION CoverageIndicator CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore EXTENSION AntennaColocationIndicator EXTENSION HCS-Prio EXTENSION SNA-Information EXTENSION GERAN-Cell-Capability EXTENSION GERAN-Classmark EXTENSION ExtendedGSMCellIndividualOffset PRESENCE optional PRESENCE PRESENCE optional }

PRESENCE PRESENCE PRESENCE PRESENCE },

3GPP

Release 11

1066

3GPP TS 25.423 V11.2.0 (2012-06)

Neighbouring-TDD-CellInformation ::= SEQUENCE ( SIZE (1..maxNrOfTDDNeighboursPerRNC,...)) OF Neighbouring-TDD-CellInformationItem Neighbouring-TDD-CellInformationItem ::= SEQUENCE { c-ID C-ID, uARFCNforNt UARFCN, frameOffset FrameOffset OPTIONAL, cellParameterID CellParameterID, syncCase SyncCase, timeSlot TimeSlot OPTIONAL -- This IE shall be present if Sync Case = Case1 -- , sCH-TimeSlot SCH-TimeSlot OPTIONAL -- This IE shall be present if Sync Case = Case2 -- , sCTD-Indicator SCTD-Indicator, cellIndividualOffset CellIndividualOffset OPTIONAL, dPCHConstantValue DPCHConstantValue OPTIONAL, pCCPCH-Power PCCPCH-Power OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Neighbouring-TDD-CellInformationItem-ExtIEs} } OPTIONAL, ... } Neighbouring-TDD-CellInformationItem-ExtIEs { ID id-RestrictionStateIndicator }| { ID id-CoverageIndicator optional }| { ID id-AntennaColocationIndicator { ID id-HCS-Prio optional }| { ID id-CellCapabilityContainer-TDD { ID id-SNA-Information optional }| { ID id-CellCapabilityContainer-TDD768 optional }| { ID id-Multiple-PLMN-List optional }, ... } RNSAP-PROTOCOL-EXTENSION ::= { CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore CRITICALITY ignore EXTENSION RestrictionStateIndicator PRESENCE optional PRESENCE PRESENCE optional }| PRESENCE PRESENCE optional }| PRESENCE PRESENCE PRESENCE

EXTENSION CoverageIndicator EXTENSION AntennaColocationIndicator EXTENSION HCS-Prio EXTENSION CellCapabilityContainer-TDD EXTENSION SNA-Information EXTENSION CellCapabilityContainer-TDD768

CRITICALITY ignore CRITICALITY ignore

EXTENSION Multiple-PLMN-List

NeighbouringTDDCellMeasurementInformation ::= SEQUENCE { uC-ID UC-ID, uARFCN UARFCN, cellParameterID CellParameterID, timeSlot TimeSlot OPTIONAL, midambleShiftAndBurstType MidambleShiftAndBurstType OPTIONAL, iE-Extensions ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformationItem-ExtIEs} } OPTIONAL, ... } NeighbouringTDDCellMeasurementInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1067

3GPP TS 25.423 V11.2.0 (2012-06)

NeighbouringTDDCellMeasurementInformationLCR ::= SEQUENCE { uC-ID UC-ID, uARFCN UARFCN, cellParameterID CellParameterID, timeSlotLCR TimeSlotLCR OPTIONAL, midambleShiftLCR MidambleShiftLCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformationLCRItem-ExtIEs} } OPTIONAL, ... } NeighbouringTDDCellMeasurementInformationLCRItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } NeighbouringTDDCellMeasurementInformation768 ::= SEQUENCE { uC-ID UC-ID, uARFCN UARFCN, cellParameterID CellParameterID, timeSlot TimeSlot OPTIONAL, midambleShiftAndBurstType768 MidambleShiftAndBurstType768 OPTIONAL, iE-Extensions ProtocolExtensionContainer { { NeighbouringTDDCellMeasurementInformationItem768-ExtIEs} } OPTIONAL, ... } NeighbouringTDDCellMeasurementInformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Neighbouring-LCR-TDD-CellInformation ::= SEQUENCE (SIZE (1.. maxNrOfLCRTDDNeighboursPerRNC,...)) OF Neighbouring-LCR-TDD-CellInformationItem Neighbouring-LCR-TDD-CellInformationItem ::= SEQUENCE { c-ID C-ID, uARFCNforNt UARFCN, frameOffset FrameOffset OPTIONAL, cellParameterID CellParameterID, sCTD-Indicator SCTD-Indicator, cellIndividualOffset CellIndividualOffset OPTIONAL, dPCHConstantValue DPCHConstantValue OPTIONAL, pCCPCH-Power PCCPCH-Power OPTIONAL, restrictionStateIndicator RestrictionStateIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { Neighbouring-LCR-TDD-CellInformationItem-ExtIEs} } OPTIONAL, ... } Neighbouring-LCR-TDD-CellInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-CoverageIndicator CRITICALITY ignore EXTENSION CoverageIndicator { ID id-AntennaColocationIndicator CRITICALITY ignore EXTENSION AntennaColocationIndicator { ID id-HCS-Prio CRITICALITY ignore EXTENSION HCS-Prio { ID id-CellCapabilityContainer-TDD-LCR CRITICALITY ignore EXTENSION CellCapabilityContainer-TDD-LCR PRESENCE PRESENCE PRESENCE PRESENCE optional}| optional}| optional}| optional}|

3GPP

Release 11

1068

3GPP TS 25.423 V11.2.0 (2012-06)

{ ID id-SNA-Information CRITICALITY ignore EXTENSION SNA-Information PRESENCE optional}| { ID id-Multiple-PLMN-List CRITICALITY ignore EXTENSION Multiple-PLMN-List PRESENCE optional}| { ID id-CellCapabilityContainerExtension-TDD-LCR CRITICALITY ignore EXTENSION CellCapabilityContainerExtension-TDD-LCR PRESENCE optional}, ... } Neighbouring-E-UTRA-CellInformation ::= SEQUENCE ( SIZE (1..maxNrOfEUTRANeighboursPerRNC,...)) OF Neighbouring-E-UTRA-CellInformationItem Neighbouring-E-UTRA-CellInformationItem eCGI eARFCN-Information iE-Extensions ... } ::= SEQUENCE { ECGI, EARFCN-Information, ProtocolExtensionContainer { { Neighbouring-E-UTRA-CellInformationItem-ExtIEs} } OPTIONAL,

Neighbouring-E-UTRA-CellInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } NonCellSpecificTxDiversity ::= ENUMERATED { txDiversity, ... } NotProvidedCellList ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMSChannelTypeCellList NrOfDLchannelisationcodes NrOfTransportBlocks ::= INTEGER (1..8) ::= INTEGER (0..512)

NRT-Load-Information-Value-IncrDecrThres ::= INTEGER(0..3) NRT-Load-Information-Value ::= INTEGER(0..3) NRTLoadInformationValue ::= SEQUENCE { uplinkNRTLoadInformationValue downlinkNRTLoadInformationValue } N-E-UCCH ::= INTEGER (1..12) N-E-UCCH-LCR ::= INTEGER (1..8) Number-Of-Supported-Carriers one-one-carrier, one-three-carrier, three-three-carrier, one-six-carrier, three-six-carrier, six-six-carrier, ::= ENUMERATED { INTEGER(0..3), INTEGER(0..3)

3GPP

Release 11
..., one-two-carrier-discontiguous, two-two-carrier-discontiguous, one-two-carrier-contiguous, two-two-carrier-contiguous

1069

3GPP TS 25.423 V11.2.0 (2012-06)

NumHS-SCCH-Codes ::= INTEGER (1..maxNrOfHSSCCHCodes) NoOfTargetCellHS-SCCH-Order::= INTEGER (1..30) Non-Serving-RL-Preconfig-Setup ::= SEQUENCE { new-non-serving-RL-selection New-non-serving-RL-setup-selection, iE-Extensions ProtocolExtensionContainer { {Non-Serving-RL-Preconfig-Setup-ExtIEs} } OPTIONAL, ... } Non-Serving-RL-Preconfig-Setup-ExtIEs RNSAP-PROTOCOL-EXTENSION::= { {ID id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup CRITICALITY ignore Setup PRESENCE optional }, ... } Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup New-non-serving-RL-setup-selection ::= CHOICE { new-Serving-RL-in-DRNS NULL, new-Serving-RL-Not-in-DRNS NULL, new-Serving-RL-in-or-Not-in-DRNS NULL, ... } Non-Serving-RL-Preconfig-Info ::= SEQUENCE { new-non-serving-RL-E-DCH-FDD-DL-ControlChannelInformation-A EDCH-FDD-DL-ControlChannelInformation OPTIONAL, new-non-serving-RL-E-DCH-FDD-DL-ControlChannelInformation-B EDCH-FDD-DL-ControlChannelInformation OPTIONAL, new-non-serving-RL-E-DCH-FDD-DL-ControlChannelInformation-C EDCH-FDD-DL-ControlChannelInformation OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Non-Serving-RL-Preconfig-Info-ExtIEs} } OPTIONAL, ... } Non-Serving-RL-Preconfig-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList PRESENCE optional}, ... } CRITICALITY ignore EXTENSION Additional-E-DCH-New-non::= NULL EXTENSION Additional-E-DCH-Non-Serving-RL-Preconfiguration-

Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList ::= SEQUENCE(SIZE(1.. maxNrOfEDCH-1)) OF SEQUENCE { new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-A EDCH-FDD-DL-ControlChannelInformation OPTIONAL, new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-B EDCH-FDD-DL-ControlChannelInformation OPTIONAL, new-non-serving-RL-E-DCH-FDD-DL-Control-Channel-Information-C EDCH-FDD-DL-ControlChannelInformation OPTIONAL,

3GPP

Release 11
iE-Extensions OPTIONAL, ... }

1070

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList-ExtIEs} }

Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList-ExtIEs ... } NeedforIdleInterval ::= ENUMERATED { true, false } -- O

RNSAP-PROTOCOL-EXTENSION ::= {

OnModification ::= SEQUENCE { measurementThreshold MeasurementThreshold, iE-Extensions ProtocolExtensionContainer { {OnModification-ExtIEs} } OPTIONAL, ... } OnModification-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } OnModificationInformation ::= SEQUENCE { informationThreshold InformationThreshold OPTIONAL, iE-Extensions ProtocolExtensionContainer { {OnModificationInformation-ExtIEs} } OPTIONAL, ... } OnModificationInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } OrdinalNumberOfFrequency ::= INTEGER (1..32,...) Out-of-Sychronization-Window ::= ENUMERATED { ms40, ms80, ms160, ms320, ms640, ... } -- P

3GPP

Release 11
PagingCause ::= ENUMERATED { terminating-conversational-call, terminating-streaming-call, terminating-interactive-call, terminating-background-call, terminating-low-priority-signalling, ..., terminating-high-priority-signalling, terminating-cause-unknown } -- See in TS 25.331 [16] PagingRecordType ::= ENUMERATED { imsi-gsm-map, tmsi-gsm-map, p-tmsi-gsm-map, imsi-ds-41, tmsi-ds-41, ... } -- See in TS 25.331 [16] PartialReportingIndicator ::= ENUMERATED { partial-reporting-allowed }

1071

3GPP TS 25.423 V11.2.0 (2012-06)

Pattern-Sequence-Identifier ::= INTEGER (1.. maxNrOfDCHMeasurementOccasionPatternSequence) PayloadCRC-PresenceIndicator ::= ENUMERATED { crc-included, crc-not-included } PCCPCH-Power ::= INTEGER (-150..400,...) -- PCCPCH-power = power * 10 -- If power <= -15 PCCPCH shall be set to -150 -- If power >= 40 PCCPCH shall be set to 400 -- Unit dBm, Range -15dBm .. +40 dBm, Step 0.1dBm PCH-InformationList ::= SEQUENCE (SIZE(0..1)) OF PCH-InformationItem PCH-InformationItem ::= SEQUENCE { transportFormatSet iE-Extensions ... } TransportFormatSet, ProtocolExtensionContainer { { PCH-InformationItem-ExtIEs} } OPTIONAL,

PCH-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
PC-Preamble ::= INTEGER(0..7,...) Periodic ::= SEQUENCE { reportPeriodicity iE-Extensions ... }

1072

3GPP TS 25.423 V11.2.0 (2012-06)

ReportPeriodicity, ProtocolExtensionContainer { {Periodic-ExtIEs} } OPTIONAL,

Periodic-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PeriodicInformation ::= SEQUENCE { informationReportPeriodicity iE-Extensions ... } InformationReportPeriodicity, ProtocolExtensionContainer { {PeriodicInformation-ExtIEs} } OPTIONAL,

PeriodicInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Permanent-NAS-UE-Identity ::= CHOICE { imsi IMSI, ... } Phase-Reference-Update-Indicator ::= ENUMERATED { phase-reference-needs-to-be-changed } PLCCHsequenceNumber ::= INTEGER (0..14) PLMN-Identity ::= OCTET STRING (SIZE(3)) PowerAdjustmentType ::= ENUMERATED { none, common, individual } PowerOffset ::= INTEGER (0..24)

PowerOffsetForSecondaryCPICHforMIMO ::= INTEGER (-6..0) -- Unit dB, Range -10dB .. 5dB, Step +1dB PowerOffsetForSecondaryCPICHforMIMORequestIndicator ::= NULL PRC ::= INTEGER (-2047..2047) --pseudo range correction; scaling factor 0.32 meters

3GPP

Release 11
PRCDeviation ::= ENUMERATED { prcd1, prcd2, prcd5, prcd10, ... } Pre-emptionCapability ::= ENUMERATED { shall-not-trigger-pre-emption, may-trigger-pre-emption } Pre-emptionVulnerability ::= ENUMERATED { not-pre-emptable, pre-emptable } PredictedSFNSFNDeviationLimit ::= INTEGER (1..256) -- Unit chip, Step 1/16 chip, Range 1/16..16 chip PredictedTUTRANGPSDeviationLimit ::= INTEGER (1..256) -- Unit chip, Step 1/16 chip, Range 1/16..16 chip

1073

3GPP TS 25.423 V11.2.0 (2012-06)

PreferredFrequencyLayerInfo ::= SEQUENCE { defaultPreferredFrequency UARFCN, additionalPreferredFrequency AdditionalPreferredFrequency OPTIONAL, iE-Extensions ProtocolExtensionContainer { { PreferredFrequencyLayerInfo-ExtIEs} } OPTIONAL, ... } PreferredFrequencyLayerInfo-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PrimaryCPICH-Power ::= INTEGER (-100..500) -- step 0.1 (Range 10.0..50.0) Unit is dBm PrimaryCPICH-EcNo ::= INTEGER (-30..30)

Primary-CPICH-Usage-For-Channel-Estimation ::= ENUMERATED { primary-CPICH-may-be-used, primary-CPICH-shall-not-be-used } PrimaryCCPCH-RSCP ::= INTEGER (0..91) -- Mapping of Non Negative values according to maping in TS 25.123 [24] PrimaryCCPCH-RSCP-Delta ::= INTEGER (-5..-1,...) -- Mapping of Negative values according to maping in TS 25.123 [24]

3GPP

Release 11
PrimaryScramblingCode ::= INTEGER (0..511)

1074

3GPP TS 25.423 V11.2.0 (2012-06)

PriorityLevel ::= INTEGER (0..15) -- 0 = spare, 1 = highest priority, ...14 = lowest priority and 15 = no priority PriorityQueue-Id ::= INTEGER (0..maxNrOfPrioQueues-1) PriorityQueue-InfoList ::= SEQUENCE (SIZE (1..maxNrOfPrioQueues)) OF PriorityQueue-InfoItem PriorityQueue-InfoItem ::= SEQUENCE { priorityQueue-Id associatedHSDSCH-MACdFlow schedulingPriorityIndicator t1 discardTimer mAC-hsWindowSize mAChsGuaranteedBitRate mACdPDU-Size-Index rLC-Mode iE-Extensions ... } PriorityQueue-Id, HSDSCH-MACdFlow-ID, SchedulingPriorityIndicator, T1, DiscardTimer OPTIONAL, MAC-hsWindowSize, MAChsGuaranteedBitRate OPTIONAL, MACdPDU-Size-IndexList, RLC-Mode, ProtocolExtensionContainer { { PriorityQueue-InfoItem-ExtIEs } }

OPTIONAL,

PriorityQueue-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY reject EXTENSION MAC-PDU-SizeExtended PRESENCE optional}| { ID id-DL-RLC-PDU-Size-Format CRITICALITY ignore EXTENSION DL-RLC-PDU-Size-Format PRESENCE optional}| { ID id-UE-AggregateMaximumBitRate-Enforcement-Indicator CRITICALITY ignore EXTENSION UE-AggregateMaximumBitRate-Enforcement-Indicator PRESENCE optional}, ... } PriorityQueue-InfoList-EnhancedFACH-PCH ::= SEQUENCE (SIZE (1..maxNrOfPrioQueues)) OF PriorityQueue-InfoItem-EnhancedFACH-PCH PriorityQueue-InfoItem-EnhancedFACH-PCH priorityQueue-Id schedulingPriorityIndicator t1 mAC-ehs-Reset-Timer discardTimer mAC-hsWindowSize maximum-MACdPDU-Size iE-Extensions ... } ::= SEQUENCE { PriorityQueue-Id, SchedulingPriorityIndicator, T1, MAC-ehs-Reset-Timer, DiscardTimer OPTIONAL, MAC-hsWindowSize, MAC-PDU-SizeExtended, ProtocolExtensionContainer { { PriorityQueue-InfoItem-EnhancedFACH-PCH-ExtIEs } }

OPTIONAL,

PriorityQueue-InfoItem-EnhancedFACH-PCH-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PriorityQueue-InfoList-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfPrioQueues)) OF ModifyPriorityQueue

3GPP

Release 11

1075

3GPP TS 25.423 V11.2.0 (2012-06)

PriorityQueue-InfoItem-to-Add ::= SEQUENCE { priorityQueue-Id PriorityQueue-Id, associatedHSDSCH-MACdFlow HSDSCH-MACdFlow-ID, schedulingPriorityIndicator SchedulingPriorityIndicator, t1 T1, discardTimer DiscardTimer OPTIONAL, mAC-hsWindowSize MAC-hsWindowSize, mAChsGuaranteedBitRate MAChsGuaranteedBitRate OPTIONAL, mACdPDU-Size-Index MACdPDU-Size-IndexList, rLC-Mode RLC-Mode, iE-Extensions ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Add-ExtIEs } } ... } PriorityQueue-InfoItem-to-Add-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY reject EXTENSION MAC-PDU-SizeExtended { ID id-DL-RLC-PDU-Size-Format CRITICALITY ignore EXTENSION DL-RLC-PDU-Size-Format ... }

OPTIONAL,

PRESENCE optional}| PRESENCE optional},

PriorityQueue-InfoItem-to-Modify ::= SEQUENCE { priorityQueue-Id PriorityQueue-Id, schedulingPriorityIndicator SchedulingPriorityIndicator OPTIONAL, t1 T1 OPTIONAL, discardTimer DiscardTimer OPTIONAL, mAC-hsWindowSize MAC-hsWindowSize OPTIONAL, mAChsGuaranteedBitRate MAChsGuaranteedBitRate OPTIONAL, mACdPDU-Size-Index-to-Modify MACdPDU-Size-IndexList-to-Modify OPTIONAL, iE-Extensions ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Modify-ExtIEs } } ... } PriorityQueue-InfoItem-to-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-MaximumMACdPDU-SizeExtended CRITICALITY reject EXTENSION { ID id-DL-RLC-PDU-Size-Format CRITICALITY ignore EXTENSION ... } MAC-PDU-SizeExtended DL-RLC-PDU-Size-Format

OPTIONAL,

PRESENCE optional} | PRESENCE optional},

PriorityQueue-InfoList-to-Modify-Unsynchronised ::= SEQUENCE (SIZE (0..maxNrOfPrioQueues)) OF PriorityQueue-InfoItem-to-Modify-Unsynchronised PriorityQueue-InfoItem-to-Modify-Unsynchronised ::= SEQUENCE { priorityQueueId PriorityQueue-Id, schedulingPriorityIndicator SchedulingPriorityIndicator OPTIONAL, discardTimer DiscardTimer OPTIONAL, mAChsGuaranteedBitRate MAChsGuaranteedBitRate OPTIONAL, iE-Extensions ProtocolExtensionContainer { { PriorityQueue-InfoItem-to-Modify-Unsynchronised-ExtIEs} } ... } PriorityQueue-InfoItem-to-Modify-Unsynchronised-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

OPTIONAL,

3GPP

Release 11
} PropagationDelay ::= INTEGER (0..255)

1076

3GPP TS 25.423 V11.2.0 (2012-06)

ProvidedInformation ::= SEQUENCE { mBMSChannelTypeInfo MBMSChannelTypeInfo OPTIONAL, mBMSPreferredFreqLayerInfo MBMSPreferredFreqLayerInfo OPTIONAL, iE-Extensions ProtocolExtensionContainer { { ProvideInformation-ExtIEs} } OPTIONAL, ... } ProvideInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UpPCH-InformationList-LCRTDD CRITICALITY ignore EXTENSION UpPCH-InformationList-LCRTDD PRESENCE optional}| -- Applicable to 1.28Mcps TDD only { ID id-ANRReportIndication CRITICALITY ignore EXTENSION ANRReportIndication PRESENCE optional}, ... } UpPCH-InformationList-LCRTDD ::= SEQUENCE (SIZE (0.. maxFrequencyinCell)) OF ProtocolIE-Single-Container {{ UpPCH-InformationItemIE-LCRTDD }} UpPCH-InformationItemIE-LCRTDD RNSAP-PROTOCOL-IES ::= { { ID id-UpPCH-InformationItem-LCRTDD CRITICALITY ignore ... } TYPE UpPCH-InformationItem-LCRTDD PRESENCE mandatory},

UpPCH-InformationItem-LCRTDD ::= SEQUENCE { uARFCNforNt UARFCN OPTIONAL, uPPCHPositionLCR UPPCHPositionLCR OPTIONAL, iE-Extensions ProtocolExtensionContainer { { UpPCH-InformationItem-LCRTDD-ExtIEs} } ... } UpPCH-InformationItem-LCRTDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } PunctureLimit ::= INTEGER (0..15) -- 0: 40%; 1: 44%; ... 14: 96%; 15: 100 -- 0 is not applicable for E-DPCH PTMCellList ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMSChannelTypeCellList PTPCellList ::= SEQUENCE (SIZE (1..maxNrOfCells)) OF MBMSChannelTypeCellList -- Q QE-Selector ::= ENUMERATED { selected, non-selected

OPTIONAL,

3GPP

Release 11
} Process-Memory-Size ::= ENUMERATED {

1077
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,...}

3GPP TS 25.423 V11.2.0 (2012-06)

-- R RABased ::= SEQUENCE { raiList iE-Extensions ... } RAI-List, ProtocolExtensionContainer { {RABased-ExtIEs} } OPTIONAL,

RABased-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RAI-List RAI ::= SEQUENCE (SIZE (1..maxNrOfRAIs)) OF

ReportInterval

::= ENUMERATED { ms250, ms500, ms1000, ms2000, ms3000, ms4000, ms6000, ms12000, ms16000, ms20000, ms24000, ms32000, ms64000, ... } ::= ENUMERATED { n1, n2, n4, n8, n16, n32, n64, infinity, ... }

ReportAmount

3GPP

Release 11
RAC RAI ::= SEQUENCE { pLMN-Identity lAC rAC } ::= OCTET STRING (SIZE(1)) PLMN-Identity, LAC, RAC ::= BIT STRING ::= BIT STRING

1078

3GPP TS 25.423 V11.2.0 (2012-06)

RANAP-EnhancedRelocationInformationRequest RANAP-EnhancedRelocationInformationResponse RANAP-RelocationInformation ::= BIT STRING

Range-Correction-Rate ::= INTEGER (-127..127) -- scaling factor 0.032 m/s RateMatchingAttribute RB-Identity ::= INTEGER (1..maxRateMatching) ::= INTEGER (0..31)

RB-Info ::= SEQUENCE (SIZE(1..maxNoOfRB)) OF RB-Identity Received-Total-Wideband-Power-Value ::= Received-total-wide-band-power Received-Total-Wideband-Power-Value-IncrDecrThres ::= INTEGER(0..620) -- Unit dB Step 0.1dB -- e.g. value 100 means 10dB Reference-E-TFCI-Information ::= SEQUENCE (SIZE (1..maxNrOfRefETFCIs)) OF Reference-E-TFCI-Information-Item Reference-E-TFCI-Information-Item ::= SEQUENCE { reference-E-TFCI E-TFCI, -- The following IE shall be ignored if id-Ext-Reference-E-TFCI-PO is present in Reference-E-TFCI-Information-Item-ExtIEs reference-E-TFCI-PO Reference-E-TFCI-PO, iE-Extensions ProtocolExtensionContainer { { Reference-E-TFCI-Information-Item-ExtIEs} } OPTIONAL, ... } Reference-E-TFCI-Information-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { -- The following IE shall be present if the ref E-TFCI power offset to be signalled exceeds maxNrOfRefETFCI-PO-QUANTSTEPs { ID id-Ext-Reference-E-TFCI-PO CRITICALITY reject EXTENSION Ext-Reference-E-TFCI-PO PRESENCE optional}, ... } Reference-E-TFCI-PO ::= INTEGER (0.. maxNrOfRefETFCI-PO-QUANTSTEPs) RefTFCNumber ::= INTEGER (0..15) Released-CN-Domain ::= CHOICE { pSDomain NULL,

3GPP

Release 11
cSDomain pS-CSDomain ... NULL, NULL,

1079

3GPP TS 25.423 V11.2.0 (2012-06)

RepetitionLength

::= INTEGER (1..63)

RepetitionPeriod ::= ENUMERATED { v1, v2, v4, v8, v16, v32, v64 } RepetitionNumber0 ::= INTEGER (0..255) RepetitionNumber1 ::= INTEGER (1..256) ReportCharacteristics ::= CHOICE { onDemand NULL, periodic Periodic, eventA EventA, eventB EventB, eventC EventC, eventD EventD, eventE EventE, eventF EventF, ..., extension-ReportCharacteristics }

Extension-ReportCharacteristics

Extension-ReportCharacteristics ::= ProtocolIE-Single-Container {{ Extension-ReportCharacteristicsIE }} Extension-ReportCharacteristicsIE RNSAP-PROTOCOL-IES ::= { { ID id-OnModification CRITICALITY reject TYPE OnModification { ID id-EventH CRITICALITY reject TYPE EventH } PRESENCE mandatory }| PRESENCE mandatory }

ReportPeriodicity ::= CHOICE { ten-msec INTEGER (1..6000,...), -- The Report Periodicity gives the reporting periodicity in number of 10 ms periods. -- E.g. value 6000 means 60000ms (i.e. 1min) -- Unit ms, Step 10ms min INTEGER (1..60,...), -- Unit min, Step 1min ... }

3GPP

Release 11
RequestedDataValue ::= SEQUENCE { gA-AccessPointPositionwithAltitude iPDLParameters dGPSCorrections gPS-NavigationModel-and-TimeRecovery gPS-Ionospheric-Model gPS-UTC-Model gPS-Almanac gPS-RealTime-Integrity gPS-RX-POS sFNSFN-GA-AccessPointPosition iE-Extensions ... }

1080
GA-AccessPointPositionwithOptionalAltitude OPTIONAL, IPDLParameters OPTIONAL, DGPSCorrections OPTIONAL, GPS-NavigationModel-and-TimeRecovery OPTIONAL, GPS-Ionospheric-Model OPTIONAL, GPS-UTC-Model OPTIONAL, GPS-Almanac OPTIONAL, GPS-RealTime-Integrity OPTIONAL, GPS-RX-POS OPTIONAL, GA-AccessPointPositionwithOptionalAltitude OPTIONAL, ProtocolExtensionContainer { { RequestedDataValue-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RequestedDataValue-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Cell-Capacity-Class-Value CRITICALITY { ID id-NACC-Related-Data CRITICALITY { ID id-MBMS-Bearer-Service-Full-Address CRITICALITY { ID id-Inter-Frequency-Cell-Information CRITICALITY { ID id-GANSS-Common-Data CRITICALITY { ID id-GANSS-Generic-Data CRITICALITY { ID id-Counting-Information CRITICALITY { ID id-Transmission-Mode-Information CRITICALITY { ID id-MBMS-Neighbouring-Cell-Information CRITICALITY { ID id-RLC-Sequence-Number CRITICALITY { ID id-ANR-Cell-Information CRITICALITY ... } RequestedDataValueInformation ::= CHOICE { informationAvailable InformationAvailable, informationNotAvailable InformationNotAvailable } RestrictionStateIndicator ::= ENUMERATED { cellNotResevedForOperatorUse, cellResevedForOperatorUse, ... } RL-ID RL-Set-ID ::= INTEGER (0..31) ::= INTEGER (0..31)

ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore ignore

EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION

Cell-Capacity-Class-Value NACC-Related-Data MBMS-Bearer-Service-Full-Address Inter-Frequency-Cell-Information GANSS-Common-Data GANSS-Generic-Data Counting-Information Transmission-Mode-Information MBMS-Neighbouring-Cell-Information RLC-Sequence-Number ANR-Cell-Information

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE

optional optional optional optional optional optional optional optional optional optional optional

}| }| }| }| }| }| }| }| }| }| },

RL-Specific-DCH-Info ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF RL-Specific-DCH-Info-Item RL-Specific-DCH-Info-Item ::= SEQUENCE { dCH-id DCH-ID, bindingID BindingID OPTIONAL,

3GPP

Release 11

1081

3GPP TS 25.423 V11.2.0 (2012-06)

-- Shall be ignored if bearer establishment with ALCAP. transportLayerAddress TransportLayerAddress OPTIONAL, -- Shall be ignored if bearer establishment with ALCAP. iE-Extensions ProtocolExtensionContainer { { RL-Specific-DCH-Info-Item-ExtIEs} } ...

OPTIONAL,

RL-Specific-DCH-Info-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TransportBearerNotRequestedIndicator CRITICALITY ignore }, -- FDD only ... }

EXTENSION TransportBearerNotRequestedIndicator

PRESENCE optional

RL-Specific-EDCH-Information ::= SEQUENCE { rL-Specific-EDCH-Info RL-Specific-EDCH-Info, e-AGCH-PowerOffset E-AGCH-PowerOffset OPTIONAL, e-RGCH-PowerOffset E-RGCH-PowerOffset OPTIONAL, e-HICH-PowerOffset E-HICH-PowerOffset OPTIONAL, iE-Extensions ProtocolExtensionContainer { { RL-Specific-EDCH-Information-Item-ExtIEs} } OPTIONAL, ... } RL-Specific-EDCH-Information-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } RL-Specific-EDCH-Info ::= SEQUENCE (SIZE (1..maxNrOfEDCHMACdFlows)) OF RL-Specific-EDCH-InfoItem RL-Specific-EDCH-InfoItem ::= SEQUENCE { eDCH-MACdFlow-ID EDCH-MACdFlow-ID, bindingID BindingID OPTIONAL, -- Shall be ignored if bearer establishment with ALCAP. transportLayerAddress TransportLayerAddress OPTIONAL, -- Shall be ignored if bearer establishment with ALCAP. iE-Extensions ProtocolExtensionContainer { { RL-Specific-EDCH-Info-Item-ExtIEs} } OPTIONAL, ... } RL-Specific-EDCH-Info-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TransportBearerNotRequestedIndicator CRITICALITY ignore }, -- FDD only ... } RLC-Mode ::= ENUMERATED { rLC-AM, rLC-UM, ... } EXTENSION TransportBearerNotRequestedIndicator PRESENCE optional

3GPP

Release 11
DL-RLC-PDU-Size-Format ::= ENUMERATED { fixed-RLC-PDU-Size, flexible-RLC-PDU-Size, ... } RLC-Sequence-Number RNC-ID ::= INTEGER (0..127) ::= INTEGER (0..4095)

1082

3GPP TS 25.423 V11.2.0 (2012-06)

RNTI-Allocation-Indicator ::= ENUMERATED { true } Round-Trip-Time-IncrDecrThres ::= INTEGER(0..32766) Round-Trip-Time-Value ::= INTEGER(0..32767) -- According to mapping in TS 25.133 [23] RSCP-Value ::= INTEGER (0..127) -- According to mapping in TS 25.123 [24] RSCP-Value-IncrDecrThres ::= INTEGER (0..126) Received-total-wide-band-power -- According to mapping in TS 25.133 [23] ::= INTEGER (0..621)

RT-Load-Value-IncrDecrThres ::= INTEGER(0..100) RT-Load-Value ::= INTEGER(0..100) RTLoadValue ::= SEQUENCE { uplinkRTLoadValue downlinkRTLoadValue } INTEGER(0..100), INTEGER(0..100)

RxTimingDeviationForTA ::= INTEGER (0..127) -- As specified in TS 25.435 [5], ch. 6.2.7.6 -- For 1.28Mcps TDD this IE must be set to 0. RxTimingDeviationForTAext ::= INTEGER (0..511) -- As specified in TS 25.435 [5] [3.84 Mcps TDD only] RxTimingDeviationForTA768 -- As specified in TS 25.435 [5] ::= INTEGER (0.. 1023)

Rx-Timing-Deviation-Value ::= INTEGER (0..8191) --According to mapping in TS 25.123 [24][3.84Mcps TDD only] Rx-Timing-Deviation-Value-ext ::= INTEGER (0..32767) --According to mapping in TS 25.123 [24][3.84Mcps TDD only]

3GPP

Release 11
Rx-Timing-Deviation-Value-LCR ::= INTEGER (0..511) --According to mapping in TS 25.123 [24][1.28Mcps TDD only] Rx-Timing-Deviation-Value-768 ::= INTEGER (0..65535) --According to mapping in TS 25.123 [24][7.68Mcps TDD only] RefBeta ::= INTEGER (-15..16) -- S SAC SAI ::= SEQUENCE { pLMN-Identity lAC sAC iE-Extensions } ::= OCTET STRING (SIZE (2))

1083

3GPP TS 25.423 V11.2.0 (2012-06)

PLMN-Identity, LAC, SAC, ProtocolExtensionContainer { {SAI-ExtIEs} } OPTIONAL

SAI-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SAT-ID ::= INTEGER (0..63) SCH-TimeSlot ::= INTEGER (0..6)

ScaledAdjustmentRatio ::= INTEGER(0..100) -- AdjustmentRatio = ScaledAdjustmentRatio / 100 SchedulingInformation included, not-included } ::= ENUMERATED {

SDPCCH-PowerOffsetInformation ::= INTEGER (0..6,...) SecondaryServingCells ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF SecondaryServingCellsItem SecondaryServingCellsItem ::= SEQUENCE { secondaryC-ID C-ID, numSecondaryHS-SCCH-Codes NumHS-SCCH-Codes OPTIONAL, sixtyfourQAM-UsageAllowedIndicator SixtyfourQAM-UsageAllowedIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SecondaryServingCellsItem-ExtIEs} } ... } SecondaryServingCellsItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-ActivationIndicator CRITICALITY ignore EXTENSION MIMO-ActivationIndicator {ID id-EDCH-Indicator CRITICALITY ignore EXTENSION NULL PRESENCE optional}| PRESENCE optional}|

OPTIONAL,

3GPP

Release 11
{ID id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator optional}, ... } Secondary-CCPCH-Info-TDD::= SEQUENCE { dl-TFCS tFCI-Coding secondary-CCPCH-TDD-InformationList fACH-InformationList pCH-InformationList iE-Extensions ... }

1084
CRITICALITY ignore

3GPP TS 25.423 V11.2.0 (2012-06)

EXTENSION PowerOffsetForSecondaryCPICHforMIMORequestIndicator PRESENCE

TFCS, TFCI-Coding, Secondary-CCPCH-TDD-InformationList, FACH-InformationList, PCH-InformationList, ProtocolExtensionContainer { { Secondary-CCPCH-Info-TDD-ExtIEs} } OPTIONAL,

Secondary-CCPCH-Info-TDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CPICH-Information ::= SEQUENCE { dl-ScramblingCode fDD-DL-ChannelisationCodeNumber iE-Extensions ... } DL-ScramblingCode, FDD-DL-ChannelisationCodeNumber, ProtocolExtensionContainer { { Secondary-CPICH-Information-ExtIEs} } OPTIONAL,

Secondary-CPICH-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CPICH-Information-Change ::= CHOICE { new-secondary-CPICH Secondary-CPICH-Information, secondary-CPICH-shall-not-be-used NULL, ... } Secondary-LCR-CCPCH-Info-TDD::= SEQUENCE { dl-TFCS tFCI-Coding secondary-LCR-CCPCH-TDD-InformationList fACH-InformationList pCH-InformationList iE-Extensions ... } TFCS, TFCI-Coding, Secondary-LCR-CCPCH-TDD-InformationList, FACH-InformationList, PCH-InformationList, ProtocolExtensionContainer { { Secondary-LCR-CCPCH-Info-TDD-ExtIEs} } OPTIONAL,

Secondary-LCR-CCPCH-Info-TDD-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11
Secondary-CCPCH-Info-TDD768::= SEQUENCE { dl-TFCS tFCI-Coding secondary-CCPCH-TDD-InformationList768 fACH-InformationList pCH-InformationList iE-Extensions ... }

1085

3GPP TS 25.423 V11.2.0 (2012-06)

TFCS, TFCI-Coding, Secondary-CCPCH-TDD-InformationList768, FACH-InformationList, PCH-InformationList, ProtocolExtensionContainer { { Secondary-CCPCH-Info-TDD768-ExtIEs} } OPTIONAL,

Secondary-CCPCH-Info-TDD768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CCPCH-TDD-InformationList ::= SEQUENCE (SIZE(0.. maxNrOfSCCPCHs)) OF Secondary-CCPCH-TDD-InformationItem Secondary-CCPCH-TDD-InformationItem ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, tFCI-Presence TFCI-Presence, secondary-CCPCH-TDD-Code-Information Secondary-CCPCH-TDD-Code-Information, tDD-PhysicalChannelOffset TDD-PhysicalChannelOffset, repetitionLength RepetitionLength, repetitionPeriod RepetitionPeriod, iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-TDD-InformationItem-ExtIEs} } OPTIONAL, ... } Secondary-CCPCH-TDD-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-LCR-CCPCH-TDD-InformationList ::= SEQUENCE (SIZE(0.. maxNrOfSCCPCHs)) OF Secondary-LCR-CCPCH-TDD-InformationItem Secondary-LCR-CCPCH-TDD-InformationItem ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, tFCI-Presence TFCI-Presence, secondary-LCR-CCPCH-TDD-Code-Information Secondary-LCR-CCPCH-TDD-Code-Information, tDD-PhysicalChannelOffset TDD-PhysicalChannelOffset, repetitionLength RepetitionLength, repetitionPeriod RepetitionPeriod, iE-Extensions ProtocolExtensionContainer { { Secondary-LCR-CCPCH-TDD-InformationItem-ExtIEs} } OPTIONAL, ... } Secondary-LCR-CCPCH-TDD-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CCPCH-TDD-InformationList768 ::= SEQUENCE (SIZE(0.. maxNrOfSCCPCHs768)) OF Secondary-CCPCH-TDD-InformationItem768

3GPP

Release 11

1086

3GPP TS 25.423 V11.2.0 (2012-06)

Secondary-CCPCH-TDD-InformationItem768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, tFCI-Presence TFCI-Presence, secondary-CCPCH-TDD-Code-Information768 Secondary-CCPCH-TDD-Code-Information768, tDD-PhysicalChannelOffset TDD-PhysicalChannelOffset, repetitionLength RepetitionLength, repetitionPeriod RepetitionPeriod, iE-Extensions ProtocolExtensionContainer { { Secondary-CCPCH-TDD-InformationItem768-ExtIEs} } OPTIONAL, ... } Secondary-CCPCH-TDD-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CCPCH-TDD-Code-Information ::= SEQUENCE ( SIZE (1..maxNrOfSCCPCHs)) OF Secondary-CCPCH-TDD-Code-InformationItem Secondary-CCPCH-TDD-Code-InformationItem ::= SEQUENCE { tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { {Secondary-CCPCH-TDD-Code-InformationItem-ExtIEs} } OPTIONAL, ... } Secondary-CCPCH-TDD-Code-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-LCR-CCPCH-TDD-Code-Information ::= SEQUENCE ( SIZE (1..maxNrOfSCCPCHs)) OF Secondary-LCR-CCPCH-TDD-Code-InformationItem Secondary-LCR-CCPCH-TDD-Code-InformationItem ::= SEQUENCE { tDD-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, s-CCPCH-TimeSlotFormat-LCR TDD-DL-DPCH-TimeSlotFormat-LCR, iE-Extensions ProtocolExtensionContainer { {Secondary-LCR-CCPCH-TDD-Code-InformationItem-ExtIEs} } OPTIONAL, ... } Secondary-LCR-CCPCH-TDD-Code-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Secondary-CCPCH-TDD-Code-Information768 ::= SEQUENCE ( SIZE (1..maxNrOfSCCPCHs768)) OF Secondary-CCPCH-TDD-Code-InformationItem768 Secondary-CCPCH-TDD-Code-InformationItem768 ::= SEQUENCE { tDD-ChannelisationCode768 TDD-ChannelisationCode768, iE-Extensions ProtocolExtensionContainer { {Secondary-CCPCH-TDD-Code-InformationItem768-ExtIEs} } OPTIONAL, ... } Secondary-CCPCH-TDD-Code-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

1087

3GPP TS 25.423 V11.2.0 (2012-06)

Secondary-Serving-Cell-List ::= SEQUENCE { possible-Secondary-Serving-Cell-List Possible-Secondary-Serving-Cell-List, iE-Extensions ProtocolExtensionContainer { { Secondary-Serving-Cell-List-ExtIEs } } ... } Secondary-Serving-Cell-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Multicell-EDCH-Restriction CRITICALITY ignore ... } EXTENSION Multicell-EDCH-Restriction

OPTIONAL,

PRESENCE optional },

--maxNrOfHSDSCH-1 represents the maximum number of possible secondary serving cells for a Multi Cell/Dual-Band capable cell when it applies to the range of Possible-Secondary-Serving-Cell-List. Possible-Secondary-Serving-Cell-List ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH-1)) OF Possible-Secondary-Serving-Cell Possible-Secondary-Serving-Cell ::= SEQUENCE { c-ID C-ID, iE-Extensions ProtocolExtensionContainer { { Possible-Secondary-Serving-Cell-ExtIEs } } ... } Possible-Secondary-Serving-Cell-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SecondInterleavingMode ::= ENUMERATED { frame-related, timeslot-related, ... } Secondary-UL-Frequency-Activation-State ::= ENUMERATED { activated, deactivated, ... } Seed ::= INTEGER (0..63) Service-ID ::= OCTET STRING (SIZE (3))

OPTIONAL,

SetsOfHS-SCCH-Codes ::= SEQUENCE (SIZE (1..maxNrOfHSDSCH)) OF SetsOfHS-SCCH-CodesItem SetsOfHS-SCCH-CodesItem ::= SEQUENCE { hS-SCCH-PreconfiguredCodes HS-SCCH-PreconfiguredCodes, hSDSCH-RNTI HSDSCH-RNTI,

3GPP

Release 11

1088

3GPP TS 25.423 V11.2.0 (2012-06)

hSPDSCH-and-HSSCCH-ScramblingCode DL-ScramblingCode, sixtyfourQAM-DL-SupportIndicator SixtyfourQAM-DL-SupportIndicator OPTIONAL, sixtyfourQAM-DL-UsageIndicator SixtyfourQAM-DL-UsageIndicator OPTIONAL, hSDSCH-TBSizeTableIndicator HSDSCH-TBSizeTableIndicator OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SetsOfHS-SCCH-CodesItem-ExtIEs} } OPTIONAL, ... } SetsOfHS-SCCH-CodesItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-MIMO-InformationResponse CRITICALITY ignore EXTENSION MIMO-InformationResponse {ID id-power-offset-for-S-CPICH-for-MIMO CRITICALITY ignore EXTENSION PowerOffsetForSecondaryCPICHforMIMO {ID id-Measurement-Power-Offset CRITICALITY ignore EXTENSION Measurement-Power-Offset ... } Setup-Or-ConfigurationChange-Or-Removal-Of-EDCH-On-secondary-UL-Frequency::= CHOICE { setup Additional-EDCH-Setup-Info, configurationChange Additional-EDCH-Cell-Information-ConfigurationChange-List, removal Additional-EDCH-Cell-Information-Removal-List, ... } Setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD ::= CHOICE { setup UL-CLTD-Information, configurationChange UL-CLTD-Information-To-Modify, removal UL-CLTD-Information-Removal, ... } Setup-Or-ConfigurationChange-Or-Removal-Of-FTPICH-Information ::= CHOICE { setup FTPICH-Information, configurationChange FTPICH-Information-To-Modify, removal FTPICH-Information-Removal, ... } SFN ::= INTEGER (0..4095) SFNSFN-FDD ::= INTEGER(0..614399) SFNSFN-TDD ::= INTEGER(0..40961) SFNSFN-TDD768 ::= INTEGER(0..81923) GA-AccessPointPositionwithOptionalAltitude ::= SEQUENCE { geographicalCoordinate GeographicalCoordinate, altitudeAndDirection GA-AltitudeAndDirection OPTIONAL, iE-Extensions ProtocolExtensionContainer { { GA-AccessPointPositionwithOptionalAltitude-ExtIEs} } OPTIONAL, ... } PRESENCE optional}| PRESENCE optional}| PRESENCE optional},

3GPP

Release 11

1089

3GPP TS 25.423 V11.2.0 (2012-06)

GA-AccessPointPositionwithOptionalAltitude-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SFNSFNChangeLimit ::= INTEGER (1..256) -- Unit chip, Step 1/16 chip, Range 1/16..16 chip SFNSFNDriftRate ::= INTEGER (-100..100) -- Unit chip/s, Step 1/256 chip/s, Range -100/256..+100/256 chip/s SFNSFNDriftRateQuality ::= INTEGER (0..100) -- Unit chip/s, Step 1/256 chip/s, Range 0..100/256 chip/s SFNSFNMeasurementThresholdInformation::= SEQUENCE { sFNSFNChangeLimit SFNSFNChangeLimit OPTIONAL, predictedSFNSFNDeviationLimit PredictedSFNSFNDeviationLimit OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SFNSFNMeasurementThresholdInformation-ExtIEs} } ... } SFNSFNMeasurementThresholdInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SFNSFNMeasurementValueInformation ::= SEQUENCE { successfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformation SEQUENCE (SIZE(1..maxNrOfMeasNCell)) OF SEQUENCE { uC-ID UC-ID, sFNSFNValue SFNSFNValue, sFNSFNQuality SFNSFNQuality OPTIONAL, sFNSFNDriftRate SFNSFNDriftRate, sFNSFNDriftRateQuality SFNSFNDriftRateQuality OPTIONAL, sFNSFNTimeStampInformation SFNSFNTimeStampInformation, iE-Extensions ProtocolExtensionContainer { { SuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs} } OPTIONAL, ... }, unsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformation SEQUENCE (SIZE(0..maxNrOfMeasNCell-1)) OF SEQUENCE { uC-ID UC-ID, iE-Extensions ProtocolExtensionContainer { { UnsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItemExtIEs} } OPTIONAL, ... }, iE-Extensions ProtocolExtensionContainer { { SFNSFNMeasurementValueInformationItem-ExtIEs} } OPTIONAL, ... } SFNSFNMeasurementValueInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

OPTIONAL,

3GPP

Release 11
}

1090

3GPP TS 25.423 V11.2.0 (2012-06)

SuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UnsuccessfullNeighbouringCellSFNSFNObservedTimeDifferenceMeasurementInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SFNSFNQuality ::= INTEGER (0..255) -- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip SFNSFNTimeStampInformation ::= CHOICE { sFNSFNTimeStamp-FDD SFN, sFNSFNTimeStamp-TDD SFNSFNTimeStamp-TDD, ... } SFNSFNTimeStamp-TDD::= SEQUENCE { sFN SFN, timeSlot TimeSlot, iE-Extensions ... }

ProtocolExtensionContainer { { SFNSFNTimeStamp-ExtIEs}} OPTIONAL,

SFNSFNTimeStamp-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SFNSFNValue ::= CHOICE { sFNSFN-FDD SFNSFN-FDD, sFNSFN-TDD SFNSFN-TDD, -- LCR & HCR TDD ..., sFNSFN-TDD768 SFNSFN-TDD768 } SID ::= INTEGER (0..maxNrOfPDUIndexes-1) Single-Stream-MIMO-ActivationIndicator ::= NULL

Single-Stream-MIMO-Mode-Indicator ::= ENUMERATED { activate, deactivate }

3GPP

Release 11
SIR-Error-Value ::= INTEGER (0..125) ::= INTEGER (0..124)

1091

3GPP TS 25.423 V11.2.0 (2012-06)

SIR-Error-Value-IncrDecrThres

SIR-Value ::= INTEGER (0..63) -- According to mapping in TS 25.215 [11]/TS 25.225 [14] SIR-Value-IncrDecrThres ::= INTEGER (0..62) SixteenQAM-UL-Operation-Indicator ::= ENUMERATED { activate, deactivate } SixtyfourQAM-UsageAllowedIndicator ::= ENUMERATED { allowed, not-allowed } SixtyfourQAM-DL-SupportIndicator ::= ENUMERATED { sixtyfourQAM-DL-supported, sixtyfourQAM-DL-not-supported } SixtyfourQAM-DL-UsageIndicator ::= ENUMERATED { sixtyfourQAM-DL-used, sixtyfourQAM-DL-not-used } SignatureSequenceGroupIndex ::= INTEGER (0..19) SNA-Information ::= SEQUENCE { pLMN-Identity PLMN-Identity, listOfSNAs ListOfSNAs OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SNA-Information-ExtIEs} } OPTIONAL, ... } SNA-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ListOfSNAs ::= SEQUENCE (SIZE (1.. maxNrOfSNAs)) OF SNACode SNACode ::= INTEGER (0..65535) SourceID ::= SAI

3GPP

Release 11
SpecialBurstScheduling ::= INTEGER (1..256) SpeechVersion::= BIT STRING (SIZE (4)) S-RNTI -- From 0 to 2^20-1 S-RNTI-Group sRNTI sRNTI-BitMaskIndex b1, b2, b3, b4, b5, b6, b7, b8, b9, b10, b11, b12, b13, b14, b15, b16, b17, b18, b19,... } } ::= INTEGER (0..1048575) ::= SEQUENCE { S-RNTI, ENUMERATED {

1092

3GPP TS 25.423 V11.2.0 (2012-06)

SRB-Delay ::= INTEGER(0..7,...)

SSDT-SupportIndicator ::= ENUMERATED { not-Used-sSDT-supported, sSDT-not-supported } Standalone-Midamble-Channel-Indicator ::= ENUMERATED { used, not-used } Status-Flag ::= ENUMERATED { activate, deactivate }

3GPP

Release 11
STTD-SupportIndicator sTTD-Supported, sTTD-not-Supported } ::= ENUMERATED {

1093

3GPP TS 25.423 V11.2.0 (2012-06)

Support-8PSK ::= ENUMERATED { v8PSK-Supported } Support-PLCCH ::= ENUMERATED { vPLCCH-Supported } Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order ::= ENUMERATED { supported, not-supported } SyncCase ::= INTEGER (1..2,...) SynchronisationConfiguration ::= SEQUENCE { n-INSYNC-IND INTEGER (1..256), n-OUTSYNC-IND INTEGER (1..256), t-RLFAILURE INTEGER (0..255), -- Unit seconds, Range 0s .. 25.5s, Step 0.1s iE-Extensions ProtocolExtensionContainer { { SynchronisationConfiguration-ExtIEs} } ... } SynchronisationConfiguration-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } SYNC-UL-ProcParameters ::= SEQUENCE { maxSYNC-UL-transmissions ENUMERATED {v1, v2, v4, v8, ...}, powerRampStep INTEGER (0..3, ...), ... } -- T T1 ::= ENUMERATED {v10,v20,v30,v40,v50,v60,v70,v80,v90,v100,v120,v140,v160,v200,v300,v400,...} TargetID ::= CGI TDD-AckNack-Power-Offset ::= INTEGER (-7..8,...) -- Unit dB, Range 7dB .. +8dB, Step 1dB TDD-ChannelisationCode chCode1div1, ::= ENUMERATED {

OPTIONAL,

3GPP

Release 11
chCode2div1, chCode2div2, chCode4div1, chCode4div2, chCode4div3, chCode4div4, chCode8div1, chCode8div2, chCode8div3, chCode8div4, chCode8div5, chCode8div6, chCode8div7, chCode8div8, chCode16div1, chCode16div2, chCode16div3, chCode16div4, chCode16div5, chCode16div6, chCode16div7, chCode16div8, chCode16div9, chCode16div10, chCode16div11, chCode16div12, chCode16div13, chCode16div14, chCode16div15, chCode16div16, ... ::= ENUMERATED {

1094

3GPP TS 25.423 V11.2.0 (2012-06)

TDD-ChannelisationCode768 chCode1div1, chCode2div1, chCode2div2, chCode4div1, chCode4div2, chCode4div3, chCode4div4, chCode8div1, chCode8div2, chCode8div3, chCode8div4, chCode8div5, chCode8div6, chCode8div7, chCode8div8, chCode16div1, chCode16div2,

3GPP

Release 11
chCode16div3, chCode16div4, chCode16div5, chCode16div6, chCode16div7, chCode16div8, chCode16div9, chCode16div10, chCode16div11, chCode16div12, chCode16div13, chCode16div14, chCode16div15, chCode16div16, chCode32div1, chCode32div2, chCode32div3, chCode32div4, chCode32div5, chCode32div6, chCode32div7, chCode32div8, chCode32div9, chCode32div10, chCode32div11, chCode32div12, chCode32div13, chCode32div14, chCode32div15, chCode32div16, chCode32div17, chCode32div18, chCode32div19, chCode32div20, chCode32div21, chCode32div22, chCode32div23, chCode32div24, chCode32div25, chCode32div26, chCode32div27, chCode32div28, chCode32div29, chCode32div30, chCode32div31, chCode32div32, ...

1095

3GPP TS 25.423 V11.2.0 (2012-06)

TDD-ChannelisationCodeLCR ::= SEQUENCE { tDD-ChannelisationCode TDD-ChannelisationCode,

3GPP

Release 11
modulation ... }

1096

3GPP TS 25.423 V11.2.0 (2012-06)

Modulation, -- Modulation options for 1.28Mcps TDD in contrast to 3.84Mcps TDD or 7.68Mcps TDD

TDD-DCHs-to-Modify ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF TDD-DCHs-to-ModifyItem TDD-DCHs-to-ModifyItem ::= SEQUENCE { ul-FP-Mode toAWS toAWE transportBearerRequestIndicator dCH-SpecificInformationList iE-Extensions ... } UL-FP-Mode OPTIONAL, ToAWS OPTIONAL, ToAWE OPTIONAL, TransportBearerRequestIndicator, TDD-DCHs-to-ModifySpecificInformationList, ProtocolExtensionContainer { {TDD-DCHs-to-ModifyItem-ExtIEs} } OPTIONAL,

TDD-DCHs-to-ModifyItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TnlQos CRITICALITY ignore ... }

EXTENSION

TnlQos

PRESENCE optional

},

TDD-DCHs-to-ModifySpecificInformationList ::= SEQUENCE (SIZE (1..maxNrOfDCHs)) OF TDD-DCHs-to-ModifySpecificItem TDD-DCHs-to-ModifySpecificItem ::= dCH-ID ul-CCTrCH-ID dl-CCTrCH-ID ul-TransportformatSet dl-TransportformatSet allocationRetentionPriority frameHandlingPriority iE-Extensions ... } SEQUENCE { DCH-ID, CCTrCH-ID OPTIONAL, CCTrCH-ID OPTIONAL, TransportFormatSet OPTIONAL, TransportFormatSet OPTIONAL, AllocationRetentionPriority OPTIONAL, FrameHandlingPriority OPTIONAL, ProtocolExtensionContainer { {TDD-DCHs-to-ModifySpecificItem-ExtIEs} } OPTIONAL,

TDD-DCHs-to-ModifySpecificItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Guaranteed-Rate-Information CRITICALITY ignore EXTENSION Guaranteed-Rate-Information { ID id-TrafficClass CRITICALITY ignore EXTENSION TrafficClass PRESENCE optional}, ... } TDD-DL-Code-Information ::= SEQUENCE ( SIZE (1..maxNrOfDPCHs)) OF TDD-DL-Code-InformationItem

PRESENCE optional

}|

TDD-DL-Code-InformationItem ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { {TDD-DL-Code-InformationItem-ExtIEs} } OPTIONAL, ... } TDD-DL-Code-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

1097

3GPP TS 25.423 V11.2.0 (2012-06)

TDD-DL-Code-LCR-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHsLCR)) OF TDD-DL-Code-LCR-InformationItem TDD-DL-Code-LCR-InformationItem ::= SEQUENCE { dPCH-ID DPCH-ID, tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, tdd-DL-DPCH-TimeSlotFormat-LCR TDD-DL-DPCH-TimeSlotFormat-LCR, iE-Extensions ProtocolExtensionContainer { { TDD-DL-Code-LCR-InformationItem-ExtIEs} } ... } TDD-DL-Code-LCR-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-DL-Code-Information768 ::= SEQUENCE ( SIZE (1..maxNrOfDPCHs768)) OF TDD-DL-Code-InformationItem768 TDD-DL-Code-InformationItem768 ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode768 TDD-ChannelisationCode768, iE-Extensions ProtocolExtensionContainer { {TDD-DL-Code-InformationItem768-ExtIEs} } OPTIONAL, ... } TDD-DL-Code-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-DL-DPCH-TimeSlotFormat-LCR ::= CHOICE { qPSK QPSK-DL-DPCH-TimeSlotFormatTDD-LCR, eightPSK EightPSK-DL-DPCH-TimeSlotFormatTDD-LCR, ... } QPSK-DL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...) EightPSK-DL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...) TDD-DPCHOffset ::= CHOICE { initialOffset INTEGER (0..255), noinitialOffset INTEGER (0..63) } TDD-PhysicalChannelOffset ::= INTEGER (0..63)

OPTIONAL,

TDD-TPC-DownlinkStepSize ::= ENUMERATED { step-size1, step-size2, step-size3,

3GPP

Release 11
} ...

1098

3GPP TS 25.423 V11.2.0 (2012-06)

TDD-TPC-UplinkStepSize-LCR ::= ENUMERATED { step-size1, step-size2, step-size3, ... } TDD-UL-Code-Information ::= SEQUENCE ( SIZE (1..maxNrOfDPCHs)) OF TDD-UL-Code-InformationItem TDD-UL-Code-InformationItem ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode TDD-ChannelisationCode, iE-Extensions ProtocolExtensionContainer { {TDD-UL-Code-InformationItem-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-UL-Code-LCR-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHsLCR)) OF TDD-UL-Code-LCR-InformationItem TDD-UL-Code-LCR-InformationItem ::= SEQUENCE { dPCH-ID DPCH-ID, tdd-ChannelisationCodeLCR TDD-ChannelisationCodeLCR, tdd-UL-DPCH-TimeSlotFormat-LCR TDD-UL-DPCH-TimeSlotFormat-LCR, iE-Extensions ProtocolExtensionContainer { { TDD-UL-Code-LCR-InformationItem-ExtIEs} } ... } TDD-UL-Code-LCR-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-UL-Code-Information768 ::= SEQUENCE ( SIZE (1..maxNrOfDPCHs768)) OF TDD-UL-Code-InformationItem768 TDD-UL-Code-InformationItem768 ::= SEQUENCE { dPCH-ID DPCH-ID, tDD-ChannelisationCode768 TDD-ChannelisationCode768, iE-Extensions ProtocolExtensionContainer { {TDD-UL-Code-InformationItem768-ExtIEs} } OPTIONAL, ... } TDD-UL-Code-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TDD-UL-DPCH-TimeSlotFormat-LCR ::= CHOICE {

OPTIONAL,

3GPP

Release 11
qPSK eightPSK ... QPSK-UL-DPCH-TimeSlotFormatTDD-LCR, EightPSK-UL-DPCH-TimeSlotFormatTDD-LCR,

1099

3GPP TS 25.423 V11.2.0 (2012-06)

QPSK-UL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..69,...) EightPSK-UL-DPCH-TimeSlotFormatTDD-LCR ::= INTEGER(0..24,...) TFCI-Coding ::= ENUMERATED { v4, v8, v16, v32, ... } TFCI-Presence ::= ENUMERATED { present, not-present } TFCI-SignallingMode ::= ENUMERATED { normal, not-Used-split } -- The value Not Used shall not be used by the SRNC. The procedure shall be rejected by the DRNC if the value Not Used is received. TGD ::= INTEGER (0|15..269) -- 0 = Undefined, only one transmission gap in the transmission gap pattern sequence TGPRC -- 0 = infinity TGPSID TGSN TimeSlot ::= INTEGER (0..511) ::= INTEGER (1.. maxTGPS) ::= INTEGER (0..14) ::= INTEGER (0..14)

TimeSlotLCR ::= INTEGER (0..6) Time-Stamp ::= INTEGER (0..9999) -- Unit: 10ms

TimingAdvanceApplied ::= ENUMERATED { yes, no }

3GPP

Release 11
SynchronisationIndicator ::= ENUMERATED { timingMaintainedSynchronisation, ... } TMGI ::= SEQUENCE { plmn-id PLMN-Identity, service-id Service-ID, iE-Extensions ...

1100

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionContainer { { TMGI-ExtIEs} }

OPTIONAL,

TMGI-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TnlQos ::= CHOICE { dsField genericTrafficCategory ... } ToAWE ToAWS TraceDepth minimum, medium, maximum, ... } TraceRecordingSessionReference TraceReference TrafficClass ::= ENUMERATED { conversational, streaming, interactive, background, ... } Transmission-Gap-Pattern-Sequence-Information ::= SEQUENCE (SIZE (1..maxTGPS)) OF SEQUENCE { tGPSID TGPSID, tGSN TGSN, tGL1 GapLength, DsField, GenericTrafficCategory,

::= INTEGER (0..2559) ::= INTEGER (0..1279) ::= ENUMERATED {

::= INTEGER (0..65535) ::= OCTET STRING (SIZE (2..3))

3GPP

Release 11

1101

3GPP TS 25.423 V11.2.0 (2012-06)

tGL2 GapLength OPTIONAL, tGD TGD, tGPL1 GapDuration, not-to-be-used-1 GapDuration OPTIONAL, -- This IE shall never be included in the SEQUENCE. If received it shall be ignored uL-DL-mode UL-DL-mode, downlink-Compressed-Mode-Method Downlink-Compressed-Mode-Method OPTIONAL, -- This IE shall be present if the value of the UL/DL mode IE is DL only or UL/DL uplink-Compressed-Mode-Method Uplink-Compressed-Mode-Method OPTIONAL, -- This IE shall be present if the value of the UL/DL mode IE is UL only or UL/DL dL-FrameType DL-FrameType, delta-SIR1 DeltaSIR, delta-SIR-after1 DeltaSIR, delta-SIR2 DeltaSIR OPTIONAL, delta-SIR-after2 DeltaSIR OPTIONAL, iE-Extensions ProtocolExtensionContainer { {Transmission-Gap-Pattern-Sequence-Information-ExtIEs} } OPTIONAL, ...

Transmission-Gap-Pattern-Sequence-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Transmission-Gap-Pattern-Sequence-ScramblingCode-Information code-change, nocode-change } ::= ENUMERATED{

Transmission-Gap-Pattern-Sequence-Status-List ::= SEQUENCE (SIZE (0..maxTGPS)) OF SEQUENCE { tGPSID TGPSID, tGPRC TGPRC, tGCFN CFN, iE-Extensions ProtocolExtensionContainer { { Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs } } OPTIONAL, ... } Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-Affected-HSDSCH-Serving-Cell-List CRITICALITY reject EXTENSION Affected-HSDSCH-Serving-Cell-List PRESENCE optional}, ... } Affected-HSDSCH-Serving-Cell-List ::= SEQUENCE (SIZE (0.. maxNrOfHSDSCH)) OF C-ID TransmissionMode p-t-p, p-t-m, not-provided, ... } ::=ENUMERATED {

3GPP

Release 11

1102

3GPP TS 25.423 V11.2.0 (2012-06)

Transmission-Mode-Information::= SEQUENCE ( SIZE (1..maxNrOfFDDNeighboursPerRNC,...)) OF Transmission-Mode-Information-List Transmission-Mode-Information-List ::= SEQUENCE { c-ID C-ID, transmissionMode TransmissionMode, iE-Extensions ProtocolExtensionContainer { { Transmission-Mode-Information-List-ExtIEs} } OPTIONAL, ... } Transmission-Mode-Information-List-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TransmissionTimeIntervalDynamic ::= ENUMERATED { msec-10, msec-20, msec-40, msec-80, ... } TransmissionTimeIntervalSemiStatic ::= ENUMERATED { msec-10, msec-20, msec-40, msec-80, dynamic, ... } TransmitDiversityIndicator ::= ENUMERATED { active, inactive } Transmitted-Carrier-Power-Value ::= INTEGER(0..100) -- according to mapping in TS 25.133 [23] and TS 25.123 [24] Transmitted-Carrier-Power-Value-IncrDecrThres ::= INTEGER(0..100) -- according to mapping in TS 25.133 [23] and TS 25.123 [24] Transport-Block-Size-Index ::= INTEGER(1..maxNrOfHS-DSCHTBSs) TUTRANGANSS ::= SEQUENCE { mS INTEGER(0..16383), lS INTEGER(0..4294967295) } TUTRANGANSSAccuracyClass ::= ENUMERATED { ganssAccuracy-class-A, ganssAccuracy-class-B,

3GPP

Release 11
ganssAccuracy-class-C, ... }

1103

3GPP TS 25.423 V11.2.0 (2012-06)

TUTRANGANSSMeasurementThresholdInformation ::= SEQUENCE { tUTRANGANSSChangeLimit INTEGER(1..256) predictedTUTRANGANSSDeviationLimit INTEGER(1..256) ie-Extensions ProtocolExtensionContainer { { TUTRANGANSSMeasurementThresholdInformation-ExtIEs } } ... } TUTRANGANSSMeasurementThresholdInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

OPTIONAL, OPTIONAL, OPTIONAL,

TUTRANGANSSMeasurementValueInformation ::= SEQUENCE { tUTRANGANSS TUTRANGANSS, tUTRANGANSSQuality INTEGER(0..255) OPTIONAL, tUTRANGANSSDriftRate INTEGER(-50..50), tUTRANGANSSDriftRateQuality INTEGER(0..50) OPTIONAL, ie-Extensions ProtocolExtensionContainer { { TUTRANGANSSMeasurementValueInformation-ExtIEs } } ... } TUTRANGANSSMeasurementValueInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-GANSS-Time-ID CRITICALITY ignore EXTENSION GANSS-Time-ID ... } TUTRANGPS ::= SEQUENCE { ms-part INTEGER (0..16383), ls-part INTEGER (0..4294967295) } TUTRANGPSChangeLimit ::= INTEGER (1..256) -- Unit chip, Step 1/16 chip, Range 1/16..16 chip TUTRANGPSDriftRate ::= INTEGER (-50..50) -- Unit chip/s, Step 1/256 chip/s, Range -50/256..+50/256 chip/s TUTRANGPSDriftRateQuality ::= INTEGER (0..50) -- Unit chip/s, Step 1/256 chip/s, Range 0..50/256 chip/s TUTRANGPSAccuracyClass ::= ENUMERATED { accuracy-class-A, accuracy-class-B,

OPTIONAL,

PRESENCE

optional},

3GPP

Release 11
accuracy-class-C, ... }

1104

3GPP TS 25.423 V11.2.0 (2012-06)

TUTRANGPSMeasurementThresholdInformation ::= SEQUENCE { tUTRANGPSChangeLimit TUTRANGPSChangeLimit OPTIONAL, predictedTUTRANGPSDeviationLimit PredictedTUTRANGPSDeviationLimit OPTIONAL, iE-Extensions ProtocolExtensionContainer { { TUTRANGPSMeasurementThresholdInformation-ExtIEs} } ... } TUTRANGPSMeasurementThresholdInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TUTRANGPSMeasurementValueInformation ::= SEQUENCE { tUTRANGPS TUTRANGPS, tUTRANGPSQuality TUTRANGPSQuality OPTIONAL, tUTRANGPSDriftRate TUTRANGPSDriftRate, tUTRANGPSDriftRateQuality TUTRANGPSDriftRateQuality OPTIONAL, iEe-Extensions ProtocolExtensionContainer { { TUTRANGPSMeasurementValueInformationItem-ExtIEs} } ... } TUTRANGPSMeasurementValueInformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TUTRANGPSQuality ::= INTEGER (0..255) -- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip TransportBearerID ::= INTEGER (0..4095) ::= ENUMERATED {

OPTIONAL,

OPTIONAL,

TransportBearerRequestIndicator bearer-requested, bearer-not-requested, ... }

TransportBearerNotRequestedIndicator ::= ENUMERATED { transport-bearer-shall-not-be-established, transport-bearer-may-not-be-established } TransportBearerNotSetupIndicator transport-bearer-not-setup } TransportBlockSize ::= ENUMERATED {

::= INTEGER (0..5000)

3GPP

Release 11
-- Unit is bits

1105

3GPP TS 25.423 V11.2.0 (2012-06)

TransportFormatCombination-Beta ::= CHOICE { signalledGainFactors SEQUENCE { betaC BetaCD, betaD BetaCD, refTFCNumber RefTFCNumber OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SignalledGainFactors-ExtIEs} } OPTIONAL, ... }, refTFCNumber RefTFCNumber, ... } SignalledGainFactors-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TFCS ::= SEQUENCE { tFCSvalues CHOICE { no-Split-in-TFCI TFCS-TFCSList, not-Used-split-in-TFCI NULL, -- This choice shall never be made by the SRNC and the DRNC shall consider the procedure as failed if it is received. ... }, iE-Extensions ProtocolExtensionContainer { { TFCS-ExtIEs} } OPTIONAL, ... } TFCS-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TFCS-TFCSList ::= SEQUENCE (SIZE (1..maxNrOfTFCs)) OF SEQUENCE { cTFC TFCS-CTFC, tFC-Beta TransportFormatCombination-Beta OPTIONAL, -- The IE shall be present if the TFCS concerns a UL DPCH [FDD or PRACH channel in FDD] iE-Extensions ProtocolExtensionContainer { { TFCS-TFCSList-ExtIEs} } OPTIONAL, ... } TFCS-TFCSList-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TFCS-CTFC ::= CHOICE { ctfc2bit ctfc4bit ctfc6bit ctfc8bit INTEGER INTEGER INTEGER INTEGER (0..3), (0..15), (0..63), (0..255),

3GPP

Release 11
ctfc12bit ctfc16bit ctfcmaxbit INTEGER (0..4095), INTEGER (0..65535), INTEGER (0..maxCTFC)

1106

3GPP TS 25.423 V11.2.0 (2012-06)

TransportFormatSet ::= SEQUENCE { dynamicParts TransportFormatSet-DynamicPartList, semi-staticPart TransportFormatSet-Semi-staticPart, iE-Extensions ProtocolExtensionContainer { {TransportFormatSet-ExtIEs} } OPTIONAL, ... } TransportFormatSet-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TransportFormatSet-DynamicPartList ::= SEQUENCE (SIZE (1..maxNrOfTFs)) OF SEQUENCE { nrOfTransportBlocks NrOfTransportBlocks, transportBlockSize TransportBlockSize OPTIONAL -- This IE shall be present if nrOfTransportBlocks is greater than 0 --, mode TransportFormatSet-ModeDP, iE-Extensions ProtocolExtensionContainer { {TransportFormatSet-DynamicPartList-ExtIEs} } OPTIONAL, ... } TransportFormatSet-DynamicPartList-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TransportFormatSet-ModeDP ::= CHOICE { tdd TDD-TransportFormatSet-ModeDP, notApplicable NULL, ... } TDD-TransportFormatSet-ModeDP ::= SEQUENCE { transmissionTimeIntervalInformation TransmissionTimeIntervalInformation OPTIONAL, -- This IE shall be present if the Transmission Time Interval of the Semi-static Transport Format Information is dynamic. Otherwise it is absent. iE-Extensions ProtocolExtensionContainer { {TDD-TransportFormatSet-ModeDP-ExtIEs} } OPTIONAL, ... } TDD-TransportFormatSet-ModeDP-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TransmissionTimeIntervalInformation ::= SEQUENCE (SIZE (1..maxTTI-Count)) OF SEQUENCE { transmissionTimeInterval TransmissionTimeIntervalDynamic,

3GPP

Release 11
iE-Extensions ... } TransmissionTimeIntervalInformation-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Transmitted-Code-Power-Value ::= INTEGER (0..127) -- According to mapping in TS 25.215 [11]/TS 25.225 [14] Transmitted-Code-Power-Value-IncrDecrThres ::= INTEGER (0..112,...) TransportFormatManagement ::= ENUMERATED { cell-based, ue-based, ... }

1107
ProtocolExtensionContainer { {TransmissionTimeIntervalInformation-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

TransportFormatSet-Semi-staticPart ::= SEQUENCE { transmissionTime TransmissionTimeIntervalSemiStatic, channelCoding ChannelCodingType, codingRate CodingRate OPTIONAL -- This IE shall be present if channelCoding is convolutional or turbo --, rateMatcingAttribute RateMatchingAttribute, cRC-Size CRC-Size, mode TransportFormatSet-ModeSSP, iE-Extensions ProtocolExtensionContainer { {TransportFormatSet-Semi-staticPart-ExtIEs} } OPTIONAL, ... } TransportFormatSet-Semi-staticPart-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } TransportFormatSet-ModeSSP ::= CHOICE { tdd SecondInterleavingMode, notApplicable NULL, ... } TransportLayerAddress TrCH-SrcStatisticsDescr speech, rRC, unknown, ... } TSN-Length ::= ENUMERATED { ::= BIT STRING (SIZE(1..160, ...)) ::= ENUMERATED {

3GPP

Release 11
tsn-6bits, tsn-9bits } TSTD-Indicator ::= ENUMERATED { active, inactive } TSTD-Support-Indicator ::= ENUMERATED { tSTD-supported, tSTD-not-supported } TxDiversityIndicator true, false } ::= ENUMERATED {

1108

3GPP TS 25.423 V11.2.0 (2012-06)

TypeOfError ::= ENUMERATED { not-understood, missing, ... } -- U UARFCN ::= INTEGER (0..16383,...) -- Corresponds to: 0.0Hz..3276.6Mhz. See TS 25.105 [7], TS 25.101 [43] UDRE ::= ENUMERATED { lessThan1, between1-and-4, between4-and-8, over8, ... } UDREGrowthRate ::= ENUMERATED { growth-1-point-5, growth-2, growth-4, growth-6, growth-8, growth-10, growth-12, growth-16 } ::= ENUMERATED { val-20sec, val-40sec,

UDREValidityTime

3GPP

Release 11
val-80sec, val-160sec, val-320sec, val-640sec, val-1280sec, val-2560sec } UE-AggregateMaximumBitRate ::= SEQUENCE { uE-AggregateMaximumBitRateDownlink uE-AggregateMaximumBitRateUplink ... } UE-AggregateMaximumBitRateDownlink -- Unit is bits per sec UE-AggregateMaximumBitRateUplink -- Unit is bits per sec

1109

3GPP TS 25.423 V11.2.0 (2012-06)

UE-AggregateMaximumBitRateDownlink UE-AggregateMaximumBitRateUplink

OPTIONAL, OPTIONAL,

::= INTEGER (1..1000000000) ::= INTEGER (1..1000000000)

UE-AggregateMaximumBitRate-Enforcement-Indicator ::= NULL UE-Capabilities-Info ::= SEQUENCE { hSDSCH-Physical-Layer-Category iE-Extensions ... } INTEGER (1..64,...), ProtocolExtensionContainer { { UE-Capabilities-Info-ExtIEs } }

OPTIONAL,

UE-Capabilities-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { {ID id-LCRTDD-uplink-Physical-Channel-Capability CRITICALITY optional}| {ID id-number-Of-Supported-Carriers CRITICALITY {ID id-MIMO-SFMode-Supported-For-HSPDSCHDualStream CRITICALITY {ID id-MultiCarrier-HSDSCH-Physical-Layer-Category CRITICALITY {ID id-UE-TS0-CapabilityLCR CRITICALITY {ID id-UE-RF-Band-CapabilityLCR CRITICALITY ... } UE-TS0-CapabilityLCR ::= ENUMERATED { tS0-Capable, tS0-Not-Capable }

ignore reject ignore ignore ignore ignore

EXTENSION LCRTDD-Uplink-Physical-Channel-Capability EXTENSION EXTENSION EXTENSION EXTENSION EXTENSION Number-Of-Supported-Carriers MIMO-SFMode-For-HSPDSCHDualStream LCRTDD-HSDSCH-Physical-Layer-Category UE-TS0-CapabilityLCR UE-RF-Band-CapabilityLCR

PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE PRESENCE optional}| optional}| optional}| optional}| conditional},

UE-RF-Band-CapabilityLCR ::= SEQUENCE (SIZE (1.. maxFreqBandsTDD)) OF Radio-Frequency-BandItem Radio-Frequency-BandItem ::= SEQUENCE { radio-Frequency-Band iE-Extensions ... } Radio-Frequency-Band, ProtocolExtensionContainer { { Radio-Frequency-BandItem-ExtIEs } }

OPTIONAL,

3GPP

Release 11
Radio-Frequency-Band ::= ENUMERATED { a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, ... } Radio-Frequency-BandItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } LCRTDD-HSDSCH-Physical-Layer-Category ::= INTEGER (1..64) UE-DPCCH-burst1 ::= ENUMERATED {v1, v2, v5} -- Unit subframe UE-DPCCH-burst2 ::= ENUMERATED {v1, v2, v5} -- Unit subframe UE-DRX-Cycle ::= ENUMERATED {v4, v5, v8, v10, v16, v20} -- Unit subframe UE-DRX-Grant-Monitoring ::= BOOLEAN -- true: applied, false: not applied UE-DTX-Cycle1-2ms ::= ENUMERATED {v1, v4, v5, v8, v10, v16, v20} -- Unit subframe UE-DTX-Cycle1-10ms ::= ENUMERATED {v1, v5, v10, v20} -- Unit subframe

1110

3GPP TS 25.423 V11.2.0 (2012-06)

UE-DTX-Cycle2-2ms ::= ENUMERATED {v4, v5, v8, v10, v16, v20, v32, v40, v64, v80, v128, v160} -- Unit subframe UE-DTX-Cycle2-10ms ::= ENUMERATED {v5, v10, v20, v40, v80, v160} -- Unit subframe UE-DTX-DRX-Offset ::= INTEGER (0..159)

3GPP

Release 11
-- Unit subframe UE-DTX-Long-Preamble ::= ENUMERATED {v2, v4, v15} -- Units of slots

1111

3GPP TS 25.423 V11.2.0 (2012-06)

UEIdentity imsi imei imeisv ... }

::= CHOICE { IMSI, IMEI, IMEISV,

UEMeasurementHysteresisTime ::= INTEGER (0..15) -- Unit dB -- Range 0..7.5 dB -- Step 0.5 dB UEMeasurementParameterModAllow ::= ENUMERATED { parameterModificationAllowed, ... } UEMeasurementReportCharacteristics ::= CHOICE { periodic UEMeasurementReportCharacteristicsPeriodic, event1h UEMeasurementReportCharacteristicsEvent1h, event1i UEMeasurementReportCharacteristicsEvent1i, event6a UEMeasurementReportCharacteristicsEvent6a, event6b UEMeasurementReportCharacteristicsEvent6b, event6c UEMeasurementReportCharacteristicsEvent6c, event6d UEMeasurementReportCharacteristicsEvent6d, ..., extension-ReportCharacteristics UEMeasurementReportCharacteristics-Extension } UEMeasurementReportCharacteristicsEvent1h ::= SEQUENCE { uEMeasurementTreshold UEMeasurementThreshold, uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger, uEMeasurementHysteresisTime UEMeasurementHysteresisTime, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent1h-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsEvent1h-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristicsEvent1i ::= SEQUENCE { uEMeasurementTreshold UEMeasurementThreshold, uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger,

3GPP

Release 11

1112

3GPP TS 25.423 V11.2.0 (2012-06)

uEMeasurementHysteresisTime UEMeasurementHysteresisTime, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent1i-ExtIEs} } OPTIONAL, ...

UEMeasurementReportCharacteristicsEvent1i-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristicsEvent6a ::= SEQUENCE { uEMeasurementTreshold UEMeasurementThreshold, uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent6a-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsEvent6a-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristicsEvent6b ::= SEQUENCE { uEMeasurementTreshold UEMeasurementThreshold, uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent6b-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsEvent6b-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristicsEvent6c ::= SEQUENCE { uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent6c-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsEvent6c-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristicsEvent6d ::= SEQUENCE { uEMeasurementTimeToTrigger UEMeasurementTimeToTrigger, iE-Extensions ProtocolExtensionContainer { { UEMeasurementReportCharacteristicsEvent6d-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsEvent6d-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1113

3GPP TS 25.423 V11.2.0 (2012-06)

UEMeasurementReportCharacteristicsPeriodic ::= SEQUENCE { amountofReporting UEMeasurementReportCharacteristicsPeriodicAmountofReporting, reportingInterval UEMeasurementReportCharacteristicsPeriodicReportingInterval, iE-Extensions ProtocolExtensionContainer { {UEMeasurementReportCharacteristicsPeriodic-ExtIEs} } OPTIONAL, ... } UEMeasurementReportCharacteristicsPeriodicAmountofReporting::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, rInfinity } UEMeasurementReportCharacteristicsPeriodicReportingInterval::= ENUMERATED { r250, r500, r1000, r2000, r3000, r4000, r6000, r8000, r12000, r16000, r20000, r24000, r28000, r32000, r64000 } UEMeasurementReportCharacteristicsPeriodic-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementReportCharacteristics-Extension ::= ProtocolIE-Single-Container {{ UEMeasurementReportCharacteristics-ExtensionIE }}

UEMeasurementReportCharacteristics-ExtensionIE RNSAP-PROTOCOL-IES ::= { ... } UEMeasurementThreshold ::= CHOICE { timeslotISCP UEMeasurementThresholdDLTimeslotISCP, uETransmitPower UEMeasurementThresholdUETransmitPower, ..., extension-UEMeasurementThreshold UEMeasurementThreshold-Extension

3GPP

Release 11
} UEMeasurementThresholdDLTimeslotISCP ::= UEMeasurementThresholdUETransmitPower ::= UEMeasurementThreshold-Extension INTEGER(-115..-25) INTEGER(-50..33)

1114

3GPP TS 25.423 V11.2.0 (2012-06)

::= ProtocolIE-Single-Container {{ UEMeasurementThreshold-ExtensionIE }}

UEMeasurementThreshold-ExtensionIE RNSAP-PROTOCOL-IES ::= { ... } UEMeasurementTimeslotInfoHCR::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementTimeslotInfoHCR-IEs UEMeasurementTimeslotInfoHCR-IEs ::= SEQUENCE { timeSlot TimeSlot, burstType UEMeasurementTimeslotInfoHCRBurstType, iE-Extensions ProtocolExtensionContainer { { UEMeasurementTimeslotInfoHCR-IEs-ExtIEs} } ... } UEMeasurementTimeslotInfoHCRBurstType ::= ENUMERATED { type1, type2, type3, ... } UEMeasurementTimeslotInfoHCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementTimeslotInfoLCR::= SEQUENCE (SIZE (1..maxNrOfTsLCR)) OF UEMeasurementTimeslotInfoLCR-IEs UEMeasurementTimeslotInfoLCR-IEs ::= SEQUENCE { timeSlot TimeSlotLCR, iE-Extensions ProtocolExtensionContainer { { UEMeasurementTimeslotInfoLCR-IEs-ExtIEs} } ... } UEMeasurementTimeslotInfoLCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementTimeslotInfo768::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementTimeslotInfo768-IEs UEMeasurementTimeslotInfo768-IEs ::= SEQUENCE { timeSlot TimeSlot, burstType UEMeasurementTimeslotInfo768BurstType, iE-Extensions ProtocolExtensionContainer { { UEMeasurementTimeslotInfo768-IEs-ExtIEs} }

OPTIONAL,

OPTIONAL,

OPTIONAL,

3GPP

Release 11
} ...

1115

3GPP TS 25.423 V11.2.0 (2012-06)

UEMeasurementTimeslotInfo768BurstType ::= ENUMERATED { type1, type2, type3, ... } UEMeasurementTimeslotInfo768-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementTimeToTrigger ::= ENUMERATED { r0, r10, r20, r40, r60, r80, r100, r120, r160, r200, r240, r320, r640, r1280, r2560, r5000 } UEMeasurementType ::= ENUMERATED { primary-CCPCH-RSCP, dL-Timeslot-ISCP, uE-Transmitted-power, ... } UEMeasurementValue ::= CHOICE { uE-Transmitted-Power UE-MeasurementValue-UE-Transmitted-Power, primary-CCPCH-RSCP UE-MeasurementValue-Primary-CCPCH-RSCP, dL-Timeslot-ISCP UE-MeasurementValue-DL-Timeslot-ISCP, ..., extension-UEMeasurementValue UEMeasurementValue-Extension } UE-MeasurementValue-UE-Transmitted-Power ::= SEQUENCE { uEMeasurementTransmittedPowerListHCR UEMeasurementValueTransmittedPowerListHCR -- Mandatory for 3.84Mcps TDD, Not applicable for 1.28Mcps TDD or 7.68Mcps TDD OPTIONAL,

3GPP

Release 11

1116

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

uEMeasurementTransmittedPowerListLCR UEMeasurementValueTransmittedPowerListLCR OPTIONAL, -- Mandatory for 1.28Mcps TDD, Not applicable for 3.84Mcps TDD or 7.68Mcps TDD iE-Extensions ProtocolExtensionContainer { { UE-MeasurementValue-UE-Transmitted-Power-ExtIEs} } ... } UE-MeasurementValue-UE-Transmitted-Power-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UEMeasurementValueTransmittedPowerList768 CRITICALITY ignore PRESENCE optional }, ... } UEMeasurementValueTransmittedPowerListHCR EXTENSION UEMeasurementValueTransmittedPowerList768

::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementValueTransmittedPowerListHCR-IEs

UEMeasurementValueTransmittedPowerListHCR-IEs ::= SEQUENCE { timeSlot TimeSlot, uETransmitPower INTEGER(0..104), -- mapping according to TS 25.123 [24],values 0..20 not used iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTransmittedPowerListHCR-IEs-ExtIEs} } ... } UEMeasurementValueTransmittedPowerListHCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValueTransmittedPowerListLCR ::= SEQUENCE (SIZE (1..maxNrOfTsLCR)) OF UEMeasurementValueTransmittedPowerListLCR-IEs UEMeasurementValueTransmittedPowerListLCR-IEs ::= SEQUENCE { timeSlotLCR TimeSlotLCR, uETransmitPower INTEGER(0..104), -- mapping according to TS 25.123 [24],values 0..20 not used iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTransmittedPowerListLCR-IEs-ExtIEs} } ... } UEMeasurementValueTransmittedPowerListLCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValueTransmittedPowerList768 ::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementValueTransmittedPowerList768-IEs

OPTIONAL,

OPTIONAL,

UEMeasurementValueTransmittedPowerList768-IEs ::= SEQUENCE { timeSlot TimeSlot, uETransmitPower INTEGER(0..104), -- mapping according to TS 25.123 [24],values 0..20 not used iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTransmittedPowerList768-IEs-ExtIEs} } ... }

OPTIONAL,

3GPP

Release 11

1117

3GPP TS 25.423 V11.2.0 (2012-06)

UEMeasurementValueTransmittedPowerList768-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UE-MeasurementValue-Primary-CCPCH-RSCP::= SEQUENCE { primaryCCPCH-RSCP PrimaryCCPCH-RSCP OPTIONAL, primaryCCPCH-RSCP-Delta PrimaryCCPCH-RSCP-Delta OPTIONAL, iE-Extensions ProtocolExtensionContainer { { UE-MeasurementValue-Primary-CCPCH-RSCP-ExtIEs} } ... } UE-MeasurementValue-Primary-CCPCH-RSCP-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UE-MeasurementValue-DL-Timeslot-ISCP ::= SEQUENCE { uEMeasurementTimeslotISCPListHCR UEMeasurementValueTimeslotISCPListHCR OPTIONAL, -- Mandatory for 3.84Mcps TDD, Not applicable for 1.28Mcps TDD or 7.68Mcps TDD uEMeasurementTimeslotISCPListLCR UEMeasurementValueTimeslotISCPListLCR OPTIONAL, -- Mandatory for 1.28Mcps TDD, Not applicable for 3.84Mcps TDD or 7.68Mcps TDD iE-Extensions ProtocolExtensionContainer { { UE-MeasurementValue-DL-Timeslot-ISCP-ExtIEs} } ... } UE-MeasurementValue-DL-Timeslot-ISCP-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-UEMeasurementValueTimeslotISCPList768 CRITICALITY ignore optional }, ... } UEMeasurementValueTimeslotISCPListHCR EXTENSION UEMeasurementValueTimeslotISCPList768

OPTIONAL,

OPTIONAL,

PRESENCE

::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementValueTimeslotISCPListHCR-IEs

UEMeasurementValueTimeslotISCPListHCR-IEs ::= SEQUENCE { timeSlot TimeSlot, dL-TimeslotISCP DL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTimeslotISCPListHCR-IEs-ExtIEs} } ... } UEMeasurementValueTimeslotISCPListHCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValueTimeslotISCPListLCR ::= SEQUENCE (SIZE (1..maxNrOfTsLCR)) OF UEMeasurementValueTimeslotISCPListLCR-IEs UEMeasurementValueTimeslotISCPListLCR-IEs ::= SEQUENCE { timeSlotLCR TimeSlotLCR, dL-TimeslotISCP DL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTimeslotISCPListLCR-IEs-ExtIEs} } ... }

OPTIONAL,

OPTIONAL,

3GPP

Release 11

1118

3GPP TS 25.423 V11.2.0 (2012-06)

UEMeasurementValueTimeslotISCPListLCR-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValueTimeslotISCPList768 ::= SEQUENCE (SIZE (1..maxNrOfTS)) OF UEMeasurementValueTimeslotISCPList768-IEs

UEMeasurementValueTimeslotISCPList768-IEs ::= SEQUENCE { timeSlot TimeSlot, dL-TimeslotISCP DL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { UEMeasurementValueTimeslotISCPList768-IEs-ExtIEs} } ... } UEMeasurementValueTimeslotISCPList768-IEs-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValue-Extension ::= ProtocolIE-Single-Container {{ UEMeasurementValue-ExtensionIE }}

OPTIONAL,

UEMeasurementValue-ExtensionIE RNSAP-PROTOCOL-IES ::= { ... } UEMeasurementValueInformation ::= CHOICE { measurementAvailable UEMeasurementValueInformationAvailable, measurementnotAvailable UEMeasurementValueInformationnotAvailable } UEMeasurementValueInformationAvailable::= SEQUENCE { uEmeasurementValue UEMeasurementValue, ie-Extensions ProtocolExtensionContainer { { UEMeasurementValueInformationAvailableItem-ExtIEs} } ... } UEMeasurementValueInformationAvailableItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UEMeasurementValueInformationnotAvailable ::= NULL UE-SupportIndicatorExtension ::= BIT STRING (SIZE (32)) -- First bit: Different HS-SCCH In Consecutive TTIs Support Indicator -- Second bit: HS-SCCH orders in HS-SCCH-less Operation Support Indicator -- Third bit: RRC Rel-9 (onwards) handling of DL secondary HS-DSCH (de)activation state Support Indicator -- Fourth bit: UE DTX/DRX related HS-SCCH orders uniform behavior indicator -- Note that undefined bits are considered as a spare bit and spare bits shall be set to 0 by the transmitter and shall be ignored by the receiver. UE-State ::= CHOICE { cell-fach-pch ura-pch ... Cell-Fach-Pch-State, Ura-Pch-State,

OPTIONAL,

3GPP

Release 11
}

1119

3GPP TS 25.423 V11.2.0 (2012-06)

Cell-Fach-Pch-State ::= SEQUENCE { d-RNTI iE-Extensions ... }

D-RNTI, ProtocolExtensionContainer

{ { Cell-Fach-Pch-State-ExtIEs} }

OPTIONAL,

Cell-Fach-Pch-State-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } Ura-Pch-State ::= SEQUENCE { srnc-id ura-id iE-Extensions ... } RNC-ID, URA-ID, ProtocolExtensionContainer

{ { Ura-Pch-State-ExtIEs} }

OPTIONAL,

Ura-Pch-State-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-SRNC-ID CRITICALITY reject ... } UL-Delta-T2TP ::= INTEGER (0..6,...) UL-DL-mode ::= ENUMERATED { ul-only, dl-only, both-ul-and-dl } UL-DPDCHIndicatorEDCH ::= ENUMERATED { uL-DPDCH-present, uL-DPDCH-not-present}

EXTENSION Extended-RNC-ID

PRESENCE optional

},

UL-Timeslot-Information::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationItem UL-Timeslot-InformationItem ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType MidambleShiftAndBurstType, tFCI-Presence TFCI-Presence, uL-Code-Information TDD-UL-Code-Information, iE-Extensions ProtocolExtensionContainer { {UL-Timeslot-InformationItem-ExtIEs} } OPTIONAL, ... } UL-Timeslot-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ...

3GPP

Release 11
}

1120

3GPP TS 25.423 V11.2.0 (2012-06)

UL-TimeslotLCR-Information ::= SEQUENCE (SIZE (1..maxNrOfULTsLCR)) OF UL-TimeslotLCR-InformationItem UL-TimeslotLCR-InformationItem ::= SEQUENCE { timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, tFCI-Presence TFCI-Presence, uL-Code-LCR-InformationList TDD-UL-Code-LCR-Information, iE-Extensions ProtocolExtensionContainer { { UL-TimeslotLCR-InformationItem-ExtIEs} } ... } UL-TimeslotLCR-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-PLCCH-Information-UL-TimeslotLCR-Info CRITICALITY ignore EXTENSION PLCCHinformation ... } PLCCHinformation ::= SEQUENCE { tDD-ChannelisationCode TDD-ChannelisationCode, timeSlotLCR TimeSlotLCR, midambleShiftLCR MidambleShiftLCR, sequenceNumber PLCCHsequenceNumber, iE-Extensions ProtocolExtensionContainer { { PLCCHinformation-ExtIEs} } ... } PLCCHinformation-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

OPTIONAL,

PRESENCE optional },

OPTIONAL,

UL-Timeslot-Information768::= SEQUENCE ( SIZE (1..maxNrOfTS)) OF UL-Timeslot-InformationItem768 UL-Timeslot-InformationItem768 ::= SEQUENCE { timeSlot TimeSlot, midambleShiftAndBurstType768 MidambleShiftAndBurstType768, tFCI-Presence TFCI-Presence, uL-Code-Information768 TDD-UL-Code-Information768, iE-Extensions ProtocolExtensionContainer { {UL-Timeslot-InformationItem768-ExtIEs} } OPTIONAL, ... } UL-Timeslot-InformationItem768-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-TimeSlot-ISCP-Info ::= SEQUENCE (SIZE (1..maxNrOfULTs)) OF UL-TimeSlot-ISCP-InfoItem UL-TimeSlot-ISCP-InfoItem ::= SEQUENCE { timeSlot TimeSlot, uL-TimeslotISCP UL-TimeslotISCP, iE-Extensions ProtocolExtensionContainer { { UL-TimeSlot-ISCP-InfoItem-ExtIEs} } OPTIONAL,

3GPP

Release 11
} ...

1121

3GPP TS 25.423 V11.2.0 (2012-06)

UL-TimeSlot-ISCP-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-TimeSlot-ISCP-LCR-Info ::= SEQUENCE (SIZE (1..maxNrOfULTsLCR)) OF UL-TimeSlot-ISCP-LCR-InfoItem

UL-TimeSlot-ISCP-LCR-InfoItem ::= SEQUENCE { timeSlotLCR TimeSlotLCR, iSCP UL-Timeslot-ISCP-Value, iE-Extensions ProtocolExtensionContainer { { UL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs} } ... } UL-TimeSlot-ISCP-LCR-InfoItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-Timeslot-ISCP-Value ::= UL-TimeslotISCP UL-Timeslot-ISCP-Value-IncrDecrThres ::= INTEGER(0..126) -- Unit dB. Step 0.5dB -- e.g. Value 100 means 50dB UL-TimingAdvanceCtrl-LCR ::= SEQUENCE { sync-UL-codes-bitmap fPACH-info prxUpPCHdes syncUL-procParameter mMax ... } Uplink-Compressed-Mode-Method sFdiv2, higher-layer-scheduling, ... } BIT STRING (SIZE(8)), FPACH-Information, INTEGER (-120 .. -58, ...), SYNC-UL-ProcParameters, INTEGER (1..32),

OPTIONAL,

::= ENUMERATED {

UL-SIR ::= INTEGER (-82..173) -- The UL-SIR gives the UL-SIR in number of 0.1 dB steps. -- E.g. Value 173 means 17.3 dB -- Unit dB. Step 0.1 dB. UC-ID ::= SEQUENCE { rNC-ID c-ID iE-Extensions ... RNC-ID, C-ID, ProtocolExtensionContainer { {UC-ID-ExtIEs} } OPTIONAL,

3GPP

Release 11
} UC-ID-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-RNC-ID CRITICALITY reject ... } UL-DPCCH-SlotFormat UL-FP-Mode ::= ENUMERATED { normal, silent, ... } UL-PhysCH-SF-Variation ::= ENUMERATED { sf-variation-supported, sf-variation-not-supported } ::= INTEGER (0..5,...) EXTENSION

1122

3GPP TS 25.423 V11.2.0 (2012-06)

Extended-RNC-ID PRESENCE optional},

UL-ScramblingCode ::= SEQUENCE { ul-ScramblingCodeNumber UL-ScramblingCodeNumber, ul-ScramblingCodeLength UL-ScramblingCodeLength, iE-Extensions ProtocolExtensionContainer { {UL-ScramblingCode-ExtIEs} } OPTIONAL } UL-ScramblingCode-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-ScramblingCodeLength ::= ENUMERATED { short, long } UL-ScramblingCodeNumber ::= INTEGER (0..16777215)

UL-Synchronisation-Parameters-LCR ::= SEQUENCE { uL-Synchronisation-StepSize UL-Synchronisation-StepSize, uL-Synchronisation-Frequency UL-Synchronisation-Frequency, iE-Extensions ProtocolExtensionContainer { { UL-Synchronisation-Parameters-LCR-ExtIEs } } ... } UL-Synchronisation-Parameters-LCR-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-Synchronisation-StepSize ::= INTEGER (1..8) UL-Synchronisation-Frequency ::= INTEGER (1..8)

OPTIONAL,

3GPP

Release 11
UL-TimeslotISCP ::= INTEGER (0..127) -- According to mapping in TS 25.225 [14] UPPCHPositionLCR ::= INTEGER (0..127) UpPTSInterferenceValue ::= INTEGER (0..127,...) ::= ENUMERATED {

1123

3GPP TS 25.423 V11.2.0 (2012-06)

Unidirectional-DCH-Indicator downlink-DCH-only, uplink-DCH-only } URA-ID

::= INTEGER (0..65535) URA-ID, MultipleURAsIndicator, RNCsWithCellsInTheAccessedURA-List OPTIONAL, ProtocolExtensionContainer { {URA-Information-ExtIEs} } OPTIONAL,

URA-Information ::= SEQUENCE { uRA-ID multipleURAsIndicator rNCsWithCellsInTheAccessedURA-List iE-Extensions ... }

URA-Information-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-Extended-RNC-ID CRITICALITY reject ... }

EXTENSION Extended-RNC-ID

PRESENCE optional },

RNCsWithCellsInTheAccessedURA-List ::= SEQUENCE (SIZE (1..maxRNCinURA-1)) OF RNCsWithCellsInTheAccessedURA-Item RNCsWithCellsInTheAccessedURA-Item ::= SEQUENCE { rNC-ID RNC-ID, iE-Extensions ProtocolExtensionContainer { {RNCsWithCellsInTheAccessedURA-Item-ExtIEs} } OPTIONAL, ... } RNCsWithCellsInTheAccessedURA-Item-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } USCH-ID USCH-Information ::= ::= INTEGER (0..255) SEQUENCE (SIZE (1..maxNoOfUSCHs)) OF USCH-InformationItem USCH-ID, CCTrCH-ID, TrCH-SrcStatisticsDescr, TransportFormatSet, AllocationRetentionPriority, SchedulingPriorityIndicator,

USCH-InformationItem ::= SEQUENCE { uSCH-ID ul-CCTrCH-ID trChSourceStatisticsDescriptor transportFormatSet allocationRetentionPriority schedulingPriorityIndicator

3GPP

Release 11
rb-Info iE-Extensions ...

1124
RB-Info, ProtocolExtensionContainer { {USCH-InformationItem-ExtIEs} } OPTIONAL,

3GPP TS 25.423 V11.2.0 (2012-06)

USCH-InformationItem-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { { ID id-TrafficClass CRITICALITY ignore { ID id-BindingID CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. { ID id-TransportLayerAddress CRITICALITY ignore -- Shall be ignored if bearer establishment with ALCAP. { ID id-TnlQos CRITICALITY ignore ... }

EXTENSION TrafficClass EXTENSION BindingID EXTENSION TransportLayerAddress EXTENSION TnlQos

PRESENCE mandatory}| PRESENCE optional}| PRESENCE optional}| PRESENCE optional},

Usefulness-Of-Battery-Optimization ::= ENUMERATED {can-benefit, cannot-benefit} User-Plane-Congestion-Fields-Inclusion Uu-ActivationState ::= ENUMERATED { activated, de-activated, ... } UMTS-Cells-Info-List ::= SEQUENCE (SIZE (0..maxNrOfCells)) OF ProtocolIE-Single-Container { {UMTS-Cells-Info-IEs} } UMTS-Cells-Info-IEs RNSAP-PROTOCOL-IES ::= { { ID id-UMTS-Cells-Info CRITICALITY ignore } UMTS-Cell-Info ::= SEQUENCE{ c-ID iE-Extensions ... } UMTS-Cell-Info-ExtIEs ... } TYPE UMTS-Cell-Info PRESENCE optional } ::= ENUMERATED { shall-be-included }

C-ID, ProtocolExtensionContainer { { UMTS-Cell-Info-ExtIEs} } OPTIONAL,

RNSAP-PROTOCOL-EXTENSION ::= {

UL-CLTD-Information ::= SEQUENCE { sDPCCH-PowerOffsetInformation SDPCCH-PowerOffsetInformation, c-ID C-ID OPTIONAL, -- The IE shall be present only if there is no serving E-DCH RL or HS-DSCH RL configuration in the concerned UE Context. uL-CLTD-Activation-Information UL-CLTD-Activation-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { UL-CLTD-Info-ExtIEs } } OPTIONAL, ... } UL-CLTD-Info-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= {

3GPP

Release 11
} ...

1125

3GPP TS 25.423 V11.2.0 (2012-06)

UL-CLTD-Information-Reconf ::=SEQUENCE{ setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD iE-Extensions ... } UL-CLTD-Information-Reconf-ExtIEs ... } RNSAP-PROTOCOL-EXTENSION ::= {

Setup-Or-ConfigurationChange-Or-Removal-Of-UL-CLTD, ProtocolExtensionContainer { { UL-CLTD-Information-Reconf-ExtIEs} } OPTIONAL,

UL-CLTD-Information-To-Modify ::= SEQUENCE { sDPCCH-PowerOffsetInformation SDPCCH-PowerOffsetInformation OPTIONAL, c-ID C-ID OPTIONAL, uL-CLTD-Activation-Information UL-CLTD-Activation-Information OPTIONAL, iE-Extensions ProtocolExtensionContainer { { UL-CLTD-Information-To-Modify-ExtIEs } } ... } UL-CLTD-Information-To-Modify-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } UL-CLTD-Information-Removal ::= ENUMERATED { remove, ... } UL-CLTD-State-Update-Information ::= ENUMERATED { activate, de-activate, ... } UL-CLTD-Activation-Information ::= ENUMERATED { activated, de-activated, ... } -----END V W X Y Z

OPTIONAL,

3GPP

Release 11

1126

3GPP TS 25.423 V11.2.0 (2012-06)

9.3.5 Common Definitions

-- ************************************************************** --- Common definitions --- ************************************************************** RNSAP-CommonDataTypes { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-CommonDataTypes (3) DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** --- Extension constants --- ************************************************************** maxPrivateIEs maxProtocolExtensions maxProtocolIEs INTEGER ::= 65535 INTEGER ::= 65535 INTEGER ::= 65535

-- ************************************************************** --- Common Data Types --- ************************************************************** Criticality Presence PrivateIE-ID local global } ProcedureCode ::= ENUMERATED { reject, ignore, notify } ::= ENUMERATED { optional, conditional, mandatory } ::= CHOICE { INTEGER (0.. maxPrivateIEs), OBJECT IDENTIFIER ::= INTEGER (0..255)

ProcedureID ::= SEQUENCE { procedureCode ProcedureCode, ddMode ENUMERATED { tdd, fdd, common, ... } } ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs)

3GPP

Release 11
TransactionID ::= CHOICE { shortTransActionId INTEGER (0..127), longTransActionId INTEGER (0..32767) } TriggeringMessage END

1127

3GPP TS 25.423 V11.2.0 (2012-06)

::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome, outcome }

9.3.6 Constant Definitions

-- ************************************************************** --- Constant definitions --- ************************************************************** RNSAP-Constants { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-Constants (4) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS ProcedureCode, ProtocolIE-ID FROM RNSAP-CommonDataTypes; -- ************************************************************** --- Elementary Procedures --- ************************************************************** id-commonTransportChannelResourcesInitialisation id-commonTransportChannelResourcesRelease id-compressedModeCommand id-downlinkPowerControl id-downlinkPowerTimeslotControl id-downlinkSignallingTransfer id-errorIndication id-dedicatedMeasurementFailure id-dedicatedMeasurementInitiation id-dedicatedMeasurementReporting id-dedicatedMeasurementTermination id-paging id-physicalChannelReconfiguration id-privateMessage ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 0 1 2 3 4 5 6 7 8 9 10 11 12 13

3GPP

Release 11
id-radioLinkAddition id-radioLinkCongestion id-radioLinkDeletion id-radioLinkFailure id-radioLinkPreemption id-radioLinkRestoration id-radioLinkSetup id-relocationCommit id-synchronisedRadioLinkReconfigurationCancellation id-synchronisedRadioLinkReconfigurationCommit id-synchronisedRadioLinkReconfigurationPreparation id-unSynchronisedRadioLinkReconfiguration id-uplinkSignallingTransfer id-commonMeasurementFailure id-commonMeasurementInitiation id-commonMeasurementReporting id-commonMeasurementTermination id-informationExchangeFailure id-informationExchangeInitiation id-informationReporting id-informationExchangeTermination id-reset id-radioLinkActivation id-gERANuplinkSignallingTransfer id-radioLinkParameterUpdate id-uEMeasurementFailure id-uEMeasurementInitiation id-uEMeasurementReporting id-uEMeasurementTermination id-iurDeactivateTrace id-iurInvokeTrace id-mBMSAttach id-mBMSDetach id-directInformationTransfer id-enhancedRelocation id-enhancedRelocationCancel id-enhancedRelocationSignallingTransfer id-enhancedRelocationRelease id-mBSFNMCCHInformation id-secondaryULFrequencyReporting id-secondaryULFrequencyUpdate id-informationTransferControl id-enhancedRelocationResourceAllocation id-enhancedRelocationResourceRelease ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode ProcedureCode

1128
::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 14 34 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 35 36 37 38 39 40 41 42 43 44 45 46 48 49 50 51 52 53 54 55 56 60 61

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- Lists --- **************************************************************

3GPP

Release 11
maxCellSIB11OrSIB12 maxCellsMeas maxRateMatching maxNoOfDSCHs maxNoOfDSCHsLCR maxNoOfRB maxNoOfUSCHs maxNoOfUSCHsLCR maxNrOfTFCs maxNrOfTFs maxNrOfCCTrCHs maxNrOfCCTrCHsLCR maxNrOfDCHs maxNrOfDL-Codes maxNrOfDPCHs maxNrOfDPCHsPerRL-1 maxNrOfDPCHsLCR maxNrOfDPCHsLCRPerRL-1 maxNrOfDPCHs768 maxNrOfDPCHs768PerRL-1 maxNrOfErrors maxNrOfMACcshSDU-Length maxNrOfMBMSServices maxNrOfActiveMBMSServices maxNrOfPoints maxNrOfRLs maxNrOfRLSets maxNrOfRLSets-1 maxNrOfRLs-1 maxNrOfRLs-2 maxNrOfUEs maxNrOfULTs maxNrOfULTsLCR maxNrOfDLTs maxNrOfDLTsLCR maxRNCinURA-1 maxTTI-Count maxCTFC maxNrOfNeighbouringRNCs maxNrOfFDDNeighboursPerRNC maxNrOfGSMNeighboursPerRNC maxNrOfTDDNeighboursPerRNC maxNrOfFACHs maxNrOfLCRTDDNeighboursPerRNC maxIBSEG maxNrOfSCCPCHs maxNrOfSCCPCHs768 maxTGPS maxNrOfTS maxNrOfLevels maxNrOfTsLCR 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 ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::=

1129
32 8 256 10 10 32 10 10 1024 32 16 16 128 8 240 239 -- maxNrofCCTrCH*maxNrOfULTs-1 240 95 -- maxNrofCCTrCH*maxNrOfULTsLCR-1 480 479 256 16 128 256 15 16 maxNrOfRLs 15 -- maxNrOfRLSets 1 15 -- maxNrOfRLs 1 14 -- maxNrOfRLs 2 4096 15 6 15 6 15 4 16777215 10 256 256 256 8 256 16 8 16 6 15 256 6

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
maxNoSat maxNoGPSTypes maxNrOfMeasNCell maxNrOfMeasNCell-1 maxResetContext maxResetContextGroup maxNrOfHARQProc maxNrOfHSSCCHCodes maxNrOfHSSICHs maxNrOfHSSICHs-1 maxNrOfMACdFlows maxNrOfMACdFlows-1 maxNrOfMACdPDUSize maxNrOfPDUIndexes maxNrOfPDUIndexes-1 maxNrOfPrioQueues maxNrOfPrioQueues-1 maxNrOfSNAs maxNrOfSatAlmanac-maxNoSat maxNrOfGERANSI maxNrOfInterfaces maxNrofSigSeqERGHICH-1 maxNrOfAddFreq maxNrOfCellsPerFreq maxNrOfEDCHMACdFlows-1 maxNrOfEDCH-HARQ-PO-QUANTSTEPs maxNrOfEDPCCH-PO-QUANTSTEPs maxNrOfEDCHHARQProcesses2msEDCH maxNrOfBits-MACe-PDU-non-scheduled maxNrOfRefETFCIs maxNrOfRefETFCI-PO-QUANTSTEPs maxNrOfEDCHMACdFlows maxNoOfLogicalChannels maxNrOfRefBetas maxNrOfEAGCHCodes maxNrOfHS-DSCHTBSs maxNrOfHS-DSCHTBSs-HS-SCCHless maxHS-PDSCHCodeNrComp-1 maxNrOfEHICHCodes maxGANSSSat maxNoGANSS maxSgnType maxNrOfBroadcastPLMNs maxHSDPAFrequency maxHSDPAFrequency-1 maxFrequencyinCell maxFrequencyinCell-1 maxGANSSSatAlmanac maxGANSSClockMod maxNrOfEDCHRLs maxEARFCN 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 ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::=

1130
16 8 96 95 -- maxNrOfMeasNCell 1 250 32 8 4 4 3 8 7 -- maxNrOfMACdFlows 1 32 8 7 -- maxNrOfPDUIndexes 1 8 7 -- maxNrOfPrioQueues 1 65536 16 8 16 39 8 65536 7 6 8 8 19982 8 29 8 16 -- only maximum 15 can be used 8 4 90 4 15 4 64 8 8 5 8 7 12 11 36 4 4 65535

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
maxNrOfEUTRANeighboursPerRNC INTEGER maxNrOfMCCHMessages INTEGER maxNrOfMBMSL3 INTEGER maxNrOfEDCHMACdFlowsLCR INTEGER maxNrOfEDCHMACdFlowsLCR-1 INTEGER maxNrOfPreconfiguredNeighbours INTEGER maxNrOfHSDSCH-1 INTEGER maxNrOfHSDSCH INTEGER maxGANSS-1 INTEGER maxlengthMBMSconcatservlists INTEGER maxNoOfTBSs-Mapping-HS-DSCH-SPS INTEGER maxNoOfTBSs-Mapping-HS-DSCH-SPS-1 INTEGER maxNoOfHS-DSCH-TBSsLCR INTEGER maxNoOfRepetition-Period-LCR INTEGER maxNoOfRepetitionPeriod-SPS-LCR-1 INTEGER maxNoOf-HS-SICH-SPS INTEGER maxNoOf-HS-SICH-SPS-1 INTEGER maxNoOfNon-HS-SCCH-Assosiated-HS-SICH INTEGER maxNrOfEDCH-1 INTEGER maxNrOfDCHMeasurementOccasionPatternSequence maxNrOfULCarriersLCR-1 INTEGER maxNrOfCellIds INTEGER maxNrOfRAIs INTEGER maxNrOfLAIs INTEGER maxNrOfExtendedNeighbouringRNCs INTEGER maxNoOfGsmCell INTEGER maxNrOfANRCells INTEGER maxFreqBandsTDD INTEGER ::= 256 ::= 5 ::= 64 ::= 256 ::= 255 ::= 256 ::= 32 ::= 33 ::= 7 ::= 96 ::= 4 ::= 3 ::= 64 ::= 4 ::= 3 ::= 4 ::= 3 ::= 4 ::= 32 INTEGER ::= 6 ::= 5 ::= 32 ::= 8 ::= 8 ::= 64 ::= 128 ::= 256 ::= 16

1131

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- IEs --- ************************************************************** id-AllowedQueuingTime id-Allowed-Rate-Information id-AntennaColocationIndicator id-BindingID id-C-ID id-C-RNTI id-Cell-Capacity-Class-Value id-CFN id-CN-CS-DomainIdentifier id-CN-PS-DomainIdentifier id-Cause id-CoverageIndicator id-CriticalityDiagnostics id-ContextInfoItem-Reset id-ContextGroupInfoItem-Reset ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 4 42 309 5 6 7 303 8 9 10 11 310 20 211 515

3GPP

Release 11
id-D-RNTI id-D-RNTI-ReleaseIndication id-DCHs-to-Add-FDD id-DCHs-to-Add-TDD id-DCH-DeleteList-RL-ReconfPrepFDD id-DCH-DeleteList-RL-ReconfPrepTDD id-DCH-DeleteList-RL-ReconfRqstFDD id-DCH-DeleteList-RL-ReconfRqstTDD id-DCH-FDD-Information id-DCH-TDD-Information id-FDD-DCHs-to-Modify id-TDD-DCHs-to-Modify id-DCH-InformationResponse id-DCH-Rate-InformationItem-RL-CongestInd id-DL-CCTrCH-InformationAddItem-RL-ReconfPrepTDD id-DL-CCTrCH-InformationListIE-RL-ReconfReadyTDD id-DL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD id-DL-CCTrCH-InformationItem-RL-SetupRqstTDD id-DL-CCTrCH-InformationListIE-PhyChReconfRqstTDD id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD id-DL-CCTrCH-InformationAddList-RL-ReconfPrepTDD id-DL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD id-DL-CCTrCH-InformationList-RL-SetupRqstTDD id-FDD-DL-CodeInformation id-DL-DPCH-Information-RL-ReconfPrepFDD id-DL-DPCH-Information-RL-SetupRqstFDD id-DL-DPCH-Information-RL-ReconfRqstFDD id-DL-DPCH-InformationItem-PhyChReconfRqstTDD id-DL-DPCH-InformationItem-RL-AdditionRspTDD id-DL-DPCH-InformationItem-RL-SetupRspTDD id-DL-DPCH-TimingAdjustment id-DLReferencePower id-DLReferencePowerList-DL-PC-Rqst id-DL-ReferencePowerInformation-DL-PC-Rqst id-DPC-Mode id-DRXCycleLengthCoefficient id-DedicatedMeasurementObjectType-DM-Fail-Ind id-DedicatedMeasurementObjectType-DM-Fail id-DedicatedMeasurementObjectType-DM-Rprt id-DedicatedMeasurementObjectType-DM-Rqst id-DedicatedMeasurementObjectType-DM-Rsp id-DedicatedMeasurementType id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspFDD id-FACH-InfoForUESelectedS-CCPCH-CTCH-ResourceRspTDD id-Guaranteed-Rate-Information id-IMSI id-HCS-Prio id-L3-Information id-AdjustmentPeriod id-MaxAdjustmentStep

1132
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 21 22 26 27 30 31 32 33 34 35 39 40 43 38 44 45 46 47 48 49 50 51 52 53 54 59 60 61 62 63 64 278 67 68 69 12 70 470 471 71 72 73 74 82 83 41 84 311 85 90 91

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-MeasurementFilterCoefficient id-MessageStructure id-MeasurementID id-Neighbouring-GSM-CellInformation id-Neighbouring-UMTS-CellInformationItem id-NRT-Load-Information-Value id-NRT-Load-Information-Value-IncrDecrThres id-PagingArea-PagingRqst id-FACH-FlowControlInformation id-PartialReportingIndicator id-Permanent-NAS-UE-Identity id-PowerAdjustmentType id-RANAP-RelocationInformation id-RL-Information-PhyChReconfRqstFDD id-RL-Information-PhyChReconfRqstTDD id-RL-Information-RL-AdditionRqstFDD id-RL-Information-RL-AdditionRqstTDD id-RL-Information-RL-DeletionRqst id-RL-Information-RL-FailureInd id-RL-Information-RL-ReconfPrepFDD id-RL-Information-RL-RestoreInd id-RL-Information-RL-SetupRqstFDD id-RL-Information-RL-SetupRqstTDD id-RL-InformationItem-RL-CongestInd id-RL-InformationItem-DM-Rprt id-RL-InformationItem-DM-Rqst id-RL-InformationItem-DM-Rsp id-RL-InformationItem-RL-PreemptRequiredInd id-RL-InformationItem-RL-SetupRqstFDD id-RL-InformationList-RL-CongestInd id-RL-InformationList-RL-AdditionRqstFDD id-RL-InformationList-RL-DeletionRqst id-RL-InformationList-RL-PreemptRequiredInd id-RL-InformationList-RL-ReconfPrepFDD id-RL-InformationResponse-RL-AdditionRspTDD id-RL-InformationResponse-RL-ReconfReadyTDD id-RL-InformationResponse-RL-SetupRspTDD id-RL-InformationResponseItem-RL-AdditionRspFDD id-RL-InformationResponseItem-RL-ReconfReadyFDD id-RL-InformationResponseItem-RL-ReconfRspFDD id-RL-InformationResponseItem-RL-SetupRspFDD id-RL-InformationResponseList-RL-AdditionRspFDD id-RL-InformationResponseList-RL-ReconfReadyFDD id-RL-InformationResponseList-RL-ReconfRspFDD id-RL-InformationResponse-RL-ReconfRspTDD id-RL-InformationResponseList-RL-SetupRspFDD id-RL-ReconfigurationFailure-RL-ReconfFail id-RL-Set-InformationItem-DM-Rprt id-RL-Set-InformationItem-DM-Rqst id-RL-Set-InformationItem-DM-Rsp id-RL-Set-Information-RL-FailureInd

1133
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 92 57 93 13 95 305 306 102 103 472 17 107 109 110 111 112 113 114 115 116 117 118 119 55 120 121 122 2 123 56 124 125 1 126 127 128 129 130 131 132 133 134 135 136 28 137 141 143 144 145 146

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-RL-Set-Information-RL-RestoreInd id-RL-Set-Successful-InformationItem-DM-Fail id-RL-Set-Unsuccessful-InformationItem-DM-Fail id-RL-Set-Unsuccessful-InformationItem-DM-Fail-Ind id-RL-Successful-InformationItem-DM-Fail id-RL-Unsuccessful-InformationItem-DM-Fail id-RL-Unsuccessful-InformationItem-DM-Fail-Ind id-ReportCharacteristics id-Reporting-Object-RL-FailureInd id-Reporing-Object-RL-RestoreInd id-RT-Load-Value id-RT-Load-Value-IncrDecrThres id-S-RNTI id-ResetIndicator id-RNC-ID id-SAI id-SRNC-ID id-SuccessfulRL-InformationResponse-RL-AdditionFailureFDD id-SuccessfulRL-InformationResponse-RL-SetupFailureFDD id-TransportBearerID id-TransportBearerRequestIndicator id-TransportLayerAddress id-TypeOfError id-UC-ID id-UL-CCTrCH-AddInformation-RL-ReconfPrepTDD id-UL-CCTrCH-InformationAddList-RL-ReconfPrepTDD id-UL-CCTrCH-InformationItem-RL-SetupRqstTDD id-UL-CCTrCH-InformationList-RL-SetupRqstTDD id-UL-CCTrCH-InformationListIE-PhyChReconfRqstTDD id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD id-UL-CCTrCH-InformationListIE-RL-ReconfReadyTDD id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD id-UL-DPCH-Information-RL-ReconfPrepFDD id-UL-DPCH-Information-RL-ReconfRqstFDD id-UL-DPCH-Information-RL-SetupRqstFDD id-UL-DPCH-InformationItem-PhyChReconfRqstTDD id-UL-DPCH-InformationItem-RL-AdditionRspTDD id-UL-DPCH-InformationItem-RL-SetupRspTDD id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD id-UL-SIRTarget id-URA-Information id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureFDD id-UnsuccessfulRL-InformationResponse-RL-SetupFailureFDD id-UnsuccessfulRL-InformationResponse-RL-SetupFailureTDD id-Active-Pattern-Sequence-Information id-AdjustmentRatio id-CauseLevel-RL-AdditionFailureFDD id-CauseLevel-RL-AdditionFailureTDD id-CauseLevel-RL-ReconfFailure id-CauseLevel-RL-SetupFailureFDD id-CauseLevel-RL-SetupFailureTDD

1134
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 147 473 474 475 476 477 478 152 153 154 307 308 155 244 245 156 157 159 160 163 164 165 140 166 167 169 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 188 189 190 193 194 197 198 199 200 201

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-DL-CCTrCH-InformationDeleteItem-RL-ReconfPrepTDD id-DL-CCTrCH-InformationModifyItem-RL-ReconfPrepTDD id-DL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD id-DL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD id-DL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD id-DL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD id-DL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD id-DL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD id-DSCHs-to-Add-TDD id-Unused-ProtocolIE-ID-216 id-DSCH-DeleteList-RL-ReconfPrepTDD id-Unused-ProtocolIE-ID-218 id-Unused-ProtocolIE-ID-219 id-DSCH-InformationListIE-RL-AdditionRspTDD id-DSCH-InformationListIEs-RL-SetupRspTDD id-DSCH-TDD-Information id-Unused-ProtocolIE-ID-223 id-Unused-ProtocolIE-ID-226 id-DSCH-ModifyList-RL-ReconfPrepTDD id-Unused-ProtocolIE-ID-228 id-Unused-ProtocolIE-ID-324 id-Unused-ProtocolIE-ID-229 id-DSCHToBeAddedOrModifiedList-RL-ReconfReadyTDD id-Unused-ProtocolIE-ID-29 id-Unused-ProtocolIE-ID-225 id-GA-Cell id-GA-CellAdditionalShapes id-Unused-ProtocolIE-ID-246 id-Transmission-Gap-Pattern-Sequence-Information id-UL-CCTrCH-DeleteInformation-RL-ReconfPrepTDD id-UL-CCTrCH-ModifyInformation-RL-ReconfPrepTDD id-UL-CCTrCH-InformationModifyItem-RL-ReconfRqstTDD id-UL-CCTrCH-InformationDeleteList-RL-ReconfPrepTDD id-UL-CCTrCH-InformationModifyList-RL-ReconfPrepTDD id-UL-CCTrCH-InformationModifyList-RL-ReconfRqstTDD id-UL-CCTrCH-InformationDeleteItem-RL-ReconfRqstTDD id-UL-CCTrCH-InformationDeleteList-RL-ReconfRqstTDD id-UL-DPCH-InformationDeleteListIE-RL-ReconfReadyTDD id-UL-DPCH-InformationModifyListIE-RL-ReconfReadyTDD id-UnsuccessfulRL-InformationResponse-RL-AdditionFailureTDD id-USCHs-to-Add id-USCH-DeleteList-RL-ReconfPrepTDD id-USCH-InformationListIE-RL-AdditionRspTDD id-USCH-InformationListIEs-RL-SetupRspTDD id-USCH-Information id-USCH-ModifyList-RL-ReconfPrepTDD id-USCHToBeAddedOrModifiedList-RL-ReconfReadyTDD id-DL-Physical-Channel-Information-RL-SetupRqstTDD id-UL-Physical-Channel-Information-RL-SetupRqstTDD id-ClosedLoopMode1-SupportIndicator

1135
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 205 206 207 208 209 210 212 213 214 215 216 217 218 219 220 221 222 223 226 227 228 324 229 230 29 225 232 3 246 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-Unused-ProtocolIE-ID-277 id-STTD-SupportIndicator id-CFNReportingIndicator id-CNOriginatedPage-PagingRqst id-InnerLoopDLPCStatus id-PropagationDelay id-RxTimingDeviationForTA id-timeSlot-ISCP id-CCTrCH-InformationItem-RL-FailureInd id-CCTrCH-InformationItem-RL-RestoreInd id-CommonMeasurementAccuracy id-CommonMeasurementObjectType-CM-Rprt id-CommonMeasurementObjectType-CM-Rqst id-CommonMeasurementObjectType-CM-Rsp id-CommonMeasurementType id-CongestionCause id-SFN id-SFNReportingIndicator id-InformationExchangeID id-InformationExchangeObjectType-InfEx-Rprt id-InformationExchangeObjectType-InfEx-Rqst id-InformationExchangeObjectType-InfEx-Rsp id-InformationReportCharacteristics id-InformationType id-neighbouring-LCR-TDD-CellInformation id-DL-Timeslot-ISCP-LCR-Information-RL-SetupRqstTDD id-RL-LCR-InformationResponse-RL-SetupRspTDD id-UL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD id-UL-DPCH-LCR-InformationItem-RL-SetupRspTDD id-DL-CCTrCH-LCR-InformationListIE-RL-SetupRspTDD id-DL-DPCH-LCR-InformationItem-RL-SetupRspTDD id-DSCH-LCR-InformationListIEs-RL-SetupRspTDD id-USCH-LCR-InformationListIEs-RL-SetupRspTDD id-DL-Timeslot-ISCP-LCR-Information-RL-AdditionRqstTDD id-RL-LCR-InformationResponse-RL-AdditionRspTDD id-UL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD id-UL-DPCH-LCR-InformationItem-RL-AdditionRspTDD id-DL-CCTrCH-LCR-InformationListIE-RL-AdditionRspTDD id-DL-DPCH-LCR-InformationItem-RL-AdditionRspTDD id-DSCH-LCR-InformationListIEs-RL-AdditionRspTDD id-USCH-LCR-InformationListIEs-RL-AdditionRspTDD id-UL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD id-UL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD id-DL-DPCH-LCR-InformationAddListIE-RL-ReconfReadyTDD id-DL-Timeslot-LCR-InformationModifyList-RL-ReconfReadyTDD id-UL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD id-DL-Timeslot-LCR-InformationList-PhyChReconfRqstTDD id-timeSlot-ISCP-LCR-List-DL-PC-Rqst-TDD id-TSTD-Support-Indicator-RL-SetupRqstTDD id-RestrictionStateIndicator id-Load-Value

1136
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 277 279 14 23 24 25 36 37 15 16 280 281 282 283 284 18 285 286 287 288 289 290 291 292 58 65 66 75 76 77 78 79 80 81 86 87 88 89 94 96 97 98 100 101 104 105 106 138 139 142 233

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-Load-Value-IncrDecrThres id-OnModification id-Received-Total-Wideband-Power-Value id-Received-Total-Wideband-Power-Value-IncrDecrThres id-SFNSFNMeasurementThresholdInformation id-Transmitted-Carrier-Power-Value id-Transmitted-Carrier-Power-Value-IncrDecrThres id-TUTRANGPSMeasurementThresholdInformation id-UL-Timeslot-ISCP-Value id-UL-Timeslot-ISCP-Value-IncrDecrThres id-Rx-Timing-Deviation-Value-LCR id-DPC-Mode-Change-SupportIndicator id-Unused-ProtocolIE-ID-247 id-Unused-ProtocolIE-ID-295 id-PrimaryCCPCH-RSCP-RL-ReconfPrepTDD id-DL-TimeSlot-ISCP-Info-RL-ReconfPrepTDD id-DL-Timeslot-ISCP-LCR-Information-RL-ReconfPrepTDD id-DSCH-RNTI id-DL-PowerBalancing-Information id-DL-PowerBalancing-ActivationIndicator id-DL-PowerBalancing-UpdatedIndicator id-DL-ReferencePowerInformation id-Enhanced-PrimaryCPICH-EcNo id-IPDL-TDD-ParametersLCR id-CellCapabilityContainer-FDD id-CellCapabilityContainer-TDD id-CellCapabilityContainer-TDD-LCR id-RL-Specific-DCH-Info id-RL-ReconfigurationRequestFDD-RL-InformationList id-RL-ReconfigurationRequestFDD-RL-Information-IEs id-RL-ReconfigurationRequestTDD-RL-Information id-CommonTransportChannelResourcesInitialisationNotRequired id-DelayedActivation id-DelayedActivationList-RL-ActivationCmdFDD id-DelayedActivationInformation-RL-ActivationCmdFDD id-DelayedActivationList-RL-ActivationCmdTDD id-DelayedActivationInformation-RL-ActivationCmdTDD id-neighbouringTDDCellMeasurementInformationLCR id-UL-SIR-Target-CCTrCH-InformationItem-RL-SetupRspTDD id-UL-SIR-Target-CCTrCH-LCR-InformationItem-RL-SetupRspTDD id-PrimCCPCH-RSCP-DL-PC-RqstTDD id-HSDSCH-FDD-Information id-HSDSCH-FDD-Information-Response id-HSDSCH-FDD-Update-Information id-HSDSCH-Information-to-Modify id-HSDSCHMacdFlowSpecificInformationList-RL-PreemptRequiredInd id-HSDSCHMacdFlowSpecificInformationItem-RL-PreemptRequiredInd id-HSDSCH-RNTI id-HSDSCH-TDD-Information id-HSDSCH-TDD-Information-Response id-HSDSCH-TDD-Update-Information

1137
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 234 235 236 237 238 239 240 241 242 243 293 19 247 295 202 203 204 249 296 297 298 299 224 252 300 301 302 317 318 319 321 250 312 313 314 315 316 251 150 151 451 452 453 466 456 516 517 457 458 459 467

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-HSPDSCH-RL-ID id-HSDSCH-MACdFlows-to-Add id-HSDSCH-MACdFlows-to-Delete id-Angle-Of-Arrival-Value-LCR id-TrafficClass id-Unused-ProtocolIE-ID-248 id-Unused-ProtocolIE-ID-253 id-PDSCH-RL-ID id-TimeSlot-RL-SetupRspTDD id-GERAN-Cell-Capability id-GERAN-Classmark id-DSCH-InitialWindowSize id-UL-Synchronisation-Parameters-LCR id-SNA-Information id-MAChs-ResetIndicator id-TDD-DL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD id-TDD-UL-DPCH-TimeSlotFormatModifyItem-LCR-RL-ReconfReadyTDD id-TDD-TPC-UplinkStepSize-LCR-RL-SetupRqstTDD id-UL-CCTrCH-InformationList-RL-AdditionRqstTDD id-UL-CCTrCH-InformationItem-RL-AdditionRqstTDD id-DL-CCTrCH-InformationList-RL-AdditionRqstTDD id-DL-CCTrCH-InformationItem-RL-AdditionRqstTDD id-TDD-TPC-UplinkStepSize-InformationAdd-LCR-RL-ReconfPrepTDD id-TDD-TPC-UplinkStepSize-InformationModify-LCR-RL-ReconfPrepTDD id-TDD-TPC-DownlinkStepSize-InformationAdd-RL-ReconfPrepTDD id-TDD-TPC-DownlinkStepSize-InformationModify-RL-ReconfPrepTDD id-UL-TimingAdvanceCtrl-LCR id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD id-HSPDSCH-Timeslot-InformationListLCR-PhyChReconfRqstTDD id-HS-SICH-Reception-Quality id-HS-SICH-Reception-Quality-Measurement-Value id-HSSICH-Info-DM-Rprt id-HSSICH-Info-DM-Rqst id-HSSICH-Info-DM id-CCTrCH-Maximum-DL-Power-RL-SetupRspTDD id-CCTrCH-Minimum-DL-Power-RL-SetupRspTDD id-CCTrCH-Maximum-DL-Power-RL-AdditionRspTDD id-CCTrCH-Minimum-DL-Power-RL-AdditionRspTDD id-CCTrCH-Maximum-DL-Power-RL-ReconfReadyTDD id-CCTrCH-Minimum-DL-Power-RL-ReconfReadyTDD id-Maximum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD id-Minimum-DL-Power-TimeslotLCR-InformationModifyItem-RL-ReconfReadyTDD id-DL-CCTrCH-InformationList-RL-ReconfRspTDD id-DL-DPCH-InformationModifyItem-LCR-RL-ReconfRspTDD id-Maximum-DL-Power-TimeslotLCR-InformationItem id-Minimum-DL-Power-TimeslotLCR-InformationItem id-TDD-Support-8PSK id-TDD-maxNrDLPhysicalchannels id-ExtendedGSMCellIndividualOffset id-RL-ParameterUpdateIndicationFDD-RL-InformationList id-Primary-CPICH-Usage-For-Channel-Estimation

1138
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 463 531 532 148 158 248 253 323 325 468 469 480 464 479 465 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 518 519

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-Secondary-CPICH-Information id-Secondary-CPICH-Information-Change id-Unused-ProtocolIE-ID-522 id-Unused-ProtocolIE-ID-523 id-RL-ParameterUpdateIndicationFDD-RL-Information-Item id-Phase-Reference-Update-Indicator id-Unidirectional-DCH-Indicator id-RL-Information-RL-ReconfPrepTDD id-Multiple-RL-InformationResponse-RL-ReconfReadyTDD id-RL-ReconfigurationResponseTDD-RL-Information id-Satellite-Almanac-Information-ExtItem id-HSDSCH-Information-to-Modify-Unsynchronised id-TnlQos id-RTLoadValue id-NRTLoadInformationValue id-CellPortionID id-UpPTSInterferenceValue id-PrimaryCCPCH-RSCP-Delta id-UEMeasurementType id-UEMeasurementTimeslotInfoHCR id-UEMeasurementTimeslotInfoLCR id-UEMeasurementReportCharacteristics id-UEMeasurementParameterModAllow id-UEMeasurementValueInformation id-InterfacesToTraceItem id-ListOfInterfacesToTrace id-TraceDepth id-TraceRecordingSessionReference id-TraceReference id-UEIdentity id-NACC-Related-Data id-GSM-Cell-InfEx-Rqst id-MeasurementRecoveryBehavior id-MeasurementRecoveryReportingIndicator id-MeasurementRecoverySupportIndicator id-DL-DPCH-Power-Information-RL-ReconfPrepFDD id-F-DPCH-Information-RL-ReconfPrepFDD id-F-DPCH-Information-RL-SetupRqstFDD id-MBMS-Bearer-Service-List id-MBMS-Bearer-Service-List-InfEx-Rsp id-Active-MBMS-Bearer-ServiceFDD id-Active-MBMS-Bearer-ServiceTDD id-Old-URA-ID id-UE-State id-URA-ID id-HARQ-Preamble-Mode id-SynchronisationIndicator id-UL-DPDCHIndicatorEDCH id-EDPCH-Information id-RL-Specific-EDCH-Information id-EDCH-RL-Indication

1139
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 520 521 522 523 524 525 526 527 528 529 530 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 568 569 571 572 573 574 575 576

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-EDCH-FDD-Information id-EDCH-RLSet-Id id-Serving-EDCHRL-Id id-EDCH-FDD-DL-ControlChannelInformation id-EDCH-FDD-InformationResponse id-EDCH-MACdFlows-To-Add id-EDCH-FDD-Information-To-Modify id-EDCH-MACdFlows-To-Delete id-EDPCH-Information-RLReconfRequest-FDD id-EDCH-MacdFlowSpecificInformationList-RL-PreemptRequiredInd id-EDCH-MacdFlowSpecificInformationItem-RL-PreemptRequiredInd id-EDCH-MacdFlowSpecificInformationList-RL-CongestInd id-EDCH-MacdFlowSpecificInformationItem-RL-CongestInd id-MBMS-Bearer-Service-Full-Address id-Initial-DL-DPCH-TimingAdjustment id-Initial-DL-DPCH-TimingAdjustment-Allowed id-User-Plane-Congestion-Fields-Inclusion id-HARQ-Preamble-Mode-Activation-Indicator id-multiple-DedicatedMeasurementValueList-TDD-DM-Rsp id-multiple-DedicatedMeasurementValueList-LCR-TDD-DM-Rsp id-ProvidedInformation id-Active-MBMS-Bearer-ServiceFDD-PFL id-Active-MBMS-Bearer-ServiceTDD-PFL id-FrequencyBandIndicator id-Serving-cell-change-CFN id-HS-DSCH-serving-cell-change-information id-HS-DSCH-serving-cell-change-informationResponse id-E-DCH-Serving-cell-change-informationResponse id-secondary-LCR-CCPCH-Info-TDD id-E-DCH-FDD-Update-Information id-Inter-Frequency-Cell-List id-Inter-Frequency-Cell-Information id-multiple-HSSICHMeasurementValueList-TDD-DM-Rsp id-TDD-Support-PLCCH id-PLCCH-Information-UL-TimeslotLCR-Info id-PLCCH-Information-PhyChReconfRqstTDD id-TDD768-maxNrDLPhysicalchannelsTS id-RL-InformationResponse-RL-AdditionRspTDD768 id-UL-CCTrCH-InformationListIE-RL-AdditionRspTDD768 id-DL-CCTrCH-InformationListIE-RL-AdditionRspTDD768 id-UL-DPCH-InformationItem-RL-AdditionRspTDD768 id-DL-DPCH-InformationItem-RL-AdditionRspTDD768 id-UL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768 id-UL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768 id-DL-DPCH-InformationAddListIE-RL-ReconfReadyTDD768 id-DL-Timeslot-InformationModifyList-RL-ReconfReadyTDD768 id-secondary-CCPCH-Info-RL-ReconfReadyTDD768 id-hSSCCH-TDD-Specific-InfoList-Response768 id-hSPDSCH-TDD-Specific-InfoList-Response768 id-HSPDSCH-Timeslot-InformationList-PhyChReconfRqstTDD768 id-UL-Timeslot-InformationList-PhyChReconfRqstTDD768

1140
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-DL-Timeslot-InformationList-PhyChReconfRqstTDD768 id-CellCapabilityContainer-TDD768 id-multiple-DedicatedMeasurementValueList-TDD768-DM-Rsp id-neighbouringTDDCellMeasurementInformation768 id-UEMeasurementTimeslotInfo768 id-Rx-Timing-Deviation-Value-768 id-UEMeasurementValueTransmittedPowerList768 id-UEMeasurementValueTimeslotISCPList768 id-RL-InformationResponse-RL-SetupRspTDD768 id-UL-CCTrCH-InformationListIE-RL-SetupRspTDD768 id-DL-CCTrCH-InformationListIE-RL-SetupRspTDD768 id-UL-DPCH-InformationItem-RL-SetupRspTDD768 id-DL-DPCH-InformationItem-RL-SetupRspTDD768 id-TDD768-minimumSpreadingFactor-UL id-TDD768-minimumSpreadingFactor-DL id-TDD768-maxNrDLPhysicalchannels id-DL-DPCH-InformationDeleteList768-RL-ReconfReadyTDD id-DPCH-ID768-DM-Rsp id-DPCH-ID768-DM-Rqst id-DPCH-ID768-DM-Rprt id-EDPCH-Information-RLAdditionReq-FDD id-HSDSCH-Configured-Indicator id-RxTimingDeviationForTAext id-RxTimingDeviationForTA768 id-Rx-Timing-Deviation-Value-ext id-E-DCH-PowerOffset-for-SchedulingInfo id-TrCH-SrcStatisticsDescr id-E-DCH-Information id-E-DCH-Serving-RL-ID id-E-DCH-Information-Reconfig id-E-DCH-Information-Response id-E-DCH-768-Information id-E-DCH-768-Information-Reconfig id-E-DCH-768-Information-Response id-ExtendedPropagationDelay id-Extended-Round-Trip-Time-Value id-AlternativeFormatReportingIndicator id-DCH-Indicator-For-E-DCH-HSDPA-Operation id-E-RGCH-E-HICH-ChannelisationCodeValidityIndicator id-E-DCH-Minimum-Set-E-TFCIValidityIndicator id-Fast-Reconfiguration-Mode id-Fast-Reconfiguration-Permission id-Continuous-Packet-Connectivity-DTX-DRX-Information id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information id-Continuous-Packet-Connectivity-HS-SCCH-Less-Information-Response id-CPC-Information id-MIMO-InformationResponse id-E-DCH-LCR-Information id-E-DCH-LCR-Information-Reconfig id-E-DCH-LCR-Information-Response id-HS-PDSCH-Code-Change-Grant

1141
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 675 677 678 679 680

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-HS-PDSCH-Code-Change-Indicator id-Extended-SRNC-ID id-Extended-RNC-ID id-SixtyfourQAM-DL-SupportIndicator id-Enhanced-FACH-Support-Indicator id-Enhanced-FACH-Information-ResponseFDD id-HSDSCH-MACdPDUSizeFormat id-MaximumMACdPDU-SizeExtended id-F-DPCH-SlotFormat id-F-DPCH-SlotFormatSupportRequest id-eDCH-MACdFlow-Retransmission-Timer-LCR id-Max-UE-DTX-Cycle id-GANSS-Common-Data id-GANSS-Information id-GANSS-Generic-Data id-TUTRANGANSSMeasurementThresholdInformation id-TUTRANGANSSMeasurementValueInformation id-Ext-Reference-E-TFCI-PO id-Ext-Max-Bits-MACe-PDU-non-scheduled id-HARQ-MemoryPartitioningInfoExtForMIMO id-MIMO-ActivationIndicator id-MIMO-Mode-Indicator id-MIMO-N-M-Ratio id-TransportBearerNotSetupIndicator id-TransportBearerNotRequestedIndicator id-PowerControlGAP id-UARFCNforNt id-LCRTDD-uplink-Physical-Channel-Capability id-number-Of-Supported-Carriers id-HSSICH-SIRTarget id-HSSICH-TPC-StepSize id-tSN-Length id-HS-SICH-ID-Extension id-HSSICH-Info-DM-Rqst-Extension id-multipleFreq-HSPDSCH-InformationList-ResponseTDDLCR id-multicarrier-number id-UPPCHPositionLCR id-UpPCH-InformationList-LCRTDD id-UpPCH-InformationItem-LCRTDD id-Multiple-PLMN-List id-UE-Capabilities-Info id-FrameOffset id-ChipOffset id-Enhanced-PCH-Capability id-SixteenQAM-UL-Operation-Indicator id-E-TFCI-Boost-Information id-SixtyfourQAM-UsageAllowedIndicator id-SixtyfourQAM-DL-UsageIndicator id-Default-Serving-Grant-in-DTX-Cycle2 id-E-DPDCH-PowerInterpolation id-Extended-E-DCH-LCRTDD-PhysicalLayerCategory

1142
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 681 682 683 684 685 686 690 691 692 693 694 695 699 700 701 702 703 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-E-DCH-MACdPDUSizeFormat id-Continuous-Packet-Connectivity-HS-SCCH-Less-Deactivate-Indicator id-E-DCH-DL-Control-Channel-Change-Information id-E-DCH-DL-Control-Channel-Grant-Information id-MaximumNumber-Of-Retransmission-For-SchedulingInfo-LCRTDD id-E-DCH-RetransmissionTimer-For-SchedulingInfo-LCRTDD id-E-PUCH-PowerControlGAP id-HSDSCH-TBSizeTableIndicator id-UE-with-enhanced-HS-SCCH-support-indicator id-DGANSS-Corrections-Req id-E-AGCH-Table-Choice id-RANAP-EnhancedRelocationInformationRequest id-RANAP-EnhancedRelocationInformationResponse id-Common-EDCH-MAC-d-Flow-Specific-InformationFDD id-Common-EDCH-Support-Indicator id-E-RNTI id-Released-CN-Domain id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rqst id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rsp id-MBMS-Bearer-Service-in-MBMS-Cell-InfEx-Rprt id-MBMS-Cell-InfEx-Rqst id-MBMS-Cell-InfEx-Rsp id-MBMS-Cell-InfEx-Rprt id-Counting-Information id-Transmission-Mode-Information id-MBMS-Neighbouring-Cell-Information id-MBMS-RLC-Sequence-Number-Information id-RLC-Sequence-Number id-Neighbouring-E-UTRA-CellInformation id-MBSFN-Cluster-Identity id-MCCH-Configuration-Info id-MCCH-Message-List id-MBSFN-Scheduling-Transmission-Time-Interval-Info-List id-GANSS-Time-ID id-GANSS-AddIonoModelReq id-GANSS-EarthOrientParaReq id-GANSS-AddNavigationModelsReq id-GANSS-AddUTCModelsReq id-GANSS-AuxInfoReq id-GANSS-SBAS-ID id-GANSS-ID id-GANSS-Additional-Ionospheric-Model id-GANSS-Earth-Orientation-Parameters id-GANSS-Additional-Time-Models id-GANSS-Additional-Navigation-Models id-GANSS-Additional-UTC-Models id-GANSS-Auxiliary-Information id-MinimumReducedE-DPDCH-GainFactor id-Enhanced-FACH-Information-ResponseLCR id-Common-EDCH-MAC-d-Flow-Specific-InformationLCR id-HSDSCH-PreconfigurationSetup

1143
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11
id-HSDSCH-PreconfigurationInfo id-NoOfTargetCellHS-SCCH-Order id-EnhancedHSServingCC-Abort id-Additional-HS-Cell-Information-RL-Setup id-Additional-HS-Cell-Information-Response id-Additional-HS-Cell-Information-RL-Addition id-Additional-HS-Cell-Change-Information-Response id-Additional-HS-Cell-Information-RL-Reconf-Prep id-Additional-HS-Cell-Information-RL-Reconf-Req id-Additional-HS-Cell-RL-Reconf-Response id-Additional-HS-Cell-Information-RL-Param-Upd id-Secondary-Serving-Cell-List id-MultiCarrier-HSDSCH-Physical-Layer-Category id-IdleIntervalInformation id-NeedforIdleInterval id-IdleIntervalConfigurationIndicator id-ContinuousPacketConnectivity-DRX-InformationLCR id-ContinuousPacketConnectivity-DRX-Information-ResponseLCR id-E-AGCH-UE-Inactivity-Monitor-Threshold id-CPC-InformationLCR id-E-DCH-Semi-PersistentScheduling-Information-LCR id-HS-DSCH-Semi-PersistentScheduling-Information-LCR id-HS-DSCH-Semi-PersistentScheduling-Information-ResponseLCR id-E-DCH-Semi-PersistentScheduling-Information-ResponseLCR id-MIMO-SFMode-For-HSPDSCHDualStream id-MIMO-SFMode-Supported-For-HSPDSCHDualStream id-MIMO-ReferenceSignal-InformationListLCR id-GANSS-alm-keplerianNAVAlmanac id-GANSS-alm-keplerianReducedAlmanac id-GANSS-alm-keplerianMidiAlmanac id-GANSS-alm-keplerianGLONASS id-GANSS-alm-ecefSBASAlmanac id-DL-RLC-PDU-Size-Format id-MACes-Maximum-Bitrate-LCR id-Single-Stream-MIMO-ActivationIndicator id-Single-Stream-MIMO-Mode-Indicator id-Dual-Band-Secondary-Serving-Cell-List id-UE-AggregateMaximumBitRate id-power-offset-for-S-CPICH-for-MIMO id-power-offset-for-S-CPICH-for-MIMO-Request-Indicator id-UE-SupportIndicatorExtension id-ActivationInformation id-CellPortionLCRID id-Additional-EDCH-Cell-Information-RL-Setup-Req id-Additional-EDCH-Cell-Information-Response id-Additional-EDCH-Cell-Information-RL-Add-Req id-Additional-EDCH-Cell-Information-Response-RLAdd id-Additional-EDCH-Cell-Information-RL-Reconf-Prep id-Additional-EDCH-Cell-Information-RL-Reconf-Req id-Additional-EDCH-Cell-Information-RL-Param-Upd id-Additional-EDCH-Preconfiguration-Information

1144
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 835 836 837 838 839 840 841 842 843 844

3GPP TS 25.423 V11.2.0 (2012-06)

3GPP

Release 11

1145
845 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 ::= 876 877 878 879 880 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 904 905

3GPP TS 25.423 V11.2.0 (2012-06)

id-MulticellEDCH-Information ProtocolIE-ID ::= id-Additional-EDCH-Cell-Information-ResponseRLReconf ProtocolIE-ID ::= id-EDCH-Indicator ProtocolIE-ID ::= id-DiversityMode ProtocolIE-ID ::= id-TransmitDiversityIndicator ProtocolIE-ID ::= id-NonCellSpecificTxDiversity ProtocolIE-ID ::= id-CellCapabilityContainerExtension-FDD ProtocolIE-ID ::= id-HSDSCH-Physical-Layer-Category ProtocolIE-ID ::= id-E-RNTI-For-FACH ProtocolIE-ID ::= id-H-RNTI-For-FACH ProtocolIE-ID ::= id-RNTI-Allocation-Indicator ProtocolIE-ID ::= id-UE-AggregateMaximumBitRate-Enforcement-Indicator ProtocolIE-ID ::= id-DCH-MeasurementOccasion-Information ProtocolIE-ID ::= id-DCH-MeasurementType-Indicator ProtocolIE-ID ::= id-Out-of-Sychronization-Window ProtocolIE-ID ::= id-MulticellEDCH-RL-SpecificInformation ProtocolIE-ID ::= id-DGNSS-ValidityPeriod ProtocolIE-ID ::= id-TS0-HS-PDSCH-Indication-LCR ProtocolIE-ID ::= id-UE-TS0-CapabilityLCR ProtocolIE-ID ::= id-Non-Serving-RL-Preconfig-Info ProtocolIE-ID ::= id-Non-Serving-RL-Preconfig-Setup ProtocolIE-ID ::= id-Non-Serving-RL-Preconfig-Removal ProtocolIE-ID ::= id-Additional-E-DCH-Non-Serving-RL-Preconfiguration-Setup ProtocolIE-ID ::= id-Additional-E-DCH-New-non-serving-RL-E-DCH-FDD-DL-Control-Channel-InfoList ProtocolIE-ID id-CellListValidityIndicator ProtocolIE-ID ::= id-completeAlmanacProvided ProtocolIE-ID ::= id-ganss-Delta-T ProtocolIE-ID ::= id-OrdinalNumberOfFrequency ProtocolIE-ID ::= id-Multicell-EDCH-Restriction ProtocolIE-ID ::= id-CellCapabilityContainerExtension-TDD-LCR ProtocolIE-ID ::= id-Multi-Carrier-EDCH-Setup ProtocolIE-ID ::= id-Multi-Carrier-EDCH-Reconfigure ProtocolIE-ID ::= id-Multi-Carrier-EDCH-Response ProtocolIE-ID ::= id-SNPL-Carrier-Group-Indicator ProtocolIE-ID ::= id-MU-MIMO-InformationLCR ProtocolIE-ID ::= id-MU-MIMO-Indicator ProtocolIE-ID ::= id-HS-SCCH-Inactivity-Threshold-for-UE-DRX-Cycle-LCR-Ext ProtocolIE-ID ::= id-Usefulness-Of-Battery-Optimization ProtocolIE-ID ::= id-Multi-Carrier-E-DCH-LCRTDD-PhysicalLayerCategory ProtocolIE-ID ::= id-Measurement-Power-Offset ProtocolIE-ID ::= id-MDT-Configuration ProtocolIE-ID ::= id-Neighbouring-UMTS-CellInformation-Ext ProtocolIE-ID ::= id-Neighbouring-UMTS-CellInformationExtensionItem ProtocolIE-ID ::= id-Control-Type-InformationTransferControlReq ProtocolIE-ID ::= id-UMTS-Cells-Info ProtocolIE-ID ::= id-ANRReportIndication ProtocolIE-ID ::= id-ANR-Cell-InfEx-Rqst ProtocolIE-ID ::= id-ANR-Cell-InfEx-Rsp ProtocolIE-ID ::= id-ANR-Cell-Information ProtocolIE-ID ::= id-Trace-Collection-Entity-IP-Address ProtocolIE-ID ::= id-Affected-HSDSCH-Serving-Cell-List ProtocolIE-ID ::=

3GPP

Release 11
id-UL-CLTD-Information id-UL-CLTD-Information-Reconf id-UL-CLTD-State-Update-Information id-Support-of-Dynamic-DTXDRX-Related-HS-SCCH-Order id-CPC-RecoveryReport id-FTPICH-Information id-FTPICH-Information-Reconf id-UE-RF-Band-CapabilityLCR id-Extended-S-RNTI id-ExtendedAffectedUEInformationForMBMS id-Extended-S-RNTI-Group id-SpeechVersion id-SourceID id-TargetID id-ClassmarkInformation2 id-ClassmarkInformation3 id-GSM-Cell-CM-Rqst id-Extension-CommonMeasurementObjectType-CM-Rprt id-Extension-CommonMeasurementObjectType-CM-Rqst id-Extension-CommonMeasurementObjectType-CM-Rsp id-Extension-FailureIndicationMeasurementList id-Extension-FailureMeasurementList id-Extension-TerminationMeasurementList id-GsmCellList-CM-Rprt id-GsmCellList-CM-Rqst id-GsmCellList-CM-Rsp id-LoadValue id-EventH END

1146
ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ProtocolIE-ID ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= 906 907 908 909 910 911 912 913 914 915 916 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064

3GPP TS 25.423 V11.2.0 (2012-06)

9.3.7 Container Definitions

-- ************************************************************** --- Container definitions --- ************************************************************** RNSAP-Containers { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) umts-Access (20) modules (3) rnsap (1) version1 (1) rnsap-Containers (5) DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ************************************************************** --- IE parameter types from other modules.

3GPP

Release 11
--- ************************************************************** IMPORTS maxPrivateIEs, maxProtocolExtensions, maxProtocolIEs, Criticality, Presence, PrivateIE-ID, ProtocolIE-ID FROM RNSAP-CommonDataTypes; -- ************************************************************** --- Class Definition for Protocol IEs --- ************************************************************** RNSAP-PROTOCOL-IES ::= CLASS { &id ProtocolIE-ID &criticality Criticality, &Value, &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality TYPE &Value PRESENCE &presence } UNIQUE,

1147

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- Class Definition for Protocol IEs --- ************************************************************** RNSAP-PROTOCOL-IES-PAIR ::= CLASS { &id ProtocolIE-ID &firstCriticality Criticality, &FirstValue, &secondCriticality Criticality, &SecondValue, &presence Presence } WITH SYNTAX { ID &id FIRST CRITICALITY &firstCriticality FIRST TYPE &FirstValue SECOND CRITICALITY &secondCriticality UNIQUE,

3GPP

Release 11
SECOND TYPE PRESENCE } -- ************************************************************** --- Class Definition for Protocol Extensions --- ************************************************************** RNSAP-PROTOCOL-EXTENSION ::= CLASS { &id ProtocolIE-ID &criticality Criticality, &Extension, &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality EXTENSION &Extension PRESENCE &presence } UNIQUE, &SecondValue &presence

1148

3GPP TS 25.423 V11.2.0 (2012-06)

-- ************************************************************** --- Class Definition for Private IEs --- ************************************************************** RNSAP-PRIVATE-IES ::= CLASS { &id PrivateIE-ID, &criticality Criticality, &Value, &presence Presence } WITH SYNTAX { ID &id CRITICALITY &criticality TYPE &Value PRESENCE &presence } -- ************************************************************** --- Container for Protocol IEs --- ************************************************************** ProtocolIE-Container {RNSAP-PROTOCOL-IES : IesSetParam} ::= SEQUENCE (SIZE (0..maxProtocolIEs)) OF ProtocolIE-Field {{IesSetParam}}

3GPP

Release 11
ProtocolIE-Single-Container {RNSAP-PROTOCOL-IES : IesSetParam} ::= ProtocolIE-Field {{IesSetParam}}

1149

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolIE-Field {RNSAP-PROTOCOL-IES : IesSetParam} ::= SEQUENCE { id RNSAP-PROTOCOL-IES.&id ({IesSetParam}), criticality RNSAP-PROTOCOL-IES.&criticality ({IesSetParam}{@id}), value RNSAP-PROTOCOL-IES.&Value ({IesSetParam}{@id}) } -- ************************************************************** --- Container for Protocol IE Pairs --- ************************************************************** ProtocolIE-ContainerPair {RNSAP-PROTOCOL-IES-PAIR : IesSetParam} ::= SEQUENCE (SIZE (0..maxProtocolIEs)) OF ProtocolIE-FieldPair {{IesSetParam}} ProtocolIE-FieldPair {RNSAP-PROTOCOL-IES-PAIR : IesSetParam} ::= SEQUENCE { id RNSAP-PROTOCOL-IES-PAIR.&id ({IesSetParam}), firstCriticality RNSAP-PROTOCOL-IES-PAIR.&firstCriticality ({IesSetParam}{@id}), firstValue RNSAP-PROTOCOL-IES-PAIR.&FirstValue ({IesSetParam}{@id}), secondCriticality RNSAP-PROTOCOL-IES-PAIR.&secondCriticality ({IesSetParam}{@id}), secondValue RNSAP-PROTOCOL-IES-PAIR.&SecondValue ({IesSetParam}{@id}) } -- ************************************************************** --- Container Lists for Protocol IE Containers --- ************************************************************** ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, RNSAP-PROTOCOL-IES : IesSetParam} ::= SEQUENCE (SIZE (lowerBound..upperBound)) OF ProtocolIE-Container {{IesSetParam}} ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, RNSAP-PROTOCOL-IES-PAIR : IesSetParam} ::= SEQUENCE (SIZE (lowerBound..upperBound)) OF ProtocolIE-ContainerPair {{IesSetParam}} -- ************************************************************** --- Container for Protocol Extensions --- ************************************************************** ProtocolExtensionContainer {RNSAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE (SIZE (1..maxProtocolExtensions)) OF ProtocolExtensionField {{ExtensionSetParam}}

3GPP

Release 11

1150

3GPP TS 25.423 V11.2.0 (2012-06)

ProtocolExtensionField {RNSAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { id RNSAP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), criticality RNSAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), extensionValue RNSAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) } -- ************************************************************** --- Container for Private IEs --- ************************************************************** PrivateIE-Container {RNSAP-PRIVATE-IES : IesSetParam} ::= SEQUENCE (SIZE (1..maxPrivateIEs)) OF PrivateIE-Field {{IesSetParam}} PrivateIE-Field {RNSAP-PRIVATE-IES : IesSetParam} ::= SEQUENCE { id RNSAP-PRIVATE-IES.&id ({IesSetParam}), criticality RNSAP-PRIVATE-IES.&criticality ({IesSetParam}{@id}), value RNSAP-PRIVATE-IES.&Value ({IesSetParam}{@id}) } END

3GPP

Release 11

1151

3GPP TS 25.423 V11.2.0 (2012-06)

9.4 Message Transfer Syntax

RNSAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Rec. X.691 [20].

9.5 Timers
T Preempt Specifies the maximum time that a DRNS may wait for pre-emption of resources for establishment or reconfiguration of Radio Links.

TRELOCprep Specifies the maximum time for the Enhanced Relocation procedure in the SRNC.

10 Handling of Unknown, Unforeseen and Erroneous Protocol Data

10.1 General
Protocol Error cases can be divided into three classes: 1. Transfer Syntax Error; 2. Abstract Syntax Error; 3. Logical Error. Protocol errors can occur in the following functions within a receiving node.

Figure 34: Protocol Errors in RNSAP The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1.

10.2

Transfer Syntax Error

A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. Examples for Transfer Syntax Errors are: Violation of value ranges in ASN.1 definition of messages. E.g.: If an IE has a defined value range of 0 to 10 (ASN.1: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error; Violation in list element constraints. E.g.: If a list is defined as containing 1 to 10 elements, and 12 elements will be received, than this case will be handled as a transfer syntax error;

3GPP

Release 11 1152 3GPP TS 25.423 V11.2.0 (2012-06) - Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message); Wrong order of elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message).

10.3

Abstract Syntax Error

10.3.1 General
An Abstract Syntax Error occurs when the receiving functional RNSAP entity: 1. Receives IEs or IE groups that cannot be understood (unknown IE id); 2 Receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); 3 Does not receive IEs or IE groups but according to the specified presence of the concerned object, the IEs or IE groups should have been present in the received message; 4 Receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; 5 receives IEs or IE groups but according to the conditional presence of the concerned object and the specified condition, the IEs or IE groups should not have been present in the received message. Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6.

10.3.2 Criticality Information

In the RNSAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: 1. Reject IE; 2. Ignore IE and Notify Sender; 3. Ignore IE. The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: 1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by a receiving entity (some may still remain unsupported). 2. EP: The comprehension of different Eps within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied.

3GPP

Release 11

1153

3GPP TS 25.423 V11.2.0 (2012-06)

10.3.3 Presence Information

For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, RNSAP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field f the concerned object of class RNSAP-PROTOCOL-IES, RNSAP-PROTOCOL-IES-PAIR, RNSAPPROTOCOL-EXTENSION or RNSAP-PRIVATE-IES. The presence field of the indicated classes supports three values: 1.Optional; 2.Conditional; 3.Mandatory. If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this erroneously present conditional IE/IE group.

10.3.4 Not Comprehended IE/IE Group

10.3.4.1 Procedure ID
The receiving node shall treat the different types of received criticality information of the Procedure ID according to the following: Reject IE: If a message is received with a Procedure ID marked with Reject IE which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure.

Ignore IE and Notify Sender: If a message is received with a Procedure ID marked with Ignore IE and Notify Sender which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure.

Ignore IE: If a message is received with a Procedure ID marked with Ignore IE which the receiving node does not comprehend, the receiving node shall ignore the procedure.

When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the Procedure ID IE, the Triggering Message IE, and the Procedure Criticality IE in the Criticality Diagnostics IE.

10.3.4.1A

Type of Message

When the receiving node cannot decode the Type of Message IE, the Error Indication procedure shall be initiated with an appropriate cause value.

10.3.4.2

IEs Other Than the Procedure ID and Type of Message

The receiving node shall treat the different types of received criticality information of an IE/IE group other than the Procedure ID IE and Type of Message IE according to the following: Reject IE: If a message initiating a procedure is received containing one or more IEs/IE groups marked with Reject IE which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be

3GPP

Release 11 1154 3GPP TS 25.423 V11.2.0 (2012-06) present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with Reject IE which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. If a response message is received containing one or more IEs/IE groups marked with Reject IE, that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.

Ignore IE and Notify Sender: If a message initiating a procedure is received containing one or more IEs/IE groups marked with Ignore IE and Notify Sender which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. If a message initiating a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with Ignore IE and Notify Sender which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. If a response message is received containing one or more IEs/IE groups marked with Ignore IE and Notify Sender which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure.

Ignore IE: If a message initiating a procedure is received containing one or more IEs/IE groups marked with Ignore IE which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. If a response message is received containing one or more IEs/IE groups marked with Ignore IE which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups.

When reporting not comprehended IEs/IE groups marked with Reject IE or Ignore IE and Notify Sender using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included. When reporting not comprehended IEs/IE groups marked with Reject IE or Ignore IE and Notify Sender using the Error Indication procedure, the Procedure ID IE, the Triggering Message IE, Procedure Criticality IE, the Transaction ID IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the not comprehended IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.

10.3.5 Missing IE or IE Group

The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of this specification used by the receiver:

3GPP

Release 11 Reject IE:

1155

3GPP TS 25.423 V11.2.0 (2012-06)

-If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality Reject IE; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. If a received message initiating a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality Reject IE, the receiving node shall terminate the procedure and initiate the Error Indication procedure. If a received response message is missing one or more IEs/IE groups with specified criticality Reject IE, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling.

Ignore IE and Notify Sender: If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality Ignore IE and Notify Sender, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. If a received message initiating a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality Ignore IE and Notify Sender, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. If a received response message is missing one or more IEs/IE groups with specified criticality Ignore IE and Notify Sender, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing.

Ignore IE: If a received message initiating a procedure is missing one or more IEs/IE groups with specified criticality Ignore IE, the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. If a received response message is missing one or more IEs/IE groups with specified criticality Ignore IE, the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message.

When reporting missing IEs/IE groups with specified criticality Reject IE or Ignore IE and Notify Sender using a response message defined for the procedure, the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included. When reporting missing IEs/IE groups with specified criticality Reject IE or Ignore IE and Notify Sender using the Error Indication procedure, the Procedure ID IE, the Triggering Message IE, Procedure Criticality IE, the Transaction ID IE, and the Information Element Criticality Diagnostics IE shall be included in the Criticality Diagnostics IE for each reported IE/IE group. In the Information Element Criticality Diagnostics IE the Repetition Number IE shall be included and in addition, if the missing IE/IE group is not at message hierarchy level 1 (top level; see annex C) also the Message Structure IE shall be included.

3GPP

Release 11

1156

3GPP TS 25.423 V11.2.0 (2012-06)

10.3.6 IEs or IE Groups Received in Wrong Order or With Too Many Occurrences or Erroneously Present
If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: If a message initiating a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value Abstract Syntax Error (Falsely Constructed Message) using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. -If a message initiating a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value Abstract Syntax Error (Falsely Constructed Message). -If a response message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node consider the procedure as unsuccessfully terminated and initiate local error handling. When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered.

10.4

Logical Error

Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IEs/IE groups containing the erroneous values. Class 1: Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: Protocol Causes: 1. Semantic Error; 2. Message not Compatible with Receiver State. Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error. Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. Class 2: Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The Procedure ID IE, the Triggering Message IE and the Transaction ID IE within the Criticality Diagnostics IE shall then be included in order to identify the message containing the logical error.

3GPP

Release 11

1157

3GPP TS 25.423 V11.2.0 (2012-06)

10.5

Exceptions

The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. In case a response message or ERROR INDICATION message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality ignore and notify have earlier occurred within the same procedure.

3GPP

Release 11

1158

3GPP TS 25.423 V11.2.0 (2012-06)

Annex A (normative): Allocation and Pre-emption of Radio Links in the DRNS A.1 Deriving Allocation Information for a Radio Link
A.1.1 Establishment of a New Radio Link
The Allocation Information for a Radio Link in the case of establishment of a new Radio Link shall be derived as follows: The latest received Allocation/Retention Priority IE for each transport channel shall be used. The Allocation/Retention Priority IE for a transport channel may have been received in a) the procedure that establishes the first Radio Link for the UE in the DRNS or b) a procedure adding or modifying the transport channel.

Note:

If the Priority Level IE in the Allocation/Retention Priority IE for all transport channels that are intended to use the Radio Link is set to no priority, the pre-emption capability of the Radio Link shall be set to shall not trigger pre-emption. If the Priority Level IE in the Allocation/Retention Priority IE for one or more of the transport channels that are intended to use the Radio Link is not set to no priority, the allocation priority and the pre-emption capability of the Radio Link shall be set according to the following: - The transport channels that have the Priority Level IE in the Allocation/Retention Priority IE set to no priority shall be excluded when setting the allocation priority and pre-emption capability of a Radio Link. - The allocation priority for a Radio Link shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all non excluded transport channels that are intended to use the Radio Link. - If all non-excluded transport channels that are intended to use a Radio Link to be established have the preemption capability, given by the Pre-emption Capability IE in the Allocation/Retention Priority IE, set to shall not trigger pre-emption, the pre-emption capability of the Radio Link shall be set to shall not trigger pre-emption. If one or more non-excluded transport channels that are intended to use the Radio Link to be established have the value of the Pre-emption Capability IE in the Allocation/Retention Priority IE set to may trigger pre-emption, the pre-emption capability of the Radio Link shall be set to may trigger preemption.

The derived allocation priority and pre-emption capability are only valid during this allocation/retention process.

A.1.2 Modification of an Existing Radio Link

The Allocation Information for a Radio Link in the case of modification of a Radio Link (addition or modification of transport channels using the Radio Link) shall be derived as follows: The latest received Allocation/Retention Priority IE for each transport channel shall be used. The Allocation/Retention Priority IE for a transport channel may have been received in a) the procedure that establishes the first Radio Link for the UE in the DRNS, b) a previous procedure adding or modifying the transport channel, or c) the current procedure adding or modifying the transport channel.

Note:

If the Priority Level IE in the Allocation/Retention Priority IE for all transport channels to be added or modified in the Radio Link is set to no priority, the pre-emption capability of the Radio Link to be modified shall be set to shall not trigger pre-emption.

3GPP

Release 11 1159 3GPP TS 25.423 V11.2.0 (2012-06) - If the Priority Level IE in the Allocation/Retention Priority IE for one or more of the transport channels to be added or modified in the Radio Link is not set to no priority, the allocation priority of and the pre-emption capability of the Radio Link to be modified shall be set according to the following: - The transport channels to be added or modified that have the Priority Level IE in the Allocation/Retention Priority IE set to no priority shall be excluded when setting the allocation priority and pre-emption capability of a Radio Link to be modified. - The allocation priority for a Radio Link to be modified shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all the non-excluded transport channels that are to be added or modified. - If all non-excluded transport channels that are to be added or modified in the Radio Link have the preemption capability, given by the Pre-emption Capability IE in the Allocation/Retention Priority IE, set to shall not trigger pre-emption, the pre-emption capability of the Radio Link to be modified shall be set to shall not trigger pre-emption. If one or more of the non-excluded transport channels to be added or modified in the Radio Link have the value of the Pre-emption Capability IE in the Allocation/Retention Priority IE set to may trigger preemption, the pre-emption capability of the Radio Link to be modified shall be set to may trigger preemption. The derived allocation priority and pre-emption capability are only valid during this allocation/retention process.

A.2 Deriving Retention Information for a Radio Link

The Retention Information for an existing Radio Link shall be derived as follows: The latest received Allocation/Retention Priority IE for each transport channel shall be used. The Allocation/Retention Priority IE for a transport channel may have been received in a) the procedure that establishes the first Radio Link for the UE in the DRNS or b) a procedure adding or modifying the transport channel.

Note:

If the Priority Level IE in the Allocation/Retention Priority IE for one or more transport channels using the Radio Link is set to no priority, the pre-emption vulnerability of the Radio Link shall be set to not preemptable. If the Priority Level IE in the Allocation/Retention Priority IE for all the transport channels using the Radio Link is not set to no priority, the retention priority of the Radio Link and the pre-emption vulnerability of the Radio Link shall be set according to the following: - The retention priority for a Radio Link shall be set to highest priority level, given by the Priority Level IE in the Allocation/Retention Priority IE, for all transport channels that uses the Radio Link. - If all transport channels that uses the Radio Link have the pre-emption vulnerability, given by the Preemption Vulnerability IE in the Allocation/Retention Priority IE, set to pre-emptable, the pre-emption vulnerability of the Radio Link shall be set to pre-emptable. If one or more transport channels that uses the Radio Link have the value of the Pre-emption Vulnerability IE in the Allocation/Retention Priority IE set to not pre-emptable, the pre-emption vulnerability of the Radio Link shall be set to not pre-emptable.

The derived retention priority and pre-emption vulnerability are valid until they are changed, or until the Radio Link is deleted. When new transport channels are added to or deleted from the Radio Link or when existing transport channels are modified with regards to the Allocation/Retention Priority IE, the retention information shall be derived again according to above.

A.3 The Allocation/Retention Process

The DRNS shall establish or modify the resources for a Radio Link according to: The value of the Allocation Information (allocation priority and pre-emption capability) of the Radio to be established or modified. The Allocation Information is derived according to clause A.1.

3GPP

Release 11 1160 3GPP TS 25.423 V11.2.0 (2012-06) - The value of the Retention Information (retention priority and pre-emption vulnerability) of existing Radio Links. The Retention Information derived according to clause A.2. The resource situation in the DRNS.

Whilst the process and the extent of the pre-emption functionality is operator dependent, the pre-emption indicators (pre-emption capability and pre-emption vulnerability) shall be treated as follows: -. If the pre-emption capability for a Radio Link to be established or modified is set to may trigger preemption and the resource situation so requires, the DRNS may trigger the pre-emption process in clause A.4 to free resources for this allocation request. -. If the pre-emption capability for a Radio Link to be established or modified is set to shall not trigger pre-emption, then this allocation request shall not trigger the pre-emption process in clause A.4. -. If the pre-emption vulnerability for an existing Radio Link is set to pre-emptable, then this Radio Link shall be included in the pre-emption process in clause A.4. -. If the pre-emption vulnerability for an existing Radio Link is set to not pre-emptable, then this Radio Link shall not be included in the pre-emption process in clause A.4.

A.4 The Pre-emption Process

The pre-emption process shall only pre-empt Radio Links with lower retention priority than the allocation priority of the Radio Link to be established or modified. The Radio Links to be pre-empted shall be selected in ascending order of the retention priority. When the pre-emption process detects that one or more Radio Links have to be pre-empted to free resources for a Radio Link(s) to be established or modified, the DRNS shall initiate the Radio Link Pre-emption procedure for all the UE Contexts having Radio Links selected for pre-emption and start the TPreempt timer. When enough resources are freed to establish or modify the Radio Link(s) according to the request, the DRNS shall stop the TPreempt timer and complete the procedure that triggered the pre-emption process in accordance with the Successful Operation subclause of the procedure. If the TPreempt timer expires, the DRNS shall reject the procedure that triggered the pre-emption process and complete the procedure in accordance with the Unsuccessful Operation subclause of the procedure.

Annex B (informative): Measurement Reporting

When the Report Characteristics IE is set to Event A (figure B.1), the Measurement Reporting procedure is initiated when the measured entity rises above the requested threshold and stays there for the requested hysteresis time. If no hysteresis time is given, the value zero shall be used for the hysteresis time.

3GPP

Release 11

1161

3GPP TS 25.423 V11.2.0 (2012-06)

Figure B.1: Event A reporting with Hysteresis Time specified When the Report Characteristics IE is set to Event B (figure B.2), the Measurement Reporting procedure is initiated when the measured entity falls below the requested threshold and stays there for the requested hysteresis time. If no hysteresis time is given, the value zero shall be used for the hysteresis time.

Figure B.2: Event B reporting with Hysteresis Time specified When the Report Characteristics IE is set to Event C (figure B.3), the Measurement Reporting procedure is initiated always when the measured entity rises by an amount greater than the requested threshold within the requested time. The reporting in figure B.3 is initiated if the Rising Time T1 is less than the requested time.

3GPP

Release 11

1162

3GPP TS 25.423 V11.2.0 (2012-06)

Figure B.3: Event C reporting When the Report Characteristics IE is set to Event D (figure B.4), the Measurement Reporting procedure is initiated always when the measured entity falls by an amount greater than the requested threshold within the requested time. The reporting in figureB.4 is initiated if the Falling Time T1 is less than the requested time.

Figure B.4: Event D reporting

When the Report Characteristics IE is set to Event E (figure B.5), the Measurement Reporting procedure (Report A) is initiated always when the measured entity rises above the Measurement Threshold 1 and stays there for the Measurement Hysteresis Time (T1 in figure B.5). If Report Periodicity IE is provided DRNS shall also initiate Measurement Reporting procedure periodically. The periodic reporting continues although the measured entity falls below the Measurement Threshold 1 and is terminated by the Report B.

3GPP

Release 11 1163 3GPP TS 25.423 V11.2.0 (2012-06) When the Report A conditions have been met and the measured entity falls below the Measurement Threshold 2 and stays there for the Measurement Hysteresis Time (T1) the Measurement Reporting procedure (Report B) is initiated and the periodic reporting is terminated.

Figure B.5: Event E reporting with Hysteresis Time specified and Periodic Reporting requested When the Report Characteristics IE is set to Event F (figure B.6), the Measurement Reporting procedure (Report A) is initiated always when the measured entity falls below the Measurement Threshold 1 and stays there for the Measurement Hysteresis Time (T1 in figure B.6). If Report Periodicity IE is provided DRNS shall also initiate Measurement Reporting procedure periodically. The periodic reporting continues although the measured entity rises above the Measurement Threshold 1 and is terminated by the Report B. When the Report A conditions have been met and the measured entity rises above the Measurement Threshold 2 and stays there for the Measurement Hysteresis Time (T1) Measurement Reporting procedure (Report B) is initiated and the periodic reporting is terminated.

3GPP

Release 11

1164

3GPP TS 25.423 V11.2.0 (2012-06)

Figure B.6: Event F reporting with Hysteresis Time specified and Periodic Reporting requested When the Report Characteristics IE is set to Event H (figure B.7), the Measurement Reporting procedure (Report A) is initiated when the measurement value of measured entity rises above the Measurement Threshold 1 and stays above the threshold for the Measurement Hysteresis Time (T1 in figure B.7).] The measurement value of measured entity in Report A substitutes the Measurement Base value for the consequent measurement reporting. When the Report A conditions has been met and the measurement value of measured entity rises above or falls below the Measurement Base Value by Measurement Fluctuation Range (H1 in figure B.7), and stays there for the Measurement Hysteresis Time (Th in figure B.7) counting from the beginning of every Report Periodicity, the Measurement Reporting procedure (Report B or Report C) is initiated. The the measurement value of measured entity in (Report B or Report C) substitutes the Measurement Base value for the consequent measurement reporting. When the Report A conditions have been met and the measurement value of measured entity falls below the Measurement Threshold 2 and stays there for the Measurement Hysteresis Time (Th in figure B.7), the Measurement Reporting procedure (Report D) is initiated and the reporting is terminated.
Measured Entity

Th

- Measurement Hysteresis Time

H1 - Jit Threshold

Jit Threshold

H1 Measurement Base Value H1 Jit Threshold

Th
Jit Threshold Measurement ThreshHold 1

Measurement Base Value Jit Threshold

H1 H1 Jit Threshold

Th

H1

Measurement ThreshHold 2

Th
T0
Report A

Measurement Base Value H1 Jit Threshold

Th

Time

T1

T2

T3

T4

T5
Report B

T6

T7
Report C

T8

T9
Report D

Figure B.7: Event H reporting with Hysteresis Time specified and Periodic Reporting requested

3GPP

Release 11

1165

3GPP TS 25.423 V11.2.0 (2012-06)

Annex C (informative): Guidelines for Usage of the Criticality Diagnostics IE

C.1 EXAMPLE MESSAGE Layout
Assume the following message format:
IE/Group Name Presence Range IE Type and Referenc e Semantics Description Criticality Assigned Criticality reject reject reject ignore ignore ignore ignore and notify reject reject reject ignore and notify

Message Type Transaction ID A B >E >>F >>>G >>H >>>G >>G >>J >>>G C >K >>L >>>M D

M M M M 1..<maxE> 1..<maxF> 0..3, 1..<maxH> 0..3, M 1..<maxJ> 0..3, M 1..<maxK> 1..<maxL> O M

YES YES YES EACH EACH EACH EACH YES EACH YES EACH YES

reject

Note 1.

The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of ordinary ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Single-Container.

For the corresponding ASN.1 layout, see subclause C.4.

3GPP

Release 11

1166

3GPP TS 25.423 V11.2.0 (2012-06)

C.2 Example on a Received EXAMPLE MESSAGE

Assume further more that a received message based on the above tabular format is according to the figure below. Level 1 (top level) A B C D

Level 2

Level 3

Level 4

Legend:

1st repetition 2nd repetition Nth repetition

IE based on a protocol container, e.g., Protocol-Single-Container IE being an "ordinary" ASN.1 type

Figure C.1: Example of content of a received RNSAP message based on the EXAMPLE MESSAGE

3GPP

Release 11

1167

3GPP TS 25.423 V11.2.0 (2012-06)

C.3 Content of Criticality Diagnostics

C.3.1 Example 1

Figure C.2: Example of a received RNSAP message containing a not comprehended IE If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure C.2 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name IE Criticality IE ID Repetition Number Type of Error Value reject id-G 11 Comment Criticality for IE on the reported level, i.e. level 4. IE ID from the reported level, i.e. level 4. Repetition number on the reported level, i.e. level 4. (Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2).

not underst ood Message Structure, first repetition >IE ID id-B IE ID from level 1. Message Structure, second repetition >IE ID id-E IE ID from the lowest level above the reported level, i.e. level 2. >Repetition 3 Repetition number from the lowest level above the reported level, i.e. level 2. Number

Note 2. Note 3.

The IE J on level 3 cannot be included in the Message Structure IE since they have no criticality of their own. The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

3GPP

Release 11

1168

3GPP TS 25.423 V11.2.0 (2012-06)

C.3.2 Example 2

Figure C.3: Example of a received RNSAP message containing a not comprehended IE If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure C.3 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name IE Criticality IE ID Repetition Number Type of Error Value ignore and notify id-K 3 Comment Criticality for IE on the reported level, i.e. level 2. IE ID from the reported level, i.e. level 2. Repetition number on the reported level, i.e. level 2.

not underst ood Message Structure, first repetition >IE ID id-C IE ID from the lowest level above the reported level, i.e. level 1.

Note 4.

The IE L on level 3 cannot be reported individually included in the Message Structure IE since it has no criticality of its own.

3GPP

Release 11

1169

3GPP TS 25.423 V11.2.0 (2012-06)

C.3.3 Example 3

Figure C.4: Example of a received RNSAP message containing a not comprehended IE If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure C.4 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name IE Criticality IE ID Repetition Number Type of Error Value ignore and notify id-G 2 Comment Criticality for IE on the reported level, i.e. level 4. IE ID from the reported level, i.e. level 4. Repetition number on the reported level, i.e. level 4.

not underst ood Message Structure, first repetition >IE ID id-B IE ID from level 1. Message Structure, second repetition >IE ID id-E IE ID from level 2. >Repetition 3 Repetition number from level 2. Number Message Structure, third repetition >IE ID id-H IE ID from the lowest level above the reported level, i.e. level 3. >Repetition 1 Repetition number from the lowest level above the reported level, i.e. level 3. Number

Note 5.

The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3).

3GPP

Release 11

1170

3GPP TS 25.423 V11.2.0 (2012-06)

C.3.4 Example 4

Figure C.5: Example of a received RNSAP message containing a not comprehended IE If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure C.5 above, this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name IE Criticality IE ID Repetition Number Type of Error Value reject id-G 5 Comment Criticality for IE on the reported level, i.e. level 3. IE ID from the reported level, i.e. level 3. Repetition number on the reported level, i.e. level 3. (Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2).

not underst ood Message Structure, first repetition >IE ID id-B IE ID from level 1. Message Structure, second repetition >IE ID id-E IE ID from the lowest level above the reported level, i.e. level 2. >Repetition 3 Repetition number from the lowest level above the reported level, i.e. level 2. Number

Note 6.

The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

3GPP

Release 11

1171

3GPP TS 25.423 V11.2.0 (2012-06)

C.3.5 Example 5

Figure C.6: Example of a received RNSAP message with a missing IE If the instance marked as grey in the IE G in the IE E shown in the figure C.6 above, is missing this will be reported within the Information Element Criticality Diagnostics IE within the Criticality Diagnostics IE as follows:
IE name IE Criticality IE ID Repetition Number Value reject id-G 4 Comment Criticality for IE on the reported level, i.e. level 3. IE ID from the reported level, i.e. level 3. Repetition number up to the missing IE on the reported level, i.e. level 3. (Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence.

Type of Error missing Message Structure, first repetition >IE ID id-B IE ID from level 1. Message Structure, second repetition >IE ID id-E IE ID from the lowest level above the reported level, i.e. level 2. >Repetition 3 Repetition number from the lowest level above the reported level, i.e. level 2. Number

Note 7.

The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2).

C.4 ASN.1 of EXAMPLE MESSAGE

ExampleMessage ::= SEQUENCE { ProtocolIEs ProtocolIE-Container ProtocolExtensions ProtocolExtensionContainer ... } ExampleMessage-IEs RNSAP-PROTOCOL-IES ::= { { ID id-A CRITICALITY reject TYPE A { ID id-B CRITICALITY reject TYPE B { ID id-C CRITICALITY reject TYPE C { ID id-D CRITICALITY reject TYPE D {{ExampleMessage-Ies}}, {{ExampleMessage-Extensions}} OPTIONAL,

PRESENCE PRESENCE PRESENCE PRESENCE

mandatory} mandatory} mandatory} mandatory}

| | | ,

3GPP

Release 11
} ...

1172

3GPP TS 25.423 V11.2.0 (2012-06)

B ::= SEQUENCE { e iE-Extensions ... }

E-List, ProtocolExtensionContainer { {B-ExtIEs} }

OPTIONAL,

B-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Single-Container { {E-IEs} } E-Ies RNSAP-PROTOCOL-IES ::= { { ID id-E CRITICALITY ignore } E ::= SEQUENCE { f h g j iE-Extensions ... } TYPE E PRESENCE mandatory }

F-List, H-List, G-List1, J-List, ProtocolExtensionContainer { {E-ExtIEs} }

OPTIONAL,

E-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } F-List ::= SEQUENCE (SIZE (1..maxF)) OF F F ::= SEQUENCE { g iE-Extensions ... } F-ExtIEs ... } G-List2 OPTIONAL, ProtocolExtensionContainer { {F-ExtIEs} }

OPTIONAL,

RNSAP-PROTOCOL-EXTENSION ::= {

G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G2-IEs} } G2-IEs RNSAP-PROTOCOL-IES ::= { { ID id-G CRITICALITY ignore } TYPE G PRESENCE mandatory }

H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Single-Container { {H-IEs} } H-Ies RNSAP-PROTOCOL-IES ::= { { ID id-H CRITICALITY ignore } H ::= SEQUENCE { g iE-Extensions ... } TYPE H PRESENCE mandatory }

G-List3 OPTIONAL, ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL,

H-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G3-IEs} } G3-IEs RNSAP-PROTOCOL-IES ::= { { ID id-G CRITICALITY notify } TYPE G PRESENCE mandatory }

G-List1 ::= ProtocolIE-Single-Container { {G1-IEs} } G1-IEs RNSAP-PROTOCOL-IES ::= { { ID id-G CRITICALITY reject } TYPE G PRESENCE mandatory }

J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J

3GPP

Release 11
J ::= SEQUENCE { g iE-Extensions ... } J-ExtIEs ... }

1173
G-List4 OPTIONAL, ProtocolExtensionContainer { {J-ExtIEs} }

3GPP TS 25.423 V11.2.0 (2012-06)

OPTIONAL,

RNSAP-PROTOCOL-EXTENSION ::= {

G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G4-IEs} } G4-IEs RNSAP-PROTOCOL-IES ::= { { ID id-G CRITICALITY reject } C ::= SEQUENCE { k iE-Extensions ... } TYPE G PRESENCE mandatory }

K-List, ProtocolExtensionContainer { {C-ExtIEs} }

OPTIONAL,

C-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Single-Container { {K-IEs} } K-IEs RNSAP-PROTOCOL-IES ::= { { ID id-K CRITICALITY notify } K ::= SEQUENCE { l iE-Extensions ... } TYPE K PRESENCE mandatory }

L-List, ProtocolExtensionContainer { {K-ExtIEs} }

OPTIONAL,

K-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } L-List ::= SEQUENCE (SIZE (1..maxL)) OF L L ::= SEQUENCE { m iE-Extensions ... } M OPTIONAL, ProtocolExtensionContainer { {L-ExtIEs} }

OPTIONAL,

L-ExtIEs RNSAP-PROTOCOL-EXTENSION ::= { ... } ExampleMessage-Extensions RNSAP-PROTOCOL-EXTENSION ::= { ... }

3GPP

Release 11

1174

3GPP TS 25.423 V11.2.0 (2012-06)

Annex D (normative): DRNS Behaviour at SRNC or RNSAP Signalling Bearer Failure

This annex describes the DRNC actions in the event of SRNC or RNSAP Signalling Bearer failure when all or some of the UE Contexts related to the SRNC need to be removed in DRNC.

D.1 Detection of SRNC or RNSAP Signalling Bearer/Connection Failure

Termination of all or some of the UE Contexts in DRNC which are related to an SRNC may be triggered due to failure of SRNC, RNSAP Signalling Bearer or the Iur signalling connection of an UE(s).

D.1.1 Termination of all UE Contexts Related to a Specific SRNC

Termination of all UE Contexts in DRNC which are related to a specific SRNC is triggered if the RNSAP Signalling Bearer failure is detected by the RNSAP according to the procedure described in the sub-clause 4.5.1.5.1 of TS 25.420. By all UE Contexts, it means all Ues having dedicated and/or common channel resources.

D.1.2 Termination of Specific UE Context

Termination of a specific UE Context in DRNC is triggered for an UE which has dedicated transport channel resources according to the procedure described in the sub-clause 4.5.1.5.2 of TS 25.420.

D.2 DRNC Actions at UE Context Termination

When termination of the UE Context is required, the DRNC shall remove any common and/or dedicated radio resources related to the UE Context. The DRNC shall also initiate release of the dedicated or common user plane resources that were involved in these UE contexts. In addition, if it is possible the DRNC shall release the RRC connection.

3GPP

Release 11

1175

3GPP TS 25.423 V11.2.0 (2012-06)

Annex E (informative): Change History

3GPP

Release 11
TSG # 09/2009 45 45 45 45 46 46 46 46 46 46 46 46 46 46 46 46 46 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 04/2010 04/2010 04/2010 48 48 48 48 48 49 49 49 49 09/2010 49 49 50 50 50 50 50 50 50 50 SP-49 51 51 51 51 51 51 51 TSG Doc. RP-090777 RP-090774 RP-090772 RP-090773 RP-091188 RP-091187 RP-091186 RP-091182 RP-091180 RP-091181 RP-091182 RP-091179 RP-091179 RP-091186 RP-091187 RP-091179 RP-091186 RP-100215 RP-100219 RP-100215 RP-100219 RP-100218 RP-100215 RP-100220 RP-100230 RP-100217 RP-100230 RP-100230 RP-100229 RP-100218 RP-100230 RP-100216 RP-100199 RP-100229 RP-100224 RP-100221 CR 1521 1528 1529 1536 1540 1541 1542 1544 1551 1558 1560 1563 1567 1568 1571 1573 1574 1576 1577 1579 1581 1584 1586 1587 1588 1591 1592 1593 1594 1596 1597 1601 1604 1605 1606 1608 Rev 2 1 2 1 1 1 1 1 1 2

1176

3GPP TS 25.423 V11.2.0 (2012-06)

New 9.0.0 9.0.0 9.0.0 9.0.0 9.0.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.1 9.2.2 9.2.3 9.3.0 9.3.0 9.3.0 9.3.0 9.3.0 9.4.0 9.4.0 9.4.0 9.4.0 10.0.0 10.0.0 10.0.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0

1 1

1 2 3 2 1 1 1 2

RP-100592 RP-100593 RP-100594 RP-100591 RP-100545 RP-100904 RP-100909 RP-100905 RP-100904 RP-100911 RP-100910 RP-101275 RP-101274 RP-101277 RP-101269 RP-101269 RP-101271 RP-101275 RP-101275 SP-100629 RP-110222 RP-110224 RP-110225 RP-110224 RP-110228 RP-110230 RP-110226

1618 1622 1625 1629 1631 1633 1634 1637 1641 1635 1638 1642 1643 1644 1647 1650 1652 1657

1 2

1 2

2 1 2 2 2 1 1

1658 3 1660 1661 1662 1663 1664 1667 1669 1 1 1 1 5

Subject/Comment Release 9 version created based on v8.6.0 Introduction of UE AMBR concept in UMTS Introduction of TxAA extension for non-MIMO Ues Introduction of Dual-Band HSDPA Introduction of MIMO for DC HSDPA Introduction of Cell Portion for 1.28 Mcps TDD Single Stream MIMO for DC-HSDPA Activation and deactivation of secondary carrier in non serving Node B Correction of abnormal conditions for Dual cell HS-DSCH in RL Addition procedure Clarification of the meaning of BIT STRING type IEs for SPS operation for 1.28Mcps TDD MAC-e Reset Indicator for MAC-I Reset Further Corrections for DC-HSDPA Wrong ref in tabular STTD is cell specific in Dual-Cell HSDPA Introduction of Dual Cell E-DCH mode of operation Removal of MAC-ehs format indicator Correction on IE E-AGCH Table Choice Introduction of Re9 HSPA Capability into RNSAP Addition of HS-DSCH physical layer category over Iur E-RNTI Allocation for UE moves to Cell_FACH from Cell_DCH Allow reconfiguration of some Ies in RL Addition procedure Correction of DC-HSDPA Capability in Iur Correction for the description of E-DCH serving radio link IE for E-DCH semi-persistent operation Combining E-DCH Radio Links within the RLS Correction of Multi-cell Capability Report in Iur Introduction of HS-PDSCH resources on TS0 for 1.28Mcps TDD Correction to state transition of Enhanced CELL_FACH UE for LCR TDD Rel-9 Flexible cell combinations in DC-HSDPA Addition of DGNSS Validity Period in RNSAP Introduction of UE Aggregate Maximum Bit Rate Enforcement Indicator Syncronization detection window configuration in CPC for 1.28 Mcps TDD Measurement occasion configuration in CELL_DCH for 1.28Mcps TDD Correction for Procedural Text on E-RNTI Allocation at E-DCH Serving Cell Change Indication of Precoding Weight Set Restriction preference Rapporteurs update of RNSAP protocol Corrections to DC HSUPA Remove Cell Specific HARQ memory partitioning for DC HSDPA+MIMO and additional corrections for HS-DSCH preconfiguration Corrected a typo in ASN.1 to make it pass the syntax checker ToC updated Corrupted headers fixed CPC parameters missing for serving HS-DSCH RL change in RL Addition procedure Correction of procedure text that appears to be duplicated and mis-placed CQI Feedback Cycle k for DC-HSDPA and MIMO operation Correction when the power offset for S-CPICH for MIMO is zero Correction for Enhanced Serving Cell Change Clarification of 64 QAM usage at intra Node B serving HS-DSCH RL change Corrections to HSDPA secondary serving cell list handling Correction of procedure text for E-DCH SPS operation Addition of UE with enhanced HS-SCCH support indicator IE for Cell_FACH Release 10 version created based on v9.4.0 Introduction of 4C-HSDPA Small Technical Enhancements and Improvements for GNSS (RNSAP) Correction of 4C-HSDPA secondary serving HS-DSCH RL change Introduction of MC-HSUPA to RNSAP Introduction of MU-MIMO to RNSAP Corrections to E-DCH MAC-d Flow Multiplexing for 1.28Mcps TDD Correction of Inactivity Threshold for UE DRX Cycle for 1.28Mcps TDD Power Offset For S-CPICH for MIMO of secondary cell Addition of simultaneous cell capability for Multi-Carrier HSDPA and Single Stream MIMO Throughput/Energy Savings tradeoff for Dual Band UEs Clarification on the use of References (TS 21.801 CR#0030) Addition of Measurement Power Offset in ESCC procedure over Iur Addition of Multi-Carrier E-DCH capability IEs for MC-HSUPA to RNSAP Correction related to "Power Offset For S-CPICH for MIMO" Correction of SNPL carrier group indicator for 1.28 Mcps TDD Multi-Carrier E-DCH Battery optimization - tabular/ASN.1 mismatch cleanup Introduction of MDT Extension of maximum number neighbouring RNCs

3GPP

Release 11
52 52 52 52 52 52 52 52 52 52 52 52 53 53 53 53 53 53 53 53 54 54 54 54 12/2011 54 54 55 55 55 56 56 56 56 56 56 RP-110688 RP-110681 RP-110689 RP-110880 RP-110689 RP-110693 RP-110681 RP-110690 RP-110686 RP-110693 RP-110693 RP-110685 RP-111194 RP-111195 RP-111195 RP-111195 RP-111194 RP-111196 RP-111196 RP-111196 RP-111654 RP-111649 RP-111651 RP-111645 RP-111653 RP-111652 RP-120235 RP-120234 RP-120231 RP-120815 RP-120745 RP-120744 RP-120752 RP-120746 RP-120751 1674 1677 1678 1681 1682 1683 1685 1686 1687 1688 1689 1690 1698 1699 1700 1701 1706 1708 1709 1710 1714 1715 1718 1724 1716 1722 1732 1735 1738 1740 1741 1743 1750 1752 1754 1 1 3 4 1 3 1 1 1 2 2 1 1 3 2 1 1 2 1 2 1 1 1 1 1 1 3

1177

3GPP TS 25.423 V11.2.0 (2012-06)

10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.3.0 10.4.0 10.4.0 10.4.0 10.4.0 10.4.0 10.4.0 10.4.0 10.4.0 10.5.0 10.5.0 10.5.0 10.5.0 11.0.0 11.0.0 11.0.0 11.1.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0 11.2.0

Clarification on the Range of Possible Secondary Serving Cell List Misalignment between message tabular and ASN.1 for Idle Interval Information IE Extend the Number of Supported Carriers for Multi-Carrier HSDPA for 1.28Mcps TDD Introduction of Enhancements of Iur-g Interface Correction of the dependency of RNSAP to a specific signalling transport network layer Introduction of information transfer control for UTRAN ANR related information UE support indicator for DL secondary HS-DSCH activation state according to RRC Rel-9 Correction of abnormal condition text Rapporteurs proposal following review of TS 25.423 ANR Report Distribution using Direct Information Transfer procedure ANR Neighbour cell configuration supported by Information Exchange Initiation procedure Reference review outcome in TS 25.423 Corrections to UMTS ANR Clarification on M1 and M2 in MDT Configuration over Iur Clarification on MDT Recording Session Reference in MDT Configuration Area scope RAI list in MDT configuration Correction of Frequency Band Indicator, adding Band XXV Rapporteur corrections Correction of some generic references to dated references Correction of the CELL_DCH Measurement Occasion Information for 1.28Mcps TDD Addition of new Band 26 for E850 Addition of TCE IP in IUR INVOKE TRACE Support for frequency specific compressed mode Support of dynamic HS-SCCH order for DTXDRX Release 11 version created based on v10.5.0 Introduction of UL CLTD Introduction of 8-carrier HSDPA Addition of new Band 26 for E850 Correction of placement of Power Offset For S-CPICH for MIMO Request Indicator IE The role of RNC in RNSAP Reset procedure Clarification of the carrier capability for two-carrier HSDPA for 1.28Mcps TDD Some corrections for UL CLTD Clarification of the enhanced TS0 capability for 1.28Mcps TDD Introduction of Extended S-RNTI Supporting Non-adjacent multi-carrier operation Introduction of enhanced DC-HSDPA

3GPP