3GPP TS 25.331 - ccsa.org.cn€¦ · Web view · 2003-12-121> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" (FDD only) when

3GPP TS 25.331

CWTS STD-DS-25.331 (2002-V4)

Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Radio Access Network;

Radio Resource Control (RRC);

Protocol Specification

(Release 4)

Keywords

UMTS, radio

CWTS

Internet

http://www.cwts.org

Contents

25Foreword

1Scope26

2References26

3Definitions and abbreviations28

3.1Definitions28

3.2Abbreviations28

4General30

4.1Overview of the specification30

4.2RRC Layer Model31

4.3Protocol specification principles34

5RRC Functions and Services provided to upper layers34

5.1RRC Functions34

5.2RRC Services provided to upper layers35

5.3Primitives between RRC and upper layers35

6Services expected from lower layers35

6.1Services expected from Layer 235


6.3Signalling Radio Bearers35

7Protocol states36

7.1Overview of RRC States and State Transitions including GSM36

7.2Processes in UE modes/states36

7.2.1UE Idle mode36

7.2.2UTRA RRC Connected mode37

7.2.2.1URA_PCH or CELL_PCH state37

7.2.2.2CELL_FACH state37

7.2.2.3CELL_DCH state38

8RRC procedures38

8.1RRC Connection Management Procedures38

8.1.1Broadcast of system information38

8.1.1.1General39

8.1.1.1.1System information structure39

8.1.1.1.2System information blocks39

8.1.1.1.3Segmentation and concatenation of system information blocks43

8.1.1.1.4Re-assembly of segments44

8.1.1.1.5Scheduling of system information45

8.1.1.2Initiation46

8.1.1.3Reception of SYSTEM INFORMATION messages by the UE46

8.1.1.4Reception of SYSTEM INFORMATION messages broadcast on a FACH transport channel46

8.1.1.5Actions upon reception of the Master Information Block and Scheduling Block(s)46

8.1.1.6Actions upon reception of system information blocks49

8.1.1.6.1System Information Block type 150


















8.1.1.7Modification of system information59

8.1.1.7.1Modification of system information blocks using a value tag59

8.1.1.7.2Synchronised modification of system information blocks60

8.1.1.7.3Actions upon system information change60

8.1.1.7.4Actions upon expiry of a system information expiry timer61

8.1.2Paging61

8.1.2.1General61

8.1.2.2Initiation61

8.1.2.3Reception of a PAGING TYPE 1 message by the UE62

8.1.3RRC connection establishment63

8.1.3.1General63

8.1.3.2Initiation63

8.1.3.3RRC CONNECTION REQUEST message contents to set64

8.1.3.4Reception of an RRC CONNECTION REQUEST message by the UTRAN64

8.1.3.5Cell re-selection or T300 timeout64

8.1.3.5aAbortion of RRC connection establishment65

8.1.3.6Reception of an RRC CONNECTION SETUP message by the UE65

8.1.3.7Physical channel failure or cell re-selection66

8.1.3.8Invalid RRC CONNECTION SETUP message, unsupported configuration or invalid configuration67

8.1.3.9Reception of an RRC CONNECTION REJECT message by the UE68

8.1.3.10Invalid RRC CONNECTION REJECT message70

8.1.4RRC connection release70

8.1.4.1General71

8.1.4.2Initiation71

8.1.4.3Reception of an RRC CONNECTION RELEASE message by the UE71

8.1.4.4Invalid RRC CONNECTION RELEASE message72

8.1.4.5Cell re-selection or radio link failure73

8.1.4.6Expiry of timer T308, unacknowledged mode transmission73

8.1.4.7Void

74

8.1.4.8Reception of an RRC CONNECTION RELEASE COMPLETE message by UTRAN74

8.1.4.9Unsuccessful transmission of the RRC CONNECTION RELEASE COMPLETE message, acknowledged mode transmission74

8.1.4.10Detection of loss of dedicated physical channel by UTRAN in CELL_DCH state75

8.1.4.11Failure to receive RRC CONNECTION RELEASE COMPLETE message by UTRAN75

8.1.4aRRC connection release requested by upper layers75

8.1.4a.1General75

8.1.4a.2Initiation75

8.1.5Void75

8.1.6Transmission of UE capability information76

8.1.6.1General76

8.1.6.2Initiation76

8.1.6.3Reception of an UE CAPABILITY INFORMATION message by the UTRAN76

8.1.6.4Reception of the UE CAPABILITY INFORMATION CONFIRM message by the UE77

8.1.6.5Invalid UE CAPABILITY INFORMATION CONFIRM message77

8.1.6.6T304 timeout77

8.1.7UE capability enquiry78

8.1.7.1General78

8.1.7.2Initiation78

8.1.7.3Reception of an UE CAPABILITY ENQUIRY message by the UE78

8.1.7.4Invalid UE CAPABILITY ENQUIRY message78

8.1.8Initial Direct transfer79

8.1.8.1General79

8.1.8.2Initiation of Initial direct transfer procedure in the UE79

8.1.8.2aRLC re-establishment or inter-RAT change80

8.1.8.2bAbortion of signalling connection establishment81

8.1.8.3Reception of INITIAL DIRECT TRANSFER message by the UTRAN81

8.1.9Downlink Direct transfer81

8.1.9.1General81

8.1.9.2Initiation of downlink direct transfer procedure in the UTRAN81

8.1.9.3Reception of a DOWNLINK DIRECT TRANSFER message by the UE82

8.1.9.3aNo signalling connection exists82

8.1.9.4Invalid DOWNLINK DIRECT TRANSFER message82

8.1.10Uplink Direct transfer83

8.1.10.1General83

8.1.10.2Initiation of uplink direct transfer procedure in the UE83

8.1.10.2aRLC re-establishment or inter-RAT change84

8.1.10.3Reception of UPLINK DIRECT TRANSFER message by the UTRAN84

8.1.11UE dedicated paging84

8.1.11.1General84

8.1.11.2Initiation85

8.1.11.3Reception of a PAGING TYPE 2 message by the UE85

8.1.11.4Invalid PAGING TYPE 2 message85

8.1.12Security mode control86

8.1.12.1General86


8.1.12.2.1Ciphering configuration change86

8.1.12.2.2Integrity protection configuration change87

8.1.12.3Reception of SECURITY MODE COMMAND message by the UE88

8.1.12.3.1New ciphering and integrity protection keys92

8.1.12.4Void93

8.1.12.4aIncompatible simultaneous security reconfiguration94

8.1.12.4bCell update procedure during security reconfiguration94

8.1.12.4cInvalid configuration95

8.1.12.5Reception of SECURITY MODE COMPLETE message by the UTRAN95

8.1.12.6Invalid SECURITY MODE COMMAND message97

8.1.13Signalling connection release procedure97

8.1.13.1General97

8.1.13.2Initiation of SIGNALLING CONNECTION RELEASE by the UTRAN97

8.1.13.3Reception of SIGNALLING CONNECTION RELEASE by the UE98

8.1.13.4Invalid SIGNALLING CONNECTION RELEASE message98

8.1.13.5Invalid configuration98

8.1.14Signalling connection release indication procedure99

8.1.14.1General99


8.1.14.3Reception of SIGNALLING CONNECTION RELEASE INDICATION by the UTRAN99

8.1.15Counter check procedure100

8.1.15.1General100


8.1.15.3Reception of a COUNTER CHECK message by the UE100

8.1.15.4Reception of the COUNTER CHECK RESPONSE message by UTRAN101

8.1.15.5Cell re-selection101

8.1.15.6Invalid COUNTER CHECK message101

8.1.16Inter RAT handover information transfer102

8.1.16.1General102


8.1.16.3INTER RAT HANDOVER INFO message contents to set102

8.2Radio Bearer control procedures103

8.2.1Radio bearer establishment103

8.2.2Reconfiguration procedures103

8.2.2.1General105


8.2.2.3Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE or TRANSPORT CHANNEL RECONFIGURATION or PHYSICAL CHANNEL RECONFIGURATION message by the UE107

8.2.2.4Transmission of a response message by the UE, normal case112

8.2.2.5Reception of a response message by the UTRAN, normal case113

8.2.2.6Unsupported configuration in the UE114

8.2.2.7Physical channel failure115


8.2.2.9Transmission of a response message by the UE, failure case116

8.2.2.10Reception of a response message by the UTRAN, failure case116


8.2.2.12Incompatible simultaneous reconfiguration117


8.2.2.12bCell update procedure during security reconfiguration118

8.2.2.13Invalid received message118

8.2.3Radio bearer release118

8.2.4Transport channel reconfiguration119

8.2.5Transport format combination control119

8.2.5.1General119


8.2.5.3Reception of a TRANSPORT FORMAT COMBINATION CONTROL message by the UE119


8.2.5.5Invalid TRANSPORT FORMAT COMBINATION CONTROL message121

8.2.6Physical channel reconfiguration122

8.2.7Physical Shared Channel Allocation [TDD only]122

8.2.7.1General122


8.2.7.3Reception of a PHYSICAL SHARED CHANNEL ALLOCATION message by the UE122

8.2.7.4Invalid PHYSICAL SHARED CHANNEL ALLOCATION message124

8.2.8PUSCH capacity request [TDD only]124

8.2.8.1General124


8.2.8.3PUSCH CAPACITY REQUEST message contents to set125

8.2.8.4Reception of a PUSCH CAPACITY REQUEST message by the UTRAN126

8.2.8.5T310 expiry126

8.2.9Void127

8.2.10Uplink Physical Channel Control [TDD only]127

8.2.10.1General127


8.2.10.3Reception of UPLINK PHYSICAL CHANNEL CONTROL message by the UE127

8.2.10.4Invalid UPLINK PHYSICAL CHANNEL CONTROL message127

8.2.11Physical channel reconfiguration failure128

8.2.11.1General128

8.2.11.2Runtime error due to overlapping compressed mode configurations128

8.2.11.3Runtime error due to overlapping compressed mode configuration and PDSCH reception129

8.3RRC connection mobility procedures129

8.3.1Cell and URA update procedures129

8.3.1.1General131


8.3.1.3CELL UPDATE / URA UPDATE message contents to set135

8.3.1.4T305 expiry and the UE detects "out of service area"136

8.3.1.4.1Re-entering "in service area"137

8.3.1.4.2Expiry of timer T307137

8.3.1.5Reception of an CELL UPDATE/URA UPDATE message by the UTRAN138

8.3.1.6Reception of the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message by the UE139

8.3.1.7Transmission of a response message to UTRAN144

8.3.1.7aPhysical channel failure146

8.3.1.8Unsupported configuration by the UE148


8.3.1.9aIncompatible simultaneous reconfiguration150

8.3.1.10Confirmation error of URA ID list151

8.3.1.11Invalid CELL UPDATE CONFIRM/URA UPDATE CONFIRM message152

8.3.1.12T302 expiry or cell reselection153

8.3.1.13T314 expiry155

8.3.1.14T315 expiry156

8.3.1.15Reception of the UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN157

8.3.2URA update157

8.3.3UTRAN mobility information157

8.3.3.1General157


8.3.3.3Reception of UTRAN MOBILITY INFORMATION message by the UE158

8.3.3.4Reception of an UTRAN MOBILITY INFORMATION CONFIRM message by the UTRAN160



8.3.3.6Invalid UTRAN MOBILITY INFORMATION message161

8.3.4Active set update161

8.3.4.1General161


8.3.4.3Reception of an ACTIVE SET UPDATE message by the UE162

8.3.4.4Unsupported configuration in the UE164


8.3.4.5aIncompatible simultaneous reconfiguration165

8.3.4.6Reception of the ACTIVE SET UPDATE COMPLETE message by the UTRAN165

8.3.4.7Reception of the ACTIVE SET UPDATE FAILURE message by the UTRAN166

8.3.4.8Invalid ACTIVE SET UPDATE message166

8.3.4.9Reception of an ACTIVE SET UPDATE message in wrong state166

8.3.5Hard handover166

8.3.5.1Timing re-initialised hard handover167

8.3.5.1.1General167

8.3.5.1.2Initiation167

8.3.5.2Timing-maintained hard handover167

8.3.5.2.1General167

8.3.5.2.2Initiation168

8.3.6Inter-RAT handover to UTRAN168

8.3.6.1General168


8.3.6.3Reception of Handover to UTRAN command message by the UE169

8.3.6.4Invalid Handover to UTRAN command message171

8.3.6.4aUnsupported configuration in HANDOVER TO UTRAN COMMAND message172

8.3.6.5UE fails to perform handover172

8.3.6.6Reception of message HANDOVER TO UTRAN COMPLETE by the UTRAN172

8.3.7Inter-RAT handover from UTRAN172

8.3.7.1General173


8.3.7.3Reception of a HANDOVER FROM UTRAN COMMAND message by the UE173

8.3.7.4Successful completion of the inter-RAT handover173

8.3.7.5UE fails to complete requested handover174

8.3.7.6Invalid HANDOVER FROM UTRAN COMMAND message175

8.3.7.7Reception of an HANDOVER FROM UTRAN FAILURE message by UTRAN175

8.3.7.8Unsupported configuration in HANDOVER FROM UTRAN COMMAND message175

8.3.7.8aReception of HANDOVER FROM UTRAN COMMAND message by UE in CELL_FACH176

8.3.8Inter-RAT cell reselection to UTRAN176

8.3.8.1General176


8.3.8.3UE fails to complete an inter-RAT cell reselection177

8.3.9Inter-RAT cell reselection from UTRAN177

8.3.9.1General177


8.3.9.3Successful cell reselection177

8.3.9.4UE fails to complete an inter-RAT cell reselection177

8.3.10Inter-RAT cell change order to UTRAN177

8.3.10.1General177


8.3.10.3UE fails to complete an inter-RAT cell change order178

8.3.11Inter-RAT cell change order from UTRAN178

8.3.11.1General178


8.3.11.3Reception of an CELL CHANGE ORDER FROM UTRAN message by the UE179

8.3.11.4Successful completion of the cell change order179

8.3.11.5Expiry of timer T309 or UE fails to complete requested cell change order179

8.3.11.6Unsupported configuration in CELL CHANGE ORDER FROM UTRAN message180

8.3.11.7Invalid CELL CHANGE ORDER FROM UTRAN message181

8.4Measurement procedures181

8.4.0Measurement related definitions181

8.4.1Measurement control183

8.4.1.1General183


8.4.1.3Reception of MEASUREMENT CONTROL by the UE184

8.4.1.4Unsupported measurement in the UE186

8.4.1.4aConfiguration Incomplete187

8.4.1.5Invalid MEASUREMENT CONTROL message187

8.4.1.6Measurements after transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state187

8.4.1.6.1Intra-frequency measurement188

8.4.1.6.2Inter-frequency measurement188

8.4.1.6.3Inter-RAT measurement188

8.4.1.6.4Quality measurement188

8.4.1.6.5UE internal measurement189

8.4.1.6.6Traffic volume measurement189

8.4.1.6.7UE positioning measurement189

8.4.1.6aActions in CELL_FACH/CELL_PCH/URA/PCH state upon cell re-selection191

8.4.1.7Measurements after transition from CELL_FACH to CELL_DCH state191






8.4.1.8Measurements after transition from idle mode to CELL_DCH state193






8.4.1.9Measurements after transition from idle mode to CELL_FACH state194






8.4.1.9aMeasurements after transition from connected mode to idle mode195

8.4.1.9a.1Intra-frequency measurement195

8.4.1.9a.2Inter-frequency measurement195

8.4.1.9a.3Inter-RAT measurement195

8.4.1.9a.4UE positioning measurement195

8.4.1.10Measurements when measurement object is no longer valid195


8.4.2Measurement report196

8.4.2.1General196


8.4.3Assistance Data Delivery197

8.4.3.1General197


8.4.3.3Reception of ASSISTANCE DATA DELIVERY message by the UE197

8.4.3.4Invalid ASSISTANCE DATA DELIVERY message198

8.5General procedures198

8.5.1Selection of initial UE identity198

8.5.2Actions when entering idle mode from connected mode199

8.5.3Open loop power control upon establishment of DPCCH200

8.5.4Physical channel establishment criteria200

8.5.5Actions in "out of service area" and "in service area"200

8.5.5.1Detection of "out of service" area200

8.5.5.1.1Actions following detection of "out of service" area in URA_PCH or CELL_PCH state200

8.5.5.1.2Actions following detection of "out of service" area in CELL_FACH state200

8.5.5.2Detection of "in service" area200

8.5.5.2.1Actions following Re-entry into "in service area" in URA_PCH or CELL_PCH state201

8.5.5.2.2Actions following re-entry into "in service area" in CELL_FACH state201

8.5.5.3T316 expiry201

8.5.5.4T317 expiry201

8.5.6Radio link failure criteria and actions upon radio link failure201

8.5.7Open loop power control202

8.5.8Maintenance of Hyper Frame Numbers204

8.5.9START value calculation205

8.5.10Integrity protection205

8.5.10.1Integrity protection in downlink206

8.5.10.2Integrity protection in uplink207

8.5.10.3Calculation of message authentication code207

8.5.11FACH measurement occasion calculation208

8.5.12Establishment of Access Service Classes208

8.5.13Mapping of Access Classes to Access Service Classes209

8.5.14PLMN Type Selection209

8.5.14aNeighbour cells list narrowing for cell reselection209

8.5.15CFN calculation210

8.5.15.1Initialisation for CELL_DCH state after state transition210

8.5.15.2Initialisation in CELL_DCH state at hard handover210

8.5.15.3Initialisation for CELL_FACH210

8.5.15.4Initialisation after intersystem handover to UTRAN211

8.5.16Configuration of CTCH occasions211

8.5.17PRACH selection211

8.5.18Selection of RACH TTI212

8.5.18.1FDD Mode212

8.5.18.21.28 Mcps TDD213

8.5.19Secondary CCPCH selection213

8.6Generic actions on receipt and absence of an information element214

8.6.1CN information elements214

8.6.1.1Void

214

8.6.1.2CN information info214

8.6.1.3Signalling connection release indication214

8.6.2UTRAN mobility information elements215

8.6.2.1URA identity215

8.6.2.2Mapping info215

8.6.3UE information elements216

8.6.3.1Activation time216

8.6.3.1aCN domain specific DRX cycle length coefficient216

8.6.3.2UTRAN DRX Cycle length coefficient216

8.6.3.3Generic state transition rules depending on received information elements217

8.6.3.4Ciphering mode info217

8.6.3.5Integrity protection mode info220

8.6.3.6Void

223

8.6.3.7Void

223

8.6.3.8Integrity check info223

8.6.3.9New C-RNTI223

8.6.3.9aNew DSCH-RNTI223

8.6.3.10New U-RNTI223

8.6.3.11RRC transaction identifier224

8.6.3.12Capability Update Requirement227

8.6.4Radio bearer information elements228

8.6.4.1Signalling RB information to setup list228

8.6.4.2RAB information for setup229

8.6.4.2aRAB information to reconfigure229

8.6.4.3RB information to setup230

8.6.4.4RB information to be affected231

8.6.4.5RB information to reconfigure231

8.6.4.6RB information to release232

8.6.4.7RB with PDCP information232

8.6.4.8RB mapping info232

8.6.4.9RLC Info235

8.6.4.10PDCP Info235

8.6.4.11PDCP SN Info236

8.6.4.12NAS Synchronisation Indicator236

8.6.5Transport channel information elements236

8.6.5.1Transport Format Set236

8.6.5.2Transport format combination set239

8.6.5.3Transport format combination subset240

8.6.5.4DCH quality target241

8.6.5.5Added or Reconfigured UL TrCH information241

8.6.5.6Added or Reconfigured DL TrCH information241

8.6.5.7Deleted UL TrCH information242

8.6.5.8Deleted DL TrCH information242

8.6.5.9UL Transport channel information common for all transport channels242

8.6.5.10DL Transport channel information common for all transport channels242

8.6.5.11DRAC static information243

8.6.5.12TFCS Reconfiguration/Addition Information243

8.6.5.13TFCS Removal Information244

8.6.5.14TFCI Field 2 Information244

8.6.5.15TFCS Explicit Configuration244

8.6.6Physical channel information elements244

8.6.6.1Frequency info245

8.6.6.2Void

245

8.6.6.2aPNBSCH allocation245

8.6.6.3Void

245

8.6.6.4Downlink information for each radio link245

8.6.6.5Void

246

8.6.6.6Uplink DPCH info246

8.6.6.7Void

246

8.6.6.8Maximum allowed UL TX power246

8.6.6.9PDSCH with SHO DCH Info (FDD only)246

8.6.6.10PDSCH code mapping (FDD only)247

8.6.6.11Uplink DPCH power control info248

8.6.6.12Secondary CPICH info249

8.6.6.13Primary CPICH usage for channel estimation249

8.6.6.14DPCH frame offset250

8.6.6.15DPCH Compressed mode info250

8.6.6.16Repetition period, Repetition length, Offset (TDD only)252

8.6.6.17Primary CCPCH info252

8.6.6.18Primary CPICH info252

8.6.6.19CPCH SET Info (FDD only)252

8.6.6.20CPCH set ID (FDD only)253

8.6.6.21Default DPCH Offset Value253

8.6.6.22Secondary Scrambling Code, Code Number253

8.6.6.23PDSCH Power Control info254

8.6.6.24Tx Diversity Mode254

8.6.6.25SSDT Information254

8.6.6.26UL Timing Advance Control (TDD only)254

8.6.6.26aUplink synchronisation parameters255

8.6.6.27Downlink information common for all radio links255

8.6.6.28Downlink DPCH info common for all radio links255

8.6.6.29ASC setting256

8.6.6.30SRB delay, PC preamble (FDD only)258

8.6.6.31FPACH/PRACH Selection (1.28 Mcps TDD only)258

8.6.7Measurement information elements259

8.6.7.1Measurement validity259

8.6.7.2Filter coefficient259

8.6.7.3Intra-frequency/Inter-frequency/Inter-RAT cell info list260

8.6.7.4Intra-frequency measurement quantity265

8.6.7.5Inter-RAT measurement quantity266

8.6.7.6Inter-RAT reporting quantity266

8.6.7.7Cell Reporting Quantities267

8.6.7.8Periodical Reporting Criteria268

8.6.7.9Reporting Cell Status268

8.6.7.10Traffic Volume Measurement269

8.6.7.11Traffic Volume Measurement Reporting Criteria269

8.6.7.12FACH measurement occasion info270

8.6.7.13Measurement Reporting Mode271

8.6.7.14Inter-frequency measurement271

8.6.7.15Inter-RAT measurement272

8.6.7.16Intra-frequency measurement272

8.6.7.17Quality measurement272

8.6.7.18UE internal measurement273

8.6.7.18aUE positioning measurement273

8.6.7.19UE positioning273

8.6.7.19.0UE positioning reporting criteria273

8.6.7.19.1UE positioning reporting quantity273

8.6.7.19.1aUE positioning reporting for UE assisted methods274

8.6.7.19.1bUE positioning reporting for UE based methods276

8.6.7.19.2UE positioning OTDOA assistance data for UE-assisted277

8.6.7.19.2aUE positioning OTDOA assistance data for UE-based278

8.6.7.19.3UE positioning GPS assistance data279

8.6.7.19.4UE positioning Ciphering info282

8.6.7.19.5UE positioning Error283

8.6.7.19.6UE positioning GPS reference cell info284

8.6.7.20Void284

8.6.7.21Intra-frequency reporting quantity for RACH reporting284

8.6.8Void284

9Handling of unknown, unforeseen and erroneous protocol data284

9.1General284

9.2ASN.1 violation or encoding error284

9.3Unknown or unforeseen message type285

9.3aUnsolicited received message285

9.3bUnexpected critical message extension286

9.4Unknown or unforeseen information element value, mandatory information element286

9.5Conditional information element error287

9.6Unknown or unforeseen information element value, conditional information element287

9.7Unknown or unforeseen information element value, optional information element288

9.8Unexpected non-critical message extension288

9.9Handling of errors in nested information elements289

10Message and information element functional definition and content289

10.1General289

10.1.1Protocol extensions290

10.1.1.1Non-critical extensions292

10.1.1.1.1Extension of an information element with additional values or choices292

10.1.1.1.2Extension of a message with additional information elements292

10.1.1.2Critical extensions292

10.1.1.2.1Extension of an information element with additional values or choices292

10.1.1.2.2Extension of a message with additional information elements292

10.2Radio Resource Control messages293

10.2.1ACTIVE SET UPDATE293

10.2.2ACTIVE SET UPDATE COMPLETE294

10.2.3ACTIVE SET UPDATE FAILURE295

10.2.4ASSISTANCE DATA DELIVERY295

10.2.5CELL CHANGE ORDER FROM UTRAN296

10.2.6CELL CHANGE ORDER FROM UTRAN FAILURE297

10.2.7CELL UPDATE297

10.2.8CELL UPDATE CONFIRM298

10.2.9COUNTER CHECK301

10.2.10COUNTER CHECK RESPONSE302

10.2.11DOWNLINK DIRECT TRANSFER302

10.2.12Void303

10.2.13Void303

10.2.14Void303

10.2.15HANDOVER FROM UTRAN COMMAND303

10.2.16HANDOVER FROM UTRAN FAILURE304

10.2.16aHANDOVER TO UTRAN COMMAND305

10.2.16bHANDOVER TO UTRAN COMPLETE307

10.2.16cINITIAL DIRECT TRANSFER308

10.2.16dINTER RAT HANDOVER INFO308

10.2.17MEASUREMENT CONTROL309

10.2.18MEASUREMENT CONTROL FAILURE310

10.2.19MEASUREMENT REPORT311

10.2.20PAGING TYPE 1311

10.2.21PAGING TYPE 2312

10.2.22PHYSICAL CHANNEL RECONFIGURATION312

10.2.23PHYSICAL CHANNEL RECONFIGURATION COMPLETE314

10.2.24PHYSICAL CHANNEL RECONFIGURATION FAILURE315

10.2.25PHYSICAL SHARED CHANNEL ALLOCATION315

10.2.26PUSCH CAPACITY REQUEST316

10.2.27RADIO BEARER RECONFIGURATION317

10.2.28RADIO BEARER RECONFIGURATION COMPLETE320

10.2.29RADIO BEARER RECONFIGURATION FAILURE321

10.2.30RADIO BEARER RELEASE322

10.2.31RADIO BEARER RELEASE COMPLETE325

10.2.32RADIO BEARER RELEASE FAILURE326

10.2.33RADIO BEARER SETUP327

10.2.34RADIO BEARER SETUP COMPLETE329

10.2.35RADIO BEARER SETUP FAILURE331

10.2.36RRC CONNECTION REJECT331

10.2.37RRC CONNECTION RELEASE332

10.2.38RRC CONNECTION RELEASE COMPLETE333

10.2.39RRC CONNECTION REQUEST333

10.2.40RRC CONNECTION SETUP334

10.2.41RRC CONNECTION SETUP COMPLETE336

10.2.41aRRC FAILURE INFO337

10.2.42RRC STATUS337

10.2.43SECURITY MODE COMMAND338

10.2.44SECURITY MODE COMPLETE339

10.2.45SECURITY MODE FAILURE339

10.2.46SIGNALLING CONNECTION RELEASE340

10.2.47SIGNALLING CONNECTION RELEASE INDICATION340

10.2.48SYSTEM INFORMATION340

10.2.48.1First Segment342

10.2.48.2First Segment (short)342

10.2.48.3Subsequent Segment343

10.2.48.4Last Segment343

10.2.48.5Last Segment (short)343

10.2.48.6Complete SIB343

10.2.48.7Complete SIB (short)344

10.2.48.8System Information Blocks344

10.2.48.8.1Master Information Block344

10.2.48.8.2Scheduling Block 1345

10.2.48.8.3Scheduling Block 2345














10.2.48.8.16.1System Information Block type 13.1351













10.2.49SYSTEM INFORMATION CHANGE INDICATION356

10.2.50TRANSPORT CHANNEL RECONFIGURATION356

10.2.51TRANSPORT CHANNEL RECONFIGURATION COMPLETE359

10.2.52TRANSPORT CHANNEL RECONFIGURATION FAILURE360

10.2.53TRANSPORT FORMAT COMBINATION CONTROL360

10.2.54TRANSPORT FORMAT COMBINATION CONTROL FAILURE361

10.2.55UE CAPABILITY ENQUIRY362

10.2.56UE CAPABILITY INFORMATION362

10.2.57UE CAPABILITY INFORMATION CONFIRM363

10.2.58UPLINK DIRECT TRANSFER363

10.2.59UPLINK PHYSICAL CHANNEL CONTROL364

10.2.60URA UPDATE365

10.2.61URA UPDATE CONFIRM366

10.2.62UTRAN MOBILITY INFORMATION367

10.2.63UTRAN MOBILITY INFORMATION CONFIRM368

10.2.64UTRAN MOBILITY INFORMATION FAILURE369

10.3Information element functional definitions369

10.3.1CN Information elements369

10.3.1.1CN domain identity369

10.3.1.2CN Domain System Information369

10.3.1.3CN Information info370

10.3.1.3aCN Information info full371

10.3.1.4IMEI371

10.3.1.5IMSI (GSM-MAP)371

10.3.1.6Intra Domain NAS Node Selector372

10.3.1.7Location Area Identification373

10.3.1.8NAS message373

10.3.1.9NAS system information (GSM-MAP)373

10.3.1.10Paging record type identifier374

10.3.1.11PLMN identity374

10.3.1.12PLMN Type374

10.3.1.13P-TMSI (GSM-MAP)375

10.3.1.14RAB identity375

10.3.1.15Routing Area Code375

10.3.1.16Routing Area Identification375

10.3.1.17TMSI (GSM-MAP)376

10.3.2UTRAN mobility Information elements376

10.3.2.1Cell Access Restriction376

10.3.2.2Cell identity376

10.3.2.3Cell selection and re-selection info for SIB3/4377

10.3.2.4Cell selection and re-selection info for SIB11/12379

10.3.2.5Mapping Info379

10.3.2.6URA identity381

10.3.3UE Information elements381

10.3.3.1Activation time381

10.3.3.2Capability Update Requirement381

10.3.3.3Cell update cause382

10.3.3.4Ciphering Algorithm382

10.3.3.5Ciphering mode info382

10.3.3.6CN domain specific DRX cycle length coefficient382

10.3.3.7CPCH Parameters383

10.3.3.8C-RNTI384

10.3.3.9DRAC system information384

10.3.3.9aDSCH-RNTI384

10.3.3.10RRC State Indicator384

10.3.3.11Establishment cause386

10.3.3.12Expiration Time Factor387

10.3.3.13Failure cause387

10.3.3.14Failure cause and error information387

10.3.3.15Initial UE identity388

10.3.3.16Integrity check info388

10.3.3.17Integrity protection activation info389

10.3.3.18Integrity protection Algorithm389

10.3.3.19Integrity protection mode info390

10.3.3.20Maximum bit rate390

10.3.3.21Measurement capability390

10.3.3.21aMeasurement capability extension392

10.3.3.22Paging cause394

10.3.3.23Paging record394

10.3.3.24PDCP capability395

10.3.3.25Physical channel capability395

10.3.3.26Protocol error cause398

10.3.3.27Protocol error indicator399

10.3.3.28RB timer indicator399

10.3.3.29Redirection info399

10.3.3.30Re-establishment timer399

10.3.3.31Rejection cause400

10.3.3.32Release cause400

10.3.3.33RF capability FDD400

10.3.3.33aRF capability FDD extension400

10.3.3.33bRF capability TDD401

10.3.3.34RLC capability401

10.3.3.35RLC re-establish indicator401

10.3.3.36RRC transaction identifier401

10.3.3.37Security capability402

10.3.3.38START402

10.3.3.39Transmission probability402

10.3.3.40Transport channel capability403

10.3.3.41UE multi-mode/multi-RAT capability404

10.3.3.42UE radio access capability405

10.3.3.42aUE radio access capability extension406

10.3.3.42bUE security information406

10.3.3.43UE Timers and Constants in connected mode406

10.3.3.44UE Timers and Constants in idle mode407

10.3.3.45UE positioning capability408

10.3.3.46URA update cause408

10.3.3.47U-RNTI409

10.3.3.48U-RNTI Short409

10.3.3.49UTRAN DRX cycle length coefficient409

10.3.3.50Wait time409

10.3.4Radio Bearer Information elements409

10.3.4.0Default configuration identity409

10.3.4.1Downlink RLC STATUS info410

10.3.4.2PDCP info410

10.3.4.3PDCP SN info412

10.3.4.4Polling info413

10.3.4.5Predefined configuration identity413

10.3.4.5aPredefined configuration status information413

10.3.4.6Predefined configuration value tag414

10.3.4.7Predefined RB configuration414

10.3.4.8RAB info414

10.3.4.9RAB info Post415

10.3.4.10RAB information for setup415

10.3.4.11RAB information to reconfigure415

10.3.4.12NAS Synchronization indicator415

10.3.4.13RB activation time info416

10.3.4.14RB COUNT-C MSB information416

10.3.4.15RB COUNT-C information416

10.3.4.16RB identity416

10.3.4.17RB information to be affected417

10.3.4.18RB information to reconfigure417

10.3.4.19RB information to release417

10.3.4.20RB information to setup417

10.3.4.21RB mapping info418

10.3.4.22RB with PDCP information419

10.3.4.23RLC info420

10.3.4.24Signalling RB information to setup421

10.3.4.25Transmission RLC Discard421

10.3.5Transport CH Information elements423

10.3.5.1Added or Reconfigured DL TrCH information423

10.3.5.2Added or Reconfigured UL TrCH information423

10.3.5.3CPCH set ID423

10.3.5.4Deleted DL TrCH information424

10.3.5.5Deleted UL TrCH information424

10.3.5.6DL Transport channel information common for all transport channels424

10.3.5.7DRAC Static Information425

10.3.5.8Power Offset Information425

10.3.5.9Predefined TrCH configuration426

10.3.5.10Quality Target427

10.3.5.11Semi-static Transport Format Information427

10.3.5.12TFCI Field 2 Information427

10.3.5.13TFCS Explicit Configuration428

10.3.5.14TFCS Information for DSCH (TFCI range method)428

10.3.5.15TFCS Reconfiguration/Addition Information430

10.3.5.16TFCS Removal Information431

10.3.5.17Void431

10.3.5.18Transport channel identity431

10.3.5.19Transport Format Combination (TFC)431

10.3.5.20Transport Format Combination Set431

10.3.5.21Transport Format Combination Set Identity432

10.3.5.22Transport Format Combination Subset432

10.3.5.23Transport Format Set433

10.3.5.24UL Transport channel information common for all transport channels435

10.3.6Physical CH Information elements436

10.3.6.1AC-to-ASC mapping436

10.3.6.2AICH Info437

10.3.6.3AICH Power offset437

10.3.6.4Allocation period info437

10.3.6.5Alpha437

10.3.6.6ASC setting437

10.3.6.7Void439

10.3.6.8CCTrCH power control info439

10.3.6.8aCell and Channel Identity info439

10.3.6.9Cell parameters Id440

10.3.6.10Common timeslot info440

10.3.6.11Constant value440

10.3.6.11aConstant value TDD441

10.3.6.12CPCH persistence levels441

10.3.6.13CPCH set info441

10.3.6.14CPCH Status Indication mode443

10.3.6.15CSICH Power offset444

10.3.6.16Default DPCH Offset Value444

10.3.6.17Downlink channelisation codes444

10.3.6.18Downlink DPCH info common for all RL445

10.3.6.19Downlink DPCH info common for all RL Post446

10.3.6.20Downlink DPCH info common for all RL Pre446

10.3.6.21Downlink DPCH info for each RL447

10.3.6.22Downlink DPCH info for each RL Post448

10.3.6.23Downlink DPCH power control information449

10.3.6.24Downlink information common for all radio links449

10.3.6.25Downlink information common for all radio links Post450

10.3.6.26Downlink information common for all radio links Pre450

10.3.6.27Downlink information for each radio link450

10.3.6.28Downlink information for each radio link Post451

10.3.6.29Void451

10.3.6.30Downlink PDSCH information451

10.3.6.31Downlink rate matching restriction information451

10.3.6.32Downlink Timeslots and Codes452

10.3.6.33DPCH compressed mode info452

10.3.6.34DPCH Compressed Mode Status Info455

10.3.6.35Dynamic persistence level456

10.3.6.35aFPACH info456

10.3.6.36Frequency info456

10.3.6.37Individual timeslot info456

10.3.6.38Individual Timeslot interference457

10.3.6.39Maximum allowed UL TX power457

10.3.6.40Void457

10.3.6.41Midamble shift and burst type457

10.3.6.42PDSCH Capacity Allocation info459

10.3.6.43PDSCH code mapping459

10.3.6.44PDSCH info460

10.3.6.45PDSCH Power Control info461

10.3.6.46PDSCH system information461

10.3.6.47PDSCH with SHO DCH Info462

10.3.6.48Persistence scaling factors462

10.3.6.49PICH Info462

10.3.6.50PICH Power offset463

10.3.6.51PRACH Channelisation Code List463

10.3.6.51aPRACH Channelisation Code 1.28 Mcps TDD464

10.3.6.52PRACH info (for RACH)464

10.3.6.53PRACH partitioning465

10.3.6.54PRACH power offset466

10.3.6.55PRACH system information list466

10.3.6.56Predefined PhyCH configuration467

10.3.6.57Primary CCPCH info467

10.3.6.58Primary CCPCH info post468

10.3.6.59Primary CCPCH TX Power468

10.3.6.60Primary CPICH info468

10.3.6.61Primary CPICH Tx power469

10.3.6.62Primary CPICH usage for channel estimation469

10.3.6.63PUSCH info469

10.3.6.64PUSCH Capacity Allocation info470

10.3.6.65PUSCH power control info470

10.3.6.66PUSCH system information470

10.3.6.67RACH transmission parameters471

10.3.6.68Radio link addition information471

10.3.6.69Radio link removal information472

10.3.6.70SCCPCH Information for FACH472

10.3.6.70aSCTD indicator472

10.3.6.71Secondary CCPCH info473

10.3.6.72Secondary CCPCH system information474

10.3.6.73Secondary CPICH info474

10.3.6.74Secondary scrambling code474

10.3.6.75SFN Time info475

10.3.6.75aSpecial Burst Scheduling475

10.3.6.76SSDT cell identity475

10.3.6.77SSDT information475

10.3.6.78STTD indicator475

10.3.6.78aSYNC_UL info476

10.3.6.79TDD open loop power control476

10.3.6.80TFC Control duration477

10.3.6.81TFCI Combining Indicator477

10.3.6.82TGPSI477

10.3.6.83Time info478

10.3.6.84Timeslot number478

10.3.6.85TPC combination index478

10.3.6.85aTSTD indicator478

10.3.6.86TX Diversity Mode478

10.3.6.87UL interference479

10.3.6.87aUL interference TDD479

10.3.6.88Uplink DPCH info480

10.3.6.89Uplink DPCH info Post481

10.3.6.90Uplink DPCH info Pre481

10.3.6.91Uplink DPCH power control info481

10.3.6.92Uplink DPCH power control info Post482

10.3.6.93Uplink DPCH power control info Pre483

10.3.6.94Uplink Timeslots and Codes483

10.3.6.95Uplink Timing Advance484

10.3.6.96Uplink Timing Advance Control485

10.3.7Measurement Information elements486

10.3.7.1Additional measurements list486

10.3.7.2Cell info486

10.3.7.3Cell measured results488

10.3.7.4Cell measurement event results488

10.3.7.5Cell reporting quantities489

10.3.7.6Cell synchronisation information489

10.3.7.7Event results490

10.3.7.8FACH measurement occasion info491

10.3.7.9Filter coefficient491

10.3.7.10HCS Cell re-selection information492

10.3.7.11HCS neighbouring cell information492

10.3.7.12HCS Serving cell information492

10.3.7.13Inter-frequency cell info list493

10.3.7.14Inter-frequency event identity493

10.3.7.15Inter-frequency measured results list493

10.3.7.16Inter-frequency measurement494

10.3.7.17Inter-frequency measurement event results495

10.3.7.18Inter-frequency measurement quantity495

10.3.7.19Inter-frequency measurement reporting criteria496

10.3.7.20Inter-frequency measurement system information497

10.3.7.21Inter-frequency reporting quantity497

10.3.7.22Inter-frequency SET UPDATE497

10.3.7.23Inter-RAT cell info list498

10.3.7.24Inter-RAT event identity499

10.3.7.25Inter-RAT info499

10.3.7.26Inter-RAT measured results list500

10.3.7.27Inter-RAT measurement500

10.3.7.28Inter-RAT measurement event results501

10.3.7.29Inter-RAT measurement quantity501

10.3.7.30Inter-RAT measurement reporting criteria502

10.3.7.31Inter-RAT measurement system information503

10.3.7.32Inter-RAT reporting quantity503

10.3.7.33Intra-frequency cell info list503

10.3.7.34Intra-frequency event identity504

10.3.7.35Intra-frequency measured results list504

10.3.7.36Intra-frequency measurement505

10.3.7.37Intra-frequency measurement event results505

10.3.7.38Intra-frequency measurement quantity506

10.3.7.39Intra-frequency measurement reporting criteria506

10.3.7.40Intra-frequency measurement system information508

10.3.7.41Intra-frequency reporting quantity509

10.3.7.42Intra-frequency reporting quantity for RACH reporting509

10.3.7.43Maximum number of reported cells on RACH510

10.3.7.44Measured results510

10.3.7.45Measured results on RACH511

10.3.7.46Measurement Command512

10.3.7.47Measurement control system information513

10.3.7.48Measurement Identity513

10.3.7.49Measurement reporting mode514

10.3.7.50Measurement Type514

10.3.7.51Measurement validity514

10.3.7.52Observed time difference to GSM cell514

10.3.7.53Periodical reporting criteria515

10.3.7.53aPLMN identities of neighbour cells515

10.3.7.54Primary CCPCH RSCP info516

10.3.7.54aQhcs516

10.3.7.55Quality measured results list517

10.3.7.56Quality measurement518

10.3.7.57Quality measurement event results518

10.3.7.58Quality measurement reporting criteria518

10.3.7.59Quality reporting quantity519

10.3.7.60Reference time difference to cell519

10.3.7.61Reporting Cell Status519

10.3.7.62Reporting information for state CELL_DCH521

10.3.7.63SFN-SFN observed time difference522

10.3.7.64Time to trigger522

10.3.7.65Timeslot ISCP info522

10.3.7.66Traffic volume event identity522

10.3.7.67Traffic volume measured results list522

10.3.7.68Traffic volume measurement523

10.3.7.69Traffic volume measurement event results523

10.3.7.70Traffic volume measurement object524

10.3.7.71Traffic volume measurement quantity524

10.3.7.72Traffic volume measurement reporting criteria526

10.3.7.73Traffic volume measurement system information527

10.3.7.74Traffic volume reporting quantity527

10.3.7.75UE internal event identity527

10.3.7.76UE internal measured results528

10.3.7.77UE internal measurement529

10.3.7.78UE internal measurement event results529

10.3.7.79UE internal measurement quantity529

10.3.7.80UE internal measurement reporting criteria530

10.3.7.81UE internal measurement system information531

10.3.7.82UE Internal reporting quantity531

10.3.7.83UE Rx-Tx time difference type 1531

10.3.7.84UE Rx-Tx time difference type 2532

10.3.7.85UE Transmitted Power info532

10.3.7.86UE positioning Ciphering info532

10.3.7.87UE positioning Error532

10.3.7.88UE positioning GPS acquisition assistance533

10.3.7.88aUE positioning GPS Additional Assistance Data Request534

10.3.7.89UE positioning GPS almanac535

10.3.7.90UE positioning GPS assistance data535

10.3.7.90aVoid536

10.3.7.91UE positioning GPS DGPS corrections536

10.3.7.91aUE positioning GPS Ephemeris and Clock Correction parameters538

10.3.7.92UE positioning GPS ionospheric model539

10.3.7.93UE positioning GPS measured results539

10.3.7.94UE positioning GPS navigation model540

10.3.7.95UE positioning GPS real-time integrity541

10.3.7.95aUE positioning GPS reference cell info541

10.3.7.96UE positioning GPS reference time541

10.3.7.97UE positioning GPS UTC model542

10.3.7.98UE positioning IPDL parameters542

10.3.7.99UE positioning measured results543

10.3.7.100UE positioning measurement543

10.3.7.101UE positioning measurement event results544

10.3.7.102Void545

10.3.7.103UE positioning OTDOA assistance data for UE-assisted545

10.3.7.103aUE positioning OTDOA assistance data for UE-based545

10.3.7.104Void545

10.3.7.105UE positioning OTDOA measured results545

10.3.7.106UE positioning OTDOA neighbour cell info546

10.3.7.106aUE positioning OTDOA neighbour cell info for UE-based548

10.3.7.107UE positioning OTDOA quality548

10.3.7.108UE positioning OTDOA reference cell info549

10.3.7.108aUE positioning OTDOA reference cell info for UE-based550

10.3.7.109UE positioning position estimate info550

10.3.7.109aUE positioning Relative Time Difference quality552

10.3.7.110UE positioning reporting criteria552

10.3.7.111UE positioning reporting quantity553

10.3.7.112TADV info554

10.3.8Other Information elements555

10.3.8.1BCCH modification info555

10.3.8.2BSIC555

10.3.8.3CBS DRX Level 1 information555

10.3.8.4Cell Value tag555

10.3.8.4aEllipsoid point556

10.3.8.4bEllipsoid point with Altitude556

10.3.8.4cEllipsoid point with Altitude and uncertainty ellipsoid556

10.3.8.4dEllipsoid point with uncertainty Circle557

10.3.8.4eEllipsoid point with uncertainty Ellipse558

10.3.8.5Inter-RAT change failure558

10.3.8.6Inter-RAT handover failure559

10.3.8.7Inter-RAT UE radio access capability559

10.3.8.8Void559

10.3.8.8aInter-RAT UE security capability560

10.3.8.9MIB Value tag560

10.3.8.10PLMN Value tag560

10.3.8.10aPNBSCH allocation560

10.3.8.11Predefined configuration identity and value tag560

10.3.8.12Protocol error information561

10.3.8.13References to other system information blocks561

10.3.8.14References to other system information blocks and scheduling blocks561

10.3.8.15Rplmn information561

10.3.8.16Scheduling information562

10.3.8.17SEG COUNT563

10.3.8.18Segment index563

10.3.8.19SIB data fixed563

10.3.8.20SIB data variable564

10.3.8.20aSIB occurrence identity564

10.3.8.20bSIB occurrence identity and value tag564

10.3.8.20cSIB occurrence value tag564

10.3.8.21SIB type564

10.3.8.22SIB type SIBs only566

10.3.9ANSI-41 Information elements567

10.3.9.1ANSI 41 Core Network Information567

10.3.9.2ANSI-41 Global Service Redirection information567

10.3.9.3ANSI-41 NAS parameter567

10.3.9.4ANSI-41 NAS system information567

10.3.9.5ANSI-41 Private Neighbour List information567

10.3.9.6ANSI-41 RAND information568

10.3.9.7ANSI-41 User Zone Identification information568

10.3.9.8MIN_P_REV568

10.3.9.9NID568

10.3.9.10P_REV568

10.3.9.11SID568

10.3.10Multiplicity values and type constraint values569

11Message and Information element abstract syntax (with ASN.1)571

11.0General571

11.1General message structure572

11.2PDU definitions575

11.3Information element definitions614

11.4Constant definitions731

11.5RRC information between network nodes732

12Message transfer syntax738

12.1Structure of encoded RRC messages738

12.1.1Basic production738

12.1.2Extension738

12.1.3Padding738

12.2ECN link module for RRC741

12.3ECN modules for RRC742

12.4RRC messages encoded otherwise742

12.4.1Messages using tabular encoding specification742

12.4.1.1TRANSPORT FORMAT COMBINATION CONTROL using transparent DCCH743

12.4.1.1.1TRANSPORT FORMAT COMBINATION CONTROL, 3 bit format743



13Protocol timers, counters, other parameters and default configurations744

13.1Timers for UE744

13.2Counters for UE745

13.3UE constants and parameters745

13.4UE variables745

13.4.0CELL INFO LIST745

13.4.00Void746

13.4.0aCELL_UPDATE_STARTED747

13.4.1CIPHERING_STATUS747

13.4.2Void747

13.4.2aCONFIGURATION_INCOMPLETE747

13.4.3C_RNTI748

13.4.3aDSCH_RNTI748

13.4.4Void748

13.4.5ESTABLISHED_RABS748

13.4.5aESTABLISHED_SIGNALLING_CONNECTIONS749

13.4.6ESTABLISHMENT_CAUSE749

13.4.7FAILURE_CAUSE749

13.4.8FAILURE_INDICATOR749

13.4.8aINCOMPATIBLE_SECURITY_RECONFIGURATION750

13.4.9INITIAL_UE_IDENTITY750

13.4.9aINTEGRITY_PROTECTION_ACTIVATION_INFO750

13.4.10INTEGRITY_PROTECTION_INFO750

13.4.10aINTER_RAT_HANDOVER_INFO_TRANSFERRED751

13.4.11INVALID_CONFIGURATION751

13.4.11aLATEST_CONFIGURED_CN_DOMAIN752

13.4.12MEASUREMENT_IDENTITY752

13.4.13Void752

13.4.14ORDERED_RECONFIGURATION752

13.4.15PDCP_SN_INFO752

13.4.16PROTOCOL_ERROR_INDICATOR753

13.4.17PROTOCOL_ERROR_INFORMATION753

13.4.18PROTOCOL_ERROR_REJECT753

13.4.19RB_TIMER_INDICATOR753

13.4.20RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO754

13.4.20aSECURITY_MODIFICATION754

13.4.21SELECTED_PLMN754

13.4.22START_THRESHOLD754

13.4.23START_VALUE_TO_TRANSMIT755

13.4.24TFC_SUBSET755

13.4.25TGPS_IDENTITY756

13.4.26TGSN_REPORTED756

13.4.26aTIMERS_AND_CONSTANTS757

13.4.27TRANSACTIONS757

13.4.27aTRIGGERED_1A_EVENT757

13.4.27bTRIGGERED_1B_EVENT758

13.4.27cTRIGGERED_1C_EVENT759

13.4.27dBEST_CELL_1D_EVENT759

13.4.27eTRIGGERED_1E_EVENT759

13.4.27fTRIGGERED_1F_EVENT760

13.4.27f1TRIGGERED_1G_EVENT760

13.4.27f2TRIGGERED_1H_EVENT760

13.4.27f3TRIGGERED_1I_EVENT760

13.4.27f4BEST_FREQUENCY_2A_EVENT761

13.4.27f5TRIGGERED_2B_EVENT761

13.4.27f6TRIGGERED_2C_EVENT761

13.4.27f7TRIGGERED_2D_EVENT761

13.4.27f8TRIGGERED_2E_EVENT762

13.4.27f9TRIGGERED_2F_EVENT762

13.4.27f10TRIGGERED_3A_EVENT762

13.4.27f11TRIGGERED_3B_EVENT763

13.4.27f12TRIGGERED_3C_EVENT763

13.4.27f13BEST_CELL_3D_EVENT763

13.4.27gUE_CAPABILITY_REQUESTED764

13.4.28UE_CAPABILITY_TRANSFERRED764

13.4.28aUE_POSITIONING_GPS_DATA764

13.4.28bUE_POSITIONING_OTDOA_DATA_UE_ASSISTED766

13.4.28cUE_POSITIONING_OTDOA_DATA_UE_BASED767

13.4.29UNSUPPORTED_CONFIGURATION767

13.4.30URA_IDENTITY767

13.4.31U_RNTI767

13.4.32VALUE_TAG768

13.5UE RRC Procedure Performance769

13.5.1Definitions769

13.5.2RRC procedure performance values770

13.6RB information parameters for signalling radio bearer RB 0775

13.6aRB information parameters for SHCCH775

13.6bRB information parameters for BCCH mapped to FACH775

13.6cRB information parameters for PCCH mapped to PCH776

13.6dParameters for BCCH mapped to BCH776

13.7Parameter values for default radio configurations776

14Specific functions799

14.1Intra-frequency measurements799

14.1.1Intra-frequency measurement quantities799

14.1.2Intra-frequency reporting events for FDD800

14.1.2.1Reporting event 1A: A Primary CPICH enters the reporting range800

14.1.2.2Reporting event 1B: A primary CPICH leaves the reporting range802

14.1.2.3Reporting event 1C: A non-active primary CPICH becomes better than an active primary CPICH804

14.1.2.4Reporting event 1D: Change of best cell806

14.1.2.5Reporting event 1E: A Primary CPICH becomes better than an absolute threshold808

14.1.2.6Reporting event 1F: A Primary CPICH becomes worse than an absolute threshold809

14.1.3Intra-frequency reporting events for TDD811

14.1.3.1Reporting event 1G: Change of best cell (TDD)811

14.1.3.2Reporting event 1H: Timeslot ISCP below a certain threshold (TDD)812

14.1.3.3Reporting event 1I: Timeslot ISCP above a certain threshold (TDD)813

14.1.4Event-triggered periodic intra-frequency measurement reports (informative)815

14.1.4.1Cell addition failure (FDD only)815

14.1.4.2Cell replacement failure (FDD only)816

14.1.5Mechanisms available for modifying intra-frequency measurement reporting behaviour (informative)816

14.1.5.1Hysteresis816

14.1.5.2Time-to-trigger817

14.1.5.3Cell individual offsets818

14.1.5.4Forbid a Primary CPICH to affect the reporting range (FDD only)819

14.1.6Report quantities in intra-frequency measurements820

14.2Inter-frequency measurements821

14.2.0aInter-frequency measurement quantities821

14.2.0bFrequency quality estimate821

14.2.0b.1FDD cells821

14.2.0b.2TDD cells822

14.2.0cInter-frequency reporting quantities822

14.2.1Inter-frequency reporting events822

14.2.1.1Event 2a: Change of best frequency.823

14.2.1.2Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold.823

14.2.1.3Event 2c: The estimated quality of a non-used frequency is above a certain threshold825

14.2.1.4Event 2d: The estimated quality of the currently used frequency is below a certain threshold826

14.2.1.5Event 2e: The estimated quality of a non-used frequency is below a certain threshold827

14.2.1.6Event 2 f: The estimated quality of the currently used frequency is above a certain threshold828

14.3Inter-RAT measurements829

14.3.0aInter-RAT measurement quantities829

14.3.0bFrequency quality estimate of the UTRAN frequency829

14.3.0cInter-RAT reporting quantities829

14.3.1Inter-RAT reporting events830

14.3.1.1Event 3a: The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold.830

14.3.1.2Event 3b: The estimated quality of other system is below a certain threshold832

14.3.1.3Event 3c: The estimated quality of other system is above a certain threshold833

14.3.1.4Event 3d: Change of best cell in other system834

14.3.2GSM measurements in compressed mode836

14.3.2.1GSM RSSI measurements836

14.3.2.2Initial BSIC identification836

14.3.2.3BSIC re-confirmation836

14.4Traffic Volume Measurements836

14.4.1Traffic Volume Measurement Quantity836

14.4.2Traffic Volume reporting triggers837

14.4.2.1Reporting event 4 A: Transport Channel Traffic Volume exceeds an absolute threshold837

14.4.2.2Reporting event 4 B: Transport Channel Traffic Volume becomes smaller than an absolute threshold838

14.4.3Traffic volume reporting mechanisms838

14.4.3.1Pending time after trigger838

14.4.4Interruption of user data transmission839

14.5Quality Measurements839

14.5.1Quality reporting measurement quantities839

14.5.2Quality reporting events839

14.5.2.1Reporting event 5A: A predefined number of bad CRCs is exceeded839

14.6UE internal measurements840

14.6.1UE internal measurement quantities840

14.6.2UE internal measurement reporting events840

14.6.2.1Reporting event 6A: The UE Tx power becomes larger than an absolute threshold840

14.6.2.2Reporting event 6B: The UE Tx power becomes less than an absolute threshold841

14.6.2.3Reporting event 6C: The UE Tx power reaches its minimum value841

14.6.2.4Reporting event 6D: The UE Tx power reaches its maximum value841

14.6.2.5Reporting event 6E: The UE RSSI reaches the UE's dynamic receiver range842

14.6.2.6Reporting event 6F (FDD): The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold842

14.6.2.6aReporting event 6F (1.28 Mcps TDD): The time difference indicated by TADV becomes larger than an absolute threshold842

14.6.2.7Reporting event 6G: The UE Rx-Tx time difference for a RL included in the active set becomes less than an absolute threshold842

14.7UE positioning measurements842

14.7.1UE positioning measurement quantities842

14.7.2Void843

14.7.3UE positioning reporting events843

14.7.3.1Reporting Event 7a: The UE position changes more than an absolute threshold843

14.7.3.2Reporting Event 7b: SFN-SFN measurement changes more than an absolute threshold843

14.7.3.3Reporting Event 7c: GPS time and SFN time have drifted apart more than an absolute threshold844

14.8Dynamic Resource Allocation Control of Uplink DCH (FDD only)844

14.9Downlink power control845

14.9.1Generalities845

14.9.2Downlink power control in compressed mode845

14.10Calculated Transport Format Combination846

14.11UE autonomous update of virtual active set on non-used frequency (FDD only)846

14.11.1Initial virtual active set847

14.11.2Virtual active set update during an inter-frequency measurement850

14.12Provision and reception of RRC information between network nodes852

14.12.0General852

14.12.0aGeneral error handling for RRC messages exchanged between network nodes853

14.12.1RRC Information to target RNC854

14.12.2RRC information, target RNC to source RNC854

14.12.3Void855

14.12.4RRC messages exchanged between network nodes855

14.12.4.0HANDOVER TO UTRAN COMMAND855

14.12.4.0aINTER RAT HANDOVER INFO855

14.12.4.1INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES856

14.12.4.2SRNS RELOCATION INFO856

14.12.4.3Void864

14.13Void864

14.14Versatile Channel Assignment Mode (VCAM) mapping rule (FDD only)864

Annex A (informative):USIM parameters866

A.1Introduction866

A.2Ciphering information866

A.3Frequency information866

A.4Multiplicity values and type constraint values867

Annex B (informative):Description of RRC state transitions868

B.1RRC states and state transitions including GSM868

B.2Transition from Idle Mode to UTRA RRC Connected Mode868

B.2.1Transitions for Emergency Calls868

B.3UTRA RRC Connected Mode States and Transitions868

B.3.1CELL_DCH state868

B.3.1.1Transition from CELL_DCH to Idle Mode869

B.3.1.2Transition from CELL_DCH to CELL_FACH state869

B.3.1.3Transition from CELL_DCH to CELL_PCH state869

B.3.1.4Transition from CELL_DCH to URA_PCH state869

B.3.1.5Radio Resource Allocation tasks (CELL_DCH)869

B.3.1.6RRC Connection mobility tasks (CELL_DCH)869

B.3.1.7UE Measurements (CELL_DCH)870

B.3.1.8Acquisition of system information (CELL_DCH)870

B.3.2CELL_FACH state870

B.3.2.1Transition from CELL_FACH to CELL_DCH state870

B.3.2.2Transition from CELL_FACH to CELL_PCH state870

B.3.2.3Transition from CELL_FACH to Idle Mode870

B.3.2.4Transition from CELL_FACH to URA_PCH State870

B.3.2.5Radio Resource Allocation Tasks (CELL_FACH)870

B.3.2.6RRC Connection mobility tasks (CELL_FACH)871

B.3.2.7UE Measurements (CELL_FACH)871

B.3.2.8Transfer and update of system information (CELL_FACH)871

B.3.3CELL_PCH state872

B.3.3.1Transition from CELL_PCH to CELL_FACH state872

B.3.3.2Radio Resource Allocation Tasks (CELL_PCH)872

B.3.3.3RRC Connection mobility tasks (CELL_PCH)872

B.3.3.4UE Measurements (CELL_PCH)872

B.3.3.5Transfer and update of system information (CELL_PCH)872

B.3.4URA_PCH State873

B.3.4.1Transition from URA_PCH State to CELL_FACH State (URA_PCH)873

B.3.4.2Radio Resource Allocation Tasks (URA_PCH)873

B.3.4.3RRC Connection mobility tasks (URA_PCH)873

B.3.4.4UE Measurements (URA_PCH)873

B.3.4.5Transfer and update of system information (URA_PCH)874

B.3.5States and Transitions for Cell Reselection in URA_PCH, CELL_PCH, and CELL_FACH874

B.4Inter-RAT handover with CS domain services874

B.5Inter-RAT handover with PS domain services875

B.6Inter-RAT handover with simultaneous PS and CS domain services875

B.6.1Inter-RAT handover UTRAN to GSM / BSS875

B.6.2Inter-RAT handover GSM / BSS to UTRAN875

Annex C (informative):Change history876

Foreword

This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

xthe first digit:

1presented to TSG for information;

2presented to TSG for approval;

3or 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.

zthe third digit is incremented when editorial only changes have been incorporated in the document.

1Scope

The present document specifies the Radio Resource Control protocol for the UE-UTRAN radio interface.

The scope of the present document also includes:

-the information to be transported in a transparent container between source RNC and target RNC in connection with SRNC relocation;

-the information to be transported in a transparent container between a target RNC and another system.

2References

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

References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.

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]3GPP TR21.905: "Vocabulary for 3GPP Specifications".

[2]3GPP TS25.301: "Radio Interface Protocol Architecture".

[3]3GPP TS25.303: "Interlayer Procedures in Connected Mode".

[4]3GPP TS25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".

[5]3GPP TS24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3".

[6]3GPP TS25.103: "RF parameters in support of RRM".

[7]3GPP TS25.215: "Physical layer Measurements (FDD)".

[8]3GPP TS25.225: "Physical layer Measurements (TDD)".

[9]3GPP TS25.401: "UTRAN overall description".

[10]3GPP TS25.402: "Synchronization in UTRAN; Stage 2".

[11]3GPP TS23.003: "Numbering, addressing and identification".

[12]ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interface".

[13]RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)".

[14]3GPP TR25.921: "Guidelines and principles for protocol description and error handling".

[15]3GPP TS25.321: "Medium Access Control (MAC) protocol specification".

[16]3GPP TS25.322: "Radio Link Control (RLC) protocol specification".

[17]3GPP TS24.007: "Mobile radio interface signalling layer 3; General aspects".

[18]3GPP TS25.305: "Stage 2 Functional Specification of UE Positioning in UTRAN".

[19]3GPPTS25.133: "Requirements for Support of Radio Resource Management (FDD)".

[20]3GPP TS25.123: "Requirements for Support of Radio Resource Management (TDD)".

[21]3GPP TS25.101: "UE Radio Transmission and Reception (FDD)".

[22]3GPP TS25.102: "UE Radio Transmission and Reception (TDD)".

[23]3GPP TS23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".

[24]3GPP TS23.032: "Universal Geographical Area Description (GAD)".

[25]3GPP TS23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".

[26]3GPP TS25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".

[27]3GPP TS25.212: "Multiplexing and channel coding (FDD)".

[28]3GPP TS25.213: "Spreading and modulation (FDD)".

[29]3GPP TS25.214: "Physical layer procedures (FDD)".

[30]3GPP TS25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".

[31]3GPP TS25.222: "Multiplexing and channel coding (TDD)".

[32]3GPP TS25.223: "Spreading and modulation (TDD)".

[33]3GPP TS25.224: "Physical Layer Procedures (TDD)".

[34]3GPP TS25.302: "Services provided by the physical layer ".

[35]3GPP TS25.306 "UE Radio Access Capabilities".

[36]3GPP TS25.323: "Packet Data Convergence Protocol (PDCP) Specification".

[37]3GPP TS25.324: "Broadcast/Multicast Control BMC".

[38]3GPP TR25.922: "Radio resource management strategies".

[39]3GPP TR25.925: "Radio interface for broadcast/multicast services".

[40]3GPP TS33.102: "3G Security; Security Architecture".

[41]3GPP TS34.108: "Common Test Environments for User Equipment (UE) Conformance Testing".

[42]3GPP TS34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification".

[43]3GPP TS44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".

[44]3GPP TS44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".

[45]3GPP TS45.005: "Radio transmission and reception".

[46]3GPP TS45.008: "Radio subsystem link control".

[47]ITU-T Recommendation X.680 (12/97) "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".

[48]ITU-T Recommendation X.681 (12/97) "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification".

[49]ITU-T Recommendation X.691 (12/97) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".

[50]3GPP TS31.102: "Characteristics of the USIM Application".

3Definitions and abbreviations

3.1Definitions

For the purposes of the present document, the terms and definitions given in [1] apply.

3.2Abbreviations

For the purposes of the present document, the following abbreviations apply:

ACKAcknowledgement

AICHAcquisition Indicator CHannel

AMAcknowledged Mode

ASAccess Stratum

ASCAccess Service Class

ASN.1Abstract Syntax Notation.1

BCCHBroadcast Control Channel

BCFEBroadcast Control Functional Entity

BERBit Error Rate

BLERBLock Error Rate

BSSBase Station Sub-system

CCCHCommon Control Channel

CCPCHCommon Control Physical CHannel

CHConditional on history

CMConnection Management

CNCore Network

CPCHCommon Packet CHannel

C-RNTICell RNTI

CTCHCommon Traffic CHannel

CTFCCalculated Transport Format Combination

CVConditional on value

DCADynamic Channel Allocation

DCCHDedicated Control Channel

DCFEDedicated Control Functional Entity

DCHDedicated Channel

DC-SAPDedicated Control SAP

DGPSDifferential Global Positioning System

DLDownlink

DRACDynamic Resource Allocation Control

DSCHDownlink Shared Channel

DTCHDedicated Traffic Channel

FACHForward Access Channel

FDDFrequency Division Duplex

FFSFor Further Study

GC-SAPGeneral Control SAP

HCSHierarchical Cell Structure

HFNHyper Frame Number

IDIdentifier

IDNNSIntra Domain NAS Node Selector

IEInformation element

IETFInternet Engineering Task Force

IMEIInternational Mobile Equipment Identity

IMSIInternational Mobile Subscriber Identity

IPInternet Protocol

ISCPInterference on Signal Code Power

L1Layer 1

L2Layer 2

L3Layer 3

LAILocation Area Identity

MACMedia Access Control

MCCMobile Country Code

MDMandatory default

MMMobility Management

MNCMobile Network Code

MPMandatory present

NASNon Access Stratum

Nt-SAPNotification SAP

NWNetwork

OPOptional

PCCHPaging Control Channel

PCHPaging Channel

PDCPPacket Data Convergence Protocol

PDSCHPhysical Downlink Shared Channel

PDUProtocol Data Unit

PLMNPublic Land Mobile Network

PNFEPaging and Notification Control Functional Entity

PRACHPhysical Random Access CHannel

P-TMSIPacket Temporary Mobile Subscriber Identity

PUSCHPhysical Uplink Shared Channel

QoSQuality of Service

RABRadio access bearer

RACHRandom Access CHannel

RAIRouting Area Identity

RATRadio Access Technology

RBRadio Bearer

RFERouting Functional Entity

RLRadio Link

RLCRadio Link Control

RNCRadio Network Controller

RNTIRadio Network Temporary Identifier

RRCRadio Resource Control

RSCPReceived Signal Code Power

RSSIReceived Signal Strength Indicator

SAPService Access Point

SCFEShared Control Function Entity

SCTDSpace Code Transmit Diversity

SFSpreading Factor

SHCCHShared Control Channel

SIRSignal to Interference Ratio

S-RNTISRNC - RNTI

SSDTSite Selection Diversity Transmission

TDDTime Division Duplex

TFTransport Format

TFCSTransport Format Combination Set

TFSTransport Format Set

TMTransparent Mode

TMETransfer Mode Entity

TMSITemporary Mobile Subscriber Identity

TrTransparent

TxTransmission

UEUser Equipment

ULUplink

UMUnacknowledged Mode

URAUTRAN Registration Area

U-RNTIUTRAN-RNTI

USCHUplink Shared Channel

UTRANUniversal Terrestrial Radio Access Network

4General

If not specified differently, descriptions are relevant for both FDD and TDD. Descriptions for TDD only are relevant for both 1.28 Mcps TDD and 3.84 Mcps TDD if not specified differently.

4.1Overview of the specification

This specification is organised as follows:

-subclause 4.2 contains the description of the model of the RRC protocol layer;

-clause 5 lists the RRC functions and the services provided to upper layers;

-clause 6 lists the services expected from the lower layers and specifies the radio bearers available for usage by the RRC messages;

-clause 7 specifies the UE states for the Access Stratum, and also specifies the processes running in the UE in the respective states;

-clause 8 specifies RRC procedures, including UE state transitions;

-clause 9 specifies the procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity;

-clause 10 describes the message in a Tabular format; these messages descriptions are referenced in clause 8;

-clause 11 specifies the encoding of the messages of the RRC protocol. This is based on the Tabular description in clause 10.

-clause 12 specifies the transfer syntax for RRC PDUs derived from the encoding definition;

-clause 13 lists the protocol timers, counters, constants and variables to be used by the UE;

-clause 14 specifies some of the processes applicable in UTRA RRC connected mode e.g. measurement processes, and also the RRC information to be transferred between network nodes. Note that not all the processes applicable in UTRA RRC connected mode are specified here i.e. some UTRA RRC connected mode processes are described in [4] e.g. cell re-selection;

-Annex A contains recommendations about the network parameters to be stored on the USIM;

-Annex B contains informative Stage 2 description of the RRC protocol states and state transitions.

The following figure summarises the mapping of UE states, including states in GSM, to the appropriate UTRA and GSM specifications that specify the UE behaviour.

UE switch-on

GSM

connected

GSM TS 04.18

GPRS

Packet Transfer

GSM TS 04.60

UE

connected

3GPP TS 25.331

UE Idle

3GPP TS

25.304

TS 23.122

GSM idle

GSM TS

05.08

UE idle

3GPP TS 25.304

3GPP TS 25.331

URA_PCH

3GPP TS 25.331

3GPP TS 25.304

CELL_FACH

3GPP TS 25.331

3GPP TS 25.304

CELL_PCH

3GPP TS 25.331

3GPP TS 25.304

CELL_DCH

3GPP TS

25.331

Figure 4.1-1: Mapping of UE state to 3GPP Specifications

4.2RRC Layer Model

The functional entities of the RRC layer are described below:

-Routing of higher layer messages to different MM/CM entities (UE side) or different core network domains (UTRAN side) is handled by the Routing Function Entity (RFE).

-Broadcast functions are handled in the broadcast control function entity (BCFE). The BCFE is used to deliver the RRC services, which are required at the GC-SAP. The BCFE can use the lower layer services provided by the Tr-SAP and UM-SAP.

-Paging of UEs that do not have an RRC connection is controlled by the paging and notification control function entity (PNFE). The PNFE is used to deliver the RRC services that are required at the Nt-SAP. The PNFE can use the lower layer services provided by the Tr-SAP and UM-SAP.

-The Dedicated Control Function Entity (DCFE) handles all functions specific to one UE. The DCFE is used to deliver the RRC services that are required at the DC-SAP and can use lower layer services of UM/AM-SAP and Tr-SAP depending on the message to be sent and on the current UE service state.

-In TDD mode, the DCFE is assisted by the Shared Control Function Entity (SCFE) location in the C-RNC, which controls the allocation of the PDSCH and PUSCH using lower layers services of UM-SAP and Tr-SAP.

-The Transfer Mode Entity (TME) handles the mapping between the different entities inside the RRC layer and the SAPs provided by RLC.

NOTE 1:Logical information exchange is necessary also between the RRC sublayer functional entities. Most of that is implementation dependent and not necessary to present in detail in a specification.

Figure 4.2-1 shows the RRC model for the UE and Figure 4.2-2 and Figure 4.2-3 show the RRC model for the UTRAN.

NOTE 2:The figure shows only the types of SAPs that are used. Multiple instances of Tr-SAP, UM-SAP and AM-SAP are possible. Especially, different functional entities usually use different instances of SAP types.

RLC

BCFE

PNFE

DCFE

MAC

MAC

ctrl

AM SAP

Tr-SAP

RLC-

ctrl

L1

L1-ctrl

UM SAP

RFE

RFE

NAS

DC-SAP

GC-SAP

RRC

Nt-SAP

RFE

NAS

...

...

...

...

...

...

GC-SAP

GC-SAP

Nt-SAP

Nt-SAP

DC-SAP

DC-SAP

TME

Access Stratum

RRC

SAPs

SCFE

Figure 4.2-1: UE side model of RRC

RLC

BCFE

PNFE

DCFE

RRC

MAC

MAC

ctrl

AM SAP

Tr-SAP

RLC-

ctrl

L1

L1-ctrl

UM SAP

RFE

RFE

RFE

...

...

...

TME

Access Stratum

RRC

SAPs

SCFE

Figure 4.2-2: UTRAN side RRC model (DS-MAP system)

RLC

DC-SAP

GC-SAP

BCFE

PNFE

DCFE

RRC

MAC

MAC

ctrl

AM SAP

Nt-SAP

RFE

DC-SAP

Tr-SAP

RLC-

ctrl

L1

L1-ctrl

RFE

RFE

NAS

NAS

...

...

...

UM SAP

...

...

...

GC-SAP

GC-SAP

Nt-SAP

Nt-SAP

DC-SAP

DC-SAP

TME

SCFE

Figure 4.2-3: UTRAN side RRC model (DS-41 System)

4.3Protocol specification principles

This protocol specification is based on the applicable general guidelines given in [14].

In this specification, a notation of variables is used. The variables are defined in subclause 13.4. Variables are typically used to represent a status or a result of an action, such as reception of an information element in a message, which is used to specify a behaviour somewhere else in the specification, such as when setting the value of an information element in a transmitted message. The variables only serve the purpose of specifying the protocol, and do not therefore impose any particular implementation.

When specifying the UE behaviour at reception of messages, the behaviour that is tied to reception or non-reception of individual information elements, and in some cases combinations of information elements, is specified in one location (subclause 8.6).

5RRC Functions and Services provided to upper layers

5.1RRC Functions

The RRC performs the functions listed below. A more detailed description of these functions is provided in [2]:

-Broadcast of information related to the non-access stratum (Core Network);

-Broadcast of information related to the access stratum;

-Establishment, maintenance and release of an RRC connection between the UE and UTRAN;

-Establishment, reconfiguration and release of Radio Bearers;

-Assignment, reconfiguration and release of radio resources for the RRC connection;

-RRC connection mobility functions;

-Control of requested QoS;

-UE measurement reporting and control of the reporting;

-Outer loop power control;

-Control of ciphering;

-Slow DCA (TDD mode);

-Paging;

-Initial cell selection and cell re-selection;

-Arbitration of radio resources on uplink DCH;

-RRC message integrity protection;

-Timing advance (TDD mode);

-CBS control.

5.2RRC Services provided to upper layers

The RRC offers the following services to upper layers, a description and primitives of these services are provided in [2] and [17].

-General Control;

-Notification;

-Dedicated control.

The RRC layer provides the UE-UTRAN portion of signalling connections to the upper layers to support the exchange of upper layer's information flow. The signalling connection is used between the user equipment and the core network to transfer upper layer information. For each core network domain, at most one signalling connection may exist at the same time. The RRC layer maps the signalling connections for one UE on a single RRC connection. For the upper layer data transfer on signalling connections, the RRC layer supports the discrimination between two different classes, named "High priority" (corresponding to "SAPI 0" for a GSM-MAP based core network) and "Low priority" (corresponding to "SAPI 3" for a GSM-MAP based core network).

5.3Primitives between RRC and upper layers

The primitives between RRC and the upper layers are described in [17].

6Services expected from lower layers


The services provided by layer 2 are described in [2], [15] and [16].


The services provided by layer 1 are described in [2].

6.3Signalling Radio Bearers

The Radio Bearers (RB) available for transmission of RRC messages are defined as "signalling radio bearers" and are specified in the following. The UE and UTRAN shall select the signalling radio bearers for RRC messages using RLC-TM, RLC-UM or RLC-AM on the DCCH and CCCH, according to the following:

-Signalling radio bearer RB0 shall be used for all messages sent on the CCCH (UL: RLC-TM, DL: RLC-UM).

-Signalling radio bearer RB1 shall be used for all messages sent on the DCCH, when using RLC unacknowledged mode (RLC-UM).

-Signalling radio bearer RB2 shall be used for all messages sent on the DCCH, when using RLC acknowledged mode (RLC-AM), except for the RRC messages carrying higher layer (NAS) signalling.

-Signalling radio bearer RB3 and optionally Signalling radio bearer RB4 shall be used for the RRC messages carrying higher layer (NAS) signalling and sent on the DCCH in RLC acknowledged mode (RLC-AM), as specified in subclauses 8.1.8., 8.1.9 and 8.1.10.

-Additionally, RBs whose identities shall be set between 5 and 32 may be used as signalling radio bearer for the RRC messages on the DCCH sent in RLC transparent mode (RLC-TM).

-RRC messages on the SHCCH are mapped either on RACH or on the USCH in the uplink using TM and either on FACH or on the DSCH using RLC-UM. These messages are only specified for TDD mode.

The Radio Bearer configuration for signalling radio bearer RB0, SHCCH, BCCH on FACH and PCCH on PCH are specified in subclauses 13.6, 13.6a, 13.6b and 13.6c.

7Protocol states

7.1Overview of RRC States and State Transitions including GSM

Figure 7.1-1 shows the RRC states in UTRA RRC Connected Mode, including transitions between UTRA RRC connected mode and GSM connected mode for CS domain services, and between UTRA RRC connected mode and GSM/GPRS packet modes for PS domain services. It also shows the transitions between Idle Mode and UTRA RRC Connected Mode and furthermore the transitions within UTRA RRC connected mode.

Establish RRC

Connection

Release RRC

Connection

UTRA RRC Connected Mode

UTRA:

Inter-RAT

Handover

GSM:

Handover

Establish RRC

Connection

Release RRC

Connection

URA_PCH

CELL_PCH

GSM

Connected

Mode

Establish RR

Connection

Release RR

Connection

Idle Mode

Camping on a UTRAN cell

1

Camping on a GSM / GPRS cell

1

GPRS Packet Idle Mode

1

GPRS

Packet

Transfer

Mode

Initiation of

temporary

block flow

Release of

temporary

block flow

Cell reselection

CELL_DCH

out of

service

in

service

CELL_FACH

out of

service

in

service

out of

service

in

service

NOTE:1: The indicated division within Idle Mode is only included for clarification and shall not be interpreted as states.

Figure 7.1-1: RRC States and State Transitions including GSM

The RRC connection is defined as a point-to-point bi-directional connection between RRC peer entities in the UE and the UTRAN characterised by the allocation of a U-RNTI. A UE has either zero or one RRC connection.

NOTE:The state transitions are specified in clause 8.

7.2Processes in UE modes/states

NOTE:This subclause specifies what processes shall be active in the UE in the different RRC modes/states. The related procedures and the conditions on which they are triggered are specified either in clause 8 or elsewhere in the relevant process definition.

7.2.1UE Idle mode

UE processes that are active in UE Idle mode are specified in [4].

The UE shall perform a periodic search for higher priority PLMNs as specified in [25].

7.2.2UTRA RRC Connected mode

In this specification unless otherwise mentioned "connected mode" shall refer to "UTRA RRC connected mode".

7.2.2.1URA_PCH or CELL_PCH state

In the URA_PCH or CELL_PCH state the UE shall perform the following actions:

NOTE:Neither DCCH nor DTCH are available in these states.

1>if the UE is "in service area":

2>maintain up-to-date system information as broadcast by the serving cell as specified in the subclause 8.1.1;

2>perform cell reselection process as specified in [4];

2>perform a periodic search for higher priority PLMNs as specified in [25];

NOTE:If the DRX cycle length is 80ms, then a search for higher priority PLMNs may not identify all the available PLMNs due to the paging occasion on the current serving cell coinciding with the MIB of the cell of interest.

2>monitor the paging occasions and PICH monitoring occasions determined according to subclauses 8.6.3.1a and 8.6.3.2 and receive paging information on the PCH mapped on the S-CCPCH selected by the UE according to the procedure in subclause 8.5.19;

2>act on RRC messages received on PCCH and BCCH;

2>perform measurements process according to measurement control information as specified in subclause 8.4 and in subclause 14.4;

2>maintain up-to-date BMC data if it supports Cell Broadcast Service (CBS) as specified in [37];

2>run timer T305 for periodical URA update if the UE is in URA_PCH or for periodical cell update if the UE is in CELL_PCH.

1>if the UE is "out of service area":


2>run timer T316;

2>run timer T305.

7.2.2.2CELL_FACH state

In the CELL_FACH state the UE shall perform the following actions:

NOTE:DCCH and, if configured, DTCH are available in this state.

1>if the UE is "in service area":

2>maintain up-to-date system information as broadcast by the serving cell as specified in subclause 8.1.1;


2>perform measurements process according to measurement control information as specified in subclause 8.4 and in subclause 14.4;

2>run timer T305 (periodical cell update);

2>listen to all FACH transport channels mapped on the S-CCPCH selected by the UE according to the procedure in subclause 8.5.19;

2>act on RRC messages received on BCCH, CCCH and DCCH;

2>act on RRC messages received on, if available, SHCCH (TDD only).

1>if the UE is "out of service area":


2>run timers T305 (periodical cell update), and T317 (cell update when re-entering "in service") or T307 (transition to Idle mode).

7.2.2.3CELL_DCH state

In the CELL_DCH state the UE shall perform the following actions:

NOTE:DCCH and, if configured, DTCH are available in this state.

1>read system information broadcast on FACH as specified in subclause 8.1.1.3 (applicable only to UEs with certain capabilities and in FDD mode);

1>read the system information as specified in subclause 8.1.1 (for UEs in TDD mode);

1>perform measurements process according to measurement control information as specified in subclause 8.4 and in clause 14;

1>act on RRC messages received on DCCH;

1>act on RRC messages received on BCCH (applicable only to UEs with certain capabilities and in FDD mode);

1>act on RRC messages received on BCCH (TDD only) and, if available, SHCCH (TDD only).

8RRC procedures

The UE shall be able to process several simultaneous RRC

Documents

3GPP TS 25.331 - ccsa.org.cn€¦ · Web view · 2003-12-121> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" (FDD only) when