1 571 - PLMN

3GPP TS 34.123-1 V5.7.
1 (2004-04)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Terminals;
User Equipment (UE) conformance specification;
Part 1: Protocol conformance specification
(Release 5)
The present document has been developed within the 3
rd
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
systemshould be obtained via the 3GPP Organisational Partners Publications Offices.
Release 5 2 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

Keywords
mobile, MS, terminal, testing, UMTS
3GPP
Postal address

3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

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

Release 5 3 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Contents
Foreword........................................................................................................................................................... 31
Introduction ...................................................................................................................................................... 31
1 Scope ...................................................................................................................................................... 32
2 References .............................................................................................................................................. 32
3 Definitions and abbreviations ................................................................................................................. 34
3.1 Definitions ....................................................................................................................................................... 34
3.2 Abbreviations ................................................................................................................................................... 34
4 Overview ................................................................................................................................................ 34
4.1 Test Methodology ............................................................................................................................................ 34
4.1.1 Testing of optional functions and procedures ............................................................................................ 34
4.1.2 Test interfaces and facilities ....................................................................................................................... 34
4.2 Implicit Testing ................................................................................................................................................ 34
5 Reference Conditions ............................................................................................................................. 35
5.1 Generic setup procedures ................................................................................................................................. 35
6 Idle mode operations .............................................................................................................................. 35
6.1 In a pure 3GPP environment ............................................................................................................................ 39
6.1.1 PLMN selection ......................................................................................................................................... 39
6.1.1.1 PLMN selection of RPLMN, HPLMN, UPLMN and OPLMN; Manual mode ................................... 39
6.1.1.2 PLMN selection of "Other PLMN / access technology combinations"; Manual mode ........................ 42
6.1.1.3 PLMN selection; independence of RF level and preferred PLMN; Manual mode ............................... 44
6.1.1.4 PLMN selection of RPLMN, HPLMN, UPLMN and OPLMN; Automatic mode ............................... 47
6.1.1.5 PLMN selection of "Other PLMN / access technology combinations"; Automatic mode ................... 49
6.1.1.6 Void ...................................................................................................................................................... 52
6.1.1.7 Cell reselection of ePLMN in manual mode ........................................................................................ 52
6.1.2 Cell selection and reselection ..................................................................................................................... 53
6.1.2.1 Cell reselection ..................................................................................................................................... 53
6.1.2.2 Cell reselection using Qhyst, Qoffset and Treselection ........................................................................ 56
6.1.2.3 HCS Cell reselection ............................................................................................................................ 59
6.1.2.4 HCS Cell reselection using reselection timing parameters for the H criterion ..................................... 62
6.1.2.5 HCS Cell reselection using reselection timing parameters for the R criterion .................................... 65
6.1.2.6 Emergency calls .................................................................................................................................... 67
6.1.2.7 Emergency calls; Intra-frequency cell "Not allowed" .......................................................................... 69
6.1.2.8 Cell reselection: Equivalent PLMN ...................................................................................................... 71
6.1.2.9 Cell reselection using cell status and cell reservations ......................................................................... 75
6.2 Multi-mode environment (2G/3G case) ........................................................................................................... 78
6.2.1 PLMN and RAT selection .......................................................................................................................... 78
6.2.1.1 Selection of the correct PLMN and associated RAT ............................................................................ 78
6.2.1.2 Selection of RAT for HPLMN; Manual mode ..................................................................................... 80
6.2.1.3 Selection of RAT for UPLMN; Manual mode ..................................................................................... 83
6.2.1.4 Selection of RAT for OPLMN; Manual mode ..................................................................................... 85
6.2.1.5 Selection of "Other PLMN / access technology combinations"; Manual mode ................................... 87
6.2.1.6 Selection of RAT for HPLMN; Automatic mode ................................................................................. 90
6.2.1.7 Selection of RAT for UPLMN; Automatic mode ................................................................................. 92
6.2.1.8 Selection of RAT for OPLMN; Automatic mode ................................................................................. 94
6.2.1.9 Selection of "Other PLMN / access technology combinations"; Automatic mode ............................... 96
6.2.2 Cell selection and reselection ..................................................................................................................... 98
6.2.2.1 Cell reselection if cell becomes barred or S<0; UTRAN to GSM ........................................................ 98
6.2.2.2 Cell reselection if cell becomes barred or C1<0; GSM to UTRAN ................................................... 100
6.2.2.3 Cell reselection timings; GSM to UTRAN ......................................................................................... 104
7 Layer 2 ................................................................................................................................................. 109
7.1 MAC .............................................................................................................................................................. 109
Release 5 4 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.1 Mapping between logical channels and transport channels ...................................................................... 109
7.1.1.1 CCCH mapped to RACH/FACH / Invalid TCTF ............................................................................... 109
7.1.1.2 DTCH or DCCH mapped to RACH/FACH / Invalid TCTF .............................................................. 115
7.1.1.3 DTCH or DCCH mapped to RACH/FACH / Invalid C/T Field ......................................................... 118
7.1.1.4 DTCH or DCCH mapped to RACH/FACH / Invalid UE ID Type Field ........................................... 121
7.1.1.5 DTCH or DCCH mapped to RACH/FACH / Incorrect UE ID ........................................................... 123
7.1.1.6 DTCH or DCCH mapped to DSCH or USCH .................................................................................... 125
7.1.1.7 DTCH or DCCH mapped to CPCH .................................................................................................... 127
7.1.1.8 DTCH or DCCH mapped to DCH / Invalid C/T Field ....................................................................... 130
7.1.2 RACH/FACH procedures ........................................................................................................................ 134
7.1.2.1 Selection and control of Power Level ................................................................................................. 134
7.1.2.1.1 Void .............................................................................................................................................. 134
7.1.2.1.2 Selection and control of Power Level (3,84 Mcps TDD option) .................................................. 134
7.1.2.1.3 Selection and control of Power Level (1,28 Mcps TDD option) .................................................. 134
7.1.2.2 Correct application of Dynamic Persistence ....................................................................................... 135
7.1.2.2.1 Void .............................................................................................................................................. 135
7.1.2.2.2 Correct application of Dynamic Persistence (3.84 Mcps TDD option) ........................................ 135
7.1.2.2.3 Correct application of Dynamic Persistence (1.28 Mcps TDD option) ........................................ 136
7.1.2.3 Correct Selection of RACH parameters.............................................................................................. 137
7.1.2.3.1 Correct Selection of RACH parameters (FDD) ............................................................................ 137
7.1.2.3.2 Correct Selection of RACH parameters (3.84 Mcps TDD option) ............................................... 141
7.1.2.3.3 Correct Selection of RACH parameters (1.28 Mcps TDD option) ............................................... 141
7.1.2.4 Correct Detection and Response to FPACH (1.28 Mcps TDD option) .............................................. 142
7.1.2.4a Access Service class selection for RACH transmission ..................................................................... 145
7.1.2.5 Void .................................................................................................................................................... 148
7.1.3 Priority handling between data flows of one UE ...................................................................................... 148
7.1.3.1 Priority handling between data flows of one UE ................................................................................ 148
7.1.4 Control of CPCH transmissions. .............................................................................................................. 150
7.1.4.1 Control of CPCH transmissions for FDD ........................................................................................... 150
7.1.5 HS-DSCH MAC-hs .................................................................................................................................. 157
7.1.5.1 MAC-hs reordering and stall avoidance ............................................................................................. 157
7.1.5.2 Priority queue handling ...................................................................................................................... 161
7.1.5.3 MAC-hs PDU header handling ........................................................................................................... 162
7.1.5.4 MAC-hs retransmissions .................................................................................................................... 165
7.2 RLC testing .................................................................................................................................................... 167
7.2.1 Transparent mode ..................................................................................................................................... 167
7.2.1.1 Segmentation and reassembly............................................................................................................. 167
7.2.2 Unacknowledged mode ............................................................................................................................ 168
7.2.2.1 General information for UM tests ....................................................................................................... 168
7.2.2.2 Segmentation and reassembly / Selection of 7 or 15 bit "Length Indicators" ..................................... 168
7.2.2.3 Segmentation and reassembly / 7-bit "Length Indicators" / Padding ................................................. 170
7.2.2.4 Segmentation and Reassembly / 7-bit "Length Indicators" / LI =0 ................................................... 171
7.2.2.5 Reassembly / 7-bit "Length Indicators" / Invalid LI value ................................................................. 173
7.2.2.6 Reassembly / 7-bit "Length Indicators" / LI value >PDU size .......................................................... 174
7.2.2.7 Reassembly / 7-bit "Length Indicators" / First data octet LI .............................................................. 175
7.2.2.8 Segmentation and reassembly / 15-bit "Length Indicators" / Padding................................................ 177
7.2.2.9 Segmentation and Reassembly / 15-bit "Length Indicators" / LI =0 ................................................. 178
7.2.2.10 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short LI................................ 179
7.2.2.11 Reassembly / 15-bit "Length Indicators" / Invalid LI value ............................................................... 181
7.2.2.12 Reassembly / 15-bit "Length Indicators" / LI value >PDU size ........................................................ 182
7.2.2.13 Reassembly / 15-bit "Length Indicators" / First data octet LI ............................................................ 183
7.2.3 Acknowledged mode ................................................................................................................................ 184
7.2.3.1 General information for AM tests ....................................................................................................... 184
7.2.3.2 Segmentation and reassembly / Selection of 7 or 15 bit Length Indicators ........................................ 185
7.2.3.3 Segmentation and Reassembly / 7-bit "Length Indicators" / Padding or Piggy-backed Status .......... 187
7.2.3.4 Segmentation and Reassembly / 7-bit "Length Indicators" / LI =0 ................................................... 189
7.2.3.5 Reassembly / 7-bit "Length Indicators" / Reserved LI value .............................................................. 191
7.2.3.6 Reassembly / 7-bit "Length Indicators" / LI value >PDU size .......................................................... 192
7.2.3.7 Segmentation and Reassembly / 15-bit "Length Indicators" / Padding or Piggy-backed Status ........ 194
7.2.3.8 Segmentation and Reassembly / 15-bit "Length Indicators" / LI =0 ................................................. 195
Release 5 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.3.9 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short LI................................ 196
7.2.3.10 Reassembly / 15-bit "Length Indicators" / Reserved LI value ............................................................ 198
7.2.3.11 Reassembly / 15-bit "Length Indicators" / LI value >PDU size ........................................................ 199
7.2.3.12 Correct use of Sequence Numbering .................................................................................................. 200
7.2.3.13 Control of Transmit Window.............................................................................................................. 202
7.2.3.14 Control of Receive Window ............................................................................................................... 206
7.2.3.15 Polling for status / Last PDU in transmission queue .......................................................................... 208
7.2.3.16 Polling for status / Last PDU in retransmission queue ....................................................................... 210
7.2.3.17 Polling for status / Poll every Poll_PDU PDUs .................................................................................. 212
7.2.3.18 Polling for status / Poll every Poll_SDU SDUs .................................................................................. 214
7.2.3.19 Polling for status / Timer triggered polling (Timer_Poll_Periodic).................................................... 216
7.2.3.20 Polling for status / Polling on Poll_Window% of transmission window ............................................ 218
7.2.3.21 Polling for status / Operation of Timer_Poll timer / Timer expiry ..................................................... 220
7.2.3.22 Polling for status / Operation of Timer_Poll timer / Stopping Timer_Poll timer ............................... 222
7.2.3.23 Polling for status / Operation of Timer_Poll timer / Restart of the Timer_Poll timer ........................ 225
7.2.3.24 Polling for status / Operation of timer Timer_Poll_Prohibit .............................................................. 227
7.2.3.25 Receiver Status Triggers / Detection of missing PDUs ...................................................................... 229
7.2.3.26 Receiver Status Triggers / Operation of timer Timer_Status_Periodic .............................................. 231
7.2.3.27 Receiver Status Triggers / Operation of timer Timer_Status_Prohibit ............................................... 232
7.2.3.28 Status reporting / Abnormal conditions / Reception of LIST SUFI with Length set to zero .............. 234
7.2.3.29 Timer based discard, with explicit signalling / Expiry of Timer_Discard .......................................... 236
7.2.3.29a Timer based discard, with explicit signalling / Expiry of Timer_Discard when
Timer_STATUS_prohibit is active ..................................................................................................... 238
7.2.3.30 Timer based discard, with explicit signalling / Obsolete MRW_ACK ............................................... 239
7.2.3.31 Timer based discard, with explicit signalling / Failure of MRW procedure ....................................... 241
7.2.3.32 SDU discard after MaxDAT-1 number of transmissions.................................................................... 243
7.2.3.33 Operation of the RLC Reset procedure / UE Originated .................................................................... 245
7.2.3.34 Operation of the RLC Reset procedure / UE Terminated ................................................................... 249
7.2.3.35 Reconfiguration of RLC parameters by upper layers ......................................................................... 251
7.3 PDCP ............................................................................................................................................................. 254
7.3.1 General ..................................................................................................................................................... 254
7.3.1.1 General assumptions ........................................................................................................................... 254
7.3.1.2 Common Test sequences and Default message contents for PDCP ................................................... 254
7.3.1.2.1 Common Test sequences for PDCP .............................................................................................. 254
7.3.1.2.2 Default PDCP Message Contents ................................................................................................. 257
7.3.2 IP Header Compression and PID assignment ........................................................................................... 259
7.3.2.1 UE in RLC AM .................................................................................................................................. 259
7.3.2.1.1 Transmission of uncompressed Header ........................................................................................ 259
7.3.2.1.2 Transmission of compressed Header ............................................................................................ 267
7.3.2.2 UE in RLC UM .................................................................................................................................. 275
7.3.2.2.1 Transmission of uncompressed Header ........................................................................................ 275
7.3.2.2.2 Transmission of compressed Header ............................................................................................ 283
7.3.2.2.3 Extension of used compression methods ...................................................................................... 290
7.3.2.2.4 Compression type used for different entities................................................................................. 296
7.3.2.2.5 Reception of not defined PID values ............................................................................................ 302
7.3.3 PDCP sequence numbering when lossless SRNS Relocation .................................................................. 306
7.3.3.1 Data transmission if lossless SRNS Relocation is supported ............................................................. 306
7.3.3.2 Synchronisation of PDCP sequence numbers ..................................................................................... 311
7.3.3.3 PDCP Sequence Numbering and Data Forwarding - Reception of reserved PDU type .................... 317
7.3.3.4 PDCP Sequence Number synchronization Reception of invalid next expected receive Sequence
Number ............................................................................................................................................... 317
7.3.3.5 UTRAN MOBILITY INFORMATION: Lossless SRNS relocation in CELL_FACH (without
pending of ciphering).......................................................................................................................... 317
7.3.3.6 Cell Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering) ................ 327
7.3.3.7 URA Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering) .............. 339
7.3.3.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success (Lossless
SRNS relocation) (without pending of ciphering) .............................................................................. 351
7.3.3.9 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH: Success
(Lossless SRNS relocation) (without pending of ciphering) .............................................................. 365
Release 5 6 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.3.10 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS
relocation) (without pending of ciphering) ......................................................................................... 380
7.3.3.11 Transport Channel Reconfiguration for transition from CELL_DCH to CELL_DCH: Success
(Lossless SRNS relocation) (without pending of ciphering) .............................................................. 390
7.3.4 PDCP configuration testing ...................................................................................................................... 401
7.3.4.1 PDCP configuration behaviour while RRC Radio bearer setup procedure ........................................ 401
7.3.4.2 PDCP configuration behaviour while RRC Radio bearer release procedure ...................................... 401
7.3.4.3 PDCP configuration behaviour while RRC Cell Update procedure ................................................... 401
7.3.4.4 PDCP configuration behaviour for an invalid RRC configuration ..................................................... 401
7.4 BMC .............................................................................................................................................................. 401
7.4.1 BMC RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH ...................................................... 402
7.4.1.1 Transport channel parameters of BMC RAB and SRBs for CCCH, SRB for DCCH, and SRB for
BCCH ................................................................................................................................................. 402
7.4.1.2 TFCS .................................................................................................................................................. 402
7.4.1.3 Physical channel parameters ............................................................................................................... 402
7.4.2 General BMC message reception ............................................................................................................. 403
7.4.2.1 UE in RRC Idle mode ......................................................................................................................... 403
7.4.2.2 UE in RRC Connected mode, state CELL_PCH ................................................................................ 405
7.4.2.3 UE in RRC Connected mode, state URA_PCH.................................................................................. 407
7.4.2.4 UE in RRC Idle mode (ANSI-41 CB data)......................................................................................... 409
7.4.2.5 UE in RRC Connected mode, state CELL_PCH (ANSI-41 CB data) ................................................ 412
7.4.2.6 UE in RRC Connected mode, state URA_PCH (ANSI-41 CB data) ................................................. 414
7.4.3 BMC message reception procedure .......................................................................................................... 417
7.4.3.1 Reception of certain CBS message types ........................................................................................... 417
8 Radio Resource Control RRC .............................................................................................................. 422
8.1 RRC Connection Management Procedure ..................................................................................................... 422
8.1.1 Paging....................................................................................................................................................... 422
8.1.1.1 Paging for Connection in idle mode ................................................................................................... 422
8.1.1.2 Paging for Connection in connected mode (CELL_PCH) .................................................................. 426
8.1.1.3 Paging for Connection in connected mode (URA_PCH) ................................................................... 429
8.1.1.4 Paging for notification of BCCH modification in idle mode .............................................................. 432
8.1.1.5 Paging for notification of BCCH modification in connected mode (CELL_PCH) ............................ 436
8.1.1.6 Paging for notification of BCCH modification in connected mode (URA_PCH) .............................. 440
8.1.1.7 Paging for Connection in connected mode (CELL_DCH) ................................................................. 444
8.1.1.8 Paging for Connection in connected mode (CELL_FACH) .............................................................. 448
8.1.1.9 Paging for Connection in idle mode (multiple paging records) .......................................................... 450
For speech in CS: 455
For packet in PS: 455
8.1.1.10 Paging for Connection in connected mode (URA_PCH, multiple paging records) ............................ 457
8.1.2 RRC Connection Establishment ............................................................................................................... 460
8.1.2.1 RRC Connection Establishment in CELL_DCH state: Success ......................................................... 460
8.1.2.2 RRC Connection Establishment: Success after T300 timeout ............................................................ 465
Contents of System Information Block type 7 (FDD) (Step 1b).................................................................................. 479
8.1.2.3 RRC Connection Establishment: Failure (V300 is greater than N300) .............................................. 479
8.1.2.4 RRC Connection Establishment: Reject ("wait time" is not equal to 0) ............................................. 482
8.1.2.5 RRC Connection Establishment: Reject ("wait time" is not equal to 0 and V300 is greater than
N300) .................................................................................................................................................. 486
8.1.2.6 RRC Connection Establishment: Reject ("wait time" is set to 0) ....................................................... 489
8.1.2.7 RRC Connection Establishment in CELL_FACH state: Success ....................................................... 491
8.1.2.8 Void .................................................................................................................................................... 495
8.1.2.9 RRC Connection Establishment: Success after Physical channel failure and Failure after Invalid
configuration....................................................................................................................................... 495
8.1.2.10 RRC connection establishment in CELL_DCH on another frequency ............................................... 499
8.1.2.11 RRC Connection Establishment in FACH state (Frequency band modification): Success ................ 503
8.1.3 RRC Connection Release ......................................................................................................................... 507
8.1.3.1 RRC Connection Release in CELL_DCH state: Success ................................................................... 507
8.1.3.2 RRC Connection Release using on DCCH in CELL_FACH state: Success ...................................... 509
8.1.3.3 RRC Connection Release using on CCCH in CELL_FACH state: Success ...................................... 511
8.1.3.4 RRC Connection Release in CELL_FACH state: Failure .................................................................. 512
8.1.3.5 RRC Connection Release in CELL_FACH state: Invalid message .................................................... 514
Release 5 7 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.1.3.6 RRC Connection Release in CELL_DCH state (Frequency band modification): Success ................. 516
8.1.3.7 RRC Connection Release in CELL_FACH state (Frequency band modification): Success............... 521
8.1.3.8 Void .................................................................................................................................................... 524
8.1.3.9 RRC Connection Release in CELL_DCH state (Network Authentication Failure): Success ............. 524
8.1.4 Void .......................................................................................................................................................... 530
8.1.5 UE capability ............................................................................................................................................ 530
8.1.5.1 UE Capability in CELL_DCH state: Success ..................................................................................... 530
8.1.5.2 UE Capability in CELL_DCH state: Success after T304 timeout ...................................................... 534
8.1.5.3 UE Capability in CELL_DCH state: Failure (After N304 re-transmissions) ..................................... 537
8.1.5.4 UE Capability in CELL_FACH state: Success ................................................................................... 541
8.1.5.5 UE Capability in CELL_FACH state: Success after T304 timeout .................................................... 545
8.1.6 Direct Transfer ......................................................................................................................................... 548
8.1.6.1 Direct Transfer in CELL DCH state (invalid message reception and no signalling connection
exists).................................................................................................................................................. 548
8.1.6.2 Direct Transfer in CELL FACH state (invalid message reception and no signalling connection
exists).................................................................................................................................................. 550
8.1.6.3 Measurement Report on INITIAL DIRECT TRANSFER message and UPLINK DIRECT
TRANSFER message ......................................................................................................................... 553
8.1.6.4 UPLINK Direct Transfer (RLC re-establishment) ............................................................................ 560
8.1.7 Security mode command .......................................................................................................................... 564
8.1.7.1 Security mode command in CELL_DCH state (CS Domain) ............................................................ 564
8.1.7.1b Security mode command in CELL_DCH state (PS Domain) ............................................................. 568
8.1.7.1c Security mode control in CELL_DCH state (CN Domain switch and new keys at RRC message
sequence number wrap around) .......................................................................................................... 574
8.1.7.1d Security mode control in CELL_DCH state interrupted by a cell update ........................................... 581
8.1.7.2 Security mode command in CELL_FACH state ................................................................................ 585
8.1.8 Counter check........................................................................................................................................... 589
8.1.8.1 Counter check in CELL_DCH state, with symmetric RAB ............................................................... 589
8.1.8.2 Counter check in CELL_FACH state ................................................................................................. 593
8.1.8.3 Counter check in CELL_DCH state, with asymmetric RAB .............................................................. 597
8.1.9 Signalling Connection Release Indication................................................................................................ 600
8.1.9a Signalling Connection Release Indication (RLC re-establishment): CS signalling connection release ... 603
8.1.9b Signalling Connection Release Indication (RLC re-establishment): PS signalling connection release ... 606
8.1.10 Broadcast of system information .............................................................................................................. 609
8.1.10.1 Dynamic change of segmentation, concatenation & scheduling and handling of unsupported
information blocks .............................................................................................................................. 609
Contents of Scheduling Block 1 (TDD 3.84 Mcps option) ............................................................................................. 616
8.1.11 Signalling Connection Release (Invalid configuration) ........................................................................... 618
8.1.12 Integrity Protection ............................................................................................................................. 621
8.2 Radio Bearer control procedure ..................................................................................................................... 624
8.2.1 Radio Bearer Establishment ..................................................................................................................... 624
8.2.1.1 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success .................... 624
8.2.1.3 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Failure
(Unsupported configuration) .............................................................................................................. 626
8.2.1.4 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Failure (Physical
channel Failure and successful reversion to old configuration) .......................................................... 629
8.2.1.5 Void .................................................................................................................................................... 633
8.2.1.6 Void .................................................................................................................................................... 633
8.2.1.7 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Failure (Invalid
message reception and Invalid configuration) .................................................................................... 633
8.2.1.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH: Success .................. 637
8.2.1.9 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH: Success (Cell re-
selection) ............................................................................................................................................ 640
8.2.1.10 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Success .................. 642
8.2.1.11 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Failure
(Unsupported configuration) .............................................................................................................. 644
8.2.1.12 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Failure (Physical
channel Failure and successful reversion to old configuration) .......................................................... 647
8.2.1.13 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Failure (Physical
channel Failure and cell reselection) .................................................................................................. 650
Release 5 8 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.2.1.14 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Failure
(Incompatible simultaneous reconfiguration) ..................................................................................... 654
8.2.1.15 Void .................................................................................................................................................... 657
8.2.1.16 Radio Bearer Establishment for transition from CELL_FACH to CELL_FACH: Success ............... 657
8.2.1.17 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: success
(Subsequently received) ..................................................................................................................... 659
8.2.1.18 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH: Success
8.2.1.19 Void .................................................................................................................................................... 664
8.2.1.20 Void .................................................................................................................................................... 664
8.2.1.21 Void .................................................................................................................................................... 664
8.2.1.22 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH (Frequency band
modification): Success ........................................................................................................................ 664
8.2.1.23 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH (Frequency band
8.2.1.24 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH (Frequency band
8.2.1.25 Radio Bearer Establishment for transition from CELL_FACH to CELL_FACH (Frequency band
8.2.1.26 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success
(Transparent mode with ciphering on)................................................................................................ 675
8.2.1.27 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success (two radio
links, start of HS-DSCH reception) .................................................................................................... 678
RADIO BEARER SETUP (Step 3) ................................................................................................................................ 681
8.2.2 Radio Bearer Reconfiguration .................................................................................................................. 682
8.2.2.1 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Success ...................................... 682
8.2.2.2 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Failure (Unsupported
configuration) ..................................................................................................................................... 690
8.2.2.3 Void .................................................................................................................................................... 693
8.2.2.4 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Failure (Physical channel
failure and cell reselection) ................................................................................................................. 693
8.2.2.5 Void .................................................................................................................................................... 698
8.2.2.6 Void .................................................................................................................................................... 698
8.2.2.7 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Success (Continue and stop) ...... 698
8.2.2.8 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Success .................................... 700
8.2.2.9 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Success (Cell re-selection) ...... 705
8.2.2.10 Radio Bearer Reconfiguration: from CELL_FACH to CELL_DCH including modification of
previously signalled CELL_DCH configuration: Success.................................................................. 710
8.2.2.11 Radio Bearer Reconfiguration from CELL_FACH to CELL_DCH: Failure (Unsupported
configuration) ..................................................................................................................................... 714
8.2.2.12 Void .................................................................................................................................................... 716
8.2.2.13 Void .................................................................................................................................................... 716
8.2.2.14 Void .................................................................................................................................................... 716
8.2.2.15 Void .................................................................................................................................................... 716
8.2.2.16 Void .................................................................................................................................................... 716
8.2.2.17 Radio Bearer Reconfiguration from CELL_FACH to CELL_FACH: Success .................................. 716
8.2.2.18 Radio Bearer Reconfiguration from CELL_FACH to CELL_FACH: Success (Cell re-selection) .... 720
8.2.2.19 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Success (Subsequently
received) ............................................................................................................................................. 725
8.2.2.20 Void .................................................................................................................................................... 739
8.2.2.21 Void .................................................................................................................................................... 739
8.2.2.22 Void .................................................................................................................................................... 739
8.2.2.23 Radio Bearer Reconfiguration from CELL_FACH to CELL_PCH: Success..................................... 739
8.2.2.24 Void .................................................................................................................................................... 744
8.2.2.25 Void .................................................................................................................................................... 744
8.2.2.26 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Success (Incompatible
Simultaneous Reconfiguration) .......................................................................................................... 744
8.2.2.27 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH (Frequency band
Release 5 9 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.2.2.28 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_FACH (Transport
channel type switching with frequency band modification): Success ................................................ 750
8.2.2.29 Void .................................................................................................................................................... 753
8.2.2.30 Void .................................................................................................................................................... 753
8.2.2.31 Radio Bearer Reconfiguration for transition from CELL_FACH to CELL_DCH (Frequency
band modification): Success ............................................................................................................... 753
8.2.2.32 Radio Bearer Reconfiguration for transition from CELL_FACH to CELL_FACH (Frequency
8.2.2.33 Void .................................................................................................................................................... 759
8.2.2.34 Radio Bearer Reconfiguration for transition from CELL_FACH to URA_PCH (Frequency band
8.2.2.35 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Successful channel switching
with multiple PS RABs established .................................................................................................... 762
8.2.2.36 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH: Success (Start
and stop of HS-DSCH reception) ....................................................................................................... 773
RADIO BEARER RECONFIGURATION (step 1) ....................................................................................................... 775
RADIO BEARER RECONFIGURATION (step 4) ....................................................................................................... 776
8.2.2.37 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_FACH and from
CELL_FACH to CELL_DCH: Success (start and stop of HS-DSCH reception) ............................... 777
RADIO BEARER RECONFIGURATION (Step 1) ...................................................................................................... 779
RADIO BEARER RECONFIGURATION (Step 3) ...................................................................................................... 782
8.2.3 Radio Bearer Release ............................................................................................................................... 783
8.2.3.1 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success .............................. 783
8.2.3.2 Void .................................................................................................................................................... 784
8.2.3.3 Void .................................................................................................................................................... 784
8.2.3.4 Void .................................................................................................................................................... 784
8.2.3.5 Void .................................................................................................................................................... 784
8.2.3.6 Void .................................................................................................................................................... 784
8.2.3.7 Radio Bearer Release for transition from CELL_DCH to CELL_FACH: Success ............................ 784
8.2.3.8 Radio Bearer Release for transition from CELL_DCH to CELL_FACH: Success (Cell re-
selection) ............................................................................................................................................ 787
8.2.3.9 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Success ............................ 790
8.2.3.10 Void .................................................................................................................................................... 791
8.2.3.11 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Failure (Physical
channel failure and successful reversion to old configuration) ........................................................... 791
8.2.3.12 Void .................................................................................................................................................... 795
8.2.3.13 Void .................................................................................................................................................... 795
8.2.3.14 Void .................................................................................................................................................... 795
8.2.3.15 Radio Bearer Release for transition from CELL_FACH to CELL_FACH: Success ......................... 795
8.2.3.16 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Subsequently
received) ............................................................................................................................................. 799
8.2.3.17 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Success (Subsequently
received) ............................................................................................................................................. 801
8.2.3.18 Radio Bearer Release from CELL_DCH to CELL_PCH: Success .................................................... 803
8.2.3.19 Radio Bearer Release from CELL_DCH to URA_PCH: Success ...................................................... 806
8.2.3.20 Radio Bearer Release for transition from CELL_DCH to CELL_FACH (Frequency band
8.2.3.21 Radio Bearer Release from CELL_DCH to CELL_PCH (Frequency band modification): Success .. 811
8.2.3.22 Radio Bearer Release for transition from CELL_FACH to CELL_PCH: Success ............................ 814
8.2.3.23 Radio Bearer Release for transition from CELL_FACH to URA_PCH: Success .............................. 816
8.2.3.24 Radio Bearer Release for transition from CELL_DCH to CELL_DCH (Frequency band
8.2.3.25 Radio Bearer Release for transition from CELL_DCH to URA_PCH (Frequency band
8.2.3.26 Radio Bearer Release for transition from CELL_FACH to CELL_PCH (Frequency band
8.2.3.27 Radio Bearer Release for transition from CELL_FACH to URA_PCH (Frequency band
8.2.3.28 Radio Bearer Release for transition from CELL_FACH to CELL_FACH (Frequency band
Release 5 10 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.2.3.29 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Associated with
signalling connection release during multi call for PS and CS services ............................................. 832
8.2.3.30 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (stop of HS-
DSCH reception) ................................................................................................................................ 834
RADIO BEARER RELEASE ........................................................................................................................................ 836
8.2.4 Transport channel reconfiguration ........................................................................................................... 836
8.2.4.1 Transport channel reconfiguration (Timing re-initialised hard handover with transmission rate
modification) from CELL_DCH to CELL_DCH: Success ................................................................ 836
8.2.4.1a Transport channel reconfiguration (Transmission Rate Modification) from CELL_DCH to
CELL_DCH of the same cell: Success ............................................................................................... 839
8.2.4.2 Void .................................................................................................................................................... 842
8.2.4.3 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Failure (Physical channel
failure and reversion to old configuration) ......................................................................................... 842
8.2.4.4 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Failure (Physical channel
failure and cell reselection) ................................................................................................................. 846
8.2.4.5 Void .................................................................................................................................................... 850
8.2.4.6 Void .................................................................................................................................................... 850
8.2.4.7 Void .................................................................................................................................................... 850
8.2.4.8 Void ................................................................................................................................................... 850
8.2.4.9 Void .................................................................................................................................................... 850
8.2.4.10 Transport channel reconfiguration from CELL_FACH to CELL_DCH: Success ............................. 850
8.2.4.11 Void .................................................................................................................................................... 852
8.2.4.12 Void .................................................................................................................................................... 852
8.2.4.13 Void .................................................................................................................................................... 852
8.2.4.14 Void .................................................................................................................................................... 852
8.2.4.15 Void .................................................................................................................................................... 852
8.2.4.16 Void .................................................................................................................................................... 852
8.2.4.17 Void .................................................................................................................................................... 852
8.2.4.18 Transport Channel Reconfiguration from CELL_DCH to CELL_DCH: Success (Subsequently
received) ............................................................................................................................................. 852
8.2.4.19 Transport Channel Reconfiguration from CELL_FACH to CELL_DCH: Success (Subsequently
received) ............................................................................................................................................. 855
8.2.4.20 Void .................................................................................................................................................... 858
8.2.4.21 Void .................................................................................................................................................... 858
8.2.4.22 Void .................................................................................................................................................... 858
8.2.4.23 Void .................................................................................................................................................... 858
8.2.4.24 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Success with uplink
transmission rate modification ............................................................................................................ 858
8.2.4.25 Transport channel reconfiguration from CELL_FACH to CELL_DCH (Frequency band
8.2.4.26 Void .................................................................................................................................................... 862
8.2.4.27 Void .................................................................................................................................................... 862
8.2.4.28 Void .................................................................................................................................................... 862
8.2.4.29 Transport Channel Reconfiguration for transition from CELL_DCH to CELL_DCH (Frequency
8.2.4.30 Void .................................................................................................................................................... 865
8.2.4.31 Void .................................................................................................................................................... 865
8.2.4.32 Void .................................................................................................................................................... 865
8.2.4.33 Void .................................................................................................................................................... 865
8.2.4.34 Void .................................................................................................................................................... 865
8.2.4.35 Transport Channel Reconfiguration for transition from CELL_DCH to CELL_DCH: Success
(serving HS-DSCH cell change with MAC-hs reset) ......................................................................... 865
TRANSPORT CHANNEL RECONFIGURATION (Step 6) ......................................................................................... 869
8.2.5 Transport format combination control ..................................................................................................... 871
8.2.5.1 Void .................................................................................................................................................... 871
8.2.5.2 Void .................................................................................................................................................... 871
8.2.5.3 Void .................................................................................................................................................... 871
8.2.5.4 Transport format combination control in CELL_DCH: Failure (Invalid configuration) .................... 871
8.2.6 Physical channel reconfiguration ............................................................................................................. 874
Release 5 11 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.2.6.1 Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (code
modification): Failure (Unsupported configuration) .......................................................................... 876
8.2.6.3 Void .................................................................................................................................................... 879
8.2.6.4 Void .................................................................................................................................................... 879
modification): Failure (Incompatible simultaneous reconfiguration) ................................................. 879
modification): Failure (Invalid message reception and Invalid configuration) ................................... 883
8.2.6.7 Physical channel reconfiguration for transition from CELL_DCH to CELL_FACH: Success .......... 887
8.2.6.8 Physical channel reconfiguration for transition from CELL_DCH to CELL_FACH: Success
(Cell re-selection) ............................................................................................................................... 889
8.2.6.9 Physical channel reconfiguration for transition from CELL_FACH to CELL_DCH: Success .......... 892
8.2.6.10 Void .................................................................................................................................................... 894
8.2.6.11 Physical channel reconfiguration for transition from CELL_FACH to CELL_DCH: Failure
(Physical channel failure and successful reversion to old configuration) ........................................... 894
(Physical channel failure and cell re-selection) .................................................................................. 897
8.2.6.13 Void .................................................................................................................................................... 901
(Invalid message reception and Invalid configuration)....................................................................... 901
8.2.6.15 Void .................................................................................................................................................... 906
8.2.6.16 Void .................................................................................................................................................... 906
modification): Success (Subsequently received) ................................................................................ 906
8.2.6.18 Physical channel reconfiguration for transition from CELL_FACH to CELL_DCH: Success
8.2.6.19 Physical Channel Reconfiguration from CELL_DCH to CELL_PCH: Success ................................ 911
8.2.6.20 Physical Channel Reconfiguration from CELL_DCH to URA_PCH: Success .................................. 913
8.2.6.21 Physical Channel Reconfiguration from CELL_FACH to URA_PCH: Success ............................... 915
8.2.6.22 Physical Channel Reconfiguration from CELL_FACH to CELL_PCH: Success .............................. 917
8.2.6.23 Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (Hard
handover to another frequency with timing maintain): Success ......................................................... 918
8.2.6.24 Void .................................................................................................................................................... 921
8.2.6.25 Physical channel reconfiguration for transition from CELL_DCH to CELL_FACH (Frequency
8.2.6.26 Physical Channel Reconfiguration from CELL_DCH to CELL_PCH (Frequency band
8.2.6.27 Physical channel reconfiguration from CELL_FACH to CELL_PCH: Success ................................ 927
8.2.6.28 Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (Downlink
channelisation code modification): Success ....................................................................................... 929
8.2.6.29 Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (Compressed
mode initiation): Success .................................................................................................................... 931
8.2.6.30 Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (Modify active
set cell): Success ................................................................................................................................. 937
8.2.6.31 Physical channel reconfiguration transition from CELL_FACH to URA_PCH: Success .................. 940
8.2.6.32 Physical channel reconfiguration for transition from CELL_DCH to URA_PCH (Frequency
8.2.6.33 Physical channel reconfiguration for transition from CELL_FACH to CELL_DCH (Frequency
8.2.6.34 Physical channel reconfiguration from CELL_FACH to CELL_PCH (Frequency band
8.2.6.35 Physical channel reconfiguration for transition from CELL_FACH to URA_PCH (Frequency
8.2.6.36 Physical channel reconfiguration for transition from CELL_FACH to CELL_FACH (Frequency
handover to another frequency with timing re-initialised) .................................................................. 955
Release 5 12 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.2.6.37a Physical channel reconfiguration for transition from CELL_DCH to CELL_DCH (Hard
handover to another frequency with timing re-initialised) (1.28 Mcps TDD) .................................... 976
handover to another frequency with timing re-initialised): Failure (Physical channel failure and
reversion to old channel) .................................................................................................................... 992
8.2.6.39 Physical Channel Reconfiguration for transition from CELL_DCH to CELL_DCH: Success
(Seamless SRNS relocation) (without pending of ciphering) ........................................................... 1003
8.2.7 Physical Shared Channel Allocation [TDD only] .................................................................................. 1009
8.2.8 PUSCH capacity request [TDD only] .................................................................................................... 1009
8.2.9 Void ........................................................................................................................................................ 1009
8.3 RRC connection mobility procedure ........................................................................................................... 1009
8.3.1 Cell Update............................................................................................................................................. 1009
8.3.1.1 Cell Update: cell reselection in CELL_FACH ................................................................................. 1009
8.3.1.2 Cell Update: cell reselection in CELL_PCH .................................................................................... 1021
8.3.1.3 Cell Update: periodical cell update in CELL_FACH ....................................................................... 1025
8.3.1.4 Cell Update: periodical cell update in CELL_PCH .......................................................................... 1032
8.3.1.5 Cell Update: UL data transmission in URA_PCH ............................................................................ 1037
8.3.1.6 Cell Update: UL data transmission in CELL_PCH .......................................................................... 1040
8.3.1.7 Void .................................................................................................................................................. 1043
8.3.1.8 Void .................................................................................................................................................. 1043
8.3.1.9 Cell Update: re-entering of service area after T305 expiry and being out of service area ................ 1043
8.3.1.10 Cell Update: expiry of T307 after T305 expiry and being out of service area ................................. 1047
8.3.1.11 Cell Update: Success after T302 time-out ........................................................................................ 1050
8.3.1.12 Cell Update: Failure (After Maximum Re-transmissions) ................................................................ 1053
8.3.1.13 Cell Update: Reception of Invalid CELL UPDATE CONFIRM Message ....................................... 1055
8.3.1.14 Cell Update: Incompatible simultaneous reconfiguration ................................................................ 1058
8.3.1.15 Cell Update: Unrecoverable error in Acknowledged Mode RLC SRB ............................................ 1061
8.3.1.16 Void .................................................................................................................................................. 1067
8.3.1.17 Cell Update: Failure (UTRAN initiate an RRC connection release procedure on CCCH)............... 1067
8.3.1.18 Cell Update: Radio Link Failure (T314>0, T315=0), CS RAB established ..................................... 1069
8.3.1.19 Void .................................................................................................................................................. 1074
8.3.1.20 Cell Update: Reception of CELL UPDATE CONFIRM Message that causes invalid
configuration..................................................................................................................................... 1074
8.3.1.21 Cell Update: Cell reselection to cell of another PLMN belonging to the equivalent PLMN list ...... 1077
8.3.1.22 Cell update: Restricted cell reselection to a cell belonging to forbidden LA list (Cell_FACH) ....... 1080
8.3.1.23 Cell Update: HCS cell reselection in CELL_FACH ......................................................................... 1083
8.3.1.24 Cell Update: HCS cell reselection in CELL_PCH ........................................................................... 1100
8.3.1.25 CELL UPDATE: Radio Link Failure (T314=0, T315=0) ................................................................ 1118
8.3.1.26 Cell Update: Radio Link Failure (T314>0, T315=0), PS RAB established...................................... 1120
8.3.1.27 Cell Update: Radio Link Failure (T314=0, T315>0), CS RAB ........................................................ 1125
8.3.1.28 Cell Update: Radio Link Failure (T314=0, T315>0), PS RAB ........................................................ 1128
8.3.1.29 Cell Update: Radio Link Failure (T314>0, T315>0), CS RAB ........................................................ 1132
8.3.1.30 Cell Update: Radio Link Failure (T314>0, T315>0), PS RAB ........................................................ 1135
8.3.1.31 Cell Update: re-entering of service area from URA_PCH after T316 expiry but before T317
expiry ................................................................................................................................................ 1141
8.3.2 URA Update ........................................................................................................................................... 1146
8.3.2.1 URA Update: Change of URA ......................................................................................................... 1146
8.3.2.2 URA Update: Periodical URA update and Reception of Invalid message ....................................... 1152
8.3.2.3 Void .................................................................................................................................................. 1155
8.3.2.4 URA Update: loss of service after expiry of timers T307 and T305 ................................................ 1155
8.3.2.5 URA Update: Success after Confirmation error of URA-ID list ...................................................... 1158
8.3.2.6 URA Update: Failure (V302 is greater than N302: Confirmation error of URA-ID list) ................. 1161
8.3.2.7 URA Update: Success after T302 timeout ........................................................................................ 1164
8.3.2.8 Void .................................................................................................................................................. 1166
8.3.2.9 URA Update: Failure (UTRAN initiate an RRC connection release procedure on CCCH) ............. 1166
8.3.2.10 URA Update: Reception of URA UPDATE CONFIRM message that causes invalid
configuration..................................................................................................................................... 1167
8.3.2.11 URA Update: Cell reselection to cell of another PLMN belonging to the equivalent PLMN list .... 1169
8.3.2.12 Restricted cell reselection to a cell belonging to forbidden LA list (URA_PCH) ............................ 1172
8.3.2.13 URA Update: Change of URA due to HCS Cell Reselection ........................................................... 1174
Release 5 13 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.3.3 UTRAN Mobility Information ............................................................................................................... 1187
8.3.3.1 UTRAN Mobility Information: Success ........................................................................................... 1187
8.3.3.2 UTRAN Mobility Information: Failure (Invalid message reception) ............................................... 1190
8.3.3.3 UTRAN MOBILITY INFORMATION: Seamless SRNS relocation in CELL_DCH (without
pending of ciphering)........................................................................................................................ 1193
8.3.4 Active set update in soft handover (FDD) .............................................................................................. 1199
8.3.4.1 Active set update in soft handover: Radio Link addition.................................................................. 1199
8.3.4.2 Active set update in soft handover: Radio Link removal.................................................................. 1206
8.3.4.3 Active set update in soft handover: Combined radio link addition and removal .............................. 1213
8.3.4.4 Active set update in soft handover: Invalid Configuration ............................................................... 1223
8.3.4.5 Active set update in soft handover: Reception of an ACTIVE SET UPDATE message in wrong
state ................................................................................................................................................... 1225
8.3.4.6 Void .................................................................................................................................................. 1229
8.3.4.7 Active set update in soft handover: Invalid Message Reception ...................................................... 1229
8.3.4.8 Active set update in soft handover: Radio Link addition in multiple radio link environment ......... 1231
8.3.5 Hard Handover ....................................................................................................................................... 1247
8.3.6 Inter-system hard handover from GSM to UTRAN ............................................................................... 1247
8.3.7 Inter-system hard handover from UTRAN to GSM ............................................................................... 1247
8.3.7.1 Inter system handover from UTRAN/To GSM/Speech/Success ...................................................... 1250
8.3.7.2 Inter system handover from UTRAN/To GSM/Data/Same data rate/Success ................................. 1254
8.3.7.2a Inter system handover from UTRAN/To GSM/Data/Same data rate/Extended Rates/Success ........ 1257
8.3.7.3 Inter system handover from UTRAN/To GSM/Data/Data rate down grading/Success ................... 1261
8.3.7.3a Inter system handover from UTRAN/To GSM/Data/Data rate down grading/Extended
Rates/Success ................................................................................................................................... 1264
8.3.7.4 Inter system handover from UTRAN/To GSM/Speech/Establishment/Success .............................. 1267
8.3.7.5 Inter system handover from UTRAN/To GSM/Speech/Failure ....................................................... 1270
8.3.7.6 Inter system handover from UTRAN/To GSM/Speech/Failure (L2 Establishment) ........................ 1275
8.3.7.7 Inter system handover from UTRAN/To GSM/Speech/Failure (L1 Synchronization) .................... 1277
8.3.7.8 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid Inter-RAT message) ........ 1279
8.3.7.9 Inter system handover from UTRAN/To GSM/Speech/Failure (Unsupported configuration) ......... 1281
8.3.7.10 Inter system handover from UTRAN/To GSM/Speech/Failure (Reception by UE in
CELL_FACH) .................................................................................................................................. 1283
8.3.7.11 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid message reception) .......... 1285
8.3.7.12 Inter system handover from UTRAN/To GSM/Speech/Failure (Physical channel Failure and
Reversion Failure) ............................................................................................................................ 1286
8.3.7.13 Inter system handover from UTRAN/To GSM/ success / call under establishment......................... 1291
8.3.8 Inter system cell reselection to UTRAN ................................................................................................ 1294
8.3.9 Inter system cell reselection from UTRAN ............................................................................................ 1295
8.3.9.1 Cell reselection if cell becomes barred or S<0; UTRAN to GPRS (CELL_FACH) ........................ 1295
8.3.9.2 Cell reselection if cell becomes barred or S<0; UTRAN to GPRS (URA_PCH) ............................. 1297
8.3.9.3 Cell reselection if S<0; UTRAN to GPRS (UE in CELL_FACH fails to complete an inter-RAT
cell reselection) ................................................................................................................................. 1299
Contents of System Information Block type 11 (FDD) ................................................................................................ 1301
8.3.9.4 Cell reselection if S<0; UTRAN to GPRS (UE in CELL_PCH fails to complete an inter-RAT
cell reselection) ................................................................................................................................. 1301
8.3.9.5 Successful Cell Reselection with RAU Q
offset
value modification; UTRAN to GPRS
(CELL_FACH) ................................................................................................................................. 1303
8.3.11 Inter-RAT cell change order from UTRAN ........................................................................................... 1305
8.3.11.1 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Success .................................. 1305
8.3.11.2 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Success ................................ 1307
8.3.11.3 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Failure (T309 expiry) ............ 1309
8.3.11.4 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Failure (Physical channel
Failure and Reversion Failure) ......................................................................................................... 1312
8.3.11.5 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Failure (T309 expiry) .......... 1316
8.3.11.6 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Failure (Physical channel
Failure and Reversion Failure) ......................................................................................................... 1318
8.3.11.7 Inter-RAT cell change order from UTRAN/To GPRS/ Failure (Unsupported configuration) ......... 1322
8.3.11.8 Inter-RAT cell change order from UTRAN/To GPRS/ Failure (Invalid Inter-RAT message) ......... 1324
8.4 Measurement procedure ............................................................................................................................... 1326
8.4.1 Measurement Control and Report .......................................................................................................... 1326
Release 5 14 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.4.1.1 Measurement Control and Report: Intra-frequency measurement for transition from idle mode to
CELL_DCH state (FDD) .................................................................................................................. 1326
8.4.1.1A Measurement Control and Report: Intra-frequency measurement for transition from idle mode to
CELL_DCH state (TDD) .................................................................................................................. 1339
8.4.1.1A.4 Method of test ............................................................................................................................. 1342
8.4.1.2 Measurement Control and Report: Inter-frequency measurement for transition from idle mode to
CELL_DCH state (FDD) .................................................................................................................. 1350
8.4.1.2A Measurement Control and Report: Inter-frequency measurement for transition from idle mode to
CELL_DCH state (TDD) .................................................................................................................. 1362
8.4.1.3 Measurement Control and Report: Intra-frequency measurement for transition from idle mode to
CELL_FACH state (FDD) ................................................................................................................ 1369
8.4.1.3A Measurement Control and Report: Intra-frequency measurement for transition from idle mode to
CELL_FACH state (TDD) ............................................................................................................... 1375
Reference 1377
8.4.1.3A.3 Test Purpose ................................................................................................................................ 1377
8.4.1.3A.4 Method of test ............................................................................................................................. 1378
8.4.1.4 Measurement Control and Report: Inter-frequency measurement for transition from idle mode to
CELL_FACH state (FDD) ................................................................................................................ 1381
8.4.1.4A Measurement Control and Report: Inter-frequency measurement for transition from idle mode to
CELL_FACH state (TDD) ............................................................................................................... 1385
8.4.1.5 Measurement Control and Report: Intra-frequency measurement for transition from CELL_DCH
to CELL_FACH state (FDD) ........................................................................................................... 1388
8.4.1.5A Measurement Control and Report: Intra-frequency measurement for transition from CELL_DCH
to CELL_FACH state (TDD) ........................................................................................................... 1398
8.4.1.6 Measurement Control and Report: Inter-frequency measurement for transition from CELL_DCH
to CELL_FACH state (FDD) ........................................................................................................... 1407
8.4.1.6A Measurement Control and Report: Inter-frequency measurement for transition from CELL_DCH
to CELL_FACH state (TDD) ........................................................................................................... 1415
8.4.1.7 Measurement Control and Report: Intra-frequency measurement for transition from
CELL_FACH to CELL_DCH state (FDD) ...................................................................................... 1420
8.4.1.7A Measurement Control and Report: Intra-frequency measurement for transition from
CELL_FACH to CELL_DCH state (TDD) ...................................................................................... 1439
8.4.1.8 Measurement Control and Report: Inter-frequency measurement for transition from
CELL_FACH to CELL_DCH state (FDD) ...................................................................................... 1455
8.4.1.8A Measurement Control and Report: Inter-frequency measurement for transition from
CELL_FACH to CELL_DCH state (TDD) ...................................................................................... 1472
8.4.1.9 Measurement Control and Report: Unsupported measurement in the UE ........................................ 1480
8.4.1.10 Measurement Control and Report: Failure (Invalid Message Reception)......................................... 1484
8.4.1.11 Void .................................................................................................................................................. 1486
8.4.1.12 Void .................................................................................................................................................. 1486
8.4.1.13 Void .................................................................................................................................................. 1486
8.4.1.14 Measurement Control and Report: Cell forbidden to affect reporting range (FDD) ........................ 1486
8.4.1.15 Measurement Control and Report: Configuration Incomplete ......................................................... 1500
8.4.1.16 Measurement Control and Report: Traffic volume measurement for transition from idle mode to
CELL_FACH state ........................................................................................................................... 1511
8.4.1.17 Measurement Control and Report: Traffic volume measurement for transition from idle mode to
CELL_DCH state ............................................................................................................................. 1518
8.4.1.18 Measurement Control and Report: Traffic volume measurement for transition from
CELL_FACH state to CELL_DCH state.......................................................................................... 1524
8.4.1.19 Measurement Control and Report: Traffic volume measurement for transition from CELL_DCH
to CELL_FACH state ....................................................................................................................... 1534
8.4.1.20 Void .................................................................................................................................................. 1542
8.4.1.21 Void .................................................................................................................................................. 1542
8.4.1.22 Measurement Control and Report: Quality measurements ............................................................... 1542
8.4.1.23 Measurement Control and Report: Intra-frequency measurement for events 1C and 1D ................. 1544
8.4.1.24 Measurement Control and Report: Inter-frequency measurement for event 2A ............................... 1551
8.4.1.25 Measurement Control and Report: Inter-frequency measurement for events 2B and 2E ................. 1560
8.4.1.26 Measurement Control and Report: Measurement for events 2D and 2F .......................................... 1570
8.4.1.27 Measurement Control and Report: UE internal measurement for events 6A and 6B ....................... 1576
8.4.1.28 Measurement Control and Report: UE internal measurement for events 6F (FDD) and 6G ............ 1580
Release 5 15 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
8.4.1.28A Measurement Control and Report: UE internal measurement for event 6F (1.28 Mcps TDD) ........ 1583
8.4.1.29 Measurement Control and Report: Event based Traffic Volume measurement in CELL_FACH
state. .................................................................................................................................................. 1585
8.4.1.30 Measurement Control and Report: Event based Traffic Volume measurement in CELL_DCH
state. .................................................................................................................................................. 1594
8.4.1.31 Measurement Control and Report: Inter-RAT measurement in CELL_DCH state. ......................... 1600
8.4.1.32 Void .................................................................................................................................................. 1607
8.4.1.33 Measurement Control and Report: Inter-RAT measurement, event 3a ............................................ 1607
8.4.1.34 Measurement Control and Report: Inter-RAT measurement, event 3b ............................................ 1615
8.4.1.35 Measurement Control and Report: Inter-RAT measurement, event 3c ............................................ 1625
8.4.1.36 Measurement Control and Report: Inter-RAT measurement, event 3d ............................................ 1632
8.4.1.37 Measurement Control and Report: UE internal measurement, event 6c ........................................... 1640
8.4.1.38 Measurement Control and Report: UE internal measurement, event 6d .......................................... 1642
8.4.1.39 Measurement Control and Report: UE internal measurement, event 6e ........................................... 1645
8.4.1.40 Measurement Control and Report: Inter-RAT measurement, event 3C, in CELL_DCH state using
sparse compressed mode pattern ...................................................................................................... 1647
8.4.1.41 Measurement Control and Report: Additional Measurements list .................................................... 1656
8.4.1.42 Measurement Control and Report: Change of Compressed Mode Method ...................................... 1661
PHYSICAL CHANNEL RECONFIGURATION MESSAGE (Step 1) ....................................................................... 1664
MEASUREMENT CONTROL (Step 3) ...................................................................................................................... 1665
MEASUREMENT REPORT (Step 5,14) ..................................................................................................................... 1666
RADIO BEARER SETUP (Step 6) .............................................................................................................................. 1667
MEASUREMENT REPORT (Step 9,18) ..................................................................................................................... 1668
RADIO BEARER SETUP (Step 6) .............................................................................................................................. 1669
RADIO BEARER RELEASE (Step 15) ....................................................................................................................... 1670
8.4.1.43 Measurement Control and Report: Compressed Mode Reconfiguration .......................................... 1671
MEASUREMENT REPORT (Step 14,23) ................................................................................................................... 1680
8.4.1.44 Measurement Control and Report: Intra-frequency measurement for events 1H and 1I (TDD) ...... 1683
8.4.1.45 Measurement Control and Report: Intra-frequency measurement for event 1G (1.28 McpsTDD) .. 1690
9 Elementary procedures of mobility management ............................................................................... 1697
9.1 TMSI reallocation ........................................................................................................................................ 1697
9.2 Authentication .............................................................................................................................................. 1700
9.2.1 Authentication accepted ......................................................................................................................... 1700
9.2.2 Authentication rejected by the network .................................................................................................. 1701
9.2.3 Authentication rejected by the UE (MAC code failure) ......................................................................... 1705
9.2.4 Authentication rejected by the UE (SQN failure) .................................................................................. 1707
9.2.5 Authentication rejected by the UE / fraudulent network ........................................................................ 1709
9.3 Identification ................................................................................................................................................ 1712
9.3.1 General Identification ............................................................................................................................. 1712
9.3.2 Handling of IMSI shorter than the maximum length ............................................................................. 1714
9.4 Location updating ........................................................................................................................................ 1717
9.4.1 Location updating / accepted .................................................................................................................. 1717
9.4.2 Location updating / rejected ................................................................................................................... 1720
9.4.2.1 Location updating / rejected / IMSI invalid ...................................................................................... 1720
9.4.2.2 Location updating / rejected / PLMN not allowed............................................................................ 1723
9.4.2.3 Location updating / rejected / location area not allowed .................................................................. 1729
9.4.2.4 Location updating / rejected / roaming not allowed in this location area ......................................... 1732
9.4.2.5 Location updating / rejected / No Suitable Cells In Location Area .................................................. 1741
9.4.3 Location updating / abnormal cases ....................................................................................................... 1743
9.4.3.1 Void .................................................................................................................................................. 1743
9.4.3.2 Location updating / abnormal cases / attempt counter less or equal to 4, LAI different .................. 1743
9.4.3.3 Location updating / abnormal cases / attempt counter equal to 4 ..................................................... 1749
9.4.3.4 Location updating / abnormal cases / attempt counter less or equal to 4, stored LAI equal to
broadcast LAI ................................................................................................................................... 1759
9.4.3.5 Location updating / abnormal cases / Failure due to non-integrity protection .................................. 1769
9.4.4 Location updating / release / expiry of T3240 ........................................................................................ 1771
9.4.5 Location updating / periodic .................................................................................................................. 1772
9.4.5.1 Location updating / periodic spread ................................................................................................. 1772
9.4.5.2 Location updating / periodic normal / test 1 ..................................................................................... 1775
9.4.5.3 Location updating / periodic normal / test 2 ..................................................................................... 1777
Release 5 16 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
9.4.5.4 Location updating / periodic search for HPLMN or higher priority PLMN when in VPLMN ........ 1779
9.4.5.4.1 Location updating / periodic search for HPLMN or higher priority PLMN / UE waits time T .. 1779
9.4.5.4.2 Location updating / periodic search for HPLMN or higher priority PLMN / UE in manual
mode ........................................................................................................................................... 1782
9.4.5.4.3 Location updating / periodic search for HPLMN or higher priority PLMN / UE waits at least
two minutes and at most T minutes............................................................................................. 1783
9.4.6 Location updating / interworking of attach and periodic........................................................................ 1785
9.4.7 Location Updating / accept with replacement or deletion of Equivalent PLMN list .............................. 1788
9.4.8 Location Updating after UE power off ................................................................................................... 1791
9.4.9 Location Updating / Accept, Interaction between Equivalent PLMNs and Forbidden PLMNs. ............ 1793
9.5 MM connection ............................................................................................................................................ 1794
9.5.1 Introduction ............................................................................................................................................ 1794
9.5.2 MM connection / establishment in security mode .................................................................................. 1794
9.5.3 Void ........................................................................................................................................................ 1796
9.5.4 MM connection / establishment rejected ................................................................................................ 1796
9.5.5 MM connection / establishment rejected cause 4 ................................................................................... 1797
9.5.6 MM connection / expiry T3230.............................................................................................................. 1799
9.5.7 MM connection / abortion by the network ............................................................................................. 1801
9.5.7.1 MM connection / abortion by the network / cause #6 ...................................................................... 1801
9.5.7.2 MM connection / abortion by the network / cause not equal to #6 ................................................... 1803
9.5.8 MM connection / follow-on request pending ......................................................................................... 1805
9.5.8.1 MM connection / follow-on request pending / test 1 ........................................................................ 1805
10 Circuit Switched Call Control (CC) ................................................................................................... 1811
10.1 Circuit switched Call Control (CC) state machine verification ................................................................... 1811
10.1.1 General on CC state machine verification .............................................................................................. 1811
10.1.2 Establishment of an outgoing call .......................................................................................................... 1812
10.1.2.1 Outgoing call / U0 null state ............................................................................................................. 1814
10.1.2.1.1 Outgoing call / U0 null state / MM connection requested .......................................................... 1814
10.1.2.2 Outgoing call / U0.1 MM connection pending ................................................................................. 1815
10.1.2.2.1 Outgoing call / U0.1 MM connection pending / CM service rejected ........................................ 1815
10.1.2.2.2 Outgoing call / U0.1 MM connection pending / CM service accepted ....................................... 1816
10.1.2.2.3 Outgoing call / U0.1 MM connection pending / lower layer failure ........................................... 1817
10.1.2.3 Outgoing call / U1 call initiated........................................................................................................ 1819
10.1.2.3.1 Outgoing call / U1 call initiated / receiving CALL PROCEEDING ........................................... 1819
10.1.2.3.2 Outgoing call / U1 call initiated / rejecting with RELEASE COMPLETE ................................. 1820
10.1.2.3.3 Outgoing call / U1 call initiated / T303 expiry ........................................................................... 1821
10.1.2.3.4 Outgoing call / U1 call initiated / lower layer failure.................................................................. 1823
10.1.2.3.5 Outgoing call / U1 call initiated / receiving ALERTING ........................................................... 1824
10.1.2.3.6 Outgoing call / U1 call initiated / entering state U10 .................................................................. 1825
10.1.2.3.7 Outgoing call / U1 call initiated / unknown message received ................................................... 1826
10.1.2.4 Outgoing call / U3 Mobile originating call proceeding .................................................................... 1827
10.1.2.4.1 Outgoing call / U3 Mobile originating call proceeding / ALERTING received ......................... 1827
10.1.2.4.2 Outgoing call / U3 Mobile originating call proceeding / CONNECT received .......................... 1828
10.1.2.4.3 Outgoing call / U3 Mobile originating call proceeding / PROGRESS received without in
band information ......................................................................................................................... 1830
10.1.2.4.4 Outgoing call / U3 Mobile originating call proceeding / PROGRESS with in band
information .................................................................................................................................. 1831
10.1.2.4.5 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT with in band tones .... 1833
10.1.2.4.6 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT without in band
tones ............................................................................................................................................ 1835
10.1.2.4.7 Outgoing call / U3 Mobile originating call proceeding / RELEASE received ........................... 1836
10.1.2.4.8 Outgoing call / U3 Mobile originating call proceeding / termination requested by the user ...... 1837
10.1.2.4.9 Outgoing call / U3 Mobile originating call proceeding / traffic channel allocation .................... 1838
10.1.2.4.10 Outgoing call / U3 Mobile originating call proceeding / timer T310 time-out ........................... 1839
10.1.2.4.11 Outgoing call / U3 Mobile originating call proceeding / lower layer failure .............................. 1841
The re-establishment takes place when a lower layer failure occurs and at least one MM connection is active (i.e..
the mobile station's MM sublayer is either in state 6 "MM CONNECTION ACTIVE" or state 20
"WAIT FOR ADDITIONAL OUTGOING MM CONNECTION"). ............................................... 1841
Release 5 17 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
10.1.2.4.12 Outgoing call / U3 Mobile originating call proceeding / unknown message received ................ 1843
10.1.2.4.13 Outgoing call / U3 Mobile originating call proceeding / Internal alerting indication ................. 1844
10.1.2.5 Outgoing call / U4 call delivered ...................................................................................................... 1845
10.1.2.5.1 Outgoing call / U4 call delivered / CONNECT received ............................................................ 1845
10.1.2.5.2 Outgoing call / U4 call delivered / termination requested by the user ........................................ 1846
10.1.2.5.3 Outgoing call / U4 call delivered / DISCONNECT with in band tones ...................................... 1847
10.1.2.5.4 Outgoing call / U4 call delivered / DISCONNECT without in band tones ................................. 1849
10.1.2.5.5 Outgoing call / U4 call delivered / RELEASE received ............................................................. 1850
10.1.2.5.6 Outgoing call / U4 call delivered / lower layer failure ................................................................ 1851
10.1.2.5.7 Outgoing call / U4 call delivered / traffic channel allocation ..................................................... 1852
10.1.2.5.8 Outgoing call / U4 call delivered / unknown message received ................................................. 1853
10.1.2.6 U10 active ......................................................................................................................................... 1854
10.1.2.6.1 U10 active / termination requested by the user ........................................................................... 1854
10.1.2.6.2 U10 active / RELEASE received ................................................................................................ 1856
10.1.2.6.3 U10 active / DISCONNECT with in band tones ......................................................................... 1857
10.1.2.6.4 U10 active / DISCONNECT without in band tones ................................................................... 1858
10.1.2.6.5 U10 active / RELEASE COMPLETE received .......................................................................... 1859
10.1.2.6.6 U10 active / SETUP received ..................................................................................................... 1860
10.1.2.7 U11 disconnect request ..................................................................................................................... 1862
10.1.2.7.1 U11 disconnect request / clear collision ...................................................................................... 1862
10.1.2.7.2 U11 disconnect request / RELEASE received ............................................................................ 1863
10.1.2.7.3 U11 disconnect request / timer T305 time-out ............................................................................ 1864
10.1.2.7.4 U11 disconnect request / lower layer failure ............................................................................... 1866
10.1.2.7.5 U11 disconnect request / unknown message received ................................................................ 1867
10.1.2.8 U12 disconnect indication ................................................................................................................ 1868
10.1.2.8.1 U12 disconnect indication / call releasing requested by the user ................................................ 1868
10.1.2.8.2 U12 disconnect indication / RELEASE received ........................................................................ 1869
10.1.2.8.3 U12 disconnect indication / lower layer failure .......................................................................... 1871
10.1.2.8.4 U12 disconnect indication / unknown message received ............................................................ 1872
10.1.2.9 Outgoing call / U19 release request .................................................................................................. 1873
10.1.2.9.1 Outgoing call / U19 release request / timer T308 time-out ......................................................... 1873
10.1.2.9.2 Outgoing call / U19 release request / 2nd timer T308 time-out .................................................. 1874
10.1.2.9.3 Outgoing call / U19 release request / RELEASE received ......................................................... 1876
10.1.2.9.4 Outgoing call / U19 release request / RELEASE COMPLETE received ................................... 1877
10.1.2.9.5 Outgoing call / U19 release request / lower layer failure ............................................................ 1878
10.1.3 Establishment of an incoming call / Initial conditions ........................................................................... 1879
10.1.3.1 Incoming call / U0 null state ............................................................................................................. 1881
10.1.3.1.1 Incoming call / U0 null state / SETUP received with a non supported bearer capability ........... 1881
10.1.3.2 Incoming call / U6 call present ......................................................................................................... 1883
10.1.3.2.1 Incoming call / U6 call present / automatic call rejection ........................................................... 1883
10.1.3.3 Incoming call / U9 mobile terminating call confirmed ..................................................................... 1884
10.1.3.3.1 Incoming call / U9 mobile terminating call confirmed / alerting or immediate connecting ....... 1884
10.1.3.3.2 Incoming call / U9 mobile terminating call confirmed / DTCH assignment .............................. 1886
10.1.3.3.3 Void ............................................................................................................................................ 1887
10.1.3.3.4 Incoming call / U9 mobile terminating call confirmed / DISCONNECT received .................... 1887
10.1.3.3.5 Incoming call / U9 mobile terminating call confirmed / RELEASE received ............................ 1888
10.1.3.3.6 Incoming call / U9 mobile terminating call confirmed / lower layer failure ............................... 1890
10.1.3.3.7 Incoming call / U9 mobile terminating call confirmed / unknown message received ................ 1891
10.1.3.4 Incoming call / U7 call received ....................................................................................................... 1892
10.1.3.4.1 Incoming call / U7 call received / call accepted .......................................................................... 1892
10.1.3.4.2 Incoming call / U7 call received / termination requested by the user ......................................... 1893
10.1.3.4.3 Incoming call / U7 call received / DISCONNECT received ....................................................... 1895
10.1.3.4.4 Incoming call / U7 call received / RELEASE received .............................................................. 1896
10.1.3.4.5 Incoming call / U7 call received / lower layer failure ................................................................. 1897
10.1.3.4.6 Incoming call / U7 call received / unknown message received................................................... 1898
10.1.3.4.7 Incoming call / U7 call received / DTCH assignment................................................................. 1900
10.1.3.4.8 Incoming call / U7 call received / RELEASE COMPLETE received ........................................ 1901
10.1.3.5 Incoming call / U8 connect request .................................................................................................. 1902
10.1.3.5.1 Incoming call / U8 connect request / CONNECT acknowledged ............................................... 1902
10.1.3.5.2 Incoming call / U8 connect request / timer T313 time-out ......................................................... 1903
Release 5 18 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
10.1.3.5.3 Incoming call / U8 connect request / termination requested by the user ..................................... 1905
10.1.3.5.4 Incoming call / U8 connect request / DISCONNECT received with in-band information ......... 1906
10.1.3.5.5 Incoming call / U8 connect request / DISCONNECT received without in-band information .... 1907
10.1.3.5.6 Incoming call / U8 connect request / RELEASE received .......................................................... 1908
10.1.3.5.7 Incoming call / U8 connect request / lower layer failure ............................................................ 1910
10.1.3.5.8 Incoming call / U8 connect request / DTCH assignment ............................................................ 1911
10.1.3.5.9 Incoming call / U8 connect request / unknown message received .............................................. 1912
10.1.4 In call functions ...................................................................................................................................... 1913
10.1.4.1 In-call functions / DTMF information transfer ................................................................................. 1913
10.1.4.1.1 In-call functions / DTMF information transfer / basic procedures .............................................. 1913
10.1.4.2 In-call functions / user notification ................................................................................................... 1915
10.1.4.2.1 In-call functions / User notification / UE terminated .................................................................. 1915
10.1.4.3 In-call functions / channel changes ................................................................................................... 1916
10.1.4.3.1 In-call functions / channel changes / a successful channel change in active state/ Hard
handover...................................................................................................................................... 1916
10.1.4.3.2 In-call functions / channel changes / an unsuccessful channel change in active mode/Hard
handover...................................................................................................................................... 1917
10.1.4.4 In-call functions / UE terminated in-call modification ..................................................................... 1919
10.1.4.4.1 In-call functions / UE terminated in-call modification / modify when new mode is not
supported ..................................................................................................................................... 1919
10.1.4.5 In-call functions / UE originated in-call modification ...................................................................... 1919
10.1.4.5.1 In-call functions / UE originated in-call modification / a successful case of modifying............. 1919
10.1.4.5.2 In-call functions / UE originated in-call modification / modify rejected .................................... 1919
10.1.4.5.3 In-call functions / UE originated in-call modification / an abnormal case of acceptance ........... 1919
10.1.4.5.4 In-call functions / UE originated in-call modification / an abnormal case of rejection............... 1919
10.1.4.5.5 In-call functions / UE originated in-call modification / time-out of timer T323 ......................... 1919
10.1.4.5.6 In-call functions / UE originated in-call modification / a successful channel change in state
mobile originating modify .......................................................................................................... 1919
10.1.4.5.7 In-call functions / UE originated in-call modification / an unsuccessful channel change in
state mobile originating modify .................................................................................................. 1919
10.1.4.5.8 In-call functions / UE originated in-call modification / unknown message received .................. 1919
10.1.4.5.9 In-call functions / UE originated in-call modification / a release complete received ................. 1919
10.2 Call Re-establishment .................................................................................................................................. 1920
10.2.1 Void ........................................................................................................................................................ 1920
10.3 User to user signalling ................................................................................................................................. 1920
11 Session Management Procedures ....................................................................................................... 1922
11.1 PDP context activation ................................................................................................................................. 1922
11.1.1 Initiated by the UE ................................................................................................................................. 1922
11.1.1.1 Attach initiated by context activation/QoS Offered by Network is the QoS Requested ................... 1922
11.1.1.1a Attach initiated by context activation/QoS Offered by Network is the QoS Requested/Correct
handling of QoS extensions for rates above 8640 kbps .................................................................... 1925
11.1.1.2 QoS offered by the network is a lower QoS ..................................................................................... 1929
11.1.1.2.1 Void ............................................................................................................................................ 1929
11.1.1.2.2 Void ............................................................................................................................................ 1929
11.1.2 PDP context activation requested by the network, successful and unsuccessful .................................... 1929
11.1.3 Abnormal Cases ..................................................................................................................................... 1932
11.1.3.1 T3380 Expiry .................................................................................................................................... 1932
11.1.3.2 Collision of UE initiated and network requested PDP context activation ........................................ 1934
11.1.3.3 Network initiated PDP context activation request for an already activated PDP context (on the
UE side) ............................................................................................................................................ 1936
11.1.4 Secondary PDP context activation procedures ....................................................................................... 1937
11.1.4.1 Successful Secondary PDP Context Activation Procedure Initiated by the UE ............................... 1937
11.1.4.1.1 QoS Offered by Network is the QoS Requested ......................................................................... 1937
11.1.4.1.2 QoS Offered by Network is a lower QoS .................................................................................... 1939
11.1.4.2 Unsuccessful Secondary PDP Context Activation Procedure Initiated by the UE ........................... 1941
11.1.4.3 Abnormal cases ................................................................................................................................ 1942
11.1.4.3.1 T3380 Expiry .............................................................................................................................. 1942
11.2 PDP context modification procedure ........................................................................................................... 1944
11.2.1 Network initiated PDP context modification ......................................................................................... 1944
11.2.2 UE initiated PDP context modification .................................................................................................. 1946
Release 5 19 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
11.2.2.1 UE initiated PDP Context Modification accepted by network ......................................................... 1946
11.2.2.2 UE initiated PDP Context Modification not accepted by the network ............................................. 1948
11.2.3 Abnormal cases ...................................................................................................................................... 1950
11.2.3.1 T3381 Expiry .................................................................................................................................... 1950
11.2.3.2 Collision of UE and network initiated PDP context modification procedures ................................. 1951
11.3 PDP context deactivation procedures .......................................................................................................... 1953
11.3.1 PDP context deactivation initiated by the UE ........................................................................................ 1953
11.3.2 PDP context deactivation initiated by the network ................................................................................ 1956
11.3.2.5 Test requirements ............................................................................................................................. 1958
11.3.3 Abnormal cases ...................................................................................................................................... 1958
11.3.3.1 T3390 Expiry .................................................................................................................................... 1958
11.3.3.2 Collision of UE and network initiated PDP context deactivation requests ....................................... 1960
11.4 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors . 1961
11.4.1 Error cases .............................................................................................................................................. 1961
12 Elementary procedure for Packet Switched Mobility Management ................................................... 1965
12.1 Applicability, default conditions and default messages ............................................................................... 1965
12.2 PS attach procedure ..................................................................................................................................... 1965
12.2.1 Normal PS attach .................................................................................................................................... 1965
12.2.1.1 PS attach / accepted .......................................................................................................................... 1966
12.2.1.2 PS attach / rejected / IMSI invalid / illegal UE ................................................................................. 1970
12.2.1.3 PS attach / rejected / IMSI invalid / PS services not allowed ........................................................... 1973
12.2.1.4 PS attach / rejected / PLMN not allowed .......................................................................................... 1976
12.2.1.5a PS attach / rejected / roaming not allowed in this location area ....................................................... 1981
12.2.1.5b PS attach / rejected / No Suitable Cells In Location Area ................................................................ 1993
12.2.1.5c PS attach / rejected / Location area not allowed ............................................................................... 1996
12.2.1.5d PS attach / rejected / PS services not allowed in this PLMN ............................................................ 1999
12.2.1.6 PS attach / abnormal cases / access barred due to access class control ............................................ 2002
12.2.1.7 PS attach / abnormal cases / change of routing area ......................................................................... 2006
12.2.1.8 PS attach / abnormal cases / power off ............................................................................................. 2009
12.2.1.9 PS attach / abnormal cases / PS detach procedure collision ............................................................. 2010
12.2.1.10 PS attach / abnormal cases / Failure due to non-integrity protection ................................................ 2013
12.2.1.10.1 Definition .................................................................................................................................... 2013
12.2.1.10.2 Conformance requirement........................................................................................................... 2013
12.2.1.10.3 Test purpose ................................................................................................................................ 2013
12.2.1.10.4 Method of test ............................................................................................................................. 2013
12.2.1.10.5 Test requirements ........................................................................................................................ 2014
12.2.2 Combined PS attach ............................................................................................................................... 2015
12.2.2.1 Combined PS attach / PS and non-PS attach accepted ..................................................................... 2015
12.2.2.2 Combined PS attach / PS only attach accepted ................................................................................. 2020
12.2.2.3 Combined PS attach / PS attach while IMSI attach .......................................................................... 2028
12.2.2.4 Combined PS attach / rejected / IMSI invalid / illegal ME .............................................................. 2030
12.2.2.5 Combined PS attach / rejected / PS services and non-PS services not allowed ................................ 2034
12.2.2.6 Combined PS attach / rejected / PS services not allowed ................................................................. 2037
12.2.2.7a Combined PS attach / rejected / location area not allowed ............................................................... 2040
12.2.2.7b Combined PS attach / rejected / No Suitable Cells In Location Area ............................................... 2045
12.2.2.7c Combined PS attach / rejected / Roaming not allowed in this location area .................................... 2048
12.2.2.7d Combined PS attach / rejected / PS services not allowed in this PLMN .......................................... 2052
12.2.2.8 Combined PS attach / abnormal cases / attempt counter check / miscellaneous reject causes ......... 2054
12.2.2.9 Combined PS attach / abnormal cases / PS detach procedure collision ............................................ 2059
12.3 PS detach procedure..................................................................................................................................... 2061
12.3.1 UE initiated PS detach procedure ........................................................................................................... 2061
12.3.1.1 PS detach / power off / accepted....................................................................................................... 2061
12.3.1.2 PS detach / accepted ......................................................................................................................... 2064
12.3.1.3 PS detach / abnormal cases / attempt counter check / procedure timeout......................................... 2066
12.3.1.4 PS detach / abnormal cases / GMM common procedure collision ................................................... 2069
12.3.1.5 PS detach / power off / accepted / PS/IMSI detach .......................................................................... 2072
12.3.1.6 PS detach / accepted / PS/IMSI detach ............................................................................................. 2074
12.3.1.7 PS detach / accepted / IMSI detach .................................................................................................. 2076
12.3.1.8 PS detach / abnormal cases / change of cell into new routing area................................................... 2078
12.3.1.9 PS detach / abnormal cases / PS detach procedure collision ............................................................ 2081
Release 5 20 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
12.3.2 Network initiated PS detach procedure .................................................................................................. 2083
12.3.2.1 PS detach / re-attach not required / accepted .................................................................................... 2083
12.3.2.2 PS detach / rejected / IMSI invalid / PS services not allowed .......................................................... 2085
12.3.2.3 PS detach / IMSI detach / accepted .................................................................................................. 2087
12.3.2.4 PS detach / re-attach requested / accepted ........................................................................................ 2090
12.3.2.5 PS detach / rejected / location area not allowed ............................................................................... 2093
12.3.2.6 PS detach / rejected / No Suitable Cells In Location Area ............................................................... 2098
12.3.2.7 PS detach / rejected / Roaming not allowed in this location area ..................................................... 2101
12.3.2.8 PS detach / rejected / PS services not allowed in this PLMN ........................................................... 2106
12.4 Routing area updating procedure ................................................................................................................. 2111
12.4.1 Normal routing area updating................................................................................................................. 2111
12.4.1.1a Routing area updating / accepted ...................................................................................................... 2111
12.4.1.1b Routing area updating / accepted / Signalling connection re-establishment ..................................... 2115
12.4.1.1c Void .................................................................................................................................................. 2118
12.4.1.2 Routing area updating / rejected / IMSI invalid / illegal ME ............................................................ 2118
12.4.1.3 Routing area updating / rejected / UE identity cannot be derived by the network............................ 2120
12.4.1.4a Routing area updating / rejected / location area not allowed ............................................................ 2123
12.4.1.4b Routing area updating / rejected / No Suitable Cells In Location Area ............................................ 2127
12.4.1.4c Routing area updating / rejected / PS services not allowed in this PLMN ....................................... 2130
12.4.1.4d Routing area updating / rejected / Roaming not allowed in this location area .................................. 2135
12.4.1.5 Routing area updating / abnormal cases / attempt counter check / miscellaneous reject causes ...... 2142
12.4.1.6 Routing area updating / abnormal cases / change of cell into new routing area ............................... 2147
12.4.1.7 Routing area updating / abnormal cases / change of cell during routing area updating procedure ... 2149
12.4.1.8 Routing area updating / abnormal cases / P-TMSI reallocation procedure collision ........................ 2152
12.4.2 Combined routing area updating ............................................................................................................ 2155
12.4.2.1 Combined routing area updating / combined RA/LA accepted ........................................................ 2155
12.4.2.2 Combined routing area updating / UE in CS operation at change of RA ......................................... 2159
12.4.2.3 Combined routing area updating / RA only accepted ....................................................................... 2161
12.4.2.3a Void .................................................................................................................................................. 2169
12.4.2.4 Combined routing area updating / rejected / PLMN not allowed ..................................................... 2169
12.4.2.5a Combined routing area updating / rejected / roaming not allowed in this location area ................... 2173
12.4.2.5b Combined routing area updating / rejected / No Suitable Cells In Location Area. ........................... 2181
12.4.2.5c Combined routing area updating / rejected / Location area not allowed .......................................... 2185
12.4.2.5d Combined routing area updating / rejected / PS services not allowed in this PLMN ....................... 2187
12.4.2.6 Combined routing area updating / abnormal cases / access barred due to access class control ........ 2190
12.4.2.7 Combined routing area updating / abnormal cases / attempt counter check / procedure timeout ..... 2195
12.4.2.8 Combined routing area updating / abnormal cases / change of cell into new routing area ............... 2199
12.4.2.9 Combined routing area updating / abnormal cases / change of cell during routing area updating
procedure .......................................................................................................................................... 2202
12.4.2.10 Combined routing area updating / abnormal cases / PS detach procedure collision ......................... 2205
12.4.3 Periodic routing area updating ............................................................................................................... 2209
12.4.3.1 Periodic routing area updating / accepted ......................................................................................... 2209
12.4.3.2 Periodic routing area updating / accepted / T3312 default value ...................................................... 2212
12.4.3.3 Periodic routing area updating / no cell available / network mode I ................................................ 2214
12.4.3.4 Periodic routing area updating / no cell available ............................................................................. 2216
12.5 P-TMSI reallocation .................................................................................................................................... 2218
12.6 PS authentication ......................................................................................................................................... 2220
12.6.1 Test of authentication ............................................................................................................................. 2220
12.6.1.1 Authentication accepted ................................................................................................................... 2220
12.6.1.2 Authentication rejected by the network ............................................................................................ 2223
12.6.1.3 Authentication rejected by the UE .................................................................................................... 2226
12.6.1.3.1 GMM cause 'MAC failure' .......................................................................................................... 2226
12.6.1.3.2 GMM cause 'Synch failure' ......................................................................................................... 2229
12.6.1.3.3 Authentication rejected by the UE / fraudulent network ............................................................. 2232
12.6.2 Void ........................................................................................................................................................ 2235
12.7 Identification procedure ............................................................................................................................... 2235
12.7.1 General Identification ............................................................................................................................. 2236
12.8 GMM READY timer handling .................................................................................................................... 2238
12.9 Service Request procedure (UMTS Only) ................................................................................................... 2241
12.9.1 Service Request Initiated by UE Procedure ........................................................................................... 2241
Release 5 21 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
12.9.2 Service Request Initiated by Network Procedure ................................................................................... 2243
12.9.3 Service Request / rejected / Illegal MS .................................................................................................. 2245
12.9.4 Service Request / rejected / PS services not allowed ............................................................................. 2249
12.9.5 Service Request / rejected / MS identity cannot be derived by the network .......................................... 2253
12.9.6 Service Request / rejected / PLMN not allowed..................................................................................... 2255
12.9.7a Service Request / rejected / No PDP context activated .......................................................................... 2258
12.9.7b Service Request / rejected / No Suitable Cells In Location Area ..................................................... 2261
12.9.7c Service Request / rejected / Roaming not allowed in this location area ................................................. 2264
12.9.8 Service Request / Abnormal cases / Access barred due to access class control ..................................... 2267
12.9.9 Service Request / Abnormal cases / Routing area update procedure is triggered .................................. 2269
12.9.10 Service Request / Abnormal cases / Power off ...................................................................................... 2272
12.9.11 Service Request / Abnormal cases / Service request procedure collision .............................................. 2274
12.9.12 Service Request / RAB re-establishment / UE initiated / Single PDP context ....................................... 2277
12.9.13 Service Request / RAB re-establishment / UE initiated / multiple PDP contexts .................................. 2280
12.9.14 Service Request / RAB re-establishment / Network initiated / single PDP context ............................... 2282
13 General Tests ...................................................................................................................................... 2284
13.1 Emergency call / general .............................................................................................................................. 2284
13.2 Emergency call ............................................................................................................................................ 2284
13.2.1 Emergency call / with USIM .................................................................................................................. 2284
13.2.1.1 Emergency call / with USIM / accept case ....................................................................................... 2284
13.2.2 Emergency call / without USIM ....................................................................................................... 2286
13.2.2.1 Emergency call / without USIM / accept case ............................................................................ 2286
13.2.2.2 Emergency call / without USIM / reject case .............................................................................. 2289
14 Interoperability Radio Bearer Tests ................................................................................................... 2290
14.1 General information for interoperability radio bearer tests .......................................................................... 2290
14.1.1 Generic radio bearer test procedure for single RB configurations ......................................................... 2291
14.1.2 Generic test procedure for testing multi-RB combinations and simultaneous signalling ....................... 2293
14.1.2a Generic test procedure for testing multi-RB combinations and simultaneous signalling in case of
DSCH ..................................................................................................................................................... 2297
14.1.3 General information interoperability radio bearer tests for HS-DSCH .................................................. 2304
14.1.3.1 Radio bearer test parameters for UE categories ................................................................................ 2304
14.1.3.2 Generic test procedure for single HS-DSCH radio bearer configurations ........................................ 2304
14.1.3.2.1 Initial conditions ......................................................................................................................... 2307
14.1.3.2.2 Test procedure ............................................................................................................................. 2307
14.2 Combinations on DPCH .............................................................................................................................. 2309
14.2.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH ................................................................................ 2309
14.2.2 Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH ................................................................................ 2310
14.2.3 Stand-alone UL:13.6 DL:13.6 kbps SRBs for DCCH ............................................................................ 2310
14.2.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH . 2310
14.2.4a Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +UL:3.4
DL:3.4 kbps SRBs for DCCH. ............................................................................................................... 2312
14.2.5 Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB +UL:3.4 DL: 3.4 kbps SRBs for DCCH 2314
14.2.5a Conversational / speech / UL:(10.2, 6.7, 5.9, 4.75) DL:(10.2, 6.7, 5.9, 4.75) kbps / CS RAB +
UL:3.4 DL:3.4 kbps SRBs for DCCH. ................................................................................................... 2315
14.2.7 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB+UL:3.4 DL:3.4 kbps SRBs for DCCH ...... 2319
14.2.7a Conversational / speech / UL:(7.4, 6.7, 5.9, 4.75) DL:(7.4, 6.7, 5.9, 4.75) kbps / CS RAB +UL:3.4
DL:3.4 kbps SRBs for DCCH. ............................................................................................................... 2321
14.2.8 Conversational / speech / UL:6.7 DL:6.7 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ..... 2324
14.2.9 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ..... 2325
14.2.12 Conversational / unknown / UL:28.8 DL:28.8 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH..................................................................................................................................................... 2330
14.2.13 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ... 2332
14.2.13.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI .......................................... 2332
14.2.14 Conversational / unknown / UL:32 DL:32 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ... 2335
Release 5 22 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
14.2.15 Streaming / unknown / UL:14.4/DL:14.4 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ..... 2338
14.2.18 Void ........................................................................................................................................................ 2344
14.2.19 Void ........................................................................................................................................................ 2344
14.2.20 Void ........................................................................................................................................................ 2344
14.2.21 Void ........................................................................................................................................................ 2344
14.2.22 Void ........................................................................................................................................................ 2344
14.2.23 Interactive or background / UL:32 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH....... 2344
14.2.23.1 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC,10 ms TTI) .................................... 2344
14.2.23.2 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC, 20 ms TTI) ................................... 2345
14.2.23.3 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 10 ms TTI) ................................... 2346
14.2.23.4 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 20 ms TTI) ................................... 2347
14.2.23a Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ........ 2347
14.2.23a.1 Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH /
CC ..................................................................................................................................................... 2347
14.2.23a.2 Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH /
TC ..................................................................................................................................................... 2348
14.2.23b Interactive or background / UL:16 DL:16 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. .... 2348
14.2.23c Interactive or background / UL:32 DL:32 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. .... 2350
14.2.23d Interactive or background / UL:32 DL:32 kbps / PS RAB (20 ms TTI) +UL:3.4 DL:3.4 kbps SRBs
for DCCH. .............................................................................................................................................. 2352
14.2.24 Void ........................................................................................................................................................ 2353
14.2.25 Interactive or background / UL:32 DL: 64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH .... 2353
14.2.25.1 Interactive or background / UL:32 DL: 64 kbps / PS RAB / (TC, 10 ms TTI) ................................ 2353
14.2.25.2 Interactive or background / UL:32 DL: 64 kbps / PS RAB / (TC, 20 ms TTI) ................................ 2355
14.2.25.3 Interactive or background / UL:32 DL:64 kbps / PS RAB / (CC, 10 ms TTI) ................................. 2356
14.2.25.4 Interactive or background / UL:32 DL:64 kbps / PS RAB / (CC, 20 ms TTI) ................................. 2357
14.2.26 Interactive or background / UL:64 DL: 64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH .... 2357
14.2.27 Interactive or background / UL:64 DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ... 2359
14.2.28 Interactive or background / UL:128 DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH . 2361
14.2.29 Interactive or background / UL:64 DL:144 kbps / PS RAB +UL:3.4 DL: 3.4 kbps SRBs for DCCH .. 2363
14.2.30 Interactive or background / UL:144 DL:144 kbps / PS RAB +UL:3.4 DL: 3.4 kbps SRBs for DCCH 2365
14.2.31.1 Interactive or background / UL:64 DL:256 kbps / PS RAB +UL:3.4 DL: 3.4 kbps SRBs for
DCCH/ 10 ms TTI ............................................................................................................................ 2367
14.2.31.2 Interactive or background / UL:64 DL:256 kbps / PS RAB / 20 ms TTI ......................................... 2369
14.2.33.1 Interactive or background / UL:128 DL:384 kbps / PS RAB / 10 ms TTI ....................................... 2377
14.2.36 Void ........................................................................................................................................................ 2394
14.2.37 Void ........................................................................................................................................................ 2394
14.2.38 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:32
DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH .............................................................. 2394
14.2.38.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:32
DL:8 kbps / PS RAB / (TC, 20 ms TTI) ........................................................................................... 2394
DL:8 kbps / PS RAB / (TC, 10 ms TTI) ........................................................................................... 2397
DL:8 kbps / PS RAB / (CC, 20 ms TTI) ........................................................................................... 2399
Release 5 23 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
DL:8 kbps / PS RAB / (CC, 10 ms TTI) ........................................................................................... 2399
14.2.38a Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:0 DL:0
kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ...................................................................... 2399
14.2.38b Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:8 DL:8
14.2.38c Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:32
DL:32 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ........................................................... 2403
14.2.38d Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:64
DL:64 kbps / PS RAB +Interactive or background / UL:64 DL:64 kbps / PS RAB +UL:3.4 DL:3.4
kbps SRBs for DCCH. ........................................................................................................................... 2408
14.2.38e Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
Interactive or background / UL:0 DL:0 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ........ 2413
14.2.38f Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ........ 2416
14.2.38g Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
Interactive or background / UL:16 DL:16 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. .... 2421
14.2.38h Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
14.2.38i Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
14.2.38j Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9 4.75) kbps / CS RAB +
Interactive or background / UL:64 DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. .. 2446
DL:64 kbps / PS RAB+UL:3.4 DL: 3.4 kbps SRBs for DCCH ............................................................ 2457
DL:64 kbps / PS RAB / (TC, 10 ms TTI) ......................................................................................... 2457
DL:64 kbps / PS RAB / (TC, 20 ms TTI) ......................................................................................... 2462
DL:64 kbps / PS RAB / (CC, 10 ms TTI) ......................................................................................... 2468
DL:64 kbps / PS RAB+UL:3.4 DL: 3.4 kbps SRBs for DCCH ............................................................ 2468
DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH .......................................................... 2473
DL:256 kbps / PS RAB / 10 ms TTI ................................................................................................. 2479
DL:2048 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ........................................................ 2506
14.2.44.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background /
UL:128 DL:2048 kbps / PS RAB / 10 ms TTI ................................................................................. 2506
UL:128 DL:2048 kbps / PS RAB / 20 ms TTI ................................................................................. 2514
14.2.45 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Streaming / unknown / UL:57.6
DL:57.6 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ......................................................... 2527
14.2.46 Void ........................................................................................................................................................ 2532
14.2.47 Void ........................................................................................................................................................ 2532
14.2.48 Void ........................................................................................................................................................ 2532
Release 5 24 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
14.2.49 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown / UL:64
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ............................................................ 2532
14.2.49.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown / UL:64
DL:64 kbps / CS RAB / 20 ms TTI .................................................................................................. 2532
14.2.49.2 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB / 40 ms TTI ....................................................................................... 2535
14.2.49a Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL(12.2 7.95 5.9 4.75) kbps / CS RAB +
Conversational / unknown / UL:64 DL:64 kbps / CS RAB+UL:3.4 DL: 3.4 kbps SRBs for DCCH
(20ms TTI) ............................................................................................................................................. 2538
14.2.49a.1 Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL(12.2 7.95 5.9 4.75) kbps / CS RAB +
Conversational / unknown / UL:64 DL:64 kbps / CS RAB+UL:3.4 DL: 3.4 kbps SRBs for
DCCH (40ms TTI) ........................................................................................................................... 2543
14.2.50 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Conversational / unknown / UL:64
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ............................................................ 2548
14.2.50.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Conversational / unknown / UL:64
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 20 ms TTI .................................. 2548
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 40 ms TTI .................................. 2551
14.2.51 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Interactive or background / UL:64
DL:64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ............................................................ 2553
14.2.51.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI +Interactive or
background / UL:64 DL:64 kbps / PS RAB ..................................................................................... 2553
14.2.51a Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Interactive or Background / UL:8 DL:8
14.2.51a.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI +Interactive or
background / UL:8 DL:8 kbps / PS RAB ......................................................................................... 2560
14.2.51a.2 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 40 ms TTI +Interactive or
background / UL:8 DL:8 kbps / PS RAB ......................................................................................... 2562
14.2.51b Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Interactive or Background / UL:16
14.2.51b.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI +Interactive or
14.2.51b.2 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 40 ms TTI +Interactive or
background / UL:64 DL:128 kbps / PS RAB ................................................................................... 2573
background / UL:64 DL:128 kbps / PS RAB ................................................................................... 2577
background / UL:128 DL:128 kbps / PS RAB ................................................................................. 2581
background / UL:128 DL:128 kbps / PS RAB ................................................................................. 2585
14.2.54 Void ........................................................................................................................................................ 2589
14.2.55 Void ........................................................................................................................................................ 2589
14.2.56 Interactive or background / UL:8 DL:8 kbps / PS RAB +Interactive or background / UL:8 DL:8
14.2.57 Interactive or background / UL:64 DL:64 kbps / PS RAB +Interactive or background / UL:64
14.2.58 Streaming / unknown / UL:16 DL:64 kbps / PS RAB +Interactive or background / UL:8 DL:8 kbps
/ PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH. ............................................................................... 2593
14.2.59 Void ........................................................................................................................................................ 2596
14.2.60 Void ........................................................................................................................................................ 2596
14.2.61 Void ........................................................................................................................................................ 2596
14.2.62 Void ........................................................................................................................................................ 2596
Release 5 25 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
14.2.63 Interactive or background / UL:64 DL:768 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH
(Rel-5) .................................................................................................................................................... 2596
DCCH/ 10 ms TTI ............................................................................................................................ 2596
DCCH / 20 ms TTI ........................................................................................................................... 2596
14.3 Combinations on PDSCH and DPCH .......................................................................................................... 2600
14.3.1 Void ........................................................................................................................................................ 2600
14.3.4 Void ........................................................................................................................................................ 2612
DL:384 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 10 ms TTI................................. 2612
DL:384 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 20 ms TTI................................. 2617
DL:2048 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 10 ms TTI............................... 2623
DL:2048 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 10 ms TTI............................... 2630
14.4 Combinations on SCCPCH .......................................................................................................................... 2639
14.4.1 Stand-alone signalling RB for PCCH ..................................................................................................... 2639
14.4.2 Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH ..... 2639
14.4.2.1 One SCCPCH: Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for DCCH +
SRB for BCCH ................................................................................................................................. 2640
14.4.2.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for DCCH
+SRB for BCCH .............................................................................................................................. 2641
14.4.2.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB +SRBs for CCCH +
SRB for DCCH +SRB for BCCH .................................................................................................... 2642
14.4.2a Interactive/Background 32 kbps PS RAB +Interactive/Background 32 kbps PS RAB +SRBs for
CCCH +SRB for DCCH +SRB for BCCH .......................................................................................... 2644
14.4.2a.1 One SCCPCH: Interactive/Background 32 kbps PS RAB +Interactive/Background 32 kbps PS
RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH ......................................................... 2644
14.4.2a.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB +Interactive/Background 32 kbps PS
RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH ......................................................... 2646
14.4.2a.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB +
Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH 2647
14.4.3 Interactive/Background 32 kbps RAB +SRBs for PCCH + SRB for CCCH +SRB for DCCH +
SRB for BCCH ....................................................................................................................................... 2649
14.4.4 RB for CTCH +SRB for CCCH +SRB for BCCH. ............................................................................... 2650
14.5 Combinations on PRACH ............................................................................................................................ 2652
14.5.1 Interactive/Background 32 kbps PS RAB +SRB for CCCH +SRB for DCCH .................................... 2652
14.5.2 Interactive/Background 32 kbps PS RAB +Interactive/Background 32 kbps PS RAB +SRB for
CCCH +SRB for DCCH ....................................................................................................................... 2652
14.6 Combinations on DPCH and HS-PDSCH ................................................................................................... 2652
14.6.1 Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB +UL:3.4
DL:3.4 kbps SRBs for DCCH ................................................................................................................ 2652
14.6.2 Interactive or background / UL:384 DL: [max bit rate depending on UE category] / PS RAB +
UL:3.4 DL:3.4 kbps SRBs for DCCH .................................................................................................... 2658
15 Supplementary Services ..................................................................................................................... 2661
16 Short message service (SMS) ............................................................................................................. 2662
16.1 Short message service point to point on CS mode ....................................................................................... 2662
Release 5 26 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
16.1.1 SMS mobile terminated .......................................................................................................................... 2662
16.1.2 SMS mobile originated........................................................................................................................... 2668
16.1.3 Test of memory full condition and memory available notification: ....................................................... 2671
16.1.4 Test of the status report capabilities and of SMS-COMMAND:............................................................ 2675
16.1.5 Test of message class 0 to 3 ................................................................................................................... 2678
16.1.5.1 Short message class 0 ....................................................................................................................... 2678
16.1.5.2 Test of class 1 short messages .......................................................................................................... 2680
16.1.6 Test of short message type 0 (R99 and REL-4 UE) ............................................................................... 2684
16.1.6a Test of short message type 0 ( REL-5 UE) .......................................................................................... 2686
16.1.6a.5 Test requirements ............................................................................................................................. 2689
16.1.7 Test of the replace mechanism for SM type 1-7 ..................................................................................... 2689
16.1.8 Test of the reply path scheme ................................................................................................................. 2691
16.1.9 Multiple SMS mobile originated ............................................................................................................ 2694
16.1.9.1 UE in idle mode ................................................................................................................................ 2694
16.1.9.2 UE in active mode ............................................................................................................................ 2698
16.1.10 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated
short message ......................................................................................................................................... 2701
16.2 Short message service point to point on PS mode ....................................................................................... 2702
16.2.1 SMS mobile terminated .......................................................................................................................... 2702
16.2.2 SMS mobile originated........................................................................................................................... 2708
16.2.3 Test of memory full condition and memory available notification: ....................................................... 2712
16.2.4 Test of the status report capabilities and of SMS-COMMAND:............................................................ 2715
16.2.5 Test of message class 0 to 3 ................................................................................................................... 2719
16.2.5.1 Short message class 0 ....................................................................................................................... 2719
16.2.6 Test of short message type 0 (R99 and REL-4 UE) ............................................................................... 2725
16.2.6a Test of short message type 0 ( REL-5 UE) .......................................................................................... 2727
16.2.6a.5 Test requirements ............................................................................................................................. 2730
16.2.7 Test of the replace mechanism for SM type 1-7 ..................................................................................... 2730
16.2.8 Test of the reply path scheme ................................................................................................................. 2733
16.2.9 Multiple SMS mobile originated ............................................................................................................ 2736
16.2.9.1 UE in idle mode ................................................................................................................................ 2736
16.2.9.2 UE in active mode ............................................................................................................................ 2736
16.2.10 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated
short message ......................................................................................................................................... 2736
16.3 Short message service cell broadcast ........................................................................................................... 2737
16.4 Default message contents: ........................................................................................................................... 2739
16.4.1 Default message contents for SM-CP protocol ...................................................................................... 2739
16.4.2 Default message contents for SM-RP protocol ...................................................................................... 2739
16.4.3 Default message contents for SM-TP protocol....................................................................................... 2740
17 Specific features ................................................................................................................................. 2741
17.1 Test of autocalling restrictions ..................................................................................................................... 2741
17.1.1 General ................................................................................................................................................... 2741
17.1.2 Constraining the access to a single number (TS 22.001 category 3) ...................................................... 2742
17.1.3 Constraining the access to a single number (TS 22.001 categories 1 and 2) .......................................... 2744
17.1.4 Behaviour of the UE when its list of blacklisted numbers is full ........................................................... 2745
17.2 Location Services ......................................................................................................................................... 2746
17.2.1 Default conditions during LCS tests ...................................................................................................... 2746
17.2.1.1 Default system information .............................................................................................................. 2746
17.2.1.2 Simulated A-GPS environment ........................................................................................................ 2746
17.2.2 Assisted GPS Network Induced Tests .................................................................................................... 2746
17.2.2.1 LCS Network Induced location request/ UE-Based GPS/ Emergency Call / with USIM / Limited
Assistance Data ................................................................................................................................ 2746
17.2.3 Assisted GPS Mobile Originated Tests .................................................................................................. 2747
17.2.3.1 LCS Mobile originated location request/ UE-Based GPS/ Assistance data sent in multiple
measurement control messages ......................................................................................................... 2747
Release 5 27 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
17.2.4 Assisted GPS Mobile Terminated Tests ................................................................................................. 2747
18 Multi-Layer Functional Tests ............................................................................................................. 2747
18.1 Radio Bearer Tests for 1.28 Mcps TDD option ........................................................................................... 2747
18.1.1 General information for radio bearer tests (1.28 Mcps TDD) ................................................................ 2747
18.1.1.1 Generic radio bearer test procedure for Single RB configuration..................................................... 2747
18.1.1.2 Generic test procedure for testing multi-RB configuration and simulateneous signalling ............... 2747
18.1.2 Combinations on DPCH ......................................................................................................................... 2747
18.1.2.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH .......................................................................... 2747
18.1.2.2 Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH .......................................................................... 2748
18.1.2.3 Stand-alone UL:13.6 DL:13.6 kbps SRBs for DCCH ...................................................................... 2748
18.1.2.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2748
18.1.2.5 Conversational / speech / UL:10.2 DL:10.2 kbps / CS RAB +UL:3.4 DL: 3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2749
DCCH ............................................................................................................................................... 2751
18.1.2.7 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB+UL:3.4 DL:3.4 kbps SRBs for DCCH. 2752
18.1.2.8 Conversational / speech / UL:6.7 DL:6.7 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH 2754
18.1.2.9 Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH 2755
DCCH ............................................................................................................................................... 2757
DCCH ............................................................................................................................................... 2758
18.1.2.12 Conversational / unknown / UL:28.8 DL:28.8 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2760
18.1.2.13 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2761
18.1.2.13.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI .................................... 2761
18.1.2.14 Conversational / unknown / UL:32 DL:32 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2765
18.1.2.15 Streaming / unknown / UL:14.4/DL:14.4 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2768
DCCH ............................................................................................................................................... 2769
DCCH ............................................................................................................................................... 2771
18.1.2.18 Streaming / unknown / UL:0 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ....... 2773
18.1.2.19 Streaming / unknown / UL:64 DL:0 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ....... 2775
18.1.2.20 Void .................................................................................................................................................. 2777
18.1.2.21 Void .................................................................................................................................................. 2777
18.1.2.22 Void .................................................................................................................................................. 2777
18.1.2.23 Interactive or background / UL:32 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH . 2777
18.1.2.23.1 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC,10 ms TTI) ............................... 2777
18.1.2.23.2 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC, 20 ms TTI) .............................. 2778
18.1.2.23.3 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 10 ms TTI) .............................. 2780
18.1.2.23.4 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 20 ms TTI) .............................. 2780
18.1.2.24 Interactive or background / UL:64 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH . 2780
18.1.2.24.1 Interactive or background / UL:64 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH / TC ................................................................................................................................. 2780
18.1.2.24.2 Interactive or background / UL:64 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH / CC ................................................................................................................................. 2782
18.1.2.25 Interactive or background / UL:32 DL: 64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2782
18.1.2.25.1 Interactive or background / UL:32 DL: 64 kbps / PS RAB / (TC, 10 ms TTI) ........................... 2782
18.1.2.25.2 Interactive or background / UL:32 DL: 64 kbps / PS RAB / (TC, 20 ms TTI) ........................... 2783
18.1.2.25.3 Interactive or background / UL:32 DL:64 kbps / PS RAB / (CC, 10 ms TTI) ............................ 2785
18.1.2.25.4 Interactive or background / UL:32 DL:64 kbps / PS RAB / (CC, 20 ms TTI) ............................ 2785
Release 5 28 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
18.1.2.26 Interactive or background / UL:64 DL: 64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2785
18.1.2.27 Interactive or background / UL:64 DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for
DCCH ............................................................................................................................................... 2787
DCCH ............................................................................................................................................... 2789
DCCH ............................................................................................................................................... 2791
DCCH ............................................................................................................................................... 2793
DCCH ............................................................................................................................................... 2795
18.1.2.31.1 Interactive or background / UL:64 DL:256 kbps / PS RAB +UL:3.4 DL: 3.4 kbps SRBs for
DCCH/ 10 ms TTI ...................................................................................................................... 2795
18.1.2.31.2 Interactive or background / UL:64 DL:256 kbps / PS RAB / 20 ms TTI.................................... 2797
DCCH ............................................................................................................................................... 2799
DCCH ............................................................................................................................................... 2804
18.1.2.33.1 Interactive or background / UL:128 DL:384 kbps / PS RAB / 10 ms TTI.................................. 2804
DCCH ............................................................................................................................................... 2809
DCCH ............................................................................................................................................... 2814
DCCH ............................................................................................................................................... 2820
18.1.2.36.1 Interactive or background / UL:128 DL:2048 kbps / PS RAB / 10 ms TTI ................................ 2820
DCCH ............................................................................................................................................... 2826
18.1.2.38.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background /
UL:32 DL:8 kbps / PS RAB / (TC, 20 ms TTI) .......................................................................... 2834
UL:32 DL:8 kbps / PS RAB / (TC, 10 ms TTI) .......................................................................... 2837
UL:32 DL:8 kbps / PS RAB / (CC, 20 ms TTI) .......................................................................... 2839
UL:32 DL:8 kbps / PS RAB / (CC, 10 ms TTI) .......................................................................... 2839
DL:64 kbps / PS RAB+UL:3.4 DL: 3.4 kbps SRBs for DCCH ...................................................... 2839
UL:32 DL:64 kbps / PS RAB / (TC, 10 ms TTI) ........................................................................ 2839
UL:32 DL:64 kbps / PS RAB / (TC, 20 ms TTI) ........................................................................ 2844
UL:32 DL:64 kbps / PS RAB / (CC, 10 ms TTI) ........................................................................ 2849
18.1.2.39.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Interactive or background / UL:32
Release 5 29 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
DL:64 kbps / PS RAB+UL:3.4 DL: 3.4 kbps SRBs for DCCH ...................................................... 2849
DL:128 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH .................................................... 2854
UL:64 DL:256 kbps / PS RAB / 10 ms TTI ................................................................................ 2858
UL:128 DL:2048 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ..................................... 2882
UL:128 DL:2048 kbps / PS RAB / 10 ms TTI ............................................................................ 2882
UL:128 DL:2048 kbps / PS RAB / 20 ms TTI ............................................................................ 2890
18.1.2.45 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Streaming / unknown / UL:57.6
DL:57.6 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ................................................... 2903
18.1.2.46 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Streaming / unknown / UL:0
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ...................................................... 2908
18.1.2.47 Void .................................................................................................................................................. 2912
18.1.2.48 Void .................................................................................................................................................. 2912
18.1.2.49 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH........................................... 2912
18.1.2.49.1 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB / 20 ms TTI ................................................................................. 2912
18.1.2.49.2 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB / 40 ms TTI ................................................................................. 2915
DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ...................................................... 2917
18.1.2.50.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 20 ms TTI ................. 2917
18.1.2.50.2 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Conversational / unknown /
UL:64 DL:64 kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH / 40 ms TTI ................. 2920
18.1.2.51 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +Interactive or background / UL:64
DL:64 kbps / PS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ...................................................... 2922
18.1.2.51.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI +Interactive or
background / UL:64 DL:64 kbps / PS RAB ................................................................................ 2922
background / UL:64 DL:64 kbps / PS RAB ................................................................................ 2925
background / UL:64 DL:128 kbps / PS RAB .............................................................................. 2929
background / UL:64 DL:128 kbps / PS RAB .............................................................................. 2933
background / UL:128 DL:128 kbps / PS RAB ............................................................................ 2937
background / UL:128 DL:128 kbps / PS RAB ............................................................................ 2941
18.1.2.54 Interactive or background / UL:64 DL:128 kbps / PS RAB +Streaming / unknown / UL:0 DL:64
kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH ................................................................. 2945
Release 5 30 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
18.1.3 Combinations on SCCPCH .................................................................................................................... 2951
18.1.3.1 Stand-alone signalling RB for PCCH ............................................................................................... 2951
18.1.3.2 Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH 2951
18.1.3.2.1 One SCCPCH: Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for
DCCH +SRB for BCCH ............................................................................................................ 2951
18.1.3.2.1.1 Conformance requirement ..................................................................................................... 2951
18.1.3.2.1.2 Test purpose .......................................................................................................................... 2951
18.1.3.2.1.3 Method of Test ...................................................................................................................... 2952
18.1.3.2.1.4 Test Requirements ................................................................................................................. 2952
18.1.3.2.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB +SRBs for CCCH +SRB for
DCCH +SRB for BCCH ............................................................................................................ 2953
18.1.3.2.2.2 Test purpose .............................................................................................................................................. 2953
18.1.3.2.2.3 Method of Test ...................................................................................................................... 2953
18.1.3.2.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB +SRBs for CCCH
+SRB for DCCH +SRB for BCCH ........................................................................................... 2954
18.1.3.2.3.2 Test purpose .......................................................................................................................... 2954
18.1.3.2.3.3 Method of Test ...................................................................................................................... 2954
18.1.3.3 Interactive/Background 32 kbps RAB +SRBs for PCCH + SRB for CCCH +SRB for DCCH +
SRB for BCCH ................................................................................................................................. 2955
18.1.3.3.1 Conformance requirement........................................................................................................... 2955
18.1.3.3.2 Test purpose ................................................................................................................................ 2955
18.1.3.3.3 Method of Test ............................................................................................................................ 2956
18.1.3.3.4 Test requirements ........................................................................................................................ 2956
18.1.4 Combinations on PRACH ...................................................................................................................... 2957
18.1.4.1 Interactive/Background 32 kbps PS RAB +SRB for CCCH +SRB for DCCH .............................. 2957
Annex A (normative): Default RRC Message Contents ............................................................... 2958
Annex B: Void .................................................................................................................................... 2959
Annex C (Normative): Generic Test Procedures to Check UEs State ........................................ 2960
C.1 Verify that UE is in Idle Mode State............................................................................................................ 2960
C.2 Verify that UE is in CELL_FACH State ..................................................................................................... 2961
C.3 Verify that UE is in CELL_DCH State ........................................................................................................ 2963
C.4 Verify that UE is in CELL_PCH State ........................................................................................................ 2964
C.5 Verify that UE is in URA_PCH State .......................................................................................................... 2966
Annex D (informative): Change history ........................................................................................... 2968

Release 5 31 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 31
Foreword
This Technical Specification (TS) has been produced by the 3
rd
Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is the first part of a multi-part conformance specification valid for 3GPP Release 1999, 3GPP
Release 4 and 3GPP Release 5. 3GPP TS 34.123-2 [11] contains a pro-forma for the Implementation Conformance
Statement (ICS) and an applicability table, indicating the release from which each tescase is applicable. 3GPP TS
34.123-3 [12] contains a detailed and executable description of the test cases written in a standard testing language,
TTCN, as defined in ISO/IEC 9646.
For at least a minimum set of services, the prose descriptions of test cases will have a matching detailed test case
implemented in TTCN [12].
For Release 1999, the minimum set of services are defined as:
- voice calls;
- emergency calls;
- SMS (both Point-to-point and Cell broadcast);
- Circuit Switched data at up to 64 k bits/second;
- fax;
including the underlying layers to support these services.
Release 1999 will also include the areas:
- auto-calling restrictions.
The present document may contain descriptions of tests for additional services, but these tests may not have matching
TTCN test cases.
The present document will not contain any tests on the USIM, or the interface between the UE and the USIM. These
tests are documented elsewhere.
Release 5 32 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 32
1 Scope
The present document specifies the protocol conformance testing for the 3
rd
Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The following information relevant to testing can be found in accompanying specifications:
- the default setting of the test parameters [9];
- the applicability of each test case [11].
A detailed description of the expected sequence of messages can be found in the 3
rd
part of this test specification.
The Implementation Conformance Statement (ICS) pro-forma can be found in the 2
nd
part of the present document.
The present document is valid for UE implemented according to 3GPP Release 1999, 3GPP Release 4 or 3GPP Release
5.
2 References
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
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.
- For a Release 1999 UE, references to 3GPP documents are to version 3.x.y, when available.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[3] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[4] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[5] 3GPP TS 25.214: "Physical layer procedures (FDD)".
[6] 3GPP TS 25.321: "MAC protocol specification".
Release 5 33 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 33
[7] 3GPP TS 25.322: "RLC protocol specification".
[8] 3GPP TS 25.331: "RRC Protocol Specification".
[9] 3GPP TS 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing".
[10] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[11] 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[12] 3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract Test Suites
(ATS)".
[13] 3GPP TS 51.010-1: "Mobile Station (MS) conformance specification; Part 1: Conformance
specification ".
[14] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework".
[15] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected
Mode".
[16] 3GPP TS 34.121: "Terminal Conformance Specification; Radio Transmission and Reception
(FDD)".
[17] 3GPP TS 34.122: "Terminal Conformance Specification; Radio Transmission and Reception
(TDD)".
[18] 3GPP TS 31.102: "Characteristics of the USIM Application".
[19] 3GPP TS 25.224: "Physical Layer Procedures (TDD)".
[20] 3GPP TS 25.215: "Physical layer - Measurements (FDD)".
[21] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)".
[22] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)".
[23] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".
[24] 3GPP TS 03.22: "Functions related to Mobile Station (MS) in idle mode and group receive mode".
[25] 3GPP TS 04.18: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[26] 3GPP TS 05.08: "Radio Subsystem Link Control".
[27] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land
Mobile Network (PLMN)".
[28] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[29] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels
(FDD)".
[30] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) Specification".
[31] 3GPP TS 33.102: "3G Security; Security Architecture".
[32] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
[33] Void.
[34] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[35] 3GPP TS 23.038: "Alphabets and language-specific information".
Release 5 34 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 34
[36] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[37] 3GPP TS 25.324: "Broadcast/Multicast Control BMC".
[38] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[39] RFC 2507: "IP Header Compression".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 apply, unless specified below:
example: text used to clarify abstract rules by applying them literally
Floor: Floor(x) is the largest integer smaller than or equal to x.
Ceil: Ceil (x) is the smallest integer larger than or equal to x.
3.2 Abbreviations
For the purposes of the present document, the abbreviations specified in TR 21.905 apply, with any additional
abbreviations specified below:
SS System Simulator
4 Overview
4.1 Test Methodology
4.1.1 Testing of optional functions and procedures
Any function or procedure which is optional, as indicated in the present document , may be subject to a conformance
test if it is implemented in the UE.
A declaration by the apparatus supplier (ICS) is used to determine whether an optional function/procedure has been
implemented.
4.1.2 Test interfaces and facilities
Detailed descriptions of the UE test interfaces and special facilities for testing are provided in [10].
4.2 Implicit Testing
For some 3GPP signalling and protocol features conformance is not verified explicitly in the present document. This
does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a
sufficient degree in other tests.
Release 5 35 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 35
5 Reference Conditions
The reference environments used by all signalling and protocol tests are specified in TS 34.108. Where a test requires
an environment that is different, this will be specified in the test itself.
5.1 Generic setup procedures
A set of basic generic procedures for radio resource signalling, and generic setup procedures for layer 3 NAS signalling
are described in TS 34.108 clause 7. These procedures are used in numerous test cases throughout the present
document.
6 Idle mode operations
In the following paragraphs some explanatory text is given concerning the nature of the tests in this clause and the
general behaviour of the SS is described.
Since the conformance requirements of most of the tests in this clause cannot be tested explicitly, testing is done
implicitly by testing the UE behaviour from its responses to the SS.
In some cases, a test is performed in multiple stages in order that the requirements can be tested within the above
constraints.
For any UE all the carriers are in its supported band(s) of operation.
Unless otherwise stated in the method of test, in all of the tests of this clause:
- the default values of the system information data fields given in TS 34.108 are used;
- the UE is equipped with a USIM containing default values. The USIM is in the idle updated state in the default
location area with a TMSI assigned at the beginning of each test;
- default cell numbering as defined in TS 34.108 clause 6.1 have been used in the cell selection and re-selection
test cases;
- the cells shall be configured such that Squal>0 (FDD only) and Srxlev>0 while applying Qqualmin (FDD only)
and Qrxlevmin in table 6.1. In addition, for an FDD cell, the measured primary CPICH RSCP value shall be
greater than or equal to -95 dBm (definition of High Quality cell, see TS 25.304, clause 5.1.2.2). In addition, for
a TDD cell, the measured P-CCPCH RSCP shall be greater than or equal to 84 dBm (definition of High Quality
cell, see TS 25.304, clause 5.1.2.2).
Three different methods A, B and C are applied in the tests:
Method A:
- the SS is continuously paging the UE on all cells at the start of the test and does not respond to RACH requests
from the UE (which causes a cell reselection). Where a test specifies that the UE is not paged on a particular cell,
only idle paging is transmitted. This method is similar to the one used in TS 51.010-1, clause 20.
Method B:
- the SS is continuously paging the UE on all cells at the start of the test and responds to RACH requests from the
UE with an IMMEDIATE ASSIGNMENT REJ ECT (GERAN cell) or RRC CONNECTION REJ ECT (UTRAN
cell) message which causes the UE to return to Idle mode. Where a test specifies that the UE is not paged in a
particular cell, only idle paging is transmitted.
Method C:
- no continuously paging as in method A or B. Normal response to RACH requests so Location Updating and
Calls can be done.
Release 5 36 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 36
In case a test specifies that UE shall read System Information on BCCH while camped on a UTRAN cell, SS shall
notify UE on the BCCH modification by sending a PAGING TYPE 1 message to UE. This message shall contain IE
BCCH Modification Info with the following settings:
Information Element Value/remark
BCCH modification info
MIB Value Tag Set to the same value as the value tag of the MIB after
the BCCH modification
BCCH Modification time Not present

Table 6.1: Default values of the system information fields
Parameter Setting
IMSI attach/detach Method A, B: Not allowed
Method C: Allowed
Intra-frequency cell re-selection
indicator
Allowed
Cell_selection_and_reselection_qua
lity_measure
CPICH RSCP (FDD)
Qqualmin (FDD only) -24 dB
Qrxlevmin (FDD) -115 dBm
Qrxlevmin (TDD) -103 dBm
DRX cycle length 1,28 s

For a UE camping in a FDD cell, CPICH_Ec/Io and SCH_Ec/Io shall fulfill requirements in TS 25.133, clause
8.1.2.2.1: The UE is able to identify a new detectable cell belonging to the monitored set within T
identify intra
when CPICH
Ec/Io >-20 dB and SCH_Ec/Io >-20 dB.
For a UE camping in a TDD cell, the UE shall be able to identify a new detectable cell belonging to the monitored set
within T
identify intra
whenfulfill requirements in TS 25.123, clause 8.1.2.2. for TDD 3.84 Mcps option and 8.1A.2.2 for
TDD 1.28 Mcps option.
It is a UE option whether to indicate access technologies to the user (TS 23.122, clause 4.4.3.1.2). Therefore, for
combined UTRAN/GSM tests, it is indicated in parentheses which access technology shall be indicated to the user if the
UE has this capability.
If a parameter is indicated with a *, it means that the parameter is calculated internally in the UE and is only shown for
clarification of the test procedure.
The PLMN numbers indicated in table 6.2 are used in test cases to associate a cell with an MCC and MNC for that cell.
If no PLMN is explicitly specified, the default value is PLMN 1.
Table 6.2: Location Area Information (LAI) in System Information
type 3 messages broadcast on the BCCH (GSM) or System Information Block Type 1 broadcast on
the BCH (UMTS)
PLMN MCC1 MCC2 MCC3 MNC1 MNC2 MNC3 LAC
1 0 0 1 0 1 Not present x
NOTE: 'x' denotes any value.

Release 5 37 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 37
References: TS 23.122, annex A and TS 23.003, clause 2.
The test channel numbers indicated in tables 6.3, 6.4, 6.4a and 6.5 are used in test cases to associate a cell with a
frequency for that cell. The frequencies for GSM and DCS cells in table 6.5 are identical to those used in TS 51.010-1,
clause 26.3.1. The RF signal levels are given in table 6.5 for GSM cells, in table 6.3 for UTRAN FDD cells, in table 6.4
for UTRAN TDD cells 3.84 Mcps option and in table 6.4a for UTRAN TDD cells 1.28 Mcps option. If no channel is
explicitly specified, the default value is Test Channel 1.
Table 6.3: UTRA (FDD) test frequenci es
Band I Band II Band III
Test
Channel
CPICH_Ec
dBm / 3.84
MHz
Uplink
UARFCN
CPICH_Ec
dBm / 3.84
MHz
Uplink
UARFCN
CPICH_Ec
dBm / 3.84
MHz
Uplink
UARFCN
1 -60 9 613 -60 9 263 -60 8 563
2 -65 9 663 -65 9 313 -65 8 613
3 -70 9 713 -70 9 363 -70 8 663
4 -75 9 763 -75 9 413 -75 8 713
5 -80 9 813 -80 9 463 -80 8 763
6 -85 9 863 -85 9 513 -85 8 813

References: TS 34.108, clause 5.1.1 and TS 34.121, clause 4.
Table 6.4: UTRA TDD test frequenci es (3.84 Mcps option)
Band a Band b Band c
Test
Channel
P-CCPCH_
RSCP
[dBm]
UARFCN P-CCPCH_
RSCP
[dBm]
UARFCN

P-CCPCH_
RSCP
[dBm]
UARFCN
1 -54 9 513 -54 9 263 -54 9563
2 -59 9 550 -59 9 400 -59 9577
3 -64 9 587 -64 9 537 -64 9591
4 -69 10 063 -69 9 663 -69 9605
5 -74 10 087 -74 9 800 -74 9619
6 -79 10 112 -79 9 937 -79 9637

Table 6.4a: UTRA TDD test frequencies (1.28 Mcps option)
Band a Band b Band c
Test
Channel
P-CCPCH_
RSCP [dBm]
UARFCN P-CCPCH_
RSCP [dBm]
UARFCN P-CCPCH_
RSCP [dBm]
UARFCN
1 -54 9 505 -54 9 255 -54 9555
2 -59 9 550 -59 9 400 -59 9573
3 -64 9 595 -64 9 545 -64 9591
4 -69 10 055 -69 9 655 -69 9608
5 -74 10 088 -74 9 800 -74 9626
6 -79 10 120 -79 9 945 -79 9645

References: TS 34.108, clause 5.1.2 and TS 34.122, clause 4.
Release 5 38 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 38
Table 6.5: GSM/DCS test frequenci es and levels
GSM 900 DCS 1 800
Test
Channel
level
dBmVemf( )
/ dBm
BCCH ARFCN level
dBmVemf( )
/ dBm
BCCH ARFCN
1 +65 / -48 1 +65 / -48 520
2 +63 / -50 7 +63 / -50 580
3 +61 / -52 39 +61 / -52 610
4 +55 / -58 65 +55 / -58 702
5 +59 / -54 66 +59 / -54 703
6 +57 / -56 85 +57 / -56 830
7 +55 / -58 97 +55 / -58 885
8 +53 / -60 124

GSM 450 DCS 480
Test
Channel
level
dBmVemf( )
/ dBm
BCCH ARFCN level
dBmVemf( )
/ dBm
BCCH ARFCN
1 +65 / -48 259 +65 / -48 306
2 +63 / -50 261 +63 / -50 308
3 +61 / -52 267 +61 / -52 314
4 +55 / -58 268 +55 / -58 315
5 +59 / -54 281 +59 / -54 328
6 +57 / -56 288 +57 / -56 335
7 +55 / -58 291 +55 / -58 338
8 +53 / -60 293 +53 / -60 340

Multiband 900/1800 PCS 1900
Test
Channel
level
dBmVemf( )
/ dBm
BCCH ARFCN level
dBmVemf( )
/ dBm
BCCH ARFCN
1 +65 / -48 520 +65 / -48 512
2 +63 / -50 7 +63 / -50 520
3 +61 / -52 39 +61 / -52 580
4 +55 / -58 702 +55 / -58 610
5 +59 / -54 66 +59 / -54 702
6 +57 / -56 85 +57 / -56 703
7 +55 / -58 885 +55 / -58 800
8 +53 / -60 124

Multiband 450/900 Multiband 480/900
Test
Channel
level
dBmVemf( )
/ dBm
BCCH ARFCN level
dBmVemf( )
/ dBm
BCCH ARFCN
1 +65 / -48 1 +65 / -48 1
2 +63 / -50 261 +63 / -50 308
3 +61 / -52 267 +61 / -52 314
4 +55 / -58 65 +55 / -58 65
5 +59 / -54 281 +59 / -54 328
6 +57 / -56 288 +57 / -56 335
7 +55 / -58 124 +55 / -58 124
8 +53 / -60 293 +53 / -60 340

Release 5 39 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 39
Multiband 450/1800 Multiband 480/1800
Test
Channel
level
dBmVemf( )
/ dBm
BCCH ARFCN level
dBmVemf( )
/ dBm
BCCH ARFCN
1 +65 / -48 520 +65 / -48 520
2 +63 / -50 261 +63 / -50 308
3 +61 / -52 267 +61 / -52 314
4 +55 / -58 702 +55 / -58 702
5 +59 / -54 281 +59 / -54 328
6 +57 / -56 288 +57 / -56 335
7 +55 / -58 885 +55 / -58 885
8 +53 / -60 293 +53 / -60 340

For testing an E-GSM Mobile station, the BCCH ARFCN of GSM Test Channel 7 at GSM 900 column shall be 985
(instead of 97). For testing an R-GSM Mobile station, the BCCH ARFCN of GSM Test Channel 7 at GSM 900 column
shall be 965 (instead of 97).
6.1 In a pure 3GPP environment
6.1.1 PLMN selection
6.1.1.1 PLMN selection of RPLMN, HPLMN, UPLMN and OPLMN; Manual mode
6.1.1.1.1 Definition
Test to verify that the UE can present the available PLMNs in priority order to the user when asked to do so in manual
mode and that the displayed PLMNs can be selected / reselected by the user. Forbidden PLMNs shall also by displayed
in the list. If available, the RPLMN shall be selected at switch-on, otherwise the displayed list shall include in priority
order HPLMN, User-PLMN and Operator-PLMN. The last priority in the list is "Other PLMN/access technology
combinations" which is not included in this test.
Only UTRAN cells and a UE equipped with a USIM with Radio Access Technology fields set to UTRAN are
considered.
6.1.1.1.2 Conformance requirement
1. At switch on, or following recovery from lack of coverage,the MS selects the registered PLMN or equivalent
PLMN (if it is available) using all access technologies that the MS is capable of and if necessary (in the case of
recovery from lack of coverage, see TS 23.122, clause 4.5.2) attempts to perform a Location Registration.
If successful registration is achieved, the MS indicates the selected PLMN.
If there is no registered PLMN, or if registration is not possible due to the PLMN being unavailable or
registration failure, the MS follows either Automatic or Manual Network Selection Mode Procedure depending
on its operating mode.
2. Manual Network Selection Mode Procedure:
The MS indicates whether there are any PLMNs, which are available using all supported access technologies.
This includes PLMNs in the "forbidden PLMNs" list and PLMNs which only offer services not supported by the
MS.
If displayed, PLMNs meeting the criteria above are presented in the following order:
2.1 HPLMN;
2.2 PLMNs contained in the "User Controlled PLMN Selector with Access Technology" data field in the SIM
(in priority order);
2.3 PLMNs contained in the "Operator Controlled PLMN Selector with Access Technology" data field in the
SIM (in priority order);
Release 5 40 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 40
2.4 Other PLMN/access technology combinations with received high quality signal in random order;
2.5 Other PLMN/access technology combinations in order of decreasing signal quality.
The user may select his desired PLMN and the MS then initiates registration on this PLMN using the access
technology chosen by the user for that PLMN or using the highest priority available access technology for that
PLMN, if the associated access technologies have a priority order. (This may take place at any time during the
presentation of PLMNs). For such a registration, the MS shall ignore the contents of the "forbidden LAs for
roaming", "forbidden LAs for regional provision of service", "forbidden PLMNs for GPRS service" and
"forbidden PLMNs" lists.
If the user does not select a PLMN, the selected PLMN shall be the one that was selected before the PLMN
selection procedure started. If no such PLMN was selected or that PLMN is no longer available, then the MS
shall attempt to camp on any acceptable cell and enter the limited service state.
3. If a "PLMN not allowed" message is received by an MS in response to an LR request from a VPLMN, that
VPLMN is added to a list of "forbidden PLMNs" in the SIM and thereafter that VPLMN will not be accessed by
the MS when in automatic mode. A PLMN is removed from the "forbidden PLMNs" list if, after a subsequent
manual selection of that PLMN, there is a successful LR. This list is retained when the MS is switched off or the
SIM is removed. The HPLMN shall not be stored on the list of "forbidden PLMNs".
References
1. TS 23.122, clause 4.4.3.1;
2. TS 23.122, clause 4.4.3.1.2;
3. TS 23.122, clause 3.1.
NOTE: TS 31.102 defines the USIM fields.
6.1.1.1.3 Test purpose
1. To verify that if available, the RPLMN is selected at switch-on.
2. To verify that in Manual Network Selection Mode Procedure, the UE presents the HPLMN, UPLMN and
OPLMN in a prioritized order.
3. To verify that forbidden PLMNs are also displayed in the list.
6.1.1.1.4 Method of test
Initial conditions
The UE is in manual PLMN selection mode.
Cell levels are from table 6.3. (FDD).
All Radio Access Technology USIM fields and cells are UTRAN.
Cell CPICH_
Ec [dBm/3.84
MHz]
(FDD)
P-CCPCH_
RSCP [dBm]
(TDD)
Test Channel PLMN
Cell 1 -60 -54 1 PLMN 1
Cell 2 -65 -59 2 PLMN 2
Cell 3 -70 -64 3 PLMN 3
Cell 4 -75 -69 4 PLMN 4
Cell 5 -80 -74 5 PLMN 5
Cell 6 -85 -79 6 PLMN 6

Release 5 41 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 41
The UE is equipped with a USIM containing default values except for those listed below.
USIM field Priority PLMN
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2
EFPLMNwAcT 1
st
PLMN 3
2
nd
PLMN 4
EFOPLMNwAcT 1
st
PLMN 5
2
nd
PLMN 6
EFFPLMN PLMN 3
Test procedure
Method C is applied.
a) The SS activates cells 1-6 and monitors the cells for random access requests from the UE.
b) The UE is switched on.
c) The SS waits for random access requests from the UE.
d) Cell 1 is switched off.
e) PLMN 4 shall be selected when the PLMN list is presented.
f) The SS waits for random access requests from the UE.
g) Cell 4 is switched off.
h) PLMN 3 shall be selected when the PLMN list is presented. The SS shall reject the Registration Request from
the UE.
i) PLMN 5 shall be selected (the list is already available).
j) The SS waits for random access requests from the UE.
k) Cell 5 is switched off.
l) PLMN 2 shall be selected when the PLMN list is presented.
m) The SS waits for random access requests from the UE.
n) Cell 2 is switched off.
o) PLMN 6 shall be selected when the PLMN list is presented.
p) The SS waits for random access requests from the UE.
q) Cell 6 is switched off.
6.1.1.1.5 Test Requirements
1) In step c), the response from the UE shall be on Cell 1. The displayed PLMN shall be PLMN 1.
2) In step e), the list shall be presented. The priority shall be as follows: PLMN 2, PLMN 3, PLMN 4, PLMN 5,
PLMN 6.
3) In step f), the response from the UE shall be on Cell 4. The displayed PLMN shall be PLMN 4.
4) In step h), the list shall be presented. The priority shall be as follows: PLMN 2, PLMN 3, PLMN 5, PLMN 6.
After PLMN 3 has been selected, the list shall appear again as the UE cannot perform registration.
6) In step j), the response from the UE shall be on Cell 5. The displayed PLMN shall be PLMN 5.
7) In step l), the list shall be presented. The priority shall be as follows: PLMN 2, PLMN 3, PLMN 6.
8) In step m), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN 2.
Release 5 42 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 42
9) In step o), the list shall be presented. The priority shall be as follows: PLMN 3, PLMN 6.
10) In step p), the response from the UE shall be on Cell 6. The displayed PLMN shall be PLMN 6.
11) After step q), the UE shall inform that only limited service is possible.
6.1.1.2 PLMN selection of "Other PLMN / access technology combinations"; Manual
mode
Test to verify that the UE can present the available high quality signal PLMNs in random order to the user when asked
to do so in manual mode and that the displayed PLMNs can be selected / reselected by the user. Forbidden PLMNs shall
also by displayed in the list.
considered.
MS.
2.1 HPLMN;
In 2.5, the MS shall order the PLMN/access technology combinations in order of decreasing signal quality
within each access technology. The order between PLMN/access technology combinations with different access
technologies is an MS implementation issue.
Release 5 43 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 43
4. The UE shall scan all RF channels in the UTRA band according to its capabilities to find available PLMNs. On
each carrier, the UE shall search for the strongest cell according to the cell search procedures (for FDD, see
TS 25.214, and TDD, see TS 25.224) and read its system information, in order to find out which PLMN the cell
belongs to. If the UE can read the PLMN identity, the found PLMN shall be reported to the NAS as a high
quality PLMN (but without the RSCP value), provided that the following high quality criterion is fulfilled:
- For an FDD cell, the measured primary CPICH RSCP value shall be greater than or equal to -95 dBm.
- For a TDD cell, the measured P-CCPCH RSCP shall be greater than or equal to 84 dBm.
Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the
PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and P-
CCPCH RSCP for UTRA TDD cells.
References
1. TS 23.122, clause 4.4.3.1.
2. TS 23.122, clause 4.4.3.1.2.
3. TS 23.122, clause 3.1.
4. TS 25.304, clause 5.1.2.2.
1. To verify that in Manual Network Selection Mode Procedure, the UE presents "Other PLMN/access technology
combinations" in a random order according to conformance requirement 2.4. UE requirement on measurement
accuracy for PLMN selection is not specified in core specifications. Therefore, the ordering of PLMNs according
to conformance requirement 2.5 is not tested.
Initial conditions
Cell CPICH_Ec
[dBm/3.84
MHz]
(FDD)
P-CCPCH_
RSCP [dBm]
(TDD)
High Quality
signal
Test Channel PLMN
Cell 1 -85 -74 Yes 1 PLMN 6
Cell 4 -80 -69 Yes 4 PLMN 10

EFLOCI PLMN 6
EFFPLMN PLMN 10

Release 5 44 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 44
Test procedure
c) PLMN 6 shall be selected when the PLMN list is presented.
d) The SS waits for random access requests from the UE.
e) Cell 1 is switched off.
f) PLMN 7 shall be selected when the PLMN list is presented.
g) The SS waits for random access requests from the UE.
h) Cell 2 is switched off.
i) PLMN 8 shall be selected when the PLMN list is presented.
l) PLMN 10 shall be selected when the PLMN list is presented. The SS shall accept the Registration Request from
the UE.
m) Cell 4 is switched off.
1) In step c), the list shall be presented. The priority shall be as follows: PLMN 6 followed by PLMN 7, PLMN 8
and PLMN 10 in random order.
2) In step d), the response from the UE shall be on Cell 1. The displayed PLMN shall be PLMN 6.
3) In step f), the list shall be presented. The priority shall be as follows: PLMN 7, PLMN 8 and PLMN 10 in
random order.
4) In step g), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN 7.
5) In step i), the list shall be presented. The priority shall be as follows: PLMN 8 and PLMN 10 in random order.
7) In step l), the list shall be presented containing only PLMN 10. The UE shall perform successful registration on
Cell 4.
8) After step m), the UE shall inform that no network is available.
6.1.1.3 PLMN selection; independence of RF level and preferred PLMN; Manual
mode
Test to verify that in Manual Network Selection Mode, the UE is able to obtain normal service on a PLMN which is
neither the better nor a preferred PLMN and that it tries to obtain service on a VPLMN if and only if the user selects it
manually.
Release 5 45 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 45
MS.
2.1 HPLMN;
References
1. TS 23.122, clause 4.4.3.1.
2. TS 23.122, clause 4.4.3.1.2
1. To verify that the selected PLMN at switch-on is the HPLMN.
2. To verify that in Manual Network Selection Mode Procedure the UE tries to obtain service on a VPLMN if and
only if the user selects it manually.
3. To verify that the UE is able to obtain normal service on a PLMN which is neither the better nor a prefered
PLMN.
Release 5 46 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 46
Initial conditions
"IMSI attach" flag in the BCCH is set to allowed.
For FDD only:
Step a-d:
Parameter Unit Cell 1 Cell 2 Cell 3
Test Channel 1 2 3
CPICH_Ec
dBm/3.84
MHz
-60 -70 OFF
PLMN 1 2 3
Step e-f:
CPICH_Ec
dBm/3.84
MHz
-60 ->OFF -70 OFF
Step g-h:
CPICH_Ec
dBm/3.84
MHz
OFF -70 OFF ->-60
Step i-l:
CPICH_Ec
dBm/3.84
MHz
OFF -70 ->OFF -60

For TDD only:
Step a-d:
Test Channel 1 2 3
P-CCPCH RSCP dBm -69 -74 OFF
PLMN 1 2 3
Step e-f:
P-CCPCH RSCP -69 ->OFF -74 OFF
Step g-h:
P-CCPCH RSCP OFF -74 OFF ->-69
Step k-l:
P-CCPCH RSCP OFF -74 ->OFF -69

EFLOCI
EFHPLMNwAcT 1
st
PLMN 1
EFPLMNwAcT 1
st
PLMN 3
Test procedure
a) The SS activates cells 1 and 2.
c) PLMN 1 is selected manually.
Release 5 47 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 47
d) The SS waits for random access requests from the UE. A complete Location Update is done.
f) The SS waits to see if there is any random access request from the UE.
g) Cell 3 is switched on.
h) The SS waits to see if there is any random access request from the UE.
i) PLMN 2 is selected manually.
j) The SS waits for random access requests from the UE. A complete Location Update is done.
l) The SS waits to see if there is any random access request from the UE.
1) In step d), there shall be a response on Cell 1. The selected PLMN shall be PLMN 1.
2) In step f), there shall be no response from the UE within 2 min.
3) In step h), there shall be no response from the UE within 2 min.
4) In step j), there shall be a response on Cell 2. The selected PLMN shall be PLMN 2.
5) In step l), there shall be no response from the UE within 2 min.
6.1.1.4 PLMN selection of RPLMN, HPLMN, UPLMN and OPLMN; Automatic mode
Test to verify that in Automatic Network Selection Mode, the UE selects PLMNs in a prioritized order. Forbidden
PLMNs shall not be selected. If available, the RPLMN shall be selected at switch-on, otherwise the list shall include in
priority order HPLMN, User-PLMN and Operator-PLMN. The last priority in the list is "Other PLMN/access
technology combinations" which is not included in this test.
considered.
2. Automatic Network Selection Mode Procedure:
The MS selects and attempts registration on other PLMNs, if available and allowable in the following order:
2.1 HPLMN (if not previously selected);
2.2 Each PLMN in the "User Controlled PLMN Selector with Access Technology" data field in the SIM (in
priority order);
2.3 Each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM
Release 5 48 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 48
If registration cannot be achieved because no PLMNs are available and allowable, the MS indicates "no service"
to the user, waits until a new PLMN is available and allowable and then repeats the procedure.
If there were one or more PLMNs which were available and allowable, but an LR failure made registration on
those PLMNs unsuccessful or an entry in the "forbidden LAs for regional provision of service" list prevented a
registration attempt, the MS selects the first such PLMN again and enters a limited service state.
References
1. TS 23.122, clause 4.4.3.1.
2. TS 23.122, clause 4.4.3.1.1.
3. TS 23.122, clause 3.1.
1. To verify that if available, the RPLMN is selected at switch-on.
2. To verify that in Automatic Network Selection Mode Procedure, the UE selects the RPLMN, HPLMN, UPLMN
and OPLMN in a prioritized order.
3. To verify that forbidden PLMNs are not selected.
Initial conditions
The UE is in automatic PLMN selection mode.
"IMSI attach" flag in the BCCH is set to allowed.
Cell levels are from table 6.3 (FDD).
Cell CPICH_
Ec [dBm/3.84
MHz]
(FDD)
P-CCPCH_
RSCP [dBm]
(TDD)
Test Channel PLMN
Cell 1 -60 -54 1 PLMN 1
Cell 2 -65 -59 2 PLMN 2
Cell 3 -70 -64 3 PLMN 3
Cell 4 -75 -69 4 PLMN 4
Cell 5 -80 -74 5 PLMN 5
Cell 6 -85 -79 6 PLMN 6

Release 5 49 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 49
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2
EFPLMNwAcT 1
st
PLMN 3
2
nd
PLMN 4
EFOPLMNwAcT 1
st
PLMN 5
2
nd
PLMN 6
EFFPLMN PLMN 3

Test procedure
e) The SS waits for random access requests from the UE.
f) Cell 2 is switched off.
i) Cell 4 is switched off.
l) The SS waits for random access requests from the UE.
m) Cell 6 is switched off.
2) In step e), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN 2.
3) In step g), the response from the UE shall be on Cell 4. The displayed PLMN shall be PLMN 4.
5) In step l), the response from the UE shall be on Cell 6. The displayed PLMN shall be PLMN 6.
6) After step m), the UE shall inform that only limited service is possible
6.1.1.5 PLMN selection of "Other PLMN / access technology combinations";
Automatic mode
Test to verify that in Automatic Network Selection Mode, the UE selects high quality signal PLMNs in a random order.
considered.
Release 5 50 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 50
priority order);
4. The UE shall scan all RF channels in the UTRA band according to its capabilities to find available PLMNs. On
each carrier, the UE shall search for the strongest cell according to the cell search procedures (for FDD, see
TS 25.214, and TDD, see TS 25.224) and read its system information, in order to find out which PLMN the cell
belongs to. If the UE can read the PLMN identity, the found PLMN shall be reported to the NAS as a high
quality PLMN (but without the RSCP value), provided that the following high quality criterion is fulfilled:
PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and P-
CCPCH RSCP for UTRA TDD cells.
References
1. TS 23.122, clause 4.4.3.1.
2. TS 23.122, clause 4.4.3.1.1.
Release 5 51 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 51
3. TS 23.122, clause 3.1.
4. TS 25.304, clause 5.1.2.2.
1. To verify that in Automatic Network Selection Mode Procedure, the UE selects "Other PLMN/access technology
combinations" in a random order according to conformance requirement 2.4. UE requirement on measurement
accuracy for PLMN selection is not specified in core specifications. Therefore, the ordering of PLMNs according
to conformance requirement 2.5 is not tested.
Initial conditions
Cell CPICH_Ec
[dBm/3.84
MHz]
(FDD)
P-CCPCH_ RSCP
[dBm]
(TDD)
High
Quality
signal
Test Channel PLMN

EFLOCI PLMN 6

Test procedure
f) The cell associated to the currently shown PLMN shall be switched off.
2) In step e), the response from the UE shall be on either Cell 2 or 3. The displayed PLMN shall be the one
associated with the cell on which the response was received.
3) In step g), the response from the UE shall be on either Cell 2 or 3 (excluding the cell in step 2). The displayed
PLMN shall be the one associated with the cell on which the response was received.
Release 5 52 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 52
6.1.1.6 Void
6.1.1.7 Cell reselection of ePLMN in manual mode
Test to verify that the UE shall be able to reselect to a cell of another PLMN declared as equivalent PLMN to the
registered PLMN in the manual mode.
B) Manual network selection mode
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different
PLMN unless:
i) The new PLMN is declared as an equivalent PLMN by the registered PLMN;
or,
ii) The user selects automatic mode.
References:
TS 22.011 clause 3.2.2.2B
To verify that in Manual Network Selection Mode Procedure, the UE can perform cell reselection to an equivalent
PLMN.
Initial conditions
Cell_selection_and_reselection_quality_measure is CPICH_RSCP (FDD).
Each cell shall include the other cells as neighbouring cells in System Information Block Type 11.

Cell CPICH_Ec
[dBm/3.84 MHz]
(FDD)
P-CCPCH_
RSCP [dBm]
(TDD)
Test Channel PLMN
Cell 1 -78 -69 1 PLMN 1
Cell 4 -62 -54 2 PLMN 2
Cell 5 -68 -64 3 PLMN 3

PLMN1 is the HPLMN.
Release 5 53 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 53
EFLOCI PLMN 1

Test procedure
a) The SS activates cells 1.
d) A Location Update Accept message shall be sent on reception of a Location Update message from the UE. The
Location Update Accept message shall include PLMN3 in the equivalent PLMN list.
e) Cell 4 and 5 are activated.
2) In step e), the UE shall perform a cell reselection and Location Update to PLMN 3, which is equivalent to
PLMN1.
6.1.2 Cell selection and reselection
6.1.2.1 Cell reselection
Test to verify that the UE performs the cell reselection correctly for intra/inter-frequency cells if the serving cell
becomes barred or S<0.
1. When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If
a better cell is found, that cell is selected. The change of cell may imply a change of RAT.
2. A "suitable cell" is a cell on which the UE may camp on to obtain normal service. Such a cell shall fulfil all the
following requirements.
2.1 The cell is part of the selected PLMN or of a PLMN considered as equivalent by the UE according to the
information provided by the NAS.
2.2 The cell is not barred.
2.3 The cell is not part of the list of "forbidden LAs for roaming".
2.4 The cell selection criteria are fulfilled.
3. When camped normally, the UE shall execute the cell reselection evaluation process on the following
occasions/triggers:
3.1 UE internal triggers, so as to meet performance as specified in TS 25.133 for FDD mode and in TS 25.123
for TDD mode.
3.2 When information on the BCCH used for the cell reselection evaluation procedure has been modified.
4. Cell Reselection Criteria:
4.1 The UE shall perform ranking of all cells that fulfil the S criterion.
4.2 The cells shall be ranked according to the R criteria, deriving Qmeas,n and Qmeas,s and calculating the R
values using CPICH RSCP, P-CCPCH RSCP and the averaged received signal level as specified in TS
Release 5 54 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 54
25.133 and TS 25.123 for FDD, TDD and GSM cells, respectively.

The offset Qoffset1
s,n
is used for Qoffset
s,n
to calculate R
n
, the hysteresis Qhyst1
s
is used for Qhyst
s
to
calculate R
s
.

If the usage of HCS is indicated in system information, TEMP_OFFSET1
n
is used for TEMP_OFFSET
n
to
calculate TO
n
. If it is indicated in system information that HCS is not used, TEMP_OFFSET
n
is not applied
when calculating R
n
. The best ranked cell is the cell with the highest R value.
If a TDD cell is ranked as the best cell, the UE shall perform cell re-selection to that TDD cell.
If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to
CPICH RSCP, the UE shall perform cell re-selection to that FDD cell.
4.3 In all cases, the UE shall reselect the new cell, only if the the following conditions are met:
- the new cell is better ranked than the serving cell during a time interval Treselection.
- more than 1 second has elapsed since the UE camped on the current serving cell.
5. When cell status "barred" is indicated, the UE shall select another cell according to the following rule:
5.1 If the "Intra-frequency cell re-selection indicator" IE in Cell Access Restriction IE is set to value "allowed",
the UE may select another cell on the same frequency if selection/re-selection criteria are fulfilled.
- If the UE is camping on another cell, the UE shall exclude the barred cell from the neighbouring cell list
until the expiry of a time interval T
barred
. The time interval T
barred
is sent via system information in a barred
cell together with Cell status information in the Cell Access Restriction IE.
- If the UE does not select another cell, and the barred cell remains to be the "best" one, the UE shall after
expiry of the time interval T
barred
again check whether the status of the barred cell has changed.
5.2 If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall not re-select a cell
on the same frequency as the barred cell. For emergency call, the Intra-frequency cell re-selection indicator
IE" shall be ignored, i.e. even if it is set to "not allowed" the UE may select another intra-frequency cell.
References
1. TS 25.304, clause 5.2.1.
2. TS 25.304, clause 4.3.
3. TS 25.304, clause 5.2.5.1.
4. TS 25.304, clause 5.2.6.1.4.
5. TS 25.304, clause 5.3.1.1.
1. To verify that the UE performs cell reselection on the following occasions:
1.1 Serving cell becomes barred;
1.2 S<0 for serving cell.
2. To verify conformance requirement 5.
NOTE: Reselection triggered by the cell becoming a part of a forbidden registration area is tested in clause
9.4.2.3 and clause 9.4.2.4.
Release 5 55 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 55
Initial conditions
Treselection, Qhyst, Qoffset, TEMP_OFFSET and PENALTY_TIME are not used, so the cell-ranking criterion R
equals CPICH_RSCP for FDD cells, and P-CCPCH RSCP for TDD cells.
Step a-c (FDD):
Test Channel 1 1 2
CPICH_Ec
dBm/3.84
MHz
-60 -70 -80
Qrxlevmin dBm -115 -115 -115
Srxlev* dBm 55 45 35
CellBarred Not barred Not barred Not barred

Step a-c (TDD):
P-CCPCH RSCP dBm -69 -74 -79
Srxlev* dB 34 29 24

Step d-f:
CellBarred
Not barred ->
Barred
Not barred
Not barred
Intra-frequency
cell re-selection
indicator
Not allowed

Tbarred 10s

Step g-h:
Intra-frequency
cell re-selection
indicator

Not Allowed -
>Allowed

Step i-k:
CellBarred
Barred ->
Not barred
Not barred Not barred

Step l-m (FDD):
Qrxlevmin dBm -115 ->-51 -115 -115
Srxlev* dBm 55 ->-9 45 35

Step l-m (TDD):
Qrxlevmin -103 ->-59 -103 -103
Srxlev* 34 ->-10 29 24

Test procedure
Method B is applied.
Release 5 56 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 56
a) The SS activates Cell 2 and 4 and monitors them for random access requests from the UE.
d) The SS sets Cell 1 to be barred. The SS notifies UE of the BCCH modification.
f) The SS sets "Intra-frequency cell re-selection indicator" to "Allowed". The SS notifies UE of the BCCH
modification.
h) The UE is switched off.
i) The SS sets Cell 1 to be not barred.
j) The UE is switched on.
k) The SS waits for random access requests from the UE.
l) For FDD cell, Qrxlevmin is increased to -51 dBm, so S will become negative.
For TDD cell, Qrxlevmin is increased to -59 dBm, so S will become negative.
The SS notifies UE of the BCCH modification
6.1.2.1.5 Test requirements
1) In step c), after the UE has responded on Cell 1, it shall not respond on any other cell within 1 min.
2) In step e), the UE shall respond on Cell 4.
3) In step g), the UE shall respond on Cell 2.
4) In step k), after the UE has responded on Cell 1, it shall not respond on any other cell within 1 min.
5) In step m), the UE shall respond on Cell 2.
6.1.2.2 Cell reselection using Qhyst, Qoffset and Treselection
Test to verify that the UE performs the cell reselection correctly if system information parameters Qoffset, Qhyst and
Treselection are applied for non-hierarchical cell structures. TEMP_OFFSET and PENALTY_TIME are only
applicable when HCS is applied and are tested in clauses 6.1.2.4 and 6.1.2.5.
occasions/triggers:
for TDD mode.
Release 5 57 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 57

The offset Qoffset1
s,n
is used for Qoffset
s,n
to calculate R
n
s
is used for Qhyst
s
to
calculate R
s
.

n
n
to
calculate TO
n
n
is not applied
when calculating R
n
References
1. TS 25.304, clause 5.2.5.1.
2. TS 25.304, clause 5.2.6.1.4.
1. To verify that the UE calculates R from Qhyst and Qoffset and that the modification of these parameters on the
BCCH triggers the cell reselection evaluation process. TEMP_OFFSET and PENALTY_TIME are not applied.
2. To verify that the UE reselects the new cell, if the cell reselection criteria are fulfilled during a time interval
Treselection.
Initial conditions
For FDD only:
Step a-c:
Parameter Unit Cell 1 Cell 2
Test channel 1 1
CPICH_Ec
dBm/3.84
MHz
-60 -70
Qhyst1s dB 20 0
Rs* dB -40 -70
Rn* dB -70 -60

Step d-e:
CPICH_Ec
dBm/3.84
MHz
-60 ->-70 -70 ->-60
Rs* dB -40 ->-50 -70 ->-60
Rn* dB -70 ->-60 -60 ->-70

Step f-g:
Qhyst1s dB 20 ->0 0
Rs* dB -50 ->-70 -60
Rn* dB -60 -70
Release 5 58 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 58
Step h-j:
CPICH_Ec
dBm/3.84
MHz
-70 ->-60 -60 ->-70
Qoffset1s,n dBm 0 ->20 0
Rs* dBm -70 ->-60 -60 ->-70
Rn* dBm -60 ->-90 -70 ->-60
Step k-l:
CPICH_Ec
dBm/3.84
MHz
-60 ->-70 -70 ->-60
Rs* dB -60 ->-70 -70 ->-60
Rn* dB -90 ->-80 -60 ->-70
Step m-n:
Qoffset1s,n dB 20 ->0 0
Rs* dB -70 -60
Rn* dB -80 ->-60 -70
Step o-p:
Treselections s 30 0

For TDD only:
Step a-c:
P-CCPCH RSCP dBm -69 -79
Qhyst1s dB 10 0
Rs* dB -59 -79
Rn* dB -79 -69
Step d-e:
P-CCPCH RSCP dBm -69 ->-79 -79 ->-69
Rs* dB -59 ->-69 -79 ->-69
Rn* dB -79 ->-69 -69 ->-79
Step f-g:
Qhyst1s dB 10 ->0 0
Rs* dB -69 ->-79 -69
Rn* dB -69 -79
Step h-j:
P-CCPCH RSCP dBm -79 ->-69 -69 ->-79
Rs* dB - 79 ->-69 -69 ->-79
Rn* dB - 69 ->-79 -79 ->-69
Step k-l:
P-CCPCH RSCP dBm -69 ->-79 -79 ->-69
Rs* dB -69 ->-79 -79 ->-69
Rn* dB -79 ->-89 -69 ->-79
Step m-n:
Rs* dB -79 -69
Rn* dB -89 ->-79 -79
Step o-p:
Treselections s 0 ->30 0

Release 5 59 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 59
Test procedure
c) The SS waits to see if there is any random access requests from the UE.
d) The SS changes the level of Cell 1 and 2 and waits for 10 s (TS 25.133, A.4.2.1.2 for FDD mode and TS 25.123,
A.4.2.1.2 for TDD mode).
f) The SS resets Qhyst for Cell 1 and notifies UE of the BCCH modification.
h) The UE is switched off. The SS changes the level of Cell 1 and Cell 2. The SS changes Qoffset in Cell 1.
i) The UE is switched on.
j) The SS waits to see if there is any random access requests from the UE.
k) The SS changes the level of Cell 1 and 2 and waits for 10 s (TS 25.133, clause A.4.2.1.2 for FDD mode and TS
25.123, clause A.4.2.1.2 for TDD mode).
l) The SS waits for random access requests from the UE.
m) The SS resets Qoffset for Cell 1, and notifies UE of the BCCH modification.
n) The SS waits for random access requests from the UE.
o) Step h-n) is repeated except that Treselection is 30 s
2) In step e), the UE shall keep responding on Cell 1.
4) In step j), the UE shall select a cell to camp on and eventually make a reselection to Cell 1.
5) In step l), the UE shall keep responding on Cell 1.
6) In step n), the UE shall respond on Cell 2.
7) In step o), the UE shall respond as in previous steps except that when reselecting to Cell 2, there shall be no
response from the UE on Cell 2 within 28 s of notifying UE on the BCCH modification, but the UE shall
respond on Cell 2 within 35 s.
NOTE: Minimum time set by Treselection 2 s tolerance. Maximum time set by Treselection +1 280 msec. for
DRX cycle +1280 ms for system information block type scheduling +2 s tolerance.
6.1.2.3 HCS Cell reselection
Test to verify that the UE performs the cell reselection correctly for hierarchical cell structures. This shall be done
according to the HCS priority, the received signal quality value Q and the quality level threshold criterion H.
Release 5 60 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 60
occasions/triggers:
for TDD mode.
2. Cell Reselection Criteria for hierarchical cells:
2.1 The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised
ranking according to hierarchical cell re-selection rules shall apply, and is calculated from the Q, Qhcs,
TEMP_OFFSET and PENALTY_TIME parameters.
2.2 The UE shall perform ranking of all cells that fulfil the S criterion among all cells that have the highest
HCS_PRIO among those cells that fulfil the criterion H >=0.
2.3 The cells shall be ranked according to the R criteria. The best ranked cell is the cell with the highest R value.
If an FDD cell is ranked as the best cell, the UE shall perform cell re-selection to that FDD cell. If a TDD cell
is ranked as the best cell, the UE shall perform cell re-selection to that TDD cell.
2.4 In all cases, the UE shall reselect the new cell, only if the cell reselection criteria are fulfilled during a time
interval Treselection.
2.5 The cell-ranking criterion R is derived from Q, Qhyst, Qoffset, TEMP_OFFSET, PENALTY_TIME.
References
1. TS 25.304, clause 5.2.2.
2. TS 25.304, clause 5.2.6.1.4.
1. Verify that the UE ignores cells with H<0 for reselection and that H is calculated from Qhcs. The modification
of this parameter on the BCCH shall trigger the cell reselection evaluation process.
2. Verify that the UE ranks cells based on both HCS priority and R. Qhyst, Qoffset, TEMP_OFFSET,
PENALTY_TIME and Treselection are not applied so R equals CPICH_RSCP for FDD cells, and P-CCPCH
RSCP for TDD cells.
Initial conditions
SS shall indicate in System Information that HCS is in use.
Each cell shall include the other cells as neighbouring cells in System Information Block Type 11.
Release 5 61 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 61
For FDD only:
Step a-c:
CPICH_Ec
dBm/3.84
MHz
-70 -65 -70
HCS priority 6 7 7
Qhcss dBm -80 -50 -50
Qhcsn=1 dBm n/a -80 -80
Qhcsn=2 dBm -50 n/a -50
Qhcsn=3 dBm -50 -50 n/a
Hs* dB 10 -15 -20
Hn=1* dB n/a 10 10
Hn=2* dB -15 n/a -15
Hn=3* dB -20 -20 n/a

Step d-e:
Qhcss dBm -80 -50 -50 ->-80
Qhcsn=3 dBm -50 ->-80 -50 ->-80 n/a
Hs* dB 10 -15 -20 ->10
Hn=3* dB -20 ->10 -20 ->10 n/a

Step f-g:
Qhcss dBm -80 -50 ->-80 -80
Qhcsn=2 dBm -50 ->-80 n/a -50 ->-80
Hs* dB 10 -15 ->15 10
Hn=2* dB -15 ->15 n/a -15 ->15

For TDD only:
Step a-c:
HCS priority 6 7 7
Qhcss dBm -89 -59 -59
Hs* dB 20 -15 -20
Hn=1* dB n/a 20 20
Hn=2* dB -15 n/a -15
Hn=3* dB -20 -20 n/a

Step d-e:
Qhcss dBm -89 -59 -59 ->-89
Qhcsn=3 dBm -59 ->-89 -59 ->-89 n/a
Hs* dB 20 -15 -20 ->10
Hn=3* dB -20 ->10 -20 ->10 n/a

Step f-g:
Qhcss dBm -89 -59 ->-89 -89
Qhcsn=2 dBm -59 ->-89 n/a -59 ->-89
Hs* dB 20 -15 ->15 10
Hn=2* dB -15 ->15 n/a -15 ->15

Release 5 62 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 62
Test procedure
a) The SS activates the cells 1-3 and monitors them for random access requests from the UE.
d) The SS changes Qhcs for Cell 3, and notifies UE of the BCCH modification.
f) The SS changes Qhcs for Cell 2, and notifies UE of the BCCH modification.
6.1.2.4 HCS Cell reselection using reselection timing parameters for the H criterion
Test to verify that the UE performs the cell reselection correctly for hierarchical cell structures using TEMP_OFFSET
and PENALTY_TIME applied to the H criterion.
occasions/triggers:
for TDD mode.
2.2 The UE shall perform ranking of all cells that fulfil the S criterion among all cells that have the highest
HCS_PRIO among those cells that fulfil the criterion H >=0.
If an FDD cell is ranked as the best cell, the UE shall perform cell re-selection to that FDD cell. If a TDD cell
2.5 The cell-ranking criterion R is derived from Q, Qhyst, Qoffset, TEMP_OFFSET and PENALTY_TIME.
3. TEMP_OFFSET
n
applies an offset to the H criteria for the duration of PENALTY_TIME
n
after the timer T
n
has
started for that cell. T
n
shall be started from zero when Q
meas,n
>Qhcs
n
. TEMP_OFFSET is only applied to the H
criteria if the cells have different HCS priorities.
Release 5 63 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 63
4 At cell reselection, a timer T
n
is stopped only if the corresponding cell is not a neighbour cell of the new serving
cell, or if the criteria given above for starting timer T
n
for the corresponding cell is no longer fulfilled with the
parameters of the new serving cell. On cell reselection, timer T
n
shall be continued to be run for the
corresponding cells but the criteria given above shall be evaluated with parameters broadcast in the new serving
cell if the corresponding cells are neighbours of the new serving cell.
References
1. TS 25.304, clause 5.2.2.
2,3,4. TS 25.304, clause 5.2.6.1.4.
1. Verify that TEMP_OFFSET is applied to the H criterion for a period of PENALTY_TIME and that the timer is
started when Q
meas,n
>Qhcs
n
if serving and neighbour cell have different HCS priorities.
Initial conditions
For FDD only:
Step a-c:
CPICH_Ec
dBm/3.84
MHz
-60 -70 -70
HCS priority 2 4 7
Qhcss dBm -80 -50 -50
TEMP_OFFSET1n=1 dB n/a n/a n/a
TEMP_OFFSET1n=2 dB inf n/a n/a
TEMP_OFFSET1n=3 dB inf inf n/a
Hs* dB 20 -20 -20
Hn=1* dB n/a 20 20
Hn=2* dBm -20 n/a -20
Hn=3* dBm -20 -20 n/a
PENALTY_TIMEn=1 sec n/a 0 0
PENALTY_TIMEn=2 sec 40 n/a 0
PENALTY_TIMEn=3 sec 60 60 n/a

Step d-e:
Qhcss dBm -80 -50 ->-80 -50 ->-80
Qhcsn=2 dBm -50 ->-80 n/a -50 ->-80
Qhcsn=3 dBm -50 ->-80 -50 ->-80 n/a
Hs* dB 20 -20 ->10 -20 ->10
Hn=2* dB
-inf ->10
(after 40 sec)
n/a -20 ->10
Hn=3* dB
-inf ->10
(after 60 sec)
-inf ->10
(after 60 sec)
n/a

Release 5 64 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 64
For TDD only:
Step a-c:
HCS priority 2 4 7
Qhcss dBm -89 -54 -54
Hs* dB 20 -20 -20
Hn=1* dB n/a 20 20
Hn=2* dB -20 n/a -20
Hn=3* dB -20 -20 n/a

Step d-e:
Qhcss dBm -89 -54 ->-94 -54 ->-94
Qhcsn=2 dBm -54 ->-94 n/a -54 ->-94
Qhcsn=3 dBm -54 ->-94 -54 ->-94 n/a
Hs* dB 20 -20 ->10 -20 ->10
Hn=2* dB
-inf ->10
(after 40 sec)
n/a -20 ->10
Hn=3* dB
-inf ->10
(after 60 sec)
-inf ->10
(after 60 sec)
n/a

Test procedure
d) The SS changes Qhcs for Cell 2 and 3, and notifies UE of the BCCH modification.
2) In step e), there shall be no response from the UE on Cell 2 within 38 s after changing the parameters in step d),
but the UE shall respond on Cell 2 within 49 s. There shall be no response from the UE on Cell 3 within 58 s
after changing the parameters in step d), but the UE shall respond on Cell 3 within 69 s.
NOTE: Minimum time set by PENALTY_TIME (cell 2) - 2 s tolerance. Maximum time set by PENALTY_TIME
(cell 2) +1 280 msec. for DRX cycle +2 s tolerance +5 s tolerance (for UE to read System Information).
Same calculation for Cell 3.
Release 5 65 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 65
6.1.2.5 HCS Cell reselection using reselection timing parameters for the R criterion
Test to verify that the UE performs the cell reselection correctly for hierarchical cell structures using TEMP_OFFSET
and PENALTY_TIME applied to the R criterion.
occasions/triggers:
for TDD mode.
2.2 The UE shall perform ranking of all cells that fulfil the S criterion among all cells, not considering HCS
priority levels, if no cell fulfil the criterion H>=0.
If a FDD cell is ranked as the best cell, the UE shall perform cell re-selection to that FDD cell. If a TDD cell
2.5 The cell-ranking criterion R is derived from Q, Qhyst, Qoffset, TEMP_OFFSET, PENALTY_TIME.
3. TEMP_OFFSET
n
applies an offset to the R criteria for the duration of PENALTY_TIME
n
after the timer T
n
has
started for that cell. T
n
shall be started from zero when Q
meas,n
>Q
meas,s
+Qoffset2
s,n
. TEMP_OFFSET is only
applied to the R criteria if the cells have identical priorities.
4. At cell-reselection, a timer T
n
is stopped only if the corresponding cell is not a neighbour cell of the new serving
cell, or if the criteria given above for starting timer T
n
for the corresponding cell is no longer fulfilled with the
parameters of the new serving cell. On cell re-selection, timer T
n
shall be continued to be run for the
corresponding cells but the criteria given above shall be evaluated with parameters broadcast in the new serving
cell if the corresponding cells are neighbours of the new serving cell.
References
1. TS 25.304, clause 5.2.2.
2,3,4. TS 25.304, clause 5.2.6.1.4.
1. Verify that TEMP_OFFSET is applied to the R criterion for a period of PENALTY_TIME if serving and
neighbour cell have identical HCS priorities and that the timer is started when Q
meas,n
>Q
meas,s
+Qoffset1
s,n
.
Initial conditions
Release 5 66 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 66
For FDD only:
Step a-c:
CPICH_Ec
dBm/3.84
MHz
-60 -70 -70
HCS priority 1 1 1
Qhcss dBm -80 -80 -80
TEMP_OFFSET1n=2 dBm inf n/a n/a
TEMP_OFFSET1n=3 dBm inf inf n/a
Hs* dBm 20 10 10
Hn=1* dB n/a 20 20
Hn=2* dBm 10 n/a 10
Hn=3* dBm 10 10 n/a
Rs* dBm -60 -70 -70
Rn=1* dBm n/a -60 -60
Rn=2* dBm -70 n/a -70
Rn=3* dBm -70 -70 n/a

Step d-e:
CPICH_Ec
dBm/3.84
MHz
-60 ->-70 -70 ->-65 -70 ->-60
Rs* dBm -60 ->-70 -70 ->-65 -70 ->-60
Rn=1* dBm n/a -60 ->-70 -60 ->-70
Rn=2* dBm
-inf ->-65
(after 40 sec)
n/a -70 ->-65
Rn=3* dBm
-inf ->-60
(after 60 sec)
-inf ->-60
(after 60 sec)
n/a

For TDD only:
Step a-c:
HCS priority 1 1 1
Qhcss dBm -89 -89 -89
Hs* dB 20 10 10
Hn=1* dB n/a 20 20
Hn=2* dB 10 n/a 10
Hn=3* dB 10 10 n/a
Rs* dBm -69 -79 -79
Rn=1* dBm n/a -69 -69
Rn=2* dBm -79 n/a -79
Rn=3* dBm -79 -79 n/a

Step d-e:
Release 5 67 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 67
P-CCPCH RSCP dBm -69 ->-79 -79 ->-74 -79 ->-69
Rs* dBm -69 ->-79 -79 ->-74 -79 ->-69
Rn=1* dBm n/a -69 ->-79 -69 ->-79
Rn=2* dBm
-inf ->-74
(after 40 sec)
n/a -79 ->-74
Rn=3* dBm
-inf ->-69
(after 60 sec)
-inf ->-69
(after 60 sec)
n/a

Test procedure
d) The SS changes the level of Cell 1-3, and notifies UE of the BCCH modification.
2) In step e), there shall be no response from the UE on Cell 2 within 38 s after changing the parameters in step d),
but the UE shall respond on Cell 2 within 55 s. There shall be no response from the UE on Cell 3 within 58 s
after changing the parameters in step d), but the UE shall respond on Cell 3 within 75 s.
NOTE: Minimum time set by PENALTY_TIME (cell 2) 2 s tolerance. Maximum time set by
PENALTY_TIME (cell 2) +6.4 s (T
evaluateFDD
from TS 25.133, table 4.1 for FDD mode and T
evaluateTDD

from TS 25.123, table 4.1 for TDD mode) +1 280 msec +5 s tolerance (for UE to read System
Information). for system info scheduling +2 s tolerance. Same calculation for Cell 3.
6.1.2.6 Emergency calls
Test to verify that the UE shall be able to initiate emergency calls when no suitable cells of the selected PLMN are
available, but at least one acceptable cell is available.
1. Acceptable cell:
An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls).
Such a cell shall fulfil the following requirements, which is the minimum set of requirements to initiate an
emergency call in a UTRAN network:
1.1 The cell is not barred;
2.1 The cell is part of the selected PLMN or, of a PLMN considered as equivalent by the UE according to the
Release 5 68 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 68
3. If the UE is unable to find any suitable cell of selected PLMN the UE shall enter the Any cell selection state.
4. Any Cell Selection State: In this state, the UE shall attempt to find an acceptable cell of an any PLMN to camp
on, trying all RATs that are supported by the UE and searching first for a high quality cell. The UE, which is not
camped on any cell, shall stay in this state until an acceptable cell is found.
5. Camped on Any Cell State: In this state the UE obtains limited service. The UE shall regularly attempt to find a
suitable cell of the selected PLMN, trying RATs that are supported by the UE. If a suitable cell is found, this
causes an exit to the Camped normally State.
6. In the Camped on Any Cell State, the UE shall perform the cell reselection evaluation process on the following
occasions/triggers:
6.1 UE internal triggers, so as to meet performance as specified in TS 25.133 for FDD mode and TS 25.123 for
TDD mode.
References
1. TS 25.304, clause 4.3.
2. TS 25.304, clause 4.3.
3. TS 25.304, clause 5.2.2.1.
4. TS 25.304, clause 5.2.8.
5. TS 25.304, clause 5.2.2.5.
6. TS 25.304, clause 5.2.9.1.
1. To verify that the UE shall be able to initiate emergency calls when no suitable cells of the selected PLMN are
available, but at least one acceptable cell is available.
2. To verify that the UE selects a cell with S>0 and CellBarred =Not Barred (i.e. an "acceptable cell") when no
suitable cells of the selected PLMN are available.
3. To verify that the UE ranks the acceptable cells according to the cell-ranking criterion R which in this test case
equals Q as Qhyst, Qoffset, TEMP_OFFSET and PENALTY_TIME parameters are not used. Treselection is not
used either.
Initial conditions
In step a-d, Cell 1 and 2 are neither suitable nor acceptable cells. Cell 3 is an acceptable cell but not suitable.
In step e-f, both Cell 1 and 3 are acceptable cells.
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2
EFFPLMN PLMN 3

All cells in this test case belong to PLMN 3.
Release 5 69 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 69
Step a-d:
For FDD only:
Test Channel 1 1 1
CPICH_Ec
dBm/3.84
MHz
-65 -60 -70
Srxlev* dB 16 -9 11
CellBarred Barred Not barred Not barred
Intra-frequency cell
re-selection indicator
Allowed
Tbarred 10s

For TDD only:
Test Channel 1 1 1
CellBarred Barred Not barred Not barred
Intra-frequency cell re-
selection indicator
Allowed
Tbarred 10s

Step e-f:
CellBarred
Barred ->Not
barred
0 0

Test procedure
a) The SS activates the cells and monitors them for random access requests from the UE.
c) 50 s after switch on, an emergency call is initiated on the UE.
d) The SS waits for random access request from the UE.
e) The SS changes the CellBarred of Cell 1 to 'Not barred'.
f) After 30 s an emergency call is initiated on the UE.
g) The SS waits for random access request from the UE.
1) In step d), the first access from the UE shall be on Cell 3.
2) In step g), the first access from the UE shall be on Cell 1.
6.1.2.7 Emergency calls; Intra-frequency cell "Not allowed"
Test to verify that for emergency call and cell status "barred", the Intra-frequency cell re-selection indicator IE is
ignored, i.e. even if it is set to "not allowed" the UE may select another intra-frequency cell.
Release 5 70 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 70
1. When cell status "barred" is indicated:
- The UE is not permitted to select/re-select this cell, not even for emergency calls.
- The UE shall select another cell according to the following rule:
- If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall not re-select a
cell on the same frequency as the barred cell. For emergency call, the Intra-frequency cell re-selection
indicator IE" shall be ignored, i.e. even if it is set to "not allowed" the UE may select another intra-
frequency cell.
References
1. TS 25.304, clause 5.3.1.1.
To verify that for an emergency call and cell status "barred", the IE Intra-frequency cell re-selection indicator is
ignored, i.e. even if this IE is set to "not allowed" the UE may select another intra-frequency cell for the emergency call.
Initial conditions
Step a-c:
For FDD only:
Test Channel 1 1
CPICH_Ec
dBm/3.84
MHz
-60 -70
CellBarred Not barred Not barred

For TDD only:
P-CCPCH RSCP dBm -69 -79
CellBarred Not barred Not barred

Step d-i:
CellBarred
Not barred ->
Barred
Not barred
Intra-frequency cell re-
selection indicator
Not allowed
Tbarred 10s

Test procedure
a) The SS activates the cells and monitors them for any random access requests from the UE.
c) The SS waits for random access request from the UE.
d) The SS sets Cell 1 to be barred, and notifies UE of the BCCH modification.
Release 5 71 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 71
e) The SS waits to see if there is any random access request from the UE.
f) By MMI, an attempt to originate a call is made.
g) The SS waits to see if there is any random access request from the UE.
h) By MMI, an emergency call is initiated on the UE.
i) The SS waits for random access request from the UE.
2) In step e), there shall be no response from the UE within 2 min.
3) In step g), there shall be no response from the UE within 2 min. It shall not be possible to originate the call.
4) In step i), the UE shall respond on Cell 2. It shall be possible to originate the emergency call.
6.1.2.8 Cell reselection: Equivalent PLMN
Test to verify that the UE performs the cell reselection correctly to a cell belonging to a PLMN Equivalent to the
registered PLMN, if the serving cell of registered PLMN becomes barred or S<0.
2.1 The cell is part of the selected PLMN or of a PLMN considered as equivalent by the UE according to the
information provided by the NAS
2.2 The cell is not barred
2.3 The cell is not part of the list of "forbidden LAs for roaming"
2.4 The cell selection criteria are fulfilled
occasions/triggers:
for TDD mode.
3.2 When information on the BCCH used for the cell reselection evaluation procedure has been modified
4.1 The UE shall perform ranking of all cells that fulfil the S criterion

The offset Qoffset1
s,n
is used for Qoffset
s,n
to calculate R
n
s
is used for Qhyst
s
to
calculate R
s
.

n
n
to
Release 5 72 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 72
calculate TO
n
n
is not applied
when calculating R
n
5. When cell status "barred" is indicated, the UE shall select another cell according to the following rule:
5.1 If the "Intra-frequency cell re-selection indicator" IE in Cell Access Restriction IE is set to value "allowed",
the UE may select another cell on the same frequency if selection/re-selection criteria are fulfilled.
- If the UE is camping on another cell, the UE shall exclude the barred cell from the neighbouring cell list
until the expiry of a time interval T
barred
barred
is sent via system information in a barred
cell together with Cell status information in the Cell Access Restriction IE.
- If the UE does not select another cell, and the barred cell remains to be the "best" one, the UE shall after
expiry of the time interval T
barred
5.2 If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall not re-select a cell
on the same frequency as the barred cell. For emergency call, the Intra-frequency cell re-selection indicator
IE" shall be ignored, i.e. even if it is set to "not allowed" the UE may select another intra-frequency cell.
References
1. TS 25.304, 5.2.1
2. TS 25.304, 4.3
3. TS 25.304, 5.2.5.1
4. TS 25.304, 5.2.6.1.4
5. TS 25.304, 5.3.1.1
1. To confirm that the UE treats the cell of the equivalent PLMN as a cell of the current PLMN.
2. To verify that the UE performs cell reselection on the following occasions:
2.1 Serving cell becomes barred.
3. To verify conformance requirement 5.
NOTE: Reselection triggered by the cell becoming a part of a forbidden registration area is tested in clause
9.4.2.3 "Location updating / rejected / location area not allowed" and 9.4.2.4 "Location updating / rejected
/ roaming not allowed in this LA".
Initial conditions
Treselection, Qhyst, Qoffset, TEMP_OFFSET and PENALTY_TIME are not used, so the cell-ranking criterion R
equals CPICH_RSCP for FDD cells, and P-CCPCH RSCP for TDD cells.
Release 5 73 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 73
The UE is Idle Updated on PLMN1 in cell 1, and The SS includes PLMN 2 and PLMN 3 under IE 'Equivalent PLMN'
during Idle Update Procedure.
Cell 1 indicates in System Information Block Type 11 that Cell 2 and Cell 4 are neighbouring cells.
Step a-c (FDD):

Test Channel 1 1 2
PLMN PLMN 1 PLMN 2 PLMN 3
CPICH_Ec
dBm/
3.84
MHz
-60 -70 -80
Srxlev* dB 55 45 35
CellBarred Not barred Not barred Not barred

Step a-c (TDD):
Test Channel 1 1 2
PLMN PLMN 1 PLMN 2 PLMN 3
Srxlev* dB 34 29 24

Step d-f:
CellBarred
Not barred-
>Barred

Intra-frequency
cell re-selection
indicator
Not Allowed

Tbarred s 10

Step g-h:
Intra-frequency
cell re-selection
indicator

Not Allowed
->Allowed

Step i-k:
Release 5 74 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 74
CellBarred
Barred ->
Not barred
Not barred Not barred

Step l-m (FDD):
Qrxlevmin dBm -115 ->-51 -115 -115
Srxlev* dBm 55 ->-9 45 35

Step l-m (TDD):
Qrxlevmin dBm -103 ->-59 -103 -103
Srxlev* dBm 34 ->-10 29 24

Test procedure
c) The SS waits for random access requests from the UE. A complete Location Update is done. SS specifies PLMN
2 and 3 are Equivalent to PLMN 1 in Location Update Accept Message.
d) The SS sets Cell 1 to be barred. The SS notifies UE of the BCCH modification.
e) The SS waits for random access requests from the UE. A complete Location Update is done. SS specifies PLMN
f) The SS sets "Intra-frequency cell re-selection indicator" to "Allowed".
g) The SS waits for random access requests from the UE. A complete Location Update is done.
i) The SS activates Cell 1, 2 and 4 and monitors them for random access requests from the UE.
j) The UE is switched on.
k) The SS waits for random access requests from the UE. A complete Location Update is done. SS specifies PLMN
l) For FDD cell, Qrxlevmin is increased to -51 dBm, so S will become negative.
For TDD cell, Qrxlevmin is increased to -59 dBm, so S will become negative.
The SS notifies UE of the BCCH modification
4) In step k), after the UE has responded on Cell 1, it shall not respond on any other cell within 1 min.
5) In step m), the UE shall respond on Cell 2.
Release 5 75 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 75
6.1.2.9 Cell reselection using cell status and cell reservations
Test to verify that the UE correctly interprets cell status and cell reservations when performing cell reselection.
1. When cell status is indicated as "not barred", "not reserved" for operator use and "not reserved" for future
extension (Cell Reservation Extension),
- the UE may select/re-select this cell during the cell selection and cell re-selection procedures in Idle mode
and in Connected mode.
2. When cell status is indicated as "not barred", "not reserved" for operator use and "reserved" for future extension
(Cell Reservation Extension),
- UEs shall behave as if cell status "barred" is indicated using the value "not allowed" in the IE "Intra-
frequency cell re-selection indicator" and the maximum value for T
barred
, see [8] (see also below).
3. When cell status is indicated as "not barred" and "reserved" for operator use,
- UEs assigned to Access Class 11 or 15 may select/re-select this cell if in the home PLMN.
- UEs assigned to an Access Class in the range 0 to 9 and 12 to 14 shall behave as if cell status "barred" is
indicated using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator" and the
maximum value for T
barred
, see [8] (see also below).
4. When cell status "barred" is indicated,
- The UE is not permitted to select/re-select this cell, not even for emergency calls.
- The UE shall ignore the "Cell Reserved for future extension (Cell Reservation Extension) use" IE.
- The UE shall select another cell according to the following rule:
- If the "Intra-frequency cell re-selection indicator" IE in Cell Access Restriction IE is set to value
"allowed", the UE may select another cell on the same frequency if selection/re-selection criteria are
fulfilled.
- If the UE is camping on another cell, the UE shall exclude the barred cell from the neighbouring cell
list until the expiry of a time interval T
barred
barred
is sent via system information in a
barred cell together with Cell status information in the Cell Access Restriction IE.
- If the UE does not select another cell, and the barred cell remains to be the "best" one, the UE shall
after expiry of the time interval T
barred
- If the "Intra-frequency cell re-selection indicator" IE is set to "not allowed" the UE shall not re-select a
cell on the same frequency as the barred cell. For emergency call, the Intra-frequency cell re-selection
indicator IE" shall be ignored, i.e. even if it is set to "not allowed" the UE may select another intra-
frequency cell.
- If the barred cell remains to be the "best" one, the UE shall after expiry of the time interval T
barred

The reselection to another cell may also include a change of RAT.
Reference(s)
3GPP TS 25.304, clause 5.3.1.1
1. To verify that when cell status is indicated as "not barred", "not reserved" for operator use and "reserved" for
future extension (Cell Reservation Extension),
Release 5 76 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 76
- UEs behave as if cell status "barred" is indicated using the value "not allowed" in the IE "Intra-frequency cell
re-selection indicator" and the maximum value for T
barred
.
2. To verify that when cell status is indicated as "not barred" and "reserved" for operator use,
- UEs assigned to Access Class 11 or 15 may select/re-select this cell if in the home PLMN.
- UEs assigned to an Access Class in the range 0 to 9 and 12 to 14 shall behave as if cell status "barred" is
indicated using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator" and the
maximum value for T
barred
.
Initial conditions
Test procedure 1: Use of USIM with "Type A" EF
ACC
as defined in TS 34.108.
Step a-c (FDD):
Test Channel 1 1 2
CPICH_Ec dBm/3.84 MHz -58 -68 -78
Srxlev* dB 25 15 5
Cell Reserved for
operator use
not reserved not reserved not reserved
Cell Reservation
Extension

Step a-c (TDD):
Srxlev* dB 15 10 5

Step d-e:
Cell Reserved for
operator use

not reserved ->
reserved
not reserved not reserved
Cell Reservation
Extension

Step f-g:
Cell Reserved for
operator use

reserved ->
not reserved
Cell Reservation
Extension

Test procedure 2: Use of USIM with "Type B" EF
ACC
as defined in TS 34.108.
Step a-c (FDD):
Release 5 77 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 77
Test Channel 1 1 2
CPICH_Ec dBm/3.84 MHz -58 -68 -78
Srxlev* dB 25 15 5
Cell Reserved for
operator use
Cell Reservation
Extension

Step a-c (TDD):
Srxlev* dB 15 10 5

Step d-e:
Cell Reserved for
operator use
Cell Reservation
Extension

not reserved ->
reserved

Step f-g:
Cell Reserved for
operator use

not reserved ->
reserved
Cell Reservation
Extension
reserved not reserved not reserved

Related ICS/IXIT Statement(s)
None
Test procedure 1
Method B applied.
a) The SS activates Cell 1, 2 and 4, and monitors them for random access requests from the UE.
d) The SS sets Cell 1 to "reserved" for operator use. The SS notifies UE of the BCCH modification.
f) The SS sets Cell 1 to "not reserved" for operator use.
Test procedure 2
Method B applied.
a) The SS activates Cell 1, 2 and 4, and monitors them for random access requests from the UE.
Release 5 78 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 78
d) The SS sets Cell 1 to "reserved" for future extension. The SS notifies UE of the BCCH modification.
f) The SS sets Cell 1 to "reserved" for operator use.
Test procedure 1
1) In step c), the UE shall respond on Cell 1.
3) In step g), the UE shall respond on Cell 1 after 1280 seconds (maximum value for T
barred
) from SS notified UE
of the BCCH modification in Cell 1 in step d).
Test procedure 2
1) In step c), the UE shall respond on Cell 1.
3) In step g), the UE shall respond on Cell 1 after 1280 seconds (maximum value for T
barred
) from SS notified UE of
the BCCH modification in Cell 1 in step d).

6.2 Multi-mode environment (2G/3G case)
6.2.1 PLMN and RAT selection
6.2.1.1 Selection of the correct PLMN and associated RAT
Test to verify that the UE selects the correct combination of PLMN and associated access technology according to the
fields on the USIM.
2. The "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology"
and "Operator Controlled PLMN Selector with Access Technology" data fields in the SIM include associated
access technologies for each PLMN entry. The PLMN/access technology combinations are listed in priority
order. If an entry includes more than one access technology, then no priority is defined for the preferred access
technology and the priority is an implementation issue.
3. To allow provision for multiple HPLMN codes, the HPLMN access technologies are stored on the SIM together
with PLMN codes. This version of the specification does not support multiple HLPMN codes and the "HPLMN
Release 5 79 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 79
Selector with Access Technology" data field is only used by the MS to get the HPLMN access technologies. The
HPLMN code is the PLMN code included in the IMSI.
priority order);
4.3 Each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM (in
priority order);
References
1. TS 23.122, clause 4.4.3.1.
2. TS 23.122, clause 4.4.3
3. TS 23.122, clause 4.4.3
4. TS 23.122, clause 4.4.3.1.1
1. To verify that the UE selects the correct combination of HPLMN/access technology combination according to
the fields on the USIM.
Initial conditions
Cell levels are from tables 6.3 and 6.4.
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
P-CCPCH_RSCP/
RF signal level
[dBm] (TDD)
Test Channel PLMN Radio Access
Technology
Cell 1 -48 -48 1 PLMN 1 GSM
Cell 2 -70 -59 1 PLMN 1 UTRAN

USIM A
USIM field Priority PLMN Access Technology
Identifier
EFLOCI
EFHPLMNwAcT 1
st
PLMN 1 GSM
2
nd
PLMN 1 UTRAN
Release 5 80 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 80

The HPLMN (MCC+MNC) of the IMSI for USIM A is set to PLMN1.
USIM B
Identifier
EFLOCI
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM

The HPLMN (MCC+MNC) of the IMSI for USIM B is set to PLMN2.
Test procedure
a) The SS activates cells 1-4 and monitors the cells for random access requests from the UE. The UE shall have a
USIM with settings according to USIM A.
d) The UE is switched off and a USIM with settings according to USIM B is inserted.
e) The UE is switched on.
f) The SS waits for random access requests from the UE.
1) In step c), the response from the UE shall be on Cell 1. The displayed PLMN shall be PLMN1 (GSM).
2) In step f), the response from the UE shall be on Cell 3. The displayed PLMN shall be PLMN2 (UTRAN).
6.2.1.2 Selection of RAT for HPLMN; Manual mode
Test to verify that the UE selects the HPLMN RAT according to the HPLMN RAT priority list on the USIM. If no RAT
on the list is available, the UE shall try to obtain registration on the same PLMN using other UE-supported RATs.
2. For HPLMN, the MS shall search for all access technologies it is capable of. The MS shall start its search using
the access technologies stored in the "HPLMN Selector with Access Technology" data field on the SIM in
priority order (i.e. the PLMN/access technology combinations are listed in priority order, if an entry includes
more than one access technology then no priority is defined for the preferred access technology and the priority
is an implementation issue).
Release 5 81 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 81
MS.
3.1 HPLMN;
NOTE: It is an MS implementation option whether to indicate access technologies to the user. If the MS does
display access technologies, then the access technology used should be the access technology chosen by
the user for that PLMN. If the MS does not display access technologies, then the access technology
chosen for a particular PLMN should be the highest priority available access technology for that PLMN,
if the associated access technologies have a priority order.
References
1. TS 23.122, clause 4.4.3.
2. TS 23.122, clause 4.4.3.1.1 (f).
3. TS 23.122, clause 4.4.3.1.2.
1. To verify that:
1.1 the UE searches for a HPLMN RAT according to the HPLMN Selector with Access Technology data field on
the USIM in priority order.
1.2 If no RAT on the priority list is available, the UE tries to obtain registration on the same PLMN using other
UE-supported RATs.
Release 5 82 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 82
Initial conditions
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP/
RF signal level
[dBm] (TDD)
Technology

USIM A
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
GSM
USIM B
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd

Test procedure
c) PLMN2 (UTRAN) shall be selected when the PLMN list is presented.
f) PLMN2 (GSM) shall be selected when the PLMN list is presented.
h) The UE is switched off and a USIM with settings according to USIM B is inserted. All cells except Cell 1 are
active.
i) The UE is switched on.
j) PLMN2 (GSM) shall be selected when the PLMN list is presented.
k) The SS waits for random access requests from the UE.
Release 5 83 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 83
1) In step c), the list shall be presented. It shall contain as highest priority PLMN2 (UTRAN as number 1 on the list
and GSM as number 2).
2) In step d), the response from the UE shall be on Cell 1 (1
st
priority RAT for EF
HPLMNwAcT
). The displayed PLMN
shall be PLMN2 (UTRAN).
3) In step f), the list shall be presented. It shall contain as highest priority PLMN2 (GSM).
4) In step g), the response from the UE shall be on Cell 2 (2
nd
priority RAT for EF
HPLMNwAcT
shall be PLMN2 (GSM).
5) In step j), the list shall be presented. It shall contain as highest priority PLMN2 (GSM).
6) In step k), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN2 (GSM). (PLMN2
is not available on UTRAN so registration on the same PLMN is attempted using other UE-supported RATs).
6.2.1.3 Selection of RAT for UPLMN; Manual mode
Test to verify that the UE selects the UPLMN RAT according to the UPLMN RAT priority list on the USIM. If no
PLMN/RAT on the UPLMN RAT priority list is available then the UE shall search for PLMNs in the OPLMN list.
MS.
1.1 HPLMN;
Release 5 84 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 84
References
1. TS 23.122, clause 4.4.3.1.2.
1. To verify that:
1.1 the UE selects the UPLMN RAT according to the UPLMN RAT priority list on the USIM.
1.2 If no RAT on the UPLMN RAT priority list is available, the UE searches for PLMNs in the OPLMN list.
Initial conditions
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP/
RF signal level
[dBm] (TDD)
Technology

Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM
EFPLMNwAcT 1
st
PLMN 3 UTRAN
2
nd
PLMN 4 GSM
EFOPLMNwAcT 1
st
PLMN 5 UTRAN
2
nd
PLMN 6 GSM

Test procedure
e) Cell 1 and Cell 2 are switched off. See note.
h) Cell 4 and Cell 3 are switched off. See note.
Release 5 85 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 85
i) PLMN5 (UTRAN) shall be selected when the PLMN list is presented.
NOTE: When the serving cell (Cell 1 in step e and Cell 4 in step h) is switched off then the UE will trigger the
recovery from lack of coverage scenario (TS 23.122 clause 4.4.3.1). The UE will search for a cell within
the registered PLMN or equivalent PLMN (if it is available) using all access technologies that the UE is
capable of. Thus Cell 2 in step e and Cell 3 in step h need to be switched off.
1) In step c), the list shall be presented. It shall contain in priority PLMN3 (UTRAN), PLMN4 (GSM), other
PLMNs.
st
priority RAT for EF
PLMNwAcT
3) In step f), the list shall be presented. It shall contain in priority PLMN4 (GSM), PLMN5 (UTRAN), other
PLMNs.
nd
priority RAT for EF
PLMNwACT
5) In step i), the list shall be presented. It shall contain as highest priority PLMN5 (UTRAN).
6) In step j), the response from the UE shall be on Cell 5 (1
st
priority RAT for EF
OPLMNwAcT
6.2.1.4 Selection of RAT for OPLMN; Manual mode
Test to verify that the UE selects the OPLMN RAT according to the OPLMN RAT priority list on the USIM. If no
PLMN/RAT on the OPLMN RAT priority list is available then the UE shall search for other PLMN/access technology
combinations with received high quality signal in random order.
MS.
1.1 HPLMN;
1.2 PLMNs contained in the "User Controlled PLMN Selector with Access Technology" data field in the SIM (in
priority order);
Release 5 86 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 86
References
1. TS 23.122, clause 4.4.3.1.2.
1. To verify that:
1.1 the UE selects the OPLMN RAT according to the OPLMN RAT priority list on the USIM.
1.2 If no PLMN/RAT on the OPLMN RAT priority list is available, the UE searches for "other PLMN/access
technology combinations with received high quality signal in random order".
Initial conditions
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP /
RF signal level
[dBm] (TDD)
Technology

USIM field Priority PLMN Access
Technology
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM
EFPLMNwAcT 1
st
PLMN 3 UTRAN
2
nd
PLMN 4 GSM
EFOPLMNwAcT 1
st
PLMN 5 UTRAN
2
nd
PLMN 6 GSM

Test procedure
Release 5 87 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 87
e) Cell 1 and Cell2 are switched off. See note.
h) Cell 4 and Cell 3 are switched off. See note.
i) PLMN7 (UTRAN) shall be selected when the PLMN list is presented.
NOTE: When the serving cell (Cell 1 in step e and Cell 4 in step h) is switched off then the UE will trigger the
capable of. Thus Cell 2 in step e and Cell 3 in step h need to be switched off.
1) In step c), the list shall be presented. It shall contain in priority PLMN5 (UTRAN), PLMN6 (GSM), other
PLMNs.
st
priority RAT for EF
OPLMNwAcT
3) In step f), the list shall be presented. It shall contain as highest priority PLMN6 (GSM) followed by PLMN5
(GSM), PLMN6 (UTRAN) and PLMN7 (UTRAN) in random order.
nd
priority RAT for EF
OPLMNwAcT
5) In step i), the list shall be presented. It shall contain PLMN5 (GSM), PLMN6 (UTRAN) and PLMN7 (UTRAN)
in random order.
6) In step j), the response from the UE shall be on Cell 5. The displayed PLMN shall be PLMN7 (UTRAN).
6.2.1.5 Selection of "Other PLMN / access technology combinations"; Manual mode
Test to verify that if neither RPLMN, HPLMN, UPLMN nor OPLMN is available, the UE tries to obtain registration on
"Other PLMN/access technology combinations with received high quality signal in random order". Forbidden PLMNs
shall also by displayed in the list.
MS.
1.1 HPLMN;
Release 5 88 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 88
2. UTRA case: The UE shall scan all RF channels in the UTRA band according to its capabilities to find available
PLMNs. On each carrier, the UE shall search for the strongest cell according to the cell search procedures (for
FDD, see TS 25.214, and TDD, see TS 25.224) and read its system information, in order to find out which
PLMN the cell belongs to. If the UE can read the PLMN identity, the found PLMN shall be reported to the NAS
as a high quality PLMN (but without the RSCP value), provided that the following high quality criterion is
fulfilled:
- For a TDD cell, the measured P-CCPCH RSCP value shall be greater than or equal to 84 dBm.
PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and
P-CCPCH RSCP for UTRA TDD cells.
3. GSM case: A PLMN shall be understood to be received with high quality signal if the signal level is above
-85 dBm.
References
1. TS 23.122, clause 4.4.3.1.2.
2. TS 25.304, clause 5.1.2.2.
3. TS 03.22, clause 4.4.3.
1. To verify that if neither RPLMN, HPLMN, UPLMN nor OPLMN is available, the UE tries to obtain registration
on "Other PLMN/access technology combinations with received high quality signal in random order".
Release 5 89 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 89
Initial conditions
Cell CPICH_Ec /RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP /
RF signal level
[dBm] (TDD)
High Quality
signal
Test
Channel
PLMN Radio Access
Technology
Cell 1 -80 -74 Yes 1 PLMN 7 UTRAN
Cell 2 -65 -65 Yes 1 PLMN 8 GSM

Technology
Identifier
EFLOCI PLMN 7 UTRAN
EFFPLMN PLMN 8
PLMN 9

Test procedure
c) PLMN7 shall be selected when the PLMN list is presented.
f) PLMN8 shall be selected when the PLMN list is presented. The SS shall accept the Registration Request from
the UE.
h) Cell 2 is switched off.
i) PLMN9 shall be selected when the PLMN list is presented. The SS shall accept the Registration Request from
the UE.
l) PLMN11 shall be selected when the PLMN list is presented.
n) Cell 4 is switched off.
In all steps, the PLMN priority list shall be as follows: PLMN7, PLMN8, PLMN9 and PLMN11 in random order.
1) In step c), the list shall be presented and contain PLMN7, 8, 9, 11.
Release 5 90 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 90
2) In step d), the response from the UE shall be on Cell 1. The displayed PLMN shall be PLMN7.
3) In step f), the list shall be presented and contain PLMN 8, 9, 11.
4) In step g), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN8.
5) In step i), the list shall be presented and contain PLMN9, 11.
6) In step j), the response from the UE shall be on Cell 3. The displayed PLMN shall be PLMN9.
7) In step l), the list shall be presented and contain PLMN11. The displayed PLMN shall be PLMN11.
8) After step n), the UE shall inform that no network is available
6.2.1.6 Selection of RAT for HPLMN; Automatic mode
Test to verify that the UE selects the HPLMN RAT according to the HPLMN RAT priority list on the USIM. If no RAT
on the list is available, the UE shall try to obtain registration on the same PLMN using other UE-supported RATs.
2. The "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology"
and "Operator Controlled PLMN Selector with Access Technology" data fields in the SIM include associated
access technologies for each PLMN entry. The PLMN/access technology combinations are listed in priority
order. If an entry includes more than one access technology, then no priority is defined for the preferred access
technology and the priority is an implementation issue.
priority order);
References
1. TS 23.122, clause 4.4.3.
2. TS 23.122, clause 4.4.3.
Release 5 91 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 91
3. TS 23.122, clause 4.4.3.1.1.
1. To verify that:
1.1 the UE searches for a HPLMN RAT according to the HPLMN Selector with Access Technology data field on
the USIM in priority order.
1.2 If no RAT on the priority list is available, the UE tries to obtain registration on the same PLMN using other
UE-supported RATs.
Initial conditions
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP /
RF signal level
[dBm] (TDD)
Technology

USIM A
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM

The HPLMN (MCC+MNC) of the IMSI for USIM A is set to PLMN2.
USIM B
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd

The HPLMN (MCC+MNC) of the IMSI for USIM B is set to PLMN2.
Test procedure
Release 5 92 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 92
d) The UE is switched off and a USIM with settings according to USIM A is again inserted. All cells except Cell 1
are active.
f) The UE is switched off and a USIM with settings according to USIM B is inserted. All cells except Cell 1 are
active.
g) The UE is switched on.
h) The SS waits for random access requests from the UE.
1) In step c), the response from the UE shall be on Cell 1 (1
st
priority RAT for EF
HPLMNwAcT
2) In step e), the response from the UE shall be on Cell 2 (2
nd
priority RAT for EF
HPLMNwAcT
3) In step h), the response from the UE shall be on Cell 2. The displayed PLMN shall be PLMN2 (GSM). (PLMN2
is not available on UTRAN so registration on the same PLMN is attempted using other UE-supported RATs).
6.2.1.7 Selection of RAT for UPLMN; Automatic mode
Test to verify that the UE selects the UPLMN RAT according to the UPLMN RAT priority list on the USIM. If no
PLMN/RAT on the UPLMN RAT priority list is available then the UE shall search for PLMNs in the OPLMN list.
priority order);
1.3 Each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM (in
priority order);
References
1. TS 23.122, clause 4.4.3.1.1.
Release 5 93 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 93
1. To verify that:
1.1 the UE selects the UPLMN RAT according to the UPLMN RAT priority list on the USIM.
1.2 If no PLMN/RAT on the UPLMN RAT priority list is available, the UE searches for PLMNs in the OPLMN
list.
Initial conditions
In system information broadcast in each cell, the neighbouring cell list does not contain any other cell belonging to the
same PLMN.

Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH / RF
signal level
[dBm] (TDD)
Technology

Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM
EFPLMNwAcT 1
st
PLMN 3 UTRAN
2
nd
PLMN 4 GSM
EFOPLMNwAcT 1
st
PLMN 5 UTRAN
2
nd
PLMN 6 GSM

The HPLMN (MCC+MNC) of the IMSI for the USIM is set to PLMN2.
Test procedure
c) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN1)
nor home PLMN/RAT (PLMN2, UTRAN or GSM) the UE shall select Cell 1 (1
st
priority PLMN/RAT in
EF
PLMNwAcT
).
d) Cell 1 and Cell 2 are switched off. See note.
e) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN3
registered at step c), home PLMN (PLMN2, UTRAN or GSM) nor any cells for the 1
st
priority PLMN/RAT in
EF
PLMNwAcT
(PLMN3/UTRAN) then UE shall select Cell 4 (2
nd
priority PLMN/RAT in EF
PLMNwAcT
).
Release 5 94 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 94
f) Cell 4 and Cell 3 are switched off. See note.
g) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN4
registered at step e), home PLMN (PLMN2, UTRAN or GSM) nor user controlled PLMN/RAT
(PLMN3/UTRAN or PLMN4/GSM) then UE shall select Cell 5 (1
st
priority RAT for EF
OPLMNwAcT
).
NOTE: When the serving cell (Cell 1 in step d and Cell 4 in step f) is switched off then the UE will trigger the
capable of. Thus need Cell 2 in step d and Cell 3 in step f to be switched off.
st
priority RAT for EF
PLMNwAcT
nd
priority RAT for EF
PLMNwAcT
st
priority RAT for EF
OPLMNwAcT
6.2.1.8 Selection of RAT for OPLMN; Automatic mode
Test to verify that the UE selects the OPLMN RAT according to the OPLMN RAT priority list on the USIM. If no
PLMN/RAT on the OPLMN list is available then the UE shall search for other PLMN/access technology combinations
with received high quality signal in random order.
priority order);
References
1. TS 23.122, clause 4.4.3.1.1.
Release 5 95 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 95
1. To verify that:
1.1 the UE selects the OPLMN RAT according to the OPLMN RAT priority list on the USIM.
1.2 If no PLMN/RAT on the OPLMN RAT priority list is available, the UE searches for "other PLMN/access
technology combinations with received high quality signal in random order".
Initial conditions
In system information broadcast in each cell, the neighbouring cell list does not contain any other cell belonging to the
same PLMN.
Cell CPICH_Ec / RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP /
RF signal level
[dBm] (TDD)
Test
Channel
PLMN Radio Access
Technology

Technology
Identifier
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 2 UTRAN
2
nd
PLMN 2 GSM
EFPLMNwAcT 1
st
PLMN 3 UTRAN
2
nd
PLMN 4 GSM
EFOPLMNwAcT 1
st
PLMN 5 UTRAN
2
nd
PLMN 6 GSM

The HPLMN (MCC+MNC) of the IMSI for the USIM is set to PLMN2.
Test procedure
c) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN1),
home PLMN/RAT (PLMN2, UTRAN or GSM) nor user controlled PLMN/RAT (PLMN3/UTRAN or
PLMN4/GSM) then the UE shall select Cell 1 (1
st
priority RAT for EF
OPLMNwAcT
).
d) Cell 1 and Cell 2 are switched off. See note.
e) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN5
registered in step c), home PLMN/RAT (PLMN2, UTRAN or GSM), user controlled PLMN/RAT
(PLMN3/UTRAN or PLMN4/GSM) nor any cells for the 1
st
OPLMNwAcT

(PLMN5/UTRAN) then UE shall select Cell 4 (2
nd
OPLMNwAcT
).
Release 5 96 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 96
f) Cell 4 and Cell 3 are switched off. See note.
g) The SS waits for random access requests from the UE. As no cell exists for neither registered PLMN (PLMN6
registered in step c), home PLMN/RAT (PLMN2, UTRAN or GSM), user controlled PLMN/RAT
(PLMN3/UTRAN or PLMN4/GSM) nor operator controlled PLMN/RAT (PLMN5/UTRAN or PLMN6/GSM)
then UE shall select another PLMN/access technology combinations with received high quality signal in random
order (Cell 5).
NOTE: When the serving cell (Cell 1 in step d and Cell 4 in step f) is switched off then the UE will trigger the
capable of. Thus need Cell 2 in step d and Cell 3 in step f to be switched off.
st
priority RAT for EF
OPLMNwAcT
nd
priority RAT for EF
OPLMNwAcT
3) In step g), the response from the UE shall be on either Cell 5 (other PLMN/access technology combination) with
associated PLMN7 (UTRAN) shown.
6.2.1.9 Selection of "Other PLMN / access technology combinations"; Automatic
mode
Test to verify that if neither RPLMN, HPLMN, UPLMN nor OPLMN is available, the UE tries to obtain registration on
"Other PLMN/access technology combinations with received high quality signal in random order".
priority order);
Release 5 97 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 97
2. UTRA case: The UE shall scan all RF channels in the UTRA band according to its capabilities to find available
PLMNs. On each carrier, the UE shall search for the strongest cell according to the cell search procedures (for
FDD, see TS 25.214, and TDD, see TS 25.224) and read its system information, in order to find out which
PLMN the cell belongs to. If the UE can read the PLMN identity, the found PLMN shall be reported to the NAS
as a high quality PLMN (but without the RSCP value), provided that the following high quality criterion is
fulfilled:
PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and
P-CCPCH RSCP for UTRA TDD cells.
3. GSM case: A PLMN shall be understood to be received with high quality signal if the signal level is above
-85 dBm.
References
1. TS 23.122, clause 4.4.3.1.1.
2. TS 25.304, clause 5.1.2.2.
3. TS 03.22, clause 4.4.3.
1. To verify that if neither RPLMN, HPLMN, UPLMN nor OPLMN is available, the UE tries to obtain registration
on "Other PLMN/access technology combinations with received high quality signal in random order".
Initial conditions
Cell CPICH_Ec /RF
signal level
[dBm/3.84 MHz]
(FDD)
P-CCPCH_RSCP
/ RF signal level
[dBm] (TDD)
" High
Quality
signal"
Test
Channel
PLMN Radio Access
Technology

Technology
Identifier
EFLOCI PLMN 7 UTRAN
Test procedure
d) The cell on which a response was received, is switched off.
Release 5 98 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 98
e) Step c-d) is repeated until the UE informs that no network is available.
1) In step c), the displayed PLMN is noted.
2) When the test procedure has finished, the noted PLMNs shall have appeared in the following order: PLMN7
first, then PLMN8 or PLMN9 in random order.
6.2.2 Cell selection and reselection
6.2.2.1 Cell reselection if cell becomes barred or S<0; UTRAN to GSM
Test to verify that if both a GSM and UTRAN network is available, the UE performs cell reselection from UTRAN to
GSM if the UTRAN cell becomes barred or S falls below zero.
2.1 The cell is part of the selected PLMN or, of a PLMN considered as equivalent by the UE according to the
occasions/triggers:
3.1 UE internal triggers, so as to meet performance as specified in TS 25.133 for FDD and TS 25.123 for TDD.
The offset Qoffset1
s,n
is used for Qoffset
s,n
to calculate R
n
s
is used for Qhyst
s
to
calculate R
s
.
n
n
to
calculate TO
n
n
is not applied
when calculating R
n
If a TDD or GSM cell is ranked as the best cell, then the UE shall perform cell re-selection to that TDD or
GSM cell.
Release 5 99 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 99
References
1. TS 25.304, clause 5.2.1.
2. TS 25.304, clause 4.3.
3. TS 25.304, clause 5.2.5.1.
4. TS 25.304, clause 5.2.6.1.4.
1. To verify that the UE performs cell reselection from UTRAN to GSM on the following occasions:
Initial conditions
UE is idle updated on cell 1.
All cells belong to the same PLMN.
The Inter-RAT Cell Info List of Cell 1 (UTRAN) refers to Cell 9 (GSM) and Cell 10 (GSM).
The 3G Neighbour Cell Description of Cell 9 (GSM) and Cell 10 (GSM) refers to Cell 1 (UTRAN)
Step a-c:
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
CPICH_Ec (FDD)
dBm /
3.84
MHz
-60
P-CCPCH_RSCP (TDD) dBm -60
Qrxlevmin dBm -101
Srxlev* dBm 41
CellBarred Not barred

Parameter Unit
Cell 9
(GSM)
Cell 10
(GSM)
Test Channel 1 2
RF Signal Level dBm -80 -85
RXLEV_ACCESS_
MIN
dBm -100 -100
C1* dBm 20 15
FDD_Qmin dB -20 -20
FDD_Qoffset dBm 0 0

Step d-f:
Parameter Unit
Cell 1
(UTRAN)
CellBarred Not barred ->Barred
Tbarred s 80
Release 5 100 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 100
Step g:
Parameter Unit
Cell 1
(UTRAN)
Qrxlevmin dB -101 ->-41
Srxlev* dB 40 ->-19

Test procedure
a) The SS activates cells 9, and 10. The SS monitors cells 9 and 10 for random access requests from the UE.
b) Void
c) Void
d) The SS sets Cell 1 to be barred.
e) The SS waits for random access request from the UE.
f) The UE is switched off.
g) Step a-e) is repeated except that in step d), Qrxlevmin is increased, so S will become negative instead of being
barred.
1) In step a), after the UE has responded on Cell 1, it shall not respond on any other cell within 1 min.
3) In step g), the UE shall respond on Cell 9 after Qrxlevmin is increased.
6.2.2.2 Cell reselection if cell becomes barred or C1<0; GSM to UTRAN
Test to verify that if both a GSM and UTRAN network is available, the UE performs cell reselection from GSM to
UTRAN if the GSM cell becomes barred or the path loss criterion C1 falls below zero for a period of 5 s.
1. At least every 5 s the MS shall calculate the value of C1 and C2 for the serving cell and re-calculate C1 and C2
values for non serving cells (if necessary). The MS shall then check whether:
1.1 The path loss criterion (C1) for current serving cell falls below zero for a period of 5 s. This indicates that the
path loss to the cell has become too high.
2. While camped on a cell of the registered PLMN ("camped normally"), the MS may need to select a different cell
("normal cell reselection" state). The following events trigger a cell reselection:
2.1 The path loss criterion parameter C1 (see TS 03.22, clause 3.6) indicates that the path loss to the cell has
become too high;
2.2 The cell camped on (current serving cell) has become barred.
References
1. TS 05.08, clause 6.6.2.
2. TS 03.22, clause 4.5.
Release 5 101 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 101
1. To verify that the UE performs cell reselection from GSM to UTRAN on the following occasions:
1.2 The path loss criterion C1 for serving cell falls below zero for a period of 5 s.
Initial conditions
UE is idle updated on Cell 9.
Cell 9:
The SS transmitted system information for Cell 1 and Cell 2 shall be according to TS 34.108, clause 6.1.4 with the
following exceptions:
The 3G Neighbour Cell Description of Cell 9 (GSM) refers Cell 1 (UTRAN) and Cell 2 (UTRAN).
SYSTEM INFORMATION TYPE 3 REST OCTETS
- SI2q indicated on BCCH Extended
Release 5 102 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 102
SYSTEM INFORMATION TYPE 2QUATER
<RR management Protocol Discriminator bit (4) > 0110'B
<Skip Indicator : bit (4) > 0000'B
<Message type : bit (8) > 0000 0111B
< SI2 quarter Rest Octets >
<BA_IND : bit > 0
<3G_BA_IND : bit > 0
<MP_CHANGE_MARK : bit > 0
<SI2quater _INDEX : bit (4) > 0000B
<SI2quater_COUNT : bit (4) > 0000B
0 | 1 <Measurement_Parameters Description > 0
0 | 1 <GPRS_Real Time Difference Description > 0
0 | 1 <GPSR_BSIC Description > 0
0 | 1 <GPRS_REPORT PRIORITY Description > 0
0 | 1 <GPRS_Measurement_Parameters Description > 0
0 | 1 <NC Measurement Parameters > 0
0 | 1 <extension length > 0
0 | 1 <3G Neighbour Cell Description > 1
0 | 1 <Index_Start_3G : bit (7) > 0
0 | 1 <Absolute_Index_Start_EMR : bit (7) > 0
0 | 1 <UTRAN FDD Description > 1
0 | 1 <Bandwidth_FDD : bit (3) > 0
1 <Repeated UTRAN FDD Neighbour Cells > ** 0 1
0 <FDD-ARFCN : bit (14) > 0 See TS 34.108, clause 6.1.5, table
6.1.1
<FDD_Indic0 : bit > 0
<NR_OF_FDD_CELLS : bit (5) > 00002B
<FDD_CELL_INFORMATION Field > 19 bits
Scrambling code according to TS
34.108, clause 6.1.4, Default settings
for cell No.1 and cell No.2
0 | 1 <UTRAN TDD Description > 0
0 | 1 <3G MEASUREMENT Parameters Description > 1
<Qsearch_I : bit (4) > 0111B (Always)
<Qsearch_C_Initial : bit (1) > 0
0 | 1 <FDD_Qoffset : bit (4) > 1 1000B (0 dB)
<FDD_REP_QUANT : bit (1) > 0
<FDD_MULTIRAT_REPORTING : bit (2) > 00B
<FDD_Qmin : bit (3) > 111B (-12 dB)
0 | 1 <TDD_Qoffset : bit (4) > 0
0 | 1 <GPRS_3G_MEASUREMENT Parameters Description > 1
<Qsearch_P : bit (4) > 1111B (Never)
<3G_SEARCH_PRIO : bit > 0
0 | 1 <FDD_REP_QUANT : bit > 0
0 | 1 <FDD_REPORTING_OFFSET : bit (3) > 0
0 | 1 <TDD_MULTIRAT_REPORTING : bit (2) > 0
0 | 1 <TDD_REPORTING_OFFSET : bit (3) > 0

Cell 1 and Cell 2:
The Inter-RAT Cell Info List of Cell 1 (UTRAN) and Cell 2 (UTRAN) refers to Cell 9 (GSM).
Release 5 103 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 103
Step a-c:
Parameter Unit
Cell 9
(GSM)
Test Channel 1
RF Signal Level dBm -50
RXLEV_ACCESS_
MIN
dBm -70
MS_TXPWR_MAX_
CCH
dBm Max. output power of UE
FDD_Qmin dB -20
FDD_Qoffset dB 0
CELL_BAR_ACCES
S
Not barred
C1* dB 20

Parameter Unit Cell 1
(UTRAN)
Cell 2
(UTRAN)
P-CCPCH_RSCP
(TDD)
dBm -60 -70
CPICH_Ec (FDD) dBm/3.84
MHz
-60 -70
Qrxlevmin dBm -101 -101
Srxlev* dB 41 31
Step d-e:
Parameter Unit
Cell 9
(GSM)
CELL_BAR_ACCES
S
Not barred ->Barred
Step f-g:
Parameter Unit
Cell 9
(GSM)
RF Signal Level dBm
-50 ->
-80 (4sec) ->
-50
C1* dB
20 ->
-10 (4sec) ->
20
Step h:
Parameter Unit
Cell 9
(GSM)
RF Signal Level dBm
-50 ->
-80
C1* dB
20 ->
-10
Test procedure
a) The SS activates cells 1, and 2. The SS monitors cells 1 and 2 for random access requests from the UE.
b) Void.
c) Void
e) The SS waits for random access request from the UE.
f) The UE is switched off.
g) Step a-e) is repeated except that in step d), the SS reduces signal level on Cell 9 to 80 dBm for 4 s and then
raises the level back to 50 dBm (C1 becomes 10 dBm during this period).
Release 5 104 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 104
h) The SS reduces signal level on Cell 9 to 80 dBm.
1) In step a), after the UE has responded on Cell 9, it shall not respond on any other cell within 1 min.
3) In step g), there shall be no access on Cell 1 within 30 s, after having reduced the signal level on Cell 1.
4) In step h), the UE shall respond on Cell 1.
6.2.2.3 Cell reselection timings; GSM to UTRAN
Test to verify that the UE meets the cell reselection timing requirements when both a GSM and UTRAN network is
available.
1. If the 3G Cell Reselection list (see TS 04.18) includes UTRAN frequencies, the MS shall, at least every 5 s
update the value RLA_C for the serving cell and each of the at least 6 strongest non-serving GSM cells.
1.1 The MS shall then reselect a suitable UTRAN cell if its measured RSCP value exceeds the value of RLA_C
for the serving cell and all of the suitable non-serving GSM cells by the value XXX_Qoffset for a period of
5 s and, for FDD, the UTRAN cells measured Ec/No value is equal or greater than the value FDD_Qmin.
- Ec/No and RSCP are the measured quantities.
- FDD_Qmin and XXX_Qoffset are broadcast on BCCH of the serving cell. XXX indicates other radio
access technology/mode.
1.2 In case of a cell reselection occurring within the previous 15 s, XXX_Qoffset is increased by 5 dB.
1.3 Cell reselection to UTRAN shall not occur within 5 s after the MS has reselected a GSM cell from an
UTRAN cell if a suitable GSM cell can be found.
1.4 If more than one UTRAN cell fulfils the above criteria, the UE shall select the cell with the greatest RSCP
value.
2. The MS shall be able to identify and select a new best UTRAN cell on a frequency, which is part of the 3G Cell
Reselection list, within 30 s after it has been activated under the condition that there is only one UTRAN
frequency in the list and under good radio conditions.
The allowed time is increased by 30 s for each additional UTRAN frequency in the 3G Cell Reselection list.
However, multiple UTRAN cells on the same frequency in the neighbour cell list does not increase the allowed
time.
NOTE: Definitions of measurements are in TS 25.215 and TS 25.101 for FDD mode, in TS 25.225 and TS
25.102 for TDD mode, clause 3.2 and TS 05.08, clause 6.1.
References
1. TS 05.08, clause 6.6.5.
2. TS 05.08, clause 6.6.4.
1. To verify that:
1.1 The UE meets conformance requirement 1.1 and additionally, that no cell reselection is performed if the
period is less than 5 s
Release 5 105 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 105
1.2 The UE meets conformance requirement 1.2.
1.3 The UE meets conformance requirement 1.3.
Initial conditions
UE is idle updated on Cell 9.
Cell 9 and Cell 10:
The 3G Neighbour Cell Description of Cell 9 (GSM) and Cell 10 (GSM) refers Cell 1 (UTRAN).
SYSTEM INFORMATION TYPE 3 REST OCTETS
- SI2q indicated on BCCH Norm
Release 5 106 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 106
SYSTEM INFORMATION TYPE 2QUATER
<RR management Protocol Discriminator bit (4) > 0110'B
<Skip Indicator : bit (4) > 0000'B
<Message type : bit (8) > 0000 0111B
< SI2 quarter Rest Octets >
<BA_IND : bit > 0
<3G_BA_IND : bit > 0
<MP_CHANGE_MARK : bit > 0
<SI2quater _INDEX : bit (4) > 0000B
<SI2quater_COUNT : bit (4) > 0000B
0 | 1 <Measurement_Parameters Description > 0
0 | 1 <GPRS_Real Time Difference Description > 0
0 | 1 <GPSR_BSIC Description > 0
0 | 1 <GPRS_REPORT PRIORITY Description > 0
0 | 1 <GPRS_Measurement_Parameters Description > 0
0 | 1 <NC Measurement Parameters > 0
0 | 1 <extension length > 0
0 | 1 <3G Neighbour Cell Description > 1
0 | 1 <Index_Start_3G : bit (7) > 0
0 | 1 <Absolute_Index_Start_EMR : bit (7) > 0
0 | 1 <UTRAN FDD Description > 1
0 | 1 <Bandwidth_FDD : bit (3) > 0
0 <FDD-ARFCN : bit (14) > 0 See TS 34.108, clause 6.1.5, table
6.1.1
<FDD_Indic0 : bit > 0
<NR_OF_FDD_CELLS : bit (5) > 00001B
<FDD_CELL_INFORMATION Field > 10 bits
Scrambling code according to TS
34.108, clause 6.1.4, Default settings
for cell No.1
0 | 1 <UTRAN TDD Description > 0
0 | 1 <3G MEASUREMENT Parameters Description > 1
<Qsearch_I : bit (4) > 0111B (Always)
<Qsearch_C_Initial : bit (1) > 0
0 | 1 <FDD_Qoffset : bit (4) > 1 1000B (0 dB)
<FDD_REP_QUANT : bit (1) > 0
<FDD_MULTIRAT_REPORTING : bit (2) > 00B
<FDD_Qmin : bit (3) > 111B (-12 dB)
0 | 1 <TDD_Qoffset : bit (4) > 0
0 | 1 <GPRS_3G_MEASUREMENT Parameters Description > 1
<Qsearch_P : bit (4) > 1111B (Never)
<3G_SEARCH_PRIO : bit > 0
0 | 1 <FDD_REP_QUANT : bit > 0
0 | 1 <FDD_REPORTING_OFFSET : bit (3) > 0
0 | 1 <TDD_MULTIRAT_REPORTING : bit (2) > 0
0 | 1 <TDD_REPORTING_OFFSET : bit (3) > 0

Release 5 107 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 107
Cell 1:
The SS transmitted system information for Cell 1 shall be according to TS 34.108, clause 6.1.4 with the following
exceptions:
The Inter-RAT Cell Info List of Cell 1 (UTRAN) refers to Cell 9 (GSM) and Cell 10 (GSM).
Step a-c:
Parameter Unit Cell 9 (GSM)
Cell 10
(GSM)
Test Channel 1 2
RXLEV_ACCESS_
MIN
dBm -100 -100
MS_TXPWR_MAX_
CCH
dBm
Max. output
power of UE
Max. output
power of UE
FDD_Qmin dBm -20 -20
FDD_Qoffset dB 5 5

Parameter Unit Cell 1 (UTRAN)
Test Channel 1
CPICH_Ec (FDD)
dBm /
3.84
MHz
-74
P-CCPCH_RSCP (TDD) dBm -74
Qrxlevmin dBm -101
Srxlev* dB 27

Step d-g:
Parameter Unit Cell 9 (GSM) Cell 10 (GSM)
RF Signal Level dBm
-70 ->
-82 (4 s) ->
-70
OFF
Step h-j:
RF Signal Level dBm
-82 ->
-70
OFF
Step k-m:
RF Signal Level dBm
-82 ->
-70 ->
-82
OFF

Test procedure
NOTE: Step a-c): Test purpose 1.3. Step d-g): test purpose 1.1. Step h-k): test purpose 1.2.
a) The SS activates the channels. The UE is not paged on any of the cells.
b) Void
c) After 50 s, the SS starts paging continuously on cells 9 and 1 for 20 s. The SS monitors cells 9 and 1 for random
access requests from the UE.
d) Cell 10 is switched off. The SS stops paging on the cells and waits for 20 s. (The UE should revert to Cell 9 due
to cell reselection).
e) The SS starts paging continuously on Cell 1.
Release 5 108 3GPP TS 34.123-1 V5.7. (2004-04)
3GPP 108
f) The SS decreases the transmit level of Cell 9 to 82 dBm for a period of 4 s (RSCP will then exceed RLA_C
value of Cell 9 by more than XXX_Qoffset) and then changes the level back to 70 dBm.
g) The SS waits to see if there is any random access requests from the UE on Cell 1.
h) The SS stops paging on all cells and sets the transmit level of Cell 9 to 82 dBm.
i) The SS waits 20 s and then starts paging continously on Cell 9. (The UE should revert to Cell 1 due to cell
reselection).
j) The SS increases the transmit level of Cell 9 to 70 dBm and waits for the UE to access on Cell 9. The SS
records the time t from the increase in the level of Cell 9 to the first response from the UE.
k) The SS stops paging on all cells and sets the transmit level of Cell 9 back to 82 dBm.
l) The SS waits 20 s (The UE should revert to Cell 1 due to cell reselection).
m) The SS increases the transmit level of Cell 9 to 70 dBm. After t+2 s (i.e. 2 s after reselection to Cell 9), the SS
starts paging continuously on Cell 1, changes the level of Cell 9 back to 82 dBm and waits to see if there is any
random access request on Cell 1. (Within 15 sec after cell reselection to GSM, the level of Cell 9 is -82 +10
dBm=-72 dBm. After the 15 s period, the level of Cell 9 is 82 +5 dBm=-77 dBm. The level of Cell 1 is 74
dBm, thus leading to reselection to Cell 1 after 15 s).
1) In step c), after the UE has reselected Cell 9 from Cell 1 as indicated by random access requests, any random
access requests on Cell 1 shall not occur within 4,5 s of the last random access request on Cell 9.
2) In step g), there shall be no access on Cell 1 within 34 s of decreasing the level of Cell 9.
3) In step j), the UE shall respond on Cell 9.
4) In step m), there shall be no response on Cell 1 within 11 s after the level of Cell 9 is changed back to -82 dBm.
NOTE: The 11 s is derived from (t+15) s minimum cell reselection timer minus (t+2) s from the start of step m)
up to the decrease of the level of Cell 9. A further 2 s are subtracted to cover for any uncertainty
introduced by the random access process occurring after step g).
Release 5 109 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7 Layer 2
7.1 MAC
General
If not otherwise mentioned, the same procedures as used in RRC test specification (TS 34.123-1 clause 8) or in the
generic setup procedures (TS 34.108 clause 7) applies to reach initial conditions for MAC testing.
If not explicitly described, the same message contents and settings are applied as described in the RRC test description
default settings.
In some MAC test cases, which are explicitly mentioned, the RLC in the system simulator is operated in Transparent
Mode (RLC TM) for the tested channel. Accordingly, no RLC header will be added by the RLC entity. Also, there is no
header included by the MAC protocol. in the system simulator. The UE, however, shall always be configured as
specified in TS 34.108 for the respective test case.
Where RLC TM is used, the payload size in the system simulator is set to the value, that corresponds to the transport
block size expected by the UE for the respective configuration. The bit positions which are interpreted as RLC and
MAC headers by the UE, are included into the RLC payload by the system simulator.
For test cases where AM RLC is employed in either UE, SS, or both, the default parameter settings as defined in clause
7.2.3.1 are applicable if not mentioned otherwise.
7.1.1 Mapping between logical channels and transport channels
7.1.1.1 CCCH mapped to RACH/FACH / Invalid TCTF
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on
the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
CCCH mapped to RACH/FACH:
- TCTF field is included in MAC header.
MAC SDU TCTF

The following fields are defined for the MAC header:
- Target Channel Type Field

Release 5 110 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Coding of the Target Channel Type Fi eld on FACH for FDD
TCTF Designation
00 BCCH
01000000 CCCH
01000001-
01111111
Reserved
(PDUs with this coding
will be discarded by this
version of the protocol)
10000000 CTCH
10000001-
10111111
Reserved
11 DCCH or DTCH
over FACH

Coding of the Target Channel Type Fi eld on FACH for TDD
TCTF Designation
000 BCCH
001 CCCH
010 CTCH
01100 DCCH or DTCH
over FACH
01101-
01111
Reserved
100
SHCCH
101-111 Reserved

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.4.
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field is correctly applied when a CCCH is mapped to the RACH/FACH.
Initial conditions
System Simulator:
1 cell, default parameters, Ciphering Off.
The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD) , 6.11.5.4.4.3(1.28Mcps TDD)
(Interactive/Background 32 kbps RAB +SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB for BCCH)
with the following exceptions for the FACH:
FDD:
Release 5 111 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Higher
layer
RAB/signalling RB SRB#0
User of Radio Bearer Test
RLC Logical channel type CCCH
RLC mode TM
Payload sizes, bit 168
Max data rate, bps 33600 (alt.
50400)
RLC header, bit 0
MAC
MAC header, bit 0 (note)
MAC multiplexing Simulated by SS
Layer 1 TrCH type FACH
TB sizes, bit 168
TFS
TF0, bits 0 x 168
TF1, bits 1 x 168
TF2, bits 2 x 168
TF3, bits N/A (alt. 3 x 168)
TTI, ms 10
Coding type CC 1/2
CRC, bit 16
Max number of bits/TTI
before rate matching
752 (alt. 1136)
RM attribute 200-240
NOTE: The SS MAC layer must be configured not to add
a MAC header so that the header can be added
by the test case in order to create the necessary
invalid values.
TDD:
Higher
layer
RAB/signalling RB SRB#0
RLC Logical channel type CCCH
RLC mode TM
50400)
RLC header, bit 0
MAC
TB sizes, bit 171
TFS
TF0, bits 0 x 171
TF1, bits 1 x 171
TF2, bits 2 x 171
TF3, bits 3 x 171
TF4, bits 4x 171
TF5, bits N/A (alt. 5x 171)
TTI, ms 20
Coding type CC 1/2
CRC, bit 16
1528 (alt. 2292)
invalid values.

And using the configuration in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) for the PCH.
The TFCS should be configured as specified in clause 6.10.2.4.3.3.1.4 (FDD), 6.11.5.4.4.3.1.4(1.28Mcps TDD).
User Equipment:
Release 5 112 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The UE shall operate under normal test conditions, Ciphering Off.
The Test-USIM shall be inserted.
The SS starts broadcasting the System Information as specified in TS 34.108 clause 6.1, using the configuration
for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION 5) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps
TDD) (Interactive/Background 32 kbps RAB +SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB
for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1(FDD), 6.11.5.4.5.2(TDD).
The SS follows the procedure in TS 34.108 clause 7.2.2.1 (CS UE) or 7.2.2.2 (PS UE) so that the UE shall be in
idle mode and registered.
Test procedure
a) The SS pages the UE.
b) The SS waits for the first RRC CONNECTION REQUEST message to arrive on the PRACH/CCCH.
c) The SS responds with an RRC CONNECTION SETUP message (specified in TS 34.108 cclause 9: Contents of
RRC CONNECTION SETUP message: UM (Transition to CELL_FACH)(FDD), or UM (Transition to
CELL_DCH) (1.28 Mcps TDD option). In this case the SS will transmit the message in 152 bit (note)
segments, with a valid UM RLC header and with the MAC header set as follows:
FDD:
Field Value
TCTF 01000001'B
TDD:
Field Value
TCTF 000'B

d) The SS waits for retransmission of the RRC CONNECTION REQUEST on the PRACH/CCCH due to expiry of
timer T300. If no retransmission is received steps a) and b) are repeated.
e) The SS repeats steps c) and d), with the TCTF field set as follows:
FDD:
Iteration TCTF Value
2 (void)
3 10000000'B
4 10000001'B
5 (void)
TDD:
2 010'B
3 01100'B
4 01101'B
5 100
6 101'B

f) The SS repeats steps c) and d), with the TCTF field set as to 01000000'B(FDD), 001B(TDD).
Release 5 113 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
FDD:
Step Direction Message Comments
UE SS
1 PAGING TYPE 1
2 RRC CONNECTION REQUEST
3 - Void
4 - Void
5 MAC PDU(TCTF, RLC UM PDU(SN, RRC
CONNECTION SETUP SEGMENT 1))
Sent with incorrect TCTF =0100
0001'B
MAC PDU(TCTF, RLC UM PDU(SN, RRC
0001'B

CONNECTION SETUP SEGMENT n))
0001'B
6 RRC CONNECTION REQUEST If this message is not received then
the PAGING TYPE 1 message as
in step 1 shall be sent again.
0000'B
MAC PDU(TCTF, UE-ID, RLC UM PDU(SN, RRC
0000'B

0000'B
0001'B
0001'B

0001'B
11 - Void
12 - Void
Sent with correct TCTF =0100
0000'B
0000'B

0000'B
14 RRC CONNECTION SETUP COMPLETE TCTF Field is recognised as correct
for the CCCH
TDD:
Release 5 114 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
1 PAGING TYPE 1
Sent with incorrect TCTF =000'B


MAC PDU(TCTF, UE-ID, RLC UM PDU(SN, RRC




Sent with correct TCTF =001'B

Sent with correct TCTF =001B
16 RRC CONNECTION SETUP COMPLETE TCTF Field is recognised as correct
for the CCCH

Release 5 115 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Specific Message Contents
None.
7.1.1.1.5 Test Requirement
On the first iteration, and on each iteration in step e) the UE should not recognise the RRC CONNECTION SETUP
message and therefore should either retransmit the RRC CONNECTION REQUEST after each expiry of T300 (the UE
should send up to N300=3 RRC CONNECTION REQUESTs before abandoning the procedure) or not respond (if N300
RRC CONNECTION REQUESTs have already been sent).
On the final iteration the UE should respond with an RRC CONNECTION SETUP COMPLETE message.
7.1.1.2 DTCH or DCCH mapped to RACH/FACH / Invalid TCTF
DTCH or DCCH mapped to RACH/FACH:
TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header.
- Target Channel Type Field

Coding of the Target Channel Type Fi eld on FACH for FDD
TCTF Designation
00 BCCH
01000000 CCCH
01000001-
01111111
Reserved
10000000 CTCH
10000001-
10111111
Reserved
11 DCCH or DTCH
over FACH

Release 5 116 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Coding of the Target Channel Type Fi eld on FACH for TDD
TCTF Designation
000 BCCH
001 CCCH
010 CTCH
01100 DCCH or DTCH
over FACH
01101-
01111
Reserved
100
SHCCH
101-111 Reserved

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field, C/T field, UE-Id type and UE-Id field are correctly applied when a DTCH or
DCCH is mapped to the RACH/FACH.
Initial conditions
System Simulator:
1 cell, default parameters, Ciphering Off.
The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (Interactive/Background 32 kbps RAB
+SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB for BCCH) with the following exceptions for the
FACH:
Higher
layer
RAB/signalling RB RB#3 (SRB#3)
RLC Logical channel type DCCH
RLC mode TM
50400)
RLC header, bit 0
MAC
TB sizes, bit 168
TFS
TF0, bits 0 x 168
TF1, bits 1 x 168
TF2, bits 2 x 168
Release 5 117 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
TTI, ms 10
Coding type CC
CRC, bit 16
752 (alt. 1136)
invalid values.

and using the configuration in TS 34.108 clause 6.10.2.4.3.3 for the PCH.
The TFCS should be configured as specified in clause 6.10.2.4.3.3.1.4.
User Equipment:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (Interactive/Background 32 kbps
RAB +SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1.
The SS follows the procedure in TS 34.108 clause 7.4.2.1 (Mobile Terminated) so that the UE shall be in state
BGP 6-2 (CS-CELL_FACH_INITIAL).
Test procedure
a) The SS receives the PAGING RESPONSE message from the UE and checks the TCTF field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message
containing an AUTHENTICATION REQUEST message.
1. Dummy octet string for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including
the correct RLC AM header.
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this domain exists).
3. The polling bit in RLC header is set for transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field Value
TCTF 01000001'B
UE ID Type C-RNTI
UE ID As set in RRC CONNECTION
SETUP message.
C/T Logical Channel ID for SRB #3 (AM-
DCCH NAS High Priority)

Where a TCTF size of 8-bits is used, 6-bits from the RLC payload shall be discarded.
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on SRB3.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct TCTF of 11'B. The sequence
numbers in the RLC headers shall be identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
Release 5 118 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB #2.
g) The SS repeats steps b), c), d) e) and f), with the TCTF field set as follows in step b):
2 01111111'B
3 10000000'B
4 10000001'B
5 10111111'B

Expected sequence
UE SS
1 PAGING RESPONSE Check TCTF
2 MAC PDU(TCTF, UE-ID, C/T, RLC AM
PDU(SN=x, DIRECT TRANSFER))
Sent with incorrect TCTF =
01000001'B, 01111111'B,
10000000'B, 10000001'B, or
10111111'B
2a wait for T =10 s SS checks that UE shall neither
transmit RRC-Status message on
SRB 2 nor RLC Status PDU on
SRB 3
See note 1 below
4 RLC-STATUS-PDU ACK PDUs with SN =x and TCTF
Field is recognised as correct for
the DCCH.
See note 2 below
5 RRC Status message
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or
GMM Timer T3317.
NOTE 2: RRC Status message may be received before RLC Status PDU.

Steps 2 5 of above expected sequence are repeated for iterations 2 to 5. Note: For iteration k the SN in steps 2 and 4
starts with x +(k 1).
None
In step a) the TCTF field should have the value 00'B. Note that this may be implied from receipt of the PAGING
RESPONSE message correctly by the SS test script.
During the test the SS shall request an RLC status report with every transmitted PDU by setting of the Polling Bit. The
UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive an RRC Status message on SRB #
2, and RLC Status PDU on SRB #3 with TCTF field set to value '01' B.
7.1.1.3 DTCH or DCCH mapped to RACH/FACH / Invalid C/T Field
Release 5 119 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- C/T field
The C/T field provides identification of the logical channel instance when multiple logical channels are carried
on the same transport channel
Structure of the C/T field
C/T field Designation
0000 Logical channel 1
... ...
1111 Reserved
(PDUs with this coding will be
discarded by this version of
the protocol)

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
1. To verify that the UE discards PDUs with reserved or incorrect values in C/T field.
Initial conditions
System Simulator:
See clause 7.1.1.2.4.
User Equipment:
Test procedure
a) The SS receives the PAGING RESPONSE message from the UE and checks the C/T field.
containing.
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this domain exists).
3. The polling bit in RLC header is set for Transmission of RLC STATUS PDU.
Release 5 120 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Field Value
TCTF 11'B
UE ID Type C-RNTI
SETUP message.
C/T 0111'B

c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct C/T value for AM-DCCH NAS
High Priority of 0010'B. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
g) The SS repeats steps b), c), d), e) and f), with the C/T field set as follows:
Iteration C/T Value
2 1111'B

Expected sequence
UE SS
1 PAGING RESPONSE Check C/T field
Sent with incorrect C/T =0111'B, or
1111'B.
SRB 3.
See note 1 below.
Sent with correct C/T =0010'B
4 RLC-STATUS-PDU ACK PDUs with SN =x
C/T Field is recognised as correct
for the DCCH.
See note 2 below.
GMM Timer T3317.

Steps 2 to 5 of the expected sequence are repeated for iteration 2. Note: For iteration k the SN in steps 2 and 4 starts
with x +(k 1).
None
In step a) the C/T field should be set to the Logical Channel ID for SRB #3 (0010'B). Note that this may be implied
from receipt of the PAGING RESPONSE message correctly by the SS test script.
During the test the SS shall request RLC status report with every transmitted PDU by setting of the Polling Bit. The UE
shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB #3,
with C/T field set to value '0010'B and RRC Status message on SRB #2.
Release 5 121 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.1.4 DTCH or DCCH mapped to RACH/FACH / Invalid UE ID Type Field
- UE-Id Type
The UE-Id Type field is needed to ensure correct decoding of the UE-Id field in MAC Headers.
Table 9.2.1.7: UE-Id Type field definition
UE-Id Type field 2 bits UE-Id Type
00 U-RNTI
01 C-RNTI
10
Reserved
the protocol)
11
Reserved
the protocol)

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
1. To verify that the UE discards PDUs with reserved values in UE-Id type field.
Initial conditions
System Simulator:
User Equipment:
Test procedure
a) The SS receives the PAGING RESPONSE message from the UE and checks the UE-Id Type field.
containing.
Release 5 122 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this domain exists)
Field Value
TCTF 11'B
UE ID Type 10'B
SETUP message.
DCCH NAS High Priority): 0010'B

d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct UE-Id type value for C-RNTI
of 01'B. The sequence numbers in the RLC headers shall be identical with those sent in b).
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB #2
g) The SS repeats steps b), c), d), e) and f), with the UE-Id type field set as follows in step b):
Iteration UE-Id type Value
2 11'B

Expected sequence
UE SS
1 PAGING RESPONSE Check UE-Id Type
Sent with incorrect UE-Id Type =
10'B, or 11'B.
SRB 3.
See note 1 below.
Sent with correct UE-Id Type =01'B
4 RLC-STATUS-PDU ACK PDU with SN =x
UE-Id is recognised as correct for
the UE.
See note 2 below.
5 RRC Status message RRC
GMM Timer T3317.

Steps 2 to 5 of the expected sequence are repeated for iteration 2. Note: For iteration k the SN in step 2 and 4 starts with
x +(k 1).
None
Release 5 123 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
In step a) the UE-Id Type field should be set to 01'B. Note that this may be implied from receipt of the PAGING
RESPONSE message correctly by the SS test script.
During the test the SS request an RLC status report with every transmitted PDU by setting of the Polling Bit. The UE
shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB #3,
with UE Id type correctly set to '01'B and RRC Status message on SRB #2.
7.1.1.5 DTCH or DCCH mapped to RACH/FACH / Incorrect UE ID
- UE-Id
The UE-Id field provides an identifier of the UE on common transport channels
Lengths of UE Id field
UE Id type Length of UE Id field
U-RNTI 32 bits
C-RNTI 16 bits

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
1. To verify that the UE ignores PDUs with UE-Ids that do not match the Id allocated to it.
Initial conditions
System Simulator:
User Equipment:
Test procedure
a) The SS receives the PAGING RESPONSE message from the UE and checks the UE-Id field.
Release 5 124 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
containing.
1. Dummy Octet String for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits,
including the correct RLC AM header.
2. The IE CN Domain Identity is Sset to PS Domain (no signalling connection for this domain exists)
Field Value
TCTF 11'B
UE ID Type C-RNTI
UE ID Address allocated in RRC
CONNECTION SETUP message +
1.
DCCH NAS High Priority): 0010'B

d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct UE-Id value of the address
allocated in the RRC CONNECTION SETUP message. The sequence numbers in the RLC headers shall be
identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU
Expected sequence
UE SS
1 PAGING RESPONSE Check UE-Id
Sent with incorrect UE-Id =C-
RNTI+1
SRB 3.
See note 1 below.
Sent with correct UE-Id =C-RNTI
UE-Id is recognised as correct for
the UE.
See note 2 below.
GMM Timer T3317.

None
In step a) the UE-Id field should be set to the C-RNTI allocated in the RRC CONNECTION SETUP message. Note that
this may be implied from receipt of the PAGING RESPONSE message correctly by the SS test script.
Release 5 125 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
During the test the SS shall request an RLC status report with every transmitted PDU by setting of the Polling Bit. The
At the end of the expected sequence (steps 4 and 5) the SS shall receive receive RLC Status PDU on SRB #3 with
correct C-RNTI and RRC Status message on SRB #2.
7.1.1.6 DTCH or DCCH mapped to DSCH or USCH
7.1.1.6.1 Definition and applicability
Applicable for if mode TDD only or FDD only is supported.
The TCTF field is included in the MAC header for TDD only. The UE-Id type and UE-Id are included in the MAC
header for FDD only. The C/T field is included if multiplexing on MAC is applied.
Reference(s)
TS 25.321 clause 9.2.1.1.
To verify when DTCH or DCCH is mapped to DSCH or USCH, the TCTF field is applied for TDD only, the UE-Id
type and UE-Id are applied for FDD only. If multiplexing on MAC is applied, C/T field is included, otherwise, the C/T
field is not included in the MAC header.
Initial conditions
System Simulator:
- 1 cell, default parameters. Ciphering Off.
User Equipment:
- The UE shall operate under normal test conditions, Ciphering Off.
- The Test-USIM shall be inserted.
The UE is in Connected mode and a connection is established as described in the TS 34.123-1, 7.3 PDCP testing, clause
"Setup a UE originated PS session using IP Header compression in AM RLC (using Loop back test mode 1).
TBD
Foreseen Final State of the UE
Test procedure
a) The SS sends a certain data block to the UE.
b) After having received the data block via configured mapped channels, the UE forwards the data to its Radio
Bearer Loop Back entity. The received data shall be returned by the UE via its MAC configuration to the SS.
c) The SS receives the returned data block and checks its MAC header whether the TCTF is applied for TDD only,
or the UE-Id type and UE-Id are applied for FDD onlyand the C/T field shall not be applied.
d) The SS configures the RLC.
Release 5 126 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
e) The SS starts a Radio Bearer Reconfiguration procedure to be connected in RLC transparent mode and
configures the Radio Bearer for multiplexing.
f) The SS sends a certain data block to the UE.
g) After having received the data block via configured mapped channels, the UE forwards the data to its Radio
h) The SS receives the returned data block and check its MAC header whether the TCTF is applied for TDD only,
or the UE-Id type and UE-Id are applied for FDD only and the C/T field is applied.
i) The SS reconfigures its RLC mode to be in AM.
Expected sequence
UE SS
1 DATA BLOCK The SS sends one data block with MAC header,
sets TCTF as "DCCH or DTCH over USCH or
DSCH" for TDD only, or sets UE-Id type as "C-
RNTI", and UE-Id as C-RNTI of UE for FDD only.
2 LOOP BACK DATA BLOCK SS receives the loop back data block from the
Uplink RB and checks the MAC header.
3 SS sends CMAC_MAC_HEADER_REQ with
enable_mac_header and CRLC_CONFIG_REQ
with RLC mode as "AM mode".
4 RADIO BEARER RECONFIGURE Reconfigures the downlink and uplink radio bearer
as multiplexing .
5 RADIO BEARER
RECONFIGURATION COMPLETE

disable_mac_header and CRLC_CONFIG_REQ
with RLC mode as "Transparent mode".
sets TCTF as "DCCH or DTCH over USCH or
DSCH" for TDD only, or sets UE-Id type as "C-
RNTI", and UE-Id as C-RNTI of UE for FDD only
and C/T field is included.

RADIO BEARER SET UP:
RLC info
- RLC mode

RB mapping info
-Downlink
- Number of logical channels
- Downlink transport channel type

-Uplink
- Uplink transport channel type

AM RLC

1
DSCH

1
USCH

Release 5 127 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
RADIO BEARER RECONFIGURE:
RLC info
- RLC mode

RB mapping info
-Downlink
-Uplink

AM RLC

2
DSCH

2
USCH

TCTF field in the MAC header of loop back data block is "DTCH or DCCH over DSCH or USCH" for TDD only. The
UE-ID type and UE-Id are applied in the MAC header for FDD only. If multiplexing on MAC is applied, C/T field is
included, otherwise, C/T field is not included.
7.1.1.7 DTCH or DCCH mapped to CPCH
All UEs which support CPCH.
UE-Id type field and UE-Id are included in the MAC header. The C/T field is included in the MAC header if
multiplexing on MAC is applied.
Reference(s)
TS 25.321 clauses 9.2.1.1 and 11.3.
TS 25.214 clause 6.2.
TS 25.211 clause 5.3.3.11.
To verify when DTCH or DCCH mapped to CPCH, UE-Id type field and UE-Id are included in the MAC header. if
multiplexing on MAC is applied, the C/T field is included in the MAC header, otherwise, C/T field is not included.
Initial conditions
System Simulator:
- 1 cell, default parameters, Ciphering Off.
User Equipment:
The UE is in Connected mode and a connection is established as described in the TS 34.123-1, 7.3 PDCP testing, clause
"Setup a UE originated PS session using IP Header compression in UM RLC (using Loop back test mode 1).
Release 5 128 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
TBD
Test procedure
a) The SS sends SIBs 7, 8, and 9, sends CSICH information and waits 30 s.
b) The SS reconfigures its RLC mode to be in transparent mode RLC. Afterwards its sends a certain data block to
the UE.
c) After having received the data block via configured mapped channels, the UE forwards the data to its Radio
d) The SS receives the returned data block and checks its MAC header, whether a UE-Id type and a UE-Id are
included.
e) The SS reconfigures its RLC mode to be in AM.
f) The SS starts a Radio Bearer Reconfiguration procedure to be connected in RLC transparent mode and
configures the Radio Bearer for multiplexing.
g) The SS sends the next data block via its MAC entity with MAC header, including the UE-Id type as "C-RNTI"
and UE-Id as C-RNTI of the UE.C/T field.
h) After having received the data block via configured mapped channels, the UE forwards the data to its Radio
i) The SS receives the returned data block and checks its MAC header, whether UE-Id type, UE-Id field are
included and C/T field is applied or not.
Expected sequence
UE SS
1 SIBs 7, 8 and 9 and CSICH
information
Containing default settings for CPCH.
sets UE-Id type as "C-RNTI", and UE-Id as C-
RNTI of UE.
5 RADIO BEARER RECONFIGURE Reconfigures the downlink and uplink radio bearer
as multiplexing.
6 RADIO BEARER

disable_mac_header and CRLC_CONFIG_REQ
with RLC mode as "Transparent mode".
sets UE-Id type as "C-RNTI", and UE-Id as C-
RNTI of UE.

Release 5 129 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
RLC info
- RLC mode

RB mapping info
-Downlink

-Uplink

AM RLC

1
FACH

1
CPCH

RADIO BEARER RECONFIGURE:
RLC info
- RLC mode

RB mapping info
-Downlink
-Uplink

AM RLC

2
FACH

2
CPCH

PRACH persistence level info in System Information Block type 7
Information Element Value/Remark
PRACHs listed in SIB 5
- Dynamic persistence level


All set to 8, which maps to minimum persistence value,
no access allowed

no access allowed

CPCH parameters in System Information Block type 8
Back off control parameters
- N_ap_retrans_max
- N_access_fails
- NF_bo_no aich
- NS_bo_busy
- NF_bo_all_busy
- NF_bo_mismatch
- T_CPCH
Power Control Algorithm
TPC step size
DL DPCCH BER

15
15
15
15
15
15
0
algorithm 1
1
15

Release 5 130 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CPCH set info in System Information Block type 8
AP preamble scrambling code
AP-AICH channelisation code
CD preamble scrambling code
CD/CA-ICH channelisation code
DeltaPp-m
UL DPCCH Slot Format
N_start_message
CPCH status indication mode
PCPCH Channel #1 info
- UL scrambling code
- DL channelisation code
- PCP length
- UCSM info
- Minimum spreading factor
- NF_max
- AP signature
- PCP length
- UCSM info
- NF_max
- AP signature

16
15
17
16
0
1
8
PA mode

18
15
8

64
64
15

19
14
8

64
64
14

PCPCH persistence level info in System Information Block type 9
CPCH set persistence levels
- PCPCH persistence level

Both set to 1, immediate access allowed

CSICH Information broadcast by SS PHY
PCPCH Channel Availability (PCA) :
-PCA1
-PCA2

Available
Available

The UE-Id type and UE-Id field are included in the MAC header. When multiplexing on MAC is not applied, C/T field
is included in the MAC header. Otherwise, C/T field is not included.
7.1.1.8 DTCH or DCCH mapped to DCH / Invalid C/T Field
the DCH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
DTCH or DCCH mapped to DCH, no multiplexing of dedicated channels on MAC: -no MAC header is required.
DTCH or DCCH mapped to DCH, with multiplexing of dedicated channels on MAC: -C/T field is included in MAC
header.
Release 5 131 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- C/T field
The C/T field provides identification of the logical channel instance when multiple logical channels are carried
on the same transport channel
Structure of the C/T field
C/T field Designation
... ...
1111 Reserved
the protocol)

Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 b).
1. To verify that the UE discards PDUs with reserved or incorrect values in C/T field.
2. To verify that the C/T field is correctly applied when a DTCH or DCCH is mapped to a DCH.
Initial conditions
System Simulator:
Release 5 132 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The DCH/DPCH is configured as specified in TS 34.108 clause 6.10.2.4.1.2 (FDD), 6.11.5.4.1.2(1.28Mcps
TDD): (Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH) with the following exception:
Higher layer RAB/signalling RB RB#3 (SRB#3)
User of Radio Bearer NAS_DT
High prio
RLC Logical channel type DCCH
RLC mode TM
Max data rate, bps 3700
RLC header, bit 0
MAC MAC header, bit 0 (note)
Layer 1 TrCH type DCH
TB sizes, bit 148
TFS TF0, bits 0 x 148
TF1, bits 1 x 148
TTI, ms 40
Coding type CC 1/3
CRC, bit 16
Max number of bits/TTI before rate
matching
516
Uplink: Max number of bits/radio
frame before rate matching
129
NOTE: The SS MAC layer must be configured not to add a MAC header so that
the header can be added by the test case in order to create the
necessary invalid values.

The TFCS should be configured as specified in clause 6.10.2.4.1.2.1.1.2 (FDD), 6.11.5.4.1.2.1.1.2(1.28 Mcps
TDD).
User Equipment:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps
TDD) (Interactive/Background 32 kbps RAB +SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB
for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1 (FDD), 6.11.5.4.5.2(1.28Mcps
TDD).
The SS follows the procedure in TS 34.108 clause 7.4.2.1 (Mobile Terminated) so that the UE shall be in state
BGP 6-1 (CS-CELL_DCH_INITIAL). During this procedure the RRC CONNECTION SETUP message shall
allocate a DCH to carry the signalling radio bearers as follows:
1. The DCH/DPCH is configured as specified in TS 34.108 clause 6.10.2.4.1.2 (FDD), 6.11.5.4.1.2(1.28Mcps
TDD): Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH).
Test procedure
a) The SS receives the PAGING RESPONSE message from the UE and checks the C/T field.
containing
Release 5 133 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this Domain exists).
Field Value
C/T '0111'B

d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct C/T value for AM-DCCH NAS
High Priority of 0010'B. The sequence numbers in the RLC headers shall be identical with those sent in b).
g) The SS repeats steps b), c), d), e) and f), with the C/T field set as follows in step b):
Iteration C/T Value
2 1111'B

Expected sequence
UE SS
1 PAGING RESPONSE Check C/T field
2 MAC PDU(C/T, RLC AM PDU(SN=x, DIRECT
TRANSFER))
Sent with incorrect C/T =0100'B, or
1111'B
SRB 3.
See note 1 below.
3 MAC PDU(C/T, RLC AM PDU(SN=x, DIRECT
TRANSFER))
Sent with correct C/T =0010'B
C/T Field is recognised as correct
for the DCCH.
See note 2 below.
GMM Timer T3317.

Steps 2 to 5 of the expected sequence are repeated for iteration 2. Note: For iteration 2 the SN in steps 2 and 4 starts
with x+1.
None
In step a) the C/T field should be set to the Logical Channel ID for SRB #3 (0010'B). Note that this may be implied
from receipt of the PAGING RESPONSE message correctly by the SS test script.
During the test the SS shall request RLC status reports with every transmitted PDU by setting of the Polling Bit. The
Release 5 134 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB #3
with C/T field set to '0010'B and RRC Status message on SRB #2.
7.1.2 RACH/FACH procedures
7.1.2.1 Selection and control of Power Level
7.1.2.1.1 Void
NOTE Test case "Selection and control of Power Level (FDD)" has been removed as the test purpose is
implicitely tested by radio resource management test cases in TS 34.121 clause 8.4.2.1 and 8.4.2.2.
7.1.2.1.2 Selection and control of Power Level (3,84 Mcps TDD option)
(FFS)
7.1.2.1.3 Selection and control of Power Level (1,28 Mcps TDD option)
7.1.2.1.3.1 Definition and applicability
All TDD 1,28 Mcps UE
7.1.2.1.3.2 Conformance requirement
1. The UE sets the initial preamble transmit power to the value P
UpPCH
given in clause 8.5.7 of TS 25.331.
2. If the UE does not receive an acknowledgement on the FPACH then the UE increases the preamble transmission
power by the specified increment Pwr
ramp
.
3. The UE ceases power ramping after the maximum number of pre-amble increments permitted has been
completed.
4. Where the UE is permitted to complete a number of power ramping cycles, the UE returns to the initial transmit
power (no increment applied) at the start of each cycle. The number of cycles completed before the UE ceases
transmission should equal the maximum number of permitted power ramping cycles.
5. The UE does not transmit on PRACH resources.
Reference(s)
TS 25.224 clause 5.6.
TS 25.331 clause 8.5.7.
TS 25.321 clause 11.2.3.
7.1.2.1.3.3 Test Purpose
To verify that:
- the UE selects the correct preamble transmit powers during a power ramp cycle, taking account of the desired
UpPCH receive power and power ramp step specified in the BCH layer 3 message SIB 5,
- the number of steps in a power ramp cycle and the number of power ramp cycles completed when no reply is
received from the UTRAN is equal to the values specified for these parameters in the BCH layer 3 messages
SIB 5,
- the UE does not transmit on the PRACH resources specified in the BCH message SIB 5.
Release 5 135 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.2.1.3.4 Method of test
Initial conditions
The UE is attached to the network and in idle mode.
Related ICS/IXT Statement(s)
TBD
The same as the initial condition.
Test procedure
a) The SS pages the UE to initiate the RACH access procedure;
b) The SS does not respond to UpPCH transmissions received from the UE;
c) The SS measures the power level of each UpPCH code that the UE transmits;
d) The SS monitors the PRACH resources to ensure that no transmissions are received from the UE;
e) The procedure is continued until the maximum permitted power ramping cycles, and within each power ramping
cycle, the maximum number of UpPCH transmissions have been made. The UpPCH and PRACH channels are
then continued for time, tbd, to ensure that no further transmissions are made by the UE.
Expected sequence
UE SS
1 <- PAGE
2 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes
3 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes +Pwrramp
4
5 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes +n. Pwrramp
6 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes
7 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes +Pwrramp
8
9 -> UpPCH PUpPCH =LPCCPCH +PRXUpPCHdes +n. Pwrramp
10 Wait for time-period

7.1.2.1.3.5 Test requirements
The power of the first UpPCH transmission should equal P
UpPCH
=L
PCCPCH
+PRX
UpPCHdes
, subsequent transmissions
should increase in power by Pwr
ramp
until the maximum permitted number of steps in a power ramping cycle has been
completed. The power ramping cycle should be repeated Mmax times before the UE ceases to transmit. The UE should
not transmit on any PRACH resources.
7.1.2.2 Correct application of Dynamic Persistence
7.1.2.2.1 Void
NOTE Test case "Correct application of Dynamic Persistence (FDD)" has been removed as the test purpose is
implicitely tested by radio resource management test cases in TS 34.121.
7.1.2.2.2 Correct application of Dynamic Persistence (3.84 Mcps TDD option)
(FFS)
Release 5 136 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.2.2.3 Correct application of Dynamic Persistence (1.28 Mcps TDD option)
All TDD 1.28 Mcps UE
The UE responds to changes in the dynamic persistence parameter broadcast in SIB 7.
Reference(s)
TS 25.331 clause 8.5.12.
TS 25.321 clause 11.2.3.
To verify that if the dynamic persistence value broadcast in SIB7 is set to zero, the UE will not attempt RACH access.
Initial conditions
The UE is attached to the network and in idle mode. The Sim card should be configured so that the UE adopts ASC =1
or greater. The SS BCH broadcast will include SIB 7 with the dynamic persistence parameter set to zero.
TBD
Test procedure
a) The SS repeatedly pages the UE for T
??
seconds.
b) The SS monitors UpPCH for a response from the UE.
Expected sequence
UE SS
1 <- PAGE
2 Wait

7.1.2.2.3.5 Test Requirements
No UpPCH transmission should be received from the UE.
Release 5 137 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.2.3 Correct Selection of RACH parameters
7.1.2.3.1 Correct Selection of RACH parameters (FDD)
7.1.2.3.1.1 Definition
The physical random access procedure described in this subclause is initiated upon request of a PHY-Data-REQ
primitive from the MAC sublayer.
The UE selection of "PRACH system information" is described in TS 25.331 clause 8.5.17.
A. The physical random-access procedure shall be performed as follows:
1 Derive the available uplink access slots, in the next full access slot set, for the set of available RACH sub-
channels within the given ASC with the help of TS 25.214, subclauses 6.1.1. and 6.1.2. Randomly select one
access slot among the ones previously determined. If there is no access slot available in the selected set,
randomly select one uplink access slot corresponding to the set of available RACH sub-channels within the
given ASC from the next access slot set. The random function shall be such that each of the allowed selections is
chosen with equal probability.
2 Randomly select a signature from the set of available signatures within the given ASC. The random function
shall be such that each of the allowed selections is chosen with equal probability.
3 Set the Preamble Retransmission Counter to Preamble Retrans Max.

5 Transmit a preamble using the selected uplink access slot, signature, and preamble transmission power.
6 If no positive or negative acquisition indicator (AI +1 nor 1) corresponding to the selected signature is
detected in the downlink access slot corresponding to the selected uplink access slot:
6.1 Select the next available access slot in the set of available RACH sub-channels within the given ASC.
6.2 Randomly select a new signature from the set of available signatures within the given ASC. The random
function shall be such that each of the allowed selections is chosen with equal probability.

6.4 Decrease the Preamble Retransmission Counter by one.
6.5 If the Preamble Retransmission Counter >0 then repeat from step 5. Otherwise pass L1 status ("No ack on
AICH") to the higher layers (MAC) and exit the physical random access procedure.
7 If a negative acquisition indicator corresponding to the selected signature is detected in the downlink access slot
corresponding to the selected uplink access slot, pass L1 status ("Nack on AICH received") to the higher layers
(MAC) and exit the physical random access procedure.
8 Transmit the random access message three or four uplink access slots after the uplink access slot of the last
transmitted preamble depending on the AICH transmission timing parameter. Transmission power of the control
part of the random access message should be P p-m [dB] higher than the power of the last transmitted preamble.
Transmission power of the data part of the random access message is set according to subclause 5.1.1.2.
9 Pass L1 status "RACH message transmitted" to the higher layers and exit the physical random access procedure.
Reference(s)
TS 25.214 clause 6.1.
7.1.2.3.1.3 Test purpose
To verify that:
Release 5 138 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
A1 the UE, initially:
- determines the ASC for the given Access Class (AC).
- derives the available uplink access slots, in the next full access slot set, for the set of available RACH sub-
channels within the given ASC with the help of TS 25.214, subclauses 6.1.1. and 6.1.2. and randomly select
one access slot among the ones previously determined.
- randomly select a new signature from the set of available signatures within the given ASC.
A2 the UE, when not receiving any reply from UTRAN:
- selects the next available access slot in the set of available RACH sub-channels within the given ASC.
- randomly select a new signature from the set of available signatures within the given ASC.
- does not transmit on the PRACH resources specified in the BCH message SIB 5 after that the physical
random access procedure is terminated.
A3 the UE, when detecting a negative acquisition indicator:
- does not transmit on the PRACH resources specified in the BCH message SIB 5 after that the physical
A4 the UE, when detecting a positive acquisition indicator:
- transmits the random access message three or four uplink access slots after the uplink access slot of the last
transmitted preamble depending on the AICH transmission timing parameter.
- terminates the random access procedure.
Initial conditions
The UE shall be attached to the network and in idle mode.
The UE shall use Access Class AC#15 which provides permission to use ASC#0 for the initial access. This condition is
achieved by inserting the USIM card with "Type B" setting of the parameter EF
ACC
(Access Control Class) as defined
in TS 34.108.
Preamble Retrans Max parameter in SIB5 set to 5.
Maximum number of preamble retransmission cycles in SIB 5 is set to Mmax =1.
2 ASC settings (ASC#0 and ASC#1) are defined (with default parameters) in SIB5, except that the parameter assigned
sub channel number is set as follows:
ASC#0 Assigned sub channel number ='0001'B
The available sub-channel number defined in SIB5 is set to '1111 1111 1111'B. Note: this value allows RACH
transmission on all sub-channels defined by "Assigned sub channel number" above.
TBD
The same as the initial conditions.
Release 5 139 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
a) The SS pages the UE until it performs a RACH access.
b) The SS measures the access slot and preamble signature used.
c) The SS does not acknowledge the RACH access, causing the UE to retry.
d) The SS again measures the access slot and preamble signature used.
e) The SS repeats the procedure from step c) until the maximum number of retries "Preamble Retrans Max"have
been attempted, and monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
f) The SS pages the UE until it performs a RACH access.
g) The SS measures the the access slot and preamble signature used.
h) The SS responds with a negative acquisition indicator on the AICH.
i) The SS monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
j) The SS pages the UE until it performs a RACH access.
k) The SS measures the access slot used.
l) The SS acknowledges the RACH access normally.
m) The SS measures the first access slot used in the PRACH message part.
n) The SS monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
Expected sequence
UE SS
1 PAGE Preamble Retransmission Counter =5
2 Access Preamble Access slot used =n, where n is defined by the
table in clause 7.1.2.3.1.5
Signature used =any from {P0 .. P7}
Preamble Retransmission Counter =4
3 Access Preamble Access slot used =mod(n+3,15)
7 Wait for T =10s SS monitors for RACH access attempts
8 PAGE
10 AICH =NEG ACQUISITION IND
12 PAGE
14 AICH =POS ACQUISITION IND
15 RRC_CONNECTION_REQUEST Message part. Access slot used =mod(n+3, 15)

Release 5 140 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The following deviations from System Information Block type 5 in TS 34.108 are applicable:
PRACH power offset info, PRACH info, and PRACH partitioning in System Information Block type 5
PRACH info
- CHOICE
- Available Sub Channel number
PRACH partitioning
- Access Service Class
- ASC Setting
- CHOICE mode
- Available signature Start Index
- Available signature End Index
- Assigned Sub-channel Number
- ASC Setting
- CHOICE mode
- Available signature Start Index
- Available signature End Index
- Assigned Sub-channel Number
PRACH power offset
- Preamble Retrans Max

FDD
'1111 1111 1111 1111'B

FDD
0 (ASC#0)
7 (ASC#0)
'0001'B

FDD
0 (ASC#1)
7 (ASC#1)
'0010'B

5

A1
At step 2
- the SS shall receive a PRACH preamble using an access slot as defined below and using a preamble
signature from the set of preamble signatures {P
0
.. P
7
}. See TS 25.213, clause 4.3.3.3 for a list of preamble
codes.
- the access slot selected for the first access preamble can be any of the shaded table entries given below for
ASC#0, depending on SFN (Note: the table entries which are not shaded are not allowed for ASC#0):
SFN modulo 8 of
corresponding P-
CCPCH frame
Sub-channel number
0 1 2 3 4 5 6 7 8 9 10 11
0 0 1 2 3 4 5 6 7
1 12 13 14 8 9 10 11
2 0 1 2 3 4 5 6 7
3 9 10 11 12 13 14 8
4 6 7 0 1 2 3 4 5
5 8 9 10 11 12 13 14
6 3 4 5 6 7 0 1 2
7 8 9 10 11 12 13 14

A2
At steps 3, 4, 5, and 6
- the SS shall receive a PRACH preamble using access slot mod(n +3, 15), where n is the access slot used in
the previous step, and using a preamble signature from the set of preamble signatures {P
0
.. P
7
}. See TS
25.213, clause 4.3.3.3 for a list of preamble codes.
At step 7
- the SS shall not receive on the PRACH resources specified in the BCH message SIB 5 after that the physical
A3
Release 5 141 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
At step 11
A4
At step 15
- the SS shall receive the random access message three access slots after the uplink access slot of the
preamble received in step 13.
At step 11
7.1.2.3.2 Correct Selection of RACH parameters (3.84 Mcps TDD option)
(FFS)
7.1.2.3.3 Correct Selection of RACH parameters (1.28 Mcps TDD option)
All TDD 1.28 Mcps UE
That the UE selects UpPCH codes and UpPCH sub-channels that are defined for the ASC that the UE should adopt
based on its AC (when the RACH message to be transmitted is an 'RRC Connection Request'). Parameters are defined
in the SIB 5 messages received by the UE.
Reference(s)
TS25.224 clauses 4.7.1 and 5.6.
TS25.321 clause 11.2.3.
To verify that the UE selects UpPCH codes and sub-channels that are allocated to the ASC that the UE should adopt
based on its AC.
Initial conditions
The UE is attached to the network and in idle mode. The Sim card should be configured so that the UE can adopt a
known ASC based on its AC. The SS will broadcast SIB 5 messages that allocate to each ASC subsets of the total
UpPCH codes and sub-channels.
TBD
Release 5 142 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
The test procedure is similar to that specified for test 7.1.2.1.3. In place of power level the test monitors the UpPCH
codes that are used for the UE's UpPCH transmissions and the sub-channels in which they are made.
a) The SS pages the UE to initiate the RACH access procedure;
b) The SS does not respond to UpPCH transmissions received from the UE;
c) The SS identifies the UpPCH codes on which the UE transmits;
d) The SS identifies the system frame numbers of the frames in which the UE's UpPCH transmissions are received;
e) The procedure is continued until the maximum permitted power ramping cycles, and within each power ramping
cycle, the maximum number of UpPCH transmissions have been made.
Expected sequence
UE SS
1 <- PAGE
2 -> UpPCH Code and sub-channel should be valid.
4
8

7.1.2.3.3.5 Test Requirements
The UpPCH transmissions should be made in sub-channels and using codes that are allocated to the ASC that the UE
should adopt based on its AC.
7.1.2.4 Correct Detection and Response to FPACH (1.28 Mcps TDD option)
All TDD 1,28 Mcps UE.
That the UE:
1. Receives and acts upon an FPACH message transmitted within WT sub-frames of the UE transmitting a UpPCH
code, provided that:
- The FPACH was transmitted in the FPACH resource associated with the UpPCH code used by the UE; and
- The FPACH message correctly identifies the UpPCH codes identity and the number of sub-frames between
the UpPCH and the FPACH transmissions.
2. Responds to the valid FPACH by transmitting an 'RRC Connection Request' message in the PRACH resources
associated with the FPACH. The transmission should:
- Occupy the PRACH resource associated with the FPACH and the sub-channel in which the FPACH was
received for the duration of the TTI;
- Be made with a timing correction and a transmission power that are based on information received in the
FPACH.
Release 5 143 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3. Does not respond to FPACH messages that are transmitted, within WT sub-frames of the UE UpPCH
transmission, in FPACH resources that are not associated with the UpPCH code that the UE used. Nor should it
respond to FPACH messages that are received on the correct FPACH resources within WT sub-frames but which
contain the incorrect UpPCH code identifier or an incorrect indication of the number of sub-frames elapsed
between the UpPCH and FPACH transmissions.
Reference(s)
TS 25.224 clauses 4.7.1, 5.2.3, 5.6.
TS 25.331 clause 8.5.7.
TS 25.321 clause 11.2.3.
7.1.2.4.3 Test Purpose
To verify that:
- The UE does not respond to FPACH transmissions that are either, received on incorrect FPACH resources, or are
received on correct resources and within WT sub-frames of the UpPCH transmission, but which do not contain
the correct UpPCH identity or elapsed sub-frames.
- The UE does respond to an FPACH transmission that is received, within WT sub-frames of the UpPCH
transmission, on the correct FPACH resources for the UpPCH code that was used, provided that the FPACH
contains the identity of the UpPCH code and the number of sub-frames elapsed between the UpPCH and the
FPACH transmissions.
- The UE response is to transmit an 'RRC Connection Request' message on the PRACH resources that are
associated with the FPACH taking account of the timing correction and power adjustment parameters received in
the FPACH.
Initial conditions
The UE is attached to the network and in idle mode. The SS BCH SIB 5 message will specify that there are two or more
FPACH associated with the UpPCH code set in a single PRACH system information. The UpPCH code set must
include one or more odd and one or more even numbered codes.
TBD
Test procedure
The test procedure consists of a number of stages:
a) The SS pages the UE to initiate RACH access.
b) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT sub-
frames of each UpPCH transmission but on an incorrect FPACH resource for the UpPCH code used. It is noted
that the UE may change the code used for each UpPCH transmission randomly amongst those available to its
ASC.
c) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
d) The SS pages the UE to initiate RACH access.
Release 5 144 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
e) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT
sub-frames of each UpPCH transmission on the correct FPACH resource for the UpPCH code used. The FPACH
transmission should contain a signature reference number that is different from that of the UpPCH code that was
used by the UE.
f) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
g) The SS pages the UE to initiate RACH access.
h) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT
sub-frames of each UpPCH transmission on the correct FPACH resource for the UpPCH code used. The FPACH
transmission should contain a relative sub-frame number that is different from that defined by the elapsed
number of frames between the UpPCH and the FPACH transmissions.
i) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
j) The SS pages the UE to initiate RACH access.
k) When UpPCH transmissions are received from the UE the SS should transmit an FPACH response on the correct
FPACH resources for the UpPCH code that was used by the UE. The FPACH response should include correct
values for the signature reference and relative sub-frame number fields. The FPACH should also include known
entries for the Received starting position of the UpPCH (UpPCH
POS
) and the Transmit Power Level Command
for RACH (PRX
PRACHdes
) fields.
l) The SS should monitor the PRACH resources associated with the FPACH commencing two or three sub-frames
(depending upon the sub-frame in which the FPACH was transmitted and the length of the TTI) following the
sub-frame in which the FPACH was transmitted and continuing for the number of sub-frames in the RACH TTI.
The power level of the PRACH transmissions and the time of arrival of their mid-ambles should be measured.
The SS should continue to monitor the UpPCH slot to ensure that the UE has ceased UpPCH transmissions.
Expected sequence
UE SS
1 <- PAGE
2 -> UpPCH
3 <- FPACH Incorrect FPACH resources
4 -> UpPCH
5 .
6 <- PAGE
7 -> UpPCH
8 <- FPACH Incorrect signature reference
9 -> UpPCH
10
11 <- PAGE
12 -> UpPCH
13 <- FPACH Incorrect relative sub-frame number
14 -> UpPCH
15 .
16 <- PAGE
17 -> UpPCH
18 <- FPACH Correct resources and information fields
19 -> RRC Connection
Request
PPRACH =LPCCPCH +PRXPRACHdes +(i-1)*Pwrramp,
UpPCHADV +UpPCHPOS- 816Tc

The UE should not respond to FPACH transmissions, which are made on the incorrect FPACH resources for the
UpPCH code that the UE uses. The UE should continue to transmit UpPCH until the permitted maximum number of
power ramping cycles is complete.
The UE should not respond to FPACH transmissions which are made within WT sub-frames of a UpPCH transmission
and on the correct FPACH resources for the UpPCH code that it used if the FPACH contains either an incorrect
Release 5 145 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
signature reference number or an incorrect relative sub-frame number. The UE should continue to transmit UpPCH until
the permitted maximum number of power ramping cycles is complete.
The UE should respond to an FPACH received within WT sub-frames of a UpPCH transmission if the FPACH is
received on the correct FPACH resources for the UpPCH code used and if it contains valid information fields. The UE
should cease transmitting UpPCH bursts and transmit an RRC Connection Request message using the PRACH
resources that are associated with the FPACH and the sub-frame in which the FPACH was received. The transmission
should commence two or three sub-frames after that containing the FPACH (dependent upon the sub-frame in which the
FPACH was transmitted and the length of the TTI) and is made in all sub-frames within the TTI. Each PRACH burst
should be made using the transmission power:
P
PRACH
=L
PCCPCH
+PRX
PRACHdes
+(i-1)*Pwr
ramp

Where i is the number of transmission attempts on UpPCH, i=1Max SYNC_UL Transmissions.When the power used
by the UE for the UpPCH transmission acknowledged by the FPACH was:
P
UpPCH
=L
PCCPCH
+PRX
UpPCHdes
+(i-1)*Pwr
ramp

And PRACH
ADV
,i.e., the offset from the start of the PRACH slot of the UE's transmission measured by SS shall be
UpPCH
ADV +
UpPCH
POS
- 816Tc chips, to an accuracy of 1/8 chip.
Where UpPCH
ADV
denotes the offset from the start of the UpPCH slot of the UE's transmission measured by SS and
UpPCH
POS
is the timing correction signalled to the UE in the FPACH.
7.1.2.4a Access Service class selection for RACH transmission
7.1.2.4a.1 Definition and applicability
All UE.
7.1.2.4a.2 Conformance requirement
The following ASC selection scheme shall be applied, where NumASC is the highest available ASC number and
MinMLP the highest logical channel priority assigned to one logical channel:
- In case all TBs in the TB set have the same MLP, select ASC=min(NumASC, MLP).
- In case TBs in a TB set have different priority, determine the highest priority level MinMLP and select
ASC=min(NumASC, MinMLP).
Reference(s)
TS 25.321 clause 11.2.1.
7.1.2.4a.3 Test purpose
To verify that MAC selects ASC correctly.
7.1.2.4a.4 Method of test
Initial conditions
System Simulator:
User Equipment:
- The Test-USIM shall be inserted
Release 5 146 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION BLOCK types 5 and 6) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (Interactive/Background 32 kbps
RAB +SRB for PCCH +SRB for CCCH +SRB for DCCH +SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1.
The SS follows the procedure in TS 34.108 clause 7.4.2.6 (initiated by Mobile Terminated connection) so that
the UE shall be in state BGP 6-11 (PS-DCCH+DTCH_FACH) with the following exception:
1. The MAC Logical channel Priority (MLP) of the user RB is set to 8.
The user RB is placed into loop-back mode 1 each with the UL SDU size set to 39 bytes.
TBD
Test procedure
a) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
The SS waits to receive uplink data on RACH TrCH via the user RB, then checks that the access slots and
preamble signatures used correspond to a valid ASC as transmitted in system information.
b) The SS reconfigures the transmitted system information as follows:
Only one ASC setting (ASC#0) is defined, with default parameters, except that the parameter "Assigned sub
channel number" is set as follows:
The available sub-channel number defined in system information is set to '1111 1111 1111'B (default
parameter setting). Note: this value allows RACH transmission on any sub-channel defined by "Assigned sub
channel number" above.
The SS then updates System Information Block 6, sends a SYSTEM INFORMATION CHANGE INDICATION
message to the UE and waits 10 s for the UE to take the system information change into account.
c) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
d) The SS waits to receive uplink data on RACH TrCH via the user RB, then checks that the access slots and
preamble signatures used correspond to ASC#0, i.e. the access slot selected for the first access preamble can be
any of the shaded table entries given below for ASC#0, depending on SFN (Note: the table entries which are not
shaded are not allowed for ASC#0):
SFN modulo 8 of
corresponding P-
CCPCH frame
Sub-channel number
0 1 2 3 4 5 6 7 8 9 10 11
0 0 1 2 3 4 5 6 7
1 12 13 14 8 9 10 11
2 0 1 2 3 4 5 6 7
3 9 10 11 12 13 14 8
4 6 7 0 1 2 3 4 5
5 8 9 10 11 12 13 14
6 3 4 5 6 7 0 1 2
7 8 9 10 11 12 13 14

e) The SS reconfigures the transmitted system information as follows:
Release 5 147 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Four ASC settings (ASC#0 to ASC#3) are defined (with default parameters), except that the parameter
assigned sub channel number is set as follows:
ASC#3 Assigned sub channel number ='0000'B (i.e. no sub channel is assigned)
The available sub-channel number defined in system information is set to '1111 1111 1111'B (default
parameter setting). Note: this value allows RACH transmission on all sub-channels defined by "Assigned sub
channel number" above.
The SS then updates System Information Block 6, sends a SYSTEM INFORMATION CHANGE INDICATION
message to the UE and waits 10 s for the UE to take the system information change into account.
f) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
g) The SS waits 10 s to ensure no uplink data is received on RACH TrCH via the user RB.
h) The SS then reconfigures the uplink user RB to have a MAC Logical channel Priority of 1.
i) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
j) The SS waits to receive uplink data on RACH TrCH via the user RB, then checks that the access slots and
preamble signatures used correspond to ASC#1, i.e. the access slot selected for the first access preamble can be
any of the shaded table entries given below for ASC#1, depending on SFN (Note: the table entries which are not
shaded are not allowed for ASC#1):
SFN modulo 8 of
corresponding P-
CCPCH frame
Sub-channel number
0 1 2 3 4 5 6 7 8 9 10 11
0 0 1 2 3 4 5 6 7
1 12 13 14 8 9 10 11
2 0 1 2 3 4 5 6 7
3 9 10 11 12 13 14 8
4 6 7 0 1 2 3 4 5
5 8 9 10 11 12 13 14
6 3 4 5 6 7 0 1 2
7 8 9 10 11 12 13 14

k) The SS may optionally release the radio bearer.
Expected sequence
UE SS
1 RLC PDU
1a RLC PDU SS checks ASC parameters
2 SYSTEM INFORMATION
CHANGE INDICATION
Modified system information
3 RLC PDU
4 RLC PDU SS checks ASC parameters (ASC#0)
CHANGE INDICATION
Modified system information
6 RLC PDU
6a SS waits to check no RLC PDUs are received
7 RB RECONFIGURATION User RB MLP =1
8 RLC PDU
9 RLC PDU SS checks ASC parameters (ASC#1)
10 RB RELEASE optional

Release 5 148 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.1.2.4a.5 Test requirements
In step 1, the access slots and preamble signatures used on the PRACH TrCH on which the RLC PDU was received
shall correspond to configured legal values for the allowed ASCs on the PRACH.
shall correspond to configured legal values for the allowed ASC#0.
In step 6a, no PDUs shall be received on PRACH.
shall correspond to configured legal values for the allowed ASC#1.
7.1.2.5 Void
NOTE Test case "Control of RACH transmissions for FDD mode" has been removed as the test purpose is
implicitely tested by radio resource management test case in TS 34.121 clause 8.4.2.3.
7.1.3 Priority handling between data flows of one UE
7.1.3.1 Priority handling between data flows of one UE
When selecting between the Transport Format Combinations in the given Transport FormatCombination Set, priorities
of the data flows to be mapped onto the corresponding Transport Channels can be taken into account.
The chosen TFC shall be selected from within the set of valid TFCs and shall satisfy the following criteria in the order
in which they are listed below:
1. No other TFC shall allow the transmission of more highest priority data than the chosen TFC.
2. No other TFC shall allow the transmission of more data from the next lower priority logical channels. Apply this
criterion recursively for the remaining priority levels.
3. No other TFC shall have a lower bit rate than the chosen TFC.
The above rules for TFC selection in the UE shall apply to DCH, and the same rules shall apply for TF selection on
RACH and CPCH.
Reference(s)
TS 25.301 clause 5.3.1.2.
TS 25.321, clause 11.4.
To verify that the UE prioritise signalling compared to data on a lower priority logical channel.
Initial conditions
System Simulator:
User Equipment:
Release 5 149 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters
as specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined
for UM 7-bit "Length Indicator" tests described in 3G TS 34.108 clause 6.11.1 is used.
Let UM_7_PayloadSize denote the RAB payload size in octets.
None
Test procedure
a. The SS closes the test loop using UE test loop mode 1 with the UL SDU size set to (UM_7_PayloadSize * 50) -
1 bytes. See note 1.
b. The SS transmits a TRANSPORT FORMAT COMBINATION CONTROL message using AM_RLC on the
DCCH, which indicates that only transport format minimum set is allowed on the uplink for DCH transport
channel on the DTCH. I.e. the restricted uplink transport format set shall be (DCCH, UM RLC 7 bit LI
RB)=(TF0, TF0), (TF1, TF0) and (TF0, TF1).
c. The SS transmits a MEASUREMENT CONTROL message requesting periodic reporting with a period of
250ms.
d. The SS sends one RLC SDUs of size floor (UM_7_PayloadSize) - 1 bytes to the UE. The UE is expected to loop
this data back in one RLC SDU, segmented into a total of 50 RLC PDUs.
e. The SS waits until data is returned in uplink.
f. The SS checks that the UE transmits alternating measurement reports and data.
Note 1. Having UE to return 50 PDUs corresponds to 50*TTI (20 ms) =1 second of continous data transmission.
As the periodic measurement interval is 250ms this will guarantee that data transmission will be
interupted by transmission of measurement reports in uplink.
Release 5 150 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 <-- ACTIVATE RB TEST MODE (DCCH) TC
2 --> ACTIVATE RB TEST MODE
COMPLETE (DCCH)
TC
3 <-- RADIO BEARER SETUP (DCCH) RRC
4 --> RADIO BEARER SETUP COMPLETE
(DCCH)
RRC
5 <-- CLOSE UE TEST LOOP (DCCH) TC
UE test mode 1 with UL RLC SDU size
parameter set to achieve UE to transmit 50
PDUs in uplink.
6 --> CLOSE UE TEST LOOP COMPLETE
(DCCH)
TC
7 <-- TRANSPORT FORMAT COMBINATION
CONTROL (DCCH)
RRC
Transport format combinations is limited to
transport format minimum set
(DCCH, AM RLC 7 bit LI RB)=(TF0, TF0),
(TF1, TF0) and (TF0, TF1).
8 <--

MEASUREMENT CONTROL (DCCH) SS sends a MEASUREMENT CONTROL
message requesting periodic reporting at
250 ms interval.
9 <--

Downlink RLC PDU SS sends a SDU fit into one PDU.
10 --> Uplink RLC PDUs SS starts receiving RLC PDUs from the UE
on the UM RLC RB
11 -->

MEASUREMENT REPORT (DCCH) SS checks that at least one
MEASUREMENT REPORT message is
received within 500 ms (=2 x reporting
interval)

12 --> Uplink RLC PDUs SS checks that UE resumes returning RLC
PDUs from the UE on the UM RLC RB

1. After step 10 the UE shall transmit a MEASUREMENT REPORT message within 500 ms.
2. After step 11 the UE shall resume data transmission.
7.1.4 Control of CPCH transmissions.
7.1.4.1 Control of CPCH transmissions for FDD
All UEs which support CPCH.
1. If counter M is not less than N_access_fails, the UE shall execute an access failure error procedure and the
CPCH access procedure ends.
2. If the sum of the Frame Count Transmitted counter plus the number of frames in the next TTI is larger than
NF_max, the UE shall exit the CPCH transmission procedure.
3. If the CSICH information indicates no PCPCH is available, the UE shall not attempt CPCH access.
4. If the CPCH Persistency levels are all set to 8, the UE shall not attempt CPCH access.
Release 5 151 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
5. If the SS issues an immediate Emergency Stop command in the DL-DPCCH for CPCH, the UE shall abort
CPCH access.
Reference(s)
TS 25.321 clause 11.3
TS 25.214 clause 6.
TS 25.211 clause 5.3.3.11.
To verify that the MAC entity control CPCH transmission correctly.
Initial conditions
System Simulator:
User Equipment:
The UE is in Connected mode and a connection is established as described in the TS 34.123-1, clause 7.3 PDCP testing,
clause "Setup a UE originated PS session using IP Header compression in AM RLC (using Loop back test mode 1).
TBD
The same as the initial conditions.
Test procedure
a) The SS ends SIBs 7, 8 and 9, sends CSICH information and waits 30 s.
b) The SS configures its RLC entity for"Transparent Mode".
c) The SS sends certain DATA BLOCKS to UE with UE-Id type and UE-Id field.
d) After having received the data block via configured mapped channels, the UE forwards the data to its Radio
e) The SS receives returned DATA BLOCKS.
f) The SS configures its RLC entity for"AM mode.
g) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
h) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
for"Transparent Mode".
i) The SS sends SIB 8 on BCH with parameter : N_access_fails =0 and waits 30 s.
j) The SS sends certain DATA BLOCKS.
Release 5 152 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
k) The SS shall not receive any LOOP BACK DATA BLOCKS within 30 s.
l) The SS configures its RLC entity for"AM mode".
m) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
n) The SS receives RADIO BEARER RECONFIGURE COMPLETE.
o) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
p) The SS sends SIB 8 on BCH with parameter : NF_max =0 and waits 30 s.
q) The SS sends certain DATA BLOCKS.
r) The SS shall not receive any returned DATA BLOCKS within 30 s.
s) The SS configures its RLC entity for"AM mode".
t) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
u) The SS receives RADIO BEARER RECONFIGURE COMPLETE.
v) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
w) The SS sends SIB 8 on BCH and waits 30 s.
x) The SS continuously sends CSICH information with PCA1=PCA2=NOT AVAILABLE.
y) The SS sends certain DATA BLOCKS.
z) The SS shall not receive any returned DATA BLOCKS within 30 s.
aa) The SS configures its RLC entity for"AM mode".
bb) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
cc) The SS receives RADIO BEARER RECONFIGURE COMPLETE.
dd) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
ee) The SS sends CSICH information with PCA1=PCA2=AVAILABLE and the SS PHY is configured to send
CPCH Emergency Stop message in all DL DPCCHs for CPCH after N_start_message frames.
ff) The SS sends certain DATA BLOCKS.
gg) The SS shall not receive any returned DATA BLOCKS within 30 s.
hh) The SS configures its RLC entity for"AM mode".
ii) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
jj) The SS receives RADIO BEARER RECONFIGURE COMPLETE.
kk) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
ll) The SS sends SIB 9 on BCH with the CPCH persistence levels set to 8, no access allowed.
mm) The SS sends certain DATA BLOCKS.
nn) The SS shall not receive any returned DATA BLOCKS within 30 s.
Release 5 153 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
oo) The SS configures its RLC entity for"AM mode".
pp) The SS starts the RB reconfiguration procedure by sending the RADIO BEARER RECONFIGURATION
message.
qq) The SS receives RADIO BEARER RECONFIGURE COMPLETE.
rr) After having received the UE confimation for the reconfiguration procedure, the SS configures its RLC entity
ss) The SS sends SIB 9 on BCH with the CPCH persistence levels set to 1, immediate access allowed.
tt) The SS sends certain DATA BLOCKS.
uu) The SS receives returned DATA BLOCKS.
vv) The SS configures its RLC entity for"AM mode".
Release 5 154 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 SIBs 7, 8 and 9 and CSICH information Containing default settings for CPCH
disable_mac_header and
CRLC_CONFIG_REQ with RLC mode as
"Transparent mode".
3 DATA BLOCKS
4 LOOP BACK DATA BLOCKS
enable_mac_header and
"AM mode".
6 RADIO BEARER RECONFIGURATION
COMPLETE

"Transparent mode".
9 SIB 8 N_access_fails =0
10 DATA BLOCK
11 The SS can't receive loop back data blocks
from UE in 30s.
"AM mode".
COMPLETE

"Transparent mode".
16 SIB 8 NF_max =0
17 DATA BLOCK UE was trigged to send data block.
18 The SS can't receive data from UE in 30s
"AM mode".
COMPLETE

"Transparent mode".
23 SIB 8 and CSICH information PCA1=PCA2=NOT AVAILABLE
24 DATA BLOCK
"AM mode".

COMPLETE

"Transparent mode".
Release 5 155 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
30 SIB 8 and CSICH information PCA1=PCA2=AVAILABLE
31 SS sends a CPCH-Estop command in all
DLDPCCHs for CPCH after
N_start_message frames
32 DATA BLOCK
"AM mode".
COMPLETE

"Transparent mode".
38 SIB 9 CPCH Persistence levels set to 8; no access
allowed
39 DATA BLOCK
"AM mode".

COMPLETE

"Transparent mode".
45 SIB 9 CPCH Persistence levels set to 1;
immediate access allowed
46 DATA BLOCK
47 LOOP BACK DATA BLOCKS
"AM mode".

RLC info
- RLC mode

RB mapping info
-Downlink

-Uplink

AM RLC

1
FACH

1
CPCH

Release 5 156 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PRACH persistence level info in System Information Block type 7


no access allowed

All set to 8,which maps to minimum persistence value,
no access allowed

CPCH parameters in System Information Block type 8
Back off control parameters
- N_ap_retrans_max
- N_access_fails
- NF_bo_no aich
- NS_bo_busy
- NF_bo_all_busy
- NF_bo_mismatch
- T_CPCH
Power Control Algorithm
TPC step size
DL DPCCH BER

15
15
15
15
15
15
0
algorithm 1
1
15

CPCH set info in System Information Block type 8
AP preamble scrambling code
AP-AICH channelisation code
CD preamble scrambling code
CD/CA-ICH channelisation code
DeltaPp-m
UL DPCCH Slot Format
N_start_message
CPCH status indication mode
- PCP length
- UCSM info
- NF_max
- AP signature
- PCP length
- UCSM info
- NF_max
- AP signature

16
15
17
16
0
1
8
PA mode

18
15
8

64
64
15

19
14
8

64
64
14

Release 5 157 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PCPCH persistence level info in System Information Block type 9
CPCH set persistence levels
- PCPCH persistence level

Both set to 1, immediate access allowed

CSICH Information broadcast by SS PHY
PCPCH Channel Availability (PCA) :
-PCA1
-PCA2

Available
Available

The SS can't receives data blocks from UE when N_access_fails or NF_max set as 0.
The SS can't receives data blocks from UE when NF_max set as 0.
The SS can't receives data blocks from UE when CSICH info indicates channels not available.
The SS can't receives data blocks from UE when CPCH Persistency level set to 8.
The SS can't receives data blocks from UE when Emergency Stop message terminates access.
7.1.5 HS-DSCH MAC-hs
7.1.5.1 MAC-hs reordering and stall avoidance
All UEs which support HS-PDSCH.
When a MAC-hs PDU with TSN =SN is received:
- If SN is within the receiver window:
- if SN <next_expected_TSN, or this MAC-hs PDU has previously been received:
- the MAC-hs PDU shall be discarded.
- else:
- the MAC-hs PDU is placed in the reordering buffer at the place indicated by the TSN.
- If SN is outside the receiver window:
- the received MAC-hs PDU shall be placed above the highest received TSN in the reordering buffer, at the
position indicated by SN;
- RcvWindow_UpperEdge shall be set to SN thus advancing the receiver window;
- any MAC-hs PDUs with TSN RcvWindow_UpperEdge RECEIVE_WINDOW_SIZE, i.e. outside the
receiver window after its position is updated, shall be removed from the reordering buffer and be delivered to
the disassembly entity;
- next_expected_TSN shall be set to RcvWindow_UpperEdge RECEIVE_WINDOW_SIZE +1;
Release 5 158 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- All received MAC-hs PDUs with consecutive TSNs from next_expected_TSN (included) up to the first not
received MAC-hs PDU are delivered to the disassembly entity.
- next_expected_TSN shall be advanced to the TSN of this first not received MAC-hs PDU.
[...]
If no timer T1 is active:
- the timer T1 shall be started when a MAC-hs PDU with TSN >next_expected_TSN is correctly received.
- T1_TSN shall be set to the TSN of this MAC-hs PDU.
If a timer T1 is already active:
- no additional timer shall be started, i.e. only one timer T1 may be active at a given time.
The timer T1 shall be stopped if:
- the MAC-hs PDU with TSN =T1_TSN can be delivered to the disassembly entity before the timer expires.
When the timer T1expires and T1_TSN >next_expected_TSN:
- all correctly received MAC-hs PDUs with TSN >next_expected_TSN up to and including T1_TSN-1 shall be
delivered to the disassembly entity;
- all correctly received MAC-hs PDUs up to the next not received MAC-hs PDU shall be delivered to the
disassembly entity.
- next_expected_TSN shall be set to the TSN of the next not received MAC-hs PDU.
When the timer T1 is stopped or expires, and there still exist some received MAC-hs PDUs that can not be delivered to
higher layer:
- timer T1 is started
- set T1_TSN to the highest TSN among those of the MAC-hs PDUs that can not be delivered.
[...]
Reference(s)
TS 25.321 clauses 11.6.2.3.1, 11.6.2.3.2
1. To confirm that the UE performs MAC-hs reordering and delivers RLC PDUs in order to RLC.
2. To confirm that the UE performs stall avoidance in case of missing MAC-hs PDUs based on a) window based
stall avoidance and b) timer based stall avoidance.
Initial conditions
System Simulator:
Default configurations for HS-DSCH tests [FSS]
User Equipment:
The SS follows the procedure in TS 34.108 7.4.2.6 (Mobile Terminated) so that the UE shall be in state BGP 6-
17 (PS-DCCH +DTCH HS-DSCH). During the procedure the radio bearer defined in TS 34.108 clause [TBD]
shall be established. The following parameters are specific for this test case:

Release 5 159 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Parameter Value
MAC-hs receiver window size 32
MAC-hs reordering timer T1 400 ms

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 39 octets.
Let T be the value of MAC-hs reordering timer T1 parameter.
Test procedure
In this test procedure each MAC-hs PDU contains one RLC PDU carrying one SDU of size 39 octets and one length
indicator indicating the end of the SDU.
a) The SS transmits a MAC-hs PDU with Transmission Sequence Number (TSN) =0 containing an RLC PDU with
SN=0.
b) The SS transmits a MAC-hs PDU with TSN =1 containing an RLC PDU with SN=1.
c) The SS checks that the RLC PDUs with SN=0,1 are looped back
d) The SS repeats the transmission of the MAC-hs PDUs in step a) and b) with identical content except that the
RLC PDUs have SN 2,3
e) The SS checks that no data is looped back (the data is discarded in the UE)
f) The SS transmits a MAC-hs PDU with TSN =3 containing an RLC PDU with SN=3
g) The SS waits 400 ms and checks that no data is looped back and no RLC status report is received during that
time
h) The SS transmits a MAC-hs PDU with TSN =2 containing an RLC PDU with SN=2
i) The SS checks that the RLC PDUs with SN =2,3 are looped back
j) The SS transmits a MAC-hs PDU with TSN =6 containing an RLC PDU with SN=4
k) The SS transmits a MAC-hs PDU with TSN =7 containing an RLC PDU with SN=5
l) The SS transmits a MAC-hs PDU with TSN =38 containing an RLC PDU with SN=6
m) The SS checks that the RLC PDU with SN =4 and 5 is looped back but the RLC PDU with SN =6 is not looped
back
n) The SS waits 400 ms and checks that the RLC PDU with SN =6 is looped back after this time

Release 5 160 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 MAC-hs PDU with TSN =0, containing RLC PDU
with SN =0

2 RLC PDU with SN 0
with SN =1

4 RLC PDU with SN 1
with SN =2
The duplicated data is discarded in
the UE
with SN =3
The duplicated data is discarded in
the UE
with SN =3

8 SS waits T ms and checks that no data is looped
back and no RLC status report is received
The waiting time may need to be
adjusted to assure that T1 has not
expired in the UE
with SN =2

10 RLC PDUs with SN 2,3
with SN =4

with SN =5

13 MAC-hs PDU with TSN =38, containing RLC
PDU with SN =6
SS need to transmit this PDU
before timer T1 in UE expires (400
ms after reception of MAC-hs PDU
with TSN=6). Note: TA
14 RLC PDUs with SN 4,5 The RLC PDUs with SN =4,5 is
looped back after reception of the
MAC_hs PDU in step 13, i.e. before
timer T1 expires
15 SS waits T ms and checks that the RLC PDU with
SN =6 is not looped back during this time

16 RLC PDU with SN 6 The RLC PDU with SN =6 is
looped back after expiry of T1.
Note: TB
NOTE 1: The RLC SN in step 5,6 is increased since otherwise the data would be discarded by RLC even
if the MAC-hs reordering does not work correctly. SInce the data is discarded the same RLC SN
can be reused later in the test sequence.
NOTE 2: In step 8 the absence of an RLC status report is used to check that the RLC PDU with SN =3 is
not delivered to RLC. If the RLC PDU was delivered to RLC the gap in the SN would trigger a
status report (detection of missing PDUs).
NOTE3: In step13, the timer T1 is restarted in the UE since the PDU with TSN =38 can not be delivered
to higher layers.
NOTE 4: General timer tolerance as defined by 34.108 sub-clause 4.2.3 applies.

None
1. After step 1, the RLC PDU with SN =0 shall be looped back
2. After step 3, the RLC PDU with SN =1 shall be looped back
3. After step 5 and 6 , no data shall be looped back
4. After step 7, no data shall be looped back and no RLC status report shall be received
5. After step 9, the RLC PDUs with SN =2,3 shall be looped back
Release 5 161 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
6. After step 13, the RLC PDUs with SN =4,5 shall be looped back
7. In step 16, the RLC PDU with SN =6 shall be looped back and T
B
T
A
shall be equal to T ms .
7.1.5.2 Priority queue handling
Reordering Queue distribution:
The reordering queue distribution function routes the MAC-hs PDUs to the correct reordering buffer based on the
Queue ID.
[...]
The HARQ process processes the Queue ID in the received MAC-hs PDUs. The UE shall:
- arrange the received MAC-hs PDUs in queues based on the Queue ID.
[...]
1. To confirm that the UE handles several priority queues, where different radio bearers are mapped to different
queues.
Initial conditions
System Simulator:
User Equipment:
17 (PS-DCCH +DTCH HS-DSCH). A radio bearer configuration is configured according to the following:

Logical Channel ID MAC-d flow (DL)
/ TrCH ID (UL)
Queue ID Comment
1 1 0
2 1 0
3 2 1
4 2 2
5 3 3
NOTE: LCH 1-2 emulates logical channels with the same priority whereas LCH 3-4
emulates logical channels with different priorities.

Test procedure
a) The SS transmits a MAC-hs PDU where:
Release 5 162 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1. The TSN =0
2. The Queue ID =0
3. The MAC-hs PDU contains an RLC PDU with SN=0.
b) The SS checks that the RLC PDU with SN=0 is looped back and checks that the transport channel and logical
IDs are correct.
c) The SS repeats steps a), b) with the Logical channel ID and Queue ID field set as follows:
Iteration Logical Channel ID Queue ID Value
1 1 0
2 2 0
3 3 1
4 4 2
5 5 3

Expected sequence
UE SS
1 MAC-hs PDU with TSN=0 containing an RLC
PDU with SN =0. The Logical channel ID and
Queue ID are set according to the table above.

2 RLC PDU with SN 0

Steps 1 to 2 of the expected sequence are repeated for iteration 2-5.
1. In step 2, for each iteration, the RLC PDU with SN=0 shall be looped back with the transport channel and logical
channel ID as specified by the table below:
Iteration Logical Channel ID Transport Channel ID
1 1 1
2 2 1
3 3 2
4 4 2
5 5 3

7.1.5.3 MAC-hs PDU header handling
MAC PDU (HS-DSCH):
Release 5 163 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

Queue ID TSN SID
1
N
1
F
1
SID
2
N
2
F
2
SID
k
N
k
F
k

MAC-hs header MAC-hs SDU Padding (opt) MAC-hs SDU
Mac-hs payload
VF

[...]
The following fields are included in the MAC header for HS-DSCH:
- Version Flag (VF):
The VF field is a one bit flag providing extension capabilities of the MAC-hs PDU format. The VF field shall be
set to zero and the value one is reserved in this version of the protocol.
- Queue identifier (Queue ID):
The Queue ID field provides identification of the reordering queue in the receiver, in order to support
independent buffer handling of data belonging to different reordering queues. The length of the Queue ID field is
3 bit.
- Transmission Sequence Number (TSN):
The TSN field provides an identifier for the transmission sequence number on the HS-DSCH. The TSN field is
used for reordering purposes to support in-sequence delivery to higher layers. The length of the TSN field is 6
bit.
- Size index identifier (SID):
The SID fields identifies the size of a set of consecutive MAC-d PDUs. The MAC-d PDU size for a given SID is
configured by higher layers and is independent for each Queue ID. The length of the SID field is 3 bit.
- Number of MAC-D PDUs (N):
The number of consecutive MAC-d PDUs with equal size is identified with the N field. The length of the N field
is 7 bits. In FDD mode, the maximum number of PDUs transmitted in a single TTI shall be assumed to be 70. In
1.28 Mcps TDD mode, the maximum number of PDUs transmitted in a single TTI shall be assumed to be 45. In
3.84 Mcps TDD mode, the maximum number of PDUs transmitted in a single TTI shall be assumed to be 318. If
more PDUs than the defined maximum number of PDUs for the corresponding mode are received, the UE
behaviour is unspecified.
- Flag (F):
The F field is a flag indicating if more SID fields are present in the MAC-hs header or not. If the F field is set to
"0" the F field is followed by a SID field. If the F field is set to "1" the F field is followed by a MAC-d PDU.
[...]
a) Use of reserved coding in the MAC header
If the MAC entity receives a MAC PDU with a header field using a value marked as reserved for this version of
the protocol, it shall discard the PDU, unless explicitly mentioned otherwise.
b) Inconsistent MAC header
If the MAC entity receives a MAC PDU with a header inconsistent with the configuration received from RRC, it
shall discard the PDU. E.g.: In case DTCH is mapped to RACH/FACH, the MAC entity shall discard a PDU
with a C/T field indicating a logical channel number that is not configured.
[...]
Reference(s)
TS 25.321 clauses 9.1.4, 9.2.2, 10
Release 5 164 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1. To confirm that the UE discards PDUs with reserved values of the fields in the MAC header
2. To confirm that the UE discards PDUs with values in the MAC header that are inconsistent with the RRC
configuration.
3. To confirm that the UE correctly reads the MAC header and disassembles the MAC-hs PDU into MAC-d PDUs and
delivers the MAC-d PDUs to the RLC layer.
Initial conditions
System Simulator:
User Equipment:
17 (PS-DCCH +DTCH HS-DSCH). The following parameters are specific for this test case:

Parameter Value
UMD_PDU_size1 128 bit
UMD_PDU_size2 320 bit
Queue ID 0
Size Index Identifier (SID) SID =0: 128 bit
SID =1: 320 bit
MAC-hs reordering timer T1 400 ms
MAC-hs receiver window size 32

The RB is configured with 2 RLC PDU sizes UMD_PDU_size1 and UMD_PDU_size2.
Let T be the value of MAC-hs reordering timer T1 parameter.
Test procedure
a) The SS transmits a MAC-hs PDU containing:
12 RLC UMD PDUs where:
RLC PDUs with SN=0, 2, 4, 6, 8, 10 has the PDU size UMD_PDU_size1 and contains one SDU of length 15
octets and one length indicator indicating the end of the SDU.
RLC PDUs with SN=1, 3, 5, 7, 9, 11 has the PDU size UMD_PDU_size2 and contains one SDU of length 39
octets and one length indicator indicating the end of the SDU.
The MAC fields in the MAC-hs header shall be set according to 25.321 with the following exception:
Field Value
Version flag VF 1

b) The SS checks that the UE does not loop back any data (since the MAC-hs PDU in the previous step is
discarded)
c) The SS again transmits a MAC-hs PDU as in a) above, but this time sets the fields in the MAC-hs header
according to 25.321 with the following exception:
Release 5 165 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Field Value
Size index identifier (SID) 2

The sequence numbers in the RLC headers shall be identical with those sent in a).
d) The SS checks that the UE does not loop back any data (since the MAC-hs PDU in the previous step is
discarded)
e) The SS again transmits a MAC-hs PDU as in a) above, but this time sets the fields in the MAC-hs header
according to 25.321. The sequence numbers in the RLC headers shall be identical with those sent in a).
f) The SS checks that the UE loops back 12 RLC PDUs and checks the sequence numbers of the RLC PDUs

Expected sequence
UE SS
1 MAC-hs PDU with a reserved value of the version
flag
discarded by the UE
2 wait for T ms SS checks that no RLC PDUs are
looped back (note)
3 MAC-hs PDU with a value of the size index
identifier that is inconsistent with RRC
configuration
discarded by the UE
4 wait for T ms SS checks that no RLC PDUs are
looped back (note)
5 MAC-hs PDU with correct values of the MAC-hs
header
Accepted by the UE and the
contained data is looped back.
6 RLC PDUs with SN 0,1, ...,11
NOTE General timer tolerance as defined by 34.108 sub-clause 4.2.3 applies.

See test procedure
1. After step 1, no data shall be looped back to the SS
2. After step 3, no data shall be looped back to the SS
3. After step 5, the RLC PDUs with SN =0,1, ...,11 shall be looped back to the SS
7.1.5.4 MAC-hs retransmissions
[...]
The UE shall:
- if the New Data Indicator has been incremented compared to the value in the previous received transmission in
this HARQ process or this is the first received transmission in the HARQ process:
- replace the data currently in the soft buffer for this HARQ process with the received data.
Release 5 166 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- if the Transport Block Size index value is equal to 111111 (FDD only):
- generate a positive acknowledgement (ACK) of the data in this HARQ process;
- discard the received data;
- assume that the data has been successfully decoded.
- if the New Data Indicator is identical to the value used in the previous received transmission in the HARQ
process:
- if the Transport Block Size index value is equal to 111111 (FDD only):
- assume that the transport block size is identical to the last valid transport block size signalled for this
HARQ process.
- if the data has not yet been successfully decoded:
- combine the received data with the data currently in the soft buffer for this HARQ process.
- if the data in the soft buffer has been successfully decoded and no error was detected:
- deliver the decoded MAC-hs PDU to the reordering entity;
- generate a positive acknowledgement (ACK) of the data in this HARQ process.
- else:
- generate a negative acknowledgement (NAK) of the data in this HARQ process;
- schedule the generated positive or negative acknowledgement for transmission and the time of transmission
relative to the reception of data in a HARQ process is configured by upper layer.
[...]
Reference(s)
TS 25.321 clauses 11.6.22
1. To confirm that the UE correctly transmit positive and negative acknowledgements when receiving MAC-hs PDUs
Initial conditions
System Simulator:
User Equipment:
17 (PS-DCCH +DTCH HS-DSCH). During the procedure the radio bearer defined in TS 34.108 clause [TBD]
shall be established.
Test procedure
a) The SS transmits a MAC-hs PDU where:
Release 5 167 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1. The TSN =0
2. The HARQ process id =0
3. The Queue ID =0
4. The MAC-hs PDU contains an RLC PDU with SN=0.
5. The physical layer CRC is modified such that the CRC check in the UE will fail
b) The SS checks that a negative acknowledgement is received for the correct HARQ process
c) The SS transmits a MAC-hs PDU with the same content as in step a) but where the CRC is correct
d) The SS checks that a postivive acknowledgement is received for the correct HARQ process
e) The SS repeats steps a), b), c), d) with the HARQ process, TSN and RLC SN set as follows for iteration 2 to 7:
Iteration HARQ process TSN RLC SN
1 0 0 0
2 1 1 1
3 2 2 2
4 3 3 3
5 4 4 4
6 5 5 5
7 6 6 6
8 7 7 7

Expected sequence
UE SS
1 MAC-hs PDU sent in process N Erroneous CRC
2 MAC-hs negative acknowledgement with process
id =N

3 MAC-hs PDU sent in process N
4 MAC-hs positive acknowledgement with process
id =N

NOTE: The process id N in step 1-4 is taken from the table in the Test procedure description above.

Steps 1 to 4 of the expected sequence are repeated for iteration 2-8.
1. After step 1, a MAC-hs negative acknowledgement shall be received for the correct HARQ process
2. After step 3, a MAC-hs positive acknowledgement shall be received for the correct HARQ process
7.2 RLC testing
7.2.1 Transparent mode
7.2.1.1 Segmentation and reassembly
Transparent mode segmentation and reassembly are not tested in this release of the specification.
Release 5 168 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.2 Unacknowledged mode
7.2.2.1 General information for UM tests
Two generic Radio Access Bearers are provided for UM tests.
The UM test RAB is set up using the Generic Procedure described in clause 7.1.3 of 3GPP TS 34.108, and with the
default RAB replaced as follows:
- For UM 7-bit "Length Indicator" tests: the RB configuration described in 3GPP TS 34.108 clause 6.11.1 is used.
For these tests, let UM_7_PayloadSize denote the RAB payload size in octets.
- For UM 15-bit "Length Indicator" tests: the RB configuration described in 3GPP TS 34.108 clause 6.11.2 is
used. For these tests, let UM_15_PayloadSize denote the RAB payload size in octets.
The UM test RABs are used in all tests with the following exception:
- Tests that explicitly specify a different Radio Bearer configuration.
All other settings are the same.
The special "Length Indicator" indicating that an SDU begins in the first octet of a PDU, described in clause 9.2.2.8 in
3GPP TS 25.322 is not used in uplink or downlink except when explicitly stated in the corresponding test case.
7.2.2.2 Segmentation and reassembly / Selection of 7 or 15 bit "Length Indicators"
The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length
Indicators" are added to allow correct reconstruction of SDUs. The selection of the size of the "Length Indicator" fields
used must follow the specified rules. Incorrect operation of segmentation, concatenation, or coding of "Length
Indicators" will result in failure of the UE to communicate.
Except for the predefined values reserved for special purposes and listed in TS 25.322 section 9.2.2.8 the "Length
Indicator" shall:
- be set to the number of octets between the end of the RLC header and up to and including the last octet of an
RLC SDU segment;
- be included in the PDUs that they refer to.
The size of the Length Indicator may be either 7 bits or 15 bits.
[...]
For UM:
- if the "largest UMD PDU size" is l25 octets:
- 7-bit "Length Indicators" shall be used.
- else:
- between modifications of the "largest UMD PDU size", the size of the "Length Indicator" is the same for all UMD
PDUs.
Reference(s)
TS 25.322 clauses 9.2.2.8 and 9.2.2.9.
Release 5 169 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
To test that if the size of the largest PDU is l25 octets, 7 bit indicators are used, otherwise, 15 bit indicators are used.
Initial conditions
for UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These settings apply to both the uplink and downlink DTCH.
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 10 bytes.
Test procedure
a) The SS transmits an RLC SDU of size 10 bytes.
b) The SS checks the "Length Indicator" values and SDU size and contents in the RLC PDU returned on the uplink
(assuming a 7-bit "Length Indicator" size).
c) The SS releases the RB, and performs the Radio Bearer establishment procedure (clause 7.1.3 of TS 34.108)
with all the parameters as specified in the procedure, with the exception that the default Radio Access Bearer is
replaced with the RAB defined for UM 15-bit "Length Indicator" tests in clause 7.2.2.1.
All other settings the same.
d) The SS transmits an RLC SDU of size 10 bytes.
e) The SS checks the "Length Indicator" values and SDU size and contents in the RLC PDU returned on the uplink
f) The SS may optionally release the radio bearer.
Expected sequence
UE SS
1 RB ESTABLISHMENT See generic procedures for UM 7 bit LIs
2 DOWNLINK RLC PDU 10 byte SDU +padding
3 UPLINK RLC PDU 10 byte SDU +padding
4 RB RELEASE
5 RB ESTABLISHMENT See generic procedures for UM 15 bit LIs
(largest UMD PDU size >125 bytes)
6 DOWNLINK RLC PDU 10 byte SDU +padding
7 UPLINK RLC PDU 10 byte SDU +padding
8 RB RELEASE Optional step
NOTE 1: The Expected Sequence shown is infomative.
The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity.
Information such as SDU, PDU or Sequence numbers given in the comments column shall be
considered informative only, for test case development purposes.

1. The UE shall send 7 bit "Length Indicators" with values that correctly indicate the end of the SDU received in
step 3.
2. The UE shall send 15 bit "Length Indicators" with values that correctly indicate the end of the SDU received in
step 7.
Release 5 170 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.2.3 Segmentation and reassembly / 7-bit "Length Indicators" / Padding
Indicators" are added to allow correct reconstruction of SDUs. Incorrect operation of segmentation, concatenation, or
coding of "Length Indicators" will result in failure of the UE to communicate.
A "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU.
Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator"
shall:
RLC SDU segment;
[...]
For UM and AM RLC:
- if a 7 bit "Length Indicator" is used in a RLC PDU and one or more padding octets are present in the RLC PDU
after the end of the last RLC SDU:
- indicate the presence of padding by including a "Length Indicator" with value "1111111" as the last "Length
Indicator" in the PDU.
NOTE: After the "Length Indicator" indicating the presence of padding has been included in the RLC PDU, the
length of the padding may be zero.
Reference(s)
TS 25.322 clauses 9.2.2.8 and 11.2.2.1.
1. To test that the UE correctly segments a large SDU, includes a "Length Indicator" indicating padding in the RLC
PDU carrying the last SDU segment, and adds padding at the end.
2. To test that the UE correctly deals with a 7-bit padding "Length Indicator" when present in a received PDU.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_7_PayloadSize +1 bytes.
Test procedure
a) The SS transmits an RLC SDU of size UM_7_PayloadSize +1 bytes. The second of the 2 PDUs sent shall
contain a "Length Indicator" indicating the end of the SDU and the "Length Indicator" indicating that padding is
present.
Release 5 171 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and
content of the received RLC SDU (assuming a 7-bit "Length Indicator" size).
c) The SS may optionally release the radio bearer.
Expected sequence
UE SS
1 RB ESTABLISHMENT See generic procedures
2 DOWNLINK RLC PDU SDU 1
3 DOWNLINK RLC PDU SDU 1 & Padding
4 UPLINK RLC PDU No LI
5 UPLINK RLC PDU Check LIs and re-assembled SDU

1. The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a
"Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second
shall indicate that the remainder of the PDU contains padding.
2. The length and data content of the received SDU shall be the same as the transmitted SDU.
7.2.2.4 Segmentation and Reassembly / 7-bit "Length Indicators" / LI =0
The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-
defined "Length Indicator" value is used to indicate when a SDU ends coincident with the end of the previous PDU.
Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to
communicate.
Except for the predefined values reserved for special purposes and listed in TS 25.322 subclause 9.2.2.8, the "Length
Indicator" shall:
RLC SDU segment;
[...]
In the case where the end of the last segment of an RLC SDU exactly ends at the end of a PDU and there is no "Length
Indicator" that indicates the end of the RLC SDU:
- if 7-bit "Length Indicator" is used:
- a "Length Indicator" with value "000 0000" shall be placed as the first "Length Indicator" in the following
PDU;
[...]
For UM and AM RLC:
Release 5 172 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference(s)
TS 25.322 clause 9.2.2.8 and 11.2.2.1.
1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0's is placed by the transmitter as the
first "Length Indicator" in the next PDU.
2. To test that where a SDU exactly fills a PDU, the receiver accepts a "Length Indicator" of all 0's, placed as the
Initial conditions
The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_7_PayloadSize bytes.
Test procedure
a) The SS transmits an RLC SDU of size 2 * UM_7_PayloadSize bytes.
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=0 and padding
5 UPLINK RLC PDU No LIs
6 UPLINK RLC PDU Check Lis and re-assembled SDU

Release 5 173 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a "Length
Indicator" indicating that the SDU exactly filled the previous UMD PDU, and a "Length Indicator" indicating that the
remainder of the PDU contains padding.
The length of the received SDU shall be UM_7_PayloadSize bytes, and the data content shall be the same as the first
UM_7_PayloadSize bytes of the transmitted SDU.
7.2.2.5 Reassembly / 7-bit "Length Indicators" / Invalid LI value
The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length
Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid
"Length Indicator" value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length
Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for
UMD PDUs in this version of the protocol, the Receiver shall:
- ignore that UMD PDU.
[...]
Length: 7 bits
Bit Description
1111101 Reserved (PDUs with this coding will be discarded by this version of the
protocol).
1111110 AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU.
UMD PDU: Reserved (PDUs with this coding will be discarded by this version of
the protocol).

Reference(s)
TS 25.322 clause 9.2.2.8 and 11.2.4.1.
To test that PDUs with invalid "Length indicator" '111 1110' are discarded by the receiving RLC.
Initial conditions
The radio bearer is placed into loop-back mode 1with the UL SDU size set to UM_7_PayloadSize +1 bytes.
Test procedure
a) The SS transmits two RLC SDUs of size UM_7_PayloadSize +1 bytes. In the third PDU for transmission, the
SS sets the value of the second (padding) LI to 1111110.
Release 5 174 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
b) The SS checks the "Length Indicator" sizes and values of any RLC PDUs returned on the uplink, and checks for
the presence of any received RLC SDUs.
Expected sequence
UE SS
3 DOWNLINK RLC PDU SDU 1 & SDU 2
4 DOWNLINK RLC PDU SDU 2 and invalid LI (=11111110)
5 UPLINK RLC PDU SDU 1
6 UPLINK RLC PDU SDU 1: Check Lis and re-assembled SDU

The UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The second shall have a
"Length Indicator" indicating the end of the SDU, and a padding "Length Indicator".
The length and data content of the received SDU shall be the same as the first transmitted SDU. The second SDU shall
not be returned.
7.2.2.6 Reassembly / 7-bit "Length Indicators" / LI value >PDU size
If the "Length Indicator" of an UMD PDU has a value that is larger than the PDU size RLC header size and is not one
of the predefined values listed in the table of TS 25.322 subclause 9.2.2.8, the Receiver shall:
- ignore the UMD PDU.
[...]
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:
- update VR(US) according to each received UMD PDU (see TS 25.322 subclause 9.4);
- if the updating step of VR(US) is not equal to one (i.e. one or more UMD PDUs are missing):
- discard the SDUs that have segments in the missing UMD PDUs.
Reference(s)
TS 25.322 clauses 11.2.4.2 and 11.2.3.
Release 5 175 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
To test that PDUs with "Length Indicators" that point beyond the end of the PDU are ignored by the receiving RLC
entity.
Initial conditions
The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_7_PayloadSize +1 bytes.
Test procedure
a) The SS transmits three RLC SDUs of size UM 7 PayloadSize +1 bytes. All the SDUs are concatenated or
segmented over successive RLC PDUs. In the third PDU for transmission, the SS sets value of the "Length
Indicator" to be UM_7_PayloadSize (decimal).
content of the received RLC SDUs (assuming a 7-bit "Length Indicator" size).
Expected sequence
UE SS
4 DOWNLINK RLC PDU SDU 2 & SDU 3, with bad LI
5 DOWNLINK RLC PDU SDU 3 and padding
7 UPLINK RLC PDU SDU 1 and padding: Check LIs and re-
assembled SDU

The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a LI
indicating the end of an SDU and an "Length Indicator" indicating that the remainder of the PDU contains padding.
The length and data content of the received SDU should be the same as the first transmitted SDU. No further SDUs or
PDUs should be received.
7.2.2.7 Reassembly / 7-bit "Length Indicators" / First data octet LI
indicators" are added to allow correct reconstruction of SDUs. A special "Length Indicator" is defined to indicate that
the start of an SDU is coincident with the start of the PDU. The special "Length Indicator"is needed to avoid discarding
Release 5 176 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
of an SDU when the first received PDU has a sequence number different from zero. Incorrect operation of
segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.
1. "Length Indicator" =1111100, UMD PDU: The first data octet in this RLC PDU is the first octet of a RLC SDU.
2. Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:
...
- if the special "Length Indicator" "1111 100" or "1111 1111 1111 100" is the first "Length Indicator" of a
UMD PDU received on the downlink:
- consider the first data octet in this UMD PDU as the first octet of an RLC SDU.
Reference(s)
1. TS 25.322 clause 9.2.2.8.
2. TS 25.322 clause 11.2.3.
To test that a UE in unacknowledged mode correctly handles a received RLC PDU with a 7-bit "Length Indicator"
having its value equal to the special "Length Indicator" value 1111100 when the sequence number of the first received
PDU is different from zero.
Initial conditions
Test procedure
a) The SS transmits a RLC SDU of size 12 bytes in a PDU which has the 'First Data Octet LI' as the first "Length
b) The SS waits until the SDU has been received back from the UE, and then transmits another SDU of 12 bytes in
a PDU which has the 'First Data Octet LI' as the first "Length Indicator" in the PDU.
c) The SS waits until this SDU has been received back from the UE.
Note: The SS sends PDUs in downlink starting at sequence number 10.
Release 5 177 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
2 DOWNLINK RLC PDU, SN 10 SDU 1 with LI =1111100
3 Wait for loopback
5 DOWNLINK RLC PDU, SN 11 SDU 2 with LI =1111100

1. The UE shall return two RLC PDUs.
2. The length and data content of each received SDU shall be the same as the transmitted SDU.
7.2.2.8 Segmentation and reassembly / 15-bit "Length Indicators" / Padding
The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length
A PDU that has unused space, to be referred to as padding, shall use a "Length Indicator" to indicate that this space is
used as padding unless the padding size is one octet for PDUs with 15-bit "Length Indicators". A padding "Length
Indicator" must be placed after any "Length Indicators" for a PU.
One "Length Indicator" field shall be included for each end of a SDU that the PDU includes. The "Length Indicator"
shall be set equal to the number of octets between the end of the header fields and the end of the segment. If padding is
needed, another "Length Indicator" field set to only 1's shall be added unless the padding size is one octet for PDUs
with 15-bit "Length Indicators".
Reference(s)
TS 25.322 clauses 9.2.2.8 and 11.2.2.1.
1. To test that the UE correctly segments a large SDU and padding is added at the end.
2. To test that the UE correctly deals with a 15-bit padding "Length Indicator" when present in a received PDU.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_15_PayloadSize +1 bytes.
Release 5 178 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
a) The SS transmits an RLC SDU of size UM_15_PayloadSize +1 bytes. The second of the 2 PDUs sent shall
contain a "Length Indicator" indicating the end of the SDU and the "Length Indicator" indicating that padding is
present.
b) The SS checks the "Length Indicator" values in the RLC PDU returned on the uplink, and checks the length and
Expected sequence
UE SS
3 DOWNLINK RLC PDU SDU 1 & Padding

1. The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a
"Length Indicator" indicating the PDU contains a SDU boundary after octet 1 of the data field, and the second
shall indicate that the remainder of the PDU contains padding.
2. The length and data content of the received SDU shall be the same as the transmitted SDU.
defined "Length Indicator" value is used to indicate when an SDUs ends coincident with the end of the previous PU.
communicate.
If the PDU is exactly filled with the last segment of a SDU and there is no room for an "Length Indicator" field, a
"Length Indicator" field set to all 0's shall be included as the first "Length Indicator" in the following PDU.
Reference(s)
TS 25.322 clause 11.2.2.1.
1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0's is placed by the transmitter as the
2. To test that where an SDU exactly fills a PDU, and an "Length Indicator" of all 0's is the first "Length Indicator"
in the next PDU, the receiver correctly reassembles the PDU.
Release 5 179 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize bytes.
Test procedure
a) The SS transmits an RLC SDU of size 2 * UM_15_PayloadSize bytes.
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=0 and padding
5 UPLINK RLC PDU No Lis

The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have an "Length
Indicators"indicating that the SDU exactly filled the previous UMD PDU, and a "Length Indicators" indicating that the
remainder of the PDU contains padding.
The length of the received SDU shall be UM_15_PayloadSize bytes, and the data content shall be the same as the first
UM_15_PayloadSize bytes of the transmitted SDU.
7.2.2.10 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short
LI
defined "Length Indicator" value is used to indicate when an SDUs ends one octet short of the end of the previous PDU.
communicate.
In the case where the last segment of an RLC SDU is one octet short of exactly filling the last RLC PDU, and 15-bit
"Length Indicators" are used, the next "Length Indicator" shall be placed as the first "Length Indicator" in the next PDU
and have value "Length Indicator"=111 1111 1111 1011.
Release 5 180 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
In the case where a PDU contains a 15-bit "Length Indicator" indicating that an SDU ends with one octet left in the
PDU, the last octet of this PDU shall be ignored and shall not be filled with the first octet of the next SDU data.
Reference(s)
TS 25.322 clause 9.2.2.8.
1. To test that where the UE transmits an SDU, which is one byte short of filling a PDU, an "Length Indicator"
indicating one byte short is placed as the first "Length Indicator" in the next PDU.
2. To test that where the UE correctly handles a received PDU containing an "Length Indicator" indicating that an
SDU ended one byte short of the end of the previous PDU.
Initial conditions
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS34.108) is executed, with all the parameters as
specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined for
UM 15-bit "Length Indicator" tests in clause 7.2.2.1.
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_15_PayloadSize - 1bytes.
Test procedure
a) The SS transmits an RLC SDU of size (2 * UM_15_PayloadSize) - 1 bytes.
b) The SS checks the "Length Indicator" sizes and values in the RLC PDUs returned on the uplink, and checks the
length and content of the received RLC SDU (assuming a 15-bit "Length Indicator" size).
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=111 1111 1111 1011 and padding

1. The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have 2
"Length Indicators". The first "Length Indicator"shall be a "Length Indicator" indicating that the SDU was one
byte short of filling the previous PDU, and the second shall be a "Length Indicator" indicating that the remainder
of the PDU contains padding.
2. The length of the received SDU shall be UM_15_PayloadSize - 1bytes, and the data content shall be the same as
the first UM_15_PayloadSize - 1 bytes of the transmitted SDU.
Release 5 181 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.2.11 Reassembly / 15-bit "Length Indicators" / Invalid LI value
Indicator" will result in failure of the UE to communicate.
Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for
UMD PDUs in this version of the protocol, the Receiver shall:
- ignore that UMD PDU.;
Length: 15bits
Bit Description
111111111111110 AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS
PDU. UMD PDU: Reserved (PDUs with this coding will be discarded by
this version of the protocol).

Reference(s)
TS 25.322 clause 11.2.4.1, 9.2.2.8.
To test that PDUs with invalid "Length Indicators" are discarded by the receiving RLC.
Initial conditions
The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize +1 bytes.
Test procedure
a) The SS transmits two RLC SDUs of size UM_15_PayloadSize +1 bytes. In the third PDU for transmission, the
SS sets the value of the second (padding) LI to 111111111111110.
b) The SS checks the "Length Indicator" sizes and values of any RLC PDUs returned on the uplink, and checks for
the presence of any received RLC SDUs.
Release 5 182 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
4 DOWNLINK RLC PDU SDU 2 and invalid LI (=111111111111110)
6 UPLINK RLC PDU SDU 1: Check Lis and re-assembled SDU

"Length Indicator" indicating the end of the SDU, and a padding "Length Indicator".
The length and data content of the received SDU shall be the same as the first transmitted SDU. The second SDU shall
not be returned.
"Length Indicator"value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length
If the "Length Indicator" of a PDU has a value that is larger than the PDU size the number of octets containing
"Length Indicators"in the PDU 1 and is not one of the predefined values listed in the table of 3GPP TS 25.322 clause
9.2.2.8, the PDU shall be discarded and treated as a missing PDU.
If a PDU with sequence number <VR(US) is missing then all SDUs that have segments in this PDU shall be discarded.
Reference(s)
TS 25.322 clauses 11.2.4.2 and 11.2.3.
To test that PDUs with "Length Indicators" that point beyond the end of the PDU are ignored by the receiving RLC
entity.
Initial conditions
The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize +1bytes.
Release 5 183 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
a) The SS transmits three RLC SDUs of size UM_15_PayloadSize +1 bytes. All the SDUs are concatenated or
Indicator" to be UM_15_PayloadSize +1 (decimal).
content of the received RLC SDUs (assuming a 15-bit "Length Indicator" size).
Expected sequence
UE SS
4 DOWNLINK RLC PDU SDU 2 & SDU 3, with bad LI
5 DOWNLINK RLC PDU SDU 3 and padding
7 UPLINK RLC PDU SDU 1 and padding: Check LIs and re-
assembled SDU

"Length Indicator" indicating the end of an SDU and a "Length Indicator" indicating that the remainder of the PDU
contains padding.
The length and data content of the received SDU shall be the same as the first transmitted SDU. No further SDUs or
PDUs shall be received.
7.2.2.13 Reassembly / 15-bit "Length Indicators" / First data octet LI
Indicators" are added to allow correct reconstruction of SDUs. A special LI is defined to indicate that the start of on
SDU is coincident with the start of the PDU. The special LI is needed to avoid discarding of an SDU when the first
received PDU has a sequence number different from zero. Incorrect operation of segmentation, concatenation, or coding
of "Length Indicators" will result in failure of the UE to communicate.
"Length Indicators" =111111111111100, UMD PDU: The first data octet in this RLC PDU is the first octet of a RLC
SDU.
Reference(s)
TS 25.322 clause 9.2.2.8.
To test that a UE in unacknowledged mode correctly handles a received RLC PDU with a 15-bit "Length Indicator"
having its value equal to the special LI value 111111111111100 when the sequence number of the first received PDU is
different from zero.
Release 5 184 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
Test procedure
a) The SS transmits a RLC SDU of size 150 bytes in a PDU which has the 'First Data Octet LI' as the first "Length
Indicator"in the PDU.
b) The SS waits until the SDU has been received back from the UE, and then transmits another SDU of 150 bytes
in a PDU which has the 'First Data Octet LI' as the first "Length Indicator"in the PDU.
c) The SS waits until this SDU has been received back from the UE.
Expected sequence
UE SS
2 DOWNLINK RLC PDU SDU 1 with LI =111111111111100
3 Wait for loopback
5 DOWNLINK RLC PDU SDU 2 with LI =111111111111100

1. The UE shall return two RLC PDUs.
2. The length and data content of each received SDU shall be the same as the transmitted SDU.
7.2.3 Acknowledged mode
7.2.3.1 General information for AM tests
Two generic Radio Access Bearers are provided for AM tests.
The AM test RAB is set up using the Generic Procedure described in clause 7.1.3 of TS 34.108, and with the default
RAB replaced as follows:
- For AM 7-bit "Length Indicator" tests: the RB configuration described in 3G TS 34.108 clause 6.11.3 is used.
For these tests, let AM_7_PayloadSize denote the RAB payload size in octets.
- For AM 15-bit "Length Indicator" tests: the RB configuration described in 3G TS 34.108 clause 6.11.4 is used.
For these tests, let AM_15_PayloadSize denote the RAB payload size in octets.
Release 5 185 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Unless specified in individual test cases, the default RLC settings are given in table 7.2/1.
Table 7.2/1: RLC Parameters for AM testing
Uplink RLC
Transmission RLC discard
Max DAT retransmissions
Max_DAT 4
Transmission window size 128
Timer_RST 500
Max_RST 4
Polling info
Timer_poll_prohibit disabled
Timer_poll disabled
Poll_PU disabled
Poll_SDU disabled
Last transmission PDU poll TRUE
Last retransmission PDU poll TRUE
Poll_Window disabled
Timer_poll_periodic disabled
Downlink RLC
In-sequence delivery TRUE
Receiving window size 128
Timer_Status_Prohibit disabled
Timer_EPC disabled
Missing PDU Indicator TRUE
Timer_STATUS_periodic disabled

The AM test RABs are used in all tests with the following exception:
- Tests that explicitly specify a different Radio Bearer configuration.
7.2.3.2 Segmentation and reassembly / Selection of 7 or 15 bit Length Indicators
The RLC segments and concatenates SDUs into PDUs according to the PDU size configured by RRC. "Length
Indicators" are added to allow correct reconstruction of SDUs. The selection of the size of the "Length Indicator" fields
used must follow the specified rules. Incorrect operation of segmentation, concatenation, or coding of "Length
Indicator" shall:
RLC SDU segment;
[...]
The size of the Length Indicator may be either 7 bits or 15 bits.
[...]
For AM:
- if the "AMD PDU size" is l26 octets:
Release 5 186 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- else:
- the size of the "Length Indicator" is always the same for all AMD PDUs, for one RLC entity.
Reference(s)
TS 25.322 clauses 9.2.2.8 and 9.2.2.9.
To test that if the configured AMD PDU size is l26 octets, 7 bit "Length Indicators" are used in transmitted AMD
PDUs, otherwise, 15 bit "Length Indicators" are used.
Initial conditions
for AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
Test procedure
a) The SS transmits an RLC SDU of size 10 bytes. The PDU carrying this SDU is transmitted with a poll for status.
b) The SS checks the "Length Indicator" values and SDU size and contents inthe RLC PDU returned on the uplink
c) The SS releases the RB.
The SS performs the Radio Bearer establishment procedure (clause 7.1.3 of TS 34.108) with all the parameters as
specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB
defined for AM 15-bit "Length Indicator" tests in clause 7.2.3.1.
The following RLC parameter values are used in place of the values in clause 7.2.3.1:
Uplink RLC
Downlink RLC

d) The SS transmits an RLC SDU of size 10 bytes. The PDU carrying this SDU is transmitted with a poll for status.
e) The SS checks the "Length Indicator" values and SDU size and contents in the RLC PDU returned on the uplink
Release 5 187 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 RB ESTABLISHMENT See generic procedures for AM 7 bit LIs
2 DOWNLINK RLC PDU 10 byte SDU +padding +poll
3 UPLINK RLC PDU 10 byte SDU +piggy-backed status +poll
3a STATUS PDU If piggy-backed status is not used in 3
4 STATUS PDU
5 RB RELEASE
6 RB ESTABLISHMENT See generic procedures for AM 15 bit LIs
(AMD PDU size >126 bytes)
7 DOWNLINK RLC PDU 10 byte SDU +padding +poll
8 UPLINK RLC PDU 10 byte SDU +piggy-backed status +poll
9 STATUS PDU

The UE shall send 7 bit "Length Indicators" with values that correctly indicate the end of SDU in step b).
The UE shall send 15 bit "Length Indicators" with values that correctly indicate the end of SDU in step e).
7.2.3.3 Segmentation and Reassembly / 7-bit "Length Indicators" / Padding or Piggy-
backed Status
The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. "Length
coding of length indicators will result in failure of the UE to communicate.
Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator"
shall:
RLC SDU segment;
Predefined values of the "Length Indicator" are used to indicate padding. The values that are reserved for special
purposes are listed in the tables below depending on the size of the "Length Indicator". Only predefined "Length
Indicator" values can refer to the padding space. These values shall only be placed after all other "Length Indicators" for
a PDU.
STATUS PDUs can be piggybacked on the AMD PDU by using part or all of the padding space. A predefined "Length
Indicator" shall be used to indicate the presence of a piggybacked STATUS PDU. This "Length Indicator" replaces the
padding "Length Indicator". The piggybacked STATUS PDU shall be appended immediately following the PDU data.
When only part of the padding space is used, the end of the piggybacked STATUS PDU is indicated by one of the SUFI
fields NO_MORE or ACK. Thus no additional "Length Indicator" is required to show that there is still padding in the
AMD PDU.
[]
Release 5 188 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Sender shall:
- when RLC SDUs are received from upper layers:
- segment the RLC SDUs into AMD PDUs where the fixed PDU size is configured by upper layer;
- set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8;
[]
The Receiver may:
- if STATUS PDU(s) to be sent fit into padding octets in AMD PDU(s) to be sent:
- piggyback a STATUS PDU on the AMD PDU to be sent.
Submission of a piggybacked STATUS PDU in an AMD PDU to the lower layer follows the same rules as an ordinary
STATUS PDU.
Reference(s)
TS 25.322 clauses 9.2.2.8, 11.3.2 and 11.5.2.1.
1. To test that a large SDU is correctly segmented and padding added at the end.
2. To test that a large SDU is received correctly, whether or not it has piggy-backed status at the end.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize +1 bytes.
Test procedure
a) The SS transmits an RLC SDU (SDU1) of size AM_7_PayloadSize +1bytes, and polls the receiver for status.
c) The SS transmits another RLC SDU (SDU2) of size AM_7_PayloadSize +1 bytes, and includes piggy-backed
status in the second of the 2 PDUs sent. The SS also polls the receiver for status.
d) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and
e) The SS may optionally release the radio bearer.
Release 5 189 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
3 DOWNLINK RLC PDU SDU 1 +poll +Padding
5 UPLINK RLC PDU Poll, Check LIs and re-assembled SDU
7 DOWNLINK RLC PDU SDU 2 +poll +piggy-backed status
10 STATUS PDU

1. In steps 4 and 5, the UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second
shall have a "Length Indicator"indicating the PDU contains an SDU boundary after octet 1 of the data field, and
the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-
backed status PDU.
2. In steps 8 and 9, the UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second
shall have a "Length Indicator"indicating the PDU contains an SDU boundary after octet 1 of the data field, and
the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-
backed status PDU.
3. The length and data content of all received SDUs shall be the same as the transmitted SDUs.
The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. A pre-
defined "Length Indicator" value is used to indicate when an SDUs ends coincident with the end of the previous PDU.
communicate.
Indicator" shall:
RLC SDU segment;
[...]
In the case where the end of the last segment of an RLC SDU exactly ends at the end of a PDU and there is no "Length
Indicator" that indicates the end of the RLC SDU:
- if 7-bit "Length Indicator" is used:
Release 5 190 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- a "Length Indicator" with value "000 0000" shall be placed as the first "Length Indicator" in the following
PDU;
[...]
For UM and AM RLC:
[...]
STATUS PDUs can be piggybacked on the AMD PDU by using part or all of the padding space. A predefined "Length
Indicator" shall be used to indicate the presence of a piggybacked STATUS PDU. This "Length Indicator" replaces the
padding "Length Indicator". The piggybacked STATUS PDU shall be appended immediately following the PDU data.
When only part of the padding space is used, the end of the piggybacked STATUS PDU is indicated by one of the SUFI
fields NO_MORE or ACK. Thus no additional "Length Indicator" is required to show that there is still padding in the
AMD PDU.
Reference(s)
TS 25.322 clause 9.2.2.8 and 11.3.2.1.
1. To test that where an SDU exactly fills a PDU, an "Length Indicator" of all 0's is placed by the transmitter as the
first "Length Indicator"in the next PDU.
2. To test that where an SDU exactly fills a PDU, and an "Length Indicator"of all 0's is the first "Length
Indicator"in the next PDU, the receiver correctly reassembles the SDU.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize bytes.
Test procedure
a) The SS transmits an RLC SDU of size 2 * AM_7_PayloadSize bytes. The SS polls the receiver for status in the
last RLC PDU sent.
b) The SS checks the "Length Indicator" sizes and values in the RLC PDUs returned on the uplink, and checks the
Release 5 191 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=0, poll and padding
6 UPLINK RLC PDU (Poll) Check Lis and re-assembled SDU
7 STATUS PDU

"Length Indicator" indicating that the SDU exactly filled the previous PDU, and a "Length Indicator" indicating either
that the remainder of the PDU contains padding, or that it contains a piggy-backed STATUS PDU.
The length of the received SDU shall be AM_7_PayloadSize bytes, and the data content shall be the same as the first
AM_7_PayloadSize bytes of the transmitted SDU.
7.2.3.5 Reassembly / 7-bit "Length Indicators" / Reserved LI value
Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of a reserved
"Length Indicator" value is specified in the conformance requirement below. Incorrect operation of segmentation,
concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.
Upon delivery by the lower layer of an AMD PDU that contains a "Length Indicator" value specified to be reserved for
AMD PDUs in this version of the protocol, the Receiver shall:
- ignore that AMD PDU.
[...]
Length: 7 bits
Bit Description
1111100 UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC
SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this
version of the protocol).
1111101 Reserved (PDUs with this coding will be discarded by this version of the
protocol).

Reference(s)
TS 25.322 clause 9.2.2.8 and 11.3.4.6.
To test that PDUs with reserved "Length Indicators" are discarded by the receiving RLC.
Release 5 192 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
for AM 7-bit "Length Indicators" tests in clause 7.2.3.1.
Downlink RLC
Missing PDU Indicator FALSE

Test procedure
a) The SS transmits three concatenated RLC SDUs of size AM_7_PayloadSize +1 bytes. In the second PDU, the
SS sets the value of the first "Length Indicator"to correctly indicate the end of SDU1 and adds a second
erroneous "Length Indicator"with value 1111100. In the third PDU for transmission, the SS sets the value of the
"Length Indicator" to 1111101.
b) The SS waits to receive a status report from the UE.
Expected sequence
UE SS
2 DOWNLINK RLC PDU #0 SDU 1
3 DOWNLINK RLC PDU #1 SDU 1 +SDU 2, good LI, LI =1111100
4 DOWNLINK RLC PDU #2 SDU 2 +SDU 3, LI =1111101
5 DOWNLINK RLC PDU #3 SDU 3 +poll
6 STATUS PDU Nack PDUs 1 and 2

1. The UE shall return a STATUS PDU indicating that PDUs with sequence numbers 1 and 2 were not received.
"Length Indicator" value where the value is too large is specified in the conformance requirement below. Incorrect
operation of segmentation, concatenation, or coding of "Length Indicator" will result in failure of the UE to
communicate.
If the "Length Indicator" of an AMD PDU has a value that is larger than the PDU size RLC header size and is not one
of the predefined values listed in the table of subclause 9.2.2.8, the Sender shall:
Release 5 193 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- ignore that AMD PDU.
Reference(s)
TS 25.322 clause 11.3.4.5.
To test that PDUs with "Length Indicators" that point beyond the end of the PDU are discarded by the receiving RLC.
Initial conditions
Downlink RLC

Test procedure
a) The SS transmits three RLC SDUs of size AM_7_PayloadSize +1bytes. All the SDUs are concatenated or
Indicator" to be AM_7_PayloadSize (decimal).
b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the content of
the received STATUS PDU (assuming a 7-bit "Length Indicator" size).
Expected sequence
UE SS
3 DOWNLINK RLC PDU #1 SDU 1 & SDU 2
4 DOWNLINK RLC PDU #2 SDU 2 & SDU 3, with bad LI
5 DOWNLINK RLC PDU #3 SDU 3, poll and padding
6 STATUS PDU Nack PDU #2

The UE shall return a STATUS PDU indicating that the PDU with sequence number 2 was not received.
Release 5 194 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.3.7 Segmentation and Reassembly / 15-bit "Length Indicators" / Padding or
Piggy-backed Status
The "Length Indicator" is used to indicate, each time, the end of an SDU occurs in the PU. The "Length Indicator"
points out the number of octets between the end of the last "Length Indicator" field and up to and including the octet at
the end of an SDU segment
A PDU that has unused space, to be referred to as padding, shall use a "Length Indicator" to indicate that this space is
used as padding unless the padding size is one octet for PDUs with 15-bit LIs. A padding "Length Indicator" must be
placed after any "Length Indicators" for a PDU.
Upon reception of a SDU, RLC shall segment the SDU to fit into the fixed size of a PDU. The segments are inserted in
the data field of a PDU. A "Length Indicator" shall be added to each PDU that includes a border of an SDU, i.e. if a
PDU does not contain a "Length Indicator", the SDU continues in the next PDU. The length indicator indicates where
the border occurs in the PDU. The data after the indicated border can be either a new SDU, padding or piggybacked
information. If padding or piggybacking is added another "Length Indicator" shall be added unless the padding size is
one octet for PDUs with 15-bit "Length Indicators", see clauses 9.2.2.8 and 9.2.2.9.
Reference(s)
TS 25.322 clauses 9.2.2.8 and 11.3.2.1.2.
1. To test that a large SDU is correctly segmented and padding added at the end.
2. To test that a large SDU is received correctly, whether or not it has piggy-backed status at the end.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to AM_15_PayloadSize +1bytes.
Test procedure
a) The SS transmits an RLC SDU (SDU1) of size AM_15_PayloadSize +1 bytes, and polls the receiver for status.
b) The SS checks the "Length Indicator" values in the RLC PDU returned on the uplink, and checks the length and
c) The SS transmits another RLC SDU (SDU2) of size AM_15_PayloadSize +1 bytes, and includes piggy-backed
status in the second of the 2 PDUs sent. The SS also polls the receiver for status.
d) The SS checks the "Length Indicator" sizes and values in the RLC PDUs returned on the uplink, and checks the
Release 5 195 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
3 DOWNLINK RLC PDU SDU 1 +poll +Padding
7 DOWNLINK RLC PDU SDU 2 +poll +piggy-backed status
10 STATUS PDU

1. In steps 4 and 5, the UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The
second shall have a "Length Indicator"indicating the PDU contains an SDU boundary after octet 1 of the data
field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a
piggy-backed status PDU.
2. In steps 8 and 9, the UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The
second shall have a "Length Indicator"indicating the PDU contains an SDU boundary after octet 1 of the data
field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a
piggy-backed status PDU.
3. The length and data content of all received SDUs shall be the same as the transmitted SDUs.
defined "Length Indicator" value is used to indicate when an SDUs ends coincident with the end of the previous PU.
communicate.
If the PDU is exactly filled with the last segment of a SDU and there is no room for a "Length Indicator" field, a
"Length Indicator" field set to only 0's shall be included as the first "Length Indicator" in the following PDU.
Reference(s)
TS 25.322 clause 11.3.2.1.
1. To test that where an SDU exactly fills a PDU, a "Length Indicator" of all 0's is placed by the transmitter as the
2. To test that where an SDU exactly fills a PDU, and a "Length Indicator" of all 0's is the first "Length Indicator"
in the next PDU, the receiver correctly reassembles the SDU.
Release 5 196 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to AM_15_PayloadSize bytes.
Test procedure
a) The SS transmits an RLC SDU of size 2 * AM_15_PayloadSize bytes. The SS polls the receiver for status in the
last RLC PDU sent.
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=0, poll and padding
6 UPLINK RLC PDU (Poll) Check Lis and re-assembled SDU
7 STATUS PDU

The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have a "Length
Indicator" indicating that the SDU exactly filled the previous PDU, and a "Length Indicator" indicating either that the
remainder of the PDU contains padding, or that it contains a piggy-backed STATUS PDU.
The length of the received SDU shall be AM_15_PayloadSize bytes, and the data content shall be the same as the first
AM_15_PayloadSize bytes of the transmitted SDU.
7.2.3.9 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short
LI
defined "Length Indicator" value is used to indicate when an SDUs ends one octet short of the end of the previous PU.
communicate.
Release 5 197 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
In the case where the last segment of an RLC SDU is one octet short of exactly filling the last RLC PU, and 15-bit
"Length Indicators" are used, the next "Length Indicator" shall be placed as the first "Length Indicator" in the next PDU
and have value "Length Indicator"=111 1111 1111 1011.
In the case where a PDU contains a 15-bit "Length Indicator" indicating that an SDU ends with one octet left in the
PDU, the last octet of this PDU shall be ignored and shall not be filled with the first octet of the next SDU data.
Reference(s)
TS 25.322 clause 9.2.2.8.
1. To test that where the UE transmits an SDU, which is one byte short of filling a PDU, a "Length Indicator"
indicating one byte short is placed as the first "Length Indicator"in the next PDU.
2. To test that where the UE correctly handles a received PDU containing a "Length Indicator" indicating that an
SDU ended one byte short of the end of the previous PDU.
Initial conditions
The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to AM_15_PayloadSize 1bytes.
Test procedure
a) The SS transmits an RLC SDU of size (2 * AM_15_PayloadSize) - 1 bytes. The SS polls the receiver for status
in the last RLC PDU sent.
b) The SS checks the "Length Indicator" values of the RLC PDUs returned on the uplink, and checks the length and
Expected sequence
UE SS
4 DOWNLINK RLC PDU LI=111 1111 1111 1011, poll and padding
6 UPLINK RLC PDU (Poll) Check LIs and re-assembled SDU
7 STATUS PDU

Release 5 198 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1. The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have 2
"Length Indicators". The first "Length Indicator"shall be an "Length Indicator" indicating that the SDU was one
byte short of filling the previous PDU, and the second shall be a "Length Indicator" indicating that the remainder
of the PDU contains padding.
2. The length of the received SDU shall be AM_15_PayloadSize - 1 bytes, and the data content shall be the same as
the first AM_15_PayloadSize - 1 bytes of the transmitted SDU.
7.2.3.10 Reassembly / 15-bit "Length Indicators" / Reserved LI value
The RLC segments and concatenates SDUs into AMD PDU according to the PDU size configured by RRC. "Length
Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of a reserved LI
value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will
result in failure of the UE to communicate.
Upon reception of an AMD PDU that contains "Length Indicator" value "111111111111100" or "111111111111101":
PDUs with this coding will be discarded by this version of the protocol.
Reference(s)
TS 25.322 clause 9.2.2.8.
To test that PDUs with reserved "Length Indicators" are discarded by the receiving RLC.
Initial conditions
Downlink RLC

Test procedure
a) The SS transmits three RLC SDUs of size AM_15_PayloadSize +1 bytes. In the second PDU, the SS sets the
value of the "Length Indicator" to 111111111111100. In the third PDU for transmission, the SS sets the value of
the second (padding) "Length Indicator" to 111111111111101.
b) The SS waits to receive a status report from the UE.
Release 5 199 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
3 DOWNLINK RLC PDU #1 SDU 1 +SDU 2, LI =111111111111100
4 DOWNLINK RLC PDU #2 SDU 2+SDU 3, LI =111111111111101
5 DOWNLINK RLC PDU #3 SDU 3 +poll
6 STATUS PDU Nack PDUs 1 and 2

1. The UE shall return a STATUS PDU indicating that PDUs with sequence numbers 1 and 2 were incorrectly
received.
2. No uplink SDUs shall be received.
The RLC segments and concatenates SDUs into PDUs according to the PDU size configured by RRC. "Length
Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid LI
value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will
result in failure of the UE to communicate.
If the "Length Indicator" of a PDU has a value that is larger than the PDU size the number of octets containing
"Length Indicators" in the PDU 1 and is not one of the predefined values listed in the table of 3GPP TS 25.322 clause
9.2.2.8, the PDU shall be discarded and treated as a missing PDU.
Reference(s)
TS 25.322 clause 11.3.4.5.
To test that PDUs with "Length Indicators" that point beyond the end of the PDU are discarded by the receiving RLC.
Initial conditions
Downlink RLC

Release 5 200 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
a) The SS transmits three RLC SDUs of size AM_15_PayloadSize +1 bytes. All the SDUs are concatenated or
Indicators" to be AM_15_PayloadSize +1 (decimal).
b) The SS checks the "Length Indicator" values of the RLC PDUs returned on the uplink, and checks the content of
the received STATUS PDUs (assuming a 15-bit "Length Indicator" size).
Expected sequence
UE SS
3 DOWNLINK RLC PDU #1 SDU 1 & SDU 2
4 DOWNLINK RLC PDU #2 SDU 2 & SDU 3, with bad LI
5 DOWNLINK RLC PDU #4 SDU 3, poll and padding
6 STATUS PDU Nack PDU #2

The UE shall indicate that the PDU with sequence number 2 was not received.
7.2.3.12 Correct use of Sequence Numbering
Peer RLC entities use sequence numbering to detect missing PDUs, and for flow control purposes. Incorrect operation
of sequence numbering will result in failure of the UE to communicate.
This sub-clause describes the state variables used in AM and UM in order to specify the peer-to-peer protocol. All state
variables are non-negative integers. UMD and AMD PDUs are numbered by modulo integer sequence numbers (SN)
cycling through the field: 0 to 2
12
1 for AM . All arithmetic operations contained in the present document on
VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) are affected by the AM modulus. . When performing
arithmetic comparisons of state variables or Sequence number values a modulus base shall be used. This modulus base
is subtracted (within the appropriate field) from all the values involved and then an absolute comparison is performed.
At the Sender, VT(A) shall be assumed to be the modulus base in AM . At the Receiver, VR(R) shall be
assumed to be the modulus base in AM .
The RLC shall maintain the following state variables in the Sender.
a) VT(S) - Send state variable.
This state variable contains the "Sequence Number" of the next AMD PDU to be transmitted for the first time
(i.e. excluding retransmitted PDUs). It shall be updated after the aforementioned AMD PDU is transmitted or
after transmission of a MRW SUFI which includes SN_MRW
LENGTH
>VT(S) (see subclause 11.6). The initial
value of this variable is 0.
[...]
If the AMD PDU is transmitted for the first time, the Sender shall:
- set the "Sequence Number" field equal to VT(S);
Release 5 201 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference(s)
TS 25.322, clauses 9.4 and 11.3.2.1.
1. To verify that the UE transmits the first PDU with the Sequence Number field equal to 0.
2. To verify that the UE increments the Sequence Number field according to the number of PDUs transmitted.
3. To verify that the UE wraps the Sequence Number after transmitting the 2
12
-1th PDU.
4. To verify that the UE receiver accepts PDUs with SNs that wrap around every 2
12
-1th PDU.
Initial conditions
AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
Uplink RLC
Polling info
Poll_PDU 64
Downlink RLC

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) - 1 bytes.
Test procedure
a) The SS sends 2049 RLC SDUs to the UE, each of (2 * AM_7_PayloadSize) - 1 bytes. The SS polls for status on
each 64
th
RLC PDU and the last PDU transmitted
b) When the SS received an uplink PDU with the P bit set to 1, the SS transmits a STATUS PDU acknowledging
all the RLC PDUs received so far.
c) The SS checks the sequence numbers of the RLC PDUs it receives in the uplink
d) The SS checks the content of the SDUs it receives from the UE.
Release 5 202 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
2 DOWNLINK RLC PDU #1
Transmission of DOWNLINK PDUs
continues
4 UPLINK RLC PDU#1 SN should be set to 0
continues to SN =63
6 DOWNLINK RLC PDU #64 Poll
7 UPLINK STATUS PDU
continues, polling every 64
th
PDU, to
SN =4094
9 DOWNLINK RLC PDU #4097 SN=0
10 DOWNLINK RLC PDU #4098 SN=1, Poll
10a UPLINK RLC PDUs UE transmission of UPLINK RLC PDUs
continues, polling every 64
th
PDU, to
SN=4094.
On poll, SS acknowledge all received PDUs.
10b Void
10c UPLINK RLC PDU#4096 SN =4095, Poll (cause: Poll_PDU=64)
10d STATUS PDU ACK SN up to 4095
10e Void
11 Void
13 UPLINK RLC PDU#4098 SN should be set to 1, Poll
14 DOWNLINK STATUS PDU
NOTE: The Expected Sequence shown is infomative.

1. The first PDU received shall have the SN field set to 0. The second PDU shall have the SN field set to 1, and the
4 097
th
PDU shall have the SN field set to 0.
2. The size and data content of the received SDUs shall match those of the transmitted SDUs.
7.2.3.13 Control of Transmit Window
This test is to check that the UE is able to correctly control its RLC transmission window. Correct operation of RLC
windowing is critical for acknowledged mode operation.
VT(MS) - Maximum Send state variable.
This state variable contains the "Sequence Number" of the first AMD PDU that can be rejected by the peer Receiver,
VT(MS) =VT(A) +VT(WS). This value represents the upper edge of the transmission window. The transmitter shall
not transmit AMD PDUs with "Sequence Number"VT(MS) unless VT(S) VT(MS). In that case, the AMD PDU
with "Sequence Number" =VT(S) - 1 can also be transmitted. VT(MS) shall be updated when VT(A) or VT(WS) is
updated.
The initial value of this variable is Configured_Tx_Window_size.
Release 5 203 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
... The receiver is always allowed to change the Tx window size of the peer entity during a connection, but the
minimum and the maximum allowed value is given by RRC configuration. The Rx window of the receiver is not
changed.
Reference(s)
TS 25.322, clauses 9.2.2.11.3 and 9.4.
To verify that the UE does not transmit PDUs with sequence numbers outside of the transmit window, except the PDU
with SN=VT(S)-1, even when the transmit window size is changed by the receiver.
Initial conditions
Uplink RLC First run Second run
Transmission window size 8 128

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize - 1 bytes.
Related IXIT statement
UE support for either RLC SDU Buffering OR RLC SDU Discard.
Test procedure
Let W be the size of the transmit window.
The length of all transmitted SDUs is set to AM_7_PayloadSize - 1 bytes.
a) The SS transmits W+1 RLC SDUs to the UE.
b) The SS checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or
transmit STATUS PDUs for any other reason.
c) After confirming that the UE has stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS
transmits a STATUS PDU acknowledging all the RLC PDUs received so far. The SS transmits W+1 additional
RLC SDUs to the UE.
d) The SS again checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or
transmit further STATUS PDUs for any other reason.
e) After confirming that the UE has again stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS
transmits a STATUS PDU acknowledging all the RLC PDUs received so far, and containing a WINDOW
command to reduce the UE transmit window size (W) to half its initial size. The SS transmits W/2+1 additional
RLC SDUs to the UE (where W is the original window size).
f) The SS checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or
transmit STATUS PDUs for any other reason.
Release 5 204 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
g) After confirming that the UE has stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS
transmits a STATUS PDU acknowledging all the RLC PDUs received so far. The SS transmits W/2+1 additional
RLC SDUs to the UE (where W is the original window size).
h) The SS checks the RLC SDUs received on the uplink.
i) The SS may optionally release the radio bearer.
NOTE: Window arithmetic is carried out modulo 4096.
The test procedure is run with the window transmit window size set to the default (8), and the repeated with the transmit
window size set to 128.
Release 5 205 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

6

SS continues to transmit RLC SDUs

7 DOWNLINK RLC PDU SDU W+1


10

SS continues to receive RLC SDUs

11 UPLINK RLC PDU SDU W +poll

12

No new transmissions from UE

13 STATUS PDU
13a DOWNLINK RLC PDUs SDU W+2
13b SS continues to transmit RLC SDUs
13c DOWNLINK RLC PDUs SDU 2W+2
14 UPLINK RLC PDU SDU W+1 (SDU buffered), or W+2 (SDU
W+1 discarded, see note 3)
15 UPLINK RLC PDU Next SDU

16


17 UPLINK RLC PDU SDU 2W+poll (SDU buffered), or SDU
2W+1+poll (SDU W+1 discarded, see note
3)

18


19 STATUS PDU WINDOW =W/2
19a DOWNLINK RLC PDUs SDU 2W+3
19c DOWNLINK RLC PDUs SDU 2W +W/2 +3
20 UPLINK RLC PDU SDU 2W+1 (SDU buffered), or 2W+3 (SDU
2W+2 discarded, see note 3)

22


23 UPLINK RLC PDU SDU 2W+W/2+poll (SDU buffered), or SDU
2W+W/2+2+poll (SDU 2W+2 discarded, see
note 3)

24


25 STATUS PDU
25a DOWNLINK RLC PDUs SDU 2W +W/2 +4
25c DOWNLINK RLC PDUs SDU 3W +4
26 UPLINK RLC PDU SDU 2W+W/2+1 (SDU buffered), or
2W+W/2+4 (SDU 2W+W/2+3 discarded, see
note 3)

28


Release 5 206 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
29 UPLINK RLC PDU SDU 3W+poll (SDU buffered), or SDU
3W+3+poll (SDU 2W+W/2+3 discarded, see
note 3)
NOTE 2: The polls in step 11, 17, 23 and 29 are transmitted as the last PDU in buffer trigger is set to
TRUE and the transmitted PDU is the last PDU in the transmitter window, see TS 25.322 clause
9.7.1.
NOTE 3: TS 25.322 does not specify the UE behaviour when transmission buffer is full. Thus, depending
on UE implementation, the uplink AM entity may or may not discard AM RLC PDUs received
from upper layer (e.g. from UE test loop function) when transmission buffer is full. The SS need
to take this into consideration when comparing SS sent SDUs in downlink with the UE returned
SDUs in uplink.

From steps 8 to 11, the SDU contents reassembled from the uplink shall match those of the first W transmitted SDUs.
At step 12 there shall be no further transmission on the uplink DTCH whilst the SS is waiting, except for any repeats of
SDUs from 1 to W.
After step 13, the UE shall resume transmission of the next W SDUs. The contents of these SDUs shall match those of
SDUs W+1 to 2*W (SDU buffered, see note 3), or W+2 to 2*W+1 (SDU W+1 discarded, see note 3), sent on the
downlink.
SDUs from W+1 to 2*W or W+2 to 2*W+1.
After step 19, the UE shall resume transmission of the next W/2 SDUs. The contents of these SDUs shall match those of
SDUs 2*W+1 to 2*W+W/2 (SDU buffered, see note 3), or 2*W+3 to 2*W+W/2+2 (SDU 2W+2 discarded, see note 3),
sent on the downlink.
SDUs from 2*W+1 to 2*W+W/2 or 2*W+3 to 2*W+W/2+2.
After step 25, the UE shall resume transmission of the next W/2 SDUs. The contents of these SDUs shall match those of
SDUs 2*W+W/2+1 to 3*W (SDU buffered, see note 3), or 2*W+W/2+4 to 3*W+3 (SDU 2W+W/2+3 discarded, see
note 3), sent on the downlink.
7.2.3.14 Control of Receive Window
This test is to check that the UE is able to correctly control its RLC receive window. Correct operation of RLC
windowing is critical for acknowledged mode operation.
This test applies to all UE.
Upon reception of an AMD PDU with "Sequence Number" outside the interval VR(R)SN<VR(MR), the Receiver
shall:
- discard the AMD PDU;
- if the "polling bit" in the discarded AMD PDU is set to "1":
- initiate the STATUS PDU transfer procedure.
Release 5 207 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference(s)
TS 25.322, clause 11.3.4.2.
To verify that the UE discards PDUs with sequence numbers outside the upper boundary of the receive window.
Initial conditions
Downlink RLC
Missing PDU Indicator FALSE FALSE
Receiving window size 8 128

Test procedure
Let W be the size of the receive window.
The length of all transmitted SDUs is set to AM_7_PayloadSize - 1 bytes.
a) The SS transmits W RLC SDUs to the UE, polling only on the last RLC PDU.
b) The SS checks the RLC SDUs received on the uplink, responding to poll requests with acknowledgements. Then
after receiving the STATUS PDU from the UE it transmits a further RLC SDU with the poll bit set. The SS sets
the sequence number for the associated RLC PDU above the top of the receive window, for example, 2*W.
c) The SS receives a STATUS PDU from the UE.
d) The SS transmits a further RLC SDU with the sequence number set to the value of the next sequence number
within the receive window.
e) The SS checks the RLC SDUs received on the uplink.
This test case is run once for the default receive window size (8) and again with the receive window size set to 128.
Release 5 208 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
2 DOWNLINK RLC PDU SDU 1, SN =0
3 DOWNLINK RLC PDU SDU 2, SN =1

4


5 DOWNLINK RLC PDU SDU W +Poll, SN =W-1
6 STATUS PDU

9

UE continues to transmit RLC SDUs

10 UPLINK RLC PDU SDU W, Poll
10a STATUS PDU
11 DOWNLINK RLC PDU SDU W+1, SN =2W, Poll
11a STATUS PDU
12 DOWNLINK RLC PDU SDU W+2, SN =W
13 UPLINK RLC PDU SDU W+2

1. The SS shall receive back SDUs 1 to W, and SDU W +2 only. No other SDUs shall be looped back.
2. The SS shall receive a STATUS PDU in step 11a. SN=2W shall not be indicated as received in the STATUS
PDU. Negative acknowledgements shall not be indicated for SN=W to 2W-1 either.
7.2.3.15 Polling for status / Last PDU in transmission queue
This case tests that the UE will poll for a status request on the last PDU in its transmission queue when that mode is
enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.
Last PDU in buffer.
When an AMD PDU to be transmitted for the first time is submitted to lower layer, the Sender shall:
- if the AMD PDU is the last AMD PDU scheduled for transmission according to subclause 11.3.2 (i.e. no data
received from upper layer remains to be segmented into AMD PDUs); or
- if the AMD PDU is the last AMD PDU that is allowed to transmit according to subclause 11.3.2.2:
- trigger a poll for this AMD PDU
....
- AMD PDUs are only allowed to transmit:
- if the AMD PDU has a "Sequence Number" <VT(MS); or
- if the AMD PDU has a "Sequence Number" equal to VT(S)-1; and
Release 5 209 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- if the AMD PDU is not restricted to be transmitted by the local suspend function, see 3GPP TS 25.322
subclause 9.7.5.
...
The Sender shall:
- if a poll has been triggered by one or several poll triggers (see 3GPP TS 25.322 subclause 9.7.1):
- if polling is not prohibited, see subclause 9.5:
- set the "Polling bit" in the AMD PDU header to "1";
- otherwise:
- set the "Polling bit" in the AMD PDU header to "0".
Reference
TS 25.322 clause 11.3.2.1.1, 9.7.1 and 11.3.2.
1. To verify that a poll is performed when only one PDU is available for transmission, and the poll prohibit timer
function is not used.
2. To verify that a poll is performed when only one PDU is available for transmission, and the poll prohibit timer
function is used, but inactive.
Initial conditions
Polling info
Timer_poll_prohibit disabled 200
Last transmission PDU poll TRUE TRUE
Last retransmission PDU poll FALSE FALSE

Test procedure
a) The SS transmits an RLC SDU of length (4 * AM_7_PayloadSize) - 1bytes to the UE.
b) The SS checks the uplink RLC PDUs for a poll for status flag.
The test is repeated using the RLC parameters given in the Second run column of the configuration table for the initial
conditions.
Release 5 210 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
5 DOWNLINK RLC PDU SDU 1 +Poll
6 STATUS PDU
8 UPLINK RLC PDU SDU 1 +Poll
9 STATUS PDU

The Poll bit shall be set in the AMD PDU header of the PDU returned in step 8. The poll bit shall not be set in the AMD
PDU header of other PDUs.
7.2.3.16 Polling for status / Last PDU in retransmission queue
This case tests that the UE will poll for a status request on the last PDU in its retransmission queue when that mode is
enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.
Last PDU in Retransmission buffer.
When a retransmitted AMD PDU is submitted to lower layer, the Sender shall:
- if the AMD PDU is the last AMD PDU scheduled for retransmission according to subclause 11.3.2; or
- if the AMD PDU is the last of the AMD PDUs scheduled for retransmission that are allowed to transmit
according to subclause 11.3.2.2:
- trigger a poll for this AMD PDU
....
- AMD PDUs are only allowed to transmit:
- if the AMD PDU has a "Sequence Number" <VT(MS); or
- if the AMD PDU has a "Sequence Number" equal to VT(S)-1; and
- if the AMD PDU is not restricted to be transmitted by the local suspend function, see 3GPP TS 25.322
subclause 9.7.5.
...
The Sender shall:
- if a poll has been triggered by one or several poll triggers (see 3GPP TS 25.322 subclause 9.7.1):
Release 5 211 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- otherwise:
Reference
25.322 clause 11.3.2.1.1, 9.7.1 and 11.3.2.
1. To verify that a poll is performed when only one PDU is available for retransmission, and the poll prohibit timer
function is not used.
2. To verify that a poll is performed when only one PDU is available for retransmission, and the poll prohibit timer
function is used, but inactive.
Initial conditions
Polling info
Timer_poll_prohibit disabled 200
Last transmission PDU poll FALSE FALSE
Last retransmission PDU poll TRUE TRUE

Test procedure
a) The SS transmits an RLC SDU of length (4 * AM_7_PayloadSize) - 1 bytes to the UE.
b) The SS checks the uplink RLC PDUs for a poll for status flag.
c) The SS transmits a STATUS PDU negatively acknowledging the first uplink RLC PDU as missing.
d) The SS waits for the RLC PDU to be retransmitted and then checks the uplink RLC PDU for a poll for status
flag.
The test is repeated using the RLC parameters given in the Second run column of the configuration table for the initial
conditions.
Release 5 212 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
5 DOWNLINK RLC PDU SDU 1 +Poll
6 STATUS PDU
7 UPLINK RLC PDU SDU 1, SN=0
9 STATUS PDU NAK: SN=0

10

Wait for retransmission
11 UPLINK RLC PDU SDU 1, SN=0 +Poll
12 STATUS PDU

The Poll bit shall be set in the AMD PDU header of the PDU returned in step 11. The poll bit shall not be set in the
AMD PDU header of other PDUs.
7.2.3.17 Polling for status / Poll every Poll_PDU PDUs
This case tests that the UE will poll for a status request every Poll_PDU PDUs when that mode is enabled. Incorrect
operation of polling will cause degradation of service, or at worst service failure.
VT(PDU).
This state variable is used when the "poll every Poll_PDU PDU" polling trigger is configured. It shall be
incremented by 1 for each AMD PDU that is transmitted including both new and retransmitted AMD PDUs.
When it becomes equal to the value Poll_PDU, a new poll shall be transmitted and the state variable shall be set
to zero.
The initial value of this variable is 0.
Poll_PDU.
This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling
every Poll_PDU PDU" is configured by upper layers. It represents the upper limit for the state variable
VT(PDU). When VT(PDU) equals the value Poll_PDU a poll shall be transmitted to the peer entity.
Every Poll_PDU PDU.
The Sender triggers the Polling function for every Poll_PDU PDU. Both retransmitted and new AMD PDUs
shall be counted.
The Sender shall:
- if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):
Release 5 213 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- otherwise:
Reference
TS 25.322 clauses 9.4, 9.6, 11.3.2.1.1 and 9.7.1.
1. To verify that a poll is performed when VT(PDU) reaches Poll_PDU.
2. To verify VT(PDU) is incremented for both new and retransmitted PDUs.
Initial conditions
Uplink RLC
Polling info
Poll_PDU 4
Last transmission PDU poll FALSE
Last retransmission PDU poll FALSE

Test procedure
Let the value of Poll_PDU be P:
a) The SS sends 3 * P - 2 RLC SDUs of size AM_7_PayloadSize - 1 bytes to the UE in PDUs with sequence
numbers that are contiguous, starting from zero.
b) The SS checks the sequence numbers and polling bits of the RLC PDUs returned on the uplink.
c) The SS sends a STATUS PDU negatively acknowledging two RLC PDUs with a sequence numbers of already
received PDUs. The other PDUs are acknowledged as received correctly.
d) The SS checks the sequence numbers and polling bits of the RLC SDUs returned on the uplink.
e) The SS terminates the connection.
Release 5 214 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

3


4 DOWNLINK RLC PDU SDU 3P 2


7


8 UPLINK RLC PDU SDU P, Poll
9 STATUS PDU NAK SN=0 and SN=1
12 UPLINK RLC PDU SDU P+1

13


14 UPLINK RLC PDU SDU 2P 2, Poll
15


16 UPLINK RLC PDU SDU 3P 2, Poll
NOTE 2: Due to retransmissions it is not possible to determine the the exact PDU that a poll is received
on. i.e. A poll may be received on a retransmitted PDU or a PDU transmitted for the first time.

The SS shall receive a poll for status every Poll_PDU RLC PDUs sent on the uplink.
7.2.3.18 Polling for status / Poll every Poll_SDU SDUs
This case tests that the UE will poll for a status request every Poll_SDU SDUs when that mode is enabled. Incorrect
operation of polling will cause degradation of service, or at worst service failure.
VT(SDU).
This state variable is used when the "poll every Poll_SDU SDU" polling trigger is configured. It shall be
incremented by 1 for a given SDU when the AMD PDUs carrying the first segment of this SDU is scheduled to
be transmitted for the first time. When it becomes equal to the value Poll_SDU a new poll shall be transmitted
and the state variable shall be set to zero. The "Polling bit" shall be set to "1" in the first transmission of the
AMD PDU that contains the Length Indicator indicating the end of the SDU.
The initial value of this variable is 0.
Poll_SDU.
Release 5 215 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling
every Poll_SDU SDU" is configured by upper layers. It represents the upper limit for state variable VT(SDU).
When VT(SDU) equals the value Poll_SDU a poll shall be transmitted to the peer entity.
Every Poll_SDU SDU.
The Sender triggers the Polling function for every Poll_SDU SDU. The poll shall be triggered for the first
transmission of the AMD PDU that contains the Length Indicator indicating the end of the SDU.
The Sender shall:
- if a poll has been triggered by one or several poll triggers (see TS 25.322 subclause 9.7.1):
- if polling is not prohibited, see TS 25.322 subclause 9.5:
- otherwise:
Reference
TS 25.322 clauses 9. 4, 9.6, 9.7.1 and 11.3.2.1.1.
1. To verify that a poll is performed when VT(SDU) reaches Poll_ SDU.
2. To verify that the poll is sent in the last PDU of the SDU.
Initial conditions
AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
Uplink RLC
Polling info
Poll_SDU 1

Let the value of Poll_SDU be P.
a) The SS sends 2 * P RLC SDUs of size AM_7_PayloadSize - 1 bytes to the UE in PDUs with sequence numbers
that are contiguous, starting from zero.
b) The SS checks the sequence numbers and polling bits of the RLC SDUs returned on the uplink.
c) The SS terminates the connection.
The test is repeated with Poll_SDU set to 16.
Release 5 216 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

3


4 DOWNLINK RLC PDU SDU 2P

5 UPLINK RLC PDU SDU 1 Expanded to (2 *
AM_7_PayloadSize) - 1 bytes by test
function
6 UPLINK RLC PDU

7


8 UPLINK RLC PDU SDU P, Poll
9 STATUS PDU
10 UPLINK RLC PDU SDU P+1 Expanded to (2 *
AM_7_PayloadSize) - 1 bytes by test
function
11 UPLINK RLC PDU
12


13 UPLINK RLC PDU SDU 2P, Poll

The UE shall return uplink PDUs that contain polls for status in sequence numbers 2 * P 1 and 4 * P 1. No other
PDUs shall poll for status.
7.2.3.19 Polling for status / Timer triggered polling (Timer_Poll_Periodic)
This case tests that the UE will poll for a status request every Timer_Poll_Periodic ms when that mode is enabled.
Incorrect operation of polling will cause degradation of service, or at worst service failure.
This timer shall only be used when "timer based polling" is configured by upper layers. The value of the timer is
signalled by upper layers. The timer shall be started when the RLC entity is created. When the timer expires, the
RLC entity shall:
- restart the timer;
- if AMD PDUs are available for transmission or retransmission (not yet acknowledged):
- trigger a poll.
[...]
The Sender shall:
- if a poll has been triggered by one or several poll triggers (see TS 25.322 subclause 9.7.1):
- if polling is not prohibited, see TS 25.322 subclause 9.5:
Release 5 217 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- otherwise:
Reference
TS 25.322 clauses 9.5, 9.7.1 and 11.3.2.1.1.
1. To verify that the UE polls the SS in the next PDU to be transmitted or retransmitted each time the
Timer_Poll_Periodic timer expires.
2. To verify that if there is no PDU to be transmitted or retransmitted, the timer is restarted, but no poll is sent.
Initial conditions
Polling info
Last retransmission PDU poll FALSE FALSE
Timer_poll_periodic 500 2000

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (AM_7_PayloadSize * ceil(T/(5*TTI)))
- 1 bytes.
Test procedure
Let T be the value of Timer_Poll_Periodic:
a) The SS waits for at least 2*T ms before starting any transmissions, and monitors the uplink.
b) The SS sends five RLC SDUs of size floor (AM_7_PayloadSize/5) - 1 bytes to the UE. The SDUs are
concatenated five SDUs to one PDU. The UE is expected to loop this data back in five RLC SDUs, segmented
into a total of at least ceil(T/TTI) RLC PDUs.
c) The SS checks that at least one RLC PDU is received on the uplink with the P bit set and records the arrival time
of the last RLC PDU received with the P bit set (T
1
) . The SS does not send any STATUS PDUs in response to
these poll requests.
d) The SS continues to receive RLC PDUs until all of the data has been received.
e) The SS waits for the UE to retransmit an RLC PDU in order to transmit a poll (this may be the PDU with SN
VT(S) - 1, or a PDU that has not been acknowledged). The SS checks that the P bit is set, and records the arrival
time (T
2
).
f) The SS responds with a STATUS PDU acknowledging all received PDUs.
g) The SS waits for 2*T ms to ensure that no further polls are received from the UE.
h) Void
Release 5 218 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The Test is repeated using the parameters specified for the second run.
Expected sequence
UE SS
1 DOWNLINK RLC PDU SDU 1, SDU2, SDU 3, SDU 4, SDU 5, SN=0
2 UPLINK RLC PDU PDU 1, SN=0
3 UPLINK RLC PDU PDU 2, SN=1
4

SS continues to receive RLC PDUs

5 UPLINK RLC PDU Poll: Note T1

6


7 UPLINK RLC PDU SN =ceil(T/TTI) - 1
8 UPLINK RLC PDU Retransmission of VT(S)-1 or
unacknowledged PDU in order to transmit a
poll. Poll: Note T2.
9 STATUS PDU Normal

10

SS monitors uplink for 2*T ms


1. No PDUs shall be received from the UE for 2*T ms before step 1.
2. Time T
2
T
1
shall be T.
3. No PDUs shall be received from the UE for 2*T ms after step 9.
7.2.3.20 Polling for status / Polling on Poll_Window% of transmission window
This case tests that the UE will poll for a status request when it has reached Poll_Window% of the transmission
window, when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service
failure.
1. A poll is triggered for each AMD PDU when J Poll_Window, where J is the window transmission percentage
defined by

(4096+VT(S) +1 VT(A)) mod 4096
VT(WS)
* 100 ,
J =

where the constant 4096 is the modulus for AM described in 3GPP TS 25.322 subclause 9.4 and VT(S) is the
value of the variable before the AMD PDU is submitted to lower layer.
Release 5 219 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2. The Polling function is used by the Sender to request the peer RLC entity for a status report. The "Polling bit" in
the AMD PDU indicates the poll request. There are several triggers for initiating the Polling function. Which of
the triggers shall be used is configured by upper layers for each RLC entity. The following triggers can be
configured:
.
6) Window based.
The Sender triggers the Polling function when the condition described in subclause 9.6 d) ("Poll_Window")
is fulfilled.
3. The Sender shall:
Reference
25.322 clauses 9.6, 9.7.1 and 11.3.2.1.1.
To verify that the UE polls the SS when the window based polling condition J >=Poll_Window is fulfilled.
Initial conditions
Uplink RLC
Polling info
Poll_Window 50
Downlink RLC

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to AM_7_PayloadSize - 1 bytes.
Test procedure
Let W be the size of the transmission window.
a) The SS transmits (W/2) +2 RLC SDUs of size AM_7_PayloadSize - 1 bytes.
b) The SS checks the sequence number of the first three uplink PDUs received with the P bit set.
c) The SS sends another RLC SDU of size AM_7_PayloadSize - 1 bytes.
d) The SS checks the sequence number of the next uplink PDU received with the P bit set.
e) The SS waits until no more new PDUs are received.
Release 5 220 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
f) The SS sends a STATUS PDU acknowledging the received RLC PDUs with SN =0 through W/2, followed by
two further RLC SDUs.
g) The SS checks the sequence number of the next uplink PDU received with the P bit set.
h) The SS may optionally release the radio bearer.
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU W/2+2

6


7 UPLINK RLC PDU SN =W/2-1, Poll
7a UPLINK RLC PDU SN =W/2, Poll
7b UPLINK RLC PDU SN =W/2 +1, Poll
8 DOWNLINK RLC PDU SDU W/2 +3
9 UPLINK RLC PDU SN =W/2 +2, Poll
9a SS waits 10 TTI periodsto ensure no more
new PDUs are received
10 STATUS PDU ACK SN 0 to W/2 (UE sets VT(A) to W/2+1)
13 UPLINK RLC PDU SN =W/2+3
14 UPLINK RLC PDU SN =W/2+4, Poll

The SS shall receive RLC PDUs with the P bit set in PDUs with sequence numbers of 3, 4, 5, 6 and 8. No other PDUs
shall have their P bits set.
7.2.3.21 Polling for status / Operation of Timer_Poll timer / Timer expiry
This case tests that the UE will retransmit a poll for status if it does not receive a STATUS PDU within Timer_Poll ms
after a poll for status is transmitted. Incorrect operation of polling will cause degradation of service, or possible service
failure.
Timer_Poll.
This timer shall only be used when so configured by upper layers. The value of the timer is signalled by upper
layers. In the UE this timer shall be started when the successful or unsuccessful transmission of an AMD PDU
containing a poll is indicated by lower layer. In UTRAN it should be started when an AMD PDU containing a
poll is submitted to lower layer. If x is the value of the state variable VT(S) after the poll was submitted to lower
layer, the timer shall be stopped upon receiving:
- positive acknowledgements for all the AMD PDUs with "Sequence Number" up to and including x - 1; or
Release 5 221 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- a negative acknowledgement for the AMD PDU with "Sequence Number" =x - 1.
If the timer expires and no STATUS PDU fulfilling the criteria above has been received:
- the Receiver shall be polled once more;
- the timer shall be restarted; and
- the new value of VT(S) shall be saved.
If a new poll is sent when the timer is active, the timer shall be restarted at the time specified above, and the
value of VT(S) shall be saved.
[...]
The Sender shall:
- otherwise:
Reference
TS 25.322 clauses 11.3.2.1.1 and 11.3.4.1.
To verify that if the timer expires and no STATUS PDU containing an acknowledgement or negative acknowledgement
of the AMD PDUs up to that which triggered the timer has been received, the receiver is polled once more.
Initial conditions
Polling info
Timer_poll 600 1000
Timer_Poll_Periodic 2000 2000

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to AM_7_PayloadSize - 1 bytes.
Test procedure
Let T be the value of the Timer_Poll_Periodic timer.
a) The SS transmits at least 2 * T / TTI SDUs of size AM_7_PayloadSize - 1 bytes.
Release 5 222 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
b) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set, but does not
respond. This time will be recorded as T
1.

c) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set.
This time will be recorded as T
2
.
d) The SS continues to receive PDUs from the UE until all transmitted PDUs have been received. The SS responds
to any PDU received with the P bit set by transmitting a STATUS PDU containing an acknowledgement of the
AMD PDUs received.
e) The SS acknowledges the last Poll PDU from the UE.
The test case is run once for each set of initial RLC parameters.
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU ceil(2T/TTI)

6


7 UPLINK RLC PDU SN =ceil(T/TTI), Poll: Note T1
8 UPLINK RLC PDU SN =ceil(T/TTI)+1

9


10 UPLINK RLC PDU Poll: Note T2

11

SS continues to receive PDUs,
acknowledging with STATUS PDUs when
polled until all PDUs have been received
and acknowledged

For the first run, the measured time T
2
T
1
shall be 600 ms.
For the second run, the measured time T
2
T
1
shall be 1000 ms.
7.2.3.22 Polling for status / Operation of Timer_Poll timer / Stopping Timer_Poll timer
This case tests that the UE will stop the Timer_Poll timer if it receives a STATUS PDU within Timer_Poll ms after a
poll for status is transmitted. Incorrect operation of polling will cause degradation of service, or possible service failure.
Timer_Poll.
Release 5 223 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
[...]
The Sender shall:
- otherwise:
Reference
TS 25.322 clause 9.5.
To verify that the Timer_Poll timer is stopped when receiving a STATUS PDU that acknowledges all AMD PDUs with
SN up to and including VT(S)-1 at the time the poll was transmitted.
Initial conditions
Tx_Window_Size 256 256
Polling info
Timer_poll 500 1000
Timer_Poll_Periodic 2000 2000

Release 5 224 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure
Let T be the value of the Timer_Poll_Periodic timer.
a) The SS transmits at least 2 * T / TTI SDUs of size AM_7_PayloadSize - 1 bytes.
b) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set. This time
will be recorded as T
1.

c) The SS sends a STATUS PDU acknowledging all the PDUs up to and including the PDU carrying the poll
request.
d) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set.
2
.
e) The SS continues to receive PDUs from the UE until all transmitted PDUs have been received. The SS responds
to any PDU received with the P bit set by transmitting a STATUS PDU containing an acknowledgement of the
AMD PDUs received.
f) The SS acknowledges the last Poll PDU from the UE.
g) The SS may optionally release the radio bearer.
The test case is run once for each set of initial RLC parameters.
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU ceil(2T/TTI)

6


7 UPLINK RLC PDU SN =ceil(T/TTI), Poll: Note T1
8 STATUS PDU ACK SN 0 to SN ceil(T/TTI)
9 UPLINK RLC PDU SN =ceil(T/TTI)+1

10


11 UPLINK RLC PDU SN =ceil(2T/TTI), Poll: Note T2

12

SS continues to receive PDUs,
acknowledging with Status PDUs when
and acknowledged

For both execution runs, the measured time T
2
T
1
shall be 2000 ms.
Release 5 225 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.3.23 Polling for status / Operation of Timer_Poll timer / Restart of the Timer_Poll
timer
This case tests that the UE will restart the Timer_Poll timer if another poll request is transmitted whilst the timer is
running. Incorrect operation of polling will cause degradation of service, or possible service failure.
Timer_Poll.
[...]
The Sender shall:
- otherwise:
Reference
TS 25.322 clause 9.5.
To verify that if a new poll is sent when the timer is running it is restarted.
Initial conditions
Release 5 226 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Uplink RLC
Polling info
Last retransmission PDU poll FALSE
Timer_poll 600
Poll_Window 60
Poll_PDU 16
Transmit window size 32

Test procedure
Let T be the value of the Timer_Poll timer.
a) The SS starts transmission of ceil(Tx_Window_Size * 60%) numbers of SDUs of size AM_7_PayloadSize -
1bytes.
b) Whilst transmitting, the SS receives PDUs from the UE, until it receives the second PDU with the P bit set. This
time is recorded as T
1
. (Note: poll due to Poll_Window).
c) Void.
d) Void.
e) The SS waits until a PDU is received with the poll bit set and notes the time when it was received. This time is
recorded as T
2
.
Release 5 227 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU ceil(Tx_Window_Size * 60%)

6


7 UPLINK RLC PDU SN =poll_PDU - 1, 1
st
Poll, Timer_Poll
started
8 Void
9 Void
10 UPLINK RLC PDU SS continues to receive RLC PDUs

11 UPLINK RLC PDU SN=ceil(Tx_Window_Size * 60%)-1, 2
nd

Poll, Timer_Poll restarted.
Note T1
12 Void
13 Void
14 Void
15 UPLINK RLC PDU SS waits for reception of PDU with poll bit
set, 3
rd
Poll, Timer_Poll expired.
Note T2

The measured time T
2
T
1
shall be 600 ms.
7.2.3.24 Polling for status / Operation of timer Timer_Poll_Prohibit
This case tests that the UE will not send a poll request within Timer_Poll_Prohibit ms of a previous poll request when
this mode of operation is enabled. Incorrect operation of polling will cause degradation of service, or possible service
failure.
The timers defined in this subclause are normative. The timers shall be considered active from the time they are started
until the time they either expire or are stopped.
b) Timer_Poll_Prohibit.
This timer shall only be used when so configured by upper layers. It is used to prohibit transmission of polls
within a certain period. The value of the timer is signalled by upper layers.
In the UE this timer shall be started when the successful or unsuccessful transmission of an AMD PDU
poll is submitted to lower layer.
From the time a poll is triggered until the timer expires, polling is prohibited. If another poll is triggered while
polling is prohibited, its transmission shall be delayed until the timer expires (see subclause 9.7.1). Only one poll
Release 5 228 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
shall be transmitted when Timer_Poll_Prohibit expires even if several polls were triggered in the meantime. This
timer shall not be affected by the reception of STATUS PDUs.
When Timer_Poll_Prohibit is not configured by upper layers, polling is never prohibited.
The Sender shall:
- otherwise:
Reference
TS 25.322 clauses 9.5, 9.7.1 and 11.3.2.1.1.
1. To verify that no poll is transmitted if one or several polls are triggered when the Timer_Poll_Prohibit timer is
active and has not expired.
2. To verify that the UE polls only once after Timer_Poll_Prohibit expires even though triggered several times
during the prohibit time.
Initial conditions
Uplink RLC
Polling info
Timer_poll_prohibit 500
Poll_PDU 2
Poll_Window 50
Downlink RLC

Test procedure
Let T be the value of the Timer_Poll_Prohibit timer.
a) The SS starts transmission of at least (2*Poll_PDU) +ceil(T / TTI) SDUs of size AM_7_PayloadSize - 1 bytes.
b) Whilst transmitting, the SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P
bit set. This time will be recorded as T
1.

c) The SS does not respond to the poll request.
Release 5 229 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
d) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set.
2
.
e) The SS waits for at least Timer_Poll_Prohibit to acknowledge any last Poll PDU from the UE.
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU (2*Poll_PDU)+ceil(T/TTI)

6


7 UPLINK RLC PDU SN =Poll_PDU - 1, Poll: Note T1

8


9 Void
10 UPLINK RLC PDU SN =(Transmission Window Size / 2) 1,
No Poll

11


12 UPLINK RLC PDU SN =Poll_PDU +ceil(T/TTI) - 1, Poll: Note
T2

12a

and acknowledged


1. The measured time T
2
T
1
shall be Timer_poll_prohibit ms.
7.2.3.25 Receiver Status Triggers / Detection of missing PDUs
This case tests that the UE transmits a status report whenever it detects that a PDU is missing, if this mode of operation
is enabled. Incorrect operation of status reporting will cause degradation of service, or possible service failure.
Detection of missing PDU(s).
If the Receiver detects one or several missing AMD PDUs it shall trigger the transmission of a status report to the
Sender.
Release 5 230 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference
TS 25.322 clause 9.7.2.
To verify that a status report is transmitted if there are one or more missing PDUs.
Initial conditions
Test procedure
a) The SS transmits 7 SDUs, each of size AM_7_PayloadSize - 1 bytes, in PDUs with consecutive sequence
numbers starting from 0, followed by 5 SDUs in PDUs with consecutive sequence numbers starting from 8,
followed by an SDU in a PDU with a sequence number of 15.
b) While transmitting, the SS monitors the uplink for STATUS PDUs.
c) The SS may optionally release the radio bearer
Expected sequence
UE SS
1 DOWNLINK RLC PDU SN =0

2


5 STATUS PDU SN =7 missing
6 DOWNLINK RLC PDU

7


10 STATUS PDU SN =7, 13, 14 missing

A STATUS PDU shall be received from the UE after step 4, indicating that the PDU with sequence number 7 was
missing.
A STATUS PDU shall be received from the UE after step 9, indicating that the PDUs with sequence numbers 7, 13 and
14 were missing.
Release 5 231 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.3.26 Receiver Status Triggers / Operation of timer Timer_Status_Periodic
This case tests that the UE transmits a status report every Timer_Status_Periodic ms when this mode of operation is
enabled. Incorrect operation of status reporting will cause degradation of service, or possible service failure.
This timer shall only be used when timer based status reporting is configured by upper layers.
This timer shall be started when the RLC entity is created. When the timer expires the transmission of a status report
shall be triggered and the timer shall be restarted.
Reference
TS 25.322 clauses 9.5, 9.7.2 and 11.5.2.
To verify that a status report is transmitted each time the Timer_Status_Periodic timer expires.
Initial conditions
Downlink RLC
Timer_STATUS_periodic 400

Test procedure
Let T be the value of the Timer_STATUS_periodic timer.
a) The SS starts transmission of at least ceil(2 * T / TTI) SDUs of size AM_7_PayloadSize - 1 bytes.
b) The SS waits to receive a STATUS PDU and notes the time. This time will be recorded as T
1
.
c) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T
2
.
d) The SS waits for at least Timer_Status_Periodic to receive any last STATUS PDU from the UE.
Release 5 232 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

2


3 DOWNLINK RLC PDU SDU m
4 STATUS PDU Note T1
5 DOWNLINK RLC PDU

6


7 DOWNLINK RLC PDU SDU m +ceil(T/TTI)
9 Void

10

STATUS PDU

SS may receive STATUS PDUs

The measured time T
2
T
1
shall be 400 ms.
7.2.3.27 Receiver Status Triggers / Operation of timer Timer_Status_Prohibit
This case tests that the UE does not transmit a status report more often than every Timer_Status_Prohibit ms when this
mode of operation is enabled. Incorrect operation of status reporting will cause degradation of service, or possible
service failure.
In the UE, this timer shall be started when the successful or unsuccessful transmission of the last STATUS PDU of an
acknowledgement status report is indicated by lower layer
[...]
When a status report is triggered the Receiver shall:
- if transmission of status reports is not prohibited by any of the functions "STATUS prohibit" or "EPC
mechanism":
- assemble and transmit the status report to the Sender, as specified in subclauses TS 25.322 11.5.2.2 and
11.5.2.3.
- otherwise (if the status report is prohibited by at least one of the functions "STATUS prohibit" or "EPC
mechanism"):
[...]
- if ACK, LIST, BITMAP, or RLIST SUFIs are required in the status report:
- delay sending these SUFIs until the prohibit function terminates.
[...]
Upon expiry of the timer Timer_Status_Prohibit [...], the Receiver shall:
Release 5 233 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- if at least one status report was triggered during the time the transmission of a status reports was prohibited that
could not be transmitted due to prohibition; and
- if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "EPC
mechanism":
- transmit one status report to the Sender, using the procedure described in subclause TS 25.322 11.5.2.3.
Reference
TS 25.322 clause 9.7.2.
1. To verify that a status report is not transmitted while the Timer_Status_Prohibit timer is active.
2. To verify that only one status report is sent on the expiry of the Timer_Status_Prohibit timer if several triggers
occur while it is active.
Initial conditions
Downlink RLC
Timer_Status_Prohibit 500
Timer_STATUS_periodic 200

Test procedure
Let T
pro
be the value of the Timer_Status_Prohibit timer, and T
per
be the value of the Timer_Status_Periodic timer.
a) The SS starts transmission of at least ceil(2 * T
pro
/ TTI) +ceil(T
per
/TTI) SDUs of size AM_7_PayloadSize - 1
bytes.
b) Whilst transmitting, the SS monitors the uplink for a STATUS PDU and notes the time. This time will be
recorded as T
1
.
c) The SS sets the P bit in one of the next floor(T
pro
/TTI) PDUs transmitted on the downlink.
d) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T
2
.
e) The SS waits for at least Timer_Status_Prohibit to receive any last STATUS PDU from the UE.
Release 5 234 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

2


5 DOWNLINK RLC PDU Poll

6

SS continues to transmit RLC PDUs

7 DOWNLINK RLC PDU SDU m +ceil(Tpro / TTI)
8 Void

10

STATUS PDU

SS may receive STATUS PDUs
11 RB RELEASE Optional Step

2
T
1
shall be 500 ms.
7.2.3.28 Status reporting / Abnormal conditions / Reception of LIST SUFI with Length
set to zero
Peer RLCs use STATUS PDUs to manage flow control and retransmission. On a STATUS report PDU with an invalid
LIST SUFI the RLC must behave as specified. Incorrect behaviour may result in degradation of QoS, or failure of the
UE to communicate.
The List super-field
The List Super-Field consists of a type identifier field (LIST), a list length field (LENGTH) and a list of LENGTH
number of pairs as shown in figure 9.11 below:
Type =LIST
LENGTH
SN1
L1
SN2
L2

SNLENGTH
LLENGTH

Figure 9.11: The List fields in a STATUS PDU
LENGTH
Length: 4 bits
The number of (SN
i
, L
i
)-pairs in the super-field of type LIST. The value "0000" is invalid and the list is discarded.
Release 5 235 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference
TS 25.322 clause 9.2.2.11.4.
To verify that if a STATUS PDU is received with a LIST SUFI and the LENGTH field is set to "0000" that the list is
discarded.
Initial conditions
Uplink RLC
Polling info
Poll_PDU 4

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (3 * Poll_PDU * AM_7_PayloadSize)
1 bytes.
Test procedure
a) The SS sends an SDU of size (AM_7_PayloadSize) 1.
b) The SS monitors the received (looped back) PDUs for a poll request.
c) The SS responds to the poll request by transmitting a STATUS PDU with a LIST SUFI. The list contains an
indication that two PDUs were not received, but has the length field set to "0000".
d) The SS continues to monitor the received PDUs to verify that none are retransmitted.
Release 5 236 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 DOWNLINK RLC PDU SDU 1 (start)

2


3 DOWNLINK RLC PDU SDU 1 (end)
4 UPLINK RLC PDU SDU 1 (start)
5 UPLINK RLC PDU

6


7 UPLINK RLC PDU SN =Poll_PDU - 1, Poll
8 STATUS PDU LIST(LENGTH ="0000", SN =1, SN =2)

9


10 UPLINK RLC PDU Poll
11 STATUS PDU Normal reply

12


13 UPLINK RLC PDU SDU 1 (end)

No RLC PDUs shall be retransmitted by the UE.
7.2.3.29 Timer based discard, with explicit signalling / Expiry of Timer_Discard
This case tests that when the transmission of an SDU exceeds a time limit, the SDU is discarded by the sender, and the
discard is signalled to the receiver. SDU discard is used to keep network delays within limits, and incorrect operation
will effect the quality of service.
If the transmission time exceeds a predefined value for a SDU in acknowledged mode RLC, this SDU is discarded in
the transmitter and a Move Receiving Window (MRW) command is sent to the receiver so that AMD PDUs carrying
that SDU are discarded in the receiver and the receiver window is updated accordingly.
This procedure is initiated by the sender when the following conditions are fulfilled Timer based SDU discard with
explicit signalling is used, and Timer_Discard expires for an SDU.
This status report is sent even if the 'STATUS prohibit' is used and the timer 'Timer_Status_Prohibit' is active.
The STATUS PDUs have higher priority than data PDUs.
Reference
TS 25.322 clauses 9.7.3.1, 11.3.4.3.1 and 11.6.
Release 5 237 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1. To verify that if the transmission time for an SDU exceeds Timer_Discard, the SDU is discarded in the
transmitter and the MRW procedure is invoked.
2. ...
Initial conditions
Uplink RLC
Timer based with explicit signalling
Timer_MRW 500
Timer_Discard 1000
MAX_MRW 4

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize 1 bytes.
Test procedure
a) The SS sends at least 2 RLC SDUs of size AM_7_PayloadSize 1bytes.
b) The SS notes the time that the first RLC PDU is received on the uplink. This time will be recorded as T
1
.
c) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU,
negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC
PDUs received.
d) The SS monitors received STATUS PDUs for the presence of a MRW SUFI, noting the time it was received.
2
.
e) The SS responds to the MRW command with a correct MRW_ACK.
f) Void.
Release 5 238 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
3 UPLINK RLC PDU SDU 1: Note T1

4


6 STATUS PDU NAK SN=0

7

SS continues to receive RLC PDU with
SN=0 +Poll

8 STATUS PDU, SS continues to NAK PDU
with SN=0
9 STATUS PDU MRW Command: Note T2
10 STATUS PDU MRW_ACK

2
T
1
shall be 1000 ms.
2. The STATUS PDU received in step 9 shall contain a MRW SUFI indicating that the first three PDUs shall be
discarded, and that the data indicated in the fourth PDU by the first LI shall also be discarded.
7.2.3.29a Timer based discard, with explicit signalling / Expiry of Timer_Discard when
Timer_STATUS_prohibit is active
7.2.3.29a.1 Definition
This case tests that when the transmission of an SDU exceeds a time limit, the SDU is discarded by the sender, and the
discard is signalled to the receiver while the Timer_STATUS_Prohibit is active. SDU discard is used to keep network
delays within limits, and incorrect operation will effect the quality of service.
If the transmission time exceeds a predefined value for a SDU in acknowledged mode RLC, this SDU is discarded in
the transmitter and a Move Receiving Window (MRW) command is sent to the receiver so that AMD PDUs carrying
that SDU are discarded in the receiver and the receiver window is updated accordingly.
Upon expiry of Timer_Discard the sender shall initiate the SDU discard with explicit signalling procedure.
This status report is sent even if the 'STATUS prohibit' is used and the timer 'Timer_Status_Prohibit' is active.
The STATUS PDUs have higher priority than data PDUs.
Reference
TS 25.322 clauses 9.7.3.1, 11.3.4.3.1 and 11.6.
1.
Release 5 239 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2. To verify that the MRW procedure status report is sent even if the 'STATUS prohibit' is used and the timer
'Timer_Status_Prohibit' is active.
TBD
TBD
7.2.3.30 Timer based discard, with explicit signalling / Obsolete MRW_ACK
This case tests the ability of the receiving AM RLC entity to handle obsolete information that can be received during a
failure of the SDU discard procedure. SDU discard is used to keep network delays within limits, and incorrect operation
will effect the quality of service.
If Timer_MRW expires before the discard procedure is terminated,the MRW SUFI shall be retransmitted, VT(MRW) is
incremented by one and Timer_MRW restarted. MRW SUFI shall be exactly the same as previously transmitted even
though some new SDUs would have been discarded during the running of the Timer_MRW.
The received MRW_ACK shall be discarded in the following cases.
1.
2. If the SN_ACK field in the received MRW_ACK <SN_MRW
LENGTH
in the transmitted MRW SUFI.
3. If the SN_ACK field in the received MRW_ACK is equal to the SN_MRW
LENGTH
in the transmitted MRW SUFI
and the N field in the received MRW_ACK is not equal to the N
LENGTH
field in the transmitted MRW SUFI
4. If the SN_ACK field in the received MRW_ACK >SN_MRW
LENGTH
in the transmitted MRW SUFI and the N
field in the received MRW_ACK is not equal to zero.
Reference
TS 25.322 clauses 11.6.5 and 11.6.6.3.
1. To verify that the MRW SUFI is retransmitted if Timer_MRW expires before a valid MRW_ACK is received.
2. To verify that the MRW_ACK is discarded if the SN_ACK field <SN_MRW
LENGTH
.
3. To verify that the MRW_ACK is discarded if the N field is not equal to N
LENGTH
transmitted in the MRW SUFI.
4. To verify that the MRW_ACK is discarded if the N field is not zero and the SN_ACK field >SN_MRW
LENGTH

in the transmitted MRW SUFI.
Initial conditions
Release 5 240 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Uplink RLC
MaxDAT Retransmissions
MaxDAT 40
Timer_MRW 500
MAX_MRW 4

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize 1bytes.
Test procedure
a) The SS sends at least 2 RLC SDUs of size AM_7_PayloadSize 1bytes.
b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU,
PDUs received.
c) The SS monitors received STATUS PDUs for the presence of a MRW SUFI, noting the time it was received.
1
.
d) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW
LENGTH

1.
e) The SS monitors received STATUS PDUs for another MRW SUFI, noting the time it was received. This time
2
.
f) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW
LENGTH
,
and the N field set to (N
LENGTH
+1) modulo 4.
g) The SS monitors received STATUS PDUs for another MRW SUFI, noting the time it was received. This time
3
.
h) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW
LENGTH
+
1, and the N field set to 1.
i) The SS monitors received STATUS PDUs for another MRW SUFI.
j) The SS responds to the MRW command with a correct MRW_ACK.
k) The SS may optionally release the radio bearer.
Release 5 241 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

6

SS continues to receive RLC PDU with
SN=0 +Poll

7 ... STATUS PDU, SS continues to NAK PDU
with SN=0
9 STATUS PDU MRW_ACK, SN_ACK =SN_MRWLENGTH 1
11 STATUS PDU MRW_ACK, N field =(NLENGTH +1) modulo 4
13 STATUS PDU MRW_ACK, SN_ACK =SN_MRWLENGTH +
1, N field =1
14 STATUS PDU MRW Command

2
T
1
shall be 500 ms.
3
T
2
shall be 500 ms.
3. The STATUS PDUs received in steps 8, 10, 12 and 14 shall contain an identical MRW SUFI.
7.2.3.31 Timer based discard, with explicit signalling / Failure of MRW procedure
This case tests that if a failure occurs during the signalling of an SDU discard to the receiver, the retransmission
protocol operates correctly. SDU discard is used to keep network delays within limits, and incorrect operation will
effect the quality of service.
If VT(MRW) =MaxMRW, the Sender shall:
- terminate the SDU discard with explicit signalling procedure;
- stop the timer Timer_MRW if it was started;
- initiate the RLC RESET procedure (see clause 11.4).
If Timer_MRW expires before the discard procedure is terminated, the Sender shall:
- increment VT(MRW) by one;
- if VT(MRW)<MaxMRW:
- set the MRW SUFI as previously transmitted (even if additional SDUs were discarded in the mean-time);
- include the MRW SUFI in a new status report (if other SUFIs are included, their contents shall be updated);
Release 5 242 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- transmit the status report by either including it in a STATUS PDU or piggybacked in an AMD PDU;
- restart Timer_MRW for this discard procedure;
- else (if VT(MRW) =MaxMRW):
- perform the actions specified in subclause 11.6.4a.
Reference
TS 25.322 clause 11.6.4a, 11.6.5.
1. To verify that when the number of retransmissions of a MRW command reaches MaxMRW, an error indication
is passed to RRC and RESET procedure is initiated.
Initial conditions
Uplink RLC
Timer based with explicit signalling
Timer_MRW 500
Timer_Discard 500
Max_MRW 4
Polling info
Poll_PDU 2

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to (2 * AM_7_PayloadSize) 1bytes.
Test procedure
a) The SS sends 4 RLC SDUs of size (2 * AM_7_PayloadSize) 1bytes.
b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests as follows: While the
VR(H) is 4 or less, with a STATUS PDU, negatively acknowledging the RLC PDU with sequence number 0,
and positively acknowledging all other RLC PDUs received. While the VR(H) is greater than 4, a STATUS PDU
negatively acknowledging RLC PDUs with sequence numbers 0 and 4, and positively acknowledging all others.
c) The SS monitors received STATUS PDUs for the presence of an MRW SUFI, noting the time it was received.
1
.
d) The SS makes no response, but monitors for the next STATUS PDU containing an MRW SUFI, noting the time
it was received. This time will be recorded as T
2
.
e) The SS sends a STATUS PDU with an MRW_ACK indicating the discard of SDU 1 moving VR(R) to 4.
f) The SS monitors for further STATUS PDUs containing an MRW SUFI, or for a RESET PDU. The SS records
the number of STATUS PDUs it received with MRW SUFI before it received the RESET PDU.
g) The SS checks any RLC SDUs reassembled from the uplink.
Release 5 243 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

4

SS continues to send RLC PDUs


7



10


12 STATUS PDU NAK SN=0, 4

13


16 STATUS PDU MRW_ACK indicating VR(R) =4
17 STATUS PDU MRW Command, discard SDU 3
21 RESET PDU
22 RESET ACK PDU

The measured time T
2
T
1
shall be 500 ms.
After step 17, the SS shall detect 3 repeats of the MRW command sent in step 17 before a RESET PDU is sent.
7.2.3.32 SDU discard after MaxDAT-1 number of transmissions
This case tests that if a PDU is unsuccessfully transmitted MaxDAT-1 times, the SDU it carries, and therefore all other
associated PDUs, are discarded by the transmitter and receiver. This mode of SDU discard is used to minimize data
loss, and incorrect operation will effect the quality of service.
1. There shall be one VT(DAT) for each PDU and each shall be incremented every time the corresponding AMD
PDU is scheduled to be transmitted. The initial value of this variable is 0.
2. If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall:
- discard all SDUs segments of which are contained in the AMD PDU; and
- utilise explicit signalling to inform the Receiver according to clause 11.6.
Release 5 244 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3. If VT(DAT) =MaxDAT, the Sender shall:
- if "No_discard after MaxDAT number of transmissions" is configured:
.
- if "SDU discard after MaxDAT number of transmissions" is configured:
- initiate the "SDU discard with explicit signalling" procedure for the corresponding SDU, see subclause
11.6.
4. Upon initiation of the SDU discard with explicit signalling procedure, the Sender shall:
..
- if "SDU discard after MaxDAT number of transmissions" is configured:
- discard all SDUs that have segments in AMD PDUs with "Sequence Number" SN inside the interval
VT(A) SN X, where X is the value of the "Sequence Number" of the AMD PDU with VT(DAT)
MaxDAT.
- discard all AMD PDUs including segments of the discarded SDUs, unless they also carry a segment of a
SDU whose timer has not expired;
- if more than 15 discarded SDUs are to be informed to the Receiver (see subclause 11.6.2.2):
.
- otherwise (less than or equal to 15 discarded SDUs are to be informed to the Receiver):
- assemble an MRW SUFI with the discard information of the SDUs.
- schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW
SUFI;
.
Reference
TS 25.322 clauses 9.4, 9.7.3.3, 11.3.3a and 11.6.
1. To verify that if VT(DAT) =MaxDAT for any PDU the sender initiates the SDU discard with explicit signalling
procedure.
Initial conditions
The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) 1 bytes.
Test procedure
a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) 1 bytes.
b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU
PDUs received.
Release 5 245 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
c) The SS monitors received STATUS PDUs for the presence of an MRW SUFI.
d) The SS responds with a STATUS PDU containing a valid MRW_ACK SUFI.
e) The SS checks any RLC SDUs reassembled from the uplink.
Expected sequence
UE SS

6


7 UPLINK RLC PDU SDU 2, Poll
9 UPLINK RLC PDU Retransmit SN=0, Poll
13 Void
14 Void

The uplink RLC PDU with sequence number 0 shall be retransmitted twice, then the SS shall detect a STATUS PDU
with an MRW command.
7.2.3.33 Operation of the RLC Reset procedure / UE Originated
This case tests that when the maximum number of retransmissions is exceeded, the UE initiates and performs the RLC
Reset procedure. Incorrect operation of this procedure may cause loss of service.
The Sender shall:
- if one of the following triggers is detected:
1) "No_Discard after MaxDAT number of transmissions" is configured and VT(DAT) equals the value MaxDAT
(see TS 25.322 subclause 9.7.3.4);

- stop transmitting any AMD PDU or STATUS PDU;
- increment VT(RST) by 1;
- if VT(RST) =MaxRST:
Release 5 246 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- the Sender may submit to the lower layer a RESET PDU;
- perform the actions specified in TS 25.322 subclause 11.4.4a.
- else (if VT(RST) <MaxRST):
- submit a RESET PDU to the lower layer;
- start the timer Timer_RST.
NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the
RLC entity may delay the RLC reset procedure until the end of the next TTI.
When a reset procedure has been initiated it can only be ended upon reception of a RESET ACK PDU with the same
RSN value as in the corresponding RESET PDU, or upon request of re-establishment or release from upper layer, a
reset procedure is not interrupted by the reception of a RESET PDU from the peer entity.
[...]
The Sender shall:
- set the HFNI field to the currently highest used HFN (DL HFN when the RESET PDU is sent by UTRAN or UL
HFN when the RESET PDU is sent by the UE);
- set the RSN field to the sequence number of the RESET PDU. The sequence number of the first RESET PDU
after the AM entity is established or re-established shall be "0". This sequence number is incremented every time
a new RESET PDU is transmitted, but not when a RESET PDU is retransmitted.
[...]
Upon reception of a RESET ACK PDU, the Sender shall:
- if the Sender has already transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK
PDU:
- if the received RSN value is the same as the one in the corresponding RESET PDU:
- set the HFN value (DL HFN when the RESET ACK PDU is received in UE or UL HFN when the RESET
ACK PDU is received in UTRAN) to the HFNI field of the received RESET ACK PDU;
- reset the state variables described in subclause 9.4 to their initial values;
- stop all the timers described in subclause 9.5;
- reset configurable parameters to their configured values;
- discard all RLC PDUs in the receiving side of the AM RLC entity;
- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC
entity;
- increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first
transmitted and received AMD PDUs after the reset procedure;
- otherwise (if the received RSN value is not the same as the one in the corresponding RESET PDU):
- discard the RESET ACK PDU;
- otherwise (if the Sender has not transmitted a RESET PDU which has not been yet acknowledged by a RESET
ACK PDU):
- discard the RESET ACK PDU.
RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI.
[...]
Release 5 247 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
If Timer_RST expires before the reset procedure is terminated, the Sender shall:
- increment VT(RST) by one;
- if VT(RST)<MaxRST:
- set the RESET PDU as previously transmitted (even if additional SDUs were discarded in the mean-time);
- transmit RESET PDU;
- restart Timer_RST.
Reference
TS 25.322 clause 11.4.2, 11.4.2.1, 11.4.4, 11.4.5.1.
1. To verify that the Reset procedure is initiated when the maximum number of retransmissions has been exceeded
(Reset trigger condition 1) in subclause 11.4.2 of 3GPP TS 25.322 (R1999).
2. To verify that the sender resets state variables to their initial value and resets configurable parameters to their
configured value.
3. To verify that RSN is updated correctly.
4. To verify operation of Timer_RST.
Initial conditions
Uplink RLC
No discard
Max_DAT 4

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) 1 bytes.
Test procedure
a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) 1 bytes.
b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU
PDUs received.
c) The SS notes the time that the RESET PDU is received. This time will be recorded as T
1
. The SS notes the value
of the RSN bit.
d) The SS makes no response, and notes the time that the next RESET PDU is received. This time will be recorded
as T
2
. The SS notes the value of the RSN bit.
e) The SS sends a RESET ACK PDU with the RSN bit set to the same value as received in the RESET PDU
received in step d).
Release 5 248 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
f) The SS sends an RLC SDU of size (2 * AM_7_PayloadSize) 1bytes. The data contents of this RLC SDU shall
be different from the contents of the RLC SDUs sent in procedure step a) above.
g) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU
PDUs received.
h) The SS notes the value of the RSN bit of the RESET PDU received.
i) The SS sends a RESET ACK PDU with the RSN bit set to the value received in the RESET PDU in step c (the
incorrect value).
j) The SS waits to receive another RESET PDU and checks the RSN bit.
k) The SS sends a RESET ACK PDU with the correct RSN bit.
l) The SS checks any RLC SDU received on the uplink.
m) The SS may optionally release the radio bearer.
Expected sequence
UE SS

6


7 UPLINK RLC PDU SDU, Poll
The Poll may appear in returned PDU for
either SDU 1 or 2
9 UPLINK RLC PDU Retransmit PDU SN=0, Poll
11 UPLINK RLC PDU Retransmit PDU SN=0, Poll
13 Void
14 Void
15 RESET PDU Note T1
16 RESET PDU Note T2, check RSN
17 RESET ACK PDU
20 UPLINK RLC PDU SDU 3, check PDU has SN=0
21 UPLINK RLC PDU SDU 3, Poll
27 Void
28 Void
29 RESET PDU Check RSN
30 RESET ACK PDU RSN =0
31 RESET PDU Check RSN
32 RESET ACK PDU RSN =1

Release 5 249 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2
T
1
shall be 500 ms.
2. In steps 20 to 21 the SS shall receive an RLC SDU with contents that match the third RLC SDU sent to the UE.
The first RLC PDU containing that SDU shall have sequence number 0.
3. The RSN bit of the first and second RESET PDUs received shall be set to 0. The RSN bit of the third and fourth
RESET PDU shall be set to 1.
7.2.3.34 Operation of the RLC Reset procedure / UE Terminated
This case tests that the UE responds correctly to the RLC Reset procedure initiated by the network. Incorrect operation
of this procedure may cause loss of service.
Upon reception of a RESET PDU the Receiver shall:
- if the RSN value in the RESET PDU is the same as the RSN value in the last received RESET PDU:
- either only submit a RESET ACK PDU to the lower layer with the contents set exactly as in the last
transmitted RESET ACK PDU (i.e., in this case the RLC entity is not reset); or
- perform the actions specified below as if the RSN value was different from the RSN value in the last received
RESET PDU.
- otherwise, if the RESET PDU is the first RESET PDU received since the entity was (re-)established or the RSN
value is different from the RSN value in the last received RESET PDU:
- submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1;
- reset the state variables described in subclause 9.4 except VT(RST) to their initial values;
- stop all the timers described in subclause 9.5 except Timer_RST;
- reset configurable parameters to their configured values;
- discard all RLC PDUs in the receiving side of the AM RLC entity;
- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;
- set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is
received in UTRAN) equal to the HFNI field in the received RESET PDU;
- increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first
transmitted and received AMD PDUs after the reset procedure.
RLC entity may delay the RLC SDUs discard in the transmitting side of the AM RLC entity until the end
of the next TTI.
Reference
TS 25.322 clause 11.4.3.
1. To verify that upon reception of a RESET PDU the receiver responds with a RESET ACK PDU.
2. To verify that the receiver resets its state variables to their initial value and resets configurable parameters to
their configured value.
Release 5 250 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
Uplink RLC
No discard
MaxDAT 4

Test procedure
a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) 1 bytes, and polls on the last PDU sent.
b) The SS checks the STATUS PDUs received on the uplink until both SDUs have been acknowledged.
c) The SS transmits a RESET PDU.
d) The SS monitors the uplink for a RESET ACK PDU.
e) The SS sends an RLC SDU of size (2 * AM_7_PayloadSize) 1 bytes, and polls on the last PDU sent.
f) The SS checks for STATUS PDUs received on the uplink until the SDU has been acknowledged.
Expected sequence
UE SS
4 DOWNLINK RLC PDU SDU 2, poll
5 STATUS PDU ACK SN=0, 1, 2 and 3
6 RESET PDU
7 RESET ACK PDU
9 DOWNLINK RLC PDU SDU 3, poll
10 STATUS PDU ACK SN=0 and 1

1. The SS shall receive a RESET ACK PDU in step 7.
2. The SS shall receive a STATUS PDU in step 10 acknowledging for the third RLC SDU transmitted with PDUs
starting at SN=0.
Release 5 251 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.2.3.35 Reconfiguration of RLC parameters by upper layers
This case verifies the UE behaviour after a reconfiguration of RLC parameters on an established RLC AM entity.
Upon reception of the IE "RLC Info", the UE shall:
1>configure the transmitting and receiving RLC entities in the UE for that radio bearer accordingly;
1>if the IE "Polling info" is present in the IE "RLC info":
2>for each present IE in the IE "Polling info":
3>configure RLC to use the corresponding function according to the value of the IE.
2>for each absent IE in the IE "Polling info":
3>configure RLC to not use the corresponding function.
1>if the IE "Polling info" is absent:
2>configure RLC to not use the polling functionality.
1>if the IE "Downlink RLC STATUS info" is present in the IE "RLC info" (this IE is present for AM RLC):
2>for each present IE in the IE "Downlink RLC STATUS info":
3>configure RLC to use the corresponding function according to value of the IE.

a) Timer_Poll.
containing a poll is indicated by lower layer.
f) Timer_Status_Prohibit.
This timer shall only be used when so configured by upper layers. It is meant to prohibit the Receiver from
sending consecutive acknowledgement status reports. A status report is an acknowledgement status report if it
contains any of the SUFIs LIST, BITMAP, RLIST or ACK. The value of the timer is signalled by upper layers.
In the UE, this timer shall be started when the successful or unsuccessful transmission of the last STATUS PDU
of an acknowledgement status report is indicated by lower layer.
Reference
TS 25.331 clause 8.6.4.9, 25.322 clause 9.5.
To verify that the UE starts to use the new set of RLC parameters when an already established AM RLC radio bearer is
reconfigured.
Initial conditions
Release 5 252 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (AM_7_PayloadSize) - 1 bytes.
Test procedure
a) After establishing the radio bearer with default settings, SS reconfigures RLC parameters for an AM RLC entity
by sending a RADIO BEARER RECONFIGURATION RRC message to the UE.
b) Let T
poll
be the value of the Timer_Poll_Periodic timer, T
pro
the value of the Timer_Status_Prohibit timer, and
T
per
the value of the Timer_Status_Periodic timer.
c) The SS transmits at least 2 * T
poll
/ TTI SDUs of size AM_7_PayloadSize - 1 bytes.
d) Whilst transmitting, the SS monitors the uplink for a STATUS PDU and notes the time. This time will be
recorded as T
1
.
e) The SS sets the P bit in one of the next floor(T
pro
/TTI) PDUs transmitted on the downlink.
f) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T
2
.
g) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set, but does not
respond. This time will be recorded as T
3.

h) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set.
4
.
Release 5 253 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 RADIO BEARER RECONFIGURATION RRC
COMPLETE
RRC
4


7 DOWNLINK RLC PDU Poll

8


9 DOWNLINK RLC PDU SDU m +ceil(Tpro / TTI)
11 DOWNLINK RLC PDU SDU ceil(2Tpoll/TTI)

14


15 UPLINK RLC PDU SN =ceil(Tpoll/TTI), First Poll: Note T3
16 UPLINK RLC PDU SN =ceil(Tpoll/TTI)+1

17


18 UPLINK RLC PDU Second Poll: Note T4
18a STATUS PDU
18b SS continues to receive PDUs,
and acknowledged

Specific message contents
RADIO BEARER RECONFIGURATION (step 1)
The default RADIO BEARER RECONFIGURATION message as defined in TS 34.108 is used, except for the
following:
RB information to reconfigure list
- RB information to reconfigure
- RB identity Refererring to the radio
bearer defined for AM 7-bit
"Length Indicator" tests in
clause 7.2.3.1.
- Downlink RLC Info
- Timer_Status_Prohibit 500
- Timer_STATUS_periodic 200
- Uplink RLC Info
- Polling info
- Last retransmission PDU poll FALSE
- Last transmission PDU poll FALSE
- Timer_poll 600
- Timer_Poll_Periodic 1000

Release 5 254 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The measured time T
2
T
1
shall be 500 ms.
The measured time T
4
T
3
shall be 600 ms.
7.3 PDCP
7.3.1 General
7.3.1.1 General assumptions
If not otherwise mentioned, the same procedures as used in RRC test specification (TS 34.123-1) or in the Generic
procedure (TS 34.108) applies to reach Initial conditions for PDCP testing. In this test description, common test
sequences for PDCP (clause 7.3.1.2) are defined and are applied either as preamble or post amble to establish or release
a Packet Switched (PS) connection for a test case.
If not explicitly described, the same message contents and settings are applied as described in the RRC test description
default settings.
Detailed IP header compression coding mechanism as well as mechanism related error recovery and packet reordering
described in IETF RFC 2507 are not verified.
For PDCP testing TCP/IP data type and UDP/IP data type as Non-TCP/IP data types are applied for IP data.
The IP data packet size shall be limited to 1500 bytes as defined in 3GPP TS 23.107, clause 6.5.1and 6.5.2 (range of
QoS attributes).
An UE supporting IP Header compression protocol RFC 2507 shall be capable to store a header compression context of
at least 512 bytes (Integer).
It shall be possible to reconfigure PDCP settings while UE test loop mode 1. With the applied test method using UE test
loop mode 1, the UE as Originator and Receiver of PDCP SDUs (concurrent transmission) is tested.
7.3.1.2 Common Test sequences and Default message contents for PDCP
General
The settings and parameter used in the "Common Test sequences for PDCP" are described in the "Default PDCP
Message Contents". If not explicitly shown there, the message contents are identical with the default contents for the
same message type of layer 3 messages for RRC tests, to establish a packet switched session or connection. The
contents of test case specific message parameters are described in the test case (Expected Sequence). If not explicitly
shown, default settings and parameter are used as message content for all Common Test sequences.
7.3.1.2.1 Common Test sequences for PDCP
7.3.1.2.1.1 Setup a UE terminated PS session using IP Header compression in AM RLC (using
UE Test loop test mode 1)
Initial Conditions
UE is in Idle mode.
Test procedure
After having received the System Information, the SS starts to setup a RRC connection. After connection establishment
and Radio Bearer Setup, the UE test loop mode 1 is activated and the UE test loop mode 1 is closed.
Release 5 255 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected Sequence
UE SS
2 PAGING TYPE 1 CN domain identity: PS domain
Paging cause: interactive session
4 RRC CONNECTION SETUP Connection Setup message PS sessions in AM
RLC used in RRC testing matches here
5 RRC CONNECTION SETUP COMPLETE
6 ACTIVATE RB TEST MODE
7 ACTIVATE RB TEST MODE COMPLETE
8 RADIO BEARER SETUP The Radio Bearer configuration is as described
in TS 34.108, clause 6.10, Prioritised RAB No.
23: QoS parameter: Traffic Class: Interactive or
Background, max. UL:64 kbps max. DL:64 kbps,
Residual BER as described in TS 34.108,
clause: 6.10.
9 RADIO BEARER SETUP COMPLETE
10 CLOSE UE TEST LOOP The SS initiates UE test loop mode 1, indicated
by the Parameter: "UE test loop mode" 1
(X1=0 and X2=0)
The "DCCH dummy transmission" not used:
disabled: (Y1=0)
11 CLOSE UE TEST LOOP COMPLETE After having received the test mode
acknowledgement, the UE test loop mode 1 is
activated.

The contents of test case specific message parameters are described in the test case (Expected Sequence). Default
contents of messages are described in the clause Default PDCP Message Contents.
7.3.1.2.1.2 Setup a UE terminated PS session using IP Header compression in UM RLC (using
UE Test loop test mode 1)
Initial Conditions
UE is in idle mode.
Test procedure
Release 5 256 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected Sequence
UE SS
2 PAGING TYPE 1 CN domain identity: PS domain
Paging cause: interactive session
4 RRC CONNECTION SETUP Connection Setup message PS sessions in UM
RLC used in RRC testing matches here
8 RADIO BEARER SETUP The Radio Bearer configuration is as described
in TS 34.108, clause 6.10, Prioritised RAB No.
23: QoS parameter: Traffic Class: Interactive or
Background, max. UL:64 kbps max. DL:64 kbps,
Residual BER as described in TS 34.108,
clause: 6.10.
by the Parameter: "UE test loop mode"1 (X1=0
and X2=0)
disabled: (Y1=0)
activated.

The contents of test case specific message parameters are described in the test case (Expected Sequence) Default
7.3.1.2.1.3 Deactivate a UE terminated PS session using IP Header compression (using UE test
loop mode 1)
Initial Conditions
UE is in connected mode, a UE test loop mode 1 for PDCP is activated, and the UE loop mode 1 is "closed".
Test procedure
The UE opens the UE test loop mode 1, deactivates the test mode and the PS session, releases the Radio Bearer and
enters Idle mode.
Expected Sequence
UE SS
1 OPEN UE TEST LOOP The SS terminates the UE test loop mode 1,
(see described parameter)
2 OPEN UE TEST LOOP COMPLETE After having received the test mode
acknowledgement, the test loop mode 1 is
deactivated.
3 DEACTIVATE RB TEST MODE SS deactivates the RB test mode
4 DEACTIVATE RB TEST MODE
COMPLETE
UE shall confirm the previous message.
Afterwards, the UE returns to normal operation
5 RRC CONNECTION RELEASE SS terminates the connection
6 RRC CONNECTION RELEASE
COMPLETE
UE confirms the connection release and returns
to Idle mode

Release 5 257 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The contents of test case specific message parameter is described in the test case (Expected Sequence). Default contents
of messages are described in the clause Default PDCP Message Contents.
7.3.1.2.1.4 Activate closed UE test loop mode 1
Initial Conditions
UE is in Idle mode.
Test procedure
Expected Sequence
UE SS
by the Parameter: "UE test loop mode" 1
(X1=0 and X2=0)
disabled: (Y1=0)
activated.

The contents of test case specific message parameters are described in the test case (Expected Sequence). Default
7.3.1.2.2 Default PDCP Message Contents
This clause contains the default values of RRC messages used for PDCP testing, other than those specified in TS 34.108
clauses 6 and 9, and default values of PDCP messages. Unless indicated otherwise in specific test cases, only PDCP
related specific message contents are described here which shall be transmitted by the system simulator in RRC
messages, and which are required to be received from the UE under test. If not explicitly described, the message
contents are identical with the default contents for the same message type of layer 3 messages for RRC tests, to
establish a packet switched session or connection.
The necessary L3 messages are listed in alphabetic order, with the exception of the SYSTEM INFORMATION
messages, where it is the information elements which are listed in alphabetic order (this is because some information
elements occur in several SYSTEM INFORMATION types).
In this clause, decimal values are normally used. However, sometimes a hexadecimal value, indicated by an "H", or a
binary value, indicated by a "B" is used.
Default SYSTEM INFORMATION:
NOTE: SYSTEM INFORMATION BLOCK TYPE 1 (except for PLMN type "GSM-MAP"), SYSTEM
INFORMATION BLOCK TYPE 8, SYSTEM INFORMATION BLOCK TYPE 9, SYSTEM
INFORMATION BLOCK TYPE 10, SYSTEM INFORMATION BLOCK TYPE 14, SYSTEM
INFORMATION BLOCK TYPE 15 and INFORMATION BLOCK TYPE 16 messages are not used.
Release 5 258 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Contents of CONNECTION SETUP message:
Capability update requirement
- UE radio access capability update requirement TRUE
- System specific capability update requirement
list
UE only supports 1 system

Contents of CONNECTION SETUP COMPLETE message:
UE radio access capability Value will be checked. Stated capability must be
compatible with 34.123-2 (c.f. PICS/PIXIT statements in
GSM) and the user settings
- Conformance test compliance
- PDCP Capability
- Max PDCP SN
- Support of lossless SRNS relocation
- Support for RFC2507
- Max HC context space

(TCP_SPACE +NON_TCP_SPACE))
- RLC Capability
- Transport channel capability
- RF Capability
- Physical channel capability
- UE multi-mode/multi-RAT capability
- Security Capability
- LCS Capability
- Measurement capability
UE system specific capability Value will be check. UE must include the classmark
information for the supported system

Contents of RB RECONFIGURATION COMPLETE message:
- Downlink counter syncronisation info
- RB with PDCP information list
- RB with information
Value will be checked. Stated capability must be

Contents of ACTIVATE RB TEST MODE message:
Protocol Discriminator TS 24.007, 11.2.3.1.1
Skip indicator TS 24.007, 11.2.3.1.2
Message type 01000100B

Contents of ACTIVATE RB TEST MODE COMPLETE message:

Contents of DEACTIVATE RB TEST MODE message:

Release 5 259 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Contents of DEACTIVATE RB TEST MODE COMPLETE message:

Contents of CLOSE UE TEST LOOP message:
UE test loop mode 000000100B (X2=0 and X1=0 for UE test mode 1, Y1=0
DCCH dummy transmission disabled)
UE test loop mode 1 LB setup
- Length of UE loop mode 1 LB setup IE
- LB setup list
- LB setup RAB subflow #1
- Z13Z0 (Uplink RLC SDU size in bits)

4 octets

016383 (binary coded, Z13 most significant bit); value
as negotiated

Contents of CLOSE UE TEST LOOP COMPLETE message:

Contents of OPEN UE TEST LOOP message:
IE Identifier (only in AM) 1000xxxx

Contents of OPEN UE TEST LOOP COMPLETE message:

7.3.2 IP Header Compression and PID assignment
7.3.2.1 UE in RLC AM
7.3.2.1.1 Transmission of uncompressed Header
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences. The UE
shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
1. The Packet Data Convergence Protocol shall perform the following functions:
- transfer of user data. This function is used for conveyance of data between users of PDCP services.
Release 5 260 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol),
the PDCP sublayer shall be able to:
- identify the correct header compression protocol; and
- distinguish different types of header compression packets within a header compression protocol.
The mapping of the PID values shall follow the general rules listed below:
- PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its
Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver;
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
The test case consists of two test procedures:
The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header
compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used
for uncompressed IP header packets, if no IP header compression is configured by higher layers.
1. To verify, that the UE transmits and receives in acknowledged mode (RLC AM) TCP/IP and UDP/IP data
packets without IP header compression as configured by higher layers.
2. To verify, that PID assignment rules are correctly applied, if usage of "PDCP Data" PDU are negotiated, i.e. the
UE shall recognize PID value =0 for a received TCP/IP and UDP/IP data packet and it shall use PID=0 to
transmit IP data packets, if no IP header compression is negotiated. If usage of "PDCP No Header" PDU is
negotiated, no PID assignment is used for transmitting and receiving TCP/IP and UDP/IP data packets.
Initial conditions
UE is in idle mode.
Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured.
Test procedure 2: No IP header compression is configured.
Support of PS Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: Test_PDCP_UDP/IP_Packet1
Test procedure 1: Transmission of uncompressed IP header packets using PDCP Data PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC AM using
Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data" PDU has been
configured by higher layers.
b) The SS sends a TCP/IP data packet with uncompressed IP Header.
c) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PDCP PDU type
and shall handle the received data packet with the appropriate decoding method. Then it forwards the data to its
Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration using
PDCP Data PDU.
Release 5 261 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
d) The SS receives and decodes the TCP/IP data packet. The decoded data packet shall be identical with the data
as sent before.
e) Step b) to d) shall be repeated by using a UDP/IP data packet with uncompressed IP Header.
The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
UE SS
Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1)
The SS creates a TCP/IP packet without IP
header compression (PDCP Data PDU).

1 PDCP Data The SS sends a PDCP Data PDU using the
RLC-AM-Data-Request Primitive with the
following content to the UE:
PDU type =000 (PDCP Data PDU)
PID =0 (uncompressed IP header)
data: below described TCP/IP packet

After having received the PDCP Data PDU, the
UE decodes the PDU and recognizes PID value
=0 (no IP header compression)
Therefore, no IP header decompression is
applied for this packet.

The data packet is forwarded via PDCP-SAP to
its Radio Bearer Loop Back (RB LB) entity.

The RB LB entity in UE test loop mode 1 returns
the received data packet and sends it back to its
PDCP entity.

Release 5 262 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
2 PDCP Data The UE sends a PDCP Data PDU using the
following content back to the SS:
data: previously received TCP/IP packet

After reception of this TCP/IP data packet, the
SS applies the appropriate decoding function for
the received data

The SS creates a UDP/IP packet without IP

data: below described UDP/IP packet

UE decodes the PDU and recognizes with PID
value =0, there was no IP header compression
applied for the UDP/IP packet.

the Radio Bearer Loop Back
(RB LB) entity.

PDCP entity.

data: previously received UDP/IP packet

After reception of this UDP/IP data packet, the
SS decodes the received data
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1)

RRC CONNECTION SETUP message
The contents of the RRC CONNECTION SETUP message applied in the preamble "Setup a UE terminated PS
session using IP Header compression in AM RLC" of this test case is identical to those of the default contents of layer 3
messages for RRC tests [TS 34.123-1] (PS connection for AM) with the following exceptions:
- UE radio access capability update requirement

TRUE
NOTE: Value will be checked. Stated capability must be

Release 5 263 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
RADIO BEARER SETUP message
The contents of the RADIO BEARER SETUP message applied in the preamble "Setup a UE terminated PS session
using IP Header compression in AM RLC" of this test case is identical to those of the default contents of layer 3
messages for RRC tests [TS 34.123-1] (PS connection for AM) which fits to the below described parameters with the
RAB information for setup
- RAB info
- RAB identity

- CN domain identity
- RB information to setup
- RB identity
- PDCP info

- PDCP PDU header
- RLC info
- Downlink RLC mode
- Uplink RLC mode

No. #23 as described in TS 34.108, Table 6.10.2.1.1
Prioritised RABs.
QoS parameter:
Traffic Class: Interactive or Background,
max. UL: 64 kbps and max. DL: 64 kbps as described in
TS 34.108, including described physical channel
parameters, configuration for AM RLC

Residual BER as described in TS 34.108, clause: 6.10
Related Signalling RB UL: 3.4 kbps, DL: 3.4 kbps
DCCH, No. #2 (as described in TS 34.108)

PS domain

20

False
(IE "Support of lossless SRNS relocation" only present,
if RLC "In-sequence delivery" is TRUE and in AM)
present

(AM RLC)
(AM RLC)

Content of PDCP Data PDU (Step 1)
PDU type
PID
Data
000
00000 (No header compression, PID =0)
PDCP test data type #1: TCP/IP data packet without IP
header compression with any data content. The data
shall be limited to 1500 bytes.

PDU type
PID
Data
000
PDCP test data type #2: UDP/IP data packet without IP

Test procedure 2: Transmission of uncompressed IP header packets using No Header PDU
Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP No Header" PDU has
been configured by higher layers.
Release 5 264 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PDCP No Header PDU.
as sent before.
f) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
UE SS
header compression (PDCP No Header PDU).

1 PDCP No Header The SS sends a PDCP No Header PDU using
the RLC-AM-Data-Request Primitive with the

After having received the PDCP No Header
PDU, the UE decodes the PDU and recognizes,
there was no PID applied for the TCP/IP packet.
Therefore, no IP header decompression shall be
applied for this packet. Then, the data packet is
forwarded via PDCP-SAP to the Radio Bearer
Loop Back (RB LB) entity.

PDCP entity.

2 PDCP No Header The UE sends a PDCP No Header PDU using

the received data


Release 5 265 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS

there was no PID applied for the UDP/IP packet.

PDCP entity.


Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1).


TRUE

Release 5 266 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
messages for RRC tests [TS 34.123-1] (PS connection for AM) which fits to the below described parameters with the
- RAB info
- RAB identity

- RB identity
- PDCP info

- PDCP PDU header
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

20

False
absent

(AM RLC)
(AM RLC)

Content of PDCP No Header PDU (Step 1)
Data PDCP test data type #1: TCP/IP data packet without IP

Data PDCP test data type #2: UDP/IP data packet without IP

1. Test requirements: Transmission of uncompressed IP header packets using PDCP Data PDU
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received
and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negotiated by
the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
2. Test requirements: Transmission of uncompressed IP header packets using PDCP No Header PDU
and handled correctly (PDCP No Header PDU). This verifies, that the PDCP configuration on UE side works as
negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
Release 5 267 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.2.1.2 Transmission of compressed Header
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP
entity which applies IP header compression protocol RFC 2507.
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol),
the PDCP sublayer shall be able to:
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
1. To verify, that the UE transmits and receives in acknowledged mode (RLC AM) TCP/IP and UDP/IP data
packets by using IP header compression protocol as described in RFC2507 as configured by higher layers.
2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID
value for the applied optimisation method for transmitting and receiving TCP/IP and UDP/IP data packets.
Initial conditions
UE is in Idle mode. Usage of "PDCP Data" PDU and IP header compression is configured.
Support of IP header compression protocol RFC 2507 - YES/NO.
Test procedure
b) The SS sends a "normal" TCP/IP data packet (no compression packet type), PID=0.
Release 5 268 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
c) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
handle the received data packet with the correct decompression protocol. Then, it forwards the data to its Radio
Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
d) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
shall be identical with the data as sent before.
e) The SS sends a TCP/IP data packet with packet type: Full_Header, PID=1.
NOTE: According to the compression protocol RFC 2507, this is necessary to transmit the created CONTEXT
and the assigned CID.
f) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
g) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
h) The SS sends a TCP/IP data packet with packet type: Compressed_TCP, PID=2.
i) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
j) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
k) Step b) to d) is repeated for a "normal" UDP/IP data packet, PID=0.
l) Step e) to g) is repeated for a UDP/IP data packet with packet type: Full_Header, PID=1.
m) The SS sends a UDP/IP data packet with packet type: Compressed_non_TCP, PID=4.
n) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
o) The SS receives and decodes the UDP/IP data packet according to the inserted PID. The decoded data packet
p) The SS deactivates the UE tests loop mode 1 and terminates the connection.
Release 5 269 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
header compression.




PDCP entity.

PID value =0 to 3

SS applies the appropriate decoding function
depending on the assigned PID.

PID =1 (Full_Header packet type [TCP/IP])

UE decodes the PDU, recognizes PID value =1
applied for this TCP/IP data packet and
decompresses it with the appropriate method.

PDCP entity.
Release 5 270 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
PID value =0 to 3


PID =2 (Compressed_TCP packet type)

decompress it with the appropriate method. The
data packet is forwarded via PDCP-SAP to its
Radio Bearer Loop Back (RB LB) entity.

PDCP entity.
PID value =0 to 3


The SS creates a UDP/IP packet without
compressed IP header compression.

(RB LB) entity.

PDCP entity.

Release 5 271 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
PDU type =000 (Data PDU with Header)
PID value =0,1 or 4 (depending on which
UDP/IP header format is used by the UE)


Release 5 272 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
PID =1 (Full_Header packet type)
=1 applied for this UDP/IP data packet and
decompress it with the appropriate method.

(RB LB) entity.

PDCP entity.



PID =4 (Compressed _non-TCP packet type)

(RB LB) entity.

PDCP entity.




Release 5 273 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

TRUE

messages for RRC tests [TS 34.123-1] (PS connection for AM) which fit to the here described parameters with the
- RAB info
- RAB identity

- RB identity
- PDCP info

- PDCP PDU header
- Header compression information
CHOICE algorithm type
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

20

False
present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)
reordering not expected (Default)

(AM RLC)
(AM RLC)

Release 5 274 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PDU type
PID
Data
000

PDU type
PID
Data
000
00001 (Full_Header, PID =1)
PDCP test data type #1: TCP/IP data packet with full
TCP/IP header with any data content. The data shall be
limited to 1500 bytes.

PDU type
PID
Data
000
00010 (Compressed_TCP, PID =2)
PDCP test data type #1: TCP/IP data packet with a
compressed header with any data content. The data

PDU type
PID
Data
000

PDU type
PID
Data
000
PDCP test data type #2: UDP/IP data packet with full
UDP/IP header with any data content. The data shall be

PDU type
PID
Data
000
00100 (Compressed_non-TCP, PID =4)
PDCP test data type #2: UDP/IP data packet with a

Release 5 275 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
and handled with the correct compression protocol. This verifies, that the PDCP configuration on UE side works as
7.3.2.2 UE in RLC UM
7.3.2.2.1 Transmission of uncompressed Header
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
- transfer of user data. This function is used for conveyance of data between users of PDCP services
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor
protocol), the PDCP sublayer shall be able to:
The mapping of the PID values shall follow the general rules listed below:
- PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its
Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver;
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
The test case consists of two test procedures:
The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header
compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used
for uncompressed IP header packets, if no IP header compression is configured by higher layers.
1. To verify, that the UE transmits and receives in unacknowledged mode (RLC UM) TCP/IP and UDP/IP data
packets without IP header compression as configured by higher layers.
2. To verify, that PID assignment rules are correctly applied, if usage of "PDCP Data" PDU are negotiated, i.e. the
UE shall recognize PID value =0 for a received TCP/IP and UDP/IP data packet and it shall use PID=0 to
transmit IP data packets, if no IP header compression is negotiated. If usage of "PDCP No Header" PDU is
negotiated, no PID assignment is used for transmitting and receiving TCP/IP and UDP/IP data packets.
Initial conditions
UE is in Idle mode.
Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured.
Release 5 276 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure 2: no IP header compression is configured.
Test procedure 1: Transmission of uncompressed IP header packets using PDCP Data PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC UM using
PDCP Data PDU.
as sent before.
The SS deactivates the UE test loop mode and terminates the connection.
Release 5 277 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
Setup a UE terminated PS session using IP Header compression in UM RLC (using UE test loop mode 1)

RLC-UM-Data-Request Primitive with the



PDCP entity.


the received data


Release 5 278 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS


(RB LB) entity.

PDCP entity.



session using IP Header compression in UM RLC" of this test case is identical to those of the default contents of layer 3
messages for RRC tests [TS 34.123-1] (PS connection for UM) with the following exceptions:

TRUE

Release 5 279 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
using IP Header compression in UM RLC" of this test case is identical to those of the default contents of layer 3
messages for RRC tests [TS 34.123-1] (PS connection for UM) which fits to the below described parameters with the
- RAB info
- RAB identity

- RB identity
- PDCP info
- PDCP PDU header
- RLC info
- Downlink RLC mode

Prioritised RABs.
QoS parameter:
parameters, configuration for UM RLC


PS domain

21

present

(UM RLC)

PDU type
PID
Data
000

PDU type
PID
Data
000

Release 5 280 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test procedure 2: Transmission of uncompressed IP header packets using No Header PDU
Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP No Header" PDU has
been configured by higher layers.
PDCP No Header PDU.
as sent before.
f) The SS deactivates the Loop back test mode and terminates the connection.
Expected sequence
UE SS

the RLC-UM-Data-Request Primitive with the

there was no PID applied for the TCP/IP packet.

PDCP entity.


the received data


Release 5 281 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS

there was no PID applied for the UDP/IP packet.

PDCP entity.




TRUE

Release 5 282 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
messages for RRC tests [TS 34.123-1] (PS connection for UM) which fits to the below described parameters with the
- RAB info
- RAB identity

- RB identity
- PDCP info

- PDCP PDU header
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

21

False

absent

(UM RLC)
(UM RLC)

Data PDCP test data type #1: TCP/IP data packet without IP

Data PDCP test data type #2: UDP/IP data packet without IP

1. Test requirements: Transmission of uncompressed IP header packets using PDCP Data PDU
and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negotiated by
2. Test requirements: Transmission of uncompressed IP header packets using PDCP No Header PDU
and handled correctly (PDCP No Header PDU). This verifies, that the PDCP configuration on UE side works as
Release 5 283 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.2.2.2 Transmission of compressed Header
The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP
entity which applies IP header compression protocol RFC 2507.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
1. To verify, that the UE transmits and receives in unacknowledged mode (RLC UM) TCP/IP and UDP/IP data
packets by using IP header compression protocol as described in RFC2507 as configured by higher layers.
2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID
value for the applied optimisation method for transmitting and receiving TCP/IP and UDP/IP data packets.
Initial conditions
UE is in Idle mode. Usage of "PDCP Data" PDU and no IP header compression is configured.
Support of IP header compression protocol RFC 2507 - YES/NO
Test procedure
Release 5 284 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
e) The SS sends a TCP/IP data packet with packet type: Full_Header, PID=1.
NOTE: According to the compression protocol RFC 2507, this is necessary to transmit the created CONTEXT
and the assigned CID.
g) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
h) The SS sends a TCP/IP data packet with packet type: Compressed_TCP, PID=2.
i) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
j) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
k) Step b) to d) is repeated for a "normal" UDP/IP data packet, PID=0.
l) Step e) to g) is repeated for a UDP/IP data packet with packet type: Full_Header, PID=1.
m) The SS sends a UDP/IP data packet with packet type: Compressed_non_TCP, PID=4.
n) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
o) The SS receives and decodes the UDP/IP data packet according to the inserted PID. The decoded data packet
p) The SS deactivates the UE test loop test mode and terminates the connection.
Release 5 285 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
header compression.




PDCP entity.

PID value =0 to 3



decompresses it with the appropriate method.

Release 5 286 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
PDCP entity.

PID value =0 to 3


PID =2 (Compressed_TCP packet type)

decompress it with the appropriate method. The
data packet is forwarded via PDCP-SAP to its
Radio Bearer Loop Back (RB LB) entity.

PDCP entity.
PID value =0 to 3


The SS creates a UDP/IP packet without
compressed IP header compression.

(RB LB) entity.

PDCP entity.

Release 5 287 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS


PID =1 (Full_Header packet type)


(RB LB) entity.

PDCP entity.



PID =4 (Compressed _non-TCP packet type)

(RB LB) entity.

PDCP entity.

Release 5 288 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS




TRUE

Release 5 289 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
messages for RRC tests [TS 34.123-1] (PS connection for UM) which fit to the here described parameters with the
- RAB info
- RAB identity

- RB identity
- PDCP info

- PDCP PDU header
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

21

False

present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)

(UM RLC)
(UM RLC)

PDU type
PID
Data
000

PDU type
PID
Data
000
TCP/IP header with any data content. The data shall be

Release 5 290 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PDU type
PID
Data
000
00010 (Compressed_TCP, PID =2)
PDCP test data type #1: TCP/IP data packet with a

PDU type
PID
Data
000

PDU type
PID
Data
000
PDCP test data type #2: UDP/IP data packet with full
UDP/IP header with any data content. The data shall be

PDU type
PID
Data
000
00100 (Compressed_non-TCP, PID =4)
PDCP test data type #2: UDP/IP data packet with a

and handled with the correct compression method. This verifies, that the PDCP configuration on UE side works as
7.3.2.2.3 Extension of used compression methods
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity
which applies IP header compression protocol: RFC 2507.
- transfer of user data. Transmission of user data means that PDCP receives PDCP SDU from the NAS and
forwards it to the RLC layer and vice versa;
Release 5 291 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3. The mapping of the PID values shall follow the general rules listed below:
- PID values are re-mapped for the PDCP entity after any reconfiguration of the header compression protocols
for that entity.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1
TS 25.323 clause 5.1.1.
1. To verify, that the UE is able to handle an extended PID value allocation table by header compression protocol
IETF RFC 2507 after PDCP reconfiguration as configured by RRC.
Initial conditions
Test procedure
Common test procedures for mobile terminated PS switched sessions (with the UE test loop mode 1). Usage of
"PDCP Data PDU" and no optimisation method has been configured by higher layers.
b) The SS sends a TCP/IP data packet (no compression packet type), PID=0.
handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity.
The received data shall be returned by the UE via its PDCP configuration.
e) The SS reconfigures (using RRC Radio Bearer Reconfiguration message) the PDCP entity by extending the PID
value allocation table and therefore the applied optimisation method with the IP header compression protocol
RFC 2507. The UE test loop mode 1 in RLC UM is still active.
f) The SS sends a TCP/IP data packet (no compression packet type), PID=0.
Release 5 292 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
g) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
h) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
i) The SS sends a TCP/IP data packet with packet type: Full_Header, PID=1.
j) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
k) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
l) The SS deactivates the UE test loop mode and terminates the connection.
Release 5 293 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
header compression.




PDCP entity.

PID value =0

3 RRC RADIO BEARER
RECONFIGURATION
SS extends the "PID value allocation table" with
IP header compression PID (RFC 2507) in the
UE.

4 RRC RADIO BEARER
UE acknowledges its new settings
PID =0 (normal packet type [TCP/IP])
data: below described TCP/IP packet.



PDCP entity.

Release 5 294 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
PID value =0 to 3


=1 applied for this TCP/IP data packet and shall


PDCP entity.

PID value =0 to 3


RRC RADIO BEARER RECONFIGURATION message
The contents of the RRC RADIO BEARER RECONFIGURATION message applied in the preamble "Setup a UE
terminated PS session using IP Header compression in UM RLC" of this test case is identical to those of the default
contents of layer 3 messages for RRC tests [TS 34.123-1] (PS connection for UM) with the following exceptions:
RB information to reconfigure
- PDCP info
- PDCP PDU header
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
1

present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)

Release 5 295 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The contents of the RRC CONNECTION SETUP message applied in the preamble "Setup a UE terminated PS session

TRUE

- RAB info
- RAB identity

- RB identity
- PDCP info
- PDCP PDU header
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

21

present

(UM RLC)
(UM RLC)

Content of PDCP Data PDU (Step 1 and 5)
PDU type
PID
Data
000

PDU type
PID
Data
000

Release 5 296 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
After PDCP reconfiguration, the UE shall return the TCP/IP data packets as indication, that the extension of used
optimisation method are applied by UE. This verifies, that the PDCP configuration on UE side works as negotiated by
7.3.2.2.4 Compression type used for different entities
Applicable only for an UE supporting the establishment of more than one PDCP entity in parallel, i.e. it shall be
possible to configure more than one Radio Bearer Loop Back entities (each PDCP entity are assigned via PDCP-SAP to
its own Radio Bearer Loop Back entity).
Applicable for all UEs supporting two Radio Bearers in RLC UM and RLC AM as described in this test case, clause
7.3.2.2.4.6 Combined PDCP Acknowledged and Unacknowledged mode configuration.
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore it shall apply IP header
compression protocol RFC 2507.
3. The mapping of the PID values shall follow the general rules listed below:
- PID values shall be mapped to the different packet types independently at each PDCP entity;
Several PDCP entities may be defined for a UE with each using the same or different protocol type. In this version of
the specification, only one header compression protocol type, RFC 2507 [6], is supported.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
TS 25.323 clause 4.2.
1. To verify, that a configured IP header compression protocol are applied to compress and decompress TCP/IP
data packets by several PDCP entities in parallel, if more than one entities are established, i.e. the UE uses the
same PID to transmit two TCP/IP data packets with the same content in parallel using two Radio Bearer
configurations.
NOTE: For this test case, the SS shall be configured to handle more than one received PDCP messages.
Initial conditions
UE is in Idle mode. Usage of "PDCP Data" PDU and IP header compression is configured for both PDCP entities.
Release 5 297 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Establishment of more than one PDCP entities - YES/NO.
Support of UM RB and AM RB
IXIT: Test_PDCP_TCP/IP_Packet1
Test procedure
a) The SS setups a packet switched session including two radio bearer configurations in parallel in UE test loop
mode 1 and in RLC UM and RLC UM using Common test procedures for mobile terminated PS switched
sessions. Usage of IP header compression protocol RFC 2507 has been configured by higher layers.
b) The SS sends two successive "normal" TCP/IP data packet, PID=0 via both PDCP configurations to their peer
entities.
c) After having received the TCP/IP data packets, the PDCP entities of the UE shall recognize the PID value and
shall handle the received data packet independent of the used PID with the correct decompression method. Then
they forward the data to their Radio Bearer Loop Back entity. Both received data shall be returned by each Radio
Bearer Loop Back entity.
d) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall
be identical with the data as sent before.
e) The SS sends two successive TCP/IP data packets with full header (PID=1) via both PDCP configurations to
their peer entities.
f) After having received the TCP/IP data packets, the PDCP entities of the UE shall recognize the PID value and
shall handle the received data packets independent of the used PID with the correct decompression method. Then
they forward the data to their Radio Bearer Loop Back entity. Both received data shall be returned by each Radio
Bearer Loop Back entity.
g) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall
h) The SS deactivates the UE test loop mode and terminates the connection.
Release 5 298 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
1 PDCP Data The SS sends two successive PDCP Data
PDUs using the RLC-UM-Data-Request
Primitive via both PDCP entities with the
following contents to the UE:

After having received both PDCP Data PDUs,
the UE decodes each PDU and recognizes PID
value =0 (no IP header compression applied for
both TCP/IP data packets).

Although the same PID is used for both PDUs,
the UE shall handle they with the correct
method and it forwards both data packets via
PDCP-SAPs to their Radio Bearer Loop Back
(RB LB) entities.

The RB LB entities in UE test loop mode 1
return the received data packets and send they
back to their PDCP entities.

Release 5 299 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
2 PDCP Data The UE sends back for each PDCP
configuration a PDCP Data PDU using the RLC-
UM-Data-Request Primitive with the following
content back to the SS:
PID value =0 to 3

After reception of TCP/IP data packets, the SS
applies the appropriate decoding function for
both received messages depending on which
PID was assigned to the received data
3 PDCP Data The SS sends two successive PDCP Data
PDUs using the RLC-UM-Data-Request
Primitive via both PDCP entities with the
following contents to the UE:

After having received both PDCP Data PDUs,
the UE decodes each PDU and recognizes PID
value =1 (Full_Header packet type applied for
both TCP/IP data packets).

Although the same PID is used for both PDUs,
the UE shall handle they with the correct
method and it forwards both data packets via
PDCP-SAPs to their Radio Bearer Loop Back
(RB LB) entities.

The RB LB entities in UE test loop mode 1
return the received data packets and send they
back to their PDCP entities.

4 PDCP Data The UE sends back for each PDCP
configuration a PDCP Data PDU using the RLC-
UM-Data-Request Primitive with the following
content back to the SS:
PID value =0 to 3

After reception of TCP/IP data packets, the SS
applies the appropriate decoding function for
both received messages depending on which
PID was assigned to the received data


TRUE

Release 5 300 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RAB info
- RAB identity

- RB identity
- PDCP info
- PDCP PDU header
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
- RLC info
- Downlink RLC mode
- Uplink RLC mode

- RB identity
- PDCP info
- PDCP PDU header
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:
parameters, configuration for UM RLC configuration for
UM RLC


PS domain

20

present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)

(AM RLC)
(AM RLC)
(NOTE: for RB ID 21, the same RAB configurations are
used (No. #23 as described in TS 34.108) as described
for RB ID 20)
21

present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)

(UM RLC)
(UM RLC)

Release 5 301 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Content of both PDCP Data PDU (Step 1)
PDU type
PID
Data
000

Content of both PDCP Data PDU (Step 3)
PDU type
PID
Data
000
TCP/IP header compression with any data content. The
data shall be limited to 1500 bytes.

The UE shall return both TCP/IP data packets as indication that the previous received data packets associated with the
same PID value are handled in parallel with the same decompression protocol. This verifies, that more than one PDCP
configuration on UE side using the same compression protocol is able to apply it in parallel. An invalid PDU type as
well as unconfigured PID values shall not be received by SS.
7.3.2.2.4.6 Combined PDCP Acknowledged and Unacknowledged mode configuration
This configuration is based on the interactive or background / UL:64 DL 64 kbps / PS RAB. The SRB configurations
are UL:3.4 DL:3.4 kbps for DCCH aligned to this combined RABs are described for SRB DL 3.4 kbps in TS 34.108,
clause 6.10.2.4.1.2.2 and for SRB DL 3.4 kbps in TS 34.108, clause 6.10.2.4.1.2.1. The TFCS refer to TS34.108, clause
6.10.2.4.1.24.1.1.3 for UL and clause 6.10.2.4.1.25.2.1.3 for DL, the Physical channel parameters refer to TS 34.108,
clause 6.10.2.4.1.24.1.2 for UL clause 6.10.2.4.1.25.2.2 and for DL accordingly. The configuration is applied to PDCP
test cases using both the acknowledged and unacknowledged mode.
Table 7.3.2.2.4/1: Uplink Transport channel parameter for combined RABs PS AM_UM
Higher
layer
RAB/Signalling RB RAB #20 RAB #21
RLC Logical channel type DTCH DTCH
RLC mode AM UM
Payload sizes, bit 316 324
Max data rate, bps 63200 64800
TrD PDU header, bit 16 8
MAC MAC header, bit 4
MAC multiplexing 2 logical channel multiplexing
TB sizes, bit 336
TFS TF0, bits 0x336
TF1, bits 1x336
TF2, bits 2x336
TF3, bits 3x336
TF4, bits 4x336
TTI, ms 20
Coding type TC
CRC, bit 16
Max number of bits/TTI after channel coding 4236
Uplink: Max number of bits/radio frame before
rate matching
2118

Release 5 302 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Table 7.3.2.2.4/2: Downlink Transport channel parameter for combined RABs PS AM_UM
Higher
layer
RAB/Signalling RB RAB #20 RAB #21
RLC Logical channel type DTCH DTCH
RLC mode AM UM
Payload sizes, bit 316 324
TrD PDU header, bit 16 8
MAC MAC header, bit 4
TB sizes, bit 336
TFS TF0, bits 0x336
TF1, bits 1x336
TF2, bits 2x336
TF3, bits 3x336
TF4, bits 4x336
TTI, ms 20
Coding type TC
CRC, bit 16
Max number of bits/TTI after channel coding 4236

7.3.2.2.5 Reception of not defined PID values
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity,
which applies PDCP Data PDU if no IP header compression protocol, is negotiated.
The UE shall not forward invalid PDCP PDU data contents to its Radio Bearer.
2. If a PDCP entity receives a PDCP PDU with a PID value that is not mapped with a valid packet type (see TS
25.323 subclause 5.1.1), it shall:
- discard the PDCP PDU.
Reference(s)
TS 25.323 clause 5.1.1.
TS 25.323 clause 9.2.
1. To verify, that a UE considers a received PDCP PDU message with not defined PID value as invalid, i.e. such an
invalid PDCP PDU is not forwarded to the Radio Bearer entity on UE side. Therefore the UE using test loop
mode 1 does not return such data packet to the SS.
Release 5 303 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
Test procedure
Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data PDU" and no
PDCP IP header compression protocol has been configured by higher layers.
handle the received data packet with the correct decoding method. Afterwards it forwards the data to its Radio
d) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall
e) The SS sends a TCP/IP data packet with PID=1. See note 1.
handle the received data packet with the correct decoding method.
g) The SS waits an amount of time to make sure, that no returned data packet was sent by UE.
h) The SS deactivates the UE test loop mode and terminates the connection.
NOTE 1 As no PDCP IP header compression protocol has been configured only PID=0 shall be recognised by the
UE and PID=1 shall be considered as invalid PID value by the UE).
Release 5 304 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS



PDCP entity.

PID value =0

data: below described TCP/IP packet.

UE shall recognize, that a not defined PID value
(as configured by higher layers) is inserted in
the PDCP PDU.

The UE shall consider this PDU as invalid, i.e.
the data packet is not forwarded via PDCP-SAP
to its Radio Bearer Loop Back (RB LB) entity.

Therefore this data packet is not returned to the
SS.

4 The SS waits a amount of time to make sure,
that the previously sent data packet is not
returned to the SS.

Release 5 305 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

TRUE

- RAB info
- RAB identity

- RB identity
- PDCP info
- PDCP PDU header
- RLC info
- Downlink RLC mode
- Uplink RLC mode

Prioritised RABs.
QoS parameter:


PS domain

21

present

(UM RLC)
(UM RLC)

PDU type
PID
Data
000
shall be limited to 1500 bytes

PDU type
PID
Data
000
00001 (Invalid PID value, PID =1)
TCP/IP header compression with any data content. The
data shall be limited to 1500 bytes.

The UE shall return the received TCP/IP data packet using the PDCP Data PDU with PID =0.
The UE shall not return the TCP/IP data packet using the PDCP Data PDU with PID =1.
Release 5 306 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.3 PDCP sequence numbering when lossless SRNS Relocation
7.3.3.1 Data transmission if lossless SRNS Relocation is supported
Applicable for all UEs supporting RLC AM, RLC in-sequence delivery, a Radio Bearer as described in the Common
Test Sequences and lossless SRNS relocation.
The UE shall be capable to deal with uncompressed TCP/IP data packets and furthermore to establish a PDCP entity
which applies PDCP Sequence Numbering
1. PDCP sequence numbering shall be applied when lossless SRNS Relocation is supported. PDCP Sequence
Numbers serve to acknowledge previously transmitted PDCP SDUs prior to relocation.
2. In case of a lossless SRNS Relocation procedure:
- the UTRAN should send to the UE the next expected UL_Receive PDCP SN; and
- the UE shall send to the UTRAN the next expected DL_Receive PDCP SN.
This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities.
Reference(s)
TS 25.323 clause 5.4.1.1
TS 25.323 clause 5.4.1.3.
1. To verify, that a UE supporting lossless SRNS relocation is able to receive and to send IP data packets by using
PDCP Sequence Numbering as configured by higher layers.
Initial conditions
SS: 2 cells - Cell A belonging to the valid SRNS (Source SRNS), Cell B belonging to the DRNS (Target SRNS). Both
cells are neighbour cells. Cell A has a higher RF power level than Cell B such that an UE shall find Cell A more
suitable for service.
UE: It is in Idle mode and has selected cell A with valid SRNS (Source SRNS). Usage of "PDCP Data" PDU, PDCP
SeqNum PDU and no IP header compression is configured.
Support of lossless SRNS Relocation - YES/NO
Test procedure
a) The SS setups a packet switched session including Radio Bearer and UE test loop mode 1 in RLC AM and in-
sequence delivery using Common test procedures for mobile terminated PS switched sessions in Cell A. The
RLC buffer discharge mode shall be set to "no discard". Usage of "PDCP Data" PDU, support of lossless SRNS
Release 5 307 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
relocation and no IP header compression has been configured by higher layers. The PDCP SN window size has
been negotiated by RRC.
e) The SS starts to broadcast BCCH messages on the primary CPICH in cell B with a power level higher than in
cell A. The UE shall chose cell B to be more suitable for service and hence perform a cell reselection.
f) After completion of cell reselection, the UE transmits a CELL UPDATE message to the SS on the uplink CCCH
of cell B with the Cell update cause "Cell Reselection".
g) The SS sends a TCP/IP data packet (no compression packet type), PID=0. The PDCP Data PDU is used during
lossless SRNS relocation procedure.
h) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall
The UE shall increase its internal Sequence Number counter by 1.The received data shall be returned by the UE
via its PDCP configuration using PDCP SeqNum PDU.
i) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet
j) After having performed SRNS relocation (target RNC allocated with new S-RNTI for the UE), the Target SRNS
is the valid SRNS and the SS sends a "CELL UPDATE CONFIRM" message with new RNC_ID to indicate the
completion of the cell update.
k) The UE shall confirm the reallocation.
l) The SS sends the next TCP/IP data packet (no compression packet type), PID=0 using the PDCP SeqNum PDU
to the UE.
m) After having received the TCP/IP data packet, the UE shall recognize the PID value and shall handle the
received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The
received data shall be returned by the UE via its PDCP configuration.
n) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall
o) The SS deactivates the UE test loop mode and terminates the connection.
Release 5 308 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS
Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1) in Cell A
header compression. The DL_Send PDCP SN
is set to "0".
Afterwards the SS increments its counter value
DL_Send PDCP SN by "1".


PDCP entity.

PID value =0

3 The SS increases the RF power level of cell B
and decreases the power level of Cell A such
that the UE finds cell B more suitable for
service.

4 The UE cell reselection is performed and Cell B
are selected for service.

5 RRC CELL UPDATE Then, the UE shall inform the SS about the new
cell selection by sending cell update with new
parameters (parameter values as used in RRC
testing).

Release 5 309 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
6 PDCP Data The SS sends a PDCP Data PDU with the


PDCP entity.

PID value =0
8 RRC CELL UPDATE CONFIRM After having performed SRNS relocation, the
Target SRNS is the valid SRNS and the SS
sends a "CELL UPDATE CONFIRM" message
See message content.
9 UTRAN MOBILITY INFORMATION
CONFIRM
The UE confirms the newly received
information.
10 PDCP SeqNum The SS sends the next PDCP SeqNum PDU
using the RLC-AM-Data-Request Primitive with
the following content to the UE:
SeqNum =current PDCP Sequence Number
After having received the PDCP SeqNum PDU,
the UE shall set the received PDCP Sequence
Number as its own valid value. It decodes the
PDU, recognizes PID value =0 applied for this
TCP/IP data packet and shall decompress it
with the appropriate method.

its Radio Bearer Loop Back (RB LB) entity. The
SN synchronisation shall be considered as
successfully performed after acknowledgement
of SeqNum PDU transmission by lower layer in
the SS.
PDCP entity.

11 PDCP SeqNum The UE sends a PDCP SeqNum PDU using the
PID value =0

Release 5 310 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

session using IP Header compression in AM RLC" of this test case are identical to those of the Default Message
Contents for Signalling in TS 34.108 clause 9.1 (UM (Transition to CELL_FACH)) with the following exceptions:

TRUE

using IP Header compression in AM RLC" of this test case are identical to those of the Default Message Contents for
Signalling in TS 34.108 clause 9.1 AM (Packet to CELL_FACH from CELL_FACH in PS) with the following
exceptions:
- RAB info
- RB identity 20
- PDCP info
- Support of lossless SRNS relocation True
- Max PDCP SN window size 65535
- PDCP PDU header Present
- CHOICE RLC info type RLC info
- CHOICE Uplink RLC mode AM RLC
- Transmission RLC Discard
- CHOICE SDU Discard Mode No discard
Note: Default value as defined in TS 34.108, Clause 9.1
- CHOICE Downlink RLC mode AM RLC
- In-sequence delivery True
Note: Default value as defined in TS 34.108, Clause 9.1
Downlink counter synchronisation info
- RB with PDCP information
- RB identity 20
- PDCP SN info 1 (Note: next expected Sequence Number)

PDU type
PID
Data
000

Release 5 311 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Content of PDCP SeqNum PDU (Step 6)
PDU type
PID
Sequence number
Data
001
(16 Bit value) valid Sequence Number of the SS

CELL UPDATE CONFIRM (Step 8)
Use the message sub-type in default message content defined in Annex A, with the following exceptions.
Information Element Value/Remarks
New U-RNTI New value of U-RNTI different from the
previous U-RNTI
Receive PDCP sequence number IE is set to the value to be counted inside SS
as next expected reception Sequence Number

UTRAN MOBILITY INFORMATION CONFIRM (Step 9)
Only the message type is checked.
PDU type
PID
Data
000

After having completed lossless SRNS relocation, the UE shall return the received TCP/IP data packet by using PDCP
SeqNum PDUs as indication, that it supports lossless SRNS relocation. This verifies, that Sequence Numbering is used
for lossless SRNS relocation. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.3.2 Synchronisation of PDCP sequence numbers
Applicable for all UEs supporting RLC AM, RLC in-sequence delivery, a Radio Bearer as described in the Common
Test Sequences.
The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore it shall be capable
to use IP Header compression protocol RFC 2507.
The PDCP SeqNum PDU shall be sent by the peer PDCP entities when synchronisation of the PDCP SN is required.
(...) Synchronisation of PDCP SN is required after (...) RB reconfiguration.
1. In case of a lossless SRNS Relocation procedure:
- the UTRAN should send to the UE the next expected UL_Receive PDCP SN; and
- the UE shall send to the UTRAN the next expected DL_Receive PDCP SN.
Release 5 312 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities.
2. For radio bearers that are configured to support lossless SRNS Relocation, the PDCP entity shall:
- if upper layer indicates to a PDCP entity that it should synchronise the PDCP SN following a RLC reset or
RB reconfiguration; or
- if the UE/UTRAN PDCP entity receives an invalid "next expected UL/DL_Receive PDCP SN" from upper
layer after Relocation:
- trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer;
- consider that the synchronisation procedure is complete on confirmation by lower layer of the successful
transmission of the PDCP SeqNum PDU.
Reference(s)
TS 25.323 clause 5.4.1.3
TS 25.323 clause 5.4.1.2
1. To verify, that the UE supporting lossless SRNS relocation as configured by higher layers is able to handle the
"PDCP SeqNum" PDU to synchronize the used PDCP Sequence Number after reconfiguration of the Radio
Bearer.
Initial conditions
SS: 2 cells - Cell A belonging to the valid SRNS (Source SRNS), Cell B belonging to the DRNS (Target SRNS). Both
cells are neighbour cells. Cell A has a higher RF power level than Cell B such that an UE shall find Cell A more
suitable for service.
UE: It is in Idle mode and has selected cell A with valid SRNS (Source SRNS). Usage of "PDCP Data" PDU, "PDCP
SeqNum" PDU and no IP header compression is configured.
Support of lossless SRNS relocation - YES/NO
Support of RLC in-sequence delivery - YES/NO
Test procedure
a) The SS setups a packet switched session including Radio Bearer and UE test loop mode 1 in RLC AM and in-
sequence delivery using Common test procedures for mobile terminated PS switched sessions in Cell A. The
RLC buffer discharge mode shall be set to "no discard". Usage of "PDCP Data" PDU and "PDCP SeqNum"
PDU, support of lossless SRNS relocation and no IP header compression has been configured by higher layers.
The PDCP SN window size has been negotiated by RRC.
Release 5 313 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
e) The SS reconfigures (using RRC Radio Bearer Reconfiguration message) the PDCP entity by extending the PID
value allocation table and therefore the applied optimisation method with the IP header compression protocol
RFC 2507. The UE test loop mode 1 in RLC AM is still active.
f) The SS sends the next TCP/IP data packet (no compression packet type), PID=0 using the "PDCP SeqNum"
PDU including the current PDCP Sequence Number value to the UE.
g) After having received the TCP/IP data packet, the UE shall recognize the PID value and shall handle the
received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The
received data shall be returned by the UE by using PDCP "SeqNum" PDU including its DL_Receive PDCP SN
via its PDCP configuration.
h) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall
i) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
UE SS
Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1) in Cell A
header compression. The DL_Send PDCP SN
is set to "0".




PDCP entity.

PID value =0

3 RRC RADIO BEARER
RECONFIGURATION
SS extends the "PID value allocation table" with
IP header compression PID (RFC 2507) in the
UE.

4 RRC RADIO BEARER
UE acknowledges its new settings
Release 5 314 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
5 PDCP SeqNum The SS sends a PDCP SeqNum PDU including
its current Sequence Number with the following
content to the UE:
PDU type =001 (PDCP SeqNum PDU)
PID =0 (normal packet type [TCP/IP])
After having received the PDCP SeqNum PDU,
the UE shall set the received PDCP Sequence
Number as its own valid value. It decodes the
PDU, recognizes PID value =0 applied for this
TCP/IP data packet and shall decompress it
with the appropriate method.
The UE shall set the value of DL_Receive
PDCP SN to the value as received from SS.
its Radio Bearer Loop Back (RB LB) entity. The
SN synchronisation shall be considered as
successfully performed after acknowledgement
of SeqNum PDU transmission by lower layer in
the SS.

PDCP entity.

6 PDCP PDU The UE sends a PDCP PDU with PDCP Header
back to the SS. The content is as follows:
PID value =0 to 3
SeqNum: current UE value, (optional parameter,
depending on PDU used)
data: previously received TCP/IP packet.


RRC RADIO BEARER RECONFIGURATION message
The contents of the RRC RADIO BEARER RECONFIGURATION message applied in the preamble "Setup a UE
terminated PS session using IP Header compression in AM RLC" of this test case is identical to those of the default
contents of layer 3 messages for RRC tests [TS 34.123-1] (PS connection for AM) with the following exceptions:
Release 5 315 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- PDCP info
- Max PDCP SN window size
- PDCP PDU header
- RFC2507
- F_MAX_PERIOD
- F_MAX_TIME
- MAX_HEADER
- TCP_SPACE
- NON_TCP_SPACE
- EXPECT_REORDERING
1

65535
TRUE
present
1

256 (Default)
5 (Default)
168 (Default)
15 (Default)
15 (Default)
Receive PDCP sequence number IE is set to the value to be counted inside SS as next
expected reception Sequence Number
U-RNTI New value of U-RNTI different from the previous U-
RNTI

The contents of the RRC CONNECTION SETUP message applied in the preamble "Setup a UE terminated PS session

TRUE

Release 5 316 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
messages for RRC tests [TS 34.123-1] (PS connection for AM) which fit to the here described parameters with the
- Downlink counter syncronisation info
- RB with PDCP information list
- RB identity
- PDCP SN info
- RAB information for setup
- RAB info
- RAB identity

- RB identity
- PDCP info
- Max PDCP SN window size
- PDCP PDU header
- RLC info
- Downlink RLC mode
- In-sequence delivery
- Uplink RLC mode
- Transmission RLC Discard

20
1 (Note: next expected Sequence Number)

Prioritised RABs.
QoS parameter:


PS domain

20

65535
TRUE
present

(AM RLC)
True
(AM RLC)
No Discard Note: Default value defined in TS 34.108,
Annex B

PDU type
PID
Data
000

Content of PDCP SeqNum PDU (Step 5)
PDU type
PID
Sequence number
Data
001
(16 Bit value) valid Sequence Number of the SS

After having received the TCP/IP data packet conveyed with the "PDCP SeqNum" PDU, the UE shall return the TCP/IP
data packets as indication, that the UE is able to handle a Sequence Number synchronisation. An invalid PDU type as
well as unconfigured PID values shall not be received by SS.
Release 5 317 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.3.3 PDCP Sequence Numbering and Data Forwarding - Reception of reserved
PDU type
FFS
7.3.3.4 PDCP Sequence Number synchronization Reception of invalid next
expected receive Sequence Number
FFS
7.3.3.5 UTRAN MOBILITY INFORMATION: Lossless SRNS relocation in
CELL_FACH (without pending of ciphering)

To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the
downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only.
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1>if the variable PDCP_SN_INFO is non-empty:
2>include the IE "RB with PDCP information list" in the UTRAN MOBILITY INFORMATION CONFIRM
message and set it to the value of the variable PDCP_SN_INFO.
1>if the received UTRAN MOBILITY INFORMATION message included the IE "Downlink counter
synchronisation info":
2>re-establish RB2;
2>set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of
COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2>increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2>calculate the START value according to TS 25.331 subclause 8.5.9;
2>include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter
synchronisation info" in the UTRAN MOBILITY INFORMATION CONFIRM message.
1>transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC;
1>if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY
INFORMATION message:
2>when RLC has confirmed the successful transmission of the response message:
3>re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all
the HFN component of the respective COUNT-C values to the START value included in the response
message for the corresponding CN domain;
3>re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN
component of the respective COUNT-C values to the START value included in the response message for
the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3>set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3>re-initialise the PDCP header compression entities of each radio bearer in the variable
ESTABLISHED_RABS.
Release 5 318 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2>when RLC has confirmed the successful transmission of the UTRAN MOBILITY INFORMATION
CONFIRM message:
3>for each radio bearer in the variable PDCP_SN_INFO:
4>if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5>configure the RLC entity for that radio bearer to "continue".
3>clear the variable PDCP_SN_INFO.
Reference
3GPP TS 25.331 clause 8.3.3
1. To confirm that the UE that support lossless SRNS relocation, sends the correct expected downlink PDCP
sequence number to SS after a successful SRNS relocation.
2. To confirm that the UE sends calculated START values for each CN domain to SS after a successful
SRNS relocation.
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statements
- Lossless SRNS relocation supported yes/no
- Support of RLC in-sequence delivery Yes/No
The contents of RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4,
use the message titled Packet to CELL_FACH from CELL_FACH in PS as found in TS 34.108 clause 9, with the
following exception.

Release 5 319 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- PDCP info
- Support for lossless SRNS relocation TRUE
- Max PDCP SN window size sn65535
- PDCP PDU header present
Test Procedure

The UE is in the CELL_FACH state. If PS RAB has been established in the initial condition, SS initiates UE to enter
loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, a PDCP PDUs has to be decided so
that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP
PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS then transmits a UTRAN
MOBILITY INFORMATION message, which includes a valid IE New C-RNTI and New U-RNTI, IE Downlink
counter synchronisation info and IE Integrity protection mode info, to the UE on the downlink DCCH using UM
RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM message. This message also
includes a calculated new START value according to the formula START
X
' =MSB
20
(MAX {COUNT-C, COUNT-I |
radio bearers and signalling radio bearers using the most recently configured CK
X
and IK
X
}) +2, calculated IE
Integrity Check Info using a new FRESH value as included in IE Integrity protection initialisation number in IE
Integrity protection mode info in UTRAN MOBILITY INFORMATION message and COUNT-I that includes
subsequent HFN as used in the old integrity protection configuration, and Receive PDCP sequence number.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to
downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS
responds with UE CAPABILITY INFORMATION CONFIRM message. SS then send IDENTITY REQUEST message
on the DCCH using RLC-AM (SRB3) in order to confirm that the UE can communicate on SRB3 by using new
integrity configuration. The UE shall respond IDENTITY RESPONSE message on the uplink DCCH using RLC-AM
(SRB3). SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the
UE.

Expected sequence
<Ciphering is supported.>

Step Direction Message Comment
UE SS
Activate closed UE test loop mode 1
Release 5 320 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The SS creates a TCP/IP packet
without IP header compression
(PDCP Data PDU).

1 PDCP Data The SS sends a PDCP Data PDU
using the RLC-AM-Data-Request
Primitive with the following content
to the UE:
data: below described TCP/IP
packet

1a After having received the PDCP
Data PDU, the UE decodes the
PDU and recognizes PID value =0
(no IP header compression)
Therefore, no IP header
decompression is applied for this
packet.

The data packet is forwarded via
PDCP-SAP to its Radio Bearer

1b The RB LB entity in UE test loop
mode 1 returns the received data
packet and sends it back to its
PDCP entity.

2 PDCP Data The UE sends a PDCP Data PDU
back to the SS:
data: previously received TCP/IP
packet

2a After reception of this TCP/IP data
packet, the SS applies the
appropriate decoding function for
the received data

2b The SS creates a UDP/IP packet
(PDCP Data PDU).

2c SS shall suspend the sending of
PDCP PDUs and wait for the last
PDCP PDU to be sent back by the
UE and then note the next PDCP
SN for the next PDCP PDU.
3 UTRAN MOBILITY INFORMATION This message is sent after last
ciphering activation time has
elapsed and there is no pending
ciphering activation time. New U-
RNTI identities are assigned to the
UE. IE Downlink counter
synchronisation info includes the
next PCDP sequence number that
SS is expected to receive from the
UE, otherwise only IE Downlink
counter synchronisation info is
included. New integrity protection
configuration is applied on DL
SRB1.
4 UTRAN MOBILITY INFORMATION New calculated START value is
Release 5 321 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CONFIRM included, IE Receive PDCP
sequence number shall be
configuration is applied on UL
SRB2. New ciphering configuration
is applied on UL SRB2 with the
downlink and uplink values of the
HFN component of COUNT-C for
SRB2 is incremented by one.
5 UE CAPABILITY ENQUIRY New integrity protection
is applied on DL SRB2 with the
same value as used in step 4.
6 UE CAPABILITY INFORMATION SS confirms that new integrity
protection configuration is applied
on SRB2 by UE.
7 UE CAPABILITY INFORMATION
CONFIRM

8 DOWNLINK DIRECT TRANSFER NAS message embedded in this
this is IDENTITY REQUEST. New
integrity protection configuration is
applied on DL SRB3. New
ciphering configuration is applied
on DL SRB3 using the re-initialised
COUNT-C HFN by the start value
as stored in step 4.
9 UPLINK DIRECT TRANSFER NAS message embedded in this is
IDENTITY RESPONSE. SS
confirms that new integrity
on UL SRB2 by UE. New ciphering
SRB3 using the re-initialised
(PDCP Data PDU).

to the UE:
packet

11 After having received the PDCP
packet.


12 The RB LB entity in UE test loop
PDCP entity.

Release 5 322 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
back to the SS:
packet

14 After reception of this TCP/IP data
the received data

15 The SS creates a UDP/IP packet
(PDCP Data PDU).


<Ciphering is not supported. >
Release 5 323 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

2c Void SS shall suspend the sending of
SN for the next PDCP PDU.
3 UTRAN MOBILITY INFORMATION New U-RNTI identities are assigned
to the UE. IE Downlink counter
SRB1.
4 UTRAN MOBILITY INFORMATION New calculated START value is
Release 5 324 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CONFIRM included. IE Receive PDCP
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

8 IDENTITY REQUEST New integrity protection
SRB3.
9 IDENTITY RESPONSE SS confirms that new integrity
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).


Release 5 325 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

UTRAN MOBILITY INFORMATION for PS only UE (Step 3)
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
Ciphering mode info Not present
Integrity protection mode info
- Integrity protection mode command Start
- Downlink integrity protection activation info Not Present
- Integrity protection algorithm UIA1
- Integrity protection initialisation number SS selects an arbitrary 32 bits number for FRESH
New U-RNTI
- SRNC Identity An arbitrary 12-bits string which is different from original
SRNC
- S-RNTI An arbitrary 20-bits string which is different from original
S-RNTI
New C-RNTI Not Present
CN Information info
- PLMN identity Not present
- CN common GSM-MAP NAS system information
- GSM-MAP NAS system information 00 01H
- CN domain related information
- CN domain identity PS
- CN domain specific NAS system information
- CN domain specific DRX cycle length coefficient 7
- CN domain identity CS
- GSM-MAP NAS system information 1E 01H
- RB with PDCP information list This IE is included
- RB identity 20
- PDCP SN info The next PCDP sequence number that SS is expected
to receive from the UE

UTRAN MOBILITY INFORMATION for CS only UE (Step 3)

Release 5 326 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
SRNC
S-RNTI
CN Information info
- RB with PDCP information list Not Present

UTRAN MOBILITY INFORMATION CONFIRM for PS only UE (Step 4)
The same message sub-type found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH with the
Uplink counter synchronisation info
- RB with PDCP information list This IE is checked
- RB identity 20
- PDCP SN info Check that the PCDP sequence number is the next
sequence number that SS would transmit to the UE. (X)
- START list Check that this IE is correct value
UTRAN MOBILITY INFORMATION CONFIRM for CS only UE (Step 4)
- RB with PDCP information list Check that this IE is not present.
- START list Check that this IE is correct value.

Content of PDCP Data PDUs used for entire test case
PDU type
PID
Data
000

Release 5 327 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)

7.3.3.5.5 Test requirement
After step 1, UE shall transmit back all the PDCP PDUs sent by the SS to the UE.
After step 3, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH
using AM RLC which includes which includes a calculated new START value according to the formula START
X
' =
MSB
20
(MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured
CK
X
and IK
X
}) +2, calculated IE Integrity Check Info using the new FRESH value as included in IE Integrity
protection initialisation number in IE Integrity protection mode info in UTRAN MOBILITY INFORMATION
message and COUNT-I that includes subsequent HFN as used in the old integrity protection configurationThis message
shall also include IE Receive PDCP sequence number for RB#20. .
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS and apply new ciphering
configuration on UL SRB3.
After step 8, the UE shall respond with a IDENTITY RESPONSE message to SS
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the UTRAN
MOBILITY INFORMATION CONFIRM message.

7.3.3.6 Cell Update: Lossless SRNS relocation in CELL_FACH (without pending of
ciphering)

When the UTRAN receives a CELL UPDATE message, the UTRAN should:
1>in case the procedure was triggered by reception of a CELL UPDATE:
2>if SRNS relocation was performed:
3>transmit a CELL UPDATE CONFIRM message on the downlink DCCH.
2>otherwise:
3>update the START value for each CN domain as maintained in UTRAN (refer to TS 25.331 subclause
8.5.9) with "START" in the IE "START list" for the CN domain as indicated by "CN domain identity" in
the IE "START list";
3>if this procedure was triggered while the UE was not in CELL_DCH state, then for each CN domain as
indicated by "CN domain identity" in the IE "START list":
4>set the 20 MSB of the MAC-d HFN with the corresponding START value in the IE "START list";
Release 5 328 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
4>set the remaining LSB of the MAC-d HFN to zero.
3>transmit a CELL UPDATE CONFIRM message on the downlink DCCH or optionally on the CCCH but
only if ciphering is not required; and
3>optionally include the IE "RLC re-establish indicator (RB5 and upwards)" to request a RLC re-
establishment in the UE, in which case the corresponding RLC entities should also be re-established in
UTRAN; or
If the UE after the state transition remains in CELL_FACH state; and
- a C-RNTI is stored in the variable C_RNTI;
the UE shall:
2>include the IE "RB with PDCP information list" in any response message transmitted below and set it to the
value of the variable PDCP_SN_INFO.
1>if the received CELL UPDATE CONFIRM message included the IE "Downlink counter synchronisation info":
2>re-establish RB2;
2>set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component
of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2);
2>increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2;
synchronisation info" in any response message transmitted below.
1>transmit a response message as specified in TS 25.331 subclause 8.3.1.7;
If the CELL UPDATE CONFIRM message:
- does not include "RB information elements"; and
- does not include "Transport channel information elements"; and
- does not include "Physical channel information elements"; and
- includes "CN information elements"; or
- includes the IE "Ciphering mode info"; or
- includes the IE "Integrity protection mode info"; or
- includes the IE "New C-RNTI"; or
- includes the IE "New U-RNTI":
the UE shall:
1>transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration
after the state transition., and the UE shall:
1>if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM
message:
Release 5 329 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
ESTABLISHED_RABS as specified in [36].
1>if the variable PDCP_SN_INFO non-empty:
3>continue with the remainder of the procedure.

Reference
1. To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA
cell.
3. To confirm that the UE sends calculated START values for each CN domain to SS after a successful
SRNS relocation.
Initial Condition
System Simulator: 2 cells - Cell 1 and 2 are active.
Specific Message Content
For RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4, uses the
message titled Packet to CELL_FACH from CELL_FACH in PS as found in TS 34.108 clause 9, with the following
exception.

Release 5 330 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- PDCP info
Test Procedure
Table 7.3.3.6
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60

Table 7.3.3.6 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution.
Columns marked "T0" denote the initial conditions.

The UE is in the CELL_FACH state in cell 1. If PS RAB has been established in the initial condition, SS initiates UE to
enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, the number of a PDCP PDU has
to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for
the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures
its downlink transmission power settings according to columns "T1" in table 7.3.3.6. The UE shall find cell 2 to be
more suitable for service and hence perform a cell reselection. After the completion of cell reselection, the UE shall
transmits a CELL UPDATE message to the SS on the uplink CCCH of cell 2 and set IE "Cell update cause" to "Cell
Reselection". SS then transmits a CELL UPDATE CONFIRM message, which includes a valid IE New C-RNTI and
New U-RNTI, IE Downlink counter synchronisation info and IE Integrity protection mode info, to the UE on the
downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM
message. This message also includes a calculated new START value according to the formula START
X
' =MSB
20

(MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CK
X
and
IK
X
}) +2, calculated IE Integrity Check Info using a new FRESH value as included in IE Integrity protection
initialisation number in IE Integrity protection mode info in CELL UPDATE CONFIRM message and COUNT-I
that includes subsequent HFN as used in the old integrity protection configuration, and Receive PDCP sequence
number.
UE.

Expected sequence

Release 5 331 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

SN for the next PDCP PDU. After
last ciphering activation time has
ciphering activation time, SS
applies the downlink transmission
power settings, according to the
values in columns "T1" of table
7.3.3.6. The UE shall find that the
cell 2 is better for service and
perform a reselection. SS waits for
the maximum duration required for
the UE to camp to cell 2.
3 CELL UPDATE Value "cell reselection" shall be
indicated in IE "Cell update cause"
Release 5 332 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
4 CELL UPDATE CONFIRM IE "RRC State Indicator" is set to
"CELL_FACH". New C-RNTI and
U-RNTI identities are assigned to
the UE. IE Downlink counter
SRB1. LAI and RAI of cell 2 are
given to the UE, and are the same
as cell 1.
CONFIRM
New calculated START value is
included. IE Receive PDCP
on UL SRB2 by UE.
CONFIRM

(PDCP Data PDU).

to the UE:
packet

Release 5 333 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

17 New ciphering configuration is
applied on UL and DL RAB using
the re-initialised COUNT-C HFN by
the start value as stored in step 5.


Release 5 334 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

SN for the next PDCP PDU. SS
3 CELL UPDATE Value "cell reselection" shall be
indicated in IE "Cell update cause"
Release 5 335 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
as cell 1.
CONFIRM
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

SRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

Release 5 336 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
back to the SS:
packet

the received data

(PDCP Data PDU).



CELL UPDATE (Step 3)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception
of the following IEs:
Cell Update Cause Check to see if set to 'Cell Re-selection'
CELL UPDATE CONFIRM for PS only UE (Step 4)
Release 5 337 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
SRNC
S-RNTI
CN Information info
- RB identity 20
to receive from the UE.(X)

CELL UPDATE CONFIRM for CS only UE (Step 4)

New U-RNTI
SRNC
S-RNTI
CN Information info

Release 5 338 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RB identity 20
sequence number that SS would transmit to the UE

PDU type
PID
Data
000


After step 2, UE shall transmit CELL UPDATE message with the value of IE Cell update cause set to cell
reselection.
X
' =
MSB
20
CK
X
and IK
X
message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, this message
shall also include IE Receive PDCP sequence number for RB#20.
Release 5 339 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
After step 6, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, the UE shall respond with an IDENTITY RESPONSE message to SS and apply new ciphering
After step 10, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the
UTRAN MOBILITY INFORMATION CONFIRM message.

7.3.3.7 URA Update: Lossless SRNS relocation in CELL_FACH (without pending of
ciphering)

When the UTRAN receives a URA UPDATE message, the UTRAN should:
1>in case the procedure was triggered by reception of a URA UPDATE:
2>if SRNS relocation was performed:
3>transmit a URA UPDATE CONFIRM message on the downlink DCCH.
the UE shall:
2>include the IE "RB with PDCP information list" in any response message transmitted below and set it to the
value of the variable PDCP_SN_INFO.
1>if the received URA UPDATE CONFIRM message included the IE "Downlink counter synchronisation info":
2>re-establish RB2;
2>set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component
of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2);
2>increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2;
synchronisation info" in any response message transmitted below.
If the URA UPDATE CONFIRM message:
- includes any one or both of the IEs "New C-RNTI" and "New U-RNTI":
the UE shall:
Release 5 340 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
after the state transition., and the UE shall:
1>if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or
URA UPDATE CONFIRM message:
ESTABLISHED_RABS.
1>if the variable PDCP_SN_INFO non-empty:
Reference
1. To confirm that the UE executes a URA update procedure after the successful reselection of another UTRA
cell.
3. To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS
relocation.
Initial Condition
UE: URA_PCH (state 6-13) in cell 1 as specified in clause 7.4 of TS 34.108.
For RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4, uses the
message titled Packet to CELL_FACH from CELL_FACH in PS as found in TS 34.108 clause 9, with the following
exception.

Release 5 341 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- PDCP info

Test Procedure
Table 7.3.3.7
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60


The UE is in the URA_PCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS
initiates UE to enter loopback mode 1 and sends a PDCP PDUs on the RAB. If ciphering is supported, a PDCP PDUs
has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait
for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS
configures its downlink transmission power settings according to columns "T1" in table 7.3.3.7. The UE shall find cell 3
to be more suitable for service and hence perform a cell reselection. After the completion of cell reselection, the UE
shall transmits a URA UPDATE message to the SS on the uplink CCCH of cell 3 and set IE "URA update cause" to
"change of URA". After the SS receives this message, it transmits a URA UPDATE CONFIRM message, which
includes a valid IE New C-RNTI and New U-RNTI, IE Downlink counter synchronisation info and IE Integrity
protection mode info, to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN
MOBILITY INFORMATION CONFIRM message. This message also includes a calculated new START value
according to the formula START
X
' =MSB
20
(MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers
using the most recently configured CK
X
and IK
X
}) +2, calculated IE Integrity Check Info using a new FRESH value
as included in IE Integrity protection initialisation number in IE Integrity protection mode info in CELL UPDATE
CONFIRM message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration,
and Receive PDCP sequence number.
UE.

Expected sequence
Release 5 342 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

Release 5 343 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

SN for the next PDCP PDU. After
last ciphering activation time has
ciphering activation time, SS
3 URA UPDATE Value "change of URA" shall be
indicated in IE "URA update cause"
Release 5 344 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
4 URA UPDATE CONFIRM IE "RRC State Indicator" is set to
as cell 1.
CONFIRM
on UL SRB2 by UE.
CONFIRM

(PDCP Data PDU).

to the UE:
packet

Release 5 345 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).



Release 5 346 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

3 URA UPDATE Value "change of URA" shall be
indicated in IE "URA update cause"
Release 5 347 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
4 URA UPDATE CONFIRM IE "RRC State Indicator" is set to
as cell 1.
CONFIRM
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

SRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

Release 5 348 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
back to the SS:
packet

the received data

(PDCP Data PDU).



URA UPDATE (Step 3)
URA Update Cause Check to see if set to change of URA
URA UPDATE CONFIRM for PS only UE (Step 4)
Release 5 349 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
SRNC
S-RNTI
CN Information info
- RB identity 20
to receive from the UE.(X)

URA UPDATE CONFIRM for CS only UE (Step 4)

New U-RNTI
SRNC
S-RNTI
CN Information info

Release 5 350 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RB identity 20
sequence number that SS would transmit to the UE.(X)

PDU type
PID
Data
000

After step 2, UE shall transmit URA UPDATE message with the value of IE URA update cause set to change of
URA.
X
' =
MSB
20
CK
X
and IK
X
message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This
message shall also include IE Receive PDCP sequence number for RB#20.
Release 5 351 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UTRAN MOBILITY INFORMATION CONFIRM message.

7.3.3.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH:
Success (Lossless SRNS relocation) (without pending of ciphering)
1>if the reconfiguration procedure is simultaneous with SRNS relocation procedure:
2>if the transmitted message is a RADIO BEARER RECONFIGURATION:
3>include the IE "New U-RNTI".
2>else:
3>include the IE "Downlink counter synchronisation info".
The UE shall:
1>if the received reconfiguration message included the IE "Downlink counter synchronisation info";
2>re-establish RB2;
2>calculate the START value according to subclause 8.5.9;
synchronisation info".
1>if the variable PDCP_SN_INFO is not empty:
2>include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.
1>if the IE "Integrity protection mode info" was present in the received reconfiguration message:
2>start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from
and including the transmitted response message.
after the state transition, and the UE shall:
1>if the IE "Downlink counter synchronisation info" was included in the reconfiguration message;
3>set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
Release 5 352 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3>perform the actions below.
Reference
3GPP TS 25.331 clause 8.2.2.
To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a RADIO
BEARER SETUP COMPLETE message in the new cell.
Initial Condition
System Simulator: 2 cells Cell 1 and 2
UE: PS-DCCH+DTCH_DCH (state 6-10) or CS-DCCH+DTCH_DCH (state 6-9) or PS+CS-DCCH+DTCH_DCH
(state 6-14) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.

For RADIO BEARER SETUP message to be transmitted during P13 as specified in TS 34.108 clause 7.4, use the
message titled Packet to CELL_DCH from CELL_DCH in PS as found in TS 34.108 clause 9, with the following
exception.

Release 5 353 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RAB info
- RAB identity 0000 0101B
- CN domain identity PS domain
- NAS Synchronization Indicator Not Present
- Re-establishment timer UseT315
- RB identity 20
- PDCP info
- Transmission RLC discard
- SDU discard mode No discard
- MAX_DAT 15
- Transmission window size 128
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll_prohibit 200
- Timer_poll 200
- Poll_PDU Not Present
- Poll_SDU 1
- Last transmission PDU poll TRUE
- Last retransmission PDU poll TRUE
- Poll_Windows 99
- Timer_poll_periodic Not Present
- In-sequence delivery TRUE
- Receiving window size 128
- Downlink RLC status info
- Timer_status_prohibit 200
- Timer_EPC Not Present
- Missing PDU indicator TRUE
- Timer_STATUS_periodic Not Present
- RB mapping info
- Information for each multiplexing option 2 RBMuxOptions
- RLC logical channel mapping indicator Not Present
- Number of uplink RLC logical channels 1
- Uplink transport channel type DCH
- UL Transport channel identity 1
- Logical channel identity 7
- CHOICE RLC size list Configured
- MAC logical channel priority 8
- Downlink RLC logical channel info
- Number of downlink RLC logical
channels
1
- Downlink transport channel type DCH
- DL DCH Transport channel identity 6
- DL DSCH Transport channel identity Not Present
- Uplink transport channel type RACH
- UL Transport channel identity Not Present
- CHOICE RLC size list Explicit List
- RLC size index Reference to TS34.108 clause 6 Parameter Set
- Number of downlink RLC logical
channels
1
- Downlink transport channel type FACH
- DL DCH Transport channel identity Not Present
Release 5 354 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Test Procedure
Table 7.3.3.8
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60


The UE is in the CELL_DCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS
initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, the a PDCP PDUs
configures its downlink transmission power settings according to columns "T1" in table 7.3.3.8. The SS sends a RADIO
BEARER SETUP message on the downlink DCCH using AM RLC requesting the UE to do a handover combined with
SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE Downlink counter
synchronisation info and IE Integrity protection mode info. UE shall reselect to cell 2 and SS verifies that the UE
sends RADIO BEARER SETUP COMPLETE message. This message also includes a calculated new START value
X
' =MSB
20
X
and IK
X
as included in IE Integrity protection initialisation number in IE Integrity protection mode info in RADIO
BEARER SETUP message and COUNT-I that includes subsequent HFN as used in the old integrity protection
configuration, and Receive PDCP sequence number.
UE.

Expected sequence

Release 5 355 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.8.
Release 5 356 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3 RADIO BEARER SETUP This message is sent after last
ciphering activation time. IE
Downlink counter synchronisation
info includes the next PCDP
sequence number that SS is
expected to receive from the UE,
otherwise only IE Downlink counter
synchronisation info is included.
New integrity protection
as cell 1.
4 RADIO BEARER SETUP COMPLETE The UE shall transmit this message
after it reselects to cell 2. New
calculated START value is
on UL SRB2 by UE.
CONFIRM

8 DOWNLINK DIRECT TRANSFER NAS message embedded in this is
IDENTITY REQUEST. New
(PDCP Data PDU).

to the UE:
packet

Release 5 357 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).



Release 5 358 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.8.
Release 5 359 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3 RADIO BEARER SETUP IE Downlink counter
as cell 1.
4 RADIO BEARER SETUP COMPLETE The UE shall transmit this message
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DL SRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

Release 5 360 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
back to the SS:
packet

the received data

(PDCP Data PDU).



RADIO BEARER SETUP for PS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled Packet to CELL_DCH from
CELL_DCH in PS, with the following exception:

Release 5 361 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- SRNC identity 0000 0000 0010B
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RAB info
- RB identity 12
- PDCP info
- Support for lossless SRNS relocation FALSE
- Max PDCP SN window size Not present
- PDCP PDU header Absent
- Header compression information Not present
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Windows 99
- RB mapping info
Release 5 362 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- Number of downlink RLC logical channels 1
- RB identity 20
- PDCP SN info The next PCDP sequence number that SS is
expected to receive from the UE.
Downlink information for each radio links
- Primary CPICH info
- Primary Scrambling Code Set to same code as used for cell 2

RADIO BEARER SETUP for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled Non speech to CELL_DCH from
CELL_DCH in CS, with the following exception:

Release 5 363 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RAB info
- CN domain identity CS domain
- RB identity 13
- PDCP info Not Present
- CHOICE Uplink RLC mode TM RLC
- Transmission RLC discard Not Present
- Segmentation indication FALSE
- CHOICE Downlink RLC mode TM RLC
- Segmentation indication FALSE
- RB mapping info
- Information for each multiplexing option
- Logical channel identity Not Present
- RB with PDCP information list Not present
RADIO BEARER SETUP COMPLETE for PS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.

Release 5 364 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RB with PDCP information list This IE is checked.
- RB identity 12
sequence number that SS would transmit to the UE.
- RB identity 20
- START list Check that this IE is present.

RADIO BEARER SETUP COMPLETE for CS only UE (Step 4)


PDU type
PID
Data
000

After step 3, the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the uplink DCCH using AM
RLC which includes which includes a calculated new START value according to the formula START
X
' =MSB
20

X
and
IK
X
}) +2, calculated IE Integrity Check Info using the new FRESH value as included in IE Integrity protection
initialisation number in IE Integrity protection mode info in RADIO BEARER SETUP message and COUNT-I that
includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE
Receive PDCP sequence number for RB#20.
Release 5 365 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the RADIO
BEARER RECONFIGURATION COMPLETE message.

7.3.3.9 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH:
2>else:
The UE shall:
1>if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New U-
RNTI" is included:
2>re-establish RB2;
1>if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New U-
RNTI" is included:
Release 5 366 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference
3GPP TS 25.331 clause 8.2.2.
BEARER RECONFIGURATION COMPLETE message in the new cell.
Initial Condition

exception.

Release 5 367 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- PDCP info
Test Procedure
Table 7.3.3.9
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60


initiates UE to enter loopback mode 1. If ciphering is supported a PDCP PDU has to be decided so that the ciphering
activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send
back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission
power settings according to columns "T1" in table 7.3.3.9. The SS sends a RADIO BEARER RECONFIGURATION
message on the downlink DCCH using AM RLC requesting the UE to do a handover combined with SRNS relocation.
This message includes IE "RRC State Indicator" set to "CELL_DCH", IE New U-RNTI and IE Integrity protection
mode info. UE shall reselect to cell 2 and SS verifies that the UE sends RADIO BEARER RECONFIGURATION
COMPLETE message. This message also includes a calculated new START value according to the formula START
X
'
=MSB
20
CK
X
and IK
X
}) +2, calculated IE Integrity Check Info using a new FRESH value as included in IE Integrity
protection initialisation number in IE Integrity protection mode info in RADIO BEARER SETUP message and
COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and Receive PDCP
sequence number.
UE.

Expected sequence

Release 5 368 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.8.
Release 5 369 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3 RADIO BEARER RECONFIGURATION This message is sent after last
ciphering activation time. IE RB
information to reconfigure includes
the next PCDP sequence number
that SS is expected to receive from
the UE. New integrity protection
as cell 1.
COMPLETE
The UE shall transmit this message
on UL SRB2 by UE.
CONFIRM

(PDCP Data PDU).

to the UE:
packet

Release 5 370 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).



Release 5 371 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.9.
3 RADIO BEARER RECONFIGURATION IE RB information to reconfigure
includes the next PCDP sequence
number that SS is expected to
receive from the UE. New integrity
on DL SRB1. LAI and RAI of cell 2
are given to the UE, and are the
same as cell 1.
Release 5 372 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
COMPLETE
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DL SRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

Release 5 373 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
(PDCP Data PDU).



RADIO BEARER RECONFIGURATION for PS only UE (Step 3)

Release 5 374 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RB information to reconfigure (AM DCCH for RRC)
- RB identity 2
- PDCP SN info Not Present
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_PDU Not present
- Poll_SDU 1
- Poll_Window 99
- Timer_EPC Not present
- RB mapping info Not Present
- RB stop/continue Not Present
- RB information to reconfigure (AM DCCH for NAS_DT High priority)
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
Release 5 375 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- Poll_SDU 1
- Poll_Window 99
- RB information to reconfigure (AM DCCH for NAS_DT Low priority)
- RB identity 4
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB information to reconfigure (AM DTCH)
- RB identity 20
- PDCP info
- PDCP PDU header Present
expected to receive from the UE
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
Release 5 376 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- Poll_SDU 1
- Poll_Window 99

RADIO BEARER RECONFIGURATION for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled Speech in CS or Non speech in
CS, with the following exception:

Release 5 377 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
Release 5 378 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99

RADIO BEARER RECONFIGURATION COMPLETE for PS only UE (Step 4)

Release 5 379 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
- RB identity 20
RADIO BEARER RECONFIGURATION COMPLETE for CS only UE (Step 4)


PDU type
PID
Data
000


After step 3, the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC which includes which includes a calculated new START value according to the formula
START
X
' =MSB
20
(MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently
configured CK
X
and IK
X
}) +2, calculated IE Integrity Check Info using the new FRESH value as included in IE
Integrity protection initialisation number in IE Integrity protection mode info in RADIO BEARER
RECONFIGURATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection
configuration. This message shall also include IE Receive PDCP sequence number for RB#20.
configuration on UL SRB3.After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to
that included in the RADIO BEARER RECONFIGURATION COMPLETE message.

Release 5 380 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.3.3.10 Radio Bearer Release for transition from CELL_DCH to CELL_DCH:
2>else:
The UE shall:
1>if the received reconfiguration message included the IE "Downlink counter synchronisation info";
2>re-establish RB2;
1>if the IE "Downlink counter synchronisation info" was included in the reconfiguration message;
Release 5 381 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Reference
3GPP TS 25.331 clause 8.2.2.
BEARER RELEASE COMPLETE message in the new cell.
Initial Condition
UE: PS+CS-DCCH+DTCH_DCH (state 6-14) or CS+CS-DCCH+DTCH_DCH (state 6-15) or PS+PS-
DCCH+DTCH_DCH (state 6-16) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by
the UE.

exception.

- PDCP info

Test Procedure
Table 7.3.3.10
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60

Release 5 382 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
initiates UE to enter loopback mode 1 and sends a PDCP PDUs on the RAB. If ciphering is supported, a PDCP PDU
configures its downlink transmission power settings according to columns "T1" in table 7.3.3.10. The SS sends a
RADIO BEARER RELEASE message on the downlink DCCH using AM RLC requesting the UE to do a handover
combined with SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE Downlink
counter synchronisation info and IE Integrity protection mode info. UE shall reselect to cell 2 and SS verifies that
the UE sends RADIO BEARER RELEASE COMPLETE message. This message also includes a calculated new
START value according to the formula START
X
' =MSB
20
(MAX {COUNT-C, COUNT-I | radio bearers and
signalling radio bearers using the most recently configured CK
X
and IK
X
}) +2, calculated IE Integrity Check Info
using a new FRESH value as included in IE Integrity protection initialisation number in IE Integrity protection mode
info in RADIO BEARER RELEASE message and COUNT-I that includes subsequent HFN as used in the old integrity
protection configuration, and Receive PDCP sequence number.
UE.

Expected sequence

Release 5 383 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.10
Release 5 384 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3 RADIO BEARER RELEASE This message is sent after last
as cell 1.
4 RADIO BEARER RELEASE
COMPLETE
on UL SRB2 by UE.
CONFIRM

(PDCP Data PDU).

to the UE:
packet

Release 5 385 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).



Release 5 386 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.10
3 RADIO BEARER RELEASE IE RB information to reconfigure
same as cell 1.
Release 5 387 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
COMPLETE
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DL SRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

Release 5 388 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
(PDCP Data PDU).



RADIO BEARER RELEASE for PS only UE (Step 3)

New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
RB information to release
- RB identity 18
- RB identity 20
RADIO BEARER RELEASE for CS only UE (Step 3)

Release 5 389 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RB identity 13

RADIO BEARER RELEASE COMPLETE for PS only UE (Step 4)

- RB identity 20

RADIO BEARER RELEASE COMPLETE for CS only UE (Step 4)


Release 5 390 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
PDU type
PID
Data
000

After step 3, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using
AM RLC which includes which includes a calculated new START value according to the formula START
X
' =MSB
20

X
and
IK
X
}) +2, calculated IE Integrity Check Info using the new FRESH value as included in IE Integrity protection
initialisation number in IE Integrity protection mode info in RADIO BEARER RELEASE message and COUNT-I
that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE
Receive PDCP sequence number for RB#20.
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the RADIO
BEARER RELEASE COMPLETE message.

7.3.3.11 Transport Channel Reconfiguration for transition from CELL_DCH to
CELL_DCH: Success (Lossless SRNS relocation) (without pending of
ciphering)
2>else:
Release 5 391 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The UE shall:
1>if the received reconfiguration message included the IE "Downlink counter synchronisation info"; or
2>re-establish RB2;
1>if the IE "Downlink counter synchronisation info" was included in the reconfiguration message; or
Reference
3GPP TS 25.331 clause 8.2.2.
To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message in the new cell.
Release 5 392 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial Condition

exception.

- PDCP info

Test Procedure
Table 7.3.3.11
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60


Release 5 393 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, a PDCP PDU has
to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for
the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures
its downlink transmission power settings according to columns "T1" in table 7.3.3.11. The SS sends a TRANSPORT
CHANNEL RECONFIGURATION message requesting the UE to do a handover combined with SRNS relocation. This
message includes IE "RRC State Indicator" set to "CELL_DCH", IE Downlink counter synchronisation info and IE
Integrity protection mode info. UE shall reselect to cell 2 and SS verifies that the UE sends TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message. This message also includes a calculated new START value
X
' =MSB
20
X
and IK
X
as included in IE Integrity protection initialisation number in IE Integrity protection mode info in TRANSPORT
CHANNEL RECONFIGURATION message and COUNT-I that includes subsequent HFN as used in the old integrity
protection configuration, and Receive PDCP sequence number.
UE.

Expected sequence

Release 5 394 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

values in columns "T1" of 7.3.3.11.
Release 5 395 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
3 TRANSPORT CHANNEL
RECONFIGURATION
This message is sent after last
as cell 1.
4 TRANSPORT CHANNEL
on UL SRB2 by UE.
CONFIRM

(PDCP Data PDU).

to the UE:
packet

Release 5 396 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).



Release 5 397 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
UE SS
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

(PDCP Data PDU).

7.3.3.11.
3 TRANSPORT CHANNEL
RECONFIGURATION
IE RB information to reconfigure
same as cell 1.
Release 5 398 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
4 TRANSPORT CHANNEL
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DLSRB3.
on UL SRB2 by UE.
(PDCP Data PDU).

to the UE:
packet

packet.


PDCP entity.

back to the SS:
packet

the received data

Release 5 399 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
(PDCP Data PDU).



TRANSPORT CHANNEL RECONFIGURATION for PS only UE (Step 3)

Ciphering mode info Not present.
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RB with PDCP information list This IE is included.
- RB identity 20

TRANSPORT CHANNEL RECONFIGURATION for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled Speech in CS or Non speech in
CS, with the following exception:

Release 5 400 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info

TRANSPORT CHANNEL RECONFIGURATION COMPLETE for PS only UE (Step 4)

- RB identity 20

TRANSPORT CHANNEL RECONFIGURATION COMPLETE for CS only UE (Step 4)


PDU type
PID
Data
000

Release 5 401 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

After step 3, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC which includes which includes a calculated new START value according to the formula
START
X
' =MSB
20
configured CK
X
and IK
X
Integrity protection initialisation number in IE Integrity protection mode info in TRANSPORT CHANNEL
configuration. This message shall also include IE Receive PDCP sequence number for RB#20.
TRANSPORT CHANNEL RECONFIGURATION COMPLETE message.
7.3.4 PDCP configuration testing
7.3.4.1 PDCP configuration behaviour while RRC Radio bearer setup procedure
FFS
7.3.4.2 PDCP configuration behaviour while RRC Radio bearer release procedure
FFS
7.3.4.3 PDCP configuration behaviour while RRC Cell Update procedure
FFS
7.3.4.4 PDCP configuration behaviour for an invalid RRC configuration
FFS
7.4 BMC
General
For BMC testing, the UE manufacturers shall define CB data as PIXIT (CB-Data 1 and 2) for different CB message
types and for CB Data41 (ANSI-41 data) and it shall describe how the reception is indicated in a clear way on UE side.
Release 5 402 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Only Cell Broadcast Services (CBS) as distributed BMC service is applied. For a UE supporting BMC, it is assumed,
that there is a BMC entity established, if Initial conditions are reached.
If not otherwise mentioned, the same procedures as used in RRC test specification [TS 34.123-1] are applied to reach
Initial conditions for BMC testing.
It shall be possible to activate and deactivate a CB message types by using the Message ID of CB data 1, 2 and CB41
data 1 on UE side.
7.4.1 BMC RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH
7.4.1.1 Transport channel parameters of BMC RAB and SRBs for CCCH, SRB for
DCCH, and SRB for BCCH
Higher
layer
RAB/signalling RB SRB#1 SRB#2 SRB#3 SRB#4 SRB#5 SRB#6 RAB#30
User of Radio Bearer RRC RRC RRC
NAS_DT
High prio
NAS_DT
Low prio
RRC -
RLC Logical channel type CCCH DCCH DCCH DCCH DCCH BCCH CTCH
RLC mode UM UM AM AM AM TM UM
Payload sizes, bit 152 136 or
120*
128 128 128 166 152
or
36000
38400 38400 38400 49800 45600
AMD/UMD/TrD PDU
header, bit
8 8 16 16 16 0 8
MAC
MAC header, bit 8 24 or
40
24 24 24 2 8
TB sizes, bit 168
TFS
TF0, bits 0x168
TF1, bits 1x168
TF2, bits 2x168
TF3, bits 3x168
TTI, ms 10
Coding type CC 1/2
CRC, bit 16
1136
* MAC header size and RLC payload size depend on use of U-RNTI or C-RNTI.
7.4.1.2 TFCS
TFCS size 4
TFCS (BMC RAB and SRBs for CCCH/DCCH/BCCH) =TF0, TF1, TF2, TF3

7.4.1.3 Physical channel parameters
SCCPCH DTX position Flexible
Spreading factor 64
Number of TFCI bits/slot 8
Number of Pilot bits/slot 0
Number of data bits/slot 72
Number of data bits/frame 1080

Release 5 403 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
7.4.2 General BMC message reception
7.4.2.1 UE in RRC Idle mode
Applicable only for a UE supporting Cell Broadcast Services (CBS) as a type of Broadcast/Multicast Services.
It shall be possible to indicate the reception of certain CBS message contents carried with certain activated CB message
types in a clear way on UE side.
A UE supporting Cell Broadcast Services shall be capable to receive BMC messages in the RRC Idle mode.
Reference(s)
To verify, that a BMC configuration for a UE is able to receive activated CBS messages when in RRC Idle mode.
Initial conditions
UE is in RRC Idle mode; BMC entity is established
SS: 1 cell,
NOTE: The CB message ID stored on the SIM shall be known for this test (parameter for CBS PDU's). The CBS
data type shall be allocated and activated in the UE.
Support of BMC Yes/No
ICS: CBS message support - YES/No
IXIT: CBS-Data 1: Octetstring of N (where N1 and less than 1246)
NOTE: For CB-Data 1 IXIT, the manufacturer shall define CBS data as Octetstring together with the CB message
ID used for transmitting this CB data, which is indicated by the UE after reception in a clear way
according to the capabilities stored on the SIM. Furthermore, the manufacturer shall describe the
indication on UE side (e.g. certain CBS traffic information)
Test procedure
a) The UE in RRC Idle mode is triggered to wait for the next system information. The UE is activated to receive
CBS messages,
b) The UE and the SS have configured their RLC, MAC and PHYs layers with all CB related system information,
broadcasted by SS
c) The SS sends the CBS message containing an activated CBS message type according to CB-Data 1 to the UE;
this shall be repeated for "CPREP" times (indicated by parameter "repetition period")
d) The UE indicates in an unambiguous way, that this message was received, by certain clear indications (e.g. a
unique part of the CB data contents)
Release 5 404 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

Transmit this message as described below on
the BCCH, in addition to the regular BCCH
transmissions (see RRC test description).
Included are CB related system information
parameter of the CBS:
- CTCH ID,
- FACH ID and associated format set,
- S-CCPCH ID,
- BMC Schedule Level 1 information (N,K)

2 The SS waits for about 10 s to make sure, that
the UE is configured to receive CBS data
3 BMC CBS Message

Activated CBS message with CB Data 1
message content as described by the
manufacturer. This message shall be repeated
"CPREP" times, Parameter:
- Message_ID,
- Serial-No,
- Data coding scheme,
- CB-Data 1,
4 After having received the BMC CBS message
the UE shall indicate the reception of CB Data 1
in a clear way.

SYSTEM INFORMATION TYPE 5 AND 6
The contents of SYSTEM INFORMATION TYPE 5 AND 6 Information Element in this test case are identical to those
of the default contents of layer 3 messages for RRC tests [TS 34.123-1] with the following exceptions:
CHOICE mode
- CTCH allocation period
- CTCH frame offset
Secondary CCPCH system
- Secondary CCPCH information
- TFCS
- FACH/PCH information
- TFS
- CTCH indicator
(see RRC default test settings)
N
K
1
1
TRUE

BMC CBS Message
Message Type

Message ID

Serial Number
- Geographic Scope Indicator (2 bit)
- Message Code (10 bit)
- Update Number (4 bit)

Data Coding Scheme

CB Data
1 (CBS message)

Bitstring (16) CB message ID, it shall fit to the stored
Message ID in the SIM inserted in the UE (source and
type) [see TS 23.041] according to the transmitted CB-
Data 1 content.
[see TS 23.041]
11 (Normal Cell wide)
in accordance with the Message ID
for a new message: 0000, incremented by one for each
repetition

Bitstring (16) ID of the alphabet/coding and the applied
language [see TS 23.041]
Octetstring, [see IXIT value: CB-Data 1]

Release 5 405 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
The UE shall store and decode a received activated CBS message.
7.4.2.2 UE in RRC Connected mode, state CELL_PCH
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages (...) in CELL_PCH RRC-
state of Connected mode.
Reference(s)
To verify, that a BMC configuration for a UE is able to receive activated CBS messages when in RRC Connected
mode, state CELL_PCH.
Initial conditions
UE is in Connected mode state CELL_PCH; BMC entity is established
SS: 1 cell,
ICS:
CBS message support - YES/No
IXIT: CBS-Data 1: Octetstring of N (where N1 and less than 1246)
Test procedure
a) The UE in RRC CELL_PCH is triggered to wait for the next system information. The UE is activated to receive
CBS messages.
broadcasted by SS.
Release 5 406 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
c) The SS sends the CBS message containing an activated CBS message type according to CB-Data 1 to the UE;
this shall be repeated for "CPREP" times (indicated by parameter "repetition period").
unique part of the CB data contents).
Expected sequence
UE SS

- CTCH ID,
- S-CCPCH ID,
2
The SS waits for about 10 s to make sure, that
3 BMC CBS Message

- Message_ID,
- Serial-No,
- CB-Data 1,
in a clear way.

SYSTEM INFORMATION TYPE 5 and 6
The contents of SYSTEM INFORMATION TYPE 5 and 6 Information Element in this test case are identical to those of
the default contents of layer 3 messages for RRC tests [TS 34.123-1] with the following exceptions:
CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator
N
K
1
1
TRUE

Release 5 407 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
BMC CBS Message
Message Type

Message ID

Serial Number

Data Coding Scheme

CB Data
1 (CBS message)

Data 1 content.
[see TS 23.041]
repetition


7.4.2.3 UE in RRC Connected mode, state URA_PCH
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages (...) in CELL_PCH and
URA_PCH RRC-state of Connected mode.
Reference(s)
TS 25.324 clause 9.1.
To verify, that a BMC configuration for a UE is able to receive activated CBS messages when in RRC Connected
mode, state URA_PCH.
Initial conditions
UE is in Connected mode state URA_PCH; BMC entity is established
SS: 1 cell.
ICS:
Release 5 408 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CBS message support - YES/No.
IXIT: CBS-Data 1: Octetstring of N (where N1 and less than 1246).
Test procedure
a) The UE in RRC URA_PCH is triggered to wait for the next system information. The UE is activated to receive
CBS messages.
broadcasted by SS.
c) The SS sends the CBS message containing an activated CBS message type according to CB-Data 1 to the UE,
this shall be repeated for "CPREP" times (indicated by parameter "repetition period").
unique part of the CB data contents).
Expected sequence
UE SS

- CTCH ID,
- S-CCPCH ID,
2
The SS waits for about 10 s to make sure, that
3 BMC CBS Message

- Message_ID,
- Serial-No,
- CB-Data 1,
in a clear way.

Release 5 409 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator
N
K
1
1
TRUE

BMC CBS Message
Message Type

Message ID

Serial Number

Data Coding Scheme

CB Data
1 (CBS message)

Data 1 content.
[see TS 23.041]
repetition


7.4.2.4 UE in RRC Idle mode (ANSI-41 CB data)
Applicable only for a UE supporting Cell Broadcast Services (CBS) for ANSI-41 CB data as a type of
Broadcast/Multicast Services.
It shall be possible to indicate the reception of a certain CBS41 message content carried with certain activated CB41
message types in a clear way on UE side.
A UE supporting Cell Broadcast Services shall be capable to receive BMC messages in RRC Idle mode. ()BMC
messages are identified: (), CBS41 Message
Reference(s)
TS 25.324 clause 9.1.
Release 5 410 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
To verify, that a BMC configuration supporting ANSI-41 CB Data is able to receive activated CBS41 messages when in
RRC Idle mode.
Initial conditions
UE is in RRC Idle mode; BMC entity is established.
SS: 1 cell,
NOTE: The CB message ID stored on the SIM shall be known for this test (parameter for CBS41 PDU's). The
CBS41 data type shall be allocated and activated in the UE.
ICS:
CBS41 message support - YES/No.
IXIT: CB41-Data 1: Octetstring of N (where N1 and less than 1246).
NOTE: For CB41-Data 1 IXIT, the manufacturer shall define CBS data as Octetstring together with the CB
message ID used for transmitting this CB41 data, which is indicated by the UE after reception in a clear
way according to the capabilities stored on the SIM. Furthermore, the manufacturer shall describe the
indication on UE side (e.g. certain CBS41 traffic information)
Test procedure
expected CBS41 messages as described by the manufacturer.
broadcasted by SS.
c) The SS sends the CBS41 message containing an activated CBS41 message type according to CB41-Data 1 to the
UE; this shall be repeated for "CPREP" times (indicated by parameter "repetition period").
unique part of the CB41 data contents).
Release 5 411 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

- CTCH ID,
- S-CCPCH ID,
In addition, the MIB and SIB 16 are sent as
described below to setup the ANSI-41
parameters

the UE is configured to receive CB41 data
3 BMC CBS41 Message

Activated CBS message with CB41 Data 1
- Message_type,
- Broadcast Address
- CB41-Data 1
the UE shall indicate the reception of CB41 Data
1 in a clear way.

MASTER INFORMATION BLOCK (MIB)
The contents of MASTER INFORMATION BLOCK Information Element in this test case are identical to those of the
default contents of layer 3 messages for RRC tests [TS 34.123-1] with the following exceptions:
ANSI-41 Core Network information Present

SYSTEM INFORMATION TYPE 5 AND 6
The contents of SYSTEM INFORMATION TYPE 5 AND 6 Information Element in this test case are identical to those
of the default contents of layer 3 messages for RRC tests [TS 34.123-1] with the following exceptions:
CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator
N
K
1
1
TRUE

Release 5 412 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
SYSTEM INFORMATION TYPE 13
The contents of SYSTEM INFORMATION TYPE 13 Information Element in this test case are identical to those of the
CHOICE CN Type
- CN domain specific NAS information
- NAS (ANSI-41) system information
ANSI-41

T.B.D

BMC CBS41 Message
Message Type
Broadcast Address
CB Data41
3 (CBS41 Message)
Bitstring (40) Address Information of higher layer
Octetstring, [see IXIT value: CB41-Data 1] (ANSI-41)

The UE shall store and decode a received activated CBS41 message.
7.4.2.5 UE in RRC Connected mode, state CELL_PCH (ANSI-41 CB data)
It shall be possible to indicate the reception of certain CBS41 message contents carried with certain activated CB41
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages (...) in CELL_PCH RRC-
state of Connected mode. ()BMC messages are identified: (), CBS41 Message.
Reference(s)
TS 25.324 clause 9.1.
RRC Connected mode, state CELL_PCH.
Initial conditions
UE is in Connected mode state CELL_PCH; BMC entity is established.
SS: 1 cell,
NOTE: The CB41 message ID stored on the SIM shall be known for this test (parameter for CBS41 PDU's). The
Release 5 413 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
ICS:
IXIT: CBS41-Data 1: Octetstring of N (where N1 and less than 1246).
indication on UE side
Test procedure
a) The UE in RRC CELL_PCH is triggered to wait for the next system information. The UE is activated to receive
b) The UE and the SS have configured their RLC, MAC and PHYs layers with all CB41 related system
information, broadcasted by SS.
UE; this shall be repeated for "CPREP" times (indicated by parameter "repetition period").
Expected sequence
UE SS

- CTCH ID,
- S-CCPCH ID,
described below for setup the ANSI-41
parameters

3 BMC CBS41 Message

- Message_type,
- Broadcast Address
- CB41-Data 1
1 in a clear way.

Release 5 414 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP

CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator

N
K
1
1
TRUE

CHOICE CN Type
ANSI-41

T.B.D

BMC CBS41 Message
Message Type
Broadcast Address
CB Data41
3 (CBS41 Message)

7.4.2.6 UE in RRC Connected mode, state URA_PCH (ANSI-41 CB data)
It shall be possible to indicate the reception of a certain CBS41 message content carried with certain activated CB41
Release 5 415 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages (...) in URA_PCH RRC-
state of Connected mode. ()BMC messages are identified: (), CBS41 Message.
Reference(s)
TS 25.324 clause 9.1.
RRC Connected mode, state URA_PCH.
Initial conditions
UE is in Connected mode state URA_PCH; BMC entity is established.
SS: 1 cell,
NOTE: The CB41 message ID stored on the SIM shall be known for this test (parameter for CBS41 PDU's). The
ICS:
IXIT: CBS41-Data 1: Octetstring of N (where N1 and less than 1246).
indication on UE side (e.g. certain CBS41 traffic information).
Test procedure
a) The UE in RRC URA_PCH is triggered to wait for the next system information. The UE is activated to receive
broadcasted by SS.
UE, this shall be repeated for "CPREP" times (indicated by parameter "repetition period").
Release 5 416 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

- CTCH ID,
- S-CCPCH ID,
described below for setup the ANSI-41
parameters

3 BMC CBS41 Message

- Message_type,
- Broadcast Address
- CB41-Data 1
1 in a clear way.


CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator
N
K
1
1
TRUE

Release 5 417 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CHOICE CN Type
ANSI-41

T.B.D

BMC CBS41 Message
Message Type
Broadcast Address
CB Data41
3 (CBS41 Message)

7.4.3 BMC message reception procedure
7.4.3.1 Reception of certain CBS message types
Applicable only for a UE supporting Cell Broadcast Services (CBS) as type of Broadcast/Multicast Services.
It shall be possible to indicate the reception of two different CBS message contents carried with different activated CB
It shall be possible to activate/deactivate the CBS message types used to receive CB Data 1 or 2.
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in RRC Idle mode.
The BMC entity on UE side evaluates received BMC Schedule Messages and takes decisions which BMC messages are
received.
If not otherwise requested by upper layers, only those CB messages received in BMC CBS Messages should be
delivered to upper layers for which the Serial Number associated with the CB message has changed. This implies that
the BMC has to store the last received Serial Number of each CB message activated by upper layers.
Reference(s)
TS 25.324 clause 9.1.
TS 25.324 clause 9.4.
1. To verify, that a UE supporting CBS ignores a deactivated CBS message type which has been broadcasted by
SS.
2. To verify, that a UE only stores Serial Numbers of a newly transmitted CBS messages. This shall be verified by
indication of a received CBS message with changed Serial Number as indication for the storage of Serial
Numbers.
Release 5 418 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Initial conditions
UE is in RRC Idle mode.
SS: 1 cell,
NOTE: The CB message ID stored on the SIM shall be known for this test (as parameter for the CBS message
PDU). The CBS data type shall be allocated and in the UE. It shall be possible to activate/deactivate such
CBS data type.
ICS:
CBS message support - YES/No.
IXIT:
- CBS-Data 1: Octetstring of N (where N1 and less than 1246), with used CB message ID for CB-Data 1.
- CBS-Data 2: Octetstring of N (where N1 and less than 1246), with used CB message ID for CB-Data 2 (CB
message ID for CB-Data 1 shall be different to CB message ID for CB-Data 2).
NOTE: For CBS data IXIT's, the manufacturer shall define CBS data as Octetstring as described in the IXIT,
which is indicated by the UE after reception in a clear way according to the capabilities stored on the
SIM. The manufacturer shall describe the indication on UE side for both CBS data types (e.g. certain
CBS broadcast information shown in the display of the UE).
Test procedure
CBS data 1, CBS data 2) are deactivated.
broadcasted by SS.
c) The SS sends the first BMC CBS schedule message to predict the next CBS messages to the UE.
d) The SS sends the CBS message containing CB-Data 1 to the UE, together with the CBS schedule message to
predict the next CBS messages (repetition of CB Data 1, and the next CBS schedule message).
e) The UE indicates on an unambiguous way, that this CB-Data 1 has been received by the UE (e.g. a unique part
of the CBS data contents shown on the display).
f) The SS sends the repeated CB Data 1, and the next CBS schedule message to predict the next CBS messages to
the UE. (CBS schedule message predicts the first repetition of CB Data).
g) The UE indicates on an unambiguous way, that CB-Data 2 has been received by the UE (e.g. a unique part of the
CBS data contents shown in the display).
h) The UE deactivates the CB Message type ID used for CB-Data 1.
i) The SS sends the CB Data 2 (as deactivated CB Data type) to the UE.
j) The UE ignores the newly received CB-Data 2, i.e. there is no indication for this CB Data 2 as described in step
e).
Release 5 419 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Expected sequence
UE SS

Transmit these messages as described below
on the BCCH, in addition to the regular BCCH
transmissions.
Included are all CB related system information
- CTCH ID,
- S-CCPCH ID,
the UE is configured to receive the CBS Data
message
3 BMC CBS Schedule

Inband CBS schedule message with BMC
schedule information Level 2 (DRX) to predict
the next CB data block (CB Data 1 new-, CBS
Schedule message)
4 BMC CBS Message

Activated CBS message with certain CB data
content (CBS data 1 as described by the
manufacturer). This message is sent the first
time. Parameter:
- Message_ID,
- Serial-No,
- CB-Data 1 (new)
5 After having received the BMC CB-Data 1 the
UE shall indicate the reception in a clear way.
6 BMC CBS Schedule

the next CB data block (CB Data 1 rep.1-, CBS
Schedule message)
7 BMC CBS Message Activated CBS message with certain CB data
manufacturer). This message is repeated.
Parameter:
- Message_ID,
- Serial-No,
- CB-Data 1 (old)
8 The UE deactivates "CB message type ID" used
for CB-Data 1
9 BMC CBS Schedule

the next CB data block (CB Data 2 new-).
10 BMC CBS Message Deactivated CBS message with certain CB data
manufacturer). This message is sent the first
time. Parameter:
- Message_ID,
- Serial-No,
- CB-Data 2 (new)
(CB-Data 2) the UE shall ignore the newly
received CBS data 1 message, i.e. there is no
indication as described by the manufacturer.

Release 5 420 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
CHOICE mode
- CTCH frame offset
- TFCS
- TFS
- CTCH indicator
N
K
1
1
TRUE

BMC CBS Message (Step 4 and 7)
Message Type

Message ID

Serial Number

Data Coding Scheme

CB Data
1 (CBS message)

type) [see TS 23.041]
[see TS 23.041]
according with the Message ID
repetition


BMC CBS Message (Step 10)
Message Type

Message ID

Serial Number

Data Coding Scheme

CB Data
1 (CBS message)

type) [see TS 23.041]
[see TS 23.041]
according with the Message ID
repetition


BMC Schedule Message (Step 3, 6 and Step 9)
The parameters for BMC Schedule Message (inband schedule message) in Step 5 are inserted for CB-Data 2 and in
Step 8 for CB-Data 1.
Release 5 421 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
Message Type

Offset to begin CTCH BS index

Length of CBS Schedule Period

New Message Bitmap

Message Description
- Message Description Type

- Message ID

- Offset to CTCH (BS index of first transmission)
2 (Schedule message)

calculated offset value of the BS (Integer: 0...255) as
recommended in TR 25.925

Number of consecutive CTCH BS of the next CBS
Schedule Period, (Integer: 1...255) as recommended in
TR 25.925

Bitmap (N*8), N =Length of CBS Schedule Period as
recommended in TR 25.925

1 for new message (see TS 25.324, Table 11.9-3)
5 for old message (see TS 25.324, Table 11.9-3)

CB message ID used for the next CB data

for Message description type 1 or 5: CB message ID IE
included (see TS 23.041)

After having received the CB-Data 1 message (step 4), the UE shall store the Serial Number of this message and
indicate the reception of the CBS message as described by the manufacturer.
After CB-Data 2 message was newly broadcasted (step 10), the UE shall not indicate the reception for the deactivated
CBS message (CB-Data 1).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
422
8 Radio Resource Control RRC
8.1 RRC Connection Management Procedure
8.1.1 Paging
8.1.1.1 Paging for Connection in idle mode

A UE in idle mode, CELL_PCH state or URA_PCH state shall receive the paging information for all its monitored
paging occasions. For an UE in idle mode, the paging occasions are specified in [25.304] and depend on the IE "CN
domain specific DRX cycle length coefficient", as specified in subclause 8.6.3.1a. For a UE in CELL_PCH state or
URA_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC
State Indicator", as specified in subclauses 8.6.3.2 and 8.6.3.3 respectively.
When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.
If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:
1>if the IE "Used paging identity" is a CN identity:
2>compare the IE "UE identity" with all of its allocated CN UE identities:
2>if one match is found:
3>indicate reception of paging; and
3>forward the IE "CN domain identity", the IE "UE identity" and the IE "Paging cause" to the upper layers.
1>otherwise:
2>ignore that paging record.
:
In the UE, the initial direct transfer procedure shall be initiated, when the upper layers request establishment of a
signalling connection. This request also includes a request for the transfer of a NAS message.
Upon initiation of the initial direct transfer procedure when the UE is in idle mode, the UE shall:
1>set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers;
1>perform an RRC connection establishment procedure, according to subclause 8.1.3;
1>if the RRC connection establishment procedure was not successful:
2>indicate failure to establish the signalling connection to upper layers and end the procedure.
1>when the RRC connection establishment procedure is completed successfully:
2>continue with the initial direct transfer procedure as below.
Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall:
1>perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission";
1>when the cell update procedure completed successfully:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
423
The UE shall, in the INITIAL DIRECT TRANSFER message:
1>set the IE "NAS message" as received from upper layers; and
1>set the IE "CN domain identity" as indicated by the upper layers; and
1>set the IE "Intra Domain NAS Node Selector" as follows:
2>derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and
2>provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:
1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a
valid TMSI/PTMSI is available;
2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;
3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.
1>calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and
1>include the calculated START value for that CN domain in the IE "START".
In CELL_FACH state, the UE shall:
1>include a measurement report in the IE "Measured results on RACH", as specified in the IE "Intra-frequency
reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" in System
Information Block type 12 (or "System Information Block Type 11" if "System Information Block Type 12" is
not being broadcast);
1>include in the IE "Measured results on RACH" all requested reporting quantities for cells for which
measurements are reported.
The UE shall:
1>transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio
bearer RB3;
1>when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission:
2>confirm the establishment of a signalling connection to upper layers; and
2>add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS.
1>when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC:
2>the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.2 and 8.1.8, 3GPP TS 25.211 clause 5.3.3.10 (FDD), 3GPP TS25.221 (TDD), 3GPP TS
25.304 clause 8.
1) For the CS domain
To confirm that the UE establishes an RRC connection after it receives a PAGING TYPE 1 message which
includes IE "UE identity"(in IE "Paging Record") set to the IMSI of the UE, and responds with a correct
INITIAL DIRECT TRANSFER message.
2) For the PS domain
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
424
includes IE "UE identity"(in IE "Paging Record") set to the P-TMSI allocated by SS at initial attach and
responds with a correct INITIAL DIRECT TRANSFER message.
Initial Condition
System Simulator: 1 cell
UE: If the CN domain being tested is CS:
MM-IDLE state and Updated update status with no TMSI
GMM-Registered with no P-TMSI (if PS supported)
If the CN domain being tested is PS:
GMM-Registered with a P-TMSI assigned
MM-IDLE state and Updated update status with no TMSI (if CS supported)
In both cases the UE shall have an IMSI.
Test Procedure
SS transmits SYSTEM INFORMATION BLOCK TYPE 1 or 13 messages, depending on the CN type supported by the
UE. The SS transmits a PAGING TYPE 1 message, which includes an unmatched CN UE identity for the UE in the idle
state. The UE shall not change its state. The SS transmits a PAGING TYPE 1 message, which includes a matched CN
UE identity for the UE in the idle state. During transmission of PAGING TYPE 1 messages, SS selects the correct
paging indicator on the PICH in order to allow the UE to respond to paging. Then the UE transmits an RRC
CONNECTION REQUEST to the SS, the SS transmits an RRC CONNECTION SETUP to the UE. When the UE
receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION SETUP
COMPLETE message and an INITIAL DIRECT TRANSFER message on the uplink DCCH.
NOTE: For UEs supporting GSM-MAP CN type only, SYSTEM INFORMATION TYPE 1 messages are to be
sent by SS in this test case. On the other hand, SS transmits SYSTEM INFORMATION TYPE 13
messages if the UE under test supports only ANSI-41 CN type.
Expected sequence
UE SS
1 SYSTEM INFORMATION BLOCK
TYPE 13 or SYSTEM INFORMATION
BLOCK TYPE 1
Transmit these messages on the
BCCH. See default message
contents in TS 34.108.
2 PAGING TYPE 1 The SS transmits the message,
which includes an unmatched
identity (incorrect IMSI), and the
UE does not change its state.
which includes a matched identity.
See default message contents in
TS 34.108.
5 RRC CONNECTION SETUP SS assigns DPCH resources to
allow UE to establish an RRC
connection.
6 RRC CONNECTION SETUP
COMPLETE

7 INITIAL DIRECT TRANSFER

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
425
SYSTEM INFORMATION BLOCK TYPE 1 (Step 1) for UEs supporting GSM-MAP core networks
Use the default message type found in TS 34.108, clause 6.1.
SYSTEM INFORMATION TYPE 13 (Step 1) for UEs supporting ANSI-41 core networks
PAGING TYPE 1 (Step 2)
Message Type
Paging record list Only 1 entry
Paging record
CHOICE Used paging identity CN identity
- Paging cause Terminating Call with one of the supported services
- CN domain identity A Registered Domain (PS Domain or CS Domain)
- CHOICE UE Identity IMSI
- IMSI Set to an arbitrary octet string of length 7 bytes which is
different from the IMSI value stored in the TEST USIM
card.
BCCH modification info Not Present

Note that Separate message types are defined in TS 34.108 for the cases of TM (Speech in CS) and for TM (Packet in
PS).
RRC CONNECTION REQUEST (Step 4)
Message type
Initial UE identity Same as the IMSI stored in the TEST USIM card, or the
registered P-TMSI depending upon CN domain
concerned.
Establishment Cause Check to see if it is set to the same value as "Paging
Cause" IE in the PAGING TYPE 1 message transmitted
on step 3.
Protocol Error Indicator Check to see if it is set to FALSE
Measured results on RACH Not checked.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
426
INITIAL DIRECT TRANSFER (Step 7) for UEs supporting GSM-MAP core networks
Message Type
Integrity check info Not present
CN domain identity CS domain or PS domain (as specified by the SS in the
PAGING TYPE 1 message of Step 3)
Intra Domain NAS Node Selector
- CHOICE version R99
-- CHOICE CN type GSM-MAP
--- CHOICE Routing basis IMSI (response to IMSI paging) in CS domain)
P-TMSI (response to P-TMSI paging in PS Domain)
---- Routing parameter If the IE "CN domain identity" is equal to "CS domain", bit
string (10) consisting of DecimalToBinary [(IMSI div 10)
mod 1000]. The first/ leftmost bit of the bit string contains
the most significant bit of the result.
If the IE "CN domain identity" is equal to "PS domain":
The TMSI/ PTMSI consists of 4 octets (32bits). This can
be represented by a string of bits numbered from b0 to
b31, with bit b0 being the least significant. The "Routing
parameter" is set to bits b14 through b23 of the TMSI/
PTMSI. The first/ leftmost/ most significant bit of the bit
string contains bit b23 of the TMSI/ PTMSI.
--- Entered parameter Not checked
NAS message Not checked
START Not checked
Measured results on RACH Not checked

INITIAL DIRECT TRANSFER (Step 7) for UEs supporting ANSI-41 core networks
Message Type
- CHOICE version ANSI-41 : Bitstring(14), all bits set to 0
START Not checked

After step 2 the UE shall not respond to PAGING TYPE 1 message sent in step 2.
After step 3 the UE shall transmit RRC CONNECTION REQUEST message on the uplink CCCH.
After step 5 the UE shall have an RRC connection based on dedicated physical channel resources and transmit an RRC
CONNECTION SETUP COMPLETE message and INITIAL DIRECT TRANSFER message on the uplink DCCH.
8.1.1.2 Paging for Connection in connected mode (CELL_PCH)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
427
:
If the UE is in connected mode, for each occurrence of the IE "Paging record" included in the message the UE shall:
1>if the IE "Used paging identity" is a UTRAN identity and if this U-RNTI is the same as the U-RNTI allocated to
the UE:
2>if the optional IE "CN originated page to connected mode UE" is included:
3>forward the IE "CN domain identity", the IE "Paging cause" and the IE "Paging record type identifier" to
the upper layers.
2>otherwise:
3>perform a cell update procedure with cause "paging response" as specified in subclause 8.3.1.2.
2>ignore any other remaining IE "Paging record" that may be present in the message.
1>otherwise:
the UE shall:
Reference
3GPP TS 25.331 clause 8.1.2, 8.3.1.7.
To confirm that the UE enters the CELL_FACH state after it receives a PAGING TYPE 1 message which indicates that
the paging has originated from UTRAN. To verify that the UE performs cell update procedure after entering the
CELL_FACH state.
Initial Condition
UE: CELL_PCH state (state 6-12) as specified in clause 7.4 of TS 34.108, with a valid U-RNTI already assigned by the
SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
428
Test Procedure
UE. The SS transmits a PAGING TYPE 1 message, which includes an unmatched U-RNTI. The UE does not change its
state. Then SS transmits a PAGING TYPE 1 message with a matched identifier but originates from the CN instead of
UTRAN. The UE shall not change state after receiving this message. The SS transmits a PAGING TYPE 1 message,
which includes a matched U-RNTI. Then the UE enters the CELL_FACH state and performs the cell updating
procedure.
Expected sequence
UE SS
BLOCK TYPE 1

Transmit these messages on the
BCCH, in addition to the normal
BCCH transmissions. See specific
message contents
2 PAGING TYPE 1 The SS transmits a message
including an unmatched identifier.
UE shall not respond to the paging.
3 PAGING TYPE 1 The SS transmits a message
includes a matched identifier but
with the used paging identity being
a CN identity, UE shall not respond
to the paging.
4 PAGING TYPE 1 The SS transmits the message
with used paging identity being a
UTRAN identity and including the
UE's assigned U-RNTI
5 CELL UPDATE The UE enters the CELL_FACH
state. UE performs cell updating
procedure. The CELL UPDATE
message shall contain the value
"Cell Update Cause" set to "paging
response".
6 CELL UPDATE CONFIRM See message content.
CONFIRM

Message Type
Paging record
- CHOICE Used paging identity UTRAN identity
- U-RNTI
- SRNC Identity Set to an arbitrary 16-bit string which is different from
the SRNC identity assigned.
- S-RNTI Set to an arbitrary 20-bit string which is different from
the S-RNTI assigned.
- CN originated page to connected mode UE Not Present

Same as the PAGING TYPE 1 message as in step 3 of clause 8.1.1.1.4.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
429
Message Type
Paging record
- U-RNTI
- SRNC Identity Set to the same SRNC identity as previously assigned.
- S-RNTI Set to the same S-RNTI as previously assigned.

SYSTEM INFORMATION BLOCK TYPE 13
Use the same SYSTEM INFORMATION BLOCK TYPE 13 message as specified in clause 8.1.1.1.4.
Use the same SYSTEM INFORMATION BLOCK TYPE 1 message as specified in clause 8.1.1.1.4.
Use the message sub-type in default message content defined in [9] (TS 34.108) Clause 9, with the following
exceptions.
New C-RNTI '1010 1010 1010 1010'

After step 2 the UE shall not respond to the PAGING TYPE 1 message sent in step 2.
After step 4 the UE shall enter the CELL FACH state and send a CELL UPDATE message with "Cell Update Cause"
IE set to "paging response".
After step 6 the UE shall be in the CELL_FACH state and shall transmit UTRAN MOBILITY INFORMATION
CONFIRM message.
8.1.1.3 Paging for Connection in connected mode (URA_PCH)
:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
430
the UE:
the upper layers.
2>otherwise:
1>otherwise:
the UE shall:
Reference
3GPP TS 25.331 clause 8.1.2, 8.3.1.7.
To confirm that the UE enters the CELL_FACH state after it receives a PAGING TYPE 1 message in which the IE
"Used paging identity" is set to "UTRAN identity", and the UE takes the U-RNTI value assigned to it in the IE "U-
RNTI".
Initial Condition
UE: URA_PCH state (state 6-13) as specified in clause 7.4 of TS 34.108, with a valid U-RNTI assigned by the SS.
Test Procedure
The SS transmits a PAGING TYPE 1 message, which includes an unmatched U-RNTI. The UE does not change its
current state. The SS transmits a PAGING TYPE 1 message which includes a matched U-RNTI. Then the UE listens to
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
431
it and enters the CELL_FACH state to transmit a CELL UPDATE message using uplink CCCH in respond to the
paging.
Expected sequence
UE SS
1 PAGING TYPE 1 The SS transmits the message that
includes an unmatched identifier,
but UE does not change its state.
includes a matched identifier.
state.
CONFIRM

Message Type
Paging record
- U-RNTI
- SRNC Identity Set to an unused SRNC identity which is different from

Message Type
Paging record
- U-RNTI
- SRNC Identity Set to the previously assigned SRNC identity
- S-RNTI Set to previously assigned S-RNTI

exceptions.
New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
432
After step 1 the UE shall not respond to the paging.
After step 2 the UE shall enter the CELL FACH state, and transmit CELL UPDATE message to initiate the cell
updating procedure with the paging cause set to "paging response".
After step 4 the UE shall be in the CELL_FACH state and shall transmit UTRAN MOBILITY INFORMATION
CONFIRM message.
8.1.1.4 Paging for notification of BCCH modification in idle mode
A UE in idle mode state shall receive the paging information for all its monitored paging occasions. For an UE in idle
mode, the paging occasions are specified in TS 25.304 and depend on the IE "CN domain specific DRX cycle length
coefficient".

If the IE "BCCH modification info" is included, any UE in idle mode state shall perform the actions as specified in TS
25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message.
The UE shall:
1>compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the
master information block in variable VALUE_TAG.
1>if the value tags differ:
2>read the master information block on BCH;
2>if the value tag of the master information block in the system information is the same as the value in IE "MIB
value tag" in "BCCH modification info" but different from the value tag stored in the variable
VALUE_TAG:
3>perform actions as specified in TS 25.331 subclause 8.1.1.5.

Upon reception of the master information block, the UE shall:
1>compare the value tag in the master information block with the value tag stored for this cell and this PLMN in
the variable VALUE_TAG;
2>store the value tag into the variable VALUE_TAG for the master information block;
2>read and store scheduling information included in the master information block.
.
For all system information blocks or scheduling blocks that are supported by the UE referenced in the master
information block or the scheduling blocks, the UE shall perform the following actions:
1>for all system information blocks with area scope "PLMN" or "Equivalent PLMN" that use value tags:
2>compare the value tag read in scheduling information for that system information block with the value stored
within the variable VALUE_TAG for that system information block;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
433
3>store the value tag read in scheduling information for that system information block into the variable
VALUE_TAG;
3>read and store the IEs of that system information block.

Reference
3GPP TS 25.331 clause 8.1.1, 8.1.2.
To confirm that the UE checks the new value tag of the master information block and reads the updated SYSTEM
INFORMATION BLOCK messages after it receives a PAGING TYPE 1 message which includes the IE "BCCH
Modification Information".
Initial Condition
UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on
the CN domain(s) supported by the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
434
Test Procedure
The SS transmits a PAGING TYPE 1 message. This message addresses the UE using its (P)TMSI and the "paging
cause" IE set to a terminating call type that is supported by the UE. The UE shall respond with RRC CONNECTION
REQUEST message. Then SS shall transmit RRC CONNECTION REJ ECT message to UE.
The SS transmits a PAGING TYPE 1 message on the paging occasions assigned to the UE. The message shall include
the IE "BCCH Modification Information" indicating the value tag of the modified master information block. For a time
SS continuously broadcasts the original MASTER INFORMATION BLOCK and various types of SYSTEM
INFORMATION BLOCK on the BCCH mapped to BCH transport channel. Then it transmits the new master
information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 message. In the new SIB TYPE 5
message, the IE "Available Signature" is different when compared to the original SIB TYPE 5 message.
At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its
(P)TMSI and the "paging cause" IE set to a terminating call type that is supported by the UE. The UE shall respond
with RRC CONNECTION REQUEST message. Then SS shall transmit RRC CONNECTION REJ ECT message to UE.
Expected sequence
UE SS
1 PAGING TYPE 1 SS starts to transmit this message
on the PCCH at the correct paging
occasion.
1a RRC CONNECTION REQUEST
1b RRC CONNECTION REJ ECT
2 PAGING TYPE 1 SS transmits the message
including the IE "BCCH
Modification Information", with the
"Value Tag" changed from the
"MIB Value Tag" of the current
Master Information Block. SS
continues to broadcast the original
MASTER INFORMATION BLOCK
and various types of SYSTEM
INFORMATION BLOCK on BCCH.
2a SS waits 5s (to ensure that the UE
waits for the new value tag before
re-reading system information)
3


SYSTEM INFORMATION BLOCK
TYPE 5
At the SFN indicated by the BCCH
modification time, SS starts to
transmit the MIB with the "MIB
Value Tag" IE different from the
original setting.

At the same time, SS starts to
transmit the affected SIB TYPE 5
messages continuously. The IE
"Available Signature" is changed
from "0000 0000 1111 1111(B)" to
"1111 1111 0000 0000(B)".

has time to read the new system
information)
4 PAGING TYPE 1 SS starts to transmit this message
continuously on the PCCH at the
correct paging occasion.
6 RRC CONNECTION REJ ECT

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
435
PAGING TYPE 1 (Step 1 and 4)
Message Type
Paging record
- CHOICE Used paging identity CN identity
- Paging Cause Terminating Call with one of the supported services
- CN Domain Identity Supported Domain (PS Domain or CS Domain)
- CHOICE UE Identity Local (P)TMSI
- Routing parameter Same as registered TMSI or P-TMSI

RRC CONNECTION REJ ECT (Step 1b)
Use the same message type found in [9] TS 34.108 clause 9.
Message Type
Paging record list Not Present
MIB Value Tag Set to (Current MIB value tag +1)
BCCH Modification time Not Present

MASTER INFORMATION BLOCK (Step 3)
MIB Value tag As in PAGING TYPE 1 in step 2

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3)
Use the same message type found in clause 6.1 of TS 34.108, with the following exception.
- PRACH system information
- PRACH info
- CHOICE mode FDD
- Available Signature '1111 1111 0000 0000'B

RRC CONNECTION REJ ECT
Use the same message type found in TS 34.108, clause 9.
After step 1 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1
messages sent in step 1, using an allowed signature according to original IE "Available signature" in SYSTEM
INFORMATION BLOCK TYPE 5.
After step 4 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1
messages sent in step 4, using an allowed signature according to modified IE "Available signature" in SYSTEM
INFORMATION BLOCK TYPE 5.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
436
8.1.1.5 Paging for notification of BCCH modification in connected mode
(CELL_PCH)
A UE in CELL_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in
CELL_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE
"RRC State Indicator", as specified in TS 25.331 subclauses 8.6.3.2 and 8.6.3.3 respectively.

If the IE "BCCH modification info" is included, any UE in CELL_PCH state shall perform the actions as specified in
TS 25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message.
The UE shall:
VALUE_TAG:
3>perform actions as specified in TS 25.331 subclause 8.1.1.5.

.
VALUE_TAG;

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
437
Reference
3GPP TS 25.331 clause 8.1.1, 8.1.2.
To confirm that the UE, in addition to any actions caused by the IE "Paging record" occurrences in the PAGING TYPE
1 message, checks the new value tag of the master information block, and read the SYSTEM INFORMATION
messages after it receives a PAGING TYPE 1 message which includes the IE "BCCH Modification Information".
Initial Condition
UE: CELL_PCH state (state 6-12) as specified in clause 7.4 of TS 34.108 with valid a U-RNTI assigned to it.
Test Procedure
The SS transmits a PAGING TYPE 1 message on the paging occasions assigned to the UE. The PAGING TYPE 1
message shall include the IE "BCCH Modification Information" indicating value tag of themodified master information
block. For a time, SS continuously broadcasts the original MASTER INFORMATION BLOCK and various types of
SYSTEM INFORMATION BLOCK on the BCCH mapped to BCH transport channel. Then it transmits the new
master information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 message. In the new SIB
TYPE 5 message, the IE "Available Signature" for FDD, "Available Channelisation codes indices " for TDD 3.84 Mcps
option or "Available SYNC_UL codes indices " for TDD 1.28 Mcps option is different when compared to the original
SIB TYPE 5 message. At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses
the UE using its U-RNTI. The UE shall respond with a CELL UPDATE message and set IE "cell update cause" to
"paging response". The SS shall transmit a CELL UPDATE CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
438
Expected sequence
UE SS
1 Void
2 PAGING TYPE 1 SS transmits the paging message
which comprises IE "BCCH
continuously broadcast the same
3


TYPE 5
original setting.

For FDD, at the same time, SS
starts to transmit the affected SIB
TYPE 5 continuously. The value of
IE "Available Signature" is changed
from "0000 0000 1111 1111(B)" to
"1111 1111 0000 0000(B)".

For TDD 3.84 Mcps option, at the
same time, SS starts to transmit
the affected SIB TYPE 6
continuously. The value of IE
"Available Channelisation codes
indices " is changed according to
test purposes.

"Available SYNC_UL codes indices
" is changed according to test
purposes.

information)
4

PAGING TYPE 1

SS transmits this message
correct paging occasion.
5 CELL UPDATE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
439
Message Type
- MIB Value Tag Set to (Current MIB value tag +1)
- BCCH Modification time Not Present


SYSTEM INFORMATION BLOCK TYPE 5 (Step 3)(FDD)
- PRACH info
- CHOICE mode FDD

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 3.84 Mcps option)
- PRACH info
- CHOICE mode TDD
- CHOICE TDD option 3.84 Mcps option
- Available Channelisation codes indices To be defined (each bit indicates availability of a
channelisation code index)

- PRACH info
- CHOICE mode TDD
- Available SYNC_UL codes indices To be defined (each bit indicates availability of a
SYNC_UL code index)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
440
Message Type
Paging record
- U-RNTI Equal to the U-RNTI assigned earlier.
- SRNC Identity
- S-RNTI

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:
U-RNTI Checked to see if it is set to the same values as in step
4
- SRNC identity
- S-RNTI
Cell update cause Paging response

Use the same message type found in (TS 34.108) Clause 9., with the following exception:
RRC State indicator CELL_PCH
UTRAN DRX cycle length coefficient 3

After step 4 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response",
using an allowed signature according to modified IE "Available signature" in SYSTEM INFORMATION BLOCK
TYPE 5.
8.1.1.6 Paging for notification of BCCH modification in connected mode (URA_PCH)
A UE in URA_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in
State Indicator", as specified in TS 25.331 subclauses 8.6.3.2 and 8.6.3.3 respectively.

If the IE "BCCH modification info" is included, any UE in URA_PCH state shall perform the actions as specified in TS
25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message as
specified above.
The UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
441
VALUE_TAG:
3>perform actions as specified in subclause 8.1.1.5.

.
VALUE_TAG;

Reference
3GPP TS 25.331 clause 8.1.1, 8.1.2.
To confirm that the UE checks the included new value tag of the master information block and reads the relevant
SYSTEM INFORMATION block(s) after it receives a PAGING TYPE 1 message which includes the IE "BCCH
Modification Information".
Initial Condition
UE: URA_PCH state (state 6-13) as specified in clause 7.4 of TS 34.108 with a valid U-RNTI assigned.
Test Procedure
The SS transmits a PAGING TYPE 1 message on the paging occasions assigned to the UE. The message shall include
the IE "BCCH Modification Information" indicating the value tag of the master information block . For a time, SS
continuously broadcasts the original MASTER INFORMATION BLOCK and various types of SYSTEM
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
442
INFORMATION BLOCK on the BCCH mapped to BCH transport channel. Then it transmits the new master
information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 message. In the new SIB TYPE 5
message, the IE "Available Signature" for FDD, "Available Channelisation codes indices " for TDD 3.84 Mcps option
or "Available SYNC_UL codes indices " for TDD 1.28 Mcps optionis different when compared to the original SIB
TYPE 5 message. At the next paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses
the UE using its U-RNTI and the "paging cause" IE set to a terminating call type that is supported by the UE. The UE
shall respond with a CELL UPDATE message and set IE "cell update cause" to "paging response". The SS shall
transmit a CELL UPDATE CONFIRM message.
Expected sequence
UE SS
1 Void
2 PAGING TYPE 1 SS transmits the paging message
which comprises IE "BCCH
continuously broadcast the same
3


TYPE 5
original setting.

For FDD, at the same time, SS
starts to transmit the affected SIB
TYPE 5 message continuously.
The value of IE "Available
Signature" is changed from "0000
0000 1111 1111(B)" to "1111 1111
0000 0000(B)".
"Available Channelisation codes
indices " is changed according to
test purposes.

"Available SYNC_UL codes indices
" is changed according to test
purposes.

information)
4 PAGING TYPE 1 SS transmits this message
correct occasion.
5 CELL UPDATE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
443
Message Type


- PRACH info
- CHOICE mode FDD

- PRACH info
- CHOICE mode TDD
- Available Channelisation codes indices To be defined (each bit indicates availability of a
channelisation code index)

- PRACH info
- CHOICE mode TDD
- Available SYNC_UL codes indices To be defined (each bit indicates availability of a
SYNC_UL code index)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
444
Message Type
Paging record
- U-RNTI Equal to the U-RNTI assigned earlier.
- SRNC Identity
- S-RNTI

U-RNTI Checked to see if it is set to the same values as in step
4
- SRNC identity
- S-RNTI
Cell update cause Paging response

Use the same message type found in TS 34.108, clause 9 with the following exceptions.
RRC State indicator URA_PCH

After step 4, the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response",
using an allowed signature according to modified IE "Available signature" in SYSTEM INFORMATION BLOCK
TYPE 5.
8.1.1.7 Paging for Connection in connected mode (CELL_DCH)
When the UE receives a PAGING TYPE 2 message, it shall not affect the state of any other ongoing RRC procedures,
when not stated otherwise elsewhere.
The UE shall:
1>forward the IE "Paging cause" and the IE "Paging record type identifier" to upper layers.

.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
445

The UE shall:
bearer RB3;
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a
radio access technology other than UTRAN, with a mandatory IE having a value, including choice, reserved for future
extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall:
1>if a default value of the IE is defined:
2>treat the rest of the message using the default value of the IE.
1>if no default value of the IE is defined:
2>set the variable PROTOCOL_ERROR_REJ ECT to TRUE;
2>set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Information
element value not comprehended";
2>perform procedure specific error handling according to clause 8.
Reference
3GPP TS 25.331 clause 8.1.8.2, 8.1.11.3, 9.4.
To confirm that the UE responds to a PAGING TYPE 2 message which includes the IE "Paging Cause" and the IE
"Paging Record Type Identifier".
To confirm that the UE responds with a RRC STATUS message after it has received an invalid PAGING TYPE 2
message.
To Page with the Paging Record Type Identifier set to "IMSI", in order to test the UEs behaviour to this situation which
may occur when details of the temporary identity have been lost in the core network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
446
Initial Condition
UE: CELL_DCH state (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108 after executing a location
registration and/or attach procedure. The UE has been registered in both CS and PS domains.
Test Procedure
The SS transmits an invalid PAGING TYPE 2 message. UE shall respond by transmitting a RRC STATUS message on
the uplink DCCH using RLC-AM mode. Finally, SS transmits a PAGING TYPE 2 message, which includes a matched
Paging Record Type Identifier. In the CS domainthe UE shall respond to this message by the transmission of an
INITIAL DIRECT TRANSFER message. In the PS Domain the UE will locally detach and then initiate a GPRS attach
procedure (as per clause 4.7.9.1.2 of TS 24.008) also involving the transmission of an INITIAL DIRECT TRANSFER
message.
Expected sequence
UE SS
1 Void
2 PAGING TYPE 2 SS pages UE from a new CN
domain, see specific message
contents.
3 RRC STATUS The UE shall respond by reporting
the protocol error to the SS.
4 PAGING TYPE 2 SS pages the UE with a matched
identifier and with a valid "paging
cause" IE from a new CN Domain.
5 INITIAL DIRECT TRANSFER The UE shall respond to the paging
message sent in step 4.

SS sends a message containing a protocol error causing the UE to perform procedure specific error handling.
Use the same message type found in clause 9 of TS 34.108, with the following exceptions.
Paging Cause Set to value "Spare"
CN Domain Identity Set to a new CN Domain
Paging Record Type Identifier Set to "IMSI (GSM-MAP)" for UEs supporting GSM-
MAP core network type or "IMSI (DS-41)" for UEs
supporting ANSI-41 core network type.

RRC STATUS (Step 3)
Use the same message type found in TS 34.108, clause 9, with the following exception.
Identification of received message
- Received message type PAGING TYPE 2
- RRC transaction identifier Checked to see if the value is identical to the same IE in
the PAGING TYPE 2 message.
Protocol error information
- Protocol Error Cause Information element value not comprehended

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
447
Use the same message type found in TS 34.108, clause 9, with the following exception.
Paging cause Terminating Call supported by the UE in the new
domain
CN domain identity New Domain supported by the UE
Paging record type identifier Set to "IMSI (GSM-MAP)" for UEs supporting GSM-

Check to see if the same message type found in TS 34.108 clause 9 is received, with the following exceptions:
CN domain identity CS domain or PS domain as specified in the PAGING
TYPE 2 message in Step 4.
-- CHOICE CN type GSM
--- CHOICE Routing basis local (P)TMSI if CS Domain
IMSI (cause UE initiated event) or IMSI (response to IMSI
paging) - if PS Domain
---- Routing parameter If the IE "CN domain identity" is equal to "CS domain":
The TMSI consists of 4 octets (32bits). This can be
represented by a string of bits numbered from b0 to b31,
with bit b0 being the least significant
The "Routing parameter" bit string consists of bits b14
through b23 of the TMSI/ PTMSI.
The first/ leftmost/ most significant bit of the bit string
contains bit b23 of the TMSI/ PTMSI.
The "Routing parameter" bit string consists of
DecimalToBinary [(IMSI div 10) mod 1000].
The first/ leftmost bit of the bit string contains the most
significant bit of the result.

Message Type
Integrity check info
- Message authentication code This IE is checked to see if it is present. The value is
compared against the XMAC-I value computed by SS.
significant bit of the MAC-I.
- RRC Message sequence number This IE is checked to see if it is present. The value is used
by SS to compute the XMAC-I value.
CN domain identity CS domain or PS domain as specified in the PAGING
TYPE 2 message in Step 4.
START Not checked

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
448
After step 2 the UE shall respond to the paging message by transmitting RRC STATUS on the DCCH, stating the
protocol error as " Information element value not comprehended ".
After step 4 the UE shall respond to the paging message by transmitting an INITIAL DIRECT TRANSFER message on
the uplink DCCH.
8.1.1.8 Paging for Connection in connected mode (CELL_FACH)
When the UE receives a PAGING TYPE 2 message, it shall not affect the state of any other ongoing RRC procedures,
when not stated otherwise elsewhere.
The UE shall:
1>forward the IE "Paging cause" and the IE "Paging record type identifier" to upper layers.


The UE shall:
bearer RB3;
Reference
3GPP TS 25.331 clause 8.1.8.2, 8.1.11.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
449
To confirm that the UE responds to a PAGING TYPE 2 message, which includes a matching value for IE "Paging
Record Type Identifier".
Initial Condition
UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108. The UE has been registered in both CS and
PS domains.
Test Procedure
The SS transmits a PAGING TYPE 2 message. Then the UE shall respond by transmitting an upper layer message to
answer this page.
Expected sequence
UE SS
1 Void
2 PAGING TYPE 2 The SS transmits the message
includes a matched identifier.
3 INITIAL DIRECT TRANSFER The UE responds by sending an
upper layer message.

Use the same message type found in [9] (TS 34.108) Clause 9, with the following exception.
Paging cause Terminating Call supported by the UE
CN domain identity CS
Paging record type identifier Set to "TMSI (GSM-MAP)/P-TMSI" for UEs supporting
GSM-MAP core network type or "TMSI (DS-41)" for UEs

Only the message type IE for this message is checked.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
450
Message Type
CN domain identity CS domain
--- CHOICE Routing basis Local (P)TMSI

---- Routing parameter The TMSI/P-TMSI consists of 4 octets (32bits). This can
b31, with bit b0 being the least significant.
through b23 of the TMSI/ PTMSI.
contains bit b23 of the TMSI/ PTMSI.
START Not checked

Message Type
START Not checked

After step 2 the UE shall respond to the PAGING TYPE 2 message by transmitting an INITIAL DIRECT TRANSFER
message on the uplink DCCH.
8.1.1.9 Paging for Connection in idle mode (multiple paging records)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
451
If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:
1>if the IE "Used paging identity" is a CN identity:
2>compare the IE "UE identity" with all of its allocated CN UE identities:
2>if one match is found:
3>forward the IE "CN domain identity", the IE "UE identity" and the IE "Paging cause" to the upper layers.
1>otherwise:
:
Upon initiation of the initial direct transfer procedure when the UE is in idle mode, the UE shall:
1>set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers;
1>perform an RRC connection establishment procedure, according to subclause 8.1.3;
1>if the RRC connection establishment procedure was not successful:
2>indicate failure to establish the signalling connection to upper layers and end the procedure.
1>when the RRC connection establishment procedure is completed successfully:
Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall:
1>perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission";
1>calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and
1>include the calculated START value for that CN domain in the IE "START".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
452
The UE shall:
bearer RB3;
Reference
3GPP TS 25.331 clause 8.1.2 and 8.1.8, 3GPP TS 25.211 clause 5.3.3.10 (FDD), 3GPP TS25.221 (TDD), 3GPP TS
25.304 clause 8.
1) For the CS domain
contains multiple paging records and includes IE "UE identity"(in IE "Paging Record") set to the IMSI of the
UE, and responds with a correct INITIAL DIRECT TRANSFER message.
2) For the PS domain
contains multiple paging records and includes IE "UE identity"(in IE "Paging Record") set to the P-TMSI
allocated by SS at initial attach and responds with a correct INITIAL DIRECT TRANSFER message.
Initial Condition
System Simulator: 1 cell. PICH is configured with Number of PI per frame set to 36.
UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity (set to IMSI in
the CS domain), depending on the CN domain(s) supported by the UE.
Test Procedure
UE. The SS also transmits SYSTEM INFORMATION BLOCK TYPE 5 messages. The SS transmits a PAGING TYPE
1 message, which includes an unmatched CN UE identity for idle mode, and an unmatched UTRAN UE identity for
connected mode. The UE shall not change its state. The SS transmits a PAGING TYPE 1 message, which includes two
unmatched identities and a matched CN UE identity for the UE in the idle state. During transmission of PAGING TYPE
1 messages, SS selects the correct paging indicator on the PICH in order to allow the UE to respond to paging. Then the
UE transmits an RRC CONNECTION REQUEST to the SS, the SS transmits an RRC CONNECTION SETUP to the
UE. When the UE receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION
SETUP COMPLETE message and an INITIAL DIRECT TRANSFER message on the uplink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
453
Expected sequence
UE SS
BLOCK TYPE 1
See specific message contents.
TYPE 5
which includes only unmatched
identities, and the UE does not
change its state.
which includes a matched identity.
6 RRC CONNECTION SETUP SS assigns DPCH resources to
allow UE to establish an RRC
connection.
COMPLETE


SYSTEM INFORMATION BLOCK TYPE 1 (Step 1) for UEs supporting GSM-MAP core networks
Use the default message type found in TS 34.108, except for the following.
CN domain system information

SYSTEM INFORMATION TYPE 13 (Step 1) for UEs supporting ANSI-41 core networks
PICH Info
- Number of PI per frame 36

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
454
Message Type
Paging record list
- Paging record 1
card.
- Paging record 2
- U-RNTI
- SRNC Identity Set to an arbitrary SRNC identity.
- S-RNTI Set to an arbitrary 20-bit string.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
455
For speech in CS:
Message Type
Paging record list
- Paging record 1
card.
- Paging record 2
- U-RNTI
- Paging record 3
- Paging cause Terminating Conversational Call
- CHOICE UE identity
- IMSI (GSM-MAP) Set to the same octet string as in the IMSI stored in the
USIM card

For packet in PS:
Message Type
Paging record list
- Paging record 1
card.
- Paging record 2
- U-RNTI
- Paging record 3
- Paging cause Terminating Interactive Call
- CHOICE UE identity
- P-TMSI Use P-TMSI allocated by SS at initial attach.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
456
Message type
registered P-TMSI depending upon CN domain
concerned.
on step 3.

Message Type
-- CHOICE CN type GSM-MAP
--- CHOICE Routing basis IMSI (response to IMSI paging) in CS domain)
P-TMSI (response to P-TMSI paging in PS Domain)
---- Routing parameter If the IE "CN domain identity" is equal to "CS domain", bit
string (10) consisting of DecimalToBinary [(IMSI div 10)
mod 1000]. The first/ leftmost bit of the bit string contains
the most significant bit of the result.
The TMSI/ PTMSI consists of 4 octets (32bits). This can
b31, with bit b0 being the least significant. The "Routing
parameter" is set to bits b14 through b23 of the TMSI/
PTMSI. The first/ leftmost/ most significant bit of the bit
string contains bit b23 of the TMSI/ PTMSI.
START Not checked

Message Type
START Not checked

After step 4 the UE shall transmit an RRC CONNECTION REQUEST message on the uplink CCCH.
After step 6 the UE shall have an RRC connection based on dedicated physical channel resources and transmit an RRC
CONNECTION SETUP COMPLETE message and an INITIAL DIRECT TRANSFER message on the uplink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
457
8.1.1.10 Paging for Connection in connected mode (URA_PCH, multiple paging
records)
:
the UE:
the upper layers.
2>otherwise:
1>otherwise:
the UE shall:
Reference
3GPP TS 25.331 clause 8.1.2, 8.3.1.7.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
458
To confirm that the UE enters the CELL_FACH state after it receives a PAGING TYPE 1 message in which the IE
"Used paging identity" is set to "UTRAN identity", and the UE takes the U-RNTI value assigned to it in the IE "U-
RNTI".
Initial Condition
System Simulator: 1 cell. PICH is configured with Number of PI per frame set to 72.
UE: URA_PCH state (state 6-13) as specified in clause 7.4 of TS 34.108, with a valid U-RNTI assigned by the SS.
Test Procedure
The SS transmits SYSTEM INFORMATION BLOCK TYPE 6 messages with a modified PCH configuration. The SS
then transmits a PAGING TYPE 1 message, which includes a matched IMSI, but the UE does not respond since it is in
connected mode. The SS transmits a PAGING TYPE 1 message, which includes a matched U-RNTI but in a paging
occasion not accrding to the DRX cycle of the UE. The UE does not reply. The SS transmits a PAGING TYPE 1
message, which includes a matched U-RNTI in a correct paging occasion. Then the UE listens to it and enters the
CELL_FACH state to transmit a CELL UPDATE message using uplink CCCH in respond to the paging. The SS sends
the UE back to URA_PCH state using CELL UPDATE CONFIRM and also modifies the UTRAN DRX cycle length
for the UE. The SS then transmits a PAGING TYPE 1 message using the new paging occasions. The UE replies to this
page.
Expected sequence
UE SS
TYPE 6
See specific message contents
includes a matched CN UE
identity, but the UE does not
respond.
includes a matched UTRAN UE
identity but in a paging occasion
not according to the DRX cycle of
the UE.
identity in the correct paging
occasion.
state.
CONFIRM
After transmitting this message, the
UE returns to URA_PCH state and
changes its UTRAN DRX cycle.
identity, using a paging occasion
which is included in the new DRX
cycle, but not in the old DRX cycle.
state.
CONFIRM

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
459
PICH Info
- Number of PI per frame 72

Message Type
Paging record list
- Paging record 1
- IMSI Set to the same octet string as in the IMSI stored in the
USIM card.
- Paging record 2
- U-RNTI

PAGING TYPE 1 (Steps 3, 4 and 8)
Message Type
Paging record list
- Paging record 1
card.
- Paging record 2
- U-RNTI
- Paging record 3
- U-RNTI

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
460
exceptions.
New C-RNTI '1010 1010 1010 1010'
RRC State Indicator URA_PCH
UTRAN DRX Cycle length coefficient 4

exceptions.
New C-RNTI '1010 1010 1010 1010'

After steps 2 and 3 the UE shall not respond to the paging.
After steps 4 and 8 the UE shall enter the CELL FACH state, and transmit CELL UPDATE message to initiate the cell
updating procedure with the cell update cause set to "paging response".
After steps 6 and 10 the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message.
8.1.2 RRC Connection Establishment
8.1.2.1 RRC Connection Establishment in CELL_DCH state: Success

The UE shall initiate the procedure when upper layers in the UE requests the establishment of a signalling connection
and the UE is in idle mode (no RRC connection exists).
Upon initiation of the procedure, the UE shall:

1>set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;
1>set CFN in relation to SFN of current cell according to TS 25.331 subclause 8.5.15;
1>perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13,
and apply the given Access Service Class when accessing the RACH;
1>submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;
1>set counter V300 to 1; and
1>start timer T300 when the MAC layer indicates success or failure to transmit the message;
1>select a Secondary CCPCH according to TS 25.304;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
461
1>start receiving all FACH transport channels mapped on the selected Secondary CCPCH.
.
The UE shall, in the transmitted RRC CONNECTION REQUEST message:
1>set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;
1>set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

The UE shall not include the IE "UE Specific Behaviour Information 1 idle".
.
The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP message
with the value of the variable INITIAL_UE_IDENTITY.
If the values are different, the UE shall:
1>ignore the rest of the message.
If the values are identical, the UE shall:
1>stop timer T300, and act upon all received information elements as specified in TS 25.331 subclause 8.6, unless
specified otherwise in the following:
2>if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of
this procedure:

1>if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this
procedure:
2>perform the physical layer synchronization procedure A as specified in TS 25.214;
2>enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;
1>submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink DCCH after
successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:
2>set the IE "RRC transaction identifier" to:
3>the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the
table "Accepted transactions" in the variable TRANSACTIONS; and
3>clear that entry.

2>retrieve its UTRA UE radio access capability information elements from variable
UE_CAPABILITY_REQUESTED; and then
2>include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this
IE is included in variable UE_CAPABILITY_REQUESTED;
2>retrieve its inter-RAT-specific UE radio access capability information elements from variable
2>include this in IE "UE system specific capability".
When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the
UE shall:
1>consider the procedure to be successful;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
462
And the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.3.2, 8.1.3.3 and 8.1.3.6
1. To confirm that the UE leaves the Idle Mode and correctly establishes signalling radio bearers on the DCCH.
2. To confirm that the UE indicates the requested UE radio access capabilities and UE system specific capabilities
(may be used by UTRAN e.g. to configure inter RAT- measurements).
3. To confirm that the UE does not include the IE "UE Specific Behaviour Information 1 idle" in the RRC
CONNECTION REQUEST message.
Initial Condition
UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
supported by the UE.
Test Procedure
The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make
an outgoing call. After SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by the
UE. SS then transmits an RRC CONNECTION SETUP message containing an IE "Initial UE Identity" that does not
match the IE "Initial UE Identity" in the most recent RRC CONNECTION REQUEST message sent by the UE. UE
receives the RRC CONNECTION SETUP message before timer T300 expires but discards it due to a IE "Initial UE
Identity" mismatch. UE shall wait for timer T300 to time out before re-transmitting a RRC CONNECTION REQUEST
message to the SS. SS again assigns the necessary radio resources and U-RNTI. SS then transmits a RRC
CONNECTION SETUP message containing an IE "Initial UE Identity" that matches the IE "Initial UE Identity" in the
most recent RRC CONNECTION REQUEST sent by the UE. SS then waits for the UE to transmit an RRC
CONNECTION SETUP COMPLETE message on the DCCH. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
463
Expected sequence
UE SS
1 RRC CONNECTION REQUEST By outgoing call operation. See
specific message contents.
2 RRC CONNECTION SETUP This message is not addressed to
the UE. See specific message
contents.
3 RRC CONNECTION REQUEST UE shall re-transmit the request
message again after a time out of
T300 from step 1.
3a SS checks IE "UE Specific
Behaviour Information 1 idle" is
not included in received RRC
CONNECTION REQUEST
message.
4 RRC CONNECTION SETUP See specific message contents.
5 The UE configures the layer 2 and
layer 1.
COMPLETE
7 CALL C.3 If the test result of C.3 indicates
that UE is in CELL_DCH state, the
test passes, otherwise it fails.

System Information Block type 11 (FDD)
Use the default system information block with the same type specified in clause 9 of TS 34.108, with the following
exceptions:
- Intra-frequency reporting quantity for RACH Reporting
- SFN-SFN observed time difference reporting
indicator
No report
- CHOICE mode
- FDD
- Reporting quantity CPICH Ec/N0
- Maximum number of reported cells on RACH current cell

System Information Block type 11 (TDD)
Use the default system information block with the same type specified in clause 9 of TS 34.108, with the following
exceptions:
indicator
No report
- CHOICE mode TDD
- Reporting quantity list
- Reporting quantity P-CCPCH RSCP

RRC CONNECTION REQUEST (Step 1) (FDD)
Use the default message with the same message type specified in clause 9 of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
464
UE Specific Behaviour Information 1 idle Check if this IE is absent.
Measured results on RACH Check to see if set in accordance with the IE "Intra-
frequency reporting quantity for RACH Reporting"
included in SYSTEM INFORMATION BLOCK Type 11
- Measurement result for current cell
- CHOICE mode
- FDD
- CHOICE measurement quantity
- CPICH Ec/N0 The actual reported value is not checked

RRC CONNECTION REQUEST (Step 1) (TDD)
- CHOICE mode TDD
- P-CCPCH RSCP The actual reported value is not checked

RRC CONNECTION SETUP (Step 2)
Use the same message type found in clause 9 of TS 34.108, with the following exception.
Initial UE Identity Set to unmatched identity (incorrect IMSI)

Use the default message with the same message type and covering the scenario used in this test (Transition to
CELL_DCH) specified in clause 9 of TS 34.108.
RRC CONNECTION SETUP COMPLETE (Step 6)
Use the default message with the same message type specified in clause 9 of TS 34.108 with the following exception.
UE Radio Access Capability Checked to see if compatible with the stated capability
in PIXIT/PICS statements.
UE radio access capability extension Checked to see if compatible with the stated capability
UE system specific Capability Checked to see if compatible with the stated capability

After step 2 the UE shall re-transmit the RRC CONNECTION REQUEST message again in order to continue the RRC
connection establishment procedure.
After step 3 the SS shall check IE "UE Specific Behaviour Information 1 idle" isn't included in received RRC
CONNECTION REQUEST message.
After step 6 the UE shall establish an RRC connection and continue the procedure of the outgoing call on the DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
465
8.1.2.2 RRC Connection Establishment: Success after T300 timeout
If the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity"
equal to the value of the variable INITIAL_UE_IDENTITY; and
if expiry of timer T300 occurs:
the UE shall:
1>check the value of V300; and
2>if V300 is equal to or smaller than N300:
3>set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;
3>submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink
CCCH;
3>increment counter V300;
3>restart timer T300 when the MAC layer indicates success or failure to transmit the message.
2>if V300 is greater than N300:

Reference
3GPP TS 25.331 clause 8.1.3.5.
To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 after the expiry of timer
T300 when the SS transmits no response for an RRC CONNECTION REQUEST message.
Initial Condition
System Simulator: 1 cell. SCCPCH configuration as specified in 6.1.1 of TS 34.108.
NOTE: This test requires that N300 is bigger than 0, which is the case (see default contents of SIB 1, specified in
TS 34.108). Expiry of timer T300 is verified only for N300 values exceeding 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
466
Test Procedure
Before the test starts, SYSTEM INFORMATION BLOCK TYPE 1, SYSTEM INFORMATION BLOCK TYPE 5 and
SYSTEM INFORMATION BLOCK TYPE 7 message are modified and this modification is notified to the UE. An
internal counter K in SS is initialized to a value =0. Following this, the UE shall transmit an RRC CONNECTION
REQUEST message to the SS on the uplink CCCH by use of selected PRACH from the available PRACH No.1 and
PRACH No.2, after the operator attempts to make an outgoing call. SS ignores this message, increments K every time
such a message is received and waits for T300 timer to expire. This cycle is repeated until K reaches N300. When K is
equal to N300, the SS transmits an RRC CONNECTION SETUP message containing an IE RRC state indicator set to
CELL_PCH as specified in step 6 to the UE. The UE shall send another RRC CONNECTION REQUEST message on
the uplink CCCH. SS replies with a valid RRC CONNECTION SETUP message. The UE shall then acknowledge the
establishment of RRC connection by sending the RRC CONNECTION SETUP COMPLETE message on uplink
DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
467
Expected sequence
UE SS
1 PAGING TYPE 1 SS transmits the paging
message which comprises
IE "BCCH Modification
Information", with the "Value
Tag" different from the "MIB
Value Tag" of the current
Master Information Block.
SS continuously broadcast
the same MASTER
INFORMATION BLOCK and
various types of SYSTEM
INFORMATION BLOCK on
BCCH. See specific
message contents.
1a SS waits 5s (to ensure that
the UE waits for the new
value tag before re-reading
system information)
1b MASTER INFORMATION BLOCK

SS starts to transmit the MIB
with the "MIB Value Tag" IE
different from the original
setting.
At the same time, SS starts
to transmit the affected SIB
TYPE 1 , SIB TYPE 5 and
SIB 7messages. See
1c SS waits 5s (to ensure that
the UE has time to read the
new system information)
2 SS initializes counter K to 0.
Operator is asked to make
an outgoing call and SS
starts to wait for RRC
CONNECTION REQUEST
on uplink CCCH.
3 RRC CONNECTION REQUEST See the clause 9 in TS
34.108 on default message
content
4 SS increments K.
5 SS checks to see if K is
equal to N300. If so, goes to
step 6. Else, continues to
execute step 3.
6 RRC CONNECTION SETUP IE RRC state indicator is
set to CELL_PCH.
7 RRC CONNECTION REQUEST See specific message
contents.
8 RRC CONNECTION SETUP This is a legal message. See
the clause 9 in TS 34.108 on
default message content for
RRC.
9 The UE configures the layer
1 and layer 2.
10 RRC CONNECTION SETUP COMPLETE See clause 9 in TS 34.108
on default message content

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
468
Message Type
Paging record list Not present

SYSTEM INFORMATION TYPE 1 (Step 1b)
Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS
34.108, with the following exceptions:
- UE Timers and constants in idle mode
-T300 2000 milliseconds
-N300 3
-T312 10 seconds
- N312 1

SYSTEM INFORMATION TYPE 5 (Step 1b) - (FDD)
Use the default parameter values for the system information block with the same type specified in clause 6.1.1 of TS
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
469
- SIB6 indicator FALSE
- PICH Power offset -5 dB
- CHOICE Mode FDD
- AICH Power offset 5 dB
- Primary CCPCH info Not present
- PRACH system information list
- PRACH system information 2PRACHs
- PRACH info (PRACH No.1)
- CHOICE mode FDD
- Available SF 64
- Preamble scrambling code number 0
- Puncturing Limit 1.00
- Available Sub Channel number '1111 1111 1111'B
- Transport Channel Identity 15
- RACH TFS
- CHOICE Transport channel type Common transport channels
- Dynamic Transport format information
- RLC size 168
- Number of TB and TTI List
- Number of Transport blocks 1
- CHOICE Mode FDD
- CHOICE Logical Channel List Configured
- RLC size 360
- CHOICE Mode FDD
- Semi-static Transport Format information
- Transmission time interval 20 ms
- Type of channel coding Convolutional
- Coding Rate 1/2
- Rate matching attribute 150
- CRC size 16
- RACH TFCS
- Normal
- TFCI Field 1 information
- CHOICE TFCS representation Complete reconfiguration
- TFCS addition information
- CHOICE CTFC Size 2 bit
- CTFC information 0
- Power offset information
- CHOICE Gain Factors Computed Gain Factor
- Reference TFC ID 0
- CHOICE Mode FDD
- Power offset Pp-m 0dB
- CHOICE Gain Factors Signalled Gain Factor
- Gain factor c 11
- Gain factor d 15
- CHOICE Mode FDD
- PRACH partitioning
- ASC Setting Not Present
- ASC Setting
- CHOICE mode FDD
- Available signature Start Index 0 (ASC#1)
- Available signature End Index 7 (ASC#1)
- Assigned Sub-Channel Number '1111'B
significant bit of the Assigned Sub-Channel Number.
- ASC Setting
- CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
470
- ASC Setting
- CHOICE mode FDD
- ASC Setting
- CHOICE mode FDD
- Persistence scaling factor
- Persistence scaling factor 0.9 (for ASC#2)
- AC-to-ASC mapping table
- AC-to-ASC mapping 6 (AC0-9)
- AC-to-ASC mapping 5 (AC10)
CHOICE mode FDD
- Primary CPICH DL TX power 31
- Constant value 10
- PRACH power offset
- Power Ramp Step 3dB
- Preamble Retrans Max 4
- RACH transmission parameters
- Mmax 2
- NB01min 3 slot
- NB01max 10 slot
- AICH info
- Channelisation code 3
- STTD indicator FALSE
- AICH transmission timing 0
- CHOICE mode FDD
- Available SF 64
- Preamble scrambling code number 1
- Puncturing Limit 1.00
- Available Sub Channel number '1111 1111 1111'B
- RACH TFS
- RLC size 168
- CHOICE Mode FDD
- RLC size 360
- CHOICE Mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
471
- Coding Rate 1/2
- CRC size 16
- RACH TFCS
- Normal
- TFCS addition information
- CHOICE CTFC Size 2 bit
- CHOICE Gain Factors Computed Gain Factor
- CHOICE Mode FDD
- Power offset Pp-m 0 dB
- CHOICE Gain Factors Signalled Gain Factor
- Gain factor c 11
- Gain factor d 15
- CHOICE Mode FDD
- ASC Setting
- CHOICE mode FDD
- ASC Setting
- CHOICE mode FDD
- ASC Setting
- CHOICE mode FDD
- ASC Setting
- CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
472
CHOICE mode FDD
- Primary CPICH DL TX power 31
- Constant value 10
- PRACH power offset
- Power Ramp Step 3dB
- Preamble Retrans Max 4
- RACH transmission parameters
- Mmax 2
- NB01min 3 slot
- NB01max 10 slot
- AICH info
- Channelisation code 4
- STTD indicator FALSE
- AICH transmission timing 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
473
SYSTEM INFORMATION TYPE 5 (Step 1b) 3.84 Mcps TDD
- CHOICE mode TDD
- CHOICE TDD option 3.84 Mcps TDD
- Timeslot Number 14
- PRACH Channelisation Code
- CHOICE SF 8
- Channelisation Code List
- Channelisation Code 8/1
- PRACH Midamble Direct
-PNBSCH allocation Not Present
- RACH TFS
- RLC size 168
- Transport Time Interval Not Present
- Number of Transport Blocks 1
- CHOICE Logical Channel List ALL
- Coding Rate 1/2
- CRC size 16
- RACH TFCS Not Present
- ASC Setting
- CHOICE mode TDD
- Available SYNC_UL codes indices '11110000'B (ASC#0)
- CHOICE subchannel size Size1
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
474
- ASC Setting
- CHOICE mode TDD
- CHOICE mode TDD
- CHOICE mode TDD
- Timeslot Number 14
- CHOICE SF 8
- Channelisation Code 8/5 where i denotes an unassigned code
- PRACH Midamble Direct
-PNBSCH allocation Not Present
- RACH TFS
- RLC size 168
- Coding Rate 1/2
- CRC size 16
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
475
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
476
SYSTEM INFORMATION TYPE 5 (Step 1b) 1.28 Mcps TDD
- CHOICE mode TDD
- SYNC_UL info
- SYNC_UL codes bitmap '11110000'B
- PRXUpPCHdes 10
- Power Ramping Step 3
- Max SYNC_UL Transmissions 8
- Mmax 32
- PRACH Definition
- Timeslot Number
- Timeslot number 1
- Midamble shift and burst type
- Midamble Allocation Mode Default
- Midamble Configuration 8
- Midamble Shift Not Present
- FPACH info
- Timeslot number 6
- Channelisation code 16/16
- Midamble Shift and burst type
- WT 4
- PNBSCH allocation Not Present
- RACH TFS
- RLC size 168
- Coding Rate
- CRC size 16
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
477
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- CHOICE mode TDD
- CHOICE mode TDD
- SYNC_UL info
- SYNC_UL codes bitmap '11110000'B
- PRXUpPCHdes 10
- Power Ramping Step 1
- Max SYNC_UL Transmissions 8
- Mmax 32
- PRACH Definition
- Timeslot Number
- Timeslot number 1
- Midamble shift and burst type
- FPACH info
- Timeslot number An available down-link timeslot
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
478
- Channelisation code 16/15
- Midamble Shift and burst type
- WT 4
- PNBSCH allocation Not Present
- RACH TFS
- RLC size 168
- Coding Rate
- CRC size 16
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
- ASC Setting
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
479
- CHOICE mode TDD

Contents of System Information Block type 7 (FDD) (Step 1b)
- PRACHs listed in system information block
type5

- Dynamic persistence level (2,2)
- PRACHs listed in system information block
type6
Not present
SS sends a message containing a critical extension not defined for the protocol release supported by the UE, as
indicated in the IE "Access stratum release indicator":
RRC state indicator CELL_PCH

Protocol Error Indicator Check to see if set to TRUE

After step 2 the UE shall select either PRACH No.1 or PRACH No.2 and transmit an RRC CONNECTION REQUEST
message.
After step 6 the UE shall re-send another RRC CONNECTION REQUEST message.
After step 9 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message and establish an RRC
connection on the DCCH logical channel.
8.1.2.3 RRC Connection Establishment: Failure (V300 is greater than N300)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
480
1>set the IE "Initial UE identity" in the variable INITIAL_UE_IDENTITY according to TS 25.331 subclause 8.5.1;

1>if the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE
identity" equal to the value of the variable INITIAL_UE_IDENTITY; and
1>if cell re-selection or expiry of timer T300 occurs:
the UE shall:


CCCH;

3>enter idle mode.
3>consider the procedure to be unsuccessful;
3>Other actions the UE shall perform when entering idle mode from connected mode are specified in TS
25.331 subclause 8.5.2;
Reference
3GPP TS 25.331 clause 8.1.3.
To confirm that the UE stops retrying to establish the RRC connection if V300 is greater than N300 and goes back to
idle mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
481
Initial Condition


Test Procedure
Before the test starts, SS initializes an internal counter K to 0. The UE transmits an RRC CONNECTION REQUEST
message to the SS on the uplink CCCH by an outgoing call operation. SS shall not respond to any RRC CONNECTION
REQUEST message, instead the counter K is increased by 1 every time such a message is received. To arrive at the
verdict, the SS checks that a total of (N300+1) such messages are received. SS calls for generic procedure C.1 to check
that UE is in Idle Mode state.
Expected sequence
UE SS
1 SS initializes counter K to 0 and
then prompts the operator to make
an outgoing call.
3 SS increments K by 1.
4 If K is greater than N300, goes to
step 5 else proceed to step 2.
5 SS monitor the uplink CCCH for a
time period enough for UE to goes
back to idle state. SS waits for 5s.
6 CALL C.1 If the test result of C.1 indicates that
UE is in Idle Mode state, the test
passes, otherwise it fails.

None
After step 5, counter K shall be equal to (N300+1) and there shall be no uplink transmission in the monitoring period
specified in step 5.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
482
8.1.2.4 RRC Connection Establishment: Reject ("wait time" is not equal to 0)
When the UE receives an RRC CONNECTION REJ ECT message on the downlink CCCH, it shall compare the value of
the IE "Initial UE identity" in the received RRC CONNECTION REJ ECT message with the value of the variable
INITIAL_UE_IDENTITY:
If the values are different, the UE shall ignore the rest of the message;
If the values are identical, the UE shall stop timer T300 and:
1>if the IE "wait time" <>'0'; and
1>if the IE "frequency info" is present and:
3>initiate cell selection on the designated UTRA carrier;
3>after having selected and camped on a cell:
4>set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause
8.1.3.3;
4>perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331
subclause 8.5.13, and apply the given Access Service Class when accessing the RACH;
4>transmit an RRC CONNECTION REQUEST message on the uplink CCCH;
4>reset counter V300;
4>start timer T300 when the MAC layer indicates success or failure in transmitting the message;
4>disable cell reselection to original carrier until the time stated in the IE "wait time" has elapsed;
3>if a cell selection on the designated carrier fails:
4>wait for the time stated in the IE "wait time";
4>set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause
8.1.3.3;
4>then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on
the uplink CCCH of the original serving cell;
4>restart timer T300 when the MAC layer indicates success or failure to transmit the message;
3>enter idle mode;
3>perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected
mode;
3>consider the RRC establishment procedure to be unsuccessful;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
483

1>If the IEs "frequency info" not present:
3>wait at least the time stated in the IE "wait time";
3>perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause
8.5.13, and apply the given Access Service Class when accessing the RACH;
3>submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the
uplink CCCH;
3>enter idle mode;
mode;
Reference
3GPP TS 25.331 clause 8.1.3.9.
To confirm that the UE retries to establish the RRC connection after the "wait time" elapses, if the UE receives an RRC
CONNECTION REJ ECT message which includes the IE "wait time" not set to 0.
To confirm that the UE performs a cell reselection when receiving an RRC CONNECTION REJ ECT message,
containing relevant frequency information of the target cell to be re-selected.
Initial Condition
System Simulator: 2 cells both cell 1 and cell 4 are active and suitable for camping, but cell 1 is transmitted using a
larger power. Cell 1 and cell 4 are being transmitted from different 2 UARFCNs. The transmission power of cell 4 is 15
dB smaller than cell 1.
Table 8.1.2.4
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -75

P-CCPCH
(TDD)
dBm
-60 -75

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
484
Test Procedure
The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by an outgoing call
operation in cell 1. SS rejects the first request by transmitting an RRC CONNECTION REJ ECT message which
indicates a non-zero wait time. In this message, frequency information for cell 4 is available. SS then waits for RRC
CONNECTION REQUEST message on the uplink CCCH of cell 4. SS will also monitor the uplink of cell 1
simultaneously to ensure that all transmission activities from cell 1 have ceased. When the UE has successfully camp
onto cell 4, it shall send an RRC CONNECTION REQUEST with the same establishment cause as its previous attempt
in cell 1. SS responds with an RRC CONNECTION REJ ECT message, indicating a non-zero "wait time" and omitting
the IE "Redirection Info". The UE shall observe the wait time period indicated. After the wait time has elapsed, the UE
shall re-transmit RRC CONNECTION REQUEST again. Finally, SS transmits an RRC CONNECTION SETUP
message to establish an RRC connection with the UE, and the UE replies with an RRC CONNECTION SETUP
COMPLETE message and enters CELL_DCH state.
Note: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Expected sequence
UE SS
1 RRC CONNECTION REQUEST SS prompts the operator to make
an outgoing call in cell 1.
2 RRC CONNECTION REJ ECT This message shall includes the IE
"wait time" set to 15 seconds and
IE "frequency info" set to the
UARFCN of cell 4.
Note: this wait time would apply
after failure of the inter frequency
cell reselection, which is not
verified in this test case
3 SS waits for a period of time
sufficient for UE to reselect to cell
4. At the same time, it monitors the
uplink of cell 1 to make sure that all
transmissions have ceased.
4 RRC CONNECTION REQUEST UE shall attempt to re-start an
RRC connection establishment
procedure in cell 4. The
establishment cause shall remain
unchanged.
5 RRC CONNECTION REJ ECT This message shall include the IE
"wait time" set to 15 seconds, but
with IE "Redirection Info" absent.
6 RRC CONNECTION REQUEST SS waits until the duration
specified in IE "wait time" has
elapsed and then listens to the
uplink CCCH for a second RRC
CONNECTION REQUEST
message.
7 RRC CONNECTION SETUP SS sends the message to UE to
setup an RRC connection with the
UE.
8 The UE shall configure the layer 2
and layer 1 in order to access the
uplink and downlink DCCH
assigned.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
485
RRC CONNECTION REQUEST (Step 1, step 4 and step 6)
Initial UE Identity Same as the IMSI stored in the TEST USIM card, or the
registered TMSI or P-TMSI
Establishment Cause Must be "Originating Call"

RRC CONNECTION REJ ECT (Step 2) - FDD
Wait time 15 seconds
Redirection Info
- Frequency Info
- CHOICE mode FDD
- UARFCN uplink (Nu) Not present
- UARFCN downlink (Nd) Set to the UARFCN for uplink carrier of cell 4

RRC CONNECTION REJ ECT (Step 2) TDD
Redirection Info
Frequency Info
CHOICE Mode TDD
UARFCN (Nt) Set to a different UARFCN from the carrier of cell 1

RRC CONNECTION REJ ECT (Step 5)
Wait time

15 seconds

After step 3 the UE shall have successfully re-selected to cell 4. UE shall trigger the start of RRC connection
establishment by transmitting RRC CONNECTION REQUEST. The establishment cause shall be originating call.
After step 5 the UE shall observe the period specified in IE "wait time" of the RRC CONNECTION REJ ECT message
and not transmit an RRC CONNECTION REQUEST message in this period.
After step 7 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message to SS on uplink DCCH and
then establish an RRC connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
486
8.1.2.5 RRC Connection Establishment: Reject ("wait time" is not equal to 0 and
V300 is greater than N300)
If the values are identical, the UE shall stop timer T300 and:
1>if the IE "wait time" <>'0'; and
1>if the IE "frequency info" is present and:
3>initiate cell selection on the designated UTRA carrier;
3>after having selected and camped on a cell:
4>set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause
8.1.3.3;
4>transmit an RRC CONNECTION REQUEST message on the uplink CCCH;
4>reset counter V300;
4>start timer T300 when the MAC layer indicates success or failure in transmitting the message;
4>disable cell reselection to original carrier until the time stated in the IE "wait time" has elapsed;
3>if a cell selection on the designated carrier fails:
4>wait for the time stated in the IE "wait time";
4>set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause
8.1.3.3;
4>then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on
the uplink CCCH of the original serving cell;
3>enter idle mode;
mode;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
487

1>If the IEs "frequency info" not present:
3>wait at least the time stated in the IE "wait time";
uplink CCCH;
3>enter idle mode;
mode;
Reference
3GPP TS 25.331 clause 8.1.3.9.
To confirm that the UE retries to establish the RRC connection after the "wait time" elapses if the UE receives an RRC
CONNECTION REJ ECT message which specifies a non-zero IE "wait time".
To confirm that the UE stops retrying to establish the RRC connection if V300 is greater than N300 and goes back to
idle mode.
Initial Condition
supported by the UE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
488
Test Procedure
Before the test starts, SS initializes an internal counter K to 0. The UE transmits an RRC CONNECTION REQUEST
message to the SS on the uplink CCCH, triggered by an outgoing data call operation. SS rejects all requests by
transmitting an RRC CONNECTION REJ ECT message which indicates a non-zero wait time and the counter K is
increased by 1 every time such a message is received. To arrive at the verdict, the SS checks that a total of (N300+1)
such messages are received and the UE enters idle state. SS calls for generic procedure C.1 to check that UE is in Idle
Mode state.
Expected sequence
UE SS
1 SS initializes counter K to 0 and
then prompts the operator to make
an outgoing data call.
2 RRC CONNECTION REQUEST Shall be sent on CCCH and contain
the correct establishment cause.
3 RRC CONNECTION REJ ECT This message includes the IE "wait
time" set to 15 seconds.
5 If K is greater than N300, goes to
step 6. Else SS waits for 15 sec
before proceeding to step 2.
6 SS monitor the uplink CCCH for a
time period enough for UE to goes
back to idle state. SS waits for 5s.
UE is in Idle Mode state, the test

Establishment Cause Must be "Originating Call"

Use the same message type found in TS 34.108 clause 9, with the following exception.

After step 6, counter K shall be equals to (N300+1) and there shall be no uplink transmission in the monitoring period
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
489
8.1.2.6 RRC Connection Establishment: Reject ("wait time" is set to 0)
If the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity"
equal to the value of the variable INITIAL_UE_IDENTITY; and
if expiry of timer T300 occurs:
the UE shall:
CCCH;

Reference
3GPP TS 25.331 clause 8.1.3.9.
To confirm that the UE goes back to idle mode, if the SS transmits an RRC CONNECTION REJ ECT message which
includes IE "wait time" set to 0. To confirm that the UE ignores an RRC CONNECT REJ ECT message not addressed to
it. To confirm that the UE is capable of handling an erroneous RRC CONNECTION REJ ECT message correctly.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
490
Test Procedure
The UE transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by making an outgoing
call. After the SS receives this message, it transmits an RRC CONNECTION REJ ECT message which is not addressed
to the UE. The UE shall disregard this message and proceed to re-transmit RRC CONNECTION REQUEST message
upon T300 timer expiry. SS answers the second RRC CONNECTION REQUEST message by transmitting an invalid
RRC CONNECTION REJ ECT message. The UE shall continue to send the third RRC CONNECTION REQUEST
message upon expiry of T300 timer. Next, the SS sends a legal RRC CONNECTION REJ ECT message which includes
IE "wait time" which is set to '0'. To confirm that the UE goes back to idle mode immediately after receiving the reject
message, SS shall monitor the uplink CCCH for the next 60 seconds and verify that there is no further transmission in
the uplink direction.
Expected sequence
UE SS
1 RRC CONNECTION REQUEST Test operator is prompted to make
an out-going call,
2 RRC CONNECTION REJ ECT IE "Initial UE identity" contains an
identity different from any of the UE
identities available.
3 RRC CONNECTION REQUEST UE shall send this message after
T300 expires.
5 RRC CONNECTION REQUEST UE shall send this message after
T300 expires.
6 RRC CONNECTION REJ ECT IE "wait time" is set to 0.
7 The UE goes back to idle mode.

RRC CONNECTION REQUEST (Step 1, 3 and 5)
Message Type
Establishment Cause Checked to see if set to one of the supported originating
call types
Protocol Error Indicator Checked to see if set to "FALSE"
Measured Results on RACH Checked to see if it is absent

Use the same message type found inclause 9 of TS 34.108, with the following exception.
Initial UE Identity

Set to the same type as in RRC CONNECTION
REQUEST message (step 1) but with a different value.

All IEs Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
491
Initial UE Identity Same as the type and value defined in RRC
CONNECTION REQUEST message (step 5)
Reject Cause Congestion
Wait time 0 second

After step 2 the UE shall transmit an RRC CONNECTION REQUEST message on uplink CCCH upon expiry of T300
timer.
After step 4 the UE shall re-transmit an RRC CONNECTION REQUEST message on the uplink CCCH upon expiry of
T300 timer.
After step 6 the UE shall stop sending an RRC CONNECTION REQUEST message, go back to idle mode immediately
and not transmit in the uplink direction again.
8.1.2.7 RRC Connection Establishment in CELL_FACH state: Success

1>set the contents of the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;
1>perform the mapping of the Access Class to an Access Service Class as specified in TS 25.331 subclause 8.5.13,
and apply the given Access Service Class when accessing the RACH;
.

with the value of the variable INITIAL_UE_IDENTITY.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
492
1>stop timer T300, and act upon all received information elements as specified in TS 25.331 subclause 8.6, unless
specified otherwise in the following:
2>if the UE, according to TS 25.331 subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of
this procedure:
3>if the IE "Frequency info" is included:
4>select a suitable UTRA cell according to TS 25.304 on that frequency;
3>enter UTRA RRC connected mode;
3>select PRACH according to TS 25.331 subclause 8.5.17;
3>select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
3>ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX.
1>if the UE, according to subclause 8.6.3.3, will be in the CELL_DCH state at the conclusion of this procedure:
2>perform the physical layer synchronization procedure as specified in TS 25.214 (FDD) or TS 25.224 (TDD);
2>enter UTRA RRC connected mode, in a state according to TS 25.331 subclause 8.6.3.3;
successful state transition per TS 25.331 subclause 8.6.3.3, with the contents set as specified below:
2>set the IE "RRC transaction identifier" to:
3>the value of "RRC transaction identifier" in the entry for the RRC CONNECTION SETUP message in the
3>clear that entry.
.
2>include this in IE "UE radio access capability" and IE "UE radio access capability extension", provided this
IE is included in variable UE_CAPABILITY_REQUESTED;
When the RRC CONNECTION SETUP COMPLETE message has been submitted to lower layers for transmission the
UE shall:
1>if the UE has entered CELL_FACH state:
2>start timer T305 using its initial value if periodical update has been configured by T305 in the IE "UE Timers
and constants in connected mode" set to any other value than "infinity" in system information block type 1.
.
1>consider the procedure to be successful;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
493
Reference
3GPP TS 25.331 clause 8.1.3.2, 8.1.3.3 and 8.1.3.6.
1. To confirm that the UE is able to enter CELL_FACH state and setup signalling radio bearers using common
physical channels.
2. To confirm that the UE indicates the requested UE radio access capabilities (used by UTRAN to decide which
RAB to establish) and UE system specific capabilities (may be used by UTRAN to configure inter RAT-
measurements).
Initial Condition
Test Procedure
an outgoing call. After the SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by
the UE, and then transmits an RRC CONNECTION SETUP message to the UE within timer T300. SS then waits for
the UE to transmit an RRC CONNECTION SETUP COMPLETE message on the DCCH. SS calls for generic
procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 RRC CONNECTION REQUEST Test operator is requested to make
an outgoing call. The UE shall
transmit this message, indicating
the correct establishment cause.
2 RRC CONNECTION SETUP See specific message contents.
3 The UE shall configure the layer 2
and layer 1.
COMPLETE
UE shall send this message on the
DCCH, carried by the assigned
PRACH resources. See specific
message contents. FDD or TDD
that UE is in CELL_FACH state,
the test passes, otherwise it fails.

RRC CONNECTION REQUEST
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
494
Establishment Cause Originating Conversational Call or Originating
Interactive Call or Originating Background Call or
Originating Streaming Call

RRC CONNECTION SETUP (FDD)
For this message, the contents of the message to be used are basically identical to the message sub-type entitled "RRC
CONNECTION SETUP message (Transition to CELL_FACH)" found in TS 34.108, clause 9 with the following
exception:
UE radio access FDD capability update requirement TRUE
UE radio access TDD capability update requirement FALSE
System specific capability update requirement list gsm

RRC CONNECTION SETUP (TDD)
CONNECTION SETUP message (Transition to CELL_FACH)" found in TS 34.108, clause 9 with the following
exception:
UE radio access FDD capability update requirement FALSE
UE radio access TDD capability update requirement TRUE
System specific capability update requirement list gsm

RRC CONNECTION SETUP COMPLETE
UE Radio Access Capability Checked to see if compatible with the stated capability
UE radio access capability extension Checked to see if compatible with the stated capability
UE system specific Capability Checked to see if compatible with the stated capability

After step 3 the UE shall establish the RRC connection, and transmit RRC CONNECTION SETUP COMPLETE
message on the DCCH using PRACH physical resource specified in system information block messages.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
495
8.1.2.8 Void
8.1.2.9 RRC Connection Establishment: Success after Physical channel failure and
Failure after Invalid configuration
If the UE failed to establish, per TS 25.331 subclause 8.5.4, the physical channel(s) indicated in the RRC
CONNECTION SETUP message.
After having received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to
the value of the variable INITIAL_UE_IDENTITY.
Before the RRC CONNECTION SETUP COMPLETE message is delivered to lower layers for transmission,
the UE shall:
1>clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable
TRANSACTIONS;
1>check the value of V300, and:
uplink CCCH;
3>increment counter V300; and
3>restart timer T300 when the MAC layer indicates success or failure in transmitting the message.

If the UE receives an RRC CONNECTION SETUP message which contains an IE "Initial UE identity" with a value
which is identical to the value of the variable INITIAL_UE_IDENTITY; and
the variable INVALID_CONFIGURATION becomes set to TRUE due to the received RRC CONNECTION SETUP
message:
the UE shall:
1>clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable
TRANSACTIONS and proceed as below;
2>set the variable PROTOCOL_ERROR_INDICATOR to TRUE;
8.5.13; and
2>apply the given Access Service Class when accessing the RACH;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
496
2>submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink
CCCH;
2>increment counter V300; and
2>restart timer T300 when the MAC layer indicates success or failure in transmitting the message.

Reference
3GPP TS 25.331 clause 8.1.3.
1. To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 when a physical
channel failure occurs because SS does not configure the physical channel that is specified in the transmitted
RRC CONNECTION SETUP message.
2. To confirm that the UE retries to establish the RRC connection until V300 is greater than N300 when the
transmitted RRC CONNECTION SETUP message causes invalid configuration in the UE.
Initial Condition
supported by the UE
Test Procedure
Before the test starts,SYSTEM INFORMATION BLOCK TYPE 1 is modified and this modification is notified to the
UE. An internal counter K in SS is initialised to a value =0. Following this, the UE shall transmit an RRC
CONNECTION REQUEST message to the SS on the uplink CCCH, after the operator attempts to make an outgoing
call. SS increments K every time such a message is received. Then, SS shall send a RRC CONNECTION SETUP
message that contains an invalid configuration. UE shall then send RRC CONNECTION REQUEST message to SS
again. This cycle is repeated until K reaches N300+1. When K is equal to N300+1, the SS again transmits an RRC
CONNECTION SETUP message including an invalid configuration. Upon receiving this message the UE shall not send
another RRC CONNECTION REQUEST message.
Next the SS re-initialises the internal counter K to value =0, after which the operator attempts to make another
outgoing call. Following this, the UE shall transmit an RRC CONNECTION REQUEST message to the SS on the
uplink CCCH. SS increments K every time such a message is received. SS transmits an RRC CONNECTION SETUP
message to make the UE configure the physical channel in order to communicate on the DCCH but SS does not
configure the physical channel. Then the UE detects the physical channel failure and transmits an RRC CONNECTION
REQUEST message. This cycle is repeated until K reaches N300+1. When K is equal to N300+1, the SS transmits the
RRC CONNECTION SETUP message and configures the physical channel. The UE shall detect "in-sync" from
physical layer and then acknowledge the establishment of RRC connection by sending the RRC CONNECTION
SETUP COMPLETE message on uplink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
497
Expected sequence
UE SS
0 PAGING TYPE 1 SS transmits the paging
message which comprises
IE "BCCH Modification
Information", with the "Value
Tag" different from the "MIB
Value Tag" of the current
Master Information Block.
Also the modification time is
set to 2048 radio frames
from the current SFN. SS
continuously broadcast the
same MASTER
INFORMATION BLOCK and
various types of SYSTEM
INFORMATION BLOCK on
BCCH. See specific
message contents.
0a MASTER INFORMATION BLOCK

SS starts to transmit the MIB
with the "MIB Value Tag" IE
different from the original
setting.
At the same time, SS starts
to transmit the affected SIB
TYPE 1 messages. See
1 SS initialises counter K to 0.
Operator is asked to make
an outgoing call and SS
starts to wait for RRC
CONNECTION REQUEST
on uplink CCCH.
2 RRC CONNECTION REQUEST See specific message
contents.
2a SS increments K by 1 for
every RRC CONNECTION
REQUEST message
received in step 2
2b RRC CONNECTION SETUP See specific message
contents.
3 SS checks to see if K is
equal to N300+1. If so, goes
to step 3a. Else, continues
to execute step 2.
3a SS waits to verify that the
UE does not send any
further RRC CONNECTION
REQUEST message
3b SS re-initialises counter K to
0. Operator is asked to
make another outgoing call
and SS starts to wait for
RRC CONNECTION
REQUEST on uplink CCCH.
3c RRC CONNECTION REQUEST See specific message
contents.
3d SS increments K by 1 for
every RRC CONNECTION
REQUEST message
received in step 3c
3e SS checks to see if K is
equal to N300+1. If so, goes
to step 6. Else, continues to
execute step 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
498
4 RRC CONNECTION SETUP Use the default message
with the same message sub-
type specified in clause 9 in
TS 34.108. SS does not
configure the physical
channel.
5 The next step is step 3c.
6 RRC CONNECTION SETUP Use the default message
TS 34.108. SS configures
the physical channel.
7 The UE configures the layer
1 and layer 2.
8 RRC CONNECTION SETUP COMPLETE Use the default message
TS 34.108.

SYSTEM INFORMATION TYPE 1 (Step 1a)
-N300 3
-T312 10 seconds
- N312 1

RRC CONNECTION REQUEST (Step 2 & step 3c, K=0)
The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:
Establishment Cause Originating Interactive Call or Originating Background
Call or Originating Streaming Call

RRC CONNECTION REQUEST (Step 2 & step 3c, K>0)
The same message sub-type found in clause 9 of TS 34.108 applies, with the following exceptions:
Protocol error indicator Not Checked

RRC CONNECTION SETUP (Step 2b)
Use the same message sub-type found in clause 9 of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
499
RRC State Indicator

CELL_DCH

Uplink DPCH info Not present

After step 3a the UE shall not send any further RRC CONNECTION REQUEST message.
After step 8 the UE shall transmit an RRC CONNECTION SETUP COMPLETE message and establish an RRC
connection.
8.1.2.10 RRC connection establishment in CELL_DCH on another frequency

1. The UE shall, in the transmitted RRC CONNECTION REQUEST message:
1>set the IE "Protocol error indicator" to the value of the variable PROTOCOL_ERROR_INDICATOR;
Information Block type 11; and
measurements are reported; and
1>take care that the maximum allowed message size is not exceeded when forming the IE "Measured results on
RACH".
.
2. The UE shall compare the value of the IE "Initial UE identity" in the received RRC CONNECTION SETUP
message with the value of the variable INITIAL_UE_IDENTITY.


2>perform the physical layer synchronisation procedure A as specified in [29] (FDD only).
Reference
3GPP TS 25.331 clauses 8.1.3.3, 8.1.3.6
To confirm that the UE manages to establish an RRC CONNECTION on another frequency when so required by SS in
the RRC CONNECTION SETUP message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
500
Initial condition
System simulator: 2 cells Cell 1 on UARFCN 1 and Cell 4 on UARFCN 4.
UE: "Registered idle mode on CS" (state 2) or "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4
of TS 34.108, depending on the CN domain supported by the UE. If the UE supports both CS and PS domains, the
initial state shall be "Registered idle mode on CS/PS" (state 7).
For system information block 11 for Cell 1 (gives IE's which are different from defaults given in 34.108 sec 6.1) to be
transmitted before idle update preamble.
System Information Block type 11
Use same message sub-clause 6.1 of TS34.108, with following exception:
SIB12 indicator FALSE
Measurement control system information
- Intra-frequency measurement system information
- Intra-frequency reporting quantity for RACH reporting
- SFN-SFN observed time difference reporting indicator No report
- CHOICE mode FDD
- Reporting quantity CPICH Ec/No
- Maximum number of reported cells on RACH Current Cell
- Reporting information for state CELL_DCH Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
501
- Intra-frequency measurement system information Not Present
- Inter-frequency measurement system information
- Inter-frequency cell info list
- New inter-frequency cell id
- Inter frequency cell id 4
- Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to table 6.1 of TS34.108 for Cell 4
- Cell info
- Cell individual offset Not Present
- Reference time difference to cell Not present
- Read SFN indicator FALSE
- CHOICE mode TDD
- Primary CCPCH info

Reference clause 6.1,TS34.108,Default settings for cell 4

- Cell parameters ID


- Primary CPICH TX power Not present
- Timeslot list

Not present

- Cell Selection and Re-selection Info Not present
For neigbouring cell, if HCS is not used and all the
parameters in cell selection and re-selection info are
Default value, this IE is absent.
- Qoffset1
s,n
0dB

- Maximum allowed UL TX power Reference to table 6.1.6, TS 34.108
- HCS neighbouring cell information Not present
- CHOICE mode TDD
- Qrxlevmin Reference to table 6.1.6, TS 34.108
- Cells for measurement Not present

Test procedure
The UE is initially in idle mode and is camping on cell 1. SIB 11 is broadcast in cell 1.
SS prompts the operator to make an outgoing call of a supported traffic class. The UE shall transmit an RRC
CONNECTION REQUEST on the CCCH, and SS replies with the RRC CONNECTION SETUP, in which the IEs are
set as described below. The UE shall send the RRC CONNECTION SETUP COMPLETE back to SS in cell 4 on the
DPCH described in the RRC CONNECTION SET UP messsage received from the SS. SS calls for generic procedure
C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
502
Expected sequence
UE SS
1 RRC CONNECTION REQUEST By outgoing call operation
2 RRC CONNECTION SETUP Indicating frequency of cell 4 and IE
"Primary CPICH info" set to Primary
Scrambling Code assigned to P-
CPICH of cell 4 for FDD.
3 The UE configures the layer 2 and
layer 1.
COMPLETE
This message is sent to SS on the
frequency indicated in the RRC
CONNECTION SETUP message
UE is in CELL_DCH state, the test

Specific message content
All messages indicated below shall use the same content as found in TS 34.108 clause 6.1 with the following
exceptions:
Measured results on RACH Check that the Ec/No for the cell 1 is reported.

Measured results on RACH Check that the P-CCPCH RSCP for the cell 1 is
reported.

RRC CONNECTION SETUP (Step 3) (FDD)
Frequency info
- UARFCN uplink(Nu) Not present
- UARFCN downlink(Nd) UARFCN downlink of cell 4

RRC CONNECTION SETUP (Step 3) (TDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
503
Frequency info
- UARFCN(Nt)

UARFCN of the cell 4

In step 4, the UE shall send the RRC CONNECTION SETUP COMPLETE message on the frequency indicated in the
RRC CONNECTION SETUP message.
8.1.2.11 RRC Connection Establishment in FACH state (Frequency band
modification): Success

with the value of the UE storing "Initial UE identity".
1>act upon all received information elements as specified in TS25.331 subclause 8.6, unless specified otherwise in
the following:
2>if the UE, according to subclause 8.6.3.3, will be in the CELL_FACH state at the conclusion of this
procedure:
3>if the IE "Frequency info" is included:
4>select a suitable UTRA cell according to TS25.304 on that frequency;
3>enter UTRA RRC connected mode;
3>select PRACH according to TS25.331 subclause 8.5.17;
3>select Secondary CCPCH according to TS5.331 subclause 8.5.19;
3>ignore the IE "UTRAN DRX cycle length coefficient" and stop using DRX.
.
2>enter UTRA RRC connected mode, in a state according to TS25.331 subclause 8.6.3.3;
successful state transition per TS25.331 subclause 8.6.3.3, with the contents set as specified below:
.
Reference
3GPP TS 25.331 clause 8.1.3.6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
504
To confirm that the UE enters to CELL_FACH state and correctly establishes signalling radio bearers using common
physical channels of a cell within the frequency band specified by SS in RRC CONNECTION SETUP message.
Initial Condition
System Simulator: 2 cellsCells 1 is active and cell 6 is inactive.
indicator
No report
- CHOICE mode
- FDD
- Reporting quantity CPICH Ec/N0

- Intra-frequency reporting quantity for RACH
Reporting

-SFN-SFN observed time difference reporting
indicator
No report
- CHOICE mode TDD
- CHOICE measurement quantity PCCPCH RSCP

Test Procedure
Table 8.1.2.11
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -72
P-CCPCH
RSCP
(TDD)
dBm
-55 -72 Off -72

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
505
SS switches the power settings from columns "T0" to "T1", whenever the description in multi-cell condition specifies
the transmission power settings for cell 1 and cell 6.
The UE is in Idle mode of cell 1 and the SS has configured its downlink transmission power setting according to
columns "T0" in table 8.1.2.11. The SS switches its downlink transmission power settings to columns "T1" and the UE
transmits an RRC CONNECTION REQUEST message to the SS on the uplink CCCH by attempting to make an
outgoing call. After SS receives this message, it assigns the necessary radio resources and U-RNTI to be used by the
UE. The SS then transmits an RRC CONNECTION SETUP message containing an IE "frequency info" IE "Frequency
info" set to uplink/downlink UARFCN as used for cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code
assigned to P-CPICH of cell 6 for FDD mode, and UARFCN as used for cell 6 and IE "Primary CCPCH RSCP info" set
as assigned in cell 6 for TDD mode. The SS monitors all uplink RACH channels of cell 6.The UE transmitting an RRC
CONNECTION SETUP COMPLETE message on the DCCH (mapped onto RACH) of cell 6.
Expected sequence
UE SS
1 The initial state of UE is in Idle
mode of cell 1 and the SS has
configured its downlink
transmission power setting
according to columns "T0" in table
8.1.2.11.
2 The SS switches its downlink
transmission power settings to
columns "T1" in table 8.1.2.11.
3 RRC CONNECTION REQUEST Operator makes an outgoing call.
The UE shall transmit this
message, indicating the proper
establishment cause.
4 RRC CONNECTION SETUP Including IE "Frequency info" set to
frequency information of cell 6 and
IE "Primary CPICH info" set to
Primary Scrambling Code assigned
to P-CPICH of cell 6 for FDD
mode, and IE "Primary CCPCH
RSCP info" set as assigned in cell
6 for TDD mode.
COMPLETE
UE shall send this message on the
DCCH, carried by the assigned
PRACH resources in cell 6.

Use the same message type found in clause 9 of TS 34.108, with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
506
- CHOICE mode
- FDD
- CPICH Ec/N0 The actual reported value is not checked

- CHOICE mode TDD
- P-CCPCH RSCP The actual reported value is not checked

RRC CONNECTION SETUP (Step 4) (FDD)
CONNECTION SETUP message (Transition to CELL_FACH)" found in [9] TS 34.108 clause 9 with the following
exception:
Frequency info
- UARFCN uplink(Nu) Same uplink UARFCN as used for cell 6
- UARFCN downlink(Nd) Same downlink UARFCN as used for cell 6

RRC CONNECTION SETUP (Step 4) (TDD)
CONNECTION SETUP message (Transition to CELL_FACH)" found in [9] TS 34.108 clause 9 with the following
exception:
Frequency info
- UARFCN (Nt) Same UARFCN as used for cell 6
- Cell parameters ID As used for cell 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
507
UE Radio Access Capability Checked to see if compatible with the stated capability in
PIXIT/PICS statements.
UE radio access capability extension Checked to see if compatible with the stated capability in
UE system specific Capability Checked to see if compatible with the stated capability in

After step 5 the UE shall transmit RRC CONNECTION SETUP COMPLETE message on the uplink DCCH in cell 6.

8.1.3 RRC Connection Release
8.1.3.1 RRC Connection Release in CELL_DCH state: Success
1. The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and
CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed
states.
When the UE receives the first RRC CONNECTION RELEASE message, it shall:

- in state CELL_DCH:
- initialise the counter V308 to zero;

- submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for
transmission using UM RLC on the DCCH to the UTRAN;

- start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio
interface.
2. When in state CELL_DCH and the timer T308 expires, the UE shall:
- increment V308 by one;
- if V308 is equal to or smaller than N308:
- retransmit the RRC CONNECTION RELEASE COMPLETE message, without incrementing "Uplink
RRC Message sequence number" for signalling radio bearer RB1 in the variable
INTEGRITY_PROTECTION_INFO;
- if V308 is greater than N308:
- release all its radio resources;

- enter idle mode;
- perform the actions specified in TS 25.331 clause 8.5.2 when entering idle mode;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
508
- and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.3, 8.1.4.6
To verify:
1. that the UE when receiving an RRC CONNECTION RELEASE message transmits N308+1 RRC
CONNECTION RELEASE COMPLETE messages before release of radio resources and entering into idle mode
2. that the time between UE transmissions of the RRC CONNECTION RELEASE COMPLETE message is equal
to the value of the T308 timer.
Initial Condition
UE: CELL_DCH state (state 6-1 or state 6-3) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
supported by the UE
Test Procedure
The UE is brought to the CELL_DCH state by prompting the operator to initiate an outgoing call. After the DCCH is
established, on reception of (CM) service request message from the UE, the SS will Send CM Service Reject message
(for state 6-1) or Service Reject message (for state 6-3) to complete the (CM) service Request procedure. After the UE
is brought into the stable state, SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the
connection. SS then waits for the UE to transmit an RRC CONNECTION RELEASE COMPLETE message using
unacknowledged mode. SS checks to see if UE re-transmit this message at each expiry of T308 timer and if N308+1
RRC CONNECTION RELEASE COMPLETE message have been received. SS calls for generic procedure C.1 to
check that UE is in Idle Mode state.
Expected sequence
UE SS
1 The UE is in the CELL_DCH
state after a successful RRC
connection establishment by
virtue of the operator making an
outgoing call.
2 RRC CONNECTION RELEASE SS disconnect the connection
established. The value in IE
"N308" is arbitrarily chosen from
1 to 8.
COMPLETE
SS waits for the arrival of N308
+1 such message with an
interarrival time of T308, using
unacknowledged mode.
4 SS verifies that the UE release
its L2 signalling radio bearer
and dedicated resources and
enters idle mode.
that UE is in Idle Mode state,
the test passes, otherwise it
fails.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
509
RRC CONNECTION RELEASE (Step 2)
Use the same message type found in clause 9 of TS 34.108, with the following exceptions:
N308 Arbitrarily chosen between 1 and 8

After step 2 the UE shall transmit N308 +1 RRC CONNECTION RELEASE COMPLETE messages. The time
between the transmissions shall be equal to the T308 timer value.
After step 3 the UE shall initiate the release of the L2 signalling radio bearer and dedicated resources and enter idle
mode.
8.1.3.2 RRC Connection Release using on DCCH in CELL_FACH state: Success
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH.
Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.
When the UE receives the first RRC CONNECTION RELEASE message; and
1>if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable
U_RNTI; or
1>if the message is received on DCCH:
the UE shall:

1>in state CELL_FACH:
2>if the RRC CONNECTION RELEASE message was received on the DCCH:
3>set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to
the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in
the table "Accepted transactions" in the variable TRANSACTIONS;
3>submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission
using AM RLC on the DCCH to the UTRAN.
3>when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been
confirmed by the lower layers:
4>release all its radio resources; and
4>indicate the release of the established signalling connections (as stored in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in
the variable ESTABLISHED_RABS) to upper layers; and
4>clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
4>clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
4>clear the variable ESTABLISHED_RABS;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
510
4>pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to
upper layers;
4>enter idle mode;
4>perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode.
3>and the procedure ends.

Reference
3GPP TS 25.331 clause 8.1.4.3.
To confirm that the UE releases the L2 signalling radio bearer and resources and goes back to the idle state after it
receives an RRC CONNECTION RELEASE message on downlink DCCH from the SS. It shall transmit an RRC
CONNECTON RELEASE COMPLETE message using acknowledged mode on uplink DCCH to the SS.
Initial Condition
UE: CELL_FACH state (state 6-2 or state 6-4) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
Test Procedure
The UE is brought to an initial state of CELL_FACH. After the successful establishment of the RRC connection, on
reception of (CM) service request message from the UE, the SS will send CM Service Reject message (for state 6-2) or
Service Reject message (for state 6-4) to complete the (CM) service Request procedure. After the UE is brought into the
stable state, the SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the radio link. When
the UE receives this message the UE transmits an RRC CONNECTION RELEASE COMPLETE message using
acknowledged mode to the SS. Finally, SS checks that the UE performs proper release of all radio resources and then
goes back to idle mode.
Expected sequence
UE SS
1 The UE is brought to the
CELL_FACH state.
2 RRC CONNECTION RELEASE SS sends this message using
unacknowledged mode RLC
operations on the uplink DCCH.
COMPLETE
The UE transmits this message
using acknowledged mode.
4 The UE releases L2 signalling
radio bearer and radio
resources. Then the UE goes to
idle mode.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
511
After step 2 the UE shall transmit an RRC CONNECTION RELEASE COMPLETE message using acknowledged
mode then it shall receive a response for this message from the SS-RLC.
After step 3 the UE shall release its L2 signalling radio bearers and radio resources, then it shall go back to idle mode.
8.1.3.3 RRC Connection Release using on CCCH in CELL_FACH state: Success
U_RNTI; or
the UE shall:


2>if the RRC CONNECTION RELEASE message was received on the CCCH:
3>release all its radio resources;
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the
variable ESTABLISHED_RABS) to the upper layers;
3>clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
upper layers;
3>enter idle mode;
3>perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode;
Reference
3GPP TS 25.331 clause 8.1.4.3.
To confirm that the UE releases all its radio resources upon the reception of a RRC CONNECTION RELEASE
message on the downlink CCCH, without transmitting RRC CONNECTION RELEASE COMPLETE message on the
uplink.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
512
Initial Condition
Test Procedure
The UE is brought to an initial state of CELL_FACH. After the successful establishment of the RRC connection, on
stable state, the SS transmits an RRC CONNECTION RELEASE message on the downlink CCCH. The UE shall
terminate the RRC connection and release all radio resources allocated to it. SS monitors the uplink DCCH and CCCH
to verify that no transmission is detected. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.
Expected sequence
UE SS
CELL_FACH state.
2 RRC CONNECTION RELEASE SS transmits this message with
the contents identical to that
found in TS 34.108 clause 9 on
downlink CCCH.
3 SS waits for a period equivalent to
60 seconds. The UE shall not
send any response message on
uplink direction during this period.
It shall release the radio
resources allocated and return to
idle mode.
that UE is in Idle Mode state, the

None.
After step 2 the UE shall release all its radio resources, return to idle mode, without transmitting RRC CONNECTION
RELEASE COMPLETE message on the uplink direction.
8.1.3.4 RRC Connection Release in CELL_FACH state: Failure
When acknowledged mode was used and RLC does not succeed in transmitting the RRC CONNECTION RELEASE
COMPLETE message, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
513
variable ESTABLISHED_RABS) to upper layers;
1>enter idle mode;
1>perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode;
Reference
3GPP TS 25.331 clause 8.1.4.9.
To confirm that the UE releases all its radio resources and enters idle mode when the UE does not succeed in
transmitting the RRC CONNECTION RELEASE COMPLETE message using acknowledged mode to the SS (i.e. the
UE-RLC does not receive an acknowledgement for the transmission of the RRC CONNECTION RELEASE
COMPLETE message from SS).
Initial Condition
supported by the UE
Test Procedure
At the start of the test, the UE is brought to CELL_FACH state. When the RRC connection has been established, on
stable state, the SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the radio link. When
the UE receives this message the UE transmits an RRC CONNECTION RELEASE COMPLETE message using
acknowledged mode to the SS. The SS ignores the message and does not transmit an RLC STATUS PDU to
acknowledge this message. SS checks to see that UE continues to release all its radio resources and then enters idle
mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
514
Expected sequence
UE SS
1 The UE is brought into
CELL_FACH state by asking the
operator to perform an outgoing
call attempt.
2 RRC CONNECTION RELEASE SS ask to disconnect the radio
link
COMPLETE
using acknowledged mode.
The SS shall not transmit an
RLC STATUS PDU to
acknowledge this message.
4 SS checks to make sure that UE
releases all its radio resources
and enters idle mode.
that UE is in Idle Mode state, the

None
After step 3 the UE shall release its L2 signalling radio bearers and radio resources then it shall go to idle mode.
8.1.3.5 RRC Connection Release in CELL_FACH state: Invalid message
If the RRC CONNECTION RELEASE message contains a protocol error causing the variable
PROTOCOL_ERROR_REJ ECT to be set to TRUE according to TS 25.331 clause 9, and if the "protocol error cause" in
PROTOCOL_ERROR_INFORMATION is set to any cause value except "ASN.1 violation or encoding error", the UE
shall perform procedure specific error handling as follows:
The UE shall:
1>ignore any IE(s) causing the error but treat the rest of the RRC CONNECTION RELEASE message as normal
according to TS 25.331 subclause 8.1.4.3, with an addition of the following actions:
3>set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to
the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in
the table "Rejected transactions" in the variable TRANSACTIONS;
3>include the IE "Error indication" in the RRC CONNECTION RELEASE COMPLETE message with:
4>the IE "Failure cause" set to the cause value "Protocol error"; and
4>the IE "Protocol error information" set to the value of the variable
PROTOCOL_ERROR_INFORMATION.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
515

radio access technology other than UTRAN, containing an undefined critical message extension, the UE shall:
1>set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension
not comprehended";
1>if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the
variable TRANSACTIONS:
2>store the IE "Message type" of the received message in the table "Rejected transactions" in the variable
TRANSACTIONS; and
2>set the IE "RRC transaction identifier" to zero in that table entry.
1>perform procedure specific error handling according to TS 25.331 clause 8.
Reference
3GPP TS 25.331 clause 8.1.4 and 9.3b.
When the UE receives an invalid RRC CONNECTION RELEASE message on the downlink DCCH, it shall transmit an
RRC CONNECTION RELEASE COMPLETE message that includes the appropriate error cause on the uplink DCCH.
Initial Condition
UE: CELL_FACH state (state 6-2 or state 6-4)as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
Test Procedure
The UE is initially in CELL FACH state. on reception of (CM) service request message from the UE, the SS will Send
CM Service Reject message (for state 6-2) or Service Reject message (for state 6-4) to complete the (CM) service
Request procedure. After the UE is brought into the stable state, the SS transmits an RRC CONNECTION RELEASE
message containing an unexpected critical message extension on the DCCH to request the UE to disconnect the RRC
connection. The UE shall transmit an RRC CONNECTION RELEASE COMPLETE message on the uplink DCCH,
which includes the IE "Error indication". This IE shall contain the "Protocol error information" IE which in turn
contains the IE Protocol error cause set to "Message extension not comprehended". Upon completion of the
procedure, the SS calls for generic procedure C.1 to check that UE is in IDLE state.
Expected sequence
UE SS
1 Void
2 Void
3 Void
4 Void
5 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
516
6 Void
7 Void
8 RRC CONNECTION RELEASE See specific message contents
for this message
COMPLETE
See specific message contents
for this message This message
is sent using acknowledged
mode.
10 Void
11 Void
12 Void
that UE is in IDLE state, the test

This message must be recognised by the UE as an RRC CONNECTION RELEASE message. However, it shall be
constructed (see TS 25.331 clause 10.1.1) such that the UE will detect critical extensions not defined for the protocol
release supported by the UE:
Message Type
RRC transaction identifier Arbitrarily selects an integer between 0 and 3
- Message authentication code SS calculates the value of MAC-I for this message and
writes to this IE. The first/ leftmost bit of the bit string
contains the most significant bit of the MAC-I.
- RRC Message sequence number SS provides the value of this IE, from its internal
counter.
Critical extensions FFH

RRC CONNECTION RELEASE COMPLETE (Step 9)
Check to see if the same message type found in clause 9 of TS 34.108 is received, with the following exceptions:
Error indication
- Failure cause Protocol error
- Protocol error information
- CHOICE diagnostics type Protocol error cause
- Protocol error cause Check to see if set to Message extension not
comprehended
After step 8 the UE shall transmit an RRC CONNECTION RELEASE COMPLETE message which includes the
appropriate cause values in IE "Protocol error information".
After step 12 the UE shall be in IDLE state.
8.1.3.6 RRC Connection Release in CELL_DCH state (Frequency band
If the UE first receives an RRC CONNECTION RELEASE message in CELL_DCH state, it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
517
- initialize the counter V308 to zero;
- submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission
using UM RLC on the DCCH to the UTRAN;
- start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio
interface.
If the timer T308 expires, the UE shall:
- increment V308 by one;
- if V308 is equal to or smaller than N308:
- retransmit the RRC CONNECTION RELEASE COMPLETE message;
- if V308 is greater than N308:
- release all its radio resources;
- enter idle mode;
- perform cell-selection according to TS25.304;
- procedure end;
Reference
3GPP TS 25.331 clause 8.1.4.
To confirm that when the UE receives an RRC CONNECTION RELEASE message the UE transmits N308+1 RRC
CONNECTION RELEASE COMPLETE messages using UM on DCCH.
To confirm that the UE enters into idle mode with performing cell-selection and selecting new cell configured by SS.
Initial Condition
System Simulator: 2 cellsCell 1 is active and cell 6 is inactive
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS
34.108, depending on the CN domain(s) supported by the UE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
518
- Frequency info
- CHOICE mode FDD
- UARFCN uplink(Nu) Not present
Absence of this IE is equivalent to apply the default
duplex distance defined for the operating frequency
according to 25.101
- UARFCN downlink(Nd) Reference to table 6.1.2 of TS34.108 for Cell 6
- Cell info
- CHOICE mode FDD
- Primary scrambling code Refer to clause titled "Default settings for cell No.6
(FDD)" in clause 6.1.4 of TS34.108
- Primary CPICH Tx power Not present
- Cell Selection and Re-selection Info
- Qoffset1
s,n
0dB
- Qoffset2s,n Not present
- Maximum allowed UL TX power Reference to table 6.1.1
- CHOICE mode FDD
- Qqualmin Reference to table 6.1.1
- Qrxlevmin Reference to table 6.1.1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
519
- Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to TS34.108 for Cell 4
- Cell info
- CHOICE mode TDD


- Cell parameters ID


- Timeslot list

Not present

- Cell Selection and Re-selection Info Not present
- Qoffset1
s,n
0dB

- Maximum allowed UL TX power Reference to table 6.1.6, TS34.108
- CHOICE mode TDD
- Qrxlevmin Reference to table 6.1.6, TS 34.108

Test Procedure
Table 8.1.3.6
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -55

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -55 Off -55

SS switches the power settings between columns "T0" and "T1", whenever the description in multi-cell condition
specifies a reverse in the transmission power settings for cell 1 and cell 6.
The UE is in CELL_DCH state of cell 1 and the SS has configured its downlink transmission power setting according to
columns "T0" in table 8.1.3.6. The SS switches its downlink transmission power settings to columns "T1". The SS
modify contents of SIB3 in cell 6. The SS transmits an RRC CONNECTION RELEASE message. After the SS
transmits an RRC CONNECTION RELEASE message to the UE, the SS waits for the UE to transmit RRC
CONNECTION RELEASE COMPLETE messages using UM on DCCH and checks to see if N308+1 such messages
has been received. The UE leaves connected mode and enters idle mode in cell 1. The UE shall perform cell reselection
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
520
and camp on cell 6 after reading the system information. The SS calls for generic procedure C.1 to check that UE is in
Idle state.
Expected sequence
UE SS
state of cell 1 and the SS has
according to columns "T0" in
table 8.1.3.6.
3 Void
4 Void
5 System Information Block type 3 The SS modifies SIB 3 in cell 1
to indicate that the cell is barred.
6 The SS waits for 5 s.
COMPLETE
The SS waits for the arrival of
N308+1 such messages send on
UM RLC.
9 The UE releases signalling radio
bearer and dedicated resources.
Then the UE goes to idle mode
in cell 1.
10 The UE select s cell 6 and camp
on it.
11 The SS waits for 15 s after
receiving the last RRC
CONNECTION
RELEASE COMPLETE
message.
that UE is in CELL_DCH state,

System Information Block type 3 (Step 5)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
521
- Cell Access Restriction
- Cell barred Barred
- Intra-frequency cell re-selection indicator Not allowed
- Tbarred 10[s]
- Cell Reserved for operator use Not reserved
- Cell Reservation Extension Not reserved
- Access Class Barred List
- Access Class Barred0 barred

N308 Arbitrarily chosen between 1 and 8

After step 6 the UE shall start to transmit N308 +1 times RRC CONNECTION RELEASE COMPLETE messages
using UM on DCCH.
After step 11 the UE shall be in Idle mode in cell 6.
8.1.3.7 RRC Connection Release in CELL_FACH state (Frequency band
When the UE receives the first RRC CONNECTION RELEASE message
the UE shall:
3>when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been
confirmed by the lower layers:
4>release all its radio resources; and
4>indicate the release of the established signalling connections ; and
upper layers;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
522
4>enter idle mode;
4>perform the actions specified in TS25.331 subclause 8.5.2 when entering idle mode.
a) 3>and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.
To confirm that when the UE receives an RRC CONNECTION RELEASE message, the UE releases signalling radio
bearer and its radio resources and goes back to the idle.
To confirm that the UE enters into idle mode withby performing cell-selection and selecting other cell than the UE
selecting cell in connected mode.

Initial Condition
System Simulator: 2 cells Cell 1 is active and cell 6 is inactive
of TS 34.108, depending on the CN domain supported by the UE If the UE supports both CS and PS domains, the initial
UE state shall be "Registered idle mode on CS/PS" (state 7).
Test Procedure
Table 8.1.3.7
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60

off -60
P-CCPCH
RSCP
(TDD)
dBm
-60 -60 off -60

The UE is in idle mode of cell 1 and the SS has configured its downlink transmission power setting according to
columns "T0" in table 8.1.3.7. SS request operator to make an outgoing call. The SS and UE execute procedure P4 or
P6. Next The SS and the UE execute procedure P8 or P10. The SS switches its downlink transmission power settings to
columns "T1" and then modifies SIB 3 to indicate that cell 1 is barred. The SS transmits an RRC CONNECTION
RELEASE message on DCCH. The UE shall transmit an RRC CONNECTION RELEASE COMPLETE message using
AM on DCCH and try to enter idle mode state in cell 1. On selecting cell 1 the UE reads system information block 3
and is aware that cell 1 is barred cell. Hence the UE selects cell 6 and camp on cell 6. Upon completion of the
procedure, the SS calls for generic procedure C.1 to check that UE is in idle mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
523
Expected sequence
UE SS
1 The UE is in the CELL_FACH
state of cell 1 and the SS has
table 8.1.3.7. SS requests
operator to make an outgoing
call.
2 SS executes procedure P4 (clause
7.4.2.1.2) or P6 (clause 7.4.2.2.2)
specified in TS 34.108.

7.4.2.3.2) or P10 (clause 7.4.2.4.2)

5 System Information Block type 3 The SS modifies SIB 3 in cell 1
to indicate that the cell is barred.
6 The SS waits for 5 s
COMPLETE

9 The SS waits for 5s
that UE is in idle mode, the test

- Cell Access Restriction
- Cell barred Barred
- Intra-frequency cell re-selection indicator Not allowed
- Tbarred 10[s]
- Cell Reserved for operator use Not reserved
- Cell Reservation Extension Not reserved
- Access Class Barred List

After step 3 the UE shall transmit RRC CONNECTION RELEASE COMPLETE messages using AM on DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
524
After step 9 the UE shall be in idle mode of cell 6.
8.1.3.8 Void
8.1.3.9 RRC Connection Release in CELL_DCH state (Network Authentication
Failure): Success
1. TS 25.331
If the upper layers request the release of the RRC connection, the UE shall:
1>enter idle mode;
1>perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2;
1>if the UE was in CELL_DCH state prior to entering idle mode:
2>consider all cells that were in the active set prior to entering idle mode to be barred according to [4]; and
2>consider the barred cells as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator",
and the maximum value in the IE "T
barred
".
2. TS 24.008
Following a UMTS authentication challenge, the MS may reject the core network, on the grounds of an incorrect
AUTN parameter (see 3GPP TS 33.102). This parameter contains two possible causes for authentication failure:
.
SQN failure:
If the MS considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it
shall send a AUTHENTICATION FAILURE message to the network, with the reject cause 'Synch failure'
and a re-synchronization token AUTS provided by the SIM (see 3GPP TS 33.102). The MS shall then follow
the procedure described in clause 4.3.2.6 (d) of TS 24.008.
.
Authentication failure (reject cause 'synch failure'):
The MS shall send an AUTHENTICATION FAILURE message, with reject cause 'synch failure,' to the network
and start the timer T3216.
.
If the timer T3216 expires, then the MS shall behave as described in clause 4.3.2.6.1 of TS 24.008.
Reference
3GPP TS 25.331 clause 8.1.4a.
3GPP TS 24.008 clause 4.3.2.5.1, 4.3.2.6
To confirm that when the upper layers request the release of the RRC connection, the UE releases signalling radio
bearer and its radio resources and goes back to idle mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
525
To confirm that the UE enters idle mode, bars the cell for a period T
barred
and hence performs cell-selection to another
(non-barred) cell.
Initial Condition
System Simulator: 3 cells Cell 1,2 and 3 are active.
UE: "CS-DCCH+DTCH_DCH" (state 6-9) or " PS-DCCH+DTCH_DCH " (state 6-10) in cell 1 as specified in clause
7.4 of TS 34.108, depending on the CN domain supported by the UE.
Test Procedure
Column marked "T0" denotes the initial conditions, while columns marked "T1" are to be applied subsequently. The
exact instants on which these values shall be applied are described in the text in this clause.

Table 8.1.3.9
T0 T1 T0 T1 T0 T1
UTRA RF Channel
Number
Ch. 1 Ch. 1 Ch. 1
CPICH Ec dBm/3.84
MHz
-60 -60 -85 -65 -85 -70
PCCPCH RSCP dBm
-60 -60 -85 -65 -85 -70

SS switches the downlink transmission power of the 3 cells to the columns "T1" in Table 8.1.3.9. UE transmits a
MEASUREMENT REPORT message which includes the primary scrambling code for cell 2 and 3 according to IE
"Intra-frequency event identity", which is set to '1a' for FDD mode and `1g` for TDD mode in the SYSTEM
INFORMATION BLOCK TYPE 11. For FDD, in steps 2 and 3, after the MEASUREMENT REPORT message is
received, the SS configures the new radio link to be added from cell 2 and then the SS transmits to the UE in cell 1 an
ACTIVE SET UPDATE message which includes IE "Radio Link Addition Information", indicating the addition of cell
2 into the active set, on DCCH using AM RLC.
When the UE receives this message, the UE shall configure layer 1 to begin reception without affecting the current
uplink and downlink activities of existing radio links. The UE shall transmit an ACTIVE SET UPDATE COMPLETE
message to the SS on the uplink DCCH using AM RLC.
The SS transmits a DOWNLINK DIRECT TRANSFER message. This message contains a NAS message
(AUTHENTICATION REQUEST for CS domain or AUTHENTICATION AND CIPHERING REQUEST for PS
domain) and an invalid SQN. The UE shall transmit an UPLINK DIRECT TRANSFER message using AM on DCCH.
After SS acknowledges the UPLINK DIRECT TRANSFER message, SS shall wait for T3216 or T3320 to expire in the
UE. The UE shall then deem that the network has failed the authentication check, release the RRC connection, enter
idle mode, bar cell 1 and 2 and perform cell reselection. Then SS wait for 5 s. SS transmits PAGING TYPE 1
message. The UE shall respond with RRC CONNECTION REQUEST message in cell 3. SS then transmit RRC
CONNECTION REJ ECT message back to UE. SS then waits for T
barred
to expire (22 minutes) before SS execute
generic procedure C.1 in cell 1 to check that UE is in idle mode in cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
526
Expected sequence
UE SS
1 MEASUREMENT REPORT See specific message contents
for this message.
2 ACTIVE SET UPDATE The SS transmit this message
on downlink DCCH using AM
RLC which includes IE "Radio
Link Addition Information" for
cell 2. This step will be only
applicable for FDD.
3 ACTIVE SET UPDATE COMPLETE The UE adds the radio link in
cell 2. This step will be only
applicable for FDD.
4 DOWNLINK DIRECT TRANSFER Depending on supported CN
domain, AUTHENTICATION
AND CIPHERING REQUEST
message (PS domain) or
AUTHENTICATION REQUEST
(CS domain) message is
embedded in DOWNLINK
DIRECT TRANSFER message.
An invalid SQN is provided in
this message.
5 UPLINK DIRECT TRANSFER After SS acknowledged this
message, SS waits for T3216
or T3320 to expire.
6 The SS waits for 5s
7 PAGING TYPE 1
8 RRC CONNECTION REQUEST SS checks that the UE sends
this message in cell 3
10 SS waits 22 minutes for Tbarred
to expire.
11 CALL C.1 SS execute this generic
procedure in cell 1. If the test
result of C.1 indicates that UE
is in idle mode, the test passes,
otherwise it fails.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
527
MEASUREMENT REPORT (Step 1) (FDD)
Message Type
- RRC Message sequence number This IE is checked to see if it is present. The value is
used by SS to compute the XMAC-I value.
Measurement identity 1
Measured Results
- Intra-frequency measured results
- Cell measured results
- Cell Identity Checked that this IE is absent
- SFN-SFN observed time difference Checked that this IE is absent
- Cell synchronisation information Checked that this IE is absent
- Primary scrambling code Refer to clause titled "Default settings for cell No.1 (FDD)"
in clause 6.1 of TS 34.108
- CPICH Ec/N0 Checked that this IE is absent
- CPICH RSCP Checked that this IE is present
- Pathloss Checked that this IE is absent
- Cell synchronisation information Checked that this IE is present and includes IE COUNT-
C-SFN frame difference
Measured results on RACH Checked that this IE is absent
Additional measured results Checked that this IE is absent
Event results
- Intra-frequency measurement event results
- Intra-frequency event identity 1a
- Cell measurement event results

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
528
MEASUREMENT REPORT (Step 1) (TDD)
Message Type
Measured Results
- CHOICE Mode TDD
- Cell parameters Id Refer to clause titled "Default settings for cell No.1 (TDD)"
- Primary CCPCH RSCP Info Checked that this IE is absent
- PCCPCH RSCP Checked to see if set to within an acceptable range"
- CHOICE Mode TDD
- CHOICE Mode TDD
Event results
- Intra-frequency event identity 1g
CHOICE Mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
529
ACTIVE SET UPDATE (Step 2) (FDD only)
The message to be used in this test is defined in TS 34.108, clause 9, with the following exceptions:
Radio link addition information
- Primary CPICH Info
- Primary Scrambling Code Set to same code as assigned for cell 2
- Downlink DPCH info for each RL

- CHOICE mode FDD
- Primary CPICH usage for channel estimation P-CPICH can be used.
- DPCH frame offset Calculated value from Cell synchronisation information
- Secondary CPICH info Not Present
- DL channelisation code This IE is repeated for all existing downlink DPCHs
allocated to the UE
- Secondary scrambling code 1
- Spreading factor Refer to TS 34.108 clause 6.10.2.4 "Typical radio
parameter sets"
- Code Number For each DPCH, assign the same code number in the
current code given in cell 1.
- Scrambling code change Not Present
- TPC Combination Index 0
- SSDT Cell Identity Not Present
- Close loop timing adjustment mode Not Present
- TFCI Combining Indicator Not Present
- SCCPCH information for FACH Not Present

ACTIVE SET UPDATE COMPLETE (Step 3) (FDD only)
Only the message type of this message is checked.
DOWNLINK DIRECT TRANSFER (Step 4)
Use the same message sub-type as found in TS 34.108 clause 9, with the following exceptions.
CN domain identity CS domain or PS domain
NAS message AUTHENTICATION REQUEST (CS domain) or
AUTHENTICATION AND CIPHERING REQUEST
(PS domain) with an invalid SQN value.

UPLINK DIRECT TRANSFER (Step 5)
Message Type
compared against the XMAC-I value computed by
SS. The first/ leftmost bit of the bit string contains the
most significant bit of the MAC-I.
NAS message AUTHENTICATION FAILURE(CS domain) or
AUTHENTICATION AND CIPHERING FAILURE (PS
domain)

At step 1 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
530
After step 2 the UE shall transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 4 the UE shall transmit an UPLINK DIRECT TRANSFER messages using AM on DCCH.
After step 7, the UE shall transmit RRC CONNECTION REQUEST message using TM RLC on CCCH in cell 3.
After step 10 the UE shall be in idle mode in cell 1.
8.1.4 Void
8.1.5 UE capability
8.1.5.1 UE Capability in CELL_DCH state: Success

The UE shall initiate the UE capability update procedure in the following situations:
1>the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

If the UE CAPABILITY INFORMATION message is sent in response to a UE CAPABILITY ENQUIRY message, the
UE shall:
1>include the IE "RRC transaction identifier"; and
1>set it to the value of "RRC transaction identifier" in the entry for the UE CAPABILITY ENQUIRY message in
UE_CAPABILITY_REQUESTED; and
1>include this in IE "UE radio access capability" and in IE "UE radio access capability extension", provided this IE
is included in variable UE_CAPABILITY_REQUESTED;
The UE RRC shall submit the UE CAPABILITY INFORMATION message to the lower layers for transmission on the
uplink DCCH using AM RLC. When the message has been delivered to lower layers for transmission the UE RRC shall
start timer T304 and set counter V304 to 1.
Upon reception of a UE CAPABILITY INFORMATION CONFIRM message, the UE shall:
1>stop timer T304;

If the UE receives a UE CAPABILITY INFORMATION CONFIRM message, which contains a protocol error causing
the variable PROTOCOL_ERROR_REJ ECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform
procedure specific error handling as follows:
1>stop timer T304;
1>transmit an RRC STATUS message on the uplink DCCH using AM RLC;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
531
1>include the IE "Identification of received message"; and
1>set the IE "Received message type" to UE CAPABILITY INFORMATION CONFIRM; and
1>set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the UE
CAPABILITY INFORMATION CONFIRM message in the table "Rejected transactions" in the variable
TRANSACTIONS; and
1>clear that entry;
1>include the IE "Protocol error information" with contents set to the value of the variable
PROTOCOL_ERROR_INFORMATION;
1>when the RRC STATUS message has been submitted to lower layers for transmission:
2>restart timer T304 and continue with any ongoing procedures or processes as if the invalid UE CAPABILITY
INFORMATION CONFIRM message has not been received.

not comprehended";
TRANSACTIONS; and
Reference
3GPP TS 25.331 clauses 8.1.6 and 8.1.7.9.3b.
1. To confirm that the UE transmits a UE CAPABILITY INFORMATION message after it receives a UE
CAPABILITY ENQUIRY message from the SS.
2. To confirm that the UE indicates an invalid message reception when invalid UE CAPABILITY ENQUIRY and
UE CAPABILITY INFORMATION CONFIRM messages are received. The UE shall transmit RRC STATUS
message with the correct error cause value to SS.
Initial Condition
Test Procedure
The UE is brought to the CELL_DCH state after a successful outgoing call attempt. The SS transmits a UE
CAPABILITY ENQUIRY message containing an unexpected critical message extension. After receiving such a
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
532
message, the UE shall report the error using RRC STATUS message with the appropriate error cause specified. Then
SS transmits a correct UE CAPABILITY ENQUIRY message, the UE receives this message and transmits a UE
CAPABILITY INFORMATION message on the uplink DCCH which includes the requested capabilities. The SS
transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry
procedure.
Then SS initiates another UE capability enquiry procedure. The UE shall reply with a UE CAPABILITY
INFORMATION message on the uplink DCCH. When SS receives this message, it transmits a UE CAPABILITY
INFORMATION CONFIRM message containing an unexpected critical message extension. The UE shall detect an
error and send an RRC STATUS message to report this event. After submitting this message to lower layers for
transmission, the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH after the
expiry of restarted T304. SS then trnsmits an error-free UE CAPABILITY INFORMATION CONFIRM message
similar to the message sent in step 6.
Expected sequence
UE SS
1 The UE is brought to
CELL_DCH state after an
outgoing call has been
established successfully.
2 UE CAPABILITY ENQUIRY See specific message
contents for this message
3 RRC STATUS See specific message
contents for this message.
5 UE CAPABILITY INFORMATION See specific message
6 UE CAPABILITY INFORMATION CONFIRM Use default message.
7 UE CAPABILITY ENQUIRY Same as in step 4.
8 UE CAPABILITY INFORMATION Shall be the same
message content as in
step 5.
9 UE CAPABILITY INFORMATION CONFIRM See specific message
10 RRC STATUS UE shall detect an error
and then transmit this
message.
11 UE CAPABILITY INFORMATION UE shall re-transmit this
message after the
restarted T304 expires.
12 UE CAPABILITY INFORMATION CONFIRM SS sends an error-free
message to acknowledge
the receipt of the uplink
message.

indicated in the IE "Access stratum release indicator":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
533
Message Type
counter.

RRC STATUS (Step 3)
- Received message type
- RRC transaction identifier

Protocol Error Information
- Protocol Error Cause

UE Capability Enquiry
Checked to see if the value is identical to the same IE in
the downlink UE CAPABILITY ENQUIRY message.

Message extension not comprehended

- Received message type UE Capability Enquiry
- Protocol Error Cause Message extension not comprehended

UE CAPABILITY ENQUIRY (Steps 4) (FDD)
Use the UE CAPABILITY ENQUIRY message as defined in [9] (TS 34.108) Clause 9, with the following exceptions:
- UE radio access FDD capability update
requirement
TRUE
- UE radio access TDD capability update
requirement
FALSE
list
Gsm

UE CAPABILITY ENQUIRY (Steps 4) (TDD)
- UE radio access FDD capability update
requirement
FALSE
- UE radio access TDD capability update
requirement
TRUE
list
Gsm

Check to see if the same message type found in [9] (TS 34.108) Clause 9 is received, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
534
UE system specific capability Presence and value will be checked. Stated capability
must be compatible with 34.123-2 (ICS statements) and
the user settings

indicated in the IE "Access stratum release indicator". Use the UE CAPABILITY INFORMATION CONFIRM
message as defined in [9] (TS 34.108) Clause 9, with the following addition:

RRC STATUS (Step 10)
- Received message type UE Capability Information Confirm
the downlink UE CAPABILITY INFORMATION
CONFIRM message.

After step 2, the UE shall transmit a RRC STATUS message on the uplink DCCH, reporting the error with protocol
error cause set to "Message extension not comprehended" correct transaction identifier.
After step 4 and 7 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to
respond to the UE CAPABILITY ENQUIRY message with correct contents.
After step 9, the UE shall transmit a RRC STATUS message on the uplink DCCH. The protocol error cause shall be set
to "Message extension not comprehended" and the transaction identifier set to the same value as used in the UE
CAPABILITY ENQUIRY message of step 7.
After step 10, the UE shall re-transmit the UE CAPABILITY INFORMATION message with a similar content as in
step 8 after the expiry of restarted T304.
8.1.5.2 UE Capability in CELL_DCH state: Success after T304 timeout

1>the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN on the DCCH using UM or AM
RLC;
1>while in connected mode the UE capabilities change compared to those stored in the variable
UE_CAPABILITY_TRANSFERRED.
UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
535
If the UE CAPABILITY INFORMATION message is sent because one or more of the UE capabilities change
compared to those stored in the variable UE_CAPABILITY_TRANSFERRED while in connected state, the UE shall
include the information elements associated with the capabilities that have changed in the UE CAPABILITY
INFORMATION message.


Upon expiry of timer T304, the UE shall check the value of V304 and:
1>if V304 is smaller than or equal to N304:
2>prior to retransmitting the UE CAPABILITY INFORMATION message:
3>if the IE "Status" in the variable INTEGRITY_PROTECTION_INFO has the value "Started":
4>include the same IEs as in the last unsuccessful attempt of this message, except for the IE "Integrity
check info", which is modified as follows:
5>increment the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the
variable INTEGRITY_PROTECTION_INFO by one;
5>set the IE "RRC Message sequence number" in the IE "Integrity check info" by the value of the
"Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable
INTEGRITY_PROTECTION_INFO in this message;
5>recalculate the IE "Message authentication code" in the IE "Integrity check info" in this message,
in accordance with TS 25.331 subclause 8.5.10.3.
3>else:
4>include the same IEs as in the last unsuccessful attempt of this message.
2>send the UE CAPABILITY INFORMATION message on signalling radio bearer RB2;
2>restart timer T304;
2>increment counter V304.

Reference
3GPP TS 25.331 clause 8.1.6 and 8.1.7.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
536
To confirm that the UE re-transmits a UE CAPABILITY INFORMATION message until V304 is greater than N304,
after the expiry of timer T304 when the UE cannot receive a UE CAPABILITY INFORMATION CONFIRM message
in response to a UE CAPABILITY INFORMATION message.
Initial Condition
Test Procedure
The UE is brought to CELL_DCH state. When the SS transmits a UE CAPABILITY ENQUIRY message which
includes the "Capability update requirement" IE, the UE shall reply with a UE CAPABILITY INFORMATION
message on the uplink DCCH which includes the "UE radio access capability" IE. The SS does not transmit a UE
CAPABILITY INFORMATION CONFIRM message to the UE, resulting in the T304 timer to expire. SS shall observe
that the UE attempts to transmit a UE CAPABILITY INFORMATION message again. The UE shall re-transmit N304
times, and SS transmits a UE CAPABILITY INFORMATION CONFIRM message to answer the last request and
completes this test procedure.
Expected sequence
UE SS
CELL_DCH state.
SS sets internal counter K
=0
2 UE CAPABILITY ENQUIRY Including the IE "Capability
update requirement".
3 UE CAPABILITY INFORMATION Including the "UE radio
access capability".
4 If K is equal to N304, then
proceed to step 6.
5 The SS does not transmit
a response and wait for
T304 timer to expire.
K=K+1 and goes to step 3.
6 UE CAPABILITY INFORMATION CONFIRM Use default message
contents

None
After step 3 the UE shall re-transmits a UE CAPABILITY INFORMATION message on the uplink DCCH, after each
expiry of timer T304. The UE CAPABILITY INFORMATION message shall contain IE "UE radio access capability"
indicating the settings found in PIC/PIXIT statements. After (N304) re-transmissions, the UE shall receive a UE
CAPABILITY INFORMATION CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
537
8.1.5.3 UE Capability in CELL_DCH state: Failure (After N304 re-transmissions)

RLC;
UE shall:


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
538
3>else:
2>initiate the Cell update procedure as specified in TS 25.331 subclause 8.3.1, using the cause "Radio link
failure".
Reference
3GPP TS 25.331 clauses 8.1.6 and 8.1.7.
To confirm that the UE stops retrying to transmit a UE CAPABILITY INFORMATION message if V304 is greater
than N304. It then initiates cell update procedure.
Initial Condition
Test Procedure
The UE is brought to CELL_DCH state. When the SS transmits a UE CAPABILITY ENQUIRY message which
includes the "Capability update requirement" IE, the UE receives this message and transmits a UE CAPABILITY
INFORMATION message on the uplink DCCH which includes the "UE radio access capability" IE. The SS does not
respond with a UE CAPABILITY INFORMATION CONFIRM message but keeps a count on the number of messages
received. When the T304 timer expires, the UE shall transmit a UE CAPABILITY INFORMATION message again.
After sending (N304+1) messages, the UE shall stop sending UE CAPABILITY INFORMATION messages and
initiates the cell update procedure. SS allows UE to return to "connected state" by issuing CELL UPDATE CONFIRM
message on the downlink DCCH. Then UE shall reconfigured its physical channel according to the CELL UPDATE
CONFIRM message and respond with PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
539
Expected sequence
UE SS
1 The UE starts from
CELL_DCH state.
SS sets counter K to 0
2 UE CAPABILITY ENQUIRY Use default message
3 UE CAPABILITY INFORMATION Use default message
a response and allows
SS increments counter K
If K is greater than N304,
proceeds to step 5 else
returns to 3.
5 CELL UPDATE The UE assumes that
radio link failure has
occurred and transmits
this message which
includes IE "Cell update
cause" set to "radio link
failure".
6 CELL UPDATE CONFIRM This message include IE
"Physical channel
information elements".
7 The SS configure the
dedicated physical
channel according to the
IE "Physical channel
information elements"
included in the CELL
UPDATE CONFIRM
message.
8 PHYSICAL CHANNEL RECONFIGURATION
COMPLETE

CELL UPDATE CONFIRM (Step 6) - FDD
The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM message" as found
in clause 9 of TS 34.108 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
540
U-RNTI Same as CELL UPDATE message in step 5
RRC State indicator CELL_DCH
Frequency info
- CHOICE mode FDD
- UARFCN uplink(Nu) Reference to TS34.108 clause 5.1 Test frequencies
- UARFCN downlink(Nd) Reference to TS34.108 clause 5.1 Test frequencies
Maximum allowed UL TX power 33dBm
CHOICE Mode FDD
- Primary scrambling code 100
- PDSCH with SHO DCH info Not Present
- PDSCH code mapping Not Present
- CHOICE mode FDD
- Primary CPICH usage for channel estimation Primary CPICH may be used
- DPCH frame offset 0 chips

- Spreading factor Reference to TS34.108 clause 6.10 Parameter Set
- Code number SF-1(SF is reference to TS34.108 clause 6.10 Parameter
Set)
- Scrambling code change No change
- TPC combination index 0
- SSDT Cell Identity -a
- Closed loop timing adjustment mode Not Present

CELL UPDATE CONFIRM (Step 6) 3.84 Mcps TDD
Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to TS34.108 clause 5.1 Test frequencies
CHOICE Mode TDD
- CHOICE mode TDD
- CHOICE SyncCase Not Present
- Cell Parameters ID Not Present
- Block STTD indicator FALSE
- CHOICE mode TDD
- DL CCTrCh List
- TFCS ID 1
- Time info
- Activation time Not Present (default)
- Duration Not Present (default)
- Common timeslot info Not Present (default)
- Downlink DPCH timeslots and codes Not Present (default)
- UL CCTrCH TPC List Not Present (default)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
541
CELL UPDATE CONFIRM (Step 6) 1.28 Mcps TDD
Frequency info
- CHOICE mode TDD
CHOICE Mode TDD
- CHOICE mode TDD
- TSTD indicator FALSE
- CHOICE mode TDD
- DL CCTrCh List
- TFCS ID 1
- Time info

After step 2, the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH. The UE shall
re-transmit this message for N304 times.
After step 4, the UE shall initiate the cell update procedure.
After step 6, UE shall respond with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after it
has configured L1 according to the CELL UPDATE CONFIRM message in step 6.
8.1.5.4 UE Capability in CELL_FACH state: Success

1>the UE receives a UE CAPABILITY ENQUIRY message from the UTRAN;

UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
542
Upon reception of a UE CAPABILITY INFORMATION CONFIRM message, the UE shall:
1>stop timer T304;

If the UE receives a UE CAPABILITY INFORMATION CONFIRM message, which contains a protocol error causing
the variable PROTOCOL_ERROR_REJ ECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform
procedure specific error handling as follows:
1>stop timer T304;
1>set the IE "Received message type" to UE CAPABILITY INFORMATION CONFIRM; and
CAPABILITY INFORMATION CONFIRM message in the table "Rejected transactions" in the variable
TRANSACTIONS; and
1>clear that entry;
2>restart timer T304 and continue with any ongoing procedures or processes as if the invalid UE CAPABILITY
INFORMATION CONFIRM message has not been received.

not comprehended";
TRANSACTIONS; and
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
543
Reference
3GPP TS 25.331 clauses 8.1.6 and 8.1.7.9.3b.
1. To confirm that the UE transmits a UE CAPABILITY INFORMATION message after it receives a UE
CAPABILITY ENQUIRY message from the SS.
2. To confirm that the UE indicates an invalid message reception when invalid UE CAPABILITY ENQUIRY and
UE CAPABILITY INFORMATION CONFIRM messages are received. The UE shall transmit RRC STATUS
message with the correct error cause value to SS.
Initial Condition
UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to the CELL_FACH state after a successful outgoing call attempt. The SS transmits a UE
CAPABILITY ENQUIRY message containing an unexpected critical message extension. After receiving such a
message, the UE shall report an error using RRC STATUS message with the appropriate error cause specified. Then SS
transmits a UE CAPABILITY ENQUIRY message which includes the IE "Capability update requirement". After UE
receives this message, it transmits a UE CAPABILITY INFORMATION message on the uplink DCCH, which includes
the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to
complete the UE capability enquiry procedure.
Then SS initiates another UE capability enquiry procedure. The UE shall reply with a UE CAPABILITY
INFORMATION message on the uplink DCCH. When SS receives this message, it transmits a UE CAPABILITY
INFORMATION CONFIRM message containing an unexpected critical message extension. The UE shall detect an
error and send an RRC STATUS message to report this event. After submitting this message to lower layers for
transmission, the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH upon the
expiry of restarted T304. SS completes this test by sending an error-free UE CAPABILITY INFORMATION
CONFIRM message similar to the message sent in step 6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
544
Expected sequence
UE SS
CELL_FACH state after
an outgoing call has been
3 RRC STATUS See specific message
4 UE CAPABILITY ENQUIRY Use default message.
5 UE CAPABILITY INFORMATION Use default message.
7 UE CAPABILITY ENQUIRY Same as in step 4.
8 UE CAPABILITY INFORMATION The message content
shall be the same as in
step 5.
9 UE CAPABILITY INFORMATION CONFIRM See specific message
10 RRC STATUS UE shall detect an error
and then transmit this
message on uplink
DCCH.
11 UE CAPABILITY INFORMATION UE shall re-transmit this
message after the
restarted T304 expires.
12 UE CAPABILITY INFORMATION CONFIRM SS sends an error-free
message to acknowledge
the receipt of the uplink
message.

Message Type
counter.

RRC STATUS (Step 3)
Check to is the same message type found in TS 34.108, clause 9 is received, with the following exceptions:
- Received message type UE Capability Enquiry
RRC transaction identifier Checked to see if the value is identical to the same IE in

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
545
indicated in the IE "Access stratum release indicator". Use the UE CAPABILITY INFORMATION CONFIRM
message as defined in [9] (TS 34.108) Clause 9, with the following addition:

RRC STATUS (Step 10)
- Received message type UE Capability Information Confirm
the downlink UE CAPABILITY INFORMATION
CONFIRM message.

After step 2, the UE shall transmit a RRC STATUS message on the uplink DCCH, reporting the error with protocol
error cause set to "Message extension not comprehended" correct transaction identifier.
After step 4 and 7 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to
respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.
to "Message extension not comprehended" and the transaction identifier set to the same value as used in the UE
CAPABILITY ENQUIRY message of step 7.
After step 10, the UE shall re-transmit the UE CAPABILITY INFORMATION message with a similar content as in
step 8 upon the expiry of restarted T304.
8.1.5.5 UE Capability in CELL_FACH state: Success after T304 timeout

RLC;
UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
546


3>else:

Reference
3GPP TS 25.331 clauses 8.1.6 and 8.1.7.
To confirm that the UE re-transmits a UE CAPABILITY INFORMATION message until V304 is greater than N304,
after the expiry of timer T304 when it fails to receive a downlink UE CAPABILITY INFORMATION CONFIRM
message in response to the uplink UE CAPABILITY INFORMATION message sent.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
547
Initial Condition
UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to CELL_FACH state. When the SS transmits a UE CAPABILITY ENQUIRY message which
includes the IE "Capability update requirement", the UE shall reply with a UE CAPABILITY INFORMATION
message on the uplink DCCH that contains the IE "UE radio access capability". The SS waits and does not transmit a
UE CAPABILITY INFORMATION CONFIRM message to the UE, resulting in the T304 timer to expire. SS shall
observe that the UE attempts to transmit a UE CAPABILITY INFORMATION message again. The UE shall
re-transmit N304 times, and SS transmits a UE CAPABILITY INFORMATION CONFIRM message to answer the last
request and completes this test procedure.
Expected sequence
UE SS
CELL_FACH state.
SS sets internal counter K
=0
2 UE CAPABILITY ENQUIRY Including the IE "Capability
update requirement".
3 UE CAPABILITY INFORMATION Including the IE "UE radio
access capability".
4 If K equals N304, then
proceeds to step 6. Else,
continue with step 5.
a response and wait for
K=K+1 and goes to step 3.
6 UE CAPABILITY INFORMATION CONFIRM Use default message
contents

None
After step 3 the UE shall re-transmit a UE CAPABILITY INFORMATION message on the uplink DCCH, after each
expiry of timer T304. The UE CAPABILITY INFORMATION message shall contain IE "UE radio access capability"
with the value matching those stated in the ICS/IXIT statements. After (N304) re-transmissions, the UE shall receive a
UE CAPABILITY INFORMATION CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
548
8.1.6 Direct Transfer
8.1.6.1 Direct Transfer in CELL DCH state (invalid message reception and no
signalling connection exists)

If the UE receives a DOWNLINK DIRECT TRANSFER message, and the signalling connection identified with the IE
"CN domain identity" does not exist according to the variable ESTABLISHED_SIGNALLING_CONNECTIONS, the
UE shall:
1>ignore the content of the DOWNLINK DIRECT TRANSFER message;
1>set the IE "Received message type" to DOWNLINK DIRECT TRANSFER; and
1>set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the
DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable
TRANSACTIONS; and
1>clear that entry;
1>include the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible
with receiver state".

If the UE receives a DOWNLINK DIRECT TRANSFER message, which contains a protocol error causing the variable
PROTOCOL_ERROR_REJ ECT to be set to TRUE according to TS 25.331 clause 9, the UE shall perform procedure
specific error handling as follows:
DOWNLINK DIRECT TRANSFER message in the table "Rejected transactions" in the variable
TRANSACTIONS; and
1>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
549
When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall:
1>continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has
not been received.

not comprehended";
Reference
3GPP TS 25.331 clause 8.1.9.3a, 8.1.9.4, 9.3b.
To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a
DOWNLINK DIRECT TRANSFER message with a non comprehended critical extension. To confirm that the UE
transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT TRANSFER
message which includes an invalid IE "CN domain identity".
Initial Condition
UE: CELL_DCH (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
Test Procedure
The UE is in the CELL_DCH state. The SS transmits an invalid DOWNLINK DIRECT TRANSFER message to the
UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message
extension not comprehended" shall be indicated in IE "Protocol error cause". The SS transmits a DOWNLINK DIRECT
TRANSFER message that contains an invalid IE "CN domain identity" to the UE. The UE shall transmit an RRC
STATUS message on the DCCH using AM RLC. The error type "Message not compatible with receiver state" shall be
indicated in IE "Protocol error cause".
Expected sequence
UE SS
1 DOWNLINK DIRECT TRANSFER See specific message content
2 RRC STATUS
3 DOWNLINK DIRECT TRANSFER Sent from a new CN domain.
4 RRC STATUS

Use the same message content as found in clause 9 of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
550

RRC STATUS (Step 2)
Message content is the same as found in clause 9 of TS 34.108, with the following exceptions:
Identification of received messag type
- Received message type DOWNLINK DIRECT TRANSFER
- RRC transaction identifier Same value in the DOWNLINK DIRECT TRANSFER
message in step 1.
Protocol error cause Message extension not comprehended

CN domain identity CS domain or PS domain as unselected domain
NAS message Arbitrary message.

RRC STATUS (Step 4)
Message content is the same as found in clause 9 of TS 34.108, with the following exceptions:
message in step 3.
Protocol error cause Message not compatible with receiver state

After step 1 the UE shall transmit an RRC STATUS message on the DCCH using AM RLC setting "Message extension
not comprehended" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received message
type".
After step 3 the UE shall transmit a n RRC STATUS message on the DCCH using AM RLC setting "Message not
compatible with receiver state" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received
message type".
8.1.6.2 Direct Transfer in CELL FACH state (invalid message reception and no
signalling connection exists)

If the UE receives a DOWNLINK DIRECT TRANSFER message, and the signalling connection identified with the IE
"CN domain identity" does not exist according to the variable ESTABLISHED_SIGNALLING_CONNECTIONS, the
UE shall:
1>ignore the content of the DOWNLINK DIRECT TRANSFER message;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
551
DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable
TRANSACTIONS; and
1>clear that entry;

If the UE receives a DOWNLINK DIRECT TRANSFER message, which contains a protocol error causing the variable
DOWNLINK DIRECT TRANSFER message in the table "Rejected transactions" in the variable
TRANSACTIONS; and
1>clear that entry;
When the RRC STATUS message has been submitted to lower layers for transmission, the UE shall:
1>continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has
not been received.

not comprehended";
Reference
3GPP TS 25.331 clause 8.1.9.3a, 8.1.9.4, 9.3b.
To confirm that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a
DOWNLINK DIRECT TRANSFER message which does not include any IEs except IE "Message Type". To confirm
that the UE transmits an RRC STATUS message on the DCCH using AM RLC if it receives a DOWNLINK DIRECT
TRANSFER message which includes an invalid IE "CN domain identity".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
552
Initial Condition
UE: CS-DCCH_FACH (state 6-6) or PS_DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108, depending
on the CN domain(s) supported by the UE.
Test Procedure
The UE is in the CELL_FACH state. The SS transmits an invalid DOWNLINK DIRECT TRANSFER message to the
UE. The UE shall transmit an RRC STATUS message on the DCCH using AM RLC. The error type "Message
extension not comprehended" shall be indicated in IE "Protocol error cause". The SS transmits a DOWNLINK DIRECT
TRANSFER message that contains an invalid IE "CN domain identity" to the UE. The UE shall transmit an RRC
STATUS message on the DCCH using AM RLC. The error type "Message not compatible with receiver state" shall be
indicated in IE "Protocol error cause".
Expected sequence
UE SS
1 DOWNLINK DIRECT TRANSFER See specific message content
2 RRC STATUS
3 DOWNLINK DIRECT TRANSFER Sent from a new CN domain.
4 RRC STATUS

Critical extentions '01'H

RRC STATUS (Step 2)
Message content is the same as found in Clause 9 of TS 34.108, with the following exceptions:
message in step 1.

CN domain identity CS domain or PS domain as unselected domain
NAS message Arbitrary message.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
553
RRC STATUS (Step 4)
Message content is the same as found in Clause 9 of TS 34.108, with the following exceptions:

Identification of received message type
message in step 3.
Protocol error cause Message not compatible with receiver state

After step 1 the UE shall transmit an RRC STATUS message on the DCCH using AM RLC setting "Message extension
not comprehended" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received message
type".
After step 3 the UE shall transmit a n RRC STATUS message on the DCCH using AM RLC setting "Message not
compatible with receiver state" in IE "Protocol error cause" and "DOWNLINK DIRECT TRANSFER" in IE "Received
message type".
8.1.6.3 Measurement Report on INITIAL DIRECT TRANSFER message and
UPLINK DIRECT TRANSFER message

Reference
3GPP TS 25.331, clause 8.1.8.2, 8.1.10.2
To confirm that the UE reports measured results on RACH messages, if it receives IE "Intra-frequency reporting
quantity for RACH reporting" and IE "Maximum number of reported cells on RACH" from System Information Block
Type 11 or 12 upon a transition from idle mode to CELL_FACH state.
Initial Condition
UE: "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108. If the UE supports both CS
and PS domains, the initial UE state shall be "Registered idle mode on CS/PS" (state 7).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
554
System Information Block type 11 (Step 1) (FDD)
Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
555
FACH measurement occasion info Not Present
- Use of HCS Not used
- Cell selection and reselection quality measure CPICH RSCP
- Intra-frequency measurement identity 5
- Intra-frequency cell info list
- CHOICE intra-frequency cell removal Remove no intra-frequency cells
- New intra-frequency cells
- Intra-frequency cell id 0
- Cell info
- Cell individual offset 0 dB
- Read SFN Indicator FALSE
- CHOICE mode FDD
- Primary CPICH TX power Not Present
- TX Diversity Indicator FALSE
- Cell selection and Re-selection info Not present
- Intra-frequency Measurement quantity
- Filter Coefficient 0
- Measurement quantity CPICH RSCP
- Intra-frequency measurement for RACH reporting
- SFN-SFN observed time difference No report
- Reporting quantity CPICH RSCP
- Maximum number of reported cells on RACH Current cell
- Reporting information for state CELL_DCH
- Intra-frequency reporting quantity
- Reporting quantities for active set cells
- Cell synchronisation information reporting
indicator
FALSE
- Cell identity reporting indicator FALSE
- CPICH Ec/No reporting indicator FALSE
- CPICH RSCP reporting indicator FALSE
- Pathloss reporting indicator FALSE
- Reporting quantities for monitored set cells
indicator
TRUE
- CPICH RSCP reporting indicator TRUE
- Reporting quantities for detected set cells Not present
- Measurement Reporting Mode
- Measurement Reporting Transfer Mode Acknowledged mode RLC
- Periodic Reporting/Event Trigger Reporting Mode Event trigger
- CHOICE report criteria Intra-frequency measurement reporting criteria
- Parameters required for each event
- Triggering condition 1 Not Present
- Triggering condition 2 Monitored set cells
- Reporting Range Constant 15 dB
- Cells forbidden to affect reporting range Not Present
- W 0.0
- Hysteresis 1.0 dB
- Threshold used frequency Not Present
- Reporting deactivation threshold 0
- Replacement activation threshold Not Present
- Time to trigger 60 ms
- Amount of reporting Infinity
- Reporting interval 16 seconds
- Reporting Cell Status
- CHOICE reported cell Report cells within active and/or monitored set on used
frequency or within active and/or monitored set on non-
used frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
556
- Maximum number of reported cells 2
- Inter-frequency measurement system information Not Present
- Traffic volume measurement system information Not Present
System Information Block type 11 (Step 1) (TDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
557
- Cell info
- CHOICE mode TDD
- Primary CCPCH Info Set to same as used for cell 1
- Measurement quantity PCCPCH RSCP
- Reporting quantity PCCPCH RSCP
indicator
FALSE
- PCCPCH RSCP reporting indicator FALSE
indicator
TRUE
- PCCPCH RSCP reporting indicator TRUE
- Periodic Reporting/Event Trigger Reporting
Mode
Event trigger
- W 0.0
- Hysteresis 1.0 dB
- CHOICE reported cell Report cells within active and/or monitored set on
used frequency or within active and/or monitored set
on non-used frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
558
Test Procedure
The UE is initially in idle mode and camps on cell 1. SS prompts the operator to make an outgoing call for one of the
traffic classes supported by the UE. SS and UE shall execute out going call procedure. During this procedure UE
transmits INITIAL DIRECT TRANSFER and UPLINK DIRECT TRANSFER messages with IE"Measured results on
RACH" which is set to measured CPICH RSCP in the current cell. After that SS releases a RRC connection.
Expected Sequence
UE SS
1 The UE is in idle mode and
camps onto cell 1.
2 SS prompts the test operator
to make an outgoing call.
4 RRC CONNECTION SETUP See default message content
(Transition to CELL_FACH)
5 RRC CONNECTION SETUP COMPLETE See default message content
6 INITIAL DIRECT TRANSFER ( SERVICE
REQUEST )
See specific message content
7 DOWNLINK DIRECT TRANSFER(
AUTHENTICATION AND CIPHERING
REQUEST )
See default message content
8 UPLINK DIRECT TRANSFER(
AUTHENTICATION AND CIPHERING
RESPONSE )
9 SECURITY MODE COMMAND See default message content
10 SECURITY MODE COMPLETE See default message content
11 UPLINK DIRECT TRANSFER( ACTIVATE
PDP CONTEXT REQUEST )
12 RRC CONNECTION RELEASE See default message content
13 RRC CONNECTION RELEASE COMPLETE See default message content

Measured results on RACH
- CHOICE measurement quantity Check to see if set to 'CPICH RSCP'
- CPICH RSCP Checked to see if set to within an acceptable range.
- Measurement results for monitored cells Checked to see if this IE is absent.

- CHOICE measurement quantity Check to see if set to 'PCCPCH RSCP'
- PCCPCH RSCP Checked to see if set to within an acceptable range.

INITIAL DIRECT TRANSFER ( SERVICE REQUEST ) (Step 6) (FDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
559

INITIAL DIRECT TRANSFER ( SERVICE REQUEST ) (Step 6) (TDD)


UPLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING RESPONSE ) (Step 8)
UPLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING RESPONSE ) (Step 8) (TDD)

UPLINK DIRECT TRANSFER( ACTIVATE PDP CONTEXT REQUEST ) (Step 11) (FDD)

UPLINK DIRECT TRANSFER( ACTIVATE PDP CONTEXT REQUEST ) (Step 11) (TDD)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
560

After step 2 the UE shall transmit a RRC CONNECTION REQUEST message which includes IE "measured results on
RACH", containing the measurement value for cell 1's CPICH RSCP (FDD mode) or PCCPCH RSCP (TDD mode).
After step 5 the UE shall transmit a INITIAL DIRECT TRANSFER ( SERVICE REQUEST) message which includes
IE "measured results on RACH", containing the measurement value for cell 1's CPICH RSCP.
After step 7 the UE shall transmit a UPLINK DIRECT TRANSFER( AUTHENTICATION AND CIPHERING
RESPONSE ) message which includes IE "measured results on RACH", containing the measurement value for cell 1's
CPICH RSCP (FDD mode) or PCCPCH RSCP (TDD mode).
After step 10 the UE shall transmit a UPLINK DIRECT TRANSFER( ACTIVATE PDP CONTEXT REQUEST )
message which includes IE "measured results on RACH", containing the measurement value for cell 1's CPICH RSCP
(FDD mode) or PCCPCH RSCP (TDD mode).
8.1.6.4 UPLINK Direct Transfer (RLC re-establishment)
If signalling radio bearer RB n (where n equals to 3 or 4) was used when transmitting the UPLINK DIRECT
TRANSFER message and a re-establishment of RLC on same signalling radio bearer RB n occurs before the successful
delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, the UE shall:
1>retransmit the UPLINK DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio
bearer RB3.
Reference
3GPP TS 25.331 clause 8.1.10.2a.
To confirm that the UE transmits a second UPLINK DIRECT TRANSFER message after the re-establishment of RLC
on RB3 which occurs before the successful delivery of the first UPLINK DIRECT TRANSFER message.
Initial Condition
System Simulator: 1 cell Cell 1 is active.
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
For RRC CONNECTION SETUP message to be transmitted in the initial setup, use the default message given in TS
34.108 subclause 9 with the following exceptions:.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
561
RRC CONNECTION SETUP
Signalling RB information to setup (AM DCCH for NAS_DT High priority)
- RB identity Not Present
- CHOICE RLC info type
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 1
- Polling info
- Timer_poll 1000
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
- Number of RLC logical channels 1
- RLC size index According to TS34.108 clause 6.10.2.4.1.3 for
FDD, 6.10.3.4.1.3 for TDD 3.84 Mcps option or
6.11.5.4.1.3 for TDD 1.28 Mcps option
(standalone 13.6 kbps signalling radio bearer)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
562
Test Procedure
UE is in CELL_DCH. SS set the RLC entity for SRB3 to stop. SS requests operator to deactivate the established PDP
context. Then the UE shall transmit an UPLINK DIRECT TRANSFER message on the uplink DCCH. SS does not
acknowledge the AM PDUs carrying UPLINK DIRECT TRANSFER message. The SS then sends a UTRAN
MOBILITY INFORMATION message on SRB1 requesting the UE to do a SRNS relocation, 5s after asking the
operator to deactivate the established PDP context. The UE shall send a UTRAN MOBILITY INFORMATION
CONFIRM message on SRB2. The SS set the RLC entity for SRB3 to continue upon receiving UTRAN MOBILITY
INFORMATION CONFIRM message. Then UE shall retransmit an UPLINK DIRECT TRANSFER message on the
uplink DCCH.
Expected sequence
UE SS
1 SS set the RLC entity for SRB3 to
stop. SS requests operator to make
an outgoing cal.
2 UPLINK DIRECT TRANSFER .
CONFIRM
UE sends this message on uplink
DCCH on AM RLC.
After the reception, SS configures
RB 3 to continue.

5 UPLINK DIRECT TRANSFER DEEACTIVATE PDP CONTEXT
REQUEST message is embedded
in UPLINK DIRECT TRANSFER
message.

UTRAN MOBILITY INFORMATION (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9 with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
563
Ciphering mode info This presence of this IE is dependent on IXIT
statements in TS 34.123-2. If ciphering is indicated to
be active, this IE present with the values of the sub
IEs as stated below. Else, this IE is omitted.
- Ciphering mode command Start/restart
- Ciphering algorithm UEA0 or UEA1. The indicated algorithm must be one
of the algorithms supported by the UE as indicated in
the IE "security capability" in the RRC CONNECTION
SETUP COMPLETE message.
- Ciphering activation time for DPCH (256+CFN-(CFN MOD 8 +8))MOD 256, this IE is set
to "Not present" if only PS RABs are established
during the initial setup procedure.
- Radio bearer downlink ciphering activation time
info

- Radio bearer activation time
- RB identity 1
- RLC sequence number Current RLC SN +2
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20, this IE is set to "Not present" if PS RAB is not
established during the initial setup procedure.
- Integrity protection initialisation number SS selects an arbitrary 32 bits number for FRESH.
significant bit of the FRESH.
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B

- START list Not checked.

Message Type
SS. The first/ leftmost bit of the bit string contains the
CN domain identity PS domain
NAS message DEACTIVATE PDP CONTEXT REQUEST

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
564
After step 3, the UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM message using uplink DCCH on
AM RLC and then retransmit UPLINK DIRECT TRANSFER message on the uplink DCCH.
8.1.7 Security mode command
8.1.7.1 Security mode command in CELL_DCH state (CS Domain)

1. This procedure is used to trigger or start of ciphering or to command the restart of ciphering with the new
ciphering configuration for the signalling radio bearers and any radio bearers of a particular CN Domain. It is
also used to start integrity protection or modify integrity protection configuration for the signalling radio bearers.
2. When the UE receives a SECURITY MODE COMMAND message from the UTRAN, which indicates a
downlink activation time for each effected SRB and RB, and new ciphering mode configuration, the UE shall
apply the old ciphering configuration, for a particular SRB or RB, before the stated downlink activation time. It
shall start to decipher using the new ciphering configuration at the downlink activation time.
3. After the UE has transmitted a SECURITY MODE COMPLETE message using the new integrity protection
configuration which includes uplink activation time, it shall start to cipher transmission in the uplink using the
new configuration at the respective uplink activation time for each SRB or RB.
Reference
3GPP TS 25.331 clauses 8.1.12, 8.6.3.4, 8.6.3.5.
To confirm that the UE activates the new ciphering configurations after the stated activation time. To confirm that after
the UE receives a SECURITY MODE COMMAND message, it transmits a SECURITY MODE COMPLETE message
to the UTRAN using the old ciphering configuration together with the application of the new integrity protection
configuration. To confirm that UE send SECURITY MODE FAILURE message when SS transmits a SECURITY
MODE COMMAND message that causes an invalid configuration. To confirm that the UE sends a SECURITY MODE
FAILURE message when the UE receives an invalid SECURITY MODE COMMAND message.
Initial Condition
UE: CELL_DCH (state 6-9) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS initiates an Authentication procedure, which will result in the generation of a
new security keyset (CK/IK). The SS transmits a SECURITY MODE COMMAND message which contains an
unexpected critical message extension. The UE shall respond by sending SECURITY MODE FAILURE message on
the DCCH. Then SS transmits a SECURITY MODE COMMAND message with IE's "Ciphering mode info" and
"Integrity protection mode info both omitted". Again the UE shall not trigger any ciphering algorithm and it shall
respond by sending SECURITY MODE FAILURE message on the DCCH. Next, the SS transmits a valid SECURITY
MODE COMMAND message which includes the correct downlink activation times and "Integrity check info" IE. Then
the UE shall check the integrity check info and shall start to configure ciphering in downlink according to the first valid
SECURITY MODE COMMAND message. The UE shall transmit a SECURITY MODE COMPLETE message which
contains the correct uplink activation times and also "Integrity check info" IE using the new integrity protection
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
565
configuration. The SS records the uplink ciphering activation time for RB 2. Next, the SS transmits UE CAPABILITY
ENQUIRY message repeatedly on the downlink DCCH using RLC-AM mode. The UE shall respond to each downlink
message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS then send UE
CAPABILITY INFORMATION CONFIRM message to the UE. This cycle repeats itself until both the uplink and
downlink ciphering activation time for RB 2 has elapsed. SS checks all uplink UE CAPABILITY INFORMATION
messages are integrity-protected by UIA algorithm, and that the messages contain the correct values for "Integrity check
info" IE. This can be verified in the SS through the reception of a correctly ciphered and integrity-protected UE
CAPABILITY INFORMATION message.
Expected sequence
UE SS
1 RRC connected state on
DCH_state.
1a AUTHENTICATION REQUEST MM message which will result
in the generation of a new
security keyset
1b AUTHENTICATION RESPONSE MM
2 SECURITY MODE COMMAND See message content.
3 SECURITY MODE FAILURE IE "Failure Cause" shall be set
to "Protocol Error" and IE
"Protocol Error Information"
shall be set to "Message
extension not comprehended".
to "invalid configuration".
6 SECURITY MODE COMMAND See specific message
contents.
7 Void
8 Void
9 SECURITY MODE COMPLETE SS verifies that this message
is sent using the old ciphering
configuration. SS records the
uplink ciphering activation time
for RB 2.
10 UE CAPABILITY ENQUIRY SS repeats step 10, 11 and 12
until its internal uplink and
downlink RLC SN have both
surpassed the uplink and
downlink ciphering activation
time specified for RB2. This
message is sent on the
downlink DCCH using RLC-
AM.
11 UE CAPABILITY INFORMATION UE shall send this message
on the uplink DCCH using
RLC-AM. SS verifies that the
last UE CAPABILITY
INFORMATION message is
both integrity-protected and
ciphered correctly.
12 UE CAPABILITY INFORMATION CONFIRM

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
566
SECURITY MODE COMMAND (Step 2)
Message authentication code Calculated result in SS. The first/ leftmost bit of the bit
string contains the most significant bit of the MAC-I.
RRC Message sequence number Next RRC SN

SECURITY MODE FAILURE (Step 3)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH, with the exception
Failure cause
Failure cause Protocol error

RRC transaction identifier 0
Security Capability Same as originally sent by UE (and stored in SS)
Ciphering mode info Not Present
- Ciphering mode command
Integrity protection mode info Not Present
CN domain identity CS Domain

The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH, with the exception
Failure cause

Failure cause Invalid configuration

See notes below for the value of Y.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
567
RRC transaction identifier X
Ciphering mode info
Ciphering mode command Start/restart
Ciphering algorithm UEA1
Activation time for DPCH (256+CFN-(CFN MOD 8 +8))MOD 256
Radio bearer downlink ciphering activation time info
RB Identity 1
RLC sequence number Current RLC SN +Y
RB Identity 2
RLC sequence number Current RLC SN +4
RB Identity 3
RB Identity 4
Integrity protection mode command Modify
Downlink integrity protection activation info
Current RRC SN for SRB0 +2
Integrity protection algorithm UIA1

Note X =0 (Step 6), and Y=1 (Step 6)
SECURITY MODE COMPLETE (Step 9)
- Message Authentication code Checked to see if present. The first/ leftmost bit of the
bit string contains the most significant bit of the MAC-I.
- RRC Message sequence number Checked to see if present
Uplink integrity protection activation info
- RRC message sequence number list Check to see if the RRC SN for RB 0 to RB 4 are
present
Radio bearer uplink ciphering activation info
- RB Identity other than RB2 Check to see if the RLC SN for RB1, 3 and 4 are
present
- RB Identity 2
- RLC sequence number SS records this value. See step 10 in 'expected
sequence'

After step 2 the UE shall transmit a SECURITY MODE FAILURE message to report the protocol error detected in the
first SECURITY MODE COMMAND message.
After step 4 the UE shall transmit a SECURITY MODE FAILURE message to report on the invalid configuration
detected in the second SECURITY MODE COMMAND message.
After step 8 the SS checks that the SECURITY MODE COMPLETE message is received ciphered using the old
configuration and that the calculated "integrity check info" IE is correct.
After step 9 SS verifies that all uplink signalling messages on RB2 are integrity protected with UIA1 algorithm.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
568
After uplink ciphering activation time has lapsed, SS verifies that the UE CAPABILITY INFORMATION message
received is integrity protected with UIA algorithm and ciphered with the new ciphering configuration and algorithm
indicated in the SECURITY MODE COMMAND (Step 6) message.
After downlink ciphering activation time has lapsed, SS shall apply ciphering to all downlink messages using the new
configuration. At least one more cycle between step 10 and step 12 shall be repeated correctly after activation time on
both directions has lapsed and the messages on both direction shall be ciphered and integrity protected..
8.1.7.1b Security mode command in CELL_DCH state (PS Domain)
8.1.7.1b.1 Definition

8.1.7.1b.2 Conformance requirement
Upon reception of the SECURITY MODE COMMAND message, the UE shall:
1>if neither IE "Ciphering mode info" nor IE "Integrity protection mode info" is included in the SECURITY
MODE COMMAND:
2>set the variable INVALID_CONFIGURATION to TRUE.

1>prior to sending the SECURITY MODE COMPLETE message:

2>if the SECURITY MODE COMMAND message contained the IE "Integrity protection mode info":
3>include and set the IE "Uplink integrity protection activation info" to the value of the variable
INTEGRITY_PROTECTION_ACTIVATION_INFO for each signalling radio bearer;

and including the transmitted SECURITY MODE COMPLETE message;
2>transmit the SECURITY MODE COMPLETE message on the uplink DCCH in AM RLC;

If the IE "Ciphering mode info" is present and if the IE "Reconfiguration" in the variable CIPHERING_STATUS is set
to FALSE, the UE shall:

1>apply the new ciphering configuration in the lower layers for all RBs that belong to a CN domain for which the
IE "Status" of the variable SECURITY_MODIFICATION is set to "Affected" and all signalling radio bearers:
1>apply the new ciphering configuration as follows:
2>consider an activation time in downlink to be pending:

3>for AM-RLC until all AMD PDUs with sequence numbers up to and including activation time 1 have
been received;
2>if the IE "Radio bearer downlink ciphering activation time info" is present:
3>apply the following procedure for each radio bearer and signalling radio bearers using RLC-AM or RLC-
UM indicated by the IE "RB identity":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
569

4>select an "RLC send sequence number" at which (activation) time the new ciphering configuration
shall be applied in uplink for that radio bearer according to the following:

6>set a suitable value that would ensure a minimised delay in the change to the latest security
configuration.

5>use the old ciphering configuration for the transmitted and received RLC PDUs with RLC
sequence numbers smaller than the corresponding RLC sequence numbers indicated in the IE
"Radio bearer uplink ciphering activation time info" sent to UTRAN and in the received IE "Radio
bearer downlink ciphering activation time info" received from UTRAN, respectively;
5>use the new ciphering configuration for the transmitted and received RLC PDUs with RLC
sequence numbers greater than or equal to the corresponding RLC sequence numbers indicated in
the IE "Radio bearer uplink ciphering activation time info" sent to UTRAN and in the received IE
"Radio bearer downlink ciphering activation time info" received from UTRAN, respectively;

If the IE "Integrity protection mode info" is present and if the IE "Reconfiguration" in the variable
INTEGRITY_PROTECTION_INFO is set to FALSE, the UE shall:

1>if IE "Integrity protection mode command" has the value "modify" and the IE "Status" in the variable
INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was included in SECURITY MODE
COMMAND:

2>start applying the new integrity protection configuration in the downlink at the RRC sequence number, for
each signalling radio bearer n, indicated by the entry for signalling radio bearer n in the "RRC message
sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity
protection mode info";

4>select a value of the RRC sequence number at which (activation) time the new integrity protection
configuration shall be applied in uplink for that signalling radio bearer according to the following:

6>set a suitable value that would ensure a minimised delay in the change to the latest integrity
protection configuration.

2>start applying the new integrity protection configuration in the uplink at the RRC sequence number, for each
RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the "RRC
message sequence number list" in the IE "Uplink integrity protection activation info", included in the variable
INTEGRITY_PROTECTION_ACTIVATION_INFO;
2>start applying the new integrity protection configuration in the uplink at the RRC sequence number for
signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration;
each RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the
"RRC message sequence number list" in the IE "Downlink integrity protection activation info";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
570
NOTE: For signalling radio bearers that have a pending activation time as set for integrity protection by a
previous procedure changing the integrity protection configuration, UTRAN should set this value in IE
"Downlink integrity protection activation info".
2>start applying the new integrity protection configuration in the downlink at the RRC sequence number for
signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration.
Reference
3GPP TS 25.331 clauses 8.1.12.3, 8.6.3.4, 8.6.3.5.
8.1.7.1b.3 Test purpose
To confirm that the UE modifies an integrity protection configuration and applies new keys on reception of a correct
SECURITY MODE COMMAND message.
To confirm that the UE modifies a ciphering configuration in the uplink and downlink and applies new keys according
to transmitted activation times. Also confirms that the UE accepts a new ciphering configuration for a RB when
ciphering is started for SRBs.
To confirm that after the UE receives a SECURITY MODE COMMAND message, it transmits a SECURITY MODE
COMPLETE message to the UTRAN using the old ciphering configuration and new integrity protection configuration.
To confirm that UE send SECURITY MODE FAILURE message when SS transmits a SECURITY MODE
COMMAND message with a non comprehended critical extension.
To confirm that the UE sends a SECURITY MODE FAILURE message when UE receives an invalid SECURITY
MODE COMMAND message.
8.1.7.1b.4 Method of test
Initial Condition
Test Procedure
The UE is in CELL_DCH state with integrity protection and ciphering started for SRBs. The SS initiates an
Authentication and Ciphering procedure, which will result in the generation of a new security keyset (CK/IK).
The SS transmits a SECURITY MODE COMMAND message which contains an unexpected critical message
extension. The UE shall respond by sending SECURITY MODE FAILURE message on the DCCH.
Then SS transmits a SECURITY MODE COMMAND message with IEs "Ciphering mode info" and "Integrity
protection mode info both omitted". Again the UE shall not trigger any ciphering algorithm and it shall respond by
sending SECURITY MODE FAILURE message on the DCCH.
Next, the SS transmits a valid SECURITY MODE COMMAND message which includes the correct downlink
activation times and "Integrity check info" IE. The UE shall check the integrity check info and shall start to configure
ciphering in downlink according to the SECURITY MODE COMMAND message.
Then UE shall transmit a SECURITY MODE COMPLETE message which contains uplink activation times and also
the correct "Integrity check info" IE using the new integrity protection configuration. SS records the uplink ciphering
activation time for RB 2.
Next, the SS transmits UE CAPABILITY ENQUIRY message repeatedly on the downlink DCCH using RLC-AM
mode. The UE shall respond to each downlink message with a UE CAPABILITY INFORMATION message on the
uplink DCCH using RLC-AM. SS shall send UE CAPABILITY INFORMATION CONFIRM messages to the UE for
each received UE CAPABILITY INFORMATION message from the UE.
This cycle repeats itself until both the uplink and downlink ciphering activation time for RB 2 has elapsed. SS checks
all uplink UE CAPABILITY INFORMATION messages are integrity-protected by UIA algorithm, and that the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
571
messages contain the correct values for "Integrity check info" IE. This can be verified in the SS through the reception of
a correctly ciphered and integrity-protected UE CAPABILITY INFORMATION message.
Expected sequence
UE SS
1 RRC connected state on
DCH_state.
1a AUTHENTICATION AND CIPHERING
REQUEST
GMM message which will
result in the generation of a
new security keyset
1b AUTHENTICATION AND CIPHERING
RESPONSE
GMM
to "invalid configuration".
contents.
configuration and with the new
integrity protection
for RB 2.
8 UE CAPABILITY ENQUIRY SS repeats step 8, 9 and 10
AM.
last UE CAPABILITY
ciphered correctly.


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
572
Message content is the same as found in Clause 9 of TS 34.108, with the exception of the following IEs:
Failure cause
Failure cause Protocol error

CN domain identity PS Domain

Message content is the same as found in Clause 9 of TS 34.108, with the exception of the following IEs:
Failure cause


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
573
SECURITY MODE COMMAND (Step 6 )
Ciphering mode info
Activation time for DPCH Not Present
RB Identity 1
RLC sequence number Current RLC SN
RB Identity 2
RB Identity 3
RB Identity 4
RB Identity 20
Current RRC SN for SRB0
0

NOTE: "Current RLC SN" is defined as the value of VT(S) in the SS at the time when the SECURITY MODE
COMMAND is submitted to RLC for transmission, that is, the RLC send sequence number of the next
transmitted RLC PDU on the particular radio bearer. "Current RRC SN" is defined as the RRC message
sequence number of the next transmitted RRC message on the particular radio bearer.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
574
- Message Authentication code This IE is checked to see if it is present. The value is
- RRC message sequence number list
-RRC message sequence number Check to see if the RRC SN for RB 0 is present
Radio bearer uplink ciphering activation time info
- RB Identity 1
- RLC sequence number Check to see if the RLC SN for RB1is present
- RB Identity 2
sequence'
- RB Identity 3
- RLC sequence number Check to see if the RLC SN for RB3 is present
- RB Identity 4
- RB Identity 20

8.1.7.1b.5 Test requirement
After step 4 the UE shall transmit a SECURITY MODE FAILURE message to report on the invalid configuration
detected in the second SECURITY MODE COMMAND message.
At step 7 SS checks that the SECURITY MODE COMPLETE message is received ciphered using the old configuration
and that the calculated "integrity check info" IE is correct according to the new integrity protection configuration (new
key and HFN set to zero).
After step 7 SS verifies that all uplink signalling messages on RB2 are integrity protected with the new integrity
protection configuration.
After uplink ciphering activation time has elapsed, SS verifies that the UE CAPABILITY INFORMATION message
received is ciphered with the new ciphering configuration asindicated in the SECURITY MODE COMMAND (Step 6)
message.
After downlink ciphering activation time has elapsed, SS shall apply ciphering to all downlink messages using the new
ciphering configuration. At least one more cycle between step 8 and step 10 shall be repeated correctly after activation
time on both directions has elapsed and the messages on both direction shall be ciphered and integrity protected.
8.1.7.1c Security mode control in CELL_DCH state (CN Domain switch and new keys
at RRC message sequence number wrap around)
8.1.7.1c.1 Definition

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
575
8.1.7.1c.2 Conformance requirement
Upon reception of the SECURITY MODE COMMAND message, the UE shall:

2>set the variable LATEST_CONFIGURED_CN_DOMAIN equal to the IE "CN domain identity";
2>set the IE "Status" in the variable SECURITY_MODIFICATION for the CN domain indicated in the IE "CN
domain identity" in the received SECURITY MODE COMMAND to the value "Affected";

If a new security key set (new ciphering and integrity protection keys) has been received from the upper layers [40] for
the CN domain as indicated in the variable LATEST_CONFIGURED_CN_DOMAIN, the UE shall:
1>set the START value for the CN domain indicated in the variable LATEST_CONFIGURED_CN_DOMAIN to
zero;
2>for integrity protection in the downlink on each signalling radio bearer except RB2:
3>if IE "Integrity protection mode command" has the value "start":

3>else:
4>for the first message for which the RRC sequence number in a received RRC message for this
signalling radio bearer is equal to or greater than the activation time as indicated in IE "Downlink
integrity protection activation info" as included in the IE "Integrity protection mode info":
5>start using the new integrity key;
5>for this signalling radio bearer:
6>set the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the
downlink COUNT-I to zero.
2>for integrity protection in the uplink on each signalling radio bearer except RB2:
3>for the first message for which the RRC sequence number in a to be transmitted RRC message for this
signalling radio bearer is equal to the activation time as indicated in IE "Uplink integrity protection
activation info" included in the transmitted SECURITY MODE COMPLETE message:
4>for this signalling radio bearer:
5>set the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink
COUNT-I to zero.
2>for integrity protection in the downlink on signalling radio bearer RB2:
3>at the received SECURITY MODECOMMAND:
4>set the IE "Downlink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the downlink
COUNT-I to zero.
2>for integrity protection in the uplink on signalling radio bearer RB2 :
3>at the transmitted SECURITY MODE COMPLETE:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
576
4>set the IE "Uplink RRC HFN" in the variable INTEGRITY_PROTECTION_INFO of the uplink
COUNT-I to zero.
1>if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info":
2>for each signalling radio bearer and for each radio bearer for the CN domain indicated in the variable
LATEST_CONFIGURED_CN_DOMAIN:
3>if the IE "Status" in the variable CIPHERING_STATUS has the value "Started" for this CN domain, then
for ciphering on radio bearers using RLC-TM:
4>at the CFN as indicated in the IE "Ciphering activation time for DPCH" in the IE "Ciphering mode
info":
5>start using the new key in uplink and downlink;
5>set the HFN component of the COUNT-C to zero.
3>if the IE "Status" in the variable CIPHERING_STATUS has the value "Started" for this CN domain, then
for ciphering on radio bearers and signalling radio bearers using RLC-AM and RLC-UM:
4>in the downlink, at the RLC sequence number indicated in IE "Radio bearer downlink ciphering
activation time info" in the IE "Ciphering mode info":
5>start using the new key;
5>set the HFN component of the downlink COUNT-C to zero.
4>in the uplink, at the RLC sequence number indicated in IE "Radio bearer uplink ciphering activation
time info":
5>start using the new key;
5>set the HFN component of the uplink COUNT-C to zero.
1>consider the value of the latest transmitted START value to be zero.

1>apply the new ciphering configuration in the lower layers for all RBs that belong to a CN domain for which the
IE "Status" of the variable SECURITY_MODIFICATION is set to "Affected" and all signalling radio bearers:
2>using the ciphering algorithm (UEA [40]) indicated by the IE "Ciphering algorithm" as part of the new
ciphering configuration;
2>for each radio bearer that belongs to a CN domain for which the IE "Status" of the variable
SECURITY_MODIFICATION is set to "Affected" and all signalling radio bearers:
3>using the value of the IE "RB identity" in the variable ESTABLISHED_RABS minus one as the value of
BEARER [40] in the ciphering algorithm.

If the IE "Integrity protection mode info" is present and if the IE "Reconfiguration" in the variable
INTEGRITY_PROTECTION_INFO is set to FALSE, the UE shall:
1>set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to TRUE;
1>if IE "Integrity protection mode command" has the value "modify" and the IE "Status" in the variable
INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was included in SECURITY MODE
COMMAND:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
577
each signalling radio bearer n, indicated by the entry for signalling radio bearer n in the "RRC message
sequence number list" in the IE "Downlink integrity protection activation info", included in the IE "Integrity
protection mode info";
2>set the content of the variable INTEGRITY_PROTECTION_ACTIVATION_INFO according to the
following:

2>start applying the new integrity protection configuration in the uplink at the RRC sequence number, for each
RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the "RRC
message sequence number list" in the IE "Uplink integrity protection activation info", included in the variable
INTEGRITY_PROTECTION_ACTIVATION_INFO;
2>start applying the new integrity protection configuration in the uplink at the RRC sequence number for
signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration;
each RBn, except for signalling radio bearer RB2, indicated by the entry for signalling radio bearer n in the
"RRC message sequence number list" in the IE "Downlink integrity protection activation info";
2>start applying the new integrity protection configuration in the downlink at the RRC sequence number for
signalling radio bearer RB2, as specified for the procedure initiating the integrity protection reconfiguration.
Reference
3GPP TS 25.331 clauses 8.1.12.3, 8.6.3.4, 8.6.3.5.
8.1.7.1c.3 Test purpose
To verify that the UE correctly modifies the integrity protection and ciphering configuration with a newly generated PS
domain keyset for when previously using the CS domain keyset.
To verify that the UE can handle change of integrity protection key when the RRC message sequence number wraps
around when the SECURITY MODE COMMAND is received.
8.1.7.1c.4 Method of test
Initial Condition
UE: has entered PS+CS-DCCH+DTCH_DCH (state 6-14) using procedure P19 as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state.
The SS transmits UE CAPABILITY ENQUIRY message repeatedly on the downlink DCCH using RLC-UM mode on
SRB1. The UE shall respond to each downlink message with a UE CAPABILITY INFORMATION message on the
uplink DCCH using RLC-AM. SS then send UE CAPABILITY INFORMATION CONFIRM message to the UE. This
procedure is repeated until the RRC message sequence number for SRB 1 in downlink equals 15.
The SS initiates an Authentication procedure, which will result in the generation of a new security keyset (CK/IK). The
SS transmits a valid SECURITY MODE COMMAND message which includes the correct downlink activation times
and "Integrity check info" IE.
Then the UE shall check the integrity check info and shall start to configure ciphering in downlink according to the first
valid SECURITY MODE COMMAND message. The UE shall transmit a SECURITY MODE COMPLETE message
which contains the correct uplink activation times and also "Integrity check info" IE using the new integrity protection
configuration.
The SS records the uplink ciphering activation time for RB 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
578
Next, the SS transmits UE CAPABILITY ENQUIRY message repeatedly on the downlink DCCH using RLC-AM
mode. The UE shall respond to each downlink message with a UE CAPABILITY INFORMATION message on the
uplink DCCH using RLC-AM. SS then send UE CAPABILITY INFORMATION CONFIRM message to the UE. This
cycle repeats itself until both the uplink and downlink ciphering activation time for RB 2 has elapsed. SS checks all
uplink UE CAPABILITY INFORMATION messages are integrity-protected by UIA algorithm, and that the messages
contain the correct values for "Integrity check info" IE. This can be verified in the SS through the reception of a
correctly ciphered and integrity-protected UE CAPABILITY INFORMATION message.
The SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-UM mode on SRB1. The
UE shall respond to this message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-
AM. SS then send UE CAPABILITY INFORMATION CONFIRM message to the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
579
Expected sequence
UE SS
1 The UE is in CELL_DCH state.
2 UE CAPABILITY ENQUIRY The SS repeats step 2, 3 and
4 until its internal downlink
RRC message sequence
number for RB 2 has the
value 15.
3 UE CAPABILITY INFORMATION The UE shall send this
message on the uplink DCCH
using RLC-AM. SS verifies
that the last UE CAPABILITY
ciphered correctly.
5 AUTHENTICATION and CIPHERING
REQUEST
new security keyset
6 AUTHENTICATION AND CIPHERING
RESPONSE
GMM
contents.
8 SECURITY MODE COMPLETE The SS verifies that this
message is sent using the old
ciphering configuration. SS
records the uplink ciphering
activation time for RB 2.
9 UE CAPABILITY ENQUIRY The SS repeats step 9, 10 and
11 until its internal uplink and
AM.
ciphered correctly.
12 UE CAPABILITY ENQUIRY The SS sends this message
with the downlink RRC
message sequence number
for SRB 1 with the value 0.
ciphered correctly.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
580
Ciphering mode info
Activation time for DPCH (256+CFN-(CFN MOD 8 +8))MOD 256
RB Identity 1
RB Identity 2
RB Identity 3
RB Identity 4
RB Identity 20
0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
581
- Message Authentication code This IE is checked to see if it is present. The value is
- RRC message sequence number list Check to see if the RRC SN for RB 0 to RB 4 are
present
Radio bearer uplink ciphering activation time info
- RB Identity 1
- RB Identity 2
sequence'
- RB Identity 3
- RB Identity 4
- RB Identity 20

8.1.7.1c.5 Test requirement
configuration and that the calculated "integrity check info" IE is correct.
both directions has lapsed and the messages on both direction shall be ciphered and integrity protected..
8.1.7.1d Security mode control in CELL_DCH state interrupted by a cell update
8.1.7.1d.1 Definition

8.1.7.1d.2 Conformance requirement
If:
- a cell update procedure according to subclause 8.3.1 is initiated; and
- the received SECURITY MODE COMMAND message causes either,
- the IE "Reconfiguration" in the variable CIPHERING_STATUS to be set to TRUE; and/or
- the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to be set to TRUE:
the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
582
1>abort the ongoing integrity and/or ciphering reconfiguration;
1>resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or
RLC-UM;
1>allow the transmission of RRC messages on all signalling radio bearers with any RRC SN;
1>when the response message has been submitted to lower layers for transmission:
2>if the SECURITY MODE COMMAND message contained the IE "Ciphering mode info":
3>set the IE "Reconfiguration" in the variable CIPHERING_STATUS to FALSE; and
3>clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO;
3>set the IE "Reconfiguration" in the variable INTEGRITY_PROTECTION_INFO to FALSE; and
3>clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO.
2>continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND
message has not been received; and
2>clear the variable SECURITY_MODIFICATION;
Reference
3GPP TS 25.331 clause 8.1.12.4b,
8.1.7.1d.3 Test purpose
To confirm that the UE aborts the ongoing integrity and ciphering configuration and the security mode control
procedure in case it is interrupted by a cell update procedure.
8.1.7.1d.4 Method of test
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS initiates an Authentication and Ciphering procedure, which will result in the
generation of a new security keyset (CK/IK).
The SS transmits a valid SECURITY MODE COMMAND message which includes the correct downlink activation
times and "Integrity check info" IE..
Then SS immediately turnes of the power in the cell, so the UE will initiate the cell reselection procedure.
The UE shall then abort the Security procedure.
Then after 6 seconds the power in turned on in the cell again.
Next, the SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM mode. The UE
shall respond to with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM using the
same old integrity and ciphierring configutation as used before the SECURITY MODE COMMAND was received...
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
583
Expected sequence
UE SS
1 The UE is in CELL_DCH state.
REQUEST
new security keyset
RESPONSE
GMM
contents.
5 When the RLC ack is received
from the UE, the SS turns off
power in the cell.
6 The UE starts cell selection
7 After waiting for 6 seconds,
the SS turns on power in the
cell.
8 CELL UPDATE This message includes the
value "Radio link failure" set in
IE "Cell update cause". The
SS verifies that message is
integrity-protected correctly
with the old security
configuration
9 CELL UPDATE CONFIRM This message includes
"Physical channel information
elements".
10 PHYSICAL CHANNEL
The UE shall send this
that message is both integrity-
protected and ciphered
correctly with the old security
configuration
11 UE CAPABILITY ENQUIRY The SS repeats step 11, 12
and 13 until its internal uplink
and downlink RLC SN have
both surpassed the uplink and
AM.
ciphered correctly.

SECURITY MODE COMMAND (Step 4 )
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
584
Ciphering mode info
RB Identity 1
RB Identity 2
RB Identity 3
RB Identity 4
RB Identity 20
0

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in clause 9 of
TS 34.108 Annex A with the following exceptions:
U-RNTI
- SRNC Identity Check to see if set to '0000 0000 0001'
- S-RNTI Check to see if set to '0000 0000 0000 0000 0000 0001'
Cell Update Cause "Radio link failure"

CELL UPDATE CONFIRM (Step 9) (FDD)
in Annex A with the following exceptions:
CHOICE channel requirement Uplink DPCH info
-UplinkDPCH Info Same as RADIO BEARER SETUP message used to
move to intial condition
Downlink information common for all radio links Same as RRC CONNECTION SETUP message used to
move to initial condition
Downlink information for each radio links Same as RADIO BEARER SETUP message used to

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
585
CELL UPDATE CONFIRM (Step 9) (TDD)
in clause 9 of TS 34.108 Annex A with the following exceptions:
UplinkDPCH timeslots and codes Same as RADIO BEARER SETUP message used to

8.1.7.1d.5 Test requirement
received at step 12 is integrity protected with UIA algorithm and ciphered with the old ciphering configuration and
algorithm and not the one indicated in the SECURITY MODE COMMAND (Step 4) message.
8.1.7.2 Security mode command in CELL_FACH state

1. This procedure is used to trigger the start of ciphering, or to command the restart of ciphering with the new
ciphering configuration for the signalling radio bearers and any radio bearers of a particular CN Domain. It is
also used to start integrity protection or modify integrity protection configuration for signalling radio bearers.
2. When the UE receives a SECURITY MODE COMMAND message from the UTRAN, which indicates the
downlink activation time for each effected SRB and RB, and new ciphering mode configuration, the UE shall
apply the old ciphering configuration, for a particular SRB or RB, before the stated downlink activation time. It
shall start to decipher using the new ciphering configuration at the downlink activation time.
3. The UE shall transmit SECURITY MODE COMPLETE message using the new integrity protection
configuration stated in the received SECURITY MODE COMMAND message. The SECURITY MODE
COMPLETE message shall include the ciphering uplink activation time. The UE shall start to apply the new
ciphering configuration on the uplink direction, after the uplink activation time has elapsed respectively for each
SRB or RB.
Reference
3GPP TS 25.331 clauses 8.1.12, 8.6.3.4, 8.6.3.5.
To confirm that after the UE receives a SECURITY MODE COMMAND message, it transmits a SECURITY MODE
COMPLETE message to the UTRAN using the old ciphering configuration together with the application of the new
integrity protection configuration. To confirm that the UE applies the old ciphering configuration in the downlink prior
to the activation time; and uses the new ciphering configuration on and after the activation time. To confirm that the UE
starts to cipher its uplink transmissions after the uplink activation time stated in SECURITY MODE COMPLETE
message is reached. To confirm that the UE sends a SECURITY MODE FAILURE message when the UE receives an
invalid SECURITY MODE COMMAND message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
586
UE: CELL_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state. The SS initiates an Authentication and Ciphering procedure, which will result in the
generation of a new security keyset (CK/IK). The SS transmits a SECURITY MODE COMMAND message which
contains an unexpected critical message extension. The UE shall respond by sending SECURITY MODE FAILURE
message on the DCCH. Next, SS transmits a valid SECURITY MODE COMMAND message which includes the
correct downlink activation times and IE "Integrity check info". The UE shall check the integrity check info. It shall
start to configure ciphering in downlink and transmit a SECURITY MODE COMPLETE message, which contains the
correct uplink activation times using the new integrity protection configuration. This message shall contain the IE
"Integrity check info". SS records the uplink ciphering activation time for RB 2. Next, SS transmits UE CAPABILITY
ENQUIRY message repeatedly on the downlink DCCH using RLC-AM mode. The UE shall respond to each downlink
message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS checks all
uplink messages are integrity-protected by UIA1 algorithm, and that the messages contain the correct values for
"Integrity check info" IE by sending a UE CAPABILITY INFORMATION CONFIRM. This cycle repeats itself until
both the uplink and downlink ciphering activation time for RB 2 have elapsed. After both the uplink and downlink
ciphering activation time for RB 2 have passed, the UE shall be able to communicate with the SS using the new
ciphering configurations. This can be verified in SS through the reception of a correctly ciphered and integrity-protected
UE CAPABILITY INFORMATION message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
587
Expected sequence
UE SS
1 UE is initially in CELL_FACH
state.
1a AUTHENTICATION AND CIPHERING
REQUEST
new security keyset
1b AUTHENTICATION AND CIPHERING
RESPONSE
GMM
2 SECURITY MODE COMMAND See specific message content
4 Void
5 Void
6 Void
7 Void
contents.
for RB 2.
10 UE CAPABILITY ENQUIRY SS repeats step 10,11 and 12
AM.
last UE CAPABILITY
ciphered correctly.


See notes below for the value of Y.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
588
Ciphering mode info
RB Identity 1
RB Identity 2
RB Identity 3
RB Identity 4
RB Identity 20
Y=1 (Step 8)
- Message Authentication code Checked to see if present. The first/ leftmost bit of the
bit string contains the most significant bit of the MAC-I.
- RRC Message sequence number Checked to see if present
- RRC message sequence number list Check to see if it the RRC SN for RB 0 to RB 4 are
present
Radio bearer uplink ciphering activation info
- RB Identity other than RB2 Check to see if the RLC SN for RB1, 3 and 4 are
present
- RB Identity 2
sequence'

configuration and that the calculated MAC-I values in "integrity check info" IE is correct.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
589
both directions has lapsed and the messages on both directions shall be ciphered and integrity protected.
8.1.8 Counter check
8.1.8.1 Counter check in CELL_DCH state, with symmetric RAB
When the UE receives a COUNTER CHECK message it shall compare the COUNT-C MSB values received in the IE
"RB COUNT-C MSB information" in the COUNTER CHECK message to the COUNT-C MSB values of the
corresponding radio bearers.
The UE shall:
1>set the IE "RRC transaction identifier" in the COUNTER CHECK RESPONSE message to the value of "RRC
transaction identifier" in the entry for the COUNTER CHECK message in the table "Accepted transactions" in
the variable TRANSACTIONS; and
1>clear that entry.
If:
- there is one or more radio bearer(s) using UM or AM RLC mode stored in the variable ESTABLISHED_RABS,
which is (are) not included in the IE "RB COUNT-C MSB information"; or
- there is one or more radio bearer(s) included in the IE "RB COUNT-C MSB information", which is (are) not
stored in the variable ESTABLISHED_RABS; or
- for any radio bearer (excluding signalling radio bearers) using UM or AM RLC mode stored in the variable
ESTABLISHED_RABS and included in the IE "RB COUNT-C MSB information" with COUNT-C MSB values
different from the MSB part of the COUNT-C values in the UE:
the UE shall:
1>include these radio bearers in the IE "RB COUNT-C information" in the COUNTER CHECK RESPONSE
message. For any RB which is included in the IE "RB COUNT-C MSB information" in the COUNTER CHECK
message but not stored in the variable ESTABLISHED_RABS in the UE, the MSB part of COUNT-C values in
the COUNTER CHECK RESPONSE message shall be set identical to COUNT-C-MSB values in the
COUNTER CHECK message. The LSB part shall be filled with zeroes.
The UE shall:
1>submit a COUNTER CHECK RESPONSE message to lower layers for transmission on the uplink DCCH using
AM RLC.
When the COUNTER CHECK RESPONSE message has been submitted to lower layers for transmission the procedure
ends.
If the UE receives a COUNTER CHECK message, which contains a protocol error causing the variable
specific error handling as follows. The UE shall:
1>set the IE "Received message type" to COUNTER CHECK; and
COUNTER CHECK message in the table "Rejected transactions" in the variable TRANSACTIONS; and
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
590
1>clear that entry;
2>continue with any ongoing processes and procedures as if the invalid COUNTER CHECK message has not
been received.
Reference
3GPP TS 25.331 clause 8.1.15.
To confirm that the UE transmits a COUNTER CHECK RESPONSE message after it receives a COUNTER CHECK
message from the SS. To confirm that the UE responds to the reception of an invalid downlink COUNTER CHECK
message by transmitting a RRC STATUS message on the uplink DCCH, stating the correct error cause value in
message.
Initial Condition
UE: PS-DCCH+DTCH_DCH state (state 6-10) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to the CELL_DCH state after a successful outgoing call attempt. The SS transmits an invalid
COUNTER CHECK message. This message contains an unexpected critical message extension. The UE shall detect a
protocol error and send RRC STATUS message to report this event. Next, the SS transmits a COUNTER CHECK
message that includes the current COUNT-C MSB information in each radio access bearer. The UE shall react by
sending a COUNTER CHECK RESPONSE message on the uplink DCCH, which does not include "RB COUNT-C
information" IE. The SS transmits a COUNTER CHECK message which includes the current COUNT-C MSB
information reversed all the bits in each radio bearer. The UE shall send a COUNTER CHECK RESPONSE message
on the uplink DCCH, specifying the current COUNT-C information for each radio access bearer established. The SS
transmits a COUNTER CHECK message which includes a different radio bearer. The UE shall send a COUNTER
CHECK RESPONSE message on the uplink DCCH, specifying the current COUNT-C information for each radio
access bearer established.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
591
Expected sequence
UE SS
2 COUNTER CHECK See specific message
3 RRC STATUS UE shall detect a protocol
error and then transmit
this message.
content.
5 COUNTER CHECK RESPONSE The message shall not
include the IE "RB
COUNT-C information".
content.
7 COUNTER CHECK RESPONSE The message shall
include the IE "RB
content.
include the IE "RB

COUNTER CHECK (Step 2)

RRC STATUS (Step 3)
Use the same message type found in Annex A, with the following exception.


Message Type
RB COUNT-C MSB information
- RB identity 20
- COUNT-C MSB uplink Current COUNT-C MSB for RB#20 in uplink
- COUNT-C MSB downlink Current COUNT-C MSB for RB#20 in downlink

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
592
COUNTER CHECK RESPONSE (Step 5)
Message Type
Integrity check info Not checked
RB COUNT-C information Check to if this IE is absent

Message Type
- RB identity Check to see if set to 20
- COUNT-C MSB uplink Toggle all bits of the current COUNT-C MSB in uplink
for RB#20
- COUNT-C MSB downlink Toggle all bits of the current COUNT-C MSB in downlink
for RB#20

Message Type
RB COUNT-C information
- COUNT-C uplink Check to see if set to Current COUNT-C for RB#20 in
uplink
- COUNT-C downlink Check to see if set to COUNT-C for RB#20 in downlink

Message Type
- COUNT-C MSB uplink Arbitrary COUNT-C MSB in uplink for RB#25
- COUNT-C MSB downlink Arbitrary COUNT-C MSB in downlink for RB#25

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
593
Message Type
uplink
- COUNT-C uplink Check to see if COUNT-C MSB is set to COUNT-C
MSB in uplink for RB#25 in step 8 and LSB is fill with '0'
- COUNT-C downlink Check to see if COUNT-C MSB is set to COUNT-C
MSB in downlink for RB#25 in step 8 and LSB is fill with
'0'

to "Message extension not comprehended".
After step 4 the UE shall transmit a COUNTER CHECK RESPONSE message which does not includes the IE "RB
COUNT-C information" to indicates that a matched comparison result is obtained.
After step 6, the UE shall transmit a COUNTER CHECK RESPONSE message which includes the IE "RB COUNT-C
information" to report that a mismatch in COUNT-C value is detected in RB#20.
information" to report that RB#25 is not found in variable ESTABLISHED_RABS and RB#20 is not found in IE "RB
COUNT-C MSB information".
8.1.8.2 Counter check in CELL_FACH state

The UE shall:
1>set the IE "RRC transaction identifier" in the COUNTER CHECK RESPONSE message to the value of "RRC
transaction identifier" in the entry for the COUNTER CHECK message in the table "Accepted transactions" in
the variable TRANSACTIONS; and
1>clear that entry.
If:
- there is one or more radio bearer(s) using UM or AM RLC mode stored in the variable ESTABLISHED_RABS,
which is (are) not included in the IE "RB COUNT-C MSB information"; or
- there is one or more radio bearer(s) included in the IE "RB COUNT-C MSB information", which is (are) not
stored in the variable ESTABLISHED_RABS; or
- for any radio bearer (excluding signalling radio bearers) using UM or AM RLC mode stored in the variable
ESTABLISHED_RABS and included in the IE "RB COUNT-C MSB information" with COUNT-C MSB values
different from the MSB part of the COUNT-C values in the UE:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
594
the UE shall:
1>include these radio bearers in the IE "RB COUNT-C information" in the COUNTER CHECK RESPONSE
message. For any RB which is included in the IE "RB COUNT-C MSB information" in the COUNTER CHECK
message but not stored in the variable ESTABLISHED_RABS in the UE, the MSB part of COUNT-C values in
the COUNTER CHECK RESPONSE message shall be set identical to COUNT-C-MSB values in the
COUNTER CHECK message. The LSB part shall be filled with zeroes.
The UE shall:
AM RLC.
When the COUNTER CHECK RESPONSE message has been submitted to lower layers for transmission the procedure
ends.
If the UE receives a COUNTER CHECK message, which contains a protocol error causing the variable
1>set the IE "Received message type" to COUNTER CHECK; and
COUNTER CHECK message in the table "Rejected transactions" in the variable TRANSACTIONS; and
1>clear that entry;
2>continue with any ongoing processes and procedures as if the invalid COUNTER CHECK message has not
been received.
Reference
3GPP TS 25.331 clause 8.1.15.
To confirm that the UE transmits a COUNTER CHECK RESPONSE message after it receives a COUNTER CHECK
message from the SS. To confirm that the UE responds to the reception of an invalid downlink COUNTER CHECK
message by transmitting a RRC STATUS message on the uplink DCCH, stating the correct error cause value in
message.
Initial Condition
UE: PS-DCCH+DTCH_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to the CELL_FACH state after a successful outgoing call attempt. The SS transmits an invalid
COUNTER CHECK message. This message contains an unexpected critical message extension. The UE shall detect a
protocol error and send RRC STATUS message to report this event. Next, the SS transmits a COUNTER CHECK
message that includes the current COUNT-C MSB information in each radio access bearer. The UE shall react by
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
595
sending a COUNTER CHECK RESPONSE message on the uplink DCCH, which does not include "RB COUNT-C
information" IE. The SS transmits a COUNTER CHECK message, which includes the current COUNT-C MSB
information for each radio bearer but with all the bits reversed. The UE shall send a COUNTER CHECK RESPONSE
message on the uplink DCCH, specifying the current COUNT-C information for each radio access bearer established.
The SS transmits a COUNTER CHECK message which includes a different radio bearer. The UE shall send a
COUNTER CHECK RESPONSE message on the uplink DCCH, specifying the current COUNT-C information for each
radio access bearer established.
Expected sequence
UE SS
CELL_FACH state after
an outgoing call has been
3 RRC STATUS UE shall detect a protocol
error and then transmit
this message.
content.
5 COUNTER CHECK RESPONSE The message shall not
include the IE "RB
content.
include the IE "RB
content.
include the IE "RB


RRC STATUS (Step 3)
Message Type


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
596
Message Type
- RB identity 20
- COUNT-C MSB uplink Current COUNT-C MSB for RB#20 in uplink
- COUNT-C MSB downlink Current COUNT-C MSB for RB#20 in downlink

Message Type
RB COUNT-C information Check to if this IE is absent

Message Type
- RB identity 20
- COUNT-C MSB uplink Toggle all bits of the current COUNT-C MSB in uplink
for RB#20
- COUNT-C MSB downlink Toggle all bits of the current COUNT-C MSB in downlink
for RB#20

Message Type
uplink

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
597
Message Type
- COUNT-C MSB uplink Arbitrary COUNT-C MSB in uplink for RB#25
- COUNT-C MSB downlink Arbitrary COUNT-C MSB in downlink for RB#25

uplink
- COUNT-C uplink Check to see if COUNT-C MSB is set to COUNT-C
MSB in uplink for RB#25 in step 8 and LSB is fill with '0'
- COUNT-C downlink Check to see if COUNT-C MSB is set to COUNT-C
MSB in downlink for RB#25 in step 8 and LSB is fill with
'0'

to "Message extension not comprehended".
After step 4 the UE shall transmit a COUNTER CHECK RESPONSE message which does not includes the IE "RB
COUNT-C information" to indicates that a matched comparison result is obtained.
information" to report that a mismatch in COUNT-C value is detected in RB#20.
information" to report that RB#25 is not found in variable ESTABLISHED_RABS and RB#20 is not found in IE "RB
COUNT-C MSB information".
8.1.8.3 Counter check in CELL_DCH state, with asymmetric RAB

The UE shall:
1>if no COUNT-C exists for a radio bearer for a given direction (uplink or downlink) because:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
598
2>it is a uni-directional radio bearer configured only for the other direction (downlink or uplink respectively),
or
2>has been configured to RLC-TM mode in one direction (uplink or downlink) and RLC-UM in the other
(downlink or uplink respectively),
3>set the COUNT-C in the IE "RB COUNT-C information" in the COUNTER CHECK RESPONSE
message, to any value;
AM RLC.
Reference
3GPP TS 25.331 clause 8.1.15.
To confirm that the UE transmits a COUNTER CHECK RESPONSE message even if COUNT-C does not exist for a
radio bearer for a given direction for reasons given in the above section.
Initial Condition
UE: CS-DCCH_DCH (state 6-5) or PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108, depending on
the domain supported by the UE.
Test Procedure
The UE is brought to the CELL_DCH state after a successful outgoing call attempt. SS sends a RADIO BEARER
SETUP message to set up an asymmetric radio bearer. UE shall configure accordingly and then reply with a RADIO
BEARER SETUP COMPLETE message. Then SS transmits a COUNTER CHECK message. The UE shall send a
COUNTER CHECK RESPONSE message on the uplink DCCH.
Expected sequence
UE SS
2 RADIO BEARER SETUP See specific message
content.
include the IE "RB

RADIO BEARER SETUP (Step 2) (FDD)
The contents of RADIO BEARER SETUP message in this test case is identical to the message sub-type indicated by
"Non speech from CELL_DCH to CELL_DCH in CS" or "Speech from CELL_DCH to CELL_DCH in CS" or "Packet
to CELL_DCH from CELL_DCH in PS" in [9] TS 34.108 clause 9, with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
599
- RAB info
- RAB identity 0000 0101B (for PS domain) or 0000 0001B (for CS
domain)
significant bit of the RAB identity.
- CN domain identity PS domain or CS domain (depending on the domain
supported by the UE)
- Re-establishment timer UseT315 (for PS domain) or UseT314 (for CS domain)
- RB identity 9
- PDCP info
- Support for lossless SRNS relocation FALSE
- Max PDCP SN window size Not present
- PDCP PDU header Absent
- CHOICE Uplink RLC mode TM RLC
- CHOICE SDU discard mode Not Present
- Segmentation indication False
- CHOICE Downlink RLC mode UM RLC
- RB mapping info
Added or Reconfigured TrCH information list 1 DCH added
- Added or Reconfigured UL TrCH information
- TFS
- CHOICE Transport channel type Dedicated transport channels
- RLC Size Reference to TS34.108 clause 6.10 Parameter Set
- Number of TBs and TTI List (This IE is repeated for TFI number.)
- Transmission Time Interval Not Present
- Number of Transport blocks Reference to TS34.108 clause 6.10 Parameter Set
- CHOICE Logical Channel list All
- Transmission time interval Reference to TS34.108 clause 6.10 Parameter Set
- Type of channel coding Reference to TS34.108 clause 6.10 Parameter Set
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
600
- Coding Rate Reference to TS34.108 clause 6.10 Parameter Set
- Rate matching attribute Reference to TS34.108 clause 6.10 Parameter Set
- CRC size Reference to TS34.108 clause 6.10 Parameter Set
Added or Reconfigured TrCH information list 1 DCH
Added or Reconfigured DL TrCH information
- DL Transport channel identity 9
- CHOICE DL parameters Same as UL
- UL TrCH identity 1
- DCH quality target
- BLER Quality value -2.0

Message Type
- RB COUNT-C MSB information
- RB identity 9
- COUNT-C MSB uplink Arbitrary
- COUNT-C MSB downlink Set to current COUNT-C for RB#9 in downlink

Message Type
- COUNT-C uplink Check to see if it is present
- COUNT-C downlink Check to see if it is present

After step 2, the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the uplink
DCCH.
After step 4, the UE shall transmit a COUNTER CHECK RESPONSE message.
8.1.9 Signalling Connection Release Indication
8.1.9.1 Definition

8.1.9.2 Conformance requirement
The UE shall, on receiving a request to release (abort) the signalling connection from upper layers for a specific CN
domain:
1>if a signalling connection in the variable ESTABLISHED_SIGNALLING_CONNECTIONS for the specific CN
domain identified with the IE "CN domain identity" exists:
2>initiate the signalling connection release indication procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
601
1>otherwise:

The UE shall:
1>set the IE "CN Domain Identity" to the value indicated by the upper layers. The value of the IE indicates the CN
domain whose associated signalling connection the upper layers are indicating to be released;
1>remove the signalling connection with the identity indicated by upper layers from the variable
ESTABLISHED_SIGNALLING_CONNECTIONS;
1>transmit a SIGNALLING CONNECTION RELEASE INDICATION message on DCCH using AM RLC.
When the SIGNALLING CONNECTION RELEASE INDICATION message has been submitted to lower layers for
transmission the procedure ends.
In order to establish an MM connection, the mobile station proceeds as follows (TS 24 008 clause 4.5.1.1, 4.5.1.2,
4.5.3.1)
If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters
MM sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an establishment
cause and a CM SERVICE REQUEST message. When the establishment of an RR connection is indicated by the
RR sublayer, the MM sublayer of the mobile station starts timer T3230, gives an indication to the CM entity that
requested the MM connection establishment, and enters MM sublayer state WAIT FOR OUTGOING MM
CONNECTION.
If T3230 expires (i.e. no response is given but a RR connection is available) the MM connection establishment is
aborted and the requesting CM sublayer is informed. If no other MM connection exists then the mobile station shall
proceed as described in clause 4.5.3.1 for release of the RR connection. Otherwise the mobile station shall return to
the MM sublayer state where the request of an MM connection was received, i.e. to MM sublayer state MM
connection active. Other ongoing MM connections (if any) shall not be affected.
If all MM connections are released by their CM entities, and no RRLP procedure (see 3GPP TS 04.31 [23b]) and no
LCS procedure over RRC (see 3GPP TS 25.331 [23c]) is ongoing, the mobile station shall set timer T3240 and enter
the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection.

The UE initiates the Service request procedure by sending a SERVICE REQUEST message. The timer T3317 shall be
started after the SERVICE REQUEST message has been sent and the UE enters the GMM-SERVICE-REQUEST-
INITIATED is entered. The SERVICE REQUEST message shall contain the valid P-TMSI and the Service type shall
indicate either signalling or paging response(TS 24.008 clause 4.7.13.1). The following abnormal cases can be
identified(TS 24.008 clause 4.7.13.5).
c) T3317 expired
The UE shall enter GMM-REGISTERED state.
If the UE is in PMM-IDLE state then the procedure shall be aborted and the UE shall initiate a PS signalling
connection release.
Reference
3GPP TS 25.331 clause 8.1.14, TS 24.008 clause 4.5.1.1, 4.5.1.2, 4.5.3.1, 4.7.13.1, 4.7.13.5.
8.1.9.3 Test purpose
To confirm that the UE transmits a SIGNALLING CONNECTION RELEASE INDICATION message after upper
layer requests to release its signalling connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
602
8.1.9.4 Method of test
Initial Condition
Test Procedure
an outgoing call. Then the UE shall establish an RRC connection and transmit a SERVICE REQUEST message or a
CM SERVICE REQUEST message using the INITIAL DIRECT TRANSFER message depending on supported CN
domain. The SS does not respond to this message, and the UE shall send a SIGNALLING CONNECTION RELEASE
INDICATION message which includes the CN domain identity with the same value as that in the INITIAL DIRECT
TRANSFER message.
Expected sequence
UE SS
1 The UE initiates an outgoing
call.
4 The UE configures the layer 2
and layer 1.
6 INITIAL DIRECT TRANSFER Depending on supported CN
domain, includes SERVICE
REQUEST message (PS
domain) or CM SERVICE
REQUEST message (CS
domain) is emdedded in INITIAL
7 The SS does not respond and
waits for T3317 (PS domain) or
T3230+T3240 (CS domain).
8 SIGNALLING CONNECTION RELEASE
INDICATION
The timing of this message is
not checked.

SIGNALLING CONNECTION RELEASE INDICATION (Step 8)
CN domain identity Check to see if this value is the same as in the uplink
INITIAL DIRECT TRANSFER message.

8.1.9.5 Test requirement
After step 7 the UE shall transmit a SIGNALLING CONNECTION RELEASE INDICATION message which includes
the same CN domain identity as that found in the INITIAL DIRECT TRANSFER message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
603
8.1.9a Signalling Connection Release Indication (RLC re-establishment):
CS signalling connection release
8.1.9a.1 Definition

8.1.9a.2 Conformance requirement
If a re-establishment of RLC on signalling radio bearer RB2 occurs before the successful delivery of the SIGNALLING
CONNECTION RELEASE INDICATION message has been confirmed by RLC, the UE shall:
1>retransmit the SIGNALLING CONNECTION RELEASE INDICATION message on the uplink DCCH using
AM RLC on signalling radio bearer RB2.
Reference
3GPP TS 25.331 clause 8.1.14.2a.
8.1.9a.3 Test purpose
To confirm that the UE re-transmits a SIGNALLING CONNECTION RELEASE INDICATION message after it re-
establishes the RLC entity on signalling radio bearer RB2 if SRNS relocation occurs before the successful delivery of
SIGNALLING CONECTION RELEASE INDICATION message.
8.1.9a.4 Method of test
Initial Condition
System Simulator: 1 cells Cell 1.
34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is in CELL_DCH mode. The SS transmits a DOWNLINK DIRECT TRANSFER message. This message
contains a NAS message (AUTHENTICATION REQUEST for CS domain or AUTHENTICATION AND
CIPHERING REQUEST for PS domain). The UE shall transmit an UPLINK DIRECT TRANSFER message
(AUTHENTICATION RESPONSE) using AM on DCCH. After SS responses with a DOWNLINK DIRECT
TRANSFER message (AUTHENTICATION REJ ECT), SS shall set the RLC entity for SRB2 to stop and wait for
T3240 to expire in the UE. The UE shall send a SIGNALLING CONNECTION RELEASE INDICATION message
which includes the CN domain identity with the same value as that in the UPLINK DIRECT TRANSFER message. But
SS do not respond with STATUS PDU for the AM DATA PDU with POLL. The SS then sends a UTRAN MOBILITY
INFORMATION message on SRB1 requesting the UE to do a SRNS relocation. SS shall set the RLC entity for SRB2
to continue. The UE shall send a UTRAN MOBILITY INFORMATION CONFIRM message. The UE shall re-transmit
a SIGNALLING CONNECTION RELEASE INDICATION message on the uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
604
Expected sequence
UE SS
1 DOWNLINK DIRECT TRANSFER
(AUTHENTICATION REQUEST)
Depending on supported CN
domain, AUTHENTICATION
AND CIPHERING REQUEST
message (PS domain) or
AUTHENTICATION REQUEST
(CS domain) message is
embedded in DOWNLINK
An invalid SQN is provided in
this message.
2 UPLINK DIRECT TRANSFER
(AUTHENTICATION RESPONSE)

(AUTHENTICATION REJ ECT)
After SS transmits this message,
SS sets the RLC entity for
SRB2 to stop and waits for
T3240 to expire.
INDICATION

5 UTRAN MOBILITY INFORMATION . SS sets RLC for SRB2 to
continue.
CONFIRM
UE sends this message on
uplink DCCH on AM.
INDICATION
UE re-transmits this message.

Use the same message sub-type as found in TS 34.108 clause 9, with the following exceptions.
NAS message AUTHENTICATION REQUEST (CS domain) or
AUTHENTICATION AND CIPHERING REQUEST
(PS domain)

Message Type
SS.
The first/ leftmost bit of the bit string contains the
NAS message AUTHENTICATION FAILURE(CS domain) or
AUTHENTICATION AND CIPHERING FAILURE (PS
domain)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
605
info

- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B


Message Type
CN domain identity Check to see if this value is the same as in the UPLINK

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
606
8.1.9a.5 Test requirement
After step 1 the UE shall transmit UPLINK DIRECT TRANSFER messages using AM on DCCH.
AM RLC.
After step 6 the UE shall re-transmit a SIGNALLING CONNECTION RELEASE INDICATION message which
includes the same CN domain identity as that found in the UPLINK DIRECT TRANSFER message.

8.1.9b Signalling Connection Release Indication (RLC re-establishment):
PS signalling connection release
8.1.9b.1 Definition

8.1.9b.2 Conformance requirement
If a re-establishment of RLC on signalling radio bearer RB2 occurs before the successful delivery of the SIGNALLING
CONNECTION RELEASE INDICATION message has been confirmed by RLC, the UE shall:
1>retransmit the SIGNALLING CONNECTION RELEASE INDICATION message on the uplink DCCH using
AM RLC on signalling radio bearer RB2.
Reference
3GPP TS 25.331 clause 8.1.14.2a.
8.1.9b.3 Test purpose
To confirm that the UE re-transmits a SIGNALLING CONNECTION RELEASE INDICATION message after it re-
establishes the RLC entity on signalling radio bearer RB2 if SRNS relocation occurs before the successful delivery of
SIGNALLING CONECTION RELEASE INDICATION message.
8.1.9b.4 Method of test
Initial Condition
System Simulator: 1 cells Cell 1 is active.
UE: Registered Idle Mode on PS (state 3) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in idle mode of cell 1. SS requests operator to initial an outgoing PS call. UE shall send RRC
CONNECTION REQUEST message on the uplink CCCH. Then the SS shall respond with a RRC CONNECTION
SETUP message, which request the UE to enter CELL_DCH state, on a downlink CCCH. The UE shall then send a
RRC CONNECTION SETUP COMPLETE message on the uplink DCCH. After this, the UE shall send a INITIAL
DIRECT TRANSFER message to SS. This message contains a NAS message (SERVICE REQUEST). After SS has
acknowledge the INITIAL DIRECT TRANSFER message, the SS shall set the RLC entity for SRB3 to stop wait for
T3240 to expire in the UE. The UE shall send a SIGNALLING CONNECTION RELEASE INDICATION message
which includes the CN domain identity with the same value as that in the INITIAL DIRECT TRANSFER message. But
SS do not respond with STATUS PDU for the AM DATA PDU with POLL. The SS then sends a UTRAN MOBILITY
INFORMATION message requesting the UE to do SRNS relocation. The UE shall send a UTRAN MOBILITY
INFORMATION CONFIRMmessage. The UE shall re-transmit a SIGNALLING CONNECTION RELEASE
INDICATION message on the uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
607
Expected sequence
UE SS
1 RRC CONNECTION REQUEST SS request the operator to make
an outgoing PS call.
(SERVICE REQUEST)
After SS acknowledges this
message, SS set the RLC entity
for SRB2 to stop and waits for
T3240 to expire.
INDICATION
SS do not send any RLC
response (STATUS PDU).
6 UTRAN MOBILITY INFORMATION SS sets RLC for SRB2 to
continue.
CONFIRM

INDICATION
UE re-transmits this message.

Check that the UE sends the same message sub-type as found in TS 34.108 clause 9, with the following exceptions.
Establishment cause Originating Interactive Call or Originating Background
Call

Use the same message sub-type "RRC CONNECTION SETUP message: UM (Transition to CELL_DCH)"as found in
TS 34.108 clause 9.
Check that the UE sends the same message sub-type as found in TS 34.108 clause 9.
INITIAL DIRECT TRANSFER (Step 4)
Check that the UE sends the same message sub-type as found in TS 34.108 clause 9, with the following exceptions.
CN domain identity PS domain
NAS message SERVICE REQUEST

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "Speech to CELL_DCH from
CELL_DCH in CS "or "Non speech to CELL_DCH from CELL_DCH in CS", with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
608
info

- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B


Message Type
CN domain identity Check to see if this value is the same as in the INITIAL

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
609
8.1.9b.5 Test requirement
In step 1, the UE shall transmit RRC CONNECTION REQUEST message using TM RLC on uplink CCCH.
After step 2, the UE shall transmit RRC CONNECTION SETUP COMPLETE message using AM RLC on uplink
DCCH.
After step 3 the UE shall transmit INITIAL DIRECT TRANSFER messages using AM on DCCH.
AM RLC.
After step 7 the UE shall re-transmit a SIGNALLING CONNECTION RELEASE INDICATION message which
includes the same CN domain identity as that found in the INITIAL DIRECT TRANSFER message.
8.1.10 Broadcast of system information
8.1.10.1 Dynamic change of segmentation, concatenation & scheduling and handling
of unsupported information blocks

1. The RRC layer in the UE shall perform re-assembly of segments. All segments belonging to the same master
information block, scheduling block or system information block shall be assembled in ascending order with
respect to the segment index. When all segments of the master information block, scheduling block or a system
information block have been received, the UE shall perform decoding of the complete master information block,
scheduling block or system information block.
2. For all system information blocks or scheduling blocks that are supported by the UE referenced in the master
..
- read and store the IEs of that system information block;
NOTE: There are options with and without scheduling blocks.
3. For system information blocks, not supported by the UE.
- skip reading this system information block;
- skip monitoring changes to this system information block.
4. However, to enable future introduction of new system information blocks, the UE shall also be able to receive
system information blocks other than the ones indicated within the scheduling information. The UE may ignore
contents of such system information block.
Reference
3GPP TS 25.331 clause 8.1.1.1.4, 8.1.1.5 and 8.1.1.6.
1. To verify that dynamic change of System Information is identified, new information read and used.
2. To verify that the UE can support all segment types and "all" segment combinations.
3. To verify that the UE can dynamically use different configurations
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
610
4. To verify that the UE properly uses combinations of Default and assigned values.
NOTE: There are 4 segment types and 11 different SYSTEM INFORMATION segment combinations to interpret
when re-assembling segments. There are many alternative SIB position offsets and repetition rates.
The allowed segment types are:
- First segment
- Subsequent segment
- Last segment
- Complete

The allowed segment combinations are:
1. No segment
2. First segment
3. Subsequent segment
4. Last segment
5. Last segment +First segment
6. Last segment +one or several Complete
7. Last segment +one or several Complete +First segment
8. One or several Complete
9. One or several Complete +First segment
10. One Complete of size 215 to 226 (not fully tested)
11. Last segment of size 215 to 222
NOTE: Segment combinations 10 and 11 are more difficult to test as they require SIBs of a very specific size.
Alternate two sets of System Information and generate a call after one or the other set has been broadcasted.
These two sets of System Information are based on the System Information specified in 34.108, section 6.
A "Minimum" configuration and a "Maximum" configuration of System Information are defined. The "Minimum"
configuration does not contain all of the Information Blocks defined for Configuration 1 in section 6 of 34.108, while
the "Maximum" configuration does. The contents of the SIBs remains the same (for the "Minimum" configuration, the
contents of SIB11 changes for the "Maximum" configuration) while the contents of the MIB and SB is altered
depending on the nature of the test, i.e. the schedule changes between the "Minimum" and "Maximum" configurations.
The four segment types and the eleven segment combinations are tested using the two configurations.
NOTE: The decoding of system information in the UE is only measurable by functional tests. A large number of
functions utilize system information. An extensive test of the system information decoding thus creates a
large number of functional tests, which is impractical. This test specification uses a "sample test", where
only a few functions are invoked.
Initial Condition
System Simulator: 2 cells (Cell 1, Cell 2), settings for Cell 1 and Cell 2 according to TS 34.108, clause 6.1.5, table 6.1.2
(Cell 1 configured as the serving cell). The Minimum Configuration System Information is being broadcast in Cell 1.
The Maximum Configuration System Information is being broadcast in Cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
611
UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity (set to IMSI)
,depending on the CN domain(s) supported by the UE.
Test procedure
Table 8.1.10.1-1 illustrates the downlink power to be applied for the 2 cells.
Table 8.1.10.1-1
UTRA RF
Channel Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-60 -65

a) The UE is in C1 in Camped Normally state.
b) UE starts establishing a MO call/session.
c) SS disconnects the call. UE shall enter IDLE state.
d) The SS sets the Cell Barred Indicator in SIB3 to "Barred". The SS notifies the UE of the changed System
Information by sending the Paging Type 1 message including the IE BCCH Modification Info indicating that
new System Information is available.
e) Based on the updated information in SIB3, the UE performs a cell reselection to Cell 2. The UE reads the
System Information in Cell 2, i.e. Maximum Configuration System Information.
f) UE starts establishing a MO call/session.
Expected sequence
UE SS
1 UE Mobile originated call/session
establishment
2 SS Disconnection of call
3 System Information (Minimum
Configuration)

System Information message is
sent in Cell 1 with the Cell Barred
Indicator in SIB3 set to "Barred".
4 Paging Type 1 This message is to inform the UE
in Idle State that System
Information has been updated.
5 UE Mobile originated call /session
establishment
that UE is in CELL_DCH state, the

Specific message content for "Minimum" configuration
The Minimum configuration is the same as the Configuration 1 System Information on 34.108, section 6 with some
differences:
- Only SIB1, SIB3, SIB5, SIB7, SIB11 are used, i.e. the Minimum number of SIBs is used.
- No SB is used, all scheduling information is contained in the MIB. The contents of this changed MIB are shown
below.
- A different schedule is used. Details below.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
612
- SIB11 lists eight cells (one serving cell and seven neighbouring cells). Only the first two of these are considered
relevant.
Other characteristics of the Minimum configuration are:
- An unknown future System Information Block (SIB-F1) is included. SIB-F1 is used to test segment combination
10. However, it should be noted that, based on the scheduling information in the MIB, UEs may decide not to
read segment combinations associated with SIBs that they do not support/comprehend. Hence, the use of SIB-F1
does not fully cover the verification of combinations 10. The tests really just verify that UE ignores it. There is
no real verification that the UE can support segment combinations 10.
The following tables show (based on SIB_REP and SIB_POS in the MIB and SB) the schedule used for the Minimum
configuration.
Table 1: The schedule in this table incorporates segment combinations 1, 2, 3, 4, 7, 8, 10.
Block
Type
MIB SIB1 SIB3 SIB5 SIB7 SIB11
SIB_REP 8 64 64 64 16 64
SEG_
COUNT
1 1 1 3 1 4

Frame No /
SIB_POS
0 2 4 6 8 10 12 14
Block Type MIB SIB7 MIB

Frame No /
SIB_POS
16 18 20 22 24 26 28 30
Block Type MIB
SIB7/SIB
3
SIB1 MIB SIB-F1 SIB5

Frame No /
SIB_POS
32 34 36 38 40 42 44 46
Block Type MIB SIB5
SIB5/SIB
7/SIB11
SIB11 MIB SIB11 SIB11

Frame No /
SIB_POS
48 50 52 54 56 58 60 62
Block Type MIB SIB7 MIB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
613
Contents of Master Information Block PLMN type is the case of GSM-MAP
- MIB value tag 1
- Supported PLMN types
- PLMN type GSM-MAP
- PLMN identity
- MCC digit Set to the same Mobile Country Codes stored in the test
USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
- MNC digit Set to the same Mobile Network Codesstored in the test
- ANSI-41 Core Network information Not Present
- References to other system information blocks
and scheduling blocks

- References to other system information
blocks

- Scheduling information
- CHOICE Value tag PLMN Value tag
- PLMN Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 22
- SIB_POS offset info Not Present use default
- SIB type System Information Type 1
- CHOICE Value tag Cell Value tag
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 20
- Cell Value tag 1
- SEG_COUNT 3
- SIB_REP 64
- SIB_POS 30
- SIB_POS offset info
- SIB_OFF 4
- SIB_OFF 2
- CHOICE Value tag Not Present
- SEG_COUNT 1
- SIB_REP 16
- SIB_POS 4
- SIB_POS offset info Not Present
- SIB and SB type System Information Type 7
- Cell Value tag 1
- SEG_COUNT 4
- SIB_REP 64
- SIB_POS 36
- SIB_OFF 2
- SIB_OFF 4
- SIB_OFF 2
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 28
- SIB and SB type System Information Type F1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
614
Specific message content for "Maximum" configuration
The Maximum configuration is the same as the Configuration 1 System Information on 34.108, section 6 with some
differences:
- A different schedule is used. Details below.
- SIB11 lists eight cells (one serving cell and seven neighbouring cells). Only the first two of these are considered
relevant.
- SIB6 and SIB12 includes all optional IEs even if having same values as correspondent IEs in SIB5 and SIB11
respectively (to fascilitate implementation of the test case for the Maximum configuration).
Other characteristics of the Maximum configuration are:
- one "unknown future" block (SIB-F2) is included. This SIB is concatenated with another SIB and is used to
verify that the UE can receive an Information Block that it does not support and still process the Information
Blocks that it does support in the correct way.
- The test of the segment combination 9 is verified if the UE is able to read SIB7 and the first segment of SIB5 in
position 4.
- The test of the segment combination 11 is verified if the UE is able to read the last segment of SIB 5. The SS
ensures that this last segment shall have the length between 215 and 222 bits. Depending on the length of SIB 5,
the combination 11 occurs either in SIB_position 6, or in the most cases in SIB_position 10
The following tables show (based on SIB_REP and SIB_POS in the MIB and SB) the schedule used for the Maximum
configuration.
Table 2: The schedule in this table incorporates segment combinations 1, 2, 3, 5, 6, 8, 9, 11.
Block
Type
MIB SB1 SIB1 SIB2 SIB3 SIB4 SIB5 SIB6 SIB7 SIB11 SIB12 SIB18
SIB_REP 8 16 64 64 64 64 64 64 32 64 64 64
SEG_
COUNT
1 1 1 1 1 1 3 3 1 4 4 1

Frame No /
SIB_POS
0 2 4 6 8 10 12 14
Block Type MIB SB1
SIB7/
SIB5
SIB5 MIB SIB5
SIB3/SIB
-F2
SIB11

Frame No /
SIB_POS
16 18 20 22 24 26 28 30
Block Type MIB SB1 SIB11 SIB11 MIB
SIB11/SI
B12
SIB12 SIB12

Frame No /
SIB_POS
32 34 36 38 40 42 44 46
Block Type MIB SB1
SIB7/SIB
18
SIB12 MIB SIB6 SIB6
SIB6/SIB
2

Frame No /
SIB_POS
48 50 52 54 56 58 60 62
Block Type MIB SB1 SIB4 MIB SIB1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
615
Contents of Master Information Block PLMN type is the case of GSM-MAP
- MIB value tag 1
- Supported PLMN types
- PLMN type GSM-MAP
- PLMN identity
- MCC digit Set to the same Mobile Country Codes stored in the test
- MNC digit Set to the same Mobile Network Codesstored in the test
- ANSI-41 Core Network information Not Present
and scheduling blocks

- References to other system information
blocks

- CHOICE Value tag Cell Value Tag
- Cell Value tag 1
- Scheduling
- SEG_COUNT 1
- SIB_REP 16
- SIB_POS 2
- SIB type Scheduling Block 1
- CHOICE Value tag PLMN Value tag
- PLMN Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 58
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 46
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 12
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 52
- Cell Value tag 1
- SEG_COUNT 3
- SIB_REP 64
- SIB_POS 4
- SIB_OFF 2
- SIB_OFF 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
616
Contents of Scheduling Block 1 (FDD and TDD 1.28 Mcps option)
- Cell Value tag 1
- SEG_COUNT 3
- SIB_REP 64
- SIB_POS 42
- SIB_OFF 2
- SIB_OFF 2
- SEG_COUNT 1
- SIB_REP 32
- SIB_POS 4
- Cell Value tag 1
- SEG_COUNT 4
- SIB_REP 64
- SIB_POS 14
- SIB_OFF 6
- SIB_OFF 2
- SIB_OFF 4
- Cell Value tag 1
- SEG_COUNT 4
- SIB_REP 64
- SIB_POS 26
- SIB_OFF 2
- SIB_OFF 2
- SIB_OFF 8
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 36
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 12

Contents of Scheduling Block 1 (TDD 3.84 Mcps option)
- Cell Value tag 1
- SEG_COUNT 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
617
- SIB_REP 128
- SIB_POS 3
- SIB_OFF 2
- SIB_OFF 2
- SEG_COUNT 1
- SIB_REP 16
- SIB_POS 2
- SIB type SIBs only System Information Type 7
- Cell Value tag 1
- SEG_COUNT 3
- SIB_REP 64
- SIB_POS 29
- SIB_OFF 2
- SIB_OFF 2
- Cell Value tag 1
- SEG_COUNT 3
- SIB_REP 64
- SIB_POS 13
- SIB_OFF 2
- SIB_OFF 2
- Cell Value tag 1
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 54
- SIB type SB System Information Type 18
- SEG_COUNT 1
- SIB_REP 64
- SIB_POS 6

Contents of System Information Block type F1
Data Arbitrary data with a size of 226 bits

Contents of System Information Block type F2
Data Arbitrary data with a size of 50 bits

NOTE: For these future System Information Block types one of the available spare values for SIB type should be
used
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
618
After step 1 the UE shall have a call/session established in Cell 1.
After step 5 the UE shall have a call/session established in Cell 2.
8.1.11 Signalling Connection Release (Invalid configuration)
8.1.11.1 Definition

Upon reception of a SIGNALLING CONNECTION RELEASE message, the UE shall:
1>indicate the release of the signalling connection and pass the value of the IE "CN domain identity" to upper
layers;
1>remove the signalling connection with the identity indicated by the IE "CN domain identity" from the variable
ESTABLISHED_SIGNALLING_CONNECTIONS;
1>clear the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions"
in the variable TRANSACTIONS;
If radio access bearers for the CN domain indicated by the IE "CN domain identity" exist in the variable
ESTABLISHED_RABS, the UE shall:
1>set the IE "Received message type" to SIGNALLING CONNECTION RELEASE; and
SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable
TRANSACTIONS and clear that entry;
1>include the IE "Protocol error information" with contents set to the value "Message not compatible with receiver
state";
2>continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION
RELEASE message has not been received.
Reference
3GPP TS 25.331 clause 8.1.13.3 and 8.1.13.5.
To confirm that the UE ignores the SIGNALLING CONNECTION RELEASE REQUEST message which request the
UE to release signalling connection of domain that contains established radio access bearers.
To confirm that the UE transmit a RRC STATUS message to SS after detecting an invalid configuration in the received
message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
619
Initial Condition
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS_DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS
Test Procedure
SS transmit MEASUREMENT CONTROL message to UE. In this message, SS requests UE to perform traffic volume
measurement. Key measurement parameters are as follows: measurement quantity ="RLC Buffer Payload", report
criteria ="periodic reporting criteria", reporting interval ="6 seconds", reporting amount ='infinity'. UE shall begin
traffic volume measurements, and shall send MEASUREMENT REPORT message after completing first measurement.
UE shall send second MEASUREMENT REPORT message 6 seconds after first MEASUREMENT REPORT message.
Then SS transmit SIGNALLING CONNECTION RELEASE message to UE. UE shall ignore the message and send a
RRC STATUS message to SS. Then the UE shall send MEASUREMENT REPORT message to SS within the next 6
seconds.
Expected sequence
UE SS
1 MEASUREMENT CONTROL Periodical traffic volume
measurement reporting is
requested.
2 MEASUREMENT REPORT
3 MEASUREMENT REPORT Time difference between earlier
and this MEASUREMENT
REPORT message should be 6
seconds.
4 SIGNALLING CONNECTION RELEASE If the initial condition of the UE
is state 6-9, set the IE "CN
domain identity" to "CS
domain". If the initial condition of
the UE is state 6-10, set the IE
"CN domain identity" to "PS
domain".
5 RRC STATUS
6 MEASUREMENT REPORT This message should be sent
within 6 seconds after the
previous message.

MEASUREMENT CONTROL (Step 1)
For MEASUREMENT CONTROL message in step 1, use the message sub-type as found in clause 9 of TS 34.108, with
the exception of the following Information Elements:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
620
Measurement Identity 1
Measurement Command Setup
Measurement reporting mode
- Transfer Mode Acknowledged mode
- Periodical or event trigger Periodic
Additional measurement list Not Present
CHOICE measurement type Traffic Volume Measurement
- Traffic volume measurement object list
- UL Target Transport Channel ID 5
- Traffic volume measurement quantity
- Measurement quantity RLC Buffer Payload
- Time Interval to take an average or a variance Not Present
- Traffic volume reporting quantity
- RLC Buffer Payload for each RB True
- Average of RLC Buffer Payload for each RB False
- Variance of RLC Buffer Payload for each RB False
- Measurement validity Not Present
- CHOICE Reporting criteria Periodical Reporting Criteria
- Reporting interval 6 Sec
DPCH compressed mode status Not Present

MEASUREMENT REPORT (Step 2, 3 and 6)
Check that the message received is the same as the message sub-type found in clause 9 of TS 34.108, with the following
exceptions and the order in which the RBs are reported is not checked.:
Measured Results
- CHOICE measurement Traffic volume measured results list
- Traffic volume measurement results
- RB identity 1
- RLC buffer payload Check to see if this IE is present
- RLC buffer payload average Check to see if this IE is absent
- RLC buffer payload variance Check to see if this IE is absent
- RB identity 2
- RB identity 3
- RB identity 4
Measured results on RACH Check to see if this IE is absent
Additional measured results Check to see if this IE is absent
Event results Check to see if this IE is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
621
SIGNALLING CONNECTION RELEASE (Step 4)
Message Type
- RRC Message sequence number SS provides the value of this IE, from its internal counter.
CN domain identity If the initial condition of the UE is state 6-9, set to "CS
domain". If the initial condition of the UE is state 6-10, set
to "PS domain".

RRC STATUS (Step 5)
Message Type
Identification of received message Not Checked
- Received message type SIGNALLING CONNECTION RELEASE
- RRC transaction identifier 0
- Protocol error cause Message not compatible with receiver state

After step 1 the UE shall transmit MEASUREMENT REPORT message twice at an interval of 6 seconds.
After step 4 the UE shall transmit a RRC STATUS message with protocol error cause set to "Message not compatible
After step 5 the UE shall transmit a MEASUREMENT REPORT within 6 seconds.
8.1.12 Integrity Protection
8.1.12.1 Definition

If the UE receives an RRC message on signalling radio bearer with RB identity n, the "Status" in the variable
INTEGRITY_ PROTECTION_INFO has the value "Started" and the IE 'Integrity check info' is present the UE shall:
1>check the value of the IE "RRC message sequence number" included in the IE "Integrity check info";
2>if the "Downlink RRC Message sequence number" is not present in the variable
INTEGRITY_PROTECTION_INFO:
3>initialise the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable
INTEGRITY_PROTECTION_INFO with the value of the IE "RRC message sequence number" included
in the IE "Integrity check info" of the received message.
2>if the "Downlink RRC Message sequence number" is present in the variable
INTEGRITY_PROTECTION_INFO:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
622
3>if the RRC message sequence number is lower than the "Downlink RRC Message sequence number" for
signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO:
4>increment "Downlink RRC HFN" for signalling radio bearer RBn in the variable
INTEGRITY_PROTECTION_INFO with one.
3>if the RRC message sequence number is equal to the "Downlink RRC Message sequence number" for
signalling radio bearer RBn in the variable INTEGRITY_PROTECTION_INFO:
4>discard the message.
1>calculate an expected message authentication code in accordance with subclause 8.5.10.3 of TS25.331;
1>compare the expected message authentication code with the value of the received IE "message authentication
code" contained in the IE "Integrity check info";
2>if the expected message authentication code and the received message authentication code are the same, the
integrity check is successful:
3>update the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable
INTEGRITY_PROTECTION_INFO with the value of the IE "RRC message sequence number" included
in the IE "Integrity check info" of the received RRC message.
2>if the calculated expected message authentication code and the received message authentication code differ:
3>if the IE "RRC message sequence number" included in the IE "Integrity check info" is lower than the
"Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable
INTEGRITY_PROTECTION_INFO (in this case the "Downlink RRC HFN" for signalling radio bearer
RBn in the variable INTEGRITY_PROTECTION_INFO was incremented by one, as stated above):
4>decrement "Downlink RRC HFN" for signalling radio bearer RBn in the variable
INTEGRITY_PROTECTION_INFO by one.
If the UE receives an RRC message on signalling radio bearer with identity n, the "Status" in the variable INTEGRITY_
PROTECTION_INFO has the value "Started" and the IE 'Integrity check info' is not present the UE shall:
Reference
3GPP TS 25.331 clause 8.5.10
8.1.12. 3 Test purpose
To confirm that the UE discards any RRC messages that include wrong messaqge authentication code, or RRC message
sequence number, or do not include IE"Integrity Check Info" after integrity protection is activated.
Initial Condition
System Simulator: 1cell.
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS_DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS
34.108, depending on the CN domain(s) supported by the UE after integrity protection is activated on all SRBs.
Test Procedure
The UE is in CELL_DCH state, radio access bearer and integrity protection is already activated in generic setup
procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
623
SS transmits RRC CONNECTION RELEASE message which does not include IE"Integrity Check Info" on downlink
DCCH. The UE shall discard this message and shall not respond using RRC CONNECTION RELEASE COMPLETE
message.
Then SS transmits RRC CONNECTION RELEASE message which includes wrong message authentication code on
downlink DCCH. The UE shall discard this message and shall not respond using RRC CONNECTION RELEASE
COMPLETE message.
Then SS transmits RRC CONNECTION RELEASE message which includes IE"RRC Message sequence number" as
set to the same sequence number as the number in previous received RRC message. The UE shall discard this message
and shall not respond using RRC CONNECTION RELEASE COMPLETE message.
Then SS transmits RRC CONNECTION RELEASE message which includes correct RRC Message sequence number
and message authentication code. The UE shall transmit RRC CONNECTION RELEASE COMPLETE message on
uplink DCCH and enter to idle state.
Expected sequence
UE SS
1 RRC CONNECTION RELEASE See specific message content
2 During 5s after step 1, confirm
that UE does not transmit RRC
CONNECTION RELEASE
COMPLETE message. If RRC
CONNECTION RELEASE
COMPLETE message is
received, the test is ended as
fail.
CONNECTION RELEASE
CONNECTION RELEASE
COMPLETE message is
received, the test is end as fail.
5 Void
6 Void
7 Void
CONNECTION RELEASE
CONNECTION RELEASE
COMPLETE message is
received, the test is end as fail.
10 RRC CONNECTION RELEASE Use default message content.
COMPLETE

that UE is in Idle state, the test

Integrity check info Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
624
- Message authentication code SS calculates the value of MAC-I for this message and set
different value from the calculated result to this IE. The
first/ leftmost bit of the bit string contains the most
- RRC Message sequence number SS provides the value of this IE, from its previous internal
counter value.

- Message authentication code SS calculates the value of MAC-I for this message and set
the result to this IE. The first/ leftmost bit of the bit string
- RRC Message sequence number SS provides the value of this IE, from its previous internal
counter value
.

After step 1 the UE shall not transmit RRC CONNECTION RELEASE COMPLETE message on the uplink DCCH.
After step 10 the UE shall transmit RRC CONNECTION RELEASE COMPLETE message on the uplink DCCH.
8.2 Radio Bearer control procedure
8.2.1 Radio Bearer Establishment
Success

If the UE receives:
- a RADIO BEARER SETUP message; or
it shall:
1>if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this
procedure:
2>perform the physical layer synchronisation procedure A as specified in TS 25.214 (FDD only);
1>act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the
following and perform the actions below.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
625
The UE shall then:
1>enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the
UE shall:
1>if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1>if the IE "Downlink information for each radio link" is absent, not change its current DL Physical channel
configuration.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements
as specified below. The UE shall:
1>set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received
message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
1bis> in TDD, if the procedure is used to perform a handover to a cell where timing advance is enabled, and the UE
can calculate the timing advance value in the new cell (i.e. in a synchronous TDD network):
2>set the IE "Uplink Timing Advance" according to subclause 8.6.6.26.In case the procedure was triggered by
reception of a RADIO BEARER SETUP message, the UE shall:
1>transmit a RADIO BEARER SETUP COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE establishes a new radio bearer according to a RADIO BEARER SETUP message.
Initial Condition
UE: CS-DCCH_DCH (state 6-5) or PS_DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108, depending on
Test Procedure
The UE is in CELL_DCH state, after the test operator is prompted to make an out-going call. Before step 1, only
signalling radio bearers have been established. The SS transmits a RADIO BEARER SETUP message to the UE . This
message requests the establishment of radio access bearer. After the UE receives this message, it configures them and
establishes a radio access bearer. Finally the UE transmits a RADIO BEARER SETUP COMPLETE message using
AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER SETUP
COMPLETE


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
626
RADIO BEARER SETUP
"Non speech from CELL_DCH to CELL_DCH in CS" or "Speech from CELL_DCH to CELL_DCH in CS" or "Packet
to CELL_DCH from CELL_DCH in PS" in [9] TS 34.108 clause 9.
After step 1 the UE shall transmit a RADIO BEARER SETUP COMPLETE message.
8.2.1.2 Void
Failure (Unsupported configuration)

If the UTRAN instructs the UE to use a configuration, which it does not support and/or if the received message causes
the variable UNSUPPORTED_CONFIGURATION to be set to TRUE, the UE shall:
1>transmit a failure response as specified in TS 25.331 subclause 8.2.2.9, setting the information elements as
specified below:
2>set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted
transactions" in the variable TRANSACTIONS; and
2>clear that entry;
2>set the IE "failure cause" to "configuration unsupported".
1>set the variable UNSUPPORTED_CONFIGURATION to FALSE;
1>continue with any ongoing processes and procedures as if the reconfiguration message was not received.
The UE shall:
1>in case of reception of a RADIO BEARER SETUP message:

2>transmit a RADIO BEARER SETUP FAILURE as response message on the DCCH using AM RLC.

The UE should set the variable UNSUPPORTED_CONFIGURATION to TRUE if the received message is not
according to the UE capabilities.
Reference
3GPP TS 25.331 clause8.2.2.6, 8.2.2.9, 8.5.20.
To confirm that the UE keeps its configuration and transmits a RADIO BEARER SETUP FAILURE message in case of
receiving a RADIO BEARER SETUP message which includes parameters of its unsupported configuration.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
627
Initial Condition
UE: CS-DCCH_DCH (state 6-5) or PS_DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108, depending on
the domain(s) supported by the UE.
Test Procedure
The UE is in CELL_DCH state. SS then send a MEASUREMENT CONTROL message to UE. The UE shall perform
periodical traffic volume measurement according to this message and then transmit MEASUREMENT REPORT
message back to SS. The SS transmits a RADIO BEARER SETUP message in which the frequency cannot be
supported by the UE. After the UE receives this message, it transmits a RADIO BEARER SETUP FAILURE message
on the DCCH using AM RLC . UE shall continue its traffic volume measurement and send MEASUREMENT
REPORT messages back to SS periodically.
Expected sequence
UE SS
0a MEASUREMENT CONTROL SS requests UE to perform
periodical traffic volume
measurement.
0b MEASUREMENT REPORT
1 RADIO BEARER SETUP Including the unsupported
configuration for the UE.
2 RADIO BEARER SETUP FAILURE The UE does not change the
configuration.

MEASUREMENT CONTROL (Step 0a)
Use the MEASUREMENT CONTROL message as defined in [9] TS 34.108 clause 9, with the following exceptions:
- Measurement Report Transfer Mode Acknowledged mode RLC
- Periodical Reporting / Event Trigger Reporting
Mode
Periodical Reporting
- Measurement validity
- UE state All states
- Reporting interval 8000

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
628
MEASUREMENT REPORT (Step 0b and 3)
Check to see if the same message type found in [9] TS 34.108 Clause 9 is received, with the following exceptions and
the order in which the RBs are reported is not checked.:
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

RADIO BEARER SETUP (Step 1)
The contents of RADIO BEARER SETUP message in this test case is indicated as "Non-speech in CS" or the RADIO
BEARER SETUP message as found in clause 9 of TS 34.108 with the following exceptions:
RADIO BEARER SETUP (FDD)
Frequency info
CHOICE mode FDD
- UARFCN uplink (Nu) 0
- UARFCN downlink (Nd) 950

RADIO BEARER SETUP (TDD)
Frequency info
CHOICE mode TDD
- UARFCN (Nt) 0

RADIO BEARER SETUP FAILURE (Step 2)
The contents of RADIO BEARER SETUP FAILURE message in this test case is the same as the RADIO BEARER
SETUP FAILURE message as found inTS 34.108 clause 9, with the following exceptions:
Message Type
Failure cause Not checked

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
629
After step 0a, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, reporting the RLC
buffer payload of each RBs mapped on DCH at every 8s interval.
After step 1 the UE transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC .
After step 2, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, reporting the RLC
Failure (Physical channel Failure and successful reversion to old
configuration)

When a physical dedicated channel establishment is initiated by the UE, the UE shall start a timer T312 and wait for
layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is
considered established and the timer T312 is stopped and reset.
If the timer T312 expires before the physical channel is established, the UE shall consider this as a "physical channel
establishment failure".
NOTE: The criteria defined in this subclause only apply in case the UE performs synchronisation procedure A
(FDD only).

If the received message caused the UE to be in CELL_DCH state and the UE according to subclause 8.5.4 failed to
establish the dedicated physical channel(s) indicated in the received message the UE shall:
1>revert to the configuration prior to the reception of the message (old configuration);

1>transmit a failure response message as specified in TS 25.331 subclause 8.2.2.9, setting the information elements
as specified below:
2>clear that entry;
2>set the IE "failure cause" to "physical channel failure".
1>set the variable ORDERED_RECONFIGURATION to FALSE;

The UE shall:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
630
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration and transmits a RADIO BEARER SETUP FAILURE message
on the DCCH using AM RLC, if the UE fails to reconfigure the radio bearer according to the RADIO BEARER SETUP
message before timer T312 expires.
Initial Condition
System Simulator: 2 cells. Cell 1 is active and cell 2 is inactive.
the domain(s) supported by the UE.
Test Procedure
Table 8.2.1.4
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60

OFF -75
P-CCPCH
RSCP
(TDD)
dBm
-60 -60 OFF -75

The UE is in CELL_DCH state in cell 1. SS then send a MEASUREMENT CONTROL message to UE. The UE shall
perform periodical traffic volume measurement according to this message and then transmit MEASUREMENT
REPORT message back to SS. Then the SS configures its downlink transmission power settings according to column
"T1" in table 8.2.1.4. The SS transmits a RADIO BEARER SETUP message to the UE specifying a configuration in
cell 2 and SS keeps its old dedicated channel configuration in cell 1. Then after T312 expiry, the UE reverts to the old
configuration and transmits a RADIO BEARER SETUP FAILURE message on the DCCH in cell 1 using AM RLC
which is set to "physical channel failure" in IE "failure cause". UE shall continue its traffic volume measurement and
send MEASUREMENT REPORT messages back to SS periodically.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
631
Expected sequence
UE SS
measurement.
1 RADIO BEARER SETUP The SS keeps its old L1
configuration in cell 1 and does
not configure a physical channel
in cell 2 after transmitting this
message.
2 The UE does not configure the
new radio access bearer and
reverts to the old configuration.
3 RADIO BEARER SETUP FAILURE UE shall transmit this message
using the old configuration.

Mode

the order in which the RBs are reported is not checked:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
632
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

The contents of the RADIO BEARER SETUP message in this test case is indicated as "Non speech to CELL_DCH
from CELL_DCH in CS", "Speech to CELL_DCH from CELL_DCH in CS" or "Packet to CELL_DCH from
CELL_DCH in PS" as found in clause 9 of TS 34.108, with the following exceptions.
Downlink information for each radio link list
- Downlink information for each radio links
- CHOICE mode FDD
- Primary CPICH scrambling code Ref. to the Default setting for cell 2 in TS34.108 clause
6.1 (FDD)

RADIO BEARER SETUP (Step 1) (TDD)
The contents of the RADIO BEARER SETUP message in this test case is indicated as "Non speech to CELL_DCH
from CELL_DCH in CS", "Speech to CELL_DCH from CELL_DCH in CS" or "Packet to CELL_DCH from
CELL_DCH in PS" as found in clause 9 of TS 34.108, with the following exceptions:

- CHOICE mode TDD
- Primary CCPCH info Ref. to the Default setting for cell 2 in TS34.108 clause
6.1 (TDD)
SETUP FAILURE message as found in clause 9 of TS 34.108, with the following exceptions:
Failure cause Physical channel failure

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
633
After step 2 the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC which
is set to "physical channel failure" in IE "failure cause".
8.2.1.5 Void
8.2.1.6 Void

Failure (Invalid message reception and Invalid configuration)

If the received reconfiguration message contains a protocol error causing the variable PROTOCOL_ERROR_REJ ECT
to be set to TRUE according to TS 25.331 clause 9, the UE shall perform procedure specific error handling as follows.
The UE shall:
as specified below:
2>set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected
2>clear that entry;
2>set the IE "failure cause" to the cause value "protocol error";
.
If the variable INVALID_CONFIGURATION is set to TRUE the UE shall:
1>keep the configuration existing before the reception of the message;
as specified below:
3>set it to the value of "RRC transaction identifier" in the entry for the received message in the table
"Accepted transactions" in the variable TRANSACTIONS; and
3>clear that entry.
2>set the IE "failure cause" to "invalid configuration".
1>set the variable INVALID_CONFIGURATION to FALSE;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
634
.
not comprehended";
TRANSACTIONS; and
.
If the IE "RAB information for setup" is included, the procedure is used to establish radio bearers belonging to a radio
access bearer, and the UE shall:
1>if several IEs "RAB information for setup" are included and the included IEs "CN domain identity" in the IE
"RAB info" does not all have the same value:
.
The UE shall:

Reference
3GPP TS 25.331 clause 8.2.2.13, 8.2.2.11, 8.2.2.9, 8.6.4.2 and 9.3b.
To confirm that the UE transmits a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC if it
receives an invalid RADIO BEARER SETUP message which contains an unexpected critical message extension.
To confirm that the UE transmits a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC if it
receives a RADIO BEARER SETUP message including an invalid configuration.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
635
Test Procedure
message back to SS. The SS transmits an invalid RADIO BEARER SETUP message to the UE which contains an
unexpected critical message extension. The UE keeps the old configuration and transmits a RADIO BEARER SETUP
FAILURE message on the DCCH using AM RLC which is set to "protocol error" in IE "failure cause", and is set to
"Message extension not comprehended" in IE "Protocol error cause". UE shall continue its traffic volume measurement
and send MEASUREMENT REPORT messages back to SS periodically. The UE keeps current configuration after SS
transmits a RADIO BEARER SETUP message including an invalid configuration. Then UE transmits a RADIO
BEARER SETUP FAILURE message on the DCCH using AM RLC, setting the value "invalid configuration" to IE
"failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT messages back
to SS periodically.
Expected sequence
UE SS
measurement.
1 RADIO BEARER SETUP See specific message content.
2 RADIO BEARER SETUP FAILURE The UE does not change its
configuration.
2a MEASUREMENT REPORT
3 RADIO BEARER SETUP This message includes an invalid
value.
4 RADIO BEARER SETUP FAILURE The UE does not change its
configuration.

Mode

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
636
MEASUREMENT REPORT (Step 0b, 2a and 5)
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Use the RADIO BEARER SETUP message as defined in [9] TS 34.108 clause 9, with the following exceptions:

Message Type
Failure cause
- Protocol error cause Message extension not comprehended
Other information element Not checked

The contents of RADIO BEARER SETUP message in this test case is identical as "Non speech from CELL_DCH to
CELL_DCH in CS", Speech to CELL_DCH from CELL_DCH in CS" or "Packet to CELL_DCH from CELL_DCH in
PS" as found in clause 9 of TS 34.108 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
637
RAB information for setup list
- RAB information for setup This IE is set as defined in message "RADIO BEARER
SETUP message: AM or UM (Speech in CS)"
- RAB information for setup This IE is set as defined in message "RADIO BEARER
SETUP message: AM or UM (Packet to CELL_DCH from
CELL_DCH in PS)"


After step 1 the UE shall keep its old configuration and transmit a RADIO BEARER SETUP FAILURE message on the
DCCH using AM RLC which is set to "protocol error" in IE "failure cause" and set to "Message extension not
comprehended" in IE "Protocol error cause".
After step 3 the UE shall keep its old configuration and transmit a RADIO BEARER SETUP FAILURE message on the
DCCH using AM RLC, setting the value "invalid configuration" to IE "failure cause".
8.2.1.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH:
Success

If the UE receives:
it shall:
1>perform the physical layer synchronisation procedure as specified in TS 25.214 (FDD only);
The UE shall then:

If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
638
1>if the IE "Frequency info" is included in the received reconfiguration message:
2>select a suitable UTRA cell according to TS 25.304 on that frequency.
1>if the IE "Frequency info" is not included in the received reconfiguration message:
2>select a suitable UTRA cell according to TS 25.304.
1>if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH
info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration
message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):
2>initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
3>if the UE is in CELL_PCH or URA_PCH state:
4>initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data
transmission";
4>proceed as below.
1>start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured
by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in system
information block type 1;
1>use the transport format set given in system information;
1>if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2>ignore that IE and stop using DRX.
1>if the contents of the variable C_RNTI is empty:
2>perform a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
transmission";
4>proceed as below.

1>clear that entry;

In case the procedure was triggered by reception of a RADIO BEARER SETUP message, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
639
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
Initial Condition
NOTE: The timer poll value in the SS RLC transmit entity should be set to 800 ms.
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state, after the test operator is asked to initiate a packet-switched data call. The SS transmits a
RADIO BEARER SETUP message to the UE. After the UE receives this message, it transits from CELL_DCH to
CELL_FACH state. Finally the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC. Then
the UE and the SS enters the communicating state. SS calls for generic procedure C.2 to check that UE is in
CELL_FACH state.
Expected sequence
UE SS
1 RADIO BEARER SETUP SS requests test operator to make
an outgoing packet-switched data
call.
COMPLETE
The UE selects PRACH and S-
CCPCH indicated in SIB5 or SIB6
after entering CELL FACH state.

For RADIO BEARER SETUP message in step 1, use the message sub-type indicated as "Packet to CELL_FACH from
CELL_DCH in PS" found in [9] TS 34.108 clause 9 with the following exception:
New C-RNTI 0000 0000 0000 0001B

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
640
8.2.1.9 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH:
Success (Cell re-selection)

1. If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:

- if the contents of the variable C_RNTI is empty:
- perform a cell update procedure according to clause 8.3.1 using the cause "Cell reselection";
2. If the CELL UPDATE CONFIRM message
the UE shall:
- transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.
3. In case the procedure was triggered by reception of a RADIO BEARER SETUP message, the UE shall:
- transmit a RADIO BEARER SETUP COMPLETE as response message on the uplink DCCH using AM
RLC;
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.3.1.7, 8.2.2.4.
1. To verify that the UE when receiving a RADIO BEARER SETUP message not including a value for C-RNTI
initiate a cell update procedure and indicating the cause "Cell reselection".
2. To verify that the UE when the CELL UPDATE CONFIRM message does not include "RB information
elements", "Transport channel information elements" nor "Physical channel information elements" but include
the IE "New C-RNTI" transmit a UTRAN MOBILITY INFORMATION CONFIRM message.
3. To confirm that the UE transmits RADIO BEARER SETUP COMPLETE message after it completes the cell
update procedure.
Initial Condition
System Simulator: 1 cell- Cell 1 is active.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
641
NOTE: The 'timer poll' value in the SS RLC transmit entity should be set to 800 ms.
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER SETUP message which includes IE "Primary
CPICH info" and no dedicated physical channel information, to request the UE to transit from CELL_DCH to
CELL_FACH. Due to absence of the C-RNTI in the RADIO BEARER SETUP message the UE shall initiate the cell
update procedure even if the UE selects the same cell as indicated by the IE "Primary CPICH info" (for FDD) or
"Primary CCPCH info" (for TDD). The UE transmits a CELL UPDATE message on uplink CCCH with IE "Cell update
cause" set to "cell reselection". The SS shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after
receiving CELL UPDATE message. The UE transmits a UTRAN MOBILITY INFORMATION CONFIRM message
on the DCCH using AM RLC. The UE transmits a RADIO BEARER SETUP COMPLETE message on the DCCH
using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 Void
2 Void
3 RADIO BEARER SETUP Assigned the transition from
CELL_DCH to CELL_FACH
4 CELL UPDATE The value "cell reselection" set
in IE "Cell update cause".
5 CELL UPDATE CONFIRM C-RNTI included
CONFIRM

fails.

The contents of RADIO BEARER SETUP message in this test case is identical as "Packet to CELL_FACH from
CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exception:
New C-RNTI Not present

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in [9]
TS 34.108 clause 9 with the following exceptions:
Cell Update Cause "cell reselection"

in [9] TS 34.108 clause 9. with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
642
New C-RNTI 0000 0000 0000 0001B

The contents of UTRAN MOBILITY INFORMATION CONFIRM message is identical as "UTRAN MOBILITY
INFORMATION CONFIRM message" as found in [9] TS 34.108 clause 9.
RADIO BEARER SETUP COMPLETE (Step 7)
The contents of RADIO BEARER SETUP COMPLETE message is identical as "RADIO BEARER SETUP
COMPLETE message" as found in [9] TS 34.108 clause 9.
1. After step 3 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to
"cell reselection".
2. After step 5 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH
using AM RLC.
3. After step 6 the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM
RLC.
8.2.1.10 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH:
Success

If the UE receives:
it shall:
procedure:
The UE shall then:
If after state transition the UE enters CELL_DCH state, the UE shall, after the state transition:
1>remove any C-RNTI from MAC;
1>clear the variable C_RNTI.
1>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
643

Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
Initial Condition
UE: PS-DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state, after SS prompts the test operator to initiate a packet-switched data call. The SS
transmits a RADIO BEARER SETUP message to the UE . After the UE receives this message, it configures them and
establishes the required radio bearers. Finally the UE transmits a RADIO BEARER SETUP COMPLETE message
using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
COMPLETE


RADIO BEARER SETUP
The contents of RADIO BEARER SETUP message in this test case is identical the message sub-type indicated by
"Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9.
After step 1 the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
644
Failure (Unsupported configuration)

specified below:
2>clear that entry;

The UE shall:


Reference
3GPP TS 25.331 clause 8.2.2.6, 8.2.2.9, 8.5.20.
To confirm that the UE keeps its configuration and transmits a RADIO BEARER SETUP FAILURE message in case of
it receiving a RADIO BEARER SETUP message, which includes parameters of an unsupported configuration.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. SS then send a MEASUREMENT CONTROL message to UE. The UE shall perform
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
645
message back to SS. The SS transmits a RADIO BEARER SETUP message with a stated frequency that cannot be
supported by the UE. After the UE receives this message, it shall transmit a RADIO BEARER SETUP FAILURE
message on the DCCH using AM RLC . UE shall continue its traffic volume measurement and send MEASUREMENT
Expected sequence
UE SS
measurement.
1 RADIO BEARER SETUP This message includes an
unsupported configuration for the
UE.
2 RADIO BEARER SETUP FAILURE The UE shall transmit this
message using RLC-AM mode
and do not change the current
configuration.

Mode
- Uplink transport channel type RACHorCPCH
- UL Target Transport Channel ID Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
646
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

The contents of RADIO BEARER SETUP message in this test case is indicated as "Packet to CELL_DCH from
CELL_FACH in PS" as found in [9] TS 34.108 Clause 9 with the following exceptions:
RADIO BEARER SETUP (FDD)
Frequency info
- CHOICE mode FDD

RADIO BEARER SETUP (TDD)
Frequency info
- CHOICE mode TDD
- UARFCN (Nt) 0

SETUP FAILURE message as found in [9] TS 34.108 Clause 9, with the following exceptions:
Message Type

buffer payload of each RBs mapped on RACH at every 8s interval.
After step 1 the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM .
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
647
Failure (Physical channel Failure and successful reversion to old
configuration)

.
If the received message caused the UE to be in CELL_DCH state and the UE failed to establish the dedicated physical
channel(s) indicated in the received message the UE shall:

as specified below:
2>clear that entry;
.
The UE shall:

Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration and transmits a RADIO BEARER SETUP FAILURE message
when the UE fails to configure the new radio bearer after it detects physical channel failure, followed by the T312
expiry.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
648
Initial Condition
Test Procedure
message back to SS. The SS transmits a RADIO BEARER SETUP message to the UE and keeps its old physical
channel configuration. After T312 expiry, the UE shall perform cell reselection procedure and detect the same serving
cell only. Then the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC.
The content of the message shall indicate "physical channel failure" in IE "failure cause". UE shall continue its traffic
volume measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
measurement.
1 RADIO BEARER SETUP The SS keep its old configuration.
2 RADIO BEARER SETUP FAILURE The UE does not configure a new
radio bearer and reverts to the old
configuration.

Mode

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
649
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

"Packet to CELL_DCH from CELL_FACH in PS" clause 9 of TS 34.108.

After step 1 the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC which
is set to "physical channel failure" in IE "failure cause".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
650
Failure (Physical channel Failure and cell reselection)

.

1>if the old configuration does not include dedicated physical channels (CELL_FACH state):
2>select a suitable UTRA cell according to TS 25.304;
2>if the UE selects another cell than the cell the UE camped on upon reception of the reconfiguration message:
3>initiate a cell update procedure according to TS 25.331 subclause 8.3.1, using the cause "Cell
reselection";
3>after the cell update procedure has completed successfully:
4>proceed as below.
as specified below:
2>clear that entry;
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
651
the UE shall:
.
The UE shall:

Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.3.1.7, 8.5.4.
To confirm that the UE transmit a RADIO BEARER SETUP FAILURE message after it completes a cell update for the
physical channel failure in the radio bearer establishment procedure.
Initial Condition
UE: PS-DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108 in cell 1.
Test Procedure
Table 8.2.1.13
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -75 -75 -60
P-CCPICH
RSCP
(TDD)
dBm
-60 -75 -75 -60

specifies reverse of the transmission power settings for cell 1 and cell 2.
The UE is in CELL_FACH state in cell 1. SS then send a MEASUREMENT CONTROL message to UE. The UE shall
REPORT message back to SS. The SS transmits a RADIO BEARER SETUP message to the UE. After transmitting the
RADIO BEARER SETUP message, the SS shall not configure its DL dedicated physical channel in accordance with
the setting in the message and release its current configuration. At the same time, the SS configures its downlink
transmission power settings according to columns "T1" in table 8.2.1.13. The UE recognize that it cannot synchronize
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
652
with the SS on the new radio bearer. The UE performs cell re-selection and transmits a CELL UPDATE message on
uplink CCCH with IE "Cell update cause" which is set to "cell reselection". The SS shall transmit a CELL UPDATE
CONFIRM message on downlink DCCH after receiving a CELL UPDATE message. The UE transmits a UTRAN
MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC and subsequently transmits a
RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC, setting the value "physical channel
failure" to IE "failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT
messages back to SS periodically.
Expected sequence
UE SS
measurement.
2 The SS does not configure the
new radio bearer in accordance
with the settings in the message
and applies the downlink
transmission power settings,
according to the values in
columns "T1" of table 8.2.1.13.
3 Void
4 The UE select the cell 2.
5 CELL UPDATE The value "cell reselection" shall
be set in IE "Cell update cause".
6 CELL UPDATE CONFIRM This message include IE "new U-
RNTI" and IE "new C-RNTI".
CONFIRM

8 RADIO BEARER SETUP FAILURE The IE "failure cause" shall be set
to "physical channel failure"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
653
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

The contents of RADIO BEARER SETUP message in this test case is identical to the message sub-type "Packet to
CELL_DCH from CELL_FACH in PS" found in clause 9 of TS 34.108.
TS 34.108 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
654

The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM" message as found
New U-RNTI
- SRNC Identity '0000 0000 0000 0001'
- S-RNTI Different from previous S-RNTI
New C-RNTI Different from previous C-RNTI

Message Type "RADIO BEARER RECONFIGURATION FAILURE"
Failure cause "physical channel failure"

After step 4 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to "cell
reselection".
After step 6 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH
using AM RLC.
After step 7 the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC,
setting the IE "failure cause" to "physical channel failure".
Failure (Incompatible simultaneous reconfiguration)

If the received message is any of the messages:
- RADIO BEARER SETUP; or

the UE shall:
2>if the variable ORDERED_RECONFIGURATION is set to TRUE; or

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
655
3>if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction
identifier" stored for the same "Message Type" as the received message in the table "Accepted
transactions" in the variable TRANSACTIONS:

3>else:
4>reject the transaction; and
4>if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in
the variable TRANSACTIONS:
5>store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the
table "Rejected transactions" in the variable TRANSACTIONS.

If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable
PROTOCOL_ERROR_REJ ECT is set to FALSE, the UE shall:
1>not apply the configuration contained in the received reconfiguration message;
1>transmit a failure response message as specified in subclause TS 25.331 8.2.2.9, setting the information elements
as specified below:
2>clear that entry;
2>set the IE "failure cause" to "incompatible simultaneous reconfiguration".

The UE shall:

Reference
3GPP TS 25.331 clause 8.2.2.9, 8.2.2.12, clause 8.6.3.11.
To confirm that if the UE receives a RADIO BEARER SETUP message during a reconfiguring procedure due to a radio
bearer message other than RADIO BEARER SETUP, it shall keep its configuration as if the RADIO BEARER SETUP
message had not been received and complete the reconfiguration procedure according to the previously received
message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
656
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RECONFIGURATION message to the UE.
The SS transmits a RADIO BEARER SETUP message before the "activation time" indicated in the RADIO BEARER
RECONFIGURATION message expires. When the UE receives the RADIO BEARER SETUP message, the UE shall
keep its current configuration as if it had not received the RADIO BEARER SETUP message and shall transmit a
RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC with IE "failure cause" set to
"incompatible simultaneous reconfiguration". After the SS acknowledges the RADIO BEARER SETUP FAILURE
message, the UE reconfigures the new physical channel parameters upon the specified activation time and transmits a
RADIO BEARER RECONFIGURATION COMPLETE message on DCCH using AM RLC. SS calls for generic
procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
3 RADIO BEAER SETUP FAILURE The UE does not change the
configuration because of the
RADIO BEARER SETUP
message, and transmit this
message on its uplink DCCH
using the same RLC-AM mode
radio bearer before step 1.
COMPLETE
This message is on DCCH using
AM RLC.

RADIO BEARER RECONFIGURATION (Step 1) (FDD)
The contents of RADIO BEARER RECONFIGURATION message in this test case are identical as "Packet to
CELL_DCH from CELL_FACH in PS" as found in clause 9 of TS 34.108 with the following exceptions:
Activation Time Not present
Uplink DPCH Info
- Scrambling code number 1

RADIO BEARER RECONFIGURATION (Step 1) (TDD)
The contents of RADIO BEARER RECONFIGURATION message in this test case are identical as "Packet to
CELL_DCH from CELL_FACH in PS" as found in clause 9 of TS 34.108 with the following exceptions:
- Uplink DPCH timeslots and codes
- First timeslot code list Assigned in step 1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
657
RADIO BEARER SETUP (for Step 2) (FDD)
For this message, use the message sub-type entitled "Packet to CELL_DCH from CELL_FACH in PS" in the default
message content. Information element(s) to be changed are listed below:
Uplink DPCH Info

RADIO BEARER SETUP (for Step 2) (TDD)
For this message, use the message sub-type entitled "Packet to CELL_DCH from CELL_FACH in PS" in the default
message content. Information element(s) to be changed are listed below:
Activation Time Not Present
- First timeslot code list A different code combination than used in step 1.

RADIO BEARER SETUP FAILURE
SETUP FAILURE message as found in Annex A, with the following exceptions:
Message Type
Failure cause Incompatible simultaneous reconfiguration

After step 2 the UE shall transmit a RADIO BEARER SETUP FAILURE message on the DCCH using AM RLC with
IE "failure cause" set to "Incompatible simultaneous reconfiguration".
After step 3 the UE shall configure the new configuration on the activation time and transmit a RADIO BEARER
RECONFIGURATION COMPLETE message on the DCCH using AM RLC.
8.2.1.15 Void

8.2.1.16 Radio Bearer Establishment for transition from CELL_FACH to CELL_FACH:
Success

If the UE receives:
it shall:
1>perform the physical layer synchronisation procedure as specified in TS 25.214;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
658
The UE shall then:
If the UE was in CELL_FACH state upon reception of the reconfiguration message and remains in CELL_FACH state,
the UE shall:
2>if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary
CCPCH info" (for TDD), and the UE selected another cell than indicated by this IE or the received
reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info"
(for TDD):

1>clear that entry;

Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE establishes a new radio access bearer according to a RADIO BEARER SETUP message.
Initial Condition
Test Procedure
The UE is in CELL_FACH state, after the test operator is being prompted to make an outgoing packet-switched call.
The SS transmits a RADIO BEARER SETUP message to the UE. After the UE receives this message, it configures
them and establishes a new radio access bearer. Finally the UE transmits a RADIO BEARER SETUP COMPLETE
message on the DCCH using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
659
Expected sequence
UE SS
COMPLETE
The UE select PRACH and S-
CCPCH using SIB5 or SIB6.

None.
After step 1, the UE shall transmit a RADIO BEARER SETUP COMPLETE message.
success (Subsequently received)

If the IE "RRC transaction identifier" is included in a received message, the UE shall perform the actions below. The
UE shall:

the UE shall:
2>if the variable CELL_UPDATE_STARTED is set to TRUE; or
2>if the table "Accepted transactions" in the variable TRANSACTIONS contains an entry with an IE "Message
Type" set to ACTIVE SET UPDATE; or
2>if the received message contains a protocol error according to TS 25.331 clause 9 causing the variable
PROTOCOL_ERROR_REJ ECT to be set to TRUE:
4>ignore the transaction; and
4>continue with any ongoing processes and procedures as the message was not received;
4>and end the procedure.
3>else:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
660
Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a new RADIO BEARER SETUP message before the UE completes the configuration
of the radio bearer according to a previous RADIO BEARER SETUP message, it ignores the new RADIO BEARER
SETUP message and configures according to the previous RADIO BEARER SETUP message received.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. SS transmits a RADIO BEARER SETUP message to the UE before the UE completes
the configuration of the radio bearer according to the RADIO BEARER SETUP message prior to this new message.
The UE ignores the new RADIO BEARER SETUP message and configures according to the former RADIO BEARER
SETUP message. On completion of radio bearer configuration, the UE shall transmit a RADIO BEARER SETUP
COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER SETUP Scrambling code number is set to
"1" for FDD mode.
2 RADIO BEARER SETUP SS send this message before the
expiry of activation time specified
in RADIO BEARER SETUP
message of step 1. For FDD the
IE "Scrambling code number" is
set to "2" and for TDD mode a
different code combination to that
used in step 11 is used.
3 RADIO BEARER SETUP COMPLETE The UE ignores the RADIO
BEARER SETUP message in
step 2 and completes
configuration according to the
RADIO BEARER SETUP
message in step 1.

For RADIO BEARER SETUP in step 1, use the message sub-type indicated as "Non speech to CELL_DCH from
CELL_DCH in CS" or "Speech to CELL_DCH from CELL_DCH in CS" or "Packet to CELL_DCH from CELL_DCH
in PS" as found in clause 9 of TS 34.108, with the exception of the following Information Elements:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
661
Activation Time [256+Current CFN-[current CFN mod 8 +8 ]]MOD 256
- Uplink DPCH Info

For RADIO BEARER SETUP in step 1, use the message sub-type indicated as "Non speech in CS" as found in clause 9
of TS 34.108, with the exception of the following Information Elements:

For RADIO BEARER SETUP in step 2, use the message sub-type indicated as "Non speech to CELL_DCH from
CELL_DCH in CS" or "Speech to CELL_DCH from CELL_DCH in CS" or "Packet to CELL_DCH from CELL_DCH
in PS" as found in clause 9 of TS 34.108, with the exception of the following:
- Uplink DPCH Info

For RADIO BEARER SETUP in step 2, use the message sub-type indicated as "Non speech in CS" as found in clause 9
of TS 34.108, with the exception of the following:
- First timeslot code list A different code combination to that used in step 1.

After step 2 the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM RLC.
Success (Subsequently received)

UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
662

the UE shall:
3>else:
Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a new RADIO BEARER SETUP message before the UE completes the configuration
of the radio bearer according to a previous RADIO BEARER SETUP message, it ignores the new RADIO BEARER
SETUP message and configures according to the previous RADIO BEARER SETUP message received.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER SETUP message, requesting the UE to setup
radio bearers using DPCH physical channels. SS transmits another RADIO BEARER SETUP message before the
activation time specified in the first message has lapsed. The UE ignores the new RADIO BEARER SETUP message
and configures the radio bearers according to the former RADIO BEARER SETUP message. On completion of radio
bearer configuration, the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM
RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
663
Expected sequence
UE SS
1 RADIO BEARER SETUP Scrambling code number is set to
"1" for FDD mode.
2 RADIO BEARER SETUP For FDD mode the IE "Scrambling
code number" is set to "2" and for
TDD mode a different code
combination to that used in step 1
1 is used.
3 RADIO BEARER SETUP COMPLETE The UE ignores the RADIO
BEARER SETUP message in
step 2 and confirms configuration
according to the RADIO BEARER
SETUP message in step 1.

For this message, use the message sub-type entitled "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108
clause 9.
- Uplink DPCH Info

For this message, use the message sub-type indicated as " Packet to CELL_DCH from CELL_FACH in PS " as found
in clause 9 of TS 34.108, with the exception of the following Information Elements:

RADIO BEARER SETUP (for Step 2) (FDD)
For this message, use the message sub-type entitled "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108
clause 9, with the following exceptions:
- Uplink DPCH Info

For this message , use the message sub-type indicated as " Packet to CELL_DCH from CELL_FACH in PS " as found
in clause 9 of TS 34.108, with the exception of the following:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
664

After step 2 the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM RLC
After step 3 the UE shall communicate with the SS on the radio bearer specified in the RADIO BEARER SETUP
message in step 1.
8.2.1.19 Void
8.2.1.20 Void
8.2.1.21 Void
8.2.1.22 Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH
(Frequency band modification): Success

If the UE receives:
-a RADIO BEARER SETUP message;
it shall:
1>act upon all received information elements as specified in TS25.331 subclause 8.6, unless specified in the
1>enter a state according to TS25.331 subclause 8.6.3.3.
2>select a suitable UTRA cell according to TS5.304 on that frequency.
2>select a suitable UTRA cell according to TS5.304.
1>if the received reconfiguration message included the IE "Primary CPICH info", and the UE selects another cell
than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info"
(FDD only):
2>initiate a cell update procedure according to TS25.331 subclause 8.3.1 using the cause "Cell reselection";
4>initiate a cell update procedure according to TS25.331 subclause 8.3.1 using the cause "Uplink data
transmission";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
665
4>proceed as below.
transmission";
4>proceed as below.
1>transmit a RADIO BEARER SETUP COMPLETE message on the uplink DCCH using AM RLC, using the new
configuration after the state transition.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_FACH according to the RADIO BEARER SETUP
message.
2. To confirm that the UE transmits RADIO BEARER SETUP COMPLETE message on the uplink DCCH using
AM RLC on a common physical channel in a different frequency.
Initial Condition
System Simulator: 2 cellsCell 1 is active and cell 6 is inactive.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
666
Test Procedure
Table 8.2.1.22
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

The UE is in idle mode state of cell 1 and the SS configures its downlink transmission power setting according to
columns "T0" in table 8.2.1.22. The SS and UE execute procedure P5. Next The SS and the UE execute procedure P9.
The SS switches its downlink transmission power settings to columns "T1"and transmits a RADIO BEARER SETUP
message with no IE "Frequency info" to the UE. After the UE receives this message, it transits from CELL_DCH in cell
1 to CELL_FACH state in cell 6, and initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell
reselection". Finally the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC in cell 6. The
SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1a SS executes procedure P5 (clause
7.4.2.2.2) specified in TS 34.108.

1b SS executes procedure) P9 (clause
7.4.2.4.2) specified in TS 34.108.

3 Void
4 RADIO BEARER SETUP Not including frequency
information.
5 CELL UPDATE The IE "Cell update cause" is set
to "cell reselection".
6 CELL UPDATE CONFIRM Including the IE" New C-RNTI"
CONFIRM

COMPLETE
The UE sends this message on a
common physical channel in cell
6.

Use the message sub-type indicated as "Packet to CELL_FACH from CELL_DCH in PS" found in [9] TS 34.108 clause
9 with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
667
Frequency info Not Present
Downlink information for each radio link Not Present

The contents of CELL UPDATE message are identical as "Contents of CELL UPDATE message" as found in [9] TS
34.108 clause 9 with the following exceptions:

The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found
in [9] TS 34.108 clause 9 with the following exceptions:
New C-RNTI 0000 0000 0000 0001B

UTRAN MOBILITY UPDATE CONFIRM (Step 7)
The contents of UTRAN MOBILITY UPDATE CONFIRM message are identical as "UTRAN MOBILITY UPDATE
CONFIRM message" as found in [9] TS 34.108 clause 9.
After step 4 the UE shall transmit a CELL UPDATE message on the CCCH in cell 6.
After step 6 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using
AM RLC in cell 6.
After step 7 the UE shall transmit a RADIO BEARER SETUP COMPLETE message on the DCCH using AM RLC in
cell 6.
After step 8 the UE shall be in CELL_FACH state of cell 6.
8.2.1.23 Radio Bearer Establishment for transition from CELL_FACH to CELL_DCH

If the UE receives:
it shall:
procedure:
2>perform the physical layer synchronisation procedure A as specified in TS25.214 (for FDD only);
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
668
1>clear the C_RNTI.
1>transmit a RADIO BEARER SETUP COMPLETE message on the uplink DCCH using AM RLC, using the new
configuration after the state transition.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_DCH according to the RADIO BEARER
SETUP message.
2. To confirm that the UE transmits RADIO BEARER SETUP COMPLETE message on the uplink DCCH
using AM RLC on a dedicated physical channel in a different frequency.
Initial Condition
UE: CS-DCCH_FACH (state 6-6) or PS_DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108, depending
on the CN domain(s) supported by the UE.
Test Procedure
Table 8.2.1.23
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -55

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -55

Off -55

The UE is in CELL_FACH state of cell 1 and the SS has configured its downlink transmission power setting according
to columns "T0" in table 8.2.1.23. The SS switches its downlink transmission power settings to columns "T1" and
transmits a RADIO BEARER SETUP message including new frequency information to the UE. After the UE receives
this message, it configures them and establishes the required radio access bearers and moves into cell 6. Finally the UE
transmits a RADIO BEARER SETUP COMPLETE message using AM RLC. The SS calls for generic procedure C.3 to
check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
669
Expected sequence
UE SS
1 The initial state of UE is in
CELL_FACH state of cell 1 and
the SS has configured its
downlink transmission power
setting according to columns
"T0" in table 8.2.1.23.
3 RADIO BEARER SETUP Including new frequency
information.
COMPLETE
The UE sends this message in
cell 6.

"Packet to CELL_DCH from CELL_FACH in PS" or "Non speech from CELL_FACH to CELL_DCH in CS" or
"Speech from CELL_FACH to CELL_DCH in CS" in [9] TS 34.108 clause 9 , with the following exception:
Frequency info
- CHOICE mode FDD
- Primary Scrambling Code 350

"Packet to CELL_DCH from CELL_FACH in PS" or "Non speech from CELL_FACH to CELL_DCH in CS" or
"Speech from CELL_FACH to CELL_DCH in CS" in [9] TS 34.108 clause 9 , with the following exception:
Frequency info
- CHOICE mode TDD

cell 6.
After step 4 the UE shall be in CELL_DCH state of cell 6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
670
8.2.1.24 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH

If the UE receives:
it shall:
procedure:
2>perform the physical layer synchronisation procedure A as specified in TS 25.214 (for FDD only);
UE shall:
configuration.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_DCH according to the RADIO BEARER SETUP
message.
2. To confirm that the UE transmits the RADIO BEARER SETUP COMPLETE message on the uplink DCCH
Initial Condition
CS-DCCH_DCH (state 6-5) or PS_DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108, depending on the
CN domain(s) supported by the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
671
Test Procedure
Table 8.2.1.24
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

columns "T0" in table 8.2.1.24. For FDD, the SS switches its downlink transmission power settings to columns "T1"
and transmits a RADIO BEARER SETUP message including IE "Frequency info" set to frequency information of cell 6
and IE "Primary CPICH info" set to Primary Scrambling Code which is assigned to P-CPICH of cell. For TDD, the SS
switches its downlink transmission power settings to columns "T1" and transmits a RADIO BEARER SETUP message
including IE "Frequency info" set to frequency information of cell 6 and IE "Primary CCPCH info" set to cell 6
parameters. The UE selects cell 6 and establish a radio access bearer after receiving this message, and then remains
CELL_DCH state. The UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC after
completes configuration according to receiving RADIO BEARER SETUP message. Upon completion of the procedure,
the SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 The UE is in CELL_DCH state of
cell 1 and the SS has configured
its downlink transmission power
setting according to columns "T0"
in table 8.2.1.24.
3 RADIO BEARER SETUP For FDD, including IE "Frequency
info" set to frequency information
of cell 6 and IE "Primary CPICH
info" set to Primary Scrambling
Code assigned to P-CPICH of cell
6.
For TDD, including IE "Frequency
info" set to frequency information
of cell 6 and IE "Primary CCPCH
info" set cell 6 parameters.
4 The UE select cell 6 and establish
a radio access bearer.
COMPLETE
dedicated physical channel in cell
6.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
672
"Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" in TS34.108 clause 9 Default Message Contents, or
identical the message sub-type indicated by "Non speech in CS" in [9] TS 34.108 clause 9, with the following
exception:
- CHOICE mode FDD
Frequency info
- CHOICE mode FDD

"Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" in TS34.108 clause 9 Default Message Contents, or
identical the message sub-type indicated by "Non speech in CS" in [9] TS 34.108 clause 9, with the following
exception:
Frequency info
- CHOICE mode TDD
- CHOICE mode TDD

cell 6.
8.2.1.25 Radio Bearer Establishment for transition from CELL_FACH to CELL_FACH

If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
673
the UE shall:
(for TDD):
3>initiate a cell update procedure according to TS25.331 subclause 8.3.1 using the cause "cell reselection";
4>proceed as below.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_FACH according to the RADIO BEARER SETUP
message.
2. To confirm that the UE transmits RADIO BEARER SETUP COMPLETE message on the uplink DCCH using
AM RLC on a common physical channel in a different frequency.
Initial Condition
System Simulator: 2 cells Cell 1 is active and cell 6 is inactive.
UE: "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN
domain supported by the UE. If the UE supports both CS and PS domains, the initial UE state shall be "Registered idle
mode on CS/PS".
Test Procedure
Table 8.2.1.25
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72 Off -55

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
674
to columns "T0" in table 8.2.1.25. SS asks operator to make an outgoing call. The SS and UE execute procedure P6.
Next The SS and the UE execute procedure P10. The SS switches its downlink transmission power settings to columns
"T1" and transmits a RADIO BEARER SETUP message including IE "Frequency info" set to frequency information of
cell 6 and no IE "Primary CPICH info" for FDD and no IE "Primary CCPCH info" for TDD. The UE selects cell 6 and
initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection". The UE remains CELL_FACH
state. The UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC after completes
configuration according to receiving RADIO BEARER SETUP message. Upon completion of the procedure, the SS
calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 The SS has configured its
in table 8.2.1.25. SS requests
operator to make an outgoing call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

5 RADIO BEARER SETUP Including IE "Frequency info" set
to frequency information of cell 6
and no IE "Primary CPICH info"
for FDD and no IE "Primary
CCPCH info" for TDD.
CONFIRM

COMPLETE
6.


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
675
New C-RNTI 0000 0000 0000 0001B

AM RLC in cell 6.
cell 6.
After step 9 the UE shall be in CELL_FACH state in cell 6.
Success (Transparent mode with ciphering on)

If the UE receives:
it shall:
procedure:
The UE shall then:
UE shall:
configuration.
1>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
676

If the IE "RAB information for setup" is included, the procedure is used to establish radio bearers belonging to a radio
access bearer, and the UE shall:
1>if the radio access bearer identified with the IE "RAB info" does not exist in the variable
ESTABLISHED_RABS:
2>if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE
"CN domain identity" and at least one transparent mode radio bearer is included in the IE "RB information to
setup"; or
2>if at least one RLC-AM or RLC-UM radio bearer is included in the IE "RB information to setup":
3>calculate the START value only once during this procedure (the same START value shall be used on all
new radio bearers created for this radio access bearer) according to subclause 8.5.9 for the CN domain as
indicated in the IE "CN domain identity" in the IE "RAB info" part of the IE "RAB information to setup";
3>store the calculated START value in the variable START_VALUE_TO_TRANSMIT.
1>for each radio bearer in the IE "RB information to setup":
2>if the radio bearer identified with the IE "RB identity" does not exist in the variable ESTABLISHED_RABS:
3>perform the actions specified in subclause 8.6.4.3;

If the IE "RB information to setup" is included, the UE shall apply the following actions on the radio bearer identified
with the value of the IE "RB identity". The UE shall:
1>use the same START value to initialise the hyper frame number components of COUNT-C variables for all the
new radio bearers to setup;
1>if the IE "RB information to setup" was received in a message other than HANDOVER TO UTRAN
COMMAND; and
1>if the IE "Uplink RLC mode" and the IE "Downlink RLC mode" either in the IE "RLC info" or referenced by the
RB identity in the IE "Same as RB" is set to "TM RLC":
2>if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE
"CN domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS and at least one
transparent mode radio bearer is included in the IE "RB information to setup":
3>if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN
domain identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to " Started":
4>at the activation time as specified in the IE "Activation Time" in the RADIO BEARER SETUP
message:
5>initialise the 20 most significant bits of the HFN component of COUNT-C common for all
transparent mode RLC radio bearer to the value of the latest transmitted START for this CN
domain, while not incrementing the value of the HFN component of COUNT-C at each CFN
cycle; and
5>set the remaining LSB of the HFN component of COUNT-C to zero;
5>start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN.
4>at the activation time as specified in the IE "Ciphering activation time for DPCH" if included in the IE
"Ciphering mode info" in the command message or, if this IE is not included, as specified in the IE
"COUNT-C activation time" included in the response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
677
5>initialise the 20 most significant bits of the HFN component of COUNT-C common for all
transparent mode radio bearers of this CN domain with the START value in the variable
START_VALUE_TO_TRANSMIT;
5>set the remaining LSB of the HFN component of COUNT-C to zero;
5>start incrementing the COUNT-C value common for all transparent mode radio bearers of this CN
domain as normal, at each CFN value, i.e. the HFN component is no longer fixed in value but
incremented at each CFN cycle.
1>if the IE "Status" in the variable CIPHERING_STATUS of the CN domain as indicated in the IE "CN domain
identity" in the IE "RAB info" in the variable ESTABLISHED_RABS is set to "Started":
2>start to perform ciphering on the radio bearer in lower layers, using the value of the IE "RB identity" minus
one as the value of BEARER in the ciphering algorithm.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.4.2, 8.6.4.3.
To confirm that the UE establishes a new radio bearer according to a RADIO BEARER SETUP message, and that
cipering is applied onto this new radio bearer
Initial Condition
UE: CS-DCCH_DCH (state 6-5).
Test Procedure
The UE is in CELL_DCH state, after the test operator is prompted to make an out-going call. Before step 1, only
signalling radio bearers have been established. The SS transmits a RADIO BEARER SETUP message to the UE . This
message requests the establishment of radio access bearer. After the UE receives this message, it configures them and
establishes a radio access bearer. Finally the UE transmits a RADIO BEARER SETUP COMPLETE message using
Expected sequence
UE SS
COMPLETE

3 Void
4 E.g. . "speech" RLC-TM PDUs Check that the ciphering is
working.
RADIO BEARER SETUP COMPLETE (Step 2)
The contents of RADIO BEARER SETUP COMPLETE message in this test case is identical to the message sub-type
indicated by "Speech from CELL_DCH to CELL_DCH in CS" in [9] TS 34.108 clause 9 with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
678
START The first/ leftmost bit of the bit string contains the most
significant bit of the START.

Success (two radio links, start of HS-DSCH reception)
All UEs which support FDD and HS-PDSCH.
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the
default value "Now", the UE shall:
1>at the activation time T:
2>for an HS-DSCH related reconfiguration caused by the received message:
3>select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely
falls within the 10 ms frame following T;
3>start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received
message, replacing any old HS-DSCH configuration.
2>for actions, other than a physical channel reconfiguration, caused by the received message:
3>perform the actions for the information elements in the received message as specified elsewhere.
NOTE: An "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-
aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and
stop of HS-SCCH reception and serving HS-DSCH cell change.

If the IE "New H-RNTI" is included, the UE shall:
1>if the IE "Downlink HS-PDSCH Information" is also included and the UE would enter CELL_DCH state
according to subclause 8.6.3.3 applied on the received message:
2>store the value in the variable H_RNTI.
When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall:
1>use the value of the variable H_RNTI as UE identity in the HS-SCCH reception procedure in the physical layer.

If the IE "Added or Reconfigured DL TrCH information" is included then for the transport channel identified by the IE
"DL Transport Channel Identity" the UE shall:
1>if the choice "DL parameters" is set to 'HSDSCH':
2>if the IE "HARQ Info" is included:
3>perform the actions specified in subclause 8.6.5.6b.
2>if the value of the IE "MAC-hs reset indicator" is TRUE:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
679
3>reset the MAC-hs entity.

If the IE "Downlink HS-PDSCH Information" is included and the UE would enter CELL_DCH state according to
subclause 8.6.3.3 applied on the received message, the UE shall:
1>if the IE "New H-RNTI" is included:
2>perform the actions as specified in subclause 8.6.3.1b.
1>if the IE "HS-SCCH Info" is included:
2>act as specified in subclause 8.6.6.33.
1>if the IE "Measurement Feedback Info" is included:
1>if, as a result of the received message, the variable H_RNTI is set and the UE has a stored IE "HS-SCCH Info"
and a stored IE "Measurement Feedback Info":
2>set the variable HS_DSCH_RECEPTION to TRUE;
2>start HS-DSCH reception procedures according to the stored HS-PDSCH configuration:
3>as stated in subclause 8.6.3.1b for the IE "H-RNTI";
3>in subclause 8.6.6.33 for the IE "HS-SCCH Info"; and
3>in subclause 8.6.6.34 for the IE "Measurement Feedback Info".
1>if the IE "HS-DSCH Timeslot Configuration" is included:
2>store the received configuration.

If the IE "HS-SCCH Info" is included, the UE shall:
1>in the case of FDD:
2>receive the HS-SCCH(s) according to the IE "HS-SCCH channelisation code" on the serving HS-DSCH
radio link applying the scrambling code as received in the IE "DL Scrambling code".
1>in the case of TDD:
2>receive the HS-SCCH(s) according to the IEs "Timeslot" and "Channelisation Code" on the serving HS-
DSCH radio link;
2>receive the HS-SICH according to the IEs "Timeslot" and "Channelisation Code" on the serving HS-DSCH
radio link.

If the IE "Measurement Feedback Info" is included, the UE shall:
1>use the information for the channel quality indication (CQI) procedure in the physical layer on the serving HS-
DSCH radio link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
680
Reference
3GPP TS 25.331 clauses 8,6,3,1, 8.6.3.1b, 8.6.5.6, 8.6.6.32, 8.6.6.33, 8.6.6.34
To confirm that the UE establishes a radio bearer mapped to HS-DSCH according to the received RADIO BEARER
SETUP message when having two radio links established.
Initial Condition
System Simulator: 2 cells - Cell 1 and 2 are active
UE: PS_DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
- UE supports FDD
- UE supports HS-PDSCH
Test Procedure
The UE is in CELL_DCH state. Only signalling radio bearers have been established.
The SS transmits to the UE an ACTIVE SET UPDATE message in cell 1 on DCCH using AM RLC to add cell 2 to the
active set. When the UE receives this message, the UE shall configure layer 1 to begin reception without affecting the
current uplink and downlink activities of existing radio links. The UE shall transmit an ACTIVE SET UPDATE
COMPLETE message to the SS on the uplink DCCH using AM RLC.
The test operator is prompted to make an out-going call. The SS transmits a RADIO BEARER SETUP message to the
UE . This message requests the establishment of radio access bearer mapped to HS-DSCH. After the UE receives this
message, it configures them and establishes a radio access bearer and cell 1 shall be assigned as the serving HS-DSCH
cell. Finally the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC. SS calls for generic
Expected sequence
UE SS
1 ACTIVE SET UPDATE The SS instructs the UE to add
cell 2 in the active set.
2 ACTIVE SET UPDATE COMPLETE The UE adds the radio link in cell
2.
COMPLETE


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
681
ACTIVE SET UPDATE (Step 1)
- Primary scrambling code Primary scrambling code of Cell 2
- CHOICE mode FDD
- Primary CPICH usage for channel estimation P-CPICH may be used.
- DPCH frame offset Calculated value from Cell synchronisation infomation
- Secondary CPICH info Not present
allocated to the UE
- Secondary scrambling code Not present
- Spreading factor Refer to the parameter set in TS 34.108
- Code number For each DPCH, assign the same code number in the
- Scrambling code change Not present
- SSDT cell identity Not present
- Close loop timing adjustment mode Not present
- TFCI combining indicator TRUE
- SCCPCH information for FACH Not present

Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except
for the following:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
682
- Downlink information for each radio link (for cell 1)
- Choice mode FDD
- Primary scrambling code Ref. to the Default setting in TS34.108 clause 6.1 (FDD)
- Serving HS-DSCH radio link indicator TRUE
- Downlink DPCH info for each RL Not present
- DPCH frame offset Set to value Default DPCH Offset Value (as currently
stored in SS) mod 38400
- Code number 0
- Choice mode FDD
- Serving HS-DSCH radio link indicator FALSE
- Code number 0

After step 1, the UE shall transmit a RADIO BEARER SETUP COMPLETE message.
8.2.2 Radio Bearer Reconfiguration
8.2.2.1 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Success

If the UE receives:
- a RADIO BEARER RECONFIGURATION message; or
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
683
procedure:
The UE shall then:
UE shall:
configuration.
1>clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RECONFIGURATION message, the UE shall:
1>transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message on the uplink DCCH
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures the radio bearers according to a RADIO BEARER RECONFIGURATION
message, which indicates a change of UL scrambling code and change of RLC parameters.
Initial Condition
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of
TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RECONFIGURATION message to the UE,
which commands a change of UL scrambling code and change of RLC parameters to be performed. The UE
reconfigures the new parameter and transmits a RADIO BEARER RECONFIGURATION COMPLETE message on the
DCCH using AM RLC.
The SS transmits a new RADIO BEARER RECONFIGURATION message to the UE, which commands the UE to
reconfigure RLC parameters. The UE reconfigures the new parameters and and transmits a RADIO BEARER
RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3 to
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
684
Expected sequence
UE SS
1 Void
2 Void
3 RADIO BEARER
RECONFIGURATION
UL scrambling code is modified.
RLC configuration is modified.
4 RADIO BEARER

5 Void
6 RADIO BEARER
RECONFIGURATION
RLC configuration is modified.
7 RADIO BEARER

8 Void

RADIO BEARER RECONFIGURATION (FDD) (Step 3)
The contents of RADIO BEARER RECONFIGURATION message in this test case is identical to the message sub-type
titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found inclause 9
of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
685
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
686
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB information to reconfigure A3 (AM DTCH)
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
UL Transport channel information for all transport
channels
Not Present
Added or Reconfigured UL TrCH information Not Present
CHOICE mode Not Present
DL Transport channel information common for all
transport channel
Not Present
Deleted DL TrCH information Not Present
Added or Reconfigured DL TrCH information Not Present
Maximum allowed UL TX power Not Present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
687
CHOICE Mode FDD
- Downlink PDSCH information Not Present
Downlink information common for all radio links Not presenr
Downlink information per radio link list
-Downlink information for each radio link
- Primary scrambling code Set to same code as used for cell 1

Condition Explanation
A1 This IE need for "Non speech in CS"
A2 This IE need for "Speech in CS"
A3 This IE need for "Packet to CELL_DCH from CELL_DCH in PS"

RADIO BEARER RECONFIGURATION (TDD)(Step 3)
titled "Packet to CELL_DCH from CELL_DCH in PS" inclause 9 of TS 34.108, with the following exceptions:
CHOICE mode TDD
Uplink DPCH timeslots and codes
- First timeslot code list Assigned by SS
Downlink information common for all radio links
- Downlink DPCH info common for all RL
- Timing Indicator Maintain

titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in clause
9 of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
688
Information Element Condition Value/remark
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
689
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB information to reconfigure A3 (AM DTCH)
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
channels
Not Present
transport channel
Not Present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
690
CHOICE channel requirement Not Present
CHOICE Mode FDD
Downlink information common for all radio links Not Present
- Doenlink information for each rdio link

Condition Explanation
A1 This IE need for "Non speech in CS"
A2 This IE need for "Speech in CS"
A3 This IE need for "Packet to CELL_DCH from CELL_DCH in PS"
RADIO BEARER RECONFIGURATION (TDD) (Step 6)
titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in clause
9 of TS 34.108, with the following exceptions:

CHOICE mode TDD
- Doenlink information for each rdio link
- Primary CCPCH info Set to same as used for cell 1

After step 3 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the new
DPCH after the specified activation time has expired.
After step 6, the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message.
8.2.2.2 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Failure
(Unsupported configuration)

specified below:
2>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
691

The UE shall:
1>in case of reception of a RADIO BEARER RECONFIGURATION message:

2>transmit a RADIO BEARER RECONFIGURATION FAILURE as response message on the DCCH using
AM RLC.

Reference
3GPP TS 25.331 clause 8.2.2.6, 8.2.2.9, 8.5.20.
To confirm that the UE transmits a RADIO BEARER RECONFIGURATION FAILURE message on the DCCH using
AM RLC if the received RADIO BEARER RECONFIGURATION message includes unsupported configuration
parameters.
Initial Condition
Test Procedure
message back to SS. The SS transmits a RADIO BEARER RECONFIGURATION message to the UE, which includes
unsupported configuration parameters for the UE. The UE shall transmit a RADIO BEARER RECONFIGURATION
FAILURE message on the DCCH using AM RLC. UE shall continue its traffic volume measurement and send
MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
measurement.
1 RADIO BEARER
RECONFIGURATION
Including unsupported
configuration by the UE
2 RADIO BEARER
RECONFIGURATION FAILURE
The UE does not change the
radio bearer.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
692
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
693
The contents of RADIO BEARER RECONFIGURATION message in this test case is identical as "Speech in CS" or
"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in clause 9 of TS 34.108 with the
Frequency info
- CHOICE mode FDD

RADIO BEARER RECONFIGURATION (TDD) (Step 1)
"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in clause 9 of TS 34.108 with the
Frequency info
- CHOICE mode TDD
- UARFCN (Nt) 0

RADIO BEARER RECONFIGURATION FAILURE (Step 2)
The contents of RADIO BEARER RECONFIGURATION FAILURE message in this test case is the same as the
RADIO BEARER RECONFIGURATION FAILURE message as found in clause 9 of TS 34.108, with the following
exceptions:
Message Type

After step 1 the UE shall transmit a RADIO BEARER RECONFIGURATION FAILURE message on the DCCH using
AM RLC .
8.2.2.3 Void

8.2.2.4 Radio Bearer Reconfiguration from CELL_DCH to CELL_DCH: Failure
(Physical channel failure and cell reselection)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
694
1>if the old configuration includes dedicated physical channels (CELL_DCH state) and the UE is unable to revert
to the old configuration:
2>initiate a cell update procedure according to TS 25.331 subclause 8.3.1, using the cause "radio link failure";
3>proceed as below.

as specified below:
2>clear that entry;

- includes "Physical channel information elements":
the UE shall:
1>transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message using AM RLC.

The UE shall:

AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.3.1.7.
To confirm that the UE transmits a RADIO BEARER RECONFIGURATION FAILURE message after it completes a
cell update procedure when the UE cannot reconfigure the new radio bearer and a subsequent failure to revert to the old
configuration.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
695
Initial Condition
Test Procedure
message back to SS. The SS transmits a RADIO BEARER RECONFIGURATION message, which includes the new
radio bearer parameters, to the UE. After the reception of the acknowledgement for the RADIO BEARER
RECONFIGURATION message in SS, the SS shall not reconfigure dedicated physical channel in accordance with the
settings in the message and release the previous configuration. The UE discovers that it cannot reconfigure the new
radio bearer and wants to revert to the old configuration, but the UE cannot revert to the old configuration. The UE
transmits a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "radio link failure". The SS
shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after receiving a CELL UPDATE message.
The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using
AM RLC and subsequently transmits a RADIO BEARER RECONFIGURATION FAILURE message on the DCCH
using AM RLC, setting the value "physical channel failure" to IE "failure cause". UE shall continue its traffic volume
measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
measurement.
2 The SS does not reconfigure the
dedicated physical channel in
accordance with the RADIO
BEARER RECONFIGURATION
message and shall release the old
configuration.
3 CELL UPDATE The value "radio link failure" shall
4 The SS configures the dedicated
physical channel according to the
IE "Physical channel information
elements" included in the CELL
UPDATE CONFIRM message.
5 CELL UPDATE CONFIRM This message include IE
elements".
6 PHYSICAL CHANNEL

FAILURE

The IE "failure cause" shall be set
to "physical channel failure"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
696
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

RADIO BEARER RECONFIGURATION message (Step 1)
titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in Clause
9 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
697
The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in Clause 9
of TS 34.108 with the following exceptions:
Cell Update Cause "radio link failure"

in Clause 9 of TS 34.108 with the following exceptions:
- UplinkDPCH Info Same as RADIO BEARER SETUP message used to
Downlink information common for all radio links Same as RADIO BEARER SETUP message used to

in Clause 9 of TS 34.108 with the following exceptions:
RRC State Indicator CELL_DCH
Same as RADIO BEARER SETUP message used to

RADIO BEARER RECONFIGURATION FAILURE (Step 7)
RADIO BEARER RECONFIGURATION FAILURE message as found in Clause 9 of TS 34.108, with the following
exceptions:

After step 2 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to "radio
link failure".
After step 5 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE on the uplink DCCH
using AM RLC.
AM RLC, setting the IE "failure cause" to "physical channel failure".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
698
8.2.2.5 Void
8.2.2.6 Void
(Continue and stop)

If the IE "RB information to reconfigure" is included, the UE shall apply the following actions on the radio bearer
identified with the value of the IE "RB identity". The UE shall:

- if the IE "RB stop/continue" is included; and
- if the "RB identity" has a value greater than 2; and
- if the value of the IE "RB stop/continue" is "stop":
- configure the RLC entity for the radio bearer to stop;
- set the IE "RB started" in the variable ESTABLISHED_RABS to "stopped" for that radio bearer;
- if the value of the IE "RB stop/continue" is "continue":
- configure the RLC entity for the radio bearer to continue;
- set the IE "RB started" in the variable ESTABLISHED_RABS to "started" for that radio bearer;
Reference
3GPP TS 25.331 clause 8.2.2, 8.6.4.5.
To confirm that the UE reconfigures new radio bearer and stop the transmission and reception of the RLC entity
belonging to the RB identity specified in the RADIO BEARER RECONFIGURATION message.
To confirm that the UE reconfigures new radio bearer and restart the transmission and reception of the RLC entity
belonging to the RB identity specified in the RADIO BEARER RECONFIGURATION message.
Initial Condition
UE: CS-DCCH+DTCH (state 6-9) or PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108,
depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RECONFIGURATION message including IE
"RB stop/continue" set to "continue" for radio bearer with RB identity '3'. The UE reconfigures new radio bearer and
transmits a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM RLC. Then, the
SS transmits an IDENTITY REQUEST message using AM RLC, the UE responds a IDENTITY RESPONSE message.
The SS transmits a RADIO BEARER RECONFIGURATION message including IE "RB stop/continue" set to "stop"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
699
for radio bearer with RB identity "3". The UE reconfigures new radio bearer and transmits a RADIO BEARER
RECONFIGURATION COMPLETE message on the DCCH using AM RLC. Then, the SS transmits a IDENTITY
REQUEST message using AM RLC, the UE does not acknowledge this message and also does not respond with a
IDENTITY RESPONSE message. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RECONFIGURATION This message include IE "RB
stop/continue" set to "continue".
2 RADIO BEARER

3 IDENTITY REQUEST
3a IDENTITY RESPONSE
4 RADIO BEARER
RECONFIGURATION
This message include IE "RB
stop/continue" set to "stop".
5 RADIO BEARER

6 IDENTITY REQUEST
7 The SS shall not receive any data
from the UE.

RADIO BEARER RECONFIGURATION (Step 1)(FDD)
"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" found in clause 9 of TS 34.108, with the
-RB identity

3
-RB stop/continue "continue"
channels
Not Present
transport channel
Not Present
CHOICE Mode FDD
"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" found in clause 9 of TS 34.108, with the

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
700
-RB identity

3
-RB stop/continue "continue"
channels
Not Present
transport channel
Not Present
CHOICE Mode TDD
- Primary CCPCH info Set to same code as used for cell 1

RADIO BEARER RECONFIGURATION (Step 4)
"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in clause 9 of TS 34.108, with the
-RB identity

3
-RB stop/continue "stop"

After step 3 the UE shall respond with a IDENTITY RESPONSE message.
After step 6 the UE shall not respond with a IDENTITY RESPONSE message on the stopped RB.
8.2.2.8 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Success

If the UE receives:
it shall:
procedure:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
701
The UE shall then:


1>clear that entry;

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE establishes the reconfigured radio bearer(s) using common physical channel, after UE receives a
RADIO BEARER RECONFIGURATION message.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RECONFIGURATION message, which invoke a
transition from CELL_DCH to CELL_FACH. The UE reconfigures the radio bearers and transmits a RADIO BEARER
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
702
RECONFIGURATION COMPLETE message using AM RLC. SS calls for generic procedure C.2 to check that UE is
in CELL_FACH state.
Expected sequence
UE SS
1 RADIO BEARER
RECONFIGURATION

2 RADIO BEARER
The UE selects PRACH and S-
CCPCH indicated in SIB5 and
SIB6 after entering CELL FACH
state.

RADIO BEARER RECONFIGURATION (Step 1)(FDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in clause 9 of TS 34.108, with
the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
703
New C-RNTI 0000 0000 0000 0001B
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
704
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
705
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in clause 9 of TS 34.108, with


After step 1 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message.
8.2.2.9 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Success
(Cell re-selection)

If the UE receives:
it shall:
procedure:
1>enter a state according to subclause 8.6.3.3.
2>select a suitable UTRA cell according to [4] on that frequency.
1>select PRACH according to subclause 8.5.17;
1>select Secondary CCPCH according to subclause 8.5.19;
The UE shall transmit a response message as specified in subclause 8.2.2.4, setting the information elements as
specified below. The UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
706
1>clear that entry;

the UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.3.1.7, 8.2.2.4.
To confirm that the UE transmits RADIO BEARER RECONFIGURATION COMPLETE message after it completes a
cell update procedure.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RECONFIGURATION message, which includes
IE "Primary CPICH info" and no dedicated physical channel information to transit from CELL_DCH to CELL_FACH.
As the UE selects another cell than the specified cell, the UE shall initiate the cell update procedure. The UE transmits a
CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "cell reselection". The SS shall transmit a
CELL UPDATE CONFIRM message on downlink DCCH after receiving a CELL UPDATE message. The UE
transmits a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls
for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
707
Expected sequence
UE SS
1 Void
2 Void
3 RADIO BEARER
RECONFIGURATION
Assign a transition from
CELL_DCH to CELL_FACH.
CONFIRM

COMPLETE


The contents of RADIO BEARER RECONFIGURATION message in this test case is identical as "Packet to
CELL_FACH from CELL_DCH in PS" found in clause 9 of TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
708
New C-RNTI 0000 0000 0000 0001B
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
709
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
710
CELL_FACH from CELL_DCH in PS" found in clause 9 of TS 34.108, with the following exceptions:
4 Set to same as used for cell 2

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in Annex A
with the following exceptions:
Cell Update Cause "Cell reselection"

Use the same message type found in clause Annex A, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

After step 3, the UE shall transmit CELL UPDATE message on the CCCH with IE "Cell update cause" set to "cell
reselection".
After step 5, the UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM message and then followed by
RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM RLC.
8.2.2.10 Radio Bearer Reconfiguration: from CELL_FACH to CELL_DCH including
modification of previously signalled CELL_DCH configuration: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
711
1>clear that entry;
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE applies a previously signalled configuration for CELL_DCH and in addition modifies
the parameters for which reconfiguration is requested in the RADIO BEARER
RECONFIGURATION message that is used to initiate transition from CELL_FACH to
CELL_DCH.8.2.2.10.4 Method of test
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RECONFIGURATION message to the UE.
The UE reconfigures the radio bearers and transmits a RADIO BEARER RECONFIGURATION COMPLETE message
using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER
RECONFIGURATION
This message includes IE
"Uplink DPCH Info"
2 Reconfiguration of radio bearer
3 RADIO BEARER


Use the same message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in clause 9 of TS 34.108, with
the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
712
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
713
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
channels
Not Present
transport channels
Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
714
After step 2 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH
using AM RLC.
8.2.2.11 Radio Bearer Reconfiguration from CELL_FACH to CELL_DCH: Failure
(Unsupported configuration)

1>transmit a failure response as specified in subclause 8.2.2.9, setting the information elements as specified below:
2>clear that entry;
The procedure ends.

Reference
3GPP TS 25.331 subclause 8.2.2.6, 8.5.20.
To confirm that the UE transmits a RADIO BEARER RECONFIGURATION FAILURE message on the DCCH using
AM RLC if the received RADIO BEARER RECONFIGURATION message includes unsupported configuration
parameters.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RECONFIGURATION message, which
includes unsupported configuration parameters, to the UE. The UE shall transmit a RADIO BEARER
RECONFIGURATION FAILURE message on the DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
715
Expected sequence
UE SS
1 RADIO BEARER
RECONFIGURATION
The message includes an
unsupported configuration for the
UE
2 RADIO BEARER
radio bearer.

RADIO BEARER RECONFIGURATION (FDD)
CELL_DCH from CELL_FACH in PS" found in TS 34.108 clause 9 with the following exceptions:
Frequency info
- CHOICE mode FDD

RADIO BEARER RECONFIGURATION (TDD)
CELL_DCH from CELL_FACH in PS" found in TS 34.108 clause 9 with the following exceptions:
Frequency info
- CHOICE mode TDD
- UARFCN (Nt) 0

RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION FAILURE message as found in TS 34.108 clause 9, with the following
exceptions:
Failure cause Not checked.

AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
716
8.2.2.12 Void
8.2.2.13 Void
8.2.2.14 Void
8.2.2.15 Void
8.2.2.16 Void
8.2.2.17 Radio Bearer Reconfiguration from CELL_FACH to CELL_FACH: Success

the UE shall:
(for TDD):

1>clear that entry;
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE establishes radio bearers according to a RADIO BEARER RECONFIGURATION message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
717
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RECONFIGURATION message, to the UE.
The UE configures the common physical channel and transmits a RADIO BEARER RECONFIGURATION
COMPLETE message using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 RADIO BEARER
RECONFIGURATION

2 Void
3 RADIO BEARER


Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9
with the following exceptions.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
718
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
719
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99

After step 2 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
720
8.2.2.18 Radio Bearer Reconfiguration from CELL_FACH to CELL_FACH: Success
(Cell re-selection)

If the UE performs cell re-selection during the reconfiguration procedure, the UE shall:
1>initiate a cell update procedure, as specified in subclause 8.3.1;
1>continue with the reconfiguration procedure.
1>clear that entry;
the UE shall:
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.2.2.8, 8.3.1.7.
To confirm that the UE transmits RADIO BEARER RECONFIGURATION COMPLETE message in cell 2 when a cell
re-selection occurs after receving a RADIO BEARER RECONFIGURATION message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
721
Test Procedure
Table 8.2.2.18
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -75

-75 -60
P-CCPCH
(TDD)
dBm
-60 -75 -75 -60

The UE is in CELL_FACH state in cell 1. The SS configures RB2 to stop transmission and reception of RLC PDUs. On
transmitting a RADIO BEARER RECONFIGURATION message to the UE on RB 1, the SS configures its downlink
transmission power settings according to columns "T1" in table 8.2.2.18. The UE shall initiate the cell reselection
procedure, which may occur either before or after submitting the RADIO BEARER RECONFIGURATION
COMPLETE message for transmission on the DCCH using AM RLC. The UE transmits a CELL UPDATE message on
uplink CCCH with IE "Cell update cause" set to "cell reselection". The SS shall transmit a CELL UPDATE CONFIRM
message on downlink DCCH and configure RB2 to continue transmission and reception of RLC PDUs after receiving
CELL UPDATE message. Any RADIO BEARER RECONFIGURATION COMPLETE message that was previously
submitted for transmission in the UE will now be received by the SS. UE transmit a UTRAN MOBILTY
INFORMATION CONFIRM message on the DCCH using AM RLC. If not already done so, the UE transmits a
RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for generic
NOTE 1: The RADIO BEARER RECONFIGURATION COMPLETE message may be received by the SS either
after reception of CELL UPDATE CONFIRM (Option 1) or after transmitting UTRAN MOBILITY
INFORMATION CONFIRM (Option 2).
NOTE 2: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
722
Expected sequence
UE SS
0 SS The SS configures RB 2 to stop
transmission and reception of
RLC PDUs.
1 RADIO BEARER RECONFIGURATION The message is transmitted on
RB 1.
2 The SS applies the downlink
3 Void
The following messages are
transmitted in cell 2.
be set in IE "cell update cause".
5a SS The SS configures RB 2 to
continue transmission and
reception of RLC PDUs.
5b RADIO BEARER RECONFIGURATION
COMPLETE (Option 1)

CONFIRM

COMPLETE (Option 2)

fails.

Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in clause 9 of TS 34.108,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
723
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
724
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99

TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
725

Use the same message type found in clause 9 of TS 34.108, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

After step 2 the UE shall transmit a CELL UPDATE message on the CCCH with IE "cell update cause" set to "cell
reselection".
After step 5 UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using AM
RLC.
The UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM
RLC. This message may be received by the SS earliest after step 5a and at latest after step 6.
(Subsequently received)

UE shall:
- RADIO BEARER RECONFIGURATION; or

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
726
3>else:

Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a new RADIO BEARER RECONFIGURATION message before the UE configures
the radio bearer according to a previous RADIO BEARER RECONFIGURATION message, it ignores the new RADIO
BEARER RECONFIGURATION message and configures the radio bearer according to the previous RADIO BEARER
RECONFIGURATION message received.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. SS transmits a RADIO BEARER RECONFIGURATION message to the UE before the
UE configures the radio bearer according to the RADIO BEARER RECONFIGURATION message prior to this new
message. The UE ignores the new RADIO BEARER RECONFIGURATION message and configures according to the
former RADIO BEARER RECONFIGURATION message. On completion of radio bearer configuration, the UE shall
transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for
generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RECONFIGURATION Periodic RLC STATUS PDU
transmission is activated.
For FDD, the UL scrambling code
is set to "1". For TDD, the code
combination is assigned by SS.
2 RADIO BEARER RECONFIGURATION Sent before the "activation time"
in step 1 has elapsed. Periodic
RLC STATUS PDU transmission
is not activated.For FDD, the UL
scrambling code is set to "2".For
TDD the code combination
assigned is different to that
assigned in step 1.
COMPLETE
The UE ignores the RADIO
BEARER RECONFIGURATION
message in step 2 and performs
RADIO BEARER
RECONFIGURATION message in
step 1.
4 Void

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
727
RADIO BEARER RECONFIGURATION (Step 1) (FDD and PS Domain)
CELL_DCH from CELL_DCH in PS" as found in TS 34.108 clause 9.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
728
Activation Time [256+Current CFN-[current CFN mod 8 +8
]]MOD 256
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
729
- RB identity 4
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
UL Transport channel information for all transport channels Not Present
DL Transport channel information common for all transport channel Not Present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
730
- CHOICE mode FDD
CHOICE Mode FDD
Downlink information per radio link list Rel-4 or later Not Present
Downlink information per radio link list R99

RADIO BEARER RECONFIGURATION (Step 1) (FDD and CS Domain)
The contents of the RADIO BEARER RECONFIGURATION message in this test case are identical to those specified
for "Speech in CS" or "Non speech in CS" as found in TS 34.108 clause 9.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
731
Activation Time [256+Current CFN-[current CFN mod 8 +8
]]MOD 256
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
732
- RB identity 4
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
DL Transport channel information common for all transport channel Not Present
- CHOICE mode FDD
CHOICE Mode FDD

"Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in TS 34.108 clause 9.1 with the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
733
CHOICE mode TDD
-Downlink information for each radio
link

RADIO BEARER RECONFIGURATION (Step 2) (FDD and PS Domain)
CELL_DCH from CELL_DCH in PS" as found in TS 34.108 clause 9.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
734
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
735
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
DL Transport channel information common for all transport
channel
Not Present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
736
CHOICE channel requirement Uplink DPCH infoN
- CHOICE mode FDD
CHOICE Mode FDD

RADIO BEARER RECONFIGURATION (Step 2) (FDD and CS Domain)
The contents of the RADIO BEARER RECONFIGURATION message in this test case are identical to those specified
for "Speech in CS" or "Non speech in CS" as found in TS 34.108 clause 9.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
737
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
738
- RLC info
- MAX_DAT 15
- Timer_RST 400
- Max_RST 4
- Polling info
- Timer_poll 150
- Poll_SDU 1
- Poll_Window 99
DL Transport channel information common for all transport
channel
Not Present
- CHOICE mode FDD
CHOICE Mode FDD

CELL_DCH from CELL_DCH in PS" found in TS 34.108 clause 9.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
739
CHOICE mode TDD
-Downlink information for each radio
link

using AM RLC.
8.2.2.20 Void

8.2.2.21 Void
8.2.2.22 Void
8.2.2.23 Radio Bearer Reconfiguration from CELL_FACH to CELL_PCH: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
If after state transition the UE enters CELL_PCH state, the UE shall, after the state transition and transmission of the
response message:
2>use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH
Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
740
1>if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:

1>clear that entry;
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE transmits RADIO BEARER RECONFIGURATION COMPLETE message and enters
CELL_PCH state after it received a RADIO BEARER RECONFIGURATION message, which invoke the UE to transit
from CELL_FACH to CELL_PCH.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RECONFIGURATION message. The UE
transmits a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC and enters CELL_PCH
state. SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
UE SS
1 RADIO BEARER
RECONFIGURATION

2 RADIO BEARER

3 SS The UE is in CELL_PCH state.

that UE is in CELL_PCH state,

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
741
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in9 of TS 34.108 with
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
742
RRC State Indicator CELL_PCH
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
743
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
744
After step 1 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on uplink DCCH
using AM RLC.
8.2.2.24 Void
8.2.2.25 Void
(Incompatible Simultaneous Reconfiguration)

If the UE receives:


to TRUE, the UE shall:
1>ignore this second attempt to change the ciphering configuration; and
1>set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to TRUE.
1>set the IE "Reconfiguration" in the variable CIPHERING_STATUS to TRUE;

If the variable INCOMPATIBLE_SECURITY_RECONFIGURATION is set to TRUE due to the received
reconfiguration message, the UE shall:
as specified below:
2>clear that entry;
2>set the IE "failure cause" to the cause value "incompatible simultaneous reconfiguration".
1>set the variable INCOMPATIBLE_SECURITY_RECONFIGURATION to FALSE;
The procedure ends.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
745
Reference
3GPP TS 25.331 clause 8.2.2.12a, clause 8.6.3.4.
1. To confirm that the UE ignores the subsequent security reconfiguration information which is contained in the
RADIO BEARER RECONFIGURATION message.
2. To confirm that the UE reconfigures according to the SECURITY MODE COMMAND message.
3. To confirm that the UE transmits RADIO BEARER RECONFIGURATION FAILURE message on the uplink
DCCH using AM RLC.
4. To confirm that the UE transmits SECURITY MODE COMPLETE message on the uplink DCCH using AM
RLC.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a SECURITY MODE COMMAND message. SS then transmits a
RADIO BEARER RECONFIGURATION message. The UE ignores the RADIO BEARER RECONFIGURATION
message and transmits a RADIO BEARER RECONFIGURATION FAILURE message and configures the radio
bearers according to the SECURITY MODE COMMAND message. On completion of ciphering reconfiguration, the
UE shall transmit a SECURITY MODE COMPLETE message on the DCCH using AM RLC.
Expected sequence
UE SS
1 SECURITY MODE COMMAND This message includes IE
"Ciphering mode info".
2 RADIO BEARER RECONFIGURATION SS send this message before the
activation time in step 1 expires.
This message includes IE
"Ciphering mode info".
FAILURE
The UE ignores the ciphering
mode information in step 2.
4 SECURITY MODE COMPLETE

If the initial state of the UE is state 6-9, use the message sub-type in clause 9 of TS 34.108, with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
746
Ciphering mode info

- Ciphering algorithm Use one of the supported ciphering algorithms
- Ciphering activation time for DPCH (256+CFN-(CFN MOD 8 +8))MOD 256
info

- RB identity 1
- RLC sequence number Current RLC SN+X (Note 1)
- RB identity 2
- RLC sequence number Current RLC SN+4
- RB identity 3
- RB identity 4

If the initial state of the UE is state 6-10, use the message sub-type in clause 9 of TS 34.108, with the following
exceptions:
Ciphering mode info

info

- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

RADIO BEARER RECONFIGURATION (for Step 2)
If the initial state of the UE is state 6-9, use the message sub-type entitled "Speech in CS" or "Non-speech in CS" in
clause 9 of TS 34.108, with the following exceptions:
Ciphering mode info

info

- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
747
If the initial state of the UE is state 6-10, use the message sub-type entitled "Packet to CELL_DCH from CELL_DCH
in PS" in clause 9 of TS 34.108, with the following exceptions:
Ciphering mode info

info

- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

Note 1: X is set to 1.
RADIO BEARER RECONFIGURATION FAILURE (for Step 3)
Check that the message received is the same as the message sub-type found in clause 9 of TS 34.108, with the following
exceptions:
Failure cause incompatible simultaneous reconfiguration

AM RLC and set the failure cause to "incompatible simultaneous reconfiguration".
After step 3 the UE shall transmit a SECURITY MODE COMPLETE message on the DCCH using AM RLC specified
in step 1.
8.2.2.27 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH

If the UE receives:
-a RADIO BEARER RECONFIGURATION message;
it shall:
1>perform the physical layer synchronisation procedure as specified in TS 25.214 for FDD and TS 25.224 for
TDD;
1>act upon all received information elements as specified in TS25.331 subclause 8.6, unless specified in the following
and perform the actions below.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
748
In case the UE receives a RADIO BEARER RECONFIGURATION message including the IE "RB information to
reconfigure" that only includes the IE "RB identity", the UE shall:
1>handle the message as if IE "RB information to reconfigure" was absent.
UE shall:
configuration.
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_DCH according to the RADIO BEARER
RECONFIGURATION message.
2. To confirm that the UE transmits the RADIO BEARER RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC on a dedicated physical channel in a different frequency.
Initial Condition
UE: CS-DCCH_DTCH_DCH (state 6-9) or PS_DCCH_DTCH_DCH (state 6-10) as specified in clause 7.4 of TS
Test Procedure
Table 8.2.2.27
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

columns "T0" in table 8.2.2.27. For FDD mode, the SS switches its downlink transmission power settings to columns
"T1" and transmits a RADIO BEARER RECONFIGURATION message including IE "Frequency info" set to
frequency information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code which is assigned to P-
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
749
CPICH of cell 6. For TDD mode, the SS switches its downlink transmission power settings to columns "T1" and
transmits a RADIO BEARER RECONFIGURATION message including IE "Frequency info" set to frequency
information of cell 6 and IE "Primary CCPCH info" set to cell 6 parameters. The UE shall selects cell 6 and reconfigure
its radio access bearer after receiving this message, and then remains in CELL_DCH state. The UE transmits a RADIO
BEARER RECONFIGURATION COMPLETE message using AM RLC after complete configuration according to
receiving RADIO BEARER RECONFIGURATION message. Upon completion of the procedure, the SS calls for
Expected sequence
UE SS
CELL_DCH state of cell 1 and the
SS has configured its downlink
8.2.2.27.
3 RADIO BEARER RECONFIGURATION Including IE "Frequency info" set
and IE "Primary CPICH info" set
to Primary Scrambling Code
assigned to P-CPICH of cell 6 for
FDD mode or IE "Primary CCPCH
info" set to cell 6 parameters.
COMPLETE
6.

The contents RADIO BEARER RECONFIGURATION message in this test case is identical the message sub-type
indicated by "Packet to in PS" or "Speech in CS" or "Non speech from CELL_DCH to CELL_DCH in CS" in [9] TS
34.108 clause 9, with the following exception:
Frequency info
CHOICE mode FDD

The contents RADIO BEARER RECONFIGURATION message in this test case is identical the message sub-type
indicated by "Packet to in PS" or "Speech in CS" or "Non speech from CELL_DCH to CELL_DCH in CS" in [9] TS
34.108 clause 9, with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
750
Frequency info
CHOICE mode TDD

using AM RLC in cell 6.
After step 4 the UE shall be in CELL_DCH state in cell 6.
8.2.2.28 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_FACH
(Transport channel type switching with frequency band modification):
Success

If the UE receives:
it shall:

1>if the received reconfiguration message included the IE "Primary CPICH info" for FDD or the IE"Primary
CCPCH info" for TDD, and the UE selects another cell than indicated by this IE:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
751
1>transmit a RADIO BEARER RECONFIGURATION COMPLETE on the uplink DCCH using AM RLC, using
the new configuration after the state transition.
Reference
3GPP TS 25.331 clause 8.2.2.
1. To confirm that the UE transits from CELL_DCH to CELL_FACH according to the RADIO BEARER
2. To confirm that the UE transmits RADIO BEARER RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC on a common physical channel in a different frequency.
Initial Condition
System Simulator: 2 cells Cell 1 in active and cell 6 is inactive.
domain supported by the UE If the UE supports both CS and PS domains, the initial UE state shall be "Registered idle
mode on CS/PS" (state 7).
Test Procedure
Table 8.2.2.28
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

columns "T0" in table 8.2.2.28. SS requests operator to make an outgoing call. The SS and UE execute procedure P5.
Next The SS and the UE execute procedure P9 and then execute procedure P13. For FDD mode, the SS switches its
downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RECONFIGURATION
message including IE "Frequency info" set to frequency information of cell 6 and IE "Primary CPICH info" set to
Primary Scrambling Code assigned to P-CPICH of cell 6. For TDD mode, the SS switches its downlink transmission
power settings to columns "T1" and transmits a RADIO BEARER RECONFIGURATION message including IE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
752
"Frequency info" set to frequency information of cell 6 and IE "Primary CCPCH info" set to cell 6 parameters. On
receiving the RADIO BEARER RECONFIGURATION message, the UE shall select cell 6 and transmit a RADIO
BEARER RECONFIGURATION COMPLETE message using AM RLC after complete configuration according to the
RADIO BEARER RECONFIGURATION message. Upon completion of the procedure, the SS calls for generic
Expected sequence
UE SS
"T0" in table 8.2.2.28. SS
requests operator to make an
outgoing call.
7.4.2.2.2) specified in TS 34.108.

3 SS executes procedure) P9 (clause
7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 RADIO BEARER
RECONFIGURATION
Including IE "Frequency info"
FDD mode or IE "Primary
CCPCH info" set to cell 6
parameters.
7 RADIO BEARER
on the common physical channel
in cell 6.
8 CALL C.2 f the test result of C.2 indicates

Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9with
Frequency info
CHOICE mode FDD
Downlink information for each radio link

Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9with
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
753
Frequency info
CHOICE mode TDD

After step 6 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC.
After step 7 the UE shall be in CELL_FACH state.
8.2.2.29 Void
8.2.2.30 Void
8.2.2.31 Radio Bearer Reconfiguration for transition from CELL_FACH to CELL_DCH

If the UE receives:

-a RADIO BEARER RECONFIGURATION message; or

it shall:

procedure:

NOTE: The RADIO BEARER RECONFIGURATION message always includes the IE "RB information to
reconfigure". UTRAN has to include it even if it does not require the reconfiguration of any RB.

1>in FDD; or
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
754
1>in TDD when "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not
specified:

1>transmit a RADIO BEARER RECONFIGURATION COMPLETE message on the uplink DCCH using AM
RLC.

Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
1. To confirm that the UE transits from CELL_FACH to CELL_DCH according to the RADIO BEARER
DCCH using AM RLC on a dedicated physical channel in a different frequency.
Initial Condition
UE: PS_DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.2.2.31
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60

Off -60
P-CCPCH
RSCP
(TDD)
dBm
-60 -60

Off -60

to columns "T0" in table 8.2.2.31. For FDD mode, the SS switches its downlink transmission power settings to columns
"T1" and transmits a RADIO BEARER RECONFIGURATION message IE "Frequency info" set to frequency
information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 6. For
TDD mode, the SS switches its downlink transmission power settings to columns "T1" and transmits a RADIO
BEARER RECONFIGURATION message including IE "Frequency info" set to frequency information of cell 6 and IE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
755
"Primary CCPCH info" set to cell 6 parameters. The UE shall select cell 6 and then enter CELL_DCH state according
to receiving RADIO BEARER RECONFIGURATION message. Finally the UE shall transmit a RADIO BEARER
RECONFIGURATION COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for
generic procedure C.3 to check that UE is in CELL_DCH state in cell 6.
Expected sequence
UE SS
1 The UE is in CELL_FACH state of
in table 8.2.2.31.
COMPLETE
6.
5 Call C.3 If the test result of C.3 indicates
that UE is in CELL_DCH state in
cell 6, the test passes, otherwise
it fails.

RADIO BEARER RECONFIGURATION (Step 3 for FDD)
The contents of RADIO BEARER RECONFIGURATION message in this test case are identical the message sub-type
indicated by "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following
exception:
Frequency info
CHOICE mode FDD

RADIO BEARER RECONFIGURATION (Step 3 for TDD)
exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
756
Frequency info
CHOICE mode TDD

8.2.2.32 Radio Bearer Reconfiguration for transition from CELL_FACH to
CELL_FACH (Frequency band modification): Success

If the UE receives:
it shall:
the UE shall:
(for TDD):
4>proceed as below.
using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
757
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_FACH according to the RADIO BEARER
DCCH using AM RLC on a common physical channel in a different frequency.
Initial Condition
mode on CS/PS".
Test Procedure
Table 8.2.2.32
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

to columns "T0" in table 8.2.2.32. SS requests operator to make an outgoing call. The SS and UE execute procedure P6.
"Frequency info" set to frequency information of cell 6 and IE "Primary CCPCH info" set to cell 6 parameters. The UE
shall select cell 6 and transmits a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC
after it completes configuration according to the received RADIO BEARER RECONFIGURATION message. Upon
completion of the procedure, the SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
758
Expected sequence
UE SS
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

COMPLETE
6.

indicated by "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following
exception:
Frequency info
CHOICE mode FDD

indicated by "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following
exception:
Frequency info
CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
759
8.2.2.33 Void
8.2.2.34 Radio Bearer Reconfiguration for transition from CELL_FACH to URA_PCH

If the UE receives:
it shall:
1>transmit a RADIO BEARER RECONFIGURATION COMPLETE on the uplink DCCH using AM RLC, using
the old configuration before the state transition.
If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the
response message:
1>prohibit periodical status transmission in RLC;
1>clear the variable C_RNTI;
Monitoring Occasion as specified in TS25.331 subclause 8.6.3.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
760
2>keep the configuration existing before the reception of the message and transmit a failure response message
as specified in TS25.331subclause 8.2.2.9
1>if the UE enters URA_PCH state, and after cell selection the criteria for URA update caused by "URA
reselection" according to subclause TS25.331 8.3.1 is fulfilled:
2>initiate a URA update procedure according to TS25.331 subclause 8.3.1 using the cause "URA reselection";
2>when the URA update procedure is successfully completed:
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transmits a RADIO BEARER RECONFIGURATION COMPLETE message on
the uplink DCCH using AM RLC.
2. To confirm that the UE transits from CELL_FACH to URA_PCH according to the RADIO BEARER
3. To confirm that the UE selects a common physical channel in a different frequency.
Initial Condition
System Simulator: 2 cellsCell 1 is active and cell 6 are active
UE: Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN
Test Procedure
Table 8.2.2.34
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
P-CCPCH
RSCP
(TDD)
dBm
-55 -72

Off -55

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
761
"Frequency info" set to frequency information of cell 6 and IE "Primary CCPCH info" set to cell 6 parameters. The UE
shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC and enter URA_PCH
state of cell 6. Upon completion of the procedure, the SS calls for generic procedure C.5 to check that UE is in
URA_PCH state.
Expected sequence
UE SS
1 System Information Block type 11 The UE is in idle mode and
camped on cell 1. The contents
of System Information Block type
11 message are different from
the default settings and the SS
has configured its downlink
table 8.2.2.34. SS requests
operator to make an outgoing
call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

FDD mode or IE "Primary
CCPCH info" set to cell 6
parameters.
COMPLETE
The UE transmit this message
on the common physical
channel. n cell 1.
that UE is in URA_PCH state,
the test passes, otherwise it fails

with following exceptions:
Frequency info
CHOICE mode FDD
- UARFCN uplink (Nu) Same uplink UARFCN as used for cell 6
- UARFCN downlink (Nd) Same downlink UARFCN as used for cell 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
762
Frequency info
CHOICE mode TDD

After step 6 the UE shall transmits a RADIO BEARER RECONFIGURATION COMPLETE message on the DCCH
After step 8 the UE shall be in URA_PCH state in cell 6.
8.2.2.35 Radio Bearer Reconfiguration from CELL_DCH to CELL_FACH: Successful
channel switching with multiple PS RABs established

If the IE "RB information to release" is included, the UE shall apply the following actions on the radio bearer identified
with the value of the IE "RB identity". The UE shall:
1>if the IE "RB identity" is set to a value less than 4:
1>if the IE "RB identity" refers to a signalling radio bearer:
2>release the RLC entity for the signalling radio bearer;
2>delete the information about the signalling radio bearer from the variable ESTABLISHED_RABS.
1>if the IE "RB identity" refers to a radio bearer:
2>release the PDCP and RLC entities for that radio bearer;
2>indicate release of the RAB subflow associated with the radio bearer to upper layers;
2>delete the information about the radio bearer from the variable ESTABLISHED_RABS;
2>when all radio bearers belonging to the same radio access bearer have been released:
3>indicate release of the radio access bearer to upper layers providing the "CN domain identity" together
with the "RAB identity" stored in the variable ESTABLISHED_RABS;
3>delete all information about the radio access bearer from the variable ESTABLISHED_RABS.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
763
If the IE "RB mapping info" is included, the UE shall:
1>for each multiplexing option of the RB:
2>if a transport channel that would not exist as a result of the message (i.e. removed in the same message in IE
"Deleted DL TrCH information" and IE "Deleted UL TrCH information") is referred to:
2>if a multiplexing option that maps a logical channel corresponding to a TM-RLC entity onto RACH, CPCH,
FACH or DSCH is included:
2>if the multiplexing option realises the radio bearer on the uplink (resp. on the downlink) using two logical
channels with different values of the IE "Uplink transport channel type" (resp. of the IE "Downlink transport
channel type"):
2>if that RB is using TM and the IE "Segmentation indication" is set to TRUE and, based on the multiplexing
configuration resulting from this message, the logical channel corresponding to it is mapped onto the same
transport channel as another logical channel:
2>if the transport channel considered in that multiplexing option is different from RACH and if that RB is using
AM and the set of RLC sizes applicable to the logical channel transferring data PDUs has more than one
element:
2>if that RB is using UM or TM and the multiplexing option realises it using two logical channels:
2>for each logical channel in that multiplexing option:
3>if the value of the IE "RLC size list" is set to "Explicit list":
4>if a "Transport format set" for the transport channel this logical channel is mapped on in this
multiplexing option is included in the same message, and the value (index) of any IE "RLC size
index" in the IE "Explicit list" does not correspond to an "RLC size" in the IE transport format set of
that transport channel given in the message; or
4>if the transport channel this logical channel is mapped on in this multiplexing option is different from
RACH, and if a "Transport format set" for that transport channel is not included in the same message,
and the value (index) of any IE "RLC size index" in the IE "Explicit list" does not correspond to an
"RLC size" in the stored transport format set of that transport channel; or
multiplexing option is included in the same message, and the value of any IE "Logical channel list" in
the transport format set is not set to "Configured"; or
multiplexing option is not included in the same message, and the value of any IE "Logical channel
list" in the stored transport format set of that transport channel is not set to "Configured":
3>if the value of the IE "RLC size list" is set to "All":
4>if the transport channel this logical channel is mapped on is RACH; or
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
764
multiplexing option is included in the same message, and the value of any IE "Logical channel list" in
the transport format set is not set to "Configured"; or
multiplexing option is not included in the same message, and the value of any IE "Logical channel
list" in the stored transport format set of that transport channel is not set to "Configured":
3>if the value of the IE "RLC size list" is set to "Configured":
4>if the transport channel this logical channel is mapped on is RACH; or
multiplexing option is included in the same message, and for none of the RLC sizes defined for that
transport channel in the "Transport format set", the "Logical Channel List" is set to "All" or given as
an "Explicit List" which contains this logical channel; or
multiplexing option is not included in the same message, and for none of the RLC sizes defined in the
transport format set stored for that transport channel, the "Logical Channel List" is set to "All" or
given as an "Explicit List" which contains this logical channel:
1>if, as a result of the message this IE is included in, several radio bearers can be mapped onto the same transport
channel, and the IE "Logical Channel Identity" was not included in the RB mapping info of any of those radio
bearers for a multiplexing option on that transport channel or the same "Logical Channel Identity" was used
more than once in the RB mapping info of those radio bearers for the multiplexing options on that transport
channel:
1>delete all previously stored multiplexing options for that radio bearer;
1>store each new multiplexing option for that radio bearer;
1>if the IE "Uplink transport channel type" is set to the value "RACH":
2>refer the IE "RLC size index" to the RACH Transport Format Set of the first PRACH received in the IE
"PRACH system information list" received in System Information Block type 5 or System Information Block
type 6.
1>determine the sets of RLC sizes that apply to the logical channels used by that RB, based on the IEs "RLC size
list" and/or the IEs "Logical Channel List" included in the applicable "Transport format set" (either the ones
received in the same message or the ones stored if none were received); and
1>in case the selected multiplexing option is a multiplexing option on RACH:
2>ignore the RLC size indexes that do not correspond to any RLC size within the Transport Format Set stored
for RACH.
1>if RACH is the transport channel to be used on the uplink, if that RB has a multiplexing option on RACH and if
it is using AM:
2>apply the largest size amongst the ones derived according to the previous bullet for the RLC size (or RLC
sizes in case the RB is realised using two logical channels) for the corresponding RLC entity.
NOTE: The IE "RB mapping info" is only included in IE "Predefined RB configurations" in system information
when used for Inter-RAT handover to UTRAN and there is no AM RLC size change involved in this
case.
1>if that RB is using AM and the RLC size applicable to the logical channel transporting data PDUs is different
from the one derived from the previously stored configuration:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
765
2>re-establish the corresponding RLC entity;
2>configure the corresponding RLC entity with the new RLC size;
2>for each AM RLC radio bearer in the CN domain as indicated in the IE "CN domain identity" in the IE "RAB
info" in the variable ESTABLISHED_RABS whose RLC size is changed; and
2>for each AM RLC signalling radio bearer in the CN domain as indicated in the IE "CN domain identity" in
the variable LATEST_CONFIGURED_CN_DOMAIN whose RLC size is changed:
3>if the IE "Status" in the variable CIPHERING_STATUS of this CN domain is set to "Started":
4>if this IE was included in CELL UPDATE CONFIRM:
5>set the HFN values for the corresponding RLC entity equal to the value of the IE "START"
included in the latest transmitted CELL UPDATE message for this CN domain.
4>if this IE was included in a reconfiguration message:
5>set the HFN values for the corresponding RLC entity equal to the value of the IE "START" that
will be included in the reconfiguration complete message for this CN domain.
1>if that RB is using UM:
2>indicate the largest applicable RLC size to the corresponding RLC entity.
1>configure MAC multiplexing according to the selected multiplexing option (MAC multiplexing shall only be
configured for a logical channel if the transport channel it is mapped on according to the selected multiplexing
option is the same as the transport channel another logical channel is mapped on according to the multiplexing
option selected for it);
1>configure the MAC with the logical channel priorities according to selected multiplexing option;
1>configure the MAC with the set of applicable RLC Sizes for each of the logical channels used for that RB;
1>if there is no multiplexing option applicable for the transport channels to be used in the RRC state indicated in
the IE "RRC State Indicator" included in the received message:
1>if there is more than one multiplexing option applicable for the transport channels to be used in the RRC state
indicated in the IE "RRC State Indicator" included in the received message:
In case IE "RLC info" includes IE "Downlink RLC mode " ("DL RLC logical channel info" is mandatory present) but
IE "Number of downlink RLC logical channels" is absent in the corresponding IE "RB mapping info", the parameter
values are exactly the same as for the corresponding UL logical channels. In case two multiplexing options are specified
for the UL, the first options shall be used as default for the DL. As regards the IE "Channel type", the following rule
should be applied to derive the DL channel type from the UL channel included in the IE:
Channel used in UL DL channel type implied by
" same as"
DCH DCH
RACH FACH
CPCH FACH
USCH DSCH

If ciphering is applied, UTRAN should not map Transparent Mode RBs of different CN domains on the same transport
channel. In such case the UE behaviour is not specified.
Reference
3GPP TS 25.331 clause 8.6.4.6, 8.6.4.8.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
766
To confirm that the UE transit from CELL_DCH to CELL_FACH state according to a RADIO BEARER
RECONFIGURATION message when having two radio access bearers established.
To confirm that the UE transit from CELL_FACH to CELL_DCH state according to a RADIO BEARER
RECONFIGURATION message when having two radio access bearers established.
To confirm that the UE release two radio access bearers included in a single RADIO BEARER RELEASE message.
Initial Condition
UE: PS-DCCH +DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108
Support of PS service Yes/No
Secondary PDP context activation procedure Yes/No
Test Procedure
The UE is in CELL_DCH state of cell 1. The UE initiates the activation of a second PDP context, upon which the SS
establishes a PS domain RAB and confirms the PDP context activation.
Next, the SS transmits a RADIO BEARER RECONFIGURATION message to move the UE to CELL_FACH state.
The UE shall apply the new configuration and return the RADIO BEARER RECONFIGURATION COMPLETE
message.
The SS will then transmit a RADIO BEARER RECONFIGURATION message to move the UE to CELL_DCH state.
The UE shall apply the new configuration and return the RADIO BEARER RECONFIGURATION COMPLETE
message.
A DEACTIVATE PDP CONTEXT REQUEST message is then sent by the SS to request the UE to deactivate both PDP
contexts. The UE shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. After this procedure, the SS
transmits a RADIO BEARER RELEASE. The UE shall release both radio bearers and transmit a RADIO BEARER
RELEASE COMPLETE message on the uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
767
Expected sequence
UE SS
CELL_DCH state of cell 1.
(ACTIVATE SECONDARY PDP
CONTEXT REQUEST)
SM
3 RADIO BEARER SETUP Establishment of second PS
domain RAB
(ACTIVATE SECONDARY PDP
CONTEXT ACCEPT)
SM
6 RADIO BEARER RECONFIGURATION To move the UE to CELL_FACH/
URA_PCH. RB reconfiguration
procedure is used to:
Modify RLC timer values
The message includes a C-RNTI
and the Primary Scrambling
code of cell 1.
COMPLETE

8 RADIO BEARER RECONFIGURATION To move the UE to CELL_DCH.
RB reconfiguration procedure is
used to:
Re- specify the DCH
configuration (don't re- use
stored multiplexing option)
Modify RLC timer values
COMPLETE

10 DEACTIVATE PDP CONTEXT REQUEST Request a deactivation both
PDP contexts
11 DEACTIVATE PDP CONTEXT ACCEPT Accept the PDP context
deactivation
12 RADIO BEARER RELEASE Release of two PS domain RABs
13 RADIO BEARER RELEASE COMPLETE

For Steps 2, 3, 4, 5 see also Test Case 12.9.13 "Service Request / RAB re-establishment / UE initiated / multiple PDP
contexts" for additional details.
The contents of RADIO BEARER SETUP message in this test case are identical the message sub-type indicated by
"Packet to CELL_DCH from CELL_DCH in PS" in [9] TS 34.108 clause 9, with the following exception :
RB information to setup
- RB identity 21

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
768
indicated by "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9, with the following
exception:
New C-RNTI 0000 0000 0000 0001B
- RB identity 20
- RLC info
- CHOICE SDU discard mode No Discard
- MAX_DAT 15
- Timer_RST 700
- Max_RST 6
- Timer_status_prohibit Not Present
- Missing PDU indicator FALSE
- RB identity 21
- RLC info
- MAX_DAT 15
- Timer_RST 700
- Max_RST 6

indicated by "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9, with the following
exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
769
New C-RNTI 0000 0000 0000 0001B
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 700
- Max_RST 6
- RB identity 21
- RLC info
- MAX_DAT 15
- Timer_RST 700
- Max_RST 6

exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
770
New C-RNTI 0000 0000 0000 0001B
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
- RB identity 21
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
771
- RB mapping info

exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
772
New C-RNTI 0000 0000 0000 0001B
- RB identity 20
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
- RB identity 21
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
773
- RB mapping info

RADIO BEARER RELEASE (Step 12)
indicated by " Contents of RADIO BEARER RELEASE message: AM or UM " in [9] TS 34.108 clause 9, with the
following exception:
- RB identity 20
- RB identity 21

After step 12 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.2.36 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH:
Success (Start and stop of HS-DSCH reception)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
774

If the IE "Downlink HS-PDSCH Information" is not included, the UE shall:
1>set the variable HS_DSCH_RECEPTION to FALSE;
1>stop HS-DSCH reception procedures according to the stored HS-PDSCH configuration.
Reference
3GPP TS 25.331 clauses, 8.6.3.1, 8.6.6.32
1. To confirm that the UE starts and stops receiving the HS-DSCH according to the received RADIO BEARER
2. To confirm that the UE uses the stored HS-DSCH configuration when the HS-DSCH reception is started.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
775
Initial Condition
UE: PS_DCCH_DTCH_HS_DSCH (state 6-17) as specified in clause 7.4 of TS 34.108.
- UE supports FDD
Test Procedure
The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established. The SS transmits a RADIO
BEARER RECONFIGURATION message instructing the UE to stop the reception of HS_DSCH. The UE transmits a
RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC.
The SS transmits a RADIO BEARER RECONFIGURATION message instructing the UE to start the reception of
HS_DSCH. The UE transmits a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC.
SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RECONFIGURATION Stop of HS-DSCH reception
2 At the activation time, SS stops
HS-DSCH transmission to the UE.
COMPLETE

4 RADIO BEARER RECONFIGURATION Start of HS-DSCH reception
5 At the activation time, SS
resumes HS-DSCH transmission
to the UE.
COMPLETE

CALL C.3 If the test result of C.3 indicates

Use the same message as specified for "Packet to CELL_DCH from CELL_DCH in PS" in 34.108, except for the
following.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
776
- RB information to reconfigure (high-speed AM DTCH)
- RB identity 23
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Windows 99
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH in PS" in 34.108 except for the
following:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
777
- RB identity 23
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 100
- Poll_SDU 1
- Poll_Windows 99
Downlink HS-PDSCH Information
- HS-SCCH Info Not present
- Measurement Feedback Info Not present
- CHOICE mode FDD (no data)

8.2.2.37 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_FACH
and from CELL_FACH to CELL_DCH: Success (start and stop of HS-DSCH
reception)
If after state transition the UE leaves CELL_DCH state, the UE shall, after the state transition:
1>stop any HS-DSCH reception procedures according to the stored HS-PDSCH configuration;
1>clear any stored HS-PDSCH configuration;
1>remove any H-RNTI stored;
1>clear the variable H_RNTI;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
778
1>set the variable HS_DSCH_RECEPTION to FALSE.

Reference
3GPP TS 25.331 clauses 8.2.2.3, 8.6.6.32
To confirm that the UE transits to CELL_FACH state from CELL_DCH state and stops receiving the HS-DSCH
according to the received RADIO BEARER RECONFIGURATION message.
To confirm that the UE transits to CELL_DCH state from CELL_FACH state and starts receiving the HS-DSCH
according to the received RADIO BEARER RECONFIGURATION message.
Initial Condition
- UE supports FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
779
Test Procedure
The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established. The SS transmits a RADIO
BEARER RECONFIGURATION message to the UE. After the UE receives this message, it stops HS-DSCH reception,
moves to CELL_FACH state and transmits a RADIO BEARER RECONFIGURATION COMPLETE message using
AM RLC.
Then, SS transmits a RADIO BEARER RECONFIGURATION message to the UE. After the UE receives this message,
it moves to CELL_DCH state, resumes HS-DSCH reception and transmits a RADIO BEARER RECONFIGURATION
COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RECONFIGURATION Stop of HS-DSCH reception and
transit to CELL_FACH state,
COMPLETE

3 RADIO BEARER RECONFIGURATION Start of HS-DSCH reception and
transit to CELL_DCH state
COMPLETE


Use the same message as specified for "Packet to CELL_FACH from CELL_DCH in PS" in 34.108, except for the
following:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
780
New C-RNTI 0000 0000 0000 0001B
- RB identity 2
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 3
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB identity 4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
781
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99
- RB information to reconfigure (High-speed AM DTCH)
- RB identity 23
- RLC info
- MAX_DAT 15
- Timer_RST 600
- Max_RST 4
- Polling info
- Timer_poll 250
- Poll_SDU 1
- Poll_Window 99

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
782
Use the same message as specified for "Packet to CELL_DCH from CELL_FACH in PS" in 34.108 except for the
following:
New H-RNTI '1010 1010 1010 1010'
- RB identity 23
- RLC info
- MAX_DAT 15
- Timer_RST 500
- Max_RST 4
- Polling info
- Timer_poll 100
- Poll_SDU 1
- Poll_Windows 99
- HS-SCCH Info
- CHOICE mode FDD
- DL Scrambling Code
- HS-SCCH Channelisation Code Information
- HS-SCCH Channelisation Code 1
- Measurement Feedback Info
- CHOICE mode FDD
- POhsdsch 6 dB
- CQI Feedback cycle, k 4 ms
- CQI repetition factor 1
- DCQI -3 dB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
783
8.2.3 Radio Bearer Release
Success

If the UE receives:
- a RADIO BEARER RELEASE message; or
it shall:
1>perform the physical layer synchronisation procedure as specified in TS 25.214;
The UE shall then:
UE shall:
configuration.
1>clear that entry;

In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1>transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM
RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE releases the existing radio bearer according to a RADIO BEARER RELEASE message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
784
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases
the radio access bearer and transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using
Expected sequence
UE SS
2 RADIO BEARER RELEASE COMPLETE Release the radio bearer.

RADIO BEARER RELEASE
None.
8.2.3.2 Void
8.2.3.3 Void
8.2.3.4 Void
8.2.3.5 Void
8.2.3.6 Void
8.2.3.7 Radio Bearer Release for transition from CELL_DCH to CELL_FACH:
Success

If the UE receives:
it shall:
procedure:
2>perform the physical layer synchronisation procedure A as specified in TS 25.214;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
785
The UE shall then:
transmission";
4>proceed as below.
transmission";
4>proceed as below.
1>clear that entry;

RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
786
To confirm that the UE release the existing the radio bearer according to a RADIO BEARER RELEASE message.
Initial Condition
UE: PS-DTCH+DCCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases
AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 RADIO BEARER RELEASE SS releases the radio bearer in
the fashion specified in the
message and allocate common
channel resources to carry the
remaining radio bearers.
2 The UE selects PRACH and S-
CCPCH indicated in SIB5 and
SIB6 after entering CELL FACH
state.
The UE shall release dedicated
channels, and reconfigure the
remaining radio bearers using
the common channel.

Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with
New C-RNTI 0000 0000 0000 0001B

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
787
8.2.3.8 Radio Bearer Release for transition from CELL_DCH to CELL_FACH:
Success (Cell re-selection)

If the UE receives:
it shall:
procedure:
The UE shall then:
2>select a suitable UTRA cell according to TS 25.304
transmission";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
788
the UE shall:

1>clear that entry;
RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.3.1.7.
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message after the UE completes a cell
update procedure.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to request the UE to transit
from CELL_DCH to CELL_FACH. The UE initiates the cell update procedure because the UE cannot detect the
specified cell in this message. The UE transmits a CELL UPDATE message on uplink CCCH with IE "Cell update
cause" set to "cell reselection". The SS shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after
receiving CELL UPDATE message. The UE then transmit a UTRAN MOBILITY INFORMATION CONFIRM
message on the DCCH using AM RLC. The UE transmits a RADIO BEARER RELEASE COMPLETE message on the
DCCH using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
789
Expected sequence
UE SS
1 Void
2 Void
3 RADIO BEARER RELEASE Assigned the transition from
CELL_DCH to CELL_FACH
be set in IE "cell update cause".
CONFIRM

fails.

RADIO BEARER RELEASE (Step 3) (FDD)

RADIO BEARER RELEASE (Step 3) (TDD)
- Cell parameters ID 4

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in [9]

Use the same message type found in clause [9] TS 34.108 clause 9, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
790
reselection".
RLC.
After step 6 UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC.
8.2.3.9 Radio Bearer Release for transition from CELL_FACH to CELL_DCH:
Success

If the UE receives:
it shall:
procedure:
The UE shall then:
1>clear that entry;

RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that an UE, in state CELL_FACH, releases the radio access bearers using common physical channel. After
the release, it shall access the affected radio bearers on the DPCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
791
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RELEASE message to the UE. In this message,
SS commands the UE to release radio access bearers on common physical channel. At the same time, SS allocates
DPCH to support the affected radio bearers. The UE shall release the indicated radio access bearers and transmit a
RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic
Expected sequence
UE SS
2 UE shall release the radio
access bearers carried by
common physical channel.

Use the same message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9.
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message using the dedicated physical
channel allocated.
8.2.3.10 Void
8.2.3.11 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Failure
(Physical channel failure and successful reversion to old configuration)


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
792

as specified below:
2>clear that entry;

The UE shall:
1>in case of reception of a RADIO BEARER RELEASE message:

2>transmit a RADIO BEARER RELEASE FAILURE as response message on the DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration and transmits a RADIO BEARER RELEASE FAILURE
message on the DCCH using AM RLC if the UE fails to release the radio bearers in accordance with the specified
settings in RADIO BEARER RELEASE message before T312 timer expires.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
793
Test Procedure
message back to SS. The SS transmits a RADIO BEARER RELEASE message and keeps its current physical channel
configuration. The UE is expected to encounter a failure while releasing the radio bearer. After T312 timer expires, the
UE shall revert to the old radio bearer configuration, so the UE transmits a RADIO BEARER RELEASE FAILURE
message on the DCCH using AM RLC which is set to "physical channel failure" in IE "failure cause". UE shall
continue its traffic volume measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
measurement.
2 The SS does not configure the
specified L1.
3 RADIO BEARER RELEASE FAILURE After T312 expiry the UE fails to
release a radio bearer and reverts
to the old configuration.

Mode

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
794
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in Clause 9 of TS 34.108.
RADIO BEARER RELEASE FAILURE (Step 2)
The contents of RADIO BEARER RELEASE FAILURE message in this test case is the same as the RADIO BEARER
RELEASE FAILURE message as found in Clause 9 of TS 34.108, with the following exceptions:

After step 2 the UE shall transmit a RADIO BEARER RELEASE FAILURE message on the DCCH using AM RLC,
setting the value "physical channel failure" in IE "failure cause".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
795
8.2.3.12 Void
8.2.3.13 Void
8.2.3.14 Void
8.2.3.15 Radio Bearer Release for transition from CELL_FACH to CELL_FACH:
Success

If the UE receives:
it shall:
procedure:
The UE shall then:
the UE shall:
1>clear that entry;

RLC.
If the IE "RAB information to reconfigure" is included then the UE shall:
1> if the entry for the radio access bearer identified by the IE "CN domain identity" together with the IE "RAB
Identity" in the variable ESTABLISHED_RABS already exists:

1> else:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
796
1>transmit a failure response message, setting the information elements as specified below:
3>clear that entry.
The procedure ends.

2>if the radio bearer reconfiguration procedure affects several radio bearers:
3> (may) include the identities of the radio bearers for which the procedure would have been successful into
the RADIO BEARER RECONFIGURATION FAILURE message.
AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.4.2a, 8.2.2.11, 8.2.2.9.
To confirm that the UE releases the existing the radio bearer(s) according to the RADIO BEARER RELEASE message.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases
AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
797
Expected sequence
UE SS
2 Void
4 RADIO BEARER RECONFIGURATION The IE "RAB information to
reconfigure" is included with the
same RAB identity as was
released with the RADIO
BEARER RELEASE message.
FAILURE
The UE responds with failure, in
case the RB is properly removed

Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9.
title "Packet to CELL_FACH from CELL_FACH in PS" as found in clause 9 of TS 34.108 with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
798
Message Type
- message authentication code SS calculates the value of MAC-I for this message and
- RRC message sequence number SS provides the value of this IE, from its internal counter.
Activation time Now
New U-RNTI Not Present
RRC State indicator CELL_FACH
UTRAN DRX cycle length coefficient Not Present
CN information info Not Present
URA identity Not Present
RAB information to reconfigure list
- RAB information to reconfigure (AM DTCH for PS domain)
- NAS Synchronization Indicator 0101B
significant bit of the NAS Synchronisation Indicator.
RB information to reconfigure list TS25.331 specifies that "Although this IE is not always
required, need is MP to align with ASN.1".
- RB information to reconfigure (Dummy)
- RB identity 1
- RLC info Not Present
RB information to be affected list Not Present
channels
Not Present
Deleted TrCH information list Not Present
Added or Reconfigured TrCH information list Not Present
Deleted DL TrCH information list Not Present
Added or Reconfigured DL TrCH information list Not Present
CHOICE Mode FDD

RADIO BEARER RECONFIGURATION FAILURE (step 5)
RADIO BEARER RECONFIGURATION FAILURE message as found in [9] TS 34.108 clause 9, with the following
exceptions:

After step 1 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC on the
common physical channel.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
799
After step 4, UE shall transmit a RADIO BEARER RECONFIGURATION FAILURE message to verify that the RAB
is properly removed.

UE shall:
- RADIO BEARER RELEASE; or

the UE shall:
3>else:

Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a new RADIO BEARER RELEASE message before the UE releases the radio bearer
according to a previous RADIO BEARER RELEASE message it ignore the new RADIO BEARER RELEASE message
and configures according to the previous RADIO BEARER RELEASE message received.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
800
Test Procedure
The UE is in CELL_DCH state. When the SS transmits a RADIO BEARER RELEASE message to the UE before the
UE releases the radio access bearer, the UE ignores the second RADIO BEARER RELEASE message and releases the
radio bearer according to the previous RADIO BEARER RELEASE message received. Finally, the UE shall transmit
RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3
to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RELEASE For FDD, the SS sets its UL
scrambling code number to "1".
2 RADIO BEARER RELEASE Message sent before the expiry of
"activation time" specified in
message in step 1. For FDD, the
set to "2". For TDD the code
combination assigned is different
from that assigned in stage 1.
3 RADIO BEARER RELEASE COMPLETE The UE ignores the RADIO
BEARER RELEASE message in
step 2 and release radio bearer
RELEASE message in step 1.

The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title
"Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108
- Uplink DPCH Info


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
801
- Uplink DPCH Info


After step 2 the UE shall transmit an RADIO BEARER RELEASE COMPLETE message on the DCCH using AM
RLC.
8.2.3.17 Radio Bearer Release for transition from CELL_FACH to CELL_DCH:

UE shall:
- RADIO BEARER RELEASE; or

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
802
3>else:
Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a new RADIO BEARER RELEASE message before the UE releases the radio bearer
according to a previous RADIO BEARER RELEASE message, it ignores the new RADIO BEARER RELEASE
message and configures according to the previous RADIO BEARER RELEASE message received.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. When the SS transmits a RADIO BEARER RELEASE message to the UE before the
UE releases the radio access bearer, the UE ignores the second RADIO BEARER RELEASE message and releases the
radio bearers according to the previous RADIO BEARER RELEASE message received. Finally, the UE shall transmit a
RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3
2 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 RADIO BEARER RELEASE For FDD, the SS sets its UL
scrambling code to "1".
2 RADIO BEARER RELEASE For TDD the IE "Secondary
scrambling code" is set to "2". For
TDD, the code combination
assigned is different from that
assigned in stage 1.
3 RADIO BEARER RELEASE COMPLETE The UE ignores the RADIO
BEARER RELEASE message in
step 2 and release radio bearers
RELEASE message in step 1.

The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Packet
to CELL_DCH from CELL_FACH in PS" found in [9] TS 34.108 clause 9 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
803
Activation Time Info Not present
- Uplink DPCH Info

to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9 with the following exceptions:
Activation Time Info [256+Current CFN-[current CFN mod 8 +8 ]]MOD 256

- Uplink DPCH Info


After step 2 the UE shall transmit an RADIO BEARER RELEASE COMPLETE message on the DCCH using AM
RLC.
8.2.3.18 Radio Bearer Release from CELL_DCH to CELL_PCH: Success

If the UE receives:
it shall:
procedure:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
804
The UE shall then:
If after state transition the UE enters CELL_PCH or URA_PCH state, the UE shall, after the state transition and
transmission of the response message:

1>clear that entry;

RLC.
If the new state is CELL_PCH, the response message shall be transmitted using the old configuration before the state
transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration
message, and the UE shall:

2>enter the new state (CELL_PCH);

Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE before entering CELL_PCH state after
it received a RADIO BEARER RELEASE message and released its radio access bearers.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
805
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message. The UE transmits a RADIO
BEARER RELEASE COMPLETE message using AM RLC and enters into CELL_PCH state. SS calls for generic
procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
UE SS
1 RADIO BEARER
RELEASE

2 RADIO BEARER
RELEASE COMPLETE
The UE sends this message
before it completes state
transition.
2a Void SS waits 5 seconds to allow the
UE to read system information
before the next step.

RRC State Indicator
UTRAN DRX cycle length coefficient
CELL_PCH
3

RRC State Indicator
CELL_PCH
3
-Cell parameters ID 4

After step 1 the UE transmits a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
806
8.2.3.19 Radio Bearer Release from CELL_DCH to URA_PCH: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
If after state transition the UE enters CELL_PCH or URA_PCH state, the UE shall, after the state transition and
transmission of the response message:

reselection" according to TS 25.331 subclause 8.3.1 is fulfilled:
2>initiate a URA update procedure according to TS 25.331 subclause 8.3.1 using the cause "URA reselection";
1>clear that entry;

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
807
RLC.
If the new state is URA_PCH, the response message shall be transmitted using the old configuration before the state
transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration
message, and the UE shall:

2>enter the new state (URA_PCH);

Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE before entering URA_PCH state after it
received a RADIO BEARER RELEASE message and released its radio bearers.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message. The UE transmits a RADIO
BEARER RELEASE COMPLETE message using AM RLC and enters into URA_PCH state. SS calls for generic
procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
UE SS
1 RADIO BEARER
RELEASE

2 RADIO BEARER
RELEASE COMPLETE
transition.
2a Void SS waits 5 seconds to allow the
UE to read system information
before the next step.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
808
RRC State Indicator
URA_PCH
3

RRC State Indicator
CELL_PCH
3

After step 1 the UE transmits a RADIO BEARER RELEASE COMPLETE message to the UE on uplink DCCH using
AM RLC.
8.2.3.20 Radio Bearer Release for transition from CELL_DCH to CELL_FACH

If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1>if the received reconfiguration message included the IE "Primary CPICH info"), and the UE selects another cell
than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" :
transmission";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
809
4>proceed as below.
transmission";
4>proceed as below.
1>transmit a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC, using the
new configuration after the state transition.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_FACH according to the RADIO BEARER
RELEASE message.
2. To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH
using AM RLC on a common physical channel in a different frequency.
Initial Condition
UE: Registered idle mode on CS" (state 2) or "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
810
Test Procedure
Table 8.2.3.20
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

columns "T0" in table 8.2.3.20. The SS and UE execute procedure P3 or P5. Next The SS and the UE execute procedure
P7 or P9 and then execute procedure P11 or P13. The SS switches its downlink transmission power settings to columns
"T1" transmits a RADIO BEARER RELEASE message with no IE "Frequency info" to the UE. The UE releases the
radio access bearer and moves into cell 6. The UE transmits CELL UPDATE message with IE "Cell update cause" set
to "cell reselection". SS then transmit CELL UDPATE CONFIRM with IE "New C_RNTI". The UE shall respond with
an UTRAN MOBILITY INFORMATION CONFIRM message, and then transmits a RADIO BEARER RELEASE
COMPLETE message on the uplink DCCH using AM RLC. The SS calls for generic procedure C.2 to check that UE is
in CELL_FACH state.
Expected sequence
UE SS
7.4.2.1.2) or P5 (clause 7.4.2.2.2)

1b SS executes procedure P7 (clause
7.4.2.3.2) or P9 (clause 7.4.2.4.2)

1c SS executes procedure P11 (clause
7.4.2.5.2) or P13 (clause 7.4.2.6.2)

3 Void
4 RADIO BEARER RELEASE Not including frequency
information.
CONFIRM


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
811
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" or "Non speech to
CELL_FACH from CELL_DCH in CS" or "Speech to CELL_FACH from CELL_DCH in CS" in [9] TS 34.108 clause
9 with the following exception:
Frequency info
Downlink information for each radio link Not present


New C-RNTI 0000 0000 0000 0001B

AM RLC in cell 6.
After step 7 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC
in cell 6.
8.2.3.21 Radio Bearer Release from CELL_DCH to CELL_PCH (Frequency band

If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
812
1>transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old
configuration before the state transition.
response message:
1>if the UE enters CELL_PCH state from CELL_DCH state, and the received reconfiguration message included
the IE "Primary CPICH info, and the UE selected another cell than indicated by this IE or the received
reconfiguration message did not include the IE "Primary CPICH info:
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
using AM RLC.
2. To confirm that the UE transits from CELL_DCH to CELL_PCH according to the RADIO BEARER
RELEASE message.
3. To confirm that the UE releases the radio access bearer and selects a common physical channel in a different
frequency indicated by SS.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
813
Test Procedure
Table 8.2.3.21
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

The UE is in idle mode in cell 1 and the SS has configured its downlink transmission power setting according to
columns "T0" in table 8.2.3.21. The SS and UE execute procedure P3 or P5. Next The SS and the UE execute procedure
P7 or P9 and then execute procedure P11 or P13. The SS switches its downlink transmission power settings to columns
"T1" and then transmits a RADIO BEARER RELEASE message with no IE "Frequency info". The UE transmits a
RADIO BEARER RELEASE COMPLETE message using AM RLC and enters CELL_PCH state of cell 6, then the UE
shall transmit CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection", to complete the
procedure. The SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
UE SS
7.4.2.1.2) or P5 (clause 7.4.2.2.2)

1b SS executes procedure P7 (clause
7.4.2.3.2) or P9 (clause 7.4.2.4.2)

7.4.2.5.2) or P13 (clause 7.4.2.6.2)

3 Void
4 RADIO BEARER RELEASE Not including new frequency
information.
5 RADIO BEARER
RELEASE COMPLETE
transition. UE sends this
message in cell 1.
"CELL_PCH".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
814
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" or "Non speech to
CELL_FACH from CELL_DCH in CS" or "Speech to CELL_FACH from CELL_DCH in CS" in [9] TS 34.108 clause
9, with following exceptions:

34.108 clause 9, with the following exceptions:

in [9] TS 34.108 clause 9, with the following exceptions:
RRC State indicator CELL_PCH

After step 4 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM
RLC in cell 1.
reselection" in cell 6.
After step 8 the UE shall be in CELL_PCH state in cell 6.
8.2.3.22 Radio Bearer Release for transition from CELL_FACH to CELL_PCH:
Success

If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
815
response message:
1>if the UE enters CELL_PCH state from CELL_FACH state, and the received reconfiguration message included
the IE "Primary CPICH info", and the UE selected another cell than indicated by this IE:
2>when the cell update procedure is successfully completed:
Reference
3GPP TS 25.331 clause 8.2.2, 8.3, 8.5 and 8.6.
using AM RLC.
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the RADIO BEARER
RELEASE message.
3. To confirm that the UE releases the radio access bearer and selects a common physical channel.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
816
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a RADIO BEARER RELEASE message. The UE shall
release all radio access bearer and enter CELL_PCH state after it transmits a RADIO BEARER RELEASE
COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for generic procedure C.4 to
check that UE is in CELL_PCH state.
Expected sequence
UE SS
1 The UE is in CELL_FACH state
of cell 1.
3 RADIO BEARER RELEASE COMPLETE The UE transmits this message
on uplink DCCH using AM RLC.


RLC.
8.2.3.23 Radio Bearer Release for transition from CELL_FACH to URA_PCH:
Success

If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
817
response message:
reselection" according to TS5.331 subclause 8.3.1 is fulfilled:
Reference
3GPP TS 25.331 clause 8.2.2, 8.3, 8.5 and 8.6.
using AM RLC.
RELEASE message.
3. To confirm that the UE releases the radio access bearer and selects a common physical channel.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
818
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a RADIO BEARER RELEASE message. The UE shall
release all radio access bearers and enter URA_PCH state after it transmits a RADIO BEARER RELEASE
COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for generic procedure C.5 to
check that UE is in URA_PCH state.
Expected sequence
UE SS
of cell 1.
3 RADIO BEARER RELEASE COMPLETE The UE transmits this message


NOTE: It is to be noted that IE URA identity is not included in this message, for the purpose of wider test
coverage. The scenario in which IE URA identity is included, is tested in other test cases.
RLC.
After step 4 the UE shall be in URA_PCH state.
8.2.3.24 Radio Bearer Release for transition from CELL_DCH to CELL_DCH

If the UE receives:
procedure:
2>perform the physical layer synchronisation procedure A as specified in TS25.214;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
819
The UE shall then:
UE shall:
configuration.
RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_DCH according to the RADIO BEARER
RELEASE message.
Initial Condition
CS-DCCH_DTCH_DCH (state 6-9) or PS_DCCH_DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108,
depending on the CN domain(s) supported by the UE.
Test Procedure
Table 8.2.4.24
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -72

columns "T0" in table 8.2.3.24. The SS switches its downlink transmission power settings to columns "T1" and
transmits a RADIO BEARER RELEASE message including IE "Frequency info" set to frequency information of cell 6
and IE "Primary CPICH info" set to Primary Scrambling Code which is assigned to P-CPICH of cell 6. The UE shall
select cell 6 and release the radio access bearer after receiving this message, and then remain in CELL_DCH state. The
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
820
UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC after it completes reconfiguration
according to received RADIO BEARER RELEASE message. Upon completion of the procedure, the SS calls for
Expected sequence
UE SS
8.2.3.24.
3 RADIO BEARER RELEASE Including IE "Frequency info" set
assigned to P-CPICH of cell 6.
4 The UE select cell 6.
5 RADIO BEARER RELEASE COMPLETE The UE sends this message on a
6.

The contents RADIO BEARER RELEASE message in this test case is identical the message sub-type indicated by
"Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" or "Non speech in CS" in [9] TS 34.108 clause 9,
with the following exception:
Frequency info

in cell 6.
8.2.3.25 Radio Bearer Release for transition from CELL_DCH to URA_PCH

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
821
If the UE receives:
it shall:
response message:
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH
using AM RLC.
2. To confirm that the UE transits from CELL_DCH to URA_PCH according to the RADIO BEARER RELEASE
message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
822
3. To confirm that the UE releases radio access bearer, dedicated physical channel and selects a common physical
channel in a different frequency.
Initial Condition
Test Procedure
Table 8.2.3.25
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

columns "T0" in table 8.2.3.25. SS requests operator to make an outgoing call. The SS and UE execute procedure P3 or
P5. Next The SS and the UE execute procedure P7 or P9 and then execute procedure P11 or P13. The SS switches its
downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message
including no IE "Frequency info".The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using
AM RLC and enter URA_PCH state of cell 6. Upon completion of the procedure, the SS calls for generic procedure C.5
to check that UE is in URA_PCH state.
NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
823
Expected sequence
UE SS
"T0" in table 8.2.3.25. SS
outgoing call.
7.4.2.1.2) or P5 (clause 7.4.2.2.2)

7.4.2.3.2) or P9 (clause 7.4.2.4.2)

7.4.2.5.2) or P13 (clause 7.4.2.6.2)

6 RADIO BEARER RELEASE Not including IE "Frequency info"
and IE "Primary CPICH info"
7 RADIO BEARER RELEASE COMPLETE UE transmit this message on the
cell 1

Use the same message sub-type titled "Speech to CELL_FACH from CELL_DCH in CS" or "Non speech to
CELL_FACH from CELL_DCH in CS" or "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9
Frequency info Not present
Downlink information for each radio link Not present

After step 6 the UE shall transmits a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC
in cell 1.
8.2.3.26 Radio Bearer Release for transition from CELL_FACH to CELL_PCH

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
824
If the UE receives:
it shall:
response message:
the IE "Primary CPICH info" , and the UE selected another cell than indicated by this IE:
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
using AM RLC.
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the RADIO BEARER
RELEASE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
825
3. To confirm that the UE releases radio access bearer and selects a common physical channel in a different
frequency.
Initial Condition
Test Procedure
Table 8.2.3.26
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

The UE is in cell 1. The SS shall transmit a RADIO BEARER RELEASE message on downlink DCCH using UM
RLC, . The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC. The SS shall
acknowledge the RADIO BEARER RELEASE COMPLETE message and then switches its downlink transmission
power settings to columns T1. . Upon completion of the procedure, the SS waits for 5 seconds and calls for generic
procedure C.4 in cell 6 to check that UE is in CELL_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
826
Expected sequence
UE SS
1 Void
2 Void
3 Void
4 Void
5 Void
6 RADIO BEARER RELEASE This message is sent on RB 1.
IE "Frequency info" and IE
"Primary CPICH info" set to that
of cell 6.
7 RADIO BEARER RELEASE COMPLETE After SS acknowledges this
message, SS switches its
settings to columns "T1" in table
8.2.3.26.
9 CALL C.4 (In cell 6) If the test result of C.4
indicates that UE is in
CELL_PCH state, the test

Frequency info
- CHOICE mode FDD
- UARFCN downlink (Nd) Set to the frequency of cell 6

in cell 1.
8.2.3.27 Radio Bearer Release for transition from CELL_FACH to URA_PCH

If the UE receives:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
827
it shall:
response message:
as specified in TS25.331subclause 8.2.2.9.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
using AM RLC.
RELEASE message.
3. To confirm that the UE releases radio access bearer and selects a common physical channel in a different
frequency.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
828
Initial Condition
Test Procedure
Table 8.2.3.27
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

Next The SS and the UE execute procedure P10 and then execute procedure P14. The SS switches its downlink
transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE not including IE "Frequency
info" and IE "Primary CPICH info". The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using
AM RLC and enter URA_PCH state of cell 6. Upon completion of the procedure, the SS calls for generic procedure C.5
to check that UE is in URA_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
829
Expected sequence
UE SS
"T0" in table 8.2.3.27. SS
outgoing call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

5 Void
6 RADIO BEARER RELEASE Not including IE "Frequency info"
7 RADIO BEARER RELEASE COMPLETE UE transmit this message on the
1. The SS switches its downlink

URA identity URA-ID 1

in cell 1.
8.2.3.28 Radio Bearer Release for transition from CELL_FACH to CELL_FACH

If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
830
the UE shall:
2>if the received reconfiguration message included the IE "Primary CPICH info", and the UE selected another
cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH
info":
4>proceed as below.
RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_FACH according to the RADIO BEARER
RELEASE message.
using AM RLC on a common physical channel in a different frequency.
Initial Condition
mode on CS/PS".
Test Procedure
Table 8.2.3.28
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
831
transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message including IE
"Frequency info" set to frequency information of cell 6 and no IE "Primary CPICH info". The UE shall select cell 6 and
initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection" . The UE shall transmit a
RADIO BEARER RELEASE COMPLETE message using AM RLC after it completes reconfiguration according to the
received RADIO BEARER RELEASE message. Upon completion of the procedure, the SS calls for generic procedure
C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 RADIO BEARER RELEASE Including IE "Frequency info" set
set to Primary Scrambling Code
CONFIRM

10 RADIO BEARER RELEASE COMPLETE The UE sends this message on a
6.

The contents of RADIO BEARER RELEASE message in this test case are identical the message sub-type indicated by
"Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following exception:
Frequency info

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
832

New C-RNTI 0000 0000 0000 0001B

The contents of UTRAN MOBILITY UPDATE CONFIRM message is identical as "UTRAN MOBILITY UPDATE
AM RLC in cell 6.
in cell 6.
Associated with signalling connection release during multi call for PS and CS
services

If the UE receives:
- a RADIO BEARER RELEASE message:
it shall:
1>set the variable ORDERED_RECONFIGURATION to TRUE;
procedure:
The UE may first release the physical channel configuration used at reception of the reconfiguration message. The UE
shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
833


UE shall:
1>if the IE "Uplink DPCH Info" is absent:
2>not change its current UL Physical channel configuration.1> in TDD:
2>if "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified:

In case the procedure was triggered by reception of a PHYSICAL CHANNEL RECONFIGURATION message, the UE
shall:
1>transmit a RADIO BEARER RELEASE COMPLETE message as response message on the uplink DCCH using
AM RLC.
.
If the IE "Signalling Connection release indication" is present in a message, the UE shall:
1>if all radio access bearers for the CN domain identified with the value of the IE "Signalling Connection release
indication" would have been released in the variable ESTABLISHED_RABS after processing of the received
message:
2>indicate release of the signalling connection identified with the value of the IE "Signalling Connection
release indication" to the upper layers;
2>remove the signalling connection identified with the value of the IE "Signalling Connection release
indication" from the variable ESTABLISHED_SIGNALLING_CONNECTIONS.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.1.3.
To confirm that the UE releases the existing radio access bearer and signalling connection according to a RADIO
BEARER RELEASE message.
Initial Condition
UE: CS-DCCH+DTCH_DCH (state 6-9) as specified in clause 7.4 of TS 34.108
Test Procedure
The UE is in CELL_DCH state of cell 1. The UE initiates a session setup to establish a PS signalling connection for
multi call. Then UE and SS enter to multi call state. The SS transmits a DISCONNECT message to release a CS domain
signalling connection. After the CC procedure, SS transmit a RADIO BEARER RELEASE message which includes IE
"Signalling Connection release indication" set to "CS domain" and new configuration for remained service to the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
834
The UE shall configure the specified channel and transmit a RADIO BEARER RELEASE COMPLETE message on the
uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
CELL_DCH state of cell 1.
(SERVICE REQUEST)
GMM ( Session setup is initiated
for multi call from UE side.)
(AUTHENTICATION AND CIPHERING
REQUEST)
GMM
(AUTHENTICATION AND CIPHERING
RESPONSE)
GMM
5 SECURITY MODE COMMAND
(ACTIVATE PDP CONTEXT REQUEST)
SM
(ACTIVATE PDP CONTEXT ACCEPT)
SM
(DISCONNECT)
CC
(RELEASE)
CC
(RELEASE COMPLETE)
CC
14 RADIO BEARER RELEASE Including IE "signalling
connection release indication"
set to "CS domain"

RADIO BEARER RELEASE (STEP 14)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type titled as
"Non speech in CS" or "Speech in CS" as found in Clause 9 of TS 34.108, with the following exceptions
Signalling Connection release indication

Success (stop of HS-DSCH reception)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
835

Reference
3GPP TS 25.331 clause 8.6.3.1, 8.6.6.32
To confirm that the UE releases a radio bearer mapped to HS-DSCH according to the received RADIO BEARER
RELEASE message.
Initial Condition
- UE supports FDD
Test Procedure
The UE is in CELL_DCH state with a radio bearer mapped on HS-DSCH established. The SS transmits a RADIO
BEARER RELEASE message to the UE . This message requests the release of the radio access bearer mapped to HS-
DSCH. After the UE receives this message, it releases the radio access bearer. Finally the UE transmits a RADIO
BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
836
Expected sequence
UE SS
COMPLETE


Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108.
After step 1, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.4 Transport channel reconfiguration
8.2.4.1 Transport channel reconfiguration (Timing re-initialised hard handover with
transmission rate modification) from CELL_DCH to CELL_DCH: Success

If the UE receives:
- a TRANSPORT CHANNEL RECONFIGURATIONmessage; or
it shall:
procedure:
The UE shall then:
UE shall:
configuration.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
837
1>clear that entry;
In case the procedure was triggered by reception of a TRANSPORT CHANNEL RECONFIGURATION message, the
UE shall:
1>transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message on the uplink
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures the channel configuration according to a TRANSPORT CHANNEL
RECONFIGURATION message, which is used to change the TFCS and the TFS while replacing the RL(s) in the active
set with a set of RL(s) disjunct with the previous active set.
Initial Condition
System Simulator: 2 cells - Cell 1 and cell 2 are active
34.108, depending on the CN domain(s) supported by the UE. Either a streaming CS domain RAB (state 6-9) or an
interactive/ background PS domain RAB (state 6-10) has been established. UE connected to cell 1.
Test Procedure
The UE is in CELL_DCH state, connected to cell 1. The SS transmits a TRANSPORT CHANNEL
RECONFIGURATION message to the UE, which includes new configuration parameters. The message is used to
replace the RL(s) in the active set with a set of RL(s) disjunct with the previous active set In this case, the connection to
cell 1 is discontinued while a new connection to cell 2 is established at the same time. The TRANSPORT CHANNEL
RECONFIGURATION message is used to also change the TFCS and TFS e.g. because the currently used rate is not
available on cell 2. The TFCS and TFS change from a value corresponding with one reference configuration in 34.108
to another such reference configuration, e.g. to change an interactive PS domain RAB from UL:64 DL:384 to UL:32
DL:64 or to change a streaming CS RAB from UL:14.4 DL:14.4 to UL:57.6 DL:57.6. The UE shall apply the new
configuration and then transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 Void
2 Void
3 TRANSPORT CHANNEL
RECONFIGURATION
The TFCS and the TFS are
changed while replacing the
RL(s) in the active set with a set
of RL(s) disjunct with the
previous active set
4 Void
5 TRANSPORT CHANNEL


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
838
TRANSPORT CHANNEL RECONFIGURATION (FDD)
The contents of TRANSPORT CHANNEL RECONFIGURATION message in this test case is identical to the message
sub-type titled as "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in Annex A, with
For condition A1 (for CS non- speech the following IEs are not present in the default message, while included below:
UL Transport channel information for all transport channels, Added or Reconfigured UL TrCH information, DL
Transport channel information common for all transport channel, Added or Reconfigured DL TrCH information).
channels
Set to the same values as for "Packet to CELL_DCH
from CELL_FACH in PS"
Added or Reconfigured UL TrCH information Set to the same values as for "Packet to CELL_DCH
transport channel
Set to the same values as for "Packet to CELL_DCH
Added or Reconfigured DL TrCH information Set to the same values as for "Packet to CELL_DCH
CHOICE channel requirement Set to the same values as for "Packet to CELL_DCH
from CELL_FACH in PS" unless explicitly indicated
otherwise in the following
-Uplink DPCH power control info Not present
Downlink information common for all radio links Set to the same values as for "Packet to CELL_DCH
- Timing indicator Initialise
- Downlink DPCH power control information Not present
- Default DPCH Offset Value Arbitrary set to value 0..306688 by step of 512
Downlink information for each radio link list Set to the same values as for "Packet to CELL_DCH
- CHOICE mode FDD
for cell 2: 150
- DPCH frame offset Set to value : Default DPCH Offset Value mod 38400

TRANSPORT CHANNEL RECONFIGURATION (TDD)
in Annex A, with the following exceptions:
- First timeslot code list A different code combination to that used previously.

After step 3 the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the
DCCH using AM RLC on a dedicated physical channel using another radio link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
839
8.2.4.1a Transport channel reconfiguration (Transmission Rate Modification) from
CELL_DCH to CELL_DCH of the same cell: Success

1. If the UE receives:
- a TRANSPORT CHANNEL RECONFIGURATIONmessage; or
it shall:
procedure:
The UE shall then:

2. If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state,
the UE shall:
1>if the IE "Uplink DPCH Info" is absent:
2>not change its current UL Physical channel configuration.

3. The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information
elements as specified below. The UE shall:
1>clear that entry;

4. In case the procedure was triggered by reception of a TRANSPORT CHANNEL RECONFIGURATION message,
the UE shall:
1> transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message on the uplink
DCCH using AM RLC.

5. If the IE "Downlink information for each radio link" is included in a received message, the UE shall:
1>in addition, if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according
to subclause 8.6.3.3 applied on the received message:
2>for each optional IE part of the IE "Downlink information for each radio link" that is not present:
3>do not change its current downlink physical channel configuration corresponding to the IE, which is
absent, if not stated otherwise elsewhere.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
840
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.6.4.
To confirm that the UE reconfigures the physical channel and transport channel configuration according to a
TRANSPORT CHANNEL RECONFIGURATION message, which specifies a reconfiguration by changing physical
channel information and TFCS.
Initial Condition
Note : Transmission rate shall be set to the maximum rate for the UE during the radio bearer establishment procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
841
Test Procedure
The radio bearer is placed into UE test loop mode 1 described in TS 34.109 clause 5.3 and the UL RLC_SDU size for
the loopback scheme is set to the maximum size possible when the maximum uplink TFS, as indicated in RADIO
BEARER SETUP message during radio bearer establishment procedure, is used.
The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to the UE to modify the transmission
rate which includes a new physical channel information and downlink TFCS to restrict the use of the highest rate
TFCIs.
The UE shall reconfigure the new configuration and then transmit a TRANSPORT CHANNEL RECONFIGURATION
COMPLETE message on the uplink DCCH using AM RLC.
UL MAC restriction is imposed on the SS so that SS can only receive using the maximum TFS and minimum TFS.
Both TFSs belong to the currently limited downlink TFCS of the UE (i.e. the TFCS after reconfiguration).
Then the SS transmits a RLC_SDU whose size is the same as the UL RLC_SDU size for the loopback scheme. The UE
receives this RLC_SDU and decode it according to the new TFCS.
The RLC_SDU is then looped backed to the SS. The SS should receive the expected data as a RLC_SDU exactly as the
one transmitted to the UE.
Expected sequence
UE SS
1 TRANSPORT CHANNEL
RECONFIGURATION

2 TRANSPORT CHANNEL

2a DOWNLINK RLC SDU
2b UPLINK RLC SDU RLC SDU sent back shall be the
same as the one sent from the
SS.
3 Void
4 Void
fails.

TRANSPORT CHANNEL RECONFIGURATION (Step 1)
sub-type titled as "Packet to CELL_DCH from CELL_DCH in PS" as found in TS 34.108 clause 9, with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
842
channels
Not Present
transport channel

- SCCPCH TFCS Not Present
- CHOICE mode FDD
- CHOICE DL parameters Explicit
- DL DCH TFCS
- CHOICE TFCI Signalling Normal
- TFCI Field 1 Information
- TFCS complete reconfigure
- CHOICE CTFC Size Number of bits used must be enough to cover all
combinations of CTFC from TS34.108 clause 6.10.2.4
Parameter Set which is used in RADIO BEARER
SETUP message in initial procedure.
- CTFC information
- CTFC Reference to TS 34.108 clause 6.10.2.4 Parameter Set
as defined in RADIO BEARER SETUP message with
highest rate CTFC removed.
- Power offset information Not Present
- CHOICE mode FDD
- Spreading factor Reference to TS34.108 clause 6.10 Parameter Set.
Set to a value that matches the new CTFC.
- CHOICE mode FDD
- Spreading factor Reference to TS34.108 clause 6.10 Parameter Set.
Set to a value that matches the new CTFC.

8.2.4.1a.5 Test requirement
DCCH using AM RLC.
After step 2a the UE shall transmit a RLC_SDU that is same as the transmitted data from SS in step 2a on the radio
access bearer.
8.2.4.2 Void
8.2.4.3 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Failure
(Physical channel failure and reversion to old configuration)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
843

as specified below:
2>clear that entry;

The UE shall:
1>in case of reception of a TRANSPORT CHANNEL RECONFIGURATION message:

2>transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE as response message on the DCCH
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration and transmits a TRANSPORT CHANNEL
RECONFIGURATION FAILURE message on the DCCH using AM RLC, if the UE fails to reconfigure the new
configuration according to a TRANSPORT CHANNEL RECONFIGURATION message.
Initial Condition
34.108, depending on the CN domain(s) supported by the UE. Either a streaming CS domain RAB (state 6-9) or an
interactive/ background PS domain RAB (state 6-10) has been established.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
844
Test Procedure
Table 8.2.4.3
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60

OFF -75
P-CCPCH
RSCP
(TDD)
dBm
-60 -60 OFF -75

The UE is in CELL_DCH state in cell 1. SS then send a MEASUREMENT CONTROL message to UE. The UE shall
REPORT message back to SS. Then the SS configures its downlink transmission power settings according to column
"T1" in table 8.2.4.3. The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to the UE to
restrict transmission on the uplink DCH used by the signalling radio bearer RB2. The message specifies a new
configuration in cell 2 but the SS does not configure the new physical channel in cell 2 specified in this message and
keep its old configuration in cell 1. Therefore, the UE cannot synchronise with the SS on the new physical channel in
cell 2 and shall revert to the old configuration in cell 1 after T312 expires. Then the UE shall transmit a TRANSPORT
CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting "physical channel
failure" in IE "failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT
messages back to SS periodically.
Expected sequence
UE SS
measurement.
1 TRANSPORT CHANNEL
RECONFIGURATION

new configuration in cell 2.
3 TRANSPORT CHANNEL
The UE reverts to the old
configuration and transmits this
message.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
845
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

sub-type titled as "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
846
channels

- TFC subset
- Restricted TrCH information
- Restricted UL TrCh identity 5 <UL DCH for SRB 2>
- Allowed TFIs
- Allowed TFI 0
- CHOICE mode FDD
6.1 (FDD)

TRANSPORT CHANNEL RECONFIGURATION FAILURE (Step 2)
The contents of TRANSPORT CHANNEL RECONFIGURATION FAILURE message in this test case is the same as
the TRANSPORT CHANNEL RECONFIGURATION FAILURE message as found in [9] TS 34.108 clause 9, with the

After step 2 the UE shall revert to the old configuration in cell 1 and transmit a TRANPORT CHANNEL
RECONFIGURATION FAILURE message on the DCCH using AM RLC, and it shall set the value "physical channel
failure" in IE "failure cause".
8.2.4.4 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Failure
(Physical channel failure and cell reselection)

1>if the old configuration includes dedicated physical channels (CELL_DCH state) and the UE is unable to revert
to the old configuration:
2>initiate a cell update procedure according to TS 25.331 subclause 8.3.1, using the cause "radio link failure";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
847
3>proceed as below.

as specified below:
2>clear that entry;
the UE shall:

The UE shall:
1>in case of reception of a TRANSPORT CHANNEL RECONFIGURATION message:

2>transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE as response message on the DCCH
using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.3.1.7.
To confirm that the UE transmits a TRANSPORT CHANNEL RECONFIGURATION FAILURE message after it
completes a cell update procedure when the UE cannot synchronise with the SS on the new channel before T312 expires
and fails to revert to the old configuration.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
848
Test Procedure
Table 8.2.4.4
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60

OFF -75
P-CCPCH
RSCP
(TDD)
dBm
-60 -60 OFF -75

The UE is in CELL_DCH state in cell 1. Then the SS configures its downlink transmission power settings according to
columns "T1" in table 8.2.4.4. The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to the
UE. The message specifies a new configuration in cell 2 but the SS does not reconfigure the new channel in cell 2
specified in this message and release the old configuration in cell 1. The UE cannot synchronise with SS before T312
expires and shall attempt to revert to the old configuration in cell 1. The UE cannot revert to the old configuration and
then transmit a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "radio link failure" in cell
1. The SS shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after receiving CELL UPDATE
message. The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC and subsequently transmits a TRANSPORT CHANNEL RECONFIGURATION FAILURE
message on the DCCH using AM RLC, setting IE "failure cause" to "physical channel failure".
Expected sequence
UE SS
1 TRANSPORT CHANNEL
RECONFIGURATION

2 The SS does not reconfigure L1
in accordance with
TRANSPORT CHANNEL
RECONFIGURTION message
and release the old
configuration.
value "radio link failure" set in IE
"Cell update cause".
4 CELL UPDATE CONFIRM This message includes IE
elements".
5 The SS changes physical
channel configuration according
to the IE "Physical channel
information elements" included
in the CELL UPDATE
CONFIRM message.
6 PHYSICAL CHANNEL

7 TRANSPORT CHANNEL
The IE "failure cause" shall be
set to "physical channel failure"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
849
Use the message sub-type titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH
in PS" as found in [9] TS 34.108 clause 9, with the following exception.
- CHOICE mode FDD
6.1 (FDD)

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in [9] TS
U-RNTI
- S-RNTI Check to see if set to '0000 0000 0000 0000 0000 0001'

UplinkDPCH Info Same as RADIO BEARER SETUP message used to
Downlink information for each radio link list Same as RADIO BEARER SETUP message used to

Same as RADIO BEARER SETUP message used to
Downlink information for each radio link list Same as RADIO BEARER SETUP message used to

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
850
TRANSPORT CHANNEL RECONGURATION FAILURE (Step 7)
The contents of TRANSPORT CHANNEL RECONFIGURATION FAILURE message in this test case is the same as
the TRANSPORT CHANNEL RECONFIGURATION FAILURE message as found in [9] TS 34.108 clause 9, with the

After step 2 the UE shall transmit a CELL UPDATE message on the uplink CCCH with IE "Cell update cause" set to
"radio link failure" in cell 1.
After step 5 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC.
After step 6 the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION FAILURE message on the
DCCH using AM RLC, setting the IE "failure cause" to "physical channel failure".
8.2.4.5 Void
8.2.4.6 Void
8.2.4.7 Void
8.2.4.8 Void
8.2.4.9 Void
8.2.4.10 Transport channel reconfiguration from CELL_FACH to CELL_DCH: Success

If the UE receives:
- a TRANSPORT CHANNEL RECONFIGURATION message; or
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
851
1>clear that entry;

UE shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures a new channel using dedicated physical channel according to a TRANSPORT
CHANNEL RECONFIGURATION message.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. The UE has previously stored radio bearer and transport channel parameters for use in
CELL_DCH. The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message, which modifies the rate
as compared to the stored configuration to the UE. The message also includes the physical layer parameters e.g. IE
"Uplink DPCH info" and IE "Downlink DPCH info" leading to a state transition from CELL_FACH to CELL_DCH in
the same cell, to the UE. The UE shall reconfigure the new channel according to this message. Finally, the UE transmits
a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message using AM RLC. SS calls for generic
Expected sequence
UE SS
1 TRANSPORT CHANNEL
RECONFIGURATION
Includes both IE "Uplink DPCH
Info" and IE "Downlink DPCH
Info" in the message.
2 Reconfiguration of transport
channel
3 TRANSPORT CHANNEL


TRANSPORT CHANNEL RECONFIGURATION
Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in Annex A with the following
exceptions:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
852
Added or Reconfigured UL TrCH information Set to the same values as for "Packet to CELL_DCH
from CELL_DCH in PS". Only the DCH for DTCH is
included, since only for that TrCH the rate is changed as
compared to the stored CELL_DCH configuration
Added or Reconfigured DL TrCH information Set to the same values as for "Packet to CELL_DCH
from CELL_DCH in PS". Only the DCH for DTCH is
included, since only for that TrCH the rate is changed as
compared to the stored CELL_DCH configuration
- CHOICE mode FDD

TRANSPORT CHANNEL RECONFIGURATION COMPLETE
Use the message with the same message type specified in Annex A.
After step 2 the UE shall transmit a TRANSPORT RECONFIGURATION COMPLETE message on the newly
configured DPCH.
8.2.4.11 Void
8.2.4.12 Void
8.2.4.13 Void
8.2.4.14 Void
8.2.4.15 Void
8.2.4.16 Void
8.2.4.17 Void
8.2.4.18 Transport Channel Reconfiguration from CELL_DCH to CELL_DCH:

UE shall:
- TRANSPORT CHANNEL RECONFIGURATION; or

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
853
the UE shall:
3>else:

Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a TRANSPORT CHANNEL RECONFIGURATION message before the UE
configures the radio bearer according to the previous TRANSPORT CHANNEL RECONFIGURATION message it
ignores the second TRANSPORT CHANNEL RECONFIGURATION message and configures according to the
previous TRANSPORT CHANNEL RECONFIGURATION message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
854
Test Procedure
The UE is in CELL_DCH state. When the SS transmits a TRANSPORT CHANNEL RECONFIGURATION message
to the UE before the activation time specified in the previous TRANSPORT CHANNEL RECONFIGURATION
message elapses, the UE ignores the new TRANSPORT CHANNEL RECONFIGURATION message and configures
according to the previous TRANSPORT CHANNEL RECONFIGURATION message. Finally, the UE shall transmit a
TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for
Expected sequence
UE SS
1 TRANSPORT CHANNEL
RECONFIGURATION
For FDD, Scrambling code
number is set to "1" and for TDD ,
the code combination is assigned
by SS.
2 TRANSPORT CHANNEL
RECONFIGURATION
SS send this message before the
expiry of "activation time"
specified in TRANSPORT
CHANNEL SETUP message of
step 1. For FDD the IE
"Scrambling code number" is set
to "2". For TDD the code
from that assigned in stage 1.
3 TRANSPORT CHANNEL
The UE ignores the TRANSPORT
CHANNEL RECONFIGURATION
message in step 2 and configures
according to the TRANSPORT
message in step 1.

TRANSPORT CHANNEL RECONFIGURATION (Step 1) (FDD)
The contents of TRANSPORT CHANNEL RECONFIGURATION messages in this test case is identical to the message
sub-type title as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in
[9] TS 34.108 clause 9 with the following exceptions:
- Uplink DPCH Info

TRANSPORT CHANNEL RECONFIGURATION (Step 1) (TDD)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
855
- Uplink DPCH Info


DCCH using AM RLC.
8.2.4.19 Transport Channel Reconfiguration from CELL_FACH to CELL_DCH:

UE shall:
- TRANSPORT CHANNEL RECONFIGURATION; or

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
856
3>else:
Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a TRANSPORT CHANNEL RECONFIGURATION message before the UE
configures the radio bearer according to the previous TRANSPORT CHANNEL RECONFIGURATION message it
ignores the second TRANSPORT CHANNEL RECONFIGURATION message and configures according to the
previous TRANSPORT CHANNEL RECONFIGURATION message.
Initial Condition
Test Procedure
The UE is in CELL_FACH state. When the SS transmits a TRANSPORT CHANNEL RECONFIGURATION message
to the UE before the activation time specified in the previous TRANSPORT CHANNEL RECONFIGURATION
message elapses, the UE ignores the new TRANSPORT CHANNEL RECONFIGURATION message and configures
according to the previous TRANSPORT CHANNEL RECONFIGURATION message. Finally, the UE shall transmit a
TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for
Expected sequence
UE SS
1 TRANSPORT CHANNEL
RECONFIGURATION
For FDD, Scrambling code
number is set to "1" and for TDD,
the code combination is assigned
by SS.
2 TRANSPORT CHANNEL
RECONFIGURATION
For FDD the IE "Scrambling code
number" is set to "2". For TDD the
code combination assigned is
different that assigned in stage 1.
3 TRANSPORT CHANNEL
The UE ignores the TRANSPORT
message in step 2 and configures
according to the TRANSPORT
message in step 1.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
857
sub-type title "Packet to CELL_DCH from CELL_FACH in PS" found in [9] TS 34.108 clause 9 with the following
exceptions:
- Uplink DPCH Info

exceptions:

exceptions:
- Uplink DPCH Info

exceptions:

DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
858
8.2.4.20 Void
8.2.4.21 Void
8.2.4.22 Void

8.2.4.23 Void

8.2.4.24 Transport channel reconfiguration from CELL_DCH to CELL_DCH: Success
with uplink transmission rate modification

If the UE receives:
- a TRANSPORT CHANNEL RECONFIGURATION message:
it shall:
procedure:
The UE shall then:
UE shall:
configuration.
UE shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
To confirm that the UE transmits TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC after reconfigure its available uplink TFC according to a TRANSPORT CHANNEL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
859
Initial Condition
Test Procedure
The UE is in CELL_DCH state of cell 1. The SS transmits a TRANSPORT CHANNEL RECONFIGURATION
message to the UE to modify the transmission rate. This message includes a new uplink transport channel information
in order to restricts available uplink TFC within assigned uplink TFCS. The UE shall transmit a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC after reconfiguring its
transport channel parameters. Next the SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to
the UE which includes a new uplink transport channel information in order to reconfigure uplink TFCS. The UE
transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using AM
RLC after reconfiguring its transport channel parameters according to the TRANSPORT CHANNEL
Expected sequence
UE SS
state of cell 1.
2 TRANSPORT CHANNEL
RECONFIGURATION
This message includes the
IE"TFC subset" and don't include
UL/DL physical channel
information.
3 TRANSPORT CHANNEL

4 TRANSPORT CHANNEL
RECONFIGURATION

5 TRANSPORT CHANNEL

sub-type titled as "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the
channels

- CHOICE mode FDD
- TFC subset
- CHOICE Subset representation Allowed transport format combination list
- Allowed transport format combination Indicate TFCs which are a part of the TFCS defined in
this message to restrict uplink allowed TFC subset.
- UL DCH TFCS Same contents as a RADIO BEARER SETUP message
used in initial procedure.
CHOICE channel requirement Not present
Downlink information per radio link list Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
860
sub-type titled as "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the
channels

- CHOICE mode FDD
- TFC subset
- UL DCH TFCS Reference to TS34.108 clause 6.10 Parameter Set
Set different parameter which is included in a RADIO
BEARER SETUP message used in initial procedure.
- Uplink DPCH power control info Same contents as a RADIO BEARER SETUP message
used in initial procedure
- CHOICE mode FDD
- Scrambling code type Long
- Scrambling code number 0 (0 to 16777215)
- Number of DPDCH Not Present
- TFCI existence Reference to TS34.108 clause 6.10 Parameter Set
- Number of FBI bit Not Present
- Puncturing Limit Reference to TS34.108 clause 6.10 Parameter Set
Downlink information per radio link list Not present

DCCH using AM RLC.
DCCH using AM RLC.
8.2.4.25 Transport channel reconfiguration from CELL_FACH to CELL_DCH

If the UE receives:
-a TRANSPORT CHANNEL RECONFIGURATION message;
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
861
1>clear the C_RNTI.
UE shall:
1>transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using
AM RLC, using the new configuration after the state transition.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_DCH according to TRANSPORT CHANNEL
2. To confirm that the UE transmits TRANSPORT CHANNEL RECONFIGURATION message on the uplink
DCCH using AM RLC on dedicated physical channel in a different frequency.
Initial Condition
Test Procedure
Table 8.2.4.25
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -55

Off -55

The UE is in CELL_FACH state of ce11 1 and the SS has configured its downlink transmission power setting according
transmits a TRANSPORT CHANNEL RECONFIGURATION message, which includes new frequency information
leading to a state transition from CELL_FACH to CELL_DCH in cell 6. The UE shall reconfigure transport channel
parameter and frequency band according to this message. Finally, the UE transmits a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE message using AM RLC in cell 6. The SS calls for generic procedure C.3 to
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
862
Expected sequence
UE SS
CELL_FACH state of cell 1 and
the SS has configured its
"T0" in table 8.2.4.25.
3 TRANSPORT CHANNEL
RECONFIGURATION

4 Reconfiguration of transport
channel.
5 TRANSPORT CHANNEL
The UE sends this message in
cell 6.

Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the
Frequency info

DCCH using AM RLC in cell 6.
8.2.4.26 Void
8.2.4.27 Void
8.2.4.28 Void

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
863
CELL_DCH (Frequency band modification): Success

If the UE receives:
-a TRANSPORT CHANNEL RECONFIGURATION message;
it shall:
procedure:
UE shall:
configuration.
UE shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_DCH according to the TRANSPORT CHANNEL
2. To confirm that the UE transmits the TRANSPORT CHANNEL RECONFIGURATION COMPLETE message
on the uplink DCCH using AM RLC on a dedicated physical channel in a different frequency.
Initial Condition
UE: CS-DCCH_DTCH_DCH (state 6-9) or PS_DCCH_DTCH_DCH (state 6-10) as specified in clause 7.4 of TS
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
864
Test Procedure
Table 8.2.4.29
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-55 -72

Off -55
PCCPCH
RSCP
(TDD)
dBm
-55 -72 off -55
transmits a TRANSPORT CHANNEL RECONFIGURATION message including IE "Frequency info" set to frequency
information of cell 6 , and for FDD IE "Primary CPICH info" set to Primary Scrambling Code which is assigned to P-
CPICH of cell 6, for TDD IE Primary CCPCH info set to cell parameter ID which is assigned to P-CCPCH of cell 6.
The UE shall select cell 6 and reconfigure its transport channel parameters after receiving this message, and then remain
in CELL_DCH state. The UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE
message using AM RLC after completes configuration according to receiving TRANSPORT CHANNEL
RECONFIGURATION message. Upon completion of the procedure, the SS calls for generic procedure C.3 to check
that UE is in CELL_DCH state.
Expected sequence
UE SS
8.2.4.29.
3 TRANSPORT CHANNEL
RECONFIGURATION
Including IE "Frequency info" set
and for FDD IE "Primary CPICH
Code assigned to P-CPICH of cell
6. For 1.28 Mcps TDD, IE
Primary CCPCH info set to cell
parameter ID which is assigned to
P-CCPCH of cell 6
4 The UE select cell 6.
5 TRANSPORT CHANNEL
6.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
865
The contents TRANSPORT CHANNEL RECONFIGURATION message in this test case is identical the message sub-
type indicated by "Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" or "Non speech from in CS" in
[9] TS 34.108 clause 9, with the following exception:
Frequency info

TRANSPORT CHANNEL RECONFIGURATION (Step 3) (1.28 Mcps TDD)
The contents TRANSPORT CHANNEL RECONFIGURATION message in this test case is identical the message sub-
type indicated by "Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" or "Non speech from in CS" in
[9] TS 34.108 clause 9, with the following exception:
Frequency info
- Cell parameters ID Same as cell 6
8.2.4.30 Void
8.2.4.31 Void
8.2.4.32 Void
8.2.4.33 Void
8.2.4.34 Void
CELL_DCH: Success (serving HS-DSCH cell change with MAC-hs reset)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
866

If the IE "Added or Reconfigured DL TrCH information" is included then for the transport channel identified by the IE
"DL Transport Channel Identity" the UE shall:
1>if the choice "DL parameters" is set to 'HSDSCH':
2>if the IE "HARQ Info" is included:
3>perform the actions specified in subclause 8.6.5.6b.
2>if the value of the IE "MAC-hs reset indicator" is TRUE:
3>reset the MAC-hs entity[TS 25.321].

If the IE "Downlink information for each radio link" is included in a received message, the UE shall:
2>if the IE "Serving HS-DSCH radio link indicator" is set to 'TRUE':
3>consider this radio link as the serving HS-DSCH radio link;

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
867
Reference
3GPP TS 25.331 clauses 8.6.3.1, 8.6.5.6, 8.6.6.4, 8.6.6.32
To confirm that the UE changes the serving HS-DSCH cell according to the received TRANSPORT CHANNEL
RECONFIGURATION message, in case of MAC-hs reset.
Initial Condition
- UE supports FDD
Test Procedure
Table 8.2.4.35
T0 T1 T0 T1

UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/3.
84MHz
-60 -70

-70

-60

The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established in cell 1.
The SS transmits to the UE an ACTIVE SET UPDATE message in cell 1 on DCCH using AM RLC to add cell 2 to the
active set. When the UE receives this message, the UE shall configure layer 1 to begin reception without affecting the
current uplink and downlink activities of existing radio links and cell 1 shall be kept as the serving HS-DSCH cell. The
UE shall transmit an ACTIVE SET UPDATE COMPLETE message to the SS on the uplink DCCH using AM RLC.
The SS sends a MEASUREMENT CONTROL message to the UE configuring event 1D Change of best cell..
SS configures its downlink transmission power settings according to columns "T1" in table 8.2.4.35. UE shall transmit a
MEASUREMENT REPORT message which includes the primary scrambling code for cell 2 according to IE "Intra-
frequency event identity" set to 1d.
The SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to the UE . At the activation time the
UE changes the serving HS-DSCH radio link to cell 2. Finally the UE transmits a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE message using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
868
Expected sequence
UE SS
1 ACTIVE SET UPDATE The SS instructs the UE to add
cell 2 in the active set.
2 ACTIVE SET UPDATE COMPLETE The UE adds the radio link in cell
2.
3 MEASUREMENT CONTROL Configure event 1D Change of
best cell
4 SS SS configures its downlink
transmission power settings
8.2.4.35
5 MEASUREMENT REPORT See specific message contents
for this message
6 TRANSPORT CHANNEL
RECONFIGURATION

7 SS At the activation time, the SS
changes the serving HS-DSCH
radio link to cell 2 and performs a
MAC-hs reset.
8 TRANSPORT CHANNEL
RECONFIGURATION
COMPLETE


- CHOICE mode FDD
allocated to the UE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
869
Measurement command Setup
- CHOICE measurement type Intra-frequency measurement
- Intra-frequency measurement objects list Not present
- Intra-frequency measurement
quantity
Not present
- Intra-frequency reporting quantity Not present
- Reporting cell status Not present
- Measurement validity Not present
- Intra-frequency event identity 1D
- Triggering condition 2 Active set cells
- Hysteresis 4
- Time to trigger 20 mSec
- Measurement reporting transfer mode Acknowledged mode RLC
- Periodic reporting / Event trigger reporting mode Event trigger
Additional measurement list Not present
DPCH compressed mode status info Not present

MEASUREMENT REPORT (Step 5)
Measured results Check to see if this IE is absent
Additional Measured results Check to see if this IE is absent
Event results Check to see if set to "Intra-frequency event results"
- Event ID Check to see if set to "1D"
- Primary scrambling code Check to see if set to "Primary scrambling code of Cell
2"

Use the same message as specified for "Packet to CELL_DCH from CELL_DCH in PS" in 34.108 except for the
following:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
870
New H-RNTI '0101 0101 0101 0101'
Added or Reconfigured TrCH information list
- Added or Reconfigured DL TrCH information (for HS-DSCH)
- Downlink transport channel type HS-DSCH
- DL Transport channel identity Not present
- CHOICE DL parameters HS-DSCH
- HARQ Info Not present
- MAC-hs reset indicator TRUE
- Added or reconfigured MAC-d flow Not present
- HS-SCCH Info
- CHOICE mode FDD
- DL Scrambling Code
- HS-SCCH Channelisation Code Information
- HS-SCCH Channelisation Code 2
- Measurement Feedback Info
- CHOICE mode FDD
- POhsdsch 6 dB
- CQI Feedback cycle, k 4 ms
- CQI repetition factor 1
- DCQI -3 dB
- Choice mode FDD
- Serving HS-DSCH radio link indicator FALSE
- Code number 0
- Choice mode FDD
- Code number 0
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
871

After step 4, the UE shall transmit a MEASUREMENT REPORT message.
After step 7, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message.
8.2.5 Transport format combination control
8.2.5.1 Void
NOTE Test case Transport format combination control in CELL_DCH: restriction have been removed as being
implicitely tested by radio bearer test cases in clause 14.
8.2.5.2 Void
NOTE Test case Transport format combination control in CELL_DCH: release a restriction have been
removed as being implicitely tested by radio bearer test cases in clause 14.
8.2.5.3 Void

8.2.5.4 Transport format combination control in CELL_DCH: Failure (Invalid
configuration)

If the variable INVALID_CONFIGURATION is set to TRUE due to the received TRANSPORT FORMAT
COMBINATION CONTROL message the UE shall:
1>if the TRANSPORT FORMAT COMBINATION CONTROL message was received on AM RLC:
2>keep the TFC subset existing before the TRANSPORT FORMAT COMBINATION CONTROL message
was received;
2>transmit a TRANSPORT FORMAT COMBINATION CONTROL FAILURE message on the DCCH using
AM RLC;
2>set the IE "RRC transaction identifier" in the TRANSPORT FORMAT COMBINATION CONTROL
FAILURE message to the value of "RRC transaction identifier" in the entry for the TRANSPORT FORMAT
COMBINATION CONTROL message in the table "Accepted transactions" in the variable
TRANSACTIONS; and
2>clear that entry;
2>set the IE "failure cause" to "invalid configuration";
2>when the TRANSPORT FORMAT COMBINATION CONTROL FAILURE message has been submitted to
lower layers for transmission the procedure ends.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
872
1>if the TRANSPORT FORMAT COMBINATION CONTROL message was received on UM RLC:
2>ignore the TRANSPORT FORMAT COMBINATION CONTROL message.
Reference
3GPP TS 25.331 clause 8.2.5.4, 8.2.5.5
To confirm that the UE transmits a TRANSPORT FORMAT COMBINATION CONTROL FAILURE message on the
DCCH using AM RLC if it receives a TRANSPORT FORMAT COMBINATION CONTROL message including an
invalid configuration.
Initial Condition
UE: DCCH+DTCH_DCH (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN
domain(s) supported by the UE.
Test Procedure
message back to SS. SS transmits a TRANSPORT FORMAT COMBINATION CONTROL message including some
IEs set to get an invalid configuration. The UE keeps its current configuration and transmits a TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message on the DCCH using AM RLC, setting the value "invalid
configuration" to IE "failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT
Expected sequence
UE SS
measurement.
1 UE is in CELL_DCH state with
a DCH for a signalling radio
bearer and a DCH for a radio
access bearer.
2

Void
3

Void
3a Void
4 TRANSPORT FORMAT
COMBINATION CONTROL
This message includes an
invalid configuration.
5 TRANSPORT FORMAT
COMBINATION CONTROL FAILURE
The UE shall not change its
configuration

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
873
Mode

MEASUREMENT REPORT (Step 0band 6)
Check to see if the same message type found in [9] TS 34.108 Clause 9 is received, with the following exceptions:
The order in which the RBs are reported is not checked.

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

TRANSPORT FORMAT COMBINATION CONTROL (Step 4)
Use the same message sub-type titled "TRANSPORT FORMAT COMBINATION CONTROL" in [9] TS 34.108
clause 9, with following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
874
TrCH information elements
-DPCH/PUSCH TFCS uplink in uplink
- Restricted TrCH information
- Restricted UL TrCH identity 15 ( for RACH transport channel identity)
- Allowed TFI 0

TRANSPORT FORMAT COMBINATION CONTROL FAILURE (Step 5)
RRC transaction identitifer Checked to see if it is set to identical value of the same
IE in the downlink TRANSPORT FORMAT
COMBINATION CONTROL message.

After step 4 the UE shall transmit a TRANSPORT FORMAT COMBINATION CONTROL FAILURE message on the
DCCH using AM RLC, setting IE "failure cause" to "invalid configuration".
8.2.6 Physical channel reconfiguration
8.2.6.1 Physical channel reconfiguration for transition from CELL_DCH to
CELL_DCH (code modification): Success

If the UE receives:
- a PHYSICAL CHANNEL RECONFIGURATIONmessage; or
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
875
UE shall:
configuration.
1>clear that entry;
shall:
1>transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message on the uplink
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures the physical channel parameters according to a PHYSICAL CHANNEL
RECONFIGURATION message received from the SS. After the reconfiguration, the UE shall be able to communicate
with the SS on the new physical channel.
Initial Condition
34.108, depending to the CN domain(s) supported by the UE.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the
UE, which includes a new several physical layer parameters. The UE shall reconfigure the physical channel at the
activation time specified in this message and transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message on the uplink DCCH AM RLC after its transition. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
See message contents
2 PHYSICAL CHANNEL


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
876
PHYSICAL CHANNEL RECONFIGURATION (FDD)
The contents of PHYSICAL CHANNEL RECONFIGURATION message in this test case is identical to the message
sub-type titled as "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found
Maximum allowed UL Tx power 31dBm
Uplink DPCH info
- Code number 1

PHYSICAL CHANNEL RECONFIGURATION (TDD)
Downlink information common for all radio links Absent

CELL_DCH (code modification): Failure (Unsupported configuration)

specified below:
2>clear that entry;

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
877
The UE shall:
1>in case of reception of a PHYSICAL CHANNEL RECONFIGURATION message:

2>transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE as response message on the DCCH
using AM RLC.

Reference
3GPP TS 25.331 clause 8.2.2.6, 8.2.2.9, 8.5.20.
To confirm that the UE keeps its configuration and transmits a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC if the received PHYSICAL CHANNEL RECONFIGURATION
message includes unsupported configuration parameters for the UE.
Initial Condition
Test Procedure
message back to SS.The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE which
includes configuration parameters unsupported by the UE. The UE transmits a PHYSICAL CHANNEL
RECONFIGURATION FAILURE message on the DCCH using AM RLC . UE shall continue its traffic volume
measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
measurement.
1 PHYSICAL CHANNEL
RECONFIGURATION
Includes configuration
unsupported by the UE
2 PHYISICAL CHANNEL
The UE shall not reconfigure and
continue to communicate using
the old configuration.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
878
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
879
PHYSICAL CHANNEL RECONFIGURATION (FDD) (Step 1)
[9] TS 34.108 Clause 9 with the following exceptions:
Frequency info

PHYSICAL CHANNEL RECONFIGURATION (TDD) (Step 1)
sub-type title "Packet to CELL_DCH from CELL_DCH in PS" found in [9] TS 34.108 Clause 9 with the following
exceptions:
Frequency info
- UARFCN (Nt) 0

PHYSICAL CHANNEL RECONFIGURATION FAILURE (Step 2)
The contents of PHYSICAL CHANNEL RECONFIGURATION FAILURE message in this test case is the same as the
PHYSICAL CHANNEL RECONFIGURATION FAILURE message as found in [9] TS 34.108 Clause 9, with the

After step 1 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH
using AM RLC .
8.2.6.3 Void
8.2.6.4 Void
CELL_DCH (code modification): Failure (Incompatible simultaneous
reconfiguration)

- PHYSICAL CHANNEL RECONFIGURATION; or
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
880

the UE shall:


3>else:
4>reject the transaction; and
4>if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in
the variable TRANSACTIONS:
5>store the IE "Message type" and the IE "RRC transaction identifier" of the received message in the
table "Rejected transactions" in the variable TRANSACTIONS.

If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable
PROTOCOL_ERROR_REJ ECT is set to FALSE, the UE shall:
1>not apply the configuration contained in the received reconfiguration message;
1>transmit a failure response message as specified in subclause TS 25.331 8.2.2.9, setting the information elements
as specified below:
2>clear that entry;
2>set the IE "failure cause" to "incompatible simultaneous reconfiguration".

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.9, 8.2.2.12, clause 8.6.3.11.
To confirm that if the UE receives a PHYSICAL CHANNEL RECONFIGURATION message during a reconfiguring
procedure due to a radio bearer message other than PHYSICAL CHANNEL RECONFIGURATION, it shall keep its
configuration as if the PHYSICAL CHANNEL RECONFIGURATION message had not been received and complete
the reconfiguration procedure according to the previously received message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
881
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RECONFIGURATION message to the UE. The
SS transmits a PHYSICAL CHANNEL RECONFIGURATION message before the "activation time" indicated in the
RADIO BEARER RECONFIGURATION message expires. When the UE receives the PHYSICAL CHANNEL
RECONFIGURATION message, the UE shall keep the configuration as if it had not received the PHYSICAL
CHANNEL RECONFIGURATION message and shall transmit a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC with IE "failure cause" set to "incompatible simultaneous
reconfiguration". After the SS acknowledges the PHYSICAL CHANNEL RECONFIGURATION FAILURE message,
the UE reconfigures the new physical channel parameters upon the activation time and transmits a RADIO BEARER
RECONFIGURATION COMPLETE message on DCCH using AM RLC. SS calls for generic procedure C.3 to check
that UE is in CELL_DCH state.
Expected sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
Sent before the "activation time"
specified in the message in step 1
has elapsed.
3 PHYSICAL CHANNEL
configuration due to the reception
of a PHYSICAL CHANNEL
COMPLETE
This message is on DCCH using
AM RLC.

For RADIO BEARER RECONFIGURATION in step 1, use the message sub-type indicated as "Speech in CS" or "Non
speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in Annex A with the following exceptions:
Activation Time Info Current CFN-[current CFN mod 8 +8 ]
Uplink DPCH info

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
882
Activation Time Current CFN-[current CFN mod 8 +8 ]

PHYSICAL CHANNEL RECONFIGURATION (Step 2) (FDD)
Uplink DPCH info

PHYSICAL CHANNEL RECONFIGURATION (Step 2) (TDD)
- First timeslot code list Different as assigned in Step 1

PHYSICAL CHANNEL RECONFIGURATION FAILURE (step 3)
PHYSICAL CHANNEL RECONFIGURATION FAILURE message as found in Annex A, with the following
exceptions:
Failure cause Incompatible simultaneous reconfiguration

using AM RLC with IE "failure cause" set to "Incompatible simultaneous reconfiguration".
After step 3 the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE message using AM RLC
on the DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
883
CELL_DCH (code modification): Failure (Invalid message reception and
Invalid configuration)

The UE shall:
as specified below:
2>clear that entry;

as specified below:
3>clear that entry.

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.13, 8.2.2.11, 8.2.2.9.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
884
To confirm that the UE transmits a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH
using AM RLC if it receives an invalid PHYSICAL CHANNEL RECONFIGURATION message which does not
include any IEs except IE "Message Type".
using AM RLC if it receives a PHYSICAL CHANNEL RECONFIGURATION message including some IEs set to give
an invalid configuration.
Initial Condition
Test Procedure
message back to SS. The SS transmits an invalid PHYSICAL CHANNEL RECONFIGURATION message to the UE,
which contains an unexpected critical message extension. The UE keeps the old configuration and transmits a
PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM RLC, with a value
"protocol error" in IE "failure cause" and also a value "Message extension not comprehended" in IE "Protocol error
cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT messages back to SS
periodically. SS transmits a PHYSICAL CHANNEL RECONFIGURATION message including some IEs which are set
to give an invalid configuration. The UE keeps its initial configuration and transmits a PHYSICAL CHANNEL
RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting the value "invalid configuration" to
IE "failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT messages
back to SS periodically.
Expected sequence
UE SS
measurement.
1 PHYSICAL CHANNEL
RECONFIGURATION
See specific message content.
2 PHYSICAL CHANNEL
The UE does not change its
configuration.
3 PHYSICAL CHANNEL
RECONFIGURATION
This message includes IEs which
is set to give an invalid
configuration
4 The UE does not change its
configuration
5 PHYSICAL CHANNEL
to "invalid configuration

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
885
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

PHYSICAL CHANNEL RECONFIGURATION (Step 1)
Use the PHYSICAL CHANNEL RECONFIGURATION message as defined in [9] TS 34.108 clause 9, with the

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
886
exceptions:
Failure cause

Annex A with the following exceptions:
- Timing Indicator Initialise
- Default DPCH Offset Value 512
- DPCH frame offset 1024

sub-type title as "Speech in CS" or "Non speech in CS" or "Packet to CELL_FACH from CELL_DCH in PS" as found
in Annex A with the following exceptions:
-PRACH TFCS Present

exceptions:

using AM RLC, setting value "protocol error" in IE "failure cause" and also setting value "Message extension not
comprehended" in IE "Protocol error cause".
using AM RLC, setting IE "failure cause" to "invalid configuration".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
887
CELL_FACH: Success

If the UE receives:
- a PHYSICAL CHANNEL RECONFIGURATION message; or
it shall:
procedure:
The UE shall then:


1>clear that entry;

shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
888
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures a common physical channel according to the PHYSICAL CHANNEL
RECONFIGURATION message, which invoke the UE to transit from CELL_DCH to CELL_FACH.
Initial Condition
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108
Test Procedure
The UE is in CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the
UE. The UE shall then reconfigure the specified common physical channel according to this message and the system
information messages. Following this, it shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message using AM RLC on the DCCH. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
IE "Uplink DPCH Info" and IE
"Downlink DPCH Info" are not
specified.
2 UE shall perform the
reconfiguration.
3 PHYSICAL CHANNEL


PHYSICAL CHANNEL RECONFIGURATION
Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in Annex A with the following
exception:
New C-RNTI 0000 0000 0000 0001B

After step 2 the UE shall transit from CELL_DCH to CELL_FACH and transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE messageon the common physical channel.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
889
CELL_FACH: Success (Cell re-selection)

If the UE receives:
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
890
the UE shall:
1>clear that entry;
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.3.1.7.
To confirm that the UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after the UE
completes a cell update procedure.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message, which
includes IE "Primary CPICH info" and no dedicated physical channel information to invoke the UE to transit from
CELL_DCH to CELL_FACH. As the UE cannot detect the specified cell, the UE shall initiate the cell update
procedure. The UE transmits a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "cell
reselection". The SS shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after receiving a CELL
UPDATE message. The UE then transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH
using AM RLC. The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
891
Expected sequence
UE SS
1 Void
2 PHYSICAL CHANNEL
RECONFIGURATION
This message include IE
"Primary CPICH info" for FDD
and Primary CCPCH info for
TDD.
3 Void
CONFIRM

7 PHYSICAL CHANNEL

exceptions:

exceptions:
- Cell parameters ID 4

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in Annex A
for FDD and Annex A for TDD with the following exceptions:

Use the same message type found in clause Annex A, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
892
reselection".
RLC.
After step 6 UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the DCCH
using AM RLC.
8.2.6.9 Physical channel reconfiguration for transition from CELL_FACH to
CELL_DCH: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
1>clear that entry;

shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE reconfigures a new physical channel according to a PHYSICAL CHANNEL
RECONFIGURATION message, which invoke UE to transit from CELL_FACH to CELL_DCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
893
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE
to transit from CELL_DCH to CELL_FACH. The UE shall reconfigure the common physical channel correctly
according to this message. To complete this procedure, the UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC. The SS transmits a PHYSICAL CHANNEL
RECONFIGURATION message to the UE to invoke the UE to transit from CELL_FACH to CELL_DCH. The UE
shall reconfigure the new dedicated physical channel correctly according to this message. To complete this procedure,
the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message using AM RLC. SS
calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
specified.
reconfiguration.
3 PHYSICAL CHANNEL

4 PHYSICAL CHANNEL
RECONFIGURATION

5 The UE shall configure the
allocated dedicated physical
channels.
6 PHYSICAL CHANNEL


Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in Annex A for FDD and Annex A
for TDD.
Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in Annex A.
After step 2 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION message on the common physical
channel.
After step 5 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION message on the new dedicated
physical channel.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
894
8.2.6.10 Void
CELL_DCH: Failure (Physical channel failure and successful reversion to old
configuration)



as specified below:
2>clear that entry;

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration and transmits a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC if the UE fails to reconfigure the new physical channel according to a
PHYSICAL CHANNEL RECONFIGURATION message before the T312 expiry.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
895
Initial Condition
Test Procedure
to invoke the UE to transit from CELL_DCH to CELL_FACH. The UE shall reconfigure the common physical channel
correctly according to this message. To complete this procedure, the UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC. SS then send a MEASUREMENT CONTROL message
to UE. The UE shall perform periodical traffic volume measurement according to this message and then transmit
MEASUREMENT REPORT message back to SS. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION
message to the UE to invoke the UE to transit from CELL_FACH to CELL_DCH. However, the SS keeps its current
physical channel configuration and then the UE cannot synchronise with the SS. After T312 expires, the UE attempt to
revert to the old configuration. Then the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC which is set "physical channel failure" in IE "failure cause". UE shall
continue its traffic volume measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
specified.
reconfiguration
3 PHYSICAL CHANNEL

measurement.
4 PHYSICAL CHANNEL
RECONFIGURATION

physical channel, hence the UE
shall detect a failure to
reconfigure to the new physical
channel.
6 PHYSICAL CHANNEL
After T312 expires the UE reverts
to the old configuration and
transmits this message.

Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in clause 9 of TS 34.108 for FDD or
for TDD.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
896
Mode
- UE state All states except CELL_DCH

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in clause 9 of TS 34.108 for FDD or
for TDD.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
897
PHYSICAL CHANNEL RECONFIGURATION FAILURE message as found in clause 9 of TS 34.108, with the

RECONFIGURATION message on the common physical channel.
using AM RLC, specifying "physical channel failure" in IE "failure cause".
CELL_DCH: Failure (Physical channel failure and cell re-selection)



1>if the old configuration does not include dedicated physical channels (CELL_FACH state):
2>if the UE selects another cell than the cell the UE camped on upon reception of the reconfiguration message:
3>initiate a cell update procedure according to TS 25.331 subclause 8.3.1, using the cause "Cell
reselection";
4>proceed as below.
as specified below:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
898
2>clear that entry;

- does not include "CN information elements"; and
- does not include the IE "Ciphering mode info"; and
- does not include the IE "Integrity protection mode info"; and
- does not include the IE "New C-RNTI"; and
- does not include the IE "New U-RNTI":
the UE shall:
1>transmit no response message.

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9,8.3.1.7, 8.5.4
To confirm that the UE initiates a cell update procedure after it fails to reconfigure the new physical channel and selects
another cell.
To confirm that UE transmits a PHYSICAL CHANNEL RECONFIGURATION FAILURE message after UE
completes cell update procedure.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
899
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108 in cell 1
Test Procedure
Table 8.2.6.12
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -75

-75

-60
P-CCPCH
RSCP
(TDD)
dBm
-60 -75 -75 -60

The UE is in CELL_DCH state in cell 1. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message
to the UE to invoke the UE to transit from CELL_DCH to CELL_FACH. The UE shall reconfigure the common
physical channel correctly according to this message. To complete this procedure, the UE shall transmit a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message using AM RLC. Then SS transmits a PHYSICAL
CHANNEL RECONFIGURATION message to the UE, but the SS does not reconfigure L1 accordingly. The SS
configures its downlink transmission power settings according to columns "T1"in table 8.2.6.12. As a result, the UE
fails to synchronise on the new physical channel before timer T312 expires. UE may send a PHYSICAL CHANNEL
RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting IE "failure cause" to "physical
channel failure" to cell 1. UE reselects to cell 2 and then the UE shall transmit a CELL UPDATE message on uplink
CCCH with IE "Cell update cause" set to "Cell reselection". The SS shall transmit a CELL UPDATE CONFIRM
message on downlink DCCH after receiving a CELL UPDATE message. If not already done so, the UE may transmit a
PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting IE "failure
cause" to "physical channel failure" in cell 2. UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM
message on the DCCH using AM RLC in cell 2 to acknowledge the reception of new C-RNTI value. If not already done
so, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using
AM RLC, setting IE "failure cause" to "physical channel failure".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
900
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
specified.
reconfiguration
3 PHYSICAL CHANNEL

4 PHYSICAL CHANNEL
RECONFIGURATION
The SS does not configure the
new dedicated physical channel
in accordance with the settings
in the message and applies the
settings, according to the values
in columns "T1" of table
8.2.6.12.
5 PHYSICAL CHANNEL
RECONGURATION FAILURE (option 1)
UE shall transmit this message
in the cell 1.
6 Void
value "cell reselection" set in IE
8 CELL UPDATE CONFIRM
8a PHYSICAL CHANNEL RECONGURATION
FAILURE (option 2)
in the cell 2.
CONFIRM

10 PHYSICAL CHANNEL
RECONGURATION FAILURE (option 3)
in the cell 2.

Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in Clause 9 of TS 34.108 for FDD
or for TDD.
Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in Clause 9 of TS 34.108 for FDD
or for TDD.
The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in Clause 9
of TS 34.108 for FDD or for TDD with the following exceptions:
U-RNTI
- SRNC Identity Assigned previously in cell 1
- S-RNTI Assigned previously in cell 1

in Clause 9 of TS 34.108, with the following exception.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
901
New C-RNTI '1010 1010 1010 1010'

The contents of UTRAN MOBILITY INFORMATION CONFIRM message is identical as "Contents of UTRAN
MOBILITY INFORMATION CONFIRM message" as found in Clause 9 of TS 34.108 for FDD or for TDD.
PHYSICAL CHANNEL RECONGURATION FAILURE (Steps 5, 8a and 10)
PHYSICAL CHANNEL RECONFIGURATION FAILURE message as found in Clause 9 of TS 34.108, with the

After step 6 the UE shall transmit a CELL UPDATE message using RLC-TM mode on the uplink CCCH with IE "Cell
update cause" set to "cell reselection" in cell 2.
After step 8, UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message.
The UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM
RLC, setting the IE "failure cause" to "physical channel failure" after step 4, 8 or 9.
8.2.6.13 Void
CELL_DCH: Failure (Invalid message reception and Invalid configuration)

The UE shall:
as specified below:
2>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
902

as specified below:
3>clear that entry.

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.13, 8.2.2.11, 8.2.2.9
using AM RLC if the received message does not include any IEs except IE "Message Type".
using AM RLC if it receives a PHYSICAL CHANNEL RECONFIGURATION message including some IEs which are
set to give an invalid configuration.
Initial Condition
Test Procedure
RECONFIGURATION COMPLETE message using AM RLC. SS then send a MEASUREMENT CONTROL message
to UE. The UE shall perform periodical traffic volume measurement according to this message and then transmit
MEASUREMENT REPORT message back to SS. The SS transmits an invalid PHYSICAL CHANNEL
RECONFIGURATION message to the UE which contains an unexpected critical message extension. The UE keeps the
old configuration and transmits a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
903
using AM RLC, setting "protocol error" in IE "failure cause" and also setting "Message extension not comprehended" in
IE "Protocol error cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT
messages back to SS periodically. SS transmits PHYSICAL CHANNEL RECONFIGURATION message including
some IEs which are set to give an invalid configuration. The UE keeps current configuration and transmits a
PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using AM RLC, setting IE "failure
cause" to "invalid configuration". UE shall continue its traffic volume measurement and send MEASUREMENT
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
specified.
reconfiguration
3 PHYSICAL CHANNEL
The UE enters CELL_FACH
state.
measurement.
4 PHYSICAL CHANNEL
RECONFIGURATION
See specific message content.
5 PHYSICAL CHANNEL
configuration.
6 PHYSICAL CHANNEL
RECONFIGURATION
This message includes IEs which
are set to give an invalid
configuration.
7 The UE does not change the
configuration
8 PHYSICAL CHANNEL
to "invalid configuration

Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in Annex A for FDD and Annex A
for TDD.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
904
Mode

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

Use the PHYSICAL CHANNEL RECONFIGURATION message as defined in [9] TS 34.108 clause 9, with the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
905

exceptions:
Failure cause

sub-type title "Packet to CELL_DCH from CELL_FACH in PS" as found in Annex A with the following exceptions:

sub-type title "Packet to CELL_DCH from CELL_FACH in PS" as found in Annex A with the following exceptions:
-PRACH TFCS Present

exceptions:

After step 4 the UE shall keep its old configuration, transmit a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC with "protocol error" in IE "failure cause" and also "Message
extension not comprehended" in IE "Protocol error cause".
using AM RLC, setting IE "failure cause" to "invalid configuration".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
906
8.2.6.15 Void
8.2.6.16 Void
CELL_DCH (code modification): Success (Subsequently received)

UE shall:

the UE shall:
3>else:

Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a PHYSICAL CHANNEL RECONFIGURATION message before the UE
reconfigures the radio bearer according to the previous PHYSICAL CHANNEL RECONFIGURATION message it
ignores the new PHYSICAL CHANNEL RECONFIGURATION message and reconfigures according to the previous
PHYSICAL CHANNEL RECONFIGURATION message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
907
Initial Condition
Test Procedure
The UE is in the CELL_DCH state. When the SS transmits a PHYSICAL CHANNEL RECONFIGURATION message
to the UE before the activation time specified in the previous PHYSICAL CHANNEL RECONFIGURATION message
elapses, the UE ignores the new PHYSICAL CHANNEL RECONFIGURATION message and reconfigures according
to the previous PHYSICAL CHANNEL RECONFIGURATION message received. Finally, the UE shall transmit a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the DCCH using AM RLC. SS calls for
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
For FDD mode Scrambling code
number is set to "1". For TDD
mode a code combination is
assigned by SS.
2 PHYSICAL CHANNEL
RECONFIGURATION
SS send this message before the
expiry of "activation time"
specified in PHYSICAL
message of step 1. For FDD, the
set to "2". For TDD, the code
to that assigned in stage 1.
3 PHYSICAL CHANNEL
The UE ignores the PHYSICAL
message in step 2 and confirms
PHYSICAL CHANNEL
step 1.

Activation Time Info [256+Current CFN-[current CFN mod 8 +8 ]]MOD 256
- Uplink DPCH info

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
908

- Uplink DPCH info

PHYSICAL CHANNEL RECONFIGURATION (Step2) (TDD)
sub-type title "Packet to CELL_DCH from CELL_DCH in PS" found in [9] TS 34.108 clause 9 with the following
exceptions:

DCCH using AM RLC.
CELL_DCH: Success (Subsequently received)

UE shall:

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
909
3>else:
Reference
3GPP TS 25.331 clause 8.6.3.11.
To confirm that if the UE receives a PHYSICAL CHANNEL RECONFIGURATION message before the UE
reconfigures the radio bearer according to the previous PHYSICAL CHANNEL RECONFIGURATION message it
ignores the new PHYSICAL CHANNEL RECONFIGURATION message and reconfigures according to the previous
PHYSICAL CHANNEL RECONFIGURATION message.
Initial Condition
Test Procedure
RECONFIGURATION COMPLETE message using AM RLC. When the SS transmits a PHYSICAL CHANNEL
RECONFIGURATION message to the UE before the activation time specified in the previous PHYSICAL CHANNEL
RECONFIGURATION message, the UE ignores the new PHYSICAL CHANNEL RECONFIGURATION message
and reconfigures according to the previous PHYSICAL CHANNEL RECONFIGURATION message received. Finally,
the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the DCCH using
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
910
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
specified.
reconfiguration
3 PHYSICAL CHANNEL
The UE enters CELL_FACH
state.
4 PHYSICAL CHANNEL
RECONFIGURATION
Scrambling code number is set to
"1" for FDD mode and A code
combination is assigned by SS for
TDD
5 PHYSICAL CHANNEL
RECONFIGURATION
For FDD the IE "Scrambling code
number" is set to "2". For TDD,
the code combination assigned is
different from that assigned in
stage 4.
6 PHYSICAL CHANNEL
The UE ignores the PHYSICAL
message in step 5 and confirms
PHYSICAL CHANNEL
step 4.

Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9.
sub-type title "Packet to CELL_DCH from CELL_FACH in PS" as found in [9] TS 34.108 clause 9 with the following
exceptions:
- Uplink DPCH info

sub-type title "Packet to CELL_DCH from CELL_FACH in PS" as found in [9] TS 34.108 clause 9 with the following
exceptions:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
911
exceptions:
- Uplink DPCH info

exceptions:

DCCH using AM RLC.
8.2.6.19 Physical Channel Reconfiguration from CELL_DCH to CELL_PCH: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
912
response message:

1>clear that entry;
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and enter
CELL_PCH state after it received a PHYSICAL CHANNEL RECONFIGURATION message, which invokes the UE to
transit from CELL_DCH to CELL_PCH.
Initial Condition
Test Procedure
The UE is in CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message, which
invokes the UE to transit from CELL_DCH to CELL_PCH. The UE transmits a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC and enters CELL_PCH state. SS calls for generic
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
913
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION

2 PHYSICAL CHANNEL

3 The UE is in CELL_PCH state.

Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in Annex A with following
exceptions:

exceptions:

After step 1 the UE shall transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
DCCH using AM RLC.
8.2.6.20 Physical Channel Reconfiguration from CELL_DCH to URA_PCH: Success
If the UE receives:
it shall:
procedure:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
914
The UE shall then:
response message:

1>clear that entry;
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
To confirm that the UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and enter
URA_PCH state after it received a PHYSICAL CHANNEL RECONFIGURATION message, which invokes the UE to
transit from CELL_DCH to URA_PCH.
Initial Condition
Test Procedure
The UE is in the CELL_DCH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message,
which invoke the UE to transit from CELL_DCH to URA_PCH. The UE transmits a PHYSICAL CHANNEL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
915
RECONFIGURATION COMPLETE message using AM RLC and enters URA_PCH state. SS calls for generic
procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION

2 PHYSICAL CHANNEL

3 The UE is in URA_PCH state.

exceptions:
URA Identity 0000 0000 0000 0001B

URA Identity 0000 0000 0000 0001B

DCCH using AM RLC.
8.2.6.21 Physical Channel Reconfiguration from CELL_FACH to URA_PCH: Success
1. In case the procedure was triggered by reception of a PHYSICAL CHANNEL RECONFIGURATION message,
the UE shall:
- transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message on the uplink
DCCH using AM RLC;
2. If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted using the old
configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was
included in the received reconfiguration message, and the UE shall:
- when RLC has confirmed the successful transmission of the response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
916
- for each radio bearer in the variable PDCP_SN_INFO:
- if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
- configure the RLC entity for that radio bearer to "continue";
- enter the new state (CELL_PCH or URA_PCH, respectively);
Reference
3GPP TS 25.331 clause 8.2.2.4
1. To verify that the UE, when receiving a PHYSICAL CHANNEL RECONFIGURATION message, responds by
transmitting a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH
using AM RLC.
2. To verify that the response message is transmitted using the old configuration before the state transition, and that
the UE enters the URA_PCH state.
Initial Condition
Test Procedure
The UE is in the CELL_FACH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message. The
UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS using AM RLC and
enters into URA_PCH state. SS calls for generic procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION

2 PHYSICAL CHANNEL
before start state transition.
3 Reconfiguration of Physical
Channel after state transition.
fails.

Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in Annex A with following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
917

1. After step 1 the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the UE
8.2.6.22 Physical Channel Reconfiguration from CELL_FACH to CELL_PCH: Success

1. In case the procedure was triggered by reception of a PHYSICAL CHANNEL RECONFIGURATION message,
the UE shall:
- transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE as response message on the uplink
DCCH using AM RLC;
2. If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted using the old
configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was
included in the received reconfiguration message, and the UE shall:
- when RLC has confirmed the successful transmission of the response message:
- for each radio bearer in the variable PDCP_SN_INFO:
- if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
- configure the RLC entity for that radio bearer to "continue";
- enter the new state (CELL_PCH or URA_PCH, respectively);
Reference
3GPP TS 25.331 clause 8.2.2.4
1. To verify that the UE, when receiving a PHYSICAL CHANNEL RECONFIGURATION message, responds by
transmitting a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH
using AM RLC.
2. To verify that the response message is transmitted using the old configuration before the state transition, and that
the UE enters the CELL_PCH state.
Initial Condition
UE: PS-DCCH+DTCH_FACH(state 6-11) as specified in clause 7.4 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
918
Test Procedure
The UE is in the CELL_FACH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message. The
UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS using AM RLC and
enters into CELL_PCH state. SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION

2 PHYSICAL CHANNEL
before start state transition.
3 Reconfiguration of Physical
Channel after state transition.

Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in Annex A with following
exceptions:

1. After step 1 the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the UE
CELL_DCH (Hard handover to another frequency with timing maintain):
Success

If the UE receives:
- a PHYSICAL CHANNEL RECONFIGURATION message:
it shall:
procedure:
The UE shall then:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
919
UE shall:
configuration.
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
To confirm that the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC, on a dedicated physical channel in a different frequency band.
Initial Condition
Test Procedure
Table 8.2.6.23
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -55 Off -55

transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE, which includes new frequency
information and IE "Timing indicator" set to maintain. The UE shall reconfigure the physical channel parameters
according to PHYSICAL CHANNEL RECONFIGURATION message and establish a radio link with the SS using a
dedicated physical channel in cell 6. The UE then transmits a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message in cell 6 on the uplink DCCH AM RLC after its transition. SS calls for generic procedure C.3 to
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
920
Expected sequence
UE SS
table 8.2.6.23.
3 PHYSICAL CHANNEL
RECONFIGURATION
Including new frequency
information.
IE "Timing indicator" is set to
maintain.
4 The UE remains in CELL_DCH
state after connecting to the SS
on a dedicated physical channel
in cell 6.
5 PHYSICAL CHANNEL
The UE transmits this message in
cell 6.

Uplink DPCH info
Frequency info

uplink DCCH using AM RLC in cell 6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
921
8.2.6.24 Void

If the UE receives:
-a PHYSICAL CHANNEL RECONFIGURATION message;
it shall:
1>if the received reconfiguration message included the IE "Primary CPICH info" (, and the UE selects another cell
than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info":
transmission";
4>proceed as below.
transmission";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
922
4>proceed as below.
shall:
1>transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_DCH to CELL_FACH according to the PHYSICAL CHANNEL
2. To confirm that the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on
the uplink DCCH using AM RLC on a common physical channel in a different frequency..
Initial Condition
Test Procedure
Table 8.2.6.25
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

columns "T0" in table 8.2.6.25. The SS and UE execute procedure P5. Next The SS and the UE execute procedure P9
and then execute procedure P13.The SS switches its downlink transmission power settings to columns "T1" and
transmits a PHYSICAL CHANNEL RECONFIGURATION message with no IE "Frequency info" and IE "Primary
CPICH info". The UE selects cell 6 and and initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell
reselection". Upon completion of the cell update procedure, UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC on the DCCH in cell 6. The SS calls for generic
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
923
Expected sequence
UE SS
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

3 Void
4 PHYSICAL CHANNEL
RECONFIGURATION
No including IE "Frequency info"
CONFIRM

8 PHYSICAL CHANNEL
The UE sends this message on
a common physical channel in
cell 6.

Use the message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9, with the


New C-RNTI 0000 0000 0000 0001B

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
924
AM RLC in cell 6.
8.2.6.26 Physical Channel Reconfiguration from CELL_DCH to CELL_PCH

If the UE receives:
it shall:
procedure:
The UE shall then:
shall:
1>transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE on the uplink DCCH using AM RLC,
using the old configuration before the state transition.
response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
925
1>if the UE enters CELL_PCH state from CELL_DCH state, and the received reconfiguration message included
the IE "Primary CPICH info", and the UE selected another cell than indicated by this IE or the received
reconfiguration message did not include the IE "Primary CPICH info":
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
2. To confirm that the UE transits from CELL_DCH to CELL_PCH according to the PHYSICAL CHANNEL
3. To confirm that the UE releases a dedicated physical channel and selects a common physical channel in a
different frequency.
Initial Condition
Test Procedure
Table 8.2.6.26
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

columns "T0" in table 8.2.6.26. The SS and UE execute procedure P5. Next The SS and the UE execute procedure P9
and then execute procedure P13. The SS switches its downlink transmission power settings to columns "T1" and
transmits a PHYSICAL CHANNEL RECONFIGURATION message, which invokes the UE to transit from
CELL_DCH to CELL_PCH. The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message using AM RLC and enters CELL_PCH state. The UE selects cell 6 and initiates CELL UPDATE procedure
with IE "Cell update cause" set to "cell reselection". Upon completion of the procedure, the SS calls for generic
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
926
Expected sequence
UE SS
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108..

7.4.2.6.2) specified in TS 34.108.

3 Void
4 PHYSICAL
CHANNELRECONFIGURATION
Not including IE" frequency info "
5 PHYSICAL CHANNEL
UE transmit this message in cell
1.
"CELL_PCH".

Frequency info
- UARFCN uplink (Nu) Same uplink UARFCN as used for cell 6
- UARFCN downlink (Nd) Same downlink UARFCN as used for cell 6


RRC State Indic CELL_PCH

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
927
reselection" in cell 6.
8.2.6.27 Physical channel reconfiguration from CELL_FACH to CELL_PCH: Success

If the UE receives:
it shall:
procedure:
The UE shall then:
shall:
response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
928
3GPP TS 25.331 clause 8.2.2,8.3, 8.5 and 8.6.
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the PHYSICAL CHANNEL
Initial Condition
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION
message. The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message using AM RLC
and enters CELL_PCH state. The SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
UE SS
of cell 1.
2 PHYSICAL CHANNEL
RECONFIGURATION

3 PHYSICAL CHANNEL



Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
929
After step 2 the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on uplink
DCCH using AM RLC.
CELL_DCH (Downlink channelisation code modification): Success

If the UE receives:
it shall:
procedure:
UE shall:
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6..
1. To confirm that the UE change assigned downlink channelisation code by SS according to a PHYSICAL
2. To confirm that the UE response PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
930
Test Procedure
The UE is in CELL_DCH state of cell 1. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message
to the UE, which includes IE " DL channelisation code " set to New DL channelisation code. The UE shall change its
downlink channelisation code for a dedicated physical channel, and then transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH AM RLC. The SS transmits UE CAPABILITY
ENQUIRY message to confirm whether the UE correctly reconfigure the DL DPCH The UE shall respond with UE
CAPABILITY INFORMATION message.
Expected sequence
UE SS
CELL_DCH state of cell 1. .
2 PHYSICAL CHANNEL
RECONFIGURATION
Including IE " DL channelisation
code " set to New DL
channelisation code
3 PHYSICAL CHANNEL

4 UE CAPABILITY ENQUIRY The SS transmits this message
to confirm whether the UE can
correctly reconfigure the DL
DPCH.
CONFIRM

- Downlink information for each radio link
- Spreading factor Same value as a RADIO BEARER SETUP message
used in initial procedure.
- Code number Different value as a RADIO BEARER SETUP message
used in initial procedure

After step 4 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
931
CELL_DCH (Compressed mode initiation): Success

If the UE receives:
it shall:
1>set the variable ORDERED_RECONFIGURATION to TRUE;
procedure:

UE shall:
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
1. To confirm that the UE activates compressed mode according to a PHYSICAL CHANNEL
uplink DCCH using AM RLC after compressed mode is activated.
3. To confirm that the UE deactivates compressed mode according to a PHYSICAL CHANNEL
uplink DCCH using AM RLC after compressed mode is deactivated..

Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
932
Test Procedure
Table 8.2.6.29
T0 T1 T2 T3 T0 T1 T2 T3
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/3
.84MH
z
-60 -60 -60 -60
Off
-60 -90 -60

SS switches the power settings from columns "T0" to "T1"or "T1" to "T2" or "T2" to "T3", whenever the description in
multi-cell condition specifies the transmission power settings for cell 1 and cell 6.
columns "T0" in table 8.2.6.29. The SS transmits MEASUREMENT CONTROL message in order for the UE to
perform Inter-frequency measurements and report event 2c. The SS switches its downlink transmission power setting
according to columns "T1" in table 8.2.6.29, but the UE shall not transmit any MEASUREMENT REPORT messages.
The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message, which includes IE "DPCH compressed
mode info" with "TGPS Status Flag" set to "Activate". The UE shall transmit PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC. The UE shall transmit
MEASUREMENT REPORT message to report event 2c with the measured CPICH RSCP value for cell 6 to the SS.
The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message, which includes IE"DPCH compressed
mode info" with "TGPS Status Flag" set to "deactivate". The UE shall respond with the PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC. After the SS switches its downlink
transmission power settings to columns "T2" in table 8.2.6.29 and 10s is passed, the SS switches its downlink
transmission power settings to columns "T3" in table 8.2.6.29. The UE shall not send any MEASUREMENT REPORT
messages on the uplink DCCH because the UE cannot measure the CPICH RSCP on non used frequency as the
compressed mode operation has been deactivated.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
933
Expected sequence
UE SS
"T0" in table 8.2.6.29.
2 MEASUREMENT CONTROL SS commands the UE to perform
Inter-frequency measurements
and to report event 2c.
4 The SS checks that no
MEASUREMENT REPORT
messages receives for 10 s.
5 PHYSICAL CHANNEL
RECONFIGURATION
Including IE"DPCH compressed
mode info", which include
parameter "TGPS Status Flag"
set to activate.
6 PHYSICAL CHANNEL

7 MEASUREMENT REPORT The UE shall report event 2c
with the measured CPICH RSCP
value for cell 6.
8 PHYSICAL CHANNEL
RECONFIGURATION
Including IE"DPCH compressed
mode info", which include
parameter "TGPS Status Flag"
set to deactivate.
9 PHYSICAL CHANNEL

11 After 10 s is passed ,the SS
switches its downlink
12 The SS checks that no
MEASUREMENT REPORT
messages receives for 10 s..

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
934
Use the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions in the IE(s) concerned:
Measurement Reporting Mode
- Measurement Reporting Transfer Mode Acknowledged Mode RLC
- Periodic Reporting / Event Trigger Reporting Mode Event Trigger
Additional measurements list Not Present
CHOICE measurement type Inter-frequency measurement
- Inter-frequency measurement object list
- CHOICE inter-frequency cell removal No inter-frequency cells removed
- New inter-frequency cells
- Inter-frequency cell id 6
- Frequency info
- UARFCN uplink (Nu) UARFCN of the uplink frequency for cell 6
- UARFCN downlink (Nd) UARFCN of the downlink frequency for cell 6
- Cell info
- Reference time difference to cell 0 chips
- CHOICE Mode FDD
- Primary CPICH TX power
- TX Diversity Indicator Not Present
- Cell for measurement Not Present

- Inter-frequency measurement quantity
- CHOICE reporting criteria Inter-frequency reporting criteria
- CHOICE Mode FDD
- Measurement quantity for frequency quality
estimate
CPICH RSCP
- Inter-frequency reporting quantity
- UTRA Carrier RSSI FALSE
- Frequency quality estimate FALSE
- Non frequency related cell reporting quantities
indicator
FALSE
- Cell Identity reporting indicator TRUE
- COICE Mode FDD
- UE state CELL_DCH
- Inter-frequency set update On with no reporting
- CHOICE report criteria Inter-frequency measurement reporting criteria
- Inter-frequency event identity 2c
- Threshold used frequency Not present
- W used frequency Not present
- Hysteresis 1.0 dB
- Time to trigger 10 [ms]
- Reporting cell status
- CHOICH reported cell Report cells within monitored and/or virtual active set on
non-used frequency
- Maximum number of reported cells per
reported non-used frequency
1
- Parameters required for each non-used
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
935
frequency
- Threshold non used frequency -68dbm
- W non-used frequency 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
936
- Timing Indication Maintain
- CFN-target SFN frame offset Not Present
- Downlink DPCH power control information
- CHOICE Mode FDD
-DPC Mode 0 (Single)
- CHOICE Mode FDD
- Power offset Pilot-DPDCH 0
- DL rate matching restriction information Not Present
- Fixed or flexible position Flexible
- TFCI existence FALSE
- Number of bits for Pilot bits (SF=128, 256) Not Present
- CHOICE mode FDD
- DPCH compressed mode info
- TGPSI 1
- TGPS Status Flag activate
- TGCFN (Current CFN+(256 TTI/10msec)) mod256
- Transmission gap pattern sequence configuration
parameters

- TGMP FDD Measurement
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD Undefined
- TGPL1 3
- TGPL2 Not Present
- RPP mode 0
- ITP mode 0
- CHOICE UL/DL Mode UL and DL, UL only, or DL only, depending on UE
capability
- Downlink compressed mode method SF/2 or Not present depending on UE capability
- Uplink compressed mode method SF/2 or Not present depending on UE capability
- Downlink frame type B
- DeltaSIR1 2.0
- DeltaSIRAfter1 1.0
- DeltaSIR2 Not Present
- DeltaSIRAfter2 Not Present
- N identify abort Not Present
- T Reconfirm abort Not Present
- TX Diversity Mode Not Present
- SSDT information Not Present
- Default DPCH Offset Value Not Present

The contents of MEASUREMENT REPORT message is the same as them found in [9] TS 34.108 clause 9, with the
Measurement Identity Check to see if set to 15
Measured Results
- CHOICE Measurement
- Inter frequency measured results list Check to see if set to "Inter-frequency measured results
list"
- Inter frequency measurement results
- Frequency info
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
937
- CHOICE FDD
- UARFCN uplink (Nu) Check to see if set to the UARFCN of the uplink
frequency for cell 6
- UARFCN downlink (Nd) Check to see if set to the UARFCN of the downlink
- UTRA carrier RSSI Not checked
- Inter frequency cell measurement results
- Cell Identity Not checked
- Cell synchronisation information Not checked
- CHOICE Mode FDD
- Primary CPICH Info Not checked
- CPICH Ec/No Not checked
- CPICH RSCP Check to see if it is present
- Pathloss Not checked
Measured Results on RACH Not checked
Additional Measured results Not checked
- Measured Result
Event results Not checked

- Downlink DPCH info common for all RL Not present
- TGPSI 1
- TGPS Status Flag deactivate
- TGCFN Not present
parameters
Not present

After step 3 the UE shall not send any MEASUREMENT REPORT messages on the uplink DCCH.
After step 6 the UE shall transmit a MEASUREMENT REPORT message containing the IE "measured results"
reporting cell 6's CPICH RSCP value, also report the triggering of event '2c' included in IE "Event results".
After 11 the UE shall not transmit any MEASUREMENT REPORT messages on the uplink DCCH.

CELL_DCH (Modify active set cell): Success

If the UE receives:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
938
- a PHYSICAL CHANNEL RECONFIGURATION message:
it shall:
procedure:
2>perform the physical layer synchronisation procedure as specified in TS25.214;
1>act upon all received information elements as specified in TS25.331 subclause 8.6, unless specified in the following
and perform the actions below.
UE shall:
configuration.
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
To confirm that the UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink
DCCH using AM RLC on a dedicated physical channel of same frequency in another cell.
Initial Condition
Test Procedure
Table 8.2.6.30
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -60 Off -60

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
939
transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE, which includes IE "Primary CPICH
info" set to Primary Scrambling Code assigned to P-CPICH of cell 2 and IE "Timing indicator" set to "initialise".. The
UE shall reconfigure the physical channel parameters according to PHYSICAL CHANNEL RECONFIGURATION
message and initiate to synchronise with new dedicated physical channel in cell 2. The UE shall then transmit a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in cell 2 on the uplink DCCH AM RLC after
synchronization.
Expected sequence
UE SS
"T0" in table 8.2.6.30.
3 PHYSICAL CHANNEL
RECONFIGURATION
Including IE "Primary CPICH
Code assigned to P-CPICH of
cell 2 and IE "Timing indicator"
which is set to 'initialise'.
4 The UE remains in CELL_DCH
state after connecting to the SS
on a dedicated physical channel
in cell 2.
5 PHYSICAL CHANNEL
in cell 2.

- Timing Indicator initialise

uplink DCCH using AM RLC in cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
940

8.2.6.31 Physical channel reconfiguration transition from CELL_FACH to URA_PCH:
Success

If the UE receives:
it shall:
shall:
response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
941
Reference
3GPP TS 25.331 clause 8.2.2, 8.3, 8.5 and 8.6.
1. To confirm that the UE transmits the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on
2. To confirm that the UE transits from CELL_FACH to URA_PCH according to the PHYSICAL CHANNEL
Initial Condition
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION
message. The UE shall enter URA_PCH state according to this message after it transmits a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for
generic procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
UE SS
of cell 1.
2 PHYSICAL CHANNEL
RECONFIGURATION

3 PHYSICAL CHANNEL
5 If the test result of C.5 indicates


NOTE: It is to be noted that IE "URA identity" is not included in this message, for the purpose of wider test
coverage. The scenario in which IE "URA identity" is included, is tested in other test cases.
DCCH using AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
942
After step 4 the UE shall be in URA PCH state.

8.2.6.32 Physical channel reconfiguration for transition from CELL_DCH to URA_PCH

If the UE receives:
it shall:
shall:
response message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
943
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on
2. To confirm that the UE transits from CELL_DCH to URA_PCH according to the PHYSICAL CHANNEL
3. To confirm that the UE releases the dedicated physical channel and selects a common physical channel in a
different frequency.
Initial Condition
Test Procedure
Table 8.2.6.32
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

transmission power settings to columns "T1" and transmits a PHYSICAL CHANNEL RECONFIGURATION message
with IE "Frequency info" omitted. The UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message using AM RLC and enter URA_PCH state of cell 6. Upon completion of the procedure, the SS
calls for generic procedure C.5 to check that UE is in URA_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
944
Expected sequence
UE SS
"T0" in table 8.2.6.32. SS
outgoing call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 PHYSICAL CHANNEL
RECONFIGURATION
Not including IE "Frequency info"
7 PHYSICAL CHANNEL
UE transmit this message on the
cell 1

Frequency info Not present


CELL_DCH (Frequency band modification): Success

If the UE receives:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
945
it shall:
1>perform the physical layer synchronisation procedure as specified in TS25.214;
The UE shall then:
1>clear the C_RNTI.
shall:
1>transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_DCH according to the PHYSICAL CHANNEL
uplink DCCH using AM RLC on a dedicated physical channel in a different frequency.
Initial Condition
UE: PS_DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.2.6.33
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

transmits a PHYSICAL CHANNEL RECONFIGURATION message including IE "Frequency info" set to frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
946
information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 6. The
UE shall select cell 6 and change its physical channel configuration after receiving this message and then enter
CELL_DCH state. Finally the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message using AM RLC. Upon completion of the procedure, the SS calls for generic procedure C.3 to check that UE is
in CELL_DCH state.
Expected sequence
UE SS
1 The UE is in CELL_FACH state of
in table 8.2.6.33.
3 PHYSICAL CHANNEL
RECONFIGURATION
assigned to P-CPICH of cell 6
4 PHYSICAL CHANNEL
RECONFIGURATION
COMPLETE
6.
5 If the test result of C.3 indicates

The contents of PHYSICAL CHANNEL RECONFIGURATION message in this test case is identical the message sub-
type indicated by "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following
exception:
Frequency info


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
947
8.2.6.34 Physical channel reconfiguration from CELL_FACH to CELL_PCH

If the UE receives:
it shall:
shall:
response message:
Reference
3GPP TS 25.331 clause 8.2.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
948
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the PHYSICAL CHANNEL
Initial Condition
mode on CS/PS".
Test Procedure
Table 8.2.6.34
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

The UE is idle mode of cell 1 and the SS has configured its downlink transmission power setting according to columns
"T0" in table 8.2.6.34. SS requests operator to make an outgoing call. The SS and UE execute procedure P6. Next The
SS and the UE execute procedure P10 and then execute procedure P14. The SS switches its downlink transmission
power settings to columns "T1" and. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message not
including IE "Frequency info" and IE "Primary CPICH info". The UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC and enter CELL_PCH state in cell 6. Upon completion
of the procedure, the SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
949
Expected sequence
UE SS
"T0" in table 8.2.6.34. SS
outgoing call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 PHYSICAL CHANNEL
RECONFIGURATION
7 PHYSICAL CHANNEL
in cell 1.



URA_PCH (Frequency band modification): Success

If the UE receives:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
950
it shall:
shall:
response message:
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
2. To confirm that the UE transits from CELL_FACH to URA_PCH according to the PHYSICAL CHANNEL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
951
Initial Condition
System Simulator: 2 cellsCell 1 in active and cell 6 is inactive
UE: Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN
mode on CS/PS".
Test Procedure
Table 8.2.6.35
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

columns "T0" in table 8.2.6.35. SS requests operator to make an outgoing call. The SS switches its downlink
transmission power settings to columns "T1" and transmits a PHYSICAL CHANNEL RECONFIGURATION message
not including IE "Frequency info" and IE "Primary CPICH info". The UE shall transmit PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message using AM RLC and enter URA_PCH state of cell 6. Upon completion of
the procedure, the SS calls for generic procedure C.5 to check that UE is in URA_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
952
Expected sequence
UE SS
"T0" in table 8.2.6.35. SS
outgoing call.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 PHYSICAL CHANNEL
RECONFIGURATION
7 PHYSICAL CHANNEL
in cell 1.



If the UE receives:
it shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
953
the UE shall:
2>if the received reconfiguration message included the IE "Primary CPICH info", and the UE selected another
cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH
info":
4>proceed as below.
shall:
DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
1. To confirm that the UE transits from CELL_FACH to CELL_FACH according to the PHYSICAL CHANNEL
uplink DCCH using AM RLC on a common physical channel in a different frequency.
Initial Condition
mode on CS/PS".
Test Procedure
Table 8.2.6.36
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-55 -72

Off -55

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
954
to columns "T0" in table 8.2.6.36. The SS modifies the contents of System formation block 11 in cell 1, so that include
IE "Inter frequency measurement system information" about cell 6. The SS and UE execute procedure P6. Next The SS
and the UE execute procedure P10 and then execute procedure P14. The SS switches its downlink transmission power
settings to columns "T1" and transmits a PHYSICAL CHANNEL RECONFIGURATION message including IE
"Frequency info" set to frequency information of cell 6 and no IE "Primary CPICH info". The UE selects cell 6 and
initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection". The UE transmits a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message using AM RLC after complete configuration
according to receiving PHYSICAL CHANNEL RECONFIGURATION message. Upon completion of the procedure,
the SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
UE SS
camped onto cell 1. The System
Information Block type 11
messages to be transmitted are
different from the default settings
and the SS has configured its
in table 8.2.6.36.
7.4.2.2.2) specified in TS 34.108.

7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

6 PHYSICAL CHANNEL
RECONFIGURATION
set to Primary Scrambling Code
CONFIRM

10 PHYSICAL CHANNEL
6.

The contents PHYSICAL CHANNEL RECONFIGURATION message in this test case is identical the message sub-
type indicated by "Packet to CELL_FACH from CELL_FACH in PS" in Annex A, with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
955
Frequency info


New C-RNTI 0000 0000 0000 0001B

The contents of UTRAN MOBILITY UPDATE CONFIRM message is identical as "UTRAN MOBILITY UPDATE
AM RLC in cell 6.
CELL_DCH (Hard handover to another frequency with timing re-initialised)

The UE shall:
1>be able to receive any of the following messages:

2>PHYSICAL CHANNEL RECONFIGURATION message;
1>perform a hard handover and apply physical layer synchronisation procedure A as specified in [29], even if no
prior UE measurements have been performed on the target cell and/or frequency.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
956
shall:
DCCH using AM RLC.

When performing hard handover with change of frequency, the UE shall:
1>stop all intra-frequency and inter-frequency measurement reporting on the cells listed in the variable
CELL_INFO_LIST. Each stopped measurement is restarted when a MEASUREMENT CONTROL message is
received with the corresponding measurement identity.

When the UE is in CELL_DCH state and receives any of the messages causing the UE to perform a hard handover, the
UE shall check the IE "Timing indication" in that message and:
1>if IE "Timing indication" has the value "initialise" (i.e. timing re-initialised hard handover):
2>read SFN on target cell identified by the first radio link listed in the IE "Downlink information per radio link
list" included in that message;
2>set the CFN according to the following formula:
3>for FDD:
CFN =(SFN - (DOFF div 38400)) mod 256
where the formula gives the CFN of the downlink DPCH frame which starts at the same time as or
which starts during the PCCPCH frame with the given SFN.

If the IE "DPCH compressed mode info" is included, and if the IE group "transmission gap pattern sequence
configuration parameters" is not included, the UE shall:
1>if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag" in
the variable TGPS_IDENTITY):
2>if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence:
3>deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time" (see
subclause 8.6.3.1 in TS 25.331) received in this message, when the new configuration received in this
message is taken into use;

If the IE "Downlink DPCH info common for all RL" is included in a message used to perform a Timing re-initialised
hard handover or the IE "Downlink DPCH info common for all RL" is included in a message other than RB SETUP
used to transfer the UE from a state different from Cell_DCH to Cell_DCH, and ciphering is active for any radio bearer
using RLC-TM, the UE shall, after having activated the dedicated physical channels indicated by that IE:
1>if any ciphering configuration for a radio bearer using RLC-TM has not been applied, due to that the activation time
from a previous procedure has not elapsed:
2>apply the ciphering configuration immediately and consider the activation time from the previous procedure
to be elapsed.
1>if the IE "MAC-d HFN initial value" is included in the IE "Downlink DPCH info common for all RL":

1>else:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
957
2>set the 20 MSB of the HFN component of COUNT-C for TM-RLC to the value of the latest transmitted IE
"START" or "START List" for this CN domain, while not incrementing the value of the HFN component of
COUNT-C at each CFN cycle; and
1>set the remaining LSBs of the HFN component of COUNT-C to zero;
1>start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN;
1>include the IE "COUNT-C activation time" in the response message and specify a CFN value other than the
default, "Now", that is a multiple of 8 frames (CFN mod 8 =0) and lies at least 200 frames ahead of the CFN in
which the response message is first transmitted;
1>calculate the START value according to subclause 8.5.9 in TS 25.331;
synchronisation info" in the response message;
1>at the CFN value as indicated in the response message in the IE "COUNT-C activation time":
2>set the 20 MSB of the HFN component of the COUNT-C variable common for all transparent mode radio
bearers of this CN domain to the START value as indicated in the IE "START list" of the response message
for the relevant CN domain; and
2>increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is
equal to zero;
2>set the CFN component of the COUNT-C to the value of the IE "COUNT-C activation time" of the response
message. The HFN component and the CFN component completely initialise the COUNT-C variable;
2>step the COUNT-C variable, as normal, at each CFN value, i.e. the HFN component is no longer fixed in
value but incremented at each CFN cycle.
Reference
3GPP TS 25.331 clauses 8.2.2.3, 8.2.2.4, 8.3.5, 8.5.15.2, 8.6.6.15, 8.6.6.28
To confirm that the UE is able to perform a hard-handover with change of frequency, with and without prior
measurements on the target frequency.
To confirm that the UE answers with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message when
the procedure has been initiated with the PHYSICAL CHANNEL RECONFIGURATION message.
To confirm that the UE stops intra-frequency measurements after the inter-frequency handover has been performed,
until a MEASUREMENT CONTROL message is received from the SS.
To confirm that the UE computes as it shall the CFN to be used after the handover.
To confirm that the UE deactivates compressed mode (if required) when it has been ordered to do so in the PHYSICAL
To confirm that the UE includes the IE "COUNT-C activation time" and the IE "START list" (in the IE "Uplink counter
synchronisation info") in the response message if ciphering is active for any radio bearer using RLC-TM.
Initial Condition
System Simulator: 5 cells Cell 1 and cell 2 on frequency f
1
, cell 4 and cell 5 on frequency f
2
, and cell 6 on frequency
f
3
. Cells 2 and 5 shall have the same primary scrambling code.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
958
UE: "CS-DCCH+DTCH_DCH" (state 6-9) or "PS-DCCH+DTCH_DCH" (state 6-10) as specified in clause 7.4 of TS
34.108, depending on the CN domain supported by the UE. If the UE supports both CS and PS domains, the test case
shall be run twice, once starting from state 6-9, once starting from state 6-10. Ciphering shall be activated.
- Compressed mode required yes/no
Test Procedure
Table 8.2.6.37-1 illustrates the downlink power to be applied for the 5 cells, as well as the frequency and scrambling
code for each cell.
Table 8.2.6.37-1
Parameter Unit Cell 1 Cell 2 Cell 4 Cell 5 Cell 6
Frequency f1 f1 f2 f2 f3
Scrambling code Scrambling code
1
Scrambling
code 2
Scrambling
code 3
Scrambling code
2
Scrambling
code 4

T0 T1 T2 T0 T1 T2 T0 T1 T2 T0 T1 T2 T0 T1 T2
CPICH Ec dBm/3.8
4 MHz
-60 -60 -75 -95 -
60
-
75
-
60
-
60
-
60
-60 -60 -
70
-50 -
50
-50

The UE is initially in CELL_DCH, and has only cell 1 in its active set.
At instant T1, the downlink power is changed according to what is shown in table 8.2.6.37 -1. Cell 2 should then trigger
event 1a as has been configured through the default System Information Block Type 11. The UE shall thus send a
MEASUREMENT REPORT to the SS, triggered by cell 2.
The SS adds then cell 2 to the active set of the Ue, by sending an ACTIVE SET UPDATE message to the UE. The UE
shall answer with an ACTIVE SET UPDATE COMPLETE message.
The SS configures then compressed mode (if required), to prepare the UE for inter-frequency measurements, by sending
a PHYSICAL CHANNEL RECONFIGURATION message on DCCH using AM-RLC. The UE shall answer with a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
The SS then sets up inter-frequency measurements (event 2b), by sending a MEASUREMENT CONTROL message to
the UE. Compressed mode is started at the same time in that message (if required).
At instant T2, the downlink power is changed according to what is shown in table 8.2.6.37-1. Frequency f
2
shall then
trigger event 2b, and the UE shall transmit a MEASUREMENT REPORT message to the SS.
SS then transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE on DCCH using AM-RLC, to
order it to perform timing reinitialised inter-frequency handover to cell 4 on frequency f
2
. The UE is also ordered to stop
compressed mode (if required) after the handover.
The UE shall then transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS when
the inter-frequency handover has succeeded. In case the initial condition was CS-DCCH+DTCH_DCH, that message
shall contain the IEs "COUNT-C activation time" and the IE "START list" (in the IE "Uplink counter synchronisation
info"), indicating to the SS when and from which value to start incrementing the HFN part of the COUNT-C variable
used for ciphering. The SS shall restart incrementing the HFN part of the COUNT-C variable from the value specified
in the IE START from the CFN indicated in the IE COUNT-C activation time.
The SS then waits for 20 seconds, and checks that no MEASUREMENT REPORT is received from the UE.
The SS sends then a MEASUREMENT CONTROL message to the UE, to modify the intra-frequency cell info list of
the UE. About 640 ms after, a MEASUREMENT REPORT message shall be received from the UE, triggered by cell 5.
Subsequent MEASUREMENT REPORT messages shall be received at 4 seconds interval.
Only if the UE requires compressed mode for performing interfrequency measurements, the SS sends a
MEASUREMENT CONTROL message to the UE that sets up inter-frequency measurements, but does not activate
compressed mode in that message. It waits then for 20 seconds, and checks that no MEASUREMENT REPORT
message triggered by cell 6 is received.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
959
Independent of the UE requiring compressed mode, the SS then continues by sending a PHYSICAL CHANNEL
RECONFIGURATION message to the UE on DCCH using AM-RLC, to order it to perform timing reinitialised inter-
frequency handover to cell 6 on frequency f
3
.
used for ciphering.
Expected Sequence
UE SS
1 The SS changes the power of
the cells according to column
T1 in table 8.2.6.37-1
2 MEASUREMENT REPORT Event 1a is triggered by cell 2
in the UE, which sends a
MEASUREMENT REPORT
message to the SS
3 ACTIVE SET UPDATE The SS adds cell 2 to the
active set of the UE.
4 ACTIVE SET UPDATE COMPLETE The UE answers with an
ACTIVE SET UPDATE
COMPLETE message to the
SS
5 PHYSICAL CHANNEL
RECONFIGURATION
The SS downloads the
compressed mode parameters
in the UE (if required).
6 PHYSICAL CHANNEL
The UE acknowleges the
downloading of the
(only if compressed mode was
configured).
7 MEASUREMENT CONTROL The SS configures inter-
frequency measurements in
the UE, and activates
compressed mode (if
required).
8 The SS changes the power
of the cells according to
column T2 in table
8.2.6.37-1.
9 MEASUREMENT REPORT Frequency f2 triggers event 2b
MEASUREMENT REPORT
message to the SS.
10 PHYSICAL CHANNEL
RECONFIGURATION
The SS orders the UE to
perform timing re-initialised
inter-frequency handover to
cell 4 on frequency f2.
11 PHYSICAL CHANNEL
After the UE has succeeded in
performing the inter-frequency
handover, it shall send a
PHYSICAL CHANNEL
RECONFIGURATION
SS using the new
configuration.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
960
12 The SS waits for 20 seconds
and monitors that no
MEASUREMENT REPORT
message is received from the
UE.
13 MEASUREMENT CONTROL The SS updates the list of
intra-frequency cells in the UE.
14 MEASUREMENT REPORT Cell 5 triggers event 1a in the
UE, which sends a
MEASUREMENT REPORT
message to the SS.
Subsequent MEASUREMENT
REPORT messages shall be
received from the UE at 4
seconds interval.
15 MEASUREMENT CONTROL The SS sets up an inter-
frequency measurement in the
UE (if compressed mode is
required), but does not
activate compressed mode.
MEASUREMENT REPORT
UE.
17 PHYSICAL CHANNEL
RECONFIGURATION
18 PHYSICAL CHANNEL
PHYSICAL CHANNEL
RECONFIGURATION
SS using the new
configuration.

All messages indicated below shall use the same content as described in default message content, with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
961
Message Type
Measured Results
- Cell Identity Check that this IE is absent
- SFN-SFN observed time difference Check that this IE is absent
- Cell synchronisation information Check that this IE is absent
- Primary scrambling code Scrambling code 1 (or scrambling code 2)
- CPICH Ec/N0 Check that this IE is absent
- CPICH RSCP Check that this IE is present
- Pathloss Check that this IE is absent
- Cell synchronisation information Check that this IE is present and includes IE COUNT-C-
SFN frame difference (This IE is related to scrambling
code 2)
- Primary scrambling code Scrambling code 2 (or scrambling code 1 if the previous
scrambling code included by the UE was scrambling code
2)
Measured results on RACH Check that this IE is absent
Additional measured results Check that this IE is absent
Event results
- Primary scrambling code Scrambling code 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
962
- Primary Scrambling Code Scrambling code 2
- Downlink DPCH info for each RL Reference to TS34.108 clause 6.10
Parameter Set
- CHOICE mode FDD
- DPCH frame offset Calculated value from Cell synchronisation
information
- Secondary scrambling code Not Present
- Spreading factor Refer to TS 34.108 clause 6.10.2.4 "Typical
radio parameter sets"
- Code Number Any value between 0 and Spreading factor-1
(use different values for each DPCH in case
several DPCHs are allocated to the UE).
- TFCI Combining Indicator FALSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
963
PHYSICAL CHANNEL RECONFIGURATION (Step 5 for the CS case)
Activation time Not Present
New DSCH-RNTI Not Present
Downlink counter synchronisation info Not Present
CHOICE mode FDD
- Downlink DPCH info common for all RL Not Present
- TGPSI 1
- TGPS Status Flag Deactivate
- TGCFN Not present
- Transmission gap pattern sequence
configuration parameters

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL Mode UL and DL, UL only or DL only (depending on
the UE capability)
- Downlink compressed mode method SF/2 (or not sent, depending on the UE
capability)
- Uplink compressed mode method SF/2 (or not sent, depending on the UE
capability)
- DeltaSIR1 2.0
- TX Diversity mode Not Present
Downlink information per radio link list 2 radio links
- CHOICE mode FDD
- Primary CPICH info Scrambling code 1
- Cell ID Not present
- PDSCH with SHO DCH info Not present
- PDSCH code mapping Not present
- CHOICE mode FDD
- Primary CPICH usage for channel
estimation
Primary CPICH may be used
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
964
- Spreading factor Reference to TS34.108 clause 6.10
Parameter Set
- Code number Same as the code currently allocated to the
UE in cell 1
- Scrambling code change Code change
- Closed loop timing adjustment mode Not present
- CHOICE mode FDD
- CHOICE mode FDD
estimation
Parameter Set
UE in cell 2
- Scrambling code change No code change

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
965
PHYSICAL CHANNEL RECONFIGURATION MESSAGE (Step 5 for the PS case)
CHOICE mode FDD
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)
- Downlink compressed mode method HLS(or not sent, depending on the UE
capability)
- Uplink compressed mode method HLS(or not sent, depending on the UE
capability)
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
966
Mode
Event Trigger
- New inter-frequency info list 2 inter-frequency cells
- Frequency info
- UARFCN uplink (Nu) UARFCN for the uplink corresponding to f2
- UARFCN downlink (Nd) UARFCN for the downlink corresponding to f2
- Cell info
- CHOICE Mode FDD
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
No report
indicator
FALSE
- UE State CELL_DCH
- Inter-frequency set update
- UE autonomous update On with no reporting
- Non autonomous update mode Not present
- Inter-frequency event identity 2b
- Threshold used frequency -70 dBm
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
967
- W used frequency 0.0
- Hysteresis 1.0 dB
- Reporting cell status Report cells within monitored and/or virtual
active set on non-used frequency
2
frequency

- Threshold non used frequency -65 dBm
DPCH compressed mode status info
- TGPS reconfiguration CFN (Current CFN +(256 TTI/10msec))mod 256
- TGPSI 1
- TGPS Status Flag Activate
- TGCFN (Current CFN +(256 TTI/10msec))mod 256

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
968
Message Type
Measured Results
- Inter-frequency measured results list
- Frequency info
-CHOICE mode FDD
- UARFCN uplink Check that the value of this IE is set to UARFCN for the
uplink corresponding to f2 (Could be absent in case the
duplex distance is the default duplex distance)
- UARFCN downlink Check that the value of this IE is set to UARFCN for the
downlink corresponding to f2
- UTRA carrier RSSI Check that this IE is absent
- Inter-frequency cell measurement results Check that the value of this IE is set to 2 cells reported
- Primary scrambling code Check that the value of this IE is set to Scrambling code 3
(or scrambling code 2)
(or scrambling code 3 if the previous scrambling code
included by the UE was scrambling code 2)
Event results
- Inter-frequency measurement event results
- Inter-frequency cells
- Frequency info
-CHOICE mode FDD
- Non freq related measurement event results

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
969
Frequency info
- CHOICE mode FDD
CHOICE mode FDD
- Timing indication Initialise
- CFN-targetSFN frame offset 0
- Downlink DPCH power control information Not Present
- Downlink rate matching restriction information Not Present
Parameter Set
- Fixed or flexible position Reference to TS34.108 clause 6.10
Parameter Set
- TFCI existence Reference to TS34.108 clause 6.10
Parameter Set
- CHOICE SF Reference to TS34.108 clause 6.10
Parameter Set
- TGPSI
- TGPS Status Flag
- TGCFN

1
Deactivate
Not present

Not present
- Default DPCH Offset Value Arbitrary value between 0..306688 by step of
512
Downlink information per radio link list 1 radio link
- CHOICE mode FDD
- CHOICE mode FDD
estimation
- DPCH frame offset Set to value of DPCH Frame Offset modulo
38400
- DL channelisation code Reference to TS34.108 clause 6.10
Parameter Set
Parameter Set
- Code number Any value between 0 and Spreading factor-1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
970

PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Steps 11 and 18 for the CS case)
Message Type
RRC transaction identifier Checked to see if it is set to identical value of the same
IE in the downlink PHYSICAL CHANNEL
RECONFIGURATION message
Uplink integrity protection activation info Check that not present
CHOICE mode FDD
COUNT-C activation time Check that this IE is present and that the CFN value is a
multiple of 8 frames (CFN mod 8 =0) and lies at least 200
frames ahead of the CFN in which the response message
is first transmitted.
Radio bearer uplink ciphering activation time info Check that not present
Uplink counter synchronisation info Check that present
>RB with PDCP information list Check that absent
>START list Check that this IE is set to 1
>>CN Domain identity Check that this IE is set to CS Domain
>>START Not checked

PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Steps 11 and 18 for the PS case)
Message Type
CHOICE mode FDD
COUNT-C activation time Check that not present

Uplink counter synchronisation info Check that not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
971
Measurement Command Modify
Measurement Reporting Mode Not present
Additional measurements list Not present
CHOICE measurement type Intra-frequency measurement
- CHOICE intra-frequency cell removal Remove all intra-frequency cells
- New intra-frequency info list 2 new intra-frequency cells
- Cell info
- CHOICE mode FDD
- Primary Scrambling Code Scrambling code 3 (for cell 4)
- Cells selection and Re-selection info Not Present
- Cell info
- Read SFN Indicator TRUE
- CHOICE mode FDD
- Primary Scrambling Code Scrambling code 2 (for cell 5)
- Cells for measurement Not Present
- Intra-frequency measurement quantity Not Present
- Intra-frequency reporting quantity Not Present
- Reporting cell status Not Present
- CHOICE report criteria Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
972
Message Type
Measured Results
- Primary scrambling code Check that this IE is set to Scrambling code 2 (or
scrambling code 3)
SFN frame difference (This IE is related to scrambling
code 2)
- Primary scrambling code Check that this IE is set to Scrambling code 3 (or
scrambling code 2 if scrambling code 3 was indicated
first)
Event results
- Primary scrambling code Check that this IE is set to Scrambling code 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
973
Mode
Event Trigger
- Frequency info
- Cell info
- CHOICE Mode FDD
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
No report
indicator
FALSE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
974
- UE State CELL_DCH
- W used frequency Not present
- Hysteresis 1.0 dB
- CHOICE reported cell Report cells within active and/or monitored set
on used frequency or within virtual active
and/or monitored set on non-used frequency
frequency
1 frequency
- W non-used frequency 0.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
975
Frequency info
- CHOICE mode FDD
- UARFCN uplink (Nu) Not Present
CHOICE mode FDD
Parameter Set
Parameter Set
Parameter Set
Parameter Set
- DPCH compressed mode info Not present
- Default DPCH Offset Value Arbitrary set to value 0..306688 by step of
512
- CHOICE mode FDD
- CHOICE mode FDD
estimation
38400
Parameter Set
Parameter Set

After step 1, the UE shall send a MEASUREMENT REPORT message triggered by event 1a for cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
976
After step 3, the UE shall send an ACTIVE SET UPDATE COMPLETE message to acknowledge that it has added cell
2 to its active set.
After step 5, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS
to acknowledge the downloading of the compressed mode parameters (only if compressed mode is required),that were
sent in the PHYSICAL CHANNEL RECONFIGURATION message of step 4.
After step 8, the UE shall transmit a MEASUREMENT REPORT message triggered by frequency f
2
. In that message,
cell 4 shall be the only cell included in the IE event results.
After step 10, the UE shall send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS in
cell 4 to acknowledge the successful timing re-initialised inter-frequency handover, and in case the UE was in state 6-9
as defined in clause 7.4 of 34.108 as initial condition to the test, the IEs "COUNT-C activation time" and "START list"
(in the IE "Uplink counter synchronisation info") shall be included in that message. The UE shall also start
incrementing the HFN part of the COUNT-C variable from the value specified in the IE START from the CFN
indicated in the IE COUNT-C activation time.
After step 11, the UE shall not send any MEASUREMENT REPORT message triggered by event 1a for cell 5.
After step 13, the UE send a MEASUREMENT REPORT message triggered by event 1a for cell 5.
For UE's that require compressed mode for performing interfrequency measurements, after step 15 the UE shall not
send any MEASUREMENT REPORT message triggered by event 2c for frequency 1.
(in the IE "Uplink counter synchronisation info") shall be included in that message.
8.2.6.37a Physical channel reconfiguration for transition from CELL_DCH to
CELL_DCH (Hard handover to another frequency with timing re-initialised)
(1.28 Mcps TDD)

In case the reconfiguration procedure is used to remove all existing RL(s) in the active set while new RL(s) are
established the UE shall:
1>perform the physical layer synchronisation procedure A as specified in TS 25.214
1>apply the hard handover procedure as specified (below);
1>be able to perform this procedure even if no prior UE measurements have been performed on the target cell
and/or frequency.

shall:
DCCH using AM RLC.

When performing hard handover with change of frequency, the UE shall:
1>stop all intra-frequency and inter-frequency measurements on the cells listed in the variable CELL_INFO_LIST.
Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the
corresponding measurement identity.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
977

When the UE is in CELL_DCH state and receives any of the messages causing the UE to perform a hard handover, the
UE shall check the IE "Timing indication" in that message and:
1>if IE "Timing indication" has the value "initialise" (i.e. timing re-initialised hard handover):
2> read SFN on target cell identified by the first radio link listed in the IE "Downlink information per radio link
list" included in that message;
2>set the CFN according to the following formula:
3>for TDD:
CFN =(SFN - DOFF) mod 256
where the formula gives the CFN of the downlink DPCH frame which starts at the same time as or
which starts during the PCCPCH frame with the given SFN.

If the IE "Downlink DPCH info common for all RL" is included in a message used to perform a Timing re-initialised
hard handover or the IE "Downlink DPCH info common for all RL" is included in a message other than RB SETUP
used to transfer the UE from a state different from Cell_DCH to Cell_DCH, and ciphering is active for any radio bearer
using RLC-TM, the UE shall, after having activated the dedicated physical channels indicated by that IE:
1>set the 20 MSB of the HFN component of COUNT-C for TM-RLC to the value of the latest transmitted IE
"START" or "START List" for this CN domain, while not incrementing the value of the HFN component of
COUNT-C at each CFN cycle; and
1>start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN;
1>include the IE "COUNT-C activation time" in the response message and specify a CFN value other than the
default, "Now" for this IE;
synchronisation info" in the response message;
1>at the CFN value as indicated in the response message in the IE "COUNT-C activation time":
2>set the 20 MSB of the HFN component of the COUNT-C variable to the START value as indicated in the IE
"START list" of the response message for the relevant CN domain; and
2>increment the HFN component of the COUNT-C variable by one;
2>set the CFN component of the COUNT-C to the value of the IE "COUNT-C activation time" of the response
message. The HFN component and the CFN component completely initialise the COUNT-C variable;
2>step the COUNT-C variable, as normal, at each CFN value, i.e. the HFN component is no longer fixed in
value but incremented at each CFN cycle.
Reference
3GPP TS 25.331 clauses 8.2.2.3, 8.2.2.4, 8.3.5, 8.5.15.2, 8.6.6.15, 8.6.6.28
8.2.6.37a.3 Test Purpose
To confirm that the UE is able to perform a hard-handover with change of frequency, with and without prior
measurements on the target frequency.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
978
To confirm that the UE answers with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message when
the procedure has been initiated with the PHYSICAL CHANNEL RECONFIGURATION message.
To confirm that the UE stops intra-frequency measurements after the inter-frequency handover has been performed,
until a MEASUREMENT CONTROL message is received from the SS.
To confirm that the UE computes as it shall the CFN to be used after the handover.
To confirm that the UE includes the IE "COUNT-C activation time" and the IE "START list" (in the IE "Uplink counter
synchronisation info") in the response message if ciphering is active for any radio bearer using RLC-TM.
Initial Condition
1
, cell 4 and cell 5 on frequency f
2
. Cells 2 and 5 shall have
the same cell parameters id. Only cell 1 is activated.
Test Procedure
Table 8.2.6.37a-1 illustrates the downlink power to be applied for the 4 cells, as well as the frequency and cell
parameters id for each cell.
Table 8.2.6.37a-1
Parameter Unit Cell 1 Cell 2 Cell 4 Cell 5
Frequency f1 f1 f2 f2
Cell parameters id Cell parameters id
1
Cell
parameters id
2
Cell
parameters
id 3
Cell parameters
id 2

T0 T1 T2 T0 T1 T2 T0 T1 T2 T0 T1 T2
P-CCPCH RSCP
(TDD)
dBm
-60 -60 -75 -95
-
55
-
75

-
60
-
60
-
60
-60 -60 -
70

The UE is initially in CELL_DCH in cell 1.
At instant T1, the downlink power is changed according to what is shown in table 8.2.6.37a -1. Cell 2 should then
trigger event 1g as has been configured through the default System Information Block Type 11. The UE shall thus send
a MEASUREMENT REPORT to the SS, triggered by cell 2.
the UE.
At instant T2, the downlink power is changed according to what is shown in table 8.2.6.37a-1. Frequency f
2
shall then
2
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
979
used for ciphering. The SS shall restart incrementing the HFN part of the COUNT-C variable from the value specified
in the IE START from the CFN indicated in the IE COUNT-C activation time.
The SS then waits for 20 seconds, and checks that no MEASUREMENT REPORT is received from the UE.
The SS sends then a MEASUREMENT CONTROL message to the UE, to modify the intra-frequency cell info list of
the UE. About 640 ms after, a MEASUREMENT REPORT message shall be received from the UE, triggered by cell 5.
Subsequent MEASUREMENT REPORT messages shall be received at 4 seconds interval.
In case the initial condition was CS-DCCH+DTCH_DCH, that message shall contain the IEs "COUNT-C activation
time" and the IE "START list" (in the IE "Uplink counter synchronisation info"), indicating to the SS when and from
which value to start incrementing the HFN part of the COUNT-C variable used for ciphering.
Expected Sequence
UE SS
T1 in table 8.2.6.37a-1
2 MEASUREMENT REPORT Event 1g is triggered by cell 2
MEASUREMENT REPORT
message to the SS
the UE.
column T2 in table
8.2.6.37a-1.
MEASUREMENT REPORT
message to the SS.
6 PHYSICAL CHANNEL
RECONFIGURATION
7 PHYSICAL CHANNEL
PHYSICAL CHANNEL
RECONFIGURATION
SS using the new
configuration.
MEASUREMENT REPORT
UE.
9 MEASUREMENT CONTROL The SS updates the list of
intra-frequency cells in the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
980
10 MEASUREMENT REPORT Cell 5 triggers event 1g in the
UE, which sends a
MEASUREMENT REPORT
message to the SS.
Subsequent MEASUREMENT
REPORT messages shall be
received from the UE at 4
seconds interval.

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
981
Message Type
Measured Results
- Cell Identity Check that this IE is present
- Cell parameters ID cell parameters ID 2
- Timeslot ISCP Check that this IE is absent
- P-CCPCH RSCP Check that this IE is present
SFN frame difference
- Cell parameters ID Cell parameters ID 1
Event results
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
982

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
983
Mode
Event Trigger
- Frequency info
- UARFCN (Nt) UARFCN corresponding to f2
- Cell info
- CHOICE Mode TDD
- Frequency info
- Cell info
- CHOICE Mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
984
estimate
P-CCPCH RSCP
indicator
No report
indicator
FALSE
- Timeslot ISCP reporting indicator FALSE
- P-CCPCH RSCP reporting indicator TRUE
- UE State CELL_DCH
- Hysteresis 1.0 dB
2
frequency


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
985
Message Type
Measured Results
- Frequency info
-CHOICE mode TDD
- UARFCN(Nt) Check that the value of this IE is set to UARFCN
corresponding to f2
- Inter-frequency cell measurement results Check that the value of this IE is set to 2 cells reported
- Cell parameters ID Check that the value of this IE is set to Cell parameters ID
3 (or Cell parameters ID 2)
2 (or Cell parameters ID 3 if the previous Cell parameters
ID included by the UE was Cell parameters ID 2)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
986
Event results
- Frequency info
-CHOICE mode TDD
- UARFCN(Nt) Check that the value of this IE is set to UARFCN
corresponding to f2
3

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
987
Frequency info
- CHOICE mode TDD
CHOICE mode TDD
- Downlink HS-PDSCH Information Not Present
- CHOICE mode TDD
- Primary CCPCH info Cell parameters ID 3
- CHOICE mode TDD
- TFCS ID Reference to TS34.108 clause 6.11
Parameter Set
- Time info Reference to TS34.108 clause 6.11
Parameter Set
- Common timeslot info Reference to TS34.108 clause 6.11
Parameter Set
- Downlink DPCH timeslots and codes as used for cell 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
988
PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Steps 7 for the CS case)
Message Type
CHOICE mode TDD
COUNT-C activation time Check that this IE shall be present
Uplink counter synchronisation info Check that present
>RB with PDCP information list Check that absent
>START list Check that this IE is set to 1
>>CN Domain identity Check that this IE is set to CS Domain
>>START Not checked

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
989
PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Steps 7 for the PS case)
Message Type
CHOICE mode TDD
COUNT-C activation time Check that not present

Uplink counter synchronisation info Check that not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
990
Measurement Reporting Mode Not present
- Cell info
- CHOICE mode TDD
- Primary CCPCH Info
- Cell parameters ID Cell parameters ID 3 (for cell 4)
- Primary CCPCH TX power Not Present
- Cell info
- CHOICE mode TDD
- Cell parameters ID Cell parameters ID 2 (for cell 5)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
991
Message Type
Measured Results
- Cell parameters ID Check that this IE is set to Cell parameters ID 2 (or Cell
parameters ID 3)
- Cell parameters ID Check that this IE is set to Cell parameters ID 3 (or Cell
parameters ID 2 if Cell parameters ID 3 was indicated
first)
- Timeslot ISCP Checked that this IE is absent
- P-CCPCH RSCP Checked that this IE is present
Event results
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
992
- Cell parameters ID Check that this IE is set to Cell parameters ID 2

8.2.6.37a.5 Test Requirement
After step 2, the UE shall send a MEASUREMENT REPORT message triggered by event 1g for cell 2.
2
. In that message,
(in the IE "Uplink counter synchronisation info") shall be included in that message. The UE shall also start
incrementing the HFN part of the COUNT-C variable from the value specified in the IE START from the CFN
indicated in the IE COUNT-C activation time.
After step 8, the UE shall not send any MEASUREMENT REPORT message.
After step 9, the UE send a MEASUREMENT REPORT message triggered by event 1g for cell 5.
CELL_DCH (Hard handover to another frequency with timing re-initialised):
Failure (Physical channel failure and reversion to old channel)



as specified below:
2>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
993

The UE shall:

using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
To confirm that the UE reverts to the old configuration (including measurement configurations, ciphering procedures
and compressed mode configurations if required) and transmits a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message on the DCCH using AM RLC if the UE fails to reconfigure the new physical channel according to
the received PHYSICAL CHANNEL RECONFIGURATION message before timer T312 expiry.
Initial Condition
1
, cell 4 on frequency f
2
and cell 5 on frequency f
3
.
Test Procedure
code for each cell.
Table 8.2.6.38-1a
Frequency f1 f1
Scrambling
code
Scrambling code 1 Scrambling code 2

T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
CPICH Ec dBm/3.8
4 MHz
-60 -60 -75 -60 -75 -95 -60 -75 -60 -75

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
994
Table 8.2.6.38-1b
Frequency f2 f3
Scrambling
code

T0 T1 T2 T3 T4 T0 T1 T2 T3 T4
CPICH Ec dBm/3.8
4 MHz

-60

-60

-60
-
122
-70 -60 -60 -70 -
122
-60

At instant T1, the downlink power is changed according to what is shown in table 8.2.6.38 -1. Cell 2 should then trigger
event 1a as has been configured through the default System Information Block Type 11. The UE shall thus send a
MEASUREMENT REPORT to the SS, triggered by cell 2.
The SS adds then cell 2 to the active set of the UE, by sending an ACTIVE SET UPDATE message to the UE. The UE
shall answer with an ACTIVE SET UPDATE COMPLETE message.
The SS then configures compressed mode, (if required by the UE) to prepare the UE for inter-frequency measurements,
by sending a PHYSICAL CHANNEL RECONFIGURATION message on DCCH using AM-RLC. The UE shall
answer with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
the UE. Compressed mode is started at the same time in that message, (if required).
2
shall then
At instance T3, the downlink power is changed according to what is shown in table 8.2.6.38-1.
2
.
The UE shall revert to the old configuration and transmits a PHYSICAL CHANNEL RECONFIGURATION
FAILURE message to the SS on the DCCH using AM RLC, with the value "physical channel failure" in the IE "failure
cause".
3
shall then
Expected Sequence
UE SS
T1 in table 8.2.6.38-1.
2 MEASUREMENT REPORT Event 1a is triggered by cell 2
MEASUREMENT REPORT
message to the SS.
3 ACTIVE SET UPDATE The SS adds cell 2 to the
active set of the UE.
4 ACTIVE SET UPDATE COMPLETE The UE answers with an
ACTIVE SET UPDATE
SS.
5 PHYSICAL CHANNEL
RECONFIGURATION
The SS downloads the
in the UE, (if required).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
995
6 PHYSICAL CHANNEL
The UE acknowledges the
downloading of the
(only if compressed mode was
configured).
the UE, and activates
compressed mode (if
required).
column T2 in table 8.2.6.38-
1.
MEASUREMENT REPORT
message to the SS.
The SS changes the power
column T3 in table 8.2.6.
38-1.
10 PHYSICAL CHANNEL
RECONFIGURATION
11 PHYSICAL CHANNEL
After T312 expires, the UE
shall revert to the old channel
and transmits this message.
1.
MEASUREMENT REPORT
message to the SS.

exceptions:
Message Type
Measured Results
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
996
- Primary scrambling code Scrambling code 1 (or scrambling code 2)
- Primary scrambling code Scrambling code 2 (or scrambling code 1 if the previous
scrambling code included by the UE was scrambling code
2)
Event results
- Primary scrambling code Scrambling code 2

- Downlink DPCH info for each RL Reference to TS34.108 clause 6.10
Parameter Set
- CHOICE mode FDD
information
- Code Number Any value between 0 and Spreading factor-1
(use different values for each DPCH in case
several DPCHs are allocated to the UE).

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
997
CHOICE mode FDD
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)
capability)
capability)
- DeltaSIR1 2.0
Downlink information per radio link list 2 radio links
- CHOICE mode FDD
- CHOICE mode FDD
estimation
Parameter Set
UE in cell 1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
998
- CHOICE mode FDD
- CHOICE mode FDD
estimation
Parameter Set
UE in cell 2

PHYSICAL CHANNEL RECONFIGURATION MESSAGE (Step 5 for the PS case)
CHOICE mode FDD
- TGPSI 1
- TGCFN Not Present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
999
capability)
capability)
- DeltaSIR1 2.0

Mode
Event Trigger
- Frequency info
- Cell info
- CHOICE Mode FDD
- Frequency info
- Cell info
- CHOICE Mode FDD
- Primary CPICH Info Not present
estimate
CPICH RSCP
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1000
indicator
No report
indicator
FALSE
- UE State CELL_DCH
- Hysteresis 1.0 dB
2
frequency

- TGPSI 1

Message Type
Measured Results
- Frequency info
-CHOICE mode FDD
- Inter-frequency cell measurement results Check that the value of this IE is set to 1 cell reported
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1001
Event results
- Frequency info
-CHOICE mode FDD

Frequency info
- CHOICE mode FDD
CHOICE mode FDD
Parameter Set
Parameter Set
Parameter Set
Parameter Set
- TGPSI
- TGPS Status Flag
- TGCFN

1
Deactivate
Not present

Not present
- Default DPCH Offset Value Arbitrary value between 0..306688 by step of
512
- CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1002
- CHOICE mode FDD
estimation
38400
Parameter Set
Parameter Set

Message Type
Measured Results
- Frequency info
-CHOICE mode FDD
Event results
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1003
- Frequency info
-CHOICE mode FDD

After step 1, the UE shall send a MEASUREMENT REPORT message triggered by event 1a for cell 2.
After step 3, the UE shall send an ACTIVE SET UPDATE COMPLETE message to acknowledge that it has added cell
2 to its active set.
to acknowledge the downloading of the compressed mode parameters that were sent in the PHYSICAL CHANNEL
RECONFIGURATION message of step 4 (only if compressed mode was required).
2
. In that message,
After step 10, the UE shall revert to the old configuration and transmit a PHYSICAL CHANNEL
RECONFIGURATION FAILURE message.
3
. In that message,
8.2.6.39 Physical Channel Reconfiguration for transition from CELL_DCH to
CELL_DCH: Success (Seamless SRNS relocation) (without pending of
ciphering)
2>else:
The UE shall:
1>if the received reconfiguration message included the IE "Downlink counter synchronisation info"; or
2>re-establish RB2;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1004
1>if the IE "Downlink counter synchronisation info" was included in the reconfiguration message; or
Reference
3GPP TS 25.331 clause 8.2.2.
To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message in the new cell.
Initial Condition

Test Procedure
Table 8.2.6.39
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -75 -75 -60

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1005

The UE is in the CELL_DCH state, camping onto cell 1. SS configures its downlink transmission power settings
according to columns "T1" in table 8.2.6.39. The SS sends a PHYSICAL CHANNEL RECONFIGURATION message
requesting the UE to do a handover combined with SRNS relocation. This message includes IE "RRC State Indicator"
set to "CELL_DCH", IE Downlink counter synchronisation info and IE Integrity protection mode info. UE shall
reselect to cell 2 and SS verifies that the UE sends PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message. This message also includes a calculated new START value according to the formula START
X
' =MSB
20

X
and
IK
X
}) +2, calculated IE Integrity Check Info using a new FRESH value as included in IE Integrity protection
initialisation number in IE Integrity protection mode info in PHYSICAL CHANNEL RECONFIGURATION
message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration.
(SRB3).

Expected sequence

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1006
UE SS
1 Void
2 Void SS applies the downlink
according to the values in columns
"T1" of table 8.2.6.29.
3 PHYSICAL CHANNEL
RECONFIGURATION
This message is sent after last
ciphering activation time. New
applied on DL SRB1. LAI and RAI
of cell 2 are given to the UE, and
are the same as cell 1.
4 PHYSICAL CHANNEL
on UL SRB2 by UE.
CONFIRM

10 Void


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1007
UE SS
1 Void
according to the values in columns
"T1" of table 8.2.6.29.
3 PHYSICAL CHANNEL
RECONFIGURATION
as cell 1.
4 PHYSICAL CHANNEL
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DL SRB3.
on UL SRB2 by UE.
10 Void


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1008
New U-RNTI
- S-RNTI 0000 0000 0000 0000 0001B
CN Information info
- RB with PDCP information list Not Present.

PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Step 4)



After step 3, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH using AM RLC which includes which includes a calculated new START value according to the formula
START
X
' =MSB
20
configured CK
X
and IK
X
Integrity protection initialisation number in IE Integrity protection mode info in PHYSICAL CHANNEL
configuration.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1009
(In the case where ciphering is supported)After step 9, UE shall start new ciphering configuration on the RAB.

8.2.7 Physical Shared Channel Allocation [TDD only]
[Editor's note: This message is not included in Release99 so this is FFS.]
8.2.8 PUSCH capacity request [TDD only]
[Editor's note: This message is not included in Release99 so this is FFS.]
8.2.9 Void
8.3 RRC connection mobility procedure
8.3.1 Cell Update
8.3.1.1 Cell Update: cell reselection in CELL_FACH

A UE shall initiate the cell update procedure in the following cases:
1>Uplink data transmission:

1>Paging response:

1>Radio link failure:

1>Re-entering service area:

1>RLC unrecoverable error:

1>Cell reselection:
2>if none of the criteria for performing cell update with the causes specified above in the current subclause is
met:
3>if the UE is in CELL_FACH or CELL_PCH state and the UE performs cell re-selection; or
3>if the UE is in CELL_FACH state and the variable C_RNTI is empty:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1010
4>perform cell update using the cause "cell reselection".

When initiating cell update procedure, the UE shall:
1>stop timer T305;
1>if the UE is in CELL_DCH state:

1>move to CELL_FACH state, if not already in that state;
1>if the UE performs cell re-selection:
2>clear the variable C_RNTI; and
2>stop using that C_RNTI just cleared from the variable C_RNTI in MAC.
1>in case of a cell update procedure:
2>set the contents of the CELL UPDATE message according to TS 25.331 subclause 8.3.1.3;
2>submit the CELL UPDATE message for transmission on the uplink CCCH.

1>set counter V302 to 1;
1>start timer T302 when the MAC layer indicates success or failure in transmitting the message.

In case of cell update procedure the UE shall transmit a CELL UPDATE message.
The UE shall set the IEs in the CELL UPDATE message as follows:
1>set the IE "Cell update cause" corresponding to the cause specified in TS 25.331 subclause 8.3.1.2 that is valid
when the CELL UPDATE message is submitted to lower layers for transmission;
NOTE: During the time period starting from when a cell update procedure is initiated by the UE until when the
procedure ends, additional CELL UPDATE messages may be transmitted by the UE with different
causes.
1>set the IE "U-RNTI" to the value of the variable U_RNTI;
1>if the value of the variable PROTOCOL_ERROR_INDICATOR is TRUE:

1>if the value of the variable FAILURE_INDICATOR is TRUE:

When the UE receives a CELL UPDATE CONFIRM message; and
- if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable
U_RNTI; or
- if the message is received on DCCH:
the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1011
1>stop timer T302;
1>in case of a cell update procedure and the CELL UPDATE CONFIRM message:
2>includes "RB information elements"; and/or
2>includes "Transport channel information elements"; and/or
2>includes "Physical channel information elements"; and
2>if the variable ORDERED_RECONFIGURATION is set to FALSE:
3>set the variable ORDERED_RECONFIGURATION to TRUE.
1>act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified otherwise in
the following:

1>enter a state according to subclause 8.6.3.3 applied on the CELL UPDATE CONFIRM / URA UPDATE
CONFIRM message.

If the UE after state transition remains in CELL_FACH state, it shall
1>start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been
configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than
"infinity";
1>not prohibit periodical status transmission in RLC;

the UE shall:

2>set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC
transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted
2>clear that entry.


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1012
- includes the IE "RB information to release list":
the UE shall:
1>transmit a RADIO BEARER RELEASE COMPLETE as response message using AM RLC.
- does not include the IE "RB information to release list"; and
- includes the IE "RB information to reconfigure list"; or
- includes the IE "RB information to be affected list":
the UE shall:
1>transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using AM RLC.
- includes "Transport channel information elements":
the UE shall:
1>transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE as response message using AM
RLC.
the UE shall:
the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1013
the UE shall:
If the new state is CELL_FACH, the response message shall be transmitted using the new configuration after the state
transition., and the UE shall:

1>if the variable PDCP_SN_INFO is empty:

2>if the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message did not contain the IE "Ciphering
mode info":
3>when RLC has been requested to transmit the response message,
4>continue with the remainder of the procedure.

If any or several of the following conditions are true:
;
- reselection to another UTRA cell (including the previously serving cell) before completion of the cell update or
URA update procedure;
the UE shall:
1>stop T302 if it is running;

1>check whether it is still in "in service area";

2>clear any entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the
variable TRANSACTIONS.
If the UE detects "in service area" if it has not entered idle mode, and:
1>if V302 is equal to or smaller than N302, the UE shall:
2>if the UE performed cell re-selection:
3>delete its C-RNTI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1014
1>if V302 is greater than N302, the UE shall:

Reference
1. To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell.
2. To confirm that the UE sends the correct uplink response message when executing cell update procedure due to
cell reselection.
Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11) in cell 1 as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.3.1.1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -69 -69 -60
P-CCPCH
RSCP (TDD)
dBm -60 -69 -69 -60

Columns marked "T0" denote the initial conditions. SS switches the power settings repeatedly between columns "T1"
and "T0", whenever the description below specifies that the transmission power settings for cell 1 and cell 2 be
reversed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1015
The UE is in the CELL_FACH state, camping onto cell 1. SS configures its downlink transmission power settings
according to columns "T1" in table 8.3.1.1. The UE shall find cell 2 to be more suitable for service and hence perform a
cell reselection. After the completion of cell reselection, the UE shall transmits a CELL UPDATE message to the SS on
the uplink CCCH of cell 2 and set IE "Cell update cause" to "Cell Reselection". After the SS receives this message, it
transmits a CELL UPDATE CONFIRM message, which includes the IE "RRC State Indicator" set to "CELL_FACH",
to the UE on the downlink DCCH. UE shall verify that IE "New C-RNTI" is not included in the downlink message and
shall send a CELL UPDATE message to SS again. SS shall then send a CELL UPDATE CONFIRM message which
includes a valid IE "New C-RNTI". SS verifies that the UE send UTRAN MOBILITY INFORMATION CONFIRM
message.. UE shall stay in CELL_FACH state. SS configures its downlink transmission power settings according to
columns "T0" in table 8.3.1.1. The UE shall send a CELL UPDATE message on the uplink CCCH of cell 1. SS replies
with CELL UPDATE CONFIRM message and allocates new C-RNTI and U-RNTI identities to the UE. The IE "RRC
State Indicator" is set to "CELL_FACH" in this message. The UE shall transmit UTRAN MOBILITY INFORMATION
CONFIRM message. Following this, SS configures its downlink transmission power settings according to columns
"T1" in table 8.3.1.1. The UE shall initiate a cell update procedure by transmitting a CELL UPDATE message and
stating the cause as 'cell re-selection'. SS replies with a CELL UPDATE CONFIRM message which contains IE
"Physical channel information elements" and IE "RRC State Indicator" is set to "CELL_DCH". The UE shall move to
CELL_DCH state and send PHSICAL CHANNEL RECONFIGURATION COMPLETE message. The SS shall
transmit PHYSICAL CHANNEL RECONFIGURATION message, asking the UE to move to CELL_FACH state. The
UE shall send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message after transiting to
CELL_FACH state. Then, SS configures its downlink transmission power settings according to columns "T0" in table
8.3.1.1. The UE shall send a CELL UPDATE message on the uplink CCCH of cell 1. SS replies with a CELL UPDATE
CONFIRM message which contains IE "Transport channel information elements" and IE "RRC State Indicator" is set to
"CELL_DCH". The UE shall move to CELL_DCH state and send TRANSPORT CHANNEL RECONFIGURATION
COMPLETE message. The SS shall transmit PHYSICAL CHANNEL RECONFIGURATION message, asking the UE
to move to CELL_FACH state. The UE shall send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message after transiting to CELL_FACH state. Following this, SS configures its downlink transmission power settings
according to columns "T1" in table 8.3.1.1. The UE shall send a CELL UPDATE message on the uplink CCCH of cell
2. SS replies with a CELL UPDATE CONFIRM message which contains IE "RB information to be affected list". The
UE shall send RADIO BEARER RECONFIGURATION COMPLETE message. Then, SS configures its downlink
transmission power settings according to columns "T0" in table 8.3.1.1. The UE shall send a CELL UPDATE message
on the uplink CCCH of cell 1. SS replies with a CELL UPDATE CONFIRM message which contains IE "RB
information to release list". The UE shall send RADIO BEARER RELEASE COMPLETE message. Finally, SS
configures its downlink transmission power settings according to columns "T1" in table 8.3.1.1. The UE shall send a
CELL UPDATE message on the uplink CCCH of cell 2. SS shall not respond to this message but SS configures its
downlink transmission power settings according to columns "T0" in table 8.3.1.1. UE shall send a CELL UPDATE
message on the uplink CCCH of cell 1. SS shall then send CELL UPDATE CONFIRM message to UE. UE shall reply
with UTRAN MOBILITY INFORMATION CONFIRM message. SS calls for generic procedure C.2 to check that UE
is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1016
Expected sequence
UE SS
state in cell 1
The UE shall find that the cell
2 is better for service and
perform a reselection. SS
waits for the maximum
duration required for the UE to
camp to cell 2.
3 CELL UPDATE Value "cell reselection" shall
be indicated in IE "Cell update
cause"
4 CELL UPDATE CONFIRM IE "RRC State Indicator" is set
to "CELL_FACH".
4a CELL UPDATE Value "cell reselection" shall
cause"
4b CELL UPDATE CONFIRM See message content.
CONFIRM

6 SS reverses the transmission
power level of cell 1 and cell 2.
7 CELL UPDATE
8 CELL UPDATE CONFIRM New C-RNTI and U-RNTI
identities are assigned to the
UE. IE "RRC State Indicator"
is set to "CELL_FACH".
CONFIRM

11 CELL UPDATE
to "CELL_DCH".
IE "Physical channel
information elements" is
included in this message
12a PHYSICAL CHANNEL

13 PHYSICAL CHANNEL
RECONFIGURATION
The UE is in CELL_DCH now.
The SS shall send PHYSICAL
CHANNEL
RECONFIGURATION
message to the UE asking the
UE to transit to CELL_FACH
state.
14 PHYSICAL CHANNEL

15 The SS reverses the
transmission power level of
cell 1 and cell 2.
16 CELL UPDATE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1017
17 CELL UPDATE CONFIRM IE "Physical channel
information elements" is
included in this message, and
IE "RRC State Indicator" is
set to "CELL_DCH". IE
"Transport channel information
elements" is included in this
message
18 TRANSPORT CHANNEL

19 PHYSICAL CHANNEL
RECONFIGURATION
The UE is in CELL_DCH now.
The SS shall send PHYSICAL
CHANNEL
RECONFIGURATION
message to the UE asking the
UE to transit to CELL_FACH
state.
20 PHYSICAL CHANNEL

cell 1 and cell 2.
22 CELL UPDATE
23 CELL UPDATE CONFIRM New C-RNTI identity is
assigned to the UE.
IE "RRC State Indicator" is set
to "CELL_FACH".
IE "RB information to
reconfigure list" and IE "RB
information to be affected list"
is included in this message.
COMPLETE

cell 1 and cell 2.
26 CELL UPDATE
assigned to the UE.
to "CELL_FACH".
IE "RB information to release
list" is included in this
message
30 CELL UPDATE
32 CELL UPDATE
assigned to the UE.
CONFIRM

35 CALL C.2 If the test result of C.2
CELL_FACH state, the test

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1018
CELL UPDATE (Step 3, 4a, 7,, 11, 16, 22, 30 and 32)
U-RNTI
- S-RNTI In step 3, 4a and 7 check to see if set to '0000 0000
0000 0000 0001'.

In step 11, 16, 22, 26, 30 and 32, check to see if set to
same string in IE "S-RNTI" in IE "New U-RNTI" of CELL
UPDATE CONFIRM message in previous assignment

Use the same message sub-type found in TS 34.108, clause 9.
CELL UPDATE CONFIRM (Step 4b)
New C-RNTI '1010 1010 1010 1010'

New U-RNTI
- SRNC Identity '0000 0000 0001'
S-RNTI
New C-RNTI '0000 0000 0000 1111'

CELL UPDATE CONFIRM (Step 12 )
Use the same message sub-type found in step 8 and k=0, with the following exceptions:
CHOICE channel requirement
Uplink DPCH info Same as the IE in RADIO BEARER SETUP (Packet to
CELL_DCH from CELL_FACH in PS)
Downlink information common for all radio links Same as the IE in RADIO BEARER SETUP (Packet to
Downlink information per radio link list Same as the IE in RADIO BEARER SETUP (Packet to

PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Step 12a)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1019
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "Packet to CELL_FACH from
CELL_DCH in PS":
Use the same message sub-type found in TS 34.108, clause 9 with the following exceptions:
channels
Same as the IE in RADIO BEARER SETUP (Packet to
Added or Reconfigured uplink TrCH information

DL Transport channel information for all transport
channels
Added or Reconfigured downlink TrCH information Same as RADIO BEARER SETUP (Packet to
CHOICE channel requirement

Uplink DPCH info Same as the IE in RADIO BEARER SETUP (Packet to
Downlink information common for all radio links Same as the IE in RADIO BEARER SETUP (Packet to
Downlink information per radio link list Same as the IE in RADIO BEARER SETUP (Packet to

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "Packet to CELL_FACH from
CELL_DCH in PS", with following exception.

New C-RNTI '0000 0000 0000 1111'

RB information to be reconfigure
New C-RNTI '1010 1010 1010 1010'
- RB identity 20
- RLC info Not Present
- RB Information Release List Not Present
- RB Information Reconfiguration List Present
- RB Information Affected List Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1020
New C-RNTI '0000 0000 0000 1111'
-RB identity

4

New C-RNTI '1010 1010 1010 1010'

At step 3 the UE shall reselect to cell 2 and then it shall transmit a CELL UPDATE message which, sets the value "cell
reselection" in IE "Cell update cause".
At step 4a the UE shall transmit CELL UPDATE message which sets the value "cell reselection" in IE "Cell update
cause".
At step 4b, the SS shall send a CELL UPDATE CONFIRM.
At step 5, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message.

At step 7 the UE shall sent a CELL UPDATE message to the cell with stronger transmitting power, in order to indicate
that a cell reselection has taken place.
At step 9, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message.

At step 12, the SS shall send a CELL UPDATE CONFIRM taking the UE into CELL_DCH state. In addition, it also
specifies the IE Physical Channel Information elements.
At step 12a, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the new
physical channel assigned.
At step 13 and 14, the SS uses PHYSICAL CHANNEL RECONFIGURATION to take the UE into CELL_FACH state.

At step 15, the SS reverses the transmission power level of cell 1 and 2 causing the UE to reselect to a different cell.
At step 17, the SS shall send a CELL UPDATE CONFIRM and take the UE into CELL_DCH state. In addition, it also
specifies the IE Physical Channel Information elements and Transport Channel Information elements.
At step 18, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE.
At step 19 and 20, the SS uses PHYSICAL CHANNEL RECONFIGURATION to take the UE into CELL_FACH state.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1021
At step 22, the UE shall send a CELL UPDATE message to the cell with stronger transmitting power, in order to
indicate that a cell reselection has taken place.
At step 23, the SS shall send a CELL UPDATE CONFIRM taking the UE into CELL_FACH state. In addition, it also
specifies RB Information Reconfigure List and RB Information Affected List Information.
At step 24, the UE shall transmit a RADIO BEARER RECONFIGURATION COMPLETE.

At step 27, the SS shall send a CELL UPDATE CONFIRM taking the UE into CELL_FACH state. In addition, it also
specifies the IE RB Information to release list.
At step 28, the UE shall transmit a RADIO BEARER RELEASE COMPLETE.

At step 33, the SS shall send a CELL UPDATE CONFIRM
At step 34, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message
8.3.1.2 Cell Update: cell reselection in CELL_PCH


1>Paging response:




Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1022
1>Cell reselection:
met:
1>stop timer T305;



causes.

1>if the value of the variable FAILURE_INDICATOR is TRUE:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1023
U_RNTI; or
the UE shall:
1>stop timer T302;
1>in case of a cell update procedure and the CELL UPDATE CONFIRM message:

the following:

1>enter a state according to subclause 8.6.3.3 applied on the CELL UPDATE CONFIRM / URA UPDATE
CONFIRM message.

If the UE after state transition enters CELL_PCH state, it shall:

1>start the timer T305 using its initial value if timer T305 is not running and periodical update has been configured
by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity";
1>select Secondary CCPCH according to subclause 8.5.19;
2>use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging Occasion and PICH
Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2 in CELL_PCH state.
the UE shall:
Reference
3GPP TS 25.331 clause 8.3.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1024
1. To confirm that the UE, in CELL_PCH state, executes a cell update procedure after the successful reselection of
another UTRA cell.
Initial Condition
System Simulator: 2 cells Cell 1 and 2 are active.
UE: CELL_PCH (state 6-12) in cell 1 as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to CELL_PCH state and is camped onto cell 1. SS configures its downlink transmission power
settings according to columns "T1" in table 8.3.1.1. When the UE detects the presence of cell 2, it moves to
CELL_FACH state and transmits a CELL UPDATE message on the uplink CCCH. The value "cell reselection" shall be
set in IE "Cell update cause" in CELL UPDATE message. Upon reception of CELL_UPDATE message, SS replies
with a CELL UPDATE CONFIRM message with the IE "RRC State Indicator" set to "CELL_PCH". After receiving
this message, the UE returns to CELL_PCH state without transmitting any uplink message. SS calls for generic
Expected sequence
UE SS
CELL_PCH state in cell 1
2 SS applies the downlink
The UE shall find that the cell
2 is better and attempt to
perform a cell reselection.
3 CELL UPDATE The UE moves to
CELL_FACH state and
transmits this message with
the IE "Cell update cause" set
to "cell reselection"
to "CELL_PCH".
5 The UE is in CELL_PCH state.
CELL_PCH state, the test

CELL UPDATE (Steps 3)
The same message found in TS 34.108 clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1025
U-RNTI
- S-RNTI Check to see if set to '0000 0000 0000 0000 0001'

Use the same message sub-type found in TS 34.108 clause 9, with the following exceptions:

After step 2 the UE shall reselect to cell 2 and transmit a CELL UPDATE message, containing the IE "Cell update
cause" set to "cell reselection".
After step 4, the UE shall enter CELL_PCH state.
8.3.1.3 Cell Update: periodical cell update in CELL_FACH

UE shall initiate the cell update procedure in the following cases:

1>Paging response:




1>Cell reselection:

1>Periodical cell update:
met; and
2>if the UE is in CELL_FACH or CELL_PCH state; and
2>if the timer T305 expires; and
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1026
2>if the criteria for "in service area" as specified in TS 25.331 subclause 8.5.5.2 is fulfilled; and
2>if periodic updating has been configured by T305 in the IE "UE Timers and constants in connected mode" set
to any other value than "infinity":
3>perform cell update using the cause "periodical cell update".
When initiating the cell update procedure, the UE shall:
1>stop timer T305;



causes.

U_RNTI; or
the UE shall:
1>stop timer T302;

the following:
1>enter a state according to TS 25.331 subclause 8.6.3.3 applied on the CELL UPDATE CONFIRM / URA
UPDATE CONFIRM message.
If the UE after state transition remains in CELL_FACH state, it shall
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1027
1>start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been
configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than
"infinity";
1>not prohibit periodical status transmission in RLC;
or
- the UE after the state transition moves to another state than the CELL_FACH state:
the UE shall:
2>set the IE "RRC transaction identifier" in any response message transmitted below to the value of "RRC
transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted
2>clear that entry.
2>clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the
1>set the variable CELL_UPDATE_STARTED to FALSE;
1>clear the variable SECURITY_MODIFICATION.

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1028
the UE shall:

1>act on received information elements as specified in TS 25.331 subclause 8.6;
1>if the IE "UE Timers and constants in connected mode" is present:
2>store the values of the IE "UE Timers and constants in connected mode" in the variable
TIMERS_AND_CONSTANTS, replacing any previously stored value for each timer and constant; and
2>for each updated timer value:
3>start using the new value next time the timer is started;
2>for each updated constant value:
3>start using the new value directly;
1>set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION CONFIRM message to the
value of "RRC transaction identifier" in the entry for the UTRAN MOBILITY INFORMATION message in the
1>clear that entry;

Reference
3GPP TS 25.331 clause 8.3.1, 8.3.3.3.
1. To confirm that the UE executes a periodical cell update procedure following the expiry of timer T305.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1029
Test Procedure
Table 8.3.1.3
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60
-69 -69
-60
P-CCPCH
RSCP
(TDD)
dBm
-60
-69 -69
-60

The UE is in CELL_FACH state. When the UE detects the expiry of timer T305 according to the settings in system
information, the UE transmits a CELL UPDATE message to the SS on the uplink CCCH with a cause indicating
periodical cell updating. SS replies with a CELL UPDATE CONFIRM message, and IE "RRC State Indicator" is set to
"CELL_FACH". SS verifies that the UE does not transmit any uplink message. SS then waits for T305 to expire again.
The UE shall send another CELL UPDATE message to report periodic cell updating. After the SS receives this
message, it transmits a CELL UPDATE CONFIRM message which includes the IEs "new C-RNTI", "new U-RNTI" to
the UE on the downlink DCCH. Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM
message on the uplink DCCH to acknowledge the receipt of the new UE identities. Next, SS transmits UTRAN
MOBILITY INFORMATION message, which includes IE "T305" set to "infinity", to UE. UE shall transmit UTRAN
MOBILITY INFORMATION CONFIRM message. SS configures its downlink transmission power settings according
to columns "T1" in table 8.3.1.3, causing the UE to enter CELL_FACH state in cell 2 and transmit a CELL UPDATE
message on uplink CCCH with IE "Cell update cause" set to "cell reselection". Then SS shall transmit CELL UPDATE
CONFIRM. Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink
DCCH to acknowledge the receipt of the new UE identities. SS then monitors the uplink CCCH for a period of 60
minutes (ideally the SS should monitor this up to the maximum possible value for timer T305 (720 minutes), but for
practical reasons 60 minutes (twice default timer of 30 minutes) is regarded as being sufficient) and verifies that no
CELL_UPDATE message is received. After this, the SS transmits UTRAN MOBILITY INFORMATION message,
which includes IE "T305" set to '5', to UE. UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM
message. SS configures its downlink transmission power settings according to columns "T0" in table 8.3.1.3, causing
the UE to enter CELL_FACH state in cell 1 and transmit a CELL UPDATE message on uplink CCCH with IE "Cell
update cause" set to "cell reselection". Then SS shall transmit CELL UPDATE CONFIRM. Then the UE shall transmit
an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to acknowledge the receipt of the
new UE identities. UE shall resume periodic cell updating procedure and transmit CELL_UPDATE message after T305
(5 minutes) expires.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1030
Expected sequence
UE SS
state. SS waits until T305 has
expired.
2 CELL UPDATE IE "Cell update cause" shall be
set to "periodical cell updating"
3 CELL UPDATE CONFIRM No RNTI identities are given.
No information on PRACH and
S-CCPCH are provided.
4 SS verifies that no uplink
message is received from UE.
SS waits for another period to
allow T305 to expire.
5 CELL UPDATE Set to "periodical cell update"
in IE "Cell update cause" upon
the expiry of timer T305.
6 CELL UPDATE CONFIRM Including IEs "new C-RNTI",
"new U-RNTI" and IE "RRC
State Indicator" is set to
"CELL_FACH"
CONFIRM

8 UTRAN MOBILITY INFORMATION IE "T305" is set to 'infintiy'.
CONFIRM

columns "T1" of table 8.3.1.3
set to "cell reselection".
12a UTRAN MOBILITY INFORMATION
CONFIRM

13 SS waits for 60 minutes and
checks that no CELL UPDATE
message is transmitted on
uplink PRACH channel.
14 UTRAN MOBILITY INFORMATION IE "T305" is set to '5.
CONFIRM

columns "T0" of table 8.3.1.3
set to "cell reselection".
CONFIRM

19 CELL UPDATE UE shall transmit this
message with "cell update
cause" set to "periodical cell
updating" after T305 expires.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1031
CELL UPDATE (Step 2 and 5)
U-RNTI
Cell Update Cause Check to see if set to 'periodical cell updating'

U-RNTI
- S-RNTI Check to see if set to same bit string as in IE "S-RNTI"
in IE "U-RNTI" of the CELL UPDATE CONFIRM
Cell Update Cause Check to see if set to "cell reselection"

CELL UPDATE CONFIRM (Step 3 and 20)
Use the same message sub-type found in TS 34.108, clause 9.
CELL UPDATE CONFIRM (Step 6, 12 and 18)
New U-RNTI
- SRNC Identity Set to '0000 0000 0001'
- S-RNTI Set to an arbitrary string different from '0000 0000 0000
0000 0001'
New C-RNTI '1010 1010 1010 1010'

U-RNTI
- S-RNTI Check to see if set to same bit string as in IE "S-RNTI"
in IE "U-RNTI" of the CELL UPDATE CONFIRM

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1032
UE Timers and constants in connected mode
- T305 infinity

- T305 5

After step 1 the UE shall detect the expiry of timer T305 and then transmits a CELL UPDATE message setting value
"periodical cell update" into IE "Cell update cause".
After step 3 the UE shall not send any uplink message as a response to CELL UPDATE CONFIRM message sent in
step 3.
After step 4 the UE shall send a CELL UPDATE message, specifying the cell updating cause to be "periodical cell
update".
After step 6 the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.
using AM RLC.
After step 10, the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "cell reselection" on
the uplink CCCH.
using AM RLC.
Between step 12a and 14, the UE shall not transmit any CELL UPDATE message.
using AM RLC.
the uplink CCCH.
using AM RLC.
After step 18a, the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "periodical cell
update" on the uplink CCCH.
8.3.1.4 Cell Update: periodical cell update in CELL_PCH

UE shall initiate the cell update procedure in the following cases:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1033

1>Paging response:




1>Cell reselection:

met; and
2>if the criteria for "in service area" as specified in TS 25.331 subclause 8.5.5.2 is fulfilled; and
1>set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION CONFIRM message to the
1>clear that entry;

Reference
3GPP TS 25.331 clause 8.3.1, 8.3.3.3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1034
1. To confirm that the UE, in CELL_PCH state, executes a cell update procedure after the expiry of timer T305.
Initial Condition
UE: CELL_PCH (state 6-12) in cell 1 as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.3.1.4
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60
-69 -69
-60
P-CCPCH
RSCP
(TDD)
dBm
-60
-69 -69
-60

The UE starts from CELL_PCH state. When the UE detects the expiry of periodic cell updating timer T305 according
to the system information, the UE moves to CELL_FACH state. It shall transmit a CELL UPDATE message on the
uplink CCCH and set the value "periodical cell update" into IE "Cell update cause". SS answers with a CELL UPDATE
CONFIRM message on the downlink DCCH. Then the UE shall transmit an UTRAN MOBILITY INFORMATION
CONFIRM message on the uplink DCCH to acknowledge the receipt of the new UE identities. SS transmits UTRAN
MOBILITY INFORMATION message, which includes IE "T305" set to "infinity", to UE. UE shall transmit UTRAN
MOBILITY INFORMATION CONFIRM message. SS configures its downlink transmission power settings according
to columns "T1" in table 8.3.1.4, causing the UE to enter CELL_FACH state in cell 2 and transmit a CELL UPDATE
message on uplink CCCH with IE "Cell update cause" set to "cell reselection". Then SS shall transmit CELL UPDATE
CONFIRM with IE "RRC state indicator" set to "CELL_PCH" on the downlink CCCH. Then UE shall enter
CELL_PCH state. SS then monitors the uplink CCCH for a period of 60 minutes (ideally the SS should monitor this up
to the maximum possible value for timer T305 (720 minutes), but for practical reasons 60 minutes (twice default timer
of 30 minutes) is regarded as being sufficient) and verifies that no CELL_UPDATE message is received. SS then
configures its downlink transmission power settings according to columns "T0" in table 8.3.1.4, causing the UE to enter
CELL_FACH state in cell 1 and transmit a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set
to "cell reselection". Then SS shall transmit CELL UPDATE CONFIRM on the downlink DCCH. Then the UE shall
transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to acknowledge the
receipt of the new UE identities. Next, SS transmits UTRAN MOBILITY INFORMATION message, which includes IE
"T305" set to "5", to UE. UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM message. SS configures
its downlink transmission power settings according to columns "T1" in table 8.3.1.4, causing the UE to enter
CELL_FACH state in cell 2 and transmit a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set
to "cell reselection". Then SS shall transmit CELL UPDATE CONFIRM with IE "RRC state indicator" set to
"CELL_PCH" on the downlink CCCH. Then UE shall enter CELL_PCH state. After T305 expires, UE shall transmit
CELL UPDATE message with IE "cell update cause" set to "periodical cell update". SS shall transmit CELL UPDATE
CONFIRM message on the downlink CCCH to end the procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1035
Expected sequence
UE SS
1 The UE is in the CELL_PCH
state. SS waits until T305 has
expired. Wait for CELL
UPDATE message and then
verify that the time of arrival of
this message is in the range of
T305 value +/- 10 % after it
entered CELL_PCH state
2 CELL UPDATE The UE shall move to
CELL_FACH state and
to "periodical cell update".
CONFIRM

4 UTRAN MOBILITY INFORMATION IE "T305" is set to 'infintiy'.
CONFIRM

CELL_FACH state and
8 CELL UPDATE CONFIRM UE enters CELL_PCH state
after receiving this message.
9 SS waits for 60 minutes and
checks that no CELL UPDATE
message is transmitted on
uplink PRACH channel.
CELL_FACH state and
CONFIRM

13 UTRAN MOBILITY INFORMATION IE "T305" is set to '5'.
CONFIRM

CELL_FACH state and
17 CELL UPDATE CONFIRM UE enters CELL_PCH state
after receiving this message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1036
UE SS
18 SS wait for T305 timer to
expire
set to "periodical cell update".

U-RNTI

CELL UPDATE (Step 7, 11 and 16)
U-RNTI
Cell Update Cause Check to see if set to "cell reselection"

New C-RNTI '1010 1010 1010 1010'

CELL UPDATE CONFIRM (Step 8, 17 and 20)
RRC state indicator CELL_PCH

UTRAN MOBILITY INFORMATION (Step 4 and 13)
- T305 Set to 'infinity' in step 4 and '5' in step 13

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1037
After step 1 the UE shall detect the expiry of timer T305, it shall then move to CELL_FACH state and transmits a
CELL UPDATE message with the IE "Cell update cause" set to "periodical cell update".
using AM RLC.
using AM RLC.
the uplink CCCH.
After step 8 and before step 10, the UE shall not transmit any CELL UPDATE messages.
the uplink CCCH.
using AM RLC.
using AM RLC.
the uplink CCCH.
After step 18 the UE shall transmit a CELL UPDATE message stating the cell update cause to be periodic updating.
8.3.1.5 Cell Update: UL data transmission in URA_PCH

2>if the UE is in URA_PCH or CELL_PCH state; and
2>if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit:
3>perform cell update using the cause "uplink data transmission".

Reference
3GPP TS 25.331 clause 8.3.1 and 8.1.2
1. To confirm that the UE executes a cell update procedure when the UE transmits uplink data if the UE is in
URA_PCH state.
Initial Condition
System Simulator: 1cell
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1038
The UE has been registered in both CS and PS domains.
Test Procedure
The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message with IE "RRC State Indicator" set to
"URA_PCH". The UE shall reply with PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and
move to URA_PCH state. The SS transmits a PAGING TYPE 1 message which includes a matched U-RNTI and the
optional IE "CN originated page to connected mode UE". The UE then moves to CELL_FACH state and transmits a
CELL UPDATE message to the SS on the uplink CCCH, with the IE "Cell update cause" set to value "uplink data
transmission". After receiving such a message, SS transmits CELL UPDATE CONFIRM message on downlink DCCH.
Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to
acknowledge the receipt of the new UE identities. The UE shall stay in CELL_FACH state and transmit an INITIAL
DIRECT TRANSFER message using AM RLC on DCCH.
Expected sequence
UE SS
CELL_FACH state.
2 Void
3 Void
4 PHYSICAL CHANNEL
RECONFIGURATION
IE "RRC State Indicator" set to
"URA_PCH"
5 PHYSICAL CHANNEL
UE moves to URA_PCH state.
5a PAGING TYPE 1 Includes Matched identifier
and optional IE CN originated
page to connected mode UE"
6 CELL UPDATE The UE shall move to CELL
FACH state with the message
set to "uplink data
transmission" in IE "Cell
update cause".
CONFIRM

8 INITIAL DIRECT TRANSFER Response to the paging
message sent in step 5a

Use the same message sub-type found in TS 34.108 clause 9, which is entitled "Packet to CELL_FACH from
CELL_FACH in PS", with the following exceptions:
URA identity 0000 0000 0000 0001B

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1039
PAGING TYPE 1 (Step 5a)
Message Type
Paging record
- U-RNTI
- CN originated page to connected mode UE
-Paging cause Terminating Call supported by the UE in the CS
domain
-CN domain identity CS Domain
-Paging record type identifier Set to "IMSI (GSM-MAP)" for UEs supporting GSM-

U-RNTI
Cell Update Cause Check to see if set to 'uplink data transmission'

New C-RNTI '1010 1010 1010 1010'

--- CHOICE Routing basis Local(P)TMSI
---- Routing parameter This bit string is set to bits b14 through b23 of the TMSI.
represented by a string of bits numbered from b0 to
b31, with bit b0 being the least significant
through b23 of the TMSI.
contains bit b23 of the TMSI

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1040
START Not checked

After step 4, UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and move to
URA_PCH state.
After step 5a, the UE shall move to CELL_FACH state to initiate a cell update procedure and transmits a CELL
UPDATE message which is set to "uplink data transmission" in IE "Cell update cause".
using AM RLC.
After step 7a, UE shall transmit INITIAL DIRECT TRANSFER message to SS using AM RLC on DCCH.
8.3.1.6 Cell Update: UL data transmission in CELL_PCH

2>if the UE is in URA_PCH or CELL_PCH state; and
2>if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit:
3>perform cell update using the cause "uplink data transmission".

Reference
3GPP TS 25.331 clause 8.3.1 and 8.1.2
1. To confirm that the UE executes a cell update procedure when the UE transmits uplink data if the UE is in
CELL_PCH state.
Initial Condition
The UE is registered in both CS and PS domains.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1041
Test Procedure
The UE is in the CELL_FACH state. The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message with
IE "RRC State Indicator" set to "CELL_PCH". The UE shall reply with PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message and move to CELL_PCH state. The SS transmits a PAGING TYPE 1
message which includes a matched U-RNTI and the optional IE "CN originated page to connected mode UE". The UE
then moves to CELL_FACH state and transmits a CELL UPDATE message to the SS on the uplink CCCH, with the IE
"Cell update cause" set to value "uplink data transmission". After receiving such a message, SS transmits a CELL
UPDATE CONFIRM message on downlink DCCH. Then the UE shall transmit an UTRAN MOBILITY
INFORMATION CONFIRM message on the uplink DCCH to acknowledge the receipt of the new UE identities. The
UE shall stay in CELL_FACH state and transmit an INITIAL DIRECT TRANSFER message using AM RLC on
DCCH.
Expected sequence
UE SS
CELL_FACH state.
2 Void
3 Void
4 PHYSICAL CHANNEL
RECONFIGURATION
IE "RRC State Indicator" set to
"CELL_PCH"
5 PHYSICAL CHANNEL
UE moves to CELL_PCH
state.
5a PAGING TYPE 1 Includes Matched identifier
and optional IE CN originated
page to connected mode UE"
6 CELL UPDATE The UE moves to CELL FACH
state and transmit this
message which is set to
"uplink data transmission" in
IE "Cell update cause".
7 CELL UPDATE CONFIRM See message content .
CONFIRM

8 INITIAL DIRECT TRANSFER Response to the paging
message sent in step 5a

Use the same message sub-type found in TS 34.108 clause 9, which is entitled "Packet to CELL_FACH from
CELL_FACH in PS", with the following exceptions:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1042
PAGING TYPE 1 (Step 5a)
Message Type
Paging record
- U-RNTI
- CN originated page to connected mode UE
-Paging cause Terminating Call supported by the UE in the CS
domain
-CN domain identity CS Domain
-Paging record type identifier Set to "IMSI (GSM-MAP)" for UEs supporting GSM-

U-RNTI
Cell Update Cause Check to see if set to 'uplink data transmission'

New C-RNTI '1010 1010 1010 1010'

--- CHOICE Routing basis Local(P)TMSI
---- Routing parameter This bit string is set to bits b14 through b23 of the TMSI.
represented by a string of bits numbered from b0 to
b31, with bit b0 being the least significant
through b23 of the TMSI.
contains bit b23 of the TMSI

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1043
START Not checked

After step 4, UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and move to
CELL_PCH state.
After step 5, the UE shall move to CELL_FACH state to initiate a cell update procedure and transmits a CELL
UPDATE message which is set to "uplink data transmission" in IE "Cell update cause".
using AM RLC.
After step 7a, UE shall transmit a INITIAL DIRECT TRANSFER message to SS using AM RLC on DCCH.
8.3.1.7 Void
8.3.1.8 Void
8.3.1.9 Cell Update: re-entering of service area after T305 expiry and being out of
service area


1>Paging response:


met; and
2>if the UE has been out of service area and re-enters service area before T307 or T317 expires:
3>perform cell update using the cause "re-entering service area".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1044
When the T305 expires and the UE detects that it is "out of service area" as specified in TS 25.331 subclause 8.5.5.1,
the UE shall
1>start timer T307;

If the UE detects "in service area" according to TS 25.331 subclause 8.5.5.2 and timer T307 or T317 is running, the UE
shall:

Reference
1. To confirm that the UE performs a cell search after experiencing an "out of service area" condition following the
expiry of timer T305.
2. To confirm that the UE initiates cell updating procedure if it manages to re-enter the service area.
Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108, using the specific message contents
as specified below.
Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exception.
T305 5 minutes
T307 50 seconds
T317 600 seconds

Specific timer tolerances
Use the same timer tolerances found in subclause 4.2.3 of TS 34.108, with the following exceptions.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1045
T305: +/- 10 s
T307: +/- 2 s
Test Procedure
Table 8.3.1.9
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -80
P-CCPCH
RSCP (TDD)
dBm -60 -80

Table 8.3.1.9 illustrates the downlink power to be applied at various time instants of the test execution. Columns
marked "T0" denote the initial conditions.
The UE is in the CELL_FACH state. The content of the SYSTEM INFORMATION BLOCK TYPE 3 and 4 is
modified. SS configures its downlink transmission power settings according to columns "T1" in table 8.3.1.9 so that
S<0. Following the expiry of periodic cell updating timer T305 according to the system information, the UE shall detect
that it is out of service area. Within the time interval equivalent to T307 timer value, SS configures its downlink
transmission power settings according to columns "T0" in table 8.3.1.9 so that S>0. The UE shall find that it is back in
service area, and transmit a CELL UPDATE message to the SS on the uplink CCCH. In this message, the IE "Cell
update cause" shall be set to "re-entered service area". After the SS receives this message, it transmits a CELL
UPDATE CONFIRM message with the IE "RRC State Indicator" set "CELL_PCH" on the downlink DCCH. The UE
shall enter CELL_PCH state. SS configures its downlink transmission power settings according to columns "T1" in
table 8.3.1.9 so that S<0. Following the expiry of periodic cell updating timer T305 according to the system
information, the UE shall detect that it is out of service area. Within the time interval equivalent to T307 timer value, SS
configures its downlink transmission power settings according to columns "T0" in table 8.3.1.9 so that S>0. The UE
shall find that it is back in service area, move to CELL_FACH and transmits a CELL UPDATE message to the SS on
the uplink CCCH. In this message, the IE "Cell update cause" shall be set to "re-entered service area". After the SS
receives this message, it transmits a CELL UPDATE CONFIRM message on the downlink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1046
Expected sequence
UE SS
state of cell 1.
and 4
SS changes the contents of
MASTER INFORMATION
BLOCK and SYSTEM
INFORMATION BLOCK (see
specific message contents).
1b SYSTEM INFORMATION CHANGE
INDICATION

2 SS configures its downlink
table 8.3.1.9 so that its S value
falls below 0.
3 The UE shall detect a "out of
service" condition upon expiry
of timer T305 and it shall
search for other cells to camp
on. (T307 timer starts)
table 8.3.1.9.
5 CELL UPDATE The value "re-entered service
area" shall be found in IE "Cell
update cause" in this message
6 CELL UPDATE CONFIRM "RRC State Indicator" is set to
"CELL_PCH"
table 8.3.1.9 so that its S value
falls below 0 and waits 5
minutes and 20 seconds until
T305 has expired.
table 8.3.1.9.
9 CELL UPDATE UE shall move to
CELL_FACH. It shall transmit
this message with cell update
cause set to "re-entered
service area"

MASTER INFORMATION BLOCK (Step 1a)
MIB Tag 2

SYSTEM INFORMATION BLOCK TYPE 3 and 4 (Step 1a)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1047
Qrxlevmin -70

SYSTEM INFORMATION CHANGE INDICATION (Step 1b)
Message Type
MIB Value tag 2

U-RNTI
Cell Update Cause Check to see if set to 're-entered service area'

Use the same message sub-type found in TS 34.108 clause 9, with the following exception.

After step 4 the UE shall transmit a CELL UPDATE message in which the IE "Cell update cause" is set to the value "re-
entered service area".
After step 8 the UE shall move to CELL_FACH and then transmit a CELL UPDATE message, with the IE "Cell
Update Cause" set to "re-entered service area".
8.3.1.10 Cell Update: expiry of T307 after T305 expiry and being out of service area

When the T307 expires, the UE shall:
1>move to idle mode;
1>release all dedicated resources;
1>perform other actions when entering idle mode from connected mode as specified in TS 25.331 subclause 8.5.2;
Reference
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1048
1 To confirm that the UE moves to idle mode after the expiry of T307, indicating that it is out of service area when
attempting to perform a periodic cell updating procedure.
Initial Condition
Timer T305 is set to 5min.
Test Procedure
Table 8.3.1.10
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 -80
P-CCPCH
RSCP (TDD)
dBm -60 -80

The UE is in CELL_FACH state at the start of the test. Before the expiry of periodic cell updating timer T305, the
content of the SYSTEM INFORMATION BLOCK TYPE 3 and 4 is modified. After T305 expires, UE shall transmit
CELL UPDATE message with IE "cell update cause" set to "periodical cell update". SS shall transmit CELL UPDATE
CONFIRM message. Now the UE and SS are synchronized. Immediately after the cell update procedure is finalized, the
SS starts a delay timer T
delay
(see below for limits on the timer value). When T
delay
expires the SS configures its
downlink transmission power settings according to columns "T1" in table 8.3.1.10 so that S<0 and this results in a "out
of service area" condition. The SS continues to listen to the uplink channel to detect possible attempts to perform a cell
updating procedure. The UE shall not send any CELL UPDATE message on the uplink CCCH, instead it triggers timer
T307 after expiry of T305. After the expiry of timer T305+T307+10% margin since completion of the cell update
procedure, SS configures its downlink transmission power settings according to columns "T0" in table 8.3.1.10 so that
S>0, the UE shall enter idle state. SS waits for 5s and then calls for generic procedure C.1 to check that UE is in idle
mode state.
Note 1 : The value chosen for Tdelay should be midway between the following logical minimum and maximum
values:
Minimum >T305 +T307 T317
Maximum <T305
Note 2 : TS 25.331 (from J une 2003) specifies that the UE should treat any value of T317 received from UTRAN as
though it is equal to infinity. Nevertheless, the value of T317 used in Note 1 should be the value
broadcast in SIB1 by the SS (or the implied default value if none is broadcast).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1049
Expected sequence
UE SS
CELL_FACH state.
and 4
MASTER INFORMATION
BLOCK and SYSTEM
1b SYSTEM INFORMATION CHANGE
INDICATION

1c CELL UPDATE IE "Cell update cause" shall be
set to "periodical cell update".
1d CELL UPDATE CONFIRM
1e SS waits Tdelay (see above)
2a SS configures its downlink
table 8.3.1.10 so that the cell
is no longer suitable for
camping. The UE shall detect
that it is out of service area
and refrains from transmitting
CELL UPDATE message due
to periodic cell updating.
2b SS waits a further
(T305+T307- Tdelay) +10% for
UE to enter idle mode.
3 The UE detects the expiry of
timer T305 and it searches for
other cells to camp on. After
the expiry of timer T307, the
UE shall enter idle mode. SS
configures its downlink
table 8.3.1.10 so that the cell
is suitable for camping. SS
waits for 5s.
indicates that UE is in idle
mode state, the test passes,
otherwise it fails.

MIB Tag 2

Qrxlevmin -70

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1050
SYSTEM INFORMATION CHANGE INDICATION (Step 1b)
Message Type
MIB Value tag 2

CELL UPDATE (Step 1c)
The same message found in Annex A shall be transmitted by the UE on the uplink CCCH, with the exception of the
following IEs:

U-RNTI

Use the same message type found in TS 34.108 clause 9, with the following exception.
Paging record
- CN domain identity Supported Domain (PS Domain or CS Domain)
- IMSI Set to the same IMSI value stored in the TEST USIM
card.

After step 3 the UE shall move to idle mode.
8.3.1.11 Cell Update: Success after T302 time-out

- expiry of timer T302;

the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1051

Reference
1. To confirm that the UE repeats the transmission of CELL UPDATE message after failing to receive any
response from the SS before T302 timer expires.
Initial Condition
Test Procedure
At the start of the test, the UE is brought to CELL_FACH state. When the UE detects the expiry of periodic cell
updating timer T305 according to the system information, the UE transmits a CELL UPDATE message to the SS on the
uplink CCCH. The IE "Cell update cause" in this message shall be set to "periodical cell update". SS ignores this
message, and the UE shall then re-transmit a CELL UPDATE message after the expiry of timer T302. When the SS has
received (N302+1) such messages, it transmits a CELL UPDATE CONFIRM message with new values for "C-RNTI"
to the UE. Finally, the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink
DCCH. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1052
Expected sequence
UE SS
1 The UE starts from
CELL_FACH state. SS
initializes its internal counter K
to 0 and waits until the expiry
of T305 timer.
2 CELL UPDATE The value "periodical cell
update" shall be set in IE "Cell
update cause".
3 If K is equal to N302 then
proceeds to step 5.
4 SS increments counter K,
transmits no response to the
UE and waits for an additional
period equal to the value of
timer T302. The next step is
step 2.
5 CELL UPDATE CONFIRM The message includes IEs
"new C-RNTI". The IE "RRC
State Indicator" is set to
"CELL_FACH".
CONFIRM


U-RNTI
Cell Update Cause Check to see if set to 'Periodic cell updating'

Use the same message sub-type found in TS 34.108 clause 9, with the following exception:
New C-RNTI Set to an arbitrary string different from '0000 0000 0000
0001'

After step 1 the UE shall detect the expiry of timer T305 then transmit a CELL UPDATE message on the uplink CCCH,
setting "periodical cell update" into IE "Cell update cause".
After step 2 the UE shall re-transmits a CELL UPDATE message after the expiry of timer T302. A total of (N302+1)
transmissions of CELL UPDATE message shall be detected in SS.
After step 5 the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH
and stay at CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1053
8.3.1.12 Cell Update: Failure (After Maximum Re-transmissions)



2>if the criteria for "in service area" as specified in subclause 8.5.5.2 in TS 25.331 is fulfilled; and


1>set the IE "Cell update cause" corresponding to the cause specified in subclause 8.3.1.2 in TS 25.331 that is valid


the UE shall:

1>check whether it is still in "in service area" (see subclause 8.5.5.2) in TS 25.331;



Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1054


2>enter idle mode;
2>other actions the UE shall perform when entering idle mode from connected mode are specified in TS
25.331subclause 8.5.2;
Reference
3GPP TS 25.331 clause 8.3.1.2, 8.3.1.3, 8.3.1.1.2.
1. To confirm that the UE repeats the cell update procedure upon the expiry of timer T302 and moves to idle state
when its internal counter V302 is greater than N302.
Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11)as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is initially in CELL_FACH state. When the UE detects the expiry of periodic cell updating timer T305, the UE
transmits a CELL UPDATE message to the SS on the uplink CCCH to perform a periodic cell updating procedure. The
SS ignores this message, and the UE shall attempt to re-transmit a CELL UPDATE message up to a maximum of
(N302) times after the expiry of timer T302. After (N302) attempts of retransmission, the UE shall return to idle state.
SS waits for 5s and then calls for generic procedure C.1 to check that UE is in idle mode state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1055
Expected sequence
UE SS
state. SS sets its internal
counter K=0 and waits for a
period equals to timer value
T305.
update cause".
3 SS transmits no response to
the UE and increments
counter K with 1.
4 SS waits for an additional
period equal to T302 timer and
if K is not greater than N302,
then next step is step 2. Else
the next step is step 5.
5 The UE shall enter idle mode
state.
otherwise it fails.

U-RNTI
Cell Update Cause Check to see if set to 'Periodical cell update'

After step 1 the UE shall transmit a CELL UPDATE message on the uplink CCCH and set value "periodical cell
update" into IE "Cell update cause".
After step 3 and if K is not greater than N302, the UE shall retry to transmit a CELL UPDATE message.
After step 3 and if K is greater than N302, the UE shall stop transmitting CELL UPDATE message and then enters idle
state.
8.3.1.13 Cell Update: Reception of Invalid CELL UPDATE CONFIRM Message

8.3.1.13.2 Conformance Requirement
If the UE receives an CELL UPDATE CONFIRM message, which contains a protocol error causing the variable
1>If V302 is equal to or smaller than N302, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1056


2>enter idle mode;
2>Other actions the UE shall perform when entering idle mode from connected mode are specified in TS 25.331
subclause 8.5.2;
Reference
3GPP TS 25.331 clause 8.3.1.11.
1. To confirm that the UE retransmits a CELL UPDATE message when it receives an invalid CELL UPDATE
CONFIRM message, before the number of retransmissions has reached the maximum allowed value.
8.3.1.13.4 Method of Test
Initial Condition
UE: CELL_PCH (state 6-12) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is brought to CELL_PCH state at the beginning of the test. SS pages the UE by sending a PAGING TYPE 1
message using the U-RNTI identity assigned during RRC connection establishment procedure. The UE shall transmit a
CELL UPDATE message on the uplink CCCH. Upon receiving such a message, the SS replies with an invalid CELL
UPDATE CONFIRM messageon downlink DCCH using UM RLC. The UE shall detect the protocol error and re-
transmit a CELL UPDATE message up to a maximum of N302 times. SS then transmit a valid CELL UPDATE
CONFIRM message. Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the
uplink DCCH to acknowledge the receipt of the new UE identities.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1057
Expected Sequence
UE SS
1 PAGING TYPE 1 The UE is in the CELL_PCH
state. SS pages for the UE
using the allocated connected
mode identity (U-RNTI).
2 CELL UPDATE Check that the value "paging
response" is set in IE "Cell
update cause".
3 CELL UPDATE CONFIRM See specific message content.
4 CELL UPDATE Check that the value "paging
response" is set in IE "Cell
update cause", the value
"protocol error" is set in IE
"failure cause" and the value
"Message extension not
comprehended" is set in IE
"Protocol error information".
CONFIRM

U-RNTI
Cell Update Cause Check to see if set to 'Paging Response'

Use the CELL UPDATE CONFIRM message as defined in [9] TS 34.108 clause 9, with the following exceptions:

U-RNTI
Failure cause Check to see if it is set to 'protocol error'
-Protocol error information Check to see if it is set to "Message extension not
comprehended"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1058
Use the same message sub-type titled "TM (Packet in PS)" in default message content of TS 34.108 with following
exceptions:
Page record list
- Paging record
- U-RNTI
- SRNC Identity '0000 0000 0001'
- S-RNTI '0000 0000 0000 0000 0001'

New C-RNTI '1010 1010 1010 1010'

After step 1 the UE shall transmit a CELL UPDATE message on the uplink CCCH, setting "paging response" into IE
After step 3 the UE shall transmit a CELL UPDATE message on the uplink CCCH, setting "paging response" into IE
"Cell update cause", "protocol error" into IE "failure cause" and "Message extension not comprehended" into IE
"Protocol error information".
using AM RLC.
8.3.1.14 Cell Update: Incompatible simultaneous reconfiguration

In case of a cell update procedure and if the received CELL UPDATE CONFIRM message
- includes "RB information elements"; and/or
- includes "Transport channel information elements"; and/or
- includes "Physical channel information elements"; and
- the variable ORDERED_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration
procedure;
and/or
- if the variable INCOMPATIBLE_SECURITY_RECONFIGURATION becomes set to TRUE of the received
CELL UPDATE CONFIRM message:
the UE shall:
2>if, caused by the received CELL UPDATE CONFIRM message

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1059
3>if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL
UPDATE CONFIRM message in case of a cell update procedure:
4>set the variable ORDERED_RECONFIGURATION to FALSE.
2>set the variable FAILURE_INDICATOR to TRUE;
2>set the variable FAILURE_CAUSE to "Incompatible simultaneous reconfiguration";
2>set the content of the CELL UPDATE message according to TS 25.331 subclause 8.3.1.3;
2>submit the CELL UPDATE message for transmission on the uplink CCCH;

Reference
3GPP TS 25.331 clause 8.3.1.9a
1. To confirm that the UE retransmits a CELL UPDATE message when it receives a CELL UPDATE CONFIRM
message that includes "Physical channel information elements" and UE's variable
ORDERED_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration procedure, before
the number of retransmissions has reached the maximum allowed value.
Initial Condition
Test Procedure
CELL UPDATE message on the uplink CCCH. Upon receiving such a message, the SS replies with a CELL UPDATE
CONFIRM message contains IE "Physical channel information elements". Following that, SS immediately transmits
another CELL UPDATE CONFIRM message contains IE "Physical channel information elements" before the
"activation time" indicated in the previous CELL UPDATE CONFIRM message expires. The UE shall re-transmit a
CELL UPDATE message with the same cause as the previous CELL UPDATE message and failure cause as
"Incompatible simultaneous reconfiguration". SS then transmits a CELL UPDATE CONFIRM message to end the
procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1060
Expected Sequence
UE SS
1 PAGING TYPE 1
2 CELL UPDATE
3 CELL UPDATE CONFIRM SS transmits this message
including IE "Physical channel
information elements".
4 CELL UPDATE CONFIRM Sent before the activation time
specified in the message in
step 3 has elapsed.
5 CELL UPDATE

U-RNTI

U-RNTI
Failure cause Check to see if set to 'Incompatible simultaneous
reconfiguration'



Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1061
exceptions:
Page record list
- Paging record
- U-RNTI
- SRNC Identity '0000 0000 0001'
- S-RNTI '0000 0000 0000 0000 0001'

After step 1, UE shall transmit a CELL UPDATE message.
After step 4 the UE shall re-transmit a CELL UPDATE message with failure cause set to "Incompatible simultaneous
reconfiguration".
8.3.1.15 Cell Update: Unrecoverable error in Acknowledged Mode RLC SRB



2>if the UE detects RLC unrecoverable error in an AM RLC entity:
3>perform cell update using the cause "RLC unrecoverable error".



1>if an unrecoverable error in any of the AM RLC entities for the signalling radio bearers RB2, RB3 or RB4 is
detected:
2>set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to TRUE.
1>otherwise:
2>set the IE "AM_RLC error indication (RB2, RB3 or RB4)" to FALSE.

When the UTRAN receives a CELL UPDATE/URA UPDATE message, the UTRAN should:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1062
1>initiate an RRC connection release procedure (see subclause 8.1.4 in TS 25.331) by transmitting an RRC
CONNECTION RELEASE message on the downlink CCCH. In particular UTRAN should:
2>if the CELL UPDATE message was sent because of an unrecoverable error in RB2, RB3 or RB4:
3>initiate an RRC connection release procedure by transmitting an RRC CONNECTION RELEASE
message on the downlink CCCH.
Reference
3GPP TS 25.331 clause 8.3.1.2, 8.3.1.3, 8.3.1.5
- To confirm that the UE reports the occurrence of an unrecoverable error in a C-plane AM RLC entity by
initiating cell update procedure.
- To confirm that UE enters idle mode state after receiving RRC CONNECTION RELEASE message on the
downlink CCCH.
Initial Condition
34.108, depending on the CN domain supported by the UE
The RRC CONNECTION SETUP message used in the initial setup should be as shown under Specific Message
Contents below.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1063
Test Procedure
The UE is initially in CELL_DCH state. SS sends a UE CAPABILITY ENQUIRY message on the DCCH using AM
mode. The UE shall reply with a UE CAPABILITY INFORMATION message, sent using AM RLC on the DCCH.
SS does not acknowledge the AM PDUs carrying this message. The UE shall continue to re-transmit the AM PDU
carrying UE CAPABILITY INFORMATION message until the maximum re-transmission count is reached.
Thereafter, the UE shall start sending RESET PDUs to request that the AM RLC entity for RRC signalling be re-
initialized. SS ignores all RESET PDUs from the UE.
At this point, the UE shall initiate a cell update procedure by transmitting a CELL UPDATE message on the uplink
CCCH. The CELL UPDATE message shall specify the value "TRUE" in IE "AM_RLC error indicator (RB2, RB3 or
RB4)" and "RLC unrecoverable error" as the cell update cause.
SS sends RRC CONNECTION RELEASE message on the downlink CCCH to UE. SS waits for 5 s and then calls for
generic procedure C.1 to check that UE is in idle mode state.
Expected Sequence
UE SS
1 The UE is initially in
CELL_DCH state.
2 UE CAPABILITY ENQUIRY
3 UE CAPABILITY INFORMATION SS does not acknowledge any
of the AM PDUs carrying the
UE CAPABILITY
INFORMATION message. The
UE shall re-transmit these AM
PDUs until the maximum
number has been reached.
4 UE shall start to transmit a
RESET PDU. SS does not
respond to any RESET PDU
frames originated from the UE.
5 CELL UPDATE IE "AM_RLC Error Indication
(RB2, RB3 or RB4)" shall be
set to 'TRUE'
6 RRC CONNECTION RELEASE Sends this message on the
downlink CCCH and includes
UE's UTRAN identity. After SS
sent this message, SS waits
for 5s.
otherwise it fails.

RRC CONNECTION SETUP (message used in the initial setup)
Use the same message type found in clause 9 of TS 34.108 with the following exception:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1064
Signalling RB information to setup (UM DCCH for RRC)
- RLC info
- CHOICE Uplink RLC mode UM RLC
- Transmission RLC discard Not Present
- CHOICE Downlink RLC mode UM RLC
- RB mapping info
- RLC size index According to TS34.108 clause 6.10.2.4.1.3 (standalone
13.6 kbps signalling radio bearer)
Signalling RB information to setup (AM DCCH for RRC)
- RLC info
- MAX_DAT 4
- Timer_RST 500
- Max_RST 1
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1065
- CHOICE RLC size list Configure
Signalling RB information to setup (AM DCCH for NAS_DT High priority)
- RLC info
- MAX_DAT 4
- Timer_RST 500
- Max_RST 1
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1066
Signalling RB information to setup (AM DCCH for NAS_DT Low priority)
- RLC info
- MAX_DAT 4
- Timer_RST 500
- Max_RST 1
- Polling info
- Timer_poll 200
- Poll_SDU 1
- Poll_Window 99
- RB mapping info
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1067

Use the same message found in TS 34.108 clause 9.
Only the message type IE is checked for this message.
U-RNTI
AM_RLC error indicator (RB2, RB3 or RB4) Check to see if set to 'TRUE'
Cell update cause Check to see if set to 'RLC unrecoverable error'

Use the same message found in TS 34.108 clause 9.
After step 4 the UE shall transmit a CELL UPDATE message on the uplink CCCH to report the occurrence of an
unrecoverable error in AM RLC entity for RB2, RB3 or RB4 data as well as cell update cause set to "RLC
unrecoverable error".
8.3.1.16 Void
8.3.1.17 Cell Update: Failure (UTRAN initiate an RRC connection release procedure
on CCCH)
1> or
CONNECTION RELEASE message on the downlink CCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1068
U_RNTI; or
the UE shall:


3>
3>enter idle mode;
Reference
3GPP TS 25.331 clause 8.3.1.5, 8.1.4.3
To confirm that the UE moves to idle state upon the reception of a RRC CONNECTION RELEASE message on
CCCH.
Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11)
Test Procedure
The UE is initially in CELL_FACH state. When the UE detects the expiry of periodic cell updating timer T305, the UE
transmits a CELL UPDATE message to the SS on the uplink CCCH to perform a periodical cell updating procedure.
The SS transmits a RRC CONNECTION RELEASE message on downlink CCCH. The UE shall return to idle mode
after release of all current signalling flows and radio access bearers. SS calls for generic procedure C.1 to check that UE
is in Idle Mode state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1069
Expected sequence
UE SS
update cause" and this
message shall be sent upon
2 RRC CONNECTION RELEASE SS transmits a RRC
CONNECTION RELEASE
message to the UE. After SS
sent this message SS waits for
5 seconds.
3 Void
4 Void
5 The UE shall enter idle mode
state.
otherwise it fails.

The same message found in Clause 9 of TS 34.108 shall be transmitted by the UE on the uplink CCCH, with the
exception of the following IEs:
U-RNTI
Cell Update Cause Check to see if set to 'Periodical cell update'

Use the same message sub-type found in Clause 9 of TS 34.108.
In step 1 the UE shall transmit a CELL UPDATE message on the uplink CCCH and set value "periodical cell update"
into IE "Cell update cause".
After step 4 the UE shall enter idle mode.
8.3.1.18 Cell Update: Radio Link Failure (T314>0, T315=0), CS RAB established


1>Paging response:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1070

met:
2>if the UE is in CELL_DCH state and the criteria for radio link failure is met as specified in TS 25.331
subclause 8.5.6:
3>perform cell update using the cause "radio link failure".

1>stop timer T305;
2>in the variable RB_TIMER_INDICATOR, set the IE "T314 expired" and the IE "T315 expired" to FALSE;
2>if the stored values of the timer T314 and timer T315 are both equal to zero; or
2>if the stored value of the timer T314 is equal to zero and there are no radio bearers associated with any radio
access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer"
is set to "useT315":

2>if the stored value of the timer T314 is equal to zero:

3>release all radio bearers associated with any radio access bearers for which in the variable
ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315";
3>in the variable RB_TIMER_INDICATOR set the IE "T315 expired" to TRUE.
2>if the stored value of the timer T314 is greater than zero:
3>if there are radio bearers associated with any radio access bearers for which in the variable
ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314":
4>start timer T314.
3>if there are no radio bearers associated with any radio access bearers for which in the variable
ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314" or "useT315":
4>start timer T314.

2>for the released radio bearer(s):
4>indicate local end release of the radio access bearer to upper layers using the CN domain identity
together with the RAB identity stored in the variable ESTABLISHED_RABS;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1071
1>set the variables PROTOCOL_ERROR_INDICATOR, FAILURE_INDICATOR,
UNSUPPORTED_CONFIGURATION and INVALID_CONFIGURATION to FALSE;
1>set the variable CELL_UPDATE_STARTED to TRUE;
1>if the UE is not already in CELL_FACH state:
2>move to CELL_FACH state;
2>use the transport format set given in system information as specified in TS 25.331 subclause 8.6.5.1.

If the received CELL UPDATE CONFIRM message would cause the UE to transit to CELL_DCH state:
1>if the UE failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM
message according to the criteria defined in subclause 8.5.4 in TS 25.331are not fulfilled; or

the UE shall:

1>if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE
CONFIRM message in case of a cell update procedure:
2>set the contents of the CELL UPDATE message according to TS 25.331 subclause 8.3.1.3, except for the IE
"Cell update cause" which shall be set to "Radio link failure";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1072

Reference
3GPP TS 25.331 clause 8.3.1.2, 8.3.1.7a
1. To confirm that the UE shall try to find a new cell after detecting that a radio link failure has occurred.
2. To confirm that the UE performs a cell selection procedure when it fails to configure the physical channel(s)
indicated in the CELL UPDATE CONFIRM message.
Initial Condition
System Simulator: 2 cells (Cell 1 and cell 2 are active).
UE: CS_DCCH+DTCH_DCH (state 6-9).
For SIB type 1 message to be transmitted throughout the test, use the message titled System Information Block type 1
(supported PLMN type is GSM-MAP) as found in TS 34.108 clause 6, with the following exception.
- T315 0

Test Procedure
Table 8.3.1.18
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
-75
-60
P-CCPCH
RSCP (TDD)
dBm -60 OFF
-75
-60

Column marked "T0" denote the initial conditions.
The UE is brought to CELL_DCH state in a cell 1 after making a successful outgoing call attempt. After the call has
been established, SS configures its downlink transmission power settings according to column "T1" in table 8.3.1.18.
The UE shall detect a radio link failure in cell 1.

Then it shall attempt to re-select to cell 2. After that, it shall transmit CELL UPDATE on the uplink CCCH to SS. The
SS transmits CELL UPDATE CONFIRM message which includes dedicated transport and physical channel parameters
on downlink DCCH. SS shall not configure according to this message. Instead, SS configures its downlink transmission
power settings according to column "T0" in table 8.3.1.18. UE shall fail to establish the dedicated channel in cell 2.
UE shall re-select to cell 1 and transmit a CELL UPDATE message with IE "Cell update cause" set to "Radio link
failure". Then SS responds with a CELL UPDATE CONFIRM message on downlink DCCH. Then the UE shall
transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1073
Expected sequence
UE SS
0 Void
1 Void
2 Void
3 Void
4 SS configures cell 1 and
2 according to column
"T1" in table 8.3.1.18. SS
starts to listen to the
uplink CCCH of cell 2.
5 Void
6 The UE detects the radio
link failure.
7 CELL UPDATE The UE shall find a new
cell 2 and the value "radio
link failure" shall be set in
8 CELL UPDATE CONFIRM Including dedicated
physical channel
parameters.
9 SS does not configure
according to the message
in step 8. SS configures
cell 1 and 2 according to
column "T0" in table
8.3.1.18.
10 CELL UPDATE UE shall select cell 1 and
transmit this message
12 TRANSPORT CHANNEL RECONFIGURATION
COMPLETE

U-RNTI
-SRNC Identity
- S-RNTI
Cell Update Cause

Check to see if set to value assigned in cell 1.
Check to see if set to 'radio link failure'
RB timer indicator
- T314 expired FALSE
- T315 expired TRUE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1074
UL Transport channel information common for all
transport channels
Same as the set defined in RADIO BEARER SETUP
message found in TS 34.108 clause 9 under condition
A1, A2, A7 or A8.
Added or Reconfigured TrCH information list Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
transport channels
Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
Added or Reconfigured TrCH information list Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
CHOICE channel requirement Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
Downlink information common for all radio links Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
Downlink information per radio link list Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.

U-RNTI
-SRNC Identity Check to see if set to value assigned in cell 1.
- S-RNTI Check to see if set to value assigned in cell 1.
Cell Update Cause Check to see if set to 'radio link failure'

After step 6, the UE shall detect the presence of cell 2, perform cell re-selection and transmit a CELL UPDATE
message.
After step 9, the UE shall transmit a CELL UPDATE message with IE "Cell update cause" set to "Radio link failure".
After step 11, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the
8.3.1.19 Void
8.3.1.20 Cell Update: Reception of CELL UPDATE CONFIRM Message that causes
invalid configuration

If the variable INVALID_CONFIGURATION is set to TRUE, the UE shall:
2>if, caused by the received CELL UPDATE CONFIRM message
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1075
3>if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL
UPDATE CONFIRM message in case of a cell update procedure:
3>set the variable FAILURE_INDICATOR to TRUE;
3>set the variable FAILURE_CAUSE to "Invalid configuration";

Reference
1. To confirm that the UE retransmits a CELL UPDATE message when it receives a CELL UPDATE CONFIRM
message that will trigger an invalid configuration in the UE, if the number of retransmissions has not reached the
maximum allowed value.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1076
Test Procedure
CELL UPDATE message on the uplink CCCH. Upon receiving such a message, the SS replies with a CELL UPDATE
CONFIRM message which is set to give an invalid configuration. The UE shall re-transmit CELL UPDATE message.
SS responds with a valid CELL UPDATE CONFIRM message to end the procedure. Then the UE shall transmit an
UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to acknowledge the receipt of the
new UE identities.
Expected Sequence
UE SS
1 PAGING TYPE 1 The UE is in the CELL_PCH
state. SS pages for the UE
using the allocated connected
mode identity (U-RNTI).
2 CELL UPDATE If CELL UPDATE message is
received, check that the value
"paging response" is set in IE
3 CELL UPDATE CONFIRM SS transmits an invalid
message.
4 CELL UPDATE IE "failure cause" is set to
"invalid configuration"
CONFIRM

U-RNTI

RRC State Indicator

CELL_DCH

Uplink DPCH info Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1077
U-RNTI
Failure cause Check to see if it is set to 'invalid configuration'

exceptions:
Page record list
- Paging record
- U-RNTI
- SRNC Identity '0000 0000 0001'
- S-RNTI '0000 0000 0000 0000 0001'

New C-RNTI '1010 1010 1010 1010'

After step 1 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response".
After step 3 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response" and
IE "failure cause" set to "invalid configuration".
using AM RLC.
8.3.1.21 Cell Update: Cell reselection to cell of another PLMN belonging to the
equivalent PLMN list

1.- Cell reselection:
- if none of the criteria for performing cell update with the causes specified above in the current clause is met;
and
- if the UE is in CELL_FACH or CELL_PCH state; and
- if the UE performs cell re-selection or the variable C_RNTI is empty:
- perform cell update using the cause "cell reselection".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1078
- The cell is part of the selected PLMN or, of a PLMN considered as equivalent by the UE according to the
- The cell is not barred.
- The cell is not part of the list of "forbidden LAs for roaming"
- The cell selection criteria are fulfilled.
3. The Mobile Equipment shall store a list of "equivalent PLMNs". This list is replaced or deleted at the end of
each location update procedure, routing area update procedure and GPRS attach procedure. The stored list
consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the network that
downloaded the list. The stored list shall not be deleted when the MS is switched off. The stored list shall be
deleted if the SIM is removed. The maximum number of possible entries in the stored list is six.
Reference
3GPP TS 25.331 clause 8.3.1.2.
3GPP TS 25.304 clause 4.3.
3GPP TS 24.008 clause 4.4.1.
1 To confirm that the UE executes a cell update procedure after a successful reselection to another UTRA cell with
a PLMN identity different from the original cell but with a PLMN identity that is part of the equivalent PLMN
list in the UE.
cell reselection.
NOTE: Verifies conformance requirement 1, 2 and 3.
3. To confirm that the UE refrains from executing a cell update procedure to a better UTRA cell with another
PLMN identity when that PLMN identity is not part of the equivalent PLMN list in the UE.
NOTE: Verifies conformance requirement 1, 2 and 3.
NOTE: Test case in 8.3.1.1 is a test where the UE reselects to a cell with the same PLMN identity as the
registered PLMN.
Initial Condition
System Simulator: 3 cells - Cell 1 is active, with the downlink transmission power shown in column marked "T0" in
table 8.3.1.21, while cell 2 and cell 3 is inactive.
UE: Shall have stored equivalent PLMN list containing PLMN-1 and PLMN-2. The equivalent PLMN list stored in the
UE shall not contain PLMN-3.
Test Procedure
The SS activates Cell 1-3 according table 8.3.1.21.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1079
Table 8.3.1.21
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
PLMN
identity
PLMN-1 PLMN-2 PLMN-3
CPICH Ec
(FDD)
dBm -60 -72 -72
Cell 2 is
switched
off
-60 -66
Cell 3 is
switched
off
Cell 3 is
switched
off
-60
P-CCPCH
RSCP (TDD)
dBm -62 -68 -62
Cell 2 is
switched
off
-62
-68 Cell 3 is
switched
off
Cell 3 is
switched
off
-62

Table 8.3.1.21-1 illustrates the downlink power to be applied for the 3 cells at various time instants of the test
execution. Columns marked "T0" denote the initial conditions, while columns marked "T1" and "T2" are to be applied
subsequently.

a) At T1, the SS activates Cell 2, and monitors Cell 2 for received messages from UE.
b) UE re-selects to Cell 2, and sends a CELL UPDATE. The SS shall reply with CELL UPDATE CONFIRM
message on downlink DCCH.
c) At T2, the SS activates Cell 3, and monitors Cell 3 for received messages from UE.
Expected sequence
UE SS
1 UE is camped on Cell 1 and
registered to PLMN1
2 CELL UPDATE At T1: Sent in Cell 2
The value "cell reselection" set
CONFIRM

5 At T2: No message sent by UE

Use the same message sub-type titled "CELL UPDATE CONFIRM message" in TS 34.108 clause 9 with following
exceptions:
- New C-RNTI

'1010 1010 1010 1010'

After step 1, the UE shall send a CELL UPDATE at T1.
After step 4, the UE shall refrain from sending a cell update (or any other message) after T2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1080
8.3.1.22 Cell update: Restricted cell reselection to a cell belonging to forbidden LA list
(Cell_FACH)

1. - Cell reselection:
- if none of the criteria for performing cell update with the causes specified above in the current clause is met;
and
- if the UE is in CELL_FACH or CELL_PCH state; and
- if the UE performs cell re-selection or the variable C_RNTI is empty:
- perform cell update using the cause "cell reselection".
- The cell is not barred.
- The cell is not part of the list of "forbidden LAs for roaming"
- The cell selection criteria are fulfilled.
3. The Mobile Equipment shall contain a list of "forbidden location areas for roaming", as well as a list of
"forbidden location areas for regional provision of service". These lists shall be erased when the MS is switched
off or when the SIM is removed, and periodically (with period in the range 12 to 24 hours). The location area
identification received on the BCCH that triggered the location updating request shall be added to the suitable
list whenever a location update reject message is received with the cause "Roaming not allowed in this location
area" or with the cause "Location Area not allowed". The lists shall accommodate each 10 or more location area
identifications. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted.
Reference
3GPP TS 25.331 clause 8.3.1.2.
3GPP TS 24.008 clause 4.4.1.
1. To confirm that the UE executes a cell update procedure after a successful reselection of another UTRA cell with
a LA identity that is not part of the list of LAs stored in the UE as "forbidden location areas for roaming".
2. To confirm that if the UE get a release message and is moved to idle mode, performs a location registration
where the LA list is updated and the UE again enters connected mode, that the UE refrains from selecting that
same UTRA cell if that is part of the forbidden LA list.
NOTE: Test case in 8.3.1.1 is a test where the UE reselects to a cell with the same LA identity as the LA identity
in the original cell.
NOTE: Test case in 8.1.3.2 is a test where normal RRC connection release on DCCH in CELL_FACH state is
tested.
NOTE: Test case in 8.1.9 is a test where normal RRC connection request and location registration is tested.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1081
Initial Condition
table 8.3.1.22, while cell 2 is inactive.
UE: Shall have an empty list of LAs stored that are "forbidden location areas for roaming". The UE shall be registered
to CS through cell 1 with LA-ID 1.
Test Procedure
Table 8.3.1.22
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
LA identity LA-ID 1 LA-ID 2
CPICH Ec
(FDD)
dBm -60 -66
Cell 2 is
switched off
-60
P-CCPCH
RSCP (TDD)
dBm -62 -68
Cell 2 is
switched off
-68

execution. Columns marked "T0" denote the initial conditions, while columns marked "T1"is to be applied
subsequently.
a) At T1, verify that the UE reselects to cell 2 and sends a cell update.
b) SS sends a RRC connection release message to the UE from cell2 on CCCH.
c) The UE performs a location registration to cell 2 (RRC Conection request, setup, initial direct transfer, DL direct
transfer (with LA forbidden for roaming), RRC connection release.)
d) The UE reselects cell 1 again although this is not the best cell.
e) The UE performs a location registration to cell 1 (RRC Conection request, setup, initial direct transfer, DL direct
transfer (without LA forbidden for roaming)).
f) Keep the UE in RRC Connected mode in CELL_FACH state.
g) Make sure the UE refrains from reselecting cell2 and sends a cell update (or any other message) in cell2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1082
Expected sequence
UE SS
1 CELL UPDATE At T1: Sent in Cell 2
The value "cell reselection" set
2 RRC CONNECTION RELEASE This message is sent on CCCH.
The value "Normal event" is set
in IE "Release cause"
3 Void
4 RRC CONNECTION REQUEST The value "Registration" is set in
IE "Establishment cause"
5 RRC CONNECTION SETUP Transits the UE to CELL_FACH
state.
7 INITIAL DIRECT TRANSFER Includes MM message
LOCATION UPDATING
REQUEST, or GMM message
ATTACH REQUEST.
8 DOWNLINK DIRECT TRANSFER Includes MM message
LOCATION UPDATING
REJ ECT, or GMM message
ATTACH with reject cause No
Suitable Cells In Location Area
9 RRC CONNECTION RELEASE This message is sent on DCCH.
COMPLETE
11 RRC CONNECTION REQUEST Sent in Cell 1.
The value "Registration" is set in
IE "Establishment cause"
12 RRC CONNECTION SETUP Transits the UE to CELL_FACH
state.
14 INITIAL DIRECT TRANSFER Includes MM message
LOCATION UPDATING
REQUEST, or GMM message
ATTACH REQUEST.
15 DOWNLINK DIRECT TRANSFER Includes MM message
LOCATION UPDATING
ACCEPT, or GMM message
ATTACH ACCEPT.

The same message found in Annex A shall be transmitted by the UE on the uplink CCCH, with the exception of the
following IEs:
U-RNTI
- SRNC Identity
- S-RNTI
Cell Update Cause

Check to see if set to '0000 0000 0001'
Check to see if set to '0000 0000 0000 0000 0001'
Check to see if set to 'cell reselection'

RRC CONNECTION RELEASE (Step 2, 9)
Use the same message sub-type found in TS34.108 clause 9.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1083
RRC CONNECTION RELEASE COMPLETE (Step 10)
Use the same message sub-type found in TS34.108 clause 9. Only the message type IE in this message will be checked.
RRC CONNECTION REQUEST (Step 4, 11)
RRC CONNECTION SETUP (Step 5, 12)
RRC CONNECTION SETUP COMPLETE (Step 6, 13)
INITIAL DIRECT TRANSFER (Step 7, 14)
DOWNLINK DIRECT TRANSFER (Step 8, 15)
In step 1, the UE shall send a CELL UPDATE in Cell 2 at T1 and attempt Location registration in Cell 2.
After step 2, the UE shall transmit RRC CONNECTION REQUEST message.
After step 5, the UE shall transmit RRC CONNECTION SETUP COMPLETE message, followed by an INITIAL
DIRECT TRANSFER message
Since the location registration is rejected in Cell 2, UE shall transmit RRC CONNECTION RELEASE COMPLETE
message after receiving RRC CONNECTION RELEASE message from SS. UE shall not send any more messages in
Cell 2.
After step 9, the UE shall transmit RRC CONNECTION REQUEST message in cell 1.
After step 12, the UE shall transmit RRC CONNECTION SETUP COMPLETE message followed by INITIAL
8.3.1.23 Cell Update: HCS cell reselection in CELL_FACH

1. The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised ranking
according to hierarchical cell re-selection rules shall apply, and is defined by:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1084
H
s
=Q
meas
,
s
- Qhcs
s
H
n
=Q
meas
,
n
- Qhcs
n

TO
n
* L
n

2. The cell-ranking criterion R is defined by:
R
s
=Q
meas
,
s
+Qhyst
s
R
n
=Q
meas
,
n
- Qoffset
s,n
- TO
n
* (1 L
n
)

where:
TOn =TEMP_OFFSETn * W(PENALTY_TIMEn Tn)
Ln =0 if HCS_PRIOn =HCS_PRIOs
Ln =1 if HCS_PRIOn <>HCS_PRIOs
W(x) =0 for x <0
W(x) =1 for x >=0

TEMP_OFFSET
n
applies an offset to the H and R criteria for the duration of PENALTY_TIME
n
after a timer T
n
has
started for that neighbouring cell.
The timer T
n
is implemented for each neighbouring cell. T
n
shall be started from zero when one of the following
conditions becomes true:
- if HCS_PRIO
n
<>HCS_PRIO
s
and
Q
meas
,
n
>Qhcs
n
Or
- if HCS_PRIO
n
=HCS_PRIO
s
and
- for serving FDD and neighbour FDD cells if the quality measure for cell selection and reselection is set to
CPICH RSCP in the serving cell, and:
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

CPICH Ec/No in the serving cell, and:
Q
meas,n
>Q
meas
,
s
+Qoffset2
s,n
- for all other serving and neighbour cells:
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

T
n
for the associated neighbour cell shall be stopped as soon as any of the above conditions are no longer fulfilled. Any
value calculated for TO
n
is valid only if the associated timer T
n
is still running else TO
n
shall be set to zero.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1085
At cell-reselection, a timer T
n
is stopped only if the corresponding cell is not a neighbour cell of the new serving cell, or
if the criteria given above for starting timer T
n
for the corresponding cell is no longer fulfilled with the parameters of
the new serving cell. On cell re-selection, timer T
n
shall be continued to be run for the corresponding cells but the
criteria given above shall be evaluated with parameters broadcast in the new serving cell if the corresponding cells are
neighbours of the new serving cell.

3. The cell selection criterion S used for cell reselection is fulfilled when:
for FDD cells: Srxlev >0 AND Squal >0
for TDD cells: Srxlev >0
for GSM cells: Srxlev >0

Where :
Squal =Q
qualmeas
Qqualmin
Srxlev =Q
rxlevmeas
- Qrxlevmin - Pcompensation

4. The UE shall perform ranking of all cells that fulfil the S criterion among
- all cells that have the highest HCS_PRIO among those cells that fulfil the criterion H >=0. Note that this rule is
not valid when UE high-mobility is detected.
- all cells, not considering HCS priority levels, if no cell fulfil the criterion H >=0. This case is also valid when it
is indicated in system information that HCS is not used, that is when serving cell does not belong to a
hierarchical cell structure.
The cells shall be ranked according to the R criteria.
The best ranked cell is the cell with the highest R value.
5. If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to CPICH
RSCP, the UE shall perform cell re-selection to that FDD cell.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:

6. The cell reselection process in Connected Mode is the same as cell reselection evaluation process used for idle
mode, described in subclause 5.2.6 of 25.304.
7. A UE shall initiate the cell update procedure in the following cases:

1>Paging response:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1086




1>Cell reselection:
met:
Reference
3GPP TS 25.304 clause 5.2.6.1.4
1. To confirm that the UE can read HCS related SIB information and act upon all HCS parameters in CELL_FACH
state.
2. To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell in
CELL_FACH state.
cell reselection.
Initial Condition
System Simulator: 3 cells Cell 1 is active with downlink transmission power shown in Column To in Table 8.3.1.23-
1. Cell 2 and 3 are switched off.
For system information blocks 4 and 11 for Cell 1 (gives IE's which are different from defaults given in 34.108 sec 6.1)
to be transmitted before idle update preamble.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1087
Contents of System Information Block type 4 (FDD)
- Cell selection and re-selection info
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- RAT List This parameter is configurable
- Slimit,SearchRAT Not Present
- Qqualmin -20 dB
- Qrxlevmin -115 dBm
- Qhyst1s 5 (gives actual value of 10 dB)
- Qhyst2s 0 dB
- HCS Serving cell information
-HCS Priority 6
- Q HCS 40 (results in actual value of 75)
- TcrMax Not Present

Contents of System Information Block type 4 (3.84 Mcps TDD and 1.28 Mcps TDD)
- CHOICE mode TDD
- SsearchHCS 47 dB
-HCS Priority 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1088
Contents of System Information Block type 11 (FDD) (Cell 1)
- SIB 12 indicator FALSE
- Measurement control system information
- Use of HCS used
- Intra-frequency measurement system
information

- Cell info
- Reference time difference to cell Not Present
- CHOICE mode FDD
in clause 6.1.4
- TX Diversity indicator FALSE
- Cell Selection and Re-selection info Not Present
- Cell info
- Read SFN indicator TRUE
- CHOICE mode FDD
in clause 6.1.4
- Cell Selection and Re-selection info
- Qoffset1
s,n
-20 dB
- Maximum allowed UL TX power 33 dBm
- HCS neighbouring cell information Present
- HCS_Priority 7
-Q_HCS 40 (results in actual value of 75)
-HCS Cell Reselection Information
- Penalty Time 40
-Temporary Offset inf
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1089

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1090
Contents of System Information Block type 11 (3.84 Mcps TDD and 1.28 Mcps TDD) (Cell 1)
- Use of HCS used
- Cell info
- CHOICE mode TDD
- Cell parameters ID Reference clause 6.1.4 in TS34.108: Default settings for
cell No.1 (TDD)
- Timeslot list Not Present
- Burst type Not Present
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1091
Test Procedure
Table 8.3.1.23-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
Cell id in
system
information
1 2 3
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
HCS
Priority
6 7 7
CPICH Ec
(FDD)
dBm
/3.8
4
MHz
-60 -60 -60 -80 -80 -70 -80 -70 -70
P-CCPCH
RSCP (TDD)
dBm -60 -60 -60 -80 -80 -70 -80 -70 -70
H* (During
penalty time)
15 15 5 -inf -inf 5 -inf -inf 5
H* (After
PenaltyTime)
15 15 15 -5 -5 5 -5 5 5
R* (During
PenaltyTime)
n.a. n.a. n.a. n.a. n.a. -50 n.a. n.a. -60
R* (After
PenaltyTime)
n.a. n.a. n.a. n.a. n.a. -50 n.a. n.a. -60

* this parameter is calculated internally in the UE and is only shown for clarification of the test procedure.

The UE is in the CELL_FACH state, camping onto cell 1. SS configures Cell 2 and 3 with power levels given in
column "TO" and starts to broadcast BCCH on the primary CCPCH in cell 2 & 3. UE shall remain camped on the Cell
1 even after expiry of penalty time i.e. 40 seconds. SS sets downlink transmission power settings according to columns
"T1" in table 8.3.1.23-1. The UE shall find cell 3 to be more suitable for service and hence perform a cell reselection to
cell 3 after at-least 40 Seconds (Penalty Time) after the power levels have been changed. After the completion of cell
reselection, the UE shall transmit a CELL UPDATE message to the SS on the uplink CCCH of cell 3 and set IE "Cell
update cause" to "Cell Reselection". After the SS receives this message, it transmits a CELL UPDATE CONFIRM
message, which includes the IE "RRC State Indicator" set to "CELL_FACH", to the UE on the downlink DCCH. Then
the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to
acknowledge the receipt of the new UE identities. UE shall stay in CELL_FACH state. SS then sets downlink
transmission power settings according to columns "T2" in table 8.3.1.23-1. The UE shall find cell 2 to be more suitable
for service and hence perform a cell reselection to cell 2 after the power levels have been changed. After the completion
of cell reselection, the UE shall transmit a CELL UPDATE message to the SS on the uplink CCCH of cell 2 and set IE
"Cell update cause" to "Cell Reselection". After the SS receives this message, it transmits a CELL UPDATE
CONFIRM message, which includes the IE "RRC State Indicator" set to "CELL_FACH", to the UE on the downlink
DCCH. Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink
DCCH to acknowledge the receipt of the new UE identities. UE shall stay in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1092
Expected sequence
UE SS
state in cell 1
2 BCCH SS applies the downlink
columns "T0" of table 8.3.1.23-
1. The SS starts to broadcast
BCCH on the primary CCPCH
in cell 2 and Cell 3. The UE
shall still find Cell 1 best for
service even after penalty time
of 40 seconds, and shall
remain in Cell 1 in
CELL_FACH State
3 SS changes the power levels
as per column 'T1' in the table
8.3.1.23-1. For the time equal
to Penalty time 40 Seconds,
after the change in power
levels, the UE shall still find
Cell 1 as best for service and
remain in cell 1. After Penalty
time of 40 Seconds, UE shall
find Cell 3 better for service
and perform a reselection. SS
camp to cell 3.
4 CELL UPDATE Value "cell reselection" shall
cause" Received in Cell 3
to "CELL_FACH".
CONFIRM

8.3.1.23-1. UE shall find Cell 2
better for service and perform
a reselection. SS waits for the
maximum duration required for
8 CELL UPDATE Received in Cell 2
to "CELL_FACH".
CONFIRM

The contents of system information block 4 and 11 messages are identical as system information block 4 and 11
messages as found in 34.108 clause 6.1 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1093
Contents of System Information Block type 4 (FDD) (Cell 2 and 3)
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- Qqualmin -20 dB
- Qhyst2s 0 dB
-HCS Priority 7

Contents of System Information Block type 4 (3.84 Mcps TDD and 1.28 Mcps TDD) (Cell 2 and 3)
- CHOICE mode TDD
- Sintersearch 0 dB
- SsearchHCS 47 dB
-HCS Priority 7

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1094
- Use of HCS used
information

- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1095

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1096
- Use of HCS used
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Cell info
- CHOICE mode TDD
- Cell parameters ID Reference clause 6.1.4 in TS 34.108: Default settings for
cell No.1 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1097
- Use of HCS used
information

- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1098

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1099
- Use of HCS used
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Cell info
- CHOICE mode TDD
cell No.1 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1100
CELL UPDATE

New C-RNTI '1010 1010 1010 1010'

After step 3 the UE shall reselect to cell 3 and then it shall transmit a CELL UPDATE message which, sets the value
"cell reselection" in IE "Cell update cause".
using AM RLC.
using AM RLC.
8.3.1.24 Cell Update: HCS cell reselection in CELL_PCH

1. The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised ranking
according to hierarchical cell re-selection rules shall apply, and is defined by:
H
s
=Q
meas
,
s
- Qhcs
s
H
n
=Q
meas
,
n
- Qhcs
n

TO
n
* L
n

R
s
=Q
meas
,
s
+Qhyst
s
R
n
=Q
meas
,
n
- Qoffset
s,n
- TO
n
* (1 L
n
)

where:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1101
W(x) =0 for x <0
W(x) =1 for x >=0

TEMP_OFFSET
n
n
after a timer T
n
has
The timer T
n
n
- if HCS_PRIO
n
<>HCS_PRIO
s
and
Q
meas
,
n
>Qhcs
n
Or
- if HCS_PRIO
n
=HCS_PRIO
s
and
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

Q
meas,n
>Q
meas
,
s
+Qoffset2
s,n
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

T
n
n
n
n
n
n
n


Where :
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1102
Squal =Q
qualmeas
Qqualmin
Srxlev =Q
rxlevmeas


7. A UE shall initiate the cell update procedure in the following cases:

1>Paging response:




1>Cell reselection:
met:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1103
Reference
3GPP TS 25.304 clause 5.2.6.1.4
1. To confirm that the UE can read HCS related SIB information and act upon all HCS parameters in CELL_PCH
state.
2. To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell in
CELL_PCH state.
cell reselection.
Initial Condition
System Simulator: 3 cells Cell 1 is active with downlink transmission power shown in Column To in table 8.3.1.24-1.
Cell 2 and 3 are switched off.
UE: CELL_PCH (state 6-12) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- Qqualmin -20 dB
- Qhyst2s 0 dB
-HCS Priority 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1104
- CHOICE mode TDD
- SsearchHCS 47 dB
-HCS Priority 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1105
- Use of HCS used
information

- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1106

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1107
- Use of HCS used
- Cell info
- CHOICE mode TDD
cell No.1 (TDD)
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1108
Test Procedure
Table 8.3.1.24-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
Cell id in
system
information
1 2 3
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
HCS Priority 6 7 7
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 -60 -60 -80 -80 -70 -80 -70 -70
P-CCPCH
RSCP (TDD)
dBm -61 -61 -61 -80 -80 -67 -80 -73 -73
H* (During
penalty time)
15 15 5 -inf -inf 5 -inf -inf 5
H* (After
PenaltyTime)
15 15 15 -5 -5 5 -5 5 5
R* (During
PenaltyTime)
n.a. n.a. n.a. n.a. n.a. -50 n.a. n.a. -60
R* (After
PenaltyTime)
n.a. n.a. n.a. n.a. n.a. -50 n.a. n.a. -60


The UE is in the CELL_PCH state, camping onto cell 1. SS configures Cell 2 and 3 with power levels given in column
"TO" and starts to broadcast BCCH on the primary CCPCH in cell 2 & 3. UE shall remain camped on the Cell 1 even
after expiry of penalty time i.e. 40 seconds. SS sets downlink transmission power settings according to columns "T1" in
table 8.3.1.24-1. The UE shall find cell 3 to be more suitable for service and hence perform a cell reselection to cell 3
after at-least 40 Seconds (Penalty Time) after the power levels have been changed. After the completion of cell
reselection, the UE shall move to CELL_FACH state and transmit a CELL UPDATE message to the SS on the uplink
CCCH of cell 3 and set IE "Cell update cause" to "Cell Reselection". After SS receives this message, it transmits a
CELL UPDATE CONFIRM message, which includes the IE "RRC State Indicator" set to "CELL_PCH", to the UE on
the downlink CCCH. UE shall return to CELL_PCH state in Cell 3 and will not transmit anything on PRACH. SS then
sets downlink transmission power settings according to columns "T2" in table 8.3.1.24-1. The UE shall find cell 2 to be
more suitable for service and hence perform a cell reselection to cell 2 after the power levels have been changed. After
the completion of cell reselection, the UE shall move to CELL_FACH state and transmit a CELL UPDATE message to
the SS on the uplink CCCH of cell 2 and set IE "Cell update cause" to "Cell Reselection". After the SS receives this
message, it transmits a CELL UPDATE CONFIRM message, which includes the IE "RRC State Indicator" set to
"CELL_PCH", to the UE on the downlink DCCH. UE shall return to CELL_PCH state in Cell 2 and will not transmit
anything on PRACH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1109
Expected sequence
UE SS
1 The UE is in the CELL_PCH
state in cell 1
2 BCCH SS applies the downlink
columns "T0" of table 8.3.1.24-
1. The SS starts to broadcast
BCCH on the primary CCPCH
in cell 2 and Cell 3. The UE
shall still find Cell 1 best for
service even after penalty time
of 40 seconds, and shall
remain in Cell 1 in CELL_PCH
State
8.3.1.24-1. For the time equal
to Penalty time 40 Seconds,
after the change in power
levels, the UE shall still find
Cell 1 as best for service and
remain in cell 1. After Penalty
time of 40 Seconds, UE shall
find Cell 3 better for service
and perform a reselection. SS
camp to cell 3.
CELL_FACH state and
to "cell reselection". Received
in Cell 3
5 CELL UPDATE CONFIRM Message sent on CCCH with
to "CELL_PCH".
8.3.1.24-1. UE shall find Cell 2
better for service and perform
a reselection. SS waits for the
maximum duration required for
CELL_FACH state and
to "cell reselection". Received
in Cell 2
9 CELL UPDATE CONFIRM Message sent on DCCH with
to "CELL_PCH".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1110
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- Qqualmin -20 dB
- Qhyst2s 0 dB
-HCS Priority 7

- CHOICE mode TDD
- Sintersearch 0 dB
- SsearchHCS 47 dB
-HCS Priority 7

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1111
- Use of HCS used
information

- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1112

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1113
- Use of HCS used
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Cell info
- CHOICE mode TDD
cell No.1 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1114

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1115
- Use of HCS used
information

- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- CHOICE mode FDD
in clause 6.1.4
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1116

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1117
- Use of HCS used
- Cell info
- CHOICE mode TDD
cell No.3 (TDD)
- Cell info
- CHOICE mode TDD
cell No.1 (TDD)
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
cell No.2 (TDD)
- Qoffset1
s,n
-20dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1118
CELL UPDATE


8.3.1.25 CELL UPDATE: Radio Link Failure (T314=0, T315=0)


1>Paging response:

met:
3>if the UE is in CELL_DCH state and the criteria for radio link failure is met as specified in TS 25.331
subclause 8.5.6; or



Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1119

3>indicate release (abort) of the established signalling connections (as stored in the variable
3>enter idle mode;
3>perform other actions when entering idle mode from connected mode as specified in TS 25.331 subclause
8.5.2;
Reference
3GPP TS 25.331 clause 8.3.1.2
1. To confirm that the UE releases all resources and enters idle mode when there is a radio link failure.
Initial Condition
System Simulator: 2 cells (Cell 1 and Cell 2 are active).
UE: PS-DCCH+DTCH_DCH (state 6-10) or CS-DCCH+DTCH_DCH (state 6-9) in cell 1 as specified in clause 7.4 of
TS 34.108, depending on the CN domain(s) supported by the UE. PS+CS-DCCH+DTCH_DCH (state 6-14) in cell 1, if
UE supports both CS and PS domains.
- T314 0
- T315 0

Test Procedure
Table 8.3.1.25
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
-75
-60
P-CCPCH
RSCP (TDD)
dBm -60 OFF
-75
-60

Column marked T0 denote the initial conditions.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1120
been established, SS configures its downlink transmission power settings according to column T1 in table 8.3.1.25.
The UE shall detect a radio link failure in cell 1 and indicate to the non-access stratum the release of all the radio
bearers. Then it shall attempt to re-select to cell 2. After that, it shall then enter idle mode state. SS calls for generic
procedure C.1 to check that UE is in Idle Mode state in cell 2.
Expected sequence
UE SS
1 In the initial set up
procedure, the SS shall
request UE to set timer
T314 and T315 to 0.
T1 in table 8.3.1.25.
3 SS waits for 5 seconds.
4 CALL C.1 SS execute this
procedure in cell 2. If the
test result of C.1
Idle Mode state, the test

None.
After step 2, the UE shall release all its radio bearers.
After step 3, the UE shall be in idle mode state in cell 2.

8.3.1.26 Cell Update: Radio Link Failure (T314>0, T315=0), PS RAB established


1>Paging response:

met; and
2>if the UE is in CELL_DCH state; and
2>if the criteria for radio link failure is met as specified in TS 25.331 subclause 8.5.6:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1121

1>stop timer T305;


3>release all radio bearers associated with any radio access bearers for which in the variable
4>start timer T314.
4>start timer T314.

1>set the variable CELL_UPDATE_STARTED to TRUE;
1>if the UE is not already in CELL_FACH state:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1122
2>select PRACH according to s TS 25.331 ubclause 8.5.17;
2>select Secondary CCPCH according to s TS 25.331 ubclause 8.5.19;
2>use the transport format set given in system information as specified in TS 25.331 subclause 8.6.5.1.

If the received CELL UPDATE CONFIRM message would cause the UE to transit to CELL_DCH state; and
1>in case of a received CELL UPDATE CONFIRM message:
2>if the UE failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM
message

the UE shall:
1>if the variable ORDERED_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE
CONFIRM message in case of a cell update procedure:
2>set the contents of the CELL UPDATE message according to TS 25.331 subclause 8.3.1.3, except for the IE
"Cell update cause" which shall be set to "Radio link failure";

Reference
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1123
1. To confirm that the UE shall indicate to the non-access stratum the release of radio access bearer which is
associated with T315 and try to find a new cell after detecting that a radio link failure has occurred.
Initial Condition
System Simulator: 2 cells (Cell 1 and cell 2 are active).
UE: PS_DCCH+DTCH_DCH (state 6-10) in cell 1 or PS+CS-DCCH+DTCH_DCH (state 6-14) in cell 1, if UE
supports both CS and PS domains.
- T315 0

Test Procedure
Table 8.3.1.26
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
-75
-60
P-CCPCH
RSCP (TDD)
dBm -60 OFF
-75
-60

Column marked "T0" denote the initial conditions.
been established, SS configures its downlink transmission power settings according to column "T1" in table 8.3.1.26.
UE shall release of the radio bearer which is associated with T315, if the latter has been set up in the initial condition.
Then it shall attempt to re-select to cell 2. After that, it shall then enter CELL_FACH state and transmit CELL
UPDATE on the uplink CCCH to SS. The SS transmits CELL UPDATE CONFIRM message which includes dedicated
physical channel parameters on downlink DCCH. Then the UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH.
SS transmits COUNTER CHECK message to UE. UE shall transmit a COUNTER CHECK RESPONSE message back
to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1124
Expected sequence
UE SS
"T1" in table 8.3.1.26. SS
starts to listen to the
uplink CCCH of cell 2.
2 The UE detects the radio
link failure.
3 CELL UPDATE The UE shall find a new
cell 2 and the value "radio
link failure" shall be set in
4 CELL UPDATE CONFIRM Including dedicated
physical channel
parameters.
COMPLETE

6 COUNTER CHECK SS sent the COUNT-C
info for the RBs that were
established in the initial
condition.
7 COUNTER CHECK RESPONSE

U-RNTI
-SRNC Identity
- S-RNTI
Cell Update Cause

Check to see if set to 'radio link failure'
RB timer indicator
- T315 expired TRUE

If the initial condition of the UE is in state 6-10, then
CHOICE channel requirement Same as the set defined in RRC CONNECTION SETUP
message: UM (Transition to CELL_DCH) found in TS
34.108 clause 9.
Downlink information common for all radio links Same as the set defined in RRC CONNECTION SETUP
34.108 clause 9.
Downlink information per radio link list Same as the set defined in RRC CONNECTION SETUP
34.108 clause 9.

If the initial condition of the UE is in state 6-14, then
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1125
CHOICE channel requirement Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
Downlink information common for all radio links Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.
Downlink information per radio link list Same as the set defined in RADIO BEARER SETUP
A1, A2, A7 or A8.

Message Type
Integrity check info Calculated value
- RB identity Set to the RB identity that was release by the UE upon
radio link failure
- COUNT-C MSB uplink Arbitrary COUNT-C MSB
- COUNT-C MSB downlink Arbitrary COUNT-C MSB

Message Type
- RB identity Check to see if set to the RB identity that was
release by the UE upon radio link failure
- COUNT-C uplink Check to see if COUNT-C MSB is set to arbitrary
value given in step 13 and LSB is fill with '0'
- COUNT-C downlink Check to see if COUNT-C MSB is set to arbitrary
value given in step 13 and LSB is fill with '0'

message.
After step 6, the UE shall transmit a COUNTER CHECK RESPONSE message with the MSB part of the COUNT-C
values set identical to COUNT-C MSB values in the COUNTER CHECK message in step 6.

8.3.1.27 Cell Update: Radio Link Failure (T314=0, T315>0), CS RAB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1126

1>Paging response:

met; and

1>stop timer T305;

3>enter idle mode;
3>perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1127

Reference
1. To confirm that the UE release radio access bearer which is associated with T314 and try to find a new cell after
detecting that a radio link failure has occurred.
Initial Condition
- T314 0

Test Procedure
Table 8.3.1.27
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
-75
-60
P-CCPCH
RSCP (TDD)
dBm -60 OFF
-75
-60

The UE shall release radio bearer associated with T314 and enter idle mode state. SS calls for generic procedure C.1 to
check that UE is in Idle Mode state in cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1128
Expected sequence
UE SS
1 SS configures cell 1
and 2 according to
column T1 in table
8.3.1.27. SS starts to
listen to the uplink
CCCH of cell 2.
2 The UE detects the
radio link failure.
procedure in cell 2. If
the test result of C.1
Idle Mode state, the
test passes. Otherwise
it fails.

None.
After step 2, the UE shall detect the presence of cell 2 and enter idle mode state in cell 2.

8.3.1.28 Cell Update: Radio Link Failure (T314=0, T315>0), PS RAB


1>Paging response:

met; and

1>stop timer T305;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1129

3>release all radio bearers, associated with any radio access bearers for which in the variable

4>start timer T315.

Reference
1. To confirm that the UE release radio access bearer which is associated with T314 and try to find a new cell after
detecting that a radio link failure has occurred.
Initial Condition
UE: PS_DCCH+DTCH_DCH (state 6-10) in cell 1 or PS+CS-DCCH+DTCH_DCH (state 6-14) in cell 1, if UE
supports both CS and PS domains.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1130
- T314 0

Test Procedure
Table 8.3.1.28
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
-75
-60
P-CCPCH
RSCP (TDD)
dBm -60 OFF
-75
-60

The UE shall attempt to re-select to cell 2. After that, it shall then enter CELL_FACH state and transmit CELL
UPDATE on the uplink CCCH to SS. The SS transmits CELL UPDATE CONFIRM message which includes dedicated
physical channel parameters on downlink DCCH. Then the UE shall transmit a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH. SS transmits COUNTER CHECK message to UE.
UE shall transmit a COUNTER CHECK RESPONSE message back to SS.
Expected sequence
UE SS
and 2 according to
column T1 in table
8.3.1.28. SS starts to
listen to the uplink
CCCH of cell 2.
2 The UE detects the
radio link failure.
3 CELL UPDATE The UE shall find a
new cell 2 and the
value "radio link failure"
shall be set in IE "Cell
update cause".
COMPLETE

info for the RBs that
were established in the
initial condition.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1131
U-RNTI
- S-RNTI Check to see if set to value assigned in cell
1.
- SRNC Identity Check to see if set to value assigned in cell
1.
RB timer indicator
- T314 expired TRUE

CHOICE channel requirement Same as the set defined in RADIO BEARER
SETUP message found in TS 34.108 clause 9
under condition A4.
Downlink information common for all radio links Same as the set defined in RADIO BEARER
under condition A4.
Downlink information per radio link list Same as the set defined in RADIO BEARER
under condition A4.

Message Type
- RB identity Set to the RB identity that was set up in the initial
condition
- COUNT-C MSB uplink Set to the value stored in the SS
- COUNT-C MSB downlink Set to the value stored in the SS

Message Type
RB COUNT-C information Not present

message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1132
After step 7, the UE shall transmit a COUNTER CHECK RESPONSE message without including IE RB COUNT-C
information.

8.3.1.29 Cell Update: Radio Link Failure (T314>0, T315>0), CS RAB


1>Paging response:

met; and



4>start timer T314.
4>start timer T314.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1133
4>start timer T315.

Upon expiry of timer T314 the UE shall:
1>if timer T302 is running:

1>if timer T302 is not running and timer T315 is running:
2>set IE "T314 expired" in variable RB_TIMER_INDICATOR to TRUE;
2>release locally all radio bearers which are associated with any radio access bearers for which in the variable
2>indicate release of those radio access bearers to upper layers;
2>delete all information about those radio access bearers from the variable ESTABLISHED_RABS.
1>if timers T302 and T315 are not running:
2>clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO;
2>clear the variable PDCP_SN_INFO;
variable TRANSACTIONS;
2>enter idle mode;
2>other actions the UE shall perform when entering idle mode from connected mode are specified in subclause
8.5.2;

ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "use T315";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1134
2>enter idle mode;
8.5.2;
Reference
2. To confirm that the UE enters idle mode after T314 expires and T302 and T315 are not running.
Initial Condition
System Simulator: 1 cell (Cell 1 is active).
- T314 12
- T315 30

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1135
Test Procedure
Table 8.3.1.29
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
P-CCPCH
RSCP (TDD)
dBm -60 OFF

The UE is brought to CELL_DCH state after making a successful outgoing call attempt. After the call has been
established, SS configures its downlink transmission power settings according to column T1 in table 8.3.1.29. The UE
shall detect a radio link failure in cell 1.
The SS shall wait for 12s (see Note 1) and then configure its downlink transmission power settings according to column
T0 in table 8.3.1.29. The UE shall release radio bearer associated with T314 and enter idle mode state. SS calls for
generic procedure C.1 to check that UE is in Idle Mode state in cell 1.
NOTE 1: Considering the timer tolerance of the UE, T314 may expire between 12s0.3s, therefore the SS must
wait for at least 12.3s before it reconfigures it downlink transmission power. Since SS has a timer
tolerance of 10% or 2*TTI+55ms (consider the greater value of the two), the test case shall set the SS to
reconfigure the power level 13.67s after the SS configures the power settings according to column T1 in
table 8.3.1.29.
Expected sequence
UE SS
according to column T1
in table 8.3.1.29.
2 SS waits for 12s after the
completion of step 1 and
then configures cell 1
in table 8.3.1.29.
test result of C.1
passes. Otherwise it fails.

None.

8.3.1.30 Cell Update: Radio Link Failure (T314>0, T315>0), PS RAB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1136

1>Paging response:

met; and



4>start timer T314.
4>start timer T314.
4>start timer T315.


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1137
2>enter idle mode;
8.5.2;

ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "use T315";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1138
2>enter idle mode;
8.5.2;
Reference
associated with T314 and try to find a new cell after detecting that a radio link failure has occurred. (This test
purpose is only applicable when CS RAB is set up in the initial condition.)
3. To confirm that the UE enters idle mode after T315 expires and T302 and T314 are not running.
Initial Condition
System Simulator: 1 cell (Cell 1 is active).
UE: PS_DCCH+DTCH_DCH (state 6-10 or PS+CS-DCCH+DTCH_DCH (state 6-14), if UE supports both CS and PS
domains.
- T314 12
- T315 30

Test Procedure
Table 8.3.1.30
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec
(FDD)
dBm/3.84MHz -60 OFF
P-CCPCH
RSCP (TDD)
dBm -60 OFF

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1139
The UE is brought to CELL_DCH state after making a successful outgoing call attempt. After the call has been
established, SS configures its downlink transmission power settings according to column T1 in table 8.3.1.30. The UE
shall detect a radio link failure in cell 1.
Case A (the initial condition of the UE is in state 6-10):
The SS shall wait for 46s (see Note 2) and then configure its downlink transmission power settings according to column
T0 in table 8.3.1.30. The UE shall release radio bearer associated with T315 and enter idle mode state. SS calls for
generic procedure C.1 to check that UE is in Idle Mode state in cell 1.
Case B (the initial condition of the UE is in state 6-14):
The SS shall wait for 12s (see Note 1) and then configure its downlink transmission power settings according to
column T0 in table 8.3.1.30. The UE shall release radio bearer associated with T314 and attempt to re-select to cell 1.
After that, it shall then enter CELL_FACH state and transmit CELL UPDATE on the uplink CCCH to SS. The SS
transmits CELL UPDATE CONFIRM message which includes dedicated physical channel parameters on downlink
DCCH. Then the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
uplink DCCH. SS transmits COUNTER CHECK message to UE. UE shall transmit a COUNTER CHECK RESPONSE
message back to SS. Then SS configures its downlink transmission power settings according to column T1 in table
8.3.1.30. The UE shall detect a radio link failure in cell 1. The SS shall wait for 46s (see Note 2) and then configure its
downlink transmission power settings according to column T0 in table 8.3.1.30. The UE shall release radio bearer
associated with T315 and enter idle mode state. SS calls for generic procedure C.1 to check that UE is in Idle Mode
state in cell 1.
table 8.3.1.30.
table 8.3.1.30.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1140
Expected sequence
UE SS
in table 8.3.1.30.
2 For Case A, go to step 9.
SS waits for 12s after the
in table 8.3.1.30.
3 CELL UPDATE UE shall select cell 1 and
enter CELL_FACH state
to transmit this message
COMPLETE

info for the RBs that were
established in the initial
condition.
in table 8.3.1.30.
9 SS waits for 46s after the
in table 8.3.1.30.
test result of C.1
passes. Otherwise it fails.

U-RNTI
- S-RNTI Check to see if set to value assigned in cell
1.
- SRNC Identity Check to see if set to value assigned in cell
1.
RB timer indicator
- T314 expired TRUE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1141
CHOICE channel requirement Same as the set defined in RADIO BEARER
under condition A4.
Downlink information common for all radio links Same as the set defined in RADIO BEARER
under condition A4.
Downlink information per radio link list Same as the set defined in RADIO BEARER
under condition A4.

Message Type
- RB identity Set to the RB identity that was set up in the initial
condition and support PS service.
- COUNT-C MSB uplink Set to the value stored in the SS
- COUNT-C MSB downlink Set to the value stored in the SS

Message Type
RB COUNT-C information Not present

Case A:

Case B:
message.
After step 7, the UE shall transmit a COUNTER CHECK RESPONSE message without including IE RB COUNT-C
information.

8.3.1.31 Cell Update: re-entering of service area from URA_PCH after T316 expiry but
before T317 expiry

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1142
If the UE detects the "out of service area" and the UE is in URA_PCH or CELL_PCH state it shall perform the
following actions:
1>start timer T316;
1>perform processes described in subclause 7.2.2.
.
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":
.
1>if the UE is "out of service area":
2>perform cell selection process as specified in [4];
2>run timer T316;
2>run timer T305.
.
On T316 expiry the UE shall perform the following actions. The UE shall:
1>if "out of service area" is detected:
2>start timer T317;
1>if "in service area" is detected:
.
If the UE detects "in service area" before T317 expiry the UE shall perform the following actions. If no cell update
procedure or URA update procedure is ongoing, the UE shall:
1>stop T317;
1>if T307 is active:
2>stop T307.
1>initiate the cell update procedure using as cause "Re-entering service area" as specified in subclause 8.3.1;
If a cell update procedure or URA update procedure is ongoing, the UE shall:
1>stop T317;
1>perform the actions as specified in 8.3.1.
Reference
3GPP TS 25.331 clause 8.3.1, 8.5.5.1.1, 8.5.5.2.2, 8.5.5.3, 7.2.2.1, and 7.2.2.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1143
To confirm that the UE executes a cell update procedure when the UE re-enters the service area before the expiry of
timer T317, after expiry of T316.
Initial Condition
System Simulator: 1 cell with URA-ID 1 and the downlink transmission power shown in column marked "T0" in table
8.3.1.31.
UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108, with URA-ID 1 in the list of URA-ID.
Test Procedure
Table 8.3.1.31
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec dBm/3.84MHz -60 -80
P-CCPCH
RSCP (TDD)
dBm -60 -80

The UE is initially in URA_PCH state. The content of the SYSTEM INFORMATION BLOCK TYPE 3 and 4 is
modified. The SS configures its downlink transmission power settings according to columns "T1" in table 8.3.1.31 so
that S<0. When the UE detects that it is out of service area, it will start T316 and search for a cell to camp. SS
configures its downlink transmission power settings according to columns "T0" in table 8.3.1.31 within a time
equivalent to T316+T317 but larger than T316, so that S>0. The UE shall detect that it returns back in service area
before T317 expires. Since the UE has moved to CELL_FACH state on expiry of T316, it shall now transmit a CELL
UPDATE message which contains the value "re-entering service area" in IE "Cell update cause" to the SS on the uplink
CCCH. After the SS receives this message, it transmits a CELL UPDATE CONFIRM message which includes the IE
"new C-RNTI", and "new U-RNTI" to the UE on the downlink DCCH. Then the UE shall transmit an UTRAN
MOBILITY INFORMATION CONFIRM message on the uplink DCCH.
Expected sequence
UE SS
1 The UE starts operating from
URA_PCH state.
and 4
MASTER INFORMATION
BLOCK and SYSTEM
1b PAGING TYPE 1 Include IE "BCCH modification
info"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1144
void
void
table 8.3.1.31 such that the
cell 1 is no longer suitable for
camping i.e. S<0.
3 The UE shall detect a "out of
service area" condition, start
T316. The UE shall start T317
on expiry of T316)
4 60 seconds after step 2 (see
note 1), the SS configures its
settings according to columns
"T0" in table 8.3.1.31 before
T317 expires.
5 CELL UPDATE Value "re-entering service
area" shall be set in IE "Cell
update cause"

CONFIRM

NOTE: The 60 seconds in step 4 should be large enough for any UE to have detected the out of service area
condition (Nserv consecutive DRX cycles +12s) and have started T317 after T316 expiry (default=30s),
but well before T317 expiry (default =180s).
MIB Tag 2
Scheduling information - Scheduling info for System Information Type 3
- Cell Value tag 2
- Cell Value tag 2

Qrxlevmin -70

PAGING TYPE 1 (Step 1b)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1145
MIB Value tag 2
BCCH modification time Not present

URA UPDATE (Step 1c)
U-RNTI
- SRNC Identity
- S-RNTI
URA Update Cause

Check to see if set to '0000 0000 0001'
Check to see if set to '0000 0000 0000 0000 0001'
Check to see if set to 'periodical URA update'

URA UPDATE CONFIRM (Step 1d)
Use the same message sub-type found in Clause 9 of TS 34.108, with the following exceptions:

U-RNTI
Cell Update Cause Check to see if set to 're-entering service area'

Use the same message sub-type found in TS 34.108 clause 9, with the exception of the following IEs:
New U-RNTI
- SRNC Identity '0000 0000 0001'
- S-RNTI '0000 0000 0000 0101 0101'
New C-RNTI '1010 1010 1010 1010'

The same message found in TS 34.108 clause 9 shall be transmitted by the UE.
After step 2 the UE shall detect that it is out of service area and shall not send a URA UPDATE on the uplink CCCH
channel.
After step 4 the UE shall transmit a CELL UPDATE message which sets value "re-entering service area" into IE "Cell
update cause".
After step 6 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1146
8.3.2 URA Update
8.3.2.1 URA Update: Change of URA

A UE in URA_PCH state shall initiate the URA update procedure in the following cases:
1>URA reselection:
2>if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not
present in the list of URA identities in system information block type 2; or
2>if the list of URA identities in system information block type 2 is empty; or
2>if the system information block type 2 can not be found:

3>perform URA update using the cause "change of URA".
When initiating the URA update procedure, the UE shall:
1>stop timer T305;
1>in case of a URA update procedure:
2>set the contents of the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;
2>submit the URA UPDATE message for transmission on the uplink CCCH.
In case of URA update procedure the UE shall transmit a URA UPDATE message.
The UE shall set the IEs in the URA UPDATE message as follows:
1>set the IE "URA update cause" corresponding to which cause as specified in TS 25.331 subclause 8.3.1.2 that is
valid when the URA UPDATE message is submitted to lower layers for transmission;

2>if the value of the variable PROTOCOL_ERROR_INDICATOR is FALSE:
3>if the value of the variable INVALID_CONFIGURATION is TRUE:

3>if the value of the variable INVALID_CONFIGURATION is FALSE:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1147
4>set the IE "Protocol error indicator" to FALSE.
If the URA UPDATE CONFIRM message:
- does not include the IE "New U-RNTI"; and
- does not include the IE "New C-RNTI":
the UE shall:


- reselection to another UTRA cell (including the previously serving cell) before completion of the cell update or
URA update procedure;
the UE shall:

1>check whether it is still in "in service area" (see TS 25.331 subclause 8.5.5.2);

2>clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the

2>if the UE performed cell re-selection:
3>delete its C-RNTI.

3>set the contents of the URA UPDATE message according to TS 25.331 subclauses 8.3.1.3 and 8.5.10;
3>if a URA UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the
variable CIPHERING_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable
INTEGRITY_PROTECTION_INFO is set to TRUE:


The UE shall:
1>if the IE "URA identity" is included in a received message:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1148
2>if the IE "RRC State Indicator" is included and set to "URA_PCH":
3>store this URA identity in the variable URA_IDENTITY;
3>after sending a possible message to UTRAN and entering URA_PCH state as specified elsewhere, read
system information block type 2 in the selected cell;
3>if the stored URA identity in the variable URA_IDENTITY is not included in the list of URA identities in
System Information Block type 2 in the selected cell, the list of URA identities in system information
block type 2 is empty or if the system information block type 2 can not be found, a confirmation error of
URA identity list has occurred:
4>if no URA update procedure is ongoing:

4>if a URA update procedure is ongoing:
5>take actions as specified in TS 25.331 subclause 8.3.1.10.
If the URA UPDATE CONFIRM message causes a confirmation error of URA identity list as specified in TS 25.331
subclause 8.6.2.1 the UE shall:
1>if V302 is smaller or equal than N302:

2>set the IEs in the URA UPDATE message according to TS 25.331 subclause 8.3.1.3;
2>submit the URA UPDATE message for transmission on the uplink CCCH;

Reference
3GPP TS 25.331 clause 8.3.1.2, 8.3.1.12, 8.6.2.1
1. To confirm that the UE executes an URA update procedure after the successful change of URA.
2. To confirm that the UE performs an URA update procedure after it detects that SIB 2 is not broadcasted.
3. To confirm that the UE performs an URA update procedure after it detects a confirmation error of URA identity
list.
Initial Condition
System Simulator: 2 cells: The URA-ID and transmission power for each cell is shown in Table 8.3.2.1, where the
initial condition is shown in column "T0".
UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108, with URA-ID 1 from the list of URA-ID in cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1149
Test Procedure
T0 T1 T2 T3 T4 T5 T6 T7 T0 T1 T2 T3 T4 T5 T6 T7
UTRA RF
Channel
Number

Ch. 1

Ch. 1
CPICH Ec dBm/3.
84MHz
-60 -75 -60 -75 -60 -75 -75 -60 -75 -60 -75 -60
P-CCPCH
RSCP
(TDD)
dBm -60 -75 -60 -75 -60 -75 -75 -60 -75 -60 -75 -60
URA ID URA-ID
1
URA-ID 2 URA-ID 1,3 and 4 no SIB2

The test begins with the downlink power transmission of both cells set according to 'T0' column in table 8.3.2.1. The
UE is in the URA_PCH state and assigned with only 1 URA identity in cell 1: URA-ID 1. The SS then adjusts the
transmission power again according to the 'T1' column. This is expected to cause the UE to perform a cell reselection to
cell 2. Since URA-ID 1 is also broadcasted in cell 2, the UE shall not perform any URA update procedure due to the
change of URA. Starting from time 'T2', SS modifies the system information in cell 1, so that URA-ID 2 is the only
URA identity in that cell. Next SS adjusts the transmission power according to 'T3' column. UE shall perform a cell
reselection to cell 1 and when the UE finds that its current URA-ID 1 is not in the new broadcasted list of URA-IDs, it
moves to CELL_FACH state and transmits a URA UPDATE message on the uplink CCCH. After the SS receives this
message, it transmits a URA UPDATE CONFIRM message, which includes the IEs "RRC State Indicator" and IE
"URA-ID" to the UE on the downlink CCCH. The IE "RRC State Indicator" is set to "URA_PCH". UE returns to
URA_PCH state in cell 1 without sending any uplink response message. Next SS adjusts the transmission power
according to 'T4' column. UE shall re-select to cell 2 and transmit a URA UPDATE message to SS. However, SS do not
acknowledge but adjusts the transmission power according to 'T5' column. UE shall perform cell re-selection to cell 1
and then send a URA UPDATE message to SS. SS shall transmit URA UPDATE CONFIRM message to UE on the
downlink CCCH. Starting from time 'T6', SS modifies the system information in cell 2, so that no SIB 2 is sent in that
cell. Next the SS adjusts the transmission power according to the 'T7' column. The UE shall re-select to cell 2 and send
a URA UPDATE message since no SIB2 is broadcasted in this cell. When the UE receives a URA UPDATE
CONFIRM message including a URA identity, the UE will again send a URA UPDATE message. When receiving this
last message, the SS shall transmit RRC Connection Release message on downlink CCCH to release the RRC
connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1150
Expected sequence
UE SS
1 The UE is updated with only 1
URA identity carried currently
by cell 1. The starting state of
the UE is URA_PCH
2 SS set the power transmission
and system information of all
cells according to column 'T1'
of table 8.3.2.1.
3 UE shall perform a cell
reselection but shall not
transmit URA UPDATE
message with the update
cause of "change of URA".
3a Starting from time 'T2', SS
modifies the system
information in cell 1, so that
URA-ID 2 is the only URA
identity in that cell
of table 8.3.2.1.
5 URA UPDATE The UE shall perform a cell
reselection first and when it
finds that its current URA-ID 1
is not in the newly
broadcasted list of URA-IDs, it
shall then transmit this
message and set value
"change of URA" into IE "URA
update cause".
6 URA UPDATE CONFIRM Message comprises IE "RRC
State Indicator" set to
"URA_PCH", and also IE
"URA Identity" equal to "URA-
ID 2".
of table 8.3.2.1.
8 URA UPDATE
9 SS do not respond to the URA
UPDATE message from UE
and set the power
transmission and system
information of all cells
according to column 'T5' of
table 8.3.2.1.
10 URA UPDATE
11 URA UPDATE CONFIRM
11a Starting from time 'T6', SS
modifies the system
information in cell 2, so that no
SIB 2 is sent in that cell.
and system informatio of all
of table 8.3.2.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1151
reselection first and when it
finds that no URA-ID is
broadcasted in this cell, it shall
then transmit this message
and set value "change of
URA" into IE "URA update
cause".
14 URA UPDATE CONFIRM Message comprises IE "RRC
State Indicator" set to
"URA_PCH", and also IE
"URA Identity" equals to
"URA-ID 2".
15 URA UPDATE
16 RRC CONNECTION RELEASE This message is sent on
CCCH.
17 Void
18 UE enters idle mode

Use the same message sub-type found in clause 6.1 of TS 34.108, with the following exceptios.
Cell 1, time T0-T1:
- URA identity list
- URA identity 0000 0000 0000 0001B

Cell 2, time T0-T5:
- URA identity list
- URA identity 0000 0000 0000 0011B
- URA identity 0000 0000 0000 0001B
- URA identity 0000 0000 0000 0100B

Cell 1, time T2-T7 (step 3a):
- URA identity list
- URA identity 0000 0000 0000 0010B

Cell 2, time T6-T7 (step 11a):
No SYSTEM INFORMATION BLOCK TYPE 2 is broadcasted in cell 2 during this time period.

URA UPDATE (Step 5, 8, 10, 13, and 15)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1152
U-RNTI
URA Update Cause Check to see if set to 'change of URA'

URA UPDATE CONFIRM (Step 6, 11 and 14)

After step 2 the UE shall not transmit a URA UPDATE message with update cause "change of URA".
After step 4 the UE shall find that URA-ID 2 is not in its maintained list of URA-IDs. After cell reselection, the UE
shall move to CELL_FACH state and transmit a URA UPDATE message setting value "change of URA" into IE "URA
update cause".
shall move to CELL_FACH state and a transmit URA UPDATE message setting value "change of URA" into IE "URA
update cause".
After step 9 the UE shall find the new cell and transmit a URA UPDATE message setting value "change of URA" into
IE "URA update cause".
After step 12 the UE shall find that no URA-ID is broadcasted in the cell, move to CELL_FACH state and transmit a
URA UPDATE message setting the update cause to "change of URA".
After step 14 the UE shall find that no URA-ID is broadcasted in the cell and transmit a URA UPDATE message setting
the update cause to "change of URA".
8.3.2.2 URA Update: Periodical URA update and Reception of Invalid message

A UE in URA_PCH state shall initiate the URA update procedure in the following cases:
1>URA reselection:

1>Periodic URA update:
2>if the criteria for performing URA update with the causes as specified above in the current subclause are not
met; and
2>if the timer T305 expires while the UE is in the service area; and
3>perform URA update using the cause "periodic URA update".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1153
If the UE receives an URA UPDATE CONFIRM message, which contains a protocol error causing the variable
1>If V302 is equal to or smaller than N302, the UE shall:


2>enter idle mode;
2>Other actions the UE shall perform when entering idle mode from connected mode are specified in TS 25.331
subclause 8.5.2;
Reference
3GPP TS 25.331 clause 8.3.1.2, 8.3.1.7, 8.3.1.11
1. To confirm that the UE executes a URA update procedure after the expiry of timer T305.
2. To verify that the UE handles an invalid URA UPDATE CONFIRM message correctly when executing the URA
update procedure.
Initial Condition
UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in URA_PCH state. When the UE detects the expiry of timer T305, set according to the value specified in
system information, the UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the
uplink CCCH. The message shall indicate the cause to be "periodic URA update" in IE "URA update cause". SS replies
with an invalid URA UPDATE CONFIRM message sent on downlink DCCH, and check to see if the UE handles this
event properly. The UE shall attempt to retransmit the identical URA UPDATE message. After the SS receives the
second URA UPDATE message, it transmits a correct URA UPDATE CONFIRM message to the UE on the downlink
CCCH. The UE then returns to URA_PCH state. SS calls for generic procedure C.5 to check that UE is in URA_PCH
state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1154
Expected sequence
UE SS
1 The UE is in URA_PCH state.
SS wait until T305 timer has
expired.
2 URA UPDATE UE shall transmit this
"periodic URA update" into IE
"URA update cause".
3 URA UPDATE CONFIRM See specific message content.
4 URA UPDATE UE shall not return to idle
mode immediately, but
attempts to re-transmit this
message.
6 Void
URA_PCH state, the test

URA UPDATE (Step 2)
U-RNTI
URA Update Cause Check to see if set to 'Periodic URA update'

URA UPDATE CONFIRM (Step 3)
Use the URA UPDATE CONFIRM message as defined in [9] TS 34.108 clause 9, with the following exceptions:

URA UPDATE (Step 4)
U-RNTI
RRC Transaction identifier Check to see if set to the value given in URA UPDATE
CONFIRM message in step 3.
Protocol error indicator TRUE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1155
Use the URA UPDATE CONFIRM message as defined in [9] TS 34.108 clause 9.

After step 1 the UE shall detect the expiry of timer T305, move to CELL_FACH state, and transmit a URA UPDATE
message which sets the value "periodical cell update" into IE "URA update cause".
After step 3 the UE shall re-transmit URA UPDATE message with IE "Protocol error indicator" set to 'TRUE' and IE
"Protocol error information" set to "Message extension not comprehended".
After step 5 the UE shall return to the URA_PCH state.
8.3.2.3 Void
8.3.2.4 URA Update: loss of service after expiry of timers T307 and T305

When the T305 expires and the UE detects that it is "out of service area" as specified in TS 25.331 subclause 8.5.5.1,
the UE shall
1>start timer T307;

When the T307 expires, the UE shall:
1>move to idle mode;
1>release all dedicated resources;
1>perform other actions when entering idle mode from connected mode as specified in TS 25.331 subclause 8.5.2;
Reference
3GPP TS 25.331 clause 8.3.1.4.
1. To confirm that the UE moves to idle mode after the expiry of timer T307, following an expiry of timer T305
when it discovers that it is out of service area.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1156
Initial Condition
Test Procedure
Table 8.3.2.4
T0 T1
UTRA RF
Channel
Number
Ch. 1
CPICH Ec dBm/3.84MHz -60 -80
P-CCPCH
RSCP (TDD)
dBm -60 -80

The UE is in CELL_DCH state. The SS transmits UTRAN MOBILITY INFORMATION message to the UE to change
the value of T305. The UE shall respond with UTRAN MOBILITY INFORMATION CONFIRM message. The UE
transits to URA_PCH state using the generic procedure P18 in TS 34.108 clause 7.4. The content of the SYSTEM
INFORMATION BLOCK TYPE 3 and 4 is modified. The SS waits for reception of a periodical URA update in order
to know the timing of the T305 in the UE. The SS replies to the received URA UPDATE message with an URA
UPDATE CONFIRM message on the downlink CCCH. SS configures its downlink transmission power settings
according to columns "T1" in table 8.3.2.4 so that S<0. When the UE detects the expiry of periodic URA updating timer
T305 according to the system information, the UE detects that it is out of service area. After the expiry of timer T307,
the UE moves to the idle state. SS configures its downlink transmission power settings according to columns "T0" in
table 8.3.2.4 so that S>0. SS waits for 5s and then calls for generic procedure C.1 to check that UE is in idle mode state.
Expected sequence
UE SS
0 Initially, the UE is in
CELL_DCH state.
0a UTRAN MOBILITY INFORMATION Include new timers value (see
0b UTRAN MOBILITY INFORMATION
CONFIRM

7.4.2.7.2) specified in TS 34.108.
Transit the UE to URA_PCH
state. URA-ID 1 shall be in the
list of URA-ID.
1 Void
and 4
MASTER INFORMATION
BLOCK and SYSTEM
1b PAGING TYPE 1 Include IE "BCCH modification
info"
1c URA UPDATE IE "URA update cause" shall
be set to "periodical cell
update".
1d URA UPDATE CONFIRM
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1157
table 8.3.2.4 so that the UE
detects that it is out of service
area.
2b SS waits (T305+T307) +10%
for UE to enter idle mode.
3 Upon the expiry of timer T305,
the UE shall search for cell to
camp and triggers T307 timer.
SS listens to the uplink CCCH
to verify that URA UPDATE
message is not transmitted.
4 After the expiry of timer T307,
the UE enters idle state. SS
waits for 5s.
otherwise it fails.

MIB Tag 2
- PLMN Value tag 2
- Cell Value tag 2
- Cell Value tag 2

Qrxlevmin -70

PAGING TYPE 1 (Step 1b)
MIB Value tag 2
BCCH modification time Not present

UTRAN MOBILITY INFORMATION (Step 0a)
Use the same message sub-type found in clause 9 of TS 34.108, with the following exception.
- T305 5 minutes

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1158
UTRAN MOBILITY INFORMATION CONFIRM (Step 0b)
Use the same message sub-type found in clause 9 of TS 34.108.
URA UPDATE (Step 1c)
U-RNTI
URA Update Cause Check to see if set to "periodical URA update"

After step 0a the UE shall respond with UTRAN MOBILITY INFORMATION CONFIRM message.
After step 2 the UE shall not transmit any URA UPDATE message on the uplink CCCH.
8.3.2.5 URA Update: Success after Confirmation error of URA-ID list

The UE shall:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1159

Reference
3GPP TS 25.331 clause 8.3.1.10, 8.6.2.1.
1. To confirm that the UE retries to perform the URA update procedure following a confirmation error of URA-ID
list.
Initial Condition
Test Procedure
At the start of this test, the UE is brought to URA_PCH state and assigned a URA with URA-ID 1. When the UE
detects the expiry of timer T305 according to the system information, the UE moves to CELL_FACH state and
transmits a URA UPDATE message to the SS on the uplink CCCH. The reason for performing URA updating shall be
set to "periodic URA update" in IE "URA update cause". After the SS receives this message, it transmits a URA
UPDATE CONFIRM message which includes the IE "RRC state indicator" set to "URA_PCH" and IE "URA identity"
set to "URA-ID 2" to the UE on the downlink CCCH. The UE finds that the indicated URA-ID is not included in the list
of URA-IDs broadcasted in system information block type 2, and then the UE shall retry to transmit a URA UPDATE
message, with "change of URA" set in IE "URA update cause", for a confirmation error of URA-ID list. SS continue to
send the same URA UPDATE CONFIRM message on the downlink CCCH until N302+1 URA UPDATE messages
have been received. Then SS transmits a URA UPDATE CONFIRM message to the UE which includes IE "URA
Identity" set to "URA-ID 1" and IE "new U-RNTI" on the downlink CCCH. The UE shall find this URA-ID in its
URA-ID list and transmits an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1160
Expected sequence
UE SS
1 The UE is URA_PCH state.
SS initializes counter K to 0

2 URA UPDATE This message shall contain
value "periodic URA update"
set in IE "URA update cause"
after expiry of timer T305.
3 Void
4 URA UPDATE CONFIRM SS transmits this message,
setting the value "URA-ID 2" to
IE "URA Identity".
value "change of URA" set in
IE "URA update cause" after
6 SS increments K by 1. If K is
not greater than N302,
proceed to step 7. If K is
greater than N302, SS
proceeds to step 8.
setting the value "URA-ID 2" to
IE "URA Identity".
And then returns to step 5.
setting IE "URA Identity" to
"URA-ID 1". This message
also comprises IE "New U-
RNTI".
CONFIRM

URA UPDATE (Step 2)
U-RNTI

Use the same message sub-type as specified in TS 34.108 clause 9, with the following exceptions:
URA Identity 2

Use the same message sub-type as specified in TS 34.108 clause 9, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1161
New U-RNTI
-SRNC Identity '0000 0000 0001'
-S-RNTI '0000 0000 0000 0101 0101'
URA Identity 1

Only the message type IE in this message is checked.
After step 1 the UE shall detect the expiry of timer T305, move to CELL_FACH state, transmit a URA UPDATE
message on the uplink CCCH and set value "periodic URA update" into IE "URA update cause".
After step 4 the UE shall re-transmit a URA UPDATE message with IE "URA update cause" set to "change of URA"
after it detects a confirmation error of URA-ID list for the URA-ID indicated in the URA UPDATE CONFIRM
message. A total of (N302+1) URA UPDATE messages shall be received by the SS.
After step 8 the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH.
8.3.2.6 URA Update: Failure (V302 is greater than N302: Confirmation error of URA-
ID list)

The UE shall:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1162
2>enter idle mode;
2>perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;
Reference
3GPP TS 25.331 clause 8.3.1.10, 8.6.2.1
1. To confirm that the UE make repeated attempts to perform the URA update procedure following a detection of a
confirmation error of URA-ID list. It then moves to idle state when internal counter V302 is greater than N302.
Initial Condition
Test Procedure
The UE is originally in URA_PCH state updated with URA-ID 1. When the UE detects the expiry of timer T305
according to the system information, the UE shall move to CELL_FACH state and transmit a URA UPDATE message
to the SS on the uplink CCCH. In this message, the value "periodic URA update" shall be set in IE "URA update
cause". After the SS receives this message, it transmits a URA UPDATE CONFIRM message which includes the IE
"RRC state indicator" set to "URA_PCH" and indicating the IE "URA Identity" to be "URA-ID 2" to the UE on the
downlink CCCH. The UE finds that the indicated URA-ID is not included in the list of URA-IDs broadcasted. Then the
UE shall retry to transmit a URA UPDATE message, with "change of URA" set in IE "URA update cause", for N302
times and each time the SS responds with the URA UPDATE CONFIRM message similar to the previous one on the
downlink CCCH. After that, the UE shall enter idle state. SS waits for 5s and then calls for generic procedure C.1 to
check that UE is in idle mode state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1163
Expected sequence
UE SS
1 The UE is in URA_PCH state
at the start of the test. SS sets
internal counter K to 0.
2 URA UPDATE The message shall indicate
"periodic URA update" in IE
"URA update cause". This
message is sent following the
SS increments counter K by 1.
4 URA UPDATE CONFIRM The SS transmit this message
and set IE "URA Identity" to
"URA-ID 2".
5 URA UPDATE The message shall indicate
"change of URA" in IE "URA
update cause". This message
is sent following the expiry of
timer T305.
SS increments counter K by 1.
6 URA UPDATE CONFIRM The SS transmit this message
and set IE "URA Identity" to
"URA-ID 2". When K is greater
than N302 proceeds to step 7,
else executes step 5.
7 Void The UE shall enter idle state.
SS waits for 5s.
8 Void
9 Void
otherwise it fails.

Use the same message sub-type defined in TS 34.108 clause 9, with the following exceptions:
URA Identity 2

After step 1 the UE shall detect the expiry of timer T305, then it shall move to CELL_FACH state and transmit a URA
UPDATE message on the uplink CCCH, setting value "periodic URA update" in IE "URA update cause".
After step 6 and if K is not greater than N302, the UE shall retry to transmit a URA UPDATE message, setting value
"periodic URA update" in IE "URA update cause" after it detects the confirmation error of URA-ID list for the URA-ID
included in the URA UPDATE CONFIRM message.
After step 6 and if K is greater than N302, the UE shall stop transmitting URA UPDATE message and then enters idle
state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1164
8.3.2.7 URA Update: Success after T302 timeout


the UE shall:
2>clear any entry for the URA UPDATE CONFIRM message in the table "Accepted transactions" in the

Reference
3GPP TS 25.331 clause 8.3.1.12.
1. To confirm that the UE attempts to repeat the URA update procedure upon the expiry of timer T302.
Initial Condition
Test Procedure
The UE is in URA_PCH. When the UE detects the expiry of timer T305 according to the system information, the UE
moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH, setting value
"periodic URA update" into IE "URA update cause". The SS ignores this message. The UE shall then retry to transmit a
URA UPDATE message after the expiry of timer T302, until a total of N302+1 URA UPDATE messages have been
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1165
received by the SS. SS transmits a URA UPDATE CONFIRM message to the UE on the downlink CCCH to end the
procedure.
Expected sequence
UE SS
1 The UE is in URA_PCH state
at the beginning of test. SS
initializes counter K to 0
SS waits for T305 to expire.
value "periodic URA update" in
IE "URA update cause" sent
upon the expiry of timer T305.
3 SS shall not reply. Increment
K by 1.
value "periodic URA update" in
IE "URA update cause" sent
upon the expiry of timer T302.
5 SS shall not reply. SS
increments K by 1. If K is not
greater than N302, proceed to
step 4. If K is greater than
N302, SS proceeds to step 6.
CONFIRM

Use the same message sub-type as in TS 34.108 clause 9, with the following exceptions:
New U-RNTI
SRNC identity 0000 0000 0001 B
S-RNTI 0000 0000 0000 1111 1111 B
New C-RNTI 1010 1010 1010 1010 B

UPDATE message on the uplink CCCH. The updating cause shall be set to "periodic URA update" in IE "URA update
cause".
After step 3 the UE shall retry to transmit a URA UPDATE message at the expiry of timer T302, until a total of
N302+1 URA UPDATE messages have been received by the SS.
After step 6, the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink
DCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1166
8.3.2.8 Void
8.3.2.9 URA Update: Failure (UTRAN initiate an RRC connection release procedure
on CCCH)
1> or
CONNECTION RELEASE message on the downlink CCCH.

U_RNTI; or
the UE shall:

3>
3>enter idle mode;
Reference
3GPP TS 25.331 clause 8.3.1.5, 8.1.4.3
To confirm that the UE moves to idle state upon the reception of RRC CONNECTION RELEASE message on
downlink CCCH during a URA update procedure.
Initial Condition
Test Procedure
The UE is in URA_PCH state. When the UE detects the expiry of periodic URA updating timer T305, the UE moves to
CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. The message shall indicate
the cause to be "periodic URA update" in IE "URA update cause". The SS transmits RRC CONNECTION RELEASE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1167
message on downlink CCCH. The UE shall return to idle mode after release of all current signalling flows and radio
access bearers. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.
Expected sequence
UE SS
1 The UE is in the URA_PCH
state. SS wait until T305 timer
has expired.
"URA update cause".
3 RRC CONNECTION RELEASE SS transmits RRC
CONNECTION RELEASE
message to the UE on the
downlink CCCH.
4 The UE releases L2 signalling
radio bearer and radio
resources then the UE goes to
idle mode.
indicates that UE is in Idle
Mode state, the test passes,
otherwise it fails.

URA UPDATE (Step 2)
U-RNTI

Use the same message sub-type found in Clause 9 of TS 34.108.
After step 1 the UE shall transmit a URA UPDATE message on the uplink CCCH and set value "periodic URA update"
into IE "Cell update cause".
After step 3 the UE shall enter idle state.
8.3.2.10 URA Update: Reception of URA UPDATE CONFIRM message that causes
invalid configuration

If the variable INVALID_CONFIGURATION is set to TRUE, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1168

Reference
3GPP TS 25.331 clause 8.3.1.9
1. To confirm that the UE retransmits a URA UPDATE message when it receives a URA UPDATE CONFIRM
message that will trigger an invalid configuration in the UE, if the number of retransmissions has not reached the
maximum allowed value.
Initial Condition
Test Procedure
The UE is in URA_PCH state. When the UE detects the expiry of timer T305 according to the system information, the
UE moves to CELL_FACH state and transmits a URA UPDATE message to the SS on the uplink CCCH. This message
shall contain value "periodical URA update" in IE "URA update cause". Upon receiving such a message, the SS replies
with a URA UPDATE CONFIRM message with IE "RRC State Indicator" set to "CELL_DCH" on the downlink
CCCH. The UE shall detect its variable "invalid configuration" is set and re-transmit URA UPDATE message. SS then
transmit a valid URA UPDATE CONFIRM UPDATE message on the downlink CCCH to end the procedure.
Expected Sequence
UE SS
1 The UE is in the URA_PCH
state. SS wait until T305 timer
has expired.
"URA update cause".
4 URA UPDATE IE "Protocol error indicator" is
set to TRUE and IE "Protocol
error information" is set to
"Information element value not
comprehended".
5 Void
6 Void

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1169
URA UPDATE (Step 2)
U-RNTI

URA UPDATE (Step 4)
U-RNTI
Protocol error indicator TRUE
- Protocol error cause Information element value not comprehended


UPDATE message on the uplink CCCH, setting value "periodic URA update" into IE "URA update cause".
After step 3 the UE shall transmit a URA UPDATE message on the uplink CCCH, setting value 'TRUE" in IE "URA
update cause" and value "Information element value not comprehended" in "Protocol error cause".
8.3.2.11 URA Update: Cell reselection to cell of another PLMN belonging to the
equivalent PLMN list

1. A UE in URA_PCH state shall initiate the URA update procedure in the following cases:
- URA reselection:
- if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not
- if the list of URA identities in system information block type 2 is empty; or
- if the system information block type 2 can not be found:
- perform URA update using the cause "change of URA".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1170
- The cell is not barred, see clause 5.3.1.1 in TS 25.304.
- The cell is not part of the list of "forbidden LAs for roaming" TS 22.011
- The cell selection criteria are fulfilled, see clause 5.2.3.1.2 in TS 25.304.
3. The Mobile Equipment shall store a list of "equivalent PLMNs". This list is replaced or deleted at the end of
each location update procedure, routing area update procedure and GPRS attach procedure. The stored list
consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the network that
downloaded the list. The stored list shall not be deleted when the MS is switched off. The stored list shall be
deleted if the SIM is removed. The maximum number of possible entries in the stored list is six.
Reference
3GPP TS 25.331 clause 8.3.1.2.
3GPP TS 24.008 clause 4.4.1.
1. To confirm that the UE executes a URA update procedure after a successful reselection of another UTRA cell
with a URA identity that is not the URA of the UE and with a PLMN identity different from the original cell but
with a PLMN that is part of the equivalent PLMN list in the UE.
NOTE: Verifies conformance requirements 1, 2 and 3.
2. To confirm that the UE refrains from executing a URA update procedure to a better UTRA cell with another
PLMN identity when that PLMN identity is not part of the equivalent PLMN list in the UE.
NOTE: Test case in 8.3.2.1 is a test where the UE reselects to a cell with the same PLMN identity as the
registered PLMN.
Initial Condition
table 8.3.2.1-1, while cell 2 and cell 3 is inactive.
UE: URA_PCH (state 6-13) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the
UE.
UE: Shall have stored equivalent PLMN list containing PLMN-1 and PLMN-2. The equivalent PLMN list stored in the
UE shall not contain PLMN-3. The UE shall also have stored the URA identity URA-ID 1 from the list of URA-IDs in
cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1171
Test Procedure
Table 8.3.2.11-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
PLMN
identity
PLMN-1 PLMN-2 PLMN-3
URA identity URA-ID 1 URA-ID 2 URA-ID 3
CPICH Ec
(FDD)
dBm/
3.84
MHz
-73 -79 -79
Cell 2 is
switched
off
-73
-73 Cell 3 is
switched
off
Cell 3 is
switched
off
-66
P-CCPCH
RSCP (TDD)
dBm -62 -68 -68
Cell 2 is
switched
off
-62 -68 Cell 3 is
switched
off
Cell 3 is
switched
off
-62

execution. Columns marked "T0" denote the initial conditions, while columns marked "T1" and "T2" are to be applied
subsequently.
a) At T0, the SS activates Cell 1.
b) At T1, the SS activates Cell 2, and monitors Cell 2 for received messages from UE.
c) UE re-selects to Cell 2, and sends a URA UPDATE message. The SS replies with an URA UPDATE CONFIRM
message on the downlink CCCH.
d) At T2, the SS activates Cell 3, and monitors Cell 3 for received messages from UE.
Expected sequence
UE SS
1 UE is in URA_PCH state,
camped on Cell 1 and registered
to PLMN1. SS applies downlink
according to values in column
"T0" of table 8.3.2.11-1.
1a SS applies downlink
"T1" of table 8.3.2.11-1.
2 URA UPDATE The UE moves to CELL_FACH
state and transmits this
message in Cell 2.
The value "change of URA"
shall be set in IE "URA update
cause".
3 URA UPDATE CONFIRM The value "URA_PCH" set in IE
"RRC State Indicator".
4 SS applies downlink
"T2" of table 8.3.2.11-1.
5 SS monitors that the UE does
not send a URA UPDATE
message or any other message.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1172
URA UPDATE (Step 2)
Use the same message sub-type found in TS 34.108 clause 9, with the following exceptions:.

Use the same message sub-type found in TS 34.108 clause 9.
After Step 1 the UE shall send a URA UPATE message.
After Step 4 the UE shall refrain from sending a URA update (or any other message).
8.3.2.12 Restricted cell reselection to a cell belonging to forbidden LA list (URA_PCH)

- URA reselection:
- if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not
- if the list of URA identities in system information block type 2 is empty; or
- if the system information block type 2 can not be found:
- perform URA update using the cause "change of URA".
- The cell is not barred, see clause 5.3.1 in TS 25.304.
- The cell is not part of the list of "forbidden LAs for roaming" in TS 22.011.
- The cell selection criteria are fulfilled, see clause 5.2.3.1.2 in TS 25.304.
3. The Mobile Equipment shall contain a list of "forbidden location areas for roaming", as well as a list of
"forbidden location areas for regional provision of service". These lists shall be erased when the MS is switched
off or when the SIM is removed, and periodically (with period in the range 12 to 24 hours). The location area
identification received on the BCCH that triggered the location updating request shall be added to the suitable
list whenever a location update reject message is received with the cause "Roaming not allowed in this location
area" or with the cause "Location Area not allowed". The lists shall accommodate each 10 or more location area
identifications. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1173
Reference
3GPP TS 25.331 clause 8.3.1.2.
3GPP TS 24.008 clause 4.4.1.
1. To confirm that the UE refrains from selects a UTRA cell and performs a URA update if that cell has a LA
identity that is part of the list of LAs stored in the UE as "forbidden location areas for roaming".
NOTE: Test case in 8.3.2.1 is a test where the UE reselects to a cell with the same LA identity as the LA identity
in the original cell.
Initial Condition
table 8.3.2.12-1, while cell 2 is inactive.
UE.
UE: Shall have stored LA-ID 2 into the list of "forbidden location areas for roaming". The UE shall also have stored
the URA identity URA-ID 1 from the list of URA-IDs in cell 1.
Test Procedure
Table 8.3.2.12-1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
URA identity URA-ID 1 URA-ID 2
LA identity LA-ID 1 LA-ID 2
CPICH Ec
(FDD)
dBm/
3.84
MHz
-73 -79
Cell 2 is
switched off
-73

P-CCPCH
RSCP (TDD)
dBm -62 -68
Cell 2 is
switched off
-62

execution. Columns marked "T0" denote the initial conditions, while column marked "T1" are to be applied
subsequently.
a) At T1, verify that the UE does not reselect to cell 2 and not send a URA update in cell 2, although cell 2 is the
best cell.
b) SS calls for generic procedure C.5 to check that UE is in URA_PCH state in cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1174
Expected sequence
UE SS
1 UE is in URA_PCH state,
camped on Cell 1 and registered
to PLMN1. SS applies downlink
"T0" of table 8.3.2.12-1.
2 SS applies downlink
"T1" of table 8.3.2.12-1.
3 SS monitors that the UE does
not send a URA UPDATE
message or any other message.
that UE is in URA_PCH state in
cell 1, the test passes, otherwise
it fails.

-
After Step 2 the UE shall refrain from sending a URA UPDATE (or any other message).
8.3.2.13 URA Update: Change of URA due to HCS Cell Reselection

1. The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised
ranking according to hierarchical cell re-selection rules shall apply, and is defined by:
H
s
=Q
meas
,
s
- Qhcs
s
H
n
=Q
meas
,
n
- Qhcs
n

TO
n
* L
n

R
s
=Q
meas
,
s
+Qhyst
s
R
n
=Q
meas
,
n
- Qoffset
s,n
- TO
n
* (1 L
n
)

where:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1175
W(x) =0 for x <0
W(x) =1 for x >=0

TEMP_OFFSET
n
n
after a timer T
n
has
The timer T
n
n
- if HCS_PRIO
n
<>HCS_PRIO
s
and
Q
meas
,
n
>Qhcs
n
Or
- if HCS_PRIO
n
=HCS_PRIO
s
and
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

Q
meas,n
>Q
meas
,
s
+Qoffset2
s,n
Q
meas,n
>Q
meas
,
s
+Qoffset1
s,n

T
n
n
n
n
n
n
n


Where :
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1176
Squal =Q
qualmeas
Qqualmin
Srxlev =Q
rxlevmeas


1>URA reselection:
2>if the UE detects that the current URA assigned to the UE, stored in the variable URA_IDENTITY, is not

3>perform URA update using the cause "change of URA".
Reference
3GPP TS 25.304 clause 5.2.6.1.4
1. To confirm that the UE can read HCS related SIB information and act upon all HCS parameters in URA_PCH
state.
2. To confirm that the UE executes an URA update procedure after the successful change of URA due to HCS Cell
Reselection in URA_PCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1177
3. To confirm UE responds correctly when it re-selects to a new cell while waiting from URA UPDATE
CONFIRM message from SS.
Initial Condition
System Simulator: 3 cells - Cell 1 is active with URA-ID 1 and downlink transmission power shown in column marked
"T0" in table 8.3.2.13-1. Cell2 with URA-ID 1 andCell 3 with URA-ID 2 are switched off
UE, with URA-ID 1 from the list of URA-ID in cell 1
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- Qqualmin -20 dB
- Qhyst2s 0 dB
-HCS Priority 6

- CHOICE mode TDD
- SsearchHCS 47 dB
-HCS Priority 6

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1178
- Use of HCS used
information

- Cell info
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
-Temporary Offset 12
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1179
- Use of HCS used
- Cell info
- Cell individual offset 0dB
- CHOICE mode TDD
- Cell parameters ID Reference clause 6.1 Default settings for cell
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1180
Test Procedure
Table 8.3.2.13-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
Cell id in
system
information
1 2 3
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
HCS
Priority
6 7 7
CPICH Ec
(FDD)
dBm
/3.8
4
MHz
-60 -60 -60 -80 -80 -70 -80 -70 -73
H* (During
penalty
time)
16 16 4 -16 -16 6 -16 -6 3
H* (After
PenaltyTime)
16 16 16 -4 -4 6 -4 6 3
P-CCPCH
RSCP (TDD)
dBm -61 -61 -61 -80 -80 -67 -80 -73 -73
H* (After
PenaltyTime)
15 15 15 -4 -4 9 -4 3 3
R* (After
PenaltyTime)
-41 -41 -41 -60 -60 -47 -60 -53 -53


The UE is in the URA_PCH state and assigned with only 1 URA identity in cell 1: URA-ID 1. SS configures Cell 2 and
3 with power level given in column "T0", and URA-Id 1 and 2 respectively and starts broadcast of BCCH on the
primary CCPCH in cells 2 and 3. UE shall remain camped on the Cell 1 even after expiry of penalty time i.e. 40
seconds. SS sets downlink transmission power settings according to columns "T1" in table 8.3.2.13-1. SS then adjusts
the transmission power again according to 'T1' column. This is expected to cause the UE to perform a cell reselection to
cell 3 after at-least 40 Seconds (Penalty Time) after the power levels have been changed. UE on performing cell
reselection to cell 3 finds that its current URA-ID 1 is not in the new broadcasted list of URA-IDs, it moves to
CELL_FACH state and transmits a URA UPDATE message on the uplink CCCH. After the SS receives this message, it
transmits URA UPDATE CONFIRM message to the UE on the downlink CCCH. The "RRC State Indicator" is set to
"URA_PCH". UE returns to URA_PCH state in cell 3 without sending a uplink response message. Next SS adjusts the
transmission power according to 'T2' column. UE shall re-select to cell 2, and transmit URA UPDATE message to SS.
However, SS do not acknowledge but adjusts the transmission power according to 'T0' column. UE shall perform cell
re-selection to cell 1 and then sent URA UPDATE message to SS. Finally SS shall transmit URA UPDATE CONFIRM
message to UE on the downlink CCCH. UE shall return to URA_PCH state in Cell 1 and will not transmit anything on
PRACH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1181
Expected sequence
UE SS
1 The UE is updated with only 1
URA identity carried currently
by cell 1. The starting state of
the UE is URA_PCH
2 BCCH SS configures cell 2 (with
URA-ID 1) and Cell 3 (with
URA-ID 2) and power levels
as given in column T0 of table
8.3.2.13-1 and starts
transmission of BCCH.
3 UE shall Remain camped on
Cell 1 and in URA_PCH state
even after expiry of Penalty
time.
of all cells according to column
'T1' of table 8.3.2.13-1.
reselection first after the
penalty time to cell 3 and
when it finds that its current
URA-ID 1 is not in the new
broadcasted list of URA-IDs, it
shall then transmit this
"change of URA" into IE "URA
update cause".
6 URA UPDATE CONFIRM Message sent on CCCH.
of all cells according to column
'T2' of table 8.3.2.13-1.
8 URA UPDATE In Cell 2
9 SS do not respond to the URA
UPDATE message from UE
and set the power
transmission of all cells
according to column 'T0' of
table 8.3.2.13-1.
10 URA UPDATE In Cell 1
11 URA UPDATE CONFIRM Message sent on CCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1182
- CHOICE mode FDD
- Sintersearch 0 dB
- SsearchHCS 35 dB
- Qqualmin -20 dB
- Qhyst2s 0 dB
-HCS Priority 7

- CHOICE mode TDD
- SsearchHCS 47 dB
-HCS Priority 7

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1183
- Use of HCS used
information

- Cell info
- Qoffset1
s,n
-20dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB
- Cell info
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1184
- Use of HCS used
- Cell info
- CHOICE mode TDD
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1185
- Use of HCS used
information

- Cell info
- Qoffset1
s,n
-20 dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode FDD
- Cell info
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode FDD
- Qqualmin -20 dB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1186
- Use of HCS used
- Cell info
- CHOICE mode TDD
- Qoffset1
s,n
-20 dB
- HCS_Priority 6
- Penalty Time 40
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Qoffset1
s,n
-20dB
- HCS_Priority 7
- Penalty Time 40
- CHOICE mode TDD

URA UPDATE (Step 5, 8 and 10)

URA UPDATE CONFIRM (Steps 6 and 11)
Use the same message sub-type found in TS 34.108 clause 9.
shall move to CELL_FACH state and transmit URA UPDATE message setting value "change of URA" into IE "URA
update cause".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1187
shall move to CELL_FACH state and transmit URA UPDATE message setting value "change of URA" into IE "URA
update cause".
8.3.3 UTRAN Mobility Information
8.3.3.1 UTRAN Mobility Information: Success

NOTE: If a new value of timer T305 is included in the IE "UE Timers and constants in connected mode", and the
old value of timer T305 is "infinity", the UE will not use the new value of the timer T305 until the next
cell reselection.

.
If the IE "New U-RNTI" is included in a received message, the UE shall:
1>store the value in the variable U_RNTI, replacing any old stored value.

If the IE "New C-RNTI" is included, the UE shall:
1>store the value in the variable C_RNTI, replacing any old stored value;
1>use that C-RNTI when using common transport channels of type RACH, FACH and CPCH in the current cell.



Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1188
Reference
3GPP TS 25.331 clauses 8.3.3, 8.6.3.9, 8.6.3.10, 8.3.1.3.
1. To confirm that the UE starts to use the new identities after it receives a UTRAN MOBILITY INFORMATION
message from the SS.
Initial Condition
For system information block 1 of Cell 1 (gives IE's which are different from defaults given in 34.108 subclause 6.1) to
be transmitted before idle update preamble.
-T305 10

Test Procedure
Initially, the UE is in CELL_FACH state and it has been assigned a C-RNTI and U-RNTI. SS waits for T305 to expire.
The UE shall transmit a CELL UPDATE message. SS sends CELL UPDATE CONFIRM message to the UE on the
downlink CCCH. Then SS transmits an UTRAN MOBILITY INFORMATION message which includes new C-RNTI
and U-RNTI to the UE. Then the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message using
the assigned new C-RNTI in MAC header as confirmation. SS waits for UE to perform periodic cell updating. When SS
received a CELL UPDATE message, SS checks that UE uses the new U-RNTI in the CELL UPDATE message. Then
SS sends CELL UPDATE CONFIRM on the downlink CCCH. SS waits for UE to perform periodic cell updating.
When SS received a CELL UPDATE message, SS sends CELL UPDATE CONFIRM on the downlink CCCH to end
the test procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1189
Expected sequence
UE SS
1 The initial state of the UE is
CELL_FACH state. UE has
been allocated both C-RNTI
and U-RNTI during RRC
connection establishment
phase.
1a SS waits for a period up to
timer T305 to allow the UE to
start performing a cell
updating procedure.
1b CELL UPDATE
1c CELL UPDATE CONFIRM
2 UTRAN MOBILITY INFORMATION Contains new C-RNTI and U-
RNTI identities and a value for
T305 that is different from the
value defined in the system
information.
CONFIRM
The assigned new C-RNTI
shall be included in MAC
header.
4 SS wait for T305 (same as the
value defined in system
information) to expire.
5 CELL UPDATE UE shall trigger cell updating.
The message shall indicate
the same U-RNTI assigned in
the UTRAN MOBILITY
INFORMATION message in
step 2.
7 SS wait for T305 (the new
value as specified in step 2) to
expire.
8 CELL UPDATE UE shall trigger cell updating.
The message shall indicate
the same U-RNTI assigned in
the UTRAN MOBILITY
INFORMATION message in
step 2.

Use the same message sub-type as in TS 34.108, clause 9, with the following exceptions:
New U-RNTI
- SRNC Identity '0000 0000 0001'
- S-RNTI '0101 0101 0101 0101 0101'
New C-RNTI 0000 0000 0000 1111
- T305 5 minutes

Only the message type IE is checked in this message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1190
CELL UPDATE (Step 1b)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH.
U-RNTI

CELL UPDATE CONFIRM (Step 1c)
Use the same message sub-type as in TS 34.108, clause 9.
Use the same message sub-type as in TS 34.108, clause 9 on the downlink CCCH, with the exception of the following
IEs:
U-RNTI

that using the assigned new C-RNTI in MAC header.
After step 4 and 7 the UE shall transmit a CELL UPDATE message on the uplink CCCH with IE "Cell update cause"
set to "periodical cell updating". The IE "U-RNTI" shall be identical to the IE "New RNTI" found in UTRAN
MOBILITY INFORMATION message sent by the SS in step 2.
8.3.3.2 UTRAN Mobility Information: Failure (Invalid message reception)

8.3.3.2.2 Conformance Requirements
If the UTRAN MOBILITY INFORMATION message contains a protocol error causing the variable
1>transmit a UTRAN MOBILITY INFORMATION FAILURE message on the uplink DCCH using AM RLC;
1>set the IE "RRC transaction identifier" in the UTRAN MOBILITY INFORMATION FAILURE message to the
table "Rejected transactions" in the variable TRANSACTIONS, and;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1191
1>when the UTRAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for
transmission:
2>continue with any ongoing processes and procedures as if the invalid UTRAN MOBILITY INFORMATION
message has not been received;
References
3GPP TS 25.331 clauses 8.3.3.6
1. To confirm that the UE ignore the erroneous UTRAN MOBILITY INFORMATION message and report this
event to the UTRAN by sending UTRAN MOBILITY INFORMATION FAILURE message, stating the
appropriate failure cause and information.
Initial Conditions
For system information block 1 (given IEs which are different from defaults given in TS34.108 clause 6.1) to be
T305 5 minutes

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1192
Test Procedure
The UE is brought to CELL_FACH state. SS waits for T305 to expire. The UE shall transmit a CELL UPDATE
message. SS sends CELL UPDATE CONFIRM message to the UE on the downlink DCCH. Then SS transmits a
UTRAN MOBILITY INFORMATION message, which contains an unexpected critical message extension, to the UE
on the DCCH using AM-RLC mode. The UE shall respond by transmitting the UTRAN MOBILITY INFORMATION
FAILURE message, indicating "protocol error" in IE "failure cause" and also "Message extension not comprehended "
in IE "Protocol error information". After receiving the UTRAN MOBILITY INFORMATION FAILURE message, SS
waits for T305 to expire. The UE shall transmit a CELL UPDATE message with the original U-RNTI identity assigned.
SS sends CELL UPDATE CONFIRM message to the UE on the downlink DCCH.
Expected Sequence
UE SS
1 The initial state of the UE is
CELL_FACH state.
1a SS waits for a period up to
updating procedure.
1b CELL UPDATE
1c CELL UPDATE CONFIRM
2 UTRAN MOBILITY INFORMATION See specific message content.
FAILURE
UE shall transmit this
message to report the error in
UTRAN MOBILITY
INFORMATION message. It
shall include the appropriate
cause in the message.
4 SS waits for a period up to
updating procedure.
5 CELL UPDATE

Use the UTRAN MOBILITY INFORMATION message as defined in [9] TS 34.108 clause 9, with the following
exceptions:

UTRAN MOBILITY INFORMATION FAILURE (Step 3)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1193
Failure Cause
- Failure Cause Check to see if set to 'Protocol error'
- Protocol Error Information Check to see if set to Message extension not
comprehended

CELL UPDATE (Step 1b and 5)
U-RNTI
- SRNC Identity Check to see if set to '0000 0000 0001'B
- S-RNTI Check to see if set to '0000 0000 0000 0000 0001'B
Cell update cause Check to see if set to 'periodical cell updating'

CELL UPDATE CONFIRM (Step 1c and 6)
Use the same message sub-type as in TS 34.108 clause 9.
After step 1a the UE shall initiate a periodic cell updating procedure by transmitting CELL UPDATE message on the
CCCH. In this message, the U-RNTI identity shall be set to the same value as assigned during the RRC connection
establishment procedure.
After step 2 the UE shall transmit UTRAN MOBILITY INFORMATION FAILURE message, indicating the value
"protocol error" in IE "failure cause" and also "Message extension not comprehended" in IE "protocol error
information".
After step 4 the UE shall initiate a periodic cell updating procedure by transmitting CELL UPDATE message on the
CCCH. In this message, the U-RNTI identity shall be set to the same value as assigned during the RRC connection
establishment procedure.
8.3.3.3 UTRAN MOBILITY INFORMATION: Seamless SRNS relocation in
CELL_DCH (without pending of ciphering)
To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the
downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only.
1>if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info" or contained the
IE "Integrity protection mode info":
2>set the IE "Status" in the variable SECURITY_MODIFICATION for all the CN domains in the variable
SECURITY_MODIFICATION to "Affected";
1>if the UTRAN MOBILITY INFORMATION message contained the IE "Ciphering mode info":
2>include and set the IE "Radio bearer uplink ciphering activation time info" to the value of the variable
RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO.
1>if the received UTRAN MOBILITY INFORMATION message included the IE " Downlink counter
synchronisation info ":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1194
2>re-establish RB2;
synchronisation info" in the UTRAN MOBILITY INFORMATION CONFIRM message.
1>if the IE "Integrity protection mode info" was present in the UTRAN MOBILITY INFORMATION message:
and including the transmitted UTRAN MOBILITY INFORMATION CONFIRM message.
1>if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY
INFORMATION message:
ESTABLISHED_RABS.
1>apply the new ciphering configuration as follows:
2>if the IE "Radio bearer downlink ciphering activation time info" is present:
3>apply the following procedure for each radio bearer and signalling radio bearers using RLC-AM or RLC-
UM indicated by the IE "RB identity":
.
4>switch to the new ciphering configuration according to the following:

5>if an RLC reset or re-establishment occurs before the activation time for the new ciphering
configuration has been reached, ignore the activation time and apply the new ciphering
configuration immediately after the RLC reset or RLC re-establishment.
1>if IE "Integrity protection mode command" has the value "start" and the IE "Status" in the variable
INTEGRITY_PROTECTION_INFO has the value "Started" and this IE was not included SECURITY MODE
COMMAND:
NOTE: This case is used in SRNS relocation
2>perform integrity protection on the received message, applying the new integrity protection configuration, as
described in subclause 8.5.10.1 of TS25.331 by:
3>using the algorithm (UIA defined in TS33.102) indicated by the IE "Integrity protection algorithm"
contained in the IE "Integrity protection mode info";
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1195
3>using the IE "Integrity protection initialisation number", contained in the IE "Integrity protection mode
info" as the value of FRESH defined in TS33.102.
2>let RBm be the signalling radio bearer where the reconfiguration message was received and let RBn be the
signalling radio bearer where the response message is transmitted;
2>prohibit transmission of RRC messages on all signalling radio bearers in the IE "ESTABLISHED_RABS"
except on RB0 and the radio bearer where the response message is transmitted;
2>if for a signalling radio bearer, a security configuration triggered by a previous SECURITY MODE
COMMAND is pending, due to the activation time for the signalling radio bearer not having elapsed:
3>if the previous SECURITY MODE COMMAND was received due to new keys being received:
4>consider the new integrity protection configuration to include the received new keys; and
4>initialise the HFN of the COUNT-I values of the corresponding signalling radio bearers according to
subclause 8.1.12.
3>else:
4>consider the new Integrity Protection configuration to include the keys associated with the
LATEST_CONFIGURED_CN_DOMAIN associated with the previously received SECURITY
MODE COMMAND; and
4>initialise the HFN of the COUNT-I values of the corresponding signalling radio bearers according to
subclause 8.1.12 using the START value associated with the
LATEST_CONFIGURED_CN_DOMAIN to be transmitted in the response to the current message.
2>start applying the new integrity protection configuration in the downlink for each signalling radio bearer in
the IE "ESTABLISHED_RABS" except RBm at the next received RRC message disregarding any pending
activation times for the corresponding signalling radio bearer;
2>start applying the new integrity protection configuration in the downlink for signalling radio bearer RBm
from and including the received configuration message;
2>start applying the new integrity protection configuration in the uplink for signalling radio bearer RBn from
and including the transmitted response message;
2>start applying the new integrity protection configuration in the uplink for signalling radio bearers other than
RBn from the first message onwards.
NOTE: The UTRAN should ignore the information included in the IE "Uplink integrity protection info".
Reference
3GPP TS 25.331 clause 8.3.3 , 8.6.3.4 and 8.6.3.5
1. To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS
relocation.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1196
Test Procedure
The UE is in the CELL_DCH state. SS then transmits a UTRAN MOBILITY INFORMATION message, which
includes a valid New U-RNTI, IE Downlink counter synchronisation info and IE Integrity protection mode info,
to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY
INFORMATION CONFIRM message. This message also includes a calculated new START value according to the
formula START
X
' =MSB
20
(MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most
recently configured CK
X
and IK
X
}) +2, calculated IE Integrity Check Info using a new FRESH value as included in
IE Integrity protection initialisation number in IE Integrity protection mode info in UTRAN MOBILITY
INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection
configuration.
(SRB3).
Expected sequence

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1197
UE SS
1 UTRAN MOBILITY INFORMATION This message is sent after last
ciphering activation time. New U-
RNTI identities are assigned to the
UE. IE Downlink counter
SRB1.
CONFIRM
on SRB2 by UE.
CONFIRM


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1198
UE SS
1 UTRAN MOBILITY INFORMATION New U-RNTI identities are assigned
to the UE. IE Downlink counter
SRB1.
CONFIRM
SRB2.
SRB2.
on UL SRB2 by UE.
CONFIRM

applied on DL SRB3.
on UL SRB2 by UE.


New U-RNTI
SRNC
S-RNTI
CN Information info
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1199


X
' =
MSB
20
( MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured
CK
X
and IK
X
message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration.
8.3.4 Active set update in soft handover (FDD)
8.3.4.1 Active set update in soft handover: Radio Link addition

Upon reception of an ACTIVE SET UPDATE message the UE shall act upon all received information elements as
specified in TS 25.331 subclause 8.6, unless specified otherwise in the following. The UE shall:
1>first add the RLs indicated in the IE "Radio Link Addition Information";
1>perform the physical layer synchronisation procedure B as specified in TS 25.214;
1>set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE COMPLETE message to the value of
"RRC transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted
1>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1200
1>transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH using AM RLC without
waiting for the completion of the Physical Layer synchronization B, specified in TS 25.214;

Reference
1. To confirm that the UE continues to communicate with the SS on both the additional radio link and an already
existing radio link after the radio link addition.
Initial Condition
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS-DCCH+DTCH_DCH (state 6-10) in cell 1 as specified in clause 7.4 of
TS 34.108, depending on the CN domain supported by the UE.
Test Procedure
Table 8.3.4.1
T0 T1 T2 T3 T0 T1 T2 T3
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -60 OFF -60 -75

-60 -60

OFF

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1201
Initially, the UE goes to connected mode and establishes a radio access bearer in CELL_DCH state in cell 1.
SS configures its downlink transmission power settings according to columns "T1" in table 8.3.4.1. UE shall be
triggered to transmit a MEASUREMENT REPORT message which includes the primary scrambling code for cell 2
according to IE "Intra-frequency event identity", which is set to '1a' in the SYSTEM INFORMATION BLOCK TYPE
11. After the MEASUREMENT REPORT message is received, the SS configures the new radio link to be added from
cell 2 and then the SS transmits to the UE an ACTIVE SET UPDATE message in cell 1 on DCCH using AM RLC
which includes the IE "Radio Link Addition Information" (e.g. Downlink DPCH information and other optional
parameters relevant for the additional radio links with Primary CPICH info used for the reference ID).
message to the SS on the uplink DCCH using AM RLC without waiting for the physical channel synchronisation B.
SS configures its downlink transmission power settings according to columns "T2" in table 8.3.4.1. UE shall not detect
the DPCH from cell 1 but continue to communicate through the another DPCH from cell 2. The UE shall transmit a
MEASUREMENT REPORT message which indicates the event '1b' for cell 1.
SS shall transmit a UE CAPABILITY ENQUIRY message to confirm that the UE can respond this message through the
DPCH in cell 2. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION message. Then SS transmits a
The SS configures its downlink transmission power settings according to columns "T3" in table 8.3.4.1. UE shall detect
DPCH from cell 1, but not detect the DPCH from cell 2, but continue to communicate through DPCH from cell 1. The
UE shall transmit a MEASUREMENT REPORT message which indicates the event '1b' for cell 2.
DPCH in cell 1. The UE shall transmit a UE CAPABILITY INFORMATION message. Then SS transmits a UE
CAPABILITY INFORMATION CONFIRM message. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Expected sequence
UE SS
table 8.3.4.1.
2 MEASUREMENT REPORT See specific message
3 ACTIVE SET UPDATE SS transmits this message in
cell 1 on downlink DCCH
using AM RLC. The message
includes IE "Radio Link
Addition Information". (e.g.
Downlink DPCH information
and other optional parameters
relevant for the additional
radio links with Primary
CPICH info used for the
reference ID in cell 2)
4 ACTIVE SET UPDATE COMPLETE The UE shall configure a new
radio link to cell 2, without
interfering with existing
connections on the radio link
in cell 1.
table 8.3.4.1
5a MEASUREMENT REPORT See specific message
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1202
9 Void
9a Void
table 8.3.4.1
CELL_DCH state, the test

The contents of SIB11 broadcasted in cell 1 shall be in accordance with the default SIB11 as specified in section 6.1 of
TS 34.108.
The contents of SIB12 in cell 1, and SIB11 and SIB12 in cell 2 shall be in accordance with the detault SIBs as specified
in TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1203
Message Type
Measured Results
- Intra-frequency measured results Check to see if measurement results for 2 cells are
included (the order in which the different cells are reported
is not important)
Event results

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1204
- Primary Scrambling Code Refer to clause titled "Default settings for cell
No.2 (FDD)" in clause 6.1 of TS 34.108
- CHOICE mode FDD
information
- DL channelisation code This IE is repeated for all existing downlink
DPCHs allocated to the UE
- Code Number For each DPCH, assign the same code
number in the current code given in cell 1.

MEASUREMENT REPORT (Step 5a)
Note 1: UE may optionally include Cell measured results IE for Cell 1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1205
Message Type
Measured Results
- Cell measured results UE may optionally include report for Cell 1
Event results
- Intra-frequency event identity 1b

Note 1: UE may optionally include Cell measured results IE for Cell 2
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1206
Message Type
Measured Results
Event results

After step 1 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC.
After step 3 the UE shall transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH using AM
RLC to acknowledge the completion of the active set additional procedure.
After step 6 the UE shall transmit a UE CAPABILITY INFORMATION message.
8.3.4.2 Active set update in soft handover: Radio Link removal

specified in 8.6, unless specified otherwise in the following. The UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1207
1>remove the RLs indicated in the IE "Radio Link Removal Information". If the UE active set is full or becomes
full, an RL, which is included in the IE "Radio Link Removal Information" for removal, shall be removed before
adding RL, which is included in the IE "Radio Link Addition Information" for addition;
1>clear that entry;

Reference
1. To confirm that the UE continues to communicate with the SS on the remaining radio link after radio link
removal on the active set.
2. To confirm that the UE is not using the removed radio link to communicate with the SS.
Initial Condition
System Simulator: 2 cells - both Cell 1 and Cell 2 are active
Test Procedure
Table 8.3.4.2
T0 T1 T2 T3 T0 T1 T2 T3
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/3.
84MHz
-60 -60 -75 -60 -75

-60 -60 OFF

At the start of the test, the UE goes to connected mode and establishes a radio access bearer service in the CELL_DCH
state in cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1208
SS configures its downlink transmission power settings according to columns "T2" in table 8.3.4.2. UE shall transmit a
frequency event identity", which is set to '1b' in the SYSTEM INFORMATION BLOCK TYPE 11. After the
MEASUREMENT REPORT message is received, the SS remove the radio link from cell 1 and then SS transmits an
ACTIVE SET UPDATE message, which includes IE "Radio Link Removal Information" and specifying the P-CPICH
information of the cell to be removed.
When the UE receives this message, the UE RRC entity shall request UE L1 entity to terminate transmission and
reception of the radio link from cell 1. Then the UE transmits an ACTIVE SET UPDATE COMPLETE message to the
SS on the uplink DCCH using AM RLC.
DPCH in cell 2. The UE shall transmit a UE CAPABILITY INFORMATION message. Then SS transmits a UE
CAPABILITY INFORMATION CONFIRM message.
SS configures its downlink transmission power settings according to columns "T3" in table 8.3.4.2 so as to generate a
radio link failure condition. The UE shall detect the radio link failure UE shall re-select to cell 1 and transmit a CELL
UPDATE message. SS transmits a CELL UPDATE CONFIRM message after it receive CELL UPDATE message from
UE. Then the UE shall transmit an UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH to
acknowledge the receipt of the new UE identities..
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1209
Expected sequence
UE SS
table 8.3.4.2
3 ACTIVE SET UPDATE SS transmits this message in
cell 1 on downlink DCCH
using AM RLC. The message
includes IE "Radio Link
Addition Information". (e.g.
Downlink DPCH information
and other optional parameters
relevant for the additional
radio links with Primary
CPICH info used for the
reference ID in cell 2)
radio link to cell 2, without
interfering with existing
connections on the radio link
in cell 1.
table 8.3.4.2
7 ACTIVE SET UPDATE The SS transmits this
message on downlink DCCH
using AM RLC which includes
IE "Radio Link Removal
Information".
8 ACTIVE SET UPDATE COMPLETE The UE shall remove the radio
link associated with cell 1.
table 8.3.4.2
13 CELL UPDATE UE sends this message in cell
1.
CONFIRM

TS 34.108:
The contents of SIB12 in cell 1, and SIB11 and SIB12 in cell 2 shall be in accordance with the detault SIBs as specified
in TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1210
Message Type
Measured Results
- Intra-frequency measured results Check to see if measurement results for 2 cells are
included (the order in which the different cells are reported
is not important)
Event results

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1211
The message to be used in this test is defined in Annex.A, with the following exceptions:
- CHOICE mode FDD
information

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1212
Message Type
Measured Results
- Intra-frequency measured results list
- CHOICE mode FDD
- CHOICE mode FDD
Event results
- CHOICE event result Intra-frequency measurement event results
- CHOICE mode FDD

The message to be used in this test is the same as the message sub-type found in TS 34.108, clause 9, with the following
exceptions:
Radio link removal information

1 radio link to be removed

- Primary scrambling code Set to the same P-CPICH scrambling code assigned for
cell 1

The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in TS 34.108,
clause 9 with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1213

New C-RNTI '1010 1010 1010 1010'

After step 7 the UE shall remove the radio link from cell 1 and it shall transmit an ACTIVE SET UPDATE
After step 12 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to "radio
link failure".
using AM RLC.
8.3.4.3 Active set update in soft handover: Combined radio link addition and removal

specified in 8.6, unless specified otherwise in the following. The UE shall:
1>remove the RLs indicated in the IE "Radio Link Removal Information". If the UE active set is full or becomes
full, an RL, which is included in the IE "Radio Link Removal Information" for removal, shall be removed before
adding RL, which is included in the IE "Radio Link Addition Information" for addition;
1>clear that entry;

Reference
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1214
1. To confirm that the UE continues to communicate with the SS on the added radio link and removes radio link
which exists prior to the execution of active set update procedure.
Initial Condition
System Simulator: 3 cells- Cell 1, Cell 2 and Cell 3 are active, with downlink transmission power settings according to
TS 34.108, depending on the CN domain supported by the UE [Active set is not full.]
Test Procedure
Table 8.3.4.3
UTRA RF
Channel
Number

Ch. 1

Ch. 1

Ch. 1

CPICH Ec
dBm/
3.84
MHz

-60

-60

-60

OFF

-60

-80

-60

-60

OFF

-70

-80

-80

-60

-60

OFF

The UE goes to connected mode and establishes a radio access bearer in the CELL_DCH state in cell 1.
SS configures its downlink transmission power settings according to columns "T1" in table 8.3.4.3. UE transmits a
frequency event identity", which is set to '1a' in the SYSTEM INFORMATION BLOCK TYPE 11. After the
MEASUREMENT REPORT message is received, the SS configures the new radio link to be added from cell 2 and then
the SS transmits to the UE in cell 1 an ACTIVE SET UPDATE message which includes IE "Radio Link Addition
Information", indicating the addition of cell 2 into the active set, on DCCH using AM RLC.
cell 3 and then the SS transmits to the UE an ACTIVE SET UPDATE message which includes IE "Radio Link Addition
Information" and IE "Radio Link Removal Information", indicating the removal of cell 2 and addition of cell 3 into the
active set, on DCCH using AM RLC.
uplink and downlink activities of existing radio links and then the UE removes the radio link specified in an ACTIVE
SET UPDATE message. The UE shall transmit an ACTIVE SET UPDATE COMPLETE message to the SS on the
SS configures its downlink transmission power settings according to columns "T3" in table 8.3.4.3. The UE shall be
according to IE Intra-frequency event identity which is set to 1b in the SYSTEM INFORMATION BLOCK TYPE
11.
After the MEASUREMENT REPORT message is received, the SS shall transmit a UE CAPABILITY ENQUIRY
message to confirm that the UE can respond to this message through the DPCH in cell 3. The UE shall transmit a UE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1215
CAPABILITY INFORMATION message. Then SS transmits a UE CAPABILITY INFORMATION CONFIRM
message.
SS configures its downlink transmission power settings according to columns "T4" in table 8.3.4.3. The UE shall be
according to IE Intra-frequency event identity which is set to 1b in the SYSTEM INFORMATION BLOCK TYPE
11.
After the MEASUREMENT REPORT is received, the SS shall transmit a UE CAPABILITY ENQUIRY message to
confirm that the UE can respond to this message through the DPCH in cell 1. The UE shall transmit a UE
CAPABILITY INFORMATION message. Then SS transmits a UE CAPABILITY INFORMATION CONFIRM
message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1216
Expected sequence
UE SS
0a SS configures the initial active
set with only cell 1. SS
configures its downlink
table 8.3.4.3
0b MEASUREMENT REPORT See specific message
0c ACTIVE SET UPDATE The SS transmit this message
cell 2.
0d ACTIVE SET UPDATE COMPLETE The UE adds the radio link in
cell 2.
table 8.3.4.3
cell 3 and IE "Radio Link
Removal Information" for cell
2.
radio link in cell 3 and
removes the old radio link in
cell 2.
table 8.3.4.3
4b MEASUREMENT REPORT See specific message
table 8.3.4.3

MEASUREMENT REPORT (Step 0b)
NOTE 1: Cell measured results for cells 1 and 2 may appear in either order (i.e. cell 1 then cell 2 or cell 2 then cell
1)
NOTE 2: Cell measured results for cell 3 may or may not be present (depends upon the capability of the UE and
test uncertainties in power level)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1217
Message Type
Measured Results
- Cell measured results See Note 1
Event results Checked that this IE is absent

ACTIVE SET UPDATE (Step 0c)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1218
- CHOICE mode FDD
allocated to the UE
parameter sets"

NOTE 1: Cell measured results for cells 1, 2 and 3 may appear in any order.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1219
Message Type
Measured Results

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1220
- CHOICE mode FDD
information

Note 1: UE may optionally include Cell measured results IE for Cell 1 and 2.
Note 2: Cell measured results for cells 1and 2 may appear in any order.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1221
Message Type
Measured Results

Note: UE may optionally include Cell measured results IE for Cell 3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1222
Message Type
Measured Results

At step 0a the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC.
After step 0c the UE shall transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 3 the UE shall transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 4a the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC.
After step 5 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH in cell 3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1223
After step 9 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH in cell 1.
8.3.4.4 Active set update in soft handover: Invalid Configuration

If any of the following conditions are valid:

- a radio link in the IE "Radio link addition information" is also present in the IE "Radio Link Removal
Information"; and/or

- the variable INVALID_CONFIGURATION is set to TRUE:
the UE shall:
1>keep the active set as it was before the ACTIVE SET UPDATE message was received;
1>transmit an ACTIVE SET UPDATE FAILURE message on the DCCH using AM RLC;
1>set the IE "RRC transaction identifier" in the ACTIVE SET UPDATE FAILURE message to the value of "RRC
transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions"
in the variable TRANSACTIONS; and
1>clear that entry;
1>set the IE "failure cause" to "Invalid configuration";
1>When the ACTIVE SET UPDATE FAILURE message has been submitted to lower layers for transmission:
2>the procedure ends on the UE side.
Reference
3GPP TS 25.331 clause 8.3.4.5
1. To confirm that the UE transmits an ACTIVE SET UPDATE FAILURE message on the DCCH using AM RLC,
if the received ACTIVE SET UPDATE message includes a radio link which is specified in both IE "Radio Link
Addition Information" and IE "Radio Link Removal Information".
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1224
Test Procedure
Table 8.3.4.4
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -75

-60 -60

The UE establishes a radio access bearer in the CELL_DCH state in cell 1. SS configures its downlink transmission
power settings according to columns "T1" in table 8.3.4.4. UE shall be triggered to transmit a MEASUREMENT
REPORT message which includes the primary scrambling code for cell 2 according to IE "Intra-frequency event
identity", which is set to '1a' in the SYSTEM INFORMATION BLOCK TYPE 11. SS then transmits an ACTIVE SET
UPDATE message in cell 1 on DCCH using AM RLC which includes the same primary scrambling code in IE
"Primary CPICH Info" of both IE"Radio Link Addition Information" and IE "Radio Link Removal Information". When
the UE receives this message, it transmits an ACTIVE SET UPDATE FAILURE message which is set to "Invalid
configuration" in IE "failure cause" on the uplink DCCH using AM RLC to the SS. UE then send another
MEASUREMENT REPORT to SS 4s after step 2. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Expected sequence
UE SS
table 8.3.4.4
using AM RLC which includes
the same primary scrambling
code in IE"Primary CPICH
Info" of both IE"Radio Link
Addition Information" and IE
"Radio Link Removal
Information".
4 ACTIVE SET UPDATE FAILURE The message shall state
"Invalid configuration" in IE
"failure cause".
The message to be used in this test is defined in the default message content clause, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1225
- CHOICE mode FDD
information
- Spreading factor Reference TS 34.108 clause 6.10 Parameter
set

ACTIVE SET UPDATE FAILURE (Step 4)
Failure cause
Not Checked
Check to see if it's set to 'Invalid configuration'

After step 3 the UE shall transmit an ACTIVE SET UPDATE FAILURE message, setting "Invalid configuration" in IE
"failure cause" and sent on the uplink DCCH using AM RLC.
After step 4 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC, 4s
after step 2.
8.3.4.5 Active set update in soft handover: Reception of an ACTIVE SET UPDATE
message in wrong state
If the UE is in another state than CELL_DCH state upon reception of the ACTIVE SET UPDATE message, the UE
shall perform procedure specific error handling as follows. The UE shall:
1>transmit a ACTIVE SET UPDATE FAILURE message on the uplink DCCH using AM RLC;
transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Accepted transactions"
1>clear that entry;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1226
with receiver state";
1>when the ACTIVE SET UPDATE FAILURE message has been delivered to lower layers for transmission:
2>continue with any ongoing processes and procedures as if the ACTIVE SET UPDATE message has not been
received;
Reference
3GPP TS 25.331 clause 8.3.4.0
1. To confirm that the UE transmit an ACTIVE SET UPDATE FAILURE message when it receives an ACTIVE
SET UPDATE message in any state other then CELL_DCH.
Initial Condition
Test Procedure
Table 8.3.4.5
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -70

At the start of the test, the UE establishes a radio access bearer service in the CELL_FACH state in cell 1. SS then send
a MEASUREMENT CONTROL message to UE. The UE shall perform periodical traffic volume measurement
according to this message and then transmit MEASUREMENT REPORT message back to SS. The SS transmits to the
UE an ACTIVE SET UPDATE message in cell 1 on DCCH using AM RLC which includes the IE "Radio Link
Addition Information" indicating the addition of cell 2 into the active set. When the UE receives this message, UE shall
transmit ACTIVE SET UPDATE FAILURE message, with the IE "failure cause" set to the cause value "protocol error"
and includes the IE "Protocol error information" with the IE "Protocol error cause" set to "Message not compatible with
receiver state", on the uplink DCCH using AM RLC. UE shall continue its traffic volume measurement and send
MEASUREMENT REPORT messages back to SS periodically. SS calls for generic procedure C.2 to check that UE is
in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1227
Expected sequence
UE SS
measurement.
2 Void
Link Addition Information".
4 ACTIVE SET UPDATE FAILURE IE "failure cause" set to the
cause value "protocol error"
and includes the IE "Protocol
error information" with the IE
"Protocol error cause" set to
"Message not compatible with
receiver state".

Mode

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1228
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

ACTIVE SET UPDATE
The message to be used in this test is defined in TS 34.108 clause 9, with the following exceptions:
- CHOICE mode FDD
- Spreading factor Reference TS 34.108 clause 6.10 Parameter
set

After step 3 the UE shall transmit an ACTIVE SET UPDATE FAILURE message on the DCCH. In this message, the
value "Message not compatible with receiver state" shall be set in IE "Protocol Error Information".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1229
8.3.4.6 Void
8.3.4.7 Active set update in soft handover: Invalid Message Reception
If the ACTIVE SET UPDATE message contains a protocol error causing the variable PROTOCOL_ERROR_REJ ECT
The UE shall:
1>transmit a ACTIVE SET UPDATE FAILURE message on the uplink DCCH using AM RLC;
transaction identifier" in the entry for the ACTIVE SET UPDATE message in the table "Rejected transactions"
1>when the ACTIVE SET UPDATE FAILURE message has been delivered to lower layers for transmission:
2>continue with any ongoing processes and procedures as if the invalid ACTIVE SET UPDATE message has
not been received;
Reference
1. To confirm that the UE retains its active set list and transmits an ACTIVE SET UPDATE FAILURE message
when it receives an invalid ACTIVE SET UPDATE message.
Initial Condition
System Simulator: 2 cells both cell 1 and cell 2 are active.
TS 34.108, depending on the CN domain supported by the UE (Integrity protection algorithm is not applied at the start
of test)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1230
Test Procedure
Table 8.3.4.7
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -75

-60 -60

The UE establishes a radio access bearer in CELL_DCH in cell 1. SS configures its downlink transmission power
settings according to columns "T1" in table 8.3.4.7. UE shall be triggered to transmit a MEASUREMENT REPORT
message which includes the primary scrambling code for cell 2 according to IE "Intra-frequency event identity", which
is set to '1a' in the SYSTEM INFORMATION BLOCK TYPE 11. SS transmits an ACTIVE SET UPDATE message
which contains an unexpected critical message extension. The UE shall transmit an ACTIVE SET UPDATE FAILURE
message, stating the reason " Message extension not comprehended " in the IE "Protocol error information". UE then
send another MEASUREMENT REPORT to SS 4s after step 2. SS calls for generic procedure C.3 to check that UE is
in CELL_DCH state.
Expected Sequence
UE SS
table 8.3.4.7
using AM RLC which does not
include any IEs except IE
"Message Type"
4 ACTIVE SET UPDATE FAILURE The message shall state
"Message extension not
comprehended " in IE
"protocol error information".

Use the ACTIVE SET UPDATE message as defined in [9] TS 34.108 clause 9, with the following exceptions:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1231
ACTIVE SET UPDATE FAILURE (Step 4)
- Protocol Error Cause

Message extension not comprehended

After step 3 the UE shall transmit an ACTIVE SET UPDATE FAILURE message on the DCCH. In this message, the
value "Message extension not comprehended" shall be set in IE "Protocol Error Information".
After step 4 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC, 4s
after step 2.
8.3.4.8 Active set update in soft handover: Radio Link addition in multiple radio link
environment

specified in TS 25.331 subclause 8.6, unless specified otherwise in the following. The UE shall:
1>clear that entry;

Reference
To confirm that the UE communicates with the SS on all radio link in the active set and keeps the connection when
some of the radio links are faded out.
Initial Condition
System Simulator: 4 cells - Cell 1, 2, 3 and 7 are active. The chip-timing between the cells shall always be within 148
chip.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1232
Test Procedure
Table 8.3.4.8-1
Cell UTRA RF Channel Number
Cell 1 Ch. 1
Cell 2 Ch. 1
Cell 3 Ch. 1
Cell 7 Ch. 1

Table 8.3.4.8-2
Time
Parameter Unit T0 T1 T2 T3 T4 T5 T6 T7
Cell 1 CPICH Ec dBm/3.84MHz
-60 -60 -60 -60 -75 -75 -75 -60
-75 -60 -60 -60 -60 -75 -75 -75
-75 -75 -60 -60 -60 -60 -75 -75
-75 -75 -75 -60 -60 -60 -60 -75

Table 8.3.4.8-1 defines the UTRA RF Channel Number for the different cells. Table 8.3.4.8-2 illustrates the downlink
power to be applied for the 4 cells at various time instants of the test execution.
Initially, the UE goes to connected mode and establishes a radio access bearer in CELL_DCH state in cell 1.
SS configures its downlink transmission power settings according to columns "T1" in table 8.3.4.8-2. UE shall be
triggered to transmit a MEASUREMENT REPORT message which includes the primary scrambling code for cell 2,
DPCH in cell 1 and cell 2. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION message. Then SS
transmits a UE CAPABILITY INFORMATION CONFIRM message.
cell 3 and then the SS transmits to the UE an ACTIVE SET UPDATE message in cell 1 and cell 2 on DCCH using AM
RLC which includes the IE "Radio Link Addition Information" (e.g. Downlink DPCH information and other optional
DPCH in cell 1, cell 2 and cell 3. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION message.
Then SS transmits a UE CAPABILITY INFORMATION CONFIRM message.
cell 7 and then the SS transmits to the UE an ACTIVE SET UPDATE message in cell 1, cell 2 and cell 3 on DCCH
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1233
using AM RLC which includes the IE "Radio Link Addition Information" (e.g. Downlink DPCH information and other
optional parameters relevant for the additional radio links with Primary CPICH info used for the reference ID).
DPCH in cell 1, cell 2, cell 3 and cell 7. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION
message. Then SS transmits a UE CAPABILITY INFORMATION CONFIRM message.
SS configures its downlink transmission power settings according to columns "T4" in table 8.3.4.8-2. The UE shall
continue to communicate through at least cell 2, cell 3 and cell 7. The UE shall transmit a MEASUREMENT REPORT
message which indicates the event '1b' for cell 1.
DPCH in cell 2, cell 3 and cell 7. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION message.
Then SS transmits a UE CAPABILITY INFORMATION CONFIRM message.
continue to communicate through at least cell 3 and cell 7. The UE shall transmit a MEASUREMENT REPORT
message which indicates the event '1b' for cell 2.
DPCH in cell 3 and cell 7. The UE shall transmit a UE CAPABILITY ENQUIRY INFORMATION message. Then SS
transmits a UE CAPABILITY INFORMATION CONFIRM message.
continue to communicate through at least cell 7. The UE shall transmit a MEASUREMENT REPORT message which
indicates the event '1b' for cell 3.
UE CAPABILITY INFORMATION CONFIRM.
continue to communicate through at least cell 1. The UE shall transmit a MEASUREMENT REPORT message which
indicates the event '1b' for cell 7.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1234
Expected sequence
UE SS
1 SS configures its downlink transmission
power settings according to columns "T1" in
table 8.3.4.8-2.
2 MEASUREMENT REPORT See specific message contents for this
message (event 1a for cell 2)
3 ACTIVE SET UPDATE SS transmits this message in cell 1 on
downlink DCCH using AM RLC. The
message includes IE "Radio Link Addition
Information". (e.g. Downlink DPCH
information and other optional parameters
relevant for the additional radio link with
Primary CPICH info used for the reference ID
in cell 2)
4 ACTIVE SET UPDATE COMPLETE The UE shall configure new radio link to cell
2 without interfering with existing connections
on the radio link in cell 1.
5 UE CAPABILITY ENQUIRY Use default message. Sent on cell 1 and cell
2.
table 8.3.4.8-2.
10 ACTIVE SET UPDATE SS transmits this message in cell 1 and cell 2
on downlink DCCH using AM RLC. The
message includes IE "Radio Link Addition
Information". (e.g. Downlink DPCH
in cell 3)
on the radio links in cell 1 and cell 2.
12 UE CAPABILITY ENQUIRY Use default message. Sent on cell 1, cell 2
and cell 3.
table 8.3.4.8-2.
17 ACTIVE SET UPDATE SS transmits this message in cell 1, cell 2
and cell 3 on downlink DCCH using AM RLC.
The message includes IE "Radio Link
Addition Information". (e.g. Downlink DPCH
in cell 7)
on the radio links in cell 1, cell 2 and cell 3.
19 UE CAPABILITY ENQUIRY Use default message. Sent on cell 1, cell 2,
cell 3 and cell 7.
table 8.3.4.8-2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1235
message (event 1b for Cell 1)
24 UE CAPABILITY ENQUIRY Use default message. Sent on cell 2, cell 3
and cell 7.
table 8.3.4.8-2.
29 UE CAPABILITY ENQUIRY Use default message. Sent on cell 3 and cell
7.
table 8.3.4.8-2.
34 UE CAPABILITY ENQUIRY Use default message. Sent on cell 7.
table 8.3.4.8-2.
message (event 1b for cell 7)
39 UE CAPABILITY ENQUIRY Use default message. Sent on cell 1.
42 CALL C.3 If the test result of C.3 indicates that UE is in
CELL_DCH state, the test passes, otherwise
it fails.

TS 34.108, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1236
- Intra-frequency measurement reporting criteria
- Parameters required for each event 3 kinds
- Reporting Range Constant 5dB
- Cells forbidden to affect Reporting range Not Present
- W 0.0
- Hysteresis 0.0
- Threshold Used Frequency Not Present
- Time to trigger 640
- Amount of reporting 4
- CHOICE reported cell Report cell within active set and/or monitored set cells
on used frequency
- Triggering condition 1 Active set cells
- W 0.0
- Hysteresis 0.0
- Reporting deactivation threshold Not Present
- Amount of reporting Not Present
- Reporting interval Not Present
on used frequency

The contents of SIB12 in cell 1, and SIB11 and SIB12 in cell 2, cell 3, and cell 7 shall be in accordance with the default
SIBs as specified in TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1237
Message Type
Measured Results
- Cell measured results Cell 1. See Note 1
Event results
- Primary CPICH info Cell 2.

NOTE 1: Cell measured results for cells 1 and 2 may appear in any order.
NOTE 2: Cell measured results for cells 3 and 7 may or may not be present (depends upon the capability of the UE
and test uncertainties in power level). If present they may appear in any order.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1238
Radio link addition information Cell 2
- CHOICE mode FDD
information

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1239
Message Type
Measured Results
Event results

test uncertainties in power level).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1240
- CHOICE mode FDD
information

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1241
Message Type
Measured Results
Event results

NOTE 1: Cell measured results for cells 1, 2, 3 and 7 may appear in any order.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1242
- CHOICE mode FDD
information

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1243
Message Type
Measured Results
- Cell measured results Cell 2. See Note 1.
Event results

test uncertainties in power level).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1244
Message Type
Measured Results
- Cell measured results Cell 3. See Note 1.
Event results

NOTE 1: Cell measured results for cells 3 and 7 may appear in any order.
NOTE 2: Cell measured results for cell 1 and cell 2 may or may not be present (depends upon the capability of the
UE and test uncertainties in power level). If present they may appear in any order.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1245
Message Type
Measured Results
- Cell measured results Cell 7.
Event results

NOTE 1: Cell measured results for cells 1. 2 and 3 may or may not be present (depends upon the capability of the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1246
Message Type
Measured Results
- Cell measured results Cell 1.
Event results

NOTE 1: Cell measured results for cells 2, 3 and 7 may or may not be present (depends upon the capability of the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1247
8.3.5 Hard Handover
[Editor's note: This test is included in the "Physical channel reconfiguration", "Radio bearer establishment", "Radio
bearer reconfiguration", "Radio bearer release" and "Transport channel reconfiguration".]
8.3.6 Inter-system hard handover from GSM to UTRAN
The content of this clause has been moved to 3GPP TS 51.010-1, clause 60.
8.3.7 Inter-system hard handover from UTRAN to GSM
Clauses 8.3.7 contains test procedures to be used for executing Inter-system Handover from UTRAN to GSM tests.
Table 8.3.7-1 contains a summary of the different combinations of parameters being tested, together with a reference to
the appropriate generic test procedure. If a test uses a parameter which the UE under test does not support, the test shall
be skipped. Test cases in this clause are applicable only to the UE supporting both UTRAN and GSM. The test TEST
USIM shall support service 27 to carry out these test cases.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1248
Table 8.3.7-1
From To State
of call
Ref.
clause
Exec
counter
Remark
UTRAN AMR
(conversational/speech/
uplink:12.2 DL:12.2 kbps/CS
RAB +
uplink:3.4 DL3.4 kbps SRBS)
GSM AMR U10 8.3.7.1 1 call active
state
UTRAN AMR
RAB +
GSM EFR U10 8.3.7.1 2 call active
state
UTRAN AMR
RAB +
GSM FR U10 8.3.7.1 3 call active
state
UTRAN AMR
RAB +
GSM HR U10 8.3.7.1 4 call active
state
UTRAN
(Streaming/unknown/
RAB +
uplink:3.4 DL:3.4 kbps SRBS)
GSM
14.4 kbps CS data
U10 8.3.7.2 1 Same data
rate
UTRAN
(Streaming/unknown/
RAB +
GSM
14.4 kbps HSCSD
U10 8.3.7.2a 1 Same data
rate
UTRAN
(Streaming/unknown/
RAB +
GSM
28.8 kbps CS data
U10 8.3.7.2 2 Same data
rate
UTRAN
(Streaming/unknown/
RAB +
GSM
57.6 kbps CS data
U10 8.3.7.2 3 Same data
rate
UTRAN
(Streaming/unknown/
RAB +interactive/ background
UL: 32kbps, DL: 32 kbps (note) +
GSM
14.4 kbps CS data
U10 8.3.7.3 1 Data rate
down grading
UTRAN
(Streaming/unknown/
GSM
14.4 kbps HSCSD
U10 8.3.7.3a 1 Data rate
down grading
UTRAN
(Streaming/unknown/
GSM
14.4 kbps HSCSD
U10 8.3.7.3 2 Data rate
down grading
UTRAN
(Streaming/unknown/
GSM
28.8 kbps CS data
U10 8.3.7.3 3 Data rate
down grading
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1249
UTRAN AMR
RAB +
GSM FR U1 8.3.7.4 1 During call
establishment
UTRAN AMR
RAB +
GSM FR U10 8.3.7.5 1 failure case
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
UTRAN AMR
RAB +
GSM FR U1 8.3.7.13 1 call under
establishment

NOTE: The PS part is only applicable for UE supporting CS+PS service.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1250
8.3.7.1 Inter system handover from UTRAN/To GSM/Speech/Success
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT
handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1>establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT
message". This IE contains a message specified in another standard, as indicated by the IE "System type", and
carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio
access technology. The correspondence between the value of the IE "System type", the standard to apply and the
message contained within IE "Inter RAT message" is shown in the following:
Value of the
IE " System
type"
Standard to appl y Inter RAT Message
GSM GSM TS 04.18, version 8.5.0 or later HANDOVER COMMAND
cdma2000 TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or
later, TIA/EIQ/IS-834 or later

1>if the IE "System type" has the value "GSM":
2>if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3>set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2>if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
1>apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1>if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2>if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS
domain":
3>connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources
indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in
the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access
technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1>if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful
delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on
signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2>retransmit those NAS messages to the network on the newly established radio connection to the target radio
access technology.
1>clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1251
Reference(s)
TS 25.331 clause 8.3.7.3, 8.3.7.4.
To test that the UE supporting both GSM and UTRAN hands over from a UTRAN serving cell to the indicated channel
of GSM target cell when the UE is in the speech call active state and receives an HANDOVER FROM UTRAN
COMMAND.
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 shall be referenced for the
default parameters of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by
the UE.
- UE supports both GSM and UTRAN Radio Access Technologies,
- UE supports GSM AMR,
- UE supports GSM EFR,
- UE supports GSM FR,
- UE supports GSM HR,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS.
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR. The SS configures the appropriate traffic
channel on the GSM cell, then sends HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the
target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall
configure itself accordingly and switch to the new channel on the target GSM cell. The SS checks whether the handover
is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS through GSM cell.
Depending on the PIXIT parameters the above procedure is executed maximum four times, each time with a different
target channel in the GSM cell.
For UEs where the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the whole test
should be repeated to cover these frequencies in order to verify the correct handling of the IE "Frequency band".
Inter RAT handover is normally preceded by the configuration and activation of compressed mode (depending on UE
capabilities/ PIXIT) and the configuration of inter- RAT measurements. The inter RAT handover is normally initiated
by the SS upon receiving an event triggered measurement report. The verification of this functionality is covered by
other subclauses.
Expected sequence
This sequence is performed for a maximum execution counter M =1, 2, 3, 4, depending on the PIXIT parameters.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1252
UE SS
1 UE The SS bring the UE into UTRAN U10 state in cell 1
2 SS The SS configures a traffic channel on cell 9 (GSM cell):
for GSM AMR (M =1); or
for GSM EFR (M =2); or
for GSM FR (M =3); or
for GSM HR (M =4).
3 HANDOVER FROM UTRAN
COMMAND-GSM
Send on cell 1 (UTRAN cell) and the message indicates:
the target channel for GSM AMR (M =1); or
the target channel for GSM EFR (M =2); or
the target channel for GSM FR (M =3); or
the target channel for GSM HR (M =4).
4 UE The UE accepts the handover command and switches to
the GSM traffic channel specified in the HANDOVER
FROM UTRAN COMMAND-GSM
5 HANDOVER ACCESS The SS receives this burst on the traffic channel of cell 9
(GSM cell) It implies that the UE has switched to GSM
cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
9 PHYSICAL INFORMATION
10 SABM
11 UA
12 HANDOVER COMPLETE The SS receives the message on the traffic channel of
GSM cell.
The SS performs a postamble and restores both UE and
SS to their initial state so that the test can be repeated
from step 1 for executions 2,3 and 4 (if required).

HANDOVER FROM UTRAN COMMAND-GSM
Message Type
RRC transaction identifier Arbitrarily selects one integer between 0 to 3
Activation time now
RAB Info
- NAS Synchronization Indicator Not present
- Re-establishment timer Use T315
Inter-system message
- CHOICE System type GSM
- Frequency Band Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this
test. Otherwise set to "GSM/DCS 1800 Band"
- CHOICE GSM message Single GSM message
- Message GSM HANDOVER COMMAND formatted and coded
according to GSM specifications as Variable Length BIT
STRING without Length Indicator. The first/ leftmost/ most
significant bit of the bit string contains bit 8 of the first octet
of the GSM message. The contents of the HANDOVER
COMMAND see next table.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1253
For execution 1:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M =2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL
MODE IE is included with value =speech full rate or half rate version 3

For execution 2:

HANDOVER COMMAND

For execution 3:

HANDOVER COMMAND

For execution 4:

HANDOVER COMMAND

At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has
switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1254
8.3.7.2 Inter system handover from UTRAN/To GSM/Data/Same data rate/Success
The UE shall:
Value of the
IE " System
type"

domain":
access technology.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1255
Reference(s)
TS 25.331 Clause 8.3.7.3, 8.3.7.4.
To test that the UE hands over to the indicated channel of same data rate in the GSM target cell when it is in the data
call active state in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
Initial conditions
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s)
supported by the UE.Related ICS/IXIT statement(s)
- UE supports UTRAN Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB +uplink:3.4 DL:3.4 kbps SRBs,
- UE supports GSM 14.4 kbps data ( full rate traffic channel for 14.4 kbit/s user data (TCH/F14.4)),
Test Procedure
The SS brings the UE into data call active state (CC state U10) with Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS
RAB +uplink:3.4 DL:3.4 kbps SRBs . The SS configures a 14.4 kbps data channel on the GSM cell, then sends a
HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through
DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch
to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE
transmits the HANDOVER COMPLETE message to the SS in GSM cell.

UEs for which the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the test should cover
these frequencies in order to verify the correct handling of the IE "Frequency band".
other subclauses.
Expected sequence
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1256
UE SS
1 UE The SS bring the UE into UTRAN U10 state in cell 1, the
configuration is:
Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB +
uplink:3.4 DL:3.4 kbps SRBs ;

for GSM 14.4 kbps data .
COMMAND GSM
the target channel
for GSM 14.4 kbps data
cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
10 SABM
11 UA
GSM cell.

:
Message Type
Activation time now
RAB Info
- CHOICE GSM message GSM message List
according to GSM specifications as BIT STRING(1..512).
contains bit 8 of the first octet of the GSM message. The
contents of the HANDOVER COMMAND see next table.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1257
HANDOVER COMMAND
MODE IE is included with value =data, 14.5 kbit/s radio interface rate (14.4 kbit/s user data (TCH/F14.4))

NOTE: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets.
Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify
that size constraint is still met.
8.3.7.2a Inter system handover from UTRAN/To GSM/Data/Same data rate/Extended
Rates/Success
The UE shall:
Value of the
IE " System
type"

domain":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1258
access technology.
Reference(s)
TS 25.331 Clause 8.3.7.3, 8.3.7.4.
To test that the UE hands over to the indicated channel of same data rate in the GSM target cell when it is in the data
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 or clause 26.13.1.3 (for
HSCSD) shall be referenced for the default parameters of cell 9.
- UE supports GSM 14.4 kbps data (HSCSD),
- UE supports GSM 28.8 kbps data (HSCSD or enhanced circuit switched full rate traffic channel for 28.8 kbit/s
user date (E-TCH/F28.8)),
- UE supports GSM 57.6 kbps data,
Test Procedure
The SS brings the UE into data call active state (CC state U10) with a suitable configuration (e.g.
Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB +uplink:3.4 DL:3.4 kbps SRBs for M =1). The SS configures
an appropriate traffic channel (e.g. 14.4 kbps HSCSD data channel for M =1)on the GSM cell, then sends a
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1259
HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through
DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch
to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE
transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Depending on the PIXIT parameters the above procedure is executed maximum three times, each time with a different
UEs for which the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the test should cover
these frequencies in order to verify the correct handling of the IE "Frequency band".
other subclauses.
Expected sequence
This sequence is performed for a maximum execution counter M =1, 2, 3, depending on the PIXIT parameters.
UE SS
configuration is:
uplink:3.4 DL:3.4 kbps SRBs (for M =1);
uplink:3.4 DL:3.4 kbps SRBs (for M =3).
for GSM HSCSD 14.4 kbps data (M =1); or
for GSM 28.8 kbps data (M =2); or
for GSM 57.6 kbps data (M =3).
COMMAND GSM
the target channel
for GSM HSCSD 14.4 kbps data (M =1); or
for GSM 28.8 kbps data (M =2); or
cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
10 SABM
11 UA
GSM cell.
from step 1 for executions 2 and 3 (if required).

:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1260
Message Type
Activation time now
RAB Info
- CHOICE GSM message GSM message List
according to GSM specifications as BIT STRING(1..512).
contains bit 8 of the first octet of the GSM message. The

For execution 1:
HANDOVER COMMAND
Same as the HANDOVER COMMAND in clause 26.13.1.3 of GSM 51.010, except that the Description of a multi-
slot configuration supporting 14.4 kbps user data.

For execution 2:

If the UE supports enhanced circuit switched full rate traffic channel for 28.8 kbps user data:
HANDOVER COMMAND
MODE IE is included with value =data, 29.0 kbit/s radio interface rate (28.8 kbit/s user data (E-TCH/F28.8))

If the UE supports HSCSD:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1261
HANDOVER COMMAND

For execution 3:

HANDOVER COMMAND

8.3.7.3 Inter system handover from UTRAN/To GSM/Data/Data rate down
grading/Success
The UE shall:
Value of the
IE " System
type"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1262
domain":
access technology.
Reference(s)
TS 25.331 Clause 8.3.7.3, 8.3.7.4.
To test that the UE hands over to the indicated channel of lower data rate in the GSM target cell when it is in the data
Initial conditions
- UE supports GSM 14.4 kbps data ( full rate traffic channel for 14.4 kbit/s user data (TCH/F14.4)),
- ,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480 GSM-PCS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1263
- UE support CS and PS service.
Test Procedure
a 14.4 kbps data channel on the GSM cell, then sends a HANDOVER FROM UTRAN COMMAND indicating the
traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the
command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether
the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM
cell.
Upon completion of the handover, depending on UE capabilities, the UE performs routing area update and (re-)
establishes the connection towards the PS domain.
Depending on the PIXIT parameters the above procedure is executed maximum two times, each time with different
Expected sequence
This sequence is performed for a maximum execution counter M =1, 2 depending on the PIXIT parameters.
UE SS
configuration is:
uplink:3.4 DL:3.4 kbps SRBs (for M =2).
for GSM 14.4 kbps data (M =1 and 2).
COMMAND-GSM
the target channel
for GSM 14.4 kbps data (M =1 and 2).
cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
10 SABM
11 UA
GSM cell.
13 ROUTING AREA UPDATE Conditional on Class A UE.
from step 1 for execution 2 (if required).

For execution 1:
Same as the message contents of clause 8.3.7.2 Procedure 1 for M =1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1264
For execution 2:
Same as the message contents of clause 8.3.7.2 Procedure 1 for M =1.

8.3.7.3a Inter system handover from UTRAN/To GSM/Data/Data rate down
grading/Extended Rates/Success
The UE shall:
Value of the
IE " System
type"

domain":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1265
access technology.
Reference(s)
TS 25.331 Clause 8.3.7.3, 8.3.7.4.
To test that the UE hands over to the indicated channel of lower data rate in the GSM target cell when it is in the data
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 or clause 26.13.1.3 (for
HSCSD) shall be referenced for the default parameters of cell 9.
- UE supports GSM 14.4 kbps data (HSCSD),
- UE supports GSM 28.8 kbps data (HSCSD or enhanced circuit switched full rate traffic channel for 28.8 kbit/s
user date (E-TCH/F28.8)),
- UE support CS and PS service.
Test Procedure
a traffic channel (e.g. 14.4 kbps HSCSD data channel for M =1)on the GSM cell, then sends a HANDOVER FROM
UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving
UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of
the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER
COMPLETE message to the SS in GSM cell.
Upon completion of the handover, depending on UE capabilities, the UE performs routing area update and (re-)
establishes the connection towards the PS domain.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1266
Depending on the PIXIT parameters the above procedure is executed maximum three times, each time with different
Expected sequence
This sequence is performed for a maximum execution counter M =1, 2, 3, depending on the PIXIT parameters.
UE SS
configuration is:
uplink:3.4 DL:3.4 kbps SRBs (for M =2 and 3).
for GSM 14.4 kbps HSCSD data (M =1 and 2); or
COMMAND-GSM
the target channel
for GSM HSCSD 14.4 kbps data (M =1 and 2); or
cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
10 SABM
11 UA
GSM cell.
13 ROUTING AREA UPDATE Conditional on Class A UE.
from step 1 for executions 2 and 3 (if required).

For execution 1:
Same as the message contents of clause 8.3.7.2.2 Procedure 2 for M =1.
For execution 2:
For execution 3:
8.3.7.3a.5 Test requirement
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1267
8.3.7.4 Inter system handover from UTRAN/To GSM/Speech/Establishment/Success
The UE shall:
Value of the
IE " System
type"

domain":
access technology.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1268
Reference(s)
TS 25.331 Clause 8.3.7.3, 8.3.7.4.
To test that the UE hands over to the indicated channel in the GSM target cell when it is in the call establishment phase
in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
Initial conditions
- UE supports UTRAN AMR,
Test Procedure
The UE is triggered to initialise an MO speech call. During the call establishment phase, after the SS receives SETUP
message the SS configures a dedicated channel on the GSM cell, then sends the UE an HANDOVER FROM UTRAN
COMMAND indicating the dedicated channel in the target GSM cell. After the UE receives the command it shall
configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is
performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1269
Expected sequence
UE SS
1 UE To trigger the UE to initialise an MO call
2 SETUP U1
3 SS The SS configures a dedicated channel SDCCH on the
GSM cell.
COMMAND-GSM
the dedicated channel SDCCH.
the GSM dedicated channel specified in the HANDOVER
6 HANDOVER ACCESS The SS receives this burst on the dedicated channel of
cell 9 (GSM cell) It implies that the UE has switched to
GSM cell.
7 HANDOVER ACCESS
8 HANDOVER ACCESS
9 HANDOVER ACCESS
11 SABM
12 UA
13 HANDOVER COMPLETE The SS receives the message on the dedicated channel
of GSM cell.

Message Type
Activation time now
RAB Info Not present

HANDOVER COMMAND
Same as the HANDOVER COMMAND for M =4 in clause 26.6.5.2 of GSM 51.010 except that Mode of first
channel IE should be set to signalling only

At step 13 the SS shall receive HANDOVER COMPLETE message on the dedicated channel of the GSM cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1270
8.3.7.5 Inter system handover from UTRAN/To GSM/Speech/Failure
If the UE does not succeed in establishing the connection to the other target radio access technology, it shall
1>revert back to the UTRA configuration;
1>establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN
COMMAND;

transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below:
2>set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN
COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2>clear that entry;
2>set the IE "Inter-RAT handover failure" to "physical channel failure".
1>When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission:
Reference(s)
TS 25.331 Clause 8.3.7.5.
To test that the UE reactivates the old configuration and uses this to transmit a HANDOVER FROM UTRAN
FAILURE message to the network including IE "Inter-RAT Handover failure cause" which is set to "physical channel
failure", when it receives an HANDOVER FROM UTRAN COMMAND and the connection to GSM for handover can
not be established.
To verify that after the handover failure the UE resumes previously configured compressed mode patterns and
measurements.
Initial conditions
the UE.
- UE supports UTRAN AMR,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1271
- UE supports compressed mode (FDD only).
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR. If the UE requires compressed mode (refer
ICS/IXIT), the SS sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to configure the
compressed mode pattern sequence parameters. When the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE is received from the UE, the SS sends a MEASUREMENT CONTROL message. This message is used to
provide measurement control parameters (GSM RSSI) to the UE and to start compressed mode for the measurement if
required according to the UE capabilities. The UE replies according to request by sending RRC: MEASUREMENT
REPORT messages periodically to SS (reporting period is 1000 ms).
The SS sends a HANDOVER FROM UTRAN COMMAND indicating a dedicated channel (not configured) of the
target GSM cell to the UE through DCCH of the serving UTRAN cell. The UE receives the command and configures
itself accordingly but can not complete the handover. The SS checks that the handover is failed by checking that the UE
transmits the HANDOVER FROM UTRAN FAILURE message to the SS using the old UTRAN configuration.
After the handover failure, the UE re-activates compressed mode (if configured) and resumes periodic measurement
reporting including sending MEASUREMENT REPORT messages periodically to SS.
Expected sequence
UE SS
1 UE The SS bring the UE into U10 state in UTRAN cell 1. If
the UE does not require compressed mode (refer
ICS/IXIT), then goto step 1c.
1a PHYSICAL CHANNEL
RECONFIGURATION
Compressed mode pattern sequence parameters are
loaded to UE.
1b PHYSICAL CHANNEL
RECONFIGURATION
COMPLETE

1c MEASUREMENT CONTROL SS provides GSM RSSI measurement control
parameters to UE. Compressed mode for GSM RSSI
measurement is started.
1d MEASUREMENT REPORT UE reports measurement results of GSM RSSI
measurement to SS.

COMMAND-GSM
the target channel for GSM FR which does not exist in
the GSM cell.
FAILURE
The SS receives the message via the old UTRAN
configuration.
5a MEASUREMENT REPORT The SS shall verify that the UE resumes periodic
measurement reporting for GSM RSSI measurements

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1272
PHYSICAL CHANNEL RECONFIGURATION (Step 1a)
Use the same message sub-type as in TS 34.108 titled "Speech in CS", with the following exceptions:
- TGPSI 1
- TGCFN Not present

- TGMP GSM Carrier RSSI Measurement
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD Undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
CHOICE UL/DL Mode UL&DL or UL-only or DL-only (depends on UE's
Measurement capability)
- Downlink compressed mode method SF/2
- Uplink compressed mode method SF/2
- Downlink frame type A
- DeltaSIR1 2.0
- DeltaSIR2After2 Not Present
- TGPSI 2
- TGCFN Not present

- TGMP GSM Initial BSIC identification
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 2.0
- N identify abort 128

MEASUREMENT CONTROL (Step 1c)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1273
- Periodic Reporting / Event Trigger Reporting Mode Periodical reporting
CHOICE measurement type
- inter-RAT measurement
- inter-RAT measurement object list
CHOICE Inter-RAT Cell Removal Remove no inter-RAT cells
- inter-RAT cell id 0
CHOICE Radio Access Technology GSM
- Cell individual offset 0
- Cell selection and re-selection info Not present
- BSIC BSIC1
- Band indicator DCS 1800 or PCS 1900 (dependent on band used)
- BCCH ARFCN 1
- BSIC BSIC2
- Band indicator DCS 1800 or PCS 1900 (dependent on band used)
- BCCH ARFCN 7
- Cell for measurement Not present
- inter-RAT measurement quantity
- Measurement quantity for UTRAN quality
estimate
Not present
CHOICE system GSM
- Measurement quantity GSM carrier RSSI
- Filter coefficient 0
- BSIC verification required not required
- inter-RAT reporting quantity
UTRAN estimated quality FALSE
CHOICE system GSM
- Observed time difference to to GSM cell
reporting indicator
FALSE
- GSM carrier RSSI reporting indicator TRUE
CHOICE reported cell
- Reported cells within active set or within
virtual active set or of the other RAT
CHOICE report criteria
- Periodical reporting criteria
- Amount of reporting infinity
Physical channel information elements
- DPCH compressed mode status info
- TGPSI 1
- TGPS status flag Activate
- TGPSI 2
- TGPS status flag Deactivate
- TGCFN Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1274
MEASUREMENT REPORT (Step 1d and step 5a)
Measurement identity Check to see if set to 15
Measured Results
- CHOICE measurement Check to see if set to "Inter-RAT measured results list"
- Inter-RAT measured result list
- CHOICE system GSM
- Measured GSM cells
- GSM carrier RSSI Check to see if present
CHOICE BSIC Non verified BSIC
- BCCH ARFCN Check that is set to "1"
- Observed time difference to GSM cell Check that not present
- GSM carrier RSSI Check that measurement result is reasonable
Measured results on RACH Check that not present
Additional Measured results Check that not present
Event results Check that not present

The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in
- System type GSM
- Message GSM HANDOVER COMMAND formatted as BIT STRING
(1..512). The contents of the HANDOVER COMMAND see
next table.

HANDOVER COMMAND
MODE IE is included with value =speech full rate or half rate version 1 and that the indicated target channel for
GSM FR does not exist in the GSM cell

HANDOVER FROM UTRAN FAILURE
The contents of this message is identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS
34.108 clause 9.
After step 4 the SS shall receive HANDOVER FROM UTRAN FAILURE message using the old UTRA configuration.
After step 5 the UE shall correctly report the GSM RSSI value.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1275
8.3.7.6 Inter system handover from UTRAN/To GSM/Speech/Failure (L2
Establishment)
If the UE does not succeed to establish the connection to the other radio access technology , as is unable to obtain L2
establishment it shall
- resume the connection to UTRAN using the resources used before receiving the HANDOVER FROM UTRAN
COMMAND message; and
- transmit the HANDOVER FROM UTRAN FAILURE message on uplink DCCH using AM RLC.
Reference(s)
TS 04.06 Clause 5.4.1.3
TS 04.08 Clause 3.1.5
To Test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message,
which is set to "physical channel failure" in IE "Inter_RAT HO failure cause", when it receives a HANDOVER FROM
UTRAN COMMAND and the connection to GSM for handover cannot be established due to failure in L2
establishment.
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 51010-1 section 26.6.5.1 shall be referenced for
the default parameters of cell 9.
UE: CC State U10 in cell 1
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. SS activates a
dedicated GSM traffic channel then sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel
of the target GSM cell to the UE through DCCH of the serving UTRAN cell. When the UE does not succeed in
establishing the connection to the target radio access technology it shall revert back to UTRA configuration establish
the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND transmit
the HANDOVER FROM UTRAN FAILURE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1276
Expected sequence
UE SS
1 UE The SS brings the UE into UTRAN U10 state in cell 1
2 SS The SS configures cell 9 as a GSM cell with traffic
channel.
COMMAND-GSM
The target channel.

cell.
6 HANDOVER ACCESS
7 HANDOVER ACCESS
8 HANDOVER ACCESS
9 PHYSICAL INFORMATION Allows a proper transmission by the MS.
Sent in unacknowledged mode as soon as the SS has
detected a HANDOVER ACCESS.
As soon as MS detects it then it stops T3124.
On SS side T3105 could be started N times at the
maximum as long as the step 8 is not performed
10 SABM To establish L2 connection
11 SS

SS does not sent UA frame
12 UE On T200 expiration, SS sends N200 times the SABM
frame (steps 10)
Then MS deactivates new channels and reactivates old
UTRA resources it had before receiving the handover
command
FAILURE
The SS receives the message on the old channel of
UTRAN cell. Sent in acknowledge mode
The cause in the IE "inter-RAT change failure" is set to
"physical channel failure"

Same as the message contents of clause 8.3.7.1 for M =3.
Message Type
RRC transaction identifier Checked to see if it matches the same value used in the
corresponding downlink HANDOVER FROM UTRAN
COMMAND GSM message
compared against the XMAC-I value computed by SS. The
Inter-RAT handover failure
-Inter-RAT handover failure cause physical channel failure
Inter-system message Not Checked

The SS shall receive HANDOVER FROM UTRAN FAILURE message on the old channel of the UTRAN cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1277
8.3.7.7 Inter system handover from UTRAN/To GSM/Speech/Failure (L1
Synchronization)
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
COMMAND;

1>transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified
below:
2>clear that entry;
Reference(s)
TS 25.331 Clause 8.3.7.5
To test that the UE reactivates its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message,
which is set to "physical channel failure" in IE "Inter-RAT Handover failure cause", when it receives a HANDOVER
FROM UTRAN COMMAND and the connection to GSM for handover cannot be established due to failure in L1
Synchronization.
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 section 26.6.5.1 shall be referenced for the
UE supports GSM FR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480 GSM-PCS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1278
Test Procedure
The SS brings the UE into call active state (CC state U10). The SS activates a dedicated channel in the GSM cell, then
sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE
through DCCH using the UTRAN configuration. The UE receives the command, configures itself accordingly and
sends the HANDOVER ACCESS burst. Upon receiving this burst, the SS turns off the dedicated channel indicated to
the UE, so the UE cannot complete the handover. The SS checks that the UE reverts to the old UTRA configuration by
checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS via the old UTRAN
configuration.
Expected sequence
UE SS
1 UE The SS brings the UE into UTRAN U10 state in cell 1.
2 SS The SS configures a traffic channel on cell 9 (GSM cell).
COMMAND-GSM
The target channel for GSM FR in GSM Cell.

cell.
6 HANDOVER ACCESS
7 SS The target GSM Traffic Channel is Switched off
FAILURE
configuration.
The cause in the IE "inter-RAT change failure" is set to
"physical channel failure"

- System type GSM
next table.

HANDOVER COMMAND

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1279
34.108 clause 9.
After step 7 the SS shall receive HANDOVER FROM UTRAN FAILURE message via the old UTRA configuration.
8.3.7.8 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid Inter-
RAT message)
If the UE does not succeed to establish the connection to the other radio access technology, as the Inter-RAT message
received is invalid, it shall
- resume the connection to UTRAN using the resources used before receiving the INTER-SYSTEM HANDOVER
- transmit the INTER-SYSTEM HANDOVER FAILURE message on uplink DCCH using AM RLC. When the
successful delivery of the INTER-SYSTEM FAILURE message has been confirmed by RLC, the procedure
ends.
Reference
3GPP TS 25.331 clause 8.3.7.6
To Test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message,
which is set to "Inter-RAT protocol error" in IE "Inter_RAT HO failure cause", when it receives a Handover From
UTRAN message, with the IE "Inter-RAT message" received within the HANDOVER FROM UTRAN COMMAND
message not including a valid inter RAT handover message in accordance with the protocol specifications for the target
RAT.
Initial conditions
System Simulator : 1 UTRAN cell.
UE : CC State U10 in cell 1
UE supports GSM FR,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1280
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. The SS then sends an
HANDOVER FROM UTRAN COMMAND message not including a valid inter RAT handover message in accordance
with the protocol specifications for the target RAT, to the UE through DCCH of the serving UTRAN cell. The UE
receives the command and finds that the Inter Rat message is Invalid. The SS checks that the handover is failed by
checking that the UE transmits the INTER-SYSTEM HANDOVER FAILURE message to the SS in UTRAN cell.
Expected sequence
UE SS
2 HandoverFromUTRAN Command-
GSM
Send on cell 1 (UTRAN cell) and the message carries an
Invalid HANDOVER FROM UTRAN COMMAND -GSM
3

InterSystemHandoverFailure The SS receives the message on the old channel of
UTRAN cell.

Message Type
Activation time Now
RAB Info Not present
- Frequency Band GSM/DCS 1800 Band

HANDOVER COMMAND
Contains an Invalid Handover Command.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1281
Message Type
COMMAND GSM message
-Inter-RAT handover failure cause Inter-RAT protocol error
Inter-system message Not checked

In step 3 the SS shall receive INTER-SYSTEM HANDOVER FAILURE message on the old channel of the UTRAN
cell.
8.3.7.9 Inter system handover from UTRAN/To GSM/Speech/Failure (Unsupported
configuration)
8.3.7.9.2 Conformance requirement:
If:

- the UTRAN instructs the UE to use a non-supported configuration; or

the UE shall:
1>transmit a HANDOVER FROM UTRAN FAILURE message, setting the information elements as specified
below:
2>clear that entry;
2>set the IE "Inter-RAT handover failure" to "configuration unacceptable";
2>when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for
transmission:
3>resume normal operation as if the invalid HANDOVER FROM UTRAN COMMAND message has not
been received;
Reference
3GPP TS 25.331 clause 8.3.7.8
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1282
To test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message,
which is set to "configuration unacceptable" in IE "Inter-RAT Handover failure cause", when it receives a
HANDOVER FROM UTRAN COMMAND message, with the IE "GSM message" containing a HANDOVER
COMMAND message including a configuration not supported by the UE.
Initial conditions
UE supports GSM FR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480 GSM-PCS.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR on the UTRAN cell. The SS then sends an
HANDOVER FROM UTRAN COMMAND message including a configuration not supported by the UE in the
HANDOVER COMMAND that is contained in the IE "GSM message", to the UE through DCCH using the UTRAN
configuration. The UE receives the command and finds that the configuration given in Inter Rat message is not
supported. The SS checks that the UE reverts to the old UTRA configuration by checking that the UE transmits the
HANDOVER FROM UTRAN FAILURE message to the SS using the old UTRA configuration.
Expected sequence
UE SS
COMMAND -GSM
Send using the UTRAN configuration and the message
carries an unsupported configuration.
3

HANDOVER FROM UTRAN
FAILURE
configuration.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1283
- System type GSM
- Message GSM HANDOVER COMMAND formatted as Variable
Length BIT STRING without Length Indicator. The

HANDOVER COMMAND
Same as the HANDOVER COMMAND for M =2 in clause 26.6.5.1 of GSM 51.010, except that the frequency band
is set to a value not supported by the UE.

-Inter-RAT handover failure cause configuration unacceptable

After step 2 the SS shall receive a HANDOVER FROM UTRAN FAILURE message via the old UTRA configuration.
8.3.7.10 Inter system handover from UTRAN/To GSM/Speech/Failure (Reception by
UE in CELL_FACH)

If the UE does not succeed to establish the connection to the other radio access technology, as the Message received is
not compatible with receiver state, it shall
ends.
Reference
3GPP TS 25.331 clause 8.3.7.8a
The UE shall keep its old configuration when the UE receives a HANDOVER FROM UTRAN COMMAND message
when in CELL_FACH state and then transmit a HANDOVER FROM UTRAN COMMAND FAILURE message on the
DCCH using AM RLC, which sets value "protocol error" in IE "Inter_RAT HO failure cause" and is set to "Message
not compatible with receiver state" in IE "Protocol error cause".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1284
Initial conditions
System Simulator : 1 UTRAN Cell
UE : RRC State CS-DCCH_FACH (state 6-6) as specified in clause 7.4 of TS 34.108, on Cell 1
UE supports GSM FR,
The UE is in RRC is in State CS-DCCH_FACH (state 6-6) as specified in clause 7.4 of TS 34.108, on cell 1.
Test Procedure
The SS starts GSM cell without activating any dedicated channel in the cell, then sends INTER-SYSTEM
HANDOVER COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH of the
serving UTRAN cell. The UE receives the command and configures itself accordingly but cannot complete the
handover. The SS checks that the handover is failed by checking that the UE transmits the INTER-SYSTEM
HANDOVER FAILURE message to the SS in UTRAN cell.
Expected sequence
UE SS
1 UE The SS brings the UE into CS-DCCH_FACH (state 6-6)
_FACH state in cell 1
2 InterSystemHandoverCommand-
GSM
The target channel for GSM
3 InterSystemHandoverFailure The SS receives the message on the old channel of
UTRAN cell.

Same as the message contents of clause 8.3.7.1 for M =3.
Message Type
COMMAND GSM message
-Inter-RAT handover failure cause Protocol Error
-Diagnostics Type Type1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1285
-Protocol Error Cause Message Not Compatible With Receiver State
Inter-system message Not Checked

After step 2 the SS shall receive INTER-SYSTEM HANDOVER FAILURE message on the old channel of the UTRAN
cell.
8.3.7.11 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid
message reception)
If the UE does not succeed to establish the connection to the other radio access technology, as the Handover Message
received is short to decode into a valid message, it shall
ends.
Reference
The UE shall keep its old configuration when the UE receives a Handover From UTRAN message, which will be short
to decode into a valid Handover From UTRAN message. It shall then transmit an RRC STATUS message on the uplink
DCCH. The IE "Protocol error information" shall contain an IE "Protocol error cause" set to "ASN.1 violation or
encoding error";
Initial conditions
UE : CC State U10 in cell 1
UE supports GSM FR,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1286
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. The SS then sends an
HANDOVER FROM UTRAN COMMAND message, which will be short to decode into a valid Handover From
UTRAN message, to the UE through DCCH of the serving UTRAN cell. The SS checks that the handover is failed by
checking that the UE transmits an RRC STATUS message on the uplink DCCH. The IE "Protocol error information"
shall contain an IE "Protocol error cause" set to "ASN.1 violation or encoding error";
Expected sequence
UE SS
2 HandoverFromUTRAN Command-
GSM
Send on cell 1 (UTRAN cell) and the message is short in
length to be decoded into a valid Handover From UTRAN
command
3

RRCStatus The SS receives the message on the old channel of
UTRAN cell.

A Short Message that shall not result in a valid Handover From UTRAN Command shall be sent.
RRC STATUS (Step 3)
Protocol error information Checked to see if set to "ASN.1 Violation or Encoding
error"

In step 3 the SS shall receive RRC Status message in the UTRAN cell.

8.3.7.12 Inter system handover from UTRAN/To GSM/Speech/Failure (Physical
channel Failure and Reversion Failure)
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
COMMAND;
1>if the UE does not succeed to establish the UTRA physical channel(s):
2>perform a cell update procedure according to subclause 8.3.1 in TS 25.331with cause "Radio link failure";
2>when the cell update procedure has completed successfully:
3>proceed as below.
1>transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified
below:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1287
2>clear that entry;
Reference
3GPP TS 25.331 clause 8.3.7.5
The UE shall perform a cell update when the UE fails to revert to the old configuration after the detection of physical
channel failure in the target RAT cell as given in the HANDOVER FROM UTRAN COMMAND message. After the
UE completes the cell update procedure, the UE shall transmit a HANDOVER FROM UTRAN FAILURE message on
the DCCH using AM RLC, including IE "failure cause" set to "physical channel failure".
Initial conditions
System Simulator : 2 cells - Cell 1 is UTRAN, Cell 9 is GSM. GSM 11.10-1 section 26.6.5.1 shall be referenced for the
the UE.
UE supports GSM FR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS.
Test Procedure
The SS and brings the UE into call active state (CC state U10) with AMR on the UTRAN cell. The SS sends a
HANDOVER FROM UTRAN COMMAND indicating a dedicated channel (not configured) of the target GSM cell to
the UE through DCCH using the UTRAN configuration. The UE receives the command and configures itself
accordingly but cannot complete the handover and wants to revert to the old configuration, but the UE cannot revert to
the old configuration because the SS released the old configuration. The UE transmits a CELL UPDATE message on
uplink CCCH with IE "Cell update cause" set to "radio link failure". The SS shall transmit CELL UPDATE CONFIRM
message on downlink CCCH after receiving CELL UPDATE message. The UE transmits PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC and subsequently transmits the
HANDOVER FROM UTRAN FAILURE message to the SS using the new UTRA configuration, on the DCCH using
AM RLC, setting the value of IE "failure cause" to " physical channel failure".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1288
Expected sequence
UE SS

COMMAND-GSM
Send using the old UTRA configuration and the message
indicates:
the target channel for GSM FR.
COMMAND message that is contained within the
HANDOVER FROM UTRAN COMMAND -GSM message
cell. Upon receiving this burst, SS removes both the
target GSM Traffic Channel and the UTRA physical
channel (DPCH) allocated to the mobile before handover
command transmission. As a result not only the handover
will fail, but also the reversion to the old UTRA
configuration.
6 CELL UPDATE The value "radio link failure" shall be set in IE "Cell
update cause".
7 CELL UPDATE CONFIRM This message include IE "Physical channel information
elements".
8 The SS configures the dedicated physical channel
according to the IE "Physical channel information
elements" included in the CELL UPDATE CONFIRM
message.
9 PHYSICAL CHANNEL
RECONFIGURATION
COMPLETE

FAILURE
The IE "failure cause" shall be set to "physical channel
failure"

Same as the message contents of clause 8.3.7.1 for Execution 3.
clause 9,with the following exceptions:
U-RNTI

in TS 34.108, clause 9,with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1289
-UplinkDPCH Info Same as RRC CONNECTION SETUP message used to
- DPCCH power offset -80dB (i.e. ASN.1 IE value of 40)
- PC Preamble 1 frame
- SRB delay 7 frames
- Power Control Algorithm Algorithm1
- TPC step size 1dB
- Number of DPDCH Not Present(1)
- spreading factor Reference to TS34.108 clause 6.10 Parameter Set
- Number of FBI bit Reference to TS34.108 clause 6.10 Parameter Set
Downlink information common for all radio links Same as RRC CONNECTION SETUP message used to
CHOICE Mode FDD
- Timing indicator Initialise
- CFN-targetSFN frame offset Not Present
- DPC mode 0 (single)
- CHOICE mode FDD
- Power offset PPilot-DPDCH 0
- Fixed or Flexible Position Reference to TS34.108 clause 6.10 Parameter Set
- CHOICE SF Reference to TS34.108 clause 6.10 Parameter Set
- DPCH compressed mode info Not Present
- TX Diversity mode None
- Default DPCH Offset Value Arbitrary set to value 0..306688 by step of 512
- Code number SF-1(SF is reference to TS34.108 clause 6.10 Parameter
Set)

CELL UPDATE CONFIRM (Step 7) (3.84 Mcps TDD)
in TS34.108, clause 9, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1290
Frequency info
- CHOICE mode TDD
CHOICE Mode TDD
- CHOICE mode TDD
- CHOICE SyncCase Not Present
- CHOICE mode TDD
- DL CCTrCh List
- TFCS ID 1
- Time info

CELL UPDATE CONFIRM (Step 7) (1.28 Mcps TDD)
in TS34.108, clause 9, with the following exceptions:
Frequency info
- CHOICE mode TDD
CHOICE Mode TDD
- CHOICE mode TDD
- CHOICE mode TDD
- DL CCTrCh List
- TFCS ID 1
- Time info

HANDOVER FROM UTRAN COMMAND
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1291
- System type GSM
next table.

HANDOVER COMMAND

34.108 clause 9.
After step 5 the SS shall receive an CELL UPDATE message.
After step 8 the SS shall receive an PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
After step 9 the SS shall receive an INTER-SYSTEM HANDOVER FAILURE message via the new UTRA
configuration.
8.3.7.13 Inter system handover from UTRAN/To GSM/ success / call under
establishment

The UE shall:
Value of the
IE " System
type"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1292
domain":
.
Upon successfully completing the handover, UTRAN should:
1>release the radio connection; and
1>remove all context information for the concerned UE.
1>if the USIM is present:
2>store the current START value for every CN domain in the USIM [50];
2>if the "START" stored in the USIM [50] for a CN domain is greater than or equal to the value
"THRESHOLD" of the variable START_THRESHOLD:
3>delete the ciphering and integrity keys that are stored in the USIM for that CN domain;
3>inform the deletion of these keys to upper layers.
1>if the SIM is present:
2>store the current START value for every CN domain in the UE;
2>if the "START" stored in the UE for a CN domain is greater than or equal to the value "THRESHOLD" of
the variable START_THRESHOLD:
3>delete the ciphering and integrity keys that are stored in the SIM for that CN domain;
3>inform the deletion of these keys to upper layers.
access technology.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1293
Reference
3GPP TS 25.331 clause 8.3.7.3, 8.3.7.4
To test that the UE supporting both GSM and UTRAN performs handover from UTRAN to the indicated channel of
GSM target cell when the UE receives a HANDOVER FROM UTRAN COMMAND in call establishment phase.
To test that the UE continues the call in the GSM cell, after succesful completion of the Handover.
Initial conditions
UE : CC State U0 (NULL state) in cell 1.
UE supports GSM FR,
The UE is in CC state U0 (NULL) on cell 1.
Test Procedure
The SS activates the UTRAN cell and GSM Cell. The UE is triggered to initialise an MO speech call. During the call
establishment phase, the SS is configured to not transmit the RLC Acknowledgment for SETUP message. SS configures
a dedicated channel in GSM Cell, then sends the UE an HANDOVER FROM UTRAN COMMAND indicating the
dedicated channel in the target GSM cell. After the UE receives the command it shall configure itself accordingly and
switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE
transmits the HANDOVER COMPLETE message to the SS in GSM cell. The SS checks MS correctly retransmits CC
SETUP message, that was not acknowledged by UTRAN RLC Layer before the Handover, following completion of the
handover to GSM cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1294
Expected sequence
UE SS
1 UE To trigger the UE to initialise an MO call
2 SETUP SS does not Acknowledge it
3 SS The SS starts the GSM cell and configure a dedicated
channel SDCCH.
COMMANDGSM
Send via the UTRA configuration and the message
indicates:
the dedicated channel SDCCH.
the GSM dedicated channel specified in the HANDOVER
6 HANDOVER ACCESS The SS receives this burst on the dedicated channel of
cell 9 (GSM cell) It implies that the UE has switched to
GSM cell.
7 HANDOVER ACCESS
8 HANDOVER ACCESS
9 HANDOVER ACCESS
11 Void
12 Void
13 HANDOVER COMPLETE The SS receives the message on the dedicated channel
of GSM cell.
14 -> SETUP The SS receives the message on the dedicated channel
of GSM cell.
15 <- CHANNEL RELEASE

- System type GSM
- Message GSM HANDOVER COMMAND formatted as Variable
Length BIT STRING without Length Indicator. The

HANDOVER COMMAND
Same as the HANDOVER COMMAND for M =4 in clause 26.6.5.2 of GSM 11.10-1 version 8.2.0 Release 1999

At step 14 the SS shall receive SETUP message on the dedicated channel of the GSM cell.
8.3.8 Inter system cell reselection to UTRAN
[Editor's note: This test is FFS until R2000 core specification will be defined.]
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1295
8.3.9 Inter system cell reselection from UTRAN
8.3.9.1 Cell reselection if cell becomes barred or S<0; UTRAN to GPRS
(CELL_FACH)
Test to verify that if both a GSM/GPRS and UTRAN network is available, the UE performs cell reselection from
UTRAN to GSM/GPRS if the UTRAN cell becomes barred or S falls below zero.
1. The purpose of the inter-RAT cell reselection procedure from UTRAN is to transfer, under the control of the UE
and to some extent the UTRAN, a connection between the UE and UTRAN to another radio access technology
(e.g. GSM/GPRS).
2. This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH. When the UE based on
received system information makes a cell reselection to a radio access technology other than UTRAN, e.g.
GSM/GPRS, according to the criteria specified in [4], the UE shall:
1>If the NAS procedures associated with inter-system change specified in [5] require the establishment of a
connection:
2>initiate the establishment of a connection to the target radio access technology according to its specifications.
3. When the UE has succeeded in reselecting a cell in the target radio access technology, the UE shall:
1>release all UTRAN specific resources.
References
TS 25.331, clause 8.3.9
1. To verify that the UE performs reselection from UTRAN to GPRS in the state CELL_FACH on the following
occasions:
- Serving cell becomes barred.
- S<0 for serving cell.
2. To verify when the UE has succeeded in reselecting a cell in the target radio access technology and has initiated
the establishment of a connection, it shall release all UTRAN specific resources.
Initial conditions
System Simulator: 3 cells Cell 1 is UTRAN FDD, Cell 2 is GPRS and Cell 3 is GSM. 51.010 clauses 20.22 and 40.1.1
shall be referenced for the default parameters of cell 2. 51.010 clause 26.6.5.1 shall be referenced for the default
parameters of cell 3.
All cells belong to the same PLMN and location area.
The Inter-RAT Cell Info List of Cell 1 (UTRAN) refers to Cell 2 (GPRS) and Cell 3 (GSM).
The 3G Neighbour Cell Description of Cell 2 (GPRS) and Cell 3 (GSM) refers to Cell 1 (UTRAN).
UE: PS-DCCH+DTCH_FACH (State 6-11) in cell 1 as specified in clause 7.4 of TS 34.108, one PS domain RAB is
established.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1296
Related ICS/IXIT statement
- UE supports both GSM/GPRS and UTRAN Radio Access Technologies,
- UE supports UTRAN interactive/ background UL: 64kbps, DL: 64 kbps/PS RAB +uplink:3.4 DL:3.4 kbps
SRBs,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480,
Step a-c:
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
CPICH Ec (FDD) dBm -60
P-CCPCH RSCP (TDD) dBm -60
Qrxlevmin dBm -101
Srxlev* dBm 41

Parameter Unit
Cell 2
(GPRS)
Test Channel 1
RXLEV_ACCESS_
MIN
dBm -100
C1* dBm 25
FDD_Qmin dB -20
FDD_Qoffset dBm 0

Parameter Unit
Cell 3
(GSM)
Test Channel 2
RXLEV_ACCESS_
MIN
dBm -100
C1* dBm 15
FDD_Qmin dB -20
FDD_Qoffset dBm 0

Step d-f:
Parameter Unit
Cell 1
(UTRAN)
Tbarred S 80
Step i:
Parameter Unit
Cell 1
(UTRAN)
Qrxlevmin DB -101 ->-41
Srxlev* DB 41 ->-19

Test procedure
a) The SS activates cells 1, 2, and 3. The SS monitors cells 1, 2 and 3 for random access requests from the UE.
c) The SS brings the UE to PS-DCCH+DTCH_FACH (State 6-11).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1297
e) The SS sends SYSTEM INFORMATION CHANGE INDICATION message to UE to inform UE of the
modification in the system information.
f) The SS waits for channel request from the UE to establish a Temporary Block flow.
g) The SS pages the UE with PAGING TYPE 2 in Cell 1 (UTRAN), if UE does not respond by transmitting an
upper layer message to answer this page, it means UE has released the UTRAN resources.
i) Step a-e) is repeated with the same initial conditions except that in step d), Qrxlevmin is increased, so S will
become negative instead of being barred.
In step f), the UE shall respond on Cell 2
In step g), the UE shall not respond in UTRAN cell.
In step i), the UE shall respond on Cell 2 after Qrxlevmin is increased.
8.3.9.2 Cell reselection if cell becomes barred or S<0; UTRAN to GPRS (URA_PCH)
Test to verify that if both a GSM/GPRS and UTRAN network is available, the UE performs cell reselection from
UTRAN to GSM/GPRS if the UTRAN cell becomes barred or S falls below zero.
(e.g. GSM/GPRS).
2. This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH.
When the UE based on received system information makes a cell reselection to a radio access technology other
than UTRAN, e.g. GSM/GPRS, according to the criteria specified in [4], the UE shall.
connection:
References
TS 25.331, clause 8.3.9
To verify that the UE performs reselection from UTRAN to GPRS in the state URA_PCH on the following occasions:
- Serving cell becomes barred.
- S<0 for serving cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1298
Initial conditions
System Simulator: 2 cells Cell 1 is UTRAN FDD, Cell 9 is GPRS. 51.010 clauses 20.22 and 40.1.1 shall be
referenced for the default parameters of cell 9.
The Inter-RAT Cell Info List of Cell 1 (UTRAN) refers to Cell 9 (GPRS).
The 3G Neighbour Cell Description of Cell 9 (GPRS) refers to Cell 1 (UTRAN)
UE: URA_PCH (state 6-13) in cell 1 as specified in clause 7.4 of TS 34.108.
SRBs,
Step a-c:
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
Qrxlevmin dBm -101
Srxlev* dBm 41

Parameter Unit
Cell 9
(GPRS)
Test Channel 1
RXLEV_ACCESS_
MIN
dBm -100
C1* dBm 20
FDD_Qmin dB -20
FDD_Qoffset dBm 0

Step d-f:
Parameter Unit
Cell 1
(UTRAN)
Tbarred s 80
Step i:
Parameter Unit
Cell 1
(UTRAN)
Srxlev* dB 40 ->-20

Test procedure
a) The SS activates cells 1 and 9. The SS monitors cells 1 and 9 for random access requests from the UE.
c) The SS brings the UE to URA_PCH (State 6-13).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1299
e) The SS sends Paging Type1 message to UE to inform UE of the modification in the system information.f) The
SS waits for channel request from the UE to establish Temporary Block flow
g) The SS pages the UE with PAGING TYPE 1 in cell 1 (UTRAN), if UE does not respond with RRC Connection
Request, it means UE has released the UTRAN resources.
i) Step a-e) is repeated with the same initial conditions except that in step d), Qrxlevmin is increased, so S will
become negative instead of being barred.
In step f), the UE shall respond on Cell 9.
In step g), the UE shall not respond in UTRAN cell.
In step i), the UE shall respond on Cell 9 after Qrxlevmin is increased.
8.3.9.3 Cell reselection if S<0; UTRAN to GPRS (UE in CELL_FACH fails to
complete an inter-RAT cell reselection)
If the inter-RAT cell reselection fails, the UE shall:
1>resume the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection
procedure.
References
TS 25.331, clause 8.3.9.4
To verify if the inter-RAT cell reselection fails before the UE in CELL_FACH succeeds in initiating the establishment
of a connection to the GPRS cell, the UE shall:
- resume the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection
procedure.
Initial conditions
System Simulator: 2 cells Cell 1 is UTRAN FDD, Cell 9 is GPRS with PBCCH. 51.010 clauses 20.22 and 40.1.1 shall
be referenced for the default parameters of cell 9.
The 3G Neighbour Cell Description of Cell 9 (GPRS) refers to Cell 1 (UTRAN)
UE: PS-DCCH+DTCH_FACH (State 6-11) in cell 1 (UTRAN) as specified in clause 7.4 of TS 34.108, one PS domain
RAB is established.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1300
SRBs,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.

Step a-c:
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
Qrxlevmin dBm -101
Treselections s 5
Srxlev* dBm 41

Parameter Unit
Cell 9
(GPRS)
Test Channel 1
GPRS_RXLEV_A
CCESS_MIN
dBm -100
C1* dBm 20
C32* dB 20
CellBarred barred

Step d:
Parameter Unit
Cell 1
(UTRAN)
Srxlev* dB 41->-19

Step f:
Parameter Unit
Cell 1
(UTRAN)
Qrxlevmin dB -41->-101
Srxlev* dB -19 ->41

Test procedure
a) The SS activates cells 1 and 9. The SS monitors cells 1and 9 for random access requests from the UE.
d) The SS increases Qrxlevmin, so S will become negative.
f) The SS decreases Qrxlevmin, so S will become positive (After the expiry of the timer Treselection)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1301
g) SS calls for generic procedure C.2 in cell 1 (UTRAN) to check that UE is in CELL_FACH state. The UE
resumes the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection
procedure
- FACH measurement occasion info
- fACH-meas-occasion-coeff 3
- inter-freq-FDD-meas-ind FALSE
- inter-freq-TDD-meas-ind FALSE
- inter-RAT-meas-ind
- RAT-Type GSM

In step f, the UE remains in CELL_FACH in cell 1.
8.3.9.4 Cell reselection if S<0; UTRAN to GPRS (UE in CELL_PCH fails to complete
an inter-RAT cell reselection)
If the inter-RAT cell reselection fails, the UE shall:
1>resume the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection
procedure.
References
TS 25.331, clause 8.3.9.4
To verify if the inter-RAT cell reselection fails before the UE in CELL_PCH succeeds in initiating the establishment of
a connection to the GPRS cell, the UE shall:
- resume the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection
procedure.
Initial conditions
The 3G Neighbour Cell Description of Cell 9 (GPRS) refers to Cell 1 (UTRAN).
UE: CELL_PCH (State 6-12) in cell 1 (UTRAN) as specified in clause 7.4 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1302
SRBs,
Step a-c:
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
Qrxlevmin dBm -101
Treselections s 5
Srxlev* dBm 41

Parameter Unit
Cell 9
(GPRS)
Test Channel 1
RXLEV_ACCESS_
MIN
dBm -100
C1* dBm 20
FDD_Qmin dB -20
FDD_Qoffset dBm 0
CellBarred barred

Step d:
Parameter Unit
Cell 1
(UTRAN)
Srxlev* dB 41 ->-19

Step f:
Parameter Unit
Cell 1
(UTRAN)
Srxlev* dB -19->41

Test procedure
c) The SS brings the UE to CELL_PCH (State 6-12).
d) The SS increases Qrxlevmin, so S will become negative.
e) The SS sends Paging Type 1 message to UE to inform UE of the modification in the system information.f) The
SS decreases Qrxlevmin, so S will become positive (After the expiry of the timer Treselection)
g) SS calls for generic procedure C.4 in cell 1 (UTRAN) to check that UE is in CELL_PCH state. The UE resumes
the connection to UTRAN using the resources used before initiating the inter-RAT cell reselection procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1303
In step f, the UE remains in CELL_PCH in cell 1.
8.3.9.5 Successful Cell Reselection with RAU Q
offset
value modification; UTRAN to
GPRS (CELL_FACH)
(e.g. GSM/GPRS).
2. This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH.
When the UE based on received system information makes a cell reselection to a radio access technology other
than UTRAN, e.g. GSM/GPRS, according to the criteria specified in [4], the UE shall.
connection:
References
TS 25.331, clause 8.3.9
To verify that the UE performs reselection correctly considering the Q
offset
value broadcast in SIB 11.
Initial conditions
The 3G Neighbour Cell Description of Cell 2 (GPRS) refers to Cell 1 (UTRAN).
established.
SRBs,
Step a-c:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1304
Parameter Unit
Cell 1
(UTRAN)
Test Channel 1
Qrxlevmin dBm -101
Srxlev* dBm 41

Parameter Unit
Cell 2
(GPRS)
Test Channel 1
RXLEV_ACCESS_
MIN
dBm -100
C1* dBm 30
FDD_Qmin dB -20
FDD_Qoffset dBm 0

Step d:
Parameter Unit
Cell 1
(UTRAN)
Qoffset1s,n dBm 20
Step f:
Parameter Unit
Cell 2
(GPRS)
RF Signal Level dBm -70 ->-50
C1* dBm 30 ->50

Test procedure
d) Q
offset
value is modified at UTRAN such that it makes the GSM cell look the best.
f) The SS increases signal level on Cell 2 to 50 dBm.
g) The SS monitors for random access requests from the UE.
h) The SS pages the UE with PAGING TYPE 1 in cell 1 (UTRAN), if UE does not respond with RRC Connection
Request, it means UE has released the UTRAN resources.
In step g), the UE shall respond on Cell 2 and enter PACKET TRANSFER mode after performing the routing area
update procedure.
In step h), the UE shall not respond in UTRAN cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1305
8.3.11 Inter-RAT cell change order from UTRAN
8.3.11.1 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Success
The purpose of the inter-RAT cell change order procedure is to transfer, under the control of the network, a connection
between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in
CELL_DCH and CELL_FACH state. This procedure may be used when no RABs are established or when the
established RABs are only from PS domain. This procedure may not be used when there is no PS signalling connection.
The procedure is initiated when UTRAN orders a UE in CELL_DCH or CELL_FACH state, to make a cell change to a
radio access technology other than UTRAN, e.g. GSM.
To initiate the procedure, UTRAN sends a CELL CHANGE ORDER FROM UTRAN message.
The UE shall be able to receive a CELL CHANGE ORDER FROM UTRAN message and perform a cell change order
to another RAT, even if no prior UE measurements have been performed on the target cell.
If the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity "PS
domain", or if the variable ESTABLISHED_SIGNALLING_CONNECTIONS includes the CN domain identity "CS
domain":
1>the UE behaviour is not specified.
The UE shall:
1>start timer T309; and
1>establish the connection to the other radio access technology, as specified within IE "Target cell description".
This IE specifies the target cell identity, in accordance with the specifications for that other RAT. In case the
target cell is a GSM/ GPRS cell, IE "Target cell description" may also include IE "NC mode", which specifies
the cell selection mode to be applied in the target cell; and
1>if IE "NC mode" is not included in the CELL CHANGE ORDER FROM UTRAN:
2>retrieve it from the target cell as specified in [43];
2>act upon IE "NC mode" as specified in [43].
1>if the IE "RAB Information List" is included in the CELL CHANGE ORDER FROM UTRAN message:
2>ignore the contents of the IE "RAB Information List".
technology and the signalling procedure are outside the scope of this specification. In case of GSM/GPRS
proceed according to the procedure Network control cell reselection procedure as specified in [44].
The UE regards the procedure as completed when it has received a successful response from the target RAT, e.g. in case
of GSM when it received the response to a (PACKET) CHANNEL REQUEST in the new cell.
Upon successful completion of the cell change order, the UE shall:
1>stop timer T309;
Upon indication of the UE having successfully completed the cell change order, UTRAN should:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1306
NOTE: The release of the UMTS radio resources is initiated from another RAT.
Reference(s)
TS 25.331 clause 8.3.11, B.6
To test that the UE shall be able to receive a CELL CHANGE ORDER FROM UTRAN message in CELL_DCH state
and perform a cell change to another RAT, even if no prior UE measurements have been performed on the target cell.
Initial conditions
System Simulator: 2 cells - Cell 1 is UTRAN, Cell 2 is GPRS. 51.010 clauses 20.22 and 40.1.1 shall be referenced for
UE: PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of TS 34.108, one PS domain RAB is
established.
SRBs,
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_DCH (State 6-10). The SS starts GPRS cell,
then sends CELL CHANGE ORDER FROM UTRAN indicating the target cell description, GPRS cell, to the UE
through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and
switch to the new channel on the target GPRS cell. The SS checks whether the cell change is performed by checking
that the UE receives a successful response to the CHANNEL REQUEST message from the SS through GPRS cell. The
UE sends a RA UPDATE REQUEST message to indicate that the UTRAN UE context needs to be transferred to
GPRS.
UE SS
1 UE The SS brings the UE into PS-DCCH+DTCH_DCH (State
6-10) in cell 1
2 SS The SS configures cell 2 as a GSM cell with GPRS
enabled
3 CELL CHANGE ORDER FROM
UTRAN
the target cell description for GPRS.
4 UE The UE accepts the cell change command and switches
to the GPRS cell specified in the CELL CHANGE
ORDER FROM UTRAN
5 CHANNEL REQUEST The SS receives this burst on the RACH of cell 2 to
establish temporary block flow (GPRS cell). It implies that
the UE has switched to GPRS cell.
6 IMMEDIATE ASSIGNMENT Uplink dynamic allocation. Sent on AGCH.
7 ROUTING AREA UPDATE
REQUEST

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1307
CELL CHANGE ORDER FROM UTRAN
Message Type
writes to this IE.
Activation time Now
Target cell description
- CHOICE Radio Access Technology
- GSM
- BSIC BSIC1
- Band Indicator DCS 1800 band used
- BCCH ARFCN 1
- NC mode NOT PRESENT

After step 3 the UE shall transmit a CHANNEL REQUEST message on RACH.

8.3.11.2 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Success
The purpose of the inter-RAT cell change order procedure is to transfer, under the control of the network, a connection
between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in
CELL_DCH and CELL_FACH state. This procedure may be used when no RABs are established or when the
established RABs are only from PS domain. This procedure may not be used when there is no PS signalling connection.
The procedure is initiated when UTRAN orders a UE in CELL_DCH or CELL_FACH state, to make a cell change to a
radio access technology other than UTRAN, e.g. GSM.
To initiate the procedure, UTRAN sends a CELL CHANGE ORDER FROM UTRAN message.
The UE shall be able to receive a CELL CHANGE ORDER FROM UTRAN message and perform a cell change order
to another RAT, even if no prior UE measurements have been performed on the target cell.
If the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity "PS
domain", or if the variable ESTABLISHED_SIGNALLING_CONNECTIONS includes the CN domain identity "CS
domain":
The UE shall:
1>start timer T309; and
1>establish the connection to the other radio access technology, as specified within IE "Target cell description".
This IE specifies the target cell identity, in accordance with the specifications for that other RAT. In case the
target cell is a GSM/ GPRS cell, IE "Target cell description" may also include IE "NC mode", which specifies
the cell selection mode to be applied in the target cell; and
1>if IE "NC mode" is not included in the CELL CHANGE ORDER FROM UTRAN:
2>retrieve it from the target cell as specified in [43];
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1308
2>act upon IE "NC mode" as specified in [43].
1>if the IE "RAB Information List" is included in the CELL CHANGE ORDER FROM UTRAN message:
2>ignore the contents of the IE "RAB Information List".
technology and the signalling procedure are outside the scope of this specification. In case of GSM/GPRS
proceed according to the procedure Network control cell reselection procedure as specified in [44].
Upon successful completion of the cell change order, the UE shall:
1>stop timer T309;
Upon indication of the UE having successfully completed the cell change order, UTRAN should:
NOTE: The release of the UMTS radio resources is initiated from another RAT.
Reference(s)
TS 25.331 clause 8.3.11, B.6
To test that the UE shall be able to receive a CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state
and perform a cell change to another RAT, even if no prior UE measurements have been performed on the target cell.
of GSM when it received the response to a CHANNEL REQUEST in the new cell.
Initial conditions
System Simulator: 2 cells - Cell 1 is UTRAN, Cell 2 is GPRS with PBCCH. 51.010 clauses 20.22 and 40.1.1 shall be
UE: PS-DCCH+DTCH_FACH (state 6-11) in cell 1 as specified in clause 7.4 of TS 34.108, one PS domain RAB is
established.
SRBs,
- UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_FACH (state 6-11). The SS starts GPRS cell,
through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1309
switch to the new channel on the target GPRS cell. The SS checks whether the cell change is performed by checking
that the UE receives a successful response to the CHANNEL REQUEST message from the SS through GPRS cell. The
UE sends a RA UPDATE REQUEST message to indicate that the UTRAN UE context needs to be transferred to
GPRS.

UE SS
1 UE The SS brings the UE into PS-DCCH_DTCH_FACH
(State 6-11) in cell 1
enabled
UTRAN
the target cell description for GPRS.
to the GPRS specified in the CELL CHANGE ORDER
FROM UTRAN
5 PACKET CHANNEL REQUEST The SS receives this burst on PRACH of cell 2 (GPRS
cell) to establish temporary block flow. It implies that the
UE has switched to GPRS cell.
6 PACKET UPLINK ASSIGNMENT Uplink dynamic allocation
Sent on PAGCH.
7 ROUTING AREA UPDATE
REQUEST

Message Type
writes to this IE.
Activation time Now
- GSM
- BSIC BSIC1
- BCCH ARFCN 1
- NC mode NOT PRESENT

After step 3 the UE shall transmit a CHANNEL REQUEST message on RACH.

8.3.11.3 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Failure
(T309 expiry)
If:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1310
- timer T309 expires prior to the successful establishment of a connection to the target RAT; or
- if the establishment of the connection to the other RAT failed due to other reasons e.g. (random) access failure,
rejection due to lack of resources:
the UE shall:
1>if it received the CELL CHANGE ORDER FROM UTRAN message in state CELL_DCH:
2>establish the UTRA physical channel(s) used at the time for reception of CELL CHANGE ORDER FROM
UTRAN;
2>if the UE does not succeed in establishing the UTRA physical channel(s):
3>perform a cell update procedure according to subclause 8.3.1 with cause "Radio link failure";
4>proceed as below.
2>transmit the CELL CHANGE ORDER FROM UTRAN FAILURE message setting the information elements
as specified below:
3>clear that entry;
3>set the IE "Inter-RAT change failure" to "physical channel failure".
2>When the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layer
for transmission, the procedure ends.
Reference(s)
TS 25.331 clause 8.3.11
To verify that when UE received CELL CHANGE ORDER FROM UTRAN message in CELL_DCH state and if the
establishment of the connection to the other RAT failed due to expiry of timer T309 prior to the successful
establishment of a connection to the target RAT:
a. revert back to the UTRA configuration;
b. establish the UTRA physical channel(s) used at the time for reception of CELL CHANGE ORDER FROM
UTRAN;
c. transmit the CELL CHANGE ORDER FROM UTRAN FAILURE message and set the IE "Inter-RAT change
failure" to "physical channel failure".
Initial conditions
UE: PS-DCCH_DCH (State 6-7) in cell 1 as specified in clause 7.4 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1311
Test Procedure
The SS starts the UTRAN cell and brings the UE into state PS-DCCH_DCH (State 6-7). The SS starts GPRS cell, then
sends CELL CHANGE ORDER FROM UTRAN indicating the target cell description, GPRS cell, to the UE through
DCCH of the serving UTRAN cell. The UE starts the timer T309. After the UE receives the command it shall configure
itself accordingly but cannot complete the cell change, as SS does not respond to the CHANNEL REQUEST message
transmitted by UE till the expiry of T309 timer. The SS checks that the cell change has failed by checking that the UE
transmits the CELL CHANGE ORDER FROM UTRAN FAILURE message to the SS in UTRAN cell.
UE SS
1 UE The SS bring the UE into PS-DCCH _DCH (State 6-7) in
cell 1
enabled
UTRAN
the target cell description for GSM/GPRS.
4 UE UE starts the timer T309. The UE accepts the cell change
command and switches to the GPRS specified in the
5 CHANNEL REQUEST The SS receives this burst on RACH of cell 2 (GPRS cell)
to establish temporary block flow
6 SS does not respond to the channel request.
UE sends M +1 CHANNEL REQUEST messages
The SS does not transmit a response and wait for T309
timer to expire.
UTRAN FAILURE
UTRAN cell.

Message Type
writes to this IE.
Activation time Now
- GSM
- BSIC BSIC1
- BCCH ARFCN 1
- NC mode Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1312
CELL CHANGE ORDER FROM UTRAN FAILURE
Message Type
corresponding downlink CELL CHANGE ORDER FROM
UTRAN message
Inter-RAT change failure
-Inter-RAT change failure cause physical channel failure

In step 5 the UE shall transmit a CHANNEL REQUEST message on RACH.
In step 7 the SS shall receive CELL CHANGE ORDER FROM UTRAN FAILURE message on the old channel of the
UTRAN cell.

8.3.11.4 Inter-RAT cell change order from UTRAN/To GPRS/CELL_DCH/Failure
(Physical channel Failure and Reversion Failure)
If:
the UE shall:
1>if it received the CELL CHANGE ORDER FROM UTRAN message in state CELL_DCH:
2>establish the UTRA physical channel(s) used at the time for reception of CELL CHANGE ORDER FROM
UTRAN;
2>if the UE does not succeed in establishing the UTRA physical channel(s):
3>perform a cell update procedure according to subclause 8.3.1 with cause "Radio link failure";
4>proceed as below.
as specified below:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1313
3>clear that entry;
for transmission, the procedure ends.
Reference(s)
TS 25.331 clause 8.3.11
To verify that when UE received CELL CHANGE ORDER FROM UTRAN message in CELL_DCH state and if the
establishment of the connection to the other RAT failed due to other reasons e.g. (random) access failure, rejection due
to lack of resources:
a. revert back to the UTRA configuration;
b. if the UE does not succeed in establishing the UTRA physical channel(s):
- perform a cell update procedure with cause "Radio link failure";
c. when the cell update procedure is completed successfully, it transmits the CELL CHANGE ORDER FROM
UTRAN FAILURE message and set the IE "Inter-RAT change failure" to "physical channel failure".
Initial conditions
established.
SRBs,
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_DCH (state 6-10). The SS starts GPRS cell,
through DCCH of the serving UTRAN cell. The UE receives the command and configures itself accordingly but cannot
complete the cell change and wants to revert to the old configuration, but the UE cannot revert to the old configuration
because the SS shall not use the old configuration. The UE transmit CELL UPDATE message on uplink CCCH with IE
"Cell update cause" set to "radio link failure". The SS shall transmit CELL UPDATE CONFIRM message on downlink
CCCH after receiving CELL UPDATE message. The UE transmits PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message on the uplink DCCH using AM RLC and subsequently transmits the CELL CHANGE ORDER
FAILURE message to the SS in UTRAN cell, on the DCCH using AM RLC, setting the value of IE " Inter-RAT change
failure " to " physical channel failure".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1314
UE SS
6-10) in cell 1
enabled
UTRAN
3a SS SS removes the physical channel (DPCH), which was
allocated to the mobile before Cell Change Order From
UTRAN transmission
to the GSM/GPRS specified in the CELL CHANGE
ORDER FROM UTRAN
to establish temporary block flow. It implies that the UE
has switched to GPRS cell.
6 IMMEDIATE ASSIGNMENT
REJ ECT
SS rejects the channel request
7 VOID
8 CELL UPDATE The value "radio link failure" shall be set in IE "Cell
update cause".
9 CELL UPDATE CONFIRM This message include IE "Physical channel information
elements".
10 The SS configure the dedicated physical channel
according to the IE "Physical channel information
elements" included in the CELL UPDATE CONFIRM
message.
11 PHYSICAL CHANNEL
RECONFIGURATION
COMPLETE

UTRAN FAILURE
The IE "Inter-RAT failure cause" shall be set to "physical
channel failure"

Message Type
writes to this IE.
Activation time Now
- GSM
- BSIC BSIC1
- BCCH ARFCN 1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1315
U-RNTI

in TS 34.108, clause 9,with the following exceptions:
Frequency info
- UARFCN uplink (Nu) Reference to TS34.108 clause 5.1 Test frequencies
- UARFCN downlink (Nd) Reference to TS34.108 clause 5.1 Test frequencies
CHOICE Mode FDD
- Code number SF-1 (SF is reference to TS34.108 clause 6.10
Parameter Set)
- SSDT Cell Identity -a

Message Type
UTRAN message

In step 8 the SS shall receive CELL UPDATE message on the old channel of the UTRAN cell with the IE Cell update
cause set to cause radio link failure .
In step 11 the SS shall receive PHYSICAL CHANNEL COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1316
In step 12 the SS shall receive CELL CHANGE ORDER FROM UTRAN FAILURE message with the IE Inter-RAT
change failure cause set to physical channel failure.

8.3.11.5 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Failure
(T309 expiry)
If:
the UE shall:
1>if the UE receives the CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state:
2>revert to the cell it was camped on at the reception of the CELL CHANGE ORDER FROM UTRAN
message;
2>if the UE is unable to return to this cell:
3>select a suitable UTRA cell according to [4];
3>initiate the cell update procedure according to subclause 8.3.1 using the cause "cell re-selection";
4>proceed as below.
as specified below:
3>set it to the value of "RRC transaction identifier" in the entry for the CELL CHANGE ORDER FROM
UTRAN message in the table "Accepted transactions" in the variable TRANSACTIONS; and
3>clear that entry;
for transmission:
Reference(s)
TS 25.331 clause 8.3.11
To verify that when UE received CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state and if the
establishment of the connection to the other RAT failed due to expiry of timer T309 prior to the successful
establishment of a connection to the target RAT:
a. revert to the cell it was camped on at the reception of the CELL CHANGE ORDER FROM UTRAN message;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1317
b. transmit the CELL CHANGE ORDER FROM UTRAN FAILURE message and set the IE "Inter-RAT change
failure" to "physical channel failure.
Initial conditions
established.
SRBs,
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS_DCCH+DTCH_FACH (state 6-11). The SS starts GPRS cell,
through DCCH of the serving UTRAN cell. The UE starts the timer T309. After the UE receives the command it shall
configure itself accordingly but cannot complete the cell change, as SS does not respond to the Channel Request
message transmitted by UE till the timer T309 expires. The SS checks that the cell change has failed by checking that
the UE transmits the CELL CHANGE ORDER FROM UTRAN FAILURE message to the SS in UTRAN cell.

UE SS
1 UE The SS bring the UE into PS-DCCH+DTCH_FACH (State
6-11) in cell 1
enabled
UTRAN
ORDER FROM UTRAN
to establish temporary block flow
6 SS does not respond to the channel request.
UE transmits CHANNEL REQUEST message M+1 times.
The SS does not transmit a response and wait for T309
timer to expire.
UTRAN FAILURE
UTRAN cell.

Message Type
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1318
writes to this IE.
Activation time Now
- GSM
- BSIC BSIC1
- BCCH ARFCN 1

Message Type
UTRAN message

UTRAN cell.

8.3.11.6 Inter-RAT cell change order from UTRAN/To GPRS/CELL_FACH/Failure
(Physical channel Failure and Reversion Failure)
If:
the UE shall:
1>if the UE receives the CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state:
2>revert to the cell it was camped on at the reception of the CELL CHANGE ORDER FROM UTRAN
message;
2>if the UE is unable to return to this cell:
3>select a suitable UTRA cell according to [4];
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1319
3>initiate the cell update procedure according to subclause 8.3.1 using the cause "cell re-selection";
4>proceed as below.
as specified below:
3>set it to the value of "RRC transaction identifier" in the entry for the CELL CHANGE ORDER FROM
UTRAN message in the table "Accepted transactions" in the variable TRANSACTIONS; and
3>clear that entry;
for transmission:
Reference(s)
TS 25.331 clause 8.3.11
To verify that when UE received CELL CHANGE ORDER FROM UTRAN message in CELL_FACH state and if the
establishment of the connection to the other RAT failed due to other reasons e.g. (random) access failure, rejection due
to lack of resources:
a. revert to the cell it was camped on at the reception of the CELL CHANGE ORDER FROM UTRAN message;
b. if the UE is unable to return to this cell:
- select a suitable UTRA cell;
c. initiate the cell update procedure using the cause "cell re-selection";
d. when the cell update procedure is completed successfully, it transmits the CELL CHANGE ORDER FROM
UTRAN FAILURE message and set the IE "Inter-RAT change failure" to "physical channel failure".
Initial conditions
System Simulator: 3 cells - Cell 1, Cell 2 are UTRAN, Cell 3 is GPRS. 51.010 clauses 20.22 and 40.1.1 shall be
established.
SRBs,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1320
Test Procedure
Table 8.3.11.6
T0 T1 T0 T1

UTRA RF
Channel
Number
Ch. 1 Ch. 1
CPICH Ec
(FDD)
dBm/
3.84
MHz
-60 Off

-75 -60

Table 8.3.11.6 illustrates the downlink power to be applied for the 2 UTRAN cells at various time instants of the test
execution. SS switches the power settings between columns "T0" and "T1", whenever the description in multi-cell
condition specifies a reverse in the transmission power settings for cell 1 and cell 2.
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_FACH (state 6-11). The SS starts GPRS cell,
through DCCH of the serving UTRAN cell. The UE receives the command and configures itself accordingly but cannot
complete the cell change and wants to revert to the old configuration, but the UE cannot revert to the old configuration
because the SS shall not use the old configuration. The SS configures its downlink transmission power settings
according to columns "T1" in table 8.3.11.6. The UE transmits CELL UPDATE message on uplink CCCH with IE
"Cell update cause" set to "cell reselection". The SS shall transmit CELL UPDATE CONFIRM message on downlink
CCCH after receiving CELL UPDATE message. The UE transmits the CELL CHANGE ORDER FAILURE message
to the SS in UTRAN cell, on the DCCH using AM RLC, setting the value of IE " Inter-RAT change failure " to "
physical channel failure".

UE SS
1 UE The SS bring the UE into PS-DCCH+DTCH_FACH (State
6-11) in cell 1
enabled
UTRAN
The target cell description for GSM/GPRS.
3a SS The SS applies the downlink transmission power settings,
the values in columns "T1" of table 8.3.11.6.
ORDER FROM UTRAN
5 CHANNEL REQUEST The SS receives this burst on the traffic channel of cell 2
(GPRS cell) to establish temporary block flow It implies
that the UE has switched to GPRS cell.
6 IMMEDIATE ASSIGNMENT
REJ ECT
SS rejects the channel request
7 VOID
8 VOID
9 CELL UPDATE The value "cell reselection" shall be set in IE "Cell update
cause".
UTRAN FAILURE
The IE "Inter-RAT failure cause" shall be set to "physical
channel failure"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1321
Message Type
writes to this IE.
Activation time Now
- GSM
- BSIC BSIC1
- BCCH ARFCN 1


in TS 34.108, clause 9
Message Type
UTRAN message

In step 9 the SS shall receive CELL UPDATE message on the old channel of the UTRAN cell with the IE Cell update
cause set to cause cell reselection .
In step 11 the SS shall receive CELL CHANGE ORDER FROM UTRAN FAILURE message with the IE Inter-RAT
change failure cause set to physical channel failure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1322
8.3.11.7 Inter-RAT cell change order from UTRAN/To GPRS/ Failure (Unsupported
configuration)
If the UTRAN instructs the UE to perform a non-supported cell change order scenario or to use a non-supported
configuration, the UE shall:
1>transmit a CELL CHANGE ORDER FROM UTRAN FAILURE message, setting the information elements as
specified below:
2>clear that entry;
2>set the IE "Inter-RAT change failure" to "configuration unacceptable";
2>when the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layers
for transmission:
3>resume normal operation as if the CELL CHANGE ORDER FROM UTRAN message has not been
received;
Reference(s)
TS 25.331 clause 8.3.11
To verify if the UTRAN instructs the UE to perform a non-supported cell change order or to use a non-supported
configuration, the UE shall:
a. Transmit a CELL CHANGE ORDER FROM UTRAN FAILURE message, setting the IE "Inter-RAT change
failure" to "configuration unacceptable";
b. Resume normal operation
Initial conditions
System Simulator : 1 UTRAN cell
UE : PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of TS 34.108, one PS domain RAB is
established.
SRBs,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1323
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_DCH (state 6-10). The SS then sends a CELL
CHANGE ORDER FROM UTRAN message including a Configuration not Supported by the UE, to the UE through
DCCH of the serving UTRAN cell. The UE receives the command and finds that the configuration given in cell change
message is not supported. The SS checks that the cell change is failed by checking that the UE transmits the CELL
CHANGE ORDER FROM UTRAN FAILURE message to the SS in UTRAN cell with the IE Inter-RAT change
failure set to configuration unsupported.

UE SS
6-10) in cell 1
UTRAN
unsupported configuration. Cell change order to a Band
not supported by the UE
UTRAN FAILURE
UTRAN cell.

Message Type
writes to this IE.
Activation time Now
Target cell description Contains a Configuration not supported By the UE (Cell
change order to a Band not supported by the UE)

Message Type
UTRAN message
-Inter-RAT change failure cause configuration unsupported

UTRAN cell.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1324
8.3.11.8 Inter-RAT cell change order from UTRAN/To GPRS/ Failure (Invalid Inter-
RAT message)
If the CELL CHANGE ORDER FROM UTRAN message contains a protocol error causing the variable
PROTOCOL_ERROR_REJ ECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error
handling as follows. The UE shall:
1>set the IE "RRC transaction identifier" in the CELL CHANGE ORDER FROM UTRAN FAILURE message to
the value of "RRC transaction identifier" in the entry for the CELL CHANGE ORDER FROM UTRAN message
in the table "Rejected transactions" in the variable TRANSACTIONS; and
1>clear that entry;
1>set the IE "Inter-RAT change failure" to the cause value "protocol error";
1>transmit a CELL CHANGE ORDER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC;
1>when the CELL CHANGE ORDER FROM UTRAN FAILURE message has been submitted to lower layers for
transmission:
2>resume normal operation as if the invalid CELL CHANGE ORDER FROM UTRAN message has not been
received;
Reference(s)
TS 25.331 clause 8.3.11
To verify that the UE shall keep its old configuration and transmit a CELL CHANGE ORDER FROM UTRAN
FAILURE message, with the "Inter-RAT change failure" set to "protocol error", when it receives a CELL CHANGE
ORDER FROM UTRAN message, not including a valid message in accordance with the protocol specifications for the
target RAT.
Initial conditions
System Simulator: 1 UTRAN cell
established.
SRBs,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1325
Test Procedure
The SS starts the UTRAN cell and brings the UE into PS-DCCH+DTCH_DCH (state 6-10). The SS then sends a CELL
CHANGE ORDER FROM UTRAN message not including a valid cell change order from UTRAN message in
accordance with the protocol specifications for the target RAT, to the UE through DCCH of the serving UTRAN cell.
The UE receives the command and finds that the cell change order message is Invalid. The SS checks that the cell
change is failed by checking that the UE transmits the CELL CHANGE ORDER FROM UTRAN FAILURE message
to the SS in UTRAN cell with the IE Inter-RAT change failure cause set to protocol error.

UE SS
1 UE The SS bring the UE into PS-DCCH+DTCH_DCH (State
6-10) in cell 1
UTRAN
invalid CELL CHANGE ORDER FROM UTRAN.
UTRAN FAILURE
UTRAN cell

Message Type
writes to this IE.
Activation time Now
- CHOICE Radio Access Technology Spare2

Message Type
UTRAN message
-Inter-RAT change failure cause protocol error

UTRAN cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1326
8.4 Measurement procedure
8.4.1 Measurement Control and Report
8.4.1.1 Measurement Control and Report: Intra-frequency measurement for
transition from idle mode to CELL_DCH state (FDD)

Upon transition from idle mode to CELL_DCH state, the UE shall:
1>begin or continue monitoring the list of cells assigned in the IE "intra-frequency cell info list" in System
Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11);
1>if the "intra-frequency measurement reporting criteria" IE was included in System Information Block type 12 (or
System Information Block type 11, according to subclause 8.1.1.6.11):
2>begin measurement reporting according to the IE.
In CELL_DCH state, the UE shall:
1>transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in
variable MEASUREMENT_IDENTITY are met for any ongoing measurements that are being performed in the
UE.

The reporting criteria are fulfilled if either:
- the first measurement has been completed for a newly initiated measurement with periodic reporting; or
- the time period indicated in the stored IE "Periodical reporting criteria" has elapsed since the last measurement
report was submitted to lower layers for a given measurement; or
- an event in stored IE "Measurement reporting criteria" was triggered.
For the measurement, which triggered the MEASUREMENT REPORT message, the UE shall:
1>set the IE "measurement identity" to the measurement identity, which is associated with that measurement in
variable MEASUREMENT_IDENTITY;
1>set the IE "measured results" to include measurements according to the IE "reporting quantity" of that
measurement stored in variable MEASUREMENT_IDENTITY; and
2>if all the reporting quantities are set to "false":
3>not set the IE "measured results".
1>set the IE "Measured results" in the IE "Additional measured results" according to the IE "reporting quantity" for
all measurements associated with the measurement identities included in the "Additional measurements list"
stored in variable MEASUREMENT_IDENTITY of the measurement that triggered the measurement report;
and
2>if more than one additional measured results are to be included:
3>include only the available additional measured results, and sort them in ascending order according to their
IE "measurement identity" in the MEASUREMENT REPORT message.
1>if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report):

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1327
The UE shall:
1>transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RLC according
to the stored IE "measurement reporting mode" associated with the measurement identity that triggered the
report.
When the MEASUREMENT REPORT message has been submitted to lower layers for transmission:

Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in TS 25.331
subclause 8.6 unless otherwise specified below.
The UE shall:
1>read the IE "Measurement command";
1>if the IE "Measurement command" has the value "setup":
2>store this measurement in the variable MEASUREMENT_IDENTITY according to the IE "measurement
identity", first releasing any previously stored measurement with that identity if that exists;
2>for measurement types "inter-RAT measurement" or "inter-frequency measurement":

2>for measurement type "UE positioning measurement":

2>for any other measurement type:
3>if the measurement is valid in the current RRC state of the UE:
4>begin measurements according to the stored control information for this measurement identity.
1>if the IE "Measurement command" has the value "modify":
2>for all IEs present in the MEASUREMENT CONTROL message:
3>if a measurement was stored in the variable MEASUREMENT_IDENTITY associated to the identity by
the IE "measurement identity":
4>for measurement types "inter-frequency measurement" that require measurements on a frequency
other than the actually used frequency, or that require measurements on another RAT:

5>replace the corresponding information stored in variable MEASUREMENT_IDENTITY
associated to the identity indicated by the IE "measurement identity" with the one received in the
MEASUREMENT CONTROL message;
5>resume the measurements according to the new stored measurement control information.
3>otherwise:
4>set the variable CONFIGURATION_INCOMPLETE to TRUE.
2>for all optional IEs that are not present in the MEASUREMENT CONTROL message:
3>leave the currently stored information elements unchanged in the variable MEASUREMENT_IDENTITY
if not stated otherwise for that IE.
1>if the IE "measurement command" has the value "release":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1328

1>clear the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the
If the IE "Reporting Cell Status" is not received for intra-frequency, inter-frequency measurement, or inter-RAT
measurement, the UE shall:
1>for intra-frequency measurement, inter-frequency measurement and inter-RAT measurement:
2>exclude the IE "Measured Results" in MEASUREMENT REPORT.
Reference
3GPP TS 25.331 clause 8.4.1.8.1, 8.4.1.3, 8.4.2.2, 8.6.7.9.
1. To confirm that the UE continues to monitor intra-frequency measurement quantity of the cells listed in System
Information Block type 11 or 12 messages, after it has entered CELL_DCH state from idle mode. When the
intra-frequency measurement reporting criteria specified in System Information Block type 11 or 12 messages
have been met, it shall report the measurements using MEASUREMENT REPORT message(s).
2. To confirm that the UE terminates monitoring and reporting activities for the cells listed in "intra-frequency cell
info list" IE in System Information Block type 11 or 12 messages, after it has received a MEASUREMENT
CONTROL message that specifies the measurement type to be "intra-frequency measurement" with the same
measurement identity as in System Information Block Type 11 or 12 messages. To confirm that the UE
reconfigures the monitoring and reporting activities based on the last MEASUREMENT CONTROL message
received.
Initial Condition
System Simulator: 3 cells Cell 1, Cell 2 and Cell 3 are active.
Test Procedure
Table 8.4.1.1-1 illustrates the downlink power to be applied for the 3 cells at various time instants of the test execution.
Column marked "T0" denotes the initial conditions, while columns marked "T1" and "T2" are to be applied
subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.4.1.1-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch.1
CPICH Ec dBm/3.84
MHz
-60 -60 -60 -70 -60 -80 -80 -60 -60

The UE is initially in idle mode and has selected cell 1 for camping. The System Information Block type 11 messages
are modified with respect to the default settings. The key measurement parameters in the modified System Information
Block message are as follow: report criteria ="periodic reporting criteria", reporting interval ="64 seconds".
SS prompts the operator to make an outgoing call of a supported traffic class. SS and UE shall execute procedure P3
(for CS service) or P5 (for PS service). Next SS and UE shall execute procedure P7 (for CS service) or P9 (for PS
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1329
service). Then SS and UE shall execute procedure P11 (for CS service) or P13 (for PS service). The UE shall send a
MEASUREMENT REPORT message after reaching CELL_DCH state, reporting cell 2's CPICH RSCP value. After 64
seconds has passed since SS receives the first MEASUREMENT REPORT message, the UE shall transmit a second
MEASUREMENT REPORT message.
Note: In P11 or P13 in step 4, in RADIO BEARER SETUP message, IE "Default DPCH Offset Value" and IE
"DPCH frame offset" are set to "0".
SS sends a MEASUREMENT CONTROL message on the downlink DCCH. In this message, SS configures an intra-
frequency measurement based on the measurement quantity CPICH RSCP. Parameters used in this message are:
measurement identity ="1", report criteria ="event-trigger", event identity ="1e", reporting threshold ="-70 dBm". SS
checks to see that no MEASUREMENT REPORT messages are sent within the next 64 seconds (which is due to
periodic reporting). SS reconfigures the downlink transmission power settings according to values in column "T1" in
table 8.4.1.1-1. The UE shall transmit a MEASUREMENT REPORT message when it detects that the CPICH RSCP of
cell 3 has risen above the threshold value specified in the previous MEASUREMENT CONTROL message.
SS sends then a new MEASUREMENT CONTROL message to add cell 2 to the list of the cells the UE shall measure.
Since the RSCP for cell 2 is above the threshold for event 1e to be triggered, a MEASUREMENT REPORT triggered
by cell 2 shall be sent by the UE.
SS reconfigures the downlink transmission power settings according to values in column "T2" in table 8.4.1.1-1. SS
sends a new MEASUREMENT CONTROL message on the downlink DCCH. In this message, SS configures an intra-
frequency measurement based on the measurement quantity CPICH RSCP. Parameters used in this message are:
measurement identity ="1", report criteria ="event-trigger", event identity ="1a", Reporting range 8db. SS
reconfigures the downlink transmission power settings according to values in column "T1" in table 8.4.1.1-1. The UE
shall transmit a MEASUREMENT REPORT message when it detects that the condition for event 1a is fulfilled. SS
calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected Sequence
UE SS
camped onto cell 1. The
System Information Block type
11 messages to be transmitted
are different from the default
settings (see specific message
contents)
2 SS executes procedure P3 (clause 7.4.2.1.2)
or P5 (clause 7.4.2.2.2) specified in TS
34.108.

34.108.

7.4.2.5.2) or P13 (clause 7.4.2.6.2) specified
in TS 34.108.
IE "Default DPCH Offset
Value" and IE "DPCH frame
offset " in RADIO BEARER
SETUP message is set to "0".
5 SS SS shall wait for a
MEASUREMENT REPORT
message.
6 MEASUREMENT REPORT After receiving this message,
SS shall expect to receive the
next MEASUREMENT
REPORT message after 64
seconds.
6a MEASUREMENT REPORT SS shall receive consecutive
MEASUREMENT REPORT
messages at 64 seconds
interval.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1330
UE SS
7 MEASUREMENT CONTROL A measurement with
"measurement identity" IE set
to "1" is assigned, with the IE
"CHOICE reporting criteria"
set to "intra-frequency
measurement reporting
criteria". See specific message
content for the rest of the
message.
8 SS waits for 64 seconds and
verifies that no further
MEASUREMENT REPORT
messages are detected on the
uplink DCCH.
9 SS re-adjusts the downlink
table 8.4.1.1-1.
10 MEASUREMENT REPORT SS verifies that UE transmits a
MEASUREMENT REPORT
message triggered by cell 3
and containing report the
measured CPICH RSCP value
of cell 3.
10a MEASUREMENT CONTROL A MEASUREMENT
CONTROL is sent to the UE to
modify the list of the cells the
UE shall monitor.
10b MEASUREMENT REPORT SS verifies that UE transmits a
MEASUREMENT REPORT
message triggered by cell 2.
table 8.4.1.1-2.
message.
table 8.4.1.1-3 and waits 5
seconds.
MEASUREMENT REPORT
message to report occurrence
of event 1a.

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1331
Use the same System Information Block Type 11 message as found in clause 6.1.0b of TS 34.108, with the following
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1332
- Intra-frequency measurement identity Not Present
Absence of this IE is equivalent to default value 1
- CHOICE intra-frequency cell removal Not present
(This IE shall be ignored by the UE for SIB11)
- Cell info
- Cell individual offset Not present
Absence of this IE is equivalent to default value 0 dB
- CHOICE Mode FDD
- Primary Scrambling Code Refer to clause titled "Default settings for cell No.1
(FDD)" in clause 6.1.4 of TS 34.108
- Cell selection and Re-selection Not Present (The IE shall be absent as this is the
serving cell)
- Cell info
Absence of this IE is equivalent to default value 0dB
- Reference time difference to cell 1024
- CHOICE Mode FDD
indicator
FALSE
- CHOICE mode FDD
indicator
FALSE
- CHOICE mode FDD
Mode
Periodical reporting
- CHOICE report criteria Periodic reporting criteria

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1333
MEASUREMENT REPORT (Step 6 and 6a)
Measured Results
- CHOICE measurement Check to see if set to "Intra-frequency measured results
list"
- Intra-frequency measurement results
- Cell Identity Check to see if it is absent
- Cell synchronisation information Check to see if this IE is absent
- Primary Scrambling Code Check to see if it's the same code for cell 2
- CPICH Ec/No Check to see if this IE is absent
- CPICH RSCP "Checked to see if set to within an acceptable range"
- Pathloss Check to see if this IE is absent
Measured Results on RACH Check to see if this IE is absent
Event Results Check to see if this IE is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1334
- Intra-frequency measurement objects list
- New intra-frequency cells 2 new intra-frequency cells
- Cell info
- CHOICE mode FDD
- Cell info
- CHOICE mode FDD
- Intra-frequency measurement quantity
- Filter Coefficient Not Present (Default is 0)
- CHOICE Mode FDD
indicator
FALSE
- CHOICE mode FDD
- CPICH Ec/No reporting indicator TRUE
indicator
TRUE
- CHOICE mode FDD
- Reporting quantities for detected cells Not present
- Parameters required for each events
- Intra-frequency event identity 1e
- Triggering condition 1 Not present
- Reporting range constant Not Present
- W Not Present
- Hysteresis 1 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1335
used frequency
DPCH compressed mode status info Not Present

Note 1: Cell measured results for cells 1 and 3 may appear in either order (i.e. cell 1 then cell 3 or cell 3 then cell 1)
Measured Results
list"
- Cell synchronisation information Check to see if it is absent.
- CPICH Ec/No Check to see if this IE is present
- CPICH RSCP Check to see if this IE is present
- Cell synchronisation information Check to see if this IE is present and that the COUNT-
C-SFN frame difference is included in it.
Additional Measured Results Check to see if this IE is absent
Event Results
- CHOICE event result Check to see if this IE is set to "Intra-frequency
measurement event results"
- Intra-frequency event identity Check to see if this IE is set to "1e"
- Cell measured event results
- CHOICE mode Check to see if this IE is set to "FDD"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1336
Measurement Reporting Mode Not Present
- New intra-frequency info list 1 new intra-frequency cell
- Cell info
- CHOICE mode FDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1337
Measured Results
list"
- Intra-frequency measurement results Check to see if measurement results for 3 cells are
included (the order in which the different cells are
reported is not important)
- Cell measured results (for cell 1)
- Cell synchronisation information Check to see if it is absent.


Event Results
- Intra-frequency event identity Check to see if this IE is set to "1e"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1338
- Cell info
- CHOICE mode FDD
- Cell info
- CHOICE mode FDD
indicator
FALSE
indicator
FALSE
- Reporting range constant 8 dB
- W 0
- Hysteresis 0 dB
- Time to trigger 5000 msec
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1339
- Reporting interval 16 s

Measured Results Check to see if this IE is absent
Event Results
- CHOICE event result
- Intra-frequency event identity Check to see if this IE is set to "1a"

After step 5 the UE shall start to transmit 2 MEASUREMENT REPORT messages at 64 seconds interval. The
measurement quantity "CPICH RSCP" of cell 2 shall be reported in these messages.
After step 7 the UE shall not transmit any MEASUREMENT REPORT messages within 64 seconds after SS has
transmitted the MEASUREMENT CONTROL message in step 7.
After step 9 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, to report that the
CPICH RSCP value for cell 3 has risen above the threshold stated in the MEASUREMENT CONTROL message
transmitted by the SS in step 7. This MEASUREMENT REPORT message shall also contain IE "Event results",
indicating the triggering of event '1e' by cell 3. It shall also contain the measured CPICH RSCP value and cell
synchronisation information for cell 3, and the measured CPICH Ec/No and RSCP values for cell 1.
After step 10a, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH to report that the
CPICH RSCP value for cell 2 has risen above the threshold stated in the MEASUREMENT CONTROL message
transmitted by the SS in step 10a. The MEASUREMENT REPORT message shall contain the measured CPICH RSCP
value and cell synchronisation information for cell 2 and cell 3, as well as the measured CPICH Ec/No and RSCP for
cell 1. The IE "Event results" in this message shall indicate that cell 2 has triggered the event.
After step 13, the UE shall transmit a MEASUREMENT REPORT message containing IE "Event results", indicating
the triggering of event '1a' by cell 2. The MEASUREMENT REPORT message shall not contain any measured results.
8.4.1.1A Measurement Control and Report: Intra-frequency measurement for
transition from idle mode to CELL_DCH state (TDD)
8.4.1.1A.1 Definition

8.4.1.1A.2 Conformance requirement
The UE shall obey the following rules for different measurement types after transiting from idle mode to CELL_DCH
state:
1>if intra-frequency measurements applicable to CELL_DCH state are stored in the variable
MEASUREMENT_IDENTITY:
2>begin measurement reporting.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1340
Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in subclause 8.6 in
TS 25.331 unless otherwise specified below.
The UE shall:
2>if the measurement type is quality, UE internal, intra-frequency, inter-frequency or inter-RAT:
3>if, according to its measurement capabilities, the UE does not require compressed mode to perform the
measurements:

2>terminate the measurement associated with the identity given in the IE "measurement identity";
2>clear all stored measurement control information related associated to this measurement identity in variable
MEASUREMENT_IDENTITY.
1>if the UE "Additional Measurement List" is present:
2>if the received measurement configuration in this MEASUREMENT CONTROL message, or any
measurement identities in the "Additional Measurement List" do not all have the same validity:

The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRAN.

In CELL_DCH state, the UE shall:
1> transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in
variable MEASUREMENT_IDENTITY are met for any ongoing measurements that are being performed in the
UE.
The reporting criteria are fulfilled if either:
- the first measurement has been completed according to the requirements set in [19] or [20] for a newly initiated
measurement with periodic reporting; or
- the time period indicated in the stored IE "Periodical reporting criteria" has elapsed since the last measurement
report was submitted to lower layers for a given measurement; or
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1341
- an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for
different measurement types are described in detail in clause 14.

and
2>set the IE "Event results" according to the event that triggered the report.
The UE shall:
report.
Reference
TS 25.331, clauses 8.4.1.8.1, 8.4.2, 8.4.1.3.
8.4.1.1A.3 Test Purpose
1. To confirm that the UE continues to monitor intra-frequency measurement quantity of the cells listed in System
Information Block type 11 or 12 messages, after it has entered CELL_DCH state from idle mode. When the
intra-frequency measurement reporting criteria specified in System Information Block type 11 or 12 messages
have been met, it shall report the measurements using MEASUREMENT REPORT message(s).
2. To confirm that the UE terminates monitoring and reporting activities for the cells listed in "intra-frequency cell
info list" IE in System Information Block type 11 or 12 messages, after it has received a MEASUREMENT
CONTROL message that specifies the measurement type to be "intra-frequency measurement" with the same
measurement identity as in System Information Block Type 11 or 12 messages.
3. To confirm that the UE reconfigures the monitoring and reporting activities based on the last MEASUREMENT
CONTROL message received.
4. To confirm that the UE sends MEASUREMENT REPORT message if event 1G is configured and intra-
frequency measurement indicates change in best cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1342
8.4.1.1A.4 Method of test
Initial Condition
System Simulator: 3 cells Cell 1, Cell 2 and Cell 3 are active.
Test Procedure
Table 8.4.1.1A-1 illustrates the downlink power to be applied for the 3 cells at various time instants of the test
execution.
Column marked "T0" denotes the initial conditions, while column marked as "T1" will be applied during the test.
Table 8.4.1.1A-1
T0 T1 T0 T1 T0 T1
UTRA RF Channel
Number
Ch. 1 Ch. 1 Ch.1
PCCPCH_RSCP dBm -69 -69 -74 -64 -79 -67

The UE is initially in idle mode and has selected cell 1 for camping. The System Information Block type 11 messages
are modified with respect to the default settings to prevent reporting of "Cell synchronisation information" and also to
include cell 2 into the monitored neighbour cell list. The key measurement parameters in the modified System
Information Block message are as follow: measurement type ="intra-frequency measurement", measurement quantity =
"PCCPCH RSCP", report criteria ="periodic reporting criteria", reporting interval ="64 seconds".
service). Then SS and UE shall execute procedure P11 (for CS service) or P13 (for PS service).
The UE shall send a MEASUREMENT REPORT message after reaching CELL_DCH state, reporting cell 2's PCCPCH
RSCP value. After 64 seconds has passed since SS receives the first MEASUREMENT REPORT message, the UE shall
transmit a second MEASUREMENT REPORT message.
SS sends a MEASUREMENT CONTROL message on the downlink DCCH. In this message, SS configures an intra-
frequency measurement based on the measurement quantity PCCPCH RSCP. Parameters used in this message are:
measurement identity ="1", report criteria ="event-trigger", event identity ="1g". All intra-frequency cells are
removed. Cell 3 is included as new intra-frequency cell. SS checks to see that no MEASUREMENT REPORT
messages are sent within the next 64 seconds (which is due to periodic reporting). SS reconfigures the downlink
transmission power settings according to values in column "T1" in table 8.4.1.1A-1. The UE shall transmit a
MEASUREMENT REPORT message when it detects that the PCCPCH RSCP of cell 3 is present. SS sends another
MEASUREMENT CONTROL message on the downlink DCCH to include cell 2 in the monitored cells. SS configures
an intra-frequency measurement based on the measurement quantity PCCPCH RSCP. Parameters used in this message
are: measurement identity ="1", report criteria ="event-trigger", event identity ="1g". The UE shall transmit a
MEASUREMENT REPORT message when it detects that the PCCPCH RSCP of cell 2 and indicating cell 2 as a best
cell. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1343
Expected Sequence
UE SS
contents). Cell 2 is included in
CELL_INFO LIST.
34.108.
UE reaches PS-CELL_DCH or
CS-CELL_DCH
34.108.
UE reaches PS-DCCH_DCH
or CS-DCCH_DCH
in TS 34.108.
UE reaches PS-
DCCH+DTCH_DCH or CS-
DCCH+DTCH_DCH
5 SS SS shall wait for a
MEASUREMENT REPORT
message
6 MEASUREMENT REPORT After receiving this message,
SS shall expect to receive the
next MEASUREMENT
REPORT message after 64
seconds
7 MEASUREMENT REPORT SS shall receive consecutive
MEASUREMENT REPORT
messages at 64 seconds
interval.
message.
9 SS waits for 64 seconds and
verifies that no further
MEASUREMENT REPORT
uplink DCCH.
table 8.4.1.1A-1.
MEASUREMENT REPORT
message triggered by cell 3
containing report the
measured PCCPCH RSCP
value of cell 3.
12 MEASUREMENT CONTROL A MEASUREMENT
CONTROL is sent to the UE to
modify the list of the cells the
UE shall monitor.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1344
UE SS
MEASUREMENT REPORT
message triggered by cell 2,
containing report the
value of cell 2. The UE shall
report event 1G for change to
best cell, cell2.

All messages indicated below shall use the same content as described in default message content, with the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1345
- Cell info
- CHOICE Mode TDD
- Primary CCPCH Info Refer to clause titled "Default settings for cell No.1
(TDD)" in clause 6.1.4 of TS 34.108
serving cell)
- Cell info
- CHOICE Mode TDD
- CHOICE Mode TDD
- Measurement quantity list
- Intra-frequency measurement for RACH reporting Not Present
- Maximum number of reported cells on RACH Not Present
indicator
FALSE
- CHOICE mode TDD
- Proposed TGSN Reporting required FALSE
indicator
FALSE
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1346
Mode
- Inter-frequency measurement system information Not present
- Inter-RAT measurement system information Not Present

MEASUREMENT REPORT (Step 6 and 7)
Measured Results
- CHOICE measurement Check to see if set to "Intra-frequency measured
results list"
- Primary CCPCH Info Check to see if it's the same for cell 2
- PCCPCH RSCP "Checked to see if set to within an acceptable range"
- Cell measured results Check to see if it is absent
- Cell Identity Check to see if this IE is absent
- Cell synchronisation information Check to see if it's the same for cell 1
- Primary CCPCH Info "Checked to see if set to within an acceptable range"
- PCCPCH RSCP Check to see if this IE is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1347
- Periodic Reporting / Event Trigger Reporting
Mode
Event Trigger
- Cell info
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Primary CCPCH Info Set to same code as for cell 1
- CHOICE Mode TDD
indicator
FALSE
indicator
TRUE
- Reporting range Not Present
- W Not Present
- Hysteresis 1 dB
- Amount of reporting Not present
- Reporting cell status Present
frequency or within active and/or monitored set on
non-used frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1348

Measured Results
results list"
- PCCPCH RSCP Check to see if this IE is present
Event Results
- Intra-frequency event identity Check to see if this IE is set to "1g"
- CHOICE mode Check to see if this IE is set to "TDD"
- Cell parameters Id Check to see if it's the same for cell 3

- Cell info
- CHOICE mode TDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1349
Measured Results
results list"
- Cell measured results (for cell2)
- Primary CPICH Info Check to see if it's the same for cell 2
- Cell measured results (for cell1)
- Cell synchronisation information Absent

Event Results
- Intra-frequency event identity Check to see if this IE is set to "1g"
- CHOICE mode Check to see if this IE is set to "TDD"
- Primary CCPCH Info Check to see if it's the same code for cell 2

8.4.1.1A.5 Test Requirement
After step 5 the UE shall start to transmit 2 MEASUREMENT REPORT messages at 64 seconds interval. The
measurement quantity "PCCPCH RSCP" of cell 2 shall be reported in these messages.
After step 8 the UE shall not transmit any MEASUREMENT REPORT messages within 64 seconds after SS has
transmitted the MEASUREMENT CONTROL message in step 8.
After step 10 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, to report the
PCCPCH RSCP value for cell 3. This MEASUREMENT REPORT message shall also contain IE "Event results",
indicating the triggering of event '1g' by cell 3. It shall also contain the measured PCCPCH RSCP value and cell
synchronisation information for cell 3, and the measured PCCPCH RSCP values for cell 1.
After step 12 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, to report the
PCCPCH RSCP value for cell 2. This MEASUREMENT REPORT message shall also contain IE "Event results",
indicating the triggering of event '1g' by cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1350
8.4.1.2 Measurement Control and Report: Inter-frequency measurement for
transition from idle mode to CELL_DCH state (FDD)

1>stop monitoring the list of cells assigned in the IE "inter-frequency cell info list" in System Information Block
type 12 (or System Information Block type 11).
Upon reception of a MEASUREMENT CONTROL message the UE shall:
2>for measurement types "inter-RAT measurement" or "inter-frequency measurement" that require
measurements on a frequency other than the actually used frequency:
3>if, according to its measurement capabilities, the UE requires compressed mode to perform that
measurement type and after reception of this message a compressed mode pattern sequence with an
appropriate measurement purpose is active according to the IE "Current TGPS Status Flag" in UE
variable TGPS_IDENTITY; or
measurements on at least one supported band of that measurement type:
If the IE "Reporting Cell Status" is not received for intra-frequency, inter-frequency measurement, or inter-RAT
measurement, the UE shall:
1>for intra-frequency measurement, inter-frequency measurement and inter-RAT measurement:
2>exclude the IE "Measured Results" in MEASUREMENT REPORT.
Reference
3GPP TS 25.331 clauses 8.4.1.3, 8.4.1.8.2, 8.6.6.15 and 8.6.7.9
1. To confirm that the UE stops monitoring the list of cells assigned in the IE "inter-frequency cell info" in System
Information Block type 11 messages, after it enters CELL_DCH state from idle mode.
2. To confirm that the UE, which requires compressed mode, starts to perform inter-frequency measurement and
related reporting activities, when it receives a MEASUREMENT CONTROL message with the "DPCH
compressed mode status info" IE indicating that a stored compressed mode pattern sequence be simultaneously
activated.
3. To confirm that the UE, which does not require compressed mode, starts to perform inter-frequency
measurement and related reporting activities when it receives a MEASUREMENT CONTROL message without
IE "DPCH compressed mode status info".
4. To confirm that the UE excludes the IE "Measured Results" for any cells in the MEASUREMENT REPORT
messages, after it receives a MEASUREMENT CONTROL message with "Reporting cell status" IE omitted.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1351
Initial Condition
System Simulator: 2 cells Cell 1 and cell 4 are active.
initial UE state shall be "Registered idle mode on CS/PS" (state 7).
Test Procedure
Table 8.4.1.2-1 illustrates the downlink power to be applied for the 2 cells.
Table 8.4.1.2-1
UTRA RF
Channel Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-60 -75

The UE is initially in idle mode and has selected cell 1 for camping.
SS prompts the operator to make an outgoing call for one of the traffic classes supported by the UE. SS and UE shall
execute procedure P3 (for CS service) or P5 (for PS service). The RRC CONNECTION SETUP message used in
procedure P3 or P5 should contain IE "DPCH compressed mode info", setting the "TGPS status flag" to "Deactivate"
and configuring transmission pattern gap sequence with TGPSI=1 only if UE requires compressed mode. Next SS and
UE shall execute procedure P7 (for CS service) or P9 (for PS service). Then SS and UE shall execute procedure P11
(for CS service) or P13 (for PS service). An optional PHYSICAL CHANNEL RECONFIGURATION message is
transmitted by SS to activate the transmission pattern gap sequence with TGPSI=1, if the UE requires compressed mode
to perform inter-frequency measurement. Correspondingly, the UE shall start the compressed mode operations at
designated time and respond with PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the UL
DCCH. The UE shall not transmit any MEASUREMENT REPORT messages, which pertain to measurement readings
for cells listed in the IE "inter-frequency cell info list" in System Information Block Type 11.
If UE requires compressed mode, SS sends PHYSICAL CHANNEL RECONFIGURATION message on the downlink
DCCH, specifying that compressed mode sequence pattern with TGPSI=1 be deactivated. The UE shall reply with
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH if UE configures
according to the PHYSICAL CHANNEL RECONFIGURATION message.
SS sends MEASUREMENT CONTROL message on the downlink DCCH. In this message, SS requests UE to perform
inter-frequency measurement with periodic reporting of CPICH RSCP values for cell 4. If UE requires compressed
mode, IE "DPCH compressed status info" IE to activate the transmission gap pattern sequence with TGPSI =1 is
included in this message.
The UE shall start inter-frequency measurement and reporting for cell 4's CPICH RSCP values. It shall report this
measurement result by transmitting MEASUREMENT REPORT messages on uplink DCCH periodically at 16 seconds
interval.
SS sends MEASUREMENT CONTROL message on the downlink DCCH omitting the IE "Reporting cell status". The
UE shall send MEASUREMENT REPORT messages on the uplink DCCH, with the IE "Cell measured results"
excluded in these messages. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1352
Expected Sequence
UE SS
1 System Information Block type 11 The UE is idle mode and
camped onto cell 1.System
Information Block Type 11 to
be transmitted is different from
the default settings (see
specific message contents)
34.108.
SS prompts the operator to
make an outgoing call.
34.108.

in TS 34.108.

5 Void (if compressed mode is not required by
the UE), or PHYSICAL CHANNEL
RECONFIGURATION (if compressed mode
is required by the UE)
If compressed mode is not
required (refer ICS/IXIT), then
goto step 6. Else, activate the
compressed mode operation.
5a Void (if compressed mode is not required by
RECONFIGURATION COMPLETE (if
compressed mode is required by the UE)
UE shall remain in CELL_DCH
state.
6 SS checks to see that no
MEASUREMENT REPORT
messages are received for
10 s.
If compressed mode is not
required (refer ICS/IXIT), then
goto step 9.
RECONFIGURATION (if compressed mode
is required by the UE)
Existing compressed mode
sequence pattern is de-
activated in this message.
RECONFIGURATION COMPLETE (if
compressed mode is required by the UE)
state.
9 MEASUREMENT CONTROL SS requests UE to start inter-
frequency measurement for
cell 4, and performing periodic
reporting for cell 4's CPICH
RSCP. See specific message
content below.
10 MEASUREMENT REPORT UE shall report cell 4's CPICH
RSCP reading periodically.
11 MEASUREMENT CONTROL SS changes the reporting
criteria of cell 4 to 'event 2c'.
"Reporting cell status" IE in
this message is omitted.
12 MEASUREMENT REPORT SS monitors the uplink DCCH
to make sure that only 1 such
message is received almost
immediately after step 11. This
message shall not contain IE
"Inter-frequency cell measured
results"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1353

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1354
-Use of HCS Not used
-Cell selection and reselection quality measure CPICH Ec/No
- Intra-frequency measurement identity Not present
- CHOICE intra-frequency cell removal Not Present
- Cell info
- CHOICE mode FDD
- Cell Selection and Re-selection info Not present
- Intra-frequency measurement quantity Not present
reporting
Not present
- Maximum number of reported cells on RACH Not present
- CHOICE inter-frequency cell removal Not present
- Frequency info
- CHOICE mode FDD
- UARFCN downlink (Nd) Reference to table 6.1.2 of TS34.108 for Cell 4
- Cell info
- CHOICE mode FDD
-Cells for measurement Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1355
If UE do not require compressed mode, use the message found in TS 34.108 clause 9.
If UE requires compressed mode, use the message found in TS 34.108 clause 9, with the following exceptions:
- Timing Indication Initialise
- DPC mode Single TPC
- CHOICE Mode FDD
- TFCI existence FALSE
- Number of bits for Pilot bits (SF=128, 256) Refer to the parameter set in TS 34.108
- DPCH compressed mode info This IE is present only if the ICS/IXIT statement
indicates that compressed mode is required.
- TGPSI 1
- TGCFN Not Present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD Undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL Mode UL and DL, UL only or DL only depending the on UE
capability
- Downlink compressed mode method SF/2 (or Not present depending on the UE capability)
- Uplink compressed mode method SF/2 or Not present depending on the UE capability
- DeltaSIR1 2.0
- TX Diversity Mode None
- CHOICE mode FDD
- Primary scrambling code Reference to 34.108
- Primary CPICH usage for channel estimation Primary CPICH can be used
- DPCH frame offset Set to value: Default DPCH Offset value mod 38400
- DL Channelisation code
- Spreading factor Reference to 34.108
- Code number 0
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1356
- SSDT Cell identity Not present
SCCPCH information for FACH Not present

Use the same message sub-type in clause 9 of TS 34.108 titled "Non speech in CS" or "Speech in CS" or "Packet to
CELL_DCH from CELL_DCH in PS", with the following exceptions:
- CHOICE mode FDD
- Spreading factor Reference to TS34.108 clause 6.10 Parameter
Set
- Fixed or Flexible Position Reference to TS34.108 clause 6.10 Parameter
Set
- TFCI existence Reference to TS34.108 clause 6.10 Parameter
Set
- Number of bits for Pilot bits (SF=128,256) Reference to TS34.108 clause 6.10 Parameter
Set
- DPCH compressed mode info This IE is present only if the ICS/IXIT
statement indicates that compressed mode is
required.
- TGPSI 1
Not Present
Downlink information per radio link list Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1357
Use the same message sub-type in clause 9 of TS 34.108 titled "Non speech in CS" or "Speech in CS" or "Packet to
CELL_DCH from CELL_DCH in PS", with the following exceptions:
- CHOICE mode FDD

- Spreading factor Reference to TS34.108 clause 6.10 Parameter
Set
- Fixed or Flexible Position Reference to TS34.108 clause 6.10 Parameter
Set
- TFCI existence Reference to TS34.108 clause 6.10 Parameter
Set
- Number of bits for Pilot bits (SF=128,256) Reference to TS34.108 clause 6.10 Parameter
Set
- TGPSI 1
- TPGS status Flag Deactivate
- TGCFN
Not Present
Not Present
Downlink information per radio link list Not Present

If UE requires compressed mode,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1358
Mode
- New inter-frequency info list
- Frequency info
- Cell info
- CHOICE mode FDD
- Filter Coefficient Not Present
estimate
CPICH RSCP
indicator
FALSE
- Cell Identity reporting indicator FALSE
- CHOICE reported cell Report cell within active and/or monitored set on used
used frequency
- Inter-frequency set update Not present
- TGPSI 1

If UE do not require compressed mode,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1359
- Frequency info
- Cell info
- CHOICE mode FDD
- Cells for measurement
estimate
CPICH RSCP
indicator
FALSE
used frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1360
Measured Results
- CHOICE measurement Check to see if set to "Inter-frequency measured results
list"
- Inter-frequency measurement results
- Frequency info
- UARFCN (uplink) Check to see if set to the UARFCN of the uplink
- UARFCN (downlink) Check to see if set to the UARFCN of the downlink
- UTRA carrier RSSI Check to see if it is absent
- Inter-frequency cell measurement results
- Cell synchronisation information Check to see if it is absent
- Primary Scrambling Code Check to see if set to the same code for cell 4
- CPICH Ec/No Check to see if it is absent
- Pathloss Check to see if it is absent
Measured Results on RACH Check to see if it is absent
Additional Measured results Check to see if it is absent
Event Results Check to see if it is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1361
Measurement Command Set up
- Frequency info
- Cell info
- CHOICE mode FDD
estimate
CPICH RSCP
indicator
FALSE
-UE Autonomous update mode On with no reporting
-Non autonomous update mode Not Present
- W used frequency Not Present
- Hysteresis 0.5 dB
- Time to trigger 0 milliseconds
frequency

- W non used frequency 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1362
Measured Results Check to see if it is absent
Additional Measured Results Check to see if it is absent
Event Results
- Inter-frequency event identity Check to see if this IE is set to "2c"
- Frequency info
- Non frequency related measurement event
results

- CHOICE Mode Check to see if set to "FDD"
- Primary Scrambling Code Check to see if set to the same code as cell 4

After step 5 the UE shall not transmit any MEASUREMENT REPORT messages pertaining to the measurement of
CPICH RSCP of cell 4.
If UE requires compressed mode operation, after step 5, UE shall activate compressed mode operations at the time
indicated by IE "TGCFN" and then transmit PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on
If UE requires compressed mode, after step 7, UE shall transmit PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message on uplink DCCH using AM RLC.
After step 9 the UE shall transmit MEASUREMENT REPORT messages on uplink DCCH, reporting cell 4's CPICH
RSCP value at periodic time interval of 16 seconds in "inter-frequency cell measurement results" IE.
After step 11 the UE shall transmit only 1 MEASUREMENT REPORT message on the uplink DCCH. In this message,
IE "Measured Results" shall be absent.
8.4.1.2A Measurement Control and Report: Inter-frequency measurement for
transition from idle mode to CELL_DCH state (TDD)

type 12 (or System Information Block type 11).
Upon reception of a MEASUREMENT CONTROL message the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1363
2>for measurement types "inter-frequency measurement":
3>if the IE "Inter-frequency cell info list" for that measurement identity is empty; or
measurements:
If the IE "Reporting Cell Status" is not received for inter-frequency measurement, the UE shall:
1>exclude the IE "Cell Measured Results" for any cell in MEASUREMENT REPORT.
Reference
3GPP TS 25.331 clauses 8.4.1.3, 8.4.1.8.2 and 8.6.7.9
Information Block type 11 messages, after it enters CELL_DCH state from idle mode.
2. To confirm that the UE excludes the IE "cell measured results" for any cells in the MEASUREMENT REPORT
messages, after it receives a MEASUREMENT CONTROL message with "Reporting cell status" IE omitted.
Initial Condition
System Simulator: 2 cells Cell 1 and cell 4 are active..
Test Procedure
Table 8.4.1.2A-1 illustrates the downlink power to be applied for the 2 cells.
Table 8.4.1.2A-1
UTRA RF
Channel Number
Ch. 1 Ch. 2
PCCPCH RSCP dBm
-60 -75

The UE is initially in idle mode and has selected cell 1 for camping.
execute procedure P3 (for CS service) or P5 (for PS service). Next SS and UE shall execute procedure P7 (for CS
service) or P9 (for PS service). Then SS and UE shall execute procedure P11 (for CS service) or P13 (for PS
service).The UE shall not transmit any MEASUREMENT REPORT messages, which pertain to measurement readings
for cells listed in the IE "inter-frequency cell info list" in System Information Block Type 11.
SS sends MEASUREMENT CONTROL message on the downlink DCCH. In this message, SS requests UE to perform
inter-frequency measurement with periodic reporting of PCCPCH RSCP values for cell 4.
The UE shall start inter-frequency measurement and reporting for cell 4's PCCPCH RSCP values. It shall report this
measurement result by transmitting MEASUREMENT REPORT messages on uplink DCCH periodically at 16 seconds
interval.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1364
SS sends MEASUREMENT CONTROL message on the downlink DCCH omitting the IE "Reporting cell status". The
UE shall send MEASUREMENT REPORT messages on the uplink DCCH, with the IE "Cell measured results"
excluded in these messages. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected Sequence
UE SS
camped onto cell 1.System
Information Block Type 11 to
34.108.
SS prompts the operator to
make an outgoing call.
34.108.

in TS 34.108.

5 Void
MEASUREMENT REPORT
messages are received.

7 MEASUREMENT CONTROL SS requests UE to start inter-
frequency measurement for
cell 4, and performing periodic
reporting for cell 4's PCCPCH
RSCP. See specific message
content below.
8 MEASUREMENT REPORT UE shall report cell 4's
PCCPCH RSCP reading
periodically.
9 MEASUREMENT CONTROL SS changes the reporting
criteria of cell 4 to 'event 2c'.
"Reporting cell status" IE in
this message is omitted.
12 MEASUREMENT REPORT SS monitors the uplink DCCH
to make sure that only 1 such
message is received almost
immediately after step 11. This
message shall not contain IE
"Inter-frequency cell measured
results"

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1365
- Cell info
- CHOICE mode TDD
reporting
Not present
- CHOICE inter-frequency cell removal Not present
- Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to table 6.1.4 of TS34.108 for Cell 4
- Cell info
- CHOICE mode TDD
- PCCPCH Refer to clause titled "Default settings for cell No.4
-Cells for measurement Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1366
UE will use the message found in TS 34.108 clause 9.
- Frequency info
- UARFCN (Nt) UARFCN of the frequency for cell 4
- Cell info
- CHOICE mode TDD
estimate
PCCPCH RSCP
indicator
FALSE
- CHOICE mode TDD
- Primary CCPCH RSCP reporting indicator TRUE
used frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1367
Measured Results
list"
- Frequency info
- UARFCN Check to see if set to the UARFCN of the frequency for
cell 4
- Primary CCPCH Info Check to see if set to the same for cell 4
- Timeslot ISCP reporting indicator Check to see if it is absent
- Proposed TGSN Reporting required Check to see if it is absent
- Primary CCPCH RSCP reporting indicator Check to see if it is present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1368
- Frequency info
- UARFCN uplink (Nt) UARFCN of the frequency for cell 4
- Cell info
- CHOICE mode TDD
estimate
PCCPCH RSCP
indicator
FALSE
-UE Autonomous update mode On with no reporting
-Non autonomous update mode Not Present
- Hysteresis 0.5 dB
- Time to trigger 0 milliseconds
frequency

- W non used frequency 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1369
Measured Results
list"
- Frequency info
cell 4
- Inter-frequency cell measurement results Check to see if it is absent
Additional Measured Results Check to see if it is absent
Event Results
- Inter-frequency event identity Check to see if this IE is set to "2c"
- Frequency info
cell 4
results

- CHOICE Mode Check to see if set to "TDD"
- Primary CCPCH info Check to see if set to the same as cell 4

After step 5 the UE shall not transmit any MEASUREMENT REPORT messages pertaining to the measurement of
PCCPCH RSCP of cell 4.
After step 7 the UE shall transmit MEASUREMENT REPORT messages on uplink DCCH, reporting cell 4's CPICH
RSCP value at periodic time interval of 16 seconds in "inter-frequency cell measurement results" IE.
After step 9 the UE shall transmit only 1 MEASUREMENT REPORT message on the uplink DCCH. In this message,
IE "inter-frequency cell measured results" shall be absent.

transition from idle mode to CELL_FACH state (FDD)

Upon transition from idle mode to CELL_FACH state, the UE shall:
1>begin or continue monitoring cells listed in the IE "intra-frequency cell info list" received in System Information
Block type 12 (or System Information Block type 11).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1370
Upon transition from CELL_FACH to CELL_DCH state, the UE shall:
1>retrieve each set of measurement control information of measurement type "intra-frequency" stored in the
1>if the IE "measurement validity" for a measurement has been assigned the value "CELL_DCH:
2>resume the measurement reporting.
1>if no intra-frequency measurements applicable to CELL_DCH state are stored in the variable
2>continue monitoring the list of neighbouring cells assigned in the IE "intra-frequency cell info list" in System
Information Block type 12 (or System Information Block type 11);
2>if the IE "intra-frequency measurement reporting criteria" was included in System Information Block type 12
(or System Information Block type 11):
3>send the MEASUREMENT REPORT message when reporting criteria in IE "Reporting information for
state CELL_DCH" are fulfilled.
Reference
3GPP TS 25.331, clause 8.4.1.9.1, 8.4.1.7.1, 8.4.2.2.
1. To confirm that the UE begins or continues to monitor cells listed in IE "intra-frequency cell info list" of
System Information Block type 11 or 12 messages after it has entered CELL_FACH state from idle mode.
2. To confirm that the UE applies the reporting criteria stated in "intra-frequency measurement reporting criteria"
IE in System Information Block Type 11 or 12 in a subsequent transition to CELL_DCH state.
3. To confirm that the UE reports measured results on RACH messages, if it receives IE "Intra-frequency
reporting quantity for RACH reporting" and IE "Maximum number of reported cells on RACH" from System
Information Block Type 11 or 12 upon a transition from idle mode to CELL_FACH state.
Initial Condition
System Simulator: 2 cells. Cell 1 and cell 2 are active.
Test Procedure
Table 8.4.1.3-1 illustrates the downlink power to be applied for the 2 cells in this test case.
Table 8.4.1.3-1
UTRA RF
Channel Number
Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -67

The UE is initially in idle mode and camps on cell 1. The System Information Block type 11 are modified compared to
the default settings. In the System Information Block type 11 messages, reporting of CPICH RSCP is also required for
intra-frequency reporting when transmitting RACH messages on cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1371
execute procedure P6. Next SS and UE shall execute procedure P10. Then SS and UE shall execute procedure P14. SS
starts timer T305 and waits until timer T305 expires, the UE shall send a CELL UPDATE message on the CCCH which
includes the measured value of cell 1's CPICH RSCP in IE "Measured results on RACH". SS then replies with CELL
UPDATE CONFIRM message on the downlink DCCH, without changing the physical channel resources.
SS transmits PHYSICAL CHANNEL RECONFIGURATION message, and allocates dedicated physical channels to the
UE. The UE shall transit to CELL_DCH state and then send a MEASUREMENT REPORT message, correctly stating
the measurement identity. The measurement identity indicated shall match the value that was previously broadcast on
System Information Block type 11 messages when the UE was still in idle mode. The IE "Measured results" in the
MEASUREMENT REPORT messages shall contain measured values of cell 2's CPICH RSCP.
Expected Sequence
UE SS
1 System Information Block type 1,
The UE is in idle mode and
camps onto cell 1. System
Information Block type 1 and
11 to be transmitted are
different from the default
contents)
SS prompts the test operator
7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

5 Void
6 SS monitors the uplink DCCH
to confirm that no
MEASUREMENT REPORT
messages are detected. SS
waits for 5 minutes (for the
expiry of T305 timer).
7 CELL UPDATE This message shall contain IE
"Measured results on RACH"
reporting the measured
CPICH RSCP for cell 1.
8 CELL UPDATE CONFIRM SS does not change the
physical channel
configurations.
9 PHYSICAL CHANNEL
RECONFIGURATION
SS assigns dedicated physical
resources.
10 PHYSICAL CHANNEL
UE shall transit to CELL_DCH
state.
11 MEASUREMENT REPORT UE shall begin to report cell
2's CPICH RSCP value
periodically at 16 seconds
interval. The measurement
identity shall match the one
that is broadcast for use in
CELL_DCH in SIB11 in step 1.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1372
exceptions:
- T305

5 minutes.

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1373
- Cell info
- CHOICE mode FDD
- Cell info
- CHOICE mode FDD
- Cell selection and Re-selection info
- Qoffset1s,n Not Present (Default is 0 dB)
- Qoffset2s,n Not Present
- HCS neighbouring cell information Not Present
- CHOICE Mode FDD
- Qqualmin -20dB
- Qrxlevmin -115dBm
reporting

indicator
No report
- CHOICE mode FDD
indicator
FALSE
- CHOICE mode FDD
- CPICH Ec/No reporting indicator TRUE
indicator
TRUE
- CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1374
- W 0.0
- Hysteresis 1.0 dB
used frequency

U-RNTI Check to see if set to same U-RNTI value assigned in
the execution of procedure P6.
START list Checked to see if this IE is present
AM_RLC error indication(RB2, RB3 or RB4) FALSE
AM_RLC error indication(RB>4) FALSE
Cell update cause Check to see if set to 'Periodical cell update'
Failure cause Check to see if this IE is absent

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "Packet to CELL_DCH from
CELL_FACH".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1375
Measured Results
list"

- CPICH RSCP Check to see if this IE is absent
- Cell synchronisation information Check to see if this IE is present and includes IE
COUNT-C-SFN frame difference
- Primary CPICH Info Check to see if it's the same code for cell 2
- Primary Scrambling Code Check to see if this IE is absent
Event Results
- CHOICE event result Check to see if set to "Intra-frequency measurement
event results"
- Intra-frequency event identity Check to see if set to "1a"
- CHOICE Mode Check to see if set to "FDD"
- Primary Scrambling Code Check to see if set to the scrambling code of cell 2

After step 5 the UE shall not transmit any MEASUREMENT REPORT messages on the uplink DCCH.
After step 6 the UE shall initiate cell update procedure by transmitting CELL UPDATE message on CCCH. In this
message, IE "cell update cause" shall be set to "periodic cell update". It shall include IE "measured results on RACH",
containing the measurement value for cell 1's CPICH RSCP.
After step 10 the UE shall transmit MEASUREMENT REPORT messages at 16 seconds interval. In these messages,
cell 2's CPICH RSCP value shall be reported in IE "Measured results". The IE "measurement identity" in this message
shall match the IE "Intra-frequency measurement identity" found in System Information Block type 11 messages
transmitted in step 1. The MEASUREMENT REPORT messsages shall also contain IE "Event results", indicating that
intra-frequency event "1a" has triggered in the UE.
transition from idle mode to CELL_FACH state (TDD)

The UE shall obey the follow rules for different measurement types after transiting from idle mode to CELL_FACH
state:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1376
1>begin or continue monitoring cells listed in the IE "intra-frequency cell info list" received in System Information
Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11, TS 25.331).
The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRAN.
variable MEASUREMENT_IDENTITY are met for any ongoing traffic volume measurement or UE positioning
measurement that is being performed in the UE;
In TDD, if the Radio Bearer associated with the MEASUREMENT_IDENTITY fulfilling the reporting criteria for an
ongoing traffic volume measurement is mapped on transport channel of type USCH, the UE shall:
1>initiate the "PUSCH CAPACITY REQUEST" procedure instead of transmitting a MEASUREMENT REPORT
(TDD Only).

and
2>set the IE "Event results" according to the event that triggered the report.
The UE shall:
report.

Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in subclause 8.6 in
TS 25.331 unless otherwise specified below.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1377
The UE shall:
measurements:

1>if the UE "Additional Measurement List" is present:
2>if the received measurement configuration in this MEASUREMENT CONTROL message, or any
measurement identities in the "Additional Measurement List" do not all have the same validity:
Reference
TS 25.331, clauses 8.4.1.9.1, 8.4.2, 8.4.1.3
1. To confirm that the UE begins or continues to monitor cells listed in IE "intra-frequency cell info list" of System
Information Block type 11 or 12 messages after it has entered CELL_FACH state from idle mode.
2. To confirm that the UE applies the reporting criteria stated in "intra-frequency measurement reporting criteria"
IE in System Information Block Type 11 or 12 in a subsequent transition to CELL_DCH state.
3. To confirm that the UE reports measured results on RACH messages, if it receives IE "Intra-frequency reporting
quantity for RACH reporting" and IE "Maximum number of reported cells on RACH" from System Information
Block Type 11 or 12 upon a transition from idle mode to CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1378
Initial Condition
System Simulator: 2 cells. Cell 1 and cell 2 are active.
Test Procedure
Table 8.4.1.3A-1 illustrates the downlink power to be applied for the 2 cells in this test case.
Table 8.4.1.3A-1
UTRA RF
Channel Number
Ch. 1 Ch. 1
PCCPCH RSCP dBm
-64 -74

The UE is initially in idle mode and camps on cell 1. The System Information Block type 11 are modified compared to
the default settings to prevent reporting of "Cell synchronisation information" and also to include cell 2 into the IE
"intra-frequency cell info list".
execute procedure P6. Next SS and UE shall execute procedure P10. Then SS and UE shall execute procedure P14. SS
starts timer T305 and waits until timer T305 expires, the UE shall send a CELL UPDATE message on the CCCH which
includes the measured value of cell 1's PCCPCH RSCP in IE "Measured results on RACH". SS then replies with CELL
UPDATE CONFIRM message on the downlink DCCH, without changing the physical channel resources.
SS transmits PHYSICAL CHANNEL RECONFIGURATION message, and allocates dedicated physical channels to the
UE. The UE shall transit to CELL_DCH state and then send a MEASUREMENT REPORT message, correctly stating
the measurement identity. The measurement identity indicated shall match the value that was previously broadcast on
System Information Block type 11 messages when the UE was still in idle mode. The IE "Measured results" in the
MEASUREMENT REPORT messages shall contain measured values of cell 2's PCCPCH RSCP.
NOTE: The Radio Bearer associated with the MEASUREMENT_IDENTITY fulfilling the reporting criteria for
an ongoing traffic volume measurement must not be mapped on transport channel of type USCH
Expected Sequence
UE SS
1 System Information Block type 1,
The UE is in idle mode and
camps onto cell 1. System
11 to be transmitted are
contents)
7.4.2.4.2) specified in TS 34.108.
UE reaches PS-DCCH FACH
7.4.2.6.2) specified in TS 34.108.
UE reaches PS-DCCH+DTCH
FACH
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1379
to confirm that no
MEASUREMENT REPORT
messages are detected. SS
waits for 5 minutes (for the
expiry of T305 timer).
6 CELL UPDATE This message shall contain IE
"Measured results on RACH"
reporting the measured
PCCPCH RSCP for cell 1.
7 CELL UPDATE CONFIRM SS does not change the
physical channel
configurations.
8 PHYSICAL CHANNEL
RECONFIGURATION
SS assigns dedicated physical
resources.
9 PHYSICAL CHANNEL
state.

- T305

5 minutes.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1380
- Cell info
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Qoffset1s,n Not Present (Default is 0 dB)
- CHOICE Mode TDD
- Qrxlevmin -103dBm
- CHOICE Mode TDD
reporting

indicator
No report
- CHOICE mode TDD
indicator
FALSE
- CHOICE mode TDD
indicator
TRUE
- CHOICE mode TDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1381
- Periodic Reporting/Event Trigger Reporting
Mode
Event trigger
- CHOICE mode TDD
- Primary CCPCH Present
- W 0.0
- Hysteresis 1.0 dB
- Amount of reporting absent
- Reporting interval absent

U-RNTI Check to see if set to same U-RNTI value assigned in
the execution of procedure P6.
Cell update cause Check to see if set to 'Periodical cell update'
Failure cause Check to see if this IE is absent
- CHOICE mode TDD
- Primary CCPCH RSCP Checked to see if set to within an acceptable range.

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "Packet to CELL_DCH from
CELL_FACH".
After step 5 the UE shall not transmit any MEASUREMENT REPORT messages on the uplink DCCH.
After step 6 the UE shall initiate cell update procedure by transmitting CELL UPDATE message on CCCH. In this
message, IE "cell update cause" shall be set to "periodic cell update". It shall include IE "measured results on RACH",
containing the measurement value for cell 1's PCCPCH RSCP.
transition from idle mode to CELL_FACH state (FDD)

1>begin or continue monitoring cells listed in the IE "inter-frequency cell info list" received in System Information
Block type 12 (or System Information Block type 11);
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1382
Reference
3GPP TS 25.331, clause 8.4.1.9.2
1. To confirm that the UE begins to monitor the list of cells assigned in the IE "inter-frequency cell info list" in
System Information Block type 11 or 12 messages, after it enters CELL_FACH state from idle mode. However,
it shall not transmit any MEASUREMENT REPORT messages to report measured results for inter-frequency
cells.
Initial Condition
Test Procedure
Columns marked "T0" denote the initial conditions, while columns marked "T1 are to be applied subsequently. The
exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.4.1.4-1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-60 -75 -75 -60

The UE is initially at idle mode and has selected cell 1 for camping. The System Information Block type 11 messages
include cell 4 into the "inter-frequency cell list" IE.
SS prompts the operator to make an outgoing call of a supported traffic class. SS and UE shall execute procedure P6.
Next SS and UE shall execute procedure P10. Then SS and UE shall execute procedure P14. The UE shall not transmit
any MEASUREMENT REPORT messages, which pertain to measurement readings for inter-frequency cells belonging
to the monitored set. SS re-adjusts its downlink power settings according to columns marked "T1" in table 8.4.1.4-1.
This is expected to trigger a cell reselection in the UE. The UE shall send CELL UPDATE message to cell 4 in order to
report this event. Upon receiving this message, SS replies with the CELL UPDATE CONFIRM message, which
includes IE "New C-RNTI", on the downlink DCCH. UE shall then reply with a UTRAN MOBILITY INFORMATION
CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1383
Expected Sequence
UE SS
1 System Information Block type 11 The UE is in idle mode in cell
1. System Information Block
type 11 to be transmitted is
contents)

7.4.2.4.2) specified in TS 34.108.


5 Void
MEASUREMENT REPORT
7 SS reconfigures the downlink
transmission power, according
to columns "T1" of table
8.4.1.4-1.
8 CELL UPDATE UE shall detect that cell 4 has
become stronger than cell 1. It
sends this message after re-
selecting to cell 4
9 CELL UPDATE CONFIRM Use message content.
CONFIRM

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1384
SIB12 Indicator FALSE
FACH measurement occasion info
- FACH Measurement occasion cycle length
coefficient
2
- Inter-frequency FDD measurement indicator TRUE
- Inter-frequency TDD measurement indicator FALSE
- Inter-RAT measurement indicators Not Present
- Frequency info
- CHOICE mode FDD
according to 25.101
- UARFCN downlink (Nd) Reference to table 6.1.2 of TS 34.108 for Cell 4
- Cell info
- CHOICE mode FDD
- Qoffsets,n 0 dB
- CHOICE Mode FDD
- Qqualmin, Qrxlevmin -20dB, -115dBm

U-RNTI Check to see if set to same U-RNTI assigned during the
execution of procedure P6.
Cell update cause Check to see if it is set to "Cell Reselection"
Protocol error info Check to see if it is absent or set to FALSE
Measured results on RACH Check to see if it is absent
Protocol error information Check to see if it is absent

New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1385

After step 5 the UE shall not transmit any MEASUREMENT REPORT messages pertaining to any measurement
quantities for cell 4.
After step 7 the UE shall reselect to cell 4 and transmit a CELL UPDATE message on the uplink CCCH of cell 4.
After step 9, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on uplink DCCH AM
RLC.
transition from idle mode to CELL_FACH state (TDD)

1>begin or continue monitoring cells listed in the IE "inter-frequency cell info list" received in System Information
Block type 12 (or System Information Block type 11);
Reference
3GPP TS 25.331, clause 8.4.1.9.2
1. To confirm that the UE begins to monitor the list of cells assigned in the IE "inter-frequency cell info list" in
System Information Block type 11 or 12 messages, after it enters CELL_FACH state from idle mode. However,
it shall not transmit any MEASUREMENT REPORT messages to report measured results for inter-frequency
cells.
Initial Condition
Test Procedure
execution. Columns marked "T0" denote the initial conditions, while columns marked "T1 are to be applied
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1386
Table 8.4.1.4A-1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
PCCPCH
RSCP
dBm
-60 -75 -75 -60

The UE is initially at idle mode and has selected cell 1 for camping. The System Information Block type 11 messages
include cell 4 into the "inter-frequency cell list" IE.
SS prompts the operator to make an outgoing call of a supported traffic class. SS and UE shall execute procedure P6.
Next SS and UE shall execute procedure P10. Then SS and UE shall execute procedure P14. The UE shall not transmit
any MEASUREMENT REPORT messages, which pertain to measurement readings for inter-frequency cells belonging
to the monitored set. SS re-adjusts its downlink power settings according to columns marked "T1" in table 8.4.1.4A-1.
This is expected to trigger a cell reselection in the UE. The UE shall send CELL UPDATE message to cell 4 in order to
report this event. Upon receiving this message, SS replies with the CELL UPDATE CONFIRM message, which
includes IE "New C-RNTI", on the downlink DCCH. UE shall then reply with a UTRAN MOBILITY INFORMATION
CONFIRM message.
Expected Sequence
UE SS
1 System Information Block type 11 The UE is in idle mode in cell
1. System Information Block
type 11 to be transmitted is
contents)

7.4.2.4.2) specified in TS 34.108.


5 Void
MEASUREMENT REPORT
7 SS reconfigures the downlink
transmission power, according
to columns "T1" of table
8.4.1.4A-1.
8 CELL UPDATE UE shall detect that cell 4 has
become stronger than cell 1. It
sends this message after re-
selecting to cell 4
9 CELL UPDATE CONFIRM Use message content.
CONFIRM

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1387

All messages indicated below shall use the same content as described in TS 34.108 clause 9, with the following
exceptions:
SIB12 Indicator FALSE
coefficient
2
- Inter-frequency FDD measurement indicator FALSE
- Inter-frequency TDD measurement indicator TRUE
- Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to table 6.1.4 of TS 34.108 for Cell 4
- Cell info
- CHOICE mode TDD
- Qoffsets,n 0 dB
- CHOICE Mode TDD

U-RNTI Check to see if set to same U-RNTI assigned during the
execution of procedure P6.

New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1388
After step 5 the UE shall not transmit any MEASUREMENT REPORT messages pertaining to any measurement
quantities for cell 4.
After step 7 the UE shall reselect to cell 4 and transmit a CELL UPDATE message on the uplink CCCH of cell 4.
After step 9, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on uplink DCCH AM
RLC.
transition from CELL_DCH to CELL_FACH state (FDD)

Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall:
1>stop intra-frequency type measurement reporting;
1>if the transition is due to a reconfiguration message which included the IE "Primary CPICH info" (for FDD) or
"Primary CCPCH info" (for TDD), and the UE selects a cell other than that indicated by this IE; or
1>if the transition is due to a reconfiguration message which does not include the IE "Primary CPICH info" (for
FDD) or "Primary CCPCH info" (for TDD); or
1>if the transition is not due to a reconfiguration message:
2>delete the measurements of type intra-frequency associated with the variable MEASUREMENT_IDENTITY.
1>begin monitoring cells listed in the IE "intra-frequency cell info list" received in System Information Block type
12 (or System Information Block type 11, according to subclause 8.1.1.6.11 in [8] TS 25.331).

Information Block type 12 (or System Information Block type 11, according to subclause 8.1.1.6.11 in [8] TS
25.331);
(or System Information Block type 11, according to subclause 8.1.1.6.11 in [8] TS 25.331):
3>send the MEASUREMENT REPORT message when reporting criteria in IE "Reporting information for
state CELL_DCH" are fulfilled.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1389
Reference
3GPP TS 25.331, clause 8.4.1.6.1, 8.4.1.7.1
1. To confirm that the UE stops performing intra-frequency measurement reporting specified in a
MEASUREMENT CONTROL message, when it moves from CELL_DCH state to CELL_FACH state.
2. To confirm that the UE reads the System Information Block type 11 or 12 messages when it enters
CELL_FACH state from CELL_DCH state, and starts to monitor the cells listed in the IE "intra-frequency cell
info list".
3 To confirm that the UE performs measurements on uplink RACH transmissions and appends the measured
results in RACH messages, when it receives IE "intra-frequency reporting quantity for RACH reporting" and IE
"Maximum number of reported cells on RACH" in the System Information Block type 11 or 12 messages.
4. To confirm that the UE applies the reporting criteria in IE "intra-frequency reporting criteria" in System
Information Block Type 11 or 12 messages following a state transition from CELL_FACH to CELL_DCH, if no
intra-frequency measurements applicable to CELL_DCH are stored.
Initial Condition
System Simulator: 3 cells Cell 1 and cell 2 are active, while cell 3 is switched off..
UE: PS-DCCH+DTCH_DCH (state 6-10) in cell 1 as specified in clause 7.4 of TS 34.108.
For system information block 11 of Cell 1 (gives IE's which are different from defaults given in 34.108 subclause 6.1)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1390
- Cell info
- CHOICE mode FDD
-Intra-frequency measurement quantity Not Present
-Intra-frequency reporting quantity for RACH
reporting
Not Present
-Maximum number of reported cells on RACH Not Present
-Reporting information for state CELL_DCH Not Present

Test Procedure
Table 8.4.1.5-1
T0 T1 T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
CPICH Ec dBm/
3.84
MHz
-60 -60 -75 -85 -122 -70

The UE is initially in CELL_DCH state. The System Information Block type 11 message is modified compared to the
default message contents, in order to prevent the reporting of "Cell synchronisation information". No measurement to be
applied by the UE in CELL_DCH state is specified in any of the System Information Block type 11 or 12 messages.
SS sends a MEASUREMENT CONTROL message to UE. In this message, the SS requests the establishment of an
intra-frequency measurement for the measurement of cell 2's CPICH RSCP. At the same time, reporting of CPICH
RSCP values of active set cells and monitored set cells are requested with the reporting criteria set to "periodic
reporting" and "reporting interval" set to 16 seconds. The UE shall start transmitting MEASUREMENT REPORT
messages at 16 seconds interval corresponding to the requested reporting event.
SS transmits PHYSICAL CHANNEL RECONFIGURATION message to move the UE to CELL_FACH. After
receiving this message, the UE shall reconfigure itself and reply with a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on RACH. SS monitors the uplink channels to verify that no
MEASUREMENT REPORT messages are received.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1391
SS reconfigures itself according to the settings in columns marked "T1" in table 8.4.1.5-1. SS transmits System
Information Block type 12 messages in cell 1, which include cell 3 into the IE "intra-frequency cell info list" and
modifies SIB11 to indicate that SIB12 is now being broadcast. IEs "Intra-frequency reporting quantity for RACH
Reporting" and IE "Maximum number of Reported cells on RACH" are also specified in the System Information Type
12 messages. Event type 1a reporting criterion is specified for intra-frequency measurements. SS transmit SYSTEM
INFORMATION CHANGE INDICATION message to UE. SS waits until T305 has expired. The UE shall respond
with a CELL UPDATE message, which comprises IE "Measured results on RACH" to report the readings of CPICH
RSCP for cell 1 and cell 3. SS replies with CELL UPDATE CONFIRM message on the downlink DCCH. This message
does not change the physical resources nor allocate any new RNTI identities. SS transmits PHYSICAL CHANNEL
RECONFIGURATION message again, and configures dedicated physical channel for both uplink and downlink
directions. The UE shall send PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and return to
CELL_DCH state. SS listens to the uplink DCCH for MEASUREMENT REPORT messages.
SS shall receive the MEASUREMENT REPORT messages at 500 milliseconds interval.
SS verifies that it includes CPICH RSCP values of the cells 1and 3 in IE "Cell measured results" and the triggering of
event '1a' on cell 3 in IE "Event results".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1392
Expected Sequence
UE SS
1 UE is in PS-
DCCH+DTCH_DCH (state 6-
10) in cell 1.
2 Void
3 Void
4 Void
5 MEASUREMENT CONTROL SS requests for measurement
of cell 2s CPICH RSCP value
and reporting of CPICH RSCP
values of active cells and
monitored set cells.
6 MEASUREMENT REPORT UE shall send periodic report
at 16 seconds interval.
7 PHYSICAL CHANNEL
RECONFIGURATION
SS moves the UE to
CELL_FACH state.
8 PHYSICAL CHANNEL
UE shall move to CELL_FACH
state.
9 Master Information Block
System Information Block type 11, 12
SS reconfigures itself
according to the settings
stated in column "T1" of table
8.4.1.5-1. SIB 11 is modified to
indicate that SIB12 is now
broadcast and to add cell 2 as
a neighbour cell. SIB 12
indicates that cell 3 is included
in the IE "intra-frequency cell
info list". SS waits for 1 minute
and verifies that no
MEASUREMENT REPORT
uplink.
10 SYSTEM INFORMATION CHANGE
INDICATION
SS waits until T305 has
expired.
message with measured
results on RACH channels for
cell 1 and cell 3 present in this
message.
12 CELL UPDATE CONFIRM No changes in physical
resource allocation and RNTI
identities.
13 PHYSICAL CHANNEL
RECONFIGURATION
SS configures dedicated
physical channels.
14 PHYSICAL CHANNEL
state.
15 MEASUREMENT REPORT Repeated at 500 milliseconds
interval

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1393
- Periodic Reporting / Event Trigger Reporting Mode Periodical Reporting
- New intra-frequency info list
- Cell info
- CHOICE mode FDD
indicator
FALSE
indicator
FALSE
used frequency
- CHOICE report criteria Periodical reporting criteria

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1394
Measured Results
list"
Additional measured result list Check to see if this IE is absent

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "(Packet to CELL_FACH from
CELL_DCH in PS)"
MIB Value Tag 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1395
SIB12 indicator TRUE
- Cell info
- CHOICE mode FDD
- Cell info
- CHOICE mode FDD
- Qoffsets,n 0 dB
- CHOICE Mode FDD
- Qqualmin -20dB
- Qrxlevmin -115dBm
reporting
Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1396
- Intra-frequency cell cells
- Cell info
- CHOICE mode FDD
- Qoffsets,n 0dB
- Maximum allowed UL TX power 0dBm
- CHOICE Mode FDD
- Qqualmin, Qrxlevmin -20dB, -115dBm
reporting

indicator
No report
- CHOICE mode FDD
- Maximum number of reported cells on RACH Current cell +best neighbour
indicator
FALSE
- CHOICE mode FDD
indicator
FALSE
- CHOICE mode FDD
- Parameter required for each event
- Reporting range constant 14.5dB
- Cells forbidden to affect reporting Not present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1397
- W 0.0
- Hysteresis 1.0 dB
- Reporting Interval 500 milliseconds
used frequency
- Inter-RAT measurement system information Not present
- Traffic volume measurement system information Not present

SYSTEM INFORMATION CHANGE INDICATION (Step 10)
- MIB Value tag

2

U-RNTI Check to see if set to the same value assigned during
the execution of procedure P3 or P5.
Cell update cause Check to see if it is set to "Periodical cell update"
Failure case Check to see if it is absent
- CHOICE measurement quantity Check to see if set to "CPICH RSCP"
- Measurement results for monitored cells
- SFN-SFN observed time difference Check to see if it is absent
- Primary scrambling code Check to see if the same as cell 3's code.
- CHOICE measurement quantity Check to see if set to "CPICH RSCP"

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "(Packet to CELL_DCH from
CELL_FACH in PS)".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1398
Measured Results
list"
- Intra-frequency measurement results list
Event results Check to see if this set to 'Intra-frequency measurement
event results'
- Intra-frequency event identity Check to see if set to '1a'
- CHOICE Mode Check to see if set to 'FDD'

After step 5, the UE shall start to transmit MEASUREMENT REPORT messages at 16 seconds interval. The message
shall contain IE "measured result" to report cell 2's CPICH RSCP value.
After step 8, the UE shall not send any MEASUREMENT REPORT messages containing reporting quantities requested
in MEASUREMENT CONTROL messages in step 5.
After step 10, the UE shall perform a cell update procedure and transmit a CELL UPDATE message. In this message,
measured values CPICH RSCP for cell 1 and cell 3 shall be included in the IE "measured results on RACH".
After step 14, the UE shall apply the intra-frequency measurement reporting criteria" received in System Information
Block type 12 messages of step 9. It shall send MEASUREMENT REPORT messages at 500 milliseconds interval. In
these messages, triggering of event '1a' shall be reported in IE "Event results" with IE "Primary CPICH info" containing
the primary scrambling code for cell 3.
The message shall contain IE "measured result" to report CPICH RSCP values of cell 1and 3.
transition from CELL_DCH to CELL_FACH state (TDD)

Upon transition from CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH state, the UE shall:
1>stop intra-frequency type measurement reporting;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1399
1>if the transition is due to a reconfiguration message which included the IE "Primary CPICH info" (for FDD) or
"Primary CCPCH info" (for TDD), and the UE selects a cell other than that indicated by this IE; or
1>if the transition is due to a reconfiguration message which does not include the IE "Primary CPICH info" (for
FDD) or "Primary CCPCH info" (for TDD); or
1>if the transition is not due to a reconfiguration message:
2>delete the measurements of type intra-frequency associated with the variable MEASUREMENT_IDENTITY.
1>begin monitoring cells listed in the IE "intra-frequency cell info list" received in System Information Block type
12 (or System Information Block type 11, according to subclause 8.1.1.6.11 in [8] TS 25.331).
Reference
3GPP TS 25.331, clause 8.4.1.6.1, 8.4.1.7.1
1. To confirm that the UE stops performing intra-frequency measurement reporting specified in a
MEASUREMENT CONTROL message, when it moves from CELL_DCH state to CELL_FACH state.
2. To confirm that the UE reads the System Information Block type 11 or 12 messages when it enters
CELL_FACH state from CELL_DCH state, and starts to monitor the cells listed in the IE "intra-frequency cell
info list".
3 To confirm that the UE performs measurements on uplink RACH transmissions and appends the measured
results in RACH messages, when it receives IE "intra-frequency reporting quantity for RACH reporting" and IE
"Maximum number of reported cells on RACH" in the System Information Block type 11 or 12 messages.
4. To confirm that the UE applies the reporting criteria in IE "intra-frequency reporting criteria" in System
Information Block Type 11 or 12 messages following a state transition from CELL_FACH to CELL_DCH, if no
intra-frequency measurements applicable to CELL_DCH are stored.
Initial Condition
System Simulator: 3 cells Cell 1 and cell 2 are active, while cell 3 is switched off.
For MASTER IFORMATION BLOCK and system information block 11 of Cell 1 (gives IE's which are different from
defaults given in 34.108 subclause 6.1) to be transmitted before idle update preamble.
MIB Value Tag 1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1400
- Cell info
- CHOICE mode TDD
- Primary PCCPCH Info Refer to clause titled "Default settings for cell No.1
reporting
Not Present

Test Procedure
execution. Columns marked "T0" denote the initial conditions, while column marked as "T1" will be applied during the
test.
Table 8.4.1.5A-1
T0 T1 T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
PCCPCH
RSCP
dBm
-60 -60 -75 -85 off -55

The UE is initially in CELL_DCH state. The System Information Block type 11 message is modified compared to the
default message contents, in order to prevent the reporting of "Cell synchronisation information". No measurement to be
applied by the UE in CELL_DCH state is specified in any of the System Information Block type 11 or 12 messages.
SS sends a MEASUREMENT CONTROL message to UE. In this message, the SS requests the establishment of an
intra-frequency measurement for the measurement of cell 2's PCCPCH RSCP. At the same time, reporting of PCCPCH
RSCP values of active set cells and monitored set cells are requested with the reporting criteria set to "periodic
reporting" and "reporting interval" set to 16 seconds. The UE shall start transmitting MEASUREMENT REPORT
messages at 16 seconds interval corresponding to the requested reporting event.
SS transmits PHYSICAL CHANNEL RECONFIGURATION message to move the UE to CELL_FACH. After
receiving this message, the UE shall reconfigure itself and reply with a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message on RACH. SS monitors the uplink channels to verify that no
SS reconfigures itself according to the settings in columns marked "T1" in table 8.4.1.5A-1. SS transmits System
Information Block type 12 messages in cell 1, which include cell 3 into the IE "intra-frequency cell info list" and
modifies SIB11 to indicate that SIB12 is now being broadcast. IEs "Intra-frequency reporting quantity for RACH
Reporting" and IE "Maximum number of Reported cells on RACH" are also specified in the System Information Type
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1401
12 messages. Event type 1g reporting criterion is specified for intra-frequency measurements. SS transmit SYSTEM
INFORMATION CHANGE INDICATION message to UE. SS waits until T305 has expired. The UE shall respond
with a CELL UPDATE message, which comprises IE "Measured results on RACH" to report the readings of PCCPCH
RSCP for cell 1 and cell 3. SS replies with CELL UPDATE CONFIRM message on the downlink DCCH. This message
does not change the physical resources nor allocate any new RNTI identities. SS transmits PHYSICAL CHANNEL
RECONFIGURATION message again, and configures dedicated physical channel for both uplink and downlink
directions. The UE shall send PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and return to
CELL_DCH state. SS listens to the uplink DCCH for MEASUREMENT REPORT messages.
SS shall receive the MEASUREMENT REPORT messages.
SS verifies that it includes PCCPCH RSCP values of the cells 1, 2 and 3 in IE "Cell measured results" and the triggering
of event '1g' on cell 3 in IE "Event results".
Expected Sequence
UE SS
1 UE is in PS-
DCCH+DTCH_DCH (state 6-
10) in cell 1.
of cell 2s PCCPCH RSCP
value and reporting of
PCCPCH RSCP values of
active cell and monitored set
cell.
3 MEASUREMENT REPORT UE shall send periodic report
at 16 seconds interval.
4 PHYSICAL CHANNEL
RECONFIGURATION
SS moves the UE to
CELL_FACH state.
5 PHYSICAL CHANNEL
UE reaches CELL_FACH
state.
System Information Block type 11, 12
SS reconfigures itself
according to the settings
stated in column "T1" of table
8.4.1.5A-1. SIB 11 is modified
to indicate that SIB12 is now
broadcast and includes cell 2
as a neighbour cell. SIB 12
indicates that cell 3 is included
in the IE "intra-frequency cell
info list". Event 1g is also
configured for cell 3. SS waits
for 1 minute and verifies that
no MEASUREMENT REPORT
uplink.
INDICATION
SS waits until T305 has
expired.
message with measured
results on RACH channels for
cell 1 and cell 3 present in this
message.
9 CELL UPDATE CONFIRM No changes in physical
resource allocation and RNTI
identities.
10 PHYSICAL CHANNEL
RECONFIGURATION
SS configures dedicated
physical channels.
11 PHYSICAL CHANNEL
state.
12 MEASUREMENT REPORT The UE shall report event 1G
for change to best cell, cell3.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1402
Mode
- Cell info
- CHOICE mode TDD
- CHOICE mode TDD
indicator
FALSE
CHOICE MODE TDD
indicator
FALSE
CHOICE MODE TDD
frequency or within active and/or monitored set on
non-used frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1403
Measured Results
results list"
Additional measured result list Check to see if this IE is absent

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "(Packet to CELL_FACH from
CELL_DCH in PS)"
MIB Value Tag 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1404
- Cell info
- CHOICE mode TDD
- Cell info
- CHOICE mode TDD
- Qoffsets,n 0 dB
- CHOICE Mode TDD
reporting
Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1405
- Intra-frequency cell cells
- Cell info
- CHOICE mode TDD
- Qoffsets,n 0dB
- Maximum allowed UL TX power 30dBm
- CHOICE Mode TDD
- Qrxlevmin -103dBm
- CHOICE mode TDD
- Measurement list
reporting

indicator
No report
- CHOICE mode TDD
- Maximum number of reported cells on RACH Current cell +best neighbour
indicator
FALSE
- CHOICE mode TDD
indicator
FALSE
- CHOICE mode TDD
- Reporting range constant 20.0 dB
- W 0.0
- Hysteresis 1.0 dB
- Amount of reporting absent
- Reporting Interval absent
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1406
- Traffic volume measurement system information Not present

- MIB Value tag

2

U-RNTI Check to see if set to the same value assigned during
the execution of procedure P3 or P5.
Cell update cause Check to see if it is set to "Periodical cell update"
Failure case Check to see if it is absent
- SFN-SFN observed time difference Not Checked
- CHOICE mode TDD
- Cell parameters Id Check to see if the same as cell 1.
- PCCPCH RSCP Check to see if it is present
- SFN-SFN observed time difference Not Checked
- CHOICE mode TDD
- Cell parameters Id Check to see if the same as cell 3.

Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "(Packet to CELL_DCH from
CELL_FACH in PS)".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1407
Measured Results
results list"
- Intra-frequency measurement results list
- Proposed TGSN Reporting required Check to see if this IE is absent
- PCCPCH RSCP reporting indicator Check to see if this IE is present
Event results Check to see if this set to 'Intra-frequency
measurement event results'
- Intra-frequency event identity Check to see if set to '1g'
- CHOICE Mode Check to see if set to 'TDD'
- Cell parameters id Check to see if it's the same for cell 3

After step 2, the UE shall start to transmit MEASUREMENT REPORT messages at 16 seconds interval. The message
shall contain IE "measured result" to report cell 2's PCCPCH RSCP value.
After step 5, the UE shall not send any MEASUREMENT REPORT messages containing reporting quantities requested
in MEASUREMENT CONTROL messages in step 2.
After step 7, the UE shall perform a cell update procedure and transmit a CELL UPDATE message. In this message,
measured values PCCPCH RSCP for cell 1 and cell 3 shall be included in the IE "measured results on RACH".
After step 12, the UE shall apply the intra-frequency measurement reporting criteria" received in System Information
Block type 12 messages of step 6. It shall send MEASUREMENT REPORT messages. In these messages, triggering of
event '1g' shall be reported in IE "Event results" with IE " Cell parameters Id " containing the same for cell 3.
The message shall contain IE "measured result" to report PCCPCH RSCP values of cell 1, 2 and 3.
transition from CELL_DCH to CELL_FACH state (FDD)

Upon transition from CELL_DCH to CELL_FACH/ CELL_PCH/URA_PCH state, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1408
1>stop the inter-frequency type measurement reporting assigned in a MEASUREMENT CONTROL message;
1>begin monitoring cells listed in the IE "inter-frequency cell info list" received in System Information Block type
12 (or System Information Block type 11);
1>in CELL_FACH state:
2>perform measurements on other frequencies according to the IE "FACH measurement occasion info".
Reference
3GPP TS 25.331, clause 8.4.1.6.2
1. To confirm that UE ceases inter-frequency type measurement reporting assigned in MEASUREMENT
CONTROL message when moving from CELL_DCH state to CELL_FACH.
2. To confirm that the UE begins to monitor the cells listed in "inter-frequency cell info" received in System
Information Block type 11 or 12 messages, following a state transition from CELL_DCH state to CELL_FACH
state.
Initial Condition
Test Procedure
Table 8.4.1.6-1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
CPICH Ec dBm/
3.84
MHz
-60 -75 -75 -60

The UE is initially in CELL_DCH state. The System Information Block type 12 message is modified with respect to the
default settings, so that no measurement tasks are required of the UE. If UE requires compressed mode, SS transmits
PHYSICAL CHANNEL RECONFIGURATION message. In this message, IE "DPCH compressed mode info" is
present, which indicates that the UE shall apply the given parameters for compressed mode operations. The UE shall
return a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to acknowledge that compressed mode
mechanism can be exercised.
SS sends a MEASUREMENT CONTROL message to the UE, including cell 4 into the IE "inter-frequency cell info".
The IE "CHOICE reporting criteria" in this message is set to "periodic reporting criteria". SS waits for 8 seconds to
allow the periodic timer to expire. The UE shall send a MEASUREMENT REPORT message containing IE "inter-
frequency cell measurement results" to report cell 4's CPICH RSCP value. SS transmits PHYSICAL CHANNEL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1409
RECONFIGURATION message and reconfigures common physical channels. The UE shall move to CELL_FACH
state and then return a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to SS.
SS modifies the contents of Master Information Block (MIB) and System Information Block (SIB) type 12. In SIB 12,
cell 4 is added to the cells listed in the "inter-frequency cell info" IE. SS transmit SYSTEM INFORMATION
CHANGE INDICATIONmessage to UE. SS waits for 8 seconds to detect any uplink MEASUREMENT REPORT
messages. SS verifies that no MEASUREMENT REPORT message(s) are received as a result of inter-frequency
measurements. SS then reconfigures the downlink transmission power settings of cell 1 and cell 4 according to the
values stated in columns "T1" of table 8.4.1.6-1. SS waits for the UE to perform cell re-selection. The UE shall transmit
a CELL UPDATE message on the uplink CCCH of cell 4, specifying the "cell update cause" IE as "cell re-selection".
SS replies with CELL UPDATE CONFIRM message, which includes IE "New C-RNTI", on the downlink DCCH to
complete the cell update procedure. The UE shall reply with a UTRAN MOBILITY INFORMATION CONFIRM
message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1410
Expected Sequence
UE SS
1 System Information Block type 12 PS-DCCH+DTCH_DCH (state
6-10) in cell 1. System
Information Block type 12 is
modified with respect to the
default settings. All
measurement and reporting
activities are disabled in this
message.
2 Void If compresed mode is not
required (refer ICS/IXIT), goto
step 8.
3 Void
4 Void
5 Void
6 PHYSICAL CHANNEL
RECONFIGURATION
SS instructs UE to begin
7 PHYSICAL CHANNEL
state.
8 MEASUREMENT CONTROL SS indicates that the CPICH
RSCP of cell 4 shall be
monitored and reported. SS
waits for 8 seconds for the
reception of MEASUREMENT
REPORT message.
9 MEASUREMENT REPORT UE shall transmit this
message to report cell 4's
CPICH RSCP value.
10 PHYSICAL CHANNEL
RECONFIGURATION
SS configures common
physical channels.
11 PHYSICAL CHANNEL
UE shall moves to
CELL_FACH state.
12 Master Information Block,
SS modifies MIB and SIB 12.
Cell 4 is included in the IE
"inter-frequency cell info"
INDICATION
SS waits for 8 seconds to
verify that no
MEASUREMENT REPORT
uplink DCCH.
14 SS changes the power
settings for cell 1 and cell 4
according to columns marked
"T1" of table 8.4.1.6-1, and
then waits for the UE to re-
select to a new cell.
15 CELL UPDATE UE shall perform cell re-
selection and transmit this
message on the new cell.
CONFIRM

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1411
System Information Block Type 12 (Step 1)
coefficient
2

Use the same message sub-type found in Clause 9 of TS 34.108, which is entitled "Transition to CELL_DCH"
Use the same message sub-type found in Annex A, which is entitled "(Packet to CELL_DCH from CELL_DCH in
PS)", with the following exceptions in the IE(s) concerned:
- CHOICE Mode FDD
- TGPSI 1
- TGCFN (Current CFN+(256 TTI/10msec)) mod 256

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL Mode UL and DL or DL only depending on UE capability
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1412
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
FALSE
used frequency
- UE state CELL_DCH
- Inter-frequency set update Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1413
Measured Results
list"
- Frequency info

If UE do not require compressed mode, use the same message sub-type found in TS 34.108 clause 9, which is entitled
"(Packet to CELL_FACH from CELL_DCH in PS)".
If UE requires compressed mode, use the same message sub-type found in TS34.108 clause 9, which is entitled "(Packet
to CELL_FACH from CELL_DCH in PS)", with the following exceptions in the IE(s) concerned:
- CHOICE mode FDD
- TGPSI 1
- TGCFN Not Present
Not Present

Master Information Block (Step 12)
MIB value tag 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1414
- Cell_selection_and_reselection_-quality_measure CPICH_Ec/No
- CHOICE Inter-frequency cell removal Not Present
- Frequency info
- CHOICE mode FDD
according to TS 25.101
- UARFCN downlink (Nd) Reference to table 6.1.2 of TS 34.108 for Cell 4
- Cell info
- CHOICE Mode FDD
- Primary CPICH Tx power Not Present
- TX diversity indicator FALSE
- Cell selection and re-selection info Not Present

- MIB Value tag

2

U-RNTI Check to see if same to value assigned in P3 or P5

Use the same message sub-type found in Annex A, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1415
If UE requires compressed mode, after step 6, the UE shall transmit PHYSICAL CHANNEL RECONFIGURATION
After step 8 the UE shall transmit MEASUREMENT REPORT message to report cell 4's RSCP value in the IE "inter-
frequency cell measured results".
After step 10, the UE shall transmit PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
After step 11 the UE shall stop sending MEASUREMENT REPORT messages, which contain inter-frequency
measured results for cell 4's CPICH RSCP value.
After step 14 the UE shall transmit CELL UPDATE message on the uplink CCCH of cell 4, and the "cell update cause"
IE shall be set to "cell reselection".
After step 16, the UE shall transmit UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH
AM RLC.
transition from CELL_DCH to CELL_FACH state (TDD)

Upon transition from CELL_DCH to CELL_FACH/ CELL_PCH/URA_PCH state, the UE shall:
1>stop the inter-frequency type measurement reporting assigned in a MEASUREMENT CONTROL message;
1>begin monitoring cells listed in the IE "inter-frequency cell info list" received in System Information Block type
12 (or System Information Block type 11);
1>in CELL_FACH state:
2>perform measurements on other frequencies according to the IE "FACH measurement occasion info".
Reference
3GPP TS 25.331, clause 8.4.1.6.2
1. To confirm that UE ceases inter-frequency type measurement reporting assigned in MEASUREMENT
CONTROL message when moving from CELL_DCH state to CELL_FACH.
2. To confirm that the UE begins to monitor the cells listed in "inter-frequency cell info" received in System
Information Block type 11 or 12 messages, following a state transition from CELL_DCH state to CELL_FACH
state.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1416
Test Procedure
execution. Columns marked "T0" denote the initial conditions, while columns marked "T1 are to be applied
Table 8.4.1.6A-1
T0 T1 T0 T1
UTRA RF
Channel
Number
Ch. 1 Ch. 2
PCCPCH
RSCP
dBm
-60 -75 -75 -60

The UE is initially in CELL_DCH state. The System Information Block type 12 message is modified with respect to the
default settings, so that no measurement tasks are required of the UE.
SS sends a MEASUREMENT CONTROL message to the UE, including cell 4 into the IE "inter-frequency cell info".
The IE "CHOICE reporting criteria" in this message is set to "periodic reporting criteria". SS waits for 8 seconds to
allow the periodic timer to expire. The UE shall send a MEASUREMENT REPORT message containing IE "inter-
frequency cell measurement results" to report cell 4's PCCPCH RSCP value. SS transmits PHYSICAL CHANNEL
RECONFIGURATION message and reconfigures common physical channels. The UE shall move to CELL_FACH
state and then return a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to SS.
SS modifies the contents of Master Information Block (MIB) and System Information Block (SIB) type 12. In SIB 12,
cell 4 is added to the cells listed in the "inter-frequency cell info" IE. SS transmit SYSTEM INFORMATION
CHANGE INDICATIONmessage to UE. SS waits for 8 seconds to detect any uplink MEASUREMENT REPORT
messages. SS verifies that no MEASUREMENT REPORT message(s) are received as a result of inter-frequency
measurements. SS then reconfigures the downlink transmission power settings of cell 1 and cell 4 according to the
values stated in columns "T1" of table 8.4.1.6A-1. SS waits for the UE to perform cell re-selection. The UE shall
transmit a CELL UPDATE message on the uplink CCCH of cell 4, specifying the "cell update cause" IE as "cell re-
selection". SS replies with CELL UPDATE CONFIRM message, which includes IE "New C-RNTI", on the downlink
DCCH to complete the cell update procedure. The UE shall reply with a UTRAN MOBILITY INFORMATION
CONFIRM message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1417
Expected Sequence
UE SS
1 System Information Block type 12 PS-DCCH+DTCH_DCH (state
6-10) in cell 1. System
Information Block type 12 is
modified with respect to the
default settings. All
activities are disabled in this
message.
2 MEASUREMENT CONTROL SS indicates that the PCCPCH
RSCP of cell 4 shall be
monitored and reported. SS
waits for 8 seconds for the
reception of MEASUREMENT
REPORT message.
3 MEASUREMENT REPORT UE shall transmit this
message to report cell 4's
PCCPCH RSCP value.
4 PHYSICAL CHANNEL
RECONFIGURATION
SS configures common
physical channels.
5 PHYSICAL CHANNEL
UE shall moves to
CELL_FACH state.
6 Master Information Block,
SS modifies MIB and SIB 12.
Cell 4 is included in the IE
"inter-frequency cell info"
INDICATION
SS waits for 8 seconds to
verify that no
MEASUREMENT REPORT
uplink DCCH.
8 SS changes the power
settings for cell 1 and cell 4
according to columns marked
"T1" of table 8.4.1.6A-1, and
then waits for the UE to re-
select to a new cell.
9 CELL UPDATE UE shall perform cell re-
selection and transmit this
message on the new cell.
CONFIRM

System Information Block Type 12 (Step 1)
coefficient
2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1418
- Frequency info
- Cell info
- CHOICE Mode TDD
estimate
PCCPCH RSCP
indicator
FALSE
used frequency
- UE state CELL_DCH

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1419
Measured Results
list"
- Frequency info

If UE do not require compressed mode, use the same message sub-type found in TS 34.108 clause 9, which is entitled
"(Packet to CELL_FACH from CELL_DCH in PS)".
MIB value tag 2

- CHOICE Inter-frequency cell removal Not Present
- Frequency info
- CHOICE mode TDD
- UARFCN (Nt) Reference to table 6.1.4 of TS 34.108 for Cell 4
- Cell info
- CHOICE Mode TDD
- Primary CCPCH info Refer to clause titled "Default settings for cell No.4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1420
- MIB Value tag

2

U-RNTI Check to see if same to value assigned in P3 or P5

Use the same message sub-type found in TS 34.108 clause 9, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

After step 2 the UE shall transmit MEASUREMENT REPORT message to report cell 4's RSCP value in the IE "inter-
frequency cell measured results".
After step 4, the UE shall transmit PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
After step 5 the UE shall stop sending MEASUREMENT REPORT messages, which contain inter-frequency measured
results for cell 4's PCCPCH RSCP value.
After step 8 the UE shall transmit CELL UPDATE message on the uplink CCCH of cell 4, and the "cell update cause"
IE shall be set to "cell reselection".
AM RLC.
transition from CELL_FACH to CELL_DCH state (FDD)

Upon transition from CELL_FACH to CELL_DCH state:
1>if intra-frequency measurements applicable to CELL_DCH state are stored in the variable
2>if the cell in which the UE transited from CELL_FACH state is included in the active set for the CELL_DCH
state, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1421
2>otherwise:
3>the UE should not resume the measurement reporting. If the UE does not resume the measurement
reporting, the measurement shall be restarted when a MEASUREMENT CONTROL message is received
with the corresponding measurement identity.

Upon cell reselection while in CELL_FACH/CELL_PCH/URA_PCH state and the cell reselection has occurred after
the measurement control information was stored, the UE shall:
1>delete all measurements of type intra-frequency, inter-frequency, and inter-RAT associated with the variable
MEASUREMENT_IDENTITY;

1>delete the traffic volume measurements that have not been set up or modified through a MEASUREMENT
CONTROL message.

Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in subclause 8.6
unless otherwise specified below.
The UE shall:
3>if the UE is in CELL_FACH state:
2>for measurement types "inter-RAT measurement" or "inter-frequency measurement" that require
measurements on a frequency other than the actually used frequency:

2>for measurement type "inter-frequency measurement" that requires measurements only on the same
frequency as the actually used frequency:


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1422
5>if the UE is in CELL_FACH state:
4>if measurement type is set to "intra-frequency measurement", for any of the optional IEs "Intra-
frequency measurement objects list", "Intra-frequency measurement quantity", "Intra-frequency
reporting quantity", "Measurement Validity", "report criteria" and "parameters required for each
event" (given "report criteria" is set to "intra-frequency measurement reporting criteria") that are
present in the MEASUREMENT CONTROL message:

5>replace the corresponding information (the IEs listed above and all their children) stored in
variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE
"measurement identity" with the one received in the MEASUREMENT CONTROL message;
5>leave all other stored information elements unchanged in the variable
Reference
3GPP TS 25.331, clause 8.4.1.3, 8.4.1.6a and 8.4.1.7.1
- To confirm that UE retrieves stored measurement control information for intra-frequency measurement type with
"measurement validity" assigned to "CELL_DCH", after it enters CELL_DCH state from CELL_FACH state.
- To confirm that the UE continues to monitor the neighbouring cells listed "intra-frequency cell info" IE in the
System Information Block type 11 or 12 messages, if no intra-frequency measurements applicable to
CELL_DCH are stored.
- To confirm that the UE transmits MEASUREMENT REPORT messages if reporting criteria stated in IE "intra-
frequency measurement reporting criteria" in System Information Block type 11 or 12 messages are fulfilled.
- To confirm that a MEASUREMENT CONTROL message received in CELL_DCH state overrides the
measurement and associated reporting contexts maintained in the UE by virtue of System Information Block
type 11 or 12 messages.
- To confirm that the UE delete all measurements of type intra-frequency upon cell reselection while in
CELL_FACH.
Initial Condition
System Simulator: 3 cells Cell 1, cell 2 and cell 3 are active.
UE: PS-DCCH+DTCH_FACH (state 6-11).
Test Procedure
Column marked "T0" denotes the initial conditions, while columns marked "T1" are to be applied subsequently. The
exact instants on which these values shall be applied are described in the text in this clause.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1423
Table 8.4.1.7-1
Para-meter Unit Cell 1 Cell 2 Cell 3
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch. 1
CPICH Ec dBm
/3.84
MHz
-60 -122 -122 -70 -60 -60 -75 -75 -60

The UE is brought to CELL_FACH state in cell 1. (step 1) SS sends SYSTEM INFORMATION CHANGE
INDICATION message to UE to inform UE of the modification in the system information.
SS sends a RADIO BEARER RECONFIGURATION message to UE (step2), and configures dedicated physical
channels on both uplink and downlink directions. The UE shall move to CELL_DCH state and then return RADIO
BEARER RECONFIGURATION COMPLETE message (step3). The UE shall send a MEASUREMENT REPORT
message containing IE "Measured results" to report cell 2's CPICH RSCP value and IE "event results" to report
triggering of event type "1e" (step 4). After receiving the MEASUREMENT REPORT message, SS transmits a
MEASUREMENT CONTROL message with only cell 3 included in the IE "intra-frequency cell info" (step 5). After
receiving such a message, the UE shall transmit another set of MEASUREMENT REPORT message for measurement
identity =11. SS verifies that only measurement readings for cell 3 's CPICH RSCP are report in IE "cell measured
results" in this message (step 6). Cell 3 shall also trigger event 1e for the measurement that the UE had stored from
system information, so a MEASUREMENT REPORT message shall be received for measurement identity =10 (step
6a) as well. The order of steps 6 and 6a is not important and could be reversed.
Next, SS sends a PHYSICAL CHANNEL RECONFIGURATION message (step 7). SS configures common physical
channels for both the uplink and the downlink directions. The UE shall transit to CELL_FACH state and then reply with
a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (step 8). SS waits and checks the uplink
RACH to confirm that no MEASUREMENT REPORT messages are received (step 9).
SS transmits then a RADIO BEARER RECONFIGURATION message to the UE, to move it to CELL_DCH state (step
9a). The UE shall move to that state, and transmit a RADIO BEARER RECONFIGURATION COMPLETE message to
SS (step 9b). Shortly after, a MEASUREMENT REPORT message shall be received that has been triggered by cell 2,
i.e. the UE shall have deleted the measurement configured through the MEASUREMENT CONTROL message of step
5, and instead apply the measurement configured in SIB12: a MEASUREMENT REPORT message with measurement
identity 10 shall be received while no such message with measurement identity 11 shall be sent by the UE (step 9c).
SS transmits MEASUREMENT CONTROL message on the downlink DCCH, to configure intra-frequency
measurements with validity CELL_DCH (step 10). The UE shall send a MEASUREMENT REPORT message (with IE
Measurement identity =12) to the SS triggered by cell 2 (step 14).
SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE to move it to CELL_FACH state
(step 14a). The UE shall move to that state and transmit a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message to SS (step 14b). SS shall wait and check that no MEASUREMENT REPORT messages are
detected on the uplink DCCH (step 14c).
SS transmits a RADIO BEARER RECONFIGURATION message to the UE, to move it to CELL_DCH state (step
14d). The UE shall move to that state, and transmit a RADIO BEARER RECONFIGURATION COMPLETE message
to SS (step 14e). Shortly after, a MEASUREMENT REPORT message shall be received that has been triggered by cell
2, i.e the UE shall have retrieved the measurement configured through the MEASUREMENT CONTROL message of
step 10, instead of the ones that are broadcast in SIB12 (step 14f).
Following the reception of the MEASUREMENT REPORT message, SS commands the UE using MEASUREMENT
CONTROL message to release measurement control information stored in "measurement identity" =12 (step 15).
Thereafter, SS verifies that no MEASUREMENT REPORT messages are detected on the uplink DCCH (step 16). After
this requirement is satisfied, SS sends MEASUREMENT CONTROL on the downlink DCCH once more (step 17).
This message is identical to the one sent in step 10 (see specific message content). A MEASUREMENT REPORT
message shall be received from the UE triggered by cell 2 (step 17a).
SS transmits a PHYSICAL CHANNEL RECONFIGURATION message on the downlink DCCH and configures
common physical channel (step 18). The UE shall transit to CELL_FACH state and then respond with a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message (step 19). SS monitors the uplink DCCH once more to
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1424
verify that no MEASUREMENT REPORT messages are detected (step 20). SS modifies the downlink transmission
power of the respect cells according to the settings in columns "T1" in table 8.4.1.7-1. System information block type
11 and System Information Block type 12 for cell 2 shall be different from the default settings according to what is
defined in the specific message content part of this section (step 21). The UE shall initiate a cell re-selection procedure.
This is verified in the SS when a CELL UPDATE message is received on the uplink CCCH with the "cell update cause"
IE set to "cell reselection" (step 22). SS transmits a CELL UPDATE CONFIRM message, which includes "New C-
RNTI", on the DCCH (step 23). Then the UE shall reply with UTRAN MOBILITY INFORMATION CONFIRM
message (step 23a). Next, SS sends a RADIO BEARER RECONFIGURATION message on the downlink DCCH,
assigning dedicated physical channels in both uplink and downlink directions (step 24). The UE shall respond with a
RADIO BEARER RECONFIGURATION COMPLETE message and then return to CELL_DCH state (step 25). SS
modifies the downlink transmission power of all cells according to the settings in columns "T2" in table 8.4.1.7-1. UE
shall then send MEASUREMENT REPORT messages reporting cell 3's CPICH RSCP according to the content in
System Information Block type 12 messages broadcasted in cell 2 (step 21).SS transmits a MEASUREMENT
CONTROL message (step 27) whereby the measurement identity is set to the same value as that in the SIB type 12
messages (step 21). UE shall send MEASUREMENT REPORT message (step 28) reporting cell 3's CPICH RSCP
according to the MEASUREMENT CONTROL message (step 27).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1425
Expected Sequence
UE SS
1 System Information Block type 11 and 12 UE is initially in PS-
DCCH+DTCH_FACH (state 6-
11) in cell 1. System
12 messages are changed
with respect to the default
contents according to the
descriptions in "Specific
Message Contents" clause.
1a SYSTEM INFORMATION CHANGE
INDICATION

2 RADIO BEARER RECONFIGURATION SS configures dedicated
physical channels.
COMPLETE
UE shall move to CELL_DCH
state.
4 MEASUREMENT REPORT Reports cell 2's CPICH RSCP
measurement value, with
measurement identity IE set
to 10.
5 MEASUREMENT CONTROL Cell 3 is added to the list of
monitored set of the UE.
6 MEASUREMENT REPORT Cell 3 shall trigger the event
1e configured in the
measurement identity 11.
6a MEASUREMENT REPORT Cell 3 shall also trigger the
event 1e configured in the
measurement identity 10. The
order of steps 6 and 6a could
be reversed.
7 PHYSICAL CHANNEL
RECONFIGURATION
SS configures PRACH and S-
CCPCH physical channels.
8 PHYSICAL CHANNEL
state.
9 SS waits and checks that no
MEASUREMENT REPORT
messages are sent by UE.
9a RADIO BEARER RECONFIGURATION SS configures dedicated
physical channels.
9b RADIO BEARER RECONFIGURATION
COMPLETE
state.
9c MEASUREMENT REPORT UE shall report cell 2's CPICH
RSCP measurement value,
with measurement identity IE
set to 10.
9d Void
9e Void
10 MEASUREMENT CONTROL SS instructs the UE to setup
intra-frequency measurement
and reporting for cell 2.
Measurement validity" IE is set
to CELL_DCH state.
11
12 Void
13 Void
14 MEASUREMENT REPORT UE reports cell 2's measured
results for CPICH RSCP, with
measurement identity IE set
to 12.
14a PHYSICAL CHANNEL
RECONFIGURATION
14b PHYSICAL CHANNEL
state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1426
UE SS
14c SS waits and check that no
MEASUREMENT REPORT
messages are sent by the UE.
14d RADIO BEARER RECONFIGURATION SS configures dedicated
physical channels.
14e RADIO BEARER RECONFIGURATION
COMPLETE
state.
14f MEASUREMENT REPORT UE shall have retrieved and
resumed the measurement set
up through the
MEASUREMENT CONTROL
of step 10.The measurement
identity IE shall be set to 12.
15 MEASUREMENT CONTROL Terminate all the intra-
frequency measurement and
reporting activities related to
"measurement identity" =12.
16 SS waits and verifies that UE
stop transmitting
MEASUREMENT REPORT
messages.
17 MEASUREMENT CONTROL This message is the same as
in step 10.
17a MEASUREMENT REPORT UE shall transmit a
MEASUREMENT REPORT
set to 12.
18 PHYSICAL CHANNEL
RECONFIGURATION
Allocates common physical
channels.
19 PHYSICAL CHANNEL
state.
20 SS checks that no
MEASUREMENT REPORT
21 System Information Block type 11
SS reconfigures the downlink
for cells 1 to 3 according to
column "T1" in table 8.4.1.7.
SS sends SIB11 and SIB12
with specific values to Cell2.
22 CELL UPDATE UE shall re-selects to cell 2
and then perform a cell update
procedure.
23 CELL UPDATE CONFIRM UE shall stay in CELL_FACH
state.
CONFIRM

24 RADIO BEARER RECONFIGURATION Dedicated physical channels
are assigned to the UE in this
message.
COMPLETE
UE shall return to CELL_DCH
state.UE shall not send
Measurement Report
message with measurement
identity =12.
25a SS reconfigures the downlink
transmission power settings of
all cells according to column
T2 in table 8.4.1.7-1.
26 MEASUREMENT REPORT UE begins to report cell 3's
measured results for CPICH
RSCP, with measurement
identity IE set to 1.
27 MEASUREMENT CONTROL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1427
UE SS
28 MEASUREMENT REPORT UE shall transmit a
MEASUREMENT REPORT
set to 1.
MIB Value Tag 3

System Information Block type 11 for cell 1 (Step 1)
- Cell selection and reselection quality measure CPICH Ec/No
- Cell info
- CHOICE mode FDD
(FDD)" in clause 6.1.4 of TS34.108
reporting
Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1428
- Cell info
- CHOICE mode FDD
- Cell selection and Re-selection info Not Present
- Filter Coefficient Not present
- CHOICE mode FDD
reporting
Not present
- Maximum number of reported cells on RACH No report
indicator
FALSE
- CHOICE mode FDD
indicator
FALSE
- Cell identity reporting indicator TRUE
- CHOICE mode FDD
- Reporting range constant Not present
- Cells forbidden to affect reporting range Not present
- W Not present
- Hysteresis 0 dB
- Reporting deactivation threshold Not present
- Replacement activation threshold Not present
- Time to trigger 0
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1429
- Reporting Interval Not Present
- CHOICE reported cells Report cells within monitored set cells on used
frequency

SYSTEM INFORMATION CHANGE INDICATION (Step 1a)
- MIB Value Tag 3
- BCCH modification time Not Present

RADIO BEARER RECONFIGURATION (Step 2, Step 9a, Step 14d and Step 24)
Use the same message type found in Annex A, with condition set to A4.
MEASUREMENT REPORT (Steps 4 and 9c)
Measured Results
list"
Event Results
- CHOICE event result Check to see if it's set to 'Intra-frequency measurement
event results'
- Intra-frequency event identity Check to see if this IE is set to '1e'
- Primary scrambling code Check to see if it's the same code for cell 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1430
- Cell info
- CHOICE mode FDD
indicator
FALSE
indicator
FALSE
- CHOICE report criteria Intra-frequency measurement criteria
- Reporting Range Not Present
- CHOICE Mode FDD
- Primary Scrambling Code Set to the same scrambling code for cell 3
- W Not Present
- Hysteresis 0 dB
- Time to Trigger 0
frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1431

Measured Results
list"
Check to see if this IE is absent
Event Results
event results'

Measured Results
list"
Event Results
event results

PHYSICAL CHANNEL RECONFIGURATION (Steps 7, 14a and 18)
Use the same message sub-type found in clause 9 of TS 34.108, which is entitled "Packet to CELL_FACH from
CELL_DCH in PS".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1432
MEASUREMENT CONTROL (Steps 10 and 17)
- CHOICE intra- frequency cell removal Remove no intra-frequency cells
- Cell info
- CHOICE Mode FDD
indicator
FALSE
indicator
FALSE
- UE state CELL_DCH
- W Not Present
- Hysteresis 0 dB
- Threshold Used Frequency -80 dBm
- Time to Trigger 0
- CHOICE reported cell Report cells within monitored set cells on used
frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1433

MEASUREMENT REPORT (Steps 14, 14f and 17a)
Measured Results
list"
Measured Results on RACH
Event Results
event results

Measurement Command Release
CHOICE Measurement type Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1434
- Cell info
- CHOICE mode FDD
(FDD)" in clause 6.1.4
- Cell info
- CHOICE mode FDD
- Cell info
- CHOICE mode FDD
- Filter coefficient Not Present
- CHOICE mode FDD
reporting
Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1435

- Intra-frequency cell info list Not Present
- Filter coefficient Not Present
- CHOICE mode FDD
reporting
Not present
indicator
FALSE
- CHOICE mode FDD
- CPICH Ec/N0 reporting indicator FALSE
indicator
TRUE
- CHOICE mode FDD
- CPICH Ec/N0 reporting indicator FALSE
- Reporting quantities for detected set cells Not Present
- Measurement reporting mode
- Intra-frequency measurement reporting criteria
- W 0
- Hysteresis 0.0
on used frequency
- UE internal measurement system information Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1436
U-RNTI
Protocol error indicator Check to see if it is absent or set to 'FALSE'

Use the default message content of the same message type in Annex A, with the following exceptions.
New C-RNTI '1010 1010 1010 1010'

UTRAN MOBILITY INFORMATION CONFIRM (Step 23a)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1437
Measured Results
- CHOICE measurement Check to see if set to "Intra-frequency
measured results list"
- Cell synchronisation information Check to see if this IE is present
- Cell synchronisation information Check to see if this IE is present
Event Results
- CHOICE event result Check to see if it's set to 'Intra-frequency
- Intra-frequency event identity Check to see if this IE is set to '1a'
- CHOICE mode FDD

- New intra-frequency info list Not present
indicator
FALSE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1438
indicator
FALSE
- CHOICE Mode FDD
- W Not Present
- Hysteresis 0 dB
- Time to Trigger 0
frequency
Measured Results
list"
- CHOICE mode FDD
Event Results
event results'

After step 3 the UE shall report cell 2's CPICH RSCP value by transmitting MEASUREMENT REPORT messages.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1439
After step 5 the UE shall transmit two MEASUREMENT REPORT messages which contain measured results of cell 3's
CPICH RSCP value only, one for measurement identity 10 and one for measurement identity 11.
After step 9 and step 11 the UE shall not transmit MEASUREMENT REPORT messages, which pertain to intra-
frequency type measurement reporting.
After step 9b, the UE shall transmit a MEASUREMENT REPORT according to what is broadcast in SIB 11 and 12 of
cell 1, and MEASUREMENT REPORT message pertaining to the MEASUREMENT CONTROL message that it had
received in step 5.
After steps 13 and 14e, the UE shall resume the measurement and reporting activities as specified in MEASUREMENT
CONTROL message received in step 10. The UE shall transmit MEASUREMENT REPORT messages, containing
measured results of cell 2's CPICH RSCP value.
After step 15 the UE shall stop measurement activities pertaining to periodic reporting of cell 2's CPICH RSCP, no
MEASUREMENT REPORT messages shall be detectable by the SS on the uplink DCCH.
After step 17, the UE shall transmit a MEASUREMENT REPORT message to the SS as specified in the
MEASUREMENT CONTROL message received in step 17.
After step 21 the UE shall re-select to cell 2 and initiate a cell update procedure. SS shall receive a CELL UPDATE
message on the uplink CCCH of cell 2, with the "cell update cause" IE stated as "cell re-selection".
AM RLC.
After step 25, UE shall not send MEASUREMENT REPORT message with measurement identity =12.
After step 25a the UE shall report cell 3's CPICH RSCP value by transmitting MEASUREMENT REPORT messages.
After step 27, UE shall send MEASUREMENT REPORT message with measurement identity =1.
transition from CELL_FACH to CELL_DCH state (TDD)

Information Block type 12 (or System Information Block type 11);
(or System Information Block type 11):
3> send the MEASUREMENT REPORT message when reporting criteria in IE "Reporting information for state
CELL_DCH" are fulfilled.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1440
Upon cell reselection while in CELL_FACH/CELL_PCH/URA/PCH state and the cell reselection has occurred after the
measurement control information was stored, the UE shall:
1>delete all measurements of type intra-frequency, inter-frequency, and inter-RAT associated with the variable
1>delete the traffic volume measurements that have not been set up or modified through a MEASUREMENT
CONTROL message.

Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in subclause 8.6
unless otherwise specified below.
The UE shall:


4>for measurement types "inter-frequency measurement" that require measurements on a frequency
other than the actually used frequency, or that require measurements on another RAT:

5>replace the corresponding information stored in variable MEASUREMENT_IDENTITY
associated to the identity indicated by the IE "measurement identity" with the one received in the
MEASUREMENT CONTROL message;
5>resume the measurements according to the new stored measurement control information.
3>otherwise:

2>for all optional IEs that are not present in the MEASUREMENT CONTROL message:
3>leave the currently stored information elements unchanged in the variable MEASUREMENT_IDENTITY
if not stated otherwise for that IE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1441
Reference
3GPP TS 25.331, clause 8.4.1.3, 8.4.1.6a and 8.4.1.7.1
1. To confirm that UE retrieves each set of measurement control information of measurement type "intra-
frequency" stored in the variable MEASUREMENT_IDENTITY;
2. To confirm that UE resumes the measurement reporting if the IE "measurement validity" for a measurement has
been assigned the value "CELL_DCH .
3. To test that UE continues monitoring the list of neighbouring cells assigned in the IE "intra-frequency cell info
list" in System Information Block type 12 (or System Information Block type 11) if no intra-frequency
measurements applicable to CELL_DCH state are stored in the variable MEASUREMENT_IDENTITY
4. To confirm that UE sends the MEASUREMENT REPORT message when reporting criteria in IE "Reporting
information for state CELL_DCH" is fulfilled if the IE "intra-frequency measurement reporting criteria" was
included in System Information Block type 12 (or System Information Block type 11).
Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11).
Test Procedure
execution. Column marked "T0" denotes the initial conditions, while column marked as "T1" will be applied during the
test.
Table 8.4.1.7A-1
T0 T1 T0 T1 T0 T1
UTRA RF Channel
Number
Ch. 1 Ch. 1 Ch. 1
PCCPCH RSCP dBm
-74 -74 -64 -69 -69 -122

The UE is initially in CELL_FACH state in cell 1. SS sends SYSTEM INFORMATION CHANGE INDICATION
message to UE to inform UE of the modification in the system information.
SS send a RADIO BEARER RECONFIGURATION message to UE, and configures dedicated physical channels on
both uplink and downlink directions. The UE shall move to CELL_DCH state and then return RADIO BEARER
RECONFIGURATION COMPLETE message. The UE shall send a MEASUREMENT REPORT message containing
IE "Measured results" to report cell 2's PCCPCH RSCP value and IE "event results" to report triggering of event type
"1g".
After receiving the MEASUREMENT REPORT message, SS transmits a MEASUREMENT CONTROL message with
only cell 3 included in the IE "intra-frequency cell info". After receiving this message, the UE shall transmit another set
of MEASUREMENT REPORT message for measurement 11. SS verifies that only measurement readings for cell 3 's
PCCPCH RSCP are report in IE "cell measured results" in these message. Cell 3 shall also trigger event 1g for the
measurement that the UE had stored from system information.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1442
SS reconfigures the downlink according to values "T1" and sends new System Information Blocks 11 and 12.
SS sends PHYSICAL CHANNEL RECONFIGURATION message. SS configures common physical channels for both
the uplink and the downlink directions. The UE shall transit to CELL_FACH state and then reply with a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE. SS waits and checks the uplink RACH to confirm that no
SS transmits then a RADIO BEARER RECONFIGURATION message to the UE, to move it to CELL_DCH. The UE
shall move to that state, and transmit a RADIO BEARER RECONFIGURATION COMPLETE message to SS. Shortly
after, a MEASUREMENT REPORT message shall be received that has been triggered by cell 2, i.e. the UE shall have
deleted the measurement measurement configured through the MEASUREMENT CONTROL message, and instead
apply the measurement configured in SIB12: a MEASUREMENT REPORT message with measurement identity 10
shall be received while no such message with measurement identity 11 shall be sent by the UE.
SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE to move it to CELL_FACH once
again. The UE shalll move to that state and transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message to SS. SS transmits MEASUREMENT CONTROL message on the downlink DCCH, to configure intra-
frequency measurements with validity CELL_DCH. SS waits, and verifies that no MEASUREMENT REPORT
messages are detected on the uplink DCCH.
SS sends RADIO BEARER RECONFIGURATION message and configures dedicated physical channels. The UE shall
return to CELL_DCH state, transmit a RADIO BEARER RECONFIGURATION COMPLETE message. The UE shall
also send a MEASUREMENT REPORT message to the SS triggered by cell 2.
SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE to move it to CELL_FACH. The
UE shall move to that state and transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to
SS. SS shall wait and check that no MEASUREMENT REPORT messages are detected on the uplink DCCH.
SS transmits a RADIO BEARER RECONFIGURATION message to the UE, to move it to CELL_DCH. The UE shall
move to that state, and transmit a RADIO BEARER RECONFIGURATION COMPLETE message to SS. Shortly after,
a MEASUREMENT REPORT message shall be received that has been triggered by cell 2, i.e the UE shall have
retrieved the measurement configured through the MEASUREMENT CONTROL message of a step before, instead of
the ones that are broadcast in SIB12.
Following the reception of the MEASUREMENT REPORT message, SS commands the UE using MEASUREMENT
CONTROL message to release measurement control information stored in "measurement identity" =12. Thereafter, SS
verifies that no MEASUREMENT REPORT messages are detected on the uplink DCCH. After this requirement is
satisfied, SS sends MEASUREMENT CONTROL on the downlink DCCH once more. This message is identical to the
one sent in a step before. A MEASUREMENT REPORT message shall be received from the UE triggered by cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1443
Expected Sequence
UE SS
1 System Information Block type 11 and 12 UE is initially in PS-
DCCH+DTCH_FACH (state 6-
11) in cell 1. System
12 messages are changed
with respect to the default
contents according to the
descriptions in "Specific
Message Contents".
Measurement identity 10 is
included for event 1g and
cell2.
INDICATION

physical channels.
COMPLETE
state.
5 MEASUREMENT REPORT Reports cell 2's PCCPCH
RSCP measurement value.
Event 1g for cell 2 is triggered.
6 MEASUREMENT CONTROL Cell 3 is added to the list of
monitored set of the UE.
Measurement identity 11 is
included for event 1g and
cell3.
7 MEASUREMENT REPORT Cell 3 shall trigger the event
1g configured in the
8 MEASUREMENT REPORT Cell 2 shall also trigger the
event 1g configured in the
9 System Information Block type 11 and 12 System Simulator reconfigures
the downlink transmission
power settings for cells
according to Table 8.4.1.7A-1
10 PHYSICAL CHANNEL
RECONFIGURATION
11 PHYSICAL CHANNEL
state.
12 SS waits and checks that no
MEASUREMENT REPORT
physical channels.
COMPLETE
state
15 MEASUREMENT REPORT UE shall report cell 2's
PCCPCH RSCP measurement
value
16 PHYSICAL CHANNEL
RECONFIGURATION
CCPCH physical channels
17 PHYSICAL CHANNEL
state
18 MEASUREMENT CONTROL SS instructs the UE to setup
and reporting for cell 2.
Measurement validity" IE is set
to CELL_DCH state.
19 SS waits and verifies that no
MEASUREMENT REPORT
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1444
UE SS
physical channels.
COMPLETE
UE shall return to CELL_DCH
state.
22 MEASUREMENT REPORT UE reports cell 2's measured
results for PCCPCH RSCP.
23 PHYSICAL CHANNEL
RECONFIGURATION
CCPCH physical channels
24 PHYSICAL CHANNEL
state
25 SS waits and check that no
MEASUREMENT REPORT
messages are sent by the UE.
physical channels
COMPLETE
state
28 MEASUREMENT REPORT UE shall have retrieved and
resumed the measurement set
up through the
MEASUREMENT CONTROL
of step 18.
29 MEASUREMENT CONTROL Terminate all the intra-
reporting activitiest related to
"measurement identity" =12.
30 SS waits and verifies that UE
stop transmitting
MEASUREMENT REPORT
messages.
31 MEASUREMENT CONTROL This message is the same as
in step 18
32 MEASUREMENT REPORT UE shall transmit a
MEASUREMENT REPORT
message triggered by cell 2.

MIB Value Tag 3

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1445
- Cell info
- CHOICE mode TDD
- Cell parameters Id Refer to clause titled "Default settings for cell No.1
(TDD)" in clause 6.1.4 of TS34.108
reporting
Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1446
- Cell info
- CHOICE mode TDD
- CHOICE mode TDD
- Intra-frequency reporting quantityfor RACH
reporting
Not present
indicator
FALSE
- CHOICE mode TDD
indicator
FALSE
- CHOICE mode TDD
- Reporting range Not present
- CHOICE Mode TDD
- W Not present
- Hysteresis 0 dB
- Time to trigger 0
frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1447
- MIB Value Tag 3

RADIO BEARER RECONFIGURATION (Step 3, Step 13, Step 20, Step 26)
Use the same message type found in TS34.108, with condition set to A4.
MEASUREMENT REPORT (Steps 5 and 22)
Measured Results
results list"
Event Results
- CHOICE event result Check to see if it's set to 'Intra-frequency
- Intra-frequency event identity Check to see if this IE is set to '1g'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1448
Mode
Event Trigger
- Cell info
- CHOICE mode TDD
- CHOICE mode TDD
indicator
FALSE
indicator
FALSE
- CHOICE Mode TDD
- Primary CCPCH Info Set to the same for cell 3
- W Not Present
- Hysteresis 0 dB
- Time to Trigger 0
frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1449
Measured Results
results list"
Check to see if this IE is absent
- Cell synchronisation information
- Proposed TGSN Reporting required Check to see if this IE is present
- PCCPCH RSCP reporting indicator Check to see if this IE is absent
Additional measured results Check to see if it's set to 'Intra-frequency
Event Results
- CHOICE event result Check to see if this IE is set to '1g'
- Intra-frequency event identity
- Cell measurement event results Check to see if it's the same for cell 3

Measured Results
results list"
Event Results Check to see if it's set to 'Intra-frequency
- Cell measurement event results Check to see if it's the same for cell 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1450
- Cell info
- CHOICE mode TDD
- Cell parameters Id Refer to clause titled "Default settings for cell No.1
(TDD)" in clause 6.1.4 of TS34.108
reporting
Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1451
- Cell info
- CHOICE mode TDD
- CHOICE mode TDD
reporting
Not present
indicator
FALSE
- CHOICE mode TDD
indicator
FALSE
- CHOICE mode TDD
- Reporting range Not present
- Cells forbidden to affect reporting Not present
- CHOICE Mode TDD
- W Not present
- Hysteresis 0 dB
- Time to trigger 0
frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1452

PHYSICAL CHANNEL RECONFIGURATION (Steps 10, 16, 23)
Use the same message sub-type found in TS 34.108, which is entitled "Packet to CELL_FACH from CELL_DCH in
PS".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1453
MEASUREMENT CONTROL (Steps 18 and 31)
Mode
Event Trigger
- CHOICE intra- frequency cell removal Remove no intra-frequency cells
- Cell info
- CHOICE Mode TDD
- CHOICE mode TDD
indicator
FALSE
indicator
FALSE
- UE state CELL_DCH
- Primary CCPCH Info Set to the same for cell 2
- W Not Present
- Hysteresis 0 dB
- Time to Trigger 0
- CHOICE reported cell Report cells within monitored set cells on used
frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1454
MEASUREMENT REPORT (Steps 22, 28 and 32)
Measured Results
results list"
- Cell measured results Check to see if this IE is absent
- Cell synchronisation information
Additional measured results Check to see if it's set to 'Intra-frequency
Event Results

CHOICE Measurement type Not Present

After step 3 the UE shall report cell 2's PCCPCH RSCP value by transmitting MEASUREMENT REPORT messages.
After step 5 the UE shall transmit two MEASUREMENT REPORT messages which contain measured results of cell 3's
PCCPCH RSCP value only, one for measurement identity 10 and one for measurement identity 11.
After step 9 and step 11 the UE shall not transmit MEASUREMENT REPORT messages, which pertain to intra-
frequency type measurement reporting.
After step 9b, the UE shall transmit a MEASUREMENT REPORT according to what is broadcast in SIB 11 and 12 of
cell 1, and MEASUREMENT REPORT message pertaining to the MEASUREMENT CONTROL message that it had
received in step 5.
After steps 13 and 14e, the UE shall resume the measurement and reporting activities as specified in MEASUREMENT
CONTROL message received in step 10. The UE shall transmit MEASUREMENT REPORT messages, containing
measured results of cell 2's PCCPCH RSCP value.
After step 15 the UE shall stop measurement activities pertaining to periodic reporting of cell 2's PCCPCH RSCP, no
MEASUREMENT REPORT messages shall be detectable by the SS on the uplink DCCH.
After step 17, the UE shall transmit a MEASUREMENT REPORT message to the SS as specified in the
MEASUREMENT CONTROL message received in step 17.
After step 21 the UE shall re-select to cell 2 and initiate a cell update procedure. SS shall receive a CELL UPDATE
message on the uplink CCCH of cell 2, with the "cell update cause" IE stated as "cell re-selection".
AM RLC.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1455
After step 25 the UE shall report cell 1 and 3's PCCPCH RSCP value by transmitting MEASUREMENT REPORT
messages.
transition from CELL_FACH to CELL_DCH state (FDD)

type 12 (or System Information Block type 11);
1>retrieve each set of measurement control information of measurement type "inter-frequency" stored in the
variable MEASUREMENT_IDENTITY; and
1>if the IE "measurement validity" for a measurement has been assigned the value "CELL_DCH":
configuration parameters" is included, the UE shall for each transmission gap pattern sequence perform the following
consistency checks:
1>if UE, according to its measurement capabilities, and for the measurement purpose indicated by IE "TGMP",
requires UL compressed mode for measurements on any of the cells to be measured according to UE variable
CELL_INFO_LIST, and CHOICE 'UL/DL mode' indicates 'DL only':
1>if UE, according to its measurement capabilities, and for the measurement purpose indicated by IE "TGMP",
requires DL compressed mode for measurements on any of the cells to be measured according to UE variable
CELL_INFO_LIST, and CHOICE 'UL/DL mode' indicates 'UL only':
1>if UE already has an active transmission gap pattern sequence that, according to IE "TGMP", has the same
measurement purpose, and both patterns will be active after the new configuration has been taken into use:
If variable INVALID_CONFIGURATION has value FALSE after UE has performed the checks above, the UE shall:
1>if pattern sequence corresponding to IE "TGPSI" is already active (according to "TGPS Status Flag"):
2>deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time" received in
this message, when the new configuration received in this message is taken into use.
1>update each pattern sequence to the variable TGPS_IDENTITY according to the IE "TGPSI";
1>update into the variable TGPS_IDENTITY the configuration information defined by IE group" transmission gap
pattern sequence configuration parameters ";
1>after the new configuration has been taken into use:
2>activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" is
set to "activate" at the time indicated by IE "TGCFN"; and
2>begin the inter-frequency corresponding to the pattern sequence measurement purpose of each activated
pattern sequence;
2>if the new configuration is taken into use at the same CFN as indicated by IE "TGCFN":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1456
3>start the concerned pattern sequence immediately at that CFN.
1>monitor if the parallel transmission gap pattern sequences create an illegal overlap, and in case of overlap, take
actions as specified in TS 25.331 subclause 8.2.11.2.
Reference
3GPP TS 25.331 clause 8.4.1.7.2, 8.4.1.3
Information Block type 11 or 12 when it transits from CELL_FACH state to CELL_DCH state.
2. To confirm that the UE resumes inter-frequency measurements and reporting stored for which the measurement
control information has IE "measurement validity" assigned to the value "CELL_DCH", after it re-enters
CELL_DCH state from CELL_FACH state.
3. To confirm that the UE resumes inter-frequency measurement and reporting activities after it has received a
MEASUREMENT CONTROL message specifying that a stored compressed mode pattern sequence be re-
activated.
Initial Condition
System Simulator: 3 cells Cells 1, cell 4 and cell 5 are active.
UE: PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of TS 34.108.
In case the UE supports both PS and CS CN domains, this test shall be run twice, once starting from the initial condition
CS-DCCH+DTCH_DCH, and once starting from the initial condition PS-DCCH+DTCH_DCH.
Test Procedure
Table 8.4.1.8-1 illustrates the downlink power to be applied for the 3 cells in this test.
Table 8.4.1.8-1
UTRA RF
Channel
Number
Ch. 1 Ch. 2 Ch. 2
CPICH Ec dBm/3.84
MHz
-60 -75 -75

Test procedure when the initial condition is that the UE is connected to the PS domain:
The UE is in CELL_DCH state in cell 1 (step 1). SS transmits MEASUREMENT CONTROL message to add cell 5
into the IE "inter-frequency cell info" (step 2). If UE requires compressed mode, SS checks that no MEASUREMENT
REPORT messages are detected on the uplink DCCH after it has transmitted the MEASUREMENT CONTROL
message. (step 3). SS checks that the UE sends a MEASUREMENT REPORT message on the uplink DCCH only if UE
does not require compressed mode.
SS sends a PHYSICAL CHANNEL RECONFIGURATION message on the downlink DCCH to move the UE to
CELL_FACH state (step 4). The UE shall reconfigure itself to receive and transmit using the common physical
channels assigned, and send PHYSICAL CHANNEL RECONFIGURATION COMPLETE on the uplink DCCH (step
5). SS modifies the content of Master Information Block and System Information Block type 12 messages, such that
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1457
cell 4 is added in the list of cells assigned in the IE "inter-frequency cell info" (step 6). SS transmits SYSTEM
INFORMATION CHANGE INDICATION message to UE. Once again, SS verifies that the UE does not transmit
MEASUREMENT REPORT messages in the uplink direction (step 7).
SS sends PHYSICAL CHANNEL RECONFIGURATION message, and configures dedicated physical. If UE requires
compressed mode, in this message, SS commands the UE to start applying compressed mode mechanism for DPCH.
The UE shall move to CELL_DCH state and then reply with PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message (step 9). SS waits for 10 seconds. The UE shall transmit 1 MEASUREMENT REPORT message,
containing the selected frequency quality estimate (in this case CPICH RSCP) of cell 4. The UE shall also report the
triggering of event '2c' in the IE "Event results" of MEASUREMENT REPORT message (step 10).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1458
SS transmits a MEASUREMENT CONTROL message on the downlink DCCH using AM-RLC (step 11). The UE shall
transmit MEASUREMENT REPORT messages at 2 seconds interval (step 12).
If UE requires compressed mode, SS transmits a PHYSICAL CHANNEL RECONFIGURATION message and
deactivates the compressed mode pattern sequence with "TGPSI" IE set to 1 (step 13). The UE shall respond by sending
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and also stop the periodic reporting activities
(step 14).
Following this if UE requires compressed mode, SS sends a MEASUREMENT CONTROL message and re-activates
the compressed mode pattern sequence by using the "DPCH compressed mode status" IE (step 15). SS confirms that the
UE has reconfigured itself to start measurement reporting again. The SS shall receive MEASUREMENT REPORT
messages continuously at 2 seconds interval (step 16). The SS then sends a MEASUREMENT CONTROL ordering the
UE to release the measurement corresponding to identity 14, and to stop compressed mode (step 17). At reception of
that message, the UE shall stop compressed mode and delete the measurement corresponding to that identity (step 18).
The SS then transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE to order the UE to start
compressed mode once again (step 19). The UE answers with a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message, and starts compressed mode (step 20). SS checks then that it does not receive any
MEASUREMENT REPORT message from the UE after that point (step 21).
Test procedure when the initial condition is that the UE is connected to the CS domain:
into the IE "inter-frequency cell info" (step 2). SS checks that the UE sends a MEASUREMENT REPORT messages on
the uplink DCCH only if UE does not require compressed mode (step 3).
If the UE requires compressed mode, SS sends PHYSICAL CHANNEL RECONFIGURATION message (step 8). In
that message, SS commands the UE to start applying compressed mode. The UE shall then reply with PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message (step 9). Following this, a UE requiring compressed mode
shall transmit 1 MEASUREMENT REPORT message, containing the selected frequency quality estimate (in this case
CPICH RSCP) of cell 5. The UE shall also report the triggering of event '2c' in the IE "Event results" of
MEASUREMENT REPORT message (step 10).
If the UE requires compressed mode, SS transmits a PHYSICAL CHANNEL RECONFIGURATION message and
deactivates the compressed mode pattern sequence with "TGPSI" IE set to 1 (step 13). The UE shall respond by sending
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message and also stop the periodic reporting activities
(step 14). Following this if the UE requires compressed mode, SS sends a MEASUREMENT CONTROL message and
re-activates the compressed mode pattern sequence by using the "DPCH compressed mode status" IE (step 15). SS
confirms that the UE has reconfigured itself to start measurement reporting again. The SS shall receive
MEASUREMENT REPORT messages continuously at 2 seconds interval (step 16). The SS then sends a
MEASUREMENT CONTROL ordering the UE to release the measurement corresponding to identity 14, and to stop
compressed mode (step 17). At reception of that message, the UE shall stop compressed mode and delete the
measurement corresponding to that identity (step 18). The SS then transmits a PHYSICAL CHANNEL
RECONFIGURATION message to the UE to order the UE to start compressed mode once again (step 19). The UE
answers with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message, and starts compressed mode
(step 20). SS checks then that it does not receive any MEASUREMENT REPORT message from the UE after that point
(step 21).
Expected Sequence
UE SS
1 (Valid for both the PS and CS
cases) The initial state of UE
is in CELL_DCH state of cell
1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1459
UE SS
2 MEASUREMENT CONTROL (Valid for both the PS and CS
cases) SS specifies inter-
reporting parameters for cell 5,
with "measurement validity" IE
present and "UE state" set to
"CELL_DCH".
3 MEASUREMENT REPORT (Valid for both the PS and CS
cases) If compresed mode is
not required (refer ICS/IXIT),
SS checks that UE transmit
this message, or else SS
checks that no
MEASUREMENT REPORT
uplink DCCH.
4 PHYSICAL CHANNEL
RECONFIGURATION
(Only in the PS case) SS
moves the UE to CELL_FACH
state.
5 PHYSICAL CHANNEL
(Only in the PS case) UE shall
move to CELL_FACH state.
modifies MIB and SIB 12 in
order to include cell 4 into the
list of cells in IE "inter-
frequency cell info".
INDICATION
(Only in the PS case) After SS
transmits this message, SS
confirms that there are no
transmissions of
MEASUREMENT REPORT
message in the uplink
direction.
8 PHYSICAL CHANNEL
RECONFIGURATION
(Valid for both the PS and CS
cases)
For the CS case, this step only
applies only if the UE requires
compressed mode. See
specific message content
below.
9 PHYSICAL CHANNEL
cases)
compressed mode. UE shall
move to CELL_DCH state.
cases)
In the PS case, UE shall
resume inter-frequency
measurement task for cell 4
and report the measured
CPICH RSCP value for cell 4.
In the CS case, a UE requiring
compressed mode shall start
inter-frequency measurement
task for cell 5 and report the
measured CPICH RSCP value
for cell 5.
In the CS case, SS shall check
that a UE not requiring
compressed mode shall not
send any MEASUREMENT
REPORT.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1460
UE SS
cases) SS changes the
reporting criteria for cell 5 to
'periodic reporting'
cases) UE shall begin to
transmit this message at 2
seconds interval. If compresed
mode is not required (refer
ICS/IXIT), the test ends here.
13 PHYSICAL CHANNEL
RECONFIGURATION
cases) SS deactivates the
currently used pattern
sequence for compressed
mode operation.
14 PHYSICAL CHANNEL
cases) UE stays in
CELL_DCH state. SS verifies
that no MEASUREMENT
REPORT messages are
received.
cases) SS activates the
pattern sequence stored by
the UE.
cases) SS checks that
MEASURE-MENT REPORT
messages are received at 2
seconds interval.
cases) SS orders the UE to
release the measurement with
identity 14, and to stop
compressed mode
cases) SS checks that the UE
has stopped compressed
mode.
19 PHYSICAL CHANNEL
RECONFIGURATION
cases) SS orders the UE to
start compressed mode again.
20 PHYSICAL CHANNEL
cases) The UE transmits the
response message and starts
compressed mode
cases) SS checks that the UE
does not send any
MEASUREMENT REPORT

Unless explicitely stated, the messages below shall be used for both the CS case and the PS case.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1461
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
FALSE
- UE State CELL_DCH
-UE autonomous update On with no reporting
- Non autonomous update mode Not Present
- Hysteresis 1.0 dB
- Time to trigger 10 seconds
used frequency
frequency


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1462
Use the same message sub-type found in Annex A titled "(Packet to CELL_FACH from CELL_DCH in PS)".
- Choice mode FDD
- Primary scrambling code Scrambling code for cell 1. Ref. to the Default
setting in TS34.108 clause 6.1 (FDD)
- Downlink DPCH info for each RL Not Present
- SCCPCH Information for FACH Not Present

Value Tag 2

coefficient
2
- Inter-frequency FDD measurement indicator TRUE
-Cell selection and reselection quality measure CPICH Ec/No
- CHOICE inter-frequency cells removal Not Present
- Inter-frequency cell id Set to id of cell 4
- Cell info
- CHOICE Mode FDD
- Cell selection and Re-selection info Not Present use default values

PHYSICAL CHANNEL RECONFIGURATION (Step 8 for the PS case)
If UE do not require compressed mode, use the same message sub-type found in [9] TS 34.108 clause 9, which is
entitled "(Packet to CELL_DCH from CELL_FACH in PS)".
If UE requires compressed mode, use the same message sub-type found in Annex A, which is entitled "(Packet to
CELL_DCH from CELL_FACH in PS)", with the following exceptions in the IE(s) concerned:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1463
- CHOICE mode FDD
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL Mode UL and DL UL only or DL only depending on UE
capability
- Downlink compressed mode method SF/2 (or not sent, depending on the UE capability)
- Uplink compressed mode method SF/2 (or not sent, depending on UE capability)
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1464
Activation time (256+CFN-(CFN MOD 8 +8))MOD 256
CHOICE mode FDD
- CHOICE mode FDD
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)

capability)
capability)
- DeltaSIR1 2.0
- CHOICE mode FDD
- Primary CPICH info Set to scrambling code of cell 1
- CHOICE mode FDD
estimation
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1465
Parameter Set
UE

MEASUREMENT REPORT (Step 3 for both the PS and the CS case, and step 10 for the CS case)
Measured Results
list"
- Frequency info
Event Results
- CHOICE event result Inter-frequency event results
- Inter-frequency event identity Check to see if it's set to '2c'
- Frequency Info
results


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1466
MEASUREMENT REPORT (Step 10 for the PS case)
Measured Results
list"
- Frequency info
Event Results
- Frequency Info
results


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1467
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
FALSE
used frequency
- Reporting interval 2000 milliseconds

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1468
MEASUREMENT REPORT (Step 12, 16)
Measured Results
list"
- Frequency info
- Cell Identity Check to see if is absent
- CFN-SFN observed time difference Check to see if it is absent

Use the same message transmitted in step 8 with the following modifications:
Activation time (256+CFN-(CFN MOD 8 +8))MOD 256
CHOICE mode FDD
>Downlink PDSCH information Not Present
- CHOICE mode FDD
- TGPSI 1
- TGCFN Not Present
Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1469
CHOICE measurement type Not Present
- TGPS reconfiguration CFN (Current CFN+(256 TTI/10msec)) mod 256
- TGPSI 1

CHOICE measurement type Not Present
- TGPS reconfiguration CFN (Current CFN+(256 TTI/10msec)) mod 256
- TGPSI 1
- TGPS Flag Deactivate
- TGCFN Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1470
PHYSICAL CHANNEL RECONFIGURATION (Step 19 for the PS case)
CHOICE mode FDD
- CHOICE mode FDD
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL Mode UL and DL, UL only or DL only (depending on the UE
capability)
- Uplink compressed mode method SF/2 (or not sent, depending on the UE capability)
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1471
CHOICE mode FDD
- CHOICE mode FDD
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
capability)
- Uplink compressed mode method SF/2 (or not sent, depending on the UE capability)
- DeltaSIR1 2.0
- CHOICE mode FDD
- Primary CPICH info Set to scrambling code of cell 1
- CHOICE mode FDD
estimation
- Code number Same as the code currently allocated to the UE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1472

After step 2, if UE requires compressed mode the UE shall not send any MEASUREMENT REPORT messages on the
uplink DCCH of cell 1. If UE do not require compressed mode, the UE shall send a MEASUREMENT REPORT
message on the uplink DCCH of cell 1.
After step 4 and 8, UE shall transmit PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
After step 8, the UE shall start compressed mode using the method specified in the PHYSICAL CHANNEL
RECONFIGURATION message sent in step 8.
After step 9 the UE shall transmit a MEASUREMENT REPORT message, containing the IE "measured results"
reporting cell 5's CPICH RSCP value in CS case and cell 4's CPICH RSCP value in the PS case. The UE shall also
report the triggering of event '2c' by including IE "Event results" in the MEASUREMENT REPORT message.
After step 11 the UE shall send MEASUREMENT REPORT messages, containing cell 5's CPICH RSCP measured
value in IE "Measured results" at 2 seconds interval. The "Event results" IE shall be omitted in these messages.
If UE requires compressed mode, after step 14, the UE shall not transmit any MEASUREMENT REPORT messages.
If UE requires compressed mode, after step 15, the UE shall start compressed mode and resume the transmission of
MEASUREMENT REPORT messages with identical contents as in those received after step 11.
After step 17, the UE shall deactivate compressed mode.
After step 20, the UE shall not transmit any MEASUREMENT REPORT message to SS.
transition from CELL_FACH to CELL_DCH state (TDD)

type 12 (or System Information Block type 11);
1>retrieve each set of measurement control information of measurement type "inter-frequency" stored in the
variable MEASUREMENT_IDENTITY; and
1>if the IE "measurement validity" for a measurement has been assigned the value "CELL_DCH":
Reference
3GPP TS 25.331 clause 8.4.1.7.2, 8.4.1.3
Information Block type 11 or 12 when it transits from CELL_FACH state to CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1473
2. To confirm that the UE resumes inter-frequency measurements and reporting stored for which the measurement
control information has IE "measurement validity" assigned to the value "CELL_DCH", after it re-enters
CELL_DCH state from CELL_FACH state.
Initial Condition
System Simulator: 3 cells Cells 1, cell 4 and cell 5 are active.
UE: PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of TS 34.108.
In case the UE supports both PS and CS CN domains, this test shall be run twice, once starting from the initial condition
CS-DCCH+DTCH_DCH, and once starting from the initial condition PS-DCCH+DTCH_DCH.
Test Procedure
Table 8.4.1.8A-1 illustrates the downlink power to be applied for the 3 cells in this test.
Table 8.4.1.8A-1
UTRA RF
Channel
Number
Ch. 1 Ch. 2 Ch. 2
PCCPCH
RSCP
dBm
-60 -75 -75

Test procedure when the initial condition is that the UE is connected to the PS domain or CS:
into the IE "inter-frequency cell info" (step 2). SS checks that UE transmit this message, or else SS checks that no
MEASUREMENT REPORT messages are detected on the uplink DCCH (step 3).
SS sends a PHYSICAL CHANNEL RECONFIGURATION message on the downlink DCCH to move the UE to
CELL_FACH state (step 4). The UE shall reconfigure itself to receive and transmit using the common physical
channels assigned, and send PHYSICAL CHANNEL RECONFIGURATION COMPLETE on the uplink DCCH (step
5). SS modifies the content of Master Information Block and System Information Block type 12 messages, such that
cell 4 is added in the list of cells assigned in the IE "inter-frequency cell info" (step 6). SS transmits SYSTEM
INFORMATION CHANGE INDICATION message to UE. Once again, SS verifies that the UE does not transmit
MEASUREMENT REPORT messages in the uplink direction (step 7).
SS sends PHYSICAL CHANNEL RECONFIGURATION message, and configures dedicated physical only in the PS
case (step 8). The UE shall move to CELL_DCH state and then reply with PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message (step 9). SS waits for 10 seconds. The UE shall transmit 1
MEASUREMENT REPORT message, containing the selected frequency quality estimate (in this case PCCPCH RSCP)
of cell 4. The UE shall also report the triggering of event '2c' in the IE "Event results" of MEASUREMENT REPORT
message (step 10).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1474
Expected Sequence
UE SS
cases) The initial state of UE
is in CELL_DCH state of cell
1.
cases) SS specifies inter-
reporting parameters for cell 5,
with "measurement validity" IE
present and "UE state" set to
"CELL_DCH".
cases) SS checks that UE
transmit this message, or else
SS checks that no
MEASUREMENT REPORT
uplink DCCH.
4 PHYSICAL CHANNEL
RECONFIGURATION
moves the UE to CELL_FACH
state.
5 PHYSICAL CHANNEL
(Only in the PS case) UE shall
move to CELL_FACH state.
modifies MIB and SIB 12 in
order to include cell 4 into the
list of cells in IE "inter-
frequency cell info".
INDICATION
(Only in the PS case) After SS
transmits this message, SS
confirms that there are no
transmissions of
MEASUREMENT REPORT
message in the uplink
direction.
8 PHYSICAL CHANNEL
RECONFIGURATION
cases)
compressed mode. See
specific message content
below.
9 PHYSICAL CHANNEL
(Valid only in the PS case)
state.
cases)
UE shall resume inter-
frequency measurement task
for cell 4 and report the
value for cell 4.

cases) SS changes the
reporting criteria for cell 5 to
'periodic reporting'
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1475
UE SS
cases) UE shall begin to
transmit this message at 2
seconds interval.

Unless explicitely stated, the messages below shall be used for both the CS case and the PS case.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1476
- Frequency info
- Cell info
- CHOICE Mode TDD
- Primary CCPCH Info Set to same code as used for cell 5
estimate
PCCPCH RSCP
indicator
FALSE
- UE State CELL_DCH
-UE autonomous update On with no reporting
- Non autonomous update mode Not Present
- Hysteresis 1.0 dB
- Time to trigger 10 seconds
used frequency
frequency


Use the same message sub-type found in TS 34.108 clause 9 titled "(Packet to CELL_FACH from CELL_DCH in PS)".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1477
- Choice mode TDD
- Primary CCPCH info For cell 1. Ref. to the Default setting in
TS34.108 clause 6.1 (TDD)
- Downlink DPCH info for each RL Not Present
- SCCPCH Information for FACH Not Present

Value Tag 2

coefficient
2
- Inter-frequency TDD measurement indicator TRUE
- CHOICE inter-frequency cells removal Not Present
- Cell info
- CHOICE Mode TDD
(TDD)" in clause 6.1.4
- Cell selection and Re-selection info Not Present use default values

PHYSICAL CHANNEL RECONFIGURATION (Step 8 only for the PS case)
UE will use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled "(Packet to CELL_DCH from
CELL_FACH in PS)".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1478
Measured Results
list"
- Frequency info
cell 4
- Primary CCPCH Info Check to see if set to the same code for cell 4
Event Results
- Frequency Info
cell 4
results


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1479
- Frequency info
- UARFCN uplink (Nt) UARFCN of the frequency for cell 5
- Cell info
- CHOICE Mode TDD
estimate
PCCPCH RSCP
indicator
FALSE
used frequency
- Reporting interval 2000 milliseconds

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1480
Measured Results
list"
- Frequency info
cell 5
- CFN-SFN observed time difference Check to see if it is absent

After step 2,. UE shall send a MEASUREMENT REPORT message on the uplink DCCH of cell 1.
After step 4 and 8, UE shall transmit PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the
After step 9 the UE shall transmit a MEASUREMENT REPORT message, containing the IE "measured results"
reporting cell 5's PCCPCH RSCP value in CS case and cell 4's PCCPCH RSCP value in the PS case. The UE shall also
report the triggering of event '2c' by including IE "Event results" in the MEASUREMENT REPORT message.
After step 11 the UE shall send MEASUREMENT REPORT messages, containing cell 5's PCCPCH RSCP measured
value in IE "Measured results" at 2 seconds interval. The "Event results" IE shall be omitted in these messages.
8.4.1.9 Measurement Control and Report: Unsupported measurement in the UE

If UTRAN instructs the UE to perform a measurement that is not supported by the UE, the UE shall:
1>retain the measurement configuration that was valid before the MEASUREMENT CONTROL message was
received;
1>set the IE "RRC transaction identifier" in the MEASUREMENT CONTROL FAILURE message to the value of
"RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Accepted
1>clear that entry.
1>set the cause value in IE "failure cause" to "unsupported measurement";
1>submit the MEASUREMENT CONTROL FAILURE message to lower layers for transmission on the DCCH
using AM RLC;
1>continue with any ongoing processes and procedures as if the invalid MEASUREMENT CONTROL message
has not been received;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1481
Reference
3GPP TS 25.331 clause 8.4.1.4
1. To confirm that the UE transmits a MEASUREMENT CONTROL FAILURE message, with the value
"unsupported measurement" in IE "failure cause" when the SS instructs the UE to perform an unsupported
measurement by sending a MEASUREMENT CONTROL message. To confirm that the UE retains its existing
valid measurement configuration, after receiving a MEASUREMENT CONTROL message containing an
unsupported measurement.
Initial Condition
UE: CS-DCCH+DTCH_DCH (State 6-9) or PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of
[Editor's note: It is assumed in this test that the UE under test does not possess any inter-RAT measurement capability.
The mandatory type(s) of measurement capability that shall be implemented by the UE is to be discussed]
Test Procedure
The UE is in the CELL_DCH state. SS sends MEASUREMENT CONTROL message to command the UE to perform
internal measurement and reporting for UE transmitted power. The UE shall transmit MEASUREMENT REPORT
messages on DCCH at 1 second interval. The SS transmits a MEASUREMENT CONTROL message to configure inter-
RAT measurements. The UE hall transmit a MEASUREMENT CONTROL FAILURE message on the uplink DCCH
using AM RLC. SS verifies that the UE continues to transmit MEASURMENT REPORT messages on uplink DCCH.
Expected sequence
UE SS
state.
2 MEASUREMENT CONTROL UE internal measurement and
reporting is requested.
3 MEASUREMENT REPORT Contains estimated reading for
UE transmitted power.
4 MEASUREMENT CONTROL Inter-RAT measurements are
requested in this message
5 MEASUREMENT CONTROL FAILURE The value "unsupported
measurement" is set in IE
"failure cause".
6 MEASUREMENT REPORT SS verifies that UE continue to
send this message on uplink
DCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1482
CHOICE measurement type UE internal measurement
- UE internal measurement quantity
- CHOICE mode FDD
- Measurement quantity UE Transmitted Power
- UE internal reporting quantity
- UE Transmitted Power TRUE
- CHOICE mode FDD
- UE Rx-Tx time difference FALSE
- Reporting interval 1000 msec

MEASUREMENT REPORT (Step 3 and Step 6)
Measurement Identity number Check to see if it's set to '1'
Measured Results
- CHOICE measurement Check to see if it's set to "UE internal measured results"
- CHOICE mode Check to see if it's set to "FDD"
- UE Transmitted Power Check to see if the reported power is compatible with
RF class
- UE Rx-Tx report entries Check to see if it is absent
Event results Check to see if it is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1483
RRC transaction identifier Select an arbitrary an integer between 0 and 3
CHOICE measurement type Inter-RAT measurement
- Inter-RAT cell info list
- CHOICE inter-RAT cell removal Remove no inter-RAT cells
- New inter-RAT cells
- Inter-RAT cell id 1
- CHOICE Radio Access Technology GSM
- BSIC Set to the BSIC code of cell 2
- BSIC ARFCN Set to the ARFCN assigned to cell 2
- Output power Not Present
- Inter-RAT cell id 2
- Inter-RAT measurement quantity
- CHOICE system GSM
- Measurement quantity GSM Carrier RSSI
- BSIC verification required Not required
- Inter-RAT reporting quantity
- UTRAN estimate quantity FALSE
- CHOICE system GSM
- Pathloss FALSE
- Observed time difference to GSM cell Reporting
indicator
FALSE
- GSM Carrier RSSI TRUE
- CHOICE report criteria No reporting

MEASUREMENT CONTROL FAILURE (Step 5)
RRC transaction identifier Check if it is set to the same value of the same IE in the
MEASUREMENT CONTROL message sent in Step 4.
Failure cause Check if it is set to "Unsupported measurement"

After step 2 the UE shall transmit a MEASUREMENT REPORT messages at 1 second interval. In these messages, the
IE "CHOICE measurement" shall be set to "UE internal measured results", and it shall contain the measured UL
transmitted power reading in IE "UE Transmitted Power".
After step 4 the UE shall transmit a MEASUREMENT CONTROL FAILURE message. In this message, the value
"unsupported measurement" shall be specified in IE "failure cause".
After step 5 the UE shall continue to transmit MEASUREMENT REPORT messages on the uplink DCCH, with the
contents of the messages identical to that received by SS after step 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1484
8.4.1.10 Measurement Control and Report: Failure (Invalid Message Reception)

If the MEASUREMENT CONTROL message contains a protocol error causing the variable
"RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Rejected
1>clear that entry.
using AM RLC;
Reference
3GPP TS 25.331 clauses 8.4.1.5 and 9.2
1. To confirm that the UE continues its ongoing processes and procedures after it has received an invalid
MEASUREMENT CONTROL message.
2. To confirm that the UE transmits MEASUREMENT CONTROL FAILURE message, after it has received an
invalid MEASUREMENT CONTROL message.
Initial Condition
Test Procedure
The UE is initially brought to CELL_DCH. SS transmits a MEASUREMENT CONTROL message to the UE,
commanding it to start transmitting report messages for the reporting quantity "UE Transmitted Power". SS waits for
the UE to transmit MEASUREMENT RERORT message on the uplink DCCH. After the MEASUREMENT REPORT
message is received, SS transmits an invalid MEASUREMENT CONTROL message again. The UE shall reply with
MEASURMENT CONTROL FAILURE message as it has detected a protocol error. It shall continue to report its UL
transmission power level using MEASUREMENT REPORT messages.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1485
Expected Sequence
UE SS
1 The UE is CELL_DCH state in
cell 1.
2 MEASUREMENT CONTROL SS transmits this message on
downlink DCCH to instruct UE
to start reporting the quantity
"UE transmitted power".
3 MEASUREMENT REPORT UE shall send this message
periodically at 32 seconds
interval
4 MEASURMENT CONTROL See message content.
5 MEASUREMENT CONTROL FAILURE UE shall continue its current
processes and procedures
after sending this message.
6 MEASUREMENT REPORT UE shall continue to transmit
this message to the SS at 32
seconds interval.

CHOICE report criteria Periodical reporting criteria

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1486
MEASUREMENT REPORT (Step 3 and Step 6)
Measured Results
CHOICE measurement Check to see if set to "UE internal measurement results"
- CHOICE mode Check to see if it's set to "FDD"
- UE Transmitted Power Check to see if the reported power is compatible with
RF class
- UE Rx-Tx report entries Check to see if this IE is absent


Failure cause Check to see if set to "protocol error"
Protocol error information Check to see if set to " Message extension not
comprehended "

After step 4 the UE shall transmit MEASUREMENT CONTROL FAILURE message, stating the IE "failure cause" as
"protocol error" and IE "protocol error information" as "Message extension not comprehended".
After step 5 the UE shall continue to send MEASUREMENT REPORT, with the measurement identity number set to 3
and "measured results" IE containing measured readings of UE Tx power, at 32 seconds interval.
8.4.1.11 Void

8.4.1.12 Void

8.4.1.13 Void

8.4.1.14 Measurement Control and Report: Cell forbidden to affect reporting range
(FDD)

The reporting range affects the reporting events 1A and 1B. The reporting range is defined as a function of all the
Primary CPICHs in the active set. If the parameter W is set to 0, the reporting range is defined relative to the best
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1487
Primary CPICH. However, there could be cases where it is good to forbid a specific Primary CPICH to affect the
reporting range. This mechanism could be effective if the operator knows by experience that the quality of a Primary
CPICH is very unstable in a specific area and therefore should not affect the reporting of the other Primary CPICHs.
The UE shall ignore that a Primary CPICH is forbidden to affect the reporting range if all of the following conditions
are fulfilled:
- the Primary CPICH is included in active set; and
- all cells in active set are defined as Primary CPICHs forbidden to affect the reporting range.
Reference
3GPP TS 25.331 clause 14.1.2.1, 14.1.2.2, clause 14.1.5.4
1. To confirm that the UE reports the triggering of event 1A to the SS, if a primary CPICH currently measured by
the UE enters the reporting range.
2. To confirm that the UE reports the triggering of event 1B to the SS, if a primary CPICH currently measured by
the UE leaves the reporting range.
3. To confirm that the UE use the forbidden cell indicated in the MEASUREMENT CONTROL message to affect
the reporting range.
4. To confirm that the UE ignores that a primary CPICH is forbidden to affect the reporting range when (a) the
primary CPICH concerned is included in active set and (b) all cells in the active set are defined as primary
CPICHs forbidden to affect the reporting range.
Initial Condition
UE: CS-DCCH+DTCH _DCH (State 6-9) or PS-DCCH+DTCH_DCH (State 6-10) in cell 1 as specified in clause 7.4 of
Test Procedure
execution. Column marked "T0" denotes the initial conditions. The exact instants on which these values shall be applied
are described in the texts in this clause.
Table 8.4.1.14-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF
Channel
Number
Ch. 1 Ch. 1 Ch.1
CPICH Ec dBm/3.8
4 MHz
-55 -50 -55 -62 -62 -64 -76 -68 -64

The UE is initially in CELL_DCH state of cell 1.
SS sends a MEASUREMENT CONTROL message with cell 1, cell 2 and cell 3 listed in IE "intra-frequency cell info
list". In this message the IE "CHOICE reporting criteria" is set to "intra-frequency measurement report criteria", with
the IE "intra-frequency event identity" set to "1A". The IE "reporting range" is set to 13 dB in the MEASUREMENT
CONTROL message. The UE shall send a MEASUREMENT REPORT on the uplink DCCH, which contains the IE
"Event results" to report that intra-frequency event 1A is triggered by cell 2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1488
SS executes the active set update procedure, requesting that cell 2 be added to the active set. The UE shall respond with
ACTIVE SET UPDATE COMPLETE message on the uplink DCCH and then include cell 2 into its current active set.
SS sends a MEASUREMENT CONTROL message to command that cell 1 in the active set is forbidden to affect the
reporting range for event 1A. SS reconfigures the downlink transmission power settings according to values in column
"T1" in table 8.4.1.14-1. The UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH to report
the triggering of intra-frequency event 1A. In this message, the IE "Events results" shall indicate that intra-frequency
event 1A is triggered by cell 3. SS executes the active set update procedure, requesting that cell 3 be added to the active
set. The UE shall respond with ACTIVE SET UPDATE COMPLETE message on the uplink DCCH and then include
cell 3 into its current active set. SS sends a MEASUREMENT CONTROL message to command that cell 1 in the active
set is forbidden to affect the reporting range for event 1B. The IE "reporting range" is set to 12 dB in the
MEASUREMENT CONTROL message. SS checks that no measurement report is sent by the UE. SS sends a
MEASUREMENT CONTROL message to command that cell 1 in the active set to be removed from the "forbidden to
affect the reporting range for event 1B" cell list. The UE shall transmit a MEASUREMENT REPORT message on the
uplink DCCH to report the triggering of intra-frequency event 1B. In this message, the IE "Events results" shall indicate
that intra-frequency event 1B is triggered by cell 3. SS reconfigures the downlink transmission power settings according
to values in column "T2" in table 8.4.1.14-1. SS sends a MEASUREMENT CONTROL message to command that cell
1 in the active set is forbidden to affect the reporting range for event 1B. The IE "reporting range" is set to 12 dB in the
MEASUREMENT CONTROL message. SS reconfigures the downlink transmission power settings according to values
in column "T1" in table 8.4.1.14-1. SS checks that no measurement report is sent by the UE. SS sends a
MEASUREMENT CONTROL message to command that all cells in the active set are forbidden to update the reporting
range for event 1B. The UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH to report the
triggering of intra-frequency event 1B. In these messages, the IE "Events results" shall indicate that intra-frequency
event 1B is triggered by cell 3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1489
Expected sequence
UE SS
1 MEASUREMENT CONTROL UE is initially in CELL_DCH state
in cell 1. Cell 1, cell 2 and cell 3
are listed in IE "Intra-frequency
cell info list". The IE "CHOICE
reporting criteria" is set to "Intra-
frequency measurement
reporting criteria" and IE "Intra-
frequency event identity" is set to
"1A" and "1B", with IE "reporting
range" set to 13 dB for both
events.
2 MEASUREMENT REPORT Measurement made on cell 2
shall trigger event 1A
3 ACTIVE SET UPDATE SS requests UE to add cell 2 into
active set.
4 ACTIVE SET UPDATE COMPLETE
5 MEASUREMENT CONTROL SS request UE to monitor cell 3
for event '1A'. SS set cell 1 to be
forbidden to affect reporting
range.
5a SS configures the downlink
power according to column 'T1'
of table 8.4.1.14-1.
shall trigger event 1A
6a ACTIVE SET UPDATE SS requests UE to add cell 3 into
active set.
6b ACTIVE SET UPDATE COMPLETE
7 MEASUREMENT CONTROL SS set cell 1 to be forbidden to
affect reporting range for event
'1B'.
7a Void SS checks that no measurement
report is sent by the UE.
7b MEASUREMENT CONTROL Cell 1 shall not be forbidden to
affect event '1B'.
shall trigger event 1B.
of table 8.4.1.14-1.
9 MEASUREMENT CONTROL SS set cell 1 to be forbidden to
affect reporting range for event
'1B'.
of table 8.4.1.14-1.
10 Void SS checks that no measurement
report is sent by the UE.
11 MEASUREMENT CONTROL SS request UE to monitor cell 3
for event '1B'. SS forbids all cells
in active list to affect the
reporting range. The SS
requests UE to report the CPICH
RSCP value of the active set
cells.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1490
The contents of MEASUREMENT CONTROL message for this test step is identical to the same message found in [9]
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1491
- CHOICE intra-frequency cell removal Remove no intra-frequency
- Cell info
- CHOICE Mode FDD
- Cell info
- CHOICE Mode FDD
- Cell for measurement
- Intra-frequency cell id 1, 2 and 3
indicator
FALSE
indicator
TRUE
- Triggering conditions 1 Not Present
- Triggering conditions 2 monitored set cells
- Reporting range 13.0 dB
- W 0
- Hysteresis 0 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1492
- CHOICE reported cells Report cells within monitored set on used frequency

RRC transaction identifier Check to see if set to 1
Measured Results
list"
Event Results Check to see if set to 'Intra-frequency measurement
event results'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1493
The contents of ACTIVE SET UPDATE message for this test step is identical to the same message found in Clause 9 of
- CHOICE mode FDD
allocated to the UE
parameter sets"
Radio link removal information Not Present

ACTIVE SET UPDATE COMPLETE (Step 4 and 6b)
RRC transaction identifier Check to see if it is set to 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1494
- Triggering conditions 2 monitored set cells
- Cells forbidden to affect reporting range
- CHOICE Mode FDD
- Primary scrambling code Set to the same code as in cell 1
- W 0
- Hysteresis 0 dB

Measured Results
list"
event results'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1495
ACTIVE SET UPDATE (Step 6a)
The contents of ACTIVE SET UPDATE message for this test step is identical to the same message found in Clause 9 of
- CHOICE mode FDD
allocated to the UE
parameter sets"

MEASUREMENT CONTROL (Step 7 and 9)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1496
- Triggering conditions 1 Active set cells
- CHOICE Mode FDD
- W 0
- Hysteresis 0 dB

MEASUREMENT CONTROL (Step 7b)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1497
- W 0
- Hysteresis 0 dB

Measured Results Not Present
event results'
- Intra-frequency event identity Check to see if set to '1b'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1498
The contents of MEASUREMENT CONTROL message for this test step is identical to the same message found in
Clause 9 of TS 34.108 with the following exceptions:
indicator
FALSE
- Reporting quantities for monitored set cells Not present
indicator
TRUE
- CHOICE Mode FDD
- CHOICE Mode FDD
- CHOICE Mode FDD
- W 0
- Hysteresis 0 dB
- CHOICE reported cells Report cells within active set

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1499
Measured Results
results list"
event results'
- Intra-frequency event identity Check to see if set to '1b'

After step 1, the UE shall send a MEASUREMENT REPORT message on the uplink DCCH. The message shall contain
the IE "Event results" to report that cell 2 has triggered intra-frequency event 1A.
After step 3, the UE shall send a ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 5a, the UE shall transmit MEASUREMENT REPORT message on the uplink DCCH. The message shall
contain IE "Event results" to report that cell 3 has triggered intra-frequency event 1A.
After step 6a, the UE shall send a ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 7b, the UE shall transmit MEASUREMENT REPORT message on the uplink DCCH. The message shall
contain IE "Event results" to report that cell 3 has triggered intra-frequency event 1B.
After step 11, the UE shall send a MEASUREMENT REPORT message on the uplink DCCH. The message shall
contain IE "Event results" to report that cell 3 has triggered intra-frequency event 1B.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1500
8.4.1.15 Measurement Control and Report: Configuration Incomplete

If IE "Traffic volume measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", but IE "Traffic volume measurement quantity" or IE "Traffic volume
reporting quantity" is not received, the UE shall:

If IE "Measurement Reporting Mode" is not received by the UE in MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", the UE shall:

If IE "Inter-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", but IE "Inter-frequency measurement quantity", IE "Inter-frequency
reporting quantity" or "CHOICE Report criteria" is not received, the UE shall:
1>set the variable CONFIGURATION_INCOMPLETE to TRUE;

If IE "Intra-frequency measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", but IE "Intra-frequency measurement quantity", IE "Intra-frequency
reporting quantity" or "CHOICE Report criteria" is not received, the UE shall:

If IE "Quality measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", but IE "Quality reporting quantity" is not received, the UE shall:

If IE "UE internal measurement" is received by the UE in a MEASUREMENT CONTROL message, where IE
"measurement command" has the value "setup", but IE "UE internal measurement quantity" or IE "UE internal
reporting quantity" is not received, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1501

If the variable CONFIGURATION_INCOMPLETE is set to TRUE, the UE shall:
1>retain the measurement configuration that was valid before the MEASUREMENT CONTROL message was
received;
"RRC transaction identifier" in the entry for the MEASUREMENT CONTROL message in the table "Accepted
transactions" in the variable TRANSACTIONS and clear that entry;
1>clear the variable CONFIGURATION_INCOMPLETE;
1>set the cause value in IE "failure cause" to "Configuration incomplete";
using AM RLC;
Reference
3GPP TS 25.331 clause 8.4.1.4a, 8.6.7.10, 8.6.7.13, 8.6.7.14, 8.6.7.16, 8.6.7.17, 8.6.7.18
1. To confirm that the UE sends a MEASUREMENT CONTROL FAILURE message, after receiving a
MEASUREMENT CONTROL message with IE "Measurement command" set to "Setup" and the following
contents:
- "CHOICE measurement type" IE is set to "Intra-frequency measurement" and "Intra-frequency measurement
quantity" is omitted; or
- "CHOICE measurement type" IE is set to "Inter-frequency measurement" and "Inter-frequency reporting
quantity" is omitted; or
- "Reporting mode" IE is omitted. or
- "CHOICE measurement type" IE is set to "Quality measurement" and IE "Quality reporting quantity" is
omitted or
- "CHOICE measurement type" IE is set to "UE internal measurement" and IE "UE internal measurement
quantity" is omitted or
- "CHOICE measurement type" IE is set to "UE internal measurement" and IE "UE internal reporting quantity"
is omitted or
- "CHOICE measurement type" IE is set to "Traffic volume measurement" and IE "Traffic volume
measurement quantity" is omitted or
- "CHOICE measurement type" IE is set to "Traffic volume measurement" and IE "Traffic volume reporting
quantity" is omitted
2. To confirm that the UE set the "failure cause" IE to value "incomplete configuration" in the uplink
MEASUREMENT CONTROL FAILURE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1502
Initial Condition
Test Procedure
The UE is initially brought to CELL_DCH. SS then send a MEASUREMENT CONTROL message to UE. The UE
shall perform periodical traffic volume measurement according to this message and then transmit MEASUREMENT
REPORT message back to SS.
SS transmits a MEASUREMENT CONTROL message to the UE, commanding it to start an intra-frequency
measurement and reporting task. However, IE "Intra-frequency measurement quantity" is absent in the message. The
UE shall not establish the intra-frequency measurement. It shall send a MEASUREMENT CONTROL FAILURE
message to report that a "configuration incomplete" error has been detected.
Next, SS sends the MEASUREMENT CONTROL message once more. In this message, SS commands the
establishment of an inter-frequency measurement and reporting task, but IE "Inter-frequency reporting quantity" is
omitted in this message. The UE shall not establish the intra-frequency measurement. It shall send a MEASUREMENT
CONTROL FAILURE message to report that a "configuration incomplete" error has been detected.
Next, SS sends a third MEASUREMENT CONTROL message. In this message, SS commands the establishment of an
intra-frequency measurement and reporting task, but IE "Measurement reporting mode" is omitted in this message. The
UE shall not establish the intra-frequency measurement. It shall send a MEASUREMENT CONTROL FAILURE
message to report that a "configuration incomplete" error has been detected.
Next, SS sends a fourth MEASUREMENT CONTROL message. In this message, SS commands the establishment of a
quality measurement and reporting task, but IE "Quality reporting quantity" is omitted in this message. The UE shall
not establish the quality measurement. It shall send a MEASUREMENT CONTROL FAILURE message to report that
a "configuration incomplete" error has been detected.
Next, SS sends a fifth MEASUREMENT CONTROL message. In this message, SS commands the establishment of UE
internal measurement and reporting task, but IE "UE internal measurement quantity" is omitted in this message. The
UE shall not establish the UE internal measurement. It shall send a MEASUREMENT CONTROL FAILURE message
to report that a "configuration incomplete" error has been detected.
Next, SS sends a sixth MEASUREMENT CONTROL message. In this message, SS commands the establishment of
UE internal measurement and reporting task, but IE "UE internal reporting quantity" is omitted in this message. The
UE shall not establish the UE internal measurement. It shall send a MEASUREMENT CONTROL FAILURE message
to report that a "configuration incomplete" error has been detected.
Next, SS sends a seventh MEASUREMENT CONTROL message. In this message, SS commands the establishment of
a traffic volume measurement and reporting task, but IE "Traffic volume measurement quantity" is omitted in this
message. The UE shall not establish the traffic volume measurement. It shall send a MEASUREMENT CONTROL
FAILURE message to report that a "configuration incomplete" error has been detected.
In the final sequence, SS sends an eight MEASUREMENT CONTROL message. In this message, SS commands the
establishment of a traffic volume measurement and reporting task, but IE "Traffic volume reporting quantity" is omitted
in this message. The UE shall not establish the traffic volume measurement. It shall send a MEASUREMENT
CONTROL FAILURE message to report that a "configuration incomplete" error has been detected. UE shall continue
its traffic volume measurement and send MEASUREMENT REPORT messages back to SS periodically. SS calls for
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1503
Expected Sequence
UE SS
1 The UE is CELL_DCH state in
cell 1.
measurement.
2 MEASUREMENT CONTROL SS commands the start of an
and reporting task. IE "Intra-
frequency measurement
quantity" is absent.
3 MEASUREMENT CONTROL FAILURE UE reports the occurrence of
"incomplete configuration"
and reporting task. IE "Inter-
frequency reporting quantity"
is absent.
and reporting task. IE
"Measurement reporting
mode" is absent.
8 MEASUREMENT CONTROL SS commands the start of a
Quality measurement and
reporting task. IE "Quality
reporting quantity" is absent.
UE internal measurement and
reporting task. IE "UE internal
measurement quantity" is
absent.
UE internal measurement and
reporting task. IE "UE internal
reporting quantity" is absent.
Traffic volume measurement
and reporting task. IE "Traffic
volume measurement
quantity" is absent.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1504
Traffic volume measurement
and reporting task. IE "Traffic
volume reporting quantity" is
absent.

Mode

Check to see if the same message type found in [9] TS 34.108 Clause 9 is received, with the following exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1505
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1506
RRC transaction Identifier Arbitrarily selected between 0 and 3
- Periodical Reporting/Event Trigger Reporting
Mode
- New intra-frequency cell Not Present
- Intra-frequency cell id Set to id of cell 1
- SFN-SFN onserved time difference reporting
indicator
No report
- Cell synchronization information reporting
indicator
FALSE
- CHOICE mode FDD
indicator
No report
indicator
FALSE
- CHOICE mode FDD
- CHOICE reported cell Report cells within active set
- Measurement validity CELL_DCH

MEASUREMENT CONTROL message sent in Step 2
Failure cause Check to see if set to "incomplete configuration"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1507
MEASUREMENT CONTROL (Step 4) (Note 1)
- Periodical Reporting/Event Trigger Reporting
Mode
- New inter-frequency cell
- Frequency info
- CHOICE Mode FDD
- UARFCN uplink (Nu) Set to the same UARFCN as cell 4 in clause 6.1 of TS
34.108
- UARFCN downlink (Nu) Set to the same UARFCN as cell 4 in clause 6.1 of TS
34.108
- Cell info
- CHOICE mode FDD
- CHOICE rerporting criteria Inter-frequency reporting criteria
- Filter coefficients 0
- CHOICE mode FDD
estimate
CPICH RSCP
- Inter-frequency reporting quantity Not Present
- CHOICE reported cell Report cells within monitored set on non-used
frequency


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1508
- New intra-frequency cell Not Present
- Intra-frequency cell id Set to id of cell 1
- CHOICE mode FDD
indicator
No report
indicator
FALSE
- CHOICE mode FDD
indicator
No report
indicator
No report
- CHOICE mode FDD


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1509
- CHOICE measurement type Quality measurement
- Quality reporting quantity Not present
- Reporting criteria Periodical reporting criteria
- Reporting amount Infinity
- Reporting interval 64 sec


- UE internal measurement quantity Not present
- CHOICE mode FDD

RRC transaction identifier

Check if it is set to the same value of the same IE in the

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1510
- CHOICE mode FDD
- UE internal reporting quantity Not present


- CHOICE measurement type Traffic Volume Measurement
- Traffic volume measurement object list Not Present
- Traffic volume measurement quantity Not present
- RB buffer payload True
- RB buffer payload average False
- RB buffer payload variance False
- Report criteria Periodical Reporting Criteria
- Reporting amount 8


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1511
- Traffic volume measurement quantity RLC Buffer Payload
- Traffic volume reporting quantity Not present


NOTE: For the MEASUREMENT CONTROL message in step 4, cell 4 is signalled to be added as a new cell into
the UE's inter-frequency cell list. However, SS does not need to transmit cell 4 in the downlink, as the
UE is not expected to perform measurement and reporting for this cell.
After step 2, 4, 6, 8, 10, 12, 14 and step 16, the UE shall transmit MEASUREMENT CONTROL FAILURE message,
stating the IE "failure cause" as "incomplete configuration". The UE shall not transmit any MEASUREMENT REPORT
messages during the execution of this test case.
8.4.1.16 Measurement Control and Report: Traffic volume measurement for transition
from idle mode to CELL_FACH state
1>store the measurement control information from the IE "Traffic volume measurement system information"
received in System Information Block type 12 (or System Information Block type 11, according to subclause
8.1.1.6.11) in the variable MEASUREMENT_IDENTITY;
1>begin traffic volume measurement reporting according to the assigned information.
The UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1512


Reference
3GPP TS 25.331 clause 8.4.1.9.4, 3GPP TS 25.331 clause 8.4.1.3.
1. To confirm that after a state transition from idle mode to CELL_FACH state, the UE shall begin a traffic volume
type measurement, as specified in System Information Block type 11 or 12 messages on BCCH.
2. To confirm that in CELL_FACH state, the UE shall send a MEASUREMENT REPORT message when
reporting criteria is satisfied. During CELL_FACH state, if the UE receives a MEASUREMENT CONTROL
message, it shall perform the measurement and reporting tasks based on the MEASUREMENT CONTROL
message received.
Initial Condition
Test Procedure
The UE is initially in idle mode. The System Information Block type 11 message is modified with respect to the default
settings to request UE to perform traffic volume measurements. Key measurement parameters are as follows:
measurement quantity ="RLC Buffer Payload", report criteria ="periodic reporting criteria", reporting interval ="6
seconds", reporting amount ='infinity'. The System Information type 12 message is not broadcasted.
execute procedure P6. Then the UE shall begin traffic volume measurements, and shall send MEASUREMENT
REPORT message after completing first measurement. Next SS and UE shall execute procedure P10. Then SS and UE
shall execute procedure P14.
UE shall continue to send MEASUREMENT REPORT messages at 6 seconds interval.
SS sends MEASUREMENT CONTROL message to the UE. This message overwrites measurement information saved
from System information type 11. Key measurement parameters are as follow: measurement type ="traffic volume
measurement", measurement quantity ="RLC Buffer Payload", report criteria ="Event triggered, event 4B: Transport
Channel Traffic Volume becomes smaller than an absolute threshold ", Time to trigger ="5 seconds", pending time
after trigger ="16 seconds", "reporting threshold ='4K'. Since there is no uplink traffic, UE shall send
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1513
MEASUREMENT REPORT message after 5 seconds (time to trigger interval). SS calls for generic procedure C.2 to
check that UE is in CELL_FACH state.
Expected Sequence
UE SS
camped onto cell 1. System
Information Block type 11 to
2a MEASUREMENT REPORT The UE shall send the first
MEASUREMENT REPORT
message, as specified in
SIB11.
7.4.2.4.2) specified in TS 34.108.

7.4.2.6.2) specified in TS 34.108.

5 Void
7 MEASUREMENT REPORT Time difference between any
two consecutive
MEASUREMENT REPORT
messages should be 6
Seconds.
8 MEASUREMENT CONTROL Traffic volume measurement
reporting is requested if
measurement is below
threshold.
to confirm that no
MEASUREMENT REPORT
messages are received in 5
seconds.
10 MEASUREMENT REPORT Measurement report because
event 4b is triggered

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1514
- Cell info
- CHOICE mode FDD
reporting
Not Present
- Reporting information for state CELL_DCH Not Present
- Traffic volume measurement system information
- Traffic volume measurement ID 4
- Traffic volume measurement object list Rach
- Traffic volume measurement reporting criteria Not Present
- Measurement validity All States except CELL_DCH
- Measurement report transfer mode Acknowledged Mode
- Periodical or event trigger Periodical
- Report criteria system Information Periodical reporting criteria

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1515
- Cell info
- CHOICE mode TDD
reporting
Not Present
- Traffic volume measurement object list RACH
- RB buffer payload TRUE
- Measurement validity All States except CELL_DCH

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1516
Measured Results
- CHOICE measurement Check to see if set to "traffic volume measured results
list"
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Measured Results
list"
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1517
- CHOICE reporting criteria Traffic Volume Measurement Reporting Criteria
- Parameters sent for each transport channel
- Uplink transport channel type Rach
- UL Transport Channel ID Not Present
- Parameters required for each Event
- Traffic volume event identity 4B
- Reporting threshold 4K
- Pending time after trigger 16000 ms
- Tx interruption after trigger Not Present
- Periodical or event trigger Event trigger

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20
Event results Traffic Volume Measurement Event Results
- Uplink transport channel type causing the event Rach
- UL Transport Channel identity Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1518
After step 5 the UE shall send MEASUREMENT REPORT messages on the uplink DCCH containg RLC buffer
payload information for all SRBs. After 6 seconds UE shall send second MEASUREMENT REPORT messages
containg RLC buffer payload information for all SRBs and RAB.
After step 8 the UE shall overwrite measurement information received from system information type 11 with
measurement information in MEASUREMENT CONTROL message. The UE shall not send MEASUREMENT
REPORT message within time to trigger interval. After step 9 the UE shall transmit MEASUREMENT REPORT
messages with event identity 4B.

from idle mode to CELL_DCH state
1>begin a traffic volume type measurement, assigned in System Information Block type 11 (or System Information
Block type 12.
The UE shall:


Reference
3GPP TS 25.331 clause 8.4.1.8.4, 3GPP TS 25.331 clause 8.4.1.3.
1. To confirm that after a state transition from idle mode to CELL_DCH state, the UE begin a traffic volume type
measurement, as specified in System Information Block type 11 or 12 messages on BCCH. When entering
CELL_DCH state, the UE shall send a MEASUREMENT REPORT message when reporting criteria is satisfied.
2. During CELL_DCH state, if the UE receives a MEASUREMENT CONTROL message, it shall perform the
measurement and reporting tasks based on the MEASUREMENT CONTROL message received.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1519
Initial Condition
Test Procedure
The UE is initially in idle mode. The System Information Block type 11 message is modified with respect to the default
settings to request UE to perform traffic volume measurements. Key measurement parameters are as follows:
measurement quantity ="Average RLC Buffer Payload", report criteria ="Event triggered, event 4B", reporting
threshold ="8K", report transfer mode ="Unacknowledged mode". The System Information type 12 message is not
broadcasted.
service). Then SS and UE shall execute procedure P11 (for CS service) or P13 (for PS service).
UE shall begin traffic volume measurements after entering in CELL_DCH state. The UE shall send MEASUREMENT
REPORT message because uplink traffic is below threshold.
SS sends MEASUREMENT CONTROL message to the UE. This message reconfigures measurement information
saved from System information type 11. Key measurement parameters are as follow: measurement type ="traffic
volume measurement", measurement quantity ="RLC Buffer Payload", report criteria ="Periodic reporting criteria",
reporting interval ="8 seconds", reporting amount ="8". The UE shall periodically send MEASUREMENT REPORT
message to report RLC Buffer Payload for each RB.
SS sends MEASUREMENT CONTROL message to release traffic volume measurement. UE shall not send
measurement report after receiving this message. SS calls for generic procedure C.3 to check that UE is in CELL_DCH
state.
Expected Sequence
UE SS
camped onto cell 1. System
Information Block type 11 to
34.108.

34.108.

in TS 34.108.

5 Void
6 MEASUREMENT REPORT Event 4B is triggered on DCH
5. This message should come
on RB1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1520
6a MEASUREMENT REPORT Event 4B is triggered on DCH
1. This message should come
on RB1 (only for PS)
7 MEASUREMENT CONTROL Periodic Traffic volume
measurement reporting is
requested.
8 MEASUREMENT REPORT This message should come on
RB2.
9 MEASUREMENT REPORT Time difference between
earlier and this
MEASUREMENT REPORT
message should be 8
Seconds.
10 MEASUREMENT CONTROL Release traffic volume
measurement.
11 Wait for 8 Seconds to confirm
that UE does not send
measurement report message.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1521
- Cell info
- CHOICE mode FDD
reporting
Not Present
- Traffic volume measurement quantity Average RLC Buffer Payload
- Time Interval to take an average 200 msec
- RB buffer payload False
- RB buffer payload average True
- Measurement report transfer mode Unacknowledged Mode
- Periodical or event trigger Event Trigger
- CHOICE reporting criteria Traffic volume measurement reporting criteria
- Uplink transport channel type Not Present
- UL transport channel id Not Present
- Parameters required for each Event
- Pending time after trigger 16000 ms

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1522
- Cell info
- CHOICE mode TDD
reporting
Not Present
- Traffic volume measurement quantity Average RLC Buffer Payload
- Time Interval to take an average 200 msec
- RB buffer payload FALSE
- RB buffer payload average TRUE
- RB buffer payload variance FALSE
- Measurement report transfer mode Unacknowledged Mode
- Periodical or event trigger Event Trigger
- Report criteria system Information Traffic volume reporting criteria
- Event specific parameters
- Event id 4B
- Time to trigger Not Present
- Pending time after trigger Not Present

MEASUREMENT REPORT (Step 6/6a)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1523
Measured Results
list"
- RB identity 1
- RLC buffer payload Check to see if this IE is absent
- RLC buffer payload average Check to see if this IE is present
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20 (for the PS case only)
Event results
- UL transport channel type causing the event DCH
- UL Transport Channel identity 5 (step 6), 1(step 6a)

- Average of RLC Buffer Payload for each RBe False

MEASUREMENT REPORT (Step 8,9)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1524
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4

Measurement reporting mode Not Present

After step 5, due to triggering of event 4B, the UE shall send MEASUREMENT REPORT message using
unacknowledged mode of RLC. After step 7, UE shall send MEASUREMENT REPORT message using
Acknowledged mode of RLC. After 8 seconds UE shall send second MEASUREMENT REPORT message. After step
10, the UE shall not send MEASUREMENT REPORT message.
from CELL_FACH state to CELL_DCH state
- retrieve each set of measurement control information of measurement type "traffic volume" stored;
- if the optional IE "measurement validity" for this measurement has not been included:
- delete the measurement;
- if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been
assigned to value "all states except CELL_DCH":
- stop measurement reporting; and
- save the measurement to be used after the next transition to CELL_FACH state;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1525
- if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been
assigned to value "all states":
- continue measurement reporting;
- if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value
"CELL_DCH":
- resume this measurement and associated reporting;
- if no traffic volume type measurement has been assigned to the UE with a MEASUREMENT CONTROL
message when transiting to CELL_DCH state:
- continue an ongoing traffic volume type measurement, assigned in System Information Block type 11 or
System Information Block type 12.
Reference
3GPP TS 25.331 clause 8.4.1.7.4
1. To confirm that the UE performs traffic volume measurements and the associated reporting when it enters
CELL_DCH state from CELL_FACH state, and that such measurement contexts (and optionally, the reporting
context) valid for CELL_DCH state have been previously stored.
2. To confirm that the UE shall continue to perform traffic volume measurement listed in the System Information
Block type 11 or 12 messages, if no previously assigned measurements are present. The UE shall transmit
MEASUREMENT REPORT messages if reporting conditions stated in System Information Block type 11 or 12
messages have been satisfied.

Initial Condition
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108
Test Procedure
Initially the UE is in CELL_FACH state. MEASUREMENT CONTROL message is sent to the UE to establish traffic
volume measurement context with optional IE "measurement validity" is not present. The UE shall perform
measurement and reporting as assigned in MEASUREMENT CONTROL message. RADIO BEARER
RECONFIGURATION procedure is used to take the UE from CELL_FACH state to CELL_DCH state. While entering
CELL_DCH state from CELL_FACH state, the UE shall delete traffic volume measurement contexts if optional IE
"measurement validity" is not present. So, in CELL_DCH state UE shall not perform traffic volume measurement and
reporting. UE is taken to the CELL_FACH state from CELL_DCH state using RADIO BEARER
RECONFIGURATION procedure. The UE shall not send MEASUREMENT REPORT message as measurement
context is already deleted.
The behavior of the UE when moved from CELL_FACH state to CELL_DCH state and assigned traffic volume
measurement context is present with IE "measurement validity" is set to "All But CELL_DCH state" or "CELL_DCH
state" or "All states" is tested in a similar way.
When the UE is in CELL_FACH state, System Information is modified to assign traffic volume measurement and
reporting to the UE. No previously assigned traffic volume measurement contexts are present in the UE. A SYSTEM
INFORMATION CHANGE INDICATION is sent on FACH to inform the UE about the change. The UE is taken to
CELL_DCH state from CELL_FACH state using RADIO BEARER RECONFIGURATION procedure. In CELL_DCH
state the UE shall continue traffic volume measurement and reporting as assigned in System Information. Traffic
volume measurement and reporting is released by sending MEASUREMENT CONTROL message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1526
Expected Sequence
UE SS
1 MEASUREMENT CONTROL Optional IE "measurement
validity" is not included.
COMPLETE
While entering in CELL_DCH
state from CELL_FACH state
UE shall delete measurement
context setup by
MEASUREMENT CONTROL
message (Step 1).
5 SS waits for 8 seconds to
confirm that there is no
MEASUREMENT REPORT
message from UE.
COMPLETE
UE is in CELL_FACH state.
MEASUREMENT REPORT
message from UE.
9 MEASUREMENT CONTROL IE "measurement validity" is
set to "All But CELL_DCH".
10 MEASUREMENT REPORT .
COMPLETE
UE shall stop traffic volume
measurement setup by
MEASUREMENT CONTROL
message (Step 9).
MEASUREMENT REPORT
message from UE.
14 MEASUREMENT CONTROL UE shall release measurement
context setup by
MEASUREMENT CONTROL
message (Step 9).
COMPLETE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1527
set to "CELL_DCH".
MEASUREMENT REPORT
message from UE.
COMPLETE
UE shall start traffic volume
MEASUREMENT CONTROL
message (Step 17).
context setup by
MEASUREMENT
CONTROL message (Step 17)
COMPLETE
set to "All states".
COMPLETE
UE shall continue traffic
volume measurement setup by
MEASUREMENT CONTROL
message (Step 25).
context setup by
MEASUREMENT
COMPLETE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1528
33 MIB and SIB12 modified Traffic volume measurements
and reporting is assigned to
Ues
33a SYSTEM INFORMATION CHANGE
INDICATION

COMPLETE
volume measurement
assigned in System
Information (Step 33).
context assigned in System


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1529
Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

RADIO BEARER RECONFIGURATION (Step 3, 11, 19, 27, and 35)
Use the same message type found in TS 34.108 clause 9 with condition set to A4.
RADIO BEARER RECONFIGURATION (Step 6, 15, 23, and 31)
The contents of this message are identical to MEASUREMENT CONTROL (Step 1) message with the following
exceptions:
- Measurement validity All But CELL_DCH

The contents of this message are identical to MEASUREMENT REPORT (Step 2) message with the following
exceptions:
Measurement identity

2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1530

exceptions:

exceptions:

3

exceptions:
Measurement Identity

3

exceptions:
- UL transport channel identity RACH
- UL transport channel identity DCH :1
- UL transport channel identity DCH : 5
- Measurement validity All States

MEASUREMENT REPORT (Step 26, and 29)
exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1531

4

exceptions:

4

MIB Value Tag 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1532
- Cell info
- CHOICE mode FDD
reporting
Not Present
- Measurement validity All states

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1533
- Cell info
- CHOICE mode TDD
reporting
Not Present
- RB buffer payload average FALSE
- Measurement validity All states
- Periodical or event trigger Periodocal

SYSTEM INFORMATION CHANGE INDICATION (Step 33a)
- MIB Value Tag 2

exceptions:

5

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1534
exceptions:

5

The UE shall send MEASUREMENT REPORT message in steps 21, 29 and 37. The UE shall not send
MEASUREMENT REPORT message in steps 5, 8, and 13.

from CELL_DCH to CELL_FACH state
Upon transition from CELL_DCH to CELL_FACH or CELL_PCH or URA_PCH state, the UE shall:
1>retrieve each set of measurement control information of measurement type "traffic volume" stored in the variable
MEASUREMENT_IDENTITY; and
2>if the optional IE "measurement validity" for this measurement has not been included:
3>delete the measurement associated with the variable MEASUREMENT_IDENTITY.
2>if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been
assigned to value "CELL_DCH":
3>stop measurement reporting;
3>store the measurement associated with the variable MEASUREMENT_IDENTITY to be used after the
next transition to CELL_DCH state.
2>if the IE "measurement validity" for the measurement has been included, and the IE "UE state" has been
assigned to value "all states":
3>continue measurement reporting.
2>if the IE "measurement validity" has been included and the IE "UE state" has been assigned to value "all
states except CELL_DCH":
3>resume this measurement and associated reporting.
1>if no traffic volume type measurement has been assigned to the UE with a MEASUREMENT CONTROL
message that is valid in CELL_FACH or CELL_PCH or URA_PCH states (stored in the variable
MEASUREMENT_IDENTITY), which has the same identity as the one indicated in the IE "Traffic volume
measurement system information":
2>store the measurement control information from the IE "Traffic volume measurement system information"
received in System Information Block type 12 (or System Information Block type 11, according to subclause
8.1.1.6.11) in the variable MEASUREMENT_IDENTITY;
2>begin traffic volume measurement reporting according to the assigned information.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1535
Reference
3GPP TS 25.331 clauses 8.4.1.6.6.
1. The UE shall performs traffic volume measurements and the associated reporting when it enters CELL_FACH
state from CELL_DCH state, and that such measurement contexts (and optionally, the reporting context) valid
for CELL_FACH state have been previously stored.
2. The UE shall perform traffic volume measurement listed in the System Information Block type 11 or 12
messages, if no previously assigned measurements are present. The UE shall transmit MEASUREMENT
REPORT messages if reporting conditions has been satisfied.
Reference
3GPP TS 25.331 clause 8.4.1.6.6
Initial Condition
Test Procedure
Initially the UE is in CELL_DCH state. MEASUREMENT CONTROL message is sent to the UE to establish traffic
volume measurement context with optional IE "measurement validity" is not present. The UE shall perform
measurement and reporting as assigned in MEASUREMENT CONTROL message. RADIO BEARER
RECONFIGURATION procedure is used to take the UE from CELL_DCH state to CELL_FACH state. While entering
CELL_FACH state from CELL_DCH state, the UE shall delete traffic volume measurement contexts if optional IE
"measurement validity" is not present. So, in CELL_FACH state UE shall not perform traffic volume measurement and
reporting. UE is taken to the CELL_DCH state from CELL_FACH state using RADIO BEARER
RECONFIGURATION procedure. The UE shall not send MEASUREMENT REPORT message as measurement
context is already deleted.
The behavior of the UE when moved from CELL_DCH state to CELL_FACH state and assigned traffic volume
measurement context is present with IE "measurement validity" is set to "All But CELL_DCH state" or "CELL_DCH
state" or "All states" is tested in a similar way.
When the UE is in CELL_DCH state, System Information is modified to assign traffic volume measurement and
reporting to the UE. No previously assigned traffic volume measurement contexts are present in the UE. The UE is
taken to CELL_FACH state from CELL_DCH state using RADIO BEARER RECONFIGURATION procedure. In
CELL_FACH state the UE shall perform traffic volume measurement and reporting as assigned in System Information.
Traffic volume measurement and reporting is released by sending MEASUREMENT CONTROL message.
Expected Sequence
UE SS
1 MEASUREMENT CONTROL Optional IE "measurement
validity" is not included.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1536
COMPLETE
While entering in CELL_FACH
state from CELL_DCH state
UE shall delete measurement
context setup by
MEASUREMENT CONTROL
message (Step 1).
MEASUREMENT REPORT
message from UE.
COMPLETE
UE is in CELL_DCH state.
MEASUREMENT REPORT
message from UE.
set to "All But CELL_DCH".
MEASUREMENT REPORT
message from UE.
COMPLETE
MEASUREMENT CONTROL
message (Step 9).
context setup by
MEASUREMENT CONTROL
message (Step 9).
COMPLETE
set to "CELL_DCH".
COMPLETE
UE shall stop traffic volume
MEASUREMENT CONTROL
message (Step 17).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1537
MEASUREMENT REPORT
context setup by
MEASUREMENT
COMPLETE
set to "All states".
COMPLETE
volume measurement setup by
MEASUREMENT CONTROL
message (Step 25).
context setup by
MEASUREMENT
COMPLETE
33 SIB12 modified Traffic volume measurements
and reporting is assigned to
UEs
COMPLETE
measurement as assigned in
System Information (Step 33).
context assigned in System

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1538

Measured Results
- RB identity 1
- RB identity 2
- RB identity 3
- RB identity 4
- RB identity 20

RADIO BEARER RECONFIGURATION (Step 3, 11, 19, 27, and 34)
RADIO BEARER RECONFIGURATION (Step 6, 15, 23, and 31)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1539
exceptions:
- Measurement validity All But CELL_DCH

exceptions:

2


exceptions:

exceptions:

3

exceptions:

3

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1540
exceptions:
- UL transport channel identity RACH
- UL transport channel identity DCH :1
- UL transport channel identity DCH : 5
- Measurement validity All States

exceptions:

4

exceptions:

4

- Cell_selection_and_reselection_quality CPICH RSCP

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1541
- RB buffer payload average FALSE

exceptions:

5

exceptions:

5

The UE shall send MEASUREMENT REPORT message in steps 13, 29 and 36. The UE shall not send
MEASUREMENT REPORT message in steps 5, 8, and 21.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1542
8.4.1.20 Void
8.4.1.21 Void
8.4.1.22 Measurement Control and Report: Quality measurements
The UE shall:


Reference
3GPP TS 25.331 clause 8.4.1.3
1. To confirm that the UE performs quality measurement as specified in MEASUREMENT CONTROL message
received. In CELL_DCH state, the UE shall send MEASUREMENT REPORT message when the reporting
criteria is fulfilled for any ongoing quality measurement.
Initial Condition
UE: CS-DCCH+DTCH_DCH (State 6-9) or PS-DCCH+DTCH_DCH (State 6-10) as specified in clause 7.4 of
Test Procedure
The UE is in CELL_DCH state. MEASUREMENT CONTROL message is sent to UE to assign quality measurement
and reporting. As assigned in MEASUREMENT CONTROL message, the UE shall periodically send
MEASUREMENT REPORT message reporting BLER of downlink transport channel(s). SS calls for generic procedure
C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1543
Expected Sequence
UE SS
1 MEASUREMENT CONTROL The UE is requested to
perform "Quality
measurements"
3 MEASUREMENT REPORT UE shall send second
MEASUREMENT REPORT
message after 64 seconds.

MEASUREMENT CONTROL (Step 1) (FDD)
- Periodical Reporting / Event Trigger Reporting Mode Periodical reporting
- Quality reporting quantity
- DL transport channel BLER True
- Transport channels for BLER reporting Not present
- CHOICE mode FDD

MEASUREMENT CONTROL (Step 1) (1.28 Mcps TDD)
- Quality reporting quantity
- DL transport channel BLER True
- Transport channels for BLER reporting Not present
- CHOICE mode TDD
- SIR measurement list
- TFCS ID Not present
- CHOICE Reporting criteria Periodical reporting criteria

MEASUREMENT REPORT (Step 2,3) (FDD)
In case of CS speech call,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1544
Measured Results
- CHOICE measurement Quality measurement
- BLER measurement results list
- Transport channel identity 6
- DL transport channel BLER Check to see if this IE is present
- CHOICE mode FDD

MEASUREMENT REPORT (Step 2,3) (1.28 Mcps TDD)
Measured Results
- CHOICE Mode TDD
- SIR measurement results Check to see if this IE is absent

In any cases except CS speech call,
Measured Results
- CHOICE mode FDD

In step 2 and 3, the UE shall send MEASUREMENT REPORT message to report BLER for downlink DCH transport
channel.
8.4.1.23 Measurement Control and Report: Intra-frequency measurement for events
1C and 1D

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1545
1. When event 1C is configured in the UE, the UE shall:
1>if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more primary CPICHs, or if
"Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for one or
more primary CPICHs, for each of these primary CPICHs:
2>if all required reporting quantities are available for that cell; and
2>if the equations have been fulfilled for a time period indicated by "Time to trigger", and if the primary
CPICH that is better is not included in the active set but the other primary CPICH is any of the primary
CPICHs included in the active set, and if that first primary CPICH is not included in the "cells triggered" in
the variable TRIGGERED_1C_EVENT:
3>include that primary CPICH in the "cells recently triggered" in the variable TRIGGERED_1C_EVENT.
1>if the value of "Replacement activation threshold" for this event is less than or equal to the current number of
cells in the active set or equal to 0 and if any primary CPICHs are stored in the "cells recently triggered" in the
variable TRIGGERED_1C_EVENT:
2>if "Reporting interval" for this event is not equal to 0:
3>if the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT is set to FALSE:
4>start a timer for with the value of "Reporting interval" for this event and set the IE "Periodical
reporting running" in the variable TRIGGERED_1C_EVENT to TRUE.
3>set "sent reports" for that primary CPICH in the variable TRIGGERED_1C_EVENT to 1.
2>send a measurement report with IEs set as below:
3>set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1c"; and
3>include in "cell measurement event results" all entries of the "cells recently triggered" in the variable
TRIGGERED_1C_EVENT not in the active set as well as the "primary CPICH info" of all the primary
CPICHs in the active set for which the measured value is worse (i.e. greater for pathloss and less for the
other measurement quantities) than the one of the entry in "cell recently triggered" that has the best
measured value. The "primary CPICH info" for those cells shall be ordered according to their measured
value taking into account their cell individual offset, beginning with the best cell to the worst one;
3>set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not
taking into account the cell individual offset for each cell.
2>.
2. When event 1D is configured in the UE, the UE shall:
1>if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for a primary CPICH that is not stored
in "Best cell" in variable BEST_CELL_1D_EVENT, or if "Measurement quantity" is "CPICH Ec/N0" or
"CPICH RSCP", and Equation 2 below is fulfilled for a primary CPICH that is not stored in "Best cell" in
variable BEST_CELL_1D_EVENT:
NOTE: If the equations are simultaneously fulfilled for more than one primary CPICH, the UE should report only
one event 1D, triggered by the best primary CPICH.
2>if all required reporting quantities are available for that cell, and if the equations have been fulfilled for a time
period indicated by "Time to trigger":
3>set "best cell" in the variable BEST_CELL_1D_EVENT to that primary CPICH that triggered the event;
4>set in "intra-frequency measurement event results"; "Intrafrequency event identity" to "1d" and "cell
measurement event results" to the CPICH info of the primary CPICH that triggered the report, not
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1546
4>set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2,
not taking into account the cell individual offset for each cell.
NOTE: Event 1D can be triggered by an active or by a non-active CPICH.
Reference
3GPP TS 25.331 clause 14.1.2.3, 14.1.2.4.
1.A To confirm that the UE sends MEASUREMENT REPORT message if event 1C is configured, and number of
cells in active set is greater than or equal to 'Replacement activation threshold' parameter, and if monitored or
detected primary CPICH on same frequency becomes better than a primary CPICH in active set.
1.B To confirm that the UE does not send MEASUREMENT REPORT message indicating event 1C if number of
cells in active set is less than 'Replacement activation threshold' parameter, and if monitored or detected
primary CPICH on same frequency becomes better than a primary CPICH in active set.
1.C To confirm that the UE stops periodic reporting of event 1C if the cell that triggered event 1C is added into
active set.
2. To confirm that the UE sends MEASUREMENT REPORT message if event 1D is configured and intra-
frequency measurement indicates change in best cell.
Initial Condition
System Simulator: 3 cells The initial configurations of the 3 cells in the SS shall follow the values indicated in the
column marked "T0" in table 8.4.1.23-1. The table is found in "Test Procedure" clause.
Test Procedure
execution. Column marked "T0" denotes the initial conditions, while columns marked "T1" and "T2" are to be applied
subsequently. The exact instants on which these values shall be applied are described in the text in this clause.
Table 8.4.1.23-1
T0 T1 T2 T0 T1 T2 T0 T1 T2
UTRA RF Channel Number Ch. 1 Ch. 1 Ch. 1
CPICH Ec dBm -60 -60 -66 -70 -70 Switched
off
Switched off -70 -60

The UE is initially in CELL_DCH state of cell 1 and has received the default broadcast information from SIB11/12 in
Cell 1. SS then performs a soft handover procedure by sending ACTIVE SET UPDATE message on the downlink
DCCH. The UE shall reply with an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH, and include
cell 2 to the active set when the activation time specified has elapsed.
SS then ask the UE to perform Intra-frequency measurement and report event 1C and event 1D. In MEASUREMENT
CONTROL message, IE 'Replacement activation threshold' is set to 3 and IE 'Cell individual offset' is set to +6 dBm for
Cell 3. SS configures itself according to the values in columns "T1" shown above. Cell 3 becomes better than Cell 2 that
is in active set of the UE, due to parameter 'Cell Individual offset' for Cell 3. However the UE shall not send
MEASUREMENT REPORT message indicating event 1C because number of cells in active set is less than parameter
'Replacement Activation Threshold'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1547
SS then sends MEASUREMENT CONTROL message to the UE to modify earlier configured intra-frequency
measurement. Now, IE 'Replacement activation threshold' is set to 1. MEASUREMENT CONTROL message contains
only those IEs that are modified and the UE shall continue to use current values of parameters that are not modified.
The UE sends MEASUREMENT REPORT message reporting event 1C, monitored Cell 3 is better than Cell 2 that is in
active set. The UE sends second MEASUREMENT REPORT message reporting event 1C after 4 seconds, equals to
parameter 'Reporting interval'.
SS then performs soft handover procedure by sending ACTIVE SET UPDATE message on the downlink DCCH. In this
message SS commands UE to add Cell 3 and remove Cell 2 from active set. The UE shall reply with an ACTIVE SET
UPDATE COMPLETE message. The UE shall also stop periodic reporting of event 1C because the Cell that triggered
it is added into active set. SS then configures itself according to the values in columns "T2" shown above. This triggers
event 1D and the UE sends MEASUREMENT REPORT message indicating Cell 3 as a best cell. SS calls for generic
Expected Sequence
UE SS
1 ACTIVE SET UPDATE SS command the UE to add
Cell 2 in active set.
3 MEASUREMENT CONTROL Event 1C and 1D are
configured. IE "Replacement
activation threshold" is set to
3.
table 8.4.1.23-1.
5 Check for 10 seconds, the UE
shall not send
MEASUREMENT REPORT
message.
6 MEASUREMENT CONTROL Measurement configured in
step 3 is modified to set
parameter 'replacement
activation threshold' to 1.
7 MEASUREMENT REPORT Event 1C is triggered. The UE
shall report that Cell 3 is better
than Cell 2.
8 MEASUREMENT REPORT The UE shall send second
report after 4 seconds
(Reporting interval)
9 ACTIVE SET UPDATE SS command the UE to
replace Cell 2 in active set by
Cell 3.
shall not send
MEASUREMENT REPORT
message.
table 8.4.1.23-1.
13 MEASUREMENT REPORT The UE shall report event 1D
change of best cell

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1548
exceptions:
- CHOICE mode FDD
allocated to the UE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1549
- Intra-frequency cell removal Remove no intra-frequency cells
- Intra-frequency cell id Id of Cell 3
- Cell info
- Cell individual offset 6 dBm
- CHOICE mode FDD
- Cell selection and Re-selection Info Not Present
- Intra-frequency cell id list Set to id of cell 1, 2 and 3.
indicator
FALSE
indicator
FALSE
- Intra-frequency event identity 1C
- Replacement activation threshold 3
- Hysteresis 4 dB
- Hysteresis 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1550
Measurement command Modify
- Intra-frequency cell info list Not present
- Intra-frequency reporting quantity Not present
- Intra-frequency event identity 1C
- Replacement activation threshold 1
- Hysteresis 4 dB
- Hysteresis 4
Measurement reporting mode Not present

Event results Checked to see if set to "Intra Frequency Event results"
- Event ID Check to see if set to "1C"
- Primary scrambling code Check to see if set to Primary scrambling code of Cell 3
- Primary scrambling code Check to see if set to Primary scrambling code of Cell 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1551
- CHOICE mode FDD
allocated to the UE
- SSDT Cell Identity Not present
- TFCI Combining Indicator TRUE

Event results Check to see if set to "Intra-frequency event results"
- Event ID Check to see if set to "1D"
- Primary scrambling code Check to see if set to "Primary scrambling code of Cell
3"

1.A In steps 7 and 8 the UE shall send MEASUREMENT REPORT message indicating event 1C. IE 'Cell
measurement event results' in MEASUREMENT REPORT message shall contain primary scrambling code of
Cell 3 and Cell 2 in that order.
1.B In step 5 the UE shall not send MEASUREMENT REPORT message.
1.C In step 11 the UE shall not send MEASUREMENT REPORT message.
2. In step 13 the UE shall send MEASUREMENT REPORT message indicating event 1D. IE 'Cell measurement
event results' in MEASUREMENT REPORT message shall contain primary scrambling code of Cell 3.
8.4.1.24 Measurement Control and Report: Inter-frequency measurement for event 2A

When event 2a is configured in the UE within a measurement, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1552
1>when the measurement is initiated or resumed:
2>store the used frequency in the variable BEST_FREQUENCY_2A_EVENT.
1>if equation 1 below has been fulfilled for a time period indicated by "Time to trigger" for a frequency included
for that event and which is not stored in the variable BEST_FREQUENCY_2A_EVENT:
3>set in "inter-frequency measurement event results":
4>"inter-frequency event identity" to "2a"; and
4>"Frequency info" to the frequency that triggered the event; and
4>"Non frequency related measurement event results" to the "Primary CPICH info" of the best primary
CPICH for FDD cells or "Primary CCPCH info" to the "Cells parameters ID" of the best primary
CCPCH for TDD cells on that frequency, not taking into account the cell individual offset;
3>if a non-used frequency triggered the measurement report:
4>set the IE "measured results" and the IE "additional measured results" according to TS 25.331
subclause 8.4.2, not taking into account the cell individual offset;
3>if the used frequency triggered the measurement report:
4>do not include the IE "Inter-frequency measured results list" in the measurement report;
2>update the variable BEST_FREQUENCY_2A_EVENT with that frequency.
Equation 1:
2 /
2a Best NotBest
H Q Q +
The variables in the formula are defined as follows:
Q
Not Best
is the quality estimate of a frequency not stored the "best frequency" in the variable
BEST_FREQUENCY_2A_EVENT.
Q
Best
is the quality estimate of the frequency stored in "best frequency" in the variable
BEST_FREQUENCY_2A_EVENT.
H
2a
is the hysteresis parameter for the event 2a in that measurement.
Reference
3GPP TS 25.331 clause 14.2.1.1
1.A To confirm that the UE sends MEASUREMENT REPORT message if event 2A is configured, and if any of
the non- used frequencies quality estimate becomes better than the currently used frequency quality estimate.
1.B To confirm that the UE does not send MEASUREMENT REPORT message indicating event 2A if hysteresis
condition is not fulfilled.
1.C To confirm that the UE does not send MEASUREMENT REPORT message indicating event 2A if time to
trigger condition is not fulfilled.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1553
Test Procedure
execution. Column marked "T0" denotes the initial conditions, while columns marked "T1", "T2", "T3", "T4" and "T5"
are to be applied subsequently. The exact instants on which these values shall be applied are described in the text in this
clause.
Table 8.4.1.24-1

T0 T1 T2 T3 T4 T5 T0 T1 T2 T3 T4 T5
UTRA RF Channel Number

Ch. 1 Ch. 2
CPICH Ec (FDD) dBm
/3.8
4
Mhz
-65 -65 -65 -70 -65 -70 -75 -60 -75 -55 -75 -55
P-CCPCH RSCP (TDD) dBm -65 -65 -65 -70 -65 -70 -75 -60 -75 -55 -75 -55

The UE is initially in CELL_DCH state of cell 1. SS commands the UE to perform measurements of transmitted power
using MEASUREMENT CONTROL message. This measurement is setup to confirm that while sending
MEASUREMENT REPORT message, the UE sets IE "Additional measured results" correctly. If UE requires
compressed mode, SS performs PHYSICAL CHANNEL RECONFIGURATION procedure to activate compressed
mode. SS then commands the UE to perform Inter-frequency measurements and report event 2A by sending
MEASUREMENT CONTROL message. In MEASUREMENT CONTROL message, IE "Hysteresis" is set to 14.5 dB
and IE "Additional measurement list" is set to id of "UE Internal measurements" configured earlier. SS then configures
itself according to the values in columns "T1" shown above. Even though quality estimate for Cell 4 has become better
than that of Cell 1, event 2A will not be triggered since hysteresis condition is not fulfilled. SS then configures itself
according to the values in columns "T2" shown above.
SS sends MEASUREMENT CONTROL message to modify parameter "Hysteresis" of Inter-frequency measurements
to 1 dB. SS then configures Cell 1 and Cell 4 according to columns "T3" for short duration (less than 5 seconds), and
then configures itself according to columns "T4" shown above. The UE will not send MEASUREMENT REPORT
message because time to trigger condition is not fulfilled. SS then configures itself according to the values in columns
"T5" shown above. The UE sends MEASUREMENT REPORT message reporting even 2A as well as measurement of
transmitted power.
Important Note: Duration between time instant "T3" and "T4" (between steps 9 and 10 of expected sequence) must be
less than 5 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1554
Expected Sequence
UE SS
1 MEASUREMENT CONTROL To setup UE Internal
measurement.
If Compressed Mode not
required (refer ICS/IXIT) go to
step 4
2 PHYSICAL CHANNEL
RECONFIGURATION
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS commands the UE to
perform Inter-frequency
measurements and to report
event 2A.
table 8.4.1.24-1.
shall not send
MEASUREMENT REPORT
message, as hysteresis
table 8.4.1.24-1.
8 MEASUREMENT CONTROL Modify hysteresis parameter
for event 2A.
table 8.4.1.24-1.
table 8.4.1.24-1. This step
should be completed within 5
seconds after completing step
9.
shall not send
MEASUREMENT REPORT
message, as time to trigger
table 8.4.1.24-1.
13 MEASUREMENT REPORT This message should come at
least 5 seconds later after
changing power setting of Cell
4.

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1555
- Measurement quantity UE transmitted power
- CHOICE mode FDD
- Periodical Reporting / Event Trigger Reporting Mode Event Trigger Reporting Mode
DPCH compressed mode status Not present

- Measurement quantity UE transmitted power
- CHOICE mode TDD
-CHOICE TDD option 1.28 Mcps TDD
- TADV info FALSE
DPCH compressed mode status Not present

Use the same message sub-type found in clause 9 of TS 34.108, which is entitled "(Packet to CELL_DCH from
CELL_DCH in PS)FDD", with the following exceptions in the IE(s) concerned:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1556
- DPC mode 0 (Single)
- CHOICE Mode FDD
- DL rate matching restriction information Not present
- TFCI existence TRUE
- Number of bits for Pilot bits (SF=128, 256) Not present
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD Undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL mode UL and DL or DL only or UL only depending on UE
capability
- DeltaSIR1 2.0
- DeltaSIR2 Not present
- DeltaSIRAfter2 Not present
- N identify abort Not present
- T Reconfirm abort Not present
- TX diversity mode None
- SSDT information Not present
- Default DPCH offset value 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1557
- CHOICE measurement type Inter-frequency measurement
- Inter-frequency cell removal Not present
- Inter-frequency cell id Id of Cell 4
- Frequency Information Frequency of Cell 4
- Cell info
- CHOICE mode FDD
- Frequency quality estimate quantity CPICH RSCP
- UTRAN carrier RSSI FALSE
- Non frequency related quantities
indicator
FALSE
- Measurement validity CELL_DCH state
- Inter-frequency SET UPDATE
- UE autonomous update mode On with no reporting
- Inter-frequency event identity 2A
- Used frequency threshold Not present
- Used frequency W 0
- Hysteresis 14.5 dB
- Non-used frequency parameter list
- Non-used frequency threshold -72 dBm
- Non-used frequency W 0
Additional measurement list
- Measurement identity 1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1558
- Inter-frequency measurement objects list
- Frequency Info Frequency of Cell 4
- Cell info
- CHOICE mode TDD
-CHOICE TDD option 1.28 Mcps TDD
- Cell parameters ID Cell parameters ID of Cell 4
- Primary CCPCH TX power Not present
- Timeslot list Not present
estimate
P-CCPCH RSCP
- UTRAN carrier RSSI FALSE
indicator
No report
indicator
FALSE
- CHOICE mode TDD
- Proposed TGSN reporting indicator FALSE
- Primary CCPCH RSCP reporting indicator FALSE
- W used frequency 0
- Hysteresis 14.5 dB
frequency

- Threshold non-used frequency -72 dBm
Additional measurement list
- Measurement identity 1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1559
Measurement command Modify
- New inter-frequency info list Not present
- Inter-frequency measurement quantity Not present
- Inter-frequency reporting quantity Not present
- UE autonomous update mode Not present
- Hysteresis 1 dB
frequency

- Threshold non-used frequency -72 dBm

Measured results Check to see if it is absent
Additional measured results
- Measured results UE internal measured results
- UE transmitted power Check to see if it is present
- UE RX TX report entry list Check to see if it is absent
Event results Inter-frequency measurement event results,
- Frequency info Frequency of Cell 4

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1560
MEASUREMENT REPORT (Step 13) (1.28 Mcps TDD)
Additional measured results
- UE transmitted power Check to see if it is present
- TADV Check to see if it is absent
Event results Check to see if set to Inter-frequency measurement
event results
- Inter-frequency event identity Check to see if set to 2A
- Inter-frequency Cells
- Frequency info Check to see if set to Frequency of Cell 4
- Non frequency related measurement event results
- CHOICE mode Check to see if set to TDD
- Cell parameters ID Check to see if set to Cell parameter ID of Cell 4

1.A In step 13 the UE shall send MEASUREMENT REPORT message indicating event 2A. IE ' Inter-frequency
Cells ' in MEASUREMENT REPORT message shall contain frequency information and primary scrambling
code (for FDD) or Cell parameters ID (for 1.28 Mcps TDD) of Cell 4.
1.B In step 6, the UE shall not send MEASUREMENT REPORT message.
1.C In step 11, the UE shall not send MEASUREMENT REPORT message.
8.4.1.25 Measurement Control and Report: Inter-frequency measurement for events
2B and 2E

When event 2b is configured in the UE within a measurement, the UE shall:
1>if equations 1 and 2 below have been fulfilled for a time period indicated by "Time to Trigger" from the same
instant, respectively for one or several non-used frequencies included for that event and for the used frequency:
2>if any of those non-used frequency is not stored in the variable TRIGGERED_2B_EVENT:
3>store the non-used frequencies that triggered the event and that were not previously stored in the variable
TRIGGERED_2B_EVENT into that variable;
5>"inter-frequency event identity" to "2b"; and
5>for each non-used frequency that triggered the event, beginning with the best frequency:
6>"Frequency info" to that non-used frequency; and
6>"Non frequency related measurement event results" to the "Primary CPICH info" of the best
primary CPICH for FDD cells or "Primary CCPCH info" to the "Cell parameters ID" of the
best primary CCPCH for TDD cells on that non-used frequency, not taking into account the
cell individual offset;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1561
1>if equation 3 below is fulfilled for a non-used frequency stored in the variable TRIGGERED_2B_EVENT:
2>remove that non-used frequency from the variable TRIGGERED_2B_EVENT.
1>if equation 4 below is fulfilled for the used frequency:
2>clear the variable TRIGGERED_2B_EVENT.
Triggering conditions:
Equation 1:
2 /
2 2 b b used Non used Non
H T Q +
Q
Non used
is the quality estimate of a non-used frequency that becomes better than an absolute threshold.
T
Non used 2b
is the absolute threshold that applies for this non-used frequency in that measurement.
H
2b
is the hysteresis parameter for the event 2b.
Equation 2:
2 /
2 2 b b Used Used
H T Q -
Q
Used
is the quality estimate of the used frequency.
T
Used 2b
is the absolute threshold that applies for the used frequency in that measurement.
H
2b
Leaving triggered state condition:
Equation 3:
2 /
2 2 b b used Non used Non
H T Q - <
Q
Non used
is the quality estimate of a non-used frequency that is stored in the variable TRIGGERED_2B_EVENT.
T
Non used 2b
is the absolute threshold that applies for this non-used frequency in that measurement.
H
2b
Equation 4:
2 /
2 2 b b Used Used
H T Q + >
Q
Used
T
Used 2b
is the absolute threshold that applies for the used frequency in that measurement.
H
2b

When event 2e is configured in the UE within a measurement, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1562
1>if equation 1 below has been fulfilled for one or several non-used frequencies included for that event during the
time "Time to trigger":
2>if any of those non-used frequencies is not stored in the variable TRIGGERED_2E_EVENT:
3>store the non-used frequencies that triggered the event and that were not previously stored in the variable
TRIGGERED_2E_EVENT into that variable;
5>"inter-frequency event identity" to "2e"; and
5>for each non-used frequency that triggered the event, beginning with the best frequency:
6>"Frequency info" to that non-used frequency; and
6>"Non frequency related measurement event results" to the "Primary CPICH info" of the best
primary CPICH for FDD cells or "Primary CCPCH info" to the "Cell parameters ID" of the
best primary CCPCH for TDD cells on that non-used frequency, not taking into account the
cell individual offset;
1>if equation 2 below is fulfilled for a non-used frequency stored in the variable TRIGGERED_2E_EVENT:
2>remove that non-used frequency from the variable TRIGGERED_2E_EVENT.
Triggering condition:
Equation 1:
2 /
2 2 e e used Non used Non
H T Q -
Q
Non used
is the quality estimate of a non-used frequency that becomes worse than an absolute threshold.
T
Non used 2e
is the absolute threshold that applies for that non-used frequency for that event.
H
2e
is the hysteresis parameter for the event 2e.
Equation 2:
2 /
2 2 e e used Non used Non
H T Q + >
Q
Non used
is the quality estimate of a non-used frequency stored in the variable TRIGGERED_2E_EVENT.
T
Non used 2e
is the absolute threshold that applies for that non-used frequency for that event.
H
2e
is the hysteresis parameter for the event 2e.
Reference
3GPP TS 25.331 clause 14.2.1.2, 14.2.1.5.
1. To confirm that the UE sends MEASUREMENT REPORT message when event 2E is configured and the
estimated quality of a non-used frequency is below the value of the IE "Threshold non-used frequency". This
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1563
MEASUREMENT REPORT message shall contain at least the best primary CPICH info(for FDD) or primary
CCPCH info(for TDD) on the non-used frequency that triggered the event.
2. To confirm that the UE sends MEASUREMENT REPORT message when event 2B is configured and estimated
quality of the currently used frequency is below the value of the IE "Threshold used frequency" and the
estimated quality of a non-used frequency is above the value of the IE "Threshold non-used frequency". This
CCPCH info(for TDD)on the non-used frequency that triggered the event.
Initial Condition
Test Procedure
execution. Column marked "T0" denotes the initial conditions, while columns marked "T1" and "T2" are to be applied
Table 8.4.1.25-1

T0 T1 T2 T0 T1 T2

Ch. 1 Ch. 2
CPICH Ec FDD dBm
/3.8
4
MHz
-55 -55 -85 -85 -55 -55
P-CCPCH RSCP(TDD) dBm -60 -60 -80 -80 -60 -60

The UE is initially in CELL_DCH state of cell 1. SS commands the UE to perform Inter-frequency measurements and
report event 2B and event 2E by sending MEASUREMENT CONTROL message. Note that the Filter Coefficient IE
has a value of 4 so Layer 3 Filtering applies in this case.
If UE requires compressed mode, SS performs PHYSICAL CHANNEL RECONFIGURATION procedure to activate
compressed mode.
Since quality estimate of non-used frequency is below threshold, the UE sends MEASUREMENT REPORT message
indicating event 2E.
SS then configures itself according to the values in columns "T1" shown above. Now quality estimate of used and non-
used frequency is above threshold and hence neither event 2B nor event 2E will be triggered. SS then configures itself
according to the values in columns "T2" shown above. Quality estimate for used frequency is now below threshold,
while that of non-used frequency is above threshold, the UE sends MEASUREMENT REPORT message to report event
2B.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1564
Expected Sequence
UE SS
event 2B and 2E.
If Compressed Mode not
required (refer ICS/IXIT) go to
step 4
2 PHYSICAL CHANNEL
RECONFIGURATION
3 PHYSICAL CHANNEL

4 MEASUREMENT REPORT The UE shall report event 2E.
Time duration between
activation of compressed
mode and reception of this
message should be at least 5
seconds.
Layer 3 Filtering causes an
additional delay.
table 8.4.1.25-1.
6 Check for 10 seconds the UE
shall not send measurement
report message.
table 8.4.1.25-1.
8 MEASUREMENT REPORT The UE shall report event 2B.
Time duration between
changing power levels
according to columns "T2" and
reception of this message
should be at least 5 seconds.
Layer 3 Filtering causes an
additional delay. For Cell 1 the
CPICH Ec value of -80
dBm(for FDD)or the P-CCPCH
RSCP value of -75 dBm (for
TDD) would have to be
reported at least three times
from the Physical Layer to
cause the Cell 1 frequency
threshold to be reached.
Depending on tolerance
values this number will be
greater (CPICH Ec (for FDD)
or P-CCPCH RSCP(for TDD)
is +/- 3 dBm, SS set
Hysteresis value is +/- 2dB)

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1565
MEASUREMENT CONTROL (Step 1)(FDD)
- Cell info
- CHOICE mode FDD
- Frequency quality estimate quantity CPICH Ec/No
- UTRAN Carrier RSSI FALSE
indicator
FALSE
- Inter-frequency SET UPDATE
- UE autonomous update mode On with no reporting
- Inter-frequency event identity 2E
- Hysteresis 1 dB
- Non used frequency parameter list
- Non used frequency threshold -70 dBm
- Non used frequency W 0
- Inter-frequency event identity 2B
- Used frequency threshold -70 dBm
- Used frequency W 0.4
- Hysteresis 1 dB
- Reporting cell status Within active set or within virtual active set or of the
other RAT
- Maximum number of reporting cells 1
- Non used frequency parameter list
- Non used frequency threshold -70 dBm
- Non used frequency W 0
- Measurement reporting transfer mode Unacknowledged Mode RLC

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1566
MEASUREMENT CONTROL (Step 1)( 1.28 Mcps TDD)
- Cell info
- CHOICE mode TDD
- CHOICE mode TDD
- TSTD Indicator FALSE
- Cell parameters ID Cell parameters ID of Cell 4
- CHOICE mode TDD
estimate
P-CCPCH RSCP
indicator
FALSE
- CHOICE mode TDD
- Hysteresis 1 dB
other RAT
frequency

- Threshold non used frequency -70dBm
- Hysteresis 1 dB
other RAT
- Maximum number of reporting cells 1
frequency

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1567

Use the same message sub-type found in Annex A, which is entitled "(Packet to CELL_DCH from CELL_DCH in
PS)", with the following exceptions in the IE(s) concerned:
- DPC mode 0 (Single)
- CHOICE Mode FDD
- DL rate matching restriction information Not present
- TFCI existence TRUE
- Number of bits for Pilot bits (SF=128, 256) Not present
- TGPSI 1

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD Undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
- CHOICE UL/DL mode UL and DL or DL only or UL only depending on UE
capability
- DeltaSIR1 2.0
- DeltaSIR2 Not present
- DeltaSIRAfter2 Not present
- N identify abort Not present
- T Reconfirm abort Not present
- TX diversity mode None
- SSDT information Not present
- Default DPCH offset value 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1568
Additional measured results Check to see if it is absent

Measured results Check to see if it set to Inter-frequency measured
results list
- Frequency information Check to see if set to Frequency of Cell 4
- Inter-frequency cell measured results
- Cell measurement results
- Cell parameters ID Check to see if set to Cell parameters ID for cell 4
- Proposed TGSN Check to see if it is absent
- Primary CCPCH RSCP Check to see if it is present
- Timeslot List/ISCP Check to see if it is absent
Event results
- CHOICE event results Check to see if set to Inter-frequency measurement
event results
- Inter-frequency event identity Check to see if set to 2E
- Non-frequency related measurement event results
- CHOICE mode option Check to see if set to 1.28 Mcps TDD
- TSTD Indicator Check to see if set to FALSE
- Cell parameters ID Check to see if set to Cell parameters ID of Cell 4
- SCTD Indicator Check to see if set to FALSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1569
Measured results Inter-frequency measured results
- Frequency information Frequency of Cell 4
- Mode Specific Info FDD
- Primary scrambling code Primary scrambling code for cell 4
Measured results Check to see if it set to Inter-frequency measured
results list
- Frequency information Check to see if set to Frequency of Cell 4
- Cell measurement results
- Cell parameters ID Check to see if set to Cell parameters ID for cell 4
- Proposed TGSN Check to see if it is absent
- Primary CCPCH RSCP Check to see if it is present
- Timeslot List/ISCP Check to see if it is absent
Event results
event results
- Inter-frequency event identity Check to see if set to 2B
- Non-frequency related measurement event results
- CHOICE mode option Check to see if set to 1.28 Mcps TDD
- TSTD Indicator Check to see if set to FALSE
- Cell parameters ID Check to see if set to Cell parameters ID of Cell 4
- SCTD Indicator Check to see if set to FALSE

1. In step 4 the UE shall send MEASUREMENT REPORT message indicating event 2E. IE "Cell measurement
event results" in this message shall contain frequency information and primary scrambling code(for FDD) or
Cell parameters ID (for 1.28Mcps TDD) of Cell 4.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1570
2. In step 8 the UE shall send MEASUREMENT REPORT message indicating event 2B. IE "Cell measurement
event results" in this message shall contain frequency information and primary scrambling code (for FDD) or
Cell parameters ID (for 1.28Mcps TDD) of Cell 4.
8.4.1.26 Measurement Control and Report: Measurement for events 2D and 2F

When event 2d is configured in the UE within a measurement, the UE shall:
1>if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger":
2>if the variable TRIGGERED_2D_EVENT is set to FALSE:
3>set the variable TRIGGERED_2D_EVENT to TRUE;
4>set in "inter-frequency event results": "inter-frequency event identity" to "2d" and no IE "Inter-
frequency cells";
subclause 8.4.2.
1>if the variable TRIGGERED_2D_EVENT is set to TRUE and if equation 2 is fulfilled for the used frequency:
2>set the variable TRIGGERED_2D_EVENT to FALSE.
Equation 1:
2 /
2 2 d d Used Used
H T Q -
Q
Used
T
Used 2d
is the absolute threshold that applies for the used frequency and event 2d.
H
2d
is the hysteresis parameter for the event 2d.
Equation 2:
2 /
2 2 d d Used Used
H T Q + >
Q
Used
T
Used 2d
is the absolute threshold that applies for the used frequency and event 2d.
H
2d
is the hysteresis parameter for the event 2d.

When event 2f is configured in the UE within a measurement, the UE shall:
1>if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1571
2>if the variable TRIGGERED_2F_EVENT is set to FALSE:
3>set the variable TRIGGERED_2F_EVENT to TRUE;
4>set in "inter-frequency event results": "inter-frequency event identity" to "2f", and no IE "Inter-
frequency cells";
subclause 8.4.2.
1>if the variable TRIGGERED_2F_EVENT is set to TRUE and if equation 2 is fulfilled for the used frequency:
2>set the variable TRIGGERED_2F_EVENT to FALSE.
Equation 1:
2 /
2 2 f f Used Used
H T Q +
Q
Used
T
Used 2f
is the absolute threshold that applies for the used frequency and event 2f.
H
2f
is the hysteresis parameter for the event 2f.
Equation 2:
2 /
2 2 f f Used Used
H T Q - <
Q
Used
T
Used 2f
is the absolute threshold that applies for the used frequency and event 2f.
H
2f
is the hysteresis parameter for the event 2f.
Reference
3GPP TS 25.331 clause 14.2.1.4, 14.2.1.6
1. To confirm that the UE sends MEASUREMENT REPORT message when event 2F is configured and estimated
quality of the currently used frequency is above the value of the IE "Threshold used frequency". This
CCPCH info(for TDD)on the used frequency.
2. To confirm that the UE sends MEASUREMENT REPORT message when event 2D is configured and estimated
quality of the currently used frequency is below the value of the IE "Threshold used frequency". This
CCPCH info(for TDD)on the used frequency.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1572
Initial Condition
System Simulator: 1 cells The initial configurations of the cell in the SS shall follow the values indicated in the
Test Procedure
Table 8.4.1.26-1 illustrates the downlink power to be applied for the cell at various time instants of the test execution.
Column marked "T0" denotes the initial conditions, while columns marked "T1" is to be applied subsequently. The
exact instant on which these values shall be applied is described in the text in this clause.
Table 8.4.1.26-1

T0 T1

Ch. 1
CPICH Ec (FDD) dBm
/3.8
4
MHz
-55 -85
P-CCPCH RSCP(TDD) dBm -60 -80

The UE is initially in CELL_DCH state of cell 1. SS commands the UE to perform Inter-frequency measurements and
report event 2D and/or event 2F by sending MEASUREMENT CONTROL message. Since quality estimate of used
frequency is above threshold, the UE sends MEASUREMENT REPORT message indicating event 2F. SS then
configures itself according to the values in columns "T1" shown above. Quality estimate for used frequency is now
below threshold, the UE sends MEASUREMENT REPORT message to report it. SS calls for generic procedure C.3 to
Expected Sequence
UE SS
1 Void
2 Void
3 Void
event 2D and 2F.
5 MEASUREMENT REPORT The UE shall report event 2F
table 8.4.1.26-1.
7 MEASUREMENT REPORT The UE shall report event 2D.

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1573
- Inter-frequency cell id Any valid identity other than that of Cell 1
- Frequency Information Any valid frequency other than that of Cell 1
- Cell info
- CHOICE mode FDD
- Primary scrambling code Any value of Primary scrambling code
- Frequency quality estimate quantity CPICH RSCP

indicator
FALSE
- UE autonomous update mode Not present
- Inter-frequency event identity 2D
- Hysteresis 1 dB
- Inter-frequency event identity 2F
- Hysteresis 1 dB

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1574
- Inter-frequency cell id Any valid identity other than that of Cell 1
- Frequency Information Any valid frequency other than that of Cell 1
- Cell info
- CHOICE mode TDD
- CHOICE Mode TDD
- Cell parameters ID Any value of Cell parameters ID
- SCTD indicator FALSE
- CHOICE mode TDD
estimate
P-CCPCH RSCP
indicator
FALSE
- CHOICE mode TDD
- Hysteresis 1 dB
- Reporting cell status Report cells within active set
- Hysteresis 1 dB
- Reporting cell status Report cells within active set

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1575

MEASUREMENT REPORT (Step 5)( 1.28 Mcps TDD)
Event results
event results,
- Inter-frequency event identity Check to see if set to 2F


Event results
event results,
- Inter-frequency event identity Check to see if set to 2D

1. In step 5 the UE shall send MEASUREMENT REPORT message indicating event 2F. IE 'Cell measurement
event results' in this message shall contain frequency information and primary scrambling code (for FDD) or
Cell parameters ID( for 1.28 Mcps TDD) of Cell 1.
2. In step 7 the UE shall send MEASUREMENT REPORT message indicating event 2D. IE 'Cell measurement
event results' in this message shall contain frequency information and primary scrambling code (for FDD) or
Cell parameters ID( for 1.28 Mcps TDD) of Cell 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1576
8.4.1.27 Measurement Control and Report: UE internal measurement for events 6A
and 6B

When event 6A is ordered by UTRAN in a measurement control message, the UE shall send a measurement report
when the UE transmission power (for TDD within a single TS) becomes larger than a predefined threshold. The
corresponding report identifies the threshold that was exceeded.
When event 6B is ordered by UTRAN in a measurement control message, the UE shall send a measurement report
when the UE transmission power (for TDD within a single TS) becomes less than a predefined threshold. The
corresponding report identifies the threshold that the UE Tx power went below.
Reference
3GPP TS 25.331, clauses 14.6.2.1 and 14.6.2.2.
1. To confirm that the UE performs UE internal measurements and reporting for events 6A and 6B, when requested
by the UTRAN to do so in the MEASUREMENT CONTROL message.
Initial Condition
System Simulator: 1 cell, cell 1.
Test Procedure
The UE is in CELL_DCH state in cell 1, after successfully executing procedures P11 or P13 as specified in clause 7.4
of TS 34.108. Next, SS transmits MEASUREMENT CONTROL message to request the UE to perform UE internal
measurements and reporting for events 6A and 6B.
SS increases the UE Tx power above the threshold set to event 6A. After 'time to trigger' UE sends MEASUREMENT
REPORT, triggered by event 6A, to SS.
SS decreases the UE Tx power below the threshold set to event 6B. After 'time to trigger' UE sends MEASUREMENT
REPORT, triggered by event 6B, to SS. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1577
Expected Sequence
UE SS
1 UE is initially in CELL_DCH
state in cell 1.
and reporting of events 6A and
6B.
3 SS sets the UE transmission
power above 18 dBm.
4 MEASUREMENT REPORT UE shall send 6A event
measurement report.
power below 15 dBm.
6 MEASUREMENT REPORT UE shall send 6B event
measurement report.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1578
- Periodic Reporting / Event Trigger Reporting Mode Event Trigger Reporting
- UE internal measurement
- UE internal measurement quantity Present
-CHOICE mode FDD
-UE internal measurement quantity UE Transmitted Power
-Filter coefficient 0
- UE internal reporting quantity Present
- CHOICE mode FDD
- CHOICE report criteria UE internal measurement reporting criteria
- Parameters sent for each UE internal
measurement event
-UE internal event identity 6A
-Time-to-trigger 100 milliseconds
-UE Transmitted Power Tx power threshold 18 dBm
-UE internal event identity 6B
-CHOICE mode TDD
- measurement quantity UE Transmitted Power
- CHOICE mode TDD
- TADV info FALSE
measurement event


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1579
Measured Results
- CHOICE measurement Check to see if set to "UE Internal measured results"
- UE internal measured results
-CHOICE mode Check to see if set to "FDD"
UE Transmitted Power Check to see if present and value is reasonable
Event results
-CHOICE event result Check to see if set to "UE internal measurement event
results"
-UE internal event identity Check to see if set to "6A"
-Primary CPICH info Check to see if this IE is absent

MEASUREMENT REPORT (Step 4)(1.28Mcps TDD)
Measured Results
-CHOICE mode Check to see if set to "TDD"
Event results
results"

Measured Results
Event results
results"
-UE internal event identity Check to see if set to "6B"

MEASUREMENT REPORT (Step 6)(1.28 Mcps TDD)
Measured Results
- UE Transmitted Power Check to see if present and value is reasonable
Event results
results"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1580
After step 3, the UE shall transmit MEASUREMENT REPORT message, containing measured results for UE
transmitted power. The 'Event results' IE contains event identity 6A.
After step 5, the UE shall transmit MEASUREMENT REPORT message, containing measured results for UE
transmitted power. The 'Event results' IE contains event identity 6B.
8.4.1.28 Measurement Control and Report: UE internal measurement for events 6F
(FDD) and 6G

When event 6F is ordered by UTRAN in a MEASUREMENT CONTROL message, the UE shall send a MEASUREMENT
REPORT message when the UE Rx-Tx time difference becomes larger than the threshold defined by the IE "UE Rx-Tx
time difference threshold".
When event 6G is ordered by UTRAN in a MEASUREMENT CONTROL message, the UE shall send a MEASUREMENT
REPORT when the UE Rx-Tx time difference becomes less than the threshold defined by the IE "UE Rx-Tx time
difference threshold".
Reference
3GPP TS 25.331, clauses 14.6.2.6 and 14.6.2.7.
1. To confirm that the UE performs UE internal measurements and reporting for events 6F and 6G, when requested
by the UTRAN to do so in the MEASUREMENT CONTROL message.
Initial Condition
System Simulator: 2 cells The initial configuration of the cells in the SS shall follow the values indicated in table 6.1.2
of TS 34.108.
Test Procedure
Table 6.1.2 of TS 34.108 specifies the radio conditions to be applied for the cells in this test.
of TS 34.108.
SS then performs an active set update procedure by sending ACTIVE SET UPDATE REQUEST message on the
downlink DCCH. Cell 2 is to be added to the active set, according to the content of this downlink message. The UE
shall reply with an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH, and include cell 2 to the active
set when the activation time specified has elapsed.SS sets the initial timing of cell 2 to be the timing of cell 1 - 5 chips.
Next, SS transmits MEASUREMENT CONTROL message to request the UE to perform UE internal measurements
and reporting for events 6F and 6G.
SS adjusts the Tx timing of cell 2 above the threshold set to event 6F. After 'time to trigger' UE sends
MEASUREMENT REPORT, triggered by event 6F, to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1581
SS adjusts the Tx timing of cell 2 below the threshold set to event 6G. After 'time to trigger' UE sends
MEASUREMENT REPORT, triggered by event 6G, to SS. SS calls for generic procedure C.3 to check that UE is in
CELL_DCH state.
Expected Sequence
UE SS
state in cell 1.
2 ACTIVE SET UPDATE SS asks UE to add cell 2 into
the active set.
and reporting of events 6F and
6G.
5 SS switches the Tx timing of
Cell 2, with respect to Cell 1 to
a delay of 19 chips.
6 MEASUREMENT REPORT UE shall send 6F event
measurement report.
7 SS switches the Tx timing of
Cell 2 with respect to Cell 1 to
a delay of 19 chips.
8 MEASUREMENT REPORT UE shall send 6G event
measurement report.

The contents of ACTIVE SET UPDATE message for this test step is identical to the same message found in Annex A
- CHOICE mode FDD
allocated to the UE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1582
ACTIVE SET UPDATE COMPLETE (Step 3)
RRC transaction identifier Check to see if it is set to 0

-UE Internal measurement quantity Present
- CHOICE mode FDD
- Measurement quantity UE Rx-Tx time difference
- Flter coefficient 0
- UE Transmitted Power FALSE
- CHOICE mode FDD
- UE Rx-Tx time difference TRUE
measurement event
-UE internal event identity 6F
-UE Rx-Tx time difference threshold 1037
-UE internal event identity 6G
-UE Rx-Tx time difference threshold 1011

Measured Results
UE Rx-Tx report entries
-Primary scrambling code Check to see if set to codes assigned for cell 1 & cell 2.
-UE Rx-Tx time difference type 1 Check to see if present and value is reasonable
Event results
results"
-UE internal event identity Check to see if set to "6F"
-Primary CPICH info
-Primary scrambling code Check to see if set to code assigned for cell 2.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1583
Measured Results
UE Rx-Tx report entries
-Primary scrambling code Check to see if set to codes assigned for cell 1 & cell 2.
-UE Rx-Tx time difference type 1 Check to see if present and value is reasonable
Event results
results"
-UE internal event identity Check to see if set to "6G"
-Primary CPICH info
-Primary scrambling code Check to see if set to code assigned for cell 2

After step 5, the UE shall transmit MEASUREMENT REPORT message, containing measured results for UE Rx-Tx
time difference. The 'Event results' IE contains event identity 6F.
After step 7, the UE shall transmit MEASUREMENT REPORT message, containing measured results for UE Rx-Tx
time difference. The 'Event results' IE contains event identity 6G.
8.4.1.28A Measurement Control and Report: UE internal measurement for event 6F
(1.28 Mcps TDD)
When event 6F is ordered by UTRAN in a MEASUREMENT CONTROL message, the UE shall send a
MEASUREMENT REPORT message when the absolute value of the difference between the measured T
ADV
and the
T
ADV
stored in the variable TRIGGERED_6F_EVENT becomes larger than the threshold defined by the IE " T
ADV

Threshold ".
Reference
3GPP TS 25.331, clauses 14.6.2.6a
1. To confirm that the UE performs UE internal measurements and reporting for event 6F, when requested by the
UTRAN to do so in the MEASUREMENT CONTROL message.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1584
Test Procedure
SS transmits MEASUREMENT CONTROL message to request the UE to perform UE internal measurements and
reporting for event 6F.
SS adjusts the Tx timing of cell 1 until the time difference indicated by T
ADV
becomes above the threshold set to event
6F. After time to trigger UE sends MEASUREMENT REPORT, triggered by event 6F, to SS.
Expected Sequence
UE SS
state in cell 1.
and reporting of event 6F.
3 SS adjusts the Tx timing of cell
1 until the time difference
indicated by TADV becomes
above a certain threshold.
4 MEASUREMENT REPORT UE shall send 6F event
measurement report.

-UE Internal measurement quantity
- CHOICE mode TDD
- Measurement quantity TADV
- Flter coefficient 0
- UE Transmitted Power FALSE
- CHOICE mode TDD
- TADV info TRUE
measurement event

-UE internal event identity 6F
-Time-to-trigger 0
- TADV threshold 60

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1585
Measured Results
- CHOICE TDD option Check to see if set to 1.28 Mcps TDD
- TADV Check to see if present and value is reasonable
Event results
results"
-UE internal event identity Check to see if set to "6F"

After step 3, the UE shall transmit MEASUREMENT REPORT message, containing measured results for T
ADV
. The
'Event results' IE contains event identity 6F.
8.4.1.29 Measurement Control and Report: Event based Traffic Volume measurement
in CELL_FACH state.

The UE shall:



For traffic volume measurements in the UE only one quantity is compared with the thresholds. This quantity is
Transport Channel Traffic Volume (which equals the sum of Buffer Occupancies of RBs multiplexed onto a transport
channel) in number of bytes. Every TTI, UE measures the Transport Channel Traffic Volume for each transport channel
and compares it with the configured thresholds. If the monitored Transport Channel Traffic Volume exceeds an
absolute threshold, i.e. if TCTF>Reporting threshold, this is an event (event 4a) that could trigger a report. The
corresponding report specifies at least which measurement ID the event that triggered the report belongs to.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1586
variable MEASUREMENT_IDENTITY are met for any ongoing traffic volume measurement or UE positioning
measurement that is being performed in the UE;
Reference
3GPP TS 25.331, clause 14.4.2.1, 3GPP TS 25.331, clause 8.4.1.3, 8.4.2.2.
1. To verify that in CELL_FACH state when event 4a triggered at TVM set up UE sends Measurement Report with
correct measurement identity and indication of UL transport channel type, radio bearer identities and
corresponding RLC buffer payloads in number of bytes.
2 To verify that in CELL_FACH state when event 4a triggerreds after TVM set up UE sends Measurement Report
with correct measurement identity and indication of UL transport channel type, radio bearer identities and
corresponding RLC buffer payloads in number of bytes.
3. To confirm that the UE sends MEASUREMENT REPORT message, with measurement report in IE
"Measurement results on RACH" as specified in System Information Block type 12.
Initial Condition
UE: Idle state (State 3 or State 7) as specified in clause 7.4 of TS 34.108.
System Information Block type 11 or 12 does not include Traffic Volume measurement system information.
Test Procedure
The UE is brought to the CELL_FACH state after a successful incoming call attempt. The SS follows the procedure in
TS 34.108 clause 7.1.3 (Mobile Terminated), to set up a user RAB, but with the default RAB replaced by the one
described in 34.108, clause 6.10.2.4.3.2(for FDD) or clause 6.11.5.4.4.2(for 1.28 Mcps TDD): Interactive/Background
32 kbps PS RAB +SRBs for CCCH +SRB for DCCH +SRB for BCCH for DL and 6.10.2.4.4.1:
Interactive/Background 32 kbps PS RAB +SRB for CCCH +SRB for DCCH (for FDD) or clause 6.11.5.4.5.1: SRB
for CCCH +SRB for DCCH (for 1.28 Mcps TDD) for UL. The radio bearer is placed into UE test loop mode 1
described in 34.109 clause 5.3. The System Information Block type 12 is modified compared to the default settings so
that CPICH RSCP (for FDD) or P-CCPCH RSCP(for TDD) is reported for intra-frequency reporting when transmitting
RACH messages. After this modification, SS configures transport channel traffic volume so as to exceed threshold and
then sends to UE MEASUREMENT CONTROL message, which includes traffic volume measurement control
parameters eg. uplink transport channel type and reporting threshold. Transport channel traffic volume exceeds
threshold and after 'time to trigger' UE sends MEASUREMENT REPORT to SS. SS does not respond and after
'pending time after trigger' UE sends the same MEASUREMENT REPORT again. SS configures UE's transport
channel load decreases to zero and UE sends no MEASUREMENT REPORT message. SS configures transport
channel traffic volume so as to exceed threshold again and after 'time to trigger' UE sends MEASUREMENT
REPORT message to SS. After 'pending time after trigger' UE sends again same MEASUREMENT REPORT message.
SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1587
Expected Sequence
UE SS
1 PAGING TYPE1 The SS transmits the
message, which includes a
allocated identity (P-TMSI).
1b RRC CONNECTION SETUP
1c RRC CONNECTION SETUP COMPLETE
1d SERVICE REQUEST
1e AUTHENTICATION AND CIPHERING
REQUEST

1f AUTHENTICATION AND CIPHERING
RESPONSE

1g SECURITY MODE COMMAND
1h SECURITY MODE COMPLETE
1i ACTIVATE RB TEST MODE TC
1j ACTIVATE RB TEST MODE COMPLETE
1k RADIO BEARER SETUP RRC RAB SETUP
See specific message
1l RADIO BEARER SETUP COMPLETE
1m CLOSED UE TEST LOOP TC
UE Test Loop Mode1
1n CLOSED UE TEST LOOP COMPLETE TC
1o MASTER INFORMATION BLOCK
12 is different from the default
contents)
1p SYSTEM INFORMATION CHANGE
INDICATION
To notify the modification of
SYSTEM INFORMATION
BLOCK TYPE 12, this
message Is transmitted.
1q SS configures transport
channel traffic volume so as
to exceed threshold.
2 MEASUREMENT CONTROL SS provides Traffic Volume
measurement criterias to UE.
3 MEASUREMENT REPORT UE reports that Traffic Volume
measurement event 4A is
triggered.
4 MEASUREMENT REPORT UE repeats message after
1100 ms.
4a SS configures UE's transport
channel load decreases to
zero
4b SS receive no
MEASUREMENT REPORT
message.
4c SS configures transport
to exceed threshold
4d MEASUREMENT REPORT UE reports that Traffic Volume
measurement event 4A is
triggered.
4e MEASUREMENT REPORT UE repeats message after
1100 ms.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1588
Message Type
Paging record
- CN domain identity PS Domain
- CHOICE UE Identity P-TMSI
- p-TMSI Allocated identity during the attach procedure.

RRC CONNECTION REQUEST (Step 1a)
Message type
on step 1

System Information Block type 12 (Step 1o) (FDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1589
- Cell info
- CHOICE mode FDD
indicator
FALSE
indicator
TRUE
- W 0.0
- Hysteresis 1.0 dB
used frequency
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1590

System Information Block type 12 (Step 1o)( 1.28 Mcps TDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1591
- Cell info
- CHOICE mode TDD
- Cell parameters ID Set to same Cell parameters ID as used for cell 1
- CHOICE mode TDD
- Measurement quantity P-CCPCH RSCP
- CHOICE mode TDD
- Reporting quantity P-CCPCH RSCP
indicator
FALSE
- CHOICE mode TDD
indicator
FALSE
- CHOICE mode TDD
- Reporting Range Constant Not Present
- W Not Present
- Hysteresis 1.0 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1592
frequency or within virtual active and/or monitored set

MASTER INFORMATION BLOCK (Step 1o)
MIB Value tag 2

SYSTEM INFORMATION CHANGE INDICATION (Step 1p)
Message Type

MIB Value Tag 2
BCCH Modification time Not Present

CHOICE measurement type Traffic volume measurement
- Traffic volume measurement object
- Measurement quantity RLC buffer payload
- RLC Buffer Payload for each RB TRUE
- Average of RLC Buffer Payload for each RB FALSE
- Variance of RLC Buffer Payload for each RB FALSE
- UE state All states except CELL_DCH
CHOICE report criteria Traffic volume measurement reporting criteria

- Traffic volume event identity 4a
- Reporting threshold 8
- Pending time after trigger 1000
- Tx interruption after trigger 250

MEASUREMENT REPORT (Step 3, step 4, step 4d and step 4e) (FDD)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1593
Measured Results
- CHOICE measurement Check to see if set to "Traffic volume measured results
list"
- RB Identity 1
- RLC Buffers Payload Check to see if this IE is present
- Average of RLC Buffer Payload Check to see if this IE is absent
- Variance of RLC Buffer Payload Check to see if this IE is absent
- RB Identity 2
- RB Identity 3
- RB Identity 4
- RB Identity 20
- RLC Buffers Payload Check to see if the value is above the threshold
- Measurement result for current cell Check to see if set to 'CPICH RSCP'
- CHOICE measurement quantity Checked to see if set to within an acceptable range.
- CPICH RSCP Checked to see if this IE is absent
- Measurement results for monitored cells Check to see if set to 'CPICH RSCP'
Event Results
- Uplink transport channel type causing the event Check to see if set to "RACH"
- UL transport channel identity Check to see that is not set
- Traffic volume event identity Check to see if set to "4a"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1594
MEASUREMENT REPORT (Step 3, step 4, step 4d and step 4e)(1.28 Mcps TDD)
Measured Results
list"
- RB Identity 1
- RB Identity 2
- RB Identity 3
- RB Identity 4
- RB Identity 20
- CHOICE mode Check to see if set toTDD
- Primary CCPCH RSCP Checked to see if this IE is absent
- CHOICE mode Check to see if set toTDD
- Primary CCPCH RSCP Checked to see if this IE is present and the value is
within an acceptable range
Event Results
CHOICE event result Check to see if set toTraffic volume measurement
event results
- Uplink transport channel type causing the event Check to see if set to "RACH"
- UL transport channel identity Check to see that is not set

In step 3 UE sends MEASUREMENT REPORT with correct measurement identity indication. RB identity and RLC
buffers payload has reasonable values. The IE "measured results on RACH", containing the measurement value for cell
1's CPICH RSCP (for FDD) or P-CCPCH RSCP (for TDD) shall be included in this message.
In step 4, 4d and 4e UE repeats message sent in step 3.
After step 3 UE is not allowed to send user data during the 'Tx interruption after trigger' timer is running.
8.4.1.30 Measurement Control and Report: Event based Traffic Volume measurement
in CELL_DCH state.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1595
The UE shall:



For traffic volume measurements in the UE only one quantity is compared with the thresholds. This quantity is
Transport Channel Traffic Volume (which equals the sum of Buffer Occupancies of RBs multiplexed onto a transport
channel) in number of bytes. Every TTI, UE measures the Transport Channel Traffic Volume for each transport channel
and compares it with the configured thresholds.
If the monitored Transport Channel Traffic Volume exceeds an absolute threshold, i.e. if TCTF>Reporting threshold,
this is an event (event 4a) that could trigger a report. The corresponding report specifies at least which measurement ID
the event that triggered the report belongs to.
If the monitored Transport Channel Traffic Volume becomes smaller than an absolute threshold, i.e. if
TCTF<Reporting threshold, this is an event (4b) that could trigger a report. The corresponding report specifies at least
which measurement ID the event that triggered the report belongs to.
Reference
3GPP TS 25.331, clause 14.4.2.2, 3GPP TS 25.331, clause 8.4.1.3.
1. To verify that in CELL_DCH state when event 4a or 4b triggered at setup TVM UE sends RRC: Measurement
Report with correct measurement identity and indication of uplink transport channel type and identity, radio
bearer identities and corresponding RLC buffer payloads in number of bytes.
2. To verify that in CELL_DCH state when event 4a or 4b triggereds after setup TVM UE sends RRC:
Measurement Report with correct measurement identity and indication of uplink transport channel type and
identity, radio bearer identities and corresponding RLC buffer payloads in number of bytes.
Initial Condition
UE: Idle state (State 3 or State 7) as specified in clause 7.4 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1596
System Information Block type 11 nor 12 does not include Traffic Volume measurement system information.
Test Procedure
The UE is brought to the CELL_DCH state after a successful incoming call attempt. The SS follows the procedure in
TS 34.108 clause 7.1.3 (Mobile Terminated), to set up a user RAB, but with the default RAB replaced by the one
described in 34.108, clause 6.10.2.4.1.26: Interactive or background / UL: 64 DL: 64 kbps / PS RAB +UL: 3.4 DL: 3.4
kbps SRBs for DCCH. The radio bearer is placed into UE test loop mode 1 described in TS 34.109 clause 5.3. SS
configures UE's transport channel traffic volume to exceeds threshold. SS sends to UE RRC: MEASUREMENT
CONTROL messages, which includes in addition to measurement identity traffic volume measurement control
parameters eg. uplink transport channel type and identity and reporting threshold for events 4a, and after 'time to trigger'
UE sends RRC: MEASUREMENT REPORT message to SS. SS does not respond and after 'pending time after trigger'
UE sends again same RRC: MEASUREMENT REPORT message. SS configures UE's transport channel load decreases
to zero and sends UE RRC: MEASUREMENT CONTROL messages, which includes in addition to measurement
identity traffic volume measurement control parameters eg. uplink transport channel type and identity and reporting
threshold for event 4b. Event 4b triggers and after 'time to trigger' UE sends RRC: MEASUREMENT REPORT
message to SS. SS does not respond and after 'pending time after trigger' UE sends again same RRC:
MEASUREMENT REPORT message. SS increses transport channel traffic volume to exceeds threshold. Event 4a is
triggered and after 'time to trigger' UE sends RRC: MEASUREMENT REPORT message to SS. SS decreases transport
channel traffic volume to zero. Event 4b is triggered and after 'time to trigger' UE sends RRC: MEASUREMENT
REPORT message to SS. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1597
Expected Sequence
UE SS
1 PAGING TYPE1 The SS transmits the
message, which includes a
allocatd identity (P-TMSI).
1c RRC CONNECTION SETUP COMPLETE
1d SERVICE REQUEST
1e AUTHENTICATION AND CIPHERING
REQUEST

1f AUTHENTICATION AND CIPHERING
RESPONSE

1g SECURITY MODE COMMAND
1h SECURITY MODE COMPLETE
1i ACTIVATE RB TEST MODE TC
1j ACTIVATE RB TEST MODE COMPLETE
1k RADIO BEARER SETUP RRC RAB SETUP
See specific message
1l RADIO BEARER SETUP COMPLETE
1m CLOSED UE TEST LOOP TC
UE Test Loop Mode1
1n CLOSED UE TEST LOOP COMPLETE TC
1o SS configures transport
to exceed threshold
2 MEASUREMENT CONTROL SS provides Traffic Volume
measurement criterias (event
4a) to UE.
3 Void
4 MEASUREMENT REPORT UE's transport channel is
loaded. UE reports that Traffic
Volume measurement event
4A is triggered.
2100 ms.
5a UE's transport channel traffic
volume decreases to zero.
5b MEASUREMENT CONTROL SS provides Traffic Volume
measurement criterias (event
4b) to UE.
6 MEASUREMENT REPORT UE reports that Traffic Volume
measurement event 4B is
triggered.
2100 ms.
7a SS increses transport channel
traffic volume so as to
exceed threshold
7b MEASUREMENT REPORT IE "Measurement Identity" is
set to "15".
7c UE's transport channel traffic
volume decreases to zero.
7d MEASUREMENT REPORT IE "Measurement Identity" is
set to "14".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1598
Message Type
Paging record
- CN domain identity PS Domain
- CHOICE UE Identity p-TMSI
- p-TMSI Allocated identity during the attach procedure

RRC CONNECTION REQUEST (Step 1a)
Message type
on step 1

- Traffic volume measurement objects
- UL target transport channel ID 1
- UE state CELL_DCH
- Traffic volume measurement reporting criteria
- Uplink transport channel type Not present
- UL Transport Channel ID Not present
- Traffic volume event identity 4a
- Tx interruption after trigger Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1599
MEASUREMENT CONTROL (Step 5b)
- Traffic volume measurement objects
- UL target transport channel ID 1
- UE state CELL_DCH
- Traffic volume measurement reporting criteria
- Uplink transport channel type Not present
- UL Transport Channel ID Not present
- Traffic volume event identity 4b
- Tx interruption after trigger Not present

MEASUREMENT REPORT (Step 4, step 5 and step 7b)
Measured Results
list"
- RB Identity 20
Event Results
- Uplink transport channel type causing the Check to see if set to "DCH"
event
- UL transport channel identity Check to see if set to "1"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1600
MEASUREMENT REPORT (Step 6, step 7 and 7d)
Measured Results
list"
- RB identity Check that value is 20
- RLC buffers payload Check that value is below the threshold
Event Results
- Uplink transport channel type causing the Check to see if set to "DCH"
event
- UL transport channel identity Check to see if set to "1"
- Traffic volume event identity Check to see if set to "4b"

In steps 4, 5, 6, 7, 7b and 7d UE sends RRC: MEASUREMENT REPORT with correct measurement identity
indication. RB identity and RLC buffers payload has correct values. Measurement identity, transport channel type,
transport channel identity and event identity has to match with set values.
8.4.1.31 Measurement Control and Report: Inter-RAT measurement in CELL_DCH
state.

A UE supporting both FDD and GSM shall be able to perform the GSM RSSI measurement and the GSM Initial BSIC
identification measurement.
If, according to its capabilities, the UE requires compressed mode to perform GSM RSSI measurements, the UE shall
perform GSM RSSI measurements in the gaps of a compressed mode pattern sequence specified for GSM RSSI
measurement purpose.
If, according to its capabilities, the UE requires compressed mode to perform GSM Initial BSIC identification
measurements, the UE shall perform GSM Initial BSIC identification in a compressed mode pattern sequence specified
for Initial BSIC identification measurement purpose.
Reference
3GPP TS 25.133, clause 8.1.2.5; 3GPP TS 25.331, clauses 8.6.7.6, 14.3.2.
Purpose of this test is to verify that UE is capable to perform GSM RSSI and GSM Initial BSIC identification
measurements.
Initial Condition
System Simulator: 1 UTRAN FDD cell and 2 GSM cells.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1601
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
Test Channel # 1 2
BCCH ARFCN # 1 7
CELL identity # 0 1
BSIC # BSIC1 BSIC2

UE: CELL_DCH state, state 6-9 as specified in clause 7.4 of TS 34.108.
System Information Block type 11 nor 12 does not include Inter-RAT measurement system information.
Test Procedure
The UE is brought to the CELL_DCH state after a successful outgoing call attempt. If the UE requires compressed
mode (refer ICS/IXIT), the SS sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to configure
the compressed mode pattern sequence parameters. Two compressed mode patterns are configured, according to the
message specified below. When the PHYSICAL CHANNEL RECONFIGURATION COMPLETE is received from the
UE, the SS sends a MEASUREMENT CONTROL message.
The first RRC: MEASUREMENT CONTROL message is used to provide measurement control parameters (GSM
RSSI) to the UE and to start compressed mode for the measurement if required according to the UE capabilities. The
UE replies according to request by sending RRC: MEASUREMENT REPORT messages periodically to SS. Reporting
period is 1000 ms.
After two RRC: MEASUREMENT REPORT messages, the SS sends a second RRC: MEASUREMENT CONTROL
message to start GSM Initial BSIC identification measurement. The UE replies similarly as in GSM RSSI measurement
case but now with a period of 12000ms.
The SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1602
Expected Sequence
UE SS
CELL_DCH state in the cell 1.
If the UE does not require
compressed mode (refer
ICS/IXIT), then goto step 4.
2 PHYSICAL CHANNEL
RECONFIGURATION
Compressed mode pattern
sequence parameters are
loaded to UE.
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS provides GSM RSSI
measurement control
parameters to UE. If the UE
requires compressed mode
(refer ICS/IXIT), compressed
mode for GSM RSSI
measurement is started.
5 MEASUREMENT REPORT UE reports measurement
results of GSM RSSI
measurement to SS.
6 MEASUREMENT REPORT Next periodical measurement
report.
7 MEASUREMENT CONTROL SS provides GSM Initial BSIC
identification measurement
control parameters to UE. If
the UE requires compressed
mode (refer
ICS/IXIT),compressed mode
for GSM Intial BSIC
identification measurement is
started.
8 MEASUREMENT REPORT UE reports measurement
results of GSM Initial BSIC
identification measurement to
SS.
9 MEASUREMENT REPORT Next periodical measurement
report.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1603
Use the same message sub-type as in TS 34.108 titled "Speech in CS", with the following exceptions:
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 2.0
- TGPSI 2
- TGCFN Not present

- TGMP GSM Initial BSIC identification
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1604
- BSIC BSIC1
- Band indicator DCS 1800 band used
- BCCH ARFCN 1
- BSIC BSIC2
- BCCH ARFCN 7
estimate
Not present
CHOICE system GSM
- BSIC verification required not required
CHOICE system GSM
reporting indicator
FALSE
- DPCH compressed mode status info If the UE requires compressed mode (refer ICS/IXIT),
this IE is present and contains the IEs as follows. If the
UE does not require compressed mode (refer ICS/IXIT),
this IE is not present.
- TGPSI 1
- TGPSI 2
- TGCFN Not present

MEASUREMENT REPORT, if the UE requires compressed mode (refer ICS/IXIT) (Step 5 and step 6)
Measured Results
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1605
- CHOICE system GSM

MEASUREMENT REPORT, if the UE doesnt requires compressed mode (refer ICS/IXIT) (Step 5 and step
6)
Measured Results
- CHOICE system GSM
CHOICE BSIC verified BSIC
- Inter-RAT cell id Check that is set to "0"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1606
- inter-RAT measurement object list Not present
estimate
Not present
CHOICE system GSM
- BSIC verification required required
CHOICE system GSM
- Observed time difference to to GSM FALSE
cell reporting indicator
- TGPSI 1
- TGCFN Not present
- TGPSI 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1607
MEASUREMENT REPORT (Step 8 and step 9)
Measured Results
- CHOICE system GSM
CHOICE BSIC Verified BSIC

In step 5 and step 6 UE reports correctly GSM RSSI values.
In step 8 and step 9 UE reports correctly BSIC values.
Reporting period is the requested one.
8.4.1.32 Void

8.4.1.33 Measurement Control and Report: Inter-RAT measurement, event 3a
1. When this event is ordered by UTRAN in a MEASUREMENT CONTROL message the UE shall send a report
when the estimated quality of the currently used frequency is below the value of the IE "Threshold own system"
and the hysteresis and time to trigger conditions are fulfilled and the estimated quality of the other system is
above the value of the IE "Threshold other system" and the hysteresis and time to trigger conditions are fulfilled.
2. If the IE "DPCH Compressed Mode Status Info" is present, [in the MEASUREMENT CONTROL message]:
- after the time indicated by IE "TGPS reconfiguration CFN" has elapsed:
- activate the pattern sequence stored in the variable TGPS_IDENTITY corresponding to each IE "TGPSI"
for which the "TGPS status flag" is set to "activate" at the time indicated by IE "TGCFN"; and
- begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence
measurement purpose of each activated pattern sequence;
- if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal:
- start the concerned pattern sequence immediately at that CFN;
- not alter pattern sequences stored in variable TGPS_IDENTITY, but not identitifed in IE "TGPSI"
3. The UE shall perform GSM RSSI measurements in the gaps of compressed mode pattern sequence specified for
GSM RSSI measurement purpose. The UE shall perform Initial BSIC identification in compressed mode pattern
sequence specified for Initial BSIC identification measurement purpose. The UE shall be able to measure the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1608
"Observed time difference to GSM cell" during a compressed mode pattern sequence configured for this
purpose. The UE shall perform BSIC re-confirmation in compressed mode pattern sequence specified for BSIC
re-confirmation measurement purpose.
4. If the IE "Inter-RAT measurement quantity" is received in a MEASUREMENT CONTROL message and
CHOICE system is GSM, the UE shall:
- if IE "BSIC verification required" is set to "required", for cells that match any of the BCCH ARFCN and
BSIC combinations in the list of inter-RAT cells that the UE has received in IE "Inter-RAT cell info list", and
that has a "verified" BSIC:
- report measurement quantities according to IE "inter-RAT reporting quantity" taking into account the
restrictions defined in TS 25.331 clause 8.6.7.6;
- trigger inter-RAT events according to IE "inter-RAT measurement reporting criteria"; and
- perform event evaluation for event-triggered reporting after BSIC has been verified for a GSM cell
- indicate non-verified BSIC for a GSM cell in the "Inter-RAT measured results list" IE
5. The UE shall include measured results in MEASUREMENT REPORT as specified in the IE "Inter-RAT
reporting quantity".
6. If IE "Observed time difference to GSM cell Reporting indicator " is set to "TRUE" [, the UE shall]:
include optional IE "Observed time difference to GSM cell" with the value set to the time difference to that
GSM cell for the GSM cells that have a BSIC that is "verified", and that match any of the BCCH ARFCN
and BSIC combinations in the list of inter-RAT cells that the UE has received in IE "Inter-RAT cell info list".
- if IE "GSM Carrier RSSI" is set to "TRUE"[, the UE shall]:
- include optional IE "GSM Carrier RSSI" with a value set to the measured RXLEV to that GSM cell in IE
"Inter-RAT measured results list".
- if the BSIC of reported GSM cell is "verified"[, the UE shall]:
- set the CHOICE BSIC to "Verified BSIC" and IE "inter-RAT cell id" to the value that GSM cell had in
the IE "Inter-RAT cell info list";
7. If the IE "Reporting Cell Status" is received, the UE shall set the IE "Measured Results" in MEASUREMENT
REPORT as follows.
- the maximum number of the IE "Cell Measured Results" to be included in the IE "Measured Results" is the
number specified in "Reporting Cell Status".
Reference
3GPP TS 25.331 clauses 8.4.1.3, 8.6.7.5, 8.6.7.6, 8.6.7.9, 14.3.1.1, 14.3.2.1, 14.3.2.2, 14.3.2.3.
1. To confirm that the UE starts compressed mode and inter-RAT measurements when so required by the network
in a MEASUREMEN CONTROL message.
2. To confirm that the UE sends MEASUREMENT REPORT message if event 3a is configured, if the quality of
the currently used UTRAN frequency is below a given threshold and the estimated quality of the other system is
above a certain threshold.
3. To confirm that the hysteresis and time to trigger behaviours for event 3a are correctly implemented.
4. To confirm that the UE verifies the BSIC of the cell triggering the event if so required by UTRAN and if the
proper compressed mode patterns have been configured in the UE by UTRAN.
5. To confirm that the content of the MEASUREMENT REPORT sent by the UE is according to what was required
by UTRAN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1609
NOTE: Test purpose 1 verifies conformance requirement 1 and 2.
NOTE: Test purpose 2 and 3 verifies conformance requirement 1.
NOTE: Test purpose 4 verifies conformance requirement 2, 3 and 4.
NOTE: Test purpose 5 verifies conformance requirement 4, 5, 6 and 7.
Initial Condition
System simulator: 1 UTRAN FDD cell and 3 GSM cells. The initial configurations of the 3 cells in the SS shall follow
the values indicated in the column marked T0. The table is found in "Test procedure".
Test procedure
Table 8.4.1.33.4-1
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
Cell 3
(GSM)
Test
Channel
# GSM Ch.1
GSM Ch.2

GSM Ch.3

BCCH
ARFCN
# 1 7 39
CELL
identity
# 0 1 2
BSIC # BSIC 1 BSIC 2 BSIC 3
RF Signal
Level
dB
m
-85 -85 -70 -76 -70 -85 -85 -85 -84 -84 -90 -90 -90 -90 -90

Table 8.4.1.33.4-2
Parameter Unit
Cell 1
(UTRA)
T0 T1 T2 T3 T4
UTRA RF
Channel Number
Ch.1
CPICH Ec
dBm
/3.84
Mhz
-60 -80 -80 -80 -60

The two tables above illustrate the downlink power to be applied for the two cells at various instants of the test
execution. Column marked "T0" denotes the initial conditions, while columns marked "T1", "T2", "T3" and "T4"
indicate the values to be applied subsequently.
The UE is initially in CELL_DCH, state 6-9 as specified in clause 7.4 of TS 34.108. UTRA cell 1 is the only cell in the
active set of the UE. If the UE requires compressed mode (refer ICS/IXIT), the SS sends a PHYSICAL CHANNEL
RECONFIGURATION message to the UE to configure the compressed mode pattern sequence parameters to the UE.
Three compressed mode patterns are configured, according to the message specified below. When the PHYSICAL
CHANNEL RECONFIGURATION COMPLETE is received from the UE, the SS sends a MEASUREMENT
CONTROL message to the UE, to set up inter-RAT measurements. Event 3a is set up in this message, and if the UE
requires compressed mode (refer ICS/IXIT), compressed mode is activated.
At instant T1, the CPICH Ec drops as described in table 8.4.1.33.4-2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1610
At instant T2, the RF signal for GSM cell 1 increases, and crosses the threshold for the other system defined for event
3a.
After reception of the MEASUREMENT REPORT message, at instant T3, the RF signal strength for GSM cell 2
increases but remains below the threshold for the other system for event 3a. During that time, the RF signal strength for
GSM cell 1 decreases, but remains above the releasing condition for event 3a.
At intant T4, the RF signal strength for GSM cell 1 increases above the threshold for the other system for event
3a+hysteresis. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1611
Expected Sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
loaded to UE.
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS configures event 3a in the
UE. If the UE requires
ICS/IXIT), compressed mode
is started.
tables 8.4.1.33.4-1 and
8.4.1.33.4-2.
6 SS waits for approximately 10
seconds and verifies that no
MEASUREMENT REPORT
messages are detected on
uplink DCCH.
tables 8.4.1.33.4-1 and
8.4.1.33.4-2.
8 MEASUREMENT REPORT After about 1.4s, the UE sends
a MEASUREMENT REPORT
to SS triggered by event 3a.
tables 8.4.1.33.4-1 and
8.4.1.33.4-2.
MEASUREMENT REPORT
uplink DCCH.
tables 8.4.1.33.4-1 and
8.4.1.33.4-2.
MEASUREMENT REPORT
uplink DCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1612
Use the same message sub-type in Annex A titled "Speech in CS", with the following exceptions:
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 1
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 2
- TGCFN Not present

- TGMP GSM BSIC identification
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 1
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 3
- TGCFN Not present

- TGMP GSM BSIC re-confirmation
- TGPRC Infinity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1613
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 1
- ITP Mode 0
- DeltaSIR1 1.0
- T Reconfirm abort 5 s

- Periodic Reporting / Event Trigger Reporting Mode Event triggered
CHOICE Inter-RAT Cell Removal Remove all inter-RAT cells
-Remove all inter-RAT cells (No Data)
New inter-RAT cells (1 to <MaxCellMeas>) MaxCellMeas=3
- BSIC BSIC1
- BCCH ARFCN 1
- BSIC BSIC2
- BCCH ARFCN 7
- BSIC BSIC3
- BCCH ARFCN 2
estimate

- CHOICE mode FDD
CHOICE system GSM
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1614
CHOICE system GSM
reporting indicator
FALSE
- Inter-RAT measurements reporting criteria
(1 to<maxMeasEvent>) <MaxMeasEvent>=1
- Inter-RAT event identity 3a
- Threshold own system -66
- W 0
- Threshold other system -80
- Hysteresis 5
- Time to Trigger 640 ms
- Reporting cell status Report cells within active set or within virtual active set
or of the other RAT
- Maximum number of reported cells 2 cells
- Transmission gap pattern sequence (1 to
<MaxTGPS>)
<MaxTGPS>=3
- TGPSI 1
- TGPSI 2
- TGPSI 3

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1615
Measured Results
- CHOICE system GSM
- Measured GSM cells Check that measurement results for two GSM cells are
included
- GSM carrier RSSI Check that measurement result is reasonable. RXLEV
is mapped to a value between 0 and 63. The RSSI bits
are numbered b0 to b5, where b0 is the least significant
bit. When mapping the RXLEV value to the RSSI bit
string, the first/ leftmost bit of the bit string contains the
most significant bit.
CHOICE BSIC Check it is set to verified BSIC
- inter-RAT cell id Check that it is set to 0.
- inter-RAT cell id Check that is set to 1
Event results Check that the IE is included
- CHOICE event result Check that this is set to inter-RAT measurement event
results
- Inter-RAT event identity Check that this is set to 3a
- Cells to report (1 to <maxCellMeas>) Check that <maxCellMeas>is set to 1
- CHOICE BSIC Check that this is set to verified BSIC
- Inter-RAT cell id Check that this is set to 0.

The UE shall not send any measurement report between instants T1 and T2.
Event 3a shall be triggered in the UE (i.e.the transmission of the MEASUREMENT REPORT) after instant T2.
Between instants T2 and T3, no MEASUREMENT REPORT message shall be received from the UE (since the
hysteresis condition for triggering event 3a is not fulfilled).
No MEASUREMENT REPORT message shall be received from the UE after instant T4 (since the signal strength for
cell 1 has not dropped under Threshold for event 3a-hysteresis).
8.4.1.34 Measurement Control and Report: Inter-RAT measurement, event 3b

If the IE "Inter-RAT cell info list" is received in a MEASUREMENT CONTROL message, the UE shall update the
variable CELL_INFO_LIST accordingly and in the following order. The UE shall:
- if the IE "Removed Inter-RAT cells" is received, at the position indicated by the IE "Inter-RAT cell id":
- clear the cell information stored in the variable CELL_INFO_LIST; and
- mark the position "vacant";
- if the IE "New Inter-RAT cells" is received, for each cell, and in the same order as the cells appear in the IE:
- update the variable CELL_INFO_LIST as follows:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1616
- if the IE "Inter-RAT cell id" is received:
- store received cell information at this position in the Inter-RAT cell info list in the variable
CELL_INFO_LIST, possibly overwriting any existing information in this position; and
- mark the position "occupied";
- if the IE "Inter-RAT cell id" is not received:
- store the received cell information at the first vacant position in ascending order in the Inter-RAT
cell info list in the variable CELL_INFO_LIST; and
- mark the position as "occupied";
When event 3b is configured in the UE within a measurement, the UE shall:
1>if the other RAT is GSM, and if IE "BSIC verification required" is set to "required":
2>if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several GSM
cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT
measurement:
3>if the inter-RAT cell id of any of those GSM cell is not stored in the variable TRIGGERED_3B_EVENT:
4>store the inter-RAT cell ids of the GSM cells that triggered the event and that were not previously
stored in the variable TRIGGERED_3B_EVENT into that variable;
5>set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b", "CHOICE BSIC"
to "verified BSIC" and "Inter-RAT cell id" to the GSM cells that triggered the event (worst one
first);
subclause 8.4.2 , not taking into account the cell individual offset;
2>if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variable
TRIGGERED_3B_EVENT:
3>remove the inter-RAT cell id of that GSM cell from the variable TRIGGERED_3B_EVENT.
1>if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required":
2>if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several of the
BCCH ARFCNs considered in that inter-RAT measurement:
3>if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3B_EVENT:
4>store the BCCH ARFCNs that triggered the event and that were not previously stored in the variable
TRIGGERED_3B_EVENT into that variable;
5>set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b", "CHOICE BSIC"
to "non verified BSIC" and "BCCH ARFCN" to BCCH ARFCNs that triggered the event (worst
one first);
5>set the IE "measured results" and the IE "additional measured results" according to 8.4.2, not
taking into account the cell individual offset;
2>if equation 2 below is fulfilled for a BCCH ARFCN that is stored in the variable TRIGGERED_3B_EVENT:
3>remove that BCCH ARFCN from the variable TRIGGERED_3B_EVENT.
Equation 1:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1617
2 /
3b RAT Other RAT Other RAT Other
H T CIO M - +
M
Other RAT
is the measurement quantity for the cell of the other system.
CIO
Other RAT
is the cell individual offset for the cell of the other system.
T
Other RAT
is the absolute threshold that applies for the other system in that measurement.
H
3b
is the hysteresis parameter for event 3b.
Equation 2:
2 /
3b RAT Other RAT Other RAT Other
H T CIO M + > +
M
Other RAT
is the measurement quantity for the cell of the other system. M
Other RAT
is expressed in dBm.
CIO
Other RAT
T
Other RAT
H
3b
is the hysteresis parameter for event 3b.
Reference
3GPP TS 25.331 clause 8.6.7.3, 14.3.1.2
1 To confirm that the UE sends MEASUREMENT REPORT message if event 3b is configured, if the estimated
quality of the other system is below a given threshold.
2 To confirm that the hysteresis and time to trigger behaviours for event 3b are correctly implemented. To confirm
that the UE updates the list of inter-RAT cells it stores according to what is ordered in the MEASUREMENT
CONTROL messages received from UTRAN.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1618
Test procedure
Table 8.4.1.34.4-1
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
Cell 3
(GSM)
T0 T1 T0 T1 T0 T1
Test Channel # GSM Ch.1 GSM Ch.2 GSM Ch.3
BCCH ARFCN # 1 7 39
CELL identity # 0 1 2
BSIC # BSIC 1 BSIC 2 BSIC 3
RF Signal Level dBm -70 -90 -70 -70 -90 -90

The table above illustrate the downlink power to be applied for the cells at various instants of the test execution.
Column marked "T0" denotes the initial conditions, while column marked "T1" indicates the values to be applied
subsequently.
CONTROL message to the UE, to set up inter-RAT measurements. Event 3b is set up in this message, and if the UE
requires compressed mode (refer ICS/IXIT), compressed mode is activated. The monitored GSM cells at measurement
establishment are GSM cells 1 and 2.
At instant T1, the RF signal strength for GSM cell 1 drops as described in table 8.4.1.34.4-1.
When the MEASUREMENT REPORT has been received by the SS, a MEASUREMENT CONTROL message is sent
to the UE, to add GSM cell 3 to the monitored GSM cells.
A second MEASUREMENT REPORT triggered by event 3b shall be received shortly after by the SS. SS calls for
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1619
Expected Sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
loaded to UE.
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS configures event 3b in the
is started.
MEASUREMENT REPORT
uplink DCCH.
tables 8.4.1.34.4-1.
7 MEASUREMENT REPORT After about 0.8 s, the UE
sends a MEASUREMENT
REPORT to SS triggered by
event 3b.
8 MEASUREMENT CONTROL SS adds GSM cell 3 to the list
of the monitored GSM cells.
sends a MEASUREMENT
event 3b.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1620
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 2
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 3
- TGCFN Not present

- TGPRC Infinity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1621
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1622
- BSIC BSIC1
- BCCH ARFCN 1
- BSIC BSIC2
- BCCH ARFCN 7
estimate
Not included
CHOICE system GSM
CHOICE system GSM
- Inter-RAT event identity 3b
- Threshold own system Not included
- W Not included
- Hysteresis 2
or of the other RAT
<MaxTGPS>)
<MaxTGPS>=3
- TGPSI 1
- TGPSI 2
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1623
- TGPSI 3

Measured Results
- CHOICE system GSM
included
- inter-RAT cell id Check that it is set to 1
- Observed time difference to GSM cell Check that the IE is not included
- Observed time difference to GSM cell Check that the IE is not present
results
- Inter-RAT event identity Check that this is set to 3b

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1624
- Measurement Reporting Transfer Mode Not present
- Periodic Reporting / Event Trigger Reporting Mode Not present
- inter-RAT cell id Not present
- BSIC BSIC3
- BCCH ARFCN 2
- inter-RAT measurement quantity Not present
- Parameters required for each event (1
to<maxMeasEvent>)
Not Present
Physical channel information elements Not present

Measured Results
- CHOICE system GSM
- Measured GSM cells Check that measurement results for three GSM cells
are included
- inter-RAT cell id Check that is set to 0 or 2.
- inter-RAT cell id Check that is set to 0 or 2 and that this inter-RAT cell id
is different from the two previous inter-RAT cell id.
results
- Inter-RAT event identity Check that this is set to 3b

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1625
Between instants T0 and T1, the UE shall not send any MEASUREMENT REPORT message to the SS.
Event 3b shall be triggered in the UE (i.e. the transmission of the first MEASUREMENT REPORT message shall
begin) after instant T1.
After the reception by the UE of the second MEASUREMENT CONTROL message, the UE shall begin to transmit the
second MEASUREMENT REPORT message (since the signal strength for GSM cell 3 is below the threshold for
triggering event 3b).
8.4.1.35 Measurement Control and Report: Inter-RAT measurement, event 3c

When event 3c is configured in the UE within a measurement, the UE shall:
2>if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several GSM
cells that match any of the BCCH ARFCN and BSIC combinations considered in that inter-RAT
measurement:
3>if the inter-RAT cell id of any of those GSM cell is not stored in the variable TRIGGERED_3C_EVENT:
4>store the Inter-RAT cell ids of the GSM cells that triggered the event and that were not previously
stored in the variable TRIGGERED_3C_EVENT into that variable;
5>set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c", "CHOICE BSIC"
to "verified BSIC" and "Inter-RAT cell id" to the GSM cells that triggered the event (best one
first);
5>set the IE "measured results" and the IE "additional measured results" according to 8.4.2, not
taking into account the cell individual offset;
2>if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variable
TRIGGERED_3C_EVENT:
3>remove the inter-RAT cell id of that GSM cell from the variable TRIGGERED_3C_EVENT.
2>if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one or several of the
BCCH ARFCNs considered in that inter-RAT measurement:
3>if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3C_EVENT:
4>store the BCCH ARFCNs that triggered the event and that were not previously stored in the variable
TRIGGERED_3C_EVENT into that variable;
5>set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c", "CHOICE BSIC"
to "non verified BSIC" and "BCCH ARFCN" to BCCH ARFCNs that triggered the event (best one
first);
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1626
2>if equation 2 is fulfilled for a BCCH ARFCN that is stored in the variable TRIGGERED_3C_EVENT:
3>remove that BCCH ARFCN from the variable TRIGGERED_3C_EVENT.
Equation 1:
2 /
3c RAT Other RAT Other RAT Other
H T CIO M + +
M
Other RAT
Other RAT
CIO
Other RAT
T
Other RAT
H
3c
is the hysteresis parameter for event 3c.
Equation 2:
2 /
3c RAT Other RAT Other RAT Other
H T CIO M - < +
M
Other RAT
Other RAT
CIO
Other RAT
T
Other RAT
H
3c
is the hysteresis parameter for event 3c.
Reference
3GPP TS 25.331 clauses 14.3.1.3, 8.4.2.2.
1 To confirm that the UE sends MEASUREMENT REPORT message if event 3c is configured, and if the quality
of the other system becomes better than the given threshold for event 3c.
2 To confirm that no other UE MEASUREMENT REPORT message is sent by the UE for a cell that has already
triggered event 3c as long as the hysteresis condition for triggering once again event 3c has not been fulfilled.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1627
Test procedure
Table 8.4.1.35.4-1
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
T0 T1 T2 T3 T0 T1 T2 T3
Test Channel # GSM Ch.1 GSM Ch.2
BCCH ARFCN # 1 7
CELL identity # 0 1
BSIC # BSIC 1 BSIC 2
RF Signal Level dBm -90 -75 -80 -75 -75 -75 -75 -75

The table above illustrate the downlink power to be applied for the two cells at various instants of the test execution.
Column marked "T0" denotes the initial conditions, while column marked "T1", "T2" and "T3" indicate the values to be
applied subsequently.
CONTROL message to the UE, to set up inter-RAT measurements. Event 3c is set up in this message, and if the UE
At instant T1, the RF signal strength for GSM cell 1 increases as described in table 8.4.1.35.4-1.
At instant T2, the RF signal strength for GSM cell 1 drops as described in table 8.4.1.35.4-1, and at instant T3, it
increases again to its previous level. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1628
Expected Sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
loaded to UE.
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS configures event 3c in the
is started.
MEASUREMENT REPORT
uplink DCCH.
table 8.4.1.35.4-1.
sends a MEASUREMENT
event 3b.
table 8.4.1.35.4-1.
table 8.4.1.35.4-1.
MEASUREMENT REPORT
uplink DCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1629
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 2
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 3
- TGCFN Not present

- TGPRC Infinity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1630
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0

- BSIC BSIC1
- BCCH ARFCN 1
- Cell individual offset -3
- BSIC BSIC2
- BCCH ARFCN 7
estimate
Not included
CHOICE system GSM
CHOICE system GSM
reporting indicator
FALSE
- Inter-RAT event identity 3c
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1631
- W Not included
- Hysteresis 5
or of the other RAT
<MaxTGPS>)
<MaxTGPS>=3
- TGPSI 1
- TGPSI 2
- TGPSI 3

Measured Results
- CHOICE system GSM
included
- inter-RAT cell id Check that it is set to either 0 or 1
- inter-RAT cell id Check that is set to 1 if the previous inter-RAT cell id
was set to 0 or to 0 if the previous cell if was set to 1.
results
- Inter-RAT event identity Check that this is set to 3c

After instant T1, since the cell individual offset for GSM cell 1 is +10 dB, event 3c shall be triggered in the UE, i.e the
UE shall begin to transmit a MEASUREMENT REPORT to the SS. Note that GSM cell 2 has not triggered event 3c
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1632
even though the RF signal strength for GSM cell 2 is the same as for cell 1, because the cell individual offset for GSM
cell 2 is -3 dB.
After instant T2, no MEASUREMENT REPORT shall be received from the UE, since GSM cell 1 has already triggered
event 3c, and since the RF signal strength has not dropped enough for the leaving condition to be met.
8.4.1.36 Measurement Control and Report: Inter-RAT measurement, event 3d

When event 3d is configured in the UE within a measurement, the UE shall:
3>store in the variable BEST_CELL_3D_EVENT the Inter-RAT cell id of the GSM cell that has the best
measured quantity among the GSM cells that match any of the BCCH ARFCN and BSIC combinations
considered in that inter-RAT measurement
3>send a measurement report with IE set as below:
4>set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d", "CHOICE BSIC" to
"verified BSIC" and "Inter-RAT cell id" to the GSM cell that is stored in the variable
BEST_CELL_3D_EVENT;
2>if equation 1 has been fulfilled for a time period indicated by "time to trigger" for a GSM cell that is different
from the one stored in BEST_CELL_3D_EVENT and that matches any of the BCCH ARFCN and BSIC
combinations considered in that inter-RAT measurement:
3>store the Inter-RAT cell id of that GSM cell in the variable BEST_CELL_3D_EVENT;
"verified BSIC" and "Inter-RAT cell id" to the GSM cell is now stored in BEST_CELL_3D_EVENT;
3>store in the variable BEST_CELL_3D_EVENT the BCCH ARFCN of the GSM cell that has the best
measured quantity among the BCCH ARFCNs considered in that inter-RAT measurement;
3>send a measurement report with IE set as below:
"non verified BSIC" and "BCCH ARFCN" to the BCH ARFCN that is stored in the variable
BEST_CELL_3D_EVENT;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1633
2>if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one of the BCCH
ARFCNs considered in that inter-RAT measurement and different from the one stored in
BEST_CELL_3D_EVENT:
3>store the BCCH ARFCN of that GSM cell in the variable BEST_CELL_3D_EVENT;
"non verified BSIC" and "BCCH ARFCN" to the BCCH ARFCN that is now stored in the variable
BEST_CELL_3D_EVENT;
Equation 1:
2 /
3 d Best New
H M M +
M
New
is the measurement quantity for a GSM cell that is not stored in the variable BEST_CELL_3D.
M
Best
is the measurement quantity for a GSM cell that is stored in the variable BEST_CELL_3D.
H
3d
is the hysteresis parameter for event 3d.
Reference
3GPP TS 25.331 clause 14.3.1.4.
1. To confirm that the UE sends MEASUREMENT REPORT message if event 3d is configured, and if the best cell
changes in the other system. To confirm that no other UE MEASUREMENT REPORT message is sent by the
UE for a cell that has already triggered event 3d as long as the hysteresis condition for triggering once again
event 3d has not been fulfilled.
Initial Condition
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1634
Test procedure
Table 8.4.1.36.4-1
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
T0 T1 T0 T1
BCCH ARFCN # 1 7
CELL identity # 0 1
RF Signal Level dBm -70 -90 -90 -70

Column marked "T0" denotes the initial conditions, while column marked "T1"indicates the values to be applied
subsequently.
CONTROL message to the UE, to set up inter-RAT measurements. Event 3d is set up in this message, and if the UE
At instant T1, the RF signal strength for GSM cell 1 increases while the RF signal strength for GSM cell 2 decreases as
described in table 8.4.1.36.4-1.
A MEASUREMENT CONTROL is then sent to the UE that releases the inter-RAT measurement, and deactivates
compressed mode. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1635
Expected Sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
loaded to UE.
3 PHYSICAL CHANNEL

4 MEASUREMENT CONTROL SS configures event 3d in the
is started.
5 MEASUREMENT REPORT The UE sends a
MEASUREMENT REPORT to
UTRAN indicating which is the
best GSM cells just after the
initiation of the measurement
tables 8.4.1.36.4-1.
7 MEASUREMENT REPORT After about 1 s, the UE sends
a MEASUREMENT REPORT
to SS triggered by event 3b.
8 MEASUREMENT CONTROL SS releases the inter-RAT
measurements, and, if the UE
requires compressed mode
(refer ICS/IXIT), deactivates
compressed mode.
9 If the UE requires compressed
mode (refer ICS/IXIT), SS
checks that the UE has
deactivated compressed
mode.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1636
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 12
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
Measurement capability) depends on UE's
- DeltaSIR1 1.0
- TGPSI 2
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 3
- TGCFN Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1637
- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 8
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0

- BSIC BSIC1
- BCCH ARFCN 1
- BSIC BSIC2
- BCCH ARFCN 7
estimate
Not included
CHOICE system GSM
CHOICE system GSM
reporting indicator
FALSE
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1638
- Inter-RAT event identity 3d
- Threshold own system Not present
- W Not present
- Threshold other system Not present
- Hysteresis 5
or of the other RAT
<MaxTGPS>)
<MaxTGPS>=3
- TGPSI 1
- TGPSI 2
- TGPSI 3

Measured Results
- CHOICE system GSM
included
results
- Inter-RAT event identity Check that this is set to 3d

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1639
Measured Results
- CHOICE system GSM
included
results
- Inter-RAT event identity Check that this is set to 3d

<MaxTGPS>)
<MaxTGPS>=3
- TGPSI 1
- TGCFN Not present
- TGPSI 2
- TGCFN Not present
- TGPSI 3
- TGCFN Not present

Shortly after the UE has received the first MEASUREMENT CONTROL message it shall transmit a MEASUREMENT
REPORT to the SS.
After instant T1, the UE shall begin to transmit a MEASUREMENT REPORT triggered by event 3d to the SS.
After receiving the second MEASUREMENT CONTROL message, the UE shall then stop running compressed mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1640
8.4.1.37 Measurement Control and Report: UE internal measurement, event 6c

When this event is ordered by UTRAN in a measurement control message, the UE shall send a measurement report
when the UE Tx power reaches its minimum value.
Reference
3GPP TS 25.331 clause 14.6.2.3.
1. To confirm that the UE sends a measurement report for event 6c when the UE Tx power reaches its minimum
value when event 6c has been configured in the UE through a MEASUREMENT CONTROL message.
Initial Condition
System simulator: 1 UTRAN cell.
Test procedure
The UE is initially in CELL_DCH, state 6-9 as specified in clause 7.4 of TS 34.108.
The SS sends a MEASUREMENT CONTROL message to the UE that configures event 6c.
The SS sends TPC_cmd equal to -1 until the transmitter power of the UE reaches its minimum value. SS calls for
Expected sequence
UE SS
UE.
3 The SS sends TPC_cmd
equal to -1 until the transmitter
power of the UE reaches its
minimum value, which shall be
below 50 dBm.
SS triggered by event 6c.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1641
Specific message content
- UE internal measurement quantity UE Transmitter Power
- UE Transmitted power TRUE
CHOICE mode
- UE internal measurement reporting criteria
measurement event
1 event
- UE internal event identity event 6c
- Time to trigger 0

- Periodic Reporting / Event Trigger Reporting Mode Event trigger
- CHOICE mode TDD
- measurement quantity UE Transmitter Power
- CHOICE mode TDD
- TADV info FALSE
measurement event

- UE internal event identity 6c
- Time to trigger 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1642
Measured Results
- CHOICE measurement Check to see if set to "UE internal measurement"
- UE Transmitted Power Check that this IE is set a value that is below 50 dBm.
- UE Rx-Tx report entities Check that this IE is not included
Measured results on RACH Check that this IE is not included
Additional measured results Check that this IE is not included
Event Results
CHOICE event result Check that this IE is set to UE internal measurement
event results
UE internal measurement results
UE internal event identity Check that this IE is set to 6c
CHOICE mode
Primary CPICH info This IE should not be included
Measured Results
- CHOICE measurement Check to see if set to "UE internal measured results "
-CHOICE mode Check to see if set to TDD
- UE Transmitted Power Check that this IE is set a value that is below 50 dBm.
- CHOICE TDD option Check to see if set to1.28 Mcps TDD
- TADV Check that this IE is not included
Event Results
event results
UE internal event identity Check that this IE is set to 6c

The UE shall then begin transmitting a MEASUREMENT REPORT message to SS triggered by event 6c when its
transmit power has reached its minimum output power. The minimum transmitted power of the UE shall be less than
50dBm.
8.4.1.38 Measurement Control and Report: UE internal measurement, event 6d
when the UE Tx power reaches its maximum value.
Reference
3GPP TS 25.331 clause 14.6.2.4
1. To confirm that the UE sends a measurement report for event 6d when the UE Tx power reaches its maximum
value when event 6d has been configured in the UE through a MEASUREMENT CONTROL message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1643
Initial Condition
System simulator: 1 UTRAN cell .
Test procedure
The SS sends TPC_cmd equal to +1 until the transmitter power of the UE reaches its maximum value. SS calls for
Expected sequence
UE SS
2 MEASUREMENT CONTROL SS configures event 6d in the
UE.
3 The SS sends TPC_cmd
equal to +1 until the
transmitter power of the UE
reaches its maximum value.
4 MEASUREMENT REPORT After about 200 ms, the UE
sends a MEASUREMENT
event 6d.

- UE internal measurement quantity UE Transmitter Power
- CHOICE mode
measurement event
1 event
- UE internal event identity event 6d

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1644
- Periodic Reporting / Event Trigger Reporting Mode Event triggere
- CHOICE mode TDD
- measurement quantity UE Transmitter Power
- CHOICE mode TDD
- TADV info FALSE
measurement event

- UE internal event identity 6d

Measured Results
- CHOICE measurement Check to see if set to "UE internal measurement"
- UE Transmitted Power Check that this IE is set to the maximum outpower of
the UE.
- UE Rx-Tx report entities Check that this IE is not included
Event Results
event results
UE internal event identity Check that this IE is set to 6d
CHOICE mode
Measured Results
- CHOICE measurement Check to see if set to "UE internal measured results "
- UE Transmitted Power Check that this IE is set to the maximum outpower of
the UE.
- CHOICE TDD option Check to see if set to 1.28 Mcps TDD
- TADV Check that this IE is not included
Event Results
event results
UE internal event identity Check that this IE is set to 6d

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1645
The UE shall then begin transmitting a MEASUREMENT REPORT message to SS triggered by event 6d when its
transmit power has reached its maximum. The maximum transmitted power of the UE shall be according to the class of
the UE.
8.4.1.39 Measurement Control and Report: UE internal measurement, event 6e
when the UE RSSI reaches the UE's dynamic receiver range.
Reference
3GPP TS 25.331 clause 14.6.2.5
1. To confirm that the UE sends a measurement report for event 6e when the UE RSSI reaches the UE's dynamic
receiver range when event 6e has been configured in the UE through a MEASUREMENT CONTROL message.
Initial Condition
System simulator: 1 UTRAN cell .
Test procedure
The SS increases its output power by 0.5 dB step until the UE RSSI reaches the UE's receiver dynamic range. SS calls
for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
UE SS
2 MEASUREMENT CONTROL SS configures event 6e in the
UE.
3 The SS increases its output
power by 0.5 dB steps until the
UE RSSI reaches the UE's
receiver dynamic range.
SS triggered by event 6e.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1646
- UE internal measurement quantity UTRA Carrier RSSI
- CHOICE mode FDD
measurement event
1 event
- UE internal event identity event 6e
- Time to trigger 0

- Periodic Reporting / Event Trigger Reporting Mode Event triggere
- CHOICE mode TDD
- measurement quantity UTRA Carrier RSSI
- UE Transmitted Power False
- CHOICE mode TDD
- TADV info False
CHOICE report criteria UE internal measurement reporting criteria
measurement event

- UE internal event identity 6e
- Time to trigger 0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1647
Measured Results
- CHOICE measurement UE internal measured results
- CHOICE mode FDD
- UE transmitted power Check that this value is within reasonable range of
value.
- UE Rx-TX report entries Check that this IE is not included
Event Results
event results
UE internal event identity Check that this IE is set to 6e
CHOICE mode

MEASUREMENT REPORT (Step 4)(TDD)
Measured Results Check that this IE is not included
Event Results
event results
UE internal event identity Check that this IE is set to 6e

The UE shall then begin transmitting a MEASUREMENT REPORT message to SS triggered by event 6e when the UE
RSSI reaches the UE's receiver dynamic range.
8.4.1.40 Measurement Control and Report: Inter-RAT measurement, event 3C, in
CELL_DCH state using sparse compressed mode pattern

1. Upon reception of a MEASUREMENT CONTROL message the UE shall perform actions specified in 3GPP TS
25.331 clause 8.6 unless otherwise specified below.

The UE shall:
- read the IE "Measurement command";
- if the IE "measurement command" has the value "setup":
- store this measurement in the variable MEASUREMENT_IDENTITY according to the IE "measurement
identity", possibly overwriting the measurement previously stored with that identity;
- for measurement types "inter-RAT measurement" or "inter-frequency measurement":
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1648
- if, according to its measurement capabilities, the UE requires compressed mode to perform the
measurements and a compressed mode pattern sequence with an appropriate measurement purpose is
simultaneously activated by the IE "DPCH compressed mode status info"; or
- if, according to its measurement capabilities, the UE does not require compressed mode to perform the
measurements:
- begin measurements according to the stored control information for this measurement identity;
2. Event 3c: The estimated quality of other system is above a certain threshold. When this event is ordered by
UTRAN in a measurement control message the UE shall send a report when the estimated quality of the other
system is above the value of the IE "Threshold other system" and the hysteresis and time to trigger conditions are
fulfilled. The corresponding report contains information specific for the other system.
Reference
3GPP TS 25.331 clause 8.4.1.3, 14.3.1.3.
This test case is only applicable to UEs supporting both FDD and GSM, and which require compressed mode to
perform the GSM related measurements.
1. To verify that the UE performs Inter-RAT measurement using a sparse compressed mode pattern as specified in
the MEASUREMENT CONTROL message.
2. To verify that the UE send MEASUREMENT REPORT message when event 3C is triggered, and if the quality
of the other system becomes better than the given threshold for event 3c.
3. To confirm that no other UE MEASUREMENT REPORT message is sent by the UE for a cell that has already
triggered event 3c as long as the hysteresis condition for triggering once again event 3c has not been fulfilled.
Table 8.4.1.40.4-1 Sparse compressed mode pattern for Inter RAT measurement
TGMP
T
G
C
F
N

T
G
P
R
C

T
G
S
N

T
G
L
1

T
G
L
2

T
G
D

T
G
P
L
1

T
G
P
L
2

Comment
GSM carrier RSSI
measurement
Note 1 Inf. 4 7 Not
sent
unde
fined
16 16 Set-up to monitor 16 GSM neighbours
every second measurement period, i.e.
every second 480ms period.
GSM Initial BSIC
identification
Note 1 Inf. 8 14 Not
sent
unde
fined
24 24 Equal to Pattern 6 in TS 25.133 table 8.7.
GSM BSIC re-
confirmation
Note 1 Inf. 8 14 Not
sent
unde
fined
24 24 Equal to Pattern 12 in TS 25.133 table 8.8.

NOTE 1: TGCFN can be found in the MEASUREMENT CONTROL message.
Initial Condition
System simulator: 1 UTRAN FDD cell and 2 GSM cells. The initial configurations of the cells in the SS shall follow
UE: "CS-DCCH +DTCH_DCH", state 6-9 as specified in clause 7.4 of TS 34.108.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1649
Test procedure
Table 8.4.1.40.4-2 Inter-RAT cell specific data
Parameter Unit
Cell 1
(GSM)
Cell 2
(GSM)
T0 T1 T2 T3 T0 T1 T2 T3
BCCH ARFCN # 1 7
CELL identity # 0 1
RF Signal Level dBm -90 -75 -80 -75 -75 -75 -75 -75

GSM cell 3 to 12 as indicated in the a MEASUREMENT CONTROL message shall not be active in the test, i.e. no
BCCH carrier shall be transmitted for GSM cell 3 to 12 in this test.
Column marked "T0" denotes the initial conditions, while column marked "T1", "T2" and "T3" indicate the values to be
applied subsequently.
The UE is initially in "CS-DCCH +DTCH_DCH", state 6-9 as specified in clause 7.4 of TS 34.108. UTRA cell 1 is the
only cell in the active set of the UE. The SS sends a PHYSICAL CHANNEL RECONFIGURATION message to the
UE to configure the compressed mode pattern sequence parameters to the UE. Three compressed mode patterns are
configured, according to the message specified below. When the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE is received from the UE, the SS sends a MEASUREMENT CONTROL message to the UE, to set up inter-
RAT measurements on 16 GSM cells. Event 3c is set up in this message, and compressed mode is activated.
At instant T1, the RF signal strength for GSM cell 1 increases as described in table 8.4.1.40.4-2, since the cell
individual offset for GSM cell 1 is 10 dB, event 3c shall be triggered in the UE. A MEASUREMENT REPORT shall be
sent to the SS. Note that GSM cell 2 has not triggered event 3c even though the RF signal strength for GSM cell 2 is the
same as for cell 1, because the cell individual offset for GSM cell 2 is -3 dB.
At instant T2, the RF signal strength for GSM cell 1 drops as described in table 8.4.1.40.4-2, and at instant T3, it
increases again to its previous level. No MEASUREMENT REPORT shall be received from the UE, since GSM cell 1
has already triggered event 3c, and since the RF signal strength has not dropped enough for the leaving condition to be
met. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1650
Expected Sequence
UE SS
2 PHYSICAL CHANNEL
RECONFIGURATION
loaded to UE.
3 PHYSICAL CHANNEL

UE, compressed mode is
started.
MEASUREMENT REPORT
uplink DCCH.
table 8.4.1.40.4-2.
sends a MEASUREMENT
event 3c.
table 8.4.1.40.4-2.
table 8.4.1.40.4-2.
MEASUREMENT REPORT
uplink DCCH.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1651
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not present
- TGD undefined
- TGPL1 16
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 2
- TGCFN Not present

- TGPRC Infinity
- TGSN 8
- TGL1 14
- TGL2 Not present
- TGD undefined
- TGPL1 24
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- TGPSI 3
- TGCFN Not present

- TGPRC Infinity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1652
- TGSN 8
- TGL1 14
- TGL2 Not present
- TGD undefined
- TGPL1 24
- TGPL2 Not present
- RPP Mode 0
- ITP Mode 0
- DeltaSIR1 1.0
- T Reconfirm abort 4.8 s

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1653
- BSIC BSIC1
- BCCH ARFCN 1
- Cell individual offset -3
- BSIC BSIC2
- BCCH ARFCN 3
- BSIC BSIC3
- BCCH ARFCN 5
- BSIC BSIC4
- BCCH ARFCN 7
- BSIC BSIC5
- BCCH ARFCN 9
- BSIC BSIC6
- BCCH ARFCN 11
- BSIC BSIC7
- BCCH ARFCN 13
- BSIC BSIC8
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1654
- BCCH ARFCN 15
- BSIC BSIC9
- BCCH ARFCN 17
- BSIC BSIC10
- BCCH ARFCN 19
- BSIC BSIC11
- BCCH ARFCN 21
- BSIC BSIC12
- BCCH ARFCN 7
- BSIC BSIC13
- BCCH ARFCN 9
- BSIC BSIC14
- BCCH ARFCN 11
- BSIC BSIC15
- BCCH ARFCN 13
- BSIC BSIC16
- BCCH ARFCN 15
estimate
Not included
CHOICE system GSM
CHOICE system GSM
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1655
- Inter-RAT event identity 3c
- W Not included
- Hysteresis 5
or of the other RAT
- DPCH compressed mode status info
<MaxTGPS>)
<MaxTGPS>=33f35s
- TGPSI 1
- TGCFN (Current CFN +(256 11 TTI/10msec)) mod 256
- TGPSI 2
- TGCFN (Current CFN +(256 7 TTI/10msec)) mod 256
- TGPSI 3
- TGCFN (Current CFN +(256 TTI/10msec)) mod 256

Measured Results
- CHOICE system GSM
included
- inter-RAT cell id Check that it is set to either 0 or 1
- inter-RAT cell id Check that is set to 1 if the previous inter-RAT cell id
was set to 0 or to 0 if the previous cell if was set to 1.
results
- Inter-RAT event identity Check that this is set to 3c

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1656
After instant T1, since the cell individual offset for GSM cell 1 is +10 dB, event 3c shall be triggered in the UE, i.e the
UE shall begin to transmit a MEASUREMENT REPORT to the SS. Note that GSM cell 2 has not triggered event 3c
even though the RF signal strength for GSM cell 2 is the same as for cell 1, because the cell individual offset for GSM
cell 2 is -3 dB.
After instant T2, no MEASUREMENT REPORT shall be received from the UE, since GSM cell 1 has already triggered
event 3c, and since the RF signal strength has not dropped enough for the leaving condition to be met.
8.4.1.41 Measurement Control and Report: Additional Measurements list

..
and
3> include only the available additional measured results, and sort them in ascending order according to
their IE "measurement identity" in the MEASUREMENT REPORT message.

If the IE "Additional Measurement List" is received in a MEASUREMENT CONTROL message, the UE shall:
1>if the received measurement configuration in this MEASUREMENT CONTROL message, or any measurement
referenced in the "Additional Measurement List" do not all have the same validity (for this consistency check the
UE should assume "CELL_DCH" as the measurement validity for measurements of type "inter-RAT", "UE
internal", and "quality"):
1>if any of the measurements referenced in the "Additional Measurement List" is an intra-frequency, inter-
frequence or inter-RAT measurement, and this measurement is configured with event based reporting:
1>if the result of this MEASUREMENT CONTROL message is such that more than one additional measurement
of the same type will be referenced in the IE "Additional Measurement List" in the
MEASUREMENT_IDENTITY variable:

If the measurement configured with the MEASUREMENT CONTROL message triggers a measurement report, the UE
shall also include the reporting quantities for the measurements referenced by the additional measurement identities.
The contents of the IE "Additional Measured results" is completely determined by the measurement configuration of the
referenced additional measurement.
..
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1657
Reference
3GPP TS 25.331, clause 8.4.2.2, 8.6.7.22
1. To confirm that the UE reports measured results for a referenced additional measurement.
2. To confirm that the UE transmits MEASUREMENT REPORT messages for a measurement, also if this
measurement is referenced as an additional measurement by another measurement.
Initial Condition
System Simulator: 1 cell, cell 1.
Test Procedure
of TS 34.108. Next, SS transmits MEASUREMENT CONTROL message to request the UE to perform UE internal
measurements and reporting for events 6A and 6B, followed by a MEASUREMENT CONTROL message to request
the UE to perform a periodic intra-frequency measurement. The intra-frequency measurement configuration references
as an additional measurement the measurement defined by the first MEASUREMENT CONTROL message.
The UE will start to periodically send MEASUREMENT REPORT messages for the intra-frequency measurement. The
reports shall include the UE Tx power as an additional measurement result.
After two MEASUREMENT REPORT messages, the SS increases the UE Tx power above the threshold set to event
6A. After 'time to trigger' the UE sends MEASUREMENT REPORT, triggered by event 6A, to the SS.
Next the SS decreases the UE Tx power below the threshold set for event 6B. After 'time to trigger' UE sends
MEASUREMENT REPORT, triggered by event 6B, to the SS.
Expected Sequence
UE SS
state in cell 1. SS sets the UE
transmission power between
15 and 18 dBm.
and reporting for events 6A
and 6B.
3 MEASUREMENT CONTROL SS requests a periodic intra-
frequency measurement.
5 MEASUREMENT REPORT Time difference between
earlier and this
MEASUREMENT REPORT
message should be 32
seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1658
UE SS
power above 18 dBm.
7 MEASUREMENT REPORT UE shall send 6A event
measurement report.
power below 15 dBm.
9 MEASUREMENT REPORT UE shall send 6B event
measurement report.

- UE internal measurement quantity Present
-CHOICE mode FDD
-UE internal measurement quantity UE Transmitted Power
- CHOICE mode FDD
measurement event

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1659
Additional measurements list
- Additional measurement identity 5
indicator
No report
indicator
FALSE
indicator
No report
indicator
FALSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1660
MEASUREMENT REPORT (Step 4 and step 5)
Measured Results
list"
- SFN-SFN observed time difference Check to see if this IE is absent
Additional Measured Results
- UE transmitted power Check to see if it is present and value is reasonable
- UE RX TX report entry list Check to see if it is absent

Measured Results
Event results
results"

Measured Results
Event results
results"

After step 3, the UE shall periodically transmit a MEASUREMENT REPORT message for measurement identity 5. In
addition to the CPICH RSCP, these reports shall also include the UL Tx power with a reasonable value.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1661
After step 6, the UE shall transmit a MEASUREMENT REPORT message, containing measured results for UE
transmitted power. The 'Event results' IE contains event identity 6A.
After step 8, the UE shall transmit a MEASUREMENT REPORT message, containing measured results for UE
transmitted power. The 'Event results' IE contains event identity 6B.
8.4.1.42 Measurement Control and Report: Change of Compressed Mode Method

1>if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag") in
3>deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see
subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken
into use.
3>set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to
"inactive".
2>if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence:
into use.
NOTE: The temporary deactivation of pattern sequences for which the status flag is set to "activate" can be used
by the network to align the timing of already active patterns with newly activated patterns.
2>activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" in
the variable TGPS_IDENTITY is set to "activate" at the time indicated by IE "TGCFN"; and
2>begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence
actions as specified in subclause 8.2.11.2.
.
Uplink and downlink compressed mode methods are described in TS 25.212. For UL "higher layer scheduling"
compressed mode method and transport format combination selection, see TS 25.321.
Reference
3GPP TS 25.331 clause 8.6.6.15.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1662
To confirm that the UE supports change of compressed mode method included in a RADIO BEARER SETUP message.
To confirm that the UE supports change of compressed mode method included in a RADIO BEARER RELEASE
message.
Initial Condition
System Simulator: 3 cells Cell 1 on frequency f
1
2
3
.
UE: "PS-DCCH_DCH" (state 6-7) as specified in clause 7.4 of TS 34.108. Ciphering shall be activated.
This test case applies only for UEs requiring compressed mode to perform inter- frequency measurements and
supporting both PS and CS domains.
Test Procedure
code for each cell.
Table 8.4.1.42-1a
Frequency f1
Scrambling
code
Scrambling code 1

T0 T1 T2 T3 T4 T5
CPICH Ec dBm/3.8
4 MHz
-60 -70 -70 -60 -70 -70

Table 8.4.1.42-1b
Frequency f2 f3
Scrambling
code

T0 T1 T2 T3 T4 T5 T0 T1 T2 T3 T4 T5
CPICH Ec dBm/3.
84 MHz
-95 -60 -60 -60 -60 -60 -95 -95 -60 -
95
-95 -60

The SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to download compressed mode
parameters in the UE but without activating compressed mode. The UE shall answer with a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message.
the UE.
The SS waits for 2560 ms for the UE to activate compressed mode.
2
shall then
The SS establishes a CS domain RAB and changes the compressed mode method to (from HLS to SF/2), by sending a
RADIO BEARER SETUP message on DCCH using AM-RLC. The UE shall answer with a RADIO BEARER SETUP
COMPLETE message.
3
shall then
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1663
At instant T3, the downlink power is changed according to what is shown in table 8.4.1.42-1.The increased quality of
the used frequency should result in clearing of the concerning TRIGGERED_2B_EVENT.
The SS establishes PS domain RAB and changes compressed mode method (from SF/2 to HLS) by sending a RADIO
BEARER SETUP message on DCCH using AM-RLC. The UE shall answer with a RADIO BEARER SETUP
COMPLETE message.
2
shall then
Next, the SS releases the PS domain RAB and changes compressed mode method (from HLS to SF/2) by sending a
RADIO BEARER RELEASE message on DCCH using AM-RLC. The UE shall answer with a RADIO BEARER
RELEASE COMPLETE message.
3
shall then
Expected Sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
SS downloads compressed
mode parameters (using HLS
method) without activating
compressed mode
2 PHYSICAL CHANNEL
downloading of compressed
mode parameters
the UE and activates
compressed mode
T1 in table 8.4.1.42-1.
MEASUREMENT REPORT
message to the SS.
6 RADIO BEARER SETUP SS establishes CS domain
RAB (speech) and changes to
SF/2 compressed mode
method
7 RADIO BEARER SETUP COMPLETE The UE acknowledges the
establishment of the RAB and
the compressed mode method
change.
1.
MEASUREMENT REPORT
message to the SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1664
the cells according to T3 in
table 8.4.1.42-1 (so the UE
can trigger event 2b again for
both frequencies if suitable
conditions arise)
11 RADIO BEARER SETUP SS establishes PS domain
RAB and changes
compressed mode method to
HLS.
the compressed mode method
change.
1.
MEASUREMENT REPORT
message to the SS.
15 RADIO BEARER RELEASE SS releases the PS domain
RAB and changes
SF/2.
16 RADIO BEARER RELEASE COMPLETE The UE acknowledges the
release of the RAB and the
compressed mode method
change.
T5 in table 8.4.1.42-1.
MEASUREMENT REPORT
message to the SS.

All messages shall use the same content as defined in [9] TS 34.108 clause 9, with the following exceptions:
PHYSICAL CHANNEL RECONFIGURATION MESSAGE (Step 1)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1665
CHOICE mode FDD
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD 0
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)
capability)
capability)
- DeltaSIR1 2.0

Mode
Event Trigger
- Frequency info
- Cell info
- CHOICE Mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1666
- Frequency info
- Cell info
- CHOICE Mode FDD
estimate
CPICH RSCP
indicator
No report
indicator
FALSE
- UE State CELL_DCH
- Hysteresis 1.0 dB
2
frequency

- TGPSI 1

Message Type
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1667
Measured Results
- Frequency info
-CHOICE mode FDD
Event results
- Frequency info
-CHOICE mode FDD

Use the same message sub-type found in TS 34.108 clause 9, which is entitled "Speech to CELL_DCH from
CELL_DCH in CS", with the following modifications:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1668
- TGPSI 1
parameters

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
capability)
- Downlink compressed mode method SF/2(or not sent, depending on the UE capability)
- Uplink compressed mode method SF/2(or not sent, depending on the UE capability)
- DeltaSIR1 2.0

Message Type
Measured Results
- Frequency info
-CHOICE mode FDD
uplink corresponding to f2 or f3(Could be absent in case
the duplex distance is the default duplex distance)
downlink corresponding to f2 or f3
(on f2) or Scrambling code 2 (on f3)
- Frequency info
-CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1669
Event results
- Frequency info
-CHOICE mode FDD
- Frequency info
-CHOICE mode FDD

Use the same message sub-type found in TS 34.108 clause 9, which is entitled "Packet to CELL_DCH from
CELL_DCH in PS", with the following modifications:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1670
- TGPSI 1
parameters

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
capability)
- Downlink compressed mode method HLS(or not sent, depending on the UE capability)
- Uplink compressed mode method HLS(or not sent, depending on the UE capability)
- DeltaSIR1 2.0

- TGPSI 1
parameters

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
capability)
- Downlink compressed mode method SF/2(or not sent, depending on the UE capability)
- Uplink compressed mode method SF/2(or not sent, depending on the UE capability)
- DeltaSIR1 2.0

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1671
to acknowledge the downloading of compressed mode parameters that were included in the PHYSICAL CHANNEL
RECONFIGURATION message of step 1.
2
. That message
shall only include cell 4 within the IE event results.
After step 6, the UE shall send a RADIO BEARER SETUP COMPLETE message to the SS to acknowledge the
establishment of the RAB and the change of compressed mode method that were included in the RADIO BEARER
SETUP message of step 6.
3
.
After step 11, the UE shall send a RADIO BEARER SETUP COMPLETE message to acknowledge the establishment
of the RAB and the compressed mode method change that were included in the RADIO BEARER SETUP message of
step 11.
2
. That message
After step 15, the UE shall send a RADIO BEARER RELEASE COMPLETE message to acknowledge the release of
the RAB and the compressed mode method change that were included in the RADIO BEARER RELEASE message of
step 15.
3
.
8.4.1.43 Measurement Control and Report: Compressed Mode Reconfiguration

1>if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag") in
into use.
into use.
"inactive".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1672
2>activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" in
the variable TGPS_IDENTITY is set to "activate" at the time indicated by IE "TGCFN"; and
actions as specified in subclause 8.2.11.2.
configuration parameters" is not included, the UE shall:
1>if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag" in
into use;
"inactive".
into use.
2>activate, at the time indicated by IE "TGCFN", the stored pattern sequence corresponding to each IE
"TGPSI" for which the "TGPS status flag" is set to "activate"; and
For transmission gap pattern sequences stored in variable TGPS_IDENTITY, but not identified in IE "TGPSI", the UE
shall:
1>if the received message implies a timing re-initialised hard handover (see subclause 8.3.5.1):
2>deactivate such transmission gap pattern sequences at the beginning of the frame, indicated by IE "Activation
time" (see subclause 8.6.3.1) received in this message; and
2>set IE "Current TGPS Status Flag" in corresponding UE variable TGPS_IDENTITY to 'inactive'.
1>if the received message not implies a timing re-initialised hard handover (see subclause 8.3.5.1):
2>continue such transmission gap pattern sequence according to IE "Current TGPS Status Flag" in the
corresponding UE variable TGPS_IDENTITY.
Uplink and downlink compressed mode methods are described in [27]. For UL "higher layer scheduling" compressed
mode method and transport format combination selection, see [15].
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1673
Reference
3GPP TS 25.331 clause 8.6.6.15.
To confirm that the UE supports deactivation of compressed mode included in a RADIO BEARER SETUP message.
To confirm that the UE supports reconfiguration of transport channel parameters (rate reduction PS RAB) and change
of compressed mode method included in a TRANSPORT CHANNEL RECONFIGURATION message.
To confirm that the UE supports change of compressed mode included in a RADIO BEARER RELEASE message.
To confirm that the UE supports reconfiguration of transport channel parameters (rate reduction PS RAB) without
performing hard handover included in a TRANSPORT CHANNEL RECONFIGURATION message.
Initial Condition
System Simulator: 3 cells Cell 1 on frequency f
1
2
3
.
UE: "CS-DCCH +DTCH_DCH" (state 6-9) as specified in clause 7.4 of TS 34.108. Ciphering shall be activated.
This test case applies only for UEs requiring compressed mode to perform inter- frequency measurements and
supporting both PS and CS domains.
Test Procedure
code for each cell.
Table 8.4.1.43-1a
Frequency f1
Scrambling
code
Scrambling code 1

T0 T1 T2 T3 T4 T5
CPICH Ec dBm/3.8
4 MHz
-60 -70 -70 -60 -70 -70

Table 8.4.1.43-1b
Frequency f2 f3
Scrambling
code

T0 T1 T2 T3 T4 T5 T0 T1 T2 T3 T4 T5
CPICH Ec dBm/3.8
4 MHz
-95 -60 -60 -95 -60 -60 -95 -95 -60 -95 -95 -60

Next, SS transmits a PHYSICAL CHANNEL RECONFIGURATION message to download compressed mode
parameters in the UE without activating compressed mode. The UE shall answer with a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message.
the UE.
The SS waits for 2560 ms for the UE to activate compressed mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1674
The SS establishes a PS domain RAB and de-activates compressed mode, by sending a RADIO BEARER SETUP
message on DCCH using AM-RLC. The UE shall answer with a RADIO BEARER SETUP COMPLETE message.
At instant T1, the downlink power is changed according to what is shown in table 8.4.1.43-1. The SS shall then verify
that the UE does not transmit a MEASUREMENT REPORT message.
Next the SS downloads compressed mode parameters and activates compressed mode by sending a PHYSICAL
CHANNEL RECONFIGURATION message on DCCH using AM-RLC. The UE shall answer with a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message.
Frequency f
2
shall then trigger event 2b, and the UE shall transmit a MEASUREMENT REPORT message to the SS.
Next, SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to reconfigure transport channel
parameters (rate reduction PS RAB) and to change compressed mode method (to SF/2). The UE shall answer with a
TRANSPORT CHANNEL RECONFIGURATION COMPLETE message.
3
shall then
At instant T3, the downlink power is changed according to what is shown in table 8.4.1.43-1.The increased quality of
the used frequency should result in clearing of the concering TRIGGERED_2B_EVENT.
Next, SS transmits a RADIO BEARER RELEASE message to release the CS domain RAB and change compressed
mode method (from SF/2 to HLS). The UE shall answer with a RADIO BEARER RELEASE COMPLETE message.
2
shall then
Next, SS transmits a TRANSPORT CHANNEL RECONFIGURATION message to reconfigure transport channel
parameters (rate increase PS RAB) without performing hard handover. The UE shall answer with a TRANSPORT
CHANNEL RECONFIGURATION COMPLETE message.
3
shall then
Expected Sequence
UE SS
1 PHYSICAL CHANNEL
RECONFIGURATION
mode parameters (using SF/2
method) without activating
compressed mode.
2 PHYSICAL CHANNEL
mode parameters.
the UE and activates
compressed mode.
3a SS waits for 2560 ms.
4 RADIO BEARER SETUP SS establishes PS domain
RAB and deactivates
compressed mode.
the deactivation of
compressed mode
T1 in table 8.4.1.43-1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1675
7 SS verifies that the UE does
not transmit a
MEASUREMENT REPORT
message to the SS.
8 PHYSICAL CHANNEL
RECONFIGURATION
mode parameters (using HLS
method) and activates
compressed mode.
9 PHYSICAL CHANNEL
mode parameters and the
activation of compressed
mode.
MEASUREMENT REPORT
message to the SS.
RECONFIGURATION
SS reconfigures transport
channel parameters (rate
reduction PS RAB) and
changes compressed mode
method to SF/2.
Rate should be reduced to 0
kbps no PS RAB room left to
use for gap.
transport channel
reconfiguration and the
change of compressed mode
method
1.
MEASUREMENT REPORT
message to the SS.
the cells according to T3 in
table 8.4.1.43-1 (so the UE
can trigger event 2b again for
both frequencies).
16 RADIO BEARER RELEASE SS releases the CS domain
RAB (speech) and changes
HLS.
17 RADIO BEARER RELEASE COMPLETE The UE acknowledges the
release of the RAB and the
compressed mode method
change.
1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1676
MEASUREMENT REPORT
message to the SS.
RECONFIGURATION
SS reconfigures transport
channel parameters (rate
increase PS RAB) without
performing hard handover. SS
includes TGCFNs for
compressed mode.
transport channel parameters
change.
T5 in table 8.4.1.43-1.
MEASUREMENT REPORT
message to the SS.

All messages shall use the same content as defined in [9] TS 34.108 clause 9, with the following exceptions:
CHOICE mode FDD
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1677
- RPP Mode 0
- ITP Mode 0
the UE capability)
- Downlink compressed mode method SF/2(or not sent, depending on the UE
capability)
- Uplink compressed mode method SF/2(or not sent, depending on the UE
capability)
- DeltaSIR1 2.0

Mode
Event Trigger
- Frequency info
- Cell info
- CHOICE Mode FDD
- Frequency info
- Cell info
- CHOICE Mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1678
estimate
CPICH RSCP
indicator
No report
indicator
FALSE
- UE State CELL_DCH
- Hysteresis 1.0 dB
2
frequency

- TGPSI 1

- TGPSI 1
- TGPS Status Flag De-activate
- TGCFN Not present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1679
CHOICE mode FDD
- TGPSI 1
- TGCFN Not present

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
the UE capability)
capability)
capability)
- DeltaSIR1 2.0

Message Type
Measured Results
- Frequency info
-CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1680
Event results
- Frequency info
-CHOICE mode FDD

sub-type titled "Packet to CELL_DCH from CELL_DCH in PS" in 34.108 [9], with the following exceptions:
channels
Do not include TFCs with TF's other than TF0 for PS
RAB
Added or Reconfigured UL TrCH information Reconfigure PS RAB TFS, only include TF0
transport channel
Do not include TFCs with TF's other than TF0 for PS
RAB
Added or Reconfigured DL TrCH information Reconfigure PS RAB TFS, only include TF0

Message Type
Measured Results
- Frequency info
-CHOICE mode FDD
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1681
- Frequency info
-CHOICE mode FDD
Event results
- Frequency info
-CHOICE mode FDD
- Frequency info
-CHOICE mode FDD

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1682
- TGPSI 1
parameters

- TGPRC Infinity
- TGSN 4
- TGL1 7
- TGL2 Not Present
- TGD undefined
- TGPL1 3
- TGPL2 Not Present
- RPP Mode 0
- ITP Mode 0
capability)
- Downlink compressed mode method HLS(or not sent, depending on the UE capability)
- Uplink compressed mode method HLS(or not sent, depending on the UE capability)
- DeltaSIR1 2.0

After step 1, the UE shall send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS to
acknowledge the downloading of the compressed mode parameters without activating compressed mode that were
included in the PHYSICAL CHANNEL RECONFIGURATION message of step 1.
After step 4, the UE shall send a RADIO BEARER SETUP COMPLETE message to acknowledge the establishment of
the PS domain RAB and the deactivation of compressed mode that were included in the RADIO BEARER SETUP
message of step 4.
After step 6, the UE shall not transmit a MEASUREMENT REPORT message.
After step 8, the UE shall send a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message to the SS to
acknowledge the downloading of the compressed mode parameters and the activation of compressed mode that were
included in the PHYSICAL CHANNEL RECONFIGURATION message of step 8.
2
. That message
After step 11, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message to the
SS to acknowledge the change of transport channel parameters and the change of compressed mode method that were
included in the TRANSPORT CHANNEL RECONFIGURATION message of step 11.
3
.
After step 17, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message to the SS to acknowledge the
release of the RAB and the change of compressed mode method that were included in the RADIO BEARER RELEASE
message of step 17.
2
. That message
After step 20, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message to the
SS to acknowledge the change of transport channel parameters that were included in the TRANSPORT CHANNEL
RECONFIGURATION message of step 20.
3
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1683
8.4.1.44 Measurement Control and Report: Intra-frequency measurement for events
1H and 1I (TDD)

When event 1h is configured in the UE, the UE shall:
1>if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH is not included in
the IE "cells triggered" in the variable TRIGGERED_1H_EVENT:
2>include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1H_EVENT;
2>send a measurement report with the IEs set as below:
3>set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1h" and in "cell
measurement event results" the "Cell parameters ID" of the P-CCPCH that triggered the report;
3>include in "Cell measured results" the "Timeslot ISCP" of those cells that are included in the variable
TRIGGERED_1H_EVENT.
1>if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1H_EVENT:
3>set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1h" and "cell
measurement event results" to the "Cell parameters ID" of the P-CCPCH that triggered the report;
3>set in "measured results " the "Timeslot ISCP" of those cells that are included in the variable
TRIGGERED_1H_EVENT and "additional measured results" according to subclause 8.4.2 in TS 25.331,
not taking into account the cell individual offset for each cell.
1>if Equation 2 below is fulfilled for a primary CCPCH:
2>if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1H_EVENT:
3>remove the entry of that primary CCPCH from "cells triggered" in the variable
TRIGGERED_1H_EVENT.
The UE shall use the equations below for evaluation of reporting event 1h:
Equation 1
, 10
1
1
h i i
T O H LogM h < + +

Equation 2
, 10
1
1
h i i
T O H LogM h > - +

M
i
is the Timeslot ISCP of the currently evaluated cell i expressed in mW
O
i
is the cell individual offset of the currently evaluated cell i
T
1h
is the Threshold for event 1h
H
1h
is the hysteresis parameter for the event 1h.
Before any evaluation is done, the Timeslot ISCP expressed in mW is filtered according to subclause 8.6.7.2. in TS
25.331
When event 1i is configured in the UE, the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1684
1>if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH is not included in
the IE "cells triggered" in the variable TRIGGERED_1I_EVENT:
2>include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1I_EVENT;
2>send a measurement report with the IEs set as below:
3>set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1i" and in "cell
measurement event results" to the "Cell parameters ID" of the P-CCPCH that triggered the report;
3>include in "measured results" the "Timeslot ISCP" of those cells that are included in the variable
TRIGGERED_1I_EVENT and "additional measured results" according to 8.4.2 in TS 25.331, not taking
into account the cell individual offset for each cell.
1>if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1I_EVENT:
3>if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1I_EVENT:
TRIGGERED_1I_EVENT.
The UE shall use the equation below for evaluation of reporting event 1i:
Equation 1
, 10
1
1
h i i
T O H LogM i > + -

Equation 2
, 10
1
1
h i i
T O H LogM i < + +

M
i
is the Timeslot ISCP of the currently evaluated cell i expressed in mW
O
i
T
1i
is the Threshold for event 1i
H
1i
is the hysteresis parameter for the event 1i.
Before any evaluation is done, the Timeslot ISCP expressed in mW is filtered according to subclause 8.6.7.2. in TS
25.331
Reference
3GPP TS 25.331 clause 14.1.3.2, 14.1.3.3.
1. To confirm that the UE sends MEASUREMENT REPORT message if event 1I is configured and intra-frequency
measurement indicates that Timeslot ISCP is above a certain threshold
2. To confirm that the UE sends MEASUREMENT REPORT message if event 1H is configured, and intra-
frequency measurement indicates that Timeslot ISCP is below a certain threshold
8.4.1.44.4.1 3.84 Mcps option
<FFS>
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1685
8.4.1.44.4.2 1.28 Mcps option
Initial Condition
System Simulator: 1 cell The initial configurations of the cell in the SS shall follow the values indicated in the column
marked "T1" in table 8.4.1.44.4.2-1. Threshold for events 1H and 1I are specified in table 8.4.1.44.4.2-2
The test consists of four successive time periods, with a time duration of T1, T2, T3 and T4 respectively. Two cells
shall be present in the test, being cell 1 the current serving cell. Timeslot ISCP values are specified for the cell, to check
against a certain threshold.
Test Procedure
Table 8.4.1.44.4.2-1 illustrates the Cell 1 specific test parameters for correct event 1H and 1I reporting in AWGN
propagation condition. The other RF values needed for the test are referred to section 8 in TS 34.122
Column marked "T1" denotes the initial conditions, while columns marked "T2", "T3" and "T4" are to be
applied subsequently. The exact instants on which these values shall be applied are described in the text
below.
Table 8.4.1.44.4.2-1
T1 T2 T3 T4
UTRA RF Channel
Number

Channel 1
DL timeslot number 6
PCCPCH RSCP dBm n.a.
TS ISCP, Note 1 -74 -64 -74 -64
oc
I
dBm /
1.28 MHz
-70
Note 1: The TS ISCP level is a calculated value.

Table 8.4.1.44.4.2-2
Parameter Unit Value Comment
Threshold used frequency dBm -69 Applicable for event 1H, cell 1 timeslot 6
Threshold used frequency dBm -69 Applicable for event 1I, cell 1 timeslot 6

The UE is initially in CELL_DCH state of cell 1. System Information Block type 11 is configured according to allow
measurement for intrafrequency, 1 Cell is defined and Timeslot 6 is defined for measurements. SS then sends
MEASUREMENT CONTROL message to the UE to modify earlier configured intra-frequency measurement and a
primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1I_EVENT and
TRIGGERED_1H_EVENT.
UE shall report TRIGGERED_1H_EVENT or TRIGGERED_1I_EVENT in the different time periods during the test.
SS re-adjusts the downlink transmission power settings according to columns "T2", "T3" and "T4" successively in table
8.4.1.44.4.2-1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1686
Expected Sequence
UE SS
1 System Information Block type 11 The UE is in CELL_DCH and
settings
2 MEASUREMENT CONTROL Event 1I and 1H are
configured. IEs and threshold
values are included
3 MEASUREMENT REPORT Event 1H is triggered. The UE
shall report that for cell 1
timeslot 6, ISCP is below than
threshold
table 8.4.1.44.4.2-1.
5 MEASUREMENT REPORT Event 1I is triggered. The UE
timeslot 6 ISCP is above
threshold
table 8.4.1.44.4.2-1.
7 MEASUREMENT REPORT Event 1H is triggered. The UE
timeslot 6, ISCP is below than
threshold
table 8.4.1.44.4.2-1.
9 MEASUREMENT REPORT Event 1I is triggered. The UE
timeslot 6 ISCP is above
threshold
passes, otherwise it fails

exceptions:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1687
- Cell info
- CHOICE Mode TDD
- Primary CCPCH TX Power Not present
- Timeslot List
- Timeslot Number 6
- Burst Type Type 1
serving cell)
- Intra-frequency measurement for RACH reporting Not Present

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1688
Mode
Event Trigger
- Intra-frequency cell info list Not present
- CHOICE Mode TDD
indicator
FALSE
- Timeslot ISCP reporting indicator TRUE
indicator
FALSE
- Intra-frequency event identity 1h
- Threshold used frequency -69 dB
- Hysteresis 0 dB
- Time to Trigger 0
- Intra-frequency event identity 1i
- Threshold used frequency -69 dB
- Hysteresis 0 dB
- Time to Trigger 0

Measured Results
results list"
- Cell parameters ID Check to see if it's the same for cell 1
- Timeslot ISCP Check to see if this IE is present
Event Results
- Intra-frequency event identity Check to see if this IE is set to "1H"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1689
Measured Results
results list"
Event Results
- Intra-frequency event identity Check to see if this IE is set to "1I"

Measured Results
results list"
Event Results
- Intra-frequency event identity Check to see if this IE is set to "1H"

Measured Results
results list"
Event Results
- Intra-frequency event identity Check to see if this IE is set to "1I"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1690
The UE shall send one event 1H triggered measurement report, with a measurement reporting delay less than 400 ms
from the beginning of time period T2.
The UE shall send one event 1I triggered measurement report, with a measurement reporting delay less than 400 ms
The UE shall send one event 1H triggered measurement report, with a measurement reporting delay less than 400 ms
The UE shall not send event 1H or 1I triggered measurement reports, as long as the reporting criteria are not fulfilled.
8.4.1.45 Measurement Control and Report: Intra-frequency measurement for event
1G (1.28 McpsTDD)

When event 1G is configured in the UE, the UE shall:
1>if the equation 1 is fulfilled for a P-CCPCHs during the time "Time to trigger" and if that P-CCPCH is not
included in the "primary CCPCH info" in the variable TRIGGERED_1G_EVENT:
2>include that P-CCPCH in "cells triggered" in the variable TRIGGERED_1G_EVENT;
3>set in "intra-frequency measurement event results": "Intrafrequency event identity" to "1g";
3>set the first entry in "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH which
was stored in the variable TRIGGERED_1G_EVENT;
3>include all entries in "cells triggered" in variable TRIGGERED_1G_EVENT in "cell measurement event
results" in the measurement report in descending order according to:

O LogM + 10

where M is the P-CCPCH RSCP and O the individual offset of a cell;
3>set the IE "measured results" and the IE "additional measured results" according to subclause 8.4.2, not
2>if a primary CCPCH is included in the "cells triggered" in the variable TRIGGERED_1G_EVENT:
TRIGGERED_1G_EVENT;
The UE shall use the equations below for evaluation of reporting event 1g:
Equation 1
, 10 10
_ _ 1 best previous best previous g
O LogM H O LogM
i i
+ > - +
M
previous_best
is the current P-CCPCH RSCP of the previous best cell expressed in mW
O
previous_best
is the cell individual offset of the previous best cell
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1691
M
i
is the current P-CCPCH RSCP of the currently evaluated cell i expressed in mW
O
i
H
1g
is the hysteresis parameter for the event 1g.
Equation 2
, 10 10
_ _ 1 best previous best previous g
O LogM H O LogM
i i
+ < + +
M
previous_best
is the current P-CCPCH RSCP of the previous best cell expressed in mW
O
previous_best
is the cell individual offset of the previous best cell
M
i
is the current P-CCPCH RSCP of the currently evaluated cell i expressed in mW
O
i
H
1g
is the hysteresis parameter for the event 1g.

Reference
3GPP TS 25.331, clauses 14.1.3.1
1. To confirm that the UE sends MEASUREMENT REPORT message if event 1G is configured and
intra-frequency measurement indicates change of best cell.

Initial Condition
System Simulator: 2 cell(cell 1 and cell 2 are active).The initial configurations of the 2 cells in the SS shall follow the
values indicated in the column marked "T0" in table 8.4.1.45-1. The table is found in "Test Procedure" clause.
Test Procedure
execution. Column marked "T0" denotes the initial conditions, while column marked "T1" is to be applied
Table 8.4.1.45-1
T0 T1 T0 T1
UTRA RFChannel
Number
Ch. 1 Ch. 1
P-CCPCH RSCP dBm -65 -65 -70 -60

The UE is initially in CELL_DCH state of cell 1.
SS transmits MEASUREMENT CONTROL message to request the UE to perform intra-frequency measurement. The
key measurement parameters are as follow: measurement type ="intra-frequency measurement", measurement quantity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1692
="PCCPCH RSCP", report criteria ="periodic reporting criteria", reporting interval ="64 seconds".UE shall transmit a
MEASUREMENT REPORT message and another after 64 seconds.
SS transmits a new MEASUREMENT CONTROL message to request UE to perform intra-frequency measurement and
report Event 1G. All intra-frequency cells are removed, and Cell 2 is included as new intra-frequency cell. SS checks to
see that no MEASUREMENT REPORT messages are sent within the next 64 seconds (which is due to periodic
reporting).
SS reconfigures the downlink transmission power settings according to values in column "T1" in table 8.4.1.45-1. The
UE shall transmit a MEASUREMENT REPORT message when it detects that the PCCPCH RSCP of cell 2 and
indicating Cell 2 as a best cell. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected Sequence
UE SS
0 The UE is in CELL_DCH of
cell 1.
1 MEASUREMENT CONTROL Intra-frequency
measurement is configured.
2 MEASUREMENT REPORT The message should be
repeated after 64 seconds
4 MEASUREMENT CONTROL Event 1G is configured
5 SS wait for 64seconds to
verify that no
MEASUREMENT
REPORTmessage is
received
table 8.4.1.45-1.
7 MEASUREMENT REPORT UE report that Event 1G is
triggered and cell 2 is the
best cell

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1693
- CHOICE Intra-frequency cell removal Remove no intra-frequency cells
- Cell info
- CHOICE mode TDD
- Cell parameters ID Set to same cell parameters ID as used for cell 1
indicator
FALSE
indicator
FALSE
- Reporting quantities for detected cells Not Present
- Periodical or event trigger Periodical reporting

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1694
MEASUREMENT REPORT (Step 2 and 3) ( 1.28 Mcps TDD)
Measured Results
- CHOICE measurement Check to see if set to Intra-frequency measured
results list
- Cell synchronisation information Check to see if is absent
- cell parameters ID Check to see if it is the same for cell 1
- PCCPCH RSCP Check to see if is present and value is
reasonable
- Pathloss Check to see if is absent
Measured results on RACH Check to see if is absent
Additional measured results Check to see if is absent
Event results Check to see if is absent

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1695
MEASUREMENT CONTROL (Step 4) ( 1.28 Mcps TDD)
- CHOICE Intra-frequency cell removal Remove all intra-frequency cells
- Cell info
- CHOICE mode TDD
- Primary CCPCH Info Set to same cell parameters ID as used for cell
1
- Cell info
- CHOICE mode TDD
- Primary CCPCH Info Set to same cell parameters ID as used for cell
2
indicator
FALSE
indicator
FALSE
- Reporting quantities for detected cells Not Present
- Reporting range Constant Not Present
- W Not Present
- Hysteresis 1 dB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-03)
3GPP
1696
- CHOICE reported cell Report cells within active and/or monitored set
on used frequency or within active and/or
monitored set on non-used frequency
- Periodical or event trigger Event trigger

MEASUREMENT REPORT (Step 7) ( 1.28 Mcps TDD)
Measured Results
- CHOICE measurement Check to see if set to Intra-frequency measured
results list
reasonable
reasonable
Measured results on RACH Check to see if is absent
Additional measured results Check to see if is absent
Event results Check to see if is absent
- CHOICE event result Check to see if set to Intra-frequency
measurement event results
- Intra-frequency event identity Check to see if set to 1g
- Cell parameters Id Check to see if it is the same for cell 2

After step 1, the UE shall transmit MEASUREMENT REPORT message periodically with the interval of 64 seconds.
After step 4, the UE shall not transmit any MEASUREMENT REPORT message.
After step 6, the UE shall transmit MEASUREMENT REPORT message, containing measured results for P-CCPCH
RSCP. The 'Event results' IE contains event identity 1G.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1697
9 Elementary procedures of mobility management
The tests are based on TS 24.008.
In this clause, when the expected sequence require that "a mobile originated CM connection is attempted", it shall be for
a service other than emergency call.
In this clause, a initial CM message is either a SETUP message, a REGISTER message or a CP-DATA message (in that
case the acknowledged mode of operation on SAPI 3 will have be established and this message will be sent on SAPI 3).
All tests in this clause shall only be performed in Network Mode of Operation II, unless specifically specified otherwise
in individual sub-clauses.
9.1 TMSI reallocation
The intention of the TMSI Reallocation procedure is to assign a new temporary identity for the UE. If the message is
not understood by the UE, the network could not establish a link to the UE. As this is a common MM procedure, it can
be initiated at any time.
9.1.1 Definition
9.1.2 Conformance requirement
1) A UE shall acknowledge a new TMSI when explicitly allocated during a location updating procedure or an
incoming call.
2) The TMSI shall be updated on the USIM when the UE is correctly deactivated in accordance with the
manufacturer's instructions.
3) A UE shall answer paging with this TMSI and includes it in the PAGING RESPONSE message.
Reference(s)
TS 24.008 clause 4.3.1.
9.1.3 Test purpose
To verify that the UE is able to receive and acknowledge a new TMSI by means of an explicit TMSI reallocation
procedure.
To verify that the UE has stored the TMSI in a non-volatile memory.
The implicit reallocation procedure is tested in clause 9.4.1.
9.1.4 Method of test
Initial conditions
- System Simulator:
- two cells A and B, belonging to different location areas a and b, default parameters.
- User Equipment:
- the UE has valid TMSI (=TMSI1), CKSN, CK, IK. It is "idle updated" on cell B.
Switch off button Yes/No.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1698
Way to bring the UE into service.
Test Procedure
The UE is paged in cell B and the security mode is established. An explicit TMSI reallocation procedure is performed.
The RRC CONNECTION is released. The UE is switched off and then its power supply is interrupted for 10 s. The
power supply is resumed and then the UE is switched on and allowed sufficient time to guarantee that the UE is in
service (listening to its paging subchannel). The system simulator then checks, by paging, whether the UE has stored the
received TMSI.
The UE is made to select cell A. A normal location updating procedure is performed in cell A. An explicit TMSI
reallocation procedure is performed and then the location updating procedure is accepted by the SS. The system
simulator checks, by paging, whether the UE has stored the allocated TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1699
Expected sequence
UE SS
The following messages are sent and shall be received on cell B.
1 Mobile terminated establishment
of Radio Resource Connection
See TS 34.108 clause 7.1.2
"Initial UE identity" =TMSI1.
Establishment Cause: Terminating Conversation Call.
2 PAGING RESPONSE "Mobile identity" =TMSI1
2a AUTHENTICATION REQUEST
2b AUTHENTICATION RESPONSE
3 SS The SS starts integrity protection.
4 Void
5 TMSI REALLOCATION
COMMAND
"Mobile identity" =new TMSI (TMSI2) different from TMSI
1.
6 TMSI REALLOCATION
COMPLETE

7 SS The SS releases the RRC connection.
8 Void
9 UE If possible (see ICS), the UE is switched off.
9a UE The power supply is interrupted for 10 s.
10 UE The UE is switched on.
11 SS The SS waits for 5 seconds to guarantee that the UE is in
service (listening to its paging subchannel).
"Initial UE identity" =TMSI2.
13 PAGING RESPONSE "Mobile identity" =TMSI2.
14 SS The SS releases the RRC connection. The following
messages are sent and shall be received on cell A
15 Void
16 SS Set the cell type of cell A to the "Serving cell".
Set the cell type of cell B to the "non-suitable cell"
(see note)
17 SS RRC CONNECTION REQUEST The SS verifies that the IE "Establishment cause" in the
received RRC CONNECTION REQUEST message is set
to "Registration".
18 Void
19 Void
20 LOCATION UPDATING
REQUEST
location updating type =normal, "ciphering key sequence
number" =CKSN, LAI =b, "mobile identity" =TMSI2.
20c SS The SS starts integrity protection.
20d Void
21 TMSI REALLOCATION
COMMAND
TMSI =TMSI1.
COMPLETE

23 LOCATION UPDATING ACCEPT This message does not contain the optional Mobile
Identity field.
25 Void
25a The SS waits for 5 seconds to allow the UE to become
"idle updated" on cell A.
"Initial UE identity" IE contains the new TMSI (=TMSI1).
"Establishment cause": Terminating Conversational Call.
27 PAGING RESPONSE "Mobile identity" IE contains the new TMSI (=TMSI1).
29 Void
NOTE: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference
Radio Conditions for signalling test cases only".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1700
None.
9.1.5 Test requirement
At step 5 the UE shall receive and acknowledge a new TMSI (TMSI2) and has stored that in the USIM, and the UE is
switched off and on after step 9 and 10.
At step 13 the UE shall transmit a new TMSI2 and includes it in the PAGING RESPONSE message.
At step 27 the UE shall answer paging with this TMSI1 and includes it in the PAGING RESPONSE message.
9.2 Authentication
The purpose of this procedure is to verify the user identity. A correct response is essential to guarantee the
establishment of the connection. If not, the connection will drop.
The SS shall be able to handle vectors of AUTN, RAND, CK, IK, AUTS and XRES in a similar way as the MSC/BSS
entities. The SS and test USIM shall incorporate a test algorithm for generating RES and CK, IK from RAND, AUTN
and IK which operates as described in TS 34.108 clause 8.1.2.
9.2.1 Authentication accepted
9.2.1.1 Definition
1) A UE shall correctly respond to an AUTHENTICATION REQUEST message by sending an
AUTHENTICATION RESPONSE message with the RES information field set to the same value as the one
produced by the authentication algorithm in the network.
2) A UE shall indicate in a PAGING RESPONSE message the ciphering key sequence number which was allocated
to it through the authentication procedure.
Reference(s)
TS 24.008 clauses 4.3.2.2 and 4.3.2.4.
1) To check that a UE correctly responds to an AUTHENTICATION REQUEST message by sending an
AUTHENTICATION RESPONSE message with the RES information field set to the same value as the one
produced by the authentication algorithm in the network.
2) To check that a UE indicates in a PAGING RESPONSE message the ciphering key sequence number which was
allocated to it through the authentication procedure.
Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE has valid TMSI, CKSN (CKSN1), CK, IK. It is "idle updated" on the cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1701
None.
Test Procedure
The UE is paged. After the UE has sent a PAGING RESPONSE message to the SS, the SS initiates an authentication
procedure and checks the value RES sent by the UE in the AUTHENTICATION RESPONSE message. The RRC
CONNECTION is released. The UE is paged and the SS checks the value of the ciphering key sequence number sent by
the UE in the PAGING RESPONSE message.
Expected sequence
UE SS
Establishment Cause: Terminating Conversational Call.
2 PAGING RESPONSE CKSN =CKSN1
3 AUTHENTICATION REQUEST The SS initiates authentication with CKSN2 different from
CKSN1.
4 AUTHENTICATION RESPONSE "Auth. parameter RES" IE shall be bit exact with the
value as produced by the authentication algorithm.
6 Void
6a The SS waits for 5 seconds to guarantee that the UE is in
service.
8 PAGING RESPONSE "Ciphering key sequence number" shall be the same as
the value that was sent in the last AUTHENTICATION
REQUEST message (=CKSN2).
10 Void

None.
1) At step 4 the UE shall send an AUTHENTICATION RESPONSE message with the RES information field set to
the same value as the XRES calculated by the SS.
2) At step 8 the UE shall indicate in a PAGING RESPONSE message the ciphering key sequence number which
was allocated to it through the authentication procedure.
9.2.2 Authentication rejected by the network
9.2.2.1 Definition
1) After reception of an AUTHENTICATION REJ ECT message the UE shall:
1.1 not perform normal location updating;
1.2 not perform periodic location updating;
1.3 not respond to paging with TMSI;
1.4 reject any request from CM entity for MM connection except for emergency call;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1702
1.5 not perform IMSI detach if deactivated.
2) After reception of an AUTHENTICATION REJ ECT message the UE, if it supports speech, shall accept a
request for an emergency call by sending a RRC CONNECTION REQUEST message with the establishment
cause set to "emergency call" and include an IMEI as mobile identity in the CM SERVICE REQUEST message.
3) After reception of an AUTHENTICATION REJ ECT message the UE shall delete the stored LAI, CKSN and
TMSI.
Reference(s)
TS 24.008 clause 4.3.2.5.
1) To check that ,after reception of an AUTHENTICATION REJ ECT message, the UE:
1.1 does not perform normal location updating;
1.2 does not perform periodic location updating;
1.3 does not respond to paging with TMSI;
1.4 rejects any request from CM entity for MM connection except for emergency call;
1.5 does not perform IMSI detach if deactivated.
2) To check that, after reception of an AUTHENTICATION REJ ECT message the UE, if it supports speech,
accepts a request for an emergency call by sending a RRC CONNECTION REQUEST message with the
establishment cause set to "emergency call" and includes an IMEI as mobile identity in the CM SERVICE
REQUEST message.
3) To check that, after reception of an AUTHENTICATION REJ ECT message and after having been deactivated
and reactivated, the UE performs location updating using its IMSI as mobile identity and indicates deleted LAI
and CKSN.
Initial conditions
- System Simulator:
- two cells: A and B, belonging to different location areas a and b;
- IMSI attach/detach is allowed in both cells;
- the T3212 time-out value is 1/10 hour in both cells.
- User Equipment:
- the UE has valid TMSI, CKSN (CKSN2) , CK and IK. It is "idle updated" on cell B.
USIM removal possible while UE is powered Yes/No.
Switch off on button Yes/No.
Support of speech Yes/No.
Test procedure
The SS rejects an authentication. The RRC CONNECTION is released. The SS checks that the UE has entered the state
MM IDLE substate NO IMSI, i.e. does not perform normal location updating, does not perform periodic updating, does
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1703
not respond to paging, rejects any requests from CM entities except emergency calls and does not perform IMSI detach
if USIM detachment is performed, switch off is performed, or the power is removed, depending on the UE (see
ICS/IXIT).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1704
Expected sequence
UE SS
The following messages are sent and shall be received on cell B
Establishment Cause: Terminating Conversational Call..
2 PAGING RESPONSE "Ciphering key sequence number" shall be the same as
the value that was sent in the last AUTHENTICATION
REQUEST message (=CKSN2).
3 AUTHENTICATION REQUEST
4 AUTHENTICATION RESPONSE
5 AUTHENTICATION REJ ECT
7 Void
8 PAGING TYPE 1 The UE is paged in cell B. "UE identity " IE contains
TMSI. Paging Cause: Terminating Conversational Call.
9 UE The UE shall ignore this message. This is verified during
3 s.
10 SS The SS waits for at least for 15 s.
11 UE A MO CM connection is attempted.
12 UE The UE shall not initiate an RRC connection
establishment on cell A or cell B. This is checked during
3 s.
13 UE If the UE supports speech (see ICS), an emergency call
is attempted.
14 SS The SS checks that the IE "Establishment cause" in the
to "Emergency call".
15 Void
16 Void
17 CM SERVICE REQUEST "CM service type": Emergency call establishment.
"Mobile identity": type of identity is set to IMEI.
18 CM SERVICE ACCEPT
19 EMERGENCY SETUP
20 RELEASE COMPLETE "Cause" =unassigned number.
22 Void
The following messages are sent and shall be received on cell A.
Set the cell type of cell B to the "non-suitable cell".
(see note)
24 UE The UE performs cell reselection according to procedure
as specified in (this however is not checked until step 29).
The UE shall not initiate an RRC connection
establishment on cell A or on cell B.
25 SS The SS waits at least 7 minutes for a possible periodic
updating.
27 UE If possible (see ICS) USIM detachment is performed.
Otherwise if possible (see ICS) switch off is performed.
Otherwise the power is removed.
establishment on cell A or on cell B. This is checked
during 3 s.
29 UE Depending on what has been performed in step 26 the
UE is brought back to operation.
30 SS The SS checks that the IE "Establishment cause" in the
to "Registration".
31 Void
32 Void
REQUEST
"location updating type" =normal, "CKSN" =no key
available, "Mobile Identity" =IMSI, "LAI" =deleted LAI
(the MCC and MNC hold the previous values, the LAC is
coded FFFE).
34 AUTHENTICATION REQUEST "CKSN" =CKSN1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1705
UE SS
36 LOCATION UPDATING ACCEPT "Mobile Identity" =TMSI.
COMPLETE

39 Void

None.
1)
1.1 At step 24 the UE shall not send any RRC CONNECTION REQUEST on cell A or on cell B.
1.3 At step 9 the UE shall not respond to paging.
2) At step 14 the UE shall send a RRC CONNECTION REQUEST message with the establishment cause set to
"emergency call"; and at step 17 the UE shall send a CM SERVICE REQUEST message with the "CM service
type" set to "Emergency call establishment".
3) At step 33 the UE shall perform location updating using its IMSI as mobile identity and indicates deleted LAI
and CKSN.
9.2.3 Authentication rejected by the UE (MAC code failure)
9.2.3.1 Definition
Following a UMTS authentication challenge, the UE may reject the core network, on the grounds of an incorrect AUTN
parameter (see TS 33.102).
If the UE considers the MAC code (supplied by the core network in the AUTN parameter) to be invalid, it shall send an
AUTHENTICATION FAILURE message to the network, with the reject cause 'MAC failure'.
1) The UE shall respond to an AUTHENTICATION REQUEST message, with a MAC code failure in the AUTN
parameter, by sending an AUTHENTICATION FAILURE message with the reject cause 'MAC failure' and start
timer T3214. When an AUTHENTICATION REQUEST message containing an invalid MAC has been received
by the UE from the network, the UE shall stop any of the retransmission timers that are running (i.e. T3210,
T3220 or T3230).
2) Upon receipt of an AUTHENTICATION FAILURE message from the UE, with reject cause 'MAC failure' the
network may initiate the identification procedure. Upon reception of an IDENTITY REQUEST message, the UE
shall identify itself by sending an IDENTITY RESPONSE message including the IMSI to the network. The
network may then check that the TMSI originally used in the authentication challenge corresponded to the
correct IMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1706
3) If the TMSI/IMSI mapping in the network was incorrect, the network should respond by sending a new
AUTHENTICATION REQUEST message to the UE. Upon receiving the second AUTHENTICATION
REQUEST message from the network, the UE shall stop the timer T3214, if running, and then process the
challenge information as normal. Upon successfully validating the network (an AUTHENTICATION
REQUEST that contains a valid MAC in the AUTN parameter is received), the UE shall send the
AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3210,
T3220 or T3230) , if they were running and stopped when the UE received the first AUTHENTICATION
REQUEST message containing an incorrect MAC.
Reference(s)
TS 24.008 clauses 4.3.2.5.1 and 4.3.2.6 (c)
1) To check that a UE shall correctly respond to an AUTHENTICATION REQUEST message, with a MAC code
failure in the AUTN parameter, by sending an AUTHENTICATION FAILURE message with the reject cause
'MAC failure'.
2) To check that upon reception of an IDENTITY REQUEST message, requesting for IMSI, the UE identifies itself
by sending an IDENTITY RESPONSE message including the IMSI to the network.
3) To check that upon receiving the second AUTHENTICATION REQUEST message from the network, the UE
shall stop the timer T3214, if running, and then process the challenge information as normal. To check that upon
successfully validating the network (an AUTHENTICATION REQUEST that contains a valid MAC is
received), the UE sends the AUTHENTICATION RESPONSE message to the network.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test procedure
The UE rejects an authentication. The AUTHENTICATION FAILURE is sent by UE. Upon receipt of the
AUTHENTICATION FAILURE message the SS initiates identification procedure. The UE responds to the SS by
sending IDENTITY RESPONSE message. The SS sends AUTHENTICATION REQUEST message with correct
AUTN parameter.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1707
Expected sequence
UE SS
3 AUTHENTICATION REQUEST With AUTN parameter having a MAC value different from
what is calculated in 34.108 clause 8.1.2.1 step 4.
4 AUTHENTICATION FAILURE With reject cause "MAC failure"
5 IDENTITY REQUEST With identity type IMSI
6 IDENTITY RESPONSE With IMSI in Mobile Identity IE
7 AUTHENTICATION REQUEST With the AUTN parameter having a valid MAC code, see
34.108 clause 8.1.2.1 step 4.
8 AUTHENTICATION RESPONSE Authentication Response Parameter IE (RES) shall be bit
exact with the value as produced by the authentication
algorithm.
COMPLETE

None.
1) At step 4 the UE shall send AUTHENTICATION FAILURE message with reject cause set to "MAC failure".
2) At step 6 the UE shall send an IDENTITY RESPONSE message including the IMSI.
3) At step 8 the UE shall send an AUTHENTICATION RESPONSE message.
9.2.4 Authentication rejected by the UE (SQN failure)
9.2.4.1 Definition
Following a UMTS authentication challenge, the UE may reject the core network, on the grounds of an incorrect AUTN
parameter (see TS 33.102).
If the UE considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it shall send an
AUTHENTICATION FAILURE message to the network, with the reject cause 'Synch failure' and a re-synchronisation
token AUTS provided by the USIM (see TS 33.102).
1) The UE shall respond to an AUTHENTICATION REQUEST message, with an SQN failure in the AUTN
parameter, by sending an AUTHENTICATION FAILURE message with the reject cause 'Synch failure' and start
the timer T3216 and stop any of the retransmission timers that are running (i.e. T3210, T3220 or T3230). Upon
receipt of an AUTHENTICATION FAILURE message from the UE with the reject cause 'synch failure,' the
network shall use the returned AUTS parameter from the authentication failure parameter IE in the
AUTHENTICATION FAILURE message, to re-synchronise.
2) Upon successfully validating the network (a second AUTHENTICATION REQUEST is received which contains
a valid SQN in the AUTN parameter) while T3216 is running, the UE shall send the AUTHENTICATION
RESPONSE message to the network and shall start any retransmission timers (e.g. T3210, T3220 or T3230), if
they were running and stopped when the UE received the first AUTHENTICATION REQUEST message
containing an invalid SQN.
Reference(s)
TS 24.008 clause 4.3.2.5.1, 4.3.2.6 (d)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1708
1) To check that a UE shall correctly respond to an AUTHENTICATION REQUEST message, with an SQN failure
in the AUTN parameter, by sending an AUTHENTICATION FAILURE message with the reject cause 'Synch
failure'.
2) To check that upon successfully validating the network (a second AUTHENTICATION REQUEST is received
which contains a valid SQN) while T3216 is running, the UE shall send the AUTHENTICATION RESPONSE
message to the network.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test procedure
The SS sends an AUTHENTICATION REQUEST having an invalid SQN code (i.e. uses the predefined AMF
RESYNCH

value to trigger the SQN re-synchronisation procedure, see TS 34.108 clause 8.1.2.2) to the UE. The SS verifies that the
UE rejects the authentication.
The SS sends a second AUTHENTICATION REQUEST with a valid SQN code (i.e. uses an AMF value different from
AMF
RESYNCH
value, see TS 34.108 clause 8.1.2.2). The SS checks that the UE accepts the authentication request.
Expected sequence
UE SS
1 Mobile terminated
establishment of Radio
Resource Connection
Establishment Cause: Terminating Conversational
Call.
3 AUTHENTICATION REQUEST with the AMF information field set to AMFRESYNCH
value to trigger SQN re-synchronisation procedure in
test USIM, see TS 34.108 clause 8.1.2.2.
4 AUTHENTICATION FAILURE including the AUTS parameter and with the reject
cause set to 'Synch failure'
5 AUTHENTICATION REQUEST with the AMF information field set to value different
from AMFRESYNCH value to cause test USIM to treat
SQN value as valid, see TS 34.108 clause 8.1.2.2.
6 AUTHENTICATION
RESPONSE
"Auth. parameter RES" IE shall be bit exact with the
value as produced by the authentication algorithm.
COMPLETE

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1709
1) At step 4 the UE shall reject an authentication and the AUTHENTICATION FAILURE is sent to SS with reject
cause "Synch failure".
2) At step 6 the UE shall send an AUTHENTICATION RESPONSE message with the RES information field set to
the same value as the XRES calculated by SS.
9.2.5 Authentication rejected by the UE / fraudulent network
9.2.5.1 Definition
R99 and REL-4:
1. It can be assumed that the source of the authentication challenge is not genuine (authentication not accepted by
the UE) if any of the following occur:
- After sending the AUTHENTICATION FAILURE message with the reject cause 'MAC failure' the timer
T3214 expires;
- Upon receipt of the second AUTHENTICATION REQUEST while T3214 is running and the MAC value
cannot be resolved.
When it has been deemed by the UE that the source of the authentication challenge is not genuine (i.e.
authentication not accepted by the UE), the UE shall behave as described in 3GPP TS 24.008 clause
4.3.2.6.1.
2. In addition to the cases specified in 3GPP TS 24.008 subclause 4.3.2.6, the UE may deem that the network has
failed the authentication check after any combination of three consecutive authentication failures, regardless
whether MAC failure, invalid SQN, or GSM authentication unacceptable was diagnosed. The authentication
failures shall be considered as consecutive only, if the authentication challenges causing the second and third
authentication failure are received by the UE, while the timer T3214 or T3216 started after the previous
authentication failure is running.
If the UE deems that the network has failed the authentication check, then it shall request RR or RRC to release
the RR connection and the PS signalling connection, if any, and bar the active cell or cells (see 3GPP TS 25.331
and 3GPP TS 04.18).
Reference(s)
3GPP TS 24.008 clauses 4.3.2.6 (c) and 4.3.2.6.1.
REL-5 and later releases:
- after sending the AUTHENTICATION FAILURE message with the reject cause "MAC failure" the timer
T3214 expires;
- the UE detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM
authentication unacceptable", during three consecutive authentication challenges. The authentication
challenges shall be considered as consecutive only, if the authentication challenges causing the second and
third authentication failure are received by the UE, while the timer T3214 or T3216 started after the previous
When it has been deemed by the UE that the source of the authentication challenge is not genuine (i.e.
authentication not accepted by the UE), the UE shall behave as described in 3GPP TS 24.008 subclause
4.3.2.6.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1710
2. If the UE deems that the network has failed the authentication check, then it shall request RR or RRC to release
and 3GPP TS 44.018).
Reference(s)
3GPP TS 24.008 clauses 4.3.2.6 (c) and 4.3.2.6.1.
R99 and REL-4:
To test UE treating a cell as barred:
1. when the UE receives the second or third AUTHENTICATION REQUEST message with invalid MAC value
during the T3214 is running.
2. when the timer T3214 has expired.
1. when the UE receives the third AUTHENTICATION REQUEST message with invalid MAC value during
the T3214 is running.
Initial conditions
- System Simulator:
- two cells: A and B, belonging to different location areas a and b.
- User Equipment:
- the UE has a valid TMSI. It is "idle updated" on cell A.
None.
Test procedure
A location updating procedure is initiated in cell B. The SS sends an AUTHENTICATION REQUEST message with
invalid MAC value and the UE responds with an AUTHENTICATION FAILURE message. The SS resends an
AUTHENTICATION REQUEST message with invalid MAC value.
For R99 and REL-4: The SS waits 30 seconds. If the UE sends an AUTHENTICATION FAILURE message during this
time then the SS repeats the authentication procedure a third time and then waits 30 seconds. The UE moves into idle
mode and do not make any access attempt on cell B.
For REL-5 and later release: The SS repeats a third time the authentication procedure, again with invalid MAC value in
its AUTHENTICATION REQUEST message. The UE moves into idle mode and do not make any access attempt on
cell B.
It is checked that the UE shall not attempt to access the network in cell B.
A location updating procedure is initiated in cell A. The SS sends an AUTHENTICATION REQUEST message with
invalid MAC value and the UE responds with an AUTHENTICATION FAILURE message. The SS waits T3214
expiry.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1711
It is checked that the UE shall not attempt to access the network in cell A.
Expected sequence
UE SS
The following messages shall be sent and received on
Cell B.
1 SS Set the cell type of cell B to the Serving cell.
Set the cell type of cell A to the non-suitable cell.
(see note)
2 SS The SS verifies that the IE "Establishment cause" in the
to Registration.
3 LOCATION UPDATING
REQUEST

4 AUTHENTICATION REQUEST with AUTN parameter having a MAC value different from
5 AUTHENTICATION FAILURE with reject cause "MAC failure"
R99 and REL-4: In case message is not received within
30s then the SS should continue from step 10.
R99 and REL-4: Optional step
9 SS The SS verifies that the UE does not attempt to access
the network for 30s.
Cell A
(see note)
to Registration.
REQUEST

15 SS The SS waits T3214 expiry.
16 SS The SS verifies that the UE does not attempt to access
the network for 30s.

None.
For R99 and REL-4 UE:
Alternative 1:
- After step 6, when the UE have received the second AUTHENTICATION REQUEST message with invalid
MAC value, the UE shall not attempt to access the network in cell B.
Alternative 2:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1712
- After step6, when the UE have received the second AUTHENTICATION REQUEST message with invalid
MAC value while the timer T3214 is running, the UE shall send an AUTHENTICATION FAILURE
message with reject cause "MAC failure" to the SS; and
- After step 8, when the UE have received the third AUTHENTICATION REQUEST message with invalid
For REL-5 UE:
- After step 6, when the UE have received the second AUTHENTICATION REQUEST message with invalid
MAC value while the timer T3214 is running, the UE shall send an AUTHENTICATION FAILURE
message with reject cause "MAC failure" to the SS; and
- After step 8, when the UE have received the third AUTHENTICATION REQUEST message with invalid
After step 15, when the timer T3214 has expired, the UE shall not attempt to access the network in cell A.
9.3 Identification
The purpose of this procedure is to check that the UE gives its identity as requested by the network. If this procedure
does not work, it will not be possible for the network to rely on the identity claimed by the UE.
9.3.1 General Identification
9.3.1.1 Definition
1) When requested by the network the UE shall send its IMSI.
2) When requested by the network the UE shall send the TMSI which it was previously allocated.
3) When requested by the network the UE shall send its IMEI as stored in the UE.
4) When requested by the network the UE shall send its IMEISV as stored in the UE.
Reference(s)
TS 24.008 clause 4.3.3.
1) To verify that the UE sends identity information as requested by the system in the following cases: IMSI and
TMSI are requested in non-security mode, IMEI is requested in security mode.
2) To verify that the UE sends its IMEI, when requested to do so, in non- security mode.
3) To verify that the UE sends its IMEISV, when requested to do so, in non- security mode.
9.3.1.4.1 Identification
Initial conditions
- System Simulator:
- 1 cell, default values.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1713
- User Equipment:
- the UE has a valid TMSI. It is "idle updated" on the cell.
IMEI of the UE.
IMEISV of the UE.
Test Procedure
The SS requests identity information from the UE:
- IMSI in non security mode;
- allocated TMSI in non security mode;
- IMEI in non security mode;
- IMEISV in non security mode;
- IMEI in security mode.
Expected sequence
UE SS
2 PAGING RESPONSE
3 IDENTITY REQUEST "Identity type" IE is IMSI.
4 IDENTITY RESPONSE "Mobile identity" IE specifies the IMSI of the UE.
5 IDENTITY REQUEST "Identity type" IE is TMSI.
6 IDENTITY RESPONSE "Mobile identity" IE specifies the allocated TMSI of the
UE.
6a IDENTITY REQUEST "Identity type" IE is IMEI.
6b IDENTITY RESPONSE "Mobile identity" IE specifies the IMEI of the UE.
6c IDENTITY REQUEST "Identity type" IE is IMEISV.
6d IDENTITY RESPONSE "Mobile identity" IE specifies the IMEISV of the UE.
7 SS The SS starts ciphering and integrity protection.
8 Void
9 IDENTITY REQUEST "Identity type" IE is IMEI.
10 IDENTITY RESPONSE "Mobile identity" IE specifies the IMEI stored in the UE.
12 Void

None.
1) At step 4 the UE shall send its IMSI.
2) At step 6 the UE shall send the TMSI which it was previously allocated.
3) At step 6b and step 10 the UE shall send its IMEI as stored in the UE.
4) At step 6 the UE shall send its IMEISV as stored in the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1714
9.3.2 Handling of IMSI shorter than the maximum length
9.3.2.1 Definition
The UE shall be capable of handling an IMSI that is not of the maximum length.
Reference(s)
TS 24.008 clause 10.5.1.4.
To check that the UE behaves correctly when activated with an IMSI of length less than the maximum length.
In this condition, the UE shall:
- perform location updating;
- answer to paging with IMSI;
- give the correct IMSI when asked by an IDENTITY REQUEST;
- attempt CM connection establishment when requested to;
- attempt IMSI detach when needed;
- erase its TMSI when the IMSI is sent by the network in a LOCATION UPDATING ACCEPT or a TMSI
REALLOCATION COMMAND message.
Initial conditions
- System Simulator:
- 1 cell, default values;
- IMSI attach/detach bit set to "1".
- User Equipment:
- the UE has no valid TMSI;
- it is "idle updated";
- the IMSI has the value 001011234.
On/Off switch - Yes/No.
Foreseen final state of UE
The UE has no valid TMSI. It is in "idle, updated".
Test Procedure
The UE is paged with its IMSI. The UE shall answer to paging and include the correct IMSI in the PAGING
RESPONSE message. During call establishment, the SS asks for the IMSI of the UE. The UE shall answer by an
IDENTITY RESPONSE message including the correct IMSI. During the active phase of the call, the SS modifies the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1715
scrambling code of DL DPCH. The UE performs call re-establishment. The TMSI REALLOCATION COMMAND
including a TMSI is sent to the UE. The UE acknowledges this message. The call is released.
The UE is paged with its TMSI. The UE shall answer to paging and includes its TMSI in the PAGING RESPONSE
message. During call establishment, the SS sends a TMSI REALLOCATION COMMAND including the IMSI to the
UE. The UE shall acknowledge this message. The UE shall erase its TMSI. The call is released.
The UE is switched off or has its power source removed. The UE performs IMSI detach. The UE shall include the
correct IMSI in the IMSI DETACH INDICATION message.
The UE is switched on or powered on. The UE performs IMSI attach. The UE shall include the correct IMSI in the
LOCATION UPDATING REQUEST message. A TMSI is allocated to the UE.
The LAC of the cell is changed. The UE performs location updating. The SS includes the IMSI in the LOCATION
UPDATING ACCEPT message.
A mobile originated CM connection is attempted. The UE shall include the correct IMSI in the CM SERVICE
REQUEST message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1716
Expected sequence
UE SS
"Initial UE identity" IE contains IMSI of UE.
Establishment cause: Terminating Conversational Call.
2 PAGING RESPONSE "mobile identity" contains the IMSI of the UE.
3 IDENTITY REQUEST "identity type" IE is IMSI.
4 IDENTITY RESPONSE "mobile identity" IE contains the IMSI of the UE.
5 The call is established using the sequence of the generic
terminating call set-up procedure.
6 The SS modifies the scrambling code of DL DPCH for
generating lower layer failure.
Cell update procedure for radio link failure is performed
6a Void
6b Void
6c Void
7 Void
8 Void
9 Void
10 Void
10d Void
COMMAND
"mobile identity" contains a TMSI.
COMPLETE

14 Void
"Initial UE identity" IE contains TMSI of UE.
Establishment cause: Terminating Conversational Call.
16 PAGING RESPONSE "mobile identity" contains the TMSI of the UE.
18a SS The SS starts integrity protection.
18b Void
COMMAND
"mobile identity" contains a IMSI of UE.
COMPLETE

22 Void
23 UE If possible (see ICS) the UE is switched off, otherwise the
UE has its power source removed.
24 SS If the UE was switched off it performs IMSI detach.
The SS verifies that the IE "Establishment cause" in the
received RRC Connection REQUEST message is set to
"Detach".
25 Void
26 Void
27 IMSI DETACH INDICATION "mobile identity" contains IMSI of UE.
29 Void
30 UE The UE is switched on or has power restored.
31 Void
32 Void
33 Void
REQUEST
"mobile identity" contains IMSI of UE.
35 LOCATION UPDATING ACCEPT "mobile identity" contains a TMSI.
COMPLETE

38 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1717
UE SS
39 SS The SS changes the LAC of the cell.
40 SS The SS verifies that the UE sends RRC Connection
REQUEST message within 35s of the LAC being
changed.
41 Void
42 Void
REQUEST
"mobile identity" contains TMSI of the UE.
44 LOCATION UPDATING ACCEPT "mobile identity" contains IMSI of the UE.
46 Void
47 UE a mobile originated CM connection is attempted.
48 Void
49 Void
50 Void
51 CM SERVICE REQUEST "mobile identity" contains IMSI of the UE.
53 Void

None.
At step 2 the UE shall answer to paging with IMSI.
At step 4 the UE shall answer to the SS with the correct IMSI in an IDENTITY RESPONSE message.
At step 19 the IMSI is sent by the network in a TMSI REALLOCATION COMMAND message, at step 27 the UE shall
attempt IMSI detach.
At step 34 the UE shall perform location updating.
At step 44 the IMSI is sent by the network in a LOCATION UPDATING ACCEPT message, at step 51 the UE shall
attempt CM connection establishment and include the correct IMSI in the CM SERVICE REQUEST message.
9.4 Location updating
This procedure is used to register the UE in the network. If it is not performed correctly, no call can be established.
9.4.1 Location updating / accepted
9.4.1.1 Definition
1.
1.1 if the network accepts a location updating from the UE and reallocates a TMSI in the LOCATION
UPDATING ACCEPT message the UE shall acknowledge the reception of the new TMSI;
1.2 the UE shall answer to paging with this TMSI and include it in a PAGING RESPONSE message.
2 If the network accepts a location updating from the UE and the LOCATION UPDATING ACCEPT message
contains neither TMSI nor IMSI, the UE shall answer to paging when addressed with the last allocated TMSI
and include it in the PAGING RESPONSE message.
3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1718
3.1 if the network accepts a location updating from the UE by use of a LOCATION UPDATING ACCEPT
message containing the IMSI of the UE, the UE shall not answer paging with the last allocated TMSI;
3.2 the UE shall still answer paging with IMSI.
Reference(s)
TS 24.008 clause 4.4.4.6.
1) To test the behaviour of the UE if the network accepts the location updating of the UE.
For the network response three different cases are identified:
1.1) TMSI is allocated;
1.2) location updating accept contains neither TMSI nor IMSI;
1.3) location updating accept contains IMSI.
Initial conditions:
- System Simulator:
- two cells, A and B, belonging to different location areas with location area identification a and b of the same
PLMN;
- User Equipment:
- the UE has a valid TMSI (=TMSI1) and CKSN (=CKSN1). It is "idle updated" on cell A.
None.
Test Procedure
The UE is made to select cell B. A normal location updating with TMSI reallocation is performed in cell B. The RRC
CONNECTION is released. The SS checks, by paging, that the UE has stored the newly allocated TMSI. The RRC
CONNECTION is released. The UE is made to select cell A. A normal location updating is performed in cell A. The
LOCATION UPDATING ACCEPT message contains neither IMSI nor TMSI. The SS checks, by paging, that the UE
has kept the old TMSI. The RRC CONNECTION is released. The UE is made to select cell B. A normal location
updating is performed in cell B. The LOCATION UPDATING ACCEPT message contains an IMSI. The SS checks, by
paging, that the UE has deleted its TMSI and responds to paging with IMSI.
Expected sequence
UE SS
1 SS Set the cell type of cell B to the "Serving cell".
Set the cell type of cell A to the "non-suitable cell".
(see note)
to: Registration.
3 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1719
UE SS
4 Void
5 LOCATION UPDATING
REQUEST
"location updating type" =normal, "CKSN" =CKSN1,
"location area identification" =a, "mobile station
classmark 1" as given by the ICS and "mobile identity" =
TMSI1. The MM message is included in the RRC
messagge INITIAL DIRECT TRANSFER with the CN
domain identity set to CS domain.
5b Void
6 LOCATION UPDATING ACCEPT "Mobile identity" =new TMSI (=TMSI2), LAI =b.
7 TMSI REALLOCATION
COMPLETE

8 SS
9 Void
9a SS waits 5 seconds to guarantee that the UE is in
service.
"Initial UE identity" IE contains the new TMSI (=TMSI2)
and the new LAI (=b).
11 PAGING RESPONSE "Mobile identity" IE contains the new TMSI (=TMSI2).
12 SS The SS releases the RRC Connection.
13 Void
(see note)
received RRC Connection REQUEST message is set to
"Registration".
16 Void
17 Void
18a LOCATION UPDATING
REQUEST
"location area identification" =b, "mobile station
TMSI2.
18b SS The SS starts integrity protection.
18c Void
19 LOCATION UPDATING ACCEPT "Mobile identity" IE not included. LAI =a
20 SS
21 Void The SS releases the RRC connection and waits 5 s to
guarantee that the UE is in service.
"Initial UE identity" IE contains the TMSI (=TMSI2) and
LAI (=a).
23 PAGING RESPONSE "Mobile identity" IE contains the TMSI (=TMSI2).
25 Void
(see note)
received RRC CONNECTION REQUEST is set to
"Registration".
28 Void
29 Void
30a LOCATION UPDATING
REQUEST
"location area identification" =a, "mobile station
TMSI2.
30c Void
31 LOCATION UPDATING ACCEPT "Mobile identity" IE contains IMSI and LAI (=b).
32 SS
33 Void The SS waits 5 s to guarantee that the UE is in service.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1720
UE SS
34 PAGING TYPE 1 "UE identity" IE contains the old TMSI (=TMSI2).
Paging Cause: Terminating Conversational Call.
35 UE The UE shall ignore this message. This is checked during
5 s.
"Initial UE identity" IE contains the IMSI.
37 PAGING RESPONSE "Mobile identity" IE contains the IMSI.
39 Void

None.
At step 7 the UE shall acknowledge the reception of the new TMSI (TMSI2).
At step 11 the UE shall answer to paging with this TMSI (TMSI2).
At step 23 the UE shall answer to paging with the last allocated TMSI (TMSI2).
At step 35 the UE shall not answer paging with the last allocated TMSI, but at step 37 the UE shall still answer paging
with IMSI.
9.4.2 Location updating / rejected
9.4.2.1 Location updating / rejected / IMSI invalid
1) If the network rejects a location updating from the UE with the cause "IMSI unknown in HLR", "Illegal MS" or
"Illegal ME" the UE shall:
1.1 not perform normal location updating;
1.2 not perform periodic location updating;
1.3 not respond to paging with IMSI;
1.5 reject any request from CM entity for MM connection other than for emergency call;
1.6 not perform IMSI detach if it is switched off or has its power source removed.
"Illegal ME" the UE, if it supports speech, shall accept a request for an emergency call by sending a RRC
CONNECTION Request message with the establishment cause set to "emergency call" and include an IMEI as
mobile identity in the CM SERVICE REQUEST message.
"Illegal ME" the UE shall delete the stored LAI, CKSN and TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1721
Reference(s)
TS 24.008 clause 4.4.4.7.
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "IMSI unknown in
HLR", "illegal MS" or "Illegal ME".
Initial conditions
- System Simulator:
- two cells: A and B, belonging to different location areas of the same PLMN;
- User Equipment:
- the UE has valid TMSI(=TMSI1), CKSN(=CKSN1) and CK, IK. It is "idle updated" on cell A.
USIM removal possible while the UE is powered Yes/No.
Support for speech Yes/No.
Test Procedure
The SS rejects a normal location updating with the cause value "IMSI unknown in HLR". The RRC CONNECTION is
released. The SS checks that the UE has entered the state MM IDLE and the substate NO IMSI, i.e. does not perform
normal location updating when a new cell of the same or another PLMN is entered, does not perform periodic updating,
does not respond to paging, rejects any requests from CM entities except emergency calls, does not perform IMSI
detach if it is switched off or has its power source removed and deletes the stored LAI, CKSN and TMSI.
The test is repeated with cause value "Illegal MS" and with cause value "Illegal ME".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1722
Expected sequence
The sequence is executed for execution counter k =1, 2, 3.
UE SS
The following messages are sent and shall be received
on cell B.
(see note)
"Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
"LAI" =a, "Mobile Identity" =TMSI1
6 LOCATION UPDATING REJ ECT "Reject cause" IE is "IMSI unknown in HLR" for k =1,
"Illegal MS" for k =2, "Illegal ME" for k =3.
7 SS The SS releases the RRC Connection.
8 Void
on cell A.
(see note)
updating.
13 PAGING TYPE 1 The UE is paged in cell A. "UE identity" IE contains IMSI.
3 s.
15 PAGING TYPE 1 The UE is paged in cell A. "UE identity" IE contains TMSI.
3 s.
during 3 s.
19 UE If the UE supports speech (see ICS), it is made to
perform an emergency call.
received RRC CONNECTION REQUESTis set to
"Emergency call".
This message is sent in cell A.
21 Void
22 Void
"Mobile identity": type of identity is set to IMEI.
25 EMERGENCY SETUP
28 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1723
UE SS
during 3 s.
"Registration".
33 Void
34 Void
REQUEST
available, "mobile station classmark 1" as given by the
ICS, "Mobile Identity" =IMSI, "LAI" =deleted LAI (the
MCC and MNC hold the previous values, the LAC is
coded FFFE).
COMPLETE

41 Void

None.
1) 1.1 At step 10 the UE shall not perform normal location updating.
1.2 At step 12 the UE shall not perform periodic location updating.
1.3 At step 14 the UE shall not respond to paging with IMSI.
1.4 At step 16 the UE shall not respond to paging with TMSI.
1.5 At step 18 the UE shall reject a MO CM connection.
1.6 At step 30 the UE shall not initiate an RRC connection establishment on cell A or on cell B.
2) At step 20 the UE shall accept a request for an emergency call with the establishment cause set to "Emergency
call".
3) At step 35 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to
its IMSI, CKSN IE set to "no key is available" and the LAI IE set to "deleted LAI" on cell A.
9.4.2.2 Location updating / rejected / PLMN not allowed
1) If the network reject a location updating from the UE with the cause "PLMN not allowed" the UE shall:
1.1 not perform periodic updating;
1.2 not perform IMSI detach when switched off;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1724
1.3 not perform IMSI attach when switched on in the same location area;
1.4 not perform normal location updating when in the same PLMN and when that PLMN is not selected
manually;
1.5 reject any request from CM entity for MM connection other than for emergency call.
2) If the network rejects a location updating from the UE with the cause "PLMN not allowed" the UE shall:
2.1 perform normal location updating when a new PLMN is entered;
2.2 accept a request for an emergency call, if it supports speech, by sending a RRC CONNECTION REQUEST
message with the establishment cause set to "emergency call".
3) If the network rejects a location updating from the UE with the cause "PLMN not allowed" and if after that the
PLMN from which this rejection was received, is manually selected, the UE shall perform a normal location
updating procedure.
4) If the network rejects a location updating from the UE with the cause "PLMN not allowed" the UE shall delete
the stored LAI, CKSN and TMSI.
Reference(s)
TS 24.008 clause 4.4.4.7.
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "PLMN not
allowed".
9.4.2.2.4.1 Location updating / rejected / PLMN not allowed / test 1
Initial conditions
- System Simulator:
- one cell: C, belonging to PLMN1;
- two cells: A and B, belonging to different location areas a and b and belonging to PLMN2. PLMN2 is
different from HPLMN and from PLMN1;
- IMSI attach/detach is allowed in cells A and B but not in cell C;
- the T3212 time-out value is 1/10 hour in cells A and B.
NB: i) Cell C will be mapped to Cell 1 as found in TS 34.108 clause 6.1.4.1.
ii) Cell A and B will be mapped to Cell 4 and 5 respectively, as found in TS 34.108 clause 6.1.4.1.
- User Equipment:
- the UE has a valid TMSI(=TMSI1) and CKSN(=CKSN1). It is "idle updated" on cell C;
- the UE is in manual mode for PLMN selection.
USIM removal possible while the UE is powered Yes/No.
The UE is automatically in automatic mode after switch on Yes/No.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1725
Test Procedure
The SS rejects a normal location updating with the cause value "PLMN not allowed". The RRC CONNECTION is
released. The SS checks that the UE does not perform periodic updating, does not perform IMSI detach, does not
perform IMSI attach if activated in the same location area, rejects any request for CM connection establishment other
than emergency call, accepts a request for an emergency call, performs normal location updating only when a new
PLMN is entered and deletes the stored LAI, CKSN and TMSI.
Expected sequence
UE SS
on cell B.
1 UE The UE is switched off (or power is removed).
Set the cell type of cell A to the "Suitable neighbour cell".
Set the cell type of cell C to the "non-suitable cell".
(see note)
3 UE The UE is switched on. (or power is reapplied) If
necessary the UE is put in manual selection mode. The
UE shall offer the new PLMN as available to the user.
The PLMN is manually selected.
to "Registration".
5 Void
6 Void
7 LOCATION UPDATING
REQUEST
"LAI" =c, "Mobile Identity" =TMSI1
8 LOCATION UPDATING REJ ECT "Reject cause" =PLMN not allowed.
10 Void
11 SS The SS waits for a possible periodic updating for 7
minutes.
during 3 s.
UE is brought back to operation. The UE is not made to
select PLMN 2.
establishment. This is checked during 3 s.
The following message are sent and shall be received on
cell A.
Set the cell type of cell B to the "Suitable neighbour cell".
(see note)
18 UE No access to the network shall be registered by the SS
within one minute.
19 UE If the UE supports speech (see ICS) it is made to perform
an emergency.
to "Emergency Call".
21 Void
22 Void
23 CM SERVICE REQUEST "CM service type" =Emergency call establishment.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1726
UE SS
25 EMERGENCY SETUP
26 RELEASE COMPLETE Cause IE: "unassigned number".
28 Void
establishment. This is checked during 3 s.
on cell C.
31 UE The UE is switched off.
32 SS Set the cell type of cell C to the "Serving cell".
(see note)
33 UE The UE is switched on. If necessary the UE is placed into
the automatic mode.
"Registration".
35 Void
36 Void
REQUEST
available, "LAI" =deleted LAI (the MCC and MNC hold
the values of PLMN1, the LAC is coded FFFE) "mobile
identity" =IMSI.
38 LOCATION UPDATING ACCEPT "Mobile identity" =TMSI.
COMPLETE

41 Void
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS
34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only".

Specific message contents:
None.
9.4.2.2.4.2 Location updating / rejected / PLMN not allowed / test 2
Initial conditions
- System Simulator:
- one cell C, belonging to PLMN1;
- two cells A and B, belonging to different location areas a and b and belonging to PLMN2. PLMN2 is
different from HPLMN;
- IMSI attach/detach is allowed in cells A and B but not in cell C;
- the T3212 time-out value is 1/10 hour in cells A and B.
- User Equipment:
- the UE has a valid TMSI. It is "idle updated" on cell C.
ii) Cell A and B will be mapped to Cell 4 and 5 respectively, as found in TS 34.108 clause 6.1.4.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1727
Test Procedure
The SS rejects a normal location updating with the cause value "PLMN not allowed". The RRC CONNECTION is
released. Then the PLMN from which this rejection was received is manually selected and the SS checks that a normal
location updating is performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1728
Expected sequence
UE SS
on cell B.
1 UE The UE is switched off (or power is removed).
Set the cell type of cell A to the "Suitable neighbour cell".
Set the cell type of cell C to the "non-suitable cell".
(see note)
3 UE The UE is switched on (or power is reapplied).
3a UE If the UE is in manual mode, it shall offer the new PLMN
as available to the user. In this case the PLMN is
manually selected.
to "Registration".
5 Void
6 Void
7 LOCATION UPDATING
REQUEST

8 LOCATION UPDATING REJ ECT "Reject cause" =PLMN not allowed.
9 SS Void The SS releases the RRC connection.
10 Void
11 UE The UE is made to search for PLMNs and the PLMN
indicated by the SS is manually selected.
to "Registration".
13 Void
14 Void
REQUEST
identity" =IMSI.
15a Void
15b LOCATION UPDATING REJ ECT "Reject cause" =PLMN not allowed.
17 Void
The following messages are sent and shall be received on cell C.
(see note)
20 UE The UE is switched on. If necessary, the UE is put into
the automatic mode.
to "Registration".
22 Void
23 Void
REQUEST
identity" =IMSI.
COMPLETE

28 Void

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1729
None.
1) 1.1 At step 12 in test 1 the UE shall not perform periodic updating.
1.2 At step 14 in test 1 the UE shall not initiate an RRC connection establishment (IMSI detach).
1.3 At step 16 in test 1 the UE shall not initiate an RRC connection establishment (IMSI attach).
1.4 At step 16 in test 1 the UE shall not perform normal location updating.
1.5 At step 30 in test 1 the UE shall reject a MO CM connection.
2) 2.1 At step 37 in test 1 the UE shall perform normal location updating.
2.2 At step 20 in test 1 the UE shall accept a request for an emergency call with the establishment cause set to
"Emergency call".
3) At step 11 in test 2 the UE is made to search for PLMNs and the PLMN indicated by the SS is manually
selected, and at step 15 the UE shall perform a normal location updating procedure.
4) At step 37 in test 1 the UE shall send a LOCATION UPDATING REQUEST message with Mobile Identity IE
set to its IMSI, CKSN IE set to "no key is available" and LAI IE set to "deleted LAI" on cell C.
9.4.2.3 Location updating / rejected / location area not allowed
1) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall:
1.4 not perform IMSI detach.
1.5 not delete the list of "equivalent PLMNs".
2) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall:
2.1 perform normal location updating when a new location area is entered;
2.2 accept a request for an emergency call, if it supports speech, by sending a RRC CONNECTION REQUEST
message with the establishment cause set to "emergency call";
2.3 delete the list of forbidden LAs after switch off (power off).
3) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall
delete the stored LAI, CKSN and TMSI.
Reference(s)
TS 24.008 clause 4.4.4.7.
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "Location Area not
allowed".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1730
To test that the UE deletes the list of forbidden LAs after switch off (power off).
Initial conditions
- System Simulator:
- three cells: A, B and C, belonging to different location areas a, b and c. Cell A and B belongs to PLMN1.
Cell C belongs to PLMN2.
- User Equipment:
- the UE has a valid TMSI(=TMSI1) and CKSN(=CKSN1). It is "idle updated" on cell A.
- the UE has a list of "equivalent PLMNs" containing PLMN1 and PLMN2.
Method to clear the list of forbidden location areas periodically.
Test Procedure
The SS rejects a normal location updating with the cause value "Location Area not allowed". The RRC CONNECTION
is released. The SS checks that the UE does not perform periodic updating, does not respond to paging with TMSI,
rejects any requests from CM entities for MM-connections except emergency calls, does not perform IMSI detach, does
not delete the list of "equivalent PLMNs", performs normal location updating when a new location area is entered,
deletes the list of forbidden LAs when switched off and deletes the stored LAI, CKSN and TMSI.
Different types of UE may use different methods to periodically clear the list of forbidden location areas (e.g. every day
at 12am). If the list is cleared while the test is being run, it may be necessary to re-run the test.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1731
Expected sequence
UE SS
on cell B.
Set the cell type of cell A to the " Suitable neighbour cell
".
Set the cell type of cell C to the " Suitable neighbour cell
".
(see note).
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
"LAI" =a, "Mobile Identity" =TMSI1
6 LOCATION UPDATING REJ ECT "Reject cause" ="Location Area not allowed".
7 SS After the sending of this message, the SS waits for the
disconnection of the mainsignalling link. The SS releases
the RRC connection.
8 Void
9 SS SS waits for a possible location updating for 7 minutes.
10 UE The UE shall not initiate an RRC-connection
establishment either on cell A, C or cell B.
11 PAGING TYPE 1 The UE is paged in cell B. "UE identity" =TMSI.
12 UE The UE shall ignore this message. This is checked during
3 s.
establishment on cell A, C or cell B. This is checked
during 3 s.
15 UE If the UE supports speech (see ICS), it is made to
perform an emergency call.
to "Emergency call".
17 Void
18 Void
21 EMERGENCY SETUP
22 RELEASE COMPLETE Cause: "unassigned number".
24 Void
25 UE If possible (see ICS) switch off is performed. Otherwise
the power is removed.
establishment on cell A, C or on cell B (check for IMSI
detach) This is checked during 3 s.
to "Registration".
29 Void
30 Void
REQUEST
available,"LAI" =deleted LAI, "mobile identity" =IMSI
(This checks the deletion of the forbidden lists)
32 LOCATION UPDATING REJ ECT "Reject cause" ="Location Area not allowed".
34 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1732
UE SS
35 SS Set the cell type of cell A to the "Suitable neighbour cell".
Set the cell type of cell B to the " Suitable neighbour cell
".
Set the cell type of cell C to the "Serving cell".
(see note).
to "Registration".
37 Void
38 Void
REQUEST

42 LOCATION UPDATING ACCEPT Mobile identity =TMSI.
COMPLETE

45 Void

None.
1) 1.1 At step 10 the UE shall not perform periodic updating.
1.2 At step 12 the UE shall not respond to paging with TMSI.
1.3 At step 14 the UE shall not initiate an RRC connection establishment.
1.4 At step 26 the UE shall not initiate an RRC connection establishment (IMSI detach).
1.5 At step 39 the UE shall perform normal location updating on cell C.
2) 2.1 At step 39 the UE shall perform normal location updating.
2.2 At step 16 the UE shall accept a request for an emergency call.
2.3 At step 31 the UE shall send a LOCATION UPDATING REQUEST message on cell B.
3) At step 31 the UE shall send a LOCATION UPDATING REQUEST message with Mobile Identity IE set to its
IMSI, CKSN IE set to "no key is available" and LAI IE set to "deleted LAI" on cell B.
9.4.2.4 Location updating / rejected / roaming not allowed in this location area
1) If the network rejects a location updating from the UE with the cause "Roaming not allowed in this location
area" the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1733
1.4 not perform IMSI detach.
2) If the network rejects a location updating from the UE with the cause "Roaming not allowed in this location
area" the UE shall:
2.1 perform normal location updating when a new location area is entered;
2.2 accept a request for an emergency call, if it supports speech, by sending a RRC CONNECTION Request
message with the establishment cause set to "emergency call";
2.3 periodically search for its HPLMN.
3) The UE shall reset the list of "Forbidden location areas for roaming" when it is switched off or has its power
source removed or when the USIM is removed.
4) The UE shall contain a list of "forbidden location areas for roaming". The location area identification received on
the BCCH that triggered the location updating request shall be added to the suitable list whenever a LOCATION
UPDATE REJ ECT message is received with the cause "Roaming not allowed in this location area". The lists
shall accommodate each 10 or more location area identifications.
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.4.3 Test purposes
Test purpose 1
To test that on receipt of a rejection using the Roaming cause code, the UE ceases trying to update on that cell, that this
situation continues for at least one periodic location interval period, and that the corresponding list is re-set by switching
off the UE or removing its power source.
Test purpose 2
To test that if no cell is available, the UE does not answer to paging with TMSI, rejects a request from CM entity other
than for emergency calls.
Test purpose 3
To test that at least 6 entries can be held in the list of "forbidden location areas for roaming" (the requirement in is to
store at least 10 entries. This is not fully tested by the third procedure).
Test purpose 4
To test that if a cell of the Home PLMN is available then the UE returns to it in preference to any other available cell.
Test purpose 5
To test that if the USIM is removed the list of "forbidden location areas for roaming" is cleared.
Initial conditions
The initial conditions shall be met before each of the different procedures.
- System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1734
- for procedures 1, 2, 3 and 5: Two cells A and B, belonging to different location areas of the same PLMN with
LAI a and b. The MCC of that PLMN is the same as that of the HPLMN. The MNC of that PLMN is
different from that of the HPLMN;
- for procedure 4: three cells A, B, C of the same PLMN which is not the HPLMN with 3 different location
area codes. Cells should differ in signal strength by 10 dB with cell A being the strongest and cell C the
weakest. There should be a 20 dB range between A and C. A should be set to a level of - 40 dBm;
- IMSI attach/detach is allowed in every cell;
- the T3212 time-out value is 1/10 hour in every cell.
- User Equipment:
- procedures 1, 2, 3 and 5: The UE has valid TMSI, CKSN and CK, IK. It is "idle updated" on cell B;
- procedure 4: The UE has valid TMSI, CKSN and CK, IK. It is "idle updated" on cell A;
- the list of "forbidden location areas for roaming" shall be empty (this may be achieved by either removing the
USIM or switching the UE OFF then ON or removing the UE power source depending on ICS).
Method to clear the list of location areas for roaming periodically.
Test Procedures
Procedure 1:
- The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". The
RRC CONNECTION is released. The SS checks that the UE does not perform periodic location updating
procedure. The UE is turned off and then on. The SS checks that the UE performs location updating on the cell
on which its location update request had been rejected (this checks that the LA is not the forbidden list after
switch on). This procedure is performed another time but the deletion of the list is checked while removing the
USIM (instead of turning off the UE).
Procedure 2:
RRC CONNECTION is released. The SS checks that the UE does not answer to a paging message with TMSI,
rejects a request from CM entity but supports an emergency call.
Procedure 3:
- The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". This
is done for 6 different location areas. Then the SS checks that the UE does not attempt to begin a location
updating procedure on the non-allowed location areas.
Procedure 4:
- The SS accepts a periodic location updating on a cell not belonging to the HPLMN. Then when the UE attempts
to perform a periodic location updating to this cell, the SS rejects this location updating with the cause value
"Roaming not allowed in this location area". Two cells are then available, one belonging to the HPLMN but with
the weakest level. It is checked that the UE returns to its HPLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1735
Procedure 5: If USIM removal is possible while UE is powered:
RRC CONNECTION is released. The SS checks that the UE does not perform periodic location updating
procedure. The USIM is removed and inserted in the UE. The SS checks that the UE performs location updating
on the cell on which its location update request had been rejected (this checks that the LA is not the forbidden
list after switch on).
Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g. every day at
12am) for roaming. If the list is cleared while the test is being run, it may be necessary to re-run the test.
Expected sequence
The following procedure is used during the test:
- change_LAI (x):
- the purpose of this procedure is to change the value of Location Area Identifier of cell x;
- the Location Area Identifier of cell x shall be changed. The code shall be chosen arbitrarily but shall be
different from any previously used in this procedure. The code shall have the same MCC as the Home PLMN
and shall not have the same MNC as the Home PLMN.
Procedure 1
UE SS
on cell A.
(see note).
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
Location Updating Type =normal.
6 LOCATION UPDATING REJ ECT "Reject cause" IE is "Roaming not allowed in this location
area".
7 SS The SS releases the RRC connection
8 Void
9 SS The SS waits at least 7 minutes for a possible location
updating.
11 UE If possible (see ICS) the UE is switched off. Otherwise if
possible the power is removed.
UE is brought back to operation and placed in an
automatic mode.
to "Registration".
14 Void
15 Void
REQUEST
17 LOCATION UPDATING ACCEPT "Mobile Identity" not IE included.
19 Void

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1736
Procedure 2
UE SS
on cell A.
(see note).
to "Registration".
This message is sent on cell A.
3 Void
4 Void
5 LOCATION UPDATING
REQUEST

area".
8 Void
on cell B.
to "Registration".
10 Void
11 Void
REQUEST

area".
15 Void
16 SS The SS waits for a possible location updating procedure
on both cells A and B for 2 minutes.
establishment on cell A or on cell B within 2 minutes after
the end of step 15.
18 PAGING TYPE 1 "UE identity" =TMSI. This message is sent on cell A and
on cell B.
19 UE The UE shall not initiate an RRC connection on cell A or
on cell B. This is checked during 3 s.
during 3 s.
Steps 22 to 31 are performed if the UE supports speech.
22 UE An emergency call is attempted.
to "Emergency Call".
24 Void
25 Void
28 EMERGENCY SETUP
31 Void
NOTE: The definitions for "Serving cell" and "Suitable neighbour cell" are specified in TS 34.108 clause 6.1
"Reference Radio Conditions for signalling test cases only".

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1737
Procedure 3
UE SS
The following messages are sent and shall be received on cell A
(see note)
2 RRC CONNECTION REQUEST "Establishment cause": Registration.
COMPLETE

5 LOCATION UPDATING
REQUEST

area".
7 RRC CONNECTION RELEASE After the sending of this message, the SS waits for the
disconnection of the main signalling link.
COMPLETE

COMPLETE

REQUEST

area".
COMPLETE

16 SS Change_LAI (A) within 5 s after step 13.
COMPLETE

REQUEST

area".
COMPLETE

24 SS Change_LAI (B) within 5 s after step 21.
COMPLETE

REQUEST

area".
COMPLETE

32 SS Change_LAI (A) within 5 s after step 29.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1738
UE SS
REQUEST

area".
COMPLETE

40 SS Change_LAI (B) within 5 s after step 37.
COMPLETE

REQUEST

area".
COMPLETE

48 SS The SS waits for a possible location updating procedure
on both cells A and B for 7 minutes.
establishment on cell A or on cell B within 7 minutes after
the end of step 47.
NOTE: The definitions for "Serving cell" and "Suitable neighbour cell" are specified in TS 34.108 clause 6.1

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1739
Procedure 4
UE SS
1 SS The SS waits for a periodic location updating procedure
on cell A for 7 minutes after the initial conditions have
been established.
COMPLETE

5 LOCATION UPDATING
REQUEST
Location Updating Type =periodic.
COMPLETE

9 SS The location area identity of cell C shall be changed to
that of a location area in the Home PLMN.
10 SS The SS waits for a periodic location updating procedure
on cell A for 7 minutes.
This message is sent on cell A within 7 minutes after the
end of step 8.
COMPLETE

REQUEST
"Location updating type" =periodic.
area".
COMPLETE

COMPLETE

REQUEST
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1740
Procedure 5
UE SS
(see note)
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST

area".
7 The SS releases the RRC connection.
8 Void
9 SS The SS waits at least 7 minutes for a possible location
updating.
11 UE The USIM is removed.
12 UE The USIM is inserted into the ME.
to "Registration".
14 Void
15 Void
REQUEST
19 Void

None.
1) 1.1 At step 10 in Procedure 1 the UE shall not perform periodic updating.
1.2 At step 19 in Procedure 2 the UE shall not respond to paging with TMSI.
1.3 At step 21 in procedure 2 the UE shall not initiate an RRC connection establishment.
1.4 After step 13 in Procedure 5 the UE shall perform location updating (at step 16; not perform IMSI detach).
2) 2.1 After step 9 in Procedure 2 the UE perform normal location updating (at step 12).
2.2 At step 23 in Procedure 2 the UE shall initiate a RRC CONNECTION REQUEST message with the
establishment cause set to "Emergency call";
2.3 After step 14 in Procedure 4 the UE shall attempt to location updating with location updating type "periodic"
(at step 21: periodically search for its HPLMN).
3) After step 12 in Procedure 5 the UE shall perform location updating (at step 16) when the USIM is removed.
4) At step 49 in Procedure 3 the UE shall not attempt to begin a location updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1741
9.4.2.5 Location updating / rejected / No Suitable Cells In Location Area
1) If the network rejects a location updating from the UE with the cause " No Suitable Cells In Location Area " the
UE shall:
1.1 perform normal location updating at a suitable cell in another location area in the same PLMN,
Reference(s)
TS 24.008 clause 4.4.4.7.
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "No Suitable Cells
In Location Area".
Initial conditions
- System Simulator:
- two cells: A and B, belonging to different location areas a and b and belonging to PLMN1;
- one cell: C, belonging to PLMN2;
- one cell: D, belonging to PLMN3;
- IMSI attach/detach is allowed in cells A, B, C and D;
ii) Cell D will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.
- User Equipment:
- the UE has a valid TMSI(=TMSI1) and CKSN(=CKSN1). It is "idle updated" on cell A.
- the UE has a list of "equivalent PLMNs" containing PLMN1 and PLMN2.
None.
Test Procedure
The SS rejects a normal location updating with the cause value "No Suitable Cells In Location Area". The RRC
CONNECTION is released. The SS checks that the UE shall search for a suitable cell in a different location area on the
equivalent PLMN, which is equal condition for the UE as same PLMN, and shall perform normal location updating
procedure in that cell
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1742
Expected sequence
UE SS
Set the cell type of cell C to the "Suitable neighbour cell".
Set the cell type of cell D to the "Suitable neighbour cell".
(see note)
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
"LAI" =a, "mobile station classmark 1" as given by the
ICS and "Mobile Identity" =TMSI1.
6 LOCATION UPDATING REJ ECT "Reject cause" ="No Suitable Cells In Location Area".
8 Void
to "Registration".
10 Void
11 Void
REQUEST
"LAI" =a, "mobile station classmark 1" as given by the
ICS, "Mobile Identity" =TMSI1.
13 Void
14 Void
16 Void
17 LOCATION UPDATING ACCEPT Mobile identity =TMSI, LAI =c.
COMPLETE

20 Void

None.
At step 12 the UE shall perform normal location updating on cell C.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1743
9.4.3 Location updating / abnormal cases
9.4.3.1 Void
9.4.3.2 Location updating / abnormal cases / attempt counter less or equal to 4, LAI
different
1) When a failure such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 has occurred during a normal
location updating procedure, if the attempt counter is smaller than 4 and after expiry of T3211, the UE shall
resend its LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE
set to "no key is available" and the Location Updating Type IE set to "normal location updating".
location updating procedure the UE shall:
2.1 not answer to paging with the previously allocated TMSI;
2.2 not perform the IMSI detach procedure, when switched off.
3) When a failure such as case e) of clause 4.4.4.9 of TS 24.008 has occurred during a normal location updating
procedure and when an emergency call establishment is requested by the user the UE, if it supports speech, shall
send a CM SERVICE REQUEST message with CM Service Type IE set to "emergency call establishment",
CKSN IE set to "no key available" and Mobile Identity IE set to its IMSI and after acceptance by the network it
shall send an EMERGENCY SETUP message.
location updating procedure the UE shall use a request from CM entity other than emergency call as a trigger for
a normal location updating procedure and shall send a LOCATION UPDATING REQUEST message with the
Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the Location Updating Type IE set
to "normal location updating".
location updating procedure the UE shall answer to paging with IMSI and shall send a PAGING RESPONSE
message with CKSN IE set to "no key available" and Mobile Identity IE set to its IMSI.
location updating procedure the UE shall perform a normal location updating procedure as soon as it enters a
new cell.
References
TS 24.008 clauses 4.4.4.2, 4.4.4.9.
To verify that the UE performs normal location updating procedures when its attempt counter is smaller than 4.
To check that the UE does not perform the IMSI detach procedure when "idle not updated".
To verify that when "idle not updated" the UE can perform an emergency call.
To verify that when "idle not updated" the UE uses requests from CM layer other than emergency call as triggering of a
normal location updating procedure.
To verify that the UE performs a normal location updating procedure if it enters a new cell while being "idle not
updated".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1744
Initial conditions
- System Simulator:
- two cells: A and B of the same PLMN, belonging to different location areas with LAI a and b;
- ATT flag shall be set to IMSI attach/detach allowed.
- User Equipment:
- the UE is "idle updated" on cell A. A valid CKSN value is stored in the USIM and is noted "initial CKSN". A
TMSI is allocated.
Test Procedure
The UE is made to perform a normal location updating procedure. Five types of failure cases are triggered:
- sending of a Location Updating Reject with cause randomly chosen between all defined cause values except 2, 3,
6, 11, 12 and 13 (which trigger a different action) (case g of TS 24.008 clause 4.4.4.9);
- RRC connection failure (case d);
- sending of a RRC CONNECTION RELEASE message before the normal end of the procedure (case f);
- T3210 time-out (case e);
- RR connection establishment failure (case h).
As there is no stored LAI or the stored LAI is different from the broadcast LAI, and the attempt counter in the UE shall
be lower than 4, the UE enters the state MM IDLE and substate ATTEMPTING TO UPDATE and waits for T3211
seconds before trying again a location updating procedure.
Then the behaviour of the UE in the MM IDLE state and ATTEMPTING TO UPDATE substate is checked, that is:
- not answer to paging with TMSI;
- not perform an IMSI detach procedure;
- support request for emergency call;
- use requests from CM layer other than emergency call as triggering of a normal location updating procedure;
- perform normal location updating procedure when a new cell is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1745
Expected sequence
UE SS
(see note)
2 RRC CONNECTION REQUEST Establishment cause: Registration.
COMPLETE

5 LOCATION UPDATING
REQUEST
location updating type =normal, CKSN =initial value, LAI
=a, mobile station classmark 1 as given by the ICS and
mobile identity =TMSI.
6 LOCATION UPDATING REJ ECT IE Reject cause is set to #X in table 10.5.95 of TS
24.008, causes #2, #3, #6, #11, #12, #13 and #15 being
excluded.
COMPLETE

establishment on cell A or on cell B during T3211
seconds at least after the RRC connection is released.
COMPLETE

REQUEST
location updating type =normal, CKSN =no key
available, LAI =deleted LAI (the MCC and MNC hold the
previous values, the LAC is coded FFFE), Mobile Identity
=IMSI.
14 SS The SS modifies the scrambling code of DL DPCH for
15 (void)
15a CELL UPDATE CCCH.
15b RRC CONNECTION RELEASE CCCH.
15c SS The SS re-modifies the scrambling code of DL DPCH to
the original one.
15d UE The UE shall not initiate an RRC connection
COMPLETE

REQUEST
=IMSI.
COMPLETE

COMPLETE

REQUEST
=IMSI.
27 AUTHENTICATION REQUEST CKSN =initial CKSN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1746
UE SS
28a SECURITY MODE COMMAND
28b SECURITY MODE COMPLETE
29 LOCATION UPDATING ACCEPT IE mobile Identity =new TMSI.
COMPLETE

disconnection of the main signalling link. UE is now "idle
updated" in cell B.
COMPLETE

(see note)
COMPLETE

REQUEST
=b, mobile station classmark 1 as given by the ICS and
38 SS performs step 6 with reject cause #100 and step 7.
38a UE performs step8.
39 PAGING TYPE 1 UE identity =old TMSI of the UE.
This message is sent continuously to the UE during 8 s.
40 SS The SS checks that there is no answer from the UE
during 12 s.
41 SS If during steps 39 and 40 the UE attempts to perform a
location updating procedure the SS will perform step 38
and then continue the procedure.
Otherwise if possible (see ICS) mobile switch off is
performed. Otherwise the power is removed.
establishment on cell A or on cell B during 30 s.
COMPLETE

REQUEST
=IMSI.
COMPLETE

updated" in cell A.
COMPLETE

(see note).
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1747
UE SS
REQUEST
61 AUTHENTICATION RESPONSE Steps 60 and 61 are performed N times. N shall be
chosen in such a way that T3210 expires.
62 UE The UE shall cease transmission and then shall not
initiate an RRC connection establishment on cell A or on
cell B during T3211 seconds at least after the expiry of
T3210.
63 UE If the UE supports speech it is made to perform an
emergency call.
64 RRC CONNECTION REQUEST Establishment cause: Emergency call.
COMPLETE

67 CM SERVICE REQUEST CM service type =Emergency call establishment; CKSN
=no key available; Mobile Identity =IMSI.
69 EMERGENCY SETUP
70 RELEASE COMPLETE Cause =unassigned number.
COMPLETE

72a UE The UE shall not initiate an RRC connection

COMPLETE

REQUEST
=IMSI.
COMPLETE

updated" in cell B.
COMPLETE

(see note).
COMPLETE

REQUEST
88 SS performs step 14.
88a (void)
88b CELL UPDATE CCCH.
88c RRC CONNECTION RELEASE CCCH.
88d SS performs step 15c.
89 UE A MO CM connection is attempted before T3211 expiry.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1748
UE SS
COMPLETE

REQUEST
=IMSI.
94 LOCATION UPDATING ACCEPT IE mobile Identity =new TMSI. If the location updating
type in the LOCATION UPDATING REQUESTcontains
FOR, then IE Follow-on Proceed is included in the
ACCEPT and steps 96 to 100 will be omitted.
COMPLETE

COMPLETE

97a SS
98 RRC CONNECTION REQUEST Establishment cause: Not checked.
COMPLETE

101 CM SERVICE REQUEST CKSN =no key available, Mobile identity =TMSI.
updated" in cell A.
COMPLETE

(see note).
COMPLETE

REQUEST
available LAI =a, mobile station classmark 1 as given by
the ICS and mobile identity =TMSI.
109 SS performs step 14.
109a (void)
109d SS performs step 15c.
(see note).
110a RRC CONNECTION REQUEST Establishment cause: Registration.
110c RRC CONNECTION SETUP
COMPLETE

110d LOCATION UPDATING
REQUEST
available LAI =deleted LAI (the MCC and MNC hold the
previous values, the LAC is coded FFFE), mobile station
classmark 1 as given by the ICS and mobile identity =
IMSI.
110e SS performs step 14.
110f CELL UPDATE CCCH.
110g RRC CONNECTION RELEASE CCCH.
110h SS performs step 15c.
"Initial UE identity" =IMSI.
112 PAGING RESPONSE "Mobile identity" =IMSI, CKSN =no key available.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1749
UE SS
COMPLETE


None.
its IMSI, CKSN IE set to "no key available" and the Location Updating Type IE set to "normal location
updating".
2)
2.1 At step 40 the UE shall not answer to paging with the previously allocated TMSI.
2.2 At step 43 the UE shall not perform the IMSI detach procedure.
3) At step 67 the UE shall send a CM SERVICE REQUEST message with CM Service Type IE set to "emergency
call establishment", CKSN IE set to "no key available" and Mobile Identity IE set to its IMSI.
At step 69 the UE shall send an EMERGENCY SETUP message.
its IMSI, CKSN IE set to "no key is available" and the Location Updating Type IE set to "normal location
updating".
5) At step 112 the UE shall send a PAGING RESPONSE message with CKSN IE set to "no key available" and
Mobile Identity IE set to its IMSI.
6) At step 110d the UE shall perform a normal location updating procedure.
9.4.3.3 Location updating / abnormal cases / attempt counter equal to 4
1) When four failures such as cases d) to h) of clause 4.4.4.9 of TS 24.008 have occurred during a normal location
updating procedure the UE shall:
1.1 perform location updating after T3212 expiry by sending a LOCATION UPATING REQUEST message with
the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the Location Updating Type
set to "normal location updating";
1.2 if the T3212 initiated location updating was unsuccessful, then after T3211 expiry the UE shall send a
LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to
"no key is available" and the Location Updating Type IE set to "normal location updating".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1750
2) When four failures such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 have occurred during a normal
location updating procedure the UE shall not perform the IMSI detach procedure, when switchd off.
location updating procedure the UE, if it supports speech, shall be able to perform an emergency call i.e. the UE
is able to send a CM SERVICE REQUEST message with the CM Service Type IE set to "emergency call
establishment", CKSN IE set to "no key is available" and Mobile Identity IE set to its IMSI and then send an
EMERGENCY SETUP message.
location updating procedure:
4.1 the UE shall use a request from CM entity for MM connection for a service other than emergency call as a
trigger for a normal location updating procedure and shall send a LOCATION UPDATING REQUEST
message with the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the Location
Updating Type IE set to "normal location updating";
4.2 after a location updating triggered by a request from the CM layer which was .unsuccessful, after T3211
expiry the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to
its IMSI, CKSN IE set to "no key is available" and the Location Updating Type IE set to "normal location
updating".
location updating procedure:
5.1 the UE shall perform a normal location updating procedure if it enters a new cell;
5.2 if this location updating is unsuccessful, after T3211 expiry the UE shall send a LOCATION UPDATING
REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the
Location Updating type IE set to "normal location updating".
References
TS 24.008 clause 4.4.4.9.
To verify that the UE performs normal location updating procedures after T3212 expiry, when its attempt counter has
reached value 4 and that the UE reset its attempt counter after a timer T3212 expiry.
To verify that the UE still follows the MM IDLE state and ATTEMPTING TO UPDATE substate requirements after its
attempt counter has reached value 4.
To verify that the attempt counter is reset in the cases where it has to be done.
Initial conditions
- System Simulator:
- two cells: A and B, belonging to different location areas a and b;
- T3212 is set to 6 minutes.
- User Equipment:
- the UE is "Idle updated" on cell B with a valid CKSN and a TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1751
Test Procedure
The UE is made to perform a normal location updating. The SS triggers a failure in this procedure by modifying
scrambing code of DL DPCH. After T3211 expiry the UE will try again the location updating procedure. The SS
triggers again a failure by modifying it. This is done again 2 times. At this point the attempt counter shall be equal to 4.
It is then checked that T3212 has been started and that at its expiry the UE will try a normal location updating
procedure. It is verified that the UE has reset its attempt counter after timer T3212 expiry.
Then it is checked that, when the attempt counter has reached the value of 4, the UE is in the MM IDLE state and
ATTEMPTING TO UPDATE substate, that is:
- not perform an IMSI detach procedure;
- support request for emergency call;
- use requests from CM layer other than emergency call as triggering of a normal location updating procedure;
- perform normal location updating procedure when a new cell is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1752
Expected sequence
UE SS
(see note).
COMPLETE

5 LOCATION UPDATING
REQUEST
6 LOCATION UPDATING REJ ECT IE Reject cause is set to #22 in table 10.5.95 of
TS 24.008, causes #2, #3, #6, #11, #12, #13 and #15
being excluded.
7 RRC CONNECTION RELEASE The SS waits for the disconnection of the main signalling
link.
COMPLETE

COMPLETE

REQUEST
=IMSI.
15 (void)
the original one.
COMPLETE

REQUEST
=IMSI.
21 AUTHENTICATION RESPONSE Steps 20 and 21 are performed N times. N shall be
chosen in such a way that T3210 expires.
22 UE The UE shall cease transmission and then shall not
initiate an RRC connection establishment on cell A or on
cell B during T3211 seconds at least after the expiry of
T3210.
COMPLETE

REQUEST
=IMSI.
link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1753
UE SS
COMPLETE

(tolerance -15s; 45s) at least after the RRC connection is
released.
COMPLETE

REQUEST
location updating type: "normal location update" CKSN =
no key available, LAI =deleted LAI (the MCC and MNC
hold the previous values, the LAC is coded FFFE) mobile
station classmark 1 as given by the ICS and mobile
identity =IMSI.
34 LOCATION UPDATING REJ ECT IE Reject cause =#17 "network failure".
link.
COMPLETE

COMPLETE

REQUEST
previous values, the LAC is coded FFFE) mobile station
IMSI.
COMPLETE

disconnection of the main signalling link. UE is now "idle,
updated" in cell A.
COMPLETE

(see note).
COMPLETE

REQUEST
53 LOCATION UPDATING REJ ECT IE Reject cause is set to #X in table 10.5.95 of
TS 24.008, causes #2, #3, #6, #11, #12, #13 and #15
being excluded.
link.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1754
UE SS
COMPLETE

REQUEST
=IMSI.
61a (void)
61d SS The SS re-modifies the scrambling code of DL DPCH to
the original one.
61e UE The UE shall not initiate an RRC connection
COMPLETE

REQUEST
=IMSI.
link.
COMPLETE

COMPLETE

REQUEST
IMSI.
73 SS performs step 53 and 54.
74 UE performs step 55.
If the UE supports speech, it is made to perform an
emergency call.
75 RRC CONNECTION REQUEST Establishment cause: Emergency call.
COMPLETE

78 CM SERVICE REQUEST CM service type =Emergency call establishment; CKSN
=no key available; Mobile Identity =IMSI.
80 EMERGENCY SETUP
81 RELEASE COMPLETE Cause =unassigned number.
link.
COMPLETE

during 30 s.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1755
UE SS
COMPLETE

REQUEST
=IMSI.
COMPLETE

updated" in cell B.
COMPLETE

(see note).
COMPLETE

REQUEST
TS 24.008, causes #2, #3, #6, #11, #12, #13 and #15
being excluded.
link.
COMPLETE

COMPLETE

REQUEST
=IMSI.
111 (void)
the original one.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1756
UE SS
REQUEST
=IMSI.
link.
COMPLETE

COMPLETE

REQUEST
IMSI.
123 (void)
123a UE performs step 61a.
123d SS performs step 61d.
COMPLETE

REQUEST
=IMSI.
129 (void)
129a UE performs step 61a.
129d SS performs step 61d.
COMPLETE

REQUEST
=IMSI.
137 LOCATION UPDATING ACCEPT IE mobile Identity =new TMSI. If the location updating
type in the LOCATION UPDATING REQUESTcontains
FOR, then IE Follow-on Proceed is included in the
ACCEPT and steps 139 to 143 will be omitted.
COMPLETE

COMPLETE
UE is now "idle, updated" in cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1757
UE SS
COMPLETE

144 CM SERVICE REQUEST CKSN =initial value, Mobile identity =TMSI.
145 CM SERVICE REJ ECT cause #17 (network failure).
link.
COMPLETE

(see note).
COMPLETE

REQUEST
TS 24.008, causes #2, #3, #6, #11, #12, #13 and #15
being excluded.
link
COMPLETE

COMPLETE

REQUEST
=IMSI.
162 (void)
the original one.
COMPLETE

REQUEST
=IMSI.
link.
COMPLETE

COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1758
UE SS
REQUEST
IMSI.
174 LOCATION UPDATING REJ ECT IE Reject cause ="retry upon entry into a new cell".
174a RRC CONNECTION RELEASE

The SS waits for the disconnection of the main signalling
link.
174b RRC CONNECTION RELEASE
COMPLETE

(see note).
COMPLETE

REQUEST
available , LAI =deleted LAI (the MCC and MNC hold the
IMSI.
180 SS performs the step 61.
181 (void)
the original one.
COMPLETE

REQUEST
=IMSI.
COMPLETE

updated" in cell A.
COMPLETE


None.
1) 1.1 At step 33 the UE shall perform location updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1759
1.2 At step 41 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set
to its IMSI, CKSN IE set to "no key is available" and the Location Updating type IE set to "normal location
updating".
2) At step 85 the UE shall not perform the IMSI detach procedure.
3) At step78 the UE shall send a CM SERVICE REQUEST message with the CM Service Type IE set to
"emergency call establishment", CKSN IE set to "no key is available" and Mobile Identity IE set to its IMSI.
At step 80 the UE shall send an EMERGENCY SETUP message.
4)
4.1 At step128 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE
set to its IMSI, CKSN IE set to "no key is available" and the Location Updating type IE set to "normal
location updating";
4.2 At step 134 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE
location updating".
5)
5.1 At step 179 the UE shall perform a normal location updating procedure if it enters a new cell;
location updating".
9.4.3.4 Location updating / abnormal cases / attempt counter less or equal to 4,
stored LAI equal to broadcast LAI
1) When a failure such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 has occurred during a periodic
location updating procedure (the broadcast LAI is equal to the stored LAI):
1.1 the UE shall be able to establish an MM connection i.e. send a RRC CONNECTION REQUEST message
and then a CM SERVICE REQUEST message, CKSN and LAI set to those which have been allocated to the
UE, Mobile Identity IE set to the TMSI which has been allocated to the UE;
1.2 then the UE shall not attempt a location updating procedure.
2) When a failure such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 has occurred during an IMSI attach
procedure (the broadcast LAI is equal to the stored LAI):
2.1 the UE shall be able to establish an MM connection i.e. send a RRC CONNECTION REQUEST message
and then a CM SERVICE REQUEST message, CKSN and LAI set to those which have been allocated to the
UE, Mobile Identity IE set to the TMSI which has been allocated to the UE;
2.2 then the UE shall not attempt a location updating procedure.
3) When a failure such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 has occurred during a periodic
location updating procedure and the attempt counter is smaller than 4 the UE shall send, after T3211 expiry, a
LOCATION UPDATING REQUEST message with the Mobile Identity IE set to the TMSI which has been
allocated to the UE, CKSN IE and LAI set to those which have been allocated to the UE and the Location
Updating Type IE set to "periodic updating".
3.1 When the UE's attempt counter reaches the value 4 (four failures such as cases d), f), g) and h) of clause
4.4.4.9 of TS 24.008 have occurred during a periodic location updating procedure) after T3212 expiry it shall
send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE
set to "no key is available" and the Location Updating Type IE set to "normal".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1760
4) When the UE's attempt counter reaches the value 4 (four failures such as cases d), f), g) and h) of clause 4.4.4.9
of TS 24.008 have occurred during a periodic location updating procedure) it shall use a request for a CM
connection other than emergency call as a trigger for a location updating procedure.
5) When a failure such as cases d), f), g) and h) of clause 4.4.4.9 of TS 24.008 has occurred during an IMSI attach
procedure and the attempt counter is smaller than 4 the UE shall send, after T3211 expiry, a LOCATION
UPDATING REQUEST message with the Mobile Identity IE set to the TMSI which has been allocated to the
UE, CKSN IE and LAI set to those which have been allocated to the UE and the Location Updating type set to
"IMSI attach".
5.1 When the UE's attempt counter reaches the value 4 (four failures such as cases d), f), g) and h) of clause
4.4.4.9 of TS 24.008 have occurred during an IMSI attach procedure) after T3212 expiry it shall send a
LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to
"no key is available" and the Location Updating type set to "normal".
6) When the UE's attempt counter reaches the value 4 (four failures such as cases d), f), g) and h) of clause 4.4.4.9
of TS 24.008 have occurred during an IMSI attach procedure) it shall use a request for a CM connection other
than emergency call as a trigger for a location updating procedure.
References
TS 24.008 clause 4.4.4.9.
To verify that in the case when the attempt counter is smaller than 4 and the broadcast LAI is equal to the stored LAI,
the UE is in the MM IDLE state and NORMAL SERVICE substate. To verify that timer T3211 is stopped after a MM
connection establishment.
To verify that the UE uses the T3211 timer. and that it enters the MM IDLE state and NORMAL SERVICE substate
when its attempt counter reaches value 4 even in the case where the stored LAI is equal to the broadcast LAI.
Initial conditions
- System Simulator:
- one cell: B, belonging to location area b;
- IMSI attach/detach is allowed;
- User Equipment:
- the UE is "Idle updated" on cell B with a valid CKSN and a TMSI.
Test Procedure
A failure during the periodic location updating is triggered: as the broadcast LAI is equal to the stored LAI, the UE is
still in the MM IDLE state and NORMAL SERVICE substate and timer T3211 is started. A CM connection other than
for emergency call is attempted. It is checked that this is possible and that T3211 is stopped. Same test is performed
with a failure during an IMSI attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1761
Then failures are triggered during the periodic location updating to let the attempt counter to reach the value of 4. The
UE shall enter the MM IDLE state and ATTEMPTING TO UPDATE substate and delete any TMSI, stored LAI,
ciphering key sequence number and ciphering key. When the attempt counter reaches the value of 4, timer T3212 shall
be started. At timer T3212 expiry a location updating procedure is started. A request for CM connection other for than
emergency call shall trigger a location updating procedure.
Same tests are performed when the failures are triggered during an IMSI attach procedure.
Expected sequence
UE SS
1 SS The SS shall wait at most T3212 +45 s.
COMPLETE

5 LOCATION UPDATING
REQUEST
location updating type =periodic, CKSN =initial value,
LAI =b, mobile station classmark 1 as given by the ICS
and mobile identity =TMSI.
6 SS performs step 6, of 9.4.3.2 with cause #17 and step 7 of
9.4.3.2.
6a UE

performs step 8 of 9.4.3.2.
COMPLETE

11 CM SERVICE REQUEST CKSN =initial CKSN, Mobile Identity =TMSI.
13 An initial CM message
link.
COMPLETE

16 SS The UE shall not initiate an RRC connection
establishment. This is checked during T3211.
Steps 18 to 23 are optional.
18 RRC CONNECTION REQUEST Establishment Cause: Detach
COMPLETE

21 IMSI DETACH INDICATION
COMPLETE

COMPLETE

REQUEST
location updating type =IMSI attach, CKSN =initial
value, LAI =b, mobile station classmark 1 as given by the
ICS and mobile identity =TMSI.
29 SS performs step 14 of 9.4.3.2.
29a (void)
29d SS performs step 15c of 9.4.3.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1762
UE SS
COMPLETE

34 CM SERVICE REQUEST CKSN =initial CKSN, Mobile Identity =TMSI.
35 SECURITY MODE COMMAND
37 An initial CM message
link.
COMPLETE

40 SS The UE shall not initiate an RRC connection
establishment. This is checked during T3211 UE is "idle,
updated" in cell B.
40/1 UE If possible (see ICS) USIM detachment is performed.
Steps 40/2 to 40/7 are optional.
40/2 RRC CONNECTION REQUEST Establishment Cause: Detach
40/3 RRC CONNECTION SETUP
COMPLETE

40/5 IMSI DETACH INDICATION
40/6 RRC CONNECTION RELEASE
COMPLETE

40/8 UE Depending on what has been performed in step 40/1, the
40/9 RRC CONNECTION REQUEST Establishment cause: Registration.
COMPLETE

40/12 LOCATION UPDATING
REQUEST
40/13 LOCATION UPDATING ACCEPT without mobile identity
COMPLETE

41 SS The SS shall wait at most T3212 +15 s.
COMPLETE

REQUEST
46a (void)
establishment during T3211 at least after the RRC
connection is released.
COMPLETE

REQUEST
52 SS performs step 6 of 9.4.3.2 with cause #17 and step 7 of
9.4.3.2.
52a UE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1763
UE SS
COMPLETE

REQUEST
59 (void)
the original one.
COMPLETE

REQUEST
64a (void)
establishment during T3212 seconds at least after the
RRC connection is released.
COMPLETE

REQUEST
IMSI.
72 (void)
72a
72b

LOCATION UPDATING ACCEPT
TMSI REALLOCATION
COMPLETE
IE mobile Identity =TMSI.
link.
COMPLETE

establishment during than T3212 seconds at least after
the RRC connection is released.
COMPLETE

REQUEST
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1764
UE SS
9.4.3.2.
80a UE

COMPLETE

REQUEST
87 (void)
the original one.
COMPLETE

REQUEST
92a (void)
COMPLETE

REQUEST
9.4.3.2.
98a UE

COMPLETE

REQUEST
IMSI.
104 LOCATION UPDATING ACCEPT IE mobile identity =TMSI. If the location updating type in
the LOCATION UPDATING REQUESTcontains FOR,
then IE Follow-on Proceed is included in the ACCEPT
and steps 106 to 110 will be omitted.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1765
UE SS
COMPLETE

COMPLETE

111 CM SERVICE REQUEST CKSN =no key available, Mobile identity =TMSI
COMPLETE

COMPLETE

COMPLETE

COMPLETE

REQUEST
location updating type =IMSI attach, CKSN =no key
available, LAI =b, mobile station classmark 1 as given by
128 (void)
the original one.
COMPLETE

REQUEST
133 RRC CONNECTION RELEASE After the sending of the message the SS waits for the
COMPLETE

COMPLETE

REQUEST
140 (void)
140a LOCATION UPDATING REJ ECT IE Reject cause is set to #X in table 10.5.95 of
TS 24.008, causes #2, #3, #6, #11, #12, #13 and #15
being excluded.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1766
UE SS
140b RRC CONNECTION RELEASE After the sending of this message, the SS waits for the
COMPLETE

COMPLETE

REQUEST
147a (void)
establishment during T3212 seconds at least after the
RRC connection is released.
COMPLETE

REQUEST
IMSI.
155 LOCATION UPDATING ACCEPT IE mobile Identity =TMSI.
COMPLETE

COMPLETE

COMPLETE

COMPLETE

COMPLETE

REQUEST
171a (void)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1767
UE SS

COMPLETE

REQUEST
9.4.3.2.
177a UE

COMPLETE

REQUEST
184 (void)
the original one.
COMPLETE

REQUEST
189a (void)
190 UE A MO CM connection id attempted before T3212 expiry
COMPLETE

REQUEST
IMSI.
197 LOCATION UPDATING ACCEPT IE mobile Identity =TMSI. If the location updating type in
the LOCATION UPDATING REQUESTcontains FOR,
then IE Follow-on Proceed is included in the ACCEPT
and steps 199 to 204 will be omitted.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1768
UE SS
COMPLETE

COMPLETE

201 (void)
COMPLETE

COMPLETE

None.
1)
1.1 At step 8 the UE shall send a RRC CONNECTION REQUEST message and at step 11 the UE shall send a
CM SERVICE REQUEST message, CKSN and LAI set to those which have been allocated to the UE,
Mobile Identity IE set to the TMSI which has been allocated to the UE;
1.2 At step 11 the UE shall not attempt a location updating procedure.
2)
2.1 At step 31 the UE shall send a RRC CONNECTION REQUEST message and at step 34 the UE shall send a
CM SERVICE REQUEST message, CKSN and LAI set to those which have been allocated to the UE,
Mobile Identity IE set to the TMSI which has been allocated to the UE;
2.2 At step 39 the UE shall not attempt a location updating procedure.
the TMSI which has been allocated to the UE, CKSN IE and LAI set to those which have been allocated to the
UE and the Location Updating Type IE set to "periodic updating".
3.1 At step 69 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set
to its IMSI, CKSN IE set to "no key is available" and the Location Updating Type IE set to "normal".
4) At step 103 the UE shall send a LOCATION UPDATING REQUEST message.
the TMSI which has been allocated to the UE, CKSN IE and LAI set to those which have been allocated to the
UE and the Location Updating Type IE set to "IMSI attach".
set to its IMSI, CKSN IE set to "no key is available" and the Location Updating Type IE set to "normal".
6) At step 194 the UE shall send a LOCATION UPDATING REQUEST message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1769
9.4.3.5 Location updating / abnormal cases / Failure due to non-integrity protection
Except the messages listed below, no layer 3 signalling messages shall be processed by the receiving MM and GMM
entities or forwarded to the CM entities, unless the security mode control procedure is activated for that domain.
- MM messages:
- AUTHENTICATION REQUEST
- AUTHENTICATION REJ ECT
- IDENTITY REQUEST
- LOCATION UPDATING ACCEPT (at periodic location update with no change of location area or
temporary identity)
- LOCATION UPDATING REJ ECT
- CM SERVICE ACCEPT, if the following two conditions apply:
- no other MM connection is established; and
- the CM SERVICE ACCEPT is the response to a CM SERVICE REQUEST with CM SERVICE
TYPE IE set to 'emergency call establishment'
- CM SERVICE REJ ECT
- ABORT
References
TS 24.008 clauses 4.1.1.1.1
To verify that the UE ignores NAS signalling messages when the security mode procedure is not activated.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
The location updating procedure is started. Upon reception of LOCATION UPDATING REQUEST message from the
UE, the SS responds to LOCATION UPDATING ACCEPT message without the integrity protection. The UE shall
ignore this message and restart the location updating procedure at expiry of timer T3211. This time the SS starts the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1770
authentication procedure and initiates the integrity protection. After receiving LOCATION UPDATING ACCEPT
message, the UE shall respond to TMSI REALLOCATION COMPLETE message.
Expected sequence
UE SS
(see note)
to "Registration".
3 LOCATION UPDATING
REQUEST

6 SS The SS does not initiate the security mode procedure.
7 LOCATION UPDATING ACCEPT
8 UE The UE ignores LOCATION UPDATING ACCEPT
message.
10 UE The UE aborts the RR connection.
to "Registration".
REQUEST

17 SS The SS starts the security mode procedure with the
integrity protection. The content of integrity protection
mode info IE in SECURITY MODE COMMAND message
is specified below.
COMPLETE


None.
At step 8 the UE shall ignore the first LOCATION UPDATING ACCEPT message.
At step 14 the UE shall send LOCATION UPDATING REQUEST message after expiry of timer T3211.
At step 16 the UE shall respond to TMSI REALLOCATION COMPLITE message after the UE receives the second
LOCATION UPDATING ACCEPT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1771
9.4.4 Location updating / release / expiry of T3240
9.4.4.1 Definition
The UE receiving a LOCATION UPDATING ACCEPT message shall start T3240: it shall abort the RR connection at
the expiry of timer T3240.
References
TS 24.008 clauses 4.4.4.8 and 11.2.
To verify that the UE aborts the RR-connection at the expiry of timer T3240.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
A normal location updating procedure is performed. The RR-connection is not released by the SS within the timer
T3240. It is checked that the UE aborts the RR-connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1772
Expected sequence
UE SS
(see note 1)
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST

8 SIGNALLING CONNECTION
RELEASE INDICATION
The UE shall abort the RR connection.
(see note 2)
CN domain identity =CS domain
10 Void Send only if RRC Connection Release is send.
NOTE1: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference
NOTE2: At the expiration of T3240, as per TS 24.008, RR connection shall be aborted. In UMTS, UE cannot
release RRC connection on its own. Instead, UE can abort the RR connection ("CS signalling
connection") and send a Signalling Connection Release Indication to the UTRAN, in order to initiate the
release of RRC connection.

None.
At step 10 the UE shall abort the RRC connection.
9.4.5 Location updating / periodic
9.4.5.1 Location updating / periodic spread
1) The UEs shall perform spreading of the time before performing a periodic location updating when the location
updating timer value is reduced.
2) The UE shall reset timer T3212 when the UE is deactivated, and shall start with a value between zero and the
broadcasted value when reactivated in the same cell, IMSI attach being forbidden.
3) When activated the UE shall start timer T3212 with a value randomly drawn in the allowed range.
NOTE: This conformance requirement is not covered by a test purpose. It is intended to be covered by a
manufacturer declaration.
References
TS 24.008 clause 4.4.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1773
1) To check that when the location updating timer is reduced, the timer running in the UE is started with a value
depending on the current timer value and the new broadcasted T3212 value.
2) To verify that when the UE is reactivated in the same cell (as the one in which it was deactivated), IMSI attach
being forbidden, the UE starts the timer T3212 with a value between zero and the broadcasted value.
NOTE: It is not tested that the value is random.
Initial conditions
- System Simulator:
- one cell, T3212 is set to 30 minutes;
- IMSI attach is allowed in the cell;
- User Equipment:
- the UE is deactivated. The stored MCC, MNC and LAC correspond to the broadcasted values. The stored
update status is "updated".
None.
Test procedure
The UE is activated. It performs IMSI attach. 3 minutes after the end of the IMSI attach procedure, the value of T3212
is set to 6 minutes. The UE shall perform periodic location updating 6 minutes after the end of the IMSI attach
procedure.
Then, the IMSI attach/detach is forbidden. T3212 is still set to 6 minutes.
The UE is deactivated. The UE is reactivated. It is checked that the UE performs a periodic location updating during the
6 minutes following activation.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1774
Expected sequence
UE SS
1 UE The UE is activated.
COMPLETE

5 LOCATION UPDATING
REQUEST
"location updating type": IMSI attach.
COMPLETE

9 SS 3 minutes after step 8 the value of T3212 is set to 6
minutes.
This message shall be sent by the UE between 5 minutes
45 s and 6 minutes 15 s after step 8.
COMPLETE

REQUEST
"location updating type": periodic updating.
COMPLETE

17 SS IMSI attach/detach is not allowed.
18 UE The UE is deactivated.
20 SS The SS waits until the periodic location updating.
This message shall arrive during the 6 minutes following
the UE activation.
COMPLETE

REQUEST
COMPLETE

None.
At step 10 the UE shall send an RRC CONNECTION REQUEST for a periodic location updating.
At step 21 the UE shall send an RRC CONNECTION REQUEST for a periodic location updating.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1775
9.4.5.2 Location updating / periodic normal / test 1
1 The UE shall stop and reset the timer T3212 of the periodic location updating procedure when the first MM
message is received or SECURITY mode setting is completed in the case of MM connection establishment.
2 The UE shall stop and reset the timer T3212 of the periodic location updating procedure when the UE has
responded to paging and thereafter has received the first correct L3 message that is not an RRC message.
References
TS 24.008 clause 4.4.2.
To verify that the UE stops and resets the timer T3212 of the periodic location updating procedure when:
- the first MM-message is received in the case of MM-connection establishment, security mode being not set;
- the UE has responded to paging and the first correct L3 message that is not an RRC message is received.
NOTE: T3212 is stopped when the MM-idle state is left and restarted when the MM sublayer returns to that state,
substate NORMAL SERVICE or ATTEMPTING TO UPDATE. As a consequence, the exact time when
T3212 is reset between those two events cannot be tested.
Initial conditions
- System Simulator:
- 1 cell, default parameters;
- IMSI attach/detach is not allowed;
- the T3212 time-out value is 2/10 hour.
- User Equipment:
- the UE has a valid TMSI. It is "idle updated".
None.
Test procedure
An UE originated MM connection is established and cleared. The RRC CONNECTION is released. It is checked that
the UE performs a periodic location updating 12 minutes after the release of the RRC CONNECTION.
One minute after the periodic location updating, the UE is paged, it sends a RRC CONNECTION REQUEST message
and the SS responds with an RRC CONNECTION SETUP message, a call is established and then cleared. It is checked
that the UE performs a periodic location updating 12 minutes after the release of the link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1776
Expected sequence
UE SS
2 Void
3 Void
4 Void
5 CM SERVICE REQUEST
8 Void
to "Registration".
This message shall arrive between 11 minutes 45 s and
12 minutes 15 s after the last release of the RRC
connection by the SS.
11 Void
12 Void
REQUEST
16 Void
17 SS The SS waits 1 minute.
"Mobile identity" =IMSI.
"Establishment cause": Terminating Conversational Call.
19 PAGING RESPONSE
23 Void
to "Registration".
This message shall arrive between 11 minutes 45 s and
12 minutes 15 s after the last release of the RRC
connection by the SS.
26 Void
27 Void
REQUEST
31 Void

None.
At step 10 the UE shall initiate an RRC CONNECTION REQUEST 12 minutes after the release of the RRC
CONNECTION (at step 7).
At step 25 the UE shall initiate an RRC CONNECTION REQUEST 12 minutes after the release of the RRC
CONNECTION (at step 22).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1777
9.4.5.3 Location updating / periodic normal / test 2
When a LOCATION UPDATING ACCEPT or a LOCATION UPDATING REJ ECT message is received, the timer
T3212 is stopped and reset and the UE shall perform a periodic location updating after T3212 expiry.
References
TS 24.008 clause 4.4.2.
To verify that the UE stops and resets the timer T3212 of the periodic location updating procedure when a LOCATION
UPDATING ACCEPT message is received.
NOTE: T3212 is stopped when the MM-idle state is left and restarted when the MM sublayer returns to that state,
substate NORMAL SERVICE or ATTEMPTING TO UPDATE. As a consequence, the exact time when
T3212 is reset between those two events cannot be tested.
Initial conditions
- System Simulator:
- 2 cells, IMSI attach/detach is allowed in both cells;
- T3212 is set to 6 minutes;
- two cells: A and B of the same PLMN, belonging to different location areas with LAI a and b.
- User Equipment:
Switch off on button yes/No.
Test procedure
A normal location updating is performed. The RRC CONNECTION is released. One minute later, the UE is
deactivated, then reactivated in the same cell. It is checked that the UE performs an IMSI attach and a periodic location
updating 6 minutes after the IMSI attach.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1778
Expected sequence
UE SS
on cell B.
(see note)
2 SS The SS verifies that the IE "establishment cause" in the
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
"location updating type" =normal.
8 Void
to "Registration".
This message shall arrive between 5 minutes 45s and 6
minutes 15 s after the last release of the RRC connection
by the SS.
11 Void
12 Void
REQUEST
16 Void
17 UE If possible (see ICS) USIM removal is performed.
Otherwise the power is removed. steps 18 to 23 may be
performed or not depending on the action made in step
17.
to "Detach".
19 Void
20 Void
23 Void
to "Registration".
26 Void
27 Void
REQUEST
"Location updating type" =IMSI attach.
31 Void
to "Registration".
This message shall arrive between 5 minutes 45 s and 6
minutes 15s after the last release of the RRC connection
by the SS.
34 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1779
UE SS
35 Void
REQUEST
39 Void

None.
After step 28 the UE shall performs an IMSI attach.
After step 33 the UE shall performs periodic location updating 6 minutes after step 28.
9.4.5.4 Location updating / periodic search for HPLMN or higher priority PLMN when
in VPLMN
9.4.5.4.1 Location updating / periodic search for HPLMN or higher priority PLMN / UE waits
time T
1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only select a PLMN if it is of a
higher priority than those of the same country as the current serving PLMN which are stored in the "Equivalent
PLMNs" list.
2. In steps i), ii) and iii) of the Automatic Network Selection Mode Procedure, the MS shall limit its attempts to
access higher priority PLMNs to PLMNs of the same country as the current serving VPLMN;
3. If the MS is in idle mode in a VPLMN, the MS shall periodically attempt to obtain service on its HPLMN or
higher priority PLMN listed in "user controlled PLMN selector" or "operator controlled PLMN selector". The
MS shall make an attempt if the MS is on the VPLMN at time T after the last attempt.
References
TS 22.011 clause 3.2.2.5. and TS 23.122 4.4.3.3.
To verify that if a UE is camped on a VPLMN it will perform a search for higher priority networks (e.g HPLMN) with a
periodicity of T, which is the Search Period stored in the USIM.
This test will confirm that, if a cell from a new PLMN becomes available, within a time T the UE will perform a
location updating on it only if the following requirements are met:
- The PLMN of this new cell if from the same country as the VPLMN, and
- This PLMN is the HPLMN stored in the USIM, or has a higher priority than the serving VPLMN or any PLMN
from the country of the VPLMN that is stored in the equivalent PLMN list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1780
Initial conditions
- System Simulator:
- four cells A, B, C and D, belonging to different location areas with location identification a, b, c and d. Their
country codes and mobile network codes are defined as follows:
Cell MCC MNC
A 001 001
B 022 002
C 001 010
D 001 100

Initially Cells A, B and C shall not be broadcasting. IMSI attach/detach is not allowed on any of other cells.
- User Equipment:
- the UE is switched off. The HPLMN Search Period on the USIM shall be set to 6 minutes. The location area
information on the USIM is "deleted".
- The following USIM fields are configured:
EFHPLMNwAcT 1
st
A
EFPLMNwAcT 1
st
B
2
nd
E
EFOPLMNwAcT 1
st
C
2
nd
D

In the table PLMN X is the PLMN code from cell X (see above). PLMN E is defined as MCC=001,
MNC=030.
Switch on/off button Yes/No.
Test Procedure
Only Cell D shall be broadcasting. The UE shall be switched on either by using the Power Switch or by applying power.
A normal location updating is performed on Cell D. The SS shall include the PLMN E in the list of equivalent PLMNs
that is sent in the Location Update Accept message. Cells B and C shall be made available after 7 minutes from
switched on, thus ensuring the UE fails to find any higher priority PLMN during its first attempt. It is verified that the
UE does not perform a location update request on Cell B or C (waiting for at least 6 minutes after broadcasting of Cells
B and C). Then Cell A is also made available, and it is verified that the UE performs a location update request on Cell A
within 6 minutes after broadcasting of Cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1781
Expected sequence
Step Direction Message Contents
UE SS
Cell D.
1 SS Set the cell type of Cell A to the "non-suitable cell".
Set the cell type of Cell B to the "non-suitable cell".
Set the cell type of Cell C to the "non-suitable cell".
Set the cell type of Cell D to the "Suitable neighbour cell".
(see note)
1a UE The UE is switched on by either using the Power Switch
or by applying power.
to "Registration".
3 Void
4 Void
5 LOCATION UPDATING
REQUEST
"Location Update Type": Normal.
6 LOCATION UPDATING ACCEPT "Equivalent PLMNs": PLMN E
8 Void
8a SS The SS waits a period of 7 minutes after the UE is
switched on, this allowing the UE to make its first periodic
search.
8b SS Set the cell type of cell B to the "Suitable neighbour cell".
Set the cell type of cell C to the "Suitable neighbour cell".
(see note)

8c SS The SS shall wait for 7 minutes during which no
messages should be received.
(see note)
Within 6 minutes after step 9, the following messages
shall be sent and received on Cell A.
to "Registration".
11 Void
12 Void
REQUEST
"Location Update Type": normal.
16 Void
NOTE: The definitions for "Suitable neighbour cell" and "non-suitable cell"are specified in TS 34.108 clause 6.1

None.
9.4.5.4.1.5 Test requirement
1. At step 8c, the UE shall not send any LOCATION UPDATING REQUEST on cell C.
2. At step 8c, the UE shall not send any LOCATION UPDATING REQUEST on cell B.
3. At step 13 the UE shall send a LOCATION UPDATING REQUEST message on Cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1782
9.4.5.4.2 Location updating / periodic search for HPLMN or higher priority PLMN / UE in
manual mode
The periodic attempts shall only be performed if in automatic mode when the UE is in a VPLMN.
References
TS 22.011 clause 3.2.2.5. and TS 23.122 clause 4.4.3.3.
To verify that no Search for HPLMN or Higher Priority PLMN is performed when the UE is not in automatic mode.
Initial conditions
- System Simulator:
- two cells A and B, belonging to different location areas with location identification a and b. Cell A shall be a
cell of the HPLMN and Cell B shall be a cell of the VPLMN with a Country Code the same as that of Cell A.
Initially Cell A shall not be broadcasting. IMSI attach/detach is not allowed on either cell.
NB: i) Cell B will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.
- User Equipment:
Test Procedure
Only Cell B shall be broadcasting. The UE shall be switched on either by using the Power Switch or by applying power.
A normal location updating is performed on Cell B. The UE is forced into manual selection mode. Cell A is made
available. It is verified that the UE does not attempt to perform a location update on Cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1783
Expected sequence
UE SS
Cell B.
Set the cell type of Cell B to the "Serving cell".
(see note)
COMPLETE

5 LOCATION UPDATING
REQUEST
7 RRC CONNECTION RELEASE After sending this message the SS waits for the
COMPLETE

9 UE The UE is forced into manual selection mode.
(see note)
11 SS The SS waits a period of 6 minutes. During this time no
messages shall be received on Cell A.

None.
At step 11 the UE shall not attempt to perform a location update.
9.4.5.4.3 Location updating / periodic search for HPLMN or higher priority PLMN / UE waits
at least two minutes and at most T minutes
After switch on, the UE waits at least 2 minutes and at most T minutes before the first Search for HPLMN or higher
priority PLMN is attempted.
References
TS 22.011 clause 3.2.2.5. and TS 23.122 4.4.3.3.
To verify that the UE waits at least 2 minutes and at most T minutes before attempting its first Search for HPLMN or
higher priority PLMN.
Initial Conditions
- System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1784
- two cells A and B, belonging to different location areas with location identification a and b. Cell A shall be a
cell of the HPLMN and Cell B shall be a cell of the VPLMN with a Country Code the same as that of Cell A.
Initially Cell A shall not be broadcasting. IMSI attach/detach is not allowed on either cell.
- User Equipment:
Test Procedure
Only Cell B shall be broadcasting. The UE shall be switched on either by using the Power Switch or by applying power.
A normal location updating is performed on Cell B. Cell A is made available. It is verified that the UE attempts to
perform a location update on Cell A, after at least 2 minutes and at most T minutes have passed following power on.
Expected sequence
UE SS
Cell B.
Set the cell type of Cell B to the "Serving cell".
(see note)
COMPLETE

5 LOCATION UPDATING
REQUEST
COMPLETE

(see note)
10 SS The SS waits a period of 2 minutes after the UE is
switched on. During this time no messages shall be
received on Cell A. The following messages shall be sent
and received on cell A. Within 6 minutes after the UE is
switched on the following messages shall be sent and
received on cell A.
11 RRC CONNECTION REQUEST "Establishment cause": Registration. This message shall
be sent between 2 and 6 minutes after step 1
COMPLETE

REQUEST
COMPLETE


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1785
None.
At step 11 the UE shall attempt to perform a location update.
9.4.6 Location updating / interworking of attach and periodic
9.4.6.1 Definition
1) If the UE is in service state NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH or PLMN
SEARCH-NORMAL SERVICE when the timer T3212 expires the location updating procedure is delayed until
this service state is left.
2) The T3212 time-out value shall not be changed in the NO CELL AVAILABLE, LIMITED SERVICE, PLMN
SEARCH and PLMN SEARCH-NORMAL SERVICE states.
3) If the selected cell is in the location area where the UE is registered and IMSI ATTACH is not required and
timer T3212 has not expired, then the state is NORMAL SERVICE.
References
1) TS 24.008 clause 4.4.2.
2) TS 24.008 clause 4.4.2.
3) TS 24.008 clause 4.2.1.1.
1) To check that if the PLU timer expires while the UE is out of coverage, the UE informs the network of its return
to coverage.
2) To check that the PLU timer is not disturbed by cells of forbidden PLMNs.
3) To check that if the PLU timer does not expire while out of coverage and if the mobile returns to the LA where it
is updated, the UE does not inform the network of its return to coverage.
Initial conditions
- System Simulator:
- two cells, a and b, of different PLMNs;
- T3212 is set to 12 minutes on cell a;
- T3212 is set to 6 minutes on cell b;
- IMSI attach is allowed in both cells.
NB: i) Cell b will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.
- User Equipment:
- the UE is deactivated. The PLMN of cell b is entered in the USIM's forbidden PLMN list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1786
None.
Test procedure
The UE is activated and placed in automatic network selection mode. It performs IMSI attach. 1 minute after the end of
the IMSI attach procedure, cell a is made unavailable. The UE shall not location update on cell b. 8 minutes after the
end of the IMSI attach procedure, cell a is made available. The UE shall not location update on cell a before 11,75
minutes after the end of the IMSI attach procedure. The UE shall perform a periodic location update on cell a between
11,75 minutes and 12,25 minutes after the end of the IMSI attach procedure.
3 minutes after the end of the periodic location updating procedure, cell a is made unavailable. The UE shall not
location update on cell b. 14 minutes after the end of the periodic location updating procedure, cell a is made available
and cell b is made unavailable. The UE shall perform a location update on cell a before 17 minutes after the end of the
periodic location updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1787
Expected sequence
UE SS
on cell A.
(see note)
1a UE The UE is activated in automatic network selection mode.
COMPLETE

5 LOCATION UPDATING
REQUEST
"location updating type": IMSI attach.
COMPLETE

9 SS The SS waits 1 minute after step 8.
(see note)
10 SS The SS waits 8 minutes after step 8.
Set the cell type of cell A to the "Serving cell".
(see note)
11 RRC CONNECTION REQUEST This message shall be sent by the UE between 11
minutes 45s and 12 minutes 15s after step 8.
COMPLETE

REQUEST
"location updating type": periodic.
COMPLETE

(see note)
(see note)
20 RRC CONNECTION REQUEST This message shall be sent by the UE before 17 minutes
after step 17.
COMPLETE

REQUEST
COMPLETE

establishment. This is checked during 12 minutes.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1788
1) At step 20 the UE shall send an RRC CONNECTION REQUEST and at step 23 the UE shall attempt to perform
a location update.
2) At step 11 the UE shall send an RRC CONNECTION REQUEST and at step 14 the UE shall attempt to perform
a location update.
3) At step 27 the UE shall not initiate an RRC connection during 12minutes.
9.4.7 Location Updating / accept with replacement or deletion of
Equivalent PLMN list
9.4.7.1 Definition
Test to verify that the UE replaces or deletes its stored Equivalent PLMN list when no Equivalent PLMN list is included
in the LOCATION UPDATING ACCEPT message from the network during a Location Update.
1) The stored list in the mobile station shall be replaced on each occurrence of the LOCATION UPDATING
ACCEPT message.
2) If no equivalent PLMN list is contained in the LOCATION UPDATING ACCEPT message, then the stored
equivalent PLMN list in the mobile station shall be deleted.
References
TS 24.008 4.4.4.6
1) To verify that the UE replaces its stored equivalent PLMN list if the equivalent PLMN list is contained in the
LOCATION UPDATING ACCEPT message received from the network during a location updating procedure.
2) To verify that the UE deletes its stored equivalent PLMN list if no equivalent PLMN list is contained in the
LOCATION UPDATING ACCEPT message received from the network during a location updating procedure.
Initial conditions:
- System Simulator:
- two cells: A and B, with different PLMN Codes (PLMN 1 and PLMN 2 respectively).
- User Equipment:
- the UE is switched off. The HPLMN is PLMN 3 and no other information about PLMN priorities or
forbidden PLMNs is stored in the USIM. The equivalent PLMN list in the mobile station is empty.
- the UE is "Idle updated" on cell B.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1789
Test procedure
When the UE is initially switched on it will perform a normal location updating in Cell A, which is the only suitable cell
available. The LOCATION UPDATING ACCEPT message sent by the SS on reception of the LOCATION
UPDATING REQUEST message shall include PLMN 2 in the equivalent PLMN list. When Cell B is made available
and its RF signal level is higher than that of Cell A the UE will perform a normal location updating in this cell. The
LOCATION UPDATING ACCEPT message sent by the SS shall include PLMN 1 in the equivalent PLMN list. When
Cell B is made unavailable the UE shall perform a normal location updating again in Cell A, but in this ocassion the
LOCATION UPDATING ACCEPT message shall contain an empty equivalent PLMN list. When Cell B is made
available again and its RF signal level is higher than that of Cell A the UE shall not perform a normal location updating
in this cell since it is not in the ePLMN list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1790
Expected Sequence
UE SS
Cell A
1 SS Set the cell type of Cell A to the "Suitable neighbour cell".
Set the cell type of Cell B to the "non-suitable cell".
(see note)
2 UE The UE is switched on by either using the Power Switch
3 SS RRC CONNECTION REQUEST The IE "Establishment cause" in the received RRC
CONNECTION REQUEST message is not checked.
4 Void
5 Void
6 LOCATION UPDATING
REQUEST
7 LOCATION UPDATING ACCEPT Equivalent PLMNs: PLMN 2
9 Void
Cell B.
10 SS Set the cell type of Cell B to the "Serving cell".
(see note)
to "Registration".
12 Void
13 Void
REQUEST
15 LOCATION UPDATING ACCEPT Equivalent PLMNs : PLMN 1
17 Void
Cell A.
18 SS Set the cell type of Cell B to the "non-suitable cell".
(see note)
to "Registration".
20 Void
21 Void
REQUEST
23 LOCATION UPDATING ACCEPT Equivalent PLMNs : empty
25 Void
26 SS Set the cell type of Cell B to the "Serving cell".
(see note)
27 SS The SS shall wait for 7 minutes during which no

None.
9.4.7.5 Test requirements
1) At step 14 the UE shall perform a normal location updating in Cell B.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1791
2) At step 27 the UE shall not perform a normal location updating in Cell B.
9.4.8 Location Updating after UE power off
9.4.8.1 Definition
Test to verify that the UE stores the equivalent PLMN list at UE power off and uses the stored equivalent PLMN list
after UE switch on.
The equivalent PLMN list shall be stored in the mobile station while switched off so that it can be used for PLMN
selection after switch on.
References
TS 24.008 4.4.4.6
To verify that the UE stores the equivalent PLMN list at UE switch off and uses the stored equivalent PLMN list after
UE switch on.
Initial conditions
- System Simulator:
- three cells: A, B and C. Cell A belongs to PLMN1 which is HPLMN. Cell B belongs to PLMN2. Cell C
belongs to PLMN3.
ii) Cell C will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.
- User Equipment:
- the UE is switched off;
- the UE is in automatic mode for PLMN selection,
- the UE is equipped with a USIM containing default values except for those listed below.

EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 1
EFPLMNwAcT Empty
EFOPLMNwAcT 1
st
PLMN 3
2
nd
PLMN 2

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1792
Test procedure
When the UE is initially swiched on it will perform a normal location updating in Cell A, which is the only suitable cell
available and belongs to the HPLMN. The LOCATION UPDATING ACCEPT message sent by the SS shall include
PLMN2 in the equivalent PLMN list. The UE shall be swiched-off. Cell A shall be made unavailable and Cells B and C
shall be made available. When the UE is switched-on again, the UE shall perform a normal location updating in Cell B
and not in Cell C because PLMN2 is stored in the UE equivalent PLMN list.
Expected Sequence
UE SS
Cell A
1 SS Set the cell type of Cell A to the "Serving cell".
Set the cell type of Cell B and Cell C to the "non-suitable
cell".
(see note)
to "Registration".
4 Void
5 Void
6 LOCATION UPDATING
REQUEST
7 LOCATION UPDATING ACCEPT Equivalent PLMN List: PLMN 2
9 UE If possible (see ICS) switch off is performed. Otherwise
the power is removed. Steps 9a to 9c may be performed
or not depending on the action made in step 9.
9a SS The SS verifies that the IE "Establishment cause" in the
to "Detach".
9b IMSI DETACH INDICATION
9c SS The SS releases the RRC connection.
Cell B.
10 Void
Set the cell type of Cell B to the "suitable neighbour cell".
Set the cell type of Cell C to the "suitable neighbour cell".
(see note)
12 UE
Depending on what has been performed in step 9 the UE
is brought back to operation.
to "Registration".
14 Void
15 Void
REQUEST
16a The SS starts integrity protection.
19 Void

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1793
At step 16 the UE shall perform a normal location updating in Cell B.
9.4.9 Location Updating / Accept, Interaction between Equivalent PLMNs
and Forbidden PLMNs.
9.4.9.1 Definition
Test to verify that, before storing the 'equivalent PLMN list' received from the network during a Location Update, the
UE removes any PLMN already included in the 'forbidden PLMN list'. Consequently the UE shall not select a PLMN
Equivalent to the registered PLMN if it is included in the 'forbidden PLMN list' in the USIM.
The mobile station shall store the equivalent PLMS list, as provided by the network, except that any PLMN code that is
already in the "forbidden PLMN list" shall be removed from the "equivalent PLMNs" list before it is stored by the
mobile station.
References
TS 24.008, 4.4.4.6
To verify tha the UE shall not select a forbidden PLMN even though it is included in the equivalent PLMN list provided
by the network because forbidden PLMNs shall not be stored in the mobile's equivalent PLMN list.
Initial conditions
- System Simulator:
- two cells: A, and B. Cell A belongs to PLMN1. Cell B belongs to PLMN2.
- User Equipment:
- the UE is switched off;
- the UE is in automatic PLMN selection mode.
- the UE is equipped with a USIM containing default values except for those listed below.
EFLOCI PLMN 1
EFHPLMNwAcT 1
st
PLMN 3
EFPLMNwAcT 1
st
PLMN 2
EFFPLMN PLMN 2

Test procedure
Cells A and B are made available. When the UE is swiched-on it will perform a normal location updating in Cell A,
since Cell B belongs to a forbidden PLMN. The SS will respond sending a LOCATION UPDATING ACCEPT
message that includes PLMN2 in the equivalent PLMN list. However the UE shall not store PLMN 2 in its equivalent
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1794
PLMN list as it is a forbidden PLMN. Therefore, when Cell A is made unavailable the UE will not select the only
remaining cell (Cell B), remaining in limited service state.
Expected Sequence
UE SS
Cell A
1 SS Set the cell type of Cell A to the "Suitable neighbour cell".
Set the cell type of Cell B to the "Suitable neighbour cell".
(see note)
to "Registration".
4 Void
5 Void
6 LOCATION UPDATING
REQUEST
7 LOCATION UPDATING ACCEPT Equivalent PLMN List: PLMN 2
9 Void
(see note)
11 SS The SS shall wait for 7 minutes during which no
NOTE: The definitions for "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1

None.
At step 11 the UE shall not perform a normal location updating in Cell B.
9.5 MM connection
9.5.1 Introduction
[tbd]
9.5.2 MM connection / establishment in security mode
9.5.2.1 Definition
1) The UE shall be able to correctly set up an MM connection in a Mobile Originating CM connection attempt and
send a CM SERVICE REQUEST message with CKSN information element as stored in the USIM and Mobile
Identity information element set to the TMSI.
2) The UE shall be able to interpret security mode setting as acceptance of its CM service request i.e. send a CM
message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1795
References
TS 24.008 clause 4.5.1.1.
To verify that the UE can correctly set up an MM connection in an origination and interpret security mode setting as
acceptance of its CM service request.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
A mobile originating CM connection is initiated. After the UE has sent the CM SERVICE REQUEST message to the
SS, an authentication procedure and a security mode setting procedure are performed. Then, the UE sends a CM
message and the SS clears the call and releases the RRC CONNECTION.
Expected sequence
UE SS
2 Void
3 Void
4 Void
9 Void
A10 SETUP
A11 RELEASE COMPLETE "Cause" IE: "unassigned number".
B10 REGISTER
B11 RELEASE COMPLETE
C10 CP-DATA
C11 CP-ACK
C12 CP-DATA
C13 CP-ACK
15 Void

None.
At step 5 the UE shall send the CM SERVICE REQUEST message to the SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1796
At step A10 or B10 or C10 the UE shall send a CM message and the SS shall release the RRC connection (step 14).
9.5.3 Void
9.5.4 MM connection / establishment rejected
9.5.4.1 Definition
If a CM SERVICE REJ ECT message is received by the mobile station, timer T3230 shall be stopped, the requesting
CM sublayer entity informed. Then the mobile station shall proceed as follows:
- If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was
received). Other MM connections shall not be affected by the CM SERVICE REJ ECT message.
References
TS 24.008 clause 4.5.1.1.
To verify that the UE stops timer T3230, informs the requesting CM sublayer entity and returns to the previous state.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
A mobile originating CM connection is attempted. After the UE has sent the CM SERVICE REQUEST message to the
SS, the SS responds with a CM SERVICE REJ ECT message with reject cause "requested service option not
subscribed". It is checked that the UE does not send a layer 3 message via the rejected MM connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1797
Expected sequence
UE SS
1 UE A MO CM connection is attempted
2 Void
3 Void
4 Void
5 CM SERVICE REQUEST A mobile originating CM connection is attempted
6 CM SERVICE REJ ECT "Reject cause" IE: "requested service option not
subscribed".
7 SS The UE shall not send a layer 3 message. This is
checked during 5 s.
Note: During this period, a new mobile originating
CM connection should not be attempted, since
then UE would send a new CM SERVICE
REQUEST.
8 SS SS releases the RRC connection.

None.
The UE shall attempt MO CM connection (step 1).
At step 5 the UE shall send a CM SERVICE REQUEST.
After step 6 the UE shall not send a layer 3 message.
9.5.5 MM connection / establishment rejected cause 4
9.5.5.1 Definition
The CM SERVICE REQUEST message contains the:
- mobile identity according to clause 10.5.1.4;
- mobile station classmark 2;
- ciphering key sequence number; and
- CM service type identifying the requested type of transaction (e.g. mobile originating call establishment,
emergency call establishment, short message service, supplementary service activation, location services)

If a CM SERVICE REJ ECT message is received by the mobile station, timer T3230 shall be stopped, the requesting
CM sublayer entity informed. Then the mobile station shall proceed as follows:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1798

- If cause value #4 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and
ciphering key sequence number in the SIM, changes the update status to NOT UPDATED (and stores it in the
SIM according to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If
subsequently the RR connection is released or aborted, this will force the mobile station to initiate a normal
location updating). Whether the CM request shall be memorized during the location updating procedure, is a
choice of implementation.
References
TS 24.008 clause 4.5.1.1.
To verify that the UE can correctly set up an MM connection in a Mobile Originating CM connection attempt and send
a CM SERVICE REQUEST message with CKSN information element as stored in the USIM and Mobile Identity
information element set to TMSI.
To verify that the UE, when receiving a CM SERVICE REJ ECT message with reject cause "IMSI unknown in VLR"
shall wait for the network to release the RRC connection.
To verify that the UE shall then perform a normal location updating procedure.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
SS, the SS responds with a CM SERVICE REJ ECT message with reject cause "IMSI unknown in VLR". On receipt of
this message, the UE shall delete any TMSI, LAI, cipher key and cipher key sequence number. The RRC
CONNECTION is released. It is checked that the UE performs a normal location updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1799
Expected sequence
UE SS
2 Void
3 Void
4 Void
6 CM SERVICE REJ ECT "Reject cause" ="IMSI unknown in VLR".
8 Void
9 SS SS verifies that the IE "Establishment cause" in the
to: "Registration".
10 Void
11 Void
REQUEST
"Ciphering key sequence number" ="No key is
available". "Mobile identity" =IMSI. "Location area
identification" =deleted LAI (the MCC and MNC hold the
previous values, the LAC is coded FFFE).
15 LOCATION UPDATING ACCEPT "Mobile identity" =new TMSI.
COMPLETE

18 Void

None.
1) The UE shall attempt MO CM connection (at step 1) and at step 5 the UE shall send a CM SERVICE REQUEST
message with CKSN information element as stored in the USIM and Mobile Identity information element set to
the TMSI.
2) At step 6 the SS should send a CM SERVICE REJ ECT message with reject cause "IMSI unknown in VLR", and
at step 9 the UE shall initiate RRC connection establishment with establishment cause set to "Registration".
3) At step 12 the UE send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its
IMSI, CKSN IE set to "no key is available" and the Location Updating type set to "deleted LAI".
9.5.6 MM connection / expiry T3230
9.5.6.1 Definition
At T3230 expiry (i.e. no response is given but an RRC connection is available) the MM connection establishment shall
be aborted.
References
TS 24.008 clauses 4.5.1.2 and 11.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1800
To verify that at T3230 expiry, the UE aborts the MM-connection establishment.
Initial conditions
- System Simulator:
- User Equipment:
None.
Test Procedure
SS, the SS waits for expiry of timer T3230. It is checked that the UE send a MM STATUS message and waits for the
release of the RRC-connection.
Expected sequence
UE SS
COMPLETE

6 SS The SS waits for expiry of timer T3230.
7 CM SERVICE ACCEPT
8 MM STATUS "Reject cause" IE is "message type not compatible with
protocol state".
COMPLETE

None.
The UE shall attempt MO CM connection (step 1).
At step 8 the UE shall send a MM STATUS message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1801
9.5.7 MM connection / abortion by the network
9.5.7.1 MM connection / abortion by the network / cause #6
At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-
establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall
delete any TMSI, LAI and ciphering key sequence number stored in the SIM, set the update status to ROAMING NOT
ALLOWED (and store it in the SIM according to clause 4.1.2.2) and consider the SIM invalid until switch off or the
SIM is removed. As a consequence the mobile station enters state MM IDLE, substate NO IMSI after the release of the
RR connection.
The mobile station shall then wait for the network to release the RR connection - see clause 4.5.3.1.
Reference(s)
TS 24.008 clause 4.3.5.2.
To check that upon reception of an ABORT message with cause #6 during call establishment:
- the UE does not send any layer 3 message;
- after reception of an ABORT message and after having been deactivated and reactivated, the UE performs
location updating using its IMSI as mobile identity and indicates deleted LAI and CKSN;
- the UE does not perform location updating, does not answer to paging with TMSI, rejects any request for mobile
originating call except emergency call, does not perform IMSI detach;
- the UE accepts a request for emergency call.
Initial Conditions
- System Simulator:
- 2 cells, default parameters.
- User Equipment:
- the UE has a valid TMSI, CKSN and CK, IK. It is "idle updated" on cell B.
Test procedure
A mobile originating CM connection is attempted. Upon reception of the AUTHENTICATION RESPONSE message,
the SS sends an ABORT message with cause #6. The SS waits for 5 s. The UE shall not send any layer 3 message. The
SS releases the RRC connection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1802
The SS checks that the UE has entered the state MM IDLE substate NO IMSI, i.e. does not perform normal location
updating, does not perform periodic updating, does not respond to paging, rejects any requests from CM entities except
emergency calls and does not perform IMSI detach if deactivated.
Expected Sequence
UE SS
The following messages are sent and shall be received on cell B

1 UE A mobile originating CM connection is attempted.
2 Void
3 Void
4 Void
5 CM SERVICE REQUEST CKSN =initial value, Mobile identity =TMSI
8 ABORT "reject cause" =#6.
9 SS The SS waits for 5 s.
10 UE The UE shall not send any layer 3 message during that
time.
12 Void

(see note)
updating.
17 PAGING TYPE 1 "UE identity" IE contains TMSI.
establishment on cell A or on cell B. This is verified
during 3 s.
during 3 s.
21 UE If the UE supports speech (see ICS), an emergency call
is attempted.
to: "Emergency call".
23 Void
24 Void
CKSN =No key is available, Mobile identity =IMEI
27 EMERGENCY SETUP
30 Void
during 3 s.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1803
UE SS
to: "Registration".
35 Void
36 Void
REQUEST
available, "Mobile Identity" =IMSI, "LAI" =deleted LAI
(the MCC and MNC hold the previous values, the LAC is
coded FFFE).
39a SS The SS starts integrity protection
COMPLETE

43 Void

None.
1) At step 10 the UE shall not send any layer 3 message.
2)
2.1 At step 14 the UE shall not initiate an RRC connection establishment (not perform normal location updating).
2.2 At step 16 the UE shall not initiate an RRC connection establishment.(not perform periodic location
updating).
2.3 At step 18 the UE shall not initiate an RRC connection establishment (not respond to paging with TMSI).
2.4 At step 20 the UE shall not initiate an RRC connection establishment (reject any request for Mobile
Originating call establishment).
2.5 At step 32 the UE shall not initiate an RRC connection establishment.(not perform IMSI detach).
3) At step 22 the UE shall initiate RRC connection establishment with the establishment cause set to "emergency
call".
4) At step 37 the UE send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its
IMSI, CKSN IE set to "no key is available" and the Location Updating type set to "deleted LAI".
9.5.7.2 MM connection / abortion by the network / cause not equal to #6
At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-
establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall
delete any TMSI, LAI and ciphering key sequence number stored in the USIM, set the update status to ROAMING
NOT ALLOWED (and store it in the USIM according to TS 24.008 clause 4.1.2.2) and consider the USIM invalid until
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1804
switch off or the USIM is removed. As a consequence the mobile station enters state MM IDLE, substate NO IMSI
after the release of the RR connection.
The mobile station shall then wait for the network to release the RR connection - see TS 24.008 clause 4.5.3.1.
Reference(s)
TS 24.008 clause 4.3.5.
To check that when multiple MM connections are established, the UE releases all MM connections upon reception of an
ABORT message, in the case when the two MM connections are established for a mobile terminating call and a non call
related supplementary service operation.
To check that the TMSI is not deleted from UE after reseption of ABORT message with cause another than #6.
Initial Conditions
- System Simulator:
- User Equipment:
- the UE is in state U10 of a mobile terminating call.
The UE supports a non call related supplementary service operation during an active call Yes/No.
Test procedure
A non call related supplementary service operation is attempted at the UE. Upon reception of the REGISTER message,
the SS sends an ABORT message with cause #17. The SS waits for 5 s. The UE shall not send any layer 3 message.
The SS releases the RRC connection. The UE shall perform periodic location updating 6 minutes after the SS releases
the RRC connection. TMSI shall be used as Mobile Identity in LOCATION UPDATING REQUEST message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1805
Expected Sequence
This procedure is performed if the UE supports non call related supplementary service operation.
UE SS
1 UE A non call related supplementary service operation is
attempted at the UE.
2 Void
3 Void
4 Void
5 CM SERVICE REQUEST The SS verifies that the IE " CM service type" in the
received CM SERVICE REQUEST is set to
"Supplementary service activation".
6 CM SERVICE ACCEPT
7 REGISTER
8 ABORT "reject cause" =#17.
9 SS The SS waits for 5 seconds.The UE shall not send any
layer 3 message during that time.
9a Void
10 Void
11 SS The UE indicates the signalling connection release. The
SS releases the RRC connection.
12 Void
"Registration".This message shall be sent by the UE
between 5 minutes 45s and 6 minutes 15s after step 11.
REQUEST
"Location updating type" =periodic updating, "Mobile
Identity" =TMSI

None.
After step 8 the UE shall release all MM connections.
After step 12 the UE shall perform periodic location updating with TMSI used as Mobile Identity.
9.5.8 MM connection / follow-on request pending
9.5.8.1 MM connection / follow-on request pending / test 1
The UE shall not attempt to establish a new MM connection after location updating on the same RRC connection if not
allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1806
To check that when the network does not include the follow on proceed IE in a LOCATION UPDATING ACCEPT
message, a UE that has a CM application request pending does not attempt to establish a new MM connection on that
RRC connection.
Initial Conditions
- System Simulator:
- 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
- User Equipment:
- the UE has a valid TMSI and is deactivated.
None.
Test procedure
The UE is activated and a CM connection is attempted during the location updating procedure. The SS does not include
the follow on proceed information element in the LOCATION UPDATING ACCEPT message. The SS waits for at
least 8 s. The UE shall not send any layer 3 message for 8 s.
Expected Sequence
UE SS
COMPLETE

5 LOCATION UPDATING
REQUEST
location updating type =IMSI attach.
Then the SS waits for 15 s. During this delay a CM
connection is attempted.
6 LOCATION UPDATING ACCEPT follow on proceed IE not included.
7 SS The SS wait for at least 8 s.
8 UE The UE shall not send any layer 3 message for 8 s after
reception of the LOCATION UPDATING ACCEPT
message.
COMPLETE

None.
After step 8 the UE shall not send any layer 3 messages.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1807
A UE supporting the follow-on request procedure and having a CM connection request pending shall correctly establish
an MM connection following a location update when allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6.
To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a
UE that supports the follow on request procedure and that has a CM application request pending establishes
successfully a new MM connection on that RRC connection.
Initial Conditions
- System Simulator:
- User Equipment:
UE supports the follow on request procedure Yes/No.
Test procedure
The UE is activated and a CM connection is attempted during the location updating procedure. The SS includes the
follow on proceed information element in the LOCATION UPDATING ACCEPT message. The SS waits for at least
8 s.
If the UE supports the follow on request procedure:
- the UE shall send a CM SERVICE REQUEST. Upon reception of that message, the SS sends a CM SERVICE
ACCEPT message. The UE shall send an initial CM message. Upon reception of that message, the SS releases
the RRC connection.
If the UE does not support the follow on request procedure:
- the UE shall not send any layer 3 message for 8 s.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1808
Expected Sequence
UE SS
COMPLETE

5 LOCATION UPDATING
REQUEST
Location updating type =IMSI attach.
Then the SS waits for 15 s. During this delay a CM
connection is attempted.
6 LOCATION UPDATING ACCEPT follow on proceed IE included.
If the UE supports the follow on request procedure (see
ICS) steps A7 to A9 are performed, otherwise steps B7
to B8 are performed.
A7 CM SERVICE REQUEST
A8 CM SERVICE ACCEPT
A9 An initial CM message
B7 SS The SS wait for at least 8 s.
B8 UE The UE shall not send any layer 3 message for 8 s after
message.
COMPLETE

None.
After step 6:
The UE shall send a CM SERVICE REQUEST if the UE supports the follow on request procedure.
The UE shall not send any layer 3 message if the UE does not support the follow on request procedure.
1) The UE shall not set the follow on proceed IE in a LOCATION UPDATING REQUEST message if no MM
connection request is pending.
2) When the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE
that has no CM application request pending shall not attempt to establish a new MM connection on that RRC
connection.
3) The UE shall correctly handle a CM connection established by the network on the RRC connection that was used
for the location updating procedure.
Reference(s)
TS 24.008 clause 4.4.4.6.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1809
1) To check that a UE that has no CM application request pending sets the follow on proceed IE to No follow-on
request pending in a LOCATION UPDATING REQUEST message.
2) To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT
message, a UE that has no CM application request pending does not attempt to establish a new MM connection
on that RRC connection.
3) To check that the UE accepts establishment by the network of a new MM connection on the existing RRC
connection.
Initial Conditions
- System Simulator:
- User Equipment:
Supported services on TCH.
Test procedure
The UE is activated. The UE performs location updating. The UE shall set the follow on proceed IE to No follow-on
request pending in the LOCATION UPDATING REQUEST message. The SS includes the follow on proceed IE in the
LOCATION UPDATING ACCEPT message. The SS waits for 5 s. The UE shall not send any layer 3 message for 5 s.
The SS sends a SETUP message to the UE requesting a basic service supported by the UE. The UE shall send either a
CALL CONFIRMED message if it supports a service on TCH or a RELEASE COMPLETE with cause #88.
Expected Sequence
UE SS
COMPLETE

5 LOCATION UPDATING
REQUEST
"Location updating type" =IMSI attach. The FOR bit is
set to No follow-on request pending.
6 LOCATION UPDATING ACCEPT follow on proceed IE is included.
7 SS The SS wait for 5 s.
8 UE The UE shall not send any layer 3 message for 5 s after
message.
9 SETUP
If the UE supports a basic service on TCH.
A10 CALL CONFIRMED
If the UE does not support any basic service on TCH.
B10 RELEASE COMPLETE cause #88.
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1810
None.
At step 8 the UE shall not send any layer 3 message.
After step 9:
The UE shall send CALL CONFIRMED message if the UE supports a basic service on TCH.
The UE shall send RELEASE COMPLETE message if the UE does not support a basic service on TCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1811
10 Circuit Switched Call Control (CC)
10.1 Circuit switched Call Control (CC) state machine verification
10.1.1 General on CC state machine verification
The principle of checking the call control functions consists in the validation of each call control identified state.
State U0 as an initial state is not verified in the tests of 10.1.2 (establishment of an outgoing call).
State U0.1 is never verified.
The steps to be followed within each performed test are:
- bring the UE into the required state;
- trigger the tested event;
- check the UE response and new state.
In clauses 10.1.2 and 10.1.3 different tables are defined to bring the UE into the required initial state. The exact table to
be chosen is specified individually in clause "Initial conditions" of "Method of test" for each test case.
For each test, unless otherwise specified, a circuit switched basic service among those supported by the UE but
excluding the emergency call teleservice shall be chosen arbitrarily, and the test shall be performed according to that
basic service. If the only circuit switched basic service supported by the mobile is emergency call, then the incoming
call tests shall not be performed and the other call control tests shall be performed with the EMERGENCY SETUP
message replacing the SETUP message.
The initial states are to be checked through STATUS ENQUIRY messages sent by the SS, when feasible. This is not
explicitly stated in the tables of expected sequences of signalling messages. The checking of final states are explicitly
included into the expected sequences of signalling messages.
The following postamble may be used by the SS to bring UE back to idle mode in those test cases, in which it is not
already included into expected sequence of signalling messages:
Table 10.1.1/1: A postamble to bring the UE back to idle mode.
UE SS
N <-- RRC CONNECTION RELEASE
n+1 --> RRC CONNECTION RELEASE COMPLETE
n+2 UE the UE releases the RRC connection

The postamble has not been included into the all of the tests in order to leave an option to concatenate the procedures in
the future by using a final state of a test case as an initial state to another one.
For the special case of U0, the state is checked by sending STATUS ENQUIRY message with all possible values of
transaction identifier (seven values) as U0 is the only state in which for every TI the UE will answer with release
complete with cause #81. If U0 is to be verified when no RRC connection exists, first a mobile terminating radio
connection must be established.
The UE responses are either call management messages received by the SS or lower layers functions activated within
the UE or MMI actions (e.g. the buzzing of an alerting tone).
A time-out within the UE is triggered by the SS when it does not answer back an UE expected response.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1812
The test sequences may be split in 3 main groups:
- establishment and release of an outgoing call;
- establishment and release of an incoming call;
- in-call functions.
Some test cases use Basic Generic Procedures, "Mobile terminated establishment of Radio Resource Connection" and
"Radio Bearer Setup Procedure" defined in TS34.108 clause 7.
General tolerance value on protocol timers defined in TS34.108 is used in some test cases if no specific tolerance on
timer is defined in a test case.
Remark on verification of transient states
Some call control states of the user equipment may be transient, depending on implementation, configuration of the UE
and previous messages.
If a test starts in a transient state, then the test is executed without verification of the starting state.
10.1.2 Establishment of an outgoing call
Initial conditions
As a minimum requirement the UE is updated and has been given a TMSI, a ciphering key and cipher key sequence
number, and the layer 2, RRC and MM functionalities have been verified.
There are as many CM initial conditions as states to be checked.
The tables below describe message exchanges which bring the UE in the requested initial states.
A state may be taken as initial only when all the states which lead to this initial states have been validated. The order
followed in the test procedure will be U0, U0.1, U1, U3, U4, U10, U12, U19, U11 as seen in the table underneath.
The UE is brought again in the initial state starting with U0 at each new test performed.
Table 10.1.2/1: Establi shment of an outgoing call, procedure 1 (late assignment)
UE SS
1 Mobile Originated establishment of Radio Resource
Connection
Establishment cause: Originating
Conversational Call
2 Void
3 Void
4 -> CM SERVICE REQUEST U0.1
5 <- AUTHENTICATION REQUEST
6 -> AUTHENTICATION RESPONSE
7 <- SECURITY MODE COMMAND
8 -> SECURITY MODE COMPLETE
9 -> SETUP U1
10 <- CALL PROCEEDING U3
11 <- ALERTING U4
12 Radio Bearer Setup Procedure See TS 34.108 clause 7.1.3
13 <- CONNECT
14 -> CONNECT ACKNOWLEDGE U10
A15 <- DISCONNECT U12 (note 1)
B15 <- DISCONNECT U12 (note 2)
B16 -> RELEASE U19
C15 MMI action, terminate call
C16 -> DISCONNECT U11
NOTE 1: The Progress Indicator IE with progress description #8 "in band information or appropriate pattern now
available" is included.
NOTE 2: The Progress Indicator IE is not included.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1813
Table 10.1.2/2: Void
Table 10.1.2/3: Establi shment of an outgoing call, procedure 3
UE SS
ConnectionVoid
Conversational Call
2 Void
3 Void
4a <- AUTHENTICATION REQUEST
4b -> AUTHENTICATION RESPONSE
7 -> SETUP U1
8 Void
9 Void
12 <- ALERTING U4
13 <- CONNECT
B16 -> RELEASE U19
NOTE 2: The Progress indicator IE is not included.

Table 10.1.2/4: Establi shment of an outgoing call, procedure 4
UE SS
Connection
Conversational Call
2 Void
3 Void
5 <- IDENTITY REQUEST
6 -> IDENTITY RESPONSE
9 -> SETUP U1
10 Radio Bearer Setup Procedure See TS 34.108 clause 7.1.3 (note 1)
12 <- ALERTING U4
13 <- CONNECT
B16 -> RELEASE U19
NOTE 1: Assigned channel is appropriate for the chosen bearer capability (see 10.1).
NOTE 3: The Progress Indicator IE is not included.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1814
10.1.2.1 Outgoing call / U0 null state
10.1.2.1.1 Outgoing call / U0 null state / MM connection requested
The call control entity of the User Equipment requests the MM-sublayer to establish a mobile originating MM-
connection.
If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters MM
sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an establishment cause
and a CM SERVICE REQUEST message.
References
TS 24.008 clause 5.2.1.1 and clause 4.5.1.1
To verify that upon initiation of an outgoing basic call by user the UE initiates establishment of an MM connection,
using as first MM message a CM SERVICE REQUEST message with CM service type "Mobile originating call
establishment or packet mode connection establishment".
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the
selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to
initiate a call. When the SS receives CM SERVICE REQUEST, the contents of it shall be checked.
Expected sequence
UE SS
1 -> UE initiates outgoing call
2 Void
3 Void
4 -> CM SERVICE REQUEST SS shall verify the CM service type
requested by the UE
5 <- The SS releases the RRC connection.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1815
After step 3 the UE shall initiate establishment of an MM connection, using as first MM message a CM SERVICE
REQUEST message with CM service type "Mobile originating call establishment or packet mode connection
establishment".
10.1.2.2 Outgoing call / U0.1 MM connection pending
10.1.2.2.1 Outgoing call / U0.1 MM connection pending / CM service rejected
A request for MM connection is rejected by the SS.
If a CM SERVICE REJ ECT message is received by the UE, timer T3230 shall be stopped, the requesting CM sublayer
entity informed. Then the UE shall proceed as follows:
- If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was
received). Other MM connections shall not be affected by the CM SERVICE REJ ECT message.
- If cause value #4 is received, the UE aborts any MM connection, deletes any TMSI, LAI and ciphering key
sequence number in the SIM, changes the update status to NOT UPDATED (and stores it in the SIM according
to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the
RR connection is released or aborted, this will force the UE to initiate a normal location updating). Whether the
CM request shall be memorized during the location updating procedure, is a choice of implementation.
- If cause value #6 is received, the UE aborts any MM connection, deletes any TMSI, LAI and ciphering key
sequence number in the SIM, changes the update status to ROAMING NOT ALLOWED (and stores it in the
SIM according to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The
UE shall consider the SIM as invalid for non-GPRS services until switch-off or the SIM is removed.
References
TS 24.008, clause 4.5.1.1.
To verify that a CC entity of the UE in CC-state U0.1, "MM-connection pending", upon the UE receiving a CM
SERVICE REJ ECT message, returns to CC state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
The UE is brought into the state U0.1 by using table 10.1.2/1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1816
Test procedure
initiate a call. When the SS receives CM SERVICE REQUEST, the contents of it shall be checked. The SS rejects it by
CM SERVICE REJ ECT. The SS performs authentication and starts integrity. Then the SS will check the state of the UE
by using STATUS ENQUIRY with all the relevant transaction identifiers.
Expected sequence
UE SS
1 <- CM SERVICE REJ ECT
1c SS starts integrity
2 <- STATUS ENQUIRY
3 -> RELEASE COMPLETE cause shall be #81 (invalid TI value)
4 SS repeat steps 2-3 to cover all the
transaction identifiers from 000 ...110

None.
After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE
messages with cause value #81 (invalid TI value).
10.1.2.2.2 Outgoing call / U0.1 MM connection pending / CM service accepted
A CM request is accepted for the MM-connection by the SS.
Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity of the
UE sends a setup message to its peer entity. This setup message is
- a SETUP message, if the call to be established is a basic call.
It then enters the "call initiated" state.
References
TS 24.008 clause 5.2.1.
To verify that a CC entity of the UE in CC-state U0.1, "MM connection pending", after completion of the security mode
control procedure, sends a SETUP message specifying the Called party BCD number that was entered into the UE and
then enters CC state U1, "Call initiated".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1817
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. When the UE is requesting a MM-connection, the SS performs authentication and starts integrity. The UE
shall respond with SETUP. Then the SS will check the state of the call control entity by STATUS ENQUIRY with the
relevant transaction identifiers.
Expected sequence
UE SS
1 <- Void
1c SS starts integrity
2 -> SETUP with called party BCD number.
3 <- STATUS ENQUIRY
4 -> STATUS cause shall be #30 (response to enq.)
and state U1 call initiated.

None.
After step 1 the UE shall send a SETUP message specifying the Called party BCD number that was entered into the UE
and then enter CC state U1, "Call initiated".
10.1.2.2.3 Outgoing call / U0.1 MM connection pending / lower layer failure
The call control entity of the UE being in the state, U0.1, a lower layer failure is accomplished at the UE and
consequently, communication at layer 3 level with the peer entity is terminated.
1. RR connection failure or IMSI deactivation
If an RR connection failure occurs or the IMSI is deactivated during the establishment of an MM connection, the
MM connection establishment is aborted, timers T3230 is stopped, and an indication is given to the CM entity
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1818
that requested the MM connection establishment. This shall be treated as a rejection for establishment of the new
MM connection, and the MM sublayer shall release all active MM connections.
2. In CELL_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1 for the established
DPCCH physical channel in FDD, and the DPCH associated with mapped DCCHs in TDD, the UE shall:
1>start timer T313;
1>upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:
2>stop and reset timer T313.
1>if T313 expires:
2>consider it as a "Radio link failure".
Periods in time where neither "in sync" nor "out of sync" is reported by layer 1 do not affect the evaluation of the
number of consecutive (resp. successive) "in sync" or "out of sync" indications.
When a radio link failure occurs, the UE shall:
1>clear the dedicated physical channel configuration;
1>perform actions as specified for the ongoing procedure;
1>if no procedure is ongoing or no actions are specified for the ongoing procedure:
2>perform a cell update procedure according to subclause 8.3.1 using the cause "radio link failure".
2. In addition, the cell update procedure also serves the following purposes:

- to act on a radio link failure in the CELL_DCH state;
References
TS 24.008, clause 4.5.1.2 a), TS 25.331 clause 8.5.6 and 8.3.1.1.
To verify that the UE with a CC entity in state U0.1, "MM connection pending", aborts MM connection establishment,
stops timer T3230 and returns to idle mode in case an RR connection failure occurs.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1819
Test procedure
initiate a call. When the UE has sent a CM SERVICE REQUEST message, the SS release the DPCH configuration to
generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure.
The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE.
The SS checks that the UE does not initiate RRC connection establishment during 60 s.
Expected sequence
UE SS
1 SS SS release the DPCH configuration to
generate lower layer failure (radio link
failure)
2 -> CELL UPDATE CCCH
3 <- RRC CONNECTION RELEASE CCCH
4 SS For a period of 60 s the SS checks that
the UE does not initiate RRC connection
establishment (since it should not re-
attempt MM connection establishment).

None.
After step 4 the UE shall not initiate RRC connection establishment during 60 s.
10.1.2.3 Outgoing call / U1 call initiated
10.1.2.3.1 Outgoing call / U1 call initiated / receiving CALL PROCEEDING
The call control entity of the UE being in the state, U1, a CALL PROCEEDING message is sent by the SS.
Having entered the "call initiated" state, when the call control entity of the UE receives a CALL PROCEEDING
message, it shall enter the "mobile originating call proceeding" state.
References
TS 24.008, clauses 5.2.1.1, 5.2.1.2 and 5.2.1.3.
To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a CALL PROCEEDING message,
enters CC state U3, "Mobile originating call proceeding".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1820
Initial conditions
System Simulator:
User Equipment:
The UE is brought into the state U1 by using table 10.1.2/1.
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. The SS sends a CALL PROCEEDING message to the
UE. The SS checks by using the status enquiry procedure that the CC entity has entered the state U3.
Expected sequence
UE SS
1 <- CALL PROCEEDING tone generation not mandatory
2 <- STATUS ENQUIRY
3 -> STATUS cause #30, state U3

None.
After step 1 the UE shall enter CC state U3, "Mobile originating call proceeding".
10.1.2.3.2 Outgoing call / U1 call initiated / rejecting with RELEASE COMPLETE
The call control entity of the UE being in the state, U1, the call is rejected by a RELEASE COMPLETE message sent
by the SS.
A call control entity of the UE in any call control state shall, upon receipt of a RELEASE COMPLETE message from
its peer entity in the network: stop all running call control timers ; release the MM connection; and return to the "null"
state.
References
TS 24.008, clause 5.4.4.1.3.
1) To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a RELEASE COMPLETE
message with valid cause value, enters CC state U0, "Null".
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile originating transaction
identifiers are in state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1821
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. The SS sends a RELEASE COMPLETE message to
the UE. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the
relevant transaction identifiers.
Expected sequence
UE SS
1 <- RELEASE COMPLETE This test case does not require a
specific cause value. E.g. value #47,
resources unavailable, is a suitable
value
2 <- STATUS ENQUIRY
3 -> RELEASE COMPLETE cause #81 (invalid TI value)
transaction identifiers from 000...110
5 <- The SS releases the RRC connection.t

None.
10.1.2.3.3 Outgoing call / U1 call initiated / T303 expiry
The call control entity of the UE being in the state, U1, if no response is then received from the SS, timer T303 expires
at the UE side.
If timer T303 elapses in the "call initiated" state before any of the CALL PROCEEDING, ALERTING, CONNECT or
RELEASE COMPLETE messages has been received, the clearing procedure described in TS 24.008 clause 5.4 is
performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1822
References
TS 24.008, clause 5.2.1.1 and clause 5.4.
1) To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon expiry of T303 sends a
DISCONNECT message to its peer entity and enters state U11, "Disconnect request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. When T303 expires at the UE, the UE shall send
DISCONNECT. The SS checks by using the status enquiry procedure that the CC entity has entered the state U11,
disconnect request.
Expected sequence
UE SS
1 SS SS waits for T303 expiry.
2 -> DISCONNECT Shall be transmitted 30 s after the CM
SERVICE REQUEST, check the timer
T303 accuracy, see TS34.108 clause
4.2.3.
3 <- STATUS ENQUIRY
4 -> STATUS cause #30, status U11

None.
After step 1 upon expiry of timer T303 the UE shall send a DISCONNECT message and enter state U11, "Disconnect
request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1823
10.1.2.3.4 Outgoing call / U1 call initiated / lower layer failure
The call control entity of the UE being in the state, U1, a lower layer failure is accomplished at the UE and
The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM connection is
interrupted, the subsequent action of the MM sublayer (call re-establishment, see TS 24.008 clause 4.5.1.6, or local
release) will then depend on the decisions by the CM entities.
References
TS 24.008, clause 4.5.2.3 and 5.2.1.1, TS 25.331 clause 8.3.1 and clause 8.5.6.
To verify that after the UE with a CC entity in state U1 "Call initiated", has detected a lower layer failure and has
returned to idle mode, the CC entity is in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The UE is brought to the state U1. The SS modifies the scrambling code of downlink transmission (DL
DPCH) to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update
procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from
the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60
s. The SS will check that the UE will not send any message during 60 s.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1824
Expected sequence
UE SS
1 SS SS modifies the scrambling code of
DPCH for generating lower layer failure
4 SS SS re-modifies the scrambling code of
DPCH to the original one.
5 SS SS waits 60 s.
UE shall send no message on DCCH

None.
After step 4 the UE shall not send any message to the SS during 60 s.
10.1.2.3.5 Outgoing call / U1 call initiated / receiving ALERTING
The call control entity of the UE being in the state, U1, an ALERTING message is sent to the UE as an indication that a
call is being alerted at a called end.
When the call control entity of the UE in the "call initiated" state or "mobile originating call proceeding" state receives
an ALERTING message then, the call control entity of the UE shall stop timer T303 and T310 (if running) and shall
enter the "call delivered" state.
References
TS 24.008, clause 5.2.1.1 and clause 5.2.1.5.
To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of an ALERTING message, enters
CC state U4, "Call delivered".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1825
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. The SS sends an ALERTING message to the UE. The
SS checks by using the status enquiry procedure that the CC entity has entered the state U4, call delivered.
Expected sequence
UE SS
1 <- ALERTING
2 <- STATUS ENQUIRY

None.
After step 1 the UE shall enter CC state U4, "Call delivered".
10.1.2.3.6 Outgoing call / U1 call initiated / entering state U10
The call control entity of the UE being in the state, U1, a CONNECT message is received by the UE.
The call control entity of the UE in the "call initiated" state, in the "mobile originating call proceeding" state or in the
"call delivered" state, shall, upon receipt of a CONNECT message:
- attach the user connection;
- return a CONNECT ACKNOWLEDGE message;
- stop any locally generated alerting indication (if applied);
- stop timer T303 and T310 (if running);
- enter the "active" state.
References
TS 24.008, clause 5.2.1.1 and clause 5.2.1.6.
To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a CONNECT message, sends a
CONNECT ACKNOWLEDGE message to its peer entity and enters CC state U10, "Active".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1826
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. The SS sends a CONNECT message to the UE. The
UE shall respond by sending a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry
procedure that the CC entity has entered the state U10, active.
Expected sequence
UE SS
1 <- CONNECT
2 -> CONNECT ACKNOWLEDGE
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a CONNECT ACKNOWLEDGE message and shall enter CC state U10, "Active".
10.1.2.3.7 Outgoing call / U1 call initiated / unknown message received
The call control entity of the UE being in the state, U1, an unknown message is received by the UE.
If a UE receives an RR, MM or CC message with message type not defined for the PD or not implemented by the
receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the protocol
discriminator) with cause #97 "message type non-existent or not implemented".
References
TS 24.008 clause 8.4.
To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a message with message type not
defined for the protocol discriminator from its peer entity returns a STATUS message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1827
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U1. The SS sends a message with message type not
defined for the protocol discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS
checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
1 <- unknown message message type not defined for PD
3 <- STATUS ENQUIRY

None.
After step 1 and step 3 the UE shall return a STATUS message with "Call state" set to state U1, "Call initiated".
10.1.2.4 Outgoing call / U3 Mobile originating call proceeding
10.1.2.4.1 Outgoing call / U3 Mobile originating call proceeding / ALERTING received
The call control entity of the UE being in the state, U3, an ALERTING message is sent to the UE as an indication that a
call is being alerted at a called end.
enter the "call delivered" state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1828
References
TS 24.008 clause 5.2.1.5.
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a
ALERTING message enters CC-state U4, "Call Delivered".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The SS sends an ALERTING message to the UE. The
SS checks by using the status enquiry procedure that the CC entity has entered the state U4, call delivered.
Expected sequence
UE SS
1 <- ALERTING
2 <- STATUS ENQUIRY

None.
After step 1 the UE shall enter CC-state U4, "Call Delivered".
10.1.2.4.2 Outgoing call / U3 Mobile originating call proceeding / CONNECT received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1829
References
TS 24.008 clause 5.2.1.6.
1) To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a
CONNECT message returns a "CONNECT ACKNOWLEDGE" message to its peer entity and enters the CC
state U10, "Active".
2) To verify that the UE stops locally generated alerting indication, if any.
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a RADIO BEARER SETUP for traffic
channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS sends a
CONNECT message to the UE. The UE shall respond by sending a CONNECT ACKNOWLEDGE message. The SS
checks by using the status enquiry procedure that the CC entity has entered the state U10, active.
Expected sequence
UE SS
2 <- CONNECT the UE shall stop locally generated
alerting indication, if any
3 -> CONNECT ACKNOWLEDGE
4 <- STATUS ENQUIRY

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1830
None.
After step 1 the UE shall return a "CONNECT ACKNOWLEDGE" message and enter the CC state U10, "Active".
The UE shall stop locally generated alerting indication.
10.1.2.4.3 Outgoing call / U3 Mobile originating call proceeding / PROGRESS received
without in band information
The call control entity of the UE being in the state, U3, a PROGRESS message is received by the UE. The PROGRESS
message does not contain indication of in-band information availability.
1) In order to inform the UE that the call is progressing in the PLMN/ISDN environment the network may send a
progress indicator information element to the calling UE either:
a) in an appropriate call control message, if a state change is required (e.g., ALERTING or CONNECT); or
b) in the PROGRESS message, if no state change is appropriate.
This progress indicator information element shall contain progress description value #32 "Call is end-to-end
ISDN/PLMN".
2) At any time during the establishment or release of a call and during an active call the network may send a
PROGRESS message to the UE.
On receipt of a PROGRESS message during the establishment or release of a call the UE shall stop all call
control timers related to that call.
References
Conformance requirement 1: TS 24.008 clause 5.2.1.4.2
Conformance requirement 2: TS 24.008 clause 5.5.6
PROGRESS message with valid cause values stays in CC-state U3.
2) To verify that after receipt of the PROGRESS message timer T310 is stopped.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1831
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a PROGRESS message not containing
indication of in-band information availability to the UE. The SS checks that the UE has stopped T310, i.e. at T310 time-
out no DISCONNECT message is sent by the UE. Then the SS checks by using the status enquiry procedure that the
state of the CC entity has remained unchanged.
Expected sequence
UE SS
1 <- PROGRESS (note)
2 <- STATUS ENQUIRY
4 SS SS waits at least 45 s and checks no
DISCONNECT is sent by the UE
5 <- STATUS ENQUIRY

NOTE: Tested with a valid Progress Indicator, Progress description value among:
- #32 call is end-to-end PLMN/ISDN.
None.
After step 1 the UE shall stay in CC-state U3.
After step 3 SS waits at least 45 s and checks no DISCONNECT is sent by the UE.
10.1.2.4.4 Outgoing call / U3 Mobile originating call proceeding / PROGRESS with in band
information
The call control entity of the UE being in the state, U3, a PROGRESS message indicating availability of in band
information is received by the UE.
1) When the network wants to make the UE attach the user connection (e.g. in order to provide in-band
tones/announcement) before the UE has reached the "active" state of a call, the network may include a progress
indicator IE indicating user attachment in a suitable CC message:
- Either it includes the IE in a SETUP, CALL PROCEEDING, ALERTING, or CONNECT message that is
send during call establishment
- it sends a PROGRESS message containing the IE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1832
On reception of a SETUP, CALL PROCEEDING, ALERTING, CONNECT, or PROGRESS message the UE
shall proceed as specified elsewhere in TS 24.008 clause 5; if the progress indicator IE indicated user attachment
and a speech mode traffic channel is appropriate for the call the UE shall in addition: attach the user connection
for speech as soon as an appropriate channel in speech mode is available.
2) At any time during the establishment or release of a call and during an active call the network may send a
PROGRESS message to the UE.
On receipt of a PROGRESS message during the establishment or release of a call the UE shall stop all call
control timers related to that call.
References
PROGRESS message indicating in-band announcement through-connects the traffic channel for speech, if
DTCH is in speech mode. If DTCH is not in a speech mode, the UE does not through-connect the DTCH.
2) To verify that after receipt of the PROGRESS message, T310 is stopped.
Initial conditions
System Simulator:
User Equipment:
Test procedure
PROGRESS message containing indication of in-band information availability to the UE. The SS checks that if channel
mode is speech, the DTCH shall be through connected. If channel mode is not speech, the DTCH shall not be through
connected. Also the SS checks that the UE has stopped T310, i.e. at T310 time-out no DISCONNECT message is sent
by the UE. Then the SS checks by using the status enquiry procedure that the state of the CC entity has remained
unchanged.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1833
Expected sequence
UE SS
1 Radio Bearer Setup Procedure See TS34.108 clause 7.1.3
2 <- PROGRESS (note)
the UE shall stop all the CC timers , if
channel mode is speech, the DTCH
shall be through connected. If channel
mode is not speech, the DTCH shall not
be through connected.
3 <- STATUS ENQUIRY
5 SS SS waits at least 45 s and checks no
DISCONNECT is sent by the UE.
6 <- STATUS ENQUIRY
8 SS If the channel mode is speech the SS
will check that the user connection for
speech is attached (both downlink and
uplink).

NOTE: Tested with a valid Progress Indicator, Progress description value among:
- #1 call is not end to end PLMN/ISDN;
- #2 destination address is non PLMN/ISDN;
- #3 originating address is non PLMN/ISDN;
- #8 in band information or appropriate pattern now available.
After step 2 the UE shall through-connect the traffic channel for speech, if DTCH is in a speech mode. If DTCH is not
in speech mode, the UE shall not through-connect the DTCH.
After step 4 the SS waits at least 45 s and checks no DISCONNECT is sent by the UE.
After step 7 the SS checks that the user connection for speech is attached (both downlink and uplink), if the channel
mode is speech.
10.1.2.4.5 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT with in
band tones
The call control entity of the UE being in the state, U3, a DISCONNECT message indicating availability of in band
The call control entity of the UE in any state except the "null" state, the "disconnect indication" state, and the "release
request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8:
i) if an appropriate speech traffic channel is not connected, continue clearing as defined in TS24.008 clause
5.4.4.1.2.1 without connecting to the in-band tone/announcement;
ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached
and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call
control entity of the UE shall proceed as defined in TS24.008 clause 5.4.4.1.2.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1834
References
TS 24.008 and clause 5.4.4.1.1.1
DISCONNECT with progress indicator #8 through-connects the speech channel to make in-band announcements
available, if traffic channel is in speech mode. If DTCH is not in speech mode, the UE sends a RELEASE message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
DISCONNECT message containing indication of in-band information availability to the UE. The SS checks that if
channel mode is speech, the DTCH shall be through connected and the UE enters state U12, disconnect indication. If
channel mode is not speech, the DTCH shall not be through connected and the UE shall enter state U19, release request.
Expected sequence
UE SS
2 <- DISCONNECT (note)
DTCH in speech mode:
A3 SS the SS will check that the audio path for
in band tones is attached.
A4 <- STATUS ENQUIRY
A5 -> STATUS cause #30, state U12
DTCH is not in speech mode:
B3 -> RELEASE
B4 <- STATUS ENQUIRY
B5 -> STATUS cause #30, state U19

NOTE: the Progress Indicator, Progress descriptionvalue:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1835
After step 2 the UE shall through-connect the speech channel to make in-band announcements available, if traffic
channel is in speech mode. If DTCH is not in speech mode, the UE shall send a RELEASE message.
10.1.2.4.6 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT without in
band tones
The call control entity of the UE being in the state, U3, a DISCONNECT message is received by the UE. The
DISCONNECT message does not contain indication of in-band information availability.
request" state, shall, upon the receipt of a DISCONNECT message without progress indicator information element or
with progress indicator different from #8:
- stop all running call control timers;
- send a RELEASE message;
- start timer T308; and
- enter the "release request" state.
References
TS 24.008 clause 5.4.4.1.2.1
DISCONNECT without progress indicator returns a RELEASE message and enters the CC-state U19, "Release
Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a DISCONNECT message not
containing indication of in-band information availability to the UE. The UE shall respond with a RELEASE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1836
The SS checks by using the status enquiry procedure that the CC entity of the UE has entered the state U19, release
request.
Expected sequence
UE SS
1 <- DISCONNECT without progress indicator
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a RELEASE message and enter the CC-state U19, "Release Request".
10.1.2.4.7 Outgoing call / U3 Mobile originating call proceeding / RELEASE received
The call control entity of the UE being in the state, U3, a RELEASE message is received by the UE.
The call control entity of the UE in any state except the "null" state and the "release request" state, shall, upon receipt of
a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM
connection; and return to the "null" state.
References
TS 24.008 clause 5.4.3.3
RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the UE on returning to the idle mode releases the MM-connection and that the CC-entities relating
to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1837
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a RELEASE message to the UE. The
UE shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that
the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
UE SS
1 <- RELEASE with cause "Normal, unspecified"
2 -> RELEASE COMPLETE
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a RELEASE COMPLETE message.
10.1.2.4.8 Outgoing call / U3 Mobile originating call proceeding / termination requested by
the user
The call control entity of the UE being in the state, U3, the user requests to terminate the call.
Apart from the exceptions identified in TS 24.008 clause 5.4.2, the call control entity of the UE shall initiate clearing
by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and entering the
"disconnect request" state.
References
TS 24.008 clause 5.4.3.1
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", upon request by the user to
terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1838
Initial conditions
System Simulator: 1 cell, default parameters.
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The user requests termination of the call. The UE shall
send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered the
state U11, disconnect request.
Expected sequence
UE SS
1 MMI action, terminate call
2 -> DISCONNECT
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
10.1.2.4.9 Outgoing call / U3 Mobile originating call proceeding / traffic channel allocation
The call control entity of the UE being in the state, U3, a radio bearer establishment procedure is performed.
It is a network dependent decision when to initiate the assignment of an appropriate traffic channel during the mobile
originating call establishment phase. Initiation of a suitable RR procedure to assign an appropriate traffic channel does
neither change the state of a call control entity nor affect any call control timer.
References
TS 24.008 clause 5.2.1.9.
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", when a traffic channel is
allocated by the network performing the radio bearer establishment procedure, stays in CC-state U3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1839
Initial conditions
System Simulator:
User Equipment:
Test procedure
channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS checks by
using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
2 <- STATUS ENQUIRY

None.
After step 1 the CC state U3, "Mobile Originating Call Proceeding", shall remain unchanged.
10.1.2.4.10 Outgoing call / U3 Mobile originating call proceeding / timer T310 time-out
at the UE side.
1) If timer T310 elapses before any of the ALERTING, CONNECT or DISCONNECT messages has been received,
the UE shall perform the clearing procedure described in TS 24.008 clause 5.4.
2) Apart from the exceptions identified in TS 24.008 clause 5.4.2, the call control entity of the UE shall initiate
clearing by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and
entering the "disconnect request" state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1840
References
Conformance requirement 1: TS 24.008 clause 5.2.1.3./Abnormal case
Conformance requirement 2: TS 24.008 clause 5.4.3.1.
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" will, upon expiry of timer
T310, initiate call release by sending DISCONNECT and enter the CC-state U11, "Disconnect Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U3. The T310 expires at the UE and the UE shall send
DISCONNECT. The SS checks timer T310 accuracy and that the CC entity has entered the state U11, disconnect
request.
Expected sequence
UE SS
1 SS the SS waits for T310 time-out
2 -> DISCONNECT check the timer T310 accuracy, see
TS34.108 clause 4.2.3
3 <- STATUS ENQUIRY

None.
After step 1 upon expiry of timer T310 the UE shall initiate call release by sending a DISCONNECT message and enter
the CC-state U11, "Disconnect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1841
10.1.2.4.11 Outgoing call / U3 Mobile originating call proceeding / lower layer failure

.
The re-establishment procedure allows a MS to resume a connection in progress after a radio link failure, possibly in
a new cell and possibly in a new location area. The conditions in which to attempt call re-establishment or not
depend on the call control state, see clause 5.5.4 and, whether or not a cell allowing call re-establishment has been
found (as described in GSM 05.08). MM connections are identified by their protocol discriminators and transaction
identifiers: these shall not be changed during call re-establishment.
The re-establishment takes place when a lower layer failure occurs and at least one MM connection is active (i.e..
the mobile station's MM sublayer is either in state 6 "MM CONNECTION ACTIVE" or state 20 "WAIT FOR
ADDITIONAL OUTGOING MM CONNECTION").
.
When a MM connection is active, an indication may be given by the MM sublayer to the call control entity to
announce that the current MM connection has been interrupted but might be re-established on request of call control.
Depending whether call re-establishment is allowed or not and on its actual state, call control shall decide to either
request re-establishment or to release the MM connection.
a) Re-establishment not required
If the call is in the call establishment or call clearing phase, i.e. any state other than the "active" state or the "mobile
originating modify" state, call control shall release the MM connection
.

In CELL_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1 for the established
DPCCH physical channel in FDD, and the DPCH associated with mapped DCCHs in TDD, the UE shall:
1>start timer T313;
1>upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:
2>stop and reset timer T313.
1>if T313 expires:
2>consider it as a "Radio link failure".
Periods in time where neither "in sync" nor "out of sync" is reported by layer 1 do not affect the evaluation of the
number of consecutive (resp. successive) "in sync" or "out of sync" indications.
When a radio link failure occurs, the UE shall:
1>clear the dedicated physical channel configuration;
1>perform actions as specified for the ongoing procedure;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1842
1>if no procedure is ongoing or no actions are specified for the ongoing procedure:
2>perform a cell update procedure according to subclause 8.3.1 using the cause "radio link failure".
In addition, the cell update procedure also serves the following purposes:

- to act on a radio link failure in the CELL_DCH state;
References
TS 24.008 clause 4.5.2.3, 4.5.1.6, and 5.5.4, TS 25.331 clause 8.5.6 and 8.3.1.1.
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" having detected a lower
layer failure and having returned to idle mode, the CC entity is in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The UE is brought to the state U3. The SS releases the DPCH configuration to generate a lower layer
failure at the UE. The SS waits long enough to perform cell update procedure. The SS sends RRC CONNECTION
RELEASE message as a response to the CELL UPDATE message from the UE.. The SS checks that the UE does not
initiate RRC connection establishment during 60 s.
Expected sequence
UE SS
1 SS SS releases the DPCH configuration to
generate lower layer failure(radio link
failure)
4 SS For a period of 60 s the SS checks that
the UE does not initiate RRC connection
establishment (since it should not re-
attempt MM connection establishment)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1843
None.
After step 4 the UE shall not initiate RRC Connection Establishment for 60 s.
10.1.2.4.12 Outgoing call / U3 Mobile originating call proceeding / unknown message
received
References
TS 24.008 clause 8.4.
To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" having received an
unknown message from its peer entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1844
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall return a STATUS message.
10.1.2.4.13 Outgoing call / U3 Mobile originating call proceeding / Internal alerting indication
The call control entity of the UE being in the state, U3, an ALERTING message is sent to the UE when the user
connection is not attached to the radio path.
enter the "call delivered" state. In this state, for speech calls:
- an alerting indication should be given to the user. If the UE has not attached the user connection then the UE
shall internally generate an alerting indication. If the UE has attached the user connection then the network is
responsible for generating the alerting indication and the UE need not generate one.
References
TS 24.008 clause 5.2.1.5.
When the call control entity of the UE in the "mobile originating call proceeding" state receives an ALERTING
message then it enters "call delivered" state and, for speech calls, if the user connection is not attached to the radio path,
the UE generates internally an alerting indication.
- way to give internally generated alerting indication for outgoing calls.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1845
Test procedure
The SS sends an ALERTING message to the UE. The SS checks by using the status enquiry procedure that the CC
entity has entered the state U4, call delivered. Also it is checked that the UE generates internally alerting indication to
the user in the way described in the ICS/IXIT statements.
Expected sequence
UE SS
1 <- ALERTING the UE shall generate an alerting
indication to the user in the way
described in the ICS/IXIT statements
2 <- STATUS ENQUIRY

None.
After step 1 the UE shall enter "Call Delivered" state and, for speech calls, if the user connection is not attached to the
radio path, the UE shall internally generate an alerting indication.
10.1.2.5 Outgoing call / U4 call delivered
10.1.2.5.1 Outgoing call / U4 call delivered / CONNECT received
References
TS 24.008 clause 5.2.1.6.
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", upon receipt of the CONNECT message returns
a CONNECT ACKNOWLEDGE to its peer entity and enters the CC-state U10, "Active".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1846
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U4. The SS sends a CONNECT message to the UE. The
UE shall respond by sending a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry
procedure that the CC entity has entered the state U10, active.
Expected sequence
UE SS
1 <- CONNECT
2 -> CONNECT ACKNOWLEDGE UE stops locally generated alerting
indication, if applicable
3 <- STATUS ENQUIRY

None.
After step 1 the UEshall return a CONNECT ACKNOWLEDGE message and enter the CC state U10, "Active".
10.1.2.5.2 Outgoing call / U4 call delivered / termination requested by the user
References
TS 24.008 clause 5.4.3.1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1847
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", upon request by the user to terminate will send a
DISCONNECT message and enter the CC-state U11, "Disconnect Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U4. The user requests termination of the call. The UE shall
send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered the
state U11, disconnect request.
Expected sequence
UE SS
2 -> DISCONNECT
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a DISCONNECT message and enter the CC state U11, "Disconnect Request".
10.1.2.5.3 Outgoing call / U4 call delivered / DISCONNECT with in band tones
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1848
i) if an appropriate speech traffic channel is not connected, continue clearing as defined in TS 24.008 clause
control entity of the UE shall proceed as defined in TS 24.008 clause 5.4.4.1.2.1.
References
TS 24.008 clause 5.4.4.1.1.1
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", upon receipt of a DISCONNECT with a progress
indicator indicating in-band information, through-connects the speech channel to make in-band announcements
available, if traffic channel is in speech mode. If DTCH is not in speech mode, the UE shall send a RELEASE message.
Initial conditions
System Simulator:
User Equipment:
The UE is brought into the state U4 by using table10.1.2/3.
Test procedure
initiate a call. The CC entity of the UE is brought to the state U4. The SS sends a DISCONNECT message containing
indication of in-band information availability to the UE. The SS checks that if channel mode is MO telephony, the
DTCH shall be through connected and the UE enters state U12, disconnect indication. If channel mode is not speech,
the DTCH shall not be through connected and the UE shall enter state U19, release request.
Expected sequence
UE SS
B2 -> RELEASE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1849
NOTE: the Progress Indicator, Progress Description value:
10.1.2.5.4 Outgoing call / U4 call delivered / DISCONNECT without in band tones
References
TS 24.008 clause 5.4.4.1.2.1
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", upon receipt of a DISCONNECT without
progress indicator, returns a RELEASE message and enters the CC-state U19, "Release Request".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1850
Test procedure
request.
Expected sequence
UE SS
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall return a RELEASE message and enter the CC-state U19, "Release Request".
10.1.2.5.5 Outgoing call / U4 call delivered / RELEASE received
References
TS 24.008 clause 5.4.3.3.
1) To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", upon receipt of the RELEASE message
will respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1851
The UE is brought into the state U4 by using table10.1.2/3.
Test procedure
UE shall respond with a RELEASE COMPLETE message.
Expected sequence
UE SS
3 <- STATUS ENQUIRY
5 Void

None.
After step 1 the UE shall respond with the RELEASE COMPLETE message.
10.1.2.5.6 Outgoing call / U4 call delivered / lower layer failure
References
TS 24.008 clause 4.5.2.3 and clause 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered" having detected a lower layer failure and has
returned to idle mode, the CC-entity is in CC-state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1852
Initial conditions
System Simulator:
User Equipment:
Test procedure
DPCH) to generate a lower layer failure at the UE. The SS waits long enough to perform cell update procedure. The SS
sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-
modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will
check that the UE will not send any message during 60 s.
Expected sequence
UE SS
5 SS SS waits 60 s.
UE shall send no message on the
DCCH

None.
10.1.2.5.7 Outgoing call / U4 call delivered / traffic channel allocation
The call control entity of the UE being in the state, U4, a radio bearer establishment procedure is performed.
It is a network dependent decision when to initiate the assignment of an appropriate traffic channel during the mobile
originating call establishment phase. Initiation of a suitable RR procedure to assign an appropriate traffic channel does
neither change the state of a call control entity nor affect any call control timer.
References
TS 24.008 clause 5.2.1.9.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1853
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", when a traffic channel is allocated by the
network performing the radio bearer establishment procedure, stays in CC-state U4.
Initial conditions
System Simulator:
User Equipment:
Test procedure
channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS checks by
Expected sequence
UE SS
2 <- STATUS ENQUIRY

None.
After step 1 the CC state U4, "Call delivered", shall remain unchanged.
10.1.2.5.8 Outgoing call / U4 call delivered / unknown message received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1854
References
TS 24.008 clause 8.4.
To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", having received an unknown message from its
peer entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
10.1.2.6 U10 active
10.1.2.6.1 U10 active / termination requested by the user
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1855
References
TS 24.008 clause 5.4.3.1
To verify that the a CC-entity of the UE in CC-state U10, "Active", upon request by the user to terminate will send a
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U10. The user requests termination of the call. The UE
shall send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has
entered the state U11, disconnect request.
Expected sequence
UE SS
2 -> DISCONNECT
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send a DISCONNECT message and enter the CC state U11, "Disconnect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1856
10.1.2.6.2 U10 active / RELEASE received
References
TS 24.008 clause 5.4.3.3.
1) To verify that the a CC-entity of the UE in CC-state U10, "Active", upon receive of the RELEASE will respond
with the RELEASE COMPLETE message and enter the CC-state U0, "Null"
Initial conditions
System Simulator:
User Equipment:
Test procedure
Expected sequence
UE SS
2 -> RELEASE COMPLETE the UE starts T3240
3 <- STATUS ENQUIRY
5 Void

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1857
After step 1 the UE shall return a RELEASE COMPLETE message.
10.1.2.6.3 U10 active / DISCONNECT with in band tones
References
TS 24.008 clause 5.4.4.1.1.1
To verify that a CC-entity of the UE in CC-state U10, "Active", upon receipt of a DISCONNECT message with a
Progress Indicator indicating in-band information, through-connects the speech channel to make in-band
announcements available, if traffic channel is in speech mode. If DTCH is not in speech mode, the UE sends a
RELEASE message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U10. The SS sends a DISCONNECT message containing
indication of in-band information availability to the UE. The SS checks that if channel mode is speech, the DTCH shall
be through connected and the UE enters state U12, disconnect indication. If channel mode is not speech, the DTCH
shall not be through connected and the UE enters state U19, release request.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1858
Expected sequence
UE SS
B2 -> RELEASE

NOTE: the Progress Indicator, Progress Description value:
#8 in band information or appropriate pattern now available.
10.1.2.6.4 U10 active / DISCONNECT without in band tones
References
TS 24.008 clause 5.4.4.1.2.1
To verify that the a CC-entity of the UE in CC-state U10, "Active", upon receipt of a DISCONNECT message without
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1859
Initial conditions
System Simulator:
User Equipment:
Test procedure
request.
Expected sequence
UE SS
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
10.1.2.6.5 U10 active / RELEASE COMPLETE received
The call control entity of the UE being in the state, U10, the call is cleared by a RELEASE COMPLETE message sent
by the SS.
1) A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing
even though the cause information element is not included.
2) A call control entity of the UE in any call control state shall, upon receipt of a RELEASE COMPLETE message
from its peer entity in the network: stop all running call control timers ; release the MM connection; and return to
the "null" state.
References
Conformance requirement 1: TS 24.008 clause 5.4.2.
Conformance requirement 2: TS 24.008 clause 5.4.4.1.3.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1860
1) To verify that a CC entity of the UE in CC-state U10, "Active" upon receipt of a RELEASE COMPLETE
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile originating transaction
Initial conditions
System Simulator:
User Equipment:
Test procedure
The SS sends a RELEASE COMPLETE message to the UE. The SS checks by using the status enquiry procedure that
Expected sequence
UE SS
1 <- RELEASE COMPLETE note 1
2 <- STATUS ENQUIRY note 2
3 -> RELEASE COMPLETE cause #81 (invalid TI value),

NOTE 1: With the cause value chosen arbitrarily or cause value not included.
NOTE 2: TI flag has the value indicating the UE as an originator of the call.
10.1.2.6.6 U10 active / SETUP received
If the UE does not react correctly when receiving a SETUP message on a new Transaction Identifier during an active
call, the active call may be lost.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1861
1) A busy UE which satisfies the compatibility requirements indicated in the SETUP message shall respond either
with a CALL CONFIRMED message if the call setup is allowed to continue or a RELEASE COMPLETE
message if the call setup is not allowed to continue, both with cause #17 "user busy".
References:
TS 24.008 clause 5.2.2.3.1.
1) To verify that a User Equipment that has a call established and receives a SETUP message answers either with a
CALL CONFIRMED message with cause "user busy" if it supports call waiting, or with a RELEASE
COMPLETE message with cause "user busy" otherwise.
2) To verify that after having sent this message, the UE is still in state U10 for the established call.
- support of call waiting Y/N.
Initial conditions
System Simulator:
User Equipment:
The UE is idle updated with valid TMSI and CKSN.
Test Procedure
The UE has a mobile originated call in the U10 state. When UE sends a SETUP message and SS receives it in the first
call establishment, SS sends a CALL PROCEEDING message without Network Call Control Capabilities IE.
The SS sends a SETUP message to the UE (with signal IE indicating "call waiting tone on" and without Network Call
Control Capabilities IE).
If the UE does not support call waiting it shall answer by a RELEASE COMPLETE message.
If the UE supports call waiting it shall answer by a CALL CONFIRMED message followed by an ALERTING. The
second transaction is then released by the SS with a RELEASE COMPLETE message.
In both cases the SS checks by using the status enquiry procedure that the CC entity of the UE is still in state U10,
active call for the original call.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1862
Expected sequence
UE SS
1 <- SETUP this message establishes a second
transaction The TI value shall be the
same as the one that is in use for the
MO call. The TI flag shall have the value
specified for an MT call.
if the UE does not support call waiting
A2 -> RELEASE COMPLETE with cause "user busy" with the TI of the
second transaction
if the UE supports call waiting
B2 -> CALL CONFIRMED with cause "user busy" with the TI of the
second transaction
B3 -> ALERTING with the TI of the second transaction
B4 <- RELEASE COMPLETE with the TI of the second transaction
5 <- STATUS ENQUIRY with the TI of the original transaction
6 -> STATUS cause #30, state U10 with the TI of the
original transaction

SETUP message contains a Signal IE with value "call waiting tone on" (H'07).
After step 1 a UE that has a call established shall answer either with a CALL CONFIRMED message with cause "user
busy" if it supports call waiting, or with a RELEASE COMPLETE message with cause "user busy" otherwise.
After step A2 or B4 the UE shall be in state U10 for the established call.
10.1.2.7 U11 disconnect request
10.1.2.7.1 U11 disconnect request / clear collision
The call control entity of the UE being in the state, U11, a DISCONNECT message is received by the UE.
References
TS 24.008 clause 5.4.4.1.2.1.
To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request", upon receipt of a DISCONNECT
message, returns to its peer entity the RELEASE message and enters the CC-state U19, "Release Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1863
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U11. The SS sends a DISCONNECT message to the UE.
The UE shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC
entity of the UE has entered the state U19, release request.
Expected sequence
UE SS
1 <- DISCONNECT
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall return the RELEASE message.
After step 3 the UE shall return a STATUS message with "Call state" set to state U19, "Release Request".
10.1.2.7.2 U11 disconnect request / RELEASE received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1864
References
TS 24.008 clause 5.4.3.3
1) To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request", upon receipt of the RELEASE
message shall return RELEASE COMPLETE and enter the CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
Expected sequence
UE SS
1 <- RELEASE
3 <- STATUS ENQUIRY
5 Void

None.
After step 1 the UE shall return the RELEASE COMPLETE.
10.1.2.7.3 U11 disconnect request / timer T305 time-out
at the UE side.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1865
The call control entity of the UE in the "disconnect request" state, shall upon expiry of timer T305: send a RELEASE
message to the network with the cause number originally contained in the DISCONNECT message and optionally, a
second cause information element with cause #102 "recovery on timer expiry", start timer T308, and enter the "release
request" state.
References
TS 24.008 clause 5.4.3.5.
To verify that the CC-entity of the UE in CC-state U11, "Disconnect Request" shall on expiry of T305, proceed with the
connection release procedure by sending the RELEASE message to its peer entity and enters the CC-state U19,
"Release Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U11. Then T305 expires at the UE and the UE shall send a
RELEASE message. The SS checks timer T305 accuracy and that the CC entity has entered the state U19, release
request.
Expected sequence
UE SS
1 SS SS waits until T305 expires at the UE
2 -> RELEASE SS checks the time between
DISCONNECT and RELEASE (note),
check the timer T305 accuracy, see
TS34.108 clause 4.2.3
3 <- STATUS ENQUIRY

NOTE: With the same cause value as originally contained in the DISCONNECT message. An additional cause
information element (#102 recovery on timer expiry) may be included.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1866
After step 1 upon expiry of timer T305 the UE shall proceed with the connection release procedure by sending the
RELEASE message and enter the CC-state U19, "Release Request".
10.1.2.7.4 U11 disconnect request / lower layer failure
References
TS 24.008 clause 4.5.2.3 and 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.
To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request" having detected a lower layer failure
returns to the idle mode. The CC entity is thus in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1867
Expected sequence
UE SS
5 SS SS waits 60 s.

None.
10.1.2.7.5 U11 disconnect request / unknown message received
References
TS 24.008 clause 8.4.
To verify that a CC-entity of the UE in CC-state U11, "Disconnect Request", having received an unknown message
from its peer entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1868
Test procedure
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
10.1.2.8 U12 disconnect indication
10.1.2.8.1 U12 disconnect indication / call releasing requested by the user
Response from the upper layers:
i) If the upper layers request the clearing of the call, the call control entity of the UE shall:
References
TS 24.008 clause 5.4.4.2.2.1
To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" being in network initiated call release
phase, shall, upon receiving a call release request from the user sends a RELEASE to its peer entity and enters CC-state
U19, "Release Request"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1869
Initial conditions
System Simulator:
User Equipment:
The UE is brought into the state U12 by using Option A of table 10.1.2/1.
Test procedure
initiate a call. The CC entity of the UE is brought to the state U12. The user requests termination of the call. The UE
shall send a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity has entered the
state U19, release request.
Expected sequence
UE SS
1 MMI action, "on hook"
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
After step 1 the UE being in network initiated call release phase, shall send a RELEASE message and enter CC-state
U19, "Release Request".
10.1.2.8.2 U12 disconnect indication / RELEASE received
References
TS 24.008 clause 5.4.3.3
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1870
1) To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication", upon receipt of a RELEASE
message returns to its peer entity the RELEASE COMPLETE message and enters the CC-state U0, "Null".
to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
UE shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that
Expected sequence
UE SS
1 <- RELEASE
3 <- STATUS ENQUIRY
6 <- The SS releases the RRC connection

None.
After step 1 the UE shall return the RELEASE COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1871
10.1.2.8.3 U12 disconnect indication / lower layer failure
References
To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having detected a lower layer failure
returns to idle mode. The CC-entity is thus in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1872
Expected sequence
UE SS
5 SS SS waits 60 s.
DCCH

None.
10.1.2.8.4 U12 disconnect indication / unknown message received
References
TS 24.008 clause 8.4.
To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having received an unknown message
from its peer entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1873
Test procedure
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
10.1.2.9 Outgoing call / U19 release request
10.1.2.9.1 Outgoing call / U19 release request / timer T308 time-out
at the UE side.
The call control entity of the UE in the "release request" state shall at first expiry of timer T308 retransmit the
RELEASE message and restart timer T308.
References
TS 24.008 clause 5.4.4.1.3.1.
To verify that a CC-entity of the UE in CC-state U19, "Release Request" will, upon the first expiry of timer T308 send
the RELEASE message to its peer entity and remain in the CC-state U19.
Initial conditions
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1874
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U19. When T308 expires at the UE, the UE shall send a
RELEASE message. The SS checks timer T308 accuracy and that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
1 SS SS waits until T308 at the UE
2 -> RELEASE SS checks the time between the two
RELEASE messages
check the timer T308 accuracy, see
TS34.108 clause 4.2.3
3 <- STATUS ENQUIRY

None.
After step 1 upon the first expiry of timer T308 the UE shall send the RELEASE message and remain in the CC-state
U19.
10.1.2.9.2 Outgoing call / U19 release request / 2nd timer T308 time-out
The call control entity of the UE being in the state, U19, if no response is then received after timer T308 has expired
two times in success at the UE.
At second expiry of timer T308, the call control entity of the UE shall: release the MM connection; and return to the
"null" state.
References
TS 24.008 clause 5.4.4.1.3.1.
1) To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon the 2nd expiry of the timer T308,
enters the CC-state U0, "Null".
2) To verify that subsequently the UE proceeds with releasing the MM-connection and enters the idle mode with
the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1875
Initial conditions
System Simulator:
User Equipment:
Test procedure
initiate a call. The CC entity of the UE is brought to the state U19. The SS allows T308 expiry at the UE, and the UE
shall repeat sending the RELEASE message and start timer T308 again. The SS allows again T308 expiry at the UE.
The UE shall abort the RRC connection. The SS waits long enough to enable the UE to return to idle state listening to
paging, and then pages UE to create RRC connection. The SS performs authentication and starts integrity. Finally, the
SS will check the state of the UE by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
UE SS
1 SS SS waits until T308 expiry at the UE
2 -> RELEASE
3 <- STATUS ENQUIRY
5 SS SS waits until the second T308 expiry at
the UE
6 SS SS waits T3240 expiry at the UE
7 UE The SS releases the RRC connection
8 SS SS waits 10 s for the UE to return to
listening to paging
9 Mobile terminated establishment of Radio Resource
Connection
See TS34.108
9a -> PAGING RESPONSE
9b <- AUTHENTICATION REQUEST
9c -> AUTHENTICATION RESPONSE
9d SS starts integrity
10 <- STATUS ENQUIRY

None.
After step 5 upon the 2nd expiry of the timer T308 the UE shall enter the CC-state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1876
10.1.2.9.3 Outgoing call / U19 release request / RELEASE received
Clear collision can also occur when both sides simultaneously transfer RELEASE messages related to the same call.
The entity receiving such a RELEASE message whilst within the "release request" state shall: stop timer T308; release
the MM connection; and enter the "null" state (without sending a RELEASE COMPLETE message).
References
TS 24.008 clause 5.4.4.2.5.1
To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon receipt of a RELEASE, shall release the
MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile originating
transaction identifiers in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
UE shall release the MM-connection. The SS checks by using the status enquiry procedure that the CC entity has
entered the state U0 with all the relevant transaction identifiers.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1877
Expected sequence
UE SS
1 <- RELEASE
2 <- STATUS ENQUIRY
5 <- The SS releases the RRC connection

None.
10.1.2.9.4 Outgoing call / U19 release request / RELEASE COMPLETE received
The call control entity of the UE being in the state, U19, a RELEASE COMPLETE message is received by the UE.
the "null" state.
References
To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon receipt of a RELEASE COMPLETE,
shall release the MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile
originating transaction identifiers in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1878
Test procedure
initiate a call. The CC entity of the UE is brought to the state U19. The SS sends a RELEASE COMPLETE message to
the UE. The UE shall release the MM-connection. The SS checks by using the status enquiry procedure that the CC
entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
UE SS
1 <- RELEASE COMPLETE
2 <- STATUS ENQUIRY

None.
10.1.2.9.5 Outgoing call / U19 release request / lower layer failure
References
To verify that a CC-entity of the UE in CC-state U19, "Release Request", having detected a lower layer failure, returns
to the idle mode, the CC entity is in state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1879
Initial conditions
System Simulator:
User Equipment:
Test procedure
Expected sequence
UE SS
5 SS SS waits 60 s.
DCCH

None.
After step 4 CC the UE shall not send any message to the SS during 60 s.
10.1.3 Establishment of an incoming call / Initial conditions
The tables below describe message exchanges which bring the UE in the requested initial states in case of an incoming
call.
A state may be taken as initial only when all the states which lead to this initial states have been validated. The order
will be U0, U6, U9, U7, U8, U10, U26 etc. as in the following tables.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1880
Table 10.1.3/1: Establi shment of an incoming call, procedure 1
UE SS
Connection
Establishment cause: Terminating
Conversational Call.
2 -> PAGING RESPONSE
7 <- SETUP U6, (note 1)
8 -> CALL CONFIRMED U9
A9 -> CONNECT U8, p =Y, (note 2)
B9 -> ALERTING U7, p =N, (note 2)
B10 UE (note 3)
B11 -> CONNECT U8
13 <- CONNECT ACKNOWLEDGE U10
NOTE 1: With signal information included in the SETUP message.
NOTE 2: The UE is supporting immediate connect (p =Y/N). See ICS/IXIT statement.
NOTE 3: If necessary (see ICS/IXIT statement), the UE is made to accept the call in the way described in a
ICS/IXIT statement.

UE SS
Connection
See TS34.108 clause 7.1.2
A8 Radio Bearer Setup Procedure See TS34.108 clause 7.1.3
B8 Radio Bearer Setup Procedure See TS34.108 clause 7.1.3
B9 UE (note 3)
B10 -> CONNECT U8
11 Void
12 Void
NOTE 1: With signal information included in the SETUP message.
ICS/IXIT statement.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1881
Table 10.1.3/3: Void
UE SS
Connection
B9 UE (note 3)
B10 -> CONNECT U8
11 Void
12 Void
NOTE 1: The signal information element is not included in the SETUP message.
ICS/IXIT statement.

10.1.3.1 Incoming call / U0 null state
10.1.3.1.1 Incoming call / U0 null state / SETUP received with a non supported bearer
capability
The call control entity of the UE being in the state, U0, a SETUP message is received with only one bearer capability
and this bearer capability is not supported by the UE.
When the network is providing a basic service at the called side, the UE shall check that the basic service(s) offered by
the network in the Bearer Capability information element(s) match(es) the basic services that the UE is able to support.
If a mismatch is detected, then the UE shall proceed as follows:
- if the SETUP message contained two bearer capability information elements for only one of which a mismatch is
detected, the UE shall either:
- under the conditions specified in 3GPP TS 27.001 (e.g. TS 61 and TS 62), accept the SETUP message with a
CALL CONFIRMED message containing the, possibly negotiated, bearer capability information element for
which no mismatch is detected, or
- reject the call using cause No. 88 "incompatible destination".
- otherwise the UE shall reject the offered call using a RELEASE COMPLETE message with cause No. 88
"incompatible destination".
References
TS 24.008 clause 5.2.2.2 and annex B.3.2
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1882
To verify that a CC entity of the UE, upon receipt of SETUP containing one bearer capability and this bearer capability
is not supported, returns a RELEASE COMPLETE with correct cause value to its peer entity, and returns to the idle
mode. To verify that the CC-entities relating to the seven mobile terminating transaction identifiers are then in the state
U0, "Null".
- supported MT circuit switched basic services.
Initial conditions
System Simulator:
User Equipment:
Test procedure
A mobile terminated call is initiated. The UE receives a SETUP message that contains a bearer capability not supported
by the UE. The UE returns a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure
that the CC entity is still in the state U0 with all the relevant transaction identifiers.
Expected sequence
UE SS
Connection
SS sends paging, See TS34.108
5 <- The SS starts integrity protection.
6 Void
7 <- SETUP (note 1)
8 -> RELEASE COMPLETE (note 2)
9 <- STATUS ENQUIRY
10 -> RELEASE COMPLETE Cause #81 (invalid TI value).
11 SS Repeat steps 9-10 to cover all the
transaction identifiers from 000... 110.

NOTE 1: With one bearer capability and that bearer capability is not supported by the UE.
NOTE 2: With cause #88 incompatible destination.
After step 7 the UE shall return a RELEASE COMPLETE message with cause value #88 (incompatible destination) and
return to the idle mode.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1883
10.1.3.2 Incoming call / U6 call present
10.1.3.2.1 Incoming call / U6 call present / automatic call rejection
Although the state U6 is transient, the ability to refuse a call (automatically) in this state is tested, if it is implemented at
the UE.
If the mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause #21 "call
rejected".
References
TS 24.008 clause 5.2.2.3.1
To verify that a CC entity of the UE in CC-state U6, "Call Present", shall upon receipt of a rejection indication of the
incoming call from the user, shall send RELEASE COMPLETE with the appropriate cause value to its peer entity and
enter the CC-state U0, "Null". The CC entities relating to the seven mobile terminating transaction identifiers are then in
state U0, "Null".
- supported teleservices;
- the UE supports an ability to refuse a call after receipt of a SETUP message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
A teleservice is selected that is supported by the UE; if the UE supports speech, the selected teleservice is speech. If
necessary, the UE is configured for that teleservice. Then a mobile terminated call is initiated. The call control entire of
the UE is brought to the state U6 (Note: The state U6 is not checked, since it is not stable). The UE is made to refuse the
call (the refusal may require some preliminary preparations in order to achieve refusal at this point). The UE shall send
a RELEASE COMPLETE message and enter a call control state U0. The SS checks by using the status enquiry
procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1884
Expected sequence
UE SS
1 the UE is made to refuse the call
2 -> RELEASE COMPLETE (note)
3 <- STATUS ENQUIRY

NOTE: With cause value #21 call rejected.
After step 1 the UE shall return a RELEASE COMPLETE message with cause value #21 (call rejected) and return to
the idle mode.
10.1.3.3 Incoming call / U9 mobile terminating call confirmed
10.1.3.3.1 Incoming call / U9 mobile terminating call confirmed / alerting or immediate
connecting
The call control entity of the UE having entered the state, U9, with signal information received in the preceding SETUP
message, the subsequent behaviour of the UE is tested.
1) The call control entity of the UE having entered the "mobile terminating call confirmed" state, if the call is
accepted at the called user side, the UE proceeds as described in TS 24.008 clause 5.2.2.5. Otherwise, if the
signal information element was present in the SETUP message user alerting is initiated at the UE side; if the
signal information element was not present in the SETUP message, user alerting is initiated when an appropriate
channel is available.
Here, initiation of user alerting means:
- the generation of an appropriate tone or indication at the UE; and
- sending of an ALERTING message by the call control entity of the MS to its peer entity in the network and
entering the "call received" state.
2) In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the UE
indicates acceptance of a mobile terminating call by:
- sending a CONNECT message to its peer entity in the network;
- starting Timer T313; and
- entering the "connect request" state.
References
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1885
Conformance requirement 2: TS 24.008 clause 5.2.2.5.
To verify that a CC entity in CC-state U9, "Mobile Terminating Call Confirmed", (if signalled by the network in
previous SETUP message that it may alert) will either send a ALERTING message to its peer entity and enter state U7,
or send a CONNECT message to its peer entity and enter U8.
- supported MT circuit switched basic services;
- MT circuit switched basic services for which immediate connect is not used.
Initial conditions
System Simulator:
User Equipment:
Test procedure
An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the
selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated
call is initiated. The CC entity of the UE is brought to the state U9 by using a SETUP message containing signalling
information element. (The state U9 is not a stable state in this case, and consequently it is not checked as an initial
state.) If the UE supports immediate connect for the selected basic service (p =Y), it sends a CONNECT message and
enters the state U8, connect request. Otherwise (p =N) the UE sends an ALERTING message and enters the state U7,
call received. The SS checks by using the status enquiry procedure that the CC entity has entered its state as described.
Expected sequence
UE SS
A1 -> CONNECT p =Y
B1 -> ALERTING p =N

None.
At step A1 the UE shall send a CONNECT message and enter U8 if the network has signalled in previous SETUP
message that UE may not alert.
At step B1 the UE shall send an ALERTING message and enter state U7 if the network has signalled in previous
SETUP message that UE may alert.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1886
10.1.3.3.2 Incoming call / U9 mobile terminating call confirmed / DTCH assignment
The call control entity of the UE being in the state, U9, a radio bearer establishment procedure is performed for traffic
channel.
1) It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile
terminating call establishment phase.
Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control
timer, but may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2).
2) The call control entity of the UE having entered the "mobile terminating call confirmed" state, if the call is
accepted at the called user side, the UE proceeds as described in TS24.008 clause 5.2.2.5. Otherwise, if the
signal information element was present in the SETUP message user alerting is initiated at the UE side; if the
signal information element was not present in the SETUP message, user alerting is initiated when an appropriate
channel is available.
Here, initiation of user alerting means:
- the generation of an appropriate tone or indication at the UE; and
- sending of an ALERTING message by the call control entity of the MS to its peer entity in the network
and entering the "call received" state.
References
Conformance requirement 1: TS 24.008 clause 5.2.2.7
Conformance requirement 2: TS 24.008 clause 5.2.2.3.2.
To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", when a traffic channel is
allocated by the network performing the radio bearer establishment procedure, shall sends an ALERTING message and
enters state U7.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1887
Test procedure
An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use
immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is
telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC
entity of the UE is brought to the state U9 (by using a SETUP message not containing the signal information element).
The SS sends a RADIO BEARER SETUP for traffic channel to the UE. The UE shall respond with a RADIO BEARER
SETUP COMPLETE message. The UE sends an ALERTING message and enters state U7, call received. The SS
verifies by using the status enquiry procedure that the UE has entered the correct state.
Expected sequence
UE SS
2 -> ALERTING
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall send an ALERTING message and enter state U7.
10.1.3.3.3 Void
10.1.3.3.4 Incoming call / U9 mobile terminating call confirmed / DISCONNECT received
References
TS 24.008 clause 5.4.4.1.2.1
To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", upon receipt of a
DISCONNECT returns a RELEASE message and enters the CC-state U19, "Release Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1888
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U9. The SS sends a DISCONNECT message to the UE. The UE responds by
sending a RELEASE message and enters state U19, release request. The SS verifies by using the status enquiry
procedure that the UE has entered the correct state.
Expected sequence
UE SS
1 <- DISCONNECT
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
10.1.3.3.5 Incoming call / U9 mobile terminating call confirmed / RELEASE received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1889
References
TS 24.008 clause 5.4.3.3
1) To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", upon receipt of a
RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U9. The SS sends a RELEASE message to the UE. The UE responds by sending
a RELEASE COMPLETE message and enters state U0, null. The SS verifies by using the status enquiry procedure that
the UE has entered the correct state with the relevant transaction identifiers.
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 the UE shall return a RELEASE COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1890
10.1.3.3.6 Incoming call / U9 mobile terminating call confirmed / lower layer failure
References
To verify that a CC entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", having detected a lower
layer failure returns to idle mode, the CC entity is in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The UE is
brought to the state U9. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower
layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends
RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-
modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1891
Expected sequence
UE SS
5 SS SS waits 60 s.
DCCH

None.
10.1.3.3.7 Incoming call / U9 mobile terminating call confirmed / unknown message received
References
TS 24.008 clause 8.4.
To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed" having received an
unknown message from its peer entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1892
Test procedure
A MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use
entity of the UE is brought to the state U9. The SS sends a message with message type not defined for the protocol
discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS checks by using the status
enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
10.1.3.4 Incoming call / U7 call received
10.1.3.4.1 Incoming call / U7 call received / call accepted
The call control entity of the UE being in the state, U7, a user accepts the incoming call.
In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the UE indicates
acceptance of a mobile terminating call by:
- sending a CONNECT message to its peer entity in the network;
- starting Timer T313; and
- entering the "connect request" state.
References
TS 24.008 clause 5.2.2.5.
To verify that a CC entity of a UE in CC-state U7, "Call Received", upon a user accepting the incoming call, shall send
a CONNECT message to its peer entity and enter the CC-state U8, "Connect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1893
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U7. The user accepts the incoming call. The UE sends a CONNECT message.
The SS checks by using the status enquiry procedure that the CC entity has entered state U8, connect request.
Expected sequence
UE SS
1 the UE is made to accept the call by the
user
2 -> CONNECT
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall send a CONNECT message and enter the CC-state U8, "Connect Request".
10.1.3.4.2 Incoming call / U7 call received / termination requested by the user
The call control entity of the UE being in the state, U7, a user requests to terminate incoming call.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1894
References
TS 24.008 clause 5.4.3.1
To verify that a CC entity of a UE in CC-state U7, "Call Received", upon request by the user to terminate will send a
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U7. The user initiates clearing the incoming call. The UE sends a DISCONNECT
message. The SS checks by using the status enquiry procedure that the CC entity has entered state U11, disconnect
request.
Expected sequence
UE SS
1 the UE is made to terminate/reject the
call
2 -> DISCONNECT
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1895
10.1.3.4.3 Incoming call / U7 call received / DISCONNECT received
References
TS 24.008 clause 5.4.4.1.1.1
To verify that a CC entity of a UE in CC-state U7, "Call Received", upon receipt of a DISCONNECT with a progress
indicator indicating in-band information from network, if a DTCH was not assigned, returns a RELEASE message and
enters the CC-state U19, "Release Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U7. The SS sends a DISCONNECT message. The UE responds with a
RELEASE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U19,
release request.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1896
Expected sequence
UE SS
2 -> RELEASE
3 <- STATUS ENQUIRY

NOTE: The Progress Indicator, Progress Description value:
After step 1 a UE if a DTCH was not assigned, shall return a RELEASE message and enter the CC-state U19, "Release
Request".
10.1.3.4.4 Incoming call / U7 call received / RELEASE received
References
TS 24.008 clause 5.4.3.3
1) To verify that a CC entity of a UE in CC-state U7, "Call Received", upon receipt of a RELEASE will return a
RELEASE COMPLETE and enter the CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1897
Test procedure
entity of the UE is brought to the state U7. The SS sends a RELEASE message. The UE responds with a RELEASE
COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U0,
null, with the relevant transaction identifiers.
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall return a RELEASE COMPLETE message.
10.1.3.4.5 Incoming call / U7 call received / lower layer failure
References
TS 24.008 clause 4.5.2.3 and clause 4.5.3, TS 25.331 clause 8.3.1, and clause 8.5.6.
To verify that a CC entity of a UE in CC-state U7, "Call Received", having detected a lower layer failure returns to idle
mode, the CC entity is in state U0, "Null".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1898
Initial conditions
System Simulator:
User Equipment:
Test procedure
telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The UE is
brought to the state U7. The SS modifies the scrambling code of downlink transmission(DL DPCH) to generate a lower
layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends
RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-
modifies the scrambling code of downlink transmission(DL DPCH) to the original one and waits 60 s. The SS will
Expected sequence
UE SS
5 SS SS waits 60 s.
DCCH

None.
10.1.3.4.6 Incoming call / U7 call received / unknown message received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1899
References
TS 24.008 clause 8.4.
To verify that a CC entity of a UE in CC-state U7, "Call Received", having received an unknown message from its peer
entity returns a STATUS message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U7. The SS sends a message with message type not defined for the protocol
discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS checks by using the status
enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall return a STATUS message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1900
10.1.3.4.7 Incoming call / U7 call received / DTCH assignment
channel.
It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call
establishment phase.
Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but
may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2).
References
TS 24.008 clause 5.2.2.7.
To verify that a CC entity of a UE in CC-state U7, "Call Received", when a traffic channel is allocated by the network
performing the radio bearer establishment procedure, stays in CC-state U7.
Initial conditions
System Simulator:
User Equipment:
Test procedure
entity of the UE is brought to the state U7. The SS sends a RADIO BEARER SETUP for traffic channel to the UE. The
UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS verifies by using the status enquiry
procedure that the state of the CC entity has remained unchanged.
Expected sequence
UE SS
2 <- STATUS ENQUIRY

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1901
None.
After step 1 the CC state U7, "Call Received", shall remain unchanged.
10.1.3.4.8 Incoming call / U7 call received / RELEASE COMPLETE received
The call control entity of the UE being in the state, U7, the call is cleared by a RELEASE COMPLETE message sent by
the SS.
the "null" state.
References
1) To verify that a CC entity of the UE in CC-state U7, "Call received", upon receipt of a RELEASE COMPLETE
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile terminating transaction
Initial conditions
System Simulator:
User Equipment:
Test procedure
immediate connection; if the UE supports MT telephony without immediate connection, the selected service is
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1902
telephony. If necessary, the UE is configured for that basic service. The mobile terminated call is initiated. The CC
entity of the UE is brought to U7. The SS sends a RELEASE COMPLETE message to the UE. The SS checks by using
the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
UE SS
1 <- RELEASE COMPLETE note 1
2 <- STATUS ENQUIRY
3 -> RELEASE COMPLETE cause #81 (invalid TI value), note 2

NOTE 1: With the cause value chosen arbitrarily.
NOTE 2: TI flag has the value indicating the SS as an originator of the call.
10.1.3.5 Incoming call / U8 connect request
10.1.3.5.1 Incoming call / U8 connect request / CONNECT acknowledged
The call control entity of the UE being in the state, U8, a CONNECT ACKNOWLEDGE message is received by the
UE.
In the "connect request" state, the call control entity of the UE shall, upon receipt of a CONNECT ACKNOWLEDGE
message: stop timer T313 and enter the "active" state.
References
TS 24.008 clause 5.2.2.6.
To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of CONNECT ACKNOWLEDGE
shall enter the CC-state U10, " Active".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1903
Initial conditions
System Simulator:
User Equipment:
Test procedure
selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated
call is initiated. The CC entity of the UE is brought to the state U8 (if the UE uses immediate connection for the
selected basic service then p =Y, otherwise p =N). The SS sends a CONNECT ACKNOWLEDGE message. The SS
checks by using the status enquiry procedure that the CC entity of the UE has entered state U10, active.
Expected sequence
UE SS
A1 Radio Bearer Setup Procedure p =Y, See TS34.108
2 <- CONNECT ACKNOWLEDGE
3 <- STATUS ENQUIRY

None.
After step 2 a UE shall enter the CC-state U10, "Active".
10.1.3.5.2 Incoming call / U8 connect request / timer T313 time-out
at the UE side.
1) When timer T313 expires prior to the receipt of a CONNECT ACKNOWLEDGE message, the UE shall initiate
clearing in accordance with clause 5.4.3.
2) Apart from the exceptions identified in TS 24.008 clause 5.4.2, the call control entity of the UE shall initiate
clearing by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and
entering the "disconnect request" state.
References
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1904
To verify that a CC entity of a UE in CC-state U8, "Connect Request", having waited for a reasonable length of time
(e.g. expiry of timer T313) without receiving the appropriate protocol message to complete the incoming call, shall
initiate the clearing of that incoming call by sending the CC message DISCONNECT and enter the CC-state U11,
"Disconnect Request".
Initial conditions
System Simulator:
User Equipment:
Test procedure
selected basic service then p =Y, otherwise p =N). The T313 expires at the UE and the UE sends a DISCONNECT
message and enters state U11, disconnect request. The SS checks by using the status enquiry procedure that the UE has
entered the correct state.
Expected sequence
UE SS
2 -> DISCONNECT Shall not be sent before 15 s after entry
into state U8. But, shall be sent before
1,1 * T313 after entry into state U8.
3 <- STATUS ENQUIRY

None.
After step A1 a UE shall initiate the clearing of that incoming call by sending a DISCONNECT message and enter the
CC-state U11, "Disconnect Request".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1905
10.1.3.5.3 Incoming call / U8 connect request / termination requested by the user
The call control entity of the UE being in the state, U8, the user requests for releasing of the call.
References
TS 24.008 clause 5.4.3.1
To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon request by the user to terminate will send a
Initial conditions
System Simulator:
User Equipment:
Test procedure
selected basic service then p =Y, otherwise p =N). Then the user requests termination of the call. The UE sends a
DISCONNECT message and enters state U11, disconnect request. The SS verifies by using the status enquiry procedure
that the UE has entered the correct state.
Expected sequence
UE SS
2 the user requests to clear the call
3 -> DISCONNECT
4 <- STATUS ENQUIRY

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1906
None.
After step 2 a UE shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
10.1.3.5.4 Incoming call / U8 connect request / DISCONNECT received with in-band
information
References
TS 24.008 clause 5.4.4.1.1.1
To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a DISCONNECT with progress
indicator #8 enters CC-state U12, if the traffic channel is in speech mode, and that the UE sends a RELEASE message
and enters CC-state U19 if the DTCH is not in speech mode.
Initial conditions
System Simulator:
User Equipment:
Test procedure
call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a DISCONNECT message containing
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1907
indication of in-band information availability to the UE. If channel mode is speech, the UE enters state U12, disconnect
indication. If channel mode is not speech, the UE sends a RELEASE message and enters state U19, release request.
Expected sequence
UE SS
B2 -> RELEASE

NOTE: The Progress Indicator, Progress description value:
After step 1 a UE shall enter CC-state U12, if the traffic channel is in speech mode. If the DTCH is not in speech mode,
the UE shall send a RELEASE message and enter CC-state U19.
10.1.3.5.5 Incoming call / U8 connect request / DISCONNECT received without in-band
information
References
TS 24.008 clause 5.4.4.1.2.1
To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a DISCONNECT without
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1908
Initial conditions
System Simulator:
User Equipment:
Test procedure
call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a DISCONNECT message not
request.
Expected sequence
UE SS
2 -> RELEASE
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall return a RELEASE message and enter the CC-state U19, "Release Request".
10.1.3.5.6 Incoming call / U8 connect request / RELEASE received
References
TS 24.008 clause 5.4.3.3
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1909
1) To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a RELEASE will return a
RELEASE COMPLETE and enter the CC-state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a RELEASE message. The UE
responds with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC
entity has entered state U0, null, with the relevant transaction identifiers.
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall return a RELEASE COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1910
10.1.3.5.7 Incoming call / U8 connect request / lower layer failure
References
To verify that a CC entity of a UE in CC-state U8, "Connect Request", having detected a lower layer failure returns to
idle mode, the CC entity is in state U0, "Null".
Initial conditions
System Simulator:
User Equipment:
Test procedure
call is initiated. The UE is brought to the state U8. The SS modifies the scrambling code of downlink transmission (DL
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1911
Expected sequence
UE SS
5 SS SS waits 60 s.
DCCH

None.
10.1.3.5.8 Incoming call / U8 connect request / DTCH assignment
channel.
It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call
establishment phase.
Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but
may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2
References
TS 24.008 clause 5.2.2.7.
To verify that a CC entity of a UE in CC-state U8, "Connect Request", when a traffic channel is allocated by the
network performing the radio bearer establishment procedure, stays in the CC-state U8.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1912
Test procedure
call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a RADIO BEARER SETUP for traffic
channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS verifies by
Expected sequence
UE SS
2 <- STATUS ENQUIRY

None.
After step 1 the CC-state U8, "Connect Request", shall remain unchanged.
10.1.3.5.9 Incoming call / U8 connect request / unknown message received
References
TS 24.008 clause 8.4.
To verify that a CC entity of a UE in CC-state U8, "Connect Request", having received an unknown message from its
peer entity returns a STATUS message.
Initial conditions
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1913
User Equipment:
Test procedure
call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a message with message type not
Expected sequence
UE SS
3 <- STATUS ENQUIRY

None.
After step 1 a UE shall return a STATUS message.
10.1.4 In call functions
10.1.4.1 In-call functions / DTMF information transfer
10.1.4.1.1 In-call functions / DTMF information transfer / basic procedures
Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used
from terminal instruments in telecommunication networks.
1) A user may cause a DTMF tone to be generated e.g. by depression of a key in the UE. The relevant action is
interpreted by the UE as a requirement for a DTMF digit to be sent in a START DTMF message on an
established FACCH. This message contains the value of the digit to be transmitted (0, 1, ..., 9, A, B, C, D, *, #).
Only a single digit will be transferred in each START DTMF message.
2) Upon receiving the START DTMF message the network will reconvert the received digit back into a DTMF
tone which is applied toward the remote user and returns a START DTMF ACKNOWLEDGE message to the
UE. This acknowledgement may be used in the UE to generate an indication as a feedback for a successful
transmission.
3) When the user indicates that the DTMF sending should cease e.g. by releasing the key the UE will send a STOP
DTMF message to the network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1914
References
Conformance requirement 2 and 4: TS 24.008 clause 5.5.7.2
1) To verify that an UE supporting the Mobile originating DTMF protocol control procedure, having a CC entity
for speech in state U10, "Active": when made to send a DTMF tone, sends a START DTMF message.
2) To verify that an UE supporting the Mobile originating DTMF protocol control procedure, having a CC entity
for speech in state U10, "Active": when made to send a DTMF tone (the corresponding IA5 character being
selected from among the ones supported), sends a START DTMF message specifying the correct IA5 character
in the "keypad information" field of the keypad facility information element and to verify that acknowledgement
send by the SS is used in the UE to generate a feedback indication for a successful transmission, if applicable.
3) To verify that the UE will send a STOP DTMF message to the network.
4) To verify that the state U10 of the UE CC entity has remained unchanged throughout the test procedure.

- supported teleservices;
- supported character set (e.g. 0-9, #, *, A, B, C, D);
- if and how DTMF tone is indicated to the user.
Initial conditions
System Simulator:
User Equipment:
The UE is brought into the state U10 "Active" by using table 10.1.2/1.
Test procedure
The UE being in the active state, a user causes a DTMF tone to be generated e.g. by depression of a key in the UE. A
DTMF digit corresponding to the digit indicated by the user is sent in a START DTMF message by the UE. The SS will
return a START DTMF ACKNOWLEDGE message to the UE. This acknowledgement may be used in the UE to
generate an indication as a feedback for a successful transmission. Then the user indicates that the DTMF sending
should cease e.g. by releasing the key. The UE will send a STOP DTMF message to the network which is
acknowledged with STOP DTMF ACKNOWLEDGE by the SS.
The sequence described above is repeated for each of the applicable characters 0-9, #, *, A, B, C, and D.
Then a case of rejecting a DTMF tone is tested.
The state of the UE is verified throughout the test procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1915
Expected sequence
UE SS
1 SS Request the user to cause a DTMF tone
to be generated
-> START DTMF the SS will verify that the transmitted
information corresponds to the digit
pressed
2 <- START DTMF ACKNOWLEDGE possible indication of a DTMF tone
depending the ICS/IXIT statements
3 <- STATUS ENQUIRY
5 -> STOP DTMF
6 <- STOP DTMF ACKNOWLEDGE the DTMF tone indication shall be
stopped
7 the steps 1-6 shall be repeated for each
of the applicable characters 0-9, #, *, A,
B, C, D.
8 <- STATUS ENQUIRY
10 SS Request the user to cause a DTMF tone
to be generated.
11 -> START DTMF
12 <- START DTMF REJ ECT
13 <- STATUS ENQUIRY

None.
Upon a user making to send a DTMF tone the UE shall send a START DTMF message on the FACCH to SS.
The SS will verify that the transmitted information corresponds to the digit pressed in the UE.
After step s 2 and 7 (successful DTMF transmission) the CC-state U10, "Active", shall remain unchanged.
After step 12 (unsuccessful DTMF transmission) the CC-state U10, "Active", shall remain unchanged.
10.1.4.2 In-call functions / user notification
10.1.4.2.1 In-call functions / User notification / UE terminated
This is a case for testing user notification procedure terminated by the user equipment.
The mobile terminating user notification procedure allows the network to notify a mobile station of any appropriate
call-related event during the "active" state of a call. The procedure consists in the network sending a NOTIFY message
to the mobile station. No state change occurs at any of the interface sides following the sending or the receipt of this
message (but an appropriate indication may optionally be generated in the mobile station).
References
TS 24.008 clause 5.3.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1916
To verify that a CC entity of a UE in CC-state U10, "active", upon receiving of a NOTIFY message remains in the
active state.
- supported circuit switched basic services.
Initial conditions
System Simulator:
User Equipment:
Test procedure
The UE being in the active state, the SS will send a NOTIFY message to the UE. The state of the UE is checked after
that.
Expected sequence
UE SS
1 <- NOTIFY
2 <- STATUS ENQUIRY

None.
After step 1 the CC-state U10, "active", shall remain unchanged.
10.1.4.3 In-call functions / channel changes
The two following test cases are for testing some elementary radio resource level procedures during an active state of a
call to ensure call maintenance also during Hard handover.
10.1.4.3.1 In-call functions / channel changes / a successful channel change in active state/
Hard handover
This is a case to test a change of the frequency of a physical channel during active state of a call.
1) The UE being in the active state after having successful completed a physical channel reconfiguration, shall
remain in the active state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1917
References
TS 24.008 clause 5.3.4.3.2, TS 25.331 clause 8.3.5.
To verify that the UE being in the active state after having successful completed a physical channel reconfiguration
remains in the active state.
- supported circuit switched basic services;
Initial conditions
System Simulator:
User Equipment:
Test procedure
The UE being in the active state, the SS initiated physical channel reconfiguration procedure causing an intracell change
of channel by sending a PHYSICAL CHANNEL RECONFIGURATION message to the UE. The UE performs
physical channel reconfiguration procedure and after the main signalling link is successfully established, the UE returns
a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC. The
state of the UE is then checked.
Expected sequence
UE SS
1 <- PHYSICAL CHANNEL RECONFIGURATION
2 -> PHYSICAL CHANNEL RECONFIGURATION
COMPLETE

3 <- STATUS ENQUIRY

None.
After step 2 the UE shall remain in the active state.
10.1.4.3.2 In-call functions / channel changes / an unsuccessful channel change in active
mode/Hard handover
This is a case to test an unsuccessful change of the frequency of a physical channel during active state of a call.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1918
1) The UE, when returning to the old channel after physical channel reconfiguration failure, shall remain in the
active state.
References
TS 24.008 clause 5.3.4.3.
To verify that the UE, when returning to the old channel after physical channel reconfiguration failure, will remain in
the active state.
- supported circuit switched basic services.
Initial conditions
System Simulator:
User Equipment:
Test procedure
The SS sends a PHYSICAL CHANNEL RECONFIGURATION message, but does not activate the assigned physical
channel. The UE shall attempt try to activate the new channel (this is not verified) and shall then reactivate the "old"
channel. The UE shall send a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH using
AM RLC and shall set the cause value in IE "failure cause" to "physical channel failure". The state of the UE is then
checked.
Expected sequence
UE SS

1 <- PHYSICAL CHANNEL RECONFIGURATION The UE attempts and fails to re-
configure the physical channel.

2 -> PHYSICAL CHANNEL RECONFIGURATION
FAILURE
NOTE
3 <- STATUS ENQUIRY

NOTE: With the cause value "physical channel failure".
After step 2 the UE shall remain in the active state.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1919
10.1.4.4 In-call functions / UE terminated in-call modification
10.1.4.4.1 In-call functions / UE terminated in-call modification / modify when new mode is
not supported
This test is not applicable for R99.
10.1.4.5 In-call functions / UE originated in-call modification
10.1.4.5.1 In-call functions / UE originated in-call modification / a successful case of
modifying
10.1.4.5.2 In-call functions / UE originated in-call modification / modify rejected
10.1.4.5.3 In-call functions / UE originated in-call modification / an abnormal case of
acceptance
10.1.4.5.4 In-call functions / UE originated in-call modification / an abnormal case of
rejection
10.1.4.5.5 In-call functions / UE originated in-call modification / time-out of timer T323
10.1.4.5.6 In-call functions / UE originated in-call modification / a successful channel change
in state mobile originating modify
10.1.4.5.7 In-call functions / UE originated in-call modification / an unsuccessful channel
change in state mobile originating modify
10.1.4.5.8 In-call functions / UE originated in-call modification / unknown message received
10.1.4.5.9 In-call functions / UE originated in-call modification / a release complete received
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1920
10.2 Call Re-establishment
10.2.1 Void
10.3 User to user signalling
10.3.1 Definition
The "user to user" information element is used to convey information between the mobile user and a remote ISDN user.
NOTE: There is no test for an UE originating call including a "user-user" information element since it is not a
mandatory UE feature.
The inclusion of the "user-user" information element in downlink call control messages shall cause no adverse effects
on the operation of the UE.
References
TS 24.008 clauses 9.3.7, 9.3.23.1 and 10.5.4.25.
10.3.3 Purpose of the test
The purpose of this test is to verify that inclusion of the "user-user" information element in either of the down link
messages, SETUP or DISCONNECT causes no adverse effects on the operation of the UE.
- Supported MT circuit switched basic services.
- Support of user-user information element, and details of suitable codings.
Initial conditions.
System Simulator:
The SS simulates 1 cell, with default parameters.
User Equipment:
The UE is in MM-state "idle updated", with a valid TMSI and CKSN.
Test procedure
The SS attempts to set up a mobile terminated call, with one of the supported circuit switched basic services which has
been arbitrarily chosen, the generic call set up procedures for mobile terminating circuit switched calls,(either speech or
data) as specified in TS 34.108 clause 7. The default SETUP message contents are modified to include the user-user
Information Element. The UE shall not respond adversely to the inclusion of the user-user information element.
After 30 s the SS sends a DISCONNECT message, again the UE shall not respond adversely to the inclusion of the
user-user information element, but shall continue to clear down the call normally.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1921
Expected sequence
UE SS
1 Generic Call Setup procedure for mobile
terminating circuit switched calls defined
in TS 34.108, depending on choice of
Bearer Capability. The SETUP message
contains the user-user IE, see Specific
message contents.
2 The SS waits 30 s.
3 <- DISCONNECT Message contains the user-user IE, see
4 -> RELEASE
5 <- RELEASE COMPLETE

SETUP message contains user-user IE with the string coded in IA5 characters: for example "Call Setup".
DISCONNECT message contains user-user IE with the string coded in IA5 characters: for example "Call Disconnect".
(The codings above are for example only. For the case of an UE which supports "user-user" signalling it may be
necessary to add meaning to the data fields, see ICS/IXIT statements.)
NOTE: The codings above are for example only. For the case of an UE which supports "user-user" signalling it
may be necessary to add meaning to the data fields, see ICS/IXIT statements.
10.3.5 Test requirements
After steps 1 and 3 the inclusion of the "user-user" information element in downlink call control messages shall cause
no adverse effects on the operation of the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1922
11 Session Management Procedures
11.1 PDP context activation
11.1.1 Initiated by the UE
11.1.1.1 Attach initiated by context activation/QoS Offered by Network is the QoS
Requested
SM procedures for identified access can only be performed if a GMM context has been established between the UE and
the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM
context by use of the GMM procedures as described in chapter 4, 3GPP TS 24.008. After GMM context establishment,
SM uses services offered by GMM (see 3GPP TS 24.007). Ongoing SM procedures are suspended during GMM
procedure execution.
In UMTS only, integrity protected signalling (see 3GPP TS 24.008 clause 4.1.1.1.1) and in general, see 3GPP TS
33.102) is mandatory. In UMTS only, all protocols shall use integrity protected signalling. Integrity protection of all SM
signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is
done using the security mode control procedure (TS 25.331).
In order to request a PDP context activation, the UE sends an ACTIVATE PDP CONTEXT REQUEST message to the
network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the selected NSAPI,
PDP type, requested QoS and, if the UE requests a static address, the PDP address.
Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message, the network selects a radio priority level based
on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the
message ACTIVATE PDP CONTEXT ACCEPT the UE shall stop timer T3380, shall enter the state PDP-ACTIVE.
If the QoS offered by the network is the same as the QoS requested by the UE, the UE shall accept the negotiated QoS.
In UMTS, both the network and the UE shall store the LLC SAPI and the radio priority in the PDP context. If a UMTS
to GSM system change is performed, the new SGSN shall initiate establishment of the logical link using the negotiated
QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context as in a GSM to GSM
Routing Area Update.
A UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI, while a UE which is capable
of operating only in UMTS shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid
unnecessary value range checking and any other possible confusion in the network.
NOTE 1: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the
messages, in order to support handover between UMTS and GSM networks.
Reference
3GPP TS 24.008 clauses 6.1.1 and 6.1.3.1.1.
To check that the UE initiates a PS attach, if one is not already active, when PDP context activation is requested.
To test the behaviour of the UE when SS responds to the PDP context activation request with the requested QoS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1923
Initial conditions
System Simulator:
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
- PS Supported yes/no
- Auto Attach supported yes / no
- Method of context activation
Test procedure
The UE is attached, then the Detach Request is originated from the UE indicating "GPRS detach without switching
off". The SS responds with a Detach Accept after completing the security mode procedures. A PDP context activation is
then requested by the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested PDP context
activation. The SS returns the ATTACH ACCEPT message to the UE. Now session management can proceed with PDP
context activation.
On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP CONTEXT ACCEPT is
returned by the SS with the same requested QoS. The contents of the ACTIVATE PDP CONTEXT REQUEST message
shall then be checked. The SS then waits for T3380 seconds to ensure T3380 has been stopped and no more
ACTIVATE PDP CONTEXT REQUEST messages are sent by the UE. The SS then sends a MODIFY PDP CONTEXT
REQUEST message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the
context has been set up.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1924
Expected sequence
UE SS
0a UE Detach is performed by the UE using MMI
or AT Commands
0 SS SS checks that the IE "Establishment
cause" in the received RRC CONNECTION
REQUEST message is set to "Detach".
1 DETACH REQUEST
2 DETACH ACCEPT SS sends Detach Accept message.
2a SS The SS releases the RRC connection.
3 UE Initiate a context activation
3a SS SS checks that the IE "Establishment
REQUEST message is set to "Registration".
4 ATTACH REQUEST Request attach with Follow-on request
pending
4a SS The SS starts ciphering and integrity
protection.
5 ATTACH ACCEPT Accept attach
Negotiated Ready timer value IE should not
be included
Force to standby IE set to Force to standby
not indicated
6 ACTIVATE PDP CONTEXT
REQUEST
Request a PDP context activation (with
static PDP address)
6a SS The SS establishes the RAB.
ACCEPT
Accept the PDP context activation
8 SS Wait for T3380 seconds to ensure no further
activate request messages come from the
UE
9 MODIFY PDP CONTEXT
REQUEST (NETWORK TO UE
DIRECTION)
SS sends a modify request to UE for the
activated context
ACCEPT (UE TO NETWORK
DIRECTION)
UE accepts the modification request from
the SS to show context is activated
11 SS SS releases the RRC connection due to
inactivity (no user data transferred)

None.
At step 0 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to
"Detach".
At step 3a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to
"Registration".
When requesting a PDP context activation, the UE shall:
- initiate a PS ATTACH if one is not already active;
- when the SS responds to a PDP context activation request, initiated by the UE, with the requested QoS, the UE
shall complete the PDP context activation procedure. To check if the PDP context activation was successful, SS
shall request PDP context modification and UE shall accept it.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1925
11.1.1.1a Attach initiated by context activation/QoS Offered by Network is the QoS
Requested/Correct handling of QoS extensions for rates above 8640 kbps
11.1.1.1a.1 Definition and applicability
UEs which support HS-PDSCH and supporting rates above 8640 kbps (UE Category 7 and UE Category 10).
1. SM procedures for identified access can only be performed if a GMM context has been established between the
UE and the network. If no GMM context has been established, the MM sublayer has to initiate the establishment
of a GMM context by use of the GMM procedures as described in chapter 4. After GMM context establishment,
SM uses services offered by GMM (see 3GPP TS 24.007). Ongoing SM procedures are suspended during GMM
procedure execution.

In UMTS only, integrity protected signalling (see 3GPP TS 24.008 clause 4.1.1.1.1) and in general, see 3GPP TS
33.102) is mandatory. In UMTS only, all protocols shall use integrity protected signalling. Integrity protection of
all SM signalling messages is the responsibility of lower layers. It is the network which activates integrity
protection. This is done using the security mode control procedure (TS 25.331).
2. In order to request a PDP context activation, the UE sends an ACTIVATE PDP CONTEXT REQUEST message
to the network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the
selected NSAPI, PDP type, requested QoS and, if the UE requests a static address, the PDP address. The UE
shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the
MS.

Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message, the network selects a radio priority level
based on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message. Upon
receipt of the message ACTIVATE PDP CONTEXT ACCEPT the UE shall stop timer T3380, shall enter the
state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS requested by
the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure.

In UMTS, both the network and the UE shall store the LLC SAPI and the radio priority in the PDP context. If a
UMTS to GSM system change is performed, the new SGSN shall initiate establishment of the logical link using
the negotiated QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context
as in a GSM to GSM Routing Area Update.

A UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI, while a UE which is
capable of operating only in UMTS shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to
avoid unnecessary value range checking and any other possible confusion in the network.
NOTE 1: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the
messages, in order to support handover between UMTS and GSM networks.
3. The quality of service is a type 4 information element with a minimum length of 14 octets and a maximum
length of 16 octets. The QoS requested by the MS shall be encoded both in the QoS attributes specified in octets
3-5 and in the QoS attributes specified in octets 6-14.

In the UE to network direction and in the network to UE direction the following applies:
- Octets 15 and 16 are optional. If octet 15 is included, then octet 16 shall also be included.
- A QoS IE received without octets 6-16, without octets 14-16, or without octets 15-16 shall be accepted by the
receiving entity.
NOTE: This behavior is required for interworking with entities supporting an earlier version of the protocol, or
when the Maximum bit rate for downlink is negotiated to a value lower than 8700 kbps.
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1926
8 7 6 5 4 3 2 1
Quality of service IEI octet 1
Length of quality of service IE Octet 2
0 0
spare
Delay
class
Reliability
class
octet 3
Peak
throughput
0
spare
Precedence
class
octet 4
0 0 0
spare
Mean
throughput
octet 5
Traffic Class Delivery order Delivery of erroneous
SDU
Octet 6
Maximum SDU size Octet 7
Maximum bit rate for uplink Octet 8
Maximum bit rate for downlink Octet 9
Residual BER SDU error ratio Octet 10
Transfer delay Traffic Handling
priority
Octet 11

Guaranteed bit rate for uplink
Octet 12
Guaranteed bit rate for downlink Octet 13
0 0 0
spare
Signal-
ling
Indicat-
ion
Source Statistics Descriptor Octet 14
Maximum bit rate for downlink (extended) Octet 15
Guaranteed bit rate for downlink (extended) Octet 16

..
Maximum bit rate for downlink, octet 9 (see 3GPP TS 23.107)

Coding is identical to that of Maximum bit rate for uplink.

If the sending entity wants to indicate a Maximum bit rate for downlink higher than 8640 kbps, it shall set octet 9
to 11111110, i.e. 8640 kbps, and shall encode the value for the Maximum bit rate in octet 15.
..
Maximum bit rate for downlink (extended), octet 15
Bits
8 7 6 5 4 3 2 1
In MS to network direction and in network to MS direction:
0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 9.

0 0 0 0 0 0 0 1 Ignore the value indicated by the Maximum bit rate for downlink in octet 9. The maximum bit
rate is
0 1 0 0 1 0 1 0 8600 kbps +((the binary coded value in 8 bits) * 100 kbps), giving a range of values from
8700 kbps to 16000 kbps in 100 kbps increments.

Reference
3GPP TS 24.008 clauses 6.1.1, 6.1.3.1.1 and 10.5.6.5.
To check that the UE initiates a PS attach, if one is not already active, when PDP context activation is requested.
To check that the UE performs correct handling of QoS extensions for rates above 8640 kbps.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1927
To check the UE successfully completes the PDP context activation when the SS responds to the PDP context activation
request with the requested QoS.
Initial conditions
System Simulator:
User Equipment:
- Auto Attach supported yes / no
- Supported downlink rates above 8640 kbps yes/no
Test procedure
Table 11.1.1.1a.1 Test execution test parameters
Execution Maximum bit rate for downlink

1 Value supported by the UE which
is less than 8640 kbps
2 Value supported by the UE which
is bigger than 8640 kbps

The UE is attached, then the Detach Request is originated from the UE indicating "GPRS detach without switching
off". The SS responds with a Detach Accept after completing the security mode procedures. A PDP context activation is
then requested. The IE Maximum bit rate for downlink is selected according to Table 11.1.1.1a.1 for execution=1.
The PS attach (ATTACH REQUEST) is then indirectly caused by a requested PDP context activation. The SS returns
the ATTACH ACCEPT message to the UE. Now session management can proceed with PDP context activation.
On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP CONTEXT ACCEPT is
returned by the SS with the same requested QoS. The contents of the ACTIVATE PDP CONTEXT REQUEST message
shall then be checked. The SS then waits for T3380 seconds to ensure T3380 has been stopped and no more
ACTIVATE PDP CONTEXT REQUEST messages are sent by the UE. The SS then sends a MODIFY PDP CONTEXT
REQUEST message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the
context has been set up.
The test case is repeated with test parameters according to Table 11.1.1.1a.1 for execution=2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1928
Expected sequence
UE SS
0a UE Detach is performed by the UE using MMI
or AT Commands
0 SS SS checks that the IE "Establishment
1 DETACH REQUEST
2 DETACH ACCEPT SS sends Detach Accept message.
3 UE Initiate a context activation with a requested
Maximum bit rate for downlink according to
Table 11.1.1.1a.1
4 ATTACH REQUEST Request attach with Follow-on request
pending
4a SS The SS starts ciphering and integrity
protection.
5 ATTACH ACCEPT Accept attach
Negotiated Ready timer value IE should not
be included
Force to standby IE set to Force to standby
not indicated
REQUEST
static PDP address)

ACCEPT
UE
DIRECTION)
activated context
DIRECTION)
the SS to show context is activated
11 SS SS releases the RRC connection due to
inactivity (no user data transferred)

The test sequence is repeated according to Table 11.1.1.1a.1.
None.
"Detach";
"Registration";
At step 4 the UE shall initiate a PS ATTACH if not already active;
At step 6 the UE shall send an ACTIVE PDP CONTEXT REQUEST message with the IE Requested QoS and
Maximum bit rate for downlink set to value according to Table 11.1.1.1a.1;
At step 10 the UE shall send a MODIFY PDP CONTEXT ACCEPT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1929
11.1.1.2 QoS offered by the network is a lower QoS
11.1.1.2.1 Void
11.1.1.2.2 Void
11.1.2 PDP context activation requested by the network, successful and
unsuccessful
11.1.2.1 Definition
This test needs to take into account the number of active PDP contexts supported simultaneously by the UE, to be able
to test the response when all contexts are activated and the network tries to initiate a new context.
1) Successful PDP context activation requested by the network
In order to request a PDP context activation, the network sends a REQUEST PDP CONTEXT ACTIVATION
message to the UE and starts timer T3385. The message contains an offered PDP address. If available, the APN
shall be included in the REQUEST PDP CONTEXT ACTIVATION message.
Upon receipt of a REQUEST PDP CONTEXT ACTIVATION message, the UE shall than either initiate the PDP
context activation procedure as described in 3GPP TS 24.008 clause 6.1.3.1.1, or shall reject the activation
request by sending a REQUEST PDP CONTEXT ACTIVATION REJ ECT message as described in 3GPP TS
24.008 clause 6.1.3.1.4. The value of the reject cause IE of the REQUEST PDP CONTEXT ACTIVATION
REJ ECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another context".
The ACTIVATE PDP CONTEXT REQUEST message sent by the UE in order to initiate the PDP context
activation procedure shall contain the PDP address, PDP Type and APN requested by the network in the
REQUEST PDP CONTEXT ACTIVATION message.
Upon receipt of the ACTIVATE PDP CONTEXT REQUEST message, the network shall stop timer T3385.
The same procedures then apply as described for UE initiated PDP context activation (3GPP TS 24.008, clause
6.1.3.1.1.
2) Unsuccessful PDP context activation requested by the network
Upon receipt of the REQUEST PDP CONTEXT ACTIVATION message, the UE may reject the network
requested PDP context activation by sending the REQUEST PDP CONTEXT ACTIVATION REJ ECT message
to the network. The message contains the same TI as included in the REQUEST PDP CONTEXT
ACTIVATION and an additional cause code that typically indicates one of the following causes:
#26: insufficient resources;
#31: activation rejected, unspecified;
#40: feature not supported; or
#95 111: protocol errors.
The network shall stop timer T3385 and enter state PDP-INACTIVE.
3) Whenever a REQUEST PDP CONTEXT ACTIVATION message is received by the UE specifying a transaction
identifier relating to a PDP context not in state PDP-INACTIVE, the UE shall locally deactivate the old PDP
context relating to the received transaction identifier. Furthermore, the UE shall continue with the activation
procedure of a new PDP context as indicated in the received message.
Reference
3GPP TS 24.008 clauses 6.1.3.1.2, 6.1.3.1.4 and 8.3.2.f).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1930
To test behaviour of the UE upon receipt of a PDP context activation request from the SS:
a) When UE supports PDP context activation requested by the network
b) When UE supporting PDP context activation requested by the network, receives REQUEST PDP CONTEXT
ACTIVATION message with transaction identifier relating to an already active PDP context
c) When UE does not support PDP context activation requested by the network

Initial conditions
System Simulator:
User Equipment:
- Network requested PDP context activation supported yes/no
- Number of network initiated PDP contexts supported
Case 1
For a UE that supports PDP context activation requested by the network.
Test procedure
A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. On receipt of the ACTIVATE PDP
CONTEXT REQUEST message from the UE, an ACTIVATE PDP CONTEXT ACCEPT message is returned by the
SS. This is repeated until the maximum number of contexts supported by the UE is activated.
If the UE cannot support seven PDP contexts then one greater than the maximum supported by the UE should be
requested.
In response to the last activation request the UE shall return a REQUEST PDP CONTEXT ACTIVATION REJ ECT
message with cause set to 'insufficient resources', 'activation rejected, unspecified' or 'protocol errors' using cause values
#26, #31, #40 or #95-111.
REQUEST PDP CONTEXT ACTIVATION message is then sent by the SS using transaction identifier of the currently
active PDP context. The UE shall activate this context in place of the previous context.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1931
Expected sequence
UE SS
1 REQUEST PDP CONTEXT
ACTIVATION
SS sends Request a PDP context activation
to UE and starts timer T3385
REQUEST
UE replies with a PDP context activation
request, Traffic class set to Streaming class
or Interactive class or Background class
2a SS The SS stops timer T3385 and establishes
the Radio Access Bearer.
ACCEPT
SS accepts the PDP context activation
4 SS Steps 1-3 are repeated for the number of
Network Initiated contexts supported using
various values for Traffic class IE.
NOTE: If all 7 contexts are supported
steps 5 and 6 should not be
performed.
ACTIVATION
SS requests a PDP context activation and
starts timer T3385
ACTIVATION REJ ECT
The context activation request is rejected
with cause 'insufficient resources' or
'activation rejected, unspecified' or 'protocol
errors' using cause values #26, #31, #40 or
#95-111.
6a SS The SS stops timer T3385
ACTIVATION
SS requests a PDP context activation for an
existing context with TI the same as one of
the active PDP contexts and starts timer
T3385
8 UE UElocally deactivates the old PDP context
with the same TI value
REQUEST
UE continues with the activation of a new
PDP context to replace locally deactivated
context
9a SS The SS stops timer T3385 and releases
Radio Access Bearer for old PDP context.
9b SS The SS stops timer T3385 and establishes
the Radio Access Bearer for new PDP
context.
ACCEPT

Case 2
For an UE that does not support PDP context activation requested by the network.
Test procedure
A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. The UE shall then send a REQUEST PDP
CONTEXT ACTIVATION REJ ECT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1932
Expected sequence
UE SS
ACTIVATION
SS requests a PDP context activation and
starts timer T3385
ACTIVATION REJ ECT
Reject the PDP context activation request
with cause 'insufficient resources' or 'feature
not supported', 'activation rejected,
unspecified' or 'protocol errors' using cause
values #26, #31, #40 or #95-111.
3 SS The SS stops timer T3385

Case 1
Step 6: REQUEST PDP CONTEXT ACTIVATION REJ ECT message contains the same TI as included in the
REQUEST PDP CONTEXT ACTIVATION message in step 5.

Step 7: TI IE value is equal to the TI value of one of the active PDP contexts, Offered PDP address IE value and/or
Access point name IE value are (is) different from the corresponding IE value(s) in the existing PDP context.
Case 2
Step 2, REQUEST PDP CONTEXT ACTIVATION REJ ECT message contains the same TI as included in the
REQUEST PDP CONTEXT ACTIVATION message in step 1.
The UE that is configured to support one or more PDP contexts simultaneously shall:
- accept PDP context activation initiated by the SS if number of active contexts is lower than the maximum.
- locally deactivate the old PDP context when a REQUEST PDP CONTEXT ACTIVATION message is received,
specifying a transaction identifier relating to an active PDP context and continue with the activation procedure of
a new PDP context as indicated in the received message.
The UE that does not support PDP Context Activation (a number of active contexts supported by the UE is equal to
maximum or UE does not support PDP context) shall reject PDP context activation initiated by the SS.
11.1.3 Abnormal Cases
11.1.3.1 T3380 Expiry
1) On the first expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.
2) On the second expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.
3) On the third expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.
4) On the fourth expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.
5) On the fifth expiry of the timer T3380, the UE shall release all resources possibly allocated for this invocation
and shall abort the procedure; no automatic PDP context activation re-attempt shall be performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1933
Reference
3GPP TS 24.008 clause 6.1.3.1.5 a).
To test the behaviour of the UE when the SS does not reply to PDP CONTEXT ACTIVATION REQUEST.
Initial conditions
System Simulator:
User Equipment:
- Method of activating a context
Test procedure
A PDP context activation is requested by the user. The UE shall send the ACTIVATE PDP CONTEXT REQUEST
message five times with T3380 seconds between each message. After this, no further ACTIVATE PDP CONTEXT
REQUEST messages shall be sent by the UE.
Expected sequence
UE SS
REQUEST
Request a PDP context activation
3 SS T3380 seconds
REQUEST
5 SS T3380 seconds
REQUEST
7 SS T3380 seconds
REQUEST
9 SS T3380 seconds
REQUEST
ACTIVATE PDP CONTEXT REQUEST
messages are sent by the UE

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1934
UE shall re-send the ACTIVATE PDP CONTEXT REQUEST to SS five times in order to initiate PDP context, with
expiry of timer T3380 between messages. After fifth try, UE shall send no more ACTIVATE PDP CONTEXT
REQUEST to SS.
11.1.3.2 Collision of UE initiated and network requested PDP context activation
This test needs to take into account the number of PDP contexts supported by the UE, to be able to test the response
when the network tries to initiate a new context.
A collision of a UE initiated and a network requested PDP context activation procedure is identified by the UE if a
REQUEST PDP CONTEXT ACTIVATION message is received from the network after the UE has sent an
ACTIVATE PDP CONTEXT REQUEST message, and the UE has not yet received an ACTIVATE PDP CONTEXT
ACCEPT or ACTIVATE PDP CONTEXT REJ ECT message.
NOTE: In general, the UE is unable to test if the PDP type, PDP address and APN in the REQUEST PDP
CONTEXT ACTIVATION message are the same as those for the PDN to which it is attempting to
activate a context. This is because the UE may have omitted one or more of the parameters in the
ACTIVATE PDP CONTEXT REQUEST message, since it is relying on default values to be provided by
the network.
In the case of such a collision, the UE initiated PDP context activation shall take precedence over the
network requested PDP context activation. If the UE is able to compare the PDP type, PDP address and
APN requested in the ACTIVATE PDP CONTEXT REQUEST message with those requested in the
REQUEST PDP CONTEXT ACTIVATION message and these parameters are equal, then the UE shall
discard the REQUEST PDP CONTEXT ACTIVATION message and shall wait for the network response
to its ACTIVATE PDP CONTEXT REQUEST message. If the UE is not able to compare the PDP type,
PDP address, and APN requested in the ACTIVATE PDP CONTEXT REQUEST message with those
requested in the REQUEST PDP CONTEXT ACTIVATION message, then the UE shall send a
REQUEST PDP CONTEXT ACTIVATION REJ ECT message with the cause 'insufficient resources' to
the network, and wait for an ACTIVATE PDP CONTEXT ACCEPT message.

Reference
3GPP TS 24.008 clause 6.1.3.1.5 b), case: Static PDP address collision detected within the UE.
To test the behaviour of the UE when there is a collision between an UE initiated and network requested PDP context
activation detected by the UE.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1935
- Network requested PDP context activation supported yes/no
- Method of PDP context activation
Case 1
For an UE that supports PDP context activation requested by the network.
Test procedure
A PDP context activation is requested by the user with a static PDP address. After receipt of the ACTIVATE PDP
CONTEXT REQUEST message the SS sends a REQUEST PDP CONTEXT ACTIVATION message followed by an
ACTIVATE PDP CONTEXT ACCEPT message in a time less than T3380 (Use T3380/2). The UE shall send no
messages within this time.
Expected sequence
UE SS
REQUEST
static PDP address)
ACTIVATION
Request a PDP context activation request
4 SS Wait for T3380/2 seconds to ensure UE
does not re-send ACTIVATE PDP
CONTEXT REQUEST
ACCEPT

Case 2
For a UE that does not support PDP context activation requested by the network.
Test procedure
A PDP context activation is requested by the user. After receipt of the ACTIVATE PDP CONTEXT REQUEST
message the SS sends a REQUEST PDP CONTEXT ACTIVATION message. The UE shall send a REQUEST PDP
CONTEXT ACTIVATION REJ ECT message with cause set to 'insufficient resources'. The SS then sends an
ACTIVATE PDP CONTEXT ACCEPT.
Expected sequence
UE SS
REQUEST
ACTIVATION
ACTIVATION REJ ECT
Cause set to 'insufficient resources'.
ACCEPT

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1936
For Case 1 and Case 2:
Step 2: ACTIVATE PDP CONTEXT REQUEST message contains PDP address and APN IEs.
Step 3: REQUEST PDPD CONTEXT ACTIVATION message contains the same PDP address and APN values as in
Step 2.
In the case of such collision,
- UE that supports PDP context activation requested by the network shall discard the REQUEST PDP CONTEXT
ACTIVATION message from SS and wait for an ACTIVATE PDP CONTEXT ACCEPT message.
- UE that does not support PDP context activation requested by the network shall reject PDP context activation
initiated by the SS.
11.1.3.3 Network initiated PDP context activation request for an already activated
PDP context (on the UE side)
If the UE receives a REQUEST PDP CONTEXT ACTIVATION message with the same combination of APN, PDP
type and PDP address as an already activated PDP context, the UE shall deactivate the existing PDP context and, if any,
all the linked PDP contexts (matching the combination of APN, PDP type and PDP address) locally without notification
to the network and proceed with the requested PDP context activation.
Reference
3GPP TS 24.008 clause 6.1.3.1.5 d).
To test the behaviour of the UE when it detects a network initiated PDP context activation for the PDP context already
activated on the UE side.
Initial conditions
System Simulator:
User Equipment:
PS Supported yes/no
Method of PDP context activation
Test procedure
A PDP context activation is requested by the user. SS accepts PDP context activation. Secondary PDP context
activation is requested by the user. SS accepts secondary PDP context activation. SS sends a REQUEST PDP
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1937
CONTEXT ACTIVATION message with the same combination of APN, PDP type and PDP address as an already
activated PDP context. The UE deactivates the existing PDP context and linked secondary PDP context (matching the
combination of APN, PDP type and PDP address) locally without notification to the SS and proceeds with the requested
PDP context activation.
Expected sequence
UE SS
REQUEST
UE requests a PDP context activation
ACCEPT
4 ACTIVATE SECONDARY PDP
CONTEXT REQUEST
UE requests a secondary PDP context
activation
CONTEXT ACCEPT
SS accepts the secondary PDP context
activation
ACTIVATION
SS requests a PDP context activation with
the same combination of APN, PDP type
and PDP address as the activated PDP
context
7 UE UE locally deactivates the activated PDP
context and the secondary PDP context
REQUEST
UE replies with a Request PDP context
activation
ACCEPT

None.
When inconsistency of PDP context between the UE and network is detected by the UE, then local synchronisation
procedure shall be initiated in the UE. The PDP context and all (if any) linked contexts are implicitly deactivated and
the new request shall be proceeded.
11.1.4 Secondary PDP context activation procedures
11.1.4.1 Successful Secondary PDP Context Activation Procedure Initiated by the UE
11.1.4.1.1 QoS Offered by Network is the QoS Requested
In order to request a secondary PDP context activation with the same PDP address and APN as an already active PDP
context, the UE shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter
the state PDP-ACTIVE-PENDING and start timer T3380. The message contains the selected NSAPI, a QoS profile, a
requested LLC SAPI and the linked TI.
If the QoS offered by the network is the same as the QoS requested by the UE, then upon receipt of the message
ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the UE shall stop timer T3380.
In GSM the UE shall initiate establishment of the logical link for the LLC SAPI indicated by the network, with the
offered QoS and selected radio priority level, if no logical link has been already established for that SAPI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1938
Although not used in UMTS, LLC SAPI shall be included in the messages, in order to support handover between
UMTS and GSM networks.
Reference
3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1.
To test the behaviour of the UE when SS responds to a Secondary PDP context activation request with the requested
QoS.
Initial conditions
System Simulator:
User Equipment:
The UE and is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
- Secondary PDP context activation supported yes/no
Test procedure
A PDP context activation is requested by the user and accepted by the SS. Secondary PDP context activation is
requested by the user. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message an
ACTIVATE SECONDARY PDP CONTEXT ACCEPT is returned by the SS with the same requested QoS. The SS
then waits for T3380 seconds to ensure T3380 has been stopped and no more ACTIVATE SECONDARY PDP
CONREXT REQUEST messages are sent by the UE. The SS then sends a MODIFY PDP CONTEXT REQUEST
message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the context has
been set up.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1939
Expected sequence
UE SS
1 UE Initiate a PDP context activation
REQUEST
Activate a PDP context
ACCEPT
Accept the PDP context
4 UE Initiate a secondary PDP context activation
CONTEXT REQUEST
Request a Secondary PDP context
activation
CONTEXT ACCEPT
Accept the Secondary PDP context
activation
UE
DIRECTION)
activated context
DIRECTION)
the network to show context is activated

The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the
TI for the PDP context already activated. The SS can derive PDP address for the secondary PDP context from Linked
TI.
To pass the test the UE shall:
- when the SS responds to a Secondary PDP context activation request initiated by the UE, with the requested
QoS, the UE shall complete the Secondary PDP context activation procedure. To check if the Secondary PDP
context activation was successful, SS shall request PDP context modification and UE shall accept it.
11.1.4.1.2 QoS Offered by Network is a lower QoS
11.1.4.1.2.1 Void
11.1.4.1.2.2 Void
11.1.4.1.2.3 LLC SAPI rejected by the UE
11.1.4.1.2.3.1 Definition
This test can only be performed if LLC SAPI can be set by the user.
11.1.4.1.2.3.2 Conformance Requirement
In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the
UE shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network.
Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall select a radio priority
level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT
message, if the request can be accepted.
Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the UE shall stop timer T3380
and enter the state PDP-ACTIVE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1940
In GSM the UE shall initiate establishment of the logical link for the LLC SAPI indicated by the network if no logical
link has been already established for that SAPI. If the LLC SAPI indicated by the network can not be supported by the
UE, the UE shall initiate the PDP context deactivation procedure.
11.1.4.1.2.3.3 Test Purpose
To verify the behaviour of the UE when the network responds to the ACTIVATE SECONDARY PDP CONTEXT
REQUEST message with a negotiated LLC SAPI which is not supported by the UE.
Reference
3GPP TS 24.008, clause 6.1.3.2.1.
11.1.4.1.2.3.4 Method of test
Initial conditions
System Simulator:
User Equipment:
- User setting of LLC SAPI supported yes/no
- Method of setting LLC SAPI
Test procedure
The requested LLC SAPI is set. This is the only LLC SAPI supported by the UE. A PDP context activation is requested
by the user and accepted by the SS. A secondary PDP context activation is requested by the user. On receipt of the
ACTIVATE SECONDARY PDP CONTEXT REQUEST message an ACTIVATE SECONDARY PDP CONTEXT
ACCEPT message is returned by the SS with the LLC SAPI not supported by the UE. The UE shall then send a
DEACTIVATE PDP CONTEXT REQUEST message for the secondary PDP context. A DEACTIVATE PDP
CONTEXT ACCEPT message will be sent in return by the SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1941
Expected sequence
UE SS
REQUEST
ACCEPT
CONTEXT REQUEST
activation
CONTEXT ACCEPT
Accept the Secondary PDP context
activation with LLC SAPI not supported by
the UE
7 DEACTIVATE PDP CONTEXT
REQUEST
Request deactivation of all PDP contexts
ACCEPT
Accept the PDP context deactivation

In step 3 Negotiated LLC SAPI IE is equal to Requested LLC SAPI IE in step 2 and step 5.
In step 7 SM cause IE shall have value #25: LLC or SNDCP failure. Also, Tear down indicator IE shall be included in
the DEACTIVATE PDP CONTEXT REQUEST message to deactivate all PDP contexts for this PDP address.
11.1.4.2 Unsuccessful Secondary PDP Context Activation Procedure Initiated by the
UE
Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network may reject the UE
initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJ ECT message to the
UE. Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJ ECT message, the UE shall stop timer T3380
and enter the state PDP-INACTIVE.
Reference
To test the behaviour of the UE when network rejects the UE initiated Secondary PDP context activation.
Initial conditions
System Simulator:
User Equipment:
The UE and is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1942
Test procedure
A PDP context activation is requested by the user and accepted by the SS. Secondary context activation is requested by
the user. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message from the UE, an
ACTIVATE SECONDARY PDP CONTEXT REJ ECT with cause #43 'unknown PDP context' is returned by the SS.
SS shall wait for T3380 seconds to ensure that the UE sends no more ACTIVATE SECONDARY PDP CONTEXT
REQUEST messages.
Expected sequence
UE SS
REQUEST
ACCEPT
CONTEXT REQUEST
activation
CONTEXT REJ ECT
SS rejects the Secondary PDP context
activation with cause '#43: unknown PDP
context'
UE

Step 5. The Linked TI information element specifies the TI which is different from the TI in the PDP context activated
in steps 1-3.
After a secondary PDP context activation being rejected by the network, the UE shall not re-send the ACTIVATE
SECONDARY PDP CONTEXT REQUEST message.
11.1.4.3 Abnormal cases
11.1.4.3.1 T3380 Expiry
1) On the first expiry of the timer T3380, the UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT
REQUEST.
2) On the second expiry of the timer T3380, the UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT
REQUEST.
3) On the third expiry of the timer T3380, the UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT
REQUEST.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1943
4) On the fourth expiry of the timer T3380, the UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT
REQUEST.
5) On the fifth expiry of the timer T3380, the UE shall release all resources possibly allocated for this invocation
and shall abort the procedure; no automatic secondary PDP context activation re-attempt shall be performed.
Reference
3GPP TS 24.008 clause 6.1.3.2.3 a).
To test the behaviour of the UE when the SS does not reply to ACTIVATE SECONDARY PDP CONTEXT REQUEST
message.
Initial conditions
System Simulator:
User Equipment:
- Method of activating a context
Test procedure
A PDP context is activated by the user and accepted by the SS. Secondary PDP context activation is requested by the
user. The UE shall send ACTIVATE SECONDARY PDP CONTEXT REQUEST message five times with T3380
seconds between each message. After this, no further ACTIVATE SECONDARY PDP CONTEXT REQUEST
messages shall be sent by the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1944
Expected sequence
UE SS
REQUEST
ACCEPT
CONTEXT REQUEST
activation
6 SS T3380 seconds
CONTEXT REQUEST
Request the Secondary PDP context
activation
8 SS T3380 seconds
CONTEXT REQUEST
activation
10 SS T3380 seconds
CONTEXT REQUEST
activation
12 SS T3380 seconds
CONTEXT REQUEST
activation
ACTIVATE SECONDARY PDP CONTEXT
REQUEST messages are sent by the UE

None.
UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST to SS five times in order to initiate a
Secondary PDP context, with expiry of timer T3380 between messages. After fifth try, UE shall send no more
ACTIVATE SECONDARY PDP CONTEXT REQUEST messages to SS.
11.2 PDP context modification procedure
11.2.1 Network initiated PDP context modification
11.2.1.1 Definition

In order to initiate the procedure, the network sends the MODIFY PDP CONTEXT REQUEST message to the UE and
starts timer T3386. The message shall contain the new QoS and the radio priority level and LLC SAPI that shall be used
by the UE in GSM at the lower layers for the transmission of data related to the PDP context.
Upon receipt of this message the UE shall reply with the MODIFY PDP CONTEXT ACCEPT message, if the UE
accepts the new QoS and the indicated LLC SAPI.
If the UE does not accept the new QoS or the indicated LLC SAPI, the UE shall initiate the PDP context deactivation
procedure for the PDP context - the reject cause IE value of the DEACTIVATE PDP CONTEXT REQUEST message
shall indicate "QoS not accepted".
The network shall upon receipt of the MODIFY PDP CONTEXT ACCEPT message stop timer T3386.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1945
In UMTS, the network shall establish, reconfigure or continue using the Radio Access Bearer with the new QoS
indicated in the MODIFY PDP CONTEXT REQUEST message.
Reference
To test behaviour of the UE upon receipt of a MODIFY PDP CONTEXT REQUEST message from SS.
Initial conditions
System Simulator:
User Equipment:
- Method of activating a PDP context
- Support of automatic PS attach procedure at switch on yes/no
Test procedure
The requested QoS is set. A PDP context is activated by the user and accepted by the SS. A MODIFY PDP CONTEXT
REQUEST message is then sent to the UE with a new QoS . The UE shall either send a DEACTIVATE PDP
CONTEXT REQUEST (UE behaviour A) or MODIFY PDP CONTEXT ACCEPT (UE behaviour B) message in
return.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1946
Expected sequence
UE SS
REQUEST
Activate the PDP context
2a SS SS establishes RAB
ACCEPT
DIRECTION)
Request the modification of a PDP context,
with a new QoS and start timer T3386.
A5 DEACTIVATE PDP CONTEXT
REQUEST
UE behaviour type A: Initiate the PDP
context deactivation. Cause set to 'QoS not
accepted'
A5a DEACTIVATE PDP CONTEXT
ACCEPT
UE behaviour type A: Accept the PDP
context deactivation and stop timer T3386.
A5b SS The SS releases the RAB associated with
this PDP Context.
A5c DETACH REQUEST UE behaviour type A: A non-auto attach UE
may (optionally) send a Detach Request.
The SS shall wait up to 'T3390' seconds for
the Detach Request.
A5d DETACH ACCEPT If the UE transmitted a Detach Request
message in step A5c then the SS responds
with a Detach Accept message.
B5 MODIFY PDP CONTEXT
DIRECTION)
UE behaviour type B: Accept the PDP
context modification
B5a SS Stop timer T3386
6 Void
7 Void
8 Void

None.
The UE shall:
- Accept or reject PDP context modification with a new QoS initiated by the SS .
11.2.2 UE initiated PDP context modification
11.2.2.1 UE initiated PDP Context Modification accepted by network
This test can only be performed if minimum QoS can be set by the user.
In order to initiate the procedure, the UE sends the MODIFY PDP CONTEXT REQUEST message to the network,
enters the state PDP-MODIFY-PENDING and starts timer T3381. The message may contain the requested new QoS
and/or the TFT and the requested LLC SAPI (used in GSM).
Upon receipt of the MODIFY PDP CONTEXT REQUEST message, the network may reply with the MODIFY PDP
CONTEXT ACCEPT message in order to accept the context modification. The reply message may contain the
negotiated QoS and the radio priority level based on the new QoS profile and the negotiated LLC SAPI, that shall be
used in GSM by the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1947
Upon receipt of the MODIFY PDP CONTEXT ACCEPT message, the UE shall stop the timer T3381. If the offered
QoS parameters received from the network differs from the QoS requested by the UE, the UE shall either accept the
negotiated QoS or initiate the PDP context deactivation procedure.
Reference
To test the behaviour of the UE upon receipt of a MODIFY PDP CONTEXT ACCEPT message from the SS with
- Requested QoS;
Initial conditions
System Simulator:
User Equipment:
- User setting of Minimum QoS supported yes/no
- Method of setting minimum QoS
Test procedure
The requested QoS and Minimum QoS are set. A PDP context is activated by the user and accepted by the SS. The UE
initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message with new QoS. The
SS accepts the context modification and replies with the MODIFY PDP CONTEXT ACCEPT message with the QoS
requested. The SS waits T3390 seconds to confirm that UE will not initiate a PDP context deactivation.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1948
Expected sequence
UE SS
REQUEST
ACCEPT
REQUEST (UE TO NETWORK
DIRECTION)
Request the modification of a PDP context,
with new QoS
ACCEPT (NETWORK TO UE
DIRECTION)
Accept the PDP context modification with
QoS requested
6 SS SS waits T3390 seconds to confirm UE
does not initiate PDP context deactivation.
7 Void
8 Void
9 Void
10 Void
11 Void

None.
When requesting the PDP context modification, the UE shall:
- Modify the PDP context if SS replied with the requested QoS;

11.2.2.2 UE initiated PDP Context Modification not accepted by the network
In order to initiate the procedure, the UE sends the MODIFY PDP CONTEXT REQUEST message to the network,
enters the state PDP-MODIFY-PENDING and starts timer T3381. The message may contain the requested new QoS
and/or the TFT and the requested LLC SAPI (used in GSM).
Upon receipt of a MODIFY PDP CONTEXT REQUEST message, the network may reject the UE initiated PDP context
modification request by sending a MODIFY PDP CONTEXT REJ ECT message to the UE. The message shall contain a
cause code that typically indicates one of the following:
#26: insufficient resources;
#32: Service option not supported;
#41: semantic error in the TFT operation;
#42: syntactical error in the TFT operation;
#44: semantic errors in packet filter(s);
#45: syntactical errors in packet filter(s);
#95 - 111: protocol errors.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1949
Upon receipt of a MODIFY PDP CONTEXT REJ ECT message, the UE shall stop timer T3381 and enter the state PDP-
ACTIVE.
Reference
3GPP TS 24.008 clauses 6.1.3.3, 6.1.3.3.2 and 6.1.3.3.3.
To test the behaviour of the UE upon receipt of a MODIFY PDP CONTEXT REJ ECT message from the network.
Initial conditions
System Simulator:
User Equipment:
Test procedure
A PDP context is activated by the user and accepted by the SS. The UE initiates a PDP context modification by sending
a MODIFY PDP CONTEXT REQUEST message. The SS rejects the context modification and replies with the
MODIFY PDP CONTEXT REJ ECT with cause set to #26: insufficient resources.
Expected sequence
UE SS
REQUEST message is set to either
Originating Streaming Call, Originating
Interactive Call or Originating Background
Call
1b SERVICE REQUEST
1c SS The SS starts ciphering and integrity
protection.
REQUEST
2a SS The SS establishes the RAB
ACCEPT
DIRECTION)
Request the modification of a PDP context
5 MODIFY PDP CONTEXT REJ ECT SS rejects PDP context modification,
SM cause= #26
MODIFY PDP CONTEXT REQUEST (UE
TO NETWORK DIRECTION) messages are
sent by the UE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1950
None.
After receiving MODIFY PDP CONTEXT REJ ECT message from the netwok, UE shall not resend PDP context
modification request.
11.2.3 Abnormal cases
11.2.3.1 T3381 Expiry
On the first expiry of timer T3381, the UE shall re-send the MODIFY PDP CONTEXT REQUEST message, reset and
restart timer T3381. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3381, the UE may
continue to use the previously negotiated QoS or it may initiate the PDP context deactivation procedure.
Reference
3GPP TS 24.008 clause 6.1.3.3.4 a) case: In the UE.
To test the behaviour of the UE when SS does not reply to MODIFY PDP CONTEXT REQUEST message.
Initial conditions
System Simulator:
User Equipment:
Test procedure
A PDP context activation is requested by the user and accepted by the SS. The UE shall send MODIFY PDP
CONTEXT REQUEST (UE TO NETWORK DIRECTION) message five times with T3381 seconds between each
message. After this no further MODIFY PDP CONTEXT REQUEST (UE TO NETWORK DIRECTION) messages
shall be sent by the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1951
Expected sequence
UE SS
Call
1b SERVICE REQUEST
protection.
REQUEST
2a SS The SS establishes the RAB
ACCEPT
DIRECTION)
Request modification of the PDP context,
with new QoS
5 SS T3381 seconds
DIRECTION)
with the same QoS as in step 4
7 SS T3381 seconds
DIRECTION)
9 SS T3381 seconds
DIRECTION)
11 SS T3381 seconds
DIRECTION)
MODIFY PDP CONTEXT REQUEST (UE
TO NETWORK DIRECTION) messages are
sent by the UE

None.
UE shall re-send the MODIFY PDP CONTEXT REQUEST (UE TO NETWORK DIRECTION) to SS five times in
order to initiate the PDP context modification, with expiry of timer T3381 between messages. After fifth try, UE shall
send no more MODIFY PDP CONTEXT REQUEST (UE TO NETWORK DIRECTION) messages to SS.
11.2.3.2 Collision of UE and network initiated PDP context modification procedures
A collision of a UE and network initiated PDP context modification procedures is identified by the UE if a MODIFY
PDP CONTEXT REQUEST message is received from the network after the UE has sent a MODIFY PDP CONTEXT
REQUEST message itself, and both messages contain the same TI and the UE has not yet received a MODIFY PDP
CONTEXT ACCEPT message from the network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1952
In the case of such a collision, the network initiated PDP context modification shall take precedence over the UE
initiated PDP context modification. The UE shall terminate internally the UE initiated PDP context modification
procedure, enter the state PDP-ACTIVE and proceed with the network initiated PDP context modification procedure by
sending a MODIFY PDP CONTEXT ACCEPT message.
Reference
3GPP TS 24.008 clause 6.1.3.3.4 b).
To test behaviour of the UE when it identifies collision of the UE and SS initiated PDP context modification with the
same TI.
Initial conditions
System Simulator:
User Equipment:
Test procedure
A PDP context is activated by the user and accepted by the SS. The UE initiates a PDP context modification by sending
a MODIFY PDP CONTEXT REQUEST message. Then the SS initiates the PDP context modification by sending
MODIFY PDP CONTEXT REQUEST message with the same TI. The UE shall reply to the SS initiated PDP context
modification procedure by sending MODIFY PDP CONTEXT ACCEPT message with the same TI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1953
Expected sequence
UE SS
Originating Conversational Call, Originating
Streaming Call, Originating Interactive Call,
Originating Background Call or Originating
High Priority Signalling
1b SERVICE REQUEST
protection.
REQUEST
ACCEPT
DIRECTION)
Request modification of the PDP context
DIRECTION)
Request modification of the PDP context
with the same TI
6 UE UE identifies collision, terminates internally
the UE initiated PDP context modification
procedure
DIRECTION)
Accept SS initiated PDP context
modification

Steps 2, 4 and 7. TI flag (bit 8) in the TI IE is set to 0 (transaction initiated by the UE).
Steps 3 and 5. TI flag (bit 8) in the TI IE is set to 1.
Steps 2, 3, 4, 5 and 7. The value of the TIO (bits 5-7) in the TI IE is the same in these test steps.
In step 6, the UE shall terminate internally the UE initiated PDP context modification procedure and proceed with SS
initiated PDP context modification.
11.3 PDP context deactivation procedures
11.3.1 PDP context deactivation initiated by the UE
11.3.1.1 Definition
In order to deactivate a PDP context, the UE sends a DEACTIVATE PDP CONTEXT REQUEST message to the
network, enters the state PDP-INACTIVE-PENDING and starts timer T3390. The message contains the transaction
identifier (TI) in use for the PDP context to be deactivated and a cause code that typically indicates one of the following
causes:
- #26: insufficient resources;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1954
- #36: regular PDP context deactivation; or
- #37: QoS not accepted.
The network shall reply with the DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the
DEACTIVATE PDP CONTEXT ACCEPT message, the UE shall stop timer T3390. In UMTS, the network shall
initiate the release of Radio Access Bearer associated with this PDP context.
Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS is
received by the UE specifying a transaction identifier which is not recognised as relating to an active context or to a
context that is in the process of activation or deactivation, the UE shall send a SM-STATUS message with cause #81
"invalid transaction identifier value" using the received transaction identifier value including the extension octet and
remain in the PDP-INACTIVE state.
Reference
3GPP TS 24.008 clauses 6.1.3.4.1 and 8.3.2 (b).
To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT ACCEPT message from the SS in
PDP context deactivation procedure initiated by the UE.
To test the behaviour of the UE upon receipt of a session management message (except REQUEST PDP CONTEXT
ACTIVATION or SM-STATUS) specifying a transaction identifier which is not recognised as relating to an active
context or to a context that is in the process of activation or deactivation.
Initial conditions
System Simulator:
User Equipment:
- Method of deactivating the PDP context
Test procedure
A PDP context is activated by the user and accepted by the SS. PDP context deactivation is then requested by the user.
The UE shall send a DEACTIVATE PDP CONTEXT REQUEST message to the SS. The SS shall then reply with a
DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then wait for T3390 seconds to ensure T3390 has
been stopped and that no further messages are sent from the UE. The UE in manual mode may perform a detach
procedure. The SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context and if the UE
has not performed a detach procedure it shall reply with an SM STATUS message with cause #81 'transaction identifier
not known'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1955
Expected sequence
UE SS
1 UE Initiate a context activation with traffic class
"originatingInteractiveCall" or
"originatingBackgroundCall".
Call
1b SERVICE REQUEST
protection.
REQUEST
ACCEPT
4 UE Initiate a context deactivation
REQUEST
Request a deactivation of a PDP context
and starts waiting for 'T3390'. SM cause set
to #36.
ACCEPT
SS accepts the PDP context deactivation
and timer T3390 is canceled.
6a SS The SS releases the RAB associated with
this PDP Context.
7 DETACH REQUEST The UE may (optionally) send a Detach
Request (only Note 1). The SS shall wait up
to 'T3390' seconds for the Detach Request.
If the SS receives a Detach Request the test
execution continues from step A8, otherwise
from step B8. SS shall check that no further
deactivate request messages are sent
during this time.
A8 MODIFY PDP CONTEXT
DIRECTION)
Send a modify request to UE for the
deactivated context.
A9 SS Start timer 'T3386' and wait until is expires
to ensure that UE does not respond to
Modify PDP Context Request(Net) after
Detach Request has been sent from UE.
A10 DETACH ACCEPT SS responds with DETACH ACCEPT
message as a Detach Request was
transmitted by the UE
DIRECTION)
deactivated context. (Allowed for Note 1 and
Note 2).
B9 SM STATUS Cause set to #81
Note 1: Support of automatic PS attach procedure at switch on no
Note 2: Support of automatic PS attach procedure at switch on yes

Steps 2 and 5: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 6, A8 and B8: TI flag in TI IE is set to 1.
Steps 2, 3, 5, 6, A8 and B8: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test
steps.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1956
At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of
the following causes:
- Originating Streaming Call;
- Originating Interactive Call or
- Originating Background Call
In PDP context deactivation procedure initiated by the UE, upon receipt of a DEACTIVATE PDP CONTEXT
ACCEPT message from the SS, the UE shall deactivate PDP context associated with given PDP address and TI.
If the UE has not performed a detach procedure then, upon modification procedure initiated by the network, for
deactivated PDP context, the UE shall reply with SM STATUS message with cause #81.
11.3.2 PDP context deactivation initiated by the network
11.3.2.1 Definition
In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the
UE and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated
and a cause code that typically indicates one of the following causes:
#36: regular PDP context deactivation;
#38: network failure; or
#39: reactivation requested.
The UE shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message. Upon
receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395. In UMTS,
the network shall initiate the release of Radio Access Bearer associated with this PDP context.
Reference
3GPP TS 24.008 clause 6.1.3.4.2.
To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the SS.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1957
Test procedure
A PDP context is activated by the user and accepted by the SS. A DEACTIVATE PDP CONTEXT REQUEST message
is then sent by the SS. The UE shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall
then wait for T3395 seconds to ensure that no further messages are sent from the UE. The UE in manual mode may
perform a detach procedure. The SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context
and if the UE has not performed a detach procedure it shall reply with an SM STATUS message with cause #81
'invalid transaction identifier value'.
Expected sequence
UE SS
1 UE Initiate a context activation with traffic class
"originatingInteractiveCall" or
"originatingBackgroundCall".
Call
1b SERVICE REQUEST
protection.
REQUEST
ACCEPT
REQUEST
and starts waiting for 'T3395'. SM cause set
to #36.
ACCEPT
Accept the PDP context deactivation and
timer T3395 is canceled.
5a SS The SS releases the RAB associated with
this PDP Context.
5b DETACH REQUEST The UE may (optionally) send a Detach
Request (only Note 1). The SS shall wait up
to 'T3395' seconds for the Detach Request.
If the SS receives a Detach Request the test
execution continues from step A6, otherwise
from step B6. SS shall check that no further
deactivate request messages are sent
during this time.
A6 MODIFY PDP CONTEXT
DIRECTION)
deactivated context.
A7 SS Start timer 'T3386' and wait until is expires
to ensure that UE does not respond to
Modify PDP Context Request(Net) after
Detach Request has been sent from UE.
A8 DETACH ACCEPT SS responds with DETACH ACCEPT
message as a Detach Request was
transmitted by the UE
DIRECTION)
deactivated context. (Allowed for Note 1 and
Note 2).
B7 SM STATUS Cause set to #81
Note 1: Support of automatic PS attach procedure at switch on no
Note 2: Support of automatic PS attach procedure at switch on yes

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1958
Steps 2 and 5: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 4, A6 and B6: TI flag in TI IE is set to 1.
Steps 2, 3, 4, 5, A6 and B6: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test
steps.
At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of
the following causes:
- Originating Streaming Call;
- Originating Interactive Call or
- Originating Background Call
Upon receipt of a request for deactivation of a PDP context from the SS, the UE shall deactivate PDP context.
If the UE has not performed a detach procedure then, upon modification procedure initiated by the network, for
deactivated PDP context, UE shall reply with SM STATUS message with cause #81, as confirmation that previously SS
requested PDP context deactivation was performed by the UE.
11.3.3 Abnormal cases
11.3.3.1 T3390 Expiry
Expiry of timers
In the UE:
On the first expiry of timer T3390, the UE shall resent the message DEACTIVATE PDP CONTEXT
REQUEST and shall reset and restart the timer T3390. This retransmission is repeated four times, i.e. on the
fifth expiry of timer T3390, the UE shall release all resources allocated and shall erase the PDP context
related data.
Reference
3GPP TS 24.008 clause 6.1.3.4.3 a), case In the UE.
To test the behaviour of the UE when the SS does not reply to a DEACTIVATE PDP CONTEXT REQUEST message
from the UE.
Initial conditions
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1959
- Method of deactivating a PDP context
Test procedure
A PDP context is activated by the user and accepted by the SS. PDP context deactivation is then requested by the user.
The UE shall send a DEACTIVATE PDP CONTEXT REQUEST message five times with T3390 seconds between
each message. T3390 seconds after the fifth message the SS shall send a MODIFY PDP CONTEXT REQUEST
message for the deactivated context and the UE shall reply with SM STATUS with cause set to #81 'Transaction
identifier not known'.
Expected sequence
UE SS
Call
1b SERVICE REQUEST
protection.
REQUEST
ACCEPT
REQUEST
6 SS T3390 seconds
REQUEST
8 SS T3390 seconds
REQUEST
10 SS T3390 seconds
REQUEST
12 SS T3390 seconds
REQUEST
14 SS Wait T3390 seconds
DIRECTION)
Try to modify the deactivated context.
16 SM STATUS Cause set to #81

Steps 2, 5, 7, 9, 11 and 13: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, and 15: TI flag in TI IE is set to 1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1960
Steps 2, 3, 5, 7, 9, 11, 13, and 15: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these
test steps.
If SS does not respond to UE initiated PDP context deactivation procedure, the UE shall retransmit a DEACTIVATE
PDP CONTEXT REQUEST five times, with T3390 timer expiry between the successive messages, before releasing
resources allocated to the PDP context and deleting PDP context related data.
11.3.3.2 Collision of UE and network initiated PDP context deactivation requests
If the UE and the network initiated PDP context deactivation requests collide, the UE and the network shall each reply
with the message DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively.
Reference
3GPP TS 24.008 clause 6.1.3.4.3 b).
To test the behaviour of the UE when there is a collision between an UE initiated and network initiated context
deactivation.
Initial conditions
System Simulator:
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN
- Method of deactivating a PDP context
Test procedure
A PDP context is activated by the user and accepted by the SS. Context deactivation is then requested by the user. Upon
receipt of the DEACTIVATE PDP CONTEXT REQUEST message the SS sends a DEACTIVATE PDP CONTEXT
REQUEST message. The UE shall reply with only one DEACTIVATE PDP CONTEXT ACCEPT message. Upon
receipt of this message the SS sends a DEACTIVATE PDP CONTEXT ACCEPT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1961
Expected sequence
UE SS
Call
1b SERVICE REQUEST
protection.
REQUEST
2a SS SS establishes the RAB
ACCEPT
REQUEST
UE requests deactivation of a PDP context
REQUEST
SS requests deactivation of a PDP context
and starts T3390 and T3395
ACCEPT
UE accepts the PDP context deactivation
requested by the SS
7a SS SS stops T3395
ACCEPT
SS accepts the PDP context deactivation
requested by the UE
9 SS SS releases the RAB
10 SS SS waits for expiry of T3390 to ensure no
further deactivate request messages are
sent

Steps 2 and 5. TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 6 and 8. TI flag in TI IE is set to 1.
Steps 2, 3, 5, 6, 7 and 8. The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test steps.
When UE and SS initiated PDP context deactivation requests collide, the UE shall reply with DEACTIVATE PDP
CONTEXT ACCEPT to the SS.
11.4 Unknown or Unforeseen Transaction Identifier/Non-
semantical Mandatory Information Element Errors
11.4.1 Error cases
11.4.1.1 Definition
The mobile station shall ignore a session management message with TI EXT bit =0. Otherwise, the following
procedures shall apply:
- Whenever any session management message, except REQUEST PDP CONTEXT ACTIVATION or SM-
STATUS, is received by the UE specifying a transaction identifier which is not recognized as relating to an
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1962
active context or to a context that is in the process of activation or deactivation, the UE shall send a SM-
STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier
value including the extension octet and remain in the PDP-INACTIVE state.
- When REQUEST PDP CONTEXT ACTIVATION message is received with a transaction identifier flag set to
"1", this message shall be ignored.
When on receipt of a message,
- an "imperative message part" error; or
- a "missing mandatory IE " error.
is diagnosed or when a message containing:
- a syntactically incorrect mandatory IE; or
- an IE unknown in the message, but encoded as "comprehension required"; or
- an out of sequence IE encoded as "comprehension required".
is received, the UE shall proceed as follows:
- If the message was a SM message, except DEACTIVATE PDP CONTEXT REQUEST and REQUEST PDP
CONTEXT ACTIVATION, the SM-STATUS message with cause #96 "invalid mandatory information" shall
be returned.
a) If the message is a DEACTIVATE PDP CONTEXT REQUEST, a DEACTIVATE PDP CONTEXT
ACCEPT message shall be returned. All resources allocated for that context shall be released.
b) If the message is a REQUEST PDP CONTEXT ACTIVATION, a REQUEST PDP CONTEXT REJ ECT
message with cause #96 "Invalid mandatory information" shall be returned.
- If a mobile station receives a GMM message or SM message with message type not defined for the PD or not
implemented by the receiver, it shall return a status message (GMM STATUS or SM STATUS depending on the
protocol discriminator) with cause #97 'message type non-existent or not implemented'.
- If the mobile station receives a message not compatible with the protocol state, the mobile station shall ignore
the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, MM
STATUS depending on the protocol discriminator) with cause #98 "Message type not compatible with protocol
state". When the message was a GMM message the GMM-STATUS message with cause #98 "Message type not
compatible with protocol state" shall be returned. When the message was a SM message the SM-STATUS
message with cause #98 'Message type not compatible with protocol state' shall be returned.
Other syntactic errors.
This clause applies to the analysis of the value part of an information element. It defines the following terminology:
- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as 'reserved', or
if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical
error that a type 4 standard IE specifies in its length indicator a greater length than possible according to the
value part specification: extra bits are ignored.
Reference
3GPP TS 24.008 clauses 8.3.2, 8.4 and 8.5.
3GPP TS 24.007 clause 11.4.2.
To test the behaviour of the UE when messages with unknown or unforeseen transaction identifiers or non-semantical
mandatory information element errors occur.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1963
Initial conditions
System Simulator:
User Equipment:
- PS supported yes/no
Test procedure
A PDP context activation is requested by the SS with the transaction identifier set to '1'. The UE shall not respond to
this request.
A PDP context is then activated from the UE. An invalid accept messages is sent by the SS. The UE replies with SM
STATUS message. After T3380 seconds UE sends second autogenerated ACTIVATE PDP CONTEXT REQUEST
message. SS again replies with invalid ACTIVATE PDP CONTEXT ACCEPT and UE returns SM STATUS message.
After further T3380 seconds UE sends third autogenerated ACTIVATE PDP CONTEXT REQUEST message. SS
replies with unknown message and UE returns SM STATUS with cause #97 'message type non-existent or not
implemented'. After T3380 seconds the UE sends next autogenerated ACTIVATE PDP CONTEXT REQUEST
message, SS repies with MODIFY PDP CONTEXT REQUEST and UE returns SM STATUS with cause #98 'message
type not compatible with protocol state'. After T3380 seconds the UE sendes last autogenerated ACTIVATE PDP
CONTEXT REQUEST message. SS replies with valid accept message.
A deactivate message is then sent from the SS with a different transaction identifier to the one used in the activate
request message sent by the UE. The UE shall reply with a SM STATUS message with cause #81 'invalid transaction
identifier value'.
Two invalid modification messages are then sent to the UE in turn. The UE shall respond each time with a SM-
STATUS message with cause #96 "invalid mandatory information".
Last MODIFY PDP CONTEXT message sent from SS has TI EXT bit =0. The UE does not respond to this message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1964
Expected sequence
UE SS
ACTIVATION
Request the activation of a PDP context
with the transaction identifier flag set to "1"
2 SS Wait T3385 seconds to ensure UE does not
request context activation
3 UE Initiate a context request
REQUEST
Activate a PDP context from the UE
ACCEPT
Unknown IE encoded as 'comprehension
required'
REQUEST
Activate a PDP context from the UE (auto-
generated)
ACCEPT
Out of sequence IE encoded as
'comprehension required'
REQUEST
generated)
13 UNKNOWN MESSAGE Message with unknown message type
REQUEST
generated)
REQUEST
Request modification of PDP context
REQUEST
generated)
ACCEPT
REQUEST
Try to deactivate the context with a different
transaction identifier to that used to activate
the context
REQUEST(NETWORK TO UE
DIRECTION)
Request the modification of the PDP context
('New QoS' mandatory IE missing in the
message)
DIRECTION)
(with 'Requested LLC SAPI' set to reserved
value '1100')
DIRECTION)
(TI EXT bit =0)
29 SS Wait T3386 seconds to ensure UE does not
respond

TBD.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1965
12 Elementary procedure for Packet Switched Mobility
Management
12.1 Applicability, default conditions and default messages
All test cases for PS mobility management apply for all PS mobiles unless otherwise stated in a specific test. Within
each test case, the ICS statement indicates whether the test shall be performed for mobiles that can only operate in mode
- class A, only in mode - class C , or in both mode - class A and C. For some procedures, the mobile class is of no
importance.
Note that only the layer 3 messages are described in the document. The mapping of the layer 3 messages to lower layers
and the use of logical channels is not described in the present document.
The terms 'PS/CS mode of operation' and 'PS mode of operation' are not used in the present document with some
exceptions. Instead the terms 'UE operation mode A' and 'UE operation mode C' are used.
The default conditions and default message contents not specified in this clause must be set as in "PS default
conditions"
Below is a list of the RAI values and the corresponding RAC, LAC and MCC used in the test cases:
RAI-1: MCC1/MNC1/LAC1/RAC1 (Used if only one cell)
RAI-2: MCC2/MNC1/LAC1/RAC1
RAI10: MCC1/MNC2/LAC1/RAC2
If the User Equipment initial condition specifies that the mobile has a valid IMSI but the initial condition does not
mention P-TMSI, than that shall be interpreted as that the mobile has no valid P-TMSI.
The tests are based on 3GPP TS 24.008.
12.2 PS attach procedure
This procedure is used to indicate for the network that the IMSI is available for traffic by establishment of a GMM
context.
12.2.1 Normal PS attach
The normal PS attach procedure is a GMM procedure used by PS UEs of UE operation mode A or C to IMSI attach for
PS services only.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1966
12.2.1.1 PS attach / accepted
1) If the network accepts the PS attach procedure (signalled by an IMSI) and allocates a P-TMSI, the UE shall
acknowledge the P-TMSI and continue communication with the P-TMSI.
2) If the network accepts the PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI, the UE
shall acknowledge the new P-TMSI and continue communication with the new P-TMSI.
3) If the network accepts the PS attach procedure (signalled by a P-TMSI) from the UE without reallocation of the
old P-TMSI, the UE shall continue communication with the old P-TMSI.
Reference
3GPP TS 24.008 clause 4.7.3.1
To test the behaviour of the UE if the network accepts the PS attach procedure.
The following cases are identified:
1) P-TMSI / P-TMSI signature is allocated;
2) P-TMSI / P-TMSI signature is reallocated;
3) Old P-TMSI / P-TMSI signature is not changed.
Initial condition
System Simulator:
One cell operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (to
prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A).
User Equipment:
The UE has a valid IMSI.
The UE has been registered in the CS domain.
UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
Test procedure
1) The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns
ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH
COMPLETE message. Further communication UE - SS is performed by the new P-TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1967
2) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS reallocates a new P-TMSI and
returns ATTACH ACCEPT message with the new P-TMSI. The UE acknowledge the P-TMSI by sending
ATTACH COMPLETE message. Further communication UE - SS is performed by the new P-TMSI. The UE
will not answer signalling addressed to the old P-TMSI.
3) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS accepts the P-TMSI and returns
ATTACH ACCEPT message without any P-TMSI. Further communication UE - SS is performed by the old P-
TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1968
Expected Sequence
UE SS
1 UE The UE is set to attach to the PS services only
(see ICS). If this is not supported by the UE,
goto step 26.
2 UE The UE is powered up or switched on and
initiates an attach (see ICS).
2a SS SS checks that the IE "Establishment cause" in
the received RRC CONNECTION REQUEST
message is set to "Registration".
3 -> ATTACH REQUEST Attach type ='PS attach'
Mobile identity =IMSI
3a <- AUTHENTICATION AND
CIPHERING REQUEST

3b -> AUTHENTICATION AND
CIPHERING RESPONSE

4 <- ATTACH ACCEPT Attach result ='PS only attached'
Mobile identity =P-TMSI-2
P-TMSI-2 signature
Routing area identity =RAI-1
5 -> ATTACH COMPLETE
6 <- PAGING TYPE1 Mobile identity =P-TMSI-2
Paging order is for PS services.
Paging cause: Terminating interactive call
message is set to "Terminating interactive call".
7 -> SERVICE REQUEST

Service type ="paging response"
7a SS The SS starts integrity protection and releases
the RRC connection.
8 UE The UE is switched off or power is removed
(see ICS).
any received RRC CONNECTION REQUEST
message is set to " Detach" (message not sent
if power is removed).
9 -> DETACH REQUEST Message not sent if power is removed.
Detach type ='power switched off, PS detach'
9a SS The SS releases the RRC connection. If no
RRC CONNECTION RELEASE COMPLETE
message have been received within 1 second
then the SS shall consider the UE as switched
off.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
14 Void
14b Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1969
UE SS
14c <- PAGING TYPE1 Mobile identity =P-TMSI-1
14d SS SS verifies that the UE transmits an RRC
CONNECTION REQUEST message. SS will
reject this request. The IE "Establishment
cause" is not checked.
16 UE No response from the UE to the request. This is
checked for 10 seconds.
(see ICS).
message is set to "Detach" (message not sent if
power is removed).
off.
CIPHERING REQUEST

CIPHERING RESPONSE

21 <- ATTACH ACCEPT No new mobile identity assigned.
P-TMSI and P-TMSI signature not included.
Attach result ='PS only attached'
Paging cause: Terminating interactive call
22b Void
22c Void
23 -> SERVICE REQUEST Service type ="paging response"
23aa SS The SS starts integrity protection and releases
the RRC connection.
23a Void
23b Void
(see ICS).
message is set to "Detach" (message not sent if
power is removed).
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1970
UE SS
26 UE The UE is set to attach to both the PS and non-
PS services (see ICS) and the test is repeated
from step 2 to step 25a.

None.
At step 2a, 10a and 19a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment
cause set to "Registration".
At step 6a and 22a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set
to "Terminating Interactive Call".
At step 8a, 17a and 24a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment
cause set to "Detach".
At step3, 11 and 20, when the UE is powered up or switched on, UE shall:
- initiate the PS attach procedure with the information elements specified in the above Expected Sequence.
UE shall perform the following actions depending on the Mobile identity in the ATTACH REQUEST message and
on the Mobile identity in the ATTACH ACCEPT message.
Case 1) The Mobile identity in the ATTACH REQUEST message is the IMSI and the Mobile identity in the
ATTACH ACCEPT message is the P-TMSI.
At step5, UE shall:
- acknowledge the P-TMSI by sending the ATTACH COMPLETE message.
Case 2) The Mobile identity in the ATTACH REQUEST message is the P-TMSI and the Mobile identity in the
ATTACH ACCEPT message is the new P-TMSI.
At step13, UE shall:
- acknowledge the new P-TMSI by sending the ATTACH COMPLETE message.
- respond to the paging message for PS domain by sending the SERVICE REQUEST message.
12.2.1.2 PS attach / rejected / IMSI invalid / illegal UE
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'Illegal MS, the User
Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'Illegal MS the User
Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
3) If the network rejects a PS attach procedure from the User Equipment with the cause 'Illegal MS, the User
Equipment shall delete the LAI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1971
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'illegal MS.
Initial condition
System Simulator:
Three cells (not simultaneously activated), cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in
MCC1/MNC1/LAC2/RAC1 (RAI-3), cell C in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All three cells are operating in network operation mode II (in case of UE operation mode A).
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" in all
cells.
User Equipment:
The UE has a valid P-TMSI-1 and RAI-1.
UE operation mode A Yes/No (only if mode C not supported)
Test procedure
The SS rejects a PS attach with the cause value 'Illegal UE'. The SS checks that the UE does not perform PS attach in
the same or another PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1972
Expected Sequence
UE SS
The following messages are sent and shall be
received on cell A.
1 UE The UE is set in UE operation mode C (see
ICS).
The SIB1 IE "CN domain specific NAS
system information", for the CS Domain, is set
to value "00 00" in all cells.
2 SS The SS is set in network operation mode II.
Set the cell type of cell B to the "Non-Suitable
cell".
Set the cell type of cell C to the "Non-Suitable
cell".
(see note)
initiates an attach (see ICS). Cell A is preferred
by the UE.
3a Void
5 <- ATTACH REJ ECT GMM cause ='Illegal MS'.
received on cell B.
6 SS Set the cell type of cell A to the "Non-Suitable
cell".
Set the cell type of cell B to the "Serving cell".
(see note)
7 UE Cell B is preferred by the UE.
8 UE No ATTACH REQUEST sent to the SS
(SS waits 30 seconds).
9 UE The UE initiates an attach by MMI or by AT
command.
received on cell C.
11 SS Set the cell type of cell B to the "Non-Suitable
cell".
(see note)
12 UE Cell C is preferred by the UE.
command.
16 UE If possible (see ICS) switch off is performed.
17 UE The UE is powered up or switched on.
18 UE Registration on CS See TS 34.108
This is applied only for UE in UE operation
mode A.
Parameter mobile identity is IMSI.
19 UE The UE initiates an attach (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1973
P-TMSI-1 signature
(see ICS).
25 SS The SS releases the RRC connection. If no
off.
NOTE: The definitions for "Non-Suitable cell" and "Serving cell" are specified in TS34.108 clause 6.1

None.
At step4, when the UE is powered up or switched on, UE shall:
At step8, 10, 13 and 15, UE shall:
- not send the ATTACH REQUEST message to SS, even if there is an instruction of attach request from MMI or
from AT command.
12.2.1.3 PS attach / rejected / IMSI invalid / PS services not allowed
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'PS services not allowed',
the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is
removed.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'PS services not allowed'
the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PS services
not allowed' (no valid PS-subscription for the IMSI).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1974
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1) and cell B in
MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both cells are operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" in both
cells.
User Equipment:
USIM removal possible without powering down Yes/No
Test procedure
The SS rejects a normal attach with the cause value 'PS services not allowed'. The SS checks that the UE does not
perform PS attach in another PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1975
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
ICS). If UE operation mode C not supported,
goto step 17.
by the UE.
5 <- ATTACH REJ ECT GMM cause ='PS services not allowed'
received on cell B.
cell".
(see note)
7a UE Registration on CS See TS 34.108
mode A.
9 UE If possible (see ICS) USIM removal is
performed. Otherwise if possible (see ICS)
switch off is performed. Otherwise the power is
removed.
10 UE The UE gets the USIM replaced, is powered up
or switched on and initiates an attach (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
off .
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1976
16 Set the cell type of cell A to the "Serving cell".
cell".
(see note)
17 UE The UE is set in UE operation mode A(see ICS)
and the test is repeated from step 3 to step 15.

None.
- initiate the PS attach procedure with information elements specified in the above Expected Sequence.
At step8, UE shall:
- not perform a PS attach procedure.
At step11, after the UE is switched on or a USIM is replaced, UE shall:
- perform the PS attach procedure.
12.2.1.4 PS attach / rejected / PLMN not allowed
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'PLMN not allowed' the
User Equipment shall:
1.1 not perform PS attach when switched on in the same routing area or location area (except for the HPLMN).
1.2 not perform PS attach when in the same PLMN and when that PLMN is not selected manually.
1.3 delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
1.4 store the PLMN in the 'forbidden PLMN' list.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'PLMN not allowed' the
User Equipment shall perform PS attach when a new PLMN is entered.
3) If the network rejects a PS attach procedure from the User Equipment with the cause 'PLMN not allowed' and if
after that the PLMN from which this rejection was received, is manually selected, the User Equipment shall
perform a PS attach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PLMN not
allowed'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1977
12.2.1.4.4.1 Test procedure 1
Initial condition
System Simulator:
Four cells (not simultaneously activated), cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell B in
MCC1/MNC2/LAC1/RAC1 (RAI-8), cell C in MCC1/MNC2/LAC2/RAC1 (RAI-9) and cell D in
All four cells are operating in network operation mode II (in case of UE operation mode A). The PLMN of the
four cells should NOT be that of the UE Home PLMN.
cells.
NB: i) Cell D will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.
User Equipment:
The UE has a valid P-TMSI-1 and RAI-8. UE is Idle Updated on cell A.
Test procedure
The SS rejects a PS attach with the cause value 'PLMN not allowed'. The SS checks that the UE does not perform PS
attach if activated in the same routing area or location area and performs PS attach only when a new PLMN is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1978
Expected Sequence
UE SS
SS The following messages are sent and shall be
received on cell A.
ICS).
cell".
cell".
Set the cell type of cell D to the "Non-Suitable
cell".
(see note)
by the UE.
3a Void
5 <- ATTACH REJ ECT GMM cause ='PLMN not allowed'
6 UE No ATTACH REQUEST sent to SS
received on cell B.
cell".
(see note)
received on cell C.
cell".
(see note)
received on cell D.
15 SS Set the cell type of cell C to the "Non-Suitable
cell".
Set the cell type of cell D to the "Serving cell".
(see note)
16 UE Cell D is preferred by the UE.
mode A.
18 UE The UE initiates an attach automatically, by
MMI or by AT command.
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1979
P-TMSI-1 signature
(see ICS).
off.

Initial condition
System Simurator:
One cell operating in network operation mode II: MCC2/MNC1/LAC1/RAC1 (RAI-2). The PLMN of the cell
should NOT be that of the Mobile Station Home PLMN.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00".
User Equipment:
The UE has a valid P-TMSI-1 and RAI-2. UE is Idle Updated on cell A.
Test procedure
The SS rejects a PS attach with the cause value 'PLMN not allowed'. The subscribers access rights is changed to allow
PS attach. Then the PLMN from which this rejection was received is manually selected and the SS check that a PS
attach is performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1980
Expected Sequence
UE SS
1 UE The UE is set in UE operation mode C or A
(see ICS).
2a Void
4 <- ATTACH REJ ECT GMM cause ='PLMN not allowed'
(SS waits 30 seconds)
6 UE The current PLMN is selected manually.
7 Void
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
off.

None.
Test requirements for test procedure 1
At step4, when the UE is powered on or switched on, UE shall:
At step6, UE shall:
- not perform PS attach procedure.
UE shall perform the following actions depending on the PLMN or the routing area or the location area
Case 1) UE is in the same routing area or location area when the power is switched on,
Case2) UE is in the same PLMN, and this PLMN is not selected manually
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1981
Case3) UE is in a new PLMN.
Test requirements for test procedure 2
At step5, UE shall:
At step9, when the UE is in the new PLMN, and this PLMN is selected manually, UE shall
12.2.1.5a PS attach / rejected / roaming not allowed in this location area
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'roaming not allowed in this
location area' the User Equipment shall:
1.1 not perform PS attach when in the same location area.
1.3 store the LA in the 'forbidden location areas for roaming' list.
1.4 perform PS attach when a new location area is entered.
1.5 Periodically search for its HPLMN.
2) The User Equipment shall reset the list of 'Forbidden location areas for roaming' when switched off or when the
USIM is removed.
3) The UE shall be capable of storing at least 10 entries in the list of 'Forbidden location areas for roaming'.
Reference
3GPP TS 24.008 clause 4.7.3.1.
Test purpose 1
To test that on receipt of a rejection using the 'roaming not allowed in this location area' cause code, the UE ceases
trying to attach on that location area. Successful PS attach procedure is possible in other location areas.
Test purpose 2
To test that if the UE is switched off or the USIM is removed the list of 'forbidden location areas for roaming' is cleared.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1982
Test purpose 3
To test that at least 6 entries can be held in the list of 'forbidden location areas for roaming' (the requirement in 3GPP
TS 24.008 is to store at least 10 entries. This is not fully tested by the third procedure).
Test purpose 4
To test that if a cell of the Home PLMN is available then the UE returns to it in preference to any other available cell.
12.2.1.5a.4.1 Test procedure 1
Initial condition
System Simulator:
Three cells (not simultaneously activated), cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B
in
MCC2/MNC1/LAC2/RAC1 (RAI-6, Not HPLMN) and cell C in MCC2/MNC1/LAC1/RAC2 (RAI-7, Not
HPLMN).
All three cells are operating in network operation mode II.
cells.
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'Roaming not allowed in this area'. A new attempt for a PS attach is not
possible. Successful PS attach / detach procedures are performed in another location area. A new attempt for a PS attach
is performed in the 1
st
location area. This attempt shall not succeed, as the LA is on the forbidden list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1983
Expected Sequence
UE SS
received on cell A.
goto step 19.
cell".
cell".
(see note)
by the UE.
3a Void
3b SS SS checks that the IE Establishment cause in
message is set to Registration.
5 <- ATTACH REJ ECT GMM cause ='Roaming not allowed in this
area'
received on cell B.
cell".
(see note)
mode A.
10a SS SS checks that the IE Establishment cause in
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
14 UE The UE initiates a PS detach (without power
off) by MMI or by AT command .
message is set to Detach.
15 -> DETACH REQUEST Detach type ='normal detach, PS detach'
16 <- DETACH ACCEPT
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1984
received on cell C.
cell".
(see note)
The UE is switched off or power is removed
(see ICS)
20 UE UE is switched off.
cell".
(see note)
22 UE The UE is set in UE operation mode A if
supported (see ICS) and the test is repeated
from step 2 to step 20.

Initial condition
System Simulator:
One cell in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN) operating in network operation mode II.
User Equipment:
Test procedure
The SS rejects a PS attach updating with the cause value 'Roaming not allowed in this area'. The UE is switched off for
10 s and switched on again. The SS check that a PS attach is possible on the cell on which the PS attach had been
rejected.
If USIM removal is possible without switching off: The SS rejects a PS attach with the cause value 'Roaming not
allowed in this area'. The USIM is removed and inserted in the UE. The SS check that a PS attach is possible on the cell
on which the PS attach had been rejected.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1985
Expected Sequence
UE SS
1 UE If UE operation mode C is supported, the UE is
set in UE operation mode C (see ICS). If UE
operation mode C is not supported, the UE is
set in UE operation mode A.
2a Void
area'

8
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
12b Void
off.

Initial condition
System Simulator:
Six cells (not simultaneously activated), cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B in
MCC2/MNC1/LAC2/RAC1 (RAI-3, Not HPLMN), cell C in MCC2/MNC1/LAC3/RAC1 (Not HPLMN), cell D
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1986
in MCC2/MNC1/LAC4/RAC1 (Not HPLMN), cell E in MCC2/MNC1/LAC5/RAC1 (Not HPLMN), cell F in
MCC2/MNC1/LAC6/RAC1 (Not HPLMN).
All six cells are operating in network operation mode II (in case of UE operation mode A).
cells.
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'Roaming not allowed in this area'. This is done for 6 different location
areas. Then the SS checks that the UE does not attempt to perform an attach procedure on the non-allowed location
areas.
Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g. every day at
12am) for roaming. If the list is cleared while the test is being run, it may be necessary to re-run the test.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1987
Expected Sequence
UE SS
received on cell A.
cell".
cell".
cell".
Set the cell type of cell E to the "Non-Suitable
cell".
Set the cell type of cell F to the "Non-Suitable
cell".
(see note)
by the UE.
3a Void
area'
received on cell B.
cell".
(see note)
This is applied only in case of UE operation
mode A.
area'
received on cell C.
cell".
(see note)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1988
UE SS
mode A.
area'
received on cell D.
cell".
(see note)
mode A.
area'
received on cell E.
28 SS Set the cell type of cell D to the "Non-Suitable
cell".
Set the cell type of cell E to the "Serving cell".
(see note)
29 UE Cell E is preferred by the UE.
mode A.
area'
received on cell F.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1989
UE SS
35 SS Set the cell type of cell E to the "Non-Suitable
cell".
Set the cell type of cell F to the "Serving cell".
(see note)
36 UE Cell F is preferred by the UE.
mode A.
area'
received on cell E.
42 SS Set the cell type of cell E to the "Serving cell".
Set the cell type of cell F to the "Non-Suitable
cell".
(see note)
43 SS Cell E is preferred by the UE.
received on cell C.
cell".
(see note)
47 SS Cell C is preferred by the UE.
received on cell A.
cell".
(see note)
51 SS Cell A will be preferred by the UE.

12.2.1.5a.4.4 Test procedure4
Initial condition
System Simulator:
Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (not HPLMN, RAI-2) and cell B in
MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1990
Both cells are operating in network operation mode II (in case of UE operation mode A).
cells.
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'Roaming not allowed in this area A second cell belonging to the
HPLMN is activated. It is checked that the UE returns to its HPLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1991
Expected Sequence
UE SS
received on cell A.
Set the cell type of cell B to the "Suitable
neighbour cell".
(see note)
by the UE.
3a Void
area'
received on cell B.
7 SS Set the cell type of cell A to the "Suitable
neighbour cell".
(see note)
mode A.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
12a -> The SS releases the RRC connection.
(see ICS).
13b Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1992
off.
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause
6.1 "Reference Radio Conditions for signalling test cases only".

None.
Test requirements for Test procedure1
At step6, when the UE receives the ATTACH REJ ECT message with GMM cause ='Roaming not allowed in this area',
UE shall:
- not perform the PS attach procedure.
At step11, when the new location area is entered, UE shall:
- perform the PS attach procedure
At step19, when the rejected location area is entered, UE shall
At step5, after the UE receives the ATTACH REJ ECT message with GMM cause ='Roaming not allowed in this area',
UE shall:
At step9, when the UE is switched off or USIM is replaced, UE shall:

At step6, 13, 20, 27, 34 and 41, after the UE receives the ATTACH REJ ECT message with GMM cause ='Roaming not
allowed in this area', UE shall:
At step11, 18, 25, 32 and 39 , UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1993
At step45, 49 and 53, UE shall:

At step6, when the UE receives the ATTACH REJ ECT message with GMM cause ='Roaming not allowed in this area',
UE shall:
At step10, when a new location area is entered, UE shall:
12.2.1.5b PS attach / rejected / No Suitable Cells In Location Area
(1) If the network rejects a PS attach procedure from the User Equipment with the cause 'No Suitable Cells In
Location Area', the User Equipment shall:
1.3 store the LA in the 'forbidden location areas for roaming' list.
1.5 perform PS attach when a new location area is entered.
Reference
3GPP TS 24.008 clauses 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'No Suitable
Cells In Location Area'.
Initial condition
System Simulator:
Three cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C
in MCC2/MNC1/LAC2/RAC1 (RAI-6)
The PLMN contains Cell C is equivalent to the PLMN that contains Cell A.
cells.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1994
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'No Suitable Cells In Location Area'. The SS checks that the UE shall
search for a suitable cell in a different location area on the equivalent PLMN and shall perform PS attach procedure in
that cell.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1995
Expected Sequence
UE SS
received on cell A.
1 UE The UE is set in UE operation mode A (see
ICS).
Set the cell type of cell B to the "Non-suitable
cell".
Set the cell type of cell C to the "Non-suitable
cell".
(see note)
3 Void
CIPHERING REQUEST

CIPHERING RESPONSE

Equivalent PLMNs =MCC2,MNC1
6 <- DETACH REQUEST Detach type =re-attach required
7 -> DETACH ACCEPT
neighbour cell".
Set the cell type of cell C to the "Suitable
neighbour cell".
(see note)
The SS configures power level of each Cell as
follows.
Cell A >Cell B =Cell C
9 Void
11 <- ATTACH REJ ECT GMM cause ='No Suitable Cells In Location
Area'
12 SS The SS initiates the RRC connection release.
The following message are sent and shall be
received on cell C.
14a SS checks that the IE Establishment cause in
16 <- AUTHENTICATION AND
CIPHERING REQUEST

17 -> AUTHENTICATION AND
CIPHERING RESPONSE

P-TMSI-1 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1996
(see ICS).
off.
NOTE: The definitions for "Suitable neighbour cell", "Non-suitable cell" and "Serving cell" are specified
in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only".

None.
12.2.1.5b.5 Test requirements
At step15, when the UE enters a suitable cell in a different location area on the equivalent PLMN, UE shall:
12.2.1.5c PS attach / rejected / Location area not allowed
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'Location area not allowed'
the User Equipment shall:
1.1 delete any RAI, P-TMSI, P-TMSI signature and PS ciphering key sequence number.
1.2 set the PS update status to GU3 ROAMING NOT ALLOWED.
1.3 reset the attach attempt counter.
1.4 store the LAI in the list of "forbidden location areas for regional provision of service".
1.1 perform a cell selection.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'Location area not allowed'
and if the User Equipment is IMSI attached via MM procedures the User Equipment shall:
2.1 set the update status to U3 ROAMING NOT ALLOWED.
2.2 delete any TMSI, LAI and ciphering key sequence number.
2.3 reset the location update attempt counter.
Reference
3GPP TS 24.008 clause 4.7.3.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1997
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'Location area
not allowed'.
Initial condition
System Simulator:
Three cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell
C in MCC2/MNC1/LAC2/RAC1 (RAI-6).
User Equipment:
The UE has a valid P-TMSI-1, RAI-1.
Test procedure
The SS rejects a PS attach with the cause value 'Location area not allowed'. The SS checks that the UE does not perform
MM IMSI attach while in the same location area and performs PS attach when a new equivalent PLMN is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1998
Expected Sequence
UE SS
received on cell A.
1 UE If UE operation mode A is supported, If UE
operation mode C is supported, the UE is set in
UE operation mode A (see ICS). If UE
operation mode A is not supported, the UE is
set in UE operation mode C.
Set the cell type of cell B to the " Non-suitable
cell ".
Set the cell type of cell C to the " Non-suitable
cell "
(see note)
mode A.

4a -> AUTHENTICATION AND
CIPHERING REQUEST

4b <- AUTHENTICATION AND
CIPHERING RESPONSE

4c SS The SS starts integrity protection

7 -> DETACH ACCEPT
Set the cell type of cell B to the " Suitable
neighbour cell ".
Set the cell type of cell C to the " Suitable
neighbour cell "
(see note)
follows.
Cell A >Cell B >Cell C
9 Void
11 <- ATTACH REJ ECT GMM cause ='Location area not allowed'
12 UE The UE performs cell selection.
received on cell C.
12a UE Registration on CS See TS 34.108.
mode A.
12b UE SS checks that the IE Establishment cause in
message is set to Registration
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
1999
P-TMSI-2 signature
19 UE No MM IMSI attach request sent to SS
(see ICS).
20b UE Detach on CS This is applied only for UE in UE operation
mode A.
off.
in TS34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only".

None.
12.2.1.5c.5 Test requirements
At step4 and 10, when the UE is powered on or switched on, UE shall:
- perform cell selection.
- perform PS attach procedure with Mobile identity =IMSI.
- not perform MM IMSI attach
12.2.1.5d PS attach / rejected / PS services not allowed in this PLMN
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'GPRS services not allowed
in this PLMN' the User Equipment shall:
1.3 store the PLMN identity in the "forbidden PLMNs for PS service" list.
1.4 perform a PLMN selection instead of a cell selection, if the UE is in UE operation mode C.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2000
2) If the UE is in UE operation mode A or B and the network is in network operation mode II the User Equipment
shall:
2.1 be still IMSI attached for CS services in the network..
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PS service not
allowed in this PLMN'.
Initial condition
System Simulator:
Three cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell
C in MCC2/MNC1/LAC1/RAC2 (RAI-7).
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'PS service not allowed in this PLMN'. The SS checks that the UE
performs PS attach with attach type =PS attach when a new equivalent PLMN is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2001
Expected Sequence
UE SS
received on cell A.
ICS).
cell ".
Set the cell type of cell C to the " Non-suitable
cell "
(see note)
by the UE.
mode A.
Mobile identity =TMSI-1
CIPHERING REQUEST

CIPHERING RESPONSE

8 -> DETACH ACCEPT
neighbour cell ".
Set the cell type of cell C to the " Suitable
neighbour cell "
(see note)
11 <- ATTACH REJ ECT GMM cause ='PS service not allowed in this
PLMN'
12 UE The UE performs PLMN selection.
received on cell C.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
19 UE PAGING TYPE1 Mobile identity =TMSI-1
Paging order is for CS services.
20 SS No response from the UE to the request. This is
21 -> RRC CONNECTION REQUEST
22 <- RRC CONNECTION SETUP
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2002
23 -> RRC CONNECTION SETUP
COMPLETE

25 <- RRC CONNECTION RELEASE After sending of this message, the SS waits for
disconnection of the CS signalling link.
26 -> RRC CONNECTION RELEASE
COMPLETE

(see ICS).
Detach type ='power switched off, combined
PS / IMSI detach'
off.

None.
12.2.1.5d.5 Test requirements
- perform PLMN selection.
- perform PS attach procedure with Mobile identity =IMSI to the equivalent cell.
- respond the Paging for CS domain service.
12.2.1.6 PS attach / abnormal cases / access barred due to access class control
1) The UE shall not perform PS attach procedure, but stays in the current serving cell and applies normal cell
reselection process.
2) The User Equipment shall perform the PS attach procedure when:
2.1 Access is granted.
2.2 Cell is changed.
Reference
3GPP TS 24.008 clause 4.7.3.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2003
Test purpose1
To test the behaviour of the UE in case of access class control (access is granted).
Test purpose2
To test the behaviour of the UE in case of access class control (Cell is changed).
12.2.1.6.4.1 Test procedure1
Initial condition
An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. Communication with
User Equipments using access class x is initially indicated to be barred.
System Simulator:
Access class x barred.
User Equipment:
Test procedure
The SS indicates access class x barred. A PS attach procedure is not performed.
The SS indicates that access class x is not barred. A PS attach procedure is performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2004
Expected Sequence
UE SS
1 UE The USIM is programmed with access class x.
goto step 12.
attempts to initiate an attach (see ICS).
4 UE No ATTACH REQUEST sent to SS, as access
class x is barred
5 SS The access class x is not barred anymore.
6 UE The UE initiates a PS attach either
automatically or manually (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
(see ICS).
off.

Initial condition
User Equipments using access class x is indicated to be barred on cell A.
System Simulator:
Two cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) has access class x barred, cell B in
MCC1/MNC1/LAC1/RAC1 (RAI-1) has access class x not barred.
cells.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2005
Test procedure
The SS indicates access class x barred. A PS attach procedure is not performed.
A cell change is performed into a cell where access class x is not barred. A PS attach procedure is performed.
Expected Sequence
UE SS
1 UE The USIM is programmed with access class x.
received on cell A.
neighbour cell".
(see note)
ICS).
attempts to initiate an attach (see ICS).
5 UE No ATTACH REQUEST sent to SS, as access
class x is barred
received on cell B.
neighbour cell".
(see note)
7 UE The UE initiates an attach either automatically
or manually (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2006
None.
At step4, when the UE access class x is barred, UE shall:
At step7, when the UE access class x is granted, UE shall:
initiate the PS attach procedure.
At step8, when the serving cell is changed, UE shall:
- initiate the PS attach procedure.

12.2.1.7 PS attach / abnormal cases / change of routing area
If a cell change into a new routing area occurs before an ATTACH ACCEPT or ATTACH REJ ECT message has been
received, the GPRS attach procedure shall be aborted and re-initiated immediately.
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE in case of procedure collision.
Initial condition
System Simulator:
One cell with MCC1/MNC1/LAC1/RAC1 (RAI-1)
The cell is operating in network operation mode II (in case of UE operation mode A).
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2007
Test procedure
The UE initiates a PS attach procedure. The ATTACH ACCEPT message is delayed from the SS. The UE receive a
new routing area code. The UE shall re-initiate a PS attach procedure in the new routing area.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2008
Expected Sequence
UE SS
received on cell A.
ICS).
(see note)
by the UE.
5 SS No response to the ATTACH REQUEST
message is given by the SS.
6 Void
6a <- UTRAN MOBILITY
INFORMATION
The SS conveys updated CN system
information for the PS domain to the UE in
connected mode, including a new routing area
code.
Note: SS transmits the updated system
information with the new RAI information in
SIB1
6b -> UTRAN MOBILITY
INFORMATION CONFIRM

7 UE The UE automatically re-initiates the attach.
CIPHERING REQUEST

CIPHERING RESPONSE

(see ICS).
11a The SS releases the RRC connection. If no
off .

UTRAN MOBILITY INFORMATION (step 6a)
The contents of the UTRAN MOBILITY INFORMATION message in this test case is identical to the default message
in TS 34.108, with the following exceptions.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2009
UE Timers and constants in connected mode Not Present
CN information info
- PLMN identity Not Present
- CN common GSM-MAP NAS system information Not Present
- CN domain specific GSM-MAP NAS system info
- T3212 Infinity
- ATT 0
- RAC RAC-2
- NMO 1 (Network Mode of Operation II)

- initiate the PS attach procedure with information elements specified in the above Expected sequence.
At step8, as the UE has received a new RAI in the UTRAN MOBILITY INFORMATION message before the
ATTACH ACCEPT message or the ATTACH REJ ECT message is received by the UE, the UE shall:
- abort the PS attach procedure and re-initiate the PS attach procedure immediately with new information
elements.

12.2.1.8 PS attach / abnormal cases / power off
When power is switched off before ATTACH ACCEPT message is received by the UE, the UE shall abort the PS attach
procedure and perform a PS detach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2010
Test procedure
The UE is switched off after initiating an attach procedure. A PS detach is automatically performed by the UE before
power is switched off.
Expected Sequence
UE SS
goto step 7.
4 SS No response to the ATTACH REQUEST
message is given by the SS.
5 UE The UE is powered off and initiates a PS detach
(with power off) by
6 -> DETACH REQUEST Detach type ='power switched off, PS detach'
ICS) and the test is repeated from step 2 to
step 6.

None.
At step6, when power is switched off before ATTACH ACCEPT message is received, UE shall:
- abort the PS attach procedure and perform the PS detach procedure.
12.2.1.9 PS attach / abnormal cases / PS detach procedure collision
1) When a DETACH REQUEST message is received by the UE (any cause except re-attach) while waiting for an
ATTACH ACCEPT message, the UE shall terminate the PS attach procedure and continue with the PS detach
procedure.
2) When a DETACH REQUEST message is received by the UE (cause re-attach) while waiting for an ATTACH
ACCEPT message, the UE shall ignore the PS detach procedure and continue with the PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2011
Reference
3GPP TS 24.008 clause 4.7.3.1.
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE initiates a PS attach procedure. The SS does not answer the PS attach procedure, but initiates a PS detach
procedure (any cause except re-attach). The UE shall terminate the PS attach procedure and continue with the PS detach
procedure.
The UE initiates a PS attach procedure. The SS does not answer the PS attach procedure, but initiates a PS detach
procedure (cause re-attach). The UE shall ignore the PS detach procedure and continue with the PS attach.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2012
Expected Sequence
UE SS
ICS).
4 SS The SS ignores the ATTACH REQUEST
message and initiates a detach procedure.
5 <- DETACH REQUEST Detach type ='re-attach not required'
6 -> DETACH ACCEPT
7 UE The UE initiates the attach procedure by MMI or
AT command.
10 <- DETACH REQUEST Detach type ='re-attach required'
11 UE The UE ignores the DETACH REQUEST
message and continue with the attach
procedure.
P-TMSI-2 signature
(see ICS).
off.

None.
UE shall perform the following actions depending on the Detach type in the DETACH REQUEST message.
Case1) Detach type ='re-attach not required' GMM cause is not re-attach
At step6, when the DETACH REQUEST message is received by the UE while waiting for an ATTACH ACCEPT
message, UE shall:
- terminate the PS attach procedure and continue with the PS detach procedure.
Case2) Detach type ='re-attach required'
At step11, when the DETACH REQUEST message is received by the UE while waiting for an ATTACH ACCEPT
message, UE shall:
- ignore the PS detach procedure and continue with the PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2013
12.2.1.10 PS attach / abnormal cases / Failure due to non-integrity protection
Except the messages listed below, no layer 3 signalling messages shall be processed by the receiving MM and GMM
entities or forwarded to the CM entities, unless the security mode control procedure is activated for that domain.
- GMM messages:
- AUTHENTICATION & CIPHERING REQUEST
- AUTHENTICATION & CIPHERING REJ ECT
- IDENTITY REQUEST
- ATTACH REJ ECT
- ROUTING AREA UPDATE ACCEPT (at periodic routing area update with no change of routing area or
temporary identity)
- ROUTING AREA UPDATE REJ ECT
- SERVICE REJ ECT
- DETACH ACCEPT (for non power-off)
Reference(s):
3GPP TS 24.008 clause 4.1.1.1.1
To verify that the UE ignores NAS signalling messages when the security mode procedure is not activated.
Initial Conditions
System Simulator:
User Equipment:
Related ICS Statements

Test procedure
The attach procedure is initiated. Upon reception of ATTACH REQUEST message from the UE, the SS responds with
an ATTACH ACCEPT message without the integrity protection. The UE shall ignore this message and re-transmit
ATTACH REQUEST message at expiry of timer T3310.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2014
This time the SS starts the authentication procedure and initiates the integrity protection. After receiving ATTACH
ACCEPT message, the UE shall respond to ATTACH COMPLETE message.
Expected Sequence
UE SS
1 UE The UE is set in UE operation mode A (see ICS).
2 UE The UE is powered up or switched on and initiates
an attach procedure (see ICS).
3 SS SS checks that the IE "Establishment cause" in
5 <- AUTHENTICATION AND CIPHERING
REQUEST
Request authentication.
Set PS-CKSN
6 -> AUTHENTICATION AND CIPHERING
RESPONSE
RES
7 SS The SS does not initiate the security mode
procedure.
8 <- ATTACH ACCEPT
9 UE The UE ignores ATTACH ACCEPT message.
10 SS The SS waits 15 sec (T3310).
11 -> ATTACH REQUEST The UE re-transmits the message.
The SS verifies that the period of time between
the ATTACH REQUEST messages corresponds
to the value of T3310.
Attach type ='PS attach'
12 <- AUTHENTICATION AND CIPHERING
REQUEST
Set PS-CKSN
13 -> AUTHENTICATION AND CIPHERING
RESPONSE
RES
Mobile identity =P-TMSI
17 UE The UE is switched off or power is removed (see
ICS).
19 SS The SS releases the RRC connection. If no RRC
CONNECTION RELEASE COMPLETE message
have been received within 1 second then the SS
shall consider the UE as switched off.

None.
At step9, UE shall;
- ignore the first ATTACH ACCEPT message.
At step11, UE shall;
- re-transmit ATTACH REQUEST message after expiry of timer T3310.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2015
- respond to ATTACH COMPLETE message after the UE receives the second ATTACH ACCEPT message.
12.2.2 Combined PS attach
12.2.2.1 Combined PS attach / PS and non-PS attach accepted
1) If the network accepts the combined PS attach procedure (signalled by an IMSI) and allocates a P-TMSI, the UE
shall acknowledge the P-TMSI and continue communication with the P-TMSI.
2) If the network accepts the combined PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI,
the UE shall acknowledge the new P-TMSI and continue communication with the new P-TMSI.
3) If the network accepts the combined PS attach procedure (signalled by a P-TMSI) from the UE without
reallocation of the previously used P-TMSI, the UE shall continue communication with the previously used P-
TMSI.
4) If the network accepts the combined PS attach procedure and determines that IMSI shall be used in CS
operations, the UE shall continue communication with the IMSI for CS operations.
5) If the network accepts the combined PS attach procedure and determines that a TMSI shall be used in CS
operations, the UE shall continue communication with the TMSI for CS operations.
Reference
3GPP TS 24.008 clause 4.7.3.2.
To test the behaviour of the UE if the network accepts the PS attach procedure.
1) P-TMSI / P-TMSI signature is allocated;
2) P-TMSI / P-TMSI signature is reallocated;
3) Old P-TMSI / P-TMSI signature is not changed;
4) Mobile terminating CS call is allowed with IMSI;
5) Mobile terminating CS call is not allowed with TMSI.
Initial condition
System Simulator:
One cell operating in network operation mode I.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2016
Test procedure
1) The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns
ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH
COMPLETE message. Further communication UE - SS is performed by the new P-TMSI. For CS calls, the
IMSI is used.
2) The UE is CS paged in order to verify that the IMSI is used for CS calls.
3) The UE is PS paged in order to verify that the new P-TMSI is used for PS services.
4) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS allocates a new P-TMSI and
returns ATTACH ACCEPT message with the new P-TMSI and a new TMSI. The UE acknowledge the P-TMSI
and the TMSI by sending ATTACH COMPLETE message. Further communication UE - SS is performed by the
new P-TMSI. For CS calls, the new TMSI is used. The UE is CS paged in order to verify that the new TMSI is
used for CS services.
5) The UE is PS paged in order to verify that the new P-TMSI is used for PS services. The UE will not answer
signalling addressed to the old P-TMSI.
6) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS accepts the P-TMSI and returns
ATTACH ACCEPT message without any P-TMSI. Further communication UE - SS is performed by the
previously used P-TMSI.
7) The UE is PS paged in order to verify that the previously used P-TMSI is used for PS services.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2017
Expected Sequence
UE SS
ICS).
3 -> ATTACH REQUEST Attach type ='Combined PS / IMSI attach'
TMSI status =no valid TMSI available
CIPHERING REQUEST

CIPHERING RESPONSE

4 <- ATTACH ACCEPT Attach result ='Combined PS / IMSI attached'
P-TMSI-1 signature
5a SS The SS releases the RRC connection and waits
5s to allow the UE to read system information.
6 <- PAGING TYPE1 Mobile identity =IMSI
Paging cause ="Terminating conversational
call"
message is set to "Terminating conversational
call".
8 Void
9 Void
10 -> PAGING RESPONSE Mobile identity =IMSI
11 SS The SS releases the RRC connection and waits
12 Void
Paging for PS services
Paging cause ="Terminating interactive call"
13b Void
13c Void
14 -> SERVICE REQUEST service type ="paging response"
14aa SS The SS starts integrity protection.
14b Void

(see ICS).
message is set to "Detach".
PS / IMSI detach'
16a SS If the power was not removed, the SS releases
the RRC connection. If no RRC CONNECTION
RELEASE COMPLETE message have been
received within 1 second then the SS shall
consider the UE as switched off .
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2018
UE SS
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
21 Void
21b Void
21c SS The SS releases the RRC connection and waits
22 <- PAGING TYPE 1 Mobile identity =TMSI-1
call"
call".
24 Void
25 Void
26 -> PAGING RESPONSE Mobile identity =TMSI-1
27 SS The SS releases the RRC connection and waits
28 Void
29b Void
29c Void
30b Void
(see ICS).
PS / IMSI detach'
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2019
UE SS
TMSI status =valid TMSI available or IE not
present
CIPHERING REQUEST

CIPHERING RESPONSE

TMSI and P-TMSI not included.
Attach result ='Combined PS / IMSI attached'
P-TMSI-3 signature
38b Void
38c Void
39b Void
(see ICS).
PS / IMSI detach'
42 SS If the power was not removed, the SS releases

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2020
Case 1) SS accept the combined PS attach procedure (signalled by an IMSI) and allocates a P-TMSI.
At step5, UE shall
- send the ATTACH COMPLETE message.
At step10, when the UE receives the paging message for CS domain with Mobile identity =IMSI, UE shall;
- respond to the paging message for CS domain by sending the PAGING RESPONSE message.
At step14, when the UE receives the paging message for PS domain with Mobile identity =P-TMSI-1, UE shall:
Case 2) SS accepts the combined PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI and TMSI.
At step26, when the UE receives the paging message for CS domain with Mobile identity =TMSI, UE shall;
Case 3) SS accepts the combined PS attach procedure (signalled by a P-TMSI) from the UE without reallocation of the
previously used P-TMSI.
12.2.2.2 Combined PS attach / PS only attach accepted
1) If the network accepts the combined PS attach procedure, but GMM cause code 'IMSI unknown in HLR' is sent
to the UE the User Equipment shall delete the stored TMSI, LAI and CKSN. The User Equipment shall consider
USIM invalid for non-PS services until power is switched off or USIM is removed.
2) If the network accepts the combined PS attach procedure, but GMM cause code 'MSC temporarily not
reachable', 'Network failure' or 'Congestion' is sent to the UE, an UE operation mode A UE may perform an MM
IMSI attach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.2.
Test purpose1
To test the behaviour of the UE if the network accepts the PS attach procedure with indication PS only, GMM cause
'IMSI unknown in HLR'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2021
Test purpose2
To test the behaviour of the UE which does not support an automatic MM IMSI attach if the network accepts the PS
attach procedure with indication PS only, GMM cause 'MSC temporarily not reachable', 'Network failure' or
'Congestion'.
Test purpose 3
To test the behaviour of the UE which supports an automatic MM IMSI attach if the network accepts the PS attach
procedure with indication PS only, GMM cause 'MSC temporarily not reachable', 'Network failure' or 'Congestion'.
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH
ACCEPT message with a P-TMSI. GMM cause 'IMSI unknown in HLR' is indicated from SS. Further communication
UE - SS is performed by the P-TMSI. CS services are not possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2022
Expected Sequence
UE SS
1 UE The UE is set in UE operation mode A.


CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
GMM cause ='IMSI unknown in HLR'
7 UE The UE shall not initiate an RRC connection.
This is checked during 3 seconds.
(see ICS).
off.

Initial condition
System Simulator:
One cell operating in network operation mode I. T3212 and T3302 is set to 6 minutes.
User Equipment:
The UE has a valid TMSI, P-TMSI and RAI.
Test procedure
The UE sends an ATTACH REQUEST message. The SS allocates a P-TMSI and returns ATTACH ACCEPT message
with a P-TMSI. GMM cause 'MSC temporarily not reachable', 'Network failure' or 'Congestion' is indicated from SS.
The cause code is arbitrarily chosen. The UE sends a ROUTING AREA UPDATE REQUEST message. The SS returns
a ROUTING AREA UPDATE ACCEPT message. GMM cause 'MSC temporarily not reachable', 'Network failure' or
'Congestion' is indicated from SS. The cause code is arbitrarily chosen. The ROUTING AREA UPDATE procedure is
repeated four times. An UE operation mode A UE may then perform an MM IMSI attach procedure (according to the
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2023
ICS statement). Further communication UE - SS is performed by the P-TMSI. The existence of a signalling channel is
verified by a request for mobile identity.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2024
Expected Sequence
UE SS
1 UE The UE is set in UE operation mode A and no
automatic MM IMSI attach procedure is
indicated (see ICS).
TMSI status =valid TMSI available or IE is
omitted
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

GMM cause ='MSC temporarily not reachable',
'Network failure' or 'Congestion' (arbitrarily
chosen)
7 -> ROUTING AREA UPDATE
REQUEST
Update type ='Combined RA / LA updating with
IMSI attach'
P-TMSI-2 signature
8 <- ROUTING AREA UPDATE
ACCEPT
No new mobile identity assigned.
P-TMSI not included.
Update result ='RA updated'
P-TMSI-3 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-3 signature
ACCEPT
P-TMSI-4 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-4 signature
13 SS The SS verifies that the time between the
previous routing area update accept and
routing area update request is T3311.
ACCEPT
P-TMSI-5 signature
chosen)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2025
UE SS
REQUEST
IMSI attach'
P-TMSI-5 signature
ACCEPT
P-TMSI-6 signature
chosen)
18-20 (void)
(see ICS).
Detach type ='power switched off, PS detach'.
Stop the sequence.
off.

Initial condition
System Simulator:
One cell operating in network operation mode I. T3212 and T3302 is set to 6 minutes.
User Equipment:
Test procedure
The UE sends an ATTACH REQUEST message. The SS allocates a P-TMSI and returns ATTACH ACCEPT message
with a P-TMSI. GMM cause 'MSC temporarily not reachable', 'Network failure' or 'Congestion' is indicated from SS.
The cause code is arbitrarily chosen. The UE sends a ROUTING AREA UPDATE REQUEST message. The SS returns
a ROUTING AREA UPDATE ACCEPT message. GMM cause 'MSC temporarily not reachable', 'Network failure' or
'Congestion' is indicated from SS. The cause code is arbitrarily chosen. The ROUTING AREA UPDATE procedure is
repeated four times. An UE operation mode A UE may then perform an MM IMSI attach procedure (according to the
ICS statement). Further communication UE - SS is performed by the P-TMSI. The existence of a signalling channel is
verified by a request for mobile identity.
Expected Sequence

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2026
UE SS
1 UE Automatic MM IMSI attach procedure is
omitted
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-2 signature
ACCEPT
P-TMSI-3 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-3 signature
ACCEPT
P-TMSI-4 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-4 signature
previous routing area update accept and routing
area update request is T3311.
ACCEPT
P-TMSI-5 signature
chosen)
REQUEST
IMSI attach'
P-TMSI-5 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2027
UE SS
previous routing area update accept and routing
area update request is T3311.
ACCEPT
P No new mobile identity assigned.
P-TMSI-6 signature
chosen)
15 UE An automatic MM IMSI attach procedure is
initiated.
16 UE Registration on CS Optional step.
See TS 34.108
mode A.
Parameter mobile identity is TMSI
Steps 4917 - 5523 are only performed if the UE
has performed the Registration Procedure in
step 4116.
17 <- PAGING TYPE1 Mobile identity =TMSI-1
COMPLETE

COMPLETE

(see ICS).
off.

None.
Test requirements for Test porpose1
- initiate the Combined PS attach procedure with information elements specified in the above Expected Sequence.
At step7, when the UE receives the paging message for CS domain, UE shall:
- not respond to the paging message for CS domain.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2028
At step7, 10, 12 and 16, when the routing area updating attempt counter is less than 5 and the stored RAI is equal to the
RAI of the current serving cell, UE shall:
- perform the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach".
At step5, 7, 9 and 11, when the routing area updating attempt counter is less than 5 and the stored RAI is equal to the
RAI of the current serving cell, UE shall:
- perform MM location updating procedure.
12.2.2.3 Combined PS attach / PS attach while IMSI attach
If the PS UE is already attached for non-PS services by the MM specific attach procedure, but wants to perform an
attach for PS services, the combined PS attach procedure is performed.
Reference
3GPP TS 24.008 clause 4.7.3.2.
To test the behaviour of the UE if PS attach performed while IMSI attached.
Initial condition
System Simulator:
One cell operating in network operation mode I. ATT flag is set.
User Equipment:
The UE has a valid TMSI-1, P-TMSI-1 and RAI-1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2029
Test procedure
The UE is forced to register for CS services but not to PS services. The SS verifies that the UE does not respond to
paging messages for PS domain. Then the UE is triggered to perform the PS attach procedure and the SS verifies that it
responds to PS paging messages.
Expected Sequence
UE SS
ICS) and configured not to perform an
automatic PS attach at switch on.
2 UE The UE is powered up or switched on. No PS
attach is performed (see ICS).
3 Registration on CS See TS 34.108
The SS allocates TMSI-1
6 UE The UE is triggered to perform a PS attach.
7 -> ATTACH REQUEST Attach type ='PS attach while IMSI attached' or
'Combined PS / IMSI attached'
CIPHERING REQUEST

CIPHERING RESPONSE

No new mobile identity assigned. TMSI and P-
TMSI not included
P-TMSI-2 signature
COMPLETE


service type ="paging response"
14 <- RRC CONNECTION RELEASE
COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2030
UE is already attached for non-PS service with the MM specific attach procedure.
At step5, UE shall:
- not respond to the paging message for PS domain.
At step7, when the UE is requested to attach for PS services, UE shall:
- perform the combined PS attach procedure.
12.2.2.4 Combined PS attach / rejected / IMSI invalid / illegal ME
1) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'Illegal ME', the
User Equipment shall consider USIM invalid for PS and non-PS services until power is switched off or USIM is
removed.
2) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'Illegal ME', the
User Equipment shall delete the stored TMSI, LAI, CSKN, RAI, PS-CKSN, P-TMSI and P-TMSI signature.
Reference
3GPP TS 24.008 clause 4.7.3.2
To test the behaviour of the UE if the network rejects the combined PS attach procedure of the UE with the cause
'Illegal ME'.
Initial condition
System Simulator:
Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in
MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC2/MNC1/LAC1/RAC1(RAI-2).
All three cells are operating in network operation mode I.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2031
Test procedure
The SS rejects a PS attach with the cause value 'Illegal ME'. The SS checks that the UE does not perform PS attach in
the same or another PLMN. CS services are not possible as the USIM is blocked for CS services. PS services are not
possible as the USIM is blocked for PS services.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2032
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
ICS).
by the UE.
4 -> ATTACH REQUEST Attach type ='Combined PS / IMSI attach' or
'PS attach while IMSI attached'
omitted
5 <- ATTACH REJ ECT GMM cause 'Illegal ME'.
6 UE PAGING TYPE1 Mobile identity =TMSI-1Paging order is for CS
services.
8 <- PAGING TYPE1 Mobile identity =IMSI Paging order is for CS
services
received on cell B.
cell".
(see note)
15 <- PAGING TYPE1 Mobile identity =IMSI Paging order is for CS
services
received on cell C.
cell".
(see note)
20 <- PAGING TYPE1 Mobile identity =IMSI Paging order is for PS
services
removed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2033
UE SS
24 UE Step 25 is only performed for non-auto attach
UE.
A location updating procedure is initiated.
25 UE Registration on CS See TS34.108
Parameter Mobile identity is IMSI.
26 UE UE initiates an attach automatically (see ICS),
by MMI or AT commands.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
- initiate the combined PS attach procedure with the information elements specified in the above Expected
Sequence.
At step7, 9 and 16, when the UE receives the paging message for CS domain, UE shall,
At step11 and 21, when the UE receives the paging message for PS domain, UE shall,
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2034
At step27, when the USIM is replaced, UE shall:
At step34, when the UE receives the paging message for CS domain, UE shall,
- respond to the paging message for CS domain by sending the RAGING RESPONSE message.
12.2.2.5 Combined PS attach / rejected / PS services and non-PS services not
allowed
1) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'PS services and
non-PS services not allowed', the User Equipment shall consider USIM invalid for PS and non-PS services until
power is switched off or USIM is removed.
2) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'PS services and
non-PS services not allowed', the User Equipment shall delete the stored TMSI, LAI, CSKN, RAI, PS-CKSN, P-
TMSI and P-TMSI signature.
Reference
3GPP TS 24.008 clause 4.7.3.2.
To test the behaviour of the UE if the network rejects the combined PS attach procedure of the UE with the cause 'PS
services and non-PS services not allowed'.
Initial condition
System Simulator:
- Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in
Both cells are operating in network operation mode I.
User Equipment:
- The UE has a valid TMSI-1, P-TMSI-1 and RAI-1.
- Support of PS service Yes/No
Test procedure
The SS rejects a PS attach with the cause value 'PS services and non-PS services not allowed'. The SS checks that the
UE does not perform PS attach in the same or another PLMN. CS services are not possible as the USIM is blocked for
CS services. PS services are not possible as the USIM is blocked for PS services.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2035
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
ICS).
by the UE.
5 <- ATTACH REJ ECT GMM cause 'PS services and non-PS services
not allowed'
6 UE The SS verifies that the UE does not attempt to
access the network.
Paging order is for PS Paging.
10 UE No response from the UE to the request.
This is checked for 10 seconds
cell".
(see note)
12 (void)
access the network.
checked for 10seconds.
19 UE The UE is powered up or switched.
This step is applied only for non-auto attach
UE.
Location Update Procedure initiated from the
UE. Parameter mobile identity is IMSI.
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2036
UE SS
P-TMSI-1 signature
COMPLETE

COMPLETE

Paging is for PS services.
COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Sequence.
At step8 and 14, when the UE receives the paging message for CS domain, UE shall:
At step10 and 17, when the UE receives the paging message for PS domain, UE shall:
- initiate the combined PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2037
At step36, when the UE receives the paging message for PS domain, UE shall:
12.2.2.6 Combined PS attach / rejected / PS services not allowed
1) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'PS services not
allowed', the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM
is removed.
2) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'PS services not
allowed' the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
3) A PS class AUE shall perform an MM IMSI attach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.2
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PS services not
allowed'.
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in
ATT flag set to 1
User Equipment:
The UE has a valid TMSI, P-TMSI-1 and RAI-1.
Test procedure
The SS rejects a normal attach with the cause value 'PS services not allowed'. The SS checks that the UE does not
perform PS attach. PS services are not possible. An UE operation mode A UE shall perform an MM IMSI attach.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2038
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
UE.
UE. Parameter mobile identity is TMSI-1.
2b UE UE initiates an attach automatically (see ICS),
via MMI or AT commands.
4 <- ATTACH REJ ECT GMM cause 'PS services not allowed'
5 UE An automatic MM IMSI attach procedure is
initiated.
The SS allocates TMSI-2.
COMPLETE

disconnection of the CS signaling link.
COMPLETE

received on cell B.
cell".
(see note)
16 UE A location updating procedure is initiated.
Location updating type =normal.
The SS allocates TMSI-1.
COMPLETE

COMPLETE

Paging is for PS services
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2039
UE SS
27a UE If switch off is performed then UE performs
IMSI detach procedure.
28 UE The UE is powered up or switched.
UE.
UE. Parameter mobile identity is TMSI-1.
28b UE UE initiates an attach automatically (see ICS),
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Sequence.
At step6, if the UE is PS class A, UE shall:
- perform the MM IMSI attach procedure.
At step11, 22 and 36, when the UE receives the paging message for CS domain, UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2040
12.2.2.7a Combined PS attach / rejected / location area not allowed
1) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'location area not
allowed' the User Equipment shall:
1.1 not perform combined PS attach when in the same location area.
1.2 delete the stored LAI, CKSN, TMSI, RAI, PS-CKSN, P-TMSI and P-TMSI signature.
1.3 store the LA in the 'forbidden location areas for regional provision of service'.
2) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'location area not
allowed' the User Equipment shall:
2.1 perform combined PS attach when a new location area is entered.
2.2 delete the list of forbidden LAs when power is switched off.
Reference
3GPP TS 24.008 clauses 4.7.3.2.
To test the behaviour of the UE if the network rejects the combined PS attach procedure with the cause 'Location Area
not allowed'.
To test that the UE deletes the list of forbidden LAs when power is switched off.
Initial condition
System Simulator:
Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in
All cells are operating in network operation mode I.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2041
PS attach attempted automatically by outstanding request Yes/No

Test procedure
The SS rejects a combined PS attach with the cause value 'Location Area not allowed'. The SS checks that the UE does
not perform combined PS attach while in the location area, performs PS attach when a new location area is entered and
deletes the list of forbidden LAs when switched off. CS services are not possible unless an IMSI attach procedure is
performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2042
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
ICS).
by the UE.
3a -> ATTACH REQUEST Attach type ='Combined PS / IMSI attach' or
"PS Attach while IMSI attached"
3b <- ATTACH ACCEPT Attach result ='Combined PS / IMSI attached'
P-TMSI-1 signature
3c <- DETACH REQUEST Detach type =re-attach required
3d -> DETACH ACCEPT
5 <- ATTACH REJ ECT GMM cause 'Location Area not allowed'
6 UE No LOCATION UPDATING REQ with type
'IMSI attach' is sent to the SS
7 <- PAGING TYPE1 Mobile identity =TMSI
10 -> No response from the UE to the request.
received on cell B.
cell".
(see note)
11a UE The UE performs cell selection.
13 UE No ATTACH REQUEST or LOCATION
UPDATING REQ is sent to SS
17 UE The UE initiates an attach by MMI or AT
command.
18 No attach is performed by the UE. This is
received on cell C.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2043
UE SS
cell".
(see note)
19a UE The UE performs cell selection
Step 20a and 20b are only performed by an UE
which will not initiate a PS attach automatically
(see ICS)
20a
conditio
nal
UE Registration on CS Parameter Mobile identity is IMSI.
See TS 34.108
20b
conditio
nal
UE UE initiates an attach via MMI or AT
commands.
CIPHERING REQUEST

CIPHERING RESPONSE

Mobile identity =P-TMSI1
P-TMSI-1 signature
COMPLETE

COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.
received on cell B.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2044
UE SS
40 UE Set the cell type of cell B to the "Non-Suitable
cell".
(see note)
Cell B is preferred by the UE.
42 Step 43 is only performed for non-auto attach
UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
COMPLETE

COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2045
Sequence
At step6, when the UE receives the ATTACH REJ ECT message with GMM cause ='Location Area not allowed', UE
shall:
- not initiate MM location updating procedure.
At step13 and 18, when the UE is in the same location area, UE shall:
At step21, when the UE enters a new location area, UE shall
12.2.2.7b Combined PS attach / rejected / No Suitable Cells In Location Area
1) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'No Suitable
Cells In Location Area', the User Equipment shall:
1.3 store the LA in the 'forbidden location areas for roaming'.
2) If the network rejects a combined PS attach procedure from the User Equipment with the cause 'No Suitable
Cells In Location Area', the User Equipment shall:
2.1 search for a suitable cell in a different location area on the same PLMN.
Reference
3GPP TS 24.008 clauses 4.7.3.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2046
To test the behaviour of the UE if the network rejects the combined PS attach procedure with the cause 'No Suitable
Initial condition
System Simulator:
User Equipment:
The UE has valid TMSI, P-TMSI and RAI
Test procedure
The SS rejects a combined PS attach with the cause value 'No Suitable Cells In Location Area'. The SS checks that the
UE shall search for a suitable cell in a different location area on the same PLMN and shall perform combined PS attach
procedure in that cell
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2047
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
ICS).
by the UE.
P-TMSI-2 signature
7 -> DETACH ACCEPT
neighbour cell".
neighbour cell".
(see note)
follows.
10 <- ATTACH REJ ECT GMM cause ='No Suitable Cells In Location
Area'
received on cell B.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2048
off.

None.
At step4 and 9, when the UE is powered up or switched on, UE shall:
sequence.
At step13, when the UE enters a suitable cell in a different location area on the same PLMN, UE shall:
12.2.2.7c Combined PS attach / rejected / Roaming not allowed in this location area
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'Roaming area not allowed
in this location area' the User Equipment shall:
1.4 store the LAI in the list of "forbidden location areas for roaming".
1.5 perform a PLMN selection.
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'Roaming not
allowed in this location area'.
Initial condition
System Simulator:
Three cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4) ,
cell C in MCC1/MNC1/LAC2/RAC2 (RAI-12)
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2049
The UE has valid TMSI, P-TMSI and RAI.
Test procedure
The SS rejects a PS attach with the cause value 'Roaming area not allowed in this location area'. The SS checks that the
UE performs PLMN selection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2050
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
ICS).
by the UE.
5 <- ATTACH REJ ECT GMM cause ='Roaming area not allowed in this
location area'
6 UE No LOCATION UPDATING REQ and ATTACH
REQ with type 'IMSI attach' is sent to the SS
7 <- PAGING TYPE1 Mobile identity =TMSI
10 -> No response from the UE to the request.
11 UE UE performs PLMN selection.
received on cell B.
cell".
(see note)
14 UE No LOCATION UPDATING REQ is sent to SS
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell C.
cell".
(see note)
20 UE Registration on CS Parameter Mobile identity is IMSI.
See TS 34.108
21 UE UE initiates an attach automatically (see ICS)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2051
UE SS
COMPLETE

COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
At step6, UE shall:
- not perform MM IMSI attach and PS attach.
At step8, UE shall:
- not respond to paging for CS domain service.
- not respond to paging for PS domain service.
- perform PS attach procedure.
- perform MM IMSI attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2052
12.2.2.7d Combined PS attach / rejected / PS services not allowed in this PLMN
1) If the network rejects a PS attach procedure from the User Equipment with the cause 'PS service not allowed in
this PLMN' the User Equipment shall:
1.3 store the PLMN identity in the "forbidden PLMNs for PS service" list.
2) If the UE is in UE operation mode A the User Equipment shall:
2.1 perform IMSI attach for non-GPRS services by use of the MM IMSI attach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.1.
To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PS service not
allowed in this PLMN'.
Initial condition
System Simulator:
Two cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All two cells are operating in network operation mode I.
The PLMN contains Cell B is equivalent to the PLMN that contains Cell A.
User Equipment:
Test procedure
The SS rejects a PS attach with the cause value 'PS service not allowed in this PLMN'. The SS checks that the UE does
not perform PS attach and performs an IMSI attach for non-PS services by use of the MM IMSI attach procedure when
in the same cell.
After the cell is changed to equivalent PLMN, the UE shall perform PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2053
Expected Sequence
UE SS
received on cell A.
ICS).
2 SS The SS is set in network operation mode I.
cell ".
(see note)
by the UE.
mode A.
P-TMSI-1 signature
8 -> DETACH ACCEPT
mode A.
11 <- ATTACH REJ ECT GMM cause ='PS service not allowed in this
PLMN'
13 SS Set the cell type of cell A to the " Non-suitable
cell ".
Set the cell type of cell B to the " Serving cell".
(see note)
received on cell B.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
(see ICS).
PS / IMSI detach'
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2054

None.
At step4 and 9, UE shall:
- perform MM IMSI attach.
12.2.2.8 Combined PS attach / abnormal cases / attempt counter check /
miscellaneous reject causes
1) When a combined PS attach procedure is rejected with the attempt counter less than five, the User Equipment
shall repeat the combined PS attach procedure after T3311 timeout.
2) When a combined PS attach procedure is rejected with the attempt counter five, the User Equipment shall delete
the stored TMSI, LAI, CKSN, P-TMSI, P-TMSI signature, PS CKSN and RAI and start T3302.
3) When the T3302 expire, a new combined PS attach procedure shall be initiated.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2055
GMM cause codes that can be selected are:

'IMSI unknown in HLR'
'UE identity cannot be derived by the network'
'Network failure'
'Congestion'
'retry upon entry into a new cell'
'Semantically incorrect message'
'Invalid mandatory information'
'Message type non-existent or not implemented'
'Message type not compatible with the protocol state'
'Information element non-existent or not implemented'
'Conditional IE error'
'Message not compatible with the protocol state'
'Protocol error, unspecified'

Reference
3GPP TS 24.008 clause 4.7.3.2.
To test the behaviour of the UE with respect to the attempt counter.
Initial condition
System Simulator:
User Equipment:
UE operation mode A Yes/No Automatic PS attach procedure at switch on or power on Yes/No
Test procedure
The UE initiates a combined PS attach procedure (attempt counter zero).
The SS rejects the attach with an arbitrarily chosen cause code.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2056
The UE initiates a new combined PS attach procedure (attempt counter one) after T3311 expires.
The UE initiates a new combined PS attach procedure (attempt counter two) after T3311 expires.
The UE initiates a new combined PS attach procedure (attempt counter three) after T3311 expires.
The UE initiates a new combined PS attach procedure (attempt counter four) after T3311 expires.
The UE shall not perform a new successful attach procedure after 15 seconds.
The UE initiates a combined PS attach procedure with attempt counter zero after T3302 expires without P-TMSI, P-
TMSI signature, PS CKSN and RAI.
T3302; set to 10 minutes.
T3311; 15 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2057
Expected Sequence
UE SS
ICS).
4 <- ATTACH REJ ECT Arbitrary chosen GMM cause
T3302 with value 10 min.
attach reject and attach request is T3311
7 <- ATTACH REJ ECT Arbitrarily chosen GMM cause
17
(optiona
l step)
UE Registration on CS See TS 34.108
mode A. Location Update Procedure may be
initiated from the UE.
20 <- PAGING TYPE1 Paging order is for PS services.
21a Void
22 SS The SS verifies that the UE does not attempt to
attach for T3302 .
CIPHERING REQUEST

CIPHERING RESPONSE

Mobile identity P-TMSI-1
P-TMSI signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2058
UE SS
Paging order is for CS services..
COMPLETE

COMPLETE


33a -> RRC CONNECTION REQUEST
33b <- RRC CONNECTION SETUP
33c -> RRC CONNECTION SETUP
COMPLETE

34a <- RRC CONNECTION RELEASE
34b -> RRC CONNECTION RELEASE
COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Sequence.
UE shall perform the following actions depending on the conditions described below.
Case1) A combined PS attach procedure is rejected with the attempt counter less than five
At step 5, 8, 11 and 14, when the timer T3311 timeout has occurred, UE shall:
- repeat the combined PS attach procedure.
Case2) A combined PS attach procedure is rejected with the attempt counter five
Case3) The T3302 expires
- re-initiate the new combined PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2059
12.2.2.9 Combined PS attach / abnormal cases / PS detach procedure collision
1) When a DETACH REQUEST message is received by the UE (any cause except re-attach) while waiting for an
ATTACH ACCEPT message or ATTACH REJ ECT message, the UE shall terminate the combined PS attach
procedure and continue with the combined PS detach procedure.
2) When a DETACH REQUEST message is received by the UE (cause re-attach) while waiting for an ATTACH
ACCEPT message or ATTACH REJ ECT message, the UE shall ignore the combined PS detach procedure and
continue with the combined PS attach procedure.
Reference
3GPP TS 24.008 clause 4.7.3.2.
Initial condition
System Simulator:
User Equipment:
The UE has valid TMSI, P-TMSI and RAI. UE is Idle Updated.
Re-attach automatically when the network commands a detach with no cause value Yes/No
Test procedure
The UE initiates a combined PS attach procedure. The SS does not answer the combined PS attach procedure, but
initiates a combined PS detach procedure (any cause except re-attach). The UE shall terminate the combined PS attach
procedure and continue with the combined PS detach procedure.
The UE initiates a combined PS attach procedure. The SS does not answer the combined PS attach procedure, but
initiates a combined PS detach procedure (cause re-attach). The UE shall ignore the combined PS detach procedure and
continue with the combined PS attach. CS services are also possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2060
Expected Sequence
UE SS
ICS).
6 -> DETACH ACCEPT
7 (void)
8 (void)
9 UE The UE is attached by MMI or AT command if
the UE does not re-attach automatically upon
receiving a network initiated detach with no
cause value, (see IXIT).
12 <- DETACH REQUEST Detach type ='re-attach required'
message and continue with the attach
procedure
P-TMSI-2 signature
COMPLETE

COMPLETE

23 <- PAGING TYPE1 Paging order is for PS services.
COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2061
None.
Sequence.
UE shall perform the following actions depending on the Detach type described below.
Case1) Detach type is not re-attach
At step6, UE shall:
- respond to DETACH REQUEST message by sending DETACH ACCEPT message.
Case2) Detach type is re-attach
- ignore the PS detach procedure.

12.3 PS detach procedure
12.3.1 UE initiated PS detach procedure
12.3.1.1 PS detach / power off / accepted
The UE detaches the IMSI for PS services if the UE is switched off.
Reference
3GPP TS 24.008 clause 4.7.4.1
To test the behaviour of the UE for the detach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2062
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE performs a PS attach procedure.
The UE sends a DETACH REQUEST message to the SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2063
Expected Sequence
UE SS
1 UE The UE is set o attach to the PS services only
(see ICS). If that is not supported by the UE,
goto step 8.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
6 UE The UE is switched off (see ICS).
7a The SS releases the RRC connection. If no
off.
from step 2 to step 7a.

None.
"Registration".
"Detach".
At step7, when the UE is switched off, UE shall:
- send the DETACH REQUEST message to SS with the Detach type ='power switched off, PS detach'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2064
12.3.1.2 PS detach / accepted
1) The GPRS detach procedure is initiated by the UE by sending a DETACH REQUEST message. The detach type
information element may indicate "GPRS detach with switching off", "GPRS detach without switching off",
"IMSI detach", "GPRS/IMSI detach with switching off" or "GPRS/IMSI detach without switching off".

The UE shall include the P-TMSI in the DETACH REQUEST message. The UE shall also include a valid P-
TMSI signature, if available.
2) Upon completion of the detach procedure, the used P-TMSI signature shall be deleted.
Reference
3GPP TS 24.008 clause 4.7.4.1.1
3GPP TS 24.008 clause 4.7.1.3
To test the behaviour of the UE for the detach procedure, including treatment of P-TMSI signature.
Initial condition
System Simulator:
User Equipment:
UE PS Release Yes/No
Test procedure
The SS signal to the UE, but no response is received, as the signalling link is disconnected.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2065
Expected Sequence
UE SS
1 UE The UE is set to attach to the PS services only
(see ICS). If that is not supported by the UE,
goto step 18.
CIPHERING REQUEST

CIPHERING RESPONSE

3c SS The SS starts ciphering and integrity protection.
P-TMSI-1 signature
5 (void)
off) by MMI or AT command.
message is set to "Detach"
P-TMSI-1 signature
7a SS The SS starts ciphering and integrity protection.
8 <- DETACH ACCEPT
commands
12a SS The SS starts ciphering and integrity protection.
13 <- ATTACH ACCEPT No new mobile identity assigned
16 <- DETACH ACCEPT
17 (void)
18 UE The UE is set to attach to both PS and non-PS
services (see ICS) and the test is repeated from
step 2 to step 16.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2066
"Registration".
"Detach".
At step7, UE shall:
- send the DETACH REQUEST message (without power off) to SS with mobile identity P-TMSI-1 and P-TMSI-1
signature.
At step 12, UE shall
- initiate ATTACH REQUEST message without P-TMSI signature IE.
At step 15, UE shall:
- send the DETACH REQUEST message (without power off) to SS with mobile identity P-TMSI-1 and without
P-TMSI-1 signature.
12.3.1.3 PS detach / abnormal cases / attempt counter check / procedure timeout
1) When a T3321 timeout has occurred during a PS detach procedure with the attempt counter less than five, the
User Equipment shall repeat the PS detach procedure.
2) When a T3321 timeout has occurred during a PS detach procedure with the attempt counter five, the User
Equipment shall not repeat the procedure.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2067
Test procedure
The UE initiates a PS detach procedure (attempt counter zero). The SS does not answer with DETACH ACCEPT
message before T3321 timeout.
The UE initiates a new PS detach procedure (attempt counter one) after T3321 expires. The SS does not answer with
DETACH ACCEPT message before T3321 timeout.
The UE initiates a new PS detach procedure (attempt counter two) after T3321expires. The SS does not answer with
The UE initiates a new PS detach procedure (attempt counter three) after T3321 expires. The SS does not answer with
The UE initiates a new PS detach procedure (attempt counter four) after T3321 expires. The SS does not answer with
The UE initiates a new PS detach procedure with attempt counter five (after T3321expires). The SS does not answer
with DETACH ACCEPT message before T3321 timeout.
At T3321 timeout in the UE, the UE then deletes the logical link since the retransmissions have been repeated four
times.
The UE performs a new PS attach procedure.
T3321; 15 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2068
Expected Sequence
UE SS
goto step 25.
CIPHERING REQUEST

CIPHERING RESPONSE

7 SS No response is given from the SS.
detach requests is 15 seconds
19 SS No response is given from the SS within 40
seconds and SS verifies that the UE will not
send a DETACH REQUEST again.
20 UE Initialte a PS attach
CIPHERING REQUEST

CIPHERING RESPONSE

23 UE is switched off or power is removed (see
ICS)
off.
step 24.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2069

None.
At step9, 12, 15 and 18, when a T3321 expires with the attempt counter less than five, UE shall:
- initiate the new PS detach procedure.
At step19, when the attempt counter is greater than or equal to five, UE shall:
- not repeat the PS detach procedure.

12.3.1.4 PS detach / abnormal cases / GMM common procedure collision
When any of the GMM common messages P-TMSI REALLOCATION COMMAND, GMM STATUS or GMM
INFORMATION is received by the UE while waiting for a DETACH ACCEPT message with detach cause different
from "power off", the UE shall ignore the GMM common message.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2070
Test procedure
The following test procedure is repeated for sequence counter k =1,2,3:
The UE performs a PS attach.
The UE initiates a PS detach. The SS initiates a P-TMSI REALLOCATION COMMAND message (k=1), a GMM
STATUS message (k=2) and a GMM INFORMATION message (k=3). The UE shall ignore the GMM common
messages and continue with the PS detach procedure. The sending of the P-TMSI REALLOCATION COMMAND
message (k =1), the GMM STATUS message (k =2), the GMM INFORMATION message (k =3) and the DETACH
ACCEPT message shall be completed within Timer T3321 -10%.
Expected Sequence
The test sequence is repeated for k =1 3
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2071
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6 UE The UE initiates a detach (without power off) by
MMI or AT command.
8A
(k=1)
SS The SS sends a P-TMSI REALLOCATION
COMMAND message
9A
(k=1)
<- P-TMSI REALLOCATION
COMMAND

10A
(k=1)
UE The UE ignores the message. This is verified
for 10 seconds.
8B
(k=2)
SS The SS sends a GMM STATUS message
9B
(k=2)
<- GMM STATUS
10C
(k=2)
UE The UE ignores the message. This is verified
for 10 seconds.
8C
(k=3)
SS The SS sends a GMM INFORMATION
message
9C
(k=3)
<- GMM INFORMATION
10C
(k=3)
UE The UE ignores the message which is verified
for 10 seconds or if GMM INFORMATION
message not implemented, sends a GMM
STATUS with GMM Cause 'Message type non-
existent or not implemented'.
11 <- DETACH ACCEPT The SS responds to the DETACH REQUEST

Note: Steps 8x, 9x, 10x and 11 shall be completed within Timer T3321 -10%.
None.
At step 10A, 10B, 10C and 13, when any of the GMM common messages P-TMSI REALLOCATION COMMAND,
GMM STATUS or GMM INFORMATION is received by the UE while waiting for a DETACH ACCEPT message
with detach cause different from "power off, UE shall:
- ignore any of the GMM common message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2072
12.3.1.5 PS detach / power off / accepted / PS/IMSI detach
The UE detach the IMSI for PS and non-PS services.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE performs a combined PS attach procedure (for PS and non-PS services).
The UE sends a DETACH REQUEST message to the SS. The UE then deletes the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2073
Expected Sequence
UE SS
1 UE The UE is setto attach to both the PS and non-
PS services (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
7 -> DETACH REQUEST Detach type ='power switched off, combined
PS / IMSI detach'
off.

None.
"Registration".
"Detach".
Sequence.
- send the DETACH REQUEST message to SS with the Detach type ='power switched off, combined PS / IMSI
detach'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2074
12.3.1.6 PS detach / accepted / PS/IMSI detach
The UE detach the IMSI for PS and non-PS services.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
- One cell operating in network operation mode I.
User Equipment:
User requested combined PS and non-PS detached without powering off Yes/No
Test procedure
The UE sends a DETACH REQUEST message to the SS. When the UE receives the DETACH ACCEPT, the UE then
deletes the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2075
Expected Sequence
UE SS
PS services (see ICS).
2a SS The SS checks that the IE "Establishment
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6 UE The UE initiates a detach (without power off) by
MMI or AT command (see ICS).
7 -> DETACH REQUEST Detach type ='normal detach, combined PS /
IMSI detach'
8 <- DETACH ACCEPT

None.
"Registration".
"Detach".
Sequence.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2076
12.3.1.7 PS detach / accepted / IMSI detach
The UE shall detach for CS services.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
User Equipment:
- The UE has a valid IMSI.
User requested non-PS detached Yes/No
Test procedure
The UE performs an PS detach (for non-PS services).
CS services are not possible.
The UE attach for non-PS services by a routing area update procedure and CS services are again possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2077
Expected Sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6 UE The UE initiates a detach for non-PS services
(without power off) (see ICS).
7 -> DETACH REQUEST Detach type ='normal detach, IMSI detach'
8 <- DETACH ACCEPT
COMPLETE


COMPLETE

Paging order is for RRC connection.
13 UE The UE initiates an attach for non-PS services
by a RA update procedure (see ICS).
REQUEST
Update type ="Combined RA/LA updating with
IMSI attach"
P-TMSI-1 signature
ACCEPT
Update result ='Combined RA/LA updated''
P-TMSI-2 signature
COMPLETE

COMPLETE

COMPLETE

(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2078
UE SS
PS / IMSI detach'
off.

None.
Sequence.
At step10, after the detach procedure (Detach type ='normal detach, IMSI detach') is completed, UE shall:
At step12, after the detach procedure (Detach type ='normal detach, IMSI detach') is completed, UE shall:
- not respond to the paging message for CS.
At step21, after the routing area updating procedure (Update type ='Combined RA/LA updating') is completed, UE
shall:
12.3.1.8 PS detach / abnormal cases / change of cell into new routing area
When a change of cell into a new routing area is performed before DETACH ACCEPT message is received by the UE,
the UE shall abort the PS detach procedure and re-initiate it after the routing area update procedure.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2079
User Equipment:
Test procedure
Sufficient time is given for the UE to identify the neighbour cell before the UE is triggered to initiate a PS detach
procedure. The DETACH ACCEPT message is delayed from the SS.
The UE performs a cell reselection to a cell in a new routing area and performs a routing area update procedure.
The UE shall re-initiate a PS detach procedure when the routing area update procedure is finished.
The UE deletes the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2080
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
ICS).
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6a SS SS waits 30 sec.
IMSI detach'
9 SS No response to the DETACH REQUEST
message is given by the SS
received on cell B.
neighbour cell".
(see note)
11 UE The UE performs a RA update in the new cell.
REQUEST
Update type ='Combined RA/LA updating'
P-TMSI-1 signature
TMSI status =valid TMSI available or IE
omitted
ACCEPT
Update result ='Combined RA/LA updated'

P-TMSI-2 signature
COMPLETE

15 -> DETACH REQUEST The detach is automatically re-attempted.
Detach type ='normal detach, combined PS /
IMSI detach'
16 <- DETACH ACCEPT
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2081
Sequence.
At step12, when a change of cell into a new routing area is performed before DETACH ACCEPT message is received
by the UE, UE shall:
- abort a PS detach procedure.
- perform routing area updating procedure.
At step15, when the UE completes a routing area updating procedure, UE shall:
- re-initiate the PS detach procedure.
12.3.1.9 PS detach / abnormal cases / PS detach procedure collision
When a DETACH REQUEST is received by the UE while waiting for a DETACH ACCEPT message, the UE shall
answer the network initiated PS detach procedure.
Reference
3GPP TS 24.008 clause 4.7.4.1.
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE initiates a PS detach. The SS does not answer the detach procedure, but initiates a detach procedure (cause re-
attach not required). The UE shall continue with the network initiated detach procedure.
The UE deletes the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2082
PS and CS services are not possible.
Expected Sequence
UE SS
1 UE The UE is set in UE operation mode A(see
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
IMSI detach'
9 -> DETACH ACCEPT The UE answers the network initiated detach.
10 <- DETACH ACCEPT The SS answers the UE initiated detach.
13 <- PAGING TYPE 1 Mobile identity =TMSI-1

None.
Sequence.
At step9, when the UE receives DETACH REQUEST message from SS before UE initiated PS detach procedure has
been completed, UE shall:
- send the DETACH ACCEPT message to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2083
12.3.2 Network initiated PS detach procedure
12.3.2.1 PS detach / re-attach not required / accepted
The UE detach the IMSI for PS services.
Reference
3GPP TS 24.008 clause 4.7.4.2.
Initial condition
System Simulator:
One cell operating in network operation mode II (in case of UE operation mode A).
User Equipment:
Test procedure
The SS sends a DETACH REQUEST message to the UE. The UE then deletes the logical link.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2084
Expected Sequence
UE SS
2 UE The UE is set to either attach to PS only or both
the PS and non-PS services (see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
7 SS The SS initiates a PS detach.
GMM cause =GPRS services and non-GPRS
services not allowed
9 -> DETACH ACCEPT

None.
"Registration".
At step9, when the UE receives the DETACH REQUEST message from SS and the detach type IE indicates 're-attach
not required', the UE shall:
- send DETACH ACCEPT message to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2085
12.3.2.2 PS detach / rejected / IMSI invalid / PS services not allowed
1) If the network performs a PS detach procedure with the cause 'PS services not allowed', the User Equipment
shall consider USIM invalid for PS services until power is switched off or USIM is removed.
2) If the network performs a PS detach procedure with the cause 'PS services not allowed' the User Equipment shall
delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
Reference
3GPP TS 24.008 clause 4.7.4.2.
To test the behaviour of the UE if the network orders a PS detach procedure with the cause 'PS services not allowed' (no
valid PS-subscription for the IMSI).
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1) and cell B in
User Equipment:
Test procedure
The SS performs a detach with the cause value 'PS services not allowed'. The SS checks that the UE does not perform
PS attach in another PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2086
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
goto step 22.
by the UE.
mode A.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
Cause ='PS services not allowed'
8 -> DETACH ACCEPT
received on cell B.
cell".
(see note)
Step 11 is only performed for UE Operation
Mode A.
mode A.
12 The UE initiates an attach automatically (see
ICS), by MMI or AT commands.
removed.
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2087
P-TMSI-1 signature
(see ICS).
off.
cell".
(see note)
step 18.

None.
At step8, when the UE receives the DETACH REQUEST message (Detach type ='re-attach not required', Cause ='PS
services not allowed') from SS, UE shall:
- send DETACH ACCEPT message.
12.3.2.3 PS detach / IMSI detach / accepted
The UE detach the IMSI for PS services.
Reference
3GPP TS 24.008 clause 4.7.4.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2088
Initial condition
System Simulator:
User Equipment:
Test procedure
The SS sends a DETACH REQUEST message to the UE. The UE then performs an IMSI detach (detach for non-PS
services).
The UE attach for non-PS services by a routing area update procedure. Both PS and CS services are possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2089
Expected Sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6 SS The SS initiates a detach for non-PS services.
7 <- DETACH REQUEST Detach type ='IMSI detach'
8 -> DETACH ACCEPT
9 UE The UE initiates an attach for non-PS services
(see ICS).
REQUEST
Update type ='Combined RA/LA updating with
IMSI attach'
P-TMSI-1 signature
ACCEPT
Update result ='Combined RA/LA updating'
P-TMSI-2 signature
COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2090
Sequence.
At step8, when the UE receives the DETACH REQUEST message with Detach type ='IMSI detach', UE shall;
- send the DETACH ACCEPT message to SS.
At step10, after the completion of the detach procedure, UE shall;
- perform combined routing area updating procedure.

12.3.2.4 PS detach / re-attach requested / accepted

When receiving the DETACH REQUEST message and the detach type IE indicates "re-attach required", the UE shall
deactivate the PDP contexts and deactivate the logical link(s), if any. The UE shall then send a DETACH ACCEPT
message to the network and shall change state to GMM-DEREGISTERED. The UE shall, after the completion of the
GPRS detach procedure, initiate a GPRS attach procedure. The UE should also activate PDP context(s) to replace any
previously active PDP contexts.
A GPRS UE operating in UE operation mode A or B in network operation mode I, which receives an DETACH
REQUEST message with detach type indicating "re-attach required" or "re-attach not required" and no cause code, is
only detached for GPRS services in the network.

Reference
3GPP TS 24.008 clause 4.7.4.2.2.
To test the behaviour of the UE for the detach procedure in case automatic re-attach.
Initial condition
System Simulator:
One cell in operating in network operation mode I.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2091
Test procedure
The SS sends a DETACH REQUEST message to the UE with cause re-attach. The UE then detaches for PS services.
The UE automatically performs a new combined PS attach procedure with Attach Type GPRS attach while IMSI
attached (for PS services) and PS and CS services are again possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2092
Expected Sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

No new P-TMSI and P-TMSI signature
assigned
6 SS The SS initiates a detach with re-attach.
7 <- DETACH REQUEST Detach type ='re-attach required', GMM cause
omitted
8 -> DETACH ACCEPT
P-TMSI-2 signature
COMPLETE


COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2093
None.
Sequence.
At step8, when the UE receives DETACH REQUEST message with Detach type ='re-attach required', UE shall;
- send DETACH ACCEPT message to SS.
At step9, after UE completed PS detach procedure with Detach type ='re-attach required', UE shall:
- initiate the combined PS attach procedure with an Attach Type of either 'Combined PS / IMSI attach' or GPRS
attach while IMSI attached.
At step13, when the UE receives the paging message for PS domain, UE shall;
12.3.2.5 PS detach / rejected / location area not allowed
1) If the network performs a PS detach procedure with the cause 'location area not allowed' the User Equipment
shall:
1.2 delete any RAI or LAI, P-TMSI, P-TMSI signature and PS ciphering key sequence number
.
1.3 store the LAI in the list of the 'forbidden location areas for regional provision of service'.
1.4 delete any TMSI, LAI and ciphering key sequence number if the UE is IMSI attached and if no RRC
connection exists or if the UE is operating in UE operation mode A and an RRC connection exists when the
RRC connection is subsequently released.
2) If the network performs a PS detach procedure with the cause 'location area not allowed' the User Equipment
shall:
2.1 perform combined PS attach when a new location area is entered.
2.2 delete the list of forbidden LAs when power is switched off.
Reference
3GPP TS 24.008 clauses 4.7.4.2.
To test the behaviour of the UE if the network orders the PS detach procedure with the cause 'Location Area not
allowed'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2094
Initial condition
System Simulator:
in MCC2/MNC1/LAC1/RAC2 (RAI-7, Not HPLMN), cell C in MCC2/MNC1/LAC2/RAC1 (RAI-6, Not
HPLMN).
User Equipment:
Test procedure
The SS orders a PS detach with the cause value 'Location Area not allowed'. The SS checks that the UE does not
perform combined PS attach while in the location area, performs PS attach when a new location area is entered and
deletes the list of forbidden LAs when switched off. CS services are not possible unless an IMSI attach procedure is
performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2095
Expected Sequence
UE SS
received on cell A.
cell ".
cell ".
(see note)
ICS).
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
Cause 'Location Area not allowed'
8 -> DETACH ACCEPT
received on cell B.
cell".
(see note)
22 No response from the UE to the request.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2096
UE SS
received on cell C.
cell".
(see note)
Step 25 and 26 are only performed by an UE
(see ICS)
25
conditio
nal
UE Registration on CS See TS34.108
26
conditio
nal
UE The UE initiates an attach by MMI or AT
command.
P-TMSI-1 signature
COMPLETE

COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.
received on cell B.
46 UE Set the cell type of cell B to the "Serving cell".
cell".
(see note)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2097
UE SS
Step 48 is only performed for non-auto attach
UE.
Parameter mobile identity is TMSI-1
present
P-TMSI-2 signature
COMPLETE

COMPLETE

COMPLETE


COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
At step8, when the UE receive the DETACH REQUEST message (Detach type ='re-attach not required', Cause =
'Location Area not allowed') from SS, UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2098
- send the DETACH ACCEPT message.
UE shall perform the following action depending on UE location.
1) UE is in the same location area.
- not perform location updating procedure.
2) UE is in the new location area.

- initiate the PS attach procedure with the information elements specified in the above Expected Sequence
12.3.2.6 PS detach / rejected / No Suitable Cells In Location Area
1. If the network performs a PS detach procedure with the cause 'No Suitable Cells In Location Area', the User
Equipment shall:
1.2 store the LA in the 'forbidden location areas for roaming'.
Reference
3GPP TS 24.008 clauses 4.7.4.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2099
To test the behaviour of the UE if the network sends the DETACH REQUEST message with the cause 'No Suitable
Initial condition
System Simulator:
cells.
User Equipment:
The UE has valid IMSI.
Test procedure
The SS sends a DETACH REQUEST message with the cause value 'No Suitable Cells In Location Area'. The SS
checks that the UE shall not perform combined PS attach while in the same location area on the same PLMN. The SS
checks that the UE shall perform PS attach when the UE enters a suitable cell in a different location area on the same
PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2100
Expected Sequence
UE SS
SS Set the cell type of cell A to the "Serving cell".
neighbour cell".
neighbour cell".
(see note)
follows.
ICS).
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
Cause 'No Suitable Cells In Location Area'
7 -> DETACH COMPLETE
received on cell B.
P-TMSI-2 signature
Routing area identity =RAI-
(see ICS).
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2101
12.3.2.7 PS detach / rejected / Roaming not allowed in this location area
1) If the network performs a PS detach procedure with the cause 'Roaming area not allowed in this location area'
the User Equipment shall:
1.2 set the GPRS update status to GU3 ROAMING NOT ALLOWED.
1.3 reset the attach attempt counter.
1.4 store the LAI in the list of "forbidden location areas for roaming".
1.5 perform a PLMN selection.
2) If the UE is IMSI attached via MM procedures, the UE shall in addition:
2.2 reset the location update attempt counter.
Reference
3GPP TS 24.008 clauses 4.7.4.2.
To test the behaviour of the UE if the network orders the PS detach procedure with the cause ' Roaming area not
allowed in this location area '.
Initial condition
System Simulator:
in MCC2/MNC1/LAC1/RAC2 (RAI-7, Not HPLMN), cell C in MCC2/MNC1/LAC2/RAC1 (RAI-6, Not
HPLMN).
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2102
Test procedure
The SS orders a PS detach with the cause value ' Roaming area not allowed in this location area '. The SS checks that
the UE does not perform combined PS attach while in the location area, performs PS attach when a new location area is
entered and deletes the list of forbidden LAs when switched off. CS services are not possible unless an IMSI attach
procedure is performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2103
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
ICS).
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
Cause 'Roaming not allowed in this location
area '
8 -> DETACH ACCEPT
received on cell B.
cell".
(see note)
22 No response from the UE to the request.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2104
UE SS
received on cell C.
cell".
(see note)
UE.
26 UE The UE initiates an attach automatically (See
ICS), by MMI or AT command.
P-TMSI-1 signature
COMPLETE

COMPLETE

COMPLETE

COMPLETE

(see ICS).
PS / IMSI detach'
off.
received on cell B.
46 UE Set the cell type of cell B to the "Serving cell".
cell".
(see note)
UE.
Parameter mobile identity is TMSI-1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2105
UE SS
present
P-TMSI-2 signature
COMPLETE

COMPLETE

COMPLETE


COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
At step8, when the UE receive the DETACH REQUEST message (Detach type ='re-attach not required', Cause ='
Roaming not allowed in this location area') from SS, UE shall:
- send the DETACH ACCEPT message.
UE shall perform the following action depending on UE location.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2106
1) UE is in the same location area.
- not perform location updating procedure.
2) UE is in the new location area.
- initiate the PS attach procedure with the information elements specified in the above Expected Sequence
12.3.2.8 PS detach / rejected / PS services not allowed in this PLMN
If the network performs a PS detach procedure with the cause ' PS services not allowed in this PLMN ', the UE:
1. shall delete any RAI, P-TMSI, P-TMSI signature, and PS ciphering key sequence number stored, shall set the PS
update status to GU3 ROAMING NOT ALLOWED (and shall store it according to section 4.1.3.2) and shall
change to state GMM-DEREGISTERED.
2. shall store the PLMN identity in the "forbidden PLMNs for PS service" list.
If the network performs a PS detach procedure with the cause ' PS services not allowed in this PLMN ', the UE
operating in UE operation mode A in network operation mode I:
1. shall set the timer T3212 to its initial value and restart it, if it is not already running.
2. is still IMSI attached for CS services in the network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2107
Reference(s):
3GPP TS 24.008 subclause 4.7.4.2.2
Test purpose for Test procedure1
To test the behaviour of the UE if the network initiates a PS detach procedure with the cause "PS services not
allowed in this PLMN" (for Conformance requirement1, 2).
Test purpose for Test procedure2
To test the behaviour of the UE operating in UE operation mode A in network operation mode I if the network
initiates a PS detach procedure with the cause "PS services not allowed in this PLMN" (for Conformance
requirement3, 4).
Initial conditions
System Simulator:
Two cells cellA in MCC1/MNC1/LAC1/RAC1, cellB in MCC1/MNC2/LAC2/RAC1.
Both two cells are operating in network operation mode II.
The PLMN contains Cell B is equivalent to the PLMN that contains Cell A.
cells.
User Equipment:
- Support of PS service Yes/No.
- UE operation mode A Yes/No
- UE operation mode C Yes/No (only if mode A not supported)..
- Switch off on button Yes/No.
- Automatic PS attach procedure at switch on or power on Yes/No.
Test procedure
Two cells are configured.
Cell A transmits with higher power so that the UE attempts an attach procedure to cell A.
The UE initiates a PS attach procedure.
The SS sends a PS detach with the cause "PS services not allowed in this PLMN".
The SS verifies that the UE does not perform a periodic ROUTING AREA UPDATE procedure in this PLMN after the
timer T3312 is expired and does not respond a paging for PS services.
Cell B transmits with high power so that the UE attempts an attach procedure to cell B.
The UE initiates a PS attach procedure.
The SS verifies that the UE performs a periodic ROUTING AREA UPDATE procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2108
Expected sequence
UE SS
received on cell A.
1 UE The UE is set in UE operation mode A or C
(see ICS).
neighbour cell "
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

8 <- ATTACH ACCEPT Attach result =' PS only attached'
P-TMSI-2 signature
T3312 =6minutes
10 <- DETACH REQUEST Detach Type ='re-attach not required'
Cause ='PS services not allowed in this PLMN'
11 -> DETACH ACCEPT
access the network for T3312.
received on cell B.
neighbour cell ".
Set the cell type of cell B to the "Serving cell "
(see note)
17 Cell B is preferred by the UE.
UE.
18 Registration on CS See TS 34.108
mode A.
19 The UE initiates an attach automatically (See
ICS), by MMI or AT command.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3312 =6minutes
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2109
27 -> ROUTING AREA UPDATING
REQUEST
Update type ='Periodic updating'
P-TMSI-2 signature
28 <- ROUTING AREA UPDATING
ACCEPT
P-TMSI and TMSI not included.
(see ICS).
Detach type ='power switched off,
off.

None.
Initial conditions
System Simulator:
One cell is operating in network operation mode I: MCC1/MNC1/LAC1/RAC1.
User Equipment:
- Support of PS service Yes/No.
- UE operation mode A Yes/No
- Switch off on button Yes/No.
- Automatic PS attach procedure at switch on or power on Yes/No.
Test procedure
One cell is configured.
The UE initiates a combined attach procedure.
The SS sends a PS detach with the cause "PS services not allowed in this PLMN".
The SS verifies that the UE performs a periodic location area updating procedure after the timer T3212 is expired.
The SS verifies that the UE responds a paging for CS services.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2110
Expected sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

7 <- ATTACH ACCEPT Attach result =' Combined PS/IMSI attached '
P-TMSI-2 signature
9 <- DETACH REQUEST Detach Type ='re-attach not required'
Cause ='PS services not allowed in this PLMN'
10 -> DETACH ACCEPT
11 The SS releases the RRC connection
12 SS The SS waits for the UE to expiry the timer
T3212.
13 UE Registration on CS The UE performs a location update procedure.
See TS 34.108
call"
15 SS The SS checks that the IE "Establishment
REQUEST message is set to "Terminating
interactive call".
17 The SS releases the RRC connection
(see ICS).
Detach type ='power switched off'
off.

None.
12.3.2.8.5.1 Test Requirement for Test procedure1
At step4, when the UE is powered up or switched on, the UE shall:
At step11, when the UE receives DETACH REQUEST message with the cause "PS services not allowed in this
PLMN", the UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2111
At step13, when the UE receives the paging for PS services with "Mobile identity =P-TMSI-2", the UE shall;
- not respond to the paging for PS services.
At step14, when the time T3312 is expired, the UE shall:
- not attempt to access the network.
At step20, when the UE enters the different cell with the equivalent PLMN, the UE shall:
At step27, when the time T3312 is expired, the UE shall:
- initiate the periodic routing area updating procedure with the information elements specified in the above
Expected Sequence.
12.3.2.8.5.2 Test Requirement for Test procedure2
At step3, when the UE is powered up or switched on, the UE shall:
At step10, when the UE receives DETACH REQUEST message with cause "PS services not allowed in this PLMN ",
the UE shall:
At step12, while the SS wait for the timer T3312 to expire, the UE shall:
- not perform the periodic location area updating procedure.
At step13, when the T3212 timer is expired, the UE shall:
- initiate the periodic location area updating procedure.
At step16, when the UE receives the paging for CS services with "Mobile identity =IMSI", the UE shall;
- respond to the paging for CS services by sending the PAGING RESPONSE message.
12.4 Routing area updating procedure
This procedure is used to update the actual routing area of an UE in the network.
12.4.1 Normal routing area updating
The routing area updating procedure is a GMM procedure used by PS UEs of UE operation mode A or C that are IMSI
attached for PS services only.
12.4.1.1a Routing area updating / accepted
1) If the network accepts the routing area updating procedure and reallocates a P-TMSI, the UE shall acknowledge
the new P-TMSI and continue communication with the new P-TMSI.
2) If the network accepts the routing area updating procedure from the UE without reallocation of the old P-TMSI,
the UE shall continue communication with the old P-TMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2112
3) The routing area updating procedure shall also be used by a UE which is attached for PS services if a new PLMN
is entered.
Reference
3GPP TS 24.008 clause 4.7.5, 4.7.5.1.
To test the behaviour of the UE if the network accepts the routing area updating procedure.
1) P-TMSI / P-TMSI signature is reallocated.
To test the behaviour of the UE if the UE enters the new PLMN.
Initial condition
System Simulator:
in MCC2/MNC1/LAC1/RAC2 (RAI-7).
The PLMN contains cell C is equivalent to the PLMN that contains cell A.
prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A) in all cells.
User Equipment:
Test procedure
1) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS reallocates the P-TMSI and returns
ROUTING AREA UPDATE ACCEPT message with a new P-TMSI. The UE acknowledge the new P-TMSI by
sending ROUTING AREA UPDATE COMPLETE message. Further communication UE - SS is performed by
the new P-TMSI. The UE will not answer signalling addressed to the old P-TMSI.
2) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS accepts the P-TMSI and returns
ROUTING AREA UPDATE ACCEPT message without any P-TMSI. Further communication UE - SS is
performed by the P-TMSI.
3) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS reallocates the P-TMSI and returns
ROUTING AREA UPDATE ACCEPT message with a new P-TMSI. The UE acknowledge the new P-TMSI by
sending ROUTING AREA UPDATE COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2113
Expected Sequence
UE SS
received on cell A.
neighbour cell".
neighbour cell".
(see note)
2 UE The UE is set to attach to PS services only (see
ICS). If that is not supported by the UE, goto
step 32.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
Equivalent PLMN: MCC =2, MNC =1
received on cell B.
neighbour cell".
(see note)
REQUEST
Update type ='RA updating'
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

11 Void
11b Void
11d <- PAGING TYPE1 Mobile identity =P-TMSI-1
11e SS SS verifies that the UE transmits an RRC
CONNECTION REQUEST message. SS will
reject this request. The IE "Establishment
cause" is not checked.
received on cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2114
UE SS
neighbour cell".
(see note)
15 UE Cell A is preferred by the UE.
REQUEST
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
Equivalent PLMN: MCC =2, MNC =1
Paging cause ="Terminating interactive call".
interactive call"
18b Void
18c Void

received on cell C.
neighbour cell".
(see note)
This is applicable only for UE in UE operation
mode A.
REQUEST
P-TMSI-1 signature
ACCEPT
P-TMSI-3 signature
COMPLETE


(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2115
UE SS
off.

None.
At step 3a, 7a, 15a and 22 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment
cause set to "Registration".
"Terminating Interactive Call".
"Detach".
At step8, UE shall;
- initiate the routing area updating procedure with the information elements specified in the above Expected
Sequence.
Sequence.
Sequence.
12.4.1.1b Routing area updating / accepted / Signalling connection re-establishment
When the UE receives an indication from the lower layers that the RRC connection has been released with cause
"Directed signalling connection re-establishment", then the UE shall enter PMM-IDLE mode and initiate immediately a
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2116
normal routing area update procedure (the use of normal or combined procedure depends on the network operation
mode in the current serving cell) regardless whether the routing area has been changed since the last update or not.
Reference
3GPP TS 24.008 clause 4.7.2.5, 4.7.5.1
To test the behaviour of the UE if the UE receives a RRC CONNECTION RELEASE message with cause ="Directed
signalling connection re-establishment".
Initial condition
System Simulator:
One cell(Cell A) in MCC1/MNC1/LAC1/RAC1 (RAI-1) operating in network operation mode I. ATT flag is set
to 0.
User Equipment:
The UE has a valid TMSI, P-TMSI-1 and RAI-1
Test procedure
a) The UE initiates a Service request procedure in order to establish the PS signalling connection for the upper
layer signalling.
b) After the Service request procedure is complete, the SS sends the RRC CONNECTION RELEASE message
with cause ="Directed signalling connection re-establishment" to the UE.
c) After the UE release the RRC connection, the UE initiate immediately a normal routing area update procedure.
Expected Sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2117
UE SS
6 UE The UE initiates an upper-layer signalling, e.g.,
Active PDP Context request, by MMI or by AT
command.
7 -> SERVICE REQUEST Service type ="signalling",
CIPHERING REQUEST

CIPHERING RESPONSE

11 SS The SS releases the RRC connection, using
Release cause=Directed Signalling Connection
Re-establishment
12 Void
13 SS SS verifies that the IE "Establishment cause" in
message is set to "Call re-establishment".
14 Void
15 Void
REQUEST
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
20 -> DETACH REQUEST Message not sent if power is removed. Detach
type ='power switched off, PS detach'
off.

None.
- initiate the routing area updating procedure whether the routing area has been changed since the last update or
not.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2118
12.4.1.1c Void
12.4.1.2 Routing area updating / rejected / IMSI invalid / illegal ME
1) If the network rejects a routing area updating procedure from the User Equipment with the cause 'Illegal ME', the
User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.
2) If the network rejects a routing area updating procedure from the User Equipment with the cause 'Illegal ME', the
User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
Reference
3GPP TS 24.008 clause 4.7.5.1.
To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause
'Illegal ME'.
Initial condition
System Simulator:
All three cells are operating in network operation mode II (in case of UE operation mode A)
cells.
User Equipment:
Test procedure
The SS rejects a routing area updating with the cause value 'Illegal ME'. The SS checks that the UE does not perform
PS attach in the same or another PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2119
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
cell".
(see note)
by the UE.
3a Void
CIPHERING REQUEST

CIPHERING RESPONSE

5 <- ATTACH ACCEPT No new mobile identity assigned.P-TMSI and P-
TMSI signature not included.
received on cell B.
neighbour cell".
(see note)
REQUEST

REJ ECT
GMM cause ='Illegal ME'
PAGING TYPE1 (used for NW-mode II).
received on cell C.
cell".
Set the cell type of cell A to the Non-Suitable
cell.
(see note)
removed.
16a Step 16b is only performed by UE in operation
mode A
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2120
16b UE Registration on CS See TS 34.108
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
off.

None.
At step8, UE shall;
Sequence.
At step11, after the routing area updating procedure is rejected with GMM cause ='Illegal ME', UE shall;
At step14, UE shall,
- not initiate PS attach procedure.
At step17, after the UE is powered up or USIM is replaced, UE shall;
12.4.1.3 Routing area updating / rejected / UE identity cannot be derived by the
network
If the network rejects a routing area updating procedure from the User Equipment with the cause 'UE identity cannot be
derived by the network', the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.
Depending on the manufacturer the UE may or may not perform a PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2121
Reference
3GPP TS 24.008 clause 4.7.5.1.
To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause 'UE
identity cannot be derived by the network'.
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in
cells.
User Equipment:
Automatic attach procedure when UE identity cannot be derived by the network Yes/No
Test procedure
The SS rejects a normal routing area updating with the cause value 'UE identity cannot be derived by the network'. The
UE detach locally. A new PS attach may be performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2122
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
ICS).
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
7 SS Set the cell type of cell A to the " Suitable
neighbour cell ".
(see note)
REQUEST
P-TMSI-2 signature
REJ ECT
GMM cause ='UE identity cannot be derived by
the network'
11 UE If an automatic attach procedure by the UE is
not possible when the UE identity cannot be
derived by the network (see ICS) goto step 19.
12 UE An Automatic PS attach procedure is initiated
(see ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
(see ICS).
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2123
UE SS
20 UE No response from the UE to the request, as the
UE has detached locally. This is checked for 10
seconds.
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in
TS34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only".

None.
At step9, UE shall;
Sequence.
UE shall perform the following actions depending on the implementation of the UE.
Case 1) UE supports an Automatic PS attach procedure.
Case 2) UE does not support an Automatic PS attach procedure.
12.4.1.4a Routing area updating / rejected / location area not allowed
1) If the network rejects a routing area updating procedure from the User Equipment with the cause 'location area
not allowed' the User Equipment shall:
1.2 delete the stored RAI, PS-CKSN, P-TMSI, P-TMSI signature and TMSI, LAI and ciphering key sequence
number.
1.3 store the LA in the 'forbidden location areas for regional provision of service'.
2) If the network rejects a routing area updating procedure from the User Equipment with the cause 'location area
not allowed' the User Equipment:
2.1 may perform routing area update when a new location area is entered.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2124
2.2 shall delete the list of forbidden LAs after switch off (power off).
Reference
3GPP TS 24.008 clauses 4.7.5.1.
To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause
'Location Area not allowed'.
Initial condition
System Simulator:
Four cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) , cell B in
MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC1/MNC1/LAC2/RAC1 (RAI-3), cell D in
MCC2/MNC1/LAC2/RAC1(RAI-6).
All four cells are operating in network operation mode II.
cells.
The PLMN contains Cell D is equivalent to the PLMN that contains Cell C.

User Equipment:
Test procedure
The SS rejects a routing area updating with the cause value 'Location Area not allowed'. The SS checks that the UE
does not perform PS attach while in the location area, performs PS attach when a new location area is entered and
deletes the list of forbidden LAs when switched off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2125
Expected Sequence
UE SS
received on cell C.
cell".
cell".
cell".
(see note)
goto step 33.
initiates an attach (see ICS). Cell C is preferred
by the UE.
3a Void
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
received on cell B.
cell".
(see note)
8 SS Cell B is preferred by the UE.
8a The following step is only performed for UE
Operation Mode A.
8b
REQUEST
P-TMSI-1 signature
REJ ECT
GMM cause ='Location Area not allowed'
received on cell A.
cell".
(see note)
cell".
(see note)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2126
UE SS
received on cell D.
Operation Mode A.
17b UE Registration on CS See TS34.108
Parameter mobile identity is IMSI
UE The UE initiates a PS attach either
automatically or manually (see ICS).
P-TMSI-2 signature
removed.
off.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
received on cell A.
cell".
(see note)
28 Cell A is preferred by the UE.
Operation Mode A.
28b UE Registration on CS See TS34.108
REQUEST
P-TMSI-1 signature
ACCEPT
No new mobile identity assigned.P-TMSI and P-
TMSI signature not included.Update result =
'RA updated'

(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2127
UE SS
off.
ICS), cell A is switched off and the test is
repeated from step 3 to step 32.

None.
At step9, UE shall:
Sequence.
At step12 and 15, when in the same location area, UE shall
At step18, when a new location area is entered, UE shall
At step24, when the USIM is replaced , UE shall;
Sequence.
12.4.1.4b Routing area updating / rejected / No Suitable Cells In Location Area
1) If the network rejects a routing area updating procedure from the User Equipment with the cause 'No Suitable Cells
In Location Area', the User Equipment shall:
1.1 store the LA identity in the 'forbidden location areas for roaming'.
1.3 not delete equivalent PLMNs list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2128
1.4 not delete the MM and GMM contexts
Reference
3GPP TS 24.008 clauses 4.7.5.1.
To test the behaviour of the UE if the network rejects the routing area updating procedure with the cause 'No Suitable
To test that the UE deletes the list of forbidden LAs when power is switched off'.
Initial condition
System Simulator:
Four cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC2/RAC1 (RAI-3), cell C
in MCC2/MNC1/LAC1/RAC1 (RAI-2), cell D in MCC1/MNC1/LAC1/RAC2 (RAI-4),
All four cells are operating in network operation mode II.
cells.
The PLMNs of cells A, B, C and D are all equivalent.
User Equipment:
Test procedure
The SS rejects a routing area updating with the cause value 'No Suitable Cells In Location Area'. The SS checks that the
UE shall perform Routing Area Update procedure when the UE enters a suitable cell in a different location area on the
same PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2129
Expected Sequence
UE SS
SS The following message are sent and shall be
received on cell D.
neighbour cell".
neighbour cell".
neighbour cell".
(see note)
initiates an attach (see ICS). Cell D is preferred
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
neighbour cell".
neighbour cell".
Set the cell type of cell D to the "Suitable
neighbour cell".
(see note)
follows.
Cell A is preferred by the UE.
REQUEST
P-TMSI-1 signature
REJ ECT
GMM cause ='No Suitable Cells In Location
Area'
received on cell B.
REQUEST
P-TMSI-1 signature
The UE shall initiate a location area updating
procedure between steps 8 and 12.
ACCEPT
P-TMSI-2 signature
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2130
off.

None.
At step7, UE shall;
- initiate the routing area updating procedure.
- perform the routing area updating procedure.
12.4.1.4c Routing area updating / rejected / PS services not allowed in this PLMN
If the network rejects a routing area updating procedure from the User Equipment with the cause 'PS service not
allowed in this PLMN', the User Equipment shall:
- delete any RAI, P-TMSI, P-TMSI signature, and PS ciphering key sequence number stored.
- shall set the PS update status to GU3 ROAMING NOT ALLOWED.
- store the PLMN identity in the "forbidden PLMNs for PS service" list.
- not delete the equivalent PLMN list.
UE shall perform the following actions depending on the update type, UE operation mode and network operation mode.
1) UE is in UE operation mode C
UE shall perform a PLMN selection instead of a cell selection.
2) UE is in UE operation mode A, update type =periodic updating and Network is in network operation mode I
UE shall set the timer T3212 to its initial value and restart it, if it is not already running.
3) UE is in UE operation mode A and Network is in network operation mode II.
UE shall be still IMSI attached for CS services in the network.
Reference
3GPP TS 24.008 clause 4.7.5.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2131
To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause 'PS
services not allowed in this PLMN'.
Initial condition
System Simulator:
cells.
User Equipment:
The UE is in UE operation mode C.
Test procedure 1
The SS rejects a routing area updating with the cause value 'PS services not allowed in this PLMN'. The SS checks that
the UE performs PLMN selection.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2132
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

5 <- ATTACH ACCEPT No new mobile identity assigned.P-TMSI and P-
TMSI signature not included.
received on cell B.
neighbour cell ".
(see note)
REQUEST

REJ ECT
GMM cause ='PS services not allowed in this
PLMN'
cell".
(see note)
cell".
(see note)
17 -> ATTACH REQUEST Update type ='PS attach'
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2133
18 <- ATTACH ACCEPT Update result ='PS only attached'
P-TMSI-1 signature
(see ICS).
off.

None.
Test procedure2
Initial condition
System Simulator:
One cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) operating in network operation mode I.
User Equipment:
The UE is in UE operation mode A.
Test procedure
The UE initiates a PS attach procedure with identity P-TMSI. The SS reallocates the P-TMSI and returns ATTACH
ACCEPT message with a new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH
COMPLETE message. A routing area updating procedure is performed at T3312 timeout. The SS rejects a routing area
updating with the cause value 'PS services not allowed in this PLMN'. The UE sets the timer T3212 to its initial value
and restart it, if it is not already running.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2134
Expected Sequence
UE SS
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3312 =6 minutes
REQUEST
P-TMSI-2 signature
REJ ECT
PLMN'
attach and the periodic RA updating is T3312
REQUEST
P-TMSI-2 signature
REJ ECT
PLMN'
(see ICS).
off.

None.
Test requirement for Test procedure1
At step8, UE shall;
Sequence.
At step11, after the routing area updating procedure is rejected with GMM cause ='PS service not allowed in this
PLMN', UE shall;
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2135
- initiate PLMN selection.
Test requirement for Test procedure2
At step6, UE shall;
Sequence.
PLMN', UE shall;
- set the timer T3212 to its initial value and restart it.
At step8, UE shall,
- not initiate periodic routing area updating procedure.
At step9, UE shall;
Sequence.
PLMN', UE shall;
- set the timer T3212 to its initial value and restart it.
- not initiate periodic routing area updating procedure.
12.4.1.4d Routing area updating / rejected / Roaming not allowed in this location area
1) If the network rejects a routing area updating procedure from the User Equipment with the cause 'roaming not
allowed in this location area' the User Equipment:
1.1 shall not perform PS attach when in the same location area.
1.2 shall store the LA in the 'forbidden location areas for roaming'.
1.3 shall perform a routing area updating when entering into a new location area if the LAI or the PLMN
identity is not contained in any of the lists "forbidden LAs for roaming", "forbidden LAs for regional
provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" and the current status
is different from "IDLE NO IMSI".
2) The User Equipment shall erase the list of 'Forbidden location areas for roaming' when switched off or when the
USIM is removed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2136
References
3GPP TS 24.008 clause 4.7.5.1.4.
3GPP TS 23.122 clause 4.5.2.
3GPP TS 24.008 clause 4.4.1.
Test purpose1
To test that on receipt of a rejection using the 'Roaming not allowed in this area' cause code, the UE ceases trying a
routing area updating procedure on that location area. Successful routing area updating procedure is possible in other
location areas.
Test purpose2
12.4.1.4d.4.1 Test procedure1
Initial condition
System Simulator:
Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2), cell B in MCC2/MNC1/LAC2/RAC1 (RAI-6).
User Equipment:
Test procedure
The SS rejects a routing area updating with the cause value 'Roaming not allowed in this area'. A new attempt for a PS
attach is not possible. Successful PS attach procedure is performed in another location area. The UE is moved back to
the 1
st
location area. A routing area updating shall not be performed, as the LA is on the forbidden list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2137
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
SS allocates Mobile identity =TMSI-1.
4 -> ATTACH REQUEST Attach type =' PS attach '
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
7 SS Set the cell type of cell A to the " Non-suitable
cell ".
(see note)
UE.
Parameter mobile identity is TMSI-1.
REQUEST
P-TMSI-2 signature
REJ ECT
GMM cause ='Roaming not allowed in this
area'
command.
received on cell A.
neighbour cell".
(see note)
UE.
20 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2138
UE SS
REQUEST
CIPHERING REQUEST

CIPHERING RESPONSE

ACCEPT
P-TMSI-1 signature
COMPLETE

25 Void
26 Void
27 Void
30 Void
32 Void
33 Void
34 Void

37 Void

received on cell B.
neighbour cell".
(see note)
39 UE No ROUTING AREA UPDATE REQUEST sent
to SS

12.4.1.4d.4.2 Test procedure2
Initial condition
System Simulator:
User Equipment:
The UE has a valid IMSI. UE is Idle Updated on cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2139
Test procedure
The SS rejects a routing area updating with the cause value 'Roaming not allowed in this area'. The UE is switched off
for 10 seconds and switched on again. The SS checks that a PS attach is possible on the cell on which the previous
routing area updating had been rejected.
If USIM removal is possible without switching off:
The SS rejects a routing area updating with the cause value 'Roaming not allowed in this area'. The USIM is removed
and inserted in the UE. The SS checks that a PS attach procedure and routing area updating procedure is possible on the
cell on which the routing area updating had previously been rejected.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2140
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
initiates an attach (see ICS.
SS allocates Mobile identity =TMSI-1.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
7 SS Set the cell type of cell A to the "Non-suitable
cell".
(see note)
UE.
REQUEST
P-TMSI-2 signature
REJ ECT
area'
command.
removed.
or switched on.
UE.
20 UE The UE initiates an attach automatically (see
ICS) by MMI or AT command.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2141
UE SS

CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
25 Void
26 Void
27 Void
30 Void

32 Void
33 Void
34 Void

37 Void
(see ICS).
off.

None.
At step9, when the RF level of the attached cell is lower than the RF level of the new cell, UE shall:
- initiate the routing area update procedure with the information elements specified above Expected Sequence
At step12, when the SS rejects the routing area update procedure with GMM cause ='Roaming not allowed in this area',
UE shall:
- not initiate a PS attach procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2142
- initiate the routing area update procedure.
At step28, when the UE receives the paging message for CS domain, UE shall;

At step9, UE shall:
- initiate the routing area update procedure with the information elements specified above Expected Sequence.
12.4.1.5 Routing area updating / abnormal cases / attempt counter check /
miscellaneous reject causes
When a routing area updating procedure is rejected with the attempt counter less than five, the UE shall repeat the
routing area updating procedure after T3330 timeout.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2143
When a T3330 timeout has occurred during a routing area updating procedure with the attempt counter five, the UE
shall start timer T3302.
When the T3302 expire, a new routing area updating procedure shall be initiated.
Reference
3GPP TS 24.008 clause 4.7.5.1.
Initial condition
System Simulator:
MCC1/MNC1/LAC1/RAC2 (RAI-4). The ATT-flag shall indicate that the MS should use IMSI attach/detach
procedures.
User Equipment:
Test procedure
The UE initiates a routing area updating procedure (attempt counter zero).
The SS rejects the routing area updating procedure with a GMM cause 'congestion' code.
The UE initiates a new routing area updating procedure (attempt counter one) after T3311 expires.
The UE initiates a new routing area updating procedure (attempt counter two) after T3311 expires.
The UE initiates a new routing area updating procedure (attempt counter three) after T3311 expires.
The UE initiates a new routing area updating procedure (attempt counter four) after T3311 expires.
The UE initiates a new routing area updating procedure with attempt counter five (after T3311 expires).
The UE shall not perform a new successful routing area updating procedure after T3311 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2144
The UE initiates a routing area updating procedure with attempt counter zero after T3302 expires with the stored P-
TMSI, P-TMSI signature, PS CKSN and RAI.
T3330; set to 15 seconds.
T3311; set to 15 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2145
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
(see note)
This step is applied only for UE in UE operation
mode A.
Parameter mobile identity is TMSI.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
REJ ECT
GMM cause ='Congestion'
routing area updating requests is 15 seconds
REQUEST

P-TMSI-2 signature
REJ ECT
REQUEST

P-TMSI-2 signature
REJ ECT
REQUEST
P-TMSI-2 signature
REJ ECT
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2146
UE SS
REQUEST

P-TMSI-2 signature
REJ ECT
attach for 10 minutes .
23 SS The SS shall release the PS signalling
connection.
This step is applied only for UE in UE operation
mode A.
Parameter mobile identity is TMSI.
REQUEST

P-TMSI-2 signature
ACCEPT
P-TMSI-3 signature
COMPLETE

(see ICS).
An IMSI Detach must be performed for an UE in
Operation Mode A either before or after the PS
Detach
off.

None.
At step8, UE shall:
Case 1) At step11, 14, 17 and 20, a routing area updating procedure is rejected from SS with the attempt counter
less than five,
UE shall:
- repeat the routing area updating procedure after T3330 timeout
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2147
Case2) At step22 a routing area updating procedure is rejected from SS with the attempt counter five
- not initiate a routing area updating procedure.
Case3) At step24, the T3302 expires
UE shall:
- initiate the new routing area updating procedure
12.4.1.6 Routing area updating / abnormal cases / change of cell into new routing
area
When a change of cell into a new routing area is performed before the routing area updating procedure is finished, the
UE shall abort the routing area updating procedure and re-initiate it in the new routing area.
Reference
3GPP TS 24.008 clause 4.7.5.1.
Initial condition
System Simulator:
MCC1/MNC1/LAC1/RAC2 (RAI-4) and cell C In MCC1/MNC1/LAC1/RAC3 (RAI-5).
All cells are operating in network operation mode II (in case of UE operation mode A).
cells.
User Equipment:
Test procedure
The UE initiates a routing area updating procedure. The ROUTING AREA UPDATE ACCEPT message is delayed
from the SS. The UE performs a cell update into a new routing area. The UE shall re-initiate a routing area updating
procedure in the new routing area.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2148
Expected Sequence
UE SS
received on cell A.
goto step 18.
cell".
cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
10 SS No response to the ROUTING AREA UPDATE
REQUEST message is given by the SS
received on cell C.
11 SS Set the cell type of cell B to the "Suitable
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-3 signature
COMPLETE

(see ICS).
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2149
ICS). Set the cell type of cell C to the "Non-
Suitable cell".The test is repeated from step 2 to
step 17.

None.
At step9, UE shall:
At step13, when change of cell into a new routing area is performed before the routing area updating procedure is
finished, UE shall:
- abort the routing area updating procedure.
- re-initiate new routing area updating procedure in the new routing area.
12.4.1.7 Routing area updating / abnormal cases / change of cell during routing area
updating procedure
When a change of cell within a new routing area is performed before the routing area updating procedure is finished, the
UE shall perform the cell update before the routing area updating procedure is finished.
Reference
3GPP TS 24.008 clause 4.7.5.1.
Initial condition
System Simulator:
MCC1/MNC1/LAC1/RAC2 (RAI-4) and cell C in MCC1/MNC1/LAC1/RAC2 (RAI-4).
cells.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2150
Test procedure
from the SS. The UE performs a cell update within the routing area. The UE then waits for the ROUTING AREA
UPDATE ACCEPT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2151
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
cell".
(see note)
by the UE.
4 -> ATTACH REQUEST Attach result ='PS attach'
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
9 SS No response to the ROUTING AREA UPDATE
REQUEST message is given by the SS
received on cell C.
neighbour cell".
(see note)
12a -> CELL UPDATE

Cell update cause ='cell reselection'
12b <- CELL UPDATE CONFIRM
ACCEPT
P-TMSI-3 signature
COMPLETE

(see ICS).
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2152

None.
At step8, UE shall:
- initiate routing area update procedure.
At step12a, when a change of cell within a new routing area is performed, UE shall:
- perform the cell update before the routing area updating procedure is finished.
12.4.1.8 Routing area updating / abnormal cases / P-TMSI reallocation procedure
collision
When a P-TMSI REALLOCATION COMMAND message is received by the UE while waiting for a ROUTING
AREA UPDATE ACCEPT message, the UE shall ignore the P-TMSI reallocation procedure and continue with the
routing area updating procedure.
Reference
3GPP TS 24.008 clause 4.7.5.1.
Initial condition
System Simulator:
cells.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2153
Test procedure
The UE initiates a routing area updating procedure. The SS does not answer the routing area updating procedure, but
initiates a P-TMSI reallocation procedure. The UE shall ignore the P-TMSI reallocation procedure and continue with
the routing area updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2154
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
(see note)
by the UE.
4 -> ATTACH REQUEST Attach result ='PS attach'

CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-1 signature
10 <- P-TMSI REALLOCATION
COMMAND
P-TMSI-1 signature
11 UE The UE ignores the P-TMSI reallocation
command.
ACCEPT
P-TMSI-2 signature
COMPLETE

(see ICS).
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2155
At step9, UE shall:
- initiate the routing area updating procedure.
At step11, when a P-TMSI REALLOCATION COMMAND message is received from SS while waiting for a
ROUTING AREA UPDATE ACCEPT message, UE shall:
- ignore the P-TMSI reallocation procedure.
- continue with the routing area updating procedure.
12.4.2 Combined routing area updating
The combined routing area updating procedure is a GMM procedure used by PS UEs of UE operation mode A that are
IMSI attached for PS and non-PS services. In order to use the combined routing area updating procedure, the network
must operate in network operation mode I.
12.4.2.1 Combined routing area updating / combined RA/LA accepted
1) If the network accepts the combined routing area updating procedure and reallocates a P-TMSI, the UE shall
acknowledge the new P-TMSI and continue communication with the new P-TMSI.
2) If the network accepts the combined routing area updating procedure from the UE without reallocation of the old
P-TMSI, the UE shall continue communication with the old P-TMSI.
Reference
3GPP TS 24.008 clause 4.7.5.2.
To test the behaviour of the UE if the network accepts the combined routing area updating procedure.
1) P-TMSI / P-TMSI signature is reallocated.
3) Mobile terminating CS call is allowed with IMSI.
4) Mobile terminating CS call is allowed with TMSI.
Initial condition
System Simulator:
Both cells operating in network operation mode I.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2156
Test procedure
1) A combined PS attach procedure is performed. The UE sends a ROUTING AREA UPDATE REQUEST
message. The SS reallocates the P-TMSI, unassigns the TMSI and returns ROUTING AREA UPDATE
ACCEPT message with a new P-TMSI and IMSI. The UE acknowledge the new P-TMSI by sending ROUTING
AREA UPDATE COMPLETE message. Further communication UE - SS is performed by the new P-TMSI. For
CS calls, the IMSI is used
2) The UE is CS paged in order to verify that the IMSI is used for CS calls.
3) A combined PS attach procedure is performed. The UE sends an ROUTING AREA UPDATE REQUEST
message. The SS accepts the P-TMSI signature and returns ROUTING AREA UPDATE ACCEPT message
without any P-TMSI and with a new TMSI. The UE acknowledge the new TMSI by sending ROUTING AREA
UPDATE COMPLETE message. Further communication UE-SS is performed by the old P-TMSI. For CS calls,
the new TMSI is used.
4) The UE is CS paged in order to verify that the TMSI is used for CS calls.
Expected Sequence
UE SS
neighbour cell".
(see note)
1a UE The UE is set in UE operation mode A (see
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2157
UE SS
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature

COMPLETE

10b Void
10c Void

11b Void
call"
call".
14 Void
15 Void
18 Void
received on cell A.
neighbour cell".
(see note)
REQUEST
P-TMSI-1 signature
ACCEPT
No P-TMSI
P-TMSI-2 signature
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2158
UE SS
23b Void
23c Void

24b Void
call"
call".
27 Void
28 Void
31 Void
(see ICS).
PS / IMSI detach'

None.
- initiate the combined PS attach procedure with information elements specified in the above Expected Sequence.
- initiate the combined routing area update procedure(Update type ='Combined RA/LA updating') with the
information elements specified above Expected Sequence.
At step9, UE shall:
- acknowledge the new P-TMSI by sending the ROUTING AREA UPDATE COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2159
- acknowledge the new TMSI by sending the ROUTING AREA UPDATE COMPLETE message.
12.4.2.2 Combined routing area updating / UE in CS operation at change of RA
PS UE in UE operation mode A that is in an ongoing CS transaction at change of routing area shall initiate the normal
routing area updating procedure.
Reference
3GPP TS 24.008 clause 4.7.5.2.1
To test the behaviour of the UE if the routing area is changed during an ongoing circuit switched transmission.
Initial condition
System Simulator:
One cell, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) is operating in network operation mode I.
User Equipment:
Test procedure
A combined PS attach procedure is performed. The UE in UE operation mode A initiates a CS call. The routing area
change. The UE will perform the normal routing area updating procedure during the ongoing circuit-switched
transaction.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2160
Expected Sequence
UE SS
(see note)
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
6 UE A CS call is initiated.
7 Void
8 Void
8a <- UTRAN MOBILITY
INFORMATION
The SS conveys updated CN system
information for the PS domain to the UE in
connected mode, including a new routing area
code.
8b -> UTRAN MOBILITY
INFORMATION CONFIRM

REQUEST
P-TMSI-2 signature

ACCEPT
P-TMSI-1 signature
COMPLETE

11a SS The SS releases the PS signalling connection,
but keeps the RRC connection.

13b SS The SS releases the CS call.
14a -> ROUTING AREA UPDATE
REQUEST
Update type =combined RA/LA updating or
"combined RA/LA updating with IMSI Attach",
P-TMSI-1 signature,
Routing area identity =RAI-4,
14c <- ROUTING AREA UPDATE
ACCEPT
Update result ="combined RA/LA updated",
No P-TMSI,
P-TMSI-3 signature,
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2161
PS / IMSI detach'

UTRAN MOBILITY INFORMATION (step 8a)
The contents of the UTRAN MOBILITY INFORMATION message in this test case is identical to the default message
in TS 34.108, with the following exceptions.
UE Timers and constants in connected mode Not Present
CN information info
- PLMN identity Not Present
- CN common GSM-MAP NAS system information Not Present
- T3212 30
- ATT 1
- RAC RAC-2
- NMO 0 (Network Mode of Operation I)

At step9, when the UE has received the new RAI from the SS in the UTRAN MOBILITY INFORMATION message,
the UE shall:
- initiate the normal routing area updating procedure.
12.4.2.3 Combined routing area updating / RA only accepted
1) If the network accepts the combined PS attach procedure, but GMM cause code 'IMSI unknown in HLR' is sent
to the UE the User Equipment shall delete the stored TMSI, LAI and CKSN. The User Equipment shall consider
USIM invalid for non-PS services until power is switched off or USIM is removed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2162
2) If the network accepts the combined PS attach procedure, but GMM cause code 'MSC temporarily not
reachable', 'Network failure' or 'Congestion' is sent to the UE, an UE operation mode A UE may perform an MM
IMSI attach procedure.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Test porpose1
To test the behaviour of the UE if the network accepts the routing area updating procedure with indication RA only,
GMM cause 'IMSI unknown in HLR'.
Test porpose2
To test the behaviour of the UE if the network accepts the routing area updating procedure with indication RA only,
GMM cause 'MSC temporarily not reachable', 'Network failure' or 'Congestion'.
Test Procedure1
Initial condition
System Simulator:
Both cells operating in network operation mode I.
User Equipment:
Test procedure
After attach, the UE sends an ROUTING AREA UPDATE REQUEST message. The SS allocates a P-TMSI and returns
ROUTING AREA UPDATE ACCEPT message with a P-TMSI. GMM cause 'IMSI unknown in HLR' is indicated from
SS. Further communication UE - SS is performed by the P-TMSI. CS services are not possible.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2163
Expected Sequence
UE SS
cell".
(see note)
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
GMM cause ='IMSI unknown in HLR'
COMPLETE

COMPLETE


COMPLETE

(see ICS).
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2164

Test Procedure2
Initial condition
System Simulator:
Both cells operating in network operation mode I. T3212 is set to 6 minutes.
User Equipment:
Automatic MM IMSI attach procedure for UE operation mode A UE Yes/No
Test procedure
After attach, the UE sends an ROUTING AREA UPDATE REQUEST message . The SS allocates a new P-TMSI
signature and returns ROUTING AREA UPDATE ACCEPT message. GMM cause 'MSC temporarily not reachable',
'Network failure' or 'Congestion' is indicated from SS. The cause code is arbitrarily chosen. This procedure is repeated
until the routing area updating attempt counter is equal to five. An UE operation mode A UE may perform an MM IMSI
attach procedure (according to the ICS statement). Further communication UE - SS is performed by the P-TMSI. The
existence of a signalling channel is verified by a request for mobile identity. It is further verified that the UE after a
successful IMSI attach procedure can perform CS services.
Expected Sequence
Dependent whether the option 'Automatic MM IMSI attach procedure for UE operation mode A UE' is not supported or
not, the steps 1-13 or 14-35 apply depending on manufacturer (see ICS).
UE SS
received on cell A
cell".
(see note)
1a UE The UE is set in UE operation mode A and no
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2165
UE SS
P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
ACCEPT
Mobile identity =P-TMSI-1P-TMSI-1 signature
chosen)
COMPLETE

10 The routing area updating attempt counter =1.
The combined routing area updating procedure
is reinitialised at the expiry of T3311
REQUEST
Update type ='Combined RA/LA updating
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2166
UE SS
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

(see ICS).
Stop the sequence.
off.
received on cell B
29 UE The UE is set in UE operation mode A and
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2167
UE SS
neighbour cell ".
(see note)
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

REQUEST
with IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2168
UE SS
COMPLETE

REQUEST
IMSI attach'
P-TMSI-1 signature
ACCEPT
P-TMSI-1 signature
chosen)
COMPLETE

55 UE Registration on CS Optional step.
See TS 34.108
mode A.
Steps 56 - 62 are only performed if the UE has
performed the Registration Procedure in step
55.
COMPLETE

COMPLETE

(see ICS).
off.

None.
Test requirements for Test Procedure1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2169
- initiate the combined routing area updating procedure.
At step9, UE shall:
- acknowledge the new P-TMSI by sending the ROUTING AREA UPDATE COMPLETE message.
Test requirements for Test Procedure2
At step6 and 35, when the RF level of the attached cell is lower than the RF level of the new cell, UE shall:
- initiate the combined routing area updating procedure.
- re-initiate the combined routing area updating procedure.
- re-initiate the combined routing area updating procedure.
- perform MM location updating procedure.
12.4.2.3a Void
12.4.2.4 Combined routing area updating / rejected / PLMN not allowed
1) If the network rejects a combined routing area updating procedure from the User Equipment with the cause
'PLMN not allowed' the User Equipment shall:
1.1 not perform combined GPRS attach when switched on in the same location area or PLMN, except when the
PLMN identity is equal to the HPLMN.
1.2 delete the stored RAI, PS-CKSN, P-TMSI, P-TMSI signature, TMSI CKSN and LAI.
1.3 store the PLMN in the 'forbidden PLMN list', except when the PLMN identity is equal to the HPLMN.
2) An MS that receives a ROUTING AREA UPDATE REJ ECT message stops timer T3330, enters state MM IDLE
and for all causes except #12, #14 and #15 deletes the list of "equivalent PLMNs".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2170
Reference
3GPP TS 24.008 clause 4.7.5.2.
To test the behaviour of the UE if the network rejects the combined routing area updating procedure of the UE with the
cause 'PLMN not allowed'.
Initial condition
System Simulator:
Five cells (not simultaneously activated), cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell B in
MCC1/MNC2/LAC1/RAC2 (RAI-10), cell C in MCC1/MNC2/LAC2/RAC1 (RAI-9) and cell D in
MCC2/MNC1/LAC1/RAC1 (RAI-2), cell E in MCC1/MNC3/LAC1/RAC1 (RAI-11).
The PLMN containing Cell E is equivalent to the PLMN that contains Cell A.
All five cells are operating in network operation mode I
The HPLMN is different from MCC1/MNC2.
ii) Cell E will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.
User Equipment:
Test procedure
The SS rejects a combined routing area updating with the cause value 'PLMN not allowed'. The SS checks that the UE
does not perform PS attach if activated in the same PLMN. The SS checks that the UE does not perform IMSI attach if
activated in the same PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2171
Expected Sequence
UE SS
received on cell A.
cell".
cell".
cell".
cell".
(see note)
2a SS The SS verifies that the IE "Establishment
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-8 signature
Equivalent PLMN: MCC =1, MNC=3

received on cell B and cell E.
neighbour cell".
Set the cell type of cell E to the "Suitable
neighbour cell".
(see note)
REQUEST
Update type ='Combined RA/LA updating'Old
P-TMSI Signature=P-TMSI-8 signature
Valid TMSI is available.
present
REJ ECT
GMM cause ='PLMN not allowed'
10b Cell E is preferred by the UE
11 UE UE starts reqistration, see 34.108
12 SS The SS verifies that the IE "Establishment
12a -> ATTACH REQUEST Attach type ='Combined PS / IMSI attach'

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2172
UE SS
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-11 signature
18 <- PAGING TYPE1 Paging is sent on cell A.
Mobile identity=P-TMSI-11
P-TMSI-11 signature
Paging order for PS services
18a The UE shall not initiate an RRC connection.
19 <- PAGING TYPE1 Paging is sent on cell B.

21 Void
22 Void
23 Void
24 Void
25 Void
26 Void
received on cell D.
27 SS Set the cell type of cell B and E to the "Non-
Suitable cell".
(see note)
Step 28a and 29 are only performed by an UE
(see ICS)
28a
conditio
nal
UE Registration on CS See TS 34.108
UE.
29
conditio
nal
UE The UE initiates an attach by MMI or by AT
command.
Valid TMSI is available. Attach Request PDU
shall not carry
present
P-TMSI-2 signature
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2173
UE SS
PS / IMSI detach'
off.
NOTE: The definitions for "Non-Suitable cell", "Serving cell" and "Suitable neighbour cell" are specified

None.
- - initiate the combined routing area update procedure(Update type ='Combined RA/LA updating') with the
At step 10, the UE shall delete the equivalent PLMN list (MCC=1, MNC=3).
At step 12, the UE shall initiate a PS attach procedure to cell E.
12.4.2.5a Combined routing area updating / rejected / roaming not allowed in this
location area
1) If the network rejects a combined routing area updating procedure from the User Equipment with the cause
'roaming not allowed in this location area' the User Equipment:
1.1 shall not perform combined PS attach when in the same location area.
1.2 shall store the LA in the 'forbidden location areas for roaming'.
1.3 shall perform a routing area update when entering in a new location area if the LAI or the PLMN identity is
not contained in any of the lists "forbidden LAs for roaming", "forbidden LAs for regional provision of
service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" and the current update status is
different from "IDLE NO IMSI".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2174
2) The User Equipment shall reset the list of 'Forbidden location areas for roaming' when switched off or when the
USIM is removed.
Reference
3GPP TS 24.008 clause 4.7.5.2.
3GPP TS 23.122 clause 4.5.2.
Test purpose1
To test that on receipt of a rejection using the 'Roaming not allowed in this area' cause code, the UE ceases trying a
routing area updating procedure on that location area. Successful combined routing area updating procedure is possible
in other location areas.
Test purpose2
Initial condition
System Simulator:
Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B in MCC2/MNC1/LAC2/RAC1
(RAI-6, Not HPLMN).
User Equipment:
Test procedure
The SS rejects a combined routing area updating with the cause value 'Roaming not allowed in this area'. A new attempt
for a combined PS attach is not possible. Successful combined routing area updating procedure is performed in another
location area. The UE is moved back to the 1
st
location area. A combined routing area updating shall not be performed,
as the LA is on the forbidden list.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2175
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
7 SS Set the cell type of cell A to the "Non-suitable
cell".
(see note)
REQUEST
P-TMSI-2 signature
Mobile identiy =P-TMSI-2
9a SS SS starts integrity protection
REJ ECT
area'
11 Void
12 Void
received on cell A.
neighbour cell".
(see note)
18a Void
19 Void
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2176
UE SS
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

call"
conversational call".
25 Void
26 Void
29 Void
Paging cause ="Terminating background call"
background call".
30b Void
30c Void

31o SS The SS starts integrity protection.
31b Void

received on cell B.
neighbour cell".
(see note)
to SS

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2177
Initial condition
System Simulator:
Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B in MCC2/MNC1/LAC2/RAC1
(RAI-6, Not HPLMN).
User Equipment:
Test procedure
The SS rejects a combined routing area updating with the cause value 'Roaming not allowed in this area'. The UE is
switched off for 10 seconds and switched on again. The SS checks that a combined PS attach is possible on the cell on
which the previous combined routing area updating had been rejected.
If USIM removal is possible without switching off:
The SS rejects a routing area updating with the cause value 'Roaming not allowed in this area'. The USIM is removed
and inserted in the UE. The SS checks that a PS attach procedure and routing area updating procedure is possible on the
cell on which the routing area updating had previously been rejected.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2178
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
cell".
(see note)
REQUEST
P-TMSI-2 signature
9a SS The SS starts integrity protection
REJ ECT
area'
11 Void
12 Void
removed.
17a SS Set the cell type of cell A to the "Suitable
neighbour cell".
(see note)
or switched on.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2179
UE SS
UE.
UE.
19 UE The UE initiates an attach (see ICS) by MMI or
AT command.
Mobile identity =P-TMSI_2
Attach Request shall not carry TMSI status.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
call"
conversational call".
25 Void
26 Void
29 Void
Paging cause ="Terminating background call"
background call".
30b Void
30c Void

31o SS The SS starts integrity protection.
31b Void
(see ICS).
PS/IMSI detach'
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2180
None.
information elements specified above Expected Sequence
At step12, when the SS rejects the combined routing area update procedure with GMM cause ='Roaming not allowed
in this area', UE shall:
- not initiate a PS attach procedure.
- initiate the combined RA/LA updating procedure.

At step9, UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2181
12.4.2.5b Combined routing area updating / rejected / No Suitable Cells In Location
Area.
1) If the network rejects a combined routing area updating procedure from the User Equipment with the cause 'No
Suitable Cells In Location Area', the User Equipment shall:
1.1 store the LA or the PLMN identity in the 'forbidden location areas for roaming'.
2) An MS that receives a ROUTING AREA UPDATE REJ ECT message stops timer T3330, enters state MM IDLE
and for all causes except #12, #14 and #15 deletes the list of "equivalent PLMNs".
Reference
3GPP TS 24.008 clauses 4.7.5.2.4
To test the behaviour of the UE if the network rejects a combined routing area updating procedure of the UE with the
cause 'No Suitable Cells In Location Area'.
To test that the UE deletes the list of forbidden LAs when power is switched off'.
Initial condition
System Simulator:
Five cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC2/RAC1 (RAI-3), cell C
in MCC2/MNC1/LAC1/RAC1 (RAI-2), cell D in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell E in
All five cells are operating in network operation mode I.
The PLMN contains Cell A, B and D is equivalent to the PLMN that contains Cell E.
iii) Cell E will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.

User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2182
Test procedure
The SS rejects a combined routing area updating with the cause value 'No Suitable Cells In Location Area'. The SS
checks that the UE shall performa combined routing area update procedure when the UE enters a suitable cell in a
different location area on the same PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2183
Expected Sequence
UE SS
SS The following message are sent and shall be
received on cell D.
neighbour cell".
neighbour cell".
neighbour cell".
cell".
(see note)
initiates an attach (see ICS). Cell D is preferred
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
neighbour cell".
neighbour cell".
cell".
(see note)
follows.
Cell A is preferred by the UE.
REQUEST
P-TMSI-1 signature
REJ ECT
Area'
received on cell B.
REQUEST
Attach type ='Combined RA/LA updating with
IMSI attach'
ACCEPT
Attach result ='Combined RA/LA updating with
IMSI attach'
P-TMSI-2 signature
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2184
12 SS Set the cell type of cell D to the "Serving cell".
neighbour cell".
Set the cell type of cell E to the "Suitable
neighbour cell".
(note)
The SS deactivates Cell B and activates Cell D
and Cell E
follows.
Cell D >Cell E
13 Cell D is preferred by the UE.
REQUEST
P-TMSI-1 signature
REJ ECT
Area'
16 The following message are sent and shall be
received on cell E.
REQUEST
Attach type ='Combined RA/LA updating with
IMSI attach'
ACCEPT
Attach result ='Combined RA/LA updated'
P-TMSI-3 signature
Equivalent PLMN: MCC=1. MNC=2
COMPLETE

off.
NOTE: The definitions for "Suitable neighbour cell", "Serving cell" and "Non-Suitable cell" are specified

None.
- initiate the Combined PS attach procedure with the information elements specified in the above Expected
Sequence.
- initiate the combined routing area update procedure.
At step 8, the UE shall maintain the equivalent PLMN list (MCC=1, MNC=2).
- perform the combined routing area update procedure.
At step 15, the UE shall maintain the equivalent PLMN list (MCC=1, MNC=2).
At step 17, when the UE enters a suitable cell in a different but equivalent PLMN (MCC=1, MNC=2), UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2185
- perform the combined routing area update procedure.
12.4.2.5c Combined routing area updating / rejected / Location area not allowed
If the network rejects a combined routing area updating procedure from the User Equipment with the cause 'Location
area not allowed', the User Equipment shall:
- set the PS update status to GU3 ROAMING NOT ALLOWED.
- delete any TMSI, LAI and ciphering key sequence number.
- store the LAI in the list of "forbidden location areas for regional provision of service"
- not delete the list of "equivalent PLMNs".
- perform a cell selection.
Reference
3GPP TS 24.008 clauses 4.7.5.2.4
Initial condition
System Simulator:
All three cells are operating in network operation mode I (in case of UE operation mode A).
User Equipment:
Test procedure
The SS rejects a combined routing area updating with the cause value 'Location area not allowed'. The SS checks that
the UE performs combined PS attach when the UE enters a equivalent PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2186
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
REJ ECT
GMM cause =Location area not allowed '
command.
cell".
Set the cell type of cell B to the " Non-Suitable
cell".
(see note)
14 UE The UE performs cell selection.
received on cell C.
P-TMSI-2 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2187
(see ICS).
off.

None.
Sequence.
At step8, UE shall:
At step 12, the UE shall:
- not initiate combined PS attach procure.
- perform combined PS attach procedure with Mobile identity =IMSI and Attach result ='Combined PS / IMSI
attached' to the equivalent cell.
12.4.2.5d Combined routing area updating / rejected / PS services not allowed in this
PLMN
If the network rejects a combined routing area updating procedure from the User Equipment with the cause 'PS Services
not allowed in this PLMN', the User Equipment shall:
- set the PS update status to GU3 ROAMING NOT ALLOWED.
- store the PLMN identity in the "forbidden PLMNs for GPRS service" list.
- not delete the list of "equivalent PLMNs".
Reference
3GPP TS 24.008 clauses 4.7.5.2.4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2188
Initial condition
System Simulator:
All three cells are operating in network operation mode I (in case of UE operation mode A).
ii) Cell C will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.
User Equipment:
Test procedure
The SS rejects a combined routing area updating with the cause value 'PS service not allowed in this PLMN'. The SS
checks that the UE performs combined PS attach when the UE enters a equivalent PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2189
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
REJ ECT
GMM cause ='PS service not allowed in this
PLMN'
command.
cell".
Set the cell type of cell B to the " Non-Suitable
cell".
(see note)
received on cell C.
P-TMSI-2 signature
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2190
off.

None.
Sequence.
At step8, UE shall:
- not initiate combined PS attach procure.
- perform combined PS attach procedure with Mobile identity =IMSI and Attach result ='Combined PS / IMSI
attached' to the equivalent cell.
12.4.2.6 Combined routing area updating / abnormal cases / access barred due to
access class control
1) The UE shall not perform combined routing area updating procedure, but stays in the current serving cell and
applies normal cell reselection process.
2) The User Equipment shall perform the combined routing area updating procedure when:
2.1 Access is granted.
2.2 Cell is changed.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Test purpose1
To test the behaviour of the UE in case of access class control (access is granted).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2191
Test purpose2
To test the behaviour of the UE in case of access class control (cell is changed).
Initial condition
User Equipments using access class x is initially indicated to be barred on Cell B.
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) has Access Class x not
barred, cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4) has Access Class x barred.

User Equipment:
The UE has valid IMSI. UE is Idle Updated on cell A.
Test procedure
A PS attach procedure is performed. The routing area is changed. The SS indicates access class x barred. A routing area
updating procedure is not performed.
The SS indicates that access class x is not barred. A routing area updating procedure is performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2192
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
to SS, as access class x is barred
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2193
Initial condition
User Equipments using access class x is indicated to be barred on cell B.
System Simulator:
Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) has access class x not
barred, cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4) has access class x barred, cell C in
MCC1/MNC1/LAC1/RAC2 (RAI-4) has access class x not barred.
User Equipment:
Test procedure
A PS attach procedure is performed. The routing area is changed. The SS indicates access class x barred. A routing area
updating procedure is not performed.
A cell change is performed into a cell where access class x is not barred. A routing area updating procedure is
performed.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2194
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell ".
(see note)
to SS, as access class x is barred

received on cell C.
neighbour cell ".
(see note)
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2195

None.
At step8, when the access class x is barred , UE shall:
- not perform the combined routing area updating procedure.
At step10, when the access class x is not barred, UE shall:
- perform the combined routing area updating procedure.
At step8, when the access class x is barred UE shall:
- not perform the combined routing area updating procedure.
At step11, when the serving cell is changed, UE shall:
- perform the combined routing area updating procedure.
12.4.2.7 Combined routing area updating / abnormal cases / attempt counter check /
procedure timeout
1) When a T3330 timeout has occurred during a routing area updating procedure, the UE shall repeat the routing
area updating procedure after T3330 timeout until the procedure is repeated five times.
2) When a routing area updating procedure is repeated five times, the routing area updating attempt counter is
incremented and five more routing area updating procedures are performed. This procedure is repeated until the
routing area updating attempt counter is five, the UE shall then start timer T3302.
3) When the T3302 expire, a new routing area updating procedure shall be initiated.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2196
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE initiates a routing area updating procedure (routing area updating attempt counter zero). The SS does not
answer with ROUTING AREA UPDATE ACCEPT message before T3330 timeout. The UE restarts the routing area
updating procedure four times. The SS never answers with ROUTING AREA UPDATE ACCEPT message before
T3330 timeout. After five consecutive routing area update procedures, the routing area updating attempt counter is
incremented and T3311 is started.
The UE initiates a new routing area updating procedure (routing area updating attempt counter one) after T3311
expires. The SS does not answer with ROUTING AREA UPDATE ACCEPT message before T3330 timeout. The UE
restarts the routing area updating procedure four times. The SS never answers with ROUTING AREA UPDATE
ACCEPT message before T3330 timeout. After five consecutive routing area update procedures, the routing area
updating attempt counter is incremented and T3311 is started.
The UE initiates a new routing area updating procedure (routing area updating attempt counter two) after T3311
The UE initiates a new routing area updating procedure (routing area updating attempt counter three) after T3311
The UE initiates a new routing area updating procedure (routing area updating attempt counter four) after T3311
updating attempt counter is incremented and as the routing area updating attempt counter is five. T3302 is started.
The UE may perform a Location Update procedure.
The UE initiates a routing area updating procedure with routing area updating attempt counter zero after T3302 expires
with the stored P-TMSI, P-TMSI signature, PS CKSN and RAI.
T3311; 15 seconds.
T3330; 15 seconds.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2197
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
cell".
(see note)
K =1.
REQUEST
P-TMSI-2 signature
Routing area updating attempt counter =k (k is
not visible. It is only used for clarifying the
sequence.)
Retransmission counter =0
10 SS The SS verifies that the time between the RA
update requests is T3330seconds
REQUEST
P-TMSI-2 signature
Routing area updating attempt counter =k
REQUEST
P-TMSI-2 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2198
UE SS
REQUEST
P-TMSI-2 signature
20 -> ROUTING AREA UPDATING
REQUEST
P-TMSI-2 signature
update requests is T3311 +T3330 seconds.
23 SS Step 8 22 is repeated four times with k =2, k
=3, k =4 and k =5
23a
optional
UE Registration on CS The UE may perform a normal location
updating procedure.
See TS 34.108
update requests is T3302 +T3330 seconds
REQUEST
Update type =
- 'combined RA/LA updating with IMSI attach'
(If Step23a is performed)
- 'combined RA/LA updating'
(If Step23a is not performed)
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2199
- initiate the combined routing area updating procedure with information elements specified in the above Expected
Sequence.
Case 1) A timer T3330 timeout has occurred during a combined routing area updating procedure with the
Routing area attempt counter less than five and the Retransmission counter less than five
- repeat the combined routing area updating procedure after the timer T3330 timeout
Case2) A timer T3330 timeout has occurred during a combined routing area updating procedure with the
Routing area attempt counter less than five and the Retransmission counter five
At step 22, UE shall:
- not repeat the combined routing area updating procedure.
Case 3) A timer T3311 timeout has occurred and the Routing area attempt counter is less than five,
- repeat the combined routing area updating procedure
Case 4) A timer T3330 timeout has occurred during a combined routing area updating procedure with the
Routing area attempt counter five and the Retransmission counter five.
- not initiate a routing area updating procedure.
Case5) The timer T3302 expires
- initiate the new routing area updating procedure
12.4.2.8 Combined routing area updating / abnormal cases / change of cell into new
routing area
When a change of cell into a new routing area is performed before the routing area updating procedure is finished, the
UE shall abort the routing area updating procedure and re-initiate it in the new routing area.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Initial condition
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2200
User Equipment:
Test procedure
from the SS. The UE performs a cell update into a new routing area. The UE shall re-initiate a routing area updating
procedure in the new routing area. The UE shall not increment the attempt counter.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2201
Expected Sequence
UE SS
received on cell A.
neighbour cell".
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
9 SS No response id given from the SS.
received on cell C.
neighbour cell".
(see note)
11 UE The RF level of cell B is lowered, and the RF
level of cell C is increased, until cell C is
preferred by the UE.
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2202
off.

None.
Sequence.
At step12, when change of cell into new routing area is performed before the routing area updating procedure is
finished, UE shall:
- abort the routing area updating procedure.
- re-initiate new routing area updating procedure in the new routing area.
12.4.2.9 Combined routing area updating / abnormal cases / change of cell during
routing area updating procedure
When a change of cell within new routing area is performed before the routing area updating procedure is finished, the
UE shall perform the cell update before the routing area updating procedure is finished.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2203
Test procedure
from the SS. The UE performs a cell update within the routing area. The UE then waits for the ROUTING AREA
UPDATE ACCEPT message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2204
Expected Sequence
UE SS
received on cell A.
neighbour cell".
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
9 SS No response id given from the SS.
received on cell C.
neighbour cell".
(see note)
11 UE The RF level of cell B is lowered until cell C is
preferred by the UE.
12a -> CELL UPDATE Cell update cause ='cell reselection'
12b <- CELL UPDATE CONFIRM
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2205

None.
Sequence.
At step12a, when a change of cell within a new routing area is performed before the routing area updating procedure is
finished, UE shall:
- perform the cell update.
12.4.2.10 Combined routing area updating / abnormal cases / PS detach procedure
collision
1) When a detach request is received with cause 'PS detach' or 'combined PS/IMSI detach' by the UE while waiting
for a ROUTING AREA UPDATE ACCEPT message, the UE shall terminate the routing area updating
procedure and continue with the PS detach procedure.
2) When a detach request is received with cause 'IMSI detach' by the UE while waiting for a ROUTING AREA
UPDATE ACCEPT message, the UE shall ignore the detach request and continue with the routing area updating
procedure.
Reference
3GPP TS 24.008 clause 4.7.5.2.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2206
Test procedure
initiates a PS detach procedure with cause 'PS detach' or 'combined PS/IMSI detach'. The UE shall terminate the routing
area updating procedure and continue with the PS detach procedure.
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
9 SS The SS ignores the ROUTING AREA UPDATE
REQUEST message and initiates a detach
procedure.
11 -> DETACH ACCEPT

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2207
Initial condition
System Simulator:
User Equipment:
The UE has a valid P-TMSI and RAI.
Test procedure
initiates a PS detach procedure with cause 'IMSI detach'. The UE shall ignore the detach procedure and continue with
the routing area updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2208
Expected Sequence
UE SS
received on cell A.
neighbour cell".
(see note)
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature

received on cell B.
neighbour cell".
(see note)
REQUEST
P-TMSI-2 signature
9 SS The SS ignores the ROUTING AREA UPDATE
REQUEST message and initiates a detach
procedure.
10 <- DETACH REQUEST Detach type ='IMSI detach'
message and continue the routing area
updating procedure.
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
PS/IMSI detach'
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2209
None.
Sequence.
At step11, when the UE receives a DETACH REQUEST message with cause 'PS detach' or 'combined PS/IMSI detach'
from SS while waiting for a ROUTING AREA UPDATE ACCEPT message, UE shall:
- terminate the routing area updating procedure
- continue with the PS detach procedure.
Sequence.
At step11, the UE receives a DETACH REQUEST message with cause 'IMSI detach' from SS while waiting for a
ROUTING AREA UPDATE ACCEPT message, UE shall:
- ignore the detach request procedure.
- continue with the routing area updating procedure.
12.4.3 Periodic routing area updating
12.4.3.1 Periodic routing area updating / accepted
The User Equipment shall perform a periodic routing area update procedure after a T3312 timeout.
Reference
3GPP TS 24.008 clauses 4.7.2.2 and 4.7.5.1.
To test the behaviour of the UE with respect to the periodic routing area updating procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2210
Initial condition
System Simulator:
One cell operating in network operation mode II (in case of UE operation mode A).
User Equipment:
Test procedure
The UE initiates a PS attach procedure with identity P-TMSI. The SS reallocates the P-TMSI and returns ATTACH
ACCEPT message with a new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH
COMPLETE message. A routing area updating procedure is performed at T3312 timeout.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2211
Expected Sequence
UE SS
1 SS The UE is set in UE operation mode C (see
goto step 11.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3312 =6 minutes
5b SS SS checks that the IE "Establishment cause" in
REQUEST
P-TMSI-2 signature
attach and the periodic RA updating is T3312
ACCEPT
P-TMSI-3 signature
(see ICS).
11 The SS is set in network operation mode II.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2212
At step6, when the timer T3312 is expired, UE shall:
- initiate the routing area updating procedure with Update type ='Periodic updating'.
12.4.3.2 Periodic routing area updating / accepted / T3312 default value
The User Equipment shall perform a periodic routing area update procedure after a T3312 timeout.
Reference
Initial condition
System Simulator:
User Equipment:
Test procedure
The UE initiates a combined PS attach procedure. The SS reallocates the P-TMSI and returns ATTACH ACCEPT
message with a new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH
COMPLETE message. After 54 minutes, a periodic routing area updating procedure is initiated by the UE.
T3312; default value 54 minutes.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2213
Expected Sequence
UE SS

CIPHERING REQUEST

CIPHERING RESPONSE

3 <- ATTACH ACCEPT Attach result ='Combined PS /IMSI attached'
P-TMSI-2 signature
T3312 =54 min
REQUEST
P-TMSI-2 signature
present.
attach request and the periodic RA updating is
T3312
ACCEPT
P-TMSI and TMSI not included.
Update result ='RAupdated'
P-TMSI-3 signature
(see ICS).
PS/IMSI detach'
off.

None.
At step5, when the timer T3312 is expired, UE shall:
- initiate the routing area updating procedure with Update type ='Periodic updating'.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2214
12.4.3.3 Periodic routing area updating / no cell available / network mode I
If the UE is both IMSI attached for PS and non-PS services, and if the UE lost coverage of the registered PLMN and
timer T3312 expires; if the UE returns to coverage in a cell that supports PS and the network is in network operation
mode I, then theUE shall perform a combined routing area update procedure indicating 'combined RA/LA updating
with IMSI attach'.
Reference
Initial condition
System Simulator:
Cell A is operating in network operation mode II and cell B is in network operation mode I.
User Equipment:
Idle updated on Cell A
Test procedure
The UE initiates a PS attach procedure. The SS reallocates the P-TMSI and returns ATTACH ACCEPT message with a
new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH COMPLETE message. PS
radio contact is distorted before T3312 timeout. PS radio contact is established again (after T3312 timeout), and a
routing area updating procedure is performed immediately.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2215
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
2 SS The UE is set in UE operation mode A (see
ICS).
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3312 =6 minutes
7 SS After 5 minutes, the signal strength is lowered
until the UE has lost contact with the SS.
Set the cell type of cell A to the "non-suitable
cell".(see note)
8 SS Wait 2 minutes.

received on cell B.
(see note)
11 UE The UE immediately starts a combined RA
updating procedure
REQUEST
IMSI attach'
P-TMSI-2 signature
TMSI status IE is omitted.
ACCEPT
P-TMSI-3 signature
COMPLETE

(see ICS).
PS / IMSI detach'
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2216
None.
At step12, when the UE is both IMSI attached for PS and non-PS service , and if the UE lost coverage of the reiterated
PLMN and the timer T3312 expires, if the UE returns to coverage in a cell that supports PS and the network is in
network oration mode I, UE shall:
12.4.3.4 Periodic routing area updating / no cell available
If the UE is both IMSI attached for PS and non-PS services, and if the UE lost coverage of the registered PLMN and
timer T3312 expires; if the UE returns to coverage in a cell that supports PS and the network is in network operation
mode II, then theUE shall perform a periodic routing area update procedure and a periodic location update procedure.
Reference
Initial condition
System Simulator:
User Equipment:
Idle updated on Cell A
Test procedure
The UE initiates a PS attach procedure. The SS reallocates the P-TMSI and returns ATTACH ACCEPT message with a
new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH COMPLETE message. PS
radio contact is distorted before T3312 timeout. PS radio contact is established again (after T3312 timeout), and a
periodic routing area updating procedure is performed immediately (no periodic location update procedure is performed
as T3212=infinity).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2217
Expected Sequence
UE SS
mode A.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3312 =6 minutes
5-12 (void)
13 SS After 5 minutes, the signal strength is lowered
until the UE have lost contact with the SS.
14 SS After 2 minutes, the signal strength is increased
until the UE have got contact with the SS.
15 UE The UE immediately start the periodic RA
updating procedure
REQUEST
P-TMSI-2 signature
ACCEPT
Update result ='RAupdated'
P-TMSI-3 signature
(see ICS).
18a IMSI DETACH INDICATION Message not sent if power is removed
mode A.
off.

RRC System information block type 1
Information element Comment Value
T3212 (Periodical Location updating) Infinity

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2218
At step16, when the UE is both IMSI attached for PS and non-PS service, and if the UE lost coverage of the reiterated
PLMN and the timer T3312 expires, if the UE returns to coverage in a cell in the same RA that supports PS and that
indicates that the network is in network operation mode II, UE shall:
- perform the periodic routing area updating procedure indicating "Periodic updating".
12.5 P-TMSI reallocation
12.5.1 Definition
1) A User Equipment shall acknowledge a new P-TMSI when explicitly allocated.
2) The P-TMSI shall be updated on the USIM when the User Equipment is correctly deactivated in accordance with
the manufacturer's instructions.
3) A User Equipment shall use the given P-TMSI in further communication with the network.
Reference
3GPP TS 24.008 clause 4.7.6.
12.5.3 Test purpose
To verify that the UE is able to receive and acknowledge a new P-TMSI by means of an explicit P-TMSI reallocation
procedure.
To verify that the UE has stored the P-TMSI in a non-volatile memory.
The implicit reallocation procedure is tested in the attach procedure.
Initial condition
System Simulator:
User Equipment:
UE operation mode C Yes/No (only if mode A not supported)
Test procedure
An explicit P-TMSI reallocation procedure is performed (P-TMSI reallocation command sent from the SS and
acknowledged from the UE by P-TMSI reallocation complete). The UE is PS detached and switched off. Its power
supply is interrupted for 10 seconds. The power supply is resumed and then the UE is switched on. A PS attach
procedure is performed with the given P-TMSI as identity.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2219
Expected Sequence
UE SS
ICS). If UE operation mode A not supported set
the UE in operation mode C.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
6 <- P-TMSI REALLOCATION
COMMAND
P-TMSI-2 signature
7 -> P-TMSI REALLOCATION
COMPLETE

(see ICS).
10 UE Ensure the power is removed from the UE for at
least 10 seconds
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-3 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2220
16 Void
17 Void

20 Void
(see ICS).

None.
At step7, when the UE receives P-TMSI REALLOCATION COMMAND message from SS, UE shall:
- acknowledge the new P-TMSI by sending P-TMSI REALLOCATION COMPLETE message.
12.6 PS authentication
12.6.1 Test of authentication
The purpose of this procedure is to verify the user identity. A correct response is essential to guarantee the
establishment of the connection. If not, the connection will drop.
12.6.1.1 Authentication accepted
A User Equipment shall correctly respond in an authentication and ciphering procedure by sending a response with the
RES information field set to the same value as the one produced by the authentication and ciphering algorithm in the
network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2221
Reference
3GPP TS 24.008 clause 4.7.7.
To test the behaviour of the UE if the network accepts the authentication and ciphering procedure.
Initial condition
System Simulator:
prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A) in both cells.
User Equipment:
Test procedure
A PS attach is performed, and the SS initiates an authentication and ciphering procedure.
The SS checks the value RES sent by the UE in the AUTHENTICATION AND CIPHERING RESPONSE message.
The UE initiates a routing area updating procedure and the SS checks the value of the PS Ciphering Key Sequence
Number sent by the UE in the ROUTING AREA REQUEST message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2222
Expected Sequence
UE SS
received on cell A.
cell".
(see note)
goto step 17.
CIPHERING REQUEST
Set PS-CKSN-1
CIPHERING RESPONSE
RES
7 SS The SS checks the RES value and starts
integrity protection.
P-TMSI-2 signature
received on cell B.
cell".
(see note)
REQUEST
P-TMSI-2 signature
PS-CKSN-1
12 SS The value of PS-CKSN is checked. Integrity
protection is started.
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
off.
cell".
(see note)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2223
step 16a.

None.
At steps 3a and 10a the UE shall transmit an RRC CONNECTION REQUEST message with the IE "Establishment
cause" set to "Registration".
At step6, when the UE receives the AUTHENTICATION AND CIPHERING REQUEST message form SS, UE shall:
- send the AUTHENTICATION AND CIPHERING RESPONSE message with the RES information field set to
the same value as the one produced by the authentication and ciphering algorithm in the network.
12.6.1.2 Authentication rejected by the network
Upon receipt of an AUTHENTICATION AND CIPHERING REJ ECT message, the UE shall set the PS update status to
GU3 ROAMING NOT ALLOWED and shall delete the P-TMSI, P-TMSI signature, RAI and PS ciphering key
sequence number stored.
The USIM shall be considered as invalid until switching off or the USIM is removed.
If the AUTHENTICATION AND CIPHERING REJ ECT message is received, the UE shall abort any GMM procedure,
shall stop the timers T3310 and T3330 (if running) and shall enter state GMM-DEREGISTERED.
Reference
3GPP TS 24.008 clauses 4.7.7.5.
To test the behaviour of the UE if the network rejects the authentication and ciphering procedure.
Initial condition
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2224
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" in
both cells.
User Equipment:
Test procedure
The test sequence is repeated for K =1, 2.
A complete PS attach procedure is performed. The SS rejects the following authentication and ciphering procedure. The
UE is paged with its IMSI and shall not respond.
The Cell is changed into a new Routing Area.
The SS checks that the UE does not perform normal routing area updating.
The SS then checks that the UE does not perform a PS detach.
The SS checks that the UE does not perform a PS Attach procedure.
Expected Sequence
The test sequence is repeated for k =1, 2
For k =1, the UE is set in UE operation mode C. If MS operation mode C not supported then k =2.
For k =2 the UE is set in UE operation mode A.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2225
UE SS
received on cell A.
cell".
(see note)
2a Void
2b SS SS checks that the IE "Establishment cause" in
4 Void
5 Void
CIPHERING REQUEST
Set PS-CKSN-1
CIPHERING RESPONSE
RES
CIPHERING REJ ECT

received on cell B.
cell".
(see note)
12 UE Cell B is preferred by the MS.
to the SS
14 UE If possible (see ICS) the UE initiates an attach
by MMI or by AT command.
17 SS No DETACH REQUEST sent to the SS
18 The UE is powered up or switched on and
Step 19 is only performed for k =2
19 UE Registration on CS Parameter mobile identity is IMSI
See TS 34.108
20 -> ATTACH REQUEST Attach type ='PS only attached'
CIPHERING REQUEST

CIPHERING RESPONSE

21 <- ATTACH ACCEPT Attach result ='PS attach'
P-TMSI-1 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2226
23 UE The UE is switched off or power is removed.
(see ICS)
25 UE If k=1 then the test is repeated for k=2.
NOTE: The definitions for "Non-Suitable celll" and "Serving cell" are specified in TS34.108 clause 6.1

None.
At step9, when the UE receives the AUTHENTICATION AND CIPHERING REJ ECT message, UE shall:
- not respond paging message for PS domain.
- not perform normal routing area updating.
- not perform PS detach procedure.
12.6.1.3 Authentication rejected by the UE
12.6.1.3.1 GMM cause 'MAC failure'
If the UE considers the MAC code (supplied by the core network in the AUTN parameter) to be invalid, the UE shall
send AUTHENTICATION AND CIPHERING FAILURE message with the reject cause 'MAC failure' to the System
Simulator.
Reference
3GPP TS 24.008 clause 4.7.7.
To test the behaviors of the UE, when the UE considers the MAC code (supplied by the core network in the AUTN
parameter) to be invalid.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2227
Initial condition
System Simulator:
cells.
The MAC (Message Authentication Code) code, which is included in AUTHENTICATION AND CIPHERING
REQUEST, is invalid value.
User Equipment:
Test procedure
The UE sends AUTHENTICATION AND CIPHERING FAILURE message with reject cause 'MAC failure' to the SS.
The SS initiates an identification procedure, upon receipt of a failure message with reject cause 'MAC failure'.
After the identification procedure is complete, the SS re-initiates an authentication and ciphering procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2228
Expected Sequence
UE SS
received on cell A.
cell".
(see note 1)
ICS). If UE operation mode C is not supported,
goto step 25.
3 UE
4 The following messages are sent and shall be
received on cell A.
Mobility identity =IMSI
CIPHERING REQUEST
Invalid Message Authentication Code (MAC).

CIPHERING FAILURE
GMM cause='MAC failure'
9a <- IDENTITY REQUEST Identity type =IMSI
9b -> IDENTITY RESPONSE Mobile identity =IMSI
CIPHERING REQUEST
Including PS-CSKN-1
CIPHERING RESPONSE
RES
13 Void
14 Void
15 Void
P-TMSI-2 signature
received on cell B.
cell".
(see note 1)
REQUEST
P-TMSI-2 signature
PS-CKSN-1
20 SS The SS checks the value of PS-CKSN and
starts integrity protection.
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2229
24 -> DETACH REQUEST Message is not sent if power is removed.
off.
step 24.

None.
- initiate the PS attach procedure with information element specified in the above Expected Sequence.
At step9, when the UE receives the AUTHENTICATION AND CIPHERING REQUEST with Invalid Message
Authentication Code, UE shall:
- send the AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'MAC failure' to the SS
At step11, when the UE receives the second AUTHENTICATION AND CIPHERING REQUEST message (containing
a valid MAC) from SS, UE shall:
- send the AUTHENTICATION AND CIPHERING RESPONSE message to SS.
At step9b, when the UE receives the IDENTITY REQUEST message with Identity type =IMSI from SS, UE shall:
- send the IDENTITY RESPONSE message with Mobile identity =IMSI to SS.
12.6.1.3.2 GMM cause 'Synch failure'
If the UE considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, the UE shall
send AUTHENTICATION AND CIPHERING FAILURE message with the reject cause 'Synch failure' to the System
Simulator.
Reference
3GPP TS 24.008 clause 4.7.7.
To test the behaviors of the UE, when the UE considers the SQN (supplied by the core network in the AUTN
parameter) to be out of range.
Initial condition
System Simulator:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2230
cells.
User Equipment:
Test procedure
UE sends AUTHENTICATION AND CIPHERING FAILURE message with reject cause 'synch failure' to the SS.
SS re-initiates an authentication and ciphering procedure.
Expected Sequence
UE SS
received on cell A.
cell".
(see note 1)
goto step 21.
received on cell A.
CIPHERING REQUEST
SQN is out of range.
6 Void
CIPHERING FAILURE
GMM cause ='Synch failure'
AUTS parameter
8 SS set new authentication vectors. (re-
synchronisation)
CIPHERING REQUEST
Including PS-CKSN-1
CIPHERING RESPONSE
RES
P-TMSI-2 signature
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2231
UE SS
received on cell B.
cell".
(see note 1)
REQUEST
P-TMSI-2 signature
PS-CKSN-1
16 SS The SS checks the value of PS-CKSN and
starts integrity protection
ACCEPT
P-TMSI-1 signature
COMPLETE

(see ICS).
20 -> DETACH REQUEST Message is not sent if power is removed.
off.
step 20.
NOTE: The definitions for "Non-Suitable cell" and "Serving cell" are specified in TS34.108 clause6.1

None.
- initiate the PS attach procedure with information element specified in the above Expected Sequence.
At step7, when the UE receives the AUTHENTICATION AND CIPHERING REQUEST message(SQN is out of
range.), UE shall:
- send the AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'synch failure' to the
SS
At step9, when the UE receives the second AUTHENTICATION AND CIPHERING REQUEST message from SS, UE
shall:
- send the AUTHENTICATION AND CIPHERING RESPONSE message to SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2232
12.6.1.3.3 Authentication rejected by the UE / fraudulent network
R99 and REL-4:
- After sending the AUTHENTICATION & CIPHERING FAILURE message with GMM cause 'MAC failure'
the timer T3318 expires;
- Upon receipt of the second AUTHENTICATION & CIPHERING REQUEST message from the network
while the T3318 is running and the MAC value cannot be resolved.
When it has been deemed by the MS that the source of the authentication challenge is not genuine
(authentication not accepted by the MS), the MS shall behave as described in 3GPP 24.008 clause 4.7.7.6.1.
2. In addition to the cases specified in subclause 4.7.7.6, the UE may deem that the network has failed the
authentication check after any combination of three consecutive authentication failures, regardless whether
'MAC failure', 'invalid SQN', or 'GSM authentication unacceptable' was diagnosed. The authentication failures
shall be considered as consecutive only, if the authentication challenges causing the second and third
authentication failure are received by the UE, while the timer T3318 or T3320 started after the previous

If the UE deems that the network has failed the authentication check, then it shall request RR or RRC to release
and 3GPP TS 04.18).
Reference
3GPP TS 24.008 clause 4.7.7.6 (f) and 4.7.7.6.1.
the UE) if any of the following occurs:
- after sending the AUTHENTICATION & CIPHERING FAILURE message with GMM cause 'MAC failure'
the timer T3318 expires;
- the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM
authentication unacceptable", during three consecutive authentication challenges. The authentication
challenges shall be considered as consecutive only, if the authentication challenges causing the second and
third authentication failure are received by the MS, while the timer T3318 or T3320 started after the
previous authentication failure is running.
When it has been deemed by the MS that the source of the authentication challenge is not genuine
(authentication not accepted by the MS), the MS shall behave as described in 3GPP TS 24.008 subclause
4.7.7.6.1.
2. If the UE deems that the network has failed the authentication check, then it shall request RR or RRC to release
and 3GPP TS 44.018).
Reference
3GPP TS 24.008 clause 4.7.7.6 (f) and 4.7.7.6.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2233
R99 and REL-4
1. when the network sends the second or third AUTHENTICATION & CIPHERING REQUEST message with
invalid MAC code during the timer T3318 is running.
REL-5 or later release:
1. when the network sends the third AUTHENTICATION & CIPHERING REQUEST message with invalid
MAC code during the timer T3318 is running.
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1(RAI-1), cell B in
MCC1/MNC1/LAC1/RAC2(RAI-2).
cells.
User Equipment:
Test procedure
Two cells are configured. Cell A transmits with higher power so that the UE attempts an attach procedure to cell A.
During the attach procedure, the SS initiates an authentication and ciphering procedure but it sends an incorrect
Message Authentication Code (MAC) value in its AUTHENTICATION AND CIPHERING REQUEST message.
The UE sends AUTHENTICATION AND CIPHERING FAILURE message to the SS indicating authentication failure.
The SS repeats a second time the authentication procedure, again with an incorrect Message Authentication Code
(MAC) value in its AUTHENTICATION AND CIPHERING REQUEST message.
For R99 and REL-4: SS waits 30 seconds. If the UE sends an AUTHENTICATION AND CIPHERING FAILURE
message during this time then the the SS repeats the authentication procedure a third time and then waits 30 seconds.
The UE moves into idle mode and do not make any access attempt on Cell A.
For REL-5 or later relaese: The SS repeats a third time the authentication procedure, again with an incorrect Message
Authentication Code (MAC) value in its AUTHENTICATION AND CIPHERING REQUEST message. The UE
moves into idle mode and do not make any access attempt on Cell A.
The UE shall attempt to attach to cell B. The SS initiates an authentication and ciphering procedure but it sends an
incorrect Message Authentication Code (MAC) value in its AUTHENTICATION AND CIPHERING REQUEST
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2234
message. The UE sends AUTHENTICATION AND CIPHERING FAILURE message to the SS indicating
authentication failure.
The SS waits for T3318 to expire.
The UE shall treat now both cells as barred and shall not attempt to access the network, even if the user triggers the UE
to perform an attach procedure.
Expected Sequence
UE SS

cell".
(see note)
received on cell A.
initiates an attach procedure.
CIPHERING REQUEST
Request for authentication.
CIPHERING FAILURE
CIPHERING REQUEST
CIPHERING FAILURE
R99 and REL-4: In case message is not
received within 30s then SS should continue
from step 9.
CIPHERING REQUEST
7b Void
8 SS SS verifies that the UE does not attempt to
access the network for 30s.
cell".
(see note)
UE shall attempt an attach on cell B.
received on cell B.
command.
CIPHERING REQUEST
CIPHERING FAILURE
14 SS SS waits T3318 (20s)
command.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2235
None.
At step3, when the UE is powered on or switched on, the UE shall:
After step4, when the UE have received the first AUTHENTICATION AND CIPHERING REQUEST message with
invalid Message Authentication Code (MAC), the UE shall:
- send the AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'MAC failure' to the
SS.
For R99 and REL-4 UE:
Alternative 1:
- After step 6, when the UE have received the second AUTHENTICATION AND CIPHERING REQUEST
message with invalid Message Authentication Code (MAC), the UE shall not attempt to access the network.
Alternative 2:
- After step6, when the UE have received the second AUTHENTICATION AND CIPHERING REQUEST
message with invalid Message Authentication Code (MAC) while the timer T3318 is running, the UE shall
send an AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'MAC failure' to the
SS; and
- After step 7a , when the UE have received the third AUTHENTICATION AND CIPHERING REQUEST
For REL-5 UE:
- After step 6, when the UE receives the second AUTHENTICATION AND CIPHERING REQUEST message
with invalid Message Authentication Code (MAC) from the network while the timer T3318 is running, the
UE shall send an AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'MAC
failure' to the SS; and
- After step 7a, when the UE have received the third AUTHENTICATION AND CIPHERING REQUEST
At step 11, when the activated cell is changed from cell A to cell B, the UE shall:
After step 12, when the UE have received the AUTHENTICATION AND CIPHERING REQUEST message with
invalid Message Authentication Code (MAC), the UE shall:
- send an AUTHENTICATION AND CIPHERING FAILURE message with GMM cause 'MAC failure' to the SS.
At step 17, when the timer T3318 have expired, the UE shall:
12.6.2 Void
12.7 Identification procedure
The purpose of this procedure is to check that the UE gives its identity as requested by the network. If this procedure
does not work, it will not be possible for the network to rely on the identity claimed by the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2236
12.7.1 General Identification
12.7.1.1 Definition
1) When requested by the network the User Equipment shall send its IMSI.
2) When requested by the network the User Equipment shall send its IMEI as stored in the Mobile Equipment.
3) When requested by the network the User Equipment shall send its IMEISV as stored in the Mobile Equipment.
Reference
3GPP TS 24.008 clauses 4.7.8
To verify that the UE sends identity information as requested by the system. The following identities can be requested:
IMSI, IMEI and IMEISV.
Initial condition
System Simulator:
One cell operating in network mode II.
User Equipment:
Test procedure
The SS requests identity information from the UE:
- IMSI
- IMEI
- IMEISV
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2237
Expected Sequence
UE SS
1 SS The UE is set to attach to PS services only (see
step 14.
4 Void
CIPHERING REQUEST

5a -> AUTHENTICATION AND
CIPHERING RESPONSE

5b SS The SS starts ciphering and integrity protection.
6 <- IDENTITY REQUEST Identity type =IMSI
7 -> IDENTITY RESPONSE Mobile identity =IMSI
8 <- IDENTITY REQUEST Identity type =IMEI
9 -> IDENTITY RESPONSE Mobile identity =IMEI
10 <- IDENTITY REQUEST Identity type =IMEISV
11 -> IDENTITY RESPONSE Mobile identity =IMEISV
11a <- ATTACH ACCEPT Attach result ='PS only attached'
P-TMSI-1 signature
11b -> ATTACH COMPLETE
(see ICS).
message is set to "Detach" (message not
received if power is removed).
off.
step 2 to step 13a.

None.
"Registration".
"Detach".
At step7, when the SS requests an IMSI with the IDENTITY REQUEST message, UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2238
- send the IDENTITY RESPONSE message with the Mobile identity =IMSI.
At step9, when the SS requests an IMEI with the IDENTITY REQUEST message, UE shall:
- send the IDENTITY RESPONSE message with the Mobile identity =IMEI.
At step11, when the SS requests an IMEISV with the IDENTITY REQUEST message, UE shall:
- send the IDENTITY RESPONSE message with the Mobile identity =IMEISV.
12.8 GMM READY timer handling

12.8.1 Definition
If a READY timer value is received by an UE capable of both UMTS and GSM in the ATTACH ACCEPT or the
ROUTING AREA UPDATE ACCEPT messages, then the received value shall be stored by the UE in order to be used
at an intersystem change from UMTS to GSM.
Reference
3GPP TS 24.008 clause 4.7.2.1
12.8.3 Test purpose
To verify that READY timer value received in UTRA can be used in GSM.
12.8.4.1 Test procedure
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A (UTRAN) in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B
(GSM) in MCC1/MNC1/LAC1/RAC2 (RAI-4).

Cell B is in neigbour cell list of cell A.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" in cell
A (UTRAN).
The value of ATT flag in SIB3 IE Control Channel Description is set to value 0 in cell B (GSM).

User Equipment:
UE supports both GSM/GPRS and UTRAN Radio Access Technologies Yes/No
UE supports UTRAN interactive/ background UL: 64kbps, DL: 64 kbps/PS RAB +uplink:3.4 DL:3.4 kbps
SRBs Yes/No
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2239
Test procedure
An attach is performed.
T3314; set to 60 seconds
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2240
Expected Sequence
UE SS
received on cell A.
Cell B is switched off.
(see note)
ICS). If UE operation mode A not supported set
the UE in operation mode C.
The UE is powered up or switched on and
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
T3314 =60 seconds
T3312=6 minutes
neighbour cell".Set the cell type of cell B to the
"Serving cell".
7 UE UE establish cell reselection to GSM system
The following messages are received on Cell B
(GERAN)
REQUEST
P-TMSI-2 signature
ACCEPT
P-TMSI-1 signature
COMPLETE

11 SS The SS verifies that the time between the end
of Step 10 and the periodic RA updating is
Ready
Timer Period (T3314) +Periodic Routing Area
Updating timer (T3312) (+/- 10%)
REQUEST
Update type ='Periodic updating
Mobile identity=P-TMSI-1
P-TMSI-1 signature
ACCEPT
Update type ='RA updated'

14 UE UE is swithed off or power is removed (see
ICS)

Detach type ='power switched off, GPRS
detach'


Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2241
None.
At step4, when the UE receives the ATTACH ACCEPT or the ROUTING AREA UPDATE ACCEPT messages, UE
shall:
- store the received READY timer value.
At step12, UE shall establish periodic Routing Area Update after Timer Period (T3314) +Periodic Routing Area
Updating timer (T3312) (+/- 10%).
12.9 Service Request procedure (UMTS Only)
12.9.1 Service Request Initiated by UE Procedure
12.9.1.1 Definition
UE shall send the Service Request message to the network in order to establish the PS signalling connection for the
upper layer signalling or for the resource reservation for active PDP context(s).
Reference
TS 24.008 clauses 4.7.13
TS 23.060 clauses 6.12.1
To test the behaviour of the UE if the UE initiates the CM layer service (e.g. SM or SMS) procedure.
Initial condition
System Simulator:
User Equipment:
The UE has a valid IMSI
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2242
Test procedure
a) The UE in PMM-IDLE state sends a SERVICE REQUEST message to the SS in order to establish the PS
signalling connection for the upper layer signalling.
b) After the SS receives the SERVICE REQUEST message, the SS performs authentication procedure.
Expected Sequence
UE SS
step 12.

CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
6a SS The IE "Establishment cause" in the received
RRC CONNECTION REQUEST message is
not checked.
7 -> SERVICE REQUEST Service type ="signalling",
8 <-
SERVICE REJ ECT

CIPHERING RESPONSE

(see ICS).
cause" in any received RRC CONNECTION
REQUEST is set to "Detach" (not received if
power is removed).
off.
step 2 to step 11a.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2243
"Registration".
"Detach".
At step7, when the UE has any signalling message (e.g. for SM or SMS) that requires security protection, the UE shall:
- send the SERVICE REQUEST message with service type indicated "signalling".
12.9.2 Service Request Initiated by Network Procedure
12.9.2.1 Definition
When the UE receives a paging request for PS domain from the network in PMM-IDLE mode, the UE shall send the
SERVICE REQUEST message to the network.
Reference
TS 24.008 clauses 4.7.13
TS 23.060 clauses 6.12.2
To test the behavior of the UE if the UE receives the paging request for PS domain service from the network.
Initial condition
System Simulator:
User Equipment:
The UE has a valid IMSI
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2244
Test procedure
a) The UE is in PMM-IDLE state. The SS pages the UE by sending a Paging message to the UE.
b) The UE sends a SERVICE REQUEST message to the SS. Service Type specifies Paging Response. The Service
Request is carried over the radio in an RRC Direct Transfer message.
c) After the SS receives the SERVICE REQUEST message from the UE, SS initiates an authentication procedure.
Expected Sequence
UE SS
step 12.
2 UE The UE is powered up or switched in and
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
7 -> SERVICE REQUEST Service type ="Paging response"
CIPHERING REQUEST

CIPHERING RESPONSE

9a SS SS starts integrity protection and releases the
RRC connection.
(see ICS).
message is set to "Detach" (message not sent
if power is removed).
off.
step 2 to step 11a.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2245
None.
"Registration".
"Terminating interactive Call".
"Detach".
At step 7, when the UE receives a paging request for PS domain from the network in PMM-IDLE mode, the UE shall:
- send the SERVICE REQUEST message with service type indicated "paging response".
12.9.3 Service Request / rejected / Illegal MS
12.9.3.1 Definition
If the network rejects a service request procedure from the UE with the cause "Illegal MS", the UE shall:
1) set the GPRS update status to GU3 ROAMING NOT ALLOWED and enter state GMM DEREGISTRATED. A
UE operating in MS operation A shall in addition to set the update status to U3 ROAMING NOT ALLOWED.
2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. A UE operating in MS
operation A shall in addition delete any TMSI, LAI and ciphering key sequence number.
3) consider the USIM as invalid for PS service until switched off or the USIM is removed.
Reference
TS 24.008 clauses 4.7.13.4
To test the behaviour of the UE if the network rejects the service request procedure with the cause "Illegal MS".
Initial condition
System Simulator:
User Equipment:
The UE has a valid P-TMSI-1, RAI-1 and IMSI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2246
Test procedure
a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for
the upper layer signalling.
b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJ ECT message with the
cause value #3(Illegal MS).
c) After the UE receives the SERVICE REJ ECT message with the cause value #3(Illegal MS), the UE deletes any
P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.
d) The SS checks that the UE does not initiate an upper-layer signalling until the power of the UE is switched off.
e) The SS checks that the UE does not initiate an upper-layer signalling until the USIM is removed from the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2247
Expected Sequence
UE SS
received on cell A.
ICS).
2 SS The SS is set in network operation mode II and
activates cell A.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
command.
8 -> SERVICE REQUEST Service type ="signalling"
9 <- SERVICE REJ ECT Reject cause ="Illegal MS"
command.
access the network.
13 Void

by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
20 <- SERVICE REJ ECT Reject cause ="Illegal MS"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2248
UE SS
command.
access the network.
23 UE If possible (see ICS) USIM replacement is
removed
24 Void
25 UE The UE initiates a PS attach, by MMI or by AT
command.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
31 <-
SERVICE REJ ECT

32 VOID
33 SS VOID
34 SS The SS releases RRC connection.
(see ICS).
off.

None.
At step11, when the UE receives the SERVICE REJ ECT message with cause "Illegal MS" UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2249
At step22, when the UE receives the SERVICE REJ ECT message with cause "Illegal MS" UE shall:
At step26, when the UE gets the USIM replaced, is powered up or switched on,UE shall:
- initiate the service request procedure.
12.9.4 Service Request / rejected / PS services not allowed
12.9.41 Definition
If the network rejects a service request procedure from the UE with the cause "PS services not allowed", the UE shall:
1) set the GPRS update state to GU3 ROAMING NOT ALLOWED.
2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.
3) consider the USIM as invalid for PS service until the UE is switched off or until the USIM is removed.
Reference
TS 24.008 clauses 4.7.13.4
To test the behaviour of the UE if the network rejects the service request procedure with the cause "PS service not
allowed".
Initial condition
System Simulator:
User Equipment:
Test procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2250
cause value #7(PS services not allowed).
c) After the UE receives the SERVICE REJ ECT message with the cause value #7(PS services not allowed), the UE
deletes any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.
d) The SS checks that the UE does not initiate an upper-layer signalling until the UE is switched off.
e) The SS checks that the UE does not initiate an upper-layer signalling until the USIM is removed from the UE.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2251
Expected Sequence
UE SS
received on cell A.
ICS).
activates cell A.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
command.
9 <- SERVICE REJ ECT Reject cause ="PS services not allowed"
command.
access the network.
(SS wait 30seconds)
13 Void
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
20 <- SERVICE REJ ECT Reject cause ="PS services not allowed"
command.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2252
UE SS
access the network.
(SS wait 30seconds)
or switched on.
24 Void
25 UE The UE initiates a PS attach, by MMI or by AT
command.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
31 <-
SERVICE REJ ECT

32 VOID
33 SS VOID
(see ICS).
off.

At step11, when the UE receives the SERVICE REJ ECT message with cause "PS services not allowed" UE shall:
At step22, when the UE receives the SERVICE REJ ECT message with cause "PS services not allowed" UE shall:
At step26, when the UE gets the USIM replaced, is powered up or switched on,UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2253
- initiate the service request procedure.
12.9.5 Service Request / rejected / MS identity cannot be derived by the
network
12.9.5.1 Definition
If the network rejects a service request procedure from the UE with the cause "MS identity cannot be derived by the
network", the UE shall:
1) set the GPRS update states to GU2 NOT UPDATED.
2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.
3) initiate the PS attach procedure automatically.
Reference
TS 24.008 clauses 4.7.13.4
To test the behaviour of the UE if the network rejects the service request procedure with the cause "MS identity cannot
be derived by the network".
Initial condition
System Simulator:
User Equipment:
Test procedure
cause value #9 (MS identity cannot be derived by the network).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2254
Expected Sequence
UE SS
received on cell A.
ICS).
activates cell A.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
command.
9 <- SERVICE REJ ECT Reject cause ="MS identity cannot be derived
by the network"
10 UE The UE automatically initiates the PS attach
procedure.
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-2 signature
command.
16 <-
SERVICE REJ ECT

17 VOID
18 SS VOID .
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2255
off.

None.
At step11, when the UE receives the SERVICE REJ ECT message with cause "MS identity cannot be derived by the
network" UE shall:
- initiate PS attach procedure automatically.
12.9.6 Service Request / rejected / PLMN not allowed
12.9.6.1 Definition
If the network rejects a service request procedure from the UE with the cause "PLMN not allowed", the UE shall:
1) delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number.
2) set the GPRS update status to GU3 ROAMING NOT ALLOWED.
3) store the PLMN identity in the appropriate forbidden list.
Reference
TS 24.008 clauses 4.7.13.4
To test the behaviour of the UE if the network rejects the service request procedure with the cause "PLMN not
allowed".
Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (Not HPLMN) cell B in
MCC2/MNC1/LAC1/RAC1.
All two cells are operating in network operation mode II.
cells.
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2256
Test procedure
cause value #11 (PLMN not allowed).
c) The SS checks that the UE does not initiate an upper-layer signalling until the UE is switched off.
d) The SS checks that the UE does not answer a Page from the SS until the power of the UE is switched off.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2257
Expected Sequence
UE SS
received on cell A.
ICS).
cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
command.
9 <- SERVICE REJ ECT Reject cause ="PLMN not allowed"
10 UE The UE stores the PLMN identity in the
"forbidden PLMN list".
command.
access the network.
(SS wait 30second)
13 <- PAGING TYPE1 Paging order is for PS service
The following messages shall be sent and shall
be received on cell B.
cell".
(see note)
mode A.
CIPHERING REQUEST

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2258
CIPHERING RESPONSE

19 <- ATTACH ACCEPT Mobile identity =P-TMSI-2
P-TMSI-2 signature
(see ICS).
off.

None.
At step9, when the UE receives the SERVICE REJ ECT message with cause "PLMN not allowed", UE shall:
- not perform a PS attach procedure in the same PLMN.
At step13, when the UE receives the paging message for PS domain UE shall:
12.9.7a Service Request / rejected / No PDP context activated
12.9.7a.1 Definition
If the network rejects a service request procedure with the cause "No PDP context activated", the UE shall:
- deactivate all active PDP contexts.
After the UE deactivates all active PDP contexts, UE shall:
- perform PDP context(s) activation.
Reference
TS 24.008 clauses 4.7.13.4
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2259
To test the behaviour of the UE if the network rejects the service request procedure with the cause "No PDP context
activated".
Initial condition
System Simulator:
User Equipment:
Test procedure
cause value #40 (No PDP context activated).
c) After the UE receives the SERVICE REJ ECT message, the UE shall send the ACTIVATE PDP CONTEXT
REQUEST message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2260
Expected Sequence
UE SS
received on cell A.
1 The UE is set in UE operation mode C (see
ICS).
2 The SS is set in network operation mode II and
activates cell A.
3 The UE is powered up or switched on and
by the UE.
4 -> ATTACH REQUEST
CIPHERING REQUEST

CIPHERING RESPONSE

5 <- ATTACH ACCEPT
7 UE The UE initiates a PS call, by MMI or by AT
command.
CIPHERING REQUEST

CIPHERING RESPONSE

11 SS The SS initiates a security mode control
procedure.
12 UE After a PS call is established, the UE suspends
transmission of the user data.
13 SS The SS initiates a Radio Bearer release
procedure.
14 UE The UE resumes the transmission of the user
data.
15 -> SERVICE REQUEST Service type ="data"
16 <- SERVICE REJ ECT Reject cause ="No PDP context activated"
17 UE The UE shall deactivate locally all active PDP
contexts.
command.
CIPHERING REQUEST

CIPHERING RESPONSE

21 SS SS initiates a security procedure by sending
SECURITY MODE COMMAND message.
(see ICS).
23 UE The UE initiates Detach request, by MMI or by
AT command.
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2261
12.9.7a.5 Test requirements
When the UE receives a SERVICE REJ ECT message with the cause "No PDP context activated", UE shall:
- deactivate all active PDP context.
- initiates a Service request procedure by sending a SERVICE REJ ECT message with Service type ="data".
12.9.7b Service Request / rejected / No Suitable Cells In Location Area
12.9.7b.1 Definition
If the network rejects a service request procedure from the UE with the cause "No Suitable Cells In Location Area", the
UE shall:
1) set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall change to state GMM-
REGISTERED.LIMITED-SERVICE.
2) store the LAI in the list of 'forbidden location areas for roaming'.
If no RRC connection exists, the UE shall perform the following additional actions immediately. If the UE is operating
in operation mode A and an RRC connection exists, the UE shall perform these actions when the RRC connection is
subsequently released:
1) if the UE is IMSI attached, the UE shall set the update status to U3 ROAMING NOT ALLOWED and shall reset
the location update attempt counter. The new MM state is MM IDLE.
2) search for a suitable cell in a different location area on the same PLMN.
Reference
TS 24.008 clauses 4.7.13.4
To test the behaviour of the UE if the network rejects the service request procedure with the cause "No Suitable Cells In
Location Area".
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2262
Test procedure
The SS rejects a Service request with the cause value 'No Suitable Cells In Location Area'. The SS checks that the UE
shall perform routing area updating procedure when the UE enters a suitable cell in a different location area on the same
PLMN.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2263
Expected Sequence
UE SS
SS Set the cell type of cell A to the "Serving cell".
neighbour cell".
neighbour cell".
(see note)
follows.
goto step 15.
by the UE.
mode A.
2b SS The SS verifies that the IE "Establishment
3 -> ATTACH REQUEST Attach type ="PS attach"
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
8 -> SERVICE REQUEST Service type ='signalling'
9 <- SERVICE REJ ECT Reject cause ='No Suitable Cells In Location
Area'
9a SS The SS releases the RRC connection
received on cell B.
9b UE Registration on CS See TS 34.108
mode A.
9c SS The SS verifies that the IE "Establishment
REQUEST
P-TMSI-1 signature
Old routing area identity =RAI-1
CIPHERING REQUEST

CIPHERING RESPONSE

ACCEPT
P-TMSI-2 signature
COMPLETE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2264
(see ICS).
13a IMSI DETACH INDICATION Message not sent if power is removed
mode A.
off.

None.
12.9.7b.5 Test requirements
12.9.7c Service Request / rejected / Roaming not allowed in this location
area
12.9.7c.1 Definition
12.9.7c.2 Conformance requirement
If the network rejects a service request procedure from the UE with the cause "Roaming not allowed in this location
area", the UE shall:
1) set the PS update status to GU3 ROAMING NOT ALLOWED
2) store the LAI in the list of "forbidden location areas for roaming".
3) perform a PLMN selection.
Reference
TS 24.008 clauses 4.7.13.4
12.9.7c.3 Test purpose
To test the behaviour of the UE if the network rejects the service request procedure with the cause "Roaming area not
allowed in this location area".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2265
12.9.7c.4 Method of test
Initial condition
System Simulator:
cells.
User Equipment:
Test procedure
The SS rejects a Service request with the cause value 'Roaming not allowed in this location area'. The SS checks that the
UE shall not perform PS attach procedure when the UE enters a different location area.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2266
Expected Sequence
UE SS
received on cell A.
cell".
cell".
(see note)
go to step 19.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

command.
9 <- SERVICE REJ ECT Reject cause ="roaming not allowed in this
location area"
11 SS Set the cell type of cell A to the " Non-Suitable
cell".
Set the cell type of cell B to the " Serving cell".
(see note)
access the network.
13 SS Set the cell type of cell B to the " Non-Suitable
cell".
Set the cell type of cell C to the " Serving cell".
(see note)
received on cell C.
REQUEST
Old routing area identity =RAI-1
CIPHERING REQUEST

CIPHERING RESPONSE

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2267
ACCEPT
Update result ='RA update'
P-TMSI-2 signature
COMPLETE

(see ICS).
PS / IMSI detach'
off.

None.
12.9.7c.5 Test requirements
At step12, when the UE enters a same location area, UE shall:
- not initiate the combined PS attach procedure.
At step14, when the UE enters a different location area, UE shall:
- initiate the routing area updating procedure with information elements specified in the above Expected
Sequence.
12.9.8 Service Request / Abnormal cases / Access barred due to access
class control
12.9.8.1 Definition
If the UE access class X is barred, the UE shall:
1) not start Service Request procedure.
2) stay in the current serving cell.
3) applie normal cell reselection process.
If the UE access class X is granted or serving cell is changed, the UE shall:
1) start Service Request procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2268
Reference
TS 24.008 clauses 4.7.13.5.
To test the behavior of the UE in case of access class control (access is granted).
Initial condition
A random access class X (0-15) is selected. The USIM is programmed with this access class X.
Initially, an access class X is barred.
System Simulator:
Access class x barred.
User Equipment:
Test procedure
The SS initiates access class X barred. A service request procedure is not performed.
The SS initiates that access class X is not barred. A service request procedure is performed.
Expected Sequence
UE SS
1 UE The USIM is set up Access class x.
The access class x is barred in cell A.
The UE is powered up or switched on and
attempt to initiate an ATTACH.
2 UE No SERVICE REQUEST sent to SS, as access
class X is barred.
4 UE The UE automatically initiates an attach.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2269
CIPHERING REQUEST

CIPHERING RESPONSE

P-TMSI-1 signature
command.
9 -> SERVICE REQUEST Service Type ="signalling".
10 <-
SERVICE REJ ECT

11 VOID
(see ICS).
off.

None.
- not perform Service Request procedure.
At step9, UE shall:
- perform Service Request procedure.
12.9.9 Service Request / Abnormal cases / Routing area update procedure
is triggered
12.9.9.1 Definition
If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before
the security mode control procedure is completed, the UE shall:
- abort Service request procedure.
- start routing area update procedure immediately.
Reference
TS 24.008 clause 4.7.13.5
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2270
To test the behavior of the UE in case of collision between Routing area update procedure and Service request
procedure.
Initial condition
System Simulator:
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" in
both cells
User Equipment:
Test procedure
the upper layer signalling in cell A.
b) The SS changes the conditions of cell A so that it is no longer a suitable Serving cell.
c) The UE aborts Service request procedure and performs Routing area updating procedure.
d) The UE re-sends the SERVICE REQUEST message to the SS in order to establish the PS signalling connection
for the upper layer signalling, this time in cell B
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2271
Expected Sequence
UE SS
received on cell A.
ICS).
neighbour cell".
(see note)
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
6a UE The UE initiates upper-layer signalling, e.g.,
Activate PDP Context request, by MMI or by AT
command.
8 SS The RF level of cell A is lowered until the level
corresponds to that of a Non-suitable cell.
Note: the SS does not initiate the security mode
control procedure.
9 UE The UE aborts Service request procedure.
received on cell B.
REQUEST

ACCEPT
P-TMSI-1 signature
COMPLETE

13 UE The UE initiates upper-layer signalling, e.g.,
Activate PDP Context request, either
automatically or by MMI or by AT command.
CIPHERING REQUEST

CIPHERING RESPONSE

17 SS The SS initiates a security mode control
procedure.
18 SS After the security mode control procedure is
completed, the SS releases RRC connection.
(see ICS).
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2272
message has been received within 1 second
off.
NOTE: The definitions for "Suitable neighbour cell", Non-suitable cell and "Serving cell" are specified

None.
- initiate the PS attach procedure with information elements specified in the above Expected Sequence .
At step7, UE shall:
- perform the service request procedure.
At steps 9 and 10, after the SS sets the cell type of cell A to Non-suitable cell before the security mode control
procedure is completed, UE shall;
- abort the Service request procedure
At step14, after the UE completes the routing area updating procedure, UE shall;
- restart the Service Request procedure.
12.9.10 Service Request / Abnormal cases / Power off
12.9.10.1 Definition
When the UE in GMM-SERVICE-REQUEST-INITIATED state is switched off, UE shall:
- perform PS detach procedure.
Reference
TS 24.008 clauses 4.7.13.5
To test the behavior of the UE in case of collision between Service request procedure and "powered off".
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2273
Test procedure
The UE is switched off after initiating a Service request procedure. A PS detach is automatically performed by the UE
before power is switched off.
Expected Sequence
UE SS
received on cell A.
ICS).
activates cell A.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

command.
8 UE The UE is powered off and initiates a PS detach
(with power off) by MMI or by AT command.
off.

None.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2274
At step7, UE shall:
- perform the service request procedure
At step9, when the UE is switched off during the Service Request procedure, UE shall;
- abort the Service request procedure.
- perform the PS detach procedure.
12.9.11 Service Request / Abnormal cases / Service request procedure
collision
Abnormal cases in the MS
The following abnormal cases can be identified:
- Procedure collision
If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-
INITIATED, the GPRS detach procedure shall be progressed and the Service request procedure shall be aborted.
If the cause IE, in the DETACH REQUEST message, indicated a "reattach request", the GPRS attach procedure
shall be performed.
Reference
TS 24.008 clauses 4.7.13.5
To test the behaviour of the UE in case of collision between Service request procedure and PS detach procedure.
Initial condition
System Simulator:
User Equipment:
Test procedure
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2275
b) The SS does not respond to the SERVICE REQUEST for data. Instead it sends a DETACH REQUEST message
to the UE, with the Detach type IE set to value "re-attach required".
c) After the UE receives the DETACH REQUEST message, the repeats the attach procedure.
d) The UE is switched off or power is removed. If the UE is switched off it sends a DETACH REQUEST.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2276
Expected Sequence
UE SS
received on cell A.
ICS).
activates cell A.
by the UE.
CIPHERING REQUEST

CIPHERING RESPONSE

6 Void
7a UE The UE initiates an upper-layer signalling, e.g.,
command.
7b -> SERVICE REQUEST Service type ="signalling"


7d SS The SS initiates a Radio Bearer release
procedure.
7e UE The UE initiates an upper-layer signalling, e.g.,
command.
8 -> SERVICE REQUEST Service type ="data"

9 SS The SS does not respond to SERVICE
REQUEST message.
10 <- DETACH REQUEST Detach type ="re-attach required"
10a -> DETACH ACCEPT
CIPHERING REQUEST

CIPHERING RESPONSE

12 <- ATTACH ACCEPT Mobile identity =P-TMSI-2
P-TMSI-2 signature
(see ICS).
off.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2277
None.
At step11, when the UE receives a DETACH REQUEST message from the network before the Service request
procedure completes, UE shall;
- repeat the attach procedure.
- retry the Service request procedure
At step 19 if the UE is switched off, UE shall:
- perform the PS detach procedure.
12.9.12 Service Request / RAB re-establishment / UE initiated / Single PDP
context
The following procedures shall be performed in the MS when radio coverage is lost:
- For a PDP context using background or interactive traffic class, the PDP context is preserved even if RRC re-
establishment procedures have failed.
- For a PDP context using streaming or conversational traffic class, the PDP context is preserved, but the
maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink) when the RRC re-establishment
procedure has failed. After coverage is regained and if the MS did not deactivate the PDP Context locally the
MS should start MS-initiated PDP Context Modification procedure or the PDP Context Deactivation procedure.
The MS shall use the PDP Context Modification procedure to re-activate the PDP context and re-establish the
RAB.
The following procedures shall be performed in the MS when the RRC layer indicate to higher layer that a RAB has
been released and the RAB release was not initiated due to a PDP Context Deactivation Procedure:
- For a PDP context using background or interactive traffic class, the PDP context is be preserved with no
modifications.
maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink).
At this point or at a later stage, the MS may start a PDP Context Deactivation procedure or PDP Context
Modification procedure. The MS shall use the PDP Context Modification procedure to re-activate the PDP
context and re-establish the RAB.
The procedure for re-establishment of RABs allows the SGSN to re-establish RABs for active PDP contexts that don't
have an associated RAB.
The MS initiates the re-establishment of RABs by using the Service Request (Service Type =Data) message.
The criteria to invoke the Service request procedure are when;
b) the MS, either in PMM-IDLE or PMM-CONNECTED mode, has pending user data to be sent and no radio
access bearer is established for the corresponding PDP context. The procedure is initiated by an indication from
the lower layers (see 3GPP TS 24.007). In this case, the service type shall be set to "data".
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2278
After completion of a Service request procedure, the pending service is resumed and uses then the connection
established by the procedure. If the service type is indicating "data", then the radio access bearers for all activated PDP
contexts are re-established by the network, except for those activated PDP contexts having maximum bit rate value set
to 0 kbit/s for both uplink and downlink. The re-establishment of radio access bearers for those PDP contexts is
specified in subclause 6.1.3.3 of 3GPP TS 24.008.
Reference
TS 23.060 clause 9.2.3.4-5, 9.2.5.2
TS 24.008 clause 4.7.13
To verify that the UE initiates a Service request procedure due to uplink data transmission with one preserved PDP
context with traffic class "Background class" after normal RRC connection release as well as when radio coverage is
lost.
To verify that the radio access bearer can be re-established for the preserved PDP context, initiated by the UE.
Initial condition
System Simulator:
One cell, default parameters.
User Equipment:
Test procedure
a) A PDP context with traffic class "Background class" is activated including the radio access bearer.
b) The SS releases the RRC connection, but keeps the PDP context.
c) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE
REQUEST.
d) The SS responds with a SERVICE ACCEPT message and establishes the RAB for the active PDP context using
a Radio bearer establishment procedure and the same QoS as previously, without the need for PDP context
modification.
e) The SS configured the cell as a non-suitable "Off" cell for 4 minutes, making the UE to release the RAB and
enter idle mode due to that radio coverage is lost.
f) The SS configures the cell as a serving cell.
g) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE
REQUEST.
h) The SS responds with a SERVICE ACCEPT message and establishes the RAB for the active PDP context using
a Radio bearer establishment procedure and the same QoS as previously, without the need for PDP context
modification.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2279
Expected Sequence
UE SS
REQUEST
Activate a PDP context with traffic class
"Background class"
3 SS The SS starts ciphering and integrity protection
and establishes the radio access bearer.
ACCEPT
6 UE The UE initiates transmission of uplink data, by
REQUEST message is set to "Originating
Background Call".
8 SERVICE REQUEST Service type ="data"

9 SS The SS starts ciphering and integrity
protection.

10 SS The SS establishes the radio access bearer for
the active PDP context, using the same QoS
that was used at activation.
11 SS The SS configures the cell as a non-suitable
"Off" cell and waits for 4 minutes, making the
UE to release the RAB and enter idle mode.
12 SS The SS configures the cell as a serving cell.
Background Call".

protection.


None.
After steps 7 and 14, UE shall:
- transmit a SERVICE REQUEST message with service type "data"
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2280
12.9.13 Service Request / RAB re-establishment / UE initiated / multiple
PDP contexts
modifications.
The MS initiates the re-establishment of RABs by using the Service Request (Service Type =Data) message.
b) the MS, either in PMM-IDLE or PMM-CONNECTED mode, has pending user data to be sent and no radio
access bearer is established for the corresponding PDP context. The procedure is initiated by an indication from
the lower layers (see 3GPP TS 24.007). In this case, the service type shall be set to "data".
Reference
TS 23.060 clause 9.2.3.4-5, 9.2.5.2
TS 24.008 clause 4.7.13
To verify that the UE initiates a Service request procedure due to uplink data transmission with two PDP contexts with
different traffic classes are activated, when one is of traffic class "background class" and the other is of traffic class
"interactive class", after normal RRC connection release.
To verify that the radio access bearers can be re-established with a single radio bearer establishment procedure for the
preserved PDP contexts, when initiated by the UE.
Initial condition
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2281
Secondary PDP context activation procedure Yes/no
Test procedure
a) Two PDP contexts with different Traffic Classes are activated including the radio access bearers.
b) The SS releases the RRC connection, but keeps the two PDP contexts.
c) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE
REQUEST.
d) The SS responds with a SERVICE ACCEPT message and establishes the RABs for the two active PDP contexts
using a single Radio bearer establishment procedure and the same QoS as previously, without the need for PDP
context modification.
Expected Sequence
UE SS
REQUEST
"Background class"
ACCEPT
CONTEXT REQUEST
Request a Secondary PDP context activation
with traffic class "Interactive class"
7 SS The SS establishes the radio access bearer.
CONTEXT ACCEPT
Accept the Secondary PDP context activation
Interactive Call", which is the most demanding
traffic class among the active PDP contexts.

protection.

14 SS The SS establishes the radio access bearers
simultaneously for the two active PDP
contexts, using the same QoS that was used at
activation.

None.
After step 11, UE shall:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2282
- transmit a SERVICE REQUEST message with service type "data".
12.9.14 Service Request / RAB re-establishment / Network initiated / single
PDP context
modifications.
When RABs for an MS that has no RRC connection needs to be re-established, the CN must first page the MS.
c) the MS receives a paging request for PS domain from the network in PMM-IDLE mode. In this case, the service
type shall be set to "paging response".
Reference
TS 23.060 clause 9.2.3.4-5, 9.2.5.2
TS 24.008 clause 4.7.13
To verify that the radio access bearers can be re-established for the preserved PDP context with traffic class
"Background class", when initiated from the network, after normal RRC connection release.
System Simulator:
User Equipment:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2283
Test procedure
a) A PDP context with traffic class "Background class" is activated including the radio access bearer.
b) The SS releases the RRC connection, but keeps the PDP context.
c) The SS initiates paging of the UE.
d) As response to the paging, the UE initiates an RRC connection establishment and sends a SERVICE REQUEST.
e) The SS responds with a SERVICE ACCEPT message and establishes the RAB for the active PDP context using
the same QoS as previously, without the need for PDP context modification.
Expected Sequence
UE SS
REQUEST
"Background class"
ACCEPT
6 SS The SS waits for 5 s to ensure the UE is in
service.
7 PAGING TYPE 1 The SS initiates paging of the UE using the
paging cause "Terminating Background Call"'
REQUEST message is set to the same value as
the paging cause.
9 SERVICE REQUEST Service type ="Paging response"



None.
After step 8, UE shall:
- transmit a SERVICE REQUEST with service type "Paging response"

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2284
13 General Tests
13.1 Emergency call / general
In this clause, the emergency call service is tested for user equipment that support Emergency speech call in the
following cases:
- emergency call initiated in the MM idle state with authentication and with security mode procedure applied;
- emergency call initiated in the MM idle, no IMSI state (hence without authentication and without security mode
procedure applied), the network accepting the call;
- emergency call initiated in the MM idle, no IMSI state (hence without authentication and without security mode
procedure applied), the network rejecting the call.
13.2 Emergency call
Emergency call establishment can be initiated by an UE whether location updating has been successful or not and
whether a USIM is inserted into the UE or not; but only if the UE is equipped for speech.
If the procedures tested in this clause are not correctly implemented in the UE, establishment, maintenance and clearing
of connections might fail in the essential case of emergency calls.
13.2.1 Emergency call / with USIM
13.2.1.1 Emergency call / with USIM / accept case
When a USIM is present, subscriber specific emergency call set-up MMI shall be provided. The operator shall specify
preferred emergency call MMI(s) (e.g. 911 for US citizens or 110, 118 and 119 for J apanese citizens) for use in any (i.e.
home or visited) PLMN. This shall be stored in the USIM and the UE shall read this and use any entry of these digits to
set up an emergency call. It shall be possible to store more than one instance of this field.
When a USIM containing stored emergency numbers is present, only those numbers are identified as emergency
numbers, i.e. default emergency numbers stored in the UE are ignored.
1) A MM connection for an emergency call may be established in all states of the mobility management sublayer
which allow MM connection establishment for a normal originating call.
When a user requests an emergency call establishment the UE will send a CM SERVICE REQUEST message to
the network with a CM service type information element indicating emergency call establishment..
2) Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity
of the UE sends a setup message to its peer entity. This setup message is
- a SETUP message, if the call to be established is a basic call; and
- an EMERGENCY SETUP message, if the call to be established is an emergency call.
3) Upon receiving an indication that the call has been accepted, the call control entity of the network shall: through
connect the traffic channel (including the connection of an interworking function, if required) and send a
CONNECT message to its peer entity at the calling UE; start timer T313 and enter the "connect indication" state.
This message indicates to the call control entity of the calling UE that a connection has been established through
the network.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2285
4) The call control entity of the network shall initiate clearing by: sending a DISCONNECT message; and entering
the "disconnect indication" state.
Reference(s):
- For conformance requirement 1: TS 24.008 clause 4.5.1.5, TS 22.101 clause 8.
- For conformance requirement 2: TS 24.008, clause 5.2.1.
- For conformance requirement 3: TS 24.008, clause 5.2.1.6.
1) To verify that an UE supporting speech in the state "MM idle", when made to call the emergency call number,
sends a CM SERVICE REQUEST message specifying the correct CKSN and TMSI, with CM service type IE
"emergency call establishment".
2) To verify that after security mode setting by the SS, the UE sends an EMERGENCY SETUP message.
3) To verify that, the SS having sent a CALL PROCEEDING message and then an ALERTING message the
correct performance of a connect procedure and that the UE has through connected the DTCH in both directions.
4) To verify that the call is cleared correctly.
Initial Conditions
- System Simulator:
- User Equipment:
- the UE is in state "MM idle" with valid TMSI and CKSN.
- Emergency speech call yes/no
Test procedure
The UE is made to initiate an emergency call. Having reached the active state, the call is cleared by the SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2286
Expected Sequence
UE SS
1 UE The "emergency number" is entered. Number
shall be one programmed in test USIM EFECC
(Emergency Call Codes), ref. 34.108 clause
8.3.2.21.
2 --> UE establishes RRC procedure for emergency
call.
Establishment cause: Emergency Call
3 Void
4 Void
5 --> CM SERVICE REQUEST The CM service type IE indicates "emergency call
establishment".
6 <-- AUTHENTICATION REQUEST IE Authentication Parameter AUTN shall be
present in the message.
7 --> AUTHENTICATION RESPONSE SRES specifies correct value.
8 SS starts security procedure.
9 Void
10 Void
11 --> EMERGENCY SETUP If the Bearer capability IE is not included the
default UMTS AMR speech version shall be
assumed.
12 <-- CALL PROCEEDING
13 <-- ALERTING
14 <-- SS sets up the radio bearer with the rate indicated
by the EMERGENCY SETUP message.
15 Void
16 <-- CONNECT
17 --> CONNECT ACKNOWLEDGE
18 UE The DTCH is through connected in both
directions.
19 <-- DISCONNECT SS disconnects the call and associated radio
bearer.

None.
In step 2 of the Expected Sequence the UE shall establish RRC procedure with establishment cause Emergency Call.
In step 5 of the Expected Sequence the UE shall send a CM SERVICE REQUEST message with CM service type
emergency call establishment.
In step 11 of the Expected Sequence the UE shall send an EMERGENCY SETUP message.
In step 18 of the Expected Sequence the UE has through connected the DTCH in both directions.
In step 19 of the Expected Sequence the call is cleared correctly.
13.2.2 Emergency call / without USIM
13.2.2.1 Emergency call / without USIM / accept case
The following emergency numbers shall be stored in the UE for use without USIM: 000, 08, 112, 110, 118, 119, 911
and 999.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2287
the network with a CM service type information element indicating emergency call establishment.
Normally, the UE will be identified by an IMSI or a TMSI. However, if none of these identifiers is available in
the UE, then the UE shall use the IMEI for identification purposes.
2) As a serving network option, emergency calls may be established without the network having to apply the
security mode procedure as defined in TS 24.008.
The following are the only cases where the "security procedure not applied" option may be used:
a) Authentication is impossible because the USIM is absent.
3) Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity
of the UE sends a setup message to its peer entity. This setup message is:
- a SETUP message, if the call to be established is a basic call; and
- an EMERGENCY SETUP message, if the call to be established is an emergency call.
4) Upon receiving an indication that the call has been accepted, the call control entity of the network shall: through
connect the traffic channel (including the connection of an interworking function, if required) and send a
CONNECT message to its peer entity at the calling UE; start timer T313 and enter the "connect indication" state.
This message indicates to the call control entity of the calling UE that a connection has been established through
the network.
5) The call control entity of the network shall initiate clearing by: sending a DISCONNECT message; and entering
the "disconnect indication" state.
Reference(s):
- For conformance requirements 3: TS 24.008, clause 5.2.1.
1) To verify that the UE in the "MM idle, no IMSI" state (no USIM inserted) when made to call the emergency call
number, sends a CM SERVICE REQUEST message in which the ciphering key sequence number IE indicates
"no key is available", the CM service type IE indicates "emergency call establishment" and the mobile identity
IE specifies the IMEI of the UE.
2) To verify that after receipt of a CM SERVICE ACCEPT message without security mode procedure applied from
the SS, the UE sends an EMERGENCY SETUP message.
3) To verify that the SS having sent a CALL PROCEEDING message and then an ALERTING message the correct
performance of a connect procedure and that the UE has through connected the DTCH in both directions.
4) To verify that the call is cleared correctly.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2288
Initial Conditions
- System Simulator:
- User Equipment:
- the UE is in MM-state "MM idle, no IMSI", no USIM inserted.
Test procedure
The UE is made to initiate an emergency call. The call is established without authentication and security. Having
reached the active state, the call is cleared by the SS.
Expected Sequence
UE SS
1 UE The "emergency number" is entered. One of the
following emergency numbers shall be used: 000,
08, 112, 110, 118, 119, 911 or 999.
call.
3 Void
4 Void
establishment". The mobile identity IE specifies
the IMEI of the UE. The cipher key sequence
number IE indicates "no key is available".
6 <-- CM SERVICE ACCEPT
7 --> EMERGENCY SETUP If the Bearer capability IE is not included the
default UMTS AMR speech version shall be
assumed.
8 <-- CALL PROCEEDING
9 <-- ALERTING
10 <-- SS sets up the radio bearer with the rate indicated
by the EMERGENCY SETUP message.
11 Void
12 <-- CONNECT
13 --> CONNECT ACKNOWLEDGE
14 UE The DTCH is through connected in both
directions.
15 <-- DISCONNECT SS disconnects the call and associated radio
bearer.

None.
emergency call establishment, mobile identity IMEI and cipher key sequence number no key is available.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2289
In step 7 of the Expected Sequence the UE shall send an EMERGENCY SETUP message.
In step 14 of the Expected Sequence the UE has through connected the DTCH in both directions.
In step 15 of the Expected Sequence the call is cleared correctly.
13.2.2.2 Emergency call / without USIM / reject case
The following emergency numbers shall be stored in the UE for use without USIM: 000, 08, 112, 110, 118, 119, 911
and 999.
the network with a CM service type information element indicating emergency call establishment.
Normally, the UE will be identified by an IMSI or a TMSI. However, if none of these identifiers is available in
the UE, then the UE shall use the IMEI for identification purposes.
2) If the network does not accept the emergency call request, e.g., because IMEI was used as identification and this
capability is not supported by the network, the network will reject the request by returning a CM SERVICE
REJ ECT message to the UE.
Reference(s):
- For conformance requirement 2: TS 24.008 clause 4.5.1.5.
1) To verify that the UE in the "MM idle, no IMSI" state (no USIM inserted) when made to call the emergency call
number, sends a CM SERVICE REQUEST message in which the ciphering key sequence number IE indicates
"no key is available", the CM service type IE indicates "emergency call establishment", and the mobile identity
IE specifies the IMEI of the UE.
2) To verify that after receipt of a CM SERVICE REJ ECT message from the SS, the UE abandons the emergency
call establishment.
Initial Conditions
- System Simulator:
- User Equipment:
- the UE is in state "MM idle, no IMSI", no USIM inserted.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2290
Test procedure
The UE is made to initiate an emergency call. The call is established without authentication, and security. The SS
responds to the CM SERVICE REQUEST from the UE with a CM SERVICE REJ ECT message specifying in the reject
cause IE the reject cause value "IMEI not accepted". The SS then verifies for during 5 seconds that the UE does not
send a layer 3 message. Then the call is cleared by the SS. The SS verifies during 20 seconds after disconnection of the
main signalling link that the UE does not initiate a RRC connection establishment.
Expected Sequence
UE SS
1 UE The "emergency number" is entered. One of the
following emergency numbers shall be used: 000,
08, 112, 110, 118, 119, 911 or 999.
call.
3 Void
4 Void
establishment". The mobile identity IE specifies
the IMEI of the UE. The cipher key sequence
number IE indicates "no key is available".
6 <-- CM SERVICE REJ ECT The reject cause IE specifies reject cause value
#5, "IMEI not accepted".
7 SS During 5 seconds, the SS verifies that the UE
does not send L3 messages.
8 Void
9 Void
10 SS During 20 seconds, the SS verifies that the UE
does not initiate a RRC connection establishment

Specific Message Contents:
None.
emergency call establishment, mobile identity IMEI and cipher key sequence number no key is available.
In step 6 of the Expected Sequence the UE shall abandon the emergency call establishment.

14 Interoperability Radio Bearer Tests
14.1 General information for interoperability radio bearer tests
The purpose of the interoperability radio bearer test cases are to ensure interoperability of UE's in different regions and
networks. For this purpose representative radio bearer configurations that will be used in real network implementations
have been defined in TS 34.108 [9], clause 6.10.
The applicability of radio bearer tests is dependent on the UE uplink and downlink radio access capabilities and UE
support tele- and bearer-services. See TS 34.123-2, annex B for applicability of the specific test cases.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2291
14.1.1 Generic radio bearer test procedure for single RB configurations
This procedure is used to test single radio bearer configurations and speech only radio bearers. For testing of multiple
radio bearer combinations as well as for testing simultaneous transmission and reception of user data and signalling data
then the procedure as specified in 14.1.2 should be used.
Initial conditions
UE in idle mode
Test procedure
a) The SS establish setup the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the
actual radio bearer test.
b) The SS limits the UE allowed uplink transport format combinations according to the "Restricted UL TFCIs", as
specified for the sub-test of the actual radio bearer test, using the RRC transport format combination control
procedure. See note 1.
c) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio
bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio
bearer test. See note 2.
d) The SS transmits, for all radio bearers under test, one or more RLC SDUs having the size equal to the "Test data
size" as specified for the sub-test of the actual radio bearer test. See note 3.
e) The SS checks that, for all radio bearers under test, the content of the received RLC SDU has the correct content
and is received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the
UE loopback of RLC SDUs.
f) The SS opens the UE test loop.
g) Steps b) to f) are repeated for all sub-tests
i) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The restricted set of TFCIs shall contain all possible TFCI that could happen in a sub-test. The actual TTI
of the different radio bearers and signaling radio bearers as well as the possible UE processing delays
shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set of
TFCIs as specified in TS 25.331, clause 8.6.5.2.
NOTE 2: Selection of UL RLC SDU size parameter:
For the case when the reference radio bearer configuration under test uses RLC transperant mode in
downlink and is not configured for segmented operation then the radio bearer test case shall set the UL
RLC SDU size equal to the UL RLC PDU size. See [7] TS 25.322 for details regarding UE operation in
RLC transperent mode. In case the reference radio bearer configuration under test does not use RLC
transparent mode then the UL RLC SDU size parameter shall be selected to achieve loop back of all test
data received in the DL RLC SDU, i.e. the UL RLC SDU size is set to the nearest multiple of the payload
size of the UL TF under test minus the size of the length indicator and expansion bit which is equal or
bigger than the test data size. For some reference radio bearer configurations this may cause the UE to
return the UL RLC SDU in more than one TTI, i.e. in case no UL TF is available to cover the UL RLC
SDU size. However, as the test procedure only send downlink test data once there is no risk for the UE
transmission buffer to become full even if the returned RLC SDUs need to be tranmitted in more than one
TTI.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2292
NOTE 3: Selection of test data size:
downlink and is not configured for segmented operation then the radio bearer test case shall use a DL
RLC SDU size (defined by the "Test data size" parameter) equal to the DL RLC PDU size. See [7] TS
25.322 for details regarding UE operation in RLC transperent mode. In case the reference radio bearer
configuration under test does not use RLC transparent mode in downlink, the DL RLC SDU size/ test
data size shall be set equal to the payload size of the DL TF under test minus the size of the length
indicator and the expansion bit.
Expected sequence
CS paging procedure
UE SS
1 <-- SYSTEM INFORMATION (BCCH) Broadcast
2 <-- PAGING TYPE 1 (PCCH) Paging (CS domain, TMSI)
3 --> RRC CONNECTION REQUEST (CCCH) RRC
4 <-- RRC CONNECTION SETUP (CCCH) RRC
5 --> RRC CONNECTION SETUP COMPLETE (DCCH) RRC
6 --> PAGING RESPONSE (DCCH) RR
6a <-- AUTHENTICATION REQUEST
6b --> AUTHENTICATION RESPONSE
6c <-- SECURITY MODE COMMAND
6d --> SECURITY MODE COMPLETE

PS paging procedure
UE SS
2 <-- PAGING TYPE 1 (PCCH) Paging (PS domain, P-TMSI)
6a --> SERVICE REQUEST (DCCH) GMM

6b <-- SECURITY MODE COMMAND RRC see note 1
6c --> SECURITY MODE COMPLETE RRC see note 1

Note 1 In addition to activate integrity protection Step 6b and Step 6c are inserted in order to stop T3317 timer in
the UE, which starts after transmitting SERVICE REQUEST message.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2293
UE SS
1..6 <--
-->
Paging Use the CS paging procedure for testing of
CS and combined CS/PS reference radio
bearer configurations.

Use the PS paging procedure for testing of
PS reference radio bearer configurations.
8 --> ACTIVATE RB TEST MODE COMPLETE (DCCH) TC
9 <-- RADIO BEARER SETUP (DCCH) RRC. For the PS radio bearer the pdcp
info IE must be omitted.
10 --> RADIO BEARER SETUP COMPLETE (DCCH) RRC
11 <-- TRANSPORT FORMAT COMBINATION CONTROL
(DCCH)
RRC
"Restricted UL TFCIs", as specified for the
sub-test
UE test mode 1
RLC SDU size is for every active radio
bearer set to "UL RLC SDU size", as
specified for the sub-test.
13 --> CLOSE UE TEST LOOP COMPLETE (DCCH) TC
14 <-- DOWNLINK RLC SDU Send test data using the downlink
transport format combination under test

15 --> UPLINK RLC SDU

16 <-- OPEN UE TEST LOOP (DCCH) TC
17 --> OPEN UE TEST LOOP COMPLETE (DCCH) TC
18 Repeat steps 11 to 17 for every sub-test.
19 RB RELEASE RRC
Optional step
20 <-- DEACTIVATE RB TEST MODE TC
Optional step
21 --> DEACTIVATE RB TEST MODE COMPLETE TC
Optional step

14.1.2 Generic test procedure for testing multi-RB combinations and
simultaneous signalling
This procedure is used to test multiple radio bearer combinations. This procedure is also used to verify simultaneous
transmission and reception of user data and signalling data.
Initial conditions
UE in idle mode
Test procedure
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual
radio bearer test. For the case when the reference radio bearer configuration includes radio bearers for both CS
and PS domain then the radio bearer setup procedure has to be performed once per domain. The first radio bearer
setup procedure shall perform configuration of the physical channel for the radio bearer combination under test
as well as the transport channels for the CS radio bearer(s),also the transport format combination set for only CS
radio bearers has to provided. The second radio bearer procedure shall perform the configuration for the
transport channel for the PS radio bearers . The Physical channel configuration shall be done for both CS and PS
radio bearers combined. Here the transport format combination set for both CS and PS radio bearers shall be
provided.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2294
d) The SS starts transmitting continous test data for all radio bearers under test. The number of RLC SDUs to
transmit every TTI and the size "Test data size" is specified for each sub-test of the actual radio bearer test. See
note 3.
e) The SS waits the time T1 equal to 12 times the largest TTI. See note 4
f) SS transmit a MEASUREMENT CONTROL message requesting periodic reporting with a period of T2.
g) SS waits the time equal to 2 times T2
h) During step e) to g) the SS checks that, for all radio bearers under test, the content of the received RLC SDUs
have the correct content and is received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2
for details regarding the UE loopback of RLC SDUs.
i) The SS opens the UE test loop.
j) Steps b) to i) are repeated for all sub-tests
i) The SS may optionally deactivate the radio bearer test mode.
RLC transperent mode. In case the reference radio bearer configuration under test does not use RLC
transparent mode then, as the test procedure is based on continous downlink transmission of test data in
sub-sequent TTIs, the UL RLC SDU size parameter shall be selected to adopt to the uplink data rate and
to the uplink/downlink TTI ratio. Selection of UL RLC SDU size for the different radio bearers under test
should be such that the UE returns data in sub-sequent TTIs without causing the UE transmission buffer
to become full. To achieve this the UL RLC SDU size shall be set to UL TF payload size under test,
minus the size of length indicator and expansion bit, and divided by the ratio between downlink and
uplink TTI. E.g. for a AM radio bearer having the the uplink RLC payload size equal to 320, the
downlink TTI equal to 10 ms, and the uplink TTI equal to 20 ms, then for the transport format 4x336 (TF
payload size =4x320=1280 bits) the UL RLC SDU size parameter should be set to 632 bits
(=1280bits/(20ms/10ms)- 8 bits).
25.322 for details regarding UE operation in RLC transperent mode. In case the reference radio bearer
NOTE 4: [10] TS 34.109 clause 5.3.2.9 defines the loopback delay requirement for UE test loop mode 1 to be max
10 times actual TTI of a radio bearer when RLC and MAC is operated in transparent mode. As
RLC/MAC may be operated in non-transparent modes depending on the actual reference radio bearer
configuration to be tested an additional 2 TTI have been added to secure that UE starts transmitting data
in uplink before SS transmit the MEASUREMENT CONTROL message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2295
Expected sequence
CS paging procedure
UE SS

PS paging procedure
UE SS


Note 1 In addition to activate integrity protection Step 6b and Step 6c are inserted in order to stop T3317 timer in

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2296
UE SS
1..6 <--
-->

Case A: CS or PS radio bearers onl y
A9 <-- RADIO BEARER SETUP (DCCH) RRC
A10 --> RADIO BEARER SETUP COMPLETE (DCCH) RRC
Case B: CS + PS radio bearers
B9 <-- RADIO BEARER SETUP (DCCH) RRC
CS radio bearer(s) are configured
B10 --> RADIO BEARER SETUP COMPLETE (DCCH) RRC
B10a <-- SECURITY MODE COMMAND See note
B10b --> SECURITY MODE COMPLETE
B10c <-- RADIO BEARER SETUP (DCCH) RRC
PS radio bearer(s) are configured. For the
PS radio bearer the poll-SDU value must
be set to 4 and the pdcp info IE must be
omitted.
B10d --> RADIO BEARER SETUP COMPLETE (DCCH) RRC
(DCCH)
RRC
sub-test
UE test mode 1
14a <--
-->
Test data SS sends continues test data in every TTI
using the downlink transport format
combination under test. The number of
RLC SDUs and their sizes are specified in
the actual test case.

SS checks returned data
14b Wait T1 SS continue to send data every TTI and
check the returned data for time T1
T1 =12 times the max TTI in the actual
radio bearer combination under test
15a <--
-->

<--
Test data (DTCH) +

MEASUREMENT CONTROL (DCCH)
SS continues sending test data in every
TTI.
SS sends a MEASUREMENT CONTROL
message simultaneously to the test data
requesting periodic reporting at interval T2
15b <--
-->

-->
Test data (DTCH) +

MEASUREMENT REPORT (DCCH)
SS continue to send data in every TTI and
check the returned data for time 2xT2

SS checks that at least one
MEASUREMENT REPORT message is
received
19 RB RELEASE (DCCH) RRC
Optional step
20 <-- DEACTIVATE RB TEST MODE (DCCH) TC
Optional step
21 --> DEACTIVATE RB TEST MODE COMPLETE (DCCH) TC
Optional step
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2297
UE SS
Note. For case B (CS+PS radio bearers) the second security mode procedure is needed to enable testing of
ciphering on the PS radio bearers. For the CS domain the security mode procedure is performed as part of
the CS paging procedure.

14.1.2a Generic test procedure for testing multi-RB combinations and
simultaneous signalling in case of DSCH
This procedure is used to test multiple radio bearer combinations where PS data goes on the DSCH. This procedure is
also used to verify simultaneous transmission and reception of user data and signaling data.
Initial conditions
UE in idle mode
Test procedure
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual
radio bearer test. For the case when the reference radio bearer configuration includes radio bearers for both CS
and PS domain then the radio bearer setup procedure has to be performed once per domain. The first radio bearer
setup procedure shall perform configuration of the physical channel for the radio bearer combination under test
as well as the transport channels for the CS radio bearer(s), also the transport format combination set for only CS
radio bearers has to be provided. The second radio bearer procedure shall perform the configuration for the
transport channel for the PS radio bearers.
procedure. Here first time only the TFCs for the data on CS RAB and the data on PS RAB are restricted.
d) The SS transmits test data on all radio bearers under test. The number of RLC SDUs to transmit every TTI and
the size "Test data size" is specified for each sub-test of the actual radio bearer test. See note 2.
e) The SS checks that UE has looped back the data on the CS and PS Radio bearer.
f) The SS opens the UE test loop.
g) SS uses the RRC transport format combination control procedure. And now restricts the TFCs for the data on CS
RAB and the data on PS RAB and also on SRB.
h) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio
i) SS transmit data on the CS RAB a MEASUREMENT CONTROL message requesting periodic reporting with a
period of T2.
j) SS transmits the data on PS RAB.
k) SS waits the time equal to 2 times T2
l) SS checks that, for all radio bearers under test, the content of the received RLC SDUs have the correct content
and is received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the
UE loop back of RLC SDUs.
m) The SS opens the UE test loop.
n) (Void)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2298
o) Steps b) to m) are repeated for all sub-tests
p) The SS may optionally release the radio bearer.
q) The SS may optionally deactivate the radio bearer test mode.
For the case when the reference radio bearer configuration under test uses RLC transparent mode in
RLC transparent mode. Selection of UL RLC SDU size for the different radio bearers under test should
be such that the UE returns data in sub-sequent TTIs without causing the UE transmission buffer to
become full. To achieve this the UL RLC SDU size shall be set to UL TF payload size under test, minus
the size of length indicator and expansion bit, and divided by the ratio between downlink and uplink TTI.
E.g. for a AM radio bearer having the uplink RLC payload size equal to 320, the downlink TTI equal to
10 ms, and the uplink TTI equal to 20 ms, then for the transport format 4x336 (TF payload size =
4x320=1280 bits) the UL RLC SDU size parameter should be set to 632 bits (=1280bits/(20ms/10ms)- 8
bits).
For the case when the reference radio bearer configuration under test uses RLC transparent mode in
25.322 for details regarding UE operation in RLC transparent mode. In case the reference radio bearer
Expected sequence
CS paging procedure
UE SS

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2299
PS paging procedure
UE SS


NOTE 1 In addition to activate integrity protection Step 6b and Step 6c are inserted in order to stop T3317 timer in
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2300
Expected sequence for DSCH multi RAB test cases.
UE SS
1..6 <--
-->

Case A: CS or PS radio bearers onl y
A9 RADIO BEARER SETUP (DCCH) RRC
A10 RADIO BEARER SETUP COMPLETE (DCCH) RRC
Case B: CS + PS radio bearers
B9 RADIO BEARER SETUP (DCCH) RRC
CS radio bearer(s) are configured
B10 RADIO BEARER SETUP COMPLETE (DCCH) RRC
B10a SECURITY MODE COMMAND See Note
B10b SECURITY MODE COMPLETE RRC
B10c RADIO BEARER SETUP (DCCH) RRC
PS radio bearer(s) are configured
B10c RADIO BEARER SETUP COMPLETE (DCCH) RRC
(DCCH)
RRC
sub-testHere the UL TFS are restricted to
test the simultaneous data on CS and PS
RAB.
UE test mode 1
14a <--

Test data (DTCH 1) and Test data on DTCH 2

SS Sends the data on the CS RAB
(DPCH).SS Sends the data on the PS
RAB .(PDSCH)
(Note 1)

14b
Test data (DTCH 1) +Test Data (DTCH 2)
SS Receives the data on CS RAB, PS
RAB
14c <-- OPEN UE TEST LOOP (DCCH) TC
14d --> OPEN UE TEST LOOP COMPLETE (DCCH) TC
15a <-- TRANSPORT FORMAT COMBINATION CONTROL
(DCCH)
RRC
sub-test
Here the UL TFS are restricted to test the
simultaneous data on CS and PS RAB and
SRB
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2301
UE SS
15b <-- CLOSE UE TEST LOOP (DCCH) TC
UE test mode 1
15c --> CLOSE UE TEST LOOP COMPLETE (DCCH) TC
15d <--

Test data (DTCH 1) and Test data on DTCH 2

SS Sends the data on the CS RAB
(DPCH). SS Sends the data on the PS
RAB. (PDSCH)
(Note 1)

15e MEASUREMENT CONTROL (DCCH) SS sends a MEASUREMENT CONTROL
message simultaneously to the test data
requesting periodic reporting at interval T2
(Note 1)
15f -->

-->
Test data (DTCH 1) +Test Data (DTCH 2)

MEASUREMENT REPORT (DCCH)
SS Receives the data on CS RAB, PS
RAB and the Measurement Control
Report.
SS Shall get at least on measurement
Control report.message
(Note 1)
19 RB RELEASE (DCCH) RRC
Optional step
20 <-- DEACTIVATE RB TEST MODE (DCCH) TC
Optional step
21 --> DEACTIVATE RB TEST MODE COMPLETE (DCCH) TC
Optional step
Note. For case B (CS+PS radio bearers) the second security mode procedure is needed to enable testing of
ciphering on the PS radio bearers. For the CS domain the security mode procedure is performed as part of
the CS paging procedure.

NOTE 1:
Here using the test steps 11 to 14d, the simultaneous data on the CS and PS RAB can be tested.
And using the steps 15a to 15f, the simultaneous data on CS RAB, PS RAB and SRB can be tested.
For testing the simultaneous data on CS RAB, PS RAB and SRB, following procedure is used.
First data on the CS RAB is sent. Then in the next step Measurement Control message is sent.
In the Downlink the restricted transport format combination will be (1 1), that SS MAC has to send the data on CS
RAB and the measurement control message on SRB simultaneously.
Here it is assumed that, since the transport format combination (1, 0) (that is send only data) will not be available in the
DL, the MAC has to wait until it get something to transmit on the SRB.
Then data on the PS RAB is sent.
With this on the UE UL Side, the data will be available on both CS and PS RAB and also on the SRB. With this the
transport format combination (1,1, 1) that is simultaneous data on RAB and SRB can be tested in the uplink.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2302
RADIO BEARER SETUP message: AM or UM (Packet to CELL_DCH from CELL_DCH in PS))
New DSCH-RNTI 0000 0000 0000 0010B
- RB mapping info
- Downlink transport channel type DSCH
- DL DSCH Transport channel identity 19
Added or Reconfigured TrCH information list 1 DCH added, 1 DCH reconfigured
transport channel

- SCCPCH TFCS Not Present
- CHOICE mode FDD
- DL DCH TFCS
- CHOICE TFCI signalling Split
- Split Type Hard
- Length of TFCI(field2) 5
- TFCS complete reconfigure
- CHOICE CTFC Size
- CTFC information This IE is repeated for TFC numbers and reference to
TS34.108 clause 6.10.2.4
- CTFC Reference to TS34.108 clause 6.10.2.4 Parameter Set
- Power offset information Not present
- CHOICE Signalling method Explicit
- TFCS explicit configuration
- CTFC information This IE is repeated for TFC numbers and reference to
TS34.108 clause 6.10.2.4
- CTFC Reference to TS34.108 clause 6.10.2.4 Parameter Set
- Power offset information Not present
Deleted TrCH information list Not Present
Added or Reconfigured TrCH information list
- Added or Reconfigured DL TrCH information
- Downlink transport channel type DSCH
- TFS
- CHOICE Transport channel type Dedicated transport channels
- RLC Size Reference to TS34.108 clause 6.10 Parameter Set
- Number of TBs and TTI List (This IE is repeated for TFI number.)
- Transmission Time Interval Not Present
- Number of Transport blocks Reference to TS34.108 clause 6.10 Parameter Set
- Transmission time interval Reference to TS34.108 clause 6.10 Parameter Set
- Type of channel coding Reference to TS34.108 clause 6.10 Parameter Set
- Coding Rate Reference to TS34.108 clause 6.10 Parameter Set
- Rate matching attribute Reference to TS34.108 clause 6.10 Parameter Set
- CRC size Reference to TS34.108 clause 6.10 Parameter Set
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2303
- DCH quality target Not Present
- CHOICE DL parameters Same as UL
- UL TrCH identity 5
- Uplink DPCH power control info
- DPCCH power offset -6dB
- PC Preamble 1 frame
- SRB delay 7 frames
- Power Control Algorithm Algorithm1
- TPC step size 1dB
- Number of DPDCH Not Present(1)
- spreading factor Reference to TS34.108 clause 6.10 Parameter Set
- Number of FBI bit Reference to TS34.108 clause 6.10 Parameter Set
CHOICE Mode FDD
- Downlink PDSCH information
- PDSCH with SHO DCH Info Not Present
- PDSCH code mapping
- DL Scrambling Code Primary scrambling code
- Choice signalling method Explicit
- PDSCH code info This IE is repeated for TFC numbers and reference to
TS34.108 clause 6.10.2.4
- Code number Reference to TS34.108 clause 6.10 Parameter Set
- multi-code info 1
- Timing indicator Maintain
- CHOICE mode FDD
- Fixed or Flexible Position Reference to TS34.108 clause 6.10 Parameter Set
- CHOICE SF Reference to TS34.108 clause 6.10 Parameter Set
- DPCH compressed mode info Not Present
- Choice mode FDD
- Primary scrambling code Reference to clause 6.1 "Default settings (FDD)"
- PDSCH code mapping
- DL Scrambling Code Primary scrambling code
- Choice signalling method Explicit
- PDSCH code info This IE is repeated for TFC numbers and reference to
TS34.108 clause 6.10.2.4
- Code number Reference to TS34.108 clause 6.10 Parameter Set
- multi-code info 1
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2304
- Code number 0

14.1.3 General information interoperability radio bearer tests for HS-DSCH
14.1.3.1 Radio bearer test parameters for UE categories
In the radio bearer tests on radio bearers mapped on HS-DSCH, the following UE specific parameters should
be used.
Table 14.1.3.1.1: FDD HS-DSCH physical layer and RLC and MAC-hs parameters for FDD HS-DSCH
physical layer categories
HS-DSCH
category
Maximum
number of
HS-DSCH
codes
received
Minimum
inter-TTI
interval
Maximum
number of bits
of an HS-DSCH
transport block
received within
an HS-DSCH
TTI
Total
number of
soft
channel
bits

Supported
modulation
Maximum
number of
AM RLC
entities
Minimum
total RLC
AM and
MAC-hs
buffer size
[kBytes]
Category 1 5 3 7298 19200 QPSK,
16QAM
6 50
Category 2 5 3 7298 28800 QPSK,
16QAM
6 50
Category 3 5 2 7298 28800 QPSK,
16QAM
6 50
Category 4 5 2 7298 38400 QPSK,
16QAM
6 50
Category 5 5 1 7298 57600 QPSK,
16QAM
6 50
Category 6 5 1 7298 67200 QPSK,
16QAM
6 50
Category 7 10 1 14411 115200 QPSK,
16QAM
8 100
Category 8 10 1 14411 134400 QPSK,
16QAM
8 100
Category 9 15 1 20251 172800 QPSK,
16QAM
8 150
Category 10 15 1 27952 172800 QPSK,
16QAM
8 150
Category 11 5 2 3630 14400 QPSK 6 50
Category 12 5 1 3630 28800 QPSK 6 50

14.1.3.2 Generic test procedure for single HS-DSCH radio bearer configurations
This procedure is used to test single HS-DSCH radio bearer configurations. The procedure is run once for each sub-test
of the actual HS-DSCH radio bearer test case.
Definition of test variables:
N
codes
Number of HS-DSCH codes (1..15, maximum number dependent on UE category)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2305
M Type of modulation scheme (QPSK, 16QAM)
k
i
TFRI signalled on the HS-SCCH value
K
0,I
See table 14.1.3.2.1
k
t
Transport Block Size index (=k
i
+k
0,I
), see table 14.6.1.2.2
TB
size
Transport Block size
N
PDUs
Number of MAC-d PDUs
MAC-hs_header_size MAC-hs header size for the reference HS-DSCH radio bearer configuration under test.
MAC-d_PDU_size MAC-d PDU size for the reference HS-DSCH radio bearer configuration under test.

Table 14.1.3.2.1: Values of k
0,i
for different numbers of channelization codes and modulation schemes
Combination I Modulation
scheme
Number of
channelization codes
i
k
, 0

0 QPSK 1 1
1 2 40
2 3 63
3 4 79
4 5 92
5 6 102
6 7 111
7 8 118
8 9 125
9 10 131
10 11 136
11 12 141
12 13 145
13 14 150
14 15 153
15 16QAM 1 40
16 2 79
17 3 102
18 4 118
19 5 131
20 6 141
21 7 150
22 8 157
23 9 164
24 10 169
25 11 175
26 12 180
27 13 184
28 14 188
29 15 192

Table 14.1.3.2.2: Mapping of HS-DSCH Transport Bl ock Size for FDD to value of index k
t
(=k
i
+ k
0,I
)
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2306
Index TB Size Index TB Size Index TB Size
1 137 86 1380 171 6324
2 149 87 1405 172 6438
3 161 88 1430 173 6554
4 173 89 1456 174 6673
5 185 90 1483 175 6793
6 197 91 1509 176 6916
7 209 92 1537 177 7041
8 221 93 1564 178 7168
9 233 94 1593 179 7298
10 245 95 1621 180 7430
11 257 96 1651 181 7564
12 269 97 1681 182 7700
13 281 98 1711 183 7840
14 293 99 1742 184 7981
15 305 100 1773 185 8125
16 317 101 1805 186 8272
17 329 102 1838 187 8422
18 341 103 1871 188 8574
19 353 104 1905 189 8729
20 365 105 1939 190 8886
21 377 106 1974 191 9047
22 389 107 2010 192 9210
23 401 108 2046 193 9377
24 413 109 2083 194 9546
25 425 110 2121 195 9719
26 437 111 2159 196 9894
27 449 112 2198 197 10073
28 461 113 2238 198 10255
29 473 114 2279 199 10440
30 485 115 2320 200 10629
31 497 116 2362 201 10821
32 509 117 2404 202 11017
33 521 118 2448 203 11216
34 533 119 2492 204 11418
35 545 120 2537 205 11625
36 557 121 2583 206 11835
37 569 122 2630 207 12048
38 581 123 2677 208 12266
39 593 124 2726 209 12488
40 605 125 2775 210 12713
41 616 126 2825 211 12943
42 627 127 2876 212 13177
43 639 128 2928 213 13415
44 650 129 2981 214 13657
45 662 130 3035 215 13904
46 674 131 3090 216 14155
47 686 132 3145 217 14411
48 699 133 3202 218 14671
49 711 134 3260 219 14936
50 724 135 3319 220 15206
51 737 136 3379 221 15481
52 751 137 3440 222 15761
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2307
53 764 138 3502 223 16045
54 778 139 3565 224 16335
55 792 140 3630 225 16630
56 806 141 3695 226 16931
57 821 142 3762 227 17237
58 836 143 3830 228 17548
59 851 144 3899 229 17865
60 866 145 3970 230 18188
61 882 146 4042 231 18517
62 898 147 4115 232 18851
63 914 148 4189 233 19192
64 931 149 4265 234 19538
65 947 150 4342 235 19891
66 964 151 4420 236 20251
67 982 152 4500 237 20617
68 1000 153 4581 238 20989
69 1018 154 4664 239 21368
70 1036 155 4748 240 21754
71 1055 156 4834 241 22147
72 1074 157 4921 242 22548
73 1093 158 5010 243 22955
74 1113 159 5101 244 23370
75 1133 160 5193 245 23792
76 1154 161 5287 246 24222
77 1175 162 5382 247 24659
78 1196 163 5480 248 25105
79 1217 164 5579 249 25558
80 1239 165 5680 250 26020
81 1262 166 5782 251 26490
82 1285 167 5887 252 26969
83 1308 168 5993 253 27456
84 1331 169 6101 254 27952
85 1356 170 6211

14.1.3.2.1 Initial conditions
UE in idle mode
14.1.3.2.2 Test procedure
a) The SS establishes the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual
radio bearer test. See note 1.
bearer test.
d) The SS sets M= QPSK.
e) The SS sets N
codes
=1.
f) The SS sets k
0,i
to the value according to table 14.1.3.2.1 based on the actual value of M and N
codes
.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2308
g) The SS sets the test parameter k
i
to 0.
h) The SS calculates the index value k
t
(=k
i
+k
0,I
) and lockup the transport block size, TB
size
, for the actual k
t
in
table 14.1.3.2.2

If TB
size
is bigger than Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH
TTI for the actual UE category then SS continues with step e).
i) The SS calculates the maximum number of MAC-d PDUs that fits into the MAC-hs transport block:

N
PDUs
=ceil((TB
size
MAC-hs_header_size) / MAC-d_PDU_size)

If N
PDUs
is bigger than 70 then SS continues with step e).
j) The SS sends a MAC-hs PDU containing N
PDUs
MAC-d PDUs, where each MAC-d PDU contains a RLC SDU
of size DL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit). See note 3.
k) For each HARQ processes under test the SS checks that the UE HARQ buffer is sufficient to store the
transmission, and if so a MAC-hs PDU of size TB
size
is transmitted with TFRI=k
0,i
. Data is transmitted every
Nth TTI where N is given by the minimum inter-TTI interval.
l) The SS checks that the content of the UE returned RLC SDU has the correct content and is received having the
correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC
SDUs.
m) The SS increments the test parameter k
i
by 1. If k
i
is less than 63 then SS repeats steps h) to m).
n) The SS increments the test parameter N_Code by 1. If N_code is less or equal to the Maximum number of HS-
DSCH codes received for the actual UE category under test then the SS repeats test steps f) to n).
o) If Modulation =QPSK and UE Category is 1 to 10 then the SS sets the test parameter Modulation to 16QAM and
repeats steps e) to o).
p) The SS opens the UE test loop.
q) Steps b) to p) are repeated for all sub-tests
r) The SS may optionally release the radio bearer.
s) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The
number of soft channel bits per HARQ process is split equally among the number of HARQ processes
configured for the actual sub-test - i.e. Total number of soft channel bits for the UE category according
to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering
queues are 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC
Transmission window size and RLC Receiving window size shall be configured as specified for the actual
sub-test.
NOTE 2: The restricted set of uplink TFCIs shall contain all possible TFCI that could happen in a sub-test. The
actual TTI of the different radio bearers and signaling radio bearers as well as the possible UE processing
delays shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set
of TFCIs as specified in TS 25.331, clause 8.6.5.2.
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that
the UE capability for Minimum total RLC AM and MAC-hs buffer size is not exceeded for the UE
category under test.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2309
Expected sequence
UE SS
6 --> SERVICE REQUEST (DCCH) GMM

7 <-- SECURITY MODE COMMAND RRC see note 1
8 --> SECURITY MODE COMPLETE RRC see note 1
11 <-- RADIO BEARER SETUP (DCCH) RRC. For the PS radio bearer the pdcp
info IE must be omitted.
12 --> RADIO BEARER SETUP COMPLETE (DCCH) RRC
(DCCH)
RRC
sub-test
UE test mode 1
16 SS The SS calculates test data for the first
TFRC, Ncodes and M.
17 <-- DOWNLINK MAC-hs PDU (HARQ process 1)
..
DOWNLINK MAC-hs PDU (HARQ process N)
Send test data for the number of HARQ
processes to be tested

18 --> UPLINK RLC SDU
..
UPLINK RLC SDU
The number of returned RLC SDUs
depends on the TFRC and the number of
HARQ processed to be tested.

19 SS The SS calculates test data for next TFRC
and repeat steps 18 to 19 until all TFRCs
have been tested.
22 RB RELEASE RRC
Optional step
23 <-- DEACTIVATE RB TEST MODE TC
Optional step
24 --> DEACTIVATE RB TEST MODE COMPLETE TC
Optional step

Note 1 In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in
14.2 Combinations on DPCH
14.2.1 Stand-alone UL:1.7 DL:1.7 kbps SRBs for DCCH
Test to verify establishment and signalling of stand-alone signalling reference radio bearer configuration as specified in
TS 34.108, clause 6.10.2.4.1.1.
The test case is performed by running test case 9.4.1 (Location updating / accepted) using the stand-alone signalling
reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.1.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2310
Test to verify establishment and signalling of stand-alone signalling reference radio bearer configuration as specified in
TS 34.108, clause 6.10.2.4.1.2.
The test case is performed by running test case 9.4.1 (Location updating / accepted) using the stand-alone signalling
reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.1.2.
Impicitely tested.
NOTE The stand-alone UL:13.6 DL:13.6 kbps SRBs for DCCH in TS 34.108, clause 6.10.2.4.1.3 is the default
signalling radio bearer used in the generic setup procedure as specified in TS 34.108 clasue 7.
14.2.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB +UL:3.4
DL:3.4 kbps SRBs for DCCH
The UE shall be able to establish the UTRAN requested radio bearers within the UE's signaled radio access capabilities.
The UE shall correctly transfer user data from peer to peer RLC entitities according to the requested radio bearer
configuration.
Reference(s)
3GPP TS 25.331, clause 8.2.1
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in
TS 34.108, clause 6.10.2.4.1.4.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 0x81 0x103 0x60 0x148
TF1, bits 1x39 1x103 1x60 1x148
TF2, bits 1x81 N/A N/A N/A

Uplink TFCS:
TFCI (RB5, RB6, RB7, DCCH)
UL_TFC0 (TF0, TF0, TF0, TF0)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2311
Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 1x0 0x103 0x60 0x148
TF1, bits 1x39 1x103 1x60 1x148

Downlink TFCS:
DL_TFC0 (TF0, TF0, TF0, TF0)

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

Implicitel y tested Restricted
UL TFCIs

(note 1)
UL RLC SDU
size

(note 2)
Test data size

(note 2)
1 DL_TFC1 UL_TFC1 DL_TFC0, DL_TFC3, UL_TFC0,
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 103 bits
RB7: 60 bits
RB5: 39 bits
RB6: No data
RB7: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5
RB5: 81 bits
RB6: 103 bits
RB7: 60 bits
RB5: 81 bits
RB6: 103 bits
RB7: 60 bits
NOTE 1: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC3 are part of minimum set of TFCIs.
NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.

See 14.1.1 for test procedure.
See 14.1.1 for definition of step 10 and step 15.
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE transmitted transport format shall be
- for sub-test 1: RB5/TF1 (1x39).
- for sub-test 2: RB5/TF2 (1x81); RB6/TF1 (1x103); and RB7/TF1 (1x60).
3. At step 15 the UE shall return
- for sub-test 1: an RLC SDU on RB5 having the same content as sent by SS; and no data shall be received on
RB6 or RB7.
- for sub-test 2: an RLC SDU on each of RB5, RB6 and RB7 having the same content as sent by SS
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2312
14.2.4a Conversational / speech / UL:(12.2 7.95 5.9 4.75) DL:(12.2 7.95 5.9
4.75) kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH.
See clause 14.2.4.1.
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause
6.10.2.4.1.4a.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 0x81 0x103 0x60 0x148
TF1, bits 1x39 1x53 1x60 1x148
TF2, bits 1x42 1x63 N/A N/A

Uplink TFCS:
TFCI (RB5, RB6, RB7,DCCH)

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 1x0 0x103 0x60 0x148
TF1, bits 1x39 1x53 1x60 1x148

Downlink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2313

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size

(note 2)
Test data size

(note 2)
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC7
RB5: 39 bits
RB6: 103 bits
RB7: 60 bits
RB5: 39 bits
RB6: No data
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC8
RB5: 42 bits
RB6: 53 bits
RB7: 60 bits
RB5: 42 bits
RB6: 53 bits
RB7: No data
UL_TFC
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC9
RB5: 55 bits
RB6: 63 bits
RB7: 60 bits
RB5: 55 bits
RB6: 63 bits
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC10
RB5: 75 bits
RB6: 84 bits
RB7: 60 bits
RB5: 75 bits
RB6: 84 bits
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC11
RB5: 81 bits
RB6: 103 bits
RB7: 60 bits
RB5: 81 bits
RB6: 103 bits
RB7: 60 bits
NOTE 1: UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC4, UL_TFC5 and UL_TFC6 are part of minimum set of
TFCIs.

See clause 14.1.1 for test procedure.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2314
- for sub-test 2: RB5/TF2 (1x42) and RB6/TF1 (1x53)
- for sub-test 5: RB5/TF5 (1x81), RB6/TF4 (1x103) and RB7/TF1 (1x60)
RB6 or RB7.
- for sub-test 2,3 and 4: an RLC SDU on RB5 and RB6 having the same content as sent by SS; and no data
shall be received on RB7.
- for sub-test 5: an RLC SDU on each of RB5, RB6 and RB7 having the same content as sent by SS.
DL: 3.4 kbps SRBs for DCCH
TS 34.108, clause 6.10.2.4.1.5.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 0x65 0x99 0x40 0x148
TF1, bits 1x39 1x99 1x40 1x148

Uplink TFCS:

Downlink TFS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2315

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 1x0 0x99 0x40 0x148
TF1, bits 1x39 1x99 1x40 1x148

Downlink TFCS:

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 99 bits
RB7: 40 bits
RB5: 39 bits
RB6: No data
RB7: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5
RB5: 65 bits
RB6: 99 bits
RB7: 40 bits
RB5: 65 bits
RB6: 99 bits
RB7: 40 bits
NOTE 1: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC3 are part of minimum set of TFCIs
- for sub-test 2: RB5/TF2 (1x65); RB6/TF1 (1x99); and RB7/TF1 (1x40).
RB6 or RB7.
- for sub-test 2: an RLC SDU on each of RB5, RB6 and RB7 having the same content as sent by SS.
14.2.5a Conversational / speech / UL:(10.2, 6.7, 5.9, 4.75) DL:(10.2, 6.7,
5.9, 4.75) kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2316
TS 34.108, clause 6.10.2.4.1.5a.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 0x65 0x99 0x40 0x148
TF1, bits 1x39 1x53 1x40 1x148

Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
RB7
(RAB subflow #3)
DCCH
TFS
TF0, bits 1x0 0x99 0x40 0x148
TF1, bits 1x39 1x53 1x40 1x148

Downlink TFCS:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2317
Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size

(note 2)
Test data size

(note 2)
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC7
RB5: 39 bits
RB6: 99 bits
RB7: 40 bits
RB5: 39 bits
RB6: No data
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC8
RB5: 42 bits
RB6: 53 bits
RB7: 40 bits
RB5: 42 bits
RB6: 53 bits
RB7: No data
UL_TFC
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC9
RB5: 55 bits
RB6: 63 bits
RB7: 40 bits
RB5: 55 bits
RB6: 63 bits
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC10
RB5: 58 bits
RB6: 76 bits
RB7: 40 bits
RB5: 58 bits
RB6: 76 bits
RB7: No data
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC11
RB5: 65 bits
RB6: 99 bits
RB7: 40 bits
RB5: 65 bits
RB6: 99 bits
RB7: 40 bits
TFCIs.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2318
- for sub-test 5: RB5/TF5 (1x65), RB6/TF4 (1x99) and RB7/TF1 (1x40)
- for sub-test 1: an RLC SDU on RB5 having the same content as sent by the SS; and no data shall be received
on RB6 or RB7.
- for sub-test 2, 3 and 4: an RLC SDU on RB5 and RB6 having the same content as sent by the SS; and no data
shall be received on RB7.
- for sub-test 5: an RLC SDU on each of RB5, RB6 and RB7 having the same content as sent by the SS.
TS 34.108, clause 6.10.2.4.1.6.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x75 0x84 0x148
TF1, bits 1x39 1x84 1x148
TF2, bits 1x75 N/A N/A

Uplink TFCS:
TFCI (RB5, RB6, DCCH)
UL_TFC0 (TF0, TF0, TF0)

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x84 0x148
TF1, bits 1x39 1x84 1x148

Downlink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2319
DL_TFC0 (TF0, TF0, TF0)

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 84 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 75 bits
RB6: 84 bits
RB5: 75 bits
RB6: 84 bits
NOTE1: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC3 are part of minimum set of TFCIs.
NOTE2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
- for sub-test 2: RB5/TF2 (1x75) and RB6/TF1 (1x84).
RB6.
- for sub-test 2: an RLC SDU on each of RB5 and RB6 having the same content as sent by SS.
14.2.7 Conversational / speech / UL:7.4 DL:7.4 kbps / CS RAB+UL:3.4
TS 34.108, clause 6.10.2.4.1.7.
Uplink TFS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2320
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x61 0x87 0x148
TF1, bits 1x39 1x87 1x148

Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x87 0x148
TF1, bits 1x39 1x87 1x148

Downlink TFCS:

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 87 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 61 bits
RB6: 87 bits
RB5: 61 bits
RB6: 87 bits
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2321
RB6.
- for sub-test 2: an RLC SDU on each of RB5 and RB6 having the same content as sent by SS
14.2.7a Conversational / speech / UL:(7.4, 6.7, 5.9, 4.75) DL:(7.4, 6.7, 5.9,
4.75) kbps / CS RAB +UL:3.4 DL:3.4 kbps SRBs for DCCH.
TS 34.108, clause 6.10.2.4.1.7a.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x61 0x87 0x148
TF1, bits 1x39 1x53 1x148
TF2, bits 1x42 1x63 N/A

Uplink TFCS:

Downlink TFS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2322

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x87 0x148
TF1, bits 1x39 1x53 1x148

Downlink TFCS:

Sub-tests:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2323
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size

(note 2)
Test data size

(note 2)
UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC7
RB5: 39 bits
RB6: 87 bits

RB5: 39 bits
RB6: No data

UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC8
RB5: 42 bits
RB6: 53 bits

RB5: 42 bits
RB6: 53 bits

UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC9
RB5: 55 bits
RB6: 63 bits

RB5: 55 bits
RB6: 63 bits

UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC10
RB5: 58 bits
RB6: 76 bits

RB5: 58 bits
RB6: 76 bits

UL_TFC6
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4,
UL_TFC5,
UL_TFC6,
UL_TFC11
RB5: 61 bits
RB6: 87 bits

RB5: 61 bits
RB6: 87 bits

TFCIs.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2324
- for sub-test 1: an RLC SDU on RB5 having the same content as sent by the SS; and no data shall be received
on RB6.
- for sub-test 2 to 5: an RLC SDU on RB5 and RB6 having the same content as sent by the SS.
TS 34.108, clause 6.10.2.4.1.8.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x58 0x76 0x148
TF1, bits 1x39 1x76 1x148

Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x76 0x148
TF1, bits 1x39 1x76 1x148

Downlink TFCS:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2325
Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 76 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 58 bits
RB6: 76 bits
RB5: 58 bits
RB6: 76 bits
See clause 14.1.1 for definition of step 10 and step 15.
RB6.
TS 34.108, clause 6.10.2.4.1.9.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x55 0x63 0x148
TF1, bits 1x39 1x63 1x148

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2326
Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x63 0x148
TF1, bits 1x39 1x63 1x148

Downlink TFCS:

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 63 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 55 bits
RB6: 63 bits
RB5: 55 bits
RB6: 63 bits
NOTE2:See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2327
RB6.
TS 34.108, clause 6.10.2.4.1.10.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x49 0x54 0x148
TF1, bits 1x39 1x54 1x148

Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x54 0x148
TF1, bits 1x39 1x54 1x148

Downlink TFCS:

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2328
Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size

(note2)
Test data size

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 54 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 49 bits
RB6: 54 bits
RB5: 49 bits
RB6: 54 bits
RB6.
TS 34.108, clause 6.10.2.4.1.11.
Uplink TFS:
TFI
RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 0x49 0x53 0x148
TF1, bits 1x39 1x53 1x148

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2329
Uplink TFCS:

Downlink TFS:

RB5
(RAB subflow #1)
RB6
(RAB subflow #2)
DCCH
TFS
TF0, bits 1x0 0x53 0x148
TF1, bits 1x39 1x53 1x148

Downlink TFCS:

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size

(note)
Test data size

(note)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC4
RB5: 39 bits
RB6: 53 bits
RB5: 39 bits
RB6: No data
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 42 bits
RB6: 53 bits
RB5: 42 bits
RB6: 53 bits
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2330
RB6.
14.2.12 Conversational / unknown / UL:28.8 DL:28.8 kbps / CS RAB +
UL:3.4 DL:3.4 kbps SRBs for DCCH
See 14.2.4.1.
TS 34.108, clause 6.10.2.4.1.12.
Initial Conditions
The following RLC Info parameter values shall be set by the SS:
Uplink RLC
TM RLC
CHOICE SDU Discard Mode
Timer based no explicit
Timer_discard 100ms
Segmentation indication FALSE
Downlink RLC
TM RLC
NOTE: 'Timer based discard without explicit signalling' is configured in
uplink to secure that the UE will be able to return data in uplink for
the case when the UE test loop function, due to processing delays,
will not deliver the SDUs in one and the same TTI, but instead in
two subsequent TTIs.

Uplink TFS:
TFI
RB5
(28.8 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF0, TF1)
UL_TFC4 (TF1, TF1)
UL_TFC5 (TF2, TF1)

Downlink TFS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2331

RB5
(28.8 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF2, TF0)
DL_TFC3 (TF0, TF1)
DL_TFC4 (TF1, TF1)
DL_TFC5 (TF2, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size
(bits)
(note2 )
Test data size
(bits)

(note 2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC4
RB5: 576 RB5: 576
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 576 RB5: 2x576
NOTE 1: UL_TFC0, UL_TFC1 and UL_TFC3 are part of minimum set of TFCIs.

- for sub-test 2: RB5/TF2 (2x576) or RB5/TF1 (1x576).
- for sub-test 1: an RLC SDU on RB5 having the same content as sent by SS.
- for sub-test 2: two RLC SDUs on RB5 having the same content as sent by SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2332
14.2.13 Conversational / unknown / UL:64 DL:64 kbps / CS RAB +UL:3.4
14.2.13.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB / 20 ms TTI
TS 34.108, clause 6.10.2.4.1.13 for the 20 ms TTI case.
Initial Conditions
Uplink RLC
TM RLC
Timer_discard 100ms
Downlink RLC
TM RLC
NOTE: Timer based discard without explicit signalling is used in uplink to
secure that the UE will be able to return data for the case when the
UE test loop function will not deliver all the SDUs in one and the
same TTI .

Uplink TFS:
TFI
RB5
(64 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 2x640 1x148

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:
TFI
RB5
(64 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 2x640 1x148

Downlink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2333
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 640 RB5: 2x640
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2334
Initial Conditions
Uplink RLC
TM RLC
Timer_discard 100ms
Downlink RLC
TM RLC
same TTI .

Uplink TFS:
TFI
RB5
(64 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 4x640 1x148

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:
TFI
RB5
(64 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 4x640 1x148

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2335
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 640 RB5: 4x640

- for sub-test 1: four RLC SDUs on RB5 having the same content as sent by SS.
14.2.14 Conversational / unknown / UL:32 DL:32 kbps / CS RAB +UL:3.4
See 14.2.4.1.
Initial Conditions
Uplink RLC
TM RLC
Downlink RLC
TM RLC

Uplink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 1x640 1x148

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2336
Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 1x640 1x148

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 640 RB5: 640

See 14.2.4.1.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2337
Initial Conditions
Uplink RLC
TM RLC
Timer_discard 100ms
Downlink RLC
TM RLC
same TTI .

Uplink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 2x640 1x148

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x640 0x148
TF1, bits 2x640 1x148

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2338
Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 640 RB5: 2x640

14.2.15 Streaming / unknown / UL:14.4/DL:14.4 kbps / CS RAB +UL:3.4
See 14.2.4.1.
TS 34.108, clause 6.10.2.4.1.15.
Uplink TFS:
TFI
RB5
(14.4 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2339
Downlink TFS:
TFI
RB5
(14.4 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 576 RB5: 576

See 14.2.4.1.
TS 34.108, clause 6.10.2.4.1.16.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2340
Initial Conditions
Uplink RLC
TM RLC
Timer_discard 100ms
Downlink RLC
TM RLC
same TTI .

Uplink TFS:
TFI
RB5
(28.8 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF0, TF1)
UL_TFC4 (TF1, TF1)
UL_TFC5 (TF2, TF1)

Downlink TFS:

RB5
(28.8 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF2, TF0)
DL_TFC3 (TF0, TF1)
DL_TFC4 (TF1, TF1)
DL_TFC5 (TF2, TF1)

Sub-tests:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2341
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC SDU
size
(bits)
(note 2)
Test data size
(bits)

(note 2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC4
RB5: 576 RB5: 576
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5,
RB5: 576 RB5: 2x576

- for sub-test 2: two RLC SDU on RB5 having the same content as sent by SS.
See 14.2.4.1.
TS 34.108, clause 6.10.2.4.1.17.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2342
Initial Conditions
Uplink RLC
TM RLC
Timer_discard 100ms
Downlink RLC
TM RLC
same TTI .

Uplink TFS:
TFI
RB5
(57.6 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A
TF3, bits 3x576 N/A
TF4, bits 4x576 N/A

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF3, TF0)
UL_TFC4 (TF4, TF0)
UL_TFC5 (TF0, TF1)
UL_TFC6 (TF1, TF1)
UL_TFC7 (TF2, TF1)
UL_TFC8 (TF3, TF1)
UL_TFC9 (TF4, TF1)

Downlink TFS:
TFI
RB5
(57.6 kbps)
DCCH
TFS
TF0, bits 0x576 0x148
TF1, bits 1x576 1x148
TF2, bits 2x576 N/A
TF3, bits 3x576 N/A
TF4, bits 4x576 N/A

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2343
Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF2, TF0)
DL_TFC3 (TF3, TF0)
DL_TFC4 (TF4, TF0)
DL_TFC5 (TF0, TF1)
DL_TFC6 (TF1, TF1)
DL_TFC7 (TF2, TF1)
DL_TFC8 (TF3, TF1)
DL_TFC9 (TF4, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data
size
(bits)
(note)
UL_TFC5,
UL_TFC0,
UL_TFC1,
UL_TFC5,
UL_TFC6
RB5: 576 RB5: 576
UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC5,
UL_TFC7
RB5: 576 RB5:
2x576
UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC5,
UL_TFC8
RB5: 576 RB5:
3x576
UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC4,
UL_TFC5,
UL_TFC9
RB5: 576 RB5:
4x576

- for sub-test 1: one RLC SDU on RB5 having the same content as sent by SS.
- for sub-test 2: two RLC SDU on RB5 having the same content as sent by SS.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2344
- for sub-test 3: three RLC SDU on RB5 having the same content as sent by SS.
- for sub-test 4: four RLC SDU on RB5 having the same content as sent by SS.
14.2.18 Void
14.2.19 Void
14.2.20 Void
14.2.21 Void
14.2.22 Void
14.2.23 Interactive or background / UL:32 DL:8 kbps / PS RAB +UL:3.4
14.2.23.1 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC,10 ms TTI)
See 14.2.4.1.
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108,
clause 6.10.2.4.1.23 for the turbo channel coding and uplink 10 ms TTI case.
Uplink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:
TFI
RB5
(8 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148

Downlink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2345
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs
UL RLC SDU
size
(bits)
(note)
Test data size
(bits)

(note)
UL_TFC2
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3
RB5: 312 RB5: 312

- for sub-test 1: an RLC SDU on RB5 having the same content as the DL RLC SDU sent by the SS.
14.2.23.2 Interactive or background / UL:32 DL:8 kbps / PS RAB / (TC, 20 ms TTI)
See 14.2.4.1.
clause 6.10.2.4.1.23 for the turbo channel coding and uplink 20 ms TTI case.
Uplink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148
TF2, bits 2x336 N/A

Uplink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2346
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF0, TF1)
UL_TFC4 (TF1, TF1)
UL_TFC5 (TF2, TF1)

Downlink TFS:
TFI
RB5
(8 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs

(note1)
UL RLC SDU
size
(bits)
(note2)
Test data size
(bits)

(note2)
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC4
RB5: 312 RB5: 312
UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5
RB5: 632 RB5: 632
NOTE1: : UL_TFC0, UL_TFC1and UL_TFC3 are part of minimum set of TFCIs.
- for sub-test 1 and 2: an RLC SDU on RB5 having the same content as the DL RLC SDU sent by the SS.
14.2.23.3 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 10 ms TTI)
clause 6.10.2.4.1.23 for the convolutional channel coding and uplink 10 ms TTI case.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2347
See test case 14.2.23.1 for test procedure and test requirement.
14.2.23.4 Interactive or background / UL:32 DL:8 kbps / PS RAB / (CC, 20 ms TTI)
clause 6.10.2.4.1.23 for the convolutional channel coding and uplink 20 ms TTI case.
See test case 14.2.23.2 for test procedure and test requirement.
14.2.23a Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4
DL:3.4 kbps SRBs for DCCH.
14.2.23a.1 Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps
SRBs for DCCH / CC
14.2.23a.1.1 Conformance requirement
See 14.2.4.1.
14.2.23a.1.2 Test purpose
6.10.2.4.1.23a, for a convolutional coding case.
14.2.23a.1.3 Method of test
Uplink TFS:
TFI
RB5
(8 kbps)
DCCH

TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148

Uplink TFCS:
TFCI (8 kbps RAB, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF0, TF1)
UL_TFC3 (TF1, TF1)

Downlink TFS:

RB5
(8 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148

Downlink TFCS:
TFCI (8 kbps RAB, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF0, TF1)
DL_TFC3 (TF1, TF1)

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2348
Sub-tests:
Sub-
test
Downlink
TFCS
Under
Test
Uplink
TFCS
Under test

Implicitel y tested Restricted UL
TFCIs
UL RLC
SDU size
(bits)
(note)
Test data size
(bits)

(note)
1 DL_TFC1 UL_TFC1 DL_TFC0, DL_TFC2,
UL_TFC0, UL_TFC2,
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3

RB5: 312

RB5: 312
RB5: Test data size has been set to DL TFS size under test minus 8 bits (size of 7 bit length indicator and
expansion bit). The UL RLC SDU size has been set equal to the uplink TFS size under test minus 8
bits (size of 7 bit length indicator and expansion bit).

14.2.23a.1.4 Test requirements
- for sub-test 1: an RLC SDU on RB5 having the same content as the DL RLC SDU sent by the SS.
14.2.23a.2 Interactive or background / UL:8 DL:8 kbps / PS RAB +UL:3.4 DL:3.4 kbps
SRBs for DCCH / TC
6.10.2.4.1.23a, for a turbo coding case.
See test case 14.2.23a.1 for test procedure and test requirement.
14.2.23b Interactive or background / UL:16 DL:16 kbps / PS RAB +UL:3.4
6.10.2.4.1.23b.
Uplink TFS:
TFI
RB5
(16 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148
TF2, bits 2x336 N/A

Uplink TFCS:
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2349
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF0, TF1)
UL_TFC4 (TF1, TF1)
UL_TFC5 (TF2, TF1)

Downlink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148
TF2, bits 2x336 N/A

Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF2, TF0)
DL_TFC3 (TF0, TF1)
DL_TFC4 (TF1, TF1)
DL_TFC5 (TF2, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC
SDU size
(bits)
(note 2)
Test data size
(bits)

(note 2)
1 DL_TFC1 UL_TFC1 DL_TFC0, UL_TFC0
DL_TFC3,UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC4
RB5: 312 RB5: 312
DL_TFC3 ,UL_TFC3
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC3,
UL_TFC5
RB5: 632 RB5: 632
RB5: Test data size has been set to the payload size of the DL TF under test minus 8 bits (size of 7 bit length
indicator and expansion bit). The UL RLC SDU size has been set equal to the size of the payload size of the
UL TF under test minus 8 bits (the size of 7 bit length indicator and expansion bit).

14.2.23b.4 Test requirements
1. At step 10 the UE shall send a RADIO BEARER SETUP COMPLETE message.
Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2350
- for sub-test 1 and 2: an RLC SDU on RB5 having the same content as sent by the SS.
14.2.23c Interactive or background / UL:32 DL:32 kbps / PS RAB +UL:3.4
6.10.2.4.1.23c.
14.2.23c.1 Conformance requirement
See 14.2.4.1.
14.2.23c.2 Test purpose
clause 6.10.2.4.1.23c.
14.2.23c.3 Method of test
Uplink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148
TF2, bits 2x336 N/A
TF3, bits 3x336 N/A
TF4, bits 4x336 N/A

Uplink TFCS:
TFCI (RB5, DCCH)
UL_TFC0 (TF0, TF0)
UL_TFC1 (TF1, TF0)
UL_TFC2 (TF2, TF0)
UL_TFC3 (TF3, TF0)
UL_TFC4 (TF4, TF0)
UL_TFC5 (TF0, TF1)
UL_TFC6 (TF1, TF1)
UL_TFC7 (TF2, TF1)
UL_TFC8 (TF3, TF1)
UL_TFC9 (TF4, TF1)

Downlink TFS:
TFI
RB5
(32 kbps)
DCCH
TFS
TF0, bits 0x336 0x148
TF1, bits 1x336 1x148
TF2, bits 2x336 N/A
TF3, bits 3x336 N/A
TF4, bits 4x336 N/A

Release 5 3GPP TS 34.123-1 V5.7.1 (2004-04)
3GPP
2351
Downlink TFCS:
TFCI (RB5, DCCH)
DL_TFC0 (TF0, TF0)
DL_TFC1 (TF1, TF0)
DL_TFC2 (TF2, TF0)
DL_TFC3 (TF3, TF0)
DL_TFC4 (TF4, TF0)
DL_TFC5 (TF0, TF1)
DL_TFC6 (TF1, TF1)
DL_TFC7 (TF2, TF1)
DL_TFC8 (TF3, TF1)
DL_TFC9 (TF4, TF1)

Sub-tests:
Sub-
test
Downlink
TFCS
Under test
Uplink
TFCS
Under test

UL TFCIs

(note 1)
UL RLC
SDU size
(bits)
(note 2)
Test data size
(bits)

(note 2)
DL_TFC5,UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC5,
UL_TFC6
RB5: 312 RB5: 312
DL_TFC5 ,UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC2,
UL_TFC5,
UL_TFC7
RB5: 632 RB5: 632
DL_TFC5 ,UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC3,
UL_TFC5,
UL_TFC8
RB5: 952 RB5: 952
DL_TFC5 ,UL_TFC5
UL_TFC0,
UL_TFC1,
UL_TFC4,
UL_TFC5,
UL_TFC9
RB5: 1272 RB5: 1272
For RB5: Test data size has been set to the payload size of the DL TF under test minus 8 bits (size of 7 bit
length indicator and expansion bit). The UL RLC SDU size has been set equal to the size of the
payload size of the UL

1 571 - PLMN

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1 571 - PLMN

Caricato da

Copyright:

Formati disponibili

3GPP TS 34.123-1 V5.7.

Potrebbero piacerti anche